diff --git a/.github/workflows/crowdin-download-workflow.yml b/.github/workflows/crowdin-download-workflow.yml
deleted file mode 100644
index b366e389a1..0000000000
--- a/.github/workflows/crowdin-download-workflow.yml
+++ /dev/null
@@ -1,123 +0,0 @@
-name: Crowdin Download Action
-
-on:
-  workflow_call:
-  workflow_dispatch:
-    inputs:
-      target_branch:
-        description: "Branch to run this workflow on"
-        required: true
-        default: "main"
-  # schedule:
-  #   - cron: "20 14,18,22 * * 1,2,3,4,5" # Runs at 20 minutes past beginning/middle/end of day Mon-Fri (UTC-6) (an hour after the upload action)
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  crowdin_download:
-    runs-on: ubuntu-latest
-
-    env:
-      TARGET_BRANCH: ${{ github.event.inputs.target_branch || 'main' }}
-      BRANCH_NAME: feature/crowdin-download-${{ github.event.inputs.target_branch || 'main' }}
-
-    steps:
-      - name: Checkout target branch
-        uses: actions/checkout@v4
-        with:
-          ref: ${{ env.TARGET_BRANCH }}
-          fetch-depth: 0
-
-      - name: Set up Git
-        run: |
-          git config --global user.name 'github-actions'
-          git config --global user.email 'github-actions@github.com'
-
-      - name: Install GitHub CLI
-        run: sudo apt-get install -y gh
-
-      - name: Delete existing PR and branch if they exist
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          gh auth setup-git
-          PR_NUMBER=$(gh pr list --head $BRANCH_NAME --json number --jq '.[0].number' || echo "")
-          if [ -n "$PR_NUMBER" ]; then
-            echo "Closing existing PR #$PR_NUMBER"
-            gh pr close $PR_NUMBER --delete-branch || true
-          fi
-          git push origin --delete $BRANCH_NAME || true
-
-      - name: Create new branch
-        run: |
-          git checkout -b $BRANCH_NAME
-
-      - name: Synchronize with Crowdin
-        uses: crowdin/github-action@v2
-        with:
-          upload_sources: false
-          upload_translations: false
-          download_translations: true
-          localization_branch_name: ${{ env.BRANCH_NAME }}
-          create_pull_request: false
-          push_translations: false
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-          CROWDIN_PROJECT_ID: ${{ env.CROWDIN_PROJECT_ID }}
-          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
-
-      - name: Set up Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: "24"
-
-      - name: Install dependencies
-        run: yarn install --frozen-lockfile
-
-      - name: Fix permissions for i18n directory
-        run: |
-          sudo mkdir -p i18n
-          sudo chown -R $USER:$USER i18n
-          sudo chmod -R 755 i18n
-          find i18n -type d -exec chmod 755 {} \;
-          find i18n -type f -exec chmod 644 {} \;
-
-      - name: Run crowdin:fix
-        run: yarn run crowdin:fix
-
-      - name: Build application
-        run: npx docusaurus build --locale es
-
-      - name: Check for changes
-        id: changes
-        run: |
-          if git diff --quiet; then
-            echo "changes=false" >> $GITHUB_OUTPUT
-          else
-            echo "changes=true" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Fix Git permissions
-        run: |
-          sudo chown -R $USER:$USER .git
-          sudo chmod -R u+rwX .git
-
-      - name: Commit and push changes
-        if: steps.changes.outputs.changes == 'true'
-        run: |
-          git add .
-          git commit -m "chore: Download crowdin translations and run crowdin:fix" || echo "No changes to commit"
-          git push origin $BRANCH_NAME
-
-      - name: Create Pull Request
-        if: steps.changes.outputs.changes == 'true'
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          gh pr create --repo ${{ github.repository }} \
-            --base ${{ env.TARGET_BRANCH }} \
-            --head $BRANCH_NAME \
-            --title "Download translations and copy ignored files" \
-            --body "This PR was created by GitHub Actions to download crowdin translations and run crowdin:fix command."
diff --git a/.github/workflows/crowdin-manual-workflow.yml b/.github/workflows/crowdin-manual-workflow.yml
deleted file mode 100644
index 7504086f2c..0000000000
--- a/.github/workflows/crowdin-manual-workflow.yml
+++ /dev/null
@@ -1,12 +0,0 @@
-name: Crowdin Manual Upload and Download
-
-on:
-  workflow_dispatch:
-
-jobs:
-  trigger-upload:
-    uses: ./.github/workflows/crowdin-upload-workflow.yml
-
-  trigger-download:
-    needs: [ trigger-upload ]
-    uses: ./.github/workflows/crowdin-download-workflow.yml
diff --git a/.github/workflows/crowdin-upload-workflow.yml b/.github/workflows/crowdin-upload-workflow.yml
deleted file mode 100644
index dda8ccb36e..0000000000
--- a/.github/workflows/crowdin-upload-workflow.yml
+++ /dev/null
@@ -1,45 +0,0 @@
-name: Crowdin Upload Action
-
-on:
-  workflow_call:
-  workflow_dispatch:
-  # schedule:
-  #   - cron: "20 13,17,21 * * 1,2,3,4,5" # Runs at 20 minutes past beginning/middle/end of day Mon-Fri (UTC-6)
-
-jobs:
-  crowdin-upload:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout Docs Repo
-        uses: actions/checkout@v4
-
-      - name: Setup Node
-        uses: actions/setup-node@v4
-        with:
-          node-version: "24"
-          cache: "yarn"
-          cache-dependency-path: "**/yarn.lock"
-
-      - name: Install Dependencies
-        run: yarn --prefer-offline --frozen-lockfile
-
-      - name: Generate CLI Docs
-        run: yarn stellar-cli:build
-
-      - name: (temp) Fix CLI links
-        run: yarn stellar-cli:fix-links
-        shell: bash
-
-      - name: Write Translations
-        run: yarn write-translations
-
-      - name: Crowdin push
-        uses: crowdin/github-action@v2
-        with:
-          upload_sources: true
-          upload_translations: false
-          download_translations: false
-          upload_sources_args: --delete-obsolete
-        env:
-          CROWDIN_PROJECT_ID: ${{ env.CROWDIN_PROJECT_ID }}
-          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
diff --git a/CROWDIN.md b/CROWDIN.md
deleted file mode 100644
index d04679d467..0000000000
--- a/CROWDIN.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Crowdin Translator How-To
-
-Stellar Developer Docs use [Crowdin](https://crowdin.com/) for localization. This document provides steps and resources for managing Stellar Docusaurus Crowdin translations as a Crowdin user with a Translator role.
-
----
-
-## Overview
-
-As new English source files are added to the Stellar Docusaurus Documentation GitHub repository, they are automatically uploaded to Crowdin. From there, an automated AI translation is run on the files to translate them into other target languages (currently only Spanish at the time of writing).
-
-In cases where the AI translation is inaccurate, a user with the Translator role will need to update and edit the translations manually.
-
----
-
-## Translator User
-
-To get started, you need to set up a Crowdin account and be added to the Stellar Documents Crowdin project. This involves creating a Crowdin user account and requesting access to the project from a project owner. 
-
-For more details, see the following documentation: 
-[Create an Account](https://support.crowdin.com/for-translators/#create-an-account)
-
----
-
-## Editor
-
-As a translator, you will have access to the editor, where you can make changes to the content. 
-
-**Note:** Crowdin uses the term "strings" for content being translated.
-
-You can access all translated documents via the Crowdin dashboard. From there, you can view each document in the editor. 
-
-For more details on working within the editor, see the following documentation: 
-[Working in the Editor](https://support.crowdin.com/for-translators/#working-in-the-editor) 
-
-For a more in-depth look, see: 
-[Online Editor Guide](https://support.crowdin.com/online-editor/)
-
----
-
-## Glossary
-
-For common words or phrases, it is good practice to add them to the glossary. The glossary helps the AI translator provide more accurate translations. 
-
-Examples include: 
-- Words or phrases that need to be translated in a specific manner. 
-- Words or phrases that should not be translated at all. 
-
-For more information, see the following documentation: 
-[Glossary](https://support.crowdin.com/glossary/)
-
----
-
-## Approving Translations
-
-As documents are translated, they will be assigned a translation percentage highlighted in blue. 
-
-To manage files that have been checked or proofread, it is recommended to mark them as approved. Approved files will display an approved percentage highlighted in green. 
-
-**Note:** All translations are synced with the Stellar Docusaurus Documentation after they are reviewed and approved. Approval is a check for managing translation files that have been edited. 
-
-For more information on approving translations, see the following documentation: 
-[Proofreading](https://support.crowdin.com/online-editor/#proofreading)
diff --git a/Dockerfile b/Dockerfile
index a3bc7d8831..c86537da9c 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -14,7 +14,6 @@ RUN apt-get update && apt-get install --no-install-recommends -y gpg curl git ma
     apt-get update && apt-get install -y nodejs yarn && apt-get clean
 
 COPY . /app/
-ARG BUILD_TRANSLATIONS="False"
 
 RUN yarn cache clean --all
 RUN yarn install --frozen-lockfile
@@ -24,12 +23,6 @@ RUN yarn stellar-cli:build --no-minify --cli-ref=main
 RUN yarn stellar-cli:fix-links
 
 ENV NODE_OPTIONS="--max-old-space-size=4096"
-# RUN if [ "$BUILD_TRANSLATIONS" = "True" ]; then \
-#     yarn docusaurus build --no-minify; \
-#   else \
-#     # In the preview build, we only want to build for English. Much quicker
-#     yarn build --no-minify; \
-#   fi
 RUN yarn build --no-minify
 
 FROM nginx:1.29
diff --git a/Makefile b/Makefile
index 1f2918e81a..564a4a97de 100644
--- a/Makefile
+++ b/Makefile
@@ -8,12 +8,9 @@ LABEL ?= $(shell git rev-parse --short HEAD)$(and $(shell git status -s),-dirty-
 TAG ?= stellar/stellar-docs:$(LABEL)
 # https://github.com/opencontainers/image-spec/blob/master/annotations.md
 BUILD_DATE := $(shell date -u +%FT%TZ)
-# If we're not in production, don't build translations
-BUILD_TRANSLATIONS ?= "False"
-
 # the app label is used by the pipelines to prune docker dangling images on the jenkins build hosts
 docker-build:
-	$(SUDO) docker build -m 8g --no-cache --pull --label app="stellar-docs" --label org.opencontainers.image.created="$(BUILD_DATE)" -t $(TAG) . --build-arg BUILD_TRANSLATIONS=${BUILD_TRANSLATIONS}
+	$(SUDO) docker build -m 8g --no-cache --pull --label app="stellar-docs" --label org.opencontainers.image.created="$(BUILD_DATE)" -t $(TAG) .
 
 docker-push:
 	$(SUDO) docker push $(TAG)
diff --git a/config/constants.ts b/config/constants.ts
index b2266ca786..08a59d7722 100644
--- a/config/constants.ts
+++ b/config/constants.ts
@@ -1,15 +1,3 @@
-export const DEFAULT_LOCALE: string = 'en';
-export const LOCALE_FULL_CODE: Record<string, string> = {
-  es: 'es-ES',
-};
-
-export const makeEditUrl = ({ locale, versionDocsDirPath, docPath }) => {
-  if (locale !== DEFAULT_LOCALE) {
-    return `https://crowdin.com/project/stellar-dev-docs/${LOCALE_FULL_CODE[locale]}`
-  }
-  return `https://github.com/stellar/stellar-docs/edit/main/${versionDocsDirPath}/${docPath}`
-};
-
 export const CODE_LANGS = {
   bash: 'bash',
   cpp: 'C++',
diff --git a/config/theme/navbar.ts b/config/theme/navbar.ts
index 2363754141..49b62f31b7 100644
--- a/config/theme/navbar.ts
+++ b/config/theme/navbar.ts
@@ -552,10 +552,6 @@ const translation: NavbarItem[] = [
     position: 'right',
     value: GOOGLE_TRANSLATE_ELEMENT,
   },
-  // {
-  //   type: 'localeDropdown',
-  //   position: 'right',
-  // },
 ]
 
 export default {
diff --git a/crowdin.yaml b/crowdin.yaml
deleted file mode 100644
index d66aae9834..0000000000
--- a/crowdin.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Crowdin credentials
-project_id: '669532'
-api_token_env: CROWDIN_PERSONAL_TOKEN
-
-# Choose file structure in Crowdin
-# e.g. true or false
-preserve_hierarchy: true
-
-# Files configuration
-files:
-  # JSON translation files
-  - source: /i18n/en/**/*
-    translation: /i18n/%two_letters_code%/**/%original_file_name%
-  # Docs Markdown files
-  - source: /docs/**/*
-    translation: /i18n/%two_letters_code%/docusaurus-plugin-content-docs/current/**/%original_file_name%
-    ignore : ['**/*.api.mdx', '**/*.info.mdx', '**/*.tag.mdx', '**/*.schema.mdx', '**/*.json']
-  # Meeting Notes Blog Markdown files
-  - source: /meeting-notes/**/*
-    translation: /i18n/%two_letters_code%/docusaurus-plugin-content-blog/**/%original_file_name%
-  # Pages Markdown files
-  - source: /src/pages/**/*
-    translation: /i18n/%two_letters_code%/docusaurus-plugin-content-pages/**/%original_file_name%
-    ignore: ['**/*.js', '**/*.jsx', '**/*.ts', '**/*.tsx', '**/*.css']
-    type: 'mdx_v2'
diff --git a/docusaurus.config.ts b/docusaurus.config.ts
index 3f7570a17f..c5ce768525 100644
--- a/docusaurus.config.ts
+++ b/docusaurus.config.ts
@@ -2,7 +2,6 @@ import remarkMath from 'remark-math';
 import rehypeKatex from 'rehype-katex';
 import { themes as prismThemes } from 'prism-react-renderer';
 
-// import { makeEditUrl, DEFAULT_LOCALE, GOOGLE_TRANSLATE_ELEMENT } from './config/constants';
 import navbarItems from './config/theme/navbar';
 import footerColumns from './config/theme/footer';
 import { headTags } from './config/theme/headTags';
@@ -27,10 +26,6 @@ const config: Config = {
   favicon: "img/docusaurus/favicon-96x96.png",
   organizationName: "stellar",
   projectName: "stellar-docs",
-  // i18n: {
-  //   defaultLocale: DEFAULT_LOCALE,
-  //   locales: ["en", "es"],
-  // },
   scripts: [
     {
       src: 'https://translate.google.com/translate_a/element.js',
@@ -121,7 +116,6 @@ const config: Config = {
           rehypePlugins: [rehypeKatex],
           sidebarPath: "config/sidebars.ts",
           sidebarItemsGenerator: require("./src/sidebar-generator"),
-          // editUrl: makeEditUrl,
           editUrl: "https://github.com/stellar/stellar-docs/edit/main",
           exclude: ['**/component/**', '**/CONTRIBUTING.md'],
         },
diff --git a/i18n/en/code.json b/i18n/en/code.json
deleted file mode 100644
index 852068e0f9..0000000000
--- a/i18n/en/code.json
+++ /dev/null
@@ -1,748 +0,0 @@
-{
-  "components.CodeExample.NoLanguageTabTitle": {
-    "message": "Example",
-    "description": "The tab title for a code example where no programming language was specified"
-  },
-  "components.EndpointsTable.Endpoints": {
-    "message": "Endpoints",
-    "description": "The default title for a table of API endpoints"
-  },
-  "components.CodeExample.MissingCodeExample": {
-    "message": "// There is no code example for {language} yet",
-    "description": "In the Wallet-SDK code example component, this message will display when the selected programming language has no accompanying example"
-  },
-  "components.WalletGuideWarn.WorkInProgress": {
-    "message": "Documentation for this language is currently work in progress. Some of information may not be applicable for this language, or missing. Code samples may be incomplete.",
-    "description": "For the Wallets SDK, if a given programming language is incomplete, display an admonition warning the user"
-  },
-  "components.ExampleResponse.Example": {
-    "message": "Example",
-    "description": "The default title for a table of example API responses"
-  },
-  "components.ReaderFeedback.ThankYou": {
-    "message": "Thanks for your feedback!",
-    "description": "Message to thank a reader for clicking a thumbsup/thumbdown button"
-  },
-  "components.ReaderFeedback.Prompt": {
-    "message": "Did you find this page helpful?",
-    "description": "A prompt to invite the reader to click a thumbsup/thumbsdown button"
-  },
-  "theme.NotFound.title": {
-    "message": "Page Not Found",
-    "description": "The title of the 404 page"
-  },
-  "components.AttributeTable.ListItem.ShowChildAttributes": {
-    "message": "Show child attributes",
-    "description": "For hand-written API schema pages, a message to tell readers they can expand a section to see more sub-items"
-  },
-  "component.Homepage.DeveloperResources.Discord.Title": {
-    "message": "Stellar Developer Discord"
-  },
-  "component.Homepage.DeveloperResources.Discord.Description": {
-    "message": "Ask questions and engage with other Stellar devs.",
-    "description": "Long description of what kind of developer resource this is."
-  },
-  "component.Homepage.DeveloperResources.DeveloperSite.Title": {
-    "message": "Developer Site"
-  },
-  "component.Homepage.DeveloperResources.DeveloperSite.Description": {
-    "message": "Get the latest news and insights about building on Stellar.",
-    "description": "Long description of what kind of developer resource this is."
-  },
-  "component.Homepage.DeveloperResources.StackExchange.Title": {
-    "message": "Stellar Stack Exchange"
-  },
-  "component.Homepage.DeveloperResources.StackExchange.Description": {
-    "message": "A question and answer site for Stellar developers; if you can’t find what you’re looking for in the docs, try searching the Stack Exchange to see if your question has been addressed. If it hasn't, feel free to ask!",
-    "description": "Long description of what kind of developer resource this is."
-  },
-  "component.Homepage.DeveloperResources.GoogleGroup.Title": {
-    "message": "Stellar Developers Google Group"
-  },
-  "component.Homepage.DeveloperResources.GoogleGroup.Description": {
-    "message": "Discuss Core Advancement Proposals (CAPs) and Stellar Ecosystem Proposals (SEPs), talk about the development of Stellar Core and Horizon, and stay informed about important network upgrades.",
-    "description": "Long description of what kind of developer resource this is."
-  },
-  "component.Homepage.DocsContribution.Heading": {
-    "message": "Contribute to the docs and leave feedback"
-  },
-  "component.Homepage.DocsContribution.Paragraph1": {
-    "message": "Stellar’s Developer Documentation is open-source, and contributions to the docs are encouraged. You can file an issue or pull request to add new content, suggest revisions to existing content, submit suggestions, report bugs, and more in the {githubRepoLink}."
-  },
-  "component.Homepage.DocsContribution.DocsGithubLink": {
-    "message": "Stellar Docs GitHub Repo",
-    "description": "Label for the link to the Stellar docs repository on Github"
-  },
-  "component.Homepage.DocsContribution.Paragraph2": {
-    "message": "Also, feel free to leave any additional feedback by filing issues in the various other {githubOrgLink}."
-  },
-  "component.Homepage.DocsContribution.StellarRepos": {
-    "message": "Stellar repos",
-    "description": "Label for the link to the Stellar organization profile on Github"
-  },
-  "component.Homepage.ExploreButton.Text": {
-    "message": "Explore",
-    "description": "The text that will be displayed on the \"Explore\" buttons"
-  },
-  "component.Homepage.NavigatingTheDocs.Build.Title": {
-    "message": "Build"
-  },
-  "component.Homepage.NavigatingTheDocs.Build.Description": {
-    "message": "Contains tutorials and how-to guides for writing smart contracts, building applications, interacting with the network, and more.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Learn.Title": {
-    "message": "Learn"
-  },
-  "component.Homepage.NavigatingTheDocs.Learn.Description": {
-    "message": "Find all informational and conceptual content here. Learn about Stellar fundamentals like how accounts and transactions function, dive deeper into the functionality of each operation, discover how fees work, and more.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Tokens.Title": {
-    "message": "Tokens"
-  },
-  "component.Homepage.NavigatingTheDocs.Tokens.Description": {
-    "message": "Information on how to issue assets on the Stellar network and create custom smart contract tokens.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Data.Title": {
-    "message": "Data"
-  },
-  "component.Homepage.NavigatingTheDocs.Data.Description": {
-    "message": "Discover various data availability options: RPC, Hubble, Horizon, Galexie, and data indexers.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Tools.Title": {
-    "message": "Tools"
-  },
-  "component.Homepage.NavigatingTheDocs.Tools.Description": {
-    "message": "Learn about all the available tools for building on, interacting with, or just watching the Stellar network. Also, find information on how to use the Anchor Platform or Stellar Disbursement Platform.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Networks.Title": {
-    "message": "Networks"
-  },
-  "component.Homepage.NavigatingTheDocs.Networks.Description": {
-    "message": "Information about deployed networks (Mainnet, Testnet, and Futurenet), current software versions, resource limitations, and fees.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Validators.Title": {
-    "message": "Validators"
-  },
-  "component.Homepage.NavigatingTheDocs.Validators.Description": {
-    "message": "Everything you'll need to know if you want to run, operate, and maintain a core validator node on the Stellar network.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.LearnMoreButton.Text": {
-    "message": "Learn More",
-    "description": "The text that will be displayed on the \"Learn More\" buttons"
-  },
-  "components.WayfindingBoxes.AssetIssuers.Title": {
-    "message": "Asset Issuers"
-  },
-  "components.WayfindingBoxes.AssetIssuers.Description": {
-    "message": "Issue an asset or create a custom smart contract token.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.SmartContractDevelopers.Title": {
-    "message": "Smart Contract Developers"
-  },
-  "components.WayfindingBoxes.SmartContractDevelopers.Description": {
-    "message": "Write smart contracts on the Stellar network.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.RampsAnchors.Title": {
-    "message": "Ramps (Anchors)"
-  },
-  "components.WayfindingBoxes.RampsAnchors.Description": {
-    "message": "Learn about and set up an anchor.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.Applications.Title": {
-    "message": "Applications"
-  },
-  "components.WayfindingBoxes.Applications.Description": {
-    "message": "Build a traditional wallet, dapp, or list Stellar assets on an exchange.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.InfrastructureProviders.Title": {
-    "message": "Infrastructure Providers"
-  },
-  "components.WayfindingBoxes.InfrastructureProviders.Description": {
-    "message": "Set up a Horizon or RPC service.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.Analytics.Title": {
-    "message": "Analytics"
-  },
-  "components.WayfindingBoxes.Analytics.Description": {
-    "message": "Use Hubble to perform analysis on Stellar network data.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.HowToGuides.GuidesInCategory": {
-    "message": "Guides in this category:",
-    "description": "The h3 title do display the other related how-to guides"
-  },
-  "theme.NotFound.p1": {
-    "message": "We could not find what you were looking for.",
-    "description": "The first paragraph of the 404 page"
-  },
-  "theme.NotFound.p2": {
-    "message": "Please contact the owner of the site that linked you to the original URL and let them know their link is broken.",
-    "description": "The 2nd paragraph of the 404 page"
-  },
-  "theme.ErrorPageContent.title": {
-    "message": "This page crashed.",
-    "description": "The title of the fallback page when the page crashed"
-  },
-  "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "Scroll back to top",
-    "description": "The ARIA label for the back to top button"
-  },
-  "theme.blog.archive.title": {
-    "message": "Archive",
-    "description": "The page & hero title of the blog archive page"
-  },
-  "theme.blog.archive.description": {
-    "message": "Archive",
-    "description": "The page & hero description of the blog archive page"
-  },
-  "theme.blog.paginator.navAriaLabel": {
-    "message": "Blog list page navigation",
-    "description": "The ARIA label for the blog pagination"
-  },
-  "theme.blog.paginator.newerEntries": {
-    "message": "Newer entries",
-    "description": "The label used to navigate to the newer blog posts page (previous page)"
-  },
-  "theme.blog.paginator.olderEntries": {
-    "message": "Older entries",
-    "description": "The label used to navigate to the older blog posts page (next page)"
-  },
-  "theme.blog.post.paginator.navAriaLabel": {
-    "message": "Blog post page navigation",
-    "description": "The ARIA label for the blog posts pagination"
-  },
-  "theme.blog.post.paginator.newerPost": {
-    "message": "Newer post",
-    "description": "The blog post button label to navigate to the newer/previous post"
-  },
-  "theme.blog.post.paginator.olderPost": {
-    "message": "Older post",
-    "description": "The blog post button label to navigate to the older/next post"
-  },
-  "theme.tags.tagsPageLink": {
-    "message": "View all tags",
-    "description": "The label of the link targeting the tag list page"
-  },
-  "theme.colorToggle.ariaLabel": {
-    "message": "Switch between dark and light mode (currently {mode})",
-    "description": "The ARIA label for the color mode toggle"
-  },
-  "theme.colorToggle.ariaLabel.mode.dark": {
-    "message": "dark mode",
-    "description": "The name for the dark color mode"
-  },
-  "theme.colorToggle.ariaLabel.mode.light": {
-    "message": "light mode",
-    "description": "The name for the light color mode"
-  },
-  "theme.docs.DocCard.categoryDescription.plurals": {
-    "message": "1 item|{count} items",
-    "description": "The default description for a category card in the generated index about how many items this category includes"
-  },
-  "theme.docs.breadcrumbs.navAriaLabel": {
-    "message": "Breadcrumbs",
-    "description": "The ARIA label for the breadcrumbs"
-  },
-  "theme.docs.paginator.navAriaLabel": {
-    "message": "Docs pages",
-    "description": "The ARIA label for the docs pagination"
-  },
-  "theme.docs.paginator.previous": {
-    "message": "Previous",
-    "description": "The label used to navigate to the previous doc"
-  },
-  "theme.docs.paginator.next": {
-    "message": "Next",
-    "description": "The label used to navigate to the next doc"
-  },
-  "theme.docs.tagDocListPageTitle.nDocsTagged": {
-    "message": "One doc tagged|{count} docs tagged",
-    "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.tagDocListPageTitle": {
-    "message": "{nDocsTagged} with \"{tagName}\"",
-    "description": "The title of the page for a docs tag"
-  },
-  "theme.docs.versionBadge.label": {
-    "message": "Version: {versionLabel}"
-  },
-  "theme.docs.versions.unreleasedVersionLabel": {
-    "message": "This is unreleased documentation for {siteTitle} {versionLabel} version.",
-    "description": "The label used to tell the user that he's browsing an unreleased doc version"
-  },
-  "theme.docs.versions.unmaintainedVersionLabel": {
-    "message": "This is documentation for {siteTitle} {versionLabel}, which is no longer actively maintained.",
-    "description": "The label used to tell the user that he's browsing an unmaintained doc version"
-  },
-  "theme.docs.versions.latestVersionSuggestionLabel": {
-    "message": "For up-to-date documentation, see the {latestVersionLink} ({versionLabel}).",
-    "description": "The label used to tell the user to check the latest version"
-  },
-  "theme.docs.versions.latestVersionLinkLabel": {
-    "message": "latest version",
-    "description": "The label used for the latest version suggestion link label"
-  },
-  "theme.common.editThisPage": {
-    "message": "Edit this page",
-    "description": "The link label to edit the current page"
-  },
-  "theme.common.headingLinkTitle": {
-    "message": "Direct link to {heading}",
-    "description": "Title for link to heading"
-  },
-  "theme.lastUpdated.atDate": {
-    "message": " on {date}",
-    "description": "The words used to describe on which date a page has been last updated"
-  },
-  "theme.lastUpdated.byUser": {
-    "message": " by {user}",
-    "description": "The words used to describe by who the page has been last updated"
-  },
-  "theme.lastUpdated.lastUpdatedAtBy": {
-    "message": "Last updated{atDate}{byUser}",
-    "description": "The sentence used to display when a page has been last updated, and by who"
-  },
-  "theme.navbar.mobileVersionsDropdown.label": {
-    "message": "Versions",
-    "description": "The label for the navbar versions dropdown on mobile view"
-  },
-  "theme.tags.tagsListLabel": {
-    "message": "Tags:",
-    "description": "The label alongside a tag list"
-  },
-  "theme.admonition.caution": {
-    "message": "caution",
-    "description": "The default label used for the Caution admonition (:::caution)"
-  },
-  "theme.admonition.danger": {
-    "message": "danger",
-    "description": "The default label used for the Danger admonition (:::danger)"
-  },
-  "theme.admonition.info": {
-    "message": "info",
-    "description": "The default label used for the Info admonition (:::info)"
-  },
-  "theme.admonition.note": {
-    "message": "note",
-    "description": "The default label used for the Note admonition (:::note)"
-  },
-  "theme.admonition.tip": {
-    "message": "tip",
-    "description": "The default label used for the Tip admonition (:::tip)"
-  },
-  "theme.admonition.warning": {
-    "message": "warning",
-    "description": "The default label used for the Warning admonition (:::warning)"
-  },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "Close",
-    "description": "The ARIA label for close button of announcement bar"
-  },
-  "theme.blog.sidebar.navAriaLabel": {
-    "message": "Blog recent posts navigation",
-    "description": "The ARIA label for recent posts in the blog sidebar"
-  },
-  "theme.CodeBlock.copied": {
-    "message": "Copied",
-    "description": "The copied button label on code blocks"
-  },
-  "theme.CodeBlock.copyButtonAriaLabel": {
-    "message": "Copy code to clipboard",
-    "description": "The ARIA label for copy code blocks button"
-  },
-  "theme.CodeBlock.copy": {
-    "message": "Copy",
-    "description": "The copy button label on code blocks"
-  },
-  "theme.CodeBlock.wordWrapToggle": {
-    "message": "Toggle word wrap",
-    "description": "The title attribute for toggle word wrapping button of code block lines"
-  },
-  "theme.DocSidebarItem.expandCategoryAriaLabel": {
-    "message": "Expand sidebar category '{label}'",
-    "description": "The ARIA label to expand the sidebar category"
-  },
-  "theme.DocSidebarItem.collapseCategoryAriaLabel": {
-    "message": "Collapse sidebar category '{label}'",
-    "description": "The ARIA label to collapse the sidebar category"
-  },
-  "theme.NavBar.navAriaLabel": {
-    "message": "Main",
-    "description": "The ARIA label for the main navigation"
-  },
-  "theme.TOCCollapsible.toggleButtonLabel": {
-    "message": "On this page",
-    "description": "The label used by the button on the collapsible TOC component"
-  },
-  "theme.navbar.mobileLanguageDropdown.label": {
-    "message": "Languages",
-    "description": "The label for the mobile language switcher dropdown"
-  },
-  "theme.blog.post.readMore": {
-    "message": "Read more",
-    "description": "The label used in blog post item excerpts to link to full blog posts"
-  },
-  "theme.blog.post.readMoreLabel": {
-    "message": "Read more about {title}",
-    "description": "The ARIA label for the link to full blog posts from excerpts"
-  },
-  "theme.blog.post.readingTime.plurals": {
-    "message": "One min read|{readingTime} min read",
-    "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.breadcrumbs.home": {
-    "message": "Home page",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
-  "theme.docs.sidebar.collapseButtonTitle": {
-    "message": "Collapse sidebar",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.collapseButtonAriaLabel": {
-    "message": "Collapse sidebar",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.navAriaLabel": {
-    "message": "Docs sidebar",
-    "description": "The ARIA label for the sidebar navigation"
-  },
-  "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
-    "message": "Close navigation bar",
-    "description": "The ARIA label for close button of mobile sidebar"
-  },
-  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
-    "message": "← Back to main menu",
-    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
-  },
-  "theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
-    "message": "Toggle navigation bar",
-    "description": "The ARIA label for hamburger menu button of mobile navigation"
-  },
-  "theme.docs.sidebar.expandButtonTitle": {
-    "message": "Expand sidebar",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.docs.sidebar.expandButtonAriaLabel": {
-    "message": "Expand sidebar",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.SearchBar.seeAll": {
-    "message": "See all {count} results"
-  },
-  "theme.SearchPage.documentsFound.plurals": {
-    "message": "One document found|{count} documents found",
-    "description": "Pluralized label for \"{count} documents found\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.SearchPage.existingResultsTitle": {
-    "message": "Search results for \"{query}\"",
-    "description": "The search page title for non-empty query"
-  },
-  "theme.SearchPage.emptyResultsTitle": {
-    "message": "Search the documentation",
-    "description": "The search page title for empty query"
-  },
-  "theme.SearchPage.inputPlaceholder": {
-    "message": "Type your search here",
-    "description": "The placeholder for search page input"
-  },
-  "theme.SearchPage.inputLabel": {
-    "message": "Search",
-    "description": "The ARIA label for search page input"
-  },
-  "theme.SearchPage.algoliaLabel": {
-    "message": "Search by Algolia",
-    "description": "The description label for Algolia mention"
-  },
-  "theme.SearchPage.noResultsText": {
-    "message": "No results were found",
-    "description": "The paragraph for empty search result"
-  },
-  "theme.SearchPage.fetchingNewResults": {
-    "message": "Fetching new results...",
-    "description": "The paragraph for fetching new search results"
-  },
-  "theme.SearchBar.label": {
-    "message": "Search",
-    "description": "The ARIA label and placeholder for search button"
-  },
-  "theme.SearchModal.searchBox.resetButtonTitle": {
-    "message": "Clear the query",
-    "description": "The label and ARIA label for search box reset button"
-  },
-  "theme.SearchModal.searchBox.cancelButtonText": {
-    "message": "Cancel",
-    "description": "The label and ARIA label for search box cancel button"
-  },
-  "theme.SearchModal.startScreen.recentSearchesTitle": {
-    "message": "Recent",
-    "description": "The title for recent searches"
-  },
-  "theme.SearchModal.startScreen.noRecentSearchesText": {
-    "message": "No recent searches",
-    "description": "The text when there are no recent searches"
-  },
-  "theme.SearchModal.startScreen.saveRecentSearchButtonTitle": {
-    "message": "Save this search",
-    "description": "The title for save recent search button"
-  },
-  "theme.SearchModal.startScreen.removeRecentSearchButtonTitle": {
-    "message": "Remove this search from history",
-    "description": "The title for remove recent search button"
-  },
-  "theme.SearchModal.startScreen.favoriteSearchesTitle": {
-    "message": "Favorite",
-    "description": "The title for favorite searches"
-  },
-  "theme.SearchModal.startScreen.removeFavoriteSearchButtonTitle": {
-    "message": "Remove this search from favorites",
-    "description": "The title for remove favorite search button"
-  },
-  "theme.SearchModal.errorScreen.titleText": {
-    "message": "Unable to fetch results",
-    "description": "The title for error screen"
-  },
-  "theme.SearchModal.errorScreen.helpText": {
-    "message": "You might want to check your network connection.",
-    "description": "The help text for error screen"
-  },
-  "theme.SearchModal.footer.selectText": {
-    "message": "to select",
-    "description": "The select text for footer"
-  },
-  "theme.SearchModal.footer.selectKeyAriaLabel": {
-    "message": "Enter key",
-    "description": "The ARIA label for select key in footer"
-  },
-  "theme.SearchModal.footer.navigateText": {
-    "message": "to navigate",
-    "description": "The navigate text for footer"
-  },
-  "theme.SearchModal.footer.navigateUpKeyAriaLabel": {
-    "message": "Arrow up",
-    "description": "The ARIA label for navigate up key in footer"
-  },
-  "theme.SearchModal.footer.navigateDownKeyAriaLabel": {
-    "message": "Arrow down",
-    "description": "The ARIA label for navigate down key in footer"
-  },
-  "theme.SearchModal.footer.closeText": {
-    "message": "to close",
-    "description": "The close text for footer"
-  },
-  "theme.SearchModal.footer.closeKeyAriaLabel": {
-    "message": "Escape key",
-    "description": "The ARIA label for close key in footer"
-  },
-  "theme.SearchModal.footer.searchByText": {
-    "message": "Search by",
-    "description": "The 'Powered by' text for footer"
-  },
-  "theme.SearchModal.noResultsScreen.noResultsText": {
-    "message": "No results for",
-    "description": "The text when there are no results"
-  },
-  "theme.SearchModal.noResultsScreen.suggestedQueryText": {
-    "message": "Try searching for",
-    "description": "The text for suggested query"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsText": {
-    "message": "Believe this query should return results?",
-    "description": "The text for reporting missing results"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsLinkText": {
-    "message": "Let us know.",
-    "description": "The link text for reporting missing results"
-  },
-  "theme.SearchModal.placeholder": {
-    "message": "Search docs",
-    "description": "The placeholder of the input of the DocSearch pop-up modal"
-  },
-  "theme.blog.post.plurals": {
-    "message": "One post|{count} posts",
-    "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.blog.tagTitle": {
-    "message": "{nPosts} tagged with \"{tagName}\"",
-    "description": "The title of the page for a blog tag"
-  },
-  "theme.blog.author.pageTitle": {
-    "message": "{authorName} - {nPosts}",
-    "description": "The title of the page for a blog author"
-  },
-  "theme.blog.authorsList.pageTitle": {
-    "message": "Authors",
-    "description": "The title of the authors page"
-  },
-  "theme.blog.authorsList.viewAll": {
-    "message": "View all authors",
-    "description": "The label of the link targeting the blog authors page"
-  },
-  "theme.blog.author.noPosts": {
-    "message": "This author has not written any posts yet.",
-    "description": "The text for authors with 0 blog post"
-  },
-  "theme.contentVisibility.unlistedBanner.title": {
-    "message": "Unlisted page",
-    "description": "The unlisted content banner title"
-  },
-  "theme.contentVisibility.unlistedBanner.message": {
-    "message": "This page is unlisted. Search engines will not index it, and only users having a direct link can access it.",
-    "description": "The unlisted content banner message"
-  },
-  "theme.contentVisibility.draftBanner.title": {
-    "message": "Draft page",
-    "description": "The draft content banner title"
-  },
-  "theme.contentVisibility.draftBanner.message": {
-    "message": "This page is a draft. It will only be visible in dev and be excluded from the production build.",
-    "description": "The draft content banner message"
-  },
-  "theme.ErrorPageContent.tryAgain": {
-    "message": "Try again",
-    "description": "The label of the button to try again rendering when the React error boundary captures an error"
-  },
-  "theme.common.skipToMainContent": {
-    "message": "Skip to main content",
-    "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
-  },
-  "theme.tags.tagsPageTitle": {
-    "message": "Tags",
-    "description": "The title of the tag list page"
-  },
-  "theme.colorToggle.ariaLabel.mode.system": {
-    "message": "system mode",
-    "description": "The name for the system color mode"
-  },
-  "theme.navbar.mobileDropdown.collapseButton.expandAriaLabel": {
-    "message": "Expand the dropdown",
-    "description": "The ARIA label of the button to expand the mobile dropdown navbar item"
-  },
-  "theme.navbar.mobileDropdown.collapseButton.collapseAriaLabel": {
-    "message": "Collapse the dropdown",
-    "description": "The ARIA label of the button to collapse the mobile dropdown navbar item"
-  },
-  "components.ReaderFeedback.ThumbsUp.Title": {
-    "message": "Like",
-    "description": "The title value for the thumbsup icon"
-  },
-  "components.ReaderFeedback.ThumbsDown.Title": {
-    "message": "Dislike",
-    "description": "The title value for the thumbsdown icon"
-  },
-  "theme.IconExternalLink.ariaLabel": {
-    "message": "(opens in new tab)",
-    "description": "The ARIA label for the external link icon"
-  },
-  "theme.SearchModal.searchBox.placeholderText": {
-    "message": "Search docs",
-    "description": "The placeholder text for the main search input field"
-  },
-  "theme.SearchModal.searchBox.placeholderTextAskAi": {
-    "message": "Ask another question...",
-    "description": "The placeholder text when in AI question mode"
-  },
-  "theme.SearchModal.searchBox.placeholderTextAskAiStreaming": {
-    "message": "Answering...",
-    "description": "The placeholder text for search box when AI is streaming an answer"
-  },
-  "theme.SearchModal.searchBox.enterKeyHint": {
-    "message": "search",
-    "description": "The hint for the search box enter key text"
-  },
-  "theme.SearchModal.searchBox.enterKeyHintAskAi": {
-    "message": "enter",
-    "description": "The hint for the Ask AI search box enter key text"
-  },
-  "theme.SearchModal.searchBox.searchInputLabel": {
-    "message": "Search",
-    "description": "The ARIA label for search input"
-  },
-  "theme.SearchModal.searchBox.backToKeywordSearchButtonText": {
-    "message": "Back to keyword search",
-    "description": "The text for back to keyword search button"
-  },
-  "theme.SearchModal.searchBox.backToKeywordSearchButtonAriaLabel": {
-    "message": "Back to keyword search",
-    "description": "The ARIA label for back to keyword search button"
-  },
-  "theme.SearchModal.startScreen.recentConversationsTitle": {
-    "message": "Recent conversations",
-    "description": "The title for recent conversations"
-  },
-  "theme.SearchModal.startScreen.removeRecentConversationButtonTitle": {
-    "message": "Remove this conversation from history",
-    "description": "The title for remove recent conversation button"
-  },
-  "theme.SearchModal.resultsScreen.askAiPlaceholder": {
-    "message": "Ask AI: ",
-    "description": "The placeholder text for Ask AI input"
-  },
-  "theme.SearchModal.askAiScreen.disclaimerText": {
-    "message": "Answers are generated with AI which can make mistakes. Verify responses.",
-    "description": "The disclaimer text for AI answers"
-  },
-  "theme.SearchModal.askAiScreen.relatedSourcesText": {
-    "message": "Related sources",
-    "description": "The text for related sources"
-  },
-  "theme.SearchModal.askAiScreen.thinkingText": {
-    "message": "Thinking...",
-    "description": "The text when AI is thinking"
-  },
-  "theme.SearchModal.askAiScreen.copyButtonText": {
-    "message": "Copy",
-    "description": "The text for copy button"
-  },
-  "theme.SearchModal.askAiScreen.copyButtonCopiedText": {
-    "message": "Copied!",
-    "description": "The text for copy button when copied"
-  },
-  "theme.SearchModal.askAiScreen.copyButtonTitle": {
-    "message": "Copy",
-    "description": "The title for copy button"
-  },
-  "theme.SearchModal.askAiScreen.likeButtonTitle": {
-    "message": "Like",
-    "description": "The title for like button"
-  },
-  "theme.SearchModal.askAiScreen.dislikeButtonTitle": {
-    "message": "Dislike",
-    "description": "The title for dislike button"
-  },
-  "theme.SearchModal.askAiScreen.thanksForFeedbackText": {
-    "message": "Thanks for your feedback!",
-    "description": "The text for thanks for feedback"
-  },
-  "theme.SearchModal.askAiScreen.preToolCallText": {
-    "message": "Searching...",
-    "description": "The text before tool call"
-  },
-  "theme.SearchModal.askAiScreen.duringToolCallText": {
-    "message": "Searching for ",
-    "description": "The text during tool call"
-  },
-  "theme.SearchModal.askAiScreen.afterToolCallText": {
-    "message": "Searched for",
-    "description": "The text after tool call"
-  },
-  "theme.SearchModal.footer.submitQuestionText": {
-    "message": "Submit question",
-    "description": "The submit question text for footer"
-  },
-  "theme.SearchModal.footer.backToSearchText": {
-    "message": "Back to search",
-    "description": "The back to search text for footer"
-  }
-}
diff --git a/i18n/en/docusaurus-plugin-content-blog/options.json b/i18n/en/docusaurus-plugin-content-blog/options.json
deleted file mode 100644
index 9aeb1f8757..0000000000
--- a/i18n/en/docusaurus-plugin-content-blog/options.json
+++ /dev/null
@@ -1,14 +0,0 @@
-{
-  "title": {
-    "message": "Meeting Notes",
-    "description": "The title for the blog used in SEO"
-  },
-  "description": {
-    "message": "Notes and recordings from the Soroban protocol & developers meetings",
-    "description": "The description for the blog used in SEO"
-  },
-  "sidebar.title": {
-    "message": "All meetings",
-    "description": "The label for the left sidebar"
-  }
-}
diff --git a/i18n/en/docusaurus-plugin-content-docs-ap/current.json b/i18n/en/docusaurus-plugin-content-docs-ap/current.json
deleted file mode 100644
index 93c37fc0b7..0000000000
--- a/i18n/en/docusaurus-plugin-content-docs-ap/current.json
+++ /dev/null
@@ -1,70 +0,0 @@
-{
-  "version.label": {
-    "message": "Next",
-    "description": "The label for version current"
-  },
-  "sidebar.anchor_platform.category.Anchor Platform": {
-    "message": "Anchor Platform",
-    "description": "The label for category Anchor Platform in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Admin Guide": {
-    "message": "Admin Guide",
-    "description": "The label for category Admin Guide in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Custody Services": {
-    "message": "Custody Services",
-    "description": "The label for category Custody Services in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Fireblocks": {
-    "message": "Fireblocks",
-    "description": "The label for category Fireblocks in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Event Handling": {
-    "message": "Event Handling",
-    "description": "The label for category Event Handling in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.API Reference": {
-    "message": "API Reference",
-    "description": "The label for category API Reference in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Platform Server": {
-    "message": "Platform Server",
-    "description": "The label for category Platform Server in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Transactions": {
-    "message": "Transactions",
-    "description": "The label for category Transactions in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.JSON-RPC API": {
-    "message": "JSON-RPC API",
-    "description": "The label for category JSON-RPC API in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Methods": {
-    "message": "Methods",
-    "description": "The label for category Methods in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Callbacks Server": {
-    "message": "Callbacks Server",
-    "description": "The label for category Callbacks Server in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Custody Server": {
-    "message": "Custody Server",
-    "description": "The label for category Custody Server in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.SEP Guides": {
-    "message": "SEP Guides",
-    "description": "The label for category SEP Guides in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Hosted Deposits and Withdrawals (SEP-24)": {
-    "message": "Hosted Deposits and Withdrawals (SEP-24)",
-    "description": "The label for category Hosted Deposits and Withdrawals (SEP-24) in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Programmatic Deposits and Withdrawals (SEP-6)": {
-    "message": "Programmatic Deposits and Withdrawals (SEP-6)",
-    "description": "The label for category Programmatic Deposits and Withdrawals (SEP-6) in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Cross-Border Payments (SEP-31)": {
-    "message": "Cross-Border Payments (SEP-31)",
-    "description": "The label for category Cross-Border Payments (SEP-31) in sidebar anchor_platform"
-  }
-}
diff --git a/i18n/en/docusaurus-plugin-content-docs-sdp/current.json b/i18n/en/docusaurus-plugin-content-docs-sdp/current.json
deleted file mode 100644
index b11c2f85a6..0000000000
--- a/i18n/en/docusaurus-plugin-content-docs-sdp/current.json
+++ /dev/null
@@ -1,342 +0,0 @@
-{
-  "version.label": {
-    "message": "Next",
-    "description": "The label for version current"
-  },
-  "sidebar.stellar_disbursement_platform.category.Stellar Disbursement Platform": {
-    "message": "Stellar Disbursement Platform",
-    "description": "The label for category Stellar Disbursement Platform in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin Guide": {
-    "message": "Admin Guide",
-    "description": "The label for category Admin Guide in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin Guide.link.generated-index.description": {
-    "message": "All you need to know about setting up, running, and using the Stellar Disbursement Platform.",
-    "description": "The generated-index page description for category Admin Guide in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.User Interface": {
-    "message": "User Interface",
-    "description": "The label for category User Interface in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Reference": {
-    "message": "API Reference",
-    "description": "The label for category API Reference in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Reference.link.generated-index.description": {
-    "message": "View all Stellar Disbursement Platform API information.",
-    "description": "The generated-index page description for category API Reference in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin (Tenant Management)": {
-    "message": "Admin (Tenant Management)",
-    "description": "The label for category Admin (Tenant Management) in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Authentication": {
-    "message": "Authentication",
-    "description": "The label for category Authentication in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Balances": {
-    "message": "Balances",
-    "description": "The label for category Balances in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Disbursements": {
-    "message": "Disbursements",
-    "description": "The label for category Disbursements in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Organization": {
-    "message": "Organization",
-    "description": "The label for category Organization in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Payments": {
-    "message": "Payments",
-    "description": "The label for category Payments in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Profile": {
-    "message": "Profile",
-    "description": "The label for category Profile in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Receivers": {
-    "message": "Receivers",
-    "description": "The label for category Receivers in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Registration": {
-    "message": "Registration",
-    "description": "The label for category Registration in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Statistics": {
-    "message": "Statistics",
-    "description": "The label for category Statistics in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Users": {
-    "message": "Users",
-    "description": "The label for category Users in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Exports": {
-    "message": "Exports",
-    "description": "The label for category Exports in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Wallets": {
-    "message": "Wallets",
-    "description": "The label for category Wallets in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Tenants": {
-    "message": "Get All Tenants",
-    "description": "The label for the doc item Get All Tenants in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-tenants"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Tenant": {
-    "message": "Create Tenant",
-    "description": "The label for the doc item Create Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Tenant": {
-    "message": "Retrieve a Tenant",
-    "description": "The label for the doc item Retrieve a Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Soft delete a Tenant": {
-    "message": "Soft delete a Tenant",
-    "description": "The label for the doc item Soft delete a Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/soft-delete-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Tenant": {
-    "message": "Update a Tenant",
-    "description": "The label for the doc item Update a Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Default Tenant": {
-    "message": "Default Tenant",
-    "description": "The label for the doc item Default Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/default-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Log In": {
-    "message": "Log In",
-    "description": "The label for the doc item Log In in sidebar stellar_disbursement_platform, linking to the doc api-reference/log-in"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Refresh Token": {
-    "message": "Refresh Token",
-    "description": "The label for the doc item Refresh Token in sidebar stellar_disbursement_platform, linking to the doc api-reference/refresh-token"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Provide Multi-Factor Authentication": {
-    "message": "Provide Multi-Factor Authentication",
-    "description": "The label for the doc item Provide Multi-Factor Authentication in sidebar stellar_disbursement_platform, linking to the doc api-reference/authenticate-mfa"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Forgot Password": {
-    "message": "Forgot Password",
-    "description": "The label for the doc item Forgot Password in sidebar stellar_disbursement_platform, linking to the doc api-reference/forgot-password"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Reset Rassword": {
-    "message": "Reset Rassword",
-    "description": "The label for the doc item Reset Rassword in sidebar stellar_disbursement_platform, linking to the doc api-reference/reset-password"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Organization (Circle) Balances": {
-    "message": "Get Organization (Circle) Balances",
-    "description": "The label for the doc item Get Organization (Circle) Balances in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-organization-circle-balances"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Disbursements": {
-    "message": "List All Disbursements",
-    "description": "The label for the doc item List All Disbursements in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-all-disbursements"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Disbursement": {
-    "message": "Create Disbursement",
-    "description": "The label for the doc item Create Disbursement in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Disbursement": {
-    "message": "Retrieve a Disbursement",
-    "description": "The label for the doc item Retrieve a Disbursement in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-a-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Deletes a Draft Disbursement": {
-    "message": "Deletes a Draft Disbursement",
-    "description": "The label for the doc item Deletes a Draft Disbursement in sidebar stellar_disbursement_platform, linking to the doc api-reference/delete-a-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Disbursement Receivers": {
-    "message": "List All Disbursement Receivers",
-    "description": "The label for the doc item List All Disbursement Receivers in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-all-disbursement-receivers"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Download Disbursement Instructions": {
-    "message": "Download Disbursement Instructions",
-    "description": "The label for the doc item Download Disbursement Instructions in sidebar stellar_disbursement_platform, linking to the doc api-reference/download-disbursement-instructions"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Upload Disbursement Instructions": {
-    "message": "Upload Disbursement Instructions",
-    "description": "The label for the doc item Upload Disbursement Instructions in sidebar stellar_disbursement_platform, linking to the doc api-reference/upload-disbursement-instructions"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Disbursement Status": {
-    "message": "Update a Disbursement Status",
-    "description": "The label for the doc item Update a Disbursement Status in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-a-disbursement-status"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Organization Info": {
-    "message": "Get Organization Info",
-    "description": "The label for the doc item Get Organization Info in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-organization-info"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Organization Profile": {
-    "message": "Update Organization Profile",
-    "description": "The label for the doc item Update Organization Profile in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-organization-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Organization Logo": {
-    "message": "Retrieve Organization Logo",
-    "description": "The label for the doc item Retrieve Organization Logo in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-organization-logo"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Circle Account Setup": {
-    "message": "Circle Account Setup",
-    "description": "The label for the doc item Circle Account Setup in sidebar stellar_disbursement_platform, linking to the doc api-reference/patch-organization-circle"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Assets": {
-    "message": "Get All Assets",
-    "description": "The label for the doc item Get All Assets in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-assets"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Asset": {
-    "message": "Create Asset",
-    "description": "The label for the doc item Create Asset in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-asset"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Delete Asset": {
-    "message": "Delete Asset",
-    "description": "The label for the doc item Delete Asset in sidebar stellar_disbursement_platform, linking to the doc api-reference/delete-asset"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Wallets": {
-    "message": "Get All Wallets",
-    "description": "The label for the doc item Get All Wallets in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-wallets"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Wallet": {
-    "message": "Update Wallet",
-    "description": "The label for the doc item Update Wallet in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-wallet"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Payments": {
-    "message": "List All Payments",
-    "description": "The label for the doc item List All Payments in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-all-payments"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Payment": {
-    "message": "Retrieve a Payment",
-    "description": "The label for the doc item Retrieve a Payment in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-a-payment"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Profile": {
-    "message": "Get Profile",
-    "description": "The label for the doc item Get Profile in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Profile": {
-    "message": "Update User Profile",
-    "description": "The label for the doc item Update User Profile in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-user-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Receivers": {
-    "message": "List All Receivers",
-    "description": "The label for the doc item List All Receivers in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-all-receivers"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Receiver": {
-    "message": "Retrieve a Receiver",
-    "description": "The label for the doc item Retrieve a Receiver in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-a-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Receiver": {
-    "message": "Update a Receiver",
-    "description": "The label for the doc item Update a Receiver in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Start Wallet Registration": {
-    "message": "Start Wallet Registration",
-    "description": "The label for the doc item Start Wallet Registration in sidebar stellar_disbursement_platform, linking to the doc api-reference/start-wallet-registration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Send One-Time Passcode": {
-    "message": "Send One-Time Passcode",
-    "description": "The label for the doc item Send One-Time Passcode in sidebar stellar_disbursement_platform, linking to the doc api-reference/send-one-time-passcode"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Verify Receiver Registration": {
-    "message": "Verify Receiver Registration",
-    "description": "The label for the doc item Verify Receiver Registration in sidebar stellar_disbursement_platform, linking to the doc api-reference/verify-receiver-registration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Stellar Info File": {
-    "message": "Retrieve Stellar Info File",
-    "description": "The label for the doc item Retrieve Stellar Info File in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-stellar-info-file"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Request Challenge Transaction": {
-    "message": "Request Challenge Transaction",
-    "description": "The label for the doc item Request Challenge Transaction in sidebar stellar_disbursement_platform, linking to the doc api-reference/request-challenge-transaction"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Provide Signed Challenge Transaction": {
-    "message": "Provide Signed Challenge Transaction",
-    "description": "The label for the doc item Provide Signed Challenge Transaction in sidebar stellar_disbursement_platform, linking to the doc api-reference/provide-signed-challenge-transaction"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Request Registration URL": {
-    "message": "Request Registration URL",
-    "description": "The label for the doc item Request Registration URL in sidebar stellar_disbursement_platform, linking to the doc api-reference/request-registration-url"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve All Statistics": {
-    "message": "Retrieve All Statistics",
-    "description": "The label for the doc item Retrieve All Statistics in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-all-statistics"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Disbursement Statistics": {
-    "message": "Retrieve Disbursement Statistics",
-    "description": "The label for the doc item Retrieve Disbursement Statistics in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-disbursement-statistics"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Users": {
-    "message": "Get All Users",
-    "description": "The label for the doc item Get All Users in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-users"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create User": {
-    "message": "Create User",
-    "description": "The label for the doc item Create User in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-user"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Activation Status": {
-    "message": "Update User Activation Status",
-    "description": "The label for the doc item Update User Activation Status in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-user-activation-status"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Roles": {
-    "message": "Get All Roles",
-    "description": "The label for the doc item Get All Roles in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-roles"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Role": {
-    "message": "Update User Role",
-    "description": "The label for the doc item Update User Role in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-user-role"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Disbursements": {
-    "message": "Export Disbursements",
-    "description": "The label for the doc item Export Disbursements in sidebar stellar_disbursement_platform, linking to the doc api-reference/export-disbursements"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Payments": {
-    "message": "Export Payments",
-    "description": "The label for the doc item Export Payments in sidebar stellar_disbursement_platform, linking to the doc api-reference/export-payments-csv"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Receivers": {
-    "message": "Export Receivers",
-    "description": "The label for the doc item Export Receivers in sidebar stellar_disbursement_platform, linking to the doc api-reference/export-receivers-csv"
-  },
-  "sidebar.stellar_disbursement_platform.category.Bridge Integration": {
-    "message": "Bridge Integration",
-    "description": "The label for category Bridge Integration in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Bridge Integration Status": {
-    "message": "Get Bridge Integration Status",
-    "description": "The label for the doc item Get Bridge Integration Status in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-bridge-integration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Bridge Integration Status": {
-    "message": "Update Bridge Integration Status",
-    "description": "The label for the doc item Update Bridge Integration Status in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-bridge-integration"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Keys": {
-    "message": "API Keys",
-    "description": "The label for category API Keys in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List API Keys": {
-    "message": "List API Keys",
-    "description": "The label for the doc item List API Keys in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-api-keys"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create API Key": {
-    "message": "Create API Key",
-    "description": "The label for the doc item Create API Key in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get API Key Details": {
-    "message": "Get API Key Details",
-    "description": "The label for the doc item Get API Key Details in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update API Key": {
-    "message": "Update API Key",
-    "description": "The label for the doc item Update API Key in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Delete API Key": {
-    "message": "Delete API Key",
-    "description": "The label for the doc item Delete API Key in sidebar stellar_disbursement_platform, linking to the doc api-reference/delete-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Wallet": {
-    "message": "Create Wallet",
-    "description": "The label for the doc item Create Wallet in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-wallet"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Direct Payment": {
-    "message": "Create Direct Payment",
-    "description": "The label for the doc item Create Direct Payment in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-direct-payment"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Receiver": {
-    "message": "Create Receiver",
-    "description": "The label for the doc item Create Receiver in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-receiver"
-  }
-}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current.json b/i18n/en/docusaurus-plugin-content-docs/current.json
deleted file mode 100644
index aef4377bc3..0000000000
--- a/i18n/en/docusaurus-plugin-content-docs/current.json
+++ /dev/null
@@ -1,1014 +0,0 @@
-{
-  "version.label": {
-    "message": "Next",
-    "description": "The label for version current"
-  },
-  "sidebar.build.category.Build Smart Contracts": {
-    "message": "Build Smart Contracts",
-    "description": "The label for category 'Build Smart Contracts' in sidebar 'build'"
-  },
-  "sidebar.build.category.Getting Started": {
-    "message": "Getting Started",
-    "description": "The label for category 'Getting Started' in sidebar 'build'"
-  },
-  "sidebar.build.category.Example Contracts": {
-    "message": "Example Contracts",
-    "description": "The label for category 'Example Contracts' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build Applications": {
-    "message": "Build Applications",
-    "description": "The label for category 'Build Applications' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build a Wallet with the Wallet SDK": {
-    "message": "Build a Wallet with the Wallet SDK",
-    "description": "The label for category 'Build a Wallet with the Wallet SDK' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build a Payment App with the JS SDK": {
-    "message": "Build a Payment App with the JS SDK",
-    "description": "The label for category 'Build a Payment App with the JS SDK' in sidebar 'build'"
-  },
-  "sidebar.build.category.Anchor Integration": {
-    "message": "Anchor Integration",
-    "description": "The label for category 'Anchor Integration' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build Custom Network Ingestion Pipeline": {
-    "message": "Build Custom Network Ingestion Pipeline",
-    "description": "The label for category 'Build Custom Network Ingestion Pipeline' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build a Passkey Powered Guestbook Dapp": {
-    "message": "Build a Passkey Powered Guestbook Dapp",
-    "description": "The label for category 'Build a Passkey Powered Guestbook Dapp' in sidebar 'build'"
-  },
-  "sidebar.build.category.How-To Guides": {
-    "message": "How-To Guides",
-    "description": "The label for category 'How-To Guides' in sidebar 'build'"
-  },
-  "sidebar.build.category.Contract Conventions": {
-    "message": "Contract Conventions",
-    "description": "The label for category 'Contract Conventions' in sidebar 'build'"
-  },
-  "sidebar.build.category.Contract Events": {
-    "message": "Contract Events",
-    "description": "The label for category 'Contract Events' in sidebar 'build'"
-  },
-  "sidebar.build.category.Contract Storage": {
-    "message": "Contract Storage",
-    "description": "The label for category 'Contract Storage' in sidebar 'build'"
-  },
-  "sidebar.build.category.Contract Testing": {
-    "message": "Contract Testing",
-    "description": "The label for category 'Contract Testing' in sidebar 'build'"
-  },
-  "sidebar.build.category.Dapp Development": {
-    "message": "Dapp Development",
-    "description": "The label for category 'Dapp Development' in sidebar 'build'"
-  },
-  "sidebar.build.category.Fees & Metering": {
-    "message": "Fees & Metering",
-    "description": "The label for category 'Fees & Metering' in sidebar 'build'"
-  },
-  "sidebar.build.category.Freighter Wallet": {
-    "message": "Freighter Wallet",
-    "description": "The label for category 'Freighter Wallet' in sidebar 'build'"
-  },
-  "sidebar.build.category.Stellar Basics": {
-    "message": "Stellar Basics",
-    "description": "The label for category 'Stellar Basics' in sidebar 'build'"
-  },
-  "sidebar.build.category.RPC": {
-    "message": "RPC",
-    "description": "The label for category 'RPC' in sidebar 'build'"
-  },
-  "sidebar.build.category.State Archival": {
-    "message": "State Archival",
-    "description": "The label for category 'State Archival' in sidebar 'build'"
-  },
-  "sidebar.build.category.Stellar Asset Contract (SAC) Tokens": {
-    "message": "Stellar Asset Contract (SAC) Tokens",
-    "description": "The label for category 'Stellar Asset Contract (SAC) Tokens' in sidebar 'build'"
-  },
-  "sidebar.build.category.Transactions": {
-    "message": "Transactions",
-    "description": "The label for category 'Transactions' in sidebar 'build'"
-  },
-  "sidebar.build.category.Type Conversions": {
-    "message": "Type Conversions",
-    "description": "The label for category 'Type Conversions' in sidebar 'build'"
-  },
-  "sidebar.build.category.Security Best Practices": {
-    "message": "Security Best Practices",
-    "description": "The label for category 'Security Best Practices' in sidebar 'build'"
-  },
-  "sidebar.build.category.Threat Modeling": {
-    "message": "Threat Modeling",
-    "description": "The label for category 'Threat Modeling' in sidebar 'build'"
-  },
-  "sidebar.learn.category.Core Concepts": {
-    "message": "Core Concepts",
-    "description": "The label for category 'Core Concepts' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Stellar Data Structures": {
-    "message": "Stellar Data Structures",
-    "description": "The label for category 'Stellar Data Structures' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Operations & Transactions": {
-    "message": "Operations & Transactions",
-    "description": "The label for category 'Operations & Transactions' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Smart Contracts": {
-    "message": "Smart Contracts",
-    "description": "The label for category 'Smart Contracts' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Contract Interactions": {
-    "message": "Contract Interactions",
-    "description": "The label for category 'Contract Interactions' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Types": {
-    "message": "Types",
-    "description": "The label for category 'Types' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Storage": {
-    "message": "Storage",
-    "description": "The label for category 'Storage' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Errors and Debugging": {
-    "message": "Errors and Debugging",
-    "description": "The label for category 'Errors and Debugging' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Data Format": {
-    "message": "Data Format",
-    "description": "The label for category 'Data Format' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Migrate from Another Chain": {
-    "message": "Migrate from Another Chain",
-    "description": "The label for category 'Migrate from Another Chain' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.EVM Networks": {
-    "message": "EVM Networks",
-    "description": "The label for category 'EVM Networks' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Interactive Learning": {
-    "message": "Interactive Learning",
-    "description": "The label for category 'Interactive Learning' in sidebar 'learn'"
-  },
-  "sidebar.data_overview.category.Analytics": {
-    "message": "Analytics",
-    "description": "The label for category 'Analytics' in sidebar 'data_overview'"
-  },
-  "sidebar.data_overview.category.APIs": {
-    "message": "APIs",
-    "description": "The label for category 'APIs' in sidebar 'data_overview'"
-  },
-  "sidebar.data_overview.category.Indexers": {
-    "message": "Indexers",
-    "description": "The label for category 'Indexers' in sidebar 'data_overview'"
-  },
-  "sidebar.data_overview.category.Oracles": {
-    "message": "Oracles",
-    "description": "The label for category 'Oracles' in sidebar 'data_overview'"
-  },
-  "sidebar.data_overview.doc.Hubble": {
-    "message": "Hubble",
-    "description": "The label for the doc item 'Hubble' in sidebar 'data_overview', linking to the doc data/analytics/hubble/README"
-  },
-  "sidebar.data_overview.doc.Data Analytics Providers": {
-    "message": "Data Analytics Providers",
-    "description": "The label for the doc item 'Data Analytics Providers' in sidebar 'data_overview', linking to the doc data/analytics/analytics-providers/analytics-providers"
-  },
-  "sidebar.data_overview.doc.RPC": {
-    "message": "RPC",
-    "description": "The label for the doc item 'RPC' in sidebar 'data_overview', linking to the doc data/apis/rpc/README"
-  },
-  "sidebar.data_overview.doc.Horizon": {
-    "message": "Horizon",
-    "description": "The label for the doc item 'Horizon' in sidebar 'data_overview', linking to the doc data/apis/horizon/README"
-  },
-  "sidebar.data_overview.doc.Migrate Horizon to RPC": {
-    "message": "Migrate Horizon to RPC",
-    "description": "The label for the doc item 'Migrate Horizon to RPC' in sidebar 'data_overview', linking to the doc data/apis/migrate-from-horizon-to-rpc"
-  },
-  "sidebar.data_overview.doc.Build Your Own Indexer": {
-    "message": "Build Your Own Indexer",
-    "description": "The label for the doc item 'Build Your Own Indexer' in sidebar 'data_overview', linking to the doc data/indexers/build-your-own/README"
-  },
-  "sidebar.data_overview.doc.Indexer Providers": {
-    "message": "Indexer Providers",
-    "description": "The label for the doc item 'Indexer Providers' in sidebar 'data_overview', linking to the doc data/indexers/indexer-providers/indexer-providers"
-  },
-  "sidebar.data_overview.doc.Oracle Providers": {
-    "message": "Oracle Providers",
-    "description": "The label for the doc item 'Oracle Providers' in sidebar 'data_overview', linking to the doc data/oracles/oracle-providers"
-  },
-  "sidebar.tools.category.SDKs": {
-    "message": "SDKs",
-    "description": "The label for category 'SDKs' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Stellar CLI": {
-    "message": "Stellar CLI",
-    "description": "The label for category 'Stellar CLI' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Lab": {
-    "message": "Lab",
-    "description": "The label for category 'Lab' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.API Explorer": {
-    "message": "API Explorer",
-    "description": "The label for category 'API Explorer' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Quickstart": {
-    "message": "Quickstart",
-    "description": "The label for category 'Quickstart' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Getting Started": {
-    "message": "Getting Started",
-    "description": "The label for category 'Getting Started' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Debugging": {
-    "message": "Debugging",
-    "description": "The label for category 'Debugging' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Cloud Deployment": {
-    "message": "Cloud Deployment",
-    "description": "The label for category 'Cloud Deployment' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Advanced Usage": {
-    "message": "Advanced Usage",
-    "description": "The label for category 'Advanced Usage' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.More Developer Tools": {
-    "message": "More Developer Tools",
-    "description": "The label for category 'More Developer Tools' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Ramps": {
-    "message": "Ramps",
-    "description": "The label for category 'Ramps' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Infrastructure Tools": {
-    "message": "Infrastructure Tools",
-    "description": "The label for category 'Infrastructure Tools' in sidebar 'tools'"
-  },
-  "sidebar.tools.link.Anchor Platform": {
-    "message": "Anchor Platform",
-    "description": "The label for link 'Anchor Platform' in sidebar 'tools', linking to '/docs/platforms/anchor-platform'"
-  },
-  "sidebar.tools.link.Stellar Disbursement Platform": {
-    "message": "Stellar Disbursement Platform",
-    "description": "The label for link 'Stellar Disbursement Platform' in sidebar 'tools', linking to '/docs/platforms/stellar-disbursement-platform'"
-  },
-  "sidebar.validators.category.Admin Guide": {
-    "message": "Admin Guide",
-    "description": "The label for category 'Admin Guide' in sidebar 'validators'"
-  },
-  "sidebar.hubble.category.Hubble": {
-    "message": "Hubble",
-    "description": "The label for category 'Hubble' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Analyst Guide": {
-    "message": "Analyst Guide",
-    "description": "The label for category 'Analyst Guide' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Developer Guide": {
-    "message": "Developer Guide",
-    "description": "The label for category 'Developer Guide' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Backfill": {
-    "message": "Backfill",
-    "description": "The label for category 'Backfill' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Source System Ingestion": {
-    "message": "Source System Ingestion",
-    "description": "The label for category 'Source System Ingestion' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Data Curation": {
-    "message": "Data Curation",
-    "description": "The label for category 'Data Curation' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Visualization": {
-    "message": "Visualization",
-    "description": "The label for category 'Visualization' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Scheduling and Orchestration": {
-    "message": "Scheduling and Orchestration",
-    "description": "The label for category 'Scheduling and Orchestration' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Data Catalog": {
-    "message": "Data Catalog",
-    "description": "The label for category 'Data Catalog' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Data Dictionary": {
-    "message": "Data Dictionary",
-    "description": "The label for category 'Data Dictionary' in sidebar 'hubble'"
-  },
-  "sidebar.galexie.category.Galexie": {
-    "message": "Galexie",
-    "description": "The label for category 'Galexie' in sidebar 'galexie'"
-  },
-  "sidebar.galexie.category.Admin Guide": {
-    "message": "Admin Guide",
-    "description": "The label for category 'Admin Guide' in sidebar 'galexie'"
-  },
-  "sidebar.ingest.category.Ingest SDK": {
-    "message": "Ingest SDK",
-    "description": "The label for category 'Ingest SDK' in sidebar 'ingest'"
-  },
-  "sidebar.ingest.category.Developer Guide": {
-    "message": "Developer Guide",
-    "description": "The label for category 'Developer Guide' in sidebar 'ingest'"
-  },
-  "sidebar.ingest.category.Ledger Backends": {
-    "message": "Ledger Backends",
-    "description": "The label for category 'Ledger Backends' in sidebar 'ingest'"
-  },
-  "sidebar.soroban_rpc.category.Stellar RPC": {
-    "message": "Stellar RPC",
-    "description": "The label for category 'Stellar RPC' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.soroban_rpc.category.Methods": {
-    "message": "Methods",
-    "description": "The label for category 'Methods' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.analytics.category.Analytics": {
-    "message": "Analytics",
-    "description": "The label for category 'Analytics' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Hubble": {
-    "message": "Hubble",
-    "description": "The label for category 'Hubble' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Analyst Guide": {
-    "message": "Analyst Guide",
-    "description": "The label for category 'Analyst Guide' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Developer Guide": {
-    "message": "Developer Guide",
-    "description": "The label for category 'Developer Guide' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Backfill": {
-    "message": "Backfill",
-    "description": "The label for category 'Backfill' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Source System Ingestion": {
-    "message": "Source System Ingestion",
-    "description": "The label for category 'Source System Ingestion' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Data Curation": {
-    "message": "Data Curation",
-    "description": "The label for category 'Data Curation' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Visualization": {
-    "message": "Visualization",
-    "description": "The label for category 'Visualization' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Scheduling and Orchestration": {
-    "message": "Scheduling and Orchestration",
-    "description": "The label for category 'Scheduling and Orchestration' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Data Catalog": {
-    "message": "Data Catalog",
-    "description": "The label for category 'Data Catalog' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Data Dictionary": {
-    "message": "Data Dictionary",
-    "description": "The label for category 'Data Dictionary' in sidebar 'analytics'"
-  },
-  "sidebar.apis.category.APIs": {
-    "message": "APIs",
-    "description": "The label for category 'APIs' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.RPC": {
-    "message": "RPC",
-    "description": "The label for category 'RPC' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Methods": {
-    "message": "Methods",
-    "description": "The label for category 'Methods' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Horizon": {
-    "message": "Horizon",
-    "description": "The label for category 'Horizon' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Resources": {
-    "message": "Resources",
-    "description": "The label for category 'Resources' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Accounts": {
-    "message": "Accounts",
-    "description": "The label for category 'Accounts' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Assets": {
-    "message": "Assets",
-    "description": "The label for category 'Assets' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Claimable Balances": {
-    "message": "Claimable Balances",
-    "description": "The label for category 'Claimable Balances' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Effects": {
-    "message": "Effects",
-    "description": "The label for category 'Effects' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Ledgers": {
-    "message": "Ledgers",
-    "description": "The label for category 'Ledgers' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Liquidity Pools": {
-    "message": "Liquidity Pools",
-    "description": "The label for category 'Liquidity Pools' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Offers": {
-    "message": "Offers",
-    "description": "The label for category 'Offers' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Operations": {
-    "message": "Operations",
-    "description": "The label for category 'Operations' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.The Operation Object": {
-    "message": "The Operation Object",
-    "description": "The label for category 'The Operation Object' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Payments": {
-    "message": "Payments",
-    "description": "The label for category 'Payments' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Trades": {
-    "message": "Trades",
-    "description": "The label for category 'Trades' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Transactions": {
-    "message": "Transactions",
-    "description": "The label for category 'Transactions' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Pagination": {
-    "message": "Pagination",
-    "description": "The label for category 'Pagination' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Aggregations": {
-    "message": "Aggregations",
-    "description": "The label for category 'Aggregations' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Order Books": {
-    "message": "Order Books",
-    "description": "The label for category 'Order Books' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Paths": {
-    "message": "Paths",
-    "description": "The label for category 'Paths' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Trade Aggregations": {
-    "message": "Trade Aggregations",
-    "description": "The label for category 'Trade Aggregations' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Fee Stats": {
-    "message": "Fee Stats",
-    "description": "The label for category 'Fee Stats' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Errors": {
-    "message": "Errors",
-    "description": "The label for category 'Errors' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.HTTP Status Codes": {
-    "message": "HTTP Status Codes",
-    "description": "The label for category 'HTTP Status Codes' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Horizon-Specific Status Codes": {
-    "message": "Horizon-Specific Status Codes",
-    "description": "The label for category 'Horizon-Specific Status Codes' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Result Codes": {
-    "message": "Result Codes",
-    "description": "The label for category 'Result Codes' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Operation-Specific Result Codes": {
-    "message": "Operation-Specific Result Codes",
-    "description": "The label for category 'Operation-Specific Result Codes' in sidebar 'apis'"
-  },
-  "sidebar.indexers.category.Indexers": {
-    "message": "Indexers",
-    "description": "The label for category 'Indexers' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Build Your Own Indexer": {
-    "message": "Build Your Own Indexer",
-    "description": "The label for category 'Build Your Own Indexer' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Galexie": {
-    "message": "Galexie",
-    "description": "The label for category 'Galexie' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Admin Guide": {
-    "message": "Admin Guide",
-    "description": "The label for category 'Admin Guide' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Ingest SDK": {
-    "message": "Ingest SDK",
-    "description": "The label for category 'Ingest SDK' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Developer Guide": {
-    "message": "Developer Guide",
-    "description": "The label for category 'Developer Guide' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Ledger Backends": {
-    "message": "Ledger Backends",
-    "description": "The label for category 'Ledger Backends' in sidebar 'indexers'"
-  },
-  "sidebar.oracles.category.Oracles": {
-    "message": "Oracles",
-    "description": "The label for category 'Oracles' in sidebar 'oracles'"
-  },
-  "sidebar.build.category.Contract Authorization": {
-    "message": "Contract Authorization",
-    "description": "The label for category 'Contract Authorization' in sidebar 'build'"
-  },
-  "sidebar.tools.category.Smart Contracts": {
-    "message": "Smart Contracts",
-    "description": "The label for category 'Smart Contracts' in sidebar 'tools'"
-  },
-  "sidebar.indexers.category.Processors": {
-    "message": "Processors",
-    "description": "The label for category 'Processors' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Token Transfer Processor": {
-    "message": "Token Transfer Processor",
-    "description": "The label for category 'Token Transfer Processor' in sidebar 'indexers'"
-  },
-  "sidebar.tools.category.Cookbook": {
-    "message": "Cookbook",
-    "description": "The label for category 'Cookbook' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Saved": {
-    "message": "Saved",
-    "description": "The label for category 'Saved' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.View XDR": {
-    "message": "View XDR",
-    "description": "The label for category 'View XDR' in sidebar 'tools'"
-  },
-  "sidebar.hubble.category.Bronze 🥉": {
-    "message": "Bronze 🥉",
-    "description": "The label for category 'Bronze 🥉' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Silver 🥈": {
-    "message": "Silver 🥈",
-    "description": "The label for category 'Silver 🥈' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Gold 🥇": {
-    "message": "Gold 🥇",
-    "description": "The label for category 'Gold 🥇' in sidebar 'hubble'"
-  },
-  "sidebar.analytics.category.Bronze 🥉": {
-    "message": "Bronze 🥉",
-    "description": "The label for category 'Bronze 🥉' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Silver 🥈": {
-    "message": "Silver 🥈",
-    "description": "The label for category 'Silver 🥈' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Gold 🥇": {
-    "message": "Gold 🥇",
-    "description": "The label for category 'Gold 🥇' in sidebar 'analytics'"
-  },
-  "sidebar.galexie.category.galexie-example-usages": {
-    "message": "Example Usages",
-    "description": "The label for category 'Example Usages' in sidebar 'galexie'"
-  },
-  "sidebar.ingest.category.ingest-sdk-example-usages": {
-    "message": "Example Usages",
-    "description": "The label for category 'Example Usages' in sidebar 'ingest'"
-  },
-  "sidebar.soroban_rpc.category.rpc-admin-guide": {
-    "message": "Admin Guide",
-    "description": "The label for category 'Admin Guide' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.soroban_rpc.category.rpc-api-reference": {
-    "message": "API Reference",
-    "description": "The label for category 'API Reference' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.soroban_rpc.category.rpc-api-structure": {
-    "message": "Structure",
-    "description": "The label for category 'Structure' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.apis.category.rpc-admin-guide": {
-    "message": "Admin Guide",
-    "description": "The label for category 'Admin Guide' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.rpc-api-reference": {
-    "message": "API Reference",
-    "description": "The label for category 'API Reference' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.rpc-api-structure": {
-    "message": "Structure",
-    "description": "The label for category 'Structure' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.horizon-admin-guide": {
-    "message": "Admin Guide",
-    "description": "The label for category 'Admin Guide' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.horizon-api-reference": {
-    "message": "API Reference",
-    "description": "The label for category 'API Reference' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.horizon-api-structure": {
-    "message": "Structure",
-    "description": "The label for category 'Structure' in sidebar 'apis'"
-  },
-  "sidebar.indexers.category.galexie-example-usages": {
-    "message": "Example Usages",
-    "description": "The label for category 'Example Usages' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.ingest-sdk-example-usages": {
-    "message": "Example Usages",
-    "description": "The label for category 'Example Usages' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.token-transfer-processor-example-usages": {
-    "message": "Example Usages",
-    "description": "The label for category 'Example Usages' in sidebar 'indexers'"
-  },
-  "sidebar.anchor_platform.category.Anchor Platform": {
-    "message": "Anchor Platform",
-    "description": "The label for category 'Anchor Platform' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Admin Guide": {
-    "message": "Admin Guide",
-    "description": "The label for category 'Admin Guide' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Event Handling": {
-    "message": "Event Handling",
-    "description": "The label for category 'Event Handling' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.API Reference": {
-    "message": "API Reference",
-    "description": "The label for category 'API Reference' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Platform Server": {
-    "message": "Platform Server",
-    "description": "The label for category 'Platform Server' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Transactions": {
-    "message": "Transactions",
-    "description": "The label for category 'Transactions' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.JSON-RPC API": {
-    "message": "JSON-RPC API",
-    "description": "The label for category 'JSON-RPC API' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Methods": {
-    "message": "Methods",
-    "description": "The label for category 'Methods' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Callbacks Server": {
-    "message": "Callbacks Server",
-    "description": "The label for category 'Callbacks Server' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.SEP Guides": {
-    "message": "SEP Guides",
-    "description": "The label for category 'SEP Guides' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Programmatic Deposits and Withdrawals (SEP-6)": {
-    "message": "Programmatic Deposits and Withdrawals (SEP-6)",
-    "description": "The label for category 'Programmatic Deposits and Withdrawals (SEP-6)' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Hosted Deposits and Withdrawals (SEP-24)": {
-    "message": "Hosted Deposits and Withdrawals (SEP-24)",
-    "description": "The label for category 'Hosted Deposits and Withdrawals (SEP-24)' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Cross-Border Payments (SEP-31)": {
-    "message": "Cross-Border Payments (SEP-31)",
-    "description": "The label for category 'Cross-Border Payments (SEP-31)' in sidebar 'anchor_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Stellar Disbursement Platform": {
-    "message": "Stellar Disbursement Platform",
-    "description": "The label for category 'Stellar Disbursement Platform' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin Guide": {
-    "message": "Admin Guide",
-    "description": "The label for category 'Admin Guide' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin Guide.link.generated-index.description": {
-    "message": "All you need to know about setting up, running, and using the Stellar Disbursement Platform.",
-    "description": "The generated-index page description for category 'Admin Guide' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.User Interface": {
-    "message": "User Interface",
-    "description": "The label for category 'User Interface' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Reference": {
-    "message": "API Reference",
-    "description": "The label for category 'API Reference' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Reference.link.generated-index.description": {
-    "message": "View all Stellar Disbursement Platform API information.",
-    "description": "The generated-index page description for category 'API Reference' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin (Tenant Management)": {
-    "message": "Admin (Tenant Management)",
-    "description": "The label for category 'Admin (Tenant Management)' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Authentication": {
-    "message": "Authentication",
-    "description": "The label for category 'Authentication' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Keys": {
-    "message": "API Keys",
-    "description": "The label for category 'API Keys' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Balances": {
-    "message": "Balances",
-    "description": "The label for category 'Balances' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Bridge Integration": {
-    "message": "Bridge Integration",
-    "description": "The label for category 'Bridge Integration' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Disbursements": {
-    "message": "Disbursements",
-    "description": "The label for category 'Disbursements' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Organization": {
-    "message": "Organization",
-    "description": "The label for category 'Organization' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Payments": {
-    "message": "Payments",
-    "description": "The label for category 'Payments' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Profile": {
-    "message": "Profile",
-    "description": "The label for category 'Profile' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Receivers": {
-    "message": "Receivers",
-    "description": "The label for category 'Receivers' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Registration": {
-    "message": "Registration",
-    "description": "The label for category 'Registration' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Statistics": {
-    "message": "Statistics",
-    "description": "The label for category 'Statistics' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Users": {
-    "message": "Users",
-    "description": "The label for category 'Users' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Exports": {
-    "message": "Exports",
-    "description": "The label for category 'Exports' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Wallets": {
-    "message": "Wallets",
-    "description": "The label for category 'Wallets' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Tenants": {
-    "message": "Get All Tenants",
-    "description": "The label for the doc item 'Get All Tenants' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-tenants"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Tenant": {
-    "message": "Create Tenant",
-    "description": "The label for the doc item 'Create Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Tenant": {
-    "message": "Retrieve a Tenant",
-    "description": "The label for the doc item 'Retrieve a Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Soft delete a Tenant": {
-    "message": "Soft delete a Tenant",
-    "description": "The label for the doc item 'Soft delete a Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Tenant": {
-    "message": "Update a Tenant",
-    "description": "The label for the doc item 'Update a Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Default Tenant": {
-    "message": "Default Tenant",
-    "description": "The label for the doc item 'Default Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/default-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Log In": {
-    "message": "Log In",
-    "description": "The label for the doc item 'Log In' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/log-in"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Refresh Token": {
-    "message": "Refresh Token",
-    "description": "The label for the doc item 'Refresh Token' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/refresh-token"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Provide Multi-Factor Authentication": {
-    "message": "Provide Multi-Factor Authentication",
-    "description": "The label for the doc item 'Provide Multi-Factor Authentication' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/authenticate-mfa"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Forgot Password": {
-    "message": "Forgot Password",
-    "description": "The label for the doc item 'Forgot Password' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/forgot-password"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Reset Rassword": {
-    "message": "Reset Rassword",
-    "description": "The label for the doc item 'Reset Rassword' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/reset-password"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List API Keys": {
-    "message": "List API Keys",
-    "description": "The label for the doc item 'List API Keys' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-api-keys"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create API Key": {
-    "message": "Create API Key",
-    "description": "The label for the doc item 'Create API Key' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get API Key Details": {
-    "message": "Get API Key Details",
-    "description": "The label for the doc item 'Get API Key Details' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update API Key": {
-    "message": "Update API Key",
-    "description": "The label for the doc item 'Update API Key' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Delete API Key": {
-    "message": "Delete API Key",
-    "description": "The label for the doc item 'Delete API Key' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/delete-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Organization (Circle) Balances": {
-    "message": "Get Organization (Circle) Balances",
-    "description": "The label for the doc item 'Get Organization (Circle) Balances' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Bridge Integration Status": {
-    "message": "Get Bridge Integration Status",
-    "description": "The label for the doc item 'Get Bridge Integration Status' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-bridge-integration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Bridge Integration Status": {
-    "message": "Update Bridge Integration Status",
-    "description": "The label for the doc item 'Update Bridge Integration Status' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-bridge-integration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Disbursements": {
-    "message": "List All Disbursements",
-    "description": "The label for the doc item 'List All Disbursements' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-all-disbursements"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Disbursement": {
-    "message": "Create Disbursement",
-    "description": "The label for the doc item 'Create Disbursement' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Disbursement": {
-    "message": "Retrieve a Disbursement",
-    "description": "The label for the doc item 'Retrieve a Disbursement' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Deletes a Draft Disbursement": {
-    "message": "Deletes a Draft Disbursement",
-    "description": "The label for the doc item 'Deletes a Draft Disbursement' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Disbursement Receivers": {
-    "message": "List All Disbursement Receivers",
-    "description": "The label for the doc item 'List All Disbursement Receivers' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Download Disbursement Instructions": {
-    "message": "Download Disbursement Instructions",
-    "description": "The label for the doc item 'Download Disbursement Instructions' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Upload Disbursement Instructions": {
-    "message": "Upload Disbursement Instructions",
-    "description": "The label for the doc item 'Upload Disbursement Instructions' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Disbursement Status": {
-    "message": "Update a Disbursement Status",
-    "description": "The label for the doc item 'Update a Disbursement Status' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Organization Info": {
-    "message": "Get Organization Info",
-    "description": "The label for the doc item 'Get Organization Info' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-organization-info"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Organization Profile": {
-    "message": "Update Organization Profile",
-    "description": "The label for the doc item 'Update Organization Profile' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-organization-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Organization Logo": {
-    "message": "Retrieve Organization Logo",
-    "description": "The label for the doc item 'Retrieve Organization Logo' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-organization-logo"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Circle Account Setup": {
-    "message": "Circle Account Setup",
-    "description": "The label for the doc item 'Circle Account Setup' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/patch-organization-circle"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Assets": {
-    "message": "Get All Assets",
-    "description": "The label for the doc item 'Get All Assets' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-assets"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Asset": {
-    "message": "Create Asset",
-    "description": "The label for the doc item 'Create Asset' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-asset"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Delete Asset": {
-    "message": "Delete Asset",
-    "description": "The label for the doc item 'Delete Asset' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/delete-asset"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Payments": {
-    "message": "List All Payments",
-    "description": "The label for the doc item 'List All Payments' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-all-payments"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Direct Payment": {
-    "message": "Create Direct Payment",
-    "description": "The label for the doc item 'Create Direct Payment' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-direct-payment"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Payment": {
-    "message": "Retrieve a Payment",
-    "description": "The label for the doc item 'Retrieve a Payment' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Profile": {
-    "message": "Get Profile",
-    "description": "The label for the doc item 'Get Profile' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Profile": {
-    "message": "Update User Profile",
-    "description": "The label for the doc item 'Update User Profile' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-user-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Receivers": {
-    "message": "List All Receivers",
-    "description": "The label for the doc item 'List All Receivers' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-all-receivers"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Receiver": {
-    "message": "Create Receiver",
-    "description": "The label for the doc item 'Create Receiver' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Receiver": {
-    "message": "Retrieve a Receiver",
-    "description": "The label for the doc item 'Retrieve a Receiver' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Receiver": {
-    "message": "Update a Receiver",
-    "description": "The label for the doc item 'Update a Receiver' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Start Wallet Registration": {
-    "message": "Start Wallet Registration",
-    "description": "The label for the doc item 'Start Wallet Registration' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/start-wallet-registration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Send One-Time Passcode": {
-    "message": "Send One-Time Passcode",
-    "description": "The label for the doc item 'Send One-Time Passcode' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Verify Receiver Registration": {
-    "message": "Verify Receiver Registration",
-    "description": "The label for the doc item 'Verify Receiver Registration' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Stellar Info File": {
-    "message": "Retrieve Stellar Info File",
-    "description": "The label for the doc item 'Retrieve Stellar Info File' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Request Challenge Transaction": {
-    "message": "Request Challenge Transaction",
-    "description": "The label for the doc item 'Request Challenge Transaction' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Provide Signed Challenge Transaction": {
-    "message": "Provide Signed Challenge Transaction",
-    "description": "The label for the doc item 'Provide Signed Challenge Transaction' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Request Registration URL": {
-    "message": "Request Registration URL",
-    "description": "The label for the doc item 'Request Registration URL' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/request-registration-url"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve All Statistics": {
-    "message": "Retrieve All Statistics",
-    "description": "The label for the doc item 'Retrieve All Statistics' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Disbursement Statistics": {
-    "message": "Retrieve Disbursement Statistics",
-    "description": "The label for the doc item 'Retrieve Disbursement Statistics' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Users": {
-    "message": "Get All Users",
-    "description": "The label for the doc item 'Get All Users' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-users"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create User": {
-    "message": "Create User",
-    "description": "The label for the doc item 'Create User' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-user"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Activation Status": {
-    "message": "Update User Activation Status",
-    "description": "The label for the doc item 'Update User Activation Status' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-user-activation-status"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Roles": {
-    "message": "Get All Roles",
-    "description": "The label for the doc item 'Get All Roles' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-roles"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Role": {
-    "message": "Update User Role",
-    "description": "The label for the doc item 'Update User Role' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-user-role"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Disbursements": {
-    "message": "Export Disbursements",
-    "description": "The label for the doc item 'Export Disbursements' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/export-disbursements"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Payments": {
-    "message": "Export Payments",
-    "description": "The label for the doc item 'Export Payments' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/export-payments-csv"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Receivers": {
-    "message": "Export Receivers",
-    "description": "The label for the doc item 'Export Receivers' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/export-receivers-csv"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Wallets": {
-    "message": "Get All Wallets",
-    "description": "The label for the doc item 'Get All Wallets' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-wallets"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Wallet": {
-    "message": "Create Wallet",
-    "description": "The label for the doc item 'Create Wallet' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-wallet"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Wallet": {
-    "message": "Update Wallet",
-    "description": "The label for the doc item 'Update Wallet' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-wallet"
-  }
-}
diff --git a/i18n/en/docusaurus-theme-classic/footer.json b/i18n/en/docusaurus-theme-classic/footer.json
deleted file mode 100644
index b7831aa765..0000000000
--- a/i18n/en/docusaurus-theme-classic/footer.json
+++ /dev/null
@@ -1,98 +0,0 @@
-{
-  "link.title.Resources": {
-    "message": "Resources",
-    "description": "The title of the footer links column with title=Resources in the footer"
-  },
-  "link.title.Tools": {
-    "message": "Tools",
-    "description": "The title of the footer links column with title=Tools in the footer"
-  },
-  "link.title.Community": {
-    "message": "Community",
-    "description": "The title of the footer links column with title=Community in the footer"
-  },
-  "link.title.About": {
-    "message": "About",
-    "description": "The title of the footer links column with title=About in the footer"
-  },
-  "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"
-  },
-  "link.item.label.Stellar Quest": {
-    "message": "Stellar Quest",
-    "description": "The label of footer link with label=Stellar Quest linking to https://quest.stellar.org/"
-  },
-  "link.item.label.Soroban Quest": {
-    "message": "Soroban Quest",
-    "description": "The label of footer link with label=Soroban Quest linking to https://fastcheapandoutofcontrol.com/tutorial"
-  },
-  "link.item.label.YouTube": {
-    "message": "YouTube",
-    "description": "The label of footer link with label=YouTube linking to https://www.youtube.com/@StellarDevelopmentFoundation"
-  },
-  "link.item.label.Twitch": {
-    "message": "Twitch",
-    "description": "The label of footer link with label=Twitch linking to https://m.twitch.tv/stellarorg/home"
-  },
-  "link.item.label.Explorer": {
-    "message": "Explorer",
-    "description": "The label of footer link with label=Explorer linking to https://stellar.expert"
-  },
-  "link.item.label.Lab": {
-    "message": "Lab",
-    "description": "The label of footer link with label=Lab linking to https://lab.stellar.org"
-  },
-  "link.item.label.Status": {
-    "message": "Status",
-    "description": "The label of footer link with label=Status linking to https://status.stellar.org/"
-  },
-  "link.item.label.Dashboard": {
-    "message": "Dashboard",
-    "description": "The label of footer link with label=Dashboard linking to https://dashboard.stellar.org/"
-  },
-  "link.item.label.All Tools": {
-    "message": "All Tools",
-    "description": "The label of footer link with label=All Tools linking to /docs/tools"
-  },
-  "link.item.label.Contribute to Docs": {
-    "message": "Contribute to Docs",
-    "description": "The label of footer link with label=Contribute to Docs linking to https://github.com/stellar/stellar-docs?tab=readme-ov-file#contributing"
-  },
-  "link.item.label.Developer Discord": {
-    "message": "Developer Discord",
-    "description": "The label of footer link with label=Developer Discord linking to https://discord.gg/stellardev"
-  },
-  "link.item.label.Developer Google Group": {
-    "message": "Developer Google Group",
-    "description": "The label of footer link with label=Developer Google Group linking to https://groups.google.com/g/stellar-dev"
-  },
-  "link.item.label.Stack Exchange": {
-    "message": "Stack Exchange",
-    "description": "The label of footer link with label=Stack Exchange linking to https://stellar.stackexchange.com/"
-  },
-  "link.item.label.Stellar Community Fund": {
-    "message": "Stellar Community Fund",
-    "description": "The label of footer link with label=Stellar Community Fund linking to https://communityfund.stellar.org/"
-  },
-  "link.item.label.About SDF": {
-    "message": "About SDF",
-    "description": "The label of footer link with label=About SDF linking to https://stellar.org/foundation"
-  },
-  "link.item.label.Careers": {
-    "message": "Careers",
-    "description": "The label of footer link with label=Careers linking to https://stellar.org/foundation/careers"
-  },
-  "link.item.label.Events": {
-    "message": "Events",
-    "description": "The label of footer link with label=Events linking to https://stellar.org/events"
-  },
-  "link.item.label.Grants & Funding": {
-    "message": "Grants & Funding",
-    "description": "The label of footer link with label=Grants & Funding linking to https://stellar.org/foundation/grants-and-funding"
-  },
-  "link.item.label.Developer Meetings": {
-    "message": "Developer Meetings",
-    "description": "The label of footer link with label=Developer Meetings linking to /meetings"
-  }
-}
diff --git a/i18n/en/docusaurus-theme-classic/navbar.json b/i18n/en/docusaurus-theme-classic/navbar.json
deleted file mode 100644
index fd3eac0c8d..0000000000
--- a/i18n/en/docusaurus-theme-classic/navbar.json
+++ /dev/null
@@ -1,314 +0,0 @@
-{
-  "item.label.Build": {
-    "message": "Build",
-    "description": "Navbar item with label Build"
-  },
-  "item.label.Learn": {
-    "message": "Learn",
-    "description": "Navbar item with label Learn"
-  },
-  "item.label.Tokens": {
-    "message": "Tokens",
-    "description": "Navbar item with label Tokens"
-  },
-  "item.label.Data": {
-    "message": "Data",
-    "description": "Navbar item with label Data"
-  },
-  "item.label.Tools": {
-    "message": "Tools",
-    "description": "Navbar item with label Tools"
-  },
-  "item.label.Networks": {
-    "message": "Networks",
-    "description": "Navbar item with label Networks"
-  },
-  "item.label.Validators": {
-    "message": "Validators",
-    "description": "Navbar item with label Validators"
-  },
-  "item.label.Overview": {
-    "message": "Overview",
-    "description": "Navbar item with label Overview"
-  },
-  "item.label.Introduction": {
-    "message": "Introduction",
-    "description": "Navbar item with label Introduction"
-  },
-  "item.label.Getting Started": {
-    "message": "Getting Started",
-    "description": "Navbar item with label Getting Started"
-  },
-  "item.label.Example Contracts": {
-    "message": "Example Contracts",
-    "description": "Navbar item with label Example Contracts"
-  },
-  "item.label.Application Design Considerations": {
-    "message": "Application Design Considerations",
-    "description": "Navbar item with label Application Design Considerations"
-  },
-  "item.label.Tutorial: Wallet SDK": {
-    "message": "Tutorial: Wallet SDK",
-    "description": "Navbar item with label Tutorial: Wallet SDK"
-  },
-  "item.label.Tutorial: Payment Application, JavaScript": {
-    "message": "Tutorial: Payment Application, JavaScript",
-    "description": "Navbar item with label Tutorial: Payment Application, JavaScript"
-  },
-  "item.label.Tutorial: Network Ingestion Pipeline": {
-    "message": "Tutorial: Network Ingestion Pipeline",
-    "description": "Navbar item with label Tutorial: Network Ingestion Pipeline"
-  },
-  "item.label.Tutorial: Passkey Dapp": {
-    "message": "Tutorial: Passkey Dapp",
-    "description": "Navbar item with label Tutorial: Passkey Dapp"
-  },
-  "item.label.Tutorial: Dapp Frontend": {
-    "message": "Tutorial: Dapp Frontend",
-    "description": "Navbar item with label Tutorial: Dapp Frontend"
-  },
-  "item.label.Smart Wallets": {
-    "message": "Smart Wallets",
-    "description": "Navbar item with label Smart Wallets"
-  },
-  "item.label.Contract Conventions": {
-    "message": "Contract Conventions",
-    "description": "Navbar item with label Contract Conventions"
-  },
-  "item.label.Contract Events": {
-    "message": "Contract Events",
-    "description": "Navbar item with label Contract Events"
-  },
-  "item.label.Contract Storage": {
-    "message": "Contract Storage",
-    "description": "Navbar item with label Contract Storage"
-  },
-  "item.label.Contract Testing": {
-    "message": "Contract Testing",
-    "description": "Navbar item with label Contract Testing"
-  },
-  "item.label.Dapp Development": {
-    "message": "Dapp Development",
-    "description": "Navbar item with label Dapp Development"
-  },
-  "item.label.Fees & Metering": {
-    "message": "Fees & Metering",
-    "description": "Navbar item with label Fees & Metering"
-  },
-  "item.label.Freighter Wallet": {
-    "message": "Freighter Wallet",
-    "description": "Navbar item with label Freighter Wallet"
-  },
-  "item.label.Stellar Basics": {
-    "message": "Stellar Basics",
-    "description": "Navbar item with label Stellar Basics"
-  },
-  "item.label.RPC": {
-    "message": "RPC",
-    "description": "Navbar item with label RPC"
-  },
-  "item.label.State Archival": {
-    "message": "State Archival",
-    "description": "Navbar item with label State Archival"
-  },
-  "item.label.Stellar Asset Contract Tokens": {
-    "message": "Stellar Asset Contract Tokens",
-    "description": "Navbar item with label Stellar Asset Contract Tokens"
-  },
-  "item.label.Transactions": {
-    "message": "Transactions",
-    "description": "Navbar item with label Transactions"
-  },
-  "item.label.Type Conversions": {
-    "message": "Type Conversions",
-    "description": "Navbar item with label Type Conversions"
-  },
-  "item.label.Stellar Stack": {
-    "message": "Stellar Stack",
-    "description": "Navbar item with label Stellar Stack"
-  },
-  "item.label.Lumens (XLM)": {
-    "message": "Lumens (XLM)",
-    "description": "Navbar item with label Lumens (XLM)"
-  },
-  "item.label.Stellar Consensus Protocol (SCP)": {
-    "message": "Stellar Consensus Protocol (SCP)",
-    "description": "Navbar item with label Stellar Consensus Protocol (SCP)"
-  },
-  "item.label.Data Structures": {
-    "message": "Data Structures",
-    "description": "Navbar item with label Data Structures"
-  },
-  "item.label.Operations & Transactions": {
-    "message": "Operations & Transactions",
-    "description": "Navbar item with label Operations & Transactions"
-  },
-  "item.label.Stellar Ecosystem Proposals (SEPs)": {
-    "message": "Stellar Ecosystem Proposals (SEPs)",
-    "description": "Navbar item with label Stellar Ecosystem Proposals (SEPs)"
-  },
-  "item.label.Smart Contracts": {
-    "message": "Smart Contracts",
-    "description": "Navbar item with label Smart Contracts"
-  },
-  "item.label.Data Format": {
-    "message": "Data Format",
-    "description": "Navbar item with label Data Format"
-  },
-  "item.label.Ramps (anchors)": {
-    "message": "Ramps (anchors)",
-    "description": "Navbar item with label Ramps (anchors)"
-  },
-  "item.label.Migrate from Another Chain": {
-    "message": "Migrate from Another Chain",
-    "description": "Navbar item with label Migrate from Another Chain"
-  },
-  "item.label.Interactive Learning": {
-    "message": "Interactive Learning",
-    "description": "Navbar item with label Interactive Learning"
-  },
-  "item.label.Stellar Assets & Contract Tokens": {
-    "message": "Stellar Assets & Contract Tokens",
-    "description": "Navbar item with label Stellar Assets & Contract Tokens"
-  },
-  "item.label.Assets Overview": {
-    "message": "Assets Overview",
-    "description": "Navbar item with label Assets Overview"
-  },
-  "item.label.Quickstart Guide": {
-    "message": "Quickstart Guide",
-    "description": "Navbar item with label Quickstart Guide"
-  },
-  "item.label.Asset Design Considerations": {
-    "message": "Asset Design Considerations",
-    "description": "Navbar item with label Asset Design Considerations"
-  },
-  "item.label.Stellar Asset Contract": {
-    "message": "Stellar Asset Contract",
-    "description": "Navbar item with label Stellar Asset Contract"
-  },
-  "item.label.Token Interface": {
-    "message": "Token Interface",
-    "description": "Navbar item with label Token Interface"
-  },
-  "item.label.Tutorial: Issue an Asset": {
-    "message": "Tutorial: Issue an Asset",
-    "description": "Navbar item with label Tutorial: Issue an Asset"
-  },
-  "item.label.Publish Asset Information": {
-    "message": "Publish Asset Information",
-    "description": "Navbar item with label Publish Asset Information"
-  },
-  "item.label.Hubble": {
-    "message": "Hubble",
-    "description": "Navbar item with label Hubble"
-  },
-  "item.label.Providers": {
-    "message": "Providers",
-    "description": "Navbar item with label Providers"
-  },
-  "item.label.Horizon": {
-    "message": "Horizon",
-    "description": "Navbar item with label Horizon"
-  },
-  "item.label.Migrate Horizon to RPC": {
-    "message": "Migrate Horizon to RPC",
-    "description": "Navbar item with label Migrate Horizon to RPC"
-  },
-  "item.label.Build Your Own": {
-    "message": "Build Your Own",
-    "description": "Navbar item with label Build Your Own"
-  },
-  "item.label.SDKs": {
-    "message": "SDKs",
-    "description": "Navbar item with label SDKs"
-  },
-  "item.label.Stellar CLI": {
-    "message": "Stellar CLI",
-    "description": "Navbar item with label Stellar CLI"
-  },
-  "item.label.Lab": {
-    "message": "Lab",
-    "description": "Navbar item with label Lab"
-  },
-  "item.label.Quickstart": {
-    "message": "Quickstart",
-    "description": "Navbar item with label Quickstart"
-  },
-  "item.label.More Developer Tools": {
-    "message": "More Developer Tools",
-    "description": "Navbar item with label More Developer Tools"
-  },
-  "item.label.MoneyGram Ramps": {
-    "message": "MoneyGram Ramps",
-    "description": "Navbar item with label MoneyGram Ramps"
-  },
-  "item.label.Cross-Chain": {
-    "message": "Cross-Chain",
-    "description": "Navbar item with label Cross-Chain"
-  },
-  "item.label.Anchor Platform": {
-    "message": "Anchor Platform",
-    "description": "Navbar item with label Anchor Platform"
-  },
-  "item.label.Stellar Disbursement Platform": {
-    "message": "Stellar Disbursement Platform",
-    "description": "Navbar item with label Stellar Disbursement Platform"
-  },
-  "item.label.Software Versions": {
-    "message": "Software Versions",
-    "description": "Navbar item with label Software Versions"
-  },
-  "item.label.Resource Limits & Fees": {
-    "message": "Resource Limits & Fees",
-    "description": "Navbar item with label Resource Limits & Fees"
-  },
-  "item.label.Validators Introduction": {
-    "message": "Validators Introduction",
-    "description": "Navbar item with label Validators Introduction"
-  },
-  "item.label.Admin Guide": {
-    "message": "Admin Guide",
-    "description": "Navbar item with label Admin Guide"
-  },
-  "item.label.Tier 1 Organizations": {
-    "message": "Tier 1 Organizations",
-    "description": "Navbar item with label Tier 1 Organizations"
-  },
-  "item.label.Contract Authorization": {
-    "message": "Contract Authorization",
-    "description": "Navbar item with label Contract Authorization"
-  },
-  "item.label.OpenZeppelin Relayer": {
-    "message": "OpenZeppelin Relayer",
-    "description": "Navbar item with label OpenZeppelin Relayer"
-  },
-  "item.label.OpenZeppelin Contracts": {
-    "message": "OpenZeppelin Contracts",
-    "description": "Navbar item with label OpenZeppelin Contracts"
-  },
-  "item.label.Tutorial: Payment Application, Swift": {
-    "message": "Tutorial: Payment Application, Swift",
-    "description": "Navbar item with label Tutorial: Payment Application, Swift"
-  },
-  "item.label.SDEX": {
-    "message": "SDEX",
-    "description": "Navbar item with label SDEX"
-  },
-  "item.label.RPC Providers": {
-    "message": "RPC Providers",
-    "description": "Navbar item with label RPC Providers"
-  },
-  "item.label.Horizon Providers": {
-    "message": "Horizon Providers",
-    "description": "Navbar item with label Horizon Providers"
-  },
-  "item.label.Scaffold Stellar": {
-    "message": "Scaffold Stellar",
-    "description": "Navbar item with label Scaffold Stellar"
-  },
-  "item.label.Networks Overview": {
-    "message": "Networks Overview",
-    "description": "Navbar item with label Networks Overview"
-  }
-}
diff --git a/i18n/es/code.json b/i18n/es/code.json
deleted file mode 100644
index 3ea4f3842c..0000000000
--- a/i18n/es/code.json
+++ /dev/null
@@ -1,748 +0,0 @@
-{
-  "components.CodeExample.NoLanguageTabTitle": {
-    "message": "Ejemplo",
-    "description": "The tab title for a code example where no programming language was specified"
-  },
-  "components.EndpointsTable.Endpoints": {
-    "message": "Puntos finales",
-    "description": "The default title for a table of API endpoints"
-  },
-  "components.CodeExample.MissingCodeExample": {
-    "message": "// Aún no hay un ejemplo de código para {language}",
-    "description": "In the Wallet-SDK code example component, this message will display when the selected programming language has no accompanying example"
-  },
-  "components.WalletGuideWarn.WorkInProgress": {
-    "message": "La documentación para este idioma está actualmente en progreso. Parte de la información puede no ser aplicable a este idioma, o puede faltar. Los ejemplos de código pueden estar incompletos.",
-    "description": "For the Wallets SDK, if a given programming language is incomplete, display an admonition warning the user"
-  },
-  "components.ExampleResponse.Example": {
-    "message": "Ejemplo",
-    "description": "The default title for a table of example API responses"
-  },
-  "components.ReaderFeedback.ThankYou": {
-    "message": "¡Gracias por tu comentario!",
-    "description": "Message to thank a reader for clicking a thumbsup/thumbdown button"
-  },
-  "components.ReaderFeedback.Prompt": {
-    "message": "¿Te fue útil esta página?",
-    "description": "A prompt to invite the reader to click a thumbsup/thumbsdown button"
-  },
-  "theme.NotFound.title": {
-    "message": "Página no encontrada",
-    "description": "The title of the 404 page"
-  },
-  "components.AttributeTable.ListItem.ShowChildAttributes": {
-    "message": "Mostrar atributos secundarios",
-    "description": "For hand-written API schema pages, a message to tell readers they can expand a section to see more sub-items"
-  },
-  "component.Homepage.DeveloperResources.Discord.Title": {
-    "message": "Discord de Desarrolladores de Stellar"
-  },
-  "component.Homepage.DeveloperResources.Discord.Description": {
-    "message": "Haz preguntas y relaciona con otros desarrolladores de Stellar.",
-    "description": "Long description of what kind of developer resource this is."
-  },
-  "component.Homepage.DeveloperResources.DeveloperSite.Title": {
-    "message": "Sitio del Desarrollador"
-  },
-  "component.Homepage.DeveloperResources.DeveloperSite.Description": {
-    "message": "Obtén las últimas noticias y percepciones sobre cómo desarrollar en Stellar.",
-    "description": "Long description of what kind of developer resource this is."
-  },
-  "component.Homepage.DeveloperResources.StackExchange.Title": {
-    "message": "Intercambio Stellar Stack"
-  },
-  "component.Homepage.DeveloperResources.StackExchange.Description": {
-    "message": "Un sitio de preguntas y respuestas para desarrolladores de Stellar; si no encuentras lo que buscas en la documentación, intenta buscar en el Stack Exchange para ver si tu pregunta ha sido abordada. Si no lo ha sido, ¡siéntete libre de preguntar!",
-    "description": "Long description of what kind of developer resource this is."
-  },
-  "component.Homepage.DeveloperResources.GoogleGroup.Title": {
-    "message": "Grupo de Google de Desarrolladores de Stellar"
-  },
-  "component.Homepage.DeveloperResources.GoogleGroup.Description": {
-    "message": "Discute Propuestas de Avance del Núcleo (CAPs) y Propuestas del Ecosistema Stellar (SEPs), habla sobre el desarrollo del Núcleo Stellar y Horizon, y mantente informado acerca de las actualizaciones importantes de la red.",
-    "description": "Long description of what kind of developer resource this is."
-  },
-  "component.Homepage.DocsContribution.Heading": {
-    "message": "Contribuye a la documentación y deja comentarios"
-  },
-  "component.Homepage.DocsContribution.Paragraph1": {
-    "message": "La Documentación para Desarrolladores de Stellar es open-source, y se fomentan las contribuciones a la documentación. Puedes presentar una incidencia o pull request para agregar nuevo contenido, sugerir revisiones al contenido existente, enviar sugerencias, reportar errores, y más en el {githubRepoLink}."
-  },
-  "component.Homepage.DocsContribution.DocsGithubLink": {
-    "message": "Repositorio de GitHub de Stellar Docs",
-    "description": "Label for the link to the Stellar docs repository on Github"
-  },
-  "component.Homepage.DocsContribution.Paragraph2": {
-    "message": "Además, siéntete libre de dejar cualquier comentario adicional reportando incidencias en los diversos {githubOrgLink}."
-  },
-  "component.Homepage.DocsContribution.StellarRepos": {
-    "message": "Repositorios de Stellar",
-    "description": "Label for the link to the Stellar organization profile on Github"
-  },
-  "component.Homepage.ExploreButton.Text": {
-    "message": "Explorar",
-    "description": "The text that will be displayed on the \"Explore\" buttons"
-  },
-  "component.Homepage.NavigatingTheDocs.Build.Title": {
-    "message": "Desarrollar"
-  },
-  "component.Homepage.NavigatingTheDocs.Build.Description": {
-    "message": "Contiene tutoriales y guías sobre cómo escribir contratos inteligentes, desarrollar aplicaciones, interactuar con la red y más.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Learn.Title": {
-    "message": "Aprender"
-  },
-  "component.Homepage.NavigatingTheDocs.Learn.Description": {
-    "message": "Encuentra aquí todo el contenido informativo y conceptual. Aprende sobre los fundamentos de Stellar como el funcionamiento de cuentas y transacciones, profundiza en la funcionalidad de cada operación, descubre cómo funcionan las tarifas y más.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Tokens.Title": {
-    "message": "Tokens"
-  },
-  "component.Homepage.NavigatingTheDocs.Tokens.Description": {
-    "message": "Información sobre cómo emitir activos en la red Stellar y crear tokens de contratos inteligentes personalizados.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Data.Title": {
-    "message": "Datos"
-  },
-  "component.Homepage.NavigatingTheDocs.Data.Description": {
-    "message": "Descubre varias opciones de disponibilidad de datos: RPC, Hubble, Horizon, Galexie y indexadores de datos.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Tools.Title": {
-    "message": "Herramientas"
-  },
-  "component.Homepage.NavigatingTheDocs.Tools.Description": {
-    "message": "Conoce todas las herramientas disponibles para desarrollar, interactuar o simplemente observar la red Stellar. Además, encuentra información sobre cómo usar la Anchor Platform o la Stellar Disbursement Platform.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Networks.Title": {
-    "message": "Redes"
-  },
-  "component.Homepage.NavigatingTheDocs.Networks.Description": {
-    "message": "Información sobre las redes desplegadas (Mainnet, Testnet y Futurenet), versiones de software actuales, limitaciones de recursos y tarifas.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.NavigatingTheDocs.Validators.Title": {
-    "message": "Validadores"
-  },
-  "component.Homepage.NavigatingTheDocs.Validators.Description": {
-    "message": "Todo lo que necesitas saber si quieres ejecutar, operar y mantener un nodo validador en el núcleo de la red Stellar.",
-    "description": "Long description of what kind of information this section of the docs."
-  },
-  "component.Homepage.LearnMoreButton.Text": {
-    "message": "Saber Más",
-    "description": "The text that will be displayed on the \"Learn More\" buttons"
-  },
-  "components.WayfindingBoxes.AssetIssuers.Title": {
-    "message": "Emisores de Activos"
-  },
-  "components.WayfindingBoxes.AssetIssuers.Description": {
-    "message": "Emite un activo o crea un token de contrato inteligente personalizado.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.SmartContractDevelopers.Title": {
-    "message": "Desarrolladores de Contratos Inteligentes"
-  },
-  "components.WayfindingBoxes.SmartContractDevelopers.Description": {
-    "message": "Escribe contratos inteligentes en la red Stellar.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.RampsAnchors.Title": {
-    "message": "Ramps (anclas)"
-  },
-  "components.WayfindingBoxes.RampsAnchors.Description": {
-    "message": "Aprende sobre y configura un anchor.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.Applications.Title": {
-    "message": "Aplicaciones"
-  },
-  "components.WayfindingBoxes.Applications.Description": {
-    "message": "Desarrolla una billetera tradicional, dapp, o lista activos de Stellar en un exchange.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.InfrastructureProviders.Title": {
-    "message": "Proveedores de Infraestructura"
-  },
-  "components.WayfindingBoxes.InfrastructureProviders.Description": {
-    "message": "Configura un servicio Horizon o RPC.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.WayfindingBoxes.Analytics.Title": {
-    "message": "Analíticas"
-  },
-  "components.WayfindingBoxes.Analytics.Description": {
-    "message": "Usa Hubble para realizar análisis sobre los datos de la red Stellar.",
-    "description": "Short, punchy description for this \"wayfinding box\" on the homepage."
-  },
-  "components.HowToGuides.GuidesInCategory": {
-    "message": "Guías en esta categoría:",
-    "description": "The h3 title do display the other related how-to guides"
-  },
-  "theme.NotFound.p1": {
-    "message": "No pudimos encontrar lo que buscabas.",
-    "description": "The first paragraph of the 404 page"
-  },
-  "theme.NotFound.p2": {
-    "message": "Por favor, contacta al propietario del sitio que te enlazó a la URL original y házle saber que su enlace está roto.",
-    "description": "The 2nd paragraph of the 404 page"
-  },
-  "theme.ErrorPageContent.title": {
-    "message": "Esta página ha fallado.",
-    "description": "The title of the fallback page when the page crashed"
-  },
-  "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "Desplazarse hacia arriba",
-    "description": "The ARIA label for the back to top button"
-  },
-  "theme.blog.archive.title": {
-    "message": "Archivo",
-    "description": "The page & hero title of the blog archive page"
-  },
-  "theme.blog.archive.description": {
-    "message": "Archivo",
-    "description": "The page & hero description of the blog archive page"
-  },
-  "theme.blog.paginator.navAriaLabel": {
-    "message": "Navegación de la lista de blog",
-    "description": "The ARIA label for the blog pagination"
-  },
-  "theme.blog.paginator.newerEntries": {
-    "message": "Entradas más recientes",
-    "description": "The label used to navigate to the newer blog posts page (previous page)"
-  },
-  "theme.blog.paginator.olderEntries": {
-    "message": "Entradas más antiguas",
-    "description": "The label used to navigate to the older blog posts page (next page)"
-  },
-  "theme.blog.post.paginator.navAriaLabel": {
-    "message": "Navegación de la página de publicaciones del blog",
-    "description": "The ARIA label for the blog posts pagination"
-  },
-  "theme.blog.post.paginator.newerPost": {
-    "message": "Entrada más reciente",
-    "description": "The blog post button label to navigate to the newer/previous post"
-  },
-  "theme.blog.post.paginator.olderPost": {
-    "message": "Entrada más antigua",
-    "description": "The blog post button label to navigate to the older/next post"
-  },
-  "theme.tags.tagsPageLink": {
-    "message": "Ver todas las etiquetas",
-    "description": "The label of the link targeting the tag list page"
-  },
-  "theme.colorToggle.ariaLabel": {
-    "message": "Cambiar entre modo oscuro y claro (actualmente {mode})",
-    "description": "The ARIA label for the color mode toggle"
-  },
-  "theme.colorToggle.ariaLabel.mode.dark": {
-    "message": "modo oscuro",
-    "description": "The name for the dark color mode"
-  },
-  "theme.colorToggle.ariaLabel.mode.light": {
-    "message": "modo claro",
-    "description": "The name for the light color mode"
-  },
-  "theme.docs.DocCard.categoryDescription.plurals": {
-    "message": "1 elemento|{count} elementos",
-    "description": "The default description for a category card in the generated index about how many items this category includes"
-  },
-  "theme.docs.breadcrumbs.navAriaLabel": {
-    "message": "Migas de pan",
-    "description": "The ARIA label for the breadcrumbs"
-  },
-  "theme.docs.paginator.navAriaLabel": {
-    "message": "Páginas de docs",
-    "description": "The ARIA label for the docs pagination"
-  },
-  "theme.docs.paginator.previous": {
-    "message": "Anterior",
-    "description": "The label used to navigate to the previous doc"
-  },
-  "theme.docs.paginator.next": {
-    "message": "Siguiente",
-    "description": "The label used to navigate to the next doc"
-  },
-  "theme.docs.tagDocListPageTitle.nDocsTagged": {
-    "message": "Una doc etiquetada|{count} docs etiquetados",
-    "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.tagDocListPageTitle": {
-    "message": "{nDocsTagged} con \"{tagName}\"",
-    "description": "The title of the page for a docs tag"
-  },
-  "theme.docs.versionBadge.label": {
-    "message": "Versión: {versionLabel}"
-  },
-  "theme.docs.versions.unreleasedVersionLabel": {
-    "message": "Esta es documentación no publicada para {siteTitle} {versionLabel}.",
-    "description": "The label used to tell the user that he's browsing an unreleased doc version"
-  },
-  "theme.docs.versions.unmaintainedVersionLabel": {
-    "message": "Esta es documentación para {siteTitle} {versionLabel}, que ya no se mantiene activamente.",
-    "description": "The label used to tell the user that he's browsing an unmaintained doc version"
-  },
-  "theme.docs.versions.latestVersionSuggestionLabel": {
-    "message": "Para documentación actualizada, consulta el {latestVersionLink} ({versionLabel}).",
-    "description": "The label used to tell the user to check the latest version"
-  },
-  "theme.docs.versions.latestVersionLinkLabel": {
-    "message": "versión más reciente",
-    "description": "The label used for the latest version suggestion link label"
-  },
-  "theme.common.editThisPage": {
-    "message": "Editar esta página",
-    "description": "The link label to edit the current page"
-  },
-  "theme.common.headingLinkTitle": {
-    "message": "Enlace directo a {heading}",
-    "description": "Title for link to heading"
-  },
-  "theme.lastUpdated.atDate": {
-    "message": " el {date}",
-    "description": "The words used to describe on which date a page has been last updated"
-  },
-  "theme.lastUpdated.byUser": {
-    "message": " por {user}",
-    "description": "The words used to describe by who the page has been last updated"
-  },
-  "theme.lastUpdated.lastUpdatedAtBy": {
-    "message": "Última actualización{atDate}{byUser}",
-    "description": "The sentence used to display when a page has been last updated, and by who"
-  },
-  "theme.navbar.mobileVersionsDropdown.label": {
-    "message": "Versiones",
-    "description": "The label for the navbar versions dropdown on mobile view"
-  },
-  "theme.tags.tagsListLabel": {
-    "message": "Etiquetas:",
-    "description": "The label alongside a tag list"
-  },
-  "theme.admonition.caution": {
-    "message": "advertencia",
-    "description": "The default label used for the Caution admonition (:::caution)"
-  },
-  "theme.admonition.danger": {
-    "message": "peligro",
-    "description": "The default label used for the Danger admonition (:::danger)"
-  },
-  "theme.admonition.info": {
-    "message": "información",
-    "description": "The default label used for the Info admonition (:::info)"
-  },
-  "theme.admonition.note": {
-    "message": "nota",
-    "description": "The default label used for the Note admonition (:::note)"
-  },
-  "theme.admonition.tip": {
-    "message": "consejo",
-    "description": "The default label used for the Tip admonition (:::tip)"
-  },
-  "theme.admonition.warning": {
-    "message": "advertencia",
-    "description": "The default label used for the Warning admonition (:::warning)"
-  },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "Cerrar",
-    "description": "The ARIA label for close button of announcement bar"
-  },
-  "theme.blog.sidebar.navAriaLabel": {
-    "message": "Navegación de publicaciones recientes del blog",
-    "description": "The ARIA label for recent posts in the blog sidebar"
-  },
-  "theme.CodeBlock.copied": {
-    "message": "Copiado",
-    "description": "The copied button label on code blocks"
-  },
-  "theme.CodeBlock.copyButtonAriaLabel": {
-    "message": "Copiar código al portapapeles",
-    "description": "The ARIA label for copy code blocks button"
-  },
-  "theme.CodeBlock.copy": {
-    "message": "Copiar",
-    "description": "The copy button label on code blocks"
-  },
-  "theme.CodeBlock.wordWrapToggle": {
-    "message": "Alternar ajuste de línea",
-    "description": "The title attribute for toggle word wrapping button of code block lines"
-  },
-  "theme.DocSidebarItem.expandCategoryAriaLabel": {
-    "message": "Expandir la categoría de la barra lateral '{label}'",
-    "description": "The ARIA label to expand the sidebar category"
-  },
-  "theme.DocSidebarItem.collapseCategoryAriaLabel": {
-    "message": "Colapsar la categoría de la barra lateral '{label}'",
-    "description": "The ARIA label to collapse the sidebar category"
-  },
-  "theme.NavBar.navAriaLabel": {
-    "message": "Principal",
-    "description": "The ARIA label for the main navigation"
-  },
-  "theme.TOCCollapsible.toggleButtonLabel": {
-    "message": "En esta página",
-    "description": "The label used by the button on the collapsible TOC component"
-  },
-  "theme.navbar.mobileLanguageDropdown.label": {
-    "message": "Idiomas",
-    "description": "The label for the mobile language switcher dropdown"
-  },
-  "theme.blog.post.readMore": {
-    "message": "Leer más",
-    "description": "The label used in blog post item excerpts to link to full blog posts"
-  },
-  "theme.blog.post.readMoreLabel": {
-    "message": "Lee más sobre {title}",
-    "description": "The ARIA label for the link to full blog posts from excerpts"
-  },
-  "theme.blog.post.readingTime.plurals": {
-    "message": "Una min de lectura|{readingTime} min de lectura",
-    "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.breadcrumbs.home": {
-    "message": "Página de inicio",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
-  "theme.docs.sidebar.collapseButtonTitle": {
-    "message": "Colapsar barra lateral",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.collapseButtonAriaLabel": {
-    "message": "Colapsar barra lateral",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.navAriaLabel": {
-    "message": "Barra lateral de docs",
-    "description": "The ARIA label for the sidebar navigation"
-  },
-  "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
-    "message": "Cerrar barra de navegación",
-    "description": "The ARIA label for close button of mobile sidebar"
-  },
-  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
-    "message": "← Regresar al menú principal",
-    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
-  },
-  "theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
-    "message": "Alternar barra de navegación",
-    "description": "The ARIA label for hamburger menu button of mobile navigation"
-  },
-  "theme.docs.sidebar.expandButtonTitle": {
-    "message": "Expandir barra lateral",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.docs.sidebar.expandButtonAriaLabel": {
-    "message": "Expandir barra lateral",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.SearchBar.seeAll": {
-    "message": "Ver todos los {count} resultados"
-  },
-  "theme.SearchPage.documentsFound.plurals": {
-    "message": "Un documento encontrado|{count} documentos encontrados",
-    "description": "Pluralized label for \"{count} documents found\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.SearchPage.existingResultsTitle": {
-    "message": "Resultados de búsqueda para \"{query}\"",
-    "description": "The search page title for non-empty query"
-  },
-  "theme.SearchPage.emptyResultsTitle": {
-    "message": "Buscar la documentación",
-    "description": "The search page title for empty query"
-  },
-  "theme.SearchPage.inputPlaceholder": {
-    "message": "Escribe tu búsqueda aquí",
-    "description": "The placeholder for search page input"
-  },
-  "theme.SearchPage.inputLabel": {
-    "message": "Buscar",
-    "description": "The ARIA label for search page input"
-  },
-  "theme.SearchPage.algoliaLabel": {
-    "message": "Buscar por Algolia",
-    "description": "The description label for Algolia mention"
-  },
-  "theme.SearchPage.noResultsText": {
-    "message": "No se encontraron resultados",
-    "description": "The paragraph for empty search result"
-  },
-  "theme.SearchPage.fetchingNewResults": {
-    "message": "Obteniendo nuevos resultados...",
-    "description": "The paragraph for fetching new search results"
-  },
-  "theme.SearchBar.label": {
-    "message": "Buscar",
-    "description": "The ARIA label and placeholder for search button"
-  },
-  "theme.SearchModal.searchBox.resetButtonTitle": {
-    "message": "Borrar la consulta",
-    "description": "The label and ARIA label for search box reset button"
-  },
-  "theme.SearchModal.searchBox.cancelButtonText": {
-    "message": "Cancelar",
-    "description": "The label and ARIA label for search box cancel button"
-  },
-  "theme.SearchModal.startScreen.recentSearchesTitle": {
-    "message": "Recientes",
-    "description": "The title for recent searches"
-  },
-  "theme.SearchModal.startScreen.noRecentSearchesText": {
-    "message": "Sin búsquedas recientes",
-    "description": "The text when there are no recent searches"
-  },
-  "theme.SearchModal.startScreen.saveRecentSearchButtonTitle": {
-    "message": "Guardar esta búsqueda",
-    "description": "The title for save recent search button"
-  },
-  "theme.SearchModal.startScreen.removeRecentSearchButtonTitle": {
-    "message": "Eliminar esta búsqueda del historial",
-    "description": "The title for remove recent search button"
-  },
-  "theme.SearchModal.startScreen.favoriteSearchesTitle": {
-    "message": "Favorito",
-    "description": "The title for favorite searches"
-  },
-  "theme.SearchModal.startScreen.removeFavoriteSearchButtonTitle": {
-    "message": "Eliminar esta búsqueda de favoritos",
-    "description": "The title for remove favorite search button"
-  },
-  "theme.SearchModal.errorScreen.titleText": {
-    "message": "No se pudieron obtener resultados",
-    "description": "The title for error screen"
-  },
-  "theme.SearchModal.errorScreen.helpText": {
-    "message": "Es posible que desees comprobar tu conexión de red.",
-    "description": "The help text for error screen"
-  },
-  "theme.SearchModal.footer.selectText": {
-    "message": "para seleccionar",
-    "description": "The select text for footer"
-  },
-  "theme.SearchModal.footer.selectKeyAriaLabel": {
-    "message": "Tecla Intro",
-    "description": "The ARIA label for select key in footer"
-  },
-  "theme.SearchModal.footer.navigateText": {
-    "message": "para navegar",
-    "description": "The navigate text for footer"
-  },
-  "theme.SearchModal.footer.navigateUpKeyAriaLabel": {
-    "message": "Tecla de flecha hacia arriba",
-    "description": "The ARIA label for navigate up key in footer"
-  },
-  "theme.SearchModal.footer.navigateDownKeyAriaLabel": {
-    "message": "Tecla de flecha hacia abajo",
-    "description": "The ARIA label for navigate down key in footer"
-  },
-  "theme.SearchModal.footer.closeText": {
-    "message": "para cerrar",
-    "description": "The close text for footer"
-  },
-  "theme.SearchModal.footer.closeKeyAriaLabel": {
-    "message": "Tecla Escape",
-    "description": "The ARIA label for close key in footer"
-  },
-  "theme.SearchModal.footer.searchByText": {
-    "message": "Buscar por",
-    "description": "The 'Powered by' text for footer"
-  },
-  "theme.SearchModal.noResultsScreen.noResultsText": {
-    "message": "Sin resultados para",
-    "description": "The text when there are no results"
-  },
-  "theme.SearchModal.noResultsScreen.suggestedQueryText": {
-    "message": "Intenta buscar",
-    "description": "The text for suggested query"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsText": {
-    "message": "¿Crees que esta consulta debería devolver resultados?",
-    "description": "The text for reporting missing results"
-  },
-  "theme.SearchModal.noResultsScreen.reportMissingResultsLinkText": {
-    "message": "Háznoslo saber.",
-    "description": "The link text for reporting missing results"
-  },
-  "theme.SearchModal.placeholder": {
-    "message": "Buscar docs",
-    "description": "The placeholder of the input of the DocSearch pop-up modal"
-  },
-  "theme.blog.post.plurals": {
-    "message": "Una publicación|{count} publicaciones",
-    "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.blog.tagTitle": {
-    "message": "{nPosts} etiquetadas con \"{tagName}\"",
-    "description": "The title of the page for a blog tag"
-  },
-  "theme.blog.author.pageTitle": {
-    "message": "{authorName} - {nPosts, plural, one {1 publicación} other {# publicaciones}}",
-    "description": "The title of the page for a blog author"
-  },
-  "theme.blog.authorsList.pageTitle": {
-    "message": "Autores",
-    "description": "The title of the authors page"
-  },
-  "theme.blog.authorsList.viewAll": {
-    "message": "Ver todos los autores",
-    "description": "The label of the link targeting the blog authors page"
-  },
-  "theme.blog.author.noPosts": {
-    "message": "Este autor no ha escrito ninguna entrada todavía.",
-    "description": "The text for authors with 0 blog post"
-  },
-  "theme.contentVisibility.unlistedBanner.title": {
-    "message": "Página no listada",
-    "description": "The unlisted content banner title"
-  },
-  "theme.contentVisibility.unlistedBanner.message": {
-    "message": "Esta página no está listada. Los motores de búsqueda no la indexarán, y solo los usuarios que tengan un enlace directo pueden acceder a ella.",
-    "description": "The unlisted content banner message"
-  },
-  "theme.contentVisibility.draftBanner.title": {
-    "message": "Página borrador",
-    "description": "The draft content banner title"
-  },
-  "theme.contentVisibility.draftBanner.message": {
-    "message": "Esta página es un borrador. Solo será visible en desarrollo y será excluida de la construcción de producción.",
-    "description": "The draft content banner message"
-  },
-  "theme.ErrorPageContent.tryAgain": {
-    "message": "Intenta de nuevo",
-    "description": "The label of the button to try again rendering when the React error boundary captures an error"
-  },
-  "theme.common.skipToMainContent": {
-    "message": "Saltar al contenido principal",
-    "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
-  },
-  "theme.tags.tagsPageTitle": {
-    "message": "Etiquetas",
-    "description": "The title of the tag list page"
-  },
-  "theme.colorToggle.ariaLabel.mode.system": {
-    "message": "modo del sistema",
-    "description": "The name for the system color mode"
-  },
-  "theme.navbar.mobileDropdown.collapseButton.expandAriaLabel": {
-    "message": "Expandir el menú desplegable",
-    "description": "The ARIA label of the button to expand the mobile dropdown navbar item"
-  },
-  "theme.navbar.mobileDropdown.collapseButton.collapseAriaLabel": {
-    "message": "Contraer el menú desplegable",
-    "description": "The ARIA label of the button to collapse the mobile dropdown navbar item"
-  },
-  "components.ReaderFeedback.ThumbsUp.Title": {
-    "message": "Me gusta",
-    "description": "The title value for the thumbsup icon"
-  },
-  "components.ReaderFeedback.ThumbsDown.Title": {
-    "message": "No me gusta",
-    "description": "The title value for the thumbsdown icon"
-  },
-  "theme.IconExternalLink.ariaLabel": {
-    "message": "(se abre en una nueva pestaña)",
-    "description": "The ARIA label for the external link icon"
-  },
-  "theme.SearchModal.searchBox.placeholderText": {
-    "message": "Buscar en la documentación",
-    "description": "The placeholder text for the main search input field"
-  },
-  "theme.SearchModal.searchBox.placeholderTextAskAi": {
-    "message": "Haz otra pregunta...",
-    "description": "The placeholder text when in AI question mode"
-  },
-  "theme.SearchModal.searchBox.placeholderTextAskAiStreaming": {
-    "message": "Respondiendo...",
-    "description": "The placeholder text for search box when AI is streaming an answer"
-  },
-  "theme.SearchModal.searchBox.enterKeyHint": {
-    "message": "buscar",
-    "description": "The hint for the search box enter key text"
-  },
-  "theme.SearchModal.searchBox.enterKeyHintAskAi": {
-    "message": "entrar",
-    "description": "The hint for the Ask AI search box enter key text"
-  },
-  "theme.SearchModal.searchBox.searchInputLabel": {
-    "message": "Buscar",
-    "description": "The ARIA label for search input"
-  },
-  "theme.SearchModal.searchBox.backToKeywordSearchButtonText": {
-    "message": "Volver a la búsqueda por palabra clave",
-    "description": "The text for back to keyword search button"
-  },
-  "theme.SearchModal.searchBox.backToKeywordSearchButtonAriaLabel": {
-    "message": "Volver a la búsqueda por palabra clave",
-    "description": "The ARIA label for back to keyword search button"
-  },
-  "theme.SearchModal.startScreen.recentConversationsTitle": {
-    "message": "Conversaciones recientes",
-    "description": "The title for recent conversations"
-  },
-  "theme.SearchModal.startScreen.removeRecentConversationButtonTitle": {
-    "message": "Eliminar esta conversación del historial",
-    "description": "The title for remove recent conversation button"
-  },
-  "theme.SearchModal.resultsScreen.askAiPlaceholder": {
-    "message": "Preguntar a AI: ",
-    "description": "The placeholder text for Ask AI input"
-  },
-  "theme.SearchModal.askAiScreen.disclaimerText": {
-    "message": "Las respuestas se generan con AI, que puede cometer errores. Verifica las respuestas.",
-    "description": "The disclaimer text for AI answers"
-  },
-  "theme.SearchModal.askAiScreen.relatedSourcesText": {
-    "message": "Fuentes relacionadas",
-    "description": "The text for related sources"
-  },
-  "theme.SearchModal.askAiScreen.thinkingText": {
-    "message": "Pensando...",
-    "description": "The text when AI is thinking"
-  },
-  "theme.SearchModal.askAiScreen.copyButtonText": {
-    "message": "Copiar",
-    "description": "The text for copy button"
-  },
-  "theme.SearchModal.askAiScreen.copyButtonCopiedText": {
-    "message": "¡Copiado!",
-    "description": "The text for copy button when copied"
-  },
-  "theme.SearchModal.askAiScreen.copyButtonTitle": {
-    "message": "Copiar",
-    "description": "The title for copy button"
-  },
-  "theme.SearchModal.askAiScreen.likeButtonTitle": {
-    "message": "Me gusta",
-    "description": "The title for like button"
-  },
-  "theme.SearchModal.askAiScreen.dislikeButtonTitle": {
-    "message": "No me gusta",
-    "description": "The title for dislike button"
-  },
-  "theme.SearchModal.askAiScreen.thanksForFeedbackText": {
-    "message": "¡Gracias por tus comentarios!",
-    "description": "The text for thanks for feedback"
-  },
-  "theme.SearchModal.askAiScreen.preToolCallText": {
-    "message": "Buscando...",
-    "description": "The text before tool call"
-  },
-  "theme.SearchModal.askAiScreen.duringToolCallText": {
-    "message": "Buscando ",
-    "description": "The text during tool call"
-  },
-  "theme.SearchModal.askAiScreen.afterToolCallText": {
-    "message": "Buscado por",
-    "description": "The text after tool call"
-  },
-  "theme.SearchModal.footer.submitQuestionText": {
-    "message": "Enviar pregunta",
-    "description": "The submit question text for footer"
-  },
-  "theme.SearchModal.footer.backToSearchText": {
-    "message": "Volver a la búsqueda",
-    "description": "The back to search text for footer"
-  }
-}
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-01-18.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-01-18.mdx
deleted file mode 100644
index 20e613c5d5..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-01-18.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: 2024-01-18
-authors: naman
-tags:
-  - protocol
----
-
-<audio controls>
-  <source
-    src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/0101802024_protocol_developer_call.mp3"
-    type="audio/mpeg"
-  ></source>
-  Tu navegador no admite el elemento de audio.
-</audio>
-
-[Hilo de agenda de Discord](https://discord.com/channels/897514728459468821/1196897067445010452)
-
-1. La necesidad de curvas de cifrado que habilitan zk como BLS12-381. [Hilo de Github](https://github.com/stellar/rs-soroban-env/issues/779).
-2. Los casos de uso en los que el ecosistema está interesado:
-   1. Excellar, es decir, personas que iniciaron esta conversación al enviar un [PR para BLS12-381](https://github.com/stellar/rs-soroban-env/pull/1310), quiere añadir un oráculo controlado por DAO donde la curva elíptica proporciona la capacidad de añadir nuevos votantes de DAO
-   2. Zkbricks quiere crear un sistema L2 que habilite el estado secreto para contratos inteligentes arbitrarios
-   3. Skyhitz quiere utilizar Stellar para computación eficiente, costo y escalabilidad mientras usa zk para probar la propiedad de activos de alto valor en otra cadena
-   4. La enumeración de casos de uso continúa en el [hilo de discord](https://discord.com/channels/897514728459468821/1197663875512942653).
-3. Consideraciones para la implementación de funciones de host
-   1. Los desarrolladores principales cuestionaron si BLS12-381 era la curva correcta y también destacaron la necesidad de determinar el nivel adecuado de abstracción dado que hay un compromiso entre flexibilidad y eficiencia. Un nivel inferior de abstracción permitirá más flexibilidad pero resultará en más bucles activos en el wasm, mientras que un nivel más alto de abstracción será altamente eficiente pero restringirá la generalidad.
-   2. ZkBricks pensó que hay una necesidad de exponer directamente combinaciones y operaciones de grupo sin ningún nivel de abstracción. El espacio está en desarrollo activo y se necesita flexibilidad para probar nuevos enfoques y sistemas de prueba. Desde el punto de vista de la agilidad criptográfica, sería bueno exponer una interfaz genérica que admita una variedad de curvas en el backend.
-4. Ruta a seguir
-   1. Los desarrolladores principales mencionaron que las curvas criptográficas pueden ser experimentadas localmente al vincular crates de Rust, lo cual, resulta que fallaron en el pasado. Esto será explorado y corregido.
-   2. ZkBricks y otros prototiparán localmente y proporcionarán retroalimentación.
-5. Cuáles son las prácticas recomendadas para gestionar transacciones en el frontend, con respecto al orden de transacciones.
-6. Los desarrolladores principales confirmaron que el orden es intencionalmente arbitrario.
-7. Solicitud de una API para la versión actual del entorno/sdk
-8. Problema de Github presentado para que el RPC devuelva versiones del nodo actual.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-01-26.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-01-26.mdx
deleted file mode 100644
index 38cb149017..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-01-26.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: 2024-01-26
-authors: kalepail
-tags:
-  - developer
----
-
-<audio controls>
-  <source
-    src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/Soroban-Dev-Call-01-26-24.mp3"
-    type="audio/mpeg"
-  ></source>
-  Tu navegador no admite el elemento de audio.
-</audio>
-
-[Hilo de agenda de Discord](https://discord.com/channels/897514728459468821/1199121845656486009)
-
-1. Planificar y programar estas reuniones
-   1. Reuniones de protocolo cada dos jueves a las 4pm ET
-   2. Reuniones de desarrollador cada dos viernes a la 1pm ET
-   3. Continuaremos ajustando según sea necesario
-2. Error de ajuste de tarifas - [anuncio](https://stellar.org/blog/developers/fee-bump-bug-disclosure) | [hilo de discusión](https://discord.com/channels/897514728459468821/1200432249594707998/1200432306314281000)
-   1. Error de patrocinio de tarifas: la tarifa no utilizada se reembolsa a la fuente de transacción interna en lugar de a la fuente del patrocinador.
-   2. Corregir en nueva versión. Depende del ecosistema y de los validadores actualizar. La corrección probablemente se implementará antes de la Fase 2.
-   3. Depende de los validadores decidir si quieren posponer la fecha de actualización v20 para esperar la corrección; o actualizar con la versión actual.
-3. Deprecación de TxMeta en Horizon - [anuncio](https://discord.com/channels/897514728459468821/900374272751591424/1199438109796999298)
-4. Ideas sobre pruebas contra imágenes de ledger - [solicitud](https://discord.com/channels/897514728459468821/1199121845656486009/1199158421254049912)
-   1. Definir las necesidades un poco más claramente
-   2. Definitivamente hay algo aquí que deberíamos abordar para facilitar las pruebas contra el estado del ledger específico
-5. ¿Cómo obtienes una lista de contratos inteligentes? - [hilo](https://discord.com/channels/897514728459468821/1199121845656486009/1199739331078803496)
-   1. Observar operaciones de creación de contratos a medida que los ledgers se cierran
-   2. Usa un [servicio de indexación](/docs/data/indexers)
-6. ¿Cuál es el estado del soporte de caché de contratos? - [pregunta](https://discord.com/channels/897514728459468821/1199121845656486009/1200484710447587490)
-   1. [respuesta](https://discord.com/channels/897514728459468821/1199121845656486009/1200516877680644276)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-02-01.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-02-01.mdx
deleted file mode 100644
index 59d504a616..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-02-01.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: 2024-02-01
-authors: naman
-tags:
-  - protocol
----
-
-<audio controls>
-  <source
-    src="https://pub-b2eaaee2bbe74d70820bacb7298958f5.r2.dev/Stellar-Protocol-Meeting-02-01-2024.mp3"
-    type="audio/mpeg"
-  ></source>
-  Your browser does not support the audio element.
-</audio>
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1201979721211203614)
-
-1. La propuesta es avanzar stellar-core añadiendo una función de host para verificar la firma secp256r1, que es la curva elíptica más común utilizada fuera del espacio blockchain. Es útil para conectar interfaces de autenticación off-chain con funcionalidad on-chain. Es útil en conectar interfaces de autenticación off-chain con funcionalidad on-chain.
-2. Nota que la propuesta no es para un nuevo tipo de firmante, sino para una función de host.
-3. Leigh investigó añadir la admisión para el caso de uso de WebAuthN, permitiendo a una cuenta / contrato inteligente personalizado firmar entradas de autenticación soroban usando una carga útil firmada por secp256r1.
-4. secp256r1 es admitido por teléfonos, claves de acceso, y permite que una app reemplace contraseñas. Este es un gran beneficio para aplicaciones orientadas al usuario como billeteras. Pros y contras de la interfaz: las blockchains generalmente implementan la interfaz de recuperación sobre la interfaz de verificación, pero la verificación es más fácil para los desarrolladores ya que reduce la carga en el cliente y la red.
-5. Pros and cons of the interface: blockchains generally implement the recovery interface over the verification interface but verification is easier for developers as it reduces burden on the client and the network.
-6. Si bien hay formas ingeniosas de lograr lo último, no es una gran experiencia para el desarrollador y la implementación final es susceptible a fallos en actualizaciones.
-7. También es costoso agrupar la decodificación con la verificación en guest.
-8. Soroban siempre ha liderado con una mentalidad de que todo viene incluido. Manteniéndose en línea con ese enfoque, tiene sentido investigar más y determinar si una función de host tiene sentido para estos también.
-9. La implementación de Leigh puede requerir una evaluación adicional de los crates utilizados para ecdsa y p256. Breve discusión sobre el proceso propuesto para añadir una función de host por un desarrollador no central.
-10. La implementación de Leigh puede requerir una evaluación adicional de las crates utilizadas para ecdsa y p256.
-11. Breve discusión sobre el proceso propuesto para la adición de una función host por un desarrollador no central.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-02-09.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-02-09.mdx
deleted file mode 100644
index b1e8bbe5ab..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-02-09.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: 2024-02-09
-authors: kalepail
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1Hgp8K_XDeq4yaON3TWeHDtQTAyVR1crY/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Hilo de agenda de Discord](https://discord.com/channels/897514728459468821/1204462856037470248)
-
-1. Presentación en borrador de la Lista de Activos Stellar (SEP-0042) por [OrbitLens](https://github.com/orbitlens)
-   1. [Borrador de SEP](https://github.com/orbitlens/stellar-protocol/blob/sep-0042-token-lists/ecosystem/sep-0042.md)
-   2. [Discusión en Discord](https://discord.com/channels/897514728459468821/1162558946867953704)
-2. Encuesta sobre la documentación de Stellar + Soroban
-   1. [Realiza la encuesta](https://discord.com/channels/897514728459468821/1204462856037470248/1205196745877757962)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-02-15.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-02-15.mdx
deleted file mode 100644
index 5a2ae63022..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-02-15.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: 2024-02-15
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1oBuYg_LvGRGnKpjezok6PQGVN8ZpqVvy/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1207385360116490360)
-
-1. La reunión se centró en el proceso de añadir funciones de host, utilizando WebAuthN como caso de uso de ejemplo; continuó de la reunión anterior.
-2. Discusión sobre las preocupaciones restantes con la adición de la función de host de verificación secp256r1 de la reunión anterior.
-   - ¿Qué significa que secp256r1 se agregue como una función de host versus como un tipo de firmante?
-     - Como función de host, el usuario puede firmar entradas de autenticación de soroban. Necesito otra cuenta stellar para financiar y enviar tx a la cadena. Este último puede ser realizado por una cuenta stellar que puede ser operada por una billetera o un contrato. Need another stellar account to fund and submit tx to the chain. El último se puede hacer mediante una cuenta stellar que puede ser operada por una billetera o un contrato.
-     - __check_auth se invoca cuando el contrato con el que se está interactuando llama a require_auth
-3. CAP-52 fue redactado para introducir funciones de codificación/decodificación para Base64, que es necesario para WebAuthN. Consideraciones discutidas en la reunión:
-   - Rendimiento: 1066 bytes que cuestan 1M instr para codificar un hash de 32bytes; así que el costo es muy bajo y es cuestionable si se necesita una función de host.
-   - La interfaz requiere dos funciones (codificar/decodificar)
-   - Implementation wise, WebAuthN requires url alphabet and padding, which decoder likely needs to support. ¿Deberíamos usar símbolos o enteros? ¿Necesitamos alfabetos personalizados?
-   - ¿Realmente necesitamos más esquemas de codificación? ¿No es suficiente XDR?
-   - Los mecanismos de autenticación costosos, es decir, webauthn, no pueden estar acoplados con contratos con lógica comercial pesada (que podrían ser muchos contratos), lo que hace que la adopción sea problemática.
-   - Probablemente deberíamos agregar bloques de construcción para permitir que el ecosistema agregue nuevos casos de uso.
-4. CAP-53 was drafted to introduce encoding/decoding functions for JSON, which is needed by WebAuthN. Considerations discussed in the meeting:
-   - Rendimiento: 3.9Kb, 2.5M instrucciones de CPU.
-   - Si el tamaño del blob de entrada es desconocido, el tiempo de ejecución aumentará.
-   - Es valioso tener tal función ligera que se utilizará en varios lugares.
-   - Interfaz: 11 funciones
-     - ¿Qué hacer con números y decimales? ¿Agregar decimales y flotantes?
-     - Solo tenemos que extraer un campo para WebAuthN, pero ¿qué pasa con el caso general?
-   - El tipo de número en JSON es decimal, pero soroban no lo soporta. ¿Cómo debería manejarse esto?
-   - Discusión sobre una interfaz alternativa e implementaciones.
-5. Preocupaciones de los desarrolladores principales
-   - Mantenibilidad: si agregas una función de host, debes mantenerla para siempre. Si hay más versiones, tenemos que mantenerlo.
-   - Superficie expandida para errores de seguridad.
-   - Debería definirse un camino donde los desarrolladores principales no estén en el bucle de implementación, ya que sus horarios están llenos de trabajo de estabilidad. How to prioritize against stability work, which may get derailed due to new functionality such as what’s being currently discussed.
-   - Próximos pasos:
-     - El equipo principal debe elaborar un plan para agregar Base64. Este es un ejercicio importante que ayuda a determinar aún más desafíos al hacerlo. El resultado de este ejercicio puede ser que Base64 _no debería_ de hecho ser implementado en este momento.
-     - La discusión sobre la interfaz JSON continuará.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-02-22.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-02-22.mdx
deleted file mode 100644
index f5a327c121..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-02-22.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: 2024-02-22
-authors: kalepail
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1ZZm1eLe6L0ZRtpTxF77RfrLkW9ThAWh4/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Hilo de la agenda de Discord](https://discord.com/channels/897514728459468821/1209582245824823337)
-
-1. Lo último y lo mejor sobre las vinculaciones de TypeScript con [@chadoh](https://github.com/chadoh)
-2. [Proveedores RPC disponibles](/docs/data/apis/rpc/providers)
-3. Configurar un contenedor Docker [`stellar-rpc`](/docs/data/apis/rpc/admin-guide#docker-image)
-4. Instalar e invocar un contrato de activo Stellar en mainnet en la Fase 0
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-02-29.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-02-29.mdx
deleted file mode 100644
index f1bd4a8efd..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-02-29.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: 2024-02-29
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1zKvUx74UqvfmpNvU8BJt5RAqj-XHyBke/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Hilo de agenda en Discord](https://discord.com/channels/897514728459468821/1212118102565855243)
-
-1. Tommaso (@tdep) propuso un cambio central para permitir extender el TTL de instancia y código con valores separados en el entorno de host para permitir diseños más eficientes en costos. La propuesta y la discusión están registradas en las discusiones de GitHub [stellar-core#1447](https://github.com/stellar/stellar-protocol/discussions/1447)
-2. Tommaso recibió comentarios sobre la propuesta y la implementación. Como no requería un cambio de medición, los desarrolladores centrales pensaron que sería un cambio rápido.
-3. El ecosistema votó a favor de la propuesta al votar a favor del post en las Discusiones de GitHub. Se registraron 13 votos [grabados](https://github.com/stellar/stellar-protocol/discussions/).
-4. Como próximos pasos, se redactará un CAP para capturar la propuesta y presentarla para su aprobación por parte del Equipo Central de CAP.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-03-07.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-03-07.mdx
deleted file mode 100644
index a6977f3eed..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-03-07.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: 2024-03-07
-authors: kalepail
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1FJueTZweJPaOyno0fxHOfU3Ec2S0gvO_/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Hilo de agenda de Discord](https://discord.com/channels/897514728459468821/911254664576643122/1215404506964172890)
-
-1. [Herramienta Sorobill](https://github.com/kalepail/sorobill)
-2. Desplegar contratos y probar invocaciones contra el [quickstart](https://github.com/stellar/quickstart) ilimitado.
-3. Utilizando el paquete Sorobil como una herramienta para obtener una imagen de todos los límites que el contrato está tocando. [Publicación de blog relevante](https://kalepail.com/blockchain/show-me-the-bill-part-2)
-4. Cómo medir los costos del contrato y qué límites estás tocando
-5. Utilizando la herramienta Sorobil para decodificar XDR y entender las transacciones fallidas.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-03-14.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-03-14.mdx
deleted file mode 100644
index da1f078113..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-03-14.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 2024-03-14
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1Gztue3zvZBQzVPshM0_Yy8ntYh7Bk33d/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/1217193723612368926)
-
-1. El equipo principal de CAP deliberó sobre las últimas propuestas presentadas por el ecosistema Stellar para avanzar stellar-core.
-2. Nicholas y David del equipo principal de CAP escucharon las siguientes propuestas y discutieron las propuestas con los autores. a. El equipo principal de CAP enviará su voto por correo electrónico.
-3. Propuestas discutidas:\
-   a. [CAP-51](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md): agregar soporte para la verificación secp256r1; por @leigh\
-   b. [CAP-53](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md): crear funciones separadas para extender el tiempo de vida de la instancia de contrato y del código del contrato; por @tdep\
-   c. [CAP-54](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0054.md): reducir los costos totales refinando el modelo de costos de Soroban utilizado para la creación de instancias de VM en varios costos separados y más precisos; por @graydon\
-   d. [CAP-55](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0055.md): reducir los costos totales al vincular menos funciones host durante la creación de instancias de VM en Soroban; por @graydon\
-   e. [CAP-56](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0056.md): reducir los costos totales almacenando en caché los módulos Wasm analizados dentro de una transacción de Soroban; por @graydon
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-03-21.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-03-21.mdx
deleted file mode 100644
index 064c9d1059..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-03-21.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: 2024-03-21
-authors: kalepail
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1vSkQFbdg80548ShpjOpyD9scnQjebkQi/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Hilo de agenda de Discord](https://discord.com/channels/897514728459468821/1219381314931917000)
-
-1. Hay una discusión sobre un cambio de meta TX que aumenta la visibilidad y los análisis dentro de la red Stellar. (https://github.com/stellar/stellar-xdr/pull/175)
-2. Se explica que las invocaciones de solo lectura para contratos garantizan que ciertas funciones sigan siendo de solo lectura sin efectos secundarios. (https://github.com/stellar/stellar-protocol/discussions/1454) (https://github.com/stellar/stellar-protocol/discussions/1456) (https://github.com/stellar/stellar-protocol/discussions/1464)
-3. Se introduce la habilitación del descubrimiento de contratos para mejorar la visibilidad y autenticidad de los contratos inteligentes dentro del ecosistema Stellar.
-4. Se propone la implementación de un esquema de metadatos estándar de contrato para vincular contratos con código fuente y mejorar la capacidad de descubrimiento de contratos.(https://docs.rs/soroban-sdk/latest/soroban_sdk/macro.contractmeta.html)
-5. Problemas relacionados con las tarifas de inclusión en la red Stellar, destacando la importancia de monitorear las tarifas de cerca y entender las implicaciones del [precios variables](/docs/learn/fundamentals/fees-resource-limits-metering#inclusion-fee)
-6. Se discuten planes para diseñar un nuevo punto final RPC que brinde a los desarrolladores mejor visibilidad e información sobre el establecimiento de tarifas de inclusión, con el objetivo de mejorar la transparencia y la toma de decisiones respecto a las compensaciones de tarifas.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-03-28.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-03-28.mdx
deleted file mode 100644
index 34ae91d52c..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-03-28.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: 2024-03-28
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1e7AgsEAno0pZBYkICuKaqC3HMQkjWRd9/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Agenda thread](https://github.com/stellar/stellar-protocol/discussions/1475)
-
-1. El Grupo de Trabajo de Normas propuso cambios al proceso SEP que empoderan al ecosistema al hacer que el proceso actual sea más descentralizado y amigable con el ecosistema.
-2. El proceso ya ha sido utilizado para varias propuestas en los últimos tres meses.
-3. Esteblock from Soroswap shared their journey of participating in the proposal for Asset List ([SEP-42](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0042.md)) and implementing the proposed standard
-4. La discusión continúa en el documento de propuesta.
-5. El siguiente paso es obtener más retroalimentación del ecosistema y luego actualizar el repositorio de SEP de Github con el proceso SEP actualizado.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-04-04.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-04-04.mdx
deleted file mode 100644
index d4caba9d80..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-04-04.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: 2024-04-04
-authors: naman
-tags:
-  - developer
----
-
-La grabación de hoy tiene dos partes. Los primeros 12 minutos son solo audio. Los próximos 45 minutos también tienen video. Ten en cuenta que las diapositivas se compartieron en el chat de discord mediante la pantalla compartida, debido a dificultades técnicas.
-
-Parte 1 (solo audio):
-
-<iframe
-  frameborder="0"
-  width="500"
-  height="100"
-  src="https://drive.google.com/file/d/14ddYFIMDgsX70hTCv8C1tKaAGmJiprw7/preview"
-></iframe>
-
-Parte 2 (video):
-
-<iframe
-  src="https://drive.google.com/file/d/1p4LrgGLfRdVww-7d21w3BGyPrLfiIDmF/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Hilo de Agenda de Discord](https://discord.com/channels/897514728459468821/1224408179363024918)
-
-1. Piyal propuso un [Estándar de Billetera](https://github.com/stellar/stellar-protocol/discussions/1467) y solicitó retroalimentación.
-2. Cubist, un proyecto del ecosistema, discutió CubeSigner, una API de baja latencia para generar claves y firmar transacciones dentro de hardware seguro.
-3. Un ejemplo de CubeSigner basado en Stellar está disponible en el [repositorio de Cubist Labs en Github](https://github.com/cubist-labs/CubeSigner-TypeScript-SDK/tree/main/examples/stellar)
-4. Los desarrolladores de Cubist pueden ser contactados a través del discord de Stellar o del [formulario web](https://cubist.dev/contact-form-cubesigner-hardware-backed-key-management).
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-04-11.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-04-11.mdx
deleted file mode 100644
index 404a5638ae..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-04-11.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: 2024-04-11
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1OCt2lXcrwhVyRd4dcwj8mfCOzxXON6nL/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-Piyal de Freighter discutió la propuesta para estandarizar la interfaz de billetera. Los puntos clave de la discusión se capturan a continuación. Para notas completas, por favor ve la grabación; y también consulta la propuesta y la publicación en las discusiones de github.
-
-1. [La propuesta borrador](https://github.com/stellar/stellar-protocol/blob/83191be659166e05f8df1257c6f655de9d1afe63/ecosystem/sep-0043.md)
-2. [Discusión en curso](https://github.com/stellar/stellar-protocol/discussions/1467)
-3. Requerir la frase de paso de la red podría ser una complejidad innecesaria.
-4. Tanto WalletConnect como las billeteras móviles probablemente tienen diferencias significativas respecto a la interfaz propuesta (que está dirigida a billeteras de extensiones de navegador); y por lo tanto es probable que requieran un SEP separado. Los SEPs mencionados deberían ser creados por equipos que trabajen en la integración de billeteras con las plataformas mencionadas.
-5. ¿Cuál es el papel de Stellar Wallet Kit en el ecosistema y cómo interactúa con el estándar mismo?
-6. Como próximos pasos, Piyal incorporará las sugerencias del ecosistema en la propuesta.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-04-18.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-04-18.mdx
deleted file mode 100644
index 481ecb0618..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-04-18.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: 2024-04-18
-authors: kalepail
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1ZUdrK0YuF69un_KA3rJGvZaD_wmgYG8N/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/911254664576643122/1215404506964172890)
-
-1. Justin de [ortege.ai](https://www.ortege.ai/) hizo una demostración de Ortege, una plataforma de análisis de datos para Stellar y Soroban.
-2. Ortege permite que cualquier persona en el ecosistema Stellar cree paneles de control para rastrear cualquier métrica deseada. Las consultas, widgets y paneles de control de Ortege son compartibles, lo que lo convierte en la plataforma perfecta para mostrar
-3. Justin lanzará pronto una IA y habilitará la consulta y los conocimientos a través del lenguaje natural.
-4. Todos están invitados a crear una cuenta gratuita y rastrear las métricas de éxito para su panel de control.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-04-25.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-04-25.mdx
deleted file mode 100644
index 651cfe9bbe..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-04-25.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: 2024-04-25
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1WdZeRnjwl0FCxwtQhy2DNqMtNIiZIgtD/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. Garand discussed changes to the State Archival proposal based on feedback received at Meridian 2023. Los cambios propuestos son:
-
-- Anteriormente, un sistema de downstream llamado el ESS (Almacenamiento de Estado Caducado) almacenaba entradas caducadas. En la nueva propuesta, no hay ESS. En la nueva propuesta, no hay ESS. Todas las entradas archivadas, así como toda la información requerida para generar pruebas de restauración para esas entradas, se almacena directamente en el Archivo de Historia.
-- Los nodos RPC pueden generar pruebas para el estado archivado durante el pre-vuelo
-- Captive-core puede ser consultado directamente para el estado archivado, lo que significa que las instancias RPC/Horizon pueden potencialmente atender consultas para el estado de archivo
-
-2. [La propuesta de borrador](https://docs.google.com/document/d/1FAs3Yfo-o-gVqccrP29NSG8ysRvdEoyvuL7ywV4ijXI/edit#heading=h.1xwsoyifxbfm)
-3. [Discusión en curso](https://github.com/stellar/stellar-protocol/discussions/1480)
-4. El tamaño de la imagen está por determinar; es una función del tamaño de la lista de cubos, así como de la memoria y las demandas históricas impuestas al RPC.
-5. Los filtros de Bloom son la solución probable para la prueba de inexistencia, aunque vienen con compensaciones. Permiten una búsqueda rápida y económica, pero son probabilísticos, no deterministas.
-6. Se agradecen más comentarios.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-05-02.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-05-02.mdx
deleted file mode 100644
index 5ce9abb6f1..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-05-02.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: 2024-05-02
-authors: naman
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1-XWdGA3vMqoMI6DqBDtjKR_DTeOImpbZ/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Hilo de Agenda de Discord](https://discord.com/channels/897514728459468821/1234887262530048010/1234887262530048010)
-
-1. Fifo presentó [Stellar Plus](https://docs.cheesecakelabs.com/stellar-plus), que es una biblioteca de Javascript para simplificar el desarrollo de Stellar y Soroban.
-2. Los miembros del ecosistema encontraron el diseño de Stellar Plus como composable e inclusivo de toda la funcionalidad relacionada con Stellar, incluyendo la gestión de activos, cuentas, operaciones relacionadas con wasm, así como utilidades RPC.
-3. Los enlaces a la presentación de Fifo y Stellar Plus son:
-   - [Tablero de Miro mostrando la arquitectura de Stellar Plus](https://miro.com/app/board/uXjVKMDkMPI=/?share_link_id=643609701897)
-   - [Repositorio de Stellar Plus](https://discord.com/channels/897514728459468821/1234887262530048010/1235699608274079865)
-   - [Repositorio de Ejemplos](https://github.com/fazzatti/stellar-plus-examples)
-   - [Documentos](https://docs.cheesecakelabs.com/stellar-plus)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-05-09.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-05-09.mdx
deleted file mode 100644
index f931d0b705..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-05-09.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: 2024-05-09
-authors: naman
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1PvA8cxInSfRjmewJbILhgpZYv4CBExZv/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. Tyler desarrolló una aplicación de votación utilizando claves de acceso para firmar la transacción, que es una implementación de la función de verificación secp256r1.
-2. Mostró una implementación multiplataforma (web y móvil) y demostró que las claves de acceso son la interfaz perfecta entre los contratos web3 y los mecanismos de autenticación web2 a los que la mayoría de los usuarios finales están acostumbrados.
-3. Los miembros del ecosistema discutieron el uso de billeteras inteligentes que utilizarían claves de acceso como firmantes. Se identificaron desafíos en torno a las tarifas requeridas para las billeteras inteligentes, la necesidad de una implementación común para una billetera inteligente, así como cómo podría interactuar con los administradores de contraseñas existentes.
-4. La aplicación de votación se puede probar en [passkey.sorobanbyexample.org/](https://passkey.sorobanbyexample.org/)
-5. El código para la demo está aquí [github.com/kalepail/soroban-passkey](https://github.com/kalepail/soroban-passkey)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-06-13.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-06-13.mdx
deleted file mode 100644
index 02684ad202..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-06-13.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: 2024-06-13
-authors: kalepail
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1goVLHLJWWwRy1xgBpJa4VF1y9axrlIqA/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. Tyler creó Super Peach, una aplicación web3 que utiliza claves de acceso para firmar transacciones. Demostró cómo se pueden usar las claves de acceso en flujos de autorización y cómo se pueden usar para firmar transacciones.
-   - Código: https://github.com/kalepail/superpeach
-   - Demostración: https://superpeach.xyz
-2. Se presentó `passkey-kit`. Un SDK de TypeScript para crear y gestionar billeteras inteligentes a través de claves de acceso (incluye la [interfaz de billetera inteligente](https://github.com/kalepail/passkey-kit/tree/main/contracts))
-   - Código: https://github.com/kalepail/passkey-kit
-   - Demostración: https://passkey-kit-demo.pages.dev
-3. Se presentó Launchtube, un servicio para enviar transacciones en cadena cubriendo tanto la tarifa de transacción COMO el número de secuencia. ¡Increíble!
-   - Código: https://github.com/kalepail/launchtube (pregunta en el canal `#passkeys` en Discord por un token de testnet)
-4. Compartió su visión para impulsar la implementación de las claves de acceso hasta convertirse en un [estándar para el ecosistema](https://docs.google.com/document/d/1c_Wom6eK1UpC3E7VuQZfOBCLc2d5lvqAhMN7VPieMBQ/edit).
-
-Únete al canal `#passkeys` en Discord para continuar la discusión
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-06-20.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-06-20.mdx
deleted file mode 100644
index 0498aef6bd..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-06-20.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: 2024-06-20
-authors: naman
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1nrEQdhiTH4wsQVgaiOO0RcmD-AS-5S2v/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. [Kirckz discute Meru](https://docs.google.com/presentation/d/1Fu4AkB0mrvOkK6UDFJHgKwCV-Ul4JRF-xPqTYJ3CQqw), una aplicación de servicios financieros para freelancers y trabajadores remotos en América Latina.
-2. Él comparte su experiencia integrando Meru con Blend, un protocolo de liquidez primitiva para Stellar.
-3. Kirckz comparte los desafíos enfrentados durante la integración y cómo fueron superados.
-4. Él comparte los sdks y bibliotecas que su equipo utilizó para facilitar la integración.
-
-Sigue a Meru en X (anteriormente Twitter) para mantenerte actualizado: https://x.com/getmeru
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-06-27.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-06-27.mdx
deleted file mode 100644
index ecb2b316e2..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-06-27.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: 2024-06-27
-authors: naman
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1PS49Cvs_DLdEwquh6c9e5JuN3MASaTpz/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. [Chad](https://github.com/chadoh) y [Willem](https://github.com/willemneal) de [Aha Labs](https://github.com/AhaLabs) discuten las actualizaciones del nuevo y mejorado [stellar-cli](https://github.com/stellar/stellar-cli)
-2. Algunos aspectos destacados incluyen el cambio del nombre 'soroban' a 'stellar' al usar la herramienta CLI y la adición de nuevos comandos.
-3. They cover some cool functions like local network setup, account creation, and transaction signing. con los siguientes comandos:
-   - `stellar network container [start|logs]`
-   - `stellar keys [generate|fund|ls]`
-   - `stellar contract init` para obtener un nuevo proyecto de Soroban
-   - ¡y mucho más!
-4. They also discuss expected future updates including support for more Stellar operations and integration with Stellar Lab V2!
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-07-11.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-07-11.mdx
deleted file mode 100644
index 886abc9aa6..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-07-11.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: 2024-07-11
-authors: naman
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1uBv-Qv6bHzri7OeRyBJo7hxJtH6CKjEH/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. 2. [Las diapositivas](https://docs.google.com/presentation/d/1QsCwFLFcDF4RmNIwtSSnNrUfZb0RM0kLxOOxC7ENY5M/edit#slide=id.g2cb5821e4de_1_1143) están disponibles públicamente y son legibles de forma asíncrona.
-2. 4. Comparte tus consultas y publica preguntas en #hubble en discord de Stellar, que es un canal dedicado a temas relacionados con datos.
-3. También se incluyen consejos para el análisis de datos en [docs](/docs/data/analytics/hubble/analyst-guide)
-4. Comparte tus consultas y publica preguntas en #hubble en el Discord de Stellar, que es un canal dedicado a temas relacionados con datos.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-07-18.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-07-18.mdx
deleted file mode 100644
index b2d378f6ab..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-07-18.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: 2024-07-18
-authors: naman
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1lml1VxNkwsRKS9BbnIMFNRXX1Kn6ktvq/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-Nota: la primera parte de la llamada se perdió. El video publicado arriba captura la segunda mitad de la llamada donde varios desarrolladores del ecosistema compartieron sus casos de uso y necesidades para una billetera inteligente en Stellar.
-
-1. Tyler propuso una [propuesta](https://github.com/stellar/stellar-protocol/discussions/1499) para una billetera inteligente como un bien público. Dado que la autenticación nativa puede sobrecargarse al usar `__check_auth`, la implementación de Stellar de una billetera inteligente es bastante sencilla. La capacidad de personalizar la autenticación ya está desarrollada en el protocolo central.
-2. Consulta la [propuesta](https://github.com/stellar/stellar-protocol/discussions/1499) aquí y la implementación [aquí](https://github.com/kalepail/passkey-kit/blob/main/contracts/webauthn-wallet/src/lib.rs)
-3. La propuesta solo utiliza firmantes basados en WebAuthN, es decir, claves de acceso. No utiliza ed25519, que, quizás debería dado que ~100 % de las cuentas en Stellar utilizan ese esquema. También introduce la noción de firmantes temporales y administradores para ilustrar que la cuenta puede ser gestionada por múltiples firmantes, cada uno con una política de acceso diferente.
-4. El mayor desbloqueo con la autenticación personalizada es la capacidad de ejecutar lógica personalizada. Escuchamos de varios miembros del ecosistema sobre cómo podrían usarlo. 4a. Un desarrollador está construyendo un protocolo perpetuo y pensó que las billeteras inteligentes podrían usarse para gestionar automáticamente posiciones de defi, lo que sería una mejora significativa sobre el statu quo donde el usuario tiene que rastrear constantemente los activos para determinar _cuándo_ ejecutar un intercambio. 4b. La gente está entusiasmada por prescindir de la frase semilla para las claves de acceso, lo cual es especialmente significativo al integrar nuevos usuarios a la blockchain. 4c. Autorizar un mensaje entre cadenas desde una cadena diferente, especialmente autorización programática, requiere una implementación de cuentas personalizadas. 4d. Algunas aplicaciones han notado que los usuarios prefieren no tener una billetera, sino simplemente experimentar el valor de la aplicación, especialmente los juegos. Para esto, la aplicación puede asignar una cuenta temporal al usuario y controlar el acceso mediante check_auth. 4c. Las microtransacciones sin necesidad de firma de usuario son también muy interesantes para las aplicaciones.
-5. Esta ha sido una reunión muy reveladora y aprendimos sobre cómo el ecosistema Stellar planea aprovechar la billetera inteligente. ¡Continuemos la conversación en Discord!
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-07-25.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-07-25.mdx
deleted file mode 100644
index b5f086716d..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-07-25.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: 2024-07-25
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1ScrEdoscrVQX_PzaMBCHavycg8dLpaIx/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-Un desarrollador principal, Dima, discutió la propuesta de añadir soporte para constructores a Soroban, el sistema de contratos inteligentes de Stellar.
-
-Enlaces relevantes: [Borrador CAP](https://github.com/stellar/stellar-protocol/blob/50dde0611440d6dc562a33462e6ba5f1504b2753/core/cap-0058.md), [Discusión en curso](https://github.com/stellar/stellar-protocol/discussions/1501), [Hilo de Discord motivador](https://discord.com/channels/897514728459468821/1067534037310255225)
-
-Puntos clave discutidos:
-
-1. La propuesta mejora la usabilidad de Soroban para desarrolladores de contratos y SDK. Un constructor garantiza la inicialización del contrato, lo que reduce el código adicional del contrato que usualmente se agrega para asegurar la inicialización.
-2. Hubo un acuerdo general con la propuesta, las preguntas se centraron principalmente en la implementación, como si los constructores deben manejar argumentos, qué debe suceder con las actualizaciones, la compatibilidad hacia atrás con las funciones de creación de contratos y el comportamiento en la actualización de wasm.
-3. El tema de alto impacto sobre la nomenclatura se somete a votación en el ecosistema, por favor vota [aquí](https://github.com/stellar/stellar-protocol/discussions/1507).
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-08-01.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-08-01.mdx
deleted file mode 100644
index 577f484f1e..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-08-01.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: 2024-08-01
-authors: naman
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1Hog269Q96QMEJeC2DZHIMUkjMtj98YYj/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. Piyal demostró que la funcionalidad de intercambio de Freighter ahora se sirve a través de [Soroswap](https://soroswap.finance/). Anteriormente, se servía a través de Stellar Dex.
-2. Freighter ha hecho disponibles las instrucciones de integración [aquí](https://github.com/stellar/freighter/blob/d248f2ad0aa03da72ea6eeaf7907ac0454fdcc72/extension/INTEGRATING_SOROSWAP.MD?plain=1#L2).
-3. Esteban compartió que [Palta Labs](https://paltalabs.io/) ha creado un agregado de DEX y lo ha hecho disponible para todos a través del [Router SDK](https://docs.soroswap.finance/03-technical-reference/07-optimal-route/01-soroswap-router-sdk).
-4. El Router SDK encuentra la ruta óptima para el intercambio en términos de costo de intercambio a través de todos los DEX en Soroban.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-08-08.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-08-08.mdx
deleted file mode 100644
index de73b96938..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-08-08.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: 2024-08-12
-authors: naman
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1Q6a8WpUKplujhbD6MMzrTlfjfdXFTrBd/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. Tdep discutió sobre Zephyr, un entorno de ejecución desarrollada sobre el indexador Mercury. También explicó ejemplos que demuestran cómo Zephyr puede simplificar el desarrollo de dapps.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-08-15.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-08-15.mdx
deleted file mode 100644
index 86fa9355b7..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-08-15.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 2024-08-15
-authors: julian
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1V5Arzh7LgWMj2E7FjZyGTFUl0vV31xll/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-1. @Soiled y @Robeart de Orbit hablaron sobre usar Blend para crear stablecoins descentralizadas para todas las monedas bajo el Protocolo Orbit, utilizando un pegkeeper descentralizado para mantener su precio y aprovechando estas stablecoins y billeteras inteligentes para crear un exchange perpetuo sin libro de órdenes, llevando Forex a Stellar
-
-2.[Enlace a la presentación](https://docs.google.com/presentation/d/1mDOrBLfe8-Bq6VCy7r5bb4w_uZjq-EOorbV3ZwYfs1k/edit?usp=sharing)
-
-_Nota_: El audio del micrófono del host no está en el video, por lo que hay algo de silencio durante la sesión de preguntas y respuestas. Aquí están las preguntas realizadas durante la sesión de preguntas y respuestas:
-
-1. (De ! markus_0) ¿por qué siempre tienes una cantidad infinita de tokens en el pool? ¿No sería más seguro empezar pequeño y acuñar más a medida que se abra la demanda? 2.(De HunterIonize) ¿Qué propósito sirve esto exactamente? Lo siento por ser directo
-2. ¿Cómo ves al Protocolo Orbit contribuyendo a la inclusión financiera a nivel global, particularmente en regiones sub-bancarizadas? ¿Qué desafíos anticipas para lograr esto?
-3. En 5-10 años, ¿cómo ves que evolucione el panorama de Forex en blockchain? ¿Qué papel crees que jugará Stellar en esta evolución, y cómo estarán Blend y el Protocolo Orbit a la vanguardia?
-4. ¿Hay alguna solicitud de la comunidad de desarrolladores?
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-08-22.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-08-22.mdx
deleted file mode 100644
index 46b3c0fe1e..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-08-22.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: 2024-08-23
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1Eqi0znJ21aSfjXYJ10V7eByhr-sTzujY/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-[Discord agenda thread](https://discord.com/channels/897514728459468821/900374272751591424/1275577430043525204)
-
-Los desarrolladores principales discutieron las últimas propuestas para avanzar en Stellar Core en la reunión de protocolo de esta semana.
-
-1. La propuesta para la adición de un constructor a la variante de Rust de Soroban fue introducida en una reunión de protocolo anterior ([reunión previa](./2024-07-25.mdx)), documentada en [CAP-58](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md). Un constructor es una función que solo se ejecutará la primera vez que se crea el contrato.
-2. En esta reunión, Dima discutió las actualizaciones realizadas desde la última reunión:
-   1. Constructor por defecto - si un constructor no se define explícitamente, el contrato se trata como si tuviera un constructor
-   2. Semántica del valor de retorno - si la transacción tiene éxito, se requiere que devuelva un valor válido
-   3. Interacción del constructor con cuentas personalizadas - las cuentas personalizadas deben ser conscientes del contexto que están autorizando.
-3. Graydon discutió la actualización de la máquina virtual Wasmi, documentada en [CAP-60](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0060.md). Wasmi funciona traduciendo código WebAssembly a una Representación Interna (IR) y luego ejecutándola. La actualización tiene un impacto de dos maneras.
-   1. Traducir de WebAssembly a IR toma más tiempo, pero la ejecución del IR resultante es eficiente.
-   2. La actualización introduce compilación perezosa. De todas las funciones en un contrato, solo aquellas que se llaman en una transacción dada serán traducidas, reduciendo así tanto la latencia como las tarifas.
-4. Jay discutió la adición de la curva criptográfica BLS12-381, documentada en [CAP-59](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md).
-   1. La adición de curvas elípticas amigables para el emparejamiento permite aplicaciones basadas en zk. Se han agregado 11 funciones de host para exponer mapeo, emparejamiento y aritmética en la curva BLS12-381.
-   2. Se presentó un caso de ejemplo de verificación de firma BLS. Consumió 26M de instrucciones (ejecutándose de forma nativa), lo que es prometedor dado que el límite por transacción es 100M.
-   3. Hubo un acuerdo general en que la interfaz es la correcta, ya que permite a un desarrollador de contratos implementar una amplia variedad de casos de uso. La discusión continúa en discord.
-   4. Jay solicitó que los desarrolladores construyan aplicaciones contra la función y den su opinión.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-08-29.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-08-29.mdx
deleted file mode 100644
index dbec1aba0f..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-08-29.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: 2024-08-29
-authors: naman
-tags:
-  - protocol
----
-
-<iframe
-  src="https://drive.google.com/file/d/1RBFt9diUPAgoeurw4xluyA9Qq1JNG2w8/preview"
-  width="640"
-  height="360"
-  allow="autoplay"
-></iframe>
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1278045556211716171)
-
-El equipo central de CAP deliberó sobre los CAPs propuestos:
-
-1. Adición de un constructor a la variante de Rust de Soroban. [CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md)
-   1. La preocupación del equipo era sobre una posible ruptura en la compatibilidad, lo cual Dima había abordado. No hubo más preocupaciones.
-2. Adición de la curva BLS12-381 y la aritmética de campo requerida - [CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md)
-   1. La preocupación del equipo era sobre proporcionar funciones para verificar entradas no válidas. Es demasiado costoso computacionalmente hacer la verificación en la capa del contrato, por lo que puede que necesite implementarse como una función de host. Jay está buscando la opinión del ecosistema sobre los casos de uso que requieren validación estricta de entradas.
-   2. No hubo más preocupaciones.
-3. Incrementar el rendimiento mejorando la VM de Soroban. [Discusión sobre CAP](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0060.md)
-   1. Los comentarios del equipo eran sobre la precisión del método de medición, pero los beneficios demostrados del tiempo de reloj se consideraron prometedores.
-   2. Se sugirió exponer las mejoras de rendimiento a los desarrolladores de contratos, creando así el incentivo para optimizar contratos y aprovechar las mejoras.
-   3. No hubo más preocupaciones.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-09-05.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-09-05.mdx
deleted file mode 100644
index fa8ddb9b57..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-09-05.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: 2024-09-05
-authors: anataliocs
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1bw1KCnF2C6cz0NhWNGKoUOg4oiC-OZck/preview"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1280678171053789317)
-
-El equipo de la plataforma demostró Galexie, una parte de CDP (Composable Data Platform):
-
-1. Galexie
-   1. Extracción de Datos: Extrae datos brutos del ledger de la red Stellar
-   2. Compresión: Comprime los datos brutos para un almacenamiento eficiente
-   3. Opciones de Almacenamiento: Admite la configuración en tiempo de ejecución a través de la abstracción del Datastore para utilizar varias capas de almacenamiento físico, comenzando con Google Cloud Storage (GCS)
-   4. Modos de Operación: Puede operar en modo por lotes o en modo de transmisión
-2. Plataforma de Datos Componible
-   1. Datastore Flexible: Múltiples opciones para capas de almacenamiento de datos físicas
-   2. Galexie: Se utiliza para extraer, comprimir y exportar datos a tu Datastore elegido
-   3. Transformar: Estructura los datos en un modelo adecuado para tu aplicación
-3. Canalizaciones de Datos Plugables
-   1. Flujos de Trabajo: Crea canalizaciones ETL (extraer, transformar, cargar)
-   2. Transmisión: Datos de transmisión rápidos y livianos
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-09-12.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-09-12.mdx
deleted file mode 100644
index f835ee57b1..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-09-12.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: 2024-09-12
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1raU1Z9EQBLCkkuUO9yyF8yD2l_3nwk4a/preview"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-Agenda: [Hilo de Discord](https://discord.com/channels/897514728459468821/900374272751591424/1282934024892973077)
-
-El miembro del equipo de Experiencia del Desarrollador, Nando Vieira, presentó las características alias y snapshot del CLI:
-
-1. Alias
-   1. Instalación del ejemplo Hello World para mostrar el alias
-   2. Se mostraron ejemplos de cómo los IDs de contrato a menudo se pasan como parámetros en comandos del CLI como invoke (copiando la cadena ID o sustitución de comando)
-   3. Cómo desplegar un contrato inteligente y crear un alias
-   4. Cómo invocar el contrato inteligente con el alias
-2. Snapshot
-   1. Cómo crear una imagen del ledger
-   2. Cómo usar la imagen en un caso de prueba
-
-Hacia el final, Nando revisó la documentación para desarrolladores, centrándose en los ejemplos de línea de comandos añadidos para usuarios de Windows y un útil recetario para comandos del CLI.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-09-19.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-09-19.mdx
deleted file mode 100644
index d1b7e63988..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-09-19.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: 2024-09-19
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1yIzMrtyuJkX6W8MlIbwrGNivYqHuhoxH/preview"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-Agenda: [hilo de Discord](https://discord.com/channels/897514728459468821/900374272751591424/1285627254130610297)
-
-El miembro del equipo de DevRel de SDF, Carsten Jacobsen, mostró cómo crear una simple dapp Hello World basada en un contrato inteligente Soroban y Next.js a través de estos pasos:
-
-1. Crear el contrato inteligente Hello World predeterminado usando el Stellar CLI
-2. Crear enlaces de TypeScript (paquete) usando el Stellar CLI
-3. Crear el Next.js predeterminado usando el comando npx create-next-app
-4. Agregar y enlazar el paquete de enlace de TypeScript al proyecto Next.js
-5. Crear un frontend simple con un formulario para enviar una cadena
-6. Importar el paquete en la página de Next.js y configurar un cliente
-7. Crear la función de envío para enviar el valor del formulario al contrato inteligente
-8. Usar useState para almacenar la respuesta del contrato inteligente y mostrarla
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-09-26.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-09-26.mdx
deleted file mode 100644
index b7dce413e5..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-09-26.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: 2024-09-26
-authors: anataliocs
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1gV-4lV32eN5R5rvtK5SY3aH1FVcbwI7D/preview"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1288890126038208532)
-
-Resumen: Hoops Finance, un protocolo DeFi, discutió su plataforma que están desarrollando. https://www.hoops.finance/
-
-1. Abstractan la complejidad de las inversiones DeFi para usuarios normales a través de una serie de indicaciones guiadas.
-2. Proporciona acceso simplificado a la abstracción de provisión de liquidez LP
-3. API AMM pública para leer/escribir datos en AMMs en Stellar
-4. API de Hoops Finance: https://api.v1.xlm.services/#overview
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-10-24.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-10-24.mdx
deleted file mode 100644
index 37d2a36fb0..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-10-24.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: 2024-10-24
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/1saHsJ793C5yQu9pUC9Ao-rAeuIoLjScQ/preview"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-Agenda: [Discord thread](https://discord.com/channels/897514728459468821/900374272751591424/1298362698123182080)
-
-El equipo de Plataforma de SDF tuvo un hackathon interno la semana pasada, con el propósito de crear aplicaciones que utilizan la [Composable Data Platform (CDP)](https://stellar.org/blog/developers/composable-data-platform). En la reunión de desarrolladores de esta semana, algunos de los miembros del equipo presentan sus proyectos. Las aplicaciones son muy variadas (aplicación de comercio, detección de fraudes, ingestor basado en navegador JS, etc.), pero la intención aquí es mostrar lo fácil que es usar CDP.
-
-Proyectos presentados en la reunión:
-
-1. Servicio de Agregaciones de Comercio
-2. Deceptiscan - detección de fraudes CDP
-3. Hackies de Composable Data Platform - indexador de datos, indexador de pagos, alerta de caducidad de contratos, índices de datos en DuckDB, torrents para índices de datos y metadatos de ledger)
-4. Ingesta de datos con JS frontend
-5. Analíticas en tiempo real
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-11-14.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-11-14.mdx
deleted file mode 100644
index 36ad5ccc65..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-11-14.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: 2024-11-14
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://drive.google.com/file/d/16-QDUaoFTvLD0WUshuVQs1lp36XeuMn9/preview"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-Agenda: [Discord thread](https://discord.com/events/897514728459468821/1304859059425382553/1306725344870400000)
-
-En la reunión de desarrolladores de esta semana, Jeesun demostró el nuevo Stellar Lab, mostrando sus características mejoradas diseñadas para mejorar la experiencia del desarrollador.
-
-Se discutió la pila tecnológica del nuevo Stellar Lab en la reunión, y se utilizaron las siguientes demostraciones para mostrar la funcionalidad del Lab:
-
-1. Activar el ejercicio MultiSig
-2. Stellar Wallets Kit
-3. Crear y financiar cuenta
-4. Se discutió la pila tecnológica del nuevo Stellar Lab en la reunión, y se utilizaron las siguientes demostraciones para mostrar la funcionalidad del Lab:
-5. Guardar función de transacciones
-6. Mapeo de XDR a JSON
-7. Métodos RPC - incluyendo simulateTransaction
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-12-05.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-12-05.mdx
deleted file mode 100644
index 69bb56e4fa..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-12-05.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 2024-12-05
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="UCYfq-RuQkY" />
-
-En la llamada de esta semana hablamos con Alberto Chaves de Trustless Work sobre cómo desarrollar un servicio de depósito en Stellar, seguido de una breve introducción al uso de herramientas basadas en IA para desarrollar contratos inteligentes Soroban.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-12-12.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-12-12.mdx
deleted file mode 100644
index 9ac88bf1f6..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-12-12.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 12 de diciembre de 2024
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="w_senlMbHVM" />
-
-En esta reunión, el Defensor del Desarrollador de SDF, Chris Anatalio, habla sobre el stack futuro, incluyendo las carteras de contratos inteligentes y Passkeys. En la segunda mitad, el Ingeniero de Software Principal de SDF, Siddharth Suresh, habla sobre el aumento de los límites de Soroban.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2024-12-19.mdx b/i18n/es/docusaurus-plugin-content-blog/2024-12-19.mdx
deleted file mode 100644
index 8af70bc77d..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2024-12-19.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 2024-12-19
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="51SitOUZySk" />
-
-En esta reunión, Jay, ingeniero de software principal de SDF, habla sobre los bloques constructores BLS y presenta ejemplos y demostraciones.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-01-16.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-01-16.mdx
deleted file mode 100644
index 0176940e53..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-01-16.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: 2025-01-16
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="PJx6effsvTA" />
-
-El equipo de DevRel del Ecosistema de Stellar Development Foundation se reunió para hablar sobre el año pasado y lo que traerá 2025.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-01-23.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-01-23.mdx
deleted file mode 100644
index 92d42c409a..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-01-23.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: 23 de enero de 2025
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="51SitOUZySk" />
-
-<b>Parte 1</b>
-
-En la reunión de esta semana, los fundadores de Hoops Finance, Bastian y Tim, hablaron sobre los avances que han logrado, algunas consideraciones de diseño y el futuro de Hoops Finance.
-
-<YouTube ID="JDlIL5y5bn8" />
-
-<b>Parte 2</b>
-
-Grabación de una reunión del protocolo donde se discutieron dos Propuestas de Avance Central -
-
-Se discutieron CAP-0062 (Priorización del Estado en Vivo de Soroban) y CAP-0066 (Recurso de Lectura en Memoria de Soroban).
-
-Aquí hay varios recursos para leer:
-
-CAP-0062 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md<br /> Discusión - https://github.com/stellar/stellar-protocol/discussions/1575
-
-CAP-0066 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md<br /> Discusión - https://github.com/stellar/stellar-protocol/discussions/1585
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-01-30.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-01-30.mdx
deleted file mode 100644
index 28396ef7b2..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-01-30.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: 30-01-2025
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="1pF9evTU3QE" />
-
-<b>Parte 1</b>
-
-RampMeDaddy se unirá a nosotros en esta Reunión de Desarrolladores de Stellar. RampMeDaddy está participando actualmente en el Programa Stellar x Draper Embark, y preguntamos qué está haciendo el equipo, aprendemos más sobre lo que están desarrollando y mantenemos una charla informal sobre cómo están creando su dapp en Stellar/Soroban.
-
-Visita su sitio web aquí: https://rampmedaddy.com
-
-<YouTube ID="ZL1LfJqmw_M" />
-
-<b>Parte 2</b>
-
-En esta reunión del protocolo se discuten dos Propuestas de Avance del Núcleo: Dima presentará CAP-0064 (Autorización de Memo para Soroban), y Graydon presentará CAP-0065 (Módulo para almacenar en caché reutilizable).
-
-Aquí hay algunos recursos:
-
-CAP-0064 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0064.md<br /> Discusión - https://github.com/stellar/stellar-protocol/discussions/1610
-
-CAP-0065 - https://github.com/stellar/stellar-protocol/blob/master/core/cap-0065.md<br /> Discusión - https://github.com/stellar/stellar-protocol/discussions/1615
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-02-06.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-02-06.mdx
deleted file mode 100644
index bc6d51b2bb..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-02-06.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: 2025-02-06
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Parte 1
-
-<YouTube ID="QrLA66qU9N8" />
-
-El equipo de desarrollo detrás de Reflector y Refractor presenta sus herramientas para finanzas descentralizadas y gestión de transacciones en Stellar. Reflector ofrece feeds de precios on-chain para mejorar los protocolos DeFi, mientras que Refractor proporciona un almacenamiento de transacciones pendientes y un agregador de multisig para la firma coordinada. Cubrirán cómo estos productos admiten interacciones financieras sin confianza y mejoran la ejecución de contratos inteligentes en Stellar.
-
-Visita su sitio web aquí: https://reflector.network
-
-## Parte 2
-
-<YouTube ID="lzxv5ij6TLw" />
-
-En esta reunión de protocolo discutimos dos Propuestas de Avance Central - Dima presentará CAP-0063 (Programación de Transacciones Amigable con el Paralelismo), y Siddharth presentará CAP-0067 (Eventos de Activos Unificados).
-
-Aquí hay algunos recursos para revisar:
-
-- [CAP-0063](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0063.md)
-
-- [Discusión de CAP-0063](https://github.com/stellar/stellar-protocol/discussions/1602)
-
-- [CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-
-- [Discusión de CAP-0067](https://github.com/stellar/stellar-protocol/discussions/1553)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-02-13.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-02-13.mdx
deleted file mode 100644
index 68bf00e784..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-02-13.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 2025-02-13
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Parte 1
-
-<YouTube ID="8UGDT1pGZYU" />
-
-OrbitLens mostrará los servicios de StellarBroker y StellarExpert. StellarBroker es un enrutador de intercambio de liquidez de múltiples fuentes que agrega liquidez de Soroban AMMs, Classic AMMs y libros de órdenes Classic. La segunda parte de la presentación se centrará en los conocimientos sobre contratos inteligentes de Stellar y en el análisis de transacciones on-chain utilizando el explorador de blockchain StellarExpert.
-
-Enlaces:
-
-- [StellarBroker](https://stellar.broker)
-
-- [StellarExpert](https://stellar.expert)
-
-## Parte 2
-
-<YouTube ID="u204TwiHJpE" />
-
-En esta reunión del protocolo, discutimos dos Propuestas de Avance Clave: Dima está presentando CAP-0068 y CAP-0069, ambas añaden nuevas funciones de host.
-
-Aquí hay algunos recursos para leer:
-
-- [CAP-0068](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0068.md)
-
-- [Discusión sobre CAP-0068](https://github.com/stellar/stellar-protocol/discussions/1626)
-
-- [CAP-0069](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0069.md)
-
-- [Discusión sobre CAP-0069](https://github.com/stellar/stellar-protocol/discussions/1633)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-02-20.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-02-20.mdx
deleted file mode 100644
index 3778b17e15..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-02-20.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: 2025-02-20
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Parte 1
-
-<YouTube ID="2XVt87tG5LI" />
-
-Elliot Voris, defensor del SDF, da una introducción al proyecto KaleFail y cubre cómo se desarrolló, su propósito y características futuras. KaleFail se basa en el proyecto KALE de Kalepail y ambos sirven como aplicaciones de demostración totalmente desarrolladas, mostrando características clave de Stellar/Soroban.
-
-Enlaces:
-
-- [KaleFail](https://kalefail.elliotfriend.com)
-
-- [Código Fuente](https://github.com/elliotfriend/project-kalefail)
-
-- [KALE](https://kalepail.com/kale)
-
-## Parte 2
-
-<YouTube ID="hDIP22z6nq4" />
-
-En esta reunión del protocolo, se discute una Propuesta de Avance Central - Siddharth Suresh presentará las actualizaciones del memorándum relacionadas con CAP-0067.
-
-Aquí hay algunos recursos para leer:
-
-- [CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-
-- [Discusión](https://github.com/stellar/stellar-protocol/discussions/1553)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-02-27.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-02-27.mdx
deleted file mode 100644
index b4eb1c021d..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-02-27.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 2025-02-27
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Parte 1
-
-<YouTube ID="hfl1n5BKbs4" />
-
-Blend, un protocolo de liquidez universal desarrollado en Stellar/Soroban, se está preparando para lanzar la V2 y lanzó la competencia de Auditoría de Blend V2 + Verificación Formal de Certora el pasado lunes. Hay $125K en USDC disponibles, y el equipo se está uniendo a la reunión de esta semana para hablar sobre la competencia y revisar algo de código. ¡Únete para aprender más sobre Blend y la competencia!
-
-Enlaces:
-
-- [Blend](https://www.blend.capital)
-
-- [Competencia](https://code4rena.com/audits/2025-02-blend-v2-audit-certora-formal-verification)
-
-## Parte 2
-
-<YouTube ID="9oCKAhbFzUY" />
-
-En esta reunión del protocolo se discuten los prototipos de Dima y Leigh para manejar memos/cuentas muxed en CAP-0067, así como actualizaciones a CAP-0066 (Recurso de Lectura en Memoria de Soroban).
-
-Enlaces:
-
-- [CAP-0066](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md)
-
-- [Discusión de CAP-0066](https://github.com/stellar/stellar-protocol/discussions/1585)
-
-- [CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-
-- [Discusiones de CAP-0067](https://github.com/stellar/stellar-protocol/discussions/1553#discussioncomment-12306846) y [Discusiones de CAP-0067](https://github.com/stellar/stellar-protocol/discussions/1553#discussioncomment-12309408)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-03-06.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-03-06.mdx
deleted file mode 100644
index 615712afa2..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-03-06.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: 2025-03-06
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="e_DH9zIRnu8" />
-
-En esta reunión, tenemos una conversación con Christian Santagata de OpenZeppelin sobre la asociación multi-año entre Stellar y OpenZeppelin, y hablamos sobre en qué está trabajando el equipo en el ecosistema de Stellar. La conversación incluye temas sobre los contratos de token de Stellar y estándares de token, y cómo utilizar el OpenZeppelin Contract Wizard que ahora admite los contratos de Stellar.
-
-Enlaces:
-
-- [OpenZeppelin Contract Wizard](https://wizard.openzeppelin.com/stellar)
-
-- [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts)
-
-- [Dev Walkthrough](https://www.youtube.com/watch?v=iD7ZspsZLVo)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-03-27.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-03-27.mdx
deleted file mode 100644
index 17c9add7fc..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-03-27.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: 2025-03-27
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-## Parte 1
-
-<YouTube ID="zqrE4mWNog0" />
-
-Nos estamos reuniendo nuevamente con el equipo de OpenZeppelin para ponernos al día sobre las últimas adiciones de características, y esta vez hemos invitado a dos de sus ingenieros, Boyan Barakov y Ozgun Ozerk, para responder preguntas técnicas de la audiencia.
-
-Enlaces:
-
-- [OpenZeppelin Contract Wizard](https://wizard.openzeppelin.com/stellar)
-
-- [OpenZeppelin Stellar Contracts](https://github.com/OpenZeppelin/stellar-contracts)
-
-- [Dev Walkthrough](https://www.youtube.com/watch?v=iD7ZspsZLVo)
-
-## Parte 2
-
-<YouTube ID="2q3NlmrtmQg" />
-
-Esta es una breve reunión protocolaria, haciendo seguimiento de discusiones previas.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-04-03.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-04-03.mdx
deleted file mode 100644
index 57ce60f8db..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-04-03.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: 2025-04-03
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="ea2fTBiLvoM" />
-
-Primero echamos un vistazo a Stellar Lab, se han añadido muchas características y mejoras desde que hicimos una presentación de Stellar Lab el año pasado. Stellar Lab es una herramienta poderosa para todos los que desarrollan en Stellar.
-
-Estamos buscando comentarios de la comunidad sobre el SEP de Contratos Actualizables, y presentaremos los detalles de esta propuesta.
-
-Enlaces:
-
-- [Stellar Lab](https://lab.stellar.org)
-
-- [Contratos Actualizables SEP](https://github.com/stellar/stellar-protocol/pull/1671)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-04-10.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-04-10.mdx
deleted file mode 100644
index 89a65351af..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-04-10.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: 2025-04-10
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="346G-EQ8ScY" />
-
-Pamphile (más conocido como tupui) es un ingeniero de software senior que trabaja en Bitpanda. Anteriormente trabajó en el equipo que desarrolló Flight Simulator 2020 y creó una empresa de consultoría para trabajar en software de código abierto.
-
-Ahora está desarrollando su proyecto llamado Tansu en la blockchain Stellar. Tansu es un sistema descentralizado que busca asegurar la cadena de suministro de software y romper las comunidades aisladas mediante el uso de una DAO.
-
-Enlace:
-
-- [Tansu](https://tansu.dev)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-04-17.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-04-17.mdx
deleted file mode 100644
index c003d2db03..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-04-17.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: 2025-04-17
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="7O4tOSn_UFc" />
-
-Esta semana profundizaremos en una de las herramientas más subestimadas: Quickstart.
-
-Quickstart es un entorno local de red Stellar (nodo) que permite a los desarrolladores ejecutar una versión local de la red Stellar para desarrollo y pruebas.
-
-Conoce Quickstart, descubre cómo instalarlo y cómo desplegar la aplicación de ejemplo Hello World en Quickstart.
-
-Enlace:
-
-- [Inicio rápido de Stellar](/docs/tools/quickstart)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-05-01.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-05-01.mdx
deleted file mode 100644
index 50774f255a..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-05-01.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: 2025-05-01
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-import YouTube from "@site/src/components/YouTube";
-
-<YouTube ID="fuX07T1HUf0" />
-
-Estamos cerca de completar la implementación de Whisk, los CAPs del Protocolo 23, el siguiente paso en el ciclo de vida de los CAP es la votación por el equipo Core CAP. En esta reunión del protocolo se proporcionó una actualización sobre los CAPs y se respondieron las preguntas finales de la comunidad.
-
-Consulta los CAPs aquí:
-
-[CAP-0062](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md) - [Discusión](https://github.com/orgs/stellar/discussions/1575)
-
-[CAP-0063](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0063.md) - [Discusión](https://github.com/orgs/stellar/discussions/1602)
-
-[CAP-0065](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0065.md) - [Discusión](https://github.com/orgs/stellar/discussions/1615)
-
-[CAP-0066](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md) - [Discusión](https://github.com/orgs/stellar/discussions/1585)
-
-[CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) - [Discusión](https://github.com/orgs/stellar/discussions/1553)
-
-[CAP-0068](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0068.md) - [Discusión](https://github.com/orgs/stellar/discussions/1626)
-
-[CAP-0069](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0069.md) - [Discusión](https://github.com/orgs/stellar/discussions/1633)
-
-[CAP-0070](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0070.md) - [Discusión](https://github.com/orgs/stellar/discussions/1719)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-05-22.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-05-22.mdx
deleted file mode 100644
index fd5ab1cbe4..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-05-22.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: 2025-05-22
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/UT8XXdcssQ8?si=xqTaXdr7VX9TWrOb"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta Reunión para desarrolladores de Stellar tenemos una charla con Bram Hoogenkamp de OpenZeppelin sobre OpenZeppelin Monitor, que proporciona monitoreo y alertas para contratos inteligentes.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-07-10.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-07-10.mdx
deleted file mode 100644
index 8c83b574ed..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-07-10.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: 2025-07-10
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/0syGaIn3ULk?si=0JFUrQiBqQHl59dC"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta llamada, recibimos una actualización sobre el emocionante proyecto Scaffold Stellar presentado por Fifo de Aha Labs.
-
-Scaffold Stellar es una excelente forma de acelerar nuevos proyectos desarrollados en Stellar. Incluye contratos inteligentes iniciales, frontend, plugins y herramientas integradas.
-
-[Repositorio Scaffold Stellar](https://github.com/theahaco/scaffold-stellar)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-07-17.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-07-17.mdx
deleted file mode 100644
index 42d7672d81..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-07-17.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: 2025-07-17
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/RNtqou5oaeE?si=mqiGrkXw7QabNgS4"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta reunión, el equipo de Nomyx nos introducirá a su avanzada arquitectura de contratos inteligentes (una implementación del Patrón Diamond) y a la interfaz de visualización proxy Diamond de Nomyx, que facilita la inspección de los diamonds desplegados y los hace un poco más fáciles de manejar.
-
-También mostrarán una instancia en vivo del despliegue del estándar proxy diamond actualmente usado para la plataforma Nomyx, que elimina las limitaciones relacionadas con el límite superior de tamaño del contrato, permitiendo a los desarrolladores lanzar productos complejos.
-
-[Sitio web de Nomyx](https://www.nomyx.io)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-07-24.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-07-24.mdx
deleted file mode 100644
index 7de0a312be..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-07-24.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: 2025-07-24
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/mSABuOLuZs8?si=FLbBbKJzXP8uo_U6"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta reunión estamos hablando con Esteban y Francisco de PaltaLabs. Stellar Hacks está actualmente realizando un hackathon en colaboración con PaltaLabs, donde el objetivo es crear usando sus proyectos Soroswap y DeFindex.
-
-Veamos cómo va el hackathon y algunos consejos si aún estás considerando participar, ¡todavía hay tiempo para entrar!
-
-Enlaces:
-
-- [Hackathon](https://dorahacks.io/hackathon/stellar-hacks-paltalabs/detail)
-- [Soroswap](https://docs.soroswap.finance)
-- [DeFindex](https://docs.defindex.io)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-08-07.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-08-07.mdx
deleted file mode 100644
index ef66629753..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-08-07.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: 2025-08-07
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/EuAUCfAWg-4?si=qnw6St8rMuWi0ON0"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta reunión hablamos con Brieuc Berruet, fundador de Flashback, quien participó en el programa de incubadora DraperU x Stellar el año pasado, para obtener una actualización sobre su proyecto (¡spoiler: está en vivo!).
-
-¡Conoce más sobre el proyecto y mira una demostración genial!
-
-[Sitio web de Flashback](https://www.flashback.tech)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-09-25.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-09-25.mdx
deleted file mode 100644
index 8d9a050ea0..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-09-25.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: 2025-09-25
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/bTiFz8VHQyQ?si=vyKk8df223kTpFKD"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En la reunión de desarrolladores de Stellar de esta semana, discutimos nuevas Propuestas de Avance del Core.
-
-Aquí tienes algunos recursos para leer:
-
-[CAP-0071](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0071.md) - [Discusión](https://github.com/orgs/stellar/discussions/1784)
-
-[CAP-0072](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0072.md) - [Discusión](https://github.com/orgs/stellar/discussions/1763)
-
-[CAP-0073](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0073.md) - [Discusión](https://github.com/orgs/stellar/discussions/1668)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-10-02.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-10-02.mdx
deleted file mode 100644
index 6b3117566b..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-10-02.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: 2025-10-02
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/8UmxYfDkWLg?si=Q6Q6jXD7KDlNaHvg"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta reunión discutiremos las funciones hash CAP-74, BN254 y Poseidon.
-
-[CAP-0074](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0074.md) - [Discusión](https://github.com/orgs/stellar/discussions/1780)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-10-09.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-10-09.mdx
deleted file mode 100644
index 2901f84790..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-10-09.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 2025-10-09
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/-uTKQIQpwAU?si=DTtCDBLTqhmeAu_W"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-## Demostración del Generador de interfaz de usuario de OpenZeppelin
-
-Nos reunimos nuevamente con el equipo de OpenZeppelin para ponernos al día con las últimas herramientas para desarrolladores que están creando.
-
-Esta vez Steve demostrará UI Builder, una manera fácil de crear una interfaz para cualquier llamada de contrato en segundos. UI Builder te permite seleccionar una función y luego genera automáticamente una interfaz React con conexión a billeteras y soporte para múltiples redes, y exporta una aplicación completa.
-
-[Generador de interfaz de usuario de OpenZeppelin](https://builder.openzeppelin.com)
-
-<iframe
-  src="https://www.youtube.com/embed/rWWB7-8A-g8?si=k0uAjapexNwHyAJV"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-## Discusión del protocolo
-
-En esta discusión de la Propuesta de Avance Central CAP-0075 (Funciones host para habilitar las funciones hash Poseidon y Poseidon2) es presentada.
-
-Esta CAP propone agregar funciones host para primitivas criptográficas que habilitan la familia de funciones hash Poseidon, que son elecciones de hash ampliamente admitidas en sistemas eficientes de prueba de conocimiento cero. Admitir estas funciones como host en Soroban puede facilitar la adopción de aplicaciones ZK e interoperabilidad con otros ecosistemas.
-
-Enlace a [CAP-0075](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0075.md)
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-10-16.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-10-16.mdx
deleted file mode 100644
index 00596a619b..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-10-16.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: 2025-10-16
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/cafR1uVsPFM?si=b-zLh8FWAu5cFUs_"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-## Discusión del protocolo
-
-En esta llamada se analiza la reciente incidencia de archivado de estado, introducida por Whisk (Protocolo 23). También se responden preguntas de constructores de la comunidad.
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-10-23.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-10-23.mdx
deleted file mode 100644
index 4b13b29135..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-10-23.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: 2025-10-23
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/-nY8U8nNmas?si=Sr9czITnAYgDaSAI"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta reunión hablamos con Dobprotocol para aprender más sobre cómo utilizan Stellar para crear una plataforma única, convirtiendo máquinas en activos invertibles.
-
-Sitio web: https://www.dobprotocol.com
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-10-30.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-10-30.mdx
deleted file mode 100644
index dae4eab8de..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-10-30.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: 2025-10-30
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/nxU16dOjN3M?si=c6fSyGCPUceFiBxY"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta reunión continuamos nuestra mini serie sobre las herramientas de código abierto basadas en Stellar que OpenZeppelin está desarrollando. En la sesión anterior hablamos brevemente sobre Relayer y esta vez profundizamos en esta herramienta y en OpenZeppelin Managed Service.
-
-OpenZeppelin Relayer: https://docs.openzeppelin.com/relayer
diff --git a/i18n/es/docusaurus-plugin-content-blog/2025-11-06.mdx b/i18n/es/docusaurus-plugin-content-blog/2025-11-06.mdx
deleted file mode 100644
index 3d5e6048ec..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/2025-11-06.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: 2025-11-06
-authors: carstenjacobsen
-tags:
-  - developer
----
-
-<iframe
-  src="https://www.youtube.com/embed/-T3Ia32nnP0?si=k1msvUWzT5v1L3Ws"
-  width="640"
-  height="480"
-  allow="autoplay"
-></iframe>
-
-En esta reunión hacemos un recorrido por las versiones Q3 de la biblioteca de OpenZeppelin para Smart Account, Vault y RWA.
-
-Enlaces a la documentación:
-
-- Smart Account: https://docs.openzeppelin.com/stellar-contracts/accounts/smart-account
-- Vault: https://docs.openzeppelin.com/stellar-contracts/tokens/vault/vault
-- RWA: https://docs.openzeppelin.com/stellar-contracts/tokens/rwa/rwa
diff --git a/i18n/es/docusaurus-plugin-content-blog/authors.yml b/i18n/es/docusaurus-plugin-content-blog/authors.yml
deleted file mode 100644
index 88a9843e26..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/authors.yml
+++ /dev/null
@@ -1,51 +0,0 @@
-carstenjacobsen:
-  name: Carsten Jacobsen
-  title: Defensor Senior de Desarrolladores
-  url: https://github.com/carstenjacobsen
-  image_url: https://github.com/carstenjacobsen.png
-  page: true
-  socials:
-    github: carstenjacobsen
-    x: CarstenJacobsen
-    linkedin: carstenjacobsendk
-elliotfriend:
-  name: Elliot Voris
-  title: Defensor Principal de Desarrolladores
-  url: https://github.com/ElliotFriend
-  image_url: https://github.com/ElliotFriend.png
-  page: true
-  socials:
-    github: ElliotFriend
-    x: ElliotFriend
-    linkedin: elliotfriend
-kalepail:
-  name: Tyler van der Hoeven
-  title: Director Defensor de Desarrolladores
-  url: https://github.com/kalepail
-  image_url: https://github.com/kalepail.png
-  page: true
-  socials:
-    github: kalepail
-    x: kalepail
-    linkedin: tyvdh
-anataliocs:
-  name: Chris Anatalio
-  title: Defensor Senior de Desarrolladores
-  url: https://github.com/anataliocs
-  image_url: https://github.com/anataliocs.png
-  socials:
-    github: anataliocs
-naman:
-  name: Naman Kumar
-  title: Gerente de Producto
-  url: https://github.com/namankumar
-  image_url: https://github.com/namankumar.png
-  socials:
-    github: namankumar
-julian:
-  name: Julian Martinez
-  title: Defensor Senior de Desarrolladores
-  url: https://github.com/Julian-dev28
-  image_url: https://github.com/Julian-dev28.png
-  socials:
-    github: Julian-dev28
diff --git a/i18n/es/docusaurus-plugin-content-blog/options.json b/i18n/es/docusaurus-plugin-content-blog/options.json
deleted file mode 100644
index 125a640bf3..0000000000
--- a/i18n/es/docusaurus-plugin-content-blog/options.json
+++ /dev/null
@@ -1,14 +0,0 @@
-{
-  "title": {
-    "message": "Notas de reunión",
-    "description": "The title for the blog used in SEO"
-  },
-  "description": {
-    "message": "Notas y grabaciones de las reuniones del protocolo Soroban y los desarrolladores",
-    "description": "The description for the blog used in SEO"
-  },
-  "sidebar.title": {
-    "message": "Todas las reuniones",
-    "description": "The label for the left sidebar"
-  }
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current.json b/i18n/es/docusaurus-plugin-content-docs-ap/current.json
deleted file mode 100644
index f31d2bf4d9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current.json
+++ /dev/null
@@ -1,70 +0,0 @@
-{
-  "version.label": {
-    "message": "Siguiente",
-    "description": "The label for version current"
-  },
-  "sidebar.anchor_platform.category.Anchor Platform": {
-    "message": "Anchor Platform",
-    "description": "The label for category Anchor Platform in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Admin Guide": {
-    "message": "Guía del administrador",
-    "description": "The label for category Admin Guide in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Custody Services": {
-    "message": "Servicios de custodia",
-    "description": "The label for category Custody Services in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Fireblocks": {
-    "message": "Fireblocks",
-    "description": "The label for category Fireblocks in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Event Handling": {
-    "message": "Manejo de eventos",
-    "description": "The label for category Event Handling in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.API Reference": {
-    "message": "Referencia de API",
-    "description": "The label for category API Reference in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Platform Server": {
-    "message": "Servidor de la plataforma",
-    "description": "The label for category Platform Server in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Transactions": {
-    "message": "Transacciones",
-    "description": "The label for category Transactions in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.JSON-RPC API": {
-    "message": "API JSON-RPC",
-    "description": "The label for category JSON-RPC API in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Methods": {
-    "message": "Métodos",
-    "description": "The label for category Methods in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Callbacks Server": {
-    "message": "Servidor de callbacks",
-    "description": "The label for category Callbacks Server in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Custody Server": {
-    "message": "Servidor de custodia",
-    "description": "The label for category Custody Server in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.SEP Guides": {
-    "message": "Guías SEP",
-    "description": "The label for category SEP Guides in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Hosted Deposits and Withdrawals (SEP-24)": {
-    "message": "Depósitos y retiradas de fondos alojados (SEP-24)",
-    "description": "The label for category Hosted Deposits and Withdrawals (SEP-24) in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Programmatic Deposits and Withdrawals (SEP-6)": {
-    "message": "Depósitos y retiradas de fondos programáticos (SEP-6)",
-    "description": "The label for category Programmatic Deposits and Withdrawals (SEP-6) in sidebar anchor_platform"
-  },
-  "sidebar.anchor_platform.category.Cross-Border Payments (SEP-31)": {
-    "message": "Pagos transnacionales (SEP-31)",
-    "description": "The label for category Cross-Border Payments (SEP-31) in sidebar anchor_platform"
-  }
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/CONTRIBUTING.md b/i18n/es/docusaurus-plugin-content-docs-ap/current/CONTRIBUTING.md
deleted file mode 100644
index bda127cb9b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/CONTRIBUTING.md
+++ /dev/null
@@ -1,251 +0,0 @@
----
-draft: true
----
-
-# Bienvenido a Anchor Platform Madness <!-- omit in toc -->
-
-¡Hola y bienvenido al hogar de la documentación de Anchor Platform recientemente versionado!
-
-Estamos muy contentos de tenerte aquí, y esperamos que este documento te ayude a entender cómo (y lo más importante, _donde_) hacer los cambios necesarios en nuestra documentación. Comencemos con un poco de vocabulario de Docusaurus, ¿te parece?
-
-## ¡AVISO! AP HA SIDO DESVERSIONADO
-
-La documentación de Anchor Platform ha sido desversionada, y a partir de ahora solo mantenemos una versión "actual" de los documentos. Por lo tanto, cualquier cosa en esta página que haga referencia a crear una nueva versión, actualizar versiones antiguas, etc., puede ser ignorada.
-
-Sin embargo, los documentos de Anchor Platform _todavía_ permanecen en su propia instancia de docusaurus. Así que la información aquí sobre vinculación entre/entre instancias sigue siendo relevante. (Esto no será así para siempre, pero por ahora, lo es.)
-
-## Resumen
-
-- Para versiones _no publicadas_ de Anchor Platform:
-  - Agrega y edita documentos en `/platforms/anchor-platform`
-  - Actualiza y regenera la documentación de la API en `/openapi/anchor-platform/main-*.yaml`
-- Para versiones _publicadas_ de Anchor Platform:
-  - Actualiza y cambia documentos en `/ap_versioned_docs`
-  - Actualiza y regenera la documentación de la API en `/openapi/anchor-platform/versions/*.yaml`
-
-Publica una **nueva versión** usando el siguiente script de yarn:
-
-```bash
-# replace `3.0.0` with the needed version
-VERSION=3.0.0 yarn ap:versions:new
-```
-
-> _Nota:_ Creo que el comando de yarn anterior es actualmente incompatible con Windows, aunque podría estar equivocado.
-
-Regenera la documentación de la API para versiones **ya publicadas** usando el siguiente script de yarn. Esto regenera la documentación de la API para **todas** las versiones publicadas, así que puede que quieras ser juicioso sobre qué archivos añades a tu commit.
-
-```bash
-yarn ap:versions:regen
-```
-
-## Tabla de Contenidos <!-- omit in toc -->
-
-- [¡AVISO! AP HA SIDO DESVERSIONADO](#notice-ap-has-been-de-versioned)
-- [Resumen](#tldr)
-- [Más sobre Docusaurus de lo que nunca quisiste saber](#more-about-docusaurus-than-you-ever-wanted-to-know)
-  - [Nomenclatura de Versiones](#versions-nomenclature)
-  - [Plugins](#plugins)
-  - [Instancias](#instances)
-  - [Enlaces](#links)
-    - [Ejemplos](#examples)
-- [Directorios para Conocer](#directories-to-know)
-  - [Directorios que Ya Conoces](#directories-you-already-know-about)
-  - [Nuevos Directorios](#new-shiny-directories)
-- [Crear Nuevas Versiones](#making-new-versions)
-  - [Usar Docusaurus para "Etiquetar" un Nueva Publicación](#use-docusaurus-to-tag-a-new-release)
-  - [Configurar el plugin OpenAPI](#configure-the-openapi-plugin)
-    - [Copiar los archivos de especificación OpenAPI (agrupados) al directorio versionado](#copy-the-bundled-openapi-specfiles-to-the-versioned-directory)
-    - [Agregar configuración a la instancia del plugin OpenAPI](#add-configuration-to-the-openapi-plugin-instance)
-- [Actualizar Versiones Antiguas](#updating-old-versions)
-  - [Actualizar Páginas de Documentación](#update-documentation-pages)
-  - [Actualizar Especificación de API](#update-api-specification)
-
-## Más sobre Docusaurus de lo que nunca quisiste saber
-
-Sé que puede parecer un poco misterioso, pero aquí tienes algo de conocimiento y contexto para ayudarte a entender lo que está por venir.
-
-### Nomenclatura de Versiones
-
-Así es como Docusaurus define estos términos, así que eso es lo que usaré en este documento también.
-
-- La **versión actual** se refiere a la versión de los documentos de AP contenidos en el directorio `/platforms/anchor-platform`. Este conjunto de documentos está disponible en la URL `/platforms/anchor-platform/next`. Este es el conjunto de documentos "en construcción". Este es el conjunto de documentos "en construcción".
-
-- La **última versión** se refiere al conjunto de documentos de AP que ha sido "publicado" más recientemente. Estos se encuentran en `/ap_versioned_docs` (más sobre eso más adelante), y está disponible en la URL `/platforms/anchor-platform`. Este es el conjunto de documentos "estables". Este es el conjunto de documentos "estables".
-
-### Plugins
-
-Hay dos plugins de Docusaurus en juego aquí:
-
-1. `@docusaurus/plugin-content-docs` es el caballo de batalla de Docusaurus. Se encarga del renderizado de markdown, enrutamiento, etc. Cuando piensas en actualizar `some-file.mdx`, este es el plugin que estás utilizando.
-2. `docusaurus-plugin-openapi-docs` es el plugin que se utiliza para generar páginas MDX a partir de los archivos de especificación de OpenAPI. Este plugin es capaz de versionar por sí mismo, aunque se debe tener cuidado y consideración con respecto a su configuración.
-
-Ambas configuraciones de plugins se han separado en un archivo `/config/anchorPlatform.config.ts`, para facilitar su gestión y despejar un poco el archivo principal `docusaurus.config.ts`.
-
-### Instancias
-
-Aquí es donde se pone un poco más "profundo", pero prometo que esta parte es útil de conocer. Ambos [plugins](#plugins) que mencioné anteriormente son realmente solo _instancias_ de esos dos plugins. De hecho, cada uno de esos plugins se utiliza en otras partes de nuestro sitio de documentación para Horizon, SDP, y simplemente documentación "regular". No es _generalmente_ importante considerar diferentes instancias de plugins, pero _sí_ es **bastante relevante** cuando discutimos enlaces. Así que...
-
-### Enlaces
-
-La mayoría de las veces, **especialmente en documentos versionados**, es importante [enlazar a otros documentos por _rutas de archivos relativas_](https://docusaurus.io/docs/versioning#link-docs-by-file-paths).
-Esto permite a Docusaurus reescribir URLs cuando sea necesario en el momento de la construcción.
-
-¡Sin embargo, hay una **GRAN EXCEPCIÓN**! Docusaurus solo puede manejar estos enlaces cuando ambos, los archivos fuente y destino, son procesados por la misma _instancia de plugin_.
-Así que, en términos prácticos:
-
-- Si estás enlazando desde **y** hacia documentos MDX _dentro_ de la misma instancia de plugin de documentos, usa _rutas de archivos relativas_.
-- Si estás enlazando _a través_ de instancias de plugins, **debes** usar _rutas URL_. Por convención, también usamos _rutas absolutas_ para esto, para que sea un poco más obvio cuándo está ocurriendo este comportamiento.
-
-#### Ejemplos
-
-Esto debería ayudarte a aclarar un poco.
-
-- Quiero enlazar _desde_ el documento MDX
-  `/platforms/anchor-platform/sep-guide/sep6/configuration.mdx` _hacia_ el documento MDX
-  `/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx`:
-  - Estamos en la misma instancia de plugin `/platforms/anchor-platform`
-  - Usa una _ruta de archivo relativa_
-  - Enlaza a ella `[algo como esto](../../api-reference/platform/rpc/methods/notify_amounts_updated.mdx)`
-- Quiero enlazar _desde_ el documento MDX `/docs/learn/fundamentals/anchors.mdx` _hasta_ el documento MDX `/platforms/anchor-platform/admin-guide/getting-started.mdx`
-  - Estamos "cruzando" entre las instancias de plugin `/docs` y `/platforms/anchor-platform`
-  - Usa una ruta de URL **absoluta**
-  - Enlaza a ella `[algo como esto](/platforms/anchor-platform/admin-guide/getting-started)` (nota que no hay extensión `.mdx`)
-- Quiero vincular _desde_ el documento MDX `/platforms/anchor-platform/README.mdx` _a_ el documento MDX `/docs/tools/developer-tools/wallets.mdx`
-  - Estamos "cruzando" entre las instancias de plugin `/platforms/anchor-platform` y `/docs`
-  - Usa una _ruta URL absoluta_
-  - Enlaza a ella `[algo como esto](/docs/tools/developer-tools/wallets)` (nota que no hay extensión `.mdx`)
-- ¡Wildcard! Quiero vincular _desde_ el documento MDX `/platforms/anchor-platform/admin-guide/events/configuration.mdx` _a_ el documento MDX `/platforms/stellar-disbursement-platform/admin-guide/60-anchor-platform-integration-points.mdx`
-  - Estamos "cruzando" entre las instancias de plugin `/platforms/anchor-platform` y `/platforms/stellar-disbursement-platform`
-  - Usa una _ruta URL absoluta_
-  - Enlaza a ella `[algo como esto](/platforms/stellar-disbursement-platform/admin-guide/anchor-platform-integration-points)` (nota que no hay extensión `.mdx`)
-
-> _Nota:_ Reemplaza la instancia del plugin `/platforms/anchor-platform` con la instancia del plugin `/platforms/stellar-disbursement-platform` en los ejemplos anteriores, y todo funcionará prácticamente igual.
-
-Lee más sobre enlaces [aquí](https://docusaurus.io/docs/markdown-features/links) (especialmente hacia la parte inferior de la página).
-
-## Directorios a Conocer
-
-Hay varios directorios que _todos_ alimentan el producto final que es nuestra documentación versionada de AP.
-
-### Directorios que Ya Conoces
-
-- `/platforms/anchor-platform` Aquí es donde estás ahora, y tradicionalmente ha sido el lugar para modificar cualquier contenido de markdown que se convierte en nuestras páginas de documentación de AP. No ha cambiado mucho aquí, excepto que requiere un cambio de mentalidad.
-  **Toda la documentación y contenido ubicado aquí ahora debe considerarse la versión `actual` (en construcción) de los documentos de AP.** Así que, mientras construimos para `v3.x` (y más allá, finalmente), querrás actualizar _contenido aquí_.
-  Los lectores aún podrán _ver_ este contenido antes de que sea "publicado", pero se les dirá que es la versión no publicada.
-
-  También hay un nuevo directorio aquí que debes conocer:
-
-  - `/platforms/anchor-platform/assets` Dado que es probable que las diversas imágenes, diagramas, etc. necesiten actualizarse/cambiarse de una versión a otra, estamos co-localizando los activos relevantes en este directorio. Esto permite que también sean versionados. Esto permite que también sean versionados. Si quieres actualizar un diagrama o imagen para una próxima publicación, debes hacerlo aquí.
-
-- `/openapi/anchor-platform` Este es el mismo lugar que probablemente ya conoces. Los archivos han sido renombrados recientemente, pero en su mayor parte querrás modificar `main-{platform,callbacks,custody}.yaml`, que luego se "agrupará" más tarde en el archivo agrupado que contiene todo en un solo archivo.
-  **Los archivos en este directorio también deben considerarse la versión `actual` (en construcción) de los documentos de especificación de AP.** Así que, mientras construimos para `v3.x` (y más allá, finalmente), querrás actualizar _archivos de especificación aquí_.
-
-  También hay un nuevo directorio aquí que debes conocer:
-
-  - `/openapi/anchor-platform/versions` Este directorio almacena una copia de los archivos de especificación _agrupados_ para cada versión que se publica. El plugin que usamos para generar la documentación de la API para estos archivos de especificación se configura para utilizar _estas_ especificaciones versionadas para toda la documentación no `actual`.
-
-- `/openrpc/src/anchor-platform` Recientemente, movimos la especificación RPC a este directorio para que pueda beneficiarse de los mismos procesos de construcción y cheques de validación que la especificación `stellar-rpc`. Similar a los otros directorios cubiertos hasta ahora, cualquier cambio en estos archivos debe considerarse en la versión `actual` (en construcción) de la documentación. No hay (¿aún?) una gran cantidad de herramientas o ergonomía en torno a la actualización de las versiones "antiguas" de estas especificaciones. La versión `actual` de la especificación se genera en `/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json`.
-  Esto significa que _sí_ se incluye en el proceso de versionado, por lo que cualquier cambio en las versiones "antiguas" probablemente solo necesitará hacerse en esos archivos de especificación versionados por ahora (más sobre eso en la siguiente sección).
-
-### Nuevos Directorios Brillantes
-
-- `/ap_versioned_sidebars` Podemos pasar rápidamente por este. Cuando haces una nueva versión de los documentos, Docusaurus guarda una copia de la barra lateral en ese momento. Realmente no deberías preocuparte por nada aquí.
-
-- `/ap_versioned_docs` Aquí es donde residen los conjuntos "publicados" de los documentos de AP.
-  Cada vez que se publica una versión, _todo_ desde el directorio `/platforms/anchor-platform` se copia en un subdirectorio aquí.
-  Notarás que ya tenemos una versión `v2.8.4` aquí. A medida que publiquemos `v3.x`, se colocará una _nueva_ copia de los archivos aquí. La copia `más reciente` (estable) de la documentación de AP se extrae del directorio. Si te encuentras con algo que corregir o actualizar en una versión publicada de los documentos, necesitarás actualizarlo en consecuencia aquí.
-
-## Crear Nuevas Versiones
-
-Como se mencionó en el [TL;DR](#tldr), este proceso está automatizado con el script `VERSION=3.0.0 yarn ap:versions:new`. Sin embargo, aquí está lo que está sucediendo bajo el capó de ese script.
-
-### Usar Docusaurus para "Etiquetar" una Nueva Publicación
-
-¡Es realmente bastante simple! Usa el CLI de Docusaurus para hacer una nueva publicación:
-
-```bash
-# `ap` is the ID of the AP `@docusaurus/plugin-content-docs` plugin instance
-yarn docusaurus docs:version:ap 3.0.0
-```
-
-Eso hace una nueva copia de los documentos en `/ap_versioned_docs`, y funcionará bastante bien para mostrar la nueva versión en el sitio. Cualquier cambio futuro en la versión 3.0.0 de los documentos debería hacerse en el directorio `/ap_versioned_docs`.
-
-### Configurar el plugin OpenAPI
-
-También querrás poder modificar/actualizar/regenerar la documentación de la API si surge la necesidad. Así que, necesitaremos configurar la instancia del plugin `docusaurus-plugin-openapi-docs` en consecuencia.
-
-#### Copiar los archivos de especificación OpenAPI (agrupados) al directorio versionado
-
-En este momento, es tan simple como copiar los archivos:
-
-```bash
-cp openapi/anchor-platform/bundled-platform.yaml openapi/anchor-platform/versions/platform-3.0.0.yaml
-cp openapi/anchor-platform/bundled-callbacks.yaml openapi/anchor-platform/versions/callbacks-3.0.0.yaml
-cp openapi/anchor-platform/bundled-custody.yaml openapi/anchor-platform/versions/custody-3.0.0.yaml
-```
-
-> Nota cómo estamos copiando el archivo _agrupado_, no el archivo _principal_. Esto asegura que el archivo versionado contenga todo lo que necesita.
-
-#### Agregar Configuración a la Instancia del Plugin OpenAPI
-
-> _Nota_: Estas partes de `versions` de la configuración ahora se generan dinámicamente, usando una función `makeVersions()`, por lo que estos pasos de configuración manual no deberían ser necesarios. Puede que desees avanzar/ajustar la cadena `anchorPlatformNextVersion` en el archivo de configuración, cuando publiques una nueva versión de los documentos, sin embargo.
-
-Para poder usar el CLI del plugin para actualizar versiones ya lanzadas,
-tenemos que actualizar la configuración en `/config/anchorPlatform.config.ts`. Haz
-a una nueva entrada en cada uno de los objetos `versions` de los archivos de especificación, y copia el formato
-de las entradas que ya están. Como referencia, así es como se ve actualmente
-para el "servidor de plataforma" en `v2.8.4`:
-
-```typescript
-ap_platform: {
-  specPath: "openapi/anchor-platform/bundled-platform.yaml",
-  outputDir: "platforms/anchor-platform/api-reference/platform/transactions",
-  hideSendButton: true,
-  template: "src/template.mustache",
-  version: "3.0.0",
-  label: "v3.0.0",
-  baseUrl: '/platforms/anchor-platform/next/api-reference/platform/transactions',
-  versions: {
-    "2.8.4": {
-      specPath: "openapi/anchor-platform/versions/platform-2.8.4.yaml",
-      outputDir: "ap_versioned_docs/version-2.8.4/api-reference/platform/transactions",
-      label: "v2.8.4",
-      baseUrl: "/platforms/anchor-platform/api-reference/platform/transactions"
-    }
-  }
-}
-```
-
-## Actualizar Versiones Antiguas
-
-### Actualizar Páginas de Documentación
-
-Supongamos que encuentro un error tipográfico en la documentación de la Guía de Administrador `v2.8.4`. Busca
-el archivo relevante en el directorio `/ap_versioned_docs/version-2.8.4`, corrígelo
-y haz un commit. Las actualizaciones de contenido son bastante fáciles aquí.
-
-> _Nota_ Dado que la especificación RPC se trata de manera similar a la documentación de MDX, usa el
-> mismo proceso para hacer actualizaciones en el archivo de especificación RPC. Para `v2.8.4`, se encuentra
-> aquí:
-> `/ap_versioned_docs/version-2.8.4/api-reference/platform/rpc/anchor-platform.openrpc.json`
-
-### Actualizar Especificación de API
-
-Esto es un poco más complicado, pero no mucho. Busca y cambia la(s)
-parte(s) relevante(s) del
-`/openapi/anchor-platform/versions/{platform, callbacks,custody}-2.8.4.yaml`
-specfile.
-
-Luego, regenera las páginas MDX:
-
-```bash
-# `ap-apis` is the ID of the AP `docusaurus-plugin-openapi-docs` plugin instance
-yarn docusaurus gen-api-docs:version -p ap-apis:2.8.4
-```
-
-> _Nota:_ Puedes usar un script de yarn para regenerar automáticamente la documentación de la API para
-> **todas** las versiones lanzadas: `yarn ap:versions:regen`. Esto realmente
-> regenera todas las versiones, así que es posible que quieras ser selectivo acerca de qué archivos
-> agregas al commit.
-
-Haz el commit de los cambios y estarás listo.
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/README.mdx
deleted file mode 100644
index 0f42b3e9e9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/README.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: "La Anchor Platform: Desarrollar y gestionar rampas de acceso y salida en la red Stellar"
-sidebar_position: 10
-sidebar_label: Descripción del producto
-description: Aprende cómo la Anchor Platform (AP) simplifica el proceso de desarrollar y gestionar una rampa de acceso y salida Stellar. Infórmate sobre cómo integrarte con la AP o obtén información de la API.
----
-
-# Anchor Platform
-
-La Plataforma Anchor ofrece un conjunto de herramientas y API para construir servicios de rampas de entrada y salida en la red Stellar. Con interfaces estandarizadas e implementaciones completas de propuestas clave del Ecosistema Stellar (SEPs), simplifica la integración con billeteras e intercambios basados en Stellar, permitiéndote centrarte en la lógica principal de tu negocio en lugar de en detalles de la implementación del protocolo.
-
-## SEPs compatibles
-
-La Plataforma Anchor implementa las siguientes Propuestas del Ecosistema Stellar:
-
-- **[SEP-1](sep-guide/sep1/README.mdx)** — Archivo Stellar.toml para el descubrimiento del servicio
-- **[SEP-6](sep-guide/sep6/README.mdx)** — Operaciones de depósito y retiro
-- **[SEP-10](sep-guide/sep10/README.mdx)** — Autenticación web usando transacciones de desafío/respuesta
-- **SEP-12** — Gestión de datos KYC/AML de clientes
-- **[SEP-24](sep-guide/sep24/README.mdx)** — Flujos interactivos de depósito y retiro
-- **[SEP-31](sep-guide/sep31/integration.mdx)** — Procesamiento de pagos transfronterizos (solo recepción)
-- **SEP-38** — Cotizaciones de precios y servicios de tasa de cambio
-- **[SEP-45](sep-guide/sep45/README.mdx)** — Autenticación web con desafíos/respuestas para cuentas de contrato
-
-## Características clave
-
-- **Implementaciones completas de SEP** — Soporte total para flujos de trabajo de depósito, retiro y procesamiento de pagos
-- **Autenticación y autorización** — Soporte de SEP-10 y SEP-45 para cuentas tradicionales y de contratos inteligentes
-- **Gestión de clientes** — Integración SEP-12 para cumplimiento KYC/AML y manejo de datos de clientes
-- **Procesamiento de transacciones** — Gestión completa del ciclo de vida de transacciones con seguimiento de estado y callbacks mediante webhook
-- **Servicios de cotización y cambio** — Integración SEP-38 para descubrimiento de precios y cálculo de tasas de cambio
-- **Soporte multi-activo** — Configuración flexible para múltiples activos con varios métodos de depósito y retiro
-- **Soporte para contratos inteligentes** — Soporte nativo para cuentas de contrato Stellar (cuentas C) mediante SEP-45
-
-## Enlaces de documentación
-
-- **[Arquitectura](./admin-guide/architecture.mdx)** — Arquitectura del sistema y descripción general de componentes
-- **[Comenzar](./admin-guide/getting-started.mdx)** — Instrucciones iniciales para configuración y despliegue
-- **[Manejo de eventos](./admin-guide/events/README.mdx)** — Entrega de eventos, webhooks y patrones de integración
-- **[Guías SEP](./sep-guide/README.mdx)** — Guías de implementación para Propuestas del Ecosistema Stellar
-- **[Referencia API](./api-reference/README.mdx)** — Documentación y referencia completa de la API
-
-## Recursos adicionales
-
-La documentación de la Plataforma Anchor está en desarrollo. Los desarrolladores son bienvenidos a explorar el código y la documentación existente en el [repositorio de GitHub](https://github.com/stellar/java-stellar-anchor-sdk).
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[sep-12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
-[anchor-platform-github]: https://github.com/stellar/java-stellar-anchor-sdk
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/README.mdx
deleted file mode 100644
index f5585941a5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Guía del Administrador
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Todo lo que necesitas saber sobre cómo configurar, ejecutar y usar la Anchor Platform.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/_category_.json b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/_category_.json
deleted file mode 100644
index 1d4401ab2f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/_category_.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
-  "label": "Admin Guide",
-  "collapsed": false
-}
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/architecture.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/architecture.mdx
deleted file mode 100644
index e877a82f75..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/architecture.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Arquitectura
-sidebar_position: 20
----
-
-## Arquitectura
-
-Antes de comenzar con la Anchor Platform, familiaricémonos con la arquitectura. Esta sección describirá los componentes involucrados y cómo interactúan.
-
-### Arquitectura Fundamental
-
-Los siguientes componentes arquitectónicos son requeridos para todas las implementaciones de la Anchor Platform.
-
-<div style={{width: '600px'}}>
-
-![fundamental anchor platform architecture](../assets/anchor-platform-architecture-1.png)
-
-</div>
-
-#### Cliente
-
-El cliente es una aplicación, como una billetera o un remitente de remesas, que actúa en nombre de un usuario y realiza solicitudes al sistema. Los clientes realizan solicitudes al componente del servidor SEP de la Anchor Platform utilizando conjuntos de estándares llamados [SEPs][seps] (Propuestas del Ecosistema Stellar).
-
-#### Servidor SEP
-
-El servidor SEP es un servidor orientado al cliente y, por lo tanto, necesita ser accesible desde una red externa. El servidor SEP procesa las solicitudes de los usuarios y gestiona el estado de las transacciones que inician. Cuando el servidor SEP necesita proporcionar información que no tiene al cliente, como la tasa de cambio para un par de activos o el estado de KYC de un cliente, realiza solicitudes síncronas [callback][callback-api] al servidor de negocio y retorna la información en un formato compatible con SEP.
-
-:::note
-
-El servidor SEP nunca almacenará información sensible, como KYC (PII), en la base de datos.
-
-:::
-
-#### Servidor de Negocios
-
-The business server is a service that you (the business) must implement to connect the Anchor Platform with your internal systems. El servidor de negocios responde a solicitudes de callback enviadas por el servidor SEP, como solicitudes de cotización, recibe eventos enviados por el servicio de eventos, como la notificación de un pago recibido a tu cuenta Stellar, y proporciona actualizaciones al servidor de plataforma cuando ocurren eventos fuera de la cadena, como la iniciación de una transferencia bancaria a un cliente.
-
-#### Servidor de Plataforma
-
-El servidor de plataforma es un componente interno. Debe ser alojado en una red privada y no debe ser accesible desde Internet. Este servidor permite al negocio recuperar y actualizar el estado de las transacciones utilizando su [API][platform-api].
-
-#### Base de Datos
-
-La Anchor Platform utiliza una base de datos PostgreSQL para almacenar eventos y entidades Stellar. Se utiliza principalmente para almacenar transacciones.
-
-#### Kafka
-
-Kafka se utiliza como el núcleo de mensajería para la Plataforma Anchor, facilitando la comunicación e interacciones impulsadas por eventos entre diferentes componentes. Permite que componentes como el servidor SEP, el servidor de negocios y el servicio de eventos publiquen y se suscriban a eventos de transacciones y pagos de manera confiable y escalable.
-
-### Arquitectura Completa
-
-Además de los componentes descritos anteriormente, la Anchor Platform incluye varios otros componentes que ofrecen funcionalidades adicionales. Tu negocio puede elegir cuáles de los componentes adicionales utilizar, pero el diagrama a continuación visualiza la arquitectura del sistema si se utilizan todos los componentes.
-
-<div style={{ width: "800px" }}>
-  [![complete anchor platform
-  architecture](../assets/anchor-platform-architecture-2.png)](../assets/anchor-platform-architecture-2.png)
-</div>
-#### Event Service
-
-El servicio de eventos permite a la Anchor Platform enviar webhooks HTTP a clientes registrados y a tu servidor de negocios cuando cambia el estado de las transacciones, eliminando la necesidad de que los clientes y/o tu servidor de negocios consulten las APIs de la Anchor Platform. Funciona leyendo eventos publicados en un tema de Kafka por los otros componentes de la Anchor Platform. [Lee más][events] sobre el uso del servicio de eventos. It works by reading events from published to a Kafka topic by the other Anchor Platform components. [Leer más][events] sobre el uso del servicio de eventos.
-
-#### Observador de Pagos
-
-El Observador de Pagos monitorea la blockchain Stellar usando Stellar RPC o Horizon, detecta automáticamente los pagos relacionados con el negocio y actualiza las transacciones correspondientes en la base de datos de la Plataforma Anchor. Si también utilizas el servicio de [events], los pagos a tus cuentas desencadenarán un callback HTTP realizado a tu servidor de negocios.
-
-Si ya tienes una solución para monitorear pagos a tus cuentas Stellar, como una integración con tu exchange, Horizon, o RPC, entonces este componente no es requerido, aunque tu servidor de negocios necesitará notificar a la Anchor Platform cuando un pago asociado con una transacción de la Anchor Platform haya sido realizado a una de tus cuentas Stellar a través de la [Platform API][platform-api].
-
-[seps]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/README.md
-[platform-api]: ../api-reference/platform/transactions/README.mdx
-[callback-api]: ../api-reference/callbacks/README.mdx
-[events]: ./events/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/assets-and-client-wallets.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/assets-and-client-wallets.mdx
deleted file mode 100644
index 1453b52620..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/assets-and-client-wallets.mdx
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Activos y Clientes de Billeteras
-sidebar_position: 40
----
-
-# Activos y Clientes de Billeteras
-
-Esta guía explica cómo configurar activos y clientes de billeteras en la Anchor Platform.
-
-## Configuración de Activos
-
-Los activos definen los tokens y monedas que tu Anchor Platform admite para depósitos y retiros. En la guía "Empezando", los activos se configuran en el archivo `config/assets.yaml` mediante el `ap_start.sh`.
-
-Para la lista completa de campos y valores predeterminados, consulta la [referencia de configuración de activos](https://github.com/stellar/anchor-platform/blob/develop/core/src/main/resources/config/anchor-asset-default-values.yaml).
-
-### Ejemplo de Configuración de Activos
-
-```yaml
-items:
-  - id: stellar:native
-    distribution_account: "G...DIST"
-    significant_decimals: 7
-    sep6:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - SEPA
-          - SWIFT
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - bank_account
-          - cash
-    sep24:
-      enabled: true
-    sep31:
-      enabled: true
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - iso4217:USD
-```
-
-### Explicación de Campos
-
-- **`id`** (Obligatorio) - El identificador del activo en el formato `SCHEMA:CÓDIGO:(EMISOR)` o `stellar:native` que representa XLM, el activo nativo de Stellar. Por ejemplo, `stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5` representa Circle USD. Para monedas fiduciarias, usa `iso4217:CÓDIGO` (por ejemplo, `iso4217:USD`, `iso4217:CAD`).
-
-- **`distribution_account`** - La dirección de la cuenta Stellar que posee el activo para distribución. No es necesario para activos fiduciarios (`iso4217`).
-
-- **`significant_decimals`** - El número de decimales que admite el activo.
-
-- **`sep6`** - Habilita SEP-6 y configura límites y métodos de depósito/retiro por activo.
-
-- **`sep24`** - Habilita los flujos interactivos SEP-24 y sus configuraciones por activo.
-
-- **`sep31`** - Habilita el soporte de pagos transfronterizos SEP-31 para el activo.
-
-- **`sep38`** - Habilita cotizaciones SEP-38 y `exchangeable_assets` para pares de divisas admitidos.
-
-## Configuración de Clientes de Billeteras
-
-Los clientes de billetera son las apps de billetera que se conectan a tu Anchor Platform para realizar transacciones en nombre de los usuarios.
-
-Para la lista completa de campos y valores predeterminados de clientes, consulta la [referencia de configuración de clientes](https://github.com/stellar/anchor-platform/blob/main/platform/src/main/resources/config/anchor-client-default-values.yaml).
-
-### Ejemplo de Configuración de Cliente
-
-```yaml
-items:
-  - name: "referenceCustodial"
-    type: custodial
-    signing_keys:
-      - GDJLB...KLTG
-    callback_urls:
-      sep6: https://client.example.com/callbacks/sep6
-      sep24: https://client.example.com/callbacks/sep24
-      sep31: https://client.example.com/callbacks/sep31
-      sep12: https://client.example.com/callbacks/sep12
-  - name: "reference"
-    type: noncustodial
-    domains:
-      - wallet-server:8092
-      - client.example.com
-    callback_urls:
-    ...
-```
-
-### Explicación de Campos
-
-**Configuración de Cliente Custodial:**
-
-- **`name`** (Obligatorio) - Un identificador único para el cliente.
-
-- **`type: custodial`** (Obligatorio) - El tipo de cliente. Debe establecerse en `custodial` para clientes custodial.
-
-- **`signing_keys`** (Obligatorio) - Una lista de claves públicas Stellar usadas para la autenticación SEP-10 del cliente. El anchor usa estas claves para verificar que las solicitudes provienen del cliente autorizado.
-
-- **`callback_urls`** (Opcional) - URLs a las cuales el servicio puede enviar callbacks para diferentes tipos SEP.
-  - **`sep6`** - URL de callback para actualizaciones del estado de transacciones SEP-6 (depósito/retiro)
-  - **`sep24`** - URL de callback para actualizaciones del estado de transacciones SEP-24 (depósito/retiro interactivo)
-  - **`sep31`** - URL de callback para actualizaciones del estado de transacciones SEP-31 (pagos transfronterizos)
-  - **`sep12`** - URL de callback para actualizaciones de información de cliente SEP-12 (KYC)
-
-**Configuración de Cliente No Custodial:**
-
-- **`name`** (Obligatorio) - Un identificador único para el cliente, similar a clientes custodial. Normalmente un nombre que representa claramente a la entidad cliente.
-
-- **`type: noncustodial`** (Obligatorio) - El tipo de cliente. Debe establecerse en `noncustodial` para clientes no custodial. Los clientes no custodial permiten a los usuarios controlar sus propias claves privadas, y la billetera actúa como interfaz para cuentas controladas por el usuario.
-
-- **`domains`** (Obligatorio) - Una lista de dominios asociados con el cliente, usados para verificar la identidad del cliente.
-
-- **`callback_urls`** (Opcional) - URLs a las cuales el servicio puede enviar callbacks para diferentes tipos SEP. Funciona igual que para clientes custodial (ver arriba).
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/observer/observer.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/observer/observer.mdx
deleted file mode 100644
index 28af649bf0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/observer/observer.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
-Usar el Payment Observer te permite delegar este paso a la Anchor Platform. Para habilitar el Payment Observer, usa el flag `--stellar-observer` en la sección de comandos del [archivo compose](../../getting-started.mdx#configuration).
-
-El Payment Observer rastreará todas las transacciones enviadas a la cuenta de distribución. Cuando se detecte la transacción con el memo esperado en la red, el estado cambiará automáticamente a `pending_anchor` y el evento será emitido (si se usa Kafka).
-
-Para actualizar los estados de las transacciones, el observer realiza las solicitudes JSON-RPC correspondientes a la plataforma. Debe usar la siguiente URL.
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_BASE_URL=http://platform-server:8085
-```
-
-</CodeExample>
-
-:::caution
-
-El Payment Observer no validará los montos. Es tu responsabilidad verificar que el monto enviado por el usuario sea correcto.
-
-:::
-
-:::info
-
-Si ya tienes un sistema que monitorea pagos, asegúrate de que la lógica del sistema iguale la descripción a continuación:
-
-Primero, espera a que la transacción se incluya en el ledger (usando un SDK). Esta transacción debe tener el memo esperado y la dirección de destino (cuenta de distribución). Una vez que esta transacción ha sido detectada y verificada, notifica al usuario que los fondos han sido recibidos usando la solicitud JSON-RPC [notify_onchain_funds_received](#funds-received-1).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/error.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/error.mdx
deleted file mode 100644
index 4ef2ef2c1e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/error.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-<div>
-
-| Código de error | Significado                                      |
-| :-------------- | :----------------------------------------------- |
-| \-32600         | El JSON enviado no es un objeto Request válido   |
-| \-32601         | El método no existe / no está disponible         |
-| \-32602         | Invalid method parameter(s)                      |
-| \-32603         | Error interno de JSON-RPC                        |
-
-</div>
-
-:::tip
-
-También haremos referencia a una variable `$transaction_id`. Esta es una identificación de la transacción que se está devolviendo desde la Anchor Platform en una solicitud de inicio de retirada de fondos o depósito. Puedes obtener el ID de la transacción conectando la billetera de prueba a tu instancia local de Anchor Platform.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/request.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/request.mdx
deleted file mode 100644
index 5ccea530bc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/request.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
-El objeto Request debe contener los siguientes atributos:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- jsonrpc
-  - cadena
-  - A String specifying the version of the JSON-RPC protocol. MUST be exactly "2.0"
-- método
-  - cadena
-  - Una cadena que contiene el nombre del método a invocar. Lista de métodos disponibles que puedes ver en [JSON-RPC Methods][json-rpc-methods]
-- params
-  - objeto
-  - A Structured value that holds the parameter values, corresponding to method call, to be used during the invocation of the method
-- id
-  - cadena
-  - Un identificador establecido por el cliente. The Server will reply with the same value in the Response object
-
-</AttributeTable>
-
-:::tip
-
-Es posible proporcionar múltiples actualizaciones en una sola solicitud JSON-RPC (colocando múltiples objetos de solicitud JSON-RPC). Cuando una actualización se realiza de esta manera, todas las actualizaciones se realizarán de forma secuencial.
-
-Lo más importante es que cada solicitud JSON-RPC no es atómica. Si una actualización falla, todas las actualizaciones anteriores se APLICARÁN y todas las actualizaciones posteriores también se PROCESARÁN y APLICARÁN.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/response.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/response.mdx
deleted file mode 100644
index 0023b6b5a2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/response.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
-La respuesta se expresa como un único objeto JSON, con los siguientes atributos:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- jsonrpc
-  - cadena
-  - Una cadena que especifica la versión del protocolo JSON-RPC. It's set to "2.0"
-- resultado
-  - objeto
-  - Un valor estructurado que contiene los detalles actualizados de la transacción
-- id
-  - cadena
-  - Un identificador enviado por el cliente
-- error
-  - objeto
-  - Un valor estructurado que contiene los detalles del error
-    - id
-      - cadena
-      - Id único de la transacción por la que ocurrió un error
-    - código
-      - número
-      - Un número que indica el tipo de error que ocurrió. Consulta una lista de [códigos de error](#error-codes) a continuación
-    - mensaje
-      - cadena
-      - Una cadena que proporciona una breve descripción del error
-    - datos
-      - cadena
-      - Un valor primitivo o estructurado que contiene información adicional sobre el error
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/rpc.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/rpc.mdx
deleted file mode 100644
index b2db75cd3c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/rpc/rpc.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
-Antes de hacer solicitudes JSON-RPC, primero vamos a crear una plantilla para hacer una solicitud a la Anchor Platform.
-
-<CodeExample>
-
-```bash
-# call-json-rpc.sh
-#!/usr/bin/env bash
-
-curl localhost:8085 \
-    -X POST \
-    -H 'Content-Type: application/json' \
-    --data "@$1"
-```
-
-</CodeExample>
-
-Este pequeño script hará una solicitud JSON-RPC a la Anchor Platform que se encuentra en el puerto predeterminado (8085). Los datos de transacción JSON almacenados en el archivo proporcionado se utilizarán como cuerpo (las solicitudes deben ser un arreglo).
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/api_key.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/api_key.mdx
deleted file mode 100644
index a612d4c922..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/api_key.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-Para habilitar la autenticación por clave de API, modifica tu archivo `dev.env`:
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_AUTH_TYPE=api_key
-# Will be used as API key
-SECRET_PLATFORM_API_AUTH_SECRET="your API key that business server will use"
-```
-
-</CodeExample>
-
-Una vez habilitado, todas las solicitudes deben incluir un encabezado válido `X-Api-Key`, configurado con la clave de API establecida.
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/jwt.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/jwt.mdx
deleted file mode 100644
index d2c9deeb7f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/jwt.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-Para habilitar la autenticación JWT, modifica tu archivo `dev.env`:
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_AUTH_TYPE=jwt
-# Will be used to sign the JWT token
-SECRET_PLATFORM_API_AUTH_SECRET="your secret that business server will use"
-```
-
-</CodeExample>
-
-Anchor Platform utiliza el algoritmo HMAC SHA-256 (HS256) para firmar tokens JWT. Asegúrate de que `SECRET_PLATFORM_API_AUTH_SECRET` tenga al menos 32 caracteres para mayor seguridad.
-
-Una vez habilitado, todas las solicitudes deben incluir un encabezado `Authorization` válido con el formato `Bearer <JWT token>`.
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/security.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/security.mdx
deleted file mode 100644
index f34047d510..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/component/security/security.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
-:::caution
-
-Por defecto, los endpoints de la API de la plataforma, como `GET /transactions` y `GET /transactions/:id`, no están protegidos y son accesibles por cualquiera que tenga acceso al servidor, incluidas las billeteras.
-
-:::
-
-:::info
-
-Se recomienda mantener el servidor de la plataforma accesible solo desde la red privada. Sin embargo, puede que quieras añadir una capa adicional de protección al asegurar la API.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/README.mdx
deleted file mode 100644
index 6bbaf661d5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Servicios de Custodia
-sidebar_position: 80
----
-
-import DocCardList from "@theme/DocCardList";
-
-Usar un servicio de custodia te permitirá utilizar un servicio externo para almacenar y gestionar tus billeteras.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/configuration.mdx
deleted file mode 100644
index 41aee044b6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/configuration.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-title: Configuración
-sidebar_position: 10
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Configuración del Servidor de Custodia
-
-Si quieres usar un servicio de custodia externo para almacenar y gestionar tus billeteras, entonces necesitas implementar un servicio más: el Servidor de Custodia.
-
-Este servicio también necesita el `STELLAR_ANCHOR_CONFIG` que se mencionó anteriormente. Por defecto, se utilizará el archivo de configuración `anchor-config-default-values.yaml`.
-
-Además, ahora no necesitas implementar el Observador Stellar ya que el Servidor de Custodia será responsable de su funcionalidad.
-
-Actualiza el archivo de configuración de la Anchor Platform con la URL base y el puerto.
-
-<CodeExample>
-
-```yaml
-custody_server:
-  # The listening port of the Custody Server.
-  # Default value: 8086
-  port: 8086
-  # The base URL of the Custody Server.
-  # Default value: http://localhost:8086
-  base_url: http://localhost:8086
-```
-
-</CodeExample>
-
-Configura el tipo de autenticación.
-
-<CodeExample>
-
-```yaml
-custody_server:
-  auth:
-    # Type of authentication that is used when the Anchor Platform communicates with the Custody Server.
-    # Supported values: [none, api_key, jwt]
-    # Default value: none
-    type: none
-```
-
-</CodeExample>
-
-Si estableces el tipo de autenticación `api_key` o `jwt`, entonces necesitas agregar una variable de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SECRET_CUSTODY_SERVER_AUTH_SECRET="Custody Server auth secret"
-```
-
-</CodeExample>
-
-Inicia el Servidor de Custodia usando Gradle o Docker.
-
-<CodeExample>
-
-```bash
-./gradlew service-runner:bootRun --args=--custody-server
-docker run stellar/anchor-platform:latest --custody-server
-```
-
-</CodeExample>
-
-## Configuración de la Anchor Platform
-
-Actualiza el archivo de configuración de la Anchor Platform con el tipo de generador de información de depósito para SEP-24 y SEP-31. También, necesitas configurar una verificación de línea de confianza, si usas JSON-RPC. Además, necesitas configurar una verificación de línea de confianza, si usas JSON-RPC.
-
-<CodeExample>
-
-```yaml
-sep24:
-  # Used to choose how the SEP-24 deposit information (deposit address, memo and memo type) will be generated
-  # Supported value: [self, custody, none]
-  # Default value: self
-  deposit_info_generator_type: custody
-sep31:
-  # Used to choose how the SEP-31 deposit information (deposit address, memo and memo type) will be generated
-  # Supported value: [self, custody, api]
-  # Default value: self
-  deposit_info_generator_type: custody
-  ## Trustline check configuration. Used only when custody integration is enabled
-custody:
-  trustline:
-    ## @param: checkCronExpression
-    ## @type: string
-    ## Cron expression which defines how often a trustline check job runs. By default, a job runs every minute
-    #
-    check_cron_expression: "0 * * * * *"
-    ## @param: checkDuration
-    ## @type: integer
-    ## Determines how long (in MINUTES) the trustline will be checked. By default - 1 hour (60 minutes)
-    #
-    check_duration: 60
-    ## @param: checkTimeoutMessage
-    ## @type: string
-    ## The message that will be added to the SEP transaction after the duration check is exceeded
-    #
-    check_timeout_message: Trustline check timed out
-```
-
-</CodeExample>
-
-:::info
-
-- `self` - el memo y el tipo de memo se generan en el código local, y la cuenta de distribución se utiliza para la dirección de depósito.
-- `custody` - el memo y el tipo de memo se generan a través de la API de custodia, por ejemplo Fireblocks, así como la dirección de depósito.
-- `none` - la dirección de depósito, el memo y el tipo de memo deben ser proporcionados por la empresa en una solicitud PATCH/JSON-RPC.
-- `api` - el memo y el tipo de memo se generan mediante la llamada al endpoint GET /unique_address del anchor.
-
-:::
-
-## Configuración del Servidor de Referencia Kotlin
-
-Actualiza el archivo de configuración del Servidor de Referencia Kotlin para habilitar la integración de custodia.
-
-<CodeExample>
-
-```yaml
-app:
-  # Flag that indicates that the custody integration is enabled and the payment will be submitted using the Custody Server.
-  # Default value: false
-  custodyEnabled: true
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/README.mdx
deleted file mode 100644
index e179fc9611..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Fireblocks
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Configurar [Fireblocks](https://fireblocks.io) para actuar como un servicio de custodia que almacena y gestiona tus billeteras.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/configuration.mdx
deleted file mode 100644
index 8c74e268d5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/configuration.mdx
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Configuración
-sidebar_position: 10
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Configurar el espacio de trabajo de Fireblocks:
-
-1. [Configurar API Co-Signer](https://support.fireblocks.io/hc/en-us/articles/4581830426268)
-2. [Agregar usuario API](https://support.fireblocks.io/hc/en-us/articles/4407823826194-Adding-new-API-users)
-3. [Configurar URL de Webhook](https://support.fireblocks.io/hc/en-us/articles/4408110107794-Configuring-Webhook-URLs)
-4. [Activar la función de dirección única](https://support.fireblocks.io/hc/en-us/articles/4409104568338)
-
-Actualiza el archivo de configuración del Servidor de Custodia.
-
-<CodeExample>
-
-```yaml
-custody:
-  # Default value: none
-  type: fireblocks
-  fireblocks:
-    # The base URL of the Fireblocks API
-    # Default value: https://api.fireblocks.io
-    base_url: https://api.fireblocks.io
-    # ID of Fireblocks vault account that will be used for payments
-    vault_account_id: "vault_account_id"
-    # Fireblocks public key that is used to verify a webhook signature
-    public_key: "public_key"
-    # Mappings of fireblocks asset codes to stellar asset codes. For example:
-    # XLM_USDC_T_CEKS stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    # XLM_TEST stellar:native
-    # Codes should be separated with a space and each pair of codes should be on a new line
-    asset_mappings: "asset_mappings"
-    reconciliation:
-      # Cron expression which defines how often the transaction reconciliation job runs.
-      # By default, job runs every 15 minutes.
-      # Default value: 0 0/15 * * * *
-      cron_expression: "0 0/15 * * * *"
-      # Determines how many times the transaction reconciliation job will attempt to update the status of the
-      # transaction before marking it as failed.
-      # Default value: 10
-      max_attempts: 10
-    retry_config:
-      # Determines how many times the Fireblocks client will attempt to send a request before marking a call as failed.
-      # Default value: 3
-      max_attempts: 3
-      # Interval between Fireblocks client call attempts (in ms)
-      # Default value: 1000
-      delay: 1000
-```
-
-</CodeExample>
-
-Agrega las variables de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-# API key, that will be added to JWT token claims. JWT token will be sent in requests to Fireblocks API
-SECRET_CUSTODY_FIREBLOCKS_API_KEY="Fireblocks API key"
-# Secret key, that is used to sign JWT token
-SECRET_CUSTODY_FIREBLOCKS_SECRET_KEY="Fireblocks secret key"
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/example.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/example.mdx
deleted file mode 100644
index 2f8f622e96..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/custody-services/fireblocks/example.mdx
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Ejemplo
-sidebar_position: 10
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-[comentario]: # "Las definiciones de diagramas de secuencia se encuentran en la carpeta /static/definitions"
-[comentario]: # "Para actualizarlas, usa https://sequencediagram.org"
-
-### Flujo de depósito SEP-24 con webhook:
-
-- request_offchain_funds
-- notify_offchain_funds_received
-- do_stellar_payment
-- notify_onchain_funds_sent [![sequence_diagram_sep24_deposit_webhook](../../../assets/sequence_diagram_sep24_deposit_webhook.png)](../../../assets/sequence_diagram_sep24_deposit_webhook.png)
-  <br />
-
-### Flujo de depósito SEP-24 con trabajo de conciliación:
-
-- request_offchain_funds
-- notify_offchain_funds_received
-- do_stellar_payment
-- notify_onchain_funds_sent [![sequence_diagram_sep24_deposit_job](../../../assets/sequence_diagram_sep24_deposit_job.png)](../../../assets/sequence_diagram_sep24_deposit_job.png)
-  <br />
-
-### Flujo de retiro SEP-24 con webhook:
-
-- do_stellar_payment
-- notify_onchain_funds_received
-- notify_offchain_funds_sent [![sequence_diagram_sep24_withdrawal_webhook](../../../assets/sequence_diagram_sep24_withdrawal_webhook.png)](../../../assets/sequence_diagram_sep24_withdrawal_webhook.png)
-  <br />
-
-### Flujo de retiro SEP-24 con trabajo de conciliación:
-
-- request_onchain_funds
-- notify_onchain_funds_received
-- notify_offchain_funds_sent [![sequence_diagram_sep24_withdrawal_job](../../../assets/sequence_diagram_sep24_withdrawal_job.png)](../../../assets/sequence_diagram_sep24_withdrawal_job.png)
-  <br />
-
-### Flujo de recepción SEP-31 con webhook:
-
-- notify_onchain_funds_received
-- notify_offchain_funds_sent [![sequence_diagram_sep31_receive_webhook](../../../assets/sequence_diagram_sep31_receive_webhook.png)](../../../assets/sequence_diagram_sep31_receive_webhook.png)
-  <br />
-
-### Flujo de recepción SEP-31 con trabajo de conciliación:
-
-- notify_onchain_funds_received
-- notify_offchain_funds_sent [![sequence_diagram_sep31_receive_job](../../../assets/sequence_diagram_sep31_receive_job.png)](../../../assets/sequence_diagram_sep31_receive_job.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/README.mdx
deleted file mode 100644
index 405b0dd365..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Manejo de eventos
-sidebar_position: 120
----
-
-import DocCardList from "@theme/DocCardList";
-
-Recibe actualizaciones de transacciones a través de eventos webhook HTTP.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/delivery.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/delivery.mdx
deleted file mode 100644
index 02e4494173..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/delivery.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Garantías de Entrega
-sidebar_position: 30
----
-
-## Garantías de Entrega
-
-Dependiendo del sistema de mensajería que utilices, habrá diferentes garantías de entrega. el servicio de eventos utiliza Kafka como sistema de mensajería, por lo que las garantías de entrega dependerán de la configuración del productor y de la configuración del corredor que utilices. Dependiendo del número de particiones configuradas para el tema `TRANSACTION`, los eventos pueden entregarse fuera de orden.
-
-:::caution
-
-Cualquier lógica de transacción que dependa del orden debe utilizar el `status` de la transacción y los campos `updated_at` para determinar el orden de los eventos.
-
-:::
-
-Las siguientes subsecciones describirán las garantías de entrega desde la perspectiva del cliente y del servidor empresarial.
-
-### Garantías de Entrega del Cliente
-
-Para cada cliente, el servicio de eventos intentará entregar cada evento hasta tres veces con un retroceso exponencial. Si el evento no se entrega después de tres intentos debido a errores HTTP 4xx o 5xx, el evento se omitirá. Si el cliente no es accesible después de tres intentos, el servicio de eventos ya no intentará entregar ningún evento a ese cliente.
-
-### Garantías de Entrega del Servidor Empresarial
-
-El servicio de eventos intentará entregar cada evento al servidor empresarial hasta tres veces con un retroceso exponencial. Si el evento no se entrega después de tres intentos debido a errores HTTP 4xx o 5xx, el evento se omitirá. Si el servidor empresarial no es accesible después de tres intentos, el servicio de eventos ya no intentará entregar ningún evento al servidor empresarial.
-
-:::note
-
-Las garantías de entrega del servidor empresarial son las mismas que las garantías de entrega del cliente. En el futuro, el servicio de eventos omitirá los eventos que no se entreguen a clientes que no sean accesibles.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/getting-started.mdx
deleted file mode 100644
index e4d7ddf544..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/getting-started.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Anchor Platform proporciona un servicio de eventos que envía notificaciones HTTP webhook a:
-
-**Servidores de Negocios**
-
-- Cambios en el estado de la transacción
-- Actualizaciones de cotizaciones
-- Cambios en el estado KYC del cliente
-
-Los esquemas de eventos para servidores empresariales están definidos en la [referencia de la API](../../api-reference/callbacks/post-event.api.mdx).
-
-**Aplicaciones de Cliente**
-
-- Cambios en el estado de la transacción que afectan a sus usuarios
-- Cambios en el estado KYC del cliente que afectan a sus usuarios
-
-_Los esquemas de eventos para las aplicaciones de cliente están definidos en sus respectivos SEPs:_
-
-- [SEP-6 Eventos de Transacción](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md#single-historical-transaction)
-- [SEP-12 Eventos de Clientes](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#response)
-- [SEP-24 Eventos de Transacción](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#single-historical-transaction)
-- [SEP-31 Eventos de Transacción](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#get-transaction)
-
-Esto elimina la necesidad de que los servidores de negocios y las aplicaciones de cliente consulten continuamente las API en busca de actualizaciones.
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/integration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/integration.mdx
deleted file mode 100644
index caa0d0ec72..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/events/integration.mdx
+++ /dev/null
@@ -1,161 +0,0 @@
----
-title: Integración
-sidebar_position: 20
----
-
-Esta guía te guiará a través de la integración con el servicio de eventos para comenzar a recibir eventos. El servicio de eventos actualmente solo admite Apache Kafka como el intermediario de mensajes de backend.
-
-Se supone que tienes familiaridad con Kafka y no cubriremos cómo configurar un clúster de Kafka.
-
-## Requisitos
-
-Anchor Platform enviará eventos al tema Kafka `TRANSACTION`. El servicio de eventos consumirá eventos de este tema y los enviará a los puntos finales apropiados.
-
-## Configuración
-
-Primero, es necesario configurar el productor de Kafka del servicio de eventos utilizando la sección `event.queue` del archivo de configuración o configurando las variables de entorno. El siguiente es el conjunto de variables de entorno requeridas para configurar el productor de Kafka del servicio de eventos:
-
-<CodeExample>
-
-```bash
-# dev.env
-EVENTS_ENABLED=true
-EVENTS_QUEUE_TYPE=kafka
-EVENTS_QUEUE_KAFKA_BOOTSTRAP_SERVER=localhost:9092
-```
-
-```yaml
-# dev.services.yaml
-events:
-  enabled: true
-  queue:
-    type: kafka
-    kafka:
-      bootstrap_server: localhost:9092
-```
-
-</CodeExample>
-
-Anchor Platform permite configurar un subconjunto de la configuración del cliente del productor de Kafka. Consulta el [archivo de valores predeterminados][default-values-file] para más información sobre lo que está disponible. Para más información sobre la configuración del cliente del productor de Kafka, consulta la [documentación de Kafka](https://kafka.apache.org/documentation/#producerconfigs).
-
-A continuación, es necesario configurar el procesador de eventos en la sección `event_processor` del archivo de configuración de Anchor Platform o configurando las variables de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-EVENT_PROCESSOR_CLIENT_STATUS_CALLBACK_ENABLED=true
-EVENT_PROCESSOR_CALLBACK_API_REQUEST_ENABLED=true
-```
-
-```yaml
-# dev.services.yaml
-event_processor:
-  client_status_callback:
-    enabled: true
-  callback_api_request:
-    enabled: true
-```
-
-</CodeExample>
-
-Esto permitirá que el procesador de eventos comience a procesar eventos del tema `TRANSACTION`. En este ejemplo, el procesador de eventos enviará eventos a los puntos finales de devolución de llamada del cliente y del servidor de negocios.
-
-## Recibiendo Eventos
-
-El servicio de eventos se puede utilizar para enviar eventos a los puntos finales de devolución de llamada del cliente y del servidor de negocios. El servicio de eventos enviará eventos a estos puntos finales como solicitudes HTTP POST con los datos del evento en el cuerpo de la solicitud.
-
-### Como Aplicación Cliente
-
-Las aplicaciones cliente pueden recibir actualizaciones sobre las transacciones de sus usuarios e información de clientes. El esquema de los datos del evento dependerá del tipo de evento que se envíe.
-
-Para recibir eventos como una aplicación cliente, necesitarás exponer URLs de devolución de llamada a las que el servicio de eventos pueda enviar eventos. El servicio de eventos enviará una solicitud POST a este punto final con los datos del evento en el cuerpo de la solicitud. El esquema de los datos del evento dependerá del tipo de evento que se envíe. Anchor Platform permite configurar puntos finales únicos por tipo de evento.
-
-Anchor Platform solo enviará eventos a los clientes que estén listados en la configuración del cliente. Consulta la [documentación de configuración del cliente][clients-config] para más información.
-
-#### Firma de Devolución de Llamada
-
-Anchor Platform firma las solicitudes de devolución de llamada que envía a las aplicaciones cliente. La firma se incluye en el encabezado `Signature` de la solicitud. La especificación de firma de URL de devolución de llamada se puede encontrar en las especificaciones de protocolo SEP correspondientes.
-
-- [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)
-
-### Como Servidor de Negocios
-
-Además de las actualizaciones del estado de transacción SEP, los servidores de negocios pueden recibir eventos sobre la creación de cotizaciones SEP-31 o actualizaciones de información de clientes SEP-12. El esquema de los datos del evento dependerá del tipo de evento que se envíe. Visita la [documentación de la API de eventos](../../api-reference/callbacks/post-event.api.mdx) para más información sobre el esquema de los datos del evento.
-
-Para recibir eventos como un servidor de negocios, necesitarás exponer una URL de devolución de llamada a la que el servicio de eventos pueda enviar eventos. El servicio de eventos enviará una solicitud POST a este punto final con los datos del evento en el cuerpo de la solicitud.
-
-#### Configuración
-
-La API de devolución de llamada del servicio de eventos se puede configurar utilizando la sección `callback_api` del archivo de configuración de Anchor Platform o configurando las variables de entorno.
-
-El siguiente es un ejemplo de cómo configurar la API de devolución de llamada del servicio de eventos con autenticación JWT:
-
-<CodeExample>
-
-```bash
-# dev.env
-
-# note `/callback` will not be used for event callbacks
-# instead events will be sent to `http://localhost:8081/event`
-# all other callbacks (rates, customer, etc.) will use the provided `/callback` root path
-CALLBACK_API_BASE_URL=http://localhost:8081/callback
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
-SECRET_CALLBACK_API_AUTH_SECRET="a secret for signing jwts"
-```
-
-```yaml
-# dev.services.yaml
-callback_api:
-  base_url: http://localhost:8081/callback
-  auth:
-    type: jwt
-    jwt:
-      expiration_milliseconds: 30000
-      http_header: Authorization
-```
-
-</CodeExample>
-
-El siguiente es un ejemplo de cómo configurar la API de devolución de llamada del servicio de eventos con autenticación de clave de API:
-
-<CodeExample>
-
-```bash
-# dev.env
-CALLBACK_API_BASE_URL=http://localhost:8081/callback
-CALLBACK_API_AUTH_TYPE=api_key
-CALLBACK_API_AUTH_API_KEY_HTTP_HEADER=X-Api-Key
-SECRET_CALLBACK_API_AUTH_SECRET="your API key"
-```
-
-```yaml
-# dev.services.yaml
-callback_api:
-  base_url: http://localhost:8081/callback
-  auth:
-    type: api_key
-    api_key:
-      http_header: X-Api-Key
-```
-
-</CodeExample>
-
-Esto configura la API de devolución de llamada del servicio de eventos que se utilizará para enviar eventos a los puntos finales de devolución de llamada del cliente y del servidor de negocios. Las siguientes son las opciones de configuración admitidas:
-
-- `base_url`: La URL base del punto final de devolución de llamada del servidor de negocios.
-- `secret`: El secreto que se utilizará al enviar eventos al punto final de devolución de llamada del servidor de negocios. Esto se utiliza para firmar el cuerpo de la solicitud cuando se habilita la autenticación JWT y es la clave de API cuando se habilita la autenticación de clave de API.
-- `auth`: El método de autenticación que se utilizará al enviar eventos al punto final de devolución de llamada del servidor de negocios. Los siguientes son los métodos de autenticación admitidos:
-  - `JWT`: El servicio de eventos enviará un JSON Web Token (JWT) en el encabezado `Authorization` de la solicitud. Las siguientes son las opciones de configuración admitidas:
-    - `expiration_milliseconds`: El tiempo de caducidad del JWT en milisegundos.
-    - `http_header`: El encabezado en el que se enviará el JWT.
-  - `API_KEY`: El servicio de eventos enviará una clave de API en el encabezado `Authorization` de la solicitud. Las siguientes son las opciones de configuración admitidas:
-    - `http_header`: El encabezado en el que se enviará la clave de API.
-
-[archivo de valores predeterminados]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[configuración de clientes]: ../../sep-guide/sep10/README.mdx#config-with-client-attribution
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/getting-started.mdx
deleted file mode 100644
index 73f0fb73c8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/getting-started.mdx
+++ /dev/null
@@ -1,139 +0,0 @@
----
-title: Comenzar
-sidebar_position: 30
----
-
-# Comenzar
-
-Esta guía te ayudará a poner en marcha rápidamente la Anchor Platform (solo TESTNET) con una referencia comercial ejecutándose localmente usando Docker Compose.
-
-Ten en cuenta que esto no está pensado para ejecutarse en producción.
-
-## Requisitos previos
-
-- [Docker](https://www.docker.com/get-started) y Docker Compose instalados
-- [Stellar CLI](https://github.com/stellar/stellar-cli) instalado
-
-## Inicio rápido
-
-### 1. Clona el repositorio de Anchor Platform
-
-```bash
-git clone https://github.com/stellar/anchor-platform
-```
-
-### 2. Navega al directorio quick-run
-
-```bash
-cd anchor-platform/quick-run
-```
-
-### 3. Inicia todos los servicios
-
-```bash
-./ap_start.sh
-```
-
-### 4. Verifica que la plataforma esté en funcionamiento
-
-Espera unos momentos para que los servicios se inicialicen, luego verifica que la plataforma responda:
-
-```bash
-curl http://localhost:8080/.well-known/stellar.toml
-```
-
-Deberías ver devuelto el archivo de configuración Stellar TOML.
-
-### 5. Verifica el estado del servicio
-
-```bash
-docker-compose ps
-```
-
-Todos los servicios deberían mostrar "Up" en la columna de estado.
-
-## Qué incluye
-
-La configuración `quick-run` incluye:
-
-- **docker-compose.yaml** - Definiciones completas de servicios con todas las dependencias
-- **dev.env** - Variables de entorno preconfiguradas
-- **config/** - Archivos de configuración necesarios:
-  - `assets.yaml` - Definiciones de activos
-  - `clients.yaml` - Configuraciones de clientes
-  - `reference-config.yaml` - Configuraciones del servidor de referencia
-  - `stellar.localhost.toml` - Archivo SEP-1 TOML
-
-:::tip
-
-Para más información sobre la configuración de activos y billeteras de clientes, consulta la guía [Assets and Client Wallets](./assets-and-client-wallets.mdx).
-
-:::
-
-## Pruebas con Stellar Demo Wallet
-
-Puedes probar la Anchor Platform usando la [Stellar Demo Wallet](https://demo-wallet.stellar.org):
-
-1. Abre la [Stellar Demo Wallet](https://demo-wallet.stellar.org) en tu navegador.
-2. Haz clic en el botón **"Generate keypair for new account (testnet only)"**.
-3. Haz clic en el botón **"Create Account"** junto a la clave PÚBLICA.
-4. Ahora deberías ver `XLM` disponible en la sección **Balances**, indicando que tu cuenta está cargada.
-5. Haz clic en **"Add home domain"** y escribe la siguiente URL:
-   ```
-   http://localhost:8080
-   ```
-   Esto conecta la demo wallet con tu instancia local de Anchor Platform ejecutándose en el puerto 8080.
-6. Ahora deberías poder realizar transacciones SEP (depósitos, retiros, etc.) con tu instancia local de Anchor Platform.
-
-## Personalizar configuración
-
-Para modificar los ajustes:
-
-1. Edita `dev.env` para variables de entorno
-2. Edita archivos en `config/` para configuraciones específicas de servicios
-3. Reinicia los servicios: `docker-compose restart`
-
-## Detener servicios
-
-Para detener todos los servicios:
-
-```bash
-docker-compose down
-```
-
-## Cómo implementar tu servidor de callback de negocio
-
-Una vez que tengas la Anchor Platform en funcionamiento, puedes reemplazar el servidor de referencia con tu propia implementación de servidor de callback de negocio. Esto te permite implementar tu propia lógica de negocio para manejar depósitos, retiros y otras operaciones del anchor.
-
-### 1. Apaga el servidor de negocio de referencia
-
-Después de que la Anchor Platform esté iniciada y en funcionamiento, detén el servicio del servidor de referencia:
-
-```bash
-docker-compose stop reference-server
-```
-
-Esto detiene el servidor de referencia mientras mantiene en funcionamiento la Anchor Platform y otros servicios. La plataforma continuará operando, pero ya no recibirá callbacks del servidor de referencia.
-
-### 2. Implementa y ejecuta tu propio servidor de referencia
-
-Implementa tu propio servidor de callback que implemente la API de callbacks de Anchor Platform.
-
-Puedes usar el [kotlin-reference-server](https://github.com/stellar/anchor-platform/tree/develop/kotlin-reference-server) como implementación de referencia para entender los endpoints y estructuras de datos requeridos.
-
-Asegúrate de que tu servidor de callback sea accesible en `http://localhost:8091` (o el endpoint configurado) y que Anchor Platform pueda alcanzarlo.
-
-Tu servidor debe:
-
-- Escuchar en el puerto **8091** (o configurar la plataforma para usar otro puerto)
-- Implementar los endpoints de callback requeridos según lo especificado en la documentación de la API de Anchor Platform
-- Manejar la lógica del negocio para:
-  - Cálculo de tarifas
-  - Determinación de la tasa de cambio
-  - Actualizaciones del estado de transacciones
-  - Gestión de información del cliente (KYC)
-  - Procesamiento de depósitos y retiros
-
-### 3. Prueba tu integración usando la demo wallet
-
-Sigue los pasos descritos en la sección [Testing with Stellar Demo Wallet](#testing-with-stellar-demo-wallet) arriba, y verifica que tu servidor maneja correctamente depósitos, retiros y otras operaciones SEP iniciadas desde la wallet.
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/overview.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/overview.mdx
deleted file mode 100644
index 07f6cf2b16..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/overview.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Descripción general
-sidebar_position: 10
----
-
-La Anchor Platform es la forma más fácil y rápida de implementar [anchos](/docs/learn/fundamentals/anchors) compatibles con [Propuestas del Ecosistema Stellar (SEPs)](https://github.com/stellar/stellar-protocol/tree/master/ecosystem).
-
-El objetivo de la Anchor Platform es manejar toda la funcionalidad y los requisitos específicos de Stellar para la ejecución de un anchor, permitiendo que las empresas se centren en la lógica de negocio esencial necesaria para ofrecer estos servicios.
-
-La Anchor Platform logra esto implementando las API estandarizadas del ecosistema (SEPs) para billeteras, exchanges y otras aplicaciones para que las consuman, mientras ofrece un conjunto de APIs de backend para que las empresas proporcionen información específica, como tarifas de transacción, tasas de cambio y estados de transacción fuera de cadena.
-
-A continuación se muestra una lista de SEPs actualmente admitidos:
-
-- [SEP-1][sep-1]: [Archivo de Información Stellar][sep1-ap]
-- [SEP-6][sep-6]: [Depósito y Retirada Programáticos][sep6-ap]
-- [SEP-10][sep-10]: [Autenticación Stellar][sep10-ap]
-- [SEP-12][sep-12]: API KYC
-- [SEP-24][sep-24]: [Depósito y Retirada Alojados][sep24-ap]
-- [SEP-31][sep-31]: [API de Pagos Transnacionales][sep31-ap]
-- [SEP-38][sep-38]: API RFQ de Anchor
-- [SEP-45][sep-45]: [Autenticación Stellar para cuentas de contrato][sep45-ap]
-
-La documentación de la Anchor Platform es un trabajo en progreso. Los desarrolladores son bienvenidos a sumergirse en el código y la documentación existente en el [repositorio de GitHub][anchor-platform-github], o si estás buscando crear un servicio de entrada y salida compatible con SEP-24, consulta nuestra [guía de inicio][sep24-ap].
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[sep-12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
-[anchor-platform-github]: https://github.com/stellar/java-stellar-anchor-sdk
-[sep1-ap]: ../sep-guide/sep1/README.mdx
-[sep6-ap]: ../sep-guide/sep6/README.mdx
-[sep10-ap]: ../sep-guide/sep10/README.mdx
-[sep24-ap]: ../sep-guide/sep24/README.mdx
-[sep31-ap]: ../sep-guide/sep31/README.mdx
-[sep45-ap]: ../sep-guide/sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep1/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep1/README.mdx
deleted file mode 100644
index 5a7342f23e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep1/README.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Archivo de información Stellar (SEP-1)
-sidebar_position: 40
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Habilitemos aplicaciones para aprender más sobre tu servicio alojando un archivo `stellar.toml` en una ruta de URL estandarizada. Este archivo permite a las aplicaciones encontrar información sobre tu negocio, los activos que utilizan tus servicios, así como las rutas de URL raíz para estos servicios. Podemos alojar este archivo utilizando la Anchor Platform.
-
-Creemos un archivo llamado `dev.stellar.toml` utilizando el contenido a continuación como punto de partida. Para el conjunto completo de atributos, consulta la [especificación SEP-1][sep-1].
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que necesitarás crear otro archivo para tu implementación de producción que use la frase de paso de la red pública, tus URL de servicio de producción, tus cuentas de distribución de Mainnet y clave de firma, así como las cuentas emisoras de Mainnet de los activos que utiliza tu servicio.
-
-En tu archivo `dev.env`, especifica lo siguiente.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/home/dev.stellar.toml
-```
-
-</CodeExample>
-
-Esto le dirá a la Anchor Platform que debe alojar el archivo especificado por `SEP1_TOML_VALUE` en `./well-known/stellar.toml`.
-
-Alternativamente, tu archivo `stellar.toml` podría ser alojado utilizando un servidor de archivos estáticos adecuado como [nginx]. Siempre que tu archivo de información incluya las URL adecuadas apuntando a la Anchor Platform, esto funcionará bien.
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep10/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep10/README.mdx
deleted file mode 100644
index b56bd6e186..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep10/README.mdx
+++ /dev/null
@@ -1,152 +0,0 @@
----
-title: Autenticación Stellar (SEP-10)
-sidebar_position: 50
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Habilitar la Autenticación Stellar
-
-Las aplicaciones de billeteras basadas en Stellar crean sesiones autenticadas con anclajes Stellar al probar que ellos, o sus usuarios, tienen suficiente control sobre una cuenta Stellar. Una vez autenticada, la aplicación de billetera utiliza un token de sesión proporcionado por el anclaje en solicitudes posteriores a los servicios estandarizados del anclaje.
-
-La Anchor Platform admite esta forma de autenticación con una configuración mínima por parte del negocio.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP10_ENABLED=true
-SEP10_HOME_DOMAIN=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret encryption key"
-```
-
-</CodeExample>
-
-`SEP_10_HOME_DOMAIN` es la propiedad `home_domain` utilizada por [sep-10]. El valor de configuración debe ser igual al host del archivo toml. Si estás alojando el archivo toml a través de la Plataforma, (`SEP1_ENABLED` está configurado como `true`), el archivo toml será alojado en el servidor SEP.
-
-`SECRET_SEP10_SIGNING_SEED` es la clave privada de la clave pública que has especificado como `SIGNING_KEY` en tu archivo `stellar.toml`. Se utilizará para firmar los desafíos de autenticación presentados a las aplicaciones de billeteras, siempre que estés en posesión de la `SIGNING_KEY`. Las billeteras comprobarán esta firma antes de firmar y devolver el desafío de autenticación.
-
-`SECRET_SEP10_JWT_SECRET` es la clave de cifrado que se utilizará para firmar y verificar los tokens de autenticación que emites a las aplicaciones de billeteras después de que ellas o sus usuarios hayan probado control sobre su cuenta Stellar.
-
-:::info
-
-Por defecto, la Anchor Platform permite que cualquier persona con una cuenta Stellar se autentique con tus servicios. Si deseas permitir solo a los usuarios de una aplicación de billetera determinada autenticarse, o quieres deshabilitar la autenticación para usuarios específicos, utiliza las siguientes variables de entorno. Esta es una característica opcional y solo debe añadirse si es un requisito empresarial.
-
-:::
-
-## Configurar Con Atribución del Cliente
-
-`SEP10_CLIENT_ATTRIBUTION_REQUIRED` informa a la Anchor Platform si debe permitir que los usuarios de billeteras no custodiales se autentiquen sin que la billetera también se identifique.
-
-`CLIENTS` es la lista de servidores de billetera externos o clientes con los que el servidor Anchor puede comunicarse de forma segura.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP10_CLIENT_ATTRIBUTION_REQUIRED=true
-```
-
-</CodeExample>
-
-<CodeExample>
-
-```yaml
-clients:
-  # Each item in the list may contain the following fields:
-  #   - name: (required) the name of the client
-  #   - type: (required) `custodial` or `noncustodial`
-  #
-  #   If the type is `custodial`,
-  #   - signing_keys: (required) the custodial SEP-10 signing key of the client.
-  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
-  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
-  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
-  #   - callback_urls.sep12: (optional) the URL of the client's SEP-10 callback API endpoint.
-  #   - allow_any_destination: (optional) default to false. If set to true, allows any destination for deposits.
-  #   - destination_accounts: (optional) list of accounts allowed to be used for the deposit.
-  #                           If allows_any_destinations set to true, this configuration option is ignored.
-  #
-  #   If the type is `noncustodial`,
-  #   - domains: (required) the domains of the client.
-  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
-  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
-  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
-  #   - callback_urls.sep12: (optional) the URL of the client's SEP-10 callback API endpoint.
-
-  # custodial client
-  - name: custodial-client1
-    type: custodial
-    signing_keys: "the signing key 1 of the client1","the signing key 2 of the client1"
-    callback_urls:
-      sep6: https://callback.custodial-client1.com/api/v1/anchor/callback/sep6
-      sep12: https://callback.custodial-client1.com/api/v1/anchor/callback/sep12
-    allow_any_destination: false
-    destination_accounts: destAccount1,destAccount2
-  - name: custodial-client2
-    type: custodial
-    signing_keys: "the signing key of the client2",
-
-  # noncustodial client
-  - name: noncustodial-client1
-    type: noncustodial
-    domains: noncustodial-client1.co,noncustodial-client1.com
-    callback_urls:
-      sep6: https://callback.noncustodial-client1.co/api/v2/anchor/callback/sep6
-      sep12: https://callback.noncustodial-client1.co/api/v2/anchor/callback/sep12
-  - name: noncustodial-client2
-    type: noncustodial
-    domains: noncustodial-client2.com
-```
-
-```bash
-# dev.env
-# custodial client
-CLIENTS[0]_NAME=custodial-client1
-CLIENTS[0]_TYPE=custodial
-CLIENTS[0]_SIGNING_KEYS="the signing key 1 of the client1","the signing key 2 of the client1"
-CLIENTS[0]_ALLOW_ANY_DESTINATION=false
-CLIENTS[0]_DESTINATION_ACCOUNTS=destAccount1,destAccount2
-CLIENTS[1]_NAME=custodial-client2
-CLIENTS[1]_TYPE=custodial
-CLIENTS[1]_SIGNING_KEYS="the signing key of the client2"
-
-# noncustodial client
-CLIENTS[2]_NAME=noncustodial-client1
-CLIENTS[2]_TYPE=noncustodial
-CLIENTS[2]_DOMAINS=noncustodial-client1.co,noncustodial-client1.com
-CLIENTS[3]_NAME=noncustodial-client2
-CLIENTS[3]_TYPE=noncustodial
-CLIENTS[3]_DOMAINS=noncustodial-client2.com
-```
-
-</CodeExample>
-
-`SEP10_CLIENT_ATTRIBUTION_REQUIRED` informa a la Anchor Platform si debe permitir que los usuarios de billeteras no custodiales se autentiquen sin que la billetera también se identifique.
-
-`CLIENTS` es la lista de servidores de billetera externos o clientes con los que el servidor Anchor puede comunicarse de forma segura.
-
-## Modificar un Archivo de Información Stellar
-
-A continuación, vamos a modificar el archivo `stellar.toml` creado [anteriormente][sep1-ap]. Las billeteras necesitan saber que la funcionalidad SEP-10 está admitida por tu negocio.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-[sep1-ap]: ../sep1/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/README.mdx
deleted file mode 100644
index 77f163d1d6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Depósitos y retiros alojados (SEP-24)
-sidebar_position: 60
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-24 permite un medio mediante el cual las billeteras y/o exchanges permiten que el usuario interactúe directamente con una rampa de entrada y salida.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/configuration.mdx
deleted file mode 100644
index bc0642f5ad..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/configuration.mdx
+++ /dev/null
@@ -1,213 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Modificar un Archivo de Información de Stellar
-
-A continuación, modifiquemos el archivo `stellar.toml` creado [anteriormente][sep1-ap]. Las billeteras necesitan saber que la funcionalidad SEP-24 es admitida por tu negocio, y también necesitan conocer todas las monedas que admites.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-TRANSFER_SERVER_SEP0024 = "http://localhost:8080/sep24"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
-WEB_AUTH_CONTRACT_ID = "Your web auth contract id"
-
-# Add support for USDC
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-# Optionally, add support for XLM
-[[CURRENCIES]]
-code = "native"
-status = "test"
-is_asset_anchored = false
-anchor_asset_type = "crypto"
-desc = "XLM, the native token of the Stellar network."
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que necesitarás crear otro archivo para tu implementación de producción que utilice la frase de entrada de la red pública, las URL de tus servicios en producción, tus cuentas de distribución de Mainnet y clave de firma, así como las cuentas emisoras de Mainnet de los activos que utiliza tu servicio.
-
-## Habilitar Depósitos y Retiros Alojados
-
-Ahora estás listo para habilitar depósitos y retiros alojados a través de la API SEP-24. Especifica lo siguiente en tu archivo `dev.assets.yaml`, y cambia los valores según tus preferencias. Este archivo de activos de ejemplo habilitará el soporte para USDC de Circle y un USD fiat.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep24:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - SEPA
-          - SWIFT
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - bank_account
-          - cash
-  - id: iso4217:USD
-    significant_decimals: 2
-  # Optional support for XLM
-  - id: stellar:native
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 7
-    sep24:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - SEPA
-          - SWIFT
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - bank_account
-          - cash
-```
-
-</CodeExample>
-
-La información proporcionada para el valor `assets` está estrechamente relacionada con la información que se expondrá a la aplicación de billetera utilizando el endpoint SEP-24 [`GET /info`][sep24-get-info]. La Anchor Platform también utiliza esta información para validar las solicitudes realizadas a tu servicio.
-
-Agrega las siguientes variables a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-// Required
-SEP24_ENABLED=true
-SEP24_INTERACTIVE_URL_BASE_URL=http://example.com
-SEP24_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET="your encryption key shared with your business server"
-SECRET_SEP24_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-
-// Optional
-SEP24_INITIAL_USER_DEADLINE_SECONDS=1209600
-```
-
-</CodeExample>
-
-`SEP24_INTERACTIVE_URL_BASE_URL` es la URL que la Anchor Platform proporcionará a las aplicaciones de billetera cuando inicien transacciones. Las aplicaciones de billetera abrirán esta URL en una vista web dentro de su app, entregando el control de la experiencia del usuario de la billetera a tu negocio. Esta URL apunta al widget web que implementa tu negocio. Contiene toda la lógica definida por el negocio. Profundizaremos más en esta experiencia en secciones posteriores.
-
-`SEP24_MORE_INFO_URL_BASE_URL` es la URL que la Anchor Platform proporcionará a las aplicaciones de billetera cuando quieran mostrar información sobre una transacción iniciada anteriormente. Esta URL es utilizada con más frecuencia por las billeteras en sus vistas de historial de transacciones, y tu negocio puede definir qué información mostrar sobre la transacción.
-
-`SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET` y `SECRET_SEP24_MORE_INFO_URL_JWT_SECRET` son claves de cifrado que la Anchor Platform utilizará para generar tokens de corta duración que agregará a las URLs proporcionadas a la billetera. Tu servidor de negocio también debe tener estas claves en su entorno para poder verificar la firma del token.
-
-`SEP24_INITIAL_USER_DEADLINE_SECONDS` es un parámetro opcional que define el tiempo en segundos que un usuario tiene para actuar antes de que la transacción pase al siguiente estado. Determina el campo `user_action_required_by`, que indica la fecha límite. Consulta [Métodos JSON-RPC][json-rpc-methods] para ejemplos de uso.
-
-## Probar con la Billetera Demostrativa
-
-¡Las billeteras ahora deberían poder descubrir, autenticar e iniciar transacciones con tu servicio! Tu proyecto y archivos fuente deberían verse algo así.
-
-<CodeExample>
-
-```
-├── dev.env
-├── docker-compose.yaml
-├── config
-│   ├── dev.assets.yaml
-│   ├── dev.stellar.toml
-```
-
-</CodeExample>
-
-Tu entorno ahora debería verse así.
-
-<CodeExample>
-
-```bash
-# dev.env
-ASSETS_TYPE=file
-ASSETS_VALUE=/home/dev.assets.yaml
-
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/home/dev.stellar.toml
-
-SEP10_ENABLED=true
-SEP10_HOME_DOMAIN=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret encryption key"
-
-SEP24_ENABLED=true
-SEP24_INTERACTIVE_URL_BASE_URL=http://localhost:8081
-SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET="your encryption key shared with your business server"
-SECRET_SEP24_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-```
-
-</CodeExample>
-
-Para probar esto, ve a la [Billetera Demostrativa Stellar][stellar-demo-wallet].
-
-[![billetera de demostración conectada a la plataforma anchor](../../assets/anchor-platform-sep24-demo-wallet.png)](../../assets/anchor-platform-sep24-demo-wallet.png)
-
-Inicia una transacción haciendo lo siguiente:
-
-- Crea un nuevo keypair
-- Haz clic en el botón "Agregar Activo" e introduce
-  - el código del activo Stellar en tu archivo `stellar.toml`
-  - tu dominio de inicio, `localhost:8080`
-- Selecciona el desplegable y haz clic en "Depósito SEP-24", luego haz clic en "Iniciar"
-
-La billetera de demostración debería poder encontrar tu archivo `stellar.toml`, autenticarse usando el keypair Stellar que acabas de crear e iniciar una transacción. Sin embargo, cuando la billetera de demostración intenta abrir la URL proporcionada por la Anchor Platform, verás una página no encontrada.
-
-[![billetera de demostración después de iniciar una transacción](../../assets/anchor-platform-sep24-demo-wallet-widget.png)](../../assets/anchor-platform-sep24-demo-wallet-widget.png)
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
-[sep1-ap]: ../sep1/README.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/example.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/example.mdx
deleted file mode 100644
index da72700f39..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/example.mdx
+++ /dev/null
@@ -1,438 +0,0 @@
----
-title: Ejemplo
-sidebar_position: 40
----
-
-La integración con la Anchor Platform involucra tres áreas clave:
-
-- Crear una experiencia de usuario basada en la web que se pueda abrir en una vista web móvil
-- Proporcionar actualizaciones del estado de las transacciones a la Anchor Platform
-- Obtener actualizaciones del estado de las transacciones desde la Anchor Platform
-
-## Crear una experiencia de usuario basada en la web
-
-La Anchor Platform no ofrece una interfaz de usuario blanca que tu negocio pueda utilizar, y en su lugar espera que el negocio cree su propia interfaz de usuario y sistema backend. No crearemos toda una experiencia de usuario de entrada y salida en esta guía, pero cubriremos las formas en que tu producto existente debería actualizarse para ser compatible con la Anchor Platform.
-
-### Autenticación
-
-Si tu negocio tiene un producto existente de entrada y salida, probablemente tengas un sistema existente para la autenticación de usuarios. Sin embargo, dado que la Anchor Platform autentica al usuario antes de proporcionar la URL del negocio, requerir que el usuario pase por otra forma de autenticación es en realidad innecesario. De esta manera, se puede pensar en la Anchor Platform como si proporcionara una forma alternativa de autenticación.
-
-El negocio es libre de continuar requiriendo que los usuarios se autentiquen utilizando su sistema existente, pero la experiencia de usuario ideal omitiría este paso y crearía una sesión autenticada para el usuario si ya se han autenticado utilizando su cuenta Stellar.
-
-La Anchor Platform agrega un parámetro de consulta `token` JWT a la URL del negocio dada a la aplicación de billetera. Este token está firmado por el valor previamente configurado `SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET`, e incluye la información que necesitas para identificar al usuario. El proceso debería verse algo como esto:
-
-1. Pasa el `token` agregado a la URL de tu sistema backend
-2. Verifica la firma en el `token` y comprueba su caducidad
-3. Crea una sesión autenticada para el usuario identificado por `token.sub`
-
-El contenido decodificado del `token` se verá algo como esto:
-
-<CodeExample>
-
-```json
-{
-  "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
-  "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB:1234567",
-  "exp": 1516239022,
-  "data": {
-    "first_name": "John",
-    "last_name": "Doe",
-    "email": "johndoe@example.com"
-  }
-}
-```
-
-</CodeExample>
-
-Ten en cuenta que el valor `sub` identifica al usuario utilizando una cuenta Stellar y un entero. Este será el valor cuando las aplicaciones custodiales que utilizan una cuenta ómnibus autentiquen con tu servicio. Cuando las billeteras no custodiales se autentican, el token puede verse ligeramente diferente.
-
-<CodeExample>
-
-```json
-{
-  "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
-  "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB",
-  "exp": 1516239022,
-  "data": {
-    "client_domain": "api.vibrantapp.com",
-    "first_name": "John",
-    "last_name": "Doe",
-    "email": "johndoe@example.com"
-  }
-}
-```
-
-</CodeExample>
-
-El valor `sub` aquí solo contiene una clave pública para identificar al usuario, y el campo `data.client_domain` identifica la aplicación de billetera utilizada para autenticar.
-
-En ambos casos, toda la información en el objeto `data` es opcional, y solo estará presente si la billetera proporciona esa información.
-
-Vamos a agregar un servidor backend a nuestro archivo de composición que se utilizará para verificar el token y crear sesiones web autenticadas para los usuarios que inician transacciones.
-
-<CodeExample>
-
-```yaml
-# docker-compose.yaml
----
-business-server:
-  build: .
-  ports:
-    - "8081:8081"
-  env_file:
-    - ./dev.env
-  depends_on:
-    - platform-server
-```
-
-</CodeExample>
-
-Vamos a crear un contenedor Docker simple para nuestra aplicación.
-
-<CodeExample>
-
-```docker
-FROM node:19
-
-WORKDIR /home
-COPY . .
-RUN npm install
-
-CMD ["node", "server.js"]
-```
-
-</CodeExample>
-
-Ahora vamos a crear una aplicación NodeJS mínima.
-
-<CodeExample>
-
-```bash
-yarn init -y
-yarn add express jsonwebtoken
-touch server.js
-```
-
-</CodeExample>
-
-A continuación se presenta un ejemplo de un servidor backend autenticando a un usuario usando NodeJS.
-
-<CodeExample>
-
-```js
-# server.js
-const express = require("express");
-const jwt = require("jsonwebtoken");
-const app = express();
-const port = process.env.BUSINESS_SERVER_PORT;
-
-app.use(express.json());
-
-/*
- * We'll store user session data in memory, but production systems
- * should store this data somewhere more persistent.
- */
-const sessions = {};
-
-/*
- * Create an authenticated session for the user.
- *
- * Return a session token to be used in future requests as well as the
- * user data. Note that you may not have a user for the stellar account
- * provided, in which case the user should go through your onboarding
- * process.
- */
-app.post("/session", async (req, res) => {
-  let decodedPlatformToken;
-  try {
-    decodedPlatformToken = validatePlatformToken(req.body.platformToken);
-  } catch (err) {
-    res.status = 400;
-    res.send({ "error": err });
-    return;
-  }
-  let user = getUser(decodedPlatformToken.sub);
-  let sessionToken = jwt.sign(
-    { "jti": decodedPlatformToken.jti },
-    process.env.SESSION_JWT_SECRET
-  );
-  sessions[sessionToken] = user;
-  res.send({
-    "token": sessionToken,
-    "user": user
-  });
-});
-
-/*
- * Validate the signature and contents of the platform's token
- */
-function validatePlatformToken(token) {
-  if (!token) {
-    throw "missing 'platformToken'";
-  }
-  let decodedToken;
-  try {
-    decodedToken = jwt.verify(token, process.env.SECRET_SEP10_JWT_SECRET);
-  } catch {
-    throw "invalid 'platformToken'";
-  }
-  if (!decodedToken.jti) {
-    throw "invalid 'platformToken': missing 'jti'";
-  }
-  return decodedToken;
-}
-
-/*
- * Query your own database for the user based on account:memo string parameter
- */
-function getUser(sub) {
-  return null;
-}
-
-app.listen(port, () => {
-    console.log(`business server listening on port ${port}`);
-});
-```
-
-</CodeExample>
-
-Ejecuta esto con el servidor de plataforma y la base de datos e inicia una nueva transacción con la [billetera demo][stellar-demo-wallet]. Luego, enviaremos el token a nuestro servidor.
-
-<CodeExample>
-
-```bash
-curl \
-  -X POST \
-  -H 'Content-Type: application/json' \
-  -d '{"platformToken": "<paste the token from the URL here>"}' \
-  http://localhost:8081/session | jq
-```
-
-</CodeExample>
-
-## Proporcionando actualizaciones a la plataforma
-
-Vamos a crear un endpoint para nuestro servidor de negocio que acepte la información recopilada en nuestra interfaz de usuario.
-
-<CodeExample>
-
-```js
-# server.js
-
-// Production systems should either let the Anchor Platform generate its own memos
-// or have your custodial service generate a memo for each transaction.
-const transactionMemos = {};
-
-app.post("/transaction", async (req, res) => {
-  let sessionToken;
-  try {
-    sessionToken = validateSessionToken(req.headers.get("authorization"));
-  } catch (err) {
-    res.status = 400;
-    res.send({ "error": err })
-    return;
-  }
-  // assuming this is a withdrawal transaction, we'll provide a memo, which is
-  // required by our third-party custodian to credit us the payment. When the
-  // payment is made with this memo, we can match the on-chain payment with the
-  // transaction in the Anchor Platform's database.
-  transactionMemos[req.body.transaction.id] = parseInt(Math.random() * 100000);
-  let rpcRequestBody = [
-    {
-      "id": 1,
-      "jsonrpc": "2.0",
-      "method": "request_onchain_funds",
-      "params": {
-        "transaction_id": req.body.transaction.id,,
-        "message": "waiting for the user to provide off-chain funds.",
-        "amount_in": {
-          "amount": req.body.amount_in.amount,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "amount_out": {
-          "amount": req.body.amount_out.amount,
-          "asset": "iso4217:USD"
-        },
-        "fee_details": {
-          "total": req.body.fee_details.total,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "destination_account": "GD...G",
-        "memo": transactionMemos[req.body.transaction.id],
-        "memo_type": "id"
-      }
-    }
-  ];
-  let platformResponse;
-  try {
-    platformResponse = await updatePlatformTransaction(rpcRequestBody);
-  } catch (err) {
-    res.status = 500;
-    res.send({ "error": err })
-    return;
-  }
-  res.send({
-    "transaction": platformResponse.records[0]
-  });
-});
-
-function validateSessionToken(authorizationHeader) {
-    let parts = authorizationHeader.split(" ");
-    if (parts.length != 2 || parts[0] != "Bearer") {
-        throw "invalid authorization header format";
-    }
-    let sessionToken = parts[1];
-    try {
-        jwt.verify(sessionToken, process.env.SESSION_JWT_SECRET);
-    } catch {
-        throw "invalid session token";
-    }
-    if (!sessions[sessionToken]) {
-        throw "expired session";
-    }
-    return sessionToken;
-}
-
-async function updatePlatformTransaction(requestBody) {
-  let response = await fetch(
-    `${process.env.PLATFORM_SERVER}`,
-    {
-      method: "POST",
-      headers: {
-        "Content-Type": "application/json"
-      },
-      body: JSON.stringify(requestBody)
-    }
-  );
-  if (response.status != 200) {
-    throw `unexpected status code: ${response.status}`;
-  }
-  return await response.json();
-}
-```
-
-</CodeExample>
-
-Esto actualizará la base de datos de la Anchor Platform con la información proporcionada y permitirá que las aplicaciones de billeteras obtengan esta información actualizada para poder transmitirla de nuevo al usuario. Ya deberías haber informado al usuario sobre los montos de la transacción y que tu negocio está esperando la llegada del pago on-chain, pero proporcionar estas actualizaciones permite a los usuarios ver el estado de sus transacciones a través de su aplicación móvil sin tener que abrir de nuevo la interfaz de usuario del negocio.
-
-:::note
-
-En este momento, la Anchor Platform no envía notificaciones a la aplicación de billetera cuando los estados de las transacciones cambian, sin embargo, está en nuestra hoja de ruta añadir estas notificaciones o "solicitudes de callback" para que las aplicaciones de billetera no tengan que consultar la Anchor Platform para actualizaciones.
-
-:::
-
-## Obteniendo actualizaciones de la plataforma
-
-Si solo usas la Anchor Platform para exponer las API SEP a las aplicaciones de billetera, entonces no tendrás una razón fuerte para obtener actualizaciones del estado de las transacciones desde la Anchor Platform, principalmente porque no actualizará el estado de la transacción hasta que hagas solicitudes de `JSON-RPC API`.
-
-Sin embargo, si utilizas la Anchor Platform para monitorear la red Stellar en busca de pagos entrantes (asociados con transacciones de retirada de fondos), la Anchor Platform actualizará los estados de las transacciones cuando se reciban pagos.
-
-Hay dos formas de obtener actualizaciones de la Anchor Platform,
-
-- Consultando el endpoint `GET /transactions/:id` de la API de la plataforma para las transacciones que esperas un pago
-- Transmitiendo eventos de cambio del estado de la transacción desde un clúster de Kafka
-
-Mientras que transmitir cambios de estado de transacciones desde un clúster de Kafka puede ser un enfoque más robusto y escalable, vamos a utilizar el método de consulta en esta guía. Configurar y usar un clúster de Kafka será el tema de una sección diferente de la documentación.
-
-Primero, configuremos la Anchor Platform para observar la red Stellar en busca de pagos entrantes.
-
-<CodeExample>
-
-```yaml
-# docker-compose.yml
----
-stellar-observer:
-  image: stellar/anchor-platform:latest
-  command: --stellar-observer
-  env_file:
-    - ./dev.env
-  volumes:
-    - ./config:/home
-  depends_on:
-    - db
-```
-
-</CodeExample>
-
-El comando `--stellar-observer` inicia un proceso que monitoriza las cuentas de distribución configuradas en tu archivo `config.yaml` para pagos de retirada.
-
-Si se envía un pago a una de estas cuentas y el memo adjunto a la transacción coincide con un valor de `memo` proporcionado o generado por la Anchor Platform, la Anchor Platform considerará la transacción con la que el memo está asociado como recibida y actualizará el estado de la transacción a `pending_anchor`. Lo hace realizando una solicitud de `JSON-RPC API`, así que necesitamos configurar la URL que debe usar.
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_BASE_URL=http://platform-server:8085
-```
-
-</CodeExample>
-
-Hagamos algunas adiciones al archivo `server.js` para que podamos consultar la Anchor Platform por nuestros pagos esperados.
-
-<CodeExample>
-
-```js
-// server.js
-...
-/*
- * Fetch the transaction data from the Platform API
- *
- * Production systems should have proper retry mechanisms.
- */
-async function getPlatformTransaction(transactionId) {
-  let response = await fetch(`${process.env.PLATFORM_SERVER}/transactions/${transactionId}`)
-  if (response.status != 200) {
-    throw `unexpected status code: ${response.status}`;
-  }
-  return await response.json();
-}
-
-(async () => {
-  while (true) {
-    await new Promise(r => setTimeout(r, 2000));
-    let requestPromises;
-    for (const transactionId in transactionMemos) {
-      requestPromises.push(getPlatformTransaction(transactionId))
-    }
-    let transactions = await new Promise.all(requestPromises);
-    for (const transaction in transactions) {
-      // assuming all requests were successful
-      if (transaction.status == "pending_anchor") {
-        // initiate off-chain delivery of funds
-        console.log(`received payment for transaction ${transaction.id}`);
-      }
-    }
-  }
-})()
-```
-
-</CodeExample>
-
-## Implementación de ejemplo completa
-
-Stellar proporciona una implementación de ejemplo de servidor de negocio para SEP-24. Está dividida en dos partes: 1) una interfaz de usuario web, accesible para el usuario final; y 2) una implementación backend, utilizada para obtener y enviar actualizaciones desde/hacia la Anchor Platform.
-
-El código para la interfaz de usuario web se puede encontrar [aquí][sep-24-ref-ui]
-
-El código para el backend es parte de la Anchor Platform, y está disponible como un [submódulo][sep-24-ref].
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/faq.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/faq.mdx
deleted file mode 100644
index 497bfb095d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/faq.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Preguntas Frecuentes
-sidebar_position: 50
----
-
-### ¿Cómo Usar JWTs?
-
-As part of the flow, once a user makes a request, i.e. an interactive withdrawal/deposit request, it will be processed by the Anchor Platform and forwarded to your service. The Anchor Platform will make a `GET` call to `<configured url>?token=<jwt token>`.
-
-This JWT token will contain:
-
-1. `sub` es la cuenta asociada con esta transacción. Puede ser utilizada para identificar la cuenta del usuario. Ten en cuenta que este valor puede ser diferente de la cuenta que se usará para recibir/enviar fondos. `jti` es el hash de la transacción.
-2. `sub` is the account associated with this transaction. Se puede utilizar para identificar la cuenta de usuario. Ten en cuenta que este valor puede ser diferente de la cuenta que se utilizará para recibir/enviar fondos.
-3. `jti` es el hash de la transacción.
-4. `data` es la carga útil adicional que ha establecido el usuario. Siempre contendrá el `asset` de Stellar que desea depositar o retirar. Si lo proporciona el cliente, también contendrá el `amount` que el usuario desea transaccionar, el `client_domain` de la billetera verificada durante la autenticación SEP-10, y `client_name` (definido como 'name' en la configuración de [clients] si se proporciona), y la preferencia de `lang` (idioma) del usuario.
-
-### ¿Cómo Proporcionar Tarifas?
-
-Actualmente, se recomienda proporcionar tarifas/tasas de intercambio en el iFrame/vista web de tu aplicación.
-
-El estándar [SEP-24] proporciona un endpoint `/fee` para permitir a las empresas establecer tarifas estáticas para sus transacciones. Sin embargo, actualmente no está admitido por la Anchor Platform.
-
-:::note
-
-El endpoint /fee será desaprobado en el futuro.
-
-:::
-
-### ¿Cómo identificar la cuenta del usuario?
-
-Debes usar el campo `sub` del token JWT. Para billeteras de custodia, este valor estará en el formato `account:memo`. Usa el memo para identificar al usuario. Para billeteras no custodiales, simplemente usa el valor `sub` en sí, que será igual a la cuenta del usuario. Utiliza el memo para identificar al usuario. Para billeteras no custodiales, simplemente utiliza el valor `sub` en sí, que será igual a la cuenta de usuario.
-
-### ¿Cómo identificar la billetera?
-
-Utiliza los atributos `data.client_domain` dentro del token JWT. En presencia de la configuración de [clients], el token JWT incorporará adicionalmente el campo `data.client_name`, permitiendo la identificación de la billetera. En presencia de la configuración de [clients], el token JWT también incorporará el campo `data.client_name`, permitiendo la identificación de la billetera.
-
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[clients]: ../sep10/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/getting-started.mdx
deleted file mode 100644
index e6017649b4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/getting-started.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía te llevará a través de la configuración e integración con la Anchor Platform con el propósito de desarrollar un servicio de ingreso y salida compatible con [SEP-24][sep-24], el protocolo estandarizado del ecosistema para depósitos y retiradas de fondos.
-
-Al aprovechar el soporte de la Anchor Platform para SEP-24, las empresas hacen que su servicio de ingreso y salida esté disponible como una experiencia dentro de la aplicación a través de aplicaciones basadas en Stellar como billeteras y exchanges, ampliando su alcance y conectando con los usuarios a través de las aplicaciones que ya utilizan.
-
-Antes de continuar con esta sección, asegúrate de haber [instalado][installation-ap] ya la Plataforma Anchor y configurado las funciones necesarias requeridas por SEP-24: [SEP-1 (Archivo de Información Stellar)][sep1-ap], [SEP-10 (Autenticación Stellar)][sep10-ap] y [SEP-45 (Autenticación Web Stellar para cuenta de contrato)][sep45-ap].
-
-## La experiencia básica del usuario
-
-La experiencia completa del cliente para un depósito y una retirada de fondos es algo como esto:
-
-1. El cliente abre la aplicación de billetera SEP-24 de su elección
-2. El cliente selecciona un activo para depositar y la billetera encuentra un anchor (los clientes también podrían elegir el anchor específico)
-3. Una vez que la billetera se autentica con el anchor, el cliente comienza a ingresar su información de KYC y transacción solicitada por el anchor
-4. La billetera proporciona instrucciones, y el cliente deposita moneda fiat real con el anchor (por ejemplo, realiza una transferencia bancaria)
-5. Una vez que la billetera recibe el depósito, el cliente recibe el activo tokenizado en la red Stellar desde la cuenta de distribución del anchor
-
-El cliente puede luego utilizar el activo digital en la red Stellar para remesas, pagos, comercio, reserva de valor, o otro caso de uso no listado aquí. En alguna fecha posterior, el cliente podría decidir retirar sus activos de la red Stellar, lo que podría lucir algo así:
-
-1. El cliente abre su aplicación de billetera
-2. El cliente selecciona el activo para la retirada y la billetera encuentra el anchor
-3. Después de autenticarse con el anchor, la billetera abre la URL interactiva proporcionada y permite al cliente ingresar su información de transacción (el KYC ya ha sido recopilado)
-4. Después de solicitar la aprobación del cliente, la billetera envía la cantidad especificada del saldo del activo del cliente a la cuenta de distribución del anchor en Stellar
-5. Una vez que el anchor recibe el pago, el cliente recibe los fondos retirados mediante transferencia bancaria.
-
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/integration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/integration.mdx
deleted file mode 100644
index 97bbb5177e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/integration.mdx
+++ /dev/null
@@ -1,1021 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-import { AttributeTable } from "@site/src/components/AttributeTable";
-import Security from "../component/security/security.mdx";
-import UsingApiKey from "../component/security/api_key.mdx";
-import UsingJwt from "../component/security/jwt.mdx";
-import Rpc from "../component/rpc/rpc.mdx";
-import RpcRequest from "../component/rpc/request.mdx";
-import RpcResponse from "../component/rpc/response.mdx";
-import RpcError from "../component/rpc/error.mdx";
-import Observer from "../component/observer/observer.mdx";
-
-Uno de los principales puntos de interacción con la Anchor Platform es notificar a la Anchor Platform sobre eventos relacionados con la transacción.
-
-En general, querrás proporcionar actualizaciones para los siguientes eventos:
-
-- Tu negocio está procesando la información KYC proporcionada por el usuario
-- Tu negocio está listo para recibir fondos del usuario
-- Tu negocio ha recibido fondos del usuario
-- Tu negocio ha enviado fondos al usuario
-- Tu negocio ha procesado una devolución para la transacción del usuario
-- Tu negocio experimentó un error inesperado
-
-Esto se hace realizando solicitudes JSON-RPC al endpoint de la API de la plataforma. Las solicitudes JSON-RPC te permiten actualizar el estado de la transacción. Para mover la transacción a un estado específico, es necesario realizar una solicitud JSON-RPC correspondiente y pasar los datos que se requieren por este método RPC.
-
-La API JSON-RPC de la Anchor Platform está diseñada para notificar a la plataforma sobre cambios en el estado de la transacción. Dado esto, la API será llamada cada vez que un usuario o el anchor realice alguna acción que avance el estado de la transacción en el flujo.
-
-La comunicación desde la Anchor Platform sobre actualizaciones de transacciones, actualizaciones de clientes y creación de cotizaciones se maneja a través del servicio de eventos. Esta es una función opcional que necesita ser configurada por separado de la integración SEP-6. Para más información, consulta [Manejo de eventos][event-handling].
-
-Puedes encontrar más información sobre el flujo y los estados de la transacción en el [documento del protocolo SEP-24][sep-24]
-
-## Callbacks
-
-La Anchor Platform depende del servidor de negocios para proporcionar y almacenar información sobre cotizaciones.
-
-### Cotizaciones y Tarifas
-
-Para admitir el exchange de activos no equivalentes, la Anchor Platform expone una API compatible con SEP-38 para proporcionar cotizaciones para el exchange. La API de cotizaciones se utiliza para proporcionar al usuario la cantidad esperada del activo que recibirá a cambio del activo que está enviando. La API de cotizaciones también se utiliza para proporcionar al usuario las tarifas esperadas para la transacción. Por lo tanto, tu servidor de negocios debe implementar la [API de tarifas][rate-callback] para proporcionar cotizaciones a la Anchor Platform.
-
-## Asegurando la API de la Plataforma
-
-<Security />
-
-### Usando Clave API
-
-<UsingApiKey />
-
-### Usando JWT
-
-<UsingJwt />
-
-## Realizando Solicitudes JSON-RPC
-
-<Rpc />
-
-### Solicitud JSON-RPC
-
-<RpcRequest />
-
-### Respuesta JSON-RPC
-
-<RpcResponse />
-
-### Códigos de Error
-
-<RpcError />
-
-## Actualizando la Transacción de Depósito a Través de JSON-RPC
-
-El diagrama de flujo de depósito SEP-24 define la secuencia/reglas de la transición del estado de la transacción y un conjunto de métodos JSON-RPC que deberían ser llamados para cambiar ese estado. No puedes definir el estado que quieres establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define estructuras de datos que espera en la solicitud. Si la solicitud no contiene un atributo requerido, la Anchor Platform devolverá un error y no cambiará el estado de la transacción.
-
-[![sep24 deposit flow](../../assets/sep24-deposit-flow-diagram.png)](../../assets/sep24-deposit-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen la manera más corta.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden ser omitidos.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en un estado de error o ha caducado.
-
-:::
-
-### Listo para Recibir Fondos
-
-El primer paso del flujo de depósito después de iniciar el depósito en sí es recolectar KYC. Generalmente se realiza en la aplicación web, pero también puede ser proporcionada opcionalmente por la aplicación de billetera, usando [SEP-9]. Una vez que se recolecta la KYC necesaria, se debe realizar una solicitud JSON-RPC `request_offchain_funds`.
-
-<CodeExample>
-
-```json
-// request-offchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_offchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request offchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es la cantidad que el usuario debe enviar al negocio.
-- `amount_out` es la cantidad que el usuario recibirá.
-- `fee_details` es el total de tarifas cobradas por el negocio.
-- `asset` es parte del campo `amount_x` y está en un formato SEP-38. En este ejemplo, está configurado en USD, asumiendo que el usuario realizó una transferencia bancaria al sistema usando USD.
-
-La información sobre las cantidades (entrada/salida/tarifa) es requerida si quieres mover la transacción del estado `incompleto` al estado `pending_user_transfer_start`. Si el estado de la transacción cambia de `pending_anchor` a `pending_user_transfer_start`, puedes omitir definir las cantidades.
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-offchain-funds.json
-```
-
-</CodeExample>
-
-:::tip
-
-Cuando el proceso KYC es largo (por ejemplo, verificación de ID), se aconseja primero establecer el estado de la transacción a `pending_anchor` utilizando la solicitud JSON-RPC `notify_interactive_flow_completed`. Esto indicará al usuario que se está procesando el KYC.
-
-:::
-
-### Procesando Información KYC
-
-:::tip
-
-Este paso es opcional. La mayoría de los negocios no lo utilizan. Puedes omitirlo y pasar al [siguiente paso](#funds-received).
-
-Usar este estado es recomendable cuando la verificación de KYC pueda necesitar ser realizada de manera asincrónica.
-
-:::
-
-Debes especificar los campos `amount_x`.
-
-<CodeExample>
-
-```json
-// kyc-in-process.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_interactive_flow_completed",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Interactive flow completed.",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh kyc-in-process.json
-```
-
-</CodeExample>
-
-### Fondos Recibidos
-
-Si se recibieron fondos offchain, querrás proporcionar una información de transacción actualizada.
-
-<CodeExample>
-
-```json
-// offchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds received",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `funds_received_at` es la fecha y hora de recepción de fondos
-- `external_transaction_id` es el ID de la transacción en la red externa
-
-Los campos de cantidad son opcionales. Si se omiten, se tomarán los valores de solicitudes JSON-RPC anteriores.
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-received.json
-```
-
-</CodeExample>
-
-### Esperando Fondos del Usuario
-
-En el mundo real, el proceso de confirmación de transferencia puede tardar. En tales casos, las transacciones deben establecerse en un nuevo estado que indique que se ha recibido la confirmación de la transferencia pero que los fondos propiamente dichos aún no han sido recibidos.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Enviando Fondos Enchain
-
-A continuación, envía una transacción en la red Stellar para satisfacer una solicitud del usuario. Después de la finalización de la transacción, es necesario enviar la solicitud JSON-RPC `notify_onchain_funds_sent` para notificar al usuario que los fondos se enviaron con éxito.
-
-<CodeExample>
-
-```json
-// onchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds sent",
-      "stellar_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `stellar_transaction_id` is the transaction id on Stellar network of the transfer
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-sent.json
-```
-
-</CodeExample>
-
-Después de esta solicitud JSON-RPC, la transacción se transferirá al estado `completed`.
-
-### Envío de Pago a Través de Servicio de Custodia
-
-La Anchor Platform proporciona la posibilidad de enviar un pago a través de servicios de custodia, como Fireblocks. Para realizar un pago a través del servicio de custodia, es necesario realizar la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// do-stellar-payment.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "do_stellar_payment",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Custody payment started"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh do-stellar-payment.json
-```
-
-</CodeExample>
-
-Después del procesamiento exitoso del pago en un servicio de custodia, la Anchor Platform automáticamente realizará la solicitud JSON-RPC `notify_onchain_funds_sent` y el estado de la transacción cambiará a `completed`.
-
-:::caution
-
-Una cuenta de usuario puede no estar lista para recibir fondos. Puedes verificar que la cuenta haya establecido una [trustline](/docs/learn/glossary#trustline). De lo contrario, puedes establecer el estado de la transacción a `pending_trust` para indicar que el anchor está esperando que el usuario establezca la trustline.
-
-Si la integración de custodia está habilitada, la Anchor Platform validará esto automáticamente por ti.
-
-:::
-
-### Trust Pendiente
-
-Este estado debe ser establecido si un pago requiere una trustline de activo que no fue configurada por el usuario. Hay dos maneras en las que la transacción puede ser movida al estado `pending_trust`. La primera es procesando un pago a través de un servicio de custodia en caso de que detecte que la trustline no está configurada. La segunda es cuando el propio negocio detecta que falta la trustline y quiere notificar al usuario que debe ser configurada. Para mover la transacción al estado `pending_trust`, es necesario realizar la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// request-trust.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_trust",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine not configured"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-trust.json
-```
-
-</CodeExample>
-
-:::info
-
-El pago a través del servicio de custodia verifica periódicamente si la trustline fue configurada. Si lo fue, automáticamente enviará un pago a un servicio de custodia y cambiará el estado de la transacción a `pending_stellar`.
-
-:::
-
-### Configuración de Confianza
-
-Este estado debe ser establecido si el negocio ha detectado que la trustline fue o no fue configurada por el usuario.
-
-<CodeExample>
-
-```json
-// trust-set.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_trust_set",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine set",
-      "success": "true"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `success` flag que define si la trustline fue o no configurada por el usuario
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh trust-set.json
-```
-
-</CodeExample>
-
-:::info
-
-Dependiendo del `success` flag, el estado de la transacción cambiará a `pending_stellar` si la trustline fue establecida, o a `pending_anchor` si no lo fue.
-
-:::
-
-### Envío de Reembolso a Través de Servicio de Custodia
-
-Existe la posibilidad de devolver fondos al usuario (reembolso). Puedes reembolsar la suma completa (reembolso completo) o realizar un conjunto de reembolsos parciales. Además, si el usuario envió más dinero del esperado, puedes reembolsar una parte de la suma al usuario y enviar el resto como fondos enchain.
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::info
-
-Si la suma de los reembolsos es menor que `amount_in`, el estado de la transacción se establecerá en `pending_anchor`. Solo si la suma de los reembolsos es igual a `amount_in`, el estado de la transacción se establecerá en `refunded`.
-
-:::
-
-### Reembolso Pendiente
-
-Es similar a [Reembolso enviado](#refund-sent), pero maneja un caso cuando un reembolso ha sido enviado a la red externa pero aún no está confirmado. El estado de la transacción se establece en `pending_external`. Este es el estado que se establecerá cuando se espera que Bitcoin u otra red de cripto externa complete una transacción, o cuando se espera una transferencia bancaria.
-
-### Error de Transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, se requiere establecer el estado de la transacción en `error`. Puedes usar el campo de mensaje para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario ha realizado una transferencia, debes hacer una recuperación de la transacción, y luego puedes volver a procesar la transacción o iniciar un reembolso.
-
-:::
-
-### Transacción Caducada
-
-Tu negocio puede querer manejar transacciones abandonadas caducando aquellas que han permanecido inactivas durante un cierto período. Para lograr esto, verifica el estado de la transacción utilizando el endpoint `GET /transactions` y ordena los resultados por la marca de tiempo `user_action_required_by`. Si la marca de tiempo ha pasado, ejecuta manualmente la lógica apropiada, como caducar la transacción o iniciar un reembolso automático, según el estado actual de la transacción. Por ejemplo, para caducar la transacción, el negocio debería cambiar el estado de la transacción a `expired`:
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no se puede usar después de que el usuario ha realizado una transferencia.
-
-:::
-
-### Transacción en Espera
-
-En casos raros, puedes querer pausar la transacción actual y solicitar más información del usuario (después de haber recibido la transferencia). Esto podría usarse para casos de uso de cumplimiento.
-
-<CodeExample>
-
-```json
-// transaction-hold.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_on_hold",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction is on hold. Please contact customer support to resolve the hold."
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-hold.json
-```
-
-</CodeExample>
-
-### Recuperación de Transacción
-
-El estado de la transacción puede ser cambiado de `error/expired` a `pending_anchor`. Después de la recuperación, puedes reembolsar los activos recibidos o proceder con el procesamiento de la transacción. Para recuperar una transacción, es necesario realizar la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-## Actualizando transacciones de retirada de fondos vía JSON-RPC
-
-Este diagrama define una secuencia/reglas de la transición del estado de las transacciones para el flujo de retirada de SEP-24.
-
-[![flujo de retirada de sep24](../../assets/sep24-withdrawal-flow-diagram.png)](../../assets/sep24-withdrawal-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden ser omitidos.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en un estado de error o ha caducado.
-
-:::
-
-Una vez que el flujo de depósito ha terminado, implementar la retirada de fondos es sencillo. Algunas partes del flujo son similares y se pueden reutilizar.
-
-El punto de partida tanto para la retirada como para el depósito es el mismo.
-
-### Listo para recibir fondos
-
-Similar al depósito, el siguiente paso es notificar al usuario que el anchor está listo para recibir fondos. Sin embargo, dado que tu servicio estará recibiendo transacciones a través de la red Stellar, la actualización se verá diferente.
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "iso4217:USD"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `memo` Valor del memo que debe anexarse a la transacción
-- `memo_type` Tipo de memo que el anchor debe anexar a la transacción
-- `destination_account` Cuenta de destino
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-:::tip
-
-Configurar `memo`, `memo_type` y `destination_account` es opcional.
-
-Si la integración con un custodio de terceros está habilitada, la Anchor Platform puede generar `memo`, `memo_type` y `destination_address` si se elige un `deposit_info_generator_type` correspondiente. Además, puedes proporcionar `memo` y `memo_type` a la solicitud como se muestra arriba. Ten en cuenta que el memo debe ser único, esto es lo que ayuda a asociar las transacciones de Stellar con las transacciones de SEP.
-
-Si tu negocio gestiona los activos, la Anchor Platform puede generar memos para ti. Cuando el estado cambia a `pending_user_transfer_start`, la Anchor Platform establece `memo` y `memo_type` automáticamente (solo si no están incluidos en la solicitud).
-
-:::
-
-:::note
-
-La cuenta de Stellar que se utilizará para recibir fondos debe estar configurada.
-
-:::
-
-### Procesando información de KYC
-
-Este paso es opcional y es similar a [Procesando información de KYC](#processing-kyc-information) del flujo de depósito.
-
-### Fondos recibidos
-
-Si se recibieron fondos en cadena, necesitas proporcionar montos y cambiar el estado de la transacción a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método será llamado automáticamente por el servidor de custodia si la integración de custodia está habilitada.
-
-:::
-
-### Monto actualizado
-
-Si se recibieron fondos en cadena, pero por alguna razón el `amount_in` difiere del especificado en el flujo interactivo (`amount_expected`), puedes actualizar `amount_out` y `fee_details` para que correspondan al `amount_in` real. El estado de la transacción en este caso no cambiará y será igual a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// amounts-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_amounts_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Amounts updated",
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh amounts-updated.json
-```
-
-</CodeExample>
-
-:::note
-
-Solo `amount_out` y `fee_details` pueden ser actualizados utilizando esta solicitud JSON-RPC, y no necesitas especificar los activos de los montos.
-
-:::
-
-### Fondos fuera de la cadena enviados
-
-Para completar la transacción y cambiar su estado a `completed`, necesitas hacer la solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Fondos fuera de la cadena disponibles
-
-Puedes mover el estado de la transacción a `pending_user_transfer_complete` si se enviaron fondos fuera de la cadena, y si está listo para que el usuario / destinatario lo recoja.
-
-<CodeExample>
-
-```json
-// offchain-funds-available.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_available",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds available",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-available.json
-```
-
-</CodeExample>
-
-### Fondos fuera de la cadena pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago ha sido enviado a una red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Reembolso enviado
-
-La lógica de reembolso funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Reembolso enviado](#refund-sent) del flujo de depósito.
-
-### Enviando reembolso vía servicio de custodia
-
-La integración con un servicio de custodia te permite hacer un reembolso a través de un servicio de custodia, como Fireblocks.
-
-<CodeExample>
-
-```json
-// do-stellar-refund.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "do_stellar_refund",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Do stellar refund",
-      "refund": {
-        "amount": {
-          "amount": 9,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh do-stellar-refund.json
-```
-
-</CodeExample>
-
-:::note
-
-Similar al flujo de depósito, puedes hacer un reembolso completo o un conjunto de reembolsos parciales. La transacción permanecerá en estado `pending_anchor` hasta que la suma de los reembolsos sea inferior a `amount_in`. Si la suma de los reembolsos es igual a `amount_in`, la Anchor Platform cambiará automáticamente el estado de la transacción a `refunded`.
-
-:::
-
-### Error de transacción
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Error de transacción](#transaction-error) del flujo de depósito.
-
-### Transacción caducada
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Transacción caducada](#expired-transaction) del flujo de depósito.
-
-### Transacción en espera
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Transacción en espera](#on-hold-transaction) del flujo de depósito.
-
-### Recuperación de transacción
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Recuperación de transacción](#transaction-recovery) del flujo de depósito.
-
-## Seguimiento de transacciones de Stellar
-
-<Observer />
-
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[event-handling]: ../events/README.mdx
-[rate-callback]: ../../api-reference/callbacks/README.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
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
deleted file mode 100644
index 1a3757b649..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/setting-up-production-server.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: Configurar un Servidor de Producción
-sidebar_position: 60
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Una vez que el servidor de prueba esté en vivo y hayas probado ambos flujos de depósito y retirada de fondos, es hora de comenzar con el despliegue real conectado a KYC real y proveedores de banking rails reales. Antes de utilizar cualquier API bancaria, es crucial que realices una auditoría de seguridad completa en el sistema para asegurarte de que no haya vulnerabilidades.
-
-## Desplegando un Entorno Seguro
-
-Asegúrate de mantener el servidor de prueba activo y desplegar el sistema de producción (mainnet) en un entorno separado. Tener dos despliegues te permite validar nuevas características en la testnet antes de moverlas al despliegue final de producción. También puedes tener un tercer entorno de preproducción si hay un gran equipo trabajando en esta base de código y/o habrá muchos empujes que se deben probar internamente antes de compartir con otras instituciones.
-
-Para cambiar a la red pública (mainnet) de Stellar, solo tienes que cambiar la [contraseña de la red](/docs/networks#network-passphrases) (para autenticar solicitudes) y la [URL de Horizon](https://horizon.stellar.org/).
-
-Puedes copiar tus configuraciones de desarrollo existentes para crear una configuración de producción.
-
-Primero, necesitas cambiar tu archivo de información (`stellar.toml`):
-
-<CodeExample>
-
-```toml
-# stellar.toml
-NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"
-```
-
-</CodeExample>
-
-A continuación, cambia tu configuración de Anchor Platform en el archivo `production.env`:
-
-### Para la conexión al servidor Horizon:
-
-<CodeExample>
-
-```bash
-# production.env STELLAR_NETWORK_NETWORK="Public"
-STELLAR_NETWORK_HORIZON_URL="https://horizon.stellar.org"
-```
-
-</CodeExample>
-
-### Para la conexión al servidor RPC de Stellar:
-
-<CodeExample>
-
-```bash
-# production.env STELLAR_NETWORK_NETWORK="Public"
-STELLAR_NETWORK_RPC_URL="https://mainnet.sorobanrpc.com"
-```
-
-</CodeExample>
-
-## Conectando a KYC Real
-
-La mayoría de los anchors necesitan recopilar información de [Conoce a tu Cliente](https://en.wikipedia.org/wiki/Know_your_customer) para cumplir con las regulaciones locales antes de honrar depósitos y retiros. El flujo de KYC generalmente consiste en un formulario simple que recopila información relevante sobre el usuario, como nombre, correo electrónico, dirección, edad y número de identificación emitido por el gobierno.
-
-Cómo manejes KYC depende de ti: hay muchos servicios que proporcionan soluciones KYC a través de APIs y iFrames, y validan los datos de entrada y sincronizan con bases de datos gubernamentales para verificar los requisitos. Cada jurisdicción tiene requisitos KYC específicos, y difieren de una jurisdicción a otra, así que es mejor encontrar un proveedor de KYC específico de cada país que satisfaga tus necesidades.
-
-Algunos países requieren diferentes campos de KYC dependiendo de la cantidad a depositar o retirar. Si ese es el caso en tu jurisdicción y necesitas adaptar tus formularios KYC según la cantidad de depósito o retirada de fondos, simplemente agrega un campo de cantidad antes del formulario de KYC y asegúrate de que los campos de KYC se actualicen según ese valor.
-
-La información de KYC debe vincularse a la sesión creada a través de [Stellar Web Authentication](../sep10/README.mdx) y, en consecuencia, al usuario, así que solo necesitas preguntar al usuario una vez. Después de que el primer flujo de KYC esté completo, un usuario no debería tener que ingresar la información nuevamente.
-
-Asegúrate de que los errores y mensajes de validación sean claros e incluyan instrucciones sobre qué hacer a continuación para garantizar una buena experiencia de usuario y aumentar la tasa de conversión de KYC. También debes localizar los mensajes según el idioma y la ubicación del usuario.
-
-## Rellenando el Formulario de KYC
-
-Rellenar el formulario de KYC de forma anticipada es una excelente manera de reducir la fricción para comenzar a utilizar un anchor, y las billeteras suelen proporcionar un conjunto de campos que se utilizan comúnmente en todo el ecosistema. En resumen, el anchor puede renderizar el formulario KYC con los valores del usuario que se enviaron previamente por la billetera en los endpoints `/transactions/deposit/interactive` y `/transactions/withdraw/interactive`.
-
-Todos los campos de [SEP-9](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md) pueden ser enviados por billeteras en los endpoints mencionados anteriormente, pero los más comunes son: correo electrónico, nombre, apellido y número de teléfono. Además, aún debes habilitar que los campos rellenados anticipadamente sean editables, ya que el usuario podría haber ingresado un nombre diferente en el proceso de registro de la billetera y podría querer editarlo antes de finalizar el proceso de KYC del Anchor.
-
-Todos los datos de SEP-9 que se enviaron desde la billetera son parte del [JWT Interactivo](./faq.mdx#how-to-use-jwts), enviado por Anchor Platform
-
-## Conectando a Banking Rails Reales
-
-Se espera que los emisores de tokens respaldados por fiat gestionen una reserva completa. Eso significa que hay una relación de 1:1 entre los tokens de la red Stellar y el dinero en el banco. Dado que cada token fiat en Stellar está respaldado por un activo subyacente del mundo real y puede ser canjeado por él, los emisores de tokens respaldados por fiat necesitan conectarse a los bancos reales para validar depósitos de usuarios (a través de transferencias bancarias, pagos con tarjeta de crédito, etc.) y completar retiros de usuarios (generalmente a través de transferencias bancarias). Si eres un anchor que honra depósitos y retiros de un token que emite otra organización, seguirás un proceso similar. y para completar los retiros de usuarios (generalmente a través de transferencias bancarias). Si eres un anchor que honra depósitos y retiros de un token que otra organización emite, seguirás un proceso similar.
-
-Para obtener (y identificar) una transferencia de usuario, los emisores generalmente adoptan uno de dos enfoques:
-
-- API Polling: esta opción consiste en obtener la API del banco, a través de un trabajo cron, para comprobar el estado actualizado de la lista de transferencias recibidas por (y enviadas desde) la cuenta bancaria del emisor. Una vez que el sistema confirma una nueva transacción e identifica que se relaciona con un depósito específico, puede enviar los fondos digitales a la cuenta de ese usuario.
-- Webhook: no todas las vías bancarias admiten esta opción, pero es la más sencilla en términos de lógica de back-end. En este enfoque, el banco accede proactivamente a un endpoint del emisor una vez que recibe una nueva transferencia, actualizando esa información en la base de datos del emisor. El emisor puede igualar esa transacción a un depósito en proceso existente y validar que el usuario pueda recibir sus fondos digitales.
-
-Algunos bancos (y países) tienen infraestructura de transferencia que permite la creación de una sola cuenta bancaria por transferencia; otros requieren que los usuarios agreguen un parámetro de identificación a sus transferencias. Algunos bancos (y países) tienen infraestructura de transferencias que permite la creación de una cuenta bancaria por transferencia; otros requieren que los usuarios añadan un parámetro de identificación a sus transferencias. Algunos bancos proporcionan el número de identificación del usuario en la información de la transacción para que los emisores puedan igualar eso con la información proporcionada en el formulario KYC.
-
-Asegúrate de realizar una auditoría de seguridad completa en tus sistemas cuando las conexiones de banking rails estén en su lugar. Algunos bancos proporcionan una API de prueba que se puede utilizar para el desarrollo y el despliegue en testnet o entornos de preproducción, lo que significa que puedes probar y auditar la base de código antes de pasar a una integración bancaria lista para producción final. Para mayor seguridad, algunos anchors también prefieren agregar un paso final manual antes de aprobar las transferencias de retirada de fondos. En términos de experiencia de usuario, esta aprobación manual es aceptable siempre que los tiempos de espera se alineen con las expectativas del usuario, lo que generalmente significa que no sean más de un par de horas.
-
-## Probando Casos Extremos
-
-Una vez que tu aplicación esté completamente funcional, es una buena idea probar diferentes escenarios y casos extremos para asegurarte de que el sistema se comporte como se espera. Aquí hay una lista de sugerencias de pruebas que deberían cubrir una gran cantidad de los casos extremos de la aplicación:
-
-### Pruebas Generales
-
-- Prueba la usabilidad del flujo interactivo
-- Prueba la interfaz utilizando diferentes informaciones regionales, y verifica el contenido traducido, incluidos mensajes de error, respuestas, formato de fechas y formato de números
-
-### Pruebas de KYC
-
-- Verifica que KYC aparezca con un nuevo SK de billetera
-- Verifica que KYC no acepte entradas con formato incorrecto y que los mensajes de error sean comprensibles
-- Verifica que puedes utilizar la misma información de KYC (correo electrónico, número de teléfono, nombre de usuario, etc.) múltiples veces
-- Verifica que puedes pasar por KYC múltiples veces con el mismo SK de Stellar.
-
-### Prueba Interactiva
-
-- Verifica que el flujo de depósito se complete y que los banking rails estén funcionando
-- Verifica que no puedes realizar una retirada de un valor superior al saldo actual
-- Verifica que el flujo de retirada se complete y que los banking rails estén funcionando
-
-### Pruebas de Seguridad
-
-- Asegúrate de que los endpoints de la plataforma estén seguros
-
-## Pulido e Internacionalización
-
-Admitir dos idiomas (inglés y el idioma del país de la moneda fiat) permite a los usuarios tener una experiencia fluida mientras navegan a través de las pantallas, y apoya a instituciones internacionales (como billeteras) que necesitan probar el producto antes de iniciar nuevas integraciones.
-
-Puedes admitir múltiples idiomas en tu aplicación web utilizando el parámetro `Accept-Language` de los encabezados de la solicitud http para localizar el contenido y permitir que los usuarios cambien eso de manera simple (por ejemplo, un ícono de bandera en la barra superior). Si una billetera específica no envía el parámetro de encabezado, recomendamos mostrar al usuario una pantalla de selección de idioma al inicio de los procesos de depósito y retirada de fondos. Una vez que un usuario elija un idioma, puedes almacenar su selección así que solo necesitas preguntarles una vez. Además de localizar el texto, asegúrate de verificar el formato de los números, las fechas, etc.
-
-Tener un grupo de beta testers es una excelente manera de verificar si hay algún caso extremo que necesita pulido y de confirmar que el sistema está funcionando bien con una variedad de entradas de usuario. Puedes probar en beta utilizando una fase de lanzamiento suave antes de que comiences a dedicar esfuerzo al marketing y la distribución. Documentar el proceso de pruebas con capturas de pantalla y videos es muy útil para futuras auditorías de seguridad y brinda claridad y confianza en el producto a nuevos socios y usuarios potenciales.
-
-## Conectando a Billeteras
-
-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.
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/README.mdx
deleted file mode 100644
index 28a964c434..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Pagos Transfronterizos (SEP-31)
-sidebar_position: 70
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-31 permite un medio por el cual las billeteras y/o exchanges interactúan con el conjunto existente de servicios del lado del envío de Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/configuration.mdx
deleted file mode 100644
index ba71732383..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/configuration.mdx
+++ /dev/null
@@ -1,346 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Modificar un Archivo de Información Stellar
-
-Empecemos por modificar nuestro archivo `stellar.toml` creado [anteriormente][sep1-ap]. Las billeteras necesitan saber que la funcionalidad SEP-31 es admitida por tu negocio, y también necesitan conocer todas las monedas que admites.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-DIRECT_PAYMENT_SERVER = "http://localhost:8080/sep31"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que necesitarás crear otro archivo para tu implementación de producción que utilice la frase de paso de la red pública, las URL de servicio de producción, tus cuentas de distribución de mainnet y clave de firma, así como las cuentas de emisión de mainnet de los activos que utiliza tu servicio.
-
-## Habilitar Pagos Transnacionales
-
-Ahora estás listo para habilitar los pagos transnacionales con la API SEP-31. Especifica lo siguiente en tu archivo `dev.assets.yaml`.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep31:
-      enabled: true
-      quotes_supported: true
-      quotes_required: true
-      receive:
-        min_amount: 0
-        max_amount: 10000
-        methods:
-          - ACH
-```
-
-</CodeExample>
-
-La información proporcionada en los objetos `sep31` y `send` se mapea estrechamente con la información que se expondrá a la aplicación de billetera usando el endpoint [`GET /info`][sep31-get-info] de SEP-31. La Anchor Platform también utiliza esta información para validar las solicitudes hechas a tu servicio. `sep31.fields.transaction` debe quedar vacío y se eliminará en una futura versión, pero puedes ajustar los valores de `send.min_amount` y `send.max_amount` de acuerdo a los límites de tu servicio.
-
-Los valores `sep31.quotes_supported` y `sep31.quotes_required` determinan si las organizaciones emisoras pueden y están obligadas a solicitar una tasa de cambio utilizando el endpoint [SEP-38 `POST /quote`][sep38-post-quote]. Casi todos los emisores prefieren este enfoque para que puedan comunicar la tasa a sus clientes antes de proceder.
-
-Agrega la siguiente variable a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP31_ENABLED=true
-```
-
-</CodeExample>
-
-Senders should now be able to discover, authenticate, and initiate transactions with your service! Ejecuta el siguiente comando para iniciar la Anchor Platform.
-
-<CodeExample>
-
-```bash
-docker compose up
-```
-
-</CodeExample>
-
-Verifica que tu API esté en vivo.
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep31/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente.
-
-<CodeExample>
-
-```json
-{
-  "receive": {
-    "USDC": {
-      "enabled": true,
-      "quotes_supported": true,
-      "quotes_required": true,
-      "min_amount": 0,
-      "max_amount": 10000,
-      "fields": {
-        "transaction": {}
-      }
-    }
-  }
-}
-```
-
-</CodeExample>
-
-## Habilitar la API de KYC de Clientes
-
-Las empresas deben recopilar y validar la información de KYC de los clientes para los cuales facilitan transacciones. Los clientes determinan qué información de KYC necesita ser recopilada y envían esa información a través de una API KYC SEP-12 alojada por la Anchor Platform, pero la Anchor Platform nunca almacena información personal identificable (PII). En su lugar, reenvía las solicitudes de los clientes al servidor del negocio y devuelve las respuestas del negocio al cliente, actuando como un servidor proxy.
-
-Consulta la [especificación de la API KYC de Anchor Platform][platform-api-kyc] para obtener detalles sobre los endpoints que deben ser implementados en el servidor de tu negocio.
-
-Para hacer que esta API esté disponible para los clientes, agreguemos la URL del servicio a nuestro Archivo de Información Stellar.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-KYC_SERVER = "http://localhost:8080/sep12"
-```
-
-</CodeExample>
-
-Habilitemos también en nuestro entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP12_ENABLED=true
-```
-
-</CodeExample>
-
-Finalmente, tenemos que definir los tipos de clientes de tu negocio. Cada tipo de cliente requiere un conjunto diferente de información de KYC. Por ejemplo, puedes ofrecer tu servicio de pagos transnacionales en dos jurisdicciones regulatorias distintas, por lo que los clientes en diferentes jurisdicciones tienen diferentes requisitos de KYC y estarían representados usando diferentes tipos.
-
-:::info
-
-Actualmente, los tipos de clientes deben ser mutuamente exclusivos, lo que significa que un cliente no puede ser más de un tipo.
-
-Esta limitación está en vigor porque la Anchor Platform no puede validar si un cliente está aprobado para un tipo específico de transacción, como una que envía una gran cantidad. Solo puede validar que un cliente está aprobado para uno de los tipos de clientes definidos. Esta limitación se eliminará en una futura versión.
-
-:::
-
-En esta guía, solo tendremos dos tipos: un tipo de cliente emisor y un tipo de cliente receptor. Actualmente, nuestros tipos de clientes están definidos en nuestra configuración de activos, pero esto cambiará en una futura versión.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-sep31:
-  sep12:
-    sender:
-      types:
-        sep31-sender:
-          description: customers sending to recipients
-    receiver:
-      types:
-        sep31-receiver:
-          description: customers receiving from senders
-```
-
-</CodeExample>
-
-Pingueemos nuevamente el endpoint de información para verificar. Después de `docker compose up`, ejecuta el siguiente comando:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep31/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente:
-
-<CodeExample>
-
-```json
-{
-  "receive": {
-    "USDC": {
-      "enabled": true,
-      "quotes_supported": true,
-      "quotes_required": true,
-      "min_amount": 0,
-      "max_amount": 10000,
-      "fields": {
-        "transaction": {}
-      }
-    }
-  }
-}
-```
-
-</CodeExample>
-
-## Habilitar la API RFQ
-
-Las empresas necesitan proporcionarle a sus contrapartes del lado de envío una API de [Tasa][get-rates-api] para verificar las tasas de cambio que están ofreciendo entre el activo on-chain que se utiliza para la liquidación y el activo fiat que se utiliza para pagar al receptor. Si la tasa es competitiva, los emisores también deben poder solicitar un compromiso a la tasa actualmente ofrecida por el negocio durante un corto período de tiempo.
-
-La Anchor Platform proporciona la [API RFQ SEP-38][sep38] a los emisores para este propósito.
-
-Para hacer que esta API esté disponible para los clientes, agreguemos la URL del servicio a nuestro Archivo de Información Stellar.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-DIRECT_PAYMENT_SERVER = "http://localhost:8080/sep31"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-KYC_SERVER = "http://localhost:8080/sep12"
-QUOTE_SERVER = "http://localhost:8080/sep38"
-```
-
-</CodeExample>
-
-Habilitemos también en nuestro entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP38_ENABLED=true
-```
-
-</CodeExample>
-
-También necesitamos habilitar el uso de USDC en esta API, así como agregar un activo off-chain con el cual se pueda intercambiar.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep31:
-      enabled: true
-      quotes_supported: true
-      quotes_required: true
-      receive:
-        min_amount: 0
-        max_amount: 10000
-        methods:
-          - ACH
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - iso4217:BRL
-      country_codes:
-        - BR
-  - id: iso421:BRL
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-      country_codes:
-        - BR
-      significant_decimals: 2
-      buy_delivery_methods:
-        - name: PIX
-          description: Have BRL sent directly to your bank account.
-```
-
-</CodeExample>
-
-¡Probemos que tu API de RFQ está en vivo! Después de `docker compose up`:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep38/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente:
-
-<CodeExample>
-
-```json
-{
-  "assets": [
-    {
-      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-    },
-    {
-      "asset": "iso4217:BRL",
-      "country_codes": ["BR"],
-      "buy_delivery_methods": [
-        {
-          "name": "PIX",
-          "description": "Have BRL sent directly to your bank account."
-        }
-      ]
-    }
-  ]
-}
-```
-
-</CodeExample>
-
-## Configurar la Autenticación de la API de Callback
-
-Así como tu negocio necesitará hacer solicitudes a la Anchor Platform, la Anchor Platform necesitará hacer solicitudes a tu negocio. Agreguemos autenticación a estas solicitudes también.
-
-<CodeExample>
-
-```bash
-# dev.env
-CALLBACK_API_BASE_URL=http://server:8081
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-SECRET_CALLBACK_API_AUTH_SECRET=<your jwt encryption key>
-```
-
-</CodeExample>
-
-`CALLBACK_API_BASE_URL` utiliza `server` en lugar de `localhost` como el host porque la Anchor Platform hará solicitudes a tu servidor de negocio desde dentro de la red local creada por docker compose. When configuring your service in a staging or production environment, make sure to update your service urls.
-
-Definiremos el servidor que implementa los endpoints definidos en la API de Callback en la siguiente sección.
-
-[sep31-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#get-info
-[sep1-ap]: ../sep1/README.mdx
-[get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
-[sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep38-post-quote]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#post-quote
-[platform-api-kyc]: ../../api-reference/callbacks/get-customer.api.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/getting-started.mdx
deleted file mode 100644
index 6dd6393638..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/getting-started.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía te guiará a través de la configuración e integración con la Anchor Platform con el propósito de desarrollar un servicio de recepción de pagos transnacionales compatible con [SEP-31][sep-31], el protocolo estandarizado del ecosistema para pagos transnacionales.
-
-Al aprovechar el apoyo de la Anchor Platform para SEP-31, las empresas hacen que su servicio sea compatible con el conjunto existente de servicios de envío de Stellar.
-
-:::info
-
-A medida que mejoramos la documentación, partes de esta guía que son relevantes para otros casos de uso pueden trasladarse a sus propias secciones.
-
-:::
-
-Antes de continuar con esta sección, asegúrate de que ya has [instalado][installation-ap] la Plataforma Anchor y configurado las características necesarias requeridas por SEP-31: [SEP-1 (Archivo de información Stellar)][sep1-ap], [SEP-10 (Autenticación Stellar)][sep10-ap] y [SEP-45 (Autenticación web Stellar para cuentas contractuales)][sep45-ap].
-
-[sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/integration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/integration.mdx
deleted file mode 100644
index eae9a79192..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep31/integration.mdx
+++ /dev/null
@@ -1,669 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Integrarse con la Anchor Platform para facilitar pagos transnacionales implica implementar lo siguiente, como mínimo:
-
-- [`GET /customer`][get-customer] & [`PUT /customer`][put-customer] puntos finales de la API KYC para solicitar y recopilar datos KYC de los clientes
-- [`GET /rate`][get-rate] punto final de la API RFQ para proporcionar tasas de FX entre los activos on-chain y off-chain admitidos
-- `GET /transactions` solicitudes para obtener actualizaciones sobre los estados de las transacciones de la Anchor Platform (documentación próximamente)
-- [`JSON-RPC`][json-rpc-methods] solicitudes para actualizar los estados de las transacciones de la Anchor Platform
-
-Lo siguiente también puede ser requerido dependiendo de tu caso de uso:
-
-- [`DELETE /customer`][delete-customer] si tu negocio desea o está obligado a permitir que los remitentes soliciten la eliminación de datos del cliente
-
-## Crear un Servidor Empresarial
-
-Primero, vamos a crear un servidor empresarial y añadirlo a nuestro archivo de docker compose.
-
-<CodeExample>
-
-```yaml
-version: "3.8"
-
-services:
-  sep-server:
-    image: stellar/anchor-platform:latest
-    command: --sep-server
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-    ports:
-      - "8080:8080"
-    depends_on:
-      - db
-  platform-server:
-    image: stellar/anchor-platform:latest
-    command: --platform-server
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-    ports:
-      - "8085:8085"
-    depends_on:
-      - db
-
-  server:
-    build: .
-    ports:
-      - "8081:8081"
-    env_file:
-      - ./dev.env
-  db:
-    image: postgres:14
-    ports:
-      - "5432:5432"
-    env_file:
-      - ./dev.env
-```
-
-</CodeExample>
-
-A continuación, crea un servidor web simple utilizando el lenguaje de programación de tu preferencia y un `Dockerfile` que inicie el servidor. `docker compose up` debería iniciar correctamente los tres servicios.
-
-Esta guía no proporciona una implementación de ejemplo de los puntos finales, pero puedes encontrar más información sobre los esquemas de solicitud y respuesta en la [Anchor Platform API Reference][ap-api], y las secciones a continuación ampliarán los conceptos importantes para entender al implementar los puntos finales.
-
-## Puntos Finales de Callback de Clientes
-
-La Anchor Platform nunca almacena la PII de tus clientes y, en su lugar, actúa como un servidor proxy entre las aplicaciones cliente y tu negocio, reenvíando solicitudes y respuestas a la otra parte. Actualmente, las solicitudes y respuestas son casi idénticas a las definidas en la [SEP-12 KYC API specification][sep12].
-
-### Identificando Clientes
-
-Los clientes pueden ser identificados utilizando dos enfoques.
-
-El primer enfoque utiliza una cuenta Stellar y un memo. Al usar la Anchor Platform para facilitar pagos transnacionales, la organización remitente utiliza su propia cuenta Stellar, la que se usó para autenticarse a través de [SEP-10 Stellar Authentication][ap-sep10], al registrar clientes con tu negocio. Los memos se utilizan para distinguir clientes únicos que provienen de la misma organización remitente.
-
-El segundo enfoque utiliza IDs de clientes generados por tu servicio. Por ejemplo, si una organización remitente está registrando un cliente, tu negocio recibirá una solicitud `PUT /customer` como la siguiente:
-
-<CodeExample>
-
-```json
-{
-  "account": "GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47",
-  "memo": "780284017",
-  "type": "sep31-sender",
-  "first_name": "John",
-  "last_name": "Doe",
-  "email": "johndoe@example.com"
-}
-```
-
-</CodeExample>
-
-En este ejemplo, la clave pública `GDJ...X47` identifica la organización remitente, y el memo `780284017` identifica al cliente. Los memos son normalmente enteros de 64 bits, pero también pueden ser otros tipos de datos, por lo que deben guardarse como cadenas. En respuesta, tu negocio debe devolver un ID de cliente.
-
-<CodeExample>
-
-```json
-{
-  "id": "fb5ddc93-1d5d-490d-ba5f-2c361cea41f7"
-}
-```
-
-</CodeExample>
-
-Tu servidor empresarial puede usar cualquier identificador para los clientes siempre que sea una cadena.
-
-Después del registro de un cliente, la organización remitente puede usar cualquiera de los enfoques al verificar el estado del cliente. Por ejemplo, puedes obtener una solicitud `GET /customer` como la siguiente:
-
-<CodeExample>
-
-```
-/customer?account=GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47&memo=780284017&type=sep31-sender
-```
-
-</CodeExample>
-
-O, la organización remitente podría usar el identificador que devolviste cuando registraron originalmente al cliente.
-
-<CodeExample>
-
-```
-/customer?id=fb5ddc93-1d5d-490d-ba5f-2c361cea41f7&type=sep31-sender
-```
-
-</CodeExample>
-
-Tu negocio necesitará mantener un mapeo entre la cuenta y el memo utilizados para registrar originalmente al cliente y el ID que devuelves en la respuesta, así como los datos KYC proporcionados. En futuras iteraciones de la Anchor Platform, es posible que mantengamos este mapeo para tu negocio para que solo tengas que trabajar con los IDs que generas.
-
-### Tipos de Clientes
-
-Tu negocio probablemente requiera diferentes conjuntos de información KYC dependiendo del tipo de cliente. Puedes definir las etiquetas para cada uno de estos tipos de clientes en tu archivo `dev.assets.yaml`, y tus organizaciones remitentes necesitarán entender qué etiqueta utilizar al registrar o consultar el estado de los clientes.
-
-En las solicitudes `PUT /customer`, deberías usar el tipo enviado para evaluar si el remitente ha proporcionado todos los campos requeridos. En las solicitudes `GET /customer`, deberías usar el tipo para determinar el estado del cliente.
-
-### Probar con la Billetera Demo
-
-Puedes probar tu implementación con la [Stellar Demo Wallet][demo-wallet] siguiendo los pasos a continuación.
-
-1. Selecciona "Generar keypair para nueva cuenta"
-2. Selecciona "Crear cuenta"
-3. Selecciona "Agregar Activo" e introduce el código del activo y el dominio principal de la Anchor Platform, `localhost:8080`
-4. Selecciona "Agregar línea de confianza"
-5. Financia tu cuenta con un saldo del activo
-6. Selecciona "SEP-31 Enviar" en el menú desplegable
-
-Deberías ver que la billetera demo encuentra las URL de tu servicio, se autentica y verifica qué campos KYC necesita recopilar. Luego debería presentar un formulario para que introduces los detalles KYC para el remitente y el receptor.
-
-[![billetera demo después de iniciar una transacción](../../assets/anchor-platform-sep31-demo-wallet-widget.png)](../../assets/anchor-platform-sep31-demo-wallet-widget.png)
-
-Una vez que hayas introducido la información solicitada, se enviará esa información a la Anchor Platform, que la enviará a tu servidor empresarial. Una vez que la billetera demo tenga los IDs de los clientes que generaste, iniciará una transacción que debería fallar.
-
-## Punto Final de Callback de Tasas
-
-Una vez que la organización remitente haya registrado a los clientes involucrados en la transacción, necesitará solicitar una cotización, o tasa FX, de tu negocio. La Anchor Platform solicita esta información a tu servidor empresarial utilizando el [`GET /rate` endpoint][get-rate].
-
-### Cotizaciones Firmes vs. Indicativas
-
-Las solicitudes de cotizaciones tendrán un parámetro `type` que puede ser [`indicative`][indicative] o [`firm`][firm]. Si `type=firm`, tu respuesta debe incluir el campo `id` y `expires_at` y reservar la liquidez necesaria para cumplir con esta cotización hasta que la cotización expire. Si `type=indicative`, no devuelvas los campos `id` o `expires_at` porque la tasa proporcionada no se utilizará en una transacción.
-
-Ten en cuenta que el cliente puede solicitar que la cotización expire después de una fecha y hora específica usando el parámetro `expires_after`. Tu negocio debe honrar esta solicitud devolviendo un valor `expires_at` que esté en o después de la fecha y hora solicitadas o rechazar la solicitud con una respuesta 400 Bad Request, que será reenviada al cliente.
-
-### Usando el ID del Cliente
-
-Las solicitudes pueden incluir un parámetro `client_id` que identifica a la organización remitente que solicita la tasa. Puedes usar este parámetro para adherirte a los términos comerciales acordados con esa organización remitente, como ofrecer tarifas con descuento. `client_id` puede no estar presente para solicitudes indicativas, en cuyo caso debe devolverse tu precio de mercado. Actualmente, `client_id` siempre será la clave pública Stellar que la organización remitente utilizó para autenticarse con la Anchor Platform.
-
-### Métodos de Entrega
-
-Es común que las tarifas y comisiones de las empresas difieran dependiendo de los rails de pago utilizados para enviar fondos al destinatario. Si tus métodos de entrega están configurados en tu archivo `asset.yaml`, los clientes siempre proporcionarán el rail de pago que desean que tu negocio use para solicitudes de cotización firme.
-
-Debido a que este punto final se utiliza actualmente solo para pagar remesas en activos off-chain, se usará el `buy_delivery_method`. Si este punto final alguna vez se utiliza en otros flujos de transacciones como depósitos SEP-24, entonces también se puede pasar `sell_delivery_method` para empresas que admiten estos tipos de transacciones.
-
-## Obtener Actualizaciones de Estado de Transacciones
-
-Para facilitar pagos transnacionales, necesitarás poder detectar cuándo una organización remitente ha enviado tu negocio un pago on-chain y determinar qué transacción estaba destinada a cumplir.
-
-La forma más fácil de hacerlo es ejecutar el Stellar Observer, que detectará estos pagos y actualizará el registro de transacciones correspondiente con información sobre el pago. Tu negocio podrá detectar estas actualizaciones consultando el punto final API `GET /transactions` de la Platform.
-
-### Ejecutar el Stellar Observer
-
-El Stellar Observer monitorea el ledger Stellar para pagos realizados a tu(s) cuenta(s) y actualiza los registros de transacciones correspondientes con información de pago on-chain. Para ejecutar el observador, añade lo siguiente a tu archivo de docker compose.
-
-<CodeExample>
-
-```yaml
-services:
-  ...
-  observer:
-    image: stellar/anchor-platform:latest
-    command: --stellar-observer
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-```
-
-</CodeExample>
-
-### Polling de Pagos Recibidos
-
-El Stellar Observer realiza solicitudes JSON-RPC a la API de la Platform cada vez que detecta pagos recibidos por transacciones iniciadas por organizaciones remitentes, actualizando así la fecha y hora `transfer_received_at` de la transacción.
-
-Tu negocio debería consultar periódicamente el punto final API `GET /transactions` de la Platform para detectar estas actualizaciones. Puedes referirte al siguiente ejemplo:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/transactions?sep=31&order_by=transfer_received_at&order=desc
-```
-
-</CodeExample>
-
-La respuesta incluirá una lista de transacciones de pago transnacionales iniciadas por organizaciones remitentes. Esta lista estará ordenada según el momento en que se recibió un pago por esa transacción. Para cada transacción devuelta, tu negocio debería verificar si ya ha detectado el pago por esa transacción. Si lo has hecho, has detectado todos los pagos realizados a tu(s) cuenta(s).
-
-## Actualizar Transacciones a Través de JSON-RPC
-
-El diagrama de flujo SEP-31 define la secuencia/reglas de la transición de estado de la transacción y un conjunto de métodos JSON-RPC que deben llamarse para cambiar ese estado. No puedes definir el estado que deseas establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define estructuras de datos que espera en la solicitud. Si la solicitud no contiene los atributos requeridos, la Anchor Platform devolverá un error y no cambiará el estado de la transacción.
-
-[![diagrama de flujo sep31](../../assets/sep31-transition-diagram.png)](../../assets/sep31-transition-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el flujo más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en un estado de error o ha caducado.
-
-:::
-
-Puedes crear una [plantilla][sep24-integration-make-json-rpc-request] para realizar solicitudes JSON-RPC a la Anchor Platform.
-
-Este capítulo también contiene información sobre el formato de [solicitud][sep24-integration-rpc-request]/[respuesta][sep24-integration-rpc-response] y [códigos de error][sep24-integration-error-codes] que pueden ser devueltos por la Anchor Platform.
-
-### Listo para Recibir Fondos
-
-Las transacciones SEP-31 deberían estar inicialmente en el estado `pending_receiver`. Para solicitar fondos del Sending Anchor, el Receiving Anchor debería cambiar el estado de la transacción a `pending_sender` haciendo la siguiente solicitud RPC:
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-El estado de la transacción cambiará a `pending_sender`.
-
-### Fondos Recibidos
-
-Si el Sending Anchor ha enviado los fondos, el Receiving Anchor debería cambiar el estado de la transacción a `pending_receiver` haciendo la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-El estado de la transacción cambiará a `pending_receiver`.
-
-### Fondos Offchain Enviados
-
-Para completar la transacción y cambiar su estado a `completed`, necesitas hacer una solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Fondos Offchain Pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago ha sido enviado a la red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Verificando la Información del Cliente
-
-En algunos casos, el Receiving Anchor puede necesitar solicitar información actualizada al Sending Anchor. Por ejemplo, el banco le dice al Receiving Anchor que el nombre del Cliente Receptor proporcionado es incorrecto o le falta un segundo nombre. Dado que esta información fue enviada a través de SEP-12, la transacción debería ir al estado `pending_customer_info_update` hasta que el Sending Anchor realice otra solicitud SEP-12 `PUT /customer` para actualizar. El Sending Anchor puede verificar qué campos necesitan ser actualizados al hacer una solicitud SEP-12 `GET /customer` incluyendo los parámetros id o cuenta y memo. El Receiving Anchor debería responder con un estado `NEEDS_INFO` y `last_name` incluido en los campos descritos.
-
-Después de que el Sending Anchor realice una solicitud SEP-12 `PUT /customer`, llama al método JSON-RPC `notify_customer_info_updated` para actualizar el estado de la transacción. Adicionalmente, llama a este método cada vez que cambie el estado SEP-12 de un cliente, como cuando se está validando la información del cliente y el estado cambia de `NEEDS_INFO` a `PROCESSING`. Esto asegura que cualquier cliente configurado con una URL de callback sea notificado del último estado del cliente, permitiendo al cliente solicitar al usuario que actualice su información.
-
-<CodeExample>
-
-```json
-// notify-customer-info-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_customer_info_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Customer info updated",
-      "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
-      "customer_type": "sep31-receiver" // or sep31-sender
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh notify-customer-info-updated.json
-```
-
-</CodeExample>
-
-### Hacer Reembolso Stellar
-
-La integración con el servicio de custodia te permite hacer reembolsos a través del servicio de custodia, como Fireblocks.
-
-<CodeExample>
-
-```json
-// do-stellar-refund.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "do_stellar_refund",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Do stellar refund",
-      "refund": {
-        "amount": {
-          "amount": 9,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh do-stellar-refund.json
-```
-
-</CodeExample>
-
-:::note
-
-No puedes hacer múltiples reembolsos en el flujo SEP-31. Por esta razón, el monto total del reembolso más la cantidad de la tarifa debería ser igual a `amount_in`. De lo contrario, recibirás un error.
-
-:::
-
-### Reembolso Enviado
-
-Existe la posibilidad de enviar todos los fondos de vuelta al `Sending Anchor` (reembolso). Debes reembolsar la suma total (reembolso completo).
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::note
-
-No puedes hacer múltiples reembolsos en el flujo SEP-31. Por esta razón, la cantidad a reembolsar más la tarifa debería ser igual a `amount_in`. De lo contrario, recibirás un error.
-
-:::
-
-### Error de Transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, es necesario establecer el estado de la transacción en `error`. Puedes usar el campo de mensaje para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario ha realizado una transferencia, deberías hacer una recuperación de la transacción, y luego puedes volver a intentar procesar la transacción o iniciar un reembolso.
-
-:::
-
-### Transacción Caducada
-
-Tu negocio puede querer caducar aquellas transacciones que han sido abandonadas por el usuario después de un tiempo. Es una buena práctica limpiar las transacciones inactivas en estado `incompleto`. Para hacerlo, simplemente cambia el estado de la transacción a `caducado`.
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no se puede usar después de que el usuario haya realizado una transferencia.
-
-:::
-
-### Recuperación de Transacción
-
-El estado de la transacción puede cambiar de `error/expired` a `pending-anchor`. Después de la recuperación, puedes devolver los activos recibidos o continuar con el procesamiento de la transacción. Para recuperar la transacción, es necesario hacer la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-### Configuración
-
-Puedes habilitar estos tipos de transacciones actualizando la configuración de tu archivo `assets.yaml`:
-
-<CodeExample>
-
-```yaml
-items:
-  - ...
-    sep31:
-      quotes_required: false
-```
-
-</CodeExample>
-
-[ap-api]: ../../README.mdx
-[ap-sep10]: ../sep10/README.mdx
-[sep12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[demo-wallet]: https://demo-wallet.stellar.org
-[indicative]: https://www.investopedia.com/terms/i/indicativequote.asp
-[firm]: https://www.investopedia.com/terms/f/firmquote.asp
-[get-customer]: ../../api-reference/callbacks/get-customer.api.mdx
-[put-customer]: ../../api-reference/callbacks/put-customer.api.mdx
-[get-rate]: ../../api-reference/callbacks/get-rates.api.mdx
-[put-customer-callback]: ../../api-reference/callbacks/put-customer.api.mdx
-[delete-customer]: ../../api-reference/callbacks/del-customer.api.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
-[sep24-integration-make-json-rpc-request]: ../sep24/integration.mdx#making-json-rpc-requests
-[sep24-integration-rpc-request]: ../sep24/integration.mdx#json-rpc-request
-[sep24-integration-rpc-response]: ../sep24/integration.mdx#json-rpc-response
-[sep24-integration-error-codes]: ../sep24/integration.mdx#error-codes
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep45/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep45/README.mdx
deleted file mode 100644
index 3cbd1869cb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep45/README.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Autenticación Stellar para Cuentas de Contrato (SEP-45)
-sidebar_position: 55
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Descripción general
-
-Las aplicaciones de billeteras inteligentes Stellar crean sesiones autenticadas con anchors de Stellar demostrando que ellas, o sus usuarios, tienen suficiente control sobre una cuenta de contrato. Una vez autenticada, la aplicación de billetera inteligente utiliza un token de sesión proporcionado por el anchor en solicitudes posteriores a los servicios estandarizados del anchor.
-
-Esto es similar a cómo funciona SEP-10, pero con algunas diferencias:
-
-- El desafío es una lista de entradas de autorización Soroban para una invocación de un contrato SEP-45 que debe ser firmado por los firmantes de la cuenta de contrato.
-- La billetera es responsable de simular la transacción y asegurar que no sea maliciosa.
-- El anchor verifica las entradas de autorización firmadas simulando la transacción en la red.
-
-Se proporciona una implementación del contrato SEP-45 en el [repositorio Anchor Platform][sep-45-contract]. Una instancia de este contrato está desplegada en `CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX` en testnet.
-
-## Habilitar autenticación Stellar para cuentas de contrato
-
-Anchor Platform admite esta forma de autenticación con una configuración mínima por parte del negocio.
-
-### Conectar a Stellar RPC
-
-SEP-45 requiere integración con Stellar RPC para simular transacciones. Anchor Platform puede conectarse al servidor Stellar RPC que elijas.
-
-Puedes usar un proveedor público de Stellar RPC, o puedes ejecutar el tuyo propio. Se puede encontrar una lista de proveedores públicos [aquí][rpc-providers]. El siguiente ejemplo usa el RPC testnet de SDF.
-
-<CodeExample>
-
-```bash
-# dev.env
-STELLAR_NETWORK_RPC_URL=https://soroban-testnet.stellar.org
-```
-
-</CodeExample>
-
-### Habilitar SEP-45
-
-Para habilitar SEP-45, configura las siguientes variables de entorno en tu archivo `dev.env`.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP_45_ENABLED=true
-SEP_45_WEB_AUTH_DOMAIN=localhost:8080
-SEP_45_WEB_AUTH_CONTRACT_ID="CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-SEP_45_HOME_DOMAINS=localhost:8080
-SEP_45_JWT_TIMEOUT=900
-SEP_45_AUTH_TIMEOUT=86400
-```
-
-</CodeExample>
-
-`SEP_45_ENABLED` habilita SEP-45.
-
-`SEP_45_WEB_AUTH_DOMAIN` es el dominio donde se ejecuta el servicio de autenticación (WEB_AUTH_ENDPOINT o WEB_AUTH_FOR_CONTRACTS_ENDPOINT). Este podría ser el mismo que el `home_domain`, un subdominio (por ejemplo, auth.example.com) o un dominio completamente diferente. Se verifica en el desafío para asegurar que el cliente se está comunicando con el endpoint correcto que descubrió a través del `home_domain`.
-
-`SEP_45_WEB_AUTH_CONTRACT_ID` es la ID del contrato del SEP-45. Este es el contrato que se usará para construir el desafío.
-
-`SEP_45_HOME_DOMAINS` es una lista separada por comas de dominios principales que están autorizados a autenticarse con el anchor. Los dominios principales son los dominios que alojan el archivo `stellar.toml`. Este archivo indica a los clientes dónde encontrar el endpoint de autenticación (`WEB_AUTH_FOR_CONTRACTS_ENDPOINT`) y qué clave pública (`SIGNING_KEY`) usará el servidor para los desafíos.
-
-`SEP_45_JWT_TIMEOUT` es el tiempo en segundos durante el cual el token JWT es válido. El valor predeterminado es 900 segundos (15 minutos).
-
-`SEP_45_AUTH_TIMEOUT` es el tiempo en segundos durante el cual el desafío de autenticación es válido. El valor predeterminado es 86400 segundos (24 horas).
-
-### Modificar un archivo de información Stellar
-
-El archivo `stellar.toml` creado [anteriormente][sep1-ap] debe actualizarse para incluir el nuevo endpoint de autenticación y la ID del contrato.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
-WEB_AUTH_CONTRACT_ID = "CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-```
-
-</CodeExample>
-
-`WEB_AUTH_FOR_CONTRACTS_ENDPOINT` es la URL donde se ejecuta el servicio de autenticación. Esta es la URL que los clientes utilizarán para autenticarse con el anchor.
-
-`WEB_AUTH_CONTRACT_ID` es la ID del contrato del SEP-45. Este es el contrato que se usará para construir el desafío.
-
-[sep1-ap]: ../sep1/README.mdx
-[sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
-[sep-45-contract]: https://github.com/stellar/anchor-platform/tree/feature/c-accounts/soroban
-[rpc-providers]: /docs/data/apis/rpc/providers
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/README.mdx
deleted file mode 100644
index 94a82c8e95..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Depósitos y Retiros Programáticos (SEP-6)
-sidebar_position: 65
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-6 permite un medio mediante el cual las billeteras y/o exchanges interactúan con un anchor en nombre de los usuarios, sin requerir que el usuario interactúe directamente con la entrada y salida.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/configuration.mdx
deleted file mode 100644
index 5ec26b1e40..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/configuration.mdx
+++ /dev/null
@@ -1,267 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-# Configuración
-
-Para habilitar los depósitos y retiradas SEP-6, la Anchor Platform debe ser configurada para hacer lo siguiente:
-
-- Proporcionar las URLs de servicio necesarias para los endpoints SEP-6, 12 y 38 en el archivo `stellar.toml`
-- Proporcionar información sobre los activos on-chain y off-chain, así como sobre los métodos de pago, admitidos por tu negocio a través de los endpoints `/info` SEP-6 y SEP-38
-- Admitir los endpoints y callbacks requeridos para solicitar información KYC y proporcionar tasas de cambio
-
-## Habilitar depósitos y retiradas programáticas
-
-Añade las siguientes variables a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_ENABLED=true
-SEP12_ENABLED=true
-SEP38_ENABLED=true
-```
-
-</CodeExample>
-
-### Modificar un archivo de información de Stellar
-
-Let's modify the `stellar.toml` file created [earlier][sep1-ap]. Las billeteras necesitan saber que la funcionalidad SEP-6 es admitida por tu negocio, y también necesitan saber todos los activos Stellar que admites.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-TRANSFER_SERVER = "http://localhost:8080/sep6"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-KYC_SERVER = "http://localhost:8080/sep12"
-ANCHOR_QUOTE_SERVER = "http://localhost:8080/sep38"
-
-# Add support for USDC
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que necesitarás crear otro archivo para tu implementación de producción que utilice la frase de paso de la red pública, las URLs de servicio de producción, tus cuentas de distribución de Mainnet y la clave de firma, así como las cuentas de emisión de Mainnet de los activos que utiliza tu servicio.
-
-### Modificar el archivo de configuración de activos
-
-Ahora estás listo para especificar lo siguiente en tu archivo `dev.assets.yaml`, y cambiar los valores según tu caso de uso. Este archivo de activos de ejemplo habilita la compatibilidad con el USDC de Circle y un USD fiat para depositar y retirar.
-
-Los métodos especificados en las secciones `sep38` son métodos que serán expuestos por el endpoint SEP-38 [`GET /info`][sep38].
-
-Los métodos especificados en las secciones `deposit` y `withdraw` son los métodos que serán expuestos por el endpoint SEP-6 [`GET /info`][sep-6]. Los métodos listados deben coincidir con los métodos definidos en la sección SEP-38 del archivo. Los métodos listados deben coincidir con los métodos definidos en la sección SEP-38 del archivo.
-
-También ten en cuenta que los activos fiat, aquellos con el `schema: iso4217`, no necesitan que se especifiquen los objetos de configuración `sep6_enabled`, `deposit`, o `withdraw`. De la misma manera, los activos Stellar, aquellos con `schema: stellar`, no necesitan que se especifiquen los objetos de configuración `sep38.sell_delivery_methods` o `sep38.buy_delivery_methods`.
-
-<CodeExample>
-
-```yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep6:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - ACH
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - ACH
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - iso4217:USD
-  - id: iso4217:USD
-    significant_decimals: 2
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-      buy_delivery_methods:
-        - name: ACH
-          description: ACH debits for US bank accounts
-      sell_delivery_methods:
-        - name: ACH
-          description: ACH credit for US bank accounts
-```
-
-</CodeExample>
-
-### Gestionando cuentas de distribución
-
-Ten en cuenta que el ejemplo anterior lista un atributo `distribution_account` para la entrada de USDC. Si se especifica, esta cuenta se proporcionará junto con un memo generado aleatoriamente y único por transacción a los clientes como la dirección a la que enviar fondos para las transacciones de retirada de fondos. El memo de la transacción es cómo tú o la Anchor Platform igualarán los fondos recibidos con un registro de transacción en la base de datos de la Anchor Platform.
-
-Si no tienes tu propia cuenta Stellar y en su lugar utilizas un tercero que te proporciona una cuenta Stellar y un memo para poder recibir fondos en tu nombre, como un exchange o custodio, debes omitir el campo `distribution_account` de tu archivo de configuración de activos. En su lugar, necesitas proporcionar la cuenta Stellar y el memo que te gustaría usar para recibir fondos a través de una solicitud a la Anchor Platform [`request_onchain_funds`][request-onchain-funds] de manera individual por transacción.
-
-Para configurar la Anchor Platform para que espere que la cuenta Stellar y el memo sean proporcionados a través de API en lugar de configurados a través del archivo de activos, especifica la siguiente variable de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=none
-```
-
-</CodeExample>
-
-Si utilizas un proveedor de billeteras que sea admitido por el servicio de custodia de la Anchor Platform, como Fireblocks, también puedes configurar la Anchor Platform para conectarse directamente a tu proveedor de billeteras para obtener tus cuentas de distribución y memos. Si esto está configurado, la Anchor Platform también utilizará el proveedor de billeteras para enviar fondos a los clientes. Consulta la sección [servicios de custodia] para más información sobre cómo configurar esta función, pero primero necesitarás especificar un valor diferente para la variable de entorno antes mencionada.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=custody
-```
-
-</CodeExample>
-
-### Habilitar callbacks al servidor del negocio
-
-Los negocios necesitan recopilar y validar la información KYC de los clientes para quienes facilitan transacciones. Los clientes preguntan a tu negocio qué información KYC necesita ser recopilada y envían esa información a través de la API KYC SEP-12 alojada por la Anchor Platform, pero la Anchor Platform nunca almacena información personalmente identificable (PII). En cambio, reenvía las solicitudes de los clientes al servidor del negocio y devuelve las respuestas del negocio al cliente, actuando como un servidor proxy.
-
-Además, los negocios deben proporcionar a los clientes una API [Rates][get-rates-api] para verificar las tasas de cambio que están ofreciendo entre los activos on-chain y off-chain admitidos por el negocio. Si la tasa es competitiva, los clientes también deben poder solicitar un compromiso con la tasa que actualmente se ofrece por el negocio por un corto período de tiempo. De manera similar a la API KYC, la Anchor Platform hace solicitudes a tu servidor de negocio para obtener tasas de cambio y cotizaciones y las devuelve a los clientes.
-
-Para habilitar estas solicitudes a tu servidor de negocio, primero necesitarás agregar tu servidor de negocio al archivo docker compose. Luego, para admitir solicitudes a tu servidor de negocio desde la Anchor Platform, necesitas habilitar callbacks.
-
-<CodeExample>
-
-```bash
-# dev.env
-CALLBACK_API_BASE_URL=http://business-server:3000/callbacks
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
-SECRET_CALLBACK_API_AUTH_SECRET="a secret used to sign JWTs"
-```
-
-</CodeExample>
-
-The above tells the Anchor Platform to include a [JWT][how-to-use-jwt], signed with the configured secret, in the `Authorization` header of requests made to `/callbacks/<callback endpoint>` so your server can authenticate the Anchor Platform before processing requests.
-
-Consulta la [API KYC][platform-api-kyc] y la [API Rates][get-rates-api] para más detalles sobre los endpoints que deben ser implementados en tu servidor de negocio.
-
-### Configuración adicional opcional
-
-`more_info_url` es una URL opcional proporcionada por tu servidor de negocio para que las aplicaciones de billetera muestren información sobre transacciones iniciadas anteriormente. Esta URL es típicamente utilizada por billeteras en sus vistas de historial de transacciones, y tu negocio puede especificar la información que se mostrará sobre la transacción.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP6_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-```
-
-</CodeExample>
-
-Los negocios pueden establecer una fecha límite para las acciones del usuario en transacciones utilizando el campo `user_action_required_by`. Para ejemplos, consulta [JSON-RPC Methods][json-rpc-methods]. Además, el parámetro `initial_user_deadline_seconds` establece un tiempo predeterminado (en segundos) que un usuario tiene para actuar antes de que la transacción pase al estado `EXPIRED`.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_INITIAL_USER_DEADLINE_SECONDS=1209600
-```
-
-</CodeExample>
-
-## Prueba con la billetera de demostración
-
-¡Las billeteras deberían ahora poder descubrir, autenticar e iniciar transacciones con tu servicio! Tus archivos del proyecto y de origen deberían ahora verse algo así.
-
-<CodeExample>
-
-```
-├── dev.env
-├── docker-compose.yaml
-├── config
-│   ├── dev.assets.yaml
-│   ├── dev.stellar.toml
-```
-
-</CodeExample>
-
-Tu entorno debería ahora verse algo así.
-
-<CodeExample>
-
-```bash
-# dev.env
-ASSETS_TYPE=file
-ASSETS_VALUE=/home/dev.assets.yaml
-
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/home/dev.stellar.toml
-
-SEP6_ENABLED=true
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=none
-SEP6_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP6_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-
-SEP10_ENABLED=true
-SEP10_HOME_DOMAIN=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret used to sign JWTs"
-
-SEP12_ENABLED=true
-
-SEP38_ENABLED=true
-
-CALLBACK_API_BASE_URL=http://business-server:3000/callbacks
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
-SECRET_CALLBACK_API_AUTH_SECRET="a secret used to sign JWTs"
-```
-
-</CodeExample>
-
-Para probar esto, ve a la [Stellar Demo Wallet][stellar-demo-wallet].
-
-Inicia una transacción de depósito haciendo lo siguiente:
-
-- Crear un nuevo keypair
-- Haz clic en el botón "Añadir activo" e introduce
-  - el código del activo Stellar en tu archivo `stellar.toml`
-  - tu dominio principal, `localhost:8080`
-- Selecciona el menú desplegable y haz clic en "SEP-6 Deposit", luego haz clic en "Iniciar"
-
-La billetera de demostración debería poder encontrar tu archivo `stellar.toml`, autenticar utilizando el keypair Stellar que acabas de crear y iniciar una transacción.
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep1-ap]: ../sep1/README.mdx
-[stellar-demo-wallet]: https://demo-wallet.stellar.org/
-[get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
-[sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[platform-api-kyc]: ../../api-reference/callbacks/get-customer.api.mdx
-[request-onchain-funds]: ../../api-reference/platform/rpc/methods/request_onchain_funds.mdx
-[how-to-use-jwt]: ../sep24/faq.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/getting-started.mdx
deleted file mode 100644
index 67ddbb9a9d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/getting-started.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía te llevará a través de la configuración e integración con la Anchor Platform con el propósito de desarrollar un servicio de entrada y salida compatible con [SEP-6][sep-6], el protocolo estandarizado del ecosistema para depósitos programáticos y retiros.
-
-Al aprovechar el soporte de Anchor Platform para SEP-6, las empresas pueden hacer que su propio servicio de entrada y salida esté disponible como una experiencia dentro de la aplicación a través de aplicaciones basadas en Stellar como billeteras y exchanges, ampliando su alcance y conectando con los usuarios a través de las aplicaciones que ya utilizan.
-
-Antes de continuar con esta sección, asegúrate de que ya has [instalado][installation-ap] la Plataforma Anchor, y configurado las características necesarias requeridas por SEP-6: [SEP-1 (Archivo de Información Stellar)][sep1-ap], [SEP-10 (Autenticación Stellar)][sep10-ap] y [SEP-45 (Autenticación Web Stellar para cuenta de contrato)][sep45-ap].
-
-## La Experiencia Básica del Usuario
-
-La experiencia completa del cliente para un depósito o retiros utilizando SEP-6 es la siguiente:
-
-1. El cliente abre la aplicación de billetera SEP-6 de su elección
-2. El cliente selecciona un activo para depositar y la billetera encuentra un anchor (los clientes también pueden elegir el anchor específico)
-3. Una vez que la billetera se autentica con el anchor, el cliente comienza a ingresar su información KYC y de transacción solicitada por el anchor
-4. La billetera proporciona instrucciones, y el cliente deposita moneda fiduciaria real con el anchor (como transferencia bancaria)
-5. Una vez que la billetera recibe el depósito, el cliente recibe el activo tokenizado en la red Stellar de la cuenta de distribución del anchor
-
-El cliente puede utilizar luego el activo digital en la red Stellar para remesas, pagos, comercio, reserva de valor, u otro caso de uso no listado aquí. En una fecha posterior, el cliente podría decidir retirar sus activos de la red Stellar, lo que se vería algo así:
-
-1. El cliente abre su aplicación de billetera
-2. El cliente selecciona el activo para el retiro y la billetera encuentra el anchor
-3. Después de autenticarse con el anchor, el cliente puede ingresar su información de transacción y cualquier información KYC adicional que no se haya recopilado ya
-4. Después de pedir la aprobación del cliente, la billetera envía la cantidad especificada del saldo del activo del cliente a la cuenta de distribución del anchor en Stellar
-5. Una vez que el anchor recibe el pago, el cliente recibe los fondos retirados a través de cualquier método admitido por el anchor (como transferencia bancaria)
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/integration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/integration.mdx
deleted file mode 100644
index 47deb12445..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep6/integration.mdx
+++ /dev/null
@@ -1,991 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-import { AttributeTable } from "@site/src/components/AttributeTable";
-import Security from "../component/security/security.mdx";
-import UsingApiKey from "../component/security/api_key.mdx";
-import UsingJwt from "../component/security/jwt.mdx";
-import Rpc from "../component/rpc/rpc.mdx";
-import RpcRequest from "../component/rpc/request.mdx";
-import RpcResponse from "../component/rpc/response.mdx";
-import RpcError from "../component/rpc/error.mdx";
-import Observer from "../component/observer/observer.mdx";
-
-Uno de los puntos principales de interacción con la Anchor Platform es notificar a la plataforma sobre eventos relacionados con las transacciones.
-
-En general, querrás proporcionar actualizaciones para los siguientes eventos.
-
-- Tu negocio requiere que el usuario envíe información KYC para procesar una transacción
-- Tu negocio actualizó los montos de entrada/salida/tasa para una transacción
-- Tu negocio está listo para recibir fondos del usuario
-- Tu negocio ha recibido fondos del usuario
-- Tu negocio ha enviado fondos al usuario
-- Tu negocio ha procesado un reembolso para la transacción del usuario
-- Tu negocio experimentó un error inesperado
-
-Esto se hace realizando solicitudes JSON-RPC al endpoint de la API de la plataforma. Las solicitudes JSON-RPC te permiten actualizar el estado de la transacción. Para mover la transacción a un estado específico, es necesario realizar una solicitud JSON-RPC correspondiente y pasar los datos requeridos por el método RPC.
-
-La API JSON-RPC de Anchor Platform está diseñada para notificar a la plataforma sobre cambios en el estado de la transacción. Dado que, la API se llamará cada vez que un usuario o el anchor realice alguna acción que avance el estado de la transacción en el flujo.
-
-La comunicación de Anchor Platform sobre actualizaciones de transacciones, actualizaciones de clientes y creación de cotizaciones se maneja a través del servicio de eventos. Esta es una característica opcional que debe configurarse por separado de la integración SEP-6. Para más información, consulta [Manejo de Eventos][event-handling].
-
-Puedes encontrar más información sobre el flujo y los estados de las transacciones en el [documento del protocolo SEP-6][sep-6].
-
-## Devoluciones
-
-La Anchor Platform se basa en el servidor del negocio para proporcionar y almacenar información sobre los clientes y las cotizaciones.
-
-### Información del Cliente
-
-La Anchor Platform no almacena información del cliente. En cambio, reenvía todas las solicitudes de clientes SEP-12 al servidor del negocio. El servidor del negocio es responsable de almacenar y gestionar esta información. Por lo tanto, tu servidor debe implementar las [APIs de clientes][customer-callback] para manejar actualizaciones KYC.
-
-### Cotizaciones y Tarifas
-
-Para admitir el exchange de activos no equivalentes, Anchor Platform expone una API compatible con SEP-38 para proporcionar cotizaciones para el exchange. La API de cotizaciones se utiliza para proporcionar al usuario la cantidad esperada del activo que recibirá a cambio del activo que está enviando. La API de cotizaciones también se utiliza para proporcionar al usuario las tarifas esperadas para la transacción. Por lo tanto, tu servidor debe implementar la [API de tarifas][rate-callback] para proporcionar cotizaciones a Anchor Platform.
-
-## Asegurando API de la Plataforma
-
-<Security />
-
-### Usando API Key
-
-<UsingApiKey />
-
-### Usando JWT
-
-<UsingJwt />
-
-## Haciendo Solicitudes JSON-RPC
-
-<Rpc />
-
-### Solicitud JSON-RPC
-
-<RpcRequest />
-
-### Respuesta JSON-RPC
-
-<RpcResponse />
-
-### Códigos de Error
-
-<RpcError />
-
-## Actualizando la Transacción de Depósito (Exchange) a Través de JSON-RPC
-
-El diagrama de flujo de depósito SEP-6 define las secuencias/reglas de la transición del estado de la transacción y un conjunto de métodos JSON-RPC que deben ser llamados para cambiar ese estado. No puedes definir el estado que deseas establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define estructuras de datos que espera en la solicitud. Si la solicitud no contiene los atributos requeridos, la Anchor Platform devolverá un error y no cambiará el estado de la transacción.
-
-El flujo del depósito de exchange es el mismo que el flujo de depósito, excepto que los montos no necesitarán ser recalculados al solicitar fondos offchain, si el usuario ha proporcionado una cotización firme del anchor.
-
-[![Diagrama de flujo de depósito SEP-6](../../assets/sep6-deposit-flow-diagram.png)](../../assets/sep6-deposit-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y se pueden omitir.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en un estado de error o ha caducado.
-
-:::
-
-### Verificando Información KYC
-
-Aunque la Anchor Platform no requiere que un cliente tenga su información KYC recolectada antes de iniciar un depósito, tu negocio puede querer recolectar esta información antes de que el cliente realice una transferencia. Escuchando eventos de creación de transacciones, o sondeando el [`GET /transactions`][get-transactions] endpoint, puedes determinar si una transacción requiere que el cliente actualice su información. Los campos requeridos de SEP-9 pueden ser comunicados al usuario devolviendo un estado `NEEDS_INFO` con los campos requeridos en el atributo `fields`.
-
-Después de que el usuario haya enviado su información KYC, llama al método JSON-RPC `notify_customer_info_updated` nuevamente para actualizar el estado de la transacción. Además, llama a este método cada vez que el estado SEP-12 de un cliente cambie, como cuando la información del cliente está siendo validada y el estado cambia de `NEEDS_INFO` a `PROCESSING`. Esto asegura que cualquier cliente configurado con una URL de callback sea notificado del último estado del cliente, permitiendo que el cliente invite al usuario a actualizar su información.
-
-<CodeExample>
-
-```json
-// notify-customer-info-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_customer_info_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Customer info updated",
-      "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
-      "customer_type": "sep6-deposit" // or sep6-withdrawal
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh notify-customer-info-updated.json
-```
-
-</CodeExample>
-
-### Listo para Recibir Fondos
-
-Después de que el usuario haya enviado su información KYC, el anchor puede notificar a la plataforma que está listo para recibir fondos. El anchor debe usar el RPC `request_offchain_funds` para proporcionar los montos finales al usuario. Para ello, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-offchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_offchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request offchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "instructions": {
-        "organization.bank_number": {
-          "value": "123456789",
-          "description": "US Bank routing number"
-        },
-        "organization.bank_account_number": {
-          "value": "123456789",
-          "description": "US Bank account number"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es el monto que el usuario debe enviar al negocio.
-- `amount_out` es el monto que el usuario recibirá.
-- `fee_details` es el monto total de tarifas recaudadas por el negocio.
-- `asset` es parte del campo `amount_x` y está en un formato SEP-38. En este ejemplo, se establece en USD, asumiendo que el usuario hizo una transferencia bancaria al sistema usando USD.
-- `instructions` es el conjunto de campos estándar SEP-9 que el usuario debe usar para enviar fondos al negocio. En este ejemplo, el usuario debe enviar fondos a la cuenta bancaria con el número de ruta `123456789` y el número de cuenta `123456789`.
-
-La información sobre los montos (entrada/salida/tasa) es requerida si deseas mover la transacción al estado `pending_user_transfer_start`.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-offchain-funds.json
-```
-
-</CodeExample>
-
-:::caution
-
-Para depósitos de exchange con una cotización firme (la solicitud está asociada con un `quote_id`), no se deben proporcionar montos.
-
-:::
-
-### Fondos Recibidos
-
-Si se recibieron fondos offchain, querrás proporcionar información transaccional actualizada.
-
-<CodeExample>
-
-```json
-// offchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds received",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `funds_received_at` es la fecha y hora de la recepción de los fondos.
-- `external_transaction_id` es el ID de la transacción en la red externa.
-
-Los campos de monto son opcionales. Si se omiten, se usarán los valores anteriores a esta solicitud.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-received.json
-```
-
-</CodeExample>
-
-### Esperando Fondos del Usuario
-
-En el mundo real, el proceso de confirmación de transferencia puede llevar tiempo. En tales casos, las transacciones deben establecerse en un nuevo estado que indique que se ha recibido la confirmación de la transferencia, pero los fondos en sí aún no se han recibido.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Enviando Fondos Onchain
-
-A continuación, envía una transacción en la red Stellar para cumplir con el depósito del usuario. Después de que la transacción Stellar haya sido enviada, es necesario enviar la solicitud JSON-RPC `notify_onchain_funds_sent` para notificar al usuario que los fondos fueron enviados exitosamente.
-
-<CodeExample>
-
-```json
-// onchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds sent",
-      "stellar_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `stellar_transaction_id` es el id de transacción en la red Stellar de la transferencia.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-sent.json
-```
-
-</CodeExample>
-
-Después de esta solicitud JSON-RPC, la transacción se transferirá al estado `completed`.
-
-### Enviando Pago a Través del Servicio de Custodia
-
-La Anchor Platform proporciona la posibilidad de enviar un pago a través de servicios de custodia, como [Fireblocks](../custody-services/fireblocks/README.mdx). Para hacer un pago a través de un servicio de custodia, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// do-stellar-payment.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "do_stellar_payment",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Custody payment started"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh do-stellar-payment.json
-```
-
-</CodeExample>
-
-Después del procesamiento exitoso del pago en un servicio de custodia, la Anchor Platform hará automáticamente la solicitud JSON-RPC `notify_onchain_funds_sent` y el estado de la transacción cambiará a `completed`.
-
-:::caution
-
-Una cuenta de usuario puede no estar lista para recibir fondos. Puedes verificar que la cuenta ha establecido una [trustline](/docs/learn/glossary#trustline). De lo contrario, puedes establecer el estado de la transacción en `pending_trust` para indicar que el anchor está esperando que el usuario establezca la trustline.
-
-Si la integración de custodia está habilitada, la Anchor Platform realizará esta validación automáticamente por ti.
-
-:::
-
-### Confianza Pendiente
-
-Este estado debe establecerse si un pago requiere una trustline de activo que no fue configurada por el usuario. Hay dos maneras en que la transacción puede moverse al estado `pending_trust`. La primera es el procesamiento de un pago a través de un servicio de custodia en caso de que detecte que la trustline no está configurada. La segunda es cuando el negocio mismo detecta que falta la trustline y quiere notificar al usuario que debe configurarse. Para mover la transacción al estado `pending_trust`, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-trust.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_trust",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine not configured"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-trust.json
-```
-
-</CodeExample>
-
-:::info
-
-El pago a través del servicio de custodia verifica periódicamente si la trustline fue configurada. Si lo fue, enviará automáticamente un pago a un servicio de custodia y cambiará el estado de la transacción a `pending_stellar`.
-
-:::
-
-### Set de Confianza
-
-Este estado debe establecerse si el negocio ha detectado que la trustline fue o no fue configurada por el usuario.
-
-<CodeExample>
-
-```json
-// trust-set.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_trust_set",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine set",
-      "success": "true"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `success` flag que define si la trustline fue o no fue configurada por el usuario
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh trust-set.json
-```
-
-</CodeExample>
-
-:::info
-
-Dependiendo de la bandera `success`, el estado de la transacción cambiará a `pending_stellar` si se estableció la trustline, o a `pending_anchor` si no se estableció.
-
-:::
-
-### Reembolso Enviado
-
-A veces, es necesario enviar fondos de regreso al usuario (reembolso). Puedes reembolsar la suma total (reembolso completo) o hacer un conjunto de reembolsos parciales de vuelta a la `source_account` usando el `refund_memo` y el `refund_memo_type` asociados con la transacción si están presentes. Además, si el usuario envió más dinero del esperado, puedes reembolsar parte de la suma de vuelta al usuario y enviar el resto como fondos onchain.
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "fee_details": {
-          "total": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::info
-
-Si la suma de los reembolsos es menor que `amount_in`, el estado de la transacción se establecerá en `pending_anchor`. Solo si la suma de los reembolsos es igual a `amount_in`, se establecerá el estado de la transacción en `refunded`.
-
-:::
-
-### Reembolso Pendiente
-
-Esto es similar a [Reembolso Enviado](#refund-sent), pero maneja el caso cuando un reembolso ha sido enviado a la red externa pero aún no ha sido confirmado. El estado de la transacción se establece en `pending_external`. Este es el estado que se establecerá cuando se espera la confirmación de la red de Bitcoin u otra red de criptomonedas externa para completar una transacción, o cuando se espera una transferencia bancaria.
-
-### Error de Transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, es necesario establecer el estado de la transacción en `error`. Puedes usar el campo de mensaje para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario ha realizado una transferencia, debes hacer una recuperación de transacción, y luego puedes volver a intentar procesar la transacción o iniciar un reembolso.
-
-:::
-
-### Transacción Caducada
-
-Tu negocio puede querer manejar transacciones abandonadas al caducar aquellas que han permanecido inactivas por un cierto período. Para lograr esto, verifica el estado de la transacción usando el endpoint `GET /transactions` y ordena los resultados por la marca de tiempo `user_action_required_by`. Si la marca de tiempo ha pasado, ejecuta manualmente la lógica apropiada, como expirar la transacción o iniciar un reembolso automático, basado en el estado actual de la transacción.
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no puede ser utilizado después de que el usuario ha realizado una transferencia.
-
-:::
-
-### Recuperación de Transacción
-
-El estado de la transacción puede cambiar de `error/expired` a `pending_anchor`. Después de la recuperación, puedes reembolsar los activos recibidos o continuar con el procesamiento de la transacción. Para recuperar una transacción, haz la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-## Actualizar la transacción de Retirada (Exchange) mediante JSON-RPC
-
-El diagrama de flujo de retirada SEP-6 define la secuencia/reglas de la transición del estado de la transacción. No puedes definir el estado que deseas establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene los atributos requeridos, la Anchor Platform retornará un error y no cambiará el estado de la transacción.
-
-El flujo de intercambio de retiradas es el mismo que el flujo de retirada, excepto que los montos no necesitarán ser recalculados al solicitar fondos onchain, si el usuario ha proporcionado una cotización firme del anchor.
-
-[![diagrama de flujo de retirada sep6](../../assets/sep6-withdrawal-flow-diagram.png)](../../assets/sep6-withdrawal-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen la manera más corta.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden ser omitidos.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en estado de error o ha caducado.
-
-:::
-
-Una vez que se complete el flujo de retirada, implementar la retirada es sencillo. Algunas partes del flujo son similares y pueden ser reutilizadas.
-
-El punto de partida tanto para la retirada como para el depósito es el mismo.
-
-### Listo para recibir fondos
-
-De manera similar al depósito, el paso después de que se recopiló el KYC es notificar al usuario que el anchor está listo para recibir fondos. Sin embargo, como tu servicio estará recibiendo transacciones a través de la red Stellar, la solicitud RPC será diferente. El anchor debe usar el RPC `request_onchain_funds` para proporcionar los montos finales al usuario. Para hacerlo, haz la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "iso4217:USD"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es el monto que el usuario debe enviar al negocio.
-- `amount_out` es el monto que el usuario recibirá.
-- `fee_details` es el monto total de las tarifas cobradas por el negocio.
-- `asset` es parte del campo `amount_x` y está en un formato SEP-38. En este ejemplo, está configurado en USD, asumiendo que el usuario hizo una transferencia bancaria al sistema usando USD.
-- `memo` es el memo que el usuario debe usar al enviar sus fondos onchain al anchor.
-- `memo_type` es el tipo de memo que el usuario debe usar al enviar sus fondos onchain al anchor.
-- `destination_account` es la cuenta a la que el usuario debe enviar los fondos.
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-:::caution
-
-Para retiradas de intercambio con una cotización firme (la solicitud está asociada con un `quote_id`), no se deben proporcionar montos.
-
-:::
-
-:::tip
-
-Configurar `memo`, `memo_type` y `destination_account` es opcional.
-
-Si la integración con un custodio de terceros está habilitada, la Anchor Platform puede generar `memo`, `memo_type` y `destination_address` si se elige un tipo correspondiente `deposit_info_generator_type`. Además, puedes proporcionar `memo` y `memo_type` a la solicitud como se mostró anteriormente. Ten en cuenta que el memo debe ser único, esto es lo que ayuda a asociar las transacciones Stellar con las transacciones SEP.
-
-Si tu negocio gestiona los activos, la Anchor Platform puede generar memos para ti. Cuando el estado cambie a `pending_user_transfer_start`, la Anchor Platform establece automáticamente el `memo` y el `memo_type` (solo si no están incluidos en la solicitud).
-
-:::
-
-:::note
-
-La cuenta de Stellar que se usará para recibir fondos debe estar configurada.
-
-:::
-
-### Fondos recibidos
-
-Si se recibieron fondos onchain, necesitas proporcionar montos y cambiar el estado de la transacción a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método será llamado automáticamente por el servidor de custodia si la integración de custodia está habilitada.
-
-:::
-
-### Monto actualizado
-
-Si se recibieron fondos onchain, pero por alguna razón el `amount_in` difiere del especificado en el flujo interactivo (`amount_expected`), puedes actualizar `amount_out` y `fee_details` para que correspondan al `amount_in` real. El estado de la transacción en este caso no cambiará y será igual a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// amounts-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_amounts_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Amounts updated",
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh amounts-updated.json
-```
-
-</CodeExample>
-
-:::note
-
-Solo `amount_out` y `fee_details` pueden ser actualizados usando esta solicitud JSON-RPC, y no necesitas especificar los activos de los montos.
-
-:::
-
-### Fondos offchain disponibles
-
-Puedes mover el estado de la transacción a `pending_user_transfer_complete` si los fondos offchain fueron enviados, y si está listo para que el usuario / receptor lo recoja.
-
-<CodeExample>
-
-```json
-// offchain-funds-available.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_available",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds available",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-available.json
-```
-
-</CodeExample>
-
-### Fondos offchain pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago ha sido enviado a una red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Fondos offchain enviados
-
-Para completar la transacción y cambiar su estado a `completed`, necesitas hacer la solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Reembolso enviado
-
-La lógica de reembolso funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Reembolso Enviado](#refund-sent) del flujo de depósito.
-
-### Enviar reembolso mediante el servicio de custodia
-
-La integración con un servicio de custodia te permite hacer un reembolso a través de un servicio de custodia, como Fireblocks.
-
-<CodeExample>
-
-```json
-// do-stellar-refund.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "do_stellar_refund",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Do stellar refund",
-      "refund": {
-        "amount": {
-          "amount": 9,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh do-stellar-refund.json
-```
-
-</CodeExample>
-
-:::note
-
-De manera similar al flujo de depósito, puedes hacer un reembolso completo o un conjunto de reembolsos parciales. La transacción permanecerá en estado `pending_anchor` hasta que la suma de reembolsos sea menor que `amount_in`. Si la suma de reembolsos es igual a `amount_in`, la Anchor Platform cambiará automáticamente el estado de la transacción a `refunded`.
-
-:::
-
-### Error de transacción
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Error de Transacción](#transaction-error) del flujo de depósito.
-
-### Transacción caducada
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Transacción Caducada](#expired-transaction) del flujo de depósito.
-
-### Recuperación de transacción
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Recuperación de Transacción](#transaction-recovery) del flujo de depósito.
-
-## Seguimiento de transacciones Stellar
-
-<Observer />
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[event-handling]: ../events/README.mdx
-[customer-callback]: ../../api-reference/callbacks/README.mdx
-[rate-callback]: ../../api-reference/callbacks/README.mdx
-[get-transactions]: ../../api-reference/platform/transactions/get-transactions.api.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/README.mdx
deleted file mode 100644
index b8868bcf2a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Referencia de API
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Ver toda la información de la API de Anchor Platform.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/_category_.json b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/README.mdx
deleted file mode 100644
index 4f4c697ed3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/README.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Servidor de callbacks
-sidebar_position: 20
----
-
-import { EndpointsTable } from "@site/src/components/EndpointsTable";
-
-La Anchor Platform proporciona varias funcionalidades de callback para tu servidor de negocios.
-
-<EndpointsTable title="Callbacks">
-
-|            |                                         |
-| ---------- | --------------------------------------- |
-| OBTENER    | [/customer](./get-customer.api.mdx)     |
-| PONER      | [/customer](./put-customer.api.mdx)     |
-| ELIMINAR   | [/customer/:id](./del-customer.api.mdx) |
-| PUBLICAR   | [/event](./post-event.api.mdx)          |
-| OBTENER    | [/rate](./get-rates.api.mdx)            |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/del-customer.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/del-customer.api.mdx
deleted file mode 100644
index 3b0cbc87dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/del-customer.api.mdx
+++ /dev/null
@@ -1,80 +0,0 @@
----
-id: del-customer
-title: "Delete Customer Data"
-description: "The request for this endpoint is identical to the"
-sidebar_label: "Delete Customer Data"
-hide_title: true
-hide_table_of_contents: true
-api: eJztVE1v2zAM/SsCd9gGOHaa7eRb0eZQYBiKpTslASZLTKxNllSRXhsY/u+DHLtptmy/YL7Ypvgh8j2+DljuCco13LTEvsFIsM3geUYYBvNqeT+7WkA2fHy4SocaSUUT2HgHJTzUKCI+tkgsdj4Krg0JdDp441gYEkajY6OkFewF17hx62+3y0/Lh6Uo1Fj02/ZdzRyoLIq94bqtcuWbghitlXF6z0L07JW3RWV9VTSSGGOBytOBGJuCMMzm86tF3ug3U+KZRouM7zduuqPGnXGohXHi2Fu+cRt3O7il64kp9C0JLVkKH8Vji+354XiWGh4qGO/yjYMMfMAo0++dhhI02mmukEGQUTbIacblugOTxhck15CBkw1CCUZDBqRqbCSUHfAhJCtxNG4PfQapCRNRQ8mxxX6bLBS8I6Tkv5h/TK9zgFatUkiUp/iPlxymGwrnE4St0zlkoLxjdJzcZQjWqKGr4julmO7PS/rqOypOXcY0AzbHK2GMPl7sxegL5rMe12P0NgM2bJPfcjD06ckAnxkdGe+O8/yBBygn6mbwU9oWL1I4za1Brv0IETIO6HANJbxwsuiM7hMcGH9OkLXRQgkTVZW0tpLqR161ZBwSzY6+OT7LJliUTtU+JipDKmnczqeWU7bj5D/k83wOlzZqdXCqjt75lsTNWIbE9f2doIDK7EY4xo1DsTquiLgeSop7K3nnYyNC9AmWgeP/znvcC5p2mUQjNYrqMKR/yfdUG4vCDIsdok/EMm4v5EkCom+EFMoadCxeMScXD2n3jzN5m+qMxB1lgfBUWu52qPi88u/+l0oMGzhR5dTeakAFMrBGoSNMIIwLdx2kqlEsBhhO6JZF8fT0lMvhNPdxX4yhVHy6u1l+Xi1ni3ye19zYgbPBEzfSvUo8CsrLbt1Klr8j3Z2W7L+MnsvoKAuMz1wEK41LijHg042LugZ1UtbS6KQStSdOJ11XScKv0fZ9Mj+2GA9QrrdJFKKRVeLHugNtKH1rKHfSEv4DnXdfRlF6L/52udEo3eGkPQDZqEpGQ7/tM6hRaoyv5OpaKQz8KuQPsT1TqyPi0Pe/AB/asHM=
-sidebar_class_name: "delete api-method"
-info_path: platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-12,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete Customer Data"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/customer/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The request for this endpoint is identical to the
-[`DELETE /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-delete)
-request defined in SEP-12.
-
-Delete the customer's data or queue the customers data for deletion.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"path","name":"id","schema":{"type":"string"},"required":true}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"204":{"description":"Success."},"404":{"description":"Customer not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/get-customer.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/get-customer.api.mdx
deleted file mode 100644
index 8b11caa759..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/get-customer.api.mdx
+++ /dev/null
@@ -1,91 +0,0 @@
----
-id: get-customer
-title: "Retrieve Customer's Info"
-description: "The request and response for this endpoint is identical to the"
-sidebar_label: "Retrieve Customer's Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWG1z2zYS/is7uA9pZihKdtJco28eRcnp2jo+y+lNx/bYELES0YAAC4CWNR7995sFSImyGbu13ZvLTfzFFAksnt199gV7wwS6zMrSS6PZkJ3kCBZ/r9B54FqARVca7RDmxoLPpQPUojRSe5AOpEDtZcYVeAM+xzN9evlhfAL9rHLeFGgvz7/LvS/dsN9fSJ9XszQzRd95VIrb5n+vtMabzKj+TJlZv+DOo+1jZtzKeSz6DsveYLC3nxbib43g3gL9yzPdCVXgXGoUIDVMx0e9vf30TJ/pkx3wXCmzdJApido78GZIawD2UniPPstJG5hLVMKFR4f2Cm0wjbToSLaxAi0pbnEhCTJw0LiEBiJcSQ68hkCWOfr0X7FMWfmXjQ9Jqcm8rYEw6EAbDzm/QuBbtI0WKGpfI5Tc8gI9WgcOyeM6vK5lJyA9uNxUimzvK6sjBWqr1aYS213RPSkQxxwvtq8aKTOsBaGAZY4atGlj4BYDjjS6aj+FUY7Z56id575yYOZtlXzOPRR8BVxZ5GIVD2jU3JDiDhcgC3KXOfocoykameT5ubEFp3iBJXfAswxLjyIBi79hFp6MBeelUqARhYPCWAz70tve6FwV9rcWxc9VKbgP5tyc3+0BuOWA9EyzhHm+cGx4ykaNIuw8Ydc9h2V4TSx9wxIW2Vo/vNqjRaZEG46bCDZkC/SNCJawrXfY8PSGSUohv1doVyxhmhfIhkwKlnQkmck7clbbtMDd1v23SBMdW1q8kqZyQJFUszBlCXNZjgVnwxvmVyWd6byVesHW66QbE88yU2nfCWwaQ4988HN1jQIO4mLglc9juiM3LKWPSeJIcU8eCeEezDd4FKYCC9MJiD7AFVcV1vl2vpJ60eZ5wMLB5ZzirVYuIf5ajETa+UKZ+7J+vnw01ouwtgswfSCHBeCVQ0Eh1UB/EPd9gBKGuiqIr4FVOXc5URuvPTv/ItgHcfIsBPMOF6WDGZKZf/x1FBJiClPEusad0MZpiZmcExuk0c+dzAlaz7VPeHmmhcmqArW/Vdoe40BvuXZR74svBGhrCcia78tc1qWxMdSLmBDJXtw5k0kKjhT+Tdm7nSnn1hS7FhZYohYOTF022ud9h+kiTbYZsZEiW2WFipTidkGJoyDiuJePs4XigVm7FniHc16pWA0uUV+m8BPXi4ovEDIjEGrfoIDKEU0m04/w5tXb3l4K/6gKroEKDp8p6kY2cl0CWW5khi6hjuVMF+gcX6BrFcCQ+KQDVR/3kIPPE9YkSUff9wcD+rerzS9cSbHJmNAkcEAZClxTHvFaOu+a6rONhRi6pOxsdbsxkC40PdSAFRU1HKU1V1LgthLF3OVqQ8w6kvvMiFUKx62fEmO5v91gQjRE0+KdaanhNEbCX9ppRi9kRnvUnuzLy1LVkdn/zZGRb+46ycyoIWDkoUhaylyxU6HCWloqrV5Gx0nR4d6kWX5PKjwYjcZHJ+N3LGFHxx9H4+l0cviBJexwPH43vZgcvv/IEnY8/ud4RIvO1wmLDUIXUC6EJJ24OtoB11agI5/eUSbK/TLmzYuZ1DwGY1XMQktBXU5AuUPhDsvUodT6xq3lJEt6LDpMtl5TMxPVa32dGaOQa7Ze04KavuLim5E6jfQURm5ImLBfxseT95PRwcnk4+HF8fhfnybHNTnRWmO7cBGyOmF2w/bSK3r1YduiNjmFcOM1L0oVbTGtsgyd+/HXUQjcqijIwLHwZdxhvH60WpWcU0OAGlzcOa+UWlFz8EKE3MdLIg5SKQ3proloJvYy3J+//qH3aj7f671++73ovd1/Pej9nX8/ED8M3mTzsKkxatt2HVScS+v8RSxct5P8yW5ZDkshLE3ueOruceuEKf5HZdPKPyUaCy7VBRfConMPig+roVn9h46o/xL2uqv+jYlT6VMy+G7kfomjSXcWX+9WgLj7fEvYAI81+F/fxX9oPLw3lRZfgw4h1DxqRx1PuBZ+Roqt+rK5CZB7Lp3U1RToc1PfOMNN0+dsyDbzE6JBuB7HIyqr2JA1HUDGlZrx7HM6o+4MnevFtWmdA7jOcmOpQ2B0FLWYpDJJiwZ/lQ7SQff1cKWz3BpN19BRfYyDg6MJ7LTrmxlKc508CEdub4ulNeSWejR1n9zY67imfXNQcIFNJ7aRt8ylQpoHSEeyKUfFW2IzIgsdOK+nHNBiThjInOlokxdu05a5uudyuD2az+eY+d2Tb6/vOiKOIGqqbNWbBq+whCmZIaXp4U3TlR+UPMsR9oMbtt4d9vvL5TLl4Wtq7KJfb3X9nyaj8eF03NtPB2nuCxU4WxrnC65bgo/RW4lXuOmCXziYEAHuFNNNoH2bin6bin6biv5fTkVjkaMJUr9UXIYGN2Sbm7rinLJNxTlPWG6cp3c3NzPu8JNV6zW9jhMFqkNCOrr1Czacc+XwgZzynEPQTlVi5ZWttpQxmoP8OZjPNBK9B+F2IPsEmH/9oPQeDerx7RPgP31s+gC8ZmL7DBi//pHpPbZ6BjN9pbPT+4xye2L8SPP8jw1W79G4ngtv9TynH1bS4Wx4SrOKHLlA27rjHISy19p154a2c7X5MD5h6/V/AIMyEEU=
-sidebar_class_name: "get api-method"
-info_path: platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-12,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Customer's Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/customer"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The request and response for this endpoint is identical to the
-[`GET /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-get)
-request and response defined in SEP-12.
-
-This endpoint allows clients to:
-
-  1. Fetch the fields the server requires in order to register a new customer via a SEP-12
-[`PUT /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-put) request
-
-If the server does not have a customer registered for the parameters sent in the request, it should return the
-fields required in the response. The same response should be returned when no parameters are sent.
-
-  2. Check the status of a customer that may already be registered
-
-This allows clients to check whether the customers information was accepted, rejected, or still needs more info.
-If the server still needs more info, or the server needs updated information, it should return the fields required.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"query","name":"id","description":"The ID of the customer as returned in the response of a previous PUT request.","schema":{"type":"string"}},{"in":"query","name":"account","description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","schema":{"type":"string"}},{"in":"query","name":"memo","description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","schema":{"type":"string"}},{"in":"query","name":"memo_type","description":"The type of memo used to identify a customer with a shared account.","schema":{"type":"string","enum":["id","hash","text"]}},{"in":"query","name":"type","description":"The type of action the customer is being KYCd for. See the\n[Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification)\ndocumented in SEP-12.\n","schema":{"type":"string"}},{"in":"query","name":"transaction_id","description":"The transaction id with which the customer's info is associated. When information from the customer depends on the\ntransaction (e.g., more information is required for larger amounts)\n","schema":{"type":"string"}},{"in":"query","name":"lang","description":"Defaults to `en`. Language code specified using ISO 639-1. Human readable descriptions, choices, and\nmessages should be in this language.\n","schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Valid request. Customer either already exists or the customer identified by the parameters is new and must\nprovide the field values described in the response body. Response bodies are identical to the schema defined\nin [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-get).\n","content":{"application/json":{"schema":{"type":"object","required":["status"],"properties":{"id":{"type":"string"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","NEEDS_INFO","REJECTED"]},"fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"}}}},"provided_fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","REJECTED","VERIFICATION_REQUIRED"]},"error":{"type":"string"}}}},"message":{"type":"string"}},"title":"GetCustomerResponse"},"examples":{"SuccessKYC":{"summary":"The case when a customer has been successfully KYC'd and approved","value":{"id":"d1ce2f48-3ff1-495d-9240-7a50d806cfed","status":"ACCEPTED","provided_fields":{"first_name":{"description":"The customer's first name","type":"string","status":"ACCEPTED"},"last_name":{"description":"The customer's last name","type":"string","status":"ACCEPTED"},"email_address":{"description":"The customer's email address","type":"string","status":"ACCEPTED"}}}}}}}},"400":{"description":"Error.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Not Found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/get-rates.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/get-rates.api.mdx
deleted file mode 100644
index 64639632c5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/get-rates.api.mdx
+++ /dev/null
@@ -1,107 +0,0 @@
----
-id: get-rates
-title: "Retrieve Rates"
-description: "Transactions that involve two non-equivalent on & off-chain assets (such as USDC on Stellar and fiat EUR) must"
-sidebar_label: "Retrieve Rates"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+tv4zYS/1cGOuA2uZPtbLYtCgP7Id1N2wB37WKToB/iXExLo4iNRGpJyl5fkP7thxlSDz8Sp9m9uz7yyZFEcjjv3wyZ2yhFmxhZOalVNI7OjFBWJPRkweXCgVRzXcwR3EKD0mqAH2o5FwUqB1rBX0Fn2SDJhVQgrEVnYc/WSQ7Cwvnp2zc05tRhUQgDQqWQSeHg+Pz9PpS1dRNVWwT8mORCXSMY4TBQFQYh0WVZK5kIhyk4DS5HSApJlEVVFfRBagUGP9RonVTXPMJ1HAzhpxxVmGOhFDc4UWG4bVZ8VwiXaVNCpg292NhQvDrMokppk9I2lJuVhEpyWkNDhi7JQbrhRE3Ue+YqEQpmCBdSpbzxOV7u5c5VdjwaLRaLoVRztE5XmEoxTHQ5cmhKO5KjbsKHWjscClvtgzYTdZFJUz5qkWxEQ7vpQzjrtkt6gMrouUzpHZy8ZUXhx0oaL2CZEXsTFWTfClAALctCYkaPeEHParNgKm2ia0Ua9Nq1FSYyk8kWTVq/r1bSUiVFnbJFIEz9+CuZTqESRpTo0EyUVxrrQliteB/H0uVoYGqxKK5ESeSnoA1MZ/WyfV7IoiCFBCIpSNXjzHY0bAyz2oHCORqYaZcP4UTxlqwoERZiGU8U9kmmWMg5muVViS7X6ZTlycQ3vpRied8m1snGYKVKEDypiQrskc/1uPOPkpTTuh29Y8FM1HnFDpOgnDf+YtBWWln0Zu512OmAxTQXhUyFQ2/lLEDmqTIyQdDZyjpM6cS/CxPJiDIhi3VX4sX9vAcc/EXnaAvpchDw/dnZO7BOuNpOVKJT3sP0y4ND+Eak8J1wuBDLKW+EDGrFEOIVM4hhykxMY6+kDHHKsadhOSVbyHRR6IUd04IDcocp2zwPxo+SlDVRAIPu/TAogp0rF3MEAZW2ktyY1q79lq28VuQMQrmrFBNZisJOIcVMKm8MLHBaChKtMnlde5ccrpNz2okikMMPtSgacdq6ZErtyBQdaWIYBBBW8i6+vn94/dp7d8/U4hVxwi+vgxX8DTqxwt+BZeO510UKztT4OFKdFcdwL6m9dVr7W4itayrVaEFp51X2GD62LBos6pfX7GSNpoT1UpduyTZKbqxrlZKPoTHaMO/A4W31w9oq05cH/9obbDOL/elERXHkxLWNxhcRJ5XoMo4+DixW/Or0+N3g1cso9n98TR91hd5gTtJoHF2j89PiqItu0fjiNpKU+j/UaJZRHClRYjSO3LLCKF6HB5RglxVbL0m28UxMh3CSwZQSwjReiQdehiHCBX3IJijyE6catFfCTYdRHNkkx1JE41u/hXFknZHqOoojVHVJnHYpMYojIhld3sURbUUaTKMx6eou3s5Wm0Y2eDtSIFNUTmYSTYMGtgGOUtx0wZPZp8QlLaXOkOZr6yGLzjI0kEr6oWUyRAYe3ZsATti03nhaJ29tm56ISBPIq3pWyARucMmve48NOVG7nDggyARzKYBM4eXBEJrU7AOEsrXBiWKgtbZSSM9d9GlCbylckiPlld7oG6UXigjPsNAkkhB00Fu4RxjBa2Qvp3r2tCo4+/VoZn2ZUxbrMZRu5YgE7h0IFjlyFtaG3HyiepMZxvg8QibC2mWQRtvszMljlCF82+AaC6JYiGU7E1bXHLJP3mewd/fZYBdOtzqYD4j3GB9LjgS8hjql6mBrtg4H1ERdHPGqJ8HCw2rfalMK14HIa+nyesbQ0Xqra34HldFOJ7oYzQo9G5XCOjQjTLRdWoflyGI1ODh49fWwTP/CZAdyhdQgY1L7O0T2WDduudshwdbGg5g68W0IrI+n/oAS62W77TLziZBhSU8SO83wAcMbwk80jHJuExNJsIlWP9cqCeu4fAWRPdGluhV2Mdfzi19tF1sZgh4/E+UZ6iPOJ3LEZZNZXhG+3crTxcnpj/Dq5VdfDV6CKKpcDA47s0Q1XMgb6StBba5H9DQ6Of3xys+4CjP2ocHPJIzaonlhIakN5yaRpgYt5aYm2tpc1wUXh5g4X3h1QZ3zQFP5cTDXql06NAfC06xejkhGUAnJGIj7AgQJpJsoCvxzIQsxK5Dz0EJTUC81NwVILBLtE8XqwcaVyByarWL1xv6CYJnlXDHt4RPgMoj26WSJLUjg0trHmj4A4HQmrS/HuFb2NbhHC16WEzWj4uDi/OwNkEK//urg5VpRbzVrUFo9oK8D2sNAqHRAewhRYpi7stgHz32XHYO+DLraKJh+cXBAJdJEvfdZfUpbFKpf7DODWpG8WUZ9EEApmGuXRKjgA422PyUTrlXFW7XiP/WjkTZsrt5zqY1EsMqvtBbBdK+yDbL3bFD1LbLMmzJOVE8MXXnbcsjonSdar96299C5QA/NN9XbSiG7XsXtCCe98LjeOviEOPmJ8hbUS2sQp+8l4EpYzYwuf+8i39rI2SXzS8rFvuqx9P3w4IB+VqV7WicJBdUojhKtHCpHY3p7Hv1saeDtJiE9+xkTSnCVocrOSU+GgOruUTLdVlKt7u3kbROg+9Hqhx/P4Pz0+C0BbAVTWuJ1h5mnQ8IgXYzcRsXHqGgcceiisLVB+rgzhJWo+jjybDe7+eP4rtUcjSVCTf+KSrEUZss+IKBNUPqqldzADWRn1FhdB0sxG4+um3KXiguq+HzH0IhU0j5EAZlUQiUYr6y64FA9o2iboTGhovPdz5mwDarlurkf38IQ32Zt2n3sOST2uhCrnY4BbQke0+6AvQuD2eeGukx3ELZm9/dZf31w+igtPoBW+4jufmR6Qi21IPBefd6ErtXmcYdpVoriGFKsQq2rFeR64Qt8aiCyQ3dWFUIh8dqDqr+W1Qewa9Nw7+PPR7Lat4DPymmGW+PSRtvFfwH/ftb0VjyBlDajqclQtZ1mgijtRqkpwGz4Ri4I54yc1Q6HGyGQu6SPEzoPZU/xqDYwyWz5uvNxumsLUVqqaeokuTDXLOMh/JNcjp2+MmiRT0qkgt9M8UkMh55xj2VhjCBUIR2Wdnfu8eDjMQKjkW0OQozZcfGjKKsCYXr05nvuLMcw/caIf8tCCk7eCf3lc4f/eopmTuHNP6JLAh89crt2cwQOP24zSm8DT3LgEMGDLfmOadeT55ZyY9fUn67Lvc2W/f60QfUz9F1n61fxZwBDwn69lsCFF36748s4ctIVtGVqBn+L+JaXfx+AS3S3Pt97TWP2m/N7M1cn+qQcr3UeeuHvkmb0V+tv4i6Ovjg83MRP56oymhAUV4fHykm3bCoqPhLqicfXPZh66NALmbVK0VinA8Rtmpx04uZrGzon5ppJgPWArX/A5Q8ALRVCduOA+KmnWk11Bk1xNlFcEIfOOS3jjwxKYv66FwJXkUsbuUP/fabTpUeunwlv8i62dqK2Ycx1q/Cze2Z0zC+8xr/chph5wNrZ8OOE7EXbntW2IuGeBwmXZfM7kAwjbIeKYKs/srnBZTRuTn/iiIukradAVJWEQo+PgPj0x+XROBpx4UD+aebNSVBtimgcNfklEUUxE8nNcFZbqdDagR87DBE5NPgTXUZERqpME5sBX0fj6NXwYHiwNSieLlWSG610beFNIGPh6N1Je0NgtRhoDkHWD6gro0kV7dHc/ev6KtF2p/ylSLHxnc6wcklNJxdiMXk+H2W03sq4SWwxNrZQ8lna4IsuXjQ3TSz2Lhi0JXBHeX38NhL+DDCYR8feKWsliqNCJkjxs8250VElkhzhkNXQaTf0lgR/5fZSmGpH/zh5c/zD6fHgcHjAXSW200pbVwrVW/g9UhtujtCcKa5l19alnu8UPd8per5T9Hyn6PlO0fOdouc7Rb/FO0UelVK5O6oKIRUBVoYKtwEqXvge82Uc5do6er69pZbkuSnu7ui1P2UgAJlKLszSaJyJwuIDsGDvfcC++/C/uFa0lUuPosNVp4Cho4gOTx7Px/O9oed7Q0+6N/SARfZvqT3RLNfc609wqegBea7cuPrcAv3D3DF6QID9+1ZPlN9v7pLRTntpWpafh+H/08WjXUr9DEw+30TaEc1Xr3J9gqSfLyc9/XLSAwpauxT2CQp6vqe09c7MrlC7eSXpv6ODP/vdpR3J4CE1XNKDkaSHaHxB/3CRo0jR9E4jjpIEq34u2ThLWTmM+O74LLq7+w+n2PMK
-sidebar_class_name: "get api-method"
-info_path: platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-31,SEP-38'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Rates"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/rate"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Transactions that involve two non-equivalent on & off-chain assets (such as USDC on Stellar and fiat EUR) must
-use exchange rates that are communicated to the client application requesting the transaction. When clients make
-requests to the Platform for these exchange rates, the Platform sends this request to the anchor to fetch it.
-
-Rates can be [indicative](https://www.investopedia.com/terms/i/indicativequote.asp) or
-[firm](https://www.investopedia.com/terms/f/firmquote.asp). The anchor must provide an ID and expiration if the
-client requests a firm rate.
-
-Anchors can provide discounted rates specific client applications. The Platform includes the `client_id` parameter
-for this reason.
-
-Either `sell_amount` or `buy_amount` will be included in requests as parameters, but never both. In the same way,
-either `sell_delivery_method` and `buy_delivery_method` may be included in requests, but never both, since either
-`sell_asset` or `buy_asset` is a Stellar asset.
-
-
-Upon receiving the response, the Anchor Platform will validate the amount and price of the response.
-
-If the validation fails, the Platform will respond to the client application's request with a HTTP status
-code of `502 Bad Gateway`.
-
-The `sell_amount`, `buy_amount`, `price`, and `fee` are validated as follows:
-
-- if `rate.fee` exists,
-  - `rate.fee.asset` must have a positive value of `significant_decimals` defined in the asset configuration.
-  - `rate.fee.total` must equal to the sum of `rate.fee.details.amount`.
-  - if the `rate.fee.asset == rate.sell_asset`, `sell_amount ~= price * buy_amount + fee` must hold true.
-  - if the `rate.fee.asset == rate.buy_asset`,  `sell_amount ~= price * (buy_amount + fee)` must hold true.
-- if `rate.fee` does not exist, `sell_amount ~= price * buy_amount` must hold true.
-
-The `~=` is defined as equality within rounding error.
-    The rounding error is defined as `10^(-significant_decimals)`
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"query","name":"type","description":"The type of rate requested. If `firm`, the response must include `rate.id` and `rate.expires_at`.","schema":{"type":"string","enum":["indicative","firm"]},"required":true},{"in":"query","name":"client_id","description":"An identifier for the client application making the request. This ID can be used to offer different fees to different clients.\n\nClient IDs will be the Stellar public key the public key used to authenticate via SEP-10. Anchors must ensure\nthat the public key specified in the request matches a public key known to belong to the sending anchor.\n\nThis parameter will only be specified if the client is authenticated via SEP-10. Anchors can define whether or not\nauthentication is required for fetching indicative rates. Firm rates always require authentication.\n","schema":{"type":"string"}},{"in":"query","name":"sell_asset","description":"The asset the client application will send to the anchor in exchange for `buy_asset` in\n[Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format).\n","schema":{"type":"string"},"required":true},{"in":"query","name":"buy_asset","description":"The asset the that the anchor will send in exchange for `sell_asset` in\n[Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format).\n","schema":{"type":"string"},"required":true},{"in":"query","name":"sell_amount","description":"The amount of `sell_asset` the client application will send in exchange for `buy_asset`. Will not be used in\nconjunction with `buy_amount`.\n","schema":{"type":"string"}},{"in":"query","name":"buy_amount","description":"The amount of `buy_asset` the anchor will send in exchange for `sell_asset`. Will not be used in conjunction\nwith `sell_amount`.\n","schema":{"type":"string"}},{"in":"query","name":"country_code","description":"The [ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) code of the user's current address.\nAnchors should expect this parameter to be provided if one of the assets of the buy/sell pair is fiat and it\nis available in two or more countries.\n","schema":{"type":"string"}},{"in":"query","name":"expire_after","description":"The client's desired `expires_at` date and time for the quote that can be used if this is a firm quote. This should\nbe a [UTC ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) string. Anchors should return `400 Bad\nRequest` if an expiration date on or after the requested value cannot be provided.\n","schema":{"type":"string"}},{"in":"query","name":"sell_delivery_method","description":"The method the client or user will use to deliver `sell_asset` to the Anchor. This value may affect the\nexpiration and price provided. The values used for this parameter is defined in the application's configuration.\nWill not be used in conjunction with `buy_delivery_method`.\n","schema":{"type":"string"}},{"in":"query","name":"buy_delivery_method","description":"The method the client or user wants used to receive `buy_asset` from the Anchor. This value may affect the\nexpiration and price provided. The values used for this parameter is defined in the application's configuration.\nWill not be used in conjunction with `sell_delivery_method`.\n","schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","properties":{"rate":{"type":"object","properties":{"id":{"type":"string","description":"ID of the firm quote. NOT USED when `type=indicative`."},"expires_at":{"type":"string","format":"date-time","description":"Expiration for the quote. NOT USED when `type=indicative`."},"price":{"type":"string","description":"The conversion price offered by the anchor for one unit of `buy_asset` in terms of `sell_asset`, without including fees. In traditional finance, `buy_asset` would be referred to as the base asset and `sell_asset` as the counter asset. The formula `sell_amount - fee = price * buy_amount` must hold true ([ref](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#price-formulas))."},"sell_amount":{"type":"string","description":"The amount of `sell_asset` the anchor will exchange for `buy_asset`. It could be different from the `sell_amount` provided in the request, depending on how fees are applied by the Anchor."},"buy_amount":{"type":"string","description":"The amount of `buy_asset` the anchor will provide with `sell_asset`. It could be different from the `buy_amount` provided in the request, depending on how fees are applied by the Anchor."},"fee":{"type":"object","description":"An object describing the fees added on top of the rate provided via the `price` attribute.","properties":{"total":{"type":"string","description":"The total fee to be applied."},"asset":{"type":"string","description":"The asset the fee will be charged in. Must be represented in [Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format)."},"details":{"type":"array","items":{"type":"object","properties":{"name":{"type":"string","description":"The name of the fee, for example `ACH fee`, `Brazilian conciliation fee`, `Service fee`, etc."},"description":{"type":"string","description":"A text describing the fee."},"amount":{"type":"string","description":"The amount of asset applied. If `fee.details` is provided, `sum(fee.details.amount)` should be equals `fee.total`."}},"required":["name","amount"],"title":"RateFeeDetailResponse"}}},"required":["total","asset"],"title":"RateFeeResponse"}},"required":["price","sell_amount","buy_amount"]}},"title":"RateResponse"}}}},"422":{"description":"Unprocessable Entity. This status should be returned when the anchor understood the request but cannot\nreturn a success response.\nIn these cases, the Platform will respond to the client application's request with a `400 Bad Request`\nand include the error message provided by the anchor in the response body.\n","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"500":{"description":"Error. The Platform will respond to the client application with the same response code and body.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/post-event.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/post-event.api.mdx
deleted file mode 100644
index 0aeff4fccd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/post-event.api.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-id: post-event
-title: "Receive an Event"
-description: "Receive a JSON object representing an event."
-sidebar_label: "Receive an Event"
-hide_title: true
-hide_table_of_contents: true
-api: eJztHF1v2zjyrxB86R1gO4nb/Ti/dbtZIIfbNlvnXi4JXFoaW2wkUiWpOEbg/34YkpIoWXZso0CzgPISmx8zw+HMcD5oPlPDlppObunlIwij6f2APg015LZtenk9/JkO7P/xO//h7QUOkjkoZrgUVzGd0FxqYwHQAY1BR4rn2Ecn9DNEwB+BMPLv6aePRM6/QmSIglyBBmG4WBImCODc0Z2gA6rgWwHa/CbjNZ0800gKg3Anz5Tlecoji/Tsq0boz1RHCWQMP5l1DnRCHQI6oLlCEg0Hjb08DsZoo7hY0s3AN7Q7BhREkSEDjGJCswhRziIFzEBMB41WbZgp9CxKmFjazm+FNBAMjgptZAZqVuSxbbpvs+gmARKAdMwgSNKIfGCCzIFIAUQuiEmALGSayhUXy8mdGJIvHRR+IUPCGhBXTBPfSUyiZLFMLKzp5TUBEeeSC6NHBAnJ2TqVLCZcEy7soBDFF7LgkMajLdRNNiAFONW1IuVNehKkxw09GmuDv26ptqmxyEfOygW+/ZW8v77aicbOrRFYoeAZaMOyvEsyFlJlzNAJxc0c4lCc4gG/LIfBqvCrFPBpQSe329NQDbiCGKWQoxxpyOmAPnBhv1jG0gFlmSyEmcFTDpGTtxi04cJqyYxFEXa7CcpAPGMG5e8g3UCEe1Rj/I7ebzxBe4bFkEvNkYQVN0ms2IqldqJfQsfUpnZcS635PK2E6ZGlBWqBIs4qhYKlA8RcRDLLUzCASug/xpazi0LE9iM85ZbHAwpKSYW7BSLmYjnTBtKUhS3wZEAJlgZNhQY1s+gXoGaWxTt7A2LKAUxESQOpUYVuQ6ADKuQsY+oBsMtIOdMZS1P/OWVqCbilhpsUuTi1XJpeXo/f7TNwbQvEtVMBVA2WrthaE8hys97F6BECbwtfh/SHYuyGo9BqDR1y6Pu7ZNHN2O7Z1At/72bXZHHxygiShXktFC0AZjEYxlP9EklGGiv0Oyhy3ccQhMLXxsyUYms6oNxA9iJFgmVQmb5timx3J0G7mddQh30s/APg92DsZqvPrWxT+gG7bGttjg8+Y7z/cNScyu4dNasyWso5b0fSiXbPuwXlts3m68MBZKA1W3bvoTPenSLSpSmzyti/EsXzZC0AXgtFOVtn1vM/QhsP8h94PHvJva5P2ep0ve9S1B9tK18LKT42OlIhSx04YtKmYdg+e6Wzhsvu2KzhdJ1ox61b6z12pA3l4hFSmVsnqRTLg9zVrpDq6vcyZApDD+/3T906iACzkuph5OxOJg8DjSNPAL5TH3ZgwGFHoCHTRBZpjPGij64JXzhIXBMhDRFFmo7C8BaekO0J0wluWmy1L9iRw6SlM57lGWzRjRGagiXXBhTE+7hVCcJBzGoEz37mgGDmgHFhMwxp2sFEtxQuxehUO7glzR6I2+gB1bJQEQRhWHdwtsuTOV7SPf42az8GrG2QeBh7vRi+BLyWKz/SMsQks/KrzXwsWJGi/JSNmy02HUSUH0zmgBscw5ybbZEK193F+hMwRQril1C9pvOrack9tTdBFmJzwAYcyr5NfZCHJ8QuL7jb4L5mY0l4TKy1DCLuPyGTN0hjddTOyoU1Sb1akFzJRx5DPCAGQ26LTleEFBpiG3A7MK2Ae7DNpwDd35JdUcrRFMUyY7wr8KpG7Izpyuxqp3neXjrGJsQkDI0YN9wnRFsc0GQujUuQahAxKMJETHwspFyWuqmqbtjLJHiuXsVvNGEKfDZce4pizIcv1piRHSKh2uJ1KXcydTkh8t4mjfSAzAtj+e77XZ49GDG6E3fiD6kIs0MuxqTk1cBlPnns056BBOpiseARt/lnSRZFmq5runBWCaOUk3mhuQCt35DfWPQAIm6h3aLcI/cm5Itd4heUI0+MbulDC97PpM5HnQzwoAimS3wsz7zSVJwIPJoyt+4Y7s6CQ4+aS24SK5y18pUnj1Tkz+IJ4qqBxbECrUtSpBhGCePo/Bhu1qc4sy6rWm619ZnqFWLmljCiE6ZqIgZklYByTl6zBzWo2o8R7Th/rmJnvZxG9XrT602vN4fqzaYM0WSvOL3i9IpzuOLUrUH8U1bKTq7Afv/KKl6wOKCy6o/P71hMfXvxA4up3oeuGyr3ICyQBjGlWEh/pyIYUd22CLu7yqNvL75rebTFur482pdH+/JoXx7ty6N9ebQvj/bl0b482pdH+/JoXx7ty6Ov7Pzqy6OvpjzK+/Lojy6PXrl0nP+RjT0DSiZon1StS6FW3Uv4I3Jlx63JCnN07R+b3LoE5f0/EmNyPTk7847SSKrlWa6kkZFMzzTkw4vxPwd3wm6//62QFwB/XpU/6wjzyzZNOiKfMJ+54hq2MrTN7GU5ra/k9on1PrHeV3J7ven1pq/k9orTK87fRXF2VXKxqHdfFhdOzsxqSNPZnvDS9e8s38yL9b7ZtnvnZFdE1UclMHPFo27331afZrv7e+vTW5/e+hzt7h6Quzk6Sxwi+8uaryB8P9GUBSA/lJBcwmsrM+szsuU7BuEjCEFywj3xUYLQuRTaoR+fn28ndHCP3FsWXBNdRBFo7TQzVxK/IOdtOoHFa1RbH0YQgbkR9ySIfbahREXmMl4jMHv3wkrLuxcRc/HIUh4Tmzf6am9idEH16QVtxcJeYCG+0OoEARN3Qrt6zu0zfYA1nZQvpQyolcK9L6Zs7lG0TSLL51J89pdO6Bn4l1M0qEebq7l9poVK6YSW6ZKIpemcRQ+j0mwN3dgRPDEsYbunBEaRzCgiwtdRPtfvqFy6QaWc1HLo5WXHKyf1Mxh0fD5+Nzz/ZTj+183FT5OfLibjX0fnv1z8jzafvmg+btHEZS89UcsTd7MpeBqivL7UvGfU1pqO+zTlORsMckfr1r0Gf9/liAn+PsohM9r3Rdylj50zgiset+WFjPYyd5u+Eu194xZFwOjg8sS+jQsvTOwb17wksW9k98WIvTTsugyxb1J1AaJec3DvoeNmwxGb7qvZh8yoK2K3bVmvavtBCb92CQ+UqEOHNqve+xjXqHTvHri531nJ3lqpO62b38u1+/JpeBTuo64uatbg9vC4WagLamrtak1Dj7aLNNuKdwjbN9agn4xqZxnocM5WxYNWWaWtFLM9E1sFhnpqo64QNIflhDpV3iS8Y7lNyloJw2NnN+OWE2ZX0WH7gArCvnZz24CHQV6rtT00DOn2HqQuTAtO5zB6Czbh9MVvu64tsC/bhqZTGoKwXiGWjLAD/Rh3XL0dnY/OO/336VpEiZJCFpp88A6Oxse6iM4hqstQWPILowsXPpHrlBl0pNGbRL/OBlz74cawQO+JeJOpScZiIHMXIVbwVglPgXDrPXpP1cUVfhpZKJlhmGGVhATP0lnH8k44b+yNrlxMjd6tSUBDjZotFljdamBuj+9CYaPAyq2vlje1/iAd0JRHIDTUVz3p+5xFCZCx3Ybar5ycna1WqxGzvbYQ56fqs/9cfbj8OL0cjkfno8RkqVUbdFozJgLA1dt+gnQ+/he83nf8O4CBxTrLU7RPG0/9s3ecb6lznO8HNEGHenJLn5/nTMN/VbrZYPO3AtSaTm7v0UNXnM2Rabd4vCXArPGqXPkPjtLhjQuEvEO//eZgw4+//jS9QbX3bxVmMsY5iq3Q+rIVnVCKLyVW18Bs2zNNmVgWzoNxMPHv/7YTTgw=
-sidebar_class_name: "post api-method"
-info_path: platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Receive an Event"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/event"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Receive a JSON object representing an event.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string"},"type":{"type":"string","enum":["transaction_created","transaction_status_changed","quote_created","customer_updated"],"description":"The transaction event type. Can be one of the following:\n- `transaction_created` - a transaction was created through the SEP endpoints. The payload is in the `transaction` field.\n- `transaction_status_changed` - the status of a transaction has changed. The payload is in the `transaction` field.\n- `quote_created` - a quote was created via the SEP38 API. The payload is in the `quote` field.\n"},"timestamp":{"type":"string","format":"date-time"},"payload":{"type":"object","properties":{"transaction":{"oneOf":[{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"},{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}]},"quote":{"type":"object","properties":{"id":{"type":"string"},"sell_amount":{"type":"string"},"sell_asset":{"type":"string"},"buy_amount":{"type":"string"},"buy_asset":{"type":"string"},"expires_at":{"type":"string","format":"date-time"},"price":{"type":"string"},"total_price":{"type":"string"},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"transaction_id":{"type":"string"},"created_at":{"type":"string","format":"date-time"}},"title":"Quote"},"customer":{"type":"object","properties":{"id":{"type":"string"}},"title":"Customer"}}}},"required":["id","type","payload","timestamp"],"title":"Event"}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"The event is successfully processed and ready to receive next event. The response body is empty."},"400":{"description":"The event is invalid or rejected. The response body contains the error message."}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/put-customer.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/put-customer.api.mdx
deleted file mode 100644
index 85959337ff..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/put-customer.api.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
----
-id: put-customer
-title: "Create or Update Customer Info"
-description: "**The Anchor Platform does not persist any customer KYC data.**"
-sidebar_label: "Create or Update Customer Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJztGmtv47jxrxDsh7tdyHLWF7Sov6Ve78G9XjbNo8UhDmRKGkW8lUgdSSUxAv/3YkjJelhytr0W6AL+ksic4bw4M5wh+UoNe9R0fk8XpTYyB6Xpg0dfJhoKO3yzvJr8kXr2/4dZ9TE7rz5++IDYMehI8cJwKeicvn9/mwK5EFEqFbnKmEmkykksQRMhDSlAaa4NYWJLooon+emXBYmZYf7792uxFkhAwW8lWLyYKNCFFBpIIhUxKdcERFxILgxhCgiPQRgesYwYSUwKa3G/ubq7JdOa/ubh+9SYQs+n00du0jL0I5lPtYEsY6r+PymUNDKS2TTMZDjNmTagphBJvdUG8qmGYnJ29mHm5/EfasKTojTv1mJQ1hgSLiAmXBBnPB9VW2QcUOyiyHjE0GSa5OzLXl9NnrlJUQuSyCyTz1w87m0RynjrkeeURynhGq3xzFQMcaU3YdbofmV8vRZ5qQ15YhmPmQErXm1+REeLk4JpDbFXyW5KJSys1vA7TTY83vjkupYvksIwLlAuKbIt0Ubhd8Ihi1H6LFuLEMaEI6yl4aZlhumvWoqNpY4GMtsCBpmuRcgFU9s2Q/K1/PIyM7xgykzRKSdogB7LtaAelQUoK9QqpnNalKYODurRai3+IuMtnb/SajJ+9pXBMR2lkDP8Qup0TmX4K0SGerRQyMVw0AjlMf7tBhJGweojkUlnQVAht07Ot4yNlcrnZEIYKRQ8cVlqgjFQietTr5bArRfdeZRFkSyd7Iecb1xUEKnIz+ULxOTCYRNWmtTFm4G4se0+0p84cw5/Nsg0h1wOc0QIOmtZR3SyRcdijeqWGSM6ZQpiUomPAQEKrBBdCMbIpvrejAoTuNEhiRCCNrWSldr5Vi3bm4IdcvQoiDLHtMpj6tGU6RRx4MXQh12NfEwQFuFg1x+4JiGgoX76ZRFjGPhrcQPOHve3OPGmgIgnlWv+t1MhijbRbQ7vSCyjMgdh2tnP5u5cYroWifTX4pNUxO0hZCtLEjFRpUz8qYh8FlZtXTs55imXCRL+WLr4bJGZnaPjT+qs6/xoo6GYnU/2+wAaC9fRhfmBOxjFhHY2DsYisoVDeOX/LiP30iaqifyY1jLiGCw++WcKwgJUbuUniZJ5dzljKEDEmrhlXos2v+/Bf/S9xoo1Fa5tnHN0PjRzxtQjZooc3VC/G1Y24UqbQLAcWumpAWfsGJTFMUfWLDuKo0DrwAaD2gaRjIcRtWEGAqmCQsknLqJhrIib7SCgkNqwbJx8JccgLJchzyAQZR6CGsSAnPEsOEYj5MqkAe6wh2CPulWic2oR9uhFxkb0dPA3jRYy8WXc9hZa5aFj2nXw6vwzwusNKkUqxVFLWqxQ4b581OAvBhQ6lvX8BFRQbxmHLpGx8CjLKCwDlnF2dPFzKWB7jEoHz/poPMZPbQsjj3pLhTK8DX6EQkHkcsWdBrIZNsaGcKENsHhwUzPspcpeI6Bxt5FRVBbMCTMYC0Umt6DGCewxjpkgY+KxZI8w7tw8HndGHr8dHDwOuNYlfH1U8jiAl4K7beXfmnbEcXhx1A4aXgbHFSSgFMvGVrGTtIInUPut9+0M9hY6Ogk3GQ5dNXVvVYdb8EANfap0T5XuqdL9lirdU/F3Kv5Oxd+p+DsVf/+z4q9IpZFo8ERJV3qMEnQnmp1JIYu+fOUcIQ1T24AV6J0sC2QS1GS+ksIbdaqjVigpk0CBxrJgKH0Nkh6rcds0ZRJwEckhrxo2Uj0r408gBqUenPf/V1f/XNfSTYG9s4K6KtcqNjs7O8wVN2UUgdaYAv7jE+j6yAirNNyFS3v1M1StD27a5aDZ67LvYrFYXt0uP1KPXl1/XixvblaXP1KPXi6XH2+C1eWnz9Sj18u/LheI9GBLEjzPHxK0qTeuOsK1FbBzuldRB8oMZ5VG5v1A5TIercLbcyGPUnaWYSjDp5JHbXaUKcWQFjeQD8UXZt7CqdeChlJmwETlENW+EwcnIw0a6fd45N4JPfqP5fXq02pxcbv6fBlcL/9+t7qunBOUkkNp3q5ODlqzx6HNqBX1P0Krm3bhXU0/HwrwlbDXdu5W9PdEeXd1x/TwhiN9180SbvZDo9TSDtRqnB+qcSkN+SRLEX8LOlT1p9B4K0vn96/0C2zpvL4N96httb7uVnz3gH5hUlndIKIWzKR0Tve30hR3R/WEV+7Iq1QZndO6ZY1YlmEN4Iel5rjHTRyuDy8sL9Dr7VVvJHOKrNCG183N5NIh1Rm8CYb9QUgz5IrR7u+qAHPNez+g+rckrT231VU2o61msiVIv4fsgAZaxwY+0DE2QNcoNr87/eEBj47e3W6wlUC6TWA7Aza9H52dzc4nZ3+azP5Me21ef8KYXq2mrjfY7+VGwP2F6nRuveFuw9YD9vq0lilG2rOW/TtdWWu8acYOTN7twUbATevVItrruA4gfenq7qg/cmD2di/U9oROCzQAGBCl1/A0gH2f0xka845eV9P1t6EG5gDj0MDtur8VX1iyNz87VfNIuPSq35HYGcHCxC0S2xBjMnSwH/wz/4z23xbZ49qtiFIlBZ77LqosqcnF1Yp0zuaqt0LN8W7/RVKhJG4vfv3gaJyuO2nTzROdnMVAwm33NPg55RkQbs9iCyWxPHeHuvXrHXvXy0h08ALIJ7d40+tS+nd6f8itq6csuvU6iCUJRKbLuY8/xMIdA1ZbXqPejd1U0Et5BFiSzF9p5dwXBYtSIDO7DM3mNJ9On5+ffWahvlSP02qqnv5ttVhe3iwnM//MT02e2b0XE3DORIvwQgG+RpKK3BX2XVJdF5EVusFB+bgvG05Py05Py771p2VVxsebkGmRMW6bFxtdr1WBeE/3BeKDR1OpDY69voZMw53Kdjsc/q0EtaXz+wcsShVnIcb1PXYqKTC7S+6r14WTYXLrmr+qhh28xtt59aSLKILCtNAPCvZOgXt1d4u1Q/UmLndbF9K1ZL3mE2Xc7f4Fg5L/Sw==
-sidebar_class_name: "put api-method"
-info_path: platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-12,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create or Update Customer Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"put"}
-  path={"/customer"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-**The Anchor Platform does not persist any customer KYC data.**
-
-The request and response for this endpoint are identical to the
-[`PUT /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-put)
-request and response defined in SEP-12.
-
-Client applications make requests with the following request body, which is forwarded to the anchor. Anchors
-must validate and persist the data passed, and return the customer's `id`. Requests containing only string fields will
-be forwarded to the anchor as with the `application/json` content type. Requests containing
-binary fields will be forwarded to the anchor as with the `multipart/form-data` content type.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","properties":{"id":{"description":"The ID of the customer as returned in the response of a previous PUT request.","type":"string"},"account":{"description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","type":"string"},"memo":{"description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","type":"string"},"memo_type":{"description":"The type of memo used to identify a customer with a shared account.","type":"string","enum":["id","hash","text"]},"type":{"description":"The type of action the customer is being KYCd for.\nSee the [Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification) documented in SEP-12 for more info.\nFor SEP-31 you can define your own types in the assets configuration.\nFor SEP-24 pre-defined value `sep24-customer` is used.\n","type":"string"},"transaction_id":{"description":"The transaction id with which the customer's info is associated. When information from the customer depends on the\ntransaction (e.g., more information is required for larger amounts)\n","type":"string"},"first_name":{"type":"string"},"last_name":{"type":"string"},"additional_name":{"type":"string"},"address_country_code":{"type":"string"},"state_or_province":{"type":"string"},"city":{"type":"string"},"postal_code":{"type":"string"},"address":{"type":"string"},"mobile_number":{"type":"string"},"email_address":{"type":"string"},"birth_date":{"type":"string","format":"date"},"birth_place":{"type":"string"},"birth_country_code":{"type":"string"},"bank_name":{"type":"string"},"bank_account_number":{"type":"string"},"bank_account_type":{"type":"string"},"bank_number":{"type":"string"},"bank_phone_number":{"type":"string"},"bank_branch_number":{"type":"string"},"external_transfer_memo":{"type":"string"},"clabe_number":{"type":"string"},"cbu_alias":{"type":"string"},"mobile_money_number":{"type":"string"},"mobile_money_provider":{"type":"string"},"crypto_address":{"type":"string"},"crypto_memo":{"description":"Deprecated. Use `external_transfer_memo` instead.","type":"string"},"tax_id":{"type":"string"},"tax_id_name":{"type":"string"},"occupation":{"type":"string"},"employer_name":{"type":"string"},"employer_address":{"type":"string"},"language_code":{"type":"string"},"id_type":{"type":"string"},"id_country_code":{"type":"string"},"id_issue_date":{"type":"string","format":"date"},"id_expiration_date":{"type":"string","format":"date"},"id_number":{"type":"string"},"ip_address":{"type":"string"},"sex":{"type":"string"},"referral_id":{"type":"string"},"mobile_number_verification":{"type":"string"},"email_address_verification":{"type":"string"}},"title":"PutCustomerRequest"}},"multipart/form-data":{"schema":{"type":"object","properties":{"id":{"description":"The ID of the customer as returned in the response of a previous PUT request.","type":"string"},"account":{"description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","type":"string"},"memo":{"description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","type":"string"},"memo_type":{"description":"The type of memo used to identify a customer with a shared account.","type":"string","enum":["id","hash","text"]},"type":{"description":"The type of action the customer is being KYCd for.\nSee the [Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification) documented in SEP-12 for more info.\nFor SEP-31 you can define your own types in the assets configuration.\nFor SEP-24 pre-defined value `sep24-customer` is used.\n","type":"string"},"first_name":{"type":"string"},"last_name":{"type":"string"},"additional_name":{"type":"string"},"address_country_code":{"type":"string"},"state_or_province":{"type":"string"},"city":{"type":"string"},"postal_code":{"type":"string"},"address":{"type":"string"},"mobile_number":{"type":"string"},"email_address":{"type":"string"},"birth_date":{"type":"string","format":"date"},"birth_place":{"type":"string"},"birth_country_code":{"type":"string"},"bank_name":{"type":"string"},"bank_account_number":{"type":"string"},"bank_account_type":{"type":"string"},"bank_number":{"type":"string"},"bank_phone_number":{"type":"string"},"bank_branch_number":{"type":"string"},"external_transfer_memo":{"type":"string"},"clabe_number":{"type":"string"},"cbu_alias":{"type":"string"},"mobile_money_number":{"type":"string"},"mobile_money_provider":{"type":"string"},"crypto_address":{"type":"string"},"crypto_memo":{"description":"Deprecated. Use `external_transfer_memo` instead.","type":"string"},"tax_id":{"type":"string"},"tax_id_name":{"type":"string"},"occupation":{"type":"string"},"employer_name":{"type":"string"},"employer_address":{"type":"string"},"language_code":{"type":"string"},"id_type":{"type":"string"},"id_country_code":{"type":"string"},"id_issue_date":{"type":"string","format":"date"},"id_expiration_date":{"type":"string","format":"date"},"id_number":{"type":"string"},"photo_id_front":{"type":"string","format":"binary"},"photo_id_back":{"type":"string","format":"binary"},"notary_approval_of_photo_id":{"type":"string","format":"binary"},"ip_address":{"type":"string"},"photo_proof_residence":{"type":"string","format":"binary"},"sex":{"type":"string"},"photo_proof_of_income":{"type":"string","format":"binary"},"proof_of_liveness":{"type":"string","format":"binary"},"referral_id":{"type":"string"},"mobile_number_verification":{"type":"string"},"email_address_verification":{"type":"string"}},"title":"PutCustomerMultipartRequest"}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","required":["status"],"properties":{"id":{"type":"string"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","NEEDS_INFO","REJECTED"]},"fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"}}}},"provided_fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","REJECTED","VERIFICATION_REQUIRED"]},"error":{"type":"string"}}}},"message":{"type":"string"}},"title":"GetCustomerResponse"}}}},"400":{"description":"Invalid data.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Not Found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/versions.json b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/versions.json
deleted file mode 100644
index 23f5ac539d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/callbacks/versions.json
+++ /dev/null
@@ -1,12 +0,0 @@
-[
-  {
-    "version": "3.0.0",
-    "label": "v3.0.0",
-    "baseUrl": "/platforms/anchor-platform/next/api-reference/callbacks"
-  },
-  {
-    "version": "2.8.4",
-    "label": "v2.8.4",
-    "baseUrl": "/platforms/anchor-platform/api-reference/callbacks"
-  }
-]
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/README.mdx
deleted file mode 100644
index e1d1afd50d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Servidor de Custodia
-sidebar_position: 30
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-El Servidor de Custodia proporciona un conjunto de endpoints para interactuar con servicios de custodia, como Fireblocks.
-
-<MethodTable title="Puntos finales del Servidor de Custodia">
-
-|                                                                    |   |
-| ------------------------------------------------------------------ | - |
-| [Transacción de Custodia](./create-custody-transaction.api.mdx)    |   |
-| [Pago](./send-payment.api.mdx)                                     |   |
-| [Reembolso](./send-refund.api.mdx)                                 |   |
-| [Generación de dirección única](./generate-unique-address.api.mdx) |   |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/create-custody-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/create-custody-transaction.api.mdx
deleted file mode 100644
index ec0c146793..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/create-custody-transaction.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: create-custody-transaction
-title: "Create Custody Transaction"
-description: "Custody Server creates custody transaction record in DB."
-sidebar_label: "Create Custody Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJytV0tz2zYQ/is7uPRCS67T9sCb4zhTTx/R1O7J8WEFrkTEIMAAS8kcjf57ZgFKlGXFk6TVQaKX+358u96oiqIOpmXjnSrVVRfZVz3cUlhRAB0ImSLogcwBXUQtzBBI+1CBcfDu7UQVyrcUUN7cVKpUWXJQdzeKqUIxLqMq7/e2Dt5G9VCop7NIbeK4vZ6d/aaK9Hvxy/Dw5mdhCvS5o8hvfdWrcqO0d0yO5RHb1hqdPJl+ihLVRkVdU4PyxH1LqlR+/ok0q0K1QfxmQ1Hemkq+n6fk9nr2LO6bdxLtoCdyMG6ptoVqqPEvhf+ixsMKbUcFcI0MJkIXqQL2YCpybBY9GDf3navAB/Ad5+cW+4Ycx6/aukvEY3tCBb8A4fjfLBaKXNdIQUylClVjrIWHnlg9bFMK2WtvX3ozG96IR0dpfM2KlDyVW0q9LdQi+OZSa9/lAh+Vx3dBE9wyWYsBMPOdTBv7r2p5R5GNS03zTaqwOa3nMtElXq4JMEbisQyRHE8DaTIrql5R+55OVPY90TelUbSI2RO+fa83j8admIc/jDRODvA7ilpR66ORkVsbrquAa7RK5jg5oB626SOE2HoX8zxenJ+fqHinNcXUpz849tnSr6eU3zim4NDuEPA6BB9+3FIGKhOokhxQUvZwjDqZPMruKiAta9jSiMvZmyFT9MTkYkLN8n6jHqlX5Q48C5VA51UQ3T4IknDtBa9bHxMcIteqVFM+xORCxZSMbKcLVpWqZm5jOZ0Om+Esc0zoCZvWEjpd+zDRvlFiRbL0zwjY15lpB7hjr2QMff53xrmMPCPSJIx4hguj1MGYj8TdwB5T0qwdEPPojIQ8A/vu3RbKuEUCeklI7pk3k/PJuXpRrKGFVHGM0TXtF2oc9qx3jjRHAWmSDmyDiQRrtJYY2uBXpqIQC4idrgEjvDeB5tbrx1iITCRXAboKhnHagzksfDic0AjGGTbIVMHKYBriy1QsmFnkhQ/NBO7qBA9hZTQJUqADtGksWHSzz7M/wOSH+RCEmJp30TiKkSKsay+LB7yjHVzErm19ENv7kCZw4wCryiToHVQvOpe8RWu4B79YUKAK5v1Ju0WiHh8uyefoYYHaWMPI9HLTiTltDTn+KR6jvji2gN53WY0EImZolQSH5BTPVPW+G8VhbawFDma5pAAIv9/dzUCjtXPUj9BgRXuRXc6GZph8dB/d3nYgrHqocUVSBuOYlvnKAoHRrOCoTVJCHLBUUfum9Y5cQnznGXZwVEhJa98t65NOZPcd5bvB+XQ1nGgWWIsp3OVBNp7Xub2Sf+heSBzeUmvMe0iM+AAy0Nmd42rsm3Wv5nJ2kzJ11YVAjm12zzvbn2gziX4cmclHOUOt0eRiQiGHjcztZYu6JrhIwzzCXDmdrtfrCaa3Ex+W00E0Tv+8ubr++/b67GJyPqm5sQmzBUobdAeKr9IxDCcO3mNwOLhk/8stPiwSOdGmrUXjBLhSRJsB4u8VH53dtWyA8l5tNnOM9G+w262QP3cUelXeP8hKCQbnAnH3cpbVhBWFg91zlV0/S5C930Av9+W22Elcak0tv8p7uKRmH27vVKHmw9Hf+EpkAq5lz+JalSr9H5JDKjeZtlEW3bLDpfBmnfL5AvWzi8k=
-sidebar_class_name: "post api-method"
-info_path: platforms/anchor-platform/api-reference/custody/custody-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Custody Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Custody Server creates custody transaction record in DB.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","properties":{"id":{"description":"SEP transaction ID.","type":"string"},"memo":{"description":"Memo value, that is used to identify inbound or outbound payments.","type":"string"},"memoType":{"description":"Type of memo, that is used to identify inbound or outbound payments.","type":"string","enum":["id","hash","text"]},"protocol":{"description":"Protocol of SEP transaction.","type":"string","enum":["6","24","31"]},"fromAccount":{"description":"Source Stellar account.","type":"string"},"toAccount":{"description":"Destination Stellar account.","type":"string"},"amount":{"description":"Amount of the asset, that is sent/received.","type":"string"},"amountFee":{"description":"Fee of SEP transaction.","type":"string"},"asset":{"description":"Asset, that is sent/received.","type":"string"},"kind":{"description":"Kind of the SEP transaction.","type":"string","enum":["deposit","withdrawal","receive"]}}}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object"}}}},"500":{"description":"Internal Server Error","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/generate-unique-address.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/generate-unique-address.api.mdx
deleted file mode 100644
index 900893c971..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/generate-unique-address.api.mdx
+++ /dev/null
@@ -1,78 +0,0 @@
----
-id: generate-unique-address
-title: "Generate Unique Address"
-description: "Custody Server calls the configured custody service to generate deposit address and memo."
-sidebar_label: "Generate Unique Address"
-hide_title: true
-hide_table_of_contents: true
-api: eJylVsFS20gQ/ZWuuexFyCyQUKWbAyahlmQJJlC7G6oYj1rWhNG0MtOycVH+91SPZEOA3cPmJJXc3e9Nv9c9flAlRhNsy5a8KtRRF5nKFUwxLDCA0c5F4BrBkK/svAtYghliIoaFNQhMMEePQTNCiS1Fy6DLMmCMoH0JDTaUf/Vf/QmFRjNQBbc6RuRbaHXQDTIG2IHbyOicDsWX6fFR8f7du+ODw9OTt2fXfxyeH348nlxNj64vDo/Pv1xf7X/6a//48vPk6uTs4NP48mD8+cP+32dnJ2fjN7dfvcoUtULHkj8tVaE27L54+73DcU9NZYr1PKrin+2h+99hE3CTqfudiG2KmU7Od96qLD33DoaX/d8lKOD3DiO/o3KligdlyDN6llfdts6aRGT0LUqDH1Q0NTZa3njVoioUzb6hYbVer9dSK7bkI0YJ2NvdlcfPCk07YzDGXGX/FylTbZAGse1hBq1eQh0/E5MJlrU1dW8IZ9EzxJo6V0JEX0LV+TIRG/AiB+vnap0pscDL+h+xIVho12EGXOttsRkKJJYC2OpVIziz1RPUf8W4TB+f48hXcZ1E/DJSptB3jVjClipTtY61xOA9qxtRkC07CX//mukuBnkHtd+8JvCpZwxeu80MTkKg8Etyi0FtwFJIo1QT1/7sgf7zY+6mrU8ONExJopP4rzOF94w+WvIyIw/qDleq2AxNppK0/zk86xvRjWuSMW0pJnNqrlWhRmlFxFGRnqPBgyh1Y2pMD9kFpwpVM7exGI2G1bTTR+R4r5vWofamppAbapQASsMuHmd20gep4mGdKeurZFSp38uxn+/mu+pFGwZ1VPbca2KdJwtSlih5j4bT/KCI2wYbEZbaOWRoAy1siSFmEDtTg45wYgPOHJm7mElOmi1ZpAEN2gVunBqhogActI/aCHwE6y1bzVjCwupk43E6O5w7zRWFJofL2sbt6rayoUG75DiW2kwpbdrvYvhzNhxCoGZdtD6JAMuaoIsI5NNkSUrs2paCYG+PlMOplwGzwm5Tuup8Yqud5RVQVaFcKsPUPcfN0tcXt5JwjgSVNtZZlouHOp5R58vH5jANM/xb3JbVxlDnWYhVsKKuLyMHERhcpMShOdlPpVbUPabD0joHHOx8jgE0fLi8PE935UybO2h0iduUTc8GM6R7cIsdUJcrqPUCRQbrGef9tQVLy3Vf4JlNUkM8sKhoqGnJy86yETwxbAY9E0lr6ub1qyR6+h77veeJbbV6zSywFCi93Yw6RjK9vRI/7V9kPHEjLLUAehYQClAFano6z9XYmnVbZnx+mjp11IWAnl1Pj7xbvWIzOf3jyOTpD4CzBmXPFg/K60bmdtxqUyPspWF+3BrFaLRcLnOdfs0pzEdDahydnR5NPk0nO3v5bl5z42Tp/QApKz98
-sidebar_class_name: "post api-method"
-info_path: platforms/anchor-platform/api-reference/custody/custody-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Generate Unique Address"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/assets/:asset/addresses"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Custody Server calls the configured custody service to generate deposit address and memo.
-
-Format of `asset` parameter - `stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5`
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object"}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","properties":{"address":{"description":"Deposit address to which the client should send funds.","type":"string"},"memo":{"description":"Memo value, that should be added to payment by the client.","type":"string"},"memoType":{"description":"Type of memo, that should be added to payment by the client.","type":"string","enum":["id","hash","text"]}},"title":"GenerateUniqueAddressResponse"}}}},"500":{"description":"Internal Server Error.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/send-payment.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/send-payment.api.mdx
deleted file mode 100644
index 68a7e02b9c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/send-payment.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: send-payment
-title: "Send Payment"
-description: "Custody Server calls the configured custody service to send payment."
-sidebar_label: "Send Payment"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVk1v4zYQ/SsDXnpRZDdJC1S3NHVRA0UbxD4s0OyBpkYWNxSpckZ2BMP/vRhKtpPY3QXaS04SSM7HezN8w50qkUy0LdvgVaHuO+JQ9rDAuMEIRjtHwDWCCb6y6y5iCWY8Qxg31iBwAEJfQqv7Bj3nKlOhxajF5bxUhZLdh2FTZYr1mlTxlxpXSH3O1MsVYZtWF7OHqx9Vlr7Xt+PPzfdyKOLfHRL/HMpeFTtlgmfxWOyUbltnTQo4+UICZKfI1Nho+eO+RVWosPqChtV+v9+LL2qDJyQ5cD2dyuctE4vOGCQSNP8xUqbaKESwHcLY8tUZ4mj9WmXvos5eGKPXDpafYP4LVDE07/nOlQBgy078LE7cPo6YRoi3l1DN/UY7W8LjwOX/Qif1sBFLKRvGGKIU6S3kYfkM9WsAY8fN0slD5rfnmR86cxm1J21kFSyBDwxV6Hz5QaFc//TvUBbjBYqaEZxtLAsifDGIJX5QQD9c7qqxa0fZSAYfNf+bbxfEEnReb7R1euXwIwLZZwpfGD3Z4EU3d+oZe1UchDRTG+06/Kqg7j9nqkGug0h0GygJluZaFWrCp0tGk8KWk/Yg1pmiVOMhaBedKlTN3FIxmYxCdTWcyPFFN61D7U0dYm5CoySkUPZ4UvLZcEgVu32mrK+CECH+h8rc5NN8qs6IGBvtTD6XMqleyaWMsOA9GiYZUyh92kZLCFvtHDK0MWxsiZEyoM7UoAl+tRFXLphnyo6jTfsSIhq0GzyMOYIqRHhNFFhv2WrGEjZWp6l5l7DDg9NchdjksKwtHQenJdAetEuXh8U3h2S2YHROR/hzNYKQUKuOrEciJNjWATpCCB4hVMmEurYNUWIfIeUw96DL0iatHF1XnU/Zame5h1BVKCN91V+Mm6XVszeB5EwBKm2ssyziFTpeiQifyOEAxln0/B0d3WpjQudZEqugD93gRoBIGNwkw5Gc7I2rPnQnc9ha54CjXa8xgobflsuH9FJZafMMjS7xaHLgbGyG/Mk/+WPsiLrsodYblDJYz7geHi2wtVwPDt61SSLEA0sVTWja4NHzYQwdrnomJa1Dt64vJjGk7xFLSdMHtlV/qVlgK6H0gQfQRMEM7ZXy0/7M4lU3wlZLQM8SJMThJZHSeV+NY7Me3dw9zBNT912M6NkN6QXv+gttJuhPVyZ/8ipTzhqUh0ixU143cm/vWm1qhOt0mU+qUUwm2+0212k3D3E9GU1p8vv8fvbHYnZ1nU/zmhsnsvcPSXzImw==
-sidebar_class_name: "post api-method"
-info_path: platforms/anchor-platform/api-reference/custody/custody-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Send Payment"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/transactions/:id/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Custody Server calls the configured custody service to send payment.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object"}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"External TX ID from custody service."}},"title":"SendPaymentResponse"}}}},"400":{"description":"Invalid Request.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}},"404":{"description":"Custody Transaction is not found.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}},"429":{"description":"Custody Service rate limit is exceeded.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}},"500":{"description":"Internal Server Error.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}},"503":{"description":"Custody Service is unavailable.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/send-refund.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/send-refund.api.mdx
deleted file mode 100644
index 08eb1ac79f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/send-refund.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: send-refund
-title: "Send Refund"
-description: "Custody Server calls configured Custody Service to send refund. Custody transaction record is also created in DB."
-sidebar_label: "Send Refund"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVktv4zYQ/isDXnpR5DRJC1S3bNZBDfQRxD4UaPZAUyOLG4pUOSM7QrD/fTGU/Ijtbg/bQ3yxMCRn5pvXN6+qRDLRtmyDV4W664hD2cMc4xojGO0cgQm+sqsuYgmH59YgcABCX0LEqvNlvjvnqD1pI1ohogmxBEugHQUwETVjCdbDxw+5ylRoMWq5OStVoUTdY9KmMsV6Rar4Ww0CUp8y9XJB2CbhfPpw8bPK0v/Vzfhx/aNcivhPh8QfQtmr4lWZ4Bk9y6duW2dNMjf5TIL5VZGpsdHyxX2LqlBh+RkNq0y1UZxjiySnDTZB/t+G7HdsAqy16zADrjXDxjoHSwRdllhKhLjGMUDQ6r5BzwJ7tEUcrV+pL1lSv0jCYxMihVCB3PhOI7oJ3RCJtyZuk/xI+aAPy29ouscz/t5jcnfv0hkF6SeZojZ4GgJ8dXl5qmzeGYNEouJ/yqMtD+6M/mRHVqcvjNFrB4u/YPYRqhgaMGNx01D8uRIAbNmJnjn68mEI/OOISQ0Qb86hmvm1draEx6FSvwudVLuNWEpTYIwhSgu8hTyIT1AfAhhbd5pubj2/OfV82+KLgxa3BD4wVGHM9TuEcvXLv0PZTrOoGcHZxrIgwheDOFb/+wP00/mqGqt2nN/pwXv1//q/E2IJOq/X2jq9dPgegXzJFL4werLBCyu9qmfsVbGlqUwlZvgmXX35JLOf6yD01wZKA0tzrQo1OeBRmhS2nMSRCTNFKcWDzS46VaiauaViMhnn1MVwI8cX3bQOtTd1iLkJjRKLErHHPU1Oh0t7mtsPxj0v7WVbGjmWJDo4IAnrq0SZ4umQ4uv8Mr9UJxEdK/ZkDi9qfDN3ZSkJ3qNhEtZDKfg2WkLYaOeQoY1hbUuMlAF1pgZNcG8jLl0wz5TtFhadlhaDdo1bviSoQjzcXAist2zTtrK2OvHZbYoiPDjNVYhNDova0pYR0o7jQbvUhSy6R2aeMzqnI/y5HEGIqWVH1iMREmzqAB0hBL9jTuraNkSxvYOUw8wL49s0dEfVVeeTt9pZ7iFUFcqituzP2s2S9GTL88NqVmljnWWZgqHjZThYJlK0jbPo+QfaqdXGSNbFsQr60A1qBIiYwXV6OAYne6OqD93++bBwcLSrFUbQ8Oti8ZB2z6U2z9DoEndPtjEbiyF/8k9+ZzuiLnuo9RolDdYzrobNEjaW60HBUZmkgHhgyaIJTRs8et7y2XZmZJLSOnSr+qwTg/seh0XMB7ZVf65YYCOm9DYOoImCGcor+af9yYvDPXqjxaBnMRLisJIkd46zsSvWnZrbh1mK1F0XI3p2g3vBu/5MmQn6fcvkT15lylmDstEUr8rrRvr2ttWmRrhKzbyfP8Vkstlscp1O8xBXk/EpTX6b3U3/mE8vrvLLvObGyfz8CoE2aek=
-sidebar_class_name: "post api-method"
-info_path: platforms/anchor-platform/api-reference/custody/custody-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Send Refund"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/transactions/:id/refunds"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Custody Server calls configured Custody Service to send refund. Custody transaction record is also created in DB.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","properties":{"memo":{"description":"Memo value, that will be added to the refund payment.","type":"string"},"memoType":{"description":"Type of memo, that will be added to the refund payment.","type":"string"},"amount":{"description":"Amount, that will be refunded.","type":"string"},"amountFee":{"description":"Fee of the refund.","type":"string"}}}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"External TX ID from custody service."}},"title":"SendPaymentResponse"}}}},"400":{"description":"Invalid Request.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}},"404":{"description":"Custody Transaction is not found.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}},"429":{"description":"Custody Service rate limit is exceeded.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}},"500":{"description":"Internal Server Error.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}},"503":{"description":"Custody Service is unavailable.","content":{"application/json":{"schema":{"type":"object","required":["error"],"properties":{"error":{"type":"string"}},"title":"CustodyError"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/versions.json b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/versions.json
deleted file mode 100644
index 26d39ec7ce..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/custody/versions.json
+++ /dev/null
@@ -1,12 +0,0 @@
-[
-  {
-    "version": "3.0.0",
-    "label": "v3.0.0",
-    "baseUrl": "/platforms/anchor-platform/next/api-reference/custody"
-  },
-  {
-    "version": "2.8.4",
-    "label": "v2.8.4",
-    "baseUrl": "/platforms/anchor-platform/api-reference/custody"
-  }
-]
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/README.mdx
deleted file mode 100644
index ebda808b42..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/README.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Servidor de Plataforma
-sidebar_position: 10
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Los datos en la Anchor Platform están disponibles a través de dos APIs diferentes: una API REST y una API JSON-RPC. Cada una de estas APIs tiene documentación asociada aquí.
-
-<MethodTable title="Tipos de API">
-
-|                                       |   |
-| ------------------------------------- | - |
-| [API REST](./transactions/README.mdx) |   |
-| [API JSON-RPC](./rpc/README.mdx)      |   |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/README.mdx
deleted file mode 100644
index defc48aa42..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: API JSON-RPC
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Interactúa con tu instancia de Anchor Platform a través del uso de solicitudes RPC ligeras y fáciles de usar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/anchor-platform.openrpc.json b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/anchor-platform.openrpc.json
deleted file mode 100644
index c3ff0ede70..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/anchor-platform.openrpc.json
+++ /dev/null
@@ -1,10163 +0,0 @@
-{
-  "openrpc": "1.2.6",
-  "info": {
-    "title": "Anchor Platform",
-    "description": "The Anchor Platform is a set of tools and APIs that enable developers and businesses to build their own on and off-ramp services for the Stellar network. It provides a standardized interface, including the implementation of several Stellar Ecosystem Proposals (SEPs), to make it easy for businesses to integrate with Stellar-based wallets and exchanges.",
-    "termsOfService": "https://stellar.org/terms-of-service",
-    "contact": {
-      "name": "Stellar Development Foundation",
-      "url": "https://stellar.org/connect",
-      "email": "hello@stellar.org"
-    },
-    "license": {
-      "name": "Apache 2.0",
-      "url": "https://www.apache.org/licenses/LICENSE-2.0.html"
-    },
-    "version": "2.8.4"
-  },
-  "servers": [
-    {
-      "name": "Platform API",
-      "url": "https://platform-server.exampleanchor.com",
-      "summary": "Example URL endpoint for the Platform Server.",
-      "description": "Example URL endpoint for the Platform Server. Note: This is an example URL only, you must configure your own Platform Server."
-    }
-  ],
-  "methods": [
-    {
-      "name": "do_stellar_payment",
-      "summary": "Submits a Stellar payment",
-      "description": "Submits a payment to a stellar network by a custody service.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "do_stellar_paymentResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "do_stellar_paymentExample",
-          "description": "Example request to the `do_stellar_payment` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Do Stellar payment"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "do_stellar_refund",
-      "summary": "Submits a Stellar refund",
-      "description": "Submits a refund payment to a stellar network by a custody service",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "refund",
-          "description": "An object describing refund associated with this transaction.",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "amount_fee"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "Amount to be refunded",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "Amount of assets to refund",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of refund",
-                    "type": "string"
-                  }
-                }
-              },
-              "amount_fee": {
-                "title": "amount_fee",
-                "description": "Amount of fee",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "The amount of fee",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of fee charged by anchor",
-                    "type": "string"
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "do_stellar_refundResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "do_stellar_refundExample",
-          "description": "Example request to the `do_stellar_refund` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Do Stellar refund"
-            },
-            {
-              "name": "refund",
-              "value": {
-                "amount": {
-                  "amount": 1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                },
-                "amount_fee": {
-                  "amount": 0.1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                }
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "get_transaction",
-      "summary": "Retrieve a transaction.",
-      "description": "Retrieve a transaction by its ID.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "get_transactionResponse",
-        "schema": {
-          "title": "Platform Transaction",
-          "description": "A platform transaction object",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "funding_method": {
-              "description": "Funding method used for transferring or settling assets.",
-              "type": "string"
-            },
-            "type": {
-              "description": "DEPRECATED in favor of funding_method. Type of deposit, withdrawal or receive.",
-              "type": "string"
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "user_action_required_by": {
-              "title": "user_action_required_by",
-              "description": "Time and date by which user action is required.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "stellar_transactions": {
-              "type": "array",
-              "items": {
-                "title": "stellar_transaction",
-                "type": "object",
-                "required": [
-                  "id",
-                  "created_at",
-                  "envelope",
-                  "payments"
-                ],
-                "properties": {
-                  "id": {
-                    "title": "hash",
-                    "description": "The Stellar transaction hash.",
-                    "type": "string"
-                  },
-                  "memo": {
-                    "title": "memo",
-                    "type": "string"
-                  },
-                  "memo_type": {
-                    "title": "memo_type",
-                    "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-                    "type": "string",
-                    "enum": [
-                      "id",
-                      "hash",
-                      "text"
-                    ]
-                  },
-                  "created_at": {
-                    "title": "created_at",
-                    "description": "The date and time when the transaction is created.",
-                    "type": "string"
-                  },
-                  "envelop": {
-                    "description": "The transaction envelope, containing all the transaction information.",
-                    "type": "string"
-                  },
-                  "payments": {
-                    "type": "array",
-                    "items": {
-                      "required": [
-                        "id",
-                        "payment_type",
-                        "source_account",
-                        "destination_account",
-                        "amount"
-                      ],
-                      "properties": {
-                        "id": {
-                          "description": " The ID of the payment in the Stellar Network.",
-                          "type": "string"
-                        },
-                        "payment_type": {
-                          "description": " The ID of the payment in the Stellar Network.",
-                          "type": "string",
-                          "enum": [
-                            "payment",
-                            "path_payment"
-                          ],
-                          "default": "payment"
-                        },
-                        "source_account": {
-                          "title": "source_account",
-                          "description": "The account being debited in the Stellar Network.",
-                          "type": "string"
-                        },
-                        "destination_account": {
-                          "title": "destination_account",
-                          "description": "The account being credited in the Stellar Network.",
-                          "type": "string"
-                        },
-                        "amount": {
-                          "type": "object",
-                          "properties": {
-                            "amount": {
-                              "title": "amount",
-                              "description": "A stringified amount of an asset.",
-                              "type": "string"
-                            },
-                            "asset": {
-                              "title": "asset",
-                              "description": "An asset.",
-                              "type": "string"
-                            }
-                          }
-                        }
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "source_account": {
-              "title": "source_account",
-              "description": "The account being debited in the Stellar Network.",
-              "type": "string"
-            },
-            "destination_account": {
-              "title": "destination_account",
-              "description": "The account being credited in the Stellar Network.",
-              "type": "string"
-            },
-            "external_transaction_id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "memo": {
-              "title": "memo",
-              "type": "string"
-            },
-            "memo_type": {
-              "title": "memo_type",
-              "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-              "type": "string",
-              "enum": [
-                "id",
-                "hash",
-                "text"
-              ]
-            },
-            "refund_memo": {
-              "title": "memo",
-              "type": "string"
-            },
-            "refund_memo_type": {
-              "title": "memo_type",
-              "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-              "type": "string",
-              "enum": [
-                "id",
-                "hash",
-                "text"
-              ]
-            },
-            "client_domain": {
-              "description": "The domain of the client.",
-              "type": "string"
-            },
-            "client_name": {
-              "description": "The domain of the client.",
-              "type": "string"
-            },
-            "customers": {
-              "description": "The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\n            this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.",
-              "type": "object",
-              "properties": {
-                "sender": {
-                  "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                  "type": "object",
-                  "properties": {
-                    "id": {
-                      "type": "string",
-                      "description": "The `id` of the customer registered through SEP-12."
-                    },
-                    "account": {
-                      "type": "string",
-                      "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                    },
-                    "memo": {
-                      "type": "string",
-                      "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                    }
-                  }
-                },
-                "receiver": {
-                  "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                  "type": "object",
-                  "properties": {
-                    "id": {
-                      "type": "string",
-                      "description": "The `id` of the customer registered through SEP-12."
-                    },
-                    "account": {
-                      "type": "string",
-                      "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                    },
-                    "memo": {
-                      "type": "string",
-                      "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                    }
-                  }
-                }
-              }
-            },
-            "creator": {
-              "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-              "type": "object",
-              "properties": {
-                "id": {
-                  "type": "string",
-                  "description": "The `id` of the customer registered through SEP-12."
-                },
-                "account": {
-                  "type": "string",
-                  "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                },
-                "memo": {
-                  "type": "string",
-                  "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "get_transactionExample",
-          "description": "Example request to the `get_transaction` method.",
-          "params": [
-            {
-              "name": "id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            }
-          ],
-          "result": {
-            "name": "platformTransactionResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "31",
-              "kind": "receive",
-              "status": "completed",
-              "funding_method": "SWIFT",
-              "amount_expected": {
-                "amount": "100",
-                "asset": "iso4217:USD"
-              },
-              "amount_in": {
-                "amount": "100.0000",
-                "asset": "iso4217:USD"
-              },
-              "amount_out": {
-                "amount": "98.0000000",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "fee_details": {
-                "total": "2.0000",
-                "asset": "iso4217:USD"
-              },
-              "quote_id": "quote-id",
-              "message": "Please don't forget to foo bar",
-              "refunds": {
-                "amount_refunded": {
-                  "amount": "90.0000",
-                  "asset": "iso4217:USD"
-                },
-                "amount_fee": {
-                  "amount": "8.0000",
-                  "asset": "iso4217:USD"
-                },
-                "payments": [
-                  {
-                    "id": "1111",
-                    "id_type": "stellar",
-                    "amount": {
-                      "amount": "50.0000",
-                      "asset": "iso4217:USD"
-                    },
-                    "fee": {
-                      "amount": "4.0000",
-                      "asset": "iso4217:USD"
-                    }
-                  },
-                  {
-                    "id": "2222",
-                    "id_type": "stellar",
-                    "amount": {
-                      "amount": "40.0000",
-                      "asset": "iso4217:USD"
-                    },
-                    "fee": {
-                      "amount": "4.0000",
-                      "asset": "iso4217:USD"
-                    }
-                  }
-                ]
-              },
-              "stellar_transactions": [
-                {
-                  "id": "stellar-tx-id",
-                  "memo": "my-memo",
-                  "memo_type": "text",
-                  "envelope": "here_comes_the_envelope",
-                  "payments": [
-                    {
-                      "id": "payment-id",
-                      "amount": {
-                        "amount": "100.0000",
-                        "asset": "iso4217:USD"
-                      },
-                      "payment_type": "payment",
-                      "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-                      "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-                    }
-                  ]
-                }
-              ],
-              "external_transaction_id": "external-tx-id",
-              "customers": {
-                "sender": {
-                  "id": "sender-id"
-                },
-                "receiver": {
-                  "id": "receiver-id"
-                }
-              },
-              "creator": {
-                "id": "creator-id"
-              }
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "get_transactions",
-      "summary": "Retrieve a list of transactions.",
-      "description": "Query a list of transactions by SEP, transaction status or other criteria.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "sep",
-          "summary": "Sep of the transaction.",
-          "description": "Sep of the transaction belongs to",
-          "required": true,
-          "schema": {
-            "title": "sep",
-            "description": "Protocol of the transaction.",
-            "type": "integer",
-            "enum": [
-              6,
-              24,
-              31
-            ]
-          }
-        },
-        {
-          "name": "order_by",
-          "summary": "The field that transactions will be ordered by .",
-          "description": "Specifies field that transactions will be ordered by. Note, that secondary sort is transaction id in ascending value.",
-          "required": false,
-          "schema": {
-            "title": "order_by",
-            "description": "The order by string used to sort the results.",
-            "type": "string",
-            "enum": [
-              "created_at",
-              "transfer_received_at",
-              "user_action_required_by"
-            ],
-            "default": "created_at"
-          }
-        },
-        {
-          "name": "statuses",
-          "summary": "The statuses of transactions.",
-          "description": "The statuses of the transaction to filter by.",
-          "required": false,
-          "schema": {
-            "title": "status",
-            "description": "The statuses of the transaction to filter by.",
-            "type": "array",
-            "enum": [
-              "incomplete",
-              "completed",
-              "refunded",
-              "expired",
-              "error",
-              "pending_stellar",
-              "pending_external",
-              "pending_user_transfer_start",
-              "pending_user_transfer_complete",
-              "pending_anchor",
-              "pending_trust",
-              "pending_user",
-              "no_market",
-              "too_small",
-              "too_large",
-              "pending_sender",
-              "pending_receiver",
-              "pending_transaction_info_update",
-              "pending_customer_info_update"
-            ]
-          }
-        },
-        {
-          "name": "page_size",
-          "summary": "The number of transactions to return.",
-          "description": "The number of records to return in each page.",
-          "required": false,
-          "schema": {
-            "title": "page_size",
-            "description": "The number of records to return in each page.",
-            "type": "integer",
-            "default": 20
-          }
-        },
-        {
-          "name": "page_number",
-          "summary": "The page number of transactions to return.",
-          "description": "Page number to use for continuous search. Page count beings at 0.",
-          "required": false,
-          "schema": {
-            "title": "page_number",
-            "description": "Page number to use for continuous search. Page count beings at 0.",
-            "type": "integer",
-            "default": 0
-          }
-        }
-      ],
-      "result": {
-        "name": "get_transactionResponse",
-        "schema": {
-          "type": "object",
-          "properties": {
-            "records": {
-              "type": "array",
-              "items": {
-                "title": "Platform Transaction",
-                "description": "A platform transaction object",
-                "type": "object",
-                "properties": {
-                  "id": {
-                    "title": "transaction_id",
-                    "description": "A unique transaction identifier.",
-                    "type": "string"
-                  },
-                  "sep": {
-                    "title": "sep",
-                    "description": "Protocol of the transaction.",
-                    "type": "integer",
-                    "enum": [
-                      6,
-                      24,
-                      31
-                    ]
-                  },
-                  "kind": {
-                    "title": "kind",
-                    "description": "The kind of transaction that is desired.",
-                    "type": "string",
-                    "enum": [
-                      "undefined",
-                      "receive",
-                      "deposit",
-                      "deposit-exchange",
-                      "withdrawal",
-                      "withdrawal-exchange"
-                    ]
-                  },
-                  "status": {
-                    "title": "status",
-                    "description": "Processing status of the transaction.",
-                    "type": "string",
-                    "enum": [
-                      "pending_anchor",
-                      "pending_trust",
-                      "pending_user",
-                      "pending_user_transfer_start",
-                      "pending_user_transfer_complete",
-                      "incomplete",
-                      "no_market",
-                      "too_small",
-                      "too_large",
-                      "pending_sender",
-                      "pending_receiver",
-                      "pending_transaction_info_update",
-                      "pending_customer_info_update",
-                      "completed",
-                      "refunded",
-                      "expired",
-                      "error",
-                      "pending_external",
-                      "pending_stellar"
-                    ]
-                  },
-                  "funding_method": {
-                    "description": "Funding method used for transferring or settling assets.",
-                    "type": "string"
-                  },
-                  "type": {
-                    "description": "DEPRECATED in favor of funding_method. Type of deposit, withdrawal or receive.",
-                    "type": "string"
-                  },
-                  "amount_expected": {
-                    "type": "object",
-                    "title": "amount_expected",
-                    "description": "The amount expected in the payment.",
-                    "properties": {
-                      "amount": {
-                        "title": "amount",
-                        "description": "A stringified amount of an asset.",
-                        "type": "string"
-                      },
-                      "asset": {
-                        "title": "asset",
-                        "description": "An asset.",
-                        "type": "string"
-                      }
-                    }
-                  },
-                  "amount_in": {
-                    "type": "object",
-                    "title": "amount_in",
-                    "description": "Amount expected/received by anchor.",
-                    "properties": {
-                      "amount": {
-                        "title": "amount",
-                        "description": "A stringified amount of an asset.",
-                        "type": "string"
-                      },
-                      "asset": {
-                        "title": "asset",
-                        "description": "An asset.",
-                        "type": "string"
-                      }
-                    }
-                  },
-                  "amount_out": {
-                    "type": "object",
-                    "title": "amount_out",
-                    "description": "The amount expected to be sent by anchor to user at end of transaction.",
-                    "properties": {
-                      "amount": {
-                        "title": "amount",
-                        "description": "A stringified amount of an asset.",
-                        "type": "string"
-                      },
-                      "asset": {
-                        "title": "asset",
-                        "description": "An asset.",
-                        "type": "string"
-                      }
-                    }
-                  },
-                  "fee_details": {
-                    "title": "fee_details",
-                    "description": "Description of fee charged by the anchor.",
-                    "type": "object",
-                    "required": [
-                      "total",
-                      "asset"
-                    ],
-                    "properties": {
-                      "total": {
-                        "type": "number"
-                      },
-                      "asset": {
-                        "type": "string"
-                      },
-                      "details": {
-                        "type": "array",
-                        "description": "Details about fee charged.",
-                        "items": {
-                          "properties": {
-                            "name": {
-                              "type": "string"
-                            },
-                            "description": {
-                              "type": "string"
-                            },
-                            "amount": {
-                              "type": "number"
-                            }
-                          }
-                        }
-                      }
-                    }
-                  },
-                  "quote_id": {
-                    "title": "quote_id",
-                    "description": "The id returned from a SEP-38 POST /quote response",
-                    "type": "string"
-                  },
-                  "started_at": {
-                    "title": "started_at",
-                    "description": "Start date and time of transaction.",
-                    "type": "string"
-                  },
-                  "updated_at": {
-                    "title": "updated_at",
-                    "description": "The date and time of transaction reaching the current status.",
-                    "type": "string"
-                  },
-                  "completed_at": {
-                    "title": "completed_at",
-                    "description": "The date and time of transaction reaching completed or refunded status.",
-                    "type": "string"
-                  },
-                  "transfer_received_at": {
-                    "title": "transfer_received_at",
-                    "description": "The date and time of receiving transfer.",
-                    "type": "string"
-                  },
-                  "user_action_required_by": {
-                    "title": "user_action_required_by",
-                    "description": "Time and date by which user action is required.",
-                    "type": "string"
-                  },
-                  "message": {
-                    "title": "message",
-                    "description": "Human readable explanation of transaction status",
-                    "type": "string"
-                  },
-                  "refunds": {
-                    "title": "refunds",
-                    "description": "An object describing any on or offchain refund associated with this transaction.",
-                    "type": "object",
-                    "properties": {
-                      "amount_refunded": {
-                        "type": "object",
-                        "description": "The total amount refunded in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "amount_fee": {
-                        "type": "object",
-                        "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "payments": {
-                        "type": "array",
-                        "description": "A list of objects containing information on the individual payments made back as refunds.",
-                        "items": {
-                          "properties": {
-                            "id": {
-                              "title": "id",
-                              "description": "The Stellar transaction hash.",
-                              "type": "string"
-                            },
-                            "id_type": {
-                              "type": "string"
-                            },
-                            "amount": {
-                              "type": "object",
-                              "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                              "properties": {
-                                "amount": {
-                                  "title": "amount",
-                                  "description": "A numerical representation of an amount of some asset.",
-                                  "type": "string"
-                                },
-                                "asset": {
-                                  "title": "asset",
-                                  "description": "An asset.",
-                                  "type": "string"
-                                }
-                              }
-                            },
-                            "fee": {
-                              "type": "object",
-                              "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                              "properties": {
-                                "amount": {
-                                  "title": "amount",
-                                  "description": "A numerical representation of an amount of some asset.",
-                                  "type": "string"
-                                },
-                                "asset": {
-                                  "title": "asset",
-                                  "description": "An asset.",
-                                  "type": "string"
-                                }
-                              }
-                            },
-                            "requested_at": {
-                              "title": "datetime",
-                              "description": "The date and time of requesting refund.",
-                              "type": "string"
-                            },
-                            "refunded_at": {
-                              "title": "datetime",
-                              "description": "The date and time of making refund.",
-                              "type": "string"
-                            }
-                          }
-                        }
-                      }
-                    }
-                  },
-                  "stellar_transactions": {
-                    "type": "array",
-                    "items": {
-                      "title": "stellar_transaction",
-                      "type": "object",
-                      "required": [
-                        "id",
-                        "created_at",
-                        "envelope",
-                        "payments"
-                      ],
-                      "properties": {
-                        "id": {
-                          "title": "hash",
-                          "description": "The Stellar transaction hash.",
-                          "type": "string"
-                        },
-                        "memo": {
-                          "title": "memo",
-                          "type": "string"
-                        },
-                        "memo_type": {
-                          "title": "memo_type",
-                          "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-                          "type": "string",
-                          "enum": [
-                            "id",
-                            "hash",
-                            "text"
-                          ]
-                        },
-                        "created_at": {
-                          "title": "created_at",
-                          "description": "The date and time when the transaction is created.",
-                          "type": "string"
-                        },
-                        "envelop": {
-                          "description": "The transaction envelope, containing all the transaction information.",
-                          "type": "string"
-                        },
-                        "payments": {
-                          "type": "array",
-                          "items": {
-                            "required": [
-                              "id",
-                              "payment_type",
-                              "source_account",
-                              "destination_account",
-                              "amount"
-                            ],
-                            "properties": {
-                              "id": {
-                                "description": " The ID of the payment in the Stellar Network.",
-                                "type": "string"
-                              },
-                              "payment_type": {
-                                "description": " The ID of the payment in the Stellar Network.",
-                                "type": "string",
-                                "enum": [
-                                  "payment",
-                                  "path_payment"
-                                ],
-                                "default": "payment"
-                              },
-                              "source_account": {
-                                "title": "source_account",
-                                "description": "The account being debited in the Stellar Network.",
-                                "type": "string"
-                              },
-                              "destination_account": {
-                                "title": "destination_account",
-                                "description": "The account being credited in the Stellar Network.",
-                                "type": "string"
-                              },
-                              "amount": {
-                                "type": "object",
-                                "properties": {
-                                  "amount": {
-                                    "title": "amount",
-                                    "description": "A stringified amount of an asset.",
-                                    "type": "string"
-                                  },
-                                  "asset": {
-                                    "title": "asset",
-                                    "description": "An asset.",
-                                    "type": "string"
-                                  }
-                                }
-                              }
-                            }
-                          }
-                        }
-                      }
-                    }
-                  },
-                  "source_account": {
-                    "title": "source_account",
-                    "description": "The account being debited in the Stellar Network.",
-                    "type": "string"
-                  },
-                  "destination_account": {
-                    "title": "destination_account",
-                    "description": "The account being credited in the Stellar Network.",
-                    "type": "string"
-                  },
-                  "external_transaction_id": {
-                    "title": "transaction_id",
-                    "description": "A unique transaction identifier.",
-                    "type": "string"
-                  },
-                  "memo": {
-                    "title": "memo",
-                    "type": "string"
-                  },
-                  "memo_type": {
-                    "title": "memo_type",
-                    "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-                    "type": "string",
-                    "enum": [
-                      "id",
-                      "hash",
-                      "text"
-                    ]
-                  },
-                  "refund_memo": {
-                    "title": "memo",
-                    "type": "string"
-                  },
-                  "refund_memo_type": {
-                    "title": "memo_type",
-                    "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-                    "type": "string",
-                    "enum": [
-                      "id",
-                      "hash",
-                      "text"
-                    ]
-                  },
-                  "client_domain": {
-                    "description": "The domain of the client.",
-                    "type": "string"
-                  },
-                  "client_name": {
-                    "description": "The domain of the client.",
-                    "type": "string"
-                  },
-                  "customers": {
-                    "description": "The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\n            this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.",
-                    "type": "object",
-                    "properties": {
-                      "sender": {
-                        "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                        "type": "object",
-                        "properties": {
-                          "id": {
-                            "type": "string",
-                            "description": "The `id` of the customer registered through SEP-12."
-                          },
-                          "account": {
-                            "type": "string",
-                            "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                          },
-                          "memo": {
-                            "type": "string",
-                            "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                          }
-                        }
-                      },
-                      "receiver": {
-                        "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                        "type": "object",
-                        "properties": {
-                          "id": {
-                            "type": "string",
-                            "description": "The `id` of the customer registered through SEP-12."
-                          },
-                          "account": {
-                            "type": "string",
-                            "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                          },
-                          "memo": {
-                            "type": "string",
-                            "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                          }
-                        }
-                      }
-                    }
-                  },
-                  "creator": {
-                    "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                    "type": "object",
-                    "properties": {
-                      "id": {
-                        "type": "string",
-                        "description": "The `id` of the customer registered through SEP-12."
-                      },
-                      "account": {
-                        "type": "string",
-                        "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                      },
-                      "memo": {
-                        "type": "string",
-                        "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "get_transactionsExample",
-          "description": "Example request to the `get_transactions` method.",
-          "params": [
-            {
-              "name": "sep",
-              "value": "31"
-            },
-            {
-              "name": "order_by",
-              "value": "created_at"
-            },
-            {
-              "name": "statuses",
-              "value": [
-                "completed"
-              ]
-            }
-          ],
-          "result": {
-            "name": "platformTransactionResponses",
-            "value": {
-              "records": [
-                {
-                  "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-                  "sep": "31",
-                  "kind": "receive",
-                  "status": "completed",
-                  "funding_method": "SWIFT",
-                  "amount_expected": {
-                    "amount": "100",
-                    "asset": "iso4217:USD"
-                  },
-                  "amount_in": {
-                    "amount": "100.0000",
-                    "asset": "iso4217:USD"
-                  },
-                  "amount_out": {
-                    "amount": "98.0000000",
-                    "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                  },
-                  "fee_details": {
-                    "total": "2.0000",
-                    "asset": "iso4217:USD"
-                  },
-                  "quote_id": "quote-id",
-                  "message": "Please don't forget to foo bar",
-                  "refunds": {
-                    "amount_refunded": {
-                      "amount": "90.0000",
-                      "asset": "iso4217:USD"
-                    },
-                    "amount_fee": {
-                      "amount": "8.0000",
-                      "asset": "iso4217:USD"
-                    },
-                    "payments": [
-                      {
-                        "id": "1111",
-                        "id_type": "stellar",
-                        "amount": {
-                          "amount": "50.0000",
-                          "asset": "iso4217:USD"
-                        },
-                        "fee": {
-                          "amount": "4.0000",
-                          "asset": "iso4217:USD"
-                        }
-                      },
-                      {
-                        "id": "2222",
-                        "id_type": "stellar",
-                        "amount": {
-                          "amount": "40.0000",
-                          "asset": "iso4217:USD"
-                        },
-                        "fee": {
-                          "amount": "4.0000",
-                          "asset": "iso4217:USD"
-                        }
-                      }
-                    ]
-                  },
-                  "stellar_transactions": [
-                    {
-                      "id": "stellar-tx-id",
-                      "memo": "my-memo",
-                      "memo_type": "text",
-                      "envelope": "here_comes_the_envelope",
-                      "payments": [
-                        {
-                          "id": "payment-id",
-                          "amount": {
-                            "amount": "100.0000",
-                            "asset": "iso4217:USD"
-                          },
-                          "payment_type": "payment",
-                          "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-                          "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-                        }
-                      ]
-                    }
-                  ],
-                  "external_transaction_id": "external-tx-id",
-                  "customers": {
-                    "sender": {
-                      "id": "sender-id"
-                    },
-                    "receiver": {
-                      "id": "receiver-id"
-                    }
-                  },
-                  "creator": {
-                    "id": "creator-id"
-                  }
-                }
-              ]
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_amounts_updated",
-      "summary": "Update transaction amounts",
-      "description": "Update amount_out and fee_details values",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_amounts_updatedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_amounts_updatedExample",
-          "description": "Example request to the `notify_amounts_updated` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Amounts updated"
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 1
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_customer_info_updated",
-      "summary": "Customer info updated",
-      "description": "The customer's status for the transaction has been updated. Use this method to notify the wallet of the status change. If `customer_id` and `customer_type` are provided, the transaction status will reflect the customer's status. If not, the transaction status will default to the standard pending status for the SEP.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "customer_id",
-          "description": "The SEP-12 ID of the customer",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        },
-        {
-          "name": "customer_type",
-          "description": "The SEP-12 type of the customer",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_customer_info_updatedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_customer_info_updatedExample",
-          "description": "Example request to the `notify_customer_info_updated` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Customer info updated"
-            },
-            {
-              "name": "customer_id",
-              "value": "45f8884d-d6e1-477f-a680-503179263359"
-            },
-            {
-              "name": "customer_type",
-              "value": "sep31-receiver"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_interactive_flow_completed",
-      "summary": "Interactive flow completed",
-      "description": "Platform has collected the transaction amounts and fees from the business",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_expected",
-          "description": "The amount expected in the payment",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_interactive_flow_completedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_interactive_flow_completedExample",
-          "description": "Example request to the `notify_interactive_flow_completed` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Interactive flow completed successfully."
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 0.9,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "amount_expected",
-              "value": {
-                "amount": 1
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_offchain_funds_available",
-      "summary": "Offchain funds are available",
-      "description": "Funds are ready for the user / recipient to pick up.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "external_transaction_id",
-          "summary": "ID of the transaction on external network",
-          "description": "The unique identifier of this transaction on the external network.",
-          "required": false,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_offchain_funds_availableResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_offchain_funds_availableExample",
-          "description": "Example request to the `notify_offchain_funds_available` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Offchain funds available"
-            },
-            {
-              "name": "stellar_transaction_id",
-              "value": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_offchain_funds_pending",
-      "summary": "Offchain funds pending",
-      "description": "Payment has been submitted to external network, but is not yet confirmed",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "external_transaction_id",
-          "summary": "ID of the transaction on external network",
-          "description": "The unique identifier of this transaction on the external network.",
-          "required": false,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_offchain_funds_pendingResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_offchain_funds_pendingExample",
-          "description": "Example request to the `notify_offchain_funds_pending` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Offchain funds pending"
-            },
-            {
-              "name": "external_transaction_id",
-              "value": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_offchain_funds_received",
-      "summary": "Offchain funds received",
-      "description": "Payment is being processed internally by anchor",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "funds_received_at",
-          "description": "The date and time of receiving funds.",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "external_transaction_id",
-          "summary": "ID of the transaction on external network",
-          "description": "The unique identifier of this transaction on the external network.",
-          "required": false,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_offchain_funds_receivedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_offchain_funds_receivedExample",
-          "description": "Example request to the `notify_offchain_funds_received` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Funds received successfully"
-            },
-            {
-              "name": "funds_received_at",
-              "value": "2023-07-04T12:34:56Z"
-            },
-            {
-              "name": "external_transaction_id",
-              "value": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1
-              }
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 0.9
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "amount_expected",
-              "value": {
-                "amount": 1
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_offchain_funds_sent",
-      "summary": "Offchain funds sent",
-      "description": "Transaction flow is fully completed for the SEP-6 and SEP-24 withdrawal flow or SEP-31 receive flow. Payment has been submitted to external network, but is not yet confirmed for SEP-24 deposit flow",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "funds_sent_at",
-          "description": "The date and time of sending funds.",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "external_transaction_id",
-          "summary": "ID of the transaction on external network",
-          "description": "The unique identifier of this transaction on the external network.",
-          "required": false,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_offchain_funds_sentResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_offchain_funds_sentExample",
-          "description": "Example request to the `notify_offchain_funds_sent` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Offchain funds sent"
-            },
-            {
-              "name": "funds_sent_at",
-              "value": "2023-07-04T12:34:38Z"
-            },
-            {
-              "name": "external_transaction_id",
-              "value": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_onchain_funds_received",
-      "summary": "Onchain funds received",
-      "description": "Notify that the payment is being processed internally by anchor for SEP-6 or SEP-24. For SEP-31, notify that the payment is being processed by the Receiving Anchor. In the request, amount parameters are optional, but have a strict rule of how to set them. Either none, only `amount_in`, or all of fields (`amount_in`, `amount_out`, `fee_details`) must be specified. ",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "stellar_transaction_id",
-          "summary": "Transaction ID on Stellar",
-          "description": "The unique transaction identifier for this transfer on the Stellar network.",
-          "required": true,
-          "schema": {
-            "title": "hash",
-            "description": "The Stellar transaction hash.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_onchain_funds_receivedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_onchain_funds_receivedExample",
-          "description": "Example request to the `notify_onchain_funds_received` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Onchain funds received"
-            },
-            {
-              "name": "stellar_transaction_id",
-              "value": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_onchain_funds_sent",
-      "summary": "Onchain funds sent",
-      "description": "Transaction flow is fully completed for SEP-6 or SEP-24 deposit",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "stellar_transaction_id",
-          "summary": "Transaction ID on Stellar",
-          "description": "The unique transaction identifier for this transfer on the Stellar network.",
-          "required": true,
-          "schema": {
-            "title": "hash",
-            "description": "The Stellar transaction hash.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_onchain_funds_sentResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_onchain_funds_sentExample",
-          "description": "Example request to the `notify_onchain_funds_sent` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Onchain funds sent"
-            },
-            {
-              "name": "stellar_transaction_id",
-              "value": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_refund_pending",
-      "summary": "Refund pending",
-      "description": "Refund has been submitted, but is not yet confirmed",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "refund",
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "amount_fee",
-              "id"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "Amount to be refunded",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "Amount of assets to refund",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of refund",
-                    "type": "string"
-                  }
-                }
-              },
-              "amount_fee": {
-                "title": "amount_fee",
-                "description": "Amount of fee",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "The amount of fee",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of fee charged by anchor",
-                    "type": "string"
-                  }
-                }
-              },
-              "id": {
-                "title": "id",
-                "description": "The Stellar transaction hash.",
-                "type": "string"
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_refund_pendingResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_refund_pendingExample",
-          "description": "Example request to the `notify_refund_pending` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Refund pending"
-            },
-            {
-              "name": "refund",
-              "value": {
-                "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
-                "amount": {
-                  "amount": 1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                },
-                "amount_fee": {
-                  "amount": 0.1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                }
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_refund_sent",
-      "summary": "Payment refunded",
-      "description": "Refund payment completed",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "refund",
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "amount_fee",
-              "id"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "Amount to be refunded",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "Amount of assets to refund",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of refund",
-                    "type": "string"
-                  }
-                }
-              },
-              "amount_fee": {
-                "title": "amount_fee",
-                "description": "Amount of fee",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "The amount of fee",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of fee charged by anchor",
-                    "type": "string"
-                  }
-                }
-              },
-              "id": {
-                "title": "id",
-                "description": "The Stellar transaction hash.",
-                "type": "string"
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_refund_sentResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_refund_sentExample",
-          "description": "Example request to the `notify_refund_sent` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Refund sent"
-            },
-            {
-              "name": "refund",
-              "value": {
-                "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
-                "amount": {
-                  "amount": 1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                },
-                "amount_fee": {
-                  "amount": 0.1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                }
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_transaction_error",
-      "summary": "Transaction processing error",
-      "description": "There was an error processing transaction",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_transaction_errorResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_transaction_errorExample",
-          "description": "Example request to the `notify_transaction_error` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Transaction error"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_transaction_expired",
-      "summary": "Transaction has expired",
-      "description": "Funds were never received by the anchor and the transaction is considered abandoned by the user",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_transaction_expiredResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_transaction_expiredExample",
-          "description": "Example request to the `notify_transaction_expired` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Transaction expired"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_transaction_on_hold",
-      "summary": "Transaction transaction is on hold",
-      "description": "Notify transaction is currently on hold by the anchor (e.g. compliance hold). Anchor should update message to guide user through the steps.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_transaction_on_holdResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_transaction_on_holdExample",
-          "description": "Example request to the `notify_transaction_on_hold` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Transaction on hold, please contact customer service to lift the hold."
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_transaction_recovery ",
-      "summary": "Transaction recovery",
-      "description": "Transaction status is changed from error / expired to pending_anchor(SEP-6 or SEP-24) or pending_receiver(SEP-31)",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_transaction_recoveryResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_transaction_recoveryExample",
-          "description": "Example request to the `notify_transaction_recovery` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Transaction recovered"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_trust_set",
-      "summary": "Asset trustline set",
-      "description": "The user has added a trustline for the asset",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "success",
-          "description": "Flag which indicates if trustline was configured by user.",
-          "required": false,
-          "schema": {
-            "type": "boolean"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_trust_setResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_trust_setExample",
-          "description": "Example request to the `notify_trust_set` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Trustline set"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "request_offchain_funds",
-      "summary": "Request offchain funds",
-      "description": "The user has to initiate transfer to the anchor",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "This is required if the transaction is associated with a firm quote and for transactions where `amount_in.asset` and `amount_out.asset` are the same.",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_expected",
-          "description": "The amount expected in the payment",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "instructions",
-          "description": "A set of SEP-9 fields that describe how the user can complete the offchain deposit",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "additionalProperties": {
-              "type": "object",
-              "properties": {
-                "name": {
-                  "type": "string",
-                  "description": "The SEP-9 field name"
-                },
-                "field": {
-                  "type": "object",
-                  "properties": {
-                    "value": {
-                      "type": "string",
-                      "description": "The value of the field"
-                    },
-                    "description": {
-                      "type": "string",
-                      "description": "A human readable description of the field"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "request_offchain_fundsResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "request_offchain_fundsExample",
-          "description": "Example request to the `request_offchain_funds` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Request offchain funds"
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 0.9,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "amount_expected",
-              "value": {
-                "amount": 1
-              }
-            },
-            {
-              "name": "instructions",
-              "value": {
-                "organization.bank_number": {
-                  "value": "123456789",
-                  "description": "US Bank routing number"
-                },
-                "organization.bank_account_number": {
-                  "value": "123456789",
-                  "description": "US Bank account number"
-                }
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "request_onchain_funds",
-      "summary": "Request onchain funds",
-      "description": "The user has to initiate transfer to the anchor",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "This is required if the transaction is associated with a firm quote and for transactions where `amount_in.asset` and `amount_out.asset` are the same.",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_expected",
-          "description": "The amount expected in the payment",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "destination_account",
-          "description": "Destination account",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        },
-        {
-          "name": "memo",
-          "description": "Value of memo to attach to transaction",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        },
-        {
-          "name": "memo_type",
-          "description": "Type of memo that anchor should attach to the transaction",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "request_onchain_fundsResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "request_onchain_fundsExample",
-          "description": "Example request to the `request_onchain_funds` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Requesting onchain funds"
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 0.9,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "amount_expected",
-              "value": {
-                "amount": 1
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "request_trust",
-      "summary": "A trustline to the asset isn't set",
-      "description": "The user must add a trustline for the asset to complete",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "request_trustResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "request_trustExample",
-          "description": "Example request to the `request_trust` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Request trust"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    }
-  ],
-  "components": {}
-}
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/README.mdx
deleted file mode 100644
index eb23be31d9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/README.mdx
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Métodos JSON-RPC
-order: 20
-sidebar_label: Métodos
----
-
-import { EndpointsTable } from "@site/src/components/EndpointsTable";
-
-Esta sección enumera los métodos de la API JSON-RPC de Anchor Platform que deben ser llamados por los clientes de Stellar para actualizar el estado de la transacción.
-
-La Especificación OpenRPC para la API JSON-RPC está disponible [aquí](https://playground.open-rpc.org/?schemaUrl=https://raw.githubusercontent.com/stellar/stellar-docs/main/static/assets/rpc-methods/open-rpc.json).
-
-La colección de Postman está disponible [aquí](https://documenter.getpostman.com/view/9257637/2s9Y5U1kra)
-
-<EndpointsTable title="Métodos JSON-RPC">
-
-|   |                                                                                       |
-| - | ------------------------------------------------------------------------------------- |
-|   | [hacer_pago_estelar](./do_stellar_payment.mdx)                                        |
-|   | [hacer_reembolso_estelar](./do_stellar_refund.mdx)                                    |
-|   | [obtener_transacción](./get_transaction.mdx)                                          |
-|   | [obtener_transacciones](./get_transactions.mdx)                                       |
-|   | [notificar_cantidades_actualizadas](./notify_amounts_updated.mdx)                     |
-|   | [notificar_información_cliente_actualizada](./notify_customer_info_updated.mdx)       |
-|   | [notificar_flujo_interactivo_completado](./notify_interactive_flow_completed.mdx)     |
-|   | [notificar_fondos_fuera_de_cadena_disponibles](./notify_offchain_funds_available.mdx) |
-|   | [notificar_fondos_fuera_de_cadena_pendientes](./notify_offchain_funds_pending.mdx)    |
-|   | [notificar_fondos_fuera_de_cadena_recibidos](./notify_offchain_funds_received.mdx)    |
-|   | [notificar_fondos_fuera_de_cadena_enviados](./notify_offchain_funds_sent.mdx)         |
-|   | [notificar_fondos_en_cadena_recibidos](./notify_onchain_funds_received.mdx)           |
-|   | [notificar_fondos_en_cadena_enviados](./notify_onchain_funds_sent.mdx)                |
-|   | [notificar_reembolso_pendiente](./notify_refund_pending.mdx)                          |
-|   | [notificar_reembolso_enviado](./notify_refund_sent.mdx)                               |
-|   | [notificar_error_transacción](./notify_transaction_error.mdx)                         |
-|   | [notificar_transacción_expirada](./notify_transaction_expired.mdx)                    |
-|   | [notificar_transacción_en_espera](./notify_transaction_on_hold.mdx)                   |
-|   | [notificar_recuperación_transacción](./notify_transaction_recovery.mdx)               |
-|   | [notificar_configuración_confianza](./notify_trust_set.mdx)                           |
-|   | [solicitar_fondos_fuera_de_cadena](./request_offchain_funds.mdx)                      |
-|   | [solicitar_fondos_en_cadena](./request_onchain_funds.mdx)                             |
-|   | [solicitar_confianza](./request_trust.mdx)                                            |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/do_stellar_payment.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/do_stellar_payment.mdx
deleted file mode 100644
index 42f491e60f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/do_stellar_payment.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: realizar_pago_stellar
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "realizar_pago_stellar")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/do_stellar_refund.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/do_stellar_refund.mdx
deleted file mode 100644
index 901173359a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/do_stellar_refund.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: realizar_reembolso_stellar
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "realizar_reembolso_stellar")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/get_transaction.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/get_transaction.mdx
deleted file mode 100644
index 9682b1bd97..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/get_transaction.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: obtener_transacción
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "obtener_transacción")[0]}
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/get_transactions.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/get_transactions.mdx
deleted file mode 100644
index 26dab85735..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/get_transactions.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: obtener_transacciones
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "obtener_transacciones")[0]}
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_amounts_updated.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
deleted file mode 100644
index 4f46e02eef..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: notificar_actualización_de_montos
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notificar_actualización_de_montos")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
deleted file mode 100644
index 45836a5f59..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_info_cliente_actualizada
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_info_cliente_actualizada",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
deleted file mode 100644
index 817a113664..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar flujo interactivo completado
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar flujo interactivo completado",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
deleted file mode 100644
index 35ed445bc2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_fuera_de_la_cadena_disponibles
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_fondos_fuera_de_la_cadena_disponibles",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
deleted file mode 100644
index aba869c587..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_fuera_de_línea_pendientes
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_fondos_fuera_de_línea_pendientes",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
deleted file mode 100644
index 291add5e3f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_fuera_de_la_cadena_recibidos
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_fondos_fuera_de_la_cadena_recibidos",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
deleted file mode 100644
index 39ca9284f4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_fuera_de_la_cadena_enviados
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_fondos_fuera_de_la_cadena_enviados",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
deleted file mode 100644
index df99ba449a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_onchain_recibidos
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_fondos_onchain_recibidos",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
deleted file mode 100644
index c80f0df8e1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_en_cadena_enviados
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_fondos_en_cadena_enviados",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_refund_pending.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_refund_pending.mdx
deleted file mode 100644
index 0d29e75064..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_refund_pending.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: notificar_reembolso_pendiente
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notificar_reembolso_pendiente")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_refund_sent.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_refund_sent.mdx
deleted file mode 100644
index 78e56bd450..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_refund_sent.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: notificar_reembolso_enviado
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notificar_reembolso_enviado")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_error.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_error.mdx
deleted file mode 100644
index d7bc13aaf4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_error.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_error_transacción
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_error_transacción",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_expired.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
deleted file mode 100644
index 119e4aece7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_transacción_expirada
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_transacción_expirada",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
deleted file mode 100644
index 430ed01d9c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_transacción_en_espera
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_transacción_en_espera",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
deleted file mode 100644
index 000198f5dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_recuperación_transacción
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notificar_recuperación_transacción",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_trust_set.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_trust_set.mdx
deleted file mode 100644
index 0fae83910c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/notify_trust_set.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: notificar_confiar_establecer
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "notificar_confiar_establecer")[0]}
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_offchain_funds.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_offchain_funds.mdx
deleted file mode 100644
index 2550832461..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_offchain_funds.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: solicitar_fondos_fuera_de_la_cadena
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "solicitar_fondos_fuera_de_la_cadena")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_onchain_funds.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_onchain_funds.mdx
deleted file mode 100644
index ec9dd3ef90..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_onchain_funds.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: solicitar_fondos_en_cadena
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "solicitar_fondos_en_cadena")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_trust.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_trust.mdx
deleted file mode 100644
index fce561c8a2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/methods/request_trust.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: solicitar_confianza
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "solicitar_confianza")[0]}
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/overview.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/overview.mdx
deleted file mode 100644
index ae54187559..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/rpc/overview.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Descripción general
-sidebar_position: 10
----
-
-JSON-RPC es un protocolo de llamada a procedimiento remoto (RPC) sin estado y ligero.
-
-Es simple y fácil de usar, ya que utiliza un único endpoint HTTP y un objeto JSON que contiene el nombre del método y los parámetros. Es agnóstico al transporte en el sentido de que los conceptos pueden usarse dentro del mismo proceso, a través de sockets, sobre http, o en muchos diversos entornos de paso de mensajes. Utiliza [JSON](http://www.json.org/) ([RFC 4627](http://www.ietf.org/rfc/rfc4627.txt)) como formato de datos.
-
-:::note
-
-Todos los nombres de los miembros intercambiados entre el Cliente y el Servidor que se consideran para la coincidencia de cualquier tipo deben considerarse sensibles a mayúsculas y minúsculas.
-
-:::
-
-Puedes leer más sobre el protocolo JSON-RPC [aquí](https://www.jsonrpc.org/specification).
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/README.mdx
deleted file mode 100644
index 7f0afc844e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Transacciones
-sidebar_position: 10
----
-
-import { EndpointsTable } from "@site/src/components/EndpointsTable";
-
-Las transacciones son representaciones de una transacción SEP. Contiene información sobre el protocolo que se está utilizando, y toda la información necesaria proporcionada por una parte externa (como una billetera o un anchor).
-
-No debe confundirse con las [transacciones](/docs/learn/glossary#transaction) de stellar.
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                               |
-| ------- | --------------------------------------------- |
-| OBTENER | [/transacciones/:id](get-transaction.api.mdx) |
-| OBTENER | [/transacciones/](./get-transactions.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/get-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/get-transaction.api.mdx
deleted file mode 100644
index 3b8158bd32..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/get-transaction.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: get-transaction
-title: "Retrieve a Transaction"
-description: "Provides the information necessary for the business to determine the state of the transaction identified by `id`, decide if any action must be taken to continue processing the transaction, and act on the decision."
-sidebar_label: "Retrieve a Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXN1P67gS/1csv+yuFFLgoPPQN/Yuu6q0HwjOfeKgHjeeNF4SO8d2KBXq/341ttOmbQotQqLnyi+Qxh8zHs+HZ36tn6llU0OHd/SLZtKwzAolDb1P6NOJgdq13F5dn3ymift/fhEePp1hJ1WDZjhkxOmQTsF2ZqEJ5WAyLWr3aUivtXoUHAyxBRAhc6UrN5ZIyMAYpuckV9q1ThojJBhDrCIcLOhKSHAtxjILROXug11RI4KDtCIXwMlkTr4J/i0hHDLBgYicMDknoWPVGEsmQCx7AIkEMiWtkA2QWitkRMjp5uwJYZLjBERJ14YzG6FkShNaM80qZBKl9UwFrrVmtqAJlawCOqSC04Rq+N4IDZwOrW4goSYroGJ0+EztvMZexmohp3SxuMfOplbSgMH289NT/LcuzY6kSa4ayZEVXApIi71ZXZcicwIe/GtwyHOHpJLwT+7YDcTV5F/I7Bqbd55vAzVN6IOQ7oNltjH+QVvgY2ZRD2qNmmCF51fwnlX5ibbeJxRkUyGxz/R+Eei80ItDrYywTrnc0wk8ZQWTU6AJnQlbcM1mrFz7sOqCFMISemhsqKsyRkxKr3KNIY+sbMBpqDOIrnqYDoNCZqqqS7Dg9sM/+v3PG8ndIzzVTsQJBa2VRh0CyYWcjo2FsmTdN/BkQUu3ovZV1hirKtBjNKJxU3PmiLXNjQE9dtzloMduo3a2dnhtOzCZFWs8Wd2YzRlQt9W4YvoBsMkqNTYVK8vwXDKN0k6oFbZEGd86Gd5eXX9GTfCCf20DvhRAKrCF4s7kkCz+4d4puM0nSpN2n4nK86xgQhKUs0mREKtUI+0YnmrIcBeGL+u7704TyoyBHsUO7X3K7Uf0GPNKBpd+9IotIY+MIdXYY+EoBxhzsEyU5jWWrLLOPHZw5JsPYQgVcZMy05rNaUKFhepVjpzbb6W6zZGPCn0M7Rbemmm8JMLfAX7r9F1stfmVLRL6vVEWxruc9cq/9xiqj910SNH1nFhRAY7xnuiwMUsPedCopf/SkIF4PJRPdIHec4/bbRtP5vtPUOFxZdq/h97N96pIn6WMl2HhSAwvsJUDHAtHNZtXIO1B1rjXgUTw8a5I1EbzVTxexuH7PkP9aF95LKwgTTCHmnNrAwcMWqw5tptgdM5xuR0brx3P3ujH3fk309B6NdSLRyhV7c5LrVrudf7tO9yMfutNZHyGcevXQSTYmdIPqfc7ldr33FSpN0y+0x52UMBuB5Aht4VqSo7ZV63BgLSYm7mZhCFSWSKbskw79mfhCcVeMIPplODO+jo7sp+29PGPDVt8z5ghGqbCWNDAX5LWUhH2ElaXRjsycYknExLzTVaWPUJcpsjpW/3gljaHSfxGJ9SoRmcwZlkW/AMHY4V0RDtvd51kDtf0QH9TtH93RLvG4n7iDWr42uQrvQo9nUBsMW4/3uPsOWtK63J4/3KxJaa9mAqdyQRwgzlMhN1Wqe66+0T/BkqZBv4aqWOKX+uePHDbrSMt9tiAfcW3WAXyboTYdQrud7jH7CyJ4MR5y07y/RdU6gvyuAy14/0iySjHmhgW7XhCbCGMJ2+WjLl0HEsiftq1mki6Qe6HFFdWCnRFXFVM9CVeyx47c7q2WNPrnreX7qoctmDoxIQVGOe2JWDIRNnC10NBctCuPBlyIZ1+lVsnYN/tdRaCVEf8J0OYBuK7mcCRL7HOCUh+gowaR9eXg8mtLw+RS1c/MgmZNNbJPbTfOPY6PdKv8qv8XWnCXJezc9LKKnFLwxouyQWUvKNxpslzkaHIsQyUN2U5X/GFo9o5Wj1pS8k/kV9Z9gCSb5Dd4jwQDy7km1viN9SjwIzZ0P+N+T6TUCE8v3j7hHtlMH3q42QWjGYpic6JxhZaNdMiCNzHgn1DzZWwBeg142sjj9Lkr+YJ+PIF41xj/T6wouSJL83hRtn5Ww6zvvzabrU7M61WiDVAwogpmF4xkZBZATrABmstaEHL/UhpT/wZce+9vEVFu4l2E+1mX7tZtCmaioYTDScazv6Gs3rbyX8CaPZmpHYTA9uV478/ont+cSCk28Fv3w+pPb/4QKj2qLHY84tDwFhhgm8UhrByxuaGQFXb+S5BRwA2ArARgI0AbARgIwAbAdgIwEYANgKwEYCNAGwEYI8sfkUA9gMB2HcFXJNtOUUANgKwsR4e6+E/Yj08ArDRbqLdRAA2Gk40nI8FYB1S9mYE9v2RVfz19R7Iagif7wimfjr7QDA1nKFXL5bHgy5A2skpe38e2/vr2T549NPZu8KjG6KL8GiERyM8GuHRCI9GeDTCoxEejfBohEcjPBrh0QiPHln8ivDo0cCjIsKjHw2PjsI1e/5mORcDWiGYUFRdQaHO3Nv5UzJy/eZkhjW6ECSX9ck7X6C8/7mwtjbDwSAclFKlp4NaK6syVQ4M1Cdn578kX6Xbfs9oqwAhXnnxr9eXXZk0Jf9gPXMmDGxVaNerl+2wiOTGwnosrEckN9pNtJuI5EbDiYbzoxjOLiQXQb17n9Jd9F2r/Cvj5MYXCQ+5T/nl+q5HO/tLvP1JaDfN9aM7CcCVe9Eu4mJ7Ed27odGKD78f+oPWE9JfaXxV9O6ZPsCcDtvLyBPqNOnFS8nx9mx/a7C/kTyUUOiQDrrZ4OBZ8IVD7PVje3N3o0s6pG3+UZfMYoHrxHdJ4YkhFOR/kptmqqJIChMgXDJO4oX/KT1NT+lqdddhHnLr5um1kpYW8bQchozJla8EEAShlARpUzKyHY9TKBMKKYzUWjzi1egh33SeKvREFZi4MgwEbD/XqnK2NXIkwKbEIdiBPEg2KcNF7d2r2HOwWeFm9lCaN8/ljewd8ZLGXaMurCGX1yPvFUuRgTSwQhjpZc2yAsi5k9dK+sPBYDabpcy1uvwvDDWDP0f/ufr79urkPD1NC1uVTrlqZWzFZGfiG7BawCMQRl64kf55ZQ//t5fTB1PEWgJqtJAOYNQOcPZ2cUc3vtExxDJ2QlG5sPX5ecIM/FeXiwW+/t6AntPh3T0aoxaoKM54uDD4zOkwZ6WBF0T9801wBr+QXQy25WM5X9k8xW/WOG8gOPrwhBbAXCa+dBOXWQa17QzZcnJr3uGPqy90sfgfaB/iSg==
-sidebar_class_name: "get api-method"
-info_path: platforms/anchor-platform/api-reference/platform/transactions/platform-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Provides the information necessary for the business to determine the state of the transaction identified by `id`, decide if any action must be taken to continue processing the transaction, and act on the decision.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"path","name":"id","required":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Transaction found.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["6"]},"kind":{"type":"string","enum":["deposit","deposit-exchange","withdrawal","withdrawal-exchange"]},"status":{"type":"string","description":"Possible status value for SEP-6 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_customer_info_update","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP6"},"type":{"type":"string","description":"The method the user used to deposit or withdraw offchain funds."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"type":"string","description":"If provided, this memo should be used for refund transactions."},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP6"},{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"},{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}]}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Transaction not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/get-transactions.api.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/get-transactions.api.mdx
deleted file mode 100644
index aaefea43a9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/get-transactions.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: get-transactions
-title: "Retrieve a List of Transactions"
-description: "Allows to query list of transactions for desired SEP. This api supports pagination, and it's possible (and recommended) to make multiple requests to query transactions. The last page is reached when the number of elements returned by the endpoint is smaller than provided `page_size`."
-sidebar_label: "Retrieve a List of Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXVtv47YS/isEX7oLKEo2G/TBb+lpehAg3Qab7dNu4NDS2GIjkSpJ5dLA//1ghpQt2bJjp4smPeDLxqZIznCu5Hxe8Yk7MbN89JV/MUJZkTmpleXXCX84sFDTk6uzy4MfeUJ/j0/Ch48fsJOuwQgccp7zEZ+B682S8BxsZmSNX/mIn5alvrfMafZnA+aRldI6pqfMdQaxqTYsBysN5Ozq7DJlXwppmagls01da+Msq8VMKiKbMKFyJt0PltXaWjkpgb3DJgOZripQOeTvkWAlboFVTelkXQIz8GcD1nVY6bKAJIGVwjqkBExaZkBkBeTsvgDFXAFMNdUEDDIPJVSgHPZxjVGQs8kjdQGV11oqh+NtJcoSDHOFUKw2+k7mkLMbnH5s5V9wk/KE18KIChwYlPoTlygy4o4nXIkK+IhbqHnCkX2UDx8500DCbVZAJfjoibvHmro5I9WMJxxUU6EKUX2kOlTbfFUvF1rfNnVfDRMotZpJNUMZOVQBKoPPk2HGtMnBjCfY8jw3mQHhIB8LxxNOVKdgxgYykHdtc2PBjD0z43a9OP81Mj8VTen4qDvR2qKuasjkVIJlUwlljqJ3/SXey7JkE2DEO+ktZZ+0g8T3tZBplQvzyKw2pMXOaCZzJhUTNgOVo5TuRNlA+k2dp5AGM5EVWCeq2tv0MdOGVdpAnwlpmcxBOZmJEgnD44IvJOvNSebPSH4nsQubBZfsSxHbt4iPCPQks/ACL1lpmWrKMmGiLFcl7Ap65sWzWBn6VsIMzITJS7AW/chqZNdTY+8+/X5xccUuTq++vE+/qV+0YfAgqrpEFoLBkIBZJR6Z0o7kFVjOSd5WV31RI0GLEUDNmFROs5sh07thE8AeyHXKzpGvZGhRWh0sF2ZXdeZDUIgHU2lwuVON4c8rdIuklmazWefWCddYsENqF8YI7CodVHbIHPp6vmzDpp+zXQ9KcJXJjilJlWnUhgOe8PZjTqFp2mDQxb4PNQWphIMxGk209r4ytg7KUnRb4MGBUaLsNFEAWGjIOmHcxqcdZtoOQmVFj6gzjV2dASWqx5Uwt0ChSOsxRerwuRRm1p3TYj7pzhnspk9mIbCxVFM9bupc9DjLGut0Bab3+DrhTroSFXVFirg6uzwtSz5fc8xfZIkpYj1pLs2fTIB8KtgJGTJ6SZt6EjalacgXLMulFZMScvYuRAU2gULcSW3eb7TBRe4aMkKpHMxILoswc3y0HmPkX4BsCmalmqENgjBZQVk3Zb82lty61lY6eQeb3YFY8Rl5R2bWebnETB+yutOssUBCzbRyUjW6sYG5lFHPTDfK+VBhmXDsKOXzazR/W2uFnjl64sdHR/inT6ezQWJT3ag8JQ9SDpTD3qKuS5nR5ubwD4tDnjor0gp+m9LuIKxNT/6AjMza4F7MSU8atz8mtzuEhcUEy03FVy7Ra/1e41Yq+kKW5D+YkHKvV6nKfD3ezP1EW/cmuCMhOlt65UB2QEqkTwfwkBVCkYNi9MyNuKcAsvyy7IIUwhJeFhHJGGgj/IohcTByvMGIORTMfkRL8IJ/TgG4+67AFTqnTQaSxX9y9MugfNxLtXpmejrNCiEVQzlT1uSiQv8cw0MNGWrhGXv33XnChbUwYNjh+ZBx+xHrT+ZLGZz60Uu2pHpjDOnGvRWOpgDjHJyQ5bNRymlH7rGBI/94H4bQEFcp7xU3KR+1Ul3nyKerIYY2C6/nGttE+AvAz52+87VnfmXzhP/ZaAfjTcF6Gd8HHHWqTYVPOIaeA9yq4hgfifYbs4iQe40aPCzuzueGM+XOE1RgrZgN69CH+UETGfKU8SItvBHHC2xNAd4KR7V4pMrKPt6404ZE5uNNmajN5st8vMjD10OO+tqx8q2wEipqezpk6wN7DJr3Atvn4HQUuEhj49727O/sf3tVKlB3UOqa9kutWe60/x3a3Jz/TFXPAvoVJV9TufLrYArcvTa3qY87ld5131TpF0y+0R82UMBue5BhV4VuypxOcwYsYFF06mfC4pF2vtzS8T8HDyj2QtgClZaT93U0spu1DPFPVaNVvu8F1m9n0jqqBG6R1sIQdhJWl0Y7MqFDpZAKD99UY1kTol+K1Cp9aRxcs+YwiVd0wq1uTAZjkWUhPuRgXSiqd1o37WT2t/RAf1W0nzqi7bG4m3iDGT43+dKuQk8SiCvG7ddePbRtnK+JaSemQudQR8xhIt26SXXXPST6F1DKDOTPkXpL+asfyQO3nfIIDXpOAbuKb75M5P0S3fAOYTjgvuVgiYAERcvO4ftXqPQX5HGRase7ZZLzaadSSOAPkbcLxug4jiURP20fPlsh968UV1ZKDEW5roQcOngtemw807XFmsHwvL50qnIQuiKVdBLz3LoELJtoV1C7r0UHoMFXodNvam0HHErWz7IQpHqe/2CZMMB8Nxs4IoBq+oiQ5gEyaomuh4HZVUDATql+ZBM2aRzJPTz/TOx1eqTflId0BHX5cMxaWREAxm5kfhOgpaXF2WY6lRmKHMtA06YsH5d84ah2jtZOJo2VCqz9gf0ksltQ+QrZNc4D8RBCbmiJN2hHgRm7Yv8r8/3IQoXw+OTlE+50ghkyH5JZcJqFJDo7GlcY3cyKIHCfC3ZNNWfSFWScS+drM4827NfmASGH0CDy3ARAD/trdeBLc6go9/iSzawvv7aqpj3TcoUEmwlmC2GWTCQIUBq/yes/QQ9a6CPlA/nnPPfRK+A60W+i30S/2dFv5u0RTUfHiY4THWd3x1m2ds4/HjTb8PBCWhdQtdfDgldRtk1VhO+PGR+f7AkadxDi74cFH5/E38cMo73HJ/vAvdIuf0kmynvxaBlUtXvcJOgI8UaIN0K8EeKNEG+EeCPEGyHeCPFGiDdCvBHijRDvG8tfEeJ9RYj3u0K6ybqcIsQbId5YcY8V939jxT1CvNFvot9EiDc6TnSc14V4ESnbjvESlvZ6IO/3B2/DO0ieA29Dhv6OeO3HD6+I1/7DLw/4+OG7IrAroosIbERgIwIbEdiIwEYENiKwEYGNCGxEYCMCGxHYiMC+sfwVEdg3g8DKiMC+NgJ77it+4f16lANaIdhQt12ireTu7fz0BkX/dlYsA4YkuSiBfvU10Ot3hXO1HR0eho1Sqs3ssDba6UyXhxbqgw/H75NvitTvGW0NIOQrL/5+CZsqsSn7DUum99LCWhG4XyBth0WwONbuY+0+gsXRb6LfRLA4Ok50nH+L42wCixHU2w4WY49rf+g7GXr99E8iZ599GXGf905vrwB7PHS4CDx8TO0ehP3ozhHhjBraRZysL6L7Dm308/3fo/1K6wkHZGV93fTrE7+FRz5q71pJONna1jtX8C3j/uXI/sKVUGThI364gm1bMHftXSKNKfmIt4eTuhQOq18Hvksarlbw/yU4zXRF7zLH0xGuFifxcv+YHqVHfLmwyzAPu6J5Bl2opcU8LQKY8eTlywQMESqtQLmUnbtOOCq0DVUWwWoj74SD9jBKYSz0DDc/iCyDAPxPja7I8c6JBLhwgUwgDwpfdG97AZriObisoJk9zuZ91+Gn1QtqcNSMSWfZ6eW5D5mlzEBZWMKP/LTGC2PYMclrKf3R4eH9/X0q6CkdDsNQe3hx/p+zT1dnB8fpUVq4yr/6v9bWVUJ1Jv4Mzki4AybYRbg+Z9udO09Ln4jX72y/fid4NRYu0EOkIjTTELrtXewr77nYdcLRTLH96WkiLPxuyvkcm/39BOh47c0KfDQVpYUt2nn3OcSQ92yP+3g2sO3Div9BT4gpnH5FtDs//2/352yVVOf6or8trnhfzqvdl/O8jl+u4H/63pXtnr28AOil9rrn3Stb2eneBfNCfv7+/SvPc7i4ImbJ4zV+MRKZ5KOviH8WIKhCuticnWYZ1K4zam1r2duT/ffsC5/P/weQ8/fV
-sidebar_class_name: "get api-method"
-info_path: platforms/anchor-platform/api-reference/platform/transactions/platform-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a List of Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows to query list of transactions for desired SEP. This api supports pagination, and it's possible (and recommended) to make multiple requests to query transactions. The last page is reached when the number of elements returned by the endpoint is smaller than provided `page_size`.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"query","name":"sep","required":true,"schema":{"type":"string","enum":["6","24","31"]},"description":"Lookup transactions belonging to this SEP."},{"in":"query","name":"order_by","schema":{"type":"string","enum":["created_at","transfer_received_at","user_action_required_by"],"default":"created_at"},"description":"Specifies field that transactions will be ordered by. Note, that secondary sort is transaction id in ascending value.\nI.e. when timestamps for 2 or more transactions is identical, they will be sorted by id."},{"in":"query","name":"order","schema":{"type":"string","enum":["asc","desc"],"default":"asc"},"description":"Specifies order. Note, that when the field is null, all transactions with null value will be last, regardless of soring order (NULLS LAST).\nFor example, transfer time may not be specified for some transactions, resulting into `transfer_received_at` being null. If so, transactions with non-null values will be sorted and returned first, followed by all transactions with null timestamps."},{"in":"query","name":"statuses","schema":{"type":"array","items":{"type":"string","description":"Possible status values for all transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEPAll"}},"description":"Filters transactions for specified array of statuses. If not provided, filtering is disabled (default behavior)"},{"in":"query","name":"page_size","schema":{"type":"integer","default":20},"description":"Size of a single search page. Must be positive."},{"in":"query","name":"page_number","schema":{"type":"integer","default":0},"description":"Page number to use for continuous search. Page count beings at 0."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Transaction found.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["6"]},"kind":{"type":"string","enum":["deposit","deposit-exchange","withdrawal","withdrawal-exchange"]},"status":{"type":"string","description":"Possible status value for SEP-6 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_customer_info_update","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP6"},"type":{"type":"string","description":"The method the user used to deposit or withdraw offchain funds."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"type":"string","description":"If provided, this memo should be used for refund transactions."},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP6"}}},"title":"TransactionListSEP6"},{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"}}},"title":"TransactionListSEP24"},{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}}},"title":"TransactionListSEP31"}]}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Transaction not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/versions.json b/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/versions.json
deleted file mode 100644
index 15ec16df99..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/api-reference/platform/transactions/versions.json
+++ /dev/null
@@ -1,12 +0,0 @@
-[
-  {
-    "version": "3.0.0",
-    "label": "v3.0.0",
-    "baseUrl": "/platforms/anchor-platform/next/api-reference/platform/transactions"
-  },
-  {
-    "version": "2.8.4",
-    "label": "v2.8.4",
-    "baseUrl": "/platforms/anchor-platform/api-reference/platform/transactions"
-  }
-]
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/SEP24-state-diagram.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/SEP24-state-diagram.png
deleted file mode 100644
index 65d2bb5363..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/SEP24-state-diagram.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-architecture-1.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-architecture-1.png
deleted file mode 100644
index 7aeec4523b..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-architecture-1.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-architecture-2.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-architecture-2.png
deleted file mode 100644
index c22e2122dd..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-architecture-2.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep24-demo-wallet-widget.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep24-demo-wallet-widget.png
deleted file mode 100644
index b2461d306e..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep24-demo-wallet-widget.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep24-demo-wallet.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep24-demo-wallet.png
deleted file mode 100644
index 169f450fa3..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep24-demo-wallet.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep31-demo-wallet-widget.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep31-demo-wallet-widget.png
deleted file mode 100644
index be483f58c9..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/anchor-platform-sep31-demo-wallet-widget.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep24-deposit-flow-diagram.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep24-deposit-flow-diagram.png
deleted file mode 100644
index 6d6baab26a..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep24-deposit-flow-diagram.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep24-withdrawal-flow-diagram.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep24-withdrawal-flow-diagram.png
deleted file mode 100644
index f69ee06dad..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep24-withdrawal-flow-diagram.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep31-transition-diagram.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep31-transition-diagram.png
deleted file mode 100644
index a04c0a28ea..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep31-transition-diagram.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep6-deposit-flow-diagram.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep6-deposit-flow-diagram.png
deleted file mode 100644
index 9036aeee0e..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep6-deposit-flow-diagram.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep6-withdrawal-flow-diagram.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep6-withdrawal-flow-diagram.png
deleted file mode 100644
index 187b871aac..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sep6-withdrawal-flow-diagram.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_deposit_job.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_deposit_job.png
deleted file mode 100644
index 30b8059f85..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_deposit_job.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_deposit_webhook.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_deposit_webhook.png
deleted file mode 100644
index 630d9173d0..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_deposit_webhook.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_withdrawal_job.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_withdrawal_job.png
deleted file mode 100644
index a768c5218f..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_withdrawal_job.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_withdrawal_webhook.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_withdrawal_webhook.png
deleted file mode 100644
index 4005a81d27..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep24_withdrawal_webhook.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep31_receive_job.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep31_receive_job.png
deleted file mode 100644
index 3150663fe1..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep31_receive_job.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep31_receive_webhook.png b/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep31_receive_webhook.png
deleted file mode 100644
index 7a66bbdcc9..0000000000
Binary files a/i18n/es/docusaurus-plugin-content-docs-ap/current/assets/sequence_diagram_sep31_receive_webhook.png and /dev/null differ
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/README.mdx
deleted file mode 100644
index 03ce6c8a55..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Guías SEP
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Guías para implementar Propuestas del Ecosistema Stellar (SEPs) con la Plataforma Anchor.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/_category_.json b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/_category_.json
deleted file mode 100644
index aa65b42d31..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/_category_.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
-  "label": "SEP Guides",
-  "collapsed": false
-}
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep1/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep1/README.mdx
deleted file mode 100644
index 156cde4358..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep1/README.mdx
+++ /dev/null
@@ -1,200 +0,0 @@
----
-title: Archivo de información Stellar (SEP-1)
-sidebar_position: 50
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Resumen
-
-SEP-1 (Archivo de información de Stellar) permite que las carteras y otras aplicaciones de Stellar descubran información sobre tu servicio ancla. Al alojar un archivo `stellar.toml` en `/.well-known/stellar.toml`, permites que las aplicaciones encuentren automáticamente:
-
-- La información de tu organización
-- Los activos y monedas compatibles
-- Puntos finales de autenticación (SEP-10)
-- Puntos finales SEP para SEP-6, SEP-24, SEP-31, SEP-38, SEP-45
-
-Para más detalles, por favor consulta la [especificación SEP-1][sep-1].
-
-## Crear tu archivo stellar.toml
-
-Crea un archivo `stellar.toml` con la información de tu servicio. Aquí tienes un ejemplo mínimo para comenzar:
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["GD...G"]  # Your distribution account public keys
-SIGNING_KEY = "GD...G"  # Your signing key (public key) for SEP-10 authentication
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"  # Use "Public Global Stellar Network ; September 2015" for mainnet
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "https://your-website.com"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-:::tip
-
-Para una lista completa de todos los atributos disponibles de `stellar.toml`, consulta la [especificación SEP-1][sep-1]. Necesitarás añadir secciones adicionales como `[[CURRENCIES]]`, `TRANSFER_SERVER`, `TRANSFER_SERVER_SEP0024`, `WEB_AUTH_ENDPOINT`, `WEB_AUTH_FOR_CONTRACTS_ENDPOINT`, `DIRECT_PAYMENT_SERVER`, etc., a medida que configures los activos compatibles y otros SEPs.
-
-:::
-
-:::important
-
-**Producción vs. Desarrollo**: Necesitarás archivos `stellar.toml` separados para testnet y mainnet:
-
-- **Testnet**: Usa `NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"`
-- **Mainnet**: Usa `NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"`
-
-Asegúrate de que tu archivo de producción incluya tus cuentas reales de distribución en Mainnet, llaves de firma y URLs del servicio en producción.
-
-:::
-
-## Configuración
-
-Para habilitar SEP-1, necesitas configurar cómo la Plataforma Anchor debe acceder a tu archivo `stellar.toml`. La plataforma soporta tres métodos:
-
-| Tipo     | Caso de uso                                  | Descripción                                                     |
-| -------- | -------------------------------------------- | --------------------------------------------------------------- |
-| `file`   | **Recomendado para la mayoría de los casos** | Leer desde un archivo local en el servidor                      |
-| `string` | Pruebas rápidas o configuraciones simples    | Proporcionar el contenido TOML directamente en la configuración |
-| `url`    | Alojamiento externo                          | Obtener desde una URL remota (útil para contenido dinámico)     |
-
-### Variables de entrono
-
-Configura SEP-1 usando las siguientes variables de entorno:
-
-- `SEP1_ENABLED`: Ponlo en `true` para habilitar SEP-1
-- `SEP1_TOML_TYPE`: Uno de `file`, `string` o `url`
-- `SEP1_TOML_VALUE`: El valor depende del tipo (ver ejemplos abajo)
-
-### Método 1: Archivo (Recomendado)
-
-Ideal para: Implementaciones en producción donde gestionas el archivo en disco.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/path/to/your/stellar.toml
-```
-
-</CodeExample>
-
-:::tip
-
-Al usar Docker, monta tu archivo `stellar.toml` como un volumen y referencia la ruta dentro del contenedor. Por ejemplo:
-
-```yaml
-# docker-compose.yaml
-volumes:
-  - ./config/stellar.toml:/config/stellar.toml:ro
-```
-
-Luego, establece `SEP1_TOML_VALUE=/config/stellar.toml` en tu entorno.
-
-:::
-
-### Método 2: Cadena (String)
-
-Ideal para: Pruebas rápidas, desarrollo o cuando gestionas la configuración vía variables de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=string
-SEP1_TOML_VALUE="ACCOUNTS = [\"GD...G\"]
-SIGNING_KEY = \"GD...G\"
-NETWORK_PASSPHRASE = \"Test SDF Network ; September 2015\"
-[DOCUMENTATION]
-ORG_NAME = \"Your organization\"
-ORG_URL = \"https://your-website.com\""
-```
-
-</CodeExample>
-
-:::caution
-
-Al usar el tipo `string`, asegúrate de que el contenido TOML está correctamente escapado para el formato de tu archivo de entorno. Para configuraciones complejas, es más fácil manejar el tipo `file`.
-
-:::
-
-### Método 3: URL
-
-Ideal para: Contenido dinámico o cuando se aloja el archivo externamente.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=url
-SEP1_TOML_VALUE=https://example.com/stellar.toml
-```
-
-</CodeExample>
-
-:::note
-
-Al usar el tipo `url`, la Plataforma Anchor obtendrá el archivo en cada solicitud. Asegúrate de que la URL sea accesible desde tu servidor de Plataforma Anchor y que retorne contenido TOML válido.
-
-:::
-
-## Accediendo a tu archivo stellar.toml
-
-Una vez configurado y habilitado, la Plataforma Anchor sirve automáticamente tu archivo `stellar.toml` en el punto final estándar SEP-1:
-
-- **`/.well-known/stellar.toml`** - Punto final principal (servido con `Content-Type: text/plain`)
-- **`/`** - Redirige a `/.well-known/stellar.toml` cuando SEP-1 está habilitado
-
-### Probando tu configuración
-
-Después de iniciar la Plataforma Anchor, verifica tu configuración:
-
-```bash
-# Test the endpoint
-curl http://localhost:8080/.well-known/stellar.toml
-
-# Or test the redirect
-curl -L http://localhost:8080/
-```
-
-Deberías ver el contenido de tu `stellar.toml` devuelto como texto plano.
-
-### Alternativa: Alojamiento externo
-
-También puedes alojar tu archivo `stellar.toml` usando un servidor de archivos estático como [nginx] o un CDN. Si eliges este enfoque:
-
-1. Aloja el archivo en `https://tu-dominio.com/.well-known/stellar.toml`
-2. Asegúrate de que sea accesible públicamente
-3. Verifica que tu archivo `stellar.toml` incluya las URLs correctas que apunten a los puntos finales de tu Plataforma Anchor
-
-El servicio SEP-1 de la Plataforma Anchor es opcional si alojas el archivo externamente, pero proporciona una manera conveniente de gestionar todo en un solo lugar.
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep10/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep10/README.mdx
deleted file mode 100644
index d8ba052cff..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep10/README.mdx
+++ /dev/null
@@ -1,293 +0,0 @@
----
-title: Autenticación Stellar (SEP-10)
-sidebar_position: 60
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Resumen
-
-SEP-10 (Stellar Web Authentication) permite que las aplicaciones de billetera creen sesiones autenticadas con los anchors de Stellar al demostrar el control sobre una cuenta Stellar. Una vez autenticadas, las billeteras reciben un JSON Web Token (JWT) que usan en solicitudes posteriores a los servicios estandarizados del anchor.
-
-Para la especificación completa, consulta [SEP-0010: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md).
-
-La Plataforma Anchor implementa SEP-10 con soporte para:
-
-- **Flujo Challenge/Response**: GET `/auth` para solicitar un desafío, POST `/auth` para validar y recibir un JWT
-- **Atribución del Cliente**: Verificación opcional de la identidad de la aplicación cliente para billeteras no custodiales
-- **Soporte para Billeteras Custodiales**: Soporte para billeteras custodiales que gestionan cuentas de usuario
-- **Múltiples Dominios Home**: Soporte para múltiples dominios y patrones comodín
-
-## Flujo Típico de Autenticación
-
-1. El **Cliente** solicita un desafío único al **Servidor**
-2. El **Cliente** verifica y firma el desafío
-3. El **Cliente** envía el desafío firmado al **Servidor**
-4. El **Servidor** verifica el desafío y responde con un token de sesión JWT
-
-## Habilitar SEP-10
-
-Para habilitar SEP-10, configura las siguientes variables de entorno en tu archivo `dev.env`.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP10_ENABLED=true
-SEP10_HOME_DOMAINS=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret encryption key"
-```
-
-</CodeExample>
-
-### Configuración Requerida (Si está habilitado)
-
-| Variable                    | Valor predeterminado | Descripción                                                                                                                                                                                                    |
-| --------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SEP10_ENABLED`             | `false`              | Establece en `true` para habilitar la autenticación SEP-10                                                                                                                                                     |
-| `SEP10_HOME_DOMAINS`        | `localhost:8080`     | Lista de dominios home (separados por comas). Soporta patrones comodín como `*.stellar.org`. El `home_domain` debe coincidir con el host donde se sirve tu archivo `stellar.toml`.                             |
-| `SECRET_SEP10_SIGNING_SEED` | _Requerido_          | La clave privada correspondiente a la `SIGNING_KEY` en tu archivo `stellar.toml`. Se usa para firmar los desafíos de autenticación. Las billeteras verifican esta firma antes de firmar y devolver el desafío. |
-| `SECRET_SEP10_JWT_SECRET`   | _Requerido_          | La clave de cifrado utilizada para firmar y verificar los tokens JWT emitidos a billeteras autenticadas.                                                                                                       |
-
-:::important
-
-La `SIGNING_KEY` en tu archivo `stellar.toml` debe ser la clave pública derivada de `SECRET_SEP10_SIGNING_SEED`. Las billeteras verificarán que las transacciones de desafío están firmadas con esta clave.
-
-:::
-
-### Configuración Opcional
-
-<CodeExample>
-
-```bash
-# dev.env
-# Optional: Specify web_auth_domain (default: first home_domain if only one is specified)
-SEP10_WEB_AUTH_DOMAIN=localhost:8080
-
-# Optional: Challenge transaction timeout in seconds (default: 900)
-SEP10_AUTH_TIMEOUT=900
-
-# Optional: JWT token timeout in seconds (default: 86400 = 24 hours)
-SEP10_JWT_TIMEOUT=86400
-
-# Optional: Require Authorization header in GET /auth requests (default: false)
-SEP10_REQUIRE_AUTH_HEADER=false
-
-# Optional: Client attribution requirement (default: false)
-SEP10_CLIENT_ATTRIBUTION_REQUIRED=false
-
-# Optional: Client allow list (default: empty, all configured clients allowed)
-# Comma-separated list of client names that are allowed to authenticate
-SEP10_CLIENT_ALLOW_LIST=client1,client2
-```
-
-</CodeExample>
-
-| Variable                            | Valor predeterminado                                                  | Descripción                                                                                                                                                                                                                                                             |
-| ----------------------------------- | --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SEP10_WEB_AUTH_DOMAIN`             | Primer `home_domain` si se especifica solo uno, de lo contrario vacío | La propiedad `web_auth_domain` usada en las respuestas SEP-10. Requerido si tienes múltiples `home_domains` o usas patrones comodín. Debe coincidir con el host del servidor SEP.                                                                                       |
-| `SEP10_AUTH_TIMEOUT`                | `900`                                                                 | Tiempo en segundos que una transacción de desafío permanece válida. Los clientes deben firmar y enviar el desafío dentro de esta ventana.                                                                                                                               |
-| `SEP10_JWT_TIMEOUT`                 | `86400`                                                               | Tiempo en segundos que un token JWT emitido permanece válido. Después de la expiración, los clientes deben volver a autenticarse.                                                                                                                                       |
-| `SEP10_REQUIRE_AUTH_HEADER`         | `false`                                                               | Si es `true`, requiere un encabezado de Autorización válido (Bearer JWT) en las solicitudes GET `/auth` de desafío. Esto previene el acceso no autorizado al endpoint y es útil para flujos de re-autenticación donde los clientes necesitan actualizar sus tokens JWT. |
-| `SEP10_CLIENT_ATTRIBUTION_REQUIRED` | `false`                                                               | Si es `true`, las billeteras no custodiales deben proporcionar un `client_domain` en las solicitudes de desafío. Requiere configuración del cliente (ver abajo).                                                                                                        |
-| `SEP10_CLIENT_ALLOW_LIST`           | Vacío (todos los clientes configurados permitidos)                    | Lista separada por comas con los nombres de clientes permitidos para autenticarse. Solo relevante cuando `SEP10_CLIENT_ATTRIBUTION_REQUIRED=true`. Si está vacía, todos los clientes configurados están permitidos.                                                     |
-
-:::tip
-
-**Múltiples Dominios Home**: Si especificas múltiples `home_domains` (p. ej., `ap.stellar.org,*.sdp.stellar.org`), también debes establecer `SEP10_WEB_AUTH_DOMAIN` para especificar qué dominio aloja el endpoint de autenticación.
-
-:::
-
-## Atribución del Cliente
-
-La atribución del cliente te permite restringir la autenticación a aplicaciones de billetera específicas y verificar su identidad. Esta es una función opcional que sólo debe habilitarse si es un requisito empresarial.
-
-:::info
-
-Por defecto, la Plataforma Anchor permite que cualquiera con una cuenta Stellar pueda autenticarse. La atribución del cliente solo es necesaria si quieres:
-
-- Restringir la autenticación a aplicaciones de billetera específicas
-- Verificar la identidad de aplicaciones de billetera no custodiales
-- Registrar qué aplicaciones de billetera usan tus usuarios
-
-:::
-
-### Habilitar la Atribución del Cliente
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP10_CLIENT_ATTRIBUTION_REQUIRED=true
-```
-
-</CodeExample>
-
-Cuando `SEP10_CLIENT_ATTRIBUTION_REQUIRED=true`, las billeteras no custodiales deben:
-
-1. Proporcionar un parámetro `client_domain` en la solicitud de desafío
-2. Firmar la transacción de desafío con la `SIGNING_KEY` del archivo `stellar.toml` de ese dominio
-3. Tener su dominio listado en tu configuración de clientes
-
-### Configuración del Cliente
-
-Configura los clientes permitidos en tu archivo de configuración YAML:
-
-<CodeExample>
-
-```yaml
-clients:
-  # Each item in the list may contain the following fields:
-  #   - name: (required) the name of the client
-  #   - type: (required) `custodial` or `noncustodial`
-  #
-  #   If the type is `custodial`,
-  #   - signing_keys: (required) the custodial SEP-10 signing key(s) of the client.
-  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
-  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
-  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
-  #   - callback_urls.sep12: (optional) the URL of the client's SEP-12 callback API endpoint.
-  #   - allow_any_destination: (optional) default to false. If set to true, allows any destination for deposits.
-  #   - destination_accounts: (optional) list of accounts allowed to be used for the deposit.
-  #                           If allow_any_destination is set to true, this configuration option is ignored.
-  #
-  #   If the type is `noncustodial`,
-  #   - domains: (required) the domains of the client.
-  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
-  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
-  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
-  #   - callback_urls.sep12: (optional) the URL of the client's SEP-12 callback API endpoint.
-
-  # custodial client
-  - name: bluecorp
-    type: custodial
-    signing_keys: "the signing key 1 of bluecorp","the signing key 2 of bluecorp"
-    callback_urls:
-      sep6: https://callback.bluecorp.com/api/v1/anchor/callback/sep6
-      sep12: https://callback.bluecorp.com/api/v1/anchor/callback/sep12
-    allow_any_destination: false
-    destination_accounts: GA...
-
-  # noncustodial client
-  - name: pinkcorp
-    type: noncustodial
-    domains: pinkcorp.com
-    callback_urls:
-      sep6: https://callback.pinkcorp.com/api/v2/anchor/callback/sep6
-      sep12: https://callback.pinkcorp.com/api/v2/anchor/callback/sep12
-
- - name: redcorp
-    type: custodial
-    signing_keys: "the signing key of redcorp",
-
-```
-
-</CodeExample>
-
-O configura mediante variables de entorno:
-
-<CodeExample>
-
-```bash
-# dev.env
-# custodial client
-CLIENTS[0]_NAME=bluecorp
-CLIENTS[0]_TYPE=custodial
-CLIENTS[0]_SIGNING_KEYS="the signing key 1 of bluecorp","the signing key 2 of bluecorp"
-CLIENTS[0]_ALLOW_ANY_DESTINATION=false
-CLIENTS[0]_DESTINATION_ACCOUNTS=GA...
-
-# noncustodial client
-CLIENTS[1]_NAME=pinkcorp
-CLIENTS[1]_TYPE=noncustodial
-CLIENTS[1]_DOMAINS=pinkcorp.com
-
-# custodial client
-CLIENTS[2]_NAME=redcorp
-CLIENTS[2]_TYPE=custodial
-CLIENTS[2]_SIGNING_KEYS="the signing key of redcorp"
-```
-
-</CodeExample>
-
-## Configurar stellar.toml
-
-Actualiza tu archivo `stellar.toml` para anunciar soporte SEP-10. Las billeteras descubren tu endpoint de autenticación mediante este archivo.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-SIGNING_KEY = "add your signing key here (public key from SECRET_SEP10_SIGNING_SEED)"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-```
-
-</CodeExample>
-
-Estos campos deben coincidir con las opciones de configuración definidas en la sección [Habilitar SEP-10](#enable-sep-10) arriba.
-
-`WEB_AUTH_ENDPOINT` - La URL donde se ejecuta el servicio de autenticación. Esta es la URL que los clientes usarán para autenticarse con el anchor. El endpoint debe soportar:
-
-- `GET <WEB_AUTH_ENDPOINT>` - Solicitar un desafío
-- `POST <WEB_AUTH_ENDPOINT>` - Intercambiar desafío firmado por un JWT de sesión
-
-`SIGNING_KEY` - La clave pública correspondiente a la clave privada especificada en `SECRET_SEP10_SIGNING_SEED`. Esta clave se usa para firmar los desafíos de autenticación presentados a las aplicaciones de billetera.
-
-:::important
-
-- **`SIGNING_KEY`**: Debe ser la clave pública derivada de `SECRET_SEP10_SIGNING_SEED`
-- **`WEB_AUTH_ENDPOINT`**: Usa `https://` en producción. La ruta `/auth` es el endpoint estándar SEP-10.
-- **Coincidencia de Host**: El host en `WEB_AUTH_ENDPOINT` debe coincidir con uno de tus `SEP10_HOME_DOMAINS` (o el `SEP10_WEB_AUTH_DOMAIN` si está especificado).
-
-:::
-
-## Cómo Probar el Flujo de Autenticación
-
-El flujo de autenticación SEP-10 consta de dos pasos:
-
-1. **GET `/auth`** - Solicitar una transacción desafío
-   - Parámetros: `account` (requerido), `memo` (opcional), `home_domain` (opcional), `client_domain` (opcional)
-   - Retorna: Una transacción desafío en formato XDR
-
-2. **POST `/auth`** - Validar el desafío firmado y recibir un JWT
-   - Cuerpo: `{ "transaction": "<signed_challenge_xdr>" }`
-   - Retorna: `{ "token": "<jwt_token>" }`
-
-El token JWT debe incluirse en las solicitudes API subsecuentes como token Bearer en el encabezado `Authorization`.
-
-:::tip
-
-**Probando tu Configuración**: Puedes probar la autenticación SEP-10 usando curl y Stellar CLI. Para más información sobre Stellar CLI, consulta la [documentación de Stellar CLI](https://developers.stellar.org/docs/tools/cli).
-
-```bash
-# Verify if `stellar` command line is installed
-stellar --version
-
-# List your Stellar keys/identities
-stellar keys ls
-
-# Get your account ID (public key) and secret seed
-# Replace 'alice' with your identity name from `stellar keys ls`
-IDENTITY_NAME="alice"
-ACCOUNT_ID=$(stellar keys public-key "$IDENTITY_NAME")
-SECRET_SEED=$(stellar keys secret "$IDENTITY_NAME")
-
-# Step 1: Request challenge and save the transaction XDR
-CHALLENGE_RESPONSE=$(curl -s "http://localhost:8080/auth?account=$ACCOUNT_ID")
-CHALLENGE_XDR=$(echo "$CHALLENGE_RESPONSE" | jq -r '.transaction')
-
-# Step 2: Sign the challenge transaction using Stellar CLI
-# Note: The output includes info messages; the signed XDR is on the last line
-SIGNED_CHALLENGE_XDR=$(echo "$CHALLENGE_XDR" | stellar tx sign --sign-with-key "$SECRET_SEED" 2>&1 | tail -1)
-
-# Step 3: Submit the signed challenge and receive JWT token
-curl -X POST "http://localhost:8080/auth" \
-  -H "Content-Type: application/json" \
-  -d "{\"transaction\": \"$SIGNED_CHALLENGE_XDR\"}"
-```
-
-:::
-
-[sep1-ap]: ../sep1/README.mdx
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/README.mdx
deleted file mode 100644
index ee8a06574e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Depósitos y Retiros Hospedados (SEP-24)
-sidebar_position: 90
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-24 permite un método mediante el cual las billeteras y/o exchanges permiten al usuario interactuar directamente con una rampa de entrada y salida.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/configuration.mdx
deleted file mode 100644
index ed02284bff..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/configuration.mdx
+++ /dev/null
@@ -1,213 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Modificar un Archivo de Información Stellar
-
-A continuación, modifica el archivo `stellar.toml` creado [anteriormente][sep1-ap]. Las billeteras necesitan saber que tu negocio admite la funcionalidad SEP-24, y también necesitan conocer todas las monedas que admites.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-TRANSFER_SERVER_SEP0024 = "http://localhost:8080/sep24"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
-WEB_AUTH_CONTRACT_ID = "Your web auth contract id"
-
-# Add support for USDC
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-# Optionally, add support for XLM
-[[CURRENCIES]]
-code = "native"
-status = "test"
-is_asset_anchored = false
-anchor_asset_type = "crypto"
-desc = "XLM, the native token of the Stellar network."
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que necesitarás crear otro archivo para tu implementación en producción que utilice la frase de contraseña de la red pública, las URLs de servicio de producción, tus cuentas de distribución y clave de firma de Mainnet, así como las cuentas emisoras de Mainnet de los activos que utiliza tu servicio.
-
-## Habilitar Depósitos y Retiradas de Fondos Hospedados
-
-Ahora estás listo para habilitar depósitos y retiradas de fondos hospedados a través de la API SEP-24. Especifica lo siguiente en tu archivo `dev.assets.yaml`, y cambia los valores según tus preferencias. Este archivo de ejemplo para activos habilitará el soporte para USDC de Circle y un dólar fiat.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep24:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - SEPA
-          - SWIFT
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - bank_account
-          - cash
-  - id: iso4217:USD
-    significant_decimals: 2
-  # Optional support for XLM
-  - id: stellar:native
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 7
-    sep24:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - SEPA
-          - SWIFT
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - bank_account
-          - cash
-```
-
-</CodeExample>
-
-La información proporcionada para el valor `assets` se corresponde estrechamente con la información que se expondrá a la aplicación billetera usando el endpoint SEP-24 [`GET /info`][sep24-get-info]. Además, Anchor Platform usa esta información para validar las solicitudes hechas a tu servicio.
-
-Agrega las siguientes variables a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-// Required
-SEP24_ENABLED=true
-SEP24_INTERACTIVE_URL_BASE_URL=http://example.com
-SEP24_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET="your encryption key shared with your business server"
-SECRET_SEP24_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-
-// Optional
-SEP24_INITIAL_USER_DEADLINE_SECONDS=1209600
-```
-
-</CodeExample>
-
-`SEP24_INTERACTIVE_URL_BASE_URL` es la URL que Anchor Platform proporcionará a las aplicaciones billetera cuando inicien transacciones. Las aplicaciones billetera abrirán esta URL en una vista web dentro de su app, transfiriendo el control de la experiencia de usuario del billetero a tu negocio. Esta URL apunta al widget web que tu negocio implementa. Contiene toda la lógica definida por el negocio. Profundizaremos en esta experiencia en secciones posteriores.
-
-`SEP24_MORE_INFO_URL_BASE_URL` es la URL que Anchor Platform proporcionará a las aplicaciones billetera cuando quieran mostrar información sobre una transacción iniciada previamente. Esta URL se usa principalmente en las vistas de historial de transacciones de las billeteras, y tu negocio puede definir qué información mostrar sobre la transacción.
-
-`SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET` y `SECRET_SEP24_MORE_INFO_URL_JWT_SECRET` son claves de encriptación que Anchor Platform usará para generar tokens de corta duración que añadirá a las URLs proporcionadas a la billetera. El servidor de tu negocio también debe tener estas claves en su entorno para poder verificar la firma del token.
-
-`SEP24_INITIAL_USER_DEADLINE_SECONDS` es un parámetro opcional que define el tiempo en segundos que un usuario tiene para actuar antes de que la transacción pase al siguiente estado. Determina el campo `user_action_required_by`, que indica la fecha límite. Consulta [Métodos JSON-RPC][json-rpc-methods] para ejemplos de uso.
-
-## Probar con la Billetera Demo
-
-¡Las billeteras ahora deberían poder descubrir, autenticar e iniciar transacciones con tu servicio! Tu proyecto y archivos fuente deberían verse ahora algo así.
-
-<CodeExample>
-
-```
-├── dev.env
-├── docker-compose.yaml
-├── config
-│   ├── dev.assets.yaml
-│   ├── dev.stellar.toml
-```
-
-</CodeExample>
-
-Tu entorno debería verse ahora como el siguiente.
-
-<CodeExample>
-
-```bash
-# dev.env
-ASSETS_TYPE=file
-ASSETS_VALUE=/home/dev.assets.yaml
-
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/home/dev.stellar.toml
-
-SEP10_ENABLED=true
-SEP10_HOME_DOMAIN=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret encryption key"
-
-SEP24_ENABLED=true
-SEP24_INTERACTIVE_URL_BASE_URL=http://localhost:8081
-SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET="your encryption key shared with your business server"
-SECRET_SEP24_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-```
-
-</CodeExample>
-
-Para probar esto, ve a la [Billetera Demo de Stellar][stellar-demo-wallet].
-
-[![demo wallet connected to the anchor platform](../../assets/anchor-platform-sep24-demo-wallet.png)](../../assets/anchor-platform-sep24-demo-wallet.png)
-
-Inicia una transacción realizando lo siguiente:
-
-- Crea un nuevo par de claves
-- Haz clic en el botón "Agregar activo" y escribe
-  - el código del activo Stellar en tu archivo `stellar.toml`
-  - tu dominio principal, `localhost:8080`
-- Selecciona el desplegable y haz clic en "Depósito SEP-24", luego haz clic en "Iniciar"
-
-La billetera demo debería poder encontrar tu archivo `stellar.toml`, autenticarse usando el par de claves Stellar que acabas de crear e iniciar una transacción. Sin embargo, cuando la billetera demo intente abrir la URL proporcionada por Anchor Platform, obtendrás una página de no encontrado.
-
-[![demo wallet after initiating a transaction](../../assets/anchor-platform-sep24-demo-wallet-widget.png)](../../assets/anchor-platform-sep24-demo-wallet-widget.png)
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
-[sep1-ap]: ../sep1/README.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/example.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/example.mdx
deleted file mode 100644
index 566a05dee6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/example.mdx
+++ /dev/null
@@ -1,438 +0,0 @@
----
-title: Ejemplo
-sidebar_position: 40
----
-
-Integrarse con Anchor Platform implica tres áreas clave:
-
-- Desarrollar una experiencia de usuario basada en web que pueda abrirse en una vista web móvil
-- Proporcionar actualizaciones de estado de transacciones a Anchor Platform
-- Obtener actualizaciones de estado de transacciones desde Anchor Platform
-
-## Desarrollar una experiencia de usuario basada en web
-
-Anchor Platform no ofrece una IU de marca blanca que tu negocio pueda utilizar, y en su lugar espera que el negocio construya su propia IU y sistema backend. No desarrollaremos toda una experiencia de usuario para on & off-ramp en esta guía, pero cubriremos las formas en que tu producto existente debe actualizarse para ser compatible con Anchor Platform.
-
-### Autenticación
-
-Si tu negocio ya cuenta con un producto on & off-ramp, probablemente tengas un sistema existente para la autenticación de usuarios. Sin embargo, dado que Anchor Platform autentica al usuario antes de proporcionar la URL del negocio, requerir que el usuario pase por otra forma de autenticación no es realmente necesario. De esta manera, se puede considerar que Anchor Platform proporciona una forma alternativa de autenticación.
-
-El negocio es libre de seguir exigiendo que los usuarios se autentiquen usando su sistema actual, pero la experiencia ideal para el usuario omitiría este paso y crearía una sesión autenticada si ya se ha autenticado con su cuenta Stellar.
-
-Anchor Platform añade un parámetro de consulta JWT `token` a la URL del negocio proporcionada a la aplicación wallet. Este token está firmado por el valor previamente configurado `SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET` e incluye la información que necesitas para identificar al usuario. El proceso debería ser algo así:
-
-1. Pasar el `token` agregado a la URL a tu sistema backend
-2. Verificar la firma del `token` y comprobar su expiración
-3. Crear una sesión autenticada para el usuario identificado por `token.sub`
-
-El contenido decodificado del `token` se verá algo así:
-
-<CodeExample>
-
-```json
-{
-  "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
-  "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB:1234567",
-  "exp": 1516239022,
-  "data": {
-    "first_name": "John",
-    "last_name": "Doe",
-    "email": "johndoe@example.com"
-  }
-}
-```
-
-</CodeExample>
-
-Observa que el valor `sub` identifica al usuario usando una cuenta Stellar y un entero. Este es el valor cuando aplicaciones custodiales que usan una cuenta común se autentican con tu servicio. Cuando billeteras no custodiales se autentican, el token puede tener un aspecto ligeramente diferente.
-
-<CodeExample>
-
-```json
-{
-  "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
-  "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB",
-  "exp": 1516239022,
-  "data": {
-    "client_domain": "api.vibrantapp.com",
-    "first_name": "John",
-    "last_name": "Doe",
-    "email": "johndoe@example.com"
-  }
-}
-```
-
-</CodeExample>
-
-Aquí, el valor `sub` solo contiene una clave pública para identificar al usuario, y el campo `data.client_domain` identifica la aplicación wallet usada para autenticar.
-
-En ambos casos, toda la información en el objeto `data` es opcional y solo estará presente si la wallet proporciona esa información.
-
-Agreguemos un servidor backend a nuestro archivo compose que se usará para verificar el token y crear sesiones web autenticadas para usuarios que inician transacciones.
-
-<CodeExample>
-
-```yaml
-# docker-compose.yaml
----
-business-server:
-  build: .
-  ports:
-    - "8081:8081"
-  env_file:
-    - ./dev.env
-  depends_on:
-    - platform-server
-```
-
-</CodeExample>
-
-Creemos un contenedor Docker simple para nuestra aplicación.
-
-<CodeExample>
-
-```docker
-FROM node:19
-
-WORKDIR /home
-COPY . .
-RUN npm install
-
-CMD ["node", "server.js"]
-```
-
-</CodeExample>
-
-Ahora creemos una aplicación NodeJS mínima.
-
-<CodeExample>
-
-```bash
-yarn init -y
-yarn add express jsonwebtoken
-touch server.js
-```
-
-</CodeExample>
-
-A continuación, un ejemplo de un servidor backend que autentica a un usuario usando NodeJS.
-
-<CodeExample>
-
-```js
-# server.js
-const express = require("express");
-const jwt = require("jsonwebtoken");
-const app = express();
-const port = process.env.BUSINESS_SERVER_PORT;
-
-app.use(express.json());
-
-/*
- * We'll store user session data in memory, but production systems
- * should store this data somewhere more persistent.
- */
-const sessions = {};
-
-/*
- * Create an authenticated session for the user.
- *
- * Return a session token to be used in future requests as well as the
- * user data. Note that you may not have a user for the stellar account
- * provided, in which case the user should go through your onboarding
- * process.
- */
-app.post("/session", async (req, res) => {
-  let decodedPlatformToken;
-  try {
-    decodedPlatformToken = validatePlatformToken(req.body.platformToken);
-  } catch (err) {
-    res.status = 400;
-    res.send({ "error": err });
-    return;
-  }
-  let user = getUser(decodedPlatformToken.sub);
-  let sessionToken = jwt.sign(
-    { "jti": decodedPlatformToken.jti },
-    process.env.SESSION_JWT_SECRET
-  );
-  sessions[sessionToken] = user;
-  res.send({
-    "token": sessionToken,
-    "user": user
-  });
-});
-
-/*
- * Validate the signature and contents of the platform's token
- */
-function validatePlatformToken(token) {
-  if (!token) {
-    throw "missing 'platformToken'";
-  }
-  let decodedToken;
-  try {
-    decodedToken = jwt.verify(token, process.env.SECRET_SEP10_JWT_SECRET);
-  } catch {
-    throw "invalid 'platformToken'";
-  }
-  if (!decodedToken.jti) {
-    throw "invalid 'platformToken': missing 'jti'";
-  }
-  return decodedToken;
-}
-
-/*
- * Query your own database for the user based on account:memo string parameter
- */
-function getUser(sub) {
-  return null;
-}
-
-app.listen(port, () => {
-    console.log(`business server listening on port ${port}`);
-});
-```
-
-</CodeExample>
-
-Ejecuta esto junto con el servidor de la plataforma y la base de datos e inicia una nueva transacción con la [billetera de demostración][stellar-demo-wallet]. Luego, enviaremos el token a nuestro servidor.
-
-<CodeExample>
-
-```bash
-curl \
-  -X POST \
-  -H 'Content-Type: application/json' \
-  -d '{"platformToken": "<paste the token from the URL here>"}' \
-  http://localhost:8081/session | jq
-```
-
-</CodeExample>
-
-## Proporcionando actualizaciones a la plataforma
-
-Creamos un endpoint para nuestro servidor de negocio que acepte la información recopilada en nuestra IU.
-
-<CodeExample>
-
-```js
-# server.js
-
-// Production systems should either let the Anchor Platform generate its own memos
-// or have your custodial service generate a memo for each transaction.
-const transactionMemos = {};
-
-app.post("/transaction", async (req, res) => {
-  let sessionToken;
-  try {
-    sessionToken = validateSessionToken(req.headers.get("authorization"));
-  } catch (err) {
-    res.status = 400;
-    res.send({ "error": err })
-    return;
-  }
-  // assuming this is a withdrawal transaction, we'll provide a memo, which is
-  // required by our third-party custodian to credit us the payment. When the
-  // payment is made with this memo, we can match the on-chain payment with the
-  // transaction in the Anchor Platform's database.
-  transactionMemos[req.body.transaction.id] = parseInt(Math.random() * 100000);
-  let rpcRequestBody = [
-    {
-      "id": 1,
-      "jsonrpc": "2.0",
-      "method": "request_onchain_funds",
-      "params": {
-        "transaction_id": req.body.transaction.id,,
-        "message": "waiting for the user to provide off-chain funds.",
-        "amount_in": {
-          "amount": req.body.amount_in.amount,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "amount_out": {
-          "amount": req.body.amount_out.amount,
-          "asset": "iso4217:USD"
-        },
-        "fee_details": {
-          "total": req.body.fee_details.total,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "destination_account": "GD...G",
-        "memo": transactionMemos[req.body.transaction.id],
-        "memo_type": "id"
-      }
-    }
-  ];
-  let platformResponse;
-  try {
-    platformResponse = await updatePlatformTransaction(rpcRequestBody);
-  } catch (err) {
-    res.status = 500;
-    res.send({ "error": err })
-    return;
-  }
-  res.send({
-    "transaction": platformResponse.records[0]
-  });
-});
-
-function validateSessionToken(authorizationHeader) {
-    let parts = authorizationHeader.split(" ");
-    if (parts.length != 2 || parts[0] != "Bearer") {
-        throw "invalid authorization header format";
-    }
-    let sessionToken = parts[1];
-    try {
-        jwt.verify(sessionToken, process.env.SESSION_JWT_SECRET);
-    } catch {
-        throw "invalid session token";
-    }
-    if (!sessions[sessionToken]) {
-        throw "expired session";
-    }
-    return sessionToken;
-}
-
-async function updatePlatformTransaction(requestBody) {
-  let response = await fetch(
-    `${process.env.PLATFORM_SERVER}`,
-    {
-      method: "POST",
-      headers: {
-        "Content-Type": "application/json"
-      },
-      body: JSON.stringify(requestBody)
-    }
-  );
-  if (response.status != 200) {
-    throw `unexpected status code: ${response.status}`;
-  }
-  return await response.json();
-}
-```
-
-</CodeExample>
-
-Esto actualizará la base de datos de Anchor Platform con la información proporcionada y permitirá que las aplicaciones wallet obtengan esta información actualizada para transmitirla al usuario. Ya deberías haber informado al usuario sobre los montos de la transacción y que tu negocio está esperando que llegue el pago en cadena, pero proporcionar estas actualizaciones permite a los usuarios ver el estado de sus transacciones a través de su aplicación móvil sin abrir de nuevo la IU del negocio.
-
-:::note
-
-Actualmente, Anchor Platform no envía notificaciones a la aplicación wallet cuando cambian los estados de las transacciones, sin embargo, está en nuestro plan agregar estas notificaciones o "callback requests" para que las aplicaciones wallet no tengan que realizar polling a Anchor Platform para actualizaciones.
-
-:::
-
-## Obteniendo actualizaciones desde la plataforma
-
-Si solo usas Anchor Platform para exponer las APIs SEP a las aplicaciones wallet, no tendrás una fuerte razón para obtener actualizaciones de estado de transacciones desde Anchor Platform, principalmente porque no actualizará el estado de la transacción hasta que hagas solicitudes `JSON-RPC API`.
-
-Sin embargo, si usas Anchor Platform para monitorear la red Stellar en busca de pagos entrantes (asociados a transacciones de retirada), Anchor Platform actualizará los estados de las transacciones cuando se reciban los pagos.
-
-Hay dos maneras de obtener actualizaciones desde Anchor Platform,
-
-- Realizar polling al endpoint `GET /transactions/:id` de la API de la plataforma para las transacciones por las que esperas un pago
-- Transmitir eventos de cambio de estado de transacciones desde un cluster Kafka
-
-Aunque la transmisión de cambios en el estado de transacciones desde un cluster Kafka puede ser un enfoque más robusto y escalable, en esta guía usaremos el método de polling. Configurar y usar un cluster Kafka será tema de una sección diferente de la documentación.
-
-Primero, configuremos Anchor Platform para observar la red Stellar en busca de pagos entrantes.
-
-<CodeExample>
-
-```yaml
-# docker-compose.yml
----
-stellar-observer:
-  image: stellar/anchor-platform:latest
-  command: --stellar-observer
-  env_file:
-    - ./dev.env
-  volumes:
-    - ./config:/home
-  depends_on:
-    - db
-```
-
-</CodeExample>
-
-El comando `--stellar-observer` inicia un proceso que monitorea las cuentas de distribución configuradas en tu archivo `config.yaml` para pagos de retirada.
-
-Si se envía un pago a una de estas cuentas y el memo adjunto a la transacción coincide con un valor `memo` proporcionado o generado por Anchor Platform, Anchor Platform considerará la transacción asociada a ese memo como recibida y actualizará su estado a `pending_anchor`. Esto se hace mediante una solicitud `JSON-RPC API`, por lo que debemos configurar la URL que debe usar.
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_BASE_URL=http://platform-server:8085
-```
-
-</CodeExample>
-
-Hagamos algunas adiciones al archivo `server.js` para que podamos realizar polling a Anchor Platform para nuestros pagos esperados.
-
-<CodeExample>
-
-```js
-// server.js
-...
-/*
- * Fetch the transaction data from the Platform API
- *
- * Production systems should have proper retry mechanisms.
- */
-async function getPlatformTransaction(transactionId) {
-  let response = await fetch(`${process.env.PLATFORM_SERVER}/transactions/${transactionId}`)
-  if (response.status != 200) {
-    throw `unexpected status code: ${response.status}`;
-  }
-  return await response.json();
-}
-
-(async () => {
-  while (true) {
-    await new Promise(r => setTimeout(r, 2000));
-    let requestPromises;
-    for (const transactionId in transactionMemos) {
-      requestPromises.push(getPlatformTransaction(transactionId))
-    }
-    let transactions = await new Promise.all(requestPromises);
-    for (const transaction in transactions) {
-      // assuming all requests were successful
-      if (transaction.status == "pending_anchor") {
-        // initiate off-chain delivery of funds
-        console.log(`received payment for transaction ${transaction.id}`);
-      }
-    }
-  }
-})()
-```
-
-</CodeExample>
-
-## Implementación completa de ejemplo
-
-Stellar proporciona una implementación de ejemplo para un servidor de negocio SEP-24. Está dividida en dos partes: 1) una IU web, accesible para el usuario final; y 2) una implementación backend, usada para obtener y enviar actualizaciones desde/hacia Anchor Platform.
-
-El código para la IU web se encuentra [aquí][sep-24-ref-ui]
-
-El código para el backend es parte de Anchor Platform y está disponible como un [submódulo][sep-24-ref].
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/faq.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/faq.mdx
deleted file mode 100644
index 829948062e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/faq.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Preguntas Frecuentes (FAQ)
-sidebar_position: 50
----
-
-### ¿Cómo usar los JWT?
-
-Como parte del flujo, una vez que un usuario realiza una solicitud, es decir, una solicitud interactiva de retirada o depósito, será procesada por la Anchor Platform y enviada a tu servicio. La Anchor Platform realizará una llamada `GET` a `<configured url>?token=<jwt token>`.
-
-Este token JWT contendrá:
-
-1. `exp` es el tiempo de expiración del token. Debes verificar que el token proporcionado no haya expirado.
-2. `sub` es la cuenta asociada con esta transacción. Puede usarse para identificar la cuenta del usuario. Ten en cuenta que este valor puede ser diferente de la cuenta que se usará para recibir o enviar fondos.
-3. `jti` es el hash de la transacción.
-4. `data` es la carga útil extra que ha sido establecida por el usuario. Siempre contendrá el `asset` de Stellar que se desea depositar o retirar. Si lo provee el cliente, también contendrá la `amount` que el usuario desea transaccionar, el `client_domain` de la billetera verificado durante la autenticación SEP-10, y `client_name` (definido como 'name' en la configuración de [clients] si está disponible), así como el `lang` (preferencia de idioma) del usuario.
-
-### ¿Cómo Proveer Tarifas?
-
-Actualmente, se recomienda proveer las tarifas/tasas de exchange en el iFrame/vista web de tu aplicación.
-
-El estándar [SEP-24] provee un endpoint `/fee` para que los negocios establezcan tarifas estáticas para sus transacciones. Sin embargo, actualmente no es admitido por la Anchor Platform.
-
-:::note
-
-El endpoint /fee será descontinuado en el futuro.
-
-:::
-
-### ¿Cómo identificar la cuenta del usuario?
-
-Debes usar el campo `sub` del token JWT. Para billeteras custodiales, este valor tendrá el formato `account:memo`. Usa el memo para identificar al usuario. Para billeteras no custodiales, simplemente usa el valor `sub`, que será igual a la cuenta del usuario.
-
-### ¿Cómo identificar la billetera?
-
-Utiliza los atributos `data.client_domain` dentro del token JWT. En presencia de la configuración [clients], el token JWT también incluirá el campo `data.client_name`, lo que permite identificar la billetera.
-
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[clients]: ../sep10/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/getting-started.mdx
deleted file mode 100644
index f9f23af640..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/getting-started.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Comenzar en español
-sidebar_position: 10
----
-
-Esta guía te llevará a través de la configuración e integración con la Plataforma Anchor con el propósito de construir un servicio de entrada y salida compatible con [SEP-24][sep-24], el protocolo estandarizado del ecosistema para depósitos y retiros alojados.
-
-Al aprovechar el soporte de la Plataforma Anchor para SEP-24, las empresas pueden ofrecer su servicio de entrada y salida como una experiencia dentro de la aplicación a través de aplicaciones basadas en Stellar como wallets e intercambios, ampliando su alcance y conectando con usuarios mediante las aplicaciones que ya utilizan.
-
-Antes de continuar con esta sección, asegúrate de haber [instalado][installation-ap] la Plataforma Anchor y configurado las funciones necesarias requeridas por SEP-24: [SEP-1 (Archivo de información de Stellar)][sep1-ap], [SEP-10 (Autenticación Stellar)][sep10-ap] y [SEP-45 (Autenticación web Stellar para cuenta de contrato)][sep45-ap].
-
-## La experiencia básica del usuario
-
-La experiencia completa del cliente en un depósito y retiro es la siguiente:
-
-1. El cliente abre la aplicación wallet SEP-24 de su elección
-2. El cliente selecciona un activo para depositar y el wallet encuentra un anchor (los clientes también pueden elegir un anchor específico)
-3. Una vez que el wallet se autentica con el anchor, el cliente comienza a ingresar su información KYC y de transacción solicitada por el anchor
-4. El wallet proporciona instrucciones, y el cliente deposita moneda fiduciaria real con el anchor (por ejemplo, realiza una transferencia bancaria)
-5. Una vez que el wallet recibe el depósito, el cliente recibe el activo tokenizado en la red Stellar desde la cuenta de distribución del anchor
-
-El cliente puede entonces usar el activo digital en la red Stellar para remesas, pagos, trading, reserva de valor u otro caso de uso no listado aquí. En una fecha posterior, el cliente podría decidir retirar sus activos de la red Stellar, lo que sería algo así:
-
-1. El cliente abre su aplicación wallet
-2. El cliente selecciona el activo para retirar y el wallet encuentra el anchor
-3. Después de autenticarse con el anchor, el wallet abre la URL interactiva dada y permite al cliente ingresar su información de transacción (el KYC ya ha sido recopilado)
-4. Después de solicitar la aprobación del cliente, el wallet envía la cantidad especificada del saldo del activo del cliente a la cuenta de distribución del anchor en Stellar
-5. Una vez que el anchor recibe el pago, el cliente recibe los fondos retirados mediante transferencia bancaria.
-
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/integration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/integration.mdx
deleted file mode 100644
index 6adbc0bb18..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/integration.mdx
+++ /dev/null
@@ -1,929 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-import { AttributeTable } from "@site/src/components/AttributeTable";
-import Security from "../../admin-guide/component/security/security.mdx";
-import UsingApiKey from "../../admin-guide/component/security/api_key.mdx";
-import UsingJwt from "../../admin-guide/component/security/jwt.mdx";
-import Rpc from "../../admin-guide/component/rpc/rpc.mdx";
-import RpcRequest from "../../admin-guide/component/rpc/request.mdx";
-import RpcResponse from "../../admin-guide/component/rpc/response.mdx";
-import RpcError from "../../admin-guide/component/rpc/error.mdx";
-import Observer from "../../admin-guide/component/observer/observer.mdx";
-
-Uno de los principales puntos de interacción con la Anchor Platform es notificar a la Anchor Platform sobre eventos relacionados con la transacción.
-
-En general, querrás proporcionar actualizaciones para los siguientes eventos:
-
-- Tu negocio está procesando la información KYC proporcionada por el usuario
-- Tu negocio está listo para recibir fondos del usuario
-- Tu negocio ha recibido fondos del usuario
-- Tu negocio ha enviado fondos al usuario
-- Tu negocio ha procesado un reembolso para la transacción del usuario
-- Tu negocio experimentó un error inesperado
-
-Esto se realiza haciendo solicitudes JSON-RPC al endpoint de la API de la Platform. Las solicitudes JSON-RPC te permiten actualizar el estado de la transacción. Para mover la transacción a un estado específico, es necesario hacer una solicitud JSON-RPC correspondiente y pasar los datos requeridos por este método RPC.
-
-La API JSON-RPC de la Anchor Platform está diseñada para notificar a la plataforma sobre cambios en el estado de la transacción. Dicho esto, la API será llamada cada vez que un usuario o la anchor realice una acción que haga avanzar el estado de la transacción en el flujo.
-
-La comunicación desde la Anchor Platform sobre actualizaciones de transacciones, actualizaciones de clientes y creación de cotizaciones se gestiona a través del servicio de eventos. Esta es una función opcional que debe configurarse por separado de la integración SEP-6. Para más información, consulta [Gestión de Eventos][event-handling].
-
-Puedes obtener más información sobre el flujo y los estados de la transacción en el [documento del protocolo SEP-24][sep-24]
-
-## Callbacks
-
-La Anchor Platform depende del servidor de negocio para proporcionar y almacenar información sobre las cotizaciones.
-
-### Cotizaciones y Tarifas
-
-Para admitir el intercambio de activos no equivalentes, la Anchor Platform expone una API compatible con SEP-38 para proporcionar cotizaciones para el exchange. La API de cotizaciones se utiliza para proporcionar al usuario la cantidad esperada del activo que recibirá a cambio del activo que envía. La API de cotizaciones también se usa para proporcionar al usuario las tarifas esperadas para la transacción. Por lo tanto, tu servidor de negocio debe implementar la [API de tarifa][rate-callback] para proporcionar cotizaciones a la Anchor Platform.
-
-## Asegurando la API de la Platform
-
-<Security />
-
-### Uso de la clave API
-
-<UsingApiKey />
-
-### Uso de JWT
-
-<UsingJwt />
-
-## Realizando solicitudes JSON-RPC
-
-<Rpc />
-
-### Solicitud JSON-RPC
-
-<RpcRequest />
-
-### Respuesta JSON-RPC
-
-<RpcResponse />
-
-### Códigos de Error
-
-<RpcError />
-
-## Actualizando la Transacción de Depósito vía JSON-RPC
-
-El diagrama del flujo de depósito SEP-24 define la secuencia/reglas para la transición de estados de la transacción y un conjunto de métodos JSON-RPC que se deben llamar para cambiar ese estado. No puedes definir el estado que quieres asignar a una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene los atributos requeridos, la Anchor Platform devolverá un error y no cambiará el estado de la transacción.
-
-[![flujo de depósito sep24](../../assets/sep24-deposit-flow-diagram.png)](../../assets/sep24-deposit-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en un estado de error o ha expirado.
-
-:::
-
-### Listo para Recibir Fondos
-
-El primer paso del flujo de depósito después de iniciar el depósito en sí es recopilar KYC. Generalmente se realiza en la aplicación web, pero también puede ser proporcionado opcionalmente por la aplicación billetera, usando [SEP-9]. Una vez que se recopila el KYC necesario, se debe hacer una solicitud JSON-RPC `request_offchain_funds`.
-
-<CodeExample>
-
-```json
-// request-offchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_offchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request offchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es la cantidad que el usuario debe enviar al negocio.
-- `amount_out` es la cantidad que el usuario recibirá.
-- `fee_details` es el monto total de tarifas cobradas por el negocio.
-- `asset` es parte del campo `amount_x` y está en formato SEP-38. En este ejemplo, está configurado en USD, asumiendo que el usuario realizó una transferencia bancaria al sistema usando USD.
-
-La información sobre los montos (entrada/salida/tarifa) es requerida si deseas mover la transacción de `incomplete` a `pending_user_transfer_start`. Si el estado de la transacción cambia de `pending_anchor` a `pending_user_transfer_start`, puedes omitir la definición de los montos.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-offchain-funds.json
-```
-
-</CodeExample>
-
-:::tip
-
-Cuando el proceso de KYC es largo (por ejemplo, verificación de identidad), se aconseja primero establecer el estado de la transacción a `pending_anchor` usando la solicitud JSON-RPC `notify_interactive_flow_completed`. Esto indicará al usuario que el KYC está en proceso.
-
-:::
-
-### Procesando Información KYC
-
-:::tip
-
-Este paso es opcional. La mayoría de los negocios no lo usan. Puedes saltarlo e ir al [siguiente paso](#funds-received).
-
-Se recomienda usar este estado cuando la verificación KYC pueda necesitar realizarse de forma asincrónica.
-
-:::
-
-**Debes** especificar los campos `amount_x`.
-
-<CodeExample>
-
-```json
-// kyc-in-process.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_interactive_flow_completed",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Interactive flow completed.",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh kyc-in-process.json
-```
-
-</CodeExample>
-
-### Fondos Recibidos
-
-Si se recibieron fondos offchain, querrás proporcionar información actualizada de la transacción.
-
-<CodeExample>
-
-```json
-// offchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds received",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `funds_received_at` es la fecha y hora de recepción de los fondos
-- `external_transaction_id` es el ID de la transacción en la red externa
-
-Los campos de cantidad son opcionales. Si se omiten, se tomarán los valores de solicitudes JSON-RPC previas.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-received.json
-```
-
-</CodeExample>
-
-### Esperando Fondos del Usuario
-
-En el mundo real, el proceso de confirmación de la transferencia puede tomar tiempo. En tales casos, las transacciones deben establecerse en un nuevo estado que indique que se ha recibido la confirmación de la transferencia, pero aún no los fondos.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Enviando Fondos Onchain
-
-Luego, envía una transacción en la red Stellar para cumplir con la solicitud del usuario. Después de completar la transacción, es necesario enviar la solicitud JSON-RPC `notify_onchain_funds_sent` para notificar al usuario que los fondos fueron enviados con éxito.
-
-<CodeExample>
-
-```json
-// onchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds sent",
-      "stellar_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `stellar_transaction_id` es el ID de la transacción en la red Stellar de la transferencia
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-sent.json
-```
-
-</CodeExample>
-
-Después de esta solicitud JSON-RPC, la transacción cambiará al estado `completed`.
-
-### Pendiente de Trustline
-
-Este estado debe establecerse si un pago requiere una trustline de activo que el usuario no configuró. Hay dos formas en que la transacción puede cambiar al estado `pending_trust`. El primero es cuando el servidor de negocio detecta que la trustline no está configurada. La segunda es cuando el negocio detecta que falta la trustline y quiere notificar al usuario que debe configurarla. Para mover la transacción al estado `pending_trust`, es necesario hacer la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// request-trust.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_trust",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine not configured"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-trust.json
-```
-
-</CodeExample>
-
-:::info
-
-El servidor de negocio verifica periódicamente si la trustline ha sido configurada. Si lo fue, puede enviar un pago y cambiar el estado de la transacción a `pending_stellar`.
-
-:::
-
-### Trustline Configurada
-
-Este estado debe establecerse si el negocio ha detectado si la trustline fue o no configurada por el usuario.
-
-<CodeExample>
-
-```json
-// trust-set.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_trust_set",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine set",
-      "success": "true"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- El flag `success` define si la trustline fue configurada por el usuario o no
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh trust-set.json
-```
-
-</CodeExample>
-
-:::info
-
-Dependiendo del flag `success`, el estado de la transacción cambiará a `pending_stellar` si la trustline fue configurada, o a `pending_anchor` si no lo fue.
-
-:::
-
-### Enviando reembolso
-
-Existe la posibilidad de devolver fondos al usuario (reembolso). Puedes reembolsar la suma completa (reembolso total) o hacer un conjunto de reembolsos parciales. Además, si el usuario envió más dinero de lo esperado, puedes devolver una parte al usuario y enviar el resto como fondos onchain.
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::info
-
-Si la suma de los reembolsos es menor que `amount_in`, el estado de la transacción se establecerá en `pending_anchor`. Solo si la suma de los reembolsos es igual a `amount_in`, el estado de la transacción se establecerá en `refunded`.
-
-:::
-
-### Reembolso Pendiente
-
-Es similar a [Reembolso enviado](#refund-sent), pero maneja el caso cuando un reembolso ha sido enviado a la red externa pero aún no está confirmado. El estado de la transacción se establece en `pending_external`. Este es el estado que se establecerá cuando se esté esperando que la red externa, como Bitcoin u otra criptomoneda, complete una transacción, o al esperar una transferencia bancaria.
-
-### Error en la Transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, es necesario establecer el estado de la transacción en `error`. Puedes usar el campo de mensaje para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario ha realizado una transferencia, deberías hacer una recuperación de la transacción, y luego puedes reintentar procesar la transacción o iniciar un reembolso.
-
-:::
-
-### Transacción Expirada
-
-Tu negocio puede querer manejar transacciones abandonadas expirándolas si han estado inactivas por cierto período. Para lograr esto, verifica el estado de la transacción usando el endpoint `GET /transactions` y ordena los resultados por la marca de tiempo `user_action_required_by`. Si la marca de tiempo ha pasado, ejecuta manualmente la lógica apropiada, como expirar la transacción o iniciar un auto-reembolso, según el estado actual de la transacción. Por ejemplo, para expirar la transacción el negocio debe cambiar el estado de la transacción a `expired`:
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no puede usarse después de que el usuario haya realizado una transferencia.
-
-:::
-
-### Transacción en Espera
-
-En casos raros, puedes querer pausar la transacción actual y solicitar más información al usuario (después de recibir la transferencia). Esto podría usarse para casos de cumplimiento normativo.
-
-<CodeExample>
-
-```json
-// transaction-hold.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_on_hold",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction is on hold. Please contact customer support to resolve the hold."
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-hold.json
-```
-
-</CodeExample>
-
-### Recuperación de Transacción
-
-El estado de la transacción puede cambiar de `error/expired` a `pending_anchor`. Después de la recuperación, puedes reembolsar los activos recibidos o continuar con el procesamiento de la transacción. Para recuperar una transacción, es necesario hacer la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-## Actualizando la Transacción de Retirada vía JSON-RPC
-
-Este diagrama define una secuencia/reglas de la transición de estados para el flujo de retirada SEP-24.
-
-[![flujo de retirada sep24](../../assets/sep24-withdrawal-flow-diagram.png)](../../assets/sep24-withdrawal-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en un estado de error o ha expirado.
-
-:::
-
-Una vez finalizado el flujo de depósito, implementar la retirada es sencillo. Algunas partes del flujo son similares y pueden reutilizarse.
-
-El punto de partida tanto para retirada como para depósito es el mismo.
-
-### Listo para Recibir Fondos
-
-Similar al depósito, el siguiente paso es notificar al usuario que la anchor está lista para recibir fondos. Sin embargo, dado que tu servicio recibirá transacciones a través de la red Stellar, la actualización será diferente.
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "iso4217:USD"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- Valor `memo` que se adjuntará a la transacción
-- Tipo de memo que la anchor debe adjuntar a la transacción
-- Cuenta destino
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-:::tip
-
-Establecer `memo`, `memo_type` y `destination_account` es opcional.
-
-Si la integración con un custodio tercero está habilitada, la Anchor Platform puede generar `memo`, `memo_type` y `destination_address` si se elige un `deposit_info_generator_type` correspondiente. Además, puedes proporcionar `memo` y `memo_type` a la solicitud como se muestra arriba. Ten en cuenta que el memo debe ser único, eso es lo que ayuda a asociar las transacciones Stellar con las transacciones SEP.
-
-Si tu negocio gestiona los activos, la Anchor Platform puede generar memos para ti. Cuando el estado cambia a `pending_user_transfer_start`, la Anchor Platform establece automáticamente el `memo` y `memo_type` (solo si no se incluyen en la solicitud).
-
-:::
-
-:::note
-
-Debe configurarse la cuenta Stellar que se usará para recibir fondos.
-
-:::
-
-### Procesando Información KYC
-
-Este paso es opcional, y es similar a [Procesando Información KYC](#processing-kyc-information) del flujo de depósito.
-
-### Fondos Recibidos
-
-Si se recibieron fondos onchain, debes proporcionar los montos y cambiar el estado de la transacción a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método será llamado automáticamente por el observador de pagos Stellar cuando detecte que se han recibido fondos onchain.
-
-:::
-
-### Monto Actualizado
-
-Si se recibieron fondos onchain, pero por alguna razón `amount_in` difiere del especificado en el flujo interactivo (`amount_expected`), puedes actualizar `amount_out` y `fee_details` para que correspondan con el `amount_in` real. El estado de la transacción en este caso no cambiará y seguirá siendo `pending_anchor`.
-
-<CodeExample>
-
-```json
-// amounts-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_amounts_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Amounts updated",
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh amounts-updated.json
-```
-
-</CodeExample>
-
-:::note
-
-Solo `amount_out` y `fee_details` pueden actualizarse usando esta solicitud JSON-RPC, y no necesitas especificar los activos de los montos.
-
-:::
-
-### Fondos Offchain Enviados
-
-Para completar la transacción y cambiar su estado a `completed`, necesitas hacer la solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Fondos Offchain Disponibles
-
-Puedes mover el estado de la transacción a `pending_user_transfer_complete` si se enviaron fondos offchain y si está listo para que el usuario/beneficiario los recoja.
-
-<CodeExample>
-
-```json
-// offchain-funds-available.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_available",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds available",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-available.json
-```
-
-</CodeExample>
-
-### Fondos Offchain Pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago ha sido enviado a una red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Reembolso Enviado
-
-La lógica de reembolso funciona igual que para el flujo de depósito. Para más detalles, consulta [Reembolso Enviado](#refund-sent) del flujo de depósito.
-
-### Error en la Transacción
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Error en la Transacción](#transaction-error) del flujo de depósito.
-
-### Transacción Expirada
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Transacción Expirada](#expired-transaction) del flujo de depósito.
-
-### Transacción en Espera
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Transacción en Espera](#on-hold-transaction) del flujo de depósito.
-
-### Recuperación de Transacción
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Recuperación de Transacción](#transaction-recovery) del flujo de depósito.
-
-## Seguimiento de Transacciones Stellar
-
-<Observer />
-
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[event-handling]: ../../admin-guide/events/README.mdx
-[rate-callback]: ../../api-reference/callbacks/README.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
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
deleted file mode 100644
index 07ff30c3ca..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/setting-up-production-server.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: Configurar un servidor de producción
-sidebar_position: 60
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Una vez que el servidor de pruebas esté en funcionamiento y hayas probado ambos flujos de depósito y retiro, es hora de comenzar con el despliegue real conectado con KYC real y proveedores reales de sistemas bancarios. Antes de usar cualquier API bancaria, es fundamental que realices una auditoría de seguridad completa en el sistema para asegurarte de que no existan vulnerabilidades.
-
-## Implementar un entorno seguro
-
-Asegúrate de mantener el servidor de pruebas activo y de desplegar el sistema de producción (mainnet) en un entorno separado. Tener dos despliegues te permite validar nuevas funcionalidades en la testnet antes de moverlas al despliegue final de producción. También puedes tener un tercer entorno de staging si hay un equipo grande trabajando en esta base de código y/o habrá muchos pull requests para probar internamente antes de compartir con otras instituciones.
-
-Para cambiar a la red pública (mainnet) de Stellar, solo tienes que cambiar la [passphrase de red](/docs/networks#network-passphrases) (para autenticar solicitudes) y la [URL de Horizon](https://horizon.stellar.org/).
-
-Puedes copiar tus configuraciones de desarrollo existentes para crear una configuración de producción.
-
-Primero, necesitas cambiar tu archivo de información (`stellar.toml`):
-
-<CodeExample>
-
-```toml
-# stellar.toml
-NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"
-```
-
-</CodeExample>
-
-Luego, cambia la configuración de la Plataforma Anchor en el archivo `production.env`:
-
-### Para la conexión al servidor Horizon:
-
-<CodeExample>
-
-```bash
-# production.env STELLAR_NETWORK_NETWORK="Public"
-STELLAR_NETWORK_HORIZON_URL="https://horizon.stellar.org"
-```
-
-</CodeExample>
-
-### Para la conexión al servidor Stellar RPC:
-
-<CodeExample>
-
-```bash
-# production.env STELLAR_NETWORK_NETWORK="Public"
-STELLAR_NETWORK_RPC_URL="https://mainnet.sorobanrpc.com"
-```
-
-</CodeExample>
-
-## Conectando con KYC Real
-
-La mayoría de los anchors necesitan recolectar información de [Conoce a tu Cliente (KYC)](https://en.wikipedia.org/wiki/Know_your_customer) para cumplir con las regulaciones locales antes de procesar depósitos y retiros. El flujo de KYC normalmente consiste en un formulario simple que recopila información relevante del usuario como nombre, correo electrónico, dirección, edad y número de identificación emitido por el gobierno.
-
-Cómo manejar el KYC depende de ti: existen muchos servicios que ofrecen soluciones KYC mediante APIs e iFrames, validan los datos ingresados y sincronizan con bases de datos gubernamentales para verificar requisitos. Cada jurisdicción tiene requisitos específicos de KYC que difieren entre sí, por lo que es mejor encontrar un proveedor de KYC específico para tu país que satisfaga tus necesidades.
-
-Algunos países requieren diferentes campos de KYC dependiendo del monto a depositar o retirar. Si este es tu caso y necesitas adaptar tus formularios KYC según el monto del depósito o retiro, simplemente agrega un campo de cantidad antes del formulario KYC y asegúrate de que los campos KYC se actualicen según ese valor.
-
-La información KYC debe vincularse a la sesión creada a través de la [Autenticación Web Stellar](../sep10/README.mdx) y, por ende, al usuario, para que solo necesites solicitarla una vez. Después de completar el primer flujo de KYC, el usuario no debería tener que volver a ingresar la información.
-
-Asegúrate de que los mensajes de error y validación sean claros e incluyan instrucciones sobre qué hacer a continuación para garantizar una buena experiencia de usuario y aumentar la tasa de conversión de KYC. También deberías localizar los mensajes según el idioma y la ubicación del usuario.
-
-## Autocompletar el formulario KYC
-
-Autocompletar el formulario KYC es una excelente manera de reducir la fricción para comenzar a usar un anchor, y las wallets suelen proporcionar un conjunto de campos comúnmente usados en el ecosistema. En resumen, el anchor puede mostrar el formulario KYC con los valores del usuario que fueron enviados previamente por la wallet en los endpoints `/transactions/deposit/interactive` y `/transactions/withdraw/interactive`.
-
-Todos los campos del [SEP-9](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md) pueden ser enviados por las wallets en los endpoints mencionados, pero los más comunes son: correo electrónico, nombre, apellido y número de teléfono. También debes permitir que los campos prellenados sean editables, ya que el usuario podría haber ingresado un nombre diferente durante el proceso de registro de la wallet y podría querer editarlo antes de finalizar el proceso KYC del Anchor.
-
-Todos los datos SEP-9 enviados desde la wallet forman parte del [JWT interactivo](./faq.mdx#how-to-use-jwts), enviado por la Plataforma Anchor.
-
-## Conectando con Sistemas Bancarios Reales
-
-Los emisores de tokens respaldados por fiat deben mantener una reserva completa. Esto significa que existe una relación 1:1 entre los tokens de la red Stellar y el dinero en el banco. Dado que cada token fiat en Stellar está respaldado y puede canjearse por un activo real subyacente, los emisores de tokens fiat deben conectarse a los sistemas bancarios reales para validar depósitos de usuarios (a través de transferencias bancarias, pagos con tarjeta de crédito, etc.) y para completar retiros de usuarios (generalmente mediante transferencias bancarias). Si eres un anchor que procesa depósitos y retiros de un token emitido por otra organización, deberás seguir un proceso similar.
-
-Para obtener (e identificar) una transferencia de usuario, los emisores suelen usar una de dos aproximaciones:
-
-- Consulta API: esta opción consiste en consultar la API del banco, mediante un trabajo cron, para verificar el estado actualizado de la lista de transferencias recibidas por (y enviadas desde) la cuenta bancaria del emisor. Una vez que el sistema confirma una nueva transacción e identifica que corresponde a un depósito específico, puede enviar los fondos digitales a la cuenta del usuario.
-- Webhook: no todos los sistemas bancarios soportan esta opción, pero es la más ligera en términos de lógica back-end. En este enfoque, el banco notifica de forma proactiva el endpoint del emisor cuando recibe una nueva transferencia, actualizando esa información en la base de datos del emisor. El emisor puede entonces relacionar esa transacción con un depósito en proceso y validar que el usuario pueda recibir sus fondos digitales.
-
-Existen muchas formas de identificar que una transferencia bancaria específica corresponde a un depósito específico (y, por consiguiente, a un usuario). Algunos bancos (y países) tienen infraestructura de transferencias que permite la creación de una cuenta bancaria única por transferencia; otros requieren que los usuarios agreguen un parámetro de identificación en sus transferencias. Algunos bancos proporcionan el número de identificación del usuario en la información de la transacción para que los emisores puedan relacionarlo con la información proporcionada en el formulario KYC.
-
-Asegúrate de realizar una auditoría de seguridad completa en tus sistemas cuando las conexiones con sistemas bancarios estén activas. Algunos bancos ofrecen una API de pruebas que puede usarse para desarrollo y despliegue en entornos de testnet o staging, lo que permite probar y auditar la base de código antes de pasar a una integración bancaria final lista para producción. Por mayor seguridad, algunos anchors prefieren agregar un paso manual final antes de aprobar transferencias de retiro. En términos de experiencia de usuario, esta aprobación manual es aceptable siempre que los tiempos de espera se ajusten a las expectativas del usuario, lo cual usualmente significa que no sean mayores a un par de horas.
-
-## Probar casos extremos
-
-Una vez que tu aplicación esté completamente funcional, es buena idea probar distintos escenarios y casos extremos para asegurarte de que el sistema funciona como se espera. Aquí tienes una lista de sugerencias de pruebas que deberían cubrir gran parte de los casos extremos de la aplicación:
-
-### Pruebas generales
-
-- Prueba la usabilidad del flujo interactivo
-- Prueba la interfaz usando información de distintos locales y verifica que el contenido traducido, incluidos los mensajes de error, respuestas, formato de fechas y números, sea correcto
-
-### Pruebas KYC
-
-- Verifica que el KYC aparezca con una nueva clave secreta (SK) de la wallet
-- Verifica que KYC no acepte entradas con formato incorrecto y que los mensajes de error sean comprensibles
-- Verifica que puedas usar la misma información KYC (correo electrónico, número de teléfono, usuario, etc.) múltiples veces
-- Verifica que puedas realizar el proceso KYC múltiples veces con la misma clave secreta (SK) de Stellar.
-
-### Prueba interactiva
-
-- Verifica que el flujo de depósito funcione correctamente y que los sistemas bancarios estén operativos
-- Verifica que no puedas hacer un retiro por un valor mayor al saldo actual
-- Verifica que el flujo de retiro funcione correctamente y que los sistemas bancarios estén operativos
-
-### Pruebas de seguridad
-
-- Asegúrate de que los puntos finales de la plataforma estén asegurados
-
-## Pulir e internacionalización
-
-Soportar dos idiomas (inglés y el idioma del país de la moneda fiat) permite a los usuarios tener una experiencia fluida al navegar y apoya a instituciones internacionales (como wallets) que necesitan probar el producto antes de iniciar nuevas integraciones.
-
-Puedes soportar múltiples idiomas en tu aplicación web usando el parámetro `Accept-Language` de las cabeceras de las solicitudes HTTP para localizar el contenido y permitiendo a los usuarios cambiarlo de manera sencilla (por ejemplo, con un ícono de flag en la barra superior). Si una wallet específica no envía el parámetro en la cabecera, recomendamos mostrar al usuario una pantalla de selección de idioma al inicio de los procesos de depósito y retiro. Una vez que un usuario elige un idioma, puedes almacenar su selección para que solo tengas que preguntarle una vez. Además de localizar el texto, asegúrate de revisar el formato de números, fechas, etc.
-
-Tener un grupo de testers beta es una excelente manera de detectar casos extremos que necesitan ajustes y para confirmar que el sistema funciona correctamente ante una variedad de entradas de usuarios. Puedes realizar una prueba beta mediante una fase de lanzamiento suave antes de comenzar a invertir en marketing y distribución. Documentar el proceso de pruebas con capturas de pantalla y videos es muy útil para auditorías de seguridad futuras y brinda a nuevos socios y potenciales usuarios claridad y confianza en el producto.
-
-## Conexión con Wallets
-
-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.
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/README.mdx
deleted file mode 100644
index 8b44e79e7e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Pagos Transfronterizos (SEP-31)
-sidebar_position: 100
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-31 permite que las carteras y/o exchanges interactúen con el conjunto existente de servicios de envío de Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/configuration.mdx
deleted file mode 100644
index 887f6c5690..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/configuration.mdx
+++ /dev/null
@@ -1,346 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Modificar un archivo Stellar Info
-
-Comencemos modificando nuestro archivo `stellar.toml` creado [anteriormente][sep1-ap]. Las billeteras necesitan saber que la funcionalidad SEP-31 está admitida por tu negocio, y también necesitan conocer todas las monedas que admites.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-DIRECT_PAYMENT_SERVER = "http://localhost:8080/sep31"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que tendrás que crear otro archivo para tu despliegue en producción que use la frase de paso de la red pública, tus URLs de servicio de producción, tus cuentas de distribución y clave de firma de mainnet, así como las cuentas emisoras de mainnet de los activos que utiliza tu servicio.
-
-## Habilitar pagos transfronterizos
-
-Ahora estás listo para habilitar pagos transfronterizos con la API SEP-31. Especifica lo siguiente en tu archivo `dev.assets.yaml`.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep31:
-      enabled: true
-      quotes_supported: true
-      quotes_required: true
-      receive:
-        min_amount: 0
-        max_amount: 10000
-        methods:
-          - ACH
-```
-
-</CodeExample>
-
-La información proporcionada en los objetos `sep31` y `send` está estrechamente relacionada con la información que será expuesta a la aplicación billetera mediante el endpoint [`GET /info`][sep31-get-info] de SEP-31. La Anchor Platform también usa esta información para validar las solicitudes hechas a tu servicio. `sep31.fields.transaction` debe quedar vacío y será eliminado en una versión futura, pero puedes ajustar los valores `send.min_amount` y `send.max_amount` según los límites de tu servicio.
-
-Los valores `sep31.quotes_supported` y `sep31.quotes_required` determinan si las organizaciones que envían pueden y deben solicitar una tasa de cambio usando el endpoint [SEP-38 `POST /quote`][sep38-post-quote]. Casi todos los remitentes prefieren este enfoque para poder comunicar la tasa a sus clientes antes de continuar.
-
-Agrega la siguiente variable a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP31_ENABLED=true
-```
-
-</CodeExample>
-
-¡Ahora los remitentes deberían poder descubrir, autenticarse e iniciar transacciones con tu servicio! Ejecuta el siguiente comando para iniciar la Anchor Platform.
-
-<CodeExample>
-
-```bash
-docker compose up
-```
-
-</CodeExample>
-
-Verifica que tu API esté activa.
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep31/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente.
-
-<CodeExample>
-
-```json
-{
-  "receive": {
-    "USDC": {
-      "enabled": true,
-      "quotes_supported": true,
-      "quotes_required": true,
-      "min_amount": 0,
-      "max_amount": 10000,
-      "fields": {
-        "transaction": {}
-      }
-    }
-  }
-}
-```
-
-</CodeExample>
-
-## Habilitar la API KYC para clientes
-
-Los negocios necesitan recopilar y validar información KYC de los clientes para quienes facilitan transacciones. Los clientes determinan qué información KYC debe recopilarse y envían esa información mediante una API SEP-12 KYC alojada por la Anchor Platform, pero la Anchor Platform nunca almacena información personal identificable (PII). En cambio, reenvía las solicitudes de los clientes al servidor del negocio y devuelve las respuestas de este al cliente, actuando como un servidor proxy.
-
-Consulta la [especificación de la API KYC de Anchor Platform][platform-api-kyc] para detalles sobre los endpoints que debe implementar el servidor de tu negocio.
-
-Para poner esta API a disposición de los clientes, añadamos la URL del servicio a nuestro Archivo Stellar Info.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-KYC_SERVER = "http://localhost:8080/sep12"
-```
-
-</CodeExample>
-
-Vamos a habilitarla también en nuestro entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP12_ENABLED=true
-```
-
-</CodeExample>
-
-Finalmente, tenemos que definir los tipos de clientes de tu negocio. Cada tipo de cliente requiere un conjunto diferente de información KYC. Por ejemplo, puedes ofrecer tu servicio de pagos transfronterizos en dos jurisdicciones regulatorias diferentes, por lo que clientes en distintas jurisdicciones tienen diferentes requisitos KYC y serían representados usando distintos tipos.
-
-:::info
-
-Actualmente, los tipos de clientes deben ser mutuamente exclusivos, lo que significa que un cliente no puede ser más de un tipo.
-
-Esta limitación existe porque la Anchor Platform no puede validar si un cliente está aprobado para un tipo específico de transacción, como uno que envía una cantidad grande. Sólo puede validar que un cliente está aprobado para uno de los tipos de clientes definidos. Esta limitación será eliminada en una versión futura.
-
-:::
-
-En esta guía, solo tendremos dos tipos, un tipo de cliente remitente y un tipo de cliente receptor. Actualmente, nuestros tipos de clientes están definidos en nuestra configuración de activos, pero esto cambiará en una versión futura.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-sep31:
-  sep12:
-    sender:
-      types:
-        sep31-sender:
-          description: customers sending to recipients
-    receiver:
-      types:
-        sep31-receiver:
-          description: customers receiving from senders
-```
-
-</CodeExample>
-
-Vamos a hacer ping al endpoint info nuevamente para verificar. Después de `docker compose up`, ejecuta el siguiente comando:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep31/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente:
-
-<CodeExample>
-
-```json
-{
-  "receive": {
-    "USDC": {
-      "enabled": true,
-      "quotes_supported": true,
-      "quotes_required": true,
-      "min_amount": 0,
-      "max_amount": 10000,
-      "fields": {
-        "transaction": {}
-      }
-    }
-  }
-}
-```
-
-</CodeExample>
-
-## Habilitar la API RFQ
-
-Los negocios necesitan proporcionar a sus contrapartes del lado emisor una API de [Rate][get-rates-api] para verificar las tasas de exchange que ofrecen entre el activo en cadena utilizado para liquidación y el activo fiduciario usado para pagar al destinatario. Si la tasa es competitiva, los remitentes también deben poder solicitar un compromiso con la tasa ofrecida actualmente por el negocio por un corto período de tiempo.
-
-La Anchor Platform proporciona la [API SEP-38 RFQ][sep38] a los remitentes para este propósito.
-
-Para poner esta API a disposición de los clientes, añadamos la URL del servicio a nuestro Archivo Stellar Info.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-DIRECT_PAYMENT_SERVER = "http://localhost:8080/sep31"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-KYC_SERVER = "http://localhost:8080/sep12"
-QUOTE_SERVER = "http://localhost:8080/sep38"
-```
-
-</CodeExample>
-
-Vamos a habilitarla también en nuestro entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP38_ENABLED=true
-```
-
-</CodeExample>
-
-También necesitamos habilitar USDC para poder usarlo en esta API, así como agregar un activo off-chain con el que pueda ser exchangeado.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep31:
-      enabled: true
-      quotes_supported: true
-      quotes_required: true
-      receive:
-        min_amount: 0
-        max_amount: 10000
-        methods:
-          - ACH
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - iso4217:BRL
-      country_codes:
-        - BR
-  - id: iso421:BRL
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-      country_codes:
-        - BR
-      significant_decimals: 2
-      buy_delivery_methods:
-        - name: PIX
-          description: Have BRL sent directly to your bank account.
-```
-
-</CodeExample>
-
-¡Vamos a probar que tu API RFQ esté activa! Luego de `docker compose up`:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep38/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente:
-
-<CodeExample>
-
-```json
-{
-  "assets": [
-    {
-      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-    },
-    {
-      "asset": "iso4217:BRL",
-      "country_codes": ["BR"],
-      "buy_delivery_methods": [
-        {
-          "name": "PIX",
-          "description": "Have BRL sent directly to your bank account."
-        }
-      ]
-    }
-  ]
-}
-```
-
-</CodeExample>
-
-## Configurar autenticación para la API de Callback
-
-Así como tu negocio necesitará hacer solicitudes a la Anchor Platform, la Anchor Platform necesitará hacer solicitudes a tu negocio. Añadamos autenticación a estas solicitudes también.
-
-<CodeExample>
-
-```bash
-# dev.env
-CALLBACK_API_BASE_URL=http://server:8081
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-SECRET_CALLBACK_API_AUTH_SECRET=<your jwt encryption key>
-```
-
-</CodeExample>
-
-`CALLBACK_API_BASE_URL` usa `server` en lugar de `localhost` como host porque la Anchor Platform realizará solicitudes a tu servidor de negocio desde dentro de la red local creada por docker compose. Al configurar tu servicio en un entorno de staging o producción, asegúrate de actualizar tus URLs de servicio.
-
-Definiremos el servidor que implementa los endpoints definidos en la API de Callback en la siguiente sección.
-
-[sep31-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#get-info
-[sep1-ap]: ../sep1/README.mdx
-[get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
-[sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep38-post-quote]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#post-quote
-[platform-api-kyc]: ../../api-reference/callbacks/get-customer.api.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/getting-started.mdx
deleted file mode 100644
index 05e5dabe36..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/getting-started.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía te llevará a configurar e integrar con la Anchor Platform para construir un servicio receptor de pagos transfronterizos compatible con [SEP-31][sep-31], el protocolo estandarizado del ecosistema para pagos transfronterizos.
-
-Al aprovechar la admisión de la Anchor Platform para SEP-31, los negocios hacen su servicio compatible con el conjunto existente de servicios de envío de Stellar.
-
-:::info
-
-A medida que mejoremos la documentación, partes de esta guía relevantes para otros casos de uso podrán trasladarse a sus propias secciones.
-
-:::
-
-Antes de continuar con esta sección, asegúrate de haber [instalado][installation-ap] la Anchor Platform y configurado las funciones necesarias requeridas por SEP-31: [SEP-1 (Archivo de información de Stellar)][sep1-ap], [SEP-10 (Autenticación de Stellar)][sep10-ap] y [SEP-45 (Autenticación web de Stellar para cuenta de contrato)][sep45-ap].
-
-[sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/integration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/integration.mdx
deleted file mode 100644
index 7b01fc31e4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep31/integration.mdx
+++ /dev/null
@@ -1,620 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Integrar con la Anchor Platform para facilitar pagos transfronterizos implica implementar, como mínimo, lo siguiente:
-
-- Puntos finales API KYC [`GET /customer`][get-customer] y [`PUT /customer`][put-customer] para solicitar y recopilar datos KYC de los clientes
-- Punto final API RFQ [`GET /rate`][get-rate] para proveer tasas FX entre los activos on-chain y off-chain admitidos
-- Solicitudes `GET /transactions` para obtener actualizaciones sobre los estados de transacciones en la Anchor Platform (documentación próximamente)
-- Solicitudes [`JSON-RPC`][json-rpc-methods] para actualizar los estados de transacciones en la Anchor Platform
-
-Lo siguiente también puede ser requerido dependiendo de tu caso de uso:
-
-- [`DELETE /customer`][delete-customer] si tu negocio desea o debe permitir que los remitentes soliciten la eliminación de datos de clientes
-
-## Crear un Servidor Empresarial
-
-Primero, crea un servidor empresarial y agrégalo a nuestro archivo docker compose.
-
-<CodeExample>
-
-```yaml
-version: "3.8"
-
-services:
-  sep-server:
-    image: stellar/anchor-platform:latest
-    command: --sep-server
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-    ports:
-      - "8080:8080"
-    depends_on:
-      - db
-  platform-server:
-    image: stellar/anchor-platform:latest
-    command: --platform-server
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-    ports:
-      - "8085:8085"
-    depends_on:
-      - db
-
-  server:
-    build: .
-    ports:
-      - "8081:8081"
-    env_file:
-      - ./dev.env
-  db:
-    image: postgres:14
-    ports:
-      - "5432:5432"
-    env_file:
-      - ./dev.env
-```
-
-</CodeExample>
-
-Luego, crea un servidor web simple usando tu lenguaje de programación preferido y un `Dockerfile` que inicie el servidor. `docker compose up` debe iniciar correctamente los tres servicios.
-
-Esta guía no proporciona una implementación de ejemplo para los puntos finales, pero puedes encontrar más información sobre los esquemas de solicitud y respuesta en la [Referencia API Anchor Platform][ap-api], y las secciones siguientes ampliarán conceptos importantes para implementarlos.
-
-## Puntos finales de Callback de Cliente
-
-La Anchor Platform nunca almacena la información personal identificable (PII) de tus clientes, actuando en cambio como un servidor proxy entre las aplicaciones cliente y tu negocio, reenviando solicitudes y respuestas a la otra parte. Actualmente, las solicitudes y respuestas son casi idénticas a las definidas en la [especificación API KYC SEP-12][sep12].
-
-### Identificando Clientes
-
-Se pueden identificar los clientes usando dos enfoques.
-
-El primer enfoque utiliza una cuenta Stellar y memo. Al usar la Anchor Platform para facilitar pagos transfronterizos, la organización remitente usa su propia cuenta Stellar, la cual se usa para autenticarse vía [SEP-10 Stellar Authentication][ap-sep10], al registrar clientes con tu negocio. Los memos se utilizan para distinguir clientes únicos provenientes de la misma organización remitente.
-
-El segundo enfoque usa IDs de cliente generados por tu servicio. Por ejemplo, si una organización remitente registra un cliente, tu negocio recibirá una solicitud `PUT /customer` como la siguiente:
-
-<CodeExample>
-
-```json
-{
-  "account": "GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47",
-  "memo": "780284017",
-  "type": "sep31-sender",
-  "first_name": "John",
-  "last_name": "Doe",
-  "email": "johndoe@example.com"
-}
-```
-
-</CodeExample>
-
-En este ejemplo, la clave pública `GDJ...X47` identifica a la organización remitente, y el memo `780284017` identifica al cliente. Los memos suelen ser enteros de 64 bits, pero pueden ser otros tipos de datos, por lo que deben guardarse como cadenas. En respuesta, tu negocio debe devolver un ID de cliente.
-
-<CodeExample>
-
-```json
-{
-  "id": "fb5ddc93-1d5d-490d-ba5f-2c361cea41f7"
-}
-```
-
-</CodeExample>
-
-Tu servidor empresarial puede usar cualquier identificador para clientes mientras sea una cadena.
-
-Tras registrar un cliente, la organización remitente puede usar cualquiera de los enfoques para consultar el estado del cliente. Por ejemplo, podrías recibir una solicitud `GET /customer` como la siguiente:
-
-<CodeExample>
-
-```
-/customer?account=GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47&memo=780284017&type=sep31-sender
-```
-
-</CodeExample>
-
-O, la organización remitente podría usar el identificador que devolviste cuando registró originalmente al cliente.
-
-<CodeExample>
-
-```
-/customer?id=fb5ddc93-1d5d-490d-ba5f-2c361cea41f7&type=sep31-sender
-```
-
-</CodeExample>
-
-Tu negocio necesitará mantener una correspondencia entre la cuenta y memo usados para registrar originalmente al cliente y el ID que devuelves en la respuesta, además de los datos KYC proporcionados. En futuras iteraciones de la Anchor Platform, podríamos mantener esta correspondencia para tu negocio, de modo que solo tengas que trabajar con los IDs que generas.
-
-### Tipos de Cliente
-
-Tu negocio probablemente requiera diferentes conjuntos de información KYC según el tipo de cliente. Puedes definir las etiquetas para cada tipo de cliente en tu archivo `dev.assets.yaml`, y las organizaciones remitentes deben saber qué etiqueta usar al registrar o consultar el estado de clientes.
-
-En las solicitudes `PUT /customer`, debes usar el tipo enviado para evaluar si el remitente ha proporcionado todos los campos necesarios. En las solicitudes `GET /customer`, debes usar el tipo para determinar el estado del cliente.
-
-### Prueba con la Demo Wallet
-
-Puedes probar tu implementación con la [Stellar Demo Wallet][demo-wallet] siguiendo los pasos a continuación.
-
-1. Selecciona "Generar par de claves para cuenta nueva"
-2. Selecciona "Crear cuenta"
-3. Selecciona "Agregar Activo" e ingresa el código de activo y el dominio principal de la Anchor Platform, `localhost:8080`
-4. Selecciona "Agregar trustline"
-5. Fondea tu cuenta con un saldo del activo
-6. Selecciona "SEP-31 Enviar" en el menú desplegable
-
-Deberías ver que la demo wallet encuentra las URL de tu servicio, se autentica y verifica qué campos KYC debe recopilar. Luego presentará un formulario para que ingreses los datos KYC del remitente y receptor.
-
-[![demo wallet after initiating a transaction](../../assets/anchor-platform-sep31-demo-wallet-widget.png)](../../assets/anchor-platform-sep31-demo-wallet-widget.png)
-
-Una vez que ingreses la información solicitada, la enviará a la Anchor Platform, que a su vez la enviará a tu servidor empresarial. Cuando la demo wallet tenga los IDs de clientes que generaste, iniciará una transacción que debería fallar.
-
-## Punto final de callback de tasa
-
-Una vez que la organización remitente haya registrado a los clientes involucrados en la transacción, necesitará solicitar una cotización, o tasa FX, a tu negocio. La Anchor Platform solicita esta información a tu servidor empresarial usando el punto final [`GET /rate`][get-rate].
-
-### Cotizaciones Firmes vs. Indicativas
-
-Las solicitudes de cotización tendrán un parámetro `type` que será [`indicativo`][indicative] o [`firme`][firm]. Si `type=firm`, tu respuesta debe incluir el campo `id` y la fecha-hora `expires_at`, y reservar la liquidez necesaria para cumplir esta cotización hasta que expire. Si `type=indicative`, no regreses los campos `id` o `expires_at` porque la tasa proporcionada no será usada en una transacción.
-
-Ten en cuenta que el cliente puede solicitar que la cotización expire tras una fecha-hora específica usando el parámetro `expires_after`. Tu negocio debe respetar esta solicitud devolviendo un valor `expires_at` que sea en o después de la fecha-hora solicitada, o rechazar la petición con un error 400 Bad Request, que será reenviado al cliente.
-
-### Uso del ID de Cliente
-
-Las solicitudes pueden incluir un parámetro `client_id` que identifica a la organización remitente que solicita la tasa. Puedes usar este parámetro para aplicar los términos comerciales acordados con esa organización remitente, como ofrecer tasas con descuento. `client_id` podría no estar presente en solicitudes indicativas, en cuyo caso debes devolver tu precio de mercado. Actualmente, `client_id` será siempre la clave pública Stellar que la organización remitente usó para autenticarse con la Anchor Platform.
-
-### Métodos de Entrega
-
-Es común que las tasas y tarifas de los negocios difieran según las vías de pago usadas para enviar fondos al destinatario. Si tus métodos de entrega están configurados en tu archivo `asset.yaml`, los clientes siempre proporcionarán la vía de pago que desean que tu negocio use para solicitudes de cotización firme.
-
-Como este punto final solo se usa actualmente para pagos de remesas en activos off-chain, se utilizará `buy_delivery_method`. Si este punto final alguna vez se usa en otros flujos de transacción como depósitos SEP-24, también se podrá pasar `sell_delivery_method` para negocios que admitan esos tipos de transacciones.
-
-## Obteniendo Actualizaciones de Estado de Transacciones
-
-Para facilitar pagos transfronterizos, necesitarás poder detectar cuándo una organización remitente ha enviado a tu negocio un pago on-chain y determinar a qué transacción pertenecía ese pago.
-
-La forma más fácil de hacerlo es ejecutar el Stellar Observer, que detectará estos pagos y actualizará el registro de transacciones correspondiente con información sobre el pago. Tu negocio puede detectar estas actualizaciones consultando periódicamente el punto final `GET /transactions` de la API Platform.
-
-### Ejecutando el Stellar Observer
-
-El Stellar Observer monitorea el libro mayor de Stellar en busca de pagos hechos a tus cuentas y actualiza los registros de transacciones correspondientes con información del pago on-chain. Para ejecutar el observador, agrega lo siguiente a tu archivo docker compose.
-
-<CodeExample>
-
-```yaml
-services:
-  ...
-  observer:
-    image: stellar/anchor-platform:latest
-    command: --stellar-observer
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-```
-
-</CodeExample>
-
-### Consultando por Pagos Recibidos
-
-El Stellar Observer realiza solicitudes JSON-RPC a la API Platform cada vez que detecta pagos recibidos para transacciones iniciadas por organizaciones remitentes, actualizando así la fecha-hora `transfer_received_at` de la transacción.
-
-Tu negocio debe consultar periódicamente el punto final `GET /transactions` de la API Platform para detectar estas actualizaciones. Puedes referirte al siguiente ejemplo:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/transactions?sep=31&order_by=transfer_received_at&order=desc
-```
-
-</CodeExample>
-
-La respuesta incluirá una lista de transacciones de pagos transfronterizos iniciadas por organizaciones remitentes. Esta lista estará ordenada según el momento en que se recibió un pago para esa transacción. Por cada transacción devuelta, tu negocio debe verificar si ya ha detectado el pago correspondiente. Si lo ha hecho, has detectado todos los pagos realizados a tus cuentas.
-
-## Actualizando la Transacción vía JSON-RPC
-
-El diagrama de flujo SEP-31 define la secuencia/reglas de la transición del estado de la transacción y un conjunto de métodos JSON-RPC que deben llamarse para cambiar ese estado. No puedes definir el estado que deseas establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene los atributos requeridos, la Anchor Platform devolverá un error y no cambiará el estado de la transacción.
-
-[![sep31 flow](../../assets/sep31-transition-diagram.png)](../../assets/sep31-transition-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el flujo más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> indican que la transacción está en estado de error o ha expirado.
-
-:::
-
-Puedes crear una [plantilla][sep24-integration-make-json-rpc-request] para hacer solicitudes JSON-RPC a la Anchor Platform.
-
-Este capítulo también contiene información sobre el formato de [solicitud][sep24-integration-rpc-request]/[respuesta][sep24-integration-rpc-response] y [códigos de error][sep24-integration-error-codes] que podría devolver la Anchor Platform.
-
-### Listo para Recibir Fondos
-
-Las transacciones SEP-31 deberían estar inicialmente en estado `pending_receiver`. Para solicitar fondos del Anchor Remitente, el Anchor Receptor debería cambiar el estado de la transacción a `pending_sender` haciendo la siguiente solicitud RPC:
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-El estado de la transacción cambiará a `pending_sender`.
-
-### Fondos Recibidos
-
-Si el Anchor Remitente ha enviado los fondos, el Anchor Receptor debería cambiar el estado de la transacción a `pending_receiver` haciendo la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-El estado de la transacción cambiará a `pending_receiver`.
-
-### Fondos Offchain Enviados
-
-Para completar la transacción y cambiar su estado a `completed`, necesitas hacer una solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Fondos Offchain Pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago ha sido enviado a una red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Verificando Información del Cliente
-
-En algunos casos, el Anchor Receptor podría necesitar solicitar información actualizada al Anchor Remitente. Por ejemplo, el banco informa al Anchor Receptor que el nombre del cliente receptor proporcionado es incorrecto o le falta una inicial intermedia. Dado que esta información fue enviada vía SEP-12, la transacción debería pasar al estado `pending_customer_info_update` hasta que el Anchor Remitente haga otra solicitud SEP-12 `PUT /customer` para actualizarla. El Anchor Remitente puede verificar qué campos necesitan actualizarse haciendo una solicitud SEP-12 `GET /customer` incluyendo los parámetros de id o cuenta y memo. El Anchor Receptor debe responder con un estado `NEEDS_INFO` y el campo `last_name` incluido en los campos descritos.
-
-Después de que el Anchor Remitente haga una solicitud SEP-12 `PUT /customer`, llama al método JSON-RPC `notify_customer_info_updated` para actualizar el estado de la transacción. Además, llama a este método cada vez que el estado SEP-12 de un cliente cambie, por ejemplo cuando la información del cliente se esté validando y el estado cambie de `NEEDS_INFO` a `PROCESSING`. Esto asegura que cualquier cliente configurado con una URL de callback sea notificado del estado más reciente del cliente, permitiendo que el cliente solicite al usuario que actualice su información.
-
-<CodeExample>
-
-```json
-// notify-customer-info-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_customer_info_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Customer info updated",
-      "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
-      "customer_type": "sep31-receiver" // or sep31-sender
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh notify-customer-info-updated.json
-```
-
-</CodeExample>
-
-### Reembolso Enviado
-
-Existe la posibilidad de enviar todos los fondos de regreso al `Sending Anchor` (reembolso). Debes reembolsar la suma total (reembolso completo).
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::note
-
-No puedes hacer múltiples reembolsos en el flujo SEP-31. Por esta razón, el monto a reembolsar más la tarifa deben sumar `amount_in`. De lo contrario, obtendrás un error.
-
-:::
-
-### Error de Transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, es obligatorio establecer el estado de la transacción en `error`. Puedes usar el campo message para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario ha hecho una transferencia, deberías hacer una recuperación de transacción, y luego puedes reintentar procesar la transacción o iniciar un reembolso.
-
-:::
-
-### Transacción Expirada
-
-Tu negocio puede querer expirar aquellas transacciones que el usuario haya abandonado tras cierto tiempo. Es una buena práctica limpiar transacciones inactivas en estado `incomplete`. Para ello, simplemente cambia el estado de la transacción a `expired`.
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no puede usarse después de que el usuario haya hecho la transferencia.
-
-:::
-
-### Recuperación de Transacción
-
-El estado de la transacción puede cambiarse de `error/expired` a `pending-anchor`. Después de la recuperación, puedes reembolsar los activos recibidos o continuar con el procesamiento de la transacción. Para recuperar la transacción, es necesario hacer la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-### Configuración
-
-Puedes habilitar estos tipos de transacciones actualizando la configuración de tu archivo `assets.yaml`:
-
-<CodeExample>
-
-```yaml
-items:
-  - ...
-    sep31:
-      quotes_required: false
-```
-
-</CodeExample>
-
-[ap-api]: ../../README.mdx
-[ap-sep10]: ../sep10/README.mdx
-[sep12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[demo-wallet]: https://demo-wallet.stellar.org
-[indicative]: https://www.investopedia.com/terms/i/indicativequote.asp
-[firm]: https://www.investopedia.com/terms/f/firmquote.asp
-[get-customer]: ../../api-reference/callbacks/get-customer.api.mdx
-[put-customer]: ../../api-reference/callbacks/put-customer.api.mdx
-[get-rate]: ../../api-reference/callbacks/get-rates.api.mdx
-[put-customer-callback]: ../../api-reference/callbacks/put-customer.api.mdx
-[delete-customer]: ../../api-reference/callbacks/del-customer.api.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
-[sep24-integration-make-json-rpc-request]: ../sep24/integration.mdx#making-json-rpc-requests
-[sep24-integration-rpc-request]: ../sep24/integration.mdx#json-rpc-request
-[sep24-integration-rpc-response]: ../sep24/integration.mdx#json-rpc-response
-[sep24-integration-error-codes]: ../sep24/integration.mdx#error-codes
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep45/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep45/README.mdx
deleted file mode 100644
index d8cf10d66e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep45/README.mdx
+++ /dev/null
@@ -1,144 +0,0 @@
----
-title: Autenticación Stellar para Cuentas de Contrato (SEP-45)
-sidebar_position: 70
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-## Descripción general
-
-SEP-45 (Stellar Web Authentication for Contract Accounts) permite a las aplicaciones de billeteras inteligentes crear sesiones autenticadas con anchors de Stellar demostrando el control sobre una cuenta de contrato (`C...`). Una vez autenticadas, las billeteras reciben un JSON Web Token (JWT) que usan en solicitudes posteriores a los servicios estandarizados del anchor.
-
-Para la especificación completa, consulta [SEP-0045: Stellar Web Authentication for Contract Accounts][sep-45].
-
-La Anchor Platform implementa SEP-45 con soporte para:
-
-- **Flujo de Challenge/Response**: GET `/sep45/auth` para solicitar entradas de autorización, POST `/sep45/auth` para validar y recibir un JWT
-- **Autenticación de Cuenta de Contrato**: Soporte para cuentas de contrato (`C...`) usando entradas de autorización Soroban
-- **Simulación de Transacciones**: Simulación automática de transacciones para verificar entradas de autorización
-- **Múltiples Dominios Principales**: Soporte para múltiples dominios y patrones comodín
-
-:::info
-
-**SEP-45 vs SEP-10**: SEP-45 no reemplaza a SEP-10. SEP-45 admite cuentas de contrato (`C...`), mientras que SEP-10 admite cuentas clásicas (`G...`) y cuentas muxed (`M...`). Los servicios que deseen admitir todos los tipos de cuentas deben implementar ambos SEPs.
-
-:::
-
-## Flujo Típico de Autenticación
-
-1. El **Cliente** solicita un desafío único al **Servidor**
-2. El **Cliente** verifica y firma el desafío
-3. El **Cliente** envía el desafío firmado al **Servidor**
-4. El **Servidor** verifica el desafío y responde con un token de sesión JWT
-
-Se proporciona una implementación del contrato SEP-45 en el [repositorio Anchor Platform][sep-45-contract]. Una instancia de este contrato está desplegada en `CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX` en testnet.
-
-## Activar SEP-45
-
-SEP-45 requiere integración con Stellar RPC para simular transacciones. Anchor Platform puede conectarse al servidor Stellar RPC que elijas. Puedes usar un proveedor público de Stellar RPC o ejecutar el tuyo propio. Una lista de proveedores públicos se encuentra [aquí][rpc-providers].
-
-Para habilitar SEP-45, configura las siguientes variables de entorno en tu archivo `dev.env`.
-
-<CodeExample>
-
-```bash
-# dev.env
-STELLAR_NETWORK_TYPE=rpc
-STELLAR_NETWORK_RPC_URL=https://soroban-testnet.stellar.org
-SEP45_ENABLED=true
-SEP45_HOME_DOMAINS=localhost:8080
-SEP45_WEB_AUTH_CONTRACT_ID="CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP45_JWT_SECRET="a secret encryption key"
-```
-
-</CodeExample>
-
-### Configuración requerida (si está habilitada)
-
-| Variable                     | Predeterminado | Descripción                                                                                                                                                                                                  |
-| ---------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `STELLAR_NETWORK_TYPE`       | _Requerido_    | Debe establecerse en `rpc` para SEP-45. Esto habilita el modo RPC para Anchor Platform.                                                                                                                      |
-| `STELLAR_NETWORK_RPC_URL`    | _Requerido_    | La URL del servidor Stellar RPC utilizado para simulate transacciones. Puedes usar un proveedor público o ejecutar el tuyo propio. Puedes encontrar una lista de proveedores públicos [aquí][rpc-providers]. |
-| `SEP45_ENABLED`              | `false`        | Establece en `true` para habilitar la autenticación SEP-45                                                                                                                                                   |
-| `SEP45_HOME_DOMAINS`         | _Requerido_    | Lista de dominios principales (separados por comas). Admite patrones comodín como `*.stellar.org`. El `home_domain` debe coincidir con el host donde se sirve tu archivo `stellar.toml`.                     |
-| `SEP45_WEB_AUTH_CONTRACT_ID` | _Requerido_    | El ID del contrato del contrato SEP-45. Este contrato debe implementar la función `web_auth_verify` como se describe en la [especificación SEP-45][sep-45].                                                  |
-| `SECRET_SEP10_SIGNING_SEED`  | _Requerido_    | La clave privada correspondiente a la `SIGNING_KEY` en tu archivo `stellar.toml`. SEP-45 usa la misma clave de firma que SEP-10. Se usa para firmar los desafíos de autenticación.                           |
-| `SECRET_SEP45_JWT_SECRET`    | _Requerido_    | La clave de cifrado utilizada para firmar y verificar los tokens JWT emitidos a billeteras autenticadas.                                                                                                     |
-
-:::important
-
-- **Requisito RPC**: SEP-45 requiere Stellar RPC para simulate transacciones. Debes establecer `STELLAR_NETWORK_TYPE=rpc` y proporcionar una `STELLAR_NETWORK_RPC_URL` válida.
-- **ID del contrato**: El `SEP45_WEB_AUTH_CONTRACT_ID` debe coincidir con el contrato desplegado en la dirección especificada en el campo `WEB_AUTH_CONTRACT_ID` de tu archivo `stellar.toml`.
-- **Clave de firma**: La `SIGNING_KEY` en tu archivo `stellar.toml` debe ser la clave pública derivada de `SECRET_SEP10_SIGNING_SEED`.
-
-:::
-
-### Configuración opcional
-
-<CodeExample>
-
-```bash
-# dev.env
-# Optional: Specify web_auth_domain (default: first home_domain if only one is specified)
-SEP45_WEB_AUTH_DOMAIN=localhost:8080
-
-# Optional: Challenge timeout in seconds (default: 900)
-SEP45_AUTH_TIMEOUT=900
-
-# Optional: JWT token timeout in seconds (default: 86400 = 24 hours)
-SEP45_JWT_TIMEOUT=86400
-```
-
-</CodeExample>
-
-| Variable                | Predeterminado                                                        | Descripción                                                                                                                                                                           |
-| ----------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SEP45_WEB_AUTH_DOMAIN` | Primer `home_domain` si se especifica solo uno, de lo contrario vacío | La propiedad `web_auth_domain` utilizada en las respuestas SEP-45. Requerido si tienes múltiples `home_domains` o usas patrones comodín. Debe coincidir con el host del servidor SEP. |
-| `SEP45_AUTH_TIMEOUT`    | `900`                                                                 | Tiempo en segundos que un desafío permanece válido. Los clientes deben firmar y enviar las entradas de autorización dentro de este período.                                           |
-| `SEP45_JWT_TIMEOUT`     | `86400`                                                               | Tiempo en segundos que un token JWT emitido permanece válido. Después de la caducidad, los clientes deben autenticarse nuevamente.                                                    |
-
-:::tip
-
-**Múltiples dominios principales**: Si especificas múltiples `home_domains` (por ejemplo, `ap.stellar.org,*.sdp.stellar.org`), también debes establecer `SEP45_WEB_AUTH_DOMAIN` para indicar qué dominio aloja el endpoint de autenticación.
-
-:::
-
-## Configurar stellar.toml
-
-Actualiza tu archivo `stellar.toml` para anunciar soporte para SEP-45. Las billeteras descubren tu endpoint de autenticación a través de este archivo.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here (public key from SECRET_SEP10_SIGNING_SEED)"
-WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
-WEB_AUTH_CONTRACT_ID = "CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-```
-
-</CodeExample>
-
-Estos campos deben coincidir con las opciones de configuración establecidas en la sección [Habilitar SEP-45](#enable-sep-45) arriba.
-
-`WEB_AUTH_FOR_CONTRACTS_ENDPOINT` - La URL donde se ejecuta el servicio de autenticación. Esta es la URL que los clientes usarán para autenticarse con el anchor. El endpoint debe admitir:
-
-- `GET <WEB_AUTH_FOR_CONTRACTS_ENDPOINT>` - Solicitar entradas de autorización
-- `POST <WEB_AUTH_FOR_CONTRACTS_ENDPOINT>` - Intercambiar entradas de autorización firmadas por JWT de sesión
-
-`WEB_AUTH_CONTRACT_ID` - El ID del contrato del contrato SEP-45. Este es el contrato que se usará para construir el desafío. El contrato debe implementar la función `web_auth_verify` como se describe en la [especificación SEP-45][sep-45]. Esto debe coincidir con `SEP45_WEB_AUTH_CONTRACT_ID`.
-
-:::important
-
-- **`SIGNING_KEY`**: Debe ser la clave pública derivada de `SECRET_SEP10_SIGNING_SEED`
-- **`WEB_AUTH_FOR_CONTRACTS_ENDPOINT`**: Usa `https://` en producción. La ruta `/sep45/auth` es el endpoint estándar de SEP-45.
-- **Coincidencia de host**: El host en `WEB_AUTH_FOR_CONTRACTS_ENDPOINT` debe coincidir con uno de tus `SEP45_HOME_DOMAINS` (o con `SEP45_WEB_AUTH_DOMAIN` si se especifica).
-
-:::
-
-[sep1-ap]: ../sep1/README.mdx
-[sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
-[sep-45-contract]: https://github.com/stellar/anchor-platform/tree/main/soroban/contracts/web-auth
-[rpc-providers]: /docs/data/apis/rpc/providers
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/README.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/README.mdx
deleted file mode 100644
index cca0608278..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Depósitos y Retiros Programáticos (SEP-6)
-sidebar_position: 80
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-6 permite que las billeteras y/o exchanges interactúen con un anchor en nombre de los usuarios, sin que el usuario tenga que interactuar directamente con la rampa de entrada y salida.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/configuration.mdx
deleted file mode 100644
index 1e8eb8b347..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/configuration.mdx
+++ /dev/null
@@ -1,256 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-# Configuración
-
-Para habilitar depósitos y retiros SEP-6, la Plataforma Anchor debe configurarse para hacer lo siguiente:
-
-- Proporcionar las URLs del servicio necesarias para los puntos finales SEP-6, 12 y 38 en el archivo `stellar.toml`
-- Proporcionar información sobre los activos onchain y offchain, así como las vías de pago, que tu negocio soporta mediante los puntos finales SEP-6 y SEP-38 `/info`
-- Soportar los endpoints y callbacks necesarios para solicitar información KYC y proporcionar tasas de cambio
-
-## Habilitar Depósitos y Retiros Programáticos
-
-Agrega las siguientes variables a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_ENABLED=true
-SEP12_ENABLED=true
-SEP38_ENABLED=true
-```
-
-</CodeExample>
-
-### Modificar un Archivo de Información Stellar
-
-Vamos a modificar el archivo `stellar.toml` creado [anteriormente][sep1-ap]. Las billeteras necesitan saber que la funcionalidad SEP-6 está soportada por tu negocio, y también necesitan conocer todos los activos Stellar que soportas.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-TRANSFER_SERVER = "http://localhost:8080/sep6"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-KYC_SERVER = "http://localhost:8080/sep12"
-ANCHOR_QUOTE_SERVER = "http://localhost:8080/sep38"
-
-# Add support for USDC
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que necesitarás crear otro archivo para tu despliegue en producción que use la frase de paso de la red pública, tus URLs de servicio de producción, tus cuentas de distribución Mainnet y clave de firma, así como las cuentas emisoras Mainnet de los activos que tu servicio utilice.
-
-### Modificar el Archivo de Configuración de Activos
-
-Ahora estás listo para especificar lo siguiente en tu archivo `dev.assets.yaml` y cambiar los valores según tu caso de uso. Este archivo de ejemplo habilita el soporte para USDC de Circle y un USD fiat para depositar y retirar.
-
-Los métodos especificados en las secciones `sep38` son los que expondrá el endpoint SEP-38 [`GET /info`][sep38].
-
-Los métodos especificados en las secciones `deposit` y `withdraw` son los que expondrá el endpoint SEP-6 [`GET /info`][sep-6]. Los métodos listados deben coincidir con los definidos en la sección SEP-38 del archivo.
-
-También observa que los activos fiat, aquellos con `schema: iso4217`, no necesitan los objetos de configuración `sep6_enabled`, `deposit` o `withdraw` especificados. De igual forma, los activos Stellar, aquellos con `schema: stellar`, no necesitan los objetos de configuración `sep38.sell_delivery_methods` ni `sep38.buy_delivery_methods` especificados.
-
-<CodeExample>
-
-```yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep6:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - ACH
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - ACH
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - iso4217:USD
-  - id: iso4217:USD
-    significant_decimals: 2
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-      buy_delivery_methods:
-        - name: ACH
-          description: ACH debits for US bank accounts
-      sell_delivery_methods:
-        - name: ACH
-          description: ACH credit for US bank accounts
-```
-
-</CodeExample>
-
-### Administrar Cuentas de Distribución
-
-Observa que en el ejemplo anterior se lista un atributo `distribution_account` para la entrada USDC. Si se especifica, esta cuenta será proporcionada junto con un memo generado aleatoriamente y único por transacción a los clientes como la dirección a la que enviar fondos para las transacciones de retiro. El memo de la transacción es cómo tú o la Plataforma Anchor coincidirán los fondos recibidos con un registro de transacción en la base de datos de la Plataforma Anchor.
-
-Si no tienes una cuenta Stellar propia y usas un tercero que te proporciona una cuenta Stellar y memo para que puedan recibir fondos en tu nombre, como un exchange o custodio, deberías omitir el campo `distribution_account` de tu archivo de configuración de activos. En su lugar, necesitarás proporcionar la cuenta Stellar y memo que deseas usar para recibir fondos mediante una solicitud al [`request_onchain_funds`][request-onchain-funds] de la Plataforma Anchor por cada transacción.
-
-Para configurar la Plataforma Anchor para que espere que la cuenta Stellar y el memo se proporcionen vía API en lugar de configurarse mediante el archivo de activos, especifica la siguiente variable de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=none
-```
-
-</CodeExample>
-
-### Habilitar Callbacks al Servidor del Negocio
-
-Los negocios necesitan recopilar y validar información KYC de los clientes para quienes facilitan transacciones. Los clientes preguntan a tu negocio qué información KYC debe recopilarse y envían esa información a través de la API KYC SEP-12 hospedada por la Plataforma Anchor, pero la Plataforma Anchor nunca almacena información personal identificable (PII). En su lugar, reenvía las solicitudes de los clientes al servidor del negocio y devuelve las respuestas del negocio al cliente, actuando como un servidor proxy.
-
-Además, los negocios necesitan proporcionar a los clientes una API de [Tasas][get-rates-api] para consultar las tasas de cambio que ofrecen entre los activos onchain y offchain soportados por el negocio. Si la tasa es competitiva, los clientes también deben poder solicitar un compromiso con la tasa que el negocio ofrece por un período corto de tiempo. De manera similar a la API KYC, la Plataforma Anchor realiza solicitudes a tu servidor de negocio para obtener tasas de cambio y cotizaciones, y las devuelve a los clientes.
-
-Para habilitar estas solicitudes a tu servidor del negocio, primero deberás agregar tu servidor del negocio al archivo docker compose. Luego, para soportar solicitudes hacia tu servidor desde la Plataforma Anchor, necesitas habilitar los callbacks.
-
-<CodeExample>
-
-```bash
-# dev.env
-CALLBACK_API_BASE_URL=http://business-server:3000/callbacks
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
-SECRET_CALLBACK_API_AUTH_SECRET="a secret used to sign JWTs"
-```
-
-</CodeExample>
-
-Lo anterior indica a la Plataforma Anchor que incluya un [JWT][how-to-use-jwt], firmado con el secreto configurado, en el encabezado `Authorization` de las solicitudes hechas a `/callbacks/<callback endpoint>` para que tu servidor pueda autenticar la Plataforma Anchor antes de procesar las solicitudes.
-
-Consulta la [API KYC][platform-api-kyc] y la [API de Tasas][get-rates-api] para detalles sobre los puntos finales que deben implementarse en tu servidor del negocio.
-
-### Configuración Adicional Opcional
-
-`more_info_url` es una URL opcional proporcionada por tu servidor del negocio para que las aplicaciones de billetera muestren información sobre transacciones iniciadas previamente. Esta URL es típicamente usada por las billeteras en sus vistas de historial de transacciones, y tu negocio puede especificar la información a mostrar acerca de la transacción.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP6_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-```
-
-</CodeExample>
-
-Los negocios pueden establecer una fecha límite para acciones del usuario sobre transacciones mediante el campo `user_action_required_by`. Para ejemplos, consulta los [Métodos JSON-RPC][json-rpc-methods]. Además, el parámetro `initial_user_deadline_seconds` establece un tiempo por defecto (en segundos) que tiene el usuario para actuar antes de que la transacción pase al estado `EXPIRED`.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_INITIAL_USER_DEADLINE_SECONDS=1209600
-```
-
-</CodeExample>
-
-## Probar con la Billetera Demo
-
-Las billeteras ahora deberían poder descubrir, autenticar y comenzar transacciones con tu servicio. Tu proyecto y archivos fuente ahora deberían verse algo así.
-
-<CodeExample>
-
-```
-├── dev.env
-├── docker-compose.yaml
-├── config
-│   ├── dev.assets.yaml
-│   ├── dev.stellar.toml
-```
-
-</CodeExample>
-
-Tu entorno ahora debería verse similar al siguiente.
-
-<CodeExample>
-
-```bash
-# dev.env
-ASSETS_TYPE=file
-ASSETS_VALUE=/home/dev.assets.yaml
-
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/home/dev.stellar.toml
-
-SEP6_ENABLED=true
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=none
-SEP6_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP6_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-
-SEP10_ENABLED=true
-SEP10_HOME_DOMAIN=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret used to sign JWTs"
-
-SEP12_ENABLED=true
-
-SEP38_ENABLED=true
-
-CALLBACK_API_BASE_URL=http://business-server:3000/callbacks
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
-SECRET_CALLBACK_API_AUTH_SECRET="a secret used to sign JWTs"
-```
-
-</CodeExample>
-
-Para probar esto, ve a la [Billetera Demo Stellar][stellar-demo-wallet].
-
-Inicia una transacción de depósito haciendo lo siguiente:
-
-- Crear un nuevo par de claves
-- Haz clic en el botón "Add Asset" e ingresa
-  - el código del activo Stellar en tu archivo `stellar.toml`
-  - tu dominio principal, `localhost:8080`
-- Selecciona el desplegable y haz clic en "SEP-6 Deposit", luego haz clic en "Start"
-
-La billetera demo debería poder encontrar tu archivo `stellar.toml`, autenticar usando el par de claves Stellar que acabas de crear e iniciar una transacción.
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep1-ap]: ../sep1/README.mdx
-[stellar-demo-wallet]: https://demo-wallet.stellar.org/
-[get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
-[sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[platform-api-kyc]: ../../api-reference/callbacks/get-customer.api.mdx
-[request-onchain-funds]: ../../api-reference/platform/rpc/methods/request_onchain_funds.mdx
-[how-to-use-jwt]: ../sep24/faq.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/getting-started.mdx
deleted file mode 100644
index d7b57a6a84..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/getting-started.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía te guiará a través de la configuración e integración con Anchor Platform con el propósito de desarrollar un servicio de acceso y salida compatible con [SEP-6][sep-6], el protocolo estandarizado del ecosistema para depósitos y retiradas de fondos programáticos.
-
-Aprovechando el soporte de Anchor Platform para SEP-6, las empresas ofrecen su propio servicio de acceso y salida como una experiencia dentro de la aplicación a través de aplicaciones basadas en Stellar, como billeteras y exchange, ampliando su alcance y conectándose con los usuarios mediante las aplicaciones que ya usan.
-
-Antes de continuar con esta sección, asegúrate de que ya has [instalado][installation-ap] Anchor Platform y configurado las funcionalidades necesarias requeridas por SEP-6: [SEP-1 (Stellar Info File)][sep1-ap], [SEP-10 (Stellar Authentication)][sep10-ap] y [SEP-45 (Stellar Web Authentication for contract account)][sep45-ap].
-
-## La experiencia básica del usuario
-
-La experiencia completa del cliente para un depósito o retirada utilizando SEP-6 es la siguiente:
-
-1. El cliente abre la aplicación de billetera SEP-6 de su elección
-2. El cliente selecciona un activo para depositar y la billetera encuentra un anchor (los clientes también podrían elegir el anchor específico)
-3. Una vez que la billetera se autentica con el anchor, el cliente empieza a ingresar su información KYC y datos de la transacción solicitados por el anchor
-4. La billetera proporciona instrucciones, y el cliente deposita moneda fiduciaria real con el anchor (como transferencia bancaria)
-5. Una vez que la billetera recibe el depósito, el cliente recibe el activo tokenizado en la red Stellar desde la cuenta de distribución del anchor
-
-Luego, el cliente puede usar el activo digital en la red Stellar para remesas, pagos, comercio, almacén de valor u otro caso de uso no listado aquí. En una fecha posterior, el cliente podría decidir retirar sus activos de la red Stellar, lo cual sería algo así:
-
-1. El cliente abre su aplicación de billetera
-2. El cliente selecciona el activo para retirada y la billetera encuentra el anchor
-3. Después de autenticarse con el anchor, el cliente puede ingresar la información de la transacción y cualquier otra información KYC adicional que no se haya recopilado aún
-4. Luego de pedir la aprobación del cliente, la billetera envía la cantidad especificada del saldo del activo del cliente a la cuenta de distribución del anchor en Stellar
-5. Una vez que el anchor recibe el pago, el cliente recibe los fondos retirados mediante cualquier método admitido por el anchor (como transferencia bancaria)
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/integration.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/integration.mdx
deleted file mode 100644
index 40b1a28719..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep6/integration.mdx
+++ /dev/null
@@ -1,899 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-import { AttributeTable } from "@site/src/components/AttributeTable";
-import Security from "../../admin-guide/component/security/security.mdx";
-import UsingApiKey from "../../admin-guide/component/security/api_key.mdx";
-import UsingJwt from "../../admin-guide/component/security/jwt.mdx";
-import Rpc from "../../admin-guide/component/rpc/rpc.mdx";
-import RpcRequest from "../../admin-guide/component/rpc/request.mdx";
-import RpcResponse from "../../admin-guide/component/rpc/response.mdx";
-import RpcError from "../../admin-guide/component/rpc/error.mdx";
-import Observer from "../../admin-guide/component/observer/observer.mdx";
-
-Uno de los principales puntos de interacción con la Plataforma Anchor es notificar a la Plataforma sobre eventos relacionados con transacciones.
-
-En general, querrás proporcionar actualizaciones para los siguientes eventos.
-
-- Tu negocio requiere que el usuario envíe información KYC para procesar una transacción
-- Tu negocio actualizó las cantidades de entrada/salida/tarifa para una transacción
-- Tu negocio está listo para recibir fondos del usuario
-- Tu negocio ha recibido fondos del usuario
-- Tu negocio ha enviado fondos al usuario
-- Tu negocio ha procesado un reembolso para la transacción del usuario
-- Tu negocio experimentó un error inesperado
-
-Esto se hace realizando solicitudes JSON-RPC al endpoint de la API de la Plataforma. Las solicitudes JSON-RPC te permiten actualizar el estado de la transacción. Para mover la transacción a un estado específico, es necesario hacer la solicitud JSON-RPC correspondiente y pasar los datos que requiere el método RPC.
-
-La API JSON-RPC de la Plataforma Anchor está diseñada para notificar a la plataforma sobre cambios en el estado de la transacción. Por ello, la API se llamará cada vez que un usuario o el anchor realice una acción que avance el estado de la transacción en el flujo.
-
-La comunicación desde la Plataforma Anchor sobre actualizaciones de transacciones, actualizaciones de clientes y creación de cotizaciones se maneja a través del servicio de eventos. Esta es una función opcional que debe configurarse por separado de la integración SEP-6. Para más información, consulta [Manejo de Eventos][event-handling].
-
-Puedes obtener más información sobre el flujo de transacciones y estados en el [documento del protocolo SEP-6][sep-6].
-
-## callbacks
-
-La Plataforma Anchor depende del servidor del negocio para proporcionar y almacenar información sobre clientes y cotizaciones.
-
-### Información del Cliente
-
-La Plataforma Anchor no almacena información del cliente. En su lugar, reenvía todas las solicitudes SEP-12 de clientes al servidor del negocio. El servidor del negocio es responsable de almacenar y gestionar esta información. Por lo tanto, tu servidor del negocio debe implementar las [APIs de cliente][customer-callback] para manejar actualizaciones KYC.
-
-### Cotizaciones y Tarifas
-
-Para soportar el intercambio de activos no equivalentes, la Plataforma Anchor expone una API compatible con SEP-38 para proporcionar cotizaciones para el intercambio. La API de cotizaciones se usa para ofrecer al usuario la cantidad esperada del activo que recibirá a cambio del activo que envía. La API de cotizaciones también se usa para proporcionar al usuario las tarifas esperadas para la transacción. Por lo tanto, tu servidor del negocio debe implementar la [API de tasas][rate-callback] para proveer cotizaciones a la Plataforma Anchor.
-
-## Asegurar la API de la Plataforma
-
-<Security />
-
-### Uso de clave API
-
-<UsingApiKey />
-
-### Uso de JWT
-
-<UsingJwt />
-
-## Realizar solicitudes JSON-RPC
-
-<Rpc />
-
-### Solicitud JSON-RPC
-
-<RpcRequest />
-
-### Respuesta JSON-RPC
-
-<RpcResponse />
-
-### Códigos de error
-
-<RpcError />
-
-## Actualizar transacción de depósito (exchange) vía JSON-RPC
-
-El diagrama del flujo de depósito SEP-6 define las secuencias/reglas de transición de estado de la transacción y un conjunto de métodos JSON-RPC que se deben llamar para cambiar ese estado. No puedes definir el estado que quieres establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene los atributos requeridos, la Plataforma Anchor devolverá un error y no cambiará el estado de la transacción.
-
-El flujo de depósito de exchange es el mismo que el flujo de depósito, excepto que no será necesario recalcular las cantidades al solicitar fondos offchain, si el usuario ha proporcionado una cotización firme del anchor.
-
-[![flujo de depósito sep6](../../assets/sep6-deposit-flow-diagram.png)](../../assets/sep6-deposit-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden ser omitidos.
-
-Los estados en <span style={{color: "red"}}>rojo</span> indican que la transacción está en un estado de error o que ha expirado.
-
-:::
-
-### Verificación de Información KYC
-
-Aunque la Plataforma Anchor no requiere que un cliente haya recopilado su información KYC antes de iniciar un depósito, tu negocio puede querer recopilar esta información antes de que el cliente realice la transferencia. Al escuchar eventos de transacción creada o mediante el sondeo del endpoint [`GET /transactions`][get-transactions], puedes determinar si una transacción requiere que el cliente actualice su información. Los campos SEP-9 requeridos pueden comunicarse al usuario devolviendo un estado `NEEDS_INFO` con los campos obligatorios en el atributo `fields`.
-
-Después de que el usuario haya enviado su información KYC, llama al método JSON-RPC `notify_customer_info_updated` para actualizar el estado de la transacción. Además, llama a este método siempre que el estado SEP-12 de un cliente cambie, como cuando la información del cliente está siendo validada y el estado cambia de `NEEDS_INFO` a `PROCESSING`. Esto asegura que cualquier cliente configurado con una URL de callback reciba la notificación del último estado del cliente, permitiendo que el cliente solicite al usuario que actualice su información.
-
-<CodeExample>
-
-```json
-// notify-customer-info-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_customer_info_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Customer info updated",
-      "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
-      "customer_type": "sep6-deposit" // or sep6-withdrawal
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh notify-customer-info-updated.json
-```
-
-</CodeExample>
-
-### Listo para Recibir Fondos
-
-Después de que el usuario haya enviado su información KYC, el anchor puede notificar a la Plataforma que está listo para recibir fondos. El anchor debe usar el RPC `request_offchain_funds` para proporcionar las cantidades finales al usuario. Para hacer esto, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-offchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_offchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request offchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "instructions": {
-        "organization.bank_number": {
-          "value": "123456789",
-          "description": "US Bank routing number"
-        },
-        "organization.bank_account_number": {
-          "value": "123456789",
-          "description": "US Bank account number"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es la cantidad que el usuario debe enviar al negocio.
-- `amount_out` es la cantidad que el usuario recibirá.
-- `fee_details` es el total de tarifas cobradas por el negocio.
-- `asset` es parte del campo `amount_x` y está en formato SEP-38. En este ejemplo, está configurado en USD, asumiendo que el usuario hizo una transferencia bancaria al sistema usando USD.
-- `instructions` es el conjunto de campos estándar SEP-9 que el usuario debe usar para enviar fondos al negocio. En este ejemplo, el usuario debe enviar fondos a la cuenta bancaria con el número de ruta `123456789` y número de cuenta `123456789`.
-
-La información sobre montos (entrada/salida/tarifa) es requerida si quieres mover la transacción al estado `pending_user_transfer_start`.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-offchain-funds.json
-```
-
-</CodeExample>
-
-:::caution
-
-Para depósitos de exchange con una cotización firme (la solicitud está asociada con un `quote_id`), no deben proporcionarse cantidades.
-
-:::
-
-### Fondos Recibidos
-
-Si se recibieron fondos offchain, querrás proporcionar información actualizada de la transacción.
-
-<CodeExample>
-
-```json
-// offchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds received",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `funds_received_at` es la fecha y hora de recepción de los fondos.
-- `external_transaction_id` es el ID de la transacción en la red externa.
-
-Los campos de cantidades son opcionales. Si se omiten, se usarán los valores previos a esta solicitud.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-received.json
-```
-
-</CodeExample>
-
-### Esperando Fondos del Usuario
-
-En el mundo real, el proceso de confirmación de la transferencia puede tomar tiempo. En tales casos, las transacciones deben establecerse en un nuevo estado que indique que se ha recibido la confirmación de la transferencia pero que los fondos aún no han sido recibidos.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Enviando Fondos Onchain
-
-A continuación, envía una transacción en la red Stellar para cumplir con el depósito del usuario. Después de que la transacción Stellar haya sido enviada, es necesario enviar la solicitud JSON-RPC `notify_onchain_funds_sent` para notificar al usuario que los fondos fueron enviados con éxito.
-
-<CodeExample>
-
-```json
-// onchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds sent",
-      "stellar_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `stellar_transaction_id` es el ID de la transacción en la red Stellar de la transferencia.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-sent.json
-```
-
-</CodeExample>
-
-Después de esta solicitud JSON-RPC, la transacción se transferirá al estado `completed`.
-
-### Confianza Pendiente
-
-Este estado debe establecerse si un pago requiere una trustline de activo que no fue configurada por el usuario. Existen dos formas en que la transacción puede moverse al estado `pending_trust`. La primera es cuando el servidor de negocios detecta que la trustline no está configurada. La segunda es cuando el negocio detecta que falta la trustline y desea notificar al usuario que debe configurarla. Para mover la transacción al estado `pending_trust`, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-trust.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_trust",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine not configured"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-trust.json
-```
-
-</CodeExample>
-
-:::info
-
-El sistema de procesamiento de pagos verifica periódicamente si la trustline se configuró. Si lo estuvo, enviará automáticamente un pago y cambiará el estado de la transacción a `pending_stellar`.
-
-:::
-
-### Confianza Establecida
-
-Este estado debe establecerse si el negocio detectó que la trustline fue o no configurada por el usuario.
-
-<CodeExample>
-
-```json
-// trust-set.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_trust_set",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine set",
-      "success": "true"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- bandera `success` que define si la trustline fue configurada o no por el usuario
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh trust-set.json
-```
-
-</CodeExample>
-
-:::info
-
-Dependiendo de la bandera `success`, el estado de la transacción cambiará a `pending_stellar` si la trustline fue establecida, o a `pending_anchor` si no lo fue.
-
-:::
-
-### Reembolso Enviado
-
-A veces es necesario devolver fondos al usuario (reembolso). Puedes reembolsar la suma completa (reembolso total) o hacer un conjunto de reembolsos parciales al `source_account` usando el `refund_memo` y el `refund_memo_type` asociados con la transacción si están presentes. Además, si el usuario envió más dinero del esperado, puedes reembolsar una parte de la suma al usuario y enviar el resto como fondos onchain.
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "fee_details": {
-          "total": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::info
-
-Si la suma de los reembolsos es menor que `amount_in`, el estado de la transacción se establecerá en `pending_anchor`. Solo si la suma de los reembolsos es igual a `amount_in`, el estado de la transacción se establecerá en `refunded`.
-
-:::
-
-### Reembolso Pendiente
-
-Esto es similar a [Reembolso Enviado](#refund-sent), pero maneja el caso cuando un reembolso ha sido enviado a una red externa pero aún no está confirmado. El estado de la transacción se establece en `pending_external`. Este es el estado que se establecerá al esperar que Bitcoin u otra red externa de criptomonedas complete una transacción, o al esperar una transferencia bancaria.
-
-### Error de Transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, es necesario establecer el estado de la transacción en `error`. Puedes usar el campo de mensaje para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario ha hecho una transferencia, deberías hacer una recuperación de transacción, y luego puedes reintentar procesarla o iniciar un reembolso.
-
-:::
-
-### Transacción Expirada
-
-Tu negocio puede querer manejar las transacciones abandonadas expirándolas si permanecen inactivas durante cierto período. Para lograr esto, verifica el estado de la transacción usando el endpoint `GET /transactions` y ordena los resultados por la marca de tiempo `user_action_required_by`. Si la marca de tiempo ha pasado, ejecuta manualmente la lógica apropiada, como expirar la transacción o iniciar un reembolso automático, según el estado actual de la transacción.
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no puede usarse después de que el usuario haya hecho una transferencia.
-
-:::
-
-### Recuperación de Transacción
-
-El estado de la transacción puede cambiar de `error/expired` a `pending_anchor`. Después de la recuperación, puedes reembolsar los activos recibidos o seguir procesando la transacción. Para recuperar una transacción, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-## Actualizar transacción de retiro (exchange) vía JSON-RPC
-
-El diagrama del flujo de retiro SEP-6 define la secuencia/reglas de transición del estado de la transacción. No puedes definir el estado que quieres establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene los atributos requeridos, la Plataforma Anchor devolverá un error y no cambiará el estado de la transacción.
-
-El flujo de retiro de exchange es el mismo que el flujo de retiro, excepto que no será necesario recalcular las cantidades al solicitar fondos onchain, si el usuario ha proporcionado una cotización firme del anchor.
-
-[![flujo de retiro sep6](../../assets/sep6-withdrawal-flow-diagram.png)](../../assets/sep6-withdrawal-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden ser omitidos.
-
-Los estados en <span style={{color: "red"}}>rojo</span> indican que la transacción está en un estado de error o que ha expirado.
-
-:::
-
-Una vez que el flujo de retiro ha finalizado, implementar el retiro es sencillo. Algunas partes del flujo son similares y pueden reutilizarse.
-
-El punto de partida tanto para retiro como para depósito es el mismo.
-
-### Listo para Recibir Fondos
-
-De forma similar al depósito, el paso después de recoger el KYC es notificar al usuario que el anchor está listo para recibir fondos. Sin embargo, como tu servicio recibirá transacciones a través de la red Stellar, la solicitud RPC será diferente. El anchor debe usar el RPC `request_onchain_funds` para proporcionar las cantidades finales al usuario. Para hacer esto, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "iso4217:USD"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es la cantidad que el usuario debe enviar al negocio.
-- `amount_out` es la cantidad que el usuario recibirá.
-- `fee_details` es el total de tarifas cobradas por el negocio.
-- `asset` es parte del campo `amount_x` y está en formato SEP-38. En este ejemplo, está configurado en USD, asumiendo que el usuario hizo una transferencia bancaria al sistema usando USD.
-- `memo` es el memo que el usuario debe usar al enviar sus fondos onchain al anchor.
-- `memo_type` es el tipo de memo que el usuario debe usar al enviar sus fondos onchain al anchor.
-- `destination_account` es la cuenta a la que el usuario debe enviar los fondos.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-:::caution
-
-Para retiros de exchange con una cotización firme (la solicitud está asociada con un `quote_id`), no deben proporcionarse cantidades.
-
-:::
-
-:::tip
-
-Establecer `memo`, `memo_type` y `destination_account` es opcional.
-
-Si la integración con un custodio externo está habilitada, la Plataforma Anchor puede generar `memo`, `memo_type` y `destination_address` si se elige un `deposit_info_generator_type` correspondiente. También puedes proveer `memo` y `memo_type` a la solicitud como se muestra arriba. Ten en cuenta que el memo debe ser único, esto ayuda a asociar las transacciones Stellar con las transacciones SEP.
-
-Si tu negocio administra los activos, la Plataforma Anchor puede generar memos para ti. Cuando el estado cambia a `pending_user_transfer_start`, la Plataforma Anchor establece automáticamente `memo` y `memo_type` (solo si no están incluidos en la solicitud).
-
-:::
-
-:::note
-
-La cuenta Stellar que se usará para recibir fondos debe estar configurada.
-
-:::
-
-### Fondos Recibidos
-
-Si se recibieron fondos onchain, debes proporcionar montos y cambiar el estado de la transacción a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método será llamado por el observador de pagos Stellar cuando detecte que se han recibido fondos en cadena.
-
-:::
-
-### Cantidad Actualizada
-
-Si se recibieron fondos onchain, pero por alguna razón `amount_in` difiere de lo especificado en el flujo interactivo (`amount_expected`), puedes actualizar `amount_out` y `fee_details` para que correspondan al `amount_in` real. El estado de la transacción en este caso no cambiará y será igual a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// amounts-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_amounts_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Amounts updated",
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh amounts-updated.json
-```
-
-</CodeExample>
-
-:::note
-
-Solo `amount_out` y `fee_details` pueden actualizarse usando esta solicitud JSON-RPC, y no necesitas especificar los activos de las cantidades.
-
-:::
-
-### Fondos Offchain Disponibles
-
-Puedes mover el estado de la transacción a `pending_user_transfer_complete` si se enviaron fondos offchain y está listo para que el usuario/destinatario los recoja.
-
-<CodeExample>
-
-```json
-// offchain-funds-available.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_available",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds available",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-available.json
-```
-
-</CodeExample>
-
-### Fondos Offchain Pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago ha sido enviado a una red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Fondos Offchain Enviados
-
-Para completar la transacción y cambiar su estado a `completed`, debes hacer la solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Reembolso Enviado
-
-La lógica de reembolso funciona igual que para el flujo de depósito. Para más detalles, consulta [Reembolso Enviado](#refund-sent) del flujo de depósito.
-
-### Error de Transacción
-
-Funciona igual que para el flujo de depósito. Para más detalles, consulta [Error de Transacción](#transaction-error) del flujo de depósito.
-
-### Transacción Expirada
-
-Funciona igual que para el flujo de depósito. Para más detalles, consulta [Transacción Expirada](#expired-transaction) del flujo de depósito.
-
-### Recuperación de Transacción
-
-Funciona igual que para el flujo de depósito. Para más detalles, consulta [Recuperación de Transacción](#transaction-recovery) del flujo de depósito.
-
-## Seguimiento de Transacciones Stellar
-
-<Observer />
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[manejo de eventos]: ../../admin-guide/events/README.mdx
-[callback de cliente]: ../../api-reference/callbacks/README.mdx
-[callback de tasa]: ../../api-reference/callbacks/README.mdx
-[obtener-transacciones]: ../../api-reference/platform/transactions/get-transactions.api.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/whats-new.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/whats-new.mdx
deleted file mode 100644
index a6250ab9e1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-ap/current/whats-new.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Qué hay de nuevo en la versión 4.0
-sidebar_position: 30
----
-
-La versión 4.0 de Anchor Platform ofrece capacidades mejoradas con las siguientes características:
-
-- Soporte para depositar y retirar hacia y desde cuentas de contrato para transacciones SEP-6 y SEP-24.
-- Integración con el servidor RPC de Stellar. Descubre más [aquí](https://developers.stellar.org/docs/data/apis/rpc).
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current.json b/i18n/es/docusaurus-plugin-content-docs-sdp/current.json
deleted file mode 100644
index 567a9c45c4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current.json
+++ /dev/null
@@ -1,342 +0,0 @@
-{
-  "version.label": {
-    "message": "Siguiente",
-    "description": "The label for version current"
-  },
-  "sidebar.stellar_disbursement_platform.category.Stellar Disbursement Platform": {
-    "message": "Plataforma de Distribución Stellar",
-    "description": "The label for category Stellar Disbursement Platform in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin Guide": {
-    "message": "Guía del Administrador",
-    "description": "The label for category Admin Guide in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin Guide.link.generated-index.description": {
-    "message": "Todo lo que necesitas saber sobre la configuración, ejecución y uso de la Stellar Disbursement Platform.",
-    "description": "The generated-index page description for category Admin Guide in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.User Interface": {
-    "message": "Interfaz de Usuario",
-    "description": "The label for category User Interface in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Reference": {
-    "message": "Referencia de API",
-    "description": "The label for category API Reference in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Reference.link.generated-index.description": {
-    "message": "Ver toda la información de la API de la Stellar Disbursement Platform.",
-    "description": "The generated-index page description for category API Reference in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin (Tenant Management)": {
-    "message": "Administración (Gestión de Inquilinos)",
-    "description": "The label for category Admin (Tenant Management) in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Authentication": {
-    "message": "Autenticación",
-    "description": "The label for category Authentication in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Balances": {
-    "message": "Saldos",
-    "description": "The label for category Balances in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Disbursements": {
-    "message": "Desembolsos",
-    "description": "The label for category Disbursements in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Organization": {
-    "message": "Organización",
-    "description": "The label for category Organization in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Payments": {
-    "message": "Pagos",
-    "description": "The label for category Payments in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Profile": {
-    "message": "Perfil",
-    "description": "The label for category Profile in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Receivers": {
-    "message": "Receptores",
-    "description": "The label for category Receivers in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Registration": {
-    "message": "Registro",
-    "description": "The label for category Registration in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Statistics": {
-    "message": "Estadísticas",
-    "description": "The label for category Statistics in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Users": {
-    "message": "Usuarios",
-    "description": "The label for category Users in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Exports": {
-    "message": "Exportaciones",
-    "description": "The label for category Exports in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.category.Wallets": {
-    "message": "Billeteras",
-    "description": "The label for category Wallets in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Tenants": {
-    "message": "Obtener Todos los Inquilinos",
-    "description": "The label for the doc item Get All Tenants in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-tenants"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Tenant": {
-    "message": "Crear Inquilino",
-    "description": "The label for the doc item Create Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Tenant": {
-    "message": "Recuperar un Inquilino",
-    "description": "The label for the doc item Retrieve a Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Soft delete a Tenant": {
-    "message": "Eliminar un Inquilino de forma suave",
-    "description": "The label for the doc item Soft delete a Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/soft-delete-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Tenant": {
-    "message": "Actualizar un Inquilino",
-    "description": "The label for the doc item Update a Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Default Tenant": {
-    "message": "Inquilino Predeterminado",
-    "description": "The label for the doc item Default Tenant in sidebar stellar_disbursement_platform, linking to the doc api-reference/default-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Log In": {
-    "message": "Iniciar Sesión",
-    "description": "The label for the doc item Log In in sidebar stellar_disbursement_platform, linking to the doc api-reference/log-in"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Refresh Token": {
-    "message": "Actualizar Token",
-    "description": "The label for the doc item Refresh Token in sidebar stellar_disbursement_platform, linking to the doc api-reference/refresh-token"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Provide Multi-Factor Authentication": {
-    "message": "Proporcionar Autenticación de Múltiples Factores",
-    "description": "The label for the doc item Provide Multi-Factor Authentication in sidebar stellar_disbursement_platform, linking to the doc api-reference/authenticate-mfa"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Forgot Password": {
-    "message": "Olvidé mi Contraseña",
-    "description": "The label for the doc item Forgot Password in sidebar stellar_disbursement_platform, linking to the doc api-reference/forgot-password"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Reset Rassword": {
-    "message": "Restablecer Contraseña",
-    "description": "The label for the doc item Reset Rassword in sidebar stellar_disbursement_platform, linking to the doc api-reference/reset-password"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Organization (Circle) Balances": {
-    "message": "Obtener Saldos de Organización (Círculo)",
-    "description": "The label for the doc item Get Organization (Circle) Balances in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-organization-circle-balances"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Disbursements": {
-    "message": "Listar Todos los Desembolsos",
-    "description": "The label for the doc item List All Disbursements in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-all-disbursements"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Disbursement": {
-    "message": "Crear Desembolso",
-    "description": "The label for the doc item Create Disbursement in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Disbursement": {
-    "message": "Recuperar un Desembolso",
-    "description": "The label for the doc item Retrieve a Disbursement in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-a-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Deletes a Draft Disbursement": {
-    "message": "Elimina un desembolso borrador",
-    "description": "The label for the doc item Deletes a Draft Disbursement in sidebar stellar_disbursement_platform, linking to the doc api-reference/delete-a-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Disbursement Receivers": {
-    "message": "Listar Todos los Receptores de Desembolsos",
-    "description": "The label for the doc item List All Disbursement Receivers in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-all-disbursement-receivers"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Download Disbursement Instructions": {
-    "message": "Descargar Instrucciones de Desembolso",
-    "description": "The label for the doc item Download Disbursement Instructions in sidebar stellar_disbursement_platform, linking to the doc api-reference/download-disbursement-instructions"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Upload Disbursement Instructions": {
-    "message": "Subir Instrucciones de Desembolso",
-    "description": "The label for the doc item Upload Disbursement Instructions in sidebar stellar_disbursement_platform, linking to the doc api-reference/upload-disbursement-instructions"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Disbursement Status": {
-    "message": "Actualizar el Estado de un Desembolso",
-    "description": "The label for the doc item Update a Disbursement Status in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-a-disbursement-status"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Organization Info": {
-    "message": "Obtener Información de la Organización",
-    "description": "The label for the doc item Get Organization Info in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-organization-info"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Organization Profile": {
-    "message": "Actualizar el Perfil de la Organización",
-    "description": "The label for the doc item Update Organization Profile in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-organization-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Organization Logo": {
-    "message": "Recuperar el Logo de la Organización",
-    "description": "The label for the doc item Retrieve Organization Logo in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-organization-logo"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Circle Account Setup": {
-    "message": "Configuración de Cuenta de Circle",
-    "description": "The label for the doc item Circle Account Setup in sidebar stellar_disbursement_platform, linking to the doc api-reference/patch-organization-circle"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Assets": {
-    "message": "Obtener Todos los Activos",
-    "description": "The label for the doc item Get All Assets in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-assets"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Asset": {
-    "message": "Crear Activo",
-    "description": "The label for the doc item Create Asset in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-asset"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Delete Asset": {
-    "message": "Eliminar Activo",
-    "description": "The label for the doc item Delete Asset in sidebar stellar_disbursement_platform, linking to the doc api-reference/delete-asset"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Wallets": {
-    "message": "Obtener Todas las Billeteras",
-    "description": "The label for the doc item Get All Wallets in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-wallets"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Wallet": {
-    "message": "Actualizar Billetera",
-    "description": "The label for the doc item Update Wallet in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-wallet"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Payments": {
-    "message": "Listar Todos los Pagos",
-    "description": "The label for the doc item List All Payments in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-all-payments"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Payment": {
-    "message": "Recuperar un Pago",
-    "description": "The label for the doc item Retrieve a Payment in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-a-payment"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Profile": {
-    "message": "Obtener Perfil",
-    "description": "The label for the doc item Get Profile in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Profile": {
-    "message": "Actualizar el Perfil de Usuario",
-    "description": "The label for the doc item Update User Profile in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-user-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Receivers": {
-    "message": "Listar Todos los Receptores",
-    "description": "The label for the doc item List All Receivers in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-all-receivers"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Receiver": {
-    "message": "Recuperar un Receptor",
-    "description": "The label for the doc item Retrieve a Receiver in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-a-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Receiver": {
-    "message": "Actualizar un Receptor",
-    "description": "The label for the doc item Update a Receiver in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Start Wallet Registration": {
-    "message": "Iniciar Registro de Billetera",
-    "description": "The label for the doc item Start Wallet Registration in sidebar stellar_disbursement_platform, linking to the doc api-reference/start-wallet-registration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Send One-Time Passcode": {
-    "message": "Enviar Código de Un Solo Uso",
-    "description": "The label for the doc item Send One-Time Passcode in sidebar stellar_disbursement_platform, linking to the doc api-reference/send-one-time-passcode"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Verify Receiver Registration": {
-    "message": "Verificar Registro de Receptor",
-    "description": "The label for the doc item Verify Receiver Registration in sidebar stellar_disbursement_platform, linking to the doc api-reference/verify-receiver-registration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Stellar Info File": {
-    "message": "Recuperar Archivo de Información de Stellar",
-    "description": "The label for the doc item Retrieve Stellar Info File in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-stellar-info-file"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Request Challenge Transaction": {
-    "message": "Solicitar Transacción de Desafío",
-    "description": "The label for the doc item Request Challenge Transaction in sidebar stellar_disbursement_platform, linking to the doc api-reference/request-challenge-transaction"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Provide Signed Challenge Transaction": {
-    "message": "Proporcionar Transacción de Desafío Firmada",
-    "description": "The label for the doc item Provide Signed Challenge Transaction in sidebar stellar_disbursement_platform, linking to the doc api-reference/provide-signed-challenge-transaction"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Request Registration URL": {
-    "message": "Solicitar URL de Registro",
-    "description": "The label for the doc item Request Registration URL in sidebar stellar_disbursement_platform, linking to the doc api-reference/request-registration-url"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve All Statistics": {
-    "message": "Recuperar Todas las Estadísticas",
-    "description": "The label for the doc item Retrieve All Statistics in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-all-statistics"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Disbursement Statistics": {
-    "message": "Recuperar Estadísticas de Desembolso",
-    "description": "The label for the doc item Retrieve Disbursement Statistics in sidebar stellar_disbursement_platform, linking to the doc api-reference/retrieve-disbursement-statistics"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Users": {
-    "message": "Obtener Todos los Usuarios",
-    "description": "The label for the doc item Get All Users in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-users"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create User": {
-    "message": "Crear Usuario",
-    "description": "The label for the doc item Create User in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-user"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Activation Status": {
-    "message": "Actualizar Estado de Activación del Usuario",
-    "description": "The label for the doc item Update User Activation Status in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-user-activation-status"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Roles": {
-    "message": "Obtener Todos los Roles",
-    "description": "The label for the doc item Get All Roles in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-all-roles"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Role": {
-    "message": "Actualizar Rol de Usuario",
-    "description": "The label for the doc item Update User Role in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-user-role"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Disbursements": {
-    "message": "Exportar desembolsos",
-    "description": "The label for the doc item Export Disbursements in sidebar stellar_disbursement_platform, linking to the doc api-reference/export-disbursements"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Payments": {
-    "message": "Exportar pagos",
-    "description": "The label for the doc item Export Payments in sidebar stellar_disbursement_platform, linking to the doc api-reference/export-payments-csv"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Receivers": {
-    "message": "Exportar receptores",
-    "description": "The label for the doc item Export Receivers in sidebar stellar_disbursement_platform, linking to the doc api-reference/export-receivers-csv"
-  },
-  "sidebar.stellar_disbursement_platform.category.Bridge Integration": {
-    "message": "Integración de Bridge",
-    "description": "The label for category Bridge Integration in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Bridge Integration Status": {
-    "message": "Obtener estado de integracion de Bridge",
-    "description": "The label for the doc item Get Bridge Integration Status in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-bridge-integration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Bridge Integration Status": {
-    "message": "Actualizar estado de integracion de Bridge",
-    "description": "The label for the doc item Update Bridge Integration Status in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-bridge-integration"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Keys": {
-    "message": "Claves API",
-    "description": "The label for category API Keys in sidebar stellar_disbursement_platform"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List API Keys": {
-    "message": "Listar Claves API",
-    "description": "The label for the doc item List API Keys in sidebar stellar_disbursement_platform, linking to the doc api-reference/list-api-keys"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create API Key": {
-    "message": "Crear Clave API",
-    "description": "The label for the doc item Create API Key in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get API Key Details": {
-    "message": "Obtener detalles de la Clave API",
-    "description": "The label for the doc item Get API Key Details in sidebar stellar_disbursement_platform, linking to the doc api-reference/get-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update API Key": {
-    "message": "Actualizar Clave API",
-    "description": "The label for the doc item Update API Key in sidebar stellar_disbursement_platform, linking to the doc api-reference/update-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Delete API Key": {
-    "message": "Eliminar Clave API",
-    "description": "The label for the doc item Delete API Key in sidebar stellar_disbursement_platform, linking to the doc api-reference/delete-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Wallet": {
-    "message": "Crear billetera",
-    "description": "The label for the doc item Create Wallet in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-wallet"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Direct Payment": {
-    "message": "Crear pago directo",
-    "description": "The label for the doc item Create Direct Payment in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-direct-payment"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Receiver": {
-    "message": "Crear receptor",
-    "description": "The label for the doc item Create Receiver in sidebar stellar_disbursement_platform, linking to the doc api-reference/create-receiver"
-  }
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/README.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/README.mdx
deleted file mode 100644
index c241588e81..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Introducción a Stellar Disbursement Platform
-sidebar_label: Introducción
-pagination_label: Introducción a Stellar Disbursement Platform
-sidebar_position: 10
-pagination_next: admin-guide/overview
----
-
-# Stellar Disbursement Platform
-
-Stellar Disbursement Platform (SDP) es una herramienta desarrollada para que las organizaciones realicen pagos masivos a un grupo de destinatarios mediante la red Stellar.
-
-Este es un proyecto open-source desarrollado sobre la red Stellar, y el código puede encontrarse en los siguientes repositorios:
-
-- [stellar/stellar-disbursement-platform-backend](https://github.com/stellar/stellar-disbursement-platform-backend): Este repositorio contiene el código backend e infraestructura para Stellar Disbursement Platform.
-- [stellar/stellar-disbursement-platform-frontend](https://github.com/stellar/stellar-disbursement-platform-frontend): Este repositorio contiene el código frontend web para Stellar Disbursement Platform.
-- [stellar/helm-charts](https://github.com/stellar/helm-charts/tree/main/charts/stellar-disbursement-platform): Este repositorio contiene el Helm chart para desplegar Stellar Disbursement Platform usando kubernetes.
-
-En esta sección encontrarás una [Guía para administradores](./stellar-disbursement-platform/admin-guide/) que te enseñará cómo ejecutar Stellar Disbursement Platform, así como una [Referencia API](./api-reference/admin.tag.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/advanced-configration.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/advanced-configration.mdx
deleted file mode 100644
index 31f5954bf9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/advanced-configration.mdx
+++ /dev/null
@@ -1,236 +0,0 @@
----
-title: Configuración avanzada
-description: Comprende cómo configurar el SDP para varios escenarios. Esto incluye multi-tenancy, testnet frente a mainnet, etc.
-keywords:
-  - SDP
-  - configuration
-sidebar_position: 45
----
-
-En esta guía, aprenderás sobre las opciones avanzadas de configuración para la Stellar Disbursement Platform (SDP). Estas configuraciones te permiten adaptar el SDP para cumplir con requisitos específicos, tales como multi-tenancy, selección de red y ajuste de rendimiento.
-
-## Configuración de Testnet a Mainnet
-
-Al provisionar una nueva instancia de SDP, esta se configura para operar en modo Mainnet o Testnet según las variables de entorno establecidas durante la configuración. La mayoría de los usuarios comenzará con Testnet para desarrollo y pruebas antes de pasar a Mainnet para uso en producción.
-
-:::caution
-
-Una instancia de SDP está diseñada para operar en Testnet o Mainnet. No se admite cambiar entre estas redes en una instancia existente y podría causar comportamientos inesperados. Si necesitas cambiar la red, se recomienda configurar una nueva instancia de SDP con la configuración deseada.
-
-:::
-
-Una vez validada tu configuración en Testnet, puedes desplegar una nueva instancia configurada para Mainnet estableciendo las variables de entorno apropiadas durante el proceso de provisión.
-
-### Variables de Entorno
-
-Al cambiar de Testnet a Mainnet, debes actualizar las siguientes variables de entorno para cada servicio para que apunten a los recursos de la red pública.
-
-#### Servicio Core SDP
-
-| Variable             | Valor en Testnet                      | Valor en Mainnet                                 | Descripción                                                                  |
-| :------------------- | :------------------------------------ | :----------------------------------------------- | :--------------------------------------------------------------------------- |
-| `NETWORK_PASSPHRASE` | `Test SDF Network ; September 2015`   | `Public Global Stellar Network ; September 2015` | La frase de paso para la red Stellar.                                        |
-| `HORIZON_URL`        | `https://horizon-testnet.stellar.org` | `https://horizon.stellar.org`                    | La URL del servidor Horizon.                                                 |
-| `DISABLE_MFA`        | x                                     | `false`                                          | Deshabilita la Autenticación Multifactor. **Debe ser `false` para Mainnet.** |
-
-#### Servicio de Envío de Transacciones (TSS)
-
-| Variable             | Valor en Testnet                      | Valor en Mainnet                                 | Descripción                           |
-| :------------------- | :------------------------------------ | :----------------------------------------------- | :------------------------------------ |
-| `NETWORK_PASSPHRASE` | `Test SDF Network ; September 2015`   | `Public Global Stellar Network ; September 2015` | La frase de paso para la red Stellar. |
-| `HORIZON_URL`        | `https://horizon-testnet.stellar.org` | `https://horizon.stellar.org`                    | La URL del servidor Horizon.          |
-
-#### Tablero
-
-| Variable             | Valor en Testnet                          | Valor en Mainnet                         | Descripción                                        |
-| :------------------- | :---------------------------------------- | :--------------------------------------- | :------------------------------------------------- |
-| `HORIZON_URL`        | `https://horizon-testnet.stellar.org`     | `https://horizon.stellar.org`            | La URL del servidor Horizon usado por el frontend. |
-| `STELLAR_EXPERT_URL` | `https://stellar.expert/explorer/testnet` | `https://stellar.expert/explorer/public` | La URL para el explorador Stellar Expert.          |
-
-### Consideraciones Críticas
-
-Antes de desplegar en Mainnet, debes cumplir con los siguientes requisitos críticos para asegurar que tu instancia funcione correctamente.
-
-**Debes** generar un nuevo par de claves seguro para tu Cuenta de Distribución en Mainnet. No reutilices claves de Testnet.
-
-- **Generar Claves**: Crea un nuevo par de claves y establece `DISTRIBUTION_PUBLIC_KEY` y `DISTRIBUTION_SEED`.
-- **Generar Frase de Encriptación**: Debes generar nuevas frases de encriptación para las cuentas de distribución de tus tenants y cuentas de canal, configurando `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE` y `CHANNEL_ACCOUNTS_ENCRYPTION_PASSPHRASE`.
-- **Financiar la Cuenta**: La Cuenta de Distribución requiere un saldo inicial de XLM para funcionar. Es responsable de:
-  1. **Crear Cuentas de Canal**: El sistema creará automáticamente `NUM_CHANNEL_ACCOUNTS` (por defecto: 2).
-  2. **Inicializar Tenants**: Al provisionar un nuevo tenant, el sistema transfiere una cantidad inicial de XLM desde la Cuenta de Distribución a la Cuenta de Distribución del tenant. Esto se controla con `TENANT_XLM_BOOTSTRAP_AMOUNT` (por defecto: 5 XLM).
-
-### Métodos de Configuración
-
-Puedes configurar el SDP para Mainnet usando Helm Charts (para despliegues en Kubernetes) o Docker Compose (para despliegues locales o simples).
-
-#### Helm Charts
-
-Si despliegas mediante Helm, el chart proporciona un ajuste global que configura automáticamente los parámetros de red necesarios.
-
-En tu archivo `values.yaml`, establece `global.isPubnet` en `true`. Esto configurará automáticamente el `NETWORK_PASSPHRASE`, `HORIZON_URL` y `STELLAR_EXPERT_URL` correctos para todos los servicios.
-
-```yaml
-global:
-  # Set to true for Mainnet
-  isPubnet: true
-```
-
-#### Docker Compose
-
-Actualiza tu archivo `.env` con los siguientes valores:
-
-```bash
-# Network Configuration
-NETWORK_TYPE="pubnet"
-NETWORK_PASSPHRASE="Public Global Stellar Network ; September 2015"
-HORIZON_URL="https://horizon.stellar.org"
-
-# Security
-DISABLE_MFA=false
-
-# Distribution Account (Mainnet Keys)
-DISTRIBUTION_PUBLIC_KEY="G..."
-DISTRIBUTION_SEED="S..."
-
-# Encryption Passphrases
-DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE="S..."
-CHANNEL_ACCOUNTS_ENCRYPTION_PASSPHRASE="S..."
-```
-
-## Configuración de Single Tenant a Multi-Tenant
-
-La Stellar Disbursement Platform (SDP) soporta multi-tenancy, permitiendo que una sola instancia sirva a varias organizaciones (tenants). Cada tenant tiene sus propios datos aislados, usuarios y cuenta de distribución (fuente de fondos).
-
-### Configuración
-
-Para habilitar multi-tenancy, debes actualizar tu configuración para desactivar el modo single-tenant y asegurar que la Admin API sea accesible.
-
-1. **Desactivar modo Single Tenant**: Establece la variable de entorno `SINGLE_TENANT_MODE` en `false`.
-2. **Exponer puerto Admin**: Asegúrate de que el puerto de la Admin API (por defecto `8003`) esté expuesto en el servicio sdp backend.
-
-### Enrutamiento e Ingreso
-
-El SDP identifica al tenant para cada solicitud utilizando uno de los siguientes métodos, en orden de precedencia:
-
-1. **Encabezado HTTP**: El encabezado `SDP-Tenant-Name`.
-2. **Subdominio**: El prefijo del nombre del host (por ejemplo, `tenant1` en `tenant1.sdp.stellar.org`).
-
-#### Encabezado HTTP
-
-Puedes especificar explícitamente el tenant configurando el encabezado `SDP-Tenant-Name` en tus solicitudes HTTP.
-
-```bash
-curl -H "SDP-Tenant-Name: tenant1" https://sdp.stellar.org/ ...
-```
-
-#### Enrutamiento por Subdominio
-
-En un entorno de producción, es común usar el enrutamiento por subdominio. Por ejemplo, `tenant1.sdp.stellar.org` y `tenant2.sdp.stellar.org` apuntarán a la misma instancia de SDP.
-
-#### Helm Charts
-
-Al desplegar mediante Helm, configuras el dominio comodín usando el valor `sdp.route.mtnDomain`. Esto crea una regla de Ingress que coincide con todos los subdominios.
-
-En tu `values.yaml`:
-
-```yaml
-sdp:
-  route:
-    # The wildcard domain for multi-tenancy
-    mtnDomain: "*.sdp.stellar.org"
-```
-
-:::note
-
-Asegúrate de que tu proveedor DNS tenga un registro A comodín (por ejemplo, `*.sdp.stellar.org`) apuntando a la IP del Load Balancer de tu Ingress Controller.
-
-:::
-
-#### Docker Compose (Desarrollo Local)
-
-Para desarrollo local con Docker Compose debes mapear subdominios específicos de tenants a `127.0.0.1` en el archivo `/etc/hosts` de tu máquina (Para usuarios de Windows, el archivo se encuentra en `C:\Windows\System32\drivers\etc\hosts`).
-
-**Ejemplo de `/etc/hosts`:**
-
-```text
-127.0.0.1   localhost
-127.0.0.1   sdp.local           # Default/Admin domain
-127.0.0.1   tenant1.sdp.local   # First tenant
-127.0.0.1   tenant2.sdp.local   # Second tenant
-```
-
-### Provisionamiento de Tenants
-
-En modo multi-tenant, provisionas nuevos tenants usando la Admin API (puerto `8003` por defecto). Cada tenant tendrá datos aislados.
-
-**Endpoint**: [POST /tenants](../api-reference/create-tenant.api.mdx) **Ejemplo de solicitud:**
-
-```bash
-curl --location 'http://localhost:8003/tenants' \
---header 'Content-Type: application/json' \
---header 'Authorization: Basic <Base64 Admin Credentials>' \
---data '{
-    "name": "tenant1",
-    "organization_name": "Tenant One Organization",
-    "base_url": "https://tenant1.sdp-api.stellar.org",
-    "sdp_ui_base_url": "https://tenant1.sdp-dashboard.stellar.org",
-    "owner_email": "owner@tenant1.com",
-    "owner_first_name": "Jane",
-    "owner_last_name": "Doe",
-    "distribution_account_type": "DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT"
-}'
-```
-
-#### Cuentas de Distribución Multi-Tenant
-
-Este es, por mucho, el campo más importante, pues determina la fuente de fondos (cuenta de distribución) para el tenant, así como cómo se almacena el secreto de esta cuenta de distribución.
-
-Esto se determina por el campo `distribution_account_type` en la llamada API mencionada anteriormente. Los valores posibles se describen a continuación:
-
-- `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT`
-
-- **Plataforma**: Stellar
-
-- **Ubicación del almacenamiento del secreto**: Base de datos, encriptada con `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`
-
-- **Activos compatibles**: Cualquier activo Stellar
-
-- **Aislamiento de clave/secreto**: Segregado por tenant
-
-- **Adecuado para**: Multi-tenant y single-tenant
-
-- **¿Cómo se configura?**: La cuenta de distribución se genera aleatoriamente y se financia durante el proceso de provisión, y el secreto se encripta y almacena de forma segura en la base de datos. La cuenta se financia desde la cuenta HOST de distribución por un monto definido en `TENANT_XLM_BOOTSTRAP_AMOUNT`.
-
-- `DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT`
-
-- **Plataforma**: [Circle](https://www.circle.com)
-
-- **Ubicación del almacenamiento del secreto**: Base de datos, encriptada con `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`
-
-- **Activos compatibles**: [USDC](https://www.circle.com/en/usdc)/[EURC](https://www.circle.com/en/eurc)
-
-- **Aislamiento de clave/secreto**: Segregado por tenant
-
-- **Adecuado para**: Multi-tenant y single-tenant
-
-- **¿Cómo se configura?**: La clave API de Circle es proporcionada por el propio tenant una vez que tiene acceso al tablero. El secreto se encripta y almacena de forma segura en la base de datos.
-
-- 🔴 `DISTRIBUTION_ACCOUNT.STELLAR.ENV`
-
-- **Plataforma**: Stellar
-
-- **Ubicación del almacenamiento del secreto**: Variable de entorno `DISTRIBUTION_SEED`
-
-- **Activos compatibles**: Cualquier activo Stellar
-
-- **Aislamiento de clave/secreto**: 🚨 Misma cuenta de distribución que el HOST
-
-- **Adecuado para**: Solo single-tenant
-
-- **¿Cómo se configura?**: El tenant usará la cuenta HOST **tal cual**. El host es responsable de crear la cuenta y configurarla con el secreto `DISTRIBUTION_SEED`.
-
-:::warning
-
-Una vez que se crea un tenant, no se puede cambiar el `distribution_account_type`. Si deseas usar un tipo diferente de cuenta de distribución, deberás crear un nuevo tenant.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/anchor-platform-integration-points.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/anchor-platform-integration-points.mdx
deleted file mode 100644
index 48b8930cd5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/anchor-platform-integration-points.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Puntos de integración de la Anchor Platform
-sidebar_position: 60
----
-
-Como se menciona en la guía de [Diseño y Arquitectura](./design-and-architecture), la Stellar Disbursement Platform consiste en varios servicios implementados juntos, donde la Anchor Platform es uno de ellos.
-
-Por esa razón, hay algunos puntos de conexión entre las dos instancias que deben configurarse adecuadamente para que la Stellar Disbursement Platform funcione correctamente. Cubriremos estos puntos de integración en esta guía.
-
-Ten en cuenta que para la implementación predeterminada de la Stellar Disbursement Platform, que se basa en valores predeterminados de Helm y en billeteras y activos predeterminados, no se necesita configuración adicional. Esta guía es para aquellos que desean personalizar la implementación cambiando las billeteras y activos disponibles en su instancia de SDP.
-
-## Rol de la Anchor Platform en SDP
-
-El flujo de Registro de Billetera se inicia dentro de la aplicación de billetera del destinatario. Esta aplicación interactúa con la [Anchor Platform] para iniciar el proceso de depósito [SEP-24] a través de la SDP (Stellar Disbursement Platform). La SDP recopila la información necesaria del destinatario para ejecutar finalmente el pago a él.
-
-La Anchor Platform (AP) se utiliza para manejar la implementación de protocolos de interoperabilidad como [SEP-1], [SEP-10] y [SEP-24], haciendo que sus endpoints estén disponibles para las aplicaciones de billetera. La [Anchor Platform] está preconfigurada tanto en el gráfico Helm de [el repo] como en el archivo Docker Compose disponible en el directorio `dev`.
-
-## Pasos para Configurar la Integración SDP-AnchorPlatform
-
-Para asegurar una integración fluida entre la SDP y la [Anchor Platform], asegúrate de seguir estos pasos:
-
-1. 🚨 **Paso Crítico**: Configura la Anchor Platform con `PLATFORM_SERVER_AUTH_TYPE: JWT`. Esta configuración es crucial para asegurar la API de backoffice de tu Anchor Platform a través de la autenticación de token JWT.
-2. **Secretos Compartidos para la Autenticación de API**: El `SECRET_PLATFORM_API_AUTH_SECRET` en la Anchor Platform debe coincidir con `ANCHOR_PLATFORM_OUTGOING_JWT_SECRET` en la SDP.
-3. **Secretos Compartidos para SEP-24**: Los secretos `SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET` y `SECRET_SEP24_MORE_INFO_URL_JWT_SECRET` en la Anchor Platform deben alinearse con `SEP24_JWT_SECRET` en la SDP.
-4. **Configuración de SEP-10**: El `SECRET_SEP10_SIGNING_SEED` en la Anchor Platform debe ser consistente con el `SEP10_SIGNING_PRIVATE_KEY` y el `SEP10_SIGNING_PUBLIC_KEY` en la SDP.
-
-Al seguir estos pasos, garantizarás una integración segura y eficiente entre tus sistemas SDP y Anchor Platform.
-
-## Sincronización Manual de Activos y Billeteras Personalizados
-
-Actualmente, algunas configuraciones dentro de la Anchor Platform son estáticas y se cargan a través de variables de entorno. Por otro lado, la SDP lee estas mismas configuraciones de su base de datos y permite que un usuario propietario las modifique. Esta dinámica se refiere particularmente a las listas de activos y billeteras admitidos.
-
-Mientras exploramos activamente formas de automatizar este proceso de sincronización, los ajustes manuales a la configuración de la Anchor Platform son necesarios cada vez que un activo o billetera se agrega o elimina en la SDP.
-
-1. **(Requerido) Actualizar Activos Admitidos**: Cada vez que cambies la lista de activos admitidos en la SDP, es esencial actualizar la configuración `ASSETS_VALUE` de la Anchor Platform para reflejar estos cambios. Consulta los valores de Helm de [el repo] o los archivos Docker Compose para ejemplos.
-2. **(Opcional, pero Recomendado) Billeteras y Dominios SEP-10**: Si utilizas la configuración `SEP10_CLIENT_ATTRIBUTION_REQUIRED: true` en la Anchor Platform - una práctica recomendada - también debes actualizar la `SEP10_CLIENT_ATTRIBUTION_ALLOW_LIST` para incluir dominios de billetera de confianza. Esto asegura que la Anchor Platform procesará solicitudes SEP-10 solo de billeteras de confianza.
-
-Al adherirte a estas pautas, puedes asegurar una configuración consistente y segura entre tus instancias de SDP y Anchor Platform.
-
-[sep-1]: https://stellar.org/protocol/sep-1
-[sep-10]: https://stellar.org/protocol/sep-10
-[sep-24]: https://stellar.org/protocol/sep-24
-[Anchor Platform]: https://github.com/stellar/java-stellar-anchor-sdk
-[el repo]: https://github.com/stellar/stellar-disbursement-platform-backend
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/cli-manual.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/cli-manual.mdx
deleted file mode 100644
index 0431310060..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/cli-manual.mdx
+++ /dev/null
@@ -1,655 +0,0 @@
----
-title: Manual de CLI
-description: Guía para usar la CLI de Stellar Disbursement Platform
-keywords:
-  - SDP
-  - CLI
-sidebar_position: 50
----
-
-## Comando raíz
-
-El comando `stellar-disbursement-platform` es el punto de entrada principal para la aplicación. Proporciona varios subcomandos para administrar el servicio, la base de datos y otras utilidades.
-
-### Uso
-
-```bash
-stellar-disbursement-platform [command] [flags]
-```
-
-:::tip
-
-Para todos los comandos siguientes, puedes usar la flag `--help` para obtener más información acerca del comando y sus opciones. Por ejemplo:
-
-```bash
-stellar-disbursement-platform serve --help
-```
-
-:::
-
-## Flags globales
-
-Las siguientes flags están disponibles para todos los comandos:
-
-| Flag                   | Descripción                                                                                                                                  |
-| :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--base-url`           | La URL base del servidor backend de SDP. Por defecto es `http://localhost:8000`.                                                             |
-| `--database-url`       | URL de la base de datos Postgres. Por defecto es `postgres://localhost:5432/sdp?sslmode=disable`.                                            |
-| `--environment`        | El entorno en el que la aplicación está ejecutándose. Ejemplo: `development`, `staging`, `production`. Por defecto es `development`.         |
-| `--log-level`          | El nivel de log utilizado en este proyecto. Opciones: `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL`, o `PANIC`. Por defecto es `TRACE`. |
-| `--network-passphrase` | La frase de contraseña de la red Stellar. Por defecto es `Test SDF Network ; September 2015`.                                                |
-| `--sdp-ui-base-url`    | La URL base del servidor UI de SDP. Por defecto es `http://localhost:3000`.                                                                  |
-| `--sentry-dsn`         | El DSN (clave cliente) del proyecto Sentry. Si no se provee, Sentry no será usado.                                                           |
-
-## Comando Serve
-
-El comando `serve` inicia el servidor backend de Stellar Disbursement Platform. Este servidor maneja las peticiones API, procesa desembolsos y administra operaciones de los tenants.
-
-### Uso
-
-```bash
-stellar-disbursement-platform serve [flags]
-```
-
-### Flags
-
-| Flag                                                 | Descripción                                                                                                                                                                                                                 |
-| :--------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--admin-account`                                    | ID de la cuenta admin. Para usarlo, añádelo al encabezado de la petición como 'Authorization', formateado como 'ADMIN_ACCOUNT:ADMIN_API_KEY' codificado en Base64.                                                          |
-| `--admin-api-key`                                    | Clave API para la cuenta admin. Para usarlo, añádelo al encabezado de la petición como 'Authorization', formateado como 'ADMIN_ACCOUNT:ADMIN_API_KEY' codificado en Base64.                                                 |
-| `--admin-port`                                       | Puerto donde el servidor tenant admin estará escuchando. Por defecto es `8003`.                                                                                                                                             |
-| `--aws-access-key-id`                                | El ID de la clave de acceso AWS.                                                                                                                                                                                            |
-| `--aws-region`                                       | La región de AWS.                                                                                                                                                                                                           |
-| `--aws-secret-access-key`                            | La clave secreta de acceso AWS.                                                                                                                                                                                             |
-| `--aws-ses-sender-id`                                | La dirección de correo electrónico que AWS usará para enviar emails. Usa AWS SES.                                                                                                                                           |
-| `--aws-sns-sender-id`                                | El ID del remitente de la cuenta AWS que envía los mensajes SMS. Usa AWS SNS.                                                                                                                                               |
-| `--bridge-api-key`                                   | Clave API de Bridge. Esto debe configurarse solo si la integración con Bridge está habilitada.                                                                                                                              |
-| `--bridge-base-url`                                  | URL base de Bridge. Esto debe configurarse solo si la integración con Bridge está habilitada. Por defecto es `https://api.bridge.xyz`.                                                                                      |
-| `--captcha-type`                                     | El tipo de CAPTCHA a usar. Opciones: `GOOGLE_RECAPTCHA_V2`, `GOOGLE_RECAPTCHA_V3`. Por defecto es `GOOGLE_RECAPTCHA_V2`.                                                                                                    |
-| `--channel-account-encryption-passphrase`            | Una clave privada ed25519 compatible con Stellar usada para encriptar/desencriptar las claves privadas de las cuentas canal. Si no está configurada, por defecto tomará el valor de la opción `distribution-seed`.          |
-| `--circle-api-type`                                  | El tipo de API de Circle. Opciones: `TRANSFERS`, `PAYOUTS`. Por defecto es `TRANSFERS`.                                                                                                                                     |
-| `--cors-allowed-origins`                             | URLs CORS que están permitidas para acceder a los endpoints, separadas por ",".                                                                                                                                             |
-| `--crash-tracker-type`                               | Tipo de rastreador de fallos. Opciones: `SENTRY`, `DRY_RUN`. Por defecto es `DRY_RUN`.                                                                                                                                      |
-| `--db-conn-max-idle-time-seconds`                    | Tiempo máximo inactivo en segundos antes de que se cierre una conexión. Por defecto es `10`.                                                                                                                                |
-| `--db-conn-max-lifetime-seconds`                     | Tiempo máximo de vida en segundos para una sola conexión. Por defecto es `300`.                                                                                                                                             |
-| `--db-max-idle-conns`                                | Número máximo de conexiones inactivas a la base de datos que se mantienen por pool. Por defecto es `2`.                                                                                                                     |
-| `--db-max-open-conns`                                | Número máximo de conexiones abiertas a la base de datos por pool. Por defecto es `20`.                                                                                                                                      |
-| `--disable-mfa`                                      | Deshabilita la autenticación multifactor (MFA) por correo electrónico.                                                                                                                                                      |
-| `--disable-recaptcha`                                | Deshabilita ReCAPTCHA para iniciar sesión y recuperar contraseña.                                                                                                                                                           |
-| `--distribution-account-encryption-passphrase`       | Una clave privada ed25519 compatible con Stellar usada para encriptar y desencriptar las claves privadas de las cuentas de distribución de los tenants.                                                                     |
-| `--distribution-public-key`                          | La clave pública de la cuenta de distribución Stellar del HOST, usada para crear cuentas canal.                                                                                                                             |
-| `--distribution-seed`                                | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas canal.                                                                                                                             |
-| `--ec256-private-key`                                | Clave privada EC256 usada para firmar el token de autenticación. Esta clave EC debe ser al menos tan fuerte como prime256v1 (P-256).                                                                                        |
-| `--email-sender-type`                                | Tipo de remitente de correo electrónico. Opciones: `DRY_RUN`, `TWILIO_EMAIL`, `AWS_EMAIL`. Por defecto es `DRY_RUN`.                                                                                                        |
-| `--enable-bridge-integration`                        | Habilita la integración con Bridge para Liquidity Sourcing.                                                                                                                                                                 |
-| `--horizon-url`                                      | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                                                        |
-| `--instance-name`                                    | Nombre de la instancia SDP. Ejemplo: `SDP Testnet`.                                                                                                                                                                         |
-| `--max-base-fee`                                     | La cuota base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                                                           |
-| `--max-invitation-resend-attempts`                   | El número máximo de intentos para reenviar la invitación a las Carteras Receptoras. Por defecto es `3`.                                                                                                                     |
-| `--metrics-port`                                     | Puerto donde el servidor de métricas estará escuchando. Por defecto es `8002`.                                                                                                                                              |
-| `--metrics-type`                                     | Tipo de monitor de métricas. Opciones: `PROMETHEUS`. Por defecto es `PROMETHEUS`.                                                                                                                                           |
-| `--port`                                             | Puerto donde el servidor estará escuchando. Por defecto es `8000`.                                                                                                                                                          |
-| `--recaptcha-site-key`                               | La clave de sitio de Google 'reCAPTCHA v2 - No soy un robot'.                                                                                                                                                               |
-| `--recaptcha-site-secret-key`                        | La clave SECRETA de sitio de Google 'reCAPTCHA v2 - No soy un robot'.                                                                                                                                                       |
-| `--recaptcha-v3-min-score`                           | Umbral mínimo de puntuación para reCAPTCHA v3 (de 0.0 a 1.0, donde 1.0 es probablemente una buena interacción). Solo se usa cuando captcha-type es GOOGLE_RECAPTCHA_V3. Por defecto es `0.5`.                               |
-| `--reset-token-expiration-hours`                     | El tiempo de expiración en horas del Token de Restablecimiento. Por defecto es `24`.                                                                                                                                        |
-| `--scheduler-payment-job-seconds`                    | El intervalo en segundos para los trabajos de pagos que sincronizan transacciones entre SDP y TSS. Debe ser mayor que 5 segundos. Por defecto es `30`.                                                                      |
-| `--scheduler-receiver-invitation-job-seconds`        | El intervalo en segundos para el trabajo de invitaciones a receptores que envía invitaciones a nuevos receptores. Debe ser mayor que 5 segundos. Por defecto es `30`.                                                       |
-| `--sep10-client-attribution-required`                | Si es verdadero, la autenticación SEP-10 requiere que client_domain sea provisto y validado. Si es falso, client_domain es opcional. Por defecto es `true`.                                                                 |
-| `--sep10-signing-private-key`                        | La clave privada de la cuenta Stellar que firma las transacciones SEP-10. También se usa para firmar URLs.                                                                                                                  |
-| `--sep10-signing-public-key`                         | La clave pública de la cuenta Stellar que firma las transacciones SEP-10. También se usa para firmar URLs.                                                                                                                  |
-| `--sep24-jwt-secret`                                 | El secreto JWT usado para firmar el token JWT SEP-24.                                                                                                                                                                       |
-| `--single-tenant-mode`                               | Esta opción habilita la función de Modo de Tenant Único. En casos donde no se requiere multi-tenancy, esta opción omite la resolución del tenant resolviendo siempre al tenant por defecto configurado en la base de datos. |
-| `--sms-sender-type`                                  | Tipo de remitente SMS. Opciones: `DRY_RUN`, `TWILIO_SMS`, `TWILIO_WHATSAPP`, `AWS_SMS`. Por defecto es `DRY_RUN`.                                                                                                           |
-| `--tenant-xlm-bootstrap-amount`                      | La cantidad del activo nativo que será enviada a la cuenta de distribución del tenant desde la cuenta de distribución del host cuando se cree, si aplica. Por defecto es `5`.                                               |
-| `--twilio-account-sid`                               | El SID de la cuenta Twilio.                                                                                                                                                                                                 |
-| `--twilio-auth-token`                                | El token de autenticación de la cuenta Twilio.                                                                                                                                                                              |
-| `--twilio-sendgrid-api-key`                          | La clave API de la cuenta Twilio SendGrid.                                                                                                                                                                                  |
-| `--twilio-sendgrid-sender-address`                   | La dirección de correo electrónico que Twilio SendGrid usará para enviar emails.                                                                                                                                            |
-| `--twilio-service-sid`                               | El ID de servicio usado dentro de Twilio para enviar mensajes.                                                                                                                                                              |
-| `--twilio-whatsapp-from-number`                      | El número de WhatsApp Business usado para enviar mensajes (con prefijo whatsapp:).                                                                                                                                          |
-| `--twilio-whatsapp-receiver-invitation-template-sid` | El SID de contenido de Twilio para la plantilla de invitación de receptor en WhatsApp (comienza con HX).                                                                                                                    |
-| `--twilio-whatsapp-receiver-otp-template-sid`        | El SID de contenido de Twilio para la plantilla OTP de receptor en WhatsApp (comienza con HX).                                                                                                                              |
-
-## Comando TSS
-
-El comando `tss` ejecuta el Servicio de Envío de Transacciones, responsable de enviar transacciones a la red Stellar.
-
-### Uso
-
-```bash
-stellar-disbursement-platform tss [flags]
-```
-
-### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                                        |
-| :--------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Una clave privada ed25519 compatible con Stellar usada para encriptar/desencriptar las claves privadas de las cuentas canal. Si no está configurada, por defecto tomará el valor de la opción `distribution-seed`. |
-| `--crash-tracker-type`                         | Tipo de rastreador de fallos. Opciones: `SENTRY`, `DRY_RUN`. Por defecto es `DRY_RUN`.                                                                                                                             |
-| `--db-conn-max-idle-time-seconds`              | Tiempo máximo inactivo en segundos antes de que se cierre una conexión. Por defecto es `10`.                                                                                                                       |
-| `--db-conn-max-lifetime-seconds`               | Tiempo máximo de vida en segundos para una sola conexión. Por defecto es `300`.                                                                                                                                    |
-| `--db-max-idle-conns`                          | Número máximo de conexiones inactivas a la base de datos que se mantienen por pool. Por defecto es `2`.                                                                                                            |
-| `--db-max-open-conns`                          | Número máximo de conexiones abiertas a la base de datos por pool. Por defecto es `20`.                                                                                                                             |
-| `--distribution-account-encryption-passphrase` | Una clave privada ed25519 compatible con Stellar usada para encriptar y desencriptar las claves privadas de las cuentas de distribución de los tenants.                                                            |
-| `--distribution-public-key`                    | La clave pública de la cuenta de distribución Stellar del HOST, usada para crear cuentas canal.                                                                                                                    |
-| `--distribution-seed`                          | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas canal.                                                                                                                    |
-| `--horizon-url`                                | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                                               |
-| `--max-base-fee`                               | La cuota base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                                                  |
-| `--num-channel-accounts`                       | Número de cuentas canal a utilizar para el envío de transacciones. Por defecto es `2`.                                                                                                                             |
-| `--queue-polling-interval`                     | Intervalo de sondeo (segundos) para consultar la base de datos en busca de transacciones pendientes a procesar. Por defecto es `6`.                                                                                |
-| `--tss-metrics-port`                           | Puerto donde el servidor de métricas estará escuchando. Por defecto es `9002`.                                                                                                                                     |
-| `--tss-metrics-type`                           | Tipo de monitor de métricas. Opciones: `TSS_PROMETHEUS`. Por defecto es `TSS_PROMETHEUS`.                                                                                                                          |
-
-## Comando DB
-
-El comando `db` proporciona utilidades para la gestión y migraciones de bases de datos. Realiza dos funciones principales:
-
-1. Ejecutar migraciones de bases de datos para varios esquemas (admin, auth, sdp, tss).
-2. Configurar activos y carteras basadas en la frase de contraseña de la red.
-
-### Uso
-
-```bash
-stellar-disbursement-platform db [command] [flags]
-```
-
-### Subcomandos
-
-| Comando             | Descripción                                                               |
-| :------------------ | :------------------------------------------------------------------------ |
-| `admin`             | Migraciones admin para el módulo multi-tenant.                            |
-| `auth`              | Migraciones del esquema de autenticación.                                 |
-| `sdp`               | Migraciones del esquema SDP.                                              |
-| `setup-for-network` | Configura activos y carteras basadas en la frase de contraseña de la red. |
-| `tss`               | Migraciones del esquema TSS.                                              |
-
----
-
-### DB Admin
-
-El comando `db admin` gestiona las migraciones para el esquema admin, el cual maneja la configuración multi-tenancy.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db admin [command] [flags]
-```
-
-#### Subcomandos
-
-| Comando   | Descripción                             |
-| :-------- | :-------------------------------------- |
-| `migrate` | Ayudantes para migraciones de esquemas. |
-
-#### DB Admin Migrate
-
-El comando `migrate` permite ejecutar migraciones hacia arriba o hacia abajo.
-
-**Uso**
-
-```bash
-stellar-disbursement-platform db admin migrate [command] [flags]
-```
-
-**Subcomandos**
-
-| Comando | Descripción                                               |
-| :------ | :-------------------------------------------------------- |
-| `up`    | Migra la base de datos hacia arriba [count] migraciones   |
-| `down`  | Migra la base de datos hacia abajo [count] migraciones    |
-
-**Ejemplos**
-
-```bash
-# Apply all pending migrations
-stellar-disbursement-platform db admin migrate up
-
-# Apply the next 2 migrations
-stellar-disbursement-platform db admin migrate up 2
-
-# Revert the last migration
-stellar-disbursement-platform db admin migrate down 1
-```
-
----
-
-### DB Auth
-
-El comando `db auth` gestiona las migraciones para el esquema de autenticación.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db auth [command] [flags]
-```
-
-#### Flags
-
-| Flag          | Descripción                                                                                                                                               |
-| :------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--all`       | Aplica el comando a todos los tenants. Debe establecerse `--tenant-id` o `--all`, pero la opción `--all` será ignorada si `--tenant-id` está configurado. |
-| `--tenant-id` | El ID del tenant donde se aplicará el comando.                                                                                                            |
-
-#### Subcomandos
-
-| Comando   | Descripción                             |
-| :-------- | :-------------------------------------- |
-| `migrate` | Ayudantes para migraciones de esquemas. |
-
-#### DB Auth Migrate
-
-Similar a `admin migrate`, este comando acepta los subcomandos `up` y `down`.
-
-**Ejemplos**
-
-```bash
-# Apply migrations for a specific tenant
-stellar-disbursement-platform db auth migrate up --tenant-id <tenant-id>
-
-# Apply migrations for all tenants
-stellar-disbursement-platform db auth migrate up --all
-```
-
----
-
-### DB SDP
-
-El comando `db sdp` gestiona las migraciones para el esquema SDP (Stellar Disbursement Platform), que contiene las tablas de lógica de negocio principal.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db sdp [command] [flags]
-```
-
-#### Flags
-
-| Flag          | Descripción                                                                                                                                               |
-| :------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--all`       | Aplica el comando a todos los tenants. Debe establecerse `--tenant-id` o `--all`, pero la opción `--all` será ignorada si `--tenant-id` está configurado. |
-| `--tenant-id` | El ID del tenant donde se aplicará el comando.                                                                                                            |
-
-#### Subcomandos
-
-| Comando   | Descripción                             |
-| :-------- | :-------------------------------------- |
-| `migrate` | Ayudantes para migraciones de esquemas. |
-
-#### DB SDP Migrate
-
-Similar a `admin migrate`, este comando acepta los subcomandos `up` y `down`.
-
-**Ejemplos**
-
-```bash
-# Apply migrations for a specific tenant
-stellar-disbursement-platform db sdp migrate up --tenant-id <tenant-id>
-
-# Apply migrations for all tenants
-stellar-disbursement-platform db sdp migrate up --all
-```
-
----
-
-### DB TSS
-
-El comando `db tss` gestiona las migraciones para el esquema TSS (Transaction Submission Service).
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db tss [command] [flags]
-```
-
-#### Subcomandos
-
-| Comando   | Descripción                             |
-| :-------- | :-------------------------------------- |
-| `migrate` | Ayudantes para migraciones de esquemas. |
-
-#### DB TSS Migrate
-
-Similar a `admin migrate`, este comando acepta los subcomandos `up` y `down`.
-
-**Ejemplos**
-
-```bash
-# Apply all pending migrations
-stellar-disbursement-platform db tss migrate up
-```
-
----
-
-### DB Setup For Network
-
-El comando `db setup-for-network` configura los activos y carteras registrados en la base de datos basados en la frase de contraseña de la red. Inserta o actualiza las entradas de estas tablas según la Frase de Contraseña de Red configurada.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db setup-for-network [flags]
-```
-
-#### Flags
-
-| Flag          | Descripción                                                                                                                                               |
-| :------------ | :-------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--all`       | Aplica el comando a todos los tenants. Debe establecerse `--tenant-id` o `--all`, pero la opción `--all` será ignorada si `--tenant-id` está configurado. |
-| `--tenant-id` | El ID del tenant donde se aplicará el comando.                                                                                                            |
-
-#### Ejemplo
-
-```bash
-# Setup for a specific tenant
-stellar-disbursement-platform db setup-for-network --tenant-id <tenant-id>
-
-# Setup for all tenants
-stellar-disbursement-platform db setup-for-network --all
-```
-
-## Comando Auth
-
-El comando `auth` ofrece ayudantes para la gestión de autenticación, específicamente para añadir usuarios al sistema.
-
-### Uso
-
-```bash
-stellar-disbursement-platform auth [command] [flags]
-```
-
-### Subcomandos
-
-| Comando    | Descripción                 |
-| :--------- | :-------------------------- |
-| `add-user` | Agregar usuario al sistema. |
-
----
-
-### Auth Add User
-
-El comando `auth add-user` agrega un nuevo usuario al sistema. El correo electrónico debe ser único y la contraseña debe tener al menos 12 caracteres.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform auth add-user <email> <first name> <last name> [flags]
-```
-
-#### Flags
-
-| Flag          | Descripción                                                                                                                                                                                    |
-| :------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--owner`     | Establecer el usuario como Propietario (superusuario). Por defecto es "false".                                                                                                                 |
-| `--password`  | Establece la contraseña del usuario. Debe tener al menos 12 caracteres. Si se omite, el comando generará una aleatoria.                                                                        |
-| `--roles`     | Establece los roles del usuario. Debe estar separado por comas. Ejemplo: `role1, role2`. Roles disponibles: `owner`, `financial_controller`, `developer`, `business`, `initiator`, `approver`. |
-| `--tenant-id` | El ID del tenant al que se añadirá el usuario.                                                                                                                                                 |
-
-#### Ejemplo
-
-Para añadir un usuario nuevo con roles específicos y una contraseña:
-
-```bash
-stellar-disbursement-platform auth add-user mary.jane@stellar.org Mary Jane \
---roles approver,initiator --password \
---tenant-id 'f347e6b0-249c-4960-b0d2-aebcf4c6a60d'
-```
-
-## Comando Channel Accounts
-
-El comando `channel-accounts` gestiona las cuentas de canal utilizadas para el envío de transacciones.
-
-### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts [command] [flags]
-```
-
-### Flags
-
-| Flag                        | Descripción                                                                                        |
-| :-------------------------- | :------------------------------------------------------------------------------------------------- |
-| `--crash-tracker-type`      | Tipo de rastreador de fallos. Opciones: `SENTRY`, `DRY_RUN`. Por defecto `DRY_RUN`.                |
-| `--distribution-public-key` | La clave pública de la cuenta Stellar de distribución del HOST, usada para crear cuentas de canal. |
-| `--tss-metrics-port`        | Puerto donde el servidor de métricas pondrá a escuchar. Por defecto `9002`.                        |
-| `--tss-metrics-type`        | Tipo de monitor de métricas. Opciones: `TSS_PROMETHEUS`. Por defecto `TSS_PROMETHEUS`.             |
-
-### Subcomandos
-
-| Comando  | Descripción                                                         |
-| :------- | :------------------------------------------------------------------ |
-| `create` | Crear cuentas de canal.                                             |
-| `delete` | Eliminar una cuenta de canal específica.                            |
-| `ensure` | Asegurar que existe un número específico de cuentas de canal.       |
-| `verify` | Verificar que las cuentas de canal existen en la red.               |
-| `view`   | Listar las claves públicas de todas las cuentas de canal.           |
-
----
-
-### Crear cuentas Channel Accounts
-
-El comando `create` crea cuentas de canal.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts create [count] [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                           |
-| :--------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Una clave privada ed25519 compatible con Stellar, usada para encriptar/descifrar las claves privadas de las cuentas de canal. Si no se establece, se usará el valor de la opción `distribution-seed`. |
-| `--distribution-account-encryption-passphrase` | Una clave privada ed25519 compatible con Stellar, utilizada para encriptar y desencriptar las claves privadas de las cuentas de distribución de los tenants.                                          |
-| `--distribution-seed`                          | La clave privada de la cuenta Stellar de distribución del HOST, usada para crear cuentas de canal.                                                                                                    |
-| `--horizon-url`                                | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto `https://horizon-testnet.stellar.org/`.                                                                     |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto `10000`.                                                                                                                       |
-
----
-
-### Eliminar cuentas Channel Accounts
-
-El comando `delete` elimina una cuenta de canal especificada del almacenamiento y de la red.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts delete [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                           |
-| :--------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Una clave privada ed25519 compatible con Stellar, usada para encriptar/descifrar las claves privadas de las cuentas de canal. Si no se establece, se usará el valor de la opción `distribution-seed`. |
-| `--channel-account-id`                         | El ID de la cuenta de canal a eliminar.                                                                                                                                                               |
-| `--delete-all-accounts`                        | Eliminar todas las cuentas de canal gestionadas en la base de datos y en la red.                                                                                                                      |
-| `--distribution-account-encryption-passphrase` | Una clave privada ed25519 compatible con Stellar, utilizada para encriptar y desencriptar las claves privadas de las cuentas de distribución de los tenants.                                          |
-| `--distribution-seed`                          | La clave privada de la cuenta Stellar de distribución del HOST, usada para crear cuentas de canal.                                                                                                    |
-| `--horizon-url`                                | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto `https://horizon-testnet.stellar.org/`.                                                                     |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto `10000`.                                                                                                                       |
-
----
-
-### Asegurar cuentas Channel Accounts
-
-El comando `ensure` asegura que exista el número especificado de cuentas de canal. Si no existen, las creará. Si existen más cuentas de canal de las especificadas, eliminará las cuentas en exceso.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts ensure <count> [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                           |
-| :--------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Una clave privada ed25519 compatible con Stellar, usada para encriptar/descifrar las claves privadas de las cuentas de canal. Si no se establece, se usará el valor de la opción `distribution-seed`. |
-| `--distribution-account-encryption-passphrase` | Una clave privada ed25519 compatible con Stellar, usada para encriptar y desencriptar las claves privadas de las cuentas de distribución de los tenants.                                              |
-| `--distribution-seed`                          | La clave privada de la cuenta Stellar de distribución del HOST, usada para crear cuentas de canal.                                                                                                    |
-| `--horizon-url`                                | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto `https://horizon-testnet.stellar.org/`.                                                                     |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto `10000`.                                                                                                                       |
-
-#### Ejemplo
-
-```bash
-stellar-disbursement-platform channel-accounts ensure 5
-```
-
----
-
-### Verificar cuentas Channel Accounts
-
-El comando `verify` verifica que todas las cuentas de canal en la base de datos existan en la red Stellar.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts verify [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                        |
-| :--------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Una clave privada ed25519 compatible con Stellar, usada para encriptar/descifrar las claves privadas de las cuentas de canal. Si no se establece, usará el valor de la opción `distribution-seed`. |
-| `--delete-invalid-accounts`                    | Eliminar cuentas de canal del almacenamiento que hayan sido verificadas como inválidas en la red.                                                                                                  |
-| `--distribution-account-encryption-passphrase` | Una clave privada ed25519 compatible con Stellar, usada para encriptar y desencriptar las claves privadas de las cuentas de distribución de los tenants.                                           |
-| `--distribution-seed`                          | La clave privada de la cuenta Stellar de distribución del HOST, usada para crear cuentas de canal.                                                                                                 |
-| `--horizon-url`                                | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto `https://horizon-testnet.stellar.org/`.                                                                  |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto `10000`.                                                                                                                    |
-
----
-
-### Ver cuentas Channel Accounts
-
-El comando `view` lista las claves públicas de todas las cuentas de canal almacenadas actualmente en la base de datos.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts view [flags]
-```
-
-## Comando Distribution Account
-
-El comando `distribution-account` gestiona la cuenta de distribución.
-
-### Uso
-
-```bash
-stellar-disbursement-platform distribution-account [command] [flags]
-```
-
-### Flags
-
-| Flag                        | Descripción                                                                                        |
-| :-------------------------- | :------------------------------------------------------------------------------------------------- |
-| `--crash-tracker-type`      | Tipo de rastreador de fallos. Opciones: `SENTRY`, `DRY_RUN`. Por defecto `DRY_RUN`.                |
-| `--distribution-public-key` | La clave pública de la cuenta Stellar de distribución del HOST, usada para crear cuentas de canal. |
-
-### Subcomandos
-
-| Comando  | Descripción                                     |
-| :------- | :---------------------------------------------- |
-| `rotate` | Rotar la cuenta de distribución para un tenant. |
-
----
-
-### Rotar cuenta Distribution Account
-
-El comando `rotate` rota la cuenta de distribución para un tenant.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform distribution-account rotate [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                        |
-| :--------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Una clave privada ed25519 compatible con Stellar, usada para encriptar/descifrar las claves privadas de las cuentas de canal. Si no se establece, usará el valor de la opción `distribution-seed`. |
-| `--distribution-account-encryption-passphrase` | Una clave privada ed25519 compatible con Stellar, usada para encriptar y desencriptar las claves privadas de las cuentas de distribución de los tenants.                                           |
-| `--distribution-seed`                          | La clave privada de la cuenta Stellar de distribución del HOST, usada para crear cuentas de canal.                                                                                                 |
-| `--horizon-url`                                | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto `https://horizon-testnet.stellar.org/`.                                                                  |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto `10000`.                                                                                                                    |
-| `--tenant-id`                                  | El ID del tenant donde se aplicará el comando.                                                                                                                                                     |
-| `--tenant-xlm-bootstrap-amount`                | La cantidad del activo nativo que se enviará a la cuenta de distribución del tenant desde la cuenta de distribución del host cuando se cree, si es aplicable. Por defecto `5`.                     |
-
-#### Ejemplo
-
-Para rotar la cuenta de distribución de un tenant específico:
-
-```bash
-stellar-disbursement-platform distribution-account rotate --tenant-id 'f347e6b0-249c-4960-b0d2-aebcf4c6a60d'
-```
-
-## Comando Message
-
-El comando `message` ofrece comandos relacionados con el mensajero.
-
-### Uso
-
-```bash
-stellar-disbursement-platform message [command] [flags]
-```
-
-### Flags
-
-| Flag                                                 | Descripción                                                                                                                 |
-| :--------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------- |
-| `--aws-access-key-id`                                | El ID de clave de acceso AWS.                                                                                               |
-| `--aws-region`                                       | La región AWS.                                                                                                              |
-| `--aws-secret-access-key`                            | La clave secreta de acceso AWS.                                                                                             |
-| `--aws-ses-sender-id`                                | La dirección de email que AWS usará para enviar correos. Usa AWS SES.                                                       |
-| `--aws-sns-sender-id`                                | El ID del remitente de la cuenta AWS que envía el mensaje SMS. Usa AWS SNS.                                                 |
-| `--message-sender-type`                              | Tipo de remitente de mensaje. Opciones: `TWILIO_SMS`, `TWILIO_WHATSAPP`, `TWILIO_EMAIL`, `AWS_SMS`, `AWS_EMAIL`, `DRY_RUN`. |
-| `--twilio-account-sid`                               | El SID de la cuenta Twilio.                                                                                                 |
-| `--twilio-auth-token`                                | El token de autenticación de la cuenta Twilio.                                                                              |
-| `--twilio-sendgrid-api-key`                          | La clave API de la cuenta Twilio SendGrid.                                                                                  |
-| `--twilio-sendgrid-sender-address`                   | La dirección de email que Twilio SendGrid usará para enviar correos.                                                        |
-| `--twilio-service-sid`                               | El ID del servicio usado en Twilio para enviar mensajes.                                                                    |
-| `--twilio-whatsapp-from-number`                      | El número de WhatsApp Business usado para enviar mensajes (con prefijo `whatsapp:`).                                        |
-| `--twilio-whatsapp-receiver-invitation-template-sid` | El SID de contenido Twilio para la plantilla de invitación de receptor WhatsApp (comienza con HX).                          |
-| `--twilio-whatsapp-receiver-otp-template-sid`        | El SID de contenido Twilio para la plantilla OTP de receptor WhatsApp (comienza con HX).                                    |
-
-### Subcomandos
-
-| Comando | Descripción        |
-| :------ | :----------------- |
-| `send`  | Enviar un mensaje. |
-
----
-
-### Enviar mensaje Message Send
-
-El comando `send` envía un mensaje a un destinatario.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform message send [flags]
-```
-
-#### Flags
-
-| Flag             | Descripción                                                                                       |
-| :--------------- | :------------------------------------------------------------------------------------------------ |
-| `--email`        | El correo electrónico al que enviar el mensaje. Obligatorio si se envía un email.                 |
-| `--message`      | El texto del mensaje a enviar.                                                                    |
-| `--phone-number` | El número de teléfono al que enviar el mensaje, en formato E.164. Obligatorio si se envía un SMS. |
-| `--title`        | El título que se establecerá en el email. Obligatorio si se envía un email.                       |
-
-#### Ejemplo
-
-```bash
-# Send an SMS
-stellar-disbursement-platform message send --phone-number "+1234567890" --message "Hello World" --message-sender-type TWILIO_SMS
-
-# Send an Email
-stellar-disbursement-platform message send --email "user@example.com" --title "Hello" --message "Hello World" --message-sender-type AWS_EMAIL
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/configuring-sdp.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/configuring-sdp.mdx
deleted file mode 100644
index 1d14325e6b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/configuring-sdp.mdx
+++ /dev/null
@@ -1,241 +0,0 @@
----
-title: Configuración
-description: Comprender las opciones de configuración disponibles para la Stellar Disbursement Platform (SDP)
-keywords:
-  - SDP
-  - configuration
-sidebar_position: 40
----
-
-Los servicios de la Stellar Disbursement Platform se pueden configurar utilizando un conjunto de opciones de configuración que se pasan a la línea de comandos o se establecen como variables de entorno. Dependiendo de cómo estés utilizando y desplegando la SDP, estas configuraciones pueden establecerse en un ConfigMap en Kubernetes, como variables de entorno en un contenedor de Docker, pasadas como argumentos de línea de comandos, etc.
-
-En esta sección, discutiremos las diferentes opciones de configuración disponibles para la SDP.
-
-:::tip[Notes]
-
-- Las configuraciones etiquetadas con 🔑 son sensibles y deben almacenarse de forma segura.
-- Todas las configuraciones se pueden pasar como variables de entorno o como flags de CLI. Por ejemplo, la variable de entorno `BASE_URL` podría pasarse a través del flag `--base-url`. Los flags de CLI tienen prioridad sobre las variables de entorno, aunque las variables de entorno son más convenientes.
-
-:::
-
-## Servicio Central de la SDP
-
-Para la configuración más actualizada, puedes ejecutar el siguiente comando en el [repositorio git de stellar-disbursement-platform-backend](https://github.com/stellar/stellar-disbursement-platform-backend):
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform serve --help
-```
-
-</CodeExample>
-
-### Configuración Operativa
-
-La Configuración Operativa permite controlar métricas, registros y otros aspectos operativos del Servicio Central de la SDP.
-
-- `PORT` - El puerto en el que el Servicio Central de la SDP escuchará las solicitudes HTTP entrantes. Por defecto: 8000.
-- `LOG_LEVEL` - Determina el nivel de verbosidad de los registros. Opciones: "TRACE", "DEBUG", "INFO", "WARN", "ERROR", "FATAL", o "PANIC". Por defecto: "TRACE".
-- `METRICS_PORT` - El puerto en el que el Servicio Central de la SDP expondrá sus métricas. Por defecto: 8002.
-- `METRICS_TYPE` - El tipo de métricas a exponer. Opciones: "PROMETHEUS". Por defecto: "PROMETHEUS".
-- `CRASH_TRACKER_TYPE` - El tipo de rastreador de fallos a utilizar. Opciones: "SENTRY", "DRY_RUN". Por defecto: "DRY_RUN".
-- `SENTRY_DSN` - 🔑 La DSN (clave de cliente) del proyecto de Sentry. Si no se proporciona, Sentry no se utilizará.
-- `ENVIRONMENT` - El entorno en el que se está ejecutando la aplicación. Ejemplo: "development", "staging", "production". Por defecto: "development".
-- `BASE_URL` - La URL base del servidor backend de la SDP. Por defecto: "http://localhost:8000". Las URLs específicas del inquilino se configurarán durante el [proceso de provisión del inquilino](./advanced-configration#provisioning-tenants).
-- `SDP_UI_BASE_URL` - La URL base de la interfaz de usuario/dashboard de la SDP utilizada para enviar el enlace de invitación cuando se crea un nuevo usuario. Las URLs específicas del inquilino se configurarán durante el [proceso de provisión del inquilino](./advanced-configration#provisioning-tenants).
-
-### Configuración de la base de datos
-
-Las siguientes configuraciones están relacionadas con la base de datos PostgreSQL utilizada por el servicio SDP Core.
-
-- `DATABASE_URL` - 🔑 La cadena de conexión para la base de datos PostgreSQL. El formato es `postgres://username:password@host:port/database?sslmode=disable`. Por defecto: "postgres://localhost:5432/sdp?sslmode=disable".
-- `DB_MAX_OPEN_CONNS` - Conexiones máximas abiertas por pool a la base de datos. Por defecto: 20.
-- `DB_MAX_IDLE_CONNS` - Conexiones inactivas máximas retenidas en el pool. Por defecto: 2.
-- `DB_CONN_MAX_IDLE_TIME_SECONDS` - Cierra las conexiones inactivas después de N segundos. Por defecto: 10.
-- `DB_CONN_MAX_LIFETIME_SECONDS` - Recicla las conexiones después de N segundos. Por defecto: 300.
-
-### Configuración de Mensajería
-
-Messaging Configuration allows configuring the messaging service used to send messages to recipients and sdp dashboard users. La configuración por defecto está establecida en "DRY_RUN", lo que significa que no se enviarán mensajes y los mensajes se registrarán en la consola. Esto se recomienda solo para fines de prueba.
-
-- `EMAIL_SENDER_TYPE`: El tipo de mensajero utilizado para enviar invitaciones a nuevos usuarios del panel. Opciones: "DRY_RUN", "TWILIO_EMAIL", "AWS_EMAIL". Por defecto: "DRY_RUN".
-- `SMS_SENDER_TYPE`: El tipo de mensajero utilizado para enviar mensajes SMS a los destinatarios. Opciones: "DRY_RUN", "TWILIO_SMS", "TWILIO_WHATSAPP", "AWS_SMS". Por defecto: "DRY_RUN".
-
-#### Configuración de AWS
-
-Las siguientes configuraciones son requeridas al usar AWS SES o SNS para enviar correos electrónicos o mensajes SMS.
-
-- `AWS_ACCESS_KEY_ID` - 🔑 La ID de clave de acceso de AWS.
-- `AWS_REGION` - La región de AWS donde está disponible el servicio SES.
-- `AWS_SECRET_ACCESS_KEY` - 🔑 La clave de acceso secreto de AWS.
-- `AWS_SES_SENDER_ID` - El correo electrónico que AWS SES utilizará como remitente al enviar correos electrónicos. Requerido cuando `EMAIL_SENDER_TYPE` se establece en "AWS_EMAIL".
-- `AWS_SNS_SENDER_ID` - La ID del remitente a utilizar al enviar mensajes SMS utilizando AWS SNS. Requerido cuando `SMS_SENDER_TYPE` se establece en "AWS_SMS".
-
-#### Configuración de Twilio
-
-Las siguientes configuraciones son requeridas cuando `SMS_SENDER_TYPE=TWILIO_SMS`.
-
-- `TWILIO_ACCOUNT_SID` - 🔑 El SID de la cuenta de Twilio.
-- `TWILIO_AUTH_TOKEN` - 🔑 El token de autenticación de Twilio.
-- `TWILIO_SERVICE_SID` - El SID del servicio de Twilio.
-
-Las siguientes configuraciones son obligatorias cuando `SMS_SENDER_TYPE=TWILIO_WHATSAPP`.
-
-- `TWILIO_ACCOUNT_SID` - 🔑 El SID de la cuenta de Twilio.
-- `TWILIO_AUTH_TOKEN` - 🔑 El token de autenticación de Twilio.
-- `TWILIO_SERVICE_SID` - El SID del servicio de Twilio.
-- `TWILIO_WHATSAPP_FROM_NUMBER` - El número de WhatsApp Business utilizado para enviar mensajes (con el prefijo whatsapp:).
-- `TWILIO_WHATSAPP_RECEIVER_INVITATION_TEMPLATE_SID` - El SID de contenido de Twilio para la plantilla de invitación de receptor de WhatsApp (comienza con HX).
-- `TWILIO_WHATSAPP_RECEIVER_OTP_TEMPLATE_SID` - El SID de contenido de Twilio para la plantilla OTP de receptor de WhatsApp (comienza con HX).
-
-Las siguientes configuraciones son requeridas cuando `EMAIL_SENDER_TYPE=TWILIO_EMAIL`.
-
-- `TWILIO_SENDGRID_API_KEY` - 🔑 La clave API para el servicio de Twilio SendGrid (correo electrónico).
-- `TWILIO_SENDGRID_SENDER_ADDRESS` - La dirección de correo electrónico utilizada para enviar correos electrónicos a través de Twilio SendGrid.
-
-#### Configuración General de Mensajería
-
-- `MAX_INVITATION_RESEND_ATTEMPTS` - El número máximo de intentos para (auto) reenviar la invitación a las billeteras de los receptores. Por defecto: 3.
-
-### Configuración de Stellar
-
-La Configuración de Stellar permite configurar cuentas, transacciones y otros ajustes relacionados con Stellar.
-
-- `NETWORK_PASSPHRASE` - La frase de paso de la red Stellar. Por defecto "Test SDF Network ; September 2015".
-- `HORIZON_URL` - La URL del servidor Horizon a utilizar para enviar transacciones. Por defecto "https://horizon-testnet.stellar.org/".
-- `SEP10_SIGNING_PUBLIC_KEY` - La clave pública de la cuenta Stellar que firma las transacciones SEP-10. También se utiliza para firmar URLs.
-- `SEP10_SIGNING_PRIVATE_KEY` - 🔑 La clave privada de la cuenta Stellar que firma las transacciones SEP-10. También se utiliza para firmar URLs.
-- `MAX_BASE_FEE` - La tarifa base máxima para enviar una transacción Stellar. Por defecto: 10000.
-- `SEP10_CLIENT_ATTRIBUTION_REQUIRED` - Determina si se requiere la atribución del cliente SEP-10. Por defecto: true.
-
-#### Configuración de Cuentas de Canal
-
-La siguiente configuración es necesaria para usar el [CLI de channel-accounts](./cli-manual#channel-accounts-command) para gestionar las cuentas de canales.
-
-- `CHANNEL_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 Una clave secreta Stellar ed25519 (que comienza con `S`) usada para encriptar/desencriptar las claves privadas de las cuentas de canal. Si no está configurado, tomará por defecto el valor de `DISTRIBUTION_SEED`.
-
-#### Configuración de Cuentas de Distribución
-
-Las siguientes configuraciones están relacionadas con las cuentas de distribución utilizadas para enviar fondos a los destinatarios. Esta configuración debe coincidir con la configuración en el Servicio Central de la SDP.
-
-- `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 Una clave secreta Stellar ed25519 (que comienza con `S`) usada para cifrar/descifrar las claves privadas de las cuentas de distribución en memoria.
-- `DISTRIBUTION_PUBLIC_KEY` - La clave pública de la cuenta de distribución Stellar del HOST. Se utiliza para distribuir fondos, crear cuentas de canal y cuentas de distribución de inquilinos.
-- `DISTRIBUTION_SEED` - 🔑 La clave privada de la cuenta de distribución Stellar del HOST. Se usa para distribuir fondos, crear cuentas de canal y cuentas de distribución de inquilinos.
-
-### Configuración de Seguridad
-
-La Configuración de Seguridad permite configurar los aspectos de seguridad del Servicio Central de la SDP.
-
-- `CORS_ALLOWED_ORIGINS` - Especifica los dominios permitidos para hacer solicitudes de origen cruzado. "_" significa que se permiten todos los dominios. Los dominios pueden contener caracteres comodín, por ejemplo, "https://_.example.com".
-- `SEP24_JWT_SECRET` - 🔑 El secreto utilizado para firmar el token JWT para transacciones SEP-24. Este secreto se utiliza durante el flujo de registro de billeteras receptoras.
-
-#### Configuración de Autenticación de Dashboard
-
-Las siguientes configuraciones están relacionadas con la autenticación y autorización de usuarios del panel.
-
-- `RESET_TOKEN_EXPIRATION_HOURS` - El tiempo de expiración en horas del token de restablecimiento de contraseña. Por defecto: 24 (horas).
-- `EC256_PUBLIC_KEY` - La clave pública EC256 utilizada para validar la firma del token. Esta clave EC necesita ser al menos tan fuerte como prime256v1 (P-256).
-- `EC256_PRIVATE_KEY` - 🔑 La clave privada EC256 utilizada para firmar el token de autenticación. Esta clave EC necesita ser al menos tan fuerte como prime256v1 (P-256).
-- `DISABLE_MFA` - Deshabilita la Autenticación Multifactor (MFA) para los usuarios del panel de la SDP.
-- `DISABLE_RECAPTCHA` - Deshabilita reCAPTCHA v2 de Google para los usuarios del panel de la SDP. Este flag no afecta el reCAPTCHA utilizado durante el flujo SEP-24.
-
-#### Configuración de Recaptcha
-
-Las siguientes configuraciones son requeridas al usar reCAPTCHA v2 de Google para proteger el Servicio Central de la SDP de bots. ReCaptcha se utiliza tanto para usuarios del panel como para receptores de fondos durante el flujo SEP-24.
-
-- `RECAPTCHA_SITE_KEY` - La clave del sitio reCAPTCHA v2 de Google - No soy un robot.
-- `RECAPTCHA_SITE_SECRET_KEY` - 🔑 La clave secreta del sitio reCAPTCHA utilizada para validar las respuestas de reCAPTCHA.
-
-### Configuración de trabajos en segundo plano
-
-- `SCHEDULER_PAYMENT_JOB_SECONDS`: Intervalo en segundos para el trabajo que sincroniza pagos entre SDP y TSS. El mínimo es 5s.
-- `SCHEDULER_RECEIVER_INVITATION_JOB_SECONDS`: Intervalo en segundos para el trabajo que envía invitaciones a receptores. El mínimo es 5s.
-
-### Configuración de Multi-tenancy
-
-- `ADMIN_ACCOUNT`: El nombre de usuario de la cuenta de administrador usada para autenticar solicitudes HTTP al servidor Admin. Las solicitudes dirigidas al Admin deben agregar el encabezado "Authorization", formateado como `"ADMIN_ACCOUNT:ADMIN_API_KEY"` codificado en Base64.
-- `ADMIN_API_KEY`: La clave api de la cuenta de administrador usada para autenticar solicitudes HTTP al servidor Admin. Las solicitudes dirigidas al Admin deben agregar el encabezado "Authorization", formateado como `"ADMIN_ACCOUNT:ADMIN_API_KEY"` codificado en Base64.
-- `ADMIN_PORT`: el puerto del servidor Admin usado para crear y administrar inquilinos. El valor predeterminado es 8003.
-- `INSTANCE_NAME`: el nombre de la instancia SDP que se mostrará en el archivo `stellar.toml`. Ejemplo: "SDP Testnet".
-- `SINGLE_TENANT_MODE`: Cuando está configurado en `"true"`, habilita el modo de inquilino único, útil para desarrollo local o configuraciones de un solo inquilino. Además de configurarlo en true, deberás configurar el inquilino predeterminado haciendo la solicitud [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx).
-- `TENANT_XLM_BOOTSTRAP_AMOUNT`: La cantidad de XLM que la cuenta Stellar del HOST depositará en la cuenta de distribución del inquilino para el arranque del inquilino.
-
-### Configuración de integración Bridge
-
-Las siguientes configuraciones son necesarias al usar la integración Bridge.
-
-- `ENABLE_BRIDGE_INTEGRATION` - Determina si la integración Bridge está habilitada.
-- `BRIDGE_BASE_URL` - La URL base de la API Bridge. Por defecto: `"https://api.bridge.xyz"`.
-- `BRIDGE_API_KEY` - 🔑 La clave API para la integración Bridge. Requerida si `ENABLE_BRIDGE_INTEGRATION` está configurado como true.
-
-## Servicio de Envío de Transacciones (TSS)
-
-Para la configuración más actualizada, puedes ejecutar el siguiente comando en el [repositorio git de stellar-disbursement-platform-backend](https://github.com/stellar/stellar-disbursement-platform-backend):
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform tss --help
-```
-
-</CodeExample>
-
-### Configuración General
-
-- `QUEUE_POLLING_INTERVAL` - Intervalo de sondeo (segundos) para consultar la base de datos en busca de transacciones pendientes para procesar. Por defecto: 6.
-
-### Configuración Operativa
-
-La Configuración Operativa permite controlar métricas, registros y otros aspectos operativos del Servicio de Envío de Transacciones (TSS)
-
-- `LOG_LEVEL` - Determina el nivel de verbosidad de los registros. Opciones: "TRACE", "DEBUG", "INFO", "WARN", "ERROR", "FATAL", o "PANIC". Por defecto: "TRACE".
-- `TSS_METRICS_PORT` - El puerto en el que el TSS expondrá sus métricas. Por defecto: 9002.
-- `TSS_METRICS_TYPE` - El tipo de métricas a exponer. Opciones: "PROMETHEUS". Por defecto: "PROMETHEUS".
-- `CRASH_TRACKER_TYPE` - El tipo de rastreador de fallos a utilizar. Opciones: "SENTRY", "DRY_RUN". Por defecto: "DRY_RUN".
-- `SENTRY_DSN` - 🔑 La DSN (clave de cliente) del proyecto de Sentry. Si no se proporciona, Sentry no se utilizará.
-- `ENVIRONMENT` - El entorno en el que se está ejecutando la aplicación. Ejemplo: "development", "staging", "production". Por defecto: "development".
-
-### Configuración de la base de datos
-
-Las siguientes configuraciones están relacionadas con la base de datos PostgreSQL utilizada por el servicio SDP Core.
-
-- `DATABASE_URL` - 🔑 La cadena de conexión para la base de datos PostgreSQL. El formato es `postgres://username:password@host:port/database?sslmode=disable`. Por defecto: "postgres://localhost:5432/sdp?sslmode=disable".
-- `DB_MAX_OPEN_CONNS` - Conexiones máximas abiertas por pool a la base de datos. Por defecto: 20.
-- `DB_MAX_IDLE_CONNS` - Conexiones inactivas máximas retenidas en el pool. Por defecto: 2.
-- `DB_CONN_MAX_IDLE_TIME_SECONDS` - Cierra las conexiones inactivas después de N segundos. Por defecto: 10.
-- `DB_CONN_MAX_LIFETIME_SECONDS` - Recicla las conexiones después de N segundos. Por defecto: 300.
-
-### Configuración de Stellar
-
-La Configuración de Stellar permite configurar cuentas, transacciones y otros ajustes relacionados con Stellar.
-
-- `NETWORK_PASSPHRASE` - La frase de paso de la red Stellar. Por defecto "Test SDF Network ; September 2015".
-- `HORIZON_URL` - La URL del servidor Horizon a utilizar para enviar transacciones. Por defecto "https://horizon-testnet.stellar.org/".
-- `MAX_BASE_FEE` - La tarifa base máxima para enviar una transacción Stellar. Por defecto: 10000.
-
-#### Configuración de cuentas de canal
-
-Las siguientes configuraciones son requeridas para usar cuentas de canal para enviar transacciones a la red Stellar.
-
-- `NUM_CHANNEL_ACCOUNTS` - Número de cuentas de canal a utilizar para el envío de transacciones. Por defecto: 2.
-- `CHANNEL_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 Una clave secreta Stellar ed25519 (que comienza con `S`) usada para cifrar/descifrar las claves privadas de las cuentas de canal. Cuando no se establece, se configurará con el valor de la opción 'DISTRIBUTION_SEED'.
-
-#### Configuración de cuentas de distribución
-
-Las siguientes configuraciones están relacionadas con las cuentas de distribución usadas para enviar fondos a los destinatarios. Esta configuración debe coincidir con la configuración en el Servicio Central SDP.
-
-- `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 Una clave secreta Stellar ed25519 (que comienza con `S`) usada para encriptar/desencriptar las claves privadas en memoria de las cuentas de distribución.
-- `DISTRIBUTION_PUBLIC_KEY` - La clave pública de la cuenta de distribución Stellar del HOST. Se usa para distribuir fondos, crear cuentas de canal y cuentas de distribución de inquilinos.
-- `DISTRIBUTION_SEED` - 🔑 La clave privada de la cuenta de distribución Stellar del HOST. Se usa para distribuir fondos, crear cuentas de canal y cuentas de distribución de inquilinos.
-
-## Tablero
-
-El Tablero de SDP es una aplicación web que permite a los usuarios gestionar sus cuentas, ver el historial de transacciones, y más. Las variables de entorno pueden establecerse ya sea en un objeto global `window._env_` o como variables `process.env`. Todas las variables de entorno utilizadas en este repositorio están en el archivo `src/constants/envVariables.ts`, incluyendo tipos. La ubicación predeterminada del objeto `window._env_` es `public/settings/env-config.js`.
-
-### Configuración General
-
-- `API_URL` - La URL base del Servicio Núcleo de SDP. Predeterminado: "http://localhost:8000".
-- `STELLAR_EXPERT_URL` - La URL base del explorador Stellar Expert. Predeterminado: "https://stellar.expert/explorer/testnet".
-- `HORIZON_URL` - La URL base del servidor Horizon. Predeterminado: "https://horizon-testnet.stellar.org".
-- `RECAPTCHA_SITE_KEY` - La clave del sitio de Google reCAPTCHA v2 - No soy un robot. Esta clave necesita igualar la clave utilizada en el Servicio Núcleo de SDP.
-- `SINGLE_TENANT_MODE` - Cuando está configurado en `"true"`, habilita el modo de un solo inquilino, útil para desarrollo local o configuraciones de un solo inquilino. Además de configurarlo en true, deberás configurar el inquilino predeterminado llamando a la solicitud [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx). Por defecto: "false".
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/deploy-the-sdp.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/deploy-the-sdp.mdx
deleted file mode 100644
index 7a8d275365..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/deploy-the-sdp.mdx
+++ /dev/null
@@ -1,112 +0,0 @@
----
-title: Despliegue
-sidebar_position: 30
----
-
-## Despliegue mediante Helm Charts
-
-### Requisitos mínimos del sistema
-
-- **Cuentas Stellar**: Necesitarás una **Cuenta de Distribución** (financiada) y una **Cuenta de Firma SEP-10**.
-- **Certificados**: Al ejecutar el SDP en una configuración multiinquilino, necesitarás adquirir certificados TLS comodín para facilitar la provisión de inquilinos, ya que el SDP depende de subdominios para diferenciar entre ellos. Esto te permitirá provisionar inquilinos sin tener que configurar manualmente certificados TLS para cada inquilino. Puedes usar un servicio como [Let's Encrypt](https://letsencrypt.org/) o [Namecheap](https://www.namecheap.com/security/ssl-certificates/) para adquirir estos certificados.
-
-| Componente     | Requisito | Nota                                                                                    |
-| :------------- | :-------- | :-------------------------------------------------------------------------------------- |
-| **Kubernetes** | v1.19+    | Para despliegue con Helm                                                                |
-| **Helm**       | v3.14.0+  | Para despliegue con Helm                                                                |
-| **PostgreSQL** | v14.0+    | Requerido para ambos métodos de despliegue                                              |
-| **RAM**        | 4GB+      | Memoria mínima recomendada para ejecutar el stack completo en modo de un solo inquilino |
-
-### Instalando el gráfico
-
-#### 1. Agregar el Repositorio Helm de Stellar
-
-Agrega el repositorio oficial de charts de Helm de Stellar a tu cliente local de Helm:
-
-```shell
-helm repo add stellar https://helm.stellar.org/charts
-```
-
-#### 2. Preparar la Configuración
-
-Descarga el archivo de configuración mínima para usarlo como base:
-
-```shell
-curl -LJO https://raw.githubusercontent.com/stellar/stellar-disbursement-platform-backend/main/helmchart/sdp/minimal-values.yaml
-```
-
-Los siguientes parámetros pueden establecerse en el archivo `minimal-values.yaml` o sobrescribirse directamente vía CLI durante la instalación:
-
-- `global.distributionPublicKey`: Clave pública de la cuenta de distribución.
-- `global.distributionPrivateKey`: Clave privada de la cuenta de distribución.
-- `global.sep10PublicKey`: Clave pública para autenticación SEP-10.
-- `global.sep10PrivateKey`: Clave privada para autenticación SEP-10.
-- `global.isPubnet`: Establecer en `true` para Mainnet.
-
-Consulta el [Helm Chart README](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/helmchart/sdp/README.md#parameters) para una lista completa de parámetros.
-
-:::tip
-
-Hay una explicación más detallada sobre cómo configurar el SDP en la [Guía de Configuración](configuring-sdp).
-
-:::
-
-#### 3. Instalar el Chart
-
-Instala el chart usando tu archivo de valores personalizado. Puedes sobrescribir valores directamente vía CLI o modificar el archivo `minimal-values.yaml`.
-
-```shell
-helm install sdp -f minimal-values.yaml stellar/stellar-disbursement-platform \
-     --set "global.distributionPublicKey=<YOUR_KEY>" \
-     --set "global.distributionPrivateKey=<YOUR_SECRET>" \
-     --set "global.sep10PublicKey=<YOUR_KEY>" \
-     --set "global.sep10PrivateKey=<YOUR_SECRET>"
-```
-
-## Despliegue mediante Docker Compose
-
-Esta sección describe cómo desplegar el SDP utilizando Docker Compose para un entorno similar a producción. A diferencia del entorno de desarrollo, esta configuración usa imágenes preconstruidas para producción y requiere una configuración explícita de variables de entorno y secretos.
-
-### Requisitos mínimos del sistema
-
-- **Cuentas Stellar**: Necesitarás una **Cuenta de Distribución** (financiada) y una **Cuenta de Firma SEP-10**.
-- **Acceso a la red**: Acceso saliente a la red Stellar (Horizon/Soroban) y a cualquier integración de terceros (Twilio, AWS SES, etc.).
-
-| Componente | Requisito | Nota                                                       |
-| :--------- | :-------- | :--------------------------------------------------------- |
-| **Docker** | v20.10+   | Requerido para orquestación de contenedores                |
-| **RAM**    | 4GB+      | Memoria mínima recomendada para ejecutar el stack completo |
-
-### Pasos del despliegue
-
-#### 1. Clonar el repositorio
-
-```shell
-git clone https://github.com/stellar/stellar-disbursement-platform-backend.git
-cd stellar-disbursement-platform-backend
-```
-
-#### 2. Crear archivo de entorno
-
-Copia el archivo de entorno de ejemplo.
-
-```shell
-cp dev/.env.example dev/.env
-```
-
-#### 3. Configurar variables de entorno
-
-Edita `dev/.env` y completa las siguientes variables con las claves de tu cuenta Stellar:
-
-- `DISTRIBUTION_PUBLIC_KEY`
-- `DISTRIBUTION_SEED`
-- `SEP10_SIGNING_PUBLIC_KEY`
-- `SEP10_SIGNING_PRIVATE_KEY`
-
-Para despliegue en mainnet, establece: _ `NETWORK_TYPE=pubnet` _ `NETWORK_PASSPHRASE=Public Global Stellar Network ; September 2015` _ `HORIZON_URL=https://horizon.stellar.org` _ `DISABLE_MFA=false` (Aplicado por seguridad)
-
-#### 4. Iniciar los servicios
-
-```shell
-docker compose -f dev/docker-compose.yml up -d
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/design-and-architecture.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/design-and-architecture.mdx
deleted file mode 100644
index 459ba813d5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/design-and-architecture.mdx
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Arquitectura
-sidebar_position: 20
----
-
-La Plataforma de Distribución Stellar consta de tres servicios desplegados juntos:
-
-- **Dashboard**: la interfaz de usuario que utilizan los administradores para iniciar y rastrear el progreso de las distribuciones
-- **SDP Core Service**: el servicio backend central que realiza varias funciones:
-  - **Dashboard API**: the API used by the front-end UI for all disbursement requests. La API está documentada [aquí](../api-reference/admin)
-  - **Admin API**: la API utilizada por la organización anfitriona para gestionar la provisión y configuración de inquilinos. La API está documentada [aquí](../api-reference/admin)
-  - **Messaging Service**: un proceso recurrente que envía mensajes de texto a los usuarios para incitarlos a descargar la billetera seleccionada para una distribución particular y verificar su teléfono con un OTP
-  - **Registro de billetera**: una aplicación web registra a un destinatario recopilando y verificando su código OTP e información de verificación mediante el protocolo [SEP-24: Hosted Deposit and Withdrawal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md) de Stellar
-- **Transaction Submission Service**: el servicio que envía todas las transacciones de pago a la red Stellar. This service is designed to maximize payment throughput, handle queuing, and graceful resubmission/error handling
-
-## Dependencias {#dependencies}
-
-- **Container Orchestration**: el SDP se empaqueta como contenedores Docker y se puede desplegar en Kubernetes o AWS Fargate. SDF provides a Helm Chart for Kubernetes
-- **Postgres**: the SDP uses a Postgres database server for all of its services
-- **Twilio o AWS SNS y SES**: el servicio de mensajería del SDP utiliza mensajes SMS/WhatsApp a través de Twilio o AWS SNS y correos electrónicos administrativos para la configuración y recuperación de la cuenta de la organización a través de AWS SES o Twilio SendGrid
-- **Stellar Accounts**:
-  - Distribution Account: the SDP requires access to at least one funded Stellar account to make payments to the recipient
-  - SEP-10 Auth Account: the SDP requires a Stellar account for the mutual authentication protocol [SEP-10: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) used to connect to wallet applications
-
-## Diagrama de Arquitectura
-
-![Architecture Diagram](/assets/SDP/SDP2-2.png)
-
-### Roles de Usuario {#user-roles}
-
-El SDP define los siguientes roles de usuario:
-
-- **Administrador Host**: la organización que aloja la instancia del SDP y gestiona el aprovisionamiento y la configuración de los tenants mediante la API `Tenant Admin`
-- **Usuario del Panel**: un usuario que pertenece a un tenant y utiliza el Panel SDP para crear y gestionar distribuciones, destinatarios y otros datos específicos del tenant.
-- **Usuario API**: un usuario que pertenece a un tenant y utiliza la `Dashboard API` para crear y gestionar distribuciones, destinatarios y otros datos específicos del tenant de forma programada
-- **Receptores**: los usuarios finales que reciben los fondos enviados a través del SDP. Los receptores pueden usar una aplicación wallet que soporte SEP-24 para el registro automático, o pueden recibir fondos directamente en su cuenta Stellar.
-
-### Flujo de Trabajo {#workflow}
-
-1. El administrador host utiliza la API `Tenant Admin` para aprovisionar y gestionar los tenants.
-2. `Usuario del Panel` y `Usuario API` usan el Servicio Central SDP para enviar distribuciones y gestionar / invitar a otros usuarios. Esto puede hacerse a través de la IU del Panel o directamente mediante la `Dashboard API`.
-3. Para pagos que requieren registro SEP-24, el `Servicio Central SDP` envía un mensaje para notificar a los receptores. El mensaje contiene un deeplink que abre la wallet objetivo, lo que a su vez activa el **flujo de depósito SEP-24** y registra a los receptores.
-4. El TSS recupera los pagos que están listos para ser procesados y luego los envía a la Red Stellar mediante Cuentas Canal.
-
-## Base de Datos & Esquemas {#database}
-
-El SDP utiliza una base de datos Postgres para todos sus servicios. El esquema de la base de datos es gestionado por el SDP Core Service y está versionado en la base de código. El esquema de la base de datos está diseñado para ser consciente de los inquilinos, lo que significa que cada inquilino tiene su propio conjunto de tablas y datos. Esto permite que el SDP sea multitenencia y soporte múltiples organizaciones utilizando la misma instancia.
-
-Hay 3 tipos de esquemas en la base de datos:
-
-- **Admin Schema**: contiene tablas para gestionar inquilinos. Este esquema es utilizado por el Admin API para gestionar la configuración y provisión de inquilinos.
-- **TSS Schema**: contiene tablas para gestionar transacciones. Este esquema es utilizado por el Transaction Submission Service para gestionar el estado de las transacciones de pago.
-- **Tenant Schemas**: cada inquilino tiene su propio esquema que contiene tablas para gestionar distribuciones, destinatarios y otros datos específicos del inquilino. Estos esquemas comienzan con `sdp_`.
-
-## Multitenencia {#multi-tenancy}
-
-El SDP puede ser desplegado en una configuración multitenencia, donde múltiples organizaciones comparten la misma instancia del SDP. Cada organización se refiere como un inquilino y tiene su propio conjunto de datos y configuración. Una organización anfitriona puede gestionar múltiples inquilinos y gestionar su configuración a través del Admin API.
-
-### Resolución de Inquilinos {#tenant-resolution}
-
-El SDP utiliza una estrategia de resolución de inquilinos para determinar a qué inquilino pertenece una solicitud. La resolución de inquilinos solo es requerida para solicitudes no autenticadas, ya que las solicitudes autenticadas incluyen la información del inquilino ya en el token JWT.
-
-- **Header**: el encabezado `SDP-Tenant-Name` se utiliza para especificar el nombre del inquilino en la solicitud. Cuando está presente, este encabezado se utiliza para intentar resolver el inquilino.
-- **Subdominio**: el SDP puede utilizar el subdominio de la URL de solicitud para resolver el inquilino. Por ejemplo, `tenant1.sdp.backend.test` se resolvería al inquilino `tenant1`.
-
-La prioridad de resolución es la siguiente: token JWT (solicitudes autenticadas) > Header > Subdominio.
-
-#### Modo de Inquilino Único {#single-tenant-mode}
-
-Cuando se habilita el modo de inquilino único utilizando la variable de entorno `SINGLE_TENANT_MODE`, todos los inquilinos se resolverán automáticamente al inquilino predeterminado. Un inquilino predeterminado se establece llamando a la API [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx).
-
-El inquilino predeterminado es útil para fines de desarrollo o cuando el SDP es utilizado por una única organización. Esto permite que la organización omita especificar el inquilino en cada solicitud y simplifica la configuración operativa del SDP al eliminar la necesidad de proporcionar certificados TLS comodín para configuraciones multitenencia.
-
-#### Resolución de Subdominio {#subdomain-resolution}
-
-Al ejecutar el SDP en modo multitenencia, el SDP utiliza el subdominio de la URL de solicitud para resolver el inquilino. Por ejemplo, `tenant1.sdp.backend.test` se resolvería al inquilino `tenant1`. Esto permite que el SDP diferencie entre inquilinos sin requerir que se especifique el nombre del inquilino en la solicitud.
-
-La resolución de subdominio es particularmente importante para el proceso de Registro de Billetera, ya que el SDP depende de subdominios para diferenciar entre inquilinos durante el flujo de depósito SEP-24. Los dominios principales, que contienen el nombre del inquilino como un subdominio, se utilizan durante el proceso de registro por el SDP para identificar al inquilino y dirigir la solicitud de registro de billetera al contexto correcto del inquilino.
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/getting-started.mdx
deleted file mode 100644
index 2546aac8bf..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/getting-started.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía cubre cómo ejecutar localmente la Plataforma de Distribución Stellar, enviar una distribución de muestra y reclamarla a través de la billetera de demostración en Testnet. Considera este recorrido como un entorno de aprendizaje más que como el camino para implementaciones en producción.
-
-### Requisitos previos
-
-- **Docker:** Asegúrate de tener Docker instalado en tu sistema. Si no, puedes descargarlo desde [aquí](https://www.docker.com/products/docker-desktop) y ejecutarlo una vez instalado.
-- **Git:** Necesitarás Git para clonar el repositorio. Puedes descargarlo desde [aquí](https://git-scm.com/downloads).
-- **Go:** Requerido para generar tu archivo de entorno. Instálalo desde [aquí](https://golang.org/dl/).
-- **jq:** Útil para scripts opcionales y diagnóstico. Puedes descargarlo desde [aquí](https://jqlang.org/download/)
-
-Para macOS y Linux, puedes instalarlo con Homebrew:
-
-```bash
-brew install --cask docker
-brew install git go jq
-```
-
-### Clona el repositorio
-
-```bash
-git clone https://github.com/stellar/stellar-disbursement-platform-backend.git
-cd stellar-disbursement-platform-backend
-```
-
-### Ejecuta el asistente
-
-```bash
-make setup
-```
-
-En los avisos, elige según lo indicado abajo. El asistente genera y financia las cuentas firmantes SEP-10 y de distribución (testnet), inicia Docker y muestra las credenciales del arrendatario.
-
-```
-? Select an existing run configuration or create new:
-▸ Create new configuration
-✔ Setup name (optional): <sdp-setup-name>
-? Select network:
-▸ testnet
-? Select tenant mode:
-▸ single-tenant
-? Account setup:
-▸ Generate new accounts
-? Launch local environment now (project=sdp-sdp-test, setup=<sdp-setup-name>)? [Y/n] Y
-? Initialize tenants and users? [y/N] Y
-```
-
-Al finalizar deberías ver:
-
-```
-🎉🎉🎉🎉 SUCCESS! 🎉🎉🎉🎉
-Single tenant mode - Login URL:
-🔗Default tenant: http://localhost:3000
-  username: owner@default.local  password: Password123!
-```
-
-### Inicia sesión en el SDP
-
-Abre http://localhost:3000 e inicia sesión usando las credenciales de administrador generadas por el asistente de configuración (organización: default). ![Login](/assets/SDP/SDP32.png)
-
-### Envía una distribución de prueba
-
-Haz clic en `New Disbursement +` en el panel; verás una cuenta de distribución financiada lista para usar:
-
-- Elige número de teléfono como Tipo de Contacto de Registro. Este es el canal que los destinatarios usarán para recibir mensajes.
-- Selecciona XLM como el activo para distribuir.
-- Elige Demo Wallet como la billetera destinataria.
-- Selecciona Fecha de Nacimiento como método de verificación; los destinatarios la ingresarán para confirmar su identidad.
-- Asigna un nombre a la distribución. ![Disbursement Details](/assets/SDP/SDP33.png)
-
-Crear y subir un archivo de distribución:
-
-- Descarga el ejemplo usando `Download CSV Template`; incluye todas las columnas requeridas.
-- Actualiza los números de teléfono de marcador de posición/invalidos antes de usarlo.
-- La columna de verificación contiene los datos de identidad que los destinatarios deben coincidir. ![Disbursement CSV](/assets/SDP/SDP34.png)
-
-Haz clic en el botón Revisar. Cuando estés listo para iniciar la distribución, haz clic en el botón "Confirmar distribución". En Detalles de la Distribución verás el pago con estado `Ready`, lo que significa que el receptor aún no ha aceptado la invitación ni el pago. ![Disbursement Dashboard](/assets/SDP/SDP35.png)
-
-### Recibir pago
-
-:::note
-
-Esta sección muestra el flujo de la Demo Wallet sólo en Testnet para que puedas observar la experiencia del receptor mientras ejecutas SDP localmente. Para integraciones en producción o con billeteras reales, sigue las indicaciones en [Haciendo tu billetera compatible con SDP](./making-your-wallet-sdp-ready.mdx).
-
-:::
-
-Reclama el pago en la billetera de demostración creando primero una billetera:
-
-- Abre la billetera de demo: http://localhost:4000.
-- Haz clic en `Generate Keypair for new account` para crear un par de claves; guarda las claves pública y secreta si planeas reutilizar la cuenta.
-- Haz clic en `Create account` para crear la cuenta en la testnet de Stellar (la cuenta inicia con 10,000 XLM). ![Demo Wallet Creation](/assets/SDP/SDP36.png)
-
-Para recibir tu pago, inicia un depósito SEP-24:
-
-- Bajo Asset XLM, haz clic en `Add Home Domain`, ingresa `localhost:8000` y haz clic en `Override`.
-- En el desplegable `Select action`, elige `SEP-24 Deposit` y luego haz clic en `Start`. ![SEP-24 Deposit](/assets/SDP/SDP37.png)
-
-Verifica tu identidad:
-
-- Cuando se te solicite, ingresa el mismo número de teléfono usado en el CSV de distribución.
-- Completa la verificación OTP y Fecha de Nacimiento. El OTP aparece en los logs del contenedor `sdp-api` (por ejemplo, “Aquí está el código de verificación de 6 dígitos que solicitaste ...”). ![OTP Code](/assets/SDP/SDP38.png) ![PII Verification](/assets/SDP/SDP39.png)
-
-### Monitoreo
-
-- En el panel del SDP, el pago cambia de `Ready` a `PENDING` durante el flujo de la billetera, luego a `Success` cuando se depositan los fondos. ![SDP Dashboard](/assets/SDP/SDP40.png)
-
-- En la billetera de demo, el saldo se actualiza para reflejar la nueva cantidad. ![Demo Wallet Balance](/assets/SDP/SDP41.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/making-your-wallet-sdp-ready.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/making-your-wallet-sdp-ready.mdx
deleted file mode 100644
index 2547fd1ec8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/making-your-wallet-sdp-ready.mdx
+++ /dev/null
@@ -1,178 +0,0 @@
----
-title: Hacer Que Tu Billetera Sea Compatible con SDP
-sidebar_position: 80
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Recuerda que cualquier instancia de SDP necesitará un acuerdo con un proveedor de billetera antes de enviar desembolsos a esa billetera. Esto asegura que las billeteras se sientan cómodas recibiendo fondos de tu organización y regula cualquier acuerdo comercial entre las organizaciones. La billetera necesitará permitir la lista blanca del dominio de SDP antes de que el SDP pueda enviar desembolsos a esa billetera. Cuando el dominio de la billetera es añadido a un SDP, efectivamente está siendo incluido en la lista blanca por el SDP. Ambas partes listando la otra les permite recuperar el archivo stellar.toml y verificar la clave de firma necesaria para el apretón de manos [SEP-10].
-
-En esta página, cubriremos los aspectos técnicos de la integración de SDP-Billetera, incluyendo cómo añadir una billetera en la base de datos de SDP, cómo validar y admitir los enlaces de registro utilizando el [deep linking] de la aplicación móvil, cómo iniciar el flujo de registro de usuario en la billetera usando [SEP-24], y un enfoque recomendado para manejar [deferred deep linking].
-
-## Añadir una Billetera a un SDP
-
-La lista predeterminada de billeteras SDP depende de qué red se esté utilizando (testnet o pubnet). La red se pasa como una variable de entorno y luego la lista de billeteras puede ser sembrada apropiadamente al iniciar SDP a través del comando de CLI `./stellar-disbursement-platform db setup-for-network`, de acuerdo con una lista codificada de billeteras conocidas. Alternativamente, las billeteras pueden ser insertadas directamente en la base de datos de SDP a través de un comando SQL. Ambos métodos requieren agregar el nombre de la billetera, la página de inicio, el dominio del cliente SEP-10 y el esquema del enlace profundo.
-
-Para insertarlo directamente en la base de datos, actualiza tus valores y ejecuta la siguiente consulta de Postgres. Asegúrate de verificar tu base de datos y espacio de nombres primero.
-
-<CodeExample>
-
-```sql
-INSERT INTO wallets (name, homepage, deep_link_schema, sep_10_client_domain)
-VALUES ('Vibrant Assist', 'https://vibrantapp.com', 'https://vibrantapp.com/sdp', 'api.vibrantapp.com');
-```
-
-</CodeExample>
-
-Para configurar una billetera a través del código, añádela a la sección de testnet o pubnet de `DefaultWalletsNetworkMap`. Esto se usará cuando ejecutes el comando CLI `./stellar-disbursement-platform db setup-for-network`, que actualiza la base de datos de SDP y hace que la billetera esté disponible para nuevos desembolsos. Añade tu nueva billetera siguiendo el mismo formato que ya está presente en el código.
-
-<CodeExample>
-
-```go
-var DefaultWalletsNetworkMap = WalletsNetworkMapType{
-	utils.PubnetNetworkType: {
-		{
-			Name:              "Vibrant Assist",
-			Homepage:          "https://vibrantapp.com/assist",
-			DeepLinkSchema:    "https://vibrantapp.com/sdp",
-			SEP10ClientDomain: "api.vibrantapp.com",
-		},
-	},
-	utils.TestnetNetworkType: {
-		{
-			Name:              "Vibrant Assist",
-			Homepage:          "https://vibrantapp.com",
-			DeepLinkSchema:    "https://vibrantapp.com/sdp-dev",
-			SEP10ClientDomain: "api-dev.vibrantapp.com",
-		},
-		{
-			Name:              "Demo Wallet",
-			Homepage:          "https://demo-wallet.stellar.org",
-			DeepLinkSchema:    "https://demo-wallet.stellar.org",
-			SEP10ClientDomain: "demo-wallet-server.stellar.org",
-		},
-	},
-}
-```
-
-</CodeExample>
-
-## Experiencia de Registro del Destinatario
-
-La experiencia de registro del destinatario es primordial para que esta aplicación sea fluida y fácil de usar. Esto requiere que la billetera admita [deferred deep linking], que se discutirá en una sección posterior. Una buena descripción de la experiencia de registro es la siguiente:
-
-1. El destinatario recibe un mensaje de invitación notificándole que tiene un pago esperando de la organización y le solicita hacer clic en un [deep link] para abrir o instalar y abrir una aplicación de billetera
-
-2. Cuando el destinatario abre la aplicación de billetera, la billetera a bordo inmediatamente al destinatario, crea una cuenta Stellar y una línea de confianza para el activo deseado, inicia una transacción de depósito [SEP-24] con el SDP, y abre la página de registro del SDP como una pantalla de superposición/iframe dentro de la aplicación.
-
-3. El usuario confirma su número de teléfono y fecha de nacimiento directamente con el SDP, sin compartir ningún dato con la billetera, y después de que finaliza el registro, el usuario es enviado de nuevo a la aplicación de billetera. Aquí están las pantallas que demuestran estos pasos:
-
-   ![Flujo de Registro](/assets/SDP/SDP25.png)
-
-4. El usuario recibe el pago en cuestión de segundos
-
-## Enlace Profundo de Registro
-
-Una vez que el usuario ha instalado la aplicación de billetera, la billetera debería ser capaz de interpretar un [deep link] que sigue el formato registrado en el SDP para iniciar el [Procedimiento de Registro de Billetera](#wallet-registration-procedure). El formato de enlace profundo admitido por el SDP sigue este formato:
-
-```url
-https://<host-with-optional-path>?asset=<asset>&domain=<domain>&name=<name>&signature=<signature>
-```
-
-- `asset`: el activo Stellar.
-- `domain`: el dominio que aloja el archivo `stellar.toml` de SDP. La billetera necesitará usarlo tanto para obtener el archivo `stellar.toml`, como para poblar el campo `home_domain` en la transacción de GET de desafío [SEP-10].
-- `name`: el nombre de la organización que envía pagos.
-- `signature`: una firma de la clave de firma de [SEP-10] de SDP.
-
-:::info
-
-Ten en cuenta que el enlace profundo es específico para cada SDP, organización pagadora y activo. No es específico por receptor individual. No hay riesgo en compartir el enlace con receptores que forman parte del mismo desembolso. El enlace será el mismo para múltiples receptores y demostrarán su identidad como parte del flujo de depósito [SEP-24].
-
-:::
-
-A continuación se muestra un ejemplo de un enlace de registro (firmado)
-
-```url
-https://vibrantapp.com/sdp-dev?asset=USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5&domain=ap-stellar-disbursement-platform-backend-dev.stellar.org&name=Stellar+Test&signature=fea6c5e805a29b903835bea2f6c60069113effdf1c5cb448d4948573c65557b1d667bcd176c24a94ed9d54a1829317c74f39319076511512a3e697b4b746ae0a
-```
-
-En este ejemplo, el host es `https://vibrantapp.com/sdp-dev` y la firma es el resultado de firmar la siguiente url (sin firmar) utilizando la clave de firma [SEP-10] `SBUSPEKAZKLZSWHRSJ2HWDZUK6I3IVDUWA7JJZSGBLZ2WZIUJI7FPNB5`, siendo la clave pública `GBFDUUZ5ZYC6RAPOQLM7IYXLFHYTMCYXBGM7NIC4EE2MWOSGIYCOSN5F`:
-
-```url
-https://vibrantapp.com/sdp-dev?asset=USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5&domain=ap-stellar-disbursement-platform-backend-dev.stellar.org&name=Stellar+Test
-```
-
-En este ejemplo, la firma es `fea6c5e805a29b903835bea2f6c60069113effdf1c5cb448d4948573c65557b1d667bcd176c24a94ed9d54a1829317c74f39319076511512a3e697b4b746ae0a`.
-
-A continuación se muestra un fragmento de JavaScript que demuestra cómo verificar la firma:
-
-```js
-#!/usr/bin/env node
-
-const { Keypair } = require("stellar-sdk");
-
-// The SDP's stellar.toml SIGNING_KEY
-//
-// For security, this should ideally be fetched from
-// https://<domain>/.well-known/stellar.toml on demand
-const keypair = Keypair.fromPublicKey(
-  "GBFDUUZ5ZYC6RAPOQLM7IYXLFHYTMCYXBGM7NIC4EE2MWOSGIYCOSN5F",
-);
-console.log("public key:", keypair.publicKey());
-
-let url =
-  "https://vibrantapp.com/sdp-dev?asset=USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5&domain=ap-stellar-disbursement-platform-backend-dev.stellar.org&name=Stellar%20Test";
-let signature =
-  "fea6c5e805a29b903835bea2f6c60069113effdf1c5cb448d4948573c65557b1d667bcd176c24a94ed9d54a1829317c74f39319076511512a3e697b4b746ae0a";
-
-console.log(
-  "verified:",
-  keypair.verify(
-    Buffer.from(url.toString(), "utf8"),
-    Buffer.from(signature, "hex"),
-  ),
-);
-```
-
-### Procedimiento de Registro de Billetera
-
-Al abrir el [deep link] de registro, estos son los pasos que la billetera debería seguir para hacer cumplir las medidas de seguridad y privacidad esperadas en este flujo, y permitir que el usuario ingrese su información directamente con el SDP:
-
-1. 🚨 Confirma que el `domain` del enlace profundo está en la lista blanca de la billetera. Esto es crucial para autenticar desde una billetera de confianza.🚨
-2. Obtén el archivo toml de SDP en `{domain}/.well-known/stellar.toml` y confirma que la variable `SIGNING_KEY` esté poblada.
-3. Verifica que la firma del enlace de registro se haya realizado utilizando `SIGNING_KEY` similar a la función `keypairPk.verify(...)` en el fragmento anterior, y que la firma sea válida con el contenido del enlace.
-4. Verifica el `asset` del enlace y confirma que el usuario destinatario tenga una línea de confianza para ese activo. Crea una si no existe.
-5. (Opcional) Usa el `name` del enlace para actualizar la interfaz de usuario de la billetera.
-6. Inicia el flujo de depósito [SEP-24] con ese activo usando el valor de `TRANSFER_SERVER_SEP0024` del archivo toml de SDP.
-   - Esto incluye utilizar [SEP-10] para autenticar al usuario con el servidor SDP. Por favor nota que el SDP requiere que tanto el campo `client_domain` como el `home_domain` sean proporcionados en la solicitud `GET <WEB_AUTH_ENDPOINT>`, y deben establecerse de la siguiente manera:
-     - `client_domain`: el dominio del servidor de billetera que expone el archivo `stellar.toml` del servidor de billetera.
-   - `home_domain`: el dominio del servidor de SDP que estaba presente en el enlace de registro.
-   - `account`: la cuenta Stellar de la billetera del receptor.
-7. Lanza el flujo de depósito en un navegador _in-app_ interactivo dentro de tu aplicación móvil, siguiendo las instrucciones en la especificación [SEP-24].
-   - ATENCIÓN: la billetera no debe, bajo ninguna circunstancia, extraer o intentar extraer el contenido del navegador _in-app_ para obtener la información del destinatario.
-   - NOTA: se recomienda encarecidamente usar un navegador _in-app_ en lugar de una webview.
-8. 🎉 ¡Felicidades! El usuario destinatario puede ahora completar los formularios en el navegador _in-app_ y registrarse para recibir su pago 🎉.
-
-Además, la billetera debería guardar el enlace y/o atributos del enlace y asociarlo con el usuario receptor individual por estas razones:
-
-1. Así es como la billetera sabrá que el usuario está asociado con una cierta organización o SDP.
-2. Guardar los datos es útil para reportar y solucionar problemas, especialmente si la billetera necesita justificar la fuente de fondos por motivos regulatorios o fiscales.
-3. Si la organización pagadora quiere pagar cualquier tarifa de retiro cobrada por la billetera o el serviciador, la billetera necesitará saber qué usuarios y transacciones deberían ser facturadas hacia arriba.
-
-### Enlaces Profundos Diferidos
-
-Es muy probable que el destinatario previsto no tenga instalada la aplicación de billetera necesaria en su dispositivo. Por esta razón, las billeteras deberían soportar el concepto de [deferred deep linking], que habilita el siguiente flujo:
-
-1. La acción inicial del destinatario de hacer clic en el enlace profundo debería redirigirlo a la tienda de aplicaciones correspondiente para descargar la aplicación de billetera.
-2. Después de instalar y abrir la aplicación, el destinatario debería ser redirigido al flujo de incorporación típico de la billetera.
-3. Una vez que el usuario se haya incorporado con éxito, la billetera debería usar la información incluida en el enlace profundo para iniciar el [Procedimiento de Registro de Billetera](#wallet-registration-procedure).
-
-El deep linking diferido es una característica comúnmente soportada por numerosas soluciones de deep linking móvil, existen servicios de terceros que pueden ser usados para implementar esta funcionalidad, como Singular, Branch, AppsFlyer, Adjust y otros. [Aquí](https://medium.com/bumble-tech/universal-links-for-android-and-ios-1ddb1e70cab0) hay una publicación de blog con más información sobre cómo implementar [deferred deep linking].
-
-El SDP soporta un formato de enlace básico, como `https://<host-with-optional-path>`. Si el sistema de deep linking de tu billetera necesita una estructura más compleja, tendrás que gestionar esto con una aplicación web. Esta aplicación debería ser propiedad del proveedor de la billetera, y debería ser capaz de recibir el enlace profundo, interpretarlo y dirigir al usuario a la ubicación correcta.
-
-[deep linking diferido]: https://en.wikipedia.org/wiki/Mobile_deep_linking#Deferred_deep_linking
-[deep link]: https://en.wikipedia.org/wiki/Mobile_deep_linking
-[deep linking]: https://en.wikipedia.org/wiki/Mobile_deep_linking
-[sep-10]: https://stellar.org/protocol/sep-10
-[sep-24]: https://stellar.org/protocol/sep-24
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/monitoring.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/monitoring.mdx
deleted file mode 100644
index 51e7aaebd8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/monitoring.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Monitoreo
-description: Guía para usar la Interfaz de Línea de Comandos de la Plataforma de Distribución Stellar
-keywords:
-  - SDP
-  - CLI
-sidebar_position: 70
----
-
-Esta guía explica cómo la Plataforma de Distribución Stellar (SDP) expone métricas en tiempo de ejecución y cómo conectar esas métricas con la pila Prometheus + Grafana.
-
-### Puntos de acceso de métricas
-
-Tanto la API del Panel como el Servicio de Envío de Transacciones (TSS) exponen puntos de acceso `/metrics` compatibles con Prometheus. El servidor HTTP está definido en [serve_metrics.go](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/internal/serve/serve_metrics.go) y se controla mediante las siguientes variables de entorno:
-
-- `METRICS_PORT` – Puerto usado por el servidor de métricas de la API del Panel (por defecto [8002](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/docker-compose-sdp.yml)).
-- `METRICS_TYPE` – Backend de monitoreo en uso (actualmente `PROMETHEUS`).
-- `TSS_METRICS_PORT` – Puerto usado por el servidor de métricas del TSS (por defecto [9002](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/docker-compose-tss.yml)).
-- `TSS_METRICS_TYPE` – Backend de monitoreo para el TSS (por defecto `TSS_PROMETHEUS`).
-
-Cuando el servidor inicia, monta la ruta `/metrics` y muestra contadores e histogramas de solicitudes, base de datos y específicos del TSS que coinciden con los paneles de Grafana provistos en el [README de Grafana](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/resources/grafana/README.md).
-
-### Pila local de Prometheus y Grafana
-
-Proveemos un archivo Docker Compose que inicia Prometheus y Grafana preconfigurados para obtener datos de los puntos de acceso de métricas del SDP.
-
-1. Desde la [raíz del repositorio](https://github.com/stellar/stellar-disbursement-platform-backend/), ejecuta:
-
-```sh
-cd dev
-docker compose -p sdp-multi-tenant -f docker-compose-monitoring.yml up -d
-```
-
-Esto lanza Prometheus en el puerto `9090` y Grafana en el puerto `3002` por defecto [configuración de monitoreo](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/docker-compose-monitoring.yml).
-
-2. El contenedor de Prometheus carga su configuración desde [configuración de prometheus](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/prometheus/prometheus.yml), que apunta a `host.docker.internal:8002/metrics` por defecto. Ajusta la lista `targets` si ejecutas la API en otro host o si quieres obtener métricas del TSS (`host.docker.internal:9002`).
-3. Grafana usa la configuración de fuente de datos en [datasource](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/grafana/datasource.yaml), que apunta a la instancia de Prometheus mencionada. Si ya tienes un despliegue de Prometheus existente, actualiza esta URL en consecuencia.
-
-Para desmontar la pila de monitoreo, ejecuta:
-
-```sh
-cd dev
-docker compose -p sdp-multi-tenant -f docker-compose-monitoring.yml down
-```
-
-### Cargar el panel de Grafana del SDP
-
-1. Navega a [http://localhost:3002](http://localhost:3002) e inicia sesión con las credenciales predeterminadas `admin` / `admin`. ![Inicio de sesión en Grafana](/assets/SDP/SDP42.png)
-
-2. Haz clic en el icono `+` en la barra de navegación superior (al lado del campo de búsqueda), elige `Importar panel` y pega el contenido de [Json del panel de Grafana](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/resources/grafana/dashboard.json). ![Importar Panel](/assets/SDP/SDP43.png)
-
-3. Selecciona la fuente de datos `prometheus` proporcionada por [datasource](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/grafana/datasource.yaml). ![Seleccionar Fuente de Datos](/assets/SDP/SDP44.png)
-
-Este panel visualiza el volumen/latencia de solicitudes HTTP, tiempos de consulta de base de datos y estadísticas de transacciones del TSS, detalles descritos en [README.md de Grafana](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/resources/grafana/README.md). Todos los paneles pueden filtrarse por método, ruta, tenant o instancia para distinguir el tráfico entre múltiples despliegues.
-
-### Integración con instancias externas de Prometheus
-
-Si ya operas un clúster de Prometheus, añade trabajos de recolección equivalentes a los de [configuración de prometheus](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/prometheus/prometheus.yml). Cada subsistema expone métricas en `http://<host>:<METRICS_PORT>/metrics` (API del Panel) y `http://<host>:<TSS_METRICS_PORT>/metrics` (TSS). Las instalaciones con [Helm](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/helmchart/sdp/values.yaml) exponen las mismas configuraciones mediante `sdp.configMap.data.METRICS_*` y `tss.configMap.data.TSS_METRICS_*`. Una vez que los nuevos trabajos estén presentes, puedes importar el mismo JSON del panel en tu despliegue de Grafana o adaptar las consultas PromQL a tu suite de observabilidad preferida.
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/overview.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/overview.mdx
deleted file mode 100644
index d203b87eaf..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/overview.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Visión general
-sidebar_position: 5
-pagination_label: "Guía de administración: Resumen"
----
-
-El proceso completo del SDP, paso a paso, generalmente se ve algo así después de que se despliega el SDP y se configuran los usuarios organizacionales:
-
-1. La organización financia la cuenta de distribución del SDP con un activo basado en Stellar (por ejemplo, USDC)
-2. Un administrador inicia sesión en el panel del SDP y sube un archivo CSV que contiene la información de pago para iniciar un nuevo desembolso
-3. El SDP envía un mensaje de texto a cada destinatario que recibe por primera vez en el CSV, invitándolos a descargar una aplicación de billetera habilitada para Stellar
-4. Mientras tanto, el SDP comienza a hacer pagos inmediatamente a cada destinatario que ya tiene una billetera registrada a su nombre
-5. Cada destinatario que recibe por primera vez hace clic en un enlace profundo para descargar la aplicación de billetera habilitada para Stellar elegida por la organización para este desembolso, descarga la aplicación y pasa por el proceso de registro de la billetera
-6. Una vez que el destinatario se ha registrado y su cuenta de Stellar ha sido creada, la billetera se autentica inmediatamente con el SDP utilizando parámetros del enlace profundo y abre la vista web de registro del SDP para que el destinatario complete la verificación
-7. El usuario confirma su identidad proporcionando un código OTP enviado a su número de teléfono y una pieza adicional de información de verificación por motivos de seguridad. El SDP admite tres tipos diferentes de información de verificación: Fecha de Nacimiento, PIN Personal y ID Nacional. Esta información es ingresada por el destinatario en un flujo web y se envía directamente al SDP, lo que significa que la billetera no necesita procesar o almacenar esta información.
-8. El SDP verifica la información del destinatario. Si coincide con la información del CSV, el SDP realiza automáticamente el pago a la cuenta de Stellar del destinatario
-
-Representación gráfica del flujo de fondos:
-
-![Flujo de Fondos](/assets/SDP/SDP1.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/secure-operation-manual.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/secure-operation-manual.mdx
deleted file mode 100644
index b87214bc6a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/secure-operation-manual.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Manual de Operación Segura
-sidebar_position: 42
----
-
-Este manual describe las medidas de seguridad implementadas en la Stellar Disbursement Platform (SDP) para proteger la integridad de la plataforma y de sus usuarios. Al seguir estas directrices, puedes asegurarte de que tu uso de la SDP sea lo más seguro posible.
-
-La seguridad es un aspecto crítico de la SDP. Las medidas descritas en este documento están diseñadas para mitigar riesgos y mejorar la seguridad de la plataforma. Se anima a los usuarios a seguir estas directrices para proteger sus cuentas y operaciones.
-
-### Implementación de reCAPTCHA
-
-El reCAPTCHA de Google se ha integrado en la SDP para prevenir ataques automatizados y asegurar que las interacciones sean realizadas por humanos, no por bots.
-
-El reCAPTCHA está habilitado por defecto y puede desactivarse en el entorno de desarrollo configurando la variable de entorno `DISABLE_RECAPTCHA` en `true`.
-
-**Nota:** Desactivar el reCAPTCHA no está admitido para entornos de producción debido a riesgos de seguridad.
-
-### Aplicación de la Autenticación de Múltiples Factores
-
-La Autenticación de Múltiples Factores (MFA) proporciona una capa adicional de seguridad a las cuentas de usuario. Se aplica por defecto en la SDP y se basa en OTP enviados al correo electrónico de la cuenta.
-
-La MFA está habilitada por defecto y puede desactivarse en el entorno de desarrollo configurando la variable de entorno `DISABLE_MFA` en `true`.
-
-**Nota:** Desactivar la MFA no está admitido para entornos de producción debido a riesgos de seguridad.
-
-### Prácticas Recomendadas para la Gestión de Billeteras
-
-La billetera de la SDP debe utilizarse principalmente como una billetera caliente con una cantidad limitada de fondos para minimizar las pérdidas potenciales.
-
-#### Billeteras Calientes y Frías
-
-- Una billetera caliente está conectada a internet y permite realizar transacciones rápidas.
-- Una billetera fría está fuera de línea y se utiliza para almacenar fondos de manera segura.
-- Aprende más sobre estos conceptos en [Investopedia](https://www.investopedia.com/hot-wallet-vs-cold-wallet-7098461).
-
-### Distribución de Responsabilidades de Desembolso
-
-Para mejorar la seguridad, las responsabilidades de desembolso deben distribuirse entre varios usuarios del controlador financiero.
-
-#### Configuración Recomendad
-
-1. **Approval Flow**: Enable the approval flow on the organization page to require two users for the disbursement process. The owner can do that at _Profile > Organization > ... > Editar detalles > Flujo de aprobación > Confirmar_.
-2. **Rol de Controlador Financiero**: Crea dos usuarios con el rol de _Controlador Financiero_ en la página de la organización para hacer cumplir la separación de funciones. El propietario puede hacer eso en _Configuración > Miembros del equipo_.
-3. **Gestión de la Cuenta del Propietario**: Utiliza la cuenta del Propietario únicamente para la gestión de usuarios y la configuración de la organización. Evita usar la cuenta del Propietario para tareas del controlador financiero para minimizar la exposición de esa cuenta.
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/security.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/security.mdx
deleted file mode 100644
index d4c8302c6b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/security.mdx
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Seguridad
-sidebar_position: 60
----
-
-Este manual describe las medidas de seguridad implementadas en la Plataforma de Distribución Stellar (SDP) para proteger la integridad de la plataforma y sus usuarios. Al seguir estas directrices, puedes asegurar que tu uso de la SDP sea lo más seguro posible.
-
-La seguridad es un aspecto crítico de la SDP. Las medidas descritas en este documento están diseñadas para mitigar riesgos y mejorar la seguridad de la plataforma. Se recomienda encarecidamente a los usuarios seguir estas directrices para proteger sus cuentas y operaciones.
-
-### Implementación de reCAPTCHA
-
-El reCAPTCHA de Google ha sido integrado en la SDP para prevenir ataques automatizados y garantizar que las interacciones sean realizadas por humanos, no bots.
-
-reCAPTCHA está habilitado por defecto y puede desactivarse configurando la variable de entorno `DISABLE_RECAPTCHA` a `true`.
-
-La configuración está disponible en dos niveles:
-
-1. **Configuración por defecto del entorno** – Establece `DISABLE_RECAPTCHA=true` para aplicar la configuración globalmente a todos los inquilinos.
-2. **Anulación a nivel de inquilino** – Cada organización puede habilitar o deshabilitar reCAPTCHA a través de su propia configuración (UI o API). Cuando está presente, la opción a nivel de inquilino anula la configuración por defecto del entorno.
-
-Utiliza las siguientes variables de entorno para controlar el comportamiento de reCAPTCHA:
-
-- `CAPTCHA_TYPE` – `GOOGLE_RECAPTCHA_V2` (predeterminado) o `GOOGLE_RECAPTCHA_V3`.
-- `RECAPTCHA_SITE_KEY` – Clave del sitio de Google emitida para el tipo de CAPTCHA elegido.
-- `RECAPTCHA_SITE_SECRET_KEY` – Clave secreta de Google emparejada con la clave del sitio.
-- `RECAPTCHA_V3_MIN_SCORE` – Puntuación mínima permitida (0.0–1.0, predeterminado 0.5) cuando `CAPTCHA_TYPE=GOOGLE_RECAPTCHA_V3`.
-
-**Nota:** Deshabilitar reCAPTCHA en implementaciones de producción (pubnet) reduce sustancialmente la protección contra abusos automatizados. Esta configuración debe usarse solo cuando existan controles compensatorios equivalentes.
-
-### Aplicación de la Autenticación Multifactor
-
-La Autenticación Multifactor (MFA) proporciona una capa adicional de seguridad a las cuentas de usuario. Se aplica por defecto en la SDP y se basa en OTPs enviados al correo electrónico asociado a la cuenta.
-
-MFA está habilitado por defecto y puede deshabilitarse en el entorno de desarrollo configurando la variable de entorno `DISABLE_MFA` a `true`.
-
-**Nota:** No es posible deshabilitar MFA en entornos de producción (pubnet) debido a riesgos de seguridad.
-
-### Limitación de la Tasa de Solicitudes y Protecciones de Red
-
-La SDP aplica limitación de tasa a nivel HTTP para frenar abusos automatizados. Cada par único `<IP, endpoint>` está limitado a 40 solicitudes dentro de 20 segundos (ventana deslizante). Las solicitudes que excedan este umbral recibirán respuestas limitadas hasta que la ventana se reinicie.
-
-### Modelos de Autenticación y Autorización
-
-Todas las rutas API autenticadas requieren que los clientes presenten una clave API emitida por SDP o un JWT derivado de los flujos SEP10/SEP24. Estos dos mecanismos funcionan en paralelo: los JWT son para usuarios interactivos, mientras que las claves API habilitan integraciones programáticas con su propio modelo de alcance.
-
-#### Roles de JWT
-
-Los JWT representan a usuarios humanos que inician sesión a través de la UI. Después de la autenticación, la plataforma los autoriza según los roles asignados a su cuenta de usuario. Los roles principales son:
-
-- **Propietario** – Control total, incluyendo la creación de usuarios, asignación de roles y edición de la configuración de la organización. El propietario es el único rol que puede otorgar o revocar acceso a otros.
-- **Controlador Financiero** – Puede realizar todas las tareas operativas (monederos, activos, distribuciones, estadísticas) excepto la gestión de usuarios. Este rol es ideal para el personal financiero que ejecuta pagos.
-- **Desarrollador** – Gestiona la configuración técnica como monederos, activos y claves API, y puede ver estadísticas; no puede modificar usuarios ni flujos financieros.
-- **Negocios** – Solo lectura en datos del negocio (distribuciones, destinatarios, estadísticas) pero sin acceso a detalles de gestión de usuarios.
-- **Iniciador** – Crea y guarda distribuciones pero no puede enviarlas. Mutuamente excluyente con el rol de Aprobador para garantizar la separación de funciones.
-- **Aprobador** – Revisa y envía distribuciones pero no puede crear nuevas; mutuamente excluyente con Iniciador.
-
-Cada endpoint API especifica qué roles JWT pueden acceder, por ejemplo, las rutas de gestión de claves API (`/api-keys`) requieren Propietario o Desarrollador, mientras que la creación de distribuciones requiere Iniciador o Controlador Financiero y el envío requiere Aprobador o Controlador Financiero.
-
-#### Permisos de Claves API
-
-Las claves API omiten los roles JWT y, en cambio, incluyen sus propios ámbitos de permiso. Cuando una solicitud incluye una clave API, el middleware valida la clave, confirma que la dirección IP del llamante esté permitida (si está restringida), verifica la expiración y finalmente asegura que la clave contenga los ámbitos requeridos por el endpoint. Las claves API se usan típicamente para automatización e integraciones servicio a servicio donde se necesita acceso preciso de lectura/escritura; crearlas o rotarlas aún requiere un usuario con el rol JWT apropiado (Propietario o Desarrollador) para acceder a los endpoints `/api-keys`.
-
-Los ámbitos disponibles se asignan directamente a los principales recursos de SDP:
-
-- `read:all`, `write:all`
-- `read:disbursements`, `write:disbursements`
-- `read:receivers`, `write:receivers`
-- `read:payments`, `write:payments`
-- `read:organization`, `write:organization`
-- `read:users`, `write:users`
-- `read:wallets`, `write:wallets`
-- `read:statistics`
-- `read:exports`
-
-#### Configuración Recomendada
-
-Para mejorar la seguridad, las responsabilidades de distribución deben distribuirse entre varios usuarios con rol de controlador financiero.
-
-1. **Flujo de Aprobación**: Habilita el flujo de aprobación en la página de la organización para requerir dos usuarios en el proceso de distribución. El propietario puede hacerlo en _Perfil > Organización > ... > Editar detalles > Flujo de aprobación > Confirmar_.
-2. **Rol de Controlador Financiero**: Crea dos usuarios con el rol de _Controlador Financiero_ en la página de la organización para garantizar la separación de funciones. El propietario puede hacerlo en _Configuración > Miembros del equipo_.
-3. **Gestión de la Cuenta Propietaria**: Usa la cuenta Propietario solo para la gestión de usuarios y configuración de la organización. Evita usar la cuenta Propietario para tareas de controlador financiero para minimizar la exposición de esa cuenta.
-
-### Buenas Prácticas para la Gestión de Monederos
-
-El monedero de la SDP debe utilizarse principalmente como monedero caliente con una cantidad limitada de fondos para minimizar pérdidas potenciales.
-
-#### Monederos Calientes y Fríos
-
-- Un monedero caliente está conectado a internet y permite transacciones rápidas.
-- Un monedero frío está desconectado y se usa para almacenar fondos de manera segura.
-- Aprende más sobre estos conceptos en [Investopedia](https://www.investopedia.com/hot-wallet-vs-cold-wallet-7098461).
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/single-tenant-to-multi-tenant-migration.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/single-tenant-to-multi-tenant-migration.mdx
deleted file mode 100644
index 7389292a50..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/single-tenant-to-multi-tenant-migration.mdx
+++ /dev/null
@@ -1,373 +0,0 @@
----
-title: Guía de migración de 1.x a 2.x
-description: Guía de migración de inquilino único a inquilino múltiple.
-keywords:
-  - migration
-  - single-tenant
-  - multi-tenant
-  - SDP
-  - 1.x
-  - 2.x
-sidebar_position: 70
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Aquí encontrarás los pasos necesarios para migrar una aplicación existente de la Stellar Disbursement Platform (SDP) de inquilino único (`1.x`) a una versión de inquilino múltiple (`2.x+`).
-
-## ¿Por qué migrar?
-
-A partir de la versión `2.x`, la SDP proporciona una arquitectura de inquilino múltiple, donde múltiples organizaciones pueden gestionar desembolsos bajo una infraestructura unificada mientras mantienen conjuntos de datos y gestión de fondos separados.
-
-Las nuevas funciones y correcciones solo se publicarán en la versión de inquilino múltiple.
-
-La versión de inquilino múltiple también se adapta a escenarios de inquilino único, a través de una configuración simplificada que se describirá más adelante en este documento.
-
-:::caution
-
-Esta guía fue preparada y probada con bases de código `1.1.7 -> 2.1.0`. Si estás en una versión posterior, es posible que las nuevas migraciones de base de datos causen un error al seguir estos pasos.
-
-Tienes la opción de usar la versión `2.1.0` para realizar esta migración, y luego actualizar a la última versión después de completar la migración.
-
-:::
-
-## Preparación para las migraciones
-
-### Detener la versión de inquilino único 🚧
-
-Antes de proceder con la migración, asegúrate de que la versión de inquilino único de la SDP no esté en ejecución. Esto es crucial para prevenir cualquier inconsistencia de datos o conflictos durante el proceso de migración.
-
-### Prevención de doble gasto 🚨
-
-Para evitar el doble gasto, asegúrate de que ningún pago esté en estado `PENDING`, de lo contrario, esto podría resultar en tener el mismo pago enviado de manera independiente por las instancias de inquilino único y de inquilino múltiple. Puedes hacer esto revisando la tabla `payments` por cualquier pago en estado `PENDING`:
-
-<CodeExample>
-
-```sql
-SELECT * FROM public.payments WHERE status = ANY(array['PENDING']::payment_status[]);
-```
-
-</CodeExample>
-
-De manera similar, revisa la tabla `submitter_transactions` por cualquier transacción en estado `PENDING`:
-
-<CodeExample>
-
-```sql
-SELECT * FROM public.submitter_transactions WHERE status = ANY(array['PROCESSING']::transaction_status[]);
-```
-
-</CodeExample>
-
-Si hay algún pago en estado `PENDING` o transacciones en estado `PROCESSING`, deberías esperar a que se procesen y se transicionen a `SUCCESS` o `FAILED` antes de continuar con la migración.
-
-### Eliminar cuentas de canal 🧹
-
-En la versión `2.x`, las cuentas de canal están cifradas utilizando el `CHANNEL_ACCOUNT_ENCRYPTION_PASSPHRASE`, que es un entorno diferente del que se utilizó en la versión de inquilino único (`DISTRIBUTION_SEED`). Para evitar problemas, eliminemos todas las cuentas de canal existentes en la versión de inquilino único antes de la migración:
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform channel-accounts delete --delete-all-accounts
-```
-
-</CodeExample>
-
-### Copia de seguridad y configuración de base de datos 💾
-
-Haz una copia de seguridad de tu base de datos de inquilino único antes de proceder con la migración. En este punto, la instancia de inquilino único debe estar detenida, y no debe haber pagos en estado `PENDING` ni `PROCESSING` en submitter_transactions.
-
-También se recomienda que crees una nueva base de datos para la versión de inquilino múltiple para evitar cualquier pérdida de datos. Usa el volcado de la base de datos de inquilino único para poblar el estado inicial de esta de inquilino múltiple. A partir de este punto, cada vez que nos referimos a **la base de datos**, nos referiremos a la nueva base de datos de inquilino múltiple que se creó a partir de un volcado de la base de datos de inquilino único.
-
-Así es como puedes hacer la copia de seguridad y la restauración:
-
-<CodeExample>
-
-```bash
-pg_dump --dbname=$singleTenantDB > sdp-singleTenant.sql
-createdb $multiTenantDB
-psql --dbname=$multiTenantDB < sdp-singleTenant.sql
-```
-
-</CodeExample>
-
-## Cambios explicados
-
-Entre los cambios introducidos en la versión de inquilino múltiple, los más significativos son:
-
-1. **Infraestructura**: la versión de inquilino múltiple incluye un corredor de eventos (Kafka) como un componente de infraestructura adicional que es altamente recomendado para configuraciones de inquilino múltiple, especialmente cuando se requiere un alto rendimiento.
-2. **Variables de entorno**: la versión de inquilino múltiple introduce nuevas variables de entorno para configurar el corredor de eventos, así como variables adicionales relevantes para la multi-tenencia.
-3. **Segregation of Funds**: the multi-tenant version introduces the concept of a distribution account for each tenant, which is used to submit transactions on behalf of the tenant. También existe la cuenta de distribución HOST, que se utiliza para financiar las cuentas de distribución de los inquilinos y las cuentas de canal TSS.
-4. **Comandos CLI**: algunos comandos de CLI han sido revisados para ser conscientes del inquilino, mientras que otros han sido incluidos para soportar nuevas características de inquilino múltiple.
-5. **Estructura de la base de datos**: la estructura de la base de datos ha sido revisada para acomodar la multi-tenencia y las tablas ahora están distribuidas en múltiples esquemas, proporcionando aislamiento entre los inquilinos.
-
-### Infraestructura
-
-Para la configuración de la infraestructura, SDP Multi-tenant ofrece modos operativos flexibles.
-
-#### Corredor de eventos frente a trabajos programados
-
-Los administradores pueden elegir entre usar un corredor de eventos para operaciones impulsadas por eventos, o trabajos programados para operaciones periódicas. Se recomiendan corredores de eventos para configuraciones de inquilino múltiple, ya que proporcionan una forma escalable y confiable de manejar eventos, mientras que los trabajos programados son recomendados para configuraciones locales o SDPs de inquilino único. Además, los corredores de eventos proporcionan una comunicación más rápida entre servicios.
-
-#### Versión de Anchor Platform
-
-Mientras que la versión de inquilino único usó [`stellar/anchor-platform:2.1.3`](https://hub.docker.com/layers/stellar/anchor-platform/2.1.3/images/sha256-e6ef4b17a8d3e5d1455fa3d8f5f7e2a2b9534ad749584ff5446d685eb07837e9?context=explore), la versión de inquilino múltiple requiere [`stellar/anchor-platform:2.6.0`](https://hub.docker.com/layers/stellar/anchor-platform/2.6.0/images/sha256-913fa2461d36d5150724a172ca46f8c76284a3890b60a9d5709fe0c606af78b9) o posterior.
-
-### Variables de entorno
-
-A continuación se presentan las variables de entorno que se han agregado o modificado en la versión de inquilino múltiple.
-
-Variables de entorno generales:
-
-- `ADMIN_ACCOUNT`: El nombre de usuario de la cuenta de administrador utilizada para autenticar las solicitudes HTTP al servidor de administración. Las solicitudes dirigidas a la administración deben agregar el encabezado "Authorization", formateado como Base64 codificado `"ADMIN_ACCOUNT:ADMIN_API_KEY"`.
-- `ADMIN_API_KEY`: La clave API de la cuenta de administrador utilizada para autenticar las solicitudes HTTP al servidor de administración. Las solicitudes dirigidas a la administración deben agregar el encabezado "Authorization", formateado como Base64 codificado `"ADMIN_ACCOUNT:ADMIN_API_KEY"`.
-- `ADMIN_PORT`: el puerto del servidor de administración utilizado para crear y gestionar inquilinos. El valor por defecto es 8003.
-- `INSTANCE_NAME`: el nombre de la instancia de SDP que se mostrará en el archivo `stellar.toml`. Ejemplo: "SDP Testnet".
-- `SINGLE_TENANT_MODE`: Cuando se establece en `"true"`, habilita el modo de inquilino único, que es útil para el desarrollo local o configuraciones de inquilino único. Además de establecerlo en verdadero, necesitarás configurar el inquilino predeterminado llamando a la solicitud [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx).
-- `TENANT_XLM_BOOTSTRAP_AMOUNT`: La cantidad de XLM que la cuenta Stellar HOST depositará en la cuenta de distribución del inquilino para su arranque.
-
-Variables de entorno para la configuración de cuentas Stellar:
-
-- `CHANNEL_ACCOUNT_ENCRYPTION_PASSPHRASE`: Una clave privada ed25519 compatible con Stellar utilizada para cifrar/desfijar las claves privadas de las cuentas de canal. Cuando no está configurado, se utilizará el valor de la opción 'distribution-seed', que fue utilizada en la versión de inquilino único. **Atención**, al migrar desde el inquilino único, establecer esta configuración en algo diferente del antiguo `DISTRIBUTION_SEED` impedirá que el código pueda descifrar las cuentas de canal.
-- `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`: Una clave privada ed25519 compatible con Stellar utilizada para cifrar/desfijar las claves privadas de las cuentas de distribución en memoria.
-
-Variables de entorno para la configuración del corredor de eventos:
-
-- `BROKER_URLS`: Una lista separada por comas de las URL del corredor de mensajes.
-- `CONSUMER_GROUP_ID`: Especifica un ID de grupo para los consumidores del corredor.
-- `EVENT_BROKER_TYPE`: Especifica el tipo de corredor de eventos que se utilizará. Opciones: "KAFKA", "NONE". El valor por defecto es "Kafka".
-- `KAFKA_SECURITY_PROTOCOL`: Define el protocolo de seguridad para Kafka. Opciones: PLAINTEXT, SASL_PLAINTEXT, SASL_SSL, SSL.
-- `KAFKA_SASL_USERNAME`: Especifica el nombre de usuario SASL de Kafka, requerido cuando el protocolo de seguridad de Kafka se establece en `SASL_PLAINTEXT` o `SASL_SSL`.
-- `KAFKA_SASL_PASSWORD`: Especifica la contraseña SASL de Kafka, requerida cuando el protocolo de seguridad de Kafka se establece en `SASL_PLAINTEXT` o `SASL_SSL`.
-- `KAFKA_SSL_ACCESS_KEY`: La clave de acceso de Kafka (almacenamiento de claves) en formato PEM, requerida cuando el protocolo de seguridad de Kafka se establece en `SSL`.
-- `KAFKA_SSL_ACCESS_CERTIFICATE`: El certificado de acceso SSL de Kafka en formato PEM que coincide con la clave de acceso de Kafka, requerido cuando el protocolo de seguridad de Kafka se establece en `SSL`.
-
-Variables de entorno del programador:
-
-- `ENABLE_SCHEDULER`: Por defecto "false". Esto habilita trabajos programados que reemplazan las operaciones de un corredor para sincronizar pagos entre SDP y TSS, así como para enviar invitaciones a receptores. Debería establecerse en "true" cuando el corredor de eventos esté deshabilitado. It should be set to "true" when the event broker is disabled.
-- `SCHEDULER_PAYMENT_JOB_SECONDS`: Interval in seconds for the job that synchronizes payments between SDP and TSS. Minimum is 5s.
-- `SCHEDULER_RECEIVER_INVITATION_JOB_SECONDS`: Interval in seconds for the job that submits receiver invitations. El mínimo es 5s.
-
-Del lado de Anchor Platform, debemos establecer las siguientes variables:
-
-- `SEP10_HOME_DOMAINS="localhost:8000, *.stellar.local:8000"`: una lista separada por comas de dominios principales utilizados para [SEP-10]. Esto debería contener los dominios de las instancias de inquilino de la SDP.
-- `SEP10_HOME_DOMAIN=""`: esto debería ser una cadena vacía para la versión de inquilino múltiple.
-- `SEP10_WEB_AUTH_DOMAIN=<localhost:8080>`: el dominio principal de la instancia de la Anchor Platform.
-
-### Segregación de fondos
-
-En la versión de inquilino múltiple, los fondos de los inquilinos están aislados entre sí **a menos que el inquilino sea creado con `"distribution_account_type": "DISTRIBUTION_ACCOUNT.STELLAR.ENV"`**. Para más información sobre los tipos de cuentas de distribución, consulta la sección de [Provisionamiento de inquilinos](./tenant-provisioning.mdx#creating-tenants).
-
-Las cuentas de canal, por otro lado, son compartidas entre inquilinos, y son creadas por la cuenta de distribución HOST, configurada en la variable de entorno `DISTRIBUTION_SEED`. Las cuentas de canal están cifradas utilizando la variable de entorno `CHANNEL_ACCOUNT_ENCRYPTION_PASSPHRASE`, o el `DISTRIBUTION_SEED` si la primera no está configurada. En la versión de inquilino único, las cuentas de canal estaban cifradas por el `DISTRIBUTION_SEED`. En la versión de inquilino único, las cuentas de canal estaban encriptadas por el `DISTRIBUTION_SEED`.
-
-### Comandos CLI
-
-Los siguientes comandos de CLI se actualizaron para ser conscientes del inquilino:
-
-#### Migraciones de base de datos y población
-
-Los comandos de inquilino único para la migración de la base de datos y la pre-población solían ser:
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform db migrate up           # ⚠️ DECOMISSIONED in 2.x!
-./stellar-disbursement-platform db auth migrate up      # ⚠️ 2.x REQUIRES A (NEW) TENANT-AWARE FLAG!
-./stellar-disbursement-platform db setup-for-network    # ⚠️ 2.x REQUIRES A (NEW) TENANT-AWARE FLAG!
-```
-
-</CodeExample>
-
-Los nuevos comandos de inquilino múltiple son:
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform db admin migrate up
-./stellar-disbursement-platform db tss migrate up
-./stellar-disbursement-platform db auth migrate up --all
-./stellar-disbursement-platform db sdp migrate up --all
-./stellar-disbursement-platform db setup-for-network --all
-```
-
-</CodeExample>
-
-Por favor, ten en cuenta que algunos comandos requieren una bandera consciente del inquilino, que puede ser:
-
-- `--all`: para ejecutar estas migraciones en todos los inquilinos.
-- `--tenant-id`: para especificar el ID del inquilino para ejecutar las migraciones.
-
-#### Cuentas de canal
-
-El comando ensure se actualizó de utilizar la bandera `--num-channel-accounts-ensure` a usar un argumento posicional:
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform channel-accounts ensure --num-channel-accounts-ensure 1 # OLD WAY
-./stellar-disbursement-platform channel-accounts ensure 1                               # NEW WAY
-```
-
-</CodeExample>
-
-### Estructura de la base de datos
-
-En la versión actualizada, la estructura de la base de datos ha sido revisada para acomodar la multi-tenencia. Como resultado, las tablas ahora están distribuidas en múltiples esquemas, y se han introducido nuevas tablas para soportar la arquitectura de inquilino múltiple. Los siguientes esquemas son utilizados en la versión de inquilino múltiple:
-
-- **admin**: alberga tablas asociadas a la administración de inquilinos. Sirve como el punto central para gestionar información relacionada con inquilinos y resolver nombres de esquemas de inquilinos basados en IDs de inquilinos. Ninguna de estas tablas existía en la versión de inquilino único.
-- **sdp\_&lt;nombre del inquilino&gt;**: son esquemas por inquilino que están precedidos por `sdp_`. Por ejemplo, para los inquilinos BlueCorp y RedCorp, los esquemas provisionados se llamarían `sdp_bluecorp` y `sdp_redcorp`, respectivamente. Estos esquemas contienen todas las tablas necesarias para la operación de la SDP adaptadas a cada inquilino, incluida la autenticación de usuarios por inquilino.
-- **tss**: es un esquema dedicado al Servicio de Presentación de Transacciones (TSS). Las tablas TSS no pertenecen a ningún inquilino, aunque cada transacción TSS contiene una columna que indica a qué inquilino pertenece.
-
-Estos cambios permiten el aislamiento de los datos de los inquilinos por esquema, asegurando que los datos de cada inquilino se mantengan separados de los demás.
-
-## Guía de migración paso a paso
-
-:::tip
-
-El proyecto tiene un [script](https://github.com/stellar/stellar-disbursement-platform-backend/blob/4420bba6628546918dfcca027ac504898121fed9/internal/integrationtests/scripts/singletenant_to_multitenant_db_migration_test.sh) que realiza estos pasos, así como un [CI](https://github.com/stellar/stellar-disbursement-platform-backend/blob/4420bba6628546918dfcca027ac504898121fed9/.github/workflows/singletenant_to_multitenant_db_migration_test.yml) que asegura que estos pasos funcionen. Puedes usarlos como referencia. Puedes usarlos como referencia.
-
-:::
-
-Usando la nueva base de datos creada a partir del volcado de la base de datos de inquilino único como punto de partida (como se describe en la sección de [Copia de seguridad y configuración de la base de datos](#database-backup--setup-)), ahora podemos proceder con los pasos de migración a continuación.
-
-### Desplegar la nueva versión
-
-Para transitar a una configuración de inquilino múltiple, despliega la última versión de la SDP `2+`. Si estás utilizando gráficos Helm, puedes obtener el gráfico Helm del [repositorio de gráficos de SDP](https://github.com/stellar/helm-charts/pull/80).
-
-### Ejecutando migraciones iniciales de base de datos
-
-Tras el despliegue de la SDP de inquilino múltiple, el siguiente paso es realizar las iniciales **migraciones de base de datos**. No incluye aún las tablas específicas del inquilino, se crearán más adelante.
-
-Comandos de migración:
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform db admin migrate up
-./stellar-disbursement-platform db tss migrate up
-```
-
-</CodeExample>
-
-Estos comandos crearán las tablas de administración de inquilinos en el esquema **admin** y las tablas del Servicio de Presentación de Transacciones en el esquema **tss**, respectivamente.
-
-### Nuevo proceso de aprovisionamiento de inquilinos
-
-Después de aplicar con éxito las migraciones de base de datos, el siguiente paso es aprovisionar un nuevo inquilino. Esto se logra haciendo una solicitud HTTP a la **API de administración**.
-
-Ten en cuenta que se aprovisionará a los inquilinos con todas las migraciones por inquilino incluidas.
-
-#### Iniciando el servidor API de SDP
-
-Para facilitar el aprovisionamiento de inquilinos, inicia el servidor SDP usando el comando:
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform serve
-```
-
-</CodeExample>
-
-#### Publicando en la API de administración
-
-- **Puerto de la API**: La API de Admin es accesible en el puerto `8003` por defecto. Esta configuración del puerto se puede ajustar alterando la variable de entorno `ADMIN_PORT`.
-- **Autenticación**: La API de Admin emplea Autenticación Básica para asegurar el acceso. Para autenticarte, completa el encabezado de la solicitud "Authorization" con `"Authorization: Basic ${Base64(ADMIN_ACCOUNT:ADMIN_API_KEY)}"`.
-
-Aquí hay un script de shell que se puede usar para crear un inquilino a través de la API de Admin:
-
-<CodeExample>
-
-```bash
-ADMIN_ACCOUNT="SDP-admin"
-ADMIN_API_KEY="api_key_1234567890"
-basicAuthCredentials=$(echo -n "$ADMIN_ACCOUNT:$ADMIN_API_KEY" | base64)
-AuthHeader="Authorization: Basic $basicAuthCredentials"
-
-tenant="bluecorp"
-baseURL="http://$tenant.stellar.local:8000"
-sdpUIBaseURL="http://$tenant.stellar.local:3000"
-ownerEmail="owner@$tenant.org"
-# NOTE: please refer to the distribution_account_type values in the API reference
-distributionAccountType="DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT"
-
-curl -X POST http://localhost:8003/tenants \
-     -H "Content-Type: application/json" \
-     -H "$AuthHeader" \
-     -d '{
-            "name": "'"$tenant"'",
-            "organization_name": "Blue Corp",
-            "base_url": "'"$baseURL"'",
-            "sdp_ui_base_url": "'"$sdpUIBaseURL"'",
-            "owner_email": "'"$ownerEmail"'",
-            "owner_first_name": "john",
-            "owner_last_name": "doe",
-            "distribution_account_type": "'"$distributionAccountType"'"
-     }'
-```
-
-</CodeExample>
-
-En el SDP de varios inquilinos, ciertas configuraciones que anteriormente se gestionaban a través de variables de entorno en la configuración de inquilino único ahora se almacenan en la tabla **tenants** en el esquema de administración. Este cambio permite que cada inquilino tenga su propia configuración personalizada.
-
-El campo **name** es importante porque es el identificador del inquilino. Los otros campos se pueden establecer con los mismos valores utilizados en las variables de entorno de la versión sin inquilino.
-
-### Importando tus datos
-
-Ahora que hemos provisionado un nuevo inquilino, podemos importar nuestros datos en él. Necesitamos copiar los datos de nuestras antiguas tablas al nuevo esquema de inquilino.
-
-Ten en cuenta que las siguientes tablas no necesitan ser copiadas:
-
-- **_gorp_migrations_**
-- **_auth_migrations_**
-- **_organizations_**
-
-Para ayudar con el proceso de importación, hemos agregado una función al esquema de `admin` que copiará los datos de las tablas v1 ubicadas en el esquema público al nuevo esquema de inquilino. La función se llama `import_tenant_data_from_v1_to_v2` y recibe como parámetro el nombre del inquilino. El nombre del inquilino debe ser el mismo que el `$name` utilizado en la llamada de la API para crear el inquilino.
-
-<CodeExample>
-
-```sql
-    SELECT admin.migrate_tenant_data_from_v1_to_v2('tenant_name')
-```
-
-</CodeExample>
-
-Esto concluye la migración de los datos del SDP a la versión de varios inquilinos. El siguiente paso es eliminar las antiguas tablas que ya no son necesarias.
-
-### Eliminar tablas antiguas
-
-Ahora, el único paso que falta es eliminar las tablas de inquilino único que no deberían estar en la base de datos de varios inquilinos:
-
-<CodeExample>
-
-```sql
-BEGIN TRANSACTION;
-
-DROP TABLE public.messages CASCADE;
-DROP TABLE public.payments CASCADE;
-DROP TABLE public.disbursements CASCADE;
-DROP TABLE public.receiver_verifications CASCADE;
-DROP TABLE public.receiver_wallets CASCADE;
-DROP TABLE public.auth_user_password_reset CASCADE;
-DROP TABLE public.auth_user_mfa_codes CASCADE;
-DROP TABLE public.receivers CASCADE;
-DROP TABLE public.auth_users CASCADE;
-DROP TABLE public.wallets_assets CASCADE;
-DROP TABLE public.assets CASCADE;
-DROP TABLE public.wallets CASCADE;
-DROP TABLE public.organizations CASCADE;
-DROP TABLE public.gorp_migrations CASCADE;
-DROP TABLE public.auth_migrations CASCADE;
-DROP TABLE public.submitter_transactions CASCADE;
-DROP TABLE public.channel_accounts CASCADE;
-
-COMMIT;
-```
-
-</CodeExample>
-
-### Conclusión 🎉
-
-Esto debería concluir la migración de datos de la versión de inquilino único a la versión de varios inquilinos del SDP. Por favor, asegúrate de ejecutar una prueba e2e para garantizar que todo funcione como se espera.
-
-[SEP-10]: https://stellar.org/protocol/sep-10
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/tenant-provisioning.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/tenant-provisioning.mdx
deleted file mode 100644
index 093336e2f1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/tenant-provisioning.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Proveer un nuevo inquilino
-description: Aprende cómo proveer y configurar un nuevo inquilino en la Stellar Disbursement Platform.
-keywords:
-  - SDP
-  - configuration
-  - tenant
-  - provisioning
-  - single-tenant
-  - multi0tenant
-sidebar_position: 48
----
-
-Esta sección cubre los pasos para proveer un nuevo inquilino en la Stellar Disbursement Platform (SDP). Un inquilino es una organización o entidad aislada que utiliza la SDP para gestionar los desembolsos. Cada inquilino tiene su propia configuración, usuarios, desembolsos y, lo más importante, su propia fuente de fondos.
-
-Los endpoints necesarios para gestionar inquilinos se pueden encontrar en la documentación de [Administración (Gestión de Inquilinos)](../api-reference/admin.tag.mdx).
-
-## Crear Inquilinos
-
-Los inquilinos pueden ser creados a través del endpoint [POST /tenants](../api-reference/create-tenant.api.mdx). Como un inicio rápido, puedes ejecutar el script [main.sh](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/main.sh) desde nuestro repositorio y asegurarte de reemplazarlo con los valores deseados.
-
-Las siguientes secciones detallan cómo se utiliza cada campo en el proceso de aprovisionamiento y, para que puedas asegurarte de que los inquilinos están aprovisionados como se espera:
-
-### `distribution_account_type`
-
-Este es, con mucho, el campo más importante, ya que determina la fuente de fondos (cuenta de distribución) para el inquilino, así como la forma en que se almacena el secreto para esta cuenta de distribución. Los posibles valores se describen a continuación:
-
-- `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT`
-  - **Plataforma**: Stellar
-  - **Ubicación de Almacenamiento del Secreto**: Base de datos, encriptada con `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`
-  - **Activos Admitidos**: Cualquier activo de Stellar
-  - **Aislamiento de Clave/Secreto**: Segregado por inquilino
-  - **Apropiado para**: Multi-inquilino y único inquilino
-  - **¿Cómo se configura?**: La cuenta de distribución se genera aleatoriamente y se financia durante el proceso de aprovisionamiento, y el secreto está encriptado y almacenado de manera segura en la base de datos.
-  - **Rendimiento de transacciones**: Aproximadamente 40 transacciones por segundo.
-- `DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT`
-  - **Plataforma**: [Circle]
-  - **Ubicación de Almacenamiento del Secreto**: Base de datos, encriptada con `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`
-  - **Activos Admitidos**: [USDC]/[EURC]
-  - **Aislamiento de Clave/Secreto**: Segregado por inquilino
-  - **Apropiado para**: Multi-inquilino y único inquilino
-  - **¿Cómo se configura?**: La clave de API de Circle es proporcionada por el propio inquilino una vez que tiene acceso al panel de control. El secreto está encriptado y almacenado de manera segura en la base de datos. El secreto está encriptado y almacenado de manera segura en la base de datos.
-  - **Rendimiento de transacciones**: ⚠️ Limitado por los límites de tasa de API de Circle.
-- 🔴 `DISTRIBUTION_ACCOUNT.STELLAR.ENV`
-  - **Plataforma**: Stellar
-  - **Ubicación de Almacenamiento del Secreto**: Variable de entorno `DISTRIBUTION_SEED`
-  - **Activos Admitidos**: Cualquier activo de Stellar
-  - **Aislamiento de Clave/Secreto**: 🚨 Mismo cuenta de distribución que el HOST
-  - **Apropiado para**: Solo único inquilino
-  - **¿Cómo se configura?**: El inquilino usará la cuenta HOST **tal como está**. El host es responsable de crear la cuenta y configurarla con el secreto `DISTRIBUTION_SEED`.
-  - **Rendimiento de transacciones**: Aproximadamente 40 transacciones por segundo.
-
-:::info
-
-Una vez que se crea un inquilino, el `distribution_account_type` no se puede cambiar. Si deseas utilizar un tipo de cuenta de distribución diferente, necesitarás crear un nuevo inquilino.
-
-:::
-
-### `name`
-
-Este es el nombre del inquilino en la base de datos administrativa. Se utiliza para generar el esquema de base de datos por inquilino, y también se usa en el panel de control para identificar al inquilino.
-
-No se puede cambiar una vez que se crea el inquilino.
-
-### `base_url`, y `sdp_ui_base_url`
-
-Estas son las URLs que el inquilino utilizará para acceder a la API y al panel de control, respectivamente. Se utilizan para generar las URLs específicas del inquilino que se usan en el panel de control y en los mensajes dirigidos al usuario o al receptor.
-
-Son importantes para permitir que el backend de la SDP dirija las solicitudes no autenticadas al inquilino correcto y para generar las URLs correctas en el panel de control.
-
-### `owner_email`, `owner_first_name`, y `owner_last_name`
-
-Esta es la información del primer usuario en la organización inquilina. Este usuario tendrá el rol de `OWNER`, que les otorga acceso completo y control sobre el inquilino.
-
-El correo electrónico, nombre y apellido pueden ser actualizados por el usuario una vez que se registre y acceda al panel de control.
-
-### `organization_name`
-
-Este campo se usa para completar el nombre del inquilino en el panel de control. Puede ser actualizado por el usuario propietario a través del panel de control.
-
-## Modo Único Inquilino
-
-La plataforma está diseñada para modo multi-inquilino, pero también puede ser utilizada en modo único inquilino. Este es el único caso en el que se acepta configurar `DISTRIBUTION_ACCOUNT.STELLAR.ENV`, mientras que los otros modos todavía se aconsejan.
-
-Para habilitar el modo único inquilino, necesitas seguir dos pasos:
-
-1. Establecer la variable de entorno `SINGLE_TENANT_MODE=true`.
-2. Como HOST, necesitas actualizar la base de datos configurando cuál inquilino es el predeterminado llamando a [POST /tenants/default-tenant](../api-reference/default-tenant.api.mdx)
-
-:::caution
-
-Una vez que esta variable de entorno `SINGLE_TENANT_MODE` esté habilitada, todas las solicitudes relacionadas con inquilinos esperarán que haya un inquilino por defecto y fallarán con un código de estado `400` si no hay uno. La respuesta de la API incluirá un mensaje indicando que falta el inquilino predeterminado.
-
-:::
-
-## Obteniendo Inquilinos
-
-Los inquilinos pueden ser obtenidos a través de los endpoints [GET /tenants](../api-reference/get-all-tenants.api.mdx) y [GET /tenants/:id-or-name](../api-reference/retrieve-a-tenant.api.mdx).
-
-## Eliminando Inquilinos
-
-Los inquilinos pueden ser eliminados a través del endpoint [DELETE /tenants/:id](../api-reference/soft-delete-a-tenant.api.mdx). Este es un borrado suave y, a pesar de que el sistema no proporciona una forma de restaurarlo, la información del inquilino no será eliminada de la base de datos con la implementación actual.
-
-## Actualizando Inquilinos
-
-Algunos campos de un inquilino pueden ser actualizados a través del endpoint [PATCH /tenants/:id](../api-reference/update-a-tenant.api.mdx). La documentación de la API proporciona más detalles sobre qué campos pueden ser actualizados.
-
-[Circle]: https://www.circle.com
-[USDC]: https://www.circle.com/en/usdc
-[EURC]: https://www.circle.com/en/eurc
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/README.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/README.mdx
deleted file mode 100644
index 0bf0873c9f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Interfaz de usuario
-sidebar_position: 100
----
-
-import DocCardList from "@theme/DocCardList";
-
-Una descripción y recorrido de las distintas partes de la interfaz de usuario de SDP.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/analytics.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/analytics.mdx
deleted file mode 100644
index 0148ecc1c0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/analytics.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Analítica
-sidebar_position: 60
----
-
-La página de Analítica proporciona información integral sobre diversos aspectos de las transacciones financieras, permitiendo al usuario rastrear y entender métricas clave relacionadas con los pagos. A medida que se disponga de más métricas y estadísticas, se añadirán más fichas a esta pantalla. La página muestra información como la tasa de pago exitoso, el total de pagos exitosos, el número de pagos fallidos y el número de pagos restantes. Además, muestra la cantidad total desembolsada, la cantidad promedio por transacción, el monto total en USDC y el número de individuos y billeteras involucrados en las transacciones.
-
-En más detalle:
-
-- La "Tasa de pago exitoso" indica el porcentaje de pagos procesados exitosamente sobre el total de pagos intentados.
-- "Pagos exitosos" muestra el conteo de todas las transacciones que se han completado con éxito.
-- "Pagos fallidos" revela el número de transacciones que no se procesaron, lo que puede ayudar a identificar incidencias en el proceso de pago.
-- "Pagos restantes" proporciona el número de transacciones que aún no se han procesado.
-- "Total desembolsado" ofrece información sobre el monto total de fondos que han sido enviados.
-- La "Cantidad promedio" ofrece un valor promedio de todas las transacciones que se han realizado en USDC.
-- "USDC" revela el monto total de fondos en el sistema, denominados en USDC.
-- "Individuos" representa el número de personas involucradas en estas transacciones.
-- "Billeteras" indica el número de billeteras digitales únicas involucradas en las transacciones.
-
-![Analítica](/assets/SDP/SDP24.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/circle-configuration.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/circle-configuration.mdx
deleted file mode 100644
index b4b704cb9f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/circle-configuration.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Configuración de Circle
-sidebar_position: 70
----
-
-Si el inquilino fue creado con una cuenta de distribución de [Circle], entonces el propietario del inquilino necesitará configurar manualmente esa cuenta desde el panel de control de SDP.
-
-Una vez que un usuario con privilegios de propietario inicie sesión, verá un banner en la parte superior de la página que dice que la cuenta de Circle está pendiente de configuración:
-
-![Banner de Configuración de Circle](/assets/SDP/SDP30.png)
-
-Al hacer clic en el banner, el usuario será llevado a la sección de Cuentas de Distribución, donde podrá ingresar la clave API de Circle y el ID de la billetera de Circle.
-
-![Configuración de Circle](/assets/SDP/SDP31.png)
-
-:::info
-
-La clave API se almacenará en la base de datos cifrada con la clave `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`, mientras que el ID de la billetera se almacena en texto claro.
-
-El ID de la billetera se utiliza para identificar la cuenta (interna) de Circle al realizar desembolsos. Es útil porque una cuenta de Circle puede tener múltiples billeteras, cada una con diferentes monedas y saldos.
-
-:::
-
-[Círculo]: https://www.circle.com
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/dashboard-home.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/dashboard-home.mdx
deleted file mode 100644
index 941c851842..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/dashboard-home.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Inicio del tablero
-sidebar_position: 10
----
-
-La página principal del tablero contiene un resumen de la actividad de desembolso reciente y métricas de rendimiento clave.
-
-Esto incluye:
-
-- Tasa de pago exitoso: El porcentaje de pagos completados con éxito (los pagos pendientes no se cuentan como exitosos).
-- Pagos exitosos: El número total de pagos que se han realizado con éxito.
-- Pagos fallidos: El número total de pagos que no se pudieron procesar.
-- Pagos pendientes: El número total de pagos que están programados pero que aún no se han procesado.
-- Total desembolsado: El monto total de fondos enviados con éxito a los receptores por una organización a lo largo del tiempo.
-- Individuos: El número total de individuos que están programados para recibir desembolsos.
-- Billeteras: El número total de billeteras utilizadas dentro de la Stellar Disbursement Platform. Esto generalmente es igual al número de individuos, pero es posible que cada persona tenga más de una billetera.
-
-![Inicio del tablero](/assets/SDP/SDP19.png)
-
-En el lado izquierdo del tablero de la Stellar Disbursement Platform está el logo de la organización y pestañas que te ayudarán a navegar por la plataforma.
-
-Incluyen:
-
-- Inicio: Este es el tablero principal que proporciona una visión general de las actividades de tu organización.
-- Desembolsos: Esta sección te muestra el historial y los detalles de todos los desembolsos.
-- Receptores: Listas de individuos que están programados para recibir desembolsos.
-- Pagos: Aquí puedes encontrar el historial y los detalles granulares de todos los pagos.
-- Billeteras: Información relacionada con la billetera de tu organización, la fuente de fondos para tus desembolsos.
-- Analíticas: Herramientas de visualización de datos que te ayudarán a analizar tus desembolsos y pagos.
-- Perfil: Administra tu información personal y organizacional.
-- Configuraciones: Ajusta la configuración de la Stellar Disbursement Platform según tu preferencia.
-
-El tablero también muestra una lista de Desembolsos recientes, proporcionando una imagen rápida de tus desembolsos más recientes.
-
-Cada entrada muestra:
-
-- Nombre del desembolso: El nombre único otorgado por tu organización a la operación de desembolso.
-- Total de pagos: Número total de pagos dentro del desembolso específico.
-- Exitoso: Número de pagos que han sido enviados con éxito desde la billetera de distribución de la Stellar Disbursement Platform a las billeteras de los receptores hasta ahora.
-- Fallido: Número de pagos que no se pudieron procesar.
-- Pendiente: Número de pagos que están programados pero que aún no se han procesado, generalmente porque el receptor aún no ha configurado una billetera.
-- Creado en: La hora y la fecha en que se creó el desembolso, mostrada en tu zona horaria local.
-- Monto total: El valor total del desembolso en el activo apropiado.
-- Monto desembolsado: La cantidad del desembolso que se ha pagado con éxito hasta ahora.
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/disbursements.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/disbursements.mdx
deleted file mode 100644
index 54fc8deb28..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/disbursements.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Pagos
-sidebar_position: 20
----
-
-La página de Pagos proporciona una lista paginada de todos los pagos, detallando el estado de cada pago y la información de pago relacionada.
-
-![Pagos](/assets/SDP/SDP20.png)
-
-La página contiene lo siguiente:
-
-- Borradores: Haz clic en el botón Borradores en la parte superior derecha para ir a una lista de pagos que han sido creados pero aún no enviados.
-- Nuevo pago: Haz clic en el botón Nuevo Pago para iniciar el proceso de crear un nuevo pago.
-- Buscar por nombre del pago: Ingresa el nombre de un pago para encontrar rápidamente detalles específicos.
-- Filtrar: Te permite reducir la lista de pagos basándote en criterios específicos como estado o fecha de creación.
-- Exportar: Usa esta opción para descargar los datos del pago en formato CSV.
-- Detalle del pago: Cada pago se muestra con los siguientes detalles:
-  - Nombre del pago: El nombre único asignado al pago por tu organización.
-  - Total de pagos: El número total de pagos dentro del pago.
-  - Exitosos: El número de pagos dentro del pago que han sido procesados exitosamente desde la cuenta de distribución a billeteras registradas.
-  - Fallidos: El número de pagos que fallaron durante el procesamiento.
-  - Pendientes: El número de pagos que aún tienen que ser procesados.
-  - Creado en: La fecha y hora en que se creó el pago.
-  - Monto total: El valor total del pago en el activo correspondiente.
-  - Monto desembolsado: La cantidad del pago que ya ha sido pagada.
-- Puedes hacer clic en un pago individual para ver sus detalles, incluyendo una lista completa de receptores y pagos.
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/payments.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/payments.mdx
deleted file mode 100644
index 528adce93c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/payments.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Pagos
-sidebar_position: 40
----
-
-La página de Pagos proporciona una lista de todos los pagos, detallando el estado de cada pago y la información relacionada.
-
-![Pagos](/assets/SDP/SDP22.png)
-
-La página de Pagos incluye:
-
-- Buscar por ID de pago: Ingresa un ID de pago para encontrar rápidamente los detalles de pago específicos.
-- Filtrar: Esta herramienta te permite reducir la lista de pagos según criterios específicos.
-- Exportar: Esta opción te permite descargar los datos de pagos en formato CSV.
-- Detalles del Pago: Cada pago se enumera con los siguientes detalles:
-  - ID de Pago: Un identificador único asignado a cada pago.
-  - Dirección de billetera: La dirección de la billetera digital donde se envía el pago. Un guion ("-") significa que la dirección de la billetera aún no está configurada. El pago no puede realizarse hasta que la billetera del receptor sea creada y vinculada en el SDP.
-  - Nombre del desembolso: El nombre del desembolso asociado con el pago.
-  - Finalizado en: La fecha y hora en que se completó el pago. Un guion ("-") significa que el pago aún no se ha completado.
-  - Monto: El valor del pago en el activo correspondiente.
-  - Estado: El estado actual del pago. Las opciones son:
-    - `BORRADOR`: Estado no terminal para pagos que fueron registrados en la base de datos pero cuyo desembolso no ha comenzado aún. Los pagos en este estado pueden ser eliminados o cambiados a `LISTO`.
-    - `LISTO`: Estado no terminal para pagos que están esperando a que el receptor se registre. Tan pronto como el receptor se registre, el estado se cambiará a `PENDIENTE`.
-    - `PENDIENTE`: Estado no terminal para pagos que fueron marcados por la plataforma respectiva de la cuenta de distribución (actualmente ya sea TSS o Circle) para su envío a la red Stellar. Pueden o no haber sido enviados a la red todavía.
-    - `PAUSADO`: Estado no terminal para pagos que fueron pausados manualmente. Los pagos en este estado pueden reanudarse.
-    - `ÉXITO`: Estado terminal para pagos que fueron enviados exitosamente a la red Stellar.
-    - `FALLIDO`: Estado terminal para pagos que fallaron al ser enviados a la red Stellar. Los pagos en este estado pueden ser reintentados.
-    - `CANCELADO`: Estado terminal para pagos que fueron cancelados manual o automáticamente.
-- Puedes hacer clic en un pago individual para ver sus detalles, incluyendo un historial de estado granular y detalles sobre la blockchain de Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/receivers.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/receivers.mdx
deleted file mode 100644
index 83afe2db80..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/receivers.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Receptores
-sidebar_position: 30
----
-
-La página de Receptores muestra una lista de individuos establecidos para recibir pagos, con información de billetera e historial de pagos. Esta información te permite rastrear y gestionar los pagos realizados a cada receptor, y proporciona una imagen de la interacción de cada receptor con un desembolso.
-
-![Receptores](/assets/SDP/SDP20x.png)
-
-La página de Receptores incluye lo siguiente:
-
-- Buscar y Filtrar - En la parte superior de la página de Receptores, hay varias herramientas disponibles para ayudarte a encontrar información específica:
-  - Buscar por número de teléfono: Ingresa el número de teléfono de un receptor para encontrar rápidamente su información.
-  - Filtrar: Usa esta herramienta para reducir la lista de receptores según criterios específicos.
-  - Exportar: Esto te permite descargar los datos del receptor en formato CSV.
-- Detalles del Receptor: Cada receptor está listado con los siguientes detalles:
-  - Número de teléfono: El número de teléfono del receptor, que sirve como un identificador único dentro del SDP.
-  - Proveedor(es) de billetera: El proveedor de la billetera digital del receptor (normalmente una aplicación no custodia en el teléfono de una persona).
-  - Billeteras registradas: El número de billeteras registradas y vinculadas exitosamente al SDP por receptor. Un guion ("-") indica que no se ha registrado ninguna billetera.
-  - Pagos totales: El número total de pagos destinados al receptor.
-  - Exitosos: El número de pagos que se han enviado exitosamente a la billetera del receptor.
-  - Creado en: El momento y la fecha en que el receptor fue creado en el sistema, mostrado en tu zona horaria local.
-  - Monto(s) recibido(s): La cantidad total que el receptor ha recibido exitosamente en el activo correspondiente.
-- Puedes hacer clic en un receptor individual para ver sus detalles, incluyendo sus billeteras vinculadas e historial completo de pagos.
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/wallets.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/wallets.mdx
deleted file mode 100644
index faf8d58584..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/admin-guide/user-interface/wallets.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Billeteras
-sidebar_position: 50
----
-
-La página de Billeteras proporciona información detallada sobre tu cuenta de distribución, que es la cuenta Stellar principal desde la que se realizan tus desembolsos.
-
-![Billeteras](/assets/SDP/SDP23.png)
-
-La página de Billeteras incluye lo siguiente:
-
-- Clave pública de la cuenta de distribución: Este es tu identificador único para tu cuenta de distribución en la red Stellar. Usas esta clave pública para recibir fondos en tu cuenta de distribución.
-- Saldo: Esta sección muestra el saldo actual de diferentes activos digitales en tu cuenta de distribución:
-  - USDC, EUROC, etc: Este es el saldo actual disponible para realizar pagos dentro de un desembolso.
-  - XLM: Este es el saldo de Stellar Lumens. Esto se utiliza para financiar la cuenta de distribución (reserva base) y las tarifas de transacción asociadas con la realización de pagos. Esto es solo para fines informativos y no es la fuente de fondos para desembolsos. En general, no necesitas preocuparte por mantener esto, ya que las tarifas de la red Stellar son muy bajas.
-
-### Añadir fondos
-
-Añade fondos a tu cuenta de distribución: Puedes depositar activos digitales basados en Stellar en tu cuenta de distribución enviándolos a la clave pública proporcionada. Asegúrate de que tu cuenta tenga una trustline para el activo antes de enviar fondos. Como principio general, no uses tu cuenta de distribución como un lugar de almacenamiento a largo plazo para el dinero. Está destinada a ser una billetera de paso para financiar desembolsos.
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/_category_.json b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/admin.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/admin.tag.mdx
deleted file mode 100644
index ac04e35d21..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/admin.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: admin
-title: "Admin (Tenant Management)"
-description: "Admin (Tenant Management)"
-custom_edit_url: null
----
-
-
-
-The Admin API oversees the management of tenants within the system, facilitating tasks such as provisioning new tenants, updating their information, and retrieving tenant data.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/api-keys.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/api-keys.tag.mdx
deleted file mode 100644
index 71bb54e4f4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/api-keys.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: api-keys
-title: "API Keys"
-description: "API Keys"
-custom_edit_url: null
----
-
-
-
-API Keys functionality allows to create access key with granular permissions and resource management.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/authenticate-mfa.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/authenticate-mfa.api.mdx
deleted file mode 100644
index 002cc5493d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/authenticate-mfa.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: authenticate-mfa
-title: "Provide Multi-Factor Authentication"
-description: "Governs the multi-factor authentication process for SDP user login, including the ability to remember the device so MFA is not always required."
-sidebar_label: "Provide Multi-Factor Authentication"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV01z2zYQ/SsYnJIMKTqetAfe5I80bpPUEznTg+NxluRSRAQCDLC0rHr03zsLkhZlJXLSNjPRRRKweHj7sNhd3EmCuZfppZy2VKEhlQMpa+RVJAv0uVNN+JvK3+wNOuMFVSjqVpOKS8jJOgFbC0XjbI7ei9I6MTs5F61HJ7SdKxMJZXLdFsrMAwpkSitaCbLCYY11hi6MF3ijchTeijcvp0J5YSwJ0EtYeeHwc6scFhMZSdugC3ueFTKVIxr45uVURrIBBzUSOvbvThqoUabyJKDHZycykoodqxAKdPKhv2cFo5UKnbDliJeM5EBCpiVoj5H0tNKM7VXdaLbA20bbAjcGeYU1yPRO0qoJluSUmcv1+qqDQ09HtlixxTYNlqA3EAUQyEjm1hAaYttnyTP+2sBvqF3KuoTrnFlcRcO2NvuEObE2jtUjhZ5X3VvuEHyoyps9Jx8Q1uxPd5jX9Rgws1YjmB3Eo25clBrmO6HAwdNB5tBQXsE12QWax3lesFmIQYfH0/OL41dTcQNaFYHqRLy7Hw2AHGWDdKI1mgOY9/94cjabHr0+vX532tt/FLk1pZq3XejxQo/ExMm1OJFr/oxDhIfDgG+s8Z3ehwcHuyc9a3O+OGWrHwi7feTQNLqfSD55a7bPf/85f6N426mgU6hzbB3JF1/ifgSFeNdF6f/HFp2z7nG2J0igtBeQ2ZbCqXUL13wNyYF/dKfgF95CuLybjeWZCSEjlGlakmO4UqEurktrZbr5PQ4iGfXjGbh7mwycMIiF53DJUIARyhDOOcbv1X2+q+57wwFhnfo7AP9Yeb9dNukJqB3bmZZvLkPU6D3Mv5BQ1l8T+y0n+bGbGxbDPi8Ono+QH674kcAB+zbmDDdHE/cJOc5ssYr7usK/O3A0XlnTFZ0FrmS6d2Ukb0C39whcEGqkynJNa2y4Tw1QJVOZ1CWnf4/uZqhprdMylWGRx7x1ilYzPv7ufI4QHDq+zaNzgEb9gaudW/T7XxecbYuQM7fzTyS8mhssxFJRxUF7Ojv85VfROHUDhGKBK67GvQzTXrchc41LLIuoTGkDG0WhZM4ItQYnTpTPWuexRkPiXAOV1tVien7GAqHzHcvDyfPJAWvQ1jU4lvaiQrEf48ns5Pwp300QZK0WWas0BTetm4PpqYY7WcMCRdbqhWhgxShhFMTc2bbhNsBhrhoVJrgdCtlm2N0gLa1bTHZr0U9H8YP5YC4q5cOWRtgGText63Lk9o3vuqAKiKc7KqEKNEMj9AAuEmCKMMFRLnIwnNxK25oiLKz4j9Z2yY2fw8Z6RdYp9CnziMWl7/CS/jsuRiLFTS9SnEG+QFNcPamIGp8myVxR1WaT3NbJdyE8TUVw/p7Kims6geq7294seKVM6cCTa3NqXe8gnws9dqaT7/CsdCGj/xfXBojHfFtiJgbbf+1NhbqO8woc+b2UR3YJOcSkBmWSfmCvP4+58Qp1LQJQ4F9go+1qeFfsv2utZ7tFm6EzSOgnHzhNEbra/1nO0IUeP5WDWz3NiXXzJBjFtox9bxZJrXI0PtSbIQE2kFcoDkOe6vIzY6VJslwuJxBmA1q/1Cevz45P385O48PJwaSiWoc8yam/BjMCPnf2RhUouhb8ZdeCTx92ilup527TK/yE77e+IBHeUtJoUIYbh6DYXV/ywhuGny8VF8L0Ut7dZeDxvdPrNQ9/bpGLwOUVF1GnIOOScnm1joaKwzWyUJ4nNq+1r0q058n3Ra5dcR8/KIdSLtfRUPuPO/j4ghE2Fvxy2xhN8xwbGk3vNHZbfcH5n7MLGXUNAz/fwtNNOljy4xSWgcB6/Q9FjJ0S
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Provide Multi-Factor Authentication"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/mfa"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Governs the multi-factor authentication process for SDP user login, including the ability to remember the device so MFA is not always required.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"Device-ID","in":"header","description":"Identifier of the device","required":false,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"MFA request data","content":{"*/*":{"schema":{"required":["mfa_code"],"type":"object","properties":{"mfa_code":{"type":"string","description":"Multi-factor authentication code"},"remember_me":{"type":"boolean","description":"Boolean flag to remember the user"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation. ReCAPTCHA token is required unless the `DISABLE_RECAPTCHA` configuration is set to true."}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Successful authentication","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string","description":"Authentication token"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/authentication.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/authentication.tag.mdx
deleted file mode 100644
index a7c1b1271d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/authentication.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: authentication
-title: "Authentication"
-description: "Authentication"
-custom_edit_url: null
----
-
-
-
-Authentication controls the log in/log out process for all SDP users, as well as the token refresh process. Authentication uses a JWT approach signed with an ES256 private key.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/balances.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/balances.tag.mdx
deleted file mode 100644
index 77993d11d2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/balances.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: balances
-title: "Balances"
-description: "Balances"
-custom_edit_url: null
----
-
-
-
-Endpoints related to balances. A balance is an amount of a particular asset held by an organization, tenant, or account.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/bridge-integration.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/bridge-integration.tag.mdx
deleted file mode 100644
index 458e0ab900..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/bridge-integration.tag.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-id: bridge-integration
-title: "Bridge Integration"
-description: "Bridge Integration"
-custom_edit_url: null
----
-
-
-
-Bridge integration endpoints for connecting organizations with Bridge services.
-
-**Integration Flow:**
-1. Organization opts into Bridge (OPTED_IN status)
-2. Complete KYC verification process via Bridge
-3. Create virtual account for USD deposits (READY_FOR_DEPOSIT status)
-4. Receive USD deposits that are automatically converted to USDC on Stellar
-
-**Status Description:**
-- NOT_ENABLED → Bridge service not configured
-- NOT_OPTED_IN → Organization hasn't opted in
-- OPTED_IN → Organization opted in, KYC link created
-- READY_FOR_DEPOSIT → Virtual account created, ready for deposits
-- ERROR → Integration error occurred
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-api-key.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-api-key.api.mdx
deleted file mode 100644
index fdad8fa3b1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-api-key.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-api-key
-title: "Create API Key"
-description: "Creates a new API Key to access SDP endpoints. API Key can be configured to have a granular read/write access, also API key can be restricted to the specific IP or range of the IPs."
-sidebar_label: "Create API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWG1v2zYQ/iuEPjWFX5KsXTd/S9MM9VY0QZOgwNIgoKWzzUYiNZKK6xr+73uOkmxZeXHTNsD2JZHJ48O74/G5Oy4iLycuGlxEBydD8RfNXXTZiRJysVW5V0ZHg+jQkvTkhBSaZqKSE94IGcfknDh9cyJIJ7lR2rveSiCWWoxIxEaP1aSwlPCSqbwhAE2s1EUqrQB00p9Z5alC6wiZOhNArtcglpy3KvYliJ+ScDnFaqxiMTwRBjhST0iYcZgbnrhe1IlMTlayDcNkZQVwoRsmLf1TAPS1SebRYBFBS0/a86fM81TFYWH/s2MPLCIXTymT/OXnOQHNjD5T7CscBePYhVpmhCFsmynnsD44M7esiFfkeH2QWeOwWXoStV3+tsik7rJz5CglwYvEGGaydZVrouXmTmtMaa2c34J8p5xnBzXWhGNY+VS5FXQnwoFk7i49SRcZ28q6DWSaYigcX/UdhhPlRoV1lMGjbiXQHg2ilmJSN2TXYs2RIJLL+SZQYyAIGDuRWn0NJ7YSag0GwcI1N6p/hakZ1KfGHuvfYdp5ADmv4tUIfcmNhcAljiFTelj6aw+/MKPs/CpBtN3lQBxjJhFoEQt0vQohs3lUx+FDpiJABRMES7dDQDzLChwq7ofSYXxceFy0HQ4N6G9mlFypPByj0XQ8xrltC7xTDKZ8g4RMEsu3G1seDt98KG8YkG+F2T2hsmxDH7A8R+AanFrwLlreYh9I17c/xGzLBz0xHAttvMA1u1EJJZ0w2+AOnHMixtZkQuo5No+WUM0rn1KLFT6UlID5ZfNee1tQGHA59i9v8f7uHv9rGVhzVsBMhCsCo42LNGU/fTfFbBKISrbTx7lWMEXAHdqDJMneRR4/lYn431assymzvC8Q2asINjqd44ARtxouMzqGiC9diEU721nuW8PvMfx3+/784KYV2sOh/zOo46jFGFVGbBhWReeV9N+5xccp6Q0WmklXx3xzg9E3RMQ5OFjMpmZ1Z1rKFnnyBMqmEqdSQTd3eZTGTZC22jx3xbzzJIo71vpeDitZikkMIi92d2/z1GuZiKr8EV1xI1OVlBFD1pqQEhtU9bz//DHsFCC2e/ENealSlJQjU/hgZrkw3AFvpdu6UzCPvsgsT6mxcTTUwSBkxLzgRWs48GCaXI2NgdTqW+DWr6i+U42PpF3J4BtlLyWOSQLZBDkFZS5NyAYXl06+Ixmca1n4qbHqawD+6R79dk9FXLwUTTmUcCMKzs7ARHJyB9ks7/Pve6TaDcvWWtT7wB8N5PaKEvmuDPhUu4Uj+uX2Ef1h7EglyJFPcj53u2+952PcsLGK1zmKC9Sp81DRvSZpyR7AaPy85AoqIziAm57cuKCx5LmoL3PVveYejxFsKLIZoLApZkPtVQOfsvWlgU34dSLMVdlHbbr0z49nVb2F5MbHwAVIaV9HODXhHD9TfsrX6Oh0/+WvKNvUDScqLuWiuiiJDqoTrMt3xeBTFCHh2nUi9tWHdQd3tHZZBbDinY3iodG2XLayLUq6/Rfd3Vfd/d/P9l4OXu4N9n/r7b7a+ztq1QKNC6j02ASfVER86inlpvZNo9MRJ6n0zPdM5MBip5e+2u/t9Xb5JIosk3Ze1UcPYzxDr73DnCVBRyYVo0KlPji72e8ErsrkNWE+vRZ1vxRadtQ8psi5LkCjpXIVJgy0Cixc767Jz4y97t1Zwv23VPykP+kzLt54Sy1wNXXXmcKikMRF5SuLZSgpMV2qgkTnTV5XRi24DjDKdB6bhOoWYmwKnYSF3GQZDgeEANTD/VIegUpuwHp0xYUr8frV/26z6+3mlZO6Ixlfk04un029z92g35/gUhSjXmyy/qMQdgYiGL9SZc4PLkiu7GEoW4kFqxCu4E60MzF3iaWBdSn/4Jn2HmEZGi1m0h8xrYbYZtuMRqKW/W5rppRm3Xgq0cs/qHJDru8tUT+DHv1q4EF7tpnxFsgiAAX9E8pTM+fw2moJqJblrgtkc8QvOZiGG+tBee54fAqGVzHzUm1WpWYPF7EfhLpm3HWVGKpW/OPScc2iB7lEHhD7gafKLMFYgJrNZj0ZZgNatdT13w0Pj96fHnWxpDf1WRrYmrMQusgGcFmy1k+FbZZpPMf9bx8fqzzpUbD0EQlIYMvKhYsqHV9Eq3SMZDTlTI2xxWIkHZ3bdLnkYaQ4Tg0X+LyRVnEPHpJ8p86GnL9D8x0dlj7rnvHOLJ4WZaZulRj8hFOuOIDRuX9QtllMnByfnkF4VD2ZZrhxGLVyxm9i+IsSgh9dfd2oh7EFmiE9KcrirMQMhc+tcqJ8d6w+Gg9VUs8bGrYLg9KQsu26Z8liURYrcGgtX07du6JybS3NZ3cJrf8FTv4Wzg==
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/api-keys"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new API Key to access SDP endpoints. API Key can be configured to have a granular read/write access, also API key can be restricted to the specific IP or range of the IPs.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","required":["name","permissions"],"properties":{"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","description":"List of permissions granted to this API key","items":{"type":"string","enum":["read:all","write:all","read:disbursements","write:disbursements","read:receivers","write:receivers","read:payments","write:payments","read:organization","write:organization","read:users","write:users","read:wallets","write:wallets","read:statistics","read:exports"]},"minItems":1},"expiry_date":{"type":"string","format":"date-time","description":"Optional expiration date for the API key (must be in the future)"},"allowed_ips":{"oneOf":[{"type":"string","description":"Single IP address or CIDR range"},{"type":"array","items":{"type":"string"},"description":"Array of IP addresses or CIDR ranges"}],"description":"IP restrictions for the API key. If not provided, the key can be used from any IP"}},"title":"CreateAPIKeyRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"API key created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"key":{"type":"string","description":"The actual API key (only returned once at creation)"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"CreateAPIKeyResponse"}}}},"400":{"description":"Bad request - validation errors","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-asset.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-asset.api.mdx
deleted file mode 100644
index 4b6d05c754..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-asset.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-asset
-title: "Create Asset"
-description: "This endpoint is used to create a new asset that can be used in a Disbursement. Note: the organization must hold a balance in a particular asset to use it in a disbursement."
-sidebar_label: "Create Asset"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVVk1T20gQ/Stdc0qqJIsQEqp0Mxg2bFggMQm1a3wYSW1rYmlGmQ8bRaX/vtUjCcxHyGZz2eVg7Jnu191vevpNwyxfGhbP2Llecim+cSuUZPOAZWhSLSr/M2aXuTCAMquUkBaEAWcwA6sg1cgtAgeJG+DGoAWbcwspl5BgZyYkcJgIkzhtsERpR3CmLMZgcwS1FRdKZyzkqsiAQ8ILLlPsvCuurUhdwfUQRBE2CNvtZ9voLGCqQu0hTzIWs0Of5JgcWcA0fnVo7IHKahY3DwodD+gJ9rVlLGCpkhalJXNeVYVIPXb0xZBPw0yaY8npG2ELjRkxmqoMWcCEMQ41UWrrClnMVPIFU0qk0pSmFWjI1ZvHzWBlrBZyyR4fBPYM9PB4w8uqII9P08kha28D/iOo3nYb5reDg8ne/snx29Or9/sX+39Mjj5PD68+7k8uPl19fn325+vJ5Yejz8ene2fjy73xh3ev/zo9PT4dv2Et/QVbFFjt0C+YSknTVbm78+p7pPd0g3FpisYsXFHU97gn9L2dncf+BzyD/lQDEHLNC3G7AInKalDaN1ul1VpkmHnyoq546ubeZ/QgXBswg6nTwtYsnjXsALlGPXY2Z/Fs3s4DdhMS0hJl2IcLKVwoeUlU0nfPrUVphJLGo6ywZvGzngFb88LdIlCgEm2uqJcrZXzvcEqCRb4XDKNE9Rp1F8HpgsXM+w35T6lFuyPYruK2R3gl3mP9qEd+v7rs7vBCaeDO5iht3/0BGLGUmMFG2By4hKPp7pu3UGmxpomwwpro7JmgaEoP4yVggsBz5BlqRjTTTfp4dy+Phm4crkXX3He9/QtdSsEXypcurO/4qcWCJsv2iIKLgtuF0iWML07oQFCbjpLd0avRDhHuypLrur9Iz2O8mE4uXlKjcbBKFZA4UVjP6fb4MzR3Sr5CSFyxgorXhOJXOSy1chWoBWhMRSX8hlpj19dDdIl2o/Rq9ORd/2+leC2vpVcVCilBVShDo5xO/S2lCdkJiTB9KkqCVR7+CbgAuMz8BvXLoD4L5WTmHXP6URRqI+QSNFbKCKu0QBNTHiHMTIcX9f/DbUEJq56kMOHpCmU2f5FbW5k4ipbC5i4ZpaqMfgrhZQy++NtUaqDBwwUxnCP0Zr4qIReaG6tdap3uC1yo+6w+eaajn6hsof3c+5XSBogf1bbBBAbbf11NjkUZpjnX1jyb8pZdZDViVHIho37h2Xp+VMY7LErwQD7/DKtC1dReP6wEnCG7lUtQS7RoRtc0Ey3q0pwvpqjXIqW5NJTVpzlSehl5o1AtQtObBawQKUrjh+UwbSue5gi7fk51YkBYcRRtNpsR97serXc10enJ4dHZ9CjcHe2MclsWfiiT1JRcbgF3DykYXlL3ZkxzJ53/u+diL4IWb2xUFVxIkglPXNMr7Yz1SjsPWE4SHM9Y0yTc4CddtC0tf3VIcjCbk3xrwRMSl9m8DQahuxP/w46p8JLi3qn9o7flPeW/OJ9esqB7EsQNKzth1HxDb1q+IcWnh6/tHhpNt9awgsul40uy7TDpaPkj9V959e+/UKbDlqy3Mnyo41059NkG33Fpmu5t0ba39t3Wdz16ugZrOo1527Z/AxqDc2E=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Asset"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/assets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to create a new asset that can be used in a Disbursement. Note: the organization must hold a balance in a particular asset to use it in a disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Asset to be created","content":{"application/json":{"schema":{"required":["code","issuer"],"type":"object","properties":{"code":{"type":"string","description":"The asset code","example":"USDC"},"issuer":{"type":"string","description":"The issuer","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Asset created successfully","content":{}},"400":{"description":"Bad request, invalid request body or the provided code/issuer is invalid.","content":{}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-direct-payment.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-direct-payment.api.mdx
deleted file mode 100644
index 92e557a704..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-direct-payment.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-direct-payment
-title: "Create Direct Payment"
-description: "Creates a new direct payment that is immediately sent to the specified receiver if they have a valid registered wallet. Direct payments bypass the disbursement workflow and are processed instantly."
-sidebar_label: "Create Direct Payment"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWetT4zgS/1dU/jSzhxMncR7Dpwsk7LLLMSyBoXZnKUq2lUSLXyfJZHKp/O/XLdmxQ7wQHlt1c1/Akbp/6pe6W9LKUnQmrcOv1gVdRixW0ro9sAImfcFTxZPYOrSOBaOKSUJJzBYk4IL5iqSGnKg5VYRLwqOIBRzowiWReiKBOUZkynw+5SwgwMb4AxOET3FmSeb0gQHoAw05zs64VEwA4YKGIVMNMtpaSRJvmVIpNWrApZcJybQIi0TcT8NkQWgcECoYSUXiMykBisdS0ViFy4Z1YCUpExR1Og02Wpk1ct2BRrB/Z0yqoyRYWocry09ihRPwSdM05L7mb/4p0TArS/pzFlH8UsuUAWji/QlwOQ5AB2hZGiWZBgfpmUL7goAgi+JMamQzX6JIJXg8sx774QoUL8ye86wL0BoRthfhwfMLDBGKnI7Ih0wywjhYGrwVkEQQZPyIyxmEXSQWZxEqG4OFHhgM+CFIxv3dcDKrIP9T6/hJULtOHZamBR4uZcbEvlyGmtAgEBAs5EPhMjIFOXLpibauzCWKlaC+utvHlMc5MVjTWq/rBRBsCvEe+4zY+TZZ7hqDLGCElLJxFgYSxSm20/u4/rLYnCgveDOiPHwBl6YvTIkA6TyJ2R3EhLePQzY4mo3kbABjUsFdAbw/kGEsJdpxwYay1gvfwHWQyFAYHsB+wwxWEeh9bH5jZDQW31vFm+c0ywmeja6Kt9g3yLwxDe/y9LJXiH/WHzQkBfcmOVVNhimDq5DVZ9xLk26BbF3NmUpkTA/INImlsWjbaeG/bRm2SwTx9QoBkZmPBWCaheHSOnh9Fn+5TzFHZzEHrSpWIImueIWYmC2/0SjVRum1PgV00O3bg367a7t+d2B/6nQC22+1Hep2B8yZdnV8vL5IVJdrOU7Dcd5cN0rA6ZQy3/U6ttvzHNsNPNemru/aPb/TdQZOt993uq/K59VFriej47cm+C3AH4+ORm7/9KR3dvNL/6L/r9H4y+T45rI/uri++dI5/60zuvp1/OXkzD0fXrnDX3/q/H52dnI2NJqYILujtd6A4hHhjBUAka14tK1J22l3bKdtO52rlnPodg+7rd8RNEuD9wcNGCSCt4H2ctBuDrqTbTDeJtD1hVSYYkk2gVTse+2N9yhZpXB9iLHeIAjsQa/l267rDuzBoNWxGe1Me0FA+167+2QdK6HmicjkP/PfDT+J9ilfJfs/Wu2O2+31B5+c7yk4av246dBzr7y53pVSdGlAP7EAMly3S223P2jb1GHMbvWcfq/PnIB5LVwvplF9e7lB+sI9AS09gajiUss4TyKW0tkzfHOlUnnYbD4YfigEhbMlS+9azp0fcix9QQIxEz+NRVNuB+yhsYsVMAALeXx/t1NV9papKYMU4d8pnvp2p3XVhi2M3m/03MF7xVQdcKXcmz5EG1hRle3R2mAMGtqaipmfL0aXw5Mr+H05Ho5+g/8X4/PR6fmP+DW8noxH8DG5Pj4eTybwdTI8PdNDx8Pz4zF+3pby5S3IxAj32i5o/ETzUzVZPm07Tus7yxOFvbaPymvdsrnQS+w0ZUc0IEVjt9V8/dD84SX9FhMi2aPYj5iCJC8J9ZJM6agxjMajgspnV9KqbCyxWdg6jc3dBI/TzLRRBZw+ht1NkwQ7oOIbr0E2PexBPu5RsaGBbxIzFki8HPEYoTFAKzbTfXJh0Jou9zqmmYI6xf+jgd/dovtbancrl2e1CJqs2iy8/iv7nifQo1Y1K6Uo1gF7VJAfcxjkup7+71pNu6iz66KTRHg8gK3/t/in3nzlmi8xwxaXVsfdVQc1P4HDw/cabi8Mi2mual1EuNWIuGQyyQScqeMNV7GcZH4muFpCkVpZR4wKJoYQO/Dzdn2LGBBHeO+YJjotphTnrGZxu2khgoDmS2qATEDbalnIWQBP0OrGLFX4jfrQlPzCljvp8eebK5LJ/FoLoxnLkzHLAZF8FuONK94xQTYaT9rdHkkFf4ASQe6ZvjY1LZk1zDeC5oRh7JGsOaNBfspHE1+Wt6fj0tLF0bVM4JuzJ1bYcrjw8eYKUZ8Zy/ni+FeObN3JVeKretLYXiM/EZQD261+Of746qmCXjbF29h1tLVNRWWex9NEOzGvssVZalS94b4IqcLyTYYXp7AORolxbrvRajgYOlkUUbF8dB6rx/gwGV18xFpFoQwlIfEyHiodHYmY0Tj3sK5REb1nMB/el5fwMErJTCRZij0a2JmnXE8keHBQldVjpvBmvlHb5v1vifhH/Ed8NcdXDInbADJQbOcbHfIRZqbNO4cRJYlhlbToUh/BHeiHCJzAACY+IEKx19lCM87xRxgmCwgBEA8SAlews5g8RDls8lUavGb+366+dthpbiTbo/49i4PbD8UpYga7OPPMCeIlCB8PiVZ+I8qS4L6CU5B5bMnJtFYQrpAhlch8lYlcQfSLes6njRdoNhW65LxFtQLiOd0WzCMF7au1mbMwsv05FUo+KXKFrqkEY008aTbzgSf1eU6NnwCZaCAtf8DSMFlieD2rCdQGpLvPIP1B/DIJqmEqZiKSn6cTKEncrx5VczEbsBGbmshOprbMyQ4sqLgsljrtF3UjpVC4SFvnKVPWEAugFotFg+pZjZazyubZ6fH4fDK2gaUxV1GoywuWzYjGFWBznVy8EpZPeFvJpvKE93/zjpmXSQWlpQkBAoV4nVt2lbcVX6208po7x44DxlYrj0p2LcL1GoehVGPF+AqfD1Rw6mH9gWbloKjq2IdAD2CZ1ywMxytcGcnDzHQcjzqs9UHBMfR9lqonaatN0cXnCR7qvfzZNTKFX9AFPqXCX2iF8P1WZ30k0GMrK6TxLDOdmcHUfd9OW3Sv26L8A7UqpuJlRcLHDY5RBP+iWrUsq5VpusCgBb2Z+kuO3LQFNfruFqT+LzAv1RU=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Direct Payment"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new direct payment that is immediately sent to the specified receiver if they have a valid registered wallet. Direct payments bypass the disbursement workflow and are processed instantly.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string","description":"The payment amount"},"asset":{"type":"object","properties":{"id":{"type":"string","description":"Asset ID (use either id or type)"},"type":{"type":"string","enum":["native","classic"],"description":"Asset type (use either id or type)"},"code":{"type":"string","description":"Asset code"},"issuer":{"type":"string","description":"Asset issuer address (required for classic assets)"},"contract_id":{"type":"string","description":"Contract ID"}},"description":"Asset reference - specify either id or type with required fields"},"receiver":{"type":"object","properties":{"id":{"type":"string","description":"Receiver ID"},"email":{"type":"string","description":"Receiver email address"},"phone_number":{"type":"string","description":"Receiver phone number"},"wallet_address":{"type":"string","description":"Receiver wallet address"}},"description":"Receiver reference - specify exactly one identifier"},"wallet":{"type":"object","properties":{"id":{"type":"string","description":"Wallet ID"},"address":{"type":"string","description":"Wallet address"}},"description":"Wallet reference - specify either id or address"},"external_payment_id":{"type":"string","description":"Optional external payment identifier"}},"title":"CreateDirectPaymentRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Direct payment created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the payment","example":"619da857-8725-4c58-933d-c120a458e0f5"},"amount":{"type":"string","description":"The payment amount","example":"100.00"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"7a4c68dd-861c-4448-8813-ea3f6dda7b25"},"email":{"type":"string","example":"horus@example.com"},"phone_number":{"type":"string","example":"+1234567890"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"description":"The receiver object"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"external_payment_id":{"type":"string","description":"External payment identifier","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DirectPayment"}}}},"400":{"description":"Bad Request","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-disbursement.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-disbursement.api.mdx
deleted file mode 100644
index 2555e7c244..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-disbursement.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-disbursement
-title: "Create Disbursement"
-description: "Creates a new disbursement in  `draft ` state with basic details. Important: a disbursement is not triggered until the organization adds receivers through the Upload Disbursement Instructions endpoint and the status changes from  `draft ` to  `ready `."
-sidebar_label: "Create Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGWtz2rj2r2j0Zbc7GAyYkPKNBHKbuynJBtJOt81Q2ToGbWzJleSwbIb/fufIhphAk/S1s/feL4Gg8z5H56U7atnM0N57OhAmzLWBFKQ19LpGOZhIi8wKJWmPHmtgFgxhRMKC8AowEZKQj1yz2JKPxFhmgSyEnZOQGRERDpaJxNTJaZopbZm0PcIeEDBEKkusFrMZaOAkl1YkxM6BKD1jUvzFUArCODdEQwTiFrQhdq5VPps7uKssUYyTqhLkVBqr8whRDQHJMyWkJUxyh4GC5oZEcyZnYEisVVpRwypCPmpgfEk+1mmNqgy0E+KUb4xRZUZrVMOnHIw9UnxJe3c0UtLiQe+O/tL4BT9MNIeU4Te7zID2qAr/gAhRM430rQCDp5KlUIEyVgs5o6saXbAkATsVfO8pM+bzh7egRSwip8I0FpDsAatRkHnqYqE/GU7PT6ZHp5eTV7RG3w37l9PX5yP3z8XpiNboqD85PR/1z6ang+no6vXR8BJjxgqbIMU3FXYnjtsKDTQTxhZmnKJ5WGSnhQifF2X4un96hlxfnY+Ga0614udpfzSYvu2fnQ0n0/5gcDkcjx9A7oOoiHlZkei4EGiCcjhhizCbbkmdgjFsBlMLaZYwu89NqxqFP1maJXDvS/p6SUaw2A5Pd7TlVAotDoedIPDCLrS8wGcvPcYD3wuazbjr804UhDGtepryVqvLDg4jrxUHvtdsAnghdA48vxW0WNRs+b7fovvdv+PlR/zz0PzPtQ59p3IyZ7dAGMnY0um9YMIKOSOx0mSp8uLm3d3VzytXfcRSWK3q5DgR0Q0eVj11JuTNaoVXtOAOuk5Xq9WquIJCA6e9mCUG3C8mU9IUF6vlN/FjO7H1dxIarVUvL8uypLRc4w+DKM+/yfsu48PEOpkDyaX4lAMRHKQVsQBNVOyS1AOxNoFFD5ovOTvsdL3DbqvjBVHn0HvZbnMPXc6CziH4cQfDeH8u2ScDQj7JdiuA0UnfclX2SRHlxqqUrJFIboCjpw1IToS8FZYV+dx5v6wEdYKoHznELE/sR1KyJsLInyzRYHMtgdfJqXTalcc/GVK6mQj7kyGZMkaECSBpxosiEaskUQuM1o1Et0wLFiZgevuDlizmIppjTUMC1XNnMOQZi1mOZQ5L0f7Y3qKRCHlDZiCxAgEn4ZKMBxcbo1jlgNbGID8LSSJmgNi5MOvSmmkwZamuWKBWKM5yq1JmRcSSZElYloHkKJ11sCD5i/pWEPxtd/q/rGQUmfxrs8K9fTuMs5fAO17Q6TAv6B62POYDeM0Dv3vQBZ9D2Hzsbt9TeiNCzaQlfWOEsYgzVylkbPYE3tzazPQajdsCn2VZPVIp4hvIpk1/GiUCpJ1ylTIhH6fFMuFxuK3v0uIA2RSDe7qTT58tU8PwDMkjvch1ZXzK7D5KsdIpnlDOLHhWuOJ7T77lt9qe3/XazUnL73X8XtCpHwSHvyPhPOM/gvDqPqreFqGz7uK+PYbimEEUhG0vOAh9L+Bh4LEgCryDqN3xD/1Ot+u7+hAp/ozM3EehiIOtMrkaD46RiDAmB/1cMgU0plgNxmwR/NfR0SDonp4cnL39tXvRfT0Yvhkfv73sDi6u3r5pj961B5Pfhm9OzoJRfxL0f3vV/v3s7OSs3/lO3m95fnvSRA/1Os3v5fldohwS+EaiByXRTkl0ta+Wji0kCdPEhRTZBNI65pw33J12k9Cj88Bl/2RCa/Ry2B+8ozU6nvQvJ8MBZs7+1dh9OT5/fXE2xB8rybLaLowLLv+QWaTQeToXxiq9rPBnWrMlrVFhITVP38PcgN47c1V91o7bnWb4EjzgfuwFfsw81m4GXjPodrph0OKsSOh/tyMwuIxlafbdgnv1GMtXhbGH0uolfQ4kAsUigenTla7asXoxhJ7f9lDEemS+V234m7KDVZYl07KxqgaDkBZmoHfbZkQgMk/DYm7YoFa4Nf0dylNTDjhfSN7kUQTGxHmyl9PhLqOYiQT4V7AqEPcrtMtGAzYjaPsv57TB/SwzlqocO54yzp452DkRSYG7mao4MYrETG+Fw6Hv133/PgAKnK/gYhUJ7yc4vsWk6W+4sFvQOJ59CZ8SZ80pA70210Mujslnrng5qwe+vzuMHzFOLos92vebwkFrtac7cYsaq9kzsvxOYi4iB0mUo9S+RdCDVVAphtNRb3S8F2HNJPD9Cll6Km9ZIjgppguSaXUrOHD648kXXtqzMrmSLLdzpcVfLr7+N900UpZsqbnPlM2qKR9g/EjChWvau645UToUnIP88X7Zr929AM8AcHoYiHIt7JL23t/RI2AadD+3c9p7f726rtE/PZw7ZiC9Mqq9UPGlVy5W8XthQpAGF0OOyg0sae9RzBq9ZUm+oYCMUrBzhXvRTLmrkzEUgjb41sMIyqtx6eQY5TqhPerQ12qM0ayF5arK3DeYmfgVljv59d9vJ8WyC1co6GxcBRYeqxEjZhJ48arCJBmOW50DkmlxiwupG1jifqY0SL+ME4eJfSwSnwPjeA9wVpOxctKUmXk9JGxt9i4SZrF9If2L02J7bAopW/Vm3Ucb5GnKsG/eGjT20/h5PLh4gYsoRqxSCQlzkVinZvVxx230UnYDJMyTm00Zdss4MtMqz4o6HYlMuAOFyy5b4S7BLpS+qe8tXf8sET/ID3JSrueYJCoD6RmV6wgwAeMtJHbO3MNYIYqSxKpsvZ59QK62edPCeCcRk9gBxCqX3CFu7TE1ZMoIq7QA00M5PPLeFPQa5ae31UxnpZG8kEU3IPn1z+tNzEzYeR4WW5gvofCiR5zyG1GWbhHLhCz2nSWY00rIWLPiGS/XpYLoF/uUT+tfoFmsXab8FtXWJJ7SbQEhWcN+tTZzSFIvmjNtzaMiV+AaVgM0sMltlD88qs9TaryCJCWOkJOfQ5aopVuTP3nXcoNwN3kIWoIFU/+AacqCTs15PAZ9K6Lquq8Us670rOGAPBV7pgSr0UREIE31qa2fsWgOpOXyVJGfkVav0VgsFnXmTh21EtU0zk6Ph6Px0GvV/frcponLk1gEUiYrhItHX/Lg1Xcr1VReff/fH8zLamfhT9vIEtwSr0p33JWV9T3drqzXuJ02Fg/u7kJm4EonqxX+/CkHrDXvr7FqF68vrjuorQvbfc0/LuzvuZ38fZHHF/hVbQ3UjyLIbOV4pz3a6gcuzse4cwnLh/3UrUypZgt8CGUL1wDUKNsp8zeuzJdfUMT1kVxWeD8s2IWI+BcF3otyd1c0EavVBr44+ixGaac1NHrjerVa/QeRl67T
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new disbursement in  `draft ` state with basic details. Important: a disbursement is not triggered until the organization adds receivers through the Upload Disbursement Instructions endpoint and the status changes from  `draft ` to  `ready `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"name":{"type":"string"},"wallet_id":{"type":"string"},"asset_id":{"type":"string"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"receiver_registration_message_template":{"type":"string"}},"example":{"name":"My New Disbursement name","wallet_id":"e2de8544-b7e2-40a9-ad40-411f70d5c4bf","asset_id":"d227a68c-2f40-11ee-be56-0242ac120002","verification_field":"DATE_OF_BIRTH","registration_contact_type":"PHONE_NUMBER","receiver_registration_message_template":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"A new disbursement","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Invalid wallet provided"}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Invalid wallet provided"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-receiver.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-receiver.api.mdx
deleted file mode 100644
index 8cde044a2b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-receiver.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-receiver
-title: "Create Receiver"
-description: "Creates a new Receiver. Allows clients to create a single receiver record, which can later be referenced in payments or disbursements."
-sidebar_label: "Create Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWdt32jgT/1d0/NTuxmAwt+RpSSBt0twaSLLbbA5HtgW48W0lOYSPw//+zUg2mEtDsu3u6cP2oTH2zE8zo9HcNDMkHQnj4N64Zi7znxgXxsOe4THhcj+RfhwZB8YRZ1QyQSiJ2ITkhCXSDoJ4Iogb+CySgsiYuIoSCIUfjQJGeEaLDzH39shk7Ltj4tKIBEDIiYM0Q8ZZ5DKP+BFJ6DRUaDEnni+clAumXpSMPSNOGKco1Im3ECsXBz5z9lfKhDyMvalxMDPcOJLAiY80SQLfVazlrwKVmhnCHbOQ4lMcscsh2GBmyGnCADl2vjJXZog+Zx4aiD2DwBENBr4HX2BFf5hBKpMlHKWTPhMICch+gA8ZopAcLGKsW7aLZIR6HmcCVB4SOV4aDaiHMQ8paJDhzWGZMUg7iNLQAYKd+FdITTT1BjygFXXaLWxGTHwPzAraAyYIuAG6apolLOWcTjdQbwvUJLO39oAN7D3DlywsQi42atX6+uumPgwsgVvpgd8M4uHA8bkcI7cfwf+RkiHf4CmjfBCCC403D0QfcNGcT1tk95QJaJBulWDdogmID46/AqSZ5/NV91NIOfLDHP7tvcVfJzQImPzPU1dAc6Ps8tE7RQfhSWuJm7QOR96F9JlUiIZ8/3pfzUy6W6meZEFA+foe6AVRm5CF8W6Yy0R7OUHyhRoaJcfecL78/QMuQ59PtGoVcELwJ+nLgG3E42sdjI35KpbkKVMvRALRQZugalXwz6qcOU6WUzwiUtcFGYZpEOAOvTq6v2z+7e7EnmmYKKWGLdtxGnbL9DxaM2sV1jBblrtvepbNGoy5VcqGr/H2JeKvlXq9XrUbrVqz/grPXjKmgleqtl1TTN86tUvyr17MfkOyUsxHyJMZckDly4xVq2qbVtW07H7FOqjVD+qVkmVZXxBDxhIkzZP0DhxkWO7aW7iGIDZI+joOy1AOBapG8OltTCNfgPVhqc1QsIWpopmUY4IdwziNtkaP1x59IZgcuLG3PVktlr3pdY5wZU3vC5Hu8rEPh4edWvPkuHF296l51TzvdG97R3fXzc7Vzd2tffGH3el/7t4en9Uu2v1a+/NH+8vZ2fFZu75Fvx0WsSzwDRUv8jDQ1mzzF+PrKy2060i0LNuyK17NrHgWnM5Wc990Gh6cTrfeqFWG+/utFivoxL9/Rau6z6rMs8whcxpmza1ZZsupNU2rZTdoq96sVWh1xRx5HDsDlZc55/sFqVOP7jOvbtbqdWrWmq2qSS3GzErDajaazPKYo9w1ouEO97r1HU4jSdpC+EJlknEcsoSOdvCNpUzEQbn8pPkhCpfcOFxRXifOXHWhM9jghZRXcOGj39un9u+n9u0n+/T4o/35vHN82ft0Xr04P/9y2Lu0b0/6je7N1ee7XueuetqsnVft6+veWXGh7RlxjWCwvVr8QQEzTbzvxvCjJ/9NGPubGAEVEtQVArZ1ICA+fgNtNQlLH1gk4EPjxqLVggcR818egY5OiamrI+rEqQRyX+T1yTY5K9YPSDA56SAX5WdKL/9lildmCnAymW63adazda7bx334fd1td/5Qfz+c9Prd624HfoBEHz7A08Nm3BU6BvX0AoulBuCbMubTv78n/6LIi2O4bbVF54WBxkTSXYfty9YEtbLqR22dbiTBRPNt5HdZ37Htm6HaU6MG+71R1x9Sj+S9wUoV/0v5l7cU7ozz+BV9ZYdJOOxiEZEY0Yy68OZ090YrVRb2XCxsnETQi/s4tEpSHd9yOOg3A28wjGPsH/JnArFw0QbtZe8dyhc08Ewixjw1SHOYjqiSjTJzaoNuaZRuIprKccz9/yngH27R11tq80hk/ZBqTlXq2QL/LftexNCPFjVbSpGvA/YoIK9zaORtzeE/tZraIntzi45j7viex6J/ZH+2m2+55lvMsMKl1NnfVOcojoYAJom5rAZoAMWSNyXsGSKH+HH9+dudcp6fFsHclPtyqia7h4xyxtuwX/DzAccWIYO9wzlyEqtQlFD8ZpT5YhCOEFw9IULKoeE2DGTNkXuohJaziL/MKIn/iW2Ok07v+iQVUDTh9AVdCIdU2j57RPijCD5NfDnGENDtVesNknD/CQfrj2xaMvKa3mhn3qc4MXEh+Bi2QYWMPQNtfb2ciXcL263HBwZIwX/L3EAV7+uDjGImL4wplq/Xhr3LGfr6jDUbiS428EEVtkNdn2f5Ix9xdQqDf3IVUIk5jrSvTvSCQpuxWoKyETcpDUOKmdzoQ3h/GeNdr3P1HkMxhSgbB8RJ/UCqfYj5iEaZLVUIDukjg+/B4/JOAt5SMuJxmuD0DRzFT/TVR4xHQBZWj5icxPyxtLH3P5+If0Z/Rn2s1HHJiMDhi0wRp9xl4HYxHilgoxI/a1Ggvpdxks8f1+D2AMNTH7BaVTc9kMuGUOh5inGMP/DeCJwAxIOz50OhAYf9AOUwyX3WmpWzv2bxEshMMiOZDnUfWeQ9vMub0BGcl9RBHy6/CeH9AVHKL0SZEoxcUOwLJWxGprQCd4WII3nqypRnCuYD1Bf3tPQGzYZcBc7vUS2H2KXbhDkkp/3b2oxZEJrumHIpXhS5QFeWnLEyNlTl7MWL+uxS4yMgEwWk5PdYEsRTdK+dmkAURrrHFGId+C8ToBqcWAh0obgc9iD4+25x0pGJiQPVsiIy46EpMjLoseFPJFSAzSN0QiFFkKqKUzqBIBZATSaTElVfFVrGKspnJ0fdi17XBJbSWIaBCuSYoUIaFYD1rJ0ULj9Xwkzh8vPnub3NEoOETFKGvYVsNc+MMsuS772xTL4POIaCxAwvZzOHCnbDg/kcX0NCw2h//4BJhfvUwdxxj/kky32YhSBT6koFrWD2i5dnB5sFCd6laY6267JEvkhbrB2uLnvY4TnZlXOoOnSD0wlexsH/UDDgtfXiKlS9mxkBjUapLiM1pirRNoqHR1U8ZA+F3EqjaUHC9TJAK4L/F64IV1lmM12agEFz+uzW8VscmWlzatw8vIT8P72WF1k=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new Receiver. Allows clients to create a single receiver record, which can later be referenced in payments or disbursements.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"oneOf":[{"type":"object","required":["external_id","verifications"],"properties":{"email":{"type":"string","description":"Email address of the receiver","format":"email"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External identifier for the receiver"},"verifications":{"type":"array","description":"Verification requirements for the receiver","items":{"type":"object","properties":{"type":{"type":"string","enum":["date_of_birth","pin","national_id","year_month"],"description":"Type of verification required"},"value":{"type":"string","description":"Expected verification value"}},"required":["type","value"]}}}},{"type":"object","required":["external_id","wallets"],"properties":{"email":{"type":"string","description":"Email address of the receiver","format":"email"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External identifier for the receiver"},"wallets":{"type":"array","description":"Wallet information for the receiver (max 1 wallet)","items":{"type":"object","properties":{"address":{"type":"string","description":"Stellar address of the wallet"},"memo":{"type":"string","description":"Optional memo for the wallet address"}},"required":["address"]},"maxItems":1}}}],"title":"CreateReceiverRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Receiver created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"400":{"description":"Bad Request","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"409":{"description":"Conflict - receiver already exists","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-tenant.api.mdx
deleted file mode 100644
index f35b9b1c4e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-tenant.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-tenant
-title: "Create Tenant"
-description: "Create Tenant"
-sidebar_label: "Create Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWW132jgW/is6OnvOtrO2IUBCh09LgJmSEqC8tduUpbJ9jTWxJY8kh6Y5/Pc9km1eAiXJbHt2PwHy1XPvla6e+8g8YEWWEjducNOPKcNzC/MEBFGUs66PG7glgCiYACNMYQsL+DMFqS65f48bD9jjTAFT+usvpV/0h/RCiIn+pk2pAF+D+1QqQd1Uwy6I5/GUqYW6TwBbmJFYf3CxJIx+M54XxdiKgVhATGi0+RVQIdW+QUSKkbmFDWoDc/cP8HTEidAJKQpSB2WsGg+FlY6KLbGFfZCeoIl2jht4EgJSJmWkJzioq5AMeRr5KCbKC5EKASVEKRAMffn3DbG/2fN//O0LXlsnUn2W293pKJ+O9DTEA+M2i8vBFgaWxnpx293xZNS9nE66g/6i2WoNpv2JM550er3myOn0Z9g6bdK+XMya097ke3at7qjV62zN5uv9nXlWXmYCSiUIBLaehojvC5ASr4/s7EshzVSzV1u4bVW8FE3P3IId1OXz4HambbBcImGRimcu2bg9RC7xboH5SIK4A/F3iTQEmo56DurqeqASBRQiH1GJGFcoEfyO+uBbplY0wopGEVoC04caEGdgIHzEmTEJuVToy2Vz3FlMR70vyOMsoMs0YwALEebvVF12GnQm0k8WKV28PKFpt+QTGbqcCB9d/pRkxu3hYtpdvDCntYXhK4mTCLY8gQX4HhcJPnmsn3269g5N9uufuQeHi+UximvggR46QnUN3CNSHSXOBh6Bj1pZ4NstwqFSiWyUSrlPOy8uR/qF/4NtfTxnY7te6xXbcnxAIglmRCacyYxtK+Uz/bFfCUO9q9LQG2KwyrcBW7vNhCRJRD2TUukPqaftdpbTFE/9Y9W42Vt8Vq9euOBX7br7a8Wu1S/K9psgqNjnZ4FbfgNQrv8a6BL/ua3C2YvJjVIwhfaDSWLPSbGVhbOD/f/x5/qk/z2/iqhUHt24vMtNOv1mf7JojTrNSaeNrWJgOBrMuuPuoL872GxNurN9u3ZnOzj/Xp8uetLz0lYQRURsunQ+WfcQHwVc7PRytkRByny5vyC/tz42r6ofr6qzd9Wr395W31+3fxuM311X+tfXny7Hg+qsO7noTIfvP4zbHypX9dp1pToajXs/QGY8jt0ojKcC/x/qjaPpfr9oDhPObAsRdVRlPTN9U0YdbOFhp9/u9n9fTMedUVFx3UHfxEvlwoeApJHaCc/lPALCDuK7zMZREJElUiExDLKSaBWCCkHsNisqs/gzbMSFbpSOQcy9FUTsGeHuL4g6tkABF7F+gn2iwFbUqOltZVbKlZpdrtqV+uSs3qicNc7PPumqSxP/x4P6EMH3QY/QLY1BKhIneoHY7uqsiESvJA/Ua5SDOn81rL3mdrMl5b2FfYJFTpftqTNs6S62V0Wbe9Jjht5w597uzPfUjG6J+E2t7Hukdm77Z35g12qeb7+pemf2xblXrlWq517lPCjc7CqfnyQgtpx/nMmPLY7hzPez9vVw0OlX3769urqozWqVd9PJoD/42K+3LmaV4Xg2bPY6s6v6sPuvweXFdbV9Nav391ezoUQK+2fkWB045XL50/7CnrBbW1hRZWoqvy9nIql2TAVNGUlVyAX9Bv6P0z4gBBeHp8hoWyWIfBrhgFNZGrsgNEQMUpLlkQaTpblTb3kYuM8V2ktzG0Xhp1Y+20F+PONnAhtsCV4qqLrHjZsHfEkk9ZqpCnHjZr6eW/ir7XEflsDs/L2H7XL/3s6PiP5+QFDZ+xK0eWECXxUwrXalcXEL97hxEtfCdyRKN/g6jBhUyPURTrhR/AnRIeJSxnr65GfKL3ORHTszschurMsn299LIAJEluRmH0lC38FhLlcfJtumqBcPmMor00KSLhn4aEVViAhDnXHl/AIlgt7p9G/h3tlySTNfdzNTH0QNHgLxdV3pZskCbqLJT08hTtpUuqmQEANTaBgRpZkcNYddvUggZBZlxTlzynoN0jgm4v6RwDmO8WrcHr7WzZQgxXmE3JRGyqS5e5uSSHEUk1tAbhrdooTcaxQzStBS8DTRekKARxNqHvC7vFsX3hmoFRe3zkkN9v8R4mf2mU30FVy7ZIgnwGzJU+GBvodrrsikCZV5KPrOzZNCUT2C296ydaUjjzDkAgp4yjaX9YBHEV9piSUg4ZIqLijIho7DRjcywyvln7a/s0h2ki9S0YDmr4ous6QqTF3H43HpRQivG8gkvwnlXr81UISyTHAVVyydFWWBIFKJ1FOpyBPU+6Ke2lPnBZkFwnSE/ya1AuKp3FbgosL2L2cTQhTbXkiEkidD3rErKQFQigllpXzgZD5PpfEWohgZoEzEQxLxe11eT2aCUqntblMXBAMF0vmsaUqBiOUgGIO4o97uBTYPU8uYkjGyeWDL3MzCEfWAyd3XSM2EeCGgiuGprSxqlEqr1coh5qlBy6fKUq/b6vTHHbvilJ1QxZHhSU3/MWE7wI+7zR7JbOhdwVdVSiJCmdHw2bU+ayI3uGgicwvr12d66OFB67epiNZrPfxnCppWb+a6NQlKXE3SN/qWk3P4trG1MhljTzIRW3Qy/d/A2iqMmp4Hidp5fKB49precDDWV0U3/8sh5r7Rp2Sl/44gK9Pr1uv/ACMxhh4=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/tenants"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Create Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"required":["distribution_account_type","name","organization_name","owner_email","owner_first_name","owner_last_name"],"type":"object","properties":{"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`"},"distribution_account_type":{"type":"string","description":"The distribution account type of the tenant.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"owner_email":{"type":"string","description":"The owner user e-mail address"},"owner_first_name":{"type":"string","description":"The owner user first name"},"owner_last_name":{"type":"string","description":"The owner user last name"},"organization_name":{"type":"string","description":"The organization name"},"base_url":{"type":"string","description":"The SDP backend server's base URL. If this field is not provided, the SDP will generate one based on the host `BASE_URL` configuration, and the tenant name."},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL. If this field is not provided, the SDP will generate one based on the host `SDP_UI_BASE_URL` configuration, and the tenant name."}},"example":{"name":"redcorp","distribution_account_type":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","owner_email":"owner@redcorp.org","owner_first_name":"Owner","owner_last_name":"Last","organization_name":"Red Corp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Provision a new tenant","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-user.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-user.api.mdx
deleted file mode 100644
index 13c4c185ce..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-user.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-user
-title: "Create User"
-description: "This endpoint creates a new SDP user as the result of an SDP owner adding their information in the UI. It also handles sending the invite email."
-sidebar_label: "Create User"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1lv2zgQ/isEn9pCsmLHzuGnTY/FprtoAzjBPrhBMRJHFmuKVEnKjtfwf18MJcdykjrbLgr0xZI1B7+5h2vuYeb4eMpvHFrHbyMu0GVWVl4azcf8upCOoRaVkdqzzCJ4dAyYxiWbvL1itUPLwDFfILPoauWZyRnoQDRLTVQhpJ4Rh7RM6tzYEkg7kzqI3Vz22KVnoJxhBWih0DGHeivEpF5IjwxLkKrHI24qtEHBpeBj/iZAIvQ84ha/1uj8ayNWfLzmmdEetafXV8kreriswBLoza8q5GNu0i+YeR7xypJeL9ERNZfW+c8aSuzwOm+lnvFNxBUcolqjGi0tBayFFY+49Fi6JyQ2EQ/GfYN0B2Wl8CEq/t4Umu9B4W8N8vvjpzytndToQlTbA5rnb40vM1PyzYbOIL9Ji4KPc1AOwxdXGe0aOwZHfXrsZ0bjeMGjrpuhqpTMQnSSL474uj7fHTNtAUVdmyIuSZ10nyHzcoF71m3tuo2eCZ0Uj/3Y8SLvnx6fpCiO49P0fBAPT0+O4rM8H8Sjfp4enSEenZ7nFMVDKdDVF+JwOCe67BSjAwH/oezZeWxHTo1RCHo/haaNe/gpDLOT0WgU9/PT43h4nh7HMOj34/x8lIpBeobZ+dF+bA7k27dSq5OJAheoKEgUvg5ab2vcRC2oUT4UeV+IODsb5vHwbADx2RBEPBr281wMT/B0BI9AgcYfBZVLDTqToD5TAluj1CN8TTVQykkfohf6TFMzw6eK4kZD7Qtj5T/fVxmHUxqtNfbJZME7b8E9r8F58HWXT9dlSqZEvETnYPZUJ9s8aD8tDP7BeLZn5g7F9pzhUb+j+aHEz1TchOb4cWh+NzaVQqD++XF52rodgP/AEOxwmNVW+lUo3NcIFu1F7Qs+nt5SUt7FmRE4Qx23cy9OjVjFbR3Qe+NC1E4a7YKWOa74+KBkxBeg6nsNdFCJvjBUopVxwQtAIHhSh52BcNoFvdEBtaWyC2Jb+BNyZ+OxrhG7DlfJP5Gw7gfs/d/XtF4Ilhsbgozat5GKmJMzjYItpS9o23g3GYxOWGXlAjyyOa5oUWgdcdHmR5CkRkrKCwQRSpn+5yagaWt84lEpsOytdGltHZaoPbtS4GlzYRdXl+QitK5BOej1e9QrXV2WYFdhZUJ2WMeLydurl0zSHuWNUSytpfLBTGNnoFuojnnDSpgjS2s1ZxWsSEv4CmxmTV3RqmUxk5UMBLNAGzam7eka/dLYee+Ra389iJ/0Jx12TTpSM1Ohjp2pbYassoaqj/kCPJEbKEYzb4L6J9RFDLQIBMpzloFmKbLc1FoEwYL+KGWWtGNarIyT3liJbkw4YjZ1jb6kfcai46S4ap0Up5DNUYvbF4X3lRsnyUz6ok5p0CTfpeHlmAXj76GsGLUokLrZrFu2YJXUuQXnbZ352rYGUlz8czHtfYdluQ0d8v+YtlXxnG1LTNmW94etKVCVcVaA9e4g5A5f4i1iUoLUSfvhoD3PmfEHqpIFRQG/wEqZ1fYKc7jWaE2fsXmdotXo0fU+UZvyaEv3MZ+gXciM+tLWrBZmz9hZEphik8euZYu4khlqFwbLtgFWkBXIBqFPNf2ZdI2TZLlc9iBQg7ZW1CV/Xb5592HyLh70jnqFL1Xok9T8S9Adxc0VgLWXr70W07l8/Yp3yHbyeLzzSaVAhg0+uGbdTrcpr7c34oKm3njK1+sUHN5YtdnQ5681Ur+f3tLEtBLSsGHfbqLtcNnN2zeNL+JrOnY3YOlSSutvw3SRZVj5DvnRarI3i68+Tq551Azp8ZqXRpCMhSXtuLAMQzji8GjUzsOobV8I4pakV52zHw7NBiL9EuAnRdbrZpBvNvf8DembEq2fttwUhdvNZvMvTKbC3w==
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create User"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/users"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint creates a new SDP user as the result of an SDP owner adding their information in the UI. It also handles sending the invite email.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"first_name":{"type":"string"},"last_name":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"email":{"type":"string"}},"example":{"first_name":"John","last_name":"Doe","roles":["business"],"email":"email@email.com"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Created","content":{"application/json":{"schema":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-wallet.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-wallet.api.mdx
deleted file mode 100644
index 2a9b24e2f0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/create-wallet.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-wallet
-title: "Create Wallet"
-description: "Creates a new wallet provider that can be used for disbursements. The wallet must be configured with supported assets and proper authentication domains."
-sidebar_label: "Create Wallet"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWFtT2zgU/isaP7WdOAkUaMsbBXbKLtsyhW53ljKMbJ8kWmzJK8lJ00z++54jybFzKYFeZvoCjqTznYvOVbPI8qGJDq+jd3rIpfjCrVAy6kQfeZ6DNdFNJ8rApFqUbuMwOtbALRjGmYQJm7hjrNRqLDLQzI64ZSmXLAFWGcjYQGmWCZNU2kAB0pouuxpBTVdUxtLRVMmBGFYaCSbCjpipylJpiz+5MSgG4zIjJiWy4JUdIZBInagsUwUX0nRRZtp2i2fZQlCvB25q+K8CY1+rbBodziLkaBGFPnlZ5gGt968hJWeRSUdQcPqy0xIQTSX/QlrjCBSUbCZ5Abg0UgWUfEifGUB5mwt5dxsQOpHBlZ3+bZoL5HfrxSWzenWsAENsHFTDzlgt5DBaNf6bquAyRsUynuTAiIipAVodVm8imrfk2o4bTrIP78/vAVzTbivwCVIwomCewvlDC71le2Kw0VZbmVyeXsQ7feapgkM4RsuuQgxAkuGyFmaiVA5croF+HAESLwkrDAv0Dh3921ENeJWjI1ldAXLwDttiwLXm0zX4I1olU7vzTMMANMgUA6vx/WSK3JHppPZhYaFw0ErCuwF64Lp7rnBZBifEs5No1fdEtt3GHgmJ5/PlGEDim3lnmyDHOeop0lVt10TxKOvCgKwK4pZ6HGKJIZw9wLW94O4s0ghjKvTlB1L504xnmQZj1lR3EEGOBfQDjPEW3XEM7O/zP7/bHtJBIdNNot3M3br3yFuRbfXKWXQOQ55O1/3z7MSwJ5jXpbKL1O4ydcjPAwF59tRZuPbRZZHnJIkVNoeV1Pze52V/oFEhRBPavVTSeGPs9nfo30qc+thMHWSG0ZNiEJlBledTdzffmOYfEiHwmRelU2gfE/IryPbjvf19Hu+9eLkb8z5AvHPQf3HwAvoZJDtknK9l+QbpL5FojlkMHVCQVe7P4g3dyNrSHPZ6Y0+PynZTVTwmpzZYvBRxBuPuOtZDCsA2mXomKwme8MKt3XK7CQmTbEE7UYaHYitcsW3gd/u7z+P+i/j5ztVu/3C/f7i33z3Ye/kPAVdl9jOAWz4cGou589u9fn/dM1/zjIWug8VszHOR+ZYFtFbaLHvns96zxzikg3hI+bVc5Ng+JaqyrpR5QqqEn63mZisnp97CNAvG0Zl0CjEhy8pGbTiXCm4HSuGpxTfVzkVwd8J6wvXiDH5jQwmZYVZRhsEWUqBxhtR4zGsjbwj/D5KKvNLiiwP+4RZ9uKWQgtuqfQ5zdOIbpwJT0sYQnn/Nvm8x0S5p1khR80F7tJBXKTzypqT3s7i5K3q+fkW/KZ2ILAP5U+5ns/kano8xwxKVU+fVujrHOKsgGMV06Aspq3dYnac7jEae1b6X59S1Txl8xrRuflxlerzbzut4MpBWWtip6yNfA9egj/BG8Sc2DnTXeLs0SJXKOL6c9qLeJEyGBKDHoI2jr3SOmxER1riXpIKXso3etCCl+APWO+PfP141o+NyB99hRgzlovWQ7PRyd/8ARxQxxkTO7mBKY6AvstFR8M56oqWqF43wElxK6URk6ffNUHjauEMAWOTUpgK38+xqJWz2NlfcdvMWhhBqcpqJ4dr3Gc0VLixVd711z9tA1f3sBqLQGtKNtDvA6/ootdBCDpS7kVDULi3kOWbik9bEzi5ybqlisqOLM2RJV+5vare70+2TvlVRcE1dI43292M8uTy5eErVgGOiVzlLKpFbd9Wq9QDhqkDB73BiqfI7VvKpezugVc6GWlUltaYaUlEKt6HGYVSruUuwE6Xvumvu9euJ+El+klc05xFLyTC6ZWxUpXFew1inmPXPKrjtRcEWwqqyntNX4DrurYQ2yFfqt5iBqnCVCEf0I8/VBH0AxcPgFhbDBMwhyRGza+PxeuF/3H69ictgpDjh6R3I7OZJ3eQNMSSrxDd4j0F4esic8gtRpvQaZOlNxwkbjjmt0F0xpWHUpLbSQcH6QeHeO+0+QrOBdpn5e1SrIbbpNoGE1We/WZsR5EWcjri25l6RW+d6VgP0KC31wsK9+mxT4w0iMwfkn/ugzNWU3GurJpjo6dxdhX0S+i8YVA0j1oIuzLvBJdYXkbYniSBmFwOx5w7FahCbcKwTYRUFHBZbOfyo5Jie2a7LU75GERZCTSaTLne7Di2Qmt752fHp28vTGEm6I1vkrlZQCSy4bAH7EZYtnhdX5uhFdf+V30tDobDYKfTwroV7IXNGmoVqfx1NmnfgEfUBuDSbJdzAB53P57SMFZRy/zV+jrkWVNpcC9Gpiy0VNizNvnUiq8RX/uEEJ4jKNwIr/Q9VMU9xhNN8ae89225VLt5dXuHhJDzyFr5aaj6hh1v8ix0KPRO7/E0H3NosyrkcVr7Ae0zXM651K3euWwkfrcc3LqctCVf7Dq8I/W0V52WS2cz3QmjQ+rzf+ipFMG19mq7uBqX+H3M9Vps=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Wallet"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/wallets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new wallet provider that can be used for disbursements. The wallet must be configured with supported assets and proper authentication domains.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","required":["name","homepage","deep_link_schema","sep_10_client_domain"],"properties":{"name":{"type":"string","description":"Human-readable name of the wallet provider"},"homepage":{"type":"string","description":"Homepage URL of the wallet provider"},"deep_link_schema":{"type":"string","description":"Deep link schema for the wallet application"},"sep_10_client_domain":{"type":"string","description":"SEP-10 client domain for authentication"},"enabled":{"type":"boolean","description":"Whether the wallet is enabled for use","default":true},"assets":{"type":"array","description":"Array of asset references supported by this wallet","items":{"oneOf":[{"type":"object","description":"Asset reference by ID","properties":{"id":{"type":"string","description":"Asset ID"}},"required":["id"]},{"type":"object","description":"Classic asset reference","properties":{"type":{"type":"string","enum":["classic"]},"code":{"type":"string","description":"Asset code"},"issuer":{"type":"string","description":"Asset issuer address"}},"required":["type","code","issuer"]},{"type":"object","description":"Native XLM asset reference","properties":{"type":{"type":"string","enum":["native"]}},"required":["type"]}]}},"assets_ids":{"type":"array","description":{"Legacy":"Array of asset IDs (cannot be used with assets field)"},"items":{"type":"string"}}},"title":"CreateWalletRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Wallet created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"}}}},"400":{"description":"Bad request - validation errors","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"409":{"description":"Conflict - wallet name, homepage, or deep link schema already exists","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/default-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/default-tenant.api.mdx
deleted file mode 100644
index faed38b9f2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/default-tenant.api.mdx
+++ /dev/null
@@ -1,77 +0,0 @@
----
-id: default-tenant
-title: "Default Tenant"
-description: "Sets the tenant specified in the request body as the default one, resolving all the incoming API request to that tenant when the env `SINGLE_TENANT_MODE` is set to true. Once set, the default tenant can be overwritten but never unset, although it is only effective when `SINGLE_TENANT_MODE` is set to true."
-sidebar_label: "Default Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWG1zGjkS/isq1VVdsssMGLCd5Rs2JMGxgRhMcnF8RDPqYbSekWYlDYS4+O9XPS+82MR2crtX92G/BEfT72p1P9131LKZoa1r2uaxkPSmQjkYX4vECiVpi47AGmJDIBYkk5aYBHwRCOBEyOxcwx8pGEs8xZeE5bQcApZGligJFaLBqGgu5IywKMo+C+mrGA/aw96a3ypiQ2ZLPYsQcvkg5+TLqNd/c96djrv9dn88vRh0ul+IMMRAzqdTcMlA+oAnlR0TCnE+k8QDouagF1pYC5J4qSUS5qBJKjM2FtlQpbOQCIvClYyWBIIAfCvmkBv0HEM+y8+ys6tdGJIaCNKIBEoTDnOIVBKDtCRJdaIMGKL0xuVRZ1iwcOItCSNGyFkEROkZk+Ibw6txyTgUBkOqFnnQt7+iMeZWJMV1LTHYW5coJEHHl+vgM8mJEXES4dWatREGbJoQlYDOpLIoWqJBGmI1L0VKAE5UQBKt5oLj6UJE3Geak/H5iPigrQiEzyyYzPs4jaxwymtRMhCzNBdv3M+SVuhaXY/TFi0iOc7oaYUWFp8ovqStO+oraUFa/POX6i/4Y/wQYoZ/IanQwDG7BcfUtssEaIsq73fwUViiUZkVYJBecPy3oDFWCzmj95/DeCuI3KWrVYXCVxYnEZQS6MFx48gD3nCOvd/qTvP4qOa8CoK6c3gQeLVXALXj3wK6WiHrxsKARQayE5MoaXKD6rUD/Nm14F5qcbBMRIZWtkPBkiTCkAslq78bZNuOy89EYe3kM92rUMli+KF4IoNLepaYUKURJzGzfpilWMKsBS3Jl39fM+ebc/PrP764OzZ5UQq+0gnq9ZiBaaqj5+nGLPeYfwv4AEDPQf/TEBRBri7Pd5WE1iamVa2WypyCzzU8cZWeoXLDk2kqpj9uw1WvypkJPYXv5uRZ+nf0WmZTs/fiZBrjAygq1ulltz3udmilPBheDia9UW/Q3z5sn457k126TndzeLOqUC5QhZeiH1Pm+yqVdso412D22rHHbQtRxDQpmEnBnJe9rE6uVcgZCVLJzW5A3px+bJ81Pp41Ju8aZ6/fNt5fdF4PRu8u6v2Li08no0Fj0hsfda+G7z+MOh/qZ8fNi3rj8nJ0Tr9nfm7zz9iOHE8aXtxEpzcaX/ZOrsa9QX/aPj0dXPXH7mjcPT9vX7rd/oRWHifpnEwn7avz8ffoTnuXp+fdDdl3b+v7SfPQ4ZwW63zWXLfErWPwTPezNOrSCh12+51e/830atS9LDOuN+hn9gozLRr4lnmeUhEw+cC+k/ycBBGb5RjChNgUFyHYEPRO47uHTzSRyrqZxEJbWYh9DcwCnzK7L0CB0jF+oZxZcKyIYScz67V606k1nPrx+OC4VT9oHR58wqxLE/7nC+UQwfeF7im3IgZjWZxsAEeJuZghL4wK7EtSCHV/1qyd5na9Kco7gX2iijyeto+94Qp2sZ0sKvrRwwq9rp07t3PzsK2/ata4z5qHDj/ggdNs+tx51fAPnKNDv9asNw79+mFQqmlRDTxrSNv9aF3Bi48PGsie/nGfZ5u2eL77K/m+4GQ18/2kczEcdPuNt2/Pzo6ak2b93dV40B987B+fHk3qw9Fk2D7vTs6Oh71/DU6OLhqds8lxfzeaLQS6u29kXx64tVrt025gH6FbVagVNsupAu3lIKm5DwVdSZbaUGnxDfifh31Aa6UfvqIM5FnNzNMSHtRUmcYeaBQRgzFstqfB5G5u5VthBu0rS3bc3FhR6mnWDrYk3+f4KwXnV9N4eDWvlfYE5yD/+nvZ793GgGcQZH4Y8FMt7JK2ru/oCTPCb6c2pK3rm9VNhX51fMVhBtIphg8HZ12neOn4dx5BkAanmEzILSxp61HOCp2zKF1LQEUx2FBhrUmUyYLA0AhazcuzqRbPrxiesARkiDXXmJeLTE7pzgjDm0fwBJgGnXu1DiNLxDtYPmgSZx/Gm2aOlw7SFjdXIUbMJHCyEDYkTJLuqH54RBIt5swCuYWlu6mB7SJfMk4sICg8BMbxPWCTl4HKrClefQmqOsJ4qTaQDcjDiFnsQLgrwJiBNrmVdffArWEM0jhmenkPmO2X8WLUGb5EEMCIVSoiXioim7m5PTwbnJ5jdgvES6NbkrAlSslOGZlphSNxQDT4IhHZB9wq5DNzoV2CXSh96z6KHf8/TMRtRbZJQJUSZ33pGJVqH3Cix9eYQyphClOy5UJSIsF74irZJgE/YOKXW5dApZJnjCH+B1cWCA01JMoIq7QA00I7HHJtcnnV4tfhW0FykiJIZeO8eVF2x5mwYeq5voqrPyThZStfo6xNWeJKwjIhc6BYjobolZCBZsbq1LepLhzEe7FP3an7A54FOquY/41rpYinfFuAR0ran/YmhCh2/JBpax41eYuuajVANWZCVouDR/15yo23EMUkE1Qs15JIrfddj7+1FPdq5Db1QEuwUOyfLOjYDIIR6LnwtwfvwkyEX9WMyFGBYwqyCo2ED9JkjaYsgAnzQyD1rE5t4FyrWl0sFi7LvmbSClZTPe+ddvujrlN3a25o4yirk9gNYia3BJc7oPVWbKfKbG3F/l7f/r2+/R+vbwtsYeGrrSYREzIbfPNdWA5ormkBaDZzdwlpbio0ROzTuqZ3dzgFXelotcLjP1LAJn99g7hJC+YhZLjGXUGBKDao6zTPfmecj4IlzML98KpSErV9HxK79fkBPt1BZMPBCBcuXrF2jhXPpjy2wJU0W2TIa7X6DxL6xLI=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Default Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/tenants/default-tenant"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Sets the tenant specified in the request body as the default one, resolving all the incoming API request to that tenant when the env `SINGLE_TENANT_MODE` is set to true. Once set, the default tenant can be overwritten but never unset, although it is only effective when `SINGLE_TENANT_MODE` is set to true.
-
-Default tenant is useful for development purposes or when the SDP is used by a single organization. This allows the organization to skip specifying the tenant in every request and simplifies the SDP setup operationally by removing the need of providing wildcard TLS certificates for multi-tenant configurations.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"required":["id"],"type":"object","properties":{"id":{"type":"string","description":"The tenant id."}},"example":{"id":"1736bed3-7b92-4760-8ff2-51fb08ee079f"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Default tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-a-disbursement.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-a-disbursement.api.mdx
deleted file mode 100644
index 8667279d57..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-a-disbursement.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: delete-a-disbursement
-title: "Deletes a Draft Disbursement"
-description: "Deletes a Disbursement in Draft or Ready Status by `id`."
-sidebar_label: "Deletes a Draft Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWW132rgS/is6+tJ2jw0mQEj5RgO5zd00yQJtT7ebQ4U1Bm1syZVksizH/33PyIaYQN76sufeL4mxZp550WhGM15Ry2aGdj/TvjDTTBtIQFpDrzzKwYRapFYoSbu0DzFYMISRKiERkvQ1iyxRmgyB8SUZWWYzQ6ZL8kXwLzXqUZWCZghzyjdAvSoK9WjKNEvAgkZdVlSyBGiXCk49KlB8yuyc3tXptE9UROwcyJcqnBOq4WsmNHDatToDjxq7jBHSiCSNgXoU/kpjxYF2IxYbJAjnkDDaXVG7TB2l1ULOaJ5fIZpJlTRgcP0gCPDfPv/wbe9wsEzEhno0VNKipd0VZWkai9A5pP6nQebVrnA1/RNC5xiN7rOiEC34roJ3vTKeA8mk+JoBERykFZEAvXYU33Y7/MWcO7r0sPGas6N2xz/qHLT9Vtg+8l83m9wPGwcBa7WPIIjaNPfKnXmKDkj5qNgtd50jdo7eDkEsQE80zISxRfBMEjCGzWBiIUljZp+oRZgZqxKyZiKZAU6sIgYkJ0IuhHXoBt+t5ZoaQdYvHCKWxfYLKUUTYeQLSzTYTEvgNXIqnXXl8gtDym0mwr4wJFXGiGkMCM04d6SRimN1I+TsVqMF04JNYzBdslrVLvSMSfG3Uwr9kefkZi7CORHGAVTXncNQZiRmmQZOmOSIMay47UzI67sYsZDXZAYSjyVwPKqj/uXGKVY5orUzyEshScgMEDsXBiGksiTVYMrzX/GAVxjOMqsSZkXI4nhJWJqC5KiddbQg+avaVhB8UhmZswUQRlK2dKFww4RFL0VKk6XKSKRVst89NXIci/D6HrvdruJb0LUitCoRhbvFQjspomg3mkBmCabGwbve6Rn16OXbi/PB5Pz9uzeDIfWK15PeeX/ysXd2NhhPev3+cDAa3aHcR3HlUSusM76q9HGh0Bj1yD16w+IY7LdmhVv/thlnr4G3/Va7zfxW5+jAZwGA3zgMOocdCDhMGw+d7VukD2KqmbSkZ4wwFnnmKoGUzR7hm1ubmm69vij4WZrWQpUgv4F00ggmYSxA2glXCRPyYSyWCp/DoraLxQHSCQb35L5k/rhOdcNThEe8UAMekAmz+5AipRNcoZxZ8K1IYAv+IDho+kHHbzbGB0G3HXRb7dph6+h3BM5S/jOA89uo+liETu5RZsyPiKEoYhC2pk2/dTgN/BaftnzWClv+YdhsB0dBu9MJXH0IXU19LDP3UCniaKtC3o/6xwgijMlAPxWmoMYUq8GYLcD/vHnTb3VOTw7PPv7auey86w8+jI4/Djv9y/cfPzTPPzX7498GH07OWue9cav329vm72dnJ2e99g/a/QM/aI4buEPdduNH7fwuKC/uHt8DeliCtkvQfF8tHVmIY6aJCymyCaR1zLndcGfaXQEfyqj9Ye9kTD06HPT6n6hHR+PecDzoY+bsvR+5h+OLd5dnA3xZSZbV60Jx0UR5C9AiKq9Uk0hAvD+W17J748Hk4mTy5nQ4fks9+mnQG07eXZy7H5en59Sj573x6cV572xy2l+n+4oSHyriTpy0jc2TuTBW6WVFPtOaLfEaayExj5/DzICePHYYm1Gz3Zi+Bh94EPmtIGI+azZafqPVaXemrQPOioT+b28EBpexLEl/WHDnD4l8Wzh7IK1e0qdQIlEkYpg8XumqN1Y/gqkfNH1UsRaaH1Ub/qXsYJVl8aS8WFWDQUgLM9C712ZkIDJLpkXfsGGtSGsEO8gTUzY4z4Q3WRiCMVEW75V0tCsoYiIG/g2iCsb9Bu2K0YCXEfT98yVteO8VxhKV4Y2njLMnNnZORVLwbroqTowiEdNb4XAUBLUguA2AgucbpFhFprcdHN8S0gg2UtgCNLZnz5FT8qwlpaDX7rorxQm554jTPMel1r62/A3jZAhfMzDWI8dMYu9SlEvCtrpSYufMkjkzxFimrbOz0rT/Uv/lOX06aK2ecH/pF/MBwqYqK5sjx5ij9Vazx+uFs3zjqY1geioXLBbY4aZZ4cw1nKuPk0gpvNStn7Gt20xMvPL9lOkNzZRpIgG4KcOBSbI+Cnm+9n9j1//vJcvsXGnx98/x6NM9tVsMi9OKEGX7um/4c49/z5UlW5bdarGW0woaFeS7HAXyvlnQz5Lmtqi5u0UnSk8F5yB/yv7sd9+tzOe4YYvLmdPaNQctP1GZ/H8Nt2eGRVSaui8iWtWIGIJRmQ7BjW8KrrU4A2GmhV260esbYBp0L7Nz2v18hcPPBOxc4ei2SJxuWourtF5NoKa+EjyniKYX6zlupmPapRRR1kJGuAOFi6qibu/LqfgVljup8r8fx8XsDidCGNk42Sxc5BEjZhI4uRF2jplpMDpoH5JUiwXO165hieOmcqTcKw+F41xPl+fAuMtk+DtSTpuy0Kx7nq1B5WXMLN7GSO/ylLr+wxRaHtQatQB9kCUJwzZgq2/aj/Fy1L98hQmYEatUTKaZiK0zU1WGXS7xJuwayDSLrze3CjdbJDOtsrS4doQiFW5B4ezOVqRLsDdKX9f2VuL/LRX/kH/IcTltZJKoFKRfRm+qFR63olwLU6qiJLEqXU+b78B5bi6KCzhwICGTWMHcEXCMW2NZDakywiotwHRRD598NgVevfzvb/UGaekkf8rCa5D86uV6sDQTdp5Ni6HScxBedYkzfqPK0s2VmZDF+LYkc1YJGWlmrM5Cm+nSQNwX+9ie1p5hWaRdHv0e09YQj9l2A1Oypv1ma+YQJ344Z9qaB1Wu0NWtBqjjnb1evnjQnsfMeAtxQhyQ059DGqulm/o/etYyg3TX2RS0xC9utT8wTVnQibmIRqAXIqxOL0s1a0rP6o7IV5FvSjKPxiIEaVzVWCfAlIVzIAcuTxX5GbG69frNzU2NuVWHVrKa+tnp8eB8NPAPakFtbpPY5clUGZswWQGufCF0XwTvfOHbyjmr29L8PV8Wy5Jh4S9bT2OcHOelTauyRn3eauSxCesKjoOMuTIWl1erKTPwXsd5jq+/ZoBp+/OVR9ffZVwh48LgM998LrzXnJfD8h79ijz0fXKv6usSKLH+LVic4S/q0WtYFl9D8yscuRfVCtUqFnphCKmtsOzcH7bKeH+A4xzqUbZTea9d5S0fUMBeje7W0EIL/Jt797CsVkVdz/MNfbF0L0dp5cZ4NCLP838AieCGsQ==
-sidebar_class_name: "delete api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Deletes a Draft Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/disbursements/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Deletes a Disbursement in Draft or Ready Status by `id`.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Deleted Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"400":{"description":"Bad Request, Cannot delete a disbursement that has started","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-api-key.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-api-key.api.mdx
deleted file mode 100644
index da2a2a2cad..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-api-key.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: delete-api-key
-title: "Delete API Key"
-description: "Permanently deletes an API key. This action cannot be undone. Once deleted, the API key will no longer be able to authenticate API requests."
-sidebar_label: "Delete API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVV01z2zYQ/SsYnOKMRDqu24Nubq1O3WYST+RMD44PILkSEYEACoBWFQ7/e3dB0JZsxR63k5n0YpHcr7eLxdt1x4NYeT675meXF+wP2Hp+M+EV+NJJG6TRfMYvwTVCgw5qyypQEMAzoRkZrGGbsata4oeStFkptDaBFcBaXRkNGXuvS0hm1YSFGkZDtpFKMW2YMnoFjmxEoYAFw0SLejrIUoRB3cFfLfjgMz7hxoITFOyiQnDn0TPqIHYUWuFEgx8c5dRxjS+oJCsUScrFilDzhwle1QRXYggmK4q7lIjHLPfQIqwhCzQnONIBxg+uhQn3ZQ2N4LOOh62lgD44qVe8729I2VujPXiSnxyf0s9+/DFEqhLzbVmC98tWqS3vJ/z0+M1jo4+aqmSc/AKUXWl0QOik9zp/TT+PQJniM5SBiuSohkEOkMA54w5gn3D4Ozjhn/fggwjtrp5umwIcuWgwD7GCQ6XpYwTRWAU7MPg7bJ+9zO5RjHGwHjueH1oMnoW1ivoHi5V/9lSx7ptFi0f0w+Mj+tW4QlbYUd/kfA6X7z7mS8qwZxXTeaJN6YIvDd7v/2nbvbA9xlQPdcbpbmd8AG9ah2x3X6AxnIeydTJsIyn9DMKBO8MewtcboghkrNoQm90xTOSpGc+FlVOsuc87WfWcHLnbkdxap1CFk4PR/4KKP1RnN8pdFdDdwJP7J/v7n1es9cg8S+N2yRelE+blSqNoI0NNtD9fnPz4E7NO3hI50wBAd4lnz9K9iJYj5dYgKjqVnt6XJqKRgerMFwGUEo6dS1+0ziN0HdilEgFxNMS86IPSHVCeZG+yY6pB2zTCbRNxP+3j1eL88ojRfEICN4oVrVQhpmncSugE1RO7N2INKFdrZsWWvMSvgq2caS1NAweltDIKDKKK02GMriFsjFtnB2fL9wXxk/6k48iWcYzjjdLT1Lh4v+imoZkIJB6g4FgPxo7z8IG7CfqooqA0FdD8p0Eeuz8a1vSilNng7UN41ngZsEXAzwjHlF37wV+efqfVTpGmNhVpWohyDbq6eVWHYP0sz1fYjm2RlabJX+ThaDbsK3dQtow4TEiqMIJNajErbFe88Tjiy9C6lCCdS3juTLMXZLZ0kUL/S2qji+dy20DBRt1/nU0NqpmWtXDBPwl5Ry8PDiBvEEeePjyZz3Np/IaeWXQU8VdgldlSez2bCZIc6a1bHBOa9lhMDW8srouNf79cILfKknhpTCvBzPAi5lFpapZTn9QmHCcI4GJHjDYSoBXIwOwk8tTAz+QLXW02m0xEafSWTH3+9uKX+bvFfIomWR0aFXkS8w64cu84HtZclpb0hyzT3c/h721bT4Mn4PTM8YBxIvSpMl0actd8HHKoPsNVHedZjQUgSdcVwsNHp/qePqNb4v1rfLwVThKAOAmxjegZJ+hSKA9PVOfVh7S6H7EXb/0HUxkHq6ZDuRWqpTd8ROPhH4/+BrXSDCSsg+AMN3wbdkxoe9pbBc7nb+dXc9QQj0b4OnZAeiCfB0E8HMZDYPrbT75i0nXDgtD3d/qD6KsWKbG7fDXl2/f/AEi6BQA=
-sidebar_class_name: "delete api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Permanently deletes an API key. This action cannot be undone. Once deleted, the API key will no longer be able to authenticate API requests.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"The unique identifier of the API key to delete","required":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"204":{"description":"API key deleted successfully"},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"API key not found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-asset.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-asset.api.mdx
deleted file mode 100644
index 0d62204e5e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/delete-asset.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: delete-asset
-title: "Delete Asset"
-description: "This endpoint is used to soft delete an asset."
-sidebar_label: "Delete Asset"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVsFu4zYQ/RViTgkgW6mx7UG3dGOgaRfdoE7Rg+MDLY0s1hTJJUf2qoL+fTGU5HqTTYJsL71YljjzZt5wOI8dkNwFyNbw0e+kUf9IUtbAJoECQ+6Vi68Z3FcqCDSFs8qQUEE0AQtBVgRbkihQI6GQRsgQkOaQgHXoI9ZtARncRINrXoQEnPSyRkLPgTswskbIQBWQgOJgTlIFjzO4vRG2FFThEINjD2EhAY+fGuWxgIx8gwkEajVDBlU7zQb42WlbIGSl1IEN8gprCVkH1LpoSV6ZHfT9htGCsyZg4PXF1RU/vs4lEhnDFyI0eY4hlI3WLSSQW0NoCLKu7xNYXL17zl9qj7JoJ5wnru+edzWWRGkb89ipTyBg3nhFbSztzyg9+uuGKsjWGyZXI1WWt+RUvFjtDNJY1pB2quiBYfxh2qDGa8gA2H1CX3EBhwqdxzjVUzr1G7ZPNvHXv+6HzimtF7KhCg2pPPZJIoLaGSzEUVHFrbRcLX78STivDpJQ7LHlthp7haNZP3Xr2DYVygI9cBGUKW3MRlFshBWh1tKLGxW2jQ9YoyFxpyWV1tfi+u4WEmC6Q5aL+Q/zK65BU9fSt7H9UbyMcbG6ubvkgyEFWavFtlGaIk17drACt20t9yi2jd4LJ1tGiV+l2HnbOG5yj7lyKi7YA/rY9FN0g3S0fj9/Utr/X4oP5sHEucEhjbAOzSzYxuconLd/Y06CKhmnyZCKNYKsm475I7hESFPEhdwWKHJpxBaHQxAdK37R2h6V2QmPzgZF1isMGecxE+sw4KXjc1acFWnmxiLNtjLfoyk2FxWRC1ma7hRVzXae2zp9E8JlJiL5Uyqt4JMqFVe4QjGaRVbKlF4G8k1OjR8J8r7Qa3s6fwOz0sdB8V+oTRCvcTviVky2382mQl3P8kp6Ci+mfGaXkkdMa6lMOn54kc9rNH5BXYsIFPMv0Gnbcnu9ykQ0ge32zRa9QcIwf+AxRejr8LFcoT+onOfSRGtMc279Lo1GM1vOwmiWgFY5moA80aYB6GReoVjEOTXMZ8bK0vR4PM5lXI1oo2tIP9y+X/6+Ws4W86t5RbWOc9LZQLU0Z8CDUotJqr+aMd2/WvP2C8EoDISfKXVaKgP9mHk3StAaBgmCBDJV8B2ksoH4e9dtZcA/ve57/vypQZ7K600CB+mV3PKMX3dQqMD/i5PMP5v9xR/jjeFSvHSv+GbOk8IZlreD1A2/QQJ7bIdbTL/pz3T2Zvlheb+EBOQThdxHhRz/MIFvQj/WuiEO//bJMy5dN+hv35/sh6VnPUbtPLEwzKLvvwCSVJKU
-sidebar_class_name: "delete api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete Asset"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/assets/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to soft delete an asset.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the asset to delete","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Asset deleted successfully","content":{}},"204":{"description":"Asset already deleted","content":{}},"404":{"description":"Asset not found","content":{}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/disbursements.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/disbursements.tag.mdx
deleted file mode 100644
index badcdef409..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/disbursements.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: disbursements
-title: "Disbursements"
-description: "Disbursements"
-custom_edit_url: null
----
-
-
-
-Endpoints related to disbursements. A disbursement is a group of payments sent to multiple individuals at once. An SDP user with the appropriate role triggers a new disbursement through the SDP dashboard by uploading a list of receivers and amounts. When the receiver has linked their wallet to the SDP, the payment automatically begins. SDP users can track their disbursements in real-time through the SDP dashboard. Each disbursement must have a unique name defined by the organization.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/download-disbursement-instructions.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/download-disbursement-instructions.api.mdx
deleted file mode 100644
index f14cbb8526..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/download-disbursement-instructions.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: download-disbursement-instructions
-title: "Download Disbursement Instructions"
-description: "Allows an SDP user to download the raw CSV file that was uploaded when creating the disbursement. This will only return results after instructions have been attached to a draft disbursement."
-sidebar_label: "Download Disbursement Instructions"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVV0tz2zYQ/isYnJIMJTqu2wNvTuy0bjupJ3Lag6PpLMmliAgEGGApRdXov3cWfJiSX3XTzDQXUUPu6/uw2MdWEiy8TK7lmfJp4zxWaMjLeSRz9JlTNSlrZCJPtbZrL8CI2dmlaDw6QVbkdm20hVxQicLBWrye/S4KpVFQCSTW4EVTswDmYl2iEZlDIGUWQSEfuZyKq1J5sVZaC2v0Rjikxhnh0DeavICC0AllPLkm45i8KGGFIkU0AoggKzHnkEDkDgraNy4jaWt0wIoXuUzkWRf4GPXFyLiMZA0OKiR0TM9WGqhQJlLlMpKKGamBSnlI08WZsEUAN7YsI+nwU6Mc5jIh12AkPW002/OqqjXKSOLnWtscZVKA9iyQlViBTLaSNnWQJKfMQu52c7bma2s8ev5+fHTEj/1Axu6HU5GRLBHyAGkrX1tDaGhypnxtvWoVD+1clRhUGX4PrT0azAe7zO8XAIqGUK7Cl8MYCD9TnPnVl3nZRTJr3YSvvc1kK/EzBGuJbMVO7iL0FeSCDxE9RUKZFWg1vBCjXNnz8iJ+wY9bQdn0I2acFrXjvCTVniQ6Z93t2A+T7AwJlPYCUttQOJFWccd0kAP/qKcAc4A9OJYXHS5l6obk2FyhUOd/FtbK5Oa/UF4MiR1171Nwg0wKThjE3PPNTJHLhzKEC3TMdEf2y9tkvzfQUGmd+isY/s8Z/edMSU9AzVjONFWKgewKvYcF3plsd/P71pLYQ3YTRe/n5OjlyPKhRmsZ6lqrLFSz+KNvr+3X8haO6LvbR/TGulTlOZqvcj5303fj8yk07GkFOCeP1Eum4Y1tzLeae0/MkaKDeld6nIzT4x1627gMhRm0ences8Yp2oRe+QrBoTttqJTJ9ZwbVoVUWm68CwwwuXcmMh43aR9vVb6L1X4X9uhWfQtunA41en7jbsZn0ZI1djqQArX6BTe3KujPf1zxDJOLwrqQ8GioIysSXi24ua0VlVywzmfH3/8gaqdWQCiWuOFu100Dp91dCZr9YNC22JDDyhQ2RKMo9JcZodbg9oYDcamBCusqcXp5ISPJcNsoj6cvp0fMQVNV4DZdN37YxrPZ2eVzrssgyFot0kZpCjCtW4DpQg31uIIlirTRS1HDJpxAOz8tnG1q7vUOM1Wr8MGueOAbeTdIa+uW01vU/v9C/GA+mDBcqjC/2hrNpMvj2lm+eO20qnwXijWCbN1POwfmIgGmnXczm6PIwHBjC5chKPK8ZHlY5inXYZisrFPoE45jIq59ay/unpPxHZjUHUmTFLIlmnz+rCSqfRLHC0Vlk04zW8VPsvA8aSfrIZSN4JIGihkuUXRiAZUyhYP2+jWuA8jnQo+d6fQJyAoXKuqXQOtNPIZtjanoZf81mhJ1NclKcOQfDHkkF5NDjCtQJu5ePIjnMRg/oa5EMBTiz7HWdtMvUQ/ftcaz3LJJ0Rkk9NMPXKYIXeV/K2boVirjutTD6sKcWreIg9DEFhPfiUVSqwyND/2jL4A1L17iONSptj6zrSSO1+v1FMLXYK1T9fGvF6/P387OJ8fTo2lJlQ51sraeKjAjw/2Cto/rYEXbqzzbm1b97W+rXfsKW0qtQRnu+YHfbdc8r+Ve85SRTLrddETRPJKl9cTS220KHt87vdvx608Ncke5nkdyBU5Byv3pestG+X8+LFT3cvzsXTf5Pxf3br13wuhbs+G+vALdhM0rkkvctAv2br7rF9UQU/vhNMuwppHKsMLtDRg/nl/JSMKtMWAZxoDuD1u9M4zDht665t9ddI/KdtsOGbvdIN9+ulejgzYgNox4t/sbFvwyRw==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Download Disbursement Instructions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}/instructions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows an SDP user to download the raw CSV file that was uploaded when creating the disbursement. This will only return results after instructions have been attached to a draft disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Disbursement CSV file","headers":{"Content-Disposition":{"description":"The filename of the returned CSV file.","style":"simple","explode":false,"schema":{"type":"string"}},"Content-Type":{"description":"text/csv","style":"simple","explode":false,"schema":{"type":"string"}}},"content":{"text/csv":{"example":""}}},"400":{"description":"Bad request, invalid request parameters","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Disbursement Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-disbursements.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-disbursements.api.mdx
deleted file mode 100644
index e4b329c3ed..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-disbursements.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: export-disbursements
-title: "Export Disbursements"
-description: "Exports a CSV file of disbursements."
-sidebar_label: "Export Disbursements"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWNty2zYQ/RUMnpIMJcpumge+qZHcpk0aT+S043E0GZBciohIgFks7aga/ntnQUqmfJEvcWbyYpHEYvecXWAvXktSCyejMzn9VlkkJ+eBTMElqCvS1shosyCUeD37R2S6AGEzkWoX1+igBENuKANpK0DFW96kMpLgN036QjKQlUJVAgGyxbU0qgQZya8ykJotfa0BV/Kq/bFwoDDJBQGWonaQCrLCywrK0daLXFAOO4gEq/awEL7WGiGVUaYKB4F0tCrYamaxlAEDLWwKMiKseTXJoVQyWktaVSzmCLVZyKYJtngdKardftDTbyohUSpKcmGNx9duY99dRfuEOAMJpi45npMP46MTGcgP0/HkVAZydjL+cDKdyEAejz/O/MPr9++O30754zyQpMnb68ds1jJt2Lwqq3bd6+25I0FQBOlnRZ9VRoD7HfPeFCuBQDWa3TMkKFckFILoFAqvTVCunUgVwVAcWSwVReL09PR08O7dYDJ5wgD3OR6ORq8Go4PB6PAWojFkFuHJmLbqfiKqziLtZ3ekoUi3t5Hld0k+5ZFOIVN1QTsh6J10jznor8371zXVCIlHvZfQZCMmMouekDaL62nuB5BSLumxad8YG9OYs0VXWePAsZbD0Yh/dqHfmpfZK9YQGPII4BuFiTvn59txZf7kyUjG2ihcyaZpmkC+HB1ct/vRqJpyi/o/SHdNvQhf3GjFxl8g4dhVyPWCdMsKEC3eclAJlbtbQ5eTL+VMXcaArKIE59QCbsrpTf8qbGHIvy2JHWaXKDZ2Xo4Oepqv7mg1q6oqdOJrYvjFscfWP8yaD9Ev10N0ZDHWaQrmh8TnZvdd2nyIG3Z28T4HSY2aVr5V+A0UAo5rymV0NudrUQLllluNBXjAipdk2DYeLrx6Dxzg+abvqLGQkZSsZWNkxp5oyfZNbRmrSv8F15PGn/+etDmQcwaHBAx1XAPh9MJAKi405UIZMZ0d/vpKVKjPFYFYworTSZejxl00VT9P5aBSPsINv2fWo+mK9IygKBSKfrEWx4Uivr1ifPxGBpLptigPhwfDEfugLku+0pE8yUHs1/FsNjl+LjS3fWRtIeJaF+RpWlwo00F1nPxLtQQR18VSVGrVVTgrlFigrSvOSQiJrrRfsOe+pF9aN0AXFpfDa679+SB+Mp/MCZdoNmmErcAMnK0xAVGh5YvTVnbtOijc+Nlq0/FdURcIZVK/kNgURKKMiEFktjbppmPMbFHYCy5DCJV1mixqcBHjGIgz1+oLu99B/8QPqs5Jg1glSzDp/FlOVLkoDBea8joeJrYMH6TheSQ8+S2UleCEojR7OAfRiXlW2mSoHGGdUI0dQY4L3RXT4QOYZejz2fdQ26i4i9sFxGIj+2g2ORTlIMkVktsLuScXEgKEpdIm7D7s5XMXjT+gKIVX5PGnUBV2xcfrTiaidiy3rGNAAwRu+InTFE9k7n02AzzXCeelDa0O5tDiIvRCA5sNXCcWyEInYJxP/5sEWKkkB3Ho81Sbn1lXFIYXFxdD5Ve9tm6rC9++eT39ezYdHA5Hw5zKwufJyjoqlekpbqdXcXUS3ck168vSeN9ptysLvqWqCqUNdxoe97orRWfdDOyt7VifBzK3jlhkvY6Vg49YNA1/bjtTLlGpdiouem3mrYC/bzy+kccSVt1Yfq6KGnytDB6C6cHT7x4Y22n7kViefODcg/WGUfjHo77n8Hg/2NvB9pG47zEW7ot1O3Y+0vY9J7g99vuj4iWIOb+gZhS++Qw2nRlf1HbjOEmg6kPfzlo7rervU/6PjLrWWi59a9k9sNbNkln1dF5tElvT/Jf9dOOW9bptXJtmK98u3bqjo7aRZu/Mm6b5H3hhCE8=
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Disbursements"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of disbursements.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"q","in":"query","description":"A search term used to query through the disbursement names.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the disbursement.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return disbursements that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return disbursements that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort disbursements","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["name","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting disbursements.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"CSV file of disbursements","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-payments-csv.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-payments-csv.api.mdx
deleted file mode 100644
index f349a4269e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-payments-csv.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: export-payments-csv
-title: "Export Payments"
-description: "Exports a CSV file of payments."
-sidebar_label: "Export Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWG1v2zYQ/isEP7WFZDle6m7+5sVOl61NgzrpEKRGQUkni7VEqkcqqWvovw9HyY7cOM7LEqBfYkl3vHueI3kvWXIrZoYPLvj4e6HRGj71eAwmQllYqRUfrARMsIPJJ5bIDJhOWCEWOShrOtzjugAUpH0U8wEHp3/SyA8mn7jHC4EiBwtIrpZciRz4gBsrbGm4xyX5+VYCLvhN7yKyLBc2SplWzKbA6mUEgt4aIIQD4VspEWI+SERmwOPGLjJylGjMuUfIMh0DH1gsSRqlkAs+WHK7KGo8KNXsBoTT23ySSVXmFL3Rx+HhKff4x/FwdM49fjI+Hh0dv6Wn4dlkPOIen5wdHIwnE+7xw+HRO/fpYHh8MKbHqcettA5rE7hJHZuKUIu8cKLaSeWtA4gQgbwE/CLj3VE8OzsaMZsKyxAKBEM7wwRbrWeyjmwsrAiFgaeL5Qb+sB/2+29E7PejqOfv96PE/yOEN/7r/l4sRARv4v3f2/QiBGEh/iLsF5FYwN0cP6hswRBsiWp9OmvOAoE1tpgzxGwqDbGFDjvUmAs7YOfn5+f++/f+aPRM7Hvdbt/v7vnd3i0cQ0g0wlOQrC39QiyNRrub2KGELGalgZhZzUh/I8U84dVORJnZjci37nHr47RqEYglQuSg7mQxWqmxRKNjIdXsuYkIE7UY1G8EixhMyaMptDJgyEqv26WfTdTb8jr3eKSVpSxHzuG7DSJzSc+3Q0rcIaOLLpXABa+qqvL4fnfvpsszJUqbapQ/IN509Sp4tdWLDr9CRFtVINUbK2tCgKjxljNpUZi7LTRV6FpPlXkISCZyMEbMYIt5x2x96tcw+LG2bIPZNYqVn/3uXsvyzytqy6IoMhm5mhp8NRSx5bN5c1v0280tOtQYyjgG9Sz7sz181z4fEoaNVbTOQFSitAvXbPwJAgGHpU354GJKNyIHm2pqVWbgAAsS8aBuXEzQugIG8HLVtJSY8QHnZGBlf0JBqHm2vazJikL+AzezxN//ntaZjpIE7QYo29D0mJEzBTG7kjZlQrHxpPe6zwqUl8ICm8OCkkiTlIbNRop2YkpBxHR6K3pPtEPTtBYTC1kmkI2kCUs0QCzZSSYsXVw2PDniHie6NcpeZ6/TpRiUeU63uW6Edtt4MRmdvGSSegurdcbCUmbW0dQ4E6qBaijF52IOLCyzeauOaSbYDHVZUCZCiGQhnUBfupp97V2BvdI472zt1X4tiJ/VZ3VKhZhcKqYLUL7RJUbACtR0Z+r6LU0DhbpcXaxazZ/MeUyo2AkiHQOLhGIhsESXKl61x4nOMn1FdQeh0EZajRLMgHD47MLU9oLm149bQfKLJkh+KKI5qHj6IrW2MIMgmEmblmEn0nnwIAsvB8yRX0NZMMolQlKEU2CNmmMlVYLCWCwjW2JDkPbF3rWnnQcwS9Clsv9DbWXiLm5XELKV7qPZpJDlfpQKtGYn5JZeYBEgyIVUQfNhJ5+7aPwFWc6cIYc/hiLTCzpedzJhpSG9eRkCKrBgOp8pTVnA3HxIJoCXMqK8tKLVwOxonAVOydeJbxo1j2cyAmVc5l8lwEJEKbCey1N1fiZbgyC4urrqCCd11pqlJnh3dDA+noz9XqfbSW2euTxZaGNzoVqG65mXnVxXgo00s7wuiPcYj5ti4HqoIhNSUWvh0C6b2nPRDM3GVaPG59TjqTaWpMslTWVnmFUVfa57T6pJsTQizFrd5A6Y95+jtwKew6I9sl+KrARXD72HwHj4ILoDzOb4+0hETzk27sC6ZZZ9VsD3HAHvh3g9mT4S8h3D3a7zVg+Oj/R79zi2w3V75Lv2P6UXlATAtZPequGi61gvHEYRFG3U6+lpo/l8O6Z/GIkbHePcdYzNA1ldidSiZfPn3q92TX8pRFuXLJd1P1pVa/1adOuKhtpKm6IzrarqPxK+AXI=
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of payments.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"status","in":"query","description":"Exact match on the status of the payment.","required":false,"style":"form","explode":true,"schema":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"example":"DRAFT"},{"name":"receiver_id","in":"query","description":"UUID that represents a receiver in the database","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"b6b667ad-6cc2-46cf-9be7-561daace7d48"},{"name":"created_at_after","in":"query","description":"Only return payments that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return payments that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"CSV file of payments","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-receivers-csv.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-receivers-csv.api.mdx
deleted file mode 100644
index bb5d9e34e4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/export-receivers-csv.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: export-receivers-csv
-title: "Export Receivers"
-description: "Exports a CSV file of receivers."
-sidebar_label: "Export Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWNtu2zgQ/RWCT20hW0622we9eWsnm912W8RpiyA1CkoaWawlUiVHdr2G/n0xlGTLieNcNgH6ElnicOacGXIuWXMUM8uDKz7+WWiDlk89HoONjCxQasWDdoEJ9nbymSUyA6YTZiACuQBj+9zjugAjSPws5gEHt+G8FXg7+cw9XggjckAwZGzNlciBB/wH97gkIz9KMCt+3fSQWRAmShmCyVlpIWaomZNlmBpdzlKGKWzAsCLVCr6pMg/BeAxyITOPCRWzsxHhNPCjlAZiHiQis+Bxi6uMcCTa5Nwj5JmOgQdoSlqNUsgFD9YcVwWJWTRSzXhVeRsGFgWW9jCN8U8RIcsFRinTyiGut5Ejd/AvRZYBPiFUj4Mqc4rv6Hx4csE9fj4eji7d8/RscjE+H4+4x0/eDU9PxyMKPkp0djbx++IwTWqeFVkWeeFEapUdZ0QGBEL8TeA3kSCYw275oLIVM4ClUdvjxDAVyIQB1ihjThPDVFoWC4Q+O9EmFxiwy8vLy977973R6AlD2+V3PBi86Q2OeoPjW0iGkGgDT8KyVvUL0bTa4GFmJxKyeHMrSX5L8ClPcAyJKDPccX3nYHc+Trs3M5YGIgf1IItRK8YSbRwLqWa76e0ZmAgbdSjUb4SLKEzJoi20smBJy/FgQI9d2HtzMfd4pBWCQmcdfqIf2QX9vh1T4o4ZD3golTArXlVV5fHXg6ObNj8pUWKqjfwX4l1Tr/xXe63o8DtEFKzCUI1AWTMCY7S55VSiEfZuDU3a3crVOZ9U5GCtmMG+tF11z/0GBv9HI9thtkXR2nk9OOpovr6j1iyKIpORq4P+d0seWz+bNRei326G6ESbUMYxqGeJz373bW0+xA07u2ifhag0EleuP/gDhAEzLDHlwdWUrkQOmGpqL2bgAAta4n7dbFi/ewcsmEXbaJQm4wHnpKE1MCEv1ES7ZjZsRSH/hpuJ4q8vF3WyozxB4QCFDU+PWTlTELOlxJQJxcaT49/fsMLIhUBgc1hRGmny0rCJpOjmphRETMe3ovdEOzRNIZ4gZJkwbCRtWBoLOShkHzOBdHPZ8OMZ9zjRrVEe94/6A/JBmed0nQN+kQI7rOPFZPTxJZPU4qHWGQtLmaGjqc1MqAaqpSyfizmwsMzmrBAr0uK+CjYzuiyaXCQL6Rb0wtXtrXUFuNRm3r/h2l8P4lf1VV1QLSaTiukCVM/q0kTACqPp0tQlXNoGCvV1umgbumvq6h6UFiIdA4uEYiGwRJcqbhvCRGeZXtalp9BWojYSbEA4euzK1vr85tmLO07qFY2TeqGI5qDi6YsUsbCB788kpmXYj3TuP0jDy4A58hsoK0bJREjycAqsEXOspEqMsGjKCEvTEKS44F0x7T+AWWJcLvs/1FoVd3FbQsha2UezSSHLe1EqDNqDkDtyPhoAPxdS+c2Hg3zuovEnZDlzihz+GIpMr+h43cmElZbk5mUIRgGC7X+lNEUjmP2QTMAsZER5qaXVwOxrM/OdUE8nPduIeTyTESjrUn+bAAsRpcCOXZ6q8zPpCnx/uVz2hVt12pqt1n939nb8z2TcO+4P+inmmcuThbaYC9VRXE+q7LxTCnbyzHpbEu8z1TblwLVRRSakou7C4V035eeqmXXrdre1OvV4qi3S8nodCgufTFZV9LnuQKksxdKKMOu0lLcCfeoZeC+rOayaaXwhshJcxfQegvIxI+4BJJup+pFwnnS0PIBzz8D7vIjvOSbeD/JmfH0k5jsGwEPxrYfLR9q9x8h2wHZ3LtwCmNKLkYTAdZxe25LRba03DqMIii7szYC105+ejunfLOJGTzl3PWXzg7S2S2rV0Xm9O6xN01/y0d4t63XdsVbVRr5eunVHQ62VJu9Mq6r6D9uw+Rc=
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of receivers.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"q","in":"query","description":"A search term used to query through the receiver phone_number, email, and ID.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the receiver wallet.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return receivers that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return receivers that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort receivers","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting receivers.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"CSV file of receivers","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/forgot-password.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/forgot-password.api.mdx
deleted file mode 100644
index 7708ea7ab1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/forgot-password.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: forgot-password
-title: "Forgot Password"
-description: "Sends an email with a token to an SDP user who has gone through the Forgot Password process."
-sidebar_label: "Forgot Password"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVk1v4zYQ/SsET7sLyUqDtgfd8lVs+rXG2kUPTrAYSWOJtURyh6M4XsP/vRhKTlyniLEtClQXSeTwcd4M5w23mqEOOl/oi54btGxKYOOsvk90haEk4+Nvrmdoq6DAKuzAtGptuFGg2K3QKnYyMbueqj4gqXXjVANB1c6i4oZcXzeKG1Q/OKodqymEsHZUKU+uxBAmOtHOI8Wdbyud62U03NvpRBN+7jHwpas2Ot8euTbC+j3saKwqYNCJLp1ltCzr3mXv5BXKBjuQLzE1hJVEIBIT4rzxqHPtij+wZJ1oT+IdGwyyZDDLt3uzwGRsrY/jdRPD5JaRuIRFJ0KrA9b5iLETXiV4Lhv4FCN5GnYeA750pAivLqbzq/cX6gFaUw1p28mTHNBi6jEOBO9sGBicn52dDuKQ5oCWVehLSdOyb9vNV8SzwxCgxtMR3Ru+IC9U2HArQ78MRh9HInog+u3fUbmESn0czsAJd09kmsjR6ZRcI4Npg4LC9RzTPSzcJRofmSCc3ClSwUfofIsHG+tbG1OrjPW9LHqGWxpsq09L56RY9t/KBPWUgGQcL4CebAogZRGrIBVboBStsYw10nBwxI3HtHQV1mjTsYzSwlWb1EIn/sv34AjaYJwV6djqFW50/urKRD9A2z8h7O4T3SE3Tordu5gnD9zoXGdD7af+ufgD0gPSsFVPrc51BAhY9mR4M5N0Dhm7RCAkkbKDmIM3P+HmRdp+/H0udVnFYoK/qF+igqktVqPKWXUzO//ue+XJPACjWuFGJGsMiezmyHwZCjDRRsAbhCpGVf6XLnozHuQZY9sCqWsTip4CdlJi0xZY1EFdTG8lWEhh8PJ88s3kTGLQdx2QhHneoHod483sevpWDoPos2tV0ZuWI01HNdjR1XgIOlihKvp2pTxsBCWOgqrJ9V7Ui7A03sQJ94AUj/d+d4u8drSavBSp/52Ld/bOzhsT4pZWOY82Da6nEqUJSU0qboBlenDFSVfze/0+gksU2CpOyIlXJVippqXrbRUXNvLTtm5tbK0IvQuGHRkMufiRqkUY8LLxnVYHQUr9GKS0gHKFtrp/0zD7kGdZbbjpi0npuuyrEN7mKpJ/cmWjRBXBSIQbVKNZZGXskiAw9SX3NBKUvPCpnE6+gtmSoij/G2p7iFPc1liove0/ZtNg26VlA8ThVZcP7DImxKwDY7Nx4FU+p2i8x7ZTESj6X6Fv3UaO10kmqg9it+oLJIuMYXInMsVIXfiwnCE9mFJ0aU9rdHPiqM6iUeqWaRjNEt2aEqX/5tsnAfRQNqjOo04N+ixYeZat1+sJxNmINi4N2c+3Vze/zm7S88nZpOGujTopbaADewB8dF08lpntc2v/r2+nYydhfOTMt2CsNPdIdTv2rYU+7lv3iW6ks+ULvd0WEPA3anc7Gf7coyj54l66IhkopC8s7nfJvm0899SrgWE6Fweem6hcZHbJ3uiiLNHz8fRhi51+mM11MvReuXC5SswI1nK1hnXsqLvdnySKRJ4=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Forgot Password"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/forgot-password"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Sends an email with a token to an SDP user who has gone through the Forgot Password process.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Forgot password request data","content":{"*/*":{"schema":{"required":["email"],"type":"object","properties":{"email":{"type":"string","description":"Email of the user","format":"email"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Forgot password email sent successfully","content":{"*/*":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"}}}},"400":{"description":"Bad Request","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-assets.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-assets.api.mdx
deleted file mode 100644
index f6cf5ccf82..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-assets.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-assets
-title: "Get All Assets"
-description: "Fetches the list of available assets to populate the dropdown box in the New Disbursement flow. Note: the organization must hold a balance in a particular asset to use it in a disbursement."
-sidebar_label: "Get All Assets"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVV11z2jgU/SsaPW1nbOzwkez4jZYkzTabpgtpZpsyO7J9wSqypJWuoZThv+9INgQS2vRjO7PLA9jS1dE5V9I9YkWRTS1N7uhrM2WSf2LIlaTjgOZgM8O1f03oGWBWgCVYABHcIlETwuaMC5YKIMxaQEtQEa10JRiCD8yN0rlaSJKqj4RL33YFCzLgNq2MhRIkkolQixa5UgiJD1A7PEhZWSSFEjlhJGWCyQwcECOaGeRZJZipJ3dzVxYIx7o/35miRQOqNBgPeZHThJ4D9oXoe9Y0oAasVtKCpcmKtuPY/ezL79+L3gzKlESQ6GKZ1oJnHj76YN2AFbVZASVzT7jUQBPKjGFLGlCOUNqddpV+gAxpQLVxJJHXNHi+E2PRcDmlAYWPrNTCNU0mDLJu2gm7x2kcdvO0G7Ju1g2Ps04v/jXunZzEPbp2NHM4hPRAn8+hj92d5GY4eOFAuLUVmK+FqaMJy3MD1u4Bnj9/PuieXJwdX96+Ork++X1w+nb44vaPk8H1ze3bztWfncHozenbs8vuVX/U7b952Xl3eXl22a+VGGAI+V8MDxGZKFO6HpozhBB5ua+kHbc7YdwO487oKE66vaR39M6BVjr/90FzEPCDoMcNaK8BXT9M9agAMkQQ9ydgu5GQo0fyq0HX7hPQbnz0eFvfSFZhoQz/BPl3bOnPbF0wRh3YLGunEg37is1vkWG1GyerMgXjIEqwlk0PbOla5jaPWxr0SiHZk3nPYjNPNz7aQX444mcC10vTebw0Z8qkPM9B/vx1OazunsBXBHgdFrLKcFzS5G5FnwMzYPoVFjS5G6/HLg1YKFd9p+C5MddFo21BtWDmYKwfXRlBE0rdsA3q0Kmshexi39dXzV/B8lFJ+u125IwhJxNlfO5BYpPAgFg+lZCTBceCMElOh+3eMdGGz52DzWDpnEOy0h+mZtlqfwwod+AFsNxtS1ci5UR5Ns3h25zNPa+7Fgzd8Sf96wsaUCe3ZtluHbVil4OqLJlZPjjfhzF+GQ6unxFuCSOolCBpxQV6mbsW6l25ZDMgaSVmRLOlQ/GtjEyNqrRzNQMZ19x3qDkYb8Sb2SXgQplZ61Fq/3sU38v3clRw66eURGmQoVWVyYBoo9yhIFgw51ANFSUJKg9/AC4gTOa+wxkjyZgkKZCJqmTuBxbuRQi14HJKDGhlOSrDwSaOR0jubI0XNb/h7qUk1E2SwpRlM5D5+JcCUdskiqYciyptZaqMvgnhWUK8+C2VJXGVg3FZ39uaMK+Ky4lhFk2VYWUagW5d8Kk1bX2DsonxhetHpG0gntK2gJRsYr9bTQGiDLOCGbRfpLwTF6EBiErGZdQ0fFHPUzJegiiJB/L8c9BCLd32elIJqayLm1UpGAkItvXelSkEU9rXkyGYOc9cXdrIami2lJlGPihUk9A2YQEVPANpfb3fFEDNsgJI29epuj47rCSKFotFi/lej9YMtdHlxYvTq+Fp2G7FrQJL4eukVhZLJneAzwFJXwiyvY7vVZnVvfv97/+ENE6F8BEjLRiX/gbqUrlq7PCONnY4DmihLLqW1SplFm6MWK9d898VOIO4Gwd0zgx30r3DBhs3cv45A+ch/SwD7bx2zkRVe+SD28OeL5+fjmhA2SNbnXlbbR4c+qZLLnewHxpkTcF9r4PPDFmtatNer7fxdddnRzQSN9Eug+P1ev0PXdMlYQ==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Assets"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/assets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the list of available assets to populate the dropdown box in the New Disbursement flow. Note: the organization must hold a balance in a particular asset to use it in a disbursement.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of assets","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-roles.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-roles.api.mdx
deleted file mode 100644
index b2f213c225..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-roles.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-roles
-title: "Get All Roles"
-description: "Fetches available SDP roles, such as owner, financial controller, business user, and developer."
-sidebar_label: "Get All Roles"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVsFy2zYQ/ZWdPSUzlOi4aQ+8uY2TpukknsieHhRNByRXIiIQYBdLKapG/95ZiLLl2ImbNun0IorYxcN7C2IftihmEbGY4lUkjjjLsKZYse3EBo8FPiepGopgVsY6UzqCybML4OAoZhD7qgETIaw9cQZz642vrHFQBS8cnNPRso/WU4zQR301voaaVuRCRzzGDPVpdLWXNRb4guTMubeKjxkyxS74SBGLLZ6enOjjNr83rzBDXY68aNR0nbNVwsvfR03ZYqwaao3+k01HWGAo31MlmGHHurrY/QJJ1VGaYTYbzNAKtcfjUdj6Be52uwzpg2k7R0fTp3gtDzO8rsnvNzXBDA9FUf1aPJx9ZTCFe3ry5G7BrrzppQls/6T665WOmAPfUyLVJGziwwhRjPTHeb5vS2KFaClGs6B7d+B21QYa+DoI3JJ5w+KwztOTJ0fIH8/4lsD7rfnu7tY8D1zauib/7fflfnU3BP5GQtIRqerZygaL6RZ/JMPEZ700WExnu5mWQZqgx3pBiZvREObaCWLOwyGPxCvtPQrRs8MCUeceoCcqda/meIGbU9rZV6TH9HYxf/ntUjtODfPAaQPIy1DFDKJdeKphbaUB4+F8cvr9D9CxXRkhWNJG+5I3rcKfDXuXZmozUPCGTK3f5k7f5yGxsaK1womQc4bhmY1lz5Fa8gIXzsg8cAtnFy8xQ5W7Z3k6fjI+0Rr0bWt4gwVeNgSfx3g0eXbxGGwEAxKCg7K3TpLMwAvjB6oRJEBrlgRl75bQmY2ipFEDCw59B2EOTJXtbAqEFTHI0eqeZB14Ob5T2v8fxXf+nb9sbExLeggd+VEMPVcEHQc9GSCNEQ3vqQQPEhL8PXB7k9JAFWqCyngoCeah93Wa2OiLc2Ft/QKYuhCtBLYUC+Uxgmnc4+XDc1QfFWnUDUUalaZakq9njxqRLhZ5vrDS9OW4Cm3+RQiPC0jir6lskgEbqxVuCIa0pMr6OZso3FfS8yBQ90Ue2tPxFyibc+pe/0baAeIhbWsq4ZD7j9U05NpR1RiW+FnKR3m5MFHeGuvzYeCzeh6S8TO5FhJQ4l9T58JGP68HlYCa/wKWfUnsSSiO32mbEuI2vplPiFe20r50kDXQHAde5ClpFOajOKRl6GxFPqamf2iAnakagtPUp/b9WbGKPF+v12OTogltmBrzX1/+dP56cj46HZ+MG2ld6pNdiNIafwT8ggTOnIPDZe9Wk9neOOB/cAcdrETog+SdM9brtSNp3Q6mNcVkWnonTXRnGTYhiga229JEumK32+nwHz1pI5/OMlwZtso32WF2cA31uSVprz+rKurUGFfG9Xsv+8jqb5noi/NLzNDcsb9lsr/hj6IfQn5zhP2xke0p6O8u+8SU7XZvrrvddf4+9MkZg8RDthZSL6N/AR1/ZDM=
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Roles"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/users/roles"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches available SDP roles, such as owner, financial controller, business user, and developer.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"roles":{"type":"array","items":{"type":"string"}}},"example":{"roles":["developer","financial_controller","business","owner"]}},"example":{"roles":["developer","financial_controller","business","owner"]}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-tenants.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-tenants.api.mdx
deleted file mode 100644
index ce94658433..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-tenants.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-tenants
-title: "Get All Tenants"
-description: "Get All Tenants"
-sidebar_label: "Get All Tenants"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV21z2rgW/isazZ257VzbvCZ0+UaATaEJUN7abZplZfsYa2NLXuk4LJvhv9+RbQIEkrTde2f2E4l89JwXHT3P0QNFttS0eUNbfswFvbWoTEAx5FL0fNqkl4CtKJqCYAI1tagCnUihQdPmA62Wy+bHB+0pnpg9tElbJOIaiQxIouQ911wK8AnmCGTFMSQYAlfEkyLgyzR3ZrA9KRAEGkiWJBH3si+l37XBfaDaCyFm5i9cJ0CblCnF1tSiHCHWe+vS/R08pBZNlEkGeR4t9/dsNCoultSi8CeLk8gsVRq1cxf8mt1wf6ra9cZ52X4XBFX7rBK45XcA5cZPAd1YVLAYTiEdlmEaQpE0MRsc0kOiQ5lGPokZelkRSMIQQQny2683zP7Lvv3Pv35zDmJyoxQ8qRLj12UaFqmKvs33pDMiLvPuQPhEg7oH9W9NDASZja8OnYSIiW6WSltndrHP0X7iSLU0zrWfLFK++P4YZr2Sz3ToSqZ8cvFN/g/8IsNUnzw4kcamcafdQWswXbTH3da026HWdmE0Hs57k95wsL/Yak9780O7Tne3eLuxqM+NCzc1eSyY58lU4IL5vgJ9Mo4TaSNEEVOk2EyKzSTV4JNAKrJzIZYkSIWvDwty2f7c6tc+92vzD7X+z+9rH687Pw8nH66rg+vrLxeTYW3em553Z6OPnyadT9V+o35drY3Hkyv6XPh5zD8Su9nxauDFSXR6k+m4dzGb9oaDRavdHs4GU2cy7V5dtcZOdzCn1ssmnYvFvDW7mj5n1+6N21fdndmzp/V80xwnnNsaujIXch/usQbfmH7WRl1q0VF30OkNLhezSXe87bjecJDFy/XCh4ClEe6F50oZARNH8V3k6ySI2JJgyDIGWWmyCgFDUFnEBcdwncefYxOpiJDoZIiFt4BFGjYW9RQwBH/B8FSBAqli84X6DMFGHsNBZ1bL1bpdrtnVxrTSaFYrzbPKF9N1aeL/70F9iOB50BN0y2PQyOLEFEjsV2fFNHmjZYBvSQHq/GhYG6OBf6RcgW8O/ZEQDwr7Cou83LYv3WHLqNhBFxV6dMzQj9x5cDq3exnmkkjf1cu+x+pntl/xA7te93z7Xc2r2OdnXrlerZ151bNg66ZJFfiZIO3r0SODFx+PBOSEfjzds29bXN/TTH6qOBlnfpx3rkfD7qD2/n2/f16f16sfZtPhYPh50Gifz6ujyXzUuurO+41R75fhxfl1rdOfNwaH1WyiSuHwjpzqA6dcLn85LOwLdhuLIsesp/JB6nhF083GtFa9XDmeqGaCpRhKxf8C/wfGpGfGIVBKquOLtTENgop9w0B1RLMijV1QBiIGrdnyhObkae61YBEGHUgkB2nuotj6qZcre8hPd/w/gTNsDV6qOK5p8+aBXjDNvVaKIW3e3G5un9LRJSBpRRHZDc4xYCjNdVtCVklmttISPhrkQ5rO0PMbQg3u1uvEHGte9wtgClTufDcMJ/wDrI94sf9putMvkxQILDrGIpovzWyezeRMkO6kenZOEsXvGQK5g7Wzu/atoh7ZTnNnDHgIzDfnbXRNBDKLpmjr7RzR4dpNlYYYBJJRxNCQLmmNetSiJt08yqpTccqmBmkcM7V+Moucxngz6YzeGt1jBKWMiJvyCLM0pVoyUYSqCUoSszsgbhrdkYStDUq2yshSyTQx0q/A4wnPPsj7Qli33gXgSqo758Vx6Z8R4lfxVUxDrjOXgsgEhK1lqjwwbzFzh/MpgusiFCkIymQ7/DyBswgTfvbBkz4QjwniAglkKvxsY2j+iSK5MtOQgkRqjlJx0E0Th01udI5XKn5tf69IdlIUaasVt2+2grDkGKau48m49F0Ib5skS/4xlLV5YiLjIp+Ntq8hkxUXgWIaVephqooEzbnga2fqfEdmgcqY+u+ktoV4LbcVuGRr+8PZhBDFthcyhfrFkPfsSqgASjHjolQsvJjPa2m8hygmGVA+b0MSybVpr1czIak2dnepC0oAgna+GppCULEeBhNQ99zbf2sWYZqJo5QZ2TKwdWFm0Yh7IHSmI1sCTJgXAqlmPLWbYJql0mq1clj2NUMrturSVa/dHUy6dtUpOyHGUcaTidQYM7EHfCwVBzTzSPAIf2IpiRgX2cCdv8FzGbmhWxm5tWgoNZqlhwczbM1UtNmY5T9SMMR6c2vRe6Y4cw1N35gnScHiRnfuwHBvy/MgMSJ1z6I015YnY4YRpkdBu+xO6WbzX3zwSBU=
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Tenants"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/tenants"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Get All Tenants
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of provisioned tenants with their configurations","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"},"title":"Tenants"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-users.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-users.api.mdx
deleted file mode 100644
index 5533067cec..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-users.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-users
-title: "Get All Users"
-description: "Fetches all SDP users within the organization, whether they are active yet or not."
-sidebar_label: "Get All Users"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV99v2zYQ/lcIPrWA5F+x48RPy5a06zZ0wZJiD2lQnKSTxZoiVfJk1zX0vw9HyY6dpMnaocBeJFs8fvy+O/I+aSMJ5l7ObuQ7j87L20hm6FOnKlLWyJl8hZQW6AVoLa7OL0XNYWKlqFBGUIHCujkY9QU4PhKrAqlAxyNrAQ4FpKSWKNZIwjphLPVkJG2FLkx4k8mZfI10pnW7fiQd+soaj17ONnI0GPDtkNJfSLUzXoCoYK4MEGZCK0/C5oJRxDkSKM1gqTWEhhgDqkqrNKza/+gZaCN9WmAJ/IvWFcqZBOdgLSOpCMtAwOGnWjnMOENYgtIykrlynj4YKJEjM774D61OGUkNd4POagw57eBt8hFTkpGsHKeAVKtSZXsUPDll5jKS+BnKSvOj4fToOMHsKJ4mp6N4PD0exCd5PoonwzwZnCAOpqe5bA6IPYn3my0Mx99RfTL83CJHt/IfRDZbmU9k8d6MZj9jd8OJtRrBhPHd6jdteuQUxunxZDKJh/n0KB6fJkcxjIbDOD+dJNkoOcH0dHBYm07ngcygZSelvf8Urr3UlruKzW5khkvUXCQu3x5bcjU2UUdqko+zfJhlcXoyzuPxyQjikzFk8WQ8zPNsfIzTCTwgBQa/l1SuDJhUgf7AG9tZrR/wy0F7bHjLKQrV4xPBRdr/72XTcJbHg+HD4/XOQE2FdeoLZt9xhL6yx9E56x7dPfiZHPjnETwB1ftxpi6TVluJ3sP8kW3cytxtph0N+daSOJB5x2K7zngw3EO+P+NHArelOXpYmlfWJSrL0Pz4ujyu7o7AvwgIOjymtVO0Dif5ZwSH7qymQs5ubnmXlkiF5aM0x8ANeEj2684MPLol/+LJtePTIXnWFvSKRbY69qHvGlGlfkfuRIdp/O3va/axTOTWhdSjoS5/kfBqbjALDifAiIur0eRYVE4tgVAscM3+1Z3bs65qYSb3OwYvEDLeldzkTG4Dm+7oXRFqDU6cK5/UzmOJhsSlBsqtK8XZ5RsZSZbbshz1hj1uab4uS3BrOZPXBYqnMV5cnV++FIq9kazVIqmVpiBz36a9ICtKWKBIar0QFawZJTwFMXe2rthKHaaqUmHALltL361ukFbWLXoPUvv/o/jevDfXhfJhSSNshSb2tnYpispZPhOCCiAebqlYI8gG+EfgIgEmCwOpzVCkYESCIre1ycLEgv9obVfKzIXDynpF1in0M+YRixvf4vW7e5ztJSmuuiTFCaQLNNnti4Ko8rN+f66oqBP2g/43IbyciSB+R2UtuHGA4gwXKLqwoEqZ3IEnV6dUu04g14Weq2nvG5TlLvSt/yJtC/GcthUmYhv73WoK1GWcFuDIP0l5L65PDrFfgjL97sGTep6T8SvqUgSgwD/DSts1b69nlYjac9yiTtAZJPS999ymCF3p/8yv0C1Vyn1pK6uj2bNu3g9Bsc1j34VFUqsUjQ/tftsAK0gLFKPQp9r+zFizfn+1WvUgjAa0bqrv//Hml4u3VxfxqDfoFVTq0Ccr66kEswf8GkmcaS22HwUHTWZz530/5vOkcw/Cz9SvNKjwshzkbTqHupH19nOpsJ74wWaTgMd3TjcNP/5UI/fsm9tILsEpSMLL7G0TbQ2CLW2B3NbP0hQrdr8l6Lq1rXt+fuCUry+uZSThgdMtgtN1Pxh9O2TWe9j3PaulwFd+q310ymbT+mjT7OLboa/O6CRuozmBt03T/AOX6wb/
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Users"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/users"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all SDP users within the organization, whether they are active yet or not.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns a paginated list of User Details","content":{"application/json":{"schema":{"type":"array","items":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"},"title":"Users"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-wallets.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-wallets.api.mdx
deleted file mode 100644
index 9b8346dfef..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-all-wallets.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-wallets
-title: "Get All Wallets"
-description: "Fetches the list of available wallet providers to populate the dropdown box in the New Disbursement flow. The organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement. The initial list reflects all SDP-compatible wallets."
-sidebar_label: "Get All Wallets"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV99v2zYQ/lcIPrWAZDtufnR689a06za0AZKuwNIgOElnizVFcuTJrmvofx+OkmMnTpO2Q4E9LA+xTd59/L4jdR+1lgSzILNL+dbPwKjPQMoamcj3oDVSkFeJLDEUXrk4kcmXSEWFQVCFQqtAwk4FLEBpyDWKZUwTztuFKtEHQVY46xoNhDGl9NaVdmlEbj8JZeLYG1yKFyrkjQ9YoyEx1XY5EBcVCrvDSoTKNroUhbW+VIYRl4qqCHFnXZHj1HoUATUWpMxMgHDgSRWNBr8XPbVegCh3KHSrK6NIge50epwyWBCgtTh/cZYWtnZAais7DGQirUMf6b4uZSZfIU203hQzkR6DsyZgkNlajkcj/rhd38lNVZc3WYU1hIY4GJzTqogLDD8GzljLUFRYA3+jlUOZSfAeVjKRirAOO+M2/4gFyUQ6zzRJdTxUuRMTyCszk4nET1A7zUNHUMJPWB6lh0dHkB6ePB+nMEJMD45HJ8cnOCoxP5BtIg3U+DDSnyr3YEhMQlCBOKeyNTqYPZJXEbmQDYeLLh+cGxS25vyA7vpgdF1ohYauS1uDMg9jgVNpiYvBPlaJ6K61MvPrvYp+NadhKB3DM17hEQjLa6D7kKbW1zwjSyBMSdV4C348Gj9LRyfps4OL8Sg7GmWHR4Pjw+d/MXDjyh8B3CaSFMWg7sTKlv8SeTg62D+o7ww0VFmvPmP5HWf0C2cRvbd+X1XLCsjDV5zmQEDNbpxp6hw9Q9QYwr1nrZN5U6MbGvKNJXFL5pbFZp3D0cEO8t2MHwncbc2z/a15aX2uyhLNj9+X+9VtCXxFQNQRsGi8opXMLtfyZwSPftJQJbPLq/aKy0CV5YY6w8gNeEoOty0yoF+gDzG98VpmUnLeBvacZXZKdsG3HdOp35Fb5u1C/vb+QjQBy84hGqrQUF/BRAQ1M1h2HgRGnJ6Pj46F82rBzjTHFbtB1xLlpN+3jbtyj5IVQsnnsuXfUxvZ9I/fOaFmo7rlimcaiJ9tMTl7LRPJcjuW48HBYMQ1aOoa/Epmks3rYYwn5y/OngoVBAiyVou8UZqizF3Ljf5dwxxF3ui5cLBilDgKYuZt49ioPBbKqThhF+ijIW9WN0hL6+eDvdL+9yh+MB/MRaVCXNII69CkwTa+QL4p8FMhqALi6Y6KNYJshL8HLhFgyjhR2BJFAUbkKKa2MWVMrPiH1nbJtxOPzgZF1isMGfNIxWXo8Ib9Z7p7PUldX6Q0h2KOprx6srGjmaKqyTsr+haEp5mI4m+orAS3DlCmu+v1YVGVMlMPgXxTUON7gbwv9NieDr5B2dTHzvVvpG0gHtO2xFxsYr9bTYW6TosKPIUHKe/EDckjDvnKMuwHHtTzmIxfUdciAkX+JTptV3y8HlUimsBx8yZHb5AwDD5wmyL0dXg7PUe/UMXunaenObB+NoxBqZ2moQ9LpFYFmhAb/qYBOigqFOPYp7r+zFjZcLhcLgcQZyNanxqGf7z+5fTN+Wk6HowGFdU69klnA9VgdoBfIYmJ1mJ7xb7VZtZb//v/zeWRN5feCgk/0dBpvke3/V6te8O9lMvta2FlA/HQep1DwHdety0P/90gW9DlVSIX4BXXNpp4svE7dug5sktNigId2/kCdNO58J0Lyi3rf3V6IRMJe8Y9j8bdf2H0zZRZ7WDfteCOAv9vky+krNfdtaBtb+K7qS9m9BI30VzCq7Zt/wEuCm2D
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Wallets"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/wallets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the list of available wallet providers to populate the dropdown box in the New Disbursement flow. The organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement. The initial list reflects all SDP-compatible wallets.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of wallets","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-api-key.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-api-key.api.mdx
deleted file mode 100644
index 89fb6dc344..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-api-key.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: get-api-key
-title: "Get API Key Details"
-description: "Retrieves a specific API key by its ID. Returns the API key details including permissions and restrictions, but does not include the actual key value for security reasons."
-sidebar_label: "Get API Key Details"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWE1z2zYQ/SsYnpKMJDpu2oNubuwmbjOtx3YmB8fjAcmViJgkGAC0omr43/sWBG3qI3ac1jPNSSSx+3bfYrG70Cpycm6j6UV0cHIs/qCljS5HUUY2Nap2SlfRNDolZxTdkBVS2JpSNVOpYPFrWopkKZSz4vhwIiDXmMoKl9PtckZOqsIKVaVFk6lqLmoypbIW0MCrMmHIAj5lW3YkksaJTMNUpV1QIg8oU9fIwmPeyKIhMdNGWEobo9wSINJCfxKNIg0DktGOM/j+hhxcAS+s1NLIkhwZ5ruKKrxAQmVYUsyzli6PNsmfw3ZTqc+wqDKqHMiTEXo2ZAklQ58bZQgmnWloFNk0p1JG01XkljWbYZLVPGrbSxa2Nbwly+v7e3v8s261D58Joc+EbdKUrJ01RcH2Ul05eMOasq4LlXrK8SfL6qtt8zr5RKnjIBgOkFOdcZDfcnEzAu+32HPoh/TbUQjmQ1Bvm1JWY2xWJpOCBCvtAhukyABTGiOZunJU2h2R3TT2TlnHGzVMuLmRiFsmnIZNZYdGZVHoBWVXqv4vjAY0cXwiZJZhw7HbAkxfHx+eCjgxR/yhTF9qZZZXmXQ7o4fYlBKbHLHA2CnEeNPgESP4zRcstJmZsJEi3uB8Jd13mviQU7V2qBfSioA6NJAsvyGZLPJnketef9PZps6ewNlCYlcC9NDKozwegmy6zWtXjX0ixy17DStOuYK66sAVrW3546u9l9v1430lG5dro/6mbL1avIhfPKZAkDHa7Mx7+uKMtA8jWCddM5SrmjIhwxAljoWc78j8jhl9kWVd0MCN6E90hTVmd170dhCPAfKmRoe8q2Q+lTW/RT9tb9Fv2iQqQ1F9kv3ZHb47m48Jw5qWp/Pq6x2L+/ZMN9WPmnaPTI+e6q7MeDXMjFOyujEpDQLUm+unGD+V/ErSkDlADuH1kqcFjCy55llmTp4mTynTKJa1GiPgNl6prI0Yxdz0o01jCohErN2Dn3Hku9AMTdw1ulp1U9L6tv7+4dzXH9+mObN5COhCMxJWzSssLZTLMcqJo7P9n38RtVE33IjgG49jYco6CIfCa/YDV45BgLek5feZ9t6EEnfmqCikEYfKJo2xcL1y4qSQjispl0hgMN3Oy/3Jy8kex6ApS2mWYWy7H+PZ2eHJc6F4qHVaF5g8VeE8TW3msgquWh4VSnlNWC+uRS2XjOK/SkwTuqm54xoMxbXyCxpe+TLeW6/ILbS5nuycLP9fLn6sPlbnPBaxyUrgOFXjkLU4XHzMoCYdL3euYOhwuu5njg24kR/veSHVGOJTICbUpb5XzPmFxyS+FRiqtVUOKUJ2yn6MxYXt8OLwO84GQRrXIUjjRKbXVGWXz3LnajuN4znSsUkmqS7jRyE8nwpP/taVpeACJlW40gQxzwrpiuOOUR+3EhMI9oPsvXs6eQSzmfH1899Q6yEe4ragRPSy380mp6Icp7k0zt7r8kAudoYoLuFHHD7cy+chGm+BLDyQ9z+jutBLTq8HmaDIsdx1gx6B/CULajixuCyW9q/ZGWqrSrku9bSCmxMcxNgLjfVsbIMY5kH84ILHFa0vgLVEBRb7vk519ZmxALVYLCbSr3q0oGrjd8evj/48OxpDZZK7svB1Erwd7lADYNxwRbi7i8Putr1ZalZ3nfgHu8yH5uTQXmMkAbpGG6K3Co3wIuobIcSnuM+i5+UIEq+sVom09N4UbcufcYvl3nCBxxtpFF9BfbdEqvEzWuxMFpbuCd6z03DNfy6+8X+BnQT6lluxhA8Ad+tRxCr+D4n2ElKhO7KH3cJBmlLtBipbc8rauPDm6ByycqvNd46FB0bf6c5mw+5c6K47X1FZrbohom1v5bulr2oEirfMmQFGon8AeweBYw==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get API Key Details"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves a specific API key by its ID. Returns the API key details including permissions and restrictions, but does not include the actual key value for security reasons.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"The unique identifier of the API key","required":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"API key retrieved successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"API key not found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-bridge-integration.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-bridge-integration.api.mdx
deleted file mode 100644
index 7cf1933567..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-bridge-integration.api.mdx
+++ /dev/null
@@ -1,68 +0,0 @@
----
-id: get-bridge-integration
-title: "Get Bridge Integration Status"
-description: "Retrieves the current Bridge integration status and information for the organization."
-sidebar_label: "Get Bridge Integration Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWm1z2zYS/isYfGo7tCQrTpPq0zmWnThJLdeyL5dzPBqIXEmoSIAFQCmqR//9ZkGQBKk3u2lmrp1ME5HAvmP32SUeaQQ6VDw1XAraozdgFIcFaGJmQMJMKRCGvFE8mgLhwsBUMVxKtGEm04SJiHAxkSrJH0+ksjulmjLB/7QPW1/EDZhMCU1ivgASMcPIRMnErnS0T68vCRdhnEVcTMmHz2c+hwVXJmMxYWEoM2FIBIbxWLe+CBpQmUIu02VEe3QKJqd4WQlLA6ohzBQ3K9q7f6RvgClQp5mZ0d79w/ohoAp0KoUGTXuPtNvp4F91w+w2gXImi4jOwhC0nmRxvKIBDaUwIAzSYmka89Bua/+ukeAj1eEMEob/MqsUaI/K8e8QGho0OJ/JJI3BwDYv+KavrOdZTkHMDETW5jSgqUJrGZ4rmq/zJNBGcTHdlMCFgaMrJ77jeM3OILKE9u7p1eB2dH51+ubjeZ8G9tfg+va8P7q8ogH1/nlzftr/PLoY3Iz659eD4eUtDej5zc3ghj4EFL4yVJ32/B2GG/tow8vDXJt1QMNMG5mAGvHosHJOjWIPuUSBK874fHTcfcHGIZKer8LRhtl2OA6DeAGKT5znSczF3HfZhkOeIu+d4H9kQHgEwvAJB1WeOeSHLGryo8AnL3+OYILiY2iOBEvgMJ+LLI4JLi38nYLSUpBMRKCm0p3SGq/3ciZIXwJygoTxeBuXXHvacyuabM/xKWFRpEBrq1rTjDWWv8uZ+Jf72Qplgqxzjof0u12lVrVt5F0QcxHxBY8yhmKOM80FaF0PzPJpFZgfPp8h7SJarEf22SFTfNPJNx+t7mF+9ouUuNMMM2NS3Wu3xzaYW9pAHDPVkmranq/CdhUARupvk4iFIaRWIAMqsclAg1rwEJ4qkJHaE2jrgdrhso0DlW/sfRFHREiDdJSBqGdtlSqJyRhfkBXY5IUvcS0Xzq5QX+qWkHFm7LZiFe5hS8ZR7VE2lj1y6n6Ru9jwhGFyBgETHnIWk8FSgKoJigTsuRkpWHBY5mx1Nk641rw4VCR/abmlqZKLQpWazsUrXKYAE8/WZcUrXJayTDfNkj/Dt3IyGUumIlxxVmTB6uEX/0R4VqYBrexIA+obiAbUVxffOqkp1tpcMsx+Vgis4SW7+vFqUPGOWJXtMaSfGkG3RcwO85h14cxECH4wpSCwkPbIbSPGy2jK9+UGrJy1sbxa5hnRUfetUlPas1Wh8O1gWCmcG5BLMVLAtBS+3kwphtiDG0i22GPdNMhNTqFMtCVt8gOfEAdbxjH86J/ue3pZep5EMswSEKZISqcuddeiccJ4jGpicVaAiGTEzN4cFDEDR4YnsOHDTzMQtXpHlkwTR7aWhLqd7sujzvFR5/i20+nZP//9rvjAOuePjCuIbP1AcaqSG5Qlz3L0yoOXl2sZsRbcdbkfaqfhIxfzSzGRqJ0DyyMHlg/jlH830HUTz98N+ySCVGpu9N8MWRrAvmbZBRu9ev3L19WfqNRTD3hTF+9Qs9DwBbPZ8rTQVOdPwWFlFq2saIW2uC2C7Ru957XTXT61slW/6kfcW1S40YnuWFTHPYIFxGjy0QRglIIKQWw9O3VL9IttZAIWvOE2NgXCNGGk3FTJ1Gm9/M7gWctMhTBy1h1xoY3KbLZ5App+w8S8cAzxt1qP6Tyn2lg1ckds1SN3zMR8NC7Ktlo9ERdfeZAYSZSh5pGqGWGYYx/XL+Umxn4qXD218wrrUVmjnukISVplnq+AghD4Ag2HBGqEP0Eca3LB1FSWDBwsP8yjKAKH2Rx3X5BfGRdkaAIyZIJcKCZCrkMZkLPTinNu5JHIkjGoJwSm75l8024bHndfnLz8+dXrXzolPyUzC2aexc9tcvwaLI47nU735DVySNkKK+ZI4RDjG4r3MEtTaRGro0gsxZ2KYnKa0YAuuQL60KxW28+DF61+lDUCYruXttuyqf/DrhTYz1W49NNEbgPDRQ43DmaNfrWYhFJM+DRTVWULpViANeAkE9FmcfMFPRwD154TnA8qSf1gcN3Q81JBTZPKJbVMYLPskw9pkZj8Zrs6qXfDfr27f9v/7br74fq3tx8u331+//Y/V3eXnwe/vju9uTu9OTt91X9/+/Ji0L24GAw+fH7xpvtp+Nu7tyefXryyZyqW4TycMS5GCSTyCeep3EBwQwkYPJMSo5jQLNwwrz3OG2Cs5staVBcG2xOIlR+3YrwSoW2v1fWiur8O1uN7p0gF2JPYXYy4GI2fEEJ32pZospxJYjdujGpxmieLSlUPLlAIx2o8/zKEv+UJaMOSlCwRzNckyAXbJccuSN8AvaOiy3iuWdy+g+DUt8cu3n+XeZrT7+e1O414daH6sGeQWsSWo2wzCTb+ILATtKhQZ0mCOKdEgH5/XKwL6ILFGfiT5tpcGEVDukU81QkP/KBAskVg7KRbDonXXpDuIVoQDPLBSNmVb1L3xs81eFwDuM1Zll3gjV9r09dqVlqOSjdnmcUo058yViPFJw79/JnfE8dydU02hjDevMWfVfhhvz0W91mvmcuqE9ZIOPvCnEWr0USqIrPWfd9sDYujXrZ+W12/7QPFvhjY0n3bVVU3WzWzjV5xa5tn27L9LA+0VTv6nGZf4mMR21XUmopaO9DsBg6B+B0Y3sfdO2C3h5s3YHMDzW4Awzp4K0FXU8/QQwDfAHK2YBwPiOwrT36k7ysluwIf/wvoSed486PlnWCZmUnF/8xPaPVB8qf2T/u/QdaBMCglt3RBtkgYxba27we+NToXrwOagNZsuqVzzTUrC1wpBr2ShtQ0q6Qo+Jx0jj3KzR055W1fZb8XN+uiF5suupBqzKMIxHfxz3bzVTyfY4baLqvOyaY6qPmFzMQ/NdyeGRYTp+q2iDjxI+IG8ixtkUy+q2Bn2NRmM4ek/HsLD0jCzKS72GBzIF5aoK6AH/HGJQe1AKXtHYdMYdKjeLmhuPswROvn5vFvQFTjh5R/gNUGGn3/6ZbgZ5r8819mZjjFzc0TEM2nAiKy5GZGmCDnw+7Ln0mqbFUjc1i1aEBdBTl1B6KQFrEZnQGL0C1r/D3JG0OHS4v61Od6nCkNtre+jplBBI33RTBfgtK5lN3WcQvLSFXvb2dA9tP4Ydi//tEOgYmRMibjjMfGqul3JBoHigmbAxln8bwYtdinjEyVzFIccykIecrtC7mAvFktuAswS6nmrU2g/38n4hfxRdzOuLYsESKDOHKRmyqJR42YGbMD8FwU7MNlWgz6GuQCC67sTSIZAQmZIGPIw99unOGPOJZLHDioHL9IxQEH9jh7v3dFu+3+Poo8Ix2lzkhHYxbOQUQPPxTwdsrNLBsjhm4/i8KPPWKVL0VZ4YjIMC60m/faZcWtJ8VypJUpp2Axpdjr09YzNJsom0O/RbWCxCHdljAmxdq/rM0M4uQonDFl9F6RvXVtowDaCeOi7R7s1eeQGu8gToglVIxBY7my1xUOnjVssqZkno1BCTDgrpfZaw6Diftg7PVQteYJFx3JyVF1FyLmIQhtK0aRAFMWzoB0bZ7K8zPS6rXby+WyxexbS81t1e2Pl2fnV8Pzo26r05qZJLZ5MpXaJEx4hN9CeUXPqx5kWE2lvKTzWNXlf+JtP1erDHw17TRmXGBJt8Z8dMXxnm4pjg8BnUlt8O3j45hpuFPxeo2P/8gAy8X9A3Z/iuPowt4KDIrahNV0DlhRTu3X/KpN3EQKa79ivz3HZpFtFNm5LbLuH0i9eCW8FnSjXOYi4P/XwY4tj495CV+vy/X5q507nIrFarTmw3q9/h9++7Od
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Bridge Integration Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/bridge-integration"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves the current Bridge integration status and information for the organization.
-Returns live data from the Bridge API including KYC status and virtual account details.
-
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Bridge integration status retrieved successfully","content":{"application/json":{"schema":{"type":"object","description":"Complete Bridge integration information including status and related data","properties":{"status":{"type":"string","description":"Current status of the Bridge integration","enum":["NOT_ENABLED","NOT_OPTED_IN","OPTED_IN","READY_FOR_DEPOSIT","ERROR"],"example":"OPTED_IN","title":"BridgeIntegrationStatus"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"kyc_status":{"type":"object","description":"KYC verification link information","properties":{"id":{"type":"string","description":"Unique identifier for the KYC link","example":"kyc_456def"},"full_name":{"type":"string","description":"Full name of the person undergoing KYC","example":"John Doe"},"email":{"type":"string","format":"email","description":"Email address for KYC verification","example":"john@example.com"},"type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"},"kyc_link":{"type":"string","format":"uri","description":"URL for completing KYC verification","example":"https://bridge.stellar.org/kyc/456def"},"tos_link":{"type":"string","format":"uri","description":"URL for accepting terms of service","example":"https://bridge.stellar.org/tos/456def"},"kyc_status":{"type":"string","description":"KYC verification status:\n- not_started: KYC process not yet started\n- incomplete: KYC process started but not complete\n- awaiting_ubo: Awaiting Ultimate Beneficial Owner verification\n- under_review: KYC submission under review\n- approved: KYC verification approved\n- rejected: KYC verification rejected\n- paused: KYC process paused\n- offboarded: Customer offboarded\n","enum":["not_started","incomplete","awaiting_ubo","under_review","approved","rejected","paused","offboarded"],"example":"under_review","title":"KYCStatus"},"tos_status":{"type":"string","description":"Terms of Service acceptance status:\n- pending: Terms of service not yet accepted\n- approved: Terms of service accepted\n","enum":["pending","approved"],"example":"approved","title":"TOSStatus"},"rejection_reasons":{"type":"array","items":{"type":"string"},"description":"Reasons for KYC rejection (if applicable)","example":["Incomplete documentation","Address verification failed"]},"created_at":{"type":"string","format":"date-time","description":"When the KYC link was created","example":"2025-01-01T00:00:00Z"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"}},"required":["id","full_name","email","type","kyc_link","tos_link","kyc_status","tos_status","customer_id"],"title":"KYCLinkInfo"},"virtual_account":{"type":"object","description":"Virtual account information for USD deposits","properties":{"id":{"type":"string","description":"Unique identifier for the virtual account","example":"va_789xyz"},"status":{"type":"string","description":"Virtual account status:\n- activated: Account is active and ready for deposits\n- deactivated: Account is deactivated\n","enum":["activated","deactivated"],"example":"activated","title":"VirtualAccountStatus"},"developer_fee_percent":{"type":"string","description":"Developer fee percentage as a string","example":"0.5"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"source_deposit_instructions":{"type":"object","description":"Bank deposit instructions for sending USD to the virtual account","properties":{"bank_beneficiary_name":{"type":"string","description":"Name of the bank account beneficiary","example":"Stellar Bridge"},"currency":{"type":"string","description":"Currency for deposits","example":"usd"},"bank_name":{"type":"string","description":"Name of the receiving bank","example":"Wells Fargo"},"bank_address":{"type":"string","description":"Address of the receiving bank","example":"123 Main St, San Francisco, CA"},"bank_account_number":{"type":"string","description":"Bank account number for deposits","example":"1234567890"},"bank_routing_number":{"type":"string","description":"Bank routing number","example":"121000248"},"payment_rails":{"type":"array","items":{"type":"string"},"description":"Supported payment rails for deposits","example":["ach","wire"]}},"required":["bank_beneficiary_name","currency","bank_name","bank_address","bank_account_number","bank_routing_number","payment_rails"],"title":"VirtualAccountDepositInstructions"},"destination":{"type":"object","description":"Destination configuration for converted funds","properties":{"payment_rail":{"type":"string","description":"Payment rail for destination","example":"stellar"},"currency":{"type":"string","description":"Destination currency","example":"usdc"},"address":{"type":"string","description":"Stellar address for receiving USDC","example":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37"},"blockchain_memo":{"type":"string","description":"Blockchain memo for the destination transaction","example":"12345"}},"required":["payment_rail","currency","address"],"title":"VirtualAccountDestination"}},"required":["id","status","developer_fee_percent","customer_id","source_deposit_instructions","destination"],"title":"VirtualAccountInfo"},"opted_in_by":{"type":"string","description":"User ID who opted the organization into Bridge","example":"user_789"},"opted_in_at":{"type":"string","format":"date-time","description":"Timestamp when organization opted into Bridge","example":"2025-01-01T00:00:00Z"},"virtual_account_created_by":{"type":"string","description":"User ID who created the virtual account","example":"user_789"},"virtual_account_created_at":{"type":"string","format":"date-time","description":"Timestamp when virtual account was created","example":"2025-01-01T00:00:00Z"}},"required":["status"],"title":"BridgeIntegrationInfo"},"examples":{"not_enabled":{"summary":"Bridge service not enabled","value":{"status":"NOT_ENABLED"}},"not_opted_in":{"summary":"Organization not opted in","value":{"status":"NOT_OPTED_IN"}},"opted_in":{"summary":"Organization opted in, KYC pending","value":{"status":"OPTED_IN","customer_id":"cust_123abc","kyc_status":{"id":"kyc_456def","full_name":"John Doe","email":"john@example.com","type":"business","kyc_link":"https://bridge.stellar.org/kyc/456def","tos_link":"https://bridge.stellar.org/tos/456def","kyc_status":"under_review","tos_status":"approved","created_at":"2025-01-01T00:00:00Z","customer_id":"cust_123abc"},"opted_in_by":"user_789","opted_in_at":"2025-01-01T00:00:00Z"}},"ready_for_deposit":{"summary":"Virtual account created and ready","value":{"status":"READY_FOR_DEPOSIT","customer_id":"cust_123abc","virtual_account":{"id":"va_789xyz","status":"activated","developer_fee_percent":"0.5","customer_id":"cust_123abc","source_deposit_instructions":{"bank_beneficiary_name":"Stellar Bridge","currency":"usd","bank_name":"Wells Fargo","bank_address":"123 Main St, San Francisco, CA","bank_account_number":"1234567890","bank_routing_number":"121000248","payment_rails":["ach","wire"]},"destination":{"payment_rail":"stellar","currency":"usdc","address":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37","blockchain_memo":"12345"}},"virtual_account_created_by":"user_789","virtual_account_created_at":"2025-01-01T00:00:00Z"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-circle-balances.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-circle-balances.api.mdx
deleted file mode 100644
index 9a02a638f8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-circle-balances.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-organization-circle-balances
-title: "Get Organization (Circle) Balances"
-description: "ATTENTION, this endpoint is only enabled when the tenant distribution account type is `CIRCLE`."
-sidebar_label: "Get Organization (Circle) Balances"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWFtz2jgU/isavWzbMZdAmszwxi0pCSEXIOk2zaSyfcDa2JIryaGU4b/vHNkGk5CEdmd3Ng/ByOd8Ohed77NZUMOmmjZuaYuFTHig6Z1DfdCe4rHhUtAGbY5G3cGodz5wiAm4JiD8WHJhCNdEinBOQDA3BJ/MAhDEBEAMCCYM8bk2irsJ4hDmeTIRhph5DOj5rd27ave738rUoTIGxdCq59MGPQZzrqZM8J927V2bKy+E96sAHapAx1Jo0LSxoLVqFT82Y74CkyihbTSyAPaHJikccddwnhQGhEEUFsch96xp5S+NUAuqvQAihlcKvidcgY/1yvKhDnULlcPsaINK9y/w8F6sMDfD01BznydQ2jCTYCDW+20U31eg7WVmiGUWU/q0caMASGZM5MTWYltLHBIr0CDMuoHPmjUcdfv95pXtFvxgURzivsftz82T+ueT+vVp/eToU/3yrHN0Pjw9qw3Ozr60huf1697ooDu+uLwZdm5qJ4f7Z7X61dWwT5cO9Wwb7mcsDMHcc3+3dHqdPJOsjan/LikUzts6g71qtXqwf1A9rGFM6f67xGFRX6np5i6d3nB01WuNcYjum+32+XgwKmclLXda99fNcX+EHiKJ8EC8at8dXFNnZ8itdmkp1mZ3Syc/hFuyX+fRbI96191CoKuFi+6g0xsc34+H3at7u9rEHendEsvKTVqGQqGa2SgsC/Oz3pspxeZbC//mMHMDURHqpSHSGsy9J/0dG27tCdrnbc/2JDw9b0MDYcgUEWBmUj1sHoDxsNPGVNNdudYJqF/ZN/X4nZ2PW63O/mHv6KB/c3p4cXjW6V4P2zdXh52L8c11ffBnvTO67F4f9fcHzdF+8/JT/Uu/f9RvfrTRRjlb7RCntX0S4bNZK1erFE/Ec/+8gznCkz5vnTHSTpQCYcJ5pky5ICUafDKRqkgU2xA0Bpifzkxf6DL9c+j+NmFpMZ8gd4M2DhHSEJ3EsVSmKH9bdY9ra56zl51ASyPlTQX6UPmwKTqvn2NQSu5wlDpgGA81Ya5MjI0gdVxig4xib0+MLcmqmauNaU88spD7hIs4MbQIN+EQ+vcTKWljfY11WGmfk627TK1sXHuSwdfESOICYYJwYWAKiq4bs/e8MWPBEhNIxX9a4J01/bfKu3vZnvOqSCIXbOUj0JpNtxDQ8qViD6QhG2muo8j32a/uFZCfevybwBZbg5cobua0cbugLWAKVDMxAW3c3i3v0N8EEh/ypmBLxfAWrRT4W4N6BKWtf6JC2qAUHXPcITYurWwRfa0cMT+F59JxcjNaswKGDcJkZ8Ihmk8Fzi83AR637rD28YDEij8yA+QB5jihgkVWAbOMrSeqDYIHwHx7PPH7RNpoMlLJubnDtZsoDRE+o1yEzEykikjzokcdiummUdbKe+Uq1iCJIqbmGTW+jvFu2Ll4j1PFiJEyJG7CQ2PTLFKonaaIPQBxk/CBxGyOKHaVkamSSYzMpMDjMbc35COol9TlOXv/v0L8Kr6KUaYHTBAZgyhpmSgPSKwkTikxAbOUnIYiBTEyzrn5CZxDmPDtDav+HhNISxOZCN86BvglDOWMiylREEvNjVQcdAPjKJFbneJVss+SXyhSKc6KVHKZ9wDCv3sXGBPrRqUy5SZI3LIno8ovIbxvEJv8KpQ5QTJkPHsdysxsVlxMFNNGJZ5JVJZgrpuv9rT8C5lNlOXif5JaDvFWbjNwSW7729kEEEYlL2DK6FdDLthVjAKoRIyLSrbwaj5vpfEJwohYIBu/D3Eo53i83syEJBrtHhIXlAADuvwVacqAivT5ZAjqkXvIS3laWZhlqaYVa1SSk5LOzBwacg+EtkqRE2DMvABIzfJUys+I1ahUZrNZmdm7Fi1z1ZV+r90dDLulWrlaDkwUWp6MpTYREwXgYzCk+NpP8vd+Unjx32CexVrk/4PfKDJ9MfDDVOKQcYEKbguwyGTsduOXgEBqg2uLhcs0jFW4XOLy9wSQ2G/vHPrIFMegrDY6uYqg7j0Acn/T8yBGlXxkYZJq25MHmQ1FPe7i+x57JocPVg6zC0TPb4l5AfupsKUh4P+l84LLYpGK7XK5sk9vveiRpZhbYw3vlsvl3+fIblM=
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Organization (Circle) Balances"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/balances"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-ATTENTION, this endpoint is only enabled when the tenant distribution account type is `CIRCLE`.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns the organization's Circle balances","content":{"application/json":{"schema":{"required":["account","balances"],"type":"object","properties":{"account":{"required":["status","type"],"type":"object","properties":{"address":{"type":"string","description":"The address of the distribution account, present when the account type is `STELLAR`.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"circle_wallet_id":{"type":"string","description":"The ID of the Circle wallet, present when the account type is `CIRCLE`.","example":"1000646072"},"type":{"type":"string","description":"The type of the distribution account.","example":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"status":{"type":"string","example":"ACTIVE","enum":["ACTIVE","PENDING_USER_ACTIVATION"]}},"title":"DistributionAccount"},"balances":{"type":"array","description":"The organization's Circle balances","items":{"type":"object","properties":{"asset_code":{"type":"string","description":"The asset code of the balance in the Stellar network.","example":"USDC"},"asset_issuer":{"type":"string","description":"The asset issuer of the balance in the Stellar network.","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"amount":{"type":"string","description":"The amount of the balance.","example":"100.00"}},"description":"The balances of the organization's distribution account. Currently, this is only used for the Circle distribution accounts.","title":"Balance"}}}}}}},"400":{"description":"Bad request, not supported when the distribution account is not of the CIRCLE type.","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-info.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-info.api.mdx
deleted file mode 100644
index 59647aee5e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-info.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-organization-info
-title: "Get Organization Info"
-description: "This endpoint returns the organization's info. It is used in many places across the UI. It returns the name in the navbar and the public key of the organization’s distribution account."
-sidebar_label: "Get Organization Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWOty4jgWfhWt/nR3rTF00tNTxT8amAzduTCBpGc3nXKEfYw1yJJHkmFoiqp9jX29fZKtI9tgCCHpndmtnT+Jkc7107lJK2rZ1ND2Hb3SUyb5V2a5kvTeoxGYUPPM/WzTccINARlliktLNNhcS0NsAkTV+F4ZwmWsfDKwhBuSG4gIlyRlckkywUIwhIVamYLzZuAI68IkSwE5iu/5hGnCZOR+ZvlE8JDMYElU/Ejzv/7xT0MibqzmkxwXCAtDlUvrU4+qDLSjGkS0Tc/A1n0dyFhRj2owmZIGDG2v6Emrhf92Ibgu7ayrJRFYxoWhHg2VtCAt8rEsEzx0BM1fDDKvqAkTSBl+afg15xoiBL1ucVBaTD3KTcCyTKs5E8GG3KNCTVWQa0E9ikBRj2ZsmYK0QchkCEI4lUEGmqsoiNgS7co0n7NwGWRK8HAZCC5nzt0Q+Bx0wOWc24JPgwEZBVxa0Ki5FGB5Cl+VhCC3YaDi2IDF+LDLDGibqskvEFqnB2G2vEDQ2ddeVVTopZxSj8JvLM0ELo0sGqxJh0d0XfPtKFNibWbazaYpmBsRN5NcG0AQGplgNlY6bUxYOAMZNSKY+yWlr/S0WT+5JipExQePYO+YjGU2d1igZc86z6JIgzGHXNnPKiAlcRXUh2LYI5k7G0sWCRTJUe4QlI+p9jAa98/PO9cP/g5eZ92fOx9Pf/54evvp9OMPP57+dNH74Wr06eLk8uLi7x9GV6e3g/H7/s3wp8+j3ueTj9+/uzg5vb4enSMwIdehgGDBhAAb8Ohl7gx6lSddx08K/pe40B1cd8/7ex68bbVa79+9b31/gjYV+l9ih5N6BNNdLb3BaHw9+HAzHlxdBp1u9+rmcuyXkPq9D8Ft5+Z8jBwyTzEgjtL3L2+p92KRB+kKKLZk92uvCsKj+dHpjge3/Zqhm4Vh/7I3uDwLbkb968CtdlAjvV8jrNwWMNSA6pSp8ESKBEU9DmawfP5Aev3hdb/bGfd7fyFDAcwA0RCDJlaRQ8L9Kim4NBZY9McF9aFidhTRv7Za7VYLWQ8W5S3vRCkBTD7yvS/ZRIAhaS4sb+QGNKnEkIXSs1ioBYmVJvVaZuo2WJ3D+htK9tYmXJ+CPlx3Upd9KibIRGzCrEuWUW9IFlwIsmDc4gEVOtzeVjNu4EplVCkgYXMgUmFTn3JjQUPkk0FMHloPXkGRAit7fSGXy2ldbAzM5trVg4gbRG738L9bv6Dp/cEAFHoII6XigpQbR4D24+nVwShQKwB40v1KWN2Ll7l/oKG/qCQiZXVuO0NMKZEUEo81XNdGS/JGSV4PzcLrYtgKUjCGTSGwkGJrfmHhDnNjVUoqpmKItIq4INxGiilALqPPJ8j6EEHMcmEfSKmacCNfVROmC8Wi9ZTbrwwppzbC7StDMmUMnwhA0SwqQj5WQqgFnvLGojnT3OV0m6xWfn2WvGQprNdkkfAwwTNEAfV9ggSoM+bTXEPkhtvVyr+uwXbO5Wxfhju5KUgcYyEik6UL0gqUvVQkr7kkIdZYi0M7Ny4hq/bLdxDwCsdZblXKLA+ZEEssTyAjtK5ICJDRm90K/DeVF6m+zYl6LixVTmKt0sPw+KQreDh7wu966mBoKZv9vkC6Gg834bA5QgN2Ax8ShCqCRziGCt21UK5uTSVYs//kIXc1Hj5iqwFxMLCOA/I/iLuN3dxgkOknwMgSJYHMQfO4vIY5v3xan3V27rvrNW69a719fO27kSy3idL8q7uDvfiad/yKAFor/TiO1+it1cw8L+HROCjzdAIaRZQgHxDv3NzguTGDXipLdtzcWlHpedd6W5O8z/HfFOxkGwhzze2Stu9W9AMwDbqT24S27+7X98hvE4W3+yk4qBhu0Z0bH0UhGruFk+HumpQicyV7hIdXoFvXsEGRZfwTLB8Vm4+fx0WXwtqHpoO0ZVx4xPCphIgsuE0Ik6Q/OvnufdFwLeBjhl9d5tu0U3pdWctReAIswlPFARRfKtCaMoKrG3SvNjiSYXkJJp3hgHoU3S2sPPHf+i3EIE9TppdlkTwu4/WoN3yDycaIVUqQSc6FdW7WgXWtOGUzIJNczKqO4FYZmWqVZzhkaQh5xt2GcjNSTbsEi6Owf7CO/3+Z+EV+keOyvjFJVAayYVSuQyCZVpipm/GwMMXNyll1Fd0T522et1zhDZkkE2wAuYwc40430JApw63SHEwb7WiQu3Iue9mDyP3rapybcpvkEz9UafObJLxpE+f8xpSla2eMl0NtSea84jLWzFidh26kdQ5Wk/LRM/W/wbNYu3r8e1yrRDzn2wImpKL9j71JQKSNMGHamqMm1+iaVgM0U8Zls1w46s9zbvwIIiVOUHHrhEyopRs2ns213CDdLJ+AlmDB+F+wTFnQqbmKR6DnPHzqzuCIGipumJLMo4KHIA1sXwtpJ2NhAuTE1amiPqOsdrO5WCx85nadtJLVNM8H3f7lqN848Vt+YlPh6mSmjE2ZrAk+A7s7FJWPvjvFZrXt7X/u5+6yW1n4zTYzwbjEmaB8Wi0a4x1Ve6/9iTIW11erCTNwo8V6jcu/5oCt4u7eo9UI6jquV/Ul7KTuCYh2whAy7L1zJvKiW+6NRzt9+qyPj1/sUYOduQZbfqD0aksua7L3W2VhAv5de0+wrFZF+16vN/TF1pMcpYsVNeJ4v16v/w0sJvOd
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Organization Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/organization"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the organization's info. It is used in many places across the UI. It returns the name in the navbar and the public key of the organization’s distribution account.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns organization details","content":{"application/json":{"schema":{"required":["distribution_account","is_approval_required","logo_url","name","payment_cancellation_period_days","privacy_policy_link","receiver_invitation_resend_interval_days","timezone_utc_offset"],"type":"object","properties":{"name":{"type":"string","example":"Stellar Aid"},"logo_url":{"type":"string","example":"https://stellar-disbursement-platform-backend-dev.stellar.org/organization/logo"},"distribution_account":{"required":["status","type"],"type":"object","properties":{"address":{"type":"string","description":"The address of the distribution account, present when the account type is `STELLAR`.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"circle_wallet_id":{"type":"string","description":"The ID of the Circle wallet, present when the account type is `CIRCLE`.","example":"1000646072"},"type":{"type":"string","description":"The type of the distribution account.","example":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"status":{"type":"string","example":"ACTIVE","enum":["ACTIVE","PENDING_USER_ACTIVATION"]}},"title":"DistributionAccount"},"distribution_account_public_key":{"type":"string","description":"DEPRECATED! Please refer to distribution_account.address instead.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"timezone_utc_offset":{"type":"string","example":"+00:00"},"is_approval_required":{"type":"boolean","description":"Enables multi-user approval workflow for disbursements","example":true},"receiver_invitation_resend_interval_days":{"type":"integer","description":"The amount of days that the SDP will wait to resend the invitation to the receivers that have not registered. If `0`, that means the resending invitation feature is disabled.","example":5},"payment_cancellation_period_days":{"type":"integer","description":"The amount of days that the SDP will wait to cancel a payment that is waiting for the receiver to register. If `0`, that means the payment cancellation feature is disabled.","example":5},"privacy_policy_link":{"type":"string","description":"The link to the organization privacy policy","example":"https://stellar.org/privacy-policy"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"otp_message_template":{"type":"string","description":"The custom OTP message template set to send OTP code to the receiver complete the registration flow. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.OTP}} which is the OTP code to send to the receiver complete the registration flow (in case this is not present in the message, it's automatically appended at the end).","example":"{{.OTP}} is your {{.OrganizationName}} phone verification code."}},"title":"Organization"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-logo.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-logo.api.mdx
deleted file mode 100644
index 6467cf18a5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-organization-logo.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-organization-logo
-title: "Retrieve Organization Logo"
-description: "Retrieves the logo of the organization for display in the UI navbar."
-sidebar_label: "Retrieve Organization Logo"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVcFu20YQ/ZXBnBKAEl0D7YE3tzFSN0FtVA56sHVYkiNyq+XudnYoVRX078WsKEdJUBtpeygvJHeGb98bku/tUUyXsHrAW+6Mt38ascHjssCWUsM25tsKfyFhSxtKID2BC12AsMrX4ew5WAWG1qbozA6sz/UPN+DNpjY8xwJDJM6dNy1W+JbkfNf3oQtYIFOKwSdKWO3x8uJCT5+SuX2HBTbBC3nRqonR2SZjlKERklkSJjNoLTU9DUavZBcJK0zC1ndY4CrwYAQrrK03vMODHgUOJH1Qdh0JFhiN9FhheS6zdEemiXhDrNPb48gOK8TDUpebka3sFrr1Ucb3ZJj4alSsJyYm2ne0w89H/dOv9zAmavMwzSg9eZnUFZBs56mFrZUejIfrxeW330FkuzFCsKadDtmbQeF1t8CnN1qgVfCeTEuMKtT6VchsrDjtXwg5Zxje2FSPnGggL3DnjOig4OruBgtUuUeWl/Nv5hc6g3EYdHoV3vcEz2O8Wry5ew02gQEJwUE9WidZ5vl0E0iAwawJ6tGtIZqdouRVAx2HMeqnx9TYaHMhbIjzp3ba3ZNsA6/nX4z2/0fx0T/6+96mvKWHEMnPUhi5IYgcfqNGQHojWj5SCR4kxNPP9xlcAca3udCElqAxHmqCVRh9mx/s9ca5sLW+A6YYkpXAllKlPGbwkI545XSetWdDmsVpSLPaNGvy7fJVLxJTVZadlX6s500Yyq9CeF1BFv9EZQf6Wxvrjz4ztWVV1q/YJOGxkZEngfpe5KV3Ov8KZSvOrvJvpJ0gXtK2pRpOvf9YTU9umDW9YUnPUj7rK4WJysFYX04Lz+p5ScaP5AbIQEfzp+jCTj+vF5XAmLRvPdbEnoTS/FFtSoiHdLtaEG9so750kjXRnAfuytw0C6tZmtoKdLYhn0gd7WSA0TQ9wWX2qaM/K1ZVltvtdm5yNaNNj6by/c0P1z8vrmeX84t5L4PLPhlDksH4M+BTGMJ5esEUX584zv5jTP1XETqFh9AfUkZnrMfDpG4/hdUDngPqaJTZssA+JNHyfl+bRB/YHQ66/PtIauAPywI3hq2pNQ4elofilBaab2tSj79qGooaixvjxmOG/U30ahA+Renb63s8HP4CJa4Ftw==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Organization Logo"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/organization/logo"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves the logo of the organization for display in the UI navbar.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/octet-stream":{"schema":{"type":"string","format":"binary"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-profile.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-profile.api.mdx
deleted file mode 100644
index 547938c8eb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/get-profile.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-profile
-title: "Get Profile"
-description: "Fetches the individual information of the logged in user to populate the Profile page."
-sidebar_label: "Get Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVlFv4zYM/iuCnu4Ax+4KbA9+Wrd2XW/DViwd9pAGg2wzthpZ0ig6uVzg/z5QttOkXdvdhgHLQ+KIH6nvo2hSe0mqDjJfyFt0K21ALhNZQShRe9LOylx+B1Q2EAQ1ILSt9EZXnTJC25XDVjFIuFW0GlfXUAltRRcABTnhne+MIojmcQfhVQ2pTKTzgNH/ppK5vAaaKCQSIXhnAwSZ7+X52Rn/nLL6BahDG4ad/MGxdJbAEuOV90aXcYPsIbDTXoaygVbxE+08yFy64gFKkon0yHRID1uuNAb63aoWjrCBUNtaJhI+qtYbXvqgLMg+kUb9Lfili2holTavIx8qB18zLHVYsw86M1AbfRSi2slEaoI2PI/V94l0WCurP8UMvECOYYdNT2UP2k6kRf4H+k84HiguZAUbMJxOLqa/YCHnBMYoFBe6Ym2kKYqezr/nTyIDlB1q2sl8sZffgELAi44amS+W/TKRLVDjuHJqiAeo2CSzx1oIgBvAEN07ZMaS/aawc66FIafHwR8z7PUPwCk+LbwPv91x0VVi5VCojhqwNJZZIoKuLVRiq6kRyoqr+fmXXwmPesPvwBp2XPZjDng3h2Ni+CA5eAOqAozHwu9XZDMmZ8rZpQ5FhwFasCRujSJ+DcXF7Y1MJMsdWJ6nX6RnnIOubRXuZC7vGhCvx3g3v7x9L3QQSpBzRhSdNhRlHp9h4Pe6VWsQRWfWwqsdR4mrStToOs/tAKHUXkeD23AvONrdAm0drtNnqf3/Uby39/au0SFuaYXzYGfBdVgC9xxuHYIaRWweqDgryPmpIT4Jlwhlq2goXQWiVFYUIFaus1V0bPiPMW6rbS0QvAuaHGoIOfOYiUUY4mXj76w6StLMj0maFapcg62W7xoiH/IsqzU1XZGWrs0+K8L7XETxByo7wf1VaTtMgxEWVWm7QhUIu5I6HAXyudBbZ5p+hrIVxvb+b6RNId7StoVCTNh/rKYB087KRiGFVykf4TJCgKxV2mbjwqt63pLxPZhWxECRfwXeuB2X15tKRBcYt+4KQAsEIb3nNkWAbfh5NQfc6JL70iRrpMmzIIugmVvNwghLpNEl2BCnzNQAvSobEOexTw39mWPlWbbdblMVrTHa6BqyH2++vfppfjU7T8/ShloT+6R3gVpljwJfA4nHq8RJi9k/XhD+u3vNOD8IPlLmjdKWZ1wUuB+n1EL6x9tW4wLx0n5fqAC/oul7Xv6jA+7bi2UiNwq1KngKLJZ9Mg0JHmtr4NZ+UZbgeQZulOmG0fXk6nMyL6+v7mQi1bNpt47Tbnzg6JPJ7o5iP51bAwX+7pMXXPb7YZb2/QE/mF70GCVOaE7hsu/7PwGOS8iP
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/profile"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the individual information of the logged in user to populate the Profile page.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns user profile","content":{"application/json":{"schema":{"type":"object","properties":{"first_name":{"type":"string","example":"Jane"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string","example":"jdoe@mail.org"},"roles":{"type":"array","items":{"type":"string"}},"organization_name":{"type":"string"}},"example":{"first_name":"Jane","last_name":"Doe","email":"jdoe@mail.org","roles":["developer"],"organization_name":"Stellar Aid"},"title":"Profile"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-disbursement-receivers.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-disbursement-receivers.api.mdx
deleted file mode 100644
index 97cf24be1a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-disbursement-receivers.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-all-disbursement-receivers
-title: "List All Disbursement Receivers"
-description: "Fetches a list of receivers within a specific disbursement using the disbursement  `id `. This endpoint supports pagination."
-sidebar_label: "List All Disbursement Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWutz2zYS/1cw/HDT9ESJbz1mOneKJTtOZMex7LhN6lFBYimh5qsAaMf16H+/AUhKlEXJcZL22pl+iSNyH79dLBe7CzxoAs+5NviojSj3c8YhhkRw7bqlEeABo5mgaaINtEMQwQI4wiiiXKA0RAwCoLfAOLqjYkEThBHPIKAhDRCpCUM5p8kciQVsPka/UIJ+aaOLBeUIEpKlNBGI51mWMsFRhuc0wVJ7W2tpaQZM/Tgm2kCbUC6GUVSHfF6h0VpahhmOQcgfg48PWoJj0AYaJVpLo9KWDIuF9tjA45E0SqKsi9VaGoPfcsqAaAPBcmhpXNxHUh6ncRaB1tLgUxalBLRBiCMuCYIFxFgbPGjiPlOUgtFkri2XrRWYDM+hgvNbDux+C8/FAqQPACV57ANDIkWhXIP2BqRKZYkpTFlcR1QifgyoELkFaBbRmIqnYZWIihhIGeESHAORswRlwBTsbwrzWsriWZpw4PK9ZRjyzyay4Soy6wuI6oERpImQizp40HCWRTRQIdX5lUsBD9sAUv9XCKRDMiYDUNBC/To0n6ZN4JPYDgVpO1bhM9D+I931g/2v9Qr8YGlLKQduP4fT3ObE80J5yUoTAXNgdd7esqWJVOBoP5npLSUhFUrf2druZUsjWNR9hRnDMlyogJg/7RdK9tsGgY3dbmDorucZuuO7WMdh19NxgEnQ9Y2+37clCogxjfaLqhLVfyVpO2Vz5aNFmsCsjLC97P82Xde1bK/ndF2l8ZMAluBo9pQJOWem1TcMU3JVIGZ3OIpAfL2DeoZt2CZxdJMYju70un3d90hfJ4HrOWbY7/d6UFf89RoNqw8WEEMPwfd0J3AMvec7Xd3o2R7uuV3HxJZWj5fq05tQoaB8K9NdTHAfiKs7rot1p9uzdGwA6KZndL0uGAR85fMite2T9J76DCcCDTmnXEieRRqDSs57+RZCZHzQ6dwW/DjL2kEabxh/pYytTOcCogizGSaEAef7pR8d/Dh8bf/42n7/xn59+Mp+dzI6fDt9c2Kdnpx8eDl9a78/vvDGl2fvrqajK+t11zmx7PPz6aSuKIY4bdiCNglmxdsGqoABFkBm+InkZRmWrRuWbtgXpjFw3IFrtg3D+CBl5Bn5ahk0uaXPktHflhFhLmYxcC7TJIdE7JC2uZ0IGgMXOM7Q3QISVRhUnxKSEqtfBOEEKZgqMyLsp7lAQhY1Zbw34TSNbZwqH88yfF+UYPvtLfJ8QTqroHwGT4hpBOQztRhFAokxTWgyfx5TgWiG4zTfZHnmRoE5BzELVJ2wT+3ldHQgNRf0lPP8qcR+9PLlyOkeH3qTqzfds+7JaPx+enB13h2dXV69t09/skcX78bvDyfO6fDCGb57ZX+YTA4nQ7fBvv2KTMNoG8ZGdhgWbEv1QWKRN/s0yWNVmp8PDy+0lnY+Ho5+Un+PjqcX4/PxSGtph5Ph0dF4JCv2x3mXFzloWihYqZotKBcpu//yNfkTIa8+wyZtso6U37KsRUCXpE99bB8aN6gNra8K74wTwe61ZRN5QV37Ar9+SyMktKzQdXXbcvu607MsHTtg6QEYpm07/X43dFR07wy37TK9oK26mgpqU2CudwXBcMJxIKXsqG+29aw7pxo3okXOnBaCUQLiLmU3bXQsUIAT5APKORAkaCrZgps6yB3MZSf5sXo8wX7KsFys6++qHTlaPWuXNsmKr/OihVK24hx/kkuzZqooQT3vvGhvJjTftvvEDHp9YpuO2fP8nul0AwuHTtBXhYjvEz8gXUxwj5h2z7PtvtH1nL6vtlLKgggKz4bAZrIrAi4+270Hih9V/KjkR8cj5UzKUZpE9yhjIPe29W5V+fIOcxRjAqX3CnGbFnYd7PV8D+t26HV1x3J83e/5hg5u38Zmn3Qdz65HyaobbzRib07btq+gbQjTHankbHw6Oj49kv8bXk5VQpleHhyMp1OZWobHE/XoYHh6MJ5sJpmzQvYz8uGjDjNBeD5nMJdlzarbjEFg2Quh4tPnSHaZxY6pLCqUyNFJQoqvZFVZpOFqufjKEcECJ3PgKA2CnDEg7W+Rl/+Kbi9LssYA+hZpv1ZPbqb9DUCb6X4/kWp769OhL8z726uRJ/S3HBAlkAga0mK68nhkVjc9z9U8a2114Jo+Nomruxaxdce0Qh27/UD3ILQt4vax79j7mqKGMQ+OYQeM2sZVe6H/miegW/39GWBXgE0vhucXKohWAXbw9uRsMr7YDKf6dGcdU/sblm3jFL3cpza+xn0e3xdsnm4bF4Y5sKyB2233bLPfdT+jB9qGpTqLgunbI+u1bdNzzUdfQ92fVbuqiuivr2rCEEPg+LbueL6hO8R3dOwEju4Ftmv0DLfbNVQ1vau6f5R+JSikaJsK/90lf5OYghpV/fi36gv2h+EXJa6ngugLhRKI4CuFeqVQd51ityO6KtZUSKFVIK0aIRVp/wzI/hmQ/UkDsr/KZOtP66F3NrCV6/8uOWu7OPubom86t9ycNDRR1E9fFLFjmNunYJcJzsUiZfR3IJsnXt93vn/OIRcwljbspsUBCMNf0o1U53ktbXfpryxb+XIFQztNBdqwbI2i0uMYZk3yY45CctOx3x+lTS2Rvb1EhynzKSGQ/CHr0+y+tc7nuGGDS5njbJsjLT9M8+TvGm7PDIuwNLUpIpx6RJwDT3MWAEpWXJU6DkHOqLhX1xNeAmbAhrlYaIOP1/KsOwaxSOU9h7k6PVDXFQZap17+884DJcsOqx1uc2C31ZWHnEXaQNOksErXVC5E4am6xvXII6NvYHvm8frqohjUhSlTAS4b1MJTLcTpPAGi7n/IU5Dx1HI9lDF6K9uXG7iXo4vyfsGw/DaKBFZeMVgAJsU9BI0mYXFeVWbAqmzcOMs/i7CQyRcNz461libNLVBabbNtSB/kcYzlJGej9GyW8d10dPZCjs8wEmkaIT+nkVBmpmyOkxKqutsQ4xtAfh7dVHMS9RSjOUvzrLwHQTOqXqTygKhp8tnY7/21IP6c/Jyo6zhSZYLSDBK9DOKMpfKrQ2KB1cyxgCL753TVnz4S11pNvGTPVk191ZegGBfyRxSld3JSxiBLORUpo8AHEoeOPpY1YTWe1TdmDVnpJN3HwQ0kZD3NnVOxyH1Zb3aeJeHFoLiLtIJyX43yuAJbkimraBIyzAXLA5Gz0kC5LuKpNW0/w7KQqXT6NaZVIp6y7Q58VNF+sTULiGI9WGAm+F7INbqOYAAdecDYKR/stecpM15BFCMlSOEnkEXpfTWI3f+tFdPxm9wHloAA3v5ZpikBLOZvwymwWxrUG5v64YIi0tNQ5yVZS4toAAlXm0eVADMcLABZKk8V+VnKGnQ6d3d3bazeKmklK+9Mjg/Gp9OxbrWN9kLEkcqTWcpFjJOaYHkZDg2jaPe1p42087DepP/fl/rKnUfAJ9HJIkzVtSLlmody0/u4MV+UtgzU2HO9713LjpQLSfrw4GMOlyxaLuXj4v6a3A0J5diPavfQdjpk36W7RrQ3cL++zXeLoxzUvtt6rtLPvVL3BIjVDb41lGv5g1GJ5ZnO+O68vL/3Au28HNmIp6ookvs6kgonJdryWg4Sis1fYipeDIMAsjr4rapsozg6GsvmGG9VMTeqiin/I6U3wnlcjxQQ5L9y8RpZHh6KGmm5XNEXr3ZylCauLJcWLJfL/wF345aZ
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Disbursement Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches a list of receivers within a specific disbursement using the disbursement  `id `. This endpoint supports pagination.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}},{"name":"page","in":"query","description":"The page number to fetch.","required":false,"style":"form","explode":true,"schema":{"type":"number"}},{"name":"page_limit","in":"query","description":"The number of records to return per page.","required":false,"style":"form","explode":true,"schema":{"type":"number"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of Disbursement Receivers","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ec3a57c0-5660-4b5a-af76-acadc7b09b93"},"email":{"type":"string","example":"receiver@mail.org"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr129001"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"},"payment":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"}},"title":"ReceiverWalletLite"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementReceiver"}}},"title":"DisbursementReceiverPagination"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-disbursements.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-disbursements.api.mdx
deleted file mode 100644
index 2aa61d6b8d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-disbursements.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-all-disbursements
-title: "List All Disbursements"
-description: "Fetches all disbursements the organization has created. This endpoint supports pagination. The response includes basic aggregations on payments within the disbursement."
-sidebar_label: "List All Disbursements"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWm1z4jgS/isqfbjdrbLBvIUMVVtXzEB2ckteNjAzlZ1NscJuY11sySPJZNgU//2qZQMmEEgyma29LyGgfnm61Wq1Wrqnhk017XymPa4nmdKQgDCa3jg0AO0rnhouBe3QEzB+BJqwOCZBmZSYCIhUUyb4XwyJScQ08RUwA0GFjCKuCYgglVwYorM0lcpokrIpF5YcSYAo0KkUGggXfpwFoMmEae4TNp0qmFpCTaQgKZvnWu+4ibiwystwKtShMgVlOU4D2qEDrk03jjfNc2jKFEvAgELj76lgCdAOTdkUqEM5WvwlAzWnD/2AYJGKKPiSgUYbqUPxC1cQ0E7IYg0O1WYeo8BQqoQ6FL6msQyAdozKcNSPIGG0c0/NPEUykSUTUFZZyLLY0E5tsXA2YI1jnnCzH1wPQi6ARPKOJEzM0atZbJ0Vx2SCmE2mBASk8NzS69/HhLpXtuHLfuhdooEpPyIGVEIyDQExklhaYiIls2m0NdkERevXAK+N4mJKy3i1YSbT+0H3vzLfkIQZP8LgRHw5G5HhztB8JZwOBZEldtVedU9G1KFX/W7vmjp0OOpejfo96tDL7oeh/efdxdnloI8/3ixQA0tSqzJnLVlcrNkxM2MWGjuXe2y/EPG8CKithMAMYQqWSYBYacRgJgiYgQo5kSphpkOur6+v3bMzt9d7xTks21j3vCPXq7le/RFDJxBKdWDJP8PSXNw/yFQt1YGcccIhDlYLDuk3jXzNqF2lhtIUlILZYnbKYzflFRlwBb5FvT8JLslIKJU1iIvppk2vuhTXRjHtl6zJvyE2NOMGNebZVqOUuufhx8MkGHNtMHmUtysSgGE8xpnwpTAgDHKyNI25b/e56n81st9vg5ST/4KPLk4V7oqG58rXu+9hWgFfzc4MtIq8f+P29HPjX+td6meMQZoqmD2Fs7bNyaa58oKVCwNTm5BWvMcLhxppWLyfrHa0QEJurL7Ltd0LhwbMlH3FlGIYTdxAog/7hQe7g+FhsZAJ/iUDwgMQhocc1K69YcMrR7U3ATtutd3jdr3lNv3Wsfum0Qhcv1b3WLN1DF7YQvz5sngKBqQ8qHYj5M5R9gJj1gc+AzVWMOXa5HXVOAGtccoMJGnMzBNR+Jk2MiFLpnXOAYEVyYybos4zkiz16rw8/LNYZH+SQjXhWvxgVgVNhZzm228x/IMmxVIh3PygSSq15pMYUDQLAksayjiWd5gbVohmTHE2iUF3yP195aJU1KI/FgtyF3E/Ijwvesvj1mGoM+TTTOGeJwKUcVVy24CL24cyYi5uyRQEVqy4f8zJsHe5coqRRZmWO4P8yAXxmS42GK6JkIakCrQ1dMMDTm44y4xMmOE+i+M5YWkKIkB0xtKCCH6qbATBtcxIxGZA2LLUJneM2wyK2XQuMxIqmex2T4W8i7l/+4jddlbxV1CVPLRKEYWzxXwzzqPo8Xqnf9Y9HWB18/7ivD8+/3D2tn9Fnfzncfe8N/7UHQz6o3G317vqD4cPKHdR3KzTQxn0uxzQCHEsHHrH4hjMS7PC2r8tFrA3ELTcZqvF3Gb7uO4yD8CtHXntozZ4AUxq+9b2WtJHPlFMGNLVmmuDPJFMwB5g9vJFxqS6U63Ocn6WphVfJsivIR3XvLEfcxBmHMiEcbFfFku5G8Cssi0rAEjHGNzjPTXsAUxVHaQoHuWVaoIdkkJbZGGJwAy4htsyolwa1Ruu13YbtVHd67S8TrNVOWoe/46CszT4HoJLm86nPHQWDmVav0YMhSEDvzlpuM2jiec2g0nTZU2/6R75jZZ37LXabc/uD74tXw5l5i6CIpa2rOTDsPcOhXCtM1BPFZNTY4pVoPWGwF/evu0126cnR4NPv7Yv22e9/sfhu09X7d7lh08fG+fXjd7ot/7Hk0HzvDtqdn973/h9MDgZdFuvNPt112uMajhDnVbttWZ+W2gAMXyj0KNCaKsQuti1lw4NxDFTxIYUWQXSMubsbNg1nZ9iX+0EuVZRLheGuZaFQ2egeFiUpeMQjxZ7dXdH/fHFyfjt6dXoPXXodb97NT67OLdfLk/PqUPPu6PTi/PuYHzaW6b7EoiPJXX2ILO2eRxxbaSav7zCyzSo8aHF2AgbrdrkDbgQeKHb9ELmskat6daa7VZ70qwHLE/of/dEYHBpw5L01YJ7sU/l+9zZfWHUnD6FEolCHsP48E5XrljdECau13ARYsXXr7U3/E3ZwR5Yxsse5s6Ty4Oljgwkb61hAb9iLR9xvC3JY10cEp8pXme+D1qHWbxT0/G2opDxGIIXqMoZdxu0rUYBFiPo++drWvE+qowlMsOKp4izJx7sLESS865OVQHRkoRs4wxKjz2v4nnrAMh5XqDFSOzirnGWldS8lRY2A4XHs+foKXiWmlJQS3c91GKVPLLE6eKxkfLR2xI1vdp2A+SDYJmJpOJ/Weteqd0BSskdJYxtnxnFnrAVbGXvotu9cGhx3trVTF6UG3QrGPRcGrJh5hrFUk/Tq5UkP+T4noLzqWlsT82JVBMeBCC+/7zstm4N4AkE1g4Nfqa4mdsbnrfAFKhuZiLa+XyD/bgETCTximgKFhvDIVp92P3UoGbLa6JMxbRDKXIvhQ/R2Nyesop10ZHyX2G7S/mfT6O8AYLHapwCbA/lfnSI5lO8pcE7LsIE6Q/rrSOSKj7DJsUtzPHMXjRFu8XssXJjNAIWYHRi/S5CadEUa3JZOG50ey5jZnBLI93LU2qLOJ2jrFdqFQ99kCUJw1pqo/jcLePHYe/yJ2xOMGKkjMkk47GxZpZvCW2XJ2G3QCZZfLu+18MGDZkqmaV57vZ5yu2AnNk7hLV2AeZOqtvKznT2z4L4h/hDjIqWDRNEpiBcLTPlA0mVxLWRXyVwXUDByySZLlt2D8Q5trmEA3hqIz4TuCuEMhPB8hZq3dtSkErNjVQcdAdxuOSzzuVVi093o8BKCye5E+bfgghuflyezqfcRNkkP5k/R8JPnfwWeAVlbptzjIu8B1aQWau4CBXTRmW+yVRhIM6LOTSnlWdYFiqbv77FtKWIQ7bdwYQsaV9sTQRx4voRU0bvhVyiqxoFUMXCp1r8sNeeQ2a8hzghVpDFH0Aay7ltnR5ca5lGuttsAkqAAV35A9MU3vLqi3AIasb9cguogFmRalq1RK4MXV2QOTTmPght0/4yAabMj4DUbZ7K8zPK6lSrd3d3FWZHrbSCVVcHp+/658O+W694lcgksc2TqdQmYaIkGB8OkG4ck4dPBzayzf16M/x/eiNRbE4GvppqGmOjb1F4777YCD/TzY3wBhuM2uDA/f2Eafig4sUCf86v4XB7DLjG9vn6Tu1RV+1+RrET1S3M1y8zZizOwG7BznPUfcvDiAOgVu8yXgjt2x4+7AH35eWYnv2uYQ+M1TuKF2J59XcGe7DueAHx/VE/8c3A02Cv3jO8EPcTXgPsm+v8tcFLF+nTLu736C+/EFiDuMEv+cWeLf2dZX2MKStn7Po+pGXoW8eajQPDL31s1LGtQv/WFvrFPyh9OSTmJdkPS/YcAv5Ff+1kub/PjxGLxYo+H3qUozBxSY1eulksFv8DJt+7Aw==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Disbursements"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all disbursements the organization has created. This endpoint supports pagination. The response includes basic aggregations on payments within the disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"q","in":"query","description":"A search term used to query through the disbursement names.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the disbursement.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"]},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return disbursements that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return disbursements that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort disbursements","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["name","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting disbursements.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}},"title":"DisbursementPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-payments.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-payments.api.mdx
deleted file mode 100644
index 38f44e2d40..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-payments.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-all-payments
-title: "List All Payments"
-description: "Returns all individual payments matching the request criteria. This endpoint supports pagination and filtering on payment status, receiver ID, and timestamp. Each payment has details on the transaction itself, receiver, disbursement, asset, status history, and blockchain information."
-sidebar_label: "List All Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJztGmtP28j2r4z84WorxcHvJEirq5QESguUkgDbdhEa2+PEi2P7esZQLuK/33PGduKQ4ARKpV3p9kOJx+d9zpzHeB4UQSdc2f2unNL7GYsFV65ais+4l4WpCJNY2VXOmMizmBMaRSSM/fA29HMakbREIDMqvGkYT4iYMpKx/+SMCwL4gmUhbZPxNOSExX6ahLEgPE/TJAOslE7CmCILQmOfBGGE8EAFFkrShAsqct4Coh4Lb1lGDgctCS3CGTChs7RNhtSbzhGmlBOfCRpGHOmgQCKjMaeeZBQKzqJgQa9F/JC7ecYZYgNpzhn8KdgSkFsk2X3B0Y0S78ab0hCoxEGSzaTobaWlJCnL5MOhD8Y6AqR+FM2t2VJSmtEZA+XQzA9KDA8AB+ozeBmigcFi2b3y1OxjEB6hKpMyH7nhQ5gxYBXQiLOWwsV9hARRJnjPfqRR4sOCyHJ8603ZjCq7D4q4TxEszmcuyySzgOaRUHb1x8fWXCwJ1SwWQJAkmLv/DWTiAh2PgCAdxqIP1DyBrGvuUa7qgqJlrqNwFopmcQcsCGNGpskdxGl8D8bkoDUndyFEs4vGxeBmPni1jF+eJjFnv8bWhlbXoYizZvmHPyB2iy1WRXQZnuADIUNE+uEt5F3xw+Csvz+G57Nhf/AV/p4OTwaHJwf4q38+Gg7gx+h8b284GsGv/f7hESxdPSIj2JqSc0GhpnO19a5Dv1nx8/PDAShIBbgkBa/IVEMXqaD0l08FdSlnb6f+kvyu4zpOh/qq43mGajleoPZc1lFtR/cp9VjHt7p19byMUdip11Rc00BI5zfo+DmO7ssIXKRTqTPNGClpEUkIliGNgrasTfZl+tklX+GfenysDga/SHtD0xxV01XNeEZHlwH1DQljOyULSn8jLTlUqWbF9kMW+STnIL1ICML/kqQ4Tx41w9f2aG1xKUEWORQlbc6PFRgBuaQSWIMrPd40qywUodyraVA8oViowRVyLHIwRyrgHfyzLHW/ah/A9hFU3CcFyUtigRUD8GiaRqEn6/POXxyRH1ZFTNy/inqTZljNRViwXrQom2Fj9kOsTaXzMPs3lqzfzX8tKtfvGHBAh91ug6mvYsIzr6FCf8UmMufMcbsAJhJBo2Yw3XlEwFBIfqcLvWEVM2wNm2YZxTCC9m7GN9sF0nyjbr4fGEZg26pp2D3V6hqGSi1mqB7TdNO0er1OYKEUdJbk8VoLr3ZNBeyTArnEVde0NsTVIwYziyKaXdfaxOv1Mq/ygQJV8lhqMovCNCoIk5iJuyS7aZNDaIppjD1HkTLCBNG8m7qQzyADBu7K79XyEXUT6DmhOb36bSpEynd3dqL5WrvUqZ1kk513LQL7usIc/kDXLJAqSCbXd961l6ykuabZ83Wv2/NN3dK7jtvVrY5n0MDyerTHfNt1fdfzoT7Srq+bXQfgtY5j9Vw0rRdmXsQKywZQ8cs+dmvz7kl8UuHPR4vDgTRmiC0+lJayOSB3UxYv2fKO4mzis9J6BbllDTsWdbquQ1UzcDqqZViu6nZdTWV2z6R6z+9YjlmPknmvv1YJCShbuq30W9vH/WT31VL2+id7Q9mI1Te0pD0qhJuLeV1OOGt295N0CzPaZJKxyVLChaGGYnIgxdbnBNMuDEjVKFgwYbyY2HCXVFMbYlfu4nNDwHQVQ0IjieflWVaMO1tmmX+W2cEKHMe/dQE0t9E6ZYq5E7MmOEJFUGW5kTFM6GJUzRzr2q5l79r6N2U5sdcE+lA4fxgLiIANQLIO1GexV+b9VW/kcQi7moQ+UA2DELZ56ZgldjXV81xODgutPVt3qe7bqm34pmrpRqBSu+epDgtMw7d71LXkHi76om1kQshnxKgVrtoL9a88ZqrRa84AzwXYaNw/G8sgmgfY3ufj06PheDmcBjWOi5iq9X9bKSfhsU4t7cYmizcFm6Oa2ljTdw1j1+60u6be69jfUKw89V8kVkQhqRRIby9Zt23qjq0/2Q11ex5BopFtBp4A/XxXEwSUeZYL4ehANbF814KuxrNgijRtravZnY5mS+fJxnmTffooFJGwdSbno8EeEgk5h9Z+WzIFNKG+D3WTLxE8eP9+YHUO952jy0+d087xYHgx2rs86wxOzy8vzJOv5mD8ZXixf2Sd9MdW/8sH89vR0f5R394chq9KXJuC6JVEfRaxnyTqlETtRYpdjeiqWZMhReaBVEWf9AbKMz8RuaNR9BbB19VMzdR9S9V9zYKWutNTXcfvqb5nO5Ye9HrdLqsz/nmOmtFjBvM1NWCuo0Kga2rXtTqq1jUd2rU7lk6Npa13VrKutt1bqW5DQ4J9qWrZNlWtThemCY0xVXegLe0wzWeu3lQLFpQuQhf6TkHATVACEWeazFi6tmzX8arO+rbAh/Gz7SWzJeUvpbKV6lVrWW3IRuoHe3/0P5p/fDQvPpkf9z+YX44H+59Hn46Nk+Pjb+9Hn82Lw7EzPD/9cjkaXBofO9axYZ6djY4279DGfQOzkrbFhtyOxssL5Nnw4HA0Hp7J0ggJ5+BguTBW0cQLy1a1cU28LZv+n5KzVpszWFtdrI/t8r2l6atHJ+cxzcU0ycL/Mv/tjkpYliVrSpA8Z4MB7jUtfHl6DiSe75elmnPzzcVQThJBltRcSFHxAePUKD/F+JWEC9eYq67ZTzI39KET/vV+Wa/dQoAtAKQenMGsFop7+WnrPaMZy/qgLDxe4UkejIjTBD+LTZiUjeIrZad2VMdZdlt9GsuzCN4qiFjRHaGehSp16ot5NQ0/sdWB9ePluDhlwUNNtD5OF4UJW4SHE/zgcxeKKYymZDgybIekWXiLvecNu8e5szxE7ZeOo/WD1CmjPgYmtl5xkEhpyp1Y1fx6a0lOIypw35P+6SHQQHULKY02ZEW0QT6bURzDl/qG9TR+Gw1O3+HZByUiSSLi5mEkpJpJNqFxKSrHE+kZvWHwPrqpHbsngDfJkly21tAAhGkoXyS38hPD6rHV2mb97yXin/GfsfzIjCxjAuEfqzzJMw+m+yzBbVF8boDXhSg4/CTz4eIJudb8uAIb7urILkhyWC0/wAVJFCV3eMyRsTThIUzIsN12UQ6VfC8LenW2pi4NimlpJNWl3g2L/cVR3ATCMXexWdh5EYV3u8UX9rko99U5DJfClmBSKwhXSFYiyz2RZ6WC6BexyaftF2gWZDJ1/YxqFYlNut0xl1Swr9ZmyqKZ6k1pJnijyDW4HZExtjMDOXbKhUZ9NqnxASgTSUjK77M0Su6rU7TmvVYcbd7kUCkhfhkH1XDGYNmMfw5GkFtDr96V1k+GJZCaBCovwVoKlBkWc5nxqwSYUsjAxJB5qsjPSAtI3d3dtal8K6mVqHzn6HBveDIaqoDSnopZJPMk6C1mNK4RxnsSpB9FpHZTYinRPCxK4P9voDTfQClroYBeZAdiLpSfbaSzHsqS+11Ja9d7puANXHt4wC/n51n0+IjLxQdCLMQgE3Wj2ie/Zz2z/pLKWoGgsirzey+3NMqZLPatF7FbvXzSwKu8zPJKXj9zc2SDAeYXV14p2ksuhTSIMr9/8koxXn5Fo0GY5Yshr5ToLS9UNMi65pbHLxV4y8sR20k8v7PxSpGbrz00hVtxo+K123HjRYUG1vXLEAv+V/gAFcLF3v07XlwqW3vMgQVi3/NYWpd6ZRhbGnMOhnhuQVdmlBs5o5Q/kHr1Kr6v0X46bRQi4P9oqrUoDw/FBAQZvIIvXj2LUapYQaOVrmCU+x+N7UfN
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns all individual payments matching the request criteria. This endpoint supports pagination and filtering on payment status, receiver ID, and timestamp. Each payment has details on the transaction itself, receiver, disbursement, asset, status history, and blockchain information.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"type","in":"query","description":"Type of payments","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["direct","disbursement"]}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"status","in":"query","description":"Exact match on the status of the payment.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED"]},"example":"DRAFT"},{"name":"receiver_id","in":"query","description":"UUID that represents a receiver in the database","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"b6b667ad-6cc2-46cf-9be7-561daace7d48"},{"name":"created_at_after","in":"query","description":"Only return payments that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return payments that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort payments","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A paginated list of payments","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"}},"title":"ReceiverWalletLite"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}},"title":"PaymentPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-receivers.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-receivers.api.mdx
deleted file mode 100644
index 2d27461f6b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-all-receivers.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-all-receivers
-title: "List All Receivers"
-description: "Returns all receivers matching the request criteria. This endpoint supports pagination and filtering on receiver status, receiver attributes, and timestamp. Each payment has details on the receiver, high-level payments metrics, and wallets associated with the receiver."
-sidebar_label: "List All Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWW1v2zgS/isEPxx2cZYtvzsGFndu7aRpkzaN02TTNjBoaWSxoUiVpOJ6A//3AynJlhNXzlsP+2G/xJE0M3yeITlDztxiTWYK97/gU/CA3oBU+KqCfVCepLGmguM+PgWdSK4QYQzJXAxFRHsh5TOkQ0ASviegNPIk1SApqaKzkCoE3I8F5RqpJI6F1ArFZEY5MYYR4T4KKDPyfIYEX9lGShOdqMr6BdFa0mmiQVWsmqYRKE2iuIpGxAtRTBYRcI1CopAPmlCmjMEUWWqjgkI6Cx0GN8ByeYUi0JJ6mdU5YQy0QkQp4VGiwUdzqsMNM1VcwSIGaSkc+riPj6jSA8bW/qvgmEgSgTYP/S+3mJMIcB/HZAa4gqlx6fcE5ALfdfRZCMZBK3eCb4YzD1SCj/sBYQoqWOkFMwYDISNcwfAjZsIH3NcyMV+9ECKC+7dYL2IjxpNoCtIOFpCEadyvL5eVDVgTRiOqy8ENIaAcUCjmKCJ8gSSohGmF5pQxNDWYzSoBH9Hc8SoWXMGvodBwixy+l0MfIAVEeiHSICOUKPCRFsjKIh1Kkcw2JxnFoeAwSUetIIgIZekSORy+BB2lzZLHRQbpki+nMfpBPJ3uu3x1p2pIBJv405X8glArGHgSmTgxPB3sn+EKPh0Nhpf29+BwfDY6HQ1xBe8fDQ4ORkN8tTSWSRTboVKVAllPgtldE6InJNB2Yktof+Bska2uQvjRIdGISECZMWQtIW3Cjk80VNG+kBHRfXR5eXnpHB87w+ELTl2RX8N1O45bd9zGT0hOIRByx95/IMvU1N+IphJyR+DYp8D81a4z8muCL7lCV7Gh4PrCwi28vCruPJ9K8CzU8vCXi6FASMvCZK0VkRfda2smRHkFCumTwWUoXJkR0xirjJWG65qfu6Evy7jgI0aVNqEiT1V5qsQV7AmugWujT+KYUc/mt9o3ZYzc3ocqpt/AM96NpcmGmqYQ1tl9tyyHH3proFktuP+Y1PRH81/rDPWHWXo4lnDzEM36fU0ySwfPVCnXMLPxZ6XbW1awFpqwcrF6Z2kEqbbjnax5LyvYJ7roKyIlMeuJaojUbr9Qv5xb0GtOp51mz/F90nJadeg4Pdfbc3y3CR0Ar0EgsFwLOazc4r/r7Xa70ez0Wt12uuU1SE7YZBeURMl6o9lsWSWTJMvFv/kC/mvEqkLa2FLYkqWKDbfRdNyG4zbP6m6/1e6361XXdT/jfK4m+YFuhx2joBLPA6WC5FFaAaEM/AdquEZDGo9wymePU5pRpUGCP8lOo+VK9VTJ7md/QiKRbI7zyLVHlAI98WyQKhv203j42oycylOlkl1r7ODVq2Gre7jfObp41z3pHg9H5+PXF6fd4cmni/Pm+8vm8Ozj6Hz/qPV+cNYafHzT/Hx0tH80aG/ht8Mjrlt1XVzcnYNUzby679QX3p09t+k2637Lqftuy2n1unvOtOPvOb7X7rTqwd5erwcFTvL5I7qNPWiA7zoBTDtOy2u5Tm/a6jpur9khvXa3VSeNDXfk4f+Iagsl9cnzgbSJT/bAbzutdps4rW6v4RAXwKl33G6nC64PU7tc07xbZumcTiXhGg2UokobnVBEYO9PpXqh1rHq12o3qT6J46onog3yF5ZsTl1pYIzICfF9CWrHXjt4/efgbfPPt83zd823+2+aH4+H+x/G744b74+PP78af2ieH551Rp9OPl6MhxeNt93WcaN5ejo+Kg4UQSS2HrOKApP06xaplwiYSew/2wblN/RRNvbu22BE6UkESpkcrYDrn1jbPM+sbv5oHsLmDR8Zi/mTjwhHFmZWbJiKRKfH5my9b8NZd18gweSikxzK3ym9/JMpHpgpsgv5s2/C9+OuSmPQOB1gNdQkpEoLuXj6nPwfIa+24bbRAnsjNVcrosExors22+etCWpj1Depd0ZcywVebhNPpbd/2/62eGy3Ai23fv8K9YmTRIdC0r/Af7mrEkgptuyE9PgtyVOmOzvrLys4C6vbSk7L4p1+BQO/Fxpt0FyjyMdpufWC5bsav9JwOjXN+1OzL+SU+j7wXz8v29mtATxAwPJQ4CWS6oWtDL8CIkEOEh3i/pcrc6OPQIfClJVnNkXFxHzCtWLBRIG8yUvLiWS4j7HRzA2PDdGUS9H8OqjE9B3cr2+8vThLazSmvGHcD1xnPqwgRWc8r4YTjkbjRruDYklviAZ0DQtT/cjKKYNs5kixpBIC8e0mNM9BegLK9uI4PfigIVXTRCqwdfwTRrSJImhwcogr2NBNUTaq9aprfJBEETGx0tbMy238Nh6e/I6oQgRpIRiaJpRpS1PIGeEZVGWKUxG5BjRN2PW6Q6AFImgmRRKb0okEj8bUfhA3tty4Hp2Dngt5Xd1a1v97QfzKv3LboDFDciRi4I4SifQAxVKYfZFWHqnKoJhys4jzOvMdc1lPJgRkzgPII9z0AwKRcD+vUweCMTFPK2axUFQLSUH1DQ4HfckOv7Xs1/ELTnLizEnOlHjXwP2r3/Jj/ozqMJmaI37tURZ+76fdqRWUBTLBg1Dj4RBQJmZZUR5IorRMPJ3IjKCZF71rTquPYBZIG7ueQy03sYvbHKYol30ymxBY5HghkVqVQi7I1bQEqJkjay17UcpnF403wCJkDVn8PsRMLPJmZPleS5SRu06mIDloUNWvJkyZzpD6EIxB3lCveJfMYJqSVc0KOSJwVCZWwYx6wJUN+XkAjIkXAmrYOJXGZ2OrX6vN5/MqsV+ttUxV1Y4OX4/ej0dOo+pWQx0xGydjoXREeMGwaTSiAWOo2GrciDS36yT4T9P2TtM2y34afuhazAi1lVo7PbdZlv2C11n2ypQclDYvb2+nRMEnyZZL8zrtDpjc61NFpqxQ7v/pXGzv625FdA2Ldav4hrAEbH6vPGa453Rqd4BaNYqfCO2lO7ElcL8/HeVTGq0lSFa93SfCedEGaAnOLW3ZX4v4gc3Mh0FeNVmfiHlHm7JsftMW6FN36+7GYsnYxe7lGsCVeZDUILAXi0p+AjdxK1UceB7ERdj3Lk0b15GDkakbkHtXiWt7lcj+MdbzT3xRsH33UpBCMH+Nr7aq3N6mF5XlciWffvqpRkYxlzZeuloul/8D/JOeXw==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns all receivers matching the request criteria. This endpoint supports pagination and filtering on receiver status, receiver attributes, and timestamp. Each payment has details on the receiver, high-level payments metrics, and wallets associated with the receiver.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"q","in":"query","description":"A search term used to query through the receiver phone_number, email, and ID.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the receiver wallet.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"]},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return receivers that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return receivers that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort receivers","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting receivers.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A paginated list of Receiver details","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}},"title":"ReceiverPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-api-keys.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-api-keys.api.mdx
deleted file mode 100644
index 017ab5aad9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/list-api-keys.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: list-api-keys
-title: "List API Keys"
-description: "Retrieves all API keys created by the current user. The results are ordered by creation date in descending order (most recent first). API key values are not included in the response for security reasons."
-sidebar_label: "List API Keys"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV01z2zYQ/SsYnuyMKDrux8E3N3YbN5nUE9mTg+PxgORKREQSLABaVjX6730LkjJNy19pPdOpDyYFYN++XWD3gavAyZkNDi6Cw9MT8YGWNrgcBSnZxKjKKV0GB8FnckbRNVkh81zwujnWicSQdJSKeClcRiKpjaHSidqSGYszjBiyde5gZUhok5JpFns7IIsU5kLhCW9UpqqcNcvETqGtg3nCeFNlrNsdd37FtcxrakBL7WCf5HUKZAC5xmmlS0tiqo2wBFbKLTEqLUbHwSjQFRnv/yRFbB+VdUD2gY+CzhgJWQX7e3v8uJuLTfSmTUoqbJ0kZO20zvMlMBJdOvBmU1lVuUq8s+ibZftVYJOMCslvblkREKUxku2Uo8L2xnX8jRKHicowZacaVirtrbHgUM6C4Yadl+rPGqlNwUNNFTLKyeDstPSD9SgoZUFPQ72vC1mGSF8q4xwZh9E2MBAslLWwsc8IrfW1HjrjzRB6KnpoYmZkyafMafhUtu8Up1EvKL1S1b/htEUTJ6dCpilOAo4BzqN4d3L0WYDEDPmHMd1Uyiyv+Oxuyx5yU0hsfsALQqeQ46HDY0boVQB8D7LZVtaVdN/p4ktGZR9ULOSmXvsO4uUzDhPqWSwyvan3Adm6Sl+BbC6xKy1038uLGPdBhrR57gq96nWIW2YNL065nJq28YH98t8o+HHv7f3Ocl7K2mXaqL9ge6eNvInebO0cD3QIMkabrQefbpyRz+gx1klX99eVdRGTYYgCdSFnW45+ExndyKLKqUcj+IQmfSeyWxadH+Sjhzy0aJC39dLX8ua36If7W/SrNrFK0VVfZX+2p+/W50vScMeK7TolhNKvgl8I6mkOETR+Xq4vOR1IAOvhjDxhyVNBJCsVzhtpRE1dk7HevjY5ZgM27HAnHHwTXx/9titXigtgWEK/fznzxeI1hXeBFasJbySsmpWYWiiXCVmK48n+Tz+Lyqhr7pqgxWreqFhw2G6gt+Tmz+AZVItP7Zp/T7Vn09bjxFGeSyOOlI1rY0EdN43TXDoue65nYHC4Dcv98dvxHuegLgppkMOArzePY+xMjk53BQRLQrp0LuJa5c6Hqc1Mli1Vy7pWyDlhPp+LSi4ZxY9KSJ+uK5YH3IRUpfyEBivfczrvJbmFNvPxvdT+9yh+Lb+WZ6zh7LIUqIkytLo2CWFXNdcKzKTj6YYKFNLpqhPIAdwIGE1XT3SKf0CM+W5SY1Q3fXmqWdP5Xmmo0lY5HBGyB8wjFBe2wYvaZ5j2khRWbZLCWCZzXE4vdzLnKnsQRTMcxzoeJ7qIXoSweyB88BsquAmjh0jFGQbZdpmPCscVTcuZOnG1aQPsbl2P7un4BZFNjW9h/yS0DuKp2BYUi27td0eTUV6ESSaNs49S7q2LnCGKCvCI2oFH43kqjPdAFh7I80+pyvWSj9eTkaDJ8bp5DRnF+SWL0FCxDhdd+8d0gt6qEu5LXVgtzTEKMfKLQj0NbbsMlxc88JnCHa1rgJVEBxb7vk81/ZmxALVYLMbSz3q01tRGH0/eHX+aHIcwGWeuyH2fRNwOF/4esL8eb74NB01mdSuD/7OvxFa2HK4PEY4H9GTd5nXVquNFsFFH6GAGLjy2WsXS0rnJ12sexmcY68UFXq+lUfwN5SV31IkTyynfSLGD+IqsWHw9dS+ZA6m/I9S/HZ9hrbynsnOvsu0Lo3dT5bKHPdTLhkJzNX7AZLVqNByBdeubqQct2hC71ZzDS1xG/gZb8Mig
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List API Keys"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/api-keys"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves all API keys created by the current user. The results are ordered by creation date in descending order (most recent first). API key values are not included in the response for security reasons.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"API keys retrieved successfully","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/log-in.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/log-in.api.mdx
deleted file mode 100644
index 971460fdf7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/log-in.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: log-in
-title: "Log In"
-description: "Allows credentialed SDP users to log in to the SDP dashboard with a password. Note: all passwords must be at least 8 characters long and a combination of uppercase letters, lowercase letters, numbers, and symbols."
-sidebar_label: "Log In"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV1tT2zgU/isaPbWdXAjby+KnDZS2pkAoSQsNZagsn9hKZEmVZIzL5L/vHNmhoWVhuruzs7OzT9bl6Ds3+XxH19SzzNHojA5Ln4PygjMvtKLnHZqC41aYMI3oUEpdOcItpCjGJKRk/PKIlA6sI14TqTMiFI58DmErZS5PNLMpqYTPCSOGOVdpm/bIofYQESblzZojRek8SYAwTyQw58mvhOfMMu5Rg9QqI0ylhBGui0SoYCfRM1IaA5YzB0SCR9kOkbr6fkmVRRIGiOHqItHS9WiHagM2QMUpjei+zmJFO9TClxKc39ZpTaNryrXyoDwOn/Sf4MfxHAqGIxQVFlIMIhRMSNqhK6cwjL42QCOqkzlwj3sWVXoBDk83J6LrlZjzVqiMLtcw7tq0wJnxPGcXXi9A/SjzffomKEZm2hILO8Ojyc6bIblkUqTB9x45vlkNgEQ4snKMlEqCcyGtn1/G4+H2/u7F8W4r/5lwrWYiK5so4kEHPlwDW0KPLpcdClesMBLW/KVznatUw2847XFdrActokXtgFvwdLlcLjtrIZ4x6SCsOKOVa2K4ubGBn9sOj97SznremDGyvdz9udPqdhLvT9IfxPg711opCvVenrzmYiT2Xr3/Gg8ORexidfyM78TP44U5/bCzt9WDem/ANz/U8dy8iAu5iOdapKeHkouBme7ELi4++I8n0uH69GSQs5OrYfOtyo+bWz4WleDFlpueHoiR9C/i4lmenLxHpZP0dFtyNTV8c6uO1SCdjSsxPc2reK6vDud8MJp8rEeTd7/M3vWeTudb9fYpz7uifPXxVXfBL3bzN0dXc1OZC8gORvvJ6PJpMn07Ghy8uuTFbjZ9diBP3wwuBrPpLHt/xQ63+cFOenzw/OD1+MtbzavXavh/ZO6JDMbm6V03dpul5LipO3/f1QVrtb2zhMCVt8w9jOA88+W6XFNJEaIA51gGd/0Z3//2jRk0VqHorNGIo+umrJQ93dhYg785hmSjWAFE2xvioP+wrqDuqst1ChmobssU3USndRflaURx3KgC5YRWSLDXdAE1je492aGXTJY3CMtztMvnGkui0eFaGOZzGtG+1JlAonJgL8E2CkqLlTUcc8BLK3w9xmvS5HEbmAWLNL+WL2bEW6h/YIu9kwn6nwbCYLc6gw5xIlOw4nRFdsebz54TY8Ul80AWUCOrtoFAbdqKr01P0aECwXNgKd6fJc5nOlgjPOaOjj1IySx5KVxSWgcFKE+OJPMzbQsyPIoxRGBdY+Vmb9DbwBiURcEsBneCnce9GI/GL48eI0kx4rWWJCmF9MFNbTOmWlNDQ1OwBZCklAtiWI0oYZWRzOrSYONhgQsjwoa+BNv0Pa12Bb7SdtH7kYj/dSZ+Up/UJBcuqFREG1Bdp0vLgRirsSYQnzOP240pGru8AH8HXNNg4Qbec8KZwp5upkuVhoM5TrCXFCojFox2wmsrwEVoR5ecuQav33676VqQuqYNUjdhfAEqPX+Ue29c1O9nwudlgq1E/6cQHkckOH9jSo0NjWdCNR1PKxa8EmpmmfO25L60rYOYF/9QTns/4dnMhsr/V1xbQTzkWwUJWcn+aW9ykEUXG3Xv7jV5Ta7vLUC/YEL124V7/XnIjTcgi/BUaP6SFIzUNV6vBz0hpUO5RZmAVeDB9T5hmfJgCzeajcFeCo51aeVWa2ZP26wfhLp61nWtWIdKwUG5QEKrAmgYz4FshjrV1GfEivr9qqp6LOwGtPao6+/HO7uH493uZm+jl/tChjqJxb9gag14X2ckvFRuVZe1l8p/9sHWMpeHK983kgmFnUgI7XXLjme0YcfzDs2RNaMzen2dMAfvrVwucflLCcgXZ+fIuFawBNnn7HzZWZHTN77eaQLanaDabwSNz8BlZyU05ByMX9v+oWW7xeVHo/GEdhqSj65poVM8Y1mFL09WBRJfLn8HWQuC8g==
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Log In"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/login"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows credentialed SDP users to log in to the SDP dashboard with a password. Note: all passwords must be at least 8 characters long and a combination of uppercase letters, lowercase letters, numbers, and symbols.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"required":["email","password"],"type":"object","properties":{"email":{"type":"string"},"password":{"type":"string"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation. ReCAPTCHA token is required unless the `DISABLE_RECAPTCHA` configuration is set to true."}},"example":{"email":"johndoe@mail.com","password":"mysecret"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Invalid credentials","extras":{"status":400,"message":"Invalid username or password"}}},"example":{"error":"Invalid credentials","extras":{"status":400,"message":"Invalid username or password"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/organization.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/organization.tag.mdx
deleted file mode 100644
index 9ce2148264..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/organization.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: organization
-title: "Organization"
-description: "Organization"
-custom_edit_url: null
----
-
-
-
-Organization endpoints manage the process of getting and updating organizational profile information. The organization's profile has basic information set at the time of SDP deployment. It can be modified by the Owner. Organizations can also manage their preferences, like which assets to use, through these endpoints.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/patch-organization-circle.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/patch-organization-circle.api.mdx
deleted file mode 100644
index 4ba566c4a3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/patch-organization-circle.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: patch-organization-circle
-title: "Circle Account Setup"
-description: "Updates the Circle configuration for the organization. Only account owners have permission to do this. Note: in the first time configuration, all fields are mandatory, but after it is been configured at least once, you can replace a single field at a time."
-sidebar_label: "Circle Account Setup"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV1Fz2zYM/is4PuzaO9nOctse/JYmuTXbrs3V6e0h9fUgCbJYU6RKgnE1n//7DpRsa2mWtFsf9jA/2DIJgPgA8AO0VYyroOa36rVfodV/IGtn1TJTJYXC6zb9nau3bYlMAbgmONe+MASFs5VeRZ80oHI+bbqRmSm8tqYDLAoXLYPbWPIBarwjaMk3OgTRZAelA651mMIrxzQHbZOpSvvAwLq5d1YGaAxUmkwZAD1Bg7ZEdr7LII8MWDF50Aw6QE5kD9pUAjIYwsDgbEEZdC5CgRY8tQYLAoSg7cpQb12kMTkwVZlyLfXnX5Vqrq6Ri3ocsz4qKlOePkYK/MKVnZpv78Xxwdixg5wgphCXKlOFs0yWRRvb1ugiic0+BDGxVaGoqUF54q4lNVcu/0AFq0y1XpxkTaHX1e/X1I0EA3ttV+p+cm+OST27voI1dbDRXI+SFMTH69eLG/gOfr68AfZoQ0U+qF2mNmgM8XtdftlJVxfgqnEhbdAQQ+VdA5uaPPXJj7YMsNHGSGyChGMnnz6+2lOp5uwjpYXQOht60KcnJ18Y9SHeEGJRUAhVNKb7dsFvKARc0UMhoU/YtIae8KuHu8vUDw8heoElvOkL7dv5TN47/3QSL4hRmwCYu8gpWb3iTqCxx/DkSQnXIQyHg9WVvUOjS9C2jazG5tJ9fF85p+bHZ7ngh2rIhvUc/UEmRw+WqAzDFUML2jKtyA/R3WUqUBG95k7Nb7fqBaEnfxa5VvPb5W6ZqU+TwpW0IjsZ7vUkd2U3sdgIPHnu/SSb7kmyki7do5qZukMTDxbkoIa4dsIsrTCLRAzFCzUbM+qsSBUz6StGiff+Tq6hHBu9UXOVjO1BLSTzfXLH0A7pwVb/St1nGf7l9xuIgcrE6hi5JstDUWUQ9MpS2TMEWrhcnP74E7Re3yGTcIdw5RAeOc35fVPJlBbjNWGZEpApKdA3R7q8PFbEgbuORTiimf3iTkxWLgHSnK7UgskY9HChQx59oIYsw7VBrpxvhN4k9uRDD/R0+v30RMIYmwZ9NzDU4zaeLS6un0vpIbBzBvKoDadIjTOVSq7BNUEezRpa7MRKWkVYeRdbYUFPhW512nB31HfQ/emWeOP8evogif63XHxn39mbWod0pAXXkp0EF31B0HonDABcY9+Qkyup6bX7PnDPXAZoy7QhFyj155ygctGWSVG6gzPGbbRdSed2QbPzmsJc/JjAbejtzYbfSTkK0qQdgjTJsViTLZfPauY2zGezleY65tPCNbOvsvB8Dgn8wZVOGJ1R235eGsQSKm0rj4F9LDj6AeB+dHo0p9OvQFb51A/+DbS9iaewbSiHvew/RlOTaSZFjZ7Doy6P5GbsiWYNajsbFh7F8xSMl2QaSIaS/yW1xnVSXk8igSgTI6xjTt4SU5i+E6Zj8k14XS3I3+lCeGkPa3Bz6vxqloQmrpqEQSxTRhdkQ6LAPYe2WNQEp4mneooXW/PZbLPZTDHtJmuDapj9dnV++WpxOTmdnkxrbkyi2tYFbtCODO8nvmE6XxDH9j7XbI+jxf+vANm+azJ94llrUFvpQCkn26Fd36oxehnN/tKwl5mqXWCR225zDPTWm91Olj9Gkv5zu5TRwGvMpZvdLnfZvl8eB4vzPiWTG/HmOEl8Nvntsr3GWVFQy4/KjieQ67Ob85cq62cTmWVdKUoeN/J6gxuZMuR9iPuJZ9uvbZVBu4pp6FW9USk8/GziWKeJY3gQWPst241cvD879EjkW3A9qLLd9vPMbneQ77f+VmOI7V5aErrc7XZ/Ai5DXfM=
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Circle Account Setup"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/organization/circle-config"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the Circle configuration for the organization. Only account owners have permission to do this. Note: in the first time configuration, all fields are mandatory, but after it is been configured at least once, you can replace a single field at a time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Circle configuration to be updated","content":{"application/json":{"schema":{"type":"object","properties":{"api_key":{"type":"string","description":"The Circle API key with permissions to POST & GET transfers"},"wallet_id":{"type":"string","description":"The ID of the Circle walet from where the funds will be sent"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Circle configuration updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string","example":"Circle configuration updated"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/payments.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/payments.tag.mdx
deleted file mode 100644
index e89ad4323c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/payments.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: payments
-title: "Payments"
-description: "Payments"
-custom_edit_url: null
----
-
-
-
-Endpoints related to payments. An SDP payment is an individual payment from an organization to a receiver. Each payment is part of a disbursement and occurs on the Stellar network. Granular payment status is stored in the SDP database and can be viewed in real-time on the SDP dashboard.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/profile.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/profile.tag.mdx
deleted file mode 100644
index 7f8a1db9f8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/profile.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: profile
-title: "Profile"
-description: "Profile"
-custom_edit_url: null
----
-
-
-
-Profiles endpoints manage the process of getting and updating individual profile information. Profile information is set when the account is created and can be updated by the user on the SDP dashboard Profile page. Note: profiles never refer to receivers of funds.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/provide-signed-challenge-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/provide-signed-challenge-transaction.api.mdx
deleted file mode 100644
index 2f426c9e15..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/provide-signed-challenge-transaction.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: provide-signed-challenge-transaction
-title: "Provide Signed Challenge Transaction"
-description: "Allows the wallet to post the signed SEP-10 challenge transaction. More information     [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the toml file under the  `WEB_AUTH_ENDPOINT ` variable."
-sidebar_label: "Provide Signed Challenge Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFmTo7YW/isq7ksm8QJ0u6ftqjx4bzw23jBeeqYSAbKRAQlLwrTp8n+/JUxv6VvTk+Q+5CE8sEhHR2fTOd/hURFwx5XGvTJDO8wFgwJTonwrKR7iLsNx/tlQmmFIUw6Ej0AKwxAJICiIKRf5EMc7gjww707KmgpcX1KQHQKCQcKhK3lUwIgyBDDZUhblmwB53fuIoW8/+ULEvFGt7rDwE6fi0qjKBQpDyJ6e5ZhRQV0aVp2QOtUIcoFYFbmUn7hAUZWjuKyqmlqJvP88C/CpAiwfAUS8mGIiQMJC4EIiJZTiOYkAmIOY0SP2kAcwybURNArBFocIJMRDLB8Dvy+7rd+aC+vut67ZmYwN0wK/gyNkGDohqiglhcboYjzDUxrK5MJznhum/SSP9WIPpaQwdEgQFy3qnZTGo+JSIhAR8vXn6s/ywV0fRVC+iVOMlIZCnT1yhVJSYia3ExjxfPYV2xdiLhgmO+V8LinoAUZxiN7RKk157eStY+BZorfY4YDG7kS/nSzbQee6U5vt9/zgf9bu0uOht/qld22vJHl/2nx7dfP7KmMLN59qbcdiq/1hvnV57bZumX8w4Wd1tt5Dk/S05qyrt51hTcWz+t1kNbeqWyMamPn6tpSv01JhP8zgyvS9vp157Vq2XtaCdVS/Hka9ZK37RxfXfCcyqXM1CBxd8+HyOlnrdWH0e5rX3z3vP+17/XEvNKaRlsF+3F121+pQtQeL3iZx+3Y4Cx5sq7PWbVV8GdmtyXq1SRa23TL3LTpU6yvYrmsj3T56Qe162RuIudU8TvXFi6pHH/XsNN/OR1+62t2+TxZtM504q9so+9w+UDH3vzjNXx5G+p2zD29WqtWKuzGzxwt737wJD6OBtr/Rj+yBaFHvCg0yPoR1XvdndNu/anK8Dq4WOX9msOB4iJqqXQ+NjWuf2gtvD2/aOA0mKbdvW1vjur0Zn2ba+PD5xI/mYJmu1f617sUPZn080Q7ZtZdEtzDu6/7h+GAv90Fn+uuvyvks40ZGKGbIUxpbGHKUj/CYEn6JO11V5eNtpiiSgA+Jx30YyHzBAU9cF3G+TUJ5VF5FOozjELv5uanu+SV+fzjsaYB+IOAvVAo6DXyn7+IxHhiLzNBMbHCDzGpu27gxgnhltwf1CjoNMm9pSKK7qbWx57a/XnTt1XKxGVjdmj23vdY0G10trdls0bWhZfeWs25szLpiaasbON8PhlPNs6dBaJuLcL0Mat3p3OBGFKtwbtwY+65q9qeZuffwWjfSjeWe1noPb6IZ3vQX+qhv+xur5W86bjbSzb25t4NR1NVNa3c16uyyTb+HR/pUH1mbaNzZaSMrSEf7KR62B7F7NZJyU+9ulroZPQ71DV+vWimaaxiuBsFwOfPdu2ayicLTZjnwXd3Ov+UZGZ6kjKHvtY2bkbXIzI6hmVlQM9sp3qz81NjTB9MaqaNsqo6yQN1OK7fEad1ebW6O/daura3q7Mq8odN2z2plHWxYzW17APlsK9RM/dcl/0SXSKdcq9r7E7wgMBE+ZThD3v/vtCLGKPvwtBZUiizbz3X5Vc2S9ZpQAY4wxN7fXZyb4KHsUg/tECkX9bjsUO9UJjCSUsp3RW4iEOGYEgmVHpUAnZTGd1eWlCMMk2cO528lJULCpxIbSNgkzQOFrzSU6jtgoZQUjtgRsctmCQuVhpKz4MhNGBanubT5xawtBBlizUTyerYtjPEXJOV+69jB0gIJRx7YUgakjxERhTtLTxguxcIHkIDuXK/dgJjhIxQIBOgkE3dhlGYRHrAAMlgy9xH0EMtdIkFeLg0W0jHK/ALhQAdzJ2EcRYgIMAmhkFgQNCeGNBdi/CKlXtEqqrRBEkWQnQp/fp/HT/PO5JN0LwSC0hA4CQ5FriZlO0gKUbkErZGsSU4SBiCGJ8klH4Vgx2gSA7oFDLk4xvkEPRbw72l3gkRKWVB5Z9p/nohfyVdi+ZjnWxJAY0TKnCbMzc+GPKJA+DAHwBdRKAGC5uz/B7sSgMTLJ2TM5yDaQWBLE+LlC335IXsETHaAoZhyLCjDiDekHGVw/0c4770yUjkujFR2oBsg4v1QQ/BdDp8aIFf+WZQTkHkMYnJpYgqyXCtMtgxywRJXJKxQUPpFfOTTyp/QbMvyNPp3VHti8ZFuKXLAE+1f1sZHYVR2fcgE/67Ir+iqgiFUjSAm1WLgu/p8pMYdCiOQM8rl91Ac0pMMrw81AQmXdEHiIEaQQLzyVaYpgVjEx9s5Ykfsyrz0pFYhZoWyXTUnKtNtmRdkJSXELiI8rzBPCTCGro+AnuepS36WvBrVapqmFZjP5tyKpbw6NNpdc94t6xW14osozPOkLAQRJK8YF20juPSN4LlxBG87xze551Xn+G+b/mGbXlRIgR5ENQ4hJsq5cOFjUZHvlfcV+VtJ8WXVbtwrj48O5GjBwvNZDh8SJGvU/TdZ8S/byK9z6akgvuCF9sVNZUuK8AIQZLN/Lj0RNV0XxeLV9DvM9QZLTMZziRec4h9CRD25hsFU/l+AaQ4czuf/Aj5zNP4=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Provide Signed Challenge Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/WEB_AUTH_ENDPOINT"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to post the signed SEP-10 challenge transaction. More information     [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the toml file under the  `WEB_AUTH_ENDPOINT ` variable.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"transaction":{"type":"string"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAvheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3AsiYk3UAAABArIrkvqmA0V9lIZcVyCUdja6CiwkPwsV8BfI4CZOyR1Oq7ysvNJWwY0G42dpxN9OP1qz4dum8apG2hqvxVWjkDQ=="}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"SEP-10 handshake was successful.","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJHQTZVSVhYUEVXWUZJTE5VSVdBQzM3WTRRUEVaTVFWREpIREtWV0ZaSjJLQ1dVQklVNUlYWk5EQSIsImp0aSI6IjE0NGQzNjdiY2IwZTcyY2FiZmRiZGU2MGVhZTBhZDczM2NjNjVkMmE2NTg3MDgzZGFiM2Q2MTZmODg1MTkwMjQiLCJpc3MiOiJodHRwczovL2ZsYXBweS1iaXJkLWRhcHAuZmlyZWJhc2VhcHAuY29tLyIsImlhdCI6MTUzNDI1Nzk5NCwiZXhwIjoxNTM0MzQ0Mzk0fQ.8nbB83Z6vGBgC1X9r3N6oQCFTBzDiITAfCJasRft0z0"}},"example":{"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJHQTZVSVhYUEVXWUZJTE5VSVdBQzM3WTRRUEVaTVFWREpIREtWV0ZaSjJLQ1dVQklVNUlYWk5EQSIsImp0aSI6IjE0NGQzNjdiY2IwZTcyY2FiZmRiZGU2MGVhZTBhZDczM2NjNjVkMmE2NTg3MDgzZGFiM2Q2MTZmODg1MTkwMjQiLCJpc3MiOiJodHRwczovL2ZsYXBweS1iaXJkLWRhcHAuZmlyZWJhc2VhcHAuY29tLyIsImlhdCI6MTUzNDI1Nzk5NCwiZXhwIjoxNTM0MzQ0Mzk0fQ.8nbB83Z6vGBgC1X9r3N6oQCFTBzDiITAfCJasRft0z0"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"The provided transaction is not valid"}},"example":{"error":"The provided transaction is not valid"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/receivers.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/receivers.tag.mdx
deleted file mode 100644
index 64d048dffd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/receivers.tag.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-id: receivers
-title: "Receivers"
-description: "Receivers"
-custom_edit_url: null
----
-
-
-
-Endpoints related to receivers. A receiver is an individual receiving a payment in a disbursement. The receiver is tracked by phone number to reduce the need for personally identifiable information. Each receiver must be unique within the disbursement.
-
-Each receiver will have at least one wallet associated with them. The wallet public key will remain null until the receiver registers with a wallet provider and links the wallet to the SDP through SEP-24. Receivers must verify their identity through that process, which requires the SDP to store verification information on receivers like date of birth, national ID number, or personal PIN. This information can be updated by the organization through the receiver endpoints.
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/refresh-token.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/refresh-token.api.mdx
deleted file mode 100644
index d1e6fba27f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/refresh-token.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: refresh-token
-title: "Refresh Token"
-description: "A user’s token expires after 15 minutes. This endpoint handles refreshing the user’s token without disrupting their experience. It is triggered within the 30-second window before the token expires."
-sidebar_label: "Refresh Token"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV+FS2zgQfhWNfrUzTkJSaAf/AwqtaSGUhAJJM4wsr20ltiQkOcbNZKavca93T3Ij2YEALVzvrjM3N/cnjqXdT7uftPvJC2xIorE/xjuFSYEbRolhguOJhyPQVDHpXn28gwoN6vdvv2lkxAw4ghvJFGhEYgMKdbdQznhhQLfRMGUaAY+kYNyglPAoA40UxAp0yniCTAoP0UpmUlEYFDGtCmkaK6bsMqAYcAptFBjENDKKJQkoiJwT4w7u1UZLAxXcDvJIlCiEWChwc/fibWMPCwnKpRlE2MendWBDa4U9rEBLwTVo7C9wb2PDPu5TcQqmUFwjgjiUiFAKukkDe5gKboAb60WkzBo+O1NtXRdY0xRyYv+ZSgL2sQinQA32sFQ2LMPqhWu4OzNtFOMJXi49DDcklxmsWWGoDtPwHWV9dnhw9jXoHrNAB/x0i+4Fr4OZvPi8d7jdhuqwS3ufq2Aq3wR5NgumgkUXxxllXTnaC3SQfzaX55m246PzbkrOb3bqZ1lc9rZNwEpG8209ujhi/cy8CfKtNDw/s4sOo4vdjPKRpL3tKuDdKB6UbHSRlsFU3BxPabc/vKz6w0+v4k/tzdF0u9q9oGmLFQeXB60ZvdpP35/cTGUpryA56n8M+/PNcPSh3z06mNN8PxltHWUX77tX3XgUJ2c35HiXHu1Fp0evj94Nrj8IWr7jO/8z8wQzlpvN753kXRKhU7guQJt/7uiCUkI9ProPG8pbMIRlGpHQ1r2t09rR7aNRRD+70vLBnjcL44DPScYixLgsrNMdXMwgi65iIbB/99/2FAXXBVMQYa8ZD4m6tQmJQhwgskWOQkCEI8YNJKActzW73cfsnnFSmFQo9tUB/1p6/zxtWBtiinU7XuQhOOZz0Jok8L3G8wOyj4VB99K8i2K1zuZGdw35ocevBHbYGmihmKmwP17gXSAKlBU77I8ny4n1N6mwOiCFqwJJ7BzuNHrVWjV2DWoOSjuUQmXYx9i6r9AHdvtqftfXuOWRSPYBqkdVcHg+tFIYoVgoF/ydBntIs4Q3MmcP3f6gt/UaScXmxACaQWW1jJPcwu80edfq7WFmwVMgkTuk9j0WLhpmLM14YCDLiEJvmQ4LpSEHbtBJRkwsVI52TgLsYZtuHWWv3W1vWA6KPCeqwj4epoCexngxeHvy0tYWQUaIDIUFy4xLU6iE8CZUV1M5mQEKi2yGJKksihslKFGikEjESAFlkrkJMQflusVqdQ6mFGrWfkTtvy/EL/wLd5cjuyRHQgJvaVEoCkgqYWsVmZS4S04diuDICAf/HTgPER65CSoiQJRw25xiUfDIOab2JctEaS9TCqTQzAjFQPs2jhYa6xqv0zxb0RpJLdmQ1AoJnQGPJi9SY6T2O52EmbQI21TknZ9CeOnXN8PbUCpkWyJhluEUUGPmsmI8VkQbVVBTqCZBuy/muT1t/0RmsXId+e+ktoJ4LrcSQrSy/cvZpJDlLZoSZfSTIa/ZdYwC6OSE8U4z8GQ+z6XxHrIcOSAXfwQyE9XqRv90rRXa2s2KEBQH+5nwxbYpAyrX/XgAas6o7UurtJow20IlHWfUEnFLN2YezhgFrp1erBqgJDQF1HN9qu7PFsvvdMqybBM369AaV935GOztHw/2W732Rjs1eeb6pBWBnPA14ObzAK2+D+41mcWdqv+nvpAa0TJwYzoyI4zby4FjddEI5BjfF8iJh1MroP4YLxYh0XCmsuXSDl8XYCVjPPHwnChGQitA48nSW+mTVdQZWFXZoRSkFeE5yYpaNR9clO4p9kl/MMQeJo+UduaUtvlj4VdTvFoDf6iZdQz2d+n9wGWxqHV8uby1r6d+6NHkuLK2TE6Wy+UfvFR/mQ==
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Refresh Token"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/refresh-token"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-A user’s token expires after 15 minutes. This endpoint handles refreshing the user’s token without disrupting their experience. It is triggered within the 30-second window before the token expires.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns a new access token","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/registration.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/registration.tag.mdx
deleted file mode 100644
index 65139164b3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/registration.tag.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-id: registration
-title: "Registration"
-description: "Registration"
-custom_edit_url: null
----
-
-
-
-The registration endpoints guide the process for a receiver to verify their identity and link their wallet address to an SDP. The registration process only needs to happen once per receiver to link their wallet. Only SDP-compatible wallet providers can facilitate the registration process. These endpoints must be supported and hit by the wallet providers after the receiver gets the initial invite. After the wallet address is successfully linked, the payment automatically begins.
-
-There are two parts to the registration flow. First, the wallet must authenticate and initiate a registration flow using the Anchor Platform Endpoints defined below. Note that these endpoints are hosted on a different host than the Stellar Disursement Platform.
-
-The second part of the registration flow is handled by the webview that is opened within the wallet application. This webview uses the endpoints defined in the Stellar Disbursement Platfrom Endpoints section to complete the registration process. The wallet application can chose not to use the webview and intstead integrate directly with the API.
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/request-challenge-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/request-challenge-transaction.api.mdx
deleted file mode 100644
index 0e88fdf953..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/request-challenge-transaction.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: request-challenge-transaction
-title: "Request Challenge Transaction"
-description: "Allows the wallet to get the SEP-10 challenge transaction to be signed. More information [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the Get Stellar toml endpoint response under the `WEB_AUTH_ENDPOINT` variable."
-sidebar_label: "Request Challenge Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtzGrkS/isqnZekFmaA2EnM1j5w9xUTwNhex5XVzDSMQCMJSQPGLv/3LWkGfGPts9mcqj1V4YG5qKfv6v5ad9iQicbVK9yHCdVGEUMFx9cFHIEOFZXusYprjImlRiYGtCSMgUFGoIm9xIAGrV6xXEJhbFf4BJBRhGsS2m8tXQBI0wmHyEMnQgGifCxU4iShqxgUXL+LjZG66vsTauI08EKR+NoAY0Str0WphBGhYH7AROAnRBtQPoRCr7SBxNcgi6VSueQl0X82mrz30DAGBDySgnKDUsVQSLhV1eoZpAZRjaQSCxpBhCh39nTAoEEmFRmRsIfvFWgpuAaU8giUI/7jvFX/Vjsb7n9rdZu904Pu8A+0IIqSgIGHC1hIyJx6EOEq7sM8BW0aawWHD57CBSyJIgkYUDYid5iTBHAVkzAUKTe4gKkNxTwFtcLPA2TNbDAK3KBaRl9Ay5iGsbM3AERQ7kiU80PvOp7nvUdCoSS9gejh/Yl7b2KShTdnu6Q6Bm3jSVITAzc0JAbQkpo4ywJQC1CetVnBPKUKIlw1KoUC1mbFrCU27LiA4UYyEcFmNYwhIbh6h81KWjJtFOUTfH9f2PgggUS87QBL5RQ0hoSxvbOKbc1LD51ytkISVEKNsbEfI7KJ+jMXUY1SbdN3IyRJtbFeFWNklUY08tCpiUHlOqwkaEQUIC4M0qmUQhmInvpmTJj+Ic4JXYC+RSIhlL/uJbKOZtMRe6gLEK33aColoxChYIUIYzml9s/dhtc/MrDXllW2lbRdr5RK9vJU19MjXMCh4Aa4savEqhe6veRPtSW5eylCBFMI7V6Ryu48QzMBjyK/RZ8C5mCWQs2+SaK1jBXRsNXlGG5IIhm8YIlr9jexf80D2k8rdTWfw2nYq3zunTdmzZ3mbn861fP4U3l/uZi3L35p74wuLHnnS+3pr+X+L27VWeiW6uNTMy4/W69nt636ZxXPu+RTqX85JV3eLtf6rUojON4t0f7efu9iMPTHB8lh133fsPo16yXSYbfkohtHndFt1Ni9vTzfnV0mezvHSTu9rMSLkO7GQdIVwYfDWVApx+R8J72s7JmDTrscdSYb+V86Uee0zQ6+JOVb0pGt89Zl6bg0Ojxr/56GnRHrz25Gw+ZlZVQyRyejeu/y4vf0bDSqd6d1cVzauyCNvfJJZbSIZrs75+1DMxjWFl8qZw+mjmNoj5ZOXAxHrfL+tMPPGt1lL7j4nNx+asyFGcRHQe2Xm5PKfjBlHy9Kw7psSTU6PRtNax/Z/OSwPP1YWagbXk7aH+DwVh+TPb0X98W486E2+e03vD32eAjaoEGzjbrZKvoVDUAaSAJQqFIq7/5Mh5/p8DQdbELsbCtkB2OkRfIU9yyJRgnVmvKJ7cCULwijrkH8oIoHSgm1tdbBjVFEv81hjTu2FMJnuZ/LwnUSIZUhHA8/FrRhtb6zqMS2xgAQJNKs8P+GpeOagImFBV8TcEYSE+Mq9l/gNlzA2mGYDH2liuEqxrZXaQhTRc1qYH2fOacORIGqpZbXxj9E0iN42XQPz4cOP6CxUI/BExW8kCPjDEYRjlqDyu5HJBVdWHA1g5W1Ou/zVppQ9JbkcNH1+RhIBMpVI5tfThtqXFdeo5km1UGqNCS28fcYMTYNUa13gAvYmptpWfHKXsn6IE0SolY5pHqdx7tBs+fgEUFGCIaClDLjzBRqQniuqgONCZlZwM1mSJKV5ZJBSTRRIpUWRykIqXSIA4lFDq7X0vM96W1Fff8uFb/yr3wYU+1EciQk8KIWqQrBzhl2o2XImupcFTcjOfZb2BUQ4VGGYkUEayw/FimP3IexfbCzma0jCqTQ1AhFQVetHkV09XyKih45qShzJxUDEs6AR//VHPYqh/dV5IzfqLJCtp4RyrPhMSdzVlE+VkQblYYmVbmBNi7mrZh6f8OysXLl9J+Ytmbxlm1LCNCa9rutiYElxTAmyuhXVX5E5xsF4Fs47+cvXrXnLTP2gSXIMXL6RyCZWNn0etMSlLp2NksDUBwMaO+rLVMGVKJPx3Y+pKGtS2uzcjU9oSa+IyqKcVHnZAXMaAg8A+LrAihJGAOquDqV1WfLq+r7y+XSI27Vccs/1f7xQaPVHbSKFa/kxSZhrk5KoU1C+CPG+ViONnM5ejqYPyk6dw8t+ue5yHefi+Qt08CN8SWzg+t9HtO7vEVf4Zct+rqAY6GNXby7C4iGM8Xu7+3rbN61jTui2gp5mLD/Mnrv+vk8+x79q85PtvpmBqsnh0ELwlJwCKXwd2z+fzknecUH+WHQdzrgUdD/4WnIKyo+P5J50PXaPmTbAFevru8LawRnUzf7uBaGIB+H+MUcYLlsYG2nNcT3938CaiWJfQ==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Request Challenge Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/WEB_AUTH_ENDPOINT"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to get the SEP-10 challenge transaction to be signed. More information [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the Get Stellar toml endpoint response under the `WEB_AUTH_ENDPOINT` variable.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account","in":"query","description":"The Client Account, which can be a stellar account (G...) or muxed account (M...) that the Client wishes to authenticate with the Server..","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"memo","in":"query","description":"The memo to attach to the challenge transaction. Only permitted if a Stellar account (G...) is used. The memo must be of type id. Other memo types are not supported.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"client_domain","in":"query","description":"a Client Domain. Need to be supplied by all Clients/Wallets.","required":true,"style":"form","explode":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"transaction":{"type":"string"},"network_passphrase":{"type":"string"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAfheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3Ag==","network_passphrase":"Test SDF Network ; September 2015"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAfheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3Ag==","network_passphrase":"Test SDF Network ; September 2015"}}}},"400":{"description":"If some information was missing or invalid.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"account":{"type":"string"}}}},"example":{"error":"Bad request.","extras":{"account":"account cannot be empty"}}},"example":{"error":"Bad request.","extras":{"account":"account cannot be empty"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/request-registration-url.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/request-registration-url.api.mdx
deleted file mode 100644
index d21a2fb924..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/request-registration-url.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: request-registration-url
-title: "Request Registration URL"
-description: "The deposit endpoint allows a wallet to get deposit information from an anchor,  so a user has all the information needed to initiate a deposit."
-sidebar_label: "Request Registration URL"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV21v2zYQ/isH7sPaQbYyJ002A8Pg5WV12iVZnKRA06CgqLPFmSJV8mTVC/Lfh6PkxEm7ZC8YsAHzF1nS8eFzD+9N14LkLIjhpTjFmQ7kJWlnxVUicgzK6yreDsVZgZBj5YImQJtXTlsCaYxrAkhopDFIQA5mSLd22k6dLyMgTL0rQVqQVhXOJwDBgYQ6oIdCBkYCKvDeEouYY86g2mrSkhDkCrv/zr6zY2YQHBikEFe34BAqVHq6BJnnmpGkuYdLhaRoHncv60AQ6qyMhAm9VKQXaJaw0BIkVK6qK3AesMwwZ0KZdw2vbLTNXcP8MgSZGeS/K35wYlAGBFWgmsfdciSpDeaQO1WXaKllc1mgx6tnBVEVhmk601TUWV+5Mg2Exki/uvYq78gpZ9LMuCwtZSD0KSoXloGwTANWvY2NwVa/zL/oWPQGz/vvrEiEq7A92HEuhuIUP9QYaP3Az09fi0TgR0JvpdlzKojh9YMQONA2h9L59pSAeYtE1N6IofiH6IubRHgMlbMBI6PBxsanxEarsAKPH2rtMdwdLzmYamPA1ffj0VkOW8wqOUMoXCA+2OVaFPVFIpSzhJZ4x6/Sr/gSVIGl5H+0rFAMhct+QUUiEZVnkUm3PNu3t1aBvLYz8TCpRqaRywChTZ216Huv6kCuRP+eOb9vM6EfT0iWlWHIp6xZung2T5E4P339eQGAc77L7FC42uR8aYAKHYBXkbvTmXO4zZX7NFeBISvd757G6Jgv1dS45nuplKstfffjaPfNztHx0cXW5k9vxwcvd49f7f58OHo1OZyMJ5Px7sHF+eFgd3v/7fjNi52dzePzzZd721sXY3ZT5097eXbr15ehVZrLwngPps63Hq2qVgqNpiL3spEmBhQGuqdFw/FUB2yXjfdYhw81+la8lLy0gQ/G2btKSa6rBIEk1QHcNBqv4O9J9s1gWoSdwbfT7c282FhsiZv2l4gSqXCcwZULMeYkFWIo0rPT0dHkYP/0/WT/9CJeTjiV1qmEtPMvXQsckYiAfoGeG8B1l8ri5oofq9prWk443tuQ/gGlRz+qectbtWWlX+HyE7UP35yxQnlUV9ZUoCWtYuYlEPTMYh5V5o6wPxm82IbK6wVX+DkuWQ0rS4bn3ZzXv7ZNKRGawQuUOXrBgnC8RzaaonSTttbAng5Z7QNymYUTI4kTH0YnY5EIdrdlOeh/3d9gDeqylH7ZRcnjGM8meyfPQXO0k3MGslobim46P5O2oxr4wEs5R8hqM4dKLhklPpUw8447yhQ8Kl3p+MItuFat7W6RGufn/c8G8r+LIrfiM04F3tKCq9D2gqu9Qqi84/LYtlwdOircg121yoEHcAlIm8cXyuUISlpur1NX2zwuLPiG5w5tZ+DbmHZeYxgyjx5cPuw7+ZpIvaoTqZdJNUeb/6HG+yjC8yFE52+pLIHbhtS27UKdWfRK26mXgXytqPadg239eeJM+3/Cs6mPXevvuLaCeMq3BjNY2f5lbwo0ZU8V0lN4lPKaXUoeMS2ltmn34FF/nnLjJZoSIlDkn2Nl3JLD60lPoA5sN68z9BYJQztuEfoyHE8n6BdarXfBjmbf+VkajXpu2gudWSKMVmhDHBxWBbCSqkAYxDp1N2oN07Rpmr6MbyNatzSkr8e7+0eT/d6gv9EvqDSxTnK/KKVdA+5mQFgfAqGdAu/Vm+u7Iej/b4D/9DdA17EJP1JaGant2oTYDhKX4ncGCV69NkrEGIngsSXfjRNXieBJkpGurzMZ8Nybmxt+HOcjMby8SsRCes1K8d1NsurmPH/MkXvwSCmsGHkhTc2MefTmmeR2+jk5npyJm5vfAD7MREc=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Request Registration URL"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/TRANSFER_SERVER_SEP0024/transactions/deposit/interactive"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The deposit endpoint allows a wallet to get deposit information from an anchor,  so a user has all the information needed to initiate a deposit.
-
-It also lets the anchor specify additional information that the user must submit interactively via a popup or embedded browser window to be able to deposit. Please check the detailed documentation [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#deposit-2).
-
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"An anchor requires the user to fill out information on a webpage hosted by the anchor.","content":{"*/*":{"schema":{"type":"object","properties":{"type":{"type":"string","description":"Always set to interactive_customer_info_needed.","example":"interactive_customer_info_needed"},"url":{"type":"string","description":"URL hosted by the anchor. The wallet should show this URL to the user as a popup.","example":"https://api.example.com/kycflow?account=GACW7NONV43MZIFHCOKCQJAKSJSISSICFVUJ2C6EZIW5773OU3HD64VI"},"id":{"type":"string","description":"The anchor's internal ID for this deposit / withdrawal request. The wallet will use this ID to query the /transaction endpoint to check status of the request.","example":"82fhs729f63dh0v4"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/reset-password.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/reset-password.api.mdx
deleted file mode 100644
index 861b11fe88..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/reset-password.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: reset-password
-title: "Reset Rassword"
-description: "Allows an SDP user who has gone through the Forgot Password process to set their new password with a token sent via email."
-sidebar_label: "Reset Rassword"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVlFv2zYQ/isHPrWFZGXBtge9pU2HZRtao86whyQoTtJJYi2R7JGy4xr+78NRcmw3RYJuD5tfLInH7+6+493HrQrYeJXfqIshtGSCLjFoa9RdoiryJWsXX3N10XV27QENLC7nMHhiWLcWWvTQWEMQWrZD00JoCX6x3NgAc/R+bbkCx7Yk7yFY8BTERDMYWoPbW6x1aAEh2CUZ8GQCrDQC9ai7mUqUdcQxrqtK5YrJU9iDq0QxfR7Ih9e22qh8+1XcH8T44GiyhQoDqkSV1gQyQba9yl7Jny9b6lGexFQzVcKOO/bmKXyMkQpLYeNI5coWn6gMKlGOJdigyQvGw758u7f0gbVp1Nf8vjumo7YciRSa1e7U57NI15HEwVMlhOtKqlpvAGGFna6OqRBmJkLUTn7JUdKBBxpdO2v8mM752dljhuengH4opdj10HWbE4YF/sdvAbzGCj5MYZyUBJ3rpgOZffLWnNbnaeaJ2fLzZF1SQN15wMIO8WTCuHGXKLoPjP5ZT5E2usfedXTkWF2ZkW9t3CCbDnC1pq76WFur8sMzaA8P5CfT9wL5waZA6RmqYhsVJJ2oTaBGTshuqt59WtqKGjLpVNa0sNUmNdhL/PI8BkLGa2uk77dqSRuVP7kzUSvshgeE3V2iegqtlV50NhbNYWhVrrJ4BNKjbvHEK+LR08CdylXc76kcWIfNQqo5Fuw1IRPLGDqiHJ3+nTaPqvbbX9fjAZdGwZPJlYDXjaH9SDHwdnH+08/gWK8wECxpIwNlYkS8WdZfxpmXKC3gLWEVSZX32sZodJDiqkWgrkOGS+2LgT31MqnmHYbacg8X8yvhitiPUZ7PfpidCQdD3yMLy9ctwdMYLxaX85dyFmQY2g6KQXchpmm5QTOFGs9Aj0uCYuiW4HAjKPErQsN2cGBrYCq103HBrmicKHvvhsLa8nL2eHr870K8NbfmutU+ujRgHZnU24FLEmGRloTQYpDlMRRrINgI/w24BNBUcUEOPJRopJlqO5gqbmzlRbROmwaYnPU6WNbkc4kjhRs/4mXTf1odkZS6iaS0wHJJprp70YbgfJ5ljQ7tUMxK22ffhfAyh5j8QygbkAmJWhhuCSazmJU2NaMPPJRh4CnBvZQ8WdPZd2RWcxzQ/ya1PcRzua2pgL3tP86mpa5PyxY5+CdDPrLLAhNlPWqTTR+ezOe5NH6lrocIFOOvyHV2I8fr2Uxg8GK3HApiQ4H87FbGVCDu/ft6QbzSpcylfVpTmDPLTRaNUlunfjJLVKdLMj6q1H4AOixbgvM4p8b5LFh5lq3X6xnG1Yg2bfXZH1dv3r5bvE3PZ2ezNvRdnJOiAj2aI+Dx2vXhIAQnU2Z7UPn/9mI5yUyg+5C5DrUR4Y88bCdNu1FfadpdoloRvfxGbbcFevqTu91OPn8eSKb8zZ0IJmssRDNu7nbJXlIOcvtmTD+9Fv8HfZU76C7ZG12UJblwtPzoPnQixfP3i2uVjBqdb1VvK9nDuJZLK66j9O52fwOrz0ME
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Reset Rassword"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/reset-password"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows an SDP user who has gone through the Forgot Password process to set their new password with a token sent via email.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Reset password request data","content":{"*/*":{"schema":{"required":["password","reset_token"],"type":"object","properties":{"password":{"type":"string","description":"New password for the user"},"reset_token":{"type":"string","description":"Token used to identify a valid password reset request"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Password reset successfully","content":{}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-disbursement.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-disbursement.api.mdx
deleted file mode 100644
index eef33ad2d4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-disbursement.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-a-disbursement
-title: "Retrieve a Disbursement"
-description: "Fetches information on a specific disbursement by  `id `."
-sidebar_label: "Retrieve a Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWVtz27gO/iscvmw7I9nyLU795sbONmfTJBu77XTbjEuLkM2NRKok5dTr0X8/A0p25Ni5tE13zpwXX0Tgw4UgAEIratnM0N4nOhBmmmkDCUhr6JVHOZhQi9QKJWmPHoMN52CIkJHSCcOnREnCiEkhFJEICa8AkOmSkC+Cky816lGVgnYcJ5z26CVYLWAB/apE6tGUaZaABY3qrKhkCdAeFZx6VKAGKbNzeletkwFREbFzIF+qcE6shq+Z0MBpz+oMPGrsMkZII5I0BupR+JbGigPtRSw2SBDOIWG0t6J2mTpKq4Wc0Ty/QjSTKmnA4HozCPBrW5eqAoSDZSI21KOhkhYt7K0oS9NYhM4V9b8NMq12harp3xA6h2h0nBWFSMF3FbvrjfEcSCbF1wyI4CCtiATotYP4trvhG3Nu6NGDxivODjtd/7Db7PjtsHPov2q1uB82mgFrdw4hiDo098odeYoOSPmo2C13nSF2jl4OQSxATzTMhLFF2EwSMIbNYGIhSWNmn6hFmBmrErJmIpkBTqwiBiQnQi6EdegGn63lmhpB1i8cIpbF9gspRRNh5G+WaLCZlsBr5EQ668rl3wwpt5kI+5shqTJGTGNAaMa5I41UHKsbIWe3Gi2YFmwag+mR1ap2rmdMin+cUuiPPCc3cxHOiTAOoLruHIYyIzHLNHDCJEeMy4rbToW8vosRC3lNZiDxQALHYzoaXGycYpUjWjuDvBCShMwAsXNhEEIqS1INxhm65QGvMJxlVmF2CFkcLwlLU5ActbOOFiR/WdsKgo8qI3O2AMJIypYuFG6YsOilSGmyVBmJtEr2u6dGjmIRXt9jt9tVfAq6VoRWJaJwt1hoJ0UU7UYTyCzBrDh82z85pR69eHN+NpycvXv7enhJveLxpH82mHzon54Ox5P+YHA5HI3uUO6juPKoFdYZX1X6qFBojHrkHr1hcQz2R7PCrX87jLNXwDt+u9Nhfrt72PRZAOA3DoLuQRcCDtPGQ2f7Fum9mGomLekbI4xFnrlKIGWzR/jm1qamV68vCn6WprVQJchvIJ00gkkYC5B2wlXChHwYi6XC57Co7WJxgHSCwT25L4k/rlPd8BThES/UgAdkwuw+pKIE0h7lzIJvRQJb8M2g2fKDrt9qjJtBrxP02p3aQfvwLwTOUv4rgPPbqPpQhE7uUWbMc8RQFDEI29OW3z6YBn6bT9s+a4dt/yBsdYLDoNPtBq4+hK6WPpaZ+6gUcbRVIe9GgyMEEcZkoJ8KU1BjitVgzBbg769fD9rdk+OD0w9/dC+6bwfD96OjD5fdwcW7D+9bZx9bg/Gfw/fHp+2z/rjd//NN66/T0+PTfueZdr/pB61xA3eo12k8187vgnKI4SdBD0rQTgma76ulIwtxzDRxIUU2gbSOObcb7kxbZjPzUEYdXPaPx9Sjl8P+4CP16GjcvxwPB5g5++9G7sfR+duL0yE+rCTLarswKqTkHl2AxuazSOqRgHh/LK9l98fDyfnx5PXJ5fgN9ejHYf9y8vb8zP25ODmjHj3rj0/Oz/qnk5PBOt1XlHhfEXfspG1snsyFsUovK/KZ1myJ7auFxDx+DjMDevLYYWxFrU5j+gp84EHkt4OI+azVaPuNdrfTnbabnBUJ/d/eCAwuY1mSPltw5w+JfFM4eyitXtKnUCJRJGKYPF7pqh2rH8HUD1o+qlgLzXPVhn8pO1hlWTwpG6tqMAhpYQZ6t21GBiKzZFrcGzasFWmNYAd5YsoLznfCmywMwZgoi/dKOtwVFDERA/8BUQXjfoN2xWjAZgR9//2SNrz3CmOJyrDjKePsiRc7pyIpeDe3Kk6MIhHTW+FwGAS1ILgNgILnB6RYRaa3Nzi+JaQRbKSwBWi8nn2PnJJnLSkFvXbXXSlOyD1HnOY5LrWDxu51/J1kmZ0rLf5xmj/TNRy0VnvakxyVtpo9Ic3vZOYidBCivEvtm0DkecUtGzXombJky8xbLdZy2kGjgnyX41cCF1vT2t2aY6WngnOQv35f9lt3q8ATCAoz2rtmoMXHKpP/3+EVlRbuC4B2NQC2Bjpyw/mLsR28gTDTwi7d5PA1MA26n9k57X26wtldAnaucPY4g2LSiEu0Xi30pr4SPKcIpRfrGWSmY9qjFCHWEka4kYWnq3Jue75U/AHLnZT3nw/jYv6EUw08JTidK2LEI0bMJHByI+ycMEmGo2bngKRaLHBGdA1LHJmU49B+ecAc53oyOgfGcYfx+iQj5bQpk+W6b9/y30XMLHYUpH9xQl0PbQotm7VGLUAfZEnCsJXd6v33Y7wYDS5e4myIEatUTKaZiK0zU1UGNm7IlrBrINMsvt5URjcfIzOtsrQonaFIhVtQOH+yFekS7I3S17W91eR/S8XP8rMclxMzJolKQfpGZToEkmqFp5bYOcPba6mKksSqdD0xvQPnudkeLuClmYRMYlF28e8Yt0aLGlJlhFVagOmhHj75ZAq8evntb/W3aekkf8rCa5D86sV6ODITdp5Ni8HI9yC87BFn/EaVpZuNMiGLEWRJ5qwSMtLMWJ2FNtOlgbgv9rE9rX2HZZF2uflnTFtDPGbbDUzJmvaHrZlDnPjhnGlrHlS5Qle3GqCOfWe9fPCgPY+Z8QbihDggpz+HNFZLN7l+9KxlBumusyloCRZM7TOmKQs6MefRCPRChNUJXKlmTelZ3RH5KvJNSebRWIQgjSsb6wSYsnAOpOnyVJGfEatXr9/c3NSYW3VoJaupn54cDc9GQ79ZC2pzm8QuT6bK2ITJCvD6tRRh5M6Lqa10s7qt9D/1TqwsFxa+2Xoa4+QzL+1ZlfXp09ZFFC8RPcHxIj5XxuLyajVlBt7pOM/x8dcMMGV/uvLo+r2CK2JcGPzNN6+57rXnxWX5xuwleei92l7V1+VPYu1bsDjDf9Sj17As3uLlVzgyLioVqlUs9MMQUlth2Wmetur370OcWLCdknvtSm75A9H3qnO3eBYq4Gfu3cOyWhUFPc839MXSvRyliRvL0YI8z/8L0ysX1w==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches information on a specific disbursement by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-payment.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-payment.api.mdx
deleted file mode 100644
index 5361404d47..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-payment.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-a-payment
-title: "Retrieve a Payment"
-description: "Fetches detailed information on a specific payment by  `id `."
-sidebar_label: "Retrieve a Payment"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWVlz27oO/iscPrUzlq3V25sbO2laJ01jJzmnaaalRMjiibaSVFJfj//7HVKSl9hZus3cc19ahwTA7wNBgIQWWJKZwP1rfEbmCaRS4JsGpiACznLJshT38SHIIAKBKEjCYqCIpWHGE6KmUZYigkQOAQtZgPLSCPLnCH1lFH1t4gbOcuBa+JjiPj4HyRncwaBaEDdwTjhJQAJXQBY4JQngPmYUNzBTAHIiI/wQ1fEQZSGSEaCvlSW9GIdvBeNAcV/yAhpYyHmsrAmW5DHgBobveZxRwP2QxEIJBBEkBPcXWM5zLSk5S2d4ubxR1kSepQKEmrdNU/23DaNau3KOwA0cZKlUvPoLTPI8ZoHm3vpHKPnF7nqZ/w8E2g1ceUqycjVGdzEp9ETz6GNKQ9sOPc9wbK9nuF3bNogLthGAaTmO2+t1QhcvG5gkWVGieWhrm8g0AlTK1n7NVxu0XtUyzaZpKrtCQhwT/kVykgoSKCtf9mPeXWe9dxvaiKV6aFIaRinI+4zfNtGxRAFJkQ+oEECRZJlSC243QT6ijArB0hm6rofHxM84kRmf37yKpMxFv9WKV2PNilMz47PW6wbK+Epz9F1tzVqplgQ93nrd3PKS6TtOj1pBt0cdy7W6bb9ruZ3AJqEb9EgPqOf71A9oh1DSpZbTbTtOz+y03Z6vXBswHsRQejYE/kXFNAj5YvceaH1U66NKHx0PtTOZQFkaz1HOQSjX3UeQbvnyngiUEAqV90pz2ww7Lml3/TYxnLDdMVzb9Q2/65sGeD2HWD3acdvOZpSscsBeElqQyEK8jF8puydM0yJRqWx4Pjic4gY+Hw2Gf+MGPhudDo9Pj9SvwcVkNMQNPLk4OBhNJriBDwfHYz10MDg9GKmfNw0smdQ0q9M9KcGtYH6JmFABswGXcE7mO2gHKSKzGYcZkUBRzIQ+XAlIQokkqDz6AqmUQViqnC1X/EAgktLylLAEhCRJrrTr7RIrRwQRSWcgUBYEBedA1VYxCYl4Psv8u9yegBBkBnsDaOWjfWTKeqWyJpFgKNGtaLZN2zFM2zCdqWX2Xa/vWZ/wcvkIoLfl5o9Syef4GSE1T5nwCy4gga08/EN5f3c3ipR9KwAxCqlkIQNeb8zWchvUi0JX1DXrwLN8YlHP8GzqGK5lhwbxeoHRhtCxqdcjvqvPcFmPX4JJST4CY6NwbUwY/xQpGHbv6QzwWIBNpoPzqQ6iVYAdfDg5G4+m2+E03FhxHVMBB3Uqv5AXFkctr+rU1ml8yuNPBVvbcMypafVtu+91ml3H6nW8TwpWkdMfghUTIVGp9PuRdZuO1fasB6dh059jJkFfM4SAn47uNYQwJBC4vmO4bd80XOq7BnED12gHjmd2Ta/TMT29efoK95x/BgoU0rKbi1xMhgfKCBOiAP5SM6U0IpRyEGLL4NGbN0O3c3zYHl+975x1Toajy8nB1XlneHZxdemc/u0Mpx9Hl4dj93QwdQcf3zqfxuPD8cB7Pgx/KnE9F0Q/aZRCDL9otF0Z9dYpdjei68uaDim0CqQ6+vRuKDwcAmB3wL/ckzj+HcHXNR3TsahrWNR0Dbfb6Rl+m/YMGnht1wp7vW4XNhf+9RVNuwc2UNMIwW8bbuCaRtd3O4bZddqk63Vci9hbR++8Wro+dr+LukeovpcarucRw+10bYOYAIbVNjvtDpgUfOupWrC2dMl8TlKJBkIwofcpyhLI95btTb36Zn1X6pM8bwZZskX+SpOtqddXy/pAPmn96OCvwTvnr3fO5Xvn3eFb5+PJ8PDD5P2JfXpy8unN5INzeTxtjy7OPl5Nhlf2u457Yjvn55Px8yf0yXPTNE3zBQfyZTZ+vECej46OJ9PRuS6Nh+PB0dF2YayjSZSerWvjnnjbdv2/JWftXs7wcqlGXdPafcpfpKSQUcbZf4D+vnc8cJ7tqTFLhV5y8jN39LRIfODKxOMXYk1z5Z8VDHyaSbRFc42iXsc1rQ3LDzX+pOFya5zdrTnMuM8ohfTP78t+dmsALxAoabi7NBTjw6xI/7/DK6wY7gsAdzMA6t5ZulL6c2a1ZQFBwZmc6zbjGyAc+KCQEe5f36huXwIyylSPcgZlW1JN4Vb10hWtBaNLrKzwu7pXWfAY9zFW2rXxidq50rWbS6w7BTl7D7utgndX07K/FWZcHwv1riuDooEEm6VA0T2TESIpGk1sr41yzu7Urf8W5urFX7VNB9WJ0pp1BzUCQtWWqktvGmYaTZUY69vW5qUencVEqoyLBmfHuIEV3RKl3bSapvJBkSRENUC2bmz7bbyaDM9eq64TQTLLYuQXLJaaZsZnJK2gCiQzlJBbQH4R39btBT1K0IxnhX7UcAhYzvREdgd8b8Nw7zPpfwvi5/RzOo2Y0EumKMshNURW8ABQzjN1TJGMiG7VlVDUszNbPesemGusGkXqqVM3S3Xoa8VI/RHH2b1qMHHIM8FkxhmIvsJhoOvqKlV3NY2tJ3peOcnwSXALKV03QWdMRoWvrmmtH7Lwuo80+RWUed0BExpsJaZZsTTkREheBLLgFUG1L/K5PW3+ALOQ62T8K9RqE89xuwcf1bI/zSaCODGCiHApnoS8IdeSHKCVEJa2qoEn+TxH4y3ECdKGNH4KeZzN6/7l02etbCrfFj7wFCSI5meVpiTwRHwIJ8DvWLD5HtjsyWshIwsNUYk1cMwCSIUuFnUCzEkQAbJ1nirzs7LVb7Xu7++bRM9qa5WqaI2PD0ank5FhN81mJJNY58k8EzIh6Ybh+ssVImj97Wor0yzWVf2Xv5pV1ULCd9nKY8JSfUdWdBZVZbrGdQbCDdxnVN3so0xINbNY+ETABY+XSzX8rQCVrK9vGviOcEZ8lfqvF6oXp37T1dewR+m8Oq8+rL1Gj3x52wu4rnmpKnh3JC7UX7iBb2FefuJb3qgXYlmeFKJyYhAEkMsNlZ0r0la9PhqpVw/ZqbO3us5WP5T1vXAeVswSgvp32XhEZbEoq/hyuZIvpx7VqCiumCsGy+Xyv38J9VY=
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Payment"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/payments/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches detailed information on a specific payment by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Payment`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Payment details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"}},"title":"ReceiverWalletLite"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-receiver.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-receiver.api.mdx
deleted file mode 100644
index d6c81f4267..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-receiver.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-a-receiver
-title: "Retrieve a Receiver"
-description: "Fetches detailed information on a specific receiver by  `id `, including all associated wallets."
-sidebar_label: "Retrieve a Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtz27gO/iscPrWzli1b8iV+Wrd20rRJmsa57DbNuJQIW2wkUktSSX08/u9noEvqxE7ctN2dnTPnxbJEXD6AIABiQS2bGdq/pCcQgrgBbehVjXIwoRapFUrSPt0FG0ZgCAfLRAycCDlVOmG4TJQkjJgUQjEVIdGlFBLMCfksOPlcI0KGccaFnBEWx4QZo0LBLHByy+IYrKnTGlUp6FzePqd9egJWC7iBQQWK1mjKNEvAIsD+5YJKlgDtU8FpjQoEmTIb0YfI94dETYmNgHyuRH1GdRr+yoQGTvtWZ1Cjxs5jFGdEksZAaxS+prHiQPtTFhskCCNIGO0vqJ2nOaXVQs7ocnmF0kyqpAGD6y3Xxcd9HJVyMsxdaGiNhkpakBZpWZrGIszNb3wxyLBYV6iCLxBadIRGZ1lRqBN8HRTCZ7khfTrteUHQ8XoO58x3/CZ0nJ4b7jjc9aADELYYTOmyRtNISZjILAlAPy3xt2a73W55nZ7fbSMnfLWgJYsn26BkRjdbnufnTAkT8dPkX7iC35GsrvQMeUINGDYTZp9mbLktz3FbjuudNt2+3+63m3XXdT+iDKssiycpmycgrdkiBxlMFoZgzDR7Ftc0PyffyeEih0aPSCFnz2OaCWNBA5+UZ+lppmbBlMcin7BEZff1MK3ZHA+UhcRsjz1mDNhJmJ+Tp9SejYevUXNBL4zJtsXY3qtXQ7+7v9s5uHjXPe4eDkfn49cXJ93h8dnFuXf0pzc8/TA63z3wjwan/uDDG+/jwcHuwaC9wb4tHnHduuvSJYaGsPmnQcGGn9ad+kwPbTsSPddzvSb3nSZ3fcfvdXecoMN3HB62O35zurPT68GKTfrnNbqtHWgBd50pBB3HD33X6QV+13F7Xof12l2/yVr33FGlrgNhcyiFT34eSJtxtgO87fjtNnP8bq/lMBfAaXbcbqcLLocgD9ci0T8l6VwEmklLBsYIY5EnUgmkbLaFL7I2Nf1G46bgZ2laD1Vyz/iL3NjKdGMhjpmeMM41mC1nbe/1H4O33h9vvfN33tvdN96Hw+Hu+/G7w9bR4eHHV+P33vn+aWd0dvzhYjy8aL3t+oct7+RkfLCqKIFEbag59wkmxeoGql+RMLOU/7QMIW/Es2TsrMuImbGTBIxhM5gYkPYRaffrrhUJGMuSlNxGIPNG4K5DQYnVGydMkhxm0dSwQGWW2EiYsknZiLPp/oICU5FOKij/pvLy/0rxnZXCWGazzT6VWYL99fBksHtKa/RkNBj+mT/39seno5PRkNbo7sFgb280xNb7Yd41RQ4aFwruVE0iYazS8x/fk38Q8t0x3KStuErQPsVE4yDptsP2cWOBuqf1TeGdkbR6TpebyAvqzWv4dVmjvttcb+XPJMtspLT4D/Bf18aD1mpDpBfttWY/sp1lL7+s0TJtbrq9LJcrvr6DQY+UJffM/Iai0uO7zRXJDzn+TsHF1njrW7OrdCA4B/n378tm674B+A6Cwgx/3Qy0eFdl8n8ivB4Pg2lp4qYI8Fcj4ASMynQIRN5xLUvRBsJMCzvPRwKvgGnQg8xGtH95hRfzBGykcKAwyyt4PiLo00bVApjGQvAlRTH6phosZDqmfUqRvZI+Ri8XbljV8S3xpuIdzNeaj7cXpyQzwMlU6TyEQdpyA2vEiJnEEYiwEfYeo3Gr3SGpFjfMArmGOU4pyhnHoIz+nLMad0TAeJ6o8H1adIllFhsXzSEZChNk2gCWe3IcM4uZlgyO92mNorkFyla9WXfRB1mSMKwn9DQC8rSMF+Ph8UsiDGHEKhWTIBOxzc1UesZkCdUQq0jCroEEWXxNqsYDvzIy0ypLcTijIRSpyBcUtmV2RbsEe6v0dX3Ntf8+iJ/kJ3mK/SKqlESlIJ0ybFOt8EgRGzGLywUUJYlVaTWeeiCuRpjk+QL2TCRkkgRQxH7OGOFLHKtbnKppSJURVmkBpo84HHJZXhAa5dPhK05y0tJJTsDCa5D86kV1FZoJG2UBXoMaz5Lwsk9y4++gzAlmLibQwxGQkiy3SsipZsbqLLSZLg3EfbHb9rT+DMumOk+cP2NaJWKbbbcQkIr2h62JIE6cMGLamichr9A1rAZoYFvfKD88ac82M95AnJBcUI6fQxqrOYbXVktIZpDuOgtAS7Bg6p8wTVnQiXk/HYO+EeHqfbuEiWO9Rk7kqKljSrIajUUI0uTlokqAKQsjIK08TxX5GWX1G43b29s6y1dzaSWraRzsvx4djUdOq+7WI5vEeZ5MlbEJkyuCqzkzYWRl0nwv1Sy+leB/Yg5eVhQLX20jjZmQ+R1c56PSonxd3g2DcIrcFxw78EgZi0uLRcAMnOl4ucTPf2WAGf3yqkZvmBYswPpwuaBcGPzP78bbj5r84qSclL8kj83SN0KuKqPEsnjD4gzfaI1ew7yY2i+vcE5TFDGEVCwMwhBSu8Ky1vTcK+t7I7yesLVqfJ1X4/IPSt8I52FdLSDg77L2CMtiUdT65fKOvlh6lKM08c5ytGC5XP4X9tWslA==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/receivers/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches detailed information on a specific receiver by  `id `, including all associated wallets.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Receiver`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Receiver Details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-tenant.api.mdx
deleted file mode 100644
index c5a90a6adb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-a-tenant.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-a-tenant
-title: "Retrieve a Tenant"
-description: "Retrieve a Tenant"
-sidebar_label: "Retrieve a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWGlz2zgS/Sso1FZtUktSp60Mv8mWkkixJUVXMnG8Ckg0RYxJgAOA1mhc+u9b4KHDku0kM1u1tZ9kA328bjReN/iANVkq7N7gNo0Zx7cWFglIopngPYpdPAYtGdxDewqccI0tnBBJYtAgjdoD5iQG7GJGsYUZxy5OiA6xhSkoX7LEGMIu7nWQkGhAYkAiQDoE9C03+M3BFpbwe8okUOxqmYKFlV5HxqhicRIBtjD8kUSCAnYDEikj4IcQE+w+YL1OMkktGV/izebWWFOJ4AqU2a9Xq+bnEE3uGlHQhEUKW9gXXAPXRpIkScT8LAGV35QRfzh2J7zfwM+SIU26NMudMXoMyYAnWRgurrUa5x7Qht3yfqnbzdZ51X4TBHX7rBZ41TcA1dYvAd5YRU6PLT2KIgSk80iMgoN6GqlQpBFFMdF+mKU5IVqD5Ojbv2+I/ad9+69/ZBnfYfKiFHwhE+PXIwoWqYy+z/ekM0Ie8e+AU6RA3oP8p0LGBJqNrw6dhFonyq1USmd2oecomjhCLo1zRZNFyhY/jmHWq1CiQk8QSdHFd/k/8KuJTtXJg+NpbK7GtDtoD6aLy3G3Pe12sFUujMbDeW/SGw72F9uX0978UK7T3S3ebixMmXHhpSaOBfF9kXK9IJRKUCdxnAhbQxQRiQplVCijVAFFgZBo54IvUZByqg4T8u7yc7vf+NxvzD80+m/fNz5ed94OJx+u64Pr6y8Xk2Fj3pued2ejj58mnU/1fqt5XW+Mx5Mr/BT8HPPPYDcaLwIvTqLTm0zHvYvZtDccLNqXl8PZYOpMpt2rq/bY6Q7m2HpepHOxmLdnV9On5C5748ur7k7sydN6umiOA85lS97bN7fNwXeGn5VRF1t41B10eoN3i9mkOy4rrjccZHiZWlAISBrpPXieEBEQfoTvIl9HQUSWSIckY5CVQqsQdAgyQ1xwDFM5/ty2oXMutJNZLLxl5LyxsC+BaKALok8lKBAyNjuYEg22ZjEcVGa9Wm/a1YZdb01rLbdec89qX0zVpQn9+41SiOBpoyfolsWgNIkTkyC+n50VUeiVEoF+jQqjzs/C2uw3xJsdKR8k9gUWeb5sn7vDVtHKd1VU9KNjht5y58Hp3O5FmLdE/KZZpT5pntm0RgO72fSp/abh1+zzM7/arDfO/PpZULpxsQSaNaT9frRl8GLzqIGc6B+PdfZli+t7mslPJSfjzI/zzvVo2B003r/v98+b82b9w2w6HAw/D1qX5/P6aDIfta+6835r1Pt1eHF+3ej0563BYTaLEWf/jpyqA6darX45TOwzchsLa6azmirmtM3G1FGzWjuefmacpDoUkv0J9O+bfUBKIU9MZKYatCTqZQtHnMrT2ANpTMSgFFmeaDB5mHv1VsDAA6HRQZg7FKWfZrW2Z/mxxn/TcH40zeOjMaJvRcr/L87l6fwFRYinUtfcT90YlEilD6bVFFqbwrQCP5VMr7NHyAVRzG+nOsTuza15AxymtXzEIIK2z5gYdCgMOS0hf9UYZVzJ6VxVHhjdGKLI5tr8pZOTCjbmS+cTcwh5li6ASJA5hm02SMI+wPqolfQ/TXct35QGcF2cr4UUW3KgaMV0iAhH3Un97Bwlkt0TDegO1s6OKdtFVWWa5fsrBELN6ZhRgAciQ1NwQzl6dZjyUqkgBq7RKCLa9CnUHvWwhU24Ocq6U3OqJgdpHBO5fjS+nbbxatIZvTajAkFaiAh5KYt0FqaQS8ILqAppgWJyB8hLozuUkLWxkq0StJQiTcy0JMFnCcs2xH0xi5TeOeiVkHfOsxPm/wbEr/wrn4ZMZS45Eglwu6jqRApz4/LBi6kCiuBIi6ScFx+ZsxDhNNvwBQXkE448yK9Gphiaf6JIrMwAKSERimkhGSjX4LDRjcrtVYpfm+4lyU6KJJXt9fZV2UOXTIep5/girvyQhdcuyoLfQlkjQ2yE8XycLB+QJirGA0mUlqmvU1kEaM5Fv3Smzg9EFsiMV/9KaKWJl2JbgYdK2Z+OJoQotv2QSK2ehbwnV9ESoBITxivFwrPxvBTGe4hilBnKnyiQRGJtyuvFSFCqjNxd6oHkoEE5Xw1NaZCxGgYTkPfM33+eFzDNkFbJhGwR2KoQs3DEfOAq6yYlASbEDwHVM57aDX1upbJarRyS7WbWClVVuepddgeTrl13qk6o4yjjyUQoHRO+Z/hUxzggmi3Fa/hDV5KIMJ69UvIPF3k3ucFFN8EWdhk1k3EolDYbDw9mTp3JaLMxy7+nYAj25tbC90Qy4hm6vnkwk6j5m24/fD3CsJ0R8Ktx8WR4jZ7/1nYSdtmuuOlV9yRKzX/Ywnewzr/tbczLsugsBli+0fZ9SPSeytGgYprlttO+607xZvMf2XEDIA==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieve a Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID or Name of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-all-statistics.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-all-statistics.api.mdx
deleted file mode 100644
index e3a4c4c711..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-all-statistics.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: retrieve-all-statistics
-title: "Retrieve All Statistics"
-description: "Fetches all metrics on all disbursements the organization has created. The response includes basic aggregations on payments, receivers, receiver wallets, and assets."
-sidebar_label: "Retrieve All Statistics"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWNty2zYQ/RUMnpIZ6mLF6YPelMRN03ZST+RMHhSNZ0WuSEQgwAJLKYqG/95ZkJKoi+3YvUz6YovE7sHZC/ZA2kiC1MvhRI4JSHlSsZfTSCboY6cKUtbIofwZKc7QC9Ba5EhOxV5YEx4T5Wel85ijIS8oQ2FdCkZ9A/YVGXgROwTCpCtuMhQOfWGNR6FMrMsEvZiBV7GANHWYBqeAXcA6QEbCYYxqia71UaxAa+RFMIkA75F8V0bSFugCxLtEDuUHZopLHGndCi6SWwpeDjdy0O/zv8N436JBB1rs3Xa8ZSRjawgNsRsUhVZx2LL3xbPvRvo4wxz4E60LlENpZ18wJhnJwjFBUvXOZAn07UH+Wk7KEKbo5HEpbthLmDKfoRN2fph/Gcm5dTlQDfDTpYwkfoW80CiHg34VySatt7EtDaHzD9NMHMzpLLG7t7qoOMuQrB/pN2CGaBJl0kd6vgixlR6TJ1D1ZRyjP5/9uz1fVpGcg9JP2jIU/7F+lxV7KuIHeV1X8vW2kK3iQs4v/e1sfRvORmsfcA7WMpKKMP+O4gf329gm2LL15LhALWby4/jN6zMMHt9dZ7Av+v1uvy/PtNQZ48HO+LSPzpi/2JsfN8+9TE475oz5y535SZvcCw5LdJA+kPG9+XErnTO+bKxP+2fUVOrupVfrUWiiKlSgHsC3zQD+QedI7ZcqT+iedDznGtL0PzvYB+f6Q5PiT3WG2+e7VoydHj5BLfa+98bR7/fblBo5bIloVfH6Zf/iVDs/Gigps059w+SfE0t0zrrTJq+YNTn4jv7zBFS27eqsMESO3p89cHWYu7zsaMj3lsRBmHsW230u+xct5GOPfxM4YHuMS6doLYeTjXyF4NCNSsrkcDKtpuxPmeVLUoohVcBLsufb9ySPrm6zyUaWTsuhlOy6RR5z6erctvH3UlOo33B90pK/froRPGrF3LpAHA01XREJr1KDiVgpygQYcTUevPxJFE4tgVAscM2XPAM5w4+amIMnKxqDZwgJ17Ti57kNbJomHhNqDU68aV2YxLUG4nMgRtfvZCQ53JrloHvR7XMOyjwHt+ajlKG4H+PZ+M31c6G8AEHWajErlaYQZvtK7AVZkcMCxazUi909l9+CSJ0ti+agqkKFBcsXXmrtbpBW1i26p6f9h6P42Xw2N5nyYUsjbIGm423pYhSFs3xOBWVAvFxTsUaQDfBn4OrrPi/wjUTEYMQMxdyWJgmOGT9obVfKpMJhYb0i6xT6IfPoiImv8XrN/0778twpmiR1ZhAv0CTTZxlR4Ye9XqooK2fd2Oa9RyE8H4oQ/I7KWvA4BGXqb0qNWYhKmbkDT66MqXRNgFwXeqim3UdENndhGv+d0LYQD8W2wpnY2j45mgx13okzcOTvpdyy65FD7OWgTK95cW88D4XxC+pcBKDAP8FC2zW314ORiNKz3aKcoTNI6LufeUwRutz/MR+jW6qY59I2rIZm17q0F4w6dt7xjVkktYqRv34ON7sBWECcoRiEOVXPZ8Ya9nqr1aoLYTWgNa6+9/u711fvx1edQbffzSjXYU4W1lMOpgW8/d4sRrr9Ffh43Gz22v6/+YGgkSbCr9QrNCjD8h9yt2k0cCL9wQ8hmfXEbzebGXj86HRV8es/S2RVmEwjuQSnYMYaM5lW0VaCWDQXyMIximMsWGSXoMtaGI/uQQeC/PbqRkYSTrR0EbS0+cDo2yWzbmEfq2JNgf9W0R0um02t1FW1s6+X7vRoQtxacxanVVX9BYk1YOY=
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve All Statistics"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/statistics"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all metrics on all disbursements the organization has created. The response includes basic aggregations on payments, receivers, receiver wallets, and assets.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"General Statistics response","content":{"application/json":{"schema":{"type":"object","properties":{"total_disbursements":{"type":"integer","description":"Total number of disbursements","format":"int64","example":20},"payment_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":2},"pending":{"type":"integer","format":"int64","example":3},"paused":{"type":"integer","format":"int64","example":1},"success":{"type":"integer","format":"int64","example":5},"failed":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":14}},"title":"PaymentCounters"},"payment_amounts_by_asset":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"payment_amounts":{"type":"object","properties":{"draft":{"type":"string","example":"100.00"},"ready":{"type":"string","example":"200.00"},"pending":{"type":"string","example":"300.00"},"paused":{"type":"string","example":"100.00"},"success":{"type":"string","example":"500.00"},"failed":{"type":"string","example":"100.00"},"average":{"type":"string","example":"100.00"},"total":{"type":"string","example":"1400.00"}},"title":"PaymentAmounts"}},"title":"PaymentAmountsByAsset"}},"receiver_wallets_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":1},"registered":{"type":"integer","format":"int64","example":1},"flagged":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":4}},"title":"ReceiverWalletsCounters"},"total_receivers":{"type":"integer","description":"Total number of receivers","format":"int64","example":1000}},"title":"GeneralStatistics"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-disbursement-statistics.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-disbursement-statistics.api.mdx
deleted file mode 100644
index cf8c9b86cb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-disbursement-statistics.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-disbursement-statistics
-title: "Retrieve Disbursement Statistics"
-description: "Fetches metrics on a specific disbursement by  `id `."
-sidebar_label: "Retrieve Disbursement Statistics"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWFFz2zYM/is8PrV3suW46R70ljbplm3X5eL0+pDmUkqCLdYSyZKQXc2n/74DJdly7Dh1tu76YlsiAH4fAAIwVxzFzPHolk9QoHQoE8fvAp6CS6w0KLXiEX8HmGTgWAFoZeKYVkwwZyCRU5mwVLq4tA4KUMjiirHPMmWfhzzg2oAVZOMy5RG/Jm1YwHlPvrdrwI2wogAES4BWXIkCeMRlygMuCYYRmPGH2C7PmZ4yzIB97hv2+1v4WkoLKY/QlhBwh1VOJp0sTA484PDN5DoFHk1F7kggyaAQPFpxrIyXRCvVjNf1HVlzRisHjtbHoxF9bWO5BiytcsytWbGptlsO4gFPtEL6Fa24MCaXiXdR+MWRjdUuBh1/gYQUjSWHomwQGFGRwftEl6rx2VMaqRVT7IlJhTADywM+1bYQ2Lz65dQ7RngXRSc1ERdpdaTeuA64AZWS947TfEWaonQUtqOhujJJwLkjNV/XAZ8KmT9rS9Qo8mP1TmvSlOjT8aqJ5NsukN4BTXBFQS/dfVzdC+egHz1hrajoaCAU3xF8r36f+Gx/mN49ZPzD5PztHgTHZ9ce2yej0XA04ntSao/weC28m0d7xF9txB8mz0EkuxmzR/z1WnwnTQ4aFwuwYvaExzfiD1Npn/BpK72bP2dtpB5felOd+SSqfQQSkAuw90uR54DuJ60jjd5MOgT7rOM5zcVs9r8d7K1zfd26+GPj4f759rbvuxjsr1fbveWGNJgqixgsdbyN7kEeo1EfUb9Dul7vrWuSOh2d7Pa0D0qUmGkr/4b0v2teYK22e/osQUcrviMJqceWfbnGNWSiAOf2nrqG5to5axj8vUa2RXODotvndHTSs/xQ40cabkLzajc077SNZZqC+vFx2c9uA+A7BDwPB0lpJVZ+wHsDwoI9KzHj0e0djVgFYKZpVpyBx0YDX8TDzTwV9mcpF65kWnOyahfd1FjanEeck7VuswmRb/j1t9x0UiP/gGrnxP3+8YZRJ/EzHIUEFLZ+DZiTMwUpW0rMmFDsYjJ+/QszVi4EAptDReNnO8CetdH0mt0sm4FIKVtrep5qj6Y9pBOEPBeW9Q8ru8oF0jFnZ1eXPOBEt0E5Hp4MR+SDsiiErahSZMAO23gxOb96yaRjgqHWOYtLmaOnqe1MqBaqY6hZIebA4jKfs3Yg8G8Fm1ldmrYOSSP9gl6A9ZN4t7sCXGo7H+4Ws58O4if1Sd1k0vktFdMG1MDp0ibAjNV0VhhmAmm5gaIVQ226/x4PzAVMqNQv0MDFEqFYDGyqS5V6xYwe8lwvpZoxC0Y7idpKcBHhGLBb19gL2+9BP+0HpnXSIBbJHFR69yJDNC4Kw5nErIyHiS7Coyy8jJgnv4ZSMSooQpKHM2CtmGcl1dQKh7ZMsLQtQYoLPhXT4RHMptbXs39DrTPxFLclxKyTfTabDPJikGTCojsIuScXogUICyFV2L44yOcpGr9BXjBvqPnPCSbXFaXXk0xY6UhuXsZgFSC44ScqUwi2cH9NJ2AXMqG61NFqYQ61nYVeaKCnA9eKBTyXCSjn20BXAI1IMmBjX6ea+ky2ojBcLpdD4Ve9tVbVhX9evr14P7kYjIejYYZF7uuk0Q4LoXqGuxuFbV5bdwpbdWe1aZPPvtNoewbCNwxNLqSiicOTWrX96pa7LQT9jsUDHsmUblgy7ZBkV6tYOPhg87qm119LoCJ+exfwhbBSxNQSbldkhX6n66uKR4m9uG5vPV6yQ3cje3l0DVFRN1yIvKQnHvA5VM1NTH1XB13vIljNwlmSgMGeys4IstXcf7244QEXO0147ptw+4Os74XzsJ02EOizDh5RWa2aFl/Xa/lm6VGNluKaOTGo6/ofs/+oyA==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Disbursement Statistics"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/statistics/disbursements/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches metrics on a specific disbursement by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns statistics for disbursement","content":{"application/json":{"schema":{"type":"object","properties":{"payment_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":2},"pending":{"type":"integer","format":"int64","example":3},"paused":{"type":"integer","format":"int64","example":1},"success":{"type":"integer","format":"int64","example":5},"failed":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":14}},"title":"PaymentCounters"},"payment_amounts_by_asset":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"payment_amounts":{"type":"object","properties":{"draft":{"type":"string","example":"100.00"},"ready":{"type":"string","example":"200.00"},"pending":{"type":"string","example":"300.00"},"paused":{"type":"string","example":"100.00"},"success":{"type":"string","example":"500.00"},"failed":{"type":"string","example":"100.00"},"average":{"type":"string","example":"100.00"},"total":{"type":"string","example":"1400.00"}},"title":"PaymentAmounts"}},"title":"PaymentAmountsByAsset"}},"receiver_wallets_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":1},"registered":{"type":"integer","format":"int64","example":1},"flagged":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":4}},"title":"ReceiverWalletsCounters"},"total_receivers":{"type":"integer","description":"Total number of receivers","format":"int64","example":100}},"title":"DisbursementsStatistics"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-stellar-info-file.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-stellar-info-file.api.mdx
deleted file mode 100644
index 53531040ab..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/retrieve-stellar-info-file.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: retrieve-stellar-info-file
-title: "Retrieve Stellar Info File"
-description: "Allows the wallet to fetch the SEP-10 server url, SEP-10 signing public key and SEP-24 server url."
-sidebar_label: "Retrieve Stellar Info File"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVltvIjcY/Suf/NSVuGQJm0hUeSAwBBJ2YBnIjUHIzHwwLh57antgKeK/VzaQsu1m022ranlBY38+PseXc7wlhi40qY3JABdMG0UNk4JMCiRGHSmWuc8aqXMu1xpMgrCmnKMBI2GOJkpcW+D1i+/PQKNaoYJc8cJLE1sIJhaQ5TPOIljiBqiIXW+lejKgRApEZrifvxOTGhmgUQxXGBjknKqOmMsW40gKRKHOpNCoSW1LKmdn9u9LukO5RAFMw4pyFrsZHXWcZXSBsGacwwyBSxpjDEKqlHK+sRwiKQwKYyENfjZlI1NuP/AzTTOOdikajd7IHwZX45DcXDcq7fuHVqflXz7ctlu9wf11o3l32xs8vvILSQFCctOsn1dvnysXreeni+pjI3iqXjRGftDuPl5eVLrt28dPrwNMIOjc+B3/ZnrnPV19Hez10eB7w4fe4G7arwdBvz2oB95VSIaoDQTNFvho1lIt4WcIMDOYzlBB5ez9h5BAuzfoPPf86WjQvQpJYkyma+VyIhX7TYqiQW0EmpLeb1dJqkVI4MG7ntZHw/bU85v9XscfnoykWfFQXIyZnuVKY4rCFDNOzVyqtDij0RJFXIxxdQpbprlJQgLDQd0PWt5gGniDe/fXPzurVP+LGTRmlWpIQjEeN3uN0UfPH9aHnZ4/mUBvcDP16x/toh1OJtRZvK9tjAYDz290vGAygUjGCFcQEm806DVCAkzrHJVrurm+blYvO62L7sPdZf/yY9O7DxoPg8tmf/Rwf+4/nTeHn7z7Vrfq14fV+qf2+XO32+rWPziUKdUazZSKKJEKY7gCo3KE/feh02yy/eRzRk1IQBtqcu1aOFthSMBemFN6r/MfBc0fmP6eXSjIbrfbFUiKJpHWPhZoSIFk1CSkRsqlNXJeXAq5FuXjRrurXSB7D7IeuCW54qRGyG5im6NcMbMJogTTvdVcI1Wo6rmF3BLLkdQIzdgdbsifDfP2YQi5xhjmUoE9sCgMi5y7FZwpYgxrZhKgAryg8uECMsVW1KC1SGtEgqbObXLjbtjelwuEWfAEaYyKWL1MzKVjw4xzp+OZbJ6cd+gfzjvU+x1SIFbunmWl9L50ZtcgT1OqNtY5rZt/E+OnoNl/Z72VgpGSwyxn3DiZUi2oOFDVNiBSukSY5XwJGd1YFNdKYaFknoGcg8KIZcx1SBsE5mR2sXei0l+W9sejGIpQDBOm3ZQCZIaiqGWuIoRMyV8wMmASamz3nooUYKSD/wpc4SWv3BWMqLBZNZe5iN3AxH7YPLa5qjCTmhmpGOqa5VGE8eGAl/+W901+Orrlgpkkn5UimZa/C+FdDZz4FyobsClKmdg/GA5lThUTc0W1UXlkcnUQaPfFvLWnpe9QNlcuxP+NtCPEW9rWOINj7T9WkyBPi1FCldHfpHxSVzYKsZxSJsqHhm/qeUtGG3kKDsjxjzHjcmOP15tKINe2bpnPUAk0qEuhtSmDKtW9eYBqxSLrS0dZpynriopyXtSHsgLhLEKh0Tra0QAzGiUIFedTe3+2WLVyeb1el6jrdWiHobrc7TQ8P/CKldJZKTEpdz6ZSW1SKk6Aj+/LF332hQmHJ+YXjrP941X4/zyED9HiHqAZp0yQ3UH79pBoY3KSaNbATzNtUiCJ1MZWbbczqnGk+G5nm3/N0br8eFIgK6oYndnMGE92hWOk2BBcog2CehRhZiN0RXn+wsbh23h8ydkbb0h2u98BxMo+qQ==
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Stellar Info File"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/.well-known/stellar.toml"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to fetch the SEP-10 server url, SEP-10 signing public key and SEP-24 server url.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Token is valid and the webpage will be loaded normally.","content":{"text/toml":{"example":"ACCOUNTS=[\"GBC2HVWFIFN7WJHFORVBCDKJORXXXXXXXXXXXXXXXXXXXXXXXX\", \"GDA34JZ26FZY64XCSY46CUNSHLX762LHJXQXXXXXXXXXXXXXXXXXXXXXXXX\"] SIGNING_KEY=\"GDA34JZ26FZY64XCSY46XXXXXXXXXXXXXXXXXXXXXXXX\" NETWORK_PASSPHRASE=\"Test SDF Network ; September 2015\" HORIZON_URL=\"https://horizon-testnet.stellar.org\" WEB_AUTH_ENDPOINT=\"https://ap-stellar-disbursement-platform-backend-dev.stellar.org/auth\" TRANSFER_SERVER_SEP0024=\"https://ap-stellar-disbursement-platform-backend-dev.stellar.org/sep24\"\n[[DOCUMENTATION]] ORG_NAME=\"Stellar Aid\"\n[[CURRENCIES]] code = \"EUROC\" issuer = \"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5\" is_asset_anchored = true anchor_asset_type = \"fiat\" status = \"live\" desc = \"EUROC\"\n[[CURRENCIES]] code = \"USDC\" issuer = \"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5\" is_asset_anchored = true anchor_asset_type = \"fiat\" status = \"live\" desc = \"USDC\"\n"}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/send-one-time-passcode.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/send-one-time-passcode.api.mdx
deleted file mode 100644
index c5df0dbf56..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/send-one-time-passcode.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: send-one-time-passcode
-title: "Send One-Time Passcode"
-description: "This endpoint generates a 6-digit OTP and sends it to the user contact (email or phone number SMS) provided in the request body, as long as it matches the receiver contact info stored in the SDP. A valid SEP-24 token should be included in this request's Authorization header."
-sidebar_label: "Send One-Time Passcode"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWEtv20YQ/iuDvSQBSMkx0gLlzUlcJH1ZiBT04BjJkByRWy932d2hZVXQfy9mSVmU7dpJH0AO1UXScnae3858y41irILKztU7qnRgj6ydVReJKikUXrfxb6YWtQ5AtmydtgwVWfLIFADh27TUlWY4W8wAbQmBbBlAM7ADrgm6QB4KZxkLhqfUoDbgPLS1swS2a3LyMP95/gxa7650SSVoGzd6+r2jwJC7cp0ABjDOVvKtGRrkoqYwyBWkr0ZGtF06COz8Xtf89WwCJ3CFRpcwP52lxy+A3SVZCLXrTAk5gbaF6W7s67Bz4EmAk45r5/UfMTlQE5bkJypRrqU+YW9Llak52fLM0kI3NMMQCleSSlSLHhti8pLljbLYkMrUgUaVKC1J7hWr27k/8HfpPOCBO0+/d75BzuDJS0JPHjZRcvvkmUqUxKA9lSpj31GiAq+N2A+6aY24R9etEUezJZogAkVNDapso3jdRkn22lZqu73otVHgl65ci8Shm2f5b1RwXwVtta0OaqwSJU/IsuzEtjW6iP5PfwuyfTOyvHf6XHkqsOWixo8xKkHm4JiL9iTDXurAmoJsjkY/DkbvhHE7t7MxDNnBqtZFHSEjeF5pYwQagSxP4FRzTR4+jS18Eix/iqj+BANmxPWJ2iYqLj/uw2k8E/+28duJe9SNxQ2+PL06mS1evRkOTI/RrXxuAyouhNbZ0Cf/+OjoHmAsZjEICF1RUAjLzpj138VDQyFgRY/jYCd4D5ITxZrjMfi5F3o3xKD6GF/cF8VLLOFdj/8v8f1hJ8l79xkofU2M2gTA3HUcAdJvFIxds8fwqKUYF11jPPV7w+qt7Xuitm3HaqxuqcmUH5fOqWz/e4wylQzrOfobmRw9WKIyCJ5zArSgLVNFvgdQzO7zu9l9b3dNLSr+b9P7+WlTgZG7sdzQWLbJQwD7i2T/4hgOwtx7sbPz4uj5SPPtHf+l4lia4+/ulubE9u0IQ3+Kh7le6Suy/XSXCWzZrOP8rzHYJwx03QpIYE08gTMrD5dM/mZd80GDO2ALWKG2k68JBnGW36eg7E/m/SAYsnqdyvaKbDrMz1QoTTowAfndV4xs0M72NOGS1ip7cGeirtB0NxpkPDfEtRMm0rrYpFrkWmVqukJjiFM/YnhTx61KVCB/tWMmnTcqU1FRoKLzmtdzSXCfgZ5bCG0ZxYqt/pHWd9rVD78upJDlDVkhy0PtEgi6slTCSnMt3eF0fvzNt9B6fYVMcElrqftnkCRJrODg3Z6SnO4PxiEJ2LfVYSLvF+5MyVFthUfGYIdhMWcyBj281iHvfKBGcDszyEvnGziZvZWakA99Eo4nzydHkuKuadCvI4cmeFjH0/nr2TPpsQjsnIG804ZjFp2v0A6ZiL21wUuCvDOX0OJatMRVhMq7rgW3lEOpWx0fOGHHPLJuiVfOX07ucoCvzsUP9oONlw8xacG1ZNPgOl+QXBgi4+QaWR73rjgL7KL6e9QlsUXJAzlYUKCVBrR0nS3jxlr+GONWQl89tS5odl5TyMSPFM5Dr286fKflKElpOyQpzbG4JFtePK2Z25BNp5XmussnhWumX6ThWQaL/ioyuLLe8ev+7jOIxai0XXoM7LuCOz8EKHXhx2o6+YLIlj625H8S2k7FY7GtKIed7N+OpibTpEWNnsODLo/kpuyJpg1qOx0WHoznsTDekGkgKor+l9QatxZ4PRoJdEHkLrucvCWmMPkgXZDJN+FsOSd/pQvpS7uwBjcnzlfTKJS6ZRoGsUQZXZBw3Gx/CW2xqAmOY5/q27/oyqbT1Wo1wfg0ahu2hulPb1+d/jI/TY8nR5OaGxPbsEybBu1IsdyE4cxSKndhGF2GD7rNZj/f/3+/cO/7hWHMMl3ztDWorYylWKjNMNzP1T3DXd5McCtXpFqIQHauNpscA733ZruV5d87kol0fiEkwmvMZb6dX2yT3XTdU5BXfYnShbiy5xx36Ng22e04KQpq+UHZMVeZnc0XKulJjFzbItNSHlcynXEllERetHBPjTb92kYZtFXXc9lep3z+BCT9qZM=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Send One-Time Passcode"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/wallet-registration/otp"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint generates a 6-digit OTP and sends it to the user contact (email or phone number SMS) provided in the request body, as long as it matches the receiver contact info stored in the SDP. A valid SEP-24 token should be included in this request's Authorization header.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"Authorization","in":"header","description":"SEP-24 token for authorization (Format: 'Bearer {token}')","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Object containing phone number","content":{"application/json":{"schema":{"required":["recaptcha_token"],"type":"object","properties":{"phone_number":{"type":"string","description":"Phone number to which the OTP will be sent. Either `phone_number` or `email` is required."},"email":{"type":"string","description":"Email to which the OTP will be sent. Either `phone_number` or `email` is required."},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OTP sent successfully","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"429":{"description":"An OTP was sent to the given user recently and hasn't expired yet. Only after expired it will be sent to the user again.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"code":{"type":"string"},"details":{"type":"string"}}}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/sidebar.ts b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/sidebar.ts
deleted file mode 100644
index 959989a851..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/sidebar.ts
+++ /dev/null
@@ -1,450 +0,0 @@
-import type { SidebarsConfig } from "@docusaurus/plugin-content-docs";
-const sidebar: SidebarsConfig = {
-  apisidebar: [{
-    type: "doc",
-    id: "api-reference/stellar-disbursement-platform-api"
-  }, {
-    type: "category",
-    label: "Administración (Gestión de inquilinos)",
-    link: {
-      type: "doc",
-      id: "api-reference/admin"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/get-all-tenants",
-      label: "Obtener todos los inquilinos",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/create-tenant",
-      label: "Crear inquilino",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/retrieve-a-tenant",
-      label: "Recuperar un inquilino",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/soft-delete-a-tenant",
-      label: "Eliminar suavemente un inquilino",
-      className: "api-method delete"
-    }, {
-      type: "doc",
-      id: "api-reference/update-a-tenant",
-      label: "Actualizar un inquilino",
-      className: "api-method patch"
-    }, {
-      type: "doc",
-      id: "api-reference/default-tenant",
-      label: "Inquilino predeterminado",
-      className: "api-method post"
-    }]
-  }, {
-    type: "category",
-    label: "Autenticación",
-    link: {
-      type: "doc",
-      id: "api-reference/authentication"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/log-in",
-      label: "Iniciar sesión",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/refresh-token",
-      label: "Actualizar token",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/authenticate-mfa",
-      label: "Proporcionar autenticación multifactor",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/forgot-password",
-      label: "Olvidé la contraseña",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/reset-password",
-      label: "Restablecer la contraseña",
-      className: "api-method post"
-    }]
-  }, {
-    type: "category",
-    label: "Claves API",
-    link: {
-      type: "doc",
-      id: "api-reference/api-keys"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/list-api-keys",
-      label: "Listar claves API",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/create-api-key",
-      label: "Crear clave API",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/get-api-key",
-      label: "Obtener detalles de la clave API",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/update-api-key",
-      label: "Actualizar clave API",
-      className: "api-method patch"
-    }, {
-      type: "doc",
-      id: "api-reference/delete-api-key",
-      label: "Eliminar clave API",
-      className: "api-method delete"
-    }]
-  }, {
-    type: "category",
-    label: "Saldos",
-    link: {
-      type: "doc",
-      id: "api-reference/balances"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/get-organization-circle-balances",
-      label: "Obtener saldos de la organización (Circle)",
-      className: "api-method get"
-    }]
-  }, {
-    type: "category",
-    label: "Integración de Bridge",
-    link: {
-      type: "doc",
-      id: "api-reference/bridge-integration"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/get-bridge-integration",
-      label: "Obtener estado de integración de Bridge",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/update-bridge-integration",
-      label: "Actualizar estado de integración de Bridge",
-      className: "api-method patch"
-    }]
-  }, {
-    type: "category",
-    label: "Desembolsos",
-    link: {
-      type: "doc",
-      id: "api-reference/disbursements"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/list-all-disbursements",
-      label: "Listar todos los desembolsos",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/create-disbursement",
-      label: "Crear desembolso",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/retrieve-a-disbursement",
-      label: "Recuperar un desembolso",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/delete-a-disbursement",
-      label: "Eliminar un desembolso borrador",
-      className: "api-method delete"
-    }, {
-      type: "doc",
-      id: "api-reference/list-all-disbursement-receivers",
-      label: "Listar todos los receptores de desembolsos",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/download-disbursement-instructions",
-      label: "Descargar instrucciones de desembolso",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/upload-disbursement-instructions",
-      label: "Subir instrucciones de desembolso",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/update-a-disbursement-status",
-      label: "Actualizar estado de un desembolso",
-      className: "api-method patch"
-    }]
-  }, {
-    type: "category",
-    label: "Organización",
-    link: {
-      type: "doc",
-      id: "api-reference/organization"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/get-organization-info",
-      label: "Obtener información de organización",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/update-organization-profile",
-      label: "Actualizar perfil de organización",
-      className: "api-method patch"
-    }, {
-      type: "doc",
-      id: "api-reference/get-organization-logo",
-      label: "Recuperar logo de organización",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/patch-organization-circle",
-      label: "Configuración de cuenta Circle",
-      className: "api-method patch"
-    }, {
-      type: "doc",
-      id: "api-reference/get-all-assets",
-      label: "Obtener todos los activos",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/create-asset",
-      label: "Crear activo",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/delete-asset",
-      label: "Eliminar activo",
-      className: "api-method delete"
-    }, {
-      type: "doc",
-      id: "api-reference/get-all-wallets",
-      label: "Obtener todas las billeteras",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/create-wallet",
-      label: "Crear billetera",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/update-wallet",
-      label: "Actualizar billetera",
-      className: "api-method patch"
-    }]
-  }, {
-    type: "category",
-    label: "Pagos",
-    link: {
-      type: "doc",
-      id: "api-reference/payments"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/list-all-payments",
-      label: "Listar todos los pagos",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/create-direct-payment",
-      label: "Crear pago directo",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/retrieve-a-payment",
-      label: "Recuperar un pago",
-      className: "api-method get"
-    }]
-  }, {
-    type: "category",
-    label: "Perfil",
-    link: {
-      type: "doc",
-      id: "api-reference/profile"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/get-profile",
-      label: "Obtener perfil",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/update-user-profile",
-      label: "Actualizar perfil de usuario",
-      className: "api-method patch"
-    }]
-  }, {
-    type: "category",
-    label: "Receptores",
-    link: {
-      type: "doc",
-      id: "api-reference/receivers"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/list-all-receivers",
-      label: "Listar todos los receptores",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/create-receiver",
-      label: "Crear receptor",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/retrieve-a-receiver",
-      label: "Recuperar un receptor",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/update-receiver",
-      label: "Actualizar un receptor",
-      className: "api-method patch"
-    }]
-  }, {
-    type: "category",
-    label: "Registro",
-    link: {
-      type: "doc",
-      id: "api-reference/registration"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/start-wallet-registration",
-      label: "Iniciar registro de billetera",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/send-one-time-passcode",
-      label: "Enviar código de acceso único",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/verify-receiver-registration",
-      label: "Verificar registro de receptor",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/retrieve-stellar-info-file",
-      label: "Recuperar archivo de información Stellar",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/request-challenge-transaction",
-      label: "Solicitar transacción de desafío",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/provide-signed-challenge-transaction",
-      label: "Proporcionar transacción de desafío firmada",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/request-registration-url",
-      label: "Solicitar URL de registro",
-      className: "api-method post"
-    }]
-  }, {
-    type: "categoría",
-    label: "Estadísticas",
-    link: {
-      type: "doc",
-      id: "api-reference/statistics"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/retrieve-all-statistics",
-      label: "Recuperar todas las estadísticas",
-      className: "api-método get"
-    }, {
-      type: "doc",
-      id: "api-reference/retrieve-disbursement-statistics",
-      label: "Recuperar estadísticas de desembolso",
-      className: "api-method get"
-    }]
-  }, {
-    type: "categoría",
-    label: "Usuarios",
-    link: {
-      type: "doc",
-      id: "api-reference/users"
-    },
-    items: [{
-      type: "doc",
-      id: "api-reference/get-all-users",
-      label: "Obtener todos los usuarios",
-      className: "método api obtener"
-    }, {
-      type: "doc",
-      id: "api-reference/create-user",
-      label: "Crear usuario",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/update-user-activation-status",
-      label: "Actualizar estado de activación de usuario",
-      className: "api-method patch"
-    }, {
-      type: "doc",
-      id: "api-reference/get-all-roles",
-      label: "Obtener todos los roles",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/update-user-role",
-      label: "Actualizar rol de usuario",
-      className: "api-method patch"
-    }]
-  }, {
-    type: "category",
-    label: "Exportaciones",
-    items: [{
-      type: "doc",
-      id: "api-reference/export-disbursements",
-      label: "Exportar desembolsos",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/export-payments-csv",
-      label: "Exportar pagos",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/export-receivers-csv",
-      label: "Exportar receptores",
-      className: "api-method get"
-    }]
-  }, {
-    type: "category",
-    label: "Billeteras",
-    items: [{
-      type: "doc",
-      id: "api-reference/get-all-wallets",
-      label: "Obtener todas las billeteras",
-      className: "api-method get"
-    }, {
-      type: "doc",
-      id: "api-reference/create-wallet",
-      label: "Crear billetera",
-      className: "api-method post"
-    }, {
-      type: "doc",
-      id: "api-reference/update-wallet",
-      label: "Actualizar billetera",
-      className: "api-method patch"
-    }]
-  }]
-};
-export default sidebar.apisidebar;
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/soft-delete-a-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/soft-delete-a-tenant.api.mdx
deleted file mode 100644
index 780aed7504..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/soft-delete-a-tenant.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: soft-delete-a-tenant
-title: "Soft delete a Tenant"
-description: "Soft delete a Tenant"
-sidebar_label: "Soft delete a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWW1zGjkS/isq1VVdsjsDGLCd5Rs2ZINjAwFMsnF8RDPqYbSekWYljb2si/9+JY2Gl4Bfkt0PV1f+BEit7qdbre5H4h5rMle4dYXbNGUcX3tYZCCJZoL3KG7hsYh0BxLQ0J4AJ1xjD2dEkhQ0SLPwHnOSAm5hRrGHGcctnBEdYw9TUKFkmVGFW7jXQSJCOgb0tVD0tYI9LOGPnEmguKVlDh5WepEYZYqlWQLYw/BnlggKuBWRRBmBMIaU4NY91ovMSmrJ+Bwvl9dGm8oEV6DMfL1WMx/bKApXKCogIAqasER56I7pGBHEBfchzfQCfaWF5IzoryhikBjvQsE1cG3UkixLWGjjVP1dGd33u9hE8DuENmLSRFWzAhmju/iNp8T63MIHx42jAGjDPw5+qfvN46Oa/yaK6v7hQRTU3gDUjn+J8NJzgd/VtO3yJAakC3fNggrqaaRikScUpUSHsd2TjGgNkqOv/7ki/l/+9c//stuzxhQkOYRCZsZuQBTMcpk8z/a4M0QBCW+AU6RA3oL8t0JGBbocnW8bibXOVKtaLY35bl1F0awi5NwYVzSb5Wz2/Rgue1VKVBwIIik6eZb9Lbua6Fzt3Tiep+YETbr9dn8yOx1125NuB3vlwHA0mPbGvUF/c7B9OulNt+U63fXg9dLDlBkTQW78mJEwFDnXM0KpBLUXxx63NSQJkcgtRm4xyhVQFAmJ1ib4HEU5p2o7IL+efmqfNT6dNabvG2dv3zU+XHTeDsbvL+r9i4vPJ+NBY9qbHHUvhx8+jjsf62fHzYt6YzQan+OH4BeYfwS7WfEkcLcTnd54MuqdXE56g/6sfXo6uOxPKuNJ9/y8Pap0+1PsPS7SOZlN25fnk4fkTnuj0/PuWuzB3Xo4aXYdLmTLIrmpbhWDZ7pv06iLPTzs9ju9/q+zy3F3VGZcb9C3eJmaUYhInugNeIEQCRC+g++kGEdRQuZIx8RWkDuF7mLQMUiL2NUYpgr8hW4kJOJCV6xGZ81W8qWHQwmkqLD7AhQJmZoZTIkGX7MUtjKzXqs3/VrDrx9PDo5b9YPW4cFnk3V5Rv95pete8Mxyy1JQmqSZCRDfjM4dUeiVEpF+jZzSyo/CWm52z6t1Ud4K7BNV5PG0fewMe67fr7PI9aPdCr2qnVu7c73hYdES8ZtmjYakeejTAxr5zWZI/TeN8MA/OgxrzXrjMKwfRqWZFpZAbUPa7EerCu4mdxrInv7x7ZpNWXd891fyfcGxNfPDtHMxHHT7jXfvzs6OmtNm/f3lZNAffOofnx5N68PxdNg+707Pjoe93wYnRxeNztn0uL8dTceHNs/Ivjyo1Gq1z9uBfURu6WHNtM0pR+aWS5NHjVpzlypNtrOWJBIIXZRpiwKIhASkY6aQyUNQ9pS/UKQXivRCkV4o0gtFeqFILxTphSL9v1Ck5r7XpBNCS+7j7eQxU+ZYI0gSNmdBAkgLFMAqp9FbIZHb3r2LN0uEGxWyEGQaxaRQHwBwQ03CGGjxilWsI6Fmt8ZfVzS/4WY/VX/6HjoGUgr59MHuFM9piAQi1xZIsXBpEllLop60ZGO9kfTOMO7xW5IwihjPco031dm3uVkkBG6tvyNHSu3J99x4QORKJiAScQCq3K4QjhjXMAdp97vY8T2kuC80eity/g++Bj4Q2+fHbJd38TwNwIY9BaXIfA+fcE7uCbVxMXIurhGUNpq15oZWPAIlchmCzcViVRk/BWEumV7YN+IToljYznWMW1fX5ql2O6zmldmdDETQ6qE5BR0LU/aKKfv0bFTganEgVPWe0aWpQpY0F8/RRcXCxkgJYWy2oojVCRAJskCyignJ2HtY7KTz2cfJmk+QXMfAtdtlDyk25+WRIxx1x/XDI5RJe+jQDSwq6zJsrAnJ/rIry0fyGAi12WZ+R8KicYWn5HUdpoJcKkiBazRMiDZNELWHPexh426Bsl45qNRMDPI0JXLxDTfcr+PVuDN8bQ4JQVqIBAU5S7R1U8g54Q6qPRwpuQEU5MkNysjCaLGjBM2lyDNDxSSELGN2Qtw6olNa56DvhLypPEpf/zcgfuFf+MRcZo1JjkQG3He5nUlhzl3B6phyUARHWmQlGf1GnYcIp3YiFBRQSLipMvaA2IWx+ZEk4s6wUwmZUEwLyUC1DA4fXalCX9V9+nQjSH7mglT27utXZYOeMx3nQSUUafW7NLxuoUlxk3dQFsiUN8J40YjK26nxivFIEqVlHupcOgfNvuin9rTyHZ5F0lbXv+NaqeIp3+4gQKXsD3sTQ5L6YUykVo9C3pCraglQTQnjVTfwqD9PufEOkhRZRcX9B7JELEx6PekJypWRu8kDkBw0qMoXU6Y0yFQNojHIWxZu3v0dTMMAq1bIF5GvnJiHExYCV7anlAUwI2EMqG7r1JpRtqrVu7u7CrGzVptbqqrnvdNuf9z165VaJdZpYutkJpROCd9Q/EDf2Ko1qyqv4U9dzRLCuL0FFQ8jRUO5wq6hYA+3GDXMOxZKm4n7e8ODL2WyXJrhP3IwNfbq2sO3RDISmIp9dW+YrvlOV39UfoNhRRbwq5EjJq/R/v9E98ItOxU3beqWJLn5hT18A4viv9elubG6pmIAFRPtMIRMbyzZYSqmT676bKd73p108XL5XzPDNpQ=
-sidebar_class_name: "delete api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Soft delete a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Soft delete a Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Deleted Tenant details, with a non-empty `deleted_at` field","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"304":{"description":"The tenant was already deleted before this request.","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"400":{"description":"Bad request, when the tenant is not elligible to be deleted. For example, when the tenant is the default tenant or when it has not been patched with the deactivated status.","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/start-wallet-registration.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/start-wallet-registration.api.mdx
deleted file mode 100644
index 88de9daca7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/start-wallet-registration.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: start-wallet-registration
-title: "Start Wallet Registration"
-description: "This is the endpoint the browser reaches with the first token so that the receiver can confirm their verification information through a webflow. Requires a valid SEP-24 token in the request."
-sidebar_label: "Start Wallet Registration"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVV1Fv2zYQ/isEn1pAttKg24Pf0jVYs3VdMKfoQxoUJ+kksaZI9niK6xn+78NRsuOkabysK7A92RLJ4/d9R353WmuGJurZpf4DGxOZgI13+irTFcaSTEiPM33RmqhMVNyiQlcFbxynh4L8MiIpQihbjGppuE0DtaHIiv0CnYpecQvDAsISzTWSKsGp0rvaUCcDhtQ1kqlNmSAo42pP3fCfW/J90ypQSyxq65dT9Qd+6g1hVKCuwZpKzU/PJ8fPxw2NG/f61GPkqc60DzhwO6v0TM8ZiN+Btci3eGc6AEGHjCSirLWDDvVMp6g600a0+NQjrfSXCuFtDH3EStWeFPTcouORmM40DdgrPWPqMdORV1Z2EcI60/g5WF/hbrRssQM9W2teBZkWmYxr9GaT3eAjcBFKif/BVIeB7s1XplIQoy8NMFY3+dvn8i9ivpJQMXgXMcr48dGR/NyBOCQxjqkFVyVISywCNKiWxlpVoLIeKqyUk3Ni7UrSXHrH6DjtjJ85b7mz8vA1QHfFeXXx22uVNtlG2mw2m0w/vw/mC6jSOcTIj9naFx+xlBWB5FSyGZRAIk+HEb5EBmOjgsL3w40aFm4kCUwQD+6UCOFn6IJkcLexPnOD3MaFnvV+uNqgrT7U3kvCt/8lP7tTkY3vC6DdnAJIOcQqKvaSLpB7ydggJVEHWZ99KetbJzfGk/kzBf5Ouv59vXRk4H5/nuu7ApPkHcYIDd530r+i8hvP6ha/GxTbfZ4fPduLfHfFEBlCsKOj5B+j6Lb+brttElFuvVhng0kg4FbPdL5MHjqhPRPNo5irznREut76aE9Wz7SW6x+x7Mnwai75GwR+gUBIJ73E3AkJwfyKX9rXL+8uvmatmYqmcVsTA6dO58c//KgCmWtgVAtMFjFa5snIcWvKyTFbhCodT3mufUJjOBndnNFaIPXSxKKniB06VucWWBxQnZyf6UwL3QHl8fTZ9Eg06LsOaLWtDw/GeDJ/ef5UbhUo9t6qojeWE01PDbgRarpNHSxQFb1dqAAriZLegmrI90H5WqqsCSYNeCm2vLe7Q156WkzvL2H/KYjv3Xu3bT3AKR/QTaLvqUQVyMtlHRoLE0co0iz4FP6ecNmukpS+wtSAFKhq37sqLZSuxVvrl8Y1ijD4aNiTwTgTHBN1GYd4+fg7qfZEmoRRpEkB5QJddfWkZQ5xlueN4bYvpqXv8kdFeDpTifwOyipVJTBuaMTGaYmVcTVBZOpL7mkkKHnhQzmdPoJZTcmLv4XaNsQhbkss1HbuP2bTou0mZQvE8UHIe/NyJsS8A+Py8cWDfA7ReIW2UylQwl9hsH4lx+sgE9VHmbfoCySHjHH6XmyKkbr4ez1Hujal+NKW1ghz6qnJ06SJrydxnJZpa0p0MdWGrQEG6djVcfKpwZ8l1izPl8vlFNJoijYujfnrs59O38xPJ8fTo2mqwuKTwUfuwO0FTs21Grprdae9vmU465va/v//wBirVmpRggXjpD1Isq7Hanmp76mWUiNSvbzKdOsjy7T1uoCIb8luNvJ6aOOlilYmQmGlCa/BRnxAzicj/OqpesSHyb0cFrja+wK6BttjKuXZN+B5/PfHQ9DufvzcYLySBzICUs8urzbZtsKLmsPqk7LEwHurbppMWb7re34+vdCbzV+5a2QA
-sidebar_class_name: "get api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Start Wallet Registration"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/wallet-registration/start"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This is the endpoint the browser reaches with the first token so that the receiver can confirm their verification information through a webflow. Requires a valid SEP-24 token in the request.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"token","in":"query","description":"The SEP-24 token used for authentication","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"transaction_id","in":"query","description":"The transaction id associated with the SEP-24 token","required":true,"style":"form","explode":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Token is valid and the webpage will be loaded normally.","content":{"text/html":{"schema":{"type":"string","description":"HTML page content"}}}},"400":{"description":"Bad Request","content":{"text/html":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"text/html":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/statistics.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/statistics.tag.mdx
deleted file mode 100644
index 3586c69ffc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/statistics.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: statistics
-title: "Statistics"
-description: "Statistics"
-custom_edit_url: null
----
-
-
-
-Statistics endpoints return general aggregated data per organization, as well as disbursement-specific metrics. SDP users can use this data to monitor their disbursements over time.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-a-disbursement-status.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-a-disbursement-status.api.mdx
deleted file mode 100644
index 3d8f15ff89..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-a-disbursement-status.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-a-disbursement-status
-title: "Update a Disbursement Status"
-description: "Updates the status of a disbursement according to the state machine. The disbursement must move from  `draft ` to  `ready ` in order to start the disbursement and trigger payments. Payments will start as soon as this endpoint is hit. A disbursement can also be moved into  `paused ` state by an SDP user to prevent further payments from going out and restarted when they are ready."
-sidebar_label: "Update a Disbursement Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWN9v2zYQ/lcOfGoB2Uqzbg96c5sWzX50QZ1iD2mAUNLZYi2R7PHk1DP0vw9HyY6dOMm6odtQ7CWyxLvj992RvI9ZK9bzoLILdWJC3lLABi0HdZmoEkNBxrNxVmXqvS81YwCuEAJrbgO4GWgod9xAF4Wj0tg5sNtaIjS6qIzFMZxXuO/QtIGhcUuEGbkG4KokPWO4En+4ItTlCq7AWHBUIsnXwJo4xt6f2ZbAZOZzJPB6FUmM4Wz4BdemrgdXHSA4Z+XJlQmAtvTOWAYToDI8hsl+5EJb0HVwkGNEWoKxEZ3XbcASrgaS+Qq0henJGbShh+oJlxJh1hJXO7h6rnMneXJtj50wosMSriu0wm8FmhBiCsYqUc4jaanFabmtxmS3ZtNYFJUor0k3yEhS1rWyukGVKVOqRBmppNdcqdvlPT2Rct5Oq0oU4afWEJYqY2oxUYFXtcQLpvE1qkThZ1+7ElU203UQg6LCRqtsrXjloyWTsXPVdZcSLXhnAwYZPz46ksc+kF8wBD1HeDdYqkQVzrKAydZKe1+bIuYh/RjEYb0z4Q3WC9X0cWQhDzhc/hELoeRJksmmR7ExPAA4UWw4sh1QbUF1wlvHDOyG2NtEMFRUdZ2Een6I7Qtdwjv81GLgLyH6MCMkcnSAj2Bm0uHxCP0G37GzbZMjSYgH0tXtZ2WAETnSluMNhM0kz4+OkvtSaAJYx/0ukC2V425W/+Hp+io+u1vF91a3XDkyv2P5zZbxrWPYo3kotc92U3vL42sG7kvz3d3SvHaUm7JE+/XrcpjdDYA/YdDTeH6XhjB+7Vr7bS+v2cDw0AJ4fu+mtVvPrxw7hg9YtGR4FXvrC9SENGm5UtnFpTS4BrlyZd9liyp2YxlU6W5bDenalF0aNh07IC037bqlWmVKSazNVFOpaJ/y3Qm3qdXe/ISrOy39x9/OISqUmaO4XdDysFgSCGZuRWwYrkS2vJoef/8DeDJLkTILjJJjUA6TYadFz42IqFCXUupO3mcuohl65ZSxrjXBXiLPas0zRw1Mzk5VooRuj/J4/Gx8JDlom0bTSmVKROLDMZ5MT86eymGtgZ2rIW9NzZGmo7m2A9QgJ3ijFwh5Wy9u1Bc70DAn13qRPISF8SYOuKXotp3ZLfK1o8X4Tmr/exA/2A/2XOSsTGnBebSj4FoqEDw52b7AlY4drofiLLDzG9F3K1zS6+kKoXAlRgmcY78RomMlL3XtrkXCEnoXDDsyGDLBMYKL0MdLh+dod/WP/JCkUa6LBdry8knF7EOWpnPDVZuPC9ekXxThaQaR/BbKCuSU1Mb2F5bBLLIydkY6MLUFtzQQlLrwYzUdfwGzGcVD+u9Q24R4jNs15rCx/ctsKqybUVFp4vAg5B27lAkxbbSx6fDhQT6P0XiDdQMxUMRfoq/dKt4kH91rbRC7RZsjWWQM4w9yTDFSE36dTZGWppBzaUNrgDl2NE+j0cjNRmEwS1RtChSJn22vThOviwrhOJ5T/fkssbI0vb6+Hus4GqMNriH9+fTlq7fTV6Pj8dG44qaO56R3gRttdwL3tzjQ+7y2F7m9M2d90/f/v4v/y3fxoe8yfubU19pYkTxxYayHfn+h9vq9SlQWL+BDy79MVOUCi916neuA76nuOvn8qUVpgheXiVpqMjqXlnqxlnDyu9xes+9dHE/eDbfgp3Dvpf4ggY2asCIllrpu5U0laoGr/v8H3WWXbBq/YOoHJkWBnndc7ojSPV10Njl/+UYlSt/RMIuoYYYfEv8goNtqpAchf7vkHpf1uldIXbe174fu9RhIbrkLh67r/gAA78jm
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Disbursement Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/disbursements/{id}/status"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the status of a disbursement according to the state machine. The disbursement must move from  `draft ` to  `ready ` in order to start the disbursement and trigger payments. Payments will start as soon as this endpoint is hit. A disbursement can also be moved into  `paused ` state by an SDP user to prevent further payments from going out and restarted when they are ready.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Message Response","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"Disbursement started"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Disbursement is not ready to be started"}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Disbursement is not ready to be started"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-a-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-a-tenant.api.mdx
deleted file mode 100644
index e468041e9a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-a-tenant.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-a-tenant
-title: "Update a Tenant"
-description: "This endpoint updates the Tenant data."
-sidebar_label: "Update a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1zGjkS/isq1VVdsjcDGLDJ8g0DWePYQACTbBwf0Yx6GK1npFlJY8K6+O9b0szwYvBLcsnV1fEFkPpdradbfY81mSvcvMYtGjOObxxMQfmSJZoJjpt4EjKFgNNEMK5RmlCiQSEdApoAJ1wjSjQpYQeLBCQxTD2Km/jKErYyGuzghEgSgwZpdN1jTmLATcwodjAzahKiQ/xQd6+DRGB1fckEfTGKJPyZMgkUN7VMwcFKLyMjTLE4iQA7GL4mkaCAmwGJlCHwQ4gJbt5jvUwspZaMz/FqdZNJA6VPBV0ail0DLpjSxoSAQUQV0iIPAAqEtHbpwj9fcA1cGxG/lH8xX3tahfcH+DYW0sRKM1Bm1yMKZqmM9u3bPwpA484QecS/BU6RAnkH8p8KGRHoanRRwisHK5rMUjb7drFXvTIlKvQEkRSd7ojURKfqkCTgaWySZ9Ltt/qTWXvUbU26HewUC8PRYNob9wb97cVWe9Kb7tJ1upvFm5X5PDxnu6ASwVUWtmqlsn9eWdbRdWqCJixSu8dDkiRivs3U8h/KsL38rBg9GISvxGZeEx81aice0Jrb8H6tuvXGScV9EwRV9/go8CpvACqNXwMT0Cz9X3IwWYIhw1BCPY1UKNKIophoP7QZmBCtQXL05d/XxP3LvfnXP+wl2djkRSn4QiZG7w/NtW0lodaJapbLhTI35yspmpSEnP+MxHxK/47e/3L2Opgyo8JLjR8z4vsi5XpGKJWgDtpxwG0NUUQkyplRzoxSBdSCz0YFn6Mg5VTtBuS39sfWee3jeW36rnb+9qz2/rLzdjB+d1ntX15+Oh0PatPe5KR7NXz/Ydz5UD1v1C+rtdFofIEfMz+z+XtsNxzPGp6fRKc3nox6p1eT3qA/a7Xbg6v+pDSedC8uWqNStz/FztMkndPZtHV1MXmMrt0btS+6G7JHT+vxpNl3OKMtStW2uHUMXui+TaMudvCw2+/0+r/NrsbdUZFxvUHf2svUjEJA0khvmecJEQHhe/adZusoiMgc6ZBYBFkotAhBh7BdxBDLynouGwmJuNAlKzHXZuvpysG+BAOzM6IPBSgQMjY72GCxq1kMO5lZrVTrbqXmVhuTo0azetQ8Pvpksi6rrD9YKIUIHhd6AG5ZDEqTODEB4tvRWRCFXikR6NcoF1r6XrN2atv1BpR3AvsMijydtk/dYSfvujZZlNejfYReY+fO6dxseZiVRPymXqE+qR+79IgGbr3uU/dNzT9yT479Sr1aO/arx0GhpoklUFuQtuvRGsHzzb0CcqB+POTZps2v72EkPxQci5nvp53L4aDbr52dnZ+f1Kf16ruryaA/+NhvtE+m1eF4OmxddKfnjWHv98HpyWWtcz5t9HejmXel23fkUB6UKpXKp93APkG3crBm2uZU3lJnPVL9UBd0SigaZW3tj2t9QEohn79EnazlQsQTqbb3J2NcmaTRkqhnNVm/thIsV4x7/I5EjCLGk1TjbXG2O58FQuDm5reBs/Utc/J1j8g1jUck4gBZW+8BIhwxrmEO0sY2i+7RgR6Tk1SHQrK/rOCfG96Xh22/zeFp7IGNfAxKkfmB8r16LNh9odGOmxsrCj31ytGW5IccP1NwdjT1/aMxpG9Fyv8vzuXx+AW5i4dCV98O3QiUSKUPppDnXEVqK/BTyfTSvsZPiWJ+K9Uhbl7fmEfxV9cXFObA3fx57HqCLt0cv83vTD1wxQTPnvS3sMTNJzkdfEeidC3BKIpBh4Jm738/tHMCYwUuZ1VXle8ZXRk8t8+PTFGG/Za98GJsTjML9ykQCTJzZh1WkrB3sNwDq/MPk01nZnIMuM4TxUGKzTlQtGA6NNjQHVePT1Ai2Z15/9/CsrQpaK08PS1nMdEIgVCLJeZ/IKw1OYQXHXKHKS+VCmLgGg0jok07gVrDngkVSJVZWS0dlSomBmkcE7l80GUflvFq3Bm+NhBIkBYiQl7KIm3dFHJOeG6qhb6Y3ALy0ugWJWRppNhVguZSpIlpaiX4LGF2Q9zlLWOhnYNeCHlbevIh8L9h4mf+mdthllHJkUiAu/n1SKQwVzfrj5nKTREcaZEUbf0DcQ4inNoNk+/IJ9zUEHvHLGNo/kSRWJg+X0IiFNNCMlBNY4eLrlUmr5x/u3QrSG6SB6nogm5eFa3OnOkw9Uq+iMvfJOF1E1nn16YskUFIwnjW9RfvfOMV44EkSsvU16nMHSwGXk+eaekbPAukBej/xLVCxHO+LcBDBe13exNCFLt+SKRWT5q8RVfWEqAcE8bL+cKT/jznxhlEMbKCspckJJFYmvR61hOUKkN3m3ogOWhQpc8GpjTIWA2CMcg75m9PUXIzTS9dtkSuCFyVkzk4Yj5wZctSAYAJ8UNAVYtTm968WS4vFosSsbtWWs6qyhe9drc/7rrVUqUU6jiyOJkIpWPCtwRnAz1E0HqQvAMz95sy//JBdV4TNHzV5SQijNvXZzaQysrPNc7LD3Zwk1Hz4gmF0mbj/t68P65ktFqZ5T9TMIh8fWNqm2TEM/h+fW9eGOY3Xc+gHzX71ShvUl+jw+Pug+YWdY0vt6oqdvIizChemUlBXoI21bmdqXUn2UOwYDQT65VTELV8HxK9tb3XP+1U7mFr0j4zb7l8gh7b0TuWZGFm9WRha/Vq9TcBCVu7
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint updates the Tenant data.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"List of fields to update for the tenant","content":{"*/*":{"schema":{"type":"object","properties":{"base_url":{"type":"string","description":"The SDP backend server's base URL."},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL."},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Updated Tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-api-key.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-api-key.api.mdx
deleted file mode 100644
index 37ff9fa5b5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-api-key.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-api-key
-title: "Update API Key"
-description: "Updates an existing API key's permissions and IP restrictions. The API key name and expiration date cannot be modified after creation."
-sidebar_label: "Update API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWN1v2zgM/1cEv9w2JPHW291D3rq2h+Vu2BVthz10RSHbTKzVljxJbpYF/t+PpO3EcdJ02Qewe2kdieKXyB9JLQMvZy4YXwfH5xPxDyxccDMIEnCxVYVXRgfj4F2RSA9OSC3gs3Je6Zkg6jtY/OZEATZXziEpUSRici4sOG9VTMfdSFyl0JILLXNgKvhcKCuJQhBzEUutjRcRiNwkaqogEXLqwYrYApONgkFgUBb/mCQrtZAzao2bhbTIHI+QNcuAJCGRSnBLkRWF9GnQN410K7X6VIJQCWhPkq0wU+E7SnsjSpaFxy18KpUFlO9tCYPAxSnkMhgvA78oSCBZrmdBVd3UxOiKVyZZEEVstEcZ9CmLIlMx2xJ+dKTKcpuViT5C7DeEXgcdd9NNFZac4hU4OtjdXPOR1srFlulv8CbJ0u79zaxEFROy2KfKtR4gF3rI3baZgwB0mZNeeE3JWGYZLs0tUjffvJwoF5XWQY7WuxVBf5VJLcSg7ukSW7LuCpMUcrHJqLPABMbOpFZf2Lsrot4iE5auK6j9xVtzVB86Mta/edt5ZISZEK9WMKCNRYKbahDkSk9qf73AX3jSzCG5VQU70Gj4d8oh2nfl5v1c4mIGlE4ySTCjnDBWnExOLwRe0gyCarB1wQ9cUtVnfUz0dPdr5tBj74JqCwd6mS2meKKTJyMxmQpKYozJe8ymZLCGi41zFsNcacy7OCVRCSbLIPDKZ9DL6os6f3C/6mceL7gC2dWRf/T8Of3r2dkkcJ29iXBlHKOt0zLLyF3fnI+bSYcQsyMvehC6hTE959El1ZD1GKvXZS71kGJORhgfjKg7mO2Hgq+NlENAYjvUv1Now21/lCICUSlZ3DJA7/Ae+iaXeMkBEQy9ymHLpWe9YrSJ/ySDqxAaJv03inifgt4oKnPpRMO1KyBafEUwIVCJeWra831lm3D/wcpmEm+lYd2VcpDGXSZ9tWnvFkH45yjuejjT9A0VY8vLXejxSiaiqeBiKO5lppI6RsBaw5WiAyDPwmeHYAazeNxvp+ClyrCvikzp2bD6IEe9t9I9KonNg88yLzLoCA4mmg0SShclHVqzQ3TKktupMUi1+hbKiRUAD5r1SNoVDX4LDZA4goWIejxk7WEGll1cO/nFtpPfaVn61Fj1hRn/cI9+vacCqulllw47mwjY2Tlij5ztgJfqIf++xTq4Ydlai1YO+qPDuX+i5ryrLv0saXxFv29f0V/GRirByvVT7me3+9YyD3HDxik25+XDTQF1KlNT6v9r2B0YHq2puyLjZTcyLsCZ0sbQcVArzkFcYje84O71FUgL9hhjCH/eULeI01dqknrUilMeyWgzCGWhhuhyFy5VUgXEx963c1ppMyThbrNlf0m+r53TFbLuJwpVj3ybF/v3+yuGee6GKLap16qdMxBOzTRuzZVPCZvOLo/++BMbVXVP9Z6a16Dtv4LjJi3aUYGnxxT7LcayQUCOvlhPdmdrf2/0XJ2R6KbXGXWiROmpYdOasnTpIcsQS087w5E4z6Sn6kdlDRUi39UmH41ejJ6TQ8s8l3bRDLT7eTy5PD1/SnguEapNJqJSZZ591h2RGMdzeQe4n92JdsSiVYkdoCkL6pJwNlOF4g2DWnGFaqVr8HNj70Y7Z+5fS8UP+oO+olZW8SMHZqceNkmAuUpZi8ekp+1aFWwCvCnaPrHHbsAPHLQRm4RfNqggcibxwZR+UDjUg1FhnPIYb+DGpMdQXLuaX9j8H3YH5WHROGkYyfgOdHLzJPW+cOMwnGFsl9EoNnl4EIenY8HGr1RZCMJDHNEcK9uQsVUYrogeOIDFvrSNge3wsfdORwdYNrUMx99jWsviMdvmEImW9putSSHLhzjL4vi/V+UOXegtQEhjcNgs7LXnMTNeI2fBjFj/BIrMLCi8HrUEEZPo7kosORi/4NA0zFiPSOb+nV4iUKuYcKk1q1FzhIkYMtHQTIeuIcMeHv/hSE6I1qJpIRHOxRHjVA32xAtZzefzkeRd5tYcdeGbycnZ28uzIR4ZpT7PGHTRbo9zb4dx/VAgmmfLPsp0Xtt+nffLpn55rMEhXi0WlqrxybKplddBWyuRfKwSKh0pmk47y2UkHbyzWVXRMhYgQvxr/LyXVtFjABdUDCD6xjo8lZmDPX55ctF09E/Fwe+gO01p67Om68D5oqRf+EkDHj/FVvQ61pRS0rXeOKk1Gl7R8fXBreaGXrzqE8dxDIXfS9vtR86Pr05eI3XUPMTiFdEhK+f0eod/WUvDLuK2g9eWOJHqWVl3RTVT7rm2mpH6hbT56Dzsbfqh31bUltSz7wNHlsu61amqFX299eCJxrcrl5MjUOv/ABnJXqI=
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates an existing API key's permissions and IP restrictions. The API key name and expiration date cannot be modified after creation.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"The unique identifier of the API key to update","required":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","required":["permissions"],"properties":{"permissions":{"type":"array","description":"List of permissions granted to this API key","items":{"type":"string","enum":["read:all","write:all","read:disbursements","write:disbursements","read:receivers","write:receivers","read:payments","write:payments","read:organization","write:organization","read:users","write:users","read:wallets","write:wallets","read:statistics","read:exports"]},"minItems":1},"allowed_ips":{"oneOf":[{"type":"string","description":"Single IP address or CIDR range"},{"type":"array","items":{"type":"string"},"description":"Array of IP addresses or CIDR ranges"}],"description":"IP restrictions for the API key. If not provided, existing restrictions remain unchanged"}},"title":"UpdateAPIKeyRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"API key updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}},"400":{"description":"Bad request - validation errors","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"API key not found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-bridge-integration.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-bridge-integration.api.mdx
deleted file mode 100644
index f7e6b348e9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-bridge-integration.api.mdx
+++ /dev/null
@@ -1,77 +0,0 @@
----
-id: update-bridge-integration
-title: "Update Bridge Integration Status"
-description: "Updates the Bridge integration status. Supports two main operations:"
-sidebar_label: "Update Bridge Integration Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWutv27YW/1cIfmoH+RE3XTd/um6ctGm6JIud9eYmgUFLxzZnidRIyp4X+H+/OCRlSZadR7sCu8AdhraWyPN+/MijBxqBDhVPDZeCdul1GjEDmpgZkPeKR1MgXBiYKoYLiDbMZLpJBlmaSmU0MUtJEsYFkSm4Nbp7Jw6a5CI1DS6IkTmZV25vl9zRi8vhcX90en5HX5MGOVJgWZ7dHJGYizmZSEWkmjLB/3JcpRhLpiIupnei0/QbyG9cmYzFpBeGMhOmzODquNe/GZ1cXI36x5cXg9NhldPC72R+J5sYUJY/S1MlFyy+EzSgG5VOI9qlmbWMU+a0MAkNqIYwU9ysaPf2gb4HpkD1MjOj3dv79X1AFfyRgTbvZbSi3Qf7kyuIaNeoDAIaSmFAGHzF0jTmoSXb+l2jPx6oDmeQMPyXWaVAu1SOf4fQ0GDLcVeOCxrcSbrffTSgqULlDAdtebjHBQ9tFBfTGo8hU1Mwnop1E4YJrxgDRJbQ7u3GxzSoe4PeBxT+ZEkaI7PNynVAIWE83iXIRKqEGdr1K7YlO8anhEWRAu0kQ28uQPGJNyh5Je1iFgckggnLYoxeSTINiliir2lZqt/lTPzL/2yGMkHpJlkcjwRL4GlTnWRxTHDpy4XBXVVZPsmZIH0JKMN8FY4c6ye9tUqByEmNeclJXER8waOMoUXHmeYCtK56Z/M0oIYb++js5ghp0/U6KEXzbR5G98XKWrZcMhPOfKhafzs+NvZkakbcxXyWJEytMDZSg/EldwQzDeiCxRmUA7gcdT6U6o6s+LGwbdm0hdaoY2jLxshXjZGvGlVBfU3aqiw7Zaynw9r+h8bUqRTamaPTbuNfVZ/uyGmX7RHRWRiC1qjbiv5tZeVIot12VxMuXFa6f4dxhhU6rw5MRERBbEWLmGFfXXSOMqVAbKqOnOzpTaWwPr8Yjo7Pe+8/H/dpYH+V4uLRwhTQ46uri6s9BeqRwB44bTBaMm1kAmrEo6eV82rke8hpv5L4+Hx00HnDxmGe+zWz7XFcreTY1lpyWc0hz5H3WvA/MiA8AmH4hIPadIG8e1fkR4EP3/4YweSry6f3dwpKY7CLCNRUYpyd3RztLZLfr4082SP+KbXZRYv1yGN2yBSvO/nqs9U9dLnvjb3fDDNjUt1ttcY2mJvaQBwz1ZRq2pqvwlYRAEbqb5OIhSGkViADKrHFQINa8BCeK5CRuiTQzoTa47JaQnm4eScaREiDdJSBqGttlSqJxRhfkJWDTPgS13Lh7QrVpX4JGWfGbstX4R62ZBzVHmVj2SU9/4tcx4YnFuqBgAkPOYvJxVKAqgiKBGzejBQsOCwdW52NE641z5OKuJeWmwXBuSoVnfNXuEwBFp6dy/JXuCxlmd42i3uGb+VkYrE9rjjKq2Dx8K6cESUr04AWdqQBLRuIBrSsLr71UlNssU4yrH5WCMT5G3bV9NqiUkqxotpjSD8bPucxO3Ax68OZiRDKwZSCwEbaJcOtGN9Ek9vnDFg4q7a8WFYyoqdetkpF6ZKtcoWHF4NCYWdALsVIAdNSlPVmSjHEHtxAssMe6/qZxVLYFNoNbfKKT4iHLeO4ioZv6enG8ySSYZaAMHlR6vnSXYnGCeMxqrmBctGImUdrECKqhuEJ1Hz4ZQai0u/IkmniyVaKUKfdedtoHzTaB8N2u2v//893xQdbaJxHFaQbbFqe5VhqD6W6XKmIleCuyn1fyYbPXMxPxUSidjtA8uM45bets3gZVGJcXA/6JIJUam7qB9dvgyx1sF5YdsFG7376+c/VX6jUcxN8W5dSUrPQ8AWz1TK/r+DaPQWPlVm0sqLl2uK2CHZvLD2vZPfmqZWt+FVN8dKi3I1edM+iSPcIFhCjyUcTgFEKKgSxM3eqlujn28gELHjDbWwKhGnCyGZTIVO7+fY7g2ctMxXCyFt3xIU2KrPV5hlo+j0T89wxpLzVeky7mmpj1cg9sVWN3DET89E4b9tq9UxcfF6CxEhiE2olUhUjDBz28eclZ2I8T4Wr5568wmpUVqhnOkKSVpmXK6AgBL5AwyGBCuEvEMeanDA1lRsGHpY/zSNvAk+zOei8Ib/g7eXABGTABDlRTIRchzIgR72CszPySGTJGNQzArPsGbdpvw0POm8O3/747qef2xt+SmYWzLyIn9/k+W2xOGi3253Dn5BDylbYMUeK8fhbmre/AoaIeIrEUtyrKBanGQ3okiug99vdanc+lKK1HGVbAbHbS7ttua3//b4S2HcqnJbLhLOB4cLBjSerRr9YTEIpJnyaqaKzhVIswBpwkomo3tzKgj4dA5clJ3gfFJKWg8Gfhl5WCiqaFC6pVAJbZZ+dpHlhKh+2i0y9HvSrp/sP/V8vO2eXv344O/148+nDv8+vT28ufvnYu7ruXR313vU/Dd+eXHROTi4uzm7evO98Gfz68cPhlzfvbE7FMpyHM8bFKIFEPiOfNhsIbtgAhpJJiVFMaBbWzGvTuQbGKr6sRHVusEcCsfDjToy3QWi7e3W1qT7eB6vxvVekHOxJPF2MuBiNnxFC19q2aLKcSWI3WpNW5jylm96t4AKFcKzC86sh/JAnoA1LUrJEMF+dNFnB9smxD9Jvgd5Rfsp4qVn8vifBadke+3j/XebZnpW97Ljz8gmBiy17HX7YPqjfgF8LlpmZVPwvK0DpmvuH1g+P32xXyysoJXf0VjuUMIrtBIVP3GD7HrMOaAJas+kOPOQ025htIwY9l4ZUNCukyPkctg9KlLd3OMq77vq/Fzfrojd1F51INeZRBOK7+Ge3+QqeLzFDZZdV57CuDmp+IjPxvxpuLwyLiVd1V0QcliPiClwrsddSblfOzrCpxnz3J7TyuPweSZiZxJF6itNAC8lwWk79fW2Db03X1QKUtsP1TOFEj+JUPR+6D9D+zkDl0XsBa1N+Bqtalfv0ZYjT1shdK2dmhrcDzkAB0XwqICJLbmaECXI86Lz9kaTKHprJHFZNGlA/Puz5lMilxQEmnQGL0DHrgKKxr4oPAI4Lm3/HmSWKMXE4x5fZHG31uR5nSoOFipcxM9gQSO/yFCeVoLQzTqd50Gyj6TfjzeEMyOM0Xg36l6/tnQYxUsZknPHY1D7lsFPuhM2BjLN4np8c7FNGpkpmKZ7aFIQ85faFXIDDXjl3AWYp1bxZ71v/OBHvxJ0Yzri2LO0XMqLhUyZVEnOcmBmz9zlOFISVMs3PrVvkAntNhC9CGQEJmSBjcHlnN87wRxzLJeJn5dCdVBzw/gmvkm498G/5vxtRyUiN1BupMWbhHER0/yofoky5mWVjjMLWiyi87hKr/EaUFZ54DONC++sLu8xqxcVEMYdDM+UVzEH3oz5tvkCzibLF+1tUy0k8pdsSxiRf+9XazCBOGuGMKaMfFbm0rmUUQAu/x2r5B4/q85QaHyFOiCWUn+pjubLTtydzDWvRlMyzMSgBBnTTXlPaqd3FxM8/SpO6yogOFzXkpFGM9mIegtC2bOZ1N2XhDEjH1inXFpBWt9VaLpdNZt9aan6rbn0+PTo+Hxw3Os12c2aS2JbnVGqTMFEifF35eKrUucigOGeV6s5DgQn+//Fc6eM535QM/Glaacy4wLZkHfXg+/0t3dHv7wM6k9rg24eHMdNwreL1Gh//kQG2ott7/KZGcZwL2S/sgrzdIkCYg/0Yx3mkMXSTDv8JTh0ErYN8R8+Oyh5dWwYul73h0Ue8YfLf9CUywk2K4ZwQ/+xS+/3g5nbZPnugMRPTzKEnR9RisxpgmVvA4v+BauWvxKok4jb0cJrgn6jXzi0PDw4Ordeb9e7V3h3etvlqdOP9er3+LwM3yU0=
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Bridge Integration Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/bridge-integration"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the Bridge integration status. Supports two main operations:
-1. Opt-in to Bridge (status: "OPTED_IN") - Creates KYC link for organization onboarding
-2. Create Virtual Account (status: "READY_FOR_DEPOSIT") - Creates virtual account after KYC approval
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"required":true,"content":{"application/json":{"schema":{"type":"object","description":"Request to update Bridge integration status","properties":{"status":{"type":"string","description":"Target status for the integration","enum":["OPTED_IN","READY_FOR_DEPOSIT"],"example":"OPTED_IN"},"email":{"type":"string","format":"email","description":"Email address for KYC verification (optional, defaults to user email)","example":"john@example.com"},"full_name":{"type":"string","description":"Full name for KYC verification (optional, defaults to user name)","example":"John Doe"},"kyc_type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"}},"required":["status"],"title":"BridgeIntegrationPatchRequest"},"examples":{"opt_in":{"summary":"Opt into Bridge integration","value":{"status":"OPTED_IN","email":"john@example.com","full_name":"John Doe","kyc_type":"business"}},"create_virtual_account":{"summary":"Create virtual account","value":{"status":"READY_FOR_DEPOSIT"}}}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Bridge integration updated successfully","content":{"application/json":{"schema":{"type":"object","description":"Complete Bridge integration information including status and related data","properties":{"status":{"type":"string","description":"Current status of the Bridge integration","enum":["NOT_ENABLED","NOT_OPTED_IN","OPTED_IN","READY_FOR_DEPOSIT","ERROR"],"example":"OPTED_IN","title":"BridgeIntegrationStatus"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"kyc_status":{"type":"object","description":"KYC verification link information","properties":{"id":{"type":"string","description":"Unique identifier for the KYC link","example":"kyc_456def"},"full_name":{"type":"string","description":"Full name of the person undergoing KYC","example":"John Doe"},"email":{"type":"string","format":"email","description":"Email address for KYC verification","example":"john@example.com"},"type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"},"kyc_link":{"type":"string","format":"uri","description":"URL for completing KYC verification","example":"https://bridge.stellar.org/kyc/456def"},"tos_link":{"type":"string","format":"uri","description":"URL for accepting terms of service","example":"https://bridge.stellar.org/tos/456def"},"kyc_status":{"type":"string","description":"KYC verification status:\n- not_started: KYC process not yet started\n- incomplete: KYC process started but not complete\n- awaiting_ubo: Awaiting Ultimate Beneficial Owner verification\n- under_review: KYC submission under review\n- approved: KYC verification approved\n- rejected: KYC verification rejected\n- paused: KYC process paused\n- offboarded: Customer offboarded\n","enum":["not_started","incomplete","awaiting_ubo","under_review","approved","rejected","paused","offboarded"],"example":"under_review","title":"KYCStatus"},"tos_status":{"type":"string","description":"Terms of Service acceptance status:\n- pending: Terms of service not yet accepted\n- approved: Terms of service accepted\n","enum":["pending","approved"],"example":"approved","title":"TOSStatus"},"rejection_reasons":{"type":"array","items":{"type":"string"},"description":"Reasons for KYC rejection (if applicable)","example":["Incomplete documentation","Address verification failed"]},"created_at":{"type":"string","format":"date-time","description":"When the KYC link was created","example":"2025-01-01T00:00:00Z"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"}},"required":["id","full_name","email","type","kyc_link","tos_link","kyc_status","tos_status","customer_id"],"title":"KYCLinkInfo"},"virtual_account":{"type":"object","description":"Virtual account information for USD deposits","properties":{"id":{"type":"string","description":"Unique identifier for the virtual account","example":"va_789xyz"},"status":{"type":"string","description":"Virtual account status:\n- activated: Account is active and ready for deposits\n- deactivated: Account is deactivated\n","enum":["activated","deactivated"],"example":"activated","title":"VirtualAccountStatus"},"developer_fee_percent":{"type":"string","description":"Developer fee percentage as a string","example":"0.5"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"source_deposit_instructions":{"type":"object","description":"Bank deposit instructions for sending USD to the virtual account","properties":{"bank_beneficiary_name":{"type":"string","description":"Name of the bank account beneficiary","example":"Stellar Bridge"},"currency":{"type":"string","description":"Currency for deposits","example":"usd"},"bank_name":{"type":"string","description":"Name of the receiving bank","example":"Wells Fargo"},"bank_address":{"type":"string","description":"Address of the receiving bank","example":"123 Main St, San Francisco, CA"},"bank_account_number":{"type":"string","description":"Bank account number for deposits","example":"1234567890"},"bank_routing_number":{"type":"string","description":"Bank routing number","example":"121000248"},"payment_rails":{"type":"array","items":{"type":"string"},"description":"Supported payment rails for deposits","example":["ach","wire"]}},"required":["bank_beneficiary_name","currency","bank_name","bank_address","bank_account_number","bank_routing_number","payment_rails"],"title":"VirtualAccountDepositInstructions"},"destination":{"type":"object","description":"Destination configuration for converted funds","properties":{"payment_rail":{"type":"string","description":"Payment rail for destination","example":"stellar"},"currency":{"type":"string","description":"Destination currency","example":"usdc"},"address":{"type":"string","description":"Stellar address for receiving USDC","example":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37"},"blockchain_memo":{"type":"string","description":"Blockchain memo for the destination transaction","example":"12345"}},"required":["payment_rail","currency","address"],"title":"VirtualAccountDestination"}},"required":["id","status","developer_fee_percent","customer_id","source_deposit_instructions","destination"],"title":"VirtualAccountInfo"},"opted_in_by":{"type":"string","description":"User ID who opted the organization into Bridge","example":"user_789"},"opted_in_at":{"type":"string","format":"date-time","description":"Timestamp when organization opted into Bridge","example":"2025-01-01T00:00:00Z"},"virtual_account_created_by":{"type":"string","description":"User ID who created the virtual account","example":"user_789"},"virtual_account_created_at":{"type":"string","format":"date-time","description":"Timestamp when virtual account was created","example":"2025-01-01T00:00:00Z"}},"required":["status"],"title":"BridgeIntegrationInfo"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-organization-profile.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-organization-profile.api.mdx
deleted file mode 100644
index 99346698cd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-organization-profile.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-organization-profile
-title: "Update Organization Profile"
-description: "Updates the organization profile details. Only account owners have permission to do this. Note: both fields are optional but at least one should be sent in the request. It is not necessary to set the header Content-Type for this request. It is set automatically by the HTTP client."
-sidebar_label: "Update Organization Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWF1z27YS/Ss7eGkylSjH7b0PfHPTdJJ+2J5amTsd22ND5FJEBAIosJTKaPjf7yxA2rStOk17O3Mf6geLIhYHZ3eB3QPtBcl1EPmlOPNradRHScoacT0TJYbCKxe/5uK9KyVhAKoR7MQSnLeV0gglklQ6ZHBmdAeyKGxrCOzOoA9Qyy2CQ9+oEHgSWSgtUK1CBqeWMIeVpRoqhboMID2CjQtLDauWQBJolIHAGoRQ21aXsEIIaAiUiZw8/tpioAzeEagAxhIYLDAE6TteLiBFuxpliR5eW0NoaL7sHEJlfeTyGITnyJZsI0kVUusOVl0EebtcnkOhFRrKxExYhz4G4115F6lpNM9TiMRMDAt8Y8tO5HtRJBb82LSalJOeFpX1zbyUJPl1KGps4hN1DkUu7OoDFiRmwnlelhQGHtV2bSdWgbwya/E4icsagS3BVk8SOYOYRgaApg3EAXZmDdbDB4dr9pOZSRK5WCkjfSf6mRh5Pr/uCXx/cXYKaRSolgTsulQmbahh73Ce2hi9LCbobryyWtsdz91gF3KA2ynzGyMbvIUXCf5lHqcY3AG/P+zqLakGP1qDNy0VN7aqAtIhhNEMksnvgKlwI53zdiv1DWdYeSxv4cXKWo3SvMxhVyPV6OPc0RJ21m8qbXe809DIlcaSg20sZXDrsUC1RX/jca0Cpe110/B+XuMNYeO0pCdOD+MwjqcTQnY4IQkygDJbRSkT2PDwdJEMLtCUaVSFdCQBG0cdn4eUj9sSK9lquoWt1G06QIppW3L/K5LhjgXC2fKcDQrbOI2Eg+U9Z+A4/hXi31kP+Jtk+By+2F+JJ/vrSuRwJU5xd+bXp/H7DK7EgW2UDL88Os6PjpLRoe3BVuRb5PE/luuE+4ttUzGV4GTXcOR2MiWTfelsC5W3Dez32bQCMeO+z+C1VsWGB3+eLPWjMpu+v98H6LNE/FA2Ew2GX573Pe/dzrb+8Hrgaj47W/SqUkXKVGFLzK5E/8WVmVaUD8Ea0cc/rpLBWRNSZTs+OuKPhwXl7Acxm1ZP6ZweVlhEqAelcww6d7nBH25wz1fU0fBJcWOGpEjzq5+S0c8DYa6IwzZ6ACEOdsxU6koIbcGNqmq17kSKwNdHr546/d7Ilmrr1UcsP8f95/1E760/4CV7Ql6GTyMEktRO7UzbrNAzxDNB7B/GaqAhTm3sufdu3rMY1/n66NUE+fGMvxM4pearp6n5zvqVKks0f39eDnt3T+APGEQ/AhatV9SJ/HIvvkHp0Z+0VIv88rq/5jBQbVnOOElFzewkD4rFdCsLhvFcriNK67XIheDpI/oFe5scmq5x55V06gfsngiG7/+zhDZgGYsa5wANDYGcQVBrgyXsFNUgDby5OP7Xv8F5teVmssGOpQqXbBYeQ/pGtorBkwSMgVKmSrJpOM8XhFpLD9+qsGp9wFhgz7UkLlRwcv5OzAS7m1geZ6+yI45B2zSsh5LAeh7jxcW35y+5bEoga1neKk3RzWlgoxRq5AZh1erNWOrjWwlrb1vHUsRjoZyKA3Y7yItxdYPEAiM7qAH/vyhemSuz5JbNSxqwDs082NYXyKWSD0eSjCoMVOIFwo1i7BHcDKQp4wC3GiikYSVb2daUceIDOenR2aDIeoUhZx5zuAwJbzF8zstJkOZuCNJ8JYsNmvL6RU3kQr5YrBXV7SorbLP4LISXOSzT3WOg0j3UxoNZ9EqZystAvi2o9YOD6fLyiZxmn+FZ5WMB+yuujRCf8m2HKxht/7Q3NepmXtTSU3iW8sRuQR5x0UhlFsOLZ/35lBtvUTcQgSL/Ep223ahdnz9rbYi3mnaF3iBhyKIsIvRNOKsu0G9VwXVpdGugmVm/XkSjua3mYTCbCa0KZBmS7+8KoJNFjXAc61Sqz4yVLxa73S6TcTSiDVPD4sd3r9+cXryZH2dHWU2NjnXS2UCNNBPgdMuFqeiD+3vug5Izuef+8zPCMz8jDC2R8DdaOC2VYQUVc7Yfuu/lAyHJGra2gfj9fr+SAd973ff8+tcWuR9dXs/EVnrFl8vY2Gdj8+N2vUFuWVMXuLvxvUjkB3+P6GfjpJOiQEcT8ydK54GGOD9Zvn4rZmI1/O7R2JInMXIEnt0/JpbyiUrYRJUwPDD7cch0ExqP+31iy/+Z+8Ep+33SIH1/Z5+GfnfGEMLRmvN03ff9fwEWx+eE
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Organization Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/organization"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the organization profile details. Only account owners have permission to do this. Note: both fields are optional but at least one should be sent in the request. It is not necessary to set the header Content-Type for this request. It is set automatically by the HTTP client.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"multipart/form-data":{"schema":{"type":"object","properties":{"logo":{"type":"string","description":"The logo of the organization, file type must be png or jpeg.","format":"binary"},"data":{"type":"string","description":"A JSON string that contains the details to update. Contains the following keys:  `organization_name` (string): the new name of the organization, `timezone_utc_offset` (string): the new timezone offset of the organization, `is_approval_required` (boolean): whether the approval workflow is enabled or not. `receiver_registration_message_template` (string): the message template sent to the receivers inviting them to registration. Sending this field empty sets the `default` value for it. `otp_message_template` (string): the message template sent to the receivers sending the OTP to complete the registration flow. Sending this field empty sets the `default` value for it. For example: '{\"organization_name\": \"NewOrgName\", \"timezone_utc_offset\": \"+02:00\", \"is_approval_required\": true, \"receiver_registration_message_template\": \"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register.\", \"otp_message_template\": \"{{.OTP}} is your {{.OrganizationName}} phone verification code.\"}'\n","format":"json"}}}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"organization profile updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-receiver.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-receiver.api.mdx
deleted file mode 100644
index c281969ef3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-receiver.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-receiver
-title: "Update a Receiver"
-description: "This endpoint allows an organization to add and update information on the receiver, including email address, external ID, date of birth, personal PIN, and national ID number. The response includes all information on the receiver."
-sidebar_label: "Update a Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWVt32zYS/is4eEq7pETdZT1VseTEie06lhO3cXNUiByJiEmAAUA7qo/+e88ApCxZsmU3zW7P7r7ECjHXD4OZweCWGjbTtHdJzyAEfg1K008ejUCHimeGS0F79DzmmoCIMsmFISxJ5I0mTBCpZkzwPxiSESMJiyLCRETyLGIGCBdTqVK3igQxEFUo8QgXYZJHXMwIpIwnyKtAa4/AVwNKsIQcDjxi5cgpmXBlYo9koLTEtdPDE8+qEla8pSYiTyegKuTcKtKZFBoKPaDR7McsqlCPygyUXTyMaI++t16UsFCPZkyxFAxC1Lu8pYKlQHuUR9SjHGHKmInpfewOB2g/avq9FPU76lLwJecKItozKgePajNPUJzmaZYA9Sh8zRIZAe1NWaKRIIwhZbR3S808s5RGcTGji8UnJw20eSmjOVKsm3DEtUEjphySSONGZcyEMZlKtQYB9WgohQFhUMaP1R/xz4ZaOfkMoUE4FOJlOGirkhkYy+nY7tSmlfdhGaxubInQ0pCFRzOEdJeU0zIeeATC8CkP3d66SNgmtoyXMY92iz9ZCa4tsmzg7pYytPG9zcVYChg7W5/gK1I/4ll5bp7k2fDukG3KssKYDcPNjaW1vW7gBzU/qNFil2it3mjSe9jaj612p7tHl0jRzzIWPxWyK6FM6T2zl/+r1Rvok+HGHopTjNfy+Jy5WKcLNHT9GNkP7uDboKwHweZxcOc6IqU8MgDDeKLXw59lWVKEU/WzluI5Z2H7DiwxpdNuYzJpN7p+FLGm36xB2+8G4Z4fBQ1oA4R1BtOnBMidxH/VWq1WvdHuNjutJwTDHWOuVa3eaDQfjec78s+RhJ+QrCLVDHlCBQjmmJnHGetBveEHdT9onNeCXrPVa9UqQRB8tLssDUvGGZunIIzeIQcZdB6GoPU0fxbXlPEEoidyBNTGUsq44GL2PKYZ1wYUROMbliSwi6nmmGwsRmOWynxdD1OKzbHEGEj17thjWoMZh7ZyPKb2/Wiwj5odPdc63xVjr16+HDQ7hwfto4u3ndPO8WD4YbR/cdYZnL6/+NA4+bUxOH83/HBw1Dzpnzf77143Ph4dHRz1W1v824FIEFSCwOahMgH0HRt+2gT1mQjtOhLdoBE0alHTr0VB0292O3v+pB3t+VHYajdr0729bhdWfFLfrjGo70EdosCfwqTtN8Nm4HcnzY4fdBtt1m11mjVWX4OjTF1H3FhTHCbfbkiLRWwPopbfbLWY3+x06z4LAPxaO+i0OxBEMKm5KpruCK8PfKKYMKSvNcdc7dFYppCx2Q6+2JhM96rVa8fPsszWiVXnL6yzpevaQJIwNS76xx0hvP9L/03jlzeND28bbw5eN94dDw5+Hr09rp8cH398Ofq58eHwvD18f/ruYjS4qL/pNI/rjbOz0dGqohRSuaULWycYu9UtVH9HwnT99bfJ4OKaP0vG3qaMhGkzTkFrNoOxBmEekLZefw1PQRuWZuQmhvUmnKDE8n94lyDWTNfUsYnMDTF4FynifZudteBvKDAl6bg05Z9UXv5fKZ5YKbRhJt+OqchTvPMOzvoH59SjZ8P+4Ff799Xh6Hx4NhxQjx4c9V+9Gg7wOnw/72qXg0ZOwVLVOObaSDX/63vybzR5eQy3aXPXZNqz3b+PpLsO28etBWpN62uHzlAYNXfd+31yR719Db8uPNrc1tK/ZNjOu2vB39bFg1LyCfey4vawTE9AHKPrwhXbveuLezeuQjE9FNcs4RHhIstdsivF2Zv8eColXibK34RrsrwOecX3CVNLmglTRAC4EcAEXHo1MCuwdejWtlyYBMtNLBX/wwr+vvA+HbbNw1LclBYeLYrStmnJA2CfSEPW3LyzotTTDGorku9zfE/Bbmsam1tzINWERxGI778v2727M+AJBM6N5qYb6PGBzMV/RXg9HAbTwsVtEdBcjYAz0DJXIRCx5FpGwd4mfPtSTBMeGpymZmtjIuWmq/9JWB8CBKe0mZLXPIKomAFznNIqYNGcMK1lyO2c5oabmDAhTQyK5NqNau+0lbMlJyLNtcHclgv+JYdlXtMQ5oqbuR3cvgSmQPVzHGddfsLx6Vcf26AZCL8YpPoTGc39YsKLv4tJldBcCjf+vYI57T3K6dFrluRLCagoBRPLyM2Kw9jOlO1QrVp2wLp6y6MFRYvVdTlpzhU6aAWUjoxwv9yWrLpz13dk/C3MN4rVm4tzhDCys1/MMTg2daHgEc1n4g5vMhzVW22SKX6Ns9ormFdoefOj/SI9Wc5y/h0Di4r5IQ7arTVFER+5uxEZcD3JlQbsdslpwgw2GqR/eohggdLOynqlVgkQgzxNGbZTNlgel/FiNDj9wUYQMVImZJLzxFg3V18pbOlL2RWQSZ5ckbLvto8XZKZknuE4VEHIM24XJN5KzIp2AeZGqqvKBrT/PBN/E78J+3TD3WtNBsIv8kqmJB5OYmJmcNmZYl9xsnIgfE+ce2/BBYx4EjKB58wmp/ItZSrxaQizkIJMam6k4qB7aIdPLov7cbX460crIPlZAZI/YeEViOjTi3ISMOMmzic4Bag+S8IPPWKdX5oyJ5gDGUeEYyAFmfWKi6li2qg8NLkqHCxfRx7d08ozPJsqm4K/xbVSxC7fbmBCStq/7E0MSeqHMVNGP2ryCl3VKIAq3mqrxYdH/dnlxmtIUmIFWfsjyBI5x/Da6QnJNdJd5RNQAgzoym+YpgyoVP88HYG65uHquKkwE6faVUvky6mvCzKPJjwEoW35KhNgxsIYSN3mKZefUVavWr25uakwu2qlFay6enS4PzwZDf16JajEJk1snsykNikTK4Ld6wRhZOXhcS3R3N6V8v+Zh9miqBn4aqpZwriwUzBlHytcBb1cjmPxHafHI7wDx1IbXLq9nTAN71WyWODnLzlgUbn8hAVacTbBEnV5SyOu8Xe0fHJ9EPcXZ8U96wfy0PvuVpPL4izmK80B9Ypegkd08Qknpa6O3jUZ+06xf47sd4z4QrvwSqJ+GEJmVpY32ry1BuS0f77/mnquNend0tTOgahiN/g4zW5sw+FRttFWXNm2oviBNm516n6D4GzEf9HirSy3t65pWSyW9G7pQY4CqCV+6OJisfgTrog8jg==
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/receivers/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint allows an organization to add and update information on the receiver, including email address, external ID, date of birth, personal PIN, and national ID number. The response includes all information on the receiver.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Receiver`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"List of fields to patch for the receiver","content":{"*/*":{"schema":{"type":"object","properties":{"date_of_birth":{"type":"string","description":"Date of birth of the receiver"},"pin":{"type":"string","description":"Personal identification number of the receiver"},"national_id":{"type":"string","description":"National ID of the receiver"},"email":{"type":"string","description":"Email of the receiver"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External ID of the receiver"}},"example":{"date_of_birth":"1980-01-01","pin":"1234","national_id":"123456789","email":"john@example.com","external_id":"external123"},"title":"PatchReceiverRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Updated Receiver Details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}},"409":{"description":"Conflicting phone number or email","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}},"example":{"error":"The provided email is already associated with another user.","extras":{"email":"email must be unique"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-activation-status.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-activation-status.api.mdx
deleted file mode 100644
index 700651a292..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-activation-status.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-user-activation-status
-title: "Update User Activation Status"
-description: "Updates the SDP user’s activation status. This endpoint is primarily used to move a user into active status when they accept the invite to join an SDP organization account and create a password."
-sidebar_label: "Update User Activation Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV21v2zYQ/isEP62F5LfYefGnpWmHthu6AE6wD24QnMiTxUYiVZKy4wYG9jf29/ZLhqNkW64zZ+lQYNgXS9Ydj89zx3vhA/cwc3w85dcOreM3EZfohFWlV0bzMb8uJXh0zGfIJq8vWeXQ/vn7H46B8GoOpMWcB1+5DrvKlGOoZWmU9kw5VlpVgFX5kpZJ5g0rzBwZBCtMaW9qM9iYYIsMNW21ZCAElj5sq/RceaTVn4zSDHQAYuwMtPpSIwAhTKU9Ay2ZsAieNinBuYWxssMjbkq0QfWd3JAixucbFpOAgEfc4ucKnX9l5JKPH7gw2qP29Pqy+5IeTmRYAL35ZYl8zE3yCYXnES8t7eMVOpISyVslW4rOW6VnfBVx5W5r5i1pYkyOoPlqFXG8h6LMcccMHwkYHPXEWSzhbBQPE9mPkwEMYoCR7Mn0eISp5Du2U8gdrlZkkWgpi3L9kb640mhXgx30evTYDf5FcCXZbHkByjJXIvis+8mRXtsl222mHAtQOY94qqzztxoKJHS7ECOew1ZoTY7hEB727GNObfmM90+OjhOUR/FJcjaIhyfHvfg0TQfxqJ8mvVPE3slZSlFoATto773JNOlvoR5Uf22QtGv6j0W/prmVgLWwJLd4LNwjK55zYKa1e/gJDMXxaDSK++nJUTw8S45iGPT7cXo2SuQgOUVx1tuNTcNzh2bgsqFSP38Mvx1hik3ExlMucY45BYnC10LrbYWrqAE1Socy7UsZi9NhGg9PBxCfDkHGo2E/TeXwGE9GsAcKNH4rqFRp0EJBfksH2Jo838NXZwMdOeVD9Kgs8N0ULNA5mJEwFK5W6VuAY1WoJpK5Sgh0Lq3yfMnrpBv2+vtZda2h8pmx6svzUutwTqC1xj562vDeW3BPW6hrcEtPV0VS+2LjgP2j+VW1amDwD8azHZpbFOt9hr1+y/LXK76n4To0R/uh+cnYREmJ+vvH5XF2WwD/QCHwcCgqq/wyZP4rBIv2vPIZH09v6FTfx8JInKGOm74WJ0Yu4yaR6L12IWqnjHbByh0u+fjgyojPIa82FmijAn1mKMdL8CIjNwCh4F1KGdfd5gwnzHZO0wZtVlnK4WBiTWVCrq291ya0LZel+hkJ927w3v92Vc8ZqbEh4Kh9E7WIOTXTKNlC+YwmiDeTweiY5pM5zQp3uKQhoXHKeXNW1mgVGc8QJOUClWKdmoCmKRgTj3kOlr1WLqmswwK1Z5c5+NTYgp1fviN3oXU1ykGn36HC66qiAEuOvqLR6qCNHyavL1/QQAXMG5OzpFK5DzTbU5ALAxbcIUuq/I6VsCQr4SuwmTVVyUzKLApVqiAwc7T1YNfsrtEvjL3r7Ln2vwfxo/6ow7xJW2pmStSxM5UVyEprKBOZzyBMoTUUo5k3wfwj5qIwOZKAzjwToFmCLDWVlmFhRn/y3CyUnjGLpXHKG6vQjQlHzKauttdtnrFsOSkuGyfFCYg71PLmh8z70o273ZnyWZVQ1+o+y8KLcT1sb6AsGZUrULqe1Bu1wErp1ILzthK+sg1Biot/KqadZzBLbaiW/4ba2sRT3BaYsLXuN7PJMC9ikYH17iDkll7XW8RuAUp3mw8H+TxF4y3mBQuGAn6JZW6WdLyeZMIqR3p3VYJWo0fX+UhlyqMt3K/pBO1cCapLa1oNzI6xs25Qik0au0Yt4rkSqF1oMusCWILIkA1CnarrM9kad7uLxaIDQRqsNUtd95d3F28+TN7Eg06vk/kiD3WyNM4XoFuG63sXowmLbW9ebHP12ik6ravX/+UW2vQvj/e+W+agwqUiOPihaZfTMGGSL1oN8ybimXGepA8PCTi8tvlqRZ8/V0gtZHpDDdkqSMIN4GYVrfvVtp1f1M6MrwjDtn/TnZbG81rpPPBtifcmn51Wf3l+dfGWR/UQQHOykbTIwoKGcFiExh5x2Gvfd6F9Ny+EcS3Sy9bmXzfiGiP9EuJHlzw81MPBarXRr0V/u6Jx1FqbYnKzWq3+An7c+m0=
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Activation Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/users/activation"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the SDP user’s activation status. This endpoint is primarily used to move a user into active status when they accept the invite to join an SDP organization account and create a password.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"user_id":{"type":"string"},"is_active":{"type":"boolean"}},"example":{"user_id":"5ca230c9-da95-4bd1-b2a2-aa5d0df65efd","is_active":false}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Created","content":{"application/json":{"schema":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"},"example":{"message":"user activation was updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-profile.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-profile.api.mdx
deleted file mode 100644
index 4c9806858a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-profile.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-user-profile
-title: "Update User Profile"
-description: "Updates the profile details of the logged in user, including changing password for authenticated/logged in users. Note: all fields are optional but at least one should be sent in the request."
-sidebar_label: "Update User Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV91v2zYQ/1cIPq2FbKVZtwc9Lf1Cu3ZpsCTYg2sMlHSyWFMkyzvF8Qz978NRkj+SzFk3FBj2YtG8z9+P1N1pI0ktUGYzeRFcpQ3IeSJLwCJoT9pZmclrXyoCFFSD8L2SKIGUNihcFbeNWyygFNqKFiEkQtvCtKW2C1HUyi544RXiyoVSVC4I1VINlnShCMr00Bqn4twRZEIZIyoNpkShAggX81FG5C0JRcKAQhLOgsDataYUOQgES+yHcwrwpQWkqUyk8xAUW78rt3iuEcIIOZGD8gtXrmW2kYWzBJZ4+TR9yg8samgUr2jtQWbS5Z+hIJlIH9g9aUCWVjog/W5VA3u6SEHbhewSadQxKTRKmwclI3sPCNnuVjXewN348g3/Oef1QWT5QW23h5D986f4Oy1cI/dDymaNUAQg2XUcjsnSAUqZVcogxB30zmJPwenJCT8OL9HH9zLZp1V5b/j4tbPpZ2SVfY53EWayAUS1iPfyOPWj4oMUkSYmSP7SK/06JCwP2du6kHwTt7e9jTemFNgWBSBWrTHrgYvnJ8/ug722fMFd0H9A+TWwj+ODEFx4+N7cUlD4uAckRe2+nm2bHAK7OELenRs2pCHPHYkDmLssxjjPT57teb5r8S0d90fz/f2jeeNCrssS7Lc/l4fR7RL4GwoRB0LRBk1rmc028gWoAOGspVpms3k3T+TtpHAlLMBOhiI2yV25ngyvOq97CsGidhajlyWsZXbUMpE3yrRbDxyoAaodlwOvqKhjheAsZOq3ZRQh3EDoY7SB60q0HBFcMqM9afs4tswpr98Dp3t4Zj//dsWd4V7r0M4mAvXCQilWmmqhrHh9efrDj8IHfaMIxBLWXP8HLs6GKxItZSI1O69BlfwKdPy/cjGboVZcEhijgnilMW8DQsPd5cIoqlxoxNnFO2YJAvZZnk6fTU+Yg7ZpVGB+r2oQx318d/nq4onQKJQg57i1aUMRpgsLZYdUUZATjVqCyFuzFF6t2UvcVWIRXOu5DwcotNdR4G4gxB44RrdAKxeW03vU/vdS/GQ/2ataYwxphfNgJ+jaUMThg19AQbUiFvepOCvI+XESueMuEcqWUcBXXRTK8phQudaW0bDmP8a4FY8oAbxDTS5owIzzmIgZ9v7S4Tkp90ia+IGkSa6KJdhy/l1N5DFL04Wmus25k6Zf5eFJJiL4bSprwVVKadvPX4NaRKVtFRRSaAtqwwCQz4UeO9PpVyCrQiyS/wba6OIxbCvIxaj7j9HUYJpJUatAeDTlPb2UAkDaKG3TYeMonsdgvAXTiOgo5l+CN27N1+tRJKJF1lu2OQQLBDj9xGWKIDT4sbqEcKMLrksjrCHNqQuLNCpNXDXBQS2RRhfAI0622RZAr4oaxGmsU319Zl9Zmq5Wq6mK0uhtMMX0w7uXr88vX09OpyfTmhoT66R3SI2ye477kVrwTC12Q/VBqdkbqv8HXxRDwyK4pdQbpS3PUJHRzdAWZ9LvPqhqh8Rbm02uEK6D6Tre/tICN4rZnLtt0CrntjObd8nYlXa9+mVP3uSKA++aM3+ddMmodFYU4GlPfG+sOejjF2dXL9/KpO/wPP26ko2CWvEXkVrF9p1Ida9JL2OTHhac4yiy673gd9ttnyP/csYPmmw2/QjQdVv9XvSXFgNRozYfxLzruj8B2ak/fQ==
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/profile"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the profile details of the logged in user, including changing password for authenticated/logged in users. Note: all fields are optional but at least one should be sent in the request.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"first_name":{"type":"string"},"last_name":{"type":"string"},"email":{"type":"string"},"password":{"type":"string"}},"example":{"first_name":"FirstName","last_name":"LastName","email":"email@email.com","password":"mysecret"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"user profile updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-role.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-role.api.mdx
deleted file mode 100644
index 564a1cfb41..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-user-role.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-user-role
-title: "Update User Role"
-description: "Updates an SDP user’s role by  `user_ID `."
-sidebar_label: "Update User Role"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1Fv20YM/iuHe1oLyXLcpkD1ljYdmnVogznBHlxjPeko62rpTiVPcTTDwP7G/t5+ycCT7NhNlrTrCuwlkkXyu+8jJZJZS68WJNOZvCRAkvNIaqAcTeONszKVl41WHkgoK6an56IlwL/++JMEugpE1gnxgR/9dnYqPoxkJF0DqDj0TO+CGfkXV4GMJMKnFsi/cLqT6Vrmznqwnm8fJ4/5QnkJteI73zUgU+myj5B7GckGGdsbILaGQ43ecySPxi7kJpJMjfYsClF1MpLGQ013RGw2kYRrVTcVHEDL41xNnozz57FWz4/jp5k+irOJmsRKHeuxLp4dQ6Hl7ryZ1HAFFbOU801AZbkGQcu0UBVBeEKNs9Tzm4zHfDlM+Ls3MtpPjGqayuQhp8lHYpcvz1INRGoBd2k+kLzzC+JDbUmsAEG0oYJaUJvnQFS0VdV9czTHPx0f3dZ+aVXrS4fmd9D/XRYA0eGdbwpce1T0MAJ55dt9P9vWGSBD3JPiz9I00JBvnRcHMm9YbM95Oj7aQ/484nsC96V5crs0PzrMjNZgv39d7lZ3Q+ALHIIOgrxF4zuZztbyBSgEPGl9KdPZfDOP5HWcOw0LsPHQleLM6S62qmYyfN+nECwZZymgLKGT6b2RkbxSVbtD4INq8KXjftIon5ecBsUsZMKfCyV9+2C6eMUtmM9psZKpDNFbFVPOap+4fS03Xa4xb4ApH9btp18vuGlrUTgMtQbrh4JFgszCghYr40tu8K+mk+NnokFzpTyIJXTc0Yd8nAyvSYjkZsrgJSjNn8GGfxcusDGeyyKnHqpKoTg1lLVIUIP14rxSvnBYi5PzM84UIPUsJ6Oj0Zhz0Na1Qs7xRQnifowfpqfnj4QhoYR3rhJZayofZDpcKDtQJeGdqNUSRNZWS9GojlHCUyUW6NpGuEIg5KYxweCuAIXfO92CXzlcjm6l9v9H8b19by9KQ+FIK1wDNibXYg6iQccfofCl8mzuqTgrvAvwd8BFQlkdDPy6i1xZkYEoXGt1CCz5R1W5lbELgdA4Mt6hAUqZRyxm1OMlwzXWe0mKmyFJcabyJVg9/6H0vqE0SRbGl202yl2dfBXCo1QE8TsqneBOpQxnuAQxuAVVxhaoyGOb+xYHgVwX/1BNR1+hrMDQKL9F2hbiIW0ryMTW91+rKaGq47xU6Oleynt+iUeApFbGJsODe/U8JOM1VLUIQIG/hqZyHb9eDyoRLbHfss0ALXig0XtuUx6wpnfFFPDK5NyXtrIGmiOHiyQ4xa6IaXCLZGVysBTmy7YBNiovQUxCn+r7M2OlSbJarUYqWAPaEErJz2cvX72dvoono/Go9HUV+mTjyNfK7gH3S7LgLVkMa/JBn9lbk792Gx9Gg4drnzSVMpY3lsB9PQyhWdjZaLfFziNZOvJsWK8zRXCJ1WbDjz+1wI15NucJh0Zl3OZn8020nQI38/Flzze+4ONvBiKv+Jto63SS59D4PfOtVeJgdp6fXLx8LaN+qvLS6TQHoVoxd7UK4zKS6tZQXIahONwwx63JdnuHfz7eeo78lxnfGbJe9yN3s9n596Z/jBgStfXmcvA/Cn8DgWvBcw==
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Role"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/users/roles"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates an SDP user’s role by  `user_ID `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"user_id":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}}},"example":{"user_id":"5ca230c9-da95-4bd1-b2a2-aa5d0df65efd","roles":["developer"]}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string"}},"example":{"message":"user roles were updated successfully"}},"example":{"message":"user roles were updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-wallet.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-wallet.api.mdx
deleted file mode 100644
index 4bbd108e2f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/update-wallet.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-wallet
-title: "Update Wallet"
-description: "This endpoint is used to enable or disable a wallet provider. Note: the organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement."
-sidebar_label: "Update Wallet"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV1tv2zYU/isEn9rCtrKg24Pf0iZAs0saNCn6kAYrJR1bbChS4yWeZ/i/75wjynauXjcMGOaHRCI/nsvHc9NKRjUPcnol3/u5svoPFbWzciQ/KWMgBnk9kjWEyuuON6bystFBgK07p20U+JwC1CI6XFOlAeG8qHXgRyUWLEV03t3qGvxEnLkIUxEbwm31idC4ZGpROedrbVUEsdCxYdw9EaKEmfMgAhioorZz1NIpH3WVjPIP0IhFABpUJh+gBRsn6JzrwLPi0xo9+tjVqLF3GDdRmmohgidaVtLiC4J0jVuaCOhUbOR9Vk6PhZvt2ouEJJaLUA+/Je0BdUWfYCRDXBqSGXTbGQLA751xNS7NlAkEqBpolZyuZFx2jIweXZXr9XUvDUJ84+olIe7a8WmjvYRsABleORvRd8KrrjO6Yu+Lr4EOrXb0bU29kv2F1hQC2QxXfkXSiSNPFEYNgQ4NwK29pXMGlH1A0yUSlNEiRBVTuEsbc6GYFeZqTb/7BPJC6JwNvfrDg4MnicgUiJCqCkKYJWOWd/l4Vbx6moIWz6g57KdgAD5yZXhUR77vX3rQh2y87J17/Zj5b1Qt8kWPMMMSerMUleJcK5fM2JdM5Bcx04DJ0+oQKB9m3rUMyOdFiZEy2eP0ngv23vmHvt2/3WOISpsgVOlSZBP6g2u61ehV2KuJCdlEwEaxPLW3yuhaaNulPkgGcez7rzPnELV5prK0ucZRXi+V32DwWViAOuRMURZFR5iD50vpr+X1k1FlXcTKkmz9b7D619mSfQrt4GxqS2DCnwnI3r/H6sAjzJ/tuLo1a1CMJO2okhjZLvkKdgga1GFFbVzdl8+q4TKLZXQqiz7xQ7HS9RqXA/jbofQmbxAhqegFqJLXcXlB3PbOvwHlwR8lErNxUnX6J1g+iMwfP132fYr7AR7BG8vOj0TQc4tb3HEwEE4uDr//ATuIvqU+dAOcO7kLkDbnt12SG0IDqubAGUki8sO2Pp/s8DnUyFzBtJ05tjvXhosIhhrY8U6rEudGRbS4FUfnp6iNiOn9OZx8NzkgtlLbKr/MlfV5GS8ujs9fUmYoDHpnRJm0iUzIbivmjGjVDeC+ucHWuiQpvKrE3LvUUcX2UOlO84ZDqzjXB+0W4sL5m8mjxf+/ZeJn+9nyPEMqrcDUsuMcwZholHJ4TPGU05uCo0p03dCz7okboYyaNyps5litLZUWTgM+2NCLMW5BVdpD54KOGEwQpmTHWFyFXl6R/493x5Zxl0kal6q6wfnr+kUTYxemRTHHwE3lpHJt8U0SXk4FO78xBTsMFjOliWE0NsPYKwxXTH2M3Somnx2ke4n77nTyDZ5h56Ja+k9cG0Ts820BpRiwf9ubBkw7rhqcPsOzJu/giugBihbtKPLCs/7sc+MdShYsiO2vAefIJYXXXk+wHBLuJmG/wPiFgK5hxuLY24b3swuswrqiujS4lc2cYCIWDBq72Thk2EhiKwEaaaabgfmoU1irxSHXqb6SkywUtVgsJop3WVo+GoqfT9+enF2cjPHIpImt4YqKfsdW2R3B/bguNvP6nSKz2vbj/8WXSm5rEVtvgUGB/Wad2VzlDnolcwdF9FTztN4gZ7SxWpUqwEdv1mtaxrZEreIKH2+V1+Q4t9lMQr35/HiS0Rcf8lD1Ujz7wfOo1UOHttSecZxL9IaP2GH776v1NaJyMyW7+o23vfbxJR3fHnwwvqxHw4kjHPW7uIOluYyGiM0Mcn50+fYdAsr8DdXyx5f0akFfa/iXDXPMAM8avLaSRtl56kedXif9/gSILmh9
-sidebar_class_name: "patch api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Wallet"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/wallets/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to enable or disable a wallet provider. Note: the organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the wallet to update","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Wallet to be updated","content":{"application/json":{"schema":{"required":["enabled"],"type":"object","properties":{"enabled":{"type":"boolean","description":"The enabled status of the wallet","example":true}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Wallet updated successfully","content":{"*/*":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"}}}},"400":{"description":"Bad request, usually caused by the `enabled` field missing from the request body.","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"404":{"description":"Wallet not found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/upload-disbursement-instructions.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/upload-disbursement-instructions.api.mdx
deleted file mode 100644
index 58ed14ad06..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/upload-disbursement-instructions.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: upload-disbursement-instructions
-title: "Upload Disbursement Instructions"
-description: "Adds a file containing a list of receivers to a  `DRAFT` disbursement. This step is required before a disbursement can begin. The file must be a CSV and has a different possible formats according with the disbursement configuration, and they can be found at [public/resources/disbursementTemplates](https://github.com/stellar/stellar-disbursement-platform-frontend/tree/58873bbf36cff4614e603daf449079b1d9fad24a/public/resources/disbursementTemplates). The operation is idempotent, guaranteed by deleting and recreating the disbursement attributes when this endpoint is called."
-sidebar_label: "Upload Disbursement Instructions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtz2zYW/isYPCU7lGg7btrwzYmTWe/utJnY2X1QPGOQOBRRgwAKHEhRNfrvnQOSMnWJk03Tnc5O9SCR4rmfD+B3sOYo5oEXM36pQhl9gBYMBn6bcQmh8sqhsoYX/ELKwASrlQZWWYNCGWXmTDCtAjJbMw8VqAX4wNAywdjd5buLNzd3TI7sTtlNowILCI6pwDz8EpUHyUqorQcmdoRZJQwrYa4MqUHnuo0BWUmir67/zYSRrBEhKdY1eNJyNgRVamC19a3AwERVWS8p2KXChmEDe26sqdU8ekGZZskmNrDq3bPaRiOZQDZzsdSqyj0EG30FIR+buYHWaYEQbp80iC4UeT5X2MRyWtk2DwhaCz/8TsaaE9KjYCe1twbByBw9QP7dDz98/6ws62fPq7o+f356Ds9PnklRn5+/OPn+RXkqX9RCnp2L/MvietpV0TroMqUGKAmtswgGMzaPwguDQO1YMQkaMDXYSGqtB5FuD6onEL0qI0JgywYMQ2owGOmsMkg+KqE1yCnP+Nb1leQFf++0FXKMuisT0MeKJALPuBNetIDgCZ5rbkQLvOBK8owrQqQT2PB9mF5dEhYpyrFlnvEBa7xAHyHjAVea7AXVOg084/DRaSuBF7XQgQSqBlrBizXHlUuS6JWZ883mtrMGAV9auSKJKvUN6bKNGpUTHvPUUikw2Xiw9hDIjBOkaan1Hmz5M1QUrPNUK1QQSCNJHcSxn/k4X6ZGpewWDloWU8U7GNDq6deyjq0JCe0L4anzDkxaLrZNhVyK1WHblyJsFw7I7aphtQJNG0VazSGWAXBoSG21tktl5gWb3bnGGrjL2B20Qmm6UJK+RWujQbpagFe1qhJg6N6JVQLJJd0sCVR4IaWHEO5ueca71c4LXioj/Ipv6LPf9vRHcNaErrJnJ6f0s1vIV4R1IJiN2iqc030w+c+B5NaHCPlE/1oIQcyPtJAChI8iAXAsx99QZ7p2gWQhVhWEOmq9+joVUjo/OTlM9aWQ7F0H5W+XLnhv/ZFkKXD0InzeQm3tUf1HCrlXlz4GfmUWQivZQb2DCPvb9OPqVz6OJvnjpfB85IP/aJGJiI316leQ/H/jomvVEVS+NyPBP1GvAgqMYzkT2xL817Vrrx7jKAY/5yenX9Gkb2G4a82zw9a8sb5UUoL54/tyPLuHAL5AoEvj/DANyvgNkZ3/a3jVfYbHAHA+BsDO+9RsNf9g28l8gCp6havEe16C8OAvIja8mN0S+WgBG0sUytm0byciVPAd2hfytZKbXO1SqgB+MfCp6DUvOCeDg79ramtX97HXbX2FU/+E1QHz+Md/blgMIGn3S2sGDPaIyVhQcwOyo97CsNfXZ989Z86rhUBg97AiYthTu4t+uSXNgeU1ICT1e0P3dfdeUJio23VHpneYHnvbk2l28faKZ5zS7aI8m55OT6gGsW2JIBSceNDjNp5cX759SiRWMLRWszIqjSlN6+fC9KGmiacV98DKqO9ZT1T6OWjubXT9fKScSg/sAnyiRIN3A7i0/n56UNo/X4gfzAeThjhyaWicMJNu7mDOW1rDDBuRmH8XijUMrRtI4J65B+JYWQm7Ixcpjmkj8+BsUGi9glBQHBM2+7LBqhTVPRj5O0az3sLToptgt6GshmE4pGB7sZSVMrUX3fKLvk+Q+oKf6+n0v8hsGBm/wdT5udyWULJB9quzaUC3k6oRHh8flEdy3TTcCmXy/o9H8/lcGn8H3bJkKMUvwWm7Gkbbx9daDCR3H0vwBhDC9ANtUwi+DT/V1+AXqqJ9aUirD3Nq/TxPQhNbT0IvlnGtKjAhvUSGDdCJqgF2lvapbn8mW0WeL5fLqUhPk7VeNeT/unr1+sfr15Oz6cm0wVanfZJeC60wI8PdrL2b1d60vbPvjCbavw5+/jr4+b0HPz19QPiIudNCGaJvCd/rnrzM+A554Rkv+oOeEUhvM94Q4ylmfL0uRYD3Xm829PcvEeiNPrvN+EJ4JUriB7M1GaVruT3U+STKn7zrIfmUffII6WgaAzUyxIsWQke64xm/h1V3WrW53WQDi6GYugevOs+TG1J/UDx2erTJBqWLqgKHI/EDbr5DD9/+dH3DM172h1RtOt1KByXJbvZwScQy4+KA7d0nttdfUPBHs93nbV2w9E2hH1VZrzsuudls5btHn9ToK7gtLOW62Wx+Ay1wFCU=
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Upload Disbursement Instructions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/disbursements/{id}/instructions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Adds a file containing a list of receivers to a  `DRAFT` disbursement. This step is required before a disbursement can begin. The file must be a CSV and has a different possible formats according with the disbursement configuration, and they can be found at [public/resources/disbursementTemplates](https://github.com/stellar/stellar-disbursement-platform-frontend/tree/58873bbf36cff4614e603daf449079b1d9fad24a/public/resources/disbursementTemplates). The operation is idempotent, guaranteed by deleting and recreating the disbursement attributes when this endpoint is called.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"multipart/form-data":{"schema":{"required":["file"],"type":"object","properties":{"file":{"type":"string","description":"Disbursement instructions file to upload. The CSV file columns can vary depending om the way the disbursement was configured, and the fields are a subset of the following: [`phone`, `email`, `id`, `amount`, `verification`, `paymentID`, `walletAddress`]","format":"binary"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Created","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string"}},"example":{"message":"File uploaded succesfully"}},"example":{"message":"File uploaded succesfully"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"foo":{"type":"string"},"message":{"type":"string"}}}},"example":{"error":"Invalid file format *.xyz","extras":{"foo":"bar","message":"Not authorized"}}},"example":{"error":"Invalid file format *.xyz","extras":{"foo":"bar","message":"Not authorized"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/users.tag.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/users.tag.mdx
deleted file mode 100644
index ca02e0b383..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/users.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: users
-title: "Users"
-description: "Users"
-custom_edit_url: null
----
-
-
-
-The users endpoints facilitate the creation of new SDP users - including setting the appropriate role, sending an email invitation, and activating a user - and managing roles.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/verify-receiver-registration.api.mdx b/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/verify-receiver-registration.api.mdx
deleted file mode 100644
index 9122a4117b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs-sdp/current/api-reference/verify-receiver-registration.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: verify-receiver-registration
-title: "Verify Receiver Registration"
-description: "This endpoint verifies the receiver's registration by validating the OTP and other verification values provided in the request body. A valid SEP-24 token should be included in the Authorization header of the request."
-sidebar_label: "Verify Receiver Registration"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1v2zYQ/isEv7QFJDsNun3QN6dx1+wlMWK3w5AGLiWdLc4UqZGnuJ6h/z4cKcVynMXd1g7D8iUWdXzujXf3UFuOYul4csOvYSkdWoHSaH4b8RxcZmXlHxM+K6RjoPPKSI3sDqxcSHAMC2AWMpB3YJ85ZnsYLN2wO6FkLlDqpZe8mk2Y0DkzWIBtQbIgfCdUDY5V1tzJHHImdYv9Ww0OWWryzYCNAiCbjifx6SuGZgWaucLUKmcpMKkzVfc2j2osjJW/Bw0FiBwsM4s+8IBH3FQQLL7IecLfk1Wb69anvaBEvBJWlIBgKWJbrkUJPOF7enjEJQUsqOMP47hn+sJYJvaMfP7G2FJgwp6dgbBg2dZLNs9e8IiTzdJCzhO0NUTc4UaRfifLSgGPOHyqlMmBJwuhHAlkBZSCJ1uOm8pLopV6yZvmNqCBwzOTb0hi38z3/dzkAkUbXMpkVRgNc12XKdghlEKqiDIbPZLQyKfbwuvRZPb67Si4zSOeGY2gkfSKqlLtnuGvjpRvD+026a+QISXAUrZQgqO3Xvmhew9jPiYxJpwzmRQIOVtLLPaObndipucT720qHAzYWPpz+rHv8EdmLPvoFX9k0rEuJwPeRLwveNysCUmzIP1vWGewOm7UlYZ4JktgE+Hc2ti8syL3p7WfYsLcez4K/v7ggOwKPt14H2sH9iHwfCFB5Y/Bg65L6l3no9l4fvVmfnZxPXvLI/7LeHQ9/+nq0j9MLi55xC9Hs4ury9GP84vz+eW7n87G19TkUKIvob5lb7y2hiokExVmhZiHc3vUv5mv6l3ArCnZd8YsFexqgDfNTu1jbeY61CVvmuZhyfsFVxntwvk/PTk5UrquzjJwblGrL1d1JTgnlvBoPj4J34oSblbkgPfh1WNWnomcdZ5+uX5grfmMwjsHFFI5JlJToz91YWNDDqAV7qgm79e9s/eK+YUOA0rqqkbeh/NHeL4whie73/0S5VG7ngp7L5MKyzRA7hgamnBCM6kRllQj99F9eRjdd7obKx7464b388PGHQqs+3Jtr2yiPz9VzZ8F+9Ig23NzZ0Wn59XJyx7ywx1fE9hjf4ozk8MSdNwO25h4TNzSBvodwEE7aXTgFCvY8OTJnRH3rbNDoFleAhaG2EtlfD1VAgue8OFaKAUY92nZcK9lR9yBvev4TG0VT7hHdJDVVuJmSmcjJC8wEiI7vSSJSv4Am4MS+/7nGbXy/J7igMZWZ8ScXOpuzgnNxtPTb75llZV3AoGtYEOk7DOoFUWYjvD1jsiMe8kM3GDXA/aH827dj8Xd4/5Ee3y9G0gHc+dgYvRqROqF8YFre/8UQSlh2bl0aW0dlKCRTZTAhbElG00uglIX7DgdvBycULrqshR24xk5sKcxnk/PJy+oxwiGxiiW1lKhz4ixS6HbqPreUooVsLRWK1aJDaH4VcGW1tQVcWYLmaykf2GIkmBPuwZcG7saHM7D/5yJH/QH7a8ypFIzU4GOnalt5pkI9SyGhUB6HUwxmqGpulvDA7hAb+kFVSvLhKYmvTA13XECZ1sYpcyaaLOFyjiJxkpwCdkRsxsX8Ibt/zjvBSmu2iDFqchWoPPb5wVi5ZLhcCmxqNNBZsrhX0J4kTDv/L0pG0ajQUgdbnKtmPdK6oUVDm2dYW1bBykveCyng7/g2cL6yfRPXOsgjvm2hpR1sn/bmwJUGWeFsOieNLknN0QLMCyF1MN24Ul/jrnxFlTJPJC3P4dKmU13v3661mpHcqs6BasBwQ0+UEdFsKW7WkzB3smM+lLnVmvmwNjl0AvFZhG7ViziSmagnW+1Xa+uRFYAO/V9KowSwkqGw/V6PRD+rUdrt7rhjxevx5fTcXw6OBkUWCrf0mmElUL3gMOVnHVkmT24lO/1nO2O7Pyfv1m00xfhEw4rJaS/jPmYb9vhf8MfGf4P59ttxAtiDMkN327pWvnOqqah5d9qoClzc0tsw0qR0sy6uW2ibvruuMrrEPB4RjbtyMkB02yibscoy6DCJ2X7pGZyNZ3xKLAdun/4TxzcijVNXLEmykJfcTBwqG1Y23Il9LIO/Cxg0t8fkvC7BA==
-sidebar_class_name: "post api-method"
-info_path: platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Verify Receiver Registration"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/wallet-registration/verification"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint verifies the receiver's registration by validating the OTP and other verification values provided in the request body. A valid SEP-24 token should be included in the Authorization header of the request.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"Authorization","in":"header","description":"SEP-24 token for authorization (Format: 'Bearer {token}')","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Verification data including phone_number/email, OTP, verification value, and reCAPTCHA token","content":{"application/json":{"schema":{"type":"object","properties":{"email":{"type":"string","description":"Email associated with the receiver in the SDP database. Either `phone_number` or `email` is required."},"phone_number":{"type":"string","description":"Phone number associated with the receiver in the SDP database. Either `phone_number` or `email` is required."},"otp":{"type":"string","description":"One-Time Password received for verification"},"verification":{"type":"string","description":"Verification value provided by the user"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"recaptcha_token":{"type":"string","description":"Token received from Google reCAPTCHA"}},"title":"ReceiverRegistrationRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Verification successful","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string","example":"ok"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current.json b/i18n/es/docusaurus-plugin-content-docs/current.json
deleted file mode 100644
index 027602edbd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current.json
+++ /dev/null
@@ -1,1262 +0,0 @@
-{
-  "version.label": {
-    "message": "Siguiente",
-    "description": "The label for version current"
-  },
-  "sidebar.build.category.Build Smart Contracts": {
-    "message": "Desarrollar Contratos Inteligentes",
-    "description": "The label for category 'Build Smart Contracts' in sidebar 'build'"
-  },
-  "sidebar.build.category.Getting Started": {
-    "message": "Comenzar",
-    "description": "The label for category 'Getting Started' in sidebar 'build'"
-  },
-  "sidebar.build.category.Example Contracts": {
-    "message": "Ejemplos de Contratos",
-    "description": "The label for category 'Example Contracts' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build Applications": {
-    "message": "Construir Aplicaciones",
-    "description": "The label for category 'Build Applications' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build a Wallet with the Wallet SDK": {
-    "message": "Construir una Billetera con el Wallet SDK",
-    "description": "The label for category 'Build a Wallet with the Wallet SDK' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build a Payment App with the JS SDK": {
-    "message": "Construir una Aplicación de Pago con el JS SDK",
-    "description": "The label for category 'Build a Payment App with the JS SDK' in sidebar 'build'"
-  },
-  "sidebar.build.category.Anchor Integration": {
-    "message": "Integración de Anchor",
-    "description": "The label for category 'Anchor Integration' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build Custom Network Ingestion Pipeline": {
-    "message": "Construir un Pipeline de Ingesta de Red Personalizado",
-    "description": "The label for category 'Build Custom Network Ingestion Pipeline' in sidebar 'build'"
-  },
-  "sidebar.build.category.Build a Passkey Powered Guestbook Dapp": {
-    "message": "Construir un Dapp de libro de visitas impulsado por Passkey",
-    "description": "The label for category 'Build a Passkey Powered Guestbook Dapp' in sidebar 'build'"
-  },
-  "sidebar.build.category.How-To Guides": {
-    "message": "Guías Prácticas",
-    "description": "The label for category 'How-To Guides' in sidebar 'build'"
-  },
-  "sidebar.build.category.Contract Conventions": {
-    "message": "Convenciones de Contratos",
-    "description": "The label for category 'Contract Conventions' in sidebar 'build'"
-  },
-  "sidebar.build.category.Contract Events": {
-    "message": "Eventos de Contrato",
-    "description": "The label for category 'Contract Events' in sidebar 'build'"
-  },
-  "sidebar.build.category.Contract Storage": {
-    "message": "Almacenamiento de Contratos",
-    "description": "The label for category 'Contract Storage' in sidebar 'build'"
-  },
-  "sidebar.build.category.Contract Testing": {
-    "message": "Pruebas de Contrato",
-    "description": "The label for category 'Contract Testing' in sidebar 'build'"
-  },
-  "sidebar.build.category.Dapp Development": {
-    "message": "Desarrollo de Dapp",
-    "description": "The label for category 'Dapp Development' in sidebar 'build'"
-  },
-  "sidebar.build.category.Fees & Metering": {
-    "message": "Tarifas y Medición",
-    "description": "The label for category 'Fees & Metering' in sidebar 'build'"
-  },
-  "sidebar.build.category.Freighter Wallet": {
-    "message": "Billetera Freighter",
-    "description": "The label for category 'Freighter Wallet' in sidebar 'build'"
-  },
-  "sidebar.build.category.Stellar Basics": {
-    "message": "Conceptos Básicos de Stellar",
-    "description": "The label for category 'Stellar Basics' in sidebar 'build'"
-  },
-  "sidebar.build.category.RPC": {
-    "message": "RPC",
-    "description": "The label for category 'RPC' in sidebar 'build'"
-  },
-  "sidebar.build.category.State Archival": {
-    "message": "Archivado de Estado",
-    "description": "The label for category 'State Archival' in sidebar 'build'"
-  },
-  "sidebar.build.category.Stellar Asset Contract (SAC) Tokens": {
-    "message": "Tokens de Contrato de Activos Stellar (SAC)",
-    "description": "The label for category 'Stellar Asset Contract (SAC) Tokens' in sidebar 'build'"
-  },
-  "sidebar.build.category.Transactions": {
-    "message": "Transacciones",
-    "description": "The label for category 'Transactions' in sidebar 'build'"
-  },
-  "sidebar.build.category.Type Conversions": {
-    "message": "Conversiones de Tipo",
-    "description": "The label for category 'Type Conversions' in sidebar 'build'"
-  },
-  "sidebar.build.category.Security Best Practices": {
-    "message": "Prácticas recomendadas de seguridad",
-    "description": "The label for category 'Security Best Practices' in sidebar 'build'"
-  },
-  "sidebar.build.category.Threat Modeling": {
-    "message": "Modelado de amenazas",
-    "description": "The label for category 'Threat Modeling' in sidebar 'build'"
-  },
-  "sidebar.learn.category.Core Concepts": {
-    "message": "Conceptos Fundamentales",
-    "description": "The label for category 'Core Concepts' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Stellar Data Structures": {
-    "message": "Estructuras de Datos de Stellar",
-    "description": "The label for category 'Stellar Data Structures' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Operations & Transactions": {
-    "message": "Operaciones y Transacciones",
-    "description": "The label for category 'Operations & Transactions' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Smart Contracts": {
-    "message": "Contratos Inteligentes",
-    "description": "The label for category 'Smart Contracts' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Contract Interactions": {
-    "message": "Interacciones de Contratos",
-    "description": "The label for category 'Contract Interactions' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Types": {
-    "message": "Tipos",
-    "description": "The label for category 'Types' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Storage": {
-    "message": "Almacenamiento",
-    "description": "The label for category 'Storage' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Errors and Debugging": {
-    "message": "Errores y Depuración",
-    "description": "The label for category 'Errors and Debugging' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Data Format": {
-    "message": "Formato de Datos",
-    "description": "The label for category 'Data Format' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Migrate from Another Chain": {
-    "message": "Migrar desde Otra Cadena",
-    "description": "The label for category 'Migrate from Another Chain' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.EVM Networks": {
-    "message": "Redes EVM",
-    "description": "The label for category 'EVM Networks' in sidebar 'learn'"
-  },
-  "sidebar.learn.category.Interactive Learning": {
-    "message": "Aprendizaje Interactivo",
-    "description": "The label for category 'Interactive Learning' in sidebar 'learn'"
-  },
-  "sidebar.data_overview.category.Analytics": {
-    "message": "Análisis",
-    "description": "The label for category 'Analytics' in sidebar 'data_overview'"
-  },
-  "sidebar.data_overview.category.APIs": {
-    "message": "APIs",
-    "description": "The label for category 'APIs' in sidebar 'data_overview'"
-  },
-  "sidebar.data_overview.category.Indexers": {
-    "message": "Indexadores",
-    "description": "The label for category 'Indexers' in sidebar 'data_overview'"
-  },
-  "sidebar.data_overview.category.Oracles": {
-    "message": "Oráculos",
-    "description": "The label for category 'Oracles' in sidebar 'data_overview'"
-  },
-  "sidebar.data_overview.doc.Hubble": {
-    "message": "Hubble",
-    "description": "The label for the doc item 'Hubble' in sidebar 'data_overview', linking to the doc data/analytics/hubble/README"
-  },
-  "sidebar.data_overview.doc.Data Analytics Providers": {
-    "message": "Proveedores de Análisis de Datos",
-    "description": "The label for the doc item 'Data Analytics Providers' in sidebar 'data_overview', linking to the doc data/analytics/analytics-providers/analytics-providers"
-  },
-  "sidebar.data_overview.doc.RPC": {
-    "message": "RPC",
-    "description": "The label for the doc item 'RPC' in sidebar 'data_overview', linking to the doc data/apis/rpc/README"
-  },
-  "sidebar.data_overview.doc.Horizon": {
-    "message": "Horizon",
-    "description": "The label for the doc item 'Horizon' in sidebar 'data_overview', linking to the doc data/apis/horizon/README"
-  },
-  "sidebar.data_overview.doc.Migrate Horizon to RPC": {
-    "message": "Migrar Horizon a RPC",
-    "description": "The label for the doc item 'Migrate Horizon to RPC' in sidebar 'data_overview', linking to the doc data/apis/migrate-from-horizon-to-rpc"
-  },
-  "sidebar.data_overview.doc.Build Your Own Indexer": {
-    "message": "Construir tu propio Indexador",
-    "description": "The label for the doc item 'Build Your Own Indexer' in sidebar 'data_overview', linking to the doc data/indexers/build-your-own/README"
-  },
-  "sidebar.data_overview.doc.Indexer Providers": {
-    "message": "Proveedores de Indexadores",
-    "description": "The label for the doc item 'Indexer Providers' in sidebar 'data_overview', linking to the doc data/indexers/indexer-providers/indexer-providers"
-  },
-  "sidebar.data_overview.doc.Oracle Providers": {
-    "message": "Proveedores de Oráculos",
-    "description": "The label for the doc item 'Oracle Providers' in sidebar 'data_overview', linking to the doc data/oracles/oracle-providers"
-  },
-  "sidebar.tools.category.SDKs": {
-    "message": "SDKs",
-    "description": "The label for category 'SDKs' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Stellar CLI": {
-    "message": "CLI de Stellar",
-    "description": "The label for category 'Stellar CLI' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Lab": {
-    "message": "Laboratorio",
-    "description": "The label for category 'Lab' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.API Explorer": {
-    "message": "Explorador de API",
-    "description": "The label for category 'API Explorer' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Quickstart": {
-    "message": "Inicio Rápido",
-    "description": "The label for category 'Quickstart' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Getting Started": {
-    "message": "Comenzar",
-    "description": "The label for category 'Getting Started' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Debugging": {
-    "message": "Depuración",
-    "description": "The label for category 'Debugging' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Cloud Deployment": {
-    "message": "Implementación en la nube",
-    "description": "The label for category 'Cloud Deployment' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Advanced Usage": {
-    "message": "Uso Avanzado",
-    "description": "The label for category 'Advanced Usage' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.More Developer Tools": {
-    "message": "Más herramientas de desarrollador",
-    "description": "The label for category 'More Developer Tools' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Ramps": {
-    "message": "Rampas",
-    "description": "The label for category 'Ramps' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Infrastructure Tools": {
-    "message": "Herramientas de Infraestructura",
-    "description": "The label for category 'Infrastructure Tools' in sidebar 'tools'"
-  },
-  "sidebar.tools.link.Anchor Platform": {
-    "message": "Anchor Platform",
-    "description": "The label for link 'Anchor Platform' in sidebar 'tools', linking to '/docs/platforms/anchor-platform'"
-  },
-  "sidebar.tools.link.Stellar Disbursement Platform": {
-    "message": "Stellar Disbursement Platform",
-    "description": "The label for link 'Stellar Disbursement Platform' in sidebar 'tools', linking to '/docs/platforms/stellar-disbursement-platform'"
-  },
-  "sidebar.validators.category.Admin Guide": {
-    "message": "Guía del Administrador",
-    "description": "The label for category 'Admin Guide' in sidebar 'validators'"
-  },
-  "sidebar.hubble.category.Hubble": {
-    "message": "Hubble",
-    "description": "The label for category 'Hubble' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Analyst Guide": {
-    "message": "Guía para Analistas",
-    "description": "The label for category 'Analyst Guide' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Developer Guide": {
-    "message": "Guía del Desarrollador",
-    "description": "The label for category 'Developer Guide' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Backfill": {
-    "message": "Rellenar",
-    "description": "The label for category 'Backfill' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Source System Ingestion": {
-    "message": "Ingesta de Sistemas Fuente",
-    "description": "The label for category 'Source System Ingestion' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Data Curation": {
-    "message": "Curación de Datos",
-    "description": "The label for category 'Data Curation' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Visualization": {
-    "message": "Visualización",
-    "description": "The label for category 'Visualization' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Scheduling and Orchestration": {
-    "message": "Programación y Orquestación",
-    "description": "The label for category 'Scheduling and Orchestration' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Data Catalog": {
-    "message": "Catálogo de Datos",
-    "description": "The label for category 'Data Catalog' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Data Dictionary": {
-    "message": "Diccionario de Datos",
-    "description": "The label for category 'Data Dictionary' in sidebar 'hubble'"
-  },
-  "sidebar.galexie.category.Galexie": {
-    "message": "Galexie",
-    "description": "The label for category 'Galexie' in sidebar 'galexie'"
-  },
-  "sidebar.galexie.category.Admin Guide": {
-    "message": "Guía del Administrador",
-    "description": "The label for category 'Admin Guide' in sidebar 'galexie'"
-  },
-  "sidebar.ingest.category.Ingest SDK": {
-    "message": "SDK de Ingesta",
-    "description": "The label for category 'Ingest SDK' in sidebar 'ingest'"
-  },
-  "sidebar.ingest.category.Developer Guide": {
-    "message": "Guía del Desarrollador",
-    "description": "The label for category 'Developer Guide' in sidebar 'ingest'"
-  },
-  "sidebar.ingest.category.Ledger Backends": {
-    "message": "Backends de Ledger",
-    "description": "The label for category 'Ledger Backends' in sidebar 'ingest'"
-  },
-  "sidebar.soroban_rpc.category.Stellar RPC": {
-    "message": "RPC Stellar",
-    "description": "The label for category 'Stellar RPC' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.soroban_rpc.category.Methods": {
-    "message": "Métodos",
-    "description": "The label for category 'Methods' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.analytics.category.Analytics": {
-    "message": "Análisis",
-    "description": "The label for category 'Analytics' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Hubble": {
-    "message": "Hubble",
-    "description": "The label for category 'Hubble' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Analyst Guide": {
-    "message": "Guía para Analistas",
-    "description": "The label for category 'Analyst Guide' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Developer Guide": {
-    "message": "Guía para Desarrolladores",
-    "description": "The label for category 'Developer Guide' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Backfill": {
-    "message": "Relleno",
-    "description": "The label for category 'Backfill' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Source System Ingestion": {
-    "message": "Ingesta del Sistema de Origen",
-    "description": "The label for category 'Source System Ingestion' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Data Curation": {
-    "message": "Curaduría de Datos",
-    "description": "The label for category 'Data Curation' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Visualization": {
-    "message": "Visualización",
-    "description": "The label for category 'Visualization' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Scheduling and Orchestration": {
-    "message": "Programación y Orquestación",
-    "description": "The label for category 'Scheduling and Orchestration' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Data Catalog": {
-    "message": "Catálogo de Datos",
-    "description": "The label for category 'Data Catalog' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Data Dictionary": {
-    "message": "Diccionario de Datos",
-    "description": "The label for category 'Data Dictionary' in sidebar 'analytics'"
-  },
-  "sidebar.apis.category.APIs": {
-    "message": "APIs",
-    "description": "The label for category 'APIs' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.RPC": {
-    "message": "RPC",
-    "description": "The label for category 'RPC' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Methods": {
-    "message": "Métodos",
-    "description": "The label for category 'Methods' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Horizon": {
-    "message": "Horizon",
-    "description": "The label for category 'Horizon' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Resources": {
-    "message": "Recursos",
-    "description": "The label for category 'Resources' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Accounts": {
-    "message": "Cuentas",
-    "description": "The label for category 'Accounts' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Assets": {
-    "message": "Activos",
-    "description": "The label for category 'Assets' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Claimable Balances": {
-    "message": "Saldos Reclamables",
-    "description": "The label for category 'Claimable Balances' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Effects": {
-    "message": "Efectos",
-    "description": "The label for category 'Effects' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Ledgers": {
-    "message": "Ledgers",
-    "description": "The label for category 'Ledgers' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Liquidity Pools": {
-    "message": "Fondos de Liquidez",
-    "description": "The label for category 'Liquidity Pools' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Offers": {
-    "message": "Ofertas",
-    "description": "The label for category 'Offers' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Operations": {
-    "message": "Operaciones",
-    "description": "The label for category 'Operations' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.The Operation Object": {
-    "message": "El Objeto de Operación",
-    "description": "The label for category 'The Operation Object' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Payments": {
-    "message": "Pagos",
-    "description": "The label for category 'Payments' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Trades": {
-    "message": "Operaciones de Comercio",
-    "description": "The label for category 'Trades' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Transactions": {
-    "message": "Transacciones",
-    "description": "The label for category 'Transactions' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Pagination": {
-    "message": "Paginación",
-    "description": "The label for category 'Pagination' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Aggregations": {
-    "message": "Agregaciones",
-    "description": "The label for category 'Aggregations' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Order Books": {
-    "message": "Libros de Órdenes",
-    "description": "The label for category 'Order Books' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Paths": {
-    "message": "Rutas",
-    "description": "The label for category 'Paths' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Trade Aggregations": {
-    "message": "Agregaciones de Comercio",
-    "description": "The label for category 'Trade Aggregations' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Fee Stats": {
-    "message": "Estadísticas de Tarifas",
-    "description": "The label for category 'Fee Stats' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Errors": {
-    "message": "Errores",
-    "description": "The label for category 'Errors' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.HTTP Status Codes": {
-    "message": "Códigos de Estado HTTP",
-    "description": "The label for category 'HTTP Status Codes' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Horizon-Specific Status Codes": {
-    "message": "Códigos de Estado Específicos de Horizon",
-    "description": "The label for category 'Horizon-Specific Status Codes' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Result Codes": {
-    "message": "Códigos de Resultado",
-    "description": "The label for category 'Result Codes' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.Operation-Specific Result Codes": {
-    "message": "Códigos de Resultado Específicos de Operación",
-    "description": "The label for category 'Operation-Specific Result Codes' in sidebar 'apis'"
-  },
-  "sidebar.indexers.category.Indexers": {
-    "message": "Indexadores",
-    "description": "The label for category 'Indexers' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Build Your Own Indexer": {
-    "message": "Construir Tu Propio Indexador",
-    "description": "The label for category 'Build Your Own Indexer' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Galexie": {
-    "message": "Galexie",
-    "description": "The label for category 'Galexie' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Admin Guide": {
-    "message": "Guía Administrativa",
-    "description": "The label for category 'Admin Guide' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Ingest SDK": {
-    "message": "SDK de Ingesta",
-    "description": "The label for category 'Ingest SDK' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Developer Guide": {
-    "message": "Guía del Desarrollador",
-    "description": "The label for category 'Developer Guide' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Ledger Backends": {
-    "message": "Backends de Ledger",
-    "description": "The label for category 'Ledger Backends' in sidebar 'indexers'"
-  },
-  "sidebar.oracles.category.Oracles": {
-    "message": "Oráculos",
-    "description": "The label for category 'Oracles' in sidebar 'oracles'"
-  },
-  "sidebar.build.category.Contract Authorization": {
-    "message": "Autorización de Contrato",
-    "description": "The label for category 'Contract Authorization' in sidebar 'build'"
-  },
-  "sidebar.tools.category.Smart Contracts": {
-    "message": "Contratos inteligentes",
-    "description": "The label for category 'Smart Contracts' in sidebar 'tools'"
-  },
-  "sidebar.indexers.category.Processors": {
-    "message": "Procesadores",
-    "description": "The label for category 'Processors' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.Token Transfer Processor": {
-    "message": "Procesador de Transferencia de Tokens",
-    "description": "The label for category 'Token Transfer Processor' in sidebar 'indexers'"
-  },
-  "sidebar.tools.category.Cookbook": {
-    "message": "Libro de recetas",
-    "description": "The label for category 'Cookbook' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.Saved": {
-    "message": "Guardado",
-    "description": "The label for category 'Saved' in sidebar 'tools'"
-  },
-  "sidebar.tools.category.View XDR": {
-    "message": "Ver XDR",
-    "description": "The label for category 'View XDR' in sidebar 'tools'"
-  },
-  "sidebar.hubble.category.Bronze 🥉": {
-    "message": "Bronce 🥉",
-    "description": "The label for category 'Bronze 🥉' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Silver 🥈": {
-    "message": "Plata 🥈",
-    "description": "The label for category 'Silver 🥈' in sidebar 'hubble'"
-  },
-  "sidebar.hubble.category.Gold 🥇": {
-    "message": "Oro 🥇",
-    "description": "The label for category 'Gold 🥇' in sidebar 'hubble'"
-  },
-  "sidebar.analytics.category.Bronze 🥉": {
-    "message": "Bronce 🥉",
-    "description": "The label for category 'Bronze 🥉' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Silver 🥈": {
-    "message": "Plata 🥈",
-    "description": "The label for category 'Silver 🥈' in sidebar 'analytics'"
-  },
-  "sidebar.analytics.category.Gold 🥇": {
-    "message": "Oro 🥇",
-    "description": "The label for category 'Gold 🥇' in sidebar 'analytics'"
-  },
-  "sidebar.galexie.category.galexie-example-usages": {
-    "message": "Usos de ejemplo",
-    "description": "The label for category 'Example Usages' in sidebar 'galexie'"
-  },
-  "sidebar.ingest.category.ingest-sdk-example-usages": {
-    "message": "Usos de ejemplo",
-    "description": "The label for category 'Example Usages' in sidebar 'ingest'"
-  },
-  "sidebar.soroban_rpc.category.rpc-admin-guide": {
-    "message": "Guía del administrador",
-    "description": "The label for category 'Admin Guide' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.soroban_rpc.category.rpc-api-reference": {
-    "message": "Referencia de la API",
-    "description": "The label for category 'API Reference' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.soroban_rpc.category.rpc-api-structure": {
-    "message": "Estructura",
-    "description": "The label for category 'Structure' in sidebar 'soroban_rpc'"
-  },
-  "sidebar.apis.category.rpc-admin-guide": {
-    "message": "Guía del administrador",
-    "description": "The label for category 'Admin Guide' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.rpc-api-reference": {
-    "message": "Referencia de la API",
-    "description": "The label for category 'API Reference' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.rpc-api-structure": {
-    "message": "Estructura",
-    "description": "The label for category 'Structure' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.horizon-admin-guide": {
-    "message": "Guía del administrador",
-    "description": "The label for category 'Admin Guide' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.horizon-api-reference": {
-    "message": "Referencia de la API",
-    "description": "The label for category 'API Reference' in sidebar 'apis'"
-  },
-  "sidebar.apis.category.horizon-api-structure": {
-    "message": "Estructura",
-    "description": "The label for category 'Structure' in sidebar 'apis'"
-  },
-  "sidebar.indexers.category.galexie-example-usages": {
-    "message": "Usos de ejemplo",
-    "description": "The label for category 'Example Usages' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.ingest-sdk-example-usages": {
-    "message": "Usos de ejemplo",
-    "description": "The label for category 'Example Usages' in sidebar 'indexers'"
-  },
-  "sidebar.indexers.category.token-transfer-processor-example-usages": {
-    "message": "Usos de ejemplo",
-    "description": "The label for category 'Example Usages' in sidebar 'indexers'"
-  },
-  "sidebar.anchor_platform.category.Anchor Platform": {
-    "message": "Anchor Platform",
-    "description": "The label for category 'Anchor Platform' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Admin Guide": {
-    "message": "Guía de administración",
-    "description": "The label for category 'Admin Guide' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Event Handling": {
-    "message": "Manejo de eventos",
-    "description": "The label for category 'Event Handling' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.API Reference": {
-    "message": "Referencia de API",
-    "description": "The label for category 'API Reference' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Platform Server": {
-    "message": "Servidor de plataforma",
-    "description": "The label for category 'Platform Server' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Transactions": {
-    "message": "Transacciones",
-    "description": "The label for category 'Transactions' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.JSON-RPC API": {
-    "message": "API JSON-RPC",
-    "description": "The label for category 'JSON-RPC API' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Methods": {
-    "message": "Métodos",
-    "description": "The label for category 'Methods' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Callbacks Server": {
-    "message": "Servidor de callbacks",
-    "description": "The label for category 'Callbacks Server' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.SEP Guides": {
-    "message": "Guías SEP",
-    "description": "The label for category 'SEP Guides' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Programmatic Deposits and Withdrawals (SEP-6)": {
-    "message": "Depósitos y retiradas de fondos programáticos (SEP-6)",
-    "description": "The label for category 'Programmatic Deposits and Withdrawals (SEP-6)' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Hosted Deposits and Withdrawals (SEP-24)": {
-    "message": "Depósitos y retiradas de fondos alojados (SEP-24)",
-    "description": "The label for category 'Hosted Deposits and Withdrawals (SEP-24)' in sidebar 'anchor_platform'"
-  },
-  "sidebar.anchor_platform.category.Cross-Border Payments (SEP-31)": {
-    "message": "Pagos transnacionales (SEP-31)",
-    "description": "The label for category 'Cross-Border Payments (SEP-31)' in sidebar 'anchor_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Stellar Disbursement Platform": {
-    "message": "Stellar Disbursement Platform",
-    "description": "The label for category 'Stellar Disbursement Platform' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin Guide": {
-    "message": "Guía de administración",
-    "description": "The label for category 'Admin Guide' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin Guide.link.generated-index.description": {
-    "message": "Todo lo que necesitas saber sobre cómo configurar, ejecutar y usar la Stellar Disbursement Platform.",
-    "description": "The generated-index page description for category 'Admin Guide' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.User Interface": {
-    "message": "Interfaz de usuario",
-    "description": "The label for category 'User Interface' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Reference": {
-    "message": "Referencia de API",
-    "description": "The label for category 'API Reference' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Reference.link.generated-index.description": {
-    "message": "Consulta toda la información del API de la Stellar Disbursement Platform.",
-    "description": "The generated-index page description for category 'API Reference' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Admin (Tenant Management)": {
-    "message": "Administración (gestión de inquilinos)",
-    "description": "The label for category 'Admin (Tenant Management)' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Authentication": {
-    "message": "Autenticación",
-    "description": "The label for category 'Authentication' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.API Keys": {
-    "message": "Claves API",
-    "description": "The label for category 'API Keys' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Balances": {
-    "message": "Saldos",
-    "description": "The label for category 'Balances' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Bridge Integration": {
-    "message": "Integración de puente",
-    "description": "The label for category 'Bridge Integration' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Disbursements": {
-    "message": "Desembolsos",
-    "description": "The label for category 'Disbursements' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Organization": {
-    "message": "Organización",
-    "description": "The label for category 'Organization' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Payments": {
-    "message": "Pagos",
-    "description": "The label for category 'Payments' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Profile": {
-    "message": "Perfil",
-    "description": "The label for category 'Profile' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Receivers": {
-    "message": "Receptores",
-    "description": "The label for category 'Receivers' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Registration": {
-    "message": "Registro",
-    "description": "The label for category 'Registration' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Statistics": {
-    "message": "Estadísticas",
-    "description": "The label for category 'Statistics' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Users": {
-    "message": "Usuarios",
-    "description": "The label for category 'Users' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Exports": {
-    "message": "Exportaciones",
-    "description": "The label for category 'Exports' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.category.Wallets": {
-    "message": "Billeteras",
-    "description": "The label for category 'Wallets' in sidebar 'stellar_disbursement_platform'"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Tenants": {
-    "message": "Obtener todos los inquilinos",
-    "description": "The label for the doc item 'Get All Tenants' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-tenants"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Tenant": {
-    "message": "Crear inquilino",
-    "description": "The label for the doc item 'Create Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Tenant": {
-    "message": "Recuperar un inquilino",
-    "description": "The label for the doc item 'Retrieve a Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Soft delete a Tenant": {
-    "message": "Eliminar un inquilino suavemente",
-    "description": "The label for the doc item 'Soft delete a Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Tenant": {
-    "message": "Actualizar un inquilino",
-    "description": "The label for the doc item 'Update a Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-a-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Default Tenant": {
-    "message": "Inquilino predeterminado",
-    "description": "The label for the doc item 'Default Tenant' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/default-tenant"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Log In": {
-    "message": "Iniciar sesión",
-    "description": "The label for the doc item 'Log In' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/log-in"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Refresh Token": {
-    "message": "Actualizar token",
-    "description": "The label for the doc item 'Refresh Token' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/refresh-token"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Provide Multi-Factor Authentication": {
-    "message": "Proporcionar autenticación multifactor",
-    "description": "The label for the doc item 'Provide Multi-Factor Authentication' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/authenticate-mfa"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Forgot Password": {
-    "message": "Olvidar contraseña",
-    "description": "The label for the doc item 'Forgot Password' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/forgot-password"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Reset Rassword": {
-    "message": "Restablecer contraseña",
-    "description": "The label for the doc item 'Reset Rassword' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/reset-password"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List API Keys": {
-    "message": "Listar claves API",
-    "description": "The label for the doc item 'List API Keys' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-api-keys"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create API Key": {
-    "message": "Crear clave API",
-    "description": "The label for the doc item 'Create API Key' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get API Key Details": {
-    "message": "Obtener detalles de clave API",
-    "description": "The label for the doc item 'Get API Key Details' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update API Key": {
-    "message": "Actualizar clave API",
-    "description": "The label for the doc item 'Update API Key' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Delete API Key": {
-    "message": "Eliminar clave API",
-    "description": "The label for the doc item 'Delete API Key' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/delete-api-key"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Organization (Circle) Balances": {
-    "message": "Obtener saldos de la organización (Circle)",
-    "description": "The label for the doc item 'Get Organization (Circle) Balances' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Bridge Integration Status": {
-    "message": "Obtener estado de integración del puente",
-    "description": "The label for the doc item 'Get Bridge Integration Status' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-bridge-integration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Bridge Integration Status": {
-    "message": "Actualizar estado de integración del puente",
-    "description": "The label for the doc item 'Update Bridge Integration Status' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-bridge-integration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Disbursements": {
-    "message": "Listar todos los desembolsos",
-    "description": "The label for the doc item 'List All Disbursements' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-all-disbursements"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Disbursement": {
-    "message": "Crear desembolso",
-    "description": "The label for the doc item 'Create Disbursement' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Disbursement": {
-    "message": "Recuperar un desembolso",
-    "description": "The label for the doc item 'Retrieve a Disbursement' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Deletes a Draft Disbursement": {
-    "message": "Eliminar un desembolso en borrador",
-    "description": "The label for the doc item 'Deletes a Draft Disbursement' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Disbursement Receivers": {
-    "message": "Listar todos los receptores de desembolsos",
-    "description": "The label for the doc item 'List All Disbursement Receivers' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Download Disbursement Instructions": {
-    "message": "Descargar instrucciones de desembolso",
-    "description": "The label for the doc item 'Download Disbursement Instructions' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Upload Disbursement Instructions": {
-    "message": "Subir instrucciones de desembolso",
-    "description": "The label for the doc item 'Upload Disbursement Instructions' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Disbursement Status": {
-    "message": "Actualizar estado de desembolso",
-    "description": "The label for the doc item 'Update a Disbursement Status' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Organization Info": {
-    "message": "Obtener información de la organización",
-    "description": "The label for the doc item 'Get Organization Info' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-organization-info"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Organization Profile": {
-    "message": "Actualizar perfil de la organización",
-    "description": "The label for the doc item 'Update Organization Profile' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-organization-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Organization Logo": {
-    "message": "Recuperar logo de la organización",
-    "description": "The label for the doc item 'Retrieve Organization Logo' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-organization-logo"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Circle Account Setup": {
-    "message": "Configuración de cuenta Circle",
-    "description": "The label for the doc item 'Circle Account Setup' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/patch-organization-circle"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Assets": {
-    "message": "Obtener todos los activos",
-    "description": "The label for the doc item 'Get All Assets' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-assets"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Asset": {
-    "message": "Crear activo",
-    "description": "The label for the doc item 'Create Asset' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-asset"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Delete Asset": {
-    "message": "Eliminar activo",
-    "description": "The label for the doc item 'Delete Asset' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/delete-asset"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Payments": {
-    "message": "Listar todos los pagos",
-    "description": "The label for the doc item 'List All Payments' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-all-payments"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Direct Payment": {
-    "message": "Crear pago directo",
-    "description": "The label for the doc item 'Create Direct Payment' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-direct-payment"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Payment": {
-    "message": "Recuperar un pago",
-    "description": "The label for the doc item 'Retrieve a Payment' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get Profile": {
-    "message": "Obtener perfil",
-    "description": "The label for the doc item 'Get Profile' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Profile": {
-    "message": "Actualizar perfil de usuario",
-    "description": "The label for the doc item 'Update User Profile' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-user-profile"
-  },
-  "sidebar.stellar_disbursement_platform.doc.List All Receivers": {
-    "message": "Listar todos los receptores",
-    "description": "The label for the doc item 'List All Receivers' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/list-all-receivers"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Receiver": {
-    "message": "Crear receptor",
-    "description": "The label for the doc item 'Create Receiver' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve a Receiver": {
-    "message": "Recuperar un receptor",
-    "description": "The label for the doc item 'Retrieve a Receiver' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update a Receiver": {
-    "message": "Actualizar un receptor",
-    "description": "The label for the doc item 'Update a Receiver' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-receiver"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Start Wallet Registration": {
-    "message": "Iniciar registro de billetera",
-    "description": "The label for the doc item 'Start Wallet Registration' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/start-wallet-registration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Send One-Time Passcode": {
-    "message": "Enviar código de un solo uso",
-    "description": "The label for the doc item 'Send One-Time Passcode' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Verify Receiver Registration": {
-    "message": "Verificar registro de receptor",
-    "description": "The label for the doc item 'Verify Receiver Registration' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Stellar Info File": {
-    "message": "Recuperar archivo de información Stellar",
-    "description": "The label for the doc item 'Retrieve Stellar Info File' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Request Challenge Transaction": {
-    "message": "Solicitar transacción de desafío",
-    "description": "The label for the doc item 'Request Challenge Transaction' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Provide Signed Challenge Transaction": {
-    "message": "Proporcionar transacción de desafío firmada",
-    "description": "The label for the doc item 'Provide Signed Challenge Transaction' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Request Registration URL": {
-    "message": "Solicitar URL de registro",
-    "description": "The label for the doc item 'Request Registration URL' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/request-registration-url"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve All Statistics": {
-    "message": "Recuperar todas las estadísticas",
-    "description": "The label for the doc item 'Retrieve All Statistics' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Retrieve Disbursement Statistics": {
-    "message": "Recuperar estadísticas de desembolso",
-    "description": "The label for the doc item 'Retrieve Disbursement Statistics' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Users": {
-    "message": "Obtener todos los usuarios",
-    "description": "The label for the doc item 'Get All Users' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-users"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create User": {
-    "message": "Crear usuario",
-    "description": "The label for the doc item 'Create User' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-user"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Activation Status": {
-    "message": "Actualizar estado de activación de usuario",
-    "description": "The label for the doc item 'Update User Activation Status' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-user-activation-status"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Roles": {
-    "message": "Obtener todos los roles",
-    "description": "The label for the doc item 'Get All Roles' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-roles"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update User Role": {
-    "message": "Actualizar rol de usuario",
-    "description": "The label for the doc item 'Update User Role' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-user-role"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Disbursements": {
-    "message": "Exportar desembolsos",
-    "description": "The label for the doc item 'Export Disbursements' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/export-disbursements"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Payments": {
-    "message": "Exportar pagos",
-    "description": "The label for the doc item 'Export Payments' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/export-payments-csv"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Export Receivers": {
-    "message": "Exportar receptores",
-    "description": "The label for the doc item 'Export Receivers' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/export-receivers-csv"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Get All Wallets": {
-    "message": "Obtener todas las billeteras",
-    "description": "The label for the doc item 'Get All Wallets' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/get-all-wallets"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Create Wallet": {
-    "message": "Crear billetera",
-    "description": "The label for the doc item 'Create Wallet' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/create-wallet"
-  },
-  "sidebar.stellar_disbursement_platform.doc.Update Wallet": {
-    "message": "Actualizar billetera",
-    "description": "The label for the doc item 'Update Wallet' in sidebar 'stellar_disbursement_platform', linking to the doc platforms/stellar-disbursement-platform/api-reference/update-wallet"
-  },
-  "sidebar.build.category.Contract Accounts": {
-    "message": "Cuentas de Contrato",
-    "description": "The label for category 'Contract Accounts' in sidebar 'build'"
-  },
-  "sidebar.data.category.Analytics Overview": {
-    "message": "Resumen de Analítica",
-    "description": "The label for category 'Analytics Overview' in sidebar 'data'"
-  },
-  "sidebar.data.category.Hubble": {
-    "message": "Hubble",
-    "description": "The label for category 'Hubble' in sidebar 'data'"
-  },
-  "sidebar.data.category.Analyst Guide": {
-    "message": "Guía del Analista",
-    "description": "The label for category 'Analyst Guide' in sidebar 'data'"
-  },
-  "sidebar.data.category.hubble-developer-guide": {
-    "message": "Guía del Desarrollador",
-    "description": "The label for category 'Developer Guide' in sidebar 'data'"
-  },
-  "sidebar.data.category.Backfill": {
-    "message": "Relleno",
-    "description": "The label for category 'Backfill' in sidebar 'data'"
-  },
-  "sidebar.data.category.Source System Ingestion": {
-    "message": "Ingesta del Sistema de Origen",
-    "description": "The label for category 'Source System Ingestion' in sidebar 'data'"
-  },
-  "sidebar.data.category.Data Curation": {
-    "message": "Curación de Datos",
-    "description": "The label for category 'Data Curation' in sidebar 'data'"
-  },
-  "sidebar.data.category.Visualization": {
-    "message": "Visualización",
-    "description": "The label for category 'Visualization' in sidebar 'data'"
-  },
-  "sidebar.data.category.Scheduling and Orchestration": {
-    "message": "Programación y Orquestación",
-    "description": "The label for category 'Scheduling and Orchestration' in sidebar 'data'"
-  },
-  "sidebar.data.category.Data Catalog": {
-    "message": "Catálogo de Datos",
-    "description": "The label for category 'Data Catalog' in sidebar 'data'"
-  },
-  "sidebar.data.category.Data Dictionary": {
-    "message": "Diccionario de Datos",
-    "description": "The label for category 'Data Dictionary' in sidebar 'data'"
-  },
-  "sidebar.data.category.Bronze 🥉": {
-    "message": "Bronce 🥉",
-    "description": "The label for category 'Bronze 🥉' in sidebar 'data'"
-  },
-  "sidebar.data.category.Silver 🥈": {
-    "message": "Plata 🥈",
-    "description": "The label for category 'Silver 🥈' in sidebar 'data'"
-  },
-  "sidebar.data.category.Gold 🥇": {
-    "message": "Oro 🥇",
-    "description": "The label for category 'Gold 🥇' in sidebar 'data'"
-  },
-  "sidebar.data.category.APIs Overview": {
-    "message": "Resumen de APIs",
-    "description": "The label for category 'APIs Overview' in sidebar 'data'"
-  },
-  "sidebar.data.category.RPC": {
-    "message": "RPC",
-    "description": "The label for category 'RPC' in sidebar 'data'"
-  },
-  "sidebar.data.category.rpc-admin-guide": {
-    "message": "Guía de administrador",
-    "description": "The label for category 'Admin Guide' in sidebar 'data'"
-  },
-  "sidebar.data.category.rpc-api-reference": {
-    "message": "Referencia de API",
-    "description": "The label for category 'API Reference' in sidebar 'data'"
-  },
-  "sidebar.data.category.Methods": {
-    "message": "Métodos",
-    "description": "The label for category 'Methods' in sidebar 'data'"
-  },
-  "sidebar.data.category.rpc-api-structure": {
-    "message": "Estructura",
-    "description": "The label for category 'Structure' in sidebar 'data'"
-  },
-  "sidebar.data.category.Horizon": {
-    "message": "Horizon",
-    "description": "The label for category 'Horizon' in sidebar 'data'"
-  },
-  "sidebar.data.category.horizon-admin-guide": {
-    "message": "Guía de administrador",
-    "description": "The label for category 'Admin Guide' in sidebar 'data'"
-  },
-  "sidebar.data.category.horizon-api-reference": {
-    "message": "Referencia de API",
-    "description": "The label for category 'API Reference' in sidebar 'data'"
-  },
-  "sidebar.data.category.Resources": {
-    "message": "Recursos",
-    "description": "The label for category 'Resources' in sidebar 'data'"
-  },
-  "sidebar.data.category.Accounts": {
-    "message": "Cuentas",
-    "description": "The label for category 'Accounts' in sidebar 'data'"
-  },
-  "sidebar.data.category.Assets": {
-    "message": "Activos",
-    "description": "The label for category 'Assets' in sidebar 'data'"
-  },
-  "sidebar.data.category.Claimable Balances": {
-    "message": "Saldos reclamables",
-    "description": "The label for category 'Claimable Balances' in sidebar 'data'"
-  },
-  "sidebar.data.category.Effects": {
-    "message": "Efectos",
-    "description": "The label for category 'Effects' in sidebar 'data'"
-  },
-  "sidebar.data.category.Ledgers": {
-    "message": "Ledgers",
-    "description": "The label for category 'Ledgers' in sidebar 'data'"
-  },
-  "sidebar.data.category.Liquidity Pools": {
-    "message": "Fondos de Liquidez",
-    "description": "The label for category 'Liquidity Pools' in sidebar 'data'"
-  },
-  "sidebar.data.category.Offers": {
-    "message": "Ofertas",
-    "description": "The label for category 'Offers' in sidebar 'data'"
-  },
-  "sidebar.data.category.Operations": {
-    "message": "Operaciones",
-    "description": "The label for category 'Operations' in sidebar 'data'"
-  },
-  "sidebar.data.category.The Operation Object": {
-    "message": "El objeto Operación",
-    "description": "The label for category 'The Operation Object' in sidebar 'data'"
-  },
-  "sidebar.data.category.Payments": {
-    "message": "Pagos",
-    "description": "The label for category 'Payments' in sidebar 'data'"
-  },
-  "sidebar.data.category.Trades": {
-    "message": "Comercios",
-    "description": "The label for category 'Trades' in sidebar 'data'"
-  },
-  "sidebar.data.category.Transactions": {
-    "message": "Transacciones",
-    "description": "The label for category 'Transactions' in sidebar 'data'"
-  },
-  "sidebar.data.category.horizon-api-structure": {
-    "message": "Estructura",
-    "description": "The label for category 'Structure' in sidebar 'data'"
-  },
-  "sidebar.data.category.Pagination": {
-    "message": "Paginación",
-    "description": "The label for category 'Pagination' in sidebar 'data'"
-  },
-  "sidebar.data.category.Aggregations": {
-    "message": "Agregaciones",
-    "description": "The label for category 'Aggregations' in sidebar 'data'"
-  },
-  "sidebar.data.category.Order Books": {
-    "message": "Libros de órdenes",
-    "description": "The label for category 'Order Books' in sidebar 'data'"
-  },
-  "sidebar.data.category.Paths": {
-    "message": "Rutas",
-    "description": "The label for category 'Paths' in sidebar 'data'"
-  },
-  "sidebar.data.category.Trade Aggregations": {
-    "message": "Agregaciones de comercio",
-    "description": "The label for category 'Trade Aggregations' in sidebar 'data'"
-  },
-  "sidebar.data.category.Fee Stats": {
-    "message": "Estadísticas de tarifa",
-    "description": "The label for category 'Fee Stats' in sidebar 'data'"
-  },
-  "sidebar.data.category.Errors": {
-    "message": "Errores",
-    "description": "The label for category 'Errors' in sidebar 'data'"
-  },
-  "sidebar.data.category.HTTP Status Codes": {
-    "message": "Códigos de estado HTTP",
-    "description": "The label for category 'HTTP Status Codes' in sidebar 'data'"
-  },
-  "sidebar.data.category.Horizon-Specific Status Codes": {
-    "message": "Códigos de estado específicos de Horizon",
-    "description": "The label for category 'Horizon-Specific Status Codes' in sidebar 'data'"
-  },
-  "sidebar.data.category.Result Codes": {
-    "message": "Códigos de resultado",
-    "description": "The label for category 'Result Codes' in sidebar 'data'"
-  },
-  "sidebar.data.category.Operation-Specific Result Codes": {
-    "message": "Códigos de resultado específicos de operación",
-    "description": "The label for category 'Operation-Specific Result Codes' in sidebar 'data'"
-  },
-  "sidebar.data.category.Indexers": {
-    "message": "Indexadores",
-    "description": "The label for category 'Indexers' in sidebar 'data'"
-  },
-  "sidebar.data.category.Build Your Own": {
-    "message": "Desarrolla el tuyo",
-    "description": "The label for category 'Build Your Own' in sidebar 'data'"
-  },
-  "sidebar.data.category.Galexie": {
-    "message": "Galexie",
-    "description": "The label for category 'Galexie' in sidebar 'data'"
-  },
-  "sidebar.data.category.Admin Guide": {
-    "message": "Guía de administrador",
-    "description": "The label for category 'Admin Guide' in sidebar 'data'"
-  },
-  "sidebar.data.category.galexie-example-usages": {
-    "message": "Ejemplos de uso",
-    "description": "The label for category 'Example Usages' in sidebar 'data'"
-  },
-  "sidebar.data.category.Ingest SDK": {
-    "message": "SDK de ingestión",
-    "description": "The label for category 'Ingest SDK' in sidebar 'data'"
-  },
-  "sidebar.data.category.ingest-sdk-developer-guide": {
-    "message": "Guía de desarrollador",
-    "description": "The label for category 'Developer Guide' in sidebar 'data'"
-  },
-  "sidebar.data.category.Ledger Backends": {
-    "message": "Backends de Ledger",
-    "description": "The label for category 'Ledger Backends' in sidebar 'data'"
-  },
-  "sidebar.data.category.ingest-sdk-example-usages": {
-    "message": "Ejemplos de uso",
-    "description": "The label for category 'Example Usages' in sidebar 'data'"
-  },
-  "sidebar.data.category.Processors": {
-    "message": "Procesadores",
-    "description": "The label for category 'Processors' in sidebar 'data'"
-  },
-  "sidebar.data.category.Token Transfer Processor": {
-    "message": "Procesador de transferencia de token",
-    "description": "The label for category 'Token Transfer Processor' in sidebar 'data'"
-  },
-  "sidebar.data.category.token-transfer-processor-example-usages": {
-    "message": "Ejemplos de uso",
-    "description": "The label for category 'Example Usages' in sidebar 'data'"
-  },
-  "sidebar.data.category.Oracles": {
-    "message": "Oráculos",
-    "description": "The label for category 'Oracles' in sidebar 'data'"
-  }
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/README.mdx
deleted file mode 100644
index 7c278c0bcc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/README.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Documentación para Desarrolladores de Stellar
-displayed_sidebar: build
-hide_table_of_contents: true
-hide_sidebar: true
----
-
-## Navegar por la documentación
-
-### [Construir](./build/README.mdx)
-
-Contiene tutoriales y guías sobre cómo escribir contratos inteligentes, desarrollar aplicaciones, interactuar con la red y más.
-
-### [Aprender](./learn/fundamentals/README.mdx)
-
-Encuentra todo el contenido informativo y conceptual aquí. Aprende sobre los fundamentos de Stellar como cómo funcionan las cuentas y las transacciones, profundiza en la funcionalidad de cada operación, descubre cómo funcionan las tarifas y más.
-
-### [Tokens](./tokens/README.mdx)
-
-Information on how to issue assets on the Stellar network and create contract tokens.
-
-### [Datos](./data/README.mdx)
-
-Descubre varias opciones de disponibilidad de datos: RPC, Hubble, Galexie, el SDK Ingest y Horizon (obsoleto).
-
-### [Herramientas](./tools/README.mdx)
-
-Aprende sobre todas las herramientas disponibles a tu disposición para desarrollar en, interactuar con o simplemente observar la red Stellar. Además, encuentra información sobre cómo utilizar la Anchor Platform o la Stellar Disbursement Platform.
-
-### [Redes](./networks/README.mdx)
-
-Información sobre redes desplegadas (Mainnet, Testnet y Futurenet), versiones actuales de software y limitaciones de recursos y tarifas.
-
-### [Validadores](./validators/README.mdx)
-
-Todo lo que necesitas saber si quieres ejecutar, operar y mantener un nodo validador central en la red Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/README.mdx
deleted file mode 100644
index 97fc1fb092..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/README.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Comenzar con el Desarrollo en Blockchain; Guías, Tutoriales y Herramientas
-sidebar_label: Introducción
-icon: casa
-sidebar_position: 0
-hide_table_of_contents: false
-description: Comenzar a desarrollar en Stellar con guías, tutoriales, herramientas y recursos. Aprende a escribir contratos inteligentes, desarrollar aplicaciones y más.
----
-
-# Introducción
-
-La sección Desarrollada está dividida en tres partes:
-
-1. [Contratos inteligentes](./smart-contracts/README.mdx)
-2. [Aplicaciones](./apps/README.mdx)
-3. [Guías prácticas](./guides/README.mdx)
-
-Las explicaciones de cada sección se indican a continuación:
-
-## Contratos inteligentes
-
-Los contratos inteligentes son programas autoejecutables con los términos de un acuerdo escritos directamente en el código. Automáticamente hacen cumplir y ejecutan los términos del contrato cuando se cumplen condiciones predefinidas. Una vez escritos y probados, los contratos inteligentes se implementan en la blockchain, donde se vuelven inmutables y accesibles públicamente.
-
-:::tip
-
-Al definir las reglas y la lógica del contrato, los desarrolladores deben ser conscientes de la seguridad para evitar vulnerabilidades como desbordamientos de enteros, fallos en el control de acceso y otras explotaciones que podrían comprometer la integridad y funcionalidad del contrato inteligente.
-
-:::
-
-Esta sección te guiará a través de cómo escribir y desplegar contratos inteligentes en Stellar, incluyendo el proceso de instalación, una introducción a las pruebas, almacenamiento de datos y más. También proporciona una variedad de contratos de ejemplo para referencia y uso.
-
-## Aplicaciones
-
-Las aplicaciones interactúan con la blockchain y pueden utilizar contratos inteligentes como el backend.
-
-Ellos:
-
-- Proporcionan interfaces de usuario (UI);
-- Gestionan interacciones de usuario;
-- Se integran con contratos inteligentes para operar.
-
-Escribir **contratos inteligentes** se centra en la lógica y las reglas del backend aplicadas en la blockchain, mientras que **desarrollar aplicaciones** implica crear el frontend e integrarlo con estos contratos inteligentes para proporcionar una experiencia de usuario completa.
-
-:::note
-
-Puedes crear aplicaciones en Stellar sin usar contratos inteligentes, como se demuestra en el [tutorial del SDK de Billetera](./apps/wallet/overview.mdx) o el [tutorial de la Aplicación de Pagos del SDK de JS](./apps/example-application-tutorial/overview.mdx).
-
-:::
-
-Esta sección te guiará a través de consideraciones de diseño para aplicaciones y tutoriales para construir aplicaciones con o sin contratos inteligentes.
-
-## Guías prácticas
-
-Esta sección proporciona instrucciones paso a paso para ayudar a los usuarios a completar tareas específicas asociadas con el desarrollo en Stellar. Estas tareas pueden incluir instrucciones para aspectos de escritura de contratos, interacción con contratos, construcción de aplicaciones, uso de operaciones de Stellar, configuración de infraestructura y más.
-
-:::note
-
-Las guías prácticas suponen que el usuario tiene algo de experiencia y conocimiento sobre cómo construir en Stellar y no están típicamente dirigidas a principiantes.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/README.mdx
deleted file mode 100644
index efb646582e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Crear aplicaciones de Blockchain: guías, herramientas y prácticas recomendadas para el desarrollo"
-sidebar_label: Desarrollar Aplicaciones
-description: Aprende a crear aplicaciones de blockchain con guías, herramientas y prácticas recomendadas. Explora conceptos clave, consejos de integración y recursos para el desarrollo en Stellar.
-sidebar_position: 30
----
-
-# Crear aplicaciones
-
-import DocCardList from "@theme/DocCardList";
-
-Esta sección te guía a través de las consideraciones de diseño para aplicaciones y tutoriales para desarrollar aplicaciones con o sin contratos inteligentes.
-
-<DocCardList />
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
deleted file mode 100644
index 11ee8d63d8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/application-design-considerations.mdx
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: Consideraciones de diseño de la aplicación
-sidebar_position: 10
----
-
-## Modelos de custodia
-
-Al construir una aplicación, una de las primeras cosas que tienes que decidir es cómo se asegurarán y almacenarán las claves secretas de tus usuarios. Las aplicaciones Stellar brindan a los usuarios acceso a sus cuentas que están almacenadas en el ledger, y el acceso a estas cuentas está controlado por la clave secreta de la cuenta. Esa clave secreta prueba que el usuario tiene custodia o "posee" la cuenta.
-
-Hay cuatro opciones de custodia a considerar:
-
-- Servicio no custodial - el usuario de la aplicación almacena su propia clave secreta
-- Servicio custodial - el proveedor de servicios (la aplicación) almacena las claves secretas de los usuarios
-- Mezcla de ambos: con el uso de [multisig](../../learn/fundamentals/transactions/signatures-multisig.mdx), esta opción es útil para mantener el estado no custodial y al mismo tiempo permitir la recuperación de la cuenta
-- Servicios de gestión de claves de terceros - integra un servicio custodial de terceros en tu aplicación que pueda almacenar las claves secretas de tus usuarios
-
-### Servicio no custodial
-
-En un servicio no custodial, el usuario de la aplicación almacena la clave secreta de su cuenta y permite que la aplicación envíe solicitudes para delegar la firma de transacciones. Hay algunos problemas de usabilidad potenciales ya que el usuario tiene que saber cómo almacenar de manera segura sus propias credenciales de cuenta y navegar de forma segura en la firma de transacciones por su parte. Si pierden su clave secreta, también perderán el acceso a su cuenta.
-
-Típicamente, las aplicaciones no custodiales crean o importan una cuenta Stellar preexistente para cada usuario.
-
-### Servicio custodial
-
-Con un servicio custodial, el proveedor de servicios (una aplicación como un exchange centralizado) almacena las claves secretas de los usuarios y delega los derechos de uso al usuario.
-
-Muchos servicios custodiales optan por usar una sola cuenta Stellar agrupada (llamada compartida, omnibus o [cuentas agrupadas](../guides/transactions/pooled-accounts-muxed-accounts-memos.mdx)) para gestionar transacciones en nombre de sus usuarios en lugar de crear una cuenta Stellar nueva para cada usuario. Para distinguir entre usuarios individuales en una cuenta agrupada, recomendamos implementar [cuentas muxed](../guides/transactions/pooled-accounts-muxed-accounts-memos.mdx).
-
-### Una mezcla de no custodial y custodial
-
-Desarrollar una aplicación con capacidades de [multi-firma](../../learn/fundamentals/transactions/signatures-multisig.mdx) te permite tener un servicio no custodial con recuperación de cuenta. Si el usuario pierde su clave secreta, todavía puede firmar transacciones con otras firmas autorizadas, dado que el umbral de firma sea lo suficientemente alto.
-
-### Servicios de gestión de claves de terceros​
-
-Hay varias aplicaciones y servicios que se especializan en agregar capas de seguridad adicionales a las cuentas de los usuarios. Considérelos si estás interesado en integrar un servicio de gestión de claves de terceros:
-
-- [Ledger](https://www.ledger.com/)
-- [Trezor](https://trezor.io/)
-- [StellarGuard](https://stellarguard.me/)
-- [LobstrVault](https://vault.lobstr.co/)
-
-## Seguridad de la aplicación
-
-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).
-
-## Servicios de billetera
-
-Una billetera típicamente tiene estas funciones básicas: almacenamiento de claves, creación de cuentas, firma de transacciones y consultas a la base de datos de Stellar. Hay algunos servicios que se encargan de todas estas funciones por ti, así que puedes construir lo que desees a su alrededor. Consulta algunos de estos servicios de billetera a continuación.
-
-- [Albedo](https://albedo.link/)
-- [Freighter](https://www.freighter.app/)
-
-## Estrategias de creación de cuentas
-
-En esta sección, revisaremos el flujo de creación de cuentas para nuevos usuarios entre billeteras no custodiales y anclajes con implementaciones de SEP-24 y/o SEP-6. Una cuenta Stellar se crea con un keypair (una clave pública y una clave privada) y el saldo mínimo de XLM.
-
-Cuando un nuevo cliente descarga la aplicación de billetera y pasa por el flujo de depósito por primera vez, su cuenta Stellar puede ser creada bien por la aplicación de billetera del usuario o por el anclaje que facilita el primer depósito. Esta sección describe cada una de estas estrategias.
-
-### Opción 1: el anclaje crea y financia la cuenta Stellar​
-
-Para esta opción, la billetera necesita permitir que los usuarios inicien su primer depósito sin tener que agregar un activo/establecer una línea de confianza. La billetera luego solicita al usuario que agregue la línea de confianza una vez que los fondos sean recibidos por el anclaje. El flujo se ve así:
-
-1. La billetera registra un nuevo usuario y emite un keypair.
-2. La billetera inicia el primer depósito en nombre del usuario sin requerir que el usuario agregue el activo/cree la línea de confianza.
-3. El anclaje proporciona instrucciones de depósito al cliente.
-4. El usuario transfiere dinero de su cuenta bancaria a la cuenta bancaria del anclaje.
-5. Una vez que el anclaje recibe la transferencia, el anclaje crea y financia la cuenta Stellar para el cliente.
-6. La billetera detecta que la cuenta ha sido creada y que se debe establecer una línea de confianza.
-7. La billetera solicita al usuario que agregue el activo/cree la línea de confianza.
-8. Finalmente, el anclaje envía los fondos del depósito a la cuenta Stellar del usuario.
-
-:::info
-
-Un anclaje siempre debe mantener una cantidad saludable de XLM en su cuenta de distribución para soportar nuevas creaciones de cuentas. Si hacerlo se vuelve insostenible, se recomienda que el anclaje colabore con billeteras para determinar una estrategia basada en el número de solicitudes de creación de cuentas. La cantidad recomendada es 2XLM por usuario para la creación de cuentas (1XLM para cumplir con el requisito de saldo mínimo, y 1XLM para establecer líneas de confianza y cubrir tarifas de transacción).
-
-:::
-
-Con el flujo descrito arriba, la billetera y el anclaje deben facilitar la escucha y la respuesta al estado de la línea de confianza, lo que puede crear fricciones en la experiencia del usuario al esperar que se establezca la línea de confianza. Para abordar este problema, el Protocolo 15 introdujo saldos reclamables, que mejoran el flujo al permitir que los usuarios empiecen a usar la billetera sin tener que asegurar XLM. Tanto la billetera como el anclaje deben implementar el soporte para saldos reclamables para que este flujo funcione.
-
-El flujo con Saldos Reclamables se ve así:
-
-1. La billetera registra un nuevo usuario y genera un keypair.
-2. La billetera inicia un depósito en nombre de un usuario.
-3. El anclaje proporciona instrucciones de depósito a la billetera.
-4. El usuario transfiere dinero de una cuenta bancaria a la cuenta del anclaje.
-5. El anclaje crea y financia la cuenta Stellar del usuario más la cantidad requerida para líneas de confianza y tarifas de transacción. Nuevamente, sugerimos 2 XLM para comenzar.
-6. El anclaje crea un Saldo Reclamable.
-7. La billetera detecta el Saldo Reclamable para la cuenta, reclama los fondos y los publica en la billetera.
-
-### Opción 2: la billetera crea y financia la cuenta Stellar al registrarse el usuario​
-
-Para esta opción, la billetera crea y financia la cuenta Stellar al registrarse cada nuevo usuario con el requisito mínimo de 1XLM, más el 0.5XLM de reserva para establecer la primera línea de confianza, además de un poco más para cubrir tarifas de transacción. Para más información sobre los saldos mínimos, consulta la [sección de Lumens](../../learn/fundamentals/lumens.mdx#minimum-balance).
-
-El flujo se ve así:
-
-1. Al registrarse un nuevo usuario, la billetera emite un keypair, luego crea y financia la cuenta Stellar del usuario con 2XLM.
-2. Luego, la billetera crea una línea de confianza e inicia el primer depósito.
-3. Una vez que la solicitud de depósito se envía al anclaje, el anclaje proporciona instrucciones para el depósito.
-4. El cliente transfiere fondos desde una cuenta bancaria personal a la cuenta del anclaje.
-5. El anclaje recibe los fondos y luego los envía a la cuenta Stellar del usuario.
-6. La billetera detecta que se enviaron fondos y notifica al usuario.
-
-:::note
-
-En los ejemplos anteriores, sugerimos que el anclaje o la billetera cubran los requisitos de saldo mínimo y de línea de confianza en XLM depositando fondos directamente en la cuenta de un usuario. Hicimos esa sugerencia por simplicidad, pero en todos los casos, el anclaje o la billetera podrían en su lugar usar reservas patrocinadas para asegurar que cuando un usuario cierra una línea de confianza o fusiona su cuenta, la reserva regrese a la cuenta patrocinadora en lugar de a la cuenta del usuario.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/dapp-frontend.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/dapp-frontend.mdx
deleted file mode 100644
index 517b5f226a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/dapp-frontend.mdx
+++ /dev/null
@@ -1,561 +0,0 @@
----
-sidebar_position: 70
-sidebar_label: Crear un frontend de dapp
-title: "Crear un frontend de dapp: Conectar billeteras, manejar transacciones y más"
-description: Aprender a crear un frontend de dapp que se conecte a contratos inteligentes. Explorar prácticas recomendadas para integrar billeteras, manejar transacciones e interactuar con la red Stellar.
----
-
-# Crear un frontend de dapp
-
-Esta es una continuación del [tutorial de Comenzar](../smart-contracts/getting-started/README.mdx), donde deberías haber desplegado dos contratos inteligentes en la red pública. En esta sección, crearemos una aplicación web que interactúe con los contratos a través de llamadas RPC.
-
-Vamos a comenzar.
-
-## Inicializar una herramienta frontend
-
-Puedes crear una aplicación Soroban con cualquier herramienta frontend o integrarla en cualquier aplicación de pila completa existente. Para este tutorial, vamos a usar [Astro](https://astro.build/). Astro funciona con React, Vue, Svelte, cualquier otra biblioteca de interfaz de usuario, o ninguna biblioteca de interfaz de usuario en absoluto. En este tutorial, no estamos usando una biblioteca de interfaz de usuario. Las partes específicas de Soroban de este tutorial serán similares sin importar qué herramienta frontend uses.
-
-Si eres nuevo en el frontend, no te preocupes. No profundizaremos demasiado. Pero será útil para ti ver y experimentar el proceso de desarrollo frontend utilizado por las aplicaciones Soroban. Cubriremos las partes relevantes de JavaScript y Astro, pero enseñar todo el desarrollo frontend y Astro está más allá del alcance de este tutorial.
-
-Vamos a comenzar.
-
-Vas a necesitar [Node.js](https://nodejs.org/en/download/package-manager/) v18.14.1 o superior. Si aún no lo has hecho, instálalo ahora.
-
-Queremos crear un proyecto Astro con los contratos de la lección anterior. Para hacer esto, podemos clonar una plantilla. Puedes encontrar plantillas de Soroban en GitHub buscando [repositorios que comiencen con "soroban-template-"](https://github.com/search?q=%22soroban-template-%22&type=repositories). Para este tutorial, usaremos [stellar/soroban-template-astro](https://github.com/stellar/soroban-template-astro). También utilizaremos una herramienta llamada [degit](https://github.com/Rich-Harris/degit) para clonar la plantilla sin su historial de git. Esto nos permitirá configurarla como nuestro propio proyecto git.
-
-Dado que tienes `node` y su administrador de paquetes `npm` instalados, también tienes `npx`.
-
-Vamos a crear un nuevo directorio de proyecto con esta plantilla para facilitar las cosas en este tutorial, así que asegúrate de que ya no estás en tu directorio `soroban-hello-world` y luego ejecuta:
-
-```sh
-npx degit stellar/soroban-template-astro first-soroban-app
-cd first-soroban-app
-git init
-git add .
-git commit -m "first commit: initialize from stellar/soroban-template-astro"
-```
-
-Este proyecto tiene la siguiente estructura de directorio, que revisaremos con más detalle a continuación.
-
-```bash
-├── contracts
-│   ├── hello_world
-│   └── increment
-├── CONTRIBUTING.md
-├── Cargo.toml
-├── Cargo.lock
-├── initialize.js
-├── package-lock.json
-├── package.json
-├── packages
-├── public
-├── src
-│   ├── components
-│   │   └── Card.astro
-│   ├── env.d.ts
-│   ├── layouts
-│   │   └── Layout.astro
-│   └── pages
-│       └── index.astro
-└── tsconfig.json
-```
-
-Los `contratos` son los mismos que revisaste en los pasos anteriores del tutorial. Dado que ya desplegamos estos contratos con alias, podemos reutilizar los archivos de ID de contrato generados copiándolos desde el directorio `soroban-hello-world/.stellar` en este proyecto:
-
-```sh
-cp -R ../soroban-hello-world/.stellar/ .stellar
-```
-
-## Generar un paquete NPM para el contrato Hello World
-
-Antes de abrir los nuevos archivos frontend, generemos un paquete NPM para el contrato Hello World. Esta es nuestra forma sugerida de interactuar con los contratos desde los frontend. Estas bibliotecas generadas funcionan con cualquier proyecto de JavaScript (no con una UI específica como React), y facilitan el trabajo con algunos de los aspectos más complejos de Soroban, como la codificación de [XDR](../../learn/fundamentals/contract-development/types/fully-typed-contracts.mdx).
-
-Esto va a utilizar el comando CLI `stellar contract bindings typescript`:
-
-```bash
-stellar contract bindings typescript \
-  --network testnet \
-  --contract-id hello_world \
-  --output-dir packages/hello_world
-```
-
-:::tip
-
-¡Nota que pudimos usar el alias del contrato, `hello_world`, en lugar del ID del contrato!
-
-:::
-
-Este proyecto está configurado como un Workspace de NPM, por lo que la biblioteca cliente `hello_world` se generó en el directorio `packages` en `packages/hello_world`.
-
-Intentamos mantener el código en estas bibliotecas generadas legible, así que ve y observa. Abre el nuevo directorio `packages/hello_world` en tu editor. Si has construido o contribuido a proyectos de Node, todo debería parecer familiar. Verás un archivo `package.json`, un directorio `src`, un `tsconfig.json`, e incluso un README.
-
-## Generar un paquete NPM para el contrato Increment
-
-Aunque podemos ejecutar `stellar contract bindings typescript` para cada uno de nuestros contratos individualmente, el proyecto [soroban-template-astro](https://github.com/stellar/soroban-astro-template) que usamos como plantilla incluye un script muy útil `initialize.js` que se encargará de esto para todos los contratos en nuestro directorio `contracts`.
-
-Además de generar los paquetes NPM, `initialize.js` también:
-
-- Generar y financiar nuestra cuenta Stellar
-- Construir todos los contratos en el directorio `contracts`
-- Desplegar nuestros contratos
-- Crear clientes de contrato útiles para cada contrato
-
-Ya nos hemos ocupado de los primeros tres puntos en pasos anteriores de este tutorial, por lo que esas tareas serán noops cuando ejecutemos `initialize.js`.
-
-### Configurar initialize.js
-
-Necesitamos asegurarnos de que `initialize.js` tenga todas las variables de entorno que necesita antes de hacer nada más. Copia el archivo `.env.example` a `.env`. Las variables de entorno establecidas en `.env` son utilizadas por el script `initialize.js`.
-
-```bash
-cp .env.example .env
-```
-
-Veamos el contenido del archivo `.env`:
-
-```
-# Prefix with "PUBLIC_" to make available in Astro frontend files
-PUBLIC_STELLAR_NETWORK_PASSPHRASE="Standalone Network ; February 2017"
-PUBLIC_STELLAR_RPC_URL="http://localhost:8000/soroban/rpc"
-
-STELLAR_ACCOUNT="me"
-STELLAR_NETWORK="standalone"
-```
-
-Este archivo `.env` está configurado para conectarse a una red que se ejecuta localmente, pero queremos configurar nuestro proyecto para comunicarse con Testnet, ya que ahí es donde desplegamos nuestros contratos. Para hacer eso, actualicemos el archivo `.env` para que se vea así:
-
-```diff
-# Prefix with "PUBLIC_" to make available in Astro frontend files
--PUBLIC_STELLAR_NETWORK_PASSPHRASE="Standalone Network ; February 2017"
-+PUBLIC_STELLAR_NETWORK_PASSPHRASE="Test SDF Network ; September 2015"
--PUBLIC_STELLAR_RPC_URL="http://localhost:8000/soroban/rpc"
-+PUBLIC_STELLAR_RPC_URL="https://soroban-testnet.stellar.org:443"
-
--STELLAR_ACCOUNT="me"
-+STELLAR_ACCOUNT="alice"
--STELLAR_NETWORK="standalone"
-+STELLAR_NETWORK="testnet"
-```
-
-:::info
-
-Este archivo `.env` se utiliza en el script `initialize.js`. Al usar la CLI, aún podemos utilizar la configuración de red que establecimos en el paso de [Configuración](../smart-contracts/getting-started/setup.mdx), o pasando las banderas `--rpc-url` y `--network-passphrase`.
-
-:::
-
-### Ejecutar `initialize.js`
-
-Primero, instalemos las dependencias de JavaScript:
-
-```bash
-npm install
-```
-
-Y luego ejecutemos `initialize.js`:
-
-```bash
-npm run init
-```
-
-Como se mencionó anteriormente, este script intenta construir y desplegar nuestros contratos, lo cual ya hemos hecho. El script es lo suficientemente inteligente como para comprobar si un paso ya ha sido tratado, y es un no-op en ese caso, por lo que es seguro ejecutarlo más de una vez.
-
-### Llamar al contrato desde el frontend
-
-Ahora abramos `src/pages/index.astro` y veamos cómo el código frontend se integra con el paquete NPM que creamos para nuestros contratos.
-
-Aquí podemos ver que estamos importando nuestro cliente `helloWorld` generado desde `../contracts/hello_world`. Luego, estamos invocando el método `hello` y agregando el resultado a la página.
-
-```ts title="src/pages/index.astro"
----
-import Layout from "../layouts/Layout.astro";
-import Card from "../components/Card.astro";
-import helloWorld from "../contracts/hello_world";
-const { result } = await helloWorld.hello({ to: "you" });
-const greeting = result.join(" ");
----
-
- ...
-
-<h1>{greeting}</h1>
-```
-
-¡Veamos esto en acción! Inicia el servidor de desarrollo:
-
-```bash
-npm run dev
-```
-
-Y abre [localhost:4321](http://localhost:4321) en tu navegador. ¡Deberías ver el saludo del contrato!
-
-Puedes intentar actualizar el argumento `{ to: 'Soroban' }`. Cuando guardes el archivo, la página se actualizará automáticamente.
-
-:::info
-
-Cuando inicies el servidor de desarrollo con `npm run dev`, verás una salida similar en tu terminal a la que obtuviste cuando ejecutaste `npm run init`. Esto se debe a que el script `dev` en package.json está configurado para ejecutar `npm run init` y `astro dev`, para que puedas asegurarte de que tu contrato desplegado y tu paquete NPM generado estén siempre sincronizados. Si solo quieres iniciar el servidor de desarrollo sin el script initialize.js, puedes ejecutar `npm run astro dev`.
-
-:::
-
-### ¿Qué está pasando aquí?
-
-Si inspeccionas la página (clic derecho, inspeccionar) y actualizas, verás un par de cosas interesantes:
-
-- La pestaña "Red" muestra que no se han realizado solicitudes Fetch/XHR. ¡Pero las llamadas RPC ocurren a través de Fetch/XHR! ¿Entonces, cómo está llamando el frontend al contrato?
-- No hay JavaScript en la página. ¡Pero acabamos de escribir algo de JavaScript! ¿Cómo está funcionando?
-
-Esta es parte de la filosofía de Astro: el frontend debe enviarse con la menor cantidad de activos posible. Prefiriendo cero JavaScript. Cuando pones JavaScript en el [frontmatter](https://docs.astro.build/en/core-concepts/astro-components/), Astro lo ejecutará en el momento de la construcción y luego reemplazará cualquier cosa en los corchetes `{...}` con la salida.
-
-Al usar el servidor de desarrollo con `npm run dev`, se ejecuta el código del frontmatter en el servidor e inyecta los valores resultantes en la página en el cliente.
-
-Puedes intentar construir para ver esto de manera más evidente:
-
-```bash
-npm run build
-```
-
-Luego verifica la carpeta `dist`. Verás que se generó un archivo HTML y CSS, pero no JavaScript. Y si miras el archivo HTML, verás un "Hola Soroban" estático en el `<h1>`.
-
-Durante la construcción, Astro realizó una única llamada a tu contrato, luego inyectó el resultado estático en la página. Esto es genial para métodos de contrato que no cambian, pero probablemente no funcionará para la mayoría de los métodos de contrato. Vamos a integrar con el contrato `incrementor` para ver cómo manejar métodos interactivos en Astro. -->
-
-## Llamar al contrato incrementor desde el frontend
-
-Mientras `hello` es un método simple de solo lectura, `increment` cambia el estado on-chain. Esto significa que alguien necesita firmar la transacción. Así que necesitaremos agregar capacidades de firma de transacciones al frontend.
-
-La forma en que funciona la firma en un navegador es con una _billetera_. Las billeteras pueden ser aplicaciones web, extensiones de navegador, aplicaciones independientes, o incluso dispositivos de hardware separados.
-
-### Instalar la extensión Freighter
-
-En este momento, la billetera que mejor admite Soroban es [Freighter](../guides/freighter/README.mdx). Está disponible como un complemento para Firefox, así como extensiones para Chrome y Brave. Ve y [instálalo ahora](https://freighter.app).
-
-Una vez instalado, ábrelo haciendo clic en el ícono de la extensión. Si esta es tu primera vez usando Freighter, necesitarás crear una nueva billetera. Sigue las indicaciones para crear una contraseña y guardar tu frase de recuperación.
-
-Ve a Configuración (el ícono de la tuerca) → Preferencias y activa la opción para Habilitar Modo Experimental. Luego regresa a su pantalla de inicio y selecciona "Test Net" en el menú desplegable de la esquina superior derecha. Finalmente, si muestra el mensaje de que tu dirección Stellar no está financiada, ve y haz clic en el botón "Financiar con Friendbot".
-
-Ahora estás completamente configurado para usar Freighter como usuario, y puedes agregarlo a tu aplicación.
-
-### Agregar StellarWalletsKit y configurarlo
-
-Aunque estamos usando Freighter para probar nuestra aplicación, hay más billeteras que admiten la firma de transacciones de contratos inteligentes. Para facilitar su integración, estamos utilizando la biblioteca `StellarWalletsKit` que nos permite soportar todas las billeteras Stellar con una sola biblioteca.
-
-Para instalar este kit, vamos a incluir el siguiente paquete:
-
-```shell
-npm install @creit.tech/stellar-wallets-kit
-```
-
-Con el paquete instalado, vamos a crear un nuevo archivo simple donde se encontrarán nuestro kit instanciado y estado simple. Crea el archivo `src/stellar-wallets-kit.ts` y pega esto:
-
-```ts title="src/stellar-wallets-kit.ts"
-import {
-  allowAllModules,
-  FREIGHTER_ID,
-  StellarWalletsKit,
-} from "@creit.tech/stellar-wallets-kit";
-
-const SELECTED_WALLET_ID = "selectedWalletId";
-
-function getSelectedWalletId() {
-  return localStorage.getItem(SELECTED_WALLET_ID);
-}
-
-const kit = new StellarWalletsKit({
-  modules: allowAllModules(),
-  network: import.meta.env.PUBLIC_STELLAR_NETWORK_PASSPHRASE,
-  // StellarWalletsKit forces you to specify a wallet, even if the user didn't
-  // select one yet, so we default to Freighter.
-  // We'll work around this later in `getPublicKey`.
-  selectedWalletId: getSelectedWalletId() ?? FREIGHTER_ID,
-});
-
-export const signTransaction = kit.signTransaction.bind(kit);
-
-export async function getPublicKey() {
-  if (!getSelectedWalletId()) return null;
-  const { address } = await kit.getAddress();
-  return address;
-}
-
-export async function setWallet(walletId: string) {
-  localStorage.setItem(SELECTED_WALLET_ID, walletId);
-  kit.setWallet(walletId);
-}
-
-export async function disconnect(callback?: () => Promise<void>) {
-  localStorage.removeItem(SELECTED_WALLET_ID);
-  kit.disconnect();
-  if (callback) await callback();
-}
-
-export async function connect(callback?: () => Promise<void>) {
-  await kit.openModal({
-    onWalletSelected: async (option) => {
-      try {
-        await setWallet(option.id);
-        if (callback) await callback();
-      } catch (e) {
-        console.error(e);
-      }
-      return option.id;
-    },
-  });
-}
-```
-
-En el código anterior, instanciamos el kit con la configuración deseada y lo exportamos. También envolvemos algunas funciones del kit y añadimos funcionalidad personalizada, como aumentar el kit permitiendo que recuerde qué opciones de billetera fueron seleccionadas entre actualizaciones de página (esa es la parte de `localStorage`). El kit requiere un `selectedWalletId` incluso antes de que el usuario seleccione uno, así que también encontramos una solución a esta limitación, como explica el comentario de código. Puedes aprender más sobre cómo funciona el kit en [la documentación de StellarWalletsKit](https://stellarwalletskit.dev/)
-
-Ahora vamos a añadir un botón "Conectar" a la página que abrirá el modal incorporado del kit e invitará al usuario a usar su billetera preferida. Una vez que el usuario elija su billetera preferida y otorgue permiso para aceptar solicitudes del sitio web, recuperaremos la clave pública y el botón de "Conectar" será reemplazado con un mensaje que dice: "Conectado como [su clave pública]".
-
-Ahora agreguemos un nuevo componente al directorio `src/components` llamado `ConnectWallet.astro` con el siguiente contenido:
-
-```html title="src/components/ConnectWallet.astro"
-<div id="connect-wrap" class="wrap" aria-live="polite">
-  &amp;nbsp;
-  <div class="ellipsis"></div>
-  <button style="display:none" data-connect aria-controls="connect-wrap">
-    Connect
-  </button>
-  <button style="display:none" data-disconnect aria-controls="connect-wrap">
-    Disconnect
-  </button>
-</div>
-
-<style>
-  .wrap {
-    text-align: center;
-    display: flex;
-    width: 18em;
-    margin: auto;
-    justify-content: center;
-    line-height: 2.7rem;
-    gap: 0.5rem;
-  }
-
-  .ellipsis {
-    overflow: hidden;
-    text-overflow: ellipsis;
-    text-align: center;
-    white-space: nowrap;
-  }
-</style>
-
-<script>
-  import { getPublicKey, connect, disconnect } from "../stellar-wallets-kit";
-
-  const ellipsis = document.querySelector(
-    "#connect-wrap .ellipsis",
-  ) as HTMLElement;
-  const connectButton = document.querySelector("[data-connect]") as HTMLButtonElement;
-  const disconnectButton = document.querySelector(
-    "[data-disconnect]",
-  ) as HTMLButtonElement;
-
-  async function showDisconnected() {
-    ellipsis.innerHTML = "";
-    ellipsis.removeAttribute("title");
-    connectButton.style.removeProperty("display");
-    disconnectButton.style.display = "none";
-  }
-
-  async function showConnected() {
-    const publicKey = await getPublicKey();
-    if (publicKey) {
-      ellipsis.innerHTML = `Signed in as ${publicKey}`;
-      ellipsis.title = publicKey ?? "";
-      connectButton.style.display = "none";
-      disconnectButton.style.removeProperty("display");
-    } else {
-      showDisconnected();
-    }
-  }
-
-  connectButton.addEventListener("click", async () => {
-    await connect(showConnected);
-  });
-
-  disconnectButton.addEventListener("click", async () => {
-    disconnect(showDisconnected);
-  });
-
-  if (await getPublicKey()) {
-    showConnected();
-  } else {
-    showDisconnected();
-  }
-</script>
-```
-
-Algunas de estas cosas pueden parecer sorprendentes. ¿`<style>` y `<script>` en medio de la página? ¿Nombres de clase poco creativos como `wrap`? ¿Declaraciones de `import` en un `<script>`? ¿`await` de nivel superior? ¿Qué está pasando aquí?
-
-Astro automáticamente delimita los estilos dentro de un componente a ese componente, así que no hay razón para que tengamos que idear nombres ingeniosos para nuestras clases.
-
-Y todas las declaraciones de `script` se agrupan y se incluyen inteligentemente en la página. Incluso si usas el mismo componente múltiples veces, el script solo se incluirá una vez. Y sí, puedes usar `await` de nivel superior.
-
-Puedes leer más sobre esto en [la página de Astro sobre scripts del lado del cliente](https://docs.astro.build/en/guides/client-side-scripts/).
-
-El código en sí aquí es bastante autocontenido. Importamos `kit` desde el archivo que creamos anteriormente. Entonces, cuando el usuario haga clic en el botón de inicio de sesión, llamamos a la función `connect` que creamos en nuestro archivo `stellar-wallets-kit.ts` anterior. Esto lanzará el modal incorporado de StellarWalletsKit, que permite al usuario elegir entre las opciones de billetera que configuramos (configuramos todas, con `allowAllModules`). Pasamos nuestra propia función `setLoggedIn` como callback, que será llamada en la función `onWalletSelected` en `stellar-wallets-kit.ts`. Terminamos actualizando la interfaz de usuario, según si el usuario está conectado o no.
-
-Ahora podemos importar el componente en el frontmatter de `pages/index.astro`:
-
-```diff title="pages/index.astro"
- ---
- import Layout from '../layouts/Layout.astro';
- import Card from '../components/Card.astro';
- import helloWorld from "../contracts/hello_world";
-+import ConnectWallet from '../components/ConnectWallet.astro'
- ...
-```
-
-Y agregarlo justo debajo del `<h1>`:
-
-```diff title="pages/index.astro"
- <h1>{greeting}</h1>
-+<ConnectWallet />
-```
-
-Si ya no estás ejecutando tu servidor de dev, ve y reinícialo:
-
-```bash
-npm run dev
-```
-
-Luego abre la página y haz clic en el botón "Conectar". You should see Freighter pop up and ask you to sign in. Una vez que lo hagas, el botón debería ser reemplazado con un mensaje que dice: "Conectado como [tu clave pública]".
-
-¡Ahora estás listo para firmar la llamada a `increment`!
-
-### Llamar a `increment`
-
-Ahora podemos importar el cliente del contrato `increment` desde `contracts/increment.ts` y comenzar a usarlo. Nuevamente, crearemos un nuevo componente Astro. Crea un nuevo archivo en `src/components/Counter.astro` con el siguiente contenido:
-
-```html title="src/components/Counter.astro"
-<strong>Incrementor</strong><br />
-Current value: <strong id="current-value" aria-live="polite">???</strong><br />
-<br />
-<button data-increment aria-controls="current-value">Increment</button>
-
-<script>
-  import { getPublicKey, signTransaction } from "../stellar-wallets-kit";
-  import incrementor from "../contracts/increment";
-  const button = document.querySelector(
-    "[data-increment]",
-  ) as HTMLButtonElement;
-  const currentValue = document.querySelector("#current-value") as HTMLElement;
-
-  button.addEventListener("click", async () => {
-    const publicKey = await getPublicKey();
-
-    if (!publicKey) {
-      alert("Please connect your wallet first");
-      return;
-    } else {
-      incrementor.options.publicKey = publicKey;
-      incrementor.options.signTransaction = signTransaction;
-    }
-
-    button.disabled = true;
-    button.classList.add("loading");
-    currentValue.innerHTML =
-      currentValue.innerHTML +
-      '<span class="visually-hidden"> – updating…</span>';
-
-    try {
-      const tx = await incrementor.increment();
-      const { result } = await tx.signAndSend();
-
-      // Only use `innerHTML` with contract values you trust!
-      // Blindly using values from an untrusted contract opens your users to script injection attacks!
-      currentValue.innerHTML = result.toString();
-    } catch (e) {
-      console.error(e);
-    } finally {
-      button.disabled = false;
-      button.classList.remove("loading");
-    }
-  });
-</script>
-```
-
-Esto debería ser algo familiar para ahora. Tenemos un `script` que, gracias al sistema de construcción de Astro, puede `importar` módulos directamente. Usamos `document.querySelector` para encontrar los elementos definidos arriba. Y agregamos un manejador de `click` al botón, que llama a `increment` y actualiza el valor en la página. También establece el botón como `deshabilitado` y agrega una clase de `cargando` mientras la llamada está en progreso para evitar que el usuario haga clic nuevamente y comunicar visualmente que algo está sucediendo. Para las personas que utilizan lectores de pantalla, el estado de carga se comunica con la etiqueta [visualmente oculta](https://www.a11yproject.com/posts/how-to-hide-content/), que será anunciada gracias a las etiquetas `aria` que vimos antes.
-
-La mayor diferencia con la llamada a `greeter.hello` es que esta transacción se ejecuta en dos pasos. La llamada inicial a `increment` construye una transacción de Soroban y luego realiza una llamada RPC para _simularla_. Para llamadas de solo lectura como `hello`, esto es todo lo que necesitas, por lo que puedes obtener el `resultado` de inmediato. Para llamadas de escritura como `increment`, debes `signAndSend` antes de que la transacción sea realmente incluida en el ledger. También necesitas asegurarte de que establezcas un `publicKey` válido y un método `signTransaction`.
-
-:::info
-
-Desestructuración `{ result }`: Si eres nuevo en JavaScript, puede que no sepas lo que está sucediendo con esas líneas `const { result }`. Esto está utilizando la característica de _desestructuración_ de JavaScript. Si la cosa a la derecha del signo igual es un objeto, entonces puedes usar este patrón para obtener rápidamente claves específicas de ese objeto y asignarlas a variables. También puedes nombrar la variable de otra manera, si lo deseas. Por ejemplo, intenta cambiar el código de arriba a:
-
-```ts
-const { result: newValue } = ...
-```
-
-:::
-
-También, ten en cuenta que no necesitas especificar manualmente a Freighter como la billetera en la llamada a `increment`. Esto puede cambiar en el futuro, pero mientras Freighter sea la única opción disponible, estas bibliotecas generadas la utilizan automáticamente. Si deseas anular este comportamiento, puedes pasar una opción `wallet`; consulta la última interfaz `Wallet` en [la fuente de la plantilla](https://github.com/stellar/soroban-tools/blob/main/cmd/crates/soroban-spec-typescript/src/project_template/src/method-options.ts) para más detalles.
-
-Ahora, usemos este componente. En `pages/index.astro`, primero impórtalo:
-
-```diff title="pages/index.astro"
- ---
- import Layout from '../layouts/Layout.astro';
- import Card from '../components/Card.astro';
- import helloWorld from "../contracts/hello_world";
- import ConnectFreighter from '../components/ConnectFreighter.astro';
-+import Counter from '../components/Counter.astro';
- ...
-```
-
-Luego úsalo. Reemplacemos el contenido del párrafo `instrucciones` con él:
-
-```diff title="pages/index.astro"
- <p class="instructions">
--  To get started, open the directory <code>src/pages</code> in your project.<br />
--  <strong>Code Challenge:</strong> Tweak the "Welcome to Astro" message above.
-+  <Counter />
- </p>
-```
-
-Revisa la página; si aún estás ejecutando tu servidor de desarrollo, debería haberse actualizado ya. Haz clic en el botón "Incrementar"; deberías ver una confirmación de Freighter. Confirma, y... ¡el valor se actualiza! 🎉
-
-Obviamente, falta algo de funcionalidad. Por ejemplo, ese `???` es frustrante. Pero nuestro contrato `incrementar` no nos da una manera de consultar el valor actual sin actualizarlo también.
-
-Antes de intentar actualizarlo, simplifiquemos el proceso de creación, implementación y generación de clientes para los contratos.
-
-## Llévalo más allá
-
-Si quieres llevarlo un poco más lejos y asegurarte de entender todas las piezas aquí, prueba lo siguiente:
-
-- Crea una carpeta `src/contracts` con un `greeter.ts` y un `incrementor.ts`. Mueve la lógica de `new Contract({ ... })` a esos archivos. También querrás extraer la variable `rpcUrl` a un archivo `src/contracts/utils.ts`.
-- Agrega un método `get_value` al contrato `incrementar`, y úsalo para mostrar el valor actual en el componente `Contador`. Cuando ejecutes `npm run dev`, el script `initialize` se ejecutará y actualizará el contrato y el cliente generado.
-- Agrega un botón "Decrementar" al componente `Contador`.
-- [Implementa](https://docs.astro.build/en/guides/deploy/) tu frontend. Puedes hacerlo rápido y gratis [con GitHub](https://docs.astro.build/en/guides/deploy/github/). Si tienes problemas al instalar stellar-cli y desplegar contratos en GitHub, consulta [cómo lo hicimos aquí](https://github.com/theahaco/soroban-tutorial-project/commit/c1f4cfde1bbaf059507100767ee6b43d29b42914).
-- En lugar de usar scripts de NPM para todo, intenta usar un corredor de scripts más elegante como [just](https://github.com/casey/just). Los scripts de npm existentes pueden llamar a `just`, como `"setup": "just setup"`.
-- Actualiza el README para explicar qué es este proyecto y cómo usarlo a posibles colaboradores y empleadores 😉
-
-## Resolución de problemas
-
-A veces las cosas salen mal. Como primer paso para solucionar problemas, es posible que quieras [clonar nuestro repositorio tutorial](https://github.com/theahaco/soroban-tutorial-project) y ver si el problema también ocurre allí. Si ocurre allí también, entonces puede ser un problema temporal con la red de Soroban.
-
-Aquí hay algunas incidencias comunes y cómo corregirlas.
-
-### La llamada a `hello` falla
-
-A veces la llamada a `hello` puede comenzar a fallar. Obviamente puedes simular la llamada y definir `result` de otra manera para solucionar problemas.
-
-Uno de los problemas comunes aquí es que el contrato se vuelva [archivado](../../learn/fundamentals/contract-development/storage/state-archival.mdx). Para verificar si este es el problema, puedes ejecutar de nuevo `npm run init`.
-
-Si sigues teniendo problemas, únete a nuestro Discord (enlace de arriba) o [abre un problema en GitHub](https://github.com/stellar/stellar-docs/issues/new/choose).
-
-### Todas las llamadas a contratos comienzan a lanzar errores `403`
-
-Esto significa que Testnet está fuera de servicio, y probablemente solo necesites esperar un poco y volver a intentarlo.
-
-## Conclusión
-
-Algunas de las cosas que hicimos en esta sección:
-
-- Aprendimos sobre el enfoque sin JS por defecto de Astro
-- Agregamos componentes de Astro y aprendimos cómo funcionan sus etiquetas `script` y `style`
-- Vimos lo fácil que es interactuar con contratos inteligentes desde JavaScript generando bibliotecas de clientes usando `stellar contract bindings typescript`
-- Aprendimos sobre billeteras y Freighter
-
-¡En este punto, has visto un ejemplo completo de inicio a fin de la creación de un contrato en Stellar! ¿Qué sigue? ¡Tú decides! Puedes:
-
-- Ver contratos de ejemplo más complejos en la sección [Contratos Ejemplo](../smart-contracts/example-contracts/README.mdx).
-- Aprende más sobre la [arquitectura interna y diseño](../../learn/fundamentals/contract-development/README.mdx) de Soroban.
-- Aprende cómo encontrar varias plantillas además de [stellar/soroban-template-astro](https://github.com/stellar/soroban-astro-template), y cómo crear las tuyas: [Desarrollar plantillas frontend de inicialización de contratos](../guides/dapps/soroban-contract-init-template.mdx)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/README.mdx
deleted file mode 100644
index 580823d49e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 40
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Crear una aplicación de pagos con el SDK de JS
-
-Crea una aplicación básica de pagos para transferir tokens entre cuentas en la Testnet de Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/_category_.json
deleted file mode 100644
index 6a2bd491a9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/_category_.json
+++ /dev/null
@@ -1,7 +0,0 @@
-{
-  "position": 40,
-  "label": "Build a Payment App with the JS SDK",
-  "link": {
-    "type": "generated-index"
-  }
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/account-creation.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/account-creation.mdx
deleted file mode 100644
index c8225cb9c3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/account-creation.mdx
+++ /dev/null
@@ -1,195 +0,0 @@
----
-title: Creación de cuenta
-sidebar_position: 20
----
-
-Las cuentas son la estructura de datos central en Stellar y solo pueden existir con un keypair válido (una clave pública y una clave secreta) y el saldo mínimo requerido de XLM. Lee más en la [sección de cuentas].
-
-## Experiencia del usuario
-
-Para comenzar, haremos que nuestro usuario cree una cuenta. En BasicPay, la página de registro mostrará un keypair público y secreto aleatorizado que el usuario podrá seleccionar con la opción de elegir un nuevo conjunto si lo prefiere.
-
-:::info
-
-Dado que estamos desarrollando una [aplicación no custodia], la clave secreta encriptada solo vivirá en el navegador. Nunca se compartirá con un servidor ni con nadie más.
-
-:::
-
-![claves pública y privada](/assets/basic-pay/public-and-private-keys.png)
-
-A continuación, haremos que el usuario envíe un código PIN para encriptar su clave secreta antes de que se guarde en el `localStorage` de su navegador (esto es manejado por el [`js-stellar-wallets` SDK]). The user will need to remember their pincode for future logins and to submit transactions.
-
-With BasicPay, when the user clicks the “Signup” button, they will be asked to confirm their pincode. When they do, the `create_account` operation is triggered, and the user's account is automatically funded with XLM for the minimum balance (starting with 10,000 XLM).
-
-![cuenta financiada](/assets/basic-pay/funded-account.png)
-
-Cuando estés listo para mover la aplicación a Pubnet, las cuentas deberán ser financiadas con XLM real. Esto es algo que la aplicación puede cubrir depositando XLM en la cuenta del usuario, con el uso de [reservas patrocinadas], o el usuario puede cubrir el saldo requerido con su propio XLM.
-
-## Implementación del código
-
-Crearemos un `store` Svelte para interactuar con el keypair generado aleatoriamente de nuestro usuario. El store aprovechará algunas de las funciones del SDK `js-stellar-wallets` para encriptar/desencriptar el keypair, así como para firmar transacciones.
-
-### Creando el store `walletStore`
-
-Nuestro `walletStore` hará varias cosas posibles a lo largo de nuestra aplicación.
-
-1. Podemos "registrar" un keypair, que encripta el keypair, lo almacena en el almacenamiento del navegador y rastrea el `keyId` de ese keypair.
-2. We can "sign" transactions by providing the pincode to decrypt the keypair.
-3. We can "confirm" the pincode is valid for the stored keypair (or that it matches for signups).
-
-```js title="/src/lib/stores/walletStore.js"
-import { persisted } from "svelte-local-storage-store";
-import { KeyManager, KeyManagerPlugins, KeyType } from "@stellar/wallet-sdk";
-import { TransactionBuilder } from "stellar-sdk";
-import { error } from "@sveltejs/kit";
-import { get } from "svelte/store";
-
-// We are wrapping this store in its own function which will allow us to write
-// and customize our own store functions to maintain consistent behavior
-// wherever the actions need to take place.
-function createWalletStore() {
-  // Make a `persisted` store that will determine which `keyId` the
-  // `keyManager` should load, when the time comes.
-  const { subscribe, set } = persisted("bpa:walletStore", {
-    keyId: "",
-    publicKey: "",
-  });
-
-  return {
-    subscribe,
-
-    // Registers a user by storing their encrypted keypair in the browser's
-    // `localStorage`.
-    register: async ({ publicKey, secretKey, pincode }) => {
-      try {
-        // Get our `KeyManager` to interact with stored keypairs
-        const keyManager = setupKeyManager();
-
-        // Use the `keyManager` to store the key in the browser's local
-        // storage
-        let keyMetadata = await keyManager.storeKey({
-          key: {
-            type: KeyType.plaintextKey,
-            publicKey: publicKey,
-            privateKey: secretKey,
-          },
-          password: pincode,
-          encrypterName: KeyManagerPlugins.ScryptEncrypter.name,
-        });
-
-        // Set the `walletStore` fields for the `keyId` and `publicKey`
-        set({
-          keyId: keyMetadata.id,
-          publicKey: publicKey,
-          // Don't include this in a real-life production application.
-          // It's just here to make the secret key accessible in case
-          // we need to do some manual transactions or something.
-          devInfo: {
-            secretKey: secretKey,
-          },
-        });
-      } catch (err) {
-        console.error("Error saving key", err);
-        throw error(400, { message: err.toString() });
-      }
-    },
-
-    // Compares a submitted pincode to make sure it is valid for the stored, encrypted keypair.
-    confirmCorrectPincode: async ({
-      pincode,
-      firstPincode = "",
-      signup = false,
-    }) => {
-      // If we are not signing up, make sure the submitted pincode successfully
-      // decrypts and loads the stored keypair.
-      if (!signup) {
-        try {
-          const keyManager = setupKeyManager();
-          let { keyId } = get(walletStore);
-          await keyManager.loadKey(keyId, pincode);
-        } catch (err) {
-          throw error(400, { message: "invalid pincode" });
-        }
-        // If we are signing up for the first time (thus, there is no stored
-        // keypair), just make sure the first and second pincodes match.
-      } else {
-        if (pincode !== firstPincode) {
-          throw error(400, { message: "pincode mismatch" });
-        }
-      }
-    },
-
-    // Sign and return a Stellar transaction
-    sign: async ({ transactionXDR, network, pincode }) => {
-      try {
-        // Get our `keyManager` to interact with stored keypairs
-        const keyManager = setupKeyManager();
-
-        // Use the `keyManager` to sign the transaction with the
-        // encrypted keypair
-        let signedTransaction = await keyManager.signTransaction({
-          transaction: TransactionBuilder.fromXDR(transactionXDR, network),
-          id: get(walletStore).keyId,
-          password: pincode,
-        });
-        return signedTransaction;
-      } catch (err) {
-        console.error("Error signing transaction", err);
-        throw error(400, { message: err.toString() });
-      }
-    },
-  };
-}
-
-// We export `walletStore` as the variable that can be used to interact with the wallet store.
-export const walletStore = createWalletStore();
-
-// Configure a `KeyManager` for use with stored keypairs.
-const setupKeyManager = () => {
-  // We make a new `KeyStore`
-  const localKeyStore = new KeyManagerPlugins.LocalStorageKeyStore();
-
-  // Configure it to use `localStorage` and specify a(n optional) prefix
-  localKeyStore.configure({
-    prefix: "bpa",
-    storage: localStorage,
-  });
-
-  // Make a new `KeyManager`, that uses the previously configured `KeyStore`
-  const keyManager = new KeyManager({
-    keyStore: localKeyStore,
-  });
-
-  // Configure the `KeyManager` to use the `scrypt` encrypter
-  keyManager.registerEncrypter(KeyManagerPlugins.ScryptEncrypter);
-
-  // Return the `KeyManager` for use in other functions
-  return keyManager;
-};
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stores/walletStore.js
-
-### Creando la cuenta en la red Stellar
-
-Después de haber registrado al usuario, necesitamos financiar la cuenta en la red Stellar. Como se discutió anteriormente, hay múltiples maneras de lograr esta tarea, pero estamos utilizando Friendbot para asegurarnos de que el usuario tenga algo de XLM en Testnet para experimentar.
-
-```js title="/src/lib/stellar/horizonQueries.js"
-// Fund an account using the Friendbot utility on the Testnet.
-export async function fundWithFriendbot(publicKey) {
-  console.log(`i am requesting a friendbot funding for ${publicKey}`);
-  await server.friendbot(publicKey).call();
-}
-```
-
-Fuente: https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-### Usando el store `walletStore`
-
-Our `walletStore` is used in a ton of places in our application, especially in the confirmation modal when asking a user to input their pincode. Sigue leyendo para ver cómo lo hemos hecho.
-
-[sección de cuentas]: ../../../learn/fundamentals/stellar-data-structures/accounts.mdx
-[aplicación no custodia]: ../application-design-considerations.mdx#non-custodial-service
-[`js-stellar-wallets` sdk]: https://github.com/stellar/js-stellar-wallets
-[reservas patrocinadas]: ../../guides/transactions/sponsored-reserves.mdx
-[lista de contactos]: ./contacts-list
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/README.mdx
deleted file mode 100644
index c6a1a6999f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 60
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Integración Anchor
-
-Interactúa con activos que no son Lumen en tu aplicación. Usa anchors para depósitos y retiradas de fondos para mover tokens dentro o fuera de la red.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/_category_.json
deleted file mode 100644
index 57bc1cfc0a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/_category_.json
+++ /dev/null
@@ -1,7 +0,0 @@
-{
-    "position": 60,
-    "label": "Anchor Integration",
-    "link": {
-      "type": "generated-index"
-    }
-  }
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep1.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep1.mdx
deleted file mode 100644
index 059a9edabf..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep1.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: "SEP-1: Stellar TOML"
-sidebar_position: 20
----
-
-El [archivo `stellar.toml`](../../../../tokens/publishing-asset-info.mdx#completing-your-stellartoml) es un lugar común donde Internet puede encontrar información sobre la integración Stellar de una organización. Independientemente del tipo de transferencia que queramos usar (SEP-6 o SEP-24), necesitamos comenzar con SEP-1.
-
-Para los anchors, nos interesa las `CURRENCIES` que emiten, las palabras clave `TRANSFER_SERVER` y/o `TRANSFER_SERVER_SEP0024` que indican si el anchor admite SEP-6, SEP-24 o ambos, y el `WEB_AUTH_ENDPOINT` que permite a una billetera establecer una sesión de usuario autenticada.
-
-BasicPay está interoperando con el anchor de prueba ubicado en `testanchor.stellar.org` y puedes ver su archivo toml [aquí](https://testanchor.stellar.org/.well-known/stellar.toml).
-
-```js title=/src/lib/stellar/sep1.js
-import { StellarTomlResolver } from "stellar-sdk";
-
-// Fetches and returns the stellar.toml file hosted by a provided domain.
-export async function fetchStellarToml(domain) {
-  let stellarToml = await StellarTomlResolver.resolve(domain);
-  return stellarToml;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep1.js
-
-Hablando estrictamente, la función `StellarTomlResolver` del SDK de JavaScript es la única función que _necesitamos_ para recuperar y usar la información proporcionada por el anchor (de hecho, incluso podríamos escribir nuestra propia función basada en `fetch`, y eludir el SDK por completo). Sin embargo, hemos creado varias funciones "auxiliares" para hacer que el resto de nuestras consultas sea un poco más verbal y claro sobre lo que buscamos del servidor anchor. ¡Asegúrate de revisar el archivo fuente `sep1.js` vinculado arriba!
-
-Usando la información de `stellar.toml` para un activo con un `home_domain`, podemos mostrar al usuario algunas opciones (dependiendo de la infraestructura disponible). Comenzaremos con la autenticación SEP-10.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep10.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
deleted file mode 100644
index e829242048..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep10.mdx
+++ /dev/null
@@ -1,321 +0,0 @@
----
-title: "SEP-10: Stellar Web Authentication"
-sidebar_position: 20
----
-
-import auth_valid from "/assets/basic-pay/auth_valid.png";
-
-Similar a la información del SEP-1, ambos protocolos SEP-6 y SEP-24 utilizan SEP-10 para la autenticación con el usuario. El usuario debe probar que es el propietario de la cuenta antes de poder retirar o depositar activos como parte de SEP-10: Stellar Web Authentication.
-
-Dado que ya tenemos la información del archivo `stellar.toml`, podemos usarla para mostrar algunos elementos interactivos al usuario.
-
-## Solicitar autenticación
-
-:::note
-
-El `/src/routes/dashboard/transfers/+page.svelte` está realizando **mucho** trabajo a lo largo de estas secciones, y lo estamos dividiendo de varias maneras para mostrarlo como parte de este tutorial. Para tener una imagen completa de este archivo, recuerda revisar el código fuente.
-
-:::
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  // `export let data` allows us to pull in any parent load data for use here.
-  /** @type {import('./$types').PageData} */
-  export let data;
-
-  // We import some of our `$lib` functions
-  import { fetchStellarToml } from "$lib/stellar/sep1";
-
-  // An object to easily and consistently class badges based on the status of
-  // a user's authentication token for a given anchor.
-  const authStatusClasses = {
-    unauthenticated: "badge badge-error",
-    auth_expired: "badge badge-warning",
-    auth_valid: "badge badge-success",
-  };
-
-  // A simple function that checks whether a user has a SEP-10 authentication token stored for an anchor, and if it is expired or not.
-  const getAuthStatus = (homeDomain) => {
-    if ($webAuthStore[homeDomain]) {
-      let token = $webAuthStore[homeDomain];
-      if (webAuthStore.isTokenExpired(token)) {
-        return "auth_expired";
-      } else {
-        return "auth_valid";
-      }
-    } else {
-      return "unauthenticated";
-    }
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-## Solicitando una transacción de desafío
-
-Ahora, cuando el usuario hace clic en el botón "autenticar", se activa la función `auth`.
-
-![autenticar](/assets/basic-pay/authenticate.png)
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* This <script> tag has been abbreviated for simplicity */
-
-  import { getChallengeTransaction } from "$lib/stellar/sep10";
-
-  // We import any Svelte components we will need
-  import ConfirmationModal from "$lib/components/ConfirmationModal.svelte";
-
-  // The `open` Svelte context is used to open the confirmation modal
-  import { getContext } from "svelte";
-  const { open } = getContext("simple-modal");
-
-  // Define some component variables that will be used throughout the page
-  let challengeXDR = "";
-  let challengeNetwork = "";
-  let challengeHomeDomain = "";
-
-  // Requests a challenge transaction from a SEP-10 server, and presents it to the user for pincode verification
-  const auth = async (homeDomain) => {
-    // Request the challenge transaction, expecting back the XDR string
-    let { transaction, network_passphrase } = await getChallengeTransaction({
-      publicKey: data.publicKey,
-      homeDomain: homeDomain,
-    });
-
-    // Set the component variables to hold the transaction details
-    challengeXDR = transaction;
-    challengeNetwork = network_passphrase;
-    challengeHomeDomain = homeDomain;
-
-    // Open the confirmation modal for the user to confirm or reject the
-    // challenge transaction. We provide our customized `onAuthConfirm`
-    // function to be called as part of the modal's confirming process.
-    open(ConfirmationModal, {
-      title: "SEP-10 Challenge Transaction",
-      body: "Please confirm your ownership of this account by signing this challenge transaction. This transaction has already been checked and verified and everything looks good from what we can tell. Feel free to double-check that everything lines up with the SEP-10 specification yourself, though.",
-      transactionXDR: challengeXDR,
-      transactionNetwork: challengeNetwork,
-      onConfirm: onAuthConfirm,
-    });
-  };
-
-  /* ... */
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-Como parte de la función `auth`, BasicPay realiza una solicitud `GET` con un parámetro `account` (la clave pública del usuario) al anchor, que devuelve una transacción Stellar firmada con la clave de firma del servidor (llamada una transacción de desafío) con un número de secuencia inválido, por lo que no podría hacer nada si se enviara accidentalmente a la red.
-
-```js title=/src/lib/stellar/sep10.js
-import { Utils } from "stellar-sdk";
-import { fetchStellarToml } from "$lib/stellar/sep1";
-
-// Requests, validates, and returns a SEP-10 challenge transaction from an anchor server.
-export async function getChallengeTransaction({ publicKey, homeDomain }) {
-  let { WEB_AUTH_ENDPOINT, TRANSFER_SERVER, SIGNING_KEY } =
-    await fetchStellarToml(homeDomain);
-
-  // In order for the SEP-10 flow to work, we must have at least a server
-  // signing key, and a web auth endpoint (which can be the transfer server as
-  // a fallback)
-  if (!WEB_AUTH_ENDPOINT || !TRANSFER_SERVER || !SIGNING_KEY) {
-    throw error(500, {
-      message:
-        "could not get challenge transaction (server missing toml entry or entries)",
-    });
-  }
-
-  // Request a challenge transaction for the users's account
-  let res = await fetch(
-    `${WEB_AUTH_ENDPOINT || TRANSFER_SERVER}?${new URLSearchParams({
-      // Possible parameters are `account`, `memo`, `home_domain`, and
-      // `client_domain`. For our purposes, we only supply `account`.
-      account: publicKey,
-    })}`,
-  );
-  let json = await res.json();
-
-  // Validate the challenge transaction meets all the requirements for SEP-10
-  validateChallengeTransaction({
-    transactionXDR: json.transaction,
-    serverSigningKey: SIGNING_KEY,
-    network: json.network_passphrase,
-    clientPublicKey: publicKey,
-    homeDomain: homeDomain,
-  });
-  return json;
-}
-
-// Validates the correct structure and information in a SEP-10 challenge transaction.
-function validateChallengeTransaction({
-  transactionXDR,
-  serverSigningKey,
-  network,
-  clientPublicKey,
-  homeDomain,
-  clientDomain,
-}) {
-  if (!clientDomain) {
-    clientDomain = homeDomain;
-  }
-
-  try {
-    // Use the `readChallengeTx` function from Stellar SDK to read and
-    // verify most of the challenge transaction information
-    let results = Utils.readChallengeTx(
-      transactionXDR,
-      serverSigningKey,
-      network,
-      homeDomain,
-      clientDomain,
-    );
-    // Also make sure the transaction was created for the correct user
-    if (results.clientAccountID === clientPublicKey) {
-      return;
-    } else {
-      throw error(400, {
-        message: "clientAccountID does not match challenge transaction",
-      });
-    }
-  } catch (err) {
-    throw error(400, { message: JSON.stringify(err) });
-  }
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep10.js
-
-## Firmar y enviar la transacción de desafío
-
-En respuesta, el usuario firma la transacción. Puede que hayas notado que presentamos esta transacción de desafío al usuario con nuestro modal de confirmación regular. Una vez que hayan firmado la transacción, la aplicación la envía de vuelta al anchor con una solicitud `POST`. Si la firma es válida, la respuesta de éxito contendrá un [JSON Web Token (JWT)](https://jwt.io/), que BasicPay almacena en la tienda `webAuthStore` para usar en futuras interacciones con el anchor.
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* ... */
-
-  // We import any stores we will need to read and/or write
-  import { invalidateAll } from "$app/navigation";
-  import { walletStore } from "$lib/stores/walletStore";
-  import { webAuthStore } from "$lib/stores/webAuthStore";
-
-  // We import some of our `$lib` functions
-  // highlight-start
-  import {
-    getChallengeTransaction,
-    submitChallengeTransaction,
-  } from "$lib/stellar/sep10";
-  // highlight-end
-
-  // Takes an action after the pincode has been confirmed by the user on a SEP-10 challenge transaction.
-  const onAuthConfirm = async (pincode) => {
-    // Sign the transaction with the user's keypair
-    let signedTransaction = await walletStore.sign({
-      transactionXDR: challengeXDR,
-      network: challengeNetwork,
-      pincode: pincode,
-    });
-    // Submit the signed tx to the SEP-10 server, and get the JWT token back
-    let token = await submitChallengeTransaction({
-      transactionXDR: signedTransaction.toXDR(),
-      homeDomain: challengeHomeDomain,
-    });
-    // Add the token to our store
-    webAuthStore.setAuth(challengeHomeDomain, token);
-    // Reload any relevant `load()` functions (i.e., refresh the page)
-    invalidateAll();
-  };
-
-  /* ... */
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-La función `submitChallengeTransaction` es bastante simple. Tomamos la transacción (en formato XDR) y el nombre de dominio, y la enviamos al `WEB_AUTH_ENDPOINT` relevante proporcionado por el archivo `stellar.toml` del dominio de origen.
-
-```js title=/src/lib/stellar/sep10.js
-// Submits a SEP-10 challenge transaction to an authentication server and returns the SEP-10 token.
-export async function submitChallengeTransaction({
-  transactionXDR,
-  homeDomain,
-}) {
-  let webAuthEndpoint = await getWebAuthEndpoint(homeDomain);
-
-  if (!webAuthEndpoint)
-    throw error(500, {
-      message: "could not authenticate with server (missing toml entry)",
-    });
-  let res = await fetch(webAuthEndpoint, {
-    method: "POST",
-    mode: "cors",
-    headers: { "Content-Type": "application/json" },
-    body: JSON.stringify({ transaction: transactionXDR }),
-  });
-  let json = await res.json();
-
-  if (!res.ok) {
-    throw error(400, { message: json.error });
-  }
-  return json.token;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep10.js
-
-## Acerca de la tienda `webAuthStore`
-
-Como gran parte de nuestra aplicación BasicPay, los diversos tokens de autenticación que el usuario puede haber acumulado con el tiempo se almacenan en el `localStorage` del navegador. No hay nada especial sobre esta tienda en particular, pero aquí está cómo la ensamblamos:
-
-```js title=/src/lib/stores/webAuthStore.js
-import { get } from "svelte/store";
-import { persisted } from "svelte-local-storage-store";
-import { Buffer } from "buffer";
-
-function createWebAuthStore() {
-  const { subscribe, update } = persisted("bpa:webAuthStore", {});
-
-  return {
-    subscribe,
-
-    // Stores a JWT authentication token associated with a home domain server.
-    setAuth: (homeDomain, token) =>
-      update((store) => {
-        return {
-          ...store,
-          [homeDomain]: token,
-        };
-      }),
-
-    // Determine whether or not a JSON web token has an expiration date in the future or in the past.
-    isTokenExpired: (homeDomain) => {
-      let token = get(webAuthStore)[homeDomain];
-      if (token) {
-        let payload = JSON.parse(
-          Buffer.from(token.split(".")[1], "base64").toString(),
-        );
-        let timestamp = Math.floor(Date.now() / 1000);
-        return timestamp > payload.exp;
-      } else {
-        return undefined;
-      }
-    },
-  };
-}
-
-export const webAuthStore = createWebAuthStore();
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stores/webAuthStore.js
-
-Ahora que hemos autenticado exitosamente a nuestro usuario con un anchor de activos, podemos mostrar y procesar las diversas capacidades de transferencia del anchor en cuestión. Comenzaremos con SEP-6, ya que eso sentará las bases para el SEP-24 que sigue.
-
-<img src={auth_valid} width="70%" />
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
deleted file mode 100644
index 8f45bb6a92..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep24.mdx
+++ /dev/null
@@ -1,279 +0,0 @@
----
-title: "SEP-24: Depósito y retirada alojados"
-sidebar_position: 40
----
-
-import sep24_transfers from "/assets/basic-pay/sep24_transfers.png";
-
-SEP-24 proporciona una manera estándar para que las billeteras y los anchors interactúen, haciendo que el usuario abra una vista web alojada por un anchor para recolectar y manejar la información KYC. En esta integración, la información KYC de un usuario es recolectada y manejada completamente por el anchor. En su mayor parte, después de que se abra la vista web del anchor, BasicPay tendrá poco conocimiento sobre lo que está sucediendo.
-
-:::info
-
-Recuerda, SEP-24 depende de [autenticación SEP-10]. Todo lo que sigue asume que el usuario se ha autenticado exitosamente con el servidor anchor, y que BasicPay tiene acceso a un token de autenticación no expirado para enviar con sus solicitudes.
-
-:::
-
-## Encuentra el `TRANSFER_SERVER_SEP0024` del anchor
-
-Antes de que podamos preguntar algo sobre _cómo_ hacer una transferencia SEP-24, debemos averiguar _dónde_ descubrir esa información. Afortunadamente, el protocolo SEP-1 describe campos estandarizados para averiguar lo que necesitamos.
-
-```js title=/src/lib/stellar/sep1.js
-// Fetches and returns the endpoint used for SEP-24 transfer interactions.
-export async function getTransferServerSep24(domain) {
-  let { TRANSFER_SERVER_SEP0024 } = await fetchStellarToml(domain);
-  return TRANSFER_SERVER_SEP0024;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep1.js
-
-## Obtener `/info`
-
-Nuestra aplicación solicitará el endpoint `/info` del servidor de transferencias del anchor para entender los métodos de transferencia admitidos (depósito, retirada) y los endpoints disponibles, así como características adicionales que pueden estar disponibles durante las transferencias.
-
-<img src={sep24_transfers} width="70%" />
-
-```js title=/src/lib/stellar/sep24.js
-// Fetches and returns basic information about what the SEP-24 transfer server supports.
-export async function getSep24Info(domain) {
-  let transferServerSep24 = await getTransferServerSep24(domain);
-
-  let res = await fetch(`${transferServerSep24}/info`);
-  let json = await res.json();
-
-  if (!res.ok) {
-    throw error(res.status, {
-      message: json.error,
-    });
-  } else {
-    return json;
-  }
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep24.js
-
-## El usuario hace clic en "depositar" o "retirar"
-
-Ahora que tenemos toda la información SEP-24 que el anchor nos ha hecho disponible, depende del usuario comenzar el proceso de iniciación. En BasicPay, lo hacen simplemente haciendo clic en un botón que luego activará la función `launchTransferWindowSep24`.
-
-:::note
-
-Este archivo fue cubierto bastante en la [sección SEP-6]. Presentaremos aquí las adiciones que hacemos a este archivo, aunque no repetiremos cosas que ya hemos cubierto. Recuerda revisar los archivos fuente para obtener la imagen completa.
-
-:::
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* This <script> tag has been abbreviated for simplicity */
-
-  // Launch the interactive SEP-24 popup window for the user to interact directly with the anchor to begin a transfer.
-  const launchTransferWindowSep24 = async ({
-    homeDomain,
-    assetCode,
-    assetIssuer,
-    endpoint,
-  }) => {
-    // We initiate the transfer from the SEP-24 server, and get the
-    // interactive URL back from it
-    let { url } = await initiateTransfer24({
-      authToken: $webAuthStore[homeDomain],
-      endpoint: endpoint,
-      homeDomain: homeDomain,
-      urlFields: {
-        asset_code: assetCode,
-        account: data.publicKey,
-      },
-    });
-
-    /* ... */
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-## Recuperar la URL interactiva
-
-Luego, BasicPay inicia un método de transferencia enviando una solicitud `POST` al endpoint de “SEP-24 Depósito” o “SEP-24 Retirada”. El anchor luego envía una URL interactiva que BasicPay abrirá como un popup para que el usuario complete y confirme la transferencia.
-
-```js title=/src/lib/stellar/sep24.js
-// Initiates a transfer using the SEP-24 protocol.
-export async function initiateTransfer24({
-  authToken,
-  endpoint,
-  homeDomain,
-  urlFields = {},
-}) {
-  let transferServerSep24 = await getTransferServerSep24(homeDomain);
-
-  let res = await fetch(
-    `${transferServerSep24}/transactions/${endpoint}/interactive`,
-    {
-      method: "POST",
-      mode: "cors",
-      headers: {
-        "Content-Type": "application/json",
-        Authorization: `Bearer ${authToken}`,
-      },
-      body: JSON.stringify(urlFields),
-    },
-  );
-  let json = await res.json();
-
-  if (!res.ok) {
-    throw error(res.status, {
-      message: json.error,
-    });
-  } else {
-    return json;
-  }
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep24.js
-
-## Lanzar la ventana emergente y escuchar un callback
-
-BasicPay no necesita (ni quiere) saber todo lo que está sucediendo entre el usuario y el anchor durante una transferencia SEP-24. Sin embargo, _sí_ queremos saber cuándo la interacción ha terminado, ya que podemos necesitar tomar alguna acción en ese momento. Así que, añadimos un callback a la URL interactiva y abrimos la ventana emergente.
-
-:::caution
-
-Dado que BasicPay es una aplicación completamente del lado del cliente, no podemos proporcionar un callback como una URL. Así que, estamos usando un callback `postMessage`. Para más información sobre los detalles de estas opciones de callback, revisa [esta sección de la especificación SEP-24].
-
-:::
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* This <script> tag has been abbreviated for simplicity */
-
-  // Launch the interactive SEP-24 popup window for the user to interact directly with the anchor to begin a transfer.
-  const launchTransferWindowSep24 = async ({
-    homeDomain,
-    assetCode,
-    assetIssuer,
-    endpoint,
-  }) => {
-    /* ... */
-
-    // We add our callback method to the end of the URL and launch the popup
-    // window for the user to interact with
-    let interactiveUrl = `${url}&callback=postMessage`;
-    let popup = window.open(interactiveUrl, "bpaTransfer24Window", "popup");
-
-    // We listen for the callback `message` from the popup window
-    window.addEventListener("message", async (event) => {
-      /* ... */
-    });
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-## Completar transferencia
-
-Una vez que el usuario haya terminado con la ventana interactiva del anchor, será llevado de regreso a BasicPay. Almacenamos los detalles de la transferencia en la tienda `transfersStore` (recuerda, esto es solo para que podamos rastrear qué anchors consultar para transferencias más adelante).
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* This <script> tag has been abbreviated for simplicity */
-
-  // Launch the interactive SEP-24 popup window for the user to interact directly with the anchor to begin a transfer.
-  const launchTransferWindowSep24 = async ({
-    homeDomain,
-    assetCode,
-    assetIssuer,
-    endpoint,
-  }) => {
-    /* ... */
-
-    // We listen for the callback `message` from the popup window
-    window.addEventListener("message", async (event) => {
-      // Close the interactive window if it's not already
-      popup?.close();
-
-      // Store the transfer in the browser's localStorage
-      transfers.addTransfer({
-        homeDomain: homeDomain,
-        protocol: "sep24",
-        assetCode: assetCode,
-        transferID: event.data.transaction.id,
-      });
-
-      /* ... */
-    });
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-## (A veces) Enviar un pago Stellar
-
-En una transacción de retirada de fondos, BasicPay también desarrollará y presentará al usuario una transacción Stellar para que la firme con su código PIN.
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* This <script> tag has been abbreviated for simplicity */
-
-  // Launch the interactive SEP-24 popup window for the user to interact directly with the anchor to begin a transfer.
-  const launchTransferWindowSep24 = async ({
-    homeDomain,
-    assetCode,
-    assetIssuer,
-    endpoint,
-  }) => {
-    /* ... */
-
-    // We listen for the callback `message` from the popup window
-    window.addEventListener("message", async (event) => {
-      /* ... */
-
-      // If the user has requested a withdraw with the anchor, they will
-      // need to submit a Stellar transaction that sends the asset from
-      // the user's account to an account controlled by the anchor.
-      if (event.data.transaction.kind === "withdrawal") {
-        // Generate a transaction with the necessary details to complete
-        // the transfer
-        let { transaction, network_passphrase } =
-          await createPaymentTransaction({
-            source: data.publicKey,
-            destination: event.data.transaction.withdraw_anchor_account,
-            asset: `${assetCode}:${assetIssuer}`,
-            amount: event.data.transaction.amount_in,
-            memo: Buffer.from(event.data.transaction.withdraw_memo, "base64"),
-          });
-
-        // Set the component variables to hold the transaction details
-        paymentXDR = transaction;
-        paymentNetwork = network_passphrase;
-
-        // Open the confirmation modal for the user to confirm or reject
-        // the Stellar payment transaction. We provide our customized
-        // `onPaymentConfirm` function to be called as part of the
-        // modal's confirming process.
-        open(ConfirmationModal, {
-          transactionXDR: paymentXDR,
-          transactionNetwork: paymentNetwork,
-          onConfirm: onPaymentConfirm,
-        });
-      }
-    });
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-[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
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep6.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep6.mdx
deleted file mode 100644
index bfbb5abae6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep6.mdx
+++ /dev/null
@@ -1,323 +0,0 @@
----
-title: "SEP-6: API de Depósito y Retirada"
-sidebar_position: 30
----
-
-import useBaseUrl from "@docusaurus/useBaseUrl";
-
-SEP-6 permite que las billeteras y otros clientes interactúen directamente con los anchors sin que el usuario necesite abandonar la billetera para ir al sitio del anchor. En esta integración, la información KYC de un usuario es recopilada y gestionada por la billetera y enviada al anchor _en nombre de_ el usuario.
-
-## Encuentra el `TRANSFER_SERVER` del anchor
-
-Antes de que podamos preguntar algo sobre _cómo_ hacer una transferencia SEP-6, tenemos que averiguar _dónde_ descubrir esa información. Afortunadamente, el protocolo SEP-1 describe campos estandarizados para averiguar lo que necesitamos.
-
-```js title=/src/lib/stellar/sep1.js
-// Fetches and returns the endpoint used for SEP-6 transfer interactions.
-export async function getTransferServerSep6(domain) {
-  let { TRANSFER_SERVER } = await fetchStellarToml(domain);
-  return TRANSFER_SERVER;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep1.js
-
-## Obtener `/info`
-
-Ahora que sabemos dónde se encuentra el servidor de transferencia, BasicPay necesita obtener el endpoint `/info` del servidor de transferencia del anchor para entender los métodos de transferencia admitidos ([depositar, retirar, depositar-intercambio y retirar-intercambio](https://stellar.org/protocol/sep-6#info)) y los endpoints disponibles, así como características adicionales que pueden estar disponibles durante las transferencias.
-
-:::note
-
-En este momento, BasicPay solo admite los métodos de transferencia `depositar` y `retirar`. Una futura versión de este tutorial incorporará los métodos de transferencia `*-intercambio`.
-
-:::
-
-```js title=/src/lib/stellar/sep6.js
-import { getTransferServerSep6 } from "$lib/stellar/sep1";
-
-// Fetches and returns basic information about what the SEP-6 transfer server suppports.
-export async function getSep6Info(domain) {
-  let transferServer = await getTransferServerSep6(domain);
-  let res = await fetch(`${transferServer}/info`);
-  let json = await res.json();
-  return json;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep6.js
-
-## Mostrar elementos interactivos
-
-Dado que muchos de los endpoints SEP-6 (y SEP-24) requieren autenticación, esperamos hasta que nuestro usuario esté [autenticado con SEP-10](./sep10.mdx) antes de mostrar qué tipos de transferencias están disponibles. Cuando tengan un token de autenticación válido, podemos mostrar algunos botones que el usuario puede usar para iniciar una transferencia.
-
-El usuario puede entonces iniciar uno de los métodos de transferencia (en BasicPay, solo se admiten depósitos y retiros) al hacer clic en el botón “Depositar” o “Retirar” debajo de un activo admitido.
-
-![sep6](/assets/basic-pay/sep6_deposit_withdraw.png)
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* This <script> tag has been abbreviated for simplicity */
-
-  // We import things from external packages that will be needed
-  import { LogInIcon, LogOutIcon } from "svelte-feather-icons";
-
-  // We import some of our `$lib` functions
-  import { getSep6Info } from "$lib/stellar/sep6";
-
-  // The `open` Svelte context is used to open the confirmation modal
-  import { getContext } from "svelte";
-  const { open } = getContext("simple-modal");
-
-  /* ... */
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-## Un componente modal SEP-6 especial
-
-Si recuerdas nuestra [sección del modal de confirmación](../confirmation-modal.mdx), diseñamos nuestro componente modal para ser útil para cualquier cosa que pudiéramos requerir. Bueno, eso es _casi_ cierto. El hecho es que las interacciones con SEP-6 son simplemente complejas. Para facilitar esa complejidad, hemos creado un modal de transferencia SEP-6 diseñado específicamente. Hay **tanto** en ello que no podríamos cubrir todo lo que hace aquí. Sin embargo, cubriremos los puntos principales y enlazaremos a los archivos fuente relevantes.
-
-El componente modal en sí se ha dividido en varios componentes Svelte más pequeños. Consulta este archivo fuente para comenzar a mirar cómo lo hemos ensamblado: https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/components/TransferModalSep6.svelte
-
-### Lanzando el modal SEP-6
-
-Los botones anteriores utilizarán la función `launchTransferModalSep6` para mostrar el modal al usuario. Así es como se define en ese mismo archivo.
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* This <script> tag has been abbreviated for simplicity */
-
-  // We import any Svelte components we will need
-  import TransferModalSep6 from "./components/TransferModalSep6.svelte";
-
-  // Launch the SEP-6 modal to begin the transfer process and gather information from the user.
-  const launchTransferModalSep6 = ({
-    homeDomain,
-    assetCode,
-    assetIssuer,
-    endpoint,
-    sep6Info,
-  }) => {
-    // Open the SEP-6 transfer modal, supplying the relevant props for our
-    // desired type of transfer.
-    open(TransferModalSep6, {
-      homeDomain: homeDomain,
-      assetIssuer: assetIssuer,
-      transferData: {
-        endpoint: endpoint,
-      },
-      formData: {
-        account: data.publicKey,
-        asset_code: assetCode,
-      },
-      sep6Info: sep6Info,
-      // This `submitPayment` function is described later on.
-      submitPayment: submitPayment,
-    });
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
-
-Una vez lanzado, el `TransferModalSep6` guiará al usuario a través de un "asistente" para recopilar toda la información requerida y, en última instancia, crear la transferencia.
-
-### Paso del modal 1: Detalles de la transferencia
-
-BasicPay solicita al usuario que ingrese información adicional, como tipo de transferencia, destino y cantidad. Parte de esto se completa automáticamente según el botón que presionó el usuario. Sin embargo, el usuario puede cambiar cualquiera de los campos si así lo elige.
-
-Vamos a omitir el ejemplo de código en esta sección, ya que principalmente son cosas de Svelte. Puedes ver el código fuente aquí: https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/components/TransferDetails.svelte
-
-<img
-  src={useBaseUrl("/assets/basic-pay/sep6_transfer_details.png")}
-  width="45%"
-/>
-
-### Paso del modal 2: Recopilar información KYC
-
-Para averiguar qué infraestructura ha puesto a nuestra disposición el anchor, necesitamos consultar el archivo `stellar.toml` del anchor para el campo `KYC_SERVER`. Si no se define esto, BasicPay recurrirá al uso del `TRANSFER_SERVER` para estas solicitudes.
-
-```js title=/src/lib/stellar/sep1.js
-// Fetches and returns the endpoint used for SEP-12 KYC interactions.
-export async function getKycServer(domain) {
-  let { KYC_SERVER, TRANSFER_SERVER } = await fetchStellarToml(domain);
-  // If `KYC_SERVER` is undefined in the domain's TOML file, `TRANSFER_SERVER`
-  // will be used
-  return KYC_SERVER ?? TRANSFER_SERVER;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep1.js
-
-Nuestro modal SEP-6 luego consulta el endpoint SEP-12 del anchor para los campos KYC requeridos con una solicitud `GET`, y presentamos estos campos para que el usuario los complete.
-
-<img src={useBaseUrl("/assets/basic-pay/sep6_kyc.png")} width="45%" />
-
-```js title=/src/lib/stellar/sep12.js
-import { getKycServer } from "$lib/stellar/sep1";
-
-// Sends a `GET` request to query KYC status for a customer, returns current status of KYC submission
-export async function getSep12Fields({ authToken, homeDomain }) {
-  let kycServer = await getKycServer(homeDomain);
-
-  let res = await fetch(`${kycServer}/customer`, {
-    method: "GET",
-    headers: {
-      "Content-Type": "application/json",
-      Authorization: `Bearer ${authToken}`,
-    },
-  });
-  let json = await res.json();
-
-  return json;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep12.js
-
-Una vez más, la presentación de los campos que el usuario debe completar está más del lado de Svelte, así que no compartiremos esos detalles aquí. Sin embargo, la fuente para este componente está disponible aquí: https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/components/KYCInformation.svelte
-
-### Paso del modal 3: Poner campos KYC y reportar estado
-
-Ahora que el usuario ha proporcionado la información necesaria para los requisitos KYC del anchor, podemos enviarlos al servidor KYC del anchor con una solicitud `PUT`.
-
-```js title=/src/lib/stellar/sep12.js
-// Sends a `PUT` request to the KYC server, submitting the supplied fields for the customer's record.
-export async function putSep12Fields({ authToken, fields, homeDomain }) {
-  let kycServer = await getKycServer(homeDomain);
-
-  let res = await fetch(`${kycServer}/customer`, {
-    method: "PUT",
-    mode: "cors",
-    headers: {
-      "Content-Type": "application/json",
-      Authorization: `Bearer ${authToken}`,
-    },
-    body: JSON.stringify(fields),
-  });
-  let json = await res.json();
-
-  return json;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep12.js
-
-BasicPay recibe de vuelta del anchor un mensaje de estado para que el usuario lo vea. Una vez que el mensaje de estado es `ACEPTADO`, ¡podemos finalmente enviar la solicitud de transferencia real!
-
-<img src={useBaseUrl("/assets/basic-pay/kyc_accepted.png")} width="50%" />
-
-Este componente del modal SEP-6, como la mayoría de ellos, está casi completamente relacionado con Svelte. Por lo tanto, para mantener este tutorial (algo) despejado, te referiremos a la fuente del componente, que puedes encontrar aquí: https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/components/KYCStatus.svelte
-
-### Paso del modal 4: Enviar transferencia
-
-BasicPay realiza esta solicitud tomando todos los campos que se han recopilado durante este proceso y envolviéndolos en una URL que contiene parámetros de consulta: [ejemplo](https://testanchor.stellar.org/sep6/deposit?account=GAXQIC2BSZ5HZP3BD6RZQSD3LB66TB6A2TA5W3LZX2VDFMBAKHC4B62J&asset_code=SRT&type=bank_account&amount=11)
-
-Enviamos una solicitud `GET` a la URL con nuestro token de autorización en los encabezados, y el anchor se encarga de eso!
-
-```js title=/src/lib/stellar/sep6.js
-// Initiates a transfer using the SEP-6 protocol.
-export async function initiateTransfer6({
-  authToken,
-  endpoint,
-  formData,
-  domain,
-}) {
-  let transferServer = await getTransferServerSep6(domain);
-  let searchParams = new URLSearchParams(formData);
-
-  let res = await fetch(`${transferServer}/${endpoint}?${searchParams}`, {
-    method: "GET",
-    mode: "cors",
-    headers: {
-      "Content-Type": "application/json",
-      Authorization: `Bearer ${authToken}`,
-    },
-  });
-  let json = await res.json();
-
-  if (!res.ok) {
-    throw error(res.status, {
-      message: json.error,
-    });
-  } else {
-    return json;
-  }
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/sep12.js
-
-Luego almacenamos los detalles de la transferencia en la tienda `transfersStore` y mostramos la respuesta del servidor de transferencia al usuario. Luego esperamos a que cierren el modal.
-
-:::note
-
-La única razón por la que estamos almacenando algo sobre la transferencia en BasicPay es para ayudarnos a llevar un registro de con qué anchors el usuario ha iniciado transferencias. De lo contrario, no podríamos consultar un historial de transferencias (como en la página `/dashboard`).
-
-:::
-
-### (A veces) Paso del modal 5: Enviar un pago Stellar
-
-En una transacción de retirada de fondos, BasicPay también desarrollará y presentará al usuario una transacción Stellar para que firme con su PIN. Aquí finalmente volveremos a nuestro modal "regular" que _es_ tan bueno en tantas cosas!
-
-```html title=/src/routes/dashboard/transfers/+page.svelte
-<script>
-  /* This <script> tag has been abbreviated for simplicity */
-
-  // Define some component variables that will be used throughout the page
-  let paymentXDR = "";
-  let paymentNetwork = "";
-
-  // After a withdraw transaction has been presented to the user, and they've confirmed with the correct pincode, sign and submit the transaction to the Stellar network.
-  const onPaymentConfirm = async (pincode) => {
-    // Use the walletStore to sign the transaction
-    let signedTransaction = await walletStore.sign({
-      transactionXDR: paymentXDR,
-      network: paymentNetwork,
-      pincode: pincode,
-    });
-    // Submit the transaction to the Stellar network
-    await submit(signedTransaction);
-  };
-
-  // Builds a Stellar payment to present to the user which will complete a transfer to the Anchor.
-  let submitPayment = async ({
-    withdrawDetails,
-    assetCode,
-    assetIssuer,
-    amount,
-  }) => {
-    let { transaction, network_passphrase } = await createPaymentTransaction({
-      source: data.publicKey,
-      destination: withdrawDetails.account_id,
-      asset: `${assetCode}:${assetIssuer}`,
-      amount: amount,
-      memo: withdrawDetails.memo
-        ? Buffer.from(withdrawDetails.memo, "base64")
-        : undefined,
-    });
-
-    // Set the component variables to hold the transaction details
-    paymentXDR = transaction;
-    paymentNetwork = network_passphrase;
-
-    // We close the SEP-6 modal, and open the regular confirmation modal
-    close();
-    open(ConfirmationModal, {
-      transactionXDR: paymentXDR,
-      transactionNetwork: paymentNetwork,
-      onConfirm: onPaymentConfirm,
-    });
-  };
-
-  /* ... */
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.svelte
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/setup.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/setup.mdx
deleted file mode 100644
index 236ba7ba10..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/setup.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Configuración para Activos Anclados
-sidebar_position: 10
----
-
-Un ancla es un término específico de Stellar para las rampas de entrada y salida que conectan la red Stellar con vías de pago tradicionales, como instituciones financieras o empresas fintech. Cuando un usuario deposita con un ancla, ese ancla acreditará su cuenta Stellar con la cantidad equivalente de tokens digitales. El usuario puede entonces mantener, transferir o comerciar esos tokens como cualquier otro activo Stellar. Cuando un usuario retira esos tokens, el ancla los canjea por efectivo o dinero en el banco. Lee más sobre los anclajes en esta [sección de anclajes](../../../../learn/fundamentals/anchors.mdx).
-
-Cuando un cliente descarga una aplicación de billetera que está conectada a un servicio de ancla, su cuenta Stellar puede ser creada por la aplicación de billetera o el servicio de ancla. En este ejemplo, la cuenta ha sido creada por la aplicación de billetera, BasicPay. Las estrategias de creación de cuentas se describen con más detalle [aquí](../../application-design-considerations.mdx#account-creation-strategies).
-
-En este ejemplo, utilizaremos un ancla en la Testnet de Stellar para simular una transferencia bancaria dentro y fuera de la billetera del usuario utilizando [SEP-6: API de Depósito y Retirada](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) y/o [SEP-24: Depósito y Retirada Alojada](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md).
-
-:::info
-
-Los SEPs definen estándares decididos por la comunidad para la interoperabilidad en Stellar. Lee más en nuestra [sección de SEPs](../../../../learn/fundamentals/stellar-ecosystem-proposals.mdx).
-
-:::
-
-También utilizaremos las siguientes SEPs:
-
-- [SEP-1: Stellar TOML](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) - un archivo que proporciona un lugar para que Internet encuentre información sobre la integración de Stellar de una organización
-- [SEP-9: Campos KYC Estándar](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md) - define una lista de campos KYC estándar para uso en protocolos del ecosistema Stellar
-- [SEP-10: Autenticación Web de Stellar](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) - define la manera estándar para que los clientes creen sesiones web autenticadas en nombre de un usuario que posee una cuenta Stellar
-- [SEP-12: API KYC](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md) - define una manera estándar para que los clientes de Stellar suban información KYC a los anclajes
-
-## Encontrando activos anclados
-
-BasicPay se encarga de todos los detalles de transferencia de anclajes en la página `/dashboard/transfers`. Véalo en acción aquí: https://basicpay.pages.dev/dashboard/transfers
-
-Necesitamos que nuestra aplicación sepa cómo puede comunicarse con los anclajes para obtener información sobre activos e infraestructura. Lo primero que haremos es determinar si el usuario tiene líneas de confianza a algún activo que tenga un campo `home_domain` configurado en la red Stellar. La presencia de ese campo en la cuenta de un emisor nos dice que el activo _puede_ estar conectado a las vías de pago existentes de Stellar, permitiendo la transferencia del activo. Si está presente, mostraremos algunos elementos interactivos al usuario para ese activo/dominio.
-
-```js title=/src/routes/dashboard/transfers/+page.js
-import { fetchAssetsWithHomeDomains } from "$lib/stellar/horizonQueries";
-
-/** @type {import('./$types').PageLoad} */
-export async function load({ parent }) {
-  const { balances } = await parent();
-  return {
-    /** @type {import('$lib/stellar/horizonQueries').HomeDomainBalanceLine[]} */
-    homeDomainBalances: await fetchAssetsWithHomeDomains(balances),
-  };
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/transfers/+page.js
-
-Ahora sabemos si hay activos que el usuario posee que pueden tener la infraestructura necesaria para transferencias autenticadas y podemos consultar el dominio en cuestión para los detalles relevantes.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/confirmation-modal.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/confirmation-modal.mdx
deleted file mode 100644
index 21e6748c0c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/confirmation-modal.mdx
+++ /dev/null
@@ -1,250 +0,0 @@
----
-title: Modal de Confirmación
-sidebar_position: 22
----
-
-Dado que el keypair del usuario está encriptado con un pincode y almacenado en su navegador, a veces necesitaremos pedirle ese pincode para firmar una transacción o de otro modo probar que debe permitírsele realizar alguna acción o ver algunos datos.
-
-## Experiencia del Usuario
-
-El usuario debe ser informado sobre cualquier acción que pueda llevarse a cabo, especialmente cuando hay fondos en juego. Para asegurarnos de esto, solicitaremos abiertamente su confirmación a través del pincode antes de realizar cualquier acción. La aplicación no tiene forma de conocer el pincode de un usuario, por lo que no puede desencriptar su keypair sin su confirmación.
-
-La ventana modal que hemos implementado facilita este flujo de confirmación siempre que lo necesitemos.
-
-![modal de confirmación](/assets/basic-pay/confirm-pincode.png)
-
-## Implementación del Código
-
-Nuestra función modal utiliza el paquete `svelte-simple-modal` para darnos un punto de partida versátil. Si lo necesitas, instálalo ahora.
-
-```bash npm2yarn
-npm install --save-dev svelte-simple-modal
-```
-
-### Envolver el resto de nuestra aplicación en la modal
-
-En el lado de Svelte, este componente modal será un "envoltorio" alrededor del resto de nuestra aplicación, lo que nos permite activar la modal desde cualquier lugar que necesitemos, y debería comportarse de manera similar sin importar qué.
-
-```html title="/src/routes/+layout.svelte"
-<script>
-  import "../app.postcss";
-
-  // We will use a `writable` Svelte store to trigger our modal
-  // highlight-next-line
-  import { writable } from "svelte/store";
-
-  // We have a custom close button for consistent styling, but this is NOT a requirement.
-  // highlight-start
-  import ModalCloseButton from "$lib/components/ModalCloseButton.svelte";
-  import Modal from "svelte-simple-modal";
-  const modal = writable(null);
-  // highlight-end
-</script>
-
-// highlight-next-line
-<Modal
-  show="{$modal}"
-  closeButton="{ModalCloseButton}"
-  classContent="rounded bg-base-100"
->
-  <slot />
-  // highlight-next-line
-</Modal>
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/+layout.svelte
-
-### Crear un componente modal reutilizable en Svelte
-
-Para evitar reinventar la rueda cada vez que necesitamos una modal, crearemos un componente reutilizable que puede acomodar la mayoría de nuestras necesidades. Luego, cuando necesitemos la modal de confirmación, podemos pasar un objeto de props para personalizar el comportamiento de la modal.
-
-:::note
-
-En nuestros archivos de componentes `*.svelte`, **no** profundizaremos en el marcado HTML fuera de las etiquetas `<script>`. La sintaxis de Svelte utilizada en HTML se usa principalmente para iterar y es bastante comprensible de leer.
-
-:::
-
-Las partes básicas de este componente se ven así:
-
-```html title="/src/lib/components/ConfirmationModal.svelte"
-<script>
-  import { copy } from "svelte-copy";
-  import { CopyIcon } from "svelte-feather-icons";
-  import { errorMessage } from "$lib/stores/alertsStore";
-  import { walletStore } from "$lib/stores/walletStore";
-  import { Networks, TransactionBuilder } from "stellar-sdk";
-
-  // A Svelte "context" is used to control when to `open` and `close` a given
-  // modal from within other components
-  import { getContext } from "svelte";
-  const { close } = getContext("simple-modal");
-
-  export let title = "Transaction Preview";
-  export let body =
-    "Please confirm the transaction below in order to sign and submit it to the network.";
-  export let confirmButton = "Confirm";
-  export let rejectButton = "Reject";
-  export let hasPincodeForm = true;
-  export let transactionXDR = "";
-  export let transactionNetwork = "";
-  export let firstPincode = "";
-
-  let isWaiting = false;
-  let pincode = "";
-  $: transaction = transactionXDR
-    ? TransactionBuilder.fromXDR(
-        transactionXDR,
-        transactionNetwork || Networks.TESTNET,
-      )
-    : null;
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/components/ConfirmationModal.svelte
-
-### Activar el componente modal al registrarse
-
-Ahora podemos usar este componente modal cada vez que necesitemos confirmar algo del usuario. Por ejemplo, aquí está cómo se activa la modal cuando alguien se registra.
-
-```html title="/src/routes/signup/+page.svelte"
-<script>
-  import { Keypair } from "stellar-sdk";
-  import TruncatedKey from "$lib/components/TruncatedKey.svelte";
-  import ConfirmationModal from "$lib/components/ConfirmationModal.svelte";
-  import { goto } from "$app/navigation";
-  import { walletStore } from "$lib/stores/walletStore";
-  import { fundWithFriendbot } from "$lib/stellar/horizonQueries";
-
-  // The `open` Svelte context is used to open the confirmation modal
-  import { getContext } from "svelte";
-  const { open } = getContext("simple-modal");
-
-  // Define some component variables that will be used throughout the page
-  let keypair = Keypair.random();
-  $: publicKey = keypair.publicKey();
-  $: secretKey = keypair.secret();
-  let showSecret = false;
-  let pincode = "";
-
-  // This function is run when the user submits the form containing the public
-  // key and their pincode. We pass an object of props that corresponds to the
-  // series of `export let` declarations made in our modal component.
-  const signup = () => {
-    open(ConfirmationModal, {
-      firstPincode: pincode,
-      title: "Confirm Pincode",
-      body: "Please re-type your 6-digit pincode to encrypt the secret key.",
-      rejectButton: "Cancel",
-    });
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/signup/+page.svelte
-
-### Personalizar el comportamiento de confirmación y rechazo
-
-Ahora, a medida que estos componentes han sido escritos hasta ahora, en realidad no _hacen_ nada cuando el usuario introduce su pincode o hace clic en un botón. ¡Cambiemos eso!
-
-Dado que el comportamiento de confirmación debe variar según las circunstancias (por ejemplo, diferentes acciones para el registro, la presentación de transacciones, etc.), necesitamos una forma de pasar eso como una prop cuando abrimos la ventana modal.
-
-Primero, en nuestro componente modal, declaramos una función dummy para actuar como una prop, así como una función "interna" que llamará a la función prop durante el curso de la ejecución.
-
-```html title="/src/lib/components/ConfirmationModal.svelte"
-<script>
-  /* ... */
-
-  // `onConfirm` is a prop function that will be overridden from the component
-  // that launches the modal
-  export let onConfirm = async () => {};
-  // `_onConfirm` is actually run when the user clicks the modal's "confirm"
-  // button, and calls (in-turn) the supplied `onConfirm` function
-  const _onConfirm = async () => {
-    isWaiting = true;
-    try {
-      // We make sure the user has supplied the correct pincode
-      await walletStore.confirmPincode({
-        pincode: pincode,
-        firstPincode: firstPincode,
-        signup: firstPincode ? true : false,
-      });
-
-      // We call the `onConfirm` function that was given to the modal by
-      // the outside component.
-      await onConfirm(pincode);
-
-      // Now we can close this modal window
-      close();
-    } catch (err) {
-      // If there was an error, we set our `errorMessage` alert
-      errorMessage.set(err.body.message);
-    }
-    isWaiting = false;
-  };
-
-  // Just like above, `onReject` is a prop function that will be overridden
-  // from the component that launches the modal
-  export let onReject = () => {};
-  // Just like above, `_onReject` is actually run when the user clicks the
-  // modal's "reject" button, and calls (if provided) the supplied `onReject`
-  // function
-  const _onReject = () => {
-    // We call the `onReject` function that was given to the modal by the
-    // outside component.
-    onReject();
-    close();
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/components/ConfirmationModal.svelte
-
-Ahora que nuestro componente modal está configurado para utilizar una función prop para la confirmación y el rechazo, podemos declarar lo que esas funciones deberían hacer dentro de la página que genera la modal.
-
-```html title="/src/routes/signup/+page.svelte"
-<script>
-  /* ... */
-
-  // highlight-start
-  const onConfirm = async (pincode) => {
-    // Register the encrypted keypair in the user's browser
-    await walletStore.register({
-      publicKey: publicKey,
-      secretKey: secretKey,
-      pincode: pincode,
-    });
-
-    // Fund the account with a request to Friendbot
-    await fundWithFriendbot(publicKey);
-
-    // If the registration was successful, redirect to the dashboard
-    if ($walletStore.publicKey) {
-      goto("/dashboard");
-    }
-  };
-  // highlight-end
-
-  const signup = () => {
-    open(ConfirmationModal, {
-      firstPincode: pincode,
-      title: "Confirm Pincode",
-      body: "Please re-type your 6-digit pincode to encrypt the secret key.",
-      rejectButton: "Cancel",
-      // highlight-next-line
-      onConfirm: onConfirm,
-    });
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/signup/+page.svelte
-
-Como puedes ver, en realidad no necesitábamos una función `onReject` personalizada, así que no pasamos ninguna. ¡Sin daño, sin falta!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/contacts-list.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/contacts-list.mdx
deleted file mode 100644
index f04e6d06c3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/contacts-list.mdx
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: Lista de contactos
-sidebar_position: 25
----
-
-Una característica central de BasicPay es una lista de contactos que contiene el nombre de un usuario y las direcciones Stellar asociadas.
-
-## Experiencia del usuario
-
-Hay varias formas para que un usuario interactúe con la lista de contactos. Una forma es que pueden añadir un usuario y una dirección en la página `/dashboard/contacts` (que también verifica si la clave pública es válida!).
-
-![lista de contactos](/assets/basic-pay/add-contact.png)
-
-Velo en acción aquí: https://basicpay.pages.dev/dashboard/contacts
-
-## Implementación de código
-
-Crearemos un `store` de Svelte para hacer un seguimiento de la lista de contactos de un usuario.
-
-### Creando el `store` de `contacts`
-
-Al igual que con el resto de nuestros datos de usuario, la lista de contactos vivirá en el `localStorage` del navegador. Estamos usando el [paquete `svelt-local-storage-store`] para facilitar esto. Creamos un `store` de Svelte para contener los datos, y añadimos varias funciones personalizadas para gestionar la lista: `empty`, `remove`, `add`, `favorite` y `lookup`.
-
-:::note
-
-Este código tutorial está simplificado para mostrarlo aquí. El código está completamente tipado, documentado y comentado en el [repositorio de código fuente].
-
-:::
-
-```js title="/src/lib/stores/contactsStore.js"
-import { v4 as uuidv4 } from "uuid";
-import { persisted } from "svelte-local-storage-store";
-import { StrKey } from "stellar-sdk";
-import { error } from "@sveltejs/kit";
-import { get } from "svelte/store";
-
-// We are wrapping this store in its own function which will allow us to write
-// and customize our own store functions to maintain consistent behavior
-// wherever the actions need to take place.
-function createContactsStore() {
-  // Make a `persisted` store that will hold our entire contact list.
-  const { subscribe, set, update } = persisted("bpa:contactList", []);
-
-  return {
-    subscribe,
-
-    // Erases all contact entries from the list and creates a new, empty contact list.
-    empty: () => set([]),
-
-    // Removes the specified contact entry from the list.
-    remove: (id) =>
-      update((list) => list.filter((contact) => contact.id !== id)),
-
-    // Adds a new contact entry to the list with the provided details.
-    add: (contact) =>
-      update((list) => {
-        if (StrKey.isValidEd25519PublicKey(contact.address)) {
-          return [...list, { ...contact, id: uuidv4() }];
-        } else {
-          throw error(400, { message: "invalid public key" });
-        }
-      }),
-
-    // Toggles the "favorite" field on the specified contact.
-    favorite: (id) =>
-      update((list) => {
-        const i = list.findIndex((contact) => contact.id === id);
-        if (i >= 0) {
-          list[i].favorite = !list[i].favorite;
-        }
-        return list;
-      }),
-
-    // Searches the contact list for an entry with the specified address.
-    lookup: (address) => {
-      let list = get(contacts);
-      let i = list.findIndex((contact) => contact.address === address);
-      if (i >= 0) {
-        return list[i].name;
-      } else {
-        return false;
-      }
-    },
-  };
-}
-
-// We export `contacts` as the variable that can be used to interact with the contacts store.
-export const contacts = createContactsStore();
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stores/contactsStore.js
-
-### Usando el `contacts` store
-
-#### En la página `/dashboard/contacts`
-
-También tenemos una página dedicada a gestionar contactos. La página `/dashboard/contacts` permitirá al usuario recopilar y gestionar una lista de entradas de contacto que almacena el nombre del contacto y la dirección Stellar. El contacto también puede ser marcado o desmarcado como un contacto "favorito" que se mostrará en la página principal `/dashboard`.
-
-```html title="/src/routes/dashboard/contacts/+page.svelte"
-<script>
-  // We import things from external packages that will be needed
-  import { Trash2Icon, UserPlusIcon } from "svelte-feather-icons";
-
-  // We import any Svelte components we will need
-  import TruncatedKey from "$lib/components/TruncatedKey.svelte";
-
-  // We import any stores we will need to read and/or write
-  // highlight-next-line
-  import { contacts } from "$lib/stores/contactsStore";
-
-  // We declare a _reactive_ component variable that will hold information for
-  // a user-created contact entry, which can be added to the contacts store.
-  $: newContact = {
-    name: "",
-    address: "",
-    favorite: false,
-    id: "",
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/contacts/+page.svelte
-
-#### En la página `/dashboard`
-
-El `contacts` store ahora se exporta desde este archivo y puede ser accedido y utilizado dentro de una página o componente de Svelte. Aquí tienes cómo hemos implementado un componente de "contactos favoritos" para mostrarlo en el panel principal de BasicPay.
-
-```html title="/src/routes/dashboard/components/FavoriteContacts.svelte"
-<script>
-  // We import the `contacts` store into our Svelte component
-  // highlight-next-line
-  import { contacts } from "$lib/stores/contactsStore";
-  import TruncatedKey from "$lib/components/TruncatedKey.svelte";
-
-  // `$:` makes a Svelte variable reactive, so it will be re-computed any time
-  // the `$contacts` store is modified. We access a Svelte store by adding `$`
-  // to the beginning of the variable name.
-  // highlight-next-line
-  $: favoriteContacts = $contacts?.filter((contact) => contact.favorite);
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/components/FavoriteContacts.svelte
-
-[paquete `svelt-local-storage-store`]: https://github.com/joshnuss/svelte-local-storage-store
-[repositorio de código fuente]: https://github.com/stellar/basic-payment-app
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/manage-trust.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/manage-trust.mdx
deleted file mode 100644
index 2a051d213b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/manage-trust.mdx
+++ /dev/null
@@ -1,255 +0,0 @@
----
-title: Gestionar Confianza
-sidebar_position: 30
----
-
-Para que una cuenta mantenga y negocie activos distintos de XLM, debe establecer una [trustline](../../../learn/fundamentals/stellar-data-structures/accounts.mdx#trustlines) con la cuenta emisora de ese activo en particular. Each trustline increases the account’s [base reserve](../../../learn/fundamentals/stellar-data-structures/accounts.mdx#base-reserves-and-subentries) by 0.5 XLM, which means the account will have to hold more XLM in its minimum balance.
-
-## Experiencia del usuario
-
-Primero, haremos que el usuario cree una trustline para un activo navegando a la página de Activos, seleccionando un activo y haciendo clic en el botón “Añadir Activo”.
-
-:::info
-
-Un activo se muestra como un código de activo y la dirección del emisor. Aprende más en nuestra [sección de Activos](../../../learn/fundamentals/stellar-data-structures/assets.mdx).
-
-:::
-
-![agregar-activos](/assets/basic-pay/add-assets.png)
-
-This triggers a modal form for the user to confirm the transaction with their pincode. Una vez confirmado, se firma una transacción que contiene la operación `changeTrust` y se envía a la red, y se establece una trustline entre la cuenta del usuario y la cuenta emisora para el activo.
-
-La operación `changeTrust` también se puede utilizar para modificar o eliminar trustlines.
-
-:::info
-
-Cada transacción debe contener un número de secuencia que se utiliza para identificar y verificar el orden de las transacciones con la cuenta. El número de secuencia de una transacción debe aumentar siempre en uno. En BasicPay, la obtención e incremento del número de secuencia se manejan automáticamente por el generador de transacciones.
-
-:::
-
-Las trustlines mantienen los saldos de todos sus activos asociados (excepto XLM, que se mantienen a nivel de cuenta), y puedes mostrar los diversos saldos del usuario en tu aplicación.
-
-![mostrar activos](/assets/basic-pay/display-assets.png)
-
-Velo en acción aquí: https://basicpay.pages.dev/dashboard/assets
-
-## Implementación de código
-
-Las trustlines que una cuenta mantiene serán necesarias para visualizarse en varias partes de la aplicación BasicPay. Primero, discutiremos cómo gestionamos diferentes trustlines para la cuenta.
-
-### La página `/dashboard/assets`
-
-La página `/dashboard/assets` permite al usuario gestionar los activos Stellar a los que su cuenta tiene trustlines. En esta página, pueden elegir entre varias opciones de activos pre-sugeridos o altamente valorados, o pueden especificar su propio activo para confiar utilizando un código de activo y una clave pública del emisor. También pueden eliminar trustlines que ya existen en su cuenta.
-
-El diseño de la página es bastante similar a nuestra página de contactos. Tiene una tabla que muestra las trustlines existentes y una sección donde puedes añadir nuevas. La diferencia clave es que el almacenamiento de `contacts` se mantiene en `localStorage` del navegador, mientras que los saldos de una cuenta se mantienen en la blockchain. Por lo tanto, consultaremos la red para obtener esa información. Para más información sobre cómo consultamos esta información de la red Stellar, revisa la función `fetchAccountBalances()` en [esta sección de consultas de datos].
-
-```html title="/src/routes/dashboard/assets/+page.svelte"
-<script>
-  // `export let data` allows us to pull in any parent load data for use here.
-  /** @type {import('./$types').PageData} */
-  export let data;
-
-  // This is where our _reactive_ array of balances is declared. The query
-  // actually takes place in `/src/routes/dashboard/+layout.js`, and is
-  // inherited here.
-  $: balances = data.balances ?? [];
-
-  // We import things from external packages that will be needed
-  import { Trash2Icon } from "svelte-feather-icons";
-
-  // We import any Svelte components we will need
-  import ConfirmationModal from "$lib/components/ConfirmationModal.svelte";
-  import TruncatedKey from "$lib/components/TruncatedKey.svelte";
-
-  // We import any stores we will need to read and/or write
-  import { walletStore } from "$lib/stores/walletStore";
-  import { invalidateAll } from "$app/navigation";
-
-  // We import some of our `$lib` functions
-  import { createChangeTrustTransaction } from "$lib/stellar/transactions";
-  import { fetchAssets } from "$lib/utils/stellarExpert";
-
-  // We import the Server and API types from @stellar/stellar-sdk/rpc for transaction submission
-  import { Server, Api } from "@stellar/stellar-sdk/rpc";
-  import { xdr } from "@stellar/stellar-sdk";
-  import { decode } from "@stellar/stellar-xdr-json";
-  import { error } from "@sveltejs/kit";
-
-  // The `open` Svelte context is used to open the confirmation modal
-  import { getContext } from "svelte";
-  const { open } = getContext("simple-modal");
-
-  // RPC server configuration for transaction submission
-  const rpcUrl = "https://soroban-testnet.stellar.org";
-  const server = new Server(rpcUrl);
-
-  // Local submit function to send transactions using RPC
-  const submit = async (transaction) => {
-    try {
-      // Send the transaction and get initial response
-      const sendTransactionResponse = await server.sendTransaction(transaction);
-
-      // Check if transaction was accepted for processing
-      if (sendTransactionResponse.status !== "PENDING") {
-        throw new Error(
-          `Failed to send transaction, status: ${sendTransactionResponse.status}`,
-        );
-      }
-
-      // Poll for the final transaction status
-      const finalResponse = await server.pollTransaction(
-        sendTransactionResponse.hash,
-      );
-
-      // Handle the final transaction status
-      switch (finalResponse.status) {
-        case Api.GetTransactionStatus.FAILED:
-          // Include decoded resultXdr for failed transactions
-          let errorDetails = `Transaction failed with status: ${finalResponse.status}`;
-          if (finalResponse.resultXdr) {
-            errorDetails += `\nResult XDR: ${finalResponse.resultXdr.toXDR("base64")}`;
-          }
-          throw new Error(errorDetails);
-        case Api.GetTransactionStatus.NOT_FOUND:
-          throw new Error(
-            `Transaction was not included in the ledger. Status: ${finalResponse.status}`,
-          );
-        case Api.GetTransactionStatus.SUCCESS:
-          return finalResponse;
-        default:
-          throw new Error(
-            `Unexpected transaction status: ${finalResponse.status}`,
-          );
-      }
-    } catch (err) {
-      throw error(400, {
-        message: err.message || `Transaction failed: ${err}`,
-      });
-    }
-  };
-
-  // Define some component variables that will be used throughout the page
-  let addAsset = "";
-  let customAssetCode = "";
-  let customAssetIssuer = "";
-  let changeTrustXDR = "";
-  let changeTrustNetwork = "";
-  $: asset =
-    addAsset !== "custom"
-      ? addAsset
-      : `${customAssetCode}:${customAssetIssuer}`;
-
-  // Takes an action after the pincode has been confirmed by the user.
-  const onConfirm = async (pincode) => {
-    // Use the walletStore to sign the transaction
-    let signedTransaction = await walletStore.sign({
-      transactionXDR: changeTrustXDR,
-      network: changeTrustNetwork,
-      pincode: pincode,
-    });
-    // Submit the transaction to the Stellar network
-    await submit(signedTransaction);
-    // `invalidateAll` will tell SvelteKit that it should re-run any `load`
-    // functions. Since we have a new (or newly deleted) trustline, this
-    // results in re-querying the network to get updated account balances.
-    invalidateAll();
-  };
-
-  // Builds and presents to the user for confirmation a Stellar transaction that
-  // will add/modify/remove a trustline on their account. This function is
-  // called when the user clicks the "add" or "delete" trustline buttons.
-  const previewChangeTrustTransaction = async (
-    addingAsset = true,
-    removeAsset = undefined,
-  ) => {
-    // Generate the transaction, expecting back the XDR string
-    let { transaction, network_passphrase } =
-      await createChangeTrustTransaction({
-        source: data.publicKey,
-        asset: removeAsset ?? asset,
-        limit: addingAsset ? undefined : "0",
-      });
-
-    // Set the component variables to hold the transaction details
-    changeTrustXDR = transaction;
-    changeTrustNetwork = network_passphrase;
-
-    // Open the confirmation modal for the user to confirm or reject the
-    // transaction. We provide our customized `onConfirm` function, but we
-    // have no need to customize and pass an `onReject` function.
-    open(ConfirmationModal, {
-      transactionXDR: changeTrustXDR,
-      transactionNetwork: changeTrustNetwork,
-      onConfirm: onConfirm,
-    });
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/assets/+page.svelte
-
-### La función `createChangeTrustTransaction`
-
-En la página anterior, hemos hecho uso de la función `createChangeTrustTransaction`. Esta función se puede usar para añadir, eliminar o modificar trustlines en una cuenta Stellar.
-
-```js title="/src/lib/stellar/transactions.js"
-import {
-  TransactionBuilder,
-  Networks,
-  Operation,
-  Asset,
-} from "@stellar/stellar-sdk";
-import { Server } from "@stellar/stellar-sdk/rpc";
-import { error } from "@sveltejs/kit";
-
-// We are setting a very high maximum fee, which increases our transaction's
-// chance of being included in the ledger. We're making this a `const` so we can
-// change it on one place as and when recommendations and/or best practices
-// evolve. Current recommended fee is `100_000` stroops.
-const maxFeePerOperation = "100000";
-const rpcUrl = "https://soroban-testnet.stellar.org";
-const networkPassphrase = Networks.TESTNET;
-const standardTimebounds = 300; // 5 minutes for the user to review/sign/submit
-
-// Constructs and returns a Stellar transaction that will create or modify a
-// trustline on an account.
-export async function createChangeTrustTransaction({ source, asset, limit }) {
-  // We start by converting the asset provided in string format into a Stellar
-  // Asset() object
-  let trustAsset = new Asset(asset.split(":")[0], asset.split(":")[1]);
-
-  // Next, we setup our transaction by loading the source account from the
-  // network using RPC, and initializing the TransactionBuilder.
-  let server = new Server(rpcUrl);
-  let sourceAccount = await server.getAccount(source);
-
-  // Chaning everything together from the `transaction` declaration means we
-  // don't have to assign anything to `builtTransaction` later on. Either
-  // method will have the same results.
-  let transaction = new TransactionBuilder(sourceAccount, {
-    networkPassphrase: networkPassphrase,
-    fee: maxFeePerOperation,
-  })
-    // Add a single `changeTrust` operation (this controls whether we are
-    // adding, removing, or modifying the account's trustline)
-    .addOperation(
-      Operation.changeTrust({
-        asset: trustAsset,
-        limit: limit?.toString(),
-      }),
-    )
-    // Before the transaction can be signed, it requires timebounds
-    .setTimeout(standardTimebounds)
-    // It also must be "built"
-    .build();
-
-  return {
-    transaction: transaction.toXDR(),
-    network_passphrase: networkPassphrase,
-  };
-}
-```
-
-[esta sección de consultas de datos]: ./querying-data.mdx#fetchaccountbalances
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/overview.mdx
deleted file mode 100644
index dc5238bd67..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/overview.mdx
+++ /dev/null
@@ -1,270 +0,0 @@
----
-title: Resumen
-sidebar_position: 10
----
-
-:::note
-
-Este tutorial describe cómo crear una aplicación con el [`js-stellar-sdk`], para construir con el Wallet SDK, por favor sigue el [tutorial de creación de una billetera](../wallet/overview.mdx). Para construir con contratos inteligentes, navega a la [sección de Contratos Inteligentes](../../../build/smart-contracts/getting-started/setup.mdx).
-
-:::
-
-En este tutorial, revisaremos los pasos necesarios para crear una aplicación de pagos básica en la Testnet de Stellar. Después de este tutorial, deberías tener una buena comprensión de los conceptos fundamentales de Stellar y una base sólida para el desarrollo iterativo.
-
-Para este tutorial, revisaremos los pasos mientras creamos una aplicación de ejemplo que hemos llamado [BasicPay], que se utilizará para mostrar diversas características.
-
-:::caution
-
-Aunque BasicPay es una aplicación completa en la Testnet de Stellar, ha sido creada únicamente para mostrar la funcionalidad de Stellar con fines educativos en este tutorial, no para ser copiada, pegada y utilizada en Mainnet.
-
-:::
-
-## Configuración del proyecto
-
-### Requisitos del proyecto
-
-Para crear una aplicación básica de Stellar, necesitarás:
-
-- Marco de aplicación: estamos utilizando [SvelteKit] optando por JavaScript con tipado JSDoc. SvelteKit es bastante flexible y podría usarse para mucho, pero principalmente lo utilizamos por sus capacidades de enrutamiento para minimizar que esto se convierta en un "tutorial de SvelteKit".
-- Marco de frontend: estamos utilizando [DaisyUI] para simplificar el uso de [Tailwind CSS].
-- Una manera de interactuar con la red Stellar: estamos utilizando el [`js-stellar-sdk`], pero podrías utilizar solicitudes fetch tradicionales. El [`js-stellar-sdk`] también se utiliza para construir transacciones que se envían a la red Stellar.
-- Una manera de interactuar con el keypair del usuario: estamos utilizando el SDK [`js-stellar-wallets`], pero puedes optar por usar una billetera existente.
-
-:::note
-
-Mientras usamos los componentes anteriores para construir nuestra aplicación, hemos hecho nuestro mejor esfuerzo para redactar este tutorial de tal manera que la dependencia de cualquiera de estas cosas se minimice. Preferiblemente, deberías poder usar el código JavaScript que hemos escrito e integrarlo en cualquier otro marco que desees con un esfuerzo mínimo.
-
-:::
-
-Hemos tomado las siguientes decisiones durante el desarrollo de BasicPay que también deberías considerar a medida que sigues el tutorial:
-
-- Hemos diseñado esta aplicación para escritorio. En su mayor parte, la aplicación es receptiva a varios tamaños de pantalla, pero hemos _elegido_ no hacer un esfuerzo especial para priorizar la experiencia del usuario móvil.
-- Hemos habilitado los temas predeterminados de DaisyUI "claro" y "oscuro", que deberían cambiar con las preferencias de tu dispositivo. Sin embargo, no hay un interruptor de conmutación habilitado.
-- Esto está escrito como una aplicación del lado del cliente. No se llevan a cabo acciones del lado del servidor. Si estás construyendo una aplicación con un backend y un frontend, deberás considerar cuidadosamente qué información vive dónde, especialmente cuando está involucrada la clave secreta de un usuario.
-- Estamos desplegando esto como una "aplicación de una sola página" estática con [Cloudflare Pages]. Tus propias decisiones de despliegue tendrán un impacto en tu configuración y proceso de construcción.
-- Es probable que la aplicación no sea tan eficiente como podría ser. Tampoco está tan optimizada como podría estarlo. Hemos intentado encapsular las diversas funcionalidades de una manera que tenga sentido para el desarrollador que lee la base de código, por lo que hay algo de duplicación de código y las cosas _podrían_ hacerse de una manera "mejor".
-- Hacemos _alguna_ gestión de errores, pero no tanto como desearías para una aplicación del mundo real. Si algo parece no funcionar, y no ves un error, abre la consola de desarrollador, y podrías ser capaz de averiguar qué ha salido mal.
-- No hemos implementado _ninguna_ prueba automatizada. Probablemente querrás algunas para tu aplicación.
-
-:::note
-
-Este tutorial probablemente se vea mejor como "_casi_ completo." No vamos a guiarte a través de cada uno de los archivos en nuestra base de código, y los archivos que utilizamos para ilustrar conceptos en el tutorial pueden no estar _totalmente_ presentes o explicados. Sin embargo, cubriremos los conceptos básicos, y te señalaremos ejemplos más completos en la base de código cuando sea aplicable.
-
-:::
-
-### Ayudantes de desarrollo
-
-- [Stellar Lab]: un parque experimental para interactuar con la red Stellar
-- Friendbot: un bot que financia cuentas con 10.000 XLM falsos en la Testnet de Stellar; puedes financiar tu cuenta accediendo a `https://friendbot.stellar.org/?addr=G...`
-- [Archivo toml de Testnet]: un ejemplo de archivo `stellar.toml` que demuestra qué información podría publicar un anchor
-- [Ayudantes de desarrollo de BasicPay]: si estás _usando_ la aplicación BasicPay, hemos creado algunas herramientas útiles para ayudarte a explorar su funcionalidad
-
-## Comenzar
-
-Aquí están los pasos que hemos seguido para comenzar a construir BasicPay. Siéntete libre de inspirarte y personalizar estas direcciones según lo consideres adecuado. Toda la [base de código de BasicPay] está abierta y disponible en GitHub para referencia.
-
-:::note
-
-Esta parte del tutorial requerirá una buena dosis de "tu experiencia puede variar." Esbozaremos los pasos que hemos tomado para nuestra situación de despliegue, pero querrás revisar qué opciones son necesarias para tu(s) entorno(s).
-
-:::
-
-### Instalar marcos
-
-Lo primero que necesitaremos hacer es crear una aplicación SvelteKit, utilizando `npm`, estamos usando la v18.x de nodejs.
-
-```bash
-npm create svelte@latest my-basic-payment-app
-```
-
-Esto te guiará a través del proceso de creación de SvelteKit, preguntándote sobre las diversas opciones. Hemos elegido las siguientes opciones:
-
-- **¿Qué plantilla de aplicación Svelte?** Proyecto esqueleto
-- **¿Estás verificando tipos con TypeScript?** Sí, usando JavaScript con comentarios JSDoc
-- **Seleccionar opciones adicionales** Agregar ESLint para el análisis de código; Agregar Prettier para el formateo de código
-
-Después de este proceso, la estructura de tu aplicación vivirá dentro del directorio `my-basic-payment-app`. Puedes `cd` a ese directorio y agregar algunas dependencias de UI.
-
-```bash npm2yarn
-cd my-basic-payment-app
-npm install --save-dev svelte-preprocess tailwindcss autoprefixer postcss @sveltejs/adapter-static \
-    @tailwindcss/typography \
-    daisyui svelte-feather-icons
-```
-
-Antes de configurar cualquier cosa, necesitaremos generar nuestros archivos `tailwind.config.js` y `postcss.config.js`.
-
-```bash
-npx tailwindcss init -p
-```
-
-Ahora, necesitaremos un poco de configuración para hacer que todos esos componentes funcionen juntos. Primero, modifica tu archivo `svelte.config.js`:
-
-```js title="/svelte.config.js"
-// highlight-start
-import preprocess from "svelte-preprocess";
-import adapter from "@sveltejs/adapter-static";
-// highlight-end
-
-/** @type {import('@sveltejs/kit').Config} */
-const config = {
-  kit: {
-    // Note: Your `adapter` configuration may need customizations depending
-    // on how you are building and deploying your application.
-    // highlight-start
-    adapter: adapter({
-      fallback: "index.html",
-    }),
-    // highlight-end
-  },
-  // highlight-start
-  preprocess: [
-    preprocess({
-      postcss: true,
-    }),
-  ],
-  // highlight-end
-};
-
-export default config;
-```
-
-A continuación, puedes configurar el archivo `tailwind.config.js`.
-
-1. Importa los plugins `daisyui` y `typography`
-2. Configura nuestras rutas de contenido (puedes necesitar modificar estos valores dependiendo de la estructura de tu proyecto)
-3. Agrega el plugin `daisyui` **después** de cualquier plugin oficialmente de `@tailwindcss` (solo `typography` en nuestro ejemplo)
-
-```js title="/tailwind.config.js"
-// highlight-start
-const daisyui = require("daisyui");
-const typography = require("@tailwindcss/typography");
-// highlight-end
-
-/** @type {import('tailwindcss').Config} */
-export default {
-  content: [
-    // highlight-start
-    "./src/routes/**/*.{html,js,svelte,ts}",
-    "./src/routes/**/**/*.{html,js,svelte,ts}",
-    "./src/lib/components/**/*.{html,js,svelte,ts}",
-    // highlight-end
-  ],
-  // highlight-next-line
-  plugins: [typography, daisyui],
-};
-```
-
-Agrega tus directivas tailwind a tu archivo CSS principal de la aplicación.
-
-```css title="/src/app.postcss"
-@tailwind base;
-@tailwind components;
-@tailwind utilities;
-```
-
-Luego importa el archivo CSS en tu diseño base de SvelteKit (puedes necesitar crear este archivo).
-
-```html title="/src/routes/+layout.svelte"
-<script>
-  import "../app.postcss";
-</script>
-
-<slot />
-```
-
-También creamos un archivo `/src/routes/+layout.js` para configurar nuestra aplicación como _solo_ del lado del cliente. Esto significa que la aplicación se entregará al cliente como HTML y JavaScript no procesado.
-
-```js title="/src/routes/+layout.js"
-// Disable pre-rendering of pages during build-time
-export const prerender = false;
-// Disable server-side rendering
-export const ssr = false;
-```
-
-¡Tu proyecto de SvelteKit ya está configurado y listo para ejecutarse!
-
-```bash npm2yarn
-npm run dev
-```
-
-### Dependencias de Stellar
-
-Para trabajar con la red Stellar, estructuras de datos y keypairs almacenados localmente, vamos a instalar y configurar algunas dependencias más.
-
-```bash npm2yarn
-# Stellar SDKs
-npm install --save-dev stellar-sdk @stellar/wallet-sdk
-# We will need some polyfills to make things available client-side
-npm install --save-dev @esbuild-plugins/node-globals-polyfill @esbuild-plugins/node-modules-polyfill \
-    path @rollup/plugin-inject buffer svelte-local-storage-store uuid
-```
-
-Usaremos un archivo `window.js` para inyectar Buffer en nuestro código del lado del cliente, ya que eso es necesario para algunas partes del `stellar-sdk`.
-
-```js title="/src/lib/window.js"
-import { browser } from "$app/environment";
-import { Buffer } from "buffer";
-
-if (browser) {
-  window.Buffer = Buffer;
-} else {
-  globalThis.Buffer = Buffer;
-  globalThis.window = {};
-}
-export default globalThis;
-```
-
-La "inyección" real tiene lugar en nuestro archivo `vite.config.js`.
-
-```js title="/vite.config.js"
-import { sveltekit } from "@sveltejs/kit/vite";
-import { defineConfig } from "vite";
-import { NodeGlobalsPolyfillPlugin } from "@esbuild-plugins/node-globals-polyfill";
-import inject from "@rollup/plugin-inject";
-import path from "path";
-
-export default defineConfig({
-  plugins: [sveltekit()],
-  optimizeDeps: {
-    esbuildOptions: {
-      define: {
-        global: "globalThis",
-      },
-      plugins: [
-        NodeGlobalsPolyfillPlugin({
-          buffer: true,
-        }),
-      ],
-    },
-  },
-  build: {
-    rollupOptions: {
-      plugins: [
-        inject({
-          window: path.resolve("src/lib/window.js"),
-        }),
-      ],
-    },
-  },
-  ssr: {
-    noExternal: ["@stellar/wallet-sdk", "@albedo-link/intent"],
-  },
-});
-```
-
-¡Eso debería encargarse de todo lo que necesitas! Si has seguido estos pasos, ahora tienes una aplicación que se ejecuta solo del lado del cliente que está lista para crear una aplicación que interactúe con la red Stellar! ¡Buen trabajo!
-
-A continuación, veremos cómo registramos a un usuario y creamos su cuenta en la red Stellar.
-
-[basicpay]: https://basicpay.pages.dev
-[sveltekit]: https://kit.svelte.dev
-[daisyui]: https://daisyui.com
-[tailwind css]: https://tailwindcss.com
-[`js-stellar-sdk`]: https://github.com/stellar/js-stellar-sdk
-[`js-stellar-wallets` sdk]: https://github.com/stellar/js-stellar-wallets
-[cloudflare pages]: https://pages.cloudflare.com/
-[stellar lab]: https://lab.stellar.org
-[testnet toml file]: https://testanchor.stellar.org/.well-known/stellar.toml
-[basicpay codebase]: https://github.com/stellar/basic-payment-app
-[basicpay dev helpers]: https://basicpay.pages.dev/dashboard/settings/dev
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/path-payment.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/path-payment.mdx
deleted file mode 100644
index 95e07f6007..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/path-payment.mdx
+++ /dev/null
@@ -1,290 +0,0 @@
----
-title: Pago por ruta
-sidebar_position: 50
----
-
-Un pago por ruta es donde el activo enviado puede ser diferente del activo recibido. Hay dos operaciones posibles de pago por ruta: 1) `path_payment_strict_send`, que permite al usuario especificar la cantidad del activo a enviar, y 2) `path_payment_strict_receive`, que permite al usuario especificar la cantidad del activo recibido. Lee más en la [Guía de Pagos por Rutas](../../../build/guides/transactions/path-payments.mdx).
-
-## Experiencia del usuario
-
-Con BasicPay, el usuario envía un pago por ruta navegando a la página de Pagos, donde puede seleccionar a un usuario de sus contactos o ingresar la clave pública de una dirección de destino. Luego selecciona el interruptor Enviar y Recibir Activos Diferentes y determina si quiere especificar el activo enviado o recibido. Finalmente selecciona el activo enviado y el activo recibido y las cantidades y selecciona el botón Vista Previa de Transacción.
-
-![ruta de pago](/assets/basic-pay/path-payment.png)
-
-The user will then preview the transaction, input their pincode, and select the Confirm button to sign and submit the transaction to the network.
-
-## Implementación del código
-
-### La página `/dashboard/send`
-
-La mayoría de esta página se ha discutido en la [sección de Pagos](./payment.mdx#the-dashboardsend-page). A continuación, estamos destacando las piezas únicas que se agregan a BasicPay para permitir la función de pago por ruta.
-
-```html title="/src/routes/dashboard/send/+page.svelte"
-<script>
-  // We import some of our `$lib` functions
-  import {
-    fetchAccount,
-    submit,
-    fetchAccountBalances,
-    // highlight-start
-    findStrictSendPaths,
-    findStrictReceivePaths,
-    // highlight-end
-  } from "$lib/stellar/horizonQueries";
-  import {
-    createCreateAccountTransaction,
-    // highlight-start
-    createPathPaymentStrictReceiveTransaction,
-    createPathPaymentStrictSendTransaction,
-    // highlight-end
-    createPaymentTransaction,
-  } from "$lib/stellar/transactions";
-
-  /* ... */
-
-  // Define some component variables that will be used throughout the page
-  let destination = "";
-  $: otherDestination = destination === "other";
-  let otherPublicKey = "";
-  let sendAsset = "native";
-  let sendAmount = "";
-  let receiveAsset = "";
-  let receiveAmount = "";
-  let memo = "";
-  let createAccount = null;
-  // highlight-start
-  let pathPayment = false;
-  let availablePaths = [];
-  let strictReceive = false;
-  // highlight-end
-  let paymentXDR = "";
-  let paymentNetwork = "";
-
-  /* ... */
-
-  // Query Horizon for available paths between a combination of source and destination assets and accounts.
-  const findPaths = async () => {
-    // Query the paths from Horizon
-    let paths = strictReceive
-      ? await findStrictReceivePaths({
-          sourcePublicKey: data.publicKey,
-          destinationAsset: receiveAsset,
-          destinationAmount: receiveAmount,
-        })
-      : await findStrictSendPaths({
-          sourceAsset: sendAsset,
-          sourceAmount: sendAmount,
-          destinationPublicKey: otherDestination ? otherPublicKey : destination,
-        });
-    // Fill the component variable `availablPaths` with our returned paths
-    availablePaths = paths;
-    // If both send and receive assets have been selected re-select the path
-    // to update the relevant amount
-    if (receiveAsset && sendAsset) {
-      selectPath();
-    }
-  };
-
-  // Select a path for use in the path payment operation, and set the component variables accordingly.
-  const selectPath = () => {
-    if (strictReceive) {
-      // Set the `sendAmount` variable to the chosen path amount. The
-      // filtering we do checks if the asset_type matches because that
-      // will give us our 'native' XLM asset, otherwise we match on the
-      // asset_code.
-      sendAmount = availablePaths.filter(
-        (path) =>
-          path.source_asset_type === sendAsset ||
-          sendAsset.startsWith(path.source_asset_code),
-      )[0].source_amount;
-    } else {
-      // Set the `receiveAmount` variable to the chosen path amount. The
-      // filtering we do checks if the asset_type matches because that
-      // will give us our 'native' XLM asset, otherwise we match on the
-      // asset_code.
-      receiveAmount = availablePaths.filter(
-        (path) =>
-          path.destination_asset_type === receiveAsset ||
-          receiveAsset.startsWith(path.destination_asset_code),
-      )[0].destination_amount;
-    }
-  };
-
-  /* ... */
-
-  // Create a payment transaction depending on user selections, and present it to the user for approval or rejection.
-  const previewPaymentTransaction = async () => {
-    let transaction, network_passphrase
-    if (createAccount) {
-      { transaction, network_passphrase } = await createCreateAccountTransaction({
-        /* ... */
-      })
-    // highlight-start
-    } else if (pathPayment && strictReceive) {
-      { transaction, network_passphrase } = await createPathPaymentStrictReceiveTransaction({
-        source: data.publicKey,
-        sourceAsset: sendAsset,
-        sourceAmount: sendAmount,
-        destination: otherDestination ? otherPublicKey : destination,
-        destinationAsset: receiveAsset,
-        destinationAmount: receiveAmount,
-        memo: memo,
-      })
-    } else if (pathPayment && !strictReceive) {
-      { transaction, network_passphrase } = await createPathPaymentStrictSendTransaction({
-        source: data.publicKey,
-        sourceAsset: sendAsset,
-        sourceAmount: sendAmount,
-        destination: otherDestination ? otherPublicKey : destination,
-        destinationAsset: receiveAsset,
-        destinationAmount: receiveAmount,
-        memo: memo,
-      })
-    // highlight-end
-    } else {
-      { transaction, network_passphrase } = await createPaymentTransaction({
-        /* ... */
-      });
-    }
-
-    /* ... */
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/send/+page.svelte
-
-### Las funciones de transacción
-
-En la sección anterior, usamos las funciones `createPathPaymentStrictReceiveTransaction` y `createPathPaymentStrictSendTransaction`. Estas se utilizan para crear transacciones que contienen la operación real de pago por ruta.
-
-```js title="/src/lib/stellar/transactions.js"
-// Constructs and returns a Stellar transaction that will contain a path payment strict send operation to send/receive different assets.
-export async function createPathPaymentStrictSendTransaction({
-  source,
-  sourceAsset,
-  sourceAmount,
-  destination,
-  destinationAsset,
-  destinationAmount,
-  memo,
-}) {
-  // First, we setup our transaction by loading the source account from the
-  // network, and initializing the TransactionBuilder. This is the first step
-  // in constructing all Stellar transactions.
-  let server = new Server(horizonUrl);
-  let sourceAccount = await server.loadAccount(source);
-  let transaction = new TransactionBuilder(sourceAccount, {
-    networkPassphrase: networkPassphrase,
-    fee: maxFeePerOperation,
-  });
-
-  // We work out the assets to be sent by the source account and received by
-  // the destination account
-  let sendAsset =
-    sourceAsset === "native"
-      ? Asset.native()
-      : new Asset(sourceAsset.split(":")[0], sourceAsset.split(":")[1]);
-  let destAsset =
-    destinationAsset === "native"
-      ? Asset.native()
-      : new Asset(
-          destinationAsset.split(":")[0],
-          destinationAsset.split(":")[1],
-        );
-
-  // We will calculate an acceptable 2% slippage here for... reasons?
-  let destMin = ((98 * parseFloat(destinationAmount)) / 100).toFixed(7);
-
-  // If a memo was supplied, add it to the transaction
-  if (memo) {
-    transaction.addMemo(Memo.text(memo));
-  }
-
-  // Add a single `pathPaymentStrictSend` operation
-  transaction.addOperation(
-    Operation.pathPaymentStrictSend({
-      sendAsset: sendAsset,
-      sendAmount: sourceAmount.toString(),
-      destination: destination,
-      destAsset: destAsset,
-      destMin: destMin,
-    }),
-  );
-
-  // Before the transaction can be signed, it requires timebounds, and it must
-  // be "built"
-  let builtTransaction = transaction.setTimeout(standardTimebounds).build();
-  return {
-    transaction: builtTransaction.toXDR(),
-    network_passphrase: networkPassphrase,
-  };
-}
-
-// Constructs and returns a Stellar transaction that will contain a path payment strict receive operation to send/receive different assets.
-export async function createPathPaymentStrictReceiveTransaction({
-  source,
-  sourceAsset,
-  sourceAmount,
-  destination,
-  destinationAsset,
-  destinationAmount,
-  memo,
-}) {
-  // First, we setup our transaction by loading the source account from the
-  // network, and initializing the TransactionBuilder. This is the first step
-  // in constructing all Stellar transactions.
-  let server = new Server(horizonUrl);
-  let sourceAccount = await server.loadAccount(source);
-  let transaction = new TransactionBuilder(sourceAccount, {
-    networkPassphrase: networkPassphrase,
-    fee: maxFeePerOperation,
-  });
-
-  // We work out the assets to be sent by the source account and received by
-  // the destination account
-  let sendAsset =
-    sourceAsset === "native"
-      ? Asset.native()
-      : new Asset(sourceAsset.split(":")[0], sourceAsset.split(":")[1]);
-  let destAsset =
-    destinationAsset === "native"
-      ? Asset.native()
-      : new Asset(
-          destinationAsset.split(":")[0],
-          destinationAsset.split(":")[1],
-        );
-
-  /** @todo Figure out a good number to use for slippage. And why! And how to calculate it?? */
-  // We will calculate an acceptable 2% slippage here for... reasons?
-  let sendMax = ((100 * parseFloat(sourceAmount)) / 98).toFixed(7);
-
-  // If a memo was supplied, add it to the transaction
-  if (memo) {
-    transaction.addMemo(Memo.text(memo));
-  }
-
-  // Add a single `pathPaymentStrictSend` operation
-  transaction.addOperation(
-    Operation.pathPaymentStrictReceive({
-      sendAsset: sendAsset,
-      sendMax: sendMax,
-      destination: destination,
-      destAsset: destAsset,
-      destAmount: destinationAmount,
-    }),
-  );
-
-  // Before the transaction can be signed, it requires timebounds, and it must
-  // be "built"
-  let builtTransaction = transaction.setTimeout(standardTimebounds).build();
-  return {
-    transaction: builtTransaction.toXDR(),
-    network_passphrase: networkPassphrase,
-  };
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/transactions.js
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/payment.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/payment.mdx
deleted file mode 100644
index 227a54af08..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/payment.mdx
+++ /dev/null
@@ -1,290 +0,0 @@
----
-title: Pago
-sidebar_position: 40
----
-
-Una operación de pago envía una cantidad en un activo específico (XLM o no-XLM) a una cuenta de destino. Con una operación de pago básica, el activo enviado es el mismo que el activo recibido. BasicPay también permite pagos por ruta (donde el activo enviado es diferente al activo recibido), de los que hablaremos en la siguiente sección.
-
-## Experiencia del usuario
-
-En nuestra aplicación BasicPay, el usuario navegará a la página de Pagos donde podrá seleccionar a un usuario de sus contactos o ingresar la clave pública de una dirección de destino con un activo específico que desea enviar junto con la cantidad del activo.
-
-![pago](/assets/basic-pay/payment.png)
-
-El usuario hace clic en el botón "Confirmar transacción". Si la cuenta de destino existe y está debidamente financiada con XLM, esto desencadenará una Vista previa de la transacción donde podrá ver los detalles de la transacción.
-
-Todas las transacciones Stellar requieren una pequeña tarifa para llegar al ledger. Lee más en nuestra [sección de tarifas](../../../learn/fundamentals/fees-resource-limits-metering.mdx).
-
-In BasicPay, we’ve set it up so that the user always pays a static fee of 100,000 [stroops](../../../learn/fundamentals/stellar-data-structures/assets.mdx#amount-precision) (one stroop equals 0.0000001 XLM) per operation. Alternativamente, puedes agregar una función a tu aplicación que permita al usuario establecer su propia tarifa.
-
-![pago](/assets/basic-pay/fees.png)
-
-The user then inputs their pincode and clicks the "Confirm" button, which signs and submits the transaction to the ledger.
-
-## Implementación de código
-
-### La página `/dashboard/send`
-
-La página `/dashboard/send` permite al usuario enviar pagos a otras direcciones Stellar. Pueden seleccionar de un menú desplegable que contiene los nombres de su lista de contactos, o pueden ingresar su propia clave pública "Otro...".
-
-Se han implementado las siguientes características adicionales:
-
-- Si la dirección de destino no es una cuenta financiada, se informa al usuario que utilizará una operación de `createAccount` y debe enviar al menos 1 XLM para financiar la cuenta.
-- El usuario puede seleccionar enviar/recibir diferentes activos y las rutas se consultan desde Horizon dependiendo de los cuatro puntos siguientes:
-  1. Si desea enviar estrictamente o recibir estrictamente,
-  2. Los activos de origen/destino que ha seleccionado,
-  3. Las cuentas de origen/destino, y
-  4. La cantidad ingresada para el valor de enviar/recibir.
-- Un campo de memo opcional está disponible para memos de solo texto.
-
-Por ahora, nos enfocaremos en pagos regulares y profundizaremos en los pagos por ruta en una [sección posterior](./path-payment.mdx).
-
-```html title="/src/routes/dashboard/send/+page.svelte"
-<script>
-  /**
-   * All functionality surrounding path payments has been omitted here. While it
-   * is contained in the same file in the source repo, in this tutorial page, we
-   * are stripping that out and will include it in a later section.
-   */
-
-  // `export let data` allows us to pull in any parent load data for use here.
-  /** @type {import('./$types').PageData} */
-  export let data;
-
-  // We import any Svelte components we will need
-  import ConfirmationModal from "$lib/components/ConfirmationModal.svelte";
-  import InfoAlert from "$lib/components/InfoAlert.svelte";
-
-  // We import any stores we will need to read and/or write
-  import { infoMessage } from "$lib/stores/alertsStore";
-  import { contacts } from "$lib/stores/contactsStore";
-  import { walletStore } from "$lib/stores/walletStore";
-
-  // We import some of our `$lib` functions
-  import {
-    fetchAccount,
-    submit,
-    fetchAccountBalances,
-  } from "$lib/stellar/horizonQueries";
-  import {
-    createCreateAccountTransaction,
-    createPaymentTransaction,
-  } from "$lib/stellar/transactions";
-
-  // The `open` Svelte context is used to open the confirmation modal
-  import { getContext } from "svelte";
-  const { open } = getContext("simple-modal");
-
-  // Define some component variables that will be used throughout the page
-  let destination = "";
-  $: otherDestination = destination === "other";
-  let otherPublicKey = "";
-  let sendAsset = "native";
-  let sendAmount = "";
-  let receiveAsset = "";
-  let receiveAmount = "";
-  let memo = "";
-  let createAccount = null;
-  let paymentXDR = "";
-  let paymentNetwork = "";
-
-  // Check whether or not the account exists and is funded on the Stellar network.
-  let checkDestination = async (publicKey) => {
-    // Only do this if the `publicKey` is not "other". This check lets us
-    // use the same function for both the select dropdown, and the
-    // `otherPublicKey` input element.
-    if (publicKey !== "other") {
-      try {
-        // If the account returns successfully, ensure we're not using a
-        // `createAccount` operation
-        await fetchAccount(publicKey);
-        createAccount = false;
-      } catch (err) {
-        // Otherwise, inform the user about what will take place
-        // @ts-ignore
-        if (err.status === 404) {
-          createAccount = true;
-          sendAsset = "native";
-          infoMessage.set(
-            "Account Not Funded: You are sending a payment to an account that does not yet exist on the Stellar ledger. Your payment will take the form of a <code>creatAccount</code> operation, and the amount you send must be at least 1 XLM.",
-          );
-        }
-      }
-    }
-  };
-
-  // Takes an action after the pincode has been confirmed by the user.
-  const onConfirm = async (pincode) => {
-    // Use the walletStore to sign the transaction
-    let signedTransaction = await walletStore.sign({
-      transactionXDR: paymentXDR,
-      network: paymentNetwork,
-      pincode: pincode,
-    });
-    // Submit the transaction to the Stellar network
-    await submit(signedTransaction);
-  };
-
-  // Create a payment transaction depending on user selections, and present it
-  // to the user for approval or rejection.
-  const previewPaymentTransaction = async () => {
-    let { transaction, network_passphrase } = createAccount
-      ? await createCreateAccountTransaction({
-          source: data.publicKey,
-          destination: otherDestination ? otherPublicKey : destination,
-          amount: sendAmount,
-          memo: memo,
-        })
-      : await createPaymentTransaction({
-          source: data.publicKey,
-          destination: otherDestination ? otherPublicKey : destination,
-          asset: sendAsset,
-          amount: sendAmount,
-          memo: memo,
-        });
-
-    // Set the component variables to hold the transaction details
-    paymentXDR = transaction;
-    paymentNetwork = network_passphrase;
-
-    // Open the confirmation modal for the user to confirm or reject the
-    // transaction. We provide our customized `onConfirm` function, but we
-    // have no need to customize and pass an `onReject` function.
-    open(ConfirmationModal, {
-      transactionXDR: paymentXDR,
-      transactionNetwork: paymentNetwork,
-      onConfirm: onConfirm,
-    });
-  };
-</script>
-
-<!-- HTML has been omitted from this tutorial. Please check the source file -->
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/routes/dashboard/send/+page.svelte
-
-### Las funciones de transacción
-
-En la sección anterior, utilizamos la función `createPaymentTransaction`. Esta función se puede utilizar para enviar un pago de cualquier activo de una dirección Stellar a otra.
-
-También utilizamos la función `createCreateAccountTransaction`. Esto se utiliza cuando la cuenta de destino no está actualmente financiada y activa en la red Stellar. El único activo posible en este escenario es el XLM nativo.
-
-```js title="/src/lib/stellar/transactions.js"
-import {
-  TransactionBuilder,
-  Networks,
-  Operation,
-  Asset,
-  Memo,
-} from "@stellar/stellar-sdk";
-import { Server } from "@stellar/stellar-sdk/rpc";
-import { error } from "@sveltejs/kit";
-
-// We are setting a very high maximum fee, which increases our transaction's
-// chance of being included in the ledger. We're making this a `const` so we can
-// change it on one place as and when recommendations and/or best practices
-// evolve. Current recommended fee is `100_000` stroops.
-const maxFeePerOperation = "100000";
-const rpcUrl = "https://soroban-testnet.stellar.org";
-const networkPassphrase = Networks.TESTNET;
-const standardTimebounds = 300; // 5 minutes for the user to review/sign/submit
-
-// Constructs and returns a Stellar transaction that contains a `payment` operaion and an optional memo.
-export async function createPaymentTransaction({
-  source,
-  destination,
-  asset,
-  amount,
-  memo,
-}) {
-  // First, we setup our transaction by loading the source account from the
-  // network, and initializing the TransactionBuilder. This is the first step
-  // in constructing all Stellar transactions.
-  let server = new Server(rpcUrl);
-  let sourceAccount = await server.getAccount(source);
-  let transaction = new TransactionBuilder(sourceAccount, {
-    networkPassphrase: networkPassphrase,
-    fee: maxFeePerOperation,
-  });
-
-  let sendAsset;
-  if (asset && asset !== "native") {
-    sendAsset = new Asset(asset.split(":")[0], asset.split(":")[1]);
-  } else {
-    sendAsset = Asset.native();
-  }
-
-  // If a memo was supplied, add it to the transaction. Here, we have the
-  // option of a hash memo because this is common practice by anchor transfers
-  if (memo) {
-    if (typeof memo === "string") {
-      transaction.addMemo(Memo.text(memo));
-    } else if (typeof memo === "object") {
-      transaction.addMemo(Memo.hash(memo.toString("hex")));
-    }
-  }
-
-  // Add a single `payment` operation
-  transaction.addOperation(
-    Operation.payment({
-      destination: destination,
-      amount: amount.toString(),
-      asset: sendAsset,
-    }),
-  );
-
-  // Before the transaction can be signed, it requires timebounds, and it must
-  // be "built"
-  let builtTransaction = transaction.setTimeout(standardTimebounds).build();
-  return {
-    transaction: builtTransaction.toXDR(),
-    network_passphrase: networkPassphrase,
-  };
-}
-
-// Constructs and returns a Stellar transaction that contains a `createAccount` operation and an optional memo.
-export async function createCreateAccountTransaction({
-  source,
-  destination,
-  amount,
-  memo,
-}) {
-  // The minimum account balance on the Stellar network is 1 XLM (2 base
-  // reserves). We'll check that `amount` meets or exceeds that requirement
-  // early, so we can fail quickly.
-  if (parseFloat(amount.toString()) < 1) {
-    throw error(400, { message: "insufficient starting balance" });
-  }
-
-  // First, we setup our transaction by loading the source account from the
-  // network, and initializing the TransactionBuilder. This is the first step
-  // in constructing all Stellar transactions.
-  let server = new Server(rpcUrl);
-  let sourceAccount = await server.getAccount(source);
-  let transaction = new TransactionBuilder(sourceAccount, {
-    networkPassphrase: networkPassphrase,
-    fee: maxFeePerOperation,
-  });
-
-  // If a memo was supplied, add it to the transaction
-  if (memo) {
-    transaction.addMemo(Memo.text(memo));
-  }
-
-  // Add a single `createAccount` operation
-  transaction.addOperation(
-    Operation.createAccount({
-      destination: destination,
-      startingBalance: amount.toString(),
-    }),
-  );
-
-  // Before the transaction can be signed, it requires timebounds, and it must
-  // be "built"
-  let builtTransaction = transaction.setTimeout(standardTimebounds).build();
-  return {
-    transaction: builtTransaction.toXDR(),
-    network_passphrase: networkPassphrase,
-  };
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/querying-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/querying-data.mdx
deleted file mode 100644
index 29888a8c20..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/querying-data.mdx
+++ /dev/null
@@ -1,345 +0,0 @@
----
-title: Consulta de Datos
-sidebar_position: 70
----
-
-Tu aplicación estará consultando datos de Horizon (una de las APIs de Stellar) a lo largo de su funcionalidad. Información como saldos de cuentas, historial de transacciones, números de secuencia de transacciones, disponibilidad de activos y más se almacenan en la base de datos de Horizon.
-
-Aquí hay una lista de algunas consultas comunes que realizarás.
-
-:::note
-
-In other places in this tutorial, we have omitted the JSDoc descriptions and typing for the sake of clean presentation. Aquí, estamos incluyendo eso para hacer que estas funciones sean más fáciles de copiar/pegar.
-
-:::
-
-## Importaciones y tipos
-
-```js title="/src/lib/stellar/horizonQueries.js"
-import { error } from "@sveltejs/kit";
-import {
-  Server,
-  TransactionBuilder,
-  Networks,
-  StrKey,
-  Asset,
-} from "stellar-sdk";
-
-const horizonUrl = "https://horizon-testnet.stellar.org";
-const server = new Server(horizonUrl);
-
-/**
- * @module $lib/stellar/horizonQueries
- * @description A collection of function that helps query various information
- * from the [Horizon API](https://developers.stellar.org/docs/data/apis/horizon). This
- * allows us to abstract and simplify some interactions so we don't have to have
- * _everything_ contained within our `*.svelte` files.
- */
-
-// We'll import some type definitions that already exists within the
-// `stellar-sdk` package, so our functions will know what to expect.
-/** @typedef {import('stellar-sdk').ServerApi.AccountRecord} AccountRecord */
-/** @typedef {import('stellar-sdk').Horizon.ErrorResponseData} ErrorResponseData */
-/** @typedef {import('stellar-sdk').ServerApi.PaymentOperationRecord} PaymentOperationRecord */
-/** @typedef {import('stellar-sdk').Horizon.BalanceLine} BalanceLine */
-/** @typedef {import('stellar-sdk').Horizon.BalanceLineAsset} BalanceLineAsset */
-/** @typedef {import('stellar-sdk').Transaction} Transaction */
-/** @typedef {import('stellar-sdk').ServerApi.PaymentPathRecord} PaymentPathRecord */
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-## fetchAccount
-
-Devuelve el número de secuencia de una cuenta, saldos de activos y líneas de confianza.
-
-```js title="/src/lib/stellar/horizonQueries.js"
-/**
- * Fetches and returns details about an account on the Stellar network.
- * @async
- * @function fetchAccount
- * @param {string} publicKey Public Stellar address to query information about
- * @returns {Promise<AccountRecord>} Object containing whether or not the account is funded, and (if it is) account details
- * @throws {error} Will throw an error if the account is not funded on the Stellar network, or if an invalid public key was provided.
- */
-export async function fetchAccount(publicKey) {
-  if (StrKey.isValidEd25519PublicKey(publicKey)) {
-    try {
-      let account = await server.accounts().accountId(publicKey).call();
-      return account;
-    } catch (err) {
-      // @ts-ignore
-      if (err.response?.status === 404) {
-        throw error(404, "account not funded on network");
-      } else {
-        // @ts-ignore
-        throw error(err.response?.status ?? 400, {
-          // @ts-ignore
-          message: `${err.response?.title} - ${err.response?.detail}`,
-        });
-      }
-    }
-  } else {
-    throw error(400, { message: "invalid public key" });
-  }
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-## fetchAccountBalances
-
-Obtiene saldos existentes para un `publicKey` dado.
-
-```js title="/src/lib/stellar/horizonQueries.js"
-/**
- * Fetches and returns balance details for an account on the Stellar network.
- * @async
- * @function fetchAccountBalances
- * @param {string} publicKey Public Stellar address holding balances to query
- * @returns {Promise<BalanceLine[]>} Array containing balance information for each asset the account holds
- */
-export async function fetchAccountBalances(publicKey) {
-  const { balances } = await fetchAccount(publicKey);
-  return balances;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-## fetchRecentPayments
-
-Encuentra cualquier pago realizado a o desde el `publicKey` dado (incluye: pagos, pagos de rutas y fusiones de cuentas).
-
-```js title="/src/lib/stellar/horizonQueries.js"
-/**
- * Fetches and returns recent `payment`, `createAccount` operations that had an effect on this account.
- * @async
- * @function fetchRecentPayments
- * @param {string} publicKey Public Stellar address to query recent payment operations to/from
- * @param {number} [limit] Number of operations to request from the server
- * @returns {Promise<PaymentOperationRecord[]>} Array containing details for each recent payment
- */
-export async function fetchRecentPayments(publicKey, limit = 10) {
-  const { records } = await server
-    .payments()
-    .forAccount(publicKey)
-    .limit(limit)
-    .order("desc")
-    .call();
-  return records;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-## submit
-
-Envía una transacción firmada a la red Stellar.
-
-```js title="/src/lib/stellar/horizonQueries.js"
-/**
- * Submits a Stellar transaction to the network for inclusion in the ledger.
- * @async
- * @function submit
- * @param {Transaction} transaction Built transaction to submit to the network
- * @throws Will throw an error if the transaction is not submitted successfully.
- */
-export async function submit(transaction) {
-  try {
-    await server.submitTransaction(transaction);
-  } catch (err) {
-    throw error(400, {
-      // @ts-ignore
-      message: `${err.response?.title} - ${err.response?.data.extras.result_codes}`,
-    });
-  }
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-## fetchAssetsWithHomeDomains
-
-Creamos un nuevo tipo `HomeDomainBalanceLine` que incluye la información del saldo de una línea de confianza de un usuario y también agrega el `home_domain` del emisor del activo. Si estás utilizando algo más para la seguridad de tipos (o nada en absoluto), siéntete libre de adaptar o ignorar los `@typedef`s que hemos incluido aquí.
-
-Luego, revisa todas las cuentas emisoras y devuelve solo las que tengan un `home_domain` establecido en la cuenta.
-
-```js title="/src/lib/stellar/horizonQueries.js"
-/**
- * @typedef {Object} HomeDomainObject
- * @property {string} home_domain Domain name the issuer of this asset has set for their account on the Stellar network.
- */
-
-/** @typedef {BalanceLineAsset & HomeDomainObject} HomeDomainBalanceLine */
-
-/**
- * Fetches `home_domain` from asset issuer accounts on the Stellar network and returns an array of balances.
- * @async
- * @function fetchAssetsWithHomeDomains
- * @param {BalanceLine[]} balances Array of balances to query issuer accounts of
- * @returns {Promise<HomeDomainBalanceLine[]>} Array of balance details for assets that do have a `home_domain` setting
- */
-export async function fetchAssetsWithHomeDomains(balances) {
-  let homeDomains = await Promise.all(
-    balances.map(async (asset) => {
-      // We are only interested in issued assets (i.e., not LPs and not XLM)
-      if ("asset_issuer" in asset) {
-        // Fetch the account from the network, and add its info to the array, along with the home_domain
-        let account = await fetchAccount(asset.asset_issuer);
-        if ("home_domain" in account) {
-          return {
-            ...asset,
-            home_domain: account.home_domain,
-          };
-        }
-      }
-    }),
-  );
-
-  // Filter out any null array entries before returning
-  // @ts-ignore
-  return homeDomains.filter((balance) => balance);
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-## findStrictSendPaths
-
-Encuentra las rutas de envío estrictas disponibles entre un activo/cantidad de origen y una cuenta receptora.
-
-```js title="/src/lib/stellar/horizonQueries.js"
-/**
- * Fetches available paths on the Stellar network between the destination account, and the asset sent by the source account.
- * @async
- * @function findStrictSendPaths
- * @param {Object} opts Options object
- * @param {string} opts.sourceAsset Stellar asset which will be sent from the source account
- * @param {string|number} opts.sourceAmount Amount of the Stellar asset that should be debited from the srouce account
- * @param {string} opts.destinationPublicKey Public Stellar address that will receive the destination asset
- * @returns {Promise<PaymentPathRecord[]>} Array of payment paths that can be selected for the transaction
- * @throws Will throw an error if there are no available payment paths.
- */
-export async function findStrictSendPaths({
-  sourceAsset,
-  sourceAmount,
-  destinationPublicKey,
-}) {
-  let asset =
-    sourceAsset === "native"
-      ? Asset.native()
-      : new Asset(sourceAsset.split(":")[0], sourceAsset.split(":")[1]);
-  let response = await server
-    .strictSendPaths(asset, sourceAmount.toString(), destinationPublicKey)
-    .call();
-  if (response.records.length > 0) {
-    return response.records;
-  } else {
-    throw error(400, { message: "no strict send paths available" });
-  }
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-## findStrictReceivePaths
-
-Encuentra las rutas de recepción estrictas disponibles entre una cuenta de origen y un activo/cantidad receptora.
-
-```js title="/src/lib/stellar/horizonQueries.js"
-/**
- * Fetches available paths on the Stellar network between the source account, and the asset to be received by the destination.
- * @async
- * @function findStrictReceivePaths
- * @param {Object} opts Options object
- * @param {string} opts.sourcePublicKey Public Stellar address that will be the source of the payment operation
- * @param {string} opts.destinationAsset Stellar asset which should be received in the destination account
- * @param {string|number} opts.destinationAmount Amount of the Stellar asset that should be credited to the destination account
- * @returns {Promise<PaymentPathRecord[]>} Array of payment paths that can be selected for the transaction
- * @throws Will throw an error if there are no available payment paths.
- */
-export async function findStrictReceivePaths({
-  sourcePublicKey,
-  destinationAsset,
-  destinationAmount,
-}) {
-  let asset =
-    destinationAsset === "native"
-      ? Asset.native()
-      : new Asset(
-          destinationAsset.split(":")[0],
-          destinationAsset.split(":")[1],
-        );
-  let response = await server
-    .strictReceivePaths(sourcePublicKey, asset, destinationAmount.toString())
-    .call();
-  if (response.records.length > 0) {
-    return response.records;
-  } else {
-    throw error(400, { message: "no strict receive paths available" });
-  }
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/stellar/horizonQueries.js
-
-## Consulta Stellar Expert
-
-Stellar Expert es un explorador de bloques de terceros que es indispensable como herramienta para entender lo que está sucediendo en la red Stellar. En nuestra página `/dashboard/assets`, estamos pre-poblando una lista de líneas de confianza de activos que un usuario podría elegir agregar a su cuenta de Stellar. Obtenemos esta lista de activos de la API de Stellar Expert.
-
-:::note
-
-Stellar Expert emplea su propio algoritmo para determinar la calidad de un activo. Este algoritmo considera cosas como el número de pagos realizados utilizando un activo, el número de cuentas que poseen ese activo, cuánto del activo está disponible en el DEX o en fondos de liquidez, y así sucesivamente. Estos rankings no son una "determinación final" de la calidad de un activo de ninguna manera, y son más como una observación de cuáles activos de Stellar ven más uso y actividad en la red.
-
-:::
-
-Hemos creado nuestro propio tipo `RankedAsset` para que BasicPay sepa cómo interactuar con estos objetos. Y luego estamos recuperando los diez activos mejor valorados de la API de Stellar Expert.
-
-```js title="/src/lib/utils/stellarExpert.js"
-const network = "testnet";
-const baseUrl = `https://api.stellar.expert/explorer/${network}`;
-
-/**
- * An asset object that has been returned by our query to Stellar.Expert
- * @typedef {Object} RankedAsset
- * @property {string} asset Asset identifier
- * @property {number} traded_amount Total traded amount (in stroops)
- * @property {number} payments_amount Total payments amount (in stroops)
- * @property {number} created Timestamp of the first recorder operation with asset
- * @property {number} supply Total issued asset supply
- * @property {Object} trustlines Trustlines established to an asset
- * @property {number} trades Total number of trades
- * @property {number} payments Total number of payments
- * @property {string} domain Associated `home_domain`
- * @property {Object} tomlInfo Asset information from stellar.toml file
- * @property {Object} rating Composite asset rating
- * @property {number} paging_token Paging token
- * @see {@link https://stellar.expert/openapi.html#tag/Asset-Info-API/operation/getAllAssets}
- */
-
-/**
- * Fetches and returns the most highly rated assets, according to the Stellar.Expert calculations.
- * @async
- * @function fetchAssets
- * @returns {Promise<RankedAsset[]>} Array of objects containing details for each asset
- */
-export async function fetchAssets() {
-  let res = await fetch(
-    `${baseUrl}/asset?${new URLSearchParams({
-      // these are all the defaults, but you could customize them if needed
-      search: "",
-      sort: "rating",
-      order: "desc",
-      limit: "10",
-      cursor: "0",
-    })}`,
-  );
-  let json = await res.json();
-
-  let records = json._embedded.records;
-  return records;
-}
-```
-
-**Fuente:** https://github.com/stellar/basic-payment-app/blob/main/src/lib/utils/stellarExpert.js
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/README.mdx
deleted file mode 100644
index 72806c157f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Desarrollar una Dapp de Libro de Visitas Potenciada por Clave de Acceso
-sidebar_position: 57
----
-
-import DocCardList from "@theme/DocCardList";
-
-Esta sección te guía a través del diseño y desarrollo de una aplicación descentralizada (dapp) que interactúa con un libro de visitas de contrato inteligente, permitiendo a los usuarios leer y escribir mensajes públicos. Este tutorial también implementa una billetera inteligente impulsada por clave de acceso para la autenticación de usuarios.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/bindings.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/bindings.mdx
deleted file mode 100644
index 80ade8a0d1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/bindings.mdx
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Generar bindings
-sidebar_position: 30
----
-
-Centrémonos en cómo interactuaremos con el contrato inteligente desplegado. ¡Aquí es donde entran los bindings de TypeScript! Pero, te escucho preguntar: ¿Qué son los bindings de TypeScript?
-
-Estos bindings son una característica de la CLI de Stellar que generará y producirá un paquete NPM completamente tipado listo para integración en tu frontend. Esto significa que puedes importar e invocar un contrato inteligente como si fuera cualquier otro paquete de Node.js! Obtienes funciones tipadas para cada una de las funciones de tu contrato, y estas darán como resultado una transacción ensamblada, simulada, firmable y enviable!
-
-:::tip
-
-¡Esto se puede hacer con CUALQUIER contrato que esté en vivo en la red! O, también puedes usarlo en contratos que solo has compilado localmente.
-
-:::
-
-Generaremos nuestros bindings de contrato y los mantendremos en el mismo repositorio que nuestro código frontend. Sin embargo, podrías hacer esto de muchas maneras diferentes:
-
-- Tu frontend puede instanciar un `contract.Client` usando la [función `fromWasmHash`](https://stellar.github.io/js-stellar-sdk/module-contract.Client.html#.fromWasmHash) del SDK de JavaScript. Esto puede generar bindings al vuelo mientras tus usuarios navegan por tu aplicación.
-- Tu proceso de implementación podría incluir un paso que crea/despliega/vincula un paquete de contrato en el momento del despliegue.
-- Incluso podrías generar y publicar un paquete de bindings por sí solo. Luego `pnpm install <bindings_package_name>` puede hacerse en cualquier dapp con el que necesites interactuar (o alguien más) que podría necesitar interactuar con ese contrato.
-
-### El método manual
-
-¡Antes de que saltes adelante! Echa un vistazo a esta sección (breve). Es _realmente_ útil tener una comprensión completa de qué pasos estamos siguiendo en la sección automatizada. Esto te ayudará a adaptar y/o solucionar problemas de este tutorial para tus propósitos específicos.
-
-#### Instalar el contrato compilado
-
-El código del contrato inteligente necesita ser instalado en la red primero. Esto sube el archivo Wasm binario compilado a la blockchain para que sea instanciado en un contrato posteriormente. Desde dentro de tu directorio de proyecto:
-
-```shell
-stellar contract upload \
-    --source-account <identity or secret key> \
-    --network testnet \
-    --wasm ./target/wasm32v1-none/release/ye_olde_guestbook.wasm
-```
-
-#### Desplegar una instancia de contrato
-
-Esto devolverá un hash hexadecimal correspondiente al Wasm ejecutable subido. Este hash puede ser usado en el comando de despliegue para crear una nueva instancia de contrato:
-
-```shell
-stellar contract deploy \
-    --source-account <identity or secret key> \
-    --network testnet \
-    --wasm-hash <wasm_hash_from_install_step>
-```
-
-#### Generar bindings para el contrato desplegado
-
-Ahora podemos (de nuevo) usar la CLI de Stellar para generar bindings del contrato que acabamos de desplegar. También puedes generar estos bindings desde tu archivo Wasm local usando el parámetro `--wasm-hash`. El parámetro `--overwrite` se usa para decirle a la CLI que debe generar el paquete de bindings, incluso si encuentra que el directorio no está vacío (es decir, estamos volviendo a vincular un contrato porque hemos modificado el código y lo hemos redeployado).
-
-```shell
-stellar contract bindings typescript \
-    --network testnet \
-    --id <contract_address_from_deploy_step> \
-    --output-dir ./packages/ye_olde_guestbook \
-    --overwrite
-```
-
-Tendremos que construir el paquete de bindings, ya que (en su estado inicial) el paquete es mayormente de tipos de TypeScript y stubs para las varias funciones del contrato.
-
-```shell
-cd packages/ye_olde_guestbook
-pnpm install
-pnpm run build
-cd ../..
-```
-
-#### Importar el paquete de bindings como una dependencia del proyecto
-
-Con nuestros bindings generados, podemos agregarlo a nuestro proyecto frontend. Ejecuta esto desde la raíz de tu proyecto:
-
-```shell
-pnpm add file:./packages/ye_olde_guestbook
-```
-
-#### Importar el cliente de bindings en el proyecto de SvelteKit
-
-:::info
-
-Nos estamos desviando un _poco_ hacia el lado Svelte de las cosas aquí. El objetivo principal de este paso es obtener el cliente del contrato (que es el "paquete de bindings" que acabamos de generar) en nuestro frontend de una manera que sea utilizable donde sea que lo necesitemos. En SvelteKit, lo ponemos en `src/lib/contracts` porque eso significa que podemos acceder fácilmente al cliente importando desde `$lib/contracts/ye_olde_guestbook` cuando y donde lo necesitemos.
-
-:::
-
-Ahora, definiremos el cliente de contrato de una manera que podamos acceder fácilmente a través del resto de nuestra aplicación.
-
-```js title="src/lib/contracts/ye_olde_guestbook.ts"
-import * as Client from "ye_olde_guestbook"; // import the package we just added as a dependency
-import { PUBLIC_STELLAR_RPC_URL } from "$env/static/public"; // import the RPC url from the .env file
-
-// instantiate and export the Client class from the bindings package
-export default new Client.Client({
-  ...Client.networks.testnet, // this includes the contract address and network passphrase
-  rpcUrl: PUBLIC_STELLAR_RPC_URL, // this is required to invoke the contract through RPC calls
-});
-```
-
-### El método automatizado
-
-¡Eso fue un montón de pasos y un montón de trabajo, ¿verdad!? La buena noticia es que nuestra plantilla inicial (¿recuerdas eso?) viene con un script `initialize.js` que realizará todas esas acciones por ti! ¡Este script pasará por todos los siguientes pasos por ti:
-
-- Crear y financiar un keypair en la CLI
-- Instalar y desplegar **todos los contratos** en el directorio `/contracts`
-- Generar bindings de los contratos desplegados
-- Crear un archivo `$lib/contracts/<contract_alias>.ts` para fácil importación en tu código frontend
-
-Siempre puedes personalizar este script para adaptarlo a tus necesidades. Consulta el [código fuente aquí](https://github.com/ElliotFriend/soroban-template-sveltekit-passkeys/blob/main/initialize.js) (que ha sido documentado con comentarios). O, puedes ver el [script mantenido oficialmente](https://github.com/stellar/soroban-template-astro/blob/main/initialize.js) en el [repositorio `soroban-template-astro`](https://github.com/stellar/soroban-template-astro), también.
-
-Ejecuta el script de inicialización así:
-
-```shell
-node initialize.js
-```
-
-:::info
-
-Para una visión más completa del proceso de crear, personalizar y usar scripts de inicialización como este, consulta la [guía de plantilla frontend](../../guides/dapps/soroban-contract-init-template.mdx).
-
-:::
-
-También hemos agregado un comando a los scripts de `package.json`, así que puedes ejecutar este script de inicialización simplemente ejecutando (desde la raíz de tu proyecto):
-
-```shell
-pnpm run setup
-```
-
-Bien, así que ahora hemos creado un proyecto inicial, escrito un contrato inteligente de libro de visitas y generado un paquete NPM que nos ayudará a interactuar con ese contrato en la red. ¡Increíble!
-
-A continuación, echémosle un vistazo a cómo nuestros usuarios se conectarán e interactuarán con nuestra dapp. ¡Es hora de las claves de acceso! (insertar ruidos de cuerno de aire)📢
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/frontend.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/frontend.mdx
deleted file mode 100644
index 4f0fccf2e4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/frontend.mdx
+++ /dev/null
@@ -1,601 +0,0 @@
----
-title: Recorrido por el frontend de Dapp
-sidebar_position: 60
----
-
-Así que ahora tenemos todas las piezas en su lugar y estamos listos para conectar los puntos.
-
-## Cosas del tipo de cuenta
-
-Dado que acabamos de pasar por la configuración de todas las claves, empecemos desde allí. Crearemos las funciones que se utilizarán para crear la billetera inteligente del usuario, iniciar sesión con su billetera inteligente y la funcionalidad de cerrar sesión. También añadiremos un "menú de perfil" que puede desplegarse cuando un usuario ha iniciado sesión y que les dará opciones para ver su billetera inteligente en un explorador de bloques, enviar una de esas donaciones tan importantes a nuestro libro de visitas, solicitar más fondos (Testnet), etc.
-
-:::info
-
-Estamos usando algunas piezas del [estado de Svelte](https://svelte.dev/docs/svelte/$state) para mantener el valor de la dirección del contrato de la billetera inteligente del usuario, así como la clave pública de su clave. Tu implementación de mantener este estado puede diferir dependiendo de tu frontend elegido, gestión de estado y diseño del proyecto. Con suerte, en cualquier situación, puedes inspirarte en la forma en que lo hemos hecho para este tutorial.
-
-:::
-
-### Configuración de botones de conexión
-
-Tenemos un componente en `$lib/components/connectButtons.svelte` que alberga toda la funcionalidad de registro, inicio de sesión y cierre de sesión. Esto se integra en el componente de encabezado y está disponible a lo largo de toda la dapp. La premisa básica de este componente es que tenemos una colección de botones, así como las funciones correspondientes que deben llevarse a cabo cuando se hace clic en el botón.
-
-Los botones en sí son bastante simples:
-
-```html title="src/lib/components/connectButtons.svelte"
-<div class="flex space-x-1 md:space-x-2">
-  <button class="btn variant-filled-primary" onclick="{signup}">Signup</button>
-  <button class="btn variant-soft-primary" onclick="{login}">Login</button>
-  <button class="btn variant-soft-error" onclick="{logout}">Logout</button>
-</div>
-```
-
-Si miras el [código fuente](https://github.com/ElliotFriend/ye-olde-guestbook/blob/main/src/lib/components/ConnectButtons.svelte) de este componente, verás que hacemos un poco más de verificación de estado en torno a la exhibición de los botones. Esto hace que un botón de "iniciar sesión" no se muestre cuando un usuario ya está _iniciado sesión_, por ejemplo. Para los propósitos de este tutorial, sin embargo, nos centraremos en las funciones mismas, en lugar del HTML de los botones.
-
-Comencemos con la función de registro.
-
-#### Registro de usuario
-
-Para registrar a nuestro usuario, utilizaremos la instancia `account` de la clase `PasskeyKit` de nuestro archivo `$lib/passkeyClient.ts`. La instancia `account` tiene una función llamada `createWallet` que hará la mayor parte del trabajo pesado por nosotros, solo necesitamos asegurarnos de llamar a la función correctamente.
-
-Hacemos una pequeña verificación de errores aquí, pero no mucho. En aplicaciones prácticas, probablemente querrías investigar la causa de cualquier error aquí y asegurarte de que se mitiguen antes de decirle a un usuario que lo intente de nuevo.
-
-```js title="src/lib/components/connectButtons.svelte"
-import { account, send, fundContract } from "$lib/passkeyClient";
-import { keyId } from "$lib/stores/keyId";
-import { contractId } from "$lib/stores/contractId";
-
-async function signup() {
-  console.log("signing up");
-  try {
-    // The createWallet function takes two strings, an app name and a user name.
-    // It returns the public key of the passkey, a contract address which will
-    // be the user's wallet, and a built transaction (ready to submit) to create
-    // the smart wallet on-chain.
-    const {
-      keyId_base64,
-      contractId: cid,
-      built,
-    } = await account.createWallet("Ye Olde Guestbook", "User Name Goes Here");
-
-    // Store the key ID and contract address in our localStorage stores
-    keyId.set(keyId_base64);
-    contractId.set(cid);
-
-    if (!built) {
-      error(500, {
-        message: "built transaction missing",
-      });
-    }
-
-    // Send the transaction, fund the smart wallet, refresh the balance
-    await send(built);
-    await fundContract($contractId);
-    getBalance();
-  } catch (err) {
-    console.log(err);
-    toastStore.trigger({
-      message: "Something went wrong signing up. Please try again later.",
-      background: "variant-filled-error",
-    });
-  }
-}
-```
-
-#### Inicio de sesión de usuario
-
-¡Genial! El usuario se registra y obtiene algunos lumens (Testnet) todo en uno. Ahora les daremos una manera de iniciar sesión con la clave que ya han asociado con la billetera inteligente.
-
-```js title="src/lib/components/connectButtons.svelte"
-import { getContractId } from "$lib/passkeyClient";
-
-async function login() {
-  console.log("logging in");
-  try {
-    // The connectWallet function requires us to pass a function that can
-    // be used to reverse-lookup the smart wallet address, provided we know
-    // the passkey's ID (the user supplies that during the function's execution)
-    const { keyId_base64, contractId: cid } = await account.connectWallet({
-      getContractId,
-    });
-
-    // Store the key ID and contract address in our localStorage stores
-    keyId.set(keyId_base64);
-    console.log($keyId);
-    contractId.set(cid);
-    console.log($contractId);
-  } catch (err) {
-    console.log(err);
-    toastStore.trigger({
-      message: "Something went wrong logging in. Please try again later.",
-      background: "variant-filled-error",
-    });
-  }
-}
-```
-
-Similar, pero más simple, en comparación con nuestra función de `signup`. Estamos utilizando la función `account.connectWallet`. Esta función hará:
-
-1. Solicitará al usuario que se autentique, proporcionando la ID de la clave en el proceso,
-2. Usará Mercury para buscar el ID del contrato dada la ID de la clave y, finalmente,
-3. Devolverá la ID de la clave y la dirección de la billetera inteligente a nuestra dapp.
-
-¡Genial! Hagamos que el usuario cierre sesión cuando lo necesite.
-
-#### Cierre de sesión de usuario
-
-Esto es bastante más fácil que las funciones de registro o inicio de sesión. Realmente no necesitamos comunicarnos con la red Stellar o Mercury aquí. Todo lo que haremos es limpiar el estado del usuario, esencialmente.
-
-```js title="src/lib/components/connectButtons.svelte"
-async function logout() {
-  try {
-    // Reset the localStorage entry for the keyId
-    keyId.reset();
-    localStorage.removeItem("yog:keyId");
-
-    // Set the contract address store to an empty string
-    contractId.set("");
-
-    // Refresh the page, just for good measure
-    window.location.reload();
-  } catch (err) {
-    console.log(err);
-    toastStore.trigger({
-      message: "Something went wrong logging out. Please try again later.",
-      background: "variant-filled-error",
-    });
-  }
-}
-```
-
-Con esas tres funciones, ¡nuestra dapp está lista para que los usuarios se autentiquen con la dapp! Mucho más fácil de lo que probablemente esperabas, ¿verdad!?
-
-### El "menú de perfil"
-
-Aún en nuestro componente `connectButtons.svelte`, también tenemos una colección de botones y funciones que representan una especie de "menú de perfil". El usuario puede usar estos botones para ver su saldo de billetera inteligente, verlo en [Stellar Expert](https://stellar.expert), enviar una donación a nuestro (humilde) mantenedor del libro de visitas, solicitar más fondos (Testnet), etc. Mucho de esto no es necesario profundizar aquí en este tutorial, aunque te recomiendo encarecidamente que eches un vistazo al [código fuente](https://github.com/ElliotFriend/ye-olde-guestbook/blob/main/src/lib/components/ConnectButtons.svelte) para obtener una mejor comprensión de esta funcionalidad.
-
-Sin embargo, aquí veremos la función `donate`. Este es un ejemplo realmente útil de cómo una dapp puede permitir que sus usuarios de billetera inteligente interactúen con cualquier activo en la red Stellar. (Aquí, estamos usando XLM de Testnet como nuestro activo, pero el flujo sería idéntico para _cualquier_ activo que desees usar.)
-
-El botón es aún bastante simple, al igual que los botones de autenticación. Estamos añadiendo algo de lógica de "carga" para cuando se realiza la transacción, sin embargo. Así que tiene _varias_ más campanas y silbatos.
-
-```html title="src/lib/components/connectButtons.svelte"
-<script lang="ts">
-  import LoaderCircle from "lucide-svelte/icons/loader-circle";
-  import HelpingHand from "lucide-svelte/icons/helping-hand";
-
-  let isDonating: boolean = false;
-</script>
-
-<button
-  class="btn variant-soft-surface w-full"
-  onclick="{donate}"
-  disabled="{isDonating}"
->
-  <span>
-    {#if isDonating}
-    <LoaderCircle class="animate-spin" />
-    {:else}
-    <HelpingHand />
-    {/if}
-  </span>
-  <span>Send Donation</span>
-</button>
-```
-
-La función `donate` aprovecha el cliente `native` SAC que hicimos en el archivo `$lib/passkeyClient.ts`. Esto nos permite llamar a la función de transferencia del contrato como cualquier otra función de JavaScript.
-
-```js title="src/lib/components/connectButtons.svelte"
-import { account, send, native } from '$lib/passkeyClient';
-import { keyId } from '$lib/stores/keyId';
-import { contractId } from '$lib/stores/contractId';
-
-async function donate() {
-    console.log('starting donation process');
-    isDonating = true;
-    try {
-        const user = prompt("Give this passkey a name")
-        const at = await native.transfer({
-            to: networks.testnet.contractId,
-            from: $contractId,
-            amount: BigInt(donation * 10_000_000),
-        });
-
-        await account.sign(at, { keyId: $keyId });
-        const res = await send(at.built!);
-        console.log(res);
-
-        toastStore.trigger({
-            message: 'Donation received! You really ARE the goat.',
-            background: 'variant-filled-success',
-        });
-        getBalance();
-    } catch (err) {
-        console.log(err);
-        toastStore.trigger({
-            message: 'Something went wrong donating. Please try again later.',
-            background: 'variant-filled-error',
-        });
-    } finally {
-        isDonating = false;
-    }
-}
-```
-
-:::info
-
-Estamos simplificando esta función _solo un poco_ para este tutorial. En la [dapp real](https://github.com/ElliotFriend/ye-olde-guestbook/blob/1a55a5238a71b624b789dfd82a6d7fd996407bd7/src/lib/components/ConnectButtons.svelte#L138), estamos usando un modal para recuperar la entrada del usuario. Eso termina luciendo un poco demasiado desordenado aquí.
-
-:::
-
-En resumen, es una invocación bastante fácil de la función `transfer` de SAC. Solo pasamos los campos `from`, `to` y `amount`. Luego, firmamos la transacción con nuestra instancia `account`, proporcionando nuestra ID de clave en los argumentos. Finalmente, enviamos la transacción usando nuestra función auxiliar, que enviará la solicitud a Launchtube, y estaremos listos para continuar. En este caso, realmente no nos preocupa el valor de retorno. Solo capturaremos cualquier error y notificaremos al usuario con un mensaje de toast.
-
-Suficiente de las cosas de cuenta y activos, ¡vamos a las entradas del libro de visitas!
-
-## Firmar el libro de visitas
-
-Primero, necesitaremos una página que nos permita realmente _firmar_ el libro de visitas. Tendremos un formulario que toma un campo `title` y `message`, y luego enviaremos la transacción con la función auxiliar `send`, tal como lo hicimos con la transferencia de XLM anteriormente.
-
-El formulario es bastante simple y apenas vale la pena mencionarlo. Tenemos un campo de texto, un campo de área de texto y un botón. Se realizan algunas verificaciones para ver si el botón debe estar habilitado (si un usuario no ha iniciado sesión, por ejemplo). De lo contrario, es bastante poco notable:
-
-```html title="src/routes/sign/+page.svelte"
-<script lang="ts">
-  import Signature from "lucide-svelte/icons/signature";
-  import LoaderCircle from "lucide-svelte/icons/loader-circle";
-
-  let messageTitle: string;
-  let messageText: string;
-  let isLoading: boolean = false;
-</script>
-
-<label class="label">
-  <span>Title</span>
-  <input
-    bind:value="{messageTitle}"
-    class="input"
-    type="text"
-    placeholder="Title"
-  />
-</label>
-
-<label class="label">
-  <span>Message</span>
-  <textarea
-    bind:value="{messageText}"
-    class="textarea"
-    rows="4"
-    placeholder="Write your message here"
-  ></textarea>
-</label>
-
-<button
-  on:click="{signGuestbook}"
-  type="button"
-  class="btn variant-filled-primary"
-  disabled="{signButtonDisabled}"
->
-  <span>
-    {#if isLoading}
-    <LoaderCircle class="animate-spin" />
-    {:else}
-    <Signature />
-    {/if}
-  </span>
-  <span>Sign!</span>
-</button>
-```
-
-La función `signGuestbook` (que se ejecuta cuando se hace clic en el botón) es donde están las partes más interesantes. Incluso así, se ve bastante similar a las otras transacciones que hemos enviado (creación de cuentas y transferencias de XLM).
-
-```js title="src/routes/sign/+page.svelte"
-import ye_olde_guestbook from '$lib/contracts/ye_olde_guestbook';
-import { contractId } from '$lib/stores/contractId';
-import { keyId } from '$lib/stores/keyId';
-import { account, send } from '$lib/passkeyClient';
-
-async function signGuestbook() {
-    try {
-        isLoading = true;
-        const at = await ye_olde_guestbook.write_message({
-            author: $contractId,
-            title: messageTitle,
-            text: messageText,
-        });
-
-        let txn = await account.sign(at.built!, { keyId: $keyId });
-        const { returnValue } = await send(txn.built!);
-        const messageId = xdr.ScVal.fromXDR(returnValue, 'base64').u32();
-
-        toastStore.trigger({
-            message: 'Huzzah!! You signed my guestbook! Thanks.',
-            background: 'variant-filled-success',
-        });
-        goto(`/read/${messageId}`);
-    } catch (err) {
-        console.log(err);
-        toastStore.trigger({
-            message: 'Something went wrong signing the guestbook. Please try again later.',
-            background: 'variant-filled-error',
-        });
-    } finally {
-        isLoading = false;
-    }
-}
-```
-
-El corazón y el alma de esta función es invocar la función `write_message` de nuestro contrato. Gracias a nuestros enlaces generados, esto se hace realmente fácil.
-
-Recibimos la ID del mensaje como valor de retorno y luego redirigimos al usuario a la página donde puede leer _esa_ entrada en particular.
-
-¿Cómo lee esta página la entrada del libro de visitas? ¡Excelente momento para esa pregunta!
-
-## Leer entradas del libro de visitas
-
-### Leer una entrada única
-
-La primera página que crearemos es una que lea y muestre un solo mensaje del libro de visitas desde el almacenamiento del contrato inteligente. Usaremos una función del lado del servidor para esto. De esa manera, si estuviéramos usando un proveedor RPC de pago, podríamos hacer que esta función se ejecute en el servidor y devuelva los datos relevantes al cliente.
-
-:::info
-
-Este `+page.server.ts` es una forma en Svelte de decir "cada vez que esta página es solicitada por un usuario, ejecuta esta función en el servidor y da los datos al cliente."
-
-La parte `[id]` del nombre de archivo le dice a esta ruta que esperamos tener un parámetro basado en la ruta, y podemos usarlo como `id`.
-
-:::
-
-```js title="src/routes/read/\[id]/+page.server.ts"
-import { error } from "@sveltejs/kit";
-import guestbook from "$lib/contracts/ye_olde_guestbook";
-import type { PageServerLoad } from "./$types";
-
-export const load: PageServerLoad = async ({ params }) => {
-  try {
-    let { result } = await guestbook.read_message({
-      message_id: parseInt(params.id),
-    });
-
-    return {
-      id: params.id,
-      message: result.unwrap(),
-    };
-  } catch (err) {
-    error(500, {
-      message:
-        "Sorry, something went wrong. Most likely, the message you're looking for doesn't exist.",
-    });
-  }
-};
-```
-
-Puedes ver aquí que estamos usando una de las funciones del contrato, `read_message` para obtener los datos. Esta es una función de "solo lectura", lo que significa que no se modifica ningún estado on-chain cuando se ejecuta. Así que podemos simplemente simular la invocación, lo cual ya está hecho para ti cuando se llama a la función generada por enlaces, y solo tomar los datos de la respuesta de simulación! ¡Bastante ingenioso, ¿verdad?!
-
-Pasamos los detalles del mensaje resultante de vuelta a la página, donde se mostrarán.
-
-```html title="src/routes/read/\[id]/+page.svelte"
-<script lang="ts">
-  import GuestbookMessage from "$lib/components/GuestbookMessage.svelte";
-  import type { PageData } from "./$types";
-
-  export let data: PageData;
-</script>
-
-<h1 class="h1">Read Message {data.id}</h1>
-<p>
-  You're viewing just message {data.id}. You can
-  <a class="anchor" href="/read">read all of them here</a>, as well.
-</p>
-
-<!-- This component is just a wrapper with a bunch of divs. We won't worry about it right now -->
-<GuestbookMessage message="{data.message}" messageId="{parseInt(data.id)}" />
-```
-
-### Leer todas las entradas
-
-¡Genial! Si conoces la ID de la entrada que deseas leer. La mayoría de las veces, probablemente no lo harías. Hagamos una página que pueda leer/mostrar todas las entradas del libro de visitas.
-
-Para esto, (de nuevo) mantendremos tanto de la lógica de consulta del lado del servidor como sea posible. Estos resultados de entrada del ledger pueden ser almacenados en caché. Y, el cliente no necesita hacer más rondas solo para consultar estas entradas. La ruta que realiza esta consulta es otro archivo `+page.server.ts`:
-
-```js title="src/routes/read/+page.server.ts"
-import {
-  getAllMessages,
-  getWelcomeMessage,
-} from "$lib/server/getLedgerEntries";
-import type { PageServerLoad } from "./$types";
-
-export const load: PageServerLoad = async () => {
-  return {
-    welcomeMessage: await getWelcomeMessage(),
-    messages: await getAllMessages(),
-  };
-};
-```
-
-Estamos haciendo uso de dos funciones que hemos definido en otro lugar. El `welcomeMessage` siempre tendrá la ID 1, y queremos _siempre_ mostrarlo en la parte superior de la página. Las dos funciones están definidas de esta manera:
-
-```js title="src/lib/server/getLedgerEntries.ts"
-
-import { rpc } from '$lib/passkeyClient';
-// notice our bindings re-exports the Stellar SDK, so we don't even really need
-// to import any Stellar-related classes or functions from elsewhere.
-import { Address, networks, Contract, type Message, xdr, scValToNative } from 'ye_olde_guestbook';
-
-// First, we need a function to build these LedgerKeys so we can query the network
-function buildMessageLedgerKey(messageId: number) {
-    const ledgerKey = xdr.LedgerKey.contractData(
-        new xdr.LedgerKeyContractData({
-            contract: new Address(networks.testnet.contractId).toScAddress(),
-            key: xdr.ScVal.scvVec([xdr.ScVal.scvSymbol('Message'), xdr.ScVal.scvU32(messageId)]),
-            durability: xdr.ContractDataDurability.persistent(),
-        }),
-    );
-
-    return ledgerKey;
-}
-
-// To get our welcome message, we use the `getLedgerEntries` function
-// from the RPC instance.
-export async function getWelcomeMessage(): Promise<Message> {
-    const result = await rpc.getLedgerEntries(buildMessageLedgerKey(1));
-    return scValToNative(result.entries[0].val.contractData().val());
-}
-
-// Our contract stores the number of guestbook messages in its instance
-// storage. So, we have a function to query exactly how many messages we
-// need to retrieve.
-export async function getMessageCount() {
-    const result = await rpc.getLedgerEntries(
-        new Contract(networks.testnet.contractId).getFootprint(),
-    );
-
-    const messageCount = result.entries[0].val
-        .contractData()
-        .val()
-        .instance()
-        .storage()
-        ?.filter((item) => item.val().switch().name === 'scvU32');
-
-    return messageCount![0].val().value() as number;
-}
-
-// Now we can iterate and make ledger key for each relevant message,
-// and add that to our getLedgerEntries query. The maximum number of ledger entries
-// to query is 200.
-export async function getAllMessages(): Promise<Message[]> {
-    const totalCount = await getMessageCount();
-    const ledgerKeysArray = [];
-    for (let messageId = 2; messageId <= totalCount; messageId++) {
-        ledgerKeysArray.push(buildMessageLedgerKey(messageId));
-    }
-
-    const result = await rpc.getLedgerEntries(...ledgerKeysArray);
-    const messages = result.entries.map((message) => {
-        return {
-            ...scValToNative(message.val.contractData().val()),
-        };
-    });
-
-    return messages;
-}
-```
-
-¿Captaste todo eso?! ¡Bien hecho! Esa es la parte de consulta para leer todos los mensajes. Ahora, para _mostrar_ esos mensajes, obtenemos esos datos en nuestra página de Svelte.
-
-```html title="src/routes/read/+page.svelte"
-<script lang="ts">
-  import { SlideToggle } from "@skeletonlabs/skeleton";
-  import GuestbookMessage from "$lib/components/GuestbookMessage.svelte";
-
-  import type { PageData } from "./$types";
-  export let data: PageData;
-
-  let sortNewestFirst = true;
-  let messages = data.messages;
-
-  $: if (sortNewestFirst) {
-    messages = messages.sort((a, b) => b.ledger - a.ledger);
-  } else {
-    messages = messages.sort((a, b) => a.ledger - b.ledger);
-  }
-</script>
-
-<div
-  class="flex flex-col md:flex-row justify-start md:justify-between space-y-4"
->
-  <div class="space-y-4">
-    <h1 class="h1">Read the Book</h1>
-    <p>Take a gander at all these messages!</p>
-  </div>
-  <div class="md:self-end">
-    <SlideToggle
-      name="sort"
-      bind:checked="{sortNewestFirst}"
-      active="bg-primary-500"
-      size="sm"
-      >Showing
-      <code class="code">{sortNewestFirst ? 'Newest' : 'Oldest'}</code>
-      First</SlideToggle
-    >
-  </div>
-</div>
-
-<GuestbookMessage message="{data.welcomeMessage}" messageId="{1}" />
-<hr class="!border-t-2" />
-
-{#each messages as message, i (message.ledger)}
-<GuestbookMessage {message} messageId="{i" + 2} />
-{/each}
-```
-
-Estamos cargando los datos que recuperamos del servidor. Incluso incluimos un pequeño interruptor de alternancia para que el usuario decida si desea ver las entradas más nuevas o más antiguas primero. Luego, es momento de mostrar los mensajes.
-
-De nuevo, usamos el componente `GuestbookMessage`. Mostramos una instancia del componente para cada entrada de mensaje.
-
-## Editar una entrada del libro de visitas
-
-Si echamos un breve vistazo dentro del [componente `GuestbookMessage`](https://github.com/ElliotFriend/ye-olde-guestbook/blob/main/src/lib/components/GuestbookMessage.svelte), podemos ver que tenemos algunos campos de formulario en caso de que el usuario quiera editar un mensaje. Limitamos la exhibición de estas partes del componente a casos donde la dirección de billetera inteligente del usuario _iniciado sesión_ `C...` coincida con el campo `author` de la entrada del libro de visitas.
-
-El HTML de la página está fuera de lo que necesitamos cubrir aquí, pero baste decir que cuando el usuario está editando una entrada, los campos de formulario se comportan bastante similar al formulario en la página de "firmar el libro de visitas". Las funciones son un poco más interesantes y más relevantes para este tutorial.
-
-:::tip
-
-El beneficio de incluir esta funcionalidad dentro del componente que muestra mensajes es que las funciones de edición pueden ser utilizadas donde sea que el usuario esté leyendo los mensajes. Ya sea que estén leyendo todas las entradas, o solo una sola entrada, si fueron el autor de un mensaje, estarán disponibles los botones de edición.
-
-:::
-
-```js title="src/lib/components/GuestbookMessage.svelte"
-import { account, send } from '$lib/passkeyClient';
-import { keyId } from '$lib/stores/keyId';
-
-// This is how we receive the "props" from the pages that instantiate this component
-export let message: Message;
-export let messageId: number;
-
-let editing: boolean;
-let isLoading: boolean;
-
-// Store the original values from the contract's storage. The form will be "bound"
-// to these values later on, when the user is modifying the entry.
-let messageTitle = message.title;
-let messageText = message.text;
-
-/**
- * If the user chooses to cancel the editing the message, we should revert the
- * message state back to the original values.
- */
-const cancelEdit = () => {
-    messageTitle = message.title;
-    messageText = message.text;
-    editing = false;
-};
-
-const submitEdit = async () => {
-    console.log('submitting message edit');
-    isLoading = true;
-    try {
-        const at = await ye_olde_guestbook.edit_message({
-            message_id: messageId,
-            title: messageTitle,
-            text: messageText,
-        });
-
-        const txn = await account.sign(at.built!, { keyId: $keyId });
-        await send(txn.built!);
-
-        toastStore.trigger({
-            message: 'Message edited successfully.',
-            background: 'variant-filled-success',
-        });
-    } catch (err) {
-        console.log(err);
-        toastStore.trigger({
-            message: 'Something went wrong editing your message. Please try again later.',
-            background: 'variant-filled-error',
-        });
-    } finally {
-        editing = false;
-        isLoading.set(false);
-    }
-};
-```
-
-Nota que, a diferencia de cuando firmamos el libro de visitas por primera vez, no tenemos que proporcionar un argumento `author`. El contrato inteligente está diseñado de tal manera que busca al autor (y requiere autenticación) _dentro_ de su propio almacenamiento. Esto asegura que el _autor original_ de una entrada en el libro de visitas es la **única** cuenta autorizada para realizar modificaciones.
-
-¡Ni siquiera nuestro amable anfitrión del libro de visitas podría modificar una entrada!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/overview.mdx
deleted file mode 100644
index b16fae3cab..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/overview.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: Resumen
-sidebar_position: 10
----
-
-¡En este tutorial, te guiaremos para crear un antiguo [libro de visitas de internet](https://en.wikipedia.org/wiki/Guestbook)! (Créeme, ¡todos estaban de moda en su momento!) Estaremos examinando cómo se construye el proyecto, comenzando con el contrato inteligente. Luego, convertiremos ese contrato inteligente desplegado en un "paquete de bindings", lo que nos permitirá integrarlo sin problemas en nuestro proyecto frontend. Para autenticar a nuestros usuarios, utilizaremos la nueva capacidad de claves de acceso de Stellar y daremos a cada uno de nuestros usuarios su propia billetera inteligente. ¡Como beneficio adicional, este libro de visitas es _ya_ un proyecto utilizable (en Testnet) con el que puedes experimentar y usar **ahora mismo**! Después de este tutorial, tendrás una comprensión sólida de cómo los contratos inteligentes y las aplicaciones web pueden trabajar juntos en armonía. También tendrás herramientas y ejemplos prácticos de cómo podrías integrar billeteras inteligentes impulsadas por claves de acceso en tus propios proyectos.
-
-Para este tutorial, caminaremos por los pasos mientras construimos una aplicación de muestra que hemos llamado [Ye](https://ye-olde-guestbook.vercel.app)[^1][ Olde Guestbook](https://ye-olde-guestbook.vercel.app), que se utilizará para mostrar varias funciones.
-
-:::caution
-
-Aunque Ye Olde Guestbook es una aplicación completamente funcional en el Testnet de Stellar, ha sido desarrollada únicamente para mostrar la funcionalidad de Stellar para el beneficio educativo de la comunidad de Stellar. No debe ser desplegada y utilizada en el Mainnet de Stellar.
-
-:::
-
-![El antiguo libro de visitas Dapp](/assets/guestbook/frontend.png)
-
-## Configuración del proyecto
-
-### Requisitos del proyecto
-
-Para crear esta aplicación de libro de visitas, necesitaremos varias piezas.
-
-- **Marco de aplicación:** estamos utilizando SvelteKit, optando por un proyecto que verifica tipos utilizando TypeScript. SvelteKit (y Svelte por sí solo) es un marco bastante capaz, y utilizaremos algunas de sus características en este proyecto. Sin embargo, no estaremos profundizando en esas áreas específicas de Svelte en este tutorial. El código fuente del proyecto está libre y disponible y cuenta con comentarios informativos decentes a lo largo, si deseas revisarlo para esos propósitos.
-- **Marco frontend:** Estamos utilizando [Skeleton](https://www.skeleton.dev/) para simplificar el uso de [Tailwind CSS](https://tailwindcss.com/).
-- **Una forma de interactuar con la red:** esta es una aplicación TypeScript, y estamos utilizando `@stellar/stellar-sdk` para esto. Podrías hacer solicitudes tradicionales `fetch` si quisieras, dependiendo de tus decisiones de despliegue. En cualquier caso, necesitaremos el SDK para interactuar con keypairs y transacciones. También estaremos utilizando un indexador de datos para acceder a eventos históricos de la red, y cubriremos más sobre esto en un punto posterior del tutorial.
-- **Una forma de interactuar con la cuenta de un usuario:** estamos prescindiendo de las billeteras tradicionales aquí, y utilizaremos `passkey-kit` para dar a nuestros usuarios una billetera inteligente con la que interactuar. Pueden interactuar con esta billetera inteligente (a través de passkey-kit) mediante métodos que ya conocen (huellas digitales, reconocimiento facial, etc.).
-
-:::note
-
-Si bien estamos utilizando los componentes anteriores para construir nuestra aplicación, hemos hecho nuestro mejor esfuerzo para redactar este tutorial de tal manera que la dependencia de cualquier cosa en particular se minimice. Preferiblemente, deberías poder usar el código TypeScript que hemos escrito y adaptarlo a cualquier otro marco que desees con un esfuerzo mínimo.
-
-:::
-
-Algunas decisiones que hemos tomado durante el curso del desarrollo:
-
-- Algunos de los componentes no relacionados con Stellar se inclinan un _poco más_ hacia la forma Svelte de hacer las cosas, pero hemos trabajado para que sea bastante fácil de traducir a React, Astro, etc.
-- Este proyecto está escrito de tal manera que un único despliegue de la aplicación interactúa con un único despliegue del contrato inteligente. Podría haberse escrito de manera diferente, pero no lo hemos hecho aquí por simplicidad.
-- Estamos implementando nuestro propio servicio de claves de acceso aquí. Eso significa que configuraremos y usaremos `passkey-kit` (tanto componentes del lado del cliente como del servidor) en nuestra propia dapp. A largo plazo, este puede no ser el patrón de uso necesario. Es probable que surjan servicios que actúen como una "fábrica de billeteras" que puedan crear billeteras inteligentes y facilitar la adición de firmantes para varias aplicaciones. ¿Quizás estos servicios serán proporcionados por billeteras existentes? ¿Quizás estos servicios serán desconocidos para el usuario (y tal vez incluso para los desarrolladores) en el futuro? ¡Quién sabe! ¡El cielo es el límite! (Pero eso no es así todavía, así que lo estamos haciendo nosotros mismos.)
-- It should be _relatively_ responsive, no promises, though
-- Hemos elegido un tema de Skeleton, así que se ve bien desde el principio.
-- Hay una mezcla de lógica del lado del cliente y del lado del servidor. Esto se debe a que necesitaremos mantener algunos credenciales de autenticación en secreto, y queremos evitar filtrar estos a el código orientado al usuario. Algunas de estas técnicas son un poco específicas de SvelteKit, pero al final debería ser comprensible.
-- Estamos desplegando en un proyecto gratuito de Vercel. Hemos tenido mucho éxito en desplegar proyectos de SvelteKit y Stellar fácil y rápidamente, y con muy poca configuración. Tu experiencia puede variar, pero este debería ser un buen punto de partida.
-- Es probable que la aplicación no sea tan eficiente como podría ser. Tampoco está optimizada como podría estarlo. Hemos intentado encapsular las varias funcionalidades de tal forma que tenga sentido para el desarrollador que lee la base de código, por lo que hay algo de duplicación de código y algunas cosas podrían hacerse de una manera "mejor".
-- Hacemos _algo_ de manejo de errores, pero no tanto como querrías para una aplicación del mundo real. Si algo parece que no está funcionando, y no estás viendo un error, abre tu consola de desarrollador y puede que logres averiguar qué ha salido mal.
-- No hemos implementado _ninguna_ prueba automatizada. Probablemente querrás algunas para tu aplicación.
-
-:::note
-
-Este tutorial probablemente sea mejor visto como "_casi_ completo." No vamos a guiarte a través de cada uno de los archivos en nuestra base de código, y los archivos que utilizamos para ilustrar conceptos en el tutorial pueden no estar _totalmente_ presentes o explicados. Sin embargo, cubriremos lo básico y te señalaremos ejemplos más completos en la base de código cuando sea aplicable.
-
-:::
-
-### Ayudantes de desarrollador
-
-- [Passkey Kit](https://github.com/kalepail/passkey-kit): Un SDK de TypeScript para crear y gestionar billeteras inteligentes de Stellar.
-- [Launchtube](https://launchtube.xyz): Similar a un [Paymaster](https://eips.ethereum.org/EIPS/eip-4337#extension-paymasters) en el mundo de EVM, el servicio de Launchtube tiene como objetivo aliviar todos los desafíos y complejidades de obtener una transacción en-chain al darte una API que acepta operaciones de Soroban y luego maneja la presentación exitosa de esas entradas a la red.
-- [Stellar Lab](https://lab.stellar.org): Un laboratorio experimental para interactuar con la red Stellar.
-
-## Comenzar
-
-Estos son los pasos que hemos tomado para comenzar a construir Ye Olde Guestbook. Siéntete libre de inspirarte y personalizar estas direcciones como mejor te parezca. Toda la [base de código de Ye Olde Guestbook](https://github.com/elliotfriend/ye-olde-guestbook) está libre y disponible en GitHub para referencia.
-
-### Comienza desde el repositorio soroban-template
-
-Con el cambio hacia el desarrollo de contratos inteligentes, una utilidad que está surgiendo en el ecosistema Stellar es la "[plantilla Soroban](../../guides/dapps/soroban-contract-init-template.mdx)." Estos templates pueden ayudar a aliviar la carga de escribir código base, y pueden ayudar a adaptar flujos de trabajo típicos de desarrollo de Stellar en templates de referencia específicos de marco. Hemos creado [justo tal template](https://github.com/ElliotFriend/soroban-template-sveltekit-passkeys) que puede ayudarte a comenzar a desarrollar con SvelteKit y claves de acceso desde el principio. Puedes utilizar el template en el sitio web de GitHub:
-
-![Proyecto de plantilla de GitHub](/assets/guestbook/github_template.png)
-
-O, puedes (hacer un fork y) clonar el repositorio del template localmente, y empezar a trabajar de esa manera:
-
-```shell
-git clone https://github.com/ElliotFriend/soroban-template-sveltekit-passkeys ye-olde-guestbook
-```
-
-Este template frontend te dará una estructura y algunos valores predeterminados (opinionados). ¡Lo que hagas a partir de ahí depende de ti!
-
-Este template te dará varias cosas para ayudarte a empezar rápidamente:
-
-- un directorio `/contracts` inicial con un contrato `hello_world` en él,
-- un conjunto preconfigurado de dependencias y paquetes, incluyendo el paquete de bindings `hello_world`,
-- lógica y ayudas de claves de acceso ya escritas de fábrica,
-- un script de inicialización para desplegar contratos y generar bindings para ellos, y
-- tendrás un sitio de SvelteKit listo para personalizar, escrito en TypeScript.
-
-¿Qué más podrías querer!?
-
-### Configura el archivo `.env`
-
-El template viene con un archivo `.env.example`, que necesitarás modificar. Primero, copia o mueve este archivo a `.env`:
-
-```shell
-cp .env.example .env
-```
-
-Luego, abre el archivo `.env`, y comienza a personalizar cualquiera de las entradas que necesites. Si planeas ejecutar en Testnet (y _deberías_ empezar allí), la mayoría de las variables serán adecuadas tal como están.
-
-Algunas variables que querrás cambiar incluyen:
-
-```shell
-PUBLIC_STELLAR_ACCOUNT=stroopy # you're welcome to use stroopy, but if you have an name you'd prefer, put that here
-PRIVATE_FUNDER_SECRET_KEY=S...ECRET # fund an account on Testnet and put the secret key here
-PUBLIC_FUNDER_PUBLIC_KEY=G...ADDRESS # put the public key from the funded account here
-```
-
-### Instalar dependencias
-
-Con nuestro template preexistente, todo lo que necesitas se debe extraer de los archivos `package.json` y `Cargo.toml`. Todo lo que tienes que hacer es abrir una terminal e instalar las dependencias:
-
-```bash
-pnpm install
-```
-
-:::note
-
-No estamos tratando de dictar qué gestor de paquetes deberías usar. Al construir una aplicación SvelteKit de pila completa usando Stellar y claves de acceso, hemos visto recientemente mucho éxito y confiabilidad usando `pnpm`. ¿Quién puede decir _por qué_ es así?, y puede que seguramente sea un golpe de suerte y limitado a nuestra propia experiencia. En cualquier caso, estaremos usando `pnpm` para el resto de este tutorial.
-
-:::
-
-A continuación, veamos el contrato inteligente que está en el corazón del proyecto.
-
-## Notas
-
-[^1]: Dato curioso: El carácter "Y" en la palabra "Ye" se usaba comúnmente en los períodos de inglés antiguo y medio, y representaba la [letra Thorn](https://en.wikipedia.org/wiki/Thorn_(letter)), que ya no forma parte del alfabeto inglés moderno. En realidad, _no_ se pronunciaba de la manera en que decimos la letra moderna "y", sino que se vocalizaba como el dígrafo "th." Así que, hace 500 años, habrías pronunciado "Ye" exactamente de la misma manera en que pronuncias "the" hoy en día. ¡Loco, ¿verdad!?
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/passkeys-prerequisites.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/passkeys-prerequisites.mdx
deleted file mode 100644
index 315a8a10f0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/passkeys-prerequisites.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: Requisitos previos de las claves de paso
-sidebar_position: 40
----
-
-Las claves de paso son una forma asombrosa de ayudar a los desarrolladores de dapps (como tú) a conectar a los usuarios con sus proyectos, protocolos, aplicaciones, etc. Aprende más en la [guía de billeteras con clave de acceso](../../guides/contract-accounts/smart-wallets.mdx).
-
-Hemos estado trabajando arduamente en algunas herramientas para aumentar la adopción y la facilidad de uso de las claves de paso en Stellar. Para este tutorial, utilizaremos el **increíble** [`paquete passkey-kit`](https://github.com/kalepail/passkey-kit), que elimina MUCHO del dolor de cabeza y las complicaciones de la situación.
-
-Antes de entrar en los detalles sobre las claves de paso, tenemos algunas tareas que hacer. Primero, configuraremos Launchtube, un servicio que ayudará a poner nuestras transacciones en la cadena sin preocuparnos por las tarifas de gas, los números de secuencia o las cuentas de origen. Realmente útil. Luego, crearemos un programa de indexación de Mercury, que se utilizará para realizar un seguimiento de la mitad de la clave pública de una clave de paso generada por el usuario y luego hacer una búsqueda inversa para ver a qué dirección de billetera inteligente se ha agregado la clave de paso.
-
-## Launchtube
-
-Comencemos con [Launchtube](https://launchtube.xyz). Como mencionamos antes, Launchtube es similar a un servicio de "pagador", si te familiarizas con la abstracción de cuentas en las redes EVM. En realidad, no necesitaremos interactuar con Launchtube _directamente_. Todo eso será manejado por el paquete `passkey-kit`. Sin embargo, necesitaremos obtener un token JWT que nos permitirá autenticar nuestra dapp con Launchtube.
-
-Para los tokens de Launchtube en Testnet, podemos generar uno en cualquier momento que queramos. Todo lo que tienes que hacer es visitar `https://testnet.launchtube.xyz/gen` para recibir un token JWT que será válido durante tres meses y tendrá 100 XLM en créditos (estos créditos se consumirán cuando envíes transacciones de red a través de Launchtube). Go ahead, [give it a try](https://testnet.launchtube.xyz/gen)!
-
-:::tip
-
-¡Tenemos tokens de Launchtube en Mainnet disponibles! Puedes solicitar un token en el [`canal #launchtube`](https://discord.com/channels/897514728459468821/1293204627361108141) en nuestro [servidor de Discord de desarrolladores de Stellar](https://discord.gg/stellardev). En particular, hacer ping a `@kalepail`, `@ElliotFriend` o `@carsten.xlm` debería ayudarte a comenzar bastante rápido.
-
-:::
-
-Una vez que tengas tu token de Launchtube, cópialo y pégalo en el archivo `.env`, como la variable `PRIVATE_LAUNCHTUBE_JWT`:
-
-```shell
-PRIVATE_LAUNCHTUBE_JWT=<insert_your_launchtube_jwt_here>
-```
-
-:::info
-
-Las variables de entorno `PRIVATE_` y `PUBLIC_` son una convención de SvelteKit, que nos permite acceder a estas variables en los lugares apropiados a lo largo de nuestro código utilizando los módulos [`$env/static/private`](https://svelte.dev/docs/kit/$env-static-private) y [`$env/static/public`](https://svelte.dev/docs/kit/$env-static-public), respectivamente.
-
-:::
-
-## Mercury
-
-Ahora, pasemos a [Mercury](https://www.mercurydata.app/). Este es un indexador de datos, que funciona tanto en Testnet como en Mainnet. El equipo está desarrollando algunas herramientas de datos de punta que están comenzando a redefinir lo que es posible con los datos de red. Un desarrollo de este tipo es el [ZephyrVM](https://docs.mercurydata.app/zephyr-full-customization/introduction): el entorno de ejecución en la nube de Mercury. En resumen, Zephyr te permite escribir programas (Rust) que se ejecutarán al cierre de _cada_ ledger en la red Stellar. Dentro de ese programa, puedes acceder a cualquier tipo de dato actual o pasado, interactuar con servicios web externos, crear funciones sin servidor y poblar bases de datos. Al igual que con Launchtube, no interactuaremos _directamente_ con Mercury dentro de la dapp Ye Olde Guestbook. Esas interacciones serán manejadas por el paquete `passkey-kit`. También, similar a Launchtube, este requiere una configuración.
-
-El paquete `passkey-kit` no "viene" con un programa de Zephyr en el paquete publicado, pero _tiene_ toda la funcionalidad de Zephyr que necesitarás en el repositorio fuente. Aquí te explico cómo hacer que ese programa Zephyr esté en funcionamiento en Mercury para que puedas acceder a los eventos de billetera inteligente indexados. Por cierto, es probable que estos comandos funcionen mejor _fuera_ del directorio donde estás construyendo tu dapp de libro de visitas.
-
-1. Clona el repositorio `passkey-kit` de GitHub y entra en el directorio `zephyr` dentro de él:
-
-   ```shell
-   git clone https://github.com/kalepail/passkey-kit
-   cd passkey-kit/zephyr
-   ```
-
-2. Obtén un token de autenticación desde la página web de Mercury. Puedes iniciar sesión en el [panel de Testnet](https://test.mercurydata.app/) aquí. Haz clic en el botón **Obtener token de acceso** en la sección "Suscripciones activas". Se te proporcionará un JWT que será válido durante los próximos siete días.
-
-   ![Token JWT de Mercury Data](/assets/guestbook/mercury_token.png)
-
-   Copia/pega este token en el archivo `.env`:
-
-   ```shell
-   PRIVATE_MERCURY_JWT=<insert_your_mercury_jwt_here>
-   ```
-
-3. (Opcionalmente) Puedes obtener un [token de autenticación de larga duración](https://docs.mercurydata.app/get-started-with-mercury/authentication) para tu cuenta usando este token y haciendo una solicitud a la API de Mercury:
-
-   ```shell
-   curl -X POST https://api.mercurydata.app/v2/key \
-       -H "authorization: Bearer <insert_your_mercury_jwt_here>
-   ```
-
-   Esto te dará una clave API que también puede ser añadida a tu archivo `.env`. El beneficio de esta clave API es que no caducará hasta que generes otra clave API.
-
-   :::info
-
-   Para este tutorial, solo necesitas una de estas. Puedes especificar el JWT **o** la clave API, y hacer que todo funcione exactamente igual. En el `PasskeyServer`, sin embargo, asegúrate de especificar el valor correspondiente.
-
-   :::
-
-4. Compila y despliega el programa de indexador de eventos Zephyr en la red de Testnet.
-
-   ```shell
-   cargo install mercury-cli
-   export MERCURY_JWT="<insert_your_mercury_jwt_here>"
-   # Make sure you're using Rust version 1.79.0 or newer
-   mercury-cli --jwt $MERCURY_JWT --local false --mainnet false deploy
-   ```
-
-Si todo sale bien, ¡estás listo para continuar! ¡Bien hecho!
-
-¡Ahora estás listo para sumergirte en la implementación real de claves de paso y autenticar a tus usuarios con la dapp del libro de visitas! ¡Vamos a hacerlo!
-
-## Resolución de problemas
-
-Es posible que algo haya salido mal durante la ejecución de los procesos anteriores. Aquí hay algunas sugerencias generales de correcciones o cosas que puedes intentar si algo sale mal con tu uso de Launchtube o Mercury:
-
-1. **Genera un nuevo token de Launchtube.** Es posible que el token de Launchtube que estás utilizando haya agotado los créditos. Dado que estamos utilizando Testnet para este tutorial, no hay problema en generar un token completamente nuevo en cualquier momento visitando `https://testnet.launchtube.xyz/gen` en tu navegador.
-2. **Asegúrate de que tu programa de Zephyr se haya desplegado exitosamente.** He estado atascado más de una vez con una solicitud de Mercury que no funcionaba porque el programa de Zephyr no se había desplegado exitosamente. Asegúrate de que la salida del comando `mercury-cli deploy` no tenga errores.
-3. **Revisa la [documentación de Mercury](https://docs.mercurydata.app/).** Es bastante buena y puede ayudarte a superar muchos de los obstáculos que podrías enfrentar.
-
-En cualquier caso, siéntete libre de hacer preguntas o iniciar un chat en los canales [`#passkeys`](https://discord.com/channels/897514728459468821/1250851135561142423) y [`#launchtube`](https://discord.com/channels/897514728459468821/1293204627361108141) en el servidor de Discord de desarrolladores de Stellar. ¡Generalmente hay alguien disponible que está listo y dispuesto a ayudar!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/setup-passkeys.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/setup-passkeys.mdx
deleted file mode 100644
index 4666f9f438..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/setup-passkeys.mdx
+++ /dev/null
@@ -1,253 +0,0 @@
----
-title: Configurar Claves de Acceso
-sidebar_position: 50
----
-
-Ahora que tenemos las cuentas, tokens, etc. requeridos creados, ¡estamos listos para empezar a poner a trabajar el `passkey-kit`, conectando a nuestros usuarios!
-
-## Cliente de Clave de Acceso
-
-Empezaremos creando una instancia de la clase `PasskeyKit`. La llamaremos `cuenta`, y esta `cuenta` será el **punto** de interacción **principal** para la dapp y la clave de acceso del usuario. Cada transacción se firmará usando `account.sign()`, los usuarios se registrarán con `account.createWallet()`, los usuarios iniciarán sesión con `account.connectWallet()`. ¡Esta `cuenta` es una verdadera máquina de trabajo! Hagámoslo realidad.
-
-Estamos creando esto en `src/lib/passkeyClient.ts` para que esté disponible en el resto de nuestro código de frontend. El [alias de importación `$lib`](https://svelte.dev/docs/kit/$lib) es algo de SvelteKit, pero lo importante es que queremos que este archivo (y sus exportaciones) estén disponibles en **todos** nuestros archivos de frontend. Cómo hacer que eso funcione para otros frameworks es un ejercicio que dejo al lector.
-
-```js title="src/lib/passkeyClient.ts"
-import { PasskeyKit } from "passkey-kit";
-import {
-  PUBLIC_STELLAR_RPC_URL,
-  PUBLIC_STELLAR_NETWORK_PASSPHRASE,
-  PUBLIC_WALLET_WASM_HASH,
-} from "$env/static/public";
-
-export const account = new PasskeyKit({
-  rpcUrl: PUBLIC_STELLAR_RPC_URL,
-  networkPassphrase: PUBLIC_STELLAR_NETWORK_PASSPHRASE,
-  walletWasmHash: PUBLIC_WALLET_WASM_HASH,
-});
-```
-
-La variable `PUBLIC_WALLET_WASM_HASH` es el hash Wasm del código del contrato de la billetera inteligente. Este hash Wasm identifica el código ejecutable que se desplegará para nuevas billeteras inteligentes y es simplemente el hash Sha256 del archivo ejecutable compilado del contrato. Este hash se devuelve durante la instalación de un contrato compilado en la red.
-
-¡Eso es todo lo que hay al respecto! ¡Esta `cuenta` estará completamente lista para autenticar usuarios y firmar transacciones! (¡Es incluso más fácil que todos los requisitos previos, ¿verdad?!)
-
-Ahora, también hemos añadido algunos "ayudantes" útiles en el archivo `$lib/passkeyClient.ts` en nuestra plantilla. El [archivo de código fuente](https://github.com/ElliotFriend/soroban-template-sveltekit-passkeys/blob/main/src/lib/passkeyClient.ts) está comentado para reflejar qué son estos ayudantes y cómo funcionan. Sin embargo, son estrictamente por conveniencia. Podrías detenerte aquí y salir con transacciones de claves de acceso firmadas perfectamente válidas. Estos ayudantes son:
-
-- Una instancia configurada de la clase `rpc.Server` para que podamos realizar solicitudes RPC sin tener que conocer/importar la URL del RPC todo el tiempo.
-
-  ```js title="src/lib/passkeyClient.ts"
-  import { Server } from "@stellar/stellar-sdk/rpc";
-
-  /**
-   * A configured Stellar RPC server instance used to interact with the network
-   */
-  export const rpc = new Server(PUBLIC_STELLAR_RPC_URL);
-  ```
-
-- Un cliente SAC para interactuar con el contrato nativo de activos XLM. Estamos haciendo la suposición de que los lumens nativos son una interacción de activos "suficientemente buena" para hacer funcionar el tutorial, y para jugar en Testnet. Podrías exportar fácilmente _otro_ cliente SAC para interactuar con USDC, por ejemplo. La dirección del contrato nativo se puede obtener con Stellar-CLI usando el comando `stellar contract id asset --asset native`.
-
-  ```js title="src/lib/passkeyClient.ts"
-  import { SACClient } from "passkey-kit";
-  import { PUBLIC_NATIVE_CONTRACT_ADDRESS } from "$env/static/public";
-
-  /**
-   * A client allowing us to easily create SAC clients for any asset on the
-   * network.
-   */
-  const sac = new SACClient({
-    rpcUrl: PUBLIC_STELLAR_RPC_URL,
-    networkPassphrase: PUBLIC_STELLAR_NETWORK_PASSPHRASE,
-  });
-
-  /**
-   * A SAC client for the native XLM asset.
-   */
-  export const native = sac.getSACClient(PUBLIC_NATIVE_CONTRACT_ADDRESS);
-  ```
-
-## Servidor de Clave de Acceso
-
-Así que eso es el código de clave de acceso del lado del cliente (y algunos ayudantes) tratado. ¿Qué sucede con el lado del servidor, donde queremos tener cuidado de no filtrar secretos y tokens?!
-
-Estamos configurando esto en `src/lib/server/passkeyServer.ts`, por razones similares a las que enumeramos anteriormente. Esto nos da una instancia de `servidor` importable que se puede acceder y utilizar en otra lógica del lado del servidor. Svelte nos brinda el beneficio adicional de [mantener el código en este directorio seguro](https://svelte.dev/docs/kit/server-only-modules#Your-modules). Cuando queremos proteger credenciales y secretos, podemos colocar cualquier código sensible en el directorio `$lib/server`.
-
-```js title="src/lib/server/passkeyServer.ts"
-import { PasskeyServer } from "passkey-kit";
-
-import {
-  PUBLIC_LAUNCHTUBE_URL,
-  PUBLIC_MERCURY_URL,
-  PUBLIC_STELLAR_RPC_URL,
-} from "$env/static/public";
-import {
-  PRIVATE_LAUNCHTUBE_JWT,
-  PRIVATE_MERCURY_JWT,
-} from "$env/static/private";
-
-export const server = new PasskeyServer({
-  rpcUrl: PUBLIC_STELLAR_RPC_URL,
-  launchtubeUrl: PUBLIC_LAUNCHTUBE_URL,
-  launchtubeJwt: PRIVATE_LAUNCHTUBE_JWT,
-  mercuryUrl: PUBLIC_MERCURY_URL,
-  mercuryJwt: PRIVATE_MERCURY_JWT,
-  // mercuryKey: PRIVATE_MERCURY_KEY, // optionally
-});
-```
-
-¡Y has terminado con el `PasskeyServer`! ¡Bien hecho!
-
-Esta instancia de `servidor` se utilizará para enviar transacciones (a través de Launchtube) y buscar direcciones de contratos a partir de un ID de clave de acceso conocido (a través de Mercury).
-
-### Rutas de API
-
-Ahora, necesitaremos una forma de utilizar algunas de las funcionalidades de este `servidor` desde el cliente sin exponer ninguna de la información sensible. Para eso, configuraremos una colección de rutas (SvelteKit) para actuar como un backend, y _esas rutas_ (no el código del lado del cliente) utilizarán la instancia de `servidor`. Estos archivos viven en `src/routes/api/*` en el repositorio del proyecto.
-
-Algunas de las estructuras aquí son un poco específicas de Svelte, pero deberían ser bastante fáciles de entender para los desarrolladores que no son de Svelte de todos modos. La única cosa específica de SvelteKit que hay que tener en cuenta es que cualquier archivo llamado `*server.{ts,svelte}` **solo** se ejecutará [en el servidor](https://svelte.dev/docs/kit/routing#server). Tus secretos, tokens, credenciales, etc. se consideran seguros para usar dentro de estos archivos.
-
-#### `/api/send`
-
-Este endpoint de API enviará una transacción a la red, a través de Launchtube. Recibe una solicitud `POST`, cuyo objeto `body` contiene una transacción codificada en base64.
-
-:::warning
-
-Si estás creando un método `yourdomain.com/api/send`, probablemente necesitarás hacer "algo" para asegurarte de que solamente los "tipos" correctos de transacciones se envíen realmente a la red. Es decir, asegúrate de que provenga de tu dapp, de tus usuarios, etc. De lo contrario, sería posible que un actor malintencionado descubriera que podría usar esto para enviar sus propias transacciones, ¡mientras tú pagas el costo de las tarifas!
-
-La implementación de esto está fuera del alcance de este tutorial, pero asegúrate de considerar este tipo de riesgos mientras te preparas para un despliegue de nivel de producción.
-
-:::
-
-```js title="src/routes/api/send/+server.ts"
-import { server } from "$lib/server/passkeyServer";
-import { json } from "@sveltejs/kit";
-import type { RequestHandler } from "./$types";
-
-export const POST: RequestHandler = async ({ request }) => {
-  const { xdr } = await request.json();
-  const res = await server.send(xdr);
-  return json(res);
-};
-```
-
-#### `/api/contract/[signer]`
-
-Este endpoint buscará en reversa (a través de Mercury) una dirección de contrato dada una ID de clave de acceso. El parámetro de ruta `[signer]` es cómo le daremos la ID de clave de acceso a la solicitud de API `GET`.
-
-```js title="src/routes/api/contract/\[signer]/+server.ts"
-
-import { server } from '$lib/server/passkeyServer';
-import type { RequestHandler } from './$types';
-
-export const GET: RequestHandler = async ({ params }) => {
-    const contractId = await server.getContractId(params.signer!);
-
-    return new Response(String(contractId));
-};
-```
-
-#### `/api/fund/[address]`
-
-¡Este es otro ayudante, pero del lado de la API! [Friendbot](../../../networks/README.mdx#friendbot) no admite direcciones `C...` para la financiación de Testnet. Así que, estamos configurando un endpoint para poder añadir algunos fondos a las billeteras de los usuarios de la dapp. Esto les da algunos tokens para jugar, y nos permite _a nosotros_ recibir esas donaciones del libro de visitas!
-
-Este endpoint de API no es estrictamente necesario. Pero, es una forma útil de ver cómo este tipo de interacciones pueden ocurrir entre una dirección `G...` "regular" y una dirección de contrato soroban `C...`.
-
-```js title="src/routes/api/fund/\[address]/+server.ts"
-
-import { error, json } from '@sveltejs/kit';
-import { PRIVATE_FUNDER_SECRET_KEY } from '$env/static/private';
-import { native } from '$lib/passkeyClient';
-import type { RequestHandler } from './$types';
-import { Keypair } from '@stellar/stellar-sdk';
-import { basicNodeSigner } from '@stellar/stellar-sdk/contract';
-import { PUBLIC_STELLAR_NETWORK_PASSPHRASE } from '$env/static/public';
-
-export const GET: RequestHandler = async ({ params, fetch }) => {
-    const fundKeypair = Keypair.fromSecret(PRIVATE_FUNDER_SECRET_KEY);
-    const fundSigner = basicNodeSigner(fundKeypair, PUBLIC_STELLAR_NETWORK_PASSPHRASE);
-
-    try {
-        const { built, ...transfer } = await native.transfer({
-            from: fundKeypair.publicKey(),
-            to: params.address,
-            amount: BigInt(25 * 10_000_000),
-        });
-
-        await transfer.signAuthEntries({
-            publicKey: fundKeypair.publicKey(),
-            signAuthEntry: (auth) => fundSigner.signAuthEntry(auth),
-        });
-
-        await fetch('/api/send', {
-            method: 'POST',
-            body: JSON.stringify({
-                xdr: built!.toXDR(),
-            }),
-        });
-
-        return json({
-            status: 200,
-            message: 'Smart wallet successfully funded',
-        });
-    } catch (err) {
-        console.error(err);
-        error(500, {
-            message: 'Error when funding smart wallet',
-        });
-    }
-};
-```
-
-### Ayudantes del Cliente de Clave de Acceso
-
-Cada uno de esos endpoints de API recibe una función correspondiente en el archivo `$lib/passkeyClient.ts`, solo para facilitar un poco más del lado del cliente el uso de las rutas de API que acabamos de crear.
-
-Esto nos permite escribir el código `fetch` una vez y usarlo consistentemente en todas partes. Son bastante sencillos y realmente no necesitan mucha explicación. Los añadiremos al final del archivo:
-
-```js title="src/lib/passkeyClient.ts"
-/**
- * A wrapper function so it's easier for our client-side code to access the
- * `/api/send` endpoint we have created.
- *
- * @param xdr - The base64-encoded, signed transaction. This transaction
- * **must** contain a Soroban operation
- * @returns JSON object containing the RPC's response
- */
-export async function send(xdr: string) {
-  return fetch("/api/send", {
-    method: "POST",
-    body: JSON.stringify({
-      xdr,
-    }),
-  }).then(async (res) => {
-    if (res.ok) return res.json();
-    else throw await res.text();
-  });
-}
-
-/**
- * A wrapper function so it's easier for our client-side code to access the
- * `/api/contract/[signer]` endpoint we have created.
- *
- * @param signer - The passkey ID we want to find an associated smart wallet for
- * @returns The contract address to which the specified signer has been added
- */
-export async function getContractId(signer: string) {
-  return fetch(`/api/contract/${signer}`).then(async (res) => {
-    if (res.ok) return res.text();
-    else throw await res.text();
-  });
-}
-
-/**
- * A wrapper function so it's easier for our client-side code to access the
- * `/api/fund/[address]` endpoint we have created.
- *
- * @param address - The contract address to fund on the Testnet
- */
-export async function fundContract(address: string) {
-  return fetch(`/api/fund/${address}`).then(async (res) => {
-    if (res.ok) return res.json();
-    else throw await res.text();
-  });
-}
-```
-
-¿Sigues con nosotros?! ¡Increíble! ¡Eres una estrella de rock! ¡Y estás listo para entrar en las interacciones con el contrato inteligente! ¡Nos vemos en la próxima página!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/smart-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/smart-contract.mdx
deleted file mode 100644
index 726ce7522a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/guestbook/smart-contract.mdx
+++ /dev/null
@@ -1,381 +0,0 @@
----
-title: El contrato del libro de visitas
-sidebar_position: 20
----
-
-El corazón de este proyecto comienza con nuestro contrato inteligente. Este contrato inteligente actuará, en esencia, como una base de datos para nuestros mensajes de libro de visitas. Los usuarios podrán escribir mensajes, leerlos y editar su(s) propios mensajes enviados anteriormente. Además, el contrato será actualizable y requerirá inicialización.
-
-## Funcionalidad requerida
-
-Toda la "lógica de negocio" siguiente será manejada por nuestro contrato inteligente:
-
-- **Un medio para escribir mensajes.** Los usuarios pueden invocar esta función para dejar un mensaje para el responsable del sitio. Tendrán que autenticar esta función, y debe contener un campo `title` y un campo `text` (ambos cadenas). La función devolverá el número de ID del mensaje, que se incrementa secuencialmente.
-- **Un medio para leer mensajes.** Esta función permitirá a un usuario "consultar" el contrato por un mensaje del libro de visitas, proporcionando el ID del mensaje. IDs que no existen resultarán en un error.
-- **Un medio para editar mensajes (con autenticación).** Si un usuario necesita modificar su mensaje escrito anteriormente, puede utilizar esta función para hacerlo. Deben proporcionar la autorización adecuada para hacerlo, y deben proporcionar ya sea un campo `title` o un campo `text` (no pueden estar ambos vacíos, pero uno de ellos podría).
-- **Un medio para recuperar donaciones y transferirlas a la dirección "admin".** La arrogancia asociada con solicitar donaciones en un sitio como este dice mucho del sentido de sí mismo del mantenedor. Sin embargo, proporcionar esta funcionalidad es un excelente ejercicio en interacciones de activos dentro del contrato inteligente.
-- También necesitaremos algunas funciones utilitarias que el contrato utilizará internamente, así como un `__constructor` y una función `upgrade`, en caso de que necesitemos actualizar nuestro contrato inteligente en el futuro.
-
-:::note
-
-Profundizaremos en cada una de las funciones principales a continuación, pero si deseas ver el contrato inteligente completo sin interrupciones, se puede encontrar aquí: [https://github.com/ElliotFriend/ye-olde-guestbook/blob/main/contracts/ye_olde_guestbook/src/lib.rs](https://github.com/ElliotFriend/ye-olde-guestbook/blob/main/contracts/ye_olde_guestbook/src/lib.rs)
-
-:::
-
-## Cómo funciona
-
-### Funciones del contrato
-
-#### `__constructor`
-
-Con la publicación y la votación exitosa de validadores del Protocolo 22, ¡los contratos inteligentes ahora pueden utilizar una función `__constructor`! Anteriormente, cualquier inicialización de un contrato inteligente tenía que hacerse en una invocación posterior del contrato tras la acción de `deploy`. Ahora, es posible realizar esa inicialización en el momento del despliegue. Esto previene el front-running y mantiene el contrato que has desplegado siempre bajo tu control.
-
-Las funciones del constructor _lucen_ prácticamente igual que las funciones `init` utilizadas anteriormente. La única diferencia es _cuándo_ se ejecuta la función.
-
-```rust
-/// Initializes the guestbook with a warm welcome message for prospective
-/// signers to read.
-///
-/// # Arguments
-///
-/// * `admin` - The address which will be the owner and administrator of the
-///   guestbook.
-/// * `title` - The title or subject of the welcome message.
-/// * `text` - The body or contents of the welcome message.
-///
-/// # Panics
-///
-/// * If the `title` argument is empty or missing.
-/// * If the `text` argument is empty or missing.
-pub fn __constructor(
-    env: Env,
-    admin: Address,
-    title: String,
-    text: String,
-) -> Result<(), Error> {
-    check_string_not_empty(&env, &title);
-    check_string_not_empty(&env, &text);
-
-    admin.require_auth();
-    env.storage().instance().set(&DataKey::Admin, &admin);
-
-    let first_message = Message {
-        author: admin,
-        ledger: env.ledger().sequence(),
-        title,
-        text,
-    };
-
-    save_message(&env, first_message);
-    Ok(())
-}
-```
-
-#### `write_message`
-
-Primero lo primero, necesitamos una función que permita que un mensaje sea escrito en el libro de visitas. Se crea una estructura simple y se almacena en el almacenamiento persistente del contrato. Esta es una función bastante simple que toma tres piezas de datos de la invocación (`author`, `title` y `text`) y luego crea una estructura para almacenar en las entradas de almacenamiento persistente del contrato. Aquí hay algunas cosas a tener en cuenta:
-
-- Estamos utilizando una función auxiliar llamada `check_string_not_empty` para asegurar que se haya pasado un valor no vacío tanto para los argumentos `title` como `text`. Más sobre esta función más adelante.
-- Estamos requiriendo autenticación de la dirección del autor, para asegurar que han autorizado la entrada del mensaje a asociarse con ellos.
-- Estamos utilizando una función utilitaria `save_message` para hacer la lectura/escritura de la entrada de almacenamiento. Más sobre los detalles de esta función [más adelante](#save_message), pero por ahora solo debes saber que está almacenando la estructura `new_message` y devolviendo el ID del mensaje almacenado.
-
-```rust
-/// Write a message to the guestbook.
-///
-/// # Arguments
-///
-/// * `author` - The sender of the message.
-/// * `title` - The title or subject of the guestbook message.
-/// * `text` - The body or contents of the guestbook message.
-///
-/// # Panics
-///
-/// * If the `title` argument is empty or missing.
-/// * If the `text` argument is empty or missing.
-pub fn write_message(
-    env: Env,
-    author: Address,
-    title: String,
-    text: String,
-) -> Result<u32, Error> {
-    check_string_not_empty(&env, &title);
-    check_string_not_empty(&env, &text);
-    author.require_auth();
-
-    let new_message = Message {
-        author,
-        ledger: env.ledger().sequence(),
-        title,
-        text,
-    };
-
-    let message_id = save_message(&env, new_message);
-    return Ok(message_id);
-}
-```
-
-#### `edit_message`
-
-También haremos posible que un usuario edite un mensaje que ya ha sido escrito. En el caso de que solo se necesiten cambiar el `text` o el `title`, permitiremos pasar cadenas vacías como argumentos aquí. Sin embargo, aseguraremos que _ambos_ no estén vacíos. Estamos utilizando una función utilitaria `get_message` aquí para leer los datos de las entradas de almacenamiento del contrato. Recuperar un mensaje es relativamente común en este contrato, por lo que hemos creado una utilidad para minimizar el código duplicado.
-
-Modificamos el mensaje al:
-
-- recuperarlo del almacenamiento (en una variable mutable),
-- asignar los campos de la estructura al valor editado (o al original si un argumento está vacío), y
-- actualizar el número de ledger del mensaje al valor del ledger actual.
-
-Es importante notar que _no_ estamos requiriendo autenticación de un argumento `Address` pasado. En su lugar, recuperamos primero la estructura del mensaje y requerimos autenticación del autor almacenado.
-
-El proceso de guardar este objeto de mensaje editado es bastante similar a la función `write_message`, excepto que no estamos modificando el `MessageCount`, ya que solo estamos _modificando_ y no _agregando_ un mensaje.
-
-```rust
-/// Edit a specified message in the guestbook.
-///
-/// # Arguments
-///
-/// * `message_id` - The ID number of the message to edit.
-/// * `title` - The title or subject of the guestbook message.
-/// * `text` - The body or contents of the guestbook message.
-///
-/// # Panics
-///
-/// * If both the `title` AND `text` arguments are empty or missing.
-/// * If there is no authorization from the original message author.
-pub fn edit_message(
-    env: Env,
-    message_id: u32,
-    title: String,
-    text: String,
-) -> Result<(), Error> {
-    if title.is_empty() {
-        check_string_not_empty(&env, &text);
-    }
-
-    if text.is_empty() {
-        check_string_not_empty(&env, &title);
-    }
-
-    let mut message = get_message(&env, message_id);
-    message.author.require_auth();
-
-    let edited_title = if title.is_empty() {
-        message.title
-    } else {
-        title
-    };
-    let edited_text = if text.is_empty() { message.text } else { text };
-
-    message.title = edited_title;
-    message.text = edited_text;
-    message.ledger = env.ledger().sequence();
-
-    env.storage()
-        .persistent()
-        .set(&DataKey::Message(message_id), &message);
-    return Ok(());
-}
-```
-
-#### `read_message`
-
-Leer un mensaje deseado es tan simple como consultar el almacenamiento persistente del contrato y devolver la estructura `Message` del contrato. Nuevamente, estamos utilizando la función utilitaria `get_message`, así que cubriremos los [detalles de eso más adelante](#get_message). Brevemente por ahora, estamos pasando el ID del mensaje y devolviendo el mensaje correspondiente, produciendo un error en el camino si el ID del mensaje no existe en el almacenamiento del contrato.
-
-```rust
-/// Read a specified message from the guestbook.
-///
-/// # Arguments
-///
-/// * `message_id` - The ID number of the message to retrieve.
-///
-/// # Panics
-///
-/// * If the message ID is not associated with a message.
-pub fn read_message(env: Env, message_id: u32) -> Result<Message, Error> {
-    let message = get_message(&env, message_id);
-    Ok(message)
-}
-```
-
-#### `read_latest`
-
-Pero, ¿y si alguien solo quiere leer el _último_ mensaje y no sabe cuál es su número de ID? Bueno, estamos proporcionando una función precisamente para eso. Sin argumentos que pasar. Sin autenticación. Solo extrae el mensaje del almacenamiento persistente del contrato y devuelve la estructura (o produce un pánico si el contrato no tiene mensajes aún). Fácil fácil.
-
-```rust
-/// Read the latest message to be sent to the guestbook.
-pub fn read_latest(env: Env) -> Result<Message, Error> {
-    let latest_id = env
-        .storage()
-        .instance()
-        .get(&DataKey::MessageCount)
-        .unwrap();
-    let latest_message = get_message(&env, latest_id);
-    Ok(latest_message)
-}
-```
-
-#### `claim_donations`
-
-:::info
-
-Dejaremos de lado si el mantenedor del libro de visitas _debería_ estar solicitando donaciones, y simplemente asumiremos que _quiere_. Es una gran manera de pensar sobre la interoperabilidad de activos en tus contratos inteligentes, ¡así que vamos por ello!
-
-:::
-
-La función `claim_donations` permitirá al invocador de la función enviar un saldo de cualquier token al administrador del contrato del libro de visitas. Dirigiremos tu atención a dos aspectos de esta función, en particular.
-
-Primero, estamos requiriendo un `Address` para el token que debe ser reclamado. Puede que sea tu primera instinto codificar y predeterminar el XLM nativo para estas donaciones. Esto ciertamente se puede hacer, pero la dirección de ese contrato será diferente en Mainnet, Testnet o Futurenet, y el contrato tendría que ser modificado y recompilado para cada red a la que desees desplegar. Un enfoque más "universalmente" aplicable es tomar la dirección del token como argumento para esta función, y permitir que los donantes y el administrador usen cualquier token que consideren adecuado para la situación.
-
-En segundo lugar, no estamos requiriendo ninguna autenticación para esta función. No es realmente necesario agregar esa lógica a la mezcla, porque no habrá un daño real si un no-administrador invoca la función:
-
-- No hay riesgo de que los fondos sean enviados a la dirección equivocada. La dirección del administrador se está leyendo del almacenamiento de la instancia del contrato.
-- No hay riesgo de que el administrador reciba tokens no deseados. Si el token requiere una trustline, y una no existe en la cuenta (es decir, el administrador no ha optado por mantener ese activo), la invocación simplemente fallará. Si es un token de contrato exclusivo de Soroban, la entrada de almacenamiento del nuevo saldo será pagada por quien invoque esta función. El administrador no pierde ningún fondo, y el saldo no tendrá un impacto significativo en su cuenta.
-- El mejor de los casos sería que una persona altruista _realmente_ quiere que el administrador tenga los tokens que han donado, así que pagará el dinero de gas para activar el envío de los tokens mantenidos por el contrato al administrador.
-
-Además de esas dos cosas, todo lo demás es bastante sencillo. Creamos un cliente de token, verificamos el saldo del contrato de ese token, y si hay un saldo positivo, entonces enviamos los tokens a la dirección del administrador.
-
-```rust
-/// Claim any donations that have been made to the guestbook contract.
-///
-/// # Panics
-///
-/// * If the contract is not holding any donations balance.
-pub fn claim_donations(env: Env, token: Address) -> Result<i128, Error> {
-    let token_client = token::TokenClient::new(&env, &token);
-    let contract_balance = token_client.balance(&env.current_contract_address());
-
-    if contract_balance == 0 {
-        panic_with_error!(&env, Error::NoDonations);
-    }
-
-    let admin_address: Address = env.storage().instance().get(&DataKey::Admin).unwrap();
-    token_client.transfer(
-        &env.current_contract_address(),
-        &admin_address,
-        &contract_balance,
-    );
-
-    Ok(contract_balance)
-}
-```
-
-### Funciones utilitarias
-
-También tenemos algunas funciones utilitarias que no están expuestas para ser invocadas por el contrato inteligente en una transacción. Estas funciones existen para que no tengamos que codificar la misma lógica una y otra vez (es decir, leer un mensaje del almacenamiento del contrato). Este es un enfoque bastante común para reducir el tamaño del contrato y hacer que la lógica del contrato sea más consistente.
-
-#### `check_string_not_empty`
-
-Aquí, simplemente estamos abstraiendo un chequeo que se realiza múltiples veces a lo largo del contrato. De este modo, podemos estar seguros de que _cada_ vez que queremos comprobar que una cadena no está vacía, lo estamos revisando de la misma manera exacta.
-
-```rust
-// Make sure the provided string is not empty.
-fn check_string_not_empty(env: &Env, sus_string: &String) {
-    if sus_string.is_empty() {
-        panic_with_error!(env, Error::InvalidMessage);
-    }
-}
-```
-
-#### `get_message`
-
-Esta función recupera una entrada de mensaje del almacenamiento del contrato del libro de visitas. Si la entrada no se encuentra, entraremos en pánico con un mensaje de error. Si se encuentra, devolvemos la estructura de mensaje completa `struct`.
-
-```rust
-// Read a message from persistent storage.
-fn get_message(env: &Env, message_id: u32) -> Message {
-    if !env
-        .storage()
-        .persistent()
-        .has(&DataKey::Message(message_id))
-    {
-        panic_with_error!(env, Error::NoSuchMessage);
-    }
-
-    let message: Message = env
-        .storage()
-        .persistent()
-        .get(&DataKey::Message(message_id))
-        .unwrap();
-    return message;
-}
-```
-
-#### `save_message`
-
-Estamos abstraiendo el método que estamos utilizando para escribir un mensaje en el almacenamiento del contrato porque se utiliza en dos lugares: las funciones `initialize` y `write_message`. Queremos que ambas almacenen mensajes de la misma manera, por lo que estamos imponiendo eso utilizando esta función utilitaria.
-
-Estamos almacenando un `MessageCount` en el almacenamiento de la instancia del contrato, para ayudarnos en el guardado, lectura, edición, etc. de mensajes. Esto ciertamente se podría hacer de otra manera, pero será conveniente para nosotros cuando se trate de guardar nuevos mensajes, leer mensajes del contrato, consultar el estado del contrato en el frontend, etc.
-
-```rust
-// Write a message to persistent storage.
-fn save_message(env: &Env, message: Message) -> u32 {
-    let mut num_messages = env
-        .storage()
-        .instance()
-        .get(&DataKey::MessageCount)
-        .unwrap_or(0 as u32);
-    num_messages += 1;
-
-    env.storage()
-        .persistent()
-        .set(&DataKey::Message(num_messages), &message);
-    env.storage()
-        .instance()
-        .set(&DataKey::MessageCount, &num_messages);
-
-    return num_messages;
-}
-```
-
-### Tipos de contrato
-
-Además de las funciones anteriores, tenemos algunos tipos personalizados escritos para nuestro contrato inteligente. Estos pueden verse en el [`types.rs file`](https://github.com/ElliotFriend/ye-olde-guestbook/blob/main/contracts/ye_olde_guestbook/src/types.rs) en el repositorio del código fuente.
-
-#### `Message`
-
-El tipo `Message` es una estructura `struct` que contendrá toda la información sobre un mensaje que ha sido escrito en el libro de visitas. Llevamos un registro del título del mensaje, texto, autor y en qué número de ledger fue escrito. Algunas de estas no son estrictamente necesarias aquí y probablemente podrían manejarse fuera del contrato inteligente (utilizando un indexador de datos, por ejemplo). Sin embargo, para los propósitos de este tutorial, mantendremos estos mensajes en entradas persistentes en el almacenamiento del contrato.
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub struct Message {
-    pub author: Address,
-    pub ledger: u32,
-    pub title: String,
-    pub text: String,
-}
-```
-
-#### `DataKey`
-
-Esta es una estructura que se utiliza en otros lugares del contrato para definir las claves para las diversas entradas de almacenamiento que mantendrá el contrato. Nada innovador o notable aquí, para ser honesto, pero aún vale la pena mostrarlo. El `Message(ID_NUMBER)` se utilizará como la clave para almacenar una estructura `Message` en on-chain como el valor correspondiente.
-
-```rust
-#[contracttype]
-#[derive(Clone)]
-pub enum DataKey {
-    Admin,
-    MessageCount,
-    Message(u32),
-}
-```
-
-#### `Error`
-
-Seguimos las [convenciones típicas de contrato](../../guides/conventions/error-enum.mdx) y creamos un `enum` para registrar nuestros errores.
-
-```rust
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum Error {
-    InvalidMessage = 1,     // The provided message is malformed in some way.
-    NoSuchMessage = 2,      // The message requested does not exist.
-    UnauthorizedToEdit = 3, // Address is not allowed to edit this message.
-    NoDonations = 4,        // Contract has no donations to claim.
-}
-```
-
-#### Pruebas
-
-Hemos escrito algunas pruebas que trabajan a través de muchos patrones de uso (previstos) para este contrato inteligente. Es demasiado extenso para profundizar aquí, pero vale la pena revisar el [código fuente](https://github.com/ElliotFriend/ye-olde-guestbook/blob/main/contracts/ye_olde_guestbook/src/test.rs) para entender la lógica de cómo se supone que las diversas funciones del contrato funcionen juntas.
-
-A continuación, veremos cómo pasamos de este contrato desplegado a un paquete NPM que se pueda importar y usar en un proyecto frontend fácilmente, y con total seguridad de tipo.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/README.mdx
deleted file mode 100644
index fbf5aeab2e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 55
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Construir tubería de ingestión de red personalizada
-
-Con la [Plataforma de Datos Componible](https://stellar.org/blog/developers/composable-data-platform) de Stellar puedes construir tuberías de datos rápidas y ligeras para datos del libro mayor.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/_category_.json
deleted file mode 100644
index 4013957377..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/_category_.json
+++ /dev/null
@@ -1,7 +0,0 @@
-{
-  "position": 55,
-  "label": "Build Custom Network Ingestion Pipeline",
-  "link": {
-    "type": "generated-index"
-  }
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/ingestion-pipeline-code.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
deleted file mode 100644
index 0a3f55c8d2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/ingestion-pipeline-code.mdx
+++ /dev/null
@@ -1,301 +0,0 @@
----
-title: Código de ejemplo de la canalización del consumidor CDP
-sidebar_position: 30
----
-
-Código completo para un pequeño ejemplo de un pipeline consumidor de metadatos del ledger de la red Stellar usando el [Ingest SDK](overview.mdx#the-ingestion-sdk-packages) de Stellar Go para demostrar el pipeline de datos desde metadatos del ledger hasta un modelo de datos derivado con procesamiento distribuido y basado en eventos hacia un microservicio de muestra (script Python) como suscriptor.
-
-Este ejemplo utiliza el SDK envoltorio de Go [goczmq](https://github.com/zeromq/goczmq) de ZeroMQ, que requiere varias [bibliotecas dependientes del sistema operativo para que también estén instaladas en la máquina host](https://github.com/zeromq/goczmq?tab=readme-ov-file#dependencies).
-
-Este ejemplo requiere tener acceso a un lago de metadatos de ledger público que esté siendo completado activamente con los últimos ledgers de la mainnet de Stellar. Para propósitos del ejemplo, utiliza un lago de datos de referencia alojado en [AWS Open Data S3](../../../data/apis/rpc/admin-guide/data-lake-integration#1-accessing-a-data-lake)
-
-### Paso #1 - Crea un directorio de ejemplo y copia los siguientes archivos a tu estación de trabajo.
-
-<CodeExample>
-```bash
-mkdir pipeline-example; cd pipeline-example
-
-````
-</CodeExample>
-
-### `main.go`
-
-<CodeExample>
-
-```go
-
-package main
-
-import (
-  "context"
-  "encoding/json"
-  "fmt"
-  "io"
-  "os"
-  "os/signal"
-
-  "github.com/pelletier/go-toml"
-  "github.com/pkg/errors"
-  "github.com/stellar/go-stellar-sdk/amount"
-  "github.com/stellar/go-stellar-sdk/historyarchive"
-  "github.com/stellar/go-stellar-sdk/ingest"
-  "github.com/stellar/go-stellar-sdk/ingest/ledgerbackend"
-  "github.com/stellar/go-stellar-sdk/network"
-  "github.com/stellar/go-stellar-sdk/support/datastore"
-  "github.com/stellar/go-stellar-sdk/support/storage"
-  "github.com/stellar/go-stellar-sdk/xdr"
-  "github.com/stellar/go-stellar-sdk/support/log"
-
-  "github.com/zeromq/goczmq"
-)
-
-// Application payment model
-type AppPayment struct {
-  Timestamp       uint
-  BuyerAccountId  string
-  SellerAccountId string
-  AssetCode       string
-  Amount          string
-}
-
-// application data pipeline
-type Message struct {
-  Payload interface{}
-}
-
-type Processor interface {
-  Process(context.Context, Message) error
-}
-
-type Publisher interface {
-  Subscribe(receiver Processor)
-}
-
-// Ingestion Pipeline Processors
-type ZeroMQOutboundAdapter struct {
-  Publisher *goczmq.Sock
-}
-
-func (adapter *ZeroMQOutboundAdapter) Process(ctx context.Context, msg Message) error {
-  _, err := adapter.Publisher.Write(msg.Payload.([]byte))
-  return err
-}
-
-type AppPaymentTransformer struct {
-  processors        []Processor
-  networkPassPhrase string
-}
-
-func (transformer *AppPaymentTransformer) Subscribe(receiver Processor) {
-  transformer.processors = append(transformer.processors, receiver)
-}
-
-func (transformer *AppPaymentTransformer) Process(ctx context.Context, msg Message) error {
-  ledgerCloseMeta := msg.Payload.(xdr.LedgerCloseMeta)
-  ledgerTxReader, err := ingest.NewLedgerTransactionReaderFromLedgerCloseMeta(transformer.networkPassPhrase, ledgerCloseMeta)
-  if err != nil {
-    return errors.Wrapf(err, "failed to create reader for ledger %v", ledgerCloseMeta.LedgerSequence())
-  }
-
-  closeTime := uint(ledgerCloseMeta.LedgerHeaderHistoryEntry().Header.ScpValue.CloseTime)
-
-  // scan all transactions in a ledger for payments to derive new model from
-  counter := 0
-  transaction, err := ledgerTxReader.Read()
-  for ; err == nil; transaction, err = ledgerTxReader.Read() {
-    for _, op := range transaction.Envelope.Operations() {
-      switch op.Body.Type {
-      case xdr.OperationTypePayment:
-        networkPayment := op.Body.MustPaymentOp()
-        myPayment := AppPayment{
-          Timestamp:       closeTime,
-          BuyerAccountId:  networkPayment.Destination.Address(),
-          SellerAccountId: op.SourceAccount.Address(),
-          AssetCode:       networkPayment.Asset.StringCanonical(),
-          Amount:          amount.String(networkPayment.Amount),
-        }
-        jsonBytes, err := json.Marshal(myPayment)
-        if err != nil {
-          return err
-        }
-
-        for _, processor := range transformer.processors {
-          processor.Process(ctx, Message{Payload: jsonBytes})
-        }
-        counter++
-      }
-    }
-  }
-
-  if err != io.EOF {
-    return errors.Wrapf(err, "failed to read transaction from ledger %v", ledgerCloseMeta.LedgerSequence())
-  }
-
-  log.Infof("Published %v payments from ledger sequnce %v", counter, ledgerCloseMeta.LedgerSequence())
-  return nil
-}
-
-type LedgerMetadataInboundAdapter struct {
-  processors                []Processor
-  historyArchiveURLs        []string
-  dataStoreConfig           datastore.DataStoreConfig
-}
-
-func (adapter *LedgerMetadataInboundAdapter) Subscribe(receiver Processor) {
-  adapter.processors = append(adapter.processors, receiver)
-}
-
-func (adapter *LedgerMetadataInboundAdapter) Run(ctx context.Context) error {
-
-  // Get the lastest ledger from network.
-  historyArchive, err := historyarchive.NewArchivePool(adapter.historyArchiveURLs, historyarchive.ArchiveOptions{
-    ConnectOptions: storage.ConnectOptions{
-      UserAgent: "payment_demo",
-      Context:   ctx,
-    },
-  })
-  if err != nil {
-    return errors.Wrap(err, "error creating history archive client")
-  }
-  latestNetworkLedger, err := historyArchive.GetLatestLedgerSequence()
-
-  if err != nil {
-    return errors.Wrap(err, "error getting latest ledger")
-  }
-
-  ledgerRange := ledgerbackend.UnboundedRange(latestNetworkLedger)
-
-  pubConfig := ingest.PublisherConfig{
-    DataStoreConfig:       adapter.dataStoreConfig,
-    BufferedStorageConfig: ingest.DefaultBufferedStorageBackendConfig(1),
-  }
-
-  log.Infof("beginning payments stream, starting at ledger %v ...\n", latestNetworkLedger)
-  return ingest.ApplyLedgerMetadata(ledgerRange, pubConfig, ctx,
-      func(lcm xdr.LedgerCloseMeta) error {
-          for _, processor := range adapter.processors {
-              if err = processor.Process(ctx, Message{Payload: lcm}); err != nil {
-                  return err
-              }
-          }
-          return nil
-      })
-}
-
-func main() {
-  // run a data pipeline that transforms Pubnet ledger metadata into payment events
-  ctx, stop := signal.NotifyContext(context.Background(), os.Interrupt, os.Kill)
-  defer stop()
-  log.SetLevel(log.InfoLevel)
-
-  cfg, err := toml.LoadFile("config.toml")
-  if err != nil {
-      fmt.Printf("config.toml shoule be accessible in current directdory: %v\n", err)
-      return
-  }
-
-  datastoreConfig := datastore.DataStoreConfig{}
-  // Unmarshal TOML data into the Config struct
-  if err = cfg.Unmarshal(&datastoreConfig); err != nil {
-      fmt.Printf("error unmarshalling TOML config: %v\n", err)
-      return
-  }
-
-  // create the inbound source of pubnet ledger metadata
-  ledgerMetadataInboundAdapter := &LedgerMetadataInboundAdapter{
-    historyArchiveURLs:        network.PublicNetworkhistoryArchiveURLs,
-    dataStoreConfig: datastoreConfig,
-  }
-
-  // create the app transformer to convert network data to application data model
-  appTransformer := &AppPaymentTransformer{networkPassPhrase: network.PublicNetworkPassphrase}
-
-  // create the outbound adapter, this is the end point of the pipeline
-  // publishes application data model as messages to a broker
-  publisher, err := goczmq.NewPub("tcp://127.0.0.1:5555")
-  if err != nil {
-    log.Infof("error creating 0MQ publisher: %v\n", err)
-    return
-  }
-  defer publisher.Destroy()
-  outboundAdapter := &ZeroMQOutboundAdapter{Publisher: publisher}
-
-  // wire up the ingestion pipeline and let it run
-  appTransformer.Subscribe(outboundAdapter)
-  ledgerMetadataInboundAdapter.Subscribe(appTransformer)
-  log.Infof("Payment ingestion pipeline ended %v\n", ledgerMetadataInboundAdapter.Run(ctx))
-}
-
-````
-
-</CodeExample>
-
-### `config.toml`
-
-La configuración de CDP, este archivo define el almacenamiento de datos que contiene los archivos de metadatos del ledger pre-generados. Se utiliza el bucket [S3 Public Blockchain](https://registry.opendata.aws/aws-public-blockchain/) para [Stellar Pubnet](hhttps://aws-public-blockchain.s3.us-east-2.amazonaws.com/index.html#v1.1/stellar/ledgers/pubnet/) en este ejemplo.
-
-<CodeExample>
-
-```
-type = "S3"
-
-[params]
-destination_bucket_path = "aws-public-blockchain/v1.1/stellar/ledgers/pubnet"
-region = "us-east-2"
-
-# this is the schema specific to the public s3 data lake being used
-[schema]
-ledgers_per_file = 1
-files_per_partition = 64000
-
-```
-
-</CodeExample>
-
-### `distributed_payment_subsciber.py`
-
-Un script de Python que demuestra cómo ahora tenemos procesamiento distribuido y arquitectura impulsada por eventos aprovechando el MQ Broker para enviar el modelo de datos de aplicación de pago derivado a otros microservicios. Asegúrate de `pip install pyzmq`
-
-<CodeExample>
-
-```python
-import sys
-import zmq
-import json
-
-#  Socket to talk to server
-context = zmq.Context()
-socket = context.socket(zmq.SUB)
-
-print("Collecting payments from pipeline ...")
-socket.connect("tcp://127.0.0.1:5555")
-socket.subscribe("")
-
-while True:
-
-    message = socket.recv()
-    json_object = json.loads(message)
-    json_formatted_str = json.dumps(json_object, indent=2)
-    print(f"Received payment:\n\n{json_formatted_str}")
-
-```
-
-</CodeExample>
-
-### Paso #2 - Compila y ejecuta el ejemplo del pipeline de ingestión.
-
-<CodeExample>
-```bash 
-go mod init example/pipeline
-go get github.com/stellar/go-stellar-sdk@latest github.com/zeromq/goczmq@v4.1.0
-go mod tidy 
-go build -o pipeline ./. 
-AWS_SHARED_CREDENTIALS_FILE=/dev/null ./pipeline
-
-```
-</CodeExample>
-
-### Step# 3 - Run the distributed pipeline consumer
-
-In separate terminal, run `python distributed_payment_subsciber.py`, this will perform distributed pipeline topology, as it receives messages with payment info from the pipeline process and does additional processing(printing it to console).
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/overview.mdx
deleted file mode 100644
index cd5af545f8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/ingest-sdk/overview.mdx
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Resumen
-sidebar_position: 10
----
-
-Este tutorial explica cómo una aplicación puede aprovechar la [arquitectura CDP](https://stellar.org/blog/developers/composable-data-platform) para crear pipelines de metadatos rápidos y livianos del Stellar Ledger utilizando unos pocos paquetes selectos del repositorio de Stellar Go [github.com/stellar/go-stellar-sdk](https://github.com/stellar/go-stellar-sdk), conocidos colectivamente como el SDK de 'Ingestión':
-
-## Los paquetes del SDK de Ingestión
-
-- Paquete utilitario `github.com/stellar/go-stellar-sdk/amount` para convertir precios de operaciones de transacciones en la red a cadena de texto
-- Paquete utilitario `github.com/stellar/go-stellar-sdk/historyarchive` `github.com/stellar/go-stellar-sdk/support/datastore` `github.com/stellar/go-stellar-sdk/support/storage` con wrappers convenientes para acceder a archivos históricos y evitar aspectos HTTP de bajo nivel
-- `github.com/stellar/go-stellar-sdk/ingest` proporciona funcionalidad de análisis sobre los metadatos del ledger en red, convierte al modelo más centrado en el desarrollador `LedgerTransaction`
-- `github.com/stellar/go-stellar-sdk/network` ofrece configuraciones preconfiguradas convenientes para las redes Testnet y Mainnet
-- `github.com/stellar/go-stellar-sdk/xdr` una vinculación completa en Golang al modelo de datos de la red Stellar
-
-## Configuración del proyecto de Ingestión
-
-### Requisitos del proyecto
-
-Para usar este ejemplo de tubería CDP para datos de transacciones en vivo de la red Stellar, necesitarás:
-
-- Una estación de trabajo de desarrollador con el runtime del lenguaje de programación [Go](https://go.dev/learn/) instalado
-- Un IDE para editar código Go, [VSCode](https://code.visualstudio.com/download) es bueno si se necesita uno
-- Una carpeta de proyecto Go nueva e inicializada, vacía. `mkdir pipeline; cd pipeline; go mod init example/pipeline`
-- Alguna familiaridad con el [modelo de metadatos del Ledger Stellar](../../../learn/fundamentals/stellar-data-structures/README.mdx). Se define en un formato IDL expresado en [código XDR](https://github.com/stellar/stellar-xdr).
-- Docker
-- Cuenta de Google Cloud Platform:
-  - un bucket creado en Google Cloud Storage(GCS)
-  - Credenciales de GCP [en el entorno de la estación de trabajo](../../../data/indexers/build-your-own/galexie/admin_guide/setup.mdx#google-cloud-platform-gcp-credentials)
-
-Nuestra aplicación de ejemplo solo está interesada en un pequeño subconjunto del modelo de datos general de la red relacionado con las transferencias de activos desencadenadas por la operación de Pago y define su propio modelo de datos derivado como el objetivo del ejercicio:
-
-<CodeExample>
-
-```
-::AppPayment
-   Timestamp: uint
-   BuyerAccountId: string
-   SellerAccountId: string
-   AssetCode: string
-   Amount: string
-}
-```
-
-</CodeExample>
-
-La aplicación de ejemplo realizará ambas tuberías del CDP. Se requieren un mínimo de dos tuberías para una arquitectura CDP de extremo a extremo completa.
-
-![](/assets/ingest-sdk/cdp_pipelines.png)
-
-### Tubería de exportación de metadatos del Ledger
-
-Esta pipeline debe iniciarse primero, es responsable de exportar metadatos del Stellar Ledger como archivos a un [CDP Datastore](https://github.com/stellar/go-stellar-sdk/blob/main/support/datastore/datastore.go).
-
-#### Determinar el Datastore
-
-El Datastore en CDP es una interfaz, que permite múltiples implementaciones que representan diferentes capas de almacenamiento físico que se pueden 'conectar' para exportar y consumir tuberías. Stellar proporciona el [Datastore de GCS] como la primera implementación de Datastore, y este ejemplo elige usar esta implementación existente.
-
-Habrá contribuciones de código abierto para implementaciones en otras capas de almacenamiento de las que elegir a medida que CDP crezca. Si no encuentras una implementación para una capa de almacenamiento que deseas usar, también es posible desarrollar tu propia implementación de [Datastore](https://github.com/stellar/go-stellar-sdk/blob/main/support/datastore/datastore.go#L17), lo cual está fuera del alcance de este ejemplo, ya que implica un ejercicio de aprendizaje separado que llegará pronto.
-
-#### Exportando metadatos de la red al Datastore
-
-Usa Galexie, un nuevo programa de línea de comandos CDP para exportar metadatos de red a datastores.
-
-- Sigue los pasos de configuración de Galexie en la [Guía del usuario de Galexie](../../../data/indexers/build-your-own/galexie/admin_guide/setup.mdx), para configurar detalles específicos del bucket de GCS y la red objetivo.
-
-- Sigue las [instrucciones de ejecución de Galexie con Docker](../../../data/indexers/build-your-own/galexie/admin_guide/running.mdx) para iniciar la exportación.
-  - Para la exportación única de un rango histórico limitado de ledgers, usa `append --start <from_ledger> --end <to_ledger>`
-  - Para una exportación continua de los ledgers anteriores y todos los nuevos ledgers generados en la red, usa `append --start <from_ledger>`.
-
-### Tubería de consumidores de metadatos del Ledger
-
-Una tubería de consumidores recupera archivos del bucket de GCS y los usa como el origen de los metadatos del Ledger en una tubería de procesamiento de datos. Puede haber muchas tuberías de consumidores separadas accediendo a la misma Datastore al mismo tiempo. Cada tubería de consumidores típicamente desempeñará tres funciones distintas de procesadores de flujo:
-
-#### Adaptador de entrada
-
-La 'fuente de origen' de los metadatos del ledger en una tubería. Este procesador recupera archivos [LedgerCloseMeta](https://github.com/stellar/go-stellar-sdk/blob/main/xdr/xdr_generated.go) del GCS Datastore, extrae el `LedgerCloseMeta` para cada Ledger y lo publica en la pipeline de mensajería.
-
-El SDK de Go proporciona la función auxiliar para consumidores [ApplyLedgerMetadata](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/producer.go) para la recuperación automatizada, eficiente y en búfer de archivos desde el datastore remoto; el código de la aplicación puede aprovechar esto para adquirir datos puros de `LedgerCloseMeta` desde una función callback.
-
-#### Transformador
-
-Se suscribe en la tubería para recibir `LedgerCloseMeta`. Utiliza el paquete Go SDK [github.com/stellar/go-stellar-sdk/xdr](https://github.com/stellar/go-stellar-sdk/tree/main/xdr) para analizar el modelo de metadatos del ledger para operaciones de pago y convertirlos en nuevas instancias del modelo de datos de la aplicación `AppPayment`. Publica `AppPayment` en la tubería.
-
-#### Adaptador de salida
-
-Actúa como la terminación de la tubería, se suscribe para recibir `ApplicationPayment` y publica los datos fuera de la tubería y a un almacén de datos externo, un Socket Publicador de ZeroMQ, que es esencialmente un intermediario de mensajes.
-
-### Resumen
-
-Consulta la [Aplicación de Ejemplo de Tubería de Ingestión](./ingestion-pipeline-code.mdx) para un ejemplo completo de código de consumidor, que demuestra una tubería de streaming en vivo contra la red Stellar, procesando los metadatos de cada nuevo ledger a medida que se cierra en la red.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/overview.mdx
deleted file mode 100644
index 3440760bea..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/overview.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Desarrollar aplicaciones de billeteras en Stellar con el SDK de billetera en cuatro lenguajes
-sidebar_position: 0
-sidebar_label: Introducción
-description: Desarrollar una aplicación de billetera en Stellar con el SDK de billetera utilizando Typescript, Flutter, Kotlin o Swift. Explorar características clave, pasos de configuración y prácticas recomendadas.
----
-
-# Resumen
-
-Stellar es un ledger distribuido open-source que puedes utilizar como backend para potenciar varias aplicaciones y servicios, como billeteras, aplicaciones de pago, exchanges de divisas, servicios de micropagos, plataformas para compras en el juego, y más — consulta los proyectos que se están creando en Stellar: [Proyectos del Ecosistema Stellar](https://stellar.org/ecosystem/projects#Projects).
-
-Stellar tiene lógica incorporada para el almacenamiento de claves, crear cuentas, firmar transacciones, rastrear saldos y realizar consultas a la base de datos de Stellar, y cualquier persona puede usar la red para emitir, almacenar, transferir e intercambiar activos.
-
-Esta documentación incluye secciones sobre cómo crear aplicaciones sin contratos inteligentes con el [Wallet SDK](./wallet/overview.mdx) o el [JS SDK](./example-application-tutorial/overview.mdx), crear con contratos inteligentes con el [tutorial de frontend para dapp](./dapp-frontend.mdx), y toda la información relacionada con la experimentación con [passkey / carteras de cuentas de contrato](../guides/contract-accounts/smart-wallets.mdx).
-
-## Anclas
-
-Muchos activos de Stellar se conectan a monedas del mundo real, y Stellar tiene protocolos abiertos para integrar depósitos y retiradas de estos activos a través de la [red de anclajes](https://stellar.org/learn/anchor-basics). Debido a esto, una aplicación basada en Stellar puede aprovechar las vías bancarias reales y conectarse a dinero real.
-
-Lee más sobre los anclajes en nuestra [sección de Anclajes](../../learn/fundamentals/anchors.mdx).
-
-Configura un anchor usando la [Anchor Platform](../../platforms/anchor-platform/README.mdx).
-
-Integra MoneyGram Ramps en una aplicación existente con el [tutorial Integrar con MoneyGram Ramps](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps).
-
-## Propuestas del Ecosistema Stellar (SEPs)
-
-Los productos y servicios basados en Stellar interoperan implementando varias Propuestas del Ecosistema Stellar (SEPs), que son documentos abiertos, creados públicamente, que se encuentran en un [repositorio de GitHub](https://github.com/stellar/stellar-protocol/tree/master/ecosystem#stellar-ecosystem-proposals-seps) y definen cómo interactúan entre sí los emisores de activos, anclajes, billeteras y otros proveedores de servicios.
-
-Como billetera, los SEPs más importantes son [SEP-24: Depósito y Retirada Alojada](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md), y [SEP-31: API de Pagos Transfronterizos](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md), [SEP-10: Autenticación Stellar](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md), [SEP-12: API de KYC](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md), y [SEP-38: API RFQ de Anclaje](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/smart-wallets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/smart-wallets.mdx
deleted file mode 100644
index 27e5818335..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/smart-wallets.mdx
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: Billeteras Inteligentes
-sidebar_position: 70
----
-
-Las billeteras inteligentes en Stellar son una parte creciente del ecosistema Stellar. Se está realizando mucho desarrollo, y esta documentación crecerá y avanzará a medida que colaboremos en una solución auditada de billetera inteligente. Mientras tanto, a continuación encontrarás una base conceptual, así como algunos ejemplos y herramientas para que comiences.
-
-## Resumen
-
-Veamos las diversas piezas que juegan un papel en las billeteras inteligentes de Stellar.
-
-### Billeteras inteligentes
-
-En resumen, una billetera inteligente es un contrato inteligente que puede actuar como una cuenta en la red. Una billetera inteligente puede mantener valor e interactuar con otros contratos inteligentes.
-
-Son billeteras digitales que aprovechan la composibilidad de contratos inteligentes para ofrecer funcionalidad y seguridad mejoradas en la gestión de activos digitales. A diferencia de las billeteras tradicionales, las billeteras inteligentes integran características como soporte multi-firma, firmantes de políticas, transacciones programables y una mejor experiencia de usuario.
-
-Las billeteras inteligentes permiten a los usuarios interactuar sin problemas con ecosistemas blockchain, proporcionando una interfaz fácil de usar para enviar, recibir y almacenar activos digitales. Pueden incorporar firmantes de muchos tipos. Entre los más emocionantes están los firmantes passkey, que implementan los estándares WebAuthn para garantizar una autenticación segura y sin contraseña, reduciendo los riesgos asociados con las frases seed y claves privadas tradicionales.
-
-Al usar contratos inteligentes, las billeteras inteligentes pueden automatizar transacciones e implementar protocolos avanzados de seguridad. Por ejemplo: transferencias con bloqueo temporal, límites de gasto y detección de fraudes. Estas características hacen que las billeteras inteligentes sean una opción ideal para los usuarios que buscan una solución segura, conveniente y versátil para gestionar sus activos digitales en el paisaje en evolución de la tecnología blockchain.
-
-### WebAuthn
-
-[WebAuthn (autenticación web)](https://www.w3.org/TR/webauthn/) es un estándar web para la autenticación segura y sin contraseña. Utiliza criptografía de clave pública para eliminar la dependencia de secretos compartidos en el mundo web2. En el contexto de una blockchain, usar un firmante WebAuthn mejora la seguridad y la usabilidad para las dapps.
-
-WebAuthn proporciona autenticación descentralizada (sin que ninguna autoridad central gestione contraseñas), mayor seguridad (las claves secretas permanecen en el dispositivo del usuario), mejor experiencia de usuario (los usuarios no tienen que preocuparse por almacenar o recordar sus claves secretas), e interoperabilidad ampliada (WebAuthn ya es admitido por los principales navegadores y plataformas).
-
-### Secp256r1
-
-El [esquema de firma secp256r1](https://wiki.hyperledger.org/display/BESU/SECP256R1+Support) es una curva elíptica que se utiliza a menudo con el algoritmo de firma digital de curva elíptica (ECDSA), que es un esquema de firma de clave pública ampliamente utilizado.
-
-Secp256r1 es un algoritmo común de firma usado en WebAuthn, que es el estándar detrás de las passkeys disponibles en navegadores, ordenadores y teléfonos. Habilitar la verificación secp256r1 on-chain permite a los desarrolladores diseñar contratos que incorporen passkeys para firmar transacciones de smart contracts y acceder a cuentas en lugar de usar frases Seed o claves de firma.
-
-El lanzamiento del Protocolo 21 permitió el soporte **nativo** de la verificación secp256r1 en smart contracts de Stellar en Mainnet como se detalla en [CAP-0051](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md). Esta integración significa que secp256r1 está desarrollada directamente en el protocolo y las aplicaciones pueden firmar transacciones y enviarlas a la red utilizando secp256r1 sin depender de un tercero.
-
-### Claves de acceso
-
-Las claves de acceso son una implementación del estándar WebAuthn. La capacidad de usar passkeys para firmar transacciones y acceder a cuentas elimina la necesidad de que los usuarios almacenen o recuerden sus claves secretas y/o frases Seed de 12 a 24 palabras, algo que ha sido una gran barrera de entrada para los usuarios finales al ingresar al espacio blockchain. Las claves secretas y las frases semilla pueden ser abrumadoras, difíciles de recordar, ingresadas incorrectamente y propensas a brechas de seguridad.
-
-Las claves de acceso ofrecen un método más rápido y seguro de autenticación de identidad utilizando datos encriptados almacenados en un dispositivo y realizando la verificación del usuario con tokens de hardware (como YubiKeys), datos biométricos (como huellas digitales o reconocimiento facial), u otros métodos criptográficos.
-
-Lee más sobre claves de acceso en este [introducción a las claves de acceso blog](https://stellar.org/blog/developers/passkeys-a-light-introduction-to-improving-blockchain-s-ux).
-
-### Cómo funcionan juntas
-
-Eso es un montón de términos técnicos. En resumen:
-
-1. Secp256r1 proporciona la base criptográfica para la generación de claves y firmas digitales,
-2. WebAuthn ofrece un marco estandarizado para la autenticación sin contraseña utilizando criptografía de clave pública, y
-3. Las passkeys implementan estas tecnologías para brindar una experiencia de usuario fluida y segura.
-
-Combina todo eso en un smart contract de Stellar, ¡y tienes la base para la mejor implementación de smart wallet del planeta!
-
-## Desarrollar con smart wallets
-
-Si estás desarrollando o experimentando con smart wallets en Stellar, algunos recursos esenciales son:
-
-### Passkey Kit
-
-El Passkey Kit es un SDK de TypeScript para crear y gestionar smart wallets de Stellar, principalmente (aunque no exclusivamente) con firmantes passkey. Está pensado para usarse junto con [Launchtube](#launchtube-transaction-submission-) para enviar transacciones firmadas on-chain, aunque esto no es un requisito. Es una biblioteca tanto para cliente como para servidor. `PasskeyKit` en el cliente y `PasskeyServer` en el servidor.
-
-El código fuente también incluye la implementación de un smart contract basado en una propuesta de [interfaz estandarizada para smart wallets](https://github.com/orgs/stellar/discussions/1499).
-
-- Usa la [app](https://passkey-kit-demo.pages.dev/)
-- Mira el [código](https://github.com/kalepail/passkey-kit)
-- Mira la [discusión](https://developers.stellar.org/meetings/2024/06/13)
-
-### Envío de transacción Launchtube
-
-Este es un servicio API donde los desarrolladores pueden enviar sus transacciones de smart contract para que sean financiadas y enviadas a la red Stellar sin tener que preocuparse por tarifas, números de secuencia, direcciones clásicas G ni otras complejidades.
-
-:::note
-
-Launchtube es un servicio prototipo. Aunque SDF mantiene una implementación en Mainnet, no podemos ofrecer garantías ni acuerdos de nivel de servicio para ella. El servicio Launchtube en Mainnet de SDF puede no ser adecuado para servicios productores críticos.
-
-:::
-
-- Ver el [código](https://github.com/stellar/launchtube)
-- Obtén un token de acceso solicitándolo en el canal `#launchtube` en [Discord](https://discord.gg/stellardev). O genera tu propio [token de testnet](https://testnet.launchtube.xyz/gen).
-- Cultiva y utiliza el [activo KALE](https://github.com/kalepail/KALE-sc) para adquirir tokens de Launchtube [aquí](https://kalefarm.xyz/launchtube/)
-
-### Smart wallet backend de SDP
-
-El equipo de la [Plataforma de Distribución Stellar](../../platforms/stellar-disbursement-platform/README.mdx) también está experimentando con implementaciones de billeteras inteligentes. En una rama de características, han implementado un contrato de smart wallet que también puede ser usado.
-
-- Ver el [código](https://github.com/stellar/stellar-disbursement-platform-backend/tree/feature/c-accounts/contracts/smart-wallet)
-
-## Proyectos de ejemplo
-
-¡Explora algunos de los trabajos actuales que se están realizando con billeteras inteligentes, claves de acceso, firmantes de políticas y más en Stellar! Juega con los varios ejemplos enlazados a continuación, construye tus propios proyectos impulsados por claves de acceso y comparte tus hallazgos en el canal `#passkeys` en [Discord](https://discord.gg/stellardev).
-
-:::note
-
-Estos ejemplos no son creados o mantenidos oficialmente por la SDF, sino por miembros dedicados de la comunidad, tanto internos como externos a la SDF.
-
-:::
-
-### Zafegard
-
-Una billetera inteligente que demuestra el uso de firmantes de políticas con estado.
-
-- Ver el [código](https://github.com/kalepail/zafegard)
-- Ver el [video de demostración](https://www.youtube.com/watch?v=I4i6sL-pHrs)
-
-### Do Math
-
-Una billetera inteligente que demuestra el uso de firma múltiple y firmantes de políticas para, sorprendentemente, hacer matemáticas sin necesidad de introducir una clave de acceso para cada interacción.
-
-- Ver el [código](https://github.com/kalepail/do-math)
-- Ver el [video de demostración](https://www.youtube.com/watch?v=lwvE6pEBmXw)
-
-### Soroban por ejemplo
-
-Una aplicación que usa claves de acceso para firmar transacciones de contratos inteligentes de Stellar.
-
-- Ver la [demostración](https://passkey.sorobanbyexample.org/)
-- Mira el [código](https://github.com/kalepail/soroban-passkey)
-- Ver el [video de demostración](https://www.youtube.com/watch?v=y38_O4oIvbY)
-- Mira la [discusión](https://developers.stellar.org/meetings/2024/05/09)
-- Lee el [blog](https://kalepail.com/blockchain/the-passkey-powered-future-of-web3)
-
-### Super Peach
-
-Un ejemplo de contrato de cuenta abstracto de múltiples firmantes impulsado por claves de acceso.
-
-- Ver la [demostración](https://superpeach.xyz/)
-- Mira el [código](https://github.com/kalepail/superpeach)
-- Ver el [video de demostración](https://youtu.be/0Agiwso2OMc?si=CHD9U8s-YLyqbXUJ)
-
-### Ye Olde Guestbook
-
-Un libro de visitas de internet impulsado por claves de acceso de antaño construido con contratos inteligentes y código frontend.
-
-- Ver la [demostración](https://ye-olde-guestbook.vercel.app)
-- Mira el [código](https://github.com/ElliotFriend/ye-olde-guestbook)
-- Lee el [tutorial](./guestbook/README.mdx)
-
-## Involúcrate
-
-### Discord de desarrolladores
-
-Únete a la discusión, haz preguntas y comparte tu propio trabajo con las billeteras inteligentes en el [Discord de Desarrolladores de Stellar](https://discord.gg/stellardev) en el canal `#passkeys`.
-
-### Discusión SEP
-
-Únete a la discusión SEP sobre la interfaz del contrato smart wallet WebAuthn en [GitHub](https://github.com/orgs/stellar/discussions/1499).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/swift-payment-app.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/swift-payment-app.mdx
deleted file mode 100644
index cb2644b4b1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/swift-payment-app.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Desarrollar una aplicación de pagos con Swift
-sidebar_position: 41
----
-
-## SwiftBasicPay
-
-SwiftBasicPay es una aplicación de pago iOS open-source que muestra cómo integrar la potente infraestructura de pagos de Stellar en aplicaciones Swift nativas usando el [Stellar Wallet SDK para Swift](https://github.com/Soneso/stellar-swift-wallet-sdk) y el [Stellar iOS SDK](https://github.com/Soneso/stellar-ios-mac-sdk).
-
-[SwiftBasicPay](https://github.com/Soneso/SwiftBasicPay) es mantenida por un desarrollador comunitario dedicado, Soneso.
-
-## Características
-
-### Funcionalidad de billetera
-
-- **Autenticación**: seguridad basada en PIN
-- **Gestión de cuentas**: creación y administración de cuentas Stellar
-- **Gestión de activos**: agregar/eliminar líneas de confianza, visión general de activos
-- **Pagos**: Enviar y recibir activos Stellar
-- **Pagos por rutas**: Pagos entre activos con enrutamiento automático
-
-### Integración Anchor
-
-- Depósitos y retiradas de fondos programáticos vía anchors
-- Cumplimiento KYC
-- Depósitos y retiradas de fondos interactivos con integración web
-
-SwiftBasicPay integra múltiples Propuestas del Ecosistema Stellar (SEPs) a través del SDK de la billetera:
-
-- **[SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)**: Stellar TOML - Proporciona metadatos de anchor y puntos finales de servicio
-- **[SEP-10](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md)**: Autenticación Web - Demuestra la propiedad de la cuenta a los anchors
-- **[SEP-6](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md)**: API de depósito/retirada de fondos - Interactúa con anchors de forma programática
-- **[SEP-9](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md)**: Campos estándar KYC - Define campos estándar para información del cliente
-- **[SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)**: API KYC - recopilación y verificación de información del cliente
-- **[SEP-24](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md)**: Depósitos/retiradas alojados - Transferencias interactivas basadas en web
-
-## Temas de aprendizaje
-
-Esta aplicación demuestra cómo:
-
-1. **Crear billeteras Stellar**: Generación de cuentas, gestión de claves
-2. **Implementar gestión de activos**: Agregar y eliminar líneas de confianza para activos Stellar
-3. **Implementar pagos**: pagos simples y pagos por rutas
-4. **Interactuar con anchors**: Integración SEP-1/10/6/12/24
-
-## Tutorial
-
-Un tutorial completo que recorre el desarrollo de esta aplicación de pagos Stellar está disponible en el [directorio de tutoriales](https://github.com/Soneso/SwiftBasicPay/tree/main/tutorial) del repositorio.
-
-El tutorial cubre almacenamiento seguro de datos, autenticación, creación de cuentas, gestión de activos, pagos, pagos por rutas e integración con anchors con explicaciones paso a paso de cómo se usan los SDKs de Stellar.
-
-## Recursos
-
-- [Repositorio de SwiftBasicPay en GitHub](https://github.com/Soneso/SwiftBasicPay)
-- [Tutorial de SwiftBasicPay](https://github.com/Soneso/SwiftBasicPay/tree/main/tutorial)
-- [Stellar Wallet SDK para Swift](https://github.com/Soneso/stellar-swift-wallet-sdk)
-- [SDK de Stellar para iOS](https://github.com/Soneso/stellar-ios-mac-sdk)
-- [Documentación del SDK de la billetera Stellar](../apps/wallet/README.mdx)
-
-## Contribuir
-
-¡Se agradecen las contribuciones a SwiftBasicPay! Por favor, crea un pull request con una descripción clara de tus cambios en el [repositorio SwiftBasicPay en GitHub](https://github.com/Soneso/SwiftBasicPay).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/CONTRIBUTING.md b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/CONTRIBUTING.md
deleted file mode 100644
index 96851c6cea..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/CONTRIBUTING.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# Guía para contribuir
-
-¡Gracias por contribuir a la documentación de la billeteras Stellar! Para comenzar,
-por favor primero lee la guía [README principal](../../../README.md).
-
-Esta documentación es principalmente para el SDK de la billeteras y sus usos para integrarse
-con varios SEPs.
-
-El documento está estructurado para ser independiente del lenguaje, pero con los componentes
-listados a continuación podemos agregar lógica específica para cada lenguaje dentro del documento.
-
-Generalmente, el texto debe ser aplicable a todos los lenguajes de programación soportados,
-pero para diferencias se puede usar el componente especial `<LanguageSpecific/>` (lee
-más abajo)
-
-## Componentes de la guía para billeteras
-
-### Encabezado
-
-El encabezado es un archivo .mdx especial que debe incluirse en todas las páginas. Contiene:
-
-- Botones de idioma
-- Una guía general sobre el uso de estos botones
-- Advertencia opcional para idiomas en progreso
-
-En todas las páginas nuevas, el encabezado debe ser el primer elemento. Opcionalmente, proporciona una lista
-de idiomas que están en progreso:
-
-```mdxjs
-<Header WIPLangs={["ts", "dart"]}/>
-```
-
-### LanguageButtons
-
-Este componente es parte del encabezado. Permite cambiar entre los
-lenguajes de programación. El idioma actual se almacena como una cookie.
-
-### WalletGuideWarn
-
-Este componente muestra una advertencia si el idioma está en progreso para esta sección.
-Por favor utiliza la propiedad `WIPLangs` para activarlo para un idioma en la página.
-
-### WalletCodeExample
-
-Este es un componente mejorado `CodeExample`. Actualmente soporta el cambio dinámico
-entre fragmentos de código en TypeScript, Kotlin, Flutter y Swift (dependiendo
-del lenguaje seleccionado por el usuario). También generará un marcador de posición si falta el fragmento
-de código. Aquí hay un ejemplo de cómo usarlo:
-
-````mdxjs
-<CodeExample>
-
-​```kotlin
-// Kotlin example here
-​```
-
-
-​```ts
-// TypeScript example here
-​```
-
-// Flutter example is replaced with an auto-generated notice
-
-</CodeExample>
-````
-
-Para ejemplos de código regular (no del SDK de billeteras) por favor usa el componente `CodeExample` normal.
-
-### LanguageSpecific
-
-Este componente permite renderizar partes de la documentación basadas en el código seleccionado.
-Para comenzar, crea 2 archivos en el directorio `component`:
-
-```md
-// ./component/kt/hello.mdx Hello, Kotlin!
-```
-
-```md
-// ./component/ts/hello.mdx Hello, TypeScript!
-```
-
-Luego, en el documento principal importa ambos archivos y el componente LanguageSpecific:
-
-```mdxjs
-// main.mdx
-import {LanguageSpecific} from "@site/src/components/LanguageSpecific";
-import KtHello from "./component/kt/hello.mdx";
-import TsHello from "./component/ts/hello.mdx";
-
-<LanguageSpecific kt={<KtHello/>} ts={<TsHello/>} /
-```
-
-Cuando el usuario selecciona Kotlin, se mostrará "Hello, Kotlin!", cuando se
-selecciona TypeScript — "Hello, TypeScript!". Finalmente, para Flutter y Swift,
-no se mostrará nada.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/README.md b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/README.md
deleted file mode 100644
index 44736a5a89..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/README.md
+++ /dev/null
@@ -1,90 +0,0 @@
-## Guía de Contribución
-
-¡Gracias por contribuir a la documentación de la billetera Stellar! Para comenzar,
-lee primero la guía [main README](../../../README.md).
-
-Esta documentación es principalmente para el SDK de billetera y sus usos para integrar
-con varios SEPs.
-
-El documento está estructurado para ser independiente del lenguaje, pero con los componentes
-enumerados a continuación podemos agregar lógica específica de idioma en el documento.
-
-En general, el texto debe ser aplicable a todos los lenguajes de programación admitidos,
-pero para las diferencias se puede usar el componente especial `<LanguageSpecific/>` (lee
-más abajo)
-
-### Componentes de guía de billetera
-
-#### Encabezado
-
-El encabezado es un archivo especial .mdx que debe incluirse en todas las páginas. Contiene:
-
-- Botones de idioma
-- Una guía general sobre cómo usar estos botones
-- Advertencia opcional para lenguajes en progreso
-
-En todas las nuevas páginas, el encabezado debe ser el primer elemento. Opcionalmente, proporciona una lista
-de idiomas que están en progreso:
-
-```mdxjs
-<Header WIPLangs={["ts", "dart"]}/>
-```
-
-#### Botones de idioma
-
-Este componente es parte del encabezado. Te permite cambiar entre lenguajes de programación. El idioma actual se almacena como una cookie.
-
-#### Advertencia de guía de billetera
-
-Este componente coloca una advertencia si el idioma está en progreso para esta sección.
-Por favor usa la propiedad `WIPLangs` para habilitarlo para un idioma en la página.
-
-#### Ejemplo de código de billetera
-
-Este es un componente `CodeExample` mejorado. Actualmente admite el cambio dinámico entre fragmentos de código de TypeScript, Kotlin, Flutter y Swift (dependiendo del idioma seleccionado por el usuario). También generará un marcador de posición si falta un fragmento de código. Aquí hay un ejemplo de cómo usarlo:
-
-````mdxjs
-<CodeExample>
-
-​```kotlin
-// Kotlin example here
-​```
-
-
-​```ts
-// TypeScript example here
-​```
-
-// Flutter example is replaced with an auto-generated notice
-
-</CodeExample>
-````
-
-Para ejemplos de código regulares (no SDK de billetera), por favor usa el componente `CodeExample`.
-
-#### Específico del idioma
-
-Este componente permite renderizar partes de la documentación basadas en el código seleccionado.
-Para comenzar, crea 2 archivos en el directorio `component`:
-
-```md
-// ./component/kt/hello.mdx Hello, Kotlin!
-```
-
-```md
-// ./component/ts/hello.mdx Hello, TypeScript!
-```
-
-Luego, en el documento principal importa ambos archivos y el componente LanguageSpecific:
-
-```mdxjs
-// main.mdx
-import {LanguageSpecific} from "@site/src/components/LanguageSpecific";
-import KtHello from "./component/kt/hello.mdx";
-import TsHello from "./component/ts/hello.mdx";
-
-<LanguageSpecific kt={<KtHello/>} ts={<TsHello/>} /
-```
-
-Cuando el usuario selecciona Kotlin, "¡Hola, Kotlin!" se va a renderizar, cuando
-se selecciona TypeScript — "¡Hola, TypeScript!". Finalmente, para Flutter y Swift, no se renderizará nada.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/README.mdx
deleted file mode 100644
index 215af9b355..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Desarrollar una billetera con el Wallet SDK
-
-Usa el Wallet SDK para integrarte con la blockchain de Stellar y conectarte a anchors usando tu lenguaje de programación preferido.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/_category_.json
deleted file mode 100644
index 26e295568d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/_category_.json
+++ /dev/null
@@ -1,7 +0,0 @@
-{
-  "position": 30,
-  "label": "Build a Wallet with the Wallet SDK",
-  "link": {
-    "type": "generated-index"
-  }
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/dart/configClient.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/dart/configClient.mdx
deleted file mode 100644
index 2c86a22315..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/dart/configClient.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-### Configurando el Cliente
-
-El SDK de Billetera Flutter utiliza el Cliente estándar del [http package](https://pub.dev/packages/http) para todas las solicitudes de red (excluyendo Horizon, donde se utiliza el cliente HTTP del SDK Stellar de Flutter).
-
-Opcionalmente, puedes establecer tu propio cliente del [http package](https://pub.dev/packages/http) que se utilizará en toda la aplicación.
-
-El cliente se puede configurar globalmente:
-
-```dart
-import 'package:http/http.dart';
-// ...
-
-// init and configure your HTTP client
-// var myClient = ...
-
-// set as default HTTP client
-var appConfig = ApplicationConfiguration(defaultClient: myClient);
-var walletCustomClient = Wallet(StellarConfiguration.testNet, applicationConfiguration: appConfig);
-```
-
-Algunos [casos de prueba](https://github.com/Soneso/stellar_wallet_flutter_sdk/tree/main/test) de este SDK utilizan, por ejemplo, el `MockClient`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/dart/install.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/dart/install.mdx
deleted file mode 100644
index 2e5b87a8cb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/dart/install.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
-```dart
-// pubspec.yaml
-stellar_wallet_flutter_sdk: ^1.0.6
-stellar_flutter_sdk: ^2.1.3
-```
-
-Puedes obtener la última versión disponible en la [página de GitHub del proyecto](https://github.com/Soneso/stellar_wallet_flutter_sdk)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/header.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/header.mdx
deleted file mode 100644
index 29d0ec88f6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/header.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-import { LanguageButtons } from "@site/src/components/LanguageButtons";
-import { WalletGuideWarn } from "@site/src/components/WalletGuideWarn";
-
-<LanguageButtons />
-
-:::info
-
-Esta guía está disponible en cuatro lenguajes de programación diferentes: Typescript, Kotlin, Flutter (Dart) y Swift. Puedes cambiar la versión mostrada en cada página mediante los botones de arriba.
-
-:::
-
-<WalletGuideWarn WIPLangs={props.WIPLangs} />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/configClient.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/configClient.mdx
deleted file mode 100644
index 9fbd785439..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/configClient.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
-### Configurar el cliente
-
-El SDK de billetera de Kotlin utiliza el [client ktor](https://ktor.io/docs/getting-started-ktor-client.html) para todas las solicitudes de red (excluyendo Horizon, donde se utiliza el cliente HTTP del SDK de Stellar). Actualmente, el motor okhttp está configurado para utilizarse con el cliente. Puedes leer más sobre cómo configurar el client ktor [aquí](https://ktor.io/docs/create-client.html#configure-client).
-
-Por ejemplo, el cliente puede ser configurado globalmente:
-
-```kotlin
-val walletCustomClient =
-  Wallet(
-    StellarConfiguration.Testnet,
-    ApplicationConfiguration(
-      defaultClientConfig = {
-        engine { this.config { this.connectTimeout(Duration.ofSeconds(10)) } }
-        install(HttpRequestRetry) {
-          retryOnServerErrors(maxRetries = 5)
-          exponentialDelay()
-        }
-      }
-    )
-  )
-```
-
-Este código de Kotlin establecerá el tiempo de espera de conexión en diez segundos a través de la [configuración de okhttp](https://ktor.io/docs/http-client-engines.html#okhttp) y también instala el [plugin de reintento](https://ktor.io/docs/client-retry.html). También puedes especificar la configuración del cliente para clases específicas del SDK de billetera.
-
-Por ejemplo, para cambiar el tiempo de espera de conexión al conectarse a algún servidor anchor:
-
-```kotlin
-val anchorCustomClient =
-  walletCustomClient.anchor("example.com") {
-    engine { this.config { this.connectTimeout(Duration.ofSeconds(30)) } }
-  }
-```
-
-### Cerrar recursos
-
-Después de que la clase de billetera ya no se utilice, es necesario cerrar todos los clientes que se utilizaron con ella. Mientras que en algunas aplicaciones puede no ser necesario (por ejemplo, la billetera vive durante toda la vida de la aplicación), en otros casos puede ser necesario. Si tu clase de billetera es de corta duración, se recomienda cerrar los recursos del cliente utilizando una función de cierre:
-
-```kotlin
-fun closeWallet() {
-  wallet.close()
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/globalSigner.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/globalSigner.mdx
deleted file mode 100644
index 5aa2720832..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/globalSigner.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
-Finalmente, con el enfoque anterior definimos el firmante y el dominio del cliente por solicitud. Si deseas definirlo una vez y utilizarlo para cada llamada de autenticación que tu aplicación está realizando, puedes hacerlo cambiando la configuración:
-
-```kotlin
-val appCfg = ApplicationConfiguration(WalletSigner.DomainSigner("https://my-domain.com/sign"), "my-domain.com")
-```
-
-Esto es particularmente útil para integrarse con múltiples anchors.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/httpConfig.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/httpConfig.mdx
deleted file mode 100644
index bafb954dcb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/httpConfig.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-Hay una configuración más disponible para una billetera que permite configurar la lógica interna del SDK. Por ejemplo, para probar con servidores locales en un protocolo HTTP, se puede habilitar manualmente HTTP.
-
-```kotlin
-val walletCustom = Wallet(
-  StellarConfiguration.Testnet,
-  ApplicationConfiguration { defaultRequest { url { protocol = URLProtocol.HTTP } } }
-)
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/install.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/install.mdx
deleted file mode 100644
index 91d62ede08..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/install.mdx
+++ /dev/null
@@ -1,6 +0,0 @@
-```kotlin
-// gradle.kts
-implementation("org.stellar:wallet-sdk:[version]")
-```
-
-Puedes obtener la última versión disponible en la [página de GitHub del proyecto](https://github.com/stellar/kotlin-wallet-sdk)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/watcher.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/watcher.mdx
deleted file mode 100644
index a505d9ba44..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/kt/watcher.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
-A continuación, obten el canal proporcionado por `WatcherResult` para recibir eventos.
-
-```kt
-do {
-  val event = result.channel.receive()
-  when (event) {
-    is StatusChange ->
-      println("Status changed to ${event.status}. Transaction: ${event.transaction}")
-    is ExceptionHandlerExit -> println("Exception handler exited the job")
-    is ChannelClosed -> println("Channel closed. Job is done")
-  }
-} while (event !is ChannelClosed)
-```
-
-Este ejemplo de código consumirá todos los eventos que provienen del canal hasta que esté cerrado. Hay tres tipos de eventos:
-
-- `StatusChange`: indica que el estado de la transacción ha cambiado.
-- `ExceptionHandlerExit`: indica que el manejador de excepciones salió del bucle de procesamiento. Con el manejador de reintentos predeterminado, esto sucede cuando se agotan los reintentos.
-- `ChannelClosed`: indica que el canal está cerrado y no se emitirán más eventos. Este evento siempre se activará. Si ocurrió `ExceptionHandlerExit`, el canal se cerrará inmediatamente después. De lo contrario, (bajo circunstancias normales) se detendrá cuando todas las transacciones alcancen estados terminales.
-
-:::info
-
-Los eventos se almacenan en el canal hasta que se reciben, y llamar al método `receive()` bloqueará el canal hasta que se reciba un mensaje. Puedes leer más sobre cómo funcionan los canales en la [documentación del canal](https://kotlinlang.org/docs/coroutines-and-channels.html#channels).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/swift/globalSigner.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/swift/globalSigner.mdx
deleted file mode 100644
index ea2b24a238..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/swift/globalSigner.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-Finalmente, con el enfoque anterior definimos el firmante y el dominio del cliente por solicitud. Si deseas definirlo una vez y usarlo para cada llamada de autenticación que realiza tu aplicación, puedes hacerlo cambiando la configuración:
-
-```swift
-let appCfg = AppConfig(defaultSigner: try DomainSigner(url: "https://my-domain.com/sign"),
-                       defaultClientDomain: "my-domain.com")
-```
-
-Esto es particularmente útil para integrarse con múltiples anchors.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/swift/install.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/swift/install.mdx
deleted file mode 100644
index 5ed3766da7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/swift/install.mdx
+++ /dev/null
@@ -1 +0,0 @@
-Agrega el repositorio (https://github.com/Soneso/stellar-swift-wallet-sdk) como una dependencia de paquete en tu proyecto de XCode. Aparecerán dos nuevas dependencias de paquete: "stellar-wallet-sdk" y "stellarsdk".
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/allowHttpInfo.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/allowHttpInfo.mdx
deleted file mode 100644
index eb979cf195..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/allowHttpInfo.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
-:::info
-
-Si el dominio de inicio del anchor utiliza http, entonces necesitas configurar el flag `allowHttp` al crear el anchor:
-
-```typescript
-let anchor = wallet.anchor({ homeDomain: "example.com", allowHttp: true });
-```
-
-Esto solo se puede usar en Testnet.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/configClient.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/configClient.mdx
deleted file mode 100644
index ae22cbd2cd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/configClient.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
-### Configurando el Cliente
-
-El SDK de billetera de Typescript usa el [cliente axios](https://axios-http.com/docs/intro) para todas las solicitudes de red. Puedes leer más sobre cómo configurar el cliente axios [aquí](https://axios-http.com/docs/instance).
-
-Por ejemplo, podemos configurar nuestro cliente axios para que esté configurado globalmente con un tiempo de espera:
-
-```typescript
-const customClient: AxiosInstance = axios.create({
-  timeout: 1000,
-});
-let appConfig = new ApplicationConfiguration(DefaultSigner, customClient);
-let wal = new Wallet({
-  stellarConfiguration: StellarConfiguration.TestNet(),
-  applicationConfiguration: appConfig,
-});
-```
-
-Puedes encontrar más [opciones de configuración aquí.](https://axios-http.com/docs/req_config)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/createKeypairInfo.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/createKeypairInfo.mdx
deleted file mode 100644
index 135f8bcc31..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/createKeypairInfo.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
-:::info
-
-Si usas react-native, `createKeypair` no funcionará. En su lugar, usa el método auxiliar `createKeypairFromRandom` así:
-
-```typescript
-import * as Random from "expo-crypto";
-const rand = Random.randomBytes(32);
-const kp = account.createKeypairFromRandom(Buffer.from(rand));
-```
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/globalSigner.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/globalSigner.mdx
deleted file mode 100644
index c502549432..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/globalSigner.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
-Finalmente, con el enfoque anterior definimos el firmante y el dominio del cliente por cada solicitud. Si deseas definirlo una vez y usarlo para cada llamada de autenticación que tu aplicación esté realizando, puedes hacerlo cambiando la configuración:
-
-```typescript
-const appCfg = new ApplicationConfiguration(
-  new DomainSigner("https://my-domain.com/sign", { ...headers }),
-  undefined,
-  "my-domain.com",
-);
-```
-
-Esto es particularmente útil para integrar con múltiples anchors.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/install.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/install.mdx
deleted file mode 100644
index b021f7e116..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/component/ts/install.mdx
+++ /dev/null
@@ -1,3 +0,0 @@
-```bash
-yarn add @stellar/typescript-wallet-sdk
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/intro.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/intro.mdx
deleted file mode 100644
index 4758c3ab4f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/intro.mdx
+++ /dev/null
@@ -1,202 +0,0 @@
----
-title: El Primer Paso para Crear una Aplicación de Billetera en Stellar con el Wallet SDK
-sidebar_position: 20
-sidebar_label: Comenzar
-description: Aprende a crear una aplicación de billetera en la red Stellar con el Wallet SDK. Explora características clave, pasos de configuración, fundamentos de Stellar y conceptos básicos de anchor.
----
-
-# Comenzar
-
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-import KtInstall from "./component/kt/install.mdx";
-import TsInstall from "./component/ts/install.mdx";
-import DartInstall from "./component/dart/install.mdx";
-import SwiftInstall from "./component/swift/install.mdx";
-import KtHttpConfig from "./component/kt/httpConfig.mdx";
-import KtConfigClient from "./component/kt/configClient.mdx";
-import TsConfigClient from "./component/ts/configClient.mdx";
-import DartConfigClient from "./component/dart/configClient.mdx";
-import AllowHttpInfo from "./component/ts/allowHttpInfo.mdx";
-
-<Header />
-
-## Instalación
-
-Primero, necesitas agregar la dependencia del SDK a tu proyecto.
-
-<LanguageSpecific
-  kt={<KtInstall />}
-  ts={<TsInstall />}
-  flutter={<DartInstall />}
-  swift={<SwiftInstall />}
-/>
-
-## Trabajando con el SDK
-
-Comencemos con la clase principal que proporciona toda la funcionalidad del SDK. Se recomienda tener un objeto billetera singleton compartido en toda la aplicación. Crear una billetera con una configuración predeterminada conectada al Testnet de Stellar es simple:
-
-<WalletCodeExample>
-
-```kotlin
-val wallet = Wallet(StellarConfiguration.Testnet)
-```
-
-```ts
-let wallet = walletSdk.Wallet.TestNet();
-```
-
-```dart
-var wallet = Wallet.testNet;
-```
-
-```swift
-let wallet = Wallet.testNet
-```
-
-</WalletCodeExample>
-
-La instancia de la billetera se puede configurar aún más. Por ejemplo, para conectarte a la red pública:
-
-<WalletCodeExample>
-
-```kotlin
-val walletTestnet = Wallet(StellarConfiguration(Network.TESTNET, "https://horizon-testnet.stellar.org"))
-```
-
-```typescript
-let wallet = new Wallet({
-  stellarConfiguration: StellarConfiguration.MainNet(),
-});
-```
-
-```dart
-var wallet = Wallet(StellarConfiguration.publicNet);
-```
-
-```swift
-let wallet = Wallet(stellarConfig: StellarConfig.publicNet)
-```
-
-</WalletCodeExample>
-
-<LanguageSpecific kt={<KtHttpConfig />} />
-
-<LanguageSpecific
-  kt={<KtConfigClient />}
-  ts={<TsConfigClient />}
-  flutter={<DartConfigClient />}
-/>
-
-## Conceptos básicos de Stellar
-
-El SDK de la billetera proporciona algunas funcionalidades adicionales además del [SDK Horizon] existente. Para interactuar con la red Stellar, el SDK de la billetera solo cubre los conceptos básicos utilizados en un flujo típico de billetera. Para casos de uso más avanzados, se debe utilizar el [SDK Horizon] subyacente en su lugar.
-
-Para interactuar con la instancia de Horizon configurada en los pasos anteriores, simplemente haz:
-
-<WalletCodeExample>
-
-```kotlin
-val stellar = wallet.stellar()
-```
-
-```typescript
-const stellar = wallet.stellar();
-```
-
-```dart
-var stellar = wallet.stellar();
-```
-
-```swift
-let stellar = wallet.stellar
-```
-
-</WalletCodeExample>
-
-Este ejemplo creará una clase Stellar que gestiona la conexión al servicio de Horizon.
-
-:::note
-
-La configuración por defecto se conecta a la instancia pública de Horizon de Stellar. Puedes cambiar este comportamiento como se describe [arriba](#working-with-the-sdk).
-
-:::
-
-Puedes leer más sobre cómo trabajar con la red Stellar en la [sección respectiva](./stellar.mdx).
-
-## Conceptos básicos de anchor
-
-El uso principal del SDK es proporcionar una forma sencilla de conectarse a los anchors a través de un conjunto de protocolos conocidos como SEPs. Veamos cómo conectar al anchor de prueba de Stellar:
-
-<WalletCodeExample>
-
-```kotlin
-val anchor = wallet.anchor("https://testanchor.stellar.org")
-```
-
-```typescript
-let anchor = wallet.anchor({ homeDomain: "testanchor.stellar.org" });
-```
-
-```dart
-var anchor = wallet.anchor("testanchor.stellar.org")
-```
-
-```swift
-let anchor = wallet.anchor(homeDomain: "testanchor.stellar.org")
-```
-
-</WalletCodeExample>
-
-<LanguageSpecific ts={<AllowHttpInfo />} />
-
-Y la interacción más básica de recuperación de un [SEP-1]: Archivo de información de Stellar:
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun anchorToml(): TomlInfo {
-  return anchor.getInfo()
-}
-```
-
-```typescript
-let resp = await anchor.sep1();
-```
-
-```dart
-var resp = await anchor.sep1();
-```
-
-```swift
-let resp = try await anchor.sep1
-```
-
-</WalletCodeExample>
-
-A continuación se pueden encontrar todos los SEPs que actualmente admite la clase anchor:
-
-- [SEP-1]: Archivo de información de Stellar como se mostró arriba
-- [SEP-10]: explorado en la sección [Autenticación Stellar]
-- [SEP-24]: explorado en la sección [Depósito y Retirada Alojados]
-- [SEP-6]: explorado en la sección [Depósito y Retirada Programáticos]
-- [SEP-12]: explorado en la subsección [Proporcionando información KYC]
-- [SEP-38]: explorado en la sección [Cotización]
-
-Además de los SEPs admitidos por la clase anchor, el SDK de la billetera también tiene soporte para el protocolo [SEP-7] que se explora en la sección [Esquema de URI para facilitar la firma delegada].
-
-[sdk horizon]: /docs/tools/sdks
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep-7]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[sep-12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[autenticación stellar]: /docs/build/apps/wallet/sep10
-[depósito y retirada alojados]: /docs/build/apps/wallet/sep24
-[depósito y retirada programáticos]: /docs/build/apps/wallet/sep6
-[proporcionar información kyc]: /docs/build/apps/wallet/sep6#providing-kyc-info
-[cotización]: /docs/build/apps/wallet/sep38
-[esquema de uri para facilitar la firma delegada]: /docs/build/apps/wallet/sep7
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/overview.mdx
deleted file mode 100644
index ef4dec5a2d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/overview.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Resumen
-sidebar_position: 10
----
-
-import Header from "./component/header.mdx";
-
-<Header />
-
-En esta guía, vamos a usar el Wallet SDK para integrarnos con la blockchain Stellar y conectar a anchors.
-
-:::note
-
-Esta documentación te guía sobre cómo crear una billetera sin usar contratos inteligentes. Para crear con contratos inteligentes, navega a la [sección de Contratos Inteligentes](../../smart-contracts/overview.mdx).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep10.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep10.mdx
deleted file mode 100644
index 8d06a8184a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep10.mdx
+++ /dev/null
@@ -1,255 +0,0 @@
----
-title: Autenticación Stellar
-sidebar_position: 40
----
-
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-import GlobalClientSignerKt from "./component/kt/globalSigner.mdx";
-import GlobalClientSignerTs from "./component/ts/globalSigner.mdx";
-import GlobalClientSignerSwift from "./component/swift/globalSigner.mdx";
-
-<Header />
-
-Las billeteras se conectan a los anchors utilizando una forma estándar de autenticación a través de la red Stellar definida por el estándar [SEP-10].
-
-Esta guía cubrirá todas las formas de usar SEP-10 para autenticarte con un anchor.
-
-## Crear una clave de autenticación
-
-:::info Solo billeteras de custodia
-
-:::
-
-Primero, vamos a crear una clave de autenticación. Aunque puedes usar la misma clave para autenticación y enviar fondos, se recomienda dividir las responsabilidades. En tu aplicación, tendrás una o más keypairs de fondos (keypairs para las cuentas que mantienen fondos e inician y reciben transacciones) y una clave de autenticación.
-
-La clave de autenticación solo se utiliza para propósitos de autenticación y no necesita mantener fondos. Ten en cuenta que no necesitas crear una cuenta para este keypair tampoco.
-
-Ve a [Stellar Lab] y genera un keypair. La clave secreta debe manejarse de manera segura, porque se utilizará para la autenticación.
-
-## Autenticación básica
-
-Hagamos una autenticación básica. En este ejemplo, utilizaremos el SDK de billetera para crear un token de autenticación.
-
-Primero, vamos a crear un objeto `anchor` para trabajar con el anchor con el que te estás integrando. En este ejemplo, utilizaremos una implementación de anchor de referencia con el dominio principal `testanchor.stellar.org`
-
-<WalletCodeExample>
-
-```kotlin
-val anchor = wallet.anchor("https://testanchor.stellar.org")
-```
-
-```typescript
-const anchor = wallet.anchor({ homeDomain: "https://testanchor.stellar.org" });
-```
-
-```dart
-final anchor = wallet.anchor("testanchor.stellar.org");
-```
-
-```swift
-let anchor = wallet.anchor(homeDomain: "testanchor.stellar.org")
-```
-
-</WalletCodeExample>
-
-A continuación, autentica con la `authKey` creada anteriormente:
-
-<WalletCodeExample>
-
-```kotlin
-val authKey = SigningKeyPair.fromSecret("my secret key")
-
-suspend fun getAuthToken(): AuthToken {
-  return anchor.sep10().authenticate(authKey)
-}
-```
-
-```typescript
-const authKey = SigningKeypair.fromSecret("my secret key");
-const sep10 = await anchor.sep10();
-
-const authToken = await sep10.authenticate({ accountKp: authKey });
-```
-
-```dart
-final authKey = SigningKeyPair.fromSecret("my secret key");
-final sep10 = await anchor.sep10();
-
-final authToken = await sep10.authenticate(authKey);
-```
-
-```swift
-let authKey = try SigningKeyPair(secretKey: "my secret key")
-let sep10 = try await anchor.sep10
-
-let authToken = try await sep10.authenticate(userKeyPair: authKey)
-```
-
-</WalletCodeExample>
-
-Para billeteras no custodiales, querrás usar la clave privada del usuario como `authKey`.
-
-## Dominio de origen (Opcional)
-
-El dominio de origen es el parámetro opcional para la autenticación SEP-10, cuando un único servidor de autenticación se comparte entre múltiples dominios. Algunos anclajes pueden requerir que proporciones este argumento. El SDK establece automáticamente el parámetro `home_domain` en todas las solicitudes SEP-10.
-
-## Dominio del cliente (Opcional)
-
-:::info Solo billeteras no custodiales
-
-:::
-
-:::caution
-
-Algunos anclajes pueden requerir que el `client_domain` siempre esté presente como parte de la solicitud, incluso para billeteras no custodiales.
-
-:::
-
-El dominio del cliente es utilizado por los anclajes para verificar el origen de la solicitud del usuario (¿qué billetera está usando este usuario?). Esto es particularmente útil para los anclajes para integrarse con billeteras no custodiales.
-
-Admitir `client_domain` tiene dos partes, la implementación del cliente de la billetera y la implementación del servidor de la billetera. En esta configuración, tendremos una clave de autenticación adicional. Esta clave se almacenará de forma remota en el servidor. Usando el archivo de información SEP-1, el anclaje podrá consultar esta clave y verificar la firma. Así, el anclaje podrá confirmar que la solicitud proviene de tu billetera, perteneciente al `client_domain` de la billetera.
-
-### Lado del Cliente
-
-Primero, implementemos el lado del cliente. En este ejemplo nos conectaremos a un signatario remoto que firma transacciones en el punto final `https://demo-wallet-server.stellar.org/sign` para el dominio del cliente `demo-wallet-server.stellar.org`.
-
-<WalletCodeExample>
-
-```kotlin
-val signer = WalletSigner.DomainSigner("https://demo-wallet-server.stellar.org/sign") {}
-
-suspend fun getAuthToken(): AuthToken {
-  return anchor
-    .sep10()
-    .authenticate(userKeyPair, signer, clientDomain = "demo-wallet-server.stellar.org")
-}
-```
-
-```typescript
-const signer = new DomainSigner(
-  "https://demo-wallet-server.stellar.org/sign",
-  {},
-);
-
-const getAuthToken = async () => {
-  return anchor.sep10().authenticate({
-    accountKp,
-    walletSigner: signer,
-    clientDomain: "demo-wallet-server.stellar.org",
-  });
-};
-```
-
-```dart
-final signer = DomainSigner("https://demo-wallet-server.stellar.org/sign");
-final sep10 = await anchor.sep10();
-
-final authToken = await sep10.authenticate(userKeyPair,
-  clientDomainSigner: signer, clientDomain: "demo-wallet-server.stellar.org");
-```
-
-```swift
-let signer = try DomainSigner(url: "https://demo-wallet-server.stellar.org/sign")
-let sep10 = try await anchor.sep10
-
-let authToken = try await sep10.authenticate(userKeyPair: authKey,
-                                             clientDomain: "demo-wallet-server.stellar.org",
-                                             clientDomainSigner: signer)
-```
-
-</WalletCodeExample>
-
-:::danger
-
-El punto final de firma de demo-wallet no está protegido para que cualquiera lo use. Tu URL de producción debe estar protegida, de lo contrario, cualquiera podría suplantar al usuario de tu billetera.
-
-:::
-
-Agreguemos autenticación con un token de portador. Simplemente actualiza el transformador de solicitudes:
-
-<WalletCodeExample>
-
-```kotlin
-val signer = WalletSigner.DomainSigner("https://demo-wallet-server.stellar.org/sign") { bearerAuth("authToken") }
-```
-
-```typescript
-const signer = new DomainSigner("https://demo-wallet-server.stellar.org/sign", {
-  Authorization: `Bearer ${authToken}`,
-});
-```
-
-```dart
-Map<String, String> requestHeaders = {
-  "Authorization": "Bearer $authToken",
-  "Content-Type": "application/json"
-};
-
-var signer = DomainSigner("https://demo-wallet-server.stellar.org/sign",
-  requestHeaders: requestHeaders);
-```
-
-```swift
-let requestHeaders = ["Authorization" : "Bearer \(authToken)"]
-
-let signer = try DomainSigner(url: "https://demo-wallet-server.stellar.org/sign",
-                              requestHeaders: requestHeaders)
-```
-
-</WalletCodeExample>
-
-<LanguageSpecific
-  kt={<GlobalClientSignerKt />}
-  ts={<GlobalClientSignerTs />}
-  swift={<GlobalClientSignerSwift />}
-/>
-
-### Lado del Servidor
-
-A continuación, implementemos el lado del servidor.
-
-Primero, genera una nueva clave de autenticación que se usará como clave de autenticación del `client_domain`.
-
-A continuación, crea un archivo toml `SEP-1` colocado bajo `<tu dominio>/.well-known/stellar.toml` con el siguiente contenido:
-
-```toml
-ACCOUNTS = [ "Authentication public key (address)" ]
-VERSION = "0.1.0"
-SIGNING_KEY = "Authentication public key (address)"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-```
-
-No olvides cambiar la frase secreta de la red para el despliegue en Mainnet.
-
-Finalmente, agreguemos la implementación en el servidor. Esta implementación de ejemplo utiliza el framework express:
-
-```javascript
-app.post("/sign", (req, res) => {
-  const envelope_xdr = req.body.transaction;
-  const network_passphrase = req.body.network_passphrase;
-  const transaction = new Transaction(envelope_xdr, network_passphrase);
-
-  if (Number.parseInt(transaction.sequence, 10) !== 0) {
-    res.status(400);
-    res.send("transaction sequence value must be '0'");
-    return;
-  }
-
-  transaction.sign(Keypair.fromSecret(SERVER_SIGNING_KEY));
-
-  res.set("Access-Control-Allow-Origin", "*");
-  res.status(200);
-  res.send({
-    transaction: transaction.toEnvelope().toXDR("base64"),
-    network_passphrase: network_passphrase,
-  });
-});
-```
-
-Puedes ver ejemplos de ambas implementaciones de billetera y servidor [aquí](https://github.com/stellar/typescript-wallet-sdk/tree/main/%40stellar/typescript-wallet-sdk/examples/sep10). Como se mencionó antes, esta implementación de servidor de ejemplo no tiene ninguna protección contra solicitudes no autorizadas, así que debes agregar verificaciones de autorización como parte de la solicitud.
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[stellar lab]: https://lab.stellar.org/
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep24.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep24.mdx
deleted file mode 100644
index ef75e909c9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep24.mdx
+++ /dev/null
@@ -1,966 +0,0 @@
----
-title: Depósito y retirada hospedados
-sidebar_position: 50
----
-
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-import KtWatcher from "./component/kt/watcher.mdx";
-
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-
-<Header />
-
-El estándar [SEP-24] define la forma estándar en que los anchors y las billeteras interactúan en nombre de los usuarios. Las billeteras utilizan este estándar para facilitar el exchange entre activos on-chain (como stablecoins) y activos off-chain (como fiat, u otros activos de red como BTC).
-
-Durante el flujo, una billetera realiza varias solicitudes al anchor, y finalmente recibe una URL interactiva para abrir en un iframe. Esta URL es utilizada por el usuario para proporcionar una entrada (como KYC) directamente al anchor. Finalmente, la billetera puede obtener información de transacciones usando puntos finales de consulta.
-
-## Obtener información del anchor
-
-Comencemos obteniendo una instancia de la clase `Sep24`, responsable de todas las interacciones SEP-24:
-
-<WalletCodeExample>
-
-```kotlin
-val sep24 = anchor.sep24()
-```
-
-```typescript
-const sep24 = await anchor.sep24();
-```
-
-```dart
-final sep24 = await anchor.sep24();
-```
-
-```swift
-let sep24 = anchor.sep24
-```
-
-</WalletCodeExample>
-
-Primero, obten la información sobre el soporte del ancla para [SEP-24]. Esta solicitud no requiere autenticación y devolverá información genérica, como las divisas admitidas y las características admitidas por el ancla. Puedes obtener una lista completa de los campos devueltos en la [especificación SEP-24](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info).
-
-<WalletCodeExample>
-
-```kt
-suspend fun getAnchorServices(): AnchorServiceInfo {
-  return sep24.getServicesInfo()
-}
-```
-
-```typescript
-const getAnchorServices = async (): Promise<AnchorServiceInfo> => {
-  return await anchor.getServicesInfo();
-};
-```
-
-```dart
-final servicesInfo = await sep24.getServiceInfo();
-```
-
-```swift
-let servicesInfo = try await sep24.info
-```
-
-</WalletCodeExample>
-
-## Flujos Interactivos
-
-Antes de comenzar, asegúrate de haberte conectado al ancla y de haber recibido un token de autenticación, como se describe en la guía de billeteras [Autenticación Stellar]. Usaremos el objeto `authToken` en los ejemplos a continuación como el token de autenticación [SEP-10] obtenido anteriormente.
-
-Para iniciar una operación, necesitamos conocer un activo. Puedes querer codificarlo de forma fija o obtenerlo dinámicamente del archivo de información del ancla, como se muestra a continuación (para USDC):
-
-<WalletCodeExample>
-
-```kt
-val asset = info.currencies.first { it.code == "USDC" }.assetId
-```
-
-```typescript
-import { IssuedAssetId } from "@stellar/typescript-wallet-sdk";
-
-const assetCode = "USDC";
-
-const info = await anchor.getInfo();
-
-const currency = info.currencies.find(({ code }) => code === assetCode);
-
-if (!currency?.code || !currency?.issuer) {
-  throw new Error(
-    `Anchor does not support ${assetCode} asset or is not correctly configured on TOML file`,
-  );
-}
-
-const asset = new IssuedAssetId(currency.code, currency.issuer);
-```
-
-```dart
-final asset = info.currencies.firstWhere((it)=>it.code=='USDC').assetId;
-```
-
-```swift
-let info = try await anchor.info
-let asset = try info.currencies?.first(where: {$0.code == "USDC"})?.assetId
-```
-
-</WalletCodeExample>
-
-:::info
-
-Antes de comenzar con el flujo de depósito, asegúrate de que la cuenta del usuario haya [establecido una línea de confianza](./stellar.mdx#modify-assets-trustlines) para el activo con el que estás trabajando.
-
-:::
-
-### Flujo Básico
-
-Comencemos con un depósito básico:
-
-<WalletCodeExample>
-
-```kt
-val deposit = sep24.deposit(asset, authToken)
-```
-
-```typescript
-const deposit = await sep24.deposit({
-  assetCode: asset.code,
-  authToken,
-});
-```
-
-```dart
-final deposit = await sep24.deposit(asset, authToken);
-```
-
-```swift
-let deposit = try await sep24.deposit(assetId: asset, authToken: authToken)
-```
-
-</WalletCodeExample>
-
-Como resultado, recibirás una [respuesta interactiva](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#deposit-and-withdraw-shared-responses) del ancla.
-
-Abre la URL recibida en un iframe y guarda el ID de la transacción para referencia futura:
-
-<WalletCodeExample>
-
-```kt
-val url = deposit.url
-val id = deposit.id
-```
-
-```typescript
-const url = deposit.url;
-const id = deposit.id;
-```
-
-```dart
-final url = deposit.url;
-final id = deposit.id;
-```
-
-```swift
-let url = deposit.url
-let id = deposit.id
-```
-
-</WalletCodeExample>
-
-De manera similar al flujo de depósito, un flujo de retiro básico tiene la misma firma de método y tipo de respuesta:
-
-<WalletCodeExample>
-
-```kt
-val withdrawal = sep24.withdraw(asset, authToken)
-val url = withdrawal.url
-val id = withdrawal.id
-```
-
-```typescript
-const withdrawal = await sep24.withdraw({
-  assetCode: asset.code,
-  authToken,
-});
-const url = withdrawal.url;
-const id = withdrawal.id;
-```
-
-```dart
-final withdrawal = await sep24.withdraw(asset, authToken);
-final url = withdrawal.url;
-final id = withdrawal.id;
-```
-
-```swift
-let withdrawal = try await sep24.withdraw(assetId: asset, authToken: authToken)
-let url = withdrawal.url
-let id = withdrawal.id
-```
-
-</WalletCodeExample>
-
-### Proporcionando Información KYC
-
-Para mejorar la experiencia del usuario, el estándar [SEP-24] admite el envío de KYC del usuario al ancla a través de [SEP-9]. A su vez, el ancla rellenará esta información en el popup interactivo.
-
-:::info
-
-Mientras que [SEP-9] admite el envío de datos binarios, la versión actual del SDK no ofrece tal funcionalidad.
-
-:::
-
-:::note
-
-En este momento, el [SEP-9] aceptado aún no está tipificado de manera estricta. La mejora de la tipificación se ofrecerá en versiones futuras.
-
-:::
-
-<WalletCodeExample>
-
-```kt
-val sep9 = mapOf("email_address" to "mail@example.com")
-
-val deposit = sep24.deposit(asset, authToken, sep9)
-```
-
-```typescript
-const deposit = await sep24.deposit({
-  assetCode: asset.code,
-  authToken,
-  extraFields: { email_address: "mail@example.com" },
-});
-```
-
-```dart
-final deposit = await sep24.deposit(asset, authToken,
-  extraFields: {"email_address": "mail@example.com"});
-```
-
-```swift
-let deposit = try await sep24.deposit(assetId: asset,
-                                      authToken: authToken,
-                                      extraFields: ["email_address" : "mail@example.com"])
-```
-
-</WalletCodeExample>
-
-### Cambio de Cuenta de Transferencia Stellar
-
-Por defecto, la transferencia Stellar se enviará a la cuenta autenticada (con un memo) que inició el depósito.
-
-Aunque en la mayoría de los casos es aceptable, algunas billeteras pueden dividir sus cuentas. Para hacerlo, pasa una cuenta adicional (y opcionalmente un memo):
-
-<WalletCodeExample>
-
-```kt
-suspend fun depositDifferentAccount(): InteractiveFlowResponse {
-  val recipientAccount = "G..."
-  val memo = "my memo" to MemoType.TEXT
-  return sep24.deposit(asset, authToken, destinationAccount = recipientAccount, destinationMemo = memo)
-}
-```
-
-```typescript
-import { Memo, MemoText } from "stellar-sdk";
-
-const recipientAccount = "G...";
-const depositDifferentAccount = async (): Promise<InteractiveFlowResponse> => {
-  return await sep24.deposit({
-    destinationAccount: recipientAccount,
-    destinationMemo: new Memo(MemoText, "some memo"),
-    assetCode: asset.code,
-    authToken,
-  });
-};
-```
-
-```dart
-final recipientAccount = "G...";
-final deposit = await sep24.deposit(asset, authToken, destinationAccount: recipientAccount,
-  destinationMemo: "my memo", destinationMemoType: MemoType.text);
-```
-
-```swift
-let recipientAccount = "G..."
-let deposit = try await sep24.deposit(assetId: asset,
-                                      authToken: authToken,
-                                      destinationAccount: recipientAccount,
-                                      destinationMemo: "my memo",
-                                      destinationMemoType: MemoType.text)
-```
-
-</WalletCodeExample>
-
-De manera similar, para un retiro, la cuenta de origen de la transacción Stellar podría cambiarse:
-
-<WalletCodeExample>
-
-```kt
-val originAccount = "G..."
-val withdrawal = sep24.withdraw(asset, authToken, withdrawalAccount = originAccount)
-```
-
-```typescript
-const originAccount = "G...";
-const withdrawal = await sep24.withdraw({
-  withdrawalAccount: originAccount,
-  assetCode: asset.code,
-  authToken,
-});
-```
-
-```dart
-final originAccount = "G...";
-final withdrawal = await sep24.withdraw(asset, authToken, withdrawalAccount: originAccount);
-```
-
-```swift
-let originAccount = "G..."
-let withdrawal = try await sep24.withdraw(assetId: asset,
-                                          authToken: authToken,
-                                          withdrawalAccount: originAccount)
-```
-
-</WalletCodeExample>
-
-## Obteniendo Información de la Transacción
-
-En el flujo típico, la billetera obtendría datos de la transacción para notificar a los usuarios sobre las actualizaciones de estado. Esto se realiza a través de los endpoints `GET /transaction` y `GET /transactions` de [SEP-24].
-
-Alternativamente, algunos anclajes admiten webhooks para notificaciones. Ten en cuenta que esta función aún no está ampliamente adoptada.
-
-### Rastreando Transacciones
-
-Veamos cómo usar el SDK de la billetera para rastrear los cambios de estado de las transacciones. Usaremos la clase `Watcher` para este propósito. Primero, inicializa el vigilante y comienza a rastrear una transacción.
-
-<WalletCodeExample>
-
-```kt
-val watcher = sep24.watcher()
-val result = watcher.watchOneTransaction(authToken, "transaction id")
-```
-
-```typescript
-const watcher = sep24.watcher();
-
-const { stop, refresh } = watcher.watchOneTransaction({
-  authToken,
-  assetCode: asset.code,
-  id: successfulTransaction.id,
-  onMessage,
-  onSuccess,
-  onError,
-});
-```
-
-```dart
-final watcher = sep24.watcher();
-final result = watcher.watchOneTransaction(authToken, "transaction id");
-```
-
-```swift
-let watcher = sep24.watcher()
-let result = watcher.watchOneTransaction(authToken: authToken,
-                                         id: "transaction id")
-```
-
-</WalletCodeExample>
-
-Alternativamente, podemos rastrear múltiples transacciones para el mismo activo.
-
-<WalletCodeExample>
-
-```kt
-val watcher = sep24.watcher()
-val result = watcher.watchAsset(getAuthToken(), asset)
-```
-
-```typescript
-const watcher = sep24.watcher();
-
-const { stop, refresh } = watcher.watchAllTransactions({
-  authToken,
-  assetCode: asset.code,
-  onMessage,
-  onError,
-});
-```
-
-```dart
-final watcher = sep24.watcher();
-final result = watcher.watchAsset(authToken, asset);
-```
-
-```swift
-let watcher = sep24.watcher()
-let result = watcher.watchAsset(authToken: authToken, asset: asset)
-```
-
-</WalletCodeExample>
-
-<LanguageSpecific kt={<KtWatcher />} />
-
-### Obteniendo Transacción
-
-Mientras que la clase `Watcher` ofrece potentes capacidades de seguimiento, a veces es necesario simplemente obtener una transacción (o transacciones) una vez. La clase `Anchor` te permite obtener una transacción por ID, ID de transacción Stellar o ID de transacción externa:
-
-<WalletCodeExample>
-
-```kt
-// "id" is the actual Anchor transaction id, all transactions should have it.
-val transaction = sep24.getTransactionBy(authToken, id = "transaction id")
-
-// "stellarTransactionId" (aka "stellar_transaction_id" on the SEP spec)
-// is the hash of the Stellar network transaction payment related to this
-// Anchor transaction.
-// The "stellarTransactionId" has a SHA256 hash format like the below:
-// - "a35135d8ed4b29b66d821444f6760f8ca1e77bea1fb49541bebeb2c3d844364a"
-// E.g. we'll only have this transaction id field AFTER the wallet sends funds
-// to Anchor on the withdrawal flow or receives funds from Anchor on the
-// deposit flow.
-val transaction = sep24.getTransactionBy(authToken, stellarTransactionId = "transaction id")
-
-// "externalTransactionId" (aka "external_transaction_id" on the SEP spec)
-// could refer to some ID of transaction on external network.
-// E.g. this could be some "reference number" displayed to the user on
-// the last step of the Interactive Flow UI which the user could use in some
-// other external place to complete the deposit or withdraw operation.
-val transaction = sep24.getTransactionBy(authToken, externalTransactionId = "transaction id")
-```
-
-```typescript
-const transaction = await sep24.getTransactionBy({
-  authToken,
-  id: transactionId,
-});
-
-// "id" is the actual Anchor transaction id, all transactions should have it.
-const transaction = await anchor.sep24().getTransactionBy({
-  authToken,
-  id: transactionId,
-});
-
-// "stellarTransactionId" (aka "stellar_transaction_id" on the SEP spec)
-// is the hash of the Stellar network transaction payment related to this
-// Anchor transaction.
-// The "stellarTransactionId" has a SHA256 hash format like the below:
-// - "a35135d8ed4b29b66d821444f6760f8ca1e77bea1fb49541bebeb2c3d844364a"
-// E.g. we'll only have this transaction id field AFTER the wallet sends funds
-// to Anchor on the withdrawal flow or receives funds from Anchor on the
-// deposit flow.
-const transaction = await anchor.sep24().getTransactionBy({
-  authToken,
-  stellarTransactionId,
-});
-
-// "externalTransactionId" (aka "external_transaction_id" on the SEP spec)
-// could refer to some ID of transaction on external network.
-// E.g. this could be some "reference number" displayed to the user on
-// the last step of the Interactive Flow UI which the user could use in some
-// other external place to complete the deposit or withdraw operation.
-const transaction = await anchor.sep24().getTransactionBy({
-  authToken,
-  externalTransactionId,
-});
-```
-
-```dart
-final transaction = await sep24.getTransaction("transaction id", authToken);
-```
-
-```swift
-// "transactionId" is the actual Anchor transaction id, all transactions should have it.
-let transaction = try await anchor.sep24.getTransactionBy(authToken: authToken,
-                                                          transactionId: "transaction id")
-
-// "stellarTransactionId" (aka "stellar_transaction_id" on the SEP spec)
-// is the hash of the Stellar network transaction payment related to this
-// Anchor transaction.
-// The "stellarTransactionId" has a SHA256 hash format like the below:
-// - "a35135d8ed4b29b66d821444f6760f8ca1e77bea1fb49541bebeb2c3d844364a"
-// E.g. we'll only have this transaction id field AFTER the wallet sends funds
-// to Anchor on the withdrawal flow or receives funds from Anchor on the
-// deposit flow.
-let transaction = try await anchor.sep24.getTransactionBy(authToken: authToken,
-                                                          stellarTransactionId: "stellar transaction id")
-
-// "externalTransactionId" (aka "external_transaction_id" on the SEP spec)
-// could refer to some ID of transaction on external network.
-// E.g. this could be some "reference number" displayed to the user on
-// the last step of the Interactive Flow UI which the user could use in some
-// other external place to complete the deposit or withdraw operation.
-let transaction = try await anchor.sep24.getTransactionBy(authToken: authToken,
-                                                          externalTransactionId: "external transaction id")
-```
-
-</WalletCodeExample>
-
-También es posible obtener transacciones por el activo
-
-<WalletCodeExample>
-
-```kt
-val transactions = sep24.getTransactionsForAsset(asset, authToken)
-```
-
-```typescript
-const transactions = await sep24.getTransactionsForAsset({
-  authToken,
-  assetCode: asset.code,
-});
-```
-
-```dart
-final transactions = await sep24.getTransactionsForAsset(asset, authToken);
-```
-
-```swift
-let transactions = try await sep24.getTransactionsForAsset(authToken: authToken, asset: asset)
-```
-
-</WalletCodeExample>
-
-## Enviando Transferencia de Retiro
-
-Antes, revisamos cómo iniciar el flujo de retiro. Ahora, veamos un ejemplo completo.
-
-Primero, inicia el retiro:
-
-<WalletCodeExample>
-
-```kt
-val withdrawal = sep24.withdraw(asset, authToken)
-```
-
-```typescript
-const withdrawal = await sep24.withdraw({
-  assetCode: asset.code,
-  authToken,
-});
-```
-
-```dart
-final withdrawal = await sep24.withdraw(asset, authToken);
-```
-
-```swift
-let withdrawal = try await sep24.withdraw(assetId: asset, authToken: authToken)
-```
-
-</WalletCodeExample>
-
-A continuación, abre una URL interactiva:
-
-<WalletCodeExample>
-
-```kt
-val url = withdrawal.url
-// open the url
-```
-
-```typescript
-const url = withdrawal.url;
-// open the url
-```
-
-```dart
-final url = withdrawal.url
-// open the url
-```
-
-```swift
-let url = withdrawal.url
-// open the url
-```
-
-</WalletCodeExample>
-
-Después de eso, necesitamos esperar hasta que el ancla esté lista para recibir fondos. Para hacerlo, esperamos hasta que la transacción alcance el estado `pending_user_transfer_start`. Este código utiliza un mecanismo de vigilancia simple (polling) sin condición de salida. El código de la aplicación debería ser más robusto.
-
-<WalletCodeExample>
-
-```kt
-val withdrawalWatcher = sep24.watcher().watchOneTransaction(authToken, withdrawal.id)
-var statusChange: StatusUpdateEvent
-
-// Wait for user input
-do {
-  statusChange = withdrawalWatcher.channel.receive()
-} while (
-  ((statusChange as? StatusChange) ?: throw Exception("Channel unexpectedly closed"))
-    .status != TransactionStatus.PENDING_USER_TRANSFER_START
-)
-```
-
-```typescript
-const watcher = sep24.watcher();
-
-const onMessage = (transaction) => {
-  if (transaction.status === "pending_user_transfer_start") {
-    // begin transfer code
-  }
-};
-
-const onSuccess = (transaction) => {
-  // transaction comes back as completed / refunded / expired
-};
-
-const onError = (transaction) => {
-  // runtime error, or the transaction comes back as
-  // no_market / too_small / too_large / error
-};
-
-// We can watch for a particular transaction.
-const { refresh, stop } = watcher.watchOneTransaction({
-  authToken,
-  assetCode: asset.code,
-  id: successfulTransaction.id,
-  onMessage,
-  onSuccess,
-  onError,
-});
-
-// Or watch for ALL transactions of a particular asset.
-const { refresh, stop } = watcher.watchAllTransactions({
-  authToken,
-  assetCode: asset.code,
-  onMessage,
-  onError,
-});
-```
-
-```dart
-final withdrawalWatcher = sep24.watcher().watchOneTransaction(authToken, withdrawal.id);
-withdrawalWatcher.controller.stream.listen(
-  (event) {
-    if (event is StatusChange && TransactionStatus.pendingUserTransferStart == event.status) {
-      // begin transfer
-    }
-  },
-  onError: (error) {
-    // handle error
-  },
-);
-```
-
-```swift
-let watcher = anchor.sep24.watcher()
-let result = watcher.watchOneTransaction(authToken: authToken,
-                                         id: withdrawal.id)
-
-NotificationCenter.default.addObserver(self,
-                                       selector: #selector(handleEvent(_:)),
-                                       name: result.notificationName,
-                                       object: nil)
-
-/// ...
-@objc public func handleEvent(_ notification: Notification) {
-    if let statusChange = notification.object as? StatusChange {
-        print("Status change to \(statusChange.status.rawValue). Transaction: \(statusChange.transaction.id)")
-        if statusChange.status == TransactionStatus.pendingUserTransferStart {
-          // begin transfer
-        }
-    } else if let _ = notification.object as? ExceptionHandlerExit {
-        print("Exception handler exited the job")
-    } else if let _ = notification.object as? NotificationsClosed {
-        print("Notifications closed. Job is done")
-    }
-}
-```
-
-</WalletCodeExample>
-
-A continuación, firma y envía la transferencia Stellar:
-
-<WalletCodeExample>
-
-```kt
-val anchorTransaction = (statusChange.transaction as WithdrawalTransaction)
-val transfer = stellar.transaction(keypair).transferWithdrawalTransaction(anchorTransaction, asset).build()
-
-transfer.sign(keypair)
-
-stellar.submitTransaction(transfer)
-```
-
-```typescript
-// Import Horizon to get the result codes for error handling
-import { Horizon } from "@stellar/stellar-sdk";
-
-// This creates a transaction builder which we'll be using to assemble
-// our transfer withdrawal transaction as shown below.
-const txBuilder = await stellar.transaction({
-  sourceAddress: keypair,
-  baseFee: 10000, // this is 0.001 XLM
-  timebounds: 180, // in seconds
-});
-
-// We can use the transaction object received on the onMessage callback from
-// the watcher, or, we can also fetch the transaction object using either
-// getTransactionBy or getTransactionsForAsset as illustrated in previous step.
-onMessage: (transaction) => {
-  if (transaction.status === "pending_user_transfer_start") {
-    // Use the builder to assemble the transfer transaction. Behind the scenes
-    // it extracts the Stellar account (withdraw_anchor_account), memo (withdraw_memo)
-    // and amount (amount_in) to use in the Stellar payment transaction that will
-    // be submitted to the Stellar network.
-    const transferTransaction = txBuilder
-      .transferWithdrawalTransaction(transaction, asset)
-      .build();
-
-    // Signs it with the account key pair
-    transferTransaction.sign(keypair);
-
-    // Finally submits it to the stellar network. This stellar.submitTransaction()
-    // function handles '504' status codes (timeout) by keep retrying it until
-    // submission succeeds or we get a different error.
-    try {
-      const response = await stellar.submitTransaction(transferTransaction);
-      console.log("Stellar-generated transaction ID: ", response.id);
-    } catch (error) {
-      /*
-        In case it's not a 504 (timeout) error, the application could try some
-        resolution strategy based on the error kind.
-
-        On Stellar docs you can find a page dedicated to error handling:
-        https://developers.stellar.org/docs/learn/encyclopedia/errors-and-debugging
-
-        And status/result codes:
-        https://developers.stellar.org/docs/data/apis/horizon/api-reference/errors
-      */
-
-      // Let's illustrate here how we could handle an 'invalid sequence number' error.
-
-      // We can access all possible result codes through Horizon's API.
-      const sdkResultCodes = Horizon.HorizonApi.TransactionFailedResultCodes;
-
-      // We can access error's response data to check for useful error details.
-      const errorData = error.response?.data;
-      /*
-        Sample of errorData object returned by the Wallet SDK:
-        {
-          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://developers.stellar.org/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed',
-          extras: {
-            envelope_xdr: 'AAAAAgAAAADBjF7n9gfByOwlnyaJH...k4BRagf/////////8AAAAAAAAAAA==',
-            result_codes: { transaction: 'tx_bad_seq' },
-            result_xdr: 'AAAAAAAAAGT////6AAAAAA=='
-          }
-        }
-      */
-
-      /*
-        Example scenario: invalid sequence numbers.
-
-        These errors typically occur when you have an outdated view of an account.
-        This could be because multiple devices are using this account, you have
-        concurrent submissions happening, or other reasons. The solution is relatively
-        simple: retrieve the account details and try again with an updated sequence number.
-      */
-      if (
-        errorData?.status == 400 &&
-        errorData?.extras?.result_codes?.transaction ===
-          sdkResultCodes.TX_BAD_SEQ
-      ) {
-        // Creating a new transaction builder means retrieving an updated sequence number.
-        const txBuilder2 = await stellar.transaction({
-          sourceAddress: keypair,
-          baseFee: 10000,
-          timebounds: 180,
-        });
-
-        // ...
-
-        // Repeat all the steps until submitting the transaction again.
-
-        // ...
-
-        const response2 = await stellar.submitTransaction(transferTransaction);
-        console.log(
-          "Stellar-generated transaction ID on retry: ",
-          response2.id,
-        );
-
-        // The application should take care to not resubmit the same transaction
-        // blindly with an updated sequence number as it could result in more than
-        // one payment being made when only one was intended.
-      }
-    }
-  }
-};
-```
-
-```dart
-final tx = event.transaction as WithdrawalTransaction;
-
-final paymentBuilder = flutter_sdk.PaymentOperationBuilder(
-  tx.withdrawAnchorAccount!,
-  flutter_sdk.Asset.createNonNativeAsset(asset.code, asset.issuer),
-  tx.amountIn!,
-);
-
-final transactionBuilder = flutter_sdk.TransactionBuilder(sourceAccount)
-  ..addOperation(paymentBuilder.build());
-
-flutter_sdk.Memo? memo;
-if ("text" == tx.withdrawalMemoType) {
-  memo = flutter_sdk.MemoText(tx.withdrawalMemo!);
-} else if ("hash" == tx.withdrawalMemoType) {
-  memo = flutter_sdk.MemoHash(base64Decode(tx.withdrawalMemo!));
-} // ... etc.
-
-if (memo != null) {
-  transactionBuilder.addMemo(memo);
-}
-
-flutter_sdk.KeyPair kp =
-  flutter_sdk.KeyPair.fromSecretSeed(userKeyPair.secretKey);
-final transaction = transactionBuilder.build()..sign(kp, network);
-final paymentResult = await sdk.submitTransaction(transaction);
-```
-
-```swift
-if let tx = statusChange.transaction as? WithdrawalTransaction {
-    let paymentOperation = try PaymentOperation(sourceAccountId: sourceAccountId,
-                                                destinationAccountId: tx.withdrawAnchorAccount!,
-                                                asset: asset.toAsset(),
-                                                amount: Decimal(string:tx.amountIn!)!)
-    var memo:Memo? = nil
-    if "text" == tx.withdrawalMemoType {
-        memo = Memo.text(tx.withdrawalMemo!)
-    } else if "hash" == tx.withdrawalMemoType {
-        memo = Memo.hash(Data(base64Encoded: tx.withdrawalMemo!)!)
-    } // ...etc
-
-    let transaction = try Transaction(sourceAccount: sourceAccount,
-                                      operations: [paymentOperation],
-                                      memo: memo)
-
-    let keypair = try KeyPair(secretSeed: userKeyPair.secretKey)
-    try transaction.sign(keyPair: keypair, network: Network.public)
-    let server = wallet.stellar.server
-    let paymentResult = await server.transactions.submitTransaction(transaction: transaction)
-}
-```
-
-</WalletCodeExample>
-
-Donde `keypair` es la cuenta autenticada por SEP-10. Si deseas transferir fondos desde una dirección diferente, consulta la sección [Cambio de Cuenta de Transferencia Stellar](#changing-stellar-transfer-account).
-
-El código para enviar transacciones a Stellar debería ser desarrollado cuidadosamente. El SDF tiene una página de documentación dedicada a [enviar transacciones y manejar errores con gracia]. Aquí hay varias cosas que debes tener en cuenta:
-
-- Ofrece una tarifa alta. Tu tarifa debería ser tan alta como estarías dispuesto a ofrecer antes de decidir que la transacción ya no vale la pena enviar. Stellar solo te cobrará lo mínimo necesario para ser incluido en el ledger; no se te cobrará la cantidad que ofrezcas a menos que todos los demás estén ofreciendo la misma cantidad o más. De lo contrario, pagarás la tarifa más baja ofrecida en el conjunto de transacciones incluidas en el ledger.
-- Establece un límite de tiempo máximo para la transacción. Esto asegura que si tu transacción no se incluye en un ledger antes del tiempo establecido, puedes reconstruir la transacción con una tarifa ofrecida más alta y volver a enviarla con mejores posibilidades de inclusión.
-- Reenvía la transacción cuando obtengas códigos de estado 504. Los códigos de estado 504 solo te están diciendo que tu transacción sigue pendiente; no que ha sido cancelada o que tu solicitud fue inválida. Simplemente debes hacer la solicitud nuevamente con la misma transacción para obtener un estado final (ya sea incluida o caducada).
-
-Por último, rastreemos las actualizaciones de estado de la transacción. En este ejemplo, simplemente verificamos si la transacción se ha completado:
-
-<WalletCodeExample>
-
-```kt
-var terminalStatus: TransactionStatus? = null
-
-do {
-  statusChange = withdrawalWatcher.channel.receive()
-
-  when (statusChange) {
-    is StatusChange -> {
-      if (statusChange.status.isTerminal()) {
-        terminalStatus = statusChange.status
-      }
-    }
-    is ChannelClosed -> println("Transaction tracking finished")
-    is ExceptionHandlerExit ->
-      println("Retries exhausted trying obtain transaction data, giving up.")
-  }
-} while (statusChange !is ChannelClosed)
-
-if (terminalStatus != TransactionStatus.COMPLETED) {
-  println("Transaction was not completed")
-}
-```
-
-```typescript
-const watcher = sep24.watcher();
-
-const onSuccess = (transaction) => {
-  // transaction came back as completed / refunded / expired
-  console.log("Transaction is completed");
-};
-
-const onError = (transaction) => {
-  // runtime error, or the transaction comes back as
-  // no_market / too_small / too_large / error
-};
-
-const { refresh, stop } = watcher.watchOneTransaction({
-  authToken,
-  assetCode: asset.code,
-  id: successfulTransaction.id,
-  onMessage,
-  onSuccess,
-  onError,
-});
-```
-
-```dart
-final watcher = sep24.watcher().watchOneTransaction(authToken, withdrawal.id);
-watcher.controller.stream.listen(
-  (event) {
-    if (event is StatusChange && event.status.isTerminal()) {
-      if (TransactionStatus.completed != event.status) {
-        print("Transaction was not completed!");
-      } else {
-        print("Success");
-      }
-    } else if (event is ExceptionHandlerExit) {
-      print("Retries exhausted trying obtain transaction data, giving up.");
-    } else if (event is StreamControllerClosed) {
-      print("Transaction tracking finished");
-    }
-  },
-  onError: (error) {
-    // handle error
-  },
-);
-```
-
-```swift
-let watcher = anchor.sep24.watcher()
-let result = watcher.watchOneTransaction(authToken: authToken,
-                                         id: withdrawal.id)
-
-NotificationCenter.default.addObserver(self,
-                                       selector: #selector(handleEvent(_:)),
-                                       name: result.notificationName,
-                                       object: nil)
-
-/// ...
-@objc public func handleEvent(_ notification: Notification) {
-    if let statusChange = notification.object as? StatusChange {
-        if statusChange.status != TransactionStatus.completed {
-          print("Transaction was not completed!")
-        } else {
-          print("Success")
-        }
-    } else if let _ = notification.object as? ExceptionHandlerExit {
-        print("Exception handler exited the job")
-    } else if let _ = notification.object as? NotificationsClosed {
-        print("Notifications closed. Job is done")
-    }
-}
-```
-
-</WalletCodeExample>
-
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[autenticación stellar]: ./sep10.mdx
-[enviar transacciones y manejar errores con gracia]: ../../../data/apis/horizon/api-reference/errors/error-handling.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep30.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep30.mdx
deleted file mode 100644
index 1dbad27266..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep30.mdx
+++ /dev/null
@@ -1,523 +0,0 @@
----
-title: Recuperación
-sidebar_position: 60
----
-
-import Header from "./component/header.mdx";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-
-<Header />
-
-El estándar [Sep-30] define la forma estándar para que un individuo (por ejemplo, un usuario o una billetera) recupere el acceso a su cuenta Stellar después de perder su clave privada sin proporcionar ningún control de terceros sobre la cuenta. Durante este flujo, la billetera se comunica con uno o más servidores de firma de recuperación para registrar la billetera para una posible recuperación posterior si es necesario.
-
-## Crear Cuenta Recuperable
-
-Primero, vamos a crear una clave de cuenta, una clave de dispositivo y una clave de recuperación que estarán asociadas a la cuenta.
-
-<WalletCodeExample>
-
-```typescript
-const accountKp = wallet.stellar().account().createKeypair();
-const deviceKp = wallet.stellar().account().createKeypair();
-const recoveryKp = wallet.stellar().account().createKeypair();
-```
-
-```kotlin
-  val accountKp = wallet.stellar().account().createKeyPair()
-  val deviceKp = wallet.stellar().account().createKeyPair()
-  val recoveryKp = wallet.stellar().account().createKeyPair()
-```
-
-```dart
-var accountKp = wallet.stellar().account().createKeyPair();
-var deviceKp = wallet.stellar().account().createKeyPair();
-var recoveryKp = wallet.stellar().account().createKeyPair();
-```
-
-```swift
-let accountKp = wallet.stellar.account.createKeyPair()
-let deviceKp = wallet.stellar.account.createKeyPair()
-let recoveryKp = wallet.stellar.account.createKeyPair()
-```
-
-</WalletCodeExample>
-
-La `accountKp` es la cuenta principal de la billetera. El `deviceKp` que vamos a agregar a la billetera como un firmante para que un dispositivo (por ejemplo, un dispositivo móvil en el que se aloja la billetera) pueda tomar control de la cuenta. Y el `recoveryKp` se utilizará para identificar la clave con los servidores de recuperación.
-
-A continuación, identifiquemos los servidores de recuperación y creemos nuestro objeto de recuperación:
-
-<WalletCodeExample>
-
-```typescript
-const server1Key = "server1";
-const server1 = {
-  endpoint: "recovery-example.com",
-  authEndpoint: "auth-example.com",
-  homeDomain: "test-domain",
-};
-
-const server2Key = "server2";
-const server2 = {
-  endpoint: "recovery-example2.com",
-  authEndpoint: "auth-example2.com",
-  homeDomain: "test-domain2",
-};
-
-const recovery = wallet.recovery({
-  servers: { [server1Key]: server1, [server2Key]: server2 },
-});
-```
-
-```kotlin
-val first = RecoveryServerKey("first")
-val second = RecoveryServerKey("second")
-val firstServer = RecoveryServer("recovery.example.com", "auth.example.com", "example.com")
-val secondServer = RecoveryServer("recovery2.example.com", "auth2.example.com", "example.com")
-val servers = mapOf(first to firstServer, second to secondServer)
-val recovery = wallet.recovery(servers)
-```
-
-```dart
-var first = RecoveryServerKey("first");
-var second = RecoveryServerKey("second");
-var firstServer = RecoveryServer("https://recovery.example1.com", "https://auth.example1.com", "recovery.example1.com");
-var secondServer = RecoveryServer("https://recovery.example2.com", "https://auth.example2.com", "recovery.example2.com");
-var servers = {first:firstServer, second:secondServer};
-var recovery = wallet.recovery(servers);
-```
-
-```swift
-let first = RecoveryServerKey(name: "first")
-let second = RecoveryServerKey(name: "second")
-
-let firstServer = RecoveryServer(endpoint:"https://recovery.example1.com",
-                                authEndpoint:"https://auth.example1.com",
-                                homeDomain:"recovery.example1.com")
-
-let secondServer = RecoveryServer(endpoint:"https://recovery.example2.com",
-                                  authEndpoint:"https://auth.example2.com",
-                                  homeDomain:"recovery.example2.com")
-
-let servers = [first: firstServer, second:secondServer]
-
-let recovery = wallet.recovery(servers: servers)
-```
-
-</WalletCodeExample>
-
-A continuación, necesitamos definir identidades SEP-30. En este ejemplo vamos a crear una identidad para ambos servidores. Registrar una identidad le dice al servidor de recuperación qué identidades están autorizadas para acceder a la cuenta.
-
-<WalletCodeExample>
-
-```typescript
-const identity1 = {
-  role: RecoveryRole.OWNER,
-  authMethods: [
-    {
-      type: RecoveryType.STELLAR_ADDRESS,
-      value: recoveryKp.publicKey,
-    },
-  ],
-};
-
-const identity2 = {
-  role: RecoveryRole.OWNER,
-  authMethods: [
-    {
-      type: RecoveryType.EMAIL,
-      value: "my-email@example.com",
-    },
-  ],
-};
-```
-
-```kotlin
-  val identity1 = listOf(RecoveryAccountIdentity(
-        RecoveryRole.OWNER,
-        listOf(RecoveryAccountAuthMethod(RecoveryType.STELLAR_ADDRESS, recoveryKp.address))
-      )
-    )
-
-    val identity2 = listOf(RecoveryAccountIdentity(
-        RecoveryRole.OWNER,
-        listOf(RecoveryAccountAuthMethod(RecoveryType.EMAIL, "my-email@example.com"))
-      )
-    )
-```
-
-```dart
-var identity1 = [
-  RecoveryAccountIdentity(RecoveryRole.owner, [
-    RecoveryAccountAuthMethod(RecoveryType.stellarAddress, recoveryKp.address)
-  ])
-];
-
-var identity2 = [
-  RecoveryAccountIdentity(RecoveryRole.owner,
-      [RecoveryAccountAuthMethod(RecoveryType.email, "my-email@example.com")])
-];
-```
-
-```swift
-let identity1 = [
-    RecoveryAccountIdentity(role:RecoveryRole.owner,
-                            authMethods: [RecoveryAccountAuthMethod(type:RecoveryType.stellarAddress,
-                                                                    value:recoveryKp.address)])
-]
-
-let identity2 = [
-    RecoveryAccountIdentity(role:RecoveryRole.owner,
-                            authMethods: [RecoveryAccountAuthMethod(type:RecoveryType.email,
-                                                                    value:"my-email@example.com")])
-]
-```
-
-</WalletCodeExample>
-
-Aquí, la clave de stellar y el correo electrónico se utilizan como métodos de recuperación. Otros servidores de recuperación pueden soportar el teléfono como método de recuperación también.
-
-Puedes leer más sobre identidades SEP-30 [aquí](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md#common-request-fields)
-
-A continuación, creemos una cuenta recuperable:
-
-<WalletCodeExample>
-
-```typescript
-const config = {
-  accountAddress: accountKp,
-  deviceAddress: deviceKp,
-  accountThreshold: { low: 10, medium: 10, high: 10 },
-  accountIdentity: { [server1Key]: [identity1], [server2Key]: [identity2] },
-  signerWeight: { device: 10, recoveryServer: 5 },
-};
-const recoverableWallet = await recovery.createRecoverableWallet(config);
-```
-
-```kotlin
-  val recoverableWallet =
-    recovery.createRecoverableWallet(
-      RecoverableWalletConfig(
-        accountKp,
-        deviceKp,
-        AccountThreshold(10, 10, 10),
-        mapOf(first to identity1, second to identity2),
-        SignerWeight(10, 5)
-      )
-    )
-```
-
-```dart
-var recoverableWallet = await recovery.createRecoverableWallet(
-    RecoverableWalletConfig(
-        accountKp,
-        deviceKp,
-        AccountThreshold(10, 10, 10),
-        {first: identity1, second: identity2},
-        SignerWeight(10, 5)
-    )
-);
-```
-
-```swift
-let config = RecoverableWalletConfig(accountAddress: accountKp,
-                                    deviceAddress: deviceKp,
-                                    accountThreshold: AccountThreshold(low: 10, medium: 10, high: 10),
-                                    accountIdentity: [first : identity1, second: identity2],
-                                    signerWeight: SignerWeight(device: 10, recoveryServer: 5))
-
-let recoverableWallet = try await recovery.createRecoverableWallet(config: config)
-```
-
-</WalletCodeExample>
-
-Con los parámetros dados, esta función creará una transacción que hará:
-
-1. Establecer `deviceKp` como la clave de cuenta principal. Ten en cuenta que la clave maestra perteneciente a `accountKp` estará bloqueada. `deviceKp` debe usarse como un firmante principal en su lugar.
-2. Establecer todos los umbrales de operación en 10. Puedes leer más acerca del umbral en la [documentación](../../../learn/fundamentals/transactions/signatures-multisig.mdx#thresholds)
-3. Usar identidades que se definieron antes en ambos servidores. (Eso significa, que ambos servidores aceptarán la autenticación SEP-10 a través de `recoveryKp` como un método de autenticación)
-4. Establecer el peso de clave del dispositivo en 10, y el peso del servidor de recuperación en 5. Dado estos umbrales de cuenta, ambos servidores deben ser usados para recuperar la cuenta, ya que una transacción firmada por uno solo tendrá un peso de 5, el cual no es suficiente para cambiar la clave de la cuenta.
-
-Finalmente, firma y envía la transacción a la red:
-
-<WalletCodeExample>
-
-```typescript
-recoverableWallet.transaction.sign(accountKp.keypair);
-
-await stellar.submitTransaction(recoverableWallet.transaction);
-```
-
-```kotlin
-  val tx = recoverableWallet.transaction.sign(accountKp)
-
-  wallet.stellar().submitTransaction(tx)
-```
-
-```dart
-var transaction = recoverableWallet.transaction;
-transaction.sign(accountKp.keyPair, flutter_sdk.Network.TESTNET);
-await wallet.stellar().submitTransaction(transaction);
-```
-
-```swift
-let transaction = recoverableWallet.transaction
-try transaction.sign(keyPair: accountKp.keyPair, network: Network.testnet)
-try await wallet.stellar.submitTransaction(signedTransaction: transaction)
-```
-
-</WalletCodeExample>
-
-## Obtener Información de la Cuenta
-
-Puedes obtener información de la cuenta desde uno o más servidores. Para hacerlo, primero necesitamos autenticar con un servidor de recuperación usando el método de autenticación SEP-10:
-
-<WalletCodeExample>
-
-```typescript
-const authToken = await recovery
-  .sep10Auth(server1Key)
-  .authenticate({ accountKp: recoveryKp });
-```
-
-```kotlin
-  val auth1 = recovery.sep10Auth(first).authenticate(recoveryKp)
-```
-
-```dart
-var sep10 = await recovery.sep10Auth(first);
-var authToken = await sep10.authenticate(recoveryKp);
-```
-
-```swift
-let sep10 = try await recovery.sep10Auth(key: first)
-let authToken = try await sep10.authenticate(userKeyPair: recoveryKp)
-```
-
-</WalletCodeExample>
-
-A continuación, obtiene información de la cuenta utilizando los tokens de autenticación:
-
-<WalletCodeExample>
-
-```typescript
-const accountResp = await recovery.getAccountInfo(accountKp, {
-  [server1Key]: authToken,
-});
-```
-
-```kotlin
-  val accountInfo = recovery.getAccountInfo(account, mapOf(first to auth1))
-
-  println("Recoverable info: $accountInfo")
-```
-
-```dart
-var accountInfo = await recovery.getAccountInfo(accountKp, {first: authToken.jwt});
-```
-
-```swift
-let accountInfo = try await recovery.getAccountInfo(accountAddress: accountKp,
-                                                    auth: [first:auth1Token.jwt])
-```
-
-</WalletCodeExample>
-
-Nuestra segunda identidad utiliza un correo electrónico como método de autenticación. Para eso no podemos usar un token de autenticación [SEP-10] para ese servidor. En cambio, necesitamos usar un token que vincule el correo electrónico al usuario. Por ejemplo, los tokens de Firebase son un buen caso de uso para esto. Para usar esto, el servidor de firmante de recuperación necesita estar preparado para manejar este tipo de tokens.
-
-Obtener información de la cuenta usando estos tokens es lo mismo que antes.
-
-<WalletCodeExample>
-
-```typescript
-// get token from firebase
-const firebaseToken = AuthToken.from(<firebase token string>)
-
-const accountResp = await recovery.getAccountInfo(accountKp, {
-  [server2Key]: firebaseToken,
-});
-```
-
-```kotlin
-  // get token from firebase
-  val firebaseToken = AuthToken.from(<firebase token string>)
-
-  val accountInfo = recovery.getAccountInfo(account, mapOf(second to firebaseToken))
-
-  println("Recoverable info: $accountInfo")
-```
-
-```dart
-var accountInfo = await recovery.getAccountInfo(accountKp, {second: <other token string>});
-```
-
-```swift
-let accountInfo = try await recovery.getAccountInfo(accountAddress: accountKp,
-                                                    auth: [second:<other token string>])
-```
-
-</WalletCodeExample>
-
-## Recuperar Billetera
-
-Supongamos que hemos perdido nuestra clave de dispositivo y necesitamos recuperar nuestra billetera.
-
-Primero, necesitamos autenticar con ambos servidores de recuperación:
-
-<WalletCodeExample>
-
-```typescript
-const authToken1 = await recovery
-  .sep10Auth(server1Key)
-  .authenticate({ accountKp: recoveryKp });
-
-// get firebase token using firebase
-const firebaseToken = AuthToken.from(<firebase token string>)
-```
-
-```kotlin
-  val auth1 = recovery.sep10Auth(first).authenticate(recoveryKp)
-
-  // get firebase token using firebase
-  val firebaseToken = AuthToken.from(<firebase token string>)
-```
-
-```dart
-var sep10 = await recovery.sep10Auth(first);
-var authToken = await sep10.authenticate(recoveryKp);
-
-var auth1 = authToken.jwt;
-var auth2 = "..."; // get other token e.g. firebase token
-```
-
-```swift
-let sep10 = try await recovery.sep10Auth(key: first)
-let authToken = try await sep10.authenticate(userKeyPair: recoveryKp)
-
-let auth1 = authToken.jwt
-let auth2 = "..."; // get other token e.g. firebase token
-```
-
-</WalletCodeExample>
-
-Necesitamos conocer las direcciones de los firmantes de recuperación que se utilizarán para firmar la transacción. Puedes obtenerlas de la billetera recuperable que creamos antes (`recoverableWallet.signers`), o mediante la obtención de información de la cuenta desde los servidores de recuperación.
-
-<WalletCodeExample>
-
-```typescript
-const recoverySignerAddress1 = recoverableWallet.signers[0];
-const recoverySignerAddress2 = recoverableWallet.signers[1];
-```
-
-```kotlin
-  val recoverySigners = recoverableWallet.signers
-```
-
-```dart
-var recoverySigners = recoverableWallet.signers;
-```
-
-```swift
-let recoverySigners = recoverableWallet.signers
-```
-
-</WalletCodeExample>
-
-A continuación, crea una nueva clave de dispositivo y recupera una transacción firmada que reemplace la clave de dispositivo:
-
-<WalletCodeExample>
-
-```typescript
-const newDeviceKp = accountService.createKeypair();
-
-const serverAuth = {
-  [server1Key]: {
-    signerAddress: recoverySignerAddress1,
-    authToken1,
-  },
-  [server2Key]: {
-    signerAddress: recoverySignerAddress2,
-    firebaseToken,
-  },
-};
-
-const recoverTxn = await recovery.replaceDeviceKey(
-  accountKp,
-  newDeviceKp,
-  serverAuth,
-);
-```
-
-```kotlin
-  val newKey = wallet.stellar().account().createKeyPair()
-
-  val serverAuth = mapOf(
-    first to RecoveryServerSigning(recoverySigners[0], auth1),
-    second to RecoveryServerSigning(recoverySigners[1], firebaseToken)
-  )
-
-  val signedReplaceKeyTransaction =
-    recovery.replaceDeviceKey(
-      accountKp,
-      newKey,
-      serverAuth
-    )
-```
-
-```dart
-var newKey = wallet.stellar().account().createKeyPair();
-var serverAuth = {
-  first: RecoveryServerSigning(recoverySigners[0], auth1),
-  second: RecoveryServerSigning(recoverySigners[1], auth2)
-};
-
-var signedReplaceKeyTx = await recovery.replaceDeviceKey(accountKp, newKey, serverAuth);
-```
-
-```swift
-let newKey = wallet.stellar.account.createKeyPair()
-let serverAuth = [
-    first: RecoveryServerSigning(signerAddress: recoverySigners[0] , authToken: auth1),
-    second: RecoveryServerSigning(signerAddress: recoverySigners[1] , authToken: auth2),
-]
-
-let signedReplaceKeyTx = try await recovery.replaceDeviceKey(account: accountKp,
-                                                             newKey: newKey,
-                                                             serverAuth: serverAuth)
-```
-
-</WalletCodeExample>
-
-Llamar a esta función creará una transacción que bloquea la clave de dispositivo anterior y la reemplaza con tu nueva clave (teniendo el mismo peso que la antigua). Ambos firmantes de recuperación habrán firmado la transacción.
-
-La clave de dispositivo perdida se deduce automáticamente si no se proporciona. Un firmante será considerado una clave de dispositivo, si una de estas condiciones coincide:
-
-1. Es el único firmante que no está en `serverAuth`.
-2. Todos los firmantes en `serverAuth` tienen el mismo peso, y el firmante potencial es el único que tiene un peso diferente.
-
-Ten en cuenta que la cuenta creada arriba coincidirá con el primer criterio. Si se usara el esquema 2-3, entonces el segundo criterio coincidiría. (En el esquema 2-3, se utilizan 3 servidores y 2 de ellos son suficientes para recuperar la clave. Este es un enfoque recomendado.)
-
-Nota: también puedes usar funciones de bajo nivel `signWithRecoveryServers` para firmar transacciones arbitrarias.
-
-Finalmente, es hora de enviar la transacción:
-
-<WalletCodeExample>
-
-```typescript
-await stellar.submitTransaction(recoverTxn);
-```
-
-```kotlin
-  wallet.stellar().submitTransaction(signedReplaceKeyTransaction)
-```
-
-```dart
-await wallet.stellar().submitTransaction(signedReplaceKeyTx);
-```
-
-```swift
-try await wallet.stellar.submitTransaction(signedTransaction: signedReplaceKeyTx)
-```
-
-</WalletCodeExample>
-
-[sep-30]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep38.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep38.mdx
deleted file mode 100644
index cae7325079..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep38.mdx
+++ /dev/null
@@ -1,280 +0,0 @@
----
-title: Cita
-sidebar_position: 70
----
-
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-
-<Header WIPLangs={["kotlin"]} />
-
-El estándar [SEP-38] define una forma para que los anchors proporcionen citas para el exchange de un activo off-chain y un activo on-chain diferente, y viceversa. Las citas pueden ser [indicativas](https://www.investopedia.com/terms/i/indicativequote.asp) o [firmes](https://www.investopedia.com/terms/f/firmquote.asp). Cuándo se utiliza cada una se explica en las secciones a continuación.
-
-## Creando Objeto Sep-38
-
-Comencemos creando un objeto sep38, que utilizaremos para todas las interacciones de SEP-38. La autenticación es opcional para estas solicitudes y depende de la implementación del anchor. Para nuestro ejemplo, la incluiremos.
-
-La autenticación se realiza utilizando [Sep-10], y añadimos el token de autenticación al objeto sep38.
-
-<WalletCodeExample>
-
-```typescript
-const accountKp = ... // our account keypair
-
-const auth = await anchor.sep10();
-const authToken = await auth.authenticate({ accountKp });
-const sep38 = anchor.sep38(authToken);
-```
-
-```dart
-var accountKp = ... // our account keypair
-
-var auth = await anchor.sep10();
-var authToken = await auth.authenticate(accountKp);
-var sep38 = anchor.sep38(authToken: authToken);
-```
-
-```swift
-let accountKp = ... // our account keypair
-
-let sep10 = try await anchor.sep10
-let authToken = try await sep10.authenticate(userKeyPair: accountKp)
-let sep38 = try await anchor.sep38(authToken: authToken)
-```
-
-</WalletCodeExample>
-
-## Obtener información del ancla
-
-Primero, obtengamos información sobre el soporte del ancla para [SEP-38]. La respuesta proporciona qué activos en cadena de Stellar y activos fuera de cadena están disponibles para el comercio.
-
-<WalletCodeExample>
-
-```typescript
-const resp = await sep38.info();
-```
-
-```dart
-var resp = await sep38.info();
-```
-
-```swift
-let resp = try await sep38.info
-```
-
-</WalletCodeExample>
-
-Por ejemplo, una respuesta se verá así. Los identificadores de activos se describen a continuación en [Formato de Identificación de Activos](#asset-identification-format).
-
-```
-{
-  assets: [
-    {
-      asset: 'stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B'
-    },
-    {
-      asset: 'iso4217:USD',
-      country_codes: [Array],
-      sell_delivery_methods: [Array],
-      buy_delivery_methods: [Array]
-    }
-  ]
-}
-```
-
-## Formato de Identificación de Activos
-
-Antes de llamar a otros endpoints, debemos entender el esquema utilizado para identificar activos en este protocolo. Se utiliza el siguiente formato:
-
-```
-<scheme>:<identifer>
-```
-
-Los valores de esquema actualmente aceptados son `stellar` para activos de Stellar, y `iso4217` para monedas fiduciarias.
-
-Por ejemplo, para identificar USDC en Stellar utilizaríamos:
-
-```
-stellar:USDC:GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN
-```
-
-Y para identificar el USD fiduciario utilizaríamos:
-
-```
-iso4217:USD
-```
-
-Se puede encontrar una explicación adicional en [especificación SEP-38](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format).
-
-## Obtener precios
-
-Ahora obtengamos precios [indicativos](https://www.investopedia.com/terms/i/indicativequote.asp) del ancla a cambio de un activo dado. Este es un precio indicativo. El precio real se calculará en el momento de la conversión una vez que el ancla reciba los fondos de un usuario.
-
-En nuestro ejemplo estamos obteniendo precios para vender 5 USD fiduciarios.
-
-<WalletCodeExample>
-
-```typescript
-const resp = await sep38.prices({
-  sell_asset: "iso4217:USD",
-  sell_amount: "5",
-});
-```
-
-```dart
-var resp = await sep38.prices(
-  sellAsset: "iso4217:USD",
-  sellAmount: "5",
-);
-```
-
-```swift
-let response = try await sep38.prices(sellAsset: "iso4217:USD",
-                                      sellAmount: "5")
-```
-
-</WalletCodeExample>
-
-La respuesta proporciona los precios de los activos para intercambiar el activo de venta solicitado. Por ejemplo, una respuesta se verá así:
-
-```
-{
-  "buy_assets": [
-    {
-      "asset": "stellar:USDC:GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN",
-      "price": "5.42",
-      "decimals": 7
-    }
-  ]
-}
-```
-
-## Obtener Precio
-
-A continuación, obtengamos un precio [indicativo](https://www.investopedia.com/terms/i/indicativequote.asp) para un par determinado.
-
-Una vez más, este es un valor indicativo. El precio real se calculará en el momento de la conversión una vez que el ancla reciba los fondos de un usuario.
-
-Debe proporcionarse un valor de `sellAmount` o `buyAmount`, pero no ambos. Y `context` se refiere a qué contexto de SEP de Stellar se utilizará (es decir, `sep6`, `sep24` o `sep31`).
-
-<WalletCodeExample>
-
-```typescript
-const resp = await sep38.price({
-  sellAsset: "iso4217:USD",
-  buyAsset:
-    "stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B",
-  sellAmount: "5",
-  context: "sep6",
-});
-```
-
-```dart
-var resp = await sep38.price(
-  sellAsset: "iso4217:USD",
-  buyAsset:
-    "stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B",
-  sellAmount: "5",
-  context: "sep6",
-);
-```
-
-```swift
-let resp = try await sep38.price(
-    context: "sep6",
-    sellAsset: "iso4217:USD",
-    buyAsset: "stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B",
-    sellAmount: "5")
-```
-
-</WalletCodeExample>
-
-La respuesta proporciona información para intercambiar estos activos. Por ejemplo, una respuesta se verá así:
-
-```
-{ price: '1.18', sell_amount: '5.00', buy_amount: '4.24' }
-```
-
-## Publicar cotización
-
-Ahora obtengamos una cotización [firme](https://www.investopedia.com/terms/f/firmquote.asp) del ancla. A diferencia de los endpoints anteriores, esta cotización es almacenada por el ancla durante un cierto período de tiempo. Mostraremos cómo podemos recuperar la cotización más tarde.
-
-El cuerpo de la solicitud es similar a la llamada `.price()` que hicimos anteriormente.
-
-<WalletCodeExample>
-
-```typescript
-const requestResp = await sep38.requestQuote({
-  sell_asset: "iso4217:USD",
-  buy_asset:
-    "stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B",
-  sell_amount: "5",
-  context: "sep6",
-});
-```
-
-```dart
-var requestResp = await sep38.requestQuote(
-  sellAsset: "iso4217:USD",
-  buyAsset:
-    "stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B",
-  sellAmount: "5",
-  context: "sep6",
-);
-```
-
-```swift
-let resp = try await sep38.requestQuote(
-    context: "sep6",
-    sellAsset: "iso4217:USD",
-    buyAsset: "stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B",
-    sellAmount: "5")
-```
-
-</WalletCodeExample>
-
-Sin embargo, ahora la respuesta proporciona un `id` que podemos utilizar para identificar la cotización. El campo `expires_at` nos indica cuánto tiempo el ancla esperará para recibir fondos por esta cotización.
-
-Una respuesta de ejemplo se verá así:
-
-```
-{
-  id: '019417b3-91ce-473a-929f-15e19470733a',
-  price: '0.81',
-  expires_at: '2024-01-03T20:34:48.190481Z',
-  sell_asset: 'iso4217:USD',
-  buy_asset: 'stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B',
-  sell_amount: '5.00',
-  buy_amount: '6.17'
-}
-```
-
-## Obtener cotización
-
-Ahora obtengamos la cotización solicitada anteriormente. Para hacerlo, utilizamos el `id` de la respuesta de `.requestQuote()`.
-
-<WalletCodeExample>
-
-```typescript
-const quoteId = requestResp.id;
-const getResp = await sep38.getQuote(quoteId);
-```
-
-```dart
-var quoteId = requestResp.id;
-var getResp = await sep38.getQuote(quoteId);
-```
-
-```swift
-let quoteId = requestResp.id
-let getResp = try await sep38.getQuote(quoteId: quoteId)
-```
-
-</WalletCodeExample>
-
-La respuesta debería coincidir con la proporcionada por `.requestQuote()` que hicimos anteriormente.
-
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep6.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep6.mdx
deleted file mode 100644
index 2eb1bee47f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep6.mdx
+++ /dev/null
@@ -1,596 +0,0 @@
----
-title: Depósito y Retirada Programática
-sidebar_position: 60
----
-
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-
-<Header WIPLangs={["kotlin"]} />
-
-El estándar [SEP-6] define una forma en que los anchors y billeteras pueden interactuar en nombre de los usuarios. Las billeteras utilizan este estándar para facilitar intercambios entre activos on-chain (como stablecoins) y activos off-chain (como fiat, u otros activos de red como BTC).
-
-Por favor, nota que esto es para depósitos y retiradas _programáticas_. Para depósitos y retiradas alojados, donde el anchor interactúa con billeteras de manera interactiva usando un popup, por favor consulta [Depósito y Retirada Alojados](./sep24.mdx).
-
-## Obtener Información del Anchor
-
-Comencemos creando un objeto sep6, que usaremos para todas las interacciones SEP-6:
-
-<WalletCodeExample>
-
-```typescript
-const sep6 = anchor.sep6();
-```
-
-```dart
-var sep6 = anchor.sep6();
-```
-
-```swift
-let sep6 = anchor.sep6
-```
-
-</WalletCodeExample>
-
-Primero, obtengamos información sobre el soporte del ancla para [SEP-6]. Esta solicitud no requiere autenticación y devolverá información genérica, como las monedas admitidas y las funciones admitidas por el ancla. Puedes obtener una lista completa de campos devueltos en la [especificación SEP-6](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md#info).
-
-<WalletCodeExample>
-
-```typescript
-const info = await sep6.info();
-```
-
-```dart
-var info = await sep6.info();
-```
-
-```swift
-let info = try await sep6.info()
-```
-
-</WalletCodeExample>
-
-## Iniciar un depósito
-
-Antes de comenzar, asegúrate de haberte conectado al ancla y de haber recibido un token de autenticación, como se describe en la guía de billeteras de [Autenticación Stellar]. Usaremos `authToken` en los ejemplos a continuación como el token de autenticación [SEP-10], obtenido anteriormente.
-
-Para iniciar una operación, necesitamos conocer un activo. Puedes codificar esto de forma fija. Asegúrate de que sea uno que esté incluido en la respuesta de información anterior.
-
-:::info
-
-Antes de comenzar con el flujo de depósito, asegúrate de que la cuenta del usuario haya [establecido una línea de confianza](./stellar.mdx#modify-assets-trustlines) para el activo con el que estás trabajando.
-
-:::
-
-Comencemos con un depósito básico. Usaremos `account` para representar la clave pública de nuestra cuenta.
-
-<WalletCodeExample>
-
-```typescript
-const deposit = await sep6.deposit({
-  authToken,
-  params: {
-    asset_code,
-    account,
-  },
-});
-```
-
-```dart
-var deposit = await anchor.sep6().deposit(
-  Sep6DepositParams(assetCode: assetCode, account: accountId),
-  authToken,
-);
-```
-
-```swift
-let params = Sep6DepositParams(assetCode: assetCode, account: account)
-let depositResponse = try await anchor.sep6.deposit(params: params, authToken: authToken)
-
-switch depositResponse {
-case .depositSuccess(let how, let id, let eta, let minAmount, let maxAmount, let feeFixed, let feePercent, let extraInfo, let instructions):
- // ...
-}
-```
-
-</WalletCodeExample>
-
-Hay varios tipos de respuestas, dependiendo de si el ancla necesita más información. Todos los depósitos y retiros tendrán estos mismos tipos de respuesta:
-
-### 1. Respuesta exitosa
-
-Si la respuesta es exitosa (HTTP 200), entonces el ancla está procesando el depósito. Si necesita información adicional, la comunicará al proporcionar la [información de la transacción](#getting-transaction-info).
-
-### 2. Aún procesando o denegado
-
-Si se devuelve un HTTP 403 con datos: `customer_info_status`, significa que la acción aún se está procesando o no ha sido aceptada. En este caso, el campo `more_info_url` debería tener un enlace que describa los próximos pasos.
-
-Un ejemplo de respuesta:
-
-```
-{
-  "type": "customer_info_status",
-  "status": "denied",
-  "more_info_url": "https://api.example.com/kycstatus?account=GACW7NONV43MZIFHCOKCQJAKSJSISSICFVUJ2C6EZIW5773OU3HD64VI"
-}
-```
-
-### 3. Necesita más información KYC
-
-Otra respuesta común es un HTTP 403, con la respuesta: `non_interactive_customer_info_needed`. En este caso, el ancla necesita más información KYC a través de [SEP-12].
-
-Un ejemplo de respuesta:
-
-```
-{
-  "type": "non_interactive_customer_info_needed",
-  "fields" : ["family_name", "given_name", "address", "tax_id"]
-}
-```
-
-Mostremos cómo una billetera puede manejar esta situación. Primero, obtenemos el objeto de respuesta del depósito. Si la respuesta incluye este error, entonces podemos ver qué campos faltantes está requiriendo el ancla.
-
-<WalletCodeExample>
-
-```typescript
-if (deposit.type === "non_interactive_customer_info_needed") {
-  // handle displaying the missing fields to the user
-  console.log(deposit.fields);
-}
-```
-
-```dart
-if (deposit is Sep6MissingKYC) {
-  print(deposit.fields);
-}
-```
-
-```swift
-switch depositResponse {
-case .missingKYC(let fields):
-   //...
-}
-```
-
-</WalletCodeExample>
-
-La billetera tendrá que manejar la visualización al usuario sobre qué campos están faltando. Y luego, para agregar esos campos, podemos usar la clase sep12 así:
-
-<WalletCodeExample>
-
-```typescript
-const sep12 = await anchor.sep12(authToken);
-
-// adding the missing kyc info (sample data)
-await sep12.add({
-  sep9Info: {
-    family_name: "smith",
-    given_name: "john",
-    address: "123 street",
-    tax_id: "123",
-  },
-});
-```
-
-```dart
-var sep12 = await anchor.sep12(authToken);
-
-// adding the missing kyc info (sample data)
-var sep9Info = {
-  'family_name': 'smith',
-  'given_name': 'john',
-  'address': '123 street',
-  'tax_id': '123',
-};
-
-var addResponse = await sep12.add(sep9Info);
-```
-
-```swift
-let sep12 = try await anchor.sep12(authToken: authToken)
-
-// adding the missing kyc info (sample data)
-let sep9Info = [
- "family_name" : "smith",
- "given_name" : "john",
- "address" : "123 street",
- "tax_id": "123",
-]
-
-let addResponse = try await sep12.add(sep9Info: sep9Info)
-```
-
-</WalletCodeExample>
-
-Luego, podemos volver a llamar al método de depósito como antes y debería ser exitoso.
-
-Más información sobre el envío de información KYC utilizando [SEP-12] se puede encontrar en [Proporcionar información KYC](#providing-kyc-info).
-
-## Proporcionar información KYC
-
-Un ancla puede responder a una solicitud de depósito o retiro diciendo que necesita información KYC adicional. Para facilitar esto, [SEP-6] admite agregar información KYC del cliente a través de [SEP-12]. El usuario puede enviar la información requerida utilizando el objeto sep12 como se muestra a continuación.
-
-Vamos a agregar algo de información KYC para nuestra cuenta utilizando datos de ejemplo. Los datos binarios (por ejemplo, datos de imagen) deben enviarse en un campo separado. Los campos permitidos que se pueden enviar al ancla se describen en [SEP-9].
-
-<WalletCodeExample>
-
-```typescript
-const sep12 = await anchor.sep12(authToken);
-
-await sep12.add({
-  sep9Info: {
-    first_name: "john",
-    last_name: "smith",
-    email_address: "123@gmail.com",
-    bank_number: "12345",
-    bank_account_number: "12345",
-  },
-  sep9BinaryInfo: {
-    photo_id_front: Buffer.from("./path/to/image/front"),
-    photo_id_back: Buffer.from("./path/to/image/back"),
-  },
-});
-```
-
-```dart
-var sep12 = await anchor.sep12(authToken);
-
-var sep9Info = {
-  'first_name': 'john',
-  'last_name': 'smith',
-  'email_address': '123@gmail.com',
-  'bank_number': '12345',
-  'bank_account_number': '12345',
-};
-
-var photoIdFront = await Util.readFile('./path/to/image/front');
-var photoIdBack = await Util.readFile('./path/to/image/back');
-
-var sep9Files = {
-  'photo_id_front': photoIdFront,
-  'photo_id_back': photoIdBack,
-};
-
-await sep12.add(sep9Info, sep9Files: sep9Files);
-```
-
-```swift
-let sep12 = try await anchor.sep12(authToken: authToken)
-
-let sep9Info = [
-    "first_name" : "john",
-    "last_name" : "smith",
-    "email_address" : "123@gmail.com",
-    "bank_number" : "12345",
-    "bank_account_number" : "12345",
-]
-
-let photoIdFront:Data = // ...
-let photoIdBack:Data = // ...
-
-let sep9Files = [
-  "photo_id_front": photoIdFront,
-  "photo_id_back": photoIdBack,
-]
-
-let addResponse = try await sep12.add(sep9Info: sep9Info, sep9Files: sep9Files)
-```
-
-</WalletCodeExample>
-
-## Iniciar un retiro
-
-Iniciar un retiro es similar a un depósito y tiene los mismos tipos de respuesta que se describieron anteriormente.
-
-<WalletCodeExample>
-
-```typescript
-const resp = await sep6.withdraw({
-  authToken,
-  params: {
-    asset_code: "SRT",
-    account: accountKp.publicKey,
-    type: "bank_account",
-    dest: "123",
-    dest_extra: "12345",
-  },
-});
-```
-
-```dart
-var params = Sep6WithdrawParams(
-    assetCode: 'SRT',
-    account: accountId,
-    type: 'bank_account',
-    dest: '123',
-    destExtra: '12345',
-);
-
-var resp = await anchor.sep6().withdraw(params, authToken);
-```
-
-```swift
-let params = Sep6WithdrawParams(
-  assetCode: "SRT",
-  account: accountId,
-  type: "bank_account",
-  dest: "123",
-  destExtra: "12345")
-
-let resp = try await anchor.sep6.withdraw(params: withdrawParams,
-                                          authToken: authToken)
-```
-
-</WalletCodeExample>
-
-## Obtener información de intercambio
-
-Si el ancla admite cotizaciones de [SEP-38], puede admitir depósitos que hagan un puente entre activos no equivalentes. Por ejemplo, un ancla recibe BRL a través de transferencias bancarias y a cambio envía USDC (de valor equivalente menos tarifas) al usuario en Stellar.
-
-Las funciones de intercambio sep6 permiten a un usuario iniciar un depósito o retiro de intercambio con el ancla, y el ancla puede comunicar los próximos pasos al usuario.
-
-Primero, comencemos un depósito de intercambio con datos de ejemplo. Los activos se describen utilizando el esquema [SEP-38].
-
-<WalletCodeExample>
-
-```typescript
-const resp = await sep6.depositExchange({
-  authToken,
-  params: {
-    destination_asset:
-      "stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B",
-    source_asset: "iso4217:USD",
-    amount: "10",
-  },
-});
-```
-
-```dart
-var params = Sep6DepositExchangeParams(
-    destinationAssetCode: 'SRT',
-    sourceAssetId: FiatAssetId('USD'),
-    amount: '10',
-);
-
-var resp = await anchor.sep6().depositExchange(params, authToken);
-```
-
-```swift
-let params = Sep6DepositExchangeParams(
-  destinationAssetCode: "SRT",
-  sourceAssetId: FiatAssetId(id: "USD"),
-  amount: "10")
-
-let resp = try await anchor.sep6.depositExchange(params: params,
-                                                 authToken: authToken)
-```
-
-</WalletCodeExample>
-
-La respuesta sigue los mismos tipos que todos los depósitos y retiros de SEP-6.
-
-Ahora vamos a crear un retiro de intercambio, que sigue el mismo formato que el depósito de intercambio. También especificamos que es una retirada de fondos desde una cuenta bancaria usando el campo `type`.
-
-<WalletCodeExample>
-
-```typescript
-const resp = await sep6.withdrawExchange({
-  authToken,
-  params: {
-    destination_asset: "iso4217:USD",
-    source_asset:
-      "stellar:SRT:GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B",
-    amount: "10",
-    type: "bank_account",
-  },
-});
-```
-
-```dart
-var params = Sep6WithdrawExchangeParams(
-    sourceAssetCode: 'SRT',
-    destinationAssetId: FiatAssetId('USD'),
-    amount: '10',
-    type: 'bank_account',
-);
-
-var resp = await anchor.sep6().withdrawExchange(params, authToken);
-```
-
-```swift
-let params = Sep6WithdrawExchangeParams(
-  sourceAssetCode: "SRT",
-  destinationAssetId: FiatAssetId("USD"),
-  amount: "10",
-  type: "bank_account")
-
-let resp = try await anchor.sep6.withdrawExchange(params: params,
-                                                  authToken: authToken)
-```
-
-</WalletCodeExample>
-
-La respuesta sigue los mismos tipos que todos los depósitos y retiros de SEP-6.
-
-## Obteniendo información de transacción
-
-En el flujo típico, la billetera obtendría datos de transacción para notificar a los usuarios sobre actualizaciones de estado. Esto se hace a través del [SEP-6] `GET /transaction` y `GET /transactions` endpoint.
-
-### Seguimiento de transacción
-
-Veamos cómo usar el sdk para rastrear los cambios en el estado de la transacción. Usaremos la clase `Watcher` para este propósito. Primero, inicialízala y comienza a rastrear una transacción.
-
-<WalletCodeExample>
-
-```typescript
-const watcher = anchor.sep6().watcher();
-
-const { stop, refresh } = watcher.watchOneTransaction({
-  authToken,
-  assetCode,
-  id: txId,
-  onSuccess,
-  onMessage,
-  onError,
-});
-```
-
-```dart
-var watcher = anchor.sep6.watcher();
-var result = watcher.watchOneTransaction(authToken, 'transaction id');
-
-result.controller.stream.listen(
-  (event) {
-    if (event is StatusChange) {
-      print('Status changed to ${event.status}. Transaction: ${event.transaction.id}');
-    } else if (event is ExceptionHandlerExit) {
-      print('Exception handler exited the job');
-    } else if (event is StreamControllerClosed) {
-      print('Stream controller closed. Job is done');
-    }
-  }
-);
-```
-
-```swift
-let watcher = anchor.sep6.watcher()
-let result = watcher.watchOneTransaction(authToken: token,
-                                         id: "transaction id")
-
-NotificationCenter.default.addObserver(self,
-                                       selector: #selector(handleEvent(_:)),
-                                       name: result.notificationName,
-                                       object: nil)
-
-/// ...
-@objc public func handleEvent(_ notification: Notification) {
-    if let statusChange = notification.object as? StatusChange {
-        print("Status change to \(statusChange.status.rawValue). Transaction: \(statusChange.transaction.id)")
-    } else if let _ = notification.object as? ExceptionHandlerExit {
-        print("Exception handler exited the job")
-    } else if let _ = notification.object as? NotificationsClosed {
-        print("Notifications closed. Job is done")
-    }
-}
-```
-
-</WalletCodeExample>
-
-Alternativamente, podemos rastrear múltiples transacciones para el mismo activo.
-
-<WalletCodeExample>
-
-```typescript
-const watcher = anchor.sep6().watcher();
-
-const { stop, refresh } = watcher.watchAllTransactions({
-  authToken,
-  assetCode,
-  onMessage,
-  onError,
-});
-```
-
-```dart
-var watcher = anchor.sep6.watcher();
-var result = watcher.watchAsset(authToken, asset);
-
-result.controller.stream.listen(
-  (event) {
-    if (event is StatusChange) {
-      print('Status changed to ${event.status}. Transaction: ${event.transaction.id}');
-    } else if (event is ExceptionHandlerExit) {
-      print('Exception handler exited the job');
-    } else if (event is StreamControllerClosed) {
-      print('Stream controller closed. Job is done');
-    }
-  }
-);
-```
-
-```swift
-let watcher = anchor.sep6.watcher()
-let result = watcher.watchAsset(authToken: token,
-                                asset: asset)
-
-NotificationCenter.default.addObserver(self,
-                                       selector: #selector(handleEvent(_:)),
-                                       name: result.notificationName,
-                                       object: nil)
-
-/// ...
-@objc public func handleEvent(_ notification: Notification) {
-    if let statusChange = notification.object as? StatusChange {
-        print("Status change to \(statusChange.status.rawValue). Transaction: \(statusChange.transaction.id)")
-    } else if let _ = notification.object as? ExceptionHandlerExit {
-        print("Exception handler exited the job")
-    } else if let _ = notification.object as? NotificationsClosed {
-        print("Notifications closed. Job is done")
-    }
-}
-```
-
-</WalletCodeExample>
-
-### Obteniendo transacción
-
-Mientras que la clase `Watcher` ofrece potentes capacidades de seguimiento, a veces es necesario simplemente obtener una transacción (o transacciones) una vez. La clase `Anchor` te permite obtener una transacción por ID, ID de transacción Stellar o ID de transacción externa:
-
-<WalletCodeExample>
-
-```typescript
-const transaction = await anchor
-  .sep6()
-  .getTransactionBy({ authToken, id: transactionId });
-```
-
-```dart
-var transaction = await anchor.sep6().getTransactionBy(
-    authToken: authToken,
-    id: transactionId,
-);
-```
-
-```swift
-let transaction = try await anchor.sep6.getTransactionBy(
-  authToken: authToken,
-  transactionId:transactionId)
-```
-
-</WalletCodeExample>
-
-También es posible obtener transacciones por el activo.
-
-<WalletCodeExample>
-
-```typescript
-const transactions = await anchor.sep6().getTransactionsForAsset({
-  authToken,
-  assetCode,
-});
-```
-
-```dart
-var transactions = await anchor.sep6().getTransactionsForAsset(
-  authToken: authToken,
-  assetCode: assetCode,
-);
-```
-
-```swift
-let transactions = try await anchor.sep6.getTransactionsForAsset(
-  authToken: authToken,
-  assetCode: assetCode)
-
-```
-
-</WalletCodeExample>
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[sep-12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[autenticación stellar]: ./sep10.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep7.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep7.mdx
deleted file mode 100644
index 0dcdc6d8d7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/sep7.mdx
+++ /dev/null
@@ -1,275 +0,0 @@
----
-title: Esquema URI para facilitar la firma delegada
-sidebar_position: 80
----
-
-import Header from "./component/header.mdx";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-
-<Header />
-
-El estándar [Sep-7] define una manera para que una aplicación que no es una billetera construya un esquema URI que represente una transacción específica para que una cuenta firme. El esquema utilizado es `web+stellar`, seguido de dos puntos. Ejemplo: `web+stellar:<operation>?<param1>=<value1>&<param2>=<value2>`
-
-## Operación Tx
-
-La operación tx representa una solicitud para firmar un sobre de transacción específico, con [algunos parámetros configurables].
-
-<WalletCodeExample>
-
-```typescript
-const sourceAccountKeyPair = "G...";
-const destinationAccountKeyPair = "G...";
-const txBuilder = await stellar.transaction({
-  sourceAddress: sourceAccountKeyPair,
-});
-const tx = txBuilder.createAccount(destinationAccountKeyPair).build();
-const xdr = encodeURIComponent(tx.toEnvelope().toXDR().toString("base64"));
-const callback = encodeURIComponent("https://example.com/callback");
-const txUri = `web+stellar:tx?xdr=${xdr}&callback=${callback}`;
-const uri = wallet.parseSep7Uri(txUri);
-// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
-```
-
-```dart
-final sourceAccountKeyPair = PublicKeyPair.fromAccountId('G...');
-final destinationAccountKeyPair = PublicKeyPair.fromAccountId('G...');
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-final tx = txBuilder.createAccount(destinationAccountKeyPair).build();
-final xdr = Uri.encodeComponent(tx.toEnvelopeXdrBase64());
-final callback = Uri.encodeComponent('https://example.com/callback');
-final txUri = 'web+stellar:tx?xdr=$xdr&callback=$callback';
-final uri = wallet.parseSep7Uri(txUri);
-// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
-```
-
-```swift
-let sourceAccountKeyPair = try PublicKeyPair(accountId: "G...")
-let destinationAccountKeyPair = try PublicKeyPair(accountId: "G...")
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.createAccount(newAccount: destinationAccountKeyPair).build()
-let xdr = try tx.encodedEnvelope().addingPercentEncoding(withAllowedCharacters: .urlHostAllowed) // url encoded
-let callback = "https://example.com/callback".addingPercentEncoding(withAllowedCharacters: .urlHostAllowed)  // url encoded
-let txUri = "web+stellar:tx?xdr=\(xdr!)&callback=\(callback!)"
-let uri = try wallet.parseSep7Uri(uri: txUri)
-// uri can be parsed and transaction can be signed/submitted by an application that implements Sep-7
-```
-
-</WalletCodeExample>
-
-Puedes establecer reemplazos que serán realizados en el xdr para campos específicos por la aplicación, estos serán añadidos en el [formato de representación de transacciones Sep-11] a la URI.
-
-<WalletCodeExample>
-
-```typescript
-const uri = new Sep7Tx(txUri);
-uri.addReplacement({
-  id: "X",
-  path: "sourceAccount",
-  hint: "account from where you want to pay fees",
-});
-```
-
-```dart
-final uri = wallet.parseSep7Uri(txUri);
-
-if (uri is Sep7Tx) {
-    uri.addReplacement(Sep7Replacement(
-        id: 'X',
-        path: 'sourceAccount',
-        hint: 'account from where you want to pay fees'));
-}
-```
-
-```swift
-let uri = try wallet.parseSep7Uri(uri: txUri)
-
-if let uri = uri as? Sep7Tx {
-    let replacement = Sep7Replacement(id:"X",
-                                      path:"sourceAccount",
-                                      hint: "account from where you want to pay fees")
-
-    uri.addReplacement(replacement: replacement)
-}
-```
-
-</WalletCodeExample>
-
-Puedes asignar parámetros después de crear la instancia inicial utilizando el setter apropiado para el parámetro.
-
-<WalletCodeExample>
-
-```typescript
-const sourceAccountKeyPair = "G...";
-const destinationAccountKeyPair = "G...";
-const txBuilder = await stellar.transaction({
-  sourceAddress: sourceAccountKeyPair,
-});
-const tx = txBuilder.createAccount(destinationAccountKeyPair).build();
-const uri = wallet.Sep7Tx.forTransaction(tx);
-uri.callback = "https://example.com/callback";
-uri.msg = "here goes a message";
-uri.toString(); // encodes everything and converts to a uri string
-```
-
-```dart
-final sourceAccountKeyPair = PublicKeyPair.fromAccountId('G...');
-final destinationAccountKeyPair = PublicKeyPair.fromAccountId('G...');
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-final tx = txBuilder.createAccount(destinationAccountKeyPair).build();
-
-final uri = Sep7Tx.forTransaction(tx);
-uri.setCallback('https://example.com/callback');
-uri.setMsg('here goes a message');
-uri.toString(); // encodes everything and converts to a uri string
-```
-
-```swift
-let sourceAccountKeyPair = try PublicKeyPair(accountId: "G...")
-let destinationAccountKeyPair = try PublicKeyPair(accountId: "G...")
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.createAccount(newAccount: destinationAccountKeyPair).build()
-
-let uri = try Sep7Tx(transaction: tx)
-uri.setCallback(callback: "https://example.com/callback")
-try uri.setMsg(msg: "here goes a message")
-let uriStr = uri.toString() // encodes everything and converts to a uri string
-```
-
-</WalletCodeExample>
-
-## Operación de pago
-
-La operación de pago representa una solicitud para pagar una dirección específica con un activo específico, independientemente del activo fuente utilizado por el pagador. Puedes [configurar parámetros] para construir la operación de pago.
-
-<WalletCodeExample>
-
-```typescript
-const destination = "G...";
-const assetIssuer = "G...";
-const assetCode = "USDC";
-const amount = "120.1234567";
-const memo = "memo";
-const message = encodeURIComponent("pay me with lumens");
-const originDomain = "example.com";
-const payUri = `web+stellar:pay?destination=${destination}&amount=${amount}&memo=${memo}&msg=${message}&origin_domain=${originDomain}&asset_issuer=${assetIssuer}&asset_code=${assetCode}`;
-const uri = parseSep7Uri(payUri);
-// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
-```
-
-```dart
-const destination = 'G...';
-const assetIssuer = 'G...';
-const assetCode = 'USDC';
-const amount = '120.1234567';
-const memo = 'memo';
-final message = Uri.encodeComponent('pay me with lumens');
-const originDomain = 'example.com';
-final payUri = 'web+stellar:pay?destination=$destination&amount=$amount&memo=$memo&msg=$message&origin_domain=$originDomain&asset_issuer=$assetIssuer&asset_code=$assetCode';
-final uri = Sep7.parseSep7Uri(payUri);
-// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
-```
-
-```swift
-let destination = "G..."
-let assetIssuer = "G..."
-let assetCode = "USDC"
-let amount = "120.1234567"
-let memo = "memo"
-let message = "pay me with lumens".addingPercentEncoding(withAllowedCharacters: .urlHostAllowed) // url encoded
-let originDomain = "example.com"
-let payUri = "web+stellar:pay?destination=\(destination)&amount=\(amount)&memo=\(memo)&msg=\(message!)&origin_domain=\(originDomain)&asset_issuer=\(assetIssuer)&asset_code=\(assetCode)"
-uri = try Sep7.parseSep7Uri(uri: payUri)
-// uri can be parsed and transaction can be built/signed/submitted by an application that implements Sep-7
-```
-
-</WalletCodeExample>
-
-Puedes asignar parámetros después de crear la instancia inicial utilizando el setter apropiado para el parámetro.
-
-<WalletCodeExample>
-
-```typescript
-const uri = wallet.Sep7Pay.forDestination("G...");
-uri.callback = "https://example.com/callback";
-uri.msg = "here goes a message";
-uri.assetCode = "USDC";
-uri.assetIssuer = "G...";
-uri.amount = "10";
-uri.toString(); // encodes everything and converts to a uri string
-```
-
-```dart
-final uri = Sep7Pay.forDestination('G...');
-uri.setCallback('https://example.com/callback');
-uri.setMsg('here goes a message');
-uri.setAssetCode('USDC');
-uri.setAssetIssuer('G...');
-uri.setAmount('10');
-uri.toString(); // encodes everything and converts to a uri string
-```
-
-```swift
-let uri = Sep7Pay(destination: "G...")
-uri.setCallback(callback: "https://example.com/callback")
-try uri.setMsg(msg: "here goes a message")
-uri.setAssetCode(assetCode: "USDC")
-uri.setAssetIssuer(assetIssuer: "G...")
-uri.setAmount(amount: "10")
-uri.toString() // encodes everything and converts to a uri string
-```
-
-</WalletCodeExample>
-
-El último paso después de construir un `Sep7Tx` o `Sep7Pay` es agregar una firma a tu uri. Esto creará una carga útil de la transacción y la firmará con el keypair proporcionado.
-
-<WalletCodeExample>
-
-```typescript
-const uri = wallet.Sep7Pay.forDestination("G...");
-uri.originDomain = "example.com";
-const keypair = wallet.stellar().account().createKeypair();
-uri.addSignature(Keypair.fromSecret(keypair.secretKey));
-console.log(uri.signature); // signed uri payload
-```
-
-```dart
-final uri = Sep7Pay.forDestination('G...');
-uri.setOriginDomain('example.com');
-final keypair = wallet.stellar().account().createKeyPair();
-uri.addSignature(keypair);
-print(uri.getSignature()); // signed uri payload
-```
-
-```swift
-uri = Sep7Pay(destination: "G..")
-uri.setOriginDomain(originDomain: "example.com")
-let keyPair = wallet.stellar.account.createKeyPair()
-try uri.addSignature(keyPair: keyPair)
-print(uri.getSignature()) // signed uri payload
-```
-
-</WalletCodeExample>
-
-La firma puede ser verificada al obtener el [archivo toml de Stellar] del dominio de origen en la uri, y utilizando la clave de firma incluida para verificar la firma de la uri. Todo esto se realiza como parte del método `verifySignature`.
-
-<WalletCodeExample>
-
-```typescript
-const passesVerification = await uri.verifySignature(); // true or false
-```
-
-```dart
-final passesVerification = await uri.verifySignature(); // true or false
-```
-
-```swift
-let passesVerification = await uri.verifySignature() // true or false
-```
-
-</WalletCodeExample>
-
-[Sep-7]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md
-[formato de representación de transacciones Sep-11]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md
-[algunos parámetros configurables]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md#operation-tx
-[configurar parámetros]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md#operation-pay
-[archivo toml de Stellar]: ../../apps/example-application-tutorial/anchor-integration/sep1.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/stellar.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/stellar.mdx
deleted file mode 100644
index 3e7b0ad460..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/wallet/stellar.mdx
+++ /dev/null
@@ -1,1408 +0,0 @@
----
-title: Red de Stellar
-sidebar_position: 30
----
-
-import { LanguageSpecific } from "@site/src/components/LanguageSpecific";
-import { WalletCodeExample } from "@site/src/components/WalletCodeExample";
-import Header from "./component/header.mdx";
-import CreateKeyPairInfo from "./component/ts/createKeypairInfo.mdx";
-
-<Header />
-
-En la sección anterior aprendimos cómo crear una billetera y un objeto `Stellar` que proporciona una conexión a Horizon. En esta sección, examinaremos los usos de esta clase.
-
-## Cuentas
-
-La entidad más básica en la red Stellar es una cuenta. Miremos el AccountService que proporciona la capacidad de trabajar con cuentas:
-
-<WalletCodeExample>
-
-```kt
-val account = wallet.stellar().account()
-```
-
-```typescript
-let account = wal.stellar().account();
-```
-
-```dart
-var account = wallet.stellar().account();
-```
-
-```swift
-let account = wallet.stellar.account
-```
-
-</WalletCodeExample>
-
-Ahora podemos crear un par de claves:
-
-<WalletCodeExample>
-
-```kt
-val accountKeyPair = account.createKeyPair()
-```
-
-```typescript
-let accountKeyPair = account.createKeypair();
-```
-
-```dart
-var accountKeyPair = account.createKeyPair();
-```
-
-```swift
-let accountKeyPair = account.createKeyPair()
-```
-
-</WalletCodeExample>
-
-<LanguageSpecific ts={<CreateKeyPairInfo />} />
-
-## Construir Transacción
-
-El constructor de transacciones te permite crear varias transacciones que pueden ser firmadas y enviadas a la red Stellar. Algunas transacciones pueden ser patrocinadas.
-
-### Construyendo Transacciones Básicas
-
-Primero, veamos cómo construir transacciones básicas.
-
-#### Crear Cuenta
-
-La transacción de crear cuenta activa/crea una cuenta con un saldo inicial de XLM (1 XLM por defecto).
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun createAccount(): Transaction {
-  return stellar.transaction(sourceAccountKeyPair).createAccount(destinationAccountKeyPair).build()
-}
-```
-
-```typescript
-const txBuilder = await stellar.transaction({
-  sourceAddress: sourceAccountKeyPair,
-});
-const tx = txBuilder.createAccount(destinationAccountKeyPair).build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-var tx = txBuilder.createAccount(destinationAccountKeyPair).build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.createAccount(newAccount: destinationAccountKeyPair).build()
-```
-
-</WalletCodeExample>
-
-#### Modificar Cuenta
-
-Puedes bloquear la clave maestra de la cuenta estableciendo su peso en 0. Ten cuidado al bloquear la clave maestra de la cuenta. Asegúrate de haber establecido los firmantes y pesos correctos. De lo contrario, bloquearás la cuenta de forma irreversible.
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun lockMasterKey(): Transaction {
-  return stellar.transaction(sourceAccountKeyPair).lockAccountMasterKey().build()
-}
-```
-
-```typescript
-const txBuilder = await stellar.transaction({
-  sourceAddress: sourceAccountKeyPair,
-});
-
-const tx = txBuilder.lockAccountMasterKey().build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-var tx = txBuilder.lockAccountMasterKey().build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.lockAccountMasterKey().build()
-```
-
-</WalletCodeExample>
-
-Añadir un nuevo firmante a la cuenta. Ten cuidado al añadir nuevos firmantes y asegúrate de establecer el peso del firmante correcto. De lo contrario, bloquearás la cuenta de forma irreversible.
-
-<WalletCodeExample>
-
-```kotlin
-val newSignerKeyPair = account.createKeyPair()
-
-suspend fun addSigner(): Transaction {
-  return stellar.transaction(sourceAccountKeyPair).addAccountSigner(newSignerKeyPair, 10).build()
-}
-```
-
-```typescript
-const newSignerKeyPair = account.createKeypair();
-
-const tx = txBuilder.addAccountSigner(newSignerKeyPair, 10).build();
-```
-
-```dart
-var newSignerKeyPair = account.createKeyPair();
-
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-var tx = txBuilder.addAccountSigner(newSignerKeyPair, 10).build();
-```
-
-```swift
-let newSignerKeyPair = account.createKeyPair()
-
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.addAccountSigner(signerAddress: newSignerKeyPair, signerWeight: 10).build()
-```
-
-</WalletCodeExample>
-
-Eliminar un firmante de la cuenta.
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun removeSigner(): Transaction {
-  return stellar.transaction(sourceAccountKeyPair).removeAccountSigner(newSignerKeyPair).build()
-}
-```
-
-```typescript
-const tx = txBuilder.removeAccountSigner(newSignerKeyPair).build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-var tx = txBuilder.removeAccountSigner(newSignerKeyPair).build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.removeAccountSigner(signerAddress: newSignerKeyPair).build()
-```
-
-</WalletCodeExample>
-
-Modificar los umbrales de la cuenta (útil cuando se asignan varios firmantes a la cuenta). Esto te permite restringir el acceso a ciertas operaciones cuando no se alcanza el límite.
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun setThreshold(): Transaction {
-  return stellar.transaction(sourceAccountKeyPair).setThreshold(low = 1, medium = 10, high = 30).build()
-}
-```
-
-```typescript
-const tx = txBuilder.setThreshold({ low: 1, medium: 10, high: 30 }).build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-var tx = txBuilder.setThreshold(low: 1, medium: 10, high: 20).build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.setThreshold(low: 1, medium: 10, high: 20).build()
-```
-
-</WalletCodeExample>
-
-#### Modificar Activos (Trustlines)
-
-Añadir un activo (trustline) a la cuenta. Esto permite a la cuenta recibir transferencias del activo.
-
-<WalletCodeExample>
-
-```kotlin
-val asset = IssuedAssetId("USDC", "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5")
-
-suspend fun addAsset(): Transaction {
-  return stellar.transaction(sourceAccountKeyPair).addAssetSupport(asset).build()
-}
-```
-
-```typescript
-const asset = new IssuedAssetId(
-  "USDC",
-  "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
-);
-
-const tx = txBuilder.addAssetSupport(asset).build();
-```
-
-```dart
-var asset = IssuedAssetId(
-        code: "USDC",
-        issuer: "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5");
-
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-var tx = txBuilder.addAssetSupport(asset).build();
-```
-
-```swift
-let asset = try IssuedAssetId(
-    code: "USDC",
-    issuer: "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5")
-
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.addAssetSupport(asset: asset).build()
-```
-
-</WalletCodeExample>
-
-Eliminar un activo de la cuenta (el saldo del activo debe ser 0).
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun removeAsset(): Transaction {
-  return stellar.transaction(sourceAccountKeyPair).removeAssetSupport(asset).build()
-}
-```
-
-```typescript
-const tx = txBuilder.removeAssetSupport(asset).build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-var tx = txBuilder.removeAssetSupport(asset).build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let tx = try txBuilder.removeAssetSupport(asset: asset).build()
-```
-
-</WalletCodeExample>
-
-#### Intercambiar
-
-Intercambiar un activo de la cuenta por otro activo diferente. La cuenta debe tener una trustline para el activo de destino.
-
-<WalletCodeExample>
-
-```typescript
-const txBuilder = await stellar.transaction({
-  sourceAddress: sourceKp,
-});
-const usdcAsset = new IssuedAssetId(
-  "USDC",
-  "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
-);
-const txn = txBuilder.swap(new NativeAssetId(), usdcAsset, ".1").build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(sourceKp);
-
-final usdcAsset = IssuedAssetId(
-    code: 'USDC',
-    issuer: 'GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5',
-);
-
-var txn = txBuilder.swap(
-    fromAsset: NativeAssetId(),
-    toAsset: usdcAsset,
-    amount: "0.1",
-  ).build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: sourceKp)
-
-let usdcAsset = try IssuedAssetId(
-    code: "USDC",
-    issuer: "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5")
-
-let txn = try txBuilder.swap(fromAsset: NativeAssetId(),
-                             toAsset: usdcAsset,
-                             amount: 0.1).build()
-```
-
-</WalletCodeExample>
-
-#### Path Pay
-
-Enviar un activo de la cuenta de origen y recibir un activo diferente en la cuenta de destino.
-
-<WalletCodeExample>
-
-```typescript
-const txBuilder = await stellar.transaction({
-  sourceAddress: sourceKp,
-});
-const usdcAsset = new IssuedAssetId(
-  "USDC",
-  "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
-);
-const txn = txBuilder
-  .pathPay({
-    destinationAddress: receivingKp.publicKey,
-    sendAsset: new NativeAssetId(),
-    destAsset: usdcAsset,
-    sendAmount: "5",
-  })
-  .build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(sourceKp);
-
-final usdcAsset = IssuedAssetId(
-    code: 'USDC',
-    issuer: 'GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5',
-);
-
-var txn = txBuilder.pathPay(
-    destinationAddress: receivingKp.address,
-    sendAsset: NativeAssetId(),
-    destinationAsset: usdcAsset,
-    sendAmount: "5",
-  ).build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: sourceKp)
-
-let usdcAsset = try IssuedAssetId(
-    code: "USDC",
-    issuer: "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5")
-
-let txn = try txBuilder.pathPay(destinationAddress: receivingKp.address,
-                                sendAsset: NativeAssetId(),
-                                destinationAsset: usdcAsset,
-                                sendAmount: 5).build()
-```
-
-</WalletCodeExample>
-
-#### Establecer Memo
-
-Establece un memo en la transacción. El objeto memo se puede importar de ["@stellar/stellar-sdk"](https://www.npmjs.com/package/@stellar/stellar-sdk).
-
-<WalletCodeExample>
-
-```typescript
-import { Memo } from "@stellar/stellar-sdk";
-
-const tx = txBuilder.setMemo(new Memo("text", "Memo string")).build();
-```
-
-```dart
-import 'package:stellar_flutter_sdk/stellar_flutter_sdk.dart' as flutter_sdk;
-
-var memo = flutter_sdk.MemoText("Memo string");
-var tx = txBuilder.setMemo(memo).build();
-```
-
-```swift
-import stellarsdk
-
-let memo = Memo.text("Memo string")
-let tx = try txBuilder.setMemo(memo: memo).build()
-```
-
-</WalletCodeExample>
-
-#### Fusión de Cuentas
-
-Fusiona la cuenta en una cuenta de destino.
-
-<WalletCodeExample>
-
-```typescript
-const txBuilder = await stellar.transaction({
-  sourceAddress: accountKp,
-  baseFee: 1000,
-});
-const mergeTxn = txBuilder
-  .accountMerge(accountKp.publicKey, sourceKp.publicKey)
-  .build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(accountKp, baseFee: 1000);
-
-var mergeTxn = txBuilder.accountMerge(
-    destinationAddress: accountKp.address,
-    sourceAddress: sourceKp.address,
-  ).build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: accountKp,
-                                              baseFee: 1000)
-
-let mergeTxn = try txBuilder.accountMerge(destinationAddress: accountKp.address,
-                                          sourceAddress: sourceKp.address).build()
-```
-
-</WalletCodeExample>
-
-#### Fondos de Cuenta de Test Net
-
-Financia una cuenta en la red de pruebas Stellar
-
-<WalletCodeExample>
-
-```typescript
-wallet.stellar().fundTestnetAccount(accountKp.publicKey);
-```
-
-```dart
-await wallet.stellar().fundTestNetAccount(accountKp.address);
-```
-
-```swift
-try await wallet.stellar.fundTestNetAccount(address: accountKp.address)
-```
-
-</WalletCodeExample>
-
-### Construyendo Transacciones Avanzadas
-
-En algunos casos, es posible que no se conozca una clave privada antes de formar una transacción. Por ejemplo, se debe financiar una nueva cuenta para que exista y la billetera puede no tener la clave de la cuenta, por lo que puede solicitar que la transacción de creación de la cuenta sea patrocinada por un tercero.
-
-<WalletCodeExample>
-
-```kt
-// Third-party key that will sponsor creating new account
-val externalKeyPair = "MySponsorAddress".toPublicKeyPair()
-val newKeyPair = account.createKeyPair()
-```
-
-```typescript
-// Third-party key that will sponsor creating new account
-const externalKeyPair = new PublicKeypair.fromPublicKey("GC5GD...");
-const newKeyPair = account.createKeypair();
-```
-
-```dart
-// Third-party key that will sponsor creating new account
-var externalKeyPair = PublicKeyPair.fromAccountId("GC5GD...");
-var newKeyPair = account.createKeyPair();
-```
-
-```swift
-// Third-party key that will sponsor creating new account
-let externalKeyPair = try PublicKeyPair(accountId: "GC5GD...")
-let newKeyPair = account.createKeyPair()
-```
-
-</WalletCodeExample>
-
-Primero, se debe crear la cuenta.
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun makeCreateTx(): Transaction {
-  return stellar.transaction(externalKeyPair).createAccount(newKeyPair).build()
-}
-```
-
-```typescript
-const createTxn = txBuilder.createAccount(newKeyPair).build();
-```
-
-```dart
-var txBuilder = await stellar.transaction(externalKeyPair);
-var createTxn = txBuilder.createAccount(newKeyPair).build();
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: externalKeyPair)
-let createTxn = try txBuilder.createAccount(newAccount: newKeyPair).build()
-```
-
-</WalletCodeExample>
-
-Esta transacción debe enviarse al firmante externo (titular de `externalKeyPair`) para ser firmada.
-
-<WalletCodeExample>
-
-```kt
-suspend fun remoteSignTransaction(transaction: Transaction) {
-  val xdrString = transaction.toEnvelopeXdrBase64()
-  // Send xdr encoded transaction to your backend server to sign
-  val xdrStringFromBackend = sendTransactionToBackend(xdrString)
-
-  // Decode xdr to get the signed transaction
-  val signedTransaction = stellar.decodeTransaction(xdrStringFromBackend)
-}
-```
-
-```typescript
-const xdrString = createTxn.toXDR();
-// Send xdr encoded transaction to your backend server to sign
-const xdrStringFromBackend = await sendTransactionToBackend(xdrString);
-
-// Decode xdr to get the signed transaction
-const signedTransaction = stellar.decodeTransaction(xdrStringFromBackend);
-```
-
-```dart
-var xdrString = createTxn.toEnvelopeXdrBase64();
-
-// Send xdr encoded transaction to your backend server to sign
-var xdrStringFromBackend = await sendTransactionToBackend(xdrString);
-
-// Decode xdr to get the signed transaction
-var signedTransaction = stellar.decodeTransaction(xdrStringFromBackend);
-```
-
-```swift
-let xdrString = createTxn.toEnvelopeXdrBase64()
-
-// Send xdr encoded transaction to your backend server to sign
-let xdrStringFromBackend = await sendTransactionToBackend(xdrString)
-
-// Decode xdr to get the signed transaction
-let signedTransaction = stellar.decodeTransaction(xdr: xdrStringFromBackend)
-```
-
-</WalletCodeExample>
-
-:::note
-
-Puedes leer más sobre cómo enviar transacciones XDR al servidor en el [capítulo siguiente](#using-xdr-to-send-transaction-data).
-
-:::
-
-La transacción firmada puede ser presentada por la billetera.
-
-<WalletCodeExample>
-
-```kt
-suspend fun submitCreateTx(signedCreateTx: Transaction) {
-  wallet.stellar().submitTransaction(signedCreateTx)
-}
-
-```
-
-```typescript
-await wallet.stellar().submitTransaction(signedTransaction);
-```
-
-```dart
-bool success = await stellar.submitTransaction(signedTransaction);
-```
-
-```swift
-try await stellar.submitTransaction(signedTransaction: signedTransaction)
-```
-
-</WalletCodeExample>
-
-Ahora, después de crear la cuenta, puede realizar operaciones. Por ejemplo, podemos desactivar el keypair maestro y reemplazarlo con uno nuevo (llamémoslo keypair del dispositivo) atómicamente en una sola transacción:
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun addDeviceKeyPair() {
-  val deviceKeyPair = account.createKeyPair()
-
-  val modifyAccountTransaction =
-    stellar
-      .transaction(newKeyPair)
-      .addAccountSigner(
-        deviceKeyPair,
-        signerWeight = 1,
-      )
-      .lockAccountMasterKey()
-      .build()
-      .sign(newKeyPair)
-
-  wallet.stellar().submitTransaction(modifyAccountTransaction)
-}
-```
-
-```typescript
-const deviceKeyPair = account.createKeypair();
-
-const txBuilder = await stellar.transaction({ sourceAddress: newKeyPair });
-const modifyAccountTransaction = txBuilder
-  .addAccountSigner(deviceKeyPair, 1)
-  .lockAccountMasterKey()
-  .build();
-newKeyPair.sign(modifyAccountTransaction);
-
-await wallet.stellar().submitTransaction(modifyAccountTransaction);
-```
-
-```dart
-var deviceKeyPair = account.createKeyPair();
-
-var txBuilder = await stellar.transaction(newKeyPair);
-var modifyAccountTransaction = txBuilder
-    .addAccountSigner(deviceKeyPair, 1)
-    .lockAccountMasterKey()
-    .build();
-
-stellar.sign(modifyAccountTransaction, newKeyPair);
-
-bool success = await stellar.submitTransaction(modifyAccountTransaction);
-```
-
-```swift
-let deviceKeyPair = account.createKeyPair()
-
-let txBuilder = try await stellar.transaction(sourceAddress: newKeyPair)
-
-let modifyAccountTransaction = try txBuilder
-    .addAccountSigner(signerAddress: deviceKeyPair, signerWeight: 1)
-    .lockAccountMasterKey()
-    .build()
-
-stellar.sign(tx: modifyAccountTransaction,
-             keyPair: newKeyPair)
-
-try await stellar.submitTransaction(signedTransaction: modifyAccountTransaction)
-```
-
-</WalletCodeExample>
-
-#### Añadiendo una Operación
-
-Agrega una Operación personalizada a una transacción. Esto puede ser cualquier [Operación](../../../learn/fundamentals/transactions/list-of-operations) admitida por la red Stellar. El objeto Operación se puede importar de ["@stellar/stellar-sdk"](https://www.npmjs.com/package/@stellar/stellar-sdk).
-
-<WalletCodeExample>
-
-```typescript
-import { Operation } from "@stellar/stellar-sdk";
-
-const txBuilder = await stellar.transaction({
-  sourceAddress: sourceAccountKeyPair,
-});
-const tx = txBuilder.addOperation(
-  Operation.manageData({
-    name: "web_auth_domain",
-    value: new URL(authServer).hostname,
-    source: sourceAccountKeyPair,
-  }),
-);
-```
-
-```dart
-import 'package:stellar_flutter_sdk/stellar_flutter_sdk.dart' as flutter_sdk;
-
-var txBuilder = await stellar.transaction(sourceAccountKeyPair);
-
-var key = "web_auth_domain";
-var value = "https://testanchor.stellar.org";
-var valueBytes = Uint8List.fromList(value.codeUnits);
-
-var manageDataOperation = flutter_sdk.ManageDataOperationBuilder(
-    key,
-    valueBytes,
-  ).build();
-
-var tx = txBuilder.addOperation(
-    manageDataOperation,
-  ).build();
-```
-
-```swift
-import stellarsdk
-
-let txBuilder = try await stellar.transaction(sourceAddress: sourceAccountKeyPair)
-let key = "web_auth_domain"
-let value = "testanchor.stellar.org"
-let manageDataOperation = ManageDataOperation(sourceAccountId: sourceAccountKeyPair.address,
-                                              name: key,
-                                              data: value.data(using: .utf8))
-
-let tx = try txBuilder.addOperation(operation: manageDataOperation).build()
-```
-
-</WalletCodeExample>
-
-### Patrocinando Transacciones
-
-#### Operaciones de Patrocinio
-
-Algunas operaciones, que modifican las reservas de la cuenta pueden ser [patrocinadas](../../guides/transactions/sponsored-reserves.mdx). Para las operaciones patrocinadas, la cuenta patrocinadora pagará las reservas en lugar de la cuenta que está siendo patrocinada. Esto te permite realizar algunas operaciones, incluso si la cuenta no tiene suficientes fondos para realizar tales operaciones. Para patrocinar una transacción, <LanguageSpecific kt={<span>simplemente inicia un bloque <code>sponsoring</code>:</span>} ts={<span>simplemente crea una función de construcción (describiendo qué operaciones van a ser patrocinadas) y pásala al método <code>sponsoring</code>:</span>}/>
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun sponsorOperation() {
-  val transaction =
-    stellar
-      .transaction(sponsoredKeyPair)
-      .sponsoring(sponsorKeyPair) { addAssetSupport(asset) }
-      .build()
-
-  transaction.sign(sponsorKeyPair).sign(sponsoredKeyPair)
-}
-```
-
-```typescript
-const txBuilder = await stellar.transaction({
-  sourceAddress: sponsoredKeyPair,
-});
-
-const buildingFunction = (bldr) => bldr.addAssetSupport(asset);
-const transaction = txBuilder
-  .sponsoring(sponsorKeyPair, buildingFunction)
-  .build();
-
-sponsoredKeyPair.sign(transaction);
-sponsorKeyPair.sign(transaction);
-```
-
-```dart
-var txBuilder = await stellar.transaction(sponsoredKeyPair);
-var transaction = txBuilder
-    .sponsoring(sponsorKeyPair, (builder) => builder.addAssetSupport(asset))
-    .build();
-
-stellar.sign(transaction, sponsorKeyPair);
-stellar.sign(transaction, sponsoredKeyPair);
-```
-
-```swift
-let txBuilder = try await stellar.transaction(sourceAddress: sponsoredKeyPair)
-let transaction = try txBuilder.sponsoring(
-    sponsorAccount: sponsorKeyPair,
-    buildingFunction:{ (builder) in builder.addAssetSupport(asset: asset)}).build()
-
-stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
-stellar.sign(tx: transaction, keyPair: sponsoredKeyPair)
-```
-
-</WalletCodeExample>
-
-:::info
-
-Solo algunas operaciones pueden ser patrocinadas, y un <LanguageSpecific kt={<span>bloque</span>} ts={<span>constructor</span>} /> de patrocinio tiene un conjunto ligeramente diferente de funciones disponibles en comparación con el `TransactionBuilder` regular. Nota que una transacción debe ser firmada por ambas cuentas: la cuenta patrocinadora (`sponsoringKeyPair`) y la cuenta que está siendo patrocinada (`sponsoredKeyPair`).
-
-:::
-
-#### Creación de Cuenta Patrocinadora
-
-Una de las cosas que se pueden hacer a través de patrocinio es crear una cuenta con un saldo inicial de 0. Esta creación de cuenta puede hacerse simplemente escribiendo:
-
-<WalletCodeExample>
-
-```kt
-suspend fun sponsorAccountCreation() {
-  val newKeyPair = account.createKeyPair()
-
-  val transaction =
-    stellar
-      .transaction(sponsorKeyPair)
-      .sponsoring(sponsorKeyPair, sponsoredAccount = newKeyPair) { createAccount(newKeyPair) }
-      .build()
-
-  transaction.sign(sponsorKeyPair).sign(newKeyPair)
-}
-```
-
-```typescript
-const txBuilder = await stellar.transaction({ sourceAddress: sponsorKeyPair });
-
-const newKeyPair = account.createKeypair();
-
-const buildingFunction = (bldr) => bldr.createAccount(newKeyPair);
-const transaction = txBuilder
-  .sponsoring(sponsorKeyPair, buildingFunction, newKeyPair)
-  .build();
-
-newKeyPair.sign(transaction);
-sponsorKeyPair.sign(transaction);
-```
-
-```dart
-var newKeyPair = account.createKeyPair();
-
-var txBuilder = await stellar.transaction(sponsorKeyPair);
-var transaction = txBuilder
-    .sponsoring(sponsorKeyPair, sponsoredAccount: newKeyPair,
-        (builder) => builder.createAccount(newKeyPair))
-    .build();
-
-stellar.sign(transaction, sponsorKeyPair);
-stellar.sign(transaction, newKeyPair);
-```
-
-```swift
-let newKeyPair = account.createKeyPair()
-
-let txBuilder = try await stellar.transaction(sourceAddress: sponsorKeyPair)
-let transaction = try txBuilder.sponsoring(
-    sponsorAccount: sponsorKeyPair,
-    buildingFunction:{ (builder) in builder.createAccount(newAccount: newKeyPair)},
-    sponsoredAccount: newKeyPair).build()
-
-stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
-stellar.sign(tx: transaction, keyPair: newKeyPair)
-```
-
-</WalletCodeExample>
-
-Nota cómo en el primer ejemplo la cuenta fuente de la transacción se establece en `sponsoredKeyPair`. Debido a esto, no necesitábamos pasar un valor de cuenta patrocinada al bloque <LanguageSpecific kt={<span>sponsoring</span>} ts={<span>método</span>} />. Ya que cuando se omite, la cuenta patrocinada predetermina a la cuenta fuente de la transacción (`sponsoredKeyPair`).
-
-Sin embargo, esta vez, la cuenta patrocinada (recientemente creada `newKeyPair`) es diferente de la cuenta fuente de la transacción. Por lo tanto, es necesario especificarla. De lo contrario, la transacción contendrá una operación mal formada. Como antes, la transacción debe ser firmada por ambas claves.
-
-#### Creación y Modificación de Cuenta Patrocinadora
-
-Si deseas crear una cuenta y modificarla en una sola transacción, es posible hacerlo pasando un argumento opcional `sponsoredAccount` al <LanguageSpecific kt={<span>bloque</span>} ts={<span>método patrocinador</span>} /> (`newKeyPair` abajo). Si este argumento está presente, todas las operaciones dentro del bloque patrocinado serán sourcing por esta `sponsoredAccount`. (Excepto la creación de cuenta, que siempre es sourcing por el patrocinador).
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun sponsorAccountCreationAndModification() {
-  val newKeyPair = account.createKeyPair()
-  val replaceWith = account.createKeyPair()
-
-  val transaction =
-    stellar
-        .transaction(sponsorKeyPair)
-        .sponsoring(sponsorKeyPair, newKeyPair) {
-          createAccount(newKeyPair)
-          // source account for below operations will be newKeyPair
-          addAccountSigner(replaceWith, 1)
-          lockAccountMasterKey()
-        }
-        .build()
-
-  transaction.sign(sponsorKeyPair).sign(newKeyPair)
-}
-```
-
-```typescript
-const txBuilder = await stellar.transaction({ sourceAddress: sponsorKeyPair });
-
-const newKeyPair = account.createKeypair();
-const replaceWith = account.createKeypair();
-
-const buildingFunction = (bldr) =>
-  bldr
-    .createAccount(newKeyPair)
-    // source account for below operations will be newKeyPair
-    .addAccountSigner(replaceWith, 1)
-    .lockAccountMasterKey();
-
-const transaction = txBuilder
-  .sponsoring(sponsorKeyPair, buildingFunction, newKeyPair)
-  .build();
-
-newKeyPair.sign(transaction);
-sponsorKeyPair.sign(transaction);
-```
-
-```dart
-var newKeyPair = account.createKeyPair();
-var replaceWith = account.createKeyPair();
-
-var txBuilder = await stellar.transaction(sponsorKeyPair);
-var transaction = txBuilder
-    .sponsoring(
-    sponsorKeyPair,
-    sponsoredAccount: newKeyPair,
-        (builder) => builder
-        .createAccount(newKeyPair)
-        .addAccountSigner(replaceWith, 1)
-        .lockAccountMasterKey())
-    .build();
-
-stellar.sign(transaction, sponsorKeyPair);
-stellar.sign(transaction, newKeyPair);
-```
-
-```swift
-let newKeyPair = account.createKeyPair()
-let replaceWith = account.createKeyPair()
-
-let txBuilder = try await stellar.transaction(sourceAddress: sponsorKeyPair)
-let transaction = try txBuilder.sponsoring(
-    sponsorAccount: sponsorKeyPair,
-    buildingFunction:{ (builder) in builder
-            .createAccount(newAccount: newKeyPair)
-            .addAccountSigner(signerAddress: replaceWith, signerWeight: 1)
-            .lockAccountMasterKey()
-    },
-    sponsoredAccount: newKeyPair).build()
-
-stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
-stellar.sign(tx: transaction, keyPair: newKeyPair)
-```
-
-</WalletCodeExample>
-
-### Transacción Fee-Bump
-
-Si deseas modificar una cuenta recién creada con un saldo de 0, también es posible hacerlo a través de `FeeBump`. Se puede combinar con un bloque de patrocinio <LanguageSpecific kt={<span>bloque</span>} ts={<span>método</span>} /> para lograr el mismo resultado que en el ejemplo anterior. Sin embargo, con `FeeBump`, también es posible agregar más operaciones (que no requieren patrocinio), como una transferencia.
-
-Primero, vamos a crear una transacción que reemplazará la clave maestra de una cuenta con un nuevo keypair.
-
-<WalletCodeExample>
-
-```kt
-val replaceWith = account.createKeyPair()
-
-val transaction =
-  stellar
-    .transaction(sponsoredKeyPair)
-    .sponsoring(sponsorKeyPair) {
-      lockAccountMasterKey()
-      addAccountSigner(replaceWith, signerWeight = 1)
-    }
-    .build()
-
-```
-
-```typescript
-const txBuilder = await stellar.transaction({
-  sourceAddress: sponsoredKeyPair,
-});
-
-const replaceWith = account.createKeypair();
-
-const buildingFunction = (bldr) =>
-  bldr.lockAccountMasterKey().addAccountSigner(replaceWith, 1);
-const transaction = txBuilder
-  .sponsoring(sponsorKeyPair, buildingFunction)
-  .build();
-```
-
-```dart
-var replaceWith = account.createKeyPair();
-
-var txBuilder = await stellar.transaction(sponsoredKeyPair);
-var transaction = txBuilder
-    .sponsoring(sponsorKeyPair,
-        (builder) => builder.lockAccountMasterKey().addAccountSigner(replaceWith, 1))
-    .build();
-```
-
-```swift
-let replaceWith = account.createKeyPair()
-
-let txBuilder = try await stellar.transaction(sourceAddress: sponsoredKeyPair)
-let transaction = try txBuilder.sponsoring(
-    sponsorAccount: sponsorKeyPair,
-    buildingFunction:{ (builder) in builder
-            .lockAccountMasterKey()
-            .addAccountSigner(signerAddress: replaceWith, signerWeight: 1)
-    }).build()
-```
-
-</WalletCodeExample>
-
-Luego, firma la transacción con ambas claves.
-
-<WalletCodeExample>
-
-```kt
-transaction.sign(sponsoredKeyPair).sign(sponsorKeyPair)
-```
-
-```typescript
-sponsorKeyPair.sign(transaction);
-sponsoredKeyPair.sign(transaction);
-```
-
-```dart
-stellar.sign(transaction, sponsorKeyPair);
-stellar.sign(transaction, sponsoredKeyPair);
-```
-
-```swift
-stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
-stellar.sign(tx: transaction, keyPair: sponsoredKeyPair)
-```
-
-</WalletCodeExample>
-
-A continuación, crea un fee bump, apuntando a la transacción.
-
-<WalletCodeExample>
-
-```kt
-val feeBump = stellar.makeFeeBump(sponsorKeyPair, transaction)
-feeBump.sign(sponsorKeyPair)
-```
-
-```typescript
-const feeBump = stellar.makeFeeBump({
-  feeAddress: sponsorKeyPair,
-  transaction,
-});
-sponsorKeyPair.sign(feeBump);
-```
-
-```dart
-var feeBump = stellar.makeFeeBump(sponsorKeyPair, transaction);
-stellar.sign(feeBump, sponsorKeyPair);
-```
-
-```swift
-let feeBump = try stellar.makeFeeBump(feeAddress: sponsorKeyPair,
-                                      transaction: transaction)
-stellar.sign(tx: transaction, keyPair: sponsorKeyPair)
-```
-
-</WalletCodeExample>
-
-Finalmente, presenta una transacción de fee-bump. Ejecutar esta transacción será completamente cubierto por el `sponsorKeyPair` y `sponsoredKeyPair` y puede que ni siquiera tenga fondos en XLM en su cuenta.
-
-<WalletCodeExample>
-
-```kt
-wallet.stellar().submitTransaction(feeBump)
-```
-
-```typescript
-await wallet.stellar().submitTransaction(feeBump);
-```
-
-```dart
-bool success = await stellar.submitTransaction(feeBump);
-```
-
-```swift
-try await stellar.submitTransaction(signedFeeBumpTransaction: feeBump)
-```
-
-</WalletCodeExample>
-
-### Usando XDR para Enviar Datos de Transacción
-
-Nota que una billetera puede no tener una clave de firma para `sponsorKeyPair`. En ese caso, es necesario convertir la transacción a XDR, enviarla al servidor, conteniendo `sponsorKey` y devolver la transacción firmada de nuevo a la billetera. Usamos el ejemplo anterior de la creación de cuenta patrocinada, pero esta vez con la clave patrocinadora desconocida para la billetera. El primer paso es definir la clave pública del keypair patrocinador:
-
-<WalletCodeExample>
-
-```kt
-val sponsorKeyPair = "SponsorAddress".toPublicKeyPair()
-```
-
-```typescript
-const sponsorKeyPair = new PublicKeypair.fromPublicKey("GC5GD...");
-```
-
-```dart
-var sponsorKeyPair = PublicKeyPair.fromAccountId("GC5GD...");
-```
-
-```swift
-let sponsorKeyPair = try PublicKeyPair(accountId: "GC5GD...")
-```
-
-</WalletCodeExample>
-
-A continuación, crea una cuenta de la misma manera que antes y fír mala con `newKeyPair`. Esta vez, convierte la transacción a XDR:
-
-<WalletCodeExample>
-
-```kt
-suspend fun sponsorAccountCreation(): String {
-  val newKeyPair = account.createKeyPair()
-
-  return stellar
-    .transaction(sponsorKeyPair)
-    .sponsoring(sponsorKeyPair) { createAccount(newKeyPair) }
-    .build()
-    .sign(newKeyPair)
-    .toEnvelopeXdrBase64()
-}
-
-```
-
-```typescript
-const txBuilder = await stellar.transaction({ sourceAddress: sponsorKeyPair });
-
-const newKeyPair = account.createKeypair();
-
-const transaction = txBuilder
-  .sponsoring(sponsorKeyPair, (bldr) => bldr.createAccount(newKeyPair))
-  .build();
-const xdrString = newKeyPair.sign(transaction).toXDR();
-```
-
-```dart
-var newKeyPair = account.createKeyPair();
-
-var txBuilder = await stellar.transaction(sponsorKeyPair);
-var transaction = txBuilder
-    .sponsoring(
-        sponsorKeyPair, (builder) => builder.createAccount(newKeyPair),
-        sponsoredAccount: newKeyPair)
-    .build();
-
-stellar.sign(transaction, newKeyPair);
-
-var xdrString = transaction.toEnvelopeXdrBase64();
-```
-
-```swift
-let newKeyPair = account.createKeyPair()
-
-let txBuilder = try await stellar.transaction(sourceAddress: sponsorKeyPair)
-let transaction = try txBuilder.sponsoring(
-            sponsorAccount: sponsorKeyPair,
-            buildingFunction:{ (builder) in builder.createAccount(newAccount: newKeyPair)},
-            sponsoredAccount: newKeyPair).build()
-
-stellar.sign(tx: transaction, keyPair: newKeyPair)
-
-let xdrString = transaction.toEnvelopeXdrBase64()
-```
-
-</WalletCodeExample>
-
-Ahora puede ser enviado al servidor. En el servidor, fír mala con una clave privada para la dirección del patrocinador:
-
-<WalletCodeExample>
-
-```kt
-// On the server
-fun signTransaction(xdrString: String): String {
-  val sponsorPrivateKey = SigningKeyPair.fromSecret("MySecret")
-
-  val signedTransaction = stellar.decodeTransaction(xdrString).sign(sponsorPrivateKey)
-
-  return signedTransaction.toEnvelopeXdrBase64()
-}
-```
-
-```typescript
-// On the server
-const sponsorPrivateKey = SigningKeyPair.fromSecret("SD3LH4...");
-
-const signedTransaction = sponsorPrivateKey.sign(
-  stellar.decodeTransaction(xdrString),
-);
-
-return signedTransaction.toXDR();
-```
-
-```dart
-String signTransaction(String xdrString) {
-  var sponsorPrivateKey = SigningKeyPair.fromSecret("SD3LH4...");
-
-  var transaction = stellar.decodeTransaction(xdrString);
-  stellar.sign(transaction, sponsorPrivateKey);
-
-  return transaction.toEnvelopeXdrBase64();
-}
-```
-
-```swift
-internal func signTransaction(xdr:String) throws -> String {
-    let sponsorPrivateKey = try SigningKeyPair(secretKey: "SD3LH4...")
-
-    let transactionEnum = stellar.decodeTransaction(xdr: xdr)
-    switch transactionEnum {
-    case .transaction(let tx):
-        stellar.sign(tx: tx, keyPair: sponsorPrivateKey)
-        return tx.toEnvelopeXdrBase64()
-    case .feeBumpTransaction(let feeBumpTx):
-        stellar.sign(feeBumpTx: feeBumpTx, keyPair: sponsorPrivateKey)
-        return feeBumpTx.toEnvelopeXdrBase64()
-    case .invalidXdrErr:
-        throw ValidationError.invalidArgument(message: "invalid xdr")
-    }
-}
-```
-
-</WalletCodeExample>
-
-Cuando el cliente recibe la transacción completamente firmada, puede ser decodificada y enviada a la red Stellar:
-
-<WalletCodeExample>
-
-```kt
-suspend fun recoverSigned(xdrString: String) {
-  val signedTransaction = stellar.decodeTransaction(xdrString)
-
-  stellar.submitTransaction(signedTransaction)
-}
-
-```
-
-```typescript
-const signedTransaction = stellar.decodeTransaction(xdrString);
-
-await wallet.stellar().submitTransaction(signedTransaction);
-```
-
-```dart
-var signedTransaction = stellar.decodeTransaction(xdrStringFromBackend);
-
-bool success = await stellar.submitTransaction(signedTransaction);
-```
-
-```swift
-let signedTransactionEnum = stellar.decodeTransaction(xdr: xdrStringFromBackend)
-
-switch signedTransactionEnum {
-case .transaction(let tx):
-    try await stellar.submitTransaction(signedTransaction: tx)
-case .feeBumpTransaction(let feeBumpTx):
-    try await stellar.submitTransaction(signedFeeBumpTransaction: feeBumpTx)
-case .invalidXdrErr:
-    throw ValidationError.invalidArgument(message: "invalid xdr")
-}
-```
-
-</WalletCodeExample>
-
-## Enviar Transacción
-
-:::info
-
-Se recomienda encarecidamente utilizar las funciones de envío de transacciones del SDK de billetera en lugar de las alternativas de Horizon. El SDK de billetera maneja elegantemente las excepciones de tiempo de espera y fuera de tarifa.
-
-:::
-
-Finalmente, vamos a enviar una transacción firmada a la red Stellar. Nota que una transacción patrocinada debe ser firmada tanto por la cuenta como por el patrocinador.
-
-La transacción se vuelve a presentar automáticamente en el error 504 de Horizon (tiempo de espera), que indica un aumento repentino en la actividad de la red.
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun signAndSubmit() {
-  val signedTxn = createAccount().sign(sourceAccountKeyPair)
-  wallet.stellar().submitTransaction(signedTxn)
-}
-```
-
-```typescript
-const signedTxn = transaction.sign(sourceAccountKeyPair);
-await wallet.stellar().submitTransaction(signedTxn);
-```
-
-```dart
-stellar.sign(transaction, sourceAccountKeyPair);
-bool success = await stellar.submitTransaction(transaction);
-```
-
-```swift
-stellar.sign(tx: transaction, keyPair: sourceAccountKeyPair)
-try await stellar.submitTransaction(signedTransaction: transaction)
-```
-
-</WalletCodeExample>
-
-Sin embargo, el método anterior no maneja elegantemente la fijación de precios de tarifas en aumento en la red. Si la tarifa requerida para que una transacción se incluya en el ledger se vuelve demasiado alta y la transacción caduca antes de entrar en el ledger, este método arrojará una excepción.
-
-Así que, en su lugar, el enfoque alternativo es:
-
-<WalletCodeExample>
-
-```kotlin
-suspend fun submitWithFeeIncrease() {
-  wallet.stellar().submitWithFeeIncrease(sourceAccountKeyPair, Duration.ofSeconds(30), 100u) {
-    this.createAccount(destinationAccountKeyPair)
-  }
-}
-```
-
-```typescript
-const buildingFunction = (builder) =>
-  builder.transfer(kp.publicKey, new NativeAssetId(), "2");
-
-await stellar.submitWithFeeIncrease({
-  sourceAddress: kp,
-  timeout: 30,
-  baseFeeIncrease: 100,
-  buildingFunction,
-});
-```
-
-```dart
-bool success = await stellar.submitWithFeeIncrease(
-    sourceAddress: sourceAccountKeyPair,
-    timeout: const Duration(seconds: 30),
-    baseFeeIncrease: 100,
-    maxBaseFee: 2000,
-    buildingFunction: (builder) =>
-    builder.transfer(destinationAccountKeyPair.address, NativeAssetId(), "10.0"));
-```
-
-```swift
-try await stellar.submitWithFeeIncrease(
-  sourceAddress: sourceAccountKeyPair,
-  timeout: 30,
-  baseFeeIncrease: 100,
-  maxBaseFee: 2000,
-  buildingFunction: {
-      (builder) in try! builder
-          .transfer(destinationAddress: destinationAccountKeyPair.address,
-                    assetId: NativeAssetId(),
-                    amount: 10.0)
-  })
-```
-
-</WalletCodeExample>
-
-Esto creará y firmará la transacción que se originó desde el `sourceAccountKeyPair`. Cada 30 segundos, esta función volverá a construir esta transacción con una nueva tarifa (aumentada en 100 stroops), repitiendo la firma y la presentación. Una vez que la transacción sea exitosa, la función devolverá el cuerpo de la transacción. Nota que cualquier otro error finalizará el ciclo de reintentos y se lanzará una excepción.
-
-## Accediendo al SDK de Horizon
-
-Es muy sencillo utilizar el SDK de Horizon conectándose a la misma instancia de Horizon que una clase `Wallet`. Para hacerlo, simplemente llama a:
-
-<WalletCodeExample>
-
-```kotlin
-val server = wallet.stellar().server
-```
-
-```typescript
-const server = wallet.stellar().server;
-```
-
-```dart
-var server = wallet.stellar().server;
-```
-
-```swift
-let server = wallet.stellar.server
-```
-
-</WalletCodeExample>
-
-Y puedes trabajar con la instancia del servidor Horizon:
-
-<WalletCodeExample>
-
-```kt
-val stellarTransaction = server.transactions().transaction("transaction_id")
-```
-
-```typescript
-const stellarTransaction = server
-  .transactions()
-  .forAccount("account_id")
-  .call();
-```
-
-```dart
-var transactions = await server.transactions.forAccount("accountId").execute();
-```
-
-```swift
-let transactionsEnum = await server.transactions.getTransactions(forAccount: "accountId")
-switch transactionsEnum {
-case .success(let page):
-    let transactions = page.records
-case .failure(let error):
-    throw error
-}
-```
-
-</WalletCodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/README.mdx
deleted file mode 100644
index 802edb60e1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Guías de Cómo-Hacer
-description: Aquí encontrarás guías realmente útiles
-sidebar_position: 40
-hide_table_of_contents: true
----
-
-Esta sección proporciona instrucciones paso a paso para ayudar a los usuarios a completar tareas específicas relacionadas con el desarrollo en Stellar. Estas tareas pueden incluir instrucciones para metas relacionadas con la redacción de contratos, la interacción con contratos, la construcción de aplicaciones, el uso de operaciones Stellar, la configuración de infraestructura y más.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/README.mdx
deleted file mode 100644
index dc5487335f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Archivo del Estado
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 77
----
-
-La nueva estrategia de Soroban para combatir el exceso de estado puede presentar una curva de aprendizaje para los desarrolladores. Aquí hay algunas guías rápidas que te ayudarán en el proceso. Lee más en la [sección de Archivo de Estado](../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/create-restoration-footprint-js.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/create-restoration-footprint-js.mdx
deleted file mode 100644
index c1df2ea4ca..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/create-restoration-footprint-js.mdx
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: Crear manualmente una huella de restauración para restaurar datos archivados usando el SDK de JavaScript
-hide_table_of_contents: true
-description: Configurar manualmente una huella de restauración con el SDK de JavaScript
----
-
-:::info
-
-La operación manual (`RestoreFootprintOp`) ya no es necesaria en su mayoría a partir del Protocolo 23, ya que las entradas archivadas se restauran automáticamente cuando aparecen en una huella durante `InvokeHostFunctionOp`. `RestoreFootprintOp` puede usarse en casos excepcionales [descritos en esta sección](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#contract-data-automatic-restoration).
-
-:::
-
-En esta guía, crearemos un método utilitario llamado `createRestorationFootprint` que se utiliza para crear manualmente una huella de restauración y restaurar datos archivados en un contrato.
-
-Primero revisemos cómo se almacenan los datos en un contrato inteligente con los tres tipos diferentes de archivo de estado:
-
-| Temporal                                    | Instancia                                                       | Persistente                                                     |
-| ------------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------- |
-| Opción más económica                        | Opción costosa                                                  | Opción costosa                                                  |
-| Eliminado después de que el TTL alcance `0` | Archivado cuando el TTL alcance `0`                             | Archivado cuando el TTL alcance `0`                             |
-| No se puede restaurar                       | Se puede restaurar utilizando la operación `RestoreFootprintOp` | Se puede restaurar utilizando la operación `RestoreFootprintOp` |
-| Cantidad ilimitada de almacenamiento        | Cantidad limitada de almacenamiento disponible                  | Cantidad ilimitada de almacenamiento                            |
-
-Como se ve arriba, todos los datos del contrato se archivan automáticamente cuando el TTL alcanza `0`, excepto las entradas `Temporal`, que se eliminan permanentemente del ledger.
-
-Ambos tipos `Instancia` y `Persistente` son adecuados para almacenar datos que no se pueden recrear fácilmente, con la matiz de que `Instancia` comparte el mismo TTL que la instancia del contrato mientras que `Persistente` no, y, si la instancia del contrato no se archiva, los datos `Persistente` pueden ser archivados y necesitar ser restaurados antes de invocar el contrato.
-
-Para una explicación detallada del archivado de datos de contratos, consulta la [sección Archivado del Estado](./../../../learn/fundamentals/contract-development/storage/state-archival.mdx) en la Enciclopedia.
-
-```typescript
-import {
-  Contract,
-  Networks,
-  Keypair,
-  Operation,
-  TransactionBuilder,
-  xdr,
-  Address,
-  Account,
-  Transaction,
-} from "@stellar/stellar-sdk";
-
-async function createRestorationFootprint(
-  account: Account,
-  contractAddress: string,
-  fee: string,
-  dataKey: xdr.ScVal,
-  signer: Keypair,
-) {
-  // Initialise contract & address
-  const contract: Contract = new Contract(contractAddress);
-  const address: Address = Address.fromString(contract.contractId());
-  // Setup contract data
-  const contractDataXDR = xdr.LedgerKey.contractData(
-    new xdr.LedgerKeyContractData({
-      contract: address.toScAddress(),
-      key: dataKey,
-      durability: xdr.ContractDataDurability.persistent(),
-    }),
-  );
-  // Prepare transaction data
-  const restoreData: xdr.SorobanTransactionData =
-    new xdr.SorobanTransactionData({
-      resources: new xdr.SorobanResources({
-        footprint: new xdr.LedgerFootprint({
-          readOnly: [],
-          readWrite: [contractDataXDR],
-        }),
-        instructions: 0,
-        readBytes: 0,
-        writeBytes: 0,
-      }),
-      resourceFee: xdr.Int64.fromString("0"),
-      // @ts-ignore
-      ext: new xdr.ExtensionPoint(0),
-    });
-  // Restore transaction with created restoration footprint
-  const restoreTx: Transaction = new TransactionBuilder(account, { fee: fee })
-    .setNetworkPassphrase(Networks.TESTNET)
-    .setSorobanData(restoreData)
-    .addOperation(Operation.restoreFootprint({}))
-    .build();
-
-  restoreTx.sign(signer);
-}
-```
-
-## Revisión del código
-
-Como estamos utilizando [Stellar SDK para JavaScript](https://stellar.github.io/js-stellar-sdk/) `js-stellar-sdk`, primero importamos el módulo.
-
-Nuestra función requerirá los siguientes parámetros:
-
-- `account`: La cuenta de Stellar desde la cual se enviará la transacción.
-- `contractAddress`: La dirección del contrato que se va a restaurar.
-- `fee`: La tarifa de la transacción.
-- `dataKey`: La clave para los datos del contrato que se van a restaurar.
-- `signer`: El keypair que firmará la transacción.
-
-Después de inicializar las instancias de contrato y dirección, creamos una representación XDR de los datos del contrato que incluye:
-
-- `contract`: La dirección del contrato.
-- `key`: La clave para los datos del contrato.
-- `durability`: Especifica que los datos del contrato son persistentes - asumimos que es `Persistente`.
-
-A continuación, estamos preparando los datos de la transacción (Soroban) con:
-
-- `resources`: Especifica los recursos necesarios para la transacción.
-- `footprint`: Define qué partes del ledger se leerán y se escribirán.
-- `instructions`, `readBytes`, `writeBytes`: Establece los límites de recursos (todos establecidos en 0 aquí).
-- `resourceFee`: Establece la tarifa de recursos en 0 (marcador).
-- `ext`: Punto de extensión para uso futuro (establecido en 0).
-
-Ten en cuenta que para las huellas de restauración solo necesitamos completar `readWrite`.
-
-La transacción ahora se puede enviar a la red Stellar (de prueba) y firmarse para restaurar los datos del contrato especificado.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/extend-persistent-entry-js.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/extend-persistent-entry-js.mdx
deleted file mode 100644
index 8891863e93..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/extend-persistent-entry-js.mdx
+++ /dev/null
@@ -1,145 +0,0 @@
----
-title: Extender una entrada persistente y un contrato utilizando el SDK de JavaScript
-description: Cómo extender una entrada persistente y un contrato utilizando el SDK de JavaScript
----
-
-El almacenamiento persistente proporciona un mecanismo duradero para retener datos en la red durante un largo período. Los datos del usuario, las instancias de contrato y su código correspondiente (hash wasm) se almacenan como almacenamiento de instancia con durabilidad persistente para asegurar que permanezcan disponibles y sean gestionados de manera eficiente por el sistema de archivo de la red.
-
-Cada entrada realizada en el almacenamiento persistente se almacena como un almacén clave-valor. Una entrada consiste en:
-
-- Una clave (identificador para los datos)
-- Un valor (los datos en sí)
-- Un Tiempo de Vida (TTL) que determina cuánto tiempo permanecen los datos en la red
-
-Cuando el TTL caduca, los datos se archivan en la red y ya no son accesibles a menos que se desarchiven. Para evitar que los datos y contratos sean inaccesibles, el TTL puede extenderse antes de que caduque.
-
-## Proceso de Extensión
-
-1. Crea la clave del ledger para la entrada que va a extenderse.
-2. Construye una transacción que incluya la operación `extendFootprintTtl` con tu TTL objetivo y adjunta los datos de la transacción de Soroban.
-3. Prepara la transacción, fírmala con tu clave secreta y envíala a la red.
-
-### Extender una entrada persistente
-
-```javascript
-const StellarSdk = require("@stellar/stellar-sdk");
-const { Server } = require("@stellar/stellar-sdk/rpc");
-
-async function extendPersistentEntryTTL(contractId, storageKey, sourceKeypair) {
-  const server = new Server("https://soroban-testnet.stellar.org");
-  const account = await server.getAccount(sourceKeypair.publicKey());
-  const fee = "100"; // BASE_FEE of 100 stroops
-
-  // Create an identifier for the persistent entry
-  const persistentEntry = new StellarSdk.xdr.LedgerKey.contractData({
-    contract: StellarSdk.Address.fromString(contractId).toScAddress(),
-    key: StellarSdk.xdr.ScVal.scvSymbol(storageKey),
-    durability: StellarSdk.xdr.ContractDataDurability.persistent(),
-  });
-
-  // Build the transaction
-  let transaction = new StellarSdk.TransactionBuilder(account, {
-    fee,
-    networkPassphrase: StellarSdk.Networks.TESTNET,
-  })
-    .addOperation(
-      StellarSdk.Operation.extendFootprintTtl({
-        extendTo: 100_000, // The number of ledgers past the LCL (last closed ledger) by which to extend. Roughly 5 days
-      }),
-    )
-    .setTimeout(30)
-    .build();
-
-  // Attach Soroban transaction data
-  const sorobanData = new StellarSdk.SorobanDataBuilder()
-    .setReadOnly(persistentEntry)
-    .build();
-  transaction.setSorobanData(sorobanData);
-
-  // Prepare the transaction for signing.
-  transaction = await server.prepareTransaction(transaction);
-
-  transaction.sign(sourceKeypair);
-  return await server.sendTransaction(transaction);
-}
-```
-
-### Extender el código del contrato
-
-```javascript
-const StellarSdk = require("@stellar/stellar-sdk");
-const { Server } = require("@stellar/stellar-sdk/rpc");
-
-async function extendContractCodeTTL(contractId, sourceKeypair) {
-  const server = new Server("https://soroban-testnet.stellar.org");
-  const account = await server.getAccount(sourceKeypair.publicKey());
-  const fee = "100";
-
-  // Get the footprint
-  const contract = new StellarSdk.Contract(contractId);
-  const footprint = contract.getFootprint();
-
-  // Build the transaction
-  let transaction = new StellarSdk.TransactionBuilder(account, {
-    fee,
-    networkPassphrase: StellarSdk.Networks.TESTNET,
-  })
-    .addOperation(
-      StellarSdk.Operation.extendFootprintTtl({
-        extendTo: 100_000, //The number of ledgers past the LCL by which to extend
-        footprint: footprint,
-      }),
-    )
-    .setTimeout(30)
-    .build();
-
-  // Attach Soroban transaction data
-  const sorobanData = new StellarSdk.SorobanDataBuilder()
-    .setFootprint(footprint)
-    .build();
-  transaction.setSorobanData(sorobanData);
-
-  // Prepare the transaction
-  transaction = await server.prepareTransaction(transaction);
-
-  transaction.sign(sourceKeypair);
-  return await server.sendTransaction(transaction);
-}
-```
-
-### Extender tanto el contrato como una entrada persistente
-
-En Stellar, cada operación de Soroban debe ser la única operación de Soroban en una sola transacción. Además, las entradas del ledger persistente tienen sus propios valores de TTL que se evalúan de forma independiente. Debido a que la operación de extensión de TTL solo acepta una huella de ledger por transacción, no puedes combinar extensiones para diferentes entradas del ledger en una sola transacción. En cambio, debes crear dos transacciones separadas para garantizar que cada clave de ledger se extienda correctamente.
-
-```javascript
-async function extendContractAndPersistentEntry(
-  contractId,
-  storageKey,
-  sourceKeypair,
-) {
-  // Extend the persistent entry
-  const persistentResult = await extendPersistentEntryTTL(
-    contractId,
-    storageKey,
-    sourceKeypair,
-  );
-
-  // Extend the contract code
-  const contractResult = await extendContractCodeTTL(contractId, sourceKeypair);
-  return { persistentResult, contractResult };
-}
-```
-
-Ejemplo de uso:
-
-```javascript
-const contractId = "CBEE2DHGMYRKJKSJO5E55LBKFMPXE57ZWKTXTCRMC5ANIRJ7IW2Y2WVE";
-const storageKey = "BALANCE";
-const sourceKeypair = StellarSdk.Keypair.fromSecret(
-  "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
-);
-
-extendPersistentEntryTTL(contractId, storageKey, sourceKeypair)
-  .then((result) => console.log("Extension successful:", result))
-  .catch((error) => console.error("Extension failed:", error));
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/restore-contract-js.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/restore-contract-js.mdx
deleted file mode 100644
index f1382a8c80..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/restore-contract-js.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Restaurar un contrato utilizando el SDK de JavaScript
-hide_table_of_contents: true
-description: Restaurar una instancia de contrato archivada o el código del contrato utilizando el SDK de JavaScript
----
-
-Como puedes imaginar, si tu instancia de contrato desplegada o el código que la respalda está archivado, no se puede cargar para ejecutar tus invocaciones. Recuerda, hay una relación distinta de uno a muchos en la cadena entre el código de un contrato y las instancias desplegadas de ese contrato:
-
-```mermaid
-flowchart LR
-    A[my instance] & B[your instance]--> C[contract WASM]
-```
-
-Necesitamos **ambos** que estén en vivo para que nuestras llamadas al contrato funcionen.
-
-Trabajemos en cómo se pueden recuperar. El proceso de recuperación es ligeramente diferente por una razón conveniente: no necesitamos simulación para averiguar las huellas. En su lugar, podemos aprovechar [`Contract.getFootprint()`](https://stellar.github.io/js-soroban-client/Contract.html#getFootprint), que prepara una huella con las claves del ledger utilizadas por una instancia de contrato dada (incluido su código WASM de respaldo).
-
-Desafortunadamente, aún necesitamos simulación para averiguar las _tarifas_ para nuestra restauración. Esto, sin embargo, puede ser fácilmente cubierto por el helper [`Server.prepareTransaction()`](https://stellar.github.io/js-soroban-client/Server.html#prepareTransaction) del SDK, que hará simulación y ensamblaje por nosotros.
-
-:::info
-
-Esta guía hace uso de la función (bien nombrada) `submitTx` que creamos en [otra guía](../transactions/submit-transaction-wait-js.mdx).
-
-:::
-
-```typescript
-import {
-  BASE_FEE,
-  Contract,
-  Keypair,
-  Networks,
-  TransactionBuilder,
-  SorobanDataBuilder,
-  Operation
-} from "@stellar/stellar-sdk";
-import { Server, Api } from "@stellar/stellar-sdk/rpc";
-
-const server = new Server("https://soroban-testnet.stellar.org");
-
-async function restoreContract(
-  signer: Keypair,
-  c: Contract,
-): Promise<Api.GetTransactionResponse> {
-  const instance = c.getFootprint();
-
-  const account = await server.getAccount(signer.publicKey());
-  const wasmEntry = await server.getLedgerEntries(
-    getWasmLedgerKey(instance)
-  );
-
-  const restoreTx = new TransactionBuilder(account, { fee: BASE_FEE })
-    .setNetworkPassphrase(Networks.TESTNET)
-    .setSorobanData(
-      // Set the restoration footprint (remember, it should be in the
-      // read-write part!)
-      new SorobanDataBuilder().setReadWrite([
-        instance,
-        wasmEntry
-      ]).build(),
-    )
-    .addOperation(Operation.restoreFootprint({}))
-    .build();
-
-  const preppedTx = await server.prepareTransaction(restoreTx);
-  preppedTx.sign(signer);
-  return submitTx(preppedTx);
-}
-
-function getWasmLedgerKey(entry: xdr.ContractDataEntry):  {
-  return xdr.LedgerKey.contractCode(
-    new xdr.LedgerKeyContractCode({
-      hash: entry.val().instance().wasmHash()
-    })
-  );
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/restore-data-js.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/restore-data-js.mdx
deleted file mode 100644
index 1a8f5b720c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/restore-data-js.mdx
+++ /dev/null
@@ -1,102 +0,0 @@
----
-title: Restaurar datos de contrato archivados utilizando el SDK de JavaScript
-hide_table_of_contents: true
-description: Restaurar datos de contrato persistentes archivados utilizando el SDK de JavaScript
----
-
-:::info
-
-La operación manual (`RestoreFootprintOp`), en su mayor parte, ya no es necesaria a partir del Protocolo 23, ya que las entradas archivadas se restauran automáticamente cuando aparecen en una footprint durante `InvokeHostFunctionOp`. `RestoreFootprintOp` puede usarse en casos raros [descritos en esta sección](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#contract-data-automatic-restoration).
-
-:::
-
-Esta es una ocurrencia bastante probable: mi pieza de datos persistentes está archivada porque no he interactuado con mi contrato en un tiempo. ¿Cómo puedo hacerlo accesible de nuevo?
-
-Si descubres que un fragmento de datos persistentes está archivado, se puede restaurar utilizando una transacción Stellar que contenga una operación `RestoreFootprintOp`. Haremos dos suposiciones para el bien de esta guía:
-
-- La instancia del contrato en sí aún está en vivo (es decir, otros han estado extendiendo su TTL mientras has estado ausente).
-- No sabes cómo se representa tu dato archivado en el ledger.
-
-El proceso de restauración que utilizaremos implica tres pasos discretos:
-
-1. Simular nuestra transacción como lo haríamos normalmente.
-2. Si la simulación lo indica, realizamos la restauración con una operación `RestoreFootprintOp` utilizando las pistas que obtuvimos de la simulación.
-3. Volvemos a intentar ejecutar nuestra transacción inicial.
-
-Aquí hay una función llamada `submitOrRestoreAndRetry()` que se encargará de todos esos pasos por nosotros:
-
-:::info
-
-Esta guía utiliza la función (convenientemente llamada) `submitTx` que creamos en [otra guía](../transactions/submit-transaction-wait-js.mdx).
-
-:::
-
-```typescript
-import {
-  BASE_FEE,
-  Networks,
-  Keypair,
-  TransactionBuilder,
-  SorobanDataBuilder,
-  rpc as StellarRpc,
-  xdr,
-} from "@stellar/stellar-sdk"; // add'l imports to submitTx
-const { Api, assembleTransaction } = StellarRpc;
-
-// assume that `server` is the Server() instance from the submitTx
-
-async function submitOrRestoreAndRetry(
-  signer: Keypair,
-  tx: Transaction,
-): Promise<Api.GetTransactionResponse> {
-  // We can't use `prepareTransaction` here because we want to do
-  // restoration if necessary, basically assembling the simulation ourselves.
-  const sim = await server.simulateTransaction(tx);
-
-  // Other failures are out of scope of this tutorial.
-  if (!Api.isSimulationSuccess(sim)) {
-    throw sim;
-  }
-
-  // If simulation didn't fail, we don't need to restore anything! Just send it.
-  if (!Api.isSimulationRestore(sim)) {
-    const prepTx = assembleTransaction(tx, sim);
-    prepTx.sign(signer);
-    return submitTx(prepTx);
-  }
-
-  // Build the restoration operation using the RPC server's hints.
-  const account = await server.getAccount(signer.publicKey());
-  let fee = parseInt(BASE_FEE);
-  fee += parseInt(sim.restorePreamble.minResourceFee);
-
-  const restoreTx = new TransactionBuilder(account, { fee: fee.toString() })
-    .setNetworkPassphrase(Networks.TESTNET)
-    .setSorobanData(sim.restorePreamble.transactionData.build())
-    .addOperation(Operation.restoreFootprint({}))
-    .build();
-
-  restoreTx.sign(signer);
-
-  const resp = await submitTx(restoreTx);
-  if (resp.status !== Api.GetTransactionStatus.SUCCESS) {
-    throw resp;
-  }
-
-  // now that we've restored the necessary data, we can retry our tx using
-  // the initial data from the simulation (which, hopefully, is still
-  // up-to-date)
-  const retryTxBuilder = TransactionBuilder.cloneFrom(tx, {
-    fee: (parseInt(tx.fee) + parseInt(sim.minResourceFee)).toString(),
-    sorobanData: sim.transactionData.build(),
-  });
-  // because we consumed a sequence number when restoring, we need to make sure
-  // we set the correct value on this copy
-  retryTxBuilder.source.incrementSequenceNumber();
-
-  const retryTx = retryTxBuilder.build();
-  retryTx.sign(signer);
-
-  return submitTx(retryTx);
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/test-ttl-extension.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/test-ttl-extension.mdx
deleted file mode 100644
index bf9d6d0304..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/archival/test-ttl-extension.mdx
+++ /dev/null
@@ -1,172 +0,0 @@
----
-title: Probar la lógica de extensión de TTL en contratos inteligentes
-hide_table_of_contents: true
-description: Probar contratos que extienden el tiempo de vida (TTL) de los datos del contrato
----
-
-Para probar contratos que extienden el [TTL](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#ttl) de datos del contrato mediante operaciones de almacenamiento `extend_ttl`, puedes usar la operación getter de TTL (`get_ttl`) en combinación con la manipulación del número de secuencia del libro mayor. Nota que la función `get_ttl` solo está disponible para pruebas y solo en Soroban SDK v21+.
-
-## Ejemplo
-
-Sigue el [ejemplo](https://github.com/stellar/soroban-examples/blob/main/ttl/src/lib.rs) que prueba las extensiones de TTL. El ejemplo tiene comentarios extensos, este documento solo destaca las partes más importantes.
-
-Usamos un contrato muy simple que solo extiende una entrada para cada tipo de almacenamiento de Soroban:
-
-```rust
-#[contractimpl]
-impl TtlContract {
-    /// Creates a contract entry in every kind of storage.
-    pub fn setup(env: Env) {
-        env.storage().persistent().set(&DataKey::MyKey, &0);
-        env.storage().instance().set(&DataKey::MyKey, &1);
-        env.storage().temporary().set(&DataKey::MyKey, &2);
-    }
-
-    /// Extend the persistent entry TTL to 5000 ledgers, when its
-    /// TTL is smaller than 1000 ledgers.
-    pub fn extend_persistent(env: Env) {
-        env.storage()
-            .persistent()
-            .extend_ttl(&DataKey::MyKey, 1000, 5000);
-    }
-
-    /// Extend the instance entry TTL to become at least 10000 ledgers,
-    /// when its TTL is smaller than 2000 ledgers.
-    pub fn extend_instance(env: Env) {
-        env.storage().instance().extend_ttl(2000, 10000);
-    }
-
-    /// Extend the temporary entry TTL to become at least 7000 ledgers,
-    /// when its TTL is smaller than 3000 ledgers.
-    pub fn extend_temporary(env: Env) {
-        env.storage()
-            .temporary()
-            .extend_ttl(&DataKey::MyKey, 3000, 7000);
-    }
-}
-```
-
-El enfoque del ejemplo son las pruebas, así que los siguientes fragmentos de código provienen de `test.rs`.
-
-Es una buena idea definir los valores personalizados de la configuración de red relacionados con el TTL, ya que los valores predeterminados son definidos por el SDK y no son inmediatamente obvios para el lector de las pruebas:
-
-```rust
-env.ledger().with_mut(|li| {
-    // Current ledger sequence - the TTL is the number of
-    // ledgers from the `sequence_number` (exclusive) until
-    // the last ledger sequence where entry is still considered
-    // alive.
-    li.sequence_number = 100_000;
-    // Minimum TTL for persistent entries - new persistent (and instance)
-    // entries will have this TTL when created.
-    li.min_persistent_entry_ttl = 500;
-    // Minimum TTL for temporary entries - new temporary
-    // entries will have this TTL when created.
-    li.min_temp_entry_ttl = 100;
-    // Maximum TTL of any entry. Note, that entries can have their TTL
-    // extended indefinitely, but each extension can be at most
-    // `max_entry_ttl` ledger from the current `sequence_number`.
-    li.max_entry_ttl = 15000;
-});
-```
-
-También podrías usar la [configuración de red actual](../../../networks/resource-limits-fees.mdx#resource-fees) al configurar las pruebas, pero ten en cuenta que estos están sujetos a cambios, y el contrato debería poder trabajar con cualquier valor de estas configuraciones.
-
-Ahora ejecutamos un escenario de prueba que verifica la lógica de extensión de TTL (consulta la prueba [`test_extend_ttl_behavior`](https://github.com/stellar/soroban-examples/blob/f595fb5df06058ec0b9b829e9e4d0fe0513e0aa8/ttl/src/test.rs#L38) para el escenario completo). Primero, configuramos los datos y aseguramos que los valores iniciales de TTL correspondan a las configuraciones de red que hemos definido anteriormente:
-
-```rust
-client.setup();
-env.as_contract(&contract_id, || {
-    // Note, that TTL doesn't include the current ledger, but when entry
-    // is created the current ledger is counted towards the number of
-    // ledgers specified by `min_persistent/temp_entry_ttl`, thus
-    // the TTL is 1 ledger less than the respective setting.
-    assert_eq!(env.storage().persistent().get_ttl(&DataKey::MyKey), 499);
-    assert_eq!(env.storage().instance().get_ttl(), 499);
-    assert_eq!(env.storage().temporary().get_ttl(&DataKey::MyKey), 99);
-});
-```
-
-Nota que usamos `env.as_contract` para acceder al almacenamiento del contrato.
-
-Luego llamamos a las operaciones de extensión de TTL y verificamos que se comporten como se esperaba, por ejemplo:
-
-```rust
-// Extend persistent entry TTL to 5000 ledgers - now it is 5000.
-client.extend_persistent();
-env.as_contract(&contract_id, || {
-    assert_eq!(env.storage().persistent().get_ttl(&DataKey::MyKey), 5000);
-});
-```
-
-Para probar los umbrales de extensión (es decir, el máximo TTL actual que requiere extensión), necesitamos aumentar el número de secuencia del ledger:
-
-```rust
-// Now bump the ledger sequence by 5000 in order to sanity-check
-// the threshold settings of `extend_ttl` operations.
-env.ledger().with_mut(|li| {
-    li.sequence_number = 100_000 + 5_000;
-});
-// Now the TTL of every entry has been reduced by 5000 ledgers.
-env.as_contract(&contract_id, || {
-    assert_eq!(env.storage().persistent().get_ttl(&DataKey::MyKey), 0);
-    assert_eq!(env.storage().instance().get_ttl(), 5000);
-    assert_eq!(env.storage().temporary().get_ttl(&DataKey::MyKey), 2000);
-});
-```
-
-Luego podemos extender las entradas nuevamente y asegurarnos de que solo las entradas que están por debajo del umbral hayan sido extendidas (específicamente, las entradas persistentes y temporales en este ejemplo):
-
-```rust
-client.extend_persistent();
-client.extend_instance();
-client.extend_temporary();
-env.as_contract(&contract_id, || {
-    assert_eq!(env.storage().persistent().get_ttl(&DataKey::MyKey), 5000);
-    // Instance TTL hasn't been increased because the remaining TTL
-    // (5000 ledgers) is larger than the threshold used by
-    // `extend_instance` (2000 ledgers)
-    assert_eq!(env.storage().instance().get_ttl(), 5000);
-    assert_eq!(env.storage().temporary().get_ttl(&DataKey::MyKey), 7000);
-});
-```
-
-Soroban SDK también emula el comportamiento para las entradas que tienen su TTL caducado. Las entradas temporales se comportan 'como si' hubieran sido eliminadas (consulta la prueba [`test_temp_entry_removal`](https://github.com/stellar/soroban-examples/blob/f595fb5df06058ec0b9b829e9e4d0fe0513e0aa8/ttl/src/test.rs#L112) para el escenario completo):
-
-```rust
-client.extend_temporary();
-// Bump the ledger sequence by 7001 ledgers (one ledger past TTL).
-env.ledger().with_mut(|li| {
-    li.sequence_number = 100_000 + 7001;
-});
-// Now the entry is no longer present in the environment.
-env.as_contract(&contract_id, || {
-    assert_eq!(env.storage().temporary().has(&DataKey::MyKey), false);
-});
-```
-
-Las entradas persistentes son más sutiles: cuando una transacción que se ejecuta on-chain contiene una entrada persistente que ha sido archivada (es decir, cuyo TTL ha expirado) en la huella, entonces ni siquiera se instanciará el entorno Soroban. Dado que este comportamiento no se puede reproducir directamente en el entorno de prueba, en su lugar se producirá un error 'interno' irreparable tan pronto como se acceda a una entrada archivada, y la prueba hará `panic`:
-
-```rust
-#[test]
-#[should_panic(expected = "[testing-only] Accessed contract instance key that has been archived.")]
-fn test_persistent_entry_archival() {
-    let env = create_env();
-    let contract_id = env.register(TtlContract, ());
-    let client = TtlContractClient::new(&env, &contract_id);
-    client.setup();
-    // Extend the instance TTL to 10000 ledgers.
-    client.extend_instance();
-    // Bump the ledger sequence by 10001 ledgers (one ledger past TTL).
-    env.ledger().with_mut(|li| {
-        li.sequence_number = 100_000 + 10_001;
-    });
-    // Now any call involving the expired contract (such as `extend_instance`
-    // call here) will panic as soon as that contract is accessed.
-    client.extend_instance();
-}
-```
-
-## Probar la extensión de TTL para otras instancias de contrato
-
-A veces, un contrato puede querer extender el TTL de otros contratos y/o sus entradas de Wasm (normalmente eso sucedería en contratos de fábrica). Esta lógica puede ser cubierta de manera similar al ejemplo anterior usando `env.deployer().get_contract_instance_ttl(&contract)` para obtener el TTL de cualquier instancia de contrato, y `env.deployer().get_contract_code_ttl(&contract)` para obtener el TTL de cualquier entrada de Wasm de contrato. Puedes encontrar un ejemplo de uso de estas funciones en la [suite de pruebas](https://github.com/stellar/rs-soroban-sdk/blob/ff05c3d4cbed97db50142372e9d7a4fa4a8d1d5d/soroban-sdk/src/tests/storage_testutils.rs#L76) del SDK.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/README.mdx
deleted file mode 100644
index b698e5fdde..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Autorización de Contrato
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 1
----
-
-Aprende sobre la autorización de contratos inteligentes en Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/_category_.json
deleted file mode 100644
index 9e90632aac..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/check-auth-tutorials.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/check-auth-tutorials.mdx
deleted file mode 100644
index 8cbf809ff2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/check-auth-tutorials.mdx
+++ /dev/null
@@ -1,1483 +0,0 @@
----
-title: Uso de __check_auth de maneras interesantes
-description: Dos guías que explican cómo usar __check_auth
----
-
-<head>
-  <title>Uso de __check_auth de maneras interesantes</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Uso de __check_auth de maneras interesantes" />
-  <meta
-    property="og:description"
-    content="Esta guía te mostrará maneras interesantes de usar __check_auth en tus aplicaciones Soroban"
-  />
-</head>
-
-## Tutorial 1: restricción basada en tiempo para transferencias de tokens
-
-Imagina un contrato de cuenta multi-sig donde ciertas acciones, como transferir tokens, necesitan estar controladas por el tiempo transcurrido entre transferencias consecutivas. Por ejemplo, una transferencia de tokens solo debería permitirse si ha pasado un cierto período desde la última transferencia. Esto puede ser útil en escenarios donde quieres limitar la frecuencia de transacciones para prevenir abuso o implementar limitación de velocidad.
-
-### Conceptos básicos
-
-#### Restricciones basadas en tiempo
-
-La idea es hacer cumplir un intervalo mínimo de tiempo entre transferencias consecutivas de tokens. Cada token puede tener su propio límite de tiempo, y el contrato hará un seguimiento del último momento de transferencia para cada token.
-
-#### Almacenamiento de datos
-
-El contrato almacenará el límite de tiempo y la hora de la última transferencia para cada token en su almacenamiento para mantener un registro de estos valores entre transacciones.
-
-### Explicación del código
-
-#### Estructura del contrato e importaciones
-
-```rust
-#![no_std]
-
-use soroban_sdk::{
-    auth::{Context, CustomAccountInterface}, contract, contracterror, contractimpl, contracttype, symbol_short, Address,
-    BytesN, Env, Symbol, Vec,
-};
-#[contract]
-struct AccountContract;
-
-#[contracttype]
-#[derive(Clone)]
-pub struct Signature {
-    pub public_key: BytesN<32>,
-    pub signature: BytesN<64>,
-}
-
-#[contracttype]
-#[derive(Clone)]
-enum DataKey {
-    SignerCnt,
-    Signer(BytesN<32>),
-    TimeLimit(Address),
-    LastTransferTime(Address),
-}
-
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum AccError {
-    NotEnoughSigners = 1,
-    NegativeAmount = 2,
-    BadSignatureOrder = 3,
-    UnknownSigner = 4,
-    InvalidContext = 5,
-    TimeLimitExceeded = 6,
-}
-
-const TRANSFER_FN: Symbol = symbol_short!("transfer");
-
-```
-
-#### Inicialización del contrato
-
-1. Inicializa el contrato con una lista de claves públicas de los firmantes
-2. Almacena el número de firmantes en el almacenamiento del contrato
-
-```rust
-#[contractimpl]
-impl AccountContract {
-
-    pub fn init(env: Env, signers: Vec<BytesN<32>>) {
-        for signer in signers.iter() {
-            env.storage().instance().set(&DataKey::Signer(signer), &());
-        }
-        env.storage()
-            .instance()
-            .set(&DataKey::SignerCnt, &signers.len());
-    }
-}
-```
-
-#### Configuración de límites de tiempo
-
-1. Permite establecer un límite de tiempo para un token específico
-2. Asegura que solo el contrato mismo pueda establecer estos límites requiriendo la autorización del contrato
-
-```rust
-#[contractimpl]
-
-impl AccountContract {
-    pub fn set_time(env: Env, token: Address, time_limit: u64) {
-        env.current_contract_address().require_auth();
-        env.storage()
-            .instance()
-            .set(&DataKey::TimeLimit(token), &time_limit);
-    }
-}
-```
-
-#### Autenticación y autorización personalizada
-
-1. Autentica las firmas
-2. Verifica si todos los firmantes requeridos han firmado
-3. Itera a través del contexto de autorización para verificar la política de autorización
-
-```rust
-#[contractimpl]
-impl CustomAccountInterface for AccountContract {
-
-    type Error = AccError;
-    type Signature = Vec<Signature>;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,
-        signature_payload: BytesN<32>,
-        signatures: Vec<Signature>,
-        auth_context: Vec<Context>,
-    ) -> Result<(), AccError> {
-        authenticate(&env, &signature_payload, &signatures)?;
-
-        let tot_signers: u32 = env
-            .storage()
-            .instance()
-            .get::<_, u32>(&DataKey::SignerCnt)
-            .unwrap();
-
-        let all_signed = tot_signers == signatures.len();
-
-        let curr_contract = env.current_contract_address();
-
-        for context in auth_context.iter() {
-            verify_authorization_policy(
-                &env,
-                &context,
-                &curr_contract,
-                all_signed,
-            )?;
-        }
-        Ok(())
-    }
-
-}
-```
-
-#### Lógica de autenticación
-
-1. Verifica que las firmas estén en el orden correcto y que cada firmante esté autorizado
-2. Utiliza la función [ed25519_verify](https://docs.rs/soroban-sdk/latest/soroban_sdk/crypto/struct.Crypto.html#method.ed25519_verify) para verificar cada firma
-
-```rust
- fn authenticate(
-        env: &Env,
-        signature_payload: &BytesN<32>,
-        signatures: &Vec<Signature>,
-) -> Result<(), AccError> {
-    for i in 0..signatures.len() {
-        let signature = signatures.get_unchecked(i);
-        if i > 0 {
-            let prev_signature = signatures.get_unchecked(i - 1);
-            if prev_signature.public_key >= signature.public_key {
-                return Err(AccError::BadSignatureOrder);
-            }
-        }
-        if !env
-            .storage()
-            .instance()
-            .has(&DataKey::Signer(signature.public_key.clone()))
-        {
-            return Err(AccError::UnknownSigner);
-        }
-        env.crypto().ed25519_verify(
-            &signature.public_key,
-            &signature_payload.clone().into(),
-            &signature.signature,
-        );
-    }
-    Ok(())
-}
-```
-
-#### Verificación de la política de autorización
-
-1. Comprueba si la función que se está llamando es una función de transferencia o aprobación
-2. Aplica la restricción basada en tiempo comparando el tiempo actual con el momento de la última transferencia
-3. Actualiza la hora de la última transferencia si se permite la transferencia
-
-```rust
-fn verify_authorization_policy(
-        env: &Env,
-        context: &Context,
-        curr_contract: &Address,
-        all_signed: bool,
-    ) -> Result<(), AccError> {
-        let contract_context = match context {
-            Context::Contract(c) => {
-                if &c.contract == curr_contract {
-                    if !all_signed {
-                        return Err(AccError::NotEnoughSigners);
-                    }
-                }
-                c
-            }
-            Context::CreateContractHostFn(_) => return Err(AccError::InvalidContext),
-        };
-
-        if contract_context.fn_name != TRANSFER_FN
-            && contract_context.fn_name != Symbol::new(env, "approve")
-        {
-            return Ok(());
-        }
-
-        let current_time = env.ledger().timestamp();
-        let time_limit: Option<u64> =
-            env.storage()
-                .instance()
-                .get::<_, u64>(&DataKey::TimeLimit(contract_context.contract.clone()));
-
-        if let Some(limit) = time_limit {
-            let last_transfer_time: u64 = env.storage()
-                .instance()
-                .get::<_, u64>(&DataKey::LastTransferTime(contract_context.contract.clone()))
-                .unwrap_or(0);
-
-            if current_time - last_transfer_time < limit {
-                return Err(AccError::TimeLimitExceeded);
-            }
-
-            env.storage()
-                .instance()
-                .set(&DataKey::LastTransferTime(contract_context.contract.clone()), &current_time);
-        }
-        Ok(())
-}
-```
-
-#### Resumen
-
-El contrato comienza inicializándose con un conjunto de firmantes autorizados. Permite establecer un límite de tiempo para las transferencias de tokens, controlando qué tan frecuentemente se puede transferir un token. La función \_\_check_auth es el núcleo del proceso de autorización, asegurando que todas las firmas necesarias sean válidas y verificando la restricción basada en tiempo para las transferencias de tokens. Si no ha pasado el tiempo requerido desde la última transferencia, el contrato negará la operación, aplicando la limitación de velocidad deseada. Al registrar la hora de la última transferencia y hacer cumplir un intervalo mínimo de tiempo entre transferencias, el contrato limita efectivamente la frecuencia de transferencias de tokens, resolviendo el problema de posible abuso mediante transacciones consecutivas rápidas.
-
-#### Código completo
-
-Aquí están todos los fragmentos apilados juntos en un único archivo para mayor comodidad:
-
-```rust
-#![no_std]
-use soroban_sdk::{
-    auth::{Context, CustomAccountInterface}, contract, contracterror, contractimpl, contracttype, symbol_short, Address,
-    BytesN, Env, Symbol, Vec,
-};
-#[contract]
-struct AccountContract;
-
-#[contracttype]
-#[derive(Clone)]
-pub struct Signature {
-    pub public_key: BytesN<32>,
-    pub signature: BytesN<64>,
-}
-
-#[contracttype]
-#[derive(Clone)]
-enum DataKey {
-    SignerCnt,
-    Signer(BytesN<32>),
-    TimeLimit(Address),
-    LastTransferTime(Address),
-}
-
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum AccError {
-    NotEnoughSigners = 1,
-    NegativeAmount = 2,
-    BadSignatureOrder = 3,
-    UnknownSigner = 4,
-    InvalidContext = 5,
-    TimeLimitExceeded = 6,
-}
-
-const TRANSFER_FN: Symbol = symbol_short!("transfer");
-
-#[contractimpl]
-impl AccountContract {
-    pub fn init(env: Env, signers: Vec<BytesN<32>>) {
-        for signer in signers.iter() {
-            env.storage().instance().set(&DataKey::Signer(signer), &());
-        }
-        env.storage()
-            .instance()
-            .set(&DataKey::SignerCnt, &signers.len());
-    }
-
-    pub fn set_time(env: Env, token: Address, time_limit: u64) {
-        env.current_contract_address().require_auth();
-        env.storage()
-            .instance()
-            .set(&DataKey::TimeLimit(token), &time_limit);
-    }
-}
-
-#[contractimpl]
-impl CustomAccountInterface for AccountContract {
-
-    type Error = AccError;
-    type Signature = Vec<Signature>;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,
-        signature_payload: BytesN<32>,
-        signatures: Vec<Signature>,
-        auth_context: Vec<Context>,
-    ) -> Result<(), AccError> {
-        authenticate(&env, &signature_payload, &signatures)?;
-
-        let tot_signers: u32 = env
-            .storage()
-            .instance()
-            .get::<_, u32>(&DataKey::SignerCnt)
-            .unwrap();
-
-        let all_signed = tot_signers == signatures.len();
-
-        let curr_contract = env.current_contract_address();
-
-        for context in auth_context.iter() {
-            verify_authorization_policy(
-                &env,
-                &context,
-                &curr_contract,
-                all_signed,
-            )?;
-        }
-        Ok(())
-    }
-
-}
-
-fn authenticate(
-    env: &Env,
-    signature_payload: &BytesN<32>,
-    signatures: &Vec<Signature>,
-) -> Result<(), AccError> {
-    for i in 0..signatures.len() {
-        let signature = signatures.get_unchecked(i);
-        if i > 0 {
-            let prev_signature = signatures.get_unchecked(i - 1);
-            if prev_signature.public_key >= signature.public_key {
-                return Err(AccError::BadSignatureOrder);
-            }
-        }
-        if !env
-            .storage()
-            .instance()
-            .has(&DataKey::Signer(signature.public_key.clone()))
-        {
-            return Err(AccError::UnknownSigner);
-        }
-        env.crypto().ed25519_verify(
-            &signature.public_key,
-            &signature_payload.clone().into(),
-            &signature.signature,
-        );
-    }
-    Ok(())
-}
-
-fn verify_authorization_policy(
-    env: &Env,
-    context: &Context,
-    curr_contract: &Address,
-    all_signed: bool,
-) -> Result<(), AccError> {
-    let contract_context = match context {
-        Context::Contract(c) => {
-            if &c.contract == curr_contract {
-                if !all_signed {
-                    return Err(AccError::NotEnoughSigners);
-                }
-            }
-            c
-        }
-        Context::CreateContractHostFn(_) => return Err(AccError::InvalidContext),
-    };
-
-    if contract_context.fn_name != TRANSFER_FN
-        && contract_context.fn_name != Symbol::new(env, "approve")
-    {
-        return Ok(());
-    }
-
-    let current_time = env.ledger().timestamp();
-    let time_limit: Option<u64> =
-        env.storage()
-            .instance()
-            .get::<_, u64>(&DataKey::TimeLimit(contract_context.contract.clone()));
-
-    if let Some(limit) = time_limit {
-        let last_transfer_time: u64 = env.storage()
-            .instance()
-            .get::<_, u64>(&DataKey::LastTransferTime(contract_context.contract.clone()))
-            .unwrap_or(0);
-
-        if current_time - last_transfer_time < limit {
-            return Err(AccError::TimeLimitExceeded);
-        }
-
-        env.storage()
-            .instance()
-            .set(&DataKey::LastTransferTime(contract_context.contract.clone()), &current_time);
-    }
-    Ok(())
-}
-
-mod test;
-```
-
-Estos son los casos de prueba:
-
-```rust
-#![cfg(test)]
-extern crate std;
-
-use ed25519_dalek::Keypair;
-use ed25519_dalek::Signer;
-use rand::thread_rng;
-use soroban_sdk::auth::ContractContext;
-use soroban_sdk::symbol_short;
-use soroban_sdk::testutils::Address as _;
-use soroban_sdk::testutils::AuthorizedFunction;
-use soroban_sdk::testutils::AuthorizedInvocation;
-use soroban_sdk::Val;
-use soroban_sdk::{
-    auth::Context, testutils::BytesN as _, vec, Address, BytesN, Env, IntoVal, Symbol,
-};
-use soroban_sdk::testutils::Ledger;
-use soroban_sdk::testutils::LedgerInfo;
-use crate::AccError;
-use crate::{AccountContract, AccountContractClient, Signature};
-
-fn generate_keypair() -> Keypair {
-    Keypair::generate(&mut thread_rng())
-}
-
-fn signer_public_key(e: &Env, signer: &Keypair) -> BytesN<32> {
-    signer.public.to_bytes().into_val(e)
-}
-
-fn create_account_contract(e: &Env) -> AccountContractClient {
-    AccountContractClient::new(e, &e.register(AccountContract {}, ()))
-}
-
-fn sign(e: &Env, signer: &Keypair, payload: &BytesN<32>) -> Val {
-    Signature {
-        public_key: signer_public_key(e, signer),
-        signature: signer
-            .sign(payload.to_array().as_slice())
-            .to_bytes()
-            .into_val(e),
-    }
-    .into_val(e)
-}
-
-fn token_auth_context(e: &Env, token_id: &Address, fn_name: Symbol, amount: i128) -> Context {
-    Context::Contract(ContractContext {
-        contract: token_id.clone(),
-        fn_name,
-        args: ((), (), amount).into_val(e),
-    })
-}
-
-#[test]
-fn test_token_auth() {
-    let env = Env::default();
-    env.mock_all_auths();
-
-    let account_contract = create_account_contract(&env);
-
-    let mut signers = [generate_keypair(), generate_keypair()];
-    if signers[0].public.as_bytes() > signers[1].public.as_bytes() {
-        signers.swap(0, 1);
-    }
-    account_contract.init(&vec![
-        &env,
-        signer_public_key(&env, &signers[0]),
-        signer_public_key(&env, &signers[1]),
-    ]);
-
-    let payload = BytesN::random(&env);
-    let token = Address::generate(&env);
-
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1000),
-        ],
-    )
-    .unwrap();
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1000),
-        ],
-    )
-    .unwrap();
-
-    // Add a time limit of 1000 seconds for the token.
-    account_contract.set_time(&token, &1000);
-
-    assert_eq!(
-        env.auths(),
-        std::vec![(
-            account_contract.address.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    account_contract.address.clone(),
-                    symbol_short!("set_time"),
-                    (token.clone(), 1000_u64).into_val(&env),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-
-    // Attempting a transfer within the time limit should fail.
-    env.ledger().set(LedgerInfo {
-        timestamp: 0,
-        protocol_version: 1,
-        sequence_number: 10,
-        network_id: Default::default(),
-        base_reserve: 10,
-        min_temp_entry_ttl: 16,
-        min_persistent_entry_ttl: 16,
-        max_entry_ttl: 100_000,
-    });
-
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1001)
-        ],
-    )
-    .err()
-    .unwrap()
-    .unwrap() == AccError::TimeLimitExceeded;
-
-    // Simulate passing of time to allow the next transfer.
-    env.ledger().set(LedgerInfo {
-        timestamp: 1000,
-        protocol_version: 1,
-        sequence_number: 10,
-        network_id: Default::default(),
-        base_reserve: 10,
-        min_temp_entry_ttl: 16,
-        min_persistent_entry_ttl: 16,
-        max_entry_ttl: 100_000,
-    });
-
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1001),
-        ],
-    )
-    .unwrap();
-}
-```
-
-## Tutorial 2: implementar una billetera inteligente (WebAuthn)
-
-Imagina un mundo donde las contraseñas tradicionales son obsoletas. En ese mundo, WebAuthn (Autenticación Web) se ha convertido en el estándar para interacciones seguras en línea. Alice, una entusiasta de blockchain, quiere crear una billetera que aproveche la tecnología WebAuthn para una seguridad mejorada. Decide implementar una billetera WebAuthn en Stellar, permitiendo a los usuarios gestionar sus activos digitales usando las características biométricas o llaves de seguridad de su dispositivo (por ejemplo, YubiKey, Google Titan Security Key, etc.).
-
-### Conceptos básicos
-
-WebAuthn es un estándar web para la autenticación sin contraseña. Permite a los usuarios autenticarse usando biometría (como huellas digitales o reconocimiento facial).
-
-La billetera WebAuthn implementada en este tutorial podrá:
-
-1. Registrar y gestionar credenciales de usuario (claves públicas)
-2. Autenticar usuarios para firmar transacciones
-3. Diferenciar entre administradores y usuarios regulares
-4. Permitir actualizaciones del contrato para mejoras futuras
-
-:::info
-
-El crédito del código de este tutorial es para el trabajo de [@kalepail](https://github.com/kalepail) en passkeys, que puedes explorar más [aquí](https://github.com/kalepail/passkey-kit).
-
-:::
-
-### Explicación del código
-
-#### Estructura del contrato e importaciones
-
-Esta sección configura la estructura del contrato e importa los componentes necesarios del Soroban SDK.
-
-```rust
-#![no_std]
-
-use soroban_sdk::{
-    auth::{Context, CustomAccountInterface},
-    contract, contracterror, contractimpl, contracttype,
-    crypto::Hash,
-    panic_with_error, symbol_short, Bytes, BytesN, Env, FromVal, Symbol, Vec,
-};
-
-#[contract]
-pub struct Contract;
-```
-
-#### Definiciones de errores
-
-Este enum define posibles errores que pueden ocurrir durante la ejecución del contrato.
-
-```rust
-#[contracterror]
-#[derive(Copy, Clone, Eq, PartialEq, Debug)]
-pub enum Error {
-    NotFound = 1,
-    NotPermitted = 2,
-    ClientDataJsonChallengeIncorrect = 3,
-    Secp256r1PublicKeyParse = 4,
-    Secp256r1SignatureParse = 5,
-    Secp256r1VerifyFailed = 6,
-    JsonParseError = 7,
-}
-```
-
-#### Funciones principales del contrato
-
-Estas funciones manejan la adición y eliminación de firmantes, actualización del contrato y gestión del conteo de administradores.
-
-```rust
-// Implementing the Contract struct with various methods
-#[contractimpl]
-impl Contract {
-    // Method to add a new signer, potentially as an admin
-    pub fn add(env: Env, id: Bytes, pk: BytesN<65>, mut admin: bool) -> Result<(), Error> {
-        // Check if the instance storage has the ADMIN_SIGNER_COUNT key
-        if env.storage().instance().has(&ADMIN_SIGNER_COUNT) {
-            // Require authentication from the current contract address
-            env.current_contract_address().require_auth();
-        } else {
-            // If it's the first signer, ensure they are an admin
-            admin = true;
-        }
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // If the signer is an admin
-        if admin {
-            // Check if the ID exists in temporary storage
-            if env.storage().temporary().has(&id) {
-                // Remove the ID from temporary storage
-                env.storage().temporary().remove(&id);
-            }
-
-            // Update the admin signer count by incrementing it
-            Self::update_admin_signer_count(&env, true);
-
-            // Store the public key in persistent storage with the given ID
-            env.storage().persistent().set(&id, &pk);
-
-            // Extend the TTL for the persistent storage entry
-            env.storage()
-                .persistent()
-                .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-        } else {
-            // If the signer is not an admin
-            // Check if the ID exists in persistent storage
-            if env.storage().persistent().has(&id) {
-                // Update the admin signer count by decrementing it
-                Self::update_admin_signer_count(&env, false);
-
-                // Remove the ID from persistent storage
-                env.storage().persistent().remove(&id);
-            }
-
-            // Store the public key in temporary storage with the given ID
-            env.storage().temporary().set(&id, &pk);
-
-            // Extend the TTL for the temporary storage entry
-            env.storage()
-                .temporary()
-                .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-        }
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Publish an event indicating a new signer has been added
-        env.events()
-            .publish((EVENT_TAG, symbol_short!("add"), id, pk), admin);
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Method to remove a signer
-    pub fn remove(env: Env, id: Bytes) -> Result<(), Error> {
-        // Require authentication from the current contract address
-        env.current_contract_address().require_auth();
-
-        // Check if the ID exists in temporary storage
-        if env.storage().temporary().has(&id) {
-            // Remove the ID from temporary storage
-            env.storage().temporary().remove(&id);
-        } else if env.storage().persistent().has(&id) {
-            // If the ID exists in persistent storage, decrement the admin signer count
-            Self::update_admin_signer_count(&env, false);
-
-            // Remove the ID from persistent storage
-            env.storage().persistent().remove(&id);
-        }
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Publish an event indicating a signer has been removed
-        env.events()
-            .publish((EVENT_TAG, symbol_short!("remove"), id), ());
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Method to update the contract with new WASM code
-    pub fn update(env: Env, hash: BytesN<32>) -> Result<(), Error> {
-        // Require authentication from the current contract address
-        env.current_contract_address().require_auth();
-
-        // Update the contract's WASM code with the new hash
-        env.deployer().update_current_contract_wasm(hash);
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Helper method to update the count of admin signers
-    fn update_admin_signer_count(env: &Env, add: bool) {
-        // Get the current count of admin signers from instance storage, defaulting to 0
-        let count = env
-            .storage()
-            .instance()
-            .get::<Symbol, i32>(&ADMIN_SIGNER_COUNT)
-            .unwrap_or(0)
-            + if add { 1 } else { -1 };
-
-        // If the count is less than or equal to 0, trigger an error
-        if count <= 0 {
-            panic_with_error!(env, Error::NotPermitted)
-        }
-
-        // Update the admin signer count in instance storage
-        env.storage()
-            .instance()
-            .set::<Symbol, i32>(&ADMIN_SIGNER_COUNT, &count);
-    }
-}
-
-```
-
-#### Estructura de la firma
-
-Esta estructura representa una firma WebAuthn.
-
-```rust
-#[contracttype]
-pub struct Signature {
-    pub id: Bytes,
-    pub authenticator_data: Bytes,
-    pub client_data_json: Bytes,
-    pub signature: BytesN<64>,
-}
-```
-
-#### Implementación de CustomAccountInterface
-
-Implementa la lógica principal de autenticación para la billetera WebAuthn.
-
-```rust
-#[contractimpl]
-impl CustomAccountInterface for Contract {
-    // Defining the error and signature types for the trait
-    type Error = Error;
-    type Signature = Signature;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,                         // The environment context
-        signature_payload: Hash<32>,      // The payload that needs to be signed
-        signature: Signature,             // The signature provided by the client
-        auth_contexts: Vec<Context>,      // Contexts for authentication
-    ) -> Result<(), Error> {
-        // Destructure the signature into its components
-        let Signature {
-            id,
-            mut authenticator_data,
-            client_data_json,
-            signature,
-        } = signature;
-
-        // Set the maximum time-to-live (TTL) for storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Try to retrieve the public key associated with the id from temporary storage
-        let pk = match env.storage().temporary().get(&id) {
-            Some(pk) => {
-                // Check if a session signer is trying to perform protected actions
-                for context in auth_contexts.iter() {
-                    match context {
-                        // If the context is a contract call
-                        Context::Contract(c) => {
-                            // Ensure that the current contract is not performing restricted actions
-                            if c.contract == env.current_contract_address()
-                                && (c.fn_name != symbol_short!("remove")
-                                    || (c.fn_name == symbol_short!("remove")
-                                        && Bytes::from_val(&env, &c.args.get(0).unwrap()) != id))
-                            {
-                                return Err(Error::NotPermitted);
-                            }
-                        }
-                        _ => {} // Allow other contexts (e.g., deploying new contracts)
-                    };
-                }
-
-                // Extend the TTL for the temporary storage entry
-                env.storage()
-                    .temporary()
-                    .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-                pk // Return the public key
-            }
-            // If not found in temporary storage, try persistent storage
-            None => {
-                env.storage()
-                    .persistent()
-                    .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-                env.storage().persistent().get(&id).ok_or(Error::NotFound)?
-            }
-        };
-
-        // Extend the authenticator data with the SHA-256 hash of the client data JSON
-        authenticator_data.extend_from_array(&env.crypto().sha256(&client_data_json).to_array());
-
-        // Verify the signature using the secp256r1 elliptic curve algorithm
-        env.crypto()
-            .secp256r1_verify(&pk, &env.crypto().sha256(&authenticator_data), &signature);
-
-        // Parse the client data JSON, extracting the base64 URL encoded challenge
-        let client_data_json = client_data_json.to_buffer::<1024>();
-        let client_data_json = client_data_json.as_slice();
-        let (client_data_json, _): (ClientDataJson, _) =
-            serde_json_core::de::from_slice(client_data_json).map_err(|_| Error::JsonParseError)?;
-
-        // Build the expected challenge from the signature payload
-        let mut expected_challenge = [0u8; 43];
-        base64_url::encode(&mut expected_challenge, &signature_payload.to_array());
-
-        // Check that the challenge inside the client data JSON matches the expected challenge
-        if client_data_json.challenge.as_bytes() != expected_challenge {
-            return Err(Error::ClientDataJsonChallengeIncorrect);
-        }
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        Ok(()) // Return success
-    }
-}
-```
-
-#### Codificación Base64 url
-
-Esta función proporciona funcionalidad de codificación Base64 URL usada en el proceso WebAuthn.
-
-```rust
-// Define the Base64 URL alphabet as a constant byte array.
-const ALPHABET: &[u8] = b"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_";
-
-// The `encode` function takes a mutable reference to a destination byte array `dst` and a source byte array `src`.
-pub fn encode(dst: &mut [u8], src: &[u8]) {
-    // Initialize destination index `di` and source index `si` to 0.
-    let mut di: usize = 0;
-    let mut si: usize = 0;
-    // Calculate the length of the source array that is a multiple of 3.
-    let n = (src.len() / 3) * 3;-
-
-    // Process the source array in chunks of 3 bytes.
-    while si < n {
-        // Combine 3 bytes into a single 24-bit value.
-        let val = (src[si] as usize) << 16 | (src[si + 1] as usize) << 8 | (src[si + 2] as usize);
-        // Encode the 24-bit value into 4 Base64 characters.
-        dst[di] = ALPHABET[val >> 18 & 0x3F];
-        dst[di + 1] = ALPHABET[val >> 12 & 0x3F];
-        dst[di + 2] = ALPHABET[val >> 6 & 0x3F];
-        dst[di + 3] = ALPHABET[val & 0x3F];
-        // Increment the source index by 3 and the destination index by 4.
-        si += 3;
-        di += 4;
-    }
-
-    // Calculate the remaining number of bytes in the source array.
-    let remain = src.len() - si;
-
-    // If there are no remaining bytes, return early.
-    if remain == 0 {
-        return;
-    }
-
-    // Initialize a 24-bit value with the remaining byte(s).
-    let mut val = (src[si] as usize) << 16;
-
-    // If there are 2 remaining bytes, add the second byte to the 24-bit value.
-    if remain == 2 {
-        val |= (src[si + 1] as usize) << 8;
-    }
-
-    // Encode the remaining bytes into 2 or 3 Base64 characters.
-    dst[di] = ALPHABET[val >> 18 & 0x3F];
-    dst[di + 1] = ALPHABET[val >> 12 & 0x3F];
-
-    // If there are 2 remaining bytes, encode the third Base64 character.
-    if remain == 2 {
-        dst[di + 2] = ALPHABET[val >> 6 & 0x3F];
-    }
-}
-
-```
-
-#### Explicación escrita del código
-
-El contrato de billetera WebAuthn gestiona credenciales de usuario y autenticación. Permite agregar y eliminar firmantes, distinguiendo entre administradores y usuarios regulares. La función agregar registra nuevos firmantes, almacenando claves de administradores de forma persistente y claves regulares temporalmente. La función eliminar borra firmantes y actualizar permite mejoras en el contrato. El núcleo de la seguridad de la billetera es la función `__check_auth`, que verifica firmas WebAuthn. Verifica la firma contra la clave pública almacenada, valida el client data JSON y asegura que el desafío coincida con el valor esperado. El contrato usa las capacidades de almacenamiento de Soroban para gestionar claves y conteos de administradores, con diferentes TTL (Tiempo de vida) para almacenamiento persistente y temporal.
-
-#### Casos de prueba
-
-Estos son casos de prueba para asegurar que nuestra billetera WebAuthn funcione correctamente. Usaremos las utilidades de prueba del Soroban SDK para crear y ejecutar estas pruebas.
-
-```rust
-#[cfg(test)]
-mod test {
-    use std::println;
-    extern crate std;
-
-    use soroban_sdk::{
-        vec,
-        Bytes,
-        BytesN,
-        Env,
-        IntoVal,
-    };
-
-    use crate::{Contract, ContractClient, Error, Signature};
-
-    #[test]
-    fn test() {
-        let env = Env::default();
-        let deployee_address = env.register(Contract, ());
-        let deployee_client = ContractClient::new(&env, &deployee_address);
-
-        // Test data
-        let id = Bytes::from_array(
-            &env,
-            &[243, 248, 216, 74, 226, 218, 85, 102, 196, 167, 14, 151, 124, 42, 73, 136, 138, 102, 187, 140],
-        );
-        let pk = BytesN::from_array(
-            &env,
-            &[4, 163, 142, 245, 242, 113, 55, 104, 189, 52, 128, 238, 206, 174, 194, 177, 4, 100,
-              161, 243, 177, 255, 10, 53, 57, 194, 205, 45, 208, 10, 131, 167, 93, 44, 123, 126, 95,
-              219, 207, 230, 175, 90, 96, 41, 121, 197, 127, 180, 74, 236, 160, 0, 60, 185, 211, 174,
-              133, 215, 200, 208, 230, 51, 210, 94, 214],
-        );
-
-        // Test adding a signer
-        deployee_client.add(&id, &pk, &true);
-
-        // Test authentication
-        let signature_payload = BytesN::from_array(
-            &env,
-            &[150, 22, 248, 96, 91, 4, 111, 72, 170, 101, 57, 225, 210, 199, 91, 29, 159, 227, 209,
-              6, 231, 63, 222, 209, 232, 57, 112, 98, 140, 118, 206, 245],
-        );
-
-        let signature = Signature {
-            authenticator_data: Bytes::from_array(
-                &env,
-                &[75, 74, 206, 229, 181, 139, 119, 89, 254, 159, 95, 149, 227, 164, 109, 143, 188,
-                  228, 143, 219, 181, 216, 77, 123, 142, 172, 60, 20, 162, 154, 181, 187, 29, 0, 0, 0, 0],
-            ),
-            client_data_json: Bytes::from_array(
-                &env,
-                &[123, 34, 116, 121, 112, 101, 34, 58, 34, 119, 101, 98, 97, 117, 116, 104, 110, 46,
-                  103, 101, 116, 34, 44, 34, 99, 104, 97, 108, 108, 101, 110, 103, 101, 34, 58, 34,
-                  108, 104, 98, 52, 89, 70, 115, 69, 98, 48, 105, 113, 90, 84, 110, 104, 48, 115,
-                  100, 98, 72, 90, 95, 106, 48, 81, 98, 110, 80, 57, 55, 82, 54, 68, 108, 119, 89,
-                  111, 120, 50, 122, 118, 85, 34, 44, 34, 111, 114, 105, 103, 105, 110, 34, 58, 34,
-                  104, 116, 116, 112, 115, 58, 47, 47, 112, 97, 115, 115, 107, 101, 121, 45, 107,
-                  105, 116, 45, 100, 101, 109, 111, 46, 112, 97, 103, 101, 115, 46, 100, 101, 118, 34, 125],
-            ),
-            id: id.clone(),
-            signature: BytesN::from_array(
-                &env,
-                &[74, 48, 29, 120, 181, 135, 255, 178, 105, 76, 82, 118, 29, 135, 193, 72, 123, 144,
-                  138, 214, 125, 27, 33, 159, 169, 200, 151, 55, 7, 250, 111, 172, 86, 89, 162, 167,
-                  148, 105, 144, 68, 21, 249, 61, 253, 80, 61, 54, 29, 14, 162, 12, 173, 206, 194,
-                  144, 227, 11, 225, 74, 254, 191, 221, 103, 86],
-            ),
-        };
-
-        let result: Result<(), Result<Error, _>> = env.try_invoke_contract_check_auth(
-            &deployee_address,
-            &signature_payload,
-            signature.into_val(&env),
-            &vec![&env],
-        );
-
-        println!("{:?}", result);
-        assert!(result.is_ok());
-
-    }
-}
-```
-
-#### Resumen
-
-Esta implementación de billetera WebAuthn ofrece una manera segura y amigable de gestionar activos digitales en Stellar. Aprovecha los beneficios de seguridad de WebAuthn mientras mantiene la flexibilidad necesaria para las interacciones con blockchain.
-
-#### Código completo
-
-Aquí están todos los fragmentos apilados en un solo archivo para mayor comodidad:
-
-```rust
-#![no_std]
-
-use soroban_sdk::{
-    auth::{Context, CustomAccountInterface},
-    contract, contracterror, contractimpl, contracttype,
-    crypto::Hash,
-    panic_with_error, symbol_short, Bytes, BytesN, Env, FromVal, Symbol, Vec,
-};
-
-#[contract]
-pub struct Contract;
-
-// Error definitions for the contract
-#[contracterror]
-#[derive(Copy, Clone, Eq, PartialEq, Debug)]
-pub enum Error {
-    NotFound = 1,
-    NotPermitted = 2,
-    ClientDataJsonChallengeIncorrect = 3,
-    Secp256r1PublicKeyParse = 4,
-    Secp256r1SignatureParse = 5,
-    Secp256r1VerifyFailed = 6,
-    JsonParseError = 7,
-}
-
-// Structure representing a WebAuthn signature
-#[contracttype]
-pub struct Signature {
-    pub id: Bytes,
-    pub authenticator_data: Bytes,
-    pub client_data_json: Bytes,
-    pub signature: BytesN<64>,
-}
-
-// Implementing the Contract struct with various methods
-#[contractimpl]
-impl Contract {
-    // Method to add a new signer, potentially as an admin
-    pub fn add(env: Env, id: Bytes, pk: BytesN<65>, mut admin: bool) -> Result<(), Error> {
-        // Check if the instance storage has the ADMIN_SIGNER_COUNT key
-        if env.storage().instance().has(&ADMIN_SIGNER_COUNT) {
-            // Require authentication from the current contract address
-            env.current_contract_address().require_auth();
-        } else {
-            // If it's the first signer, ensure they are an admin
-            admin = true;
-        }
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // If the signer is an admin
-        if admin {
-            // Check if the ID exists in temporary storage
-            if env.storage().temporary().has(&id) {
-                // Remove the ID from temporary storage
-                env.storage().temporary().remove(&id);
-            }
-
-            // Update the admin signer count by incrementing it
-            Self::update_admin_signer_count(&env, true);
-
-            // Store the public key in persistent storage with the given ID
-            env.storage().persistent().set(&id, &pk);
-
-            // Extend the TTL for the persistent storage entry
-            env.storage()
-                .persistent()
-                .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-        } else {
-            // If the signer is not an admin
-            // Check if the ID exists in persistent storage
-            if env.storage().persistent().has(&id) {
-                // Update the admin signer count by decrementing it
-                Self::update_admin_signer_count(&env, false);
-
-                // Remove the ID from persistent storage
-                env.storage().persistent().remove(&id);
-            }
-
-            // Store the public key in temporary storage with the given ID
-            env.storage().temporary().set(&id, &pk);
-
-            // Extend the TTL for the temporary storage entry
-            env.storage()
-                .temporary()
-                .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-        }
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Publish an event indicating a new signer has been added
-        env.events()
-            .publish((EVENT_TAG, symbol_short!("add"), id, pk), admin);
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Method to remove a signer
-    pub fn remove(env: Env, id: Bytes) -> Result<(), Error> {
-        // Require authentication from the current contract address
-        env.current_contract_address().require_auth();
-
-        // Check if the ID exists in temporary storage
-        if env.storage().temporary().has(&id) {
-            // Remove the ID from temporary storage
-            env.storage().temporary().remove(&id);
-        } else if env.storage().persistent().has(&id) {
-            // If the ID exists in persistent storage, decrement the admin signer count
-            Self::update_admin_signer_count(&env, false);
-
-            // Remove the ID from persistent storage
-            env.storage().persistent().remove(&id);
-        }
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Publish an event indicating a signer has been removed
-        env.events()
-            .publish((EVENT_TAG, symbol_short!("remove"), id), ());
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Method to update the contract with new WASM code
-    pub fn update(env: Env, hash: BytesN<32>) -> Result<(), Error> {
-        // Require authentication from the current contract address
-        env.current_contract_address().require_auth();
-
-        // Update the contract's WASM code with the new hash
-        env.deployer().update_current_contract_wasm(hash);
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Helper method to update the count of admin signers
-    fn update_admin_signer_count(env: &Env, add: bool) {
-        // Get the current count of admin signers from instance storage, defaulting to 0
-        let count = env
-            .storage()
-            .instance()
-            .get::<Symbol, i32>(&ADMIN_SIGNER_COUNT)
-            .unwrap_or(0)
-            + if add { 1 } else { -1 };
-
-        // If the count is less than or equal to 0, trigger an error
-        if count <= 0 {
-            panic_with_error!(env, Error::NotPermitted)
-        }
-
-        // Update the admin signer count in instance storage
-        env.storage()
-            .instance()
-            .set::<Symbol, i32>(&ADMIN_SIGNER_COUNT, &count);
-    }
-}
-
-// Implementing the core authentication logic for the WebAuthn wallet
-#[contractimpl]
-impl CustomAccountInterface for Contract {
-    // Defining the error and signature types for the trait
-    type Error = Error;
-    type Signature = Signature;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,                         // The environment context
-        signature_payload: Hash<32>,      // The payload that needs to be signed
-        signature: Signature,             // The signature provided by the client
-        auth_contexts: Vec<Context>,      // Contexts for authentication
-    ) -> Result<(), Error> {
-        // Destructure the signature into its components
-        let Signature {
-            id,
-            mut authenticator_data,
-            client_data_json,
-            signature,
-        } = signature;
-
-        // Get the maximum time-to-live (TTL) for storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Try to retrieve the public key associated with the id from temporary storage
-        let pk = match env.storage().temporary().get(&id) {
-            Some(pk) => {
-                // Check if a session signer is trying to perform protected actions
-                for context in auth_contexts.iter() {
-                    match context {
-                        // If the context is a contract call
-                        Context::Contract(c) => {
-                            // Ensure that the current contract is not performing restricted actions
-                            if c.contract == env.current_contract_address()
-                                && (c.fn_name != symbol_short!("remove")
-                                    || (c.fn_name == symbol_short!("remove")
-                                        && Bytes::from_val(&env, &c.args.get(0).unwrap()) != id))
-                            {
-                                return Err(Error::NotPermitted);
-                            }
-                        }
-                        _ => {} // Allow other contexts (e.g., deploying new contracts)
-                    };
-                }
-
-                // Extend the TTL for the temporary storage entry
-                env.storage()
-                    .temporary()
-                    .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-                pk // Return the public key
-            }
-            // If not found in temporary storage, try persistent storage
-            None => {
-                env.storage()
-                    .persistent()
-                    .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-                env.storage().persistent().get(&id).ok_or(Error::NotFound)?
-            }
-        };
-
-        // Extend the authenticator data with the SHA-256 hash of the client data JSON
-        authenticator_data.extend_from_array(&env.crypto().sha256(&client_data_json).to_array());
-
-        // Verify the signature using the secp256r1 elliptic curve algorithm
-        env.crypto()
-            .secp256r1_verify(&pk, &env.crypto().sha256(&authenticator_data), &signature);
-
-        // Parse the client data JSON, extracting the base64 URL encoded challenge
-        let client_data_json = client_data_json.to_buffer::<1024>();
-        let client_data_json = client_data_json.as_slice();
-        let (client_data_json, _): (ClientDataJson, _) =
-            serde_json_core::de::from_slice(client_data_json).map_err(|_| Error::JsonParseError)?;
-
-        // Build the expected challenge from the signature payload
-        let mut expected_challenge = [0u8; 43];
-        base64_url::encode(&mut expected_challenge, &signature_payload.to_array());
-
-        // Check that the challenge inside the client data JSON matches the expected challenge
-        if client_data_json.challenge.as_bytes() != expected_challenge {
-            return Err(Error::ClientDataJsonChallengeIncorrect);
-        }
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        Ok(()) // Return success
-    }
-}
-
-// Define the Base64 URL alphabet as a constant byte array.
-const ALPHABET: &[u8] = b"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_";
-
-// The `encode` function takes a mutable reference to a destination byte array `dst` and a source byte array `src`.
-pub fn encode(dst: &mut [u8], src: &[u8]) {
-    // Initialize destination index `di` and source index `si` to 0.
-    let mut di: usize = 0;
-    let mut si: usize = 0;
-    // Calculate the length of the source array that is a multiple of 3.
-    let n = (src.len() / 3) * 3;
-
-    // Process the source array in chunks of 3 bytes.
-    while si < n {
-        // Combine 3 bytes into a single 24-bit value.
-        let val = (src[si] as usize) << 16 | (src[si + 1] as usize) << 8 | (src[si + 2] as usize);
-        // Encode the 24-bit value into 4 Base64 characters.
-        dst[di] = ALPHABET[val >> 18 & 0x3F];
-        dst[di + 1] = ALPHABET[val >> 12 & 0x3F];
-        dst[di + 2] = ALPHABET[val >> 6 & 0x3F];
-        dst[di + 3] = ALPHABET[val & 0x3F];
-        // Increment the source index by 3 and the destination index by 4.
-        si += 3;
-        di += 4;
-    }
-
-    // Calculate the remaining number of bytes in the source array.
-    let remain = src.len() - si;
-
-    // If there are no remaining bytes, return early.
-    if remain == 0 {
-        return;
-    }
-
-    // Initialize a 24-bit value with the remaining byte(s).
-    let mut val = (src[si] as usize) << 16;
-
-    // If there are 2 remaining bytes, add the second byte to the 24-bit value.
-    if remain == 2 {
-        val |= (src[si + 1] as usize) << 8;
-    }
-
-    // Encode the remaining bytes into 2 or 3 Base64 characters.
-    dst[di] = ALPHABET[val >> 18 & 0x3F];
-    dst[di + 1] = ALPHABET[val >> 12 & 0x3F];
-
-    // If there are 2 remaining bytes, encode the third Base64 character.
-    if remain == 2 {
-        dst[di + 2] = ALPHABET[val >> 6 & 0x3F];
-    }
-}
-
-#[cfg(test)]
-mod test {
-    use std::println;
-    extern crate std;
-
-    use soroban_sdk::{
-        vec,
-        Bytes,
-        BytesN,
-        Env,
-        IntoVal,
-    };
-
-    use crate::{Contract, ContractClient, Error, Signature};
-
-    #[test]
-    fn test() {
-        let env = Env::default();
-        let deployee_address = env.register(Contract, ());
-        let deployee_client = ContractClient::new(&env, &deployee_address);
-
-        // Test data
-        let id = Bytes::from_array(
-            &env,
-            &[243, 248, 216, 74, 226, 218, 85, 102, 196, 167, 14, 151, 124, 42, 73, 136, 138, 102, 187, 140],
-        );
-        let pk = BytesN::from_array(
-            &env,
-            &[4, 163, 142, 245, 242, 113, 55, 104, 189, 52, 128, 238, 206, 174, 194, 177, 4, 100,
-              161, 243, 177, 255, 10, 53, 57, 194, 205, 45, 208, 10, 131, 167, 93, 44, 123, 126, 95,
-              219, 207, 230, 175, 90, 96, 41, 121, 197, 127, 180, 74, 236, 160, 0, 60, 185, 211, 174,
-              133, 215, 200, 208, 230, 51, 210, 94, 214],
-        );
-
-        // Test adding a signer
-        deployee_client.add(&id, &pk, &true);
-
-        // Test authentication
-        let signature_payload = BytesN::from_array(
-            &env,
-            &[150, 22, 248, 96, 91, 4, 111, 72, 170, 101, 57, 225, 210, 199, 91, 29, 159, 227, 209,
-              6, 231, 63, 222, 209, 232, 57, 112, 98, 140, 118, 206, 245],
-        );
-
-        let signature = Signature {
-            authenticator_data: Bytes::from_array(
-                &env,
-                &[75, 74, 206, 229, 181, 139, 119, 89, 254, 159, 95, 149, 227, 164, 109, 143, 188,
-                  228, 143, 219, 181, 216, 77, 123, 142, 172, 60, 20, 162, 154, 181, 187, 29, 0, 0, 0, 0],
-            ),
-            client_data_json: Bytes::from_array(
-                &env,
-                &[123, 34, 116, 121, 112, 101, 34, 58, 34, 119, 101, 98, 97, 117, 116, 104, 110, 46,
-                  103, 101, 116, 34, 44, 34, 99, 104, 97, 108, 108, 101, 110, 103, 101, 34, 58, 34,
-                  108, 104, 98, 52, 89, 70, 115, 69, 98, 48, 105, 113, 90, 84, 110, 104, 48, 115,
-                  100, 98, 72, 90, 95, 106, 48, 81, 98, 110, 80, 57, 55, 82, 54, 68, 108, 119, 89,
-                  111, 120, 50, 122, 118, 85, 34, 44, 34, 111, 114, 105, 103, 105, 110, 34, 58, 34,
-                  104, 116, 116, 112, 115, 58, 47, 47, 112, 97, 115, 115, 107, 101, 121, 45, 107,
-                  105, 116, 45, 100, 101, 109, 111, 46, 112, 97, 103, 101, 115, 46, 100, 101, 118, 34, 125],
-            ),
-            id: id.clone(),
-            signature: BytesN::from_array(
-                &env,
-                &[74, 48, 29, 120, 181, 135, 255, 178, 105, 76, 82, 118, 29, 135, 193, 72, 123, 144,
-                  138, 214, 125, 27, 33, 159, 169, 200, 151, 55, 7, 250, 111, 172, 86, 89, 162, 167,
-                  148, 105, 144, 68, 21, 249, 61, 253, 80, 61, 54, 29, 14, 162, 12, 173, 206, 194,
-                  144, 227, 11, 225, 74, 254, 191, 221, 103, 86],
-            ),
-        };
-
-        let result: Result<(), Result<Error, _>> = env.try_invoke_contract_check_auth(
-            &deployee_address,
-            &signature_payload,
-            signature.into_val(&env),
-            &vec![&env],
-        );
-
-        println!("{:?}", result);
-        assert!(result.is_ok());
-
-    }
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/contract-authorization.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/contract-authorization.mdx
deleted file mode 100644
index 62e6d5e4ad..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/auth/contract-authorization.mdx
+++ /dev/null
@@ -1,450 +0,0 @@
----
-title: Guía introductoria de autorización de contratos inteligentes
-hide_table_of_contents: true
-description: Aprende sobre la autorización de contratos inteligentes en Stellar
----
-
-## Introducción a la autorización de contratos inteligentes
-
-Por defecto, los contratos inteligentes pueden ser invocados sin autorización del llamador. La funcionalidad del contrato inteligente puede justificar, o incluso requerir, autorización. Supongamos que queremos leer o escribir información sensible: entonces el acceso al contrato debería estar restringido mediante autorización. Se requiere autorización si el contrato firma transacciones.
-
-Para una comprensión más profunda de cómo funciona la autorización, consulta la sección de [Seguridad](../../../learn/fundamentals/contract-development/authorization.mdx).
-
-### Autorización basada en direcciones
-
-Los contratos inteligentes de Stellar usan direcciones como identificadores para la autorización. Existen dos tipos de direcciones: direcciones de cuenta (direcciones G) y direcciones de contrato (direcciones C), pero proporcionan la misma interfaz. Esto significa que los desarrolladores no necesitan considerar el tipo de dirección usada para la autorización; los métodos de autorización tratan ambos tipos igual, desde el punto de vista del desarrollador.
-
-## 1. Autorización básica
-
-Los contratos inteligentes de Stellar tienen incorporados métodos de autorización, como `require_auth()` y `require_auth_for_args()`. Estos dos métodos ofrecen una forma sencilla de autenticar y autorizar usuarios en funciones del contrato.
-
-### `require_auth()`
-
-El método `require_auth()` autentica y autoriza a un usuario que invoca una función de contrato inteligente. Para determinar si un usuario ha autorizado la invocación de la función, simplemente llama a `require_auth()` en la dirección del usuario. La función del contrato no necesita considerar firmas u otros procesos de autorización.
-
-Para verificar si un usuario está autorizado a invocar una función, llama a `require_auth()` en la dirección del usuario:
-
-`<user_address>.require_auth()`
-
-Veamos cómo se puede añadir autorización a una función sencilla, en este caso, una función `increment()`. La función increment recibe dos argumentos, un usuario (dirección secreta) y un valor, que se usa para incrementar el valor actual del contador.
-
-La función llamará a `require_auth()` en el usuario cuando se invoque la función.
-
-```rust
-   pub fn increment(env: Env, user: Address, value: u32) -> u32 {
-      user.require_auth();
-
-      let mut count: u32 = env.storage().instance().get(&user).unwrap_or(0);
-      count += value;
-      env.storage().persistent().set(&user, &count);
-
-      count
-   }
-```
-
-La función primero comprobará si el usuario está autorizado, luego obtendrá el valor actual de `count` (o 0 si no hay valor almacenado). Luego, `count` se incrementa añadiendo el argumento `value` al `count` actual. El conteo incrementado se almacena y se devuelve. La dirección `user` se usa como clave de almacenamiento para obtener y establecer el valor `count` en el almacenamiento.
-
-Ejecuta el siguiente comando para invocar la función del contrato con la clave secreta del usuario para autorizarlo:
-
-```rust
-stellar contract invoke \
-  --id CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN \
-  --source-account alice \
-  --network testnet \
-  -- \
-  increment \
-  --user SDWDUC7IIZPRIDUZIK44UHUD2KOG6A5XWUGVZBQG2RM3J2L5DSOROBAN \
-  --value 10
-```
-
-La llamada a la función debería devolver la siguiente salida:
-
-```rust
-10
-```
-
-Si la autorización falla, la función causará un pánico en el contrato.
-
-Este ejemplo se basa en el contrato de autenticación del ejemplo en el [repositorio de ejemplos de Soroban](https://github.com/stellar/soroban-examples/tree/main/auth).
-
-#### Prueba
-
-Las funciones de contrato que usan `require_auth()` para autorización pueden probarse con `cargo test` simulando la autorización. Nuevamente, usamos el ejemplo de autenticación en el [repositorio de ejemplos de Soroban](https://github.com/stellar/soroban-examples/tree/main/auth) para ilustrar cómo probar la autorización.
-
-Primero, indicamos al entorno que simule todas las autorizaciones y permita que todas las llamadas a `require_auth()` tengan éxito usando `env.mock_all_auths()`. Después, generamos un usuario con `Address::generate(&env)` e insertamos ese usuario como parámetro en la función `increment()` del contrato, junto con el parámetro de valor. La prueba tiene dos afirmaciones: la primera invoca `increment()` con el usuario generado y el valor como parámetros, luego verifica si el valor devuelto se incrementó como se esperaba.
-
-La segunda prueba verifica si ocurrió la autorización esperada y que solo ocurrió la autorización esperada.
-
-```rust
-#[test]
-fn test() {
-   let env = Env::default();
-   let contract_id = env.register(IncrementContract, {});
-   let client = IncrementContractClient::new(&env, &contract_id);
-
-   env.mock_all_auths();
-   let user = Address::generate(&env);
-   let value = 10;
-
-   assert_eq!(client.increment(&user, &value), 10);
-
-   let expected_auth = AuthorizedInvocation {
-      function: AuthorizedFunction::Contract((
-         contract_id.clone(),
-         symbol_short!("increment"),
-         (user.clone(), value.clone()).into_val(&env),
-      )),
-      sub_invocations: std::vec![]
-   };
-
-   assert_eq!(env.auths(), std::vec![(user.clone(), expected_auth)]);
-}
-```
-
-Antes de realizar la prueba de autorización, podemos ejecutar la prueba:
-
-```rust
-cargo test
-```
-
-Deberías ver la siguiente salida:
-
-```rust
-running 1 test
-test test::test ... ok
-```
-
-**Probar la autorización**
-
-Al probar invocaciones de contratos autorizadas, verificamos los detalles de la autorización examinando `env.auths()`. Contendrá los detalles de todas las autorizaciones que ocurrieron, así que al comparar el contenido de `env.auths()` con lo que esperamos, podemos verificar si la autorización fue exitosa. Y tan importante como eso, dado que `env.auths()` contiene detalles de todas las autorizaciones durante la invocación del contrato, probar contra lo esperado también asegura que no hubo autorizaciones inesperadas.
-
-El contenido esperado de `env.auths()` se ve así:
-
-```rust
-[(
-  Contract(CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFCT4),
-  AuthorizedInvocation {
-    function: Contract((
-      Contract(CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD2KM),
-      Symbol(increment),
-      Vec(Ok(Address(obj#75)))
-    )),
-    sub_invocations: []
-  }
-)]
-```
-
-El contenido de env.auths() es un arreglo con la dirección de un usuario autorizado y los detalles asociados de la invocación del contrato.
-
-### `require_auth_for_args()`
-
-El método `require_auth_for_args()` te permite especificar explícitamente los argumentos de llamada al contrato que quieres autorizar, mientras que `require_auth()` pasa automáticamente todos los argumentos de llamada al contrato en la carga útil de autorización.
-
-Usemos el mismo ejemplo que en la sección de `require_auth()`; la única diferencia es que explicitamos que queremos autorizar el argumento `value`.
-
-```rust
-   pub fn increment(env: Env, user: Address, value: u32) -> u32 {
-      user.require_auth_for_args((value.clone(),).into_val(&env));
-
-      let mut count: u32 = env.storage().instance().get(&user).unwrap_or(0);
-      count += value.clone();
-      env.storage().persistent().set(&user, &count);
-
-      count
-   }
-```
-
-`require_auth_for_args()` se llama sobre el `user`. En este caso, autorizamos el argumento `value`, y como en el ejemplo de `require_auth()`, la dirección del usuario se usa como clave en el almacenamiento clave-valor. El argumento `value` es el valor por el cual se incrementa el `count` actual cuando se llama la función. La función devuelve el valor actual del contador.
-
-Ejecuta el siguiente comando para invocar la función del contrato con la dirección del usuario para su autorización:
-
-```rust
-stellar contract invoke \
-  --id CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN \
-  --source-account alice \
-  --network testnet \
-  -- \
-  increment \
-  --user SDWDUC7IIZPRIDUZIK44UHUD2KOG6A5XWUGVZBQG2RM3J2L5DSOROBAN \
-  --value 10
-```
-
-Debería aparecer la siguiente salida:
-
-```rust
-10
-```
-
-Si la autorización falla, la función no llegará a la línea de retorno del código.
-
-#### Prueba
-
-Las funciones del contrato que usan `require_auth_for_args()` para autorización pueden probarse con `cargo test` simulando la autorización. La prueba es muy similar a la usada en la sección `require_auth()`, donde la prueba se realiza en dos partes.
-
-Primero se realiza una prueba de la función del contrato, donde se simula la autorización, seguida de una prueba de la autorización en sí.
-
-```rust
-#[test]
-fn test() {
-   let env = Env::default();
-   let contract_id = env.register(IncrementContract, {});
-   let client = IncrementContractClient::new(&env, &contract_id);
-
-   env.mock_all_auths();
-   let user = Address::generate(&env);
-   let value = 10;
-
-   assert_eq!(client.increment(&user, &value), 10);
-
-   let expected_auth = AuthorizedInvocation {
-      function: AuthorizedFunction::Contract((
-         contract_id.clone(),
-         symbol_short!("increment"),
-         (user.clone(), value.clone()).into_val(&env),
-      )),
-      sub_invocations: std::vec![]
-   };
-
-   assert_eq!(env.auths(), std::vec![(user.clone(), expected_auth)]);
-}
-```
-
-De manera similar a cómo se prueba la autorización en la sección `require_auth()`, verificamos si la autorización funciona como se espera comparando el contenido de env.auths() con los detalles esperados de autorización.
-
-El contenido esperado de `env.auths()` se ve así:
-
-```rust
-[(
-  Contract(CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFCT4),
-  AuthorizedInvocation {
-    function: Contract((
-      Contract(CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD2KM),
-      Symbol(increment),
-      Vec(Ok(String(obj#43), Ok(I32(10)))
-    )),
-    sub_invocations: []
-  }
-)]
-```
-
-El contenido de `env.auths()` es un arreglo con la dirección de un usuario autorizado y los detalles asociados de la invocación del contrato.
-
-Ahora ejecuta la prueba:
-
-```rust
-cargo test
-```
-
-Deberías ver la siguiente salida:
-
-```rust
-running 1 test
-test test::test ... ok
-```
-
-## 2. Autorización entre contratos
-
-Los contratos inteligentes pueden invocar funciones en otros contratos (llamadas entre contratos). Estas llamadas directas están implícitamente autorizadas por el invocador y no necesitan ser autorizadas. Sin embargo, la función del contrato invocada puede requerir autorización de un usuario distinto del contrato mismo. Un ejemplo podría ser una función de transferencia, donde un usuario externo debe autorizar la transferencia al contrato actual.
-
-Para ilustrar cómo agregar autorización a una simple invocación entre contratos, usamos el [contrato de ejemplo de Llamadas entre Contratos](../../smart-contracts/example-contracts/cross-contract-call.mdx), que consta de dos contratos separados: uno con una función de contrato para suma simple y otro que invoca al primero.
-
-### Contrato invocador
-
-El contrato invocador en el ejemplo mencionado crea un cliente para invocar la función `add()` en el contrato de suma. Supongamos que queremos que el contrato `add()` sea autorizado por un usuario. Entonces, necesitamos pasar el usuario a la función `add()` desde la función invocadora.
-
-Aunque la función invocadora puede no requerir autorización del usuario, la función `add()` entrará en pánico si encuentra una autorización no vinculada a la invocación raíz o principal del contrato. Por lo tanto, necesitamos usar `require_auth()` en el usuario dentro de la función invocadora.
-
-Así es como se ve la función:
-
-```rust
-#[contractimpl]
-impl ContractB {
-   pub fn add_with(env: Env, x: u32, y: u32, contract: Address, user: Address) -> u32 {
-       user.require_auth();
-
-       let client = contract_a::Client::new(&env, &contract);
-       client.add(&user, &x, &y)
-   }
-}
-```
-
-La función `add_with()` recibe cuatro parámetros. Los parámetros x e y son los dos números a sumar, el contrato es el ID del contrato que tiene la función `add()`, y el usuario es quien autorizará la ejecución de `add()`.
-
-### Contrato de suma
-
-La función del contrato de suma es muy sencilla. En su forma original en el contrato ejemplo, simplemente recibe los números a sumar (x e y). Aquí solo necesitamos añadir la dirección `user` como parámetro y luego llamar a `require_auth()` sobre el usuario para autorizar la invocación.
-
-```rust
-   pub fn add(user: Address, x: u32, y: u32) -> u32 {
-       user.require_auth();
-       x.checked_add(y).expect("no overflow")
-   }
-```
-
-### Autorización del invocador
-
-En la función `add_with()` anterior, se pasa un usuario como argumento y el usuario es autorizado en la función invocada `add()`. Supongamos que no necesitamos autorización de un usuario externo para la invocación, sino que queremos permitir que el invocador autorice la llamada. Esto se puede hacer pasando la dirección del invocador como usuario, así:
-
-```rust
-#[contractimpl]
-impl ContractB {
-   pub fn add_with(env: Env, x: u32, y: u32, contract: Address, user: Address) -> u32 {
-      user.require_auth();
-
-      let current_contract_address = env.current_contract_address();
-      let client = contract_a::Client::new(&env, &contract);
-      client.add(&current_contract_address, &x, &y)
-   }
-}
-```
-
-Usando `env.current_contract_address()`, podemos obtener la dirección del invocador y pasarla a la función `add()`.
-
-## 3. Autorización de cuenta de contrato
-
-Las cuentas de contrato son contratos que implementan una función reservada especial para validar firmas proporcionadas externamente dentro del contexto de autorización respectivo. Estas cuentas son esencialmente contratos regulares, con una capacidad añadida para verificar la autenticación proporcionada externamente.
-
-### `__check_auth()`
-
-Un contrato que implementa la interfaz `CustomAccountInterface` para autorizar llamadas se convierte en una cuenta de contrato. La interfaz contiene una única función llamada `__check_auth()`. La función es reservada y la invoca automáticamente el Host cuando un contrato autoriza una transacción. No puede ser llamada manualmente.
-
-La función `__check_auth()` puede ser invocada para un contrato dado si se cumplen dos condiciones. La primera condición es cuando se llaman a `require_auth()` o `require_auth_for_args()`. La segunda condición ocurre cuando un contrato de cuenta no provee autorización al invocador, por ejemplo, llamando a una función que requiere autorización directamente.
-
-#### Cómo funciona
-
-`__check_auth()` verifica las credenciales y la política para una dirección de cuenta cada vez que otro contrato invoca `require_auth`. Una implementación mínima, mostrada a continuación y documentada de principio a fin en el [ejemplo de Cuenta Simple](../../smart-contracts/example-contracts/simple-account.mdx), carga una keypair Ed25519 almacenada y verifica la firma del payload contra ella:
-
-```rust
-   pub fn __check_auth(
-      env: Env,
-      signature_payload: BytesN<32>,
-      signature: BytesN<64>,
-      _auth_context: Vec<Context>,
-   ) {
-      let public_key: BytesN<32> = env
-         .storage()
-         .instance()
-         .get::<_, BytesN<32>>(&DataKey::Owner)
-         .unwrap();
-
-      env.crypto().ed25519_verify(&public_key, &signature_payload.into(), &signature);
-   }
-```
-
-Las cuentas más avanzadas se basan en la misma estructura: el [ejemplo de Cuenta Compleja](../../smart-contracts/example-contracts/complex-account.mdx) añade múltiples firmantes, pesos de firmas y límites de gasto aplicados mediante la navegación del `auth_context`.
-
-#### Lógica de autorización
-
-Puedes personalizar `__check_auth()` para aplicar las reglas que la cuenta requiera. Las verificaciones comunes incluyen comprobar que estén todos los firmantes necesarios, limitar qué subinvocaciones entre contratos están permitidas o aplicar límites de gasto. Consulta los ejemplos de Cuenta Simple y Compleja para implementaciones completas.
-
-### Cómo probar
-
-Como se muestra en ejemplos anteriores, la autorización se puede simular en pruebas añadiendo `env.mock_all_auths()`. Sin embargo, `mock_all_auths` omite `__check_auth()`, por lo que aún necesitas cobertura directa de la lógica de la cuenta. La forma recomendada es llamar a `env.try_invoke_contract_check_auth`, que emula el host e introduce un payload, firma(s) y contexto de autorización en tu cuenta. Un patrón típico es:
-
-```rust
-#[test]
-fn test_account() {
-   let env = Env::default();
-   let signer = generate_keypair();
-   let payload = BytesN::random(&env);
-
-   ...
-
-   account_contract.init(&signer.public.to_bytes().into_val(&env));
-
-   env.try_invoke_contract_check_auth::<Error>(
-      &account_contract.address,
-      &payload,
-      sign(&env, &signer, &payload),
-      &vec![&env],
-   )
-   .unwrap();
-}
-```
-
-Ese fragmento destaca las entradas clave: dirección del contrato, payload, firma y árbol de autorización. Para las pruebas completas, consulta el [ejemplo de Cuenta Simple](../../smart-contracts/example-contracts/simple-account.mdx); la documentación de Cuenta Compleja incluye cobertura de multisig y políticas.
-
-#### `set_auths()`
-
-:::note
-
-`set_auths()` puede no ser relevante para la mayoría de desarrolladores.
-
-:::
-
-Otro método es usar `set_auths()`, que llamará a `__check_auth()` cuando se ejecute la función del contrato, similar a cómo el host llama a `__check_auth()` en Testnet o Mainnet. Este método es más complejo y ofrece un control de nivel inferior sobre el proceso de autorización en pruebas.
-
-Para mostrar cómo usar `set_auths()` para probar la autorización, usaremos una función del contrato muy simple `fn1()` y una función `__check_auth()` muy sencilla. Esta simplemente llama a `require_auth()` y devuelve un entero. `__check_auth()` pasará sin hacer ninguna verificación. El ejemplo se basa en los casos de prueba de autenticación del [SDK de Soroban](https://github.com/stellar/rs-soroban-sdk/blob/35ff7aaecedd38056a131843a7a657b1ddc9e684/tests/auth/src/lib.rs).
-
-```rust
-   #[contract]
-   pub struct ContractA;
-
-   #[contractimpl]
-   impl ContractA {
-      pub fn fn1(a: Address) -> u64 {
-         a.require_auth();
-         2
-      }
-
-      #[allow(non_snake_case)]
-      pub fn __check_auth(
-         _signature_payload: Val,
-         _signatures: Val,
-         _auth_context: Vec<Context>,
-      ) {}
-   }
-```
-
-Primero, se crea una instancia del cliente y se obtienen el ID del contrato y la dirección registrando el contrato. Luego se llama a la función `fn1()` usando el cliente, se establecen los detalles de autorización y finalmente se compara el valor devuelto con el esperado usando `assert_eq!()`.
-
-```rust
-   #[test]
-   fn test_with_real_contract_auth_approve() {
-      let e = Env::default();
-      let contract_id = e.register(ContractA, ());
-      let client = ContractAClient::new(&e, &contract_id);
-
-      let a = e.register(ContractA, ());
-      let a_xdr: ScAddress = (&a).try_into().unwrap();
-
-      let r = client
-         .set_auths(&[SorobanAuthorizationEntry {
-            credentials: SorobanCredentials::Address(
-               SorobanAddressCredentials {
-                  address: a_xdr.clone(),
-                  nonce: 123,
-                  signature_expiration_ledger: 100,
-                  signature: ScVal::Void,
-               }
-            ),
-            root_invocation: SorobanAuthorizedInvocation {
-              function: SorobanAuthorizedFunction::ContractFn(
-                 InvokeContractArgs {
-                    contract_address: contract_id
-                       .clone()
-                       .try_into()
-                       .unwrap(),
-                    function_name: StringM::try_from("fn1")
-                       .unwrap().into(),
-                    args: std::vec![ScVal::Address(
-                       a_xdr.clone())]
-                          .try_into().unwrap(),
-                 }
-              ),
-              sub_invocations: VecM::default(),
-            },
-         }])
-        .fn1(&a);
-
-      assert_eq!(r, 2);
-   }
-```
-
-De forma similar a cómo el host ejecuta la autorización en Testnet y Mainnet, el método `set_auths()` también usa una lista de entradas `SorobanAuthorizationEntry` para verificar la autorización durante la ejecución de la función del contrato.
-
-Una `SorobanAuthorizationEntry` contiene credenciales de autorización y detalles de la invocación del contrato. La parte de credenciales especifica la dirección del contrato de la función `__check_auth()` y los datos relevantes de autorización. La parte de invocación raíz especifica el ID del contrato, el nombre de la función que se prueba, y sus argumentos.
-
-Para obtener más información sobre los detalles de autorización proporcionados en `set_auths()`, consulta la documentación de [Transacciones Stellar](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx).
-
-Probar usando `set_auths()` es más complejo que usar `try_invoke_contract_check_auth`, pero permite escenarios de prueba más avanzados. Si se requiere probar casos avanzados, como pruebas de bordes específicas de autorización, `set_auths()` puede ser una buena opción. De lo contrario, generalmente se recomienda el método `try_invoke_contract_check_auth` para pruebas.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/README.mdx
deleted file mode 100644
index 90d5258b36..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Fundamentos de Stellar
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 80
----
-
-Aprende cómo realizar acciones básicas en la red Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/_category_.json
deleted file mode 100644
index 9e90632aac..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/automate-reset-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/automate-reset-data.mdx
deleted file mode 100644
index 6c0ca95cd8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/automate-reset-data.mdx
+++ /dev/null
@@ -1,373 +0,0 @@
----
-title: Automatizar los datos de restablecimiento de Testnet y Futurenet
-description: Aprende a automatizar los datos de restablecimiento de Testnet y Futurenet en Stellar
----
-
-<head>
-  <title>{`Automatizar los datos de restablecimiento de Testnet y Futurenet en Stellar`}</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Automatizar los datos de restablecimiento de Testnet y Futurenet en Stellar"
-  />
-  <meta
-    property="og:description"
-    content="Automatizar los datos de restablecimiento de Testnet y Futurenet en Stellar"
-  />
-</head>
-
-## Resumen
-
-Stellar opera dos entornos de prueba principales: el [Testnet y el Futurenet](../../../networks/README.mdx). Estas redes permiten a los desarrolladores experimentar con las características de Stellar sin arriesgar activos reales. Periódicamente, estas redes se restablecen para asegurarse de que permanezcan limpias y manejables.
-
-## ¿Qué es el restablecimiento de Testnet y Futurenet?
-
-Testnet y Futurenet se restablecen periódicamente al ledger génesis para deshacerse del desorden en la red, eliminar el spam, reducir el tiempo necesario para actualizarse al último ledger y ayudar a mantener el sistema. Estos restablecimientos ocurren aproximadamente cada tres meses. Los restablecimientos eliminan todas las entradas del ledger (cuentas, líneas de confianza, ofertas, datos de contratos inteligentes, etc.), transacciones y datos históricos de Stellar Core, Horizon y el Stellar RPC, por lo que los desarrolladores no deben confiar en la persistencia de las cuentas o el estado de los saldos al usar Testnet o Futurenet.
-
-Puedes consultar las fechas actuales de reinicio [aquí](../../../networks/README.mdx#testnet-and-futurenet-data-reset).
-
-## Por qué los restablecimientos son importantes
-
-1. **Limpieza:** Los restablecimientos regulares garantizan que tanto Testnet como Futurenet proporcionen un entorno limpio para las pruebas. Esto ayuda a evitar complicaciones derivadas de datos o configuraciones antiguas.
-2. **Rendimiento:** Con el tiempo, los entornos de prueba pueden acumular muchos datos, lo que puede ralentizar el rendimiento. Los restablecimientos ayudan a mantener un rendimiento óptimo.
-3. **Actualizaciones de protocolo:** Introducir nuevas características o cambios en el protocolo a menudo requiere un restablecimiento para garantizar la compatibilidad y la estabilidad.
-4. **Ciclos de desarrollo:** Alinear con los ciclos de desarrollo permite a los desarrolladores planear sus fases de prueba y garantiza que tengan un entorno confiable para su trabajo.
-
-## Automatización de datos en Testnet y Futurenet
-
-Automatizar el estado de la blockchain en Testnet y Futurenet de Stellar puede optimizar los flujos de trabajo de desarrollo, asegurando que puedas probar y validar tus aplicaciones de manera consistente en estos entornos.
-
-### Análisis de código
-
-### Requisitos previos:
-
-- [Node.js](https://nodejs.org/en) y `npm` instalados.
-- Stellar SDK para [JavaScript](https://www.npmjs.com/package/@stellar/stellar-sdk) y `fs` instalados
-- Una comprensión de la función de sondeo de transacciones rudimentarias con soporte para reintentos `submitTx` que describimos en [otra guía](../transactions/submit-transaction-wait-js.mdx)
-
-### Código
-
-```javascript
-import {
-  Networks,
-  Keypair,
-  TransactionBuilder,
-  Operation,
-  Address,
-  StrKey,
-  Contract,
-  LiquidityPoolAsset,
-  LiquidityPoolFeeV18,
-  BASE_FEE,
-} from "@stellar/stellar-sdk";
-import { Server, Api } from "@stellar/stellar-sdk/rpc";
-import fs from "fs";
-
-// const networkRPC = "USE EITHER FUTERNET OR TESTNET RPC"
-const networkRPC = "https://soroban-testnet.stellar.org";
-// Example
-// FOR FUTERENET - https://rpc-futurenet.stellar.org
-// FOR TESTNET - https://soroban-testnet.stellar.org
-const server = new Server(networkRPC);
-
-// const networkURL = "USE EITHER FUTERNET OR TESTNET URL"
-const networkURL = "https://friendbot.stellar.org";
-// Example
-// FOR FUTURENET - https://friendbot-futurenet.stellar.org
-// FOR TESTNET - https://friendbot.stellar.org
-
-const networkPassphrase = Networks.TESTNET; // or Networks.FUTURENET, PUBLIC
-
-// Create an Account
-async function createAccount(networkURL, SecretKey) {
-  if (!SecretKey) {
-    try {
-      // Generate a keypair
-      const pair = Keypair.random();
-      // Fund the new account using Friendbot
-      const response = await fetch(
-        `${networkURL}?addr=${encodeURIComponent(pair.publicKey())}`,
-      );
-      const responseJSON = await response.json();
-      console.log("Account created:", responseJSON);
-
-      return pair;
-    } catch (error) {
-      console.error("Error creating account:", error);
-    }
-  } else {
-    try {
-      const pair = Keypair.fromSecret(SecretKey);
-      console.log("Account Restored:", pair);
-      return pair;
-    } catch (error) {
-      console.error("Error restoring account:", error);
-    }
-  }
-}
-
-// Issues an Asset
-async function issueAsset(issuerKeys, receivingKeys, customAsset) {
-  try {
-    // First, the receiving account must trust the asset
-    const receiver = await server.getAccount(receivingKeys.publicKey());
-    let transaction = new TransactionBuilder(receiver, {
-      fee: BASE_FEE,
-      networkPassphrase,
-    })
-      .addOperation(
-        Operation.changeTrust({
-          asset: customAsset,
-          limit: "100000",
-        }),
-      )
-      // setTimeout is required for a transaction
-      .setTimeout(100)
-      .build();
-    transaction.sign(receivingKeys);
-    const status = await submitTx(transaction);
-    if (status !== Api.GetTransactionStatus.SUCCESS) {
-      throw status;
-    }
-    console.log(`Receiver Trusting ${customAsset.code} Asset......`);
-
-    // Second, the issuing account actually sends a payment using the asset
-    const issuer = await server.getAccount(issuerKeys.publicKey());
-    transaction = new TransactionBuilder(issuer, {
-      fee: BASE_FEE,
-      networkPassphrase,
-    })
-      .addOperation(
-        Operation.payment({
-          destination: receivingKeys.publicKey(),
-          asset: customAsset,
-          amount: "1000", // change to desired amount you want to pay
-        }),
-      )
-      // setTimeout is required for a transaction
-      .setTimeout(100)
-      .build();
-    transaction.sign(issuerKeys);
-    const status = await submitTx(transaction);
-    if (status !== Api.GetTransactionStatus.SUCCESS) {
-      throw status;
-    }
-    console.log(
-      `Issuer Payment using ${
-        customAsset.code
-      } to  ${receivingKeys.publicKey()}`,
-    );
-  } catch (e) {
-    console.error("An error occurred while issuing assets:", e);
-  }
-}
-
-//Create Liquidity Pool
-async function createLiquidityPool(accountKeypair, nativeAsset, customAsset) {
-  try {
-    const account = await server.getAccount(accountKeypair.publicKey());
-
-    // Create the liquidity pool
-    const poolIdAsset = new LiquidityPoolAsset(
-      nativeAsset,
-      customAsset,
-      LiquidityPoolFeeV18,
-    );
-    const poolId = poolIdAsset.toString().split(":")[1]; // To Get the Pool ID
-
-    const transaction = new TransactionBuilder(account, {
-      fee: BASE_FEE,
-      networkPassphrase: networkPassPhrase,
-    })
-      .addOperation(
-        Operation.changeTrust({
-          asset: poolIdAsset,
-          limit: "100000", // Set an appropriate limit
-        }),
-      )
-      .addOperation(
-        Operation.liquidityPoolDeposit({
-          liquidityPoolId: poolId,
-          maxAmountA: "1000", // Amount of asset A to deposit
-          maxAmountB: "500", // Amount of asset B to deposit
-          minPrice: "0.5", // Minimum price ratio
-          maxPrice: "2.0", // Maximum price ratio
-        }),
-      )
-      .setTimeout(30)
-      .build();
-    transaction.sign(accountKeypair);
-    const status = await submitTx(transaction);
-    if (status !== Api.GetTransactionStatus.SUCCESS) {
-      throw status;
-    }
-    console.log(
-      `Creating Liquidity Pool for ${nativeAsset.code} and ${customAsset.code}`,
-    );
-  } catch (error) {
-    console.error("Error creating liquidity pool:", error);
-    throw error;
-  }
-}
-//Deploy and Invoke Contract
-async function deployAndInvokeContract(deployer, contractWasmFilePath) {
-  try {
-    // Step 1: Upload WASM
-    const bytecode = fs.readFileSync(contractWasmFilePath);
-    const account = await server.getAccount(deployer.publicKey());
-
-    const uploadTransaction = new TransactionBuilder(account, {
-      fee: BASE_FEE,
-      networkPassphrase,
-    })
-      .addOperation(Operation.uploadContractWasm({ wasm: bytecode }))
-      .setTimeout(30)
-      .build();
-
-    const uploadTx = await server.prepareTransaction(uploadTransaction);
-    uploadTx.sign(deployer);
-
-    console.log("Submitting WASM upload transaction...");
-    let status = await submitTx(uploadTx);
-    if (status !== Api.GetTransactionStatus.SUCCESS) {
-      throw status;
-    }
-    const wasmHash = status.returnValue.bytes();
-
-    const deployerAddress = new Address(deployer.publicKey());
-
-    // Deploy the Contract
-    const createContractTransaction = new TransactionBuilder(account, {
-      fee: BASE_FEE,
-      networkPassphrase,
-    })
-      .addOperation(
-        Operation.createCustomContract({
-          address: deployerAddress,
-          wasmHash,
-        }),
-      )
-      .setTimeout(30)
-      .build();
-
-    const createContractTx = await server.prepareTransaction(
-      createContractTransaction,
-    );
-    createContractTx.sign(deployer);
-    status = await submitTx(createContractTx);
-    if (status !== Api.GetTransactionStatus.SUCCESS) {
-      throw status;
-    }
-    console.log(`Contract Deployed...`);
-
-    const contractAddr = Address.fromScAddress(
-      returnContractResponse.returnValue.address(),
-    );
-    const contractId = contractAddr.toString();
-    const contract = new Contract(contractId);
-
-    // Invoke Contract
-    const invokeContractTransaction = new TransactionBuilder(account, {
-      fee: BASE_FEE,
-      networkPassphrase,
-    })
-      .addOperation(
-        contract.call("hello", nativeToScVal("World", { type: "symbol" })),
-      )
-      .setTimeout(30)
-      .build();
-
-    const invokeContractTx = await server.prepareTransaction(
-      invokeContractTransaction,
-    );
-    invokeContractTx.sign(deployer);
-    const returnInvokeContractResponse = await submitTx(invokeContractTx);
-    console.log(`Invoke Contract.`);
-
-    const returnValues = scValToNative(
-      returnInvokeContractResponse.returnValue,
-    ).filter(Boolean);
-
-    return { contractId, returnValues };
-  } catch (error) {
-    console.error("Error in contract deployment and invocation:", error);
-    throw error;
-  }
-}
-
-async function automateSetup() {
-  try {
-    //Check Network Status
-    console.log("Checking network health...");
-    const health = await server.getHealth();
-    console.log("Network health:", health);
-
-    // Flexible Account Configuration
-    const secretkey =
-      "SBGGNMUPVF2SDN4KZOJQFVFX7VDR4Q4NK3FMEFRQC64D3UBMFELKF5GC"; // This is an example of a user's secret key
-
-    const accountOne = await createAccount(networkURL, secretkey);
-    const accountTwo = await createAccount(networkURL);
-
-    console.log("Issuing an Asset...");
-    // Issue assets to these accounts
-    const customAsset = new Asset("Boya", accountOne.publicKey());
-    await issueAsset(accountOne, accountTwo, customAsset);
-
-    // Create liquidity pool
-    console.log("Creating liquidity pool...");
-    const nativeAsset = Asset.native();
-    await createLiquidityPool(accountTwo, nativeAsset, customAsset);
-
-    // Deploy a contract
-    console.log("Deploying contract...");
-    // Ensure you have the contract Wasm file compiled and saved in the specified path.
-    // Adjust this path as necessary
-    const contractWasmFilePath =
-      "./target/wasm32v1-none/release/hello_world.wasm";
-    const ContractData = await deployAndInvokeContract(
-      accountOne,
-      contractWasmFilePath,
-    );
-
-    console.log("Contract ID:", ContractData.contractId);
-    console.log("Return Values:", ContractData.returnValues.join(", "));
-  } catch (error) {
-    console.error("An error occurred:", error);
-  }
-}
-
-automateSetup();
-```
-
-El código define varias funciones asíncronas:
-
-1. `crearCuenta(networkURL)`:
-
-Genera un nuevo keypair de Stellar (claves pública y secreta). Usa FriendBot para financiar la nueva cuenta en la red de pruebas. Retorna el keypair creado.
-
-2. `emitirActivos(clavesEmisor, clavesRecepcion, activoPersonalizado)`:
-
-Configura una línea de confianza para que la cuenta receptora acepte el activo personalizado, emite el activo personalizado desde la cuenta emisora a la cuenta receptora.
-
-3. `crearGrupoDeLiquidez(claveParDeCuentas, activoNativo, activoPersonalizado)`:
-
-Crea un activo de fondo de liquidez, establece una línea de confianza para el fondo y deposita liquidez inicial en el fondo.
-
-4. `desplegarEInvocarContrato(desplegador, rutaArchivoWasmDelContrato)`:
-
-Sube el código WebAssembly (Wasm) del contrato, crea y despliega el contrato en la red, invoca la función del contrato y devuelve el ID del contrato y los valores de retorno de la función
-
-5. `automatizarConfiguracion()`:
-
-Inicializa la conexión del servidor Stellar, crea dos cuentas, emite un activo personalizado, crea un fondo de liquidez, despliega un contrato inteligente y retorna el ID del contrato y los valores de la función.
-
-**Funciones auxiliares**
-
-`sleep(ms)`: Una función utilitaria para introducir retrasos en operaciones asíncronas.
-
-`submitTx(tx)`: una función de envío de transacciones con soporte para reintentos `submitTx` descrita en [otra guía](../transactions/submit-transaction-wait-js.mdx)
-
-### Conclusión
-
-Automatizar la configuración de datos en Testnet y Futurenet de Stellar puede mejorar significativamente tu flujo de trabajo de desarrollo, asegurando que puedas volver a las pruebas rápidamente después de un restablecimiento de la red. Siguiendo los pasos anteriores y utilizando los ejemplos de código proporcionados, puedes optimizar tus procesos y mantener la consistencia a través de los restablecimientos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/classic-transition.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/classic-transition.mdx
deleted file mode 100644
index 6aa4aba0fb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/classic-transition.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Añadir soporte para contratos inteligentes
-sidebar_position: 50
-description: Consideraciones para integrar con los contratos inteligentes de Stellar específicamente para billeteras y exchanges
----
-
-Stellar recientemente [actualizó su protocolo](https://stellar.org/blog/developers/protocol-20-preparing-smart-contracts-to-stellar) para admitir contratos inteligentes, añadiendo una nueva forma de interactuar con la red. Este documento de una página destaca las consideraciones clave para integrar con los contratos inteligentes de Stellar específicamente para billeteras y exchanges que ya admiten las operaciones 'clásicas' de Stellar. Esboza rápidamente qué cambios esperar, proporciona enlaces a documentación detallada y es un punto de partida para adaptar los procesos existentes de Stellar Classic al nuevo entorno de contratos inteligentes.
-
-## 1. Infraestructura
-
-### Transición de Horizon a RPC
-
-Para admitir correctamente los contratos inteligentes de Stellar, debes usar [Stellar RPC](../../../data/apis/rpc). Más específicamente, necesitas RPC para simular transacciones que ejecutan contratos inteligentes, como se describe en la sección "Simulando Transacciones", y proporciona una [API](../../../data/apis/rpc/api-reference) conveniente para consumir eventos de contrato. Ambas características no están disponibles en Horizon.
-
-### Ejecutar tu propio RPC vs. Aprovechar proveedores de terceros
-
-Puedes configurar un entorno RPC al alojar tu propio nodo o utilizando un proveedor de terceros. Para obtener orientación sobre cómo alojar tu propia instancia, incluida una configuración basada en Docker, consulta la [Guía Administrativa](../../../data/apis/rpc/admin-guide). Alternativamente, una lista de proveedores de confianza está disponible en la [documentación de proveedores RPC del ecosistema](../../../data/apis/rpc/providers).
-
-## 2. Ingesta de Datos
-
-### Ingestar Eventos de Contratos Inteligentes
-
-Horizon ofrece un endpoint de efectos que describe los cambios de estado ejecutados por operaciones clásicas. De manera similar, los contratos emiten [eventos](../../../learn/fundamentals/stellar-data-structures/events.mdx) que describen cambios en su estado, los cuales pueden ser consultados mediante la API de RPC. Las soluciones off-chain pueden [monitorear e ingresar estos eventos](../../../build/guides/events/ingest.mdx) (para transferencias de tokens o actualizaciones de protocolo) y mantenerse en sincronía con los datos on-chain. Cada evento está definido por el contrato y está sujeto a los estándares aplicados a la implementación. Dependiendo de los requisitos para la retención, una solución podría tener que manejar la ingestión directamente o usar un [servicio de terceros](../../../data/indexers/README.mdx) para un historial a largo plazo.
-
-### Simulando Transacción
-
-Mientras que los eventos deben usarse para monitorear cambios en el estado de un contrato, los clientes también pueden necesitar determinar el estado actual de un contrato. [La simulación](../../../build/guides/transactions/simulateTransaction-Deep-Dive.mdx) permite a los clientes ejecutar invocaciones de contratos sin incurrir en tarifas o finalizar cambios, lo que la convierte en un enfoque ideal para obtener el estado actual de los contratos. Por ejemplo, los clientes pueden llamar a la función de saldo en un contrato de token compatible con [SEP-0041](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md) para obtener el saldo actual de un usuario.
-
-## 3. Cambios en el Flujo de Trabajo de Transacciones
-
-### Construir Transacciones
-
-La construcción de transacciones implica especificar una llamada a una función de contrato en lugar de cualquiera de las operaciones integradas que Stellar ofrece. Al construir estas llamadas a contrato, es necesario especificar el ID del contrato relevante y los argumentos de función de acuerdo con la interfaz del contrato. Consulta más información en [Documentación para la interacción con contratos - Transacción Stellar](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx).
-
-Puedes seguir usando las bibliotecas o herramientas que ya conoces para ensamblar estas transacciones, [pero ten en cuenta los pasos adicionales requeridos para la invocación de contratos](../../../build/guides/transactions/invoke-contract-tx-sdk.mdx).
-
-### Simulando Transacción
-
-Las transacciones que ejecutan contratos inteligentes deben ser [simuladas](../../../build/guides/transactions/simulateTransaction-Deep-Dive.mdx) antes de enviarlas. Esto se debe a que la simulación no solo proporciona los resultados de la ejecución de transacciones; también ofrece información esencial como la [huella](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx#footprint) de lectura/escritura de la transacción y las [autorizaciones](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx#authorization) necesarias, y los clientes deben añadir esta información a la transacción antes de enviarla a la red para su ejecución.
-
-### Firmando & Entradas de Autenticación
-
-Los contratos inteligentes pueden definir su propia [lógica de autorización personalizada](../../../learn/fundamentals/contract-development/authorization.mdx), lo que significa que podrías necesitar [firmas adicionales para datos específicos de autorización](../../../learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx#authorization-data) para demostrar permiso en ciertas llamadas al contrato. Cada contrato puede tener sus propios requisitos, por lo que una buena práctica es [aprovechar las simulaciones de transacciones para identificar requisitos específicos de autorización de una transacción](../../../learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx#authorization).
-
-### Envío Asincrónico de Transacciones
-
-A diferencia de Horizon, [RPC solo pone en cola las transacciones para inclusión en lugar de esperar la confirmación final](../../../data/apis/rpc/api-reference/methods/sendTransaction). Por lo tanto, es necesario [consultar el estado de la transacción](../../../data/apis/rpc/api-reference/methods/getTransaction) para determinar si una transacción finalmente tiene éxito o falla. Este modelo asincrónico, así como otros desafíos comunes, se pueden ver en la [Documentación para el Desarrollo de Dapp - Errores Comunes](../../../build/guides/dapps/frontend-guide.mdx#7-common-pitfalls).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/create-account.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/create-account.mdx
deleted file mode 100644
index bf39b09499..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/create-account.mdx
+++ /dev/null
@@ -1,297 +0,0 @@
----
-title: "Crear una cuenta de Blockchain: Guía sobre keypairs, financiación y conceptos básicos de la cuenta"
-sidebar_position: 10
-sidebar_label: Crear una cuenta
-description: Sigue esta guía paso a paso para aprender los conceptos básicos de la cuenta y cómo crear una cuenta de Blockchain en Stellar, lo que implica crear un keypair y financiarlo.
----
-
-# Crear una cuenta
-
-import { CodeExample } from "@site/src/components/CodeExample";
-import { Alert } from "@site/src/components/Alert";
-
-_Before we get started with working with Stellar in code, consider going through the following examples using the [Stellar Lab](https://lab.stellar.org). _El laboratorio te permite crear cuentas, financiar cuentas en la red de prueba de Stellar, construir transacciones, ejecutar cualquier operación e inspeccionar respuestas de Horizon a través del Explorador de Endpoints._
-
-Las [cuentas](../../../learn/fundamentals/stellar-data-structures/accounts.mdx) son un bloque de construcción fundamental de Stellar: sostienen todos tus saldos, te permiten enviar y recibir pagos, y te dejan hacer ofertas para comprar y vender activos. Dado que prácticamente todo en Stellar está de alguna manera relacionado con una cuenta, lo primero que generalmente necesitas hacer cuando comienzas a desarrollar es crear una. Este tutorial para principiantes te mostrará cómo hacerlo.
-
-## Crear un Keypair
-
-Stellar utiliza criptografía de clave pública para garantizar que cada transacción sea segura: cada cuenta Stellar tiene un keypair que consiste en una **clave pública** y una **clave secreta**. La clave pública siempre es segura para compartir: otras personas la necesitan para identificar tu cuenta y verificar que autorizaste una transacción. Es como una dirección de correo electrónico. La clave secreta, sin embargo, es información privada que demuestra que eres el dueño —y te da acceso a— tu cuenta. Es como una contraseña, y nunca debes compartirla con nadie.
-
-Antes de crear una cuenta, necesitas generar tu propio keypair:
-
-<CodeExample>
-
-```js
-// create a completely new and unique pair of keys
-// see more about KeyPair objects: https://stellar.github.io/js-stellar-sdk/Keypair.html
-const pair = StellarSdk.Keypair.random();
-
-pair.secret();
-// SAV76USXIJOBMEQXPANUOQM6F5LIOTLPDIDVRJBFFE2MDJXG24TAPUU7
-pair.publicKey();
-// GCFXHS4GXL6BVUCXBWXGTITROWLVYXQKQLF4YH5O5JT3YZXCYPAFBJZB
-```
-
-```java
-// create a completely new and unique pair of keys.
-// see more about KeyPair objects: https://stellar.github.io/java-stellar-sdk/org/stellar/sdk/KeyPair.html
-import org.stellar.sdk.KeyPair;
-KeyPair pair = KeyPair.random();
-
-System.out.println(new String(pair.getSecretSeed()));
-// SAV76USXIJOBMEQXPANUOQM6F5LIOTLPDIDVRJBFFE2MDJXG24TAPUU7
-System.out.println(pair.getAccountId());
-// GCFXHS4GXL6BVUCXBWXGTITROWLVYXQKQLF4YH5O5JT3YZXCYPAFBJZB
-```
-
-```go
-package main
-
-import (
-	"log"
-
-	"github.com/stellar/go/keypair"
-)
-
-func main() {
-	pair, err := keypair.Random()
-	if err != nil {
-		log.Fatal(err)
-	}
-
-	log.Println(pair.Seed())
-	// SAV76USXIJOBMEQXPANUOQM6F5LIOTLPDIDVRJBFFE2MDJXG24TAPUU7
-	log.Println(pair.Address())
-	// GCFXHS4GXL6BVUCXBWXGTITROWLVYXQKQLF4YH5O5JT3YZXCYPAFBJZB
-}
-```
-
-```python
-# stellar-sdk >= 2.0.0 required
-# create a completely new and unique pair of keys
-# see more about KeyPair objects: https://stellar-sdk.readthedocs.io/en/latest/api.html#keypair
-from stellar_sdk import Keypair
-
-pair = Keypair.random()
-print(f"Secret: {pair.secret}")
-# Secret: SCMDRX7A7OVRPAGXLUVRNIYTWBLCS54OV7UH2TF5URSG4B4JQMUADCYU
-print(f"Public Key: {pair.public_key}")
-# Public Key: GAG7SXULMNWCW6LX42JKZOZRA2JJXQT23LYY32OXA6XECUQG7RZTQJHO
-```
-
-</CodeExample>
-
-## Crear Cuenta
-
-Un keypair válido, sin embargo, no crea una cuenta: para evitar que las cuentas no utilizadas aumenten el ledger, Stellar requiere que las cuentas mantengan un [saldo mínimo](../../../learn/fundamentals/lumens.mdx#minimum-balance) de 1 XLM antes de que realmente existan. Hasta que no obtenga un poco de financiamiento, tu keypair no justifica espacio en el ledger.
-
-En la [red pública](../../../learn/fundamentals/networks.mdx), donde los usuarios reales realizan transacciones en vivo, tu siguiente paso sería adquirir XLM, lo que puedes hacer consultando nuestra [sección sobre lumens](https://stellar.org/learn/lumens). Because this tutorial runs on the [test network](../../../learn/fundamentals/networks.mdx), you can get 10,000 test XLM from Friendbot, which is a friendly account funding tool.
-
-Para hacerlo, envía a Friendbot la clave pública que creaste. Él creará y financiará una nueva cuenta usando esa clave pública como el ID de la cuenta.
-
-<CodeExample>
-
-```js
-// The SDK does not have tools for creating test accounts, so you'll have to
-// make your own HTTP request.
-
-// if you're trying this on Node, install the `node-fetch` library and
-// uncomment the next line:
-// const fetch = require('node-fetch');
-
-(async function main() {
-  try {
-    const response = await fetch(
-      `https://friendbot.stellar.org?addr=${encodeURIComponent(
-        pair.publicKey(),
-      )}`,
-    );
-    const responseJSON = await response.json();
-    console.log("SUCCESS! You have a new account :)\n", responseJSON);
-  } catch (e) {
-    console.error("ERROR!", e);
-  }
-  // After you've got your test lumens from friendbot, we can also use that account to create a new account on the ledger.
-  try {
-    const server = new StellarSdk.Horizon.Server(
-      "https://horizon-testnet.stellar.org",
-    );
-    var parentAccount = await server.loadAccount(pair.publicKey()); //make sure the parent account exists on ledger
-    var childAccount = StellarSdk.Keypair.random(); //generate a random account to create
-    //create a transacion object.
-    var createAccountTx = new StellarSdk.TransactionBuilder(parentAccount, {
-      fee: StellarSdk.BASE_FEE,
-      networkPassphrase: StellarSdk.Networks.TESTNET,
-    });
-    //add the create account operation to the createAccountTx transaction.
-    createAccountTx = await createAccountTx
-      .addOperation(
-        StellarSdk.Operation.createAccount({
-          destination: childAccount.publicKey(),
-          startingBalance: "5",
-        }),
-      )
-      .setTimeout(180)
-      .build();
-    //sign the transaction with the account that was created from friendbot.
-    await createAccountTx.sign(pair);
-    //submit the transaction
-    let txResponse = await server
-      .submitTransaction(createAccountTx)
-      // some simple error handling
-      .catch(function (error) {
-        console.log("there was an error");
-        console.log(error.response);
-        console.log(error.status);
-        console.log(error.extras);
-        return error;
-      });
-    console.log(txResponse);
-    console.log("Created the new account", childAccount.publicKey());
-  } catch (e) {
-    console.error("ERROR!", e);
-  }
-})();
-```
-
-```java
-// The SDK does not have tools for creating test accounts, so you'll have to
-// make your own HTTP request.
-import java.net.*;
-import java.io.*;
-import java.util.*;
-
-String friendbotUrl = String.format(
-  "https://friendbot.stellar.org/?addr=%s",
-  pair.getAccountId());
-InputStream response = new URL(friendbotUrl).openStream();
-String body = new Scanner(response, "UTF-8").useDelimiter("\\A").next();
-System.out.println("SUCCESS! You have a new account :)\n" + body);
-```
-
-```go
-package main
-
-import (
-	"net/http"
-	"io/ioutil"
-	"log"
-	"fmt"
-)
-
-func main() {
-	// pair is the pair that was generated from previous example, or create a pair based on
-	// existing keys.
-	address := pair.Address()
-	resp, err := http.Get("https://friendbot.stellar.org/?addr=" + address)
-	if err != nil {
-		log.Fatal(err)
-	}
-
-	defer resp.Body.Close()
-	body, err := ioutil.ReadAll(resp.Body)
-	if err != nil {
-		log.Fatal(err)
-	}
-	fmt.Println(string(body))
-}
-```
-
-```python
-# The SDK does not have tools for creating test accounts, so you'll have to
-# make your own HTTP request.
-
-# if you're trying this on Python, install the `requests` library.
-import requests
-
-public_key = "GD4NB2FLQAN5JO7PKPGZJMNBDYQXVSNVC7DEIZMOL5WSNSBLEBUTEF5Q"
-response = requests.get(f"https://friendbot.stellar.org?addr={public_key}")
-if response.status_code == 200:
-    print(f"SUCCESS! You have a new account :)\n{response.text}")
-else:
-    print(f"ERROR! Response: \n{response.text}")
-```
-
-</CodeExample>
-
-Ahora, para el último paso: obtener los detalles de la cuenta y comprobar su saldo. Las cuentas pueden tener múltiples saldos —uno para cada tipo de moneda que mantienen.
-
-<CodeExample>
-
-```js
-const server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-
-// the JS SDK uses promises for most actions, such as retrieving an account
-const account = await server.loadAccount(pair.publicKey());
-console.log("Balances for account: " + pair.publicKey());
-account.balances.forEach(function (balance) {
-  console.log("Type:", balance.asset_type, ", Balance:", balance.balance);
-});
-```
-
-```java
-import org.stellar.sdk.Server;
-import org.stellar.sdk.responses.AccountResponse;
-
-Server server = new Server("https://horizon-testnet.stellar.org");
-AccountResponse account = server.accounts().account(pair.getAccountId());
-System.out.println("Balances for account " + pair.getAccountId());
-for (AccountResponse.Balance balance : account.getBalances()) {
-  System.out.printf(
-    "Type: %s, Code: %s, Balance: %s%n",
-    balance.getAssetType(),
-    balance.getAssetCode(),
-    balance.getBalance()
-  );
-}
-```
-
-```go
-package main
-
-import (
-	"log"
-
-	"github.com/stellar/go/clients/horizonclient"
-)
-
-func main() {
-	// Replace this with the output from earlier, or use pair.Address()
-	address := "GCFXHS4GXL6BVUCXBWXGTITROWLVYXQKQLF4YH5O5JT3YZXCYPAFBJZB"
-
-	request := horizonclient.AccountRequest{AccountID: address}
-	account, err := horizonclient.DefaultTestNetClient.AccountDetail(request)
-	if err != nil {
-		log.Fatal(err)
-	}
-
-	log.Println("Balances for account:", address)
-
-	for _, balance := range account.Balances {
-		log.Println(balance)
-	}
-}
-```
-
-```python
-from stellar_sdk import Server
-
-server = Server("https://horizon-testnet.stellar.org")
-public_key = "GD4NB2FLQAN5JO7PKPGZJMNBDYQXVSNVC7DEIZMOL5WSNSBLEBUTEF5Q"
-account = server.accounts().account_id(public_key).call()
-for balance in account['balances']:
-    print(f"Type: {balance['asset_type']}, Balance: {balance['balance']}")
-```
-
-</CodeExample>
-
-Ahora que tienes una cuenta, puedes [comenzar a enviar y recibir pagos](send-and-receive-payments.mdx), o, si estás listo para concentrarte, puedes avanzar y [construir una billetera](../../apps/wallet/overview.mdx) o [emitir un activo de la red Stellar](../../../tokens/anatomy-of-an-asset.mdx).
-
-<Alert>
-
-En los ejemplos de código anteriores, se omitió la verificación de errores adecuada por brevedad. Sin embargo, siempre debes _validar tus resultados_, ya que hay muchas formas en que las solicitudes pueden fallar. Debes consultar la guía sobre [Manejo de Errores](../../../data/apis/horizon/api-reference/errors/error-handling.mdx) para obtener consejos sobre estrategias de gestión de errores.
-
-</Alert>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/follow-received-payments.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/follow-received-payments.mdx
deleted file mode 100644
index 2f02e96a25..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/follow-received-payments.mdx
+++ /dev/null
@@ -1,267 +0,0 @@
----
-title: Seguir pagos recibidos
-sidebar_position: 30
-description: Observa los pagos entrantes utilizando Horizon
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Este tutorial muestra lo fácil que es usar Horizon para observar los pagos entrantes en una [cuenta](../../../learn/fundamentals/stellar-data-structures/accounts.mdx) utilizando JavaScript y `EventSource`. Evitaremos usar [`js-stellar-sdk`](https://github.com/stellar/js-stellar-sdk), la biblioteca de ayuda de alto nivel, para mostrar que es posible que realices esta tarea por tu cuenta con cualquier lenguaje de programación que desees usar.
-
-Este tutorial asume que tú:
-
-- Tienes node.js instalado localmente en tu máquina.
-- Tienes curl instalado localmente en tu máquina.
-- Estás ejecutando en Linux, macOS o cualquier otro sistema que tenga acceso a un shell similar a bash.
-- Estás familiarizado con iniciar y ejecutar comandos en un terminal.
-
-En este tutorial aprenderemos:
-
-- Cómo crear una nueva cuenta.
-- Cómo financiar tu cuenta usando friendbot.
-- Cómo seguir los pagos a tu cuenta usando curl y EventSource.
-
-## Esqueleto del proyecto
-
-Comencemos construyendo el esqueleto de nuestro proyecto:
-
-<CodeExample>
-
-```bash
-$ mkdir follow_tutorial
-$ cd follow_tutorial
-$ npm install --save stellar-base
-$ npm install --save eventsource
-```
-
-</CodeExample>
-
-Esto debería haber creado un `package.json` en el directorio `follow_tutorial`. Puedes verificar que todo salió bien ejecutando el siguiente comando:
-
-<CodeExample>
-
-```bash
-$ node -e "require('stellar-base')"
-```
-
-</CodeExample>
-
-Todo fue exitoso si no se generó salida del comando anterior. Ahora escribamos un script para crear una nueva cuenta.
-
-## Creando una cuenta
-
-Crea un nuevo archivo llamado `make_account.js` y pega el siguiente texto en él:
-
-<CodeExample>
-
-```js
-var Keypair = require("stellar-base").Keypair;
-
-var newAccount = Keypair.random();
-
-console.log("New key pair created!");
-console.log("  Account ID: " + newAccount.publicKey());
-console.log("  Secret: " + newAccount.secret());
-```
-
-</CodeExample>
-
-Guarda el archivo y ejecútalo:
-
-<CodeExample>
-
-```bash
-$ node make_account.js
-New key pair created!
-  Account ID: GB7JFK56QXQ4DVJRNPDBXABNG3IVKIXWWJJRJICHRU22Z5R5PI65GAK3
-  Secret: SCU36VV2OYTUMDSSU4EIVX4UUHY3XC7N44VL4IJ26IOG6HVNC7DY5UJO
-$
-```
-
-</CodeExample>
-
-Antes de que nuestra cuenta pueda hacer nada, debe ser financiada. ¡De hecho, antes de que una cuenta se financie, no existe realmente!
-
-## Financiando tu cuenta
-
-La red de prueba de Stellar proporciona el Friendbot, una herramienta que los desarrolladores pueden usar para obtener testnet lumens para propósitos de prueba. Para financiar tu cuenta, simplemente ejecuta el siguiente comando curl:
-
-<CodeExample>
-
-```bash
-$ curl "https://friendbot.stellar.org/?addr=GB7JFK56QXQ4DVJRNPDBXABNG3IVKIXWWJJRJICHRU22Z5R5PI65GAK3"
-```
-
-</CodeExample>
-
-No olvides reemplazar el ID de cuenta anterior con el tuyo. Si la solicitud tiene éxito, deberías ver una respuesta como:
-
-<CodeExample>
-
-```json
-{
-  "hash": "ed9e96e136915103f5d8978cbb2036628e811f2c59c4c3d88534444cf504e360",
-  "result": "received",
-  "submission_result": "000000000000000a0000000000000001000000000000000000000000"
-}
-```
-
-</CodeExample>
-
-Después de unos segundos, la red Stellar llevará a cabo un consenso, cerrará el ledger y tu cuenta habrá sido creada. A continuación, escribiremos un comando que esté atento a los nuevos pagos a tu cuenta y de salida un mensaje en el terminal.
-
-## Siguiendo pagos usando `curl`
-
-Para seguir los nuevos pagos conectados a tu cuenta, simplemente necesitas enviar el encabezado `Accept: text/event-stream` al punto final de [/payments](../../../data/apis/horizon/api-reference/resources/operations/README.mdx).
-
-<CodeExample>
-
-```bash
-$ curl -H "Accept: text/event-stream" "https://horizon-testnet.stellar.org/accounts/GB7JFK56QXQ4DVJRNPDBXABNG3IVKIXWWJJRJICHRU22Z5R5PI65GAK3/payments"
-```
-
-</CodeExample>
-
-Como resultado, verás algo como:
-
-<CodeExample>
-
-```text
-retry: 1000
-event: open
-data: "hello"
-
-id: 713226564145153
-data: {"_links":{"effects":{"href":"/operations/713226564145153/effects/{?cursor,limit,order}","templated":true},
-       "precedes":{"href":"/operations?cursor=713226564145153\u0026order=asc"},
-       "self":{"href":"/operations/713226564145153"},
-       "succeeds":{"href":"/operations?cursor=713226564145153\u0026order=desc"},
-       "transactions":{"href":"/transactions/713226564145152"}},
-       "account":"GB7JFK56QXQ4DVJRNPDBXABNG3IVKIXWWJJRJICHRU22Z5R5PI65GAK3",
-       "funder":"GBS43BF24ENNS3KPACUZVKK2VYPOZVBQO2CISGZ777RYGOPYC2FT6S3K",
-       "id":713226564145153,
-       "paging_token":"713226564145153",
-       "starting_balance":"10000",
-       "type_i":0,
-       "type":"create_account"}
-```
-
-</CodeExample>
-
-Cada vez que recibas un nuevo pago, obtendrás una nueva fila de datos. Los pagos no son el único endpoint que admite streaming. También puedes transmitir transacciones [/transactions](../../../data/apis/horizon/api-reference/resources/transactions/README.mdx) y operaciones [/operations](../../../data/apis/horizon/api-reference/resources/operations/README.mdx).
-
-## Siguiendo pagos usando `EventStream`
-
-> **Advertencia!** El objeto `EventSource` no se reconecta para ciertos tipos de error, por lo que puede dejar de funcionar. Si necesitas una conexión de streaming fiable, por favor utiliza nuestro [SDK](https://github.com/stellar/js-stellar-sdk).
-
-Otra forma de seguir pagos es escribiendo un simple script de JS que transmitirá pagos e imprimirlos en la consola. Crea un archivo `stream_payments.js` y pega el siguiente código en él:
-
-<CodeExample>
-
-```js
-var EventSource = require("eventsource");
-var es = new EventSource(
-  "https://horizon-testnet.stellar.org/accounts/GB7JFK56QXQ4DVJRNPDBXABNG3IVKIXWWJJRJICHRU22Z5R5PI65GAK3/payments",
-);
-es.onmessage = function (message) {
-  var result = message.data ? JSON.parse(message.data) : message;
-  console.log("New payment:");
-  console.log(result);
-};
-es.onerror = function (error) {
-  console.log("An error occurred!");
-};
-```
-
-</CodeExample>
-
-Ahora, ejecuta nuestro script: `node stream_payments.js`. Deberías ver la siguiente salida:
-
-<CodeExample>
-
-```bash
-New payment:
-{ _links:
-   { effects:
-      { href: '/operations/713226564145153/effects/{?cursor,limit,order}',
-        templated: true },
-     precedes: { href: '/operations?cursor=713226564145153&order=asc' },
-     self: { href: '/operations/713226564145153' },
-     succeeds: { href: '/operations?cursor=713226564145153&order=desc' },
-     transactions: { href: '/transactions/713226564145152' } },
-  account: 'GB7JFK56QXQ4DVJRNPDBXABNG3IVKIXWWJJRJICHRU22Z5R5PI65GAK3',
-  funder: 'GBS43BF24ENNS3KPACUZVKK2VYPOZVBQO2CISGZ777RYGOPYC2FT6S3K',
-  id: 713226564145153,
-  paging_token: '713226564145153',
-  starting_balance: '10000',
-  type_i: 0,
-  type: 'create_account' }
-```
-
-</CodeExample>
-
-## Probándolo
-
-Ahora sabemos cómo obtener un stream de transacciones a una cuenta. Verifiquemos si nuestra solución realmente funciona y si aparecen nuevos pagos. Observemos mientras enviamos un pago ([`create_account` operation](../../../learn/fundamentals/transactions/list-of-operations.mdx#create-account)) desde nuestra cuenta a otra cuenta.
-
-Usamos la operación `create_account` porque estamos enviando un pago a una nueva cuenta no financiada. Si estuviéramos enviando un pago a una cuenta que ya está financiada, usaríamos la operación [`payment`](../../../learn/fundamentals/transactions/list-of-operations.mdx#payment).
-
-Primero, verifiquemos el número de secuencia de nuestra cuenta para que podamos crear una transacción de pago. Para hacerlo, enviamos una solicitud a horizon:
-
-<CodeExample>
-
-```bash
-$ curl "https://horizon-testnet.stellar.org/accounts/GB7JFK56QXQ4DVJRNPDBXABNG3IVKIXWWJJRJICHRU22Z5R5PI65GAK3"
-```
-
-</CodeExample>
-
-El número de secuencia se puede encontrar bajo el campo `sequence`. Para nuestro ejemplo, el número de secuencia actual es `713226564141056`. Guarda tu valor en algún lugar.
-
-Ahora, crea el archivo `make_payment.js` y pega el siguiente código en él, reemplazando el número de secuencia según corresponda:
-
-<CodeExample>
-
-```js
-var StellarBase = require("stellar-base");
-var StellarSdk = require("stellar-sdk");
-
-var keypair = StellarBase.Keypair.fromSecret(
-  "SCU36VV2OYTUMDSSU4EIVX4UUHY3XC7N44VL4IJ26IOG6HVNC7DY5UJO",
-);
-var account = new StellarBase.Account(keypair.publicKey(), "713226564141056");
-
-var amount = "100";
-var transaction = new StellarSdk.TransactionBuilder(account, {
-  networkPassphrase: StellarBase.Networks.TESTNET,
-  fee: StellarSdk.BASE_FEE,
-})
-  .addOperation(
-    StellarBase.Operation.createAccount({
-      destination: StellarBase.Keypair.random().publicKey(),
-      startingBalance: amount,
-    }),
-  )
-  .setTimeout(180)
-  .build();
-
-transaction.sign(keypair);
-
-console.log(transaction.toEnvelope().toXDR().toString("base64"));
-```
-
-</CodeExample>
-
-Después de ejecutar este script, deberías ver un blob de transacción firmado. Para enviar esta transacción, la enviamos a Horizon o Stellar-Core. Pero antes de hacerlo, abramos una nueva consola y comencemos nuestro script anterior con `node stream_payments.js`.
-
-Ahora, para enviar una transacción, solo usa Horizon:
-
-<CodeExample>
-
-```bash
-curl -H "Content-Type: application/json" -X POST -d '{"tx":"AAAAAgAAAAB+kqu+heHB1TFrxhuALTbRVSL2slMUoEeNNaz2PXo90wAAAGQAAoitAAAAAQAAAAEAAAAAAAAAAAAAAABgJHaDAAAAAAAAAAEAAAAAAAAAAAAAAAByS4gefO1iu/ZfYlr+PMA2AZsHJmSK/4NActJ1Oa1BIgAAAAA7msoAAAAAAAAAAAE9ej3TAAAAQPo1YHJMpdWKatEQxj7DqP1rrR6pA+OjK9q3WcU/sBwvKk6GhpdwA3gkUDrkREU0cFQSNKwugNFkGkR0zFmROgw="}' "https://horizon-testnet.stellar.org/transactions"
-```
-
-</CodeExample>
-
-Deberías ver un nuevo pago en una ventana que ejecuta el script `stream_payments.js`.
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
deleted file mode 100644
index 61f36d383a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/send-and-receive-payments.mdx
+++ /dev/null
@@ -1,1409 +0,0 @@
----
-title: Enviar y recibir pagos
-sidebar_position: 20
-description: Aprender a enviar pagos y vigilar los pagos recibidos en la red Stellar
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-import { Alert } from "@site/src/components/Alert";
-
-La mayor parte del tiempo, estarás enviando dinero a alguien más que tiene su propia cuenta. Sin embargo, para este tutorial, necesitarás una segunda cuenta para realizar transacciones. Así que antes de continuar, sigue los pasos descritos en [Crear una Cuenta](./create-account.mdx) para hacer _dos_ cuentas: una para enviar y una para recibir. También usaremos tanto las operaciones de pago como las invocaciones de contratos inteligentes para realizar pagos. Para más detalles sobre los diferentes tipos de transacciones, consulta la documentación de [Operaciones y Transacciones](../../../learn/fundamentals/transactions/README.mdx).
-
-## Acerca de Operaciones y Transacciones
-
-Hay dos formas de realizar pagos en Stellar. Una opción es usar las operaciones relacionadas con pagos de Stellar, y la otra es invocar una función en el contrato del token; la opción que deberías tomar depende del caso de uso.
-
-Si quieres hacer un pago de un activo Stellar entre dos cuentas Stellar, utiliza las operaciones de pago. Las tarifas de transacción son más económicas cuando usas estas operaciones en comparación con las que invocan el contrato de activo Stellar (o SAC).
-
-Si quieres hacer un pago de un activo Stellar entre una cuenta Stellar y una dirección de contrato, o entre dos direcciones de contrato, debes usar el SAC. Las operaciones relacionadas con pagos de Stellar no pueden tener direcciones de contrato como origen o destino.
-
-Finalmente, si quieres hacer un pago de un token de contrato (no un activo Stellar), debes usar el contrato del token. Las operaciones de pago de Stellar solo pueden usarse para transferir activos Stellar.
-
-Para aprender más sobre las diferencias entre activos Stellar y tokens de contrato, consulta la visión general de [Tokens](../../../../docs/tokens).
-
-Además, hay dos opciones principales para interactuar con la red Stellar: la [API Horizon](../../../data/apis/horizon/README.mdx) y [Stellar RPC](../../../data/apis/rpc/README.mdx). En general, deberías usar RPC salvo que necesites características que solo Horizon provea. Si tu caso de uso se limita a hacer pagos, RPC debería ser suficiente. De todas formas, cada ejemplo de pago se desglosará para mostrar cómo realizar dichos pagos con cualquiera de las dos opciones.
-
-<Alert>
-
-En los siguientes ejemplos de código, se omite la verificación de errores adecuada por brevedad. Sin embargo, debes _siempre_ validar tus resultados, ya que hay muchas formas en que las solicitudes pueden fallar. Debes consultar la guía sobre [Manejo de Errores](../../../data/apis/horizon/api-reference/errors/error-handling.mdx) para obtener consejos sobre estrategias de gestión de errores.
-
-</Alert>
-
-## Usando la Operación de Pago
-
-### Enviar un Pago
-
-Al enviar pagos en Stellar, construyes una transacción con una operación de pago, la firmas y la envías a la red. Stellar almacena y comunica los datos de transacciones en un formato binario llamado [XDR](../../../learn/fundamentals/data-format/xdr.mdx), que está optimizado para el rendimiento de la red pero no es legible para el ojo humano. Por suerte, la [API Horizon](../../../data/apis/horizon/README.mdx), Stellar RPC y los [SDKs de Stellar](../../../tools/sdks/README.mdx) convierten los XDRs en formatos más amigables. Así es como podrías enviar 10 lumens a una cuenta:
-
-#### Usando Stellar RPC
-
-<CodeExample>
-
-```js
-import * as StellarSdk from "stellar-sdk";
-
-// Initialize Soroban RPC server for testnet
-const rpc = new StellarSdk.rpc.Server("https://soroban-testnet.stellar.org");
-
-// Initalize the source account's secret key and destination account ID.
-// The source account is the one that will send the payment, and the destination account
-// is the one that will receive the payment.
-const sourceKeys = StellarSdk.Keypair.fromSecret(
-  "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4"
-);
-const destinationId =
-  "GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5";
-
-// First, check to make sure that the destination account exists.
-try {
-  await rpc.getAccount(destinationId);
-} catch (error) {
-  console.error("Error checking destination account:", error);
-  throw error;
-}
-
-// Now we also load the source account to build the transaction.
-let sourceAccount: StellarSdk.Account;
-try {
-  sourceAccount = await rpc.getAccount(sourceKeys.publicKey());
-} catch (error) {
-  console.error("Error checking source account:", error);
-  throw error;
-}
-
-// The next step is to parametrize and build the transaction object:
-// Using the source account we just loaded we begin to assemble the transaction.
-// We set the fee to the base fee, which is 100 stroops (0.00001 XLM).
-// We also set the network passphrase to TESTNET.
-const transaction = new StellarSdk.TransactionBuilder(sourceAccount, {
-  fee: StellarSdk.BASE_FEE,
-  networkPassphrase: StellarSdk.Networks.TESTNET,
-})
-  // We then add a payment operation to the transaction oject.
-  // This operation will send 10 XLM to the destination account.
-  // Obs.: Not specifying a explicit source account here means that the
-  // operation will use the source account of the whole transaction, which we specified above.
-  .addOperation(
-    StellarSdk.Operation.payment({
-      destination: destinationId,
-      asset: StellarSdk.Asset.native(),
-      amount: "10",
-    })
-  )
-  // We include an optional memo which oftentimes is used to identify the transaction
-  // when working with pooled accounts or to facilitate reconciliation.
-  .addMemo(StellarSdk.Memo.id("1234567890"))
-  // Finally, we set a timeout for the transaction.
-  // This means that the transaction will not be valid anymore after 180 seconds.
-  .setTimeout(180)
-  .build();
-
-
-// We sign the transaction with the source account's secret key.
-transaction.sign(sourceKeys);
-
-// Now we can send the transaction to the network.
-// The sendTransaction method immediately returns a reply with the transaction hash
-// and the status "PENDING". This means the transaction was received and is being processed.
-const sendTransactionResponse = await rpc.sendTransaction(transaction);
-
-// Here we check the status of the transaction as there are
-// a possible outcomes after sending a transaction that would have
-// to be handled accordingly, such as "DUPLICATE" or "TRY_AGAIN_LATER".
-if (sendTransactionResponse.status !== "PENDING") {
-  throw new Error(
-    `Failed to send transaction, status: ${sendTransactionResponse.status}`
-  );
-}
-
-// Here we poll the transaction status to await for its final result.
-// We can use the transaction hash to poll the transaction status later.
-const finalStatus = await rpc.pollTransaction(sendTransactionResponse.hash, {
-  sleepStrategy: (_iter: number) => 500,
-  attempts: 5,
-});
-
-// The pollTransaction method will return the final status of the transaction
-// after the specified number of attempts or when the transaction is finalized.
-// We then check the final status of the transaction and handle it accordingly.
-switch (finalStatus.status) {
-  case StellarSdk.rpc.Api.GetTransactionStatus.FAILED:
-  case StellarSdk.rpc.Api.GetTransactionStatus.NOT_FOUND:
-    throw new Error(`Transaction failed with status: ${finalStatus.status}`);
-  case StellarSdk.rpc.Api.GetTransactionStatus.SUCCESS:
-    console.log("Success! Results:", finalStatus);
-    break;
-}
-
-```
-
-</CodeExample>
-
-Las diferencias clave al usar RPC en lugar de Horizon:
-
-1. **Envío instantáneo**: `rpc.sendTransaction()` devuelve inmediatamente con un estado "PENDING"
-2. **Requiere sondeo activo**: Debes sondear con `rpc.pollTransaction()` para obtener el resultado final
-3. **Configuración del sondeo**: Puedes personalizar los intervalos del sondeo y los intentos de reintento
-4. **Manejo de estado**: Verifica los estados SUCCESS, FAILED o NOT_FOUND en el resultado final
-
-#### Usando la API Horizon
-
-<CodeExample>
-
-```js
-import * as StellarSdk from "stellar-sdk";
-
-// Initialize Horizon server for testnet
-const server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org"
-);
-
-// Initalize the source account's secret key and destination account ID.
-// The source account is the one that will send the payment, and the destination account
-// is the one that will receive the payment.
-
-const sourceKeys = StellarSdk.Keypair.fromSecret(
-  "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4"
-);
-const destinationId =
-  "GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5";
-
-// First, check to make sure that the destination account exists.
-try {
-  await server.loadAccount(destinationId);
-} catch (error) {
-  console.error("Error checking destination account:", error);
-  throw error;
-}
-
-// Now we also load the source account to build the transaction.
-let sourceAccount: StellarSdk.Account;
-try {
-  sourceAccount = await server.loadAccount(sourceKeys.publicKey());
-} catch (error) {
-  console.error("Error checking source account:", error);
-  throw error;
-}
-
-// The next step is to parametrize and build the transaction object:
-// Using the source account we just loaded we begin to assemble the transaction.
-// We set the fee to the base fee, which is 100 stroops (0.00001 XLM).
-// We also set the network passphrase to TESTNET.
-const transaction = new StellarSdk.TransactionBuilder(sourceAccount, {
-    fee: StellarSdk.BASE_FEE,
-    networkPassphrase: StellarSdk.Networks.TESTNET,
-  })
-  // We then add a payment operation to the transaction oject.
-  // This operation will send 10 XLM to the destination account.
-  // Obs.: Not specifying a explicit source account here means that the
-  // operation will use the source account of the whole transaction, which we specified above.
-  .addOperation(
-    StellarSdk.Operation.payment({
-      destination: destinationId,
-      asset: StellarSdk.Asset.native(),
-      amount: "10",
-    })
-  )
-  // We include an optional memo which oftentimes is used to identify the transaction
-  // when working with pooled accounts or to facilitate reconciliation.
-  .addMemo(StellarSdk.Memo.id("1234567890"))
-  // Finally, we set a timeout for the transaction.
-  // This means that the transaction will not be valid anymore after 180 seconds.
-  .setTimeout(180)
-  .build();
-
-
-// We sign the transaction with the source account's secret key.
-transaction.sign(sourceKeys);
-
-// Now we can send the transaction to the network.
-// The sendTransaction method returns a promise that resolves with the transaction result.
-// The result will contain the transaction hash and other details.
-try {
-  const result = await server.submitTransaction(transaction);
-  console.log("Success! Results:", result);
-} catch (error) {
-  console.error("Something went wrong!", error);
-}
-
-```
-
-```java
-Server server = new Server("https://horizon-testnet.stellar.org");
-
-KeyPair source = KeyPair.fromSecretSeed("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4");
-KeyPair destination = KeyPair.fromAccountId("GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5");
-
-// First, check to make sure that the destination account exists.
-// You could skip this, but if the account does not exist, you will be charged
-// the transaction fee when the transaction fails.
-// It will throw HttpResponseException if account does not exist or there was another error.
-server.accounts().account(destination.getAccountId());
-
-// If there was no error, load up-to-date information on your account.
-AccountResponse sourceAccount = server.accounts().account(source.getAccountId());
-
-// Start building the transaction.
-Transaction transaction = new Transaction.Builder(sourceAccount, Network.TESTNET)
-        .addOperation(new PaymentOperation.Builder(destination.getAccountId(), new AssetTypeNative(), "10").build())
-        // A memo allows you to add your own metadata to a transaction. It's
-        // optional and does not affect how Stellar treats the transaction.
-        .addMemo(Memo.text("Test Transaction"))
-        // Wait a maximum of three minutes for the transaction
-        .setTimeout(180)
-        // Set the amount of lumens you're willing to pay per operation to submit your transaction
-        .setBaseFee(Transaction.MIN_BASE_FEE)
-        .build();
-// Sign the transaction to prove you are actually the person sending it.
-transaction.sign(source);
-
-// And finally, send it off to Stellar!
-try {
-  SubmitTransactionResponse response = server.submitTransaction(transaction);
-  System.out.println("Success!");
-  System.out.println(response);
-} catch (Exception e) {
-  System.out.println("Something went wrong!");
-  System.out.println(e.getMessage());
-  // If the result is unknown (no response body, timeout etc.) we simply resubmit
-  // already built transaction:
-  // SubmitTransactionResponse response = server.submitTransaction(transaction);
-}
-```
-
-```go
-package main
-
-import (
-    "github.com/stellar/go/keypair"
-    "github.com/stellar/go/network"
-    "github.com/stellar/go/txnbuild"
-    "github.com/stellar/go/clients/horizonclient"
-    "fmt"
-)
-
-func main () {
-    source := "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4"
-    destination := "GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5"
-    client := horizonclient.DefaultTestNetClient
-
-    // Make sure destination account exists
-    destAccountRequest := horizonclient.AccountRequest{AccountID: destination}
-    destinationAccount, err := client.AccountDetail(destAccountRequest)
-    if err != nil {
-        panic(err)
-    }
-
-    fmt.Println("Destination Account", destinationAccount)
-
-    // Load the source account
-    sourceKP := keypair.MustParseFull(source)
-    sourceAccountRequest := horizonclient.AccountRequest{AccountID: sourceKP.Address()}
-    sourceAccount, err := client.AccountDetail(sourceAccountRequest)
-    if err != nil {
-        panic(err)
-    }
-
-    // Build transaction
-    tx, err := txnbuild.NewTransaction(
-      txnbuild.TransactionParams{
-        SourceAccount:        &sourceAccount,
-        IncrementSequenceNum: true,
-        BaseFee:              txnbuild.MinBaseFee,
-        Preconditions: txnbuild.Preconditions{
-          TimeBounds: txnbuild.NewInfiniteTimeout(), // Use a real timeout in production!
-        },
-        Operations: []txnbuild.Operation{
-          &txnbuild.Payment{
-            Destination: destination,
-            Amount:      "10",
-            Asset:       txnbuild.NativeAsset{},
-          },
-        },
-      },
-    )
-
-    if err != nil {
-        panic(err)
-    }
-
-    // Sign the transaction to prove you are actually the person sending it.
-    tx, err = tx.Sign(network.TestNetworkPassphrase, sourceKP)
-    if err != nil {
-        panic(err)
-    }
-
-    // And finally, send it off to Stellar!
-    resp, err := horizonclient.DefaultTestNetClient.SubmitTransaction(tx)
-    if err != nil {
-        panic(err)
-    }
-
-    fmt.Println("Successful Transaction:")
-    fmt.Println("Ledger:", resp.Ledger)
-    fmt.Println("Hash:", resp.Hash)
-}
-```
-
-```python
-from stellar_sdk import Asset, Keypair, Network, Server, TransactionBuilder
-from stellar_sdk.exceptions import NotFoundError, BadResponseError, BadRequestError
-
-server = Server("https://horizon-testnet.stellar.org")
-source_key = Keypair.from_secret("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4")
-destination_id = "GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5"
-
-# First, check to make sure that the destination account exists.
-# You could skip this, but if the account does not exist, you will be charged
-# the transaction fee when the transaction fails.
-try:
-    server.load_account(destination_id)
-except NotFoundError:
-    # If the account is not found, surface an error message for logging.
-    raise Exception("The destination account does not exist!")
-
-# If there was no error, load up-to-date information on your account.
-source_account = server.load_account(source_key.public_key)
-
-# Let's fetch base_fee from network
-base_fee = server.fetch_base_fee()
-
-# Start building the transaction.
-transaction = (
-    TransactionBuilder(
-        source_account=source_account,
-        network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-        base_fee=base_fee,
-    )
-        # Because Stellar allows transaction in many currencies, you must specify the asset type.
-        # Here we are sending Lumens.
-        .append_payment_op(destination=destination_id, asset=Asset.native(), amount="10")
-        # A memo allows you to add your own metadata to a transaction. It's
-        # optional and does not affect how Stellar treats the transaction.
-        .add_text_memo("Test Transaction")
-        # Wait a maximum of three minutes for the transaction
-        .set_timeout(10)
-        .build()
-)
-
-# Sign the transaction to prove you are actually the person sending it.
-transaction.sign(source_key)
-
-try:
-    # And finally, send it off to Stellar!
-    response = server.submit_transaction(transaction)
-    print(f"Response: {response}")
-except (BadRequestError, BadResponseError) as err:
-    print(f"Something went wrong!\n{err}")
-```
-
-</CodeExample>
-
-#### Desglose paso a paso
-
-¿Qué exactamente sucedió allí? Desglosemoslo.
-
-1. Confirma que la ID de cuenta (también conocida como la _clave pública_) a la que envías realmente existe cargando los datos de la cuenta asociada desde la red Stellar. Está bien omitir este paso, pero te da la oportunidad de evitar hacer una transacción que inevitablemente fallará.
-
-<CodeExample>
-
-```js
-// Using RPC
-try {
-  const destinationAccount = await rpc.getAccount(destinationId);
-  /* validate the account */
-} catch (error) {
-  console.error("Error checking the destination account:", error);
-  throw error;
-}
-
-// Using Horizon
-try {
-  const destinationAccount = await server.loadAccount(destinationId);
-  /* validate the account */
-} catch (error) {
-  console.error("Error checking the destination account:", error);
-  throw error;
-}
-```
-
-```java
-server.accounts().account(destination.getAccountId());
-```
-
-```go
-destAccountRequest := horizonclient.AccountRequest{AccountID: destination}
-destinationAccount, err := client.AccountDetail(destAccountRequest)
-if err != nil {
-    panic(err)
-}
-fmt.Println("Destination Account", destinationAccount)
-```
-
-```python
-server.load_account(destination_id)
-```
-
-</CodeExample>
-
-2. Carga los datos de la cuenta desde la que estás enviando. Una cuenta solo puede realizar una transacción a la vez y tiene algo llamado un [número de secuencia](../../../learn/glossary.mdx#sequence-number), que ayuda a Stellar a verificar el orden de las transacciones. El número de secuencia de una transacción debe coincidir con el número de secuencia de la cuenta, así que necesitas obtener el número de secuencia actual de la cuenta de la red.
-
-<CodeExample>
-
-```js
-// Using RPC
-let sourceAccount: StellarSdk.Account;
-try {
-  sourceAccount = await rpc.getAccount(sourceKeys.publicKey());
-  /* validate the account */
-} catch (error) {
-  console.error("Error checking source account:", error);
-  throw error;
-}
-/* use sourceAccount to build transaction */
-
-
-
-// Using Horizon
-let sourceAccount: StellarSdk.Account;
-try {
-  sourceAccount = await server.loadAccount(sourceKeys.publicKey());
-  /* validate the account */
-} catch (error) {
-  console.error("Error checking source account:", error);
-  throw error;
-}
-/* use sourceAccount to build transaction */
-```
-
-```java
-AccountResponse sourceAccount = server.accounts().account(source.getAccountId());
-```
-
-```go
-sourceKP := keypair.MustParseFull(source)
-sourceAccountRequest := horizonclient.AccountRequest{AccountID: sourceKP.Address()}
-sourceAccount, err := client.AccountDetail(sourceAccountRequest)
-if err != nil {
-  panic(err)
-}
-```
-
-```python
-source_account = server.load_account(source_key.public_key)
-```
-
-</CodeExample>
-
-El SDK incrementará automáticamente el número de secuencia de la cuenta cuando construyas una transacción, así que no necesitarás recuperar esta información nuevamente si deseas realizar una segunda transacción.
-
-3. Empieza a construir una transacción. Esto requiere un objeto de cuenta, no solo una ID de cuenta, porque incrementará el número de secuencia de la cuenta.
-
-<CodeExample>
-
-```js
-const transaction = new StellarSdk.TransactionBuilder(sourceAccount);
-```
-
-```java
-Transaction transaction = new Transaction.Builder(sourceAccount, Network.TESTNET)
-```
-
-```go
-tx, err := txnbuild.NewTransaction(
-  txnbuild.TransactionParams{
-    SourceAccount:        &sourceAccount,
-    IncrementSequenceNum: true,
-    BaseFee:              MinBaseFee,
-    Preconditions: txnbuild.Preconditions{
-      TimeBounds: txnbuild.NewInfiniteTimeout(), // Use a real timeout in production!
-    },
-    ...
-  },
-)
-
-if err != nil {
-    panic(err)
-}
-```
-
-```python
-transaction = TransactionBuilder(
-    source_account=source_account,
-    network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-    base_fee=base_fee
-)
-```
-
-</CodeExample>
-
-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:
-
-<CodeExample>
-
-```js
-.addOperation(StellarSdk.Operation.payment({
-  destination: destinationId,
-  asset: StellarSdk.Asset.native(),
-  amount: "10"
-}))
-```
-
-```java
-.addOperation(new PaymentOperation.Builder(destination.getAccountId(), new AssetTypeNative(), "10").build())
-```
-
-```go
-Operations: []txnbuild.Operation{
-    &txnbuild.Payment{
-      Destination: destination,
-      Amount:      "10",
-      Asset:       txnbuild.NativeAsset{},
-    },
-  },
-```
-
-```python
-.append_payment_op(destination=destination_id, asset=Asset.native(), amount="10")
-```
-
-</CodeExample>
-
-También debes notar que la cantidad es una cadena en lugar de un número. Al trabajar con fracciones extremadamente pequeñas o grandes valores, [la matemática de punto flotante puede introducir pequeñas inexactitudes](https://en.wikipedia.org/wiki/Floating_point#Accuracy_problems). Dado que no todos los sistemas tienen una forma nativa de representar con precisión decimales extremadamente pequeños o grandes, Stellar utiliza cadenas como una forma confiable de representar la cantidad exacta en cualquier sistema.
-
-5. Opcionalmente, puedes agregar tus propios metadatos, llamados [memo](../../../learn/encyclopedia/transactions-specialized/memos.mdx), a una transacción. Stellar no hace nada con estos datos, pero puedes usarlos para cualquier propósito que desees. Muchos exchanges requieren memos para transacciones entrantes porque utilizan una sola cuenta Stellar para todos sus usuarios y dependen del memo para diferenciar entre cuentas internas de usuarios.
-
-<CodeExample title="Agregar un Memo">
-
-```js
-.addMemo(StellarSdk.Memo.text('Test Transaction'))
-```
-
-```java
-.addMemo(Memo.text("Test Transaction"));
-```
-
-```go
-Memo: txnbuild.MemoText("Test Transaction")
-```
-
-```python
-.add_text_memo("Test Transaction")
-```
-
-</CodeExample>
-
-6. Ahora que la transacción tiene todos los datos que necesita, debes firmarla criptográficamente utilizando tu clave secreta. Esto demuestra que los datos realmente provinieron de ti y no de alguien que te imita.
-
-<CodeExample>
-
-```js
-transaction.sign(sourceKeys);
-```
-
-```java
-transaction.sign(source);
-```
-
-```go
-tx, err = tx.Sign(network.TestNetworkPassphrase, sourceKP)
-if err != nil {
-    panic(err)
-}
-```
-
-```python
-transaction.sign(source_key)
-```
-
-</CodeExample>
-
-7. Y finalmente, ¡envíala a la red Stellar!
-
-<CodeExample>
-
-```js
-// Using RPC - requires polling for final status
-let sendTransactionResponse: StellarSdk.rpc.Api.SendTransactionResponse;
-try {
-  sendTransactionResponse = await rpc.sendTransaction(transaction);
-  if (sendTransactionResponse.status !== "PENDING") {
-    throw sendTransactionResponse;
-  }
-} catch (error) {
-  console.error("Error sending transaction:", error);
-  throw error;
-}
-
-try {
-  const finalStatus = await rpc.pollTransaction(sendTransactionResponse.hash, {
-    sleepStrategy: (_iter: number) => 500,
-    attempts: 5,
-  });
-  switch (finalStatus.status) {
-    case StellarSdk.rpc.Api.GetTransactionStatus.FAILED:
-    case StellarSdk.rpc.Api.GetTransactionStatus.NOT_FOUND:
-      throw new Error(`Transaction failed with status: ${finalStatus.status}`);
-    case StellarSdk.rpc.Api.GetTransactionStatus.SUCCESS:
-      console.log("Success! Results:", finalStatus);
-      break;
-  }
-} catch (error) {
-  console.error("Error polling transaction status:", error);
-  throw error;
-}
-
-
-// Using Horizon - returns final status immediately
-try {
-  const result = await server.submitTransaction(transaction);
-  console.log("Success! Results:", result);
-} catch (error) {
-  console.error("Something went wrong!", error);
-}
-```
-
-```java
-server.submitTransaction(transaction);
-```
-
-```go
-resp, err := horizonclient.DefaultTestNetClient.SubmitTransaction(tx)
-if err != nil {
-    panic(err)
-}
-```
-
-```python
-server.submit_transaction(transaction)
-```
-
-</CodeExample>
-
-En este ejemplo, estamos enviando la transacción a la instancia pública de Horizon mantenida por SDF (la API Stellar) o a un servidor Stellar RPC. Al enviar transacciones a un servidor Horizon o RPC — que es lo que la mayoría hace — es posible que no recibas respuesta del servidor debido a bugs, condiciones de red, etc. En tal situación, es imposible determinar el estado de tu transacción.
-
-Por eso deberías siempre guardar una transacción construida (o una transacción codificada en formato XDR) en una variable o base de datos y reenviarla si no conoces su estado. Si la transacción ya se aplicó exitosamente al ledger, tanto Horizon como RPC devolverán simplemente el resultado guardado y no intentarán enviar la transacción otra vez. Solo en casos donde el estado de la transacción es desconocido (y por ende tiene posibilidad de ser incluida en un ledger) se realizará un reenvío a la red.
-
-### Recibir un Pago
-
-En realidad, no necesitas hacer nada para recibir pagos en una cuenta Stellar: si un pagador realiza una transacción exitosa para enviarte activos, esos activos se agregarán automáticamente a tu cuenta.
-
-Sin embargo, es posible que desees estar atento a los pagos entrantes. Un programa simple que vigila la red en busca de pagos e imprime cada uno podría verse así:
-
-#### Usando Stellar RPC
-
-<Alert>
-Con el próximo lanzamiento del Protocolo 23, los pagos nativos para activos también emitirán eventos de contratos inteligentes, lo que permitirá usar Stellar RPC para transmitir pagos de activos nativos. El proceso será similar al ejemplo bajo la sección [Contrato de Activo Stellar (SAC) -> Recibir un Pago](#receive-a-payment-1). Por ahora, puedes usar la API Horizon para transmitir pagos de activos nativos.
-
-</Alert>
-
-#### Usando Horizon
-
-<CodeExample title="Recibir Pagos">
-
-```js
-var StellarSdk = require("stellar-sdk");
-
-var server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-var accountId = "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF";
-
-// Create an API call to query payments involving the account.
-var payments = server.payments().forAccount(accountId);
-
-// If some payments have already been handled, start the results from the
-// last seen payment. (See below in `handlePayment` where it gets saved.)
-var lastToken = loadLastPagingToken();
-if (lastToken) {
-  payments.cursor(lastToken);
-}
-
-// `stream` will send each recorded payment, one by one, then keep the
-// connection open and continue to send you new payments as they occur.
-payments.stream({
-  onmessage: function (payment) {
-    // Record the paging token so we can start from here next time.
-    savePagingToken(payment.paging_token);
-
-    // The payments stream includes both sent and received payments. We only
-    // want to process received payments here.
-    if (payment.to !== accountId) {
-      return;
-    }
-
-    // In Stellar’s API, Lumens are referred to as the “native” type. Other
-    // asset types have more detailed information.
-    var asset;
-    if (payment.asset_type === "native") {
-      asset = "lumens";
-    } else {
-      asset = payment.asset_code + ":" + payment.asset_issuer;
-    }
-
-    console.log(payment.amount + " " + asset + " from " + payment.from);
-  },
-
-  onerror: function (error) {
-    console.error("Error in payment stream");
-  },
-});
-
-function savePagingToken(token) {
-  // In most cases, you should save this to a local database or file so that
-  // you can load it next time you stream new payments.
-}
-
-function loadLastPagingToken() {
-  // Get the last paging token from a local database or file
-}
-```
-
-```java
-Server server = new Server("https://horizon-testnet.stellar.org");
-KeyPair account = KeyPair.fromAccountId("GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF");
-
-// Create an API call to query payments involving the account.
-PaymentsRequestBuilder paymentsRequest = server.payments().forAccount(account.getAccountId());
-
-// If some payments have already been handled, start the results from the
-// last seen payment. (See below in `handlePayment` where it gets saved.)
-String lastToken = loadLastPagingToken();
-if (lastToken != null) {
-  paymentsRequest.cursor(lastToken);
-}
-
-// `stream` will send each recorded payment, one by one, then keep the
-// connection open and continue to send you new payments as they occur.
-paymentsRequest.stream(new EventListener<OperationResponse>() {
-  @Override
-  public void onEvent(OperationResponse payment) {
-    // Record the paging token so we can start from here next time.
-    savePagingToken(payment.getPagingToken());
-
-    // The payments stream includes both sent and received payments. We only
-    // want to process received payments here.
-    if (payment instanceof PaymentOperationResponse) {
-      if (!((PaymentOperationResponse) payment).getTo().equals(account.getAccountId()) {
-        return;
-      }
-
-      String amount = ((PaymentOperationResponse) payment).getAmount();
-
-      Asset asset = ((PaymentOperationResponse) payment).getAsset();
-      String assetName;
-      if (asset.equals(new AssetTypeNative())) {
-        assetName = "lumens";
-      } else {
-        StringBuilder assetNameBuilder = new StringBuilder();
-        assetNameBuilder.append(((AssetTypeCreditAlphaNum) asset).getCode());
-        assetNameBuilder.append(":");
-        assetNameBuilder.append(((AssetTypeCreditAlphaNum) asset).getIssuer());
-        assetName = assetNameBuilder.toString();
-      }
-
-      StringBuilder output = new StringBuilder();
-      output.append(amount);
-      output.append(" ");
-      output.append(assetName);
-      output.append(" from ");
-      output.append(((PaymentOperationResponse) payment).getFrom());
-      System.out.println(output.toString());
-    }
-  }
-
-  @Override
-  public void onFailure(Optional<Throwable> optional, Optional<Integer> optional1) {
-
-  }
-});
-```
-
-```go
-package main
-
-import (
-    "context"
-    "fmt"
-    "time"
-
-    "github.com/stellar/go/clients/horizonclient"
-    "github.com/stellar/go/protocols/horizon/operations"
-)
-
-func main() {
-    client := horizonclient.DefaultTestNetClient
-    opRequest := horizonclient.OperationRequest{ForAccount: "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF", Cursor: "now"}
-
-    ctx, cancel := context.WithCancel(context.Background())
-    go func() {
-        // Stop streaming after 60 seconds.
-        time.Sleep(60 * time.Second)
-        cancel()
-    }()
-
-    printHandler := func(op operations.Operation) {
-        fmt.Println(op)
-    }
-    err := client.StreamPayments(ctx, opRequest, printHandler)
-    if err != nil {
-        fmt.Println(err)
-    }
-
-}
-```
-
-```python
-from stellar_sdk import Server
-
-def load_last_paging_token():
-    # Get the last paging token from a local database or file
-    return "now"
-
-def save_paging_token(paging_token):
-    # In most cases, you should save this to a local database or file so that
-    # you can load it next time you stream new payments.
-    pass
-
-server = Server("https://horizon-testnet.stellar.org")
-account_id = "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF"
-
-# Create an API call to query payments involving the account.
-payments = server.payments().for_account(account_id)
-
-# If some payments have already been handled, start the results from the
-# last seen payment. (See below in `handle_payment` where it gets saved.)
-last_token = load_last_paging_token()
-if last_token:
-    payments.cursor(last_token)
-
-# `stream` will send each recorded payment, one by one, then keep the
-# connection open and continue to send you new payments as they occur.
-for payment in payments.stream():
-    # Record the paging token so we can start from here next time.
-    save_paging_token(payment["paging_token"])
-
-    # We only process `payment`, ignore `create_account` and `account_merge`.
-    if payment["type"] != "payment":
-        continue
-
-    # The payments stream includes both sent and received payments. We
-    # only want to process received payments here.
-    if payment['to'] != account_id:
-        continue
-
-    # In Stellar’s API, Lumens are referred to as the “native” type. Other
-    # asset types have more detailed information.
-    if payment["asset_type"] == "native":
-        asset = "Lumens"
-    else:
-        asset = f"{payment['asset_code']}:{payment['asset_issuer']}"
-    print(f"{payment['amount']} {asset} from {payment['from']}")
-```
-
-</CodeExample>
-
-Hay dos partes principales en este programa. Primero, creas una consulta para pagos que involucran una cuenta dada. Como la mayoría de las consultas en Stellar, esto podría devolver un gran número de elementos, así que la API devuelve tokens de paginación, que puedes usar más tarde para comenzar tu consulta desde el mismo punto donde la dejaste anteriormente. En el ejemplo anterior, las funciones para guardar y cargar tokens de paginación se dejaron en blanco, pero en una aplicación real, querrías guardar los tokens de paginación en un archivo o base de datos para poder continuar donde te quedaste en caso de que el programa se bloquee o el usuario lo cierre.
-
-<CodeExample>
-
-```js
-var payments = server.payments().forAccount(accountId);
-var lastToken = loadLastPagingToken();
-if (lastToken) {
-  payments.cursor(lastToken);
-}
-```
-
-```java
-PaymentsRequestBuilder paymentsRequest = server.payments().forAccount(account.getAccountId());
-String lastToken = loadLastPagingToken();
-if (lastToken != null) {
-  paymentsRequest.cursor(lastToken);
-}
-```
-
-```go
-client := horizonclient.DefaultTestNetClient
-opRequest := horizonclient.OperationRequest{ForAccount: "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF", Cursor: "now"}
-```
-
-```python
-payments = server.payments().for_account(account_id)
-last_token = load_last_paging_token()
-if last_token:
-    payments.cursor(last_token)
-```
-
-</CodeExample>
-
-En segundo lugar, los resultados de la consulta se transmiten. Esta es la forma más fácil de vigilar los pagos u otras transacciones. Cada pago existente se envía a través de la transmisión, uno por uno. Una vez que se han enviado todos los pagos existentes, la transmisión se mantiene abierta y se envían nuevos pagos a medida que se realizan.
-
-Pruébalo: Ejecuta este programa y luego, en otra ventana, crea y envía un pago. Deberías ver que este programa registra el pago.
-
-<CodeExample>
-
-```js
-payments.stream({
-  onmessage: function (payment) {
-    // handle a payment
-  },
-});
-```
-
-```java
-paymentsRequest.stream(new EventListener<OperationResponse>() {
-  @Override
-  public void onEvent(OperationResponse payment) {
-    // Handle a payment
-  }
-});
-```
-
-```go
-ctx, cancel := context.WithCancel(context.Background())
-go func() {
-    // Stop streaming after 60 seconds.
-    time.Sleep(60 * time.Second)
-    cancel()
-}()
-
-printHandler := func(op operations.Operation) {
-    fmt.Println(op)
-}
-err := client.StreamPayments(ctx, opRequest, printHandler)
-if err != nil {
-    fmt.Println(err)
-}
-```
-
-```python
-for payment in payments.stream():
-    # handle a payment
-```
-
-</CodeExample>
-
-También puedes solicitar pagos en grupos o páginas. Una vez que hayas procesado cada página de pagos, necesitarás solicitar la siguiente hasta que no quede ninguna.
-
-<CodeExample>
-
-```js
-payments.call().then(function handlePage(paymentsPage) {
-  paymentsPage.records.forEach(function (payment) {
-    // handle a payment
-  });
-  return paymentsPage.next().then(handlePage);
-});
-```
-
-```java
-Page<OperationResponse> page = payments.execute();
-
-for (OperationResponse operation : page.getRecords()) {
-    // handle a payment
-}
-
-page = page.getNextPage();
-```
-
-```python
-payments_current = payments.call()
-payments_next = payments.next()
-```
-
-</CodeExample>
-
-## Pagos con Stellar Asset Contract (SAC)
-
-Al enviar pagos usando Stellar Asset Contracts, invocas funciones de contratos inteligentes en lugar de usar operaciones de pago. Los pagos SAC utilizan la operación `invokeHostFunction` para llamar métodos del contrato como `transfer`, que proporciona la misma funcionalidad de pago pero mediante lógica de contrato. Este enfoque ofrece flexibilidad y programabilidad adicionales mientras mantiene compatibilidad con el sistema de activos de Stellar.
-
-En el ejemplo siguiente, usamos SAC como interfaz de contrato inteligente para el activo nativo, por lo que el resultado final es el mismo que si se hubiera ejecutado una operación de pago nativa. Sin embargo, el mismo proceso puede aplicarse para cualquier transferencia de contrato inteligente que involucre tokens de contrato estandarizados que sigan la [interfaz del token de contrato](../../../tokens/token-interface.mdx). Esto convierte a los pagos SAC en un enfoque unificado para manejar tanto activos nativos como tokens de contrato mediante una interfaz consistente basada en contratos.
-
-Así es como podrías enviar 10 lumens usando un SAC:
-
-<Alert>
-  Para usar el ejemplo de RPC a continuación, primero debes generar las bindings del contrato para que el
-  cliente pueda usarse apropiadamente. Esto puede lograrse mediante la [CLI Stellar](../../../tools/cli/README.mdx).
-
-Ejemplo: Generar las bindings de typescript para el contrato `sac` de un activo dado:
-
-```bash
- stellar contract bindings typescript --network=testnet --contract-id=CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC --output-dir=./bindings
-```
-
-</Alert>
-
-### Enviar un Pago
-
-<CodeExample>
-
-```js
-import {
-  Account,
-  Asset,
-  Keypair,
-  Networks,
-  TransactionBuilder,
-} from "stellar-sdk";
-import { Client } from "sac";
-import { Server } from "stellar-sdk/rpc";
-
-// Initialize Soroban RPC server for testnet
-const rpc = new Server("https://soroban-testnet.stellar.org");
-
-// Initalize the source account's secret key and destination account ID.
-// The source account is the one that will send the payment, and the destination account
-// is the one that will receive the payment.
-const sourceKeys = Keypair.fromSecret(
-  "SAMAJBEGN2743SLFDSBSVRCTQ7AC33XFZHWJVCJ2UMOIVH4MUJ7WWHEJ",
-);
-const destinationId =
-  "GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5";
-
-// First, check to make sure that the destination account exists.
-try {
-  await rpc.getAccount(destinationId);
-} catch (error) {
-  console.error("Error checking destination account:", error);
-  throw error;
-}
-
-// Now we also load the source account to build the transaction.
-try {
-  await rpc.getAccount(sourceKeys.publicKey());
-} catch (error) {
-  console.error("Error checking source account:", error);
-  throw error;
-}
-
-// Now we initialize the Stellar Asset Contract (SAC) client.
-// The client needs the RPC endpoint, network passphrase, contract ID for the asset,
-// and your account's public key. A signing function can also be provided to automatically
-// handle transaction signing when invoking contract methods with this client.
-//
-// In this case, we are using the native asset contract ID for the testnet.
-// The contract ID is derived from the native asset, which is represented by `Asset.native()`.
-// The `contractId` method will return the contract ID for the native asset on the specified network.
-const xlmClient = new Client({
-  rpcUrl: "https://soroban-testnet.stellar.org",
-  networkPassphrase: Networks.TESTNET,
-  contractId: Asset.native().contractId(Networks.TESTNET),
-  publicKey: sourceKeys.publicKey(),
-  signTransaction: async (txXdr) => {
-    const tx = await TransactionBuilder.fromXDR(txXdr, Networks.TESTNET);
-    tx.sign(sourceKeys);
-    return { signedTxXdr: tx.toXDR(), signerAddress: sourceKeys.publicKey() };
-  },
-});
-
-// Now, using the client, we assemble a soroban transaction to invoke the transfer
-// function of the native asset contract. The client will automatically
-// bundle the operation and simulate the transaction before providing us
-// with an assembled transaction object that we can sign and send.
-let assembledTx;
-try {
-  assembledTx = await xlmClient.transfer({
-    to: destinationId,
-    amount: BigInt(10_0000000), // Amount in stroops (1 XLM = 10,000,000 stroops)
-    from: sourceKeys.publicKey(),
-  });
-} catch (error) {
-  console.error("Error assembling the transaction:", error);
-  throw error;
-}
-
-// The assembled transaction is ready to be signed and sent. It already includes
-// a function that allows us to perform the signing and sending in one step. It will
-// use the signTransaction function we provided to the client to sign the transaction or
-// alternatively, receive a custom one just for this transaction.
-try {
-  const result = await assembledTx.signAndSend();
-  console.log("Transaction successful:", result.getTransactionResponse?.txHash);
-} catch (error) {
-  console.error("Error during transaction processing:", error);
-  throw error;
-}
-```
-
-</CodeExample>
-
-#### Desglose paso a paso
-
-¿Qué ocurrió exactamente en el ejemplo de pago SAC? Vamos a desglosarlo:
-
-1. Importa el cliente generado del contrato desde las bindings producidas por la CLI. Este cliente provee métodos tipados para interactuar con Stellar Asset Contract.
-
-<CodeExample>
-
-```js
-import { Client } from "sac";
-```
-
-</CodeExample>
-
-2. Inicializa el cliente SAC con detalles de conexión y una función personalizada de firma. El cliente necesita el endpoint RPC, la frase de red, el ID del contrato para el activo y la clave pública de tu cuenta. Se puede proporcionar una función de firma para manejar automáticamente la firma de transacciones al invocar métodos del contrato con este cliente.
-
-<CodeExample>
-
-```js
-const xlmClient = new Client({
-  rpcUrl: "https://soroban-testnet.stellar.org",
-  networkPassphrase: Networks.TESTNET,
-  contractId: Asset.native().contractId(Networks.TESTNET),
-  publicKey: sourceKeys.publicKey(),
-  signTransaction: async (txXdr) => {
-    const tx = await TransactionBuilder.fromXDR(txXdr, Networks.TESTNET);
-    tx.sign(sourceKeys);
-    return {
-      signedTxXdr: tx.toXDR(),
-      signerAddress: sourceKeys.publicKey(),
-    };
-  },
-});
-```
-
-</CodeExample>
-
-3. Inicia la transferencia llamando al método `transfer` del contrato. Esto devuelve una transacción ensamblada lista para firmar y enviar.
-
-<CodeExample>
-
-```js
-xlmClient.transfer({
-  to: destinationId,
-  amount: BigInt(10_0000000), // Amount in stroops (1 XLM = 10,000,000 stroops)
-  from: sourceKeys.publicKey(),
-});
-```
-
-</CodeExample>
-
-4. Firma y envía la transacción usando `signAndSend()`. El cliente gestiona la simulación, la firma (usando la función provista), el envío a la red y el sondeo del resultado final.
-
-<CodeExample>
-
-```js
-try {
-  const result = await assembledTx.signAndSend();
-  console.log("Transaction successful:", result.getTransactionResponse?.txHash);
-} catch (error) {
-  console.error("Error during transaction processing:", error);
-  throw error;
-}
-```
-
-</CodeExample>
-
-### Recibir un Pago
-
-No necesitas hacer nada especial para recibir pagos SAC en una cuenta Stellar: si un pagador realiza una transferencia exitosa mediante contrato, esos activos se añadirán automáticamente a tu cuenta.
-
-Sin embargo, puede que quieras monitorear los pagos SAC entrantes. Como los pagos SAC generan eventos de contrato en lugar de operaciones de pago tradicionales, necesitarás observar eventos del contrato en vez de usar flujos de pagos de Horizon. Aquí se muestra cómo puedes monitorear transferencias de contratos inteligentes entrantes:
-
-<CodeExample>
-
-```js
-import { Server } from "stellar-sdk/rpc";
-import { xdr, Asset, Networks, Address } from "stellar-sdk";
-
-// Initialize Soroban RPC server for testnet
-const rpc = new Server("https://soroban-testnet.stellar.org");
-
-// Get the native XLM contract ID for testnet
-const contractId = Asset.native().contractId(Networks.TESTNET);
-
-// The address we want to monitor for incoming payments
-const monitoredAddress = new Address(
-  "GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5"
-);
-
-// Paging state for event polling (similar to useSubscription hook)
-let lastLedgerStart: number | undefined;
-let pagingToken: string | undefined;
-
-async function pollForTransfers() {
-  // Set starting ledger if not set (get the latest ledger as starting point)
-  if (!lastLedgerStart) {
-    const latestLedger = await rpc.getLatestLedger();
-    lastLedgerStart = latestLedger.sequence;
-  }
-  console.log(`> Monitoring transfers for ledger: ${lastLedgerStart}`);
-
-  // Get events for "transfer" topic from the native asset contract
-  const response = await rpc.getEvents({
-    startLedger: !pagingToken ? lastLedgerStart : undefined,
-    cursor: pagingToken,
-    filters: [
-      {
-        contractIds: [contractId],
-        // Filter for transfer events to the monitored address
-        // Using wildcards (*) to match any sender and asset
-        // Event structure: ["transfer", fromAddress, toAddress, assetName]
-        topics: [
-          [
-            xdr.ScVal.scvSymbol("transfer").toXDR("base64"),
-            "*",
-            monitoredAddress.toScVal().toXDR("base64"),
-            "*",
-          ],
-        ],
-        type: "contract",
-      },
-    ],
-    limit: 10,
-  });
-
-  // Update paging tokens for next poll
-  pagingToken = undefined;
-  if (response.latestLedger) {
-    lastLedgerStart = response.latestLedger;
-  }
-
-  // Process events and check for payments to our monitored address
-  if (response.events) {
-    response.events.forEach((event) => {
-      try {
-        const topics = event.topic;
-        console.log(
-          `Processing event: ${event.txHash} at ledger ${event.ledger}`
-        );
-        if (topics && topics.length >= 3) {
-          // Extract recipient address from event topics
-          const toAddress = Address.fromScAddress(
-            topics[2].address()
-          ).toString();
-
-          // Check if the payment is to our monitored address
-          if (toAddress === monitoredAddress.toString()) {
-            console.log("PAYMENT RECEIVED!");
-            console.log(`  Transaction: ${event.txHash}`);
-            console.log(`  Ledger: ${event.ledger}`);
-            console.log(
-              `  Sender: ${Address.fromScAddress(
-                topics[1].address()
-              ).toString()}`
-            );
-            console.log(`  Amount: ${event.value.i128().lo().toBigInt()}`);
-          }
-        }
-      } catch (error) {
-        console.error("Error processing event:", error);
-      } finally {
-        // Update paging token for next poll
-        pagingToken = event.pagingToken;
-      }
-    });
-  }
-
-  // Continue polling after 4 seconds
-  setTimeout(pollForTransfers, 4000);
-}
-
-// Start monitoring for payment events
-console.log(`Starting payment monitor for: ${monitoredAddress}`);
-pollForTransfers();
-
-```
-
-</CodeExample>
-
-#### Desglose paso a paso
-
-¿Qué ocurrió exactamente en el ejemplo de recepción de pago SAC? Vamos a desglosarlo:
-
-1. Configura la conexión RPC y obtén el ID del contrato para el activo que quieres monitorear. Para XLM nativo, usamos el ID de contrato incorporado.
-
-<CodeExample>
-
-```js
-const rpc = new Server("https://soroban-testnet.stellar.org");
-const contractId = Asset.native().contractId(Networks.TESTNET);
-const monitoredAddress = new Address(
-  "GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5",
-);
-```
-
-</CodeExample>
-
-2. Inicializa el sistema de sondeo obteniendo la última secuencia del ledger como punto de partida para monitorear eventos.
-
-<CodeExample>
-
-```js
-if (!lastLedgerStart) {
-  const latestLedger = await rpc.getLatestLedger();
-  lastLedgerStart = latestLedger.sequence;
-}
-```
-
-</CodeExample>
-
-3. Consulta eventos de contratos usando filtros específicos para eventos de transferencia. El filtro apunta al ID del contrato y escucha eventos de "transfer" donde tu dirección es la destinataria. El arreglo topics define la estructura del evento: el primer elemento es el nombre del evento ("transfer"), el segundo es el emisor (comodín "_" para cualquier), el tercero es el receptor (tu dirección monitoreada), y el cuarto es el activo (comodín "_" para cualquier activo).
-
-<CodeExample>
-
-```js
-const response = await rpc.getEvents({
-  startLedger: !pagingToken ? lastLedgerStart : undefined,
-  cursor: pagingToken,
-  filters: [
-    {
-      contractIds: [contractId],
-      // Topics filter structure: ["event_name", "from_address", "to_address", "asset"]
-      // Using wildcards (*) allows matching any value in that position
-      topics: [
-        [
-          xdr.ScVal.scvSymbol("transfer").toXDR("base64"), // Event name: "transfer"
-          "*", // From: any address
-          monitoredAddress.toScVal().toXDR("base64"), // To: our monitored address
-          "*", // Asset: any asset
-        ],
-      ],
-      type: "contract",
-    },
-  ],
-  limit: 10,
-});
-```
-
-</CodeExample>
-
-4. Procesa los eventos extrayendo detalles de transferencia de los topics y valores del evento, luego continúa sondeando nuevos eventos después de una breve espera.
-
-<CodeExample>
-
-```js
-response.events.forEach((event) => {
-  const topics = event.topic;
-  if (topics && topics.length >= 3) {
-    const toAddress = Address.fromScAddress(topics[2].address()).toString();
-
-    if (toAddress === monitoredAddress.toString()) {
-      console.log("PAYMENT RECEIVED!");
-      console.log(`Amount: ${event.value.i128().lo().toBigInt()}`);
-    }
-  }
-});
-
-// Continue polling
-setTimeout(pollForTransfers, 4000);
-```
-
-</CodeExample>
-
-**Diferencias clave con el monitoreo clásico de pagos:**
-
-- **Basado en eventos**: Monitorea eventos de contratos en lugar de operaciones de pago
-- **Solo RPC**: Usa exclusivamente endpoints RPC, sin soporte Horizon
-- **Filtrado por topics**: Usa topics de eventos para filtrar patrones específicos de transferencia
-- **Sondeo activo**: Requiere sondeo continuo en vez de transmisión
-- **Estructura de eventos**: Extrae datos de pagos desde topics y valores de eventos de contrato en lugar de campos de operación
-
-## Transaccionar en Otras Monedas
-
-Una de las cosas sorprendentes de la red Stellar es que puedes crear, mantener, enviar, recibir e intercambiar cualquier tipo de activo. Muchas organizaciones emiten activos en Stellar que representan monedas del mundo real, como dólares estadounidenses o nairas nigerianas, o criptomonedas como bitcoin o ether.
-
-Cada uno de estos activos redimibles — _anclado_ en la jerga Stellar — es esencialmente un crédito emitido por una cuenta particular que representa las reservas que esas cuentas tienen fuera de la red. Por eso los activos en el ejemplo anterior tenían tanto un `código` como un `emisor`: el `emisor` es la clave pública de la cuenta que creó el activo, una cuenta propiedad de la organización que finalmente honra el crédito que representa ese activo. Además, con la introducción de contratos inteligentes, los activos clásicos pueden también ser representados por un `contract id` [(Interfaz SAC)](../../../tokens/stellar-asset-contract.mdx)) que permite interacciones más complejas e interoperabilidad con aplicaciones de contratos inteligentes.
-
-Otros tokens personalizados, desarrollados completamente con contratos inteligentes, también son representados por su propio `contract id` y deberían ofrecer una interfaz similar para la interacción al seguir la [interfaz de token](https://soroban.stellar.org/docs/reference/interfaces/token-interface).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/verify-trustlines.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/verify-trustlines.mdx
deleted file mode 100644
index 3668be0cdc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/verify-trustlines.mdx
+++ /dev/null
@@ -1,329 +0,0 @@
----
-title: Verificar Trustlines
-sidebar_position: 40
-description: Aprende a verificar trustlines antes de enviar transacciones a Stellar.
----
-
-Al realizar pagos en Stellar para [Activos Stellar](../../../tokens/README.mdx) que no sean XLM, es importante asegurarse de que la cuenta receptora tenga establecida una trustline para el activo que se envía. Esta página ofrece una visión rápida de cómo verificar los trustlines antes de enviar transacciones, asegurando que los pagos se procesen sin problemas y permitiendo que la aplicación maneje adecuadamente los casos en que los trustlines no estén establecidos o sean inválidos.
-
-## ¿Por qué verificar los trustlines?
-
-En Stellar, los trustlines se usan para establecer una relación entre una cuenta y un Activo Stellar. Indican que la cuenta está dispuesta a mantener y transaccionar con ese activo. Si no se establece un trustline para un activo, la cuenta no puede recibir pagos en ese activo, lo que conduce a fallos en la transacción.
-
-Además, los emisores de activos pueden aplicar requisitos específicos a través de los trustlines, como los saldos máximos que una cuenta puede mantener o autorizaciones granulares para recibir/enviar el activo o mantener responsabilidades. Consulta las [Consideraciones sobre el diseño de activos](../../../tokens/control-asset-access.mdx) para obtener más detalles sobre cómo se pueden usar los flags de control y las trustlines para personalizar estos comportamientos.
-
-Verificar los trustlines antes de enviar transacciones ayuda a asegurar que la cuenta receptora cumple con los requisitos y puede recibir el activo con éxito. Esto permite que la aplicación maneje casos donde los trustlines no estén establecidos o sean inválidos, brindando retroalimentación clara y una experiencia de usuario fluida mientras se previenen transacciones fallidas.
-
-## Verificar un Trustline a través del RPC de Stellar
-
-Para comprobar si existe un trustline para un activo específico, puedes usar la API RPC de Stellar para obtener directamente la entrada del ledger para el trustline y validar su estado. El siguiente fragmento de código demuestra cómo verificar si existe un trustline para un activo específico usando el método `getLedgerEntries` de la API RPC de Stellar:
-
-<CodeExample>
-
-```js
-import { Asset, StrKey, xdr } from "stellar-sdk";
-import { Server } from "stellar-sdk/rpc";
-
-// Initialize Soroban RPC server for testnet
-const rpc = new Server("https://soroban-testnet.stellar.org");
-
-// Define the receiver account ID
-// This is the account that will receive the payment and for which we will check the trustline.
-const receiver = "GCLNZP3WX3GG4D2HC3L2VVXNYBSVHO2OPGGTDQ4YGBQOUXHHTM3FSBNH";
-
-// First, check to make sure that the destination account exists.
-try {
-  await rpc.getAccount(receiver);
-} catch (error) {
-  console.error("Error checking destination account:", error);
-  throw error;
-}
-
-// Now we defined which asset we want to check the trustline for.
-// In this case, we are checking for USDC issued in testnet.
-const USDC = new Asset(
-  "USDC",
-  "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
-);
-
-// This is the amount we want to send.
-const sendingAmount = "1";
-
-// We then conver the receiver's public key to the XDR format.
-// This is necessary to create the ledger key for the trustline.
-const publicKeyXdr = xdr.PublicKey.publicKeyTypeEd25519(
-  StrKey.decodeEd25519PublicKey(receiver),
-);
-
-// Now we create the trustline ledger key using the public key and the asset.
-// The trustline ledger key is used to retrieve the trustline entry from the ledger.
-const trustlineKeyXdr = new xdr.LedgerKeyTrustLine({
-  accountId: publicKeyXdr,
-  asset: USDC.toTrustLineXDRObject(),
-});
-
-// We then create the ledger key based on the trustline key XDR.
-// This key is used to query the ledger for the trustline entry.
-// The ledger key is a unique identifier for the trustline in the Stellar network.
-// It combines the account ID and the asset to form a deterministic unique key for the trustline entry
-const key = xdr.LedgerKey.trustline(trustlineKeyXdr);
-
-// Now we query the ledger through the RPC for the trustline entry using the ledger key.
-// The `_getLedgerEntries` method retrieves the ledger entries for the specified key.
-// This will return the trustline entry if it exists, or an empty array if it does not.
-const response = await rpc._getLedgerEntries(key);
-
-// If the trustline entry is not found, we log an error and throw an exception.
-// This indicates that the account does not have a trustline set up for the specified asset.
-if (!response.entries || response.entries.length === 0) {
-  console.error(
-    `Trustline for asset ${USDC.code} issued by ${USDC.issuer} not found for account ${receiver}.`,
-  );
-  throw new Error("Trustline not found");
-}
-
-// If the trustline entry is found, we parse the XDR data from the response.
-// The response contains an array of entries, and we take the first one.
-// This is because we are querying for a specific trustline, so there should only be one entry.
-const ledgerData = response.entries[0];
-
-// We then convert the XDR data to a LedgerEntryData object.
-// This object contains the trustline data, which includes the asset, account ID, limit,
-// balance, and flags.
-const trustlineData = xdr.LedgerEntryData.fromXDR(
-  ledgerData.xdr,
-  "base64",
-).trustLine();
-
-// At this point, since the trustline is found, we check if it is authorized.
-// An authorized trustline means that the account is allowed to receive payments.
-// Here the authorization is indicated by the flags field in the trustline entry.
-if (trustlineData.flags() !== 1) {
-  console.error(
-    `Trustline for asset ${USDC.code} issued by ${USDC.issuer} is not authorized for account ${receiver}.`,
-  );
-  throw new Error("Trustline not authorized");
-}
-
-// Before checking the values, we parse the limit and balance from the
-// trustline data from stroops (1 XLM = 10,000,000 stroops).
-const limit = Number(trustlineData.limit().toBigInt()) / 10 ** 7;
-const balance = Number(trustlineData.balance().toBigInt()) / 10 ** 7;
-
-// Finally, we check if the trustline has enough limit to receive the payment.
-// We compare the trustline's limit minus its current balance with the amount we want to send.
-// Attempting to send an amount that exceeds the available limit will result in a failed transaction,
-// therefore, if the limit is insufficient, we log an error and throw an exception.
-if (limit - balance < parseFloat(sendingAmount)) {
-  console.error(
-    `Insufficient limit for asset ${USDC.code} issued by ${USDC.issuer} in account ${receiver}.`,
-  );
-  throw new Error("Insufficient limit for asset");
-}
-
-// If all checks pass, we log that the trustline is valid and ready for payment.
-console.log(
-  `Trustline for asset ${USDC.code} issued by ${USDC.issuer} is valid for account ${receiver}.`,
-);
-
-// Proceed with sending the payment...
-```
-
-</CodeExample>
-
-## Verificar un Trustline a través de la API Horizon
-
-Dada una dirección receptora, el siguiente fragmento de código muestra cómo comprobar si existe una trustline para un activo específico utilizando la API Horizon:
-
-<CodeExample>
-
-```js
-import * as StellarSdk from "stellar-sdk";
-
-// Initialize Horizon server for testnet
-const server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org"
-);
-
-// Define the receiver account ID
-// This is the account that will receive the payment and for which we will check the trustline.
-const receiver = "GCLNZP3WX3GG4D2HC3L2VVXNYBSVHO2OPGGTDQ4YGBQOUXHHTM3FSBNH";
-
-// First, check to make sure that the destination account exists.
-try {
-  await server.loadAccount(receiver);
-} catch (error) {
-  console.error("Error checking destination account:", error);
-  throw error;
-}
-
-// Now we defined which asset we want to check the trustline for.
-// In this case, we are checking for USDC issued in testnet.
-const assetCode = "USDC";
-const assetIssuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5";
-
-// This is the amount we want to send.
-const sendingAmount = "1";
-
-// We then load the account data for the receiver to check if the trustline exists.
-// This will also include other balances and trustlines for the account.
-const accountData = await server.accounts().accountId(receiver).call();
-
-// Now we check if the trustline for the specified asset exists in the account data.
-// We are looking for a trustline that matches the asset code and issuer.
-const trustline = accountData.balances.find(
-  (balance) =>
-    balance.asset_type === "credit_alphanum4" &&
-    balance.asset_code === assetCode &&
-    balance.asset_issuer === assetIssuer
-) as StellarSdk.Horizon.HorizonApi.BalanceLineAsset<StellarSdk.AssetType.credit4>;
-
-// If the trustline is not found, we log an error and throw an exception.
-// This indicates that the account does not have a trustline set up for the specified asset.
-if (!trustline) {
-  console.error(
-    `Trustline for asset ${assetCode} issued by ${assetIssuer} not found for account ${receiver}.`
-  );
-  throw new Error("Trustline not found");
-}
-
-// If the trustline is found, we check if it is authorized.
-// An authorized trustline means that the account is allowed to receive payments.
-if (trustline.is_authorized === false) {
-  console.error(
-    `Trustline for asset ${assetCode} issued by ${assetIssuer} is not authorized for account ${receiver}.`
-  );
-  throw new Error("Trustline not authorized");
-}
-
-// Finally, we check if the trustline has enough limit to receive the payment.
-// We compare the trustline's limit minus its current balance with the amount we want to send.
-// Attempting to send an amount that exceeds the available limit will result in a failed transaction,
-// therefore, if the limit is insufficient, we log an error and throw an exception.
-if (
-  Number(trustline.limit) - Number(trustline.balance) <
-  parseFloat(sendingAmount)
-) {
-  console.error(
-    `Insufficient limit for asset ${assetCode} issued by ${assetIssuer} in account ${receiver}.`
-  );
-  throw new Error("Insufficient limit for asset");
-}
-
-// If all checks pass, we log that the trustline is valid and ready for payment.
-console.log(
-  `Trustline for asset ${assetCode} issued by ${assetIssuer} is valid for account ${receiver}.`
-);
-
-// Proceed with sending the payment...
-```
-
-</CodeExample>
-
-## Verificar un Trustline a través del Stellar Asset Contract (SAC)
-
-Todos los activos Stellar, incluido el activo nativo (XLM), pueden ser gestionados con transacciones de contratos inteligentes mediante Stellar Asset Contracts (SAC). Los SACs proporcionan una interfaz de contrato inteligente para manejar activos, permitiendo interacciones más complejas y programabilidad. Esto significa que incluyen ciertas funciones para ayudar a los desarrolladores a gestionar activos, como verificar trustlines y enviar pagos, de una forma más flexible que las operaciones clásicas.
-
-Para este ejemplo, usaremos SAC como interfaz de contrato inteligente para el activo USDC en testnet. Se hará una transacción de invocación de contrato para llamar a la función `authorized`, que verifica si existe un trustline para una cuenta dada y devuelve un booleano que indica si el trustline está autorizado.
-
-Esta función puede ser accedida directamente en una invocación de contrato inteligente como demuestra el ejemplo a continuación, o también puede ser invocada por otro contrato, permitiendo construir interacciones más complejas y programabilidad en contratos inteligentes.
-
-:::info
-
-Para usar el ejemplo RPC que aparece a continuación, primero debes generar los enlaces del contrato para que el cliente pueda utilizarse correctamente. Esto se puede lograr mediante el [Stellar CLI](../../../tools/cli/README.mdx).
-
-Por ejemplo: Generando los bindings en TypeScript para el contrato `sac` de un activo dado:
-
-```bash
- stellar contract bindings typescript --network=testnet --contract-id=CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA --output-dir=./bindings
-```
-
-:::
-
-Dada una dirección receptora, el siguiente fragmento de código demuestra cómo simular una transacción para verificar si existe un trustline para un activo específico:
-
-<CodeExample>
-
-```js
-import { Asset, Networks } from "stellar-sdk";
-import { Client } from "sac";
-import { Server } from "stellar-sdk/rpc";
-
-// Initialize Soroban RPC server for testnet
-const rpc = new Server("https://soroban-testnet.stellar.org");
-
-// Define the receiver account ID
-// This is the account that will receive the payment and for which we will check the trustline.
-const receiver = "GCLNZP3WX3GG4D2HC3L2VVXNYBSVHO2OPGGTDQ4YGBQOUXHHTM3FSBNH";
-
-// First, check to make sure that the destination account exists.
-try {
-  await rpc.getAccount(receiver);
-} catch (error) {
-  console.error("Error checking destination account:", error);
-  throw error;
-}
-
-// Now we defined which asset we want to check the trustline for.
-// In this case, we are checking for USDC issued in testnet.
-const USDC = new Asset(
-  "USDC",
-  "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
-);
-
-// Now we initialize the Stellar Asset Contract (SAC) client.
-// The client needs the RPC endpoint, network passphrase, contract ID for the asset,
-// and your account's public key. Since we are only going to simulate the transaction,
-// we do not need to provide a signing function.
-const usdcClient = new Client({
-  rpcUrl: "https://soroban-testnet.stellar.org",
-  networkPassphrase: Networks.TESTNET,
-  contractId: USDC.contractId(Networks.TESTNET),
-  publicKey: receiver,
-});
-
-// Now, using the client, we assemble a soroban transaction to invoke the transfer
-// function of the USDC asset contract. The cient will automatically
-// bundle the operation and simulate the transaction before providing us
-// with an assembled transaction object. This object contains the result of the simulation,
-// which we can check to see if the trustline is authorized or not.
-let assembledTx;
-try {
-  assembledTx = await usdcClient.authorized({
-    id: receiver,
-  });
-
-  // The result parameter contains the return value of the contract function.
-  // If the trustline is authorized, it will return true; otherwise, it will return false.
-  const result = assembledTx.result;
-
-  // If the trustline is not authorized, we log an error and throw an exception.
-  // This indicates that the account does not have a trustline set up for the specified asset and
-  // any attempt to send USDC to this account will fail.
-  if (result === false) {
-    console.error(
-      `Trustline for asset ${USDC.code} issued by ${USDC.issuer} not authorized for account ${receiver}.`,
-    );
-    throw new Error("Trustline not authorized");
-  }
-
-  // If the trustline is authorized, we log a success message.
-  // This means that the account is allowed to receive payments in USDC.
-  console.log(
-    `Trustline for asset ${USDC.code} issued by ${USDC.issuer} is authorized for account ${receiver}.`,
-  );
-
-  // assembledTx = await xlmClient.transfer({
-  //   to: destinationId,
-  //   amount: BigInt(10_0000000), // Amount in stroops (1 XLM = 10,000,000 stroops)
-  //   from: sourceKeys.publicKey(),
-  // });
-} catch (error) {
-  console.error("Error assembling and simulating the transaction:", error);
-  throw error;
-}
-
-// If the trustline is authorized, we can proceed with sending the payment...
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/README.mdx
deleted file mode 100644
index 841595784f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Stellar CLI
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 95
----
-
-El [Stellar CLI] es una herramienta crucial para que los desarrolladores la utilicen mientras crean e interactúan con contratos inteligentes de Stellar.
-
-[stellar cli]: ../../../tools/cli/stellar-cli.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/asset-management.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/asset-management.mdx
deleted file mode 100644
index debcc6b6a3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/asset-management.mdx
+++ /dev/null
@@ -1,291 +0,0 @@
----
-title: Gestión de activos
-hide_table_of_contents: false
-description: Emitir un Activo Stellar, desplegar su contrato, y acuñar, quemar, congelar y recuperar.
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/asset-management.mdx
----
-
-El [stellar-cli] puede usarse para emitir y administrar activos en la red Stellar.
-
-La siguiente guía asume que el [stellar-cli] ha sido configurado para usar testnet o una red de prueba local. Para usar testnet, ejecuta el siguiente comando.
-
-```bash
-stellar network use testnet
-```
-
-### Emisión de activos
-
-Para crear un Activo Stellar usando el [stellar-cli], se realizan varios pasos:
-
-- Debe existir una cuenta emisora.
-- Se selecciona un código de activo.
-- Opcionalmente, se configura un administrador.
-
-#### Creación del emisor
-
-Para crear un emisor, genera una clave y fúndala. El funding usa friendbot, la fuente de testnet, y solo está disponible en testnet.
-
-```bash
-stellar keys generate issuer
-```
-
-```bash
-stellar keys fund issuer
-```
-
-Visualiza la clave pública con:
-
-```bash
-stellar keys public-key issuer
-```
-
-Configura la clave del emisor que se usará para firmar transacciones:
-
-```bash
-stellar keys use issuer
-```
-
-#### Configuración del emisor
-
-Las cuentas emisoras tienen varias flags de configuración que pueden activarse o desactivarse y afectan todos los activos emitidos por el emisor.
-
-En esta guía, la cuenta del emisor se configurará con las funciones revocables y habilitadas para clawback. Estas funciones permiten que el administrador del activo revoque la autorización para usar un activo, lo que tiene el efecto de congelar su saldo, y que recupere, lo que tiene el efecto de quemar forzosamente el activo.
-
-```bash
-stellar tx new set-options \
-  --set-revocable \
-  --set-clawback-enabled
-```
-
-Para otras opciones, consulta el manual del comando [stellar tx new set-options].
-
-Para ver la transacción antes de enviarla, usa la opción `--build-only` y pasa la transacción por el comando tx edit:
-
-```bash cookbooktest.ignore="because piping isn't supported"
-stellar tx new set-options \
-  --set-revocable \
-  --set-clawback-enabled \
-  --build-only \
-  | stellar tx edit \
-  | stellar sign \
-  | stellar send
-```
-
-#### Elección del código de activo
-
-Elige un código de activo de 1 a 12 caracteres.
-
-El código de activo junto con la dirección de la cuenta emisora identificarán de forma única al activo. Un emisor puede emitir múltiples activos, diferenciados por su código de activo.
-
-Para el resto de esta guía se usará el código de activo `ABC`.
-
-#### Configuración del contrato de activo
-
-Existe un contrato integrado en la red para cada activo. Su dirección está reservada y puede calcularse usando el siguiente comando.
-
-```bash
-stellar contract asset id --asset ABC:issuer
-```
-
-El contrato no se despliega automáticamente. Cualquiera puede desplegar el contrato, no es una acción que requiera autorización.
-
-##### Despliegue del contrato
-
-Despliega el contrato de activo incorporado.
-
-La opción `--asset` especifica el nombre del activo, que tiene el formato `<asset-code>:<asset-issuer>`.
-
-La opción `--alias` almacena localmente un alias que puede usarse en comandos posteriores para referenciar la dirección del contrato.
-
-```bash
-stellar contract asset deploy --asset ABC:issuer --alias mycontract
-```
-
-Ejecuta el siguiente comando para obtener algunos datos de solo lectura del contrato y confirmar que está desplegado.
-
-```bash
-stellar contract invoke --id mycontract -- name
-```
-
-##### Configuración del administrador
-
-En este punto, el emisor es el administrador del contrato. Creemos otra cuenta que será el administrador.
-
-```bash
-stellar keys generate admin
-```
-
-```bash
-stellar keys public-key admin
-```
-
-```bash
-stellar keys fund admin
-```
-
-Usando la cuenta del emisor, invoca la función `set_admin` del contrato del activo.
-
-```bash
-stellar keys use issuer
-```
-
-```bash
-stellar contract invoke --source issuer --id mycontract -- set_admin --new_admin admin
-```
-
-### Acciones
-
-Una vez que el contrato de activo está desplegado y configurado, pueden efectuarse las siguientes acciones.
-
-#### Acuñar (Solo admin)
-
-Genera y financia una cuenta de usuario a la que se transferirá el activo acuñado.
-
-```bash
-stellar keys generate user
-```
-
-```bash
-stellar keys fund user
-```
-
-```bash
-stellar keys public-key user
-```
-
-Usando la cuenta de usuario, confía en el activo para que la cuenta pueda tenerlo.
-
-```bash
-stellar keys use user
-```
-
-```bash
-stellar tx new change-trust --line ABC:issuer
-```
-
-Para acuñar el activo al usuario, usa la cuenta de administrador e invoca la función `mint` del contrato del activo.
-
-```bash
-stellar keys use admin
-```
-
-```bash
-stellar contract invoke --id mycontract -- mint --to user --amount 25
-```
-
-Verifica el saldo después de acuñar.
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user
-```
-
-#### Transferir
-
-Genera y financia una segunda cuenta de usuario a la que la cuenta del usuario anterior puede transferir el activo.
-
-```bash
-stellar keys generate user2
-```
-
-```bash
-stellar keys fund user2
-```
-
-```bash
-stellar keys public-key user2
-```
-
-Usando la cuenta user2, confía en el activo para que la nueva cuenta pueda tenerlo.
-
-```bash
-stellar keys use user2
-```
-
-```bash
-stellar tx new change-trust --line ABC:issuer
-```
-
-Usando la cuenta de usuario, invoca la función `transfer` del contrato del activo.
-
-```bash
-stellar keys use user
-```
-
-```bash
-stellar contract invoke --id mycontract -- transfer --from user --to user2 --amount 3
-```
-
-Revisa los saldos después de la transferencia.
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user
-```
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user2
-```
-
-#### Quemar
-
-Usando la cuenta de usuario, invoca la función `burn` del contrato del activo.
-
-```bash
-stellar keys use user
-```
-
-```bash
-stellar contract invoke --id mycontract -- burn --from user --amount 5
-```
-
-Verifica el saldo después de quemar.
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user
-```
-
-#### Revocar autorización / Congelar (Solo admin)
-
-Un administrador puede revocar la autorización de un usuario para usar el activo. El usuario seguirá teniendo el saldo pero no podrá transferirlo ni crear nuevos pagos. Cualquier responsabilidad existente, como las creadas por ofertas en Stellar, continuará existiendo y puede seguir ejecutándose.
-
-Usando el admin, invoca la función `set_authorized` del contrato del activo.
-
-```bash
-stellar keys use admin
-```
-
-```bash
-stellar contract invoke --id mycontract -- set_authorized --id user --authorize false
-```
-
-Usando la cuenta de usuario, invoca la función `transfer` del contrato del activo. La invocación fallará porque ya no está autorizado para transferir.
-
-```bash
-stellar keys use user
-```
-
-```bash cookbooktest.fail cookbooktest.stderr="balance is deauthorized"
-stellar contract invoke --id mycontract -- transfer --from user --to user2 --amount 3
-```
-
-#### Recuperar (Solo admin)
-
-Un administrador puede recuperar el saldo de un usuario. La cantidad recuperada será quemada.
-
-Usando el admin, invoca la función `clawback` del contrato del activo.
-
-```bash
-stellar keys use admin
-```
-
-```bash
-stellar contract invoke --id mycontract -- clawback --from user --amount 1
-```
-
-Verifica el saldo después de la recuperación.
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user
-```
-
-[stellar-cli]: https://developers.stellar.org/docs/tools/cli
-[stellar tx new set-options]: https://developers.stellar.org/docs/tools/cli/stellar-cli#stellar-tx-new-set-options
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/contract-lifecycle.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/contract-lifecycle.mdx
deleted file mode 100644
index b23d8ca67e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/contract-lifecycle.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Ciclo de Vida del Contrato
-hide_table_of_contents: true
-description: Gestionar el ciclo de vida de un contrato inteligente Stellar utilizando la CLI
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/contract-lifecycle.mdx
----
-
-Para gestionar el ciclo de vida de un contrato inteligente de Stellar utilizando el CLI, sigue estos pasos:
-
-1. Configura tu red preferida. En esta guía, usaremos `testnet`. Una lista de redes disponibles se encuentra [aquí](https://developers.stellar.org/docs/networks)
-
-```bash
-stellar network use testnet
-```
-
-2. Crea una identidad para Alice:
-
-```bash
-stellar keys generate alice -q
-```
-
-3. Financia la identidad:
-
-```bash
-stellar keys fund alice
-```
-
-4. Despliega un contrato:
-
-```bash
-stellar keys use alice
-```
-
-```bash
-stellar contract deploy --wasm /path/to/contract.wasm --alias mycontract
-```
-
-Esto mostrará el ID del contrato resultante, p. ej.:
-
-```
-CBB65ZLBQBZL5IYHDHEEPCVUUMFOQUZSQKAJFV36R7TZETCLWGFTRLOQ
-```
-
-Para aprender más sobre cómo crear archivos de contrato `.wasm`, echa un vistazo a nuestro [tutorial para comenzar](https://developers.stellar.org/docs/build/smart-contracts/getting-started/setup).
-
-5. Invoca una función del contrato:
-
-```bash
-stellar contract invoke --id mycontract -- <FUNCTION>
-```
-
-6. Ve el estado del contrato:
-
-```bash
-stellar contract read --id mycontract --durability <DURABILITY> --key <KEY>
-```
-
-Nota: `<DURABILITY>` es `persistente` o `temporal`. `KEY` proporciona la clave de la entrada de almacenamiento que se está leyendo.
-
-7. Gestiona estados caducados:
-
-```bash
-stellar contract extend --id mycontract --ledgers-to-extend 1000 --durability <DURABILITY> --key <KEY>
-```
-
-Esto extiende el estado de la instancia proporcionada por la clave dada a al menos 1000 ledgers desde el ledger actual.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/deploy-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/deploy-contract.mdx
deleted file mode 100644
index 6bffe6d47a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/deploy-contract.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Desplegar un contrato a partir de bytecode Wasm instalado
-hide_table_of_contents: true
-description: Desplegar una instancia de un contrato compilado que ya está instalado en la red
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/deploy-contract.mdx
----
-
-Para desplegar una instancia de un contrato inteligente compilado que ya ha sido instalado en la red Stellar, utiliza el comando `stellar contract deploy`:
-
-```bash
-stellar contract deploy \
-    --source S... \
-    --network testnet \
-    --wasm-hash <hex-encoded-wasm-hash> \
-    --alias <alias>
-```
-
-:::tip Opcionalmente asigna un alias reemplazando `<alias>` con el nombre de alias que desees para el contrato. El alias es un mapeo almacenado localmente a la dirección del contrato, y puede usarse en otros comandos de stellar-cli en lugar de la dirección. :::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/deploy-stellar-asset-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/deploy-stellar-asset-contract.mdx
deleted file mode 100644
index 3b905c4569..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/deploy-stellar-asset-contract.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Desplegar el Contrato de Activo Stellar para un activo Stellar
-hide_table_of_contents: true
-description: Desplegar un SAC para un activo Stellar para que pueda interactuar con contratos inteligentes
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/deploy-stellar-asset-contract.mdx
----
-
-El CLI de Stellar puede desplegar un [Contrato de Activo Stellar] para un activo Stellar de manera que cualquier contrato inteligente Stellar pueda interactuar con el activo.
-
-Cada activo Stellar tiene reservado un contrato que cualquiera puede desplegar. Una vez desplegado, cualquier contrato puede interactuar con ese activo al mantener un saldo del activo, recibir el activo o enviar el activo.
-
-Desplegar el Contrato de Activo Stellar para un activo Stellar habilita dicho activo para su uso en contratos inteligentes.
-
-El Contrato de Activo Stellar puede ser desplegado para cualquier activo Stellar posible, ya sea activos que ya estén en uso en Stellar o activos que nunca hayan tenido ninguna actividad. Esto significa que el emisor no necesita haber sido creado, y nadie necesita estar aún en posesión del activo en Stellar.
-
-Para realizar el despliegue, usa el siguiente comando:
-
-```bash cookbooktest.ignore
-stellar contract asset deploy \
-    --source S... \
-    --network testnet \
-    --asset USDC:GCYEIQEWOCTTSA72VPZ6LYIZIK4W4KNGJR72UADIXUXG45VDFRVCQTYE
-```
-
-El argumento `asset` corresponde al símbolo y la dirección de su emisor, que es cómo se identifican los activos en Stellar.
-
-Lo mismo puede hacerse para el activo nativo [Lumens]:
-
-```bash cookbooktest.fail cookbooktest.stderr="contract already exists"
-stellar contract asset deploy \
-    --source S... \
-    --network testnet \
-    --asset native
-```
-
-:::note
-
-Desplegar el activo nativo fallará en testnet o mainnet, ya que ya existe un Contrato de Activo Stellar.
-
-:::
-
-Para cualquier activo, la dirección del contrato se puede obtener con:
-
-```bash
-stellar contract id asset \
-    --network testnet \
-    --asset native
-```
-
-[contrato de activo stellar]: ../../../tokens/stellar-asset-contract.mdx
-[lumens]: ../../../learn/fundamentals/lumens.mdx
-[sep-41]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md
-[`soroban_sdk::token`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/
-[`token::tokenclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.TokenClient.html
-[`token::stellarassetclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.StellarAssetClient.html
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-instance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-instance.mdx
deleted file mode 100644
index ac56b74601..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-instance.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Extender el TTL de una instancia de contrato desplegada
-hide_table_of_contents: true
-description: Usar el CLI para extender el tiempo de vida (TTL) de una instancia de contrato
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-instance.mdx
----
-
-Puedes usar el Stellar CLI para extender el TTL de una instancia de contrato así:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-Este ejemplo utiliza 535.679 ledgers como el nuevo TTL de archivo. Este es el valor máximo permitido para este argumento en el CLI. Esto corresponde a aproximadamente 30 días (promediando tiempos de cierre de ledger de 5 segundos).
-
-Cuando extiendes una instancia de contrato, esto incluye:
-
-- la instancia de contrato en sí
-- cualquier entrada `env.storage().instance()` en el contrato
-- el código Wasm del contrato
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-storage.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-storage.mdx
deleted file mode 100644
index 431ddeb2d6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-storage.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Extender el TTL de la entrada de almacenamiento de un contrato desplegado
-hide_table_of_contents: true
-description: Usar la CLI para extender el tiempo de vida (TTL) de la entrada de almacenamiento persistente de un contrato
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-storage.mdx
----
-
-Puedes usar el CLI de Stellar para extender el TTL de la entrada de almacenamiento persistente de un contrato. Para una entrada de almacenamiento que utiliza un `Symbol` simple como su clave de almacenamiento, puedes ejecutar un comando así:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --key COUNTER \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-Este ejemplo utiliza 535.679 ledgers como el nuevo TTL de archivo. Este es el valor máximo permitido para este argumento en el CLI. Esto corresponde a aproximadamente 30 días (promediando 5 segundos de tiempo de cierre de ledger).
-
-Si tu entrada de almacenamiento utiliza una clave de almacenamiento más avanzada, como `Balance(Address)` en un contrato de token, necesitarás proporcionar la clave en un formato XDR codificado en base64:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --key-xdr AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAA4AAAAHQmFsYW5jZQAAAAAB \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-:::info
-
-Asegúrate de consultar nuestra [guía sobre cómo crear claves de ledger XDR](../rpc/generate-ledger-keys-python.mdx) para obtener ayuda generándolas.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-wasm.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-wasm.mdx
deleted file mode 100644
index f3bb59758c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/extend-contract-wasm.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Extender el TTL del código Wasm de un contrato desplegado
-hide_table_of_contents: true
-description: Usar Stellar CLI para extender el TTL del bytecode Wasm del contrato, con o sin binario local
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-wasm.mdx
----
-
-Puedes usar el Stellar CLI para extender el TTL del bytecode Wasm de un contrato. Esto se puede hacer de dos formas: si tienes o no el contrato compilado localmente. Si tienes el binario compilado en tu máquina local:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --wasm ../relative/path/to/soroban_contract.wasm \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-Este ejemplo utiliza 535.679 ledgers como el nuevo TTL de archivo. Este es el valor máximo permitido para este argumento en el CLI. Esto corresponde a aproximadamente 30 días (promediando 5 segundos de tiempo de cierre del ledger).
-
-Si no tienes el binario compilado en tu máquina local, aún puedes usar el CLI para extender el TTL del bytecode. Necesitarás conocer el hash Wasm del código del contrato instalado:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --wasm-hash <hex-encoded-wasm-hash> \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-:::info
-
-Puedes aprender más sobre cómo encontrar el hash Wasm correcto para una instancia de contrato [aquí (JavaScript)](../rpc/retrieve-contract-code-js.mdx) y [aquí (Python)](../rpc/retrieve-contract-code-python.mdx).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/install-deploy.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/install-deploy.mdx
deleted file mode 100644
index 4d05f325dd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/install-deploy.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Instalar y desplegar un contrato inteligente
-hide_table_of_contents: true
-description: Combina los comandos de instalar y desplegar en la Stellar CLI para realizar ambas tareas
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/install-deploy.mdx
----
-
-Puedes combinar los comandos `install` y `deploy` del Stellar CLI para realizar ambas tareas:
-
-```bash
-stellar contract deploy \
-    --source S... \
-    --network testnet \
-    --wasm ../relative/path/to/soroban_contract.wasm
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/install-wasm.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/install-wasm.mdx
deleted file mode 100644
index 4c4f230f79..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/install-wasm.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Subir bytecode Wasm
-hide_table_of_contents: true
-description: Usa el CLI de Stellar para subir un contrato inteligente compilado al ledger
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/install-wasm.mdx
----
-
-Para usar el CLI de Stellar y subir un contrato inteligente compilado al ledger, usa el comando `stellar contract upload`:
-
-```bash
-stellar contract upload \
-    --source S... \
-    --network testnet \
-    --wasm ../relative/path/to/soroban_contract.wasm
-```
-
-:::note
-
-Nota que este comando devolverá el ID de hash del bytecode Wasm, en lugar de una dirección para una instancia de contrato.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/payments-and-assets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/payments-and-assets.mdx
deleted file mode 100644
index e70dabb056..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/payments-and-assets.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Pagos y Activos
-hide_table_of_contents: true
-description: Envía XLM, stellar classic o un activo soroban usando el CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/payments-and-assets.mdx
----
-
-Para enviar pagos y trabajar con activos utilizando el Stellar CLI, sigue estos pasos:
-
-1. Establece tu red preferida. Para esta guía, usaremos `testnet`. Una lista de redes disponibles se puede encontrar [aquí](https://developers.stellar.org/docs/networks)
-
-```bash
-stellar network use testnet
-```
-
-2. Fondea las cuentas:
-
-```bash
-stellar keys generate alice
-```
-
-```bash
-stellar keys fund alice
-```
-
-```bash
-stellar keys generate bob
-```
-
-```bash
-stellar keys fund bob
-```
-
-3. Obtén el ID de contrato de activo stellar:
-
-```bash
-stellar contract id asset --asset native
-```
-
-4. Consigue la clave pública de Bob:
-
-```bash
-stellar keys address bob
-```
-
-5. Envía 100 XLM de Alice a Bob:
-
-```bash
-stellar keys use alice
-```
-
-```bash
-stellar contract invoke --id <ASSET_CONTRACT_ID> -- transfer --to bob --from alice --amount 100
-```
-
-6. Verifica el saldo de la cuenta:
-
-```bash
-stellar contract invoke --id <ASSET_CONTRACT_ID> -- balance --id bob
-```
-
-Para más información sobre las funciones disponibles en el contrato de activo stellar, consulta el [código de interfaz de token](https://developers.stellar.org/docs/tokens/token-interface#code).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/restore-contract-instance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/restore-contract-instance.mdx
deleted file mode 100644
index 437d4c026a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/restore-contract-instance.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Restaurar un contrato archivado usando el CLI de Stellar
-hide_table_of_contents: true
-description: Restaurar una instancia de contrato archivada usando el CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/restore-contract-instance.mdx
----
-
-Si tu instancia de contrato ha sido archivada, se puede restaurar fácilmente usando el CLI de Stellar.
-
-```bash
-stellar contract restore \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --durability persistent
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/restore-contract-storage.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/restore-contract-storage.mdx
deleted file mode 100644
index f8044e1fe8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/restore-contract-storage.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Restaurar datos de contrato archivados utilizando el CLI de Stellar
-hide_table_of_contents: true
-description: Restaurar entradas de almacenamiento de contrato archivadas utilizando el CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/restore-contract-storage.mdx
----
-
-Si la entrada de almacenamiento persistente de un contrato ha sido archivada, puedes restaurarla utilizando el CLI de Stellar. Para una entrada de almacenamiento que utiliza un `Symbol` simple como su clave de almacenamiento, puedes ejecutar un comando así:
-
-```bash
-stellar contract restore \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --key COUNTER \
-    --durability persistent
-```
-
-Si tu entrada de almacenamiento utiliza una clave de almacenamiento más avanzada, como `Balance(Address)` en un contrato de token, necesitarás proporcionar la clave en un formato XDR codificado en base64:
-
-```bash
-stellar contract restore \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --key-xdr AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAA4AAAAHQmFsYW5jZQAAAAAB \
-    --durability persistent
-```
-
-:::info
-
-Asegúrate de consultar nuestra [guía sobre cómo crear claves de ledger en XDR](../rpc/generate-ledger-keys-python.mdx) para obtener ayuda para generarlas.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-new-create-claimable-balance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-new-create-claimable-balance.mdx
deleted file mode 100644
index 91190c05ec..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-new-create-claimable-balance.mdx
+++ /dev/null
@@ -1,248 +0,0 @@
----
-title: Crear saldo reclamable
-hide_table_of_contents: true
-description: Crear saldos reclamables con varios predicados de reclamación usando la CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-new-create-claimable-balance.mdx
----
-
-Los saldos reclamables te permiten enviar pagos que el destinatario puede reclamar bajo condiciones específicas. Esto es útil para funciones similares a escrow, pagos condicionales o transferencias bloqueadas por tiempo.
-
-## Configuración
-
-Para los siguientes ejemplos usaremos estas cuentas:
-
-```bash
-stellar network use testnet
-```
-
-```bash
-stellar keys generate --fund alice
-```
-
-```bash
-stellar keys generate bob --fund
-```
-
-```bash
-stellar keys generate charlie --fund
-```
-
-## Ejemplos básicos
-
-### Saldo reclamable incondicional
-
-Crear un saldo reclamable que el destinatario pueda reclamar inmediatamente:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 50_000_000 \
-  --asset native \
-  --claimant bob
-```
-
-También puedes especificar explícitamente incondicional:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 50_000_000 \
-  --asset native \
-  --claimant 'bob:"unconditional"'
-```
-
-### Múltiples reclamantes
-
-Crear un saldo reclamable que pueda ser reclamado por cualquiera de varios destinatarios:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 75_000_000 \
-  --asset native \
-  --claimant bob \
-  --claimant charlie
-```
-
-## Predicados basados en tiempo
-
-### Antes de un tiempo absoluto
-
-Crear un saldo reclamable que debe ser reclamado antes de una fecha específica:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 30_000_000 \
-  --asset native \
-  --claimant 'bob:{"before_absolute_time":"1735689599"}'
-```
-
-### Antes de un tiempo relativo
-
-Crear un saldo reclamable que debe reclamarse dentro de 1 hora (3600 segundos) desde su creación:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 25_000_000 \
-  --asset native \
-  --claimant 'bob:{"before_relative_time":"3600"}'
-```
-
-## Predicados lógicos
-
-### Predicado Not
-
-Crear un saldo reclamable que puede ser reclamado después de cierto tiempo (NO antes de un tiempo relativo):
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 40_000_000 \
-  --asset native \
-  --claimant 'bob:{"not":{"before_relative_time":"7200"}}'
-```
-
-Esto significa: "Puede ser reclamado, PERO NO antes de que hayan pasado 2 horas" (efectivamente: puede ser reclamado después de 2 horas).
-
-### Predicado And
-
-Crear un saldo reclamable con múltiples condiciones que TODAS deben ser verdaderas:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 60_000_000 \
-  --asset native \
-  --claimant 'bob:{"and":[{"before_absolute_time":"1735689599"},{"not":{"before_relative_time":"86400"}}]}'
-```
-
-Esto significa: "Puede ser reclamado antes del 31 de diciembre de 2024 Y después de que haya pasado 1 día".
-
-### Predicado Or
-
-Crear un saldo reclamable donde cualquiera de las condiciones puede ser verdadera:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 35_000_000 \
-  --asset native \
-  --claimant 'bob:{"or":[{"before_relative_time":"3600"},{"not":{"before_absolute_time":"1717200000"}}]}'
-```
-
-Esto significa: "Puede ser reclamado dentro de 1 hora O después del 1 de junio de 2024".
-
-## Ejemplos complejos
-
-### Reclamantes mixtos con diferentes predicados
-
-Crear un saldo reclamable con múltiples reclamantes que tienen diferentes condiciones de reclamación:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 100_000_000 \
-  --asset native \
-  --claimant 'bob:{"before_relative_time":"3600"}' \
-  --claimant 'charlie:{"not":{"before_relative_time":"86400"}}'
-```
-
-Esto crea un saldo donde:
-
-- Bob puede reclamar dentro de 1 hora
-- Charlie puede reclamar después de que haya pasado 1 día
-
-### Pago estilo escrow
-
-Crear un escrow donde el destinatario tiene 30 días para reclamar, de lo contrario regresa al remitente:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 200_000_000 \
-  --asset native \
-  --claimant 'bob:{"before_relative_time":"2592000"}' \
-  --claimant 'alice:{"not":{"before_relative_time":"2592000"}}'
-```
-
-Esto significa:
-
-- Bob puede reclamar dentro de 30 días
-- Alice puede recuperar después de 30 días si Bob no ha reclamado
-
-### Saldo reclamable de activo personalizado
-
-Crear un saldo reclamable para un activo personalizado:
-
-```bash cookbooktest.ignore
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 1000_000_000 \
-  --asset USDC:GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
-  --claimant 'bob:{"before_absolute_time":"1735689599"}'
-```
-
-## Comprendiendo los predicados
-
-**Nota**: Los predicados deben ser JSON válido, por lo que debes usar comillas y escape adecuados.
-
-### Tipos de predicados
-
-| Tipo                   | Descripción                                             | Ejemplo                                 |
-| ---------------------- | ------------------------------------------------------- | --------------------------------------- |
-| `unconditional`        | Puede ser reclamado en cualquier momento                | `"unconditional"`                       |
-| `before_absolute_time` | Debe reclamarse antes de una marca de tiempo específica | `{"before_absolute_time":"1735689599"}` |
-| `before_relative_time` | Debe reclamarse dentro de X segundos desde la creación  | `{"before_relative_time":"3600"}`       |
-| `not`                  | Niega otro predicado                                    | `{"not":{...}}`                         |
-| `and`                  | Ambos predicados deben ser verdaderos                   | `{"and":[{...},{...}]}`                 |
-| `or`                   | Cualquiera de los predicados puede ser verdadero        | `{"or":[{...},{...}]}`                  |
-
-### Notas sobre el formato de tiempo
-
-- **Tiempos absolutos**: Usa marcas de tiempo Unix (segundos desde epoch)
-- **Tiempos relativos**: Segundos desde el tiempo de creación del saldo reclamable
-- **Marcas de tiempo**: Deben estar en el futuro al crear el saldo
-
-## Casos de uso comunes
-
-### 1. Pago simple con fecha límite
-
-```bash
-# Bob has 7 days to claim
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 50_000_000 \
-  --claimant 'bob:{"before_relative_time":"604800"}'
-```
-
-### 2. Pago retrasado
-
-```bash
-# Bob can only claim after 1 day
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 100_000_000 \
-  --claimant 'bob:{"not":{"before_relative_time":"86400"}}'
-```
-
-### 3. Fondo de emergencia
-
-```bash
-# Bob can claim immediately, but if he doesn't claim within 48 hours, Alice can reclaim
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 500_000_000 \
-  --claimant 'bob:{"before_relative_time":"172800"}' \
-  --claimant 'alice:{"not":{"before_relative_time":"172800"}}'
-```
-
-## Notas
-
-- `--amount`: Cantidad en stroops (1 XLM = 10,000,000 stroops)
-- `--asset`: Usa "native" para XLM o el formato "CODE:ISSUER" para otros activos
-- `--claimant`: Cuenta con predicado opcional (puede especificarse varias veces)
-- Los predicados se evalúan cuando se reclama el saldo reclamable, no al crearlo
-- Los predicados `And` y `Or` deben tener exactamente 2 subpredicados
-- Los predicados complejos pueden anidarse para crear condiciones sofisticadas de reclamación
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-new.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-new.mdx
deleted file mode 100644
index 61bf8dc7af..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-new.mdx
+++ /dev/null
@@ -1,193 +0,0 @@
----
-title: Comandos tx
-hide_table_of_contents: true
-description: Crear transacciones Stellar utilizando el CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-new.mdx
----
-
-Hasta ahora, los ejemplos del CLI interactuando con la blockchain han sido a través del comando `contract`. Subir contratos, desplegar contratos e invocarlos. Cada uno de estos son diferentes tipos de transacciones, que deben ser firmadas y enviadas a la red (y en el caso de las transacciones relacionadas con contratos, simuladas primero).
-
-Técnicamente, estas tres son diferentes operaciones, de las cuales una transacción puede contener hasta 100 operaciones. Sin embargo, en el caso de operaciones relacionadas con contratos, una transacción está limitada a solo una.
-
-Así que para todas las demás transacciones, el CLI proporciona los subcomandos `tx`. Estos son:
-
-- `new`
-- `sign`
-- `send`
-- `simulate`
-
-## `tx nuevo`
-
-Para los siguientes ejemplos, utilizaremos las siguientes cuentas:
-
-```sh
-stellar keys generate --fund alice --network testnet
-stellar keys generate bob
-# You can add a public key to the keys
-stellar keys add --public-key GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI charlie
-## and use testnet
-stellar network use testnet
-```
-
-### Crear Cuenta
-
-Crea y financia una nueva cuenta Stellar. Arriba, `alice` fue financiado por [friendbot](https://developers.stellar.org/docs/learn/fundamentals/networks#friendbot). Sin embargo, `bob` y `charlie` no lo fueron. Así que podemos usar el comando `create-account` para financiarlos.
-
-`bob` recibirá 10 XLM y `charlie` obtendrá 1 XLM.
-
-```sh
-stellar tx new create-account \
-  --source alice \
-  --destination bob \
-  --starting-balance 100_000_000
-
-stellar tx new create-account \
-  --source alice \
-  --destination charlie \
-  --starting-balance 10_000_000
-```
-
-Notas:
-
-- `--starting-balance`: El balance inicial en stroops para financiar la cuenta (1 XLM = <b>10,000,000</b> stroops)
-
-### Pago
-
-`bob` se siente mal porque `charlie` solo recibió 1 XLM, así que enviará 4 XLM más a `charlie`.
-
-```sh
-stellar tx new payment \
-  --source bob \
-  --destination charlie \
-  --asset native \
-  --amount 40_000_000
-```
-
-Notas:
-
-- `--asset`: El activo a enviar - ya sea "nativo" para XLM o en formato "CODE:ISSUER" para otros activos
-
-### Aumentar Secuencia
-
-Aumentar el número de secuencia de una cuenta:
-
-```sh
-stellar tx new bump-sequence \
-  --source alice \
-  --bump-to 123450
-```
-
-### Fusión de Cuenta
-
-Fusionar una cuenta en otra, transfiriendo todos los XLM.
-
-`bob` decide seguir compartiendo la riqueza y fusiona su cuenta en la de `charlie`.
-
-```sh
-stellar tx new account-merge \
-  --source bob \
-  --account charlie
-```
-
-Notas:
-
-- `--source`: La cuenta a eliminar del ledger, por lo tanto, esta es su transacción final
-
-### Establecer Flags de Línea de Confianza
-
-Modificar las flags de autorización en una línea de confianza:
-
-```sh
-stellar tx new set-trustline-flags \
-  --source alice \
-  --asset USDC:GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
-  --trustor charlie \
-  --set-authorize \
-  --set-authorize-to-maintain-liabilities \
-  --set-trustline-clawback-enabled
-```
-
-Argumentos:
-
-- `--source`: La cuenta emisora que establece las flags (debe ser el emisor del activo)
-- `--asset`: El activo en formato CODE:ISSUER
-- `--trustor`: La cuenta cuya flags de línea de confianza se modificará
-- `--set-authorize`: Habilitar autorización completa
-- `--set-authorize-to-maintain-liabilities`: Habilitar autorización limitada
-- `--set-trustline-clawback-enabled`: Habilitar clawback para esta línea de confianza
-- `--clear-*`: Flags de limpieza correspondientes para eliminar cada configuración
-
-### Establecer Opciones
-
-Configurar configuraciones de cuenta:
-
-```sh
-stellar tx new set-options \
-  --source alice \
-  --inflation-dest GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
-  --home-domain "example.com" \
-  --master-weight 100 \
-  --med-threshold 100 \
-  --low-threshold 100 \
-  --high-threshold 100 \
-  --signer GBXSGN5GX4PZOSBHB4JJF67CEGSGT7DGBGGUGWXI4WOQMQEA4SFV2HTJ \
-  --signer-weight 1 \
-  --set-required \
-  --set-revocable \
-  --set-clawback-enabled \
-  --set-immutable
-```
-
-Notas:
-
-- `--source`: Cuenta para modificar las configuraciones
-- `--inflation-dest`: Establecer la cuenta de destino de inflación
-- `--home-domain`: Establecer el dominio principal para federación / cumplimiento
-- `--master-weight`: Peso de la clave maestra de la cuenta (0-255)
-- `--low-threshold`: Umbral de peso para operaciones de baja seguridad
-- `--med-threshold`: Umbral de peso para operaciones de seguridad media
-- `--high-threshold`: Umbral de peso para operaciones de alta seguridad
-- `--signer`: Añadir una nueva clave pública de firmante
-- `--signer-weight`: Peso para el nuevo firmante (0 elimina el firmante)
-- `--set-required`: Habilitar requerir autorización para nuevas líneas de confianza
-- `--set-revocable`: Habilitar la revocación de líneas de confianza
-- `--set-clawback-enabled`: Habilitar clawback para la cuenta emisora de activos
-- `--set-immutable`: Hacer que las configuraciones de la cuenta sean inmutables
-- `--clear-*`: Flags de limpieza correspondientes para eliminar cada configuración
-
-### Cambiar Confianza
-
-Crear o modificar una línea de confianza:
-
-```sh
-stellar tx new change-trust \
-  --source alice \
-  --line USDC:ISSUER \
-  --limit 100000000
-```
-
-Argumentos:
-
-- `--source`: Cuenta creando/modificando la línea de confianza
-- `--line`: Activo para crear la línea de confianza en formato CODE:ISSUER
-- `--limit`: Cantidad máxima que se puede mantener (0 elimina la línea de confianza)
-
-### Gestionar Datos
-
-Gestionar entradas de datos de la cuenta:
-
-```sh
-stellar tx new manage-data \
-  --source alice \
-  --data-name config \
-  --data-value 7465737476616c7565 # hex encoded
-```
-
-Notas:
-
-- `--data-name`: Nombre de la entrada de datos (hasta 64 bytes)
-- `--data-value`: Valor codificado en hex para almacenar (hasta 64 bytes, omite para eliminar)
-
-```
-
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-op-add.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-op-add.mdx
deleted file mode 100644
index 8830959190..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-op-add.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: tx op agregar
-hide_table_of_contents: true
-description: Crear transacciones Stellar usando el CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-op-add.mdx
----
-
-Como se vio antes, puedes usar tuberías para pasar un sobre de transacción entre comandos. Antes solo hemos estado viendo transacciones con una operación, sin embargo, como se mencionó, puede haber hasta 100 operaciones en una sola transacción.
-
-Para agregar una operación a una transacción, puedes usar el comando `tx op agregar`. Este comando toma el sobre de la transacción del comando anterior y le agrega una operación.
-
-Considera un ejemplo más complicado. Considera emitir un activo, aquí `USDC`, con el requisito de que solo el emisor puede transferir fondos al distribuidor.
-
-```sh
-
-stellar keys generate --fund issuer
-stellar keys generate --fund distributor
-
-ISSUER_PK=$(stellar keys address issuer)
-
-ASSET="USDC:$ISSUER_PK"
-
-# Issue the asset by setting its options, establishing a trustline, and
-# transferring the smallest amount possible to the distributor. Then
-# deauthorize the distributor so that people can only send Claimable Balances,
-# rather than transferring assets directly.
-
-# first the issuer sets the options for being able to clawback and revoke the asset
-stellar tx new set-options --fee 1000 --source issuer --set-clawback-enabled --set-revocable --build-only \
-# next the distributor establishes a trustline with the asset. Note that here the distributor the source account for the operation, not the issuer
-| stellar tx op add change-trust --op-source distributor --line $ASSET \
-# then the issuer sends the smallest amount possible to the distributor
-| stellar tx op add payment --destination distributor --asset $ASSET --amount 1 \
-# finally the issuer deauthorizes the distributor from being able to send the asset
-| stellar tx op add set-trustline-flags --asset $ASSET --trustor distributor --clear-authorize \
-# Then both accounts need to sign the transaction
-| stellar tx sign --sign-with-key issuer \
-| stellar tx sign --sign-with-key distributor \
-| stellar tx send
-
-# Next is an example of sandwiching an operation. That is giving permission in one operation, preforming the operation, and then removing the permission in a third operation.
-# Here is an example of minting new assets to the distributor with a sandwich transaction
-# First authorize the distributor to receive the asset
-stellar tx new set-trustline-flags --fee 1000 --build-only --source issuer --asset $ASSET --trustor $distributor_PK --set-authorize \
-# Then mint the asset to the distributor
-| stellar tx op add payment --destination distributor --asset $ASSET --amount 1_000_000_000_000 \
-# Finally remove the authorization
-| stellar tx op add set-trustline-flags --asset $ASSET --trustor distributor --clear-authorize \
-| stellar tx sign --sign-with-key issuer \
-| stellar tx send
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-sign.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-sign.mdx
deleted file mode 100644
index c61f0fbde8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/cli/tx-sign.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: firma tx y envía tx
-hide_table_of_contents: true
-description: Crear transacciones stellar utilizando el CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-sign.mdx
----
-
-Los ejemplos anteriores de utilizar `tx new` mostraron cómo crear transacciones. Sin embargo, estas transacciones estaban listas para ser firmadas y enviadas a la red.
-
-Para evitar esto, cada uno de los subcomandos tiene el argumento `--build-only`, que como su nombre sugiere, solo construye la transacción e imprime el sobre de la transacción.
-
-## `tx sign`
-
-Regresamos al primer ejemplo de crear la cuenta de `bob`:
-
-```sh
-stellar tx new create-account \
-  --source alice \
-  --destination bob \
-  --starting-balance 100_000_000 \
-  --build-only
-```
-
-debería generar algo como:
-
-```sh
-AAAAAgAAAADwSUp9CwmVlPN40mKX1I1j39y6DmYc36QS1aK2x6eYVQAAAGQAEcMsAAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAACTMkzn1TwPo8SIhnKvnyuv9K2/aWjpX9NTYfyiA7vXaAAAAAAX14QAAAAAAAAAAAA==
-```
-
-Puedes inspeccionarlo con [stellar lab!](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&xdr$blob=AAAAAgAAAADwSUp9CwmVlPN40mKX1I1j39y6DmYc36QS1aK2x6eYVQAAAGQAEcMsAAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAACTMkzn1TwPo8SIhnKvnyuv9K2//aWjpX9NTYfyiA7vXaAAAAAAX14QAAAAAAAAAAAA==;;) Donde también puedes firmar y enviar la transacción.
-
-Sin embargo, también puedes firmar la transacción con el comando `tx sign`. Para hacer esto, puedes canalizar la salida del comando `tx new` al comando `tx sign`:
-
-```sh
-stellar tx new create-account \
-    --source alice \
-    --destination bob \
-    --starting-balance 100_000_000 \
-    --build-only \
-  | stellar tx sign --sign-with-key alice
-```
-
-Esto debería producir algo como:
-
-```sh
-AAAAAgAAAAAebE8Ewg9uzvHRAl+UmvP0kixsyp238kkz0zOy+91FeQAAAGQAFJk4AAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAPpiy8qfSw4pLYG/Bav78FfrFWlte7YQfiHX41DQ+nGWAAAAAAX14QAAAAAAAAAAAfvdRXkAAABA4kjz9Yeub/IrzogjMr57U4nYwCmSJAXxIW+7Xyjan/UweIByF7uEhVS4gEl1N138uq07njVxZwRMtugWyMleCg==
-```
-
-Puedes [volver a verlo en el laboratorio y ver que ahora hay una firma adjunta al sobre de la transacción](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&xdr$blob=AAAAAgAAAAAebE8Ewg9uzvHRAl+UmvP0kixsyp238kkz0zOy+91FeQAAAGQAFJk4AAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAPpiy8qfSw4pLYG//Bav78FfrFWlte7YQfiHX41DQ+nGWAAAAAAX14QAAAAAAAAAAAfvdRXkAAABA4kjz9Yeub//IrzogjMr57U4nYwCmSJAXxIW+7Xyjan//UweIByF7uEhVS4gEl1N138uq07njVxZwRMtugWyMleCg==;;).
-
-::tip O firma con lab! Aunque actualmente debes enviarlo desde lab y no puedes regresar al CLI (¡un trabajo en progreso!).
-
-```sh
-stellar tx new create-account \
-    --source alice \
-    --destination bob \
-    --starting-balance 100_000_000 \
-    --build-only \
-  | stellar tx sign --sign-with-lab
-```
-
-:::
-
-## `tx send`
-
-Finalmente, para enviar la transacción a la red, puedes usar el comando `tx send`. Este comando enviará la transacción a la red.
-
-```sh
-stellar tx new create-account \
-    --source alice \
-    --destination bob \
-    --starting-balance 100_000_000 \
-    --build-only \
-  | stellar tx sign --sign-with-key alice \
-  | stellar tx send
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/README.mdx
deleted file mode 100644
index 46fb959cf6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/README.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Cuentas de contrato
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 5
-description: Construye, evalúa y amplía las cuentas de contrato en Stellar.
----
-
-Las cuentas de contrato son contratos inteligentes que actúan como cuentas. Mantienen saldos y usan `__check_auth` para decidir quién puede actuar y bajo qué condiciones.
-
-Usa una cuenta de contrato cuando:
-
-- Necesites autenticación personalizada en el contrato (passkeys/WebAuthn, claves hardware u otras verificaciones de firmantes).
-- Necesites reglas en cadena como límites de gasto, listas permitidas o bloqueos temporales.
-
-Mantente con una cuenta clásica cuando:
-
-- Quieres la opción más simple: una clave privada, financia la cuenta, sin código extra de contrato ni infraestructura.
-- Debas interoperar con sistemas/herramientas que esperan memos (por ejemplo, algunos exchanges requieren pagos con memos desde una dirección G; los pagos de cuentas de contrato pasan por el Stellar Asset Contract como transferencias muxed, por lo que las transferencias desde contratos no son soportadas por exchanges actualmente).
-
-Enlaces rápidos:
-
-- [Ejemplo de cuenta sencilla](../../smart-contracts/example-contracts/simple-account.mdx)
-- [Ejemplo de cuenta compleja](../../smart-contracts/example-contracts/complex-account.mdx)
-- [Guía introductoria de autorización de contrato](../auth/contract-authorization.mdx) y [Fundamentos de autorización](../../../learn/fundamentals/contract-development/authorization.mdx)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/_category_.json
deleted file mode 100644
index 163cb24ca4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/advanced-patterns.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/advanced-patterns.mdx
deleted file mode 100644
index cff7b262b2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/advanced-patterns.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Patrones avanzados de cuenta de contrato
-description: Límites de gasto por capa, listas de permitidos, reglas de tiempo y otros mecanismos de protección para cuentas de contrato.
-sidebar_position: 40
----
-
-Utiliza estos patrones para extender una cuenta de contrato básica con mecanismos de protección. Coloca la lógica en `__check_auth` o en un auxiliar que este llame, y prueba tanto las rutas de autorización como de denegación. Trata las reglas del firmante como “quién puede actuar” y las reglas de la política como “bajo qué condiciones.”
-
-## Límites de gasto
-
-- Almacena un límite y un total acumulado en el almacenamiento de la instancia (por ejemplo, salidas durante las últimas 24 horas).
-- Deriva una clave de ventana a partir de la marca temporal del libro mayor (por ejemplo, `day = timestamp / 86_400`) y reinicia el total cuando la ventana cambia.
-- En cada solicitud, verifica la asignación restante; si la cantidad la excedería, rechaza y emite un evento con la cantidad intentada y la asignación restante.
-
-Consulta el [ejemplo de Cuenta Compleja](../../smart-contracts/example-contracts/complex-account.mdx) para una implementación de referencia con firmantes ponderados y límites.
-
-## Listas de permitidos
-
-- Mantén las direcciones de destino permitidas o IDs de contrato en el almacenamiento.
-- Inspecciona tanto la invocación raíz como las subinvocaciones en `auth_context` antes de aprobar para que las llamadas anidadas no puedan evitar la lista.
-
-## Firmantes de políticas
-
-- Define uno o más roles de firmantes de políticas en el almacenamiento. Un firmante de política existe para aprobar o denegar acciones específicas (por ejemplo, una clave de auditor, una clave de guardián, o un servicio que aplica reglas de gasto).
-- Para llamadas de contrato de alto riesgo (p. ej., transferencias grandes, cambio de firmantes), requiere tanto al usuario final como a un firmante de política; rechaza si falta alguno de los dos.
-- Separa roles (administrador vs. estándar) para que el uso diario pueda delegarse mientras las actualizaciones o recuperación se mantengan con administradores.
-
-## Reglas de tiempo
-
-- Bloquea la ejecución hasta una marca temporal específica del libro mayor, o agrega un tiempo de espera tras acciones como rotación de claves o transferencias grandes.
-- Almacena la marca temporal más temprana permitida en el almacenamiento de la instancia; compárala con la marca temporal actual del libro mayor en `__check_auth`.
-
-## Claves de sesión
-
-- Genera una clave de sesión de corta duración (por ejemplo, una clave p256 creada del lado del cliente y guardada en almacenamiento seguro del navegador) y limita su uso a una función y a una cantidad máxima.
-- Guarda un registro para la clave de sesión con su expiración, alcance permitido y asignación restante; reduce la asignación en cada llamada autorizada.
-- Rechaza si la clave de sesión es desconocida, ha expirado, no tiene asignación o se usa fuera de su alcance permitido.
-
-## Contratos de política externos
-
-- Delegar verificaciones específicas (listas de denegados, ventanas temporales, postura del dispositivo) a un contrato de política dedicado; pasa el contexto a `__check_auth` y exige que el contrato de política apruebe antes de devolver éxito.
-- Mantén la interfaz de la política mínima (por ejemplo, `fn approve(auth_context) -> bool`) para que puedas cambiar políticas sin modificar tu cuenta.
-
-## A dónde ir a continuación
-
-- Consulta estos patrones aplicados en los [ejemplos de cuentas de contrato](./examples.mdx).
-- Explora implementaciones de referencia y bibliotecas:
-  - [Contratos Stellar de OpenZeppelin](https://github.com/OpenZeppelin/stellar-contracts/)
-  - [Cuenta inteligente Crossmint](https://github.com/Crossmint/stellar-smart-account)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/examples.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/examples.mdx
deleted file mode 100644
index d65a3ff176..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/examples.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Ejemplos de cuentas contrato
-description: Proyectos reales que muestran firmantes de políticas, passkeys y la experiencia de usuario de cuentas contrato en Stellar.
-sidebar_position: 50
----
-
-Utiliza estos proyectos como referencias o puntos de partida. Están desarrollados por la comunidad; revisa y prueba antes de reutilizarlos en producción.
-
-### Zafegard
-
-Una billetera inteligente que demuestra el uso de firmantes de política con estado.
-
-- Ver el [código](https://github.com/kalepail/zafegard)
-- Ver el [video demostrativo](https://www.youtube.com/watch?v=I4i6sL-pHrs)
-
-### Haz matemáticas
-
-Una billetera inteligente que demuestra el uso de multi-sig y firmantes de políticas para, sorprendentemente, hacer matemáticas sin necesidad de introducir un passkey para cada interacción.
-
-- Ver el [código](https://github.com/kalepail/do-math)
-- Ver el [video demostrativo](https://www.youtube.com/watch?v=lwvE6pEBmXw)
-
-### Soroban por ejemplo
-
-Una aplicación que usa passkeys para firmar transacciones de contratos inteligentes en Stellar.
-
-- Ver la [demostración](https://passkey.sorobanbyexample.org/)
-- Ver el [código](https://github.com/kalepail/soroban-passkey)
-- Ver el [video demostrativo](https://www.youtube.com/watch?v=y38_O4oIvbY)
-- Mira la [discusión](/meetings/2024/05/09)
-- Leer el [blog](https://kalepail.com/blockchain/the-passkey-powered-future-of-web3)
-
-### Super Peach
-
-Un ejemplo de contrato de cuenta abstracta con múltiples firmantes impulsado por passkeys.
-
-- Ver la [demostración](https://superpeach.xyz/)
-- Ver el [código](https://github.com/kalepail/superpeach)
-- Ver el [video demostrativo](https://youtu.be/0Agiwso2OMc?si=CHD9U8s-YLyqbXUJ)
-
-### Ye Olde Guestbook
-
-Un libro de visitas en internet impulsado por passkeys de antaño construido con contratos inteligentes y código frontend.
-
-- Ver la [demostración](https://ye-olde-guestbook.vercel.app)
-- Ver el [código](https://github.com/ElliotFriend/ye-olde-guestbook)
-- Leer el [tutorial](../../apps/guestbook/README.mdx)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/smart-wallets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/smart-wallets.mdx
deleted file mode 100644
index 2729a8b2c4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/contract-accounts/smart-wallets.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Billeteras inteligentes
-sidebar_position: 10
----
-
-Las billeteras inteligentes son cuentas de contrato que actúan como billeteras de usuario. Mantienen activos y aplican la autenticación en `__check_auth` en lugar de una única clave secreta. Las passkeys (WebAuthn) son comunes, pero también puedes usar claves Ed25519, firmantes de políticas, claves de sesión o cualquier cosa que el contrato pueda verificar.
-
-## Cuándo usar una billetera inteligente
-
-- Necesitas autenticación programable (límites, listas permitidas, aprobaciones multifactor como usuario más clave de dispositivo).
-- Quieres una experiencia con passkey o clave hardware sin exponer frases Seed.
-- Necesitas mezclas flexibles de firmantes: passkeys para experiencia de usuario, Ed25519 para compatibilidad, firmantes de políticas o multisig para controles de riesgo.
-
-## WebAuthn
-
-[WebAuthn](https://www.w3.org/TR/webauthn/) es un estándar del navegador para autenticación sin contraseña usando criptografía de clave pública. Un dispositivo crea un keypair y demuestra su posesión con un flujo de desafío/respuesta. Las claves permanecen en el dispositivo o se sincronizan entre dispositivos mediante proveedores en la nube.
-
-Beneficios:
-
-- Funciona en navegadores y plataformas modernas.
-- Flujos familiares (Touch ID, Face ID, claves hardware) sin frases Seed.
-- Produce firmas que verificas en `__check_auth`.
-
-## secp256r1 en Stellar
-
-`secp256r1` (prime256v1) es la curva que utilizan la mayoría de los autenticadores WebAuthn. Stellar añadió verificación nativa para esta curva en el Protocolo 21, así contratos pueden validar firmas WebAuthn on-chain.
-
-## Passkeys
-
-- WebAuthn es el estándar del navegador para autenticación sin contraseña.
-- secp256r1 es la curva que la mayoría de autenticadores usan; Stellar la verifica on-chain.
-- Las passkeys son credenciales basadas en plataforma o hardware que implementan WebAuthn.
-- Consulta [ejemplos](./examples.mdx) para proyectos reales.
-
-## Passkeys en la práctica
-
-- Registro: usa WebAuthn para crear un keypair en el dispositivo; guarda la clave pública (y el ID de credencial opcional) en el estado del contrato.
-- Firma: solicita una afirmación WebAuthn cuando el usuario aprueba una acción; retorna una firma sobre la carga.
-- Verificación: pasa la firma y el ID de credencial a tu contrato; en `__check_auth`, verifica la firma secp256r1 y aplica controles de políticas (límites, listas permitidas, bloqueos temporales).
-
-## Herramientas
-
-- **Passkey Kit**: SDK en TypeScript para crear cuentas de contrato y firmar con passkeys.
-  - Demo: [passkey-kit-demo.pages.dev](https://passkey-kit-demo.pages.dev/)
-  - Código: [github.com/kalepail/passkey-kit](https://github.com/kalepail/passkey-kit)
-- **Launchtube**: relé para enviar transacciones y manejar tarifas/números de secuencia.
-  - Código: [github.com/stellar/launchtube](https://github.com/stellar/launchtube)
-
-## Participa
-
-- Únete a la conversación en el canal `#passkeys` en el [Discord de Desarrollo de Stellar](https://discord.gg/stellardev).
-- Sigue la evolución de la interfaz de cuentas de contrato en [la discusión SEP](https://github.com/orgs/stellar/discussions/1499).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/README.mdx
deleted file mode 100644
index 3b00c181d2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Convenciones de Contrato
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 10
----
-
-Estas guías describen la forma "típica" en que algo podría lograrse en un contrato de Rust. Estas guías no pretenden ser tan _prescriptivas_ como algunas otras; en cambio, sirven para resaltar algunas de las normas que hemos observado cuando surgen en el desarrollo de contratos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/check-auth-tutorials.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/check-auth-tutorials.mdx
deleted file mode 100644
index 7f26200e94..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/check-auth-tutorials.mdx
+++ /dev/null
@@ -1,1483 +0,0 @@
----
-title: Usar __check_auth de maneras interesantes
-description: Dos guías que explican cómo usar __check_auth
----
-
-<head>
-  <title>Usar __check_auth de maneras interesantes</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Usar __check_auth de maneras interesantes" />
-  <meta
-    property="og:description"
-    content="Esta guía te explicará maneras interesantes en las que puedes usar __check_auth en tus aplicaciones Soroban"
-  />
-</head>
-
-## Tutorial 1: restricción basada en tiempo en transferencias de tokens
-
-Imagina un contrato de cuenta multi-firma donde ciertas acciones, como transferir tokens, deben ser controladas por el tiempo transcurrido entre transferencias consecutivas. Por ejemplo, una transferencia de tokens solo debería permitirse si ha pasado un cierto período de tiempo desde la última transferencia. Esto puede ser útil en escenarios donde deseas limitar la frecuencia de las transacciones para prevenir el mal uso o implementar límites de tasa.
-
-### Conceptos básicos
-
-#### Restricciones basadas en tiempo
-
-La idea es hacer cumplir un intervalo de tiempo mínimo entre transferencias de tokens consecutivas. Cada token puede tener su propio límite de tiempo, y el contrato rastreará el tiempo de la última transferencia para cada token.
-
-#### Almacenamiento de datos
-
-El contrato almacenará el límite de tiempo y el tiempo de la última transferencia para cada token en su almacenamiento para mantener un registro de estos valores a través de las transacciones.
-
-### Revisión del código
-
-#### Estructura del contrato e importaciones
-
-```rust
-#![no_std]
-
-use soroban_sdk::{
-    auth::{Context, CustomAccountInterface}, contract, contracterror, contractimpl, contracttype, symbol_short, Address,
-    BytesN, Env, Symbol, Vec,
-};
-#[contract]
-struct AccountContract;
-
-#[contracttype]
-#[derive(Clone)]
-pub struct Signature {
-    pub public_key: BytesN<32>,
-    pub signature: BytesN<64>,
-}
-
-#[contracttype]
-#[derive(Clone)]
-enum DataKey {
-    SignerCnt,
-    Signer(BytesN<32>),
-    TimeLimit(Address),
-    LastTransferTime(Address),
-}
-
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum AccError {
-    NotEnoughSigners = 1,
-    NegativeAmount = 2,
-    BadSignatureOrder = 3,
-    UnknownSigner = 4,
-    InvalidContext = 5,
-    TimeLimitExceeded = 6,
-}
-
-const TRANSFER_FN: Symbol = symbol_short!("transfer");
-
-```
-
-#### Inicialización del contrato
-
-1. Inicializa el contrato con una lista de las claves públicas de los firmantes
-2. Almacena el conteo de firmantes en el almacenamiento del contrato
-
-```rust
-#[contractimpl]
-impl AccountContract {
-
-    pub fn init(env: Env, signers: Vec<BytesN<32>>) {
-        for signer in signers.iter() {
-            env.storage().instance().set(&DataKey::Signer(signer), &());
-        }
-        env.storage()
-            .instance()
-            .set(&DataKey::SignerCnt, &signers.len());
-    }
-}
-```
-
-#### Establecer límites de tiempo
-
-1. Permite establecer un límite de tiempo para un token específico
-2. Asegura que solo el contrato mismo pueda establecer estos límites al requerir la autorización del contrato
-
-```rust
-#[contractimpl]
-
-impl AccountContract {
-    pub fn set_time(env: Env, token: Address, time_limit: u64) {
-        env.current_contract_address().require_auth();
-        env.storage()
-            .instance()
-            .set(&DataKey::TimeLimit(token), &time_limit);
-    }
-}
-```
-
-#### Autenticación y autorización personalizadas
-
-1. Autentica las firmas
-2. Verifica si todos los firmantes requeridos han firmado
-3. Itera a través del contexto de autorización para verificar la política de autorización
-
-```rust
-#[contractimpl]
-impl CustomAccountInterface for AccountContract {
-
-    type Error = AccError;
-    type Signature = Vec<Signature>;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,
-        signature_payload: BytesN<32>,
-        signatures: Vec<Signature>,
-        auth_context: Vec<Context>,
-    ) -> Result<(), AccError> {
-        authenticate(&env, &signature_payload, &signatures)?;
-
-        let tot_signers: u32 = env
-            .storage()
-            .instance()
-            .get::<_, u32>(&DataKey::SignerCnt)
-            .unwrap();
-
-        let all_signed = tot_signers == signatures.len();
-
-        let curr_contract = env.current_contract_address();
-
-        for context in auth_context.iter() {
-            verify_authorization_policy(
-                &env,
-                &context,
-                &curr_contract,
-                all_signed,
-            )?;
-        }
-        Ok(())
-    }
-
-}
-```
-
-#### Lógica de autenticación
-
-1. Verifica que las firmas estén en el orden correcto y que cada firmante esté autorizado
-2. Usa la función [ed25519_verify](https://docs.rs/soroban-sdk/latest/soroban_sdk/crypto/struct.Crypto.html#method.ed25519_verify) para verificar cada firma
-
-```rust
- fn authenticate(
-        env: &Env,
-        signature_payload: &BytesN<32>,
-        signatures: &Vec<Signature>,
-) -> Result<(), AccError> {
-    for i in 0..signatures.len() {
-        let signature = signatures.get_unchecked(i);
-        if i > 0 {
-            let prev_signature = signatures.get_unchecked(i - 1);
-            if prev_signature.public_key >= signature.public_key {
-                return Err(AccError::BadSignatureOrder);
-            }
-        }
-        if !env
-            .storage()
-            .instance()
-            .has(&DataKey::Signer(signature.public_key.clone()))
-        {
-            return Err(AccError::UnknownSigner);
-        }
-        env.crypto().ed25519_verify(
-            &signature.public_key,
-            &signature_payload.clone().into(),
-            &signature.signature,
-        );
-    }
-    Ok(())
-}
-```
-
-#### Verificación de la política de autorización
-
-1. Verifica si la función que se está llamando es una función de transferencia o de aprobación
-2. Forzar la restricción basada en tiempo comparando el tiempo actual con el tiempo de la última transferencia
-3. Actualiza el tiempo de la última transferencia si se permite la transferencia
-
-```rust
-fn verify_authorization_policy(
-        env: &Env,
-        context: &Context,
-        curr_contract: &Address,
-        all_signed: bool,
-    ) -> Result<(), AccError> {
-        let contract_context = match context {
-            Context::Contract(c) => {
-                if &c.contract == curr_contract {
-                    if !all_signed {
-                        return Err(AccError::NotEnoughSigners);
-                    }
-                }
-                c
-            }
-            Context::CreateContractHostFn(_) => return Err(AccError::InvalidContext),
-        };
-
-        if contract_context.fn_name != TRANSFER_FN
-            && contract_context.fn_name != Symbol::new(env, "approve")
-        {
-            return Ok(());
-        }
-
-        let current_time = env.ledger().timestamp();
-        let time_limit: Option<u64> =
-            env.storage()
-                .instance()
-                .get::<_, u64>(&DataKey::TimeLimit(contract_context.contract.clone()));
-
-        if let Some(limit) = time_limit {
-            let last_transfer_time: u64 = env.storage()
-                .instance()
-                .get::<_, u64>(&DataKey::LastTransferTime(contract_context.contract.clone()))
-                .unwrap_or(0);
-
-            if current_time - last_transfer_time < limit {
-                return Err(AccError::TimeLimitExceeded);
-            }
-
-            env.storage()
-                .instance()
-                .set(&DataKey::LastTransferTime(contract_context.contract.clone()), &current_time);
-        }
-        Ok(())
-}
-```
-
-#### Resumen
-
-El contrato comienza inicializándose con un conjunto de firmantes autorizados. Permite establecer un límite de tiempo para transferencias de tokens, que controla con qué frecuencia un token puede ser transferido. La función __check_auth es el núcleo del proceso de autorización, asegurando que todas las firmas necesarias sean válidas y verificando la restricción basada en tiempo para transferencias de tokens. Si el tiempo requerido no ha pasado desde la última transferencia, el contrato negará la operación, haciendo cumplir el límite de tasa deseado. Al rastrear el tiempo de la última transferencia y hacer cumplir un intervalo mínimo de tiempo entre transferencias, el contrato limita efectivamente la frecuencia de las transferencias de tokens, resolviendo el problema del abuso potencial a través de transacciones consecutivas rápidas.
-
-#### Código completo
-
-Aquí están todos los fragmentos apilados juntos en un solo archivo para conveniencia:
-
-```rust
-#![no_std]
-use soroban_sdk::{
-    auth::{Context, CustomAccountInterface}, contract, contracterror, contractimpl, contracttype, symbol_short, Address,
-    BytesN, Env, Symbol, Vec,
-};
-#[contract]
-struct AccountContract;
-
-#[contracttype]
-#[derive(Clone)]
-pub struct Signature {
-    pub public_key: BytesN<32>,
-    pub signature: BytesN<64>,
-}
-
-#[contracttype]
-#[derive(Clone)]
-enum DataKey {
-    SignerCnt,
-    Signer(BytesN<32>),
-    TimeLimit(Address),
-    LastTransferTime(Address),
-}
-
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum AccError {
-    NotEnoughSigners = 1,
-    NegativeAmount = 2,
-    BadSignatureOrder = 3,
-    UnknownSigner = 4,
-    InvalidContext = 5,
-    TimeLimitExceeded = 6,
-}
-
-const TRANSFER_FN: Symbol = symbol_short!("transfer");
-
-#[contractimpl]
-impl AccountContract {
-    pub fn init(env: Env, signers: Vec<BytesN<32>>) {
-        for signer in signers.iter() {
-            env.storage().instance().set(&DataKey::Signer(signer), &());
-        }
-        env.storage()
-            .instance()
-            .set(&DataKey::SignerCnt, &signers.len());
-    }
-
-    pub fn set_time(env: Env, token: Address, time_limit: u64) {
-        env.current_contract_address().require_auth();
-        env.storage()
-            .instance()
-            .set(&DataKey::TimeLimit(token), &time_limit);
-    }
-}
-
-#[contractimpl]
-impl CustomAccountInterface for AccountContract {
-
-    type Error = AccError;
-    type Signature = Vec<Signature>;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,
-        signature_payload: BytesN<32>,
-        signatures: Vec<Signature>,
-        auth_context: Vec<Context>,
-    ) -> Result<(), AccError> {
-        authenticate(&env, &signature_payload, &signatures)?;
-
-        let tot_signers: u32 = env
-            .storage()
-            .instance()
-            .get::<_, u32>(&DataKey::SignerCnt)
-            .unwrap();
-
-        let all_signed = tot_signers == signatures.len();
-
-        let curr_contract = env.current_contract_address();
-
-        for context in auth_context.iter() {
-            verify_authorization_policy(
-                &env,
-                &context,
-                &curr_contract,
-                all_signed,
-            )?;
-        }
-        Ok(())
-    }
-
-}
-
-fn authenticate(
-    env: &Env,
-    signature_payload: &BytesN<32>,
-    signatures: &Vec<Signature>,
-) -> Result<(), AccError> {
-    for i in 0..signatures.len() {
-        let signature = signatures.get_unchecked(i);
-        if i > 0 {
-            let prev_signature = signatures.get_unchecked(i - 1);
-            if prev_signature.public_key >= signature.public_key {
-                return Err(AccError::BadSignatureOrder);
-            }
-        }
-        if !env
-            .storage()
-            .instance()
-            .has(&DataKey::Signer(signature.public_key.clone()))
-        {
-            return Err(AccError::UnknownSigner);
-        }
-        env.crypto().ed25519_verify(
-            &signature.public_key,
-            &signature_payload.clone().into(),
-            &signature.signature,
-        );
-    }
-    Ok(())
-}
-
-fn verify_authorization_policy(
-    env: &Env,
-    context: &Context,
-    curr_contract: &Address,
-    all_signed: bool,
-) -> Result<(), AccError> {
-    let contract_context = match context {
-        Context::Contract(c) => {
-            if &c.contract == curr_contract {
-                if !all_signed {
-                    return Err(AccError::NotEnoughSigners);
-                }
-            }
-            c
-        }
-        Context::CreateContractHostFn(_) => return Err(AccError::InvalidContext),
-    };
-
-    if contract_context.fn_name != TRANSFER_FN
-        && contract_context.fn_name != Symbol::new(env, "approve")
-    {
-        return Ok(());
-    }
-
-    let current_time = env.ledger().timestamp();
-    let time_limit: Option<u64> =
-        env.storage()
-            .instance()
-            .get::<_, u64>(&DataKey::TimeLimit(contract_context.contract.clone()));
-
-    if let Some(limit) = time_limit {
-        let last_transfer_time: u64 = env.storage()
-            .instance()
-            .get::<_, u64>(&DataKey::LastTransferTime(contract_context.contract.clone()))
-            .unwrap_or(0);
-
-        if current_time - last_transfer_time < limit {
-            return Err(AccError::TimeLimitExceeded);
-        }
-
-        env.storage()
-            .instance()
-            .set(&DataKey::LastTransferTime(contract_context.contract.clone()), &current_time);
-    }
-    Ok(())
-}
-
-mod test;
-```
-
-Estos son los casos de prueba:
-
-```rust
-#![cfg(test)]
-extern crate std;
-
-use ed25519_dalek::Keypair;
-use ed25519_dalek::Signer;
-use rand::thread_rng;
-use soroban_sdk::auth::ContractContext;
-use soroban_sdk::symbol_short;
-use soroban_sdk::testutils::Address as _;
-use soroban_sdk::testutils::AuthorizedFunction;
-use soroban_sdk::testutils::AuthorizedInvocation;
-use soroban_sdk::Val;
-use soroban_sdk::{
-    auth::Context, testutils::BytesN as _, vec, Address, BytesN, Env, IntoVal, Symbol,
-};
-use soroban_sdk::testutils::Ledger;
-use soroban_sdk::testutils::LedgerInfo;
-use crate::AccError;
-use crate::{AccountContract, AccountContractClient, Signature};
-
-fn generate_keypair() -> Keypair {
-    Keypair::generate(&mut thread_rng())
-}
-
-fn signer_public_key(e: &Env, signer: &Keypair) -> BytesN<32> {
-    signer.public.to_bytes().into_val(e)
-}
-
-fn create_account_contract(e: &Env) -> AccountContractClient {
-    AccountContractClient::new(e, &e.register_contract(None, AccountContract {}))
-}
-
-fn sign(e: &Env, signer: &Keypair, payload: &BytesN<32>) -> Val {
-    Signature {
-        public_key: signer_public_key(e, signer),
-        signature: signer
-            .sign(payload.to_array().as_slice())
-            .to_bytes()
-            .into_val(e),
-    }
-    .into_val(e)
-}
-
-fn token_auth_context(e: &Env, token_id: &Address, fn_name: Symbol, amount: i128) -> Context {
-    Context::Contract(ContractContext {
-        contract: token_id.clone(),
-        fn_name,
-        args: ((), (), amount).into_val(e),
-    })
-}
-
-#[test]
-fn test_token_auth() {
-    let env = Env::default();
-    env.mock_all_auths();
-
-    let account_contract = create_account_contract(&env);
-
-    let mut signers = [generate_keypair(), generate_keypair()];
-    if signers[0].public.as_bytes() > signers[1].public.as_bytes() {
-        signers.swap(0, 1);
-    }
-    account_contract.init(&vec![
-        &env,
-        signer_public_key(&env, &signers[0]),
-        signer_public_key(&env, &signers[1]),
-    ]);
-
-    let payload = BytesN::random(&env);
-    let token = Address::generate(&env);
-
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1000),
-        ],
-    )
-    .unwrap();
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1000),
-        ],
-    )
-    .unwrap();
-
-    // Add a time limit of 1000 seconds for the token.
-    account_contract.set_time(&token, &1000);
-
-    assert_eq!(
-        env.auths(),
-        std::vec![(
-            account_contract.address.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    account_contract.address.clone(),
-                    symbol_short!("set_time"),
-                    (token.clone(), 1000_u64).into_val(&env),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-
-    // Attempting a transfer within the time limit should fail.
-    env.ledger().set(LedgerInfo {
-        timestamp: 0,
-        protocol_version: 1,
-        sequence_number: 10,
-        network_id: Default::default(),
-        base_reserve: 10,
-        min_temp_entry_ttl: 16,
-        min_persistent_entry_ttl: 16,
-        max_entry_ttl: 100_000,
-    });
-
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1001)
-        ],
-    )
-    .err()
-    .unwrap()
-    .unwrap() == AccError::TimeLimitExceeded;
-
-    // Simulate passing of time to allow the next transfer.
-    env.ledger().set(LedgerInfo {
-        timestamp: 1000,
-        protocol_version: 1,
-        sequence_number: 10,
-        network_id: Default::default(),
-        base_reserve: 10,
-        min_temp_entry_ttl: 16,
-        min_persistent_entry_ttl: 16,
-        max_entry_ttl: 100_000,
-    });
-
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1001),
-        ],
-    )
-    .unwrap();
-}
-```
-
-## Tutorial 2: implementar una billetera inteligente (WebAuthn)
-
-Imagina un mundo donde las contraseñas tradicionales son obsoletas. En este mundo, WebAuthn (Autenticación Web) se ha convertido en el estándar para interacciones en línea seguras. Alice, una entusiasta de blockchain, quiere crear una billetera que aproveche la tecnología WebAuthn para una mayor seguridad. Decide implementar una billetera WebAuthn en Stellar, permitiendo a los usuarios gestionar sus activos digitales utilizando las características biométricas de su dispositivo o claves de seguridad (por ejemplo, YubiKey, Google Titan Security Key, etc.).
-
-### Conceptos básicos
-
-WebAuthn es un estándar web para autenticación sin contraseña. Permite a los usuarios autenticarse utilizando biometría (como huellas dactilares o reconocimiento facial).
-
-La billetera WebAuthn implementada en este tutorial será capaz de:
-
-1. Registrar y gestionar credenciales de usuario (claves públicas)
-2. Autenticar a los usuarios para la firma de transacciones
-3. Diferenciar entre administradores y usuarios regulares
-4. Permitir actualizaciones de contrato para futuras mejoras
-
-:::info
-
-El crédito de código de este tutorial va al trabajo de [@kalepail](https://github.com/kalepail) sobre claves de acceso, que puedes explorar más [aquí](https://github.com/kalepail/passkey-kit).
-
-:::
-
-### Revisión del código
-
-#### Estructura del contrato e importaciones
-
-Esta sección establece la estructura del contrato y importa los componentes necesarios del SDK de Soroban.
-
-```rust
-#![no_std]
-
-use soroban_sdk::{
-    auth::{Context, CustomAccountInterface},
-    contract, contracterror, contractimpl, contracttype,
-    crypto::Hash,
-    panic_with_error, symbol_short, Bytes, BytesN, Env, FromVal, Symbol, Vec,
-};
-
-#[contract]
-pub struct Contract;
-```
-
-#### Definiciones de errores
-
-Esta enumeración define los posibles errores que pueden ocurrir durante la ejecución del contrato.
-
-```rust
-#[contracterror]
-#[derive(Copy, Clone, Eq, PartialEq, Debug)]
-pub enum Error {
-    NotFound = 1,
-    NotPermitted = 2,
-    ClientDataJsonChallengeIncorrect = 3,
-    Secp256r1PublicKeyParse = 4,
-    Secp256r1SignatureParse = 5,
-    Secp256r1VerifyFailed = 6,
-    JsonParseError = 7,
-}
-```
-
-#### Funciones principales del contrato
-
-Estas funciones manejan la adición y eliminación de firmantes, actualización del contrato y gestión de cuentas de administrador.
-
-```rust
-// Implementing the Contract struct with various methods
-#[contractimpl]
-impl Contract {
-    // Method to add a new signer, potentially as an admin
-    pub fn add(env: Env, id: Bytes, pk: BytesN<65>, mut admin: bool) -> Result<(), Error> {
-        // Check if the instance storage has the ADMIN_SIGNER_COUNT key
-        if env.storage().instance().has(&ADMIN_SIGNER_COUNT) {
-            // Require authentication from the current contract address
-            env.current_contract_address().require_auth();
-        } else {
-            // If it's the first signer, ensure they are an admin
-            admin = true;
-        }
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // If the signer is an admin
-        if admin {
-            // Check if the ID exists in temporary storage
-            if env.storage().temporary().has(&id) {
-                // Remove the ID from temporary storage
-                env.storage().temporary().remove(&id);
-            }
-
-            // Update the admin signer count by incrementing it
-            Self::update_admin_signer_count(&env, true);
-
-            // Store the public key in persistent storage with the given ID
-            env.storage().persistent().set(&id, &pk);
-
-            // Extend the TTL for the persistent storage entry
-            env.storage()
-                .persistent()
-                .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-        } else {
-            // If the signer is not an admin
-            // Check if the ID exists in persistent storage
-            if env.storage().persistent().has(&id) {
-                // Update the admin signer count by decrementing it
-                Self::update_admin_signer_count(&env, false);
-
-                // Remove the ID from persistent storage
-                env.storage().persistent().remove(&id);
-            }
-
-            // Store the public key in temporary storage with the given ID
-            env.storage().temporary().set(&id, &pk);
-
-            // Extend the TTL for the temporary storage entry
-            env.storage()
-                .temporary()
-                .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-        }
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Publish an event indicating a new signer has been added
-        env.events()
-            .publish((EVENT_TAG, symbol_short!("add"), id, pk), admin);
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Method to remove a signer
-    pub fn remove(env: Env, id: Bytes) -> Result<(), Error> {
-        // Require authentication from the current contract address
-        env.current_contract_address().require_auth();
-
-        // Check if the ID exists in temporary storage
-        if env.storage().temporary().has(&id) {
-            // Remove the ID from temporary storage
-            env.storage().temporary().remove(&id);
-        } else if env.storage().persistent().has(&id) {
-            // If the ID exists in persistent storage, decrement the admin signer count
-            Self::update_admin_signer_count(&env, false);
-
-            // Remove the ID from persistent storage
-            env.storage().persistent().remove(&id);
-        }
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Publish an event indicating a signer has been removed
-        env.events()
-            .publish((EVENT_TAG, symbol_short!("remove"), id), ());
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Method to update the contract with new WASM code
-    pub fn update(env: Env, hash: BytesN<32>) -> Result<(), Error> {
-        // Require authentication from the current contract address
-        env.current_contract_address().require_auth();
-
-        // Update the contract's WASM code with the new hash
-        env.deployer().update_current_contract_wasm(hash);
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Helper method to update the count of admin signers
-    fn update_admin_signer_count(env: &Env, add: bool) {
-        // Get the current count of admin signers from instance storage, defaulting to 0
-        let count = env
-            .storage()
-            .instance()
-            .get::<Symbol, i32>(&ADMIN_SIGNER_COUNT)
-            .unwrap_or(0)
-            + if add { 1 } else { -1 };
-
-        // If the count is less than or equal to 0, trigger an error
-        if count <= 0 {
-            panic_with_error!(env, Error::NotPermitted)
-        }
-
-        // Update the admin signer count in instance storage
-        env.storage()
-            .instance()
-            .set::<Symbol, i32>(&ADMIN_SIGNER_COUNT, &count);
-    }
-}
-
-```
-
-#### Estructura de la firma
-
-Esta estructura representa una firma WebAuthn.
-
-```rust
-#[contracttype]
-pub struct Signature {
-    pub id: Bytes,
-    pub authenticator_data: Bytes,
-    pub client_data_json: Bytes,
-    pub signature: BytesN<64>,
-}
-```
-
-#### Implementación de CustomAccountInterface
-
-Esto implementa la lógica de autenticación principal para la billetera WebAuthn.
-
-```rust
-#[contractimpl]
-impl CustomAccountInterface for Contract {
-    // Defining the error and signature types for the trait
-    type Error = Error;
-    type Signature = Signature;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,                         // The environment context
-        signature_payload: Hash<32>,      // The payload that needs to be signed
-        signature: Signature,             // The signature provided by the client
-        auth_contexts: Vec<Context>,      // Contexts for authentication
-    ) -> Result<(), Error> {
-        // Destructure the signature into its components
-        let Signature {
-            id,
-            mut authenticator_data,
-            client_data_json,
-            signature,
-        } = signature;
-
-        // Set the maximum time-to-live (TTL) for storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Try to retrieve the public key associated with the id from temporary storage
-        let pk = match env.storage().temporary().get(&id) {
-            Some(pk) => {
-                // Check if a session signer is trying to perform protected actions
-                for context in auth_contexts.iter() {
-                    match context {
-                        // If the context is a contract call
-                        Context::Contract(c) => {
-                            // Ensure that the current contract is not performing restricted actions
-                            if c.contract == env.current_contract_address()
-                                && (c.fn_name != symbol_short!("remove")
-                                    || (c.fn_name == symbol_short!("remove")
-                                        && Bytes::from_val(&env, &c.args.get(0).unwrap()) != id))
-                            {
-                                return Err(Error::NotPermitted);
-                            }
-                        }
-                        _ => {} // Allow other contexts (e.g., deploying new contracts)
-                    };
-                }
-
-                // Extend the TTL for the temporary storage entry
-                env.storage()
-                    .temporary()
-                    .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-                pk // Return the public key
-            }
-            // If not found in temporary storage, try persistent storage
-            None => {
-                env.storage()
-                    .persistent()
-                    .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-                env.storage().persistent().get(&id).ok_or(Error::NotFound)?
-            }
-        };
-
-        // Extend the authenticator data with the SHA-256 hash of the client data JSON
-        authenticator_data.extend_from_array(&env.crypto().sha256(&client_data_json).to_array());
-
-        // Verify the signature using the secp256r1 elliptic curve algorithm
-        env.crypto()
-            .secp256r1_verify(&pk, &env.crypto().sha256(&authenticator_data), &signature);
-
-        // Parse the client data JSON, extracting the base64 URL encoded challenge
-        let client_data_json = client_data_json.to_buffer::<1024>();
-        let client_data_json = client_data_json.as_slice();
-        let (client_data_json, _): (ClientDataJson, _) =
-            serde_json_core::de::from_slice(client_data_json).map_err(|_| Error::JsonParseError)?;
-
-        // Build the expected challenge from the signature payload
-        let mut expected_challenge = [0u8; 43];
-        base64_url::encode(&mut expected_challenge, &signature_payload.to_array());
-
-        // Check that the challenge inside the client data JSON matches the expected challenge
-        if client_data_json.challenge.as_bytes() != expected_challenge {
-            return Err(Error::ClientDataJsonChallengeIncorrect);
-        }
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        Ok(()) // Return success
-    }
-}
-```
-
-#### Codificación de url Base64
-
-Esta función proporciona la funcionalidad de codificación URL Base64 utilizada en el proceso WebAuthn.
-
-```rust
-// Define the Base64 URL alphabet as a constant byte array.
-const ALPHABET: &[u8] = b"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_";
-
-// The `encode` function takes a mutable reference to a destination byte array `dst` and a source byte array `src`.
-pub fn encode(dst: &mut [u8], src: &[u8]) {
-    // Initialize destination index `di` and source index `si` to 0.
-    let mut di: usize = 0;
-    let mut si: usize = 0;
-    // Calculate the length of the source array that is a multiple of 3.
-    let n = (src.len() / 3) * 3;-
-
-    // Process the source array in chunks of 3 bytes.
-    while si < n {
-        // Combine 3 bytes into a single 24-bit value.
-        let val = (src[si] as usize) << 16 | (src[si + 1] as usize) << 8 | (src[si + 2] as usize);
-        // Encode the 24-bit value into 4 Base64 characters.
-        dst[di] = ALPHABET[val >> 18 & 0x3F];
-        dst[di + 1] = ALPHABET[val >> 12 & 0x3F];
-        dst[di + 2] = ALPHABET[val >> 6 & 0x3F];
-        dst[di + 3] = ALPHABET[val & 0x3F];
-        // Increment the source index by 3 and the destination index by 4.
-        si += 3;
-        di += 4;
-    }
-
-    // Calculate the remaining number of bytes in the source array.
-    let remain = src.len() - si;
-
-    // If there are no remaining bytes, return early.
-    if remain == 0 {
-        return;
-    }
-
-    // Initialize a 24-bit value with the remaining byte(s).
-    let mut val = (src[si] as usize) << 16;
-
-    // If there are 2 remaining bytes, add the second byte to the 24-bit value.
-    if remain == 2 {
-        val |= (src[si + 1] as usize) << 8;
-    }
-
-    // Encode the remaining bytes into 2 or 3 Base64 characters.
-    dst[di] = ALPHABET[val >> 18 & 0x3F];
-    dst[di + 1] = ALPHABET[val >> 12 & 0x3F];
-
-    // If there are 2 remaining bytes, encode the third Base64 character.
-    if remain == 2 {
-        dst[di + 2] = ALPHABET[val >> 6 & 0x3F];
-    }
-}
-
-```
-
-#### Explicación escrita del código
-
-El contrato de la billetera WebAuthn gestiona las credenciales de usuario y la autenticación. Permite agregar y eliminar firmantes, diferenciando entre administradores y usuarios regulares. La función de añadir registra nuevos firmantes, almacenando claves de administrador de manera persistente y claves regulares de forma temporal. La función de eliminar borra firmantes, y actualizar permite mejoras del contrato. El núcleo de la seguridad de la billetera es la función `__check_auth`, que verifica las firmas WebAuthn. Verifica la firma contra la clave pública almacenada, valida el JSON de datos del cliente y asegúrate de que el desafío coincida con el valor esperado. El contrato utiliza las capacidades de almacenamiento de Soroban para gestionar claves y cantidades de administradores, con diferentes TTL (Tiempo de Vida) para almacenamiento persistente y temporal.
-
-#### Casos de prueba
-
-Estos son casos de prueba para asegurar que nuestra billetera WebAuthn esté funcionando correctamente. Utilizaremos las utilidades de prueba del SDK de Soroban para crear y ejecutar estas pruebas.
-
-```rust
-#[cfg(test)]
-mod test {
-    use std::println;
-    extern crate std;
-
-    use soroban_sdk::{
-        vec,
-        Bytes,
-        BytesN,
-        Env,
-        IntoVal,
-    };
-
-    use crate::{Contract, ContractClient, Error, Signature};
-
-    #[test]
-    fn test() {
-        let env = Env::default();
-        let deployee_address = env.register_contract(None, Contract);
-        let deployee_client = ContractClient::new(&env, &deployee_address);
-
-        // Test data
-        let id = Bytes::from_array(
-            &env,
-            &[243, 248, 216, 74, 226, 218, 85, 102, 196, 167, 14, 151, 124, 42, 73, 136, 138, 102, 187, 140],
-        );
-        let pk = BytesN::from_array(
-            &env,
-            &[4, 163, 142, 245, 242, 113, 55, 104, 189, 52, 128, 238, 206, 174, 194, 177, 4, 100,
-              161, 243, 177, 255, 10, 53, 57, 194, 205, 45, 208, 10, 131, 167, 93, 44, 123, 126, 95,
-              219, 207, 230, 175, 90, 96, 41, 121, 197, 127, 180, 74, 236, 160, 0, 60, 185, 211, 174,
-              133, 215, 200, 208, 230, 51, 210, 94, 214],
-        );
-
-        // Test adding a signer
-        deployee_client.add(&id, &pk, &true);
-
-        // Test authentication
-        let signature_payload = BytesN::from_array(
-            &env,
-            &[150, 22, 248, 96, 91, 4, 111, 72, 170, 101, 57, 225, 210, 199, 91, 29, 159, 227, 209,
-              6, 231, 63, 222, 209, 232, 57, 112, 98, 140, 118, 206, 245],
-        );
-
-        let signature = Signature {
-            authenticator_data: Bytes::from_array(
-                &env,
-                &[75, 74, 206, 229, 181, 139, 119, 89, 254, 159, 95, 149, 227, 164, 109, 143, 188,
-                  228, 143, 219, 181, 216, 77, 123, 142, 172, 60, 20, 162, 154, 181, 187, 29, 0, 0, 0, 0],
-            ),
-            client_data_json: Bytes::from_array(
-                &env,
-                &[123, 34, 116, 121, 112, 101, 34, 58, 34, 119, 101, 98, 97, 117, 116, 104, 110, 46,
-                  103, 101, 116, 34, 44, 34, 99, 104, 97, 108, 108, 101, 110, 103, 101, 34, 58, 34,
-                  108, 104, 98, 52, 89, 70, 115, 69, 98, 48, 105, 113, 90, 84, 110, 104, 48, 115,
-                  100, 98, 72, 90, 95, 106, 48, 81, 98, 110, 80, 57, 55, 82, 54, 68, 108, 119, 89,
-                  111, 120, 50, 122, 118, 85, 34, 44, 34, 111, 114, 105, 103, 105, 110, 34, 58, 34,
-                  104, 116, 116, 112, 115, 58, 47, 47, 112, 97, 115, 115, 107, 101, 121, 45, 107,
-                  105, 116, 45, 100, 101, 109, 111, 46, 112, 97, 103, 101, 115, 46, 100, 101, 118, 34, 125],
-            ),
-            id: id.clone(),
-            signature: BytesN::from_array(
-                &env,
-                &[74, 48, 29, 120, 181, 135, 255, 178, 105, 76, 82, 118, 29, 135, 193, 72, 123, 144,
-                  138, 214, 125, 27, 33, 159, 169, 200, 151, 55, 7, 250, 111, 172, 86, 89, 162, 167,
-                  148, 105, 144, 68, 21, 249, 61, 253, 80, 61, 54, 29, 14, 162, 12, 173, 206, 194,
-                  144, 227, 11, 225, 74, 254, 191, 221, 103, 86],
-            ),
-        };
-
-        let result: Result<(), Result<Error, _>> = env.try_invoke_contract_check_auth(
-            &deployee_address,
-            &signature_payload,
-            signature.into_val(&env),
-            &vec![&env],
-        );
-
-        println!("{:?}", result);
-        assert!(result.is_ok());
-
-    }
-}
-```
-
-#### Resumen
-
-Esta implementación de billetera WebAuthn proporciona una manera segura y fácil de gestionar activos digitales en Stellar. Aprovecha los beneficios de seguridad de WebAuthn mientras mantiene la flexibilidad necesaria para interacciones en blockchain.
-
-#### Código completo
-
-Aquí están todos los fragmentos apilados juntos en un solo archivo para conveniencia:
-
-```rust
-#![no_std]
-
-use soroban_sdk::{
-    auth::{Context, CustomAccountInterface},
-    contract, contracterror, contractimpl, contracttype,
-    crypto::Hash,
-    panic_with_error, symbol_short, Bytes, BytesN, Env, FromVal, Symbol, Vec,
-};
-
-#[contract]
-pub struct Contract;
-
-// Error definitions for the contract
-#[contracterror]
-#[derive(Copy, Clone, Eq, PartialEq, Debug)]
-pub enum Error {
-    NotFound = 1,
-    NotPermitted = 2,
-    ClientDataJsonChallengeIncorrect = 3,
-    Secp256r1PublicKeyParse = 4,
-    Secp256r1SignatureParse = 5,
-    Secp256r1VerifyFailed = 6,
-    JsonParseError = 7,
-}
-
-// Structure representing a WebAuthn signature
-#[contracttype]
-pub struct Signature {
-    pub id: Bytes,
-    pub authenticator_data: Bytes,
-    pub client_data_json: Bytes,
-    pub signature: BytesN<64>,
-}
-
-// Implementing the Contract struct with various methods
-#[contractimpl]
-impl Contract {
-    // Method to add a new signer, potentially as an admin
-    pub fn add(env: Env, id: Bytes, pk: BytesN<65>, mut admin: bool) -> Result<(), Error> {
-        // Check if the instance storage has the ADMIN_SIGNER_COUNT key
-        if env.storage().instance().has(&ADMIN_SIGNER_COUNT) {
-            // Require authentication from the current contract address
-            env.current_contract_address().require_auth();
-        } else {
-            // If it's the first signer, ensure they are an admin
-            admin = true;
-        }
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // If the signer is an admin
-        if admin {
-            // Check if the ID exists in temporary storage
-            if env.storage().temporary().has(&id) {
-                // Remove the ID from temporary storage
-                env.storage().temporary().remove(&id);
-            }
-
-            // Update the admin signer count by incrementing it
-            Self::update_admin_signer_count(&env, true);
-
-            // Store the public key in persistent storage with the given ID
-            env.storage().persistent().set(&id, &pk);
-
-            // Extend the TTL for the persistent storage entry
-            env.storage()
-                .persistent()
-                .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-        } else {
-            // If the signer is not an admin
-            // Check if the ID exists in persistent storage
-            if env.storage().persistent().has(&id) {
-                // Update the admin signer count by decrementing it
-                Self::update_admin_signer_count(&env, false);
-
-                // Remove the ID from persistent storage
-                env.storage().persistent().remove(&id);
-            }
-
-            // Store the public key in temporary storage with the given ID
-            env.storage().temporary().set(&id, &pk);
-
-            // Extend the TTL for the temporary storage entry
-            env.storage()
-                .temporary()
-                .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-        }
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Publish an event indicating a new signer has been added
-        env.events()
-            .publish((EVENT_TAG, symbol_short!("add"), id, pk), admin);
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Method to remove a signer
-    pub fn remove(env: Env, id: Bytes) -> Result<(), Error> {
-        // Require authentication from the current contract address
-        env.current_contract_address().require_auth();
-
-        // Check if the ID exists in temporary storage
-        if env.storage().temporary().has(&id) {
-            // Remove the ID from temporary storage
-            env.storage().temporary().remove(&id);
-        } else if env.storage().persistent().has(&id) {
-            // If the ID exists in persistent storage, decrement the admin signer count
-            Self::update_admin_signer_count(&env, false);
-
-            // Remove the ID from persistent storage
-            env.storage().persistent().remove(&id);
-        }
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Publish an event indicating a signer has been removed
-        env.events()
-            .publish((EVENT_TAG, symbol_short!("remove"), id), ());
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Method to update the contract with new WASM code
-    pub fn update(env: Env, hash: BytesN<32>) -> Result<(), Error> {
-        // Require authentication from the current contract address
-        env.current_contract_address().require_auth();
-
-        // Update the contract's WASM code with the new hash
-        env.deployer().update_current_contract_wasm(hash);
-
-        // Get the maximum time-to-live (TTL) for the storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        // Return Ok indicating success
-        Ok(())
-    }
-
-    // Helper method to update the count of admin signers
-    fn update_admin_signer_count(env: &Env, add: bool) {
-        // Get the current count of admin signers from instance storage, defaulting to 0
-        let count = env
-            .storage()
-            .instance()
-            .get::<Symbol, i32>(&ADMIN_SIGNER_COUNT)
-            .unwrap_or(0)
-            + if add { 1 } else { -1 };
-
-        // If the count is less than or equal to 0, trigger an error
-        if count <= 0 {
-            panic_with_error!(env, Error::NotPermitted)
-        }
-
-        // Update the admin signer count in instance storage
-        env.storage()
-            .instance()
-            .set::<Symbol, i32>(&ADMIN_SIGNER_COUNT, &count);
-    }
-}
-
-// Implementing the core authentication logic for the WebAuthn wallet
-#[contractimpl]
-impl CustomAccountInterface for Contract {
-    // Defining the error and signature types for the trait
-    type Error = Error;
-    type Signature = Signature;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,                         // The environment context
-        signature_payload: Hash<32>,      // The payload that needs to be signed
-        signature: Signature,             // The signature provided by the client
-        auth_contexts: Vec<Context>,      // Contexts for authentication
-    ) -> Result<(), Error> {
-        // Destructure the signature into its components
-        let Signature {
-            id,
-            mut authenticator_data,
-            client_data_json,
-            signature,
-        } = signature;
-
-        // Get the maximum time-to-live (TTL) for storage entries
-        let max_ttl = env.storage().max_ttl();
-
-        // Try to retrieve the public key associated with the id from temporary storage
-        let pk = match env.storage().temporary().get(&id) {
-            Some(pk) => {
-                // Check if a session signer is trying to perform protected actions
-                for context in auth_contexts.iter() {
-                    match context {
-                        // If the context is a contract call
-                        Context::Contract(c) => {
-                            // Ensure that the current contract is not performing restricted actions
-                            if c.contract == env.current_contract_address()
-                                && (c.fn_name != symbol_short!("remove")
-                                    || (c.fn_name == symbol_short!("remove")
-                                        && Bytes::from_val(&env, &c.args.get(0).unwrap()) != id))
-                            {
-                                return Err(Error::NotPermitted);
-                            }
-                        }
-                        _ => {} // Allow other contexts (e.g., deploying new contracts)
-                    };
-                }
-
-                // Extend the TTL for the temporary storage entry
-                env.storage()
-                    .temporary()
-                    .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-                pk // Return the public key
-            }
-            // If not found in temporary storage, try persistent storage
-            None => {
-                env.storage()
-                    .persistent()
-                    .extend_ttl(&id, max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-                env.storage().persistent().get(&id).ok_or(Error::NotFound)?
-            }
-        };
-
-        // Extend the authenticator data with the SHA-256 hash of the client data JSON
-        authenticator_data.extend_from_array(&env.crypto().sha256(&client_data_json).to_array());
-
-        // Verify the signature using the secp256r1 elliptic curve algorithm
-        env.crypto()
-            .secp256r1_verify(&pk, &env.crypto().sha256(&authenticator_data), &signature);
-
-        // Parse the client data JSON, extracting the base64 URL encoded challenge
-        let client_data_json = client_data_json.to_buffer::<1024>();
-        let client_data_json = client_data_json.as_slice();
-        let (client_data_json, _): (ClientDataJson, _) =
-            serde_json_core::de::from_slice(client_data_json).map_err(|_| Error::JsonParseError)?;
-
-        // Build the expected challenge from the signature payload
-        let mut expected_challenge = [0u8; 43];
-        base64_url::encode(&mut expected_challenge, &signature_payload.to_array());
-
-        // Check that the challenge inside the client data JSON matches the expected challenge
-        if client_data_json.challenge.as_bytes() != expected_challenge {
-            return Err(Error::ClientDataJsonChallengeIncorrect);
-        }
-
-        // Extend the TTL for the instance storage
-        env.storage()
-            .instance()
-            .extend_ttl(max_ttl - WEEK_OF_LEDGERS, max_ttl);
-
-        Ok(()) // Return success
-    }
-}
-
-// Define the Base64 URL alphabet as a constant byte array.
-const ALPHABET: &[u8] = b"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_";
-
-// The `encode` function takes a mutable reference to a destination byte array `dst` and a source byte array `src`.
-pub fn encode(dst: &mut [u8], src: &[u8]) {
-    // Initialize destination index `di` and source index `si` to 0.
-    let mut di: usize = 0;
-    let mut si: usize = 0;
-    // Calculate the length of the source array that is a multiple of 3.
-    let n = (src.len() / 3) * 3;
-
-    // Process the source array in chunks of 3 bytes.
-    while si < n {
-        // Combine 3 bytes into a single 24-bit value.
-        let val = (src[si] as usize) << 16 | (src[si + 1] as usize) << 8 | (src[si + 2] as usize);
-        // Encode the 24-bit value into 4 Base64 characters.
-        dst[di] = ALPHABET[val >> 18 & 0x3F];
-        dst[di + 1] = ALPHABET[val >> 12 & 0x3F];
-        dst[di + 2] = ALPHABET[val >> 6 & 0x3F];
-        dst[di + 3] = ALPHABET[val & 0x3F];
-        // Increment the source index by 3 and the destination index by 4.
-        si += 3;
-        di += 4;
-    }
-
-    // Calculate the remaining number of bytes in the source array.
-    let remain = src.len() - si;
-
-    // If there are no remaining bytes, return early.
-    if remain == 0 {
-        return;
-    }
-
-    // Initialize a 24-bit value with the remaining byte(s).
-    let mut val = (src[si] as usize) << 16;
-
-    // If there are 2 remaining bytes, add the second byte to the 24-bit value.
-    if remain == 2 {
-        val |= (src[si + 1] as usize) << 8;
-    }
-
-    // Encode the remaining bytes into 2 or 3 Base64 characters.
-    dst[di] = ALPHABET[val >> 18 & 0x3F];
-    dst[di + 1] = ALPHABET[val >> 12 & 0x3F];
-
-    // If there are 2 remaining bytes, encode the third Base64 character.
-    if remain == 2 {
-        dst[di + 2] = ALPHABET[val >> 6 & 0x3F];
-    }
-}
-
-#[cfg(test)]
-mod test {
-    use std::println;
-    extern crate std;
-
-    use soroban_sdk::{
-        vec,
-        Bytes,
-        BytesN,
-        Env,
-        IntoVal,
-    };
-
-    use crate::{Contract, ContractClient, Error, Signature};
-
-    #[test]
-    fn test() {
-        let env = Env::default();
-        let deployee_address = env.register_contract(None, Contract);
-        let deployee_client = ContractClient::new(&env, &deployee_address);
-
-        // Test data
-        let id = Bytes::from_array(
-            &env,
-            &[243, 248, 216, 74, 226, 218, 85, 102, 196, 167, 14, 151, 124, 42, 73, 136, 138, 102, 187, 140],
-        );
-        let pk = BytesN::from_array(
-            &env,
-            &[4, 163, 142, 245, 242, 113, 55, 104, 189, 52, 128, 238, 206, 174, 194, 177, 4, 100,
-              161, 243, 177, 255, 10, 53, 57, 194, 205, 45, 208, 10, 131, 167, 93, 44, 123, 126, 95,
-              219, 207, 230, 175, 90, 96, 41, 121, 197, 127, 180, 74, 236, 160, 0, 60, 185, 211, 174,
-              133, 215, 200, 208, 230, 51, 210, 94, 214],
-        );
-
-        // Test adding a signer
-        deployee_client.add(&id, &pk, &true);
-
-        // Test authentication
-        let signature_payload = BytesN::from_array(
-            &env,
-            &[150, 22, 248, 96, 91, 4, 111, 72, 170, 101, 57, 225, 210, 199, 91, 29, 159, 227, 209,
-              6, 231, 63, 222, 209, 232, 57, 112, 98, 140, 118, 206, 245],
-        );
-
-        let signature = Signature {
-            authenticator_data: Bytes::from_array(
-                &env,
-                &[75, 74, 206, 229, 181, 139, 119, 89, 254, 159, 95, 149, 227, 164, 109, 143, 188,
-                  228, 143, 219, 181, 216, 77, 123, 142, 172, 60, 20, 162, 154, 181, 187, 29, 0, 0, 0, 0],
-            ),
-            client_data_json: Bytes::from_array(
-                &env,
-                &[123, 34, 116, 121, 112, 101, 34, 58, 34, 119, 101, 98, 97, 117, 116, 104, 110, 46,
-                  103, 101, 116, 34, 44, 34, 99, 104, 97, 108, 108, 101, 110, 103, 101, 34, 58, 34,
-                  108, 104, 98, 52, 89, 70, 115, 69, 98, 48, 105, 113, 90, 84, 110, 104, 48, 115,
-                  100, 98, 72, 90, 95, 106, 48, 81, 98, 110, 80, 57, 55, 82, 54, 68, 108, 119, 89,
-                  111, 120, 50, 122, 118, 85, 34, 44, 34, 111, 114, 105, 103, 105, 110, 34, 58, 34,
-                  104, 116, 116, 112, 115, 58, 47, 47, 112, 97, 115, 115, 107, 101, 121, 45, 107,
-                  105, 116, 45, 100, 101, 109, 111, 46, 112, 97, 103, 101, 115, 46, 100, 101, 118, 34, 125],
-            ),
-            id: id.clone(),
-            signature: BytesN::from_array(
-                &env,
-                &[74, 48, 29, 120, 181, 135, 255, 178, 105, 76, 82, 118, 29, 135, 193, 72, 123, 144,
-                  138, 214, 125, 27, 33, 159, 169, 200, 151, 55, 7, 250, 111, 172, 86, 89, 162, 167,
-                  148, 105, 144, 68, 21, 249, 61, 253, 80, 61, 54, 29, 14, 162, 12, 173, 206, 194,
-                  144, 227, 11, 225, 74, 254, 191, 221, 103, 86],
-            ),
-        };
-
-        let result: Result<(), Result<Error, _>> = env.try_invoke_contract_check_auth(
-            &deployee_address,
-            &signature_payload,
-            signature.into_val(&env),
-            &vec![&env],
-        );
-
-        println!("{:?}", result);
-        assert!(result.is_ok());
-
-    }
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/cross-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/cross-contract.mdx
deleted file mode 100644
index 872be171e4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/cross-contract.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-title: Hacer llamadas entre contratos
-description: Llamar a un contrato inteligente desde otro contrato inteligente
----
-
-Al igual que desarrollar software en cualquier idioma, desarrollar un contrato inteligente Stellar con un conjunto de características ricas puede ser una tarea desafiante y que consume mucho tiempo. Afortunadamente, alguien más podría haber resuelto parte de tus incidencias o construir componentes que podrían ser reutilizados. La comunidad de código abierto es vibrante y la comunidad de Stellar no decepciona.
-
-Hay dos tipos de dependencias que se pueden introducir en un contrato inteligente Stellar:
-
-1. Se pueden usar otros crates de Rust (siempre que sean compatibles con el [dialecto Rust](../../../learn/fundamentals/contract-development/rust-dialect.mdx) de Soroban);
-2. Se puede usar otro contrato inteligente. Esto se conoce como una [llamada entre contratos](../../../learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx).
-
-En lo siguiente, veremos cómo se pueden aprovechar los contratos desde dentro de otro contrato.
-
-## Contrato como dependencia
-
-Si bien encontrar un contrato está fuera del alcance de esta guía, hay varios lugares que hay que tener en cuenta. La mayoría de los proyectos y dApps divulgan públicamente la dirección de su contrato inteligente Stellar en su sitio web. Con esta información, un [explorador de bloques](../../../tools/developer-tools/block-explorers.mdx) es una herramienta poderosa para entender cómo se está utilizando un contrato. Algunos exploradores también te permiten descargar el contrato compilado como un archivo Wasm. También hay proyectos que proporcionan un enlace para acceder al código mismo.
-
-:::info[Contract dirección]
-
-Para depender de un proyecto, necesitamos conocer la dirección del contrato del que vamos a depender.
-
-:::
-
-## API pública
-
-Se pueden llamar todas las funciones públicas de un contrato. Usar un explorador de red puede ser útil, ya que algunos proponen ver la interfaz de Rust de un contrato. Los bindings también se pueden generar usando el CLI:
-
-```bash
-stellar contract bindings rust --network --contract-id ... --output-dir ...
-```
-
-## Haciendo una llamada entre contratos
-
-Una vez que sabemos qué función llamar y qué argumentos usar, hay dos maneras principales de hacer una llamada entre contratos: podemos cargar el Wasm o llamar al contrato.
-
-Empecemos usando solo la dirección de un contrato. En este ejemplo, tenemos un contrato externo con una función pública llamada `add_with` que toma dos `u32` como valores de entrada para sumarlos.
-
-```rust
-#[contract]
-pub struct ContractB;
-
-#[contractimpl]
-impl ContractB {
-    pub fn add_with(env: Env, contract: Address, x: u32, y: u32) -> u32 {
-        env.invoke_contract(&contract, symbol_short!("add"), vec![&env, x.to_val(), y.to_val()])
-    }
-}
-```
-
-Usar solo el contrato viene con sus propios desafíos. Debido a que no tenemos acceso al código Wasm, no tenemos ninguna inferencia de tipos y tenemos que convertir manualmente las entradas de la función a `Val`. Si queremos más herramientas que nos ayuden, podemos cargar el código Wasm en el contrato. Esto nos permite pasar tipos normales sin necesitar conversiones manuales de nuestra parte. Detrás de escena, esta manera de hacerlo es simplemente un envoltorio conveniente alrededor de `env.invoke_contract`.
-
-```rust
-mod contract_a {
-    soroban_sdk::contractimport!(
-        file = "soroban_contract_a.wasm"
-    );
-}
-
-#[contract]
-pub struct ContractB;
-
-#[contractimpl]
-impl ContractB {
-    pub fn add_with(env: Env, contract: Address, x: u32, y: u32) -> u32 {
-        let client = contract_a::Client::new(&env, &contract);
-        client.add(&x, &y)
-    }
-}
-```
-
-Aunque tenemos acceso al Wasm, aún necesitamos una dirección de contrato porque podría haber múltiples contratos desplegados en la cadena que usan el mismo código subyacente. Esto puede ser importante si, por ejemplo, la función que necesitas requiere acceso a valores almacenados de otros usuarios.
-
-:::tip[Address y Wasm]
-
-Gracias a los bindings de Rust del contrato externo, también podemos usar cualquier enumeración pública del contrato como si las hubiéramos definido dentro de nuestro propio contrato.
-
-```rust
-client::ContractAEnum::SomeField
-```
-
-:::
-
-## Manejo de respuestas
-
-En los ejemplos anteriores, hemos utilizado `env.invoke_contract` y `client.some_function`. En ambos casos, si hay un problema con la llamada al contrato subyacente, el contrato entrará en pánico. Este podría ser un enfoque válido, pero en algunos casos queremos capturar errores y manejarlos dependiendo del resultado. Esto es para transmitir un mensaje de error personalizado, o incluso desencadenar un camino de código alternativo.
-
-Ingresa `try_`. Al usar `env.try_invoke_contract` o `client.try_some_function`, los errores subyacentes no harán que el contrato entre en pánico. En su lugar, los errores se envolverán y se pueden manejar. Por ejemplo, si quisiéramos establecer como predeterminado 0 en caso de un error:
-
-```rust
-client.try_add(&x, &y).unwrap_or(Ok(0)).unwrap()
-```
-
-Por supuesto, podríamos tener un manejo de errores mucho más complejo aprovechando la declaración `match`:
-
-```rust
-match client.try_add(&x, &y) {
-    // the contract returned a value
-    Ok(Ok(number)) => todo!("do something with the number returned"),
-    Ok(Err(ConversionError)) => todo!("got a value back, but it wasn't a number like we expected"),
-
-    // the contract errored
-    Err(Ok(Error::AnError)) => todo!("do something when an error occurs that the contract included in its contract spec"),
-    Err(Err(status)) => todo!("do something when an unrecognized error, or system error, occurs"),
-}
-```
-
-## Dependiendo de otro contrato
-
-Felicidades, ahora puedes aprovechar eficazmente todo el ecosistema de Soroban y su multitud de contratos inteligentes. Hay un último punto a discutir antes de cerrar: **dependencia**.
-
-Al igual que al llamar a cualquier contrato inteligente, depender de un contrato inteligente externo debe hacerse con cuidado. Es aconsejable hacer tu propia investigación y análisis sobre el contrato que deseas utilizar. Como los contratos se pueden actualizar sin que su dirección cambie, es importante prestar atención a cualquier cambio en el código subyacente.
-
-:::tip[Contract Wasm]
-
-Se puede obtener el Wasm utilizando el [Stellar CLI](../../../tools/cli/README.mdx). Esto puede servir como una manera rápida de (por ejemplo) automatizar una verificación de hash en un sistema de integración continua. Sin embargo, tal verificación no proporcionaría fuertes garantías en la cadena, ¡pero uno podría construir un contrato para eso!
-
-```bash
-stellar contract fetch --id C... --network ... > contract.wasm
-```
-
-:::
-
-Además de esta consideración de seguridad, actualizar un contrato es una parte integral del ciclo de vida de un contrato. Se añaden nuevas características, se corrigen errores y se realizan cambios en la API pública. Aquí también, es importante observar cualquier desarrollo en estos contratos para garantizar el funcionamiento continuo de tu propio contrato.
-
-## Ejemplos
-
-Consulta el siguiente ejemplo completo con pruebas:
-
-- [Llamadas entre contratos](../../smart-contracts/example-contracts/cross-contract-call.mdx) muestra cómo crear dos contratos, desplegarlos y luego cómo llamar a uno desde el otro.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/deploy-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/deploy-contract.mdx
deleted file mode 100644
index e8c23663b7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/deploy-contract.mdx
+++ /dev/null
@@ -1,241 +0,0 @@
----
-title: Desplegar un contrato a partir de bytecode Wasm instalado usando un contrato desplegador
-description: Desplegar un contrato a partir de bytecode Wasm instalado usando un contrato desplegador
----
-
-<head>
-  <title>
-    {`Desplegar un contrato a partir de bytecode Wasm instalado usando un contrato desplegador`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Desplegar un contrato a partir de bytecode Wasm instalado usando un contrato desplegador"
-  />
-  <meta
-    property="og:description"
-    content="Desplegar un contrato a partir de bytecode Wasm instalado usando un contrato desplegador"
-  />
-</head>
-
-## Descripción general
-
-Esta guía te lleva a través del proceso de desplegar un contrato inteligente a partir de bytecode Wasm instalado usando un contrato desplegador. Cubriremos la configuración de tu entorno, la carga de bytecode Wasm y el despliegue e inicialización de un contrato de forma atómica.
-
-### Requisitos previos:
-
-- Conocimiento básico del [lenguaje de programación Rust](https://www.rust-lang.org/). Para refrescarte en Rust, visita [Rustlings](https://github.com/rust-lang/rustlings) o [El libro de Rust](https://doc.rust-lang.org/book/).
-- Familiaridad con [contratos inteligentes Stellar](../../smart-contracts/getting-started/hello-world.mdx)
-- Cargo instalado, [Stellar CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli) y SDK de Soroban
-
-### Configuración del entorno
-
-El [ejemplo de desplegador](https://github.com/stellar/soroban-examples/tree/v22.0.1/deployer) demuestra cómo desplegar contratos usando un contrato.
-
-1. Clona el repositorio de ejemplos de Soroban:
-
-```bash
-git clone -b v20.2.0 https://github.com/stellar/soroban-examples
-```
-
-2. Navega al ejemplo de desplegador:
-
-```bash
-cd soroban-examples/deployer/deployer
-```
-
-:::note
-
-Para que este ejemplo funcione, debes navegar a `deployer/contracts` y `deployer/deployer` y ejecutar el comando `stellar contract build` en cada directorio para generar los archivos de destino.
-
-:::
-
-3. Ejecuta pruebas:
-
-En el `deployer/deployer`, ejecuta el siguiente comando:
-
-```bash
-cargo test
-```
-
-Deberías ver la salida indicando que las pruebas pasaron:
-
-```bash
-running 2 tests
-test test::test_deploy_from_contract ... ok
-test test::test_deploy_from_address ... ok
-```
-
-### Descripción del código
-
-```rust title="deployer/deployer/src/lib.rs"
-#[contract]
-pub struct Deployer;
-
-#[contractimpl]
-impl Deployer {
-    /// Deploy the contract Wasm and after deployment invoke the init function
-    /// of the contract with the given arguments.
-    ///
-    /// This has to be authorized by `deployer` (unless the `Deployer` instance
-    /// itself is used as deployer). This way the whole operation is atomic
-    /// and it's not possible to frontrun the contract initialization.
-    ///
-    /// Returns the contract address and result of the init function.
-    pub fn deploy(
-        env: Env,
-        deployer: Address,
-        wasm_hash: BytesN<32>,
-        salt: BytesN<32>,
-        init_fn: Symbol,
-        init_args: Vec<Val>,
-    ) -> (Address, Val) {
-        // Skip authorization if deployer is the current contract.
-        if deployer != env.current_contract_address() {
-            deployer.require_auth();
-        }
-
-        // Deploy the contract using the uploaded Wasm with given hash.
-        let deployed_address = env
-            .deployer()
-            .with_address(deployer, salt)
-            .deploy(wasm_hash);
-
-        // Invoke the init function with the given arguments.
-        let res: Val = env.invoke_contract(&deployed_address, &init_fn, init_args);
-        // Return the contract ID of the deployed contract and the result of
-        // invoking the init result.
-        (deployed_address, res)
-    }
-}
-```
-
-## Cómo funciona
-
-El contrato desplegador proporciona un mecanismo para desplegar otros contratos de manera segura y determinista. Asegura que el despliegue esté autorizado por la dirección de desplegador especificada y admite la inicialización atómica del contrato recién desplegado. Esto garantiza que el contrato esté correctamente inicializado inmediatamente después del despliegue, previniendo cualquier problema potencial con contratos no inicializados.
-
-### Desglose de funciones
-
-- `env: Env`: El objeto Env representa el entorno de ejecución del contrato actual. Proporciona métodos para interactuar con la blockchain y otros contratos, así como realizar varias operaciones.
-- `deployer: Address`: La dirección de la entidad que está solicitando el despliegue del contrato. Esta dirección se utilizará para autorizar el despliegue.
-- `wasm_hash: BytesN<32>`: El hash del bytecode Wasm del contrato que se va a desplegar y que debe estar ya instalado y en el ledger. Este hash se utiliza para identificar de manera única el código del contrato.
-- `salt: BytesN<32>`: Un valor único utilizado para derivar la dirección del contrato desplegado. La misma combinación de dirección del desplegador y sal siempre producirá la misma dirección de contrato desplegado, asegurando direcciones de contrato deterministas.
-- `init_fn: Symbol`: El nombre de la función de inicialización que se llamará en el contrato recién desplegado.
-- `init_args: Vec<Val>`: Un vector de argumentos, especificados como objetos `{type: value}`, que se pasarán a la función de inicialización del contrato desplegado.
-
-### Pasos de la función
-
-```rust
-if deployer != env.current_contract_address() {
-   deployer.require_auth();
-}
-```
-
-La función verifica si la dirección `deployer` es la misma que la dirección del contrato actual. Si no lo es, requiere autorización de la dirección del desplegador para asegurar que el desplegador ha permitido este despliegue.
-
-```rust
-let deployed_address = env
-   .deployer()
-   .with_address(deployer, salt)
-   .deploy(wasm_hash);
-```
-
-- Usa el método `env.deployer()` para crear un objeto desplegador.
-- `with_address(deployer, salt)` especifica la dirección del desplegador y la sal para derivar la nueva dirección del contrato.
-- `deploy(wasm_hash)` despliega el contrato usando el hash de bytecode Wasm proporcionado y devuelve la dirección del contrato recién desplegado.
-
-```rust
-let res: Val = env.invoke_contract(&deployed_address, &init_fn, init_args);
-```
-
-- Invoca la función de inicialización especificada (`init_fn`) en el contrato recién desplegado (`deployed_address`), pasando los argumentos de inicialización proporcionados (`init_args`).
-- El resultado de esta llamada a la función se almacena en `res`.
-
-```rust
-(deployed_address, res)
-```
-
-Devuelve una tupla que contiene la dirección del contrato recién desplegado y el resultado de la función de inicialización.
-
-### Construir los contratos
-
-Para construir el contrato en un archivo `.wasm`, usa el comando `stellar contract build`. Este comando construye tanto el contrato desplegador como el contrato de prueba.
-
-```sh
-stellar contract build
-```
-
-Ambos archivos `.wasm` deberían encontrarse en ambos directorios de destino del contrato después de construir ambos contratos:
-
-```
-target/wasm32v1-none/release/soroban_deployer_contract.wasm
-```
-
-```
-target/wasm32v1-none/release/soroban_deployer_test_contract.wasm
-```
-
-## Ejecutar el contrato
-
-Antes de desplegar el contrato de prueba con el desplegador, instala el bytecode Wasm del contrato de prueba usando el comando `install`. El comando `install` imprimirá el hash derivado del archivo Wasm que debe ser utilizado por el desplegador.
-
-```sh
-stellar contract upload \
---wasm  contract/target/wasm32v1-none/release/soroban_deployer_test_contract.wasm \
---source-account alice \
---network testnet
-```
-
-Al desplegar un contrato inteligente en la red, debes especificar una identidad que se utilizará para firmar las transacciones. Cambia la [identidad] `alice` por la tuya.
-
-[identidad]: ../../smart-contracts/getting-started/setup.mdx#configure-an-identity
-
-El comando imprime el hash en formato hexadecimal. Se verá algo así como `6bc6d975ef99c057231481c40f69f4c2a8a89ac56e8826ef0378f8e5c6abc4be`.
-
-También necesitamos desplegar el contrato `Deployer`:
-
-```sh
-stellar contract deploy \
-  --wasm deployer/target/wasm32v1-none/release/soroban_deployer_contract.wasm \
-  --source-account alice  \
-  --network testnet
-```
-
-Esto devolverá la dirección del desplegador. Por ejemplo: `CDKYZMA3OXR54YAHOQ5D4EWDFDT3ZNKKRYKQT7MGPWH22ZVD2DX2BJID`.
-
-Luego, el contrato desplegador puede ser invocado con el valor hash de Wasm anterior.
-
-```sh
-stellar contract invoke \
-  --id CDKYZMA3OXR54YAHOQ5D4EWDFDT3ZNKKRYKQT7MGPWH22ZVD2DX2BJID \
-  --source-account alice \
-  --network testnet \
-  -- \
-  deploy \
-  --deployer CDKYZMA3OXR54YAHOQ5D4EWDFDT3ZNKKRYKQT7MGPWH22ZVD2DX2BJID \
-  --salt 123 \
-  --wasm_hash 6bc6d975ef99c057231481c40f69f4c2a8a89ac56e8826ef0378f8e5c6abc4be \
-  --init_fn init \
-  --init_args '[{"u32":8}]'
-```
-
-reemplaza `alice` con tu propia identidad
-
-La invocación del contrato desplegador devolverá la dirección del contrato (por ejemplo: `CCTVFX6BFTQHTGAHA5TY4YZQJRUKRE2RRNUTGVBNKE3PJF5C7CI53APY`) del contrato de prueba que se ha desplegado recientemente.
-
-Invoca el contrato de prueba desplegado usando la dirección devuelta del comando anterior.
-
-```sh
-stellar contract invoke \
-  --id CCTVFX6BFTQHTGAHA5TY4YZQJRUKRE2RRNUTGVBNKE3PJF5C7CI53APY \
-  --source-account alice \
-  --network testnet \
-  -- \
-  value
-```
-
-Deberías recibir algo como la siguiente salida:
-
-```json
-8
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/deploy-sac-with-code.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/deploy-sac-with-code.mdx
deleted file mode 100644
index 2653e3e558..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/deploy-sac-with-code.mdx
+++ /dev/null
@@ -1,153 +0,0 @@
----
-title: Desplegar un SAC para un activo Stellar utilizando código
-description: Desplegar un SAC para un activo Stellar utilizando el SDK de Javascript
----
-
-<head>
-  <title>
-    {`Desplegar un Contrato de Activo Stellar (SAC) para un activo Stellar utilizando código`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Desplegar un Contrato de Activo Stellar (SAC) para un activo Stellar utilizando código"
-  />
-  <meta
-    property="og:description"
-    content="Esta es una guía paso a paso para ayudarte a desplegar un SAC para un activo Stellar utilizando el SDK de Stellar."
-  />
-</head>
-
-## Resumen
-
-En esta guía, aprenderás a desplegar un [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) para un activo Stellar utilizando el [Stellar SDK](../../../tools/sdks/client-sdks.mdx#javascript-sdk). El SDK de Stellar es un conjunto de herramientas y una biblioteca diseñadas para ayudar a los desarrolladores a construir aplicaciones que interactúan con la red de blockchain de Stellar.
-
-### Requisitos previos:
-
-- - [Node.js ](https://nodejs.org/en) y npm instalados.
-- - SDK de Stellar para [JavaScript](https://www.npmjs.com/package/@stellar/stellar-sdk) instalado
-- [Conocimiento sobre cómo emitir un activo en Stellar](../../../tokens/how-to-issue-an-asset.mdx)
-- Una comprensión de la función rudimentaria de sondeo de transacciones habilitada para reintentos `submitTx` que describimos en [otra guía](../transactions/submit-transaction-wait-js.mdx)
-
-## Resumen del código
-
-```javascript title="deployassetcontract.js"
-import * as StellarSdk from "@stellar/stellar-sdk";
-import { Server } from "@stellar/stellar-sdk/rpc";
-
-const networkRPC = "https://soroban-testnet.stellar.org";
-const server = new Server(networkRPC);
-const networkPassphrase = StellarSdk.Networks.TESTNET;
-
-const deployStellarAssetContract = async () => {
-  const sourceSecrets =
-    "SASI6PA4K52GQJF6BC263GLYOADVKFJ4SZ7TFX4QQF2U76T3EJ54DT7Y"; // Replace with your Secret Key
-  const sourceKeypair = StellarSdk.Keypair.fromSecret(sourceSecrets);
-  const sourceAccount = await server.getAccount(sourceKeypair.publicKey());
-
-  try {
-    const assetCode = "JOEBOY";
-    const issuerPublicKey = sourceKeypair.publicKey();
-    const customAsset = new StellarSdk.Asset(assetCode, issuerPublicKey);
-
-    const transaction = new StellarSdk.TransactionBuilder(sourceAccount, {
-      fee: StellarSdk.BASE_FEE,
-      networkPassphrase,
-    })
-      .addOperation(
-        StellarSdk.Operation.createStellarAssetContract({
-          asset: customAsset,
-        }),
-      )
-      .setTimeout(30)
-      .build();
-
-    const uploadTx = await server.prepareTransaction(transaction);
-    uploadTx.sign(sourceKeypair);
-
-    const feedback = await submitTx(uploadTx);
-    const contract = StellarSdk.Address.fromScAddress(
-      feedback.returnValue.address(),
-    );
-    console.log(
-      `ContractID of Our ${customAsset.code} Asset`,
-      contract.toString(),
-    );
-  } catch (e) {
-    console.error("An error occurred while Deploying assets:", e);
-  }
-};
-
-await deployStellarAssetContract();
-```
-
-## Explicación del código
-
-**Configuración del servidor**
-
-```javascript
-import * as StellarSdk from "@stellar/stellar-sdk";
-
-const networkRPC = "https://soroban-testnet.stellar.org";
-const server = new StellarSdk.rpc.Server(networkRPC);
-const network_passphrase = StellarSdk.Networks.TESTNET;
-```
-
-- `networkRPC`: La URL para la red de pruebas Soroban.
-- `server`: Se crea una nueva instancia de `rpc.Server`, que se utilizará para interactuar con la red de pruebas de Soroban.
-- `network_passphrase`: establece la frase de la red a TESTNET
-
-**Función `DeployStellarAssetContract`**
-
-```javascript
-const deployStellarAssetContract = async () => {
-  const sourceSecrets =
-    "SASI6PA4K52GQJF6BC263GLYOADVKFJ4SZ7TFX4QQF2U76T3EJ54DT7Y"; // Replace with your Secret Key
-  const networkPassphrase = StellarSdk.Networks.TESTNET;
-  const sourceKeypair = StellarSdk.Keypair.fromSecret(sourceSecrets);
-  const sourceAccount = await server.getAccount(sourceKeypair.publicKey());
-
-  try {
-    const assetCode = "JOEBOY";
-    const issuerPublicKey = sourceKeypair.publicKey();
-    const customAsset = new StellarSdk.Asset(assetCode, issuerPublicKey);
-
-    const transaction = new StellarSdk.TransactionBuilder(sourceAccount, {
-      fee: StellarSdk.BASE_FEE,
-      networkPassphrase,
-    })
-      .addOperation(
-        StellarSdk.Operation.createStellarAssetContract({
-          asset: customAsset,
-        }),
-      )
-      .setTimeout(30)
-      .build();
-
-    const uploadTx = await server.prepareTransaction(transaction);
-    uploadTx.sign(sourceKeypair);
-
-    const feedback = await submitTx(uploadTx);
-    const contract = StellarSdk.Address.fromScAddress(
-      feedback.returnValue.address(),
-    );
-    console.log(
-      `ContractID of Our ${customAsset.code} Asset`,
-      contract.toString(),
-    );
-  } catch (e) {
-    console.error("An error occurred while Deploying assets:", e);
-  }
-};
-
-await deployStellarAssetContract();
-```
-
-Esta función está diseñada para desplegar un Contrato de Activo Stellar (SAC) en la red de pruebas Soroban.
-
-- **Clave secreta**: Comienza definiendo la clave secreta para la cuenta fuente (`sourceSecrets`), que debes reemplazar con la tuya.
-- **Keypair y cuenta**: Genera el keypair a partir de la clave secreta y obtiene los detalles de la cuenta del servidor Soroban.
-- **Activo personalizado**: Define un activo personalizado con el código `JOEBOY` y la clave pública del emisor.
-- **Construcción de la transacción**: Se construye una transacción utilizando el `TransactionBuilder`, que incluye la operación `createStellarAssetContract` para el activo personalizado. La transacción se prepara y se firma.
-- **Enviar transacción**: La transacción firmada se envía a la red usando `server.sendTransaction`.
-- **Manejo de la Retroalimentación**: Espera la retroalimentación de la transacción utilizando la función `submitTx` para asegurar que ha tenido éxito. extrae el búfer del contrato de la retroalimentación y lo convierte en un ID de contrato utilizando `StellarSdk.Address`. finalmente, registra la ID del contrato para el activo desplegado.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/error-enum.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/error-enum.mdx
deleted file mode 100644
index 30d7423482..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/error-enum.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Organizar errores de contrato con un tipo de enumeración de errores
-hide_table_of_contents: true
-description: Gestionar y comunicar errores de contrato utilizando una estructura de enumeración almacenada como valores de Estado
----
-
-Una manera conveniente de gestionar y comunicar de manera significativa los errores de contrato es recopilarlos en una estructura de `enum`. Estos errores son un tipo especial de tipo entero de enumeración que se almacenan en el ledger como valores de Estado que contienen un código `u32`. Primero, crea la estructura `Error` en tu contrato inteligente.
-
-```rust
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum Error {
-    FirstError = 1,
-    AnotherError = 2,
-    YetAnotherError = 3,
-    GenericError = 4
-}
-```
-
-Luego, causa un pánico con un error cuando se cumplan las condiciones. Este ejemplo causará un pánico con el error especificado.
-
-```rust
-#[contractimpl]
-impl Contract {
-    pub fn causeerror(env: Env, error_code: u32) -> Result<(), Error> {
-        match error_code {
-            1 => Err(Error::FirstError),
-            2 => Err(Error::AnotherError),
-            3 => Err(Error::YetAnotherError),
-            _ => Err(Error::GenericError),
-        }
-    }
-}
-```
-
-Cuando se convierte a XDR, el valor se convierte en un `ScVal`, que contiene un `ScError`, que contiene el valor entero del error como error de contrato.
-
-```json
-{ "error": { "contractError": 1 } }
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/extending-wasm-ttl.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/extending-wasm-ttl.mdx
deleted file mode 100644
index abe79a7883..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/extending-wasm-ttl.mdx
+++ /dev/null
@@ -1,180 +0,0 @@
----
-title: Extender el TTL de un contrato desplegado con código
-description: Cómo extender el TTL del código Wasm de un contrato desplegado
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Extendiendo el TTL de un contrato desplegado usando código
-
-Cuando se despliega un contrato inteligente en la red Stellar, su código WebAssembly (Wasm) tiene un [Tiempo de Vida (TTL)](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#ttl) que determina cuánto tiempo permanece accesible.
-
-El TTL es el número de ledgers entre el ledger actual y el ledger final al que se puede acceder todavía a los datos del contrato. Si el TTL caduca, el código del contrato se archiva y se vuelve inaccesible. Para prevenir esto, necesitas extender periódicamente el TTL del código Wasm del contrato.
-
-Esta guía te mostrará cómo extender el TTL del código Wasm de un contrato desplegado utilizando los SDKs de Javascript y Rust.
-
-## Entendiendo el TTL en Soroban
-
-Antes de demostrar los métodos de extensión de TTL, debes tener en cuenta que en Soroban:
-
-- Las instancias de contrato y el código se almacenan en el almacenamiento de instancias
-- El TTL existe para evitar que la blockchain se llene de contratos inactivos
-- La extensión de TTL se puede hacer tanto para la instancia de contrato como para el código de contrato
-
-## Requisitos previos
-
-- Stellar SDK: `npm install @stellar/stellar-sdk` para Javascript
-- Un endpoint [Stellar RPC](../../../data/apis/rpc/README.mdx) (por ejemplo, `https://soroban-testnet.stellar.org`)
-- Conocimientos básicos del SDK en uso
-
-## Métodos para extender el TTL
-
-Esta guía cubrirá tres formas de extender el TTL de un contrato:
-
-1. Auto-extensión: Extender el TTL desde dentro del contrato mismo, en Rust.
-   - Caso de uso: Cuando un contrato necesita gestionar su propia vida útil
-   - Proceso: Accediendo directamente al almacenamiento de instancias del contrato para extender su TTL
-
-2. Extensión externa: Extender el TTL desde otro contrato (el desplegador), en Rust.
-   - Caso de uso: Al gestionar múltiples instancias de contratos o implementar control administrativo
-   - Proceso: Usando la autoridad del desplegador para extender el TTL de cualquier contrato que haya desplegado
-
-3. Extensión de cliente: Extender el TTL desde un cliente externo utilizando Javascript.
-   - Caso de uso: Cuando necesitas gestionar los TTL de los contratos a través de una aplicación externa o un sistema automatizado.
-   - Proceso:
-     - Obtener la huella del contrato
-     - Establecer una tarifa de recursos razonable (quizás comenzar en <b>10.000</b> stroops ya que esta es una operación costosa)
-     - Establecer los datos de Soroban como solo lectura
-     - Establecer el TTL del ledger deseado para caducar el contrato
-     - Crear una operación `StellarSdk.Operation.extendFootprintTtl`
-
-:::note
-
-Se cobran tanto una tarifa de recursos como una tarifa base en esta operación.
-
-:::
-
-<Tabs groupId="language" defaultValue="rust">
-<TabItem value="rust" label="Rust">
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, Env, symbol_short};
-
-#[contract]
-pub struct ExtendTTLContract;
-
-#[contractimpl]
-impl ExtendTTLContract {
-    // Self-extension
-    pub fn extend_contract_ttl(env: Env, threshold: u32, extend_to: u32) {
-        env.storage().instance().extend_ttl(threshold, extend_to);
-    }
-
-    // External extension
-    pub fn extend_other_contract_ttl(env: Env, contract_address: Address, threshold: u32, extend_to: u32) {
-        let deployer = env.deployer();
-        deployer.extend_ttl(
-            contract_address,
-            threshold,
-            extend_to
-        );
-    }
-}
-```
-
-- `env.storage().instance().extend_ttl(...)` se llama para extender el TTL de la instancia de contrato actual.
-- `threshold` es una verificación que asegura que el TTL actual de la instancia de contrato sea menor que el valor umbral establecido.
-- `extend_to` es el número de ledgers que se agregarán al TTL actual.
-- `contract_address` es la dirección de la instancia de contrato cuyo TTL queremos extender.
-- `env.deployer()` accede al desplegador, que tiene métodos para gestionar el ciclo de vida del contrato.
-- `deployer.extend_ttl(...)` extiende el TTL de la instancia de contrato especificada.
-
-</TabItem>
-<TabItem value="js" label="JS">
-
-El código a continuación utiliza el entorno de Nodejs, pero el mismo concepto también se puede aplicar en el navegador usando la billetera Freighter o usando cualquier otro [Stellar SDK](../../../tools/sdks/client-sdks.mdx).
-
-```javascript
-import * as StellarSdk from "@stellar/stellar-sdk";
-import { Server } from "@stellar/stellar-sdk/rpc";
-
-async function extendContractWasmTTL(contractId, sourceKeypair) {
-  const server = new Server("https://soroban-testnet.stellar.org");
-
-  // Create a new transaction builder
-  const account = await server.getAccount(sourceKeypair.publicKey());
-  const fee = "200100"; // Base fee plus resource fee
-
-  // Get the contract instance
-  const contract = new StellarSdk.Contract(contractId);
-  const instance = contract.getFootprint();
-
-  // Set the Soroban data and create an operation to extend the contract's TTL
-  const sorobanData = new StellarSdk.SorobanDataBuilder()
-    .setResourceFee(200_000)
-    .setReadOnly([instance])
-    .build();
-  const transaction = new StellarSdk.TransactionBuilder(account, {
-    fee,
-    networkPassphrase: StellarSdk.Networks.TESTNET, // Use appropriate network
-  })
-    .setSorobanData(sorobanData)
-    .addOperation(
-      StellarSdk.Operation.extendFootprintTtl({
-        extendTo: 500_000,
-      }),
-    )
-    .setTimeout(30)
-    .build();
-
-  // Sign and submit the transaction
-  transaction.sign(sourceKeypair);
-  const result = await server.sendTransaction(transaction);
-
-  console.log(
-    "Transaction submitted. Result:",
-    JSON.stringify(result, null, 2),
-  );
-  return result;
-}
-
-// Usage
-const contractId = "CC6MWZMG2JPQEENRL7XVICAY5RNMHJ2OORMUHXKRDID6MNGXSSOJZLLF";
-const sourceKeypair = StellarSdk.Keypair.fromSecret(
-  "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
-);
-
-extendContractWasmTTL(contractId, sourceKeypair)
-  .then(console.log)
-  .catch(console.error);
-```
-
-### Desglosando el código
-
-Vamos a repasar las partes clave de esta función:
-
-1. Configurando los datos de Soroban: El `SorobanDataBuilder()` es donde preparamos la información específica de Soroban para nuestra transacción.
-
-- Establecemos una tarifa de recursos con `setResourceFee(200_000)`. Esto cubre los costos adicionales de almacenamiento y ejecución.
-- Usamos `setReadOnly([instance])` para decirle a la red qué datos del contrato necesitamos acceder. Estamos usando `setReadOnly()` en lugar de `setReadWrite()` porque solo estamos extendiendo el TTL, no cambiando ningún dato.
-
-¿Por qué `setReadOnly()`? Algunas razones:
-
-- Es más rápido y utiliza menos recursos
-- Es más seguro: no podemos cambiar accidentalmente datos que no deberíamos
-- La operación `ExtendFootprintTTLOp` lo requiere
-
-2. Añadiendo la operación: Después de configurar los datos de Soroban, agregamos la operación `extendFootprintTtl` a nuestra transacción. We're telling it to extend the TTL to 500,000 ledgers with `extendTo: 500_000`.
-
-3. ¿Cuál es el punto? Todo este proceso trata de mantener los datos de nuestro contrato vivos en el ledger. Es como renovar un contrato de arrendamiento: le estamos diciendo a la red "¡Oye, mantén estas cosas alrededor por más tiempo, aún las estamos usando!"
-
-Esto es súper importante para los contratos que necesitan permanecer por un tiempo. Sin extender el TTL, los datos del contrato podrían caducar y desaparecer del ledger.
-
-</TabItem>
-</Tabs>
-
-Aprende cómo probar la extensión de TTL en esta [guía](../archival/test-ttl-extension.mdx).
-
-¿Quieres profundizar más? Consulta la documentación sobre la [operación Extender Tiempo de Vida de Huella (Extend Footprint TTL)](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#extendfootprintttlop).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/upgrading-contracts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/upgrading-contracts.mdx
deleted file mode 100644
index c4cc9fae73..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/upgrading-contracts.mdx
+++ /dev/null
@@ -1,304 +0,0 @@
----
-title: Actualizando el bytecode de Wasm para un contrato desplegado
-description: Actualizar el bytecode de Wasm para un contrato desplegado
----
-
-<head>
-  <title>Actualizando el Bytecode de Wasm para un Contrato Desplegado</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Actualizando el Bytecode de Wasm para un Contrato Desplegado"
-  />
-  <meta
-    property="og:description"
-    content="Actualizando el Bytecode de Wasm para un Contrato Desplegado"
-  />
-</head>
-
-## Introducción
-
-Actualizar un contrato inteligente te permite mejorar o modificar tu contrato sin cambiar su dirección. Esta guía te llevará a través del proceso de actualizar un contrato de bytecode de WebAssembly (Wasm) usando el Soroban SDK.
-
-### Requisitos previos:
-
-- Entendimiento básico del [lenguaje de programación Rust]. Para ponerte al día con Rust, revisa [Rustlings](https://github.com/rust-lang/rustlings) o [El libro de Rust](https://doc.rust-lang.org/book/).
-- Familiaridad con [contratos inteligentes de Stellar](../../smart-contracts/getting-started/hello-world.mdx)
-- Tener instalado [Stellar CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli) y Soroban SDK
-
-### Descargar el ejemplo de contrato actualizable
-
-El [ejemplo de contrato actualizable] demuestra cómo actualizar un contrato de Wasm.
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de contrato actualizable]: https://github.com/stellar/soroban-examples/tree/v23.0.0/upgradeable_contract
-[lenguaje de programación Rust]: https://www.rust-lang.org/
-
-### Código
-
-El ejemplo contiene tanto un contrato "viejo" como uno "nuevo", donde actualizamos de "viejo" a "nuevo". El código a continuación es para el contrato "viejo".
-
-```rust title="upgradeable_contract/old_contract/src/lib.rs"
-#![no_std]
-
-use soroban_sdk::{contract, contractimpl, contracttype, Address, BytesN, Env};
-
-#[contracttype]
-#[derive(Clone)]
-enum DataKey {
-    Admin,
-}
-
-#[contract]
-pub struct UpgradeableContract;
-
-#[contractimpl]
-impl UpgradeableContract {
-    pub fn __constructor(env: Env, admin: Address) {
-        env.storage().instance().set(&DataKey::Admin, &admin);
-    }
-
-    pub fn version() -> u32 {
-        1
-    }
-
-    pub fn upgrade(env: Env, new_wasm_hash: BytesN<32>) {
-        let admin: Address = e.storage().instance().get(&DataKey::Admin).unwrap();
-        admin.require_auth();
-
-        env.deployer().update_current_contract_wasm(new_wasm_hash);
-    }
-}
-
-mod test;
-```
-
-Fuente: https://github.com/stellar/soroban-examples/blob/v23.0.0/upgradeable_contract/old_contract/src/lib.rs
-
-## Cómo funciona
-
-Al actualizar un contrato, la función clave utilizada es `env.deployer().update_current_contract_wasm`, que toma el hash Wasm del nuevo contrato como parámetro. Aquí tienes un desglose paso a paso de cómo funciona este proceso:
-
-1. **No hay cambio en la dirección del contrato**: La dirección del contrato permanece igual después de la actualización. Esto asegura que todas las referencias al contrato permanezcan intactas.
-
-2. **El ejecutable Wasm debe estar ya cargado**: La actualización depende de que el ejecutable compilado (identificado por el `new_wasm_hash`) esté cargado y disponible en la blockchain. Esto debe hacerse _antes_ de invocar la función `upgrade(...)` del contrato.
-
-3. **Autorización del administrador**: Antes de actualizar, el contrato verifica si la acción está autorizada por la dirección `Admin`. Esto es crucial para prevenir actualizaciones no autorizadas. Solo alguien con derechos de administrador puede realizar la actualización.
-
-4. **La función de actualización**: A continuación se muestra la función que maneja el proceso de actualización:
-
-   ```rust
-   pub fn upgrade(env: Env, new_wasm_hash: BytesN<32>) {
-       let admin: Address = env.storage().instance().get(&DataKey::Admin).unwrap();
-       admin.require_auth();
-
-       env.deployer().update_current_contract_wasm(new_wasm_hash);
-   }
-   ```
-
-   - `env: Env`: El objeto de entorno que representa el estado actual de la blockchain.
-   - `new_wasm_hash: BytesN<32>`: El hash del nuevo código Wasm para el contrato. El bytecode de Wasm debe ya estar instalado/presente en el ledger.
-   - La función primero recupera la dirección del administrador del almacenamiento del contrato.
-   - Luego requiere la autorización del administrador (`admin.require_auth()`) para proceder.
-   - Finalmente, actualiza el contrato con el nuevo bytecode Wasm (`env.deployer().update_current_contract_wasm(new_wasm_hash)`).
-
-5. La función de host `update_current_contract_wasm` también emitirá un [evento] de contrato `SYSTEM` que contiene la referencia de wasm antigua y nueva, permitiendo a los usuarios posteriores ser notificados cuando un contrato que utilizan se actualiza. La estructura del evento tendrá `topics = ["executable_update", old_executable: ContractExecutable, old_executable: ContractExecutable]` y `data = []`.
-
-[evento]: ../../../learn/fundamentals/stellar-data-structures/events.mdx#event-types
-
-## Pruebas
-
-Abre el archivo `upgradeable_contract/old_contract/src/test.rs` para seguir.
-
-```rust title="upgradeable_contract/old_contract/src/test.rs"
-#![cfg(test)]
-
-extern crate std;
-
-use soroban_sdk::{
-    symbol_short,
-    testutils::{Address as _, AuthorizedFunction, AuthorizedInvocation},
-    Address, BytesN, Env, IntoVal,
-};
-
-use crate::{UpgradeableContract, UpgradeableContractClient};
-
-mod new_contract {
-    soroban_sdk::contractimport!(
-        file = "../new_contract/target/wasm32v1-none/release/soroban_upgradeable_contract_new_contract.wasm"
-    );
-}
-
-fn install_new_wasm(env: &Env) -> BytesN<32> {
-    env.deployer().upload_contract_wasm(new_contract::WASM)
-}
-
-#[test]
-fn test() {
-    let env = Env::default();
-    env.mock_all_auths();
-
-    let admin = Address::generate(&env);
-    let contract_id = env.register(UpgradeableContract, (&admin,));
-
-    let client = UpgradeableContractClient::new(&env, &contract_id);
-
-    assert_eq!(1, client.version());
-
-    let new_wasm_hash = install_new_wasm(&env);
-
-    client.upgrade(&new_wasm_hash);
-    assert_eq!(2, client.version());
-
-    // new_v2_fn was added in the new contract, so the existing
-    // client is out of date. Generate a new one.
-    let client = new_contract::Client::new(&env, &contract_id);
-    assert_eq!(1010101, client.new_v2_fn());
-
-    // New contract version requires the `NewAdmin` key to be initialized, but since the constructor
-    // hasn't been called, it is not initialized, thus calling try_upgrade won't work.
-    let new_update_result = client.try_upgrade(&new_wasm_hash);
-    assert!(new_update_result.is_err());
-
-    // `handle_upgrade` sets the `NewAdmin` key properly.
-    client.handle_upgrade();
-
-    // Now upgrade should succeed (though we are not actually changing the Wasm).
-    client.upgrade(&new_wasm_hash);
-    // The new admin is the same as the old admin, so the authorization is still performed for
-    // the `admin` address.
-    assert_eq!(
-        env.auths(),
-        std::vec![(
-            admin,
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    contract_id.clone(),
-                    symbol_short!("upgrade"),
-                    (new_wasm_hash,).into_val(&env),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    )
-}
-```
-
-Fuente: https://github.com/stellar/soroban-examples/blob/v23.0.0/upgradeable_contract/old_contract/src/test.rs
-
-Primero importamos el archivo Wasm compilado para el nuevo contrato:
-
-```rust
-mod new_contract {
-    soroban_sdk::contractimport!(
-        file = "../new_contract/target/wasm32v1-none/release/soroban_upgradeable_contract_new_contract.wasm"
-    );
-}
-```
-
-Registramos el contrato antiguo, lo inicializamos con un administrador y verificamos la versión que devuelve. La nota en el código a continuación es importante:
-
-```rust
-let admin = Address::generate(&env);
-let contract_id = env.register(UpgradeableContract, (&admin,));
-
-let client = UpgradeableContractClient::new(&env, &contract_id);
-
-assert_eq!(1, client.version());
-```
-
-Instalamos el Wasm del nuevo contrato:
-
-```rust
-let new_wasm_hash = install_new_wasm(&env);
-```
-
-Luego ejecutamos la actualización y verificamos que la actualización funcionó:
-
-```rust
-client.upgrade(&new_wasm_hash);
-assert_eq!(2, client.version());
-```
-
-## Crear el contrato
-
-Para crear los archivos `.wasm` del contrato, ejecuta `stellar contract build` en `upgradeable_contract/old_contract` y `upgradeable_contract/new_contract` en ese orden. Ambos archivos `.wasm` deberían encontrarse en ambos directorios `target` del contrato después de construir ambos contratos:
-
-```
-target/wasm32v1-none/release/soroban_upgradeable_contract_old_contract.wasm
-```
-
-```
-target/wasm32v1-none/release/soroban_upgradeable_contract_new_contract.wasm
-```
-
-## Ejecutar el contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar funciones del contrato. Despliega el contrato viejo e instala el Wasm para el nuevo contrato.
-
-Primero, navega al directorio `upgradeable_contract/old_contract` y despliega una instancia del contrato antiguo. Estamos proporcionando la identidad `alice` a la función `__constructor`, por lo que será la dirección `Admin` del contrato. Crea y proporciona tus propias [identidades], cuando sea necesario.
-
-Este comando mostrará la dirección del contrato en la que fue desplegado.
-
-```sh
-stellar contract deploy \
-  --wasm target/wasm32v1-none/release/soroban_upgradeable_contract_old_contract.wasm \
-  --source-account alice  \
-  --network testnet \
-  -- --admin alice
-# CAS6FKBXGVXFGU2SPPPJJOIULJNPMPR6NVKWLOQP24SZJPMB76TGH7Y3
-```
-
-Luego, navega a `upgradeable_contract/new_contract` y sube el archivo ejecutable compilado para el nuevo contrato. Este comando mostrará el hash Sha256 del ejecutable, que se usará más adelante para el parámetro `new_wasm_hash`.
-
-```sh
-stellar contract upload \
-  --source-account alice \
-  --wasm target/wasm32v1-none/release/soroban_upgradeable_contract_new_contract.wasm \
-  --network testnet
-# aa24c81289997ad815489b29db337b53f284cca5aba86e9a8ae5cef7d31842c2
-```
-
-Nuestra dirección de `old_contract` desplegada es `CAS6FKBXGVXFGU2SPPPJJOIULJNPMPR6NVKWLOQP24SZJPMB76TGH7Y3`. Es posible que necesites reemplazar este valor por el tuyo. Invoca la función `version` del contrato para ver la versión actual desplegada.
-
-```sh
-stellar contract invoke \
-  --id CAS6FKBXGVXFGU2SPPPJJOIULJNPMPR6NVKWLOQP24SZJPMB76TGH7Y3 \
-  --source-account alice \
-  --network testnet \
-  -- version
-# 1
-```
-
-Ahora actualiza el contrato. Nota que la opción `--source-account` debe ser el nombre de la identidad que igualarán la dirección pasada a la función `__constructor` cuando se desplegó el contrato.
-
-```sh
-stellar contract invoke \
-  --id CAS6FKBXGVXFGU2SPPPJJOIULJNPMPR6NVKWLOQP24SZJPMB76TGH7Y3 \
-  --source-account alice \
-  --network testnet \
-  -- \
-  upgrade \
-  --new_wasm_hash aa24c81289997ad815489b29db337b53f284cca5aba86e9a8ae5cef7d31842c2
-```
-
-Invoca la función `version` nuevamente. Ahora que el contrato fue actualizado, verás una nueva versión.
-
-```sh
-stellar contract invoke \
-  --id CAS6FKBXGVXFGU2SPPPJJOIULJNPMPR6NVKWLOQP24SZJPMB76TGH7Y3 \
-  --source-account alice \
-  --network testnet \
-  -- version
-# 2
-```
-
-¡Hurra, nuestro contrato ha sido actualizado!
-
-[`stellar-cli`]: ../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli
-[identidades]: ../../smart-contracts/getting-started/setup.mdx#configure-an-identity
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/wasm-metadata.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/wasm-metadata.mdx
deleted file mode 100644
index f147873fae..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/wasm-metadata.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Escribir metadatos para tu contrato
-hide_table_of_contents: true
-description: Usa el contractmeta! macro en Rust SDK para escribir metadatos en contratos Wasm
----
-
-<head>
-  <title>Escribir metadatos estructurados.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Escribir metadatos para tu contrato." />
-  <meta
-    property="og:description"
-    content="Usa un macro proporcionado en el Rust SDK para escribir metadatos estructurados y usa las herramientas disponibles para leer y mostrar esta información a los usuarios."
-  />
-</head>
-
-El macro [`contractmeta!`] proporcionado en el Rust SDK permite a los usuarios escribir dos cadenas - una `key` y una `val` - dentro de un objeto XDR serializado `SCMetaEntry::SCMetaV0` en la sección personalizada de los contratos Wasm. El nombre de la sección para estos metadatos es `contractmetav0`. Los desarrolladores pueden utilizar este macro para escribir metadatos, y las herramientas pueden luego leer y mostrar esta información a los usuarios.
-
-El [ejemplo de fondos de liquidez] proporciona una demostración clara de cómo usar el macro `contractmeta!`:
-
-```rust
-// Metadata that is added on to the Wasm custom section
-contractmeta!(
-    key = "Description",
-    val = "Constant product AMM with a .3% swap fee"
-);
-
-pub trait LiquidityPoolTrait {...
-```
-
-[`contractmeta!`]: https://docs.rs/soroban-sdk/22.0.4/soroban_sdk/macro.contractmeta.html
-[ejemplo de fondos de liquidez]: https://github.com/stellar/soroban-examples/blob/v22.0.1/liquidity_pool/src/lib.rs#L152-L155
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/work-contractspec-js.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/work-contractspec-js.mdx
deleted file mode 100644
index 988e82e19d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/work-contractspec-js.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Trabajar con ContractSpecs en JavaScript
-hide_table_of_contents: true
-draft: true
----
-
-Haces algo...
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/workspace.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/workspace.mdx
deleted file mode 100644
index d04015bf5f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conventions/workspace.mdx
+++ /dev/null
@@ -1,331 +0,0 @@
----
-title: Espacios de trabajo
-hide_table_of_contents: true
-description: Organizar contratos usando espacios de trabajo de Cargo
----
-
-# Espacio de trabajo
-
-Usar la [función](https://doc.rust-lang.org/book/ch14-03-cargo-workspaces.html) de espacios de trabajo de Cargo facilita mucho la organización de tus contratos inteligentes en subdirectorios de la raíz de tu proyecto.
-
-Es muy simple comenzar a usar la CLI:
-
-```
-stellar contract init soroban-project --name add_contract
-```
-
-Ejecutar este comando creará un directorio raíz del proyecto (`soroban-project`) y luego inicializará un espacio de trabajo del proyecto con un único contrato llamado `add_contract`.
-
-Agregar un contrato plantilla más al proyecto se puede hacer usando el mismo comando:
-
-```
-stellar contract init soroban-project --name main_contract
-```
-
-El árbol del proyecto en el directorio `soroban-project` se verá así:
-
-```
-.
-├── Cargo.toml
-├── contracts
-│   ├── add-contract
-│   │   ├── Cargo.toml
-│   │   ├── Makefile
-│   │   └── src
-│   │       ├── lib.rs
-│   │       └── test.rs
-│   └── main-contract
-│       ├── Cargo.toml
-│       ├── Makefile
-│       └── src
-│           ├── lib.rs
-│           └── test.rs
-└── README.md
-```
-
-Ejecutar el comando `stellar contract init` creó un nuevo contrato, ubicado en `./contracts`, cada uno conteniendo:
-
-- Archivo Cargo.toml con la dependencia `soroban-sdk`
-- Directorio `src` con un contrato de ejemplo hello-world y una prueba.
-
-Desarrolla los contratos con el siguiente comando (no olvides cambiar el directorio de trabajo a `soroban-project` antes de ejecutarlo) y verifica el directorio de compilación `target/wasm32v1-none/release/` para los archivos `.wasm` compilados.
-
-```
-stellar contract build
-```
-
-### Integrar contratos en el mismo espacio de trabajo
-
-Con la estructura de proyecto dada, se pueden realizar fácilmente llamadas cruzadas de contrato. Comenzar modificando el contrato de ejemplo hello world en un contrato add:
-
-```rust title="contracts/add_contract/src/lib.rs"
-#![no_std]
-use soroban_sdk::{contract, contractimpl};
-
-#[contract]
-pub struct ContractAdd;
-
-#[contractimpl]
-impl ContractAdd {
-    pub fn add(x: u32, y: u32) -> u32 {
-        x.checked_add(y).expect("no overflow")
-    }
-}
-```
-
-:::tip
-
-En este tutorial usamos espacios de trabajo para importar el cliente del contrato. Sin embargo, también es posible usar el código compilado del contrato en su lugar (por ejemplo, si no tienes un código fuente para él). Consulta la guía sobre [hacer llamadas entre contratos](./cross-contract.mdx) para más información
-
-:::
-
-A continuación, para llamar a `ContractAdd` desde otro contrato, es necesario agregar una dependencia de espacio de trabajo:
-
-```toml title="./contracts/main_contract/Cargo.toml"
-# <...>
-[dependencies]
-soroban-sdk = { workspace = true }
-add_contract = { path = "../add_contract" }
-# <...>
-```
-
-`ContractAdd` ahora puede ser referenciado y utilizado desde otros contratos usando `ContractAddClient`:
-
-```rust title="contracts/main_contract/src/lib.rs"
-#![no_std]
-use add_contract::ContractAddClient;
-use soroban_sdk::{contract, contractimpl, Address, Env};
-
-#[contract]
-pub struct ContractMain;
-
-#[contractimpl]
-impl ContractMain {
-    pub fn add_with(env: Env, contract: Address, x: u32, y: u32) -> u32 {
-        let client = ContractAddClient::new(&env, &contract);
-        client.add(&x, &y)
-    }
-}
-
-mod test;
-```
-
-Aquí, el contrato principal invocará la función `add` de `ContractAdd` para calcular la suma de 2 números. Es una buena idea actualizar las pruebas para nuestro contrato principal también:
-
-```rust title="contracts/main_contract/src/test.rs"
-#![cfg(test)]
-
-use crate::{ContractMain, ContractMainClient};
-use soroban_sdk::Env;
-use add_contract::ContractAdd;
-
-#[test]
-fn test_adding_cross_contract() {
-    let env = Env::default();
-
-    // Register add contract using the imported contract.
-    let contract_add_id = env.register(ContractAdd, ());
-
-    // Register main contract defined in this crate.
-    let contract_main_id = env.register(ContractMain, ());
-
-    // Create a client for calling main contract.
-    let client = ContractMainClient::new(&env, &contract_main_id);
-
-    // Invoke main contract via its client. Main contract will invoke add contract.
-    let sum = client.add_with(&contract_add_id, &5, &7);
-    assert_eq!(sum, 12);
-}
-```
-
-Los contratos ahora pueden volver a compilarse ejecutando el siguiente comando desde la raíz del proyecto:
-
-```
-stellar contract build
-```
-
-Y comprobar que la prueba esté funcionando correctamente, ejecutando pruebas en `contracts/main_contract`:
-
-```
-cargo test
-
-running 1 test
-test test::test_adding_cross_contract ... ok
-
-test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s
-```
-
-Finalmente, despleguemos estos contratos y llamemos a nuestro contrato principal usando CLI. Si aún no lo has hecho, configura una cuenta (alice) primero
-
-```bash
-stellar keys generate alice --fund --network testnet
-stellar keys use alice
-```
-
-El segundo paso es desplegar los contratos:
-
-```bash
-stellar contract deploy --network testnet --wasm target/wasm32v1-none/release/add_contract.wasm --alias add_contract
-stellar contract deploy --network testnet --wasm target/wasm32v1-none/release/main_contract.wasm --alias main_contract
-```
-
-Y finalmente llama al contrato principal:
-
-```
-$ stellar contract invoke --id main_contract --network testnet -- add_with --contract add_contract --x 9 --y 10
-ℹ️ Send skipped because simulation identified as read-only. Send by rerunning with `--send=yes`.
-19
-```
-
-### Agregando interfaces de contrato
-
-Como siguiente paso, podemos abstraer el contrato add y permitir que tenga múltiples implementaciones. El contrato principal utilizará a su vez la interfaz del contrato que no está vinculada a su implementación.
-
-```
-stellar contract init . --name adder_interface
-stellar contract init . --name add_extra_contract
-```
-
-Primero, creemos una interfaz y cambiemos nuestra implementación existente para usar esta interfaz:
-
-```rust title="contracts/adder_interface/src/lib.rs"
-#![no_std]
-
-use soroban_sdk::contractclient;
-
-#[contractclient(name = "ContractAClient")]
-pub trait ContractAInterface {
-    fn add(x: u32, y: u32) -> u32;
-}
-```
-
-Para utilizar la definición de interfaz, nuestros miembros del espacio de trabajo ahora tendrán un `adder_interface` como dependencia:
-
-```toml title="./Cargo.toml"
-# <...>
-[workspace.dependencies]
-soroban-sdk = "21.0.0"
-adder-interface = { path = "contracts/adder_interface" }
-# <...>
-```
-
-```toml title="./contracts/add_contract/Cargo.toml"
-# <...>
-[dependencies]
-soroban-sdk = { workspace = true }
-adder-interface = {workspace = true}
-# <...>
-```
-
-```toml title="./contracts/main_contract/Cargo.toml"
-# <...>
-[dependencies]
-soroban-sdk = { workspace = true }
-adder-interface = {workspace = true}
-add_contract = { path = "../add_contract" }
-# <...>
-```
-
-```toml title="./contracts/add_extra_contract/Cargo.toml"
-# <...>
-[dependencies]
-soroban-sdk = { workspace = true }
-adder-interface = {workspace = true}
-# <...>
-```
-
-Y cambiamos el tipo de lib del crate `adder_interface`:
-
-```toml title="./contracts/adder_interface/Cargo.toml"
-# <...>
-[lib]
-crate-type = ["rlib"]
-# <...>
-```
-
-```rust title="./contracts/adder_interface/src/lib.rs"
-#![no_std]
-
-use soroban_sdk::contractclient;
-
-#[contractclient(name = "AdderClient")]
-pub trait Adder {
-    fn add(x: u32, y: u32) -> u32;
-}
-
-```
-
-```rust title="contracts/add_contract/src/lib.rs"
-#![no_std]
-use soroban_sdk::{contract, contractimpl};
-use adder_interface::Adder;
-
-#[contract]
-pub struct ContractAdd;
-
-#[contractimpl]
-impl Adder for ContractAdd {
-    fn add(x: u32, y: u32) -> u32 {
-        x.checked_add(y).expect("no overflow")
-    }
-}
-
-```
-
-```rust title="contracts/main_contract/src/lib.rs"
-#![no_std]
-
-use soroban_sdk::{contract, contractimpl, Address, Env};
-use adder_interface::AdderClient;
-
-#[contract]
-pub struct ContractMain;
-
-#[contractimpl]
-impl ContractMain {
-    pub fn add_with(env: Env, contract: Address, x: u32, y: u32) -> u32 {
-        let client = AdderClient::new(&env, &contract);
-        client.add(&x, &y)
-    }
-}
-
-mod test;
-```
-
-Como paso final, podemos crear una implementación alternativa de `Adder` que sume un extra 1:
-
-```rust title="contracts/add_extra_contract/src/lib.rs"
-#![no_std]
-use soroban_sdk::{contract, contractimpl};
-use adder_interface::Adder;
-
-#[contract]
-pub struct ContractAdd;
-
-#[contractimpl]
-impl Adder for ContractAdd {
-    fn add(x: u32, y: u32) -> u32 {
-        x.checked_add(y).expect("no overflow").checked_add(1).expect("no overflow")
-    }
-}
-```
-
-Ahora podemos desplegar estos contratos y probar el nuevo comportamiento:
-
-```bash
-stellar contract build
-stellar contract deploy --network testnet --wasm target/wasm32v1-none/release/add_contract.wasm --alias add_contract
-stellar contract deploy --network testnet --wasm target/wasm32v1-none/release/add_extra_contract.wasm --alias wrong_math_contract
-stellar contract deploy --network testnet --wasm target/wasm32v1-none/release/main_contract.wasm --alias main_contract
-```
-
-Ahora intentemos sumar 2 enteros sin signo provocando un desbordamiento:
-
-```
-$ stellar contract invoke --id main_contract --network testnet -- add_with --contract add_contract --x 2 --y 2
-ℹ️ Send skipped because simulation identified as read-only. Send by rerunning with `--send=yes`.
-4
-$ stellar contract invoke --id main_contract --network testnet -- add_with --contract wrong_math_contract --x 2 --y 2
-ℹ️ Send skipped because simulation identified as read-only. Send by rerunning with `--send=yes`.
-5
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/README.mdx
deleted file mode 100644
index 58fd13520f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Conversiones de tipos
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 130
----
-
-Una colección de guías para convertir de un tipo de dato a otro en una variedad de lenguajes SDK.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-conversions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-conversions.mdx
deleted file mode 100644
index a058b9beba..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-conversions.mdx
+++ /dev/null
@@ -1,125 +0,0 @@
----
-title: Convertir una dirección a otros tipos
-hide_table_of_contents: true
-description: Convertir una dirección a otros tipos
----
-
-La `Address` es un tipo opaco que representa ya sea una cuenta externa "default" en la red Stellar, o un contrato (que también puede proporcionar lógica para cuentas externas personalizadas, consulta la [documentación de autorización](../../../learn/fundamentals/contract-development/authorization.mdx#account-abstraction) para más detalles). Para los contratos inteligentes normalmente no importa qué tipo de `Address` se utilice. Sin embargo, en algunos contextos es útil convertir `Address` a/de diferentes tipos de datos, como cadena o XDR. Las conversiones tienen propósitos claramente diferentes dependiendo de si ocurren en el propio contrato inteligente o en el código cliente.
-
-## Conversiones de cadena
-
-El formato de cadena por defecto para `Address` es el llamado 'string key' (o 'strkey'), definido completamente en [SEP-23](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md). Para las cuentas externas por defecto, strkey siempre empieza con `G` y para todos los contratos empieza con `C`.
-
-### Conversiones de cadenas en los SDKs de cliente
-
-Fuera de los contratos inteligentes, es conveniente representar `Address` como cadena la mayor parte del tiempo. Puede almacenarse en formatos de serialización de cadena como JSON y XML. Almacenar direcciones como cadenas en bases de datos puede simplificar el diseño de esquemas de bases de datos y consultas. Las cadenas son más fáciles de manipular y son más compatibles con interfaces de usuario y APIs. Por lo tanto
-
-<CodeExample>
-
-```js
-const StellarSdk = require("@stellar/stellar-sdk");
-
-// Example Stellar address
-const stellarAddress =
-  "GCM5WPR4DDR24FSAX5LIEM4J7AI3KOWJYANSXEPKYXCSZOTAYXE75AFN";
-// Create an Address object from string
-const address = new StellarSdk.Address(stellarAddress);
-// Convert the address back to string
-const addressToString = address.toString();
-```
-
-```python
-from stellar_sdk import Address
-
-# Example Stellar address
-stellar_address = "GCM5WPR4DDR24FSAX5LIEM4J7AI3KOWJYANSXEPKYXCSZOTAYXE75AFN"
-# Create an Address object from string
-address = Address(stellar_address)
-# Convert the address back to string
-address_to_string = address.address
-```
-
-</CodeExample>
-
-### Conversiones de cadenas en contratos inteligentes
-
-Por lo general, se prefiere que los contratos operen directamente sobre el tipo `Address`. Las conversiones de cadenas pueden ser útiles para casos de uso especializados, como pasar los `Address` de Stellar hacia y desde otras cadenas.
-
-```rust
-use soroban_sdk::{Address, String, Env};
-
-pub fn address_to_string(address: Address) -> String {
-    address.to_string()
-}
-
-pub fn address_from_string(strkey: String) -> Address {
-    Address::from_string(&strkey)
-}
-```
-
-`Address` también puede crearse a partir de un literal de cadena, lo que puede ser útil para pruebas.
-
-```rust
-let test_address = Address::from_str(
-    &env,
-    "GCM5WPR4DDR24FSAX5LIEM4J7AI3KOWJYANSXEPKYXCSZOTAYXE75AFN",
-);
-```
-
-## Conversiones XDR
-
-XDR es un formato de serialización binaria basado en esquema utilizado por la red Stellar. Se utiliza para todas las interacciones con la blockchain Stellar, como crear las transacciones, almacenar datos en el ledger, comunicar los resultados de las transacciones, etc. Los SDK Stellar proporcionan envoltorios tipados para todos los tipos de datos XDR de Stellar. Address se representa como tipo `ScAddress`, que puede envolverse dentro de `ScVal`, un tipo que representa cualquier tipo de contrato admitido por los contratos Stellar.
-
-### Conversiones XDR en los SDKs de cliente
-
-En el lado cliente, las conversiones XDR son útiles para crear las transacciones y procesar los resultados de las transacciones.
-
-<CodeExample>
-
-```js
-// Example Stellar address
-const stellarAddress =
-  "GCM5WPR4DDR24FSAX5LIEM4J7AI3KOWJYANSXEPKYXCSZOTAYXE75AFN";
-// Create an Address object from string
-const address = new StellarSdk.Address(stellarAddress);
-// Convert the Address to xdr.ScVal
-const scVal = address.toScVal();
-// Convert scVal structure to the binary format
-const scValBuffer = scVal.toXDR("raw");
-// Convert the Address to xdr.ScAddress
-const scAddress = address.toScAddress();
-```
-
-```python
-from stellar_sdk import Address
-
-# Example Stellar address
-stellar_address = 'GBJCHUKZMTFSLOMNC7P4TS4VJJBTCYL3XKSOLXAUJSD56C4LHND5TWUC'
-# Create an Address object
-address = Address(stellar_address)
-# Convert the Address object to an ScAddress
-sc_address_xdr = address.to_xdr_sc_address()
-```
-
-</CodeExample>
-
-### Conversiones XDR en contratos inteligentes
-
-Los contratos inteligentes no necesitan interactuar explícitamente con los tipos XDR, ya que todos los tipos de datos de contratos inteligentes se convierten automáticamente a XDR por el entorno de ejecución del contrato. Cada tipo de contrato, incluyendo `Address`, puede serializarse a bytes XDR. Esta conversión es útil, por ejemplo, para realizar hashing en los contratos inteligentes. También es posible convertir los bytes XDR serializados de nuevo a tipos de contrato, lo que puede ser útil en casos de uso específicos, como esquemas de autenticación personalizados.
-
-Nota, que las conversiones XDR son una función avanzada y no son necesarias para la mayoría de los contratos inteligentes de Stellar.
-
-```rust
-use soroban_sdk::{
-    xdr::{FromXdr, ToXdr},
-    Address, Bytes, Env,
-};
-
-pub fn address_to_xdr_bytes(env: Env, address: Address) -> Bytes {
-    address.to_xdr(&env)
-}
-
-pub fn address_from_xdr_bytes(env: Env, bytes: Bytes) -> Address {
-    Address::from_xdr(&env, &bytes).unwrap()
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-to-bytesn.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-to-bytesn.mdx
deleted file mode 100644
index ee415421dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-to-bytesn.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Convertir una dirección a BytesN usando el SDK de Rust
-hide_table_of_contents: true
-description: Convertir una dirección a BytesN usando el SDK de Rust
-draft: true
----
-
-El `Address` es un tipo opaco que podría representar una "cuenta" en la red Stellar (es decir, un keypair), o un "contrato." Desde el punto de vista de Soroban, realmente no importa cuál sea. La variedad "cuenta" de estas direcciones se muestra típicamente como una dirección pública `G...`, y la variedad "contrato" se muestra típicamente como una dirección `C...`. Otra forma que se puede usar para mostrar una dirección es un array de 32 bytes. El SDK de Rust puede manejar la conversión entre los dos fácilmente:
-
-```rust
-
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-to-id.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-to-id.mdx
deleted file mode 100644
index c724b35092..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/address-to-id.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Convertir una dirección de contrato en un ID de contrato en Rust
-hide_table_of_contents: true
-draft: true
----
-
-`C...` se convierte en un ID `deadb33f` codificado en hexadecimal.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/bytes-conversions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/bytes-conversions.mdx
deleted file mode 100644
index 520f1d7d26..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/bytes-conversions.mdx
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: Convertir de bytes a otros tipos
-hide_table_of_contents: true
-description: Convertir de bytes a otros tipos
----
-
-Bytes es un tipo de arreglo contiguo que crece y contiene u8s. Pueden representar varios tipos de datos, incluyendo cadenas, direcciones u otra información. Convertir cualquier tipo de dato a bytes garantiza que los datos sean manejados de manera consistente por el entorno de ejecución de Soroban y los sistemas interactuantes.
-
-## Bytes a Dirección
-
-Al recuperar datos almacenados en la blockchain, las direcciones pueden estar almacenadas en representación de bytes por razones de compactación y eficiencia. Los sistemas fuera de la cadena, como APIs, bases de datos o interfaces de usuario, generalmente esperan direcciones en un formato legible por humanos. En tales casos, necesitas convertir los bytes a un formato de dirección para asegurar la compatibilidad.
-
-<CodeExample>
-
-```rust
-use soroban_sdk::{Address, Bytes};
-
-pub fn bytes_to_address(bytes: Bytes) -> Address {
-    Address::from_string_bytes(&bytes)
-}
-```
-
-```js
-const StellarSdk = require("@stellar/stellar-sdk");
-
-// Example bytes value
-const rawBytes = Buffer.from(
-  "99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe",
-  "hex",
-);
-// Convert bytes to an account Address
-const addressFromBytes = StellarSdk.Address.account(rawBytes);
-addressFromBytes.toString();
-// Convert from bytes to a string address
-const addressFromBytes = StellarSdk.Address.contract(rawBytes);
-addressFromBytes.toString();
-```
-
-```python
-from stellar_sdk.address import Address
-
-# Example bytes value
-raw_bytes = bytes.fromhex("99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe")
-bytes_to_address = Address.from_raw_account(raw_bytes)
-```
-
-</CodeExample>
-
-## Bytes a Cadena
-
-Al trabajar con datos binarios, puedes necesitar convertir ciertas porciones de los datos a un formato legible por humanos, como cadenas, para registro, depuración, procesamiento o visualización.
-
-<CodeExample>
-
-```rust
-use soroban_sdk::{String, Bytes};
-
-pub fn bytes_to_string(bytes: Bytes) -> String {
-    String::from(bytes)
-}
-```
-
-```js
-// Example bytes value
-const rawBytes = Buffer.from(
-  "99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe",
-  "hex",
-);
-// Convert bytes to string
-const bytesToString = rawBytes.toString("hex");
-```
-
-```python
-# Example bytes value
-raw_bytes = bytes.fromhex("99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe")
-# Convert bytes to string
-bytes_to_string = raw_bytes.hex()
-```
-
-</CodeExample>
-
-## Bytes a ScVal
-
-En un contrato inteligente de Soroban que interactúa con un servicio de oráculo externo para proporcionar datos de precios en formato de byte crudo, necesitarías convertir los bytes a ScVal para procesar y manipular los datos dentro de tu contrato.
-
-<CodeExample>
-
-```rust
-use soroban_sdk::{Bytes, Val};
-
-pub fn bytes_to_val(bytes: Bytes) -> Val {
-    Val::from(bytes)
-}
-```
-
-```js
-// Example bytes value
-const rawBytes = Buffer.from(
-  "99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe",
-  "hex",
-);
-// Convert bytes to xdr.ScVal
-const bytesToScVal = StellarSdk.nativeToScVal(rawBytes);
-```
-
-```python
-# Example bytes value
-raw_bytes = bytes.fromhex("99db3e3c18e3ae1640bf56823389f811b53ac9c01b2b91eac5c52cba60c5c9fe")
-# Convert bytes to ScVal
-sc_val = stellar_sdk.scval.to_bytes(raw_bytes)
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/id-to-address.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/id-to-address.mdx
deleted file mode 100644
index 65af97dd8b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/id-to-address.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Convertir un ID de contrato a una dirección de contrato
-hide_table_of_contents: true
-description: Convertir un ID de contrato a una dirección de contrato
-draft: true
----
-
-El ID codificado en hex-`deadb33f` se convierte en un `C...` StrKey.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/scval-conversions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/scval-conversions.mdx
deleted file mode 100644
index 8e4a8d8970..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/scval-conversions.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Convertir un ScVal a otro tipo
-hide_table_of_contents: true
-description: Convertir un ScVal a otro tipo
----
-
-El valor del contrato Soroban (`ScVal`) es un tipo personalizado definido dentro del entorno de ejecución Soroban que representa otros tipos de datos como cadenas, bytes y estructuras más complejas utilizadas dentro de contratos inteligentes en un formato que el entorno de ejecución Soroban puede procesar, almacenar y recuperar de manera eficiente.
-
-## ScVal a bytes
-
-<CodeExample>
-
-```js
-// An ScVal bytes value
-const myScVal = StellarSdk.xdr.ScVal.fromXDR("AAAADQAAAARQ/8AB", "base64");
-// Convert the ScVal to a Buffer
-const bytesFromScVal = StellarSdk.scValToNative(myScVal);
-```
-
-```python
-# Convert the ScVal to bytes
-bytes_from_sc_val = stellar_sdk.scval.from_bytes("AAAADQAAAARQ/8AB")
-```
-
-</CodeExample>
-
-## ScVal a dirección
-
-<CodeExample>
-
-```js
-// An ScVal Address value
-const myScVal = StellarSdk.xdr.ScVal.fromXDR(
-  "AAAAEgAAAAAAAAAAmds+PBjjrhZAv1aCM4n4EbU6ycAbK5HqxcUsumDFyf4=",
-  "base64",
-);
-// Convert the ScVal to an Address
-const addressFromScVal = StellarSdk.Address.fromScVal(myScVal);
-```
-
-```python
-# Convert the ScVal to address
-address_from_sc_val = stellar_sdk.scval.from_address("AAAAEgAAAAAAAAAAmds+PBjjrhZAv1aCM4n4EbU6ycAbK5HqxcUsumDFyf4=")
-```
-
-</CodeExample>
-
-## ScVal a cadena
-
-<CodeExample>
-
-```js
-// An ScVal string value
-const myScVal = StellarSdk.xdr.ScVal.fromXDR(
-  "AAAADgAAAA9IZWxsbywgU3RlbGxhciEA",
-  "base64",
-);
-// Convert the ScVal to a string
-const stringFromScVal = StellarSdk.scValToNative(myScVal);
-```
-
-```python
-# Convert the ScVal to a string
-string_from_sc_val = stellar_sdk.scval.from_string("AAAADgAAAA9IZWxsbywgU3RlbGxhciEA").decode()
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/string-conversions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/string-conversions.mdx
deleted file mode 100644
index 975ac8de29..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/conversions/string-conversions.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Convertir una cadena a otros tipos
-hide_table_of_contents: true
-description: Convertir una cadena a otros tipos
----
-
-Las cadenas son una secuencia de caracteres utilizados para representar texto legible. Se utilizan para almacenar y manipular información basada en texto, como nombres de funciones, argumentos, datos clave-valor e interfaces con sistemas externos. Las cadenas a menudo pueden necesitar ser convertidas a otros tipos de datos para un procesamiento y almacenamiento eficientes.
-
-## Cadena a bytesN
-
-Algunos sistemas utilizan formatos binarios donde los datos necesitan ser representados como un arreglo de bytes de longitud fija para almacenamiento o procesamiento. Por ejemplo, hashes o identificadores de longitud fija. Convertir cadenas a un tamaño de bytes fijo asegura que los datos se ajusten a las restricciones de tamaño requeridas.
-
-<CodeExample>
-
-```rust
-use soroban_sdk::{Bytes, String};
-
-pub fn string_to_bytes(string: String) -> Bytes {
-    Bytes::from(string)
-}
-```
-
-```js
-// Example string
-const stringValue = "Hello, Stellar!";
-// Convert the string to bytes format
-const byteValue = Buffer.from(stringValue, "utf-8");
-```
-
-```python
-# Example string
-string_value = "Hello, Stellar!"
-# Convert the string to bytes format
-string_value.encode()
-```
-
-</CodeExample>
-
-## Cadena a dirección
-
-Una dirección recibida en una entrada de usuario puede ser de tipo cadena y necesitarías convertirla a un tipo dirección para realizar validaciones, transacciones u otras operaciones dentro de tu contrato inteligente.
-
-<CodeExample>
-
-```rust
-use soroban_sdk::{Address, Env, String};
-
-pub fn string_to_address(string: String) -> Address {
-    Address::from_string(&string)
-}
-```
-
-```js
-const StellarSdk = require("@stellar/stellar-sdk");
-
-// Example Stellar address
-const stellarAddress =
-  "GCM5WPR4DDR24FSAX5LIEM4J7AI3KOWJYANSXEPKYXCSZOTAYXE75AFN";
-// Create an Address object from string
-const address = new StellarSdk.Address(stellarAddress);
-// Convert the address back to string
-const addressToString = address.toString();
-```
-
-```python
-from stellar_sdk import Address
-
-# Example Stellar address
-stellar_address = "GCM5WPR4DDR24FSAX5LIEM4J7AI3KOWJYANSXEPKYXCSZOTAYXE75AFN"
-# Create an Address object from string
-address = Address(stellar_address)
-# Convert the address back to string
-address_to_string = address.address
-```
-
-</CodeExample>
-
-## Cadena a ScVal
-
-Al llamar a funciones o métodos que esperan tipos ScVal, necesitas convertir tus datos de cadena a ScVal para que la llamada sea exitosa. Por ejemplo, si tu contrato inteligente necesita almacenar o manipular una cadena de entrada de usuario dentro de su estado o utilizarla como parte de su lógica, deberías convertir la cadena a un tipo ScVal para integrarla con las operaciones del contrato.
-
-<CodeExample>
-
-```rust
-use soroban_sdk::{String, Val};
-
-pub fn string_to_val(string: String) -> Val {
-    Val::from(string)
-}
-```
-
-```js
-import StellarSdk from "@stellar/stellar-sdk";
-
-// Example string value
-const stringValue = "Hello, Stellar!";
-// Convert the string to ScVal
-const stringToScVal = StellarSdk.xdr.ScVal.scvString(stringValue);
-```
-
-```python
-import stellar_sdk
-
-# Example string value
-string_value = "Hello, Stellar!"
-# Convert the string to ScVal
-string_to_sc_val = stellar_sdk.scval.to_string(string_value)
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/README.mdx
deleted file mode 100644
index 21fc8f62fa..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Desarrollo de Dapps
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 50
----
-
-Hemos escrito algunas guías útiles sobre algunas de las herramientas más útiles disponibles para ti, el desarrollador de dapps.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/docker.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/docker.mdx
deleted file mode 100644
index 04fd14c65d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/docker.mdx
+++ /dev/null
@@ -1,138 +0,0 @@
----
-title: Usar Docker para crear y ejecutar dapps
-description: Entender Docker y usarlo para crear aplicaciones
-draft: true
----
-
-## ¿Qué es Docker?
-
-Bienvenido al mundo de [Docker](https://www.docker.com/), una herramienta esencial para el desarrollo de software. Docker empaqueta software en unidades conocidas como contenedores, asegurando consistencia, aislamiento, portabilidad y escalabilidad.
-
-Docker es particularmente útil en el desarrollo de dapps. Ayuda a gestionar microservicios, mantener entornos consistentes a lo largo de las etapas de desarrollo y simular una red descentralizada durante las pruebas.
-
-Entender Docker comienza con entender las imágenes y contenedores de Docker. Una imagen de Docker, creada a partir de un Dockerfile, es un paquete que contiene todo lo necesario para ejecutar el software. Un contenedor de Docker es una instancia en ejecución de esta imagen.
-
-## Construir y Ejecutar una Imagen de Docker
-
-Puedes crear una imagen de Docker usando el comando docker build con un Dockerfile. Una vez que la imagen está creada, puedes ejecutar un contenedor de Docker usando el comando docker run.
-
-En el contexto de los dapps de ejemplo Soroban, entender cómo construir imágenes de Docker es crucial. Las imágenes de Docker sirven como la base para nuestro contenedor, que proporciona el entorno para que nuestro dapp se ejecute.
-
-Aquí tienes un ejemplo de nuestro ejemplo
-
-Para ilustrar el proceso, tomemos un ejemplo de nuestra [ejemplo de dapp de crowdfunding]. Para construir la imagen de Docker, utilizas un comando que está encapsulado dentro de nuestro Makefile:
-
-```bash
-make build-docker
-```
-
-Este comando simplifica el proceso de construcción de Docker y asegura que se ejecute de manera consistente cada vez. Cuando ejecutas `make build-docker`, Docker ejecuta las siguientes instrucciones:
-
-```bash
-docker build . \
- --tag soroban-preview:11 \
- --force-rm \
- --rm
-```
-
-### Descripción General del Makefile
-
-```bash
-docker build .
-```
-
-Instruye a Docker para construir una imagen usando el Dockerfile en el directorio actual (indicado por el ".").
-
-```bash
---tag soroban-preview:11
-```
-
-Asigna un nombre y una etiqueta a nuestra imagen, en este caso, soroban-preview con la etiqueta 9.
-
-```bash
---force-rm
-```
-
-Asegura que Docker elimine cualquier contenedor intermedio después de que finalice el proceso de construcción. Esto mantiene nuestro entorno limpio.
-
-```bash
---rm
-```
-
-Garantiza la eliminación del contenedor intermedio, incluso si la construcción falla. Al usar `make build-docker`, estás aprovechando el poder de Docker para crear un entorno consistente y confiable para nuestro dapp.
-
-## Despliegue de Contenedores
-
-Puedes agilizar el proceso de despliegue utilizando un script para ejecutar el contenedor de Docker. El siguiente script es un envoltorio para la [`stellar/quickstart` imagen de Docker], que proporciona una forma rápida de ejecutar una red Stellar. Puedes encontrar un ejemplo del script `quickstart.sh` ubicado en el directorio raíz de la [ejemplo de dapp de crowdfunding].
-
-```bash title="quickstart.sh"
-#!/bin/bash
-
-set -e
-
-case "$1" in
-standalone)
-    echo "Using standalone network"
-    ARGS="--standalone"
-    ;;
-futurenet)
-    echo "Using Futurenet network"
-    ARGS="--futurenet"
-    ;;
-*)
-    echo "Usage: $0 standalone|futurenet"
-    exit 1
-    ;;
-esac
-
-shift
-
-# Run the soroban-preview container
-# Remember to do:
-# make build-docker
-
-echo "Creating docker soroban network"
-(docker network inspect soroban-network -f '{{.Id}}' 2>/dev/null) \
-  || docker network create soroban-network
-
-echo "Searching for a previous soroban-preview docker container"
-containerID=$(docker ps --filter="name=soroban-preview" --all --quiet)
-if [[ ${containerID} ]]; then
-    echo "Start removing soroban-preview container."
-    docker rm --force soroban-preview
-    echo "Finished removing soroban-preview container."
-else
-    echo "No previous soroban-preview container was found"
-fi
-
-currentDir=$(pwd)
-docker run -dti \
-  --volume ${currentDir}:/workspace \
-  --name soroban-preview \
-  -p 8001:8000 \
-  --ipc=host \
-  --network soroban-network \
-  soroban-preview:11
-
-# Run the stellar quickstart image
-
-docker run --rm -ti \
-  --name stellar \
-  --network soroban-network \
-  -p 8000:8000 \
-  stellar/quickstart:testing \
-  $ARGS \
-  --enable-soroban-rpc \
-  "$@" # Pass through args from the CLI
-```
-
-El script `quickstart.sh` configura el entorno de Docker para ejecutar el dapp. Te permite elegir entre una red independiente o la red Futurenet. El script realiza los siguientes pasos:
-
-- Determina la red en función del argumento proporcionado (`standalone` o `futurenet`).
-- Crea la red de Docker llamada `soroban-network` si no existe.
-- Elimina cualquier contenedor de Docker `soroban-preview` existente.
-- Ejecuta el contenedor `soroban-preview`, que proporciona el entorno para el desarrollo de Soroban Preview.
-- Ejecuta la imagen de Docker `stellar/quickstart`, que configura la red Stellar utilizando el tipo de red elegido y habilita Stellar RPC.
-
-[`stellar/quickstart` imagen de docker]: https://hub.docker.com/r/stellar/quickstart
-[ejemplo de dapp de crowdfunding]: https://github.com/stellar/soroban-example-dapp
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/frontend-guide.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/frontend-guide.mdx
deleted file mode 100644
index 85bb7106ad..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/frontend-guide.mdx
+++ /dev/null
@@ -1,844 +0,0 @@
----
-title: Guía completa de frontend para dapps Stellar
-description: Aprende a crear interfaces de frontend funcionales para dapps Stellar usando React, Tailwind CSS y el Stellar SDK.
----
-
-## Requisitos previos:
-
-- Conocimiento básico de React, Tailwind CSS y tecnologías web relacionadas
-- Comprensión básica de la blockchain Stellar
-- Node.js y npm instalados
-- Navegador web con la extensión [Freighter Wallet](https://www.freighter.app) instalada
-
-## 1. Introducción
-
-### El papel del frontend en las dapps Stellar
-
-El desarrollo de frontend juega un papel crucial en las aplicaciones descentralizadas (dapps) creadas en la red Stellar. Sirve como la interfaz principal entre los usuarios y la tecnología blockchain subyacente. Un frontend bien diseñado no solo hace que tu dapp sea accesible y fácil de usar, sino que también ayuda a los usuarios a interactuar sin problemas con operaciones complejas de blockchain.
-
-En las dapps Stellar, el frontend es responsable de:
-
-1. Presentar datos de blockchain en un formato legible por humanos
-2. Facilitar interacciones de usuario con contratos inteligentes y operaciones de Stellar
-3. Gestionar cuentas y claves de usuario de forma segura
-4. Proporcionar actualizaciones en tiempo real sobre el estado de las transacciones y los saldos de las cuentas
-5. Guiar a los usuarios a través de procesos complejos como transacciones de múltiples firmas u operaciones de saldos reclamables
-
-### Importancia de la interfaz de usuario y la experiencia del usuario
-
-La importancia de una buena interfaz de usuario (UI) y experiencia de usuario (UX) en dapps Stellar no puede ser exagerada. La tecnología blockchain puede ser intimidante para muchos usuarios, y un diseño de UI/UX bien hecho puede marcar la diferencia entre una dapp exitosa y una que los usuarios consideran frustrante o confusa.
-
-Aspectos clave de UI/UX en dapps Stellar incluyen:
-
-1. Simplicidad: Presentar conceptos complejos de blockchain de manera fácil de entender
-2. Transparencia: Proporcionar información clara sobre tarifas de transacción, estado de la red y resultados de operaciones
-3. Retroalimentación: Ofrecer retroalimentación inmediata y clara sobre las acciones del usuario y el progreso de la transacción
-4. Manejo de Errores: Gestionar y explicar errores de manera amistosa para el usuario
-5. Rendimiento: Asegurar tiempos de carga rápidos e interacciones receptivas, incluso cuando se trata de operaciones de blockchain
-
-Al enfocarte en estos aspectos, puedes crear dapps Stellar que no solo sean funcionales, sino también agradables de usar, fomentando una adopción más amplia de tu aplicación y de la red Stellar en su conjunto.
-
-## 2. Configurando el entorno de desarrollo
-
-Antes de comenzar a crear nuestra dapp Stellar, necesitamos configurar nuestro entorno de desarrollo. Usaremos React con Next.js como nuestro marco de frontend, Tailwind CSS para el estilo y el Stellar SDK para interactuar con la red Stellar.
-
-### Instalando Node.js y npm
-
-Primero, asegúrate de tener Node.js y npm (Node Package Manager) instalados en tu sistema. Puedes descargarlos e instalarlos desde el sitio web oficial de Node.js: https://nodejs.org/
-
-Para verificar tu instalación, abre una terminal y ejecuta:
-
-```bash
-node --version
-npm --version
-```
-
-Ambos comandos deberían devolver números de versión si la instalación fue exitosa.
-
-### Configurando un proyecto de Next.js
-
-Next.js es un marco de React que proporciona características como el renderizado del lado del servidor y enrutamiento desde el principio. Para crear un nuevo proyecto de Next.js, ejecuta los siguientes comandos en tu terminal:
-
-```bash
-npx create-next-app@latest stellar-dapp
-cd stellar-dapp
-```
-
-Cuando se te pregunte, elige las siguientes opciones:
-
-- ¿Te gustaría usar TypeScript? Sí
-- ¿Te gustaría usar ESLint? Sí
-- ¿Te gustaría usar Tailwind CSS? Sí
-- ¿Te gustaría usar el directorio `src/`? No
-- ¿Te gustaría usar App Router? Sí
-- ¿Te gustaría personalizar el alias de importación predeterminado? No
-
-### Configurar HTTPS en Localhost
-
-La billetera Freighter requiere una conexión segura (HTTPS) para interactuar con tu dapp. Para habilitar HTTPS en localhost, puedes usar una herramienta como `mkcert`. Afortunadamente, Next.js proporciona soporte integrado para HTTPS.
-
-Para habilitar HTTPS en tu proyecto de Next.js, abre el archivo `package.json` y edita la sección `scripts` de la siguiente manera:
-
-```json
-"scripts": {
-   "dev": "next dev --experimental-https",
-}
-```
-
-### Instalando Stellar SDK y otras dependencias
-
-Para interactuar con la red Stellar, necesitaremos instalar el Stellar SDK y algunas dependencias adicionales:
-
-```bash
-npm install stellar-sdk @stellar/freighter-api bignumber.js
-```
-
-- `stellar-sdk`: El SDK oficial de Stellar para interactuar con la red Stellar
-- `@stellar/freighter-api`: Una biblioteca para integrar con la billetera Freighter (una popular extensión de navegador para billeteras Stellar)
-- `bignumber.js`: Una biblioteca para aritmética decimal y no decimal de precisión arbitraria
-
-Ahora que tenemos nuestro entorno de desarrollo configurado, ¡estamos listos para comenzar a crear nuestra dapp Stellar!
-
-## 3. Creando elementos básicos de la interfaz
-
-En esta sección, crearemos componentes reutilizables para nuestra dapp Stellar e implementaremos formularios y entradas utilizando React y Tailwind CSS.
-
-### Creando componentes reutilizables
-
-Comencemos creando un componente de botón que utilizaremos en toda nuestra aplicación. Crea un nuevo archivo `components/Button.tsx`:
-
-```typescript
-import React from "react";
-
-interface ButtonProps {
-  onClick?: () => void;
-  children: React.ReactNode;
-  disabled?: boolean;
-  className?: string;
-}
-
-const Button: React.FC<ButtonProps> = ({
-  onClick,
-  children,
-  disabled = false,
-  className = "",
-}) => {
-  return (
-    <button
-      onClick={onClick}
-      disabled={disabled}
-      className={`px-4 py-2 font-bold text-white bg-blue-500 rounded hover:bg-blue-700 focus:outline-none focus:shadow-outline ${
-        disabled ? "opacity-50 cursor-not-allowed" : ""
-      } ${className}`}
-    >
-      {children}
-    </button>
-  );
-};
-
-export default Button;
-```
-
-Este componente de botón utiliza clases de Tailwind CSS para el estilo y acepta props para la personalización.
-
-A continuación, crearemos otro botón auxiliar para ayudar a conectar la billetera Freighter. Crea un nuevo archivo `components/ConnectWalletButton.tsx`:
-
-```typescript
-"use client";
-import React from "react";
-import { setAllowed } from "@stellar/freighter-api";
-
-export interface ConnectButtonProps {
-  label: string;
-  isHigher?: boolean;
-}
-
-export function ConnectButton({ label }: ConnectButtonProps) {
-  return (
-    <button
-      className={`bg-blue-500 hover:bg-blue-700 text-white font-bold py-2 px-4 rounded`}
-      onClick={setAllowed}
-    >
-      {label}
-    </button>
-  );
-}
-```
-
-Este componente de botón utiliza la función `setAllowed` de la biblioteca `@stellar/freighter-api` para conectar la billetera Freighter cuando se hace clic.
-
-### Implementando formularios y entradas
-
-A continuación, crearemos un componente de entrada reutilizable. Crea un nuevo archivo `components/Input.tsx`:
-
-```typescript
-import React from "react";
-
-interface InputProps {
-  type: string;
-  placeholder: string;
-  value: string;
-  onChange: (e: React.ChangeEvent<HTMLInputElement>) => void;
-  className?: string;
-}
-
-const Input: React.FC<InputProps> = ({
-  type,
-  placeholder,
-  value,
-  onChange,
-  className = "",
-}) => {
-  return (
-    <input
-      type={type}
-      placeholder={placeholder}
-      value={value}
-      onChange={onChange}
-      className={`shadow appearance-none border rounded w-full py-2 px-3 text-gray-700 leading-tight focus:outline-none focus:shadow-outline ${className}`}
-    />
-  );
-};
-
-export default Input;
-```
-
-Ahora, vamos a crear un componente de formulario que utilice estos componentes reutilizables. Crea un nuevo archivo `components/SendPaymentForm.tsx`:
-
-```typescript
-"use client";
-
-import React, { useState } from "react";
-
-import Button from "./Button";
-import Input from "./Input";
-
-interface SendPaymentFormProps {
-  onSubmit: (destination: string, amount: string) => void;
-}
-
-const SendPaymentForm: React.FC<SendPaymentFormProps> = ({ onSubmit }) => {
-  const [destination, setDestination] = useState("");
-  const [amount, setAmount] = useState("");
-
-  const handleSubmit = (e: React.FormEvent) => {
-    e.preventDefault();
-    onSubmit(destination, amount);
-  };
-
-  return (
-    <form onSubmit={handleSubmit} className="space-y-4">
-      <div>
-        <label
-          htmlFor="destination"
-          className="block text-sm font-medium text-gray-700"
-        >
-          Destination Address
-        </label>
-        <Input
-          type="text"
-          placeholder="GXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
-          value={destination}
-          required
-          onChange={(e) => setDestination(e.target.value)}
-        />
-      </div>
-      <div>
-        <label
-          htmlFor="amount"
-          className="block text-sm font-medium text-gray-700"
-        >
-          Amount (XLM)
-        </label>
-        <Input
-          type="number"
-          placeholder="0.0"
-          value={amount}
-          required
-          onChange={(e) => setAmount(e.target.value)}
-        />
-      </div>
-      <Button type="submit" disabled={!destination || !amount}>
-        Send Payment
-      </Button>
-    </form>
-  );
-};
-
-export default SendPaymentForm;
-```
-
-### Diseñando diseños responsivos con Tailwind CSS
-
-Para crear un diseño responsivo para nuestra dapp, utilizaremos clases de utilidad de Tailwind CSS. Creamos un componente de diseño que podamos usar en nuestras páginas. Edita el archivo `app/layout.tsx`:
-
-```typescript
-import "./globals.css";
-
-import { Inter } from "next/font/google";
-import type { Metadata } from "next";
-import React from "react";
-
-export const metadata: Metadata = {
-  title: "Stellar Payment DApp",
-  description: "Payment DApp built on Stellar",
-};
-
-interface LayoutProps {
-  children: React.ReactNode;
-}
-
-const Layout: React.FC<LayoutProps> = ({ children }) => {
-  return (
-    <html lang="en">
-      <body>
-        <div className="min-h-screen bg-gray-100">
-          <header className="bg-white shadow">
-            <div className="max-w-7xl mx-auto py-6 px-4 sm:px-6 lg:px-8">
-              <h1 className="text-3xl font-bold text-gray-900">Stellar Dapp</h1>
-            </div>
-          </header>
-          <main>
-            <div className="max-w-7xl mx-auto py-6 sm:px-6 lg:px-8">
-              <div className="px-4 py-6 sm:px-0">
-                <div className="border-4 border-dashed border-gray-200 rounded-lg h-96">
-                  {children}
-                </div>
-              </div>
-            </div>
-          </main>
-        </div>
-      </body>
-    </html>
-  );
-};
-
-export default Layout;
-```
-
-Ahora, actualicemos nuestro archivo `app/page.tsx` para usar este diseño y nuestros nuevos componentes:
-
-```typescript
-"use client";
-
-import React from "react";
-import SendPaymentForm from "../components/SendPaymentForm";
-
-export default function Home() {
-  const handleSendPayment = (destination: string, amount: string) => {
-    // We'll implement this function in the next section
-    console.log(`Sending ${amount} XLM to ${destination}`);
-  };
-
-  return (
-    <div className="max-w-md mx-auto">
-      <h2 className="text-2xl font-bold mb-4">Send Payment</h2>
-      <SendPaymentForm onSubmit={handleSendPayment} />
-    </div>
-  );
-}
-```
-
-Esta configuración proporciona una base sólida para construir la interfaz de usuario de nuestra dapp Stellar. En la próxima sección, integraremos estos componentes con el Stellar SDK para realizar operaciones reales de blockchain.
-
-## 4. Conceptos básicos de los contratos Soroban
-
-Antes de comenzar a integrar la funcionalidad de contratos inteligentes en nuestra dapp Stellar, entendamos los conceptos básicos de los contratos Soroban.
-
-Soroban es una plataforma de contratos inteligentes construida sobre la red Stellar. Permite a los desarrolladores escribir y desplegar contratos inteligentes que se ejecutan en la blockchain Stellar. Los contratos de Soroban están escritos en Rust y compilados a [XDR (Representación Externa de Datos)](../../../learn/fundamentals/data-format/xdr.mdx) para su ejecución en la red Stellar.
-
-### Tipos de datos
-
-Stellar admite algunos tipos de datos que pueden ser utilizados en contratos Soroban y necesitamos realizar conversiones de vez en cuando entre esos tipos y los tipos que tenemos en Javascript. La lista completa de tipos de datos primitivos se explica [aquí](../../../learn/fundamentals/contract-development/types/built-in-types.mdx).
-
-### XDR
-
-Los valores que se pasan a los contratos y se devuelven de los contratos se serializan usando XDR. XDR es un formato estándar de serialización de datos utilizado en Stellar para representar estructuras de datos complejas. Se utiliza para codificar y decodificar datos para su transmisión a través de la red Stellar. XDR se representa principalmente en Javascript como cadena y se puede convertir a otros tipos usando el Stellar SDK.
-
-### Tarifas
-
-Las tarifas de gas, como se les llama en la red Ethereum, se cobran de manera diferente aquí. Al enviar diferentes tipos de transacciones, el tipo de tarifas pagadas es diferente. Al enviar una transacción a la red que interactúa con ella, se paga una tarifa base junto con la tarifa de recursos para la operación. La tarifa base es una tarifa fija que se paga por cada transacción en la red. La tarifa de recursos es una tarifa que se paga por los recursos utilizados por la operación y se calcula en función de los recursos utilizados por la operación y el precio actual de recursos de la red.
-
-Calcular estas tarifas puede ser complicado, pero el Stellar SDK proporciona una manera de calcular estas tarifas utilizando el método `server.prepareTransaction` que simula la transacción, obtiene las tarifas apropiadas y agrega la configuración correcta de tarifas a la transacción.
-
-### ABI o Spec
-
-El ABI o spec es un archivo json que contiene la interfaz del contrato. Define las funciones que se pueden llamar en el contrato, sus parámetros y tipos de retorno. El ABI es utilizado por los clientes para interactuar con el contrato y ejecutar sus funciones. El ABI se genera a partir del código fuente del contrato y se utiliza para compilar el contrato en XDR para su ejecución en la red Stellar.
-
-El ABI se puede generar para un contrato usando el comando [`stellar contract bindings`](../../../tools/cli/stellar-cli.mdx#stellar-contract-bindings-json) y se puede usar para interactuar con el contrato.
-
-Este ABI también puede ser generado como una biblioteca de TypeScript para facilitar el desarrollo en tu DApp y lo veremos más adelante en esta guía
-
-## 5. Integrando con la blockchain Stellar
-
-Ahora que tenemos nuestros componentes básicos de UI en su lugar, integremoslos con la blockchain Stellar usando el Stellar SDK. Es imperativo saber que la blockchain Stellar tiene tres redes principales:
-
-- Red pública (también llamada Mainnet): Esta es la red Stellar principal donde ocurren transacciones reales.
-- Red de prueba: Este es un entorno de prueba para desarrolladores para probar sus aplicaciones sin usar lúmenes reales.
-- Red Futurenet: Esta es una red para probar nuevas características antes de que se implementen en la red pública.
-
-Para esta guía, utilizaremos la red de prueba para evitar usar lúmenes reales durante el desarrollo. Lee más sobre las [redes Stellar aquí](../../../networks/README.mdx).
-
-### Configurando el Stellar SDK
-
-A continuación se muestra un fragmento que muestra cómo configurar el Stellar SDK en tu proyecto. Usaremos partes de él mucho en esta guía así que intentemos entenderlo.
-
-```typescript
-import * as StellarSdk from "@stellar/stellar-sdk";
-
-import { rpc as StellarRpc } from "@stellar/stellar-sdk";
-
-export const server = new StellarRpc.Server("https://soroban-testnet.stellar.org"); // soroban testnet server
-
-const transaction = new StellarSdk.TransactionBuilder(account, {
-    fee:  StellarSdk.BASE_FEE
-    networkPassphrase: StellarSdk.Networks.TESTNET, // Use appropriate network
-})
-```
-
-En el fragmento anterior, importamos el Stellar SDK y creamos una instancia del servidor para el Stellar Testnet.
-
-También creamos una instancia de constructor de transacciones con la frase de paso de red apropiada. La `BASE_FEE` es la tarifa mínima requerida para una transacción en la red Stellar. mientras que la `Networks.TESTNET` es la frase de paso de red para el Stellar Testnet. Al usar la red pública, puedes reemplazar `TESTNET` por `PUBLIC` o `FUTURENET` para la red Futurenet.
-
-### Interaccionando con la red Stellar
-
-Si estás codificando a lo largo de esta guía en este punto, deberías tener una aplicación web mínima con un formulario para enviar pagos. Ahora, integremos este formulario con el Stellar SDK para enviar pagos reales en la red Stellar.
-
-Antes de continuar, asegúrate de haber configurado la extensión de billetera Freighter en tu navegador. Puedes descargarla [aquí](https://www.freighter.app). Además, asegúrate de tener lúmenes en la cuenta de Testnet que estás usando. Puedes obtener lúmenes gratis del [Stellar Friendbot](https://laboratory.stellar.org/#account-creator?network=test).
-
-Ahora, actualicemos nuestro componente `app/page` para interactuar con la red Stellar:
-
-```typescript
-"use client";
-
-import React, { useState, useEffect } from "react";
-import SendPaymentForm from "../components/SendPaymentForm";
-import * as StellarSdk from "@stellar/stellar-sdk";
-import { rpc as StellarRpc } from "@stellar/stellar-sdk";
-import {
-  isConnected,
-  setAllowed,
-  getAddress,
-  signTransaction,
-} from "@stellar/freighter-api";
-
-export default function Home() {
-  const [publicKey, setPublicKey] = useState<string | null>(null);
-
-  useEffect(() => {
-    const checkFreighter = async () => {
-      try {
-        const connected = await isConnected();
-        if (connected) {
-          const pubKey = await getAddress();
-          setPublicKey(pubKey.address);
-        }
-      } catch (error) {
-        console.error("Error checking Freighter connection:", error);
-      }
-    };
-
-    checkFreighter();
-  }, []);
-
-  const handleConnectWallet = async () => {
-    try {
-      await setAllowed();
-      const pubKey = await getAddress();
-      setPublicKey(pubKey.address);
-    } catch (error) {
-      console.error("Error connecting to Freighter:", error);
-    }
-  };
-
-  const handleSendPayment = async (destination: string, amount: string) => {
-    if (!publicKey) {
-      console.error("Wallet not connected");
-      return;
-    }
-
-    try {
-      const server = new StellarRpc.Server(
-        "https://soroban-testnet.stellar.org",
-      );
-      const sourceAccount = await server.getAccount(publicKey);
-      const transaction = new StellarSdk.TransactionBuilder(sourceAccount, {
-        fee: StellarSdk.BASE_FEE,
-        networkPassphrase: StellarSdk.Networks.TESTNET,
-      })
-        .addOperation(
-          StellarSdk.Operation.payment({
-            destination: destination,
-            asset: StellarSdk.Asset.native(),
-            amount: amount,
-          }),
-        )
-        .setTimeout(30)
-        .build();
-
-      const signedTransaction = await signTransaction(transaction.toXDR(), {
-        networkPassphrase: StellarSdk.Networks.TESTNET,
-      });
-
-      const transactionResult = await server.sendTransaction(
-        StellarSdk.TransactionBuilder.fromXDR(
-          signedTransaction.signedTxXdr,
-          StellarSdk.Networks.TESTNET,
-        ),
-      );
-
-      console.log("Transaction successful:", transactionResult);
-      alert("Payment sent successfully!");
-    } catch (error) {
-      console.error("Error sending payment:", error);
-      alert("Error sending payment. Please check the console for details.");
-    }
-  };
-
-  return (
-    <div className="max-w-md mx-auto">
-      <h2 className="text-2xl font-bold mb-4">Send Payment</h2>
-      {publicKey ? (
-        <>
-          <p className="mb-4">Connected: {publicKey}</p>
-          <SendPaymentForm onSubmit={handleSendPayment} />
-        </>
-      ) : (
-        <button
-          onClick={handleConnectWallet}
-          className="bg-blue-500 hover:bg-blue-700 text-white font-bold py-2 px-4 rounded"
-        >
-          Connect Freighter Wallet
-        </button>
-      )}
-    </div>
-  );
-}
-```
-
-En el componente `app/page` actualizado, agregamos un hook `useEffect` para verificar si la billetera Freighter está conectada y recuperar la clave pública. También agregamos una función `handleConnectWallet` para conectar la billetera si no está ya conectada.
-
-La función `handleSendPayment` ahora interactúa con la red Stellar para enviar un pago. Recupera los detalles de la cuenta de origen, crea una transacción de pago, firma la transacción usando la billetera Freighter, y envía la transacción a la red Stellar. Si la transacción es exitosa, muestra una alerta al usuario.
-
-Observa cómo importamos las funciones `isConnected`, `setAllowed`, `getAddress` y `signTransaction` de la biblioteca `@stellar/freighter-api`. Estas funciones se utilizan para interactuar con la extensión de billetera Freighter y firmar transacciones de forma segura.
-
-:::tip
-
-¡Hurra! Has integrado con éxito tu dapp Stellar con la red Stellar. Ahora puedes enviar pagos usando la extensión de billetera Freighter en el Stellar Testnet.
-
-:::
-
-### Interactuando con contratos inteligentes
-
-En el ejemplo anterior, enviamos una transacción de pago simple utilizando la operación `StellarSdk.Operation.payment`. Sin embargo, Stellar también soporta muchas otras operaciones, una de las cuales es la operación `invokeHostFunction` que se utiliza para interactuar con contratos inteligentes en la red Stellar.
-
-Trabajaremos con una versión desplegada del [contrato inteligente contador](https://github.com/stellar/soroban-examples/tree/main/events) en el Stellar Testnet. El contrato inteligente tiene una única función `increment` que incrementa un valor contador almacenado en la red Stellar.
-
-Crea un nuevo archivo `app/counter/page.tsx`:
-
-```typescript
-"use client";
-
-import {
-  BASE_FEE,
-  Contract,
-  Networks,
-  rpc as StellarRpc,
-  Transaction,
-  TransactionBuilder,
-  xdr,
-} from "@stellar/stellar-sdk";
-import React, { useEffect, useState } from "react";
-import {
-  getAddress,
-  isConnected,
-  signTransaction,
-} from "@stellar/freighter-api";
-
-import { ConnectButton } from "@/components/ConnectButton";
-
-// Replace with your actual contract ID and network details
-const CONTRACT_ID = "CBWNXQRGC7WFYGDXUANDAZSRF2E5NPPA3NP6UZSPHYBVU3K46PSNWQOO";
-const NETWORK_PASSPHRASE = Networks.TESTNET;
-const SOROBAN_URL = "https://soroban-testnet.stellar.org:443";
-
-export default function CounterPage() {
-  const [publicKey, setPublicKey] = useState<string | null>(null);
-  const [count, setCount] = useState<number | null>(null);
-  const [loading, setLoading] = useState(false);
-
-  const server = new StellarRpc.Server(SOROBAN_URL);
-
-  useEffect(() => {
-    const checkWallet = async () => {
-      const connected = await isConnected();
-      if (connected) {
-        const pubKey = await getAddress();
-        setPublicKey(pubKey.address);
-      }
-    };
-
-    checkWallet();
-  }, []);
-
-  const handleIncrement = async () => {
-    if (!publicKey) {
-      console.error("Wallet not connected");
-      return;
-    }
-
-    setLoading(true);
-
-    try {
-      const account = await server.getAccount(publicKey);
-
-      const contract = new Contract(CONTRACT_ID);
-      // const instance = contract.getFootprint();
-
-      const tx = new TransactionBuilder(account, {
-        fee: BASE_FEE,
-        networkPassphrase: NETWORK_PASSPHRASE,
-      })
-        .addOperation(contract.call("increment"))
-        .setTimeout(30)
-        .build();
-
-      const preparedTx = await server.prepareTransaction(tx);
-
-      const signedXdr = await signTransaction(
-        preparedTx.toEnvelope().toXDR("base64"),
-        {
-          networkPassphrase: NETWORK_PASSPHRASE,
-        },
-      );
-
-      const signedTx = TransactionBuilder.fromXDR(
-        signedXdr.signedTxXdr,
-        NETWORK_PASSPHRASE,
-      ) as Transaction;
-
-      const txResult = await server.sendTransaction(signedTx);
-
-      if (txResult.status !== "PENDING") {
-        throw new Error("Something went Wrong");
-      }
-      const hash = txResult.hash;
-      let getResponse = await server.getTransaction(hash);
-      // Poll `getTransaction` until the status is not "NOT_FOUND"
-
-      while (getResponse.status === "NOT_FOUND") {
-        console.log("Waiting for transaction confirmation...");
-        getResponse = await server.getTransaction(hash);
-        await new Promise((resolve) => setTimeout(resolve, 1000));
-      }
-
-      if (getResponse.status === "SUCCESS") {
-        // Make sure the transaction's resultMetaXDR is not empty
-        if (!getResponse.resultMetaXdr) {
-          throw "Empty resultMetaXDR in getTransaction response";
-        }
-      } else {
-        throw `Transaction failed: ${getResponse.resultXdr}`;
-      }
-
-      // Extract the new count from the transaction result
-      const returnValue = getResponse.resultMetaXdr
-        .v4()
-        .sorobanMeta()
-        ?.returnValue();
-      if (returnValue) {
-        const newCount = returnValue.u32();
-        setCount(newCount);
-      }
-    } catch (error) {
-      console.error("Error incrementing counter:", error);
-      alert(
-        "Error incrementing counter. Please check the console for details.",
-      );
-    } finally {
-      setLoading(false);
-    }
-  };
-
-  return (
-    <div className="max-w-md mx-auto mt-10 text-black">
-      <h1 className="text-2xl font-bold mb-4">
-        Stellar Smart Contract Counter
-      </h1>
-      {publicKey ? (
-        <div>
-          <p className="mb-4">Connected: {publicKey}</p>
-          <p className="mb-4">
-            Current Count: {count === null ? "Unknown" : count}
-          </p>
-          <button
-            onClick={handleIncrement}
-            disabled={loading}
-            className="bg-blue-500 hover:bg-blue-700 text-white font-bold py-2 px-4 rounded disabled:opacity-50"
-          >
-            {loading ? (
-              <span className="flex items-center">
-                <svg
-                  className="animate-spin -ml-1 mr-3 h-5 w-5 text-white"
-                  xmlns="http://www.w3.org/2000/svg"
-                  fill="none"
-                  viewBox="0 0 24 24"
-                >
-                  <circle
-                    className="opacity-25"
-                    cx="12"
-                    cy="12"
-                    r="10"
-                    stroke="currentColor"
-                    strokeWidth="4"
-                  ></circle>
-                  <path
-                    className="opacity-75"
-                    fill="currentColor"
-                    d="M4 12a8 8 0 018-8V0C5.373 0 0 5.373 0 12h4zm2 5.291A7.962 7.962 0 014 12H0c0 3.042 1.135 5.824 3 7.938l3-2.647z"
-                  ></path>
-                </svg>
-                Processing...
-              </span>
-            ) : (
-              "Increment Counter"
-            )}
-          </button>
-        </div>
-      ) : (
-        <>
-          <p>Please connect your Freighter wallet to use this app.</p>
-          <ConnectButton label="Connect Wallet" />
-        </>
-      )}
-    </div>
-  );
-}
-```
-
-En el fragmento de código anterior, creamos un nuevo componente de página `CounterPage` que interactúa con el contrato inteligente contador en la red Stellar. La función `handleIncrement` envía una transacción al contrato inteligente para incrementar el valor del contador. Luego recupera el valor actualizado del contador del resultado de la transacción y lo muestra al usuario.
-
-Observa cómo utilizamos una operación diferente `contract.call("increment")` para interactuar con el contrato inteligente. Esta operación es una fachada para la operación `invokeHostFunction` en la red Stellar. También utilizamos los métodos `prepareTransaction` y `sendTransaction` para enviar la transacción a la red y recuperar el resultado de la transacción.
-
-La llamada `prepareTransaction` se utiliza para preparar una transacción para su presentación a la red. Simula la transacción, luego utiliza las tarifas de recursos apropiadas y otros parámetros para crear una transacción que esté lista para enviarse a la red.
-
-`<ConnectButton>` es un botón auxiliar que conecta la billetera Freighter cuando se hace clic, como describimos anteriormente.
-
-Después de llamar a la transacción para incrementar exitosamente, necesitamos hacer polling y luego llamar a otro método `server.getTransaction` para obtener el resultado de la transacción. El resultado de la transacción contiene el nuevo valor del contador que extraemos y mostramos al usuario.
-
-El valor obtenido del resultado de la transacción se almacena en una forma llamada `scval` debido al número limitado de [tipos](../../../learn/fundamentals/contract-development/types/built-in-types.mdx) que existen en soroban hoy en día. This value is transmitted about in the form of `xdr` which can be converted to an `scVal` using the sdk. El valor se analiza luego como `u32` que es un entero sin signo de 32 bits. Aprenderemos más sobre cómo convertir estos tipos [en esta colección de guías](../conversions/README.mdx).
-
-:::tip
-
-¡Felicidades! Has interactuado exitosamente con un contrato inteligente en la red Stellar usando tu dapp.
-
-:::
-
-### Leyendo eventos de la red Stellar
-
-Los eventos en Stellar son valores emitidos por contratos agrupados por temas. Estos eventos se emiten cuando se llama a un contrato y pueden ser leídos por cualquier cliente interesado en el contrato. Los eventos se almacenan en el ledger de Stellar y pueden ser leídos por cualquier cliente interesado en el contrato.
-
-Además de enviar transacciones e interactuar con contratos inteligentes, también puedes leer eventos de la red Stellar utilizando el Stellar SDK. Esto te permite monitorear cambios en cuentas, estado de transacciones y otros eventos de red en tiempo real.
-
-Esto es posible utilizando el método `server.getEvents`, que te permite consultar eventos basados en temas. Consideraremos un ejemplo simple donde leemos eventos del contrato inteligente contador con el que interactuamos anteriormente.
-
-Estaremos editando el componente `CounterPage` para leer eventos del contrato inteligente contador inmediatamente cuando se cargue la página para obtener el valor inicial del contador y actualizar en lugar de usar "Desconocido". Antes de continuar, por favor revisa el [código del contrato](https://github.com/stellar/soroban-examples/blob/main/events/src/lib.rs). En el código del contrato, un evento llamado `increment` se emite cada vez que se llama a la función `increment`. Se publica en 2 temas, `increment` y `COUNTER`, y necesitamos escuchar estos temas para obtener los eventos.
-
-Los temas se almacenan en un tipo de dato llamado `symbol` y necesitaremos convertir tanto `increment` como `COUNTER` a `symbol` antes de poder usarlos en el método [`server.getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents.mdx). Como máximo, los RPC estelares rastrean eventos durante 7 días y puedes consultar eventos que hayan ocurrido en los últimos 7 días, por lo que, si necesitas almacenar eventos por más tiempo, puede que necesites usar un [indexer](../../../data/indexers/README.mdx).
-
-Para usar eventos, editamos nuestra página de contador y añadimos el siguiente código:
-
-```typescript
-useEffect(() => {
-  const checkWallet = async () => {
-    const connected = await isConnected();
-    if (connected) {
-      const pubKey = await getAddress();
-      setPublicKey(pubKey.address);
-    }
-  };
-  checkWallet();
-  getInitialCount();
-}, []);
-
-const getInitialCount = async () => {
-  try {
-    const topic1 = xdr.ScVal.scvSymbol("COUNTER").toXDR("base64");
-    const topic2 = xdr.ScVal.scvSymbol("increment").toXDR("base64");
-
-    const latestLedger = await server.getLatestLedger();
-    const events = await server.getEvents({
-      startLedger: latestLedger.sequence - 2000,
-      filters: [
-        {
-          type: "contract",
-          contractIds: [CONTRACT_ID],
-          topics: [[topic1, topic2]],
-        },
-      ],
-      limit: 20,
-    });
-    setCount(events.events.map((e) => e.value.u32()).pop() || null);
-  } catch (error) {
-    console.error(error);
-  }
-};
-```
-
-En el código anterior, usamos un método RPC llamado `getEvents` para consultar eventos de la red Stellar. Pasamos el ID del contrato, los temas y otros filtros como el ledger para comenzar la búsqueda desde 2000 ledgers atrás para obtener los eventos que nos interesan. Luego extraemos el valor del contador de los eventos y actualizamos el estado en consecuencia.
-
-Sin embargo, tuvimos que convertir los temas `COUNTER` e `increment` a `symbol` usando el `xdr.ScVal.scvSymbol` y luego convertirlos a XDR antes de poder usarlos en el método `getEvents`. Esto se debe a que los temas se almacenan en forma de `symbol` y se transmiten en formato XDR a la red, como discutimos anteriormente. De manera similar, el valor del nuevo conteo se envía a través de la red como XDR, pero el SDK nos ayudó a convertirlo a un `scVal` y luego lo parseamos como un `u32` para obtener el valor real.
-
-El código fuente para este programa está disponible [aquí](https://github.com/myestery/stellar-dapp)
-
-Ahora, cuando la página se carga, consultará los eventos de la red Stellar y actualizará el valor del contador en consecuencia.
-
-## 6. Usar las vinculaciones de Typescript
-
-El Stellar CLI viene con soporte para exportar una especificación de contrato a una biblioteca de typescript. Esta biblioteca está optimizada para importar como un módulo basado en npm en tu aplicación.
-
-La biblioteca generada contiene métodos auxiliares para llamar a cada contrato y también realiza una conversión automática de tipos para cualquier método de contrato.
-
-### Cómo crear la biblioteca de vinculación
-
-Para lograr esto, necesitas
-
-- Tener instalado el [Stellar CLI](../../../tools/cli/install-cli.mdx).
-- Tener el código fuente o el ID del contrato desplegado del contrato.
-- Conocer la red a la que se desplegó.
-
-#### Escenario 1: Tengo el ID del contrato pero no el código
-
-En este escenario, necesitamos usar el comando [`stellar contract fetch`](../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch) para obtener el código wasm del contrato
-
-#### Escenario 2: Tengo el código
-
-El siguiente paso aquí es crear un archivo wasm usando el comando [`stellar contract build`](../../../tools/cli/stellar-cli.mdx#stellar-contract-build).
-
-### Generando la biblioteca
-
-Después de obtener el wasm, ahora podemos ejecutar [`stellar contract bindings typescript`](../../../tools/cli/stellar-cli.mdx#stellar-contract-bindings-typescript) para generar la biblioteca que está lista para ser publicada en NPM. La biblioteca generada es adecuada para trabajar con contratos complejos.
-
-## 7. Trampas comunes
-
-A continuación se presentan algunas trampas comunes que los desarrolladores de DApp de Soroban podrían encontrar
-
-### Conversiones de tipo de datos
-
-Los tipos de datos en Javascript son diferentes de los tipos de datos en Soroban. Al trabajar con contratos Soroban, debes ser consciente de los tipos de datos y cómo convertirlos a los tipos que conoces en Javascript. El Stellar SDK proporciona métodos auxiliares para convertir entre tipos XDR y Javascript en el espacio de nombres `xdr`.
-
-### Honorarios
-
-Calcular tarifas para transacciones puede ser complicado. El Stellar SDK proporciona una manera de calcular tarifas utilizando el método `server.prepareTransaction`, que simula la transacción y devuelve las tarifas apropiadas. Las tarifas se calculan en [stroops](../../../learn/glossary.mdx#stroop)
-
-### Enviar transacciones y obtener transacciones
-
-Los resultados de la ejecución de un contrato inteligente o de cualquier transacción [válida](../../../learn/fundamentals/transactions/list-of-operations.mdx#extend-footprint-ttl) en soroban no son inmediatos. Se mantienen en un estado `PENDING` hasta que se confirmen. Necesitas consultar el método `getTransaction` para obtener el resultado final de la transacción.
-
-### Archivado de estado
-
-El archivado de estado es una característica de los contratos Soroban donde algunos datos almacenados en el ledger sobre el contrato podrían ser archivados. Estas [guías](../archival/README.mdx) ayudan a entender cómo trabajar con el archivado de estado en DApps.
-
-### Retención de datos
-
-Los datos solo pueden consultarse dentro de la ventana de retención configurada de la instancia RPC que estás utilizando (el valor predeterminado es de 7 días). Por lo tanto, puede que necesites un indexador para almacenar datos de transacciones o eventos durante períodos más largos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/initialization.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/initialization.mdx
deleted file mode 100644
index 54fa3e0f81..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/initialization.mdx
+++ /dev/null
@@ -1,201 +0,0 @@
----
-title: Inicializa una dapp usando scripts
-description: Configura la inicialización correctamente para asegurar un proceso fluido para tu dapp
----
-
-Al configurar un ejemplo de Dapp Soroban, la inicialización correcta es crucial. Este proceso implica varios pasos, incluyendo desplegar Docker, clonar y desplegar contratos inteligentes, e invocar funciones para configurarlos. En esta guía completa, te guiaré a través de los pasos necesarios para crear y desplegar estos contratos inteligentes, asegurando un proceso fluido para tu Dapp Soroban.
-
-## Desarrollar el Contrato Inteligente Soroban Token
-
-En dapps como el [Ejemplo de Dapp de Pago](https://github.com/stellar/soroban-react-payment/), los [contratos inteligentes Token Soroban](https://github.com/stellar/soroban-examples/tree/main/token) se utilizan para representar el activo tokenizado que los usuarios pueden enviar y recibir. Aquí hay un ejemplo de cómo crear y desplegar los contratos inteligentes Token Soroban:
-
-Comienza clonando el repositorio de ejemplos de Soroban:
-
-```shell
-git clone https://github.com/stellar/soroban-examples.git
-```
-
-Luego, navega al directorio `token`:
-
-```shell
-cd soroban-examples/token
-```
-
-En este punto, puedes construir el contrato inteligente:
-
-```shell
-make
-```
-
-Esta acción compilará los contratos inteligentes y los colocará en el directorio `token/target/wasm32v1-none/release`. Después de desarrollarlo, estás listo para desplegar los contratos inteligentes en Testnet.
-
-## Desplegar e Inicializar el Contrato Inteligente Soroban Token
-
-El contrato inteligente puede inicializarse en el momento del despliegue utilizando la función `__constructor`. Esta función se llamará en el momento del despliegue y puede declararse con parámetros que puedes pasar a la función con el comando de despliegue.
-
-La función `__constructor` se añade al punto de entrada del contrato; en este contrato inteligente `token` se encuentra en el archivo [contract.rs](https://github.com/stellar/soroban-examples/blob/main/token/src/contract.rs).
-
-```rust title="contract.rs"
-#[contractimpl]
-impl Token {
-  pub fn __constructor(e: Env, admin: Address, decimal: u32, name: String, symbol: String) {
-      if decimal > 18 {
-          panic!("Decimal must not be greater than 18");
-      }
-      write_administrator(&e, &admin);
-      write_metadata(
-          &e,
-          TokenMetadata {
-              decimal,
-              name,
-              symbol,
-          },
-      )
-  }
-  ...
-}
-```
-
-La función `__constructor` en este proyecto de ejemplo recibe los siguientes parámetros:
-
-- Cuenta del administrador: Esta es la clave pública de la cuenta del administrador. El administrador tiene control y autoridad sobre el contrato del token, lo que permite gestionar diversas funcionalidades del contrato. Aprende más sobre el rol del administrador en la Interfaz del Soroban Token.
-
-- Precisión decimal: La precisión decimal especifica el número máximo de decimales que el token puede admitir en las transacciones. Este nivel de precisión permite flexibilidad al transferir cantidades del token.
-
-- Nombre del token: El nombre del token.
-
-- Símbolo del token: Este es el símbolo del token.
-
-Para desplegar el contrato inteligente en este ejemplo, abre una terminal en el directorio `soroban-examples/token` y ejecuta lo siguiente:
-
-```shell
-stellar contract deploy \
- --wasm target/wasm32v1-none/release/soroban_token_contract.wasm \
- --source-account alice \
- --rpc-url https://soroban-testnet.stellar.org \
- --network-passphrase 'Test SDF Network ; September 2015'
- -- \
- --admin alice \
- --decimal 10 \
- --name 'Demo Token' \
- --symbol 'DT'
-```
-
-Este comando despliega los contratos inteligentes en Testnet utilizando la función `stellar contract deploy`. El contrato inteligente se desplegará con los parámetros obligatorios y se inicializará con estos valores.
-
-## Crear Tokens
-
-Por último, necesitas crear algunos tokens para la cuenta del remitente:
-
-```shell
-stellar contract invoke \
- --id <TOKEN_CONTRACT_ID> \
- --source-account alice \
- --rpc-url https://soroban-testnet.stellar.org \
- --network-passphrase 'Test SDF Network ; September 2015'
- -- mint \
- --to bob \
- --amount 1000000000
-```
-
-Este comando acuñará 100 tokens en la cuenta del usuario designado, en este caso `bob`.
-
-Al seguir estos pasos, aseguras que los contratos inteligentes Token Soroban estén correctamente desplegados e inicializados, preparando el escenario para que la Dapp interactúe efectivamente con el token.
-
-Para profundizar en los comandos CLI de Stellar, consulta el [repositorio CLI de Stellar](https://github.com/stellar/stellar-cli/blob/main/FULL_HELP_DOCS.md).
-
-## Automatizando la Inicialización con Scripts
-
-Para optimizar el proceso de inicialización, puedes usar un script. Este script debería automatizar varias tareas como configurar la red, generar identidades admin-token, financiar la cuenta admin-token, construir y desplegar los contratos, e inicializarlos con los parámetros necesarios.
-
-Aquí hay un ejemplo de script de inicialización:
-
-```bash title="initialize.sh"
-#!/bin/bash
-
-set -e
-
-NETWORK="$1"
-
-# If stellar-cli is called inside the soroban-preview docker container,
-# it can call the stellar standalone container just using its name "stellar"
-if [[ "$IS_USING_DOCKER" == "true" ]]; then
-  SOROBAN_RPC_HOST="http://stellar:8000"
-else
-  SOROBAN_RPC_HOST="http://localhost:8000"
-fi
-
-case "$1" in
-standalone)
-  echo "Using standalone network"
-  SOROBAN_NETWORK_PASSPHRASE="Standalone Network ; February 2017"
-  FRIENDBOT_URL="$SOROBAN_RPC_HOST/friendbot"
-  SOROBAN_RPC_URL="$SOROBAN_RPC_HOST/soroban/rpc"
-  ;;
-futurenet)
-  echo "Using Futurenet network"
-  SOROBAN_NETWORK_PASSPHRASE="Test SDF Future Network ; October 2022"
-  FRIENDBOT_URL="https://friendbot-futurenet.stellar.org/"
-  SOROBAN_RPC_URL="https://rpc-futurenet.stellar.org"
-  ;;
-testnet)
-  echo "Using Testnet network"
-  SOROBAN_NETWORK_PASSPHRASE="Test SDF Network ; September 2015"
-  FRIENDBOT_URL="https://friendbot.stellar.org/"
-  SOROBAN_RPC_URL="https://soroban-testnet.stellar.org"
-  ;;
-*)
-  echo "Usage: $0 standalone|futurenet|testnet"
-  exit 1
-  ;;
-esac
-
-echo Add the $NETWORK network to cli client
-stellar network add \
-  --rpc-url "$SOROBAN_RPC_URL" \
-  --network-passphrase "$SOROBAN_NETWORK_PASSPHRASE" "$NETWORK"
-
-if !(stellar keys ls | grep token-admin 2>&1 >/dev/null); then
-  echo Create the token-admin identity
-  stellar keys generate token-admin
-fi
-TOKEN_ADMIN_SECRET="$(stellar keys show token-admin)"
-TOKEN_ADMIN_ADDRESS="$(stellar keys address token-admin)"
-
-echo "$TOKEN_ADMIN_SECRET" > .soroban-example-dapp/token_admin_secret
-echo "$TOKEN_ADMIN_ADDRESS" > .soroban-example-dapp/token_admin_address
-
-# This will fail if the account already exists, but it'll still be fine.
-echo Fund token-admin account from friendbot
-curl --silent -X POST "$FRIENDBOT_URL?addr=$TOKEN_ADMIN_ADDRESS" >/dev/null
-
-echo Build the contract
-make build
-
-echo Deploy the contract
-ARGS="--network $NETWORK --source-account token-admin -- --admin $2 --decimal $3 --name $4 --symbol $5"
-CROWDFUND_ID="$(
-  stellar contract deploy $ARGS \
-    --wasm target/wasm32v1-none/release/soroban_token_contract.wasm
-)"
-echo "Contract deployed successfully with ID: $CROWDFUND_ID"
-echo "$CROWDFUND_ID" > .soroban-example-dapp/crowdfund_id
-
-echo "Done"
-```
-
-Aquí tienes un resumen de lo que hace el script `initialize.sh`:
-
-- Identifica la red (standalone o futurenet) basado en la entrada del usuario
-- Determina la URL del host RPC Stellar dependiendo de su entorno de ejecución (ya sea dentro del contenedor Docker de soroban-preview o localmente)
-- Establece la URL RPC de Stellar basada en la URL del host previamente determinada
-- Establece la frase de paso de la red Soroban y la URL de Friendbot dependiendo de la red elegida
-- Agrega la configuración de red usando `stellar network add`
-- Genera una identidad de administrador de token usando `stellar keys generate`
-- Recoge el TOKEN_ADMIN_SECRET y el TOKEN_ADMIN_ADDRESS de la identidad recién generada
-- Guarda el TOKEN_ADMIN_SECRET y el TOKEN_ADMIN_ADDRESS en el directorio .soroban
-- Financia la cuenta del administrador de token usando Friendbot
-- Desarrolla el contrato con `make build` y lo despliega usando `stellar contract deploy`, almacenando el CROWDFUND_ID devuelto
-- Imprime "Hecho" para significar el final del proceso de inicialización
-
-Al aprovechar la inicialización automatizada, puedes optimizar el proceso de configuración para tu Dapp Soroban, asegurando que esté correctamente desplegada e inicializada.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/react.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/react.mdx
deleted file mode 100644
index 566ec0e2ed..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/react.mdx
+++ /dev/null
@@ -1,140 +0,0 @@
----
-title: Crear un frontend para tu dapp usando React
-description: Conectar frontends de dapp a contratos y la billetera Freighter usando @soroban-react
-draft: true
----
-
-Esta sección explica cómo los frontends de tu dapp pueden interactuar con los contratos de ejemplo y acceder a datos de la cadena, además de conectarse a una billetera freighter. Esto se ilustrará utilizando bibliotecas proporcionadas por [`@soroban-react`](https://soroban-react.gitbook.io/index/), un marco simple y poderoso para desarrollar Dapps modernas usando React. `@soroban-react` fue creada y es mantenida por un increíble miembro de la comunidad!
-
-:::info
-
-Esta guía demostrará cómo se desarrolló un frontend de un [dapp de crowdfunding de ejemplo] con React. Aunque gran parte del código es específico para este proyecto, los principios demostrados deberían ser lo suficientemente educativos para ayudarte a comenzar.
-
-:::
-
-A continuación se muestra una lista de las bibliotecas utilizadas a lo largo del código del frontend y sus respectivas importaciones:
-
-```jsx
-import { SorobanReactProvider } from "@soroban-react/core";
-import { testnet, sandbox, standalone } from "@soroban-react/chains";
-import { freighter } from "@soroban-react/freighter";
-import { ChainMetadata, Connector } from "@soroban-react/types";
-import type {
-  WalletChain,
-  ChainMetadata,
-  ChainName,
-} from "@soroban-react/types";
-import { useSorobanReact } from "@soroban-react/core";
-```
-
-Estas importaciones incluyen `SorobanReactProvider` de `@soroban-react/core`, que es un proveedor de contexto utilizado para pasar la instancia de SorobanReact a otros componentes. También importas varios tipos como `WalletChain`, `ChainMetadata` y `ChainName`, que ayudan a mantener la seguridad de tipos dentro de nuestra aplicación.
-
-## Componentes de React y Pasaje de Props
-
-React prospera en su arquitectura basada en componentes. Los componentes son piezas reutilizables de código que devuelven un elemento de React para ser renderizado en la página. Una aplicación típica de React consiste en múltiples componentes que trabajan en armonía para crear una interfaz de usuario dinámica.
-
-Miremos un componente del [dapp de crowdfunding de ejemplo], el [componente `MintButton`](https://github.com/stellar/soroban-example-dapp/blob/07504b922bc75a48e5220711aea2cb4962f90367/components/molecules/form-pledge/index.tsx#L27):
-
-```tsx
-function MintButton({
-  account,
-  decimals,
-  symbol,
-}: {
-  account: string;
-  decimals: number;
-  symbol: string;
-}) {
-  const [isSubmitting, setSubmitting] = useState(false);
-  const { activeChain, server } = useNetwork();
-  const networkPassphrase = activeChain?.networkPassphrase ?? "";
-  const { sendTransaction } = useSendTransaction();
-  const amount = BigNumber(100);
-
-  return <Button props omitted here />;
-}
-```
-
-Este componente funcional toma tres propiedades como argumentos: `account`, `decimals` y `symbol`. Demuestra el concepto de paso de props, una forma de pasar datos de componentes padre a hijo en React. La prop `onComplete` incluso te permite pasar funciones a tus componentes como props. También vemos el hook `useState` de React para la gestión del estado local, un método para preservar valores entre llamadas a funciones.
-
-## Gestión del Estado y Hooks
-
-La gestión del estado es otro concepto central de React, permitiendo que los componentes creen y manejen sus propios datos. El `useState` hook es una característica introducida en React 16.8 que permite a los componentes funcionales tener su propio estado.
-
-En el componente `MintButton`, el hook `useState` se utiliza para gestionar el estado `isSubmitting`:
-
-```tsx
-const [isSubmitting, setSubmitting] = useState(false);
-```
-
-El hook `useState` devuelve un par de valores: el estado actual y una función que lo actualiza. En este caso, el estado `isSubmitting` se inicializa en `false` y la función `setSubmitting` se utiliza para actualizarlo. React también permite la creación de hooks personalizados, como `useNetwork` y `useSendTransaction`, para encapsular y reutilizar lógica con estado en múltiples componentes.
-
-## Hooks Personalizados
-
-Los hooks de React son funciones que te permiten “conectar” con el estado de React y las características del ciclo de vida desde componentes funcionales. Los hooks personalizados te permiten encapsular lógica compleja y hacerla reutilizable en componentes. Miremos a `useNetwork` y `useSendTransaction`, dos hooks personalizados utilizados en el [dapp de crowdfunding de ejemplo].
-
-El hook `useNetwork` se utiliza para interactuar con la red de blockchain, y el hook `useSendTransaction` se usa para despachar transacciones. Estos hooks abstraen lógica compleja, facilitando la lectura y comprensión del código principal del componente.
-
-Así es como usas estos hooks en el componente `MintButton`:
-
-```tsx
-const { activeChain, server } = useNetwork();
-const networkPassphrase = activeChain?.networkPassphrase ?? "";
-const { sendTransaction } = useSendTransaction();
-```
-
-`useNetwork` proporciona la cadena activa y el servidor, y `useSendTransaction` nos da el método `sendTransaction`, que usarás más tarde para acuñar tokens. De esta manera, puedes mantener el componente enfocado en la renderización y la lógica de manejo de eventos, facilitando su prueba y mantenimiento.
-
-## Procesamiento Asincrónico y Manejo Robusto de Errores
-
-Al tratar con operaciones que pueden tomar un tiempo impredecible, como peticiones de red o, en nuestro caso, acuñar tokens en la blockchain, el soporte de React para operaciones asincrónicas es crucial. Esto permite la ejecución del resto del código sin ser bloqueado por estas operaciones.
-
-Adentrémonos en el fragmento de código que maneja el proceso de acuñación asincrónica:
-
-```tsx
-try {
-  console.log("Minting the token...");
-  const paymentResult = await sendTransaction(
-    new SorobanClient.TransactionBuilder(adminSource, {
-      networkPassphrase,
-      fee: "1000",
-    })
-      .setTimeout(10)
-      .addOperation(
-        SorobanClient.Operation.payment({
-          destination: walletSource.accountId(),
-          asset: new SorobanClient.Asset(symbol, Constants.TokenAdmin),
-          amount: amount.toString(),
-        }),
-      )
-      .build(),
-    {
-      timeout: 10 * 1000,
-      skipAddingFootprint: true,
-      secretKey: Constants.TokenAdminSecretKey,
-      sorobanContext,
-    },
-  );
-  console.debug(paymentResult);
-  sorobanContext.connect();
-} catch (err) {
-  console.log("Error while minting the token: ", err);
-  console.error(err);
-}
-```
-
-Este bloque es donde ocurre la acuñación real de tokens. Está envuelto en un bloque `try-catch`, asegurando que cualquier error durante el proceso de acuñación sea capturado y manejado adecuadamente, evitando que la aplicación se bloquee y dándote la oportunidad de proporcionar retroalimentación al usuario.
-
-La palabra clave `await` pausa la ejecución de la función hasta que la promesa devuelta por `sendTransaction` se resuelva. `sendTransaction` es una función obtenida de nuestro hook `useSendTransaction`, y construye y envía una operación de pago a la red Stellar.
-
-El método `sendTransaction` acepta dos argumentos: una instancia de `TransactionBuilder` y un objeto de opciones. El `TransactionBuilder` establece los detalles de la transacción, como la cuenta de origen, la frase de red, la tasa de transacción y las operaciones a realizar—en este caso, una operación de pago.
-
-Si la transacción tiene éxito, `paymentResult` contiene el resultado, que registras para fines de depuración. Si ocurre un error durante la transacción, la función lanza un error, el cual capturas y registras.
-
-## Conclusión
-
-React ofrece una variedad de conceptos de alto nivel que pueden mejorar drásticamente tu proceso de desarrollo web. Al comprender y utilizar estos conceptos—como componentes, paso de props, gestión de estado, operaciones asincrónicas y manejo de errores—puedes crear aplicaciones escalables, mantenibles y eficientes.
-
-Recuerda, la clave para dominar React es la práctica. ¡Así que sigue construyendo y experimentando!
-
-[dapp de crowdfunding de ejemplo]: https://github.com/stellar/soroban-example-dapp
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/soroban-contract-init-template.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/soroban-contract-init-template.mdx
deleted file mode 100644
index 39d7df8ec0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/soroban-contract-init-template.mdx
+++ /dev/null
@@ -1,295 +0,0 @@
----
-title: Desarrollar contrato con plantillas de frontend
-description: Entender, encontrar y crear tus propias plantillas de interfaz de usuario para usarlas con el comando `stellar contract init` de Stellar CLI
----
-
-<head>
-  <title>Desarrollar contrato con plantillas de frontend</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Desarrollar contrato con plantillas de frontend"
-  />
-  <meta
-    property="og:description"
-    content="Entiende, encuentra y crea tus propias plantillas de frontend para usar con el comando `stellar contract init` de Stellar CLI"
-  />
-</head>
-
-Esta guía continúa donde terminó [Desarrollar un frontend de Dapp](../../apps/dapp-frontend.mdx). A partir de ahí, vamos a:
-
-1. Buscar en GitHub otras plantillas de Soroban
-2. Crear nuestra propia plantilla simple
-
-Crear nuestra propia plantilla será una excelente manera de aprender cómo funcionan. ¡No son tan complicadas!
-
-## Buscar en GitHub otras plantillas de Soroban
-
-La plantilla oficial mantenida por Stellar Development Foundation (SDF), como se usó en [Construir un frontend de Dapp](../../apps/dapp-frontend.mdx), está en GitHub en [stellar/soroban-template-astro](https://github.com/stellar/soroban-astro-template). Usa el marco web [Astro](https://astro.build/). Aunque Astro funciona con React, Vue, Svelte y cualquier otra biblioteca de interfaz de usuario, la plantilla opta por no usarlas, prefiriendo el propio lenguaje de plantillas de Astro, que usa JavaScript puro sin biblioteca de interfaz de usuario.
-
-(Puede que te preguntes por qué toma esta elección poco popular. ¡Una pregunta justa! El equipo quería equilibrar la utilidad real con un enfoque amplio. ¡No todos los que aprenden Stellar y Soroban están familiarizados con React, ni con ninguna otra biblioteca de interfaz de usuario. También demuestra que las bibliotecas centrales de Soroban funcionan con cualquier proyecto de JavaScript.)
-
-Para usar otras plantillas, las clonaremos desde sus repositorios y luego copiaremos estos archivos en la raíz del directorio existente `soroban-hello-world`:
-
-```bash
-# For example, you could clone this repository
-git clone https://github.com/stellar/soroban-examples
-```
-
-Ahora copia los archivos en la raíz de `soroban-hello-world`.
-
-¿Entonces cómo puedes encontrar otras plantillas de interfaz de usuario válidas?
-
-En algún momento podríamos establecer un DAO u otro sistema de votación para curar una lista de plantillas de alta calidad, pero por ahora... ¡busca en GitHub! Y en GitLab. Y en cualquier otro sitio de código fuente que conozcas.
-
-En GitHub, en la barra de búsqueda principal, busca por `"soroban-template-"`. Con las comillas. Aquí tienes un enlace directo a los resultados de búsqueda: [github.com/search?q=%22soroban-template-%22](https://github.com/search?q=%22soroban-template-%22)
-
-Puedes copiar este enfoque para cualquier otro sitio web de código fuente, como GitLab.
-
-¿Cómo sabes si alguno de estos es bueno? Prueba ellos. Mira su código fuente. ¿Cuántas estrellas tienen? ¿Cuán activos son sus mantenedores? Ninguna de estas es una métrica perfecta, que es por qué un registro curado podría ser agradable en el futuro.
-
-Si ninguno de ellos se ajusta, entonces podría ser tiempo de...
-
-## Crear tu propia plantilla
-
-Esto será más fácil de lo que podrías imaginar. Hay algunas complicaciones, pero en general estas plantillas son proyectos de Node bastante estándar.
-
-### Pero primero, ¿cómo están organizados estos proyectos?
-
-Cuando ejecutas `stellar contract init`, _siempre_ incluye un proyecto de Rust/Cargo, con un `Cargo.toml` que define un espacio de trabajo, y miembros del espacio de trabajo ubicados en una carpeta `contracts`. Como mínimo, hay un contrato, `contracts/hello_world`, pero puedes obtener más usando `--name`.
-
-Así que ten eso en mente. Estamos creando un proyecto de Node bastante simple, y contándole sobre nuestro material de Soroban, como la carpeta `contracts`.
-
-### 1. Inicializar un proyecto NPM
-
-Así que, ¡hagamos un proyecto de Node simple! En lugar de inicializar un proyecto Astro, como la plantilla de interfaz de usuario oficial, intentemos algo nuevo. La [Encuesta del Estado de JS](https://2022.stateofjs.com/en-US/libraries/front-end-frameworks/#front_end_frameworks_experience_linechart) me dice que algo llamado "Solid" es bastante nuevo y querido. [¿Qué dice que hay que hacer?](https://www.solidjs.com/)
-
-```bash
-npx degit solidjs/templates/ts soroban-template-solid
-cd soroban-template-solid
-npm install
-npm run dev
-```
-
-¡Ok, tenemos una plantilla de Solid en funcionamiento! ¡Ahora vamos a convertirlo en una plantilla de Soroban!
-
-### 2. git init
-
-¡Haz commit temprano, haz commit a menudo! Puedes detener el servidor de desarrollo (el que comenzaste con `npm run dev` arriba; deténlo con <kbd>ctrl</kbd><kbd>c</kbd>, incluso en un Mac) si quieres, o abre una nueva terminal y:
-
-```bash
-git init
-git add .
-git commit -m "init from solid ts template"
-```
-
-### 3. Copia el script `initialize.js`
-
-La plantilla `soroban-template-astro` mantenida por la SDF tiene [un script `initialize.js`](https://github.com/stellar/soroban-astro-template/blob/main/initialize.js) en su raíz del proyecto. Cópialo en tu proyecto.
-
-Si estás familiarizado con la scripting en Node, deberías poder averiguar lo que está haciendo. Si no, ¡es una gran manera de aprender! Consejo: comienza desde el final, donde hace el `generateAccount(); buildAll(); deployAll();`.
-
-Ese material al final debería darte una pista sobre lo que hace este script. Hace cosas que una aplicación _Soroban_ necesita. Las aplicaciones Soroban hacen llamadas a Soroban.
-
-Así que este script:
-
-1. genera una cuenta Soroban/Stellar
-2. construye todos los contratos
-3. despliega todos los contratos (a una red Soroban que se ejecuta localmente; recapitularé esto pronto)
-4. _binds_ contracts — that is, it creates NPM projects for each deployed contract by running `stellar contract bindings typescript`
-5. importa los contratos para un uso directo en el resto de tu proyecto
-
-Recuerda que necesita hacer todo esto _de manera independiente del contrato_. ¡La plantilla de interfaz de usuario no sabe qué contratos podría encontrar! Pero necesita construir, desplegar, vincular e importar lo que haya.
-
-Así que este script hace eso.
-
-Pero necesita algunas otras cosas.
-
-#### A. `devDependencies`
-
-El script utiliza un par de paquetes NPM. Instálalos:
-
-```bash
-npm install --save-dev dotenv glob
-```
-
-#### B. `.env`
-
-El paquete [`dotenv`](https://www.npmjs.com/package/dotenv) instalado anteriormente analiza variables de entorno desde un archivo `.env`. La plantilla oficial incluye [un `.env.example`](https://github.com/stellar/soroban-astro-template/blob/main/.env.example). Ve y cópialo en tu propio proyecto. Para prepararte para probarlo, también puedes copiarlo a un `.env` local.
-
-```bash
-cp .env.example .env
-```
-
-#### C. `.gitignore`
-
-Querrás ignorar el archivo `.env` que creaste anteriormente, así como algunos otros artefactos de construcción creados por el script `initialize.js`. Pega la parte inferior de [el `.gitignore` de la plantilla oficial](https://github.com/stellar/soroban-astro-template/blob/main/.gitignore) en el `.gitignore` de tu plantilla:
-
-```gitignore
-# environment variables
-.env
-.env.production
-
-# generated contract clients
-packages/*
-# if you have other workspace packages, add them here
-!packages/.gitkeep
-
-# generated contract client imports
-src/contracts/*
-!src/contracts/util.ts
-```
-
-#### C. `package.json`
-
-Asegúrate de que los usuarios de tu plantilla no olviden ejecutar el script `initialize.js`. Modifica la sección `scripts` de la siguiente manera:
-
-```diff
--    "start": "vite",
--    "dev": "vite",
--    "build": "vite build",
--    "serve": "vite preview"
-+    "init": "node initialize.js",
-+    "start": "npm run init && vite",
-+    "dev": "npm run init && vite",
-+    "build": "npm run init && vite build",
-+    "serve": "npm run init && vite preview"
-```
-
-Alternativamente, en lugar de agregar las repetitivas declaraciones `npm run init`, podrías optar por añadir [un script `postinstall`](https://docs.npmjs.com/cli/v7/using-npm/scripts#life-cycle-operation-order) donde ejecutes `npm run init`, o simplemente `node initialize.js` allí.
-
-También necesitas decirle a NPM que trate esto como un espacio de trabajo. ¡Sí, este proyecto es un espacio de trabajo de Cargo _y_ un espacio de trabajo de NPM! El paso `bindAll` de `initialize.js` coloca los paquetes de NPM generados en `packages/*`. En la parte inferior de `package.json`, añade:
-
-```diff
-   "dependencies": {
-     "solid-js": "^1.8.11"
--  }
-+  },
-+  "workspaces": [
-+    "packages/*"
-+  ]
-}
-```
-
-También asegúrate de que este proyecto esté configurado para permitir las declaraciones `import` en el script `initialize.js`. Añade esto a nivel superior:
-
-```diff
-   "description": "",
-+  "type": "module",
-   "scripts": {
-```
-
-Mientras estás aquí, también puedes actualizar el `name` (quizás `"soroban-template-solid"`) y `description`.
-
-#### E. `src/contracts/util.ts`
-
-En el `.gitignore` anterior, es posible que hayas notado que este archivo está explícitamente incluido. Cópialo desde [la plantilla oficial](https://github.com/stellar/soroban-astro-template/blob/main/src/contracts/util.ts). Necesitarás crear la carpeta `src/contracts`.
-
-Como puedes ver, simplemente facilita `import { rpcUrl, networkPassphrase } from 'util'` en los archivos generados en el paso de `importAll`.
-
-#### F. README
-
-Quizás quieras comenzar copiando [el README de la plantilla oficial](https://github.com/stellar/soroban-astro-template/blob/main/README.md) para explicar cómo hacer `cp .env.example .env`. From there, this might also be a good time to explain anything else that makes your template unique! ¿Por qué la gente querría usarla?
-
-### 4. `git commit`
-
-¡Haz commit de los cambios!
-
-```bash
-git add .
-git commit -m "add initialize.js script and supporting changes"
-```
-
-### 5. ¡Prueba esto!
-
-¡Eso es todo! You have an NPM project with an `initialize.js` script (and its supporting cast). ¡Eso es todo lo que realmente necesitas!
-
-Vamos a probarlo. Primero, asegúrate de que estás ejecutando una red Stellar local. Inicia Docker Desktop o cualquier alternativa que prefieras, entonces:
-
-```bash
-stellar network container start local
-```
-
-Vamos a incluir un contrato extra. Ve a [el ejemplo de incremento](https://github.com/stellar/soroban-examples/tree/main/increment) y copia los archivos de incremento en el directorio raíz.
-
-Luego ejecutaremos el script `dev` (recuerda que ejecutará primero el script `initialize.js`).
-
-```bash
-npm run dev
-```
-
-Después de hacer esto, es posible que notes muchos cambios nuevos en el proyecto. ¡Todo ese material de Rust, Cargo y Soroban!
-
-```bash
-$ git status --short
-
-?? .soroban/
-?? Cargo.lock
-?? Cargo.toml
-?? contracts/
-?? target/
-```
-
-Q: Should you commit this stuff?<br />A: **_NO!_**
-
-Q: Should you _gitignore_ this stuff?<br />A: **_NO!_**
-
-Las carpetas `.soroban` y `target` [están ignoradas por git según la plantilla principal de Rust/Cargo](https://github.com/stellar/stellar-cli/tree/main/cmd/soroban-cli/src/utils/contract-template). En los proyectos que especifiquen el tuyo como su `--frontend-template`, ese `.gitignore` se fusionará con el tuyo. No es necesario incluir esas líneas dos veces.
-
-Y los proyectos que utilizan el tuyo querrán hacer commit de los archivos `Cargo.*` y `contracts`, pero tu _plantilla_ no debería incluirlos. Eso puede causar problemas con la inicialización del proyecto más adelante. Nor should it gitignore them, because your `.gitignore` will be part of projects started with your template! ¡Causaría problemas y confusión, si la gente no se diera cuenta de que algunos de sus archivos más importantes estaban gitignoreados!
-
-Está bien. Ve y abre la aplicación en tu navegador. Solid ejecuta su servidor de desarrollo en `http://localhost:3000`. ¿Se carga? ¡Debería! ¡En realidad no utilizamos el nuevo material `src/contracts/*` en la aplicación misma!
-
-### 6. Espera. ¿Debería la plantilla realmente usar los contratos?
-
-¡Buena pregunta!
-
-Sabes que el contrato `hello_world` siempre estará allí. Así que podrías demostrar a tus usuarios cómo importarlo y usarlo en un archivo de aplicación (como `src/App.tsx`, en la plantilla de Solid). Pero recuerda: ¡ningún otro contrato tiene garantizado estar allí! So don't commit any changes that import and use something like `increment`!
-
-Aquí tienes una forma de demostrar cómo importar y usar el contrato `hello_world` en el `App.tsx` de la plantilla de Solid:
-
-```diff
-+import greeter from "./contracts/hello_world";
-
- const App: Component = () => {
-   return (
-     <div class={styles.App}>
-       <header class={styles.header}>
-+        <form
-+          onSubmit={async (e) => {
-+            e.preventDefault();
-+            const { result } = await greeter.hello({
-+              to: e.currentTarget.toWhom.value,
-+            });
-+            alert(result);
-+          }}
-+        >
-+          <label>
-+            Who you gonna call? &amp;nbsp;
-+            <input name="toWhom" value="World" /> &amp;nbsp;
-+          </label>
-+          <button type="submit">Say Hello</button>
-+        </form>
-```
-
-### 7. ¡Hazlo tan complejo como quieras!
-
-Esta es _tu_ plantilla. Ve y añade dependencias útiles y archivos de utilidad que siempre quieras, como gestión de billeteras o lo que sea. Si quieres añadir un montón de componentes de interfaz de usuario, estilos y bibliotecas de gestión de estado, ¡adelante!
-
-La plantilla oficial se esfuerza por la simplicidad. Incluso por superficialidad. Está destinado a ser una herramienta de enseñanza, para personas con diferentes niveles de experiencia en JS y Soroban. ¡La tuya no tiene tales restricciones! Debería ser útil para _ti_.
-
-¡Y las plantillas son baratas de hacer! Si quieres tener una `soroban-template-framework-x-basic` para un público más amplio, y otra `soroban-template-framework-x-opinionated` para tus propios proyectos, ¡puedes hacerlo!
-
-## Conclusión
-
-Algunas cosas que hicimos en esta sección:
-
-- Buscamos en GitHub nuevas plantillas de interfaz de usuario
-- Aprendimos que algunas plantillas podrían no estar en GitHub
-- Vimos cómo funcionan las plantillas de interfaz de usuario e interactúan con la plantilla "backend" que siempre viene con `stellar contract init`
-- Desarrollada nuestra propia plantilla al agregar un script `initialize.js` a una plantilla básica de NPM
-
-Después de que termines de construir tu propia plantilla de frontend, ¿qué sigue? ¡Tú eliges! Puedes:
-
-- Ver más ejemplos de contratos complejos en la sección de [Ejemplos de Contratos](../../smart-contracts/example-contracts/README.mdx).
-- Aprende más sobre la [arquitectura interna y diseño](../../../learn/fundamentals/contract-development/README.mdx) de Soroban.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/state-archival.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/state-archival.mdx
deleted file mode 100644
index e42bfb9dbb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/state-archival.mdx
+++ /dev/null
@@ -1,353 +0,0 @@
----
-title: Implementar archivo de estado en dapps
-description: Aprender cómo implementar archivo de estado en tu dapp
----
-
-Al desarrollar aplicaciones descentralizadas en Stellar, el archivo de estado es parte de lo que necesitamos considerar debido a cómo se almacena la información en la red. Esta guía te ayudará a entender cómo trabajar con el archivo de estado en tu dapp.
-
-Algunos términos de archivo de estado que usaremos en esta guía se describen en la [sección de archivo de estado](../../../learn/fundamentals/contract-development/storage/state-archival.mdx#terms-and-semantics).
-
-## Por qué gestionar el archivo de estado es importante para las aplicaciones
-
-Gestionar el archivo de estado es crucial para las dapps de Stellar por varias razones:
-
-- Accesibilidad de datos: Los datos archivados se vuelven inaccesibles, lo que podría romper la funcionalidad de la aplicación, por lo que es importante gestionar el ciclo de vida de los datos y saber cuándo restaurar.
-- Eficiencia de costos: Diferentes tipos de almacenamiento tienen tarifas y comportamientos de archivo variables, lo que permite a los desarrolladores optimizar costos. Debido a esto, algunos datos pueden ser más rentables de almacenar de una manera que causa que se archiven después de un cierto período.
-- Gestión del ciclo de vida de los datos: Una gestión adecuada asegura que los datos importantes permanezcan accesibles mientras se permite que los datos temporales caduquen.
-- Continuidad de la aplicación: Asegurar que las instancias del contrato y el código Wasm permanezcan en vivo es esencial para un funcionamiento ininterrumpido de la dapp. Es esencial verificar la disponibilidad del contrato antes de intentar interactuar con el contrato después de un largo período de inactividad.
-
-## Métodos para implementar archivo de estado en el lado del cliente
-
-### 1. Extender TTL desde el contrato inteligente
-
-Este método implica invocar el [`extend_ttl()` method](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Instance.html#method.extend_ttl) desde tu contrato inteligente para extender el TTL de la instancia del contrato y sus datos asociados. Este método es útil cuando quieres mantener los datos accesibles por un período más largo. Para usar este método, tu contrato no debe estar archivado en el momento de la llamada.
-
-`extend_ttl()` tiene dos parámetros importantes (T,N):
-
-- T es el umbral, la altura del ledger actual en la que debe ocurrir la extensión.
-- N es la nueva altura del ledger en la que los datos caducarán.
-- El TTL actual debe ser menor que T para que la extensión ocurra.
-- Si N es menor que la altura actual del ledger, el TTL no se extenderá y la llamada se considerará un no-op.
-- Si N es mayor que la altura actual del ledger, el TTL se extenderá a N.
-
-Veamos un ejemplo de cómo podemos implementar esto en un contrato inteligente:
-
-```rust
-#![no_std]
-/// This is a simple contract that just extends TTL for its keys.
-/// It's main purpose is to demonstrate how TTL extension can be tested,
-use soroban_sdk::{contract, contractimpl, contracttype, Env};
-
-#[contracttype]
-pub enum DataKey {
-    MyKey,
-}
-
-#[contract]
-pub struct TtlContract;
-
-#[contractimpl]
-impl TtlContract {
-    /// Creates a contract entry in every kind of storage.
-    pub fn setup(env: Env) {
-        env.storage().persistent().set(&DataKey::MyKey, &0);
-        env.storage().instance().set(&DataKey::MyKey, &1);
-        env.storage().temporary().set(&DataKey::MyKey, &2);
-    }
-
-    /// Extend the persistent entry TTL to 5000 ledgers, when its
-    /// TTL is smaller than 1000 ledgers.
-    pub fn extend_persistent(env: Env) {
-        env.storage()
-            .persistent()
-            .extend_ttl(&DataKey::MyKey, 1000, 5000);
-    }
-
-    /// Extend the instance entry TTL to become at least 10000 ledgers,
-    /// when its TTL is smaller than 2000 ledgers.
-    pub fn extend_instance(env: Env) {
-        env.storage().instance().extend_ttl(2000, 10000);
-    }
-
-    /// Extend the temporary entry TTL to become at least 7000 ledgers,
-    /// when its TTL is smaller than 3000 ledgers.
-    pub fn extend_temporary(env: Env) {
-        env.storage()
-            .temporary()
-            .extend_ttl(&DataKey::MyKey, 3000, 7000);
-    }
-}
-
-mod test;
-```
-
-:::info
-
-El contrato anterior muestra cómo extender el TTL de una entrada de datos `Persistent`, `Instance` y `Temporary`. El método `extend_ttl()` se usa para extender el TTL de la entrada de datos a una nueva altura del ledger.
-
-:::
-
-#### Usando el método Extender TTL en tu contrato
-
-Cuando creamos DApps, no solemos crear botones para extender el TTL de las entradas de datos. En cambio, podemos crear una función que extienda el TTL de las entradas de datos cuando se utiliza la DApp.
-
-Por ejemplo, podemos aumentar el TTL de una entrada de datos temporal llamada `highestBid` en un DApp de subastas cuando se realiza una nueva oferta. Esto asegurará que los datos de la oferta permanezcan accesibles durante el tiempo que se necesiten.
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, contracttype, Env};
-
-#[contracttype]
-pub enum DataKey {
-    HighestBid,
-}
-
-#[contract]
-pub struct BiddingContract;
-
-#[contractimpl]
-impl BiddingContract {
-    /// Creates a contract entry in every kind of storage.
-    pub fn setup(env: Env) {
-        env.storage().temporary().set(&DataKey::HighestBid, &0);
-    }
-
-    /// Place a bid and extend the TTL of the highest bid data entry.
-    pub fn place_bid(env: Env, bid: u64) {
-        let highest_bid: u64 = env.storage().temporary().get(&DataKey::HighestBid).unwrap_or(0);
-        if bid > highest_bid {
-            env.storage().temporary().set(&DataKey::HighestBid, &bid);
-            env.storage().temporary().extend_ttl(&DataKey::HighestBid, 1000, 5000);
-        }
-    }
-}
-```
-
-### 2. Restaurar datos archivados
-
-Al desarrollar un dapp en Stellar, puedes encontrar situaciones donde los datos del contrato o la instancia del contrato han sido archivados debido a inactividad. Vamos a recorrer el proceso de restaurar datos archivados usando el SDK de JavaScript y la billetera Freighter.
-
-#### Requisitos
-
-- Stellar SDK: `npm install @stellar/stellar-sdk`
-- Freighter API: `npm install @stellar/freighter-api`
-- Un punto final RPC de Stellar (por ejemplo, `https://soroban-testnet.stellar.org`)
-
-#### Paso 1: Configurar el SDK y Freighter
-
-Primero, importamos los componentes necesarios:
-
-```javascript
-import * as StellarSdk from "@stellar/stellar-sdk";
-import {
-  isConnected,
-  setAllowed,
-  getAddress,
-  signTransaction,
-} from "@stellar/freighter-api";
-
-import { Api } from "@stellar/stellar-sdk/rpc";
-const rpcUrl = "https://soroban-testnet.stellar.org";
-const server = new StellarSdk.rpc.Server(rpcUrl);
-const networkPassphrase = StellarSdk.Networks.TESTNET; // Use PUBLIC for production
-```
-
-Esta configuración proporciona la base para interactuar con la red Stellar y la billetera Freighter.
-
-#### Paso 2: Crear una función de ayuda para la restauración
-
-Creamos una función de ayuda que intenta enviar una transacción, y si falla debido a datos archivados, restaurará los datos y volverá a intentar:
-
-```javascript
-async function submitOrRestoreAndRetry(contractId, method, ...args) {
-  try {
-    let hasFreighter = await isConnected();
-    if (!hasFreighter) {
-      return alert("Freighter wallet is required for transactions");
-    }
-
-    const isAllowed = await setAllowed();
-    if (!isAllowed) {
-      return alert("Please allow the transaction in Freighter wallet");
-    }
-
-    const accountId = await getAddress();
-    const contract = new StellarSdk.Contract(contractId);
-    const account = await server.getAccount(accountId.address);
-    const fee = StellarSdk.BASE_FEE;
-
-    const transaction = new StellarSdk.TransactionBuilder(account, {
-      fee,
-      networkPassphrase,
-    })
-      .addOperation(contract.call(method, ...args))
-      .setTimeout(30)
-      .build();
-
-    let preparedTransaction = await server.prepareTransaction(transaction);
-
-    let signedXDR = await signTransaction(preparedTransaction.toXDR(), {
-      networkPassphrase,
-    });
-
-    let signedTransaction = StellarSdk.TransactionBuilder.fromXDR(
-      signedXDR.signedTxXdr,
-      networkPassphrase,
-    );
-
-    // Try to send the transaction
-    const sim = await server.simulateTransaction(signedTransaction);
-
-    // Other failures are out of scope of this tutorial.
-    if (!Api.isSimulationSuccess(sim)) {
-      throw sim;
-    }
-
-    // If simulation didn't fail, we don't need to restore anything! Just send it.
-    if (Api.isSimulationRestore(sim)) {
-      console.log("Data archived. Attempting restoration...");
-
-      // Prepare restoration transaction
-      const restoreTx = new StellarSdk.TransactionBuilder(account, { fee })
-        .setNetworkPassphrase(networkPassphrase)
-        .addOperation(StellarSdk.Operation.restoreFootprint({}))
-        .setTimeout(30)
-        .build();
-
-      let preparedRestoreTx = await server.prepareTransaction(restoreTx);
-      let signedRestoreXDR = await signTransaction(preparedRestoreTx.toXDR());
-      let signedRestoreTx = StellarSdk.TransactionBuilder.fromXDR(
-        signedRestoreXDR.signedTxXdr,
-        networkPassphrase,
-      );
-
-      await server.sendTransaction(signedRestoreTx);
-      console.log("Restoration complete. Retrying original transaction...");
-
-      // Retry the original transaction
-      return submitOrRestoreAndRetry(contractId, method, ...args);
-    }
-
-    const result = await server.sendTransaction(signedTransaction);
-
-    return result;
-  } catch (error) {
-    console.error("Transaction failed:", error);
-    throw error;
-  }
-}
-```
-
-Esta función ahora utiliza Freighter para firmar transacciones. Primero verifica si Freighter está conectado y autorizado, luego procede con la transacción. Si se necesita restauración (indicado por un `HostStorageError`), crea una transacción de restauración separada, la firma con Freighter y la envía antes de volver a intentar la transacción original.
-
-#### Paso 3: Usa la función de ayuda en tu dapp
-
-Ahora puedes usar esta función para hacer llamadas al contrato que manejan automáticamente la restauración:
-
-```javascript
-async function performContractAction(contractId, method, ...args) {
-  try {
-    const result = await submitOrRestoreAndRetry(contractId, method, ...args);
-    console.log("Transaction successful:", result);
-    return result;
-  } catch (error) {
-    console.error("Error performing contract action:", error);
-    // Handle the error appropriately in your UI
-  }
-}
-```
-
-#### Paso 4: Manejo de la restauración de la instancia del contrato
-
-Para restaurar una instancia completa del contrato, es posible que necesites una función separada:
-
-Aquí utilizaremos el [`método getLedgerEntries`](../../../data/apis/rpc/api-reference/methods/getLedgerEntries.mdx#2-request-the-contractcode-using-the-retrieved-ledgerkey) para obtener el código WASM del contrato y también la [`operación restoreFootprint`](../../../learn/fundamentals/transactions/list-of-operations.mdx#restore-footprint) para restaurar la instancia del contrato.
-
-```javascript
-async function restoreContractInstance(contractId) {
-  try {
-    let hasFreighter = await isConnected();
-    if (!hasFreighter) {
-      return alert("Freighter wallet is required for transactions");
-    }
-
-    const isAllowed = await setAllowed();
-    if (!isAllowed) {
-      return alert("Please allow the transaction in Freighter wallet");
-    }
-
-    const accountId = await getAddress();
-    const account = await server.getAccount(accountId.address);
-    const fee = StellarSdk.BASE_FEE;
-
-    const contract = new StellarSdk.Contract(contractId);
-    const instance = contract.getFootprint();
-
-    window.ins = instance;
-
-    // Fetch the WASM entry from the ledger
-
-    const wasmEntry = await server.getLedgerEntries(instance);
-
-    const restoreTx = new StellarSdk.TransactionBuilder(account, {
-      fee: StellarSdk.BASE_FEE,
-    })
-      .setNetworkPassphrase(StellarSdk.Networks.TESTNET)
-      .setSorobanData(
-        // Set the restoration footprint (remember, it should be in the
-        // read-write part!)
-        new StellarSdk.SorobanDataBuilder()
-          .setReadWrite([
-            instance,
-            ...wasmEntry.entries.map((entry) => entry.key),
-          ])
-          .build(),
-      )
-      .setTimebounds(0, Date.now() + 10000)
-      .addOperation(StellarSdk.Operation.restoreFootprint({}))
-      .build();
-
-    let preparedTx = await server.prepareTransaction(restoreTx);
-    let signedXDR = await signTransaction(preparedTx.toXDR(), {
-      networkPassphrase: networkPassphrase,
-    });
-    let signedTx = StellarSdk.TransactionBuilder.fromXDR(
-      signedXDR.signedTxXdr,
-      networkPassphrase,
-    );
-
-    return server.sendTransaction(signedTx);
-  } catch (error) {
-    console.error("Error restoring contract instance:", error);
-    throw error;
-  }
-}
-
-// Helper function to get the ledger key for the WASM entry
-function getWasmLedgerKey(entry) {
-  return StellarSdk.xdr.LedgerKey.contractCode(
-    new StellarSdk.xdr.LedgerKeyContractCode({
-      hash: entry.val().instance().wasmHash(),
-    }),
-  );
-}
-```
-
-:::info
-
-Esta función específicamente restaura una instancia del contrato y su código Wasm asociado. Recupera la huella del contrato y la entrada Wasm, crea una transacción de restauración, que luego se firma usando Freighter y se envía a la red.
-
-:::
-
-## Cuándo usar estas funciones
-
-1. El ayudante [`performContractAction`](#step-3-use-the-helper-function-in-your-dapp) puede ser utilizado cuando se intenta invocar una función de contrato inteligente. Puede ayudar a restaurar datos persistentes asociados a la llamada.
-2. El ayudante [`restoreContractInstance`](#step-4-handling-contract-instance-restoration) puede ser utilizado durante la inicialización de la app después de que no se haya utilizado durante mucho tiempo. Usar un indexador para obtener esta información (cuándo se usó la última vez la app) es un gran enfoque.
-
-## Conclusión
-
-Al implementar estas técnicas de archivo de estado y restauración, tu dapp podrá manejar situaciones donde los datos o instancias del contrato han sido archivados, asegurando una experiencia de usuario más fluida incluso después de períodos de inactividad. El uso de billeteras como Freighter para la firma de transacciones proporciona una forma segura y fácil de usar para que los usuarios interactúen con tu dapp.
-
-Recuerda manejar los errores adecuadamente y proporcionar retroalimentación clara a los usuarios durante todo el proceso de restauración. También puedes querer implementar un indicador de carga en tu interfaz de usuario mientras se está llevando a cabo la restauración, ya que puede tardar un momento en completarse.
-
-Comprender y gestionar eficazmente el archivo de estado es crucial para crear dapps robustas y eficientes basadas en Stellar que puedan mantener la funcionalidad y la integridad de los datos a lo largo del tiempo.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/working-with-contract-specs.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/working-with-contract-specs.mdx
deleted file mode 100644
index 1cad72339e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/dapps/working-with-contract-specs.mdx
+++ /dev/null
@@ -1,1338 +0,0 @@
----
-title: Trabajar con especificaciones de contrato en Java, Python y PHP
-description: Una guía para entender e interactuar con los contratos inteligentes de Soroban en diferentes lenguajes de programación
----
-
-## Introducción
-
-Los contratos inteligentes de Soroban son herramientas poderosas para construir aplicaciones descentralizadas en la red Stellar. Para interactuar con estos contratos de manera efectiva, es crucial entender sus especificaciones y cómo utilizarlas en tu lenguaje de programación de elección.
-
-Una especificación de contrato típica (espec) incluye:
-
-1. Tipos de datos utilizados por el contrato
-2. Definiciones de función con sus entradas y salidas
-3. Tipos de error que el contrato puede devolver
-
-Estos detalles guían cómo interactúas con el contrato, independientemente del lenguaje de programación que estés utilizando.
-
-## Requisitos previos
-
-Antes de sumergirte en las interacciones con el contrato, asegúrate de tener lo siguiente:
-
-- CLI de Stellar ([`stellar`](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli)) instalado
-- Un SDK compatible con Soroban para tu lenguaje de programación. Consulta la [lista de SDKs disponibles](../../../tools/sdks/README.mdx) para encontrar uno que se adapte a tus necesidades
-- Acceso a un [servidor RPC](../../..//README.mdx) de Stellar (local o en una Test Net)
-
-Para esta guía, nos centraremos en los SDK de [Java](../../../tools/sdks/client-sdks.mdx#java-sdk), [Python](../../../tools/sdks/client-sdks.mdx#python-sdk) y [PHP](../../../tools/sdks/client-sdks.mdx#php-sdk) como referencia, pero los conceptos también se pueden aplicar a otros lenguajes.
-
-## ¿Qué son las especificaciones de contrato?
-
-Una especificación de contrato es como un ABI (Interfaz Binaria de Aplicación) en Ethereum. Es una descripción estandarizada de la interfaz de un contrato inteligente, típicamente en formato JSON o formato XDR. Define las funciones del contrato, estructuras de datos, eventos y errores de una manera que las aplicaciones externas pueden entender y usar.
-
-Esta especificación actúa como un puente crucial entre el contrato inteligente y las aplicaciones cliente, permitiendo que interactúen sin necesidad de conocer los detalles internos de implementación del contrato.
-
-# Especificación del contrato de Stellar
-
-Cuando compilas un contrato inteligente utilizando el SDK de Rust, el archivo Wasm resultante incluye una sección especial que contiene una descripción completa de los tipos de interfaz de tu contrato. Esto se conoce a menudo como la `especificación` o `especificación del contrato`. La especificación del contrato de Stellar, conocida como `especificación del contrato`, es un elemento fundamental para interactuar con los contratos y para construir dApps en la red Stellar. La especificación del contrato proporciona definiciones robustas y completamente tipadas para interactuar con contratos inteligentes, ofreciendo una funcionalidad equivalente al ABI de Ethereum, mientras aborda sus limitaciones.
-
-La especificación del contrato sirve como una interfaz estandarizada para interactuar con contratos inteligentes de Stellar. Similar a los ABI de Ethereum, pero con ventajas clave:
-
-- Disponibilidad on-chain: Cada especificación de contrato se almacena on-chain
-- Comentarios de desarrollador: Se preservan los comentarios del autor del contrato
-- Comunicación fluida entre contratos y aplicaciones externas
-- Compatibilidad en todo el ecosistema con herramientas como billeteras, exploradores y SDKs
-
-Esta estandarización simplifica las integraciones y acelera el proceso de desarrollo.
-
-## Definiciones de contrato completamente tipadas
-
-La especificación del contrato establece definiciones completamente tipadas para todas las funciones, entradas y salidas del contrato. Esto asegura que:
-
-- Los desarrolladores pueden definir el comportamiento del contrato de manera explícita, reduciendo la ambigüedad.
-- Las discrepancias de tipo y los errores de ejecución se minimizan, lo que conduce a contratos inteligentes más confiables.
-- Las herramientas pueden proporcionar sugerencias inteligentes y validaciones durante el desarrollo.
-
-Al incorporar la seguridad de tipo a nivel de protocolo, la especificación de contratos de Stellar crea un entorno de desarrollo más predecible y robusto.
-
-## Comparativa con el ABI de Ethereum
-
-La especificación de contratos de Stellar comparte muchas similitudes con el ABI de Ethereum, pero también introduce mejoras:
-
-| Característica                    | ABI de Ethereum       | Especificación del contrato de Stellar       |
-| --------------------------------- | --------------------- | -------------------------------------------- |
-| Contratos completamente tipados   | Parcial               | Sí                                           |
-| Decodificación y validación       | Manual o externo      | Incorporado                                  |
-| Enfoque en la seguridad           | Moderado              | Alto (seguridad de tipo impuesta)            |
-
-## Generación de especificaciones de contrato
-
-[El CLI de Stellar](https://github.com/stellar/stellar-cli) proporciona un comando para generar una especificación de contrato a partir del código fuente de un contrato. Este proceso es fácil pero requiere que tengas el binario Wasm del contrato.
-
-A veces, es posible que no tengas acceso al código fuente del contrato o la capacidad de compilarlo. En tales casos, debes usar el comando [`stellar contract fetch`](../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch) para descargar el binario Wasm del contrato y generar la especificación.
-
-Finalmente, usamos el comando [`stellar bindings`](../../../tools/cli/stellar-cli.mdx#stellar-contract-bindings-json) para generar la especificación del contrato a partir del binario Wasm.
-
-El Laboratorio Stellar tiene un [Explorador de Contratos](https://lab.stellar.org/smart-contracts/contract-explorer) que también ofrece la capacidad de ver y descargar la especificación de un contrato.
-
-### Obteniendo el binario del contrato
-
-```bash
-stellar contract fetch --network-passphrase 'Test SDF Network ; September 2015' --rpc-url https://soroban-testnet.stellar.org --id CONTRACT_ID --out-file contract.wasm
-```
-
-### Generando la especificación del contrato a partir de Wasm
-
-```bash
-stellar contract bindings json --wasm contract.wasm > abi.json
-```
-
-## Entendiendo la especificación del contrato
-
-La especificación ABI (Interfaz Binaria de Aplicación) para contratos inteligentes Stellar incluye varios componentes clave que definen cómo interactuar con el contrato. Examinemos estos en detalle con ejemplos:
-
-1. **Funciones:** Las funciones se definen con su nombre, entradas y salidas. Representan los métodos llamables del contrato. Pueden usarse para escribir datos en el contrato y leer datos del contrato.
-
-   Ejemplo:
-
-   ```json
-   {
-     "type": "function",
-     "name": "mint",
-     "inputs": [
-       {
-         "name": "contract",
-         "value": { "type": "address" }
-       },
-       {
-         "name": "minter",
-         "value": { "type": "address" }
-       },
-       {
-         "name": "to",
-         "value": { "type": "address" }
-       },
-       {
-         "name": "amount",
-         "value": { "type": "i128" }
-       }
-     ],
-     "outputs": [
-       {
-         "type": "result",
-         "value": { "type": "tuple", "elements": [] },
-         "error": { "type": "error" }
-       }
-     ]
-   }
-   ```
-
-   Esto define una función `mint` que toma cuatro parámetros y devuelve ya sea una tupla vacía o un error. Fíjate en el tipo de cada parámetro: `address` para las direcciones de cuentas Stellar, `i128` para enteros de 128 bits, etc.
-
-2. **Estructuras:** Las estructuras definen tipos de datos complejos con múltiples campos.
-
-   Ejemplo:
-
-   ```json
-   {
-     "type": "struct",
-     "name": "ClaimableBalance",
-     "fields": [
-       {
-         "name": "amount",
-         "value": { "type": "i128" }
-       },
-       {
-         "name": "claimants",
-         "value": {
-           "type": "vec",
-           "element": { "type": "address" }
-         }
-       },
-       {
-         "name": "time_bound",
-         "value": {
-           "type": "custom",
-           "name": "TimeBound"
-         }
-       },
-       {
-         "name": "token",
-         "value": { "type": "address" }
-       }
-     ]
-   }
-   ```
-
-   Esto define una estructura `ClaimableBalance` con cuatro campos.
-
-3. **Uniones:** Las uniones representan variables que pueden ser de varios tipos.
-
-   Ejemplo:
-
-   ```json
-   {
-     "type": "union",
-     "name": "DataKey",
-     "cases": [
-       {
-         "name": "Init",
-         "values": []
-       },
-       {
-         "name": "Balance",
-         "values": []
-       }
-     ]
-   }
-   ```
-
-   Esto define una unión `DataKey` que puede ser `Init` o `Balance`.
-
-4. **Tipos personalizados:** Los tipos personalizados se refieren a otros tipos definidos en la ABI.
-
-   Ejemplo:
-
-   ```json
-   {
-     "name": "time_bound",
-     "value": {
-       "type": "custom",
-       "name": "TimeBound"
-     }
-   }
-   ```
-
-   Esto se refiere a un tipo `TimeBound` personalizado definido en otro lugar de la ABI.
-
-5. **Tipos de vector:** Los vectores representan matrices de un tipo específico.
-
-   Ejemplo:
-
-   ```json
-   {
-     "name": "claimants",
-     "value": {
-       "type": "vec",
-       "element": { "type": "address" }
-     }
-   }
-   ```
-
-   Esto define un vector de direcciones.
-
-6. **Tipos primitivos:** Estos incluyen tipos básicos como `i128` (entero de 128 bits), `u64` (entero sin signo de 64 bits), `address`, etc.
-
-   Ejemplo:
-
-   ```json
-   {
-     "name": "amount",
-     "value": { "type": "i128" }
-   }
-   ```
-
-Estas especificaciones son cruciales para codificar y decodificar datos al interactuar con el contrato. Por ejemplo:
-
-- Al llamar a la función `mint`, debes proporcionar cuatro parámetros: tres direcciones y un entero de 128 bits.
-- Si una función devuelve un `ClaimableBalance`, esperarías recibir una estructura con una cantidad (i128), un vector de direcciones (claimants), un objeto TimeBound, y una dirección (token).
-- Si una función podría devolver un `Error`, lo más probable es que falle en la simulación y no necesitarás decodificar el resultado.
-
-## Tipos en Soroban
-
-Antes de profundizar en la interacción con los contratos inteligentes de Stellar, es importante destacar que Soroban tiene su propio conjunto de tipos que se utilizan para interactuar con los contratos como se describe en [esta guía](../../../learn/fundamentals/contract-development/types/built-in-types.mdx). Aquí hay algunos de los tipos comunes:
-
-- `u32`: Entero sin signo de 32 bits
-- `u64`: Entero sin signo de 64 bits
-- `i32`: Entero con signo de 32 bits
-- `i64`: Entero con signo de 64 bits
-- `u128`: Entero sin signo de 128 bits
-- `i128`: Entero con signo de 128 bits
-- `bool`: Booleano
-- `string`: Cadena codificada en UTF-8
-- `vec`: Arreglo de longitud variable
-- `address`: Dirección de cuenta Stellar
-- `map`: Mapa clave-valor
-- `symbol`: Una cadena pequeña utilizada principalmente para nombres de función y claves de mapa
-
-En esta guía y los SDKs, estos tipos se representan como `ScU32`, `ScU64`, `ScI32`, `ScI64`, `ScU128`, `ScI128`, `ScBool`, `ScString`, `ScVec`, `ScAddress`, `ScMap`, y `ScSymbol` respectivamente.
-
-Cada otro tipo complejo puede derivarse utilizando estos tipos básicos, pero estos tipos no se traducen realmente a valores en los lenguajes de programación. Los SDKs de Stellar proporcionan clases de ayuda para trabajar con estos tipos.
-
-## Trabajando con tipos nativos de Soroban
-
-Una de las tareas más comunes al trabajar con contratos inteligentes de Stellar es convertir entre tipos de contrato inteligente de Stellar y tipos nativos en tu lenguaje de programación. En esta guía, revisaremos algunas conversiones comunes y mostraremos cómo pueden usarse para invocar contratos con la ayuda de la especificación del contrato.
-
-En la mayoría de los SDKs, se usa la clase o función `ScVal` para convertir entre tipos Soroban y tipos nativos.
-
-:::note
-
-El bloque de código JSON muestra la especificación del contrato, mientras que los bloques de código en Rust muestran el contrato para cada ejemplo.
-
-:::
-
-### 1. Invocar una función de contrato sin parámetros
-
-Usaremos la función `increment` del [contrato de incremento](https://github.com/stellar/soroban-examples/tree/main/increment) de ejemplo para ejemplificar esto. La función `increment` no toma parámetros y aumenta el contador en 1.
-
-En este escenario, no es necesario realizar conversiones y pasar el valor `null` como argumentos del contrato es suficiente en la mayoría de los SDKs.
-
-<CodeExample>
-
-```rust
-#[contractimpl]
-impl IncrementContract {
-    /// Increment increments an internal counter, and returns the value.
-    pub fn increment(env: Env) -> u32 {
-        // Get the current count.
-        let mut count: u32 = env.storage().instance().get(&COUNTER).unwrap_or(0); // If no value set, assume 0.
-        log!(&env, "count: {}", count);
-        // Increment the count.
-        count += 1;
-
-        // Save the count.
-        env.storage().instance().set(&COUNTER, &count);
-        env.storage().instance().extend_ttl(50, 100);
-
-        // Return the count to the caller.
-        count
-    }
-}
-```
-
-```json
-[
-  {
-    "type": "function",
-    "doc": "Increment increments an internal counter, and returns the value.",
-    "name": "increment",
-    "inputs": [],
-    "outputs": [
-      {
-        "type": "u32"
-      }
-    ]
-  }
-]
-```
-
-```python
-# pip install --upgrade stellar-sdk
-from stellar_sdk import SorobanServer, soroban_rpc, Account, Asset, Keypair, Network, TransactionBuilder
-
-def send_transaction() -> soroban_rpc.SendTransactionResponse:
-    server = SorobanServer(server_url='https://soroban-testnet.stellar.org', client=None)
-
-    root_keypair = Keypair.from_secret(
-        "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
-    )
-    root_account = Account(account=root_keypair.public_key, sequence=1)
-    contract_id = "CA3D5KRYM6CB7OWQ6TWYRR3Z4T7GNZLKERYNZGGA5SOAOPIFY6YQGAXE"
-    transaction = (
-        TransactionBuilder(
-            source_account=root_account,
-            network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-            base_fee=100,
-        )
-        .append_invoke_contract_function_op(
-            contract_id=contract_id,
-            function_name="increment",
-            parameters=[],
-            source=root_keypair.public_key,
-        )
-        # mark this transaction as valid only for the next 30 seconds
-        .set_timeout(30)
-        .build()
-    )
-    transaction.sign(root_keypair)
-    response = server.send_transaction(transaction)
-    return response
-
-response = send_transaction()
-
-print("status", response.status)
-print("hash:", response.hash)
-print("status:", response.status)
-print("errorResultXdr:", response.error_result_xdr)
-```
-
-```java
-// implementation 'network.lightsail:stellar-sdk:2.1.0'
-import org.stellar.sdk.KeyPair;
-import org.stellar.sdk.Network;
-import org.stellar.sdk.SorobanServer;
-import org.stellar.sdk.Transaction;
-import org.stellar.sdk.TransactionBuilder;
-import org.stellar.sdk.TransactionBuilderAccount;
-import org.stellar.sdk.xdr.InvokeHostFunctionOp;
-import org.stellar.sdk.operations.InvokeHostFunctionOperation;
-import org.stellar.sdk.exception.PrepareTransactionException;
-import org.stellar.sdk.exception.NetworkException;
-import org.stellar.sdk.responses.sorobanrpc.SendTransactionResponse;
-
-public class SendTransactionExample {
-
-    public static void main(String[] args) {
-        SorobanServer server = new SorobanServer("https://soroban-testnet.stellar.org");
-        try {
-            // Replace with your source account's public key
-            String sourcePublicKey = "GBSBL6FBPX5UHKL4AZCPUU6PXKUBYMKRUN3L4YQ4V2CCWSE7YMN2HYPB";
-
-            // Replace with your source account's secret key
-            String sourceSecretSeed = "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
-            KeyPair sourceKeyPair = KeyPair.fromSecretSeed(sourceSecretSeed);
-
-            // Decode the source account's public key to TransactionBuilderAccount
-            TransactionBuilderAccount account = server.getAccount(sourceKeyPair.getAccountId());
-
-            // Define the contract ID and function to invoke
-            String contractId = "CA3D5KRYM6CB7OWQ6TWYRR3Z4T7GNZLKERYNZGGA5SOAOPIFY6YQGAXE";
-            String functionName = "increment";
-
-            InvokeHostFunctionOperation operation =
-                InvokeHostFunctionOperation.invokeContractFunctionOperationBuilder(
-                  contractId,
-                  functionName,
-                  null
-                )
-                .build();
-
-            Transaction unpreparedTransaction =
-                new TransactionBuilder(account, Network.TESTNET)
-                  .setBaseFee(Transaction.MIN_BASE_FEE)
-                  .addOperation(operation)
-                  .setTimeout(300)
-                  .build();
-
-            Transaction transaction;
-            try {
-                transaction = server.prepareTransaction(unpreparedTransaction);
-            } catch (PrepareTransactionException e) {
-                throw new RuntimeException("Prepare transaction failed", e);
-            } catch (NetworkException e) {
-                throw new RuntimeException("Network error", e);
-            }
-
-            // Sign the transaction
-            transaction.sign(sourceKeyPair);
-
-            // Send the transaction using the SorobanServer
-            SendTransactionResponse response = server.sendTransaction(transaction);
-
-            System.out.println("Status: " + response.getStatus());
-            System.out.println("Transaction Hash: " + response.getHash());
-            System.out.println("Latest Ledger: " + response.getLatestLedger());
-            System.out.println("Ledger Close Time: " + response.getLatestLedgerCloseTime());
-        } catch (Exception e) {
-            System.err.println("An error has occurred:");
-            e.printStackTrace();
-        }
-    }
-}
-
-```
-
-```php
-<?php
-
-namespace App\Models;
-
-use Soneso\StellarSDK\TransactionBuilder;
-use Soneso\StellarSDK\Soroban\SorobanServer;
-use Soneso\StellarSDK\SEP\Derivation\Mnemonic;
-use Soneso\StellarSDK\Crypto\KeyPair;
-use Soneso\StellarSDK\Network;
-use Soneso\StellarSDK\InvokeContractHostFunction;
-use Soneso\StellarSDK\InvokeHostFunctionOperationBuilder;
-use Soneso\StellarSDK\Soroban\Requests\SimulateTransactionRequest;
-
-class Invoker
-{
-    public function invoker2()
-    {
-        $server = new SorobanServer("https://soroban-testnet.stellar.org");
-        $accountASeed = "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
-        $accountAKeyPair = Keypair::fromSeed($accountASeed);
-        $accountAId = "GBWIPGMM27M7O43NIHS6MXMVBDDI6WUYXWCJX7FL7DBA6B4ITXBC6JPN";
-        $accountA = $server->getAccount($accountAId);
-        $network = Network::testnet();
-        $contractId = "CAMN24E6KNIXQBYPJJ4K7XRCUUJUMYSJRCSLZ2WOO6WJTSKIXAZWNYHK";
-
-        $invokeContractHostFunction = new InvokeContractHostFunction($contractId, "increment", null);
-        $builder = new InvokeHostFunctionOperationBuilder($invokeContractHostFunction);
-        $op = $builder->build();
-
-        $transaction = (new TransactionBuilder($accountA))
-            ->addOperation($op)->build();
-
-        $request = new SimulateTransactionRequest($transaction);
-        $simulateResponse = $server->simulateTransaction($request);
-
-        $transaction->setSorobanTransactionData($simulateResponse->getTransactionData());
-        $transaction->addResourceFee($simulateResponse->minResourceFee);
-        $transaction->sign($accountAKeyPair, $network);
-
-        $server->sendTransaction($transaction);
-    }
-}
-```
-
-</CodeExample>
-
-:::info
-
-Los ejemplos subsiguientes mostrarán bloques de código solo para usar la especificación del contrato para reducir la redundancia.
-
-:::
-
-### 2. Invocar una función de contrato con uno o más parámetros
-
-Generalmente, esto implica pasar un array nativo (no un ScVec) de parámetros a la función del contrato.
-
-Usaremos la función `hello` del [contrato Hello World](https://github.com/stellar/soroban-examples/tree/main/hello_world) de ejemplo para ejemplificar esto.
-
-En este escenario, necesitamos convertir el parámetro de cadena a un tipo `ScString` antes de pasarlo al contrato. En este escenario, necesitamos convertir el parámetro de cadena a un tipo `ScString` antes de pasarlo al contrato.
-
-Este proceso es conveniente utilizando la clase o función `ScVal` en la mayoría de los SDKs.
-
-<CodeExample>
-
-```rust
-#[contract]
-pub struct HelloContract;
-
-#[contractimpl]
-impl HelloContract {
-    pub fn hello(env: Env, to: String) -> Vec<String> {
-        vec![&env, String::from_str(&env, "Hello"), to]
-    }
-}
-```
-
-```json
-[
-  {
-    "type": "function",
-    "doc": "",
-    "name": "hello",
-    "inputs": [
-      {
-        "doc": "",
-        "name": "to",
-        "value": {
-          "type": "string"
-        }
-      }
-    ],
-    "outputs": [
-      {
-        "type": "vec",
-        "element": {
-          "type": "string"
-        }
-      }
-    ]
-  }
-]
-```
-
-```python
-from stellar_sdk import Keypair, Network, SorobanServer, TransactionBuilder, scval
-.....
-tx = (
-  TransactionBuilder(source, network_passphrase, base_fee=100)
-  .set_timeout(300)
-  .append_invoke_contract_function_op(
-      contract_id=contract_id,
-      function_name="hello",
-      parameters=[
-          scval.to_string("John"),
-      ]
-).build())
-```
-
-```java
-import org.stellar.sdk.scval.Scv;
-import org.stellar.sdk.xdr.SCVal;
-// .....
-List<SCVal> contractArgs = new ArrayList<SCVal>();
-contractArgs.add(Scv.toString("John"));
-InvokeHostFunctionOperation operation = InvokeHostFunctionOperation
-                .invokeContractFunctionOperationBuilder(contractId, "hello", contractArgs).build();
-TransactionBuilder transaction = new TransactionBuilder(source, Network.TESTNET);
-Transaction tx = transaction.addOperation(operation).build();
-```
-
-```php
-$arg = \Soneso\StellarSDK\Xdr\XdrSCVal::forString("John");
-$invokeContractHostFunction = new InvokeContractHostFunction($contractId, "hello", [$arg]);
-$builder = new InvokeHostFunctionOperationBuilder($invokeContractHostFunction);
-$op = $builder->build();
-
-$transaction = (new TransactionBuilder($accountA))
-    ->addOperation($op)->build();
-```
-
-</CodeExample>
-
-### 3. Obteniendo respuestas de los contratos
-
-Los datos devueltos de los contratos también están en formato `ScVal` y necesitan ser convertidos a tipos nativos en tu lenguaje de programación.
-
-Todavía usaremos la función `hello` del [contrato Hello World](https://github.com/stellar/soroban-examples/tree/main/hello_world) de ejemplo para ejemplificar esto.
-
-En este escenario, necesitamos convertir el valor devuelto de un `ScVec` de tipo `ScString` a un `array` de `string` antes de hacer uso de él. En este escenario, necesitamos convertir el valor devuelto de un `ScVec` de tipo `ScString` a un `array` de `string` antes de hacer uso de él.
-
-Pasos:
-
-- Extraer un `ScVec` del valor de retorno
-- Extraer cada `ScString` del `ScVec`
-- Convertir cada `ScString` a una cadena nativa
-
-Este proceso es conveniente usando la clase o función `ScVal` en la mayoría de los SDKs.
-
-Preferiblemente, para recuperar este valor, necesitamos usar el método RPC [`getTransaction`](../../../data/apis/rpc/api-reference/methods/getTransaction.mdx) utilizando el hash de respuesta de la transacción que invocó la función del contrato.
-
-<CodeExample>
-
-```rust
-#[contract]
-pub struct HelloContract;
-
-#[contractimpl]
-impl HelloContract {
-    pub fn hello(env: Env, to: String) -> Vec<String> {
-        vec![&env, String::from_str(&env, "Hello"), to]
-    }
-}
-```
-
-```json
-[
-  {
-    "type": "function",
-    "doc": "",
-    "name": "hello",
-    "inputs": [
-      {
-        "doc": "",
-        "name": "to",
-        "value": {
-          "type": "string"
-        }
-      }
-    ],
-    "outputs": [
-      {
-        "type": "vec",
-        "element": {
-          "type": "string"
-        }
-      }
-    ]
-  }
-]
-```
-
-```python
-from stellar_sdk import SorobanServer, soroban_rpc
-from stellar_sdk import xdr as stellar_xdr
-from stellar_sdk.soroban_rpc import GetTransactionStatus
-
-def get_transaction(hash: str) -> soroban_rpc.GetTransactionResponse:
-    server = SorobanServer(server_url='https://soroban-testnet.stellar.org', client=None)
-    tx = server.get_transaction(hash)
-    return tx
-
-get_transaction_data = get_transaction("7e47c6ba2ebe53e156bc50c48e34302d49c91c04c465e8cd2b8a25219c2c8121")
-
-if get_transaction_data.status == GetTransactionStatus.SUCCESS:
-    transaction_meta = stellar_xdr.TransactionMeta.from_xdr(
-        get_transaction_data.result_meta_xdr
-    )
-    result = transaction_meta.v4.soroban_meta.return_value
-    output = []
-    for x in result.vec.sc_vec:
-        decoded_string = x.str.sc_string.decode()
-        output.append(decoded_string)
-    print(f"transaction result: {output}")
-else:
-    print(f"Transaction failed: {get_transaction_data.result_xdr}")
-```
-
-```java
-import org.stellar.sdk.responses.sorobanrpc.GetTransactionResponse;
-import org.stellar.sdk.xdr.SCVal;
-import org.stellar.sdk.xdr.TransactionMeta;
-import org.stellar.sdk.SorobanServer;
-import java.util.ArrayList;
-import java.util.List;
-
-public static void main(String[] args) {
-  SorobanServer server = new SorobanServer("https://soroban-testnet.stellar.org");
-  try {
-    GetTransactionResponse tx = server
-        .getTransaction("7e47c6ba2ebe53e156bc50c48e34302d49c91c04c465e8cd2b8a25219c2c8121");
-
-    if (tx.getStatus() == GetTransactionResponse.GetTransactionStatus.SUCCESS) {
-      List<String> output = new ArrayList<String>();
-      String base64Xdr = tx.getResultMetaXdr();
-
-      // convert the string to a result
-      SCVal[] result = TransactionMeta.fromXdrBase64(base64Xdr).getV4()
-          .getSorobanMeta().getReturnValue().getVec()
-          .getSCVec();
-      for (SCVal x : result) {
-        output.add(x.getStr().getSCString().toString());
-      }
-
-      System.out.println("transaction result: " + output.toString());
-    } else {
-      System.out.println("Transaction failed: " + tx.getStatus());
-    }
-  } catch (Exception e) {
-    System.err.println("An error has occurred:");
-    e.printStackTrace();
-  }
-}
-```
-
-```php
-<?php
-use Soneso\StellarSDK\Soroban\Responses\GetTransactionResponse;
-use Soneso\StellarSDK\Soroban\SorobanServer;
-
-class Test {
- public function getTx()
-    {
-        $txhash = "7e47c6ba2ebe53e156bc50c48e34302d49c91c04c465e8cd2b8a25219c2c8121";
-        $server = new SorobanServer("https://soroban-testnet.stellar.org");
-        $statusResponse = $server->getTransaction($txhash);
-        $status = $statusResponse->status;
-        $resultArr = [];
-
-        if ($status == GetTransactionResponse::STATUS_FAILED) {
-            print ("Transaction failed: " . $statusResponse->error . PHP_EOL);
-        } else if ($status == GetTransactionResponse::STATUS_SUCCESS) {
-            $resultValue = $statusResponse->getResultValue();
-            $resVec = $resultValue->vec;
-            foreach ($resVec as $strVal) {
-                $resultArr[] = $strVal->str;
-            }
-            print_r($resultArr);
-        }
-        return $resultArr;
-    }
-}
-```
-
-</CodeExample>
-
-## Trabajando con tipos de datos complejos
-
-Como se describe en [esta guía](../../../learn/fundamentals/contract-development/types/custom-types.mdx), Soroban admite algunas otras variantes de estructura de datos. Ellas son
-
-- `Struct` con campos nombrados
-- `Struct` con campos no nombrados
-- `Enum` (variantes unitarias y de tupla)
-- `Enum` (variantes enteras)
-
-Veremos cómo estas variantes se traducen a la especificación y cómo construirlas en los diferentes SDKs.
-
-### Struct con campos nombrados
-
-Las estructuras con valores nombrados cuando se convierten a ABI o especificación se representan como un `ScMap` donde cada valor tiene la clave en `ScSymbol` y el valor en el tipo subyacente.
-
-<CodeExample>
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub struct State {
-    pub count: u32,
-    pub last_incr: u32,
-}
-```
-
-```json
-[
-  {
-    "type": "struct",
-    "doc": "",
-    "name": "State",
-    "fields": [
-      {
-        "doc": "",
-        "name": "count",
-        "value": {
-          "type": "u32"
-        }
-      },
-      {
-        "doc": "",
-        "name": "last_incr",
-        "value": {
-          "type": "u32"
-        }
-      }
-    ]
-  }
-]
-```
-
-```python
-from stellar_sdk import scval
-scval.to_map(
-    {
-        scval.to_symbol("count"): scval.to_u32(0),
-        scval.to_symbol("last_incr"): scval.to_u32(0),
-    }
-)
-```
-
-```java
-import org.stellar.sdk.xdr.SCVal;
-import org.stellar.sdk.scval.Scv;
-import java.util.LinkedHashMap;
-
-LinkedHashMap<SCVal, SCVal> map = new LinkedHashMap<SCVal, SCVal>();
-map.put(Scv.toSymbol("count"), Scv.toUint32(0));
-map.put(Scv.toSymbol("last_incr"), Scv.toUint32(0));
-SCVal val = Scv.toMap(map);
-```
-
-```php
-<?php
-use Soneso\StellarSDK\Xdr\XdrSCVal;
-
-XdrSCVal::forMap(
-    [
-        XdrSCVal::forSymbol("count") => XdrSCVal::forU32(0),
-        XdrSCVal::forSymbol("last_incr") => XdrSCVal::forU32(0),
-    ]
-);
-```
-
-</CodeExample>
-
-### Struct con campos no nombrados
-
-Las estructuras con valores no nombrados cuando se convierten a ABI o especificación se representan como un `ScVal` donde cada valor tiene el tipo subyacente.
-
-<CodeExample>
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub struct State(pub u32, pub u32);
-```
-
-```json
-[
-  {
-    "type": "struct",
-    "doc": "",
-    "name": "State",
-    "fields": [
-      {
-        "doc": "",
-        "value": {
-          "type": "u32"
-        }
-      },
-      {
-        "doc": "",
-        "value": {
-          "type": "u32"
-        }
-      }
-    ]
-  }
-]
-```
-
-```python
-from stellar_sdk import scval
-scval.to_vec(
-    [
-        scval.to_uint32(0),
-        scval.to_uint32(0),
-    ]
-)
-```
-
-```java
-import org.stellar.sdk.xdr.SCVal;
-import org.stellar.sdk.scval.Scv;
-import java.util.LinkedHashMap;
-
-List<SCVal> vec = new ArrayList<SCVal>();
-vec.add(Scv.toUint32(0));
-vec.add(Scv.toUint32(0));
-SCVal val = Scv.toVec(vec);
-```
-
-```php
-<?php
-use Soneso\StellarSDK\Xdr\XdrSCVal;
-
-XdrSCVal::forVec(
-    [
-        XdrSCVal::forU32(0),
-        XdrSCVal::forU32(0),
-    ]
-);
-```
-
-</CodeExample>
-
-### Enum (variantes unitarias y de tupla)
-
-Los enums generalmente se representan con `ScVec`, sus tipos unitarios se representan como `ScSymbol` y sus variantes de tupla se representan como los tipos subyacentes.
-
-<CodeExample>
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub enum Enum {
-    A,
-    B(u32),
-}
-```
-
-```json
-[
-  {
-    "type": "union",
-    "doc": "",
-    "name": "Enum",
-    "cases": [
-      {
-        "doc": "",
-        "name": "A",
-        "values": []
-      },
-      {
-        "doc": "",
-        "name": "B",
-        "values": [
-          {
-            "type": "u32"
-          }
-        ]
-      }
-    ]
-  }
-]
-```
-
-```python
-from stellar_sdk import scval
-scval.to_vec(
-    [
-        scval.to_symbol("A"),
-        scval.to_map(
-            {
-                scval.to_symbol("B"): scval.to_uint32(0),
-            }
-        ),
-    ]
-)
-```
-
-```java
-import org.stellar.sdk.xdr.SCVal;
-import org.stellar.sdk.scval.Scv;
-import java.util.LinkedHashMap;
-
-List<SCVal> vec = new ArrayList<SCVal>();
-vec.add(Scv.toSymbol("A"));
-LinkedHashMap<SCVal, SCVal> map = new LinkedHashMap<SCVal, SCVal>();
-map.put(Scv.toSymbol("B"), Scv.toUint32(0));
-vec.add(Scv.toMap(map));
-SCVal val = Scv.toVec(vec);
-```
-
-```php
-<?php
-use Soneso\StellarSDK\Xdr\XdrSCVal;
-
-XdrSCVal::forVec(
-    [
-        XdrSCVal::forSymbol("A"),
-        XdrSCVal::forMap(
-            [
-                XdrSCVal::forSymbol("B") => XdrSCVal::forU32(0),
-            ]
-        ),
-    ]
-);
-```
-
-</CodeExample>
-
-### Enum (variantes enteras)
-
-Los enums generalmente se representan con `ScVec`, la variante entera no tiene claves, así que es solo un `ScVec` del tipo subyacente.
-
-<CodeExample>
-
-```rust
-#[contracttype]
-#[derive(Copy, Clone, Debug, Eq, PartialEq)]
-#[repr(u32)]
-pub enum Enum {
-    A = 1,
-    B = 2,
-}
-```
-
-```json
-[
-  {
-    "type": "struct",
-    "doc": "",
-    "name": "Enum",
-    "fields": [
-      {
-        "doc": "",
-        "name": "A",
-        "type": "u32"
-      },
-      {
-        "doc": "",
-        "name": "B",
-        "type": "u32"
-      }
-    ]
-  }
-]
-```
-
-```python
-from stellar_sdk import scval
-scval.to_vec(
-    [
-        scval.to_uint32(0),
-        scval.to_uint32(0),
-    ]
-)
-```
-
-```java
-import org.stellar.sdk.xdr.SCVal;
-import org.stellar.sdk.scval.Scv;
-import java.util.LinkedHashMap;
-
-List<SCVal> vec = new ArrayList<SCVal>();
-vec.add(Scv.toUint32(0));
-vec.add(Scv.toUint32(0));
-SCVal val = Scv.toVec(vec);
-```
-
-```php
-<?php
-use Soneso\StellarSDK\Xdr\XdrSCVal;
-
-XdrSCVal::forVec(
-    [
-        XdrSCVal::forU32(0),
-        XdrSCVal::forU32(0),
-    ]
-);
-```
-
-</CodeExample>
-
-### Un ejemplo complejo
-
-Usaremos el ejemplo del [contrato de bloqueo de tiempo](https://github.com/stellar/soroban-examples/blob/main/timelock/src/lib.rs) para mostrar cómo interactuar con un contrato que tiene tipos de datos complejos.
-
-Este ejemplo utiliza una estructura `TimeBound` que tiene un enum `TimeBoundKind` como uno de sus campos, que son parámetros para la función `deposit`. Este ejemplo combina la mayoría de los conceptos que hemos discutido hasta ahora.
-
-<CodeExample>
-
-```rust
-#[derive(Clone)]
-#[contracttype]
-pub enum TimeBoundKind {
-    Before,
-    After,
-}
-
-#[derive(Clone)]
-#[contracttype]
-pub struct TimeBound {
-    pub kind: TimeBoundKind,
-    pub timestamp: u64,
-}
-
-#[contracttype]
-#[contractimpl]
-impl ClaimableBalanceContract {
-    pub fn deposit(
-        env: Env,
-        from: Address,
-        token: Address,
-        amount: i128,
-        claimants: Vec<Address>,
-        time_bound: TimeBound,
-    )  {}
-}
-```
-
-```json
-[
-  {
-    "type": "union",
-    "doc": "",
-    "name": "TimeBoundKind",
-    "cases": [
-      {
-        "doc": "",
-        "name": "Before",
-        "values": []
-      },
-      {
-        "doc": "",
-        "name": "After",
-        "values": []
-      }
-    ]
-  },
-  {
-    "type": "struct",
-    "doc": "",
-    "name": "TimeBound",
-    "fields": [
-      {
-        "doc": "",
-        "name": "kind",
-        "value": {
-          "type": "custom",
-          "name": "TimeBoundKind"
-        }
-      },
-      {
-        "doc": "",
-        "name": "timestamp",
-        "value": {
-          "type": "u64"
-        }
-      }
-    ]
-  },
-  {
-    "type": "function",
-    "doc": "",
-    "name": "deposit",
-    "inputs": [
-      {
-        "doc": "",
-        "name": "from",
-        "value": {
-          "type": "address"
-        }
-      },
-      {
-        "doc": "",
-        "name": "token",
-        "value": {
-          "type": "address"
-        }
-      },
-      {
-        "doc": "",
-        "name": "amount",
-        "value": {
-          "type": "i128"
-        }
-      },
-      {
-        "doc": "",
-        "name": "claimants",
-        "value": {
-          "type": "vec",
-          "element": {
-            "type": "address"
-          }
-        }
-      },
-      {
-        "doc": "",
-        "name": "time_bound",
-        "value": {
-          "type": "custom",
-          "name": "TimeBound"
-        }
-      }
-    ],
-    "outputs": []
-  }
-]
-```
-
-```python
-from stellar_sdk import scval, SorobanServer, Keypair, Network, TransactionBuilder
-
-secret = "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
-rpc_server_url = "https://soroban-testnet.stellar.org:443"
-contract_id = "CAIKIZOT2LXM2WBEPGTZTPHHTGVHGLEOSI4WE6BOHWIBHJOKHPMCOPLO"
-
-network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-
-kp = Keypair.from_secret(secret)
-soroban_server = SorobanServer(rpc_server_url)
-source = soroban_server.load_account(kp.public_key)
-
-# Let's build a transaction that invokes the `deposit` function.
-tx = (
-    TransactionBuilder(source, network_passphrase, base_fee=1000)
-    .set_timeout(300)
-    .append_invoke_contract_function_op(
-        contract_id=contract_id,
-        function_name="deposit",
-        parameters=[
-            scval.to_address(kp.public_key),
-            scval.to_address("GXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"),
-            scval.to_int128(1),
-            scval.to_vec(
-                [
-                    scval.to_address("GXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"),
-                ]
-            ),
-            scval.to_map(
-                {
-                    scval.to_symbol("kind"): scval.to_vec(
-                        [
-                            scval.to_symbol("Before"),
-                        ]
-                    ),
-                    scval.to_symbol("timestamp"): scval.to_uint64(12346),
-                }
-            ),
-        ],
-    )
-    .build()
-)
-```
-
-</CodeExample>
-
-## Lectura de eventos del contrato
-
-Leer eventos del contrato es similar a leer resultados de transacciones. Puedes usar el método RPC [`getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents.mdx) para obtener la lista de eventos asociados con un contrato.
-
-Una convención común es que cadenas pequeñas como nombres de función, claves de enum y temas de eventos se representan como `ScSymbol` en la especificación del contrato.
-
-Sin embargo, los temas de eventos pueden ser de cualquier tipo `scval` dependiendo de la implementación del contrato.
-
-En el siguiente ejemplo, codificaremos el mint a `ScSymbol` antes de consultarlo, y también codificaremos las direcciones a `ScAddress`. Incluso después de obtener el evento, necesitaremos analizar los temas y valores para recuperar los valores reales de xdr base 64 a sus tipos correspondientes antes de convertirlos a tipos nativos.
-
-<CodeExample>
-
-```rust
-let address_1: &Address = "GXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX".into();
-let address_2: &Address = "GXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX".into();
-let count: i128 = 1;
-env.events()
-    .publish((symbol_short!("mint"), address_1, address_2), count);
-```
-
-```python
-from stellar_sdk import SorobanServer, scval, stellar_xdr
-from stellar_sdk.exceptions import NotFoundError, BadResponseError
-from stellar_sdk.soroban_server import EventFilter, EventFilterType
-
-def get_events():
-    server = SorobanServer("https://soroban-testnet.stellar.org")
-    # Define the request parameters
-    start_ledger = 835020
-    contract_id = "CDLYESZILKBHBRSPKQCQ3Q4K4N6MBI6UIQR3QXJ5L6WSYXC4EMTHSNNX"
-    topic = [
-            scval.to_symbol("mint").to_xdr(),
-            scval.to_address("GALIALRZJ5EU2IJJSIQEA3D3ZIEHK5HPBHZJFUEPTGQU3MYEKKIUINTY").to_xdr(),
-            scval.to_address("GC45QSBFYHGQUIWWQEOZ43INQGXX57CSSAABWRZ325H7MNFIFWZ56FD4").to_xdr(),
-        ]
-
-    try:
-        # Use the get_events method directly
-        events_response = server.get_events(
-            start_ledger=start_ledger,
-            filters=[
-                EventFilter(
-                    event_type=EventFilterType.CONTRACT,
-                    contract_ids=[contract_id],
-                    topics=[topic]
-                )
-            ],
-            limit=20
-        )
-
-        # Process the response
-        print(f"Latest ledger: {events_response.latest_ledger}")
-        for event in events_response.events:
-            print(f"Event ID: {event.id}")
-            print(f"Contract ID: {event.contract_id}")
-            for _topic in event.topic:
-                if _topic is None:
-                    continue
-                sc_val = stellar_xdr.SCVal.from_xdr(_topic)
-                if sc_val.sym is not None:
-                    print(f"Topic: {scval.from_symbol(sc_val)}")
-                if sc_val.address is not None:
-                    print(f"Topic: {scval.from_address(sc_val).address}")
-            if event.value is not None:
-                value_sc_val = stellar_xdr.SCVal.from_xdr(event.value)
-                if value_sc_val.i128 is not None:
-                    print(f"Value: {scval.from_int128(value_sc_val)}")
-            print("---")
-
-    except NotFoundError:
-        print("No events found for the given parameters.")
-    except BadResponseError as e:
-        print(f"Error occurred: {str(e)}")
-```
-
-```bash
-curl -X POST \
-  -H 'Content-Type: application/json' \
-  -d '{
-    "jsonrpc": "2.0",
-    "id": 1,
-    "method": "getEvents",
-    "params": {
-      "startLedger": 1190000,
-      "filters": [
-        {
-          "type": "contract",
-          "contractIds": [
-            "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"
-          ],
-          "topics": [
-            [
-              "AAAADwAAAARtaW50",
-              "AAAAEgAAAAAAAAAAFoAuOU9JTSEpkiBAbHvKCHV07wnyktCPmaFNswRSkUQ=",
-              "AAAAEgAAAAAAAAAAudhIJcHNCiLWgR2ebQ2Br378UpAAG0c710/2NKgts98=",
-            ]
-          ]
-        }
-      ],
-      "pagination": {
-        "limit": 20
-      }
-    }
-  }' \
-  https://soroban-testnet.stellar.org
-```
-
-</CodeExample>
-
-## Conclusión
-
-Como hemos visto, trabajar con contratos inteligentes de Soroban en diferentes lenguajes de programación no es ciencia espacial, pero requiere atención cuidadosa a los detalles. Los puntos clave son:
-
-- Siempre comienza con un sólido entendimiento de la especificación de tu contrato
-- Conviértete en un experto en convertir entre tipos nativos y las peculiares estructuras de datos de Soroban
-- No te intimidis por los tipos de datos complejos - son solo acertijos esperando ser resueltos
-- Cuando tengas dudas, consulta la documentación de tu SDK para las sutilezas específicas del lenguaje
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/README.mdx
deleted file mode 100644
index e9bd1644f5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Eventos del contrato
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 20
----
-
-Aprender a emitir, ingerir y usar eventos publicados desde un contrato inteligente de Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/consume.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/consume.mdx
deleted file mode 100644
index 1c13d299f6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/consume.mdx
+++ /dev/null
@@ -1,210 +0,0 @@
----
-title: Consumir eventos previamente ingeridos
-description: Consumir eventos ingeridos sin consultar de nuevo el RPC
----
-
-Una vez que los eventos han sido ingeridos en una base de datos, por ejemplo, como se hace en la [guía de ingestión], pueden ser consumidos sin que sea necesario consultar nuevamente el RPC de Stellar. A continuación, mostraremos cómo podemos consumir estos eventos.
-
-¡Vamos a comenzar!
-
-## Primero, obtén algunos eventos en una base de datos
-
-Siguiendo justo donde lo dejamos en la [guía de ingestión], utilizaremos los modelos ORM para añadir varias más eventos.
-
-```python
-from sqlalchemy import create_engine
-engine = create_engine("sqlite://", echo=True)
-```
-
-Recuerda que los eventos publicados por Soroban están codificados en XDR. Podemos utilizar [stellar-sdk] para convertir entre valores y la representación XDR.
-
-A continuación, usaremos un tema llamado `transfer` y necesitaremos algunos valores y direcciones. Podemos generar algunos datos de prueba:
-
-```python
-import stellar_sdk
-
-stellar_sdk.scval.to_symbol("transfer").to_xdr()
-# 'AAAADwAAAAh0cmFuc2Zlcg=='
-stellar_sdk.scval.to_int32(10_000).to_xdr()
-# 'AAAABAAAJxA='
-stellar_sdk.scval.to_int32(5_000).to_xdr()
-# 'AAAABAAAE4g='
-stellar_sdk.scval.to_int32(1_000).to_xdr()
-# 'AAAABAAAA+g='
-stellar_sdk.scval.to_address("GA7YNBW5CBTJZ3ZZOWX3ZNBKD6OE7A7IHUQVWMY62W2ZBG2SGZVOOPVH").to_xdr()
-# 'AAAAEgAAAAAAAAAAP4aG3RBmnO85da+8tCofnE+D6D0hWzMe1bWQm1I2auc='
-stellar_sdk.scval.to_address("GAFYGBHKVFP36EOIRGG74V42F3ORAA2ZWBXNULMNDXAMMXQH5MCIGXXI").to_xdr()
-# 'AAAAEgAAAAAAAAAAC4ME6qlfvxHIiY3+V5ou3RADWbBu2i2NHcDGXgfrBIM='
-```
-
-Ahora podemos crear algunos eventos usando nuestro ORM y enviarlos a la base de datos:
-
-```python
-from sqlalchemy.orm import sessionmaker
-
-contract_id = "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"
-Session = sessionmaker(engine)
-with Session.begin() as session:
-    event_1 = Event(
-        ledger=1,
-        contract_id=contract_id,
-        topics={
-            # transfer
-            "topic_1": "AAAADwAAAAh0cmFuc2Zlcg==",
-            # GA7YNBW5CBTJZ3ZZOWX3ZNBKD6OE7A7IHUQVWMY62W2ZBG2SGZVOOPVH
-            "topic_2": "AAAAEgAAAAAAAAAAP4aG3RBmnO85da+8tCofnE+D6D0hWzMe1bWQm1I2auc="
-        },
-        value="AAAABAAAJxA="
-    )
-    event_2 = Event(
-        ledger=1,
-        contract_id=contract_id,
-        topics={
-            # transfer
-            "topic_1": "AAAADwAAAAh0cmFuc2Zlcg==",
-            # GAFYGBHKVFP36EOIRGG74V42F3ORAA2ZWBXNULMNDXAMMXQH5MCIGXXI
-            "topic_2": "AAAAEgAAAAAAAAAAC4ME6qlfvxHIiY3+V5ou3RADWbBu2i2NHcDGXgfrBIM="
-        },
-        value="AAAABAAAE4g="
-    )
-    session.add_all([event_1, event_2])
-```
-
-```text
-INFO sqlalchemy.engine.Engine BEGIN (implicit)
-INFO sqlalchemy.engine.Engine INSERT INTO "SorobanEvent" (contract_id, ledger, topics, value) VALUES (?, ?, ?, ?) RETURNING id
-INFO sqlalchemy.engine.Engine [...] ('CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC', 1, '{"topic_1": "AAAADwAAAAh0cmFuc2Zlcg==", "topic_2": "AAAAEgAAAAAAAAAAP4aG3RBmnO85da+8tCofnE+D6D0hWzMe1bWQm1I2auc="}', 'AAAABAAAJxA=')
-INFO sqlalchemy.engine.Engine INSERT INTO "SorobanEvent" (contract_id, ledger, topics, value) VALUES (?, ?, ?, ?) RETURNING id
-INFO sqlalchemy.engine.Engine [...] ('CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC', 1, '{"topic_1": "AAAADwAAAAh0cmFuc2Zlcg==", "topic_2": "AAAAEgAAAAAAAAAAC4ME6qlfvxHIiY3+V5ou3RADWbBu2i2NHcDGXgfrBIM="}', 'AAAABAAAE4g=')
-INFO sqlalchemy.engine.Engine COMMIT
-```
-
-:::info
-
-Aquí, estamos almacenando valores codificados en XDR. En su lugar, podríamos haber decidido almacenar valores decodificados en la base de datos. Dado que XDR es un formato comprimido, elegir cuándo decodificar el valor es un compromiso entre el uso de CPU y el consumo de memoria.
-
-:::
-
-## Consumiendo eventos
-
-Utilizando el mismo modelo que usamos para ingerir eventos en la base de datos, podemos consultar la base de datos para iterar sobre todos los eventos presentes en la tabla.
-
-```python
-import sqlalchemy
-from sqlalchemy import orm
-
-with orm.Session(engine) as session:
-    stmt = sqlalchemy.select(Event)
-    for event in session.scalars(stmt):
-        print(event.topics, event.value)
-```
-
-```text
-INFO sqlalchemy.engine.Engine BEGIN (implicit)
-INFO sqlalchemy.engine.Engine SELECT "SorobanEvent".id, "SorobanEvent".contract_id, "SorobanEvent".ledger, "SorobanEvent".topics, "SorobanEvent".value
-FROM "SorobanEvent"
-INFO sqlalchemy.engine.Engine [...] ()
-...
-['AAAADwAAAAh0cmFuc2Zlcg==', 'AAAAEgAAAAAAAAAAbskHLxwXdlUVH3X3pVMFqpLHYpwmDD/PoaqYnQkX7J4=', 'AAAAEgAAAAGqo5kAOYww4Z8QWIx9TqXkXUvjFUg8mpEbsg03vV+8/w==', 'AAAADgAAAAZuYXRpdmUAAA=='] AAAACgAAAAAAAAAAAAAAC6Q7dAA=
-['AAAADwAAAAh0cmFuc2Zlcg==', 'AAAAEgAAAAAAAAAAL6/diRR4by9YIZCM/+O0/BGYKWlSn2CvTEiHBptJs+k=', 'AAAAEgAAAAGqo5kAOYww4Z8QWIx9TqXkXUvjFUg8mpEbsg03vV+8/w==', 'AAAADgAAAAZuYXRpdmUAAA=='] AAAACgAAAAAAAAAAAAAAAAvrwgA=
-{'topic_1': 'AAAADwAAAAh0cmFuc2Zlcg==', 'topic_2': 'AAAAEgAAAAAAAAAAP4aG3RBmnO85da+8tCofnE+D6D0hWzMe1bWQm1I2auc='} AAAABAAAJxA=
-{'topic_1': 'AAAADwAAAAh0cmFuc2Zlcg==', 'topic_2': 'AAAAEgAAAAAAAAAAC4ME6qlfvxHIiY3+V5ou3RADWbBu2i2NHcDGXgfrBIM='} AAAABAAAE4g=
-INFO sqlalchemy.engine.Engine ROLLBACK
-```
-
-:::note
-
-Observa cómo los eventos anteriores están presentes y tienen un formato ligeramente diferente. Aunque estamos utilizando un esquema, todavía es fácil corromper una base de datos. Esto solo se muestra con fines de demostración.
-
-:::
-
-SQLAlchemy permite realizar consultas avanzadas. Por ejemplo, podríamos filtrar un solo evento basado en algunos campos específicos.
-
-```python
-with orm.Session(engine) as session:
-    stmt = sqlalchemy.select(Event).where(Event.ledger == 1)
-    for event in session.scalars(stmt):
-        print(event.topics, event.value)
-```
-
-```text
-INFO sqlalchemy.engine.Engine BEGIN (implicit)
-INFO sqlalchemy.engine.Engine SELECT "SorobanEvent".id, "SorobanEvent".contract_id, "SorobanEvent".ledger, "SorobanEvent".topics, "SorobanEvent".value
-FROM "SorobanEvent"
-WHERE "SorobanEvent".ledger = ?
-INFO sqlalchemy.engine.Engine [...] (1,)
-{'topic_1': 'AAAADwAAAAh0cmFuc2Zlcg==', 'topic_2': 'AAAAEgAAAAAAAAAAP4aG3RBmnO85da+8tCofnE+D6D0hWzMe1bWQm1I2auc='} AAAABAAAJxA=
-{'topic_1': 'AAAADwAAAAh0cmFuc2Zlcg==', 'topic_2': 'AAAAEgAAAAAAAAAAC4ME6qlfvxHIiY3+V5ou3RADWbBu2i2NHcDGXgfrBIM='} AAAABAAAE4g=
-INFO sqlalchemy.engine.Engine ROLLBACK
-```
-
-## Transmitiendo eventos
-
-Dependiendo de nuestra aplicación, podríamos querer consumir eventos periódicamente llamando a la base de datos para ver si hay algo nuevo. O obtener datos según lo necesite nuestra aplicación. Hay otra posibilidad: ¡oyentes de eventos!
-
-Mientras tanto, podemos hacer que los resultados sean más legibles o utilizables en Python utilizando el asistente de conversión proporcionado por [stellar-sdk].
-
-```python
-@sqlalchemy.event.listens_for(Event, "after_insert")
-def event_handler(mapper, connection, target):
-    topics = target.topics
-    value = stellar_sdk.scval.to_native(target.value)
-
-    for key, topic in topics.items():
-        topics[key] = stellar_sdk.scval.to_native(topic)
-
-    print(f"Event listener: {topics} {value}")
-```
-
-La próxima vez que se inserte un registro en la base de datos, se llamará a este handler de eventos. Intenta esto:
-
-```python
-with Session.begin() as session:
-    event_3 = Event(
-        ledger=2,
-        contract_id=contract_id,
-        topics={
-            # transfer
-            "topic_1": "AAAADwAAAAh0cmFuc2Zlcg==",
-            # GA7YNBW5CBTJZ3ZZOWX3ZNBKD6OE7A7IHUQVWMY62W2ZBG2SGZVOOPVH
-            "topic_2": "AAAAEgAAAAAAAAAAP4aG3RBmnO85da+8tCofnE+D6D0hWzMe1bWQm1I2auc="
-        },
-        value="AAAABAAAJxA="
-    )
-    session.add(event_3)
-```
-
-```text
-INFO sqlalchemy.engine.Engine BEGIN (implicit)
-INFO sqlalchemy.engine.Engine INSERT INTO "SorobanEvent" (contract_id, ledger, topics, value) VALUES (?, ?, ?, ?)
-INFO sqlalchemy.engine.Engine [...] ('CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC', 2, '{"topic_1": "AAAADwAAAAh0cmFuc2Zlcg==", "topic_2": "AAAAEgAAAAAAAAAAP4aG3RBmnO85da+8tCofnE+D6D0hWzMe1bWQm1I2auc="}', 'AAAABAAAJxA=')
-Event listener: {'topic_1': 'transfer', 'topic_2': <Address [type=ACCOUNT, address=GA7YNBW5CBTJZ3ZZOWX3ZNBKD6OE7A7IHUQVWMY62W2ZBG2SGZVOOPVH]>} 10000
-INFO sqlalchemy.engine.Engine COMMIT
-```
-
-¡Felicidades, estás listo para consumir eventos de Stellar RPC!
-
-## Avanzando
-
-Utilizar las técnicas que acabamos de presentar probablemente sería suficiente para muchos casos de uso. Sin embargo, para los lectores que quieren avanzar, hay algunas cosas en las que mirar.
-
-### Programación asincrónica
-
-Hasta ahora, hemos utilizado SQLAlchemy de manera sincrónica. Si tuviéramos un endpoint en el backend llamando a la base de datos, este endpoint se bloquearía durante la llamada a la base de datos. SQLAlchemy admite la programación asincrónica con las palabras clave `async` y `await`.
-
-Como reflexión general, es más simple comenzar con una lógica sincrónica y luego pasar a añadir soporte para asincrónica cuando todo funcione como se espera. Depurar aplicaciones concurrentes trae una capa adicional de complejidad.
-
-SQLAlchemy te permite cambiar simplemente de una sesión sincrónica a una asincrónica sin necesidad de cambiar tus modelos ni consultas, lo que hace que sea una tarea muy fácil usar uno u otro.
-
-### Consideraciones de idempotencia
-
-Dependiendo de tu aplicación, podrías querer investigar el concepto de idempotencia. O dicho de otra manera: garantizar que un evento sea consumido solo una vez.
-
-Por ejemplo, si usas eventos para fines contables en una aplicación de pagos, procesar dos veces el mismo evento podría resultar en un doble gasto. En tales casos, querrás que tu sistema sea idempotente para garantizar que este escenario esté cubierto.
-
-Hay una gran cantidad de literatura técnica sobre este tema y no hay una solución única que funcione para todos. Podría ser suficiente que tu aplicación agregue una columna en la base de datos para marcar un mensaje como procesado, aunque necesitarías tener en cuenta los problemas de red que pueden ocurrir mientras procesas un evento determinado. Usar SQLAlchemy con una base de datos como PostgreSQL podría ayudar, ya que si se hace correctamente, las operaciones pueden hacerse atómicas. Es decir, puedes asegurarte de que una cierta cadena de acciones ha sido realizada antes de comprometer una transacción a la base de datos.
-
-Mientras investigas este tema, podrías buscar _brokers de mensajes_ como RabbitMQ o Kafka, para citar soluciones ampliamente utilizadas.
-
-[guía de ingestión]: ingest.mdx
-[stellar-sdk]: https://stellar-sdk.readthedocs.io/
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/ingest.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/ingest.mdx
deleted file mode 100644
index e2b34ec897..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/ingest.mdx
+++ /dev/null
@@ -1,318 +0,0 @@
----
-title: Ingerir eventos publicados desde un contrato
-description: Usar el método getEvents de Stellar RPC para consultar eventos, con una ventana de retención de 7 días
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-Stellar RPC proporciona un [`método getEvents`] que te permite consultar eventos de un contrato inteligente. Sin embargo, la ventana de retención de datos para estos eventos es de 7 días como máximo. Si necesitas acceso a un registro de estos eventos más duradero, querrás "ingerir" los eventos a medida que se publican, manteniendo tu propio registro o base de datos a medida que se ingieren los eventos.
-
-Hay muchas estrategias que puedes usar para ingerir y mantener los eventos publicados por un contrato inteligente. Entre las más simples podría estar utilizar una herramienta desarrollada por la comunidad como [Mercury](https://mercurydata.app), que se encargará de todo el trabajo de infraestructura por una baja tarifa de suscripción. O bien, [los indexadores](../../../data/indexers/README.mdx) pueden proporcionar datos de eventos ingeridos a precios accesibles.
-
-Otro enfoque que exploraremos aquí es usar un trabajo cron para consultar Stellar RPC periódicamente y almacenar los eventos relevantes en una base de datos SQLite almacenada localmente. Vamos a usar un Mapeador Relacional de Objetos (ORM), que nos permitirá escribir consultas a la base de datos directamente en Python o JavaScript.
-
-## Configuración
-
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
-
-En un [entorno virtual](https://docs.python.org/3/tutorial/venv.html), instala las dependencias de Python:
-
-```sh
-pip install sqlalchemy stellar-sdk
-```
-
-</TabItem>
-</Tabs>
-
-## Configurar el Cliente de Base de Datos
-
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
-
-Para acceder a la base de datos, vamos a usar [SQLAlchemy](https://www.sqlalchemy.org), que es una biblioteca de Python frecuentemente utilizada para consultar bases de datos.
-
-Vamos a ingerir eventos en una tabla llamada `StellarEvent`. En SQLAlchemy, esto se traduce en una clase, también llamada modelo de base de datos:
-
-```python
-from typing import Any
-from sqlalchemy import orm, JSON
-
-
-class Base(orm.DeclarativeBase):
-    # needed to tell SQLAlchemy to translate a dictionary into a JSON entry
-    type_annotation_map = {
-        dict[str, Any]: JSON,
-    }
-
-
-class Event(Base):
-    __tablename__ = "StellarEvent"
-
-    id: orm.Mapped[int] = orm.mapped_column(primary_key=True)
-    contract_id: orm.Mapped[str]
-    ledger: orm.Mapped[int]
-    topics: orm.Mapped[dict[str, Any]]
-    value: orm.Mapped[str]
-```
-
-Usaremos una base de datos SQLite solo en memoria para esta guía, pero gracias al uso de un ORM, podríamos estar usando cualquier otra base de datos admitida. Simplemente tendríamos que cambiar la cadena de conexión.
-
-```python
-from sqlalchemy import create_engine
-engine = create_engine("sqlite://", echo=True)
-
-# the following creates the table in the DB
-Base.metadata.create_all(engine)
-```
-
-:::tip
-
-Al establecer `echo=True`, podemos entender lo que está sucediendo en la base de datos. La creación de la tabla de la base de datos genera los siguientes registros:
-
-:::
-
-```text
-BEGIN (implicit)
-PRAGMA main.table_info("StellarEvent")
-...
-PRAGMA temp.table_info("StellarEvent")
-...
-CREATE TABLE StellarEvent (
-	id INTEGER NOT NULL,
-    contract_id VARCHAR NOT NULL,
-    ledger INTEGER NOT NULL,
-	topics JSON NOT NULL,
-	value VARCHAR NOT NULL,
-	PRIMARY KEY (id)
-)
-...
-COMMIT
-```
-
-</TabItem>
-<TabItem value="js" label="JavaScript">
-
-Los detalles más finos de elegir una configuración de Prisma están más allá del alcance de este documento. Puedes obtener mucha más información en la [guía rápida de Prisma](https://www.prisma.io/docs/getting-started/quickstart). Aquí está el modelo del esquema de nuestro Prisma:
-
-```text
-model StellarEvent {
-  id          String @id
-  type        String
-  ledger      Int
-  contract_id String
-  topic_1     String?
-  topic_2     String?
-  topic_3     String?
-  topic_4     String?
-  value       String
-}
-```
-
-</TabItem>
-</Tabs>
-
-:::info
-
-Usar un modelo de base de datos es muy conveniente ya que nos permite controlar el esquema de la base de datos programáticamente. Si necesitamos cambiar el esquema, por ejemplo, agregando nuevas columnas, entonces usar un ORM nos permite utilizar herramientas de migración muy poderosas.
-
-:::
-
-Usaremos este modelo para crear y consultar los eventos almacenados en nuestra base de datos.
-
-## Consultar eventos desde Stellar RPC
-
-Primero, necesitaremos consultar los eventos desde Stellar RPC. Este ejemplo sencillo realiza una solicitud RPC usando el [`método getEvents`], filtrando todos los eventos `transfer` que emite el contrato nativo de XLM.
-
-:::note
-
-Estamos haciendo algunas suposiciones aquí. Supondremos que tu contrato tiene suficiente actividad, y que estás consultando eventos con suficiente frecuencia para no estar en peligro de necesitar averiguar cuál es el ledger más antiguo que Stellar RPC conoce. El enfoque que estamos tomando es encontrar el número de secuencia del ledger más grande (más reciente) en la base de datos y consultar eventos comenzando desde allí. Tu caso de uso puede requerir algo de lógica para determinar cuál es el ledger más reciente y cuál es el ledger más antiguo disponible, etc.
-
-:::
-
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
-
-Si comenzamos desde cero, no hay ledger conocido, así que podemos intentar ingerir aproximadamente los últimos 7 días asumiendo que un ledger se cierra cada 6s.
-
-```python
-import stellar_sdk
-
-soroban_server = stellar_sdk.SorobanServer("https://soroban-testnet.stellar.org")
-ledger = soroban_server.get_latest_ledger().sequence - int(3600 / 6 * 24 * 7)
-```
-
-Más adelante, podremos empezar desde el ledger más recientemente ingerido haciendo una consulta a nuestra base de datos.
-
-```python
-with orm.Session(engine) as session:
-    stmt = sqlalchemy.select(Event.ledger).where(
-        Event.contract_id == contract_id
-    ).order_by(Event.ledger.desc())
-    ingested_ledger = session.scalars(stmt).first()
-
-    if ingested_ledger:
-      ledger = ingested_ledger
-```
-
-¡Obtengamos eventos de Stellar RPC!
-
-```python
-from stellar_sdk.soroban_rpc import EventFilter, EventFilterType
-
-contract_id = "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"
-
-res = soroban_server.get_events(
-    ledger,
-    filters=[
-        EventFilter(
-            type=EventFilterType.CONTRACT,
-            contract_ids=[contract_id],
-            topics=[["AAAADwAAAAh0cmFuc2Zlcg==", "*", "*", "*"]],
-        )
-    ],
-)
-events = res.events
-```
-
-</TabItem>
-<TabItem value="js" label="JavaScript">
-
-Usamos la biblioteca `@stellar/stellar-sdk`:
-
-```javascript
-import { Server } from "@stellar/stellar-sdk/rpc";
-import { PrismaClient } from "@prisma/client";
-
-const server = new Server("https://soroban-testnet.stellar.org");
-const prisma = new PrismaClient();
-
-let latestEventIngested = await prisma.stellarEvent.findFirst({
-  orderBy: [
-    {
-      ledger: "desc",
-    },
-  ],
-});
-
-let { events } = await server.getEvents({
-  startLedger: latestEventIngested.ledger,
-  filters: [
-    {
-      type: "contract",
-      contractIds: ["CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"],
-      topics: [["AAAADwAAAAh0cmFuc2Zlcg==", "*", "*", "*"]],
-    },
-  ],
-});
-```
-
-</TabItem>
-</Tabs>
-
-## Almacenar eventos en la base de datos
-
-Ahora, vamos a verificar si el objeto `events` contiene algún evento nuevo que debamos almacenar, y hacemos exactamente eso. Estamos almacenando los topics y valores del evento como cadenas codificadas en base64 aquí, pero podrías decodificar los topics y valores necesarios a los tipos de datos apropiados para tu caso de uso.
-
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
-
-:::tip
-
-Facilita tu vida con un [`sessionmaker`](https://docs.sqlalchemy.org/en/20/orm/session_basics.html#using-a-sessionmaker) de SQLAlchemy al hacer transacciones (por ejemplo, añade más de un registro en una sola llamada a la base de datos).
-
-:::
-
-```python
-import sqlalchemy
-from sqlalchemy.orm import sessionmaker
-
-Session = sessionmaker(engine)
-with Session.begin() as session:
-    events_ = []
-    for event in events:
-        topic_ = event.topic
-        events_.append(Event(contract_id=contract_id, ledger=event.ledger, topics=topic_, value=event.value))
-    session.add_all(events_)
-```
-
-```text
-BEGIN (implicit)
-INFO sqlalchemy.engine.Engine COMMIT
-INFO sqlalchemy.engine.Engine BEGIN (implicit)
-INFO sqlalchemy.engine.Engine INSERT INTO "StellarEvent" (contract_id, ledger, topics, value) VALUES (?, ?, ?, ?) RETURNING id
-INFO sqlalchemy.engine.Engine [...] ('CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC', 3311, '["AAAADwAAAAh0cmFuc2Zlcg==", "AAAAEgAAAAAAAAAAJY16rJOcKxQayCR7ayNA80hW5q1U4ypIGOY7NktBfKU=", "AAAAEgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQ==", "AAAADgAAAAZuYXRpdmUAAA=="]', 'AAAACgAAAAAAAAAAAAAAAAAAAGQ=')
-INFO sqlalchemy.engine.Engine INSERT INTO "StellarEvent" (contract_id, ledger, topics, value) VALUES (?, ?, ?, ?) RETURNING id
-INFO sqlalchemy.engine.Engine [...] ('CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC', 3325, '["AAAADwAAAAh0cmFuc2Zlcg==", "AAAAEgAAAAAAAAAAJY16rJOcKxQayCR7ayNA80hW5q1U4ypIGOY7NktBfKU=", "AAAAEgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQ==", "AAAADgAAAAZuYXRpdmUAAA=="]', 'AAAACgAAAAAAAAAAAAAAAAAAAGQ=')
-...
-COMMIT
-```
-
-</TabItem>
-<TabItem value="js" label="JavaScript">
-
-```javascript
-if (events?.length) {
-  events.forEach(async (event) => {
-    await prisma.stellarEvent.create({
-      data: {
-        id: event.id,
-        type: event.type,
-        ledger: event.ledger,
-        contract_id: event.contractId!.toString(),
-        topic_1: event.topic[0]?.toXDR('base64') || null,
-        topic_2: event.topic[1]?.toXDR('base64') || null,
-        topic_3: event.topic[2]?.toXDR('base64') || null,
-        topic_4: event.topic[3]?.toXDR('base64') || null,
-        value: event.value.toXDR('base64')
-      },
-    });
-  });
-}
-```
-
-</TabItem>
-</Tabs>
-
-## Ejecutar el Script con Cron
-
-Una entrada cron es una excelente manera de automatizar este script para recopilar e ingerir eventos cada cierto tiempo. Puedes configurar este script para que se ejecute tan (in)frecuentemente como desees o necesites. Este ejemplo ejecutaría el script cada 24 horas a la 1:14 pm:
-
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
-
-```sh
-14 13 * * * python /absolute/path/to/script.py
-```
-
-</TabItem>
-<TabItem value="js" label="JavaScript">
-
-```sh
-14 13 * * * node /absolute/path/to/script.js
-```
-
-</TabItem>
-</Tabs>
-
-Aquí hay otro ejemplo que ejecutaría el script cada 30 minutos:
-
-<Tabs groupId="language" defaultValue="python">
-<TabItem value="python" label="Python">
-
-```sh
-30 * * * * python /absolute/path/to/script.py
-```
-
-</TabItem>
-<TabItem value="js" label="JavaScript">
-
-```sh
-30 * * * * node /absolute/path/to/script.js
-```
-
-</TabItem>
-</Tabs>
-
-[Método `getEvents`]: ../../../data/apis/rpc/api-reference/methods/getEvents.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/publish.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/publish.mdx
deleted file mode 100644
index 42366346a1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/events/publish.mdx
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Publicar eventos desde un contrato de Rust
-hide_table_of_contents: true
-description: Publicar eventos desde un contrato de Rust
----
-
-Un evento puede contener temas, además de los datos que está publicando. Los datos de los temas pueden ser cualquier valor o tipo que desees.
-
-:::info[Whisk Cambios]
-
-Con el lanzamiento de Whisk, Protocolo 23, la sintaxis para publicar eventos de contratos inteligentes ha cambiado. Para proporcionar la información más actualizada, esta guía se ha actualizado para incluir los nuevos patrones. Encuentra información más detallada en la [documentación del SDK de Rust].
-
-:::
-
-La estrategia aquí es primero crear algunas `struct`s que definirán cómo se estructuran nuestros eventos. Luego, dentro de la función del contrato, podemos crear y publicar esas structs.
-
-```rust
-// This event will be published with the following structure:
-// `["COUNTER", "increment"], data = count: u32`
-#[contractevent(topics = ["COUNTER", "increment"], data_format = "single-value")]
-pub struct Increment {
-    count: u32,
-}
-
-// Events without explicit topics will use the struct name for the sole topic.
-// By default, the event data will follow the struct shape.
-// This event will be published with the following structure:
-// `["borrow"], data = {addr: Address, amount: i128}`
-#[contractevent]
-pub struct Borrow {
-    addr: Address,
-    amount: i128,
-}
-
-// Event topics can also be noted in the struct, so they're dynamic.
-// This event will be published with the following structure:
-// `["deposit", addr: Address, token: Address], data = [amount: i128, time: u64]`
-#[contractevent(data_format = "vec")]
-pub struct Deposit {
-    #[topic]
-    addr: Address,
-    #[topic]
-    token: Address,
-    amount: i128,
-    time: u64,
-}
-
-// This function does nothing beside publish events.
-pub fn events_function(env: Env, invoker: Address, token: Address) {
-    Increment {
-        count: 8675309,
-    }.publish(&env);
-
-    Borrow {
-        addr: invoker.clone(),
-        amount: 123_0000000,
-    }.publish(&env);
-
-    Deposit {
-        addr: invoker,
-        token: token,
-        amount: 321_0000000,
-        time: env.ledger().timestamp(),
-    }.publish(&env);
-}
-```
-
-Un ejemplo más realista se puede encontrar en la forma en que funciona la [interfaz de token]. Por ejemplo, la interfaz requiere que se publique un evento cada vez que se invoca la función `transfer`, con la siguiente información:
-
-```rust
-#[contractevent(data_format = "single-value")]
-pub struct Transfer {
-    #[topic]
-    from: Address,
-    #[topic]
-    to: Address,
-    amount: i128,
-}
-
-pub fn transfer(env: Env, from: Address, to: Address, amount: i128) {
-    // transfer logic omitted here
-    Transfer { from, to, amount }.publish(&env);
-}
-```
-
-[interfaz de token]: ../../../tokens/token-interface.mdx
-[Documentación del SDK de Rust]: https://docs.rs/soroban-sdk/latest/soroban_sdk/_migrating/v23_contractevent/index.html
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/README.mdx
deleted file mode 100644
index 36f741d489..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Tarifas y Medición
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 60
----
-
-Las tarifas y la medición en contratos inteligentes Soroban funcionan de manera diferente a las tarifas de las transacciones "regulares" Stellar. ¡La red Stellar sigue ofreciendo transacciones baratas y accesibles, y eso ahora incluye la medición de contratos inteligentes!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/analyzing-smart-contract-cost.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/analyzing-smart-contract-cost.mdx
deleted file mode 100644
index a58e3c61e7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/analyzing-smart-contract-cost.mdx
+++ /dev/null
@@ -1,596 +0,0 @@
----
-title: Analizar el costo y la eficiencia del contrato inteligente
-hide_table_of_contents: false
-description: Crear contratos eficientes y rentables
----
-
-Varios factores influyen en cuán rápida y eficientemente se ejecutan tus contratos inteligentes en la red Stellar. Esta guía te ayudará a entender estos factores y te proporcionará consejos sobre cómo redactar contratos rentables.
-
-## Cómo optimizar el costo del contrato inteligente:
-
-Los contratos complejos con numerosas condiciones, bucles y cálculos requieren más potencia de procesamiento en Stellar. Esto puede llevar a costos de gas más altos (comisiones por transacción) y tiempos de ejecución más lentos.
-
-### 1 Uso eficiente de llamadas a bucles y almacenamiento
-
-Un contrato que requiere múltiples bucles y condiciones para ejecutarse costará más que un contrato simple que ejecuta una sola operación.
-
-#### Contrato No Óptimo ❎
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, log, vec, Map, Env};
-
-#[contract]
-pub struct ExampleContract;
-
-#[contractimpl]
-impl ExampleContract {
-    // Function to update values in storage inefficiently
-    pub fn update_values(env: Env, values: Vec<u32>) {
-        for &value in values.iter() {
-            let current_count = env.storage().persistent().get("total_count");
-            env.storage().persistent().set("total_count", &(current_count + value));
-        }
-    }
-}
-
-```
-
-:::danger
-
-**Problema**: Cada iteración del bucle realiza una operación de lectura y escritura separada para actualizar total_count en el almacenamiento.
-
-**Ineficiente**: Esto resulta en múltiples operaciones de almacenamiento costosas (lectura y escritura) dentro del bucle, aumentando significativamente los costos de gas a medida que crece el tamaño de la matriz (values.len()).
-
-:::
-
-#### Contrato Óptimo ✅
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, log, vec, Env, Map};
-
-#[contract]
-pub struct ExampleContract;
-
-#[contractimpl]
-impl ExampleContract {
-    // Function to update values in storage efficiently
-    pub fn update_values(env: Env, values: Vec<u32>) {
-        let mut total_count = env.storage().persistent().get("total_count");
-
-        for &value in values.iter() {
-            total_count += value;
-        }
-
-        env.storage().persistent().set("total_count", &total_count);
-    }
-}
-
-```
-
-:::tip
-
-En este enfoque optimizado, acumularemos los cambios fuera del bucle y realizaremos una única actualización de almacenamiento y también una única operación de lectura. Esto reduce el número de operaciones de almacenamiento y el costo total de gas del contrato.
-
-:::
-
-### 2 Uso adecuado de operaciones en lote
-
-Del primer ejemplo, podemos ver que las operaciones en lote son más eficientes que las operaciones individuales. Esto se debe a que las operaciones en lote reducen el número de llamadas externas a la blockchain, que pueden ser costosas. Sin embargo, hay algunos escenarios en los que el uso de operaciones en lote puede ser optimizado aún más. A continuación se muestran ejemplos.
-
-#### Contrato No Óptimo ❎
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, Address, Env, Symbol};
-use soroban_sdk::token::Client as TokenClient;
-
-#[contract]
-pub struct TokenTransferContract;
-
-#[contractimpl]
-impl TokenTransferContract {
-    // Inefficient way: Multiple individual transfers
-    pub fn transfer_tokens_inefficient(
-        env: Env,
-        token: Address,
-        from: Address,
-        to: Vec<Address>,
-        amount_each: i128,
-    ) {
-        let token_client = TokenClient::new(&env, &token);
-
-        for recipient in to.iter() {
-            token_client.transfer(&from, recipient, &amount_each);
-        }
-    }
-}
-```
-
-:::danger
-
-Esta función realiza transferencias individuales para cada destinatario. Si bien es directa, es ineficiente porque cada transferencia es una llamada de subcontrato separada, lo que puede llevar a costos de gas más altos y a una ejecución más lenta.
-
-:::
-
-#### Contrato Óptimo ✅
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, Address, Env, Symbol};
-use soroban_sdk::token::Client as TokenClient;
-
-#[contract]
-pub struct TokenTransferContract;
-
-#[contractimpl]
-impl TokenTransferContract {
-    // Efficient way: Batch transfer
-    pub fn transfer_tokens_efficient(
-        env: Env,
-        token: Address,
-        from: Address,
-        to: Vec<Address>,
-        amount_each: i128,
-    ) {
-        let token_client = TokenClient::new(&env, &token);
-        let total_amount = amount_each * (to.len() as i128);
-
-        // Perform a single transfer for the total amount
-        token_client.transfer(&from, &env.current_contract_address(), &total_amount);
-
-        // Then distribute from the contract
-        for recipient in to.iter() {
-            token_client.transfer(&env.current_contract_address(), recipient, &amount_each);
-        }
-    }
-}
-```
-
-:::tip
-
-Esta función optimiza el proceso al:
-
-- Primero transfiriendo el monto total al contrato en una sola operación.
-- Luego distribuyendo los tokens desde el contrato a cada destinatario.
-
-Las distribuciones internas son más baratas debido a la reducción en el número de costosas transacciones externas de blockchain. Al transferir el monto total al contrato y luego distribuirlo internamente, el contrato minimiza el número de llamadas externas, reduciendo los costos de gas y mejorando la eficiencia.
-
-:::
-
-### 3 Uso de eventos en lugar de almacenamiento
-
-Los eventos son una forma rentable de almacenar datos que no necesitan ser accedidos con frecuencia. Los eventos son más baratos que las operaciones de almacenamiento y pueden ser utilizados para almacenar datos que no necesitan ser accedidos con frecuencia.
-
-#### Contrato Predeterminado
-
-```rust
-#![no_std]
-use soroban_sdk::{
-    contract, contractimpl, log, symbol_short, vec, Address, Env, Symbol,Map, Vec
-};
-
-#[contract]
-pub struct GameContract;
-
-#[contractimpl]
-impl GameContract {
-    // Function to record a game move and update storage
-    pub fn record_move(env: Env, player: Address, move_type: Symbol) {
-        let mut player_moves: Map<Address, Vec<Symbol>> = env.storage().persistent().get("player_moves");
-        let moves = player_moves.get(&player);
-        moves.push(move_type.clone());
-        player_moves.set(player, moves);
-        env.storage().persistent().set("player_moves", &player_moves);
-    }
-
-    // Function to unlock an achievement and update storage
-    pub fn unlock_achievement(env: Env, player: Address, achievement: Symbol) {
-        let mut player_achievements: Map<Address, Vec<Symbol>> = env.storage().persistent().get("player_achievements");
-        let achievements = player_achievements.get(&player);
-        achievements.push(achievement.clone());
-        player_achievements.set(player, achievements);
-        env.storage().persistent().set("player_achievements", &player_achievements);
-    }
-
-}
-```
-
-:::danger
-
-No podemos almacenar todo en el almacenamiento como lo haríamos en una base de datos tradicional. Este enfoque no es rentable ya que implica múltiples operaciones de almacenamiento para cada movimiento de jugador y guarda cada logro en el almacenamiento
-
-:::
-
-#### Optimizando con Eventos
-
-```rust
-#![no_std]
-use soroban_sdk::{
-    contract, contractimpl, log, symbol_short, vec, Address, Env, Symbol,Map, Vec,
-};
-
-#[contract]
-pub struct GameContract;
-
-#[contractimpl]
-impl GameContract {
-    // Function to record a game move and emit an event
-    pub fn record_move(env: Env, player: Address, move_type: Symbol) {
-        // Emit event for the game move
-        env.events().publish(("game_move",), (&player, move_type.clone()));
-    }
-
-    // Function to unlock an achievement and emit an event
-    pub fn unlock_achievement(env: Env, player: Address, achievement: Symbol) {
-        // Emit event for the unlocked achievement
-        env.events().publish(("achievement_unlocked",), (&player, achievement.clone()));
-    }
-}
-```
-
-:::tip
-
-En este enfoque optimizado, utilizamos eventos para almacenar datos que no necesitan ser accedidos con frecuencia. Esto reduce el número de operaciones de almacenamiento y el costo total de gas del contrato.
-
-:::
-
-#### Compensaciones:
-
-El enfoque actual utilizando eventos está efectivamente optimizado para la eficiencia del gas, pero viene con su propio conjunto de compromisos. Veamos diferentes enfoques y sus implicaciones:
-
-##### Enfoque Actual (Usando Eventos)
-
-- Ventajas:
-  - Extremadamente eficiente en gas ya que minimiza las operaciones de almacenamiento
-  - Útil para aplicaciones fuera de la cadena que pueden escuchar y procesar eventos
-  - Ideal para datos que no necesitan ser accedidos frecuentemente en la cadena
-
-- Contras:
-  - Los datos no son directamente accesibles dentro del contrato
-  - Depende de sistemas externos para captar y procesar los datos de eventos
-  - No apto si necesitas consultar o validar movimientos pasados dentro del contrato
-
-##### Almacenamiento del Último Movimiento en Almacenamiento Persistente e Historial en Almacenamiento Temporal
-
-Este enfoque ofrece un equilibrio entre accesibilidad y eficiencia.
-
-- Ventajas:
-  - El movimiento más reciente siempre es accesible en la cadena
-  - Los datos históricos están disponibles dentro de la misma transacción
-  - Más flexible para la lógica del contrato que podría necesitar historia reciente
-
-- Contras:
-  - Costo de gas ligeramente más alto que usar solo eventos
-  - El almacenamiento temporal se borra después de cada transacción, por lo que los datos históricos no son accesibles de manera permanente en la cadena
-
-### 4 Uso de estructuras de datos eficientes
-
-Las matrices asignadas en el heap son lentas y costosas. Prefiere matrices de tamaño fijo o `soroban_sdk::vec!`. Esto es crucial para matrices grandes, ya que superar el tamaño actual de memoria lineal (un múltiplo de 64KB) desencadena `wasm32::memory_grow`, lo cual es altamente intensivo computacionalmente.
-
-##### Ejemplo (Matriz Asignada en Heap) ❎
-
-```rust
-let mut v1 = alloc::vec![];
-```
-
-##### Ejemplo (Matriz de Tamaño Fijo) ✅
-
-```rust
-let mut v2 = [0; 100];
-```
-
-Almacenar muchos elementos en un `Vec` puede ser ineficiente debido a la complejidad de tiempo lineal de las comprobaciones de membresía. Sin embargo, hay algunas alternativas para tener un `Vec` engorroso:
-
-##### Ejemplo (Almacenamiento de Datos Ineficiente) ❎
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, Address, Env, Symbol, Vec};
-
-#[derive(Clone)]
-pub struct PlayerMove {
-    player: Address,
-    move_type: Symbol,
-}
-
-#[derive(Clone)]
-pub struct PlayerAchievement {
-    player: Address,
-    achievement: Symbol,
-}
-
-#[contract]
-pub struct NonOptimalGameContract;
-
-#[contractimpl]
-impl NonOptimalGameContract {
-    // Function to record a move for a specific player
-    pub fn record_move(env: Env, player: Address, move_type: Symbol) {
-        let mut all_moves: Vec<PlayerMove> = env.storage().persistent().get("all_moves").unwrap_or_default();
-        all_moves.push(PlayerMove { player: player.clone(), move_type });
-        env.storage().persistent().set("all_moves", &all_moves);
-    }
-
-    // Function to get moves for a specific player
-    pub fn get_moves(env: Env, player: Address) -> Vec<Symbol> {
-        let all_moves: Vec<PlayerMove> = env.storage().persistent().get("all_moves").unwrap_or_default();
-        all_moves
-            .iter()
-            .filter(|m| m.player == player)
-            .map(|m| m.move_type.clone())
-            .collect()
-    }
-
-    // Function to unlock an achievement for a specific player
-    pub fn unlock_achievement(env: Env, player: Address, achievement: Symbol) {
-        let mut all_achievements: Vec<PlayerAchievement> = env.storage().persistent().get("all_achievements").unwrap_or_default();
-        if !all_achievements.iter().any(|a| a.player == player && a.achievement == achievement) {
-            all_achievements.push(PlayerAchievement { player: player.clone(), achievement });
-            env.storage().persistent().set("all_achievements", &all_achievements);
-        }
-    }
-
-    // Function to get achievements for a specific player
-    pub fn get_achievements(env: Env, player: Address) -> Vec<Symbol> {
-        let all_achievements: Vec<PlayerAchievement> = env.storage().persistent().get("all_achievements").unwrap_or_default();
-        all_achievements
-            .iter()
-            .filter(|a| a.player == player)
-            .map(|a| a.achievement.clone())
-            .collect()
-    }
-}
-```
-
-:::danger Esta versión no óptima tiene varias ineficiencias:
-
-- Un solo Vec para todos los Datos:
-
-  Todos los movimientos y logros se almacenan en Vecs únicos (all_moves y all_achievements), independientemente del jugador. Esto significa que cada operación requiere cargar y guardar el conjunto de datos completo, lo que se vuelve cada vez más costoso a medida que aumenta el número de entradas.
-
-- Operaciones de Búsqueda Lineal:
-
-  Recuperar movimientos o logros para un jugador específico requiere iterar a través del Vec completo, lo cual tiene una complejidad de tiempo O(n). Esto se vuelve muy lento y consume mucho gas a medida que aumenta el número de entradas.
-
-- Almacenamiento de Datos Redundante:
-
-  La dirección del jugador se almacena repetidamente para cada movimiento y logro, lo que lleva a una duplicación innecesaria de datos.
-
-- Comprobación Ineficiente de Logros:
-
-  Antes de agregar un nuevo logro, el código itera a través de todos los logros para verificar duplicados, lo que es una operación O(n).
-
-- Ineficiencia de Gas:
-
-  Cada operación (agregar un movimiento, desbloquear un logro, recuperar datos) requiere cargar y guardar todo el conjunto de datos, lo cual es extremadamente ineficiente en gas.
-
-- Problemas de Escalabilidad:
-
-  A medida que aumenta el número de jugadores y sus acciones, el rendimiento de este contrato se degradará significativamente.
-
-- Falta de Separación de Datos:
-
-  Los movimientos y logros no están claramente separados en la estructura de almacenamiento, lo que dificulta la gestión y potencialmente lleva a confusiones en escenarios más complejos.
-
-:::
-
-##### Alternativa: usar vecs con clave ✅
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, Address, Env, Symbol, Vec};
-
-#[derive(Clone)]
-pub enum DataKey {
-    Moves(Address),
-    Achievements(Address),
-}
-
-#[contract]
-pub struct GameContract;
-
-#[contractimpl]
-impl GameContract {
-    // Function to record a move for a specific player
-    pub fn record_move(env: Env, player: Address, move_type: Symbol) {
-        let key = DataKey::Moves(player.clone());
-        let mut moves: Vec<Symbol> = env.storage().persistent().get(&key).unwrap_or_default();
-        moves.push(move_type.clone());
-        env.storage().persistent().set(&key, &moves);
-    }
-
-    // Function to get moves for a specific player
-    pub fn get_moves(env: Env, player: Address) -> Vec<Symbol> {
-        let key = DataKey::Moves(player);
-        env.storage().persistent().get(&key).unwrap_or_default()
-    }
-
-    // Function to unlock an achievement for a specific player
-    pub fn unlock_achievement(env: Env, player: Address, achievement: Symbol) {
-        let key = DataKey::Achievements(player.clone());
-        let mut achievements: Vec<Symbol> = env.storage().persistent().get(&key).unwrap_or_default();
-        if !achievements.contains(&achievement) {
-            achievements.push(achievement);
-            env.storage().persistent().set(&key, &achievements);
-        }
-    }
-
-    // Function to get achievements for a specific player
-    pub fn get_achievements(env: Env, player: Address) -> Vec<Symbol> {
-        let key = DataKey::Achievements(player);
-        env.storage().persistent().get(&key).unwrap_or_default()
-    }
-}
-```
-
-:::tip
-
-Aquí tienes un desglose de las optimizaciones y beneficios:
-
-- Almacenamiento Específico de Dirección:
-
-  Los movimientos y logros de cada jugador se almacenan por separado, lo que permite una recuperación eficiente de datos específicos del jugador. La enumeración DataKey proporciona una estructura clara para organizar diferentes tipos de datos asociados con las direcciones.
-
-- Acceso Eficiente a los Datos:
-
-  Al usar la enumeración como clave, podemos acceder directamente a los datos de un jugador específico sin necesidad de buscar a través de una estructura de datos más grande. Este enfoque es particularmente eficiente cuando necesitas acceder o actualizar datos con frecuencia para jugadores individuales.
-
-- Estructura de Datos Flexible:
-
-  El uso de `Vec<Symbol>` para movimientos y logros permite un número ilimitado de entradas para cada jugador. Esta estructura es adecuada para almacenar listas ordenadas de movimientos o logros únicos.
-
-- Eficiencia de Gas:
-
-  Al almacenar datos por separado para cada jugador, evitamos tener que cargar y modificar una gran estructura de datos integral para cada operación. Esto puede llevar a ahorros significativos en gas, especialmente a medida que aumenta el número de jugadores y la cantidad de datos.
-
-- Separación Clara de Preocupaciones:
-
-  La enumeración separa claramente diferentes tipos de datos (movimientos vs. logros), haciendo que el código sea más legible y mantenible.
-
-- Fácil Ampliación:
-
-  Si necesitas agregar nuevos tipos de datos asociados con jugadores, puedes ampliar fácilmente la enumeración DataKey sin cambiar la estructura existente.
-
-:::
-
-### 5 Uso de mecanismos `env.storage` apropiados
-
-Hay tres tipos de mecanismos de almacenamiento en Stellar:
-
-#### [`env.storage().persistent()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.persistent)
-
-El almacenamiento persistente se utiliza para almacenar datos que deben conservarse a través de las invocaciones de contratos. Los datos almacenados en el almacenamiento persistente se mantienen entre las invocaciones del contrato y son accesibles para todas las funciones del contrato. El almacenamiento para datos aquí está destinado a permanecer en el ledger indefinidamente hasta que se elimine explícitamente. Las entradas caducadas pueden restaurarse pero no pueden recrearse.
-
-#### Casos de uso
-
-- Datos que requieren persistencia a largo plazo, como saldos de tokens y propiedades de usuarios.
-- Cuando los datos necesitan almacenarse indefinidamente y deben sobrevivir incluso si caducan y necesitan restauración.
-- Ejemplos: Saldos de tokens, propiedades de usuarios.
-
-#### Costo
-
-- Costo más alto en comparación con otros debido a la persistencia a largo plazo.
-
-#### Duración de vida
-
-- Los datos se comportan como si estuvieran almacenados para siempre, pero pueden caducar y ser restaurados.
-
-### [`env.storage().temporary()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.temporary)
-
-El almacenamiento temporal se utiliza para almacenar datos que solo se necesitan durante la invocación actual del contrato. Los datos almacenados en almacenamiento temporal se borran al final de la invocación del contrato y no son accesibles para otras funciones del contrato. El almacenamiento para datos aquí se hace con una vida útil limitada en el ledger. Las entradas se eliminarán después de que termine su vida útil y pueden recrearse con diferentes valores.
-
-#### Casos de uso
-
-- Datos que solo necesitan existir temporalmente, como datos de oráculo, saldos reclamables y ofertas.
-- Cuando los datos solo necesitan existir por un tiempo limitado y pueden recrearse si es necesario.
-- Ejemplos: Datos de oráculo, saldos reclamables, ofertas.
-
-#### Costo
-
-- Más barato que el almacenamiento persistente debido a la vida útil limitada de los datos. (Costo más barato).
-
-#### Duración de vida
-
-- Los datos existen por un período predefinido y luego se eliminan.
-
-### [`env.storage().instance()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html#method.instance)
-
-El almacenamiento aquí se realiza para una pequeña cantidad de datos persistentes estrechamente relacionados con la instancia del contrato. Los datos se cargan desde el ledger cada vez que se carga la instancia del contrato y está limitado por el tamaño de entrada del ledger, que típicamente es del orden de 100 KB serializados.
-
-#### Casos de uso
-
-- Pequeños datos directamente asociados al contrato, como detalles de administrador, configuraciones y tokens. Para datos pequeños, que se utilizan con frecuencia y son parte integral de la instancia del contrato y se benefician de ser cargados cada vez que se utiliza el contrato.
-- Ejemplos: Detalles del administrador del contrato, configuraciones, tokens operados por el contrato.
-
-#### Costo
-
-- Probablemente más barato que almacenar datos por separado en almacenamiento persistente.
-
-#### Duración de vida
-
-- Propiedades de duración de vida similares a las del almacenamiento persistente, pero no aparecen en la huella del ledger.
-
-### 5 Tamaño del contrato
-
-El tamaño del binario `wasm` de tu contrato inteligente influye en el costo de ejecutar tu contrato inteligente en la red Stellar. Los binarios `wasm` más grandes requieren más potencia de procesamiento y memoria para ejecutarse, lo que lleva a costos de gas más altos. Los binarios más grandes también cuestan más gas para desplegar e invocar.
-
-Para optimizar el tamaño de tu binario `wasm`, puedes:
-
-- Eliminar código innecesario
-- Minimizar el uso de dependencias externas
-- Usar herramientas integradas para optimizar el tamaño de tu binario `wasm`
-
-## Otros consejos para optimizar el costo del contrato inteligente:
-
-### 1 Uso de herramientas integradas
-
-Una forma de optimizar el tamaño de tu binario `wasm` es usando `--optimize` al desarrollar tus contratos con el [Stellar CLI](../../../tools/cli/stellar-cli.mdx). Esta flag optimizará el tamaño de tu binario `wasm` eliminando código innecesario y reduciendo el tamaño del binario.
-
-```bash
-stellar contract build --optimize
-```
-
-Otra manera de optimizar tu contrato inteligente es usar el comando `stellar contract invoke` con la flag `--cost`. Este comando te proporcionará un desglose detallado del costo de ejecutar tu contrato inteligente en la red Stellar.
-
-```bash
-stellar contract invoke \
-  --id CC6MWZMG2JPQEENRL7XVICAY5RNMHJ2OORMUHXKRDID6MNGXSSOJZLLF \
-  --source-account alice \
-  --network testnet \
-  --cost \
-  -- \
-  increment
-```
-
-Referencia: [Guías del CLI de Stellar](../../../tools/cli/cookbook/README.mdx).
-
-### 2 Revisión manual del código
-
-Realiza una revisión manual de tu contrato inteligente para identificar áreas donde puedes optimizar el código. Busca bucles redundantes, condiciones y operaciones de almacenamiento que pueden minimizarse o eliminarse.
-
-### 3 Pruebas unitarias con mediciones de gas
-
-Usa pruebas unitarias para medir el costo de gas de las funciones de tu contrato inteligente. Esto te ayudará a identificar funciones que consumen mucho gas y optimizarlas en consecuencia.
-
-Además, usar el método auxiliar rpc [simulateTransaction](../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx) puede darte una idea del costo de gas de las funciones de tu contrato.
-
-### 4 Herramientas de análisis estático
-
-Herramientas como [Clippy](https://doc.rust-lang.org/clippy/) (parte del compilador de Rust) pueden identificar posibles incidencias de rendimiento durante la etapa de compilación. Estas herramientas pueden advertir sobre:
-
-- Asignaciones innecesarias
-- Código redundante
-
-### 5. Reconsiderando ubicaciones de almacenamiento
-
-#### Variables de Estado
-
-- **Costo**: Las variables de estado se almacenan directamente en el almacenamiento de la blockchain. El costo está influenciado principalmente por la cantidad de datos almacenados (medidos en bytes) y la frecuencia de las operaciones de lectura y escritura.
-
-- **Consideraciones**: Escribir datos en variables de estado generalmente implica costos de gas más altos en comparación con la lectura de datos. Las estructuras de datos complejas (por ejemplo, las matrices, mappings) o grandes cantidades de datos aumentan los costos de almacenamiento y el consumo de gas. Stellar cobra tarifas de gas por cada byte de datos almacenados y actualizados, por lo que una gestión eficiente de datos es crucial para la optimización de costos.
-
-#### Registros de Eventos
-
-- **Costo**: Emitir eventos en contratos Rust no conlleva costos directos de almacenamiento ya que los eventos no se guardan permanentemente en la blockchain. En su lugar, se incluyen en los registros de transacciones.
-
-- **Consideraciones**: Emitir eventos consume gas, principalmente debido a los recursos computacionales requeridos para ejecutar la emisión de eventos y la generación de registros. Los eventos son útiles para aplicaciones off-chain y arquitecturas orientadas a eventos, pero no contribuyen directamente a los costos de almacenamiento on-chain.
-
-#### Fuentes de Datos Externas
-
-- **Costo**: Interactuar con fuentes de datos externas como oráculos implica tarifas de transacción para la recuperación y procesamiento de datos.
-
-- **Consideraciones**: Las llamadas a oráculos generan costos de gas para la ejecución del contrato, que pueden variar según la complejidad y frecuencia de la obtención de datos. Los desarrolladores de contratos deben considerar los límites de gas y optimizar las interacciones con oráculos para minimizar costos garantizando una integración de datos confiable.
-
-#### Datos y Constantes Inmutables
-
-- **Costo**: Las constantes y las variables inmutables generan costos de almacenamiento insignificantes ya que generalmente se almacenan como parte del bytecode o metadatos del contrato.
-
-- **Consideraciones**: Las constantes y los datos inmutables son cruciales para la configuración y parametraje del contrato, pero no afectan significativamente los costos de transacción o almacenamiento. Se definen previamente durante el despliegue del contrato y no cambian durante la ejecución del mismo, evitando costos adicionales de gas por actualizaciones de almacenamiento.
-
-#### Almacenamiento Off-Chain y IPFS
-
-- **Costo**: Almacenar datos fuera de la cadena usando soluciones como IPFS evita costos directos de almacenamiento on-chain, pero implica costos por la recuperación de datos y el uso de la red IPFS.
-
-- **Consideraciones**: Los contratos almacenan solo el hash o referencia a los datos fuera de la cadena on-chain, minimizando los costos de almacenamiento on-chain. Pueden aplicarse costos de gas al recuperar y procesar datos off-chain, dependiendo de la complejidad y frecuencia de acceso. Las soluciones de almacenamiento off-chain ofrecen escalabilidad y flexibilidad pero requieren una consideración cuidadosa de las tarifas de red y la disponibilidad de datos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/cost-analysis.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/cost-analysis.mdx
deleted file mode 100644
index f841ad948e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/fees/cost-analysis.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Analizar el costo y la eficiencia del contrato
-hide_table_of_contents: true
-draft: true
----
-
-Consulta [incidencia #552](https://github.com/stellar/soroban-docs/issues/552) para más contexto
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/README.mdx
deleted file mode 100644
index 82f17b0dc2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Billetera Freighter
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 70
----
-
-[Freighter](https://www.freighter.app/) es una billetera de extensión para el navegador proporcionada por la Stellar Development Foundation. Proporciona a los usuarios una forma de interactuar con los tokens de Soroban directamente desde el navegador web.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/connect-testnet.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/connect-testnet.mdx
deleted file mode 100644
index eee3fa8c2d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/connect-testnet.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Conectar a la Testnet
-hide_table_of_contents: true
-description: Crear una cuenta Stellar en Testnet con Freighter
----
-
-1. Instala la [extensión del navegador](https://www.freighter.app) Freighter.
-
-2. Crea un keypair o importa una cuenta existente utilizando una frase mnemotécnica para completar la configuración.
-
-3. A continuación, cambia a Testnet. Testnet está disponible en el menú desplegable de redes.
-
-4. Si tu cuenta no existe en la red seleccionada, Freighter te pedirá que la financies utilizando Friendbot. Alternativamente, puedes hacerlo en el [Stellar Lab](https://lab.stellar.org/account/create).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/enable-soroban-tokens.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/enable-soroban-tokens.mdx
deleted file mode 100644
index f829e9cc2e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/enable-soroban-tokens.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Habilitar tokens Soroban
-hide_table_of_contents: true
-description: Añadir tokens de contrato inteligente a tu billetera Freighter
----
-
-Con una cuenta Stellar financiada, ahora puedes añadir tokens Soroban a tu billetera Freighter.
-
-1. En la pantalla de la cuenta de Freighter, haz clic en este botón `Manage assets` en el menú desplegable de opciones `...` en la parte superior izquierda de la pantalla.
-
-2. Ahora verás un botón para `Add an asset` en la parte inferior de la pantalla. Haz clic en este botón `Add an asset`.
-
-3. En la siguiente pantalla, ingresa el ID del token que deseas agregar a Freighter y haz clic en el botón `Add` cuando aparezca. Haz clic en `Confirm` para agregarlo a tu wallet.
-
-4. Ahora verás el saldo de tu token en la página de la cuenta de Freighter. Al hacer clic en el saldo, se mostrará un historial de pagos enviados usando este token.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/integrate-freighter-react.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/integrate-freighter-react.mdx
deleted file mode 100644
index 3b330de33e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/integrate-freighter-react.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Integrar Freighter con una dapp de React
-description: Integrar la billetera Freighter en tus dapps de React
----
-
-Las billeteras son una parte esencial de cualquier dapp. Permiten a los usuarios interactuar con la blockchain y firmar transacciones. En esta sección, aprenderás cómo integrar la billetera Freighter en tus dapps de React.
-
-### Componente WalletData
-
-En la [dapp de crowdfund de ejemplo](https://github.com/stellar/soroban-example-dapp), el componente `WalletData` juega un papel clave en la integración de la billetera. Desglosaremos el código y entenderemos su funcionalidad:
-
-```tsx title="/components/moleculres/wallet-data/index.tsx"
-import React from "react";
-import { useAccount, useIsMounted } from "../../../hooks";
-import { ConnectButton } from "../../atoms";
-import styles from "./style.module.css";
-
-export function WalletData() {
-  const mounted = useIsMounted();
-  const account = useAccount();
-
-  return (
-    <>
-      {mounted && account ? (
-        <div className={styles.displayData}>
-          <div className={styles.card}>{account.displayName}</div>
-        </div>
-      ) : (
-        <ConnectButton label="Connect Wallet" />
-      )}
-    </>
-  );
-}
-```
-
-Aquí tienes un desglose del código:
-
-- La variable `mounted` se obtiene usando el [`useIsMounted` hook](https://github.com/stellar/soroban-example-dapp/blob/main/hooks/useIsMounted.ts), indicando si el componente está actualmente montado o no.
-- El [`useAccount` hook](https://github.com/stellar/soroban-example-dapp/blob/main/hooks/useAccount.ts) se utiliza para obtener los datos de la cuenta del usuario, y la propiedad `data` se desestructura del resultado.
-- Se utiliza renderización condicional para mostrar contenido diferente según el estado de montaje del componente y la disponibilidad de datos de cuenta.
-- Si el componente está montado y los datos de la cuenta están disponibles, se muestra la información de la billetera del usuario. Esto incluye el nombre de usuario de la cuenta.
-- Si el componente no está montado o los datos de la cuenta no están disponibles, se renderiza un componente [`ConnectButton`](https://github.com/stellar/soroban-example-dapp/blob/main/components/atoms/connect-button/index.tsx), permitiendo al usuario conectarse con Freighter.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/prompt-to-sign-tx.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/prompt-to-sign-tx.mdx
deleted file mode 100644
index aed79beb6f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/prompt-to-sign-tx.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Indicar a Freighter que firme transacciones como desarrollador de dapp JS
-hide_table_of_contents: true
-description: Firmar transacciones de contratos inteligentes utilizando la extensión del navegador Freighter
----
-
-Si estás desarrollando un dapp JS, firma fácilmente transacciones Soroban utilizando la [extensión del navegador Freighter](https://www.freighter.app/) y su correspondiente biblioteca cliente [@stellar/freighter-api](https://www.npmjs.com/package/@stellar/freighter-api):
-
-1. Sigue las instrucciones de configuración para [conectar al Testnet](./connect-testnet.mdx), si es necesario durante el desarrollo.
-
-2. Ahora, puedes utilizar el `signTransaction` [método](https://docs.freighter.app/docs/guide/usingFreighterWebApp) de `@stellar/freighter-api` en tu dapp para firmar XDRs Soroban usando la cuenta en Freighter.
-
-3. Al llamar a `signTransaction`, Freighter se abrirá y pedirá al usuario que firme la transacción. Al aprobar la transacción, se devolverá un objeto que contiene el XDR firmado a la dapp que lo solicitó.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/send-token-payments.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/send-token-payments.mdx
deleted file mode 100644
index 5c4a354384..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/send-token-payments.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Enviar pagos de tokens Soroban
-hide_table_of_contents: true
-description: Enviar un pago de token de contrato inteligente directamente desde Freighter
----
-
-Una vez que hayas agregado un token Soroban a tu billetera Freighter, ahora puedes enviar un pago de ese token directamente desde Freighter.
-
-1. En la pantalla de cuenta de Freighter, haz clic en el icono `Send` en la parte superior de la pantalla.
-
-2. Introduce una clave pública del destinatario. Haz clic en `Continuar`.
-
-3. Selecciona tu token de la lista de activos en la parte inferior de la pantalla e introduce una cantidad de tokens. Haz clic en `Continuar`.
-
-4. Introduce un memo (opcional). Haz clic en `Revisar Envío`.
-
-5. Revisa los detalles de tu pago. Haz clic en `Enviar`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/sign-auth-entries.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/sign-auth-entries.mdx
deleted file mode 100644
index 178d8edfba..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/sign-auth-entries.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Firmar entradas de autorización
-hide_table_of_contents: true
-description: Usa la API de Freighter para firmar una entrada de autorización
----
-
-Para aprovechar la [autorización de contratos](../../../learn/fundamentals/contract-development/authorization.mdx), puedes usar la API de Freighter para firmar una entrada de autorización. Un buen ejemplo de cómo funciona la firma de una entrada de autorización se puede encontrar en el [`authorizeEntry` helper de `stellar-sdk`](https://github.com/stellar/js-stellar-base/blob/e3d6fc3351e7d242b374c7c6057668366364a279/src/auth.js#L97).
-
-Como en el helper, puedes construir un [`HashIdPreimageSorobanAuthorization`](https://github.com/stellar/js-stellar-base/blob/a9567e5843760bfb6a8b786592046aee4c9d38b2/types/next.d.ts#L6895) y usar la representación xdr de esa estructura para llamar `await freighterApi.signAuthEntry(preimageXdr)`. Esta llamada devolverá un `Buffer` del hash firmado del `HashIdPreimageSorobanAuthorization` pasado, que luego puede ser utilizado para enviar a la red durante un flujo de trabajo de autorización de contrato.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/sign-soroban-xdrs.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/sign-soroban-xdrs.mdx
deleted file mode 100644
index c7b7b8d1ed..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/freighter/sign-soroban-xdrs.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Firmar Soroban XDRs
-hide_table_of_contents: true
-description: Firmar XDRs de contratos inteligentes utilizando dapps integradas con Freighter
----
-
-Con una cuenta de Testnet financiada, ahora puedes firmar Soroban XDRs utilizando dApps que están integradas con Freighter. Un ejemplo de una dApp integrada es el [Laboratorio](https://lab.stellar.org/transaction/sign?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;) de Stellar.
-
-1. En el firmador de transacciones del Laboratorio, introduce un Soroban XDR en el campo del formulario.
-
-2. Haz clic en `Firmar con Freighter`.
-
-3. Freighter se abrirá con los detalles del XDR. Haz clic en `Aprobar` para firmar o `Rechazar` para descartar sin una firma.
-
-4. Si se aprueba, Freighter transmitirá un XDR firmado de vuelta al Laboratorio.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/README.mdx
deleted file mode 100644
index 16b34f213c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: RPC
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 75
----
-
-Usar e interactuar con el Stellar RPC es una parte importante del ciclo de vida del desarrollo de contratos inteligentes. Lee más sobre el RPC en nuestra [documentación de RPC](../../../data/apis/rpc/README.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/generate-ledger-keys-python.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/generate-ledger-keys-python.mdx
deleted file mode 100644
index ecf61caafc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/generate-ledger-keys-python.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Generar parámetros de clave de ledger con una clave de símbolo utilizando el SDK de Python
-hide_table_of_contents: true
-description: Generar parámetros de clave de ledger con una clave de símbolo utilizando el SDK de Python
----
-
-En el [contrato de ejemplo `increment`] se almacena un valor entero en una entrada de ledger que está identificada por una clave con el símbolo `COUNTER`. El valor de esta clave de ledger puede derivarse utilizando los siguientes fragmentos de código.
-
-```python
-from stellar_sdk import xdr, scval, Address
-
-def get_ledger_key_symbol(contract_id: str, symbol_text: str) -> str:
-    ledger_key = xdr.LedgerKey(
-        type=xdr.LedgerEntryType.CONTRACT_DATA,
-        contract_data=xdr.LedgerKeyContractData(
-            contract=Address(contract_id).to_xdr_sc_address(),
-            key=scval.to_symbol(symbol_text),
-            durability=xdr.ContractDataDurability.PERSISTENT
-        ),
-    )
-    return ledger_key.to_xdr()
-
-print(
-    get_ledger_key_symbol(
-        "CCPYZFKEAXHHS5VVW5J45TOU7S2EODJ7TZNJIA5LKDVL3PESCES6FNCI",
-        "COUNTER"
-    )
-)
-```
-
-[Contrato de ejemplo `increment`]: ../../smart-contracts/getting-started/storing-data.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/retrieve-contract-code-js.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/retrieve-contract-code-js.mdx
deleted file mode 100644
index f4eaa5a0ec..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/retrieve-contract-code-js.mdx
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: Recuperar una entrada de ledger de código de contrato utilizando el SDK de JavaScript
-hide_table_of_contents: true
-description: Recuperar una entrada de ledger de código de contrato utilizando el SDK de JavaScript
----
-
-Cuando despliegas un contrato, primero el código se "instala" (es decir, se sube a la blockchain). Esto crea una `LedgerEntry` que contiene el código en bytes Wasm, que se identifica de manera única por su hash (es decir, el hash del código subido en sí). Luego, cuando el contrato está "desplegado," creamos una `LedgerEntry` con una referencia al hash de ese código. Por lo tanto, obtener el código del contrato es un proceso de dos pasos:
-
-1. Primero, buscamos el contrato en sí, para ver a qué hash de código está haciendo referencia.
-2. Luego, podemos buscar el código en bytes Wasm sin procesar utilizando ese hash.
-
-```javascript
-import { Contract } from "@stellar/stellar-sdk";
-
-function getLedgerKeyContractCode(contractId) {
-  const instance = new Contract(contractId).getFootprint();
-  return instance.toXDR("base64");
-}
-
-console.log(
-  getLedgerKeyContractCode(
-    "CCPYZFKEAXHHS5VVW5J45TOU7S2EODJ7TZNJIA5LKDVL3PESCES6FNCI",
-  ),
-);
-// OUTPUT: AAAABgAAAAGfjJVEBc55drW3U87N1Py0Rw0/nlqUA6tQ6r28khEl4gAAABQAAAAB
-```
-
-Luego tomamos nuestra salida de esta función y la usamos como el elemento en el parámetro de array `keys` en nuestra llamada al método `getLedgerEntries`.
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 8675309,
-  "method": "getLedgerEntries",
-  "params": {
-    "keys": ["AAAABgAAAAGfjJVEBc55drW3U87N1Py0Rw0/nlqUA6tQ6r28khEl4gAAABQAAAAB"]
-  }
-}
-```
-
-Y la respuesta que obtenemos contiene los datos de `LedgerEntryData` que pueden ser utilizados para encontrar el `hash` que debemos usar para solicitar el código en bytes Wasm. Este hash es el `LedgerKey` que ha sido asociado con el código de contrato desplegado.
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 8675309,
-  "result": {
-    "entries": [
-      {
-        "key": "AAAABgAAAAGfjJVEBc55drW3U87N1Py0Rw0/nlqUA6tQ6r28khEl4gAAABQAAAAB",
-        "xdr": "AAAABgAAAAAAAAABn4yVRAXOeXa1t1POzdT8tEcNP55alAOrUOq9vJIRJeIAAAAUAAAAAQAAABMAAAAA5DNtbckOGVRsNVb8L7X/lIhAOy2o5G6GkLKXvc7W8foAAAAA",
-        "lastModifiedLedgerSeq": 261603
-      }
-    ],
-    "latestLedger": 262322
-  }
-}
-```
-
-Ahora toma el campo `xdr` del objeto `result` de la respuesta anterior y crea un `LedgerKey` a partir del hash contenido dentro.
-
-```javascript
-import { xdr } from "@stellar/stellar-sdk";
-
-function getLedgerKeyWasmId(contractCodeLedgerEntryData) {
-  const entry = xdr.LedgerEntryData.fromXDR(
-    contractCodeLedgerEntryData,
-    "base64",
-  );
-
-  const wasmHash = entry
-    .contractData()
-    .val()
-    .instance()
-    .executable()
-    .wasmHash();
-
-  let ledgerKey = xdr.LedgerKey.contractCode(
-    new xdr.LedgerKeyContractCode({
-      hash: wasmHash,
-    }),
-  );
-
-  return ledgerKey.toXDR("base64");
-}
-
-console.log(
-  getLedgerKeyWasmId(
-    "AAAABgAAAAAAAAABn4yVRAXOeXa1t1POzdT8tEcNP55alAOrUOq9vJIRJeIAAAAUAAAAAQAAABMAAAAA5DNtbckOGVRsNVb8L7X/lIhAOy2o5G6GkLKXvc7W8foAAAAA",
-  ),
-);
-// OUTPUT: AAAAB+QzbW3JDhlUbDVW/C+1/5SIQDstqORuhpCyl73O1vH6
-```
-
-Ahora, finalmente tenemos un `LedgerKey` que corresponde al código en bytes Wasm que ha sido desplegado bajo el `ContractId` con el que comenzamos hace tanto tiempo. Este `LedgerKey` puede ser utilizado en una solicitud final al punto final Stellar-RPC.
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 8675309,
-  "method": "getLedgerEntries",
-  "params": {
-    "keys": ["AAAAB+QzbW3JDhlUbDVW/C+1/5SIQDstqORuhpCyl73O1vH6"]
-  }
-}
-```
-
-Y la respuesta que obtenemos contiene (aún más) `LedgerEntryData` que podemos decodificar y analizar para obtener el código de contrato desplegado y real. Dejaremos ese ejercicio en tus manos. Puedes consultar lo que contiene utilizando la ["Ver XDR" página del Stellar Lab](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;).
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 8675309,
-  "result": {
-    "entries": [
-      {
-        "key": "AAAAB+QzbW3JDhlUbDVW/C+1/5SIQDstqORuhpCyl73O1vH6",
-        "xdr": "AAAABwAAAADkM21tyQ4ZVGw1Vvwvtf+UiEA7LajkboaQspe9ztbx+gAAAkgAYXNtAQAAAAEVBGACfn4BfmADfn5+AX5gAAF+YAAAAhkEAWwBMAAAAWwBMQAAAWwBXwABAWwBOAAAAwUEAgMDAwUDAQAQBhkDfwFBgIDAAAt/AEGAgMAAC38AQYCAwAALBzUFBm1lbW9yeQIACWluY3JlbWVudAAEAV8ABwpfX2RhdGFfZW5kAwELX19oZWFwX2Jhc2UDAgqnAQSSAQIBfwF+QQAhAAJAAkACQEKOutCvhtQ5QgEQgICAgABCAVINAEKOutCvhtQ5QgEQgYCAgAAiAUL/AYNCBFINASABQiCIpyEACyAAQQFqIgBFDQFCjrrQr4bUOSAArUIghkIEhCIBQgEQgoCAgAAaQoSAgICgBkKEgICAwAwQg4CAgAAaIAEPCwAACxCFgICAAAALCQAQhoCAgAAACwQAAAALAgALAHMOY29udHJhY3RzcGVjdjAAAAAAAAAAQEluY3JlbWVudCBpbmNyZW1lbnRzIGFuIGludGVybmFsIGNvdW50ZXIsIGFuZCByZXR1cm5zIHRoZSB2YWx1ZS4AAAAJaW5jcmVtZW50AAAAAAAAAAAAAAEAAAAEAB4RY29udHJhY3RlbnZtZXRhdjAAAAAAAAAAFAAAAAAAbw5jb250cmFjdG1ldGF2MAAAAAAAAAAFcnN2ZXIAAAAAAAAGMS43Ni4wAAAAAAAAAAAACHJzc2RrdmVyAAAALzIwLjMuMSNiYTA0NWE1N2FmOTcxZmM4M2U0NzU3NDZiNTlhNTAzYjdlZjQxNjQ5AA==",
-        "lastModifiedLedgerSeq": 368441,
-        "liveUntilLedgerSeq": 2442040
-      }
-    ],
-    "latestLedger": 370940
-  }
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/retrieve-contract-code-python.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/retrieve-contract-code-python.mdx
deleted file mode 100644
index 06fefc3557..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/retrieve-contract-code-python.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: Recuperar una entrada del libro de contabilidad del código del contrato usando el SDK de Python
-hide_table_of_contents: true
-description: Recuperar una entrada del libro de contabilidad del código del contrato usando el SDK de Python
----
-
-Cuando despliegas un contrato, primero el código es "instalado" (es decir, se carga en la blockchain). Esto crea una `LedgerEntry` que contiene el byte-código Wasm, que se identifica de manera única por su hash (es decir, el hash del código cargado en sí). Luego, cuando el contrato es "desplegado", creamos una `LedgerEntry` con una referencia al hash de ese código. Así que obtener el código del contrato es un proceso de dos pasos:
-
-1. Primero, buscamos el contrato en sí, para ver qué hash de código está referenciando.
-2. Luego, podemos buscar el byte-código Wasm en bruto usando ese hash.
-
-```python
-from stellar_sdk import xdr, Address
-
-def get_ledger_key_contract_code(contract_id: str) -> str:
-    ledger_key = xdr.LedgerKey(
-        type=xdr.LedgerEntryType.CONTRACT_DATA,
-        contract_data=xdr.LedgerKeyContractData(
-            contract=Address(contract_id).to_xdr_sc_address(),
-            key=xdr.SCVal(xdr.SCValType.SCV_LEDGER_KEY_CONTRACT_INSTANCE),
-            durability=xdr.ContractDataDurability.PERSISTENT
-        )
-    )
-    return ledger_key.to_xdr()
-
-print(
-    get_ledger_key_contract_code(
-        "CCPYZFKEAXHHS5VVW5J45TOU7S2EODJ7TZNJIA5LKDVL3PESCES6FNCI"
-    )
-)
-# OUTPUT: AAAABgAAAAGfjJVEBc55drW3U87N1Py0Rw0/nlqUA6tQ6r28khEl4gAAABQAAAAB
-```
-
-Luego tomamos nuestra salida de esta función y la usamos como el elemento en el parámetro del arreglo `keys` en nuestra llamada al método `getLedgerEntries`.
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 8675309,
-  "method": "getLedgerEntries",
-  "params": {
-    "keys": ["AAAABgAAAAGfjJVEBc55drW3U87N1Py0Rw0/nlqUA6tQ6r28khEl4gAAABQAAAAB"]
-  }
-}
-```
-
-Y la respuesta que recibimos contiene el `LedgerEntryData` que se puede usar para encontrar el `hash` que debemos usar para solicitar el byte-código Wasm. Este hash es el `LedgerKey` que se ha asociado con el código del contrato desplegado.
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 8675309,
-  "result": {
-    "entries": [
-      {
-        "key": "AAAABgAAAAGfjJVEBc55drW3U87N1Py0Rw0/nlqUA6tQ6r28khEl4gAAABQAAAAB",
-        "xdr": "AAAABgAAAAAAAAABn4yVRAXOeXa1t1POzdT8tEcNP55alAOrUOq9vJIRJeIAAAAUAAAAAQAAABMAAAAA5DNtbckOGVRsNVb8L7X/lIhAOy2o5G6GkLKXvc7W8foAAAAA",
-        "lastModifiedLedgerSeq": 261603
-      }
-    ],
-    "latestLedger": 262322
-  }
-}
-```
-
-Ahora toma el campo `xdr` del objeto `result` de la respuesta anterior y crea un `LedgerKey` a partir del hash contenido dentro.
-
-```python
-from stellar_sdk import xdr
-
-def get_ledger_key_wasm_id(contract_code_ledger_entry_data: str) -> str:
-    # First, we dig the wasm_id hash out of the xdr we received from RPC
-    contract_code_wasm_hash = xdr.LedgerEntryData.from_xdr(
-        contract_code_ledger_entry_data
-    ).contract_data.val.instance.executable.wasm_hash
-    # Now, we can create the `LedgerKey` as we've done in previous examples
-    ledger_key = xdr.LedgerKey(
-        type=xdr.LedgerEntryType.CONTRACT_CODE,
-        contract_code=xdr.LedgerKeyContractCode(
-            hash=contract_code_wasm_hash
-        ),
-    )
-    return ledger_key.to_xdr()
-
-print(
-    get_ledger_key_wasm_id(
-        "AAAABgAAAAAAAAABn4yVRAXOeXa1t1POzdT8tEcNP55alAOrUOq9vJIRJeIAAAAUAAAAAQAAABMAAAAA5DNtbckOGVRsNVb8L7X/lIhAOy2o5G6GkLKXvc7W8foAAAAA"
-    )
-)
-# OUTPUT: AAAAB+QzbW3JDhlUbDVW/C+1/5SIQDstqORuhpCyl73O1vH6
-```
-
-Ahora, finalmente tenemos un `LedgerKey` que corresponde al byte-código Wasm que ha sido desplegado bajo el `ContractId` con el que comenzamos hace tanto tiempo. Este `LedgerKey` se puede usar en una solicitud final al punto final Stellar-RPC.
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 8675309,
-  "method": "getLedgerEntries",
-  "params": {
-    "keys": ["AAAAB+QzbW3JDhlUbDVW/C+1/5SIQDstqORuhpCyl73O1vH6"]
-  }
-}
-```
-
-Y la respuesta que obtenemos contiene (aún más) `LedgerEntryData` que podemos decodificar y analizar para obtener el byte-código del contrato desplegado y real. Dejaremos ese ejercicio en tus manos. Puedes ver lo que contiene usando la ["Página Ver XDR" del Stellar Lab](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;).
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 8675309,
-  "result": {
-    "entries": [
-      {
-        "key": "AAAAB+QzbW3JDhlUbDVW/C+1/5SIQDstqORuhpCyl73O1vH6",
-        "xdr": "AAAABwAAAADkM21tyQ4ZVGw1Vvwvtf+UiEA7LajkboaQspe9ztbx+gAAAkgAYXNtAQAAAAEVBGACfn4BfmADfn5+AX5gAAF+YAAAAhkEAWwBMAAAAWwBMQAAAWwBXwABAWwBOAAAAwUEAgMDAwUDAQAQBhkDfwFBgIDAAAt/AEGAgMAAC38AQYCAwAALBzUFBm1lbW9yeQIACWluY3JlbWVudAAEAV8ABwpfX2RhdGFfZW5kAwELX19oZWFwX2Jhc2UDAgqnAQSSAQIBfwF+QQAhAAJAAkACQEKOutCvhtQ5QgEQgICAgABCAVINAEKOutCvhtQ5QgEQgYCAgAAiAUL/AYNCBFINASABQiCIpyEACyAAQQFqIgBFDQFCjrrQr4bUOSAArUIghkIEhCIBQgEQgoCAgAAaQoSAgICgBkKEgICAwAwQg4CAgAAaIAEPCwAACxCFgICAAAALCQAQhoCAgAAACwQAAAALAgALAHMOY29udHJhY3RzcGVjdjAAAAAAAAAAQEluY3JlbWVudCBpbmNyZW1lbnRzIGFuIGludGVybmFsIGNvdW50ZXIsIGFuZCByZXR1cm5zIHRoZSB2YWx1ZS4AAAAJaW5jcmVtZW50AAAAAAAAAAAAAAEAAAAEAB4RY29udHJhY3RlbnZtZXRhdjAAAAAAAAAAFAAAAAAAbw5jb250cmFjdG1ldGF2MAAAAAAAAAAFcnN2ZXIAAAAAAAAGMS43Ni4wAAAAAAAAAAAACHJzc2RrdmVyAAAALzIwLjMuMSNiYTA0NWE1N2FmOTcxZmM4M2U0NzU3NDZiNTlhNTAzYjdlZjQxNjQ5AA==",
-        "lastModifiedLedgerSeq": 368441,
-        "liveUntilLedgerSeq": 2442040
-      }
-    ],
-    "latestLedger": 370940
-  }
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/self-deploy-rpc.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/self-deploy-rpc.mdx
deleted file mode 100644
index ccab204095..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/self-deploy-rpc.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Autodesplegar y usar tu propia instancia RPC
-hide_table_of_contents: true
-draft: true
----
-
-El texto de marcador de posición va aquí.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/use-public-rpc.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/use-public-rpc.mdx
deleted file mode 100644
index 460ebfea3c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/rpc/use-public-rpc.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Hacer uso de una instancia RPC pública
-hide_table_of_contents: true
-draft: true
----
-
-El texto de marcador de posición va aquí.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/README.mdx
deleted file mode 100644
index 37d2b2d999..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Almacenamiento de Contratos
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 30
----
-
-El almacenamiento de contratos inteligentes está disponible para acomodar de manera asequible una amplia gama de usos. Obtén más información en la [sección de archivado de estado](../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/choose-type.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/choose-type.mdx
deleted file mode 100644
index 1ed185bc35..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/choose-type.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Elige el tipo de almacenamiento adecuado para tu caso de uso
-hide_table_of_contents: true
-draft: true
----
-
-El texto de marcador de posición va aquí.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/choosing-the-right-storage.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/choosing-the-right-storage.mdx
deleted file mode 100644
index 48b09aee77..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/choosing-the-right-storage.mdx
+++ /dev/null
@@ -1,223 +0,0 @@
----
-title: Cómo elegir el tipo de almacenamiento adecuado para tu caso de uso
-hide_table_of_contents: true
-description: Esta guía te lleva a elegir el tipo de almacenamiento más adecuado para tu caso de uso y cómo implementarlo
----
-
-## Tipos de almacenamiento
-
-Los contratos inteligentes pueden persistir datos en el ledger Stellar utilizando la interfaz de almacenamiento (`env.storage()` en el SDK de Soroban). Hay tres tipos de almacenamiento disponibles en la red Stellar:
-
-| Tipo de almacenamiento | API del SDK                  | Costo         | Comportamiento cuando caduca el TTL | Número de claves                            |
-| ---------------------- | ---------------------------- | ------------- | ----------------------------------- | ------------------------------------------- |
-| Persistente            | `env.storage().persistent()` | Más caro      | Los datos se archivan               | Ilimitado                                   |
-| Temporal               | `env.storage().temporary()`  | Menos costoso | Los datos se eliminan para siempre  | Ilimitado                                   |
-| Instancia              | `env.storage().instance()`   | Más costoso   | Los datos se archivan               | Limitado por el límite de tamaño de entrada |
-
-Cada tipo de almacenamiento puede considerarse como un mapa de claves arbitrarias a valores arbitrarios. Los datos se almacenan físicamente en el ledger Stellar.
-
-Cada 'mapa' de almacenamiento es completamente independiente de cada otro 'mapa' de almacenamiento. Es posible almacenar diferentes datos para la misma clave en cada almacenamiento. Por ejemplo, en almacenamiento temporal, la clave `123_u32` puede tener un valor de `100_u32`, mientras que en almacenamiento persistente la misma clave `123_u32` puede tener un valor de `abcd`.
-
-Todos los tipos de almacenamiento tienen casi exactamente la misma funcionalidad, además de las diferencias destacadas en la tabla anterior, específicamente el costo, el comportamiento cuando caduca el TTL y el límite para el número de claves almacenadas por contrato.
-
-### Una nota sobre el TTL
-
-Si te preguntas qué significa 'TTL', aquí hay una breve introducción sobre los TTL y el archivo de estado en Stellar.
-
-El archivo de estado es un mecanismo especial definido por el protocolo Stellar que garantiza que el tamaño del estado del ledger activo no crezca indefinidamente. En términos simples, cada entrada de datos de contrato almacenada, así como la entrada de código de contrato (Wasm), tiene asignado un cierto 'tiempo de vida' (TTL). El TTL es solo un número de ledgers por el cual la entrada se considera 'activa', y después de ese número de ledgers, se considera que el TTL ha caducado y, por lo tanto, ya no está activa. Diferentes tipos de almacenamiento manejan la expiración del TTL de manera diferente: los datos se moverán a los archivos ('fríos', almacenamiento off-chain) o se eliminarán automáticamente del ledger (en caso de almacenamiento temporal). Los datos almacenados en el archivo pueden ser restaurados on-chain más tarde y, por lo tanto, volverse activos nuevamente.
-
-El TTL también puede extenderse tantas veces como sea necesario, por una tarifa.
-
-Lee más sobre el archivo de estados [aquí](../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
-
-## Almacenamiento persistente
-
-Este tipo de almacenamiento se utiliza para almacenar datos en la red durante un período de tiempo indefinido.
-
-Para el almacenamiento persistente, cuando el TTL alcanza cero, la entrada se mueve al almacenamiento archivado. Luego, se puede restaurar cuando sea necesario utilizando la operación `RestoreFootprintOp`.
-
-El almacenamiento persistente es el tipo de almacenamiento predeterminado en términos de casos de uso. El almacenamiento de instancia y temporal solo son útiles para los casos de uso específicos descritos en las secciones respectivas. El protocolo Stellar también utiliza almacenamiento persistente para almacenar los contratos y sus ejecutables en Wasm, de modo que siempre puedan ser accedidos o restaurados.
-
-Ejemplos de datos que pueden ser almacenados en almacenamiento persistente incluyen saldos de usuario, metadatos de token, decisiones de votación y gobernanza, y todos los datos que deben permanecer accesibles para siempre o hasta que se eliminen explícitamente.
-
-Veamos un contrato para un sistema de puntos de lealtad donde los usuarios pueden acumular puntos y canjearlos por recompensas. El saldo de puntos de cada usuario se almacenará en almacenamiento persistente.
-
-```rust
-use soroban_sdk::{contractimpl, contracttype, Address, Env};
-
-#[contracttype]
-pub enum DataKey {
-    Points(Address),
-}
-
-#[contract]
-pub struct LoyaltyPointsContract;
-
-#[contractimpl]
-impl LoyaltyPointsContract {
-    // This function redeems points according to the user's balance
-    pub fn redeem_points(env: Env, user: Address, points: u64) -> bool {
-        user.require_auth();
-        let key = DataKey::Points(user.clone());
-        let current_points: u64 = env.storage().persistent().get(&key).unwrap_or(0);
-
-        if current_points >= points {
-            let new_points = current_points - points;
-            env.storage().persistent().set(&key, &new_points);
-            true
-        } else {
-            false
-        }
-    }
-
-    // This function retrieves the user's points balance
-    pub fn get_points(env: Env, user: Address) -> u64 {
-        let key = DataKey::Points(user);
-        env.storage().persistent().get(&key).unwrap_or(0)
-    }
-
-    // ...
-    // This example omits functions that add points to the users, see the next
-    // section for these.
-}
-```
-
-## Almacenamiento de instancia
-
-El almacenamiento de instancia es un mapa pequeño y de tamaño limitado adjunto a la instancia del contrato. Se almacena físicamente en la misma entrada de ledger que el contrato mismo y comparte el TTL con él.
-
-Al igual que el almacenamiento persistente, el almacenamiento de instancia almacena datos de forma permanente. Sin embargo, tiene algunos pros y contras en comparación con él:
-
-- Pro: Data TTL is tied to the contract instance, thus making state archival behavior much easier
-- Pro/Con: Data is loaded automatically together with the contract, thus reducing the transaction footprint size, but increasing the number of bytes read every time the contract is loaded (_usually_ this still will result in a lower fee)
-- Con: El tamaño total de todas las claves y valores en el almacenamiento de instancia está limitado por el límite de tamaño de entrada del ledger. Consulta el valor actual del límite [aquí](../../../networks/resource-limits-fees.mdx). El número total de claves admitidas está en el orden de decenas a cientos dependiendo del tamaño de los datos subyacentes y el límite actual de la red. Ten en cuenta que el límite de la red nunca puede disminuir, por lo que la instancia nunca puede volverse no válida.
-
-El almacenamiento de instancia es más adecuado para datos que tienen un límite de tamaño bien conocido y que son muy pequeños o son necesarios para cada invocación del contrato. Por ejemplo, la entrada del administrador del contrato (pequeña y debería mantenerse junto con la instancia del contrato), o un par de tokens para un fondo de liquidez (necesario para casi toda operación en un fondo de liquidez).
-
-Veamos funciones adicionales para el contrato de puntos de lealtad de la sección anterior, específicamente las funciones que definen al administrador del contrato y agregan puntos a los usuarios:
-
-```rust
-use soroban_sdk::{contractimpl, Address,  Env};
-
-#[contracttype]
-pub enum DataKey {
-    Points(Address),
-    Admin
-}
-
-#[contractimpl]
-impl LoyaltyPointsContract {
-    // Initialize a contract with the administrator address.
-    // Note, that since protocol 22 this should be `__constructor` instead.
-    pub fn init(env: Env, admin: Address) {
-        env.storage().instance().set(&DataKey::Admin, &admin);
-    }
-
-    pub fn add_points(env: Env, user: Address, points: u64) {
-        // Load the admin from the instance storage and make sure it has
-        // authorized this invocation.
-        let admin: Address =
-             env.storage().instance().get(&DataKey::Admin).unwrap();
-        admin.require_auth();
-
-        let key = DataKey::Points(user.clone());
-        let current_points: u64 = env.storage().persistent().get(&key).unwrap_or(0);
-
-        let new_points = current_points + points;
-        env.storage().persistent().set(&key, &new_points);
-    }
-}
-```
-
-## Almacenamiento temporal
-
-Como indica el nombre, el almacenamiento temporal almacena datos solo por un cierto período de tiempo, y luego los descarta automáticamente cuando caduca el TTL. **Las entradas temporales desaparecen para siempre cuando caduca su TTL**.
-
-El beneficio del almacenamiento temporal es el costo más bajo y la capacidad de establecer un TTL muy bajo, ambos resultan en tarifas de renta más bajas en comparación con el almacenamiento persistente. Consulta la información actual sobre los tiempos de vida mínimos y tarifas de renta [aquí](../../../networks/resource-limits-fees.mdx).
-
-El almacenamiento temporal es adecuado para datos que son solo necesarios por un período de tiempo relativamente corto y bien definido. 'Bien definido' aquí significa que al crear una entrada, el contrato debería poder definir su TTL máximo necesario.
-
-:::caution
-
-Mientras que el TTL para los datos temporales se puede extender, no es seguro depender de las extensiones para preservar datos. Siempre existe el riesgo de perder datos temporales. Solo la extensión de TTL realizada cuando se crea la entrada está garantizada.
-
-:::
-
-:::caution
-
-Tampoco es seguro depender de una entrada que caduque, ya que puede ser extendida por cualquiera. Cuando se tiene que hacer cumplir un límite de tiempo, inclúyelo siempre en los datos también.
-
-**El almacenamiento temporal es una optimización de costos, no es un mecanismo para hacer cumplir invariantes basados en el tiempo.**
-
-:::
-
-El almacenamiento temporal es más adecuado para datos fácilmente reemplazables o datos que son solo relevantes dentro de un cierto período de tiempo. Por ejemplo, datos de feeds de precios de oráculos que solo son relevantes por unos minutos, o autorizaciones de tiempo limitadas como asignaciones de tokens, tokens de sesión, subastas, bloqueos de tiempo, etc. Los nonces para las firmas de Soroban también se almacenan en la memoria temporal, al menos hasta que la firma misma caduca.
-
-Veamos cómo se puede implementar el almacenamiento temporal en un contrato que realiza subastas periódicamente y los usuarios pueden realizar ofertas que son válidas solo hasta algún punto de tiempo definido por el usuario:
-
-```rust
-use soroban_sdk::{contracttype, contractimpl, Env, Address};
-
-#[contracttype]
-pub enum DataKey {
-    Bid(Address),
-}
-
-#[contracttype]
-pub struct Bid {
-    value: i128,
-    // The bid is no longer valid after this ledger sequence number. It's
-    // important to store this value alongside the entry, as the entry may live
-    // longer than expected.
-    expiration_ledger_seq: u32,
-}
-
-#[contractimpl]
-impl AuctionContract {
-    // This function lets a user place a bid that lives only until the auction ends.
-    pub fn place_bid(env: Env, user: Address, bid: i128, bid_expiration_ledger_seq: u32) {
-        user.require_auth();
-        let bid_key = DataKey::Bid(user.clone());
-
-        // Store the bid in the temporary storage.
-        env.storage().temporary().set(&bid_key, &Bid {
-            value: bid,
-            expiration_ledger_seq: bid_expiration_ledger_seq,
-        });
-        // Compute the TTL that the bid requires.
-        let bid_ttl = bid_expiration_ledger_seq
-            .checked_sub(e.ledger().sequence())
-            .unwrap();
-        // Extend the TTL for the bid, such that it's guaranteed to live at
-        // least until the `bid_expiration_ledger_seq` that the user has
-        // requested. This operation is will fail in
-        // case if extension is longer than the protocol allows, so there is
-        // no need to further validate `bid_ttl`.
-        env.storage().temporary().extend_ttl(&bid_key, bid_ttl, bid_ttl);
-    }
-
-    // This function returns a user's bid (0 if it has expired).
-    pub fn get_bid(env: Env, user: Symbol) -> i64 {
-        let maybe_bid: Bid = env.storage().temporary().get(&DataKey::Bid(user));
-        if let Some(bid) = maybe_bid {
-            if bid.expiration_ledger_seq <= e.ledger().sequence() {
-                bid.value
-            } else {
-                // Even though the entry is still in the storage, it has
-                // logically expired. Somebody must have extended the entry in
-                // order to trick our contract, so return 0.
-                0
-            }
-
-        } else {
-            // There is no bid for the user - it either hasn't existed at all,
-            // or has been removed from the temporary storage. In either case,
-            // just return 0.
-            0
-        }
-    }
-
-    // ...
-    // The functions that initialize and run the auctions are omitted.
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-instance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-instance.mdx
deleted file mode 100644
index cf9b42e44a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-instance.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Usar almacenamiento de instancia en un contrato
-hide_table_of_contents: true
-description: El almacenamiento de instancia tiene un TTL de archivo que está vinculado a la instancia del contrato en sí
----
-
-Bajo el capó, el almacenamiento de instancia es exactamente como el almacenamiento persistente. La única diferencia es que cualquier cosa almacenada en el almacenamiento de instancia tiene un TTL de archivo que está vinculado a la instancia del contrato en sí. Así que, si un contrato está en vivo y disponible, el almacenamiento de instancia está garantizado a estarlo también.
-
-El almacenamiento de instancia es realmente útil para los datos globales del contrato que son compartidos entre todos los usuarios del contrato (administrador del token, por ejemplo). Del [contrato de ejemplo del token](../../smart-contracts/example-contracts/tokens.mdx), las funciones auxiliares para establecer y recuperar la dirección del administrador son básicamente solo envolturas que rodean la entrada de ledger de Admin.
-
-:::caution
-
-Se debe notar que _cada_ pieza de datos almacenada en `instance()` almacenamiento es recuperada del ledger _cada_ vez que se invoca el contrato. Incluso si la función invocada no interactúa con ningún dato de ledger en absoluto. Esto puede llevar a invocaciones de función más costosas (computacionalmente y financieramente) si los datos almacenados crecen con el tiempo. Elige con juicio qué partes de datos realmente pertenecen al almacenamiento de instancia, y cuáles deben mantenerse en el almacenamiento persistente.
-
-:::
-
-```rust
-pub fn has_administrator(e: &Env) -> bool {
-    let key = DataKey::Admin;
-    e.storage().instance().has(&key)
-}
-
-pub fn read_administrator(e: &Env) -> Address {
-    let key = DataKey::Admin;
-    e.storage().instance().get(&key).unwrap()
-}
-
-pub fn write_administrator(e: &Env, id: &Address) {
-    let key = DataKey::Admin;
-    e.storage().instance().set(&key, id);
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-persistent.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-persistent.mdx
deleted file mode 100644
index 217fe3c1fb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-persistent.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Usar almacenamiento persistente en un contrato
-hide_table_of_contents: true
-description: El almacenamiento persistente puede ser útil para las entradas del ledger que no son comunes entre cada usuario de la instancia del contrato
----
-
-El almacenamiento persistente puede ser muy útil para las entradas del ledger que no son comunes entre cada usuario de la instancia del contrato, pero que no son adecuadas para ser temporales (los saldos de usuario, por ejemplo). En esta guía, asumiremos que queremos almacenar un número aleatorio para un usuario y guardarlo en el almacenamiento persistente del contrato como si fuera su número favorito.
-
-```rust
-#[contracttype]
-pub enum DataKey {
-    Favorite(Address),
-}
-
-#[contract]
-pub struct FavoriteContract;
-
-#[contractimpl]
-impl FavoriteContract {
-    // This function generates, stores, and returns a random number for the user
-    pub fn generate_fave(env: Env, user: Address) -> u64 {
-        let key = DataKey::Favorite(user);
-        let fave: u64 = env.prng().gen();
-        env.storage().persistent().set(&key, &fave);
-        fave
-    }
-
-    // This function retrieves and returns the random number for the user
-    pub fn get_fave(env: Env, user: Address) -> u64 {
-        let key = DataKey::Favorite(user);
-        if let Some(fave) = env.storage().persistent().get(&key) {
-            fave
-        } else {
-            0
-        }
-    }
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-temporary.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-temporary.mdx
deleted file mode 100644
index 1b5dfc9de0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/storage/use-temporary.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Usar almacenamiento temporal en un contrato
-hide_table_of_contents: true
-description: El almacenamiento temporal es útil para un contrato para almacenar datos que pueden volverse irrelevantes o desactualizados rápidamente
----
-
-El almacenamiento temporal es útil para un contrato para almacenar datos que pueden volverse irrelevantes o desactualizados rápidamente. Por ejemplo, así es como un contrato podría usarse para almacenar un precio reciente de BTC con respecto al dólar estadounidense.
-
-```rust
-// This function updates the BTC price
-pub fn update_btc_price(env: Env, price: i128) {
-    env.storage().temporary().set(&!symbol_short("BTC"), &price);
-}
-
-// This function reads and returns the current BTC price (zero if the storage
-// entry is archived)
-pub fn get_btc_price(env: Env) -> i128 {
-    if let Some(price) = env.storage().temporary().get(&!symbol_short("BTC")) {
-        price
-    } else {
-        0
-    }
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/README.mdx
deleted file mode 100644
index f43b298f0b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/README.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Pruebas de Contrato
-description: Pruebas de Contratos Inteligentes de Stellar
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 40
----
-
-Las pruebas son vitales para asegurar que los contratos inteligentes sean seguros, resistentes y precisos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/code-coverage.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/code-coverage.mdx
deleted file mode 100644
index d7deb76ce8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/code-coverage.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Cobertura de Código
-hide_table_of_contents: true
-description: Las herramientas de cobertura de código encuentran código no probado.
-sidebar_position: 11
----
-
-Medir la cobertura de código utiliza herramientas para identificar las líneas de código que son y no son ejecutadas por las pruebas. Las estadísticas de cobertura de código pueden darnos una idea de cuánto de un contrato está realmente probado por sus pruebas.
-
-:::tip
-
-Las pruebas de mutación son otra forma de pruebas de cobertura. Ver [Pruebas de Mutación].
-
-:::
-
-En proyectos de Rust, la herramienta `cargo-llvm-cov` se puede utilizar para generar estadísticas de cobertura, informes en HTML y archivos lcov que los IDE cargarán para mostrar la cobertura en el editor de código.
-
-Instala `cargo-llvm-cov` antes de proceder con los otros comandos.
-
-```
-cargo install cargo-llvm-cov
-```
-
-## Cómo Obtener Estadísticas de Cobertura
-
-Ejecuta el subcomando de prueba que ejecutará las pruebas y mostrará las estadísticas por archivo.
-
-```
-cargo llvm-cov test
-```
-
-## Cómo Generar un Informe de Cobertura con Código
-
-Ejecuta el subcomando de prueba que ejecutará las pruebas y generará un conjunto de archivos HTML que mostrarán qué líneas de código están cubiertas.
-
-```
-cargo llvm-cov test --html --open
-```
-
-La salida del comando indicará dónde se ha escrito el archivo HTML. Abre el archivo en un navegador.
-
-## Cómo Generar un Archivo LCOV para IDEs
-
-Ejecuta el subcomando de prueba que ejecutará las pruebas y generará un único archivo `lcov.info`.
-
-```
-cargo llvm-cov test --lcov --output-path=lcov.info
-```
-
-Carga el archivo `lcov.info` en tu IDE utilizando su función de cobertura. En VSCode, esto se puede hacer instalando la extensión [Coverage Gutters] y ejecutando el comando `Coverage Gutters: Watch`.
-
-:::info
-
-Medir la cobertura de código en pruebas de fuzz requiere herramientas diferentes. Ver [Fuzzing].
-
-:::
-
-[Canales de Cobertura]: https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters
-[Pruebas de Mutación]: mutation-testing.mdx
-[Fuzzing]: fuzzing.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/differential-tests-with-test-snapshots.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/differential-tests-with-test-snapshots.mdx
deleted file mode 100644
index 8f73d693f2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/differential-tests-with-test-snapshots.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Pruebas Diferenciales con Imágenes de Prueba
-hide_table_of_contents: true
-description: Prueba diferencial utilizando imágenes de prueba automáticas.
-sidebar_position: 9
----
-
-Las pruebas están escritas para garantizar que los contratos se comporten hoy como se espera, y en el futuro también. Con el tiempo, un contrato puede cambiar y en todo el desarrollo de software permanece la posibilidad de que los cambios causen efectos secundarios inesperados. Las pruebas son una de las maneras en que identificamos cambios inesperados.
-
-Sin embargo, las pruebas son limitadas, ya que solo muestran cambios en los valores sobre los que las pruebas afirman.
-
-:::tip
-
-Las imágenes de prueba son una herramienta para realizar pruebas diferenciales. Consulta [Pruebas Diferenciales] para otras maneras.
-
-:::
-
-### Imágenes de Prueba
-
-El SDK de Soroban Rust genera imágenes de prueba en cada prueba que involucra un `Env`. Las imágenes de prueba están habilitadas por defecto. Al final de la prueba, el `Env` escribe un archivo JSON en el directorio `test_snapshots` con una imagen completa de todos los eventos publicados y el estado final del almacenamiento del ledger.
-
-La mayoría de las pruebas tienen un solo `Env` y resultarán en una sola imagen de prueba. Las pruebas que tienen múltiples `Env`s escribirán múltiples imágenes de prueba, una para cada `Env`. Los archivos de imagen de prueba se nombran con un número creciente al final para separar las imágenes de prueba para cada `Env`.
-
-### Cómo Usar Imágenes de Prueba
-
-1. Escribe pruebas utilizando el `Env` predeterminado. Por ejemplo:
-
-   ```rust
-   #![cfg(test)]
-   use soroban_sdk::Env;
-
-   use crate::{Contract, ContractClient};
-
-   #[test]
-   fn test_abc() {
-       let env = Env::default();
-       let contract_id = env.register(Contract, ());
-       let client = ContractClient::new(&env, &contract_id);
-
-       assert_eq!(client.increment(), 1);
-
-       // highlight-start
-       // At the end of the test the Env will automatically write a test snapshot
-       // to the following directory: test_snapshots/test_abc.1.json
-       // highlight-end
-   }
-   ```
-
-2. Ejecuta las pruebas y observa que las imágenes de prueba se han escrito en `test_snapshots/`.
-
-3. Confirma las imágenes de prueba en el control de versiones.
-
-4. En actualizaciones futuras, presta atención a los cambios en las imágenes de prueba en pruebas que sean inesperados. Por ejemplo, al cambiar una parte de un contrato, si las imágenes de prueba de otras partes del contrato o pruebas de fin a fin no relacionadas cambian, eso podría señalar que han ocurrido efectos secundarios.
-
-5. Difunde imágenes de prueba según sea necesario para buscar pistas sobre por qué ha ocurrido un cambio inesperado.
-
-:::info
-
-Los archivos de imágenes de prueba son verbosos. Las imágenes de prueba son más útiles cuando aparecen cambios y pueden ser diferenciadas, como un nuevo evento que se publica o un cambio en el almacenamiento.
-
-:::
-
-Para probar esto, consulta el contrato [Comenzar] o cualquiera de los [ejemplos], ejecuta las pruebas y busca las imágenes de prueba en el disco.
-
-[Pruebas Diferenciales]: ./differential-tests.mdx
-[Comenzar]: ../../smart-contracts/getting-started/README.mdx
-[ejemplos]: ../../smart-contracts/example-contracts/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/differential-tests.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/differential-tests.mdx
deleted file mode 100644
index db4eba3b2a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/differential-tests.mdx
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: Pruebas Diferenciales
-hide_table_of_contents: true
-description: Las pruebas diferenciales detectan cambios no intencionados.
-sidebar_position: 8
----
-
-Las pruebas diferenciales son la prueba de dos cosas para descubrir diferencias en su comportamiento.
-
-El objetivo es probar que las dos cosas se comportan de manera consistente y que no divergen en su comportamiento salvo por algunas diferencias esperadas. Las afirmaciones deben ser tan amplias como sea posible, probando ampliamente que todos los resultados observables no cambian, excepto por cualquier cambio esperado.
-
-Esta estrategia es efectiva al desarrollar algo nuevo que debería comportarse como algo que ya existe. Podría tratarse de una nueva versión de un contrato que mantiene el mismo comportamiento que su versión anterior. O podría ser el mismo contrato con un SDK o dependencia actualizada. O podría ser una reorganización que espera no tener cambios funcionales.
-
-Esta estrategia se puede utilizar en el contexto de pruebas unitarias e integradas, o en el contexto de pruebas de fuzz también.
-
-:::tip
-
-Todos los contratos desarrollados con el SDK de Rust Soroban tienen una forma de pruebas diferenciales incorporadas y habilitadas por defecto. Consulta [Pruebas Diferenciales con Imágenes de Prueba].
-
-:::
-
-## Cómo Escribir Pruebas Diferenciales
-
-Para experimentar escribiendo una prueba diferencial, abre un contrato que hayas desplegado, o revisa un ejemplo del repositorio [soroban-examples] y desplégalo.
-
-Asumiendo que el contrato ha sido desplegado y se están realizando cambios en la copia local. Necesitamos verificar que el comportamiento inalterado en el contrato no ha cambiado en comparación con lo que está desplegado.
-
-1. Utiliza el comando [stellar contract fetch] para obtener el contrato que ya está desplegado. El contrato ya desplegado se utilizará como base que se espera que la copia local iguale.
-
-   ```shell
-   stellar contract fetch --id C... --out-file contract.wasm
-   ```
-
-2. Importa el contrato en las pruebas con el macro `contractimport!`.
-
-   ```rust
-   mod deployed {
-       soroban_sdk::contractimport!(file = "contract.wasm");
-   }
-   ```
-
-3. Escribe una prueba que ejecute la misma lógica para el contrato desplegado y el contrato local, comparando el resultado. Asumiendo que el [ejemplo de incremento] está en uso, la prueba se vería algo así como lo siguiente.
-
-   ```rust
-   #![cfg(test)]
-   use crate::{IncrementContract, IncrementContractClient};
-   use soroban_sdk::{testutils::Events as _, Env};
-
-   mod deployed {
-       soroban_sdk::contractimport!(file = "contract.wasm");
-   }
-
-   #[test]
-   fn differential_test() {
-       assert_eq!(
-           // Baseline – the deployed contract
-           {
-               let env = Env::default();
-               let contract_id = env.register(deployed::WASM, ());
-               let client = IncrementContractClient::new(&env, &contract_id);
-               (
-                   // Return Values
-                   (
-                       client.increment(),
-                       client.increment(),
-                       client.increment(),
-                   ),
-                   // Events
-                   env.events().all(),
-               )
-           },
-           // Local – the changed or refactored contract
-           {
-               let env = Env::default();
-               let contract_id = env.register(IncrementContract, ());
-               let client = IncrementContractClient::new(&env, &contract_id);
-               (
-                   // Return Values
-                   (
-                       client.increment(),
-                       client.increment(),
-                       client.increment(),
-                   ),
-                   // Events
-                   env.events().all(),
-               )
-           },
-       );
-   }
-   ```
-
-4. Ejecuta la prueba para comparar la línea base y los resultados observables locales.
-
-Esta prueba utiliza los mismos patrones utilizados en [pruebas unitarias] y [pruebas de integración]:
-
-1. Crear un entorno, el `Env`.
-2. Importa el contrato Wasm para comparar.
-3. Registra el contrato local para ser probado.
-4. Invoca funciones utilizando un cliente.
-5. Afirmar igualdad.
-
-:::tip
-
-Las pruebas diferenciales funcionan mejor cuando se hacen menos suposiciones. En lugar de afirmar solo sobre valores de retorno específicos o sobre detalles de implementación como un estado específico, afirmar sobre todos los resultados observables e incluir cosas como eventos publicados o valores de retorno de otras funciones de contrato de solo lectura ayudará a descubrir cambios inesperados.
-
-:::
-
-[Comenzar]: ../../smart-contracts/comenzar
-[ejemplo de incremento]: https://github.com/stellar/soroban-examples/blob/main/increment/src/lib.rs
-[Pruebas Diferenciales con Imágenes de Prueba]: ./differential-tests-with-test-snapshots.mdx
-[fetch de contrato stellar]: ../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch
-[pruebas de integración]: ./integration-tests.mdx
-[pruebas unitarias]: ./unit-tests.mdx
-[stellar/rs-soroban-sdk#1360]: https://github.com/stellar/rs-soroban-sdk/issues/1360
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/fork-testing.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/fork-testing.mdx
deleted file mode 100644
index 47c1130958..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/fork-testing.mdx
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: Pruebas de Fork
-hide_table_of_contents: true
-description: Pruebas de integración utilizando datos de mainnet.
-sidebar_position: 6
----
-
-Las pruebas de bifurcación son otra forma de [pruebas de integración], donde no solo se pueden utilizar contratos de mainnet, sino también sus datos en mainnet. Se toma una imagen del ledger y se utiliza para crear un entorno para las pruebas. La prueba opera como un fork de ese estado inicial.
-
-Nuestra capacidad para probar un contrato que depende de otro contrato se limita a nuestro propio conocimiento de este otro contrato y de los diferentes estados en los que puede entrar. Las pruebas de integración, donde se utilizan dependencias reales, eliminan algunas suposiciones, pero si una dependencia tiene un estado complejo, también puede ser útil probar contra datos de mainnet tal como existen en diferentes momentos.
-
-Probar con datos de mainnet es una forma de cerrar aún más la brecha.
-
-El [Soroban Rust SDK] y el [Stellar CLI] se unen para hacer posible las pruebas con datos de mainnet.
-
-## Cómo Escribir Pruebas con Datos de Mainnet
-
-El siguiente es un ejemplo de una prueba que incluye un contrato de dependencia en la prueba, en lugar de simularlo. La prueba está escrita para probar el [contrato increment-with-pause] y el [contrato pause]. El contrato tiene una función `increment` que aumenta el valor de un contador en uno en cada invocación. El contrato depende del contrato pause para controlar si la funcionalidad de incremento está pausada.
-
-Las siguientes pruebas configuran el contrato `increment-with-pause`, usando una imagen del ledger que ya tiene desplegado el contrato dependencia `pause` junto con sus datos de contrato.
-
-1. Utiliza el comando [stellar snapshot create] para crear una imagen del contrato de pausa y sus datos.
-
-   ```
-   stellar snapshot create --address C... --output json --out snapshot.json
-   ```
-
-   :::info
-
-   La opción `--ledger <ledger-seq>` se puede agregar para especificar un ledger para la imagen. Cuando no se especifica, el último ledger que se ha enviado a archivos es la imagen, que generalmente tiene menos de 5 minutos.
-
-   :::
-
-2. Utiliza `Env::from_ledger_snapshot_file(...)` para cargar la imagen en un `Env` en la prueba.
-
-   ```rust
-   let env = Env::from_ledger_snapshot_file("snapshot.json");
-   ```
-
-3. Escribe una prueba similar a la siguiente que utilice el `Env` precargado con los contratos y los datos del contrato en `snapshot.json`. La prueba hace afirmaciones sobre el comportamiento del contrato principal en el contexto de las dependencias reales y los datos que las dependencias tienen en la red.
-
-   ```rust
-   #[test]
-   fn test() {
-       // highlight-start
-       let env = Env::from_ledger_snapshot_file("snapshot.json");
-       // highlight-end
-
-       let contract_id = env.register(
-           IncrementContract,
-           IncrementContractArgs::__constructor(&pause_id),
-       );
-       let client = IncrementContractClient::new(&env, &contract_id);
-
-       assert_eq!(client.increment(), 1);
-   }
-   ```
-
-La mayoría de las pruebas, sean unitarias, simulaciones o pruebas de integración, se verán muy similares a la prueba anterior. Las pruebas harán cuatro cosas:
-
-1. Crea un entorno, el `Env`, ya sea con `Env::default()` o `Env::from_ledger_snapshot_file(...)`.
-2. Registra el o los contratos a probar.
-3. Invoca funciones usando el cliente generado.
-4. Asegura el resultado.
-
-:::tip
-
-Las imágenes creadas desde testnet o mainnet también pueden ser una forma de probar y depurar incidentes con un contrato en la red. Se puede crear una imagen en un ledger específico y escribir pruebas utilizando esa imagen para entender mejor por qué o cómo ocurrió una serie de eventos.
-
-:::
-
-:::tip
-
-Se puede crear una imagen de cualquier contrato desplegado en mainnet o testnet usando el comando `stellar snapshot create`. Puede ser una forma divertida de experimentar y aprender sobre contratos desplegados al cargar una imagen en una prueba e invocar el contrato. Fuzzing incluso se puede realizar en contratos utilizando esta herramienta.
-
-:::
-
-[contrato increment-with-pause]: https://github.com/stellar/soroban-examples/blob/main/increment_with_pause/src/lib.rs
-[contrato pause]: https://github.com/stellar/soroban-examples/blob/main/pause/src/lib.rs
-[prueba de integración]: ./integration-tests.mdx
-[Hacer Llamadas Entre Contratos]: ../conventions/cross-contract.mdx
-[SDK de Rust para Soroban]: ../../../tools/sdks/contract-sdks.mdx#sdk-de-soroban-en-rust
-[Stellar CLI]: ../../../tools/cli/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/fuzzing.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/fuzzing.mdx
deleted file mode 100644
index 6ad0da1476..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/fuzzing.mdx
+++ /dev/null
@@ -1,175 +0,0 @@
----
-title: Fuzzing
-hide_table_of_contents: true
-description: Fuzzing y pruebas de propiedades para encontrar comportamientos inesperados.
-sidebar_position: 7
----
-
-Fuzzing es el proceso de proporcionar datos aleatorios a programas para identificar comportamientos inesperados, como caídas y pánicos.
-
-Las pruebas de fuzz también pueden escribirse como pruebas de propiedades que, en lugar de buscar identificar pánicos y caídas, afirman que alguna propiedad se mantenga verdadera. El fuzzing, demostrado aquí y en otros lugares de estos documentos, utiliza principios tanto de pruebas de propiedades como de fuzzing, pero solo usará el término fuzzing para referirse a ambos.
-
-Los siguientes pasos pueden usarse en cualquier espacio de trabajo de contrato Stellar. Si estás experimentando, pruébalos en el [ejemplo de incremento]. El contrato tiene una función `increment` que aumenta un valor contador en uno en cada invocación.
-
-## Cómo escribir pruebas de fuzzing
-
-1. Instala la toolchain nightly de Rust. Rust nightly es necesario para ejecutar cargo-fuzz.
-
-   ```
-   rustup install nightly
-   ```
-
-2. Instala `cargo-fuzz`.
-
-   ```text
-   cargo install --locked cargo-fuzz
-   ```
-
-3. Inicializa un proyecto de fuzz ejecutando el siguiente comando dentro del directorio de tu contrato.
-
-   ```text
-   cargo fuzz init
-   ```
-
-4. Abre el archivo `Cargo.toml` del contrato. Agrega `lib` como tipo de `crate`.
-
-   ```diff
-    [lib]
-   -crate-type = ["cdylib"]
-   +crate-type = ["lib", "cdylib"]
-   ```
-
-5. Abre el archivo generado `fuzz/Cargo.toml`. Agrega la dependencia `soroban-sdk`.
-
-   ```diff
-    [dependencies]
-    libfuzzer-sys = "0.4"
-   +soroban-sdk = { version = "*", features = ["testutils"] }
-   ```
-
-6. Abre el archivo generado `fuzz/src/fuzz_target_1.rs`. Se verá como el siguiente.
-
-   ```rust
-   #![no_main]
-   use libfuzzer_sys::fuzz_target;
-
-   fuzz_target!(|data: &[u8]| {
-       // fuzzed code goes here
-   });
-   ```
-
-7. Completa la llamada `fuzz_target!` con la configuración de la prueba y las aserciones. Por ejemplo, para el [ejemplo de incremento]:
-
-   ```rust
-   #![no_main]
-   use libfuzzer_sys::fuzz_target;
-   use soroban_increment_with_fuzz_contract::{IncrementContract, IncrementContractClient};
-   use soroban_sdk::{
-       testutils::arbitrary::{arbitrary, Arbitrary},
-       Env,
-   };
-
-   #[derive(Debug, Arbitrary)]
-   pub struct Input {
-       pub by: u64,
-   }
-
-   fuzz_target!(|input: Input| {
-       let env = Env::default();
-       let id = env.register(IncrementContract, ());
-       let client = IncrementContractClient::new(&env, &id);
-
-       let mut last: Option<u32> = None;
-       for _ in input.by.. {
-           match client.try_increment() {
-               Ok(Ok(current)) => assert!(Some(current) > last),
-               Err(Ok(_)) => {} // Expected error
-               Ok(Err(_)) => panic!("success with wrong type returned"),
-               Err(Err(_)) => panic!("unrecognised error"),
-           }
-       }
-   });
-   ```
-
-8. Ejecuta el objetivo de fuzz.
-
-   ```text
-   cargo +nightly fuzz run --sanitizer=thread fuzz_target_1
-   ```
-
-   :::info
-
-   Si estás desarrollando en MacOS, necesitas agregar la bandera `--sanitizer=thread` para solucionar un [problema conocido](https://github.com/stellar/rs-soroban-sdk/issues/1056).
-
-   :::
-
-Esta prueba usa los mismos patrones usados en [pruebas unitarias] e [integración]:
-
-1. Crea un ambiente, el `Env`.
-2. Registra el contrato que será probado.
-3. Invoca funciones usando un cliente.
-4. Afirma las expectativas.
-
-:::tip
-
-Para un ejemplo detallado completo, ve el [ejemplo de fuzzing].
-
-:::
-
-:::info
-
-Hay otra herramienta para fuzzing de código Rust, `cargo-afl`. Consulta el [Rust Fuzz book] para un tutorial sobre cómo usarla.
-
-:::
-
-## Cómo obtener cobertura de código de pruebas de fuzzing
-
-Obtener datos de cobertura de código para pruebas de fuzz requiere herramientas diferentes que al hacerlo para pruebas regulares de Rust.
-
-1. Ejecuta las pruebas de fuzz hasta que produzcan un corpus, igual que en el paso 7 arriba.
-
-   ```text
-   cargo +nightly fuzz run --sanitizer thread fuzz_target_1
-   ```
-
-2. Instala las herramientas llvm para el compilador nightly.
-
-   ```text
-   rustup component add --toolchain nightly llvm-tools-preview
-   ```
-
-3. Ejecuta el comando de cobertura fuzz que ejecutará el corpus y escribirá datos de cobertura en el directorio coverage en formato `profdata`.
-
-   ```text
-   cargo +nightly fuzz coverage --sanitizer thread fuzz_target_1
-   ```
-
-4. Ejecuta el comando llvm-cov para convertir el archivo profdata a un archivo lcov.
-
-   ```
-   $(find $(rustc --print sysroot) -name llvm-cov) export \
-       -instr-profile=fuzz/coverage/fuzz_target_1/coverage.profdata \
-       -object target/$(rustc -vV | sed -n 's|host: ||p')/coverage/$(rustc -vV | sed -n 's|host: ||p')/release/fuzz_target_1 \
-       --ignore-filename-regex "rustc" \
-       -format=lcov \
-       > lcov.info
-   ```
-
-   Carga el archivo `lcov.info` en tu IDE usando su función de cobertura. En VSCode esto puede hacerse instalando la extensión [Coverage Gutters] y ejecutando el comando `Coverage Gutters: Watch`.
-
-:::tip
-
-Para medir la cobertura de código de pruebas regulares de Rust, ve [Cobertura de código].
-
-:::
-
-[ejemplo de incremento]: https://github.com/stellar/soroban-examples/blob/main/increment/src/lib.rs
-[Pruebas diferenciales con snapshots de prueba]: ./differential-tests-with-test-snapshots.mdx
-[stellar contract fetch]: ../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch
-[pruebas de integración]: ./integration-tests.mdx
-[pruebas unitarias]: ./unit-tests.mdx
-[stellar/rs-soroban-sdk#1360]: https://github.com/stellar/rs-soroban-sdk/issues/1360
-[ejemplo de fuzzing]: ../../smart-contracts/example-contracts/fuzzing.mdx
-[Rust Fuzz Book]: https://rust-fuzz.github.io/book
-[Cobertura de código]: code-coverage.mdx
-[Coverage Gutters]: https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/integration-tests.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/integration-tests.mdx
deleted file mode 100644
index b505554961..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/integration-tests.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Pruebas de Integración
-hide_table_of_contents: true
-description: Las pruebas de integración utilizan contratos de dependencia en lugar de simulaciones.
-sidebar_position: 5
----
-
-Las pruebas de integración son pruebas que incluyen la integración entre componentes y, por lo tanto, prueban un ámbito más amplio como otros contratos.
-
-El [Soroban Rust SDK] facilita igualmente las pruebas de integración al proporcionar utilidades para probar contra contratos reales obtenidos de mainnet, testnet o el sistema de archivos local.
-
-## Cómo Escribir Pruebas de Integración
-
-El siguiente es un ejemplo de una prueba que incluye un contrato de dependencia en la prueba, en lugar de simularlo. La prueba está escrita para probar el [increment-with-pause contract] y el [pause contract]. El contrato tiene una función `increment` que aumenta el valor de un contador en uno en cada invocación. El contrato depende del contrato de pausa para controlar si la funcionalidad de incremento está pausada.
-
-Las siguientes pruebas configuran el contrato `increment-with-pause`, además de importar y registrar el contrato real de pausa usando su archivo wasm.
-
-1. Usa el comando [stellar contract fetch] para obtener el contrato de dependencia que ya está desplegado en testnet o mainnet.
-
-   ```shell
-   stellar contract fetch --id C... > pause.wasm
-   ```
-
-2. Importa el contrato en las pruebas con el macro `contractimport!`.
-
-   ```rust
-   mod pause {
-       soroban_sdk::contractimport!(file = "pause.wasm");
-   }
-   ```
-
-3. Escribe una prueba similar a la siguiente que registre no solo el contrato increment-with-pause, sino también el contrato de pausa que fue importado. La prueba verifica que cuando el contrato de pausa no está pausado, el contrato de incremento funciona como se espera. Cuando está pausado, la función de incremento genera un error. Una vez que se ha reanudado, la función funciona como se espera.
-
-   ```rust
-   #[test]
-   fn test() {
-       let env = Env::default();
-
-       // highlight-start
-       let pause_id = env.register(pause::WASM, ());
-       let pause_client = pause::Client::new(&env, &pause_id);
-       // highlight-end
-
-       let contract_id = env.register(
-           IncrementContract,
-           IncrementContractArgs::__constructor(&pause_id),
-       );
-       let client = IncrementContractClient::new(&env, &contract_id);
-
-       pause_client.set(&false);
-       assert_eq!(client.increment(), 1);
-
-       pause_client.set(&true);
-       assert_eq!(client.try_increment(), Err(Ok(Error::Paused)));
-
-       pause_client.set(&false);
-       assert_eq!(client.increment(), 2);
-   }
-   ```
-
-La mayoría de las pruebas, sean unitarias, simulaciones o pruebas de integración, se verán muy similares a la prueba anterior. Las pruebas harán cuatro cosas:
-
-1. Crear un entorno, el `Env`.
-2. Registrar el/los contrato(s) a probar.
-3. Invocar funciones usando el cliente generado.
-4. Afirmar el resultado.
-
-[contrato increment-with-pause]: https://github.com/stellar/soroban-examples/blob/main/increment_with_pause/src/lib.rs
-[contrato de pausa]: https://github.com/stellar/soroban-examples/blob/main/pause/src/lib.rs
-[Pruebas de Integración]: ./integration-tests.mdx
-[Hacer Llamadas entre Contratos]: ../conventions/cross-contract.mdx
-[Soroban Rust SDK]: ../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/ledger-snapshot-testing.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/ledger-snapshot-testing.mdx
deleted file mode 100644
index 792996328d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/ledger-snapshot-testing.mdx
+++ /dev/null
@@ -1,283 +0,0 @@
----
-title: Pruebas con imagen de ledger
-hide_table_of_contents: true
-description: Usa imágenes de ledger para probar contratos con datos del ledger
-sidebar_position: 12
----
-
-Las imágenes de ledger se pueden usar para probar smart contracts con una copia local de las entradas del ledger. Aprende a crear una imagen de ledger y usarla para pruebas de smart contracts en unos pocos pasos simples. Los ejemplos aquí cubrirán los siguientes casos de uso:
-
-- Leer el valor almacenado de los datos del ledger
-- Leer un valor almacenado llamando a una función del smart contract
-- Leer el saldo de una cuenta
-
-## 1. Crear un proyecto por defecto
-
-Antes de crear una imagen de ledger y comenzar con las pruebas, primero creemos un smart contract simple que pueda usarse para los ejemplos de prueba.
-
-Comienza creando el contrato Hello World por defecto:
-
-```bash
-stellar contract init <project_name>
-```
-
-El smart contract tiene dos funciones: `set_value()` para almacenar un valor, y `get_value()` para leer el valor almacenado. Reemplaza la función `hello()` por defecto con estas dos funciones:
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, vec, Env, String, Vec};
-
-#[contract]
-pub struct Contract;
-
-#[contractimpl]
-impl Contract {
-    pub fn set_value(env: Env, key: String, value: u32) {
-        env.storage().persistent().set(&key, &value);
-    }
-
-    pub fn get_value(env: Env, key: String) -> u32 {
-        env.storage().persistent().get(&key).unwrap_or(0)
-    }
-}
-```
-
-Dado que queremos escribir una prueba que lea datos almacenados en el ledger, o más precisamente, en una imagen del ledger, debemos crear, desplegar e invocar el contrato inteligente.
-
-#### Crear contrato
-
-Usa el [Stellar CLI](../../../tools/cli/stellar-cli.mdx) para construir el contrato:
-
-```bash
-stellar contract build
-```
-
-#### Desplegar contrato
-
-A continuación, desplegamos el contrato en Testnet:
-
-```bash
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/hello_world.wasm \
-    --source alice \
-    --network testnet
-```
-
-El comando deploy devolverá la dirección del contrato (p. ej., `CB5QCALXDP2N6H473AQBNIFEAPCNHWCIWOASRNGTHCSC4WNC3SOROBAN`), la cual se usará en los siguientes pasos.
-
-#### Invocar contrato
-
-Finalmente, invocamos la función set_value() para almacenar un valor en el ledger de Testnet:
-
-```bash
-stellar contract invoke \
-    --id CB5QCALXDP2N6H473AQBNIFEAPCNHWCIWOASRNGTHCSC4WNC3SOROBAN \
-    --source alice \
-    --network testnet \
-    -- \
-    set_value \
-    --key "count" --value 123456
-```
-
-Ahora tenemos una función de contrato inteligente desplegada y en funcionamiento que ha almacenado un valor en el ledger. Puedes verificar el valor invocando la función `get_value()`.
-
-## 2. Crear una imagen del ledger
-
-Se puede crear una imagen del ledger usando el Stellar CLI. El comando CLI permite personalizar y limitar el alcance de la imagen, ya que probablemente no sea necesario crear una imagen de todas las entradas del ledger. Consulta la [documentación](../../../tools/cli/stellar-cli.mdx#stellar-snapshot-create) para obtener detalles completos sobre cómo limitar la instantánea.
-
-Para los ejemplos aquí usados, queremos limitar la imagen del ledger para incluir las entradas relacionadas con:
-
-- El contrato inteligente
-- El usuario `alice`
-- La dirección del token nativo (XLM)
-
-Desde la raíz del proyecto del contrato inteligente, crea la imagen del ledger con este comando:
-
-```bash
-stellar snapshot create \
-    --output json \
-    --network testnet \
-    --address CB5QCALXDP2N6H473AQBNIFEAPCNHWCIWOASRNGTHCSC4WNC3SOROBAN \
-    --address alice \
-    --address CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC
-```
-
-El comando almacenará la imagen como un archivo JSON llamado `snapshot.json`.
-
-Este es un ejemplo de la imagen, que muestra el valor almacenado cuando se invocó la función del contrato `set_value()`:
-
-```json
-{
-    "protocol_version": 23,
-    "sequence_number": 801343,
-    "timestamp": 0,
-    "network_id": "cee0302d59844d32bdca915c8203dd44b33fbb7edc19051ea37abedf28ecd472",
-    "base_reserve": 1,
-    "min_persistent_entry_ttl": 0,
-    "min_temp_entry_ttl": 0,
-    "max_entry_ttl": 0,
-    "ledger_entries": [
-        ...
-        [
-            {
-                "contract_data": {
-                    "contract": "CB5QCALXDP2N6H473AQBNIFEAPCNHWCIWOASRNGTHCSC4WNC3SOROBAN",
-                    "key": {
-                        "string": "count"
-                    },
-                    "durability": "persistent"
-                }
-            },
-            [
-                {
-                    "last_modified_ledger_seq": 801330,
-                    "data": {
-                        "contract_data": {
-                            "ext": "v0",
-                            "contract": "CB5QCALXDP2N6H473AQBNIFEAPCNHWCIWOASRNGTHCSC4WNC3SOROBAN",
-                            "key": {
-                                "string": "count"
-                            },
-                            "durability": "persistent",
-                            "val": {
-                                "u32": 123456
-                            }
-                        }
-                    },
-                    "ext": "v0"
-                },
-                4294967295
-            ]
-        ],
-    ]
-    ...
-}
-```
-
-Ahora podemos empezar a escribir un script de prueba que cargue la imagen en el entorno de prueba.
-
-Si se vuelve a invocar la función del contrato inteligente `set_value()`, ejecuta nuevamente el comando `stellar snapshot create` para garantizar que la imagen refleje el ledger.
-
-## 3. Leer valores almacenados y balances
-
-Para ilustrar cómo las pruebas de contratos inteligentes pueden utilizar los datos de la imagen del ledger, leeremos el valor almacenado de dos maneras distintas y obtendremos el balance del usuario `alice`.
-
-### Cargar datos de la imagen
-
-Como punto de partida, usamos el archivo de prueba `test.rs` incluido en el proyecto de contrato inteligente predeterminado que creamos y modificamos. Dado que la función `hello()` fue eliminada y reemplazada por las funciones para almacenar y obtener un valor, la prueba para `hello()` también puede eliminarse.
-
-Primero, se cargan los datos de la imagen del ledger en el entorno:
-
-```rust
-#[test]
-fn test() {
-    let env = Env::from_ledger_snapshot_file(
-        "../../snapshot.json",
-    ;
-}
-```
-
-### Leer valor almacenado del ledger
-
-En este primer ejemplo, leemos el valor almacenado directamente del ledger usando `env.storage()`. El método `env.as_contract()` nos permite ejecutar código en el contexto de un ID de contrato dado. Esto significa que podemos ejecutar código como si estuviéramos dentro del contrato.
-
-Primero, definimos el ID del contrato para la prueba, que es el ID devuelto cuando se desplegó el contrato inteligente.
-
-Luego, `env.as_contract()` se usa para obtener el valor del almacenamiento, es decir, del ledger. Cuando se invocó la función del contrato `set_value()`, usamos `count` como clave, así que se usa la misma clave para obtener el valor.
-
-```rust
-#[test]
-fn test() {
-    let env = Env::from_ledger_snapshot_file(
-        "../../snapshot.json",
-    );
-
-    let contract_id = Address::from_str(
-        &env,
-        "CB5QCALXDP2N6H473AQBNIFEAPCNHWCIWOASRNGTHCSC4WNC3SOROBAN"
-    );
-
-    env.as_contract(&contract_id, || {
-        let val: u32 = env.storage().persistent().get(
-            &String::from_str(&env, "count")
-        ).unwrap_or(0);
-        assert_eq!(val, 123456);
-    });
-}
-```
-
-Ahora ejecuta la prueba:
-
-```bash
-cargo test
-```
-
-El valor esperado es `123456`, y el valor se verifica con `assert_eq!()`. Si la prueba no pasa, esta fallará con pánico.
-
-### Leer valor almacenado con función del contrato
-
-La forma más típica de leer un valor almacenado en pruebas es llamar a la función del contrato que lee el valor. La prueba para este enfoque es la misma que si se cargara el entorno predeterminado, excepto que no necesitamos registrar el contrato en la prueba; usamos un ID real de contrato, como en el ejemplo anterior, porque en la imagen del ledger, el valor está vinculado a un ID de contrato específico.
-
-```rust
-#[test]
-fn test() {
-    let env = Env::from_ledger_snapshot_file(
-        "../../snapshot.json",
-    );
-
-    let contract_id = Address::from_str(
-        &env,
-        "CB5QCALXDP2N6H473AQBNIFEAPCNHWCIWOASRNGTHCSC4WNC3SOROBAN"
-    );
-
-    let client = ContractClient::new(&env, &contract_id);
-
-    let value: u32 = client.get_value(&String::from_str(&env, "count"));
-
-    assert_eq!(value, 123456);
-}
-```
-
-Este ejemplo muestra que solo hay diferencias menores entre probar funciones de contratos con el entorno predeterminado y el entorno de la imagen.
-
-### Leer balance de cuenta
-
-En este último ejemplo, queremos leer el balance de una cuenta. Puede ser el balance de una cuenta de usuario o de un contrato inteligente; cualquier cuenta que pueda tener un balance. En este ejemplo, verificamos el balance de la cuenta del usuario `alice`.
-
-En este ejemplo, asumimos que `alice` ya tiene un saldo en XLM, y dado que los ejemplos están basados en Testnet, la cuenta de `alice` fue financiada por FriendBot si se siguió esta [guía](../../../tools/cli/cookbook/stellar-keys.mdx) al crear la cuenta. La dirección de `alice` se puede consultar ejecutando este comando:
-
-```bash
-stellar keys address alice
-```
-
-Los tokens, como XLM, están encapsulados en una interfaz de contrato llamada [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx). Esta interfaz proporciona una forma conveniente de consultar el balance de una cuenta. El primer paso para obtener el balance de la cuenta es crear un cliente de contrato para los tokens XLM.
-
-La dirección SAC para XLM es una dirección reservada y será la misma para todos los proyectos. USDC y otros activos tendrán otra dirección SAC, pero estas no cambian. Usamos la dirección SAC para definir un cliente usando `TokenClient`.
-
-Luego definimos la dirección de la cuenta cuyo balance queremos consultar, y llamamos a `client.balance()` con la dirección de la cuenta como argumento.
-
-```rust
-#[test]
-fn test() {
-    let env = Env::from_ledger_snapshot_file(
-        "../../snapshot.json",
-    );
-
-    let client = TokenClient::new(
-        &env,
-        &Address::from_string(&String::from_str(
-            &env,
-            "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"
-        ))
-    );
-
-    let account = Address::from_string(&String::from_str(
-        &env,
-        "GDKOYSOKU4TNHGGR763NOL6VNY52WKJL3XI33TOUKDNF4AZN7SOROBAN"
-    ));
-
-    assert_eq!(client.balance(&account), 99602342515);
-}
-```
-
-La cuenta puede ser un usuario, como en este caso, pero también puede ser un contrato que posea activos, como una billetera de contrato inteligente.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/mocking.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/mocking.mdx
deleted file mode 100644
index add823fe8c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/mocking.mdx
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: Simulación
-hide_table_of_contents: true
-description: Simulación de contratos dependientes en pruebas.
-sidebar_position: 2
----
-
-Los mocks se usan en pruebas para excluir funcionalidades que no se quieren probar. Los mocks se usan cuando es difícil probar contra un componente externo.
-
-:::tip
-
-El [Soroban Rust SDK] facilita probar contra un contrato real tanto como probar contra un mock de un contrato. En algunos ecosistemas se evitan las pruebas de integración. No ocurre así en el ecosistema Stellar. Consulta [Pruebas de Integración].
-
-:::
-
-## Cómo escribir pruebas con mocks
-
-El siguiente es un ejemplo de una prueba que usa un mock, escrita para probar el [contrato increment-with-pause]. El contrato tiene una función `increment` que aumenta un contador en uno cada vez que se invoca. El contrato depende de otro contrato que controla si la función de incremento está en pausa.
-
-Las siguientes pruebas configuran el contrato `increment-with-pause` junto con un mock del contrato de pausa, e invocan varias veces la función del contrato de incremento bajo diferentes condiciones esperadas del contrato de pausa.
-
-La siguiente prueba verifica que cuando el contrato de pausa no está en pausa, el contrato de incremento funciona.
-
-```rust
-#![cfg(test)]
-use crate::{Error, IncrementContract, IncrementContractArgs, IncrementContractClient, Pause};
-use soroban_sdk::{contract, contractimpl, Env};
-
-mod notpaused {
-    use super::*;
-    // highlight-start
-    #[contract]
-    pub struct Mock;
-    #[contractimpl]
-    impl Pause for Mock {
-        fn paused(_env: Env) -> bool {
-            false
-        }
-    }
-    // highlight-end
-}
-
-#[test]
-fn test_notpaused() {
-    let env = Env::default();
-    // highlight-start
-    let pause_id = env.register(notpaused::Mock, ());
-    // highlight-end
-    let contract_id = env.register(
-        IncrementContract,
-        IncrementContractArgs::__constructor(&pause_id),
-    );
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.increment(), 1);
-    assert_eq!(client.increment(), 2);
-    assert_eq!(client.increment(), 3);
-}
-```
-
-La siguiente prueba verifica que cuando el contrato de pausa está en pausa, la función del contrato de incremento rechaza los intentos de incrementar.
-
-```rust
-#![cfg(test)]
-use crate::{Error, IncrementContract, IncrementContractArgs, IncrementContractClient, Pause};
-use soroban_sdk::{contract, contractimpl, Env};
-
-mod paused {
-    use super::*;
-    // highlight-start
-    #[contract]
-    pub struct Mock;
-    #[contractimpl]
-    impl Pause for Mock {
-        fn paused(_env: Env) -> bool {
-            true
-        }
-    }
-    // highlight-end
-}
-
-#[test]
-fn test_paused() {
-    let env = Env::default();
-    // highlight-start
-    let pause_id = env.register(paused::Mock, ());
-    // highlight-end
-    let contract_id = env.register(
-        IncrementContract,
-        IncrementContractArgs::__constructor(&pause_id),
-    );
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.try_increment(), Err(Ok(Error::Paused)));
-}
-```
-
-La mayoría de las pruebas, ya sean unitarias, con mocks o de integración, serán muy similares a estas. Harán cuatro cosas:
-
-1. Crear un ambiente, el `Env`.
-2. Registrar el/los contratos que se van a probar.
-3. Invocar funciones usando el cliente generado.
-4. Verificar el resultado.
-
-:::warning
-
-La simulación introduce supuestos sobre el comportamiento de otro contrato. Aunque el contrato publique una interfaz que diga que devolverá un bool (true/false), los contratos pueden devolver cualquier tipo.
-
-```rust
-impl Pause {
-    fn paused(env: Env) -> ? { ? }
-}
-```
-
-Esta es una razón por la que es útil probar y hacer fuzzing usando dependencias reales y programar con defensiva asumiendo que cualquier llamada externa puede causar que tu contrato falle.
-
-Consulta [Pruebas de Integración] para saber cómo probar con dependencias reales.
-
-El [Soroban Rust SDK] maneja las llamadas a contratos de forma defensiva para que cualquier error inesperado o tipo inesperado devuelto haga que la ejecución se detenga. El SDK también ofrece métodos para realizar estas llamadas y para interceptar situaciones de error. Consulta [Realizar llamadas entre contratos] para más detalles.
-
-:::
-
-[contrato increment-with-pause]: https://github.com/stellar/soroban-examples/blob/main/increment_with_pause/src/lib.rs
-[Pruebas de Integración]: ./integration-tests.mdx
-[Realizar llamadas entre contratos]: ../conventions/cross-contract.mdx
-[Soroban Rust SDK]: ../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/mutation-testing.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/mutation-testing.mdx
deleted file mode 100644
index 659e20375f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/mutation-testing.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Pruebas de Mutación
-hide_table_of_contents: true
-description: La prueba de mutación encuentra código no probado.
-sidebar_position: 10
----
-
-La prueba de mutación consiste en hacer cambios a un programa, ya sea manual o automáticamente, para identificar cambios que se pueden realizar y que no son detectados por las pruebas.
-
-Las pruebas de mutación son similares a medir la [cobertura de código], compartiendo el mismo objetivo de identificar el código no cubierto por las pruebas. Pero mientras que la cobertura de código se enfoca en verificar si una línea de código se ejecuta durante una prueba, las pruebas de mutación realmente comprueban que una prueba falle cuando esa línea es modificada. Una línea de código puede parecer cubierta por las pruebas, pero los resultados y efectos secundarios pueden no ser validados en dichas pruebas.
-
-## Cómo realizar Pruebas de Mutación
-
-La herramienta `cargo-mutants` se puede utilizar para modificar automáticamente e iterativamente el código de Rust, y volver a ejecutar las pruebas después de cada mutación, para identificar código no probado.
-
-1. Instalar `cargo-mutants`:
-
-   ```shell
-   cargo install --locked cargo-mutants
-   ```
-
-2. Ejecuta el comando `cargo mutants` dentro del directorio del crate de tu contrato.
-
-   ```shell
-   $ cargo mutants
-   Found 4 mutants to test
-   ok       Unmutated baseline in 19.0s build + 0.6s test
-    INFO Auto-set test timeout to 20s
-   MISSED   src/lib.rs:14:9: replace IncrementContract::increment -> u32 with 1 in 0.4s build + 0.4s test
-   4 mutants tested in 23s: 1 missed, 3 caught
-   ```
-
-   El código que se identifica como no cubierto por una prueba será mostrado como una línea `MISSED` en la salida.
-
-   Las diferencias de cada cambio que se intentó pueden encontrarse en el directorio `mutants.out/diff`.
-
-[cobertura de código]: code-coverage.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/test-contract-auth.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/test-contract-auth.mdx
deleted file mode 100644
index 315a6129b6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/test-contract-auth.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Prueba de Autorización
-hide_table_of_contents: true
-description: Escribe pruebas que verifiquen la autorización del contrato.
-sidebar_position: 3
----
-
-Las pruebas pueden afirmar sobre las autenticaciones que se espera que ocurran.
-
-El siguiente ejemplo configura un entorno de prueba, registra un Increment Contract y verifica después de la invocación del incremento qué autenticaciones fueron necesarias.
-
-```rust
-#[test]
-fn test() {
-    let env = Env::default();
-    env.mock_all_auths();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    let user_1 = Address::random(&env);
-
-    assert_eq!(client.increment(&user_1, &5), 5);
-
-    // highlight-start
-    // Verify that the user indeed had to authorize a call of `increment` with
-    // the expected arguments:
-    assert_eq!(
-        // Get the auths that were seen in the last invocation.
-        env.auths(),
-        std::vec![(
-            // Address for which authorization check is performed
-            user_1.clone(),
-            // Invocation tree that needs to be authorized
-            AuthorizedInvocation {
-                // Function that is authorized. Can be a contract function or
-                // a host function that requires authorization.
-                function: AuthorizedFunction::Contract((
-                    // Address of the called contract
-                    contract_id.clone(),
-                    // Name of the called function
-                    symbol_short!("increment"),
-                    // Arguments used to call `increment` (converted to the
-                    // env-managed vector via `into_val`)
-                    (user_1.clone(), 5_u32).into_val(&env),
-                )),
-                // The contract doesn't call any other contracts that require
-                // authorization,
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-    // highlight-end
-}
-```
-
-:::tip
-
-Para el ejemplo completo del cual se extrae el fragmento anterior, consulta el [ejemplo de contrato de autenticación](../../smart-contracts/example-contracts/auth.mdx).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/test-contract-events.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/test-contract-events.mdx
deleted file mode 100644
index 903c873640..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/test-contract-events.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Eventos de Prueba
-hide_table_of_contents: true
-description: Escribe pruebas que verifiquen los eventos de contrato.
-sidebar_position: 4
----
-
-Las pruebas pueden afirmar sobre los eventos que se espera que se publiquen.
-
-El siguiente ejemplo establece un entorno de prueba, registra un Increment Contract y verifica, después de las invocaciones de incremento, qué eventos fueron publicados.
-
-```rust
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.increment(), 1);
-    assert_eq!(client.increment(), 2);
-    assert_eq!(client.increment(), 3);
-
-    // highlight-start
-    assert_eq!(
-        // Get all events published since the Env was created.
-        env.events().all(),
-        // Compare the events with the expected events.
-        vec![
-            &env,
-            (
-                contract_id.clone(),
-                (symbol_short!("COUNTER"), symbol_short!("increment")).into_val(&env),
-                1u32.into_val(&env)
-            ),
-            (
-                contract_id.clone(),
-                (symbol_short!("COUNTER"), symbol_short!("increment")).into_val(&env),
-                2u32.into_val(&env)
-            ),
-            (
-                contract_id,
-                (symbol_short!("COUNTER"), symbol_short!("increment")).into_val(&env),
-                3u32.into_val(&env)
-            ),
-        ]
-    );
-    // highlight-end
-}
-```
-
-:::tip
-
-Para el ejemplo completo del cual se extrajo el fragmento anterior, consulta el [ejemplo de contrato de eventos](../../smart-contracts/example-contracts/events.mdx).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/unit-tests.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/unit-tests.mdx
deleted file mode 100644
index 30eacaee97..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/testing/unit-tests.mdx
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Pruebas Unitarias
-hide_table_of_contents: true
-description: Las pruebas unitarias son pruebas pequeñas que prueban contratos inteligentes.
-sidebar_position: 1
----
-
-Las pruebas unitarias son pruebas pequeñas que prueban una pieza de funcionalidad dentro de un contrato.
-
-## Cómo Escribir Pruebas Unitarias
-
-Lo siguiente es un ejemplo de una prueba unitaria, escrita para testear el [Increment Contract](https://github.com/stellar/soroban-examples/blob/main/increment/src/lib.rs). El contrato tiene una función `increment`, que aumenta el valor de un contador en uno en cada invocación. La siguiente prueba invoca varias veces la función de ese contrato y comprueba que el valor aumenta en uno.
-
-```rust
-#![cfg(test)]
-use soroban_sdk::Env;
-use crate::{IncrementContract, IncrementContractClient};
-
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.increment(), 1);
-    assert_eq!(client.increment(), 2);
-    assert_eq!(client.increment(), 3);
-}
-```
-
-Ref: https://github.com/stellar/soroban-examples/blob/main/increment/src/test.rs
-
-En la prueba hay una configuración completa del entorno, utilizada y destruida en la prueba, y ocurre rápidamente. El arnés de prueba de Rust ejecuta todas las pruebas para un contrato en paralelo y cada una tendrá su propio entorno de contrato aislado.
-
-La mayoría de las pruebas, incluso las pruebas de integración y las pruebas de fuzz, se parecerán mucho a esta prueba unitaria. Hacer cuatro cosas:
-
-1. Crear un entorno, el `Env`.
-
-   ```rust
-   let env = Env::default();
-   ```
-
-2. Registrar el/los contrato(s) a probar. Incluye como segundo parámetro cualquier parámetro de constructor.
-
-   ```rust
-   let contract_id = env.register(IncrementContract, ());
-   ```
-
-3. Invoca funciones usando el cliente generado.
-
-   ```rust
-   let client = IncrementContractClient::new(&env, &contract_id);
-   client.increment()
-   ```
-
-4. Afirmar el resultado.
-
-   ```rust
-   assert_eq!(client.increment(), 1);
-   ```
-
-:::tip
-
-Las pruebas están escritas en Rust, junto con el contrato. Las mismas herramientas. Las mismas APIs. El mismo SDK. ¡Sin cambios de contexto! Utiliza tus herramientas y bibliotecas favoritas de Rust que usarías para cualquier prueba de Rust.
-
-:::
-
-:::info
-
-El `Env` creado al principio de la prueba no es una simulación del Entorno Soroban. Es el mismo entorno de Soroban que utiliza la mainnet para ejecutar contratos. Solo hay algunas diferencias menores: se habilitan utilidades de prueba y el backend de almacenamiento es diferente.
-
-:::
-
-Es una prueba simple, pero completa. Se realiza una configuración completa del entorno, se usa y se desmantela en la prueba, y todo ocurre rápido. El framework de pruebas de Rust ejecuta todas las pruebas de un contrato en paralelo y cada una tendrá su propio entorno de contrato aislado.
-
-La mayoría de las pruebas, incluso las pruebas de integración y las pruebas fuzz, serán muy similares a esta prueba unitaria. Harán cuatro cosas:
-
-1. Crear un entorno, el `Env`.
-2. Registrar el o los contratos que se probarán.
-3. Invocar funciones usando un cliente.
-4. Afirmar el resultado.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/README.mdx
deleted file mode 100644
index 247ae43c62..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/README.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Tokens del Contrato de Activos Stellar (SAC)
-description: Tokens y Contrato de Activos Stellar (SAC)
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 76
----
-
-El Contrato de Activos Stellar (SAC) es un estándar introducido en la blockchain Stellar para simplificar y mejorar la emisión y gestión de tokens. Aprender sobre el uso de tokens en Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/custom-sac-admin.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/custom-sac-admin.mdx
deleted file mode 100644
index 192403c36f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/custom-sac-admin.mdx
+++ /dev/null
@@ -1,157 +0,0 @@
----
-title: Establecer una cuenta de administrador personalizada para un Contrato de Activo Stellar (SAC)
-hide_table_of_contents: true
-description: Establecer una cuenta de administrador personalizada en un SAC desplegado
----
-
-El [Contrato de Activos Stellar (SAC)](../../../tokens/stellar-asset-contract.mdx) incluye funcionalidad para establecer una cuenta de administración personalizada en el contrato mismo. Esto puede permitir arreglos flexibles de administración de activos, que pueden configurarse para ajustarse a muchos casos de uso distintos.
-
-Por ejemplo, puedes establecer un administrador SAC personalizado y luego bloquear la cuenta del emisor, permitiendo que la administración de tokens se realice _exclusivamente_ a través del contrato SAC. O, podrías establecer un administrador SAC personalizado y aún mantener la cuenta del emisor desbloqueada, permitiendo un enfoque híbrido para la administración de tokens.
-
-:::info
-
-Se debe entender que la cuenta del emisor de un activo puede tener un conjunto distinto de firmas y pesos, y estos son independientes de la dirección del administrador SAC.
-
-:::
-
-## Consideraciones
-
-Para utilizar eficazmente la funcionalidad de administrador del SAC, debes ser consciente de varias cosas primero:
-
-- Cuando un SAC se habilita inicialmente para un activo emitido, la dirección `Admin` en el contrato por defecto es la cuenta del emisor.
-- Una dirección `Admin` de un SAC puede ser una cuenta Stellar normal (`G...`), o puede ser una dirección de smart contract (`C...`). Los casos de uso que requieren un contrato inteligente para actuar como un `Admin` SAC tienden a ser más comunes. Esto abre la posibilidad de acuñar programáticamente y tomar otras acciones administrativas para un activo a través de una invocación de smart contract.
-- Cambiar una dirección de `Admin` SAC requiere autorización de la dirección de `Admin` _actual_ del activo, que será la cuenta del emisor la primera vez que se realice la acción.
-
-Dependiendo del caso de uso, puede ser beneficioso para los emisores de activos acuñar una oferta total de tokens por adelantado y luego bloquear la cuenta del emisor. Esto mantendría la oferta total de tokens limitada para siempre. Puedes aprender más sobre esta práctica en la página de [consideraciones de diseño de activos](../../../tokens/control-asset-access.mdx#limiting-the-supply-of-an-asset). Sin embargo, dado que la cuenta del emisor y una dirección de `Admin` SAC actúan de manera independiente, hay algunos puntos interesantes que hacer que pueden parecer contradictorios a primera vista.
-
-- Si la cuenta del emisor de un activo está bloqueada mientras la dirección `Admin` del SAC no ha sido cambiada, _nunca_ será posible cambiar la dirección `Admin` del SAC. Esto es porque la cuenta del emisor ya no puede autorizar la primera invocación de `set_admin`.
-- Si la cuenta del emisor de un activo está bloqueada después de que se ha cambiado la dirección de `Admin` SAC, los tokens aún serán acuñables y/o recuperables (si se habilita) desde el SAC siempre que esté autorizado por la dirección de `Admin` _actual_.
-
-:::danger
-
-Al cambiar una dirección de `Admin` SAC, la nueva dirección de administrador proporcionada no se valida en ese momento. Esto significa que puedes bloquear la administración desde el SAC **para siempre**. Considera tu elección de dirección de `Admin` SAC con cuidado y a fondo.
-
-:::
-
-## Ejemplo
-
-El siguiente ejemplo generará un nuevo activo Stellar, `STAR:GCS5NEHKJALCSVJAKIORXXVS554QQV5FNDLBK33CCAH6UIRYPXYZFC34`. Luego, crearemos un contrato simple para regular un airdrop hipotético para el token. Este contrato se configurará como la dirección de `Admin` SAC para el activo `STAR`, y podrá realizar cualquier función administrativa que deseemos.
-
-:::note
-
-No demostraremos cómo establecer una nueva cuenta `G...` como un administrador SAC en esta guía. Cualquier caso de uso que requiera delegar la administración de activos a otra cuenta `G...` probablemente se beneficiará más al aprovechar las capacidades [multisig existentes](../../../learn/fundamentals/transactions/signatures-multisig.mdx) de las cuentas Stellar.
-
-:::
-
-### Habilitar el contrato SAC integrado
-
-Primero, habilitaremos el contrato SAC usando el CLI de Stellar:
-
-```shell
-stellar contract asset deploy \
-    --source-account starIssuer --network testnet \
-    --asset STAR:GCS5NEHKJALCSVJAKIORXXVS554QQV5FNDLBK33CCAH6UIRYPXYZFC34
-# CBVYF2KJ72BRPLVPCUL3PGWDO5RK2XP4AJDHKX7GDDBJW42L2C6VT3SF
-```
-
-Esto nos da la dirección SAC de `CBVYF2KJ72BRPLVPCUL3PGWDO5RK2XP4AJDHKX7GDDBJW42L2C6VT3SF`.
-
-:::note
-
-Estamos utilizando la cuenta emisora del activo aquí para habilitar el SAC en la red Testnet, pero esta acción se puede realizar usando _cualquier_ cuenta.
-
-:::
-
-### Verifica la dirección de `Admin` inicial
-
-Ahora que tenemos el SAC desplegado en la red, podemos invocar la función `admin` para averiguar cuál es su dirección `Admin` actual:
-
-```shell
-stellar contract invoke \
-    --source-account starIssuer --network testnet \
-    --id CBVYF2KJ72BRPLVPCUL3PGWDO5RK2XP4AJDHKX7GDDBJW42L2C6VT3SF \
-    -- \
-    admin
-# GCS5NEHKJALCSVJAKIORXXVS554QQV5FNDLBK33CCAH6UIRYPXYZFC34
-```
-
-No es sorprendente que esté configurada en la cuenta `GCS5...` del emisor. Cambiemos eso.
-
-### Establecer la dirección `Admin` en alguna dirección de contrato `C...`
-
-Para esta parte del ejemplo, utilizaremos un contrato simple de "airdrop" como la dirección `Admin`. Tiene una implementación muy simple, y solo una función principal, `claim_airdrop`. Cada vez que alguien invoca esa función, 12.3456789 `STAR` se acuñará en su cuenta.
-
-```rust
-#[contractimpl]
-impl Contract {
-    pub fn __constructor(env: Env, sac_address: Address) {
-        env.storage().instance().set(&symbol_short!("SAC_ADDR"), &sac_address);
-    }
-
-    pub fn claim_airdrop(env: Env, receiver: Address) {
-        if env.storage().persistent().has(&receiver) {
-            panic!("receiver has already claimed")
-        }
-
-        receiver.require_auth();
-        let amount: i128 = 123456789;
-        env.storage().persistent().set(&receiver, &amount);
-
-        let sac_address: Address = env.storage().instance().get(&symbol_short!("SAC_ADDR")).unwrap();
-        let token_client = token::StellarAssetClient::new(&env, &sac_address);
-        token_client.mint(&receiver, &amount);
-    }
-}
-```
-
-Este contrato se despliega, y la dirección podría ser (por ejemplo) `CBCGKTU6CD25S2E7SEMJ72MQUL4XEGAXAJ43GQE3HSYOZKZ4C4LOH756`. Ahora podemos establecer la dirección `Admin` del SAC en este contrato:
-
-```sh
-stellar contract invoke \
-    --source-account starIssuer --network testnet \
-    --id CBVYF2KJ72BRPLVPCUL3PGWDO5RK2XP4AJDHKX7GDDBJW42L2C6VT3SF \
-    -- \
-    set_admin --new_admin CBCGKTU6CD25S2E7SEMJ72MQUL4XEGAXAJ43GQE3HSYOZKZ4C4LOH756
-```
-
-Al verificar nuestro trabajo con la función `admin` del SAC, veremos que nuestro contrato de airdrop es ahora la dirección `Admin`:
-
-```shell
-stellar contract invoke \
-    --source-account starIssuer --network testnet \
-    --id CBVYF2KJ72BRPLVPCUL3PGWDO5RK2XP4AJDHKX7GDDBJW42L2C6VT3SF \
-    -- \
-    admin
-# CBCGKTU6CD25S2E7SEMJ72MQUL4XEGAXAJ43GQE3HSYOZKZ4C4LOH756
-```
-
-Ahora, dado que el contrato de airdrop es el administrador del SAC, podemos invocar su función `claim_airdrop` desde cualquier cuenta que deseemos. (Recordatorio: si estás usando una dirección `G...` como destino para la función `mint` de un SAC, necesitará tener creada una trustline para el activo de antemano.)
-
-```sh
-stellar contract invoke \
-    --source-account randomStarHolder --network testnet \
-    --id CBCGKTU6CD25S2E7SEMJ72MQUL4XEGAXAJ43GQE3HSYOZKZ4C4LOH756 \
-    -- \
-    claim_airdrop --receiver randomStarHolder
-```
-
-Ahora, esta cuenta `randomStarHolder` tendrá un saldo de 12.3456789 `STAR`, y la acuñación del token fue ejecutada por el contrato de airdrop en sí.
-
-### Realizando una operación de `payment` desde la cuenta del emisor
-
-Dado que no hemos bloqueado al/los firmante(s) de nuestra cuenta del emisor, todavía es completamente posible que la cuenta del emisor `GCS5...` cree y envíe a la red cualquier operación de `payment` que desee. Esto significa que los tokens aún podrían ser acuñados con una operación de `payment`, o quemados con una operación de `clawback`, o modificados los flags de trustline, etc., todo utilizando la cuenta del emisor original del activo. La dirección `Admin` del SAC y los permisos de firma de la cuenta emisora operan y funcionan de manera independiente entre sí.
-
-## En la práctica
-
-Un ejemplo divertido de un proyecto que utiliza una dirección de administrador personalizada en un SAC se puede encontrar con el [Proyecto `KALE`](https://github.com/kalepail/KALE-sc). El emisor de KALE es `GBDVX4VELCDSQ54KQJYTNHXAHFLBCA77ZY2USQBM4CSHTTV7DME7KALE`, pero puedes ver que la dirección `Admin` para el SAC está establecida en otro contrato:
-
-```sh
-stellar contract invoke \
-    --source-account S...ECRETKEY --network mainnet \
-    --id CB23WRDQWGSP6YPMY4UV5C4OW5CBTXKYN3XEATG7KJEZCXMJBYEHOUOV \
-    -- \
-    admin
-# CDL74RF5BLYR2YBLCCI7F5FB6TPSCLKEJUBSD2RSVWZ4YHF3VMFAIGWA
-```
-
-Este [contrato `CDL7...`](https://stellar.expert/explorer/public/contract/CDL74RF5BLYR2YBLCCI7F5FB6TPSCLKEJUBSD2RSVWZ4YHF3VMFAIGWA) es el contrato "homestead" creado para facilitar la acuñación/quema/minado del activo `KALE`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/deploying-a-sac.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/deploying-a-sac.mdx
deleted file mode 100644
index ebd8fe3de7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/deploying-a-sac.mdx
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Desplegar un contrato de activo Stellar (SAC) desde dentro de un contrato
-hide_table_of_contents: true
-description: Desplegar un SAC desde otro contrato inteligente utilizando el SDK de Rust
----
-
-<head>
-  <title>
-    {`Desplegando un contrato de activo Stellar (SAC) desde dentro de un contrato`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Desplegando un contrato de activo Stellar (SAC) desde dentro de un contrato"
-  />
-  <meta
-    property="og:description"
-    content="Esta es una guía paso a paso para ayudarte a desplegar un SAC desde dentro de un contrato inteligente en Stellar."
-  />
-</head>
-
-## Resumen
-
-En esta guía, aprenderás a desplegar un [contrato de activo Stellar (SAC)](../../../tokens/stellar-asset-contract.mdx) desde dentro de otro contrato inteligente utilizando el SDK de Rust de Soroban. El SDK de Rust de Soroban proporciona herramientas y utilidades para trabajar con contratos inteligentes de Stellar, permitiéndote desplegar e interactuar con los SAC directamente desde la lógica de tu contrato. El SDK de Rust de Soroban proporciona herramientas y utilidades para trabajar con contratos inteligentes Stellar, permitiéndote desplegar e interactuar con los SAC directamente desde la lógica de tu contrato.
-
-## Requisitos previos:
-
-Antes de comenzar, asegúrate de tener lo siguiente:
-
-- Conocimiento básico del [lenguaje de programación Rust](https://www.rust-lang.org/). Para refrescar tus conocimientos sobre Rust, consulta [Rustlings](https://github.com/rust-lang/rustlings) o [El libro de Rust](https://doc.rust-lang.org/book/).
-- [Soroban Rust SDK](../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk) instalado y configurado en tu entorno de desarrollo.
-- Conocimiento básico del SDK de Rust de Soroban y familiaridad con los conceptos fundamentales de Soroban y la programación en Rust.
-
-## 1. Definir el contrato SacDeployer
-
-El contrato SacDeployer será responsable de desplegar el contrato de activo Stellar. Aquí está el código para el contrato SacDeployer:
-
-```rust title="lib.rs"
-use soroban_sdk::{contract, contractimpl, Env, Address, Bytes};
-
-#[contract]
-pub struct SacDeployer;
-
-#[contractimpl]
-impl SacDeployer {
-    pub fn deploy_sac(env: Env, serialized_asset: Bytes) -> Address {
-        // Create the Deployer with Asset
-        let deployer = env.deployer().with_stellar_asset(serialized_asset);
-        let _ = deployer.deployed_address();
-        // Deploy the Stellar Asset Contract
-        let sac_address = deployer.deploy();
-
-        sac_address
-    }
-}
-```
-
-### Explicación
-
-- `SacDeployer` contrato: este contrato define la función `deploy_sac` para manejar el despliegue del SAC.
-- Función `deploy_sac`:
-  - `env.deployer().with_stellar_asset(serialized_asset)`: crea un desplegador configurado para desplegar un contrato de activo Stellar utilizando el activo serializado proporcionado.
-  - `deployer.deploy()`: Despliega el SAC y devuelve la dirección del contrato desplegado.
-
-## 2. Probar el despliegue
-
-Necesitas probar el despliegue para asegurarte de que todo funcione como se espera. El siguiente código demuestra cómo probar el contrato SacDeployer utilizando las utilidades de prueba del SDK de Rust de Soroban.
-
-```rust
-#[cfg(feature = "testutils")]
-fn main() {
-    let env = TestEnv::default();
-    let serialized_asset = Bytes::from("actual serialized asset"); // Replace with actual serialized asset info
-    let sac_deployer = SacDeployer::default();
-    let sac_address = sac_deployer.deploy_sac(env.clone(), serialized_asset);
-    println!("SAC Address: {}", sac_address.to_string());
-}
-```
-
-### Explicación
-
-- `TestEnv::default()`: crea un entorno de prueba predeterminado para el despliegue.
-- `SacDeployer::default()`: inicializa el contrato SacDeployer.
-- `deploy_sac(env.clone(), serialized_asset)`: llama a la función `deploy_sac` para desplegar el SAC y recupera la dirección.
-- `println!("Dirección SAC: {}", sac_address.to_string())`: imprime la dirección del SAC desplegado.
-- `assert!(sac_address.to_string().len() > 0, "La dirección SAC debería ser no vacía")`: afirma que la dirección del SAC no está vacía, asegurando un despliegue exitoso.
-- `serialized_asset` es el `Asset` XDR de Stellar serializado en bytes. Consulta `[soroban_sdk::xdr::Asset]` [XDR](https://docs.rs/stellar-xdr/latest/stellar_xdr/curr/enum.Asset.html)
-
-### Conclusión
-
-Siguiendo esta guía, has desplegado con éxito un contrato de activo Stellar desde dentro de otro contrato utilizando el SDK de Rust de Soroban. Este enfoque permite que los contratos inteligentes manejen los despliegues de SAC de manera dinámica, proporcionando flexibilidad para varios casos de uso en el ecosistema Stellar.
-
-Para más detalles, consulta la documentación del SDK de Soroban y explora características y configuraciones más avanzadas.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/stellar-asset-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/stellar-asset-contract.mdx
deleted file mode 100644
index 342e9c113e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/tokens/stellar-asset-contract.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Integrar Contratos de Activos Stellar
-hide_table_of_contents: true
-description: Probar y usar activos Stellar en un contrato inteligente Stellar
----
-
-Al interactuar con activos en un contrato inteligente, el [Contrato de Activos Stellar](../../../tokens/stellar-asset-contract.mdx) no es diferente de cualquier otro token que implemente la [Interfaz de Token SEP-41] de Stellar.
-
-## Código del Contrato
-
-El SDK de Rust contiene un cliente pre-generado para cualquier contrato que implemente la interfaz de token:
-
-```rust
-use soroban_sdk::{contract, contractimpl}
-use soroban_sdk::token;
-
-#[contract]
-pub struct MyContract;
-
-#[contractimpl]
-impl MyContract {
-    pub fn token_fn(e: Env, id: Address) {
-        // Create a client instance for the provided token identifier. If the id
-        // value corresponds to an SAC contract, then SAC implementation is used.
-        let client = token::TokenClient::new(&env, &id);
-        // Call token functions part of the Stellar SEP-41 token interface
-        client.transfer(...);
-    }
-}
-```
-
-El parámetro `asset` no es la dirección del emisor de un activo, corresponde a la dirección del contrato desplegado para este activo.
-
-```bash
-stellar contract id asset \
-    --source-account G... \
-    --network testnet \
-    --asset [asset:issuer]
-```
-
-Por ejemplo. para USDC, sería `--asset USDC:G...` Para el activo nativo, XLM, `--asset native`. Consulta la guía de [despliegue SAC] para más detalles.
-
-[desplegar SAC]: ../../../tools/cli/cookbook/deploy-stellar-asset-contract.mdx
-
-:::info[Clients]
-
-Un cliente creado por [`token::TokenClient`] implementa las funciones definidas por cualquier contrato que implemente la [Interfaz de Token SEP-41]. Pero con [el activo estandarizado de contrato inteligente CAP-46-6], el Contrato de Activos Stellar expone funciones adicionales como `mint`. Para acceder a las funciones adicionales, se necesita usar otro cliente: [`token::StellarAssetClient`]. Este cliente solo implementa las funciones de CAP-46-6, que no son parte de la interfaz SEP-41.
-
-```rust
-let client = token::StellarAssetClient::new(&env, &id);
-// Call token functions which are not part of the SEP-41 token interface
-// but part of the CAP-46-6 Smart Contract Standardized Asset
-client.mint(...);
-```
-
-:::
-
-## Pruebas
-
-El SDK de Soroban Rust proporciona una manera fácil de instanciar tokens de Contrato de Activos Stellar usando `register_stellar_asset_contract_v2`. Esta función puede verse como el despliegue de un token genérico. Esta función puede verse como el despliegue de un token genérico. También te permite manipular flags en la cuenta del emisor como `AUTH_REVOCABLE` y `AUTH_REQUIRED`. En el siguiente ejemplo, estamos siguiendo las prácticas recomendadas descritas en la [sección de Cuentas de Emisión y Distribución](../../../tokens/control-asset-access.mdx#issuing-and-distribution-accounts):
-
-```rust
-#![cfg(test)]
-
-use soroban_sdk::testutils::Address as _;
-use soroban_sdk::{token, Address, Env};
-use token::{StellarAssetClient, TokenClient};
-
-#[test]
-fn test() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    let issuer = Address::generate(&e);
-    let distributor = Address::generate(&e);
-
-    let sac = e.register_stellar_asset_contract_v2(issuer.clone());
-    let token_address = sac.address();
-
-    // client for SEP-41 functions
-    let token = TokenClient::new(&e, &token_address);
-    // client for Stellar Asset Contract functions
-    let token_sac = StellarAssetClient::new(&e, &token_address);
-
-    // note that you need to account for the difference between the minimal
-    // unit and the unit itself when working with amounts.
-    // E.g. to mint 1 TOKEN, we need to use 1*1e7 in the mint function.
-    let genesis_amount: i128 = 1_000_000_000 * 10_000_000;
-
-    token_sac.mint(&distributor, &genesis_amount);
-
-    assert_eq!(token.balance(&distributor), genesis_amount);
-
-    // Make issuer AuthRequired and AuthRevocable
-    sac.issuer().set_flag(IssuerFlags::RevocableFlag);
-    sac.issuer().set_flag(IssuerFlags::RequiredFlag);
-}
-```
-
-## Ejemplos
-
-Consulta los ejemplos completos que utilizan el contrato de token de diversas maneras para más detalles:
-
-- [Timelock](../../smart-contracts/example-contracts/timelock.mdx) y [oferta única](../../smart-contracts/example-contracts/single-offer-sale.mdx) mueven tokens a través de `transfer` hacia y desde el contrato
-- [Intercambio atómico](../../smart-contracts/example-contracts/atomic-swap.mdx) usa `transfer` para transferir tokens en nombre del usuario
-
-[interfaz de token sep-41]: ../../../tokens/token-interface.mdx
-[activo estandarizado de contrato inteligente cap-46-6]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-06.md
-[`token::tokenclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.TokenClient.html
-[`token::stellarassetclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.StellarAssetClient.html
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/README.mdx
deleted file mode 100644
index bbc9b73fa7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Transacciones
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 120
----
-
-Las transacciones de Stellar están compuestas por operaciones. Estas guías te llevarán a través de diversas operaciones de Stellar, transacciones sin contrato y transacciones con contrato inteligente. Lee más sobre operaciones y transacciones en la [sección de Operaciones y Transacciones](../../../learn/fundamentals/transactions/README.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/channel-accounts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/channel-accounts.mdx
deleted file mode 100644
index c8f969b00e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/channel-accounts.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Cuentas canalizadas
-description: Crea cuentas canalizadas para enviar transacciones a la red a una alta velocidad.
-sidebar_position: 10
----
-
-Las cuentas canalizadas proporcionan un método para enviar transacciones a la red a una alta velocidad.
-
-Las transacciones de una cuenta siempre deben enviarse a la red con incrementos de un número de secuencia (a menos que se establezcan condiciones previas de número de secuencia mínimo). Esto puede causar problemas si envías transacciones a una alta velocidad, ya que pueden llegar a Stellar Core fuera de orden y serán rechazadas con un error de secuencia incorrecta.
-
-Para evitar esto, puedes crear cuentas canalizadas separadas que se puedan usar como cuenta origen para la transacción y usar la cuenta que posee los activos como cuenta base o como cuenta origen para las operaciones individuales dentro de la transacción. En este escenario, los activos saldrán de la cuenta base, y el número de secuencia y las comisiones serán consumidos por la cuenta canalizada.
-
-Los canales aprovechan el hecho de que la cuenta origen de una transacción puede ser diferente de la cuenta origen de las operaciones dentro de la transacción. Con esta configuración, puedes crear tantas cuentas canalizadas como necesites para mantener la tasa de transacciones deseada.
-
-Por supuesto, tendrás que firmar la transacción tanto con la keypair de la cuenta base como con la keypair de la cuenta canalizada.
-
-Por ejemplo:
-
-<CodeExample>
-
-```js
-// channelAccounts[] is an array of accountIDs, one for each channel
-// channelKeys[] is an array of secret keys, one for each channel
-// channelIndex is the channel you want to send this transaction over
-
-// create payment from baseAccount to customerAddress
-var transaction = new StellarSdk.TransactionBuilder(
-  channelAccounts[channelIndex],
-  {
-    fee: StellarSdk.BASE_FEE,
-    networkPassphrase: StellarSdk.Networks.TESTNET,
-  },
-)
-  .addOperation(
-    StellarSdk.Operation.payment({
-      source: baseAccount.address(),
-      destination: customerAddress,
-      asset: StellarSdk.Asset.native(),
-      amount: amountToSend,
-    }),
-  )
-  // Wait a maximum of three minutes for the transaction
-  .setTimeout(180)
-  .build();
-
-transaction.sign(baseAccountKey); // base account must sign to approve the payment
-transaction.sign(channelKeys[channelIndex]); // channel must sign to approve it being the source of the transaction
-```
-
-```python
-# channelAccounts[] is an array of accountIDs, one for each channel
-# channelKeys[] is an array of secret keys, one for each channel
-# channelIndex is the channel you want to send this transaction over
-
-transaction = (
-    TransactionBuilder(
-      source_account=channelAccounts[channelIndex],
-      network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-      base_fee=base_fee,
-    )
-    .append_payment_op(
-      source=baseAccount.public_key,
-      destination=customerAddress,
-      asset=Asset.native(),
-      amount=amountToSend,
-    )
-    .set_timeout(180) # Wait a maximum of three minutes for the transaction
-    .build()
-)
-
-transaction.sign(baseAccountKey) # base account must sign to approve the payment
-transaction.sign(channelKeys[channelIndex]) # channel must sign to approve it being the source of the transaction
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/claimable-balances.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/claimable-balances.mdx
deleted file mode 100644
index 45eacbd9d8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/claimable-balances.mdx
+++ /dev/null
@@ -1,702 +0,0 @@
----
-title: Saldos reclamables
-description: Divide un pago en dos partes creando un saldo reclamable.
-sidebar_position: 20
----
-
-import Details from "@theme/Details";
-
-Los saldos reclamables fueron introducidos en [CAP-0023](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) y se usan para dividir un pago en dos partes.
-
-- Parte 1: la cuenta que envía crea un pago, o ClaimableBalanceEntry, usando la operación Create Claimable Balance
-- Parte 2: la(s) cuenta(s) destinataria(s), o reclamante(s), acepta(n) el ClaimableBalanceEntry usando la operación Claim Claimable Balance
-
-Los saldos reclamables permiten que una cuenta envíe un pago a otra cuenta que no necesariamente está preparada para recibir el pago. Pueden usarse cuando envías un activo no nativo a una cuenta que aún no ha establecido una trustline, lo cual puede ser útil para anchors que integran nuevos usuarios. El reclamante debe establecer una trustline para el activo antes de poder reclamar el saldo reclamable; de lo contrario, la reclamación resultará en un error `op_no_trust`.
-
-Es importante notar que si un saldo reclamable no es reclamado, permanece en el ledger para siempre, ocupando espacio y, en última instancia, haciendo que la red sea menos eficiente. **Por esta razón, es buena idea poner una de tus propias cuentas como reclamante de un saldo reclamable.** Así puedes aceptar tu propio saldo reclamable si es necesario, liberando espacio en la red.
-
-Cada ClaimableBalanceEntry es una entrada del ledger, y cada reclamante en esa entrada incrementa el balance mínimo de la cuenta fuente en una reserva base.
-
-Una vez que un ClaimableBalanceEntry ha sido reclamado, es eliminado.
-
-## Operaciones
-
-### Crear saldo reclamable
-
-Para parámetros básicos, consulta la entrada Crear saldo reclamable en nuestra [sección Lista de operaciones](../../../learn/fundamentals/transactions/list-of-operations.mdx#create-claimable-balance).
-
-#### Parámetros adicionales
-
-`Claim_Predicate_` Reclamante — un objeto que contiene tanto la cuenta destino que puede reclamar el ClaimableBalanceEntry como un ClaimPredicate que debe evaluarse como verdadero para que la reclamación tenga éxito.
-
-Un ClaimPredicate es una estructura de datos recursiva que puede usarse para construir condicionales complejos usando diferentes ClaimPredicateTypes. A continuación, algunos ejemplos con el prefijo `Claim_Predicate_` removido para mayor legibilidad. Ten en cuenta que los SDKs esperan que las marcas de tiempo Unix estén expresadas en segundos.
-
-- Puede reclamar en cualquier momento - `UNCONDITIONAL`
-- Puede reclamar si el tiempo de cierre del ledger, incluyendo la reclamación, es antes de X segundos + el tiempo de cierre del ledger en el que se creó el ClaimableBalanceEntry - `BEFORE_RELATIVE_TIME(X)`
-- Puede reclamar si el tiempo de cierre del ledger incluyendo la reclamación es antes de X (marca de tiempo Unix) - `BEFORE_ABSOLUTE_TIME(X)`
-- Puede reclamar si el tiempo de cierre del ledger, incluyendo la reclamación, es en o después de X segundos + el tiempo de cierre del ledger en el que se creó el ClaimableBalanceEntry - `NOT(BEFORE_RELATIVE_TIME(X))`
-- Puede reclamar si el tiempo de cierre del ledger, incluyendo la reclamación, es en o después de X (marca de tiempo Unix) - `NOT(BEFORE_ABSOLUTE_TIME(X))`
-- Puede reclamar entre las marcas de tiempo Unix X e Y (dado que X < Y) - `AND(NOT(BEFORE_ABSOLUTE_TIME(X))`, `BEFORE_ABSOLUTE_TIME(Y))`
-- Puede reclamar fuera de las marcas de tiempo Unix X e Y (dado que X < Y) - `OR(BEFORE_ABSOLUTE_TIME(X)`, `NOT(BEFORE_ABSOLUTE_TIME(Y))`
-
-`ClaimableBalanceID` ClaimableBalanceID es una unión con un posible tipo (`CLAIMABLE_BALANCE_ID_TYPE_V0`). Contiene un hash SHA-256 del OperationID para Saldos Reclamables.
-
-Una operación Crear saldo reclamable exitosa devolverá un ID de Balance, que es requerido al reclamar el ClaimableBalanceEntry con la operación Claim Claimable Balance.
-
-### Reclamar saldo reclamable
-
-Para parámetros básicos, consulta la entrada Reclamar saldo reclamable en nuestra [sección Lista de operaciones](../../../learn/fundamentals/transactions/list-of-operations#claim-claimable-balance).
-
-Esta operación cargará el ClaimableBalanceEntry que corresponde al Balance ID y luego buscará la cuenta fuente de esta operación en la lista de reclamantes de la entrada. Si se encuentra una coincidencia en el reclamante, y el ClaimPredicate evalúa a verdadero, entonces el ClaimableBalanceEntry puede ser reclamado. El saldo en la entrada será transferido a la cuenta fuente si no hay problemas de límite o trustline (para activos no nativos), lo que significa que el reclamante debe establecer una trustline para el activo antes de reclamarlo.
-
-### Recuperar saldo reclamable
-
-Esta operación recupera un saldo reclamable, devolviendo el activo a la cuenta emisora, quemándolo. Debes recuperar el saldo reclamable completo, no solo una parte. Una vez que un saldo reclamable ha sido reclamado, usa la operación regular de recuperación para recuperarlo.
-
-Las recuperaciones de saldos reclamables requieren el ID del saldo reclamable.
-
-Aprende más sobre recuperaciones en nuestra [Guía de recuperaciones](./clawbacks.mdx).
-
-## Ejemplo
-
-El código a continuación demuestra, mediante los SDKs de JavaScript y Go, cómo una cuenta (Cuenta A) crea un ClaimableBalanceEntry con dos reclamantes: Cuenta A (ella misma) y Cuenta B (otro destinatario).
-
-Cada una de estas cuentas solo puede reclamar el saldo bajo condiciones únicas. La Cuenta B tiene un minuto completo para reclamar el saldo antes de que la Cuenta A pueda recuperarlo para sí misma.
-
-**Nota:** en general no existe un mecanismo de recuperación para un saldo reclamable — si ninguno de los predicados puede cumplirse, el saldo no puede recuperarse. El ejemplo de recuperación a continuación funciona como una red de seguridad para esta situación.
-
-<Details summary="Haz clic aquí para ver funciones auxiliares">
-
-<CodeExample>
-
-```go
-func fundAccount(rpcClient *client.Client, address string) error {
-	ctx := context.Background()
-
-	// Use GetNetwork method from client
-	networkResp, err := rpcClient.GetNetwork(ctx)
-	if err != nil {
-		return err
-	}
-
-	if networkResp.FriendbotURL != "" {
-		friendbotURL := networkResp.FriendbotURL + "?addr=" + url.QueryEscape(address)
-		resp, err := http.Post(friendbotURL, "application/x-www-form-urlencoded", nil)
-		if err != nil {
-			return err
-		}
-		defer resp.Body.Close()
-
-		if resp.StatusCode != 200 {
-			return fmt.Errorf("friendbot failed with status: %d", resp.StatusCode)
-		}
-		return nil
-	}
-
-	return fmt.Errorf("friendbot not configured for network - %s", networkResp.Passphrase)
-}
-
-func panicIf(err error) {
-	if err != nil {
-		log.Fatal(err)
-	}
-}
-```
-
-</CodeExample>
-
-</Details>
-
-<CodeExample>
-
-```js
-import * as StellarSdk from "@stellar/stellar-sdk";
-
-/**
- * Creates a claimable balance on Stellar testnet
- * A claimable balance allows splitting a payment into two parts:
- * 1. Sender creates the claimable balance
- * 2. Recipient(s) can claim it later
- */
-async function createClaimableBalance() {
-  // Connect to Stellar testnet RPC server
-  const server = new StellarSdk.rpc.Server(
-    "https://soroban-testnet.stellar.org",
-  );
-
-  const A = StellarSdk.Keypair.random();
-  const B = StellarSdk.Keypair.random();
-
-  console.log(
-    `Account A... public key: ${A.publicKey()}, secret: ${A.secret()}`,
-  );
-  console.log(
-    `Account B... public key: ${B.publicKey()}, secret: ${B.secret()}`,
-  );
-
-  try {
-    // Fund the source account using testnet's built-in airdrop
-    await server.requestAirdrop(A.publicKey());
-
-    // Load the funded account to get current sequence number
-    const aAccount = await server.getAccount(A.publicKey());
-    console.log(`Account sequence: ${aAccount.sequenceNumber()}`);
-
-    // Create a claimable balance with our two above-described conditions.
-    let soon = Math.ceil(Date.now() / 1000 + 60); // .now() is in ms
-    let bCanClaim = StellarSdk.Claimant.predicateBeforeRelativeTime("60");
-    let aCanReclaim = StellarSdk.Claimant.predicateNot(
-      StellarSdk.Claimant.predicateBeforeAbsoluteTime(soon.toString()),
-    );
-
-    // Create claimable balance operation
-    const claimableBalanceOp = StellarSdk.Operation.createClaimableBalance({
-      claimants: [
-        new StellarSdk.Claimant(B.publicKey(), bCanClaim),
-        new StellarSdk.Claimant(A.publicKey(), aCanReclaim),
-      ],
-      asset: StellarSdk.Asset.native(),
-      amount: "420",
-    });
-
-    // Build the transaction
-    console.log(`Building transaction...`);
-    const transaction = new StellarSdk.TransactionBuilder(aAccount, {
-      fee: StellarSdk.BASE_FEE,
-      networkPassphrase: StellarSdk.Networks.TESTNET,
-    })
-      .addOperation(claimableBalanceOp)
-      .setTimeout(180)
-      .build();
-
-    /*
-      Claimable BalanceIds are predictable and can be derived from the Sha256 hash of the operation that creates them.
-    */
-    const predictableBalanceId = transaction.getClaimableBalanceId(0);
-
-    // Sign the transaction with source account
-    transaction.sign(A);
-
-    // Submit transaction to the network
-    console.log(`Submitting transaction...`);
-    const response = await server.sendTransaction(transaction);
-
-    // Poll for transaction completion (RPC is asynchronous)
-    console.log(`Polling for result...`);
-    const finalResponse = await server.pollTransaction(response.hash);
-
-    if (finalResponse.status === "SUCCESS") {
-      // Extract claimable balance ID from transaction result
-      const txResult = finalResponse.resultXdr;
-      const results = txResult.result().results();
-      const operationResult = results[0].value().createClaimableBalanceResult();
-      const balanceId = operationResult.balanceId().toXDR("hex");
-
-      console.log(`Balance ID (from txResult): ${balanceId}`);
-      console.log(
-        `Predictable Balance ID (obtained before txSubmission): ${predictableBalanceId}`,
-      );
-      if (balanceId === predictableBalanceId) {
-        console.log(`Balance ID from txResult matches the predictable ID`);
-      } else {
-        console.log(
-          ` Balance ID from txResult does NOT match the predictable ID`,
-        );
-      }
-    } else {
-      console.log(`Transaction failed: ${finalResponse.status}`);
-    }
-  } catch (error) {
-    console.error(`Error: ${error.message}`);
-  }
-}
-
-// Run the function
-createClaimableBalance();
-```
-
-```go
-package main
-
-import (
-	"context"
-	"fmt"
-	"log"
-	"net/http"
-	"net/url"
-	"time"
-
-	"github.com/stellar/stellar-rpc/client"
-	"github.com/stellar/stellar-rpc/protocol"
-
-	"github.com/stellar/go-stellar-sdk/keypair"
-	"github.com/stellar/go-stellar-sdk/network"
-	"github.com/stellar/go-stellar-sdk/txnbuild"
-	"github.com/stellar/go-stellar-sdk/xdr"
-)
-
-func main() {
-	// Create RPC client
-	rpcClient := client.NewClient("https://soroban-testnet.stellar.org", nil)
-	defer rpcClient.Close()
-
-	// Generate random keypairs
-	A := keypair.MustRandom()
-	B := keypair.MustRandom()
-
-	fmt.Printf("Account A: public key: %s, secret key: %s\n", A.Address(), A.Seed())
-	fmt.Printf("Account B: public key: %s\n", B.Address())
-
-	// Fund account using GetNetwork + friendbot
-	fmt.Println("\nFunding account...")
-	panicIf(fundAccount(rpcClient, A.Address()))
-	fmt.Println("Account funded")
-
-	// Wait for funding
-	time.Sleep(3 * time.Second)
-
-	// Use LoadAccount method from the client
-	ctx := context.Background()
-	sourceAccount, err := rpcClient.LoadAccount(ctx, A.Address())
-	panicIf(err)
-
-	// Create a claimable balance with our two above-described conditions.
-	soon := time.Now().Add(time.Second * 60)
-	bCanClaim := txnbuild.BeforeRelativeTimePredicate(60)
-	aCanReclaim := txnbuild.NotPredicate(
-		txnbuild.BeforeAbsoluteTimePredicate(soon.Unix()),
-	)
-
-	// Create claimable balance operation
-	claimableBalanceOp := txnbuild.CreateClaimableBalance{
-		Destinations: []txnbuild.Claimant{
-			txnbuild.NewClaimant(B.Address(), &bCanClaim),
-			txnbuild.NewClaimant(A.Address(), &aCanReclaim),
-		},
-		Asset:  txnbuild.NativeAsset{},
-		Amount: "1",
-	}
-
-	// Build transaction
-	tx, err := txnbuild.NewTransaction(
-		txnbuild.TransactionParams{
-			SourceAccount:        sourceAccount,
-			IncrementSequenceNum: true,
-			BaseFee:              txnbuild.MinBaseFee,
-			Preconditions:        txnbuild.Preconditions{TimeBounds: txnbuild.NewInfiniteTimeout()},
-			Operations:           []txnbuild.Operation{&claimableBalanceOp},
-		},
-	)
-	panicIf(err)
-
-	// Sign transaction
-	tx, err = tx.Sign(network.TestNetworkPassphrase, A)
-	panicIf(err)
-
-	// Get transaction XDR
-	txXDR, err := tx.Base64()
-	panicIf(err)
-
-	// Submit using RPC client's SendTransaction method
-	fmt.Println("Submitting transaction...")
-	sendResp, err := rpcClient.SendTransaction(ctx, protocol.SendTransactionRequest{
-		Transaction: txXDR,
-	})
-	panicIf(err)
-
-	if sendResp.Status != "PENDING" {
-		log.Fatalf("Transaction not pending: %s", sendResp.Status)
-	}
-
-	fmt.Printf("Transaction submitted: %s\n", sendResp.Hash)
-
-	// Poll using RPC client's GetTransaction method
-	fmt.Println("Polling for result...")
-	for i := 0; i < 10; i++ {
-		resp, err := rpcClient.GetTransaction(ctx, protocol.GetTransactionRequest{
-			Hash: sendResp.Hash,
-		})
-		if err != nil {
-			log.Printf("Error getting transaction: %v", err)
-			time.Sleep(1 * time.Second)
-			continue
-		}
-
-		if resp.Status != protocol.TransactionStatusNotFound {
-			if resp.Status == protocol.TransactionStatusSuccess {
-				// Extract balance ID
-				balanceID, err := extractBalanceID(&resp)
-				if err != nil {
-					log.Printf("Error extracting balance ID: %v", err)
-				} else {
-					fmt.Println("\nSUCCESS: Claimable balance created")
-					fmt.Printf("Balance ID: %s\n", balanceID)
-				}
-			} else {
-				fmt.Printf("Transaction failed: %s\n", resp.Status)
-			}
-			return
-		}
-
-		time.Sleep(time.Duration(i+1) * time.Second)
-	}
-
-	fmt.Println("Transaction polling timeout")
-}
-
-func extractBalanceID(resp *protocol.GetTransactionResponse) (string, error) {
-	if resp.ResultXDR == "" {
-		return "", fmt.Errorf("no result XDR")
-	}
-
-	var txResult xdr.TransactionResult
-	err := xdr.SafeUnmarshalBase64(resp.ResultXDR, &txResult)
-	if err != nil {
-		return "", err
-	}
-
-	if results, ok := txResult.OperationResults(); ok && len(results) > 0 {
-		operationResult := results[0].MustTr().CreateClaimableBalanceResult
-		return xdr.MarshalHex(operationResult.BalanceId)
-	}
-
-	return "", fmt.Errorf("no operation results")
-}
-```
-
-</CodeExample>
-
-En este punto, el `ClaimableBalanceEntry` existe en el libro mayor, pero necesitaremos su ID de saldo para reclamarlo. Puedes llamar al endpoint [`getLedgerEntries`](../../../data/apis/rpc/api-reference/methods/getLedgerEntries.mdx) del RPC para hacer esto.
-
-<CodeExample>
-
-```js
-import * as StellarSdk from "@stellar/stellar-sdk";
-
-// Replace with your actual Claimable Balance ID
-// Format: 72 hex characters (includes ClaimableBalanceId type + hash)
-const BALANCE_ID =
-  "00000000db1108ff108a807150d02b8672d9a8c0e808bff918cdbe5c7605e63a7f565df5";
-
-/**
- * Fetches and displays claimable balance details using Stellar RPC
- */
-async function fetchClaimableBalance(balanceId) {
-  const server = new StellarSdk.rpc.Server(
-    "https://soroban-testnet.stellar.org",
-  );
-
-  try {
-    console.log(`Looking up balance ID: ${balanceId}`);
-
-    // Parse the claimable balance ID from hex XDR
-    const claimableBalanceId = StellarSdk.xdr.ClaimableBalanceId.fromXDR(
-      balanceId,
-      "hex",
-    );
-
-    // Create ledger key for the claimable balance entry
-    const ledgerKey = StellarSdk.xdr.LedgerKey.claimableBalance(
-      new StellarSdk.xdr.LedgerKeyClaimableBalance({
-        balanceId: claimableBalanceId,
-      }),
-    );
-
-    console.log(`Fetching from RPC server...`);
-
-    // Use SDK's getLedgerEntries method with XDR object array
-    const response = await server.getLedgerEntries(ledgerKey);
-
-    if (response.entries && response.entries.length > 0) {
-      const claimableBalance = response.entries[0].val.claimableBalance();
-
-      const asset = StellarSdk.Asset.fromOperation(claimableBalance.asset());
-
-      console.log(`Found claimable balance`);
-      console.log(`Amount: ${claimableBalance.amount().toString()}`);
-      console.log(`Asset: ${asset.toString()} `);
-      // Show claimant details
-      console.log(`\nClaimants:`);
-      claimableBalance.claimants().forEach((claimant, index) => {
-        const destination = claimant.v0().destination().ed25519();
-        console.log(
-          `   ${index + 1}. ${StellarSdk.StrKey.encodeEd25519PublicKey(
-            destination,
-          )}`,
-        );
-      });
-    } else {
-      console.log(`Claimable balance not found`);
-    }
-  } catch (error) {
-    console.error(`Error: ${error.message}`);
-  }
-}
-
-fetchClaimableBalance(BALANCE_ID);
-```
-
-```go
-package main
-
-import (
-	"context"
-	"fmt"
-	"github.com/stellar/stellar-rpc/client"
-	"github.com/stellar/stellar-rpc/protocol"
-
-	"github.com/stellar/go-stellar-sdk/xdr"
-)
-
-// Replace with your claimable balance ID
-const BALANCE_ID = "00000000a4c91c4561f2d8b30dad9cf6475221b3003a3b4e12fc0cf78a13251c0e7ff665"
-
-func main() {
-	// Create RPC client
-	rpcClient := client.NewClient("https://soroban-testnet.stellar.org", nil)
-	defer rpcClient.Close()
-
-	fmt.Printf("Looking up balance ID: %s\n", BALANCE_ID)
-
-	// Parse claimable balance ID from hex
-	var claimableBalanceID xdr.ClaimableBalanceId
-	err := xdr.SafeUnmarshalHex(BALANCE_ID, &claimableBalanceID)
-	panicIf(err)
-
-	// Create ledger key for claimable balance
-	ledgerKey := xdr.LedgerKey{
-		Type: xdr.LedgerEntryTypeClaimableBalance,
-		ClaimableBalance: &xdr.LedgerKeyClaimableBalance{
-			BalanceId: claimableBalanceID,
-		},
-	}
-
-	// Convert ledger key to base64 for RPC call
-	ledgerKeyB64, err := xdr.MarshalBase64(ledgerKey)
-	panicIf(err)
-
-	fmt.Println("Fetching from RPC server...")
-
-	// Use GetLedgerEntries method from client
-	ctx := context.Background()
-	resp, err := rpcClient.GetLedgerEntries(ctx, protocol.GetLedgerEntriesRequest{
-		Keys: []string{ledgerKeyB64},
-	})
-	panicIf(err)
-
-	if len(resp.Entries) > 0 {
-		entry := resp.Entries[0]
-		fmt.Println("Found claimable balance")
-
-		// Parse the ledger entry XDR
-		var ledgerEntryData xdr.LedgerEntryData
-		err = xdr.SafeUnmarshalBase64(entry.DataXDR, &ledgerEntryData)
-		panicIf(err)
-
-		claimableBalance := ledgerEntryData.ClaimableBalance
-
-		// Display details
-		fmt.Printf("Amount: %d\n", int64(claimableBalance.Amount))
-		fmt.Printf("Asset: %s\n", claimableBalance.Asset.String())
-		// Show claimants
-		fmt.Println("\nClaimants:")
-		for i, claimant := range claimableBalance.Claimants {
-			address := claimant.V0.Destination.Address()
-			fmt.Printf("   %d. %s\n", i+1, address)
-		}
-	} else {
-		fmt.Println("Claimable balance not found")
-	}
-}
-```
-
-</CodeExample>
-
-Con el ID de Claimable Balance obtenido, tanto la Cuenta B como la A pueden enviar una reclamación, dependiendo de qué predicado se cumpla. Aquí asumiremos que ha pasado un minuto, así que la Cuenta A simplemente reclama de nuevo la entrada de saldo.
-
-<CodeExample>
-
-```js
-import * as StellarSdk from "@stellar/stellar-sdk";
-
-// Replace with your claimable balance ID
-const BALANCE_ID =
-  "0000000067a94da6c5d487fa09fc93c558ca91f6338413d3152d2a17771353f7c4111e11";
-
-// Replace with the secret key of one of the claimants
-const CLAIMANT_SECRET =
-  "SDJLAUDIHMDO6PAIVVVYH5IFIE5QMZOOBHO37NLF43335ULECK6EURVJ";
-
-/**
- * Claims a claimable balance
- */
-async function claimClaimableBalance(balanceId, claimantSecret) {
-  const server = new StellarSdk.rpc.Server(
-    "https://soroban-testnet.stellar.org",
-  );
-
-  try {
-    console.log(`Claiming balance ID: ${balanceId}`);
-    // Create keypair from claimant's secret key
-    const claimantKeypair = StellarSdk.Keypair.fromSecret(claimantSecret);
-
-    // Load the claiming account
-    const claimantAccount = await server.getAccount(
-      claimantKeypair.publicKey(),
-    );
-
-    // Convert balance ID to proper format for the operation
-    const claimableBalanceId = StellarSdk.xdr.ClaimableBalanceId.fromXDR(
-      balanceId,
-      "hex",
-    );
-    const balanceIdHex = claimableBalanceId.toXDR("hex");
-
-    // Create claim operation
-    const claimOperation = StellarSdk.Operation.claimClaimableBalance({
-      balanceId: balanceIdHex,
-    });
-
-    // Build and sign transaction
-    const transaction = new StellarSdk.TransactionBuilder(claimantAccount, {
-      fee: StellarSdk.BASE_FEE,
-      networkPassphrase: StellarSdk.Networks.TESTNET,
-    })
-      .addOperation(claimOperation)
-      .setTimeout(180)
-      .build();
-
-    transaction.sign(claimantKeypair);
-
-    // Submit and poll for completion
-    const response = await server.sendTransaction(transaction);
-    const finalResponse = await server.pollTransaction(response.hash);
-
-    if (finalResponse.status === "SUCCESS") {
-      console.log(`Claimable balance claimed successfully`);
-      console.log(`Transaction hash: ${response.hash}`);
-    } else {
-      console.log(`Transaction failed: ${finalResponse.status}`);
-    }
-  } catch (error) {
-    console.error(`Error: ${error.message}`);
-  }
-}
-
-claimClaimableBalance(BALANCE_ID, CLAIMANT_SECRET);
-```
-
-```go
-package main
-
-import (
-	"context"
-	"fmt"
-	"log"
-	"time"
-
-	"github.com/stellar/stellar-rpc/client"
-	"github.com/stellar/stellar-rpc/protocol"
-
-	"github.com/stellar/go-stellar-sdk/keypair"
-	"github.com/stellar/go-stellar-sdk/network"
-	"github.com/stellar/go-stellar-sdk/txnbuild"
-)
-
-// Replace with your claimable balance ID and claimant secret
-const BALANCE_ID = "00000000a4c91c4561f2d8b30dad9cf6475221b3003a3b4e12fc0cf78a13251c0e7ff665"
-const CLAIMANT_SECRET = "SBMODTOLLH2LGF4AJU5XOGHRQCGKEVJUZSAUAGJL7KGKC7XLJ3SG3F7N"
-
-func main() {
-	// Create RPC client
-	rpcClient := client.NewClient("https://soroban-testnet.stellar.org", nil)
-	defer rpcClient.Close()
-
-	// Create keypair from claimant secret
-	keypairAccA, err := keypair.ParseFull(CLAIMANT_SECRET)
-	panicIf(err)
-
-	fmt.Printf("Claiming account: %s\n", keypairAccA.Address())
-	fmt.Printf("Balance ID: %s\n", BALANCE_ID)
-
-	ctx := context.Background()
-
-	// Load the claimant account using client's LoadAccount method
-	accountA, err := rpcClient.LoadAccount(ctx, keypairAccA.Address())
-	panicIf(err)
-
-	// Create claim claimable balance operation
-	claimOp := txnbuild.ClaimClaimableBalance{
-		BalanceID: BALANCE_ID,
-	}
-
-	// Build transaction
-	fmt.Println("Building claim transaction...")
-	tx, err := txnbuild.NewTransaction(
-		txnbuild.TransactionParams{
-			SourceAccount:        accountA,
-			IncrementSequenceNum: true,
-			BaseFee:              txnbuild.MinBaseFee,
-			Preconditions:        txnbuild.Preconditions{TimeBounds: txnbuild.NewInfiniteTimeout()},
-			Operations:           []txnbuild.Operation{&claimOp},
-		},
-	)
-	panicIf(err)
-
-	// Sign transaction
-	tx, err = tx.Sign(network.TestNetworkPassphrase, keypairAccA)
-	panicIf(err)
-
-	// Get transaction XDR
-	txXDR, err := tx.Base64()
-	panicIf(err)
-
-	// Submit using RPC client's SendTransaction method
-	fmt.Println("Submitting claim transaction...")
-	sendResp, err := rpcClient.SendTransaction(ctx, protocol.SendTransactionRequest{
-		Transaction: txXDR,
-	})
-	panicIf(err)
-
-	if sendResp.Status != "PENDING" {
-		log.Fatalf("Transaction not pending: %s", sendResp.Status)
-	}
-
-	fmt.Printf("Transaction submitted: %s\n", sendResp.Hash)
-
-	// Poll for completion using RPC client's GetTransaction method
-	fmt.Println("Polling for result...")
-	for i := 0; i < 10; i++ {
-		resp, err := rpcClient.GetTransaction(ctx, protocol.GetTransactionRequest{
-			Hash: sendResp.Hash,
-		})
-		if err != nil {
-			log.Printf("Error getting transaction: %v", err)
-			time.Sleep(1 * time.Second)
-			continue
-		}
-
-		if resp.Status != protocol.TransactionStatusNotFound {
-			if resp.Status == protocol.TransactionStatusSuccess {
-				fmt.Println("\nSUCCESS: Claimable balance claimed")
-				fmt.Printf("Transaction hash: %s\n", sendResp.Hash)
-				fmt.Printf("Claimed by: %s\n", keypairAccA.Address())
-			} else {
-				fmt.Printf("Transaction failed: %s\n", resp.Status)
-				if resp.ResultXDR != "" {
-					fmt.Printf("Result XDR: %s\n", resp.ResultXDR)
-				}
-			}
-			return
-		}
-
-		time.Sleep(time.Duration(i+1) * time.Second)
-	}
-
-	fmt.Println("Transaction polling timeout")
-}
-```
-
-</CodeExample>
-
-¡Y eso es todo! Como optamos por la ruta de recuperación, la Cuenta A debería tener el mismo saldo con el que empezó (menos las tarifas), y la Cuenta B debería permanecer sin cambios.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/clawbacks.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/clawbacks.mdx
deleted file mode 100644
index 796c0cdea7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/clawbacks.mdx
+++ /dev/null
@@ -1,887 +0,0 @@
----
-title: Recuperaciones
-description: Usa las recuperaciones para quemar una cantidad específica de un activo habilitado para recuperación desde una trustline o un saldo reclamable.
-sidebar_position: 30
----
-
-Los clawbacks se introdujeron en [CAP-0035: Asset Clawback](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0035.md) y permiten que el emisor de un activo destruya una cantidad específica de un activo habilitado para clawback desde una trustline o un balance reclamable, eliminándolo efectivamente y quitándolo del saldo del receptor.
-
-Fueron diseñadas para permitir a los emisores de activos cumplir con regulaciones de valores, que en muchas jurisdicciones requieren que los emisores de activos (o agentes de transferencia designados) tengan la capacidad de revocar activos en caso de una transacción errónea o fraudulenta u otra acción regulatoria relacionada con una persona o activo específico.
-
-Las recuperaciones son útiles para:
-
-- Recuperar activos que han sido obtenidos fraudulentamente
-- Responder a acciones regulatorias
-- Permitir que personas con identidad verificada recuperen un activo habilitado en caso de pérdida de custodia de clave o robo
-
-## Operaciones
-
-### Configurar opciones
-
-El emisor configura su cuenta para habilitar las recuperaciones usando la bandera `AUTH_CLAWBACK_ENABLED`. Esto causa que cada trustline establecida posteriormente para cualquier activo emitido por esa cuenta tenga automáticamente la bandera `TRUSTLINE_CLAWBACK_ENABLED_FLAG` establecida.
-
-Si una cuenta emisora desea establecer la bandera `AUTH_CLAWBACK_ENABLED_FLAG`, debe tener establecida la bandera `AUTH_REVOCABLE_FLAG`. Esto permite al emisor de un activo recuperar saldos bloqueados en ofertas revocando primero la autorización de una trustline, lo que elimina todas las ofertas que involucran esa trustline. Luego, el emisor puede realizar la recuperación.
-
-### Recuperación
-
-La cuenta emisora utiliza esta operación para recuperar parte o la totalidad de un activo. Una vez que una cuenta posee un activo para el cual se han habilitado las recuperaciones, la cuenta emisora puede recuperarlo, quemándolo. Debes proporcionar el activo, una cantidad y la cuenta desde la que recuperarás el activo. Para más detalles, consulta la [operación Recuperación](../../../learn/fundamentals/transactions/list-of-operations.mdx#clawback).
-
-### Recuperar saldo reclamable
-
-Esta operación recupera un saldo reclamable, devolviendo el activo a la cuenta emisora, quemándolo. Debes recuperar la totalidad del saldo reclamable, no solo una parte de él. Una vez que un saldo reclamable ha sido reclamado, utiliza la operación de recuperación regular para recuperarlo. Las recuperaciones de saldos reclamables requieren el ID del saldo reclamable. Para más detalles, consulta la [operación de Recuperar saldo reclamable](../../../learn/fundamentals/transactions/list-of-operations.mdx#clawback-claimable-balance).
-
-### Establecer bandera de trustline
-
-La cuenta emisora utiliza esta operación para eliminar las capacidades de recuperación en una trustline específica removiendo la bandera `TRUSTLINE_CLAWBACK_ENABLED_FLAG` vía la operación [**SetTrustLineFlags**](../../../learn/fundamentals/transactions/list-of-operations.mdx#set-trustline-flags).
-
-Solo puedes eliminar una bandera, no establecerla. Por lo tanto, eliminar una bandera de recuperación en una trustline es irreversible. Esto se hace para que no cambies retroactivamente las reglas para los poseedores de tu activo. Si quieres habilitar los clawbacks de nuevo, los poseedores deben volver a emitir sus trustlines.
-
-## Ejemplos
-
-Aquí cubriremos los siguientes métodos para recuperar un activo.
-
-**Ejemplo 1:** La cuenta emisora (Cuenta A) crea un activo habilitado para recuperación y lo envía a la Cuenta B. La Cuenta B envía ese activo a la Cuenta C. La Cuenta A luego recupera el activo de C. **Ejemplo 2:** La Cuenta B crea un saldo reclamable para la Cuenta C, y la Cuenta A recupera el saldo reclamable. **Ejemplo 3:** La Cuenta A emite un activo habilitado para recuperación a la Cuenta B. A recupera parte del activo de B, luego elimina la bandera habilitada para recuperación de la trustline y ya no puede recuperar el activo.
-
-### Preámbulo: Crear y Financiar Cuentas y Emitir un Activo Recuperable
-
-Primero, configuraremos una cuenta para habilitar clawbacks y emitir un activo en consecuencia.
-
-Emitir un activo correctamente (con cuentas separadas para emisión y distribución) es un poco más complejo, pero usaremos un método más simple aquí.
-
-Además, ten en cuenta que primero necesitamos habilitar recuperaciones y luego establecer trustlines, ya que no puedes habilitar recuperación retroactivamente en trustlines existentes.
-
-El siguiente fragmento de código contiene funciones auxiliares que se usarán en los ejemplos siguientes.
-
-<CodeExample>
-
-```js
-import * as sdk from "@stellar/stellar-sdk";
-
-let server = new sdk.rpc.Server("https://soroban-testnet.stellar.org");
-
-const A = sdk.Keypair.random();
-const B = sdk.Keypair.random();
-const C = sdk.Keypair.random();
-
-console.log("=== ACCOUNT SETUP ===");
-console.log(`Account A (Issuer): ${A.publicKey()}`);
-console.log(`Account B (Trustor): ${B.publicKey()}`);
-console.log(`Account C (Trustor): ${C.publicKey()}`);
-console.log();
-
-const ASSET = new sdk.Asset("CLAW", A.publicKey());
-
-// Helper function to format account ID with label
-function formatAccount(accountId) {
-  const shortId = accountId.substring(0, 8);
-  if (accountId === A.publicKey()) {
-    return `${shortId} (Account A)`;
-  } else if (accountId === B.publicKey()) {
-    return `${shortId} (Account B)`;
-  } else if (accountId === C.publicKey()) {
-    return `${shortId} (Account C)`;
-  }
-  return shortId;
-}
-
-// Helper function to safely scale XDR Int64 asset amounts
-function scaleAsset(x) {
-  return Number((x * 10n) / 10000000n) / 10; // one decimal place
-}
-
-// Helper function to fetch claimable balance details using SDK's built-in method
-async function fetchClaimableBalance(
-  balanceId,
-  description = "Claimable Balance",
-) {
-  try {
-    console.log(`\n--- Checking ${description} ---`);
-    console.log(`Looking up balance ID: ${balanceId}`);
-
-    // Use SDK's built-in getClaimableBalance method
-    const claimableBalance = await server.getClaimableBalance(balanceId);
-    const asset = sdk.Asset.fromOperation(claimableBalance.asset());
-    const amount = scaleAsset(claimableBalance.amount().toBigInt()).toFixed(1);
-
-    console.log(`✅ Found claimable balance`);
-    console.log(`   Amount: ${amount} ${asset.code}`);
-    console.log(
-      `   Number of claimants: ${claimableBalance.claimants().length}`,
-    );
-
-    // Show claimant details
-    claimableBalance.claimants().forEach((claimant, index) => {
-      const destination = claimant.v0().destination().ed25519();
-      const claimantAddress = sdk.StrKey.encodeEd25519PublicKey(destination);
-      console.log(
-        `   Claimant ${index + 1}: ${formatAccount(claimantAddress)}`,
-      );
-    });
-
-    return true; // Balance exists
-  } catch (error) {
-    console.log(`❌ Claimable balance not found (${error.message})`);
-    return false; // Balance doesn't exist
-  }
-}
-
-// Fund accounts first
-function fundAccounts() {
-  console.log("=== FUNDING ACCOUNTS WITH XLM ===");
-  return Promise.all([
-    server.requestAirdrop(A.publicKey()),
-    server.requestAirdrop(B.publicKey()),
-    server.requestAirdrop(C.publicKey()),
-  ]).then(() => {
-    console.log("All accounts funded with XLM via airdrop");
-    // Wait for funding to complete
-    return new Promise((resolve) => setTimeout(resolve, 3000));
-  });
-}
-
-// Enables AuthClawbackEnabledFlag on an account.
-function enableClawback(account, keys) {
-  console.log(
-    `Enabling clawback flags on account ${formatAccount(account.accountId())}`,
-  );
-  return submitAndPollTransaction(
-    buildTx(account, keys, [
-      sdk.Operation.setOptions({
-        setFlags: sdk.AuthClawbackEnabledFlag | sdk.AuthRevocableFlag,
-      }),
-    ]),
-    "Enable Clawback Flags",
-  );
-}
-
-// Establishes a trustline for `recipient` for the CLAW Asset
-const establishTrustline = function (recipient, key) {
-  console.log(
-    `${formatAccount(recipient.accountId())} establishing trustline for ${
-      ASSET.code
-    }`,
-  );
-  return submitAndPollTransaction(
-    buildTx(recipient, key, [
-      sdk.Operation.changeTrust({
-        asset: ASSET,
-        limit: "5000", // arbitrary
-      }),
-    ]),
-    `Establish Trustline (${formatAccount(recipient.accountId())})`,
-  );
-};
-
-// Retrieves latest account info for all accounts.
-function getAccounts() {
-  return Promise.all([
-    server.getAccount(A.publicKey()),
-    server.getAccount(B.publicKey()),
-    server.getAccount(C.publicKey()),
-  ]);
-}
-
-// Show XLM balances (after funding)
-function showXLMBalances(accounts) {
-  console.log("\n=== XLM BALANCES ===");
-  return Promise.all(
-    accounts.map((acc) => {
-      return getXLMBalance(acc.accountId()).then((balance) => {
-        console.log(`${formatAccount(acc.accountId())}: ${balance} XLM`);
-      });
-    }),
-  );
-}
-
-// Get XLM balance using account ledger entry
-function getXLMBalance(accountId) {
-  return server
-    .getAccountEntry(accountId)
-    .then((accountEntry) => {
-      return scaleAsset(accountEntry.balance().toBigInt()).toFixed(1);
-    })
-    .catch(() => "0");
-}
-
-// Show CLAW balances
-function showCLAWBalances(accounts) {
-  console.log("\n=== CLAW BALANCES ===");
-  return Promise.all(
-    accounts.map((acc) => {
-      return getBalance(acc.accountId()).then((balance) => {
-        console.log(`${formatAccount(acc.accountId())}: ${balance} CLAW`);
-      });
-    }),
-  );
-}
-
-// Get CLAW balance using getTrustline
-function getBalance(accountId) {
-  return server
-    .getTrustline(accountId, ASSET)
-    .then((trustlineEntry) => {
-      return scaleAsset(trustlineEntry.balance().toBigInt()).toFixed(1);
-    })
-    .catch(() => "0");
-}
-
-// Helps simplify creating & signing a transaction.
-function buildTx(source, signer, ops) {
-  var tx = new sdk.TransactionBuilder(source, {
-    fee: sdk.BASE_FEE,
-    networkPassphrase: sdk.Networks.TESTNET,
-  });
-
-  ops.forEach((op) => tx.addOperation(op));
-  tx = tx.setTimeout(30).build();
-  tx.sign(signer);
-  return tx;
-}
-
-// Helper function to submit transaction and poll for completion using RPC
-function submitAndPollTransaction(transaction, description = "Transaction") {
-  return server.sendTransaction(transaction).then((submitResponse) => {
-    if (submitResponse.status !== "PENDING") {
-      throw new Error(
-        `Transaction submission failed: ${submitResponse.status}`,
-      );
-    }
-
-    console.log(`${description} submitted: ${submitResponse.hash}`);
-
-    return server.pollTransaction(submitResponse.hash).then((finalResponse) => {
-      if (finalResponse.status === "SUCCESS") {
-        console.log(`${description} completed successfully`);
-      } else {
-        console.log(`${description} failed: ${finalResponse.status}`);
-      }
-
-      return {
-        hash: submitResponse.hash,
-        status: finalResponse.status,
-        resultXdr: finalResponse.resultXdr,
-      };
-    });
-  });
-}
-
-// Makes payment from `fromAccount` to `toAccount` of `amount`
-function makePayment(toAccount, fromAccount, fromKey, amount) {
-  console.log(
-    `\nPayment: ${formatAccount(fromAccount.accountId())} → ${formatAccount(
-      toAccount.accountId(),
-    )} (${amount} CLAW)`,
-  );
-  return submitAndPollTransaction(
-    buildTx(fromAccount, fromKey, [
-      sdk.Operation.payment({
-        destination: toAccount.accountId(),
-        asset: ASSET,
-        amount: amount,
-      }),
-    ]),
-    `Payment of ${amount} CLAW`,
-  );
-}
-
-// Creates a claimable balance from `fromAccount` to `toAccount` of `amount`
-function createClaimable(fromAccount, fromKey, toAccount, amount) {
-  console.log(
-    `\nCreating claimable balance: ${formatAccount(
-      fromAccount.accountId(),
-    )} → ${formatAccount(toAccount.accountId())} (${amount} CLAW)`,
-  );
-  return submitAndPollTransaction(
-    buildTx(fromAccount, fromKey, [
-      sdk.Operation.createClaimableBalance({
-        asset: ASSET,
-        amount: amount,
-        claimants: [new sdk.Claimant(toAccount.accountId())],
-      }),
-    ]),
-    `Create Claimable Balance of ${amount} CLAW`,
-  );
-}
-
-// Parse the ClaimableBalanceId from the transaction result XDR
-function getBalanceId(txResponse) {
-  const txResult = txResponse.resultXdr;
-  const operationResult = txResult.result().results()[0];
-
-  let creationResult = operationResult.value().createClaimableBalanceResult();
-  return creationResult.balanceId().toXDR("hex");
-}
-
-// Clawback the claimable balance using its ID
-function clawbackClaimable(issuerAccount, issuerKey, balanceId) {
-  console.log(
-    `\nClawback claimable balance: ${formatAccount(
-      issuerAccount.accountId(),
-    )} clawing back balance ${balanceId}`,
-  );
-  return submitAndPollTransaction(
-    buildTx(issuerAccount, issuerKey, [
-      sdk.Operation.clawbackClaimableBalance({ balanceId }),
-    ]),
-    `Clawback Claimable Balance`,
-  );
-}
-
-// Clawback `amount` of CLAW from `fromAccount` by `byAccount`
-function doClawback(byAccount, byKey, fromAccount, amount) {
-  console.log(
-    `\nClawback: ${formatAccount(
-      byAccount.accountId(),
-    )} clawing back ${amount} CLAW from ${formatAccount(
-      fromAccount.accountId(),
-    )}`,
-  );
-  return submitAndPollTransaction(
-    buildTx(byAccount, byKey, [
-      sdk.Operation.clawback({
-        from: fromAccount.accountId(),
-        asset: ASSET,
-        amount: amount,
-      }),
-    ]),
-    `Clawback of ${amount} CLAW`,
-  );
-}
-
-// Disable clawback for a trustline by the issuer
-function disableClawback(issuerAccount, issuerKeys, forTrustor) {
-  console.log(
-    `\nDisabling clawback for ${formatAccount(
-      forTrustor.accountId(),
-    )} on asset ${ASSET.code}`,
-  );
-  return submitAndPollTransaction(
-    buildTx(issuerAccount, issuerKeys, [
-      sdk.Operation.setTrustLineFlags({
-        trustor: forTrustor.accountId(),
-        asset: ASSET,
-        flags: {
-          clawbackEnabled: false,
-        },
-      }),
-    ]),
-    "Disable Clawback on Trustline",
-  );
-}
-
-// Enables clawback on A, and establishes trustlines for the CLAW asset for accounts B and C.
-function preamble() {
-  console.log("\n=== SETTING UP CLAWBACK AND TRUSTLINES ===");
-  return getAccounts().then(function (accounts) {
-    let [accountA, accountB, accountC] = accounts;
-
-    return enableClawback(accountA, A)
-      .then(() => {
-        console.log("Clawback enabled successfully");
-        // Get fresh accounts after enabling clawback
-        return getAccounts();
-      })
-      .then((refreshedAccounts) => {
-        let [newAccountA, newAccountB, newAccountC] = refreshedAccounts;
-
-        return Promise.all([
-          establishTrustline(newAccountB, B),
-          establishTrustline(newAccountC, C),
-        ]);
-      })
-      .then(() => {
-        console.log("All trustlines established successfully");
-      });
-  });
-}
-```
-
-</CodeExample>
-
-### Ejemplo 1: Pagos
-
-Este ejemplo mostrará cómo el emisor del activo mantiene el control sobre su activo sin importar cómo se distribuya en el mundo.
-
-En este escenario:
-
-- La Cuenta A pagará a la Cuenta B con 1000 tokens de su activo personalizado.
-- Luego, la Cuenta B pagará a la Cuenta C 500 tokens a su vez.
-- Finalmente, la Cuenta A recuperará la mitad del saldo de la Cuenta C, quemando 250 tokens CLAW.
-
-<CodeExample>
-
-```js
-function examplePaymentAndThenClawback() {
-  console.log("\n=== PAYMENT AND CLAWBACK EXAMPLE ===");
-  return getAccounts()
-    .then(function (accounts) {
-      let [accountA, accountB, accountC] = accounts;
-
-      // A issues 1000 CLAW to B
-      return makePayment(accountB, accountA, A, "1000")
-        .then(() => {
-          console.log("\n--- After A → B payment ---");
-          return getAccounts();
-        })
-        .then((refreshedAccounts) => {
-          [accountA, accountB, accountC] = refreshedAccounts;
-          return showCLAWBalances([accountA, accountB, accountC]);
-        })
-        .then(() => {
-          // B sends 500 CLAW to C
-          return makePayment(accountC, accountB, B, "500");
-        })
-        .then(() => {
-          console.log("\n--- After B → C payment ---");
-          return getAccounts();
-        })
-        .then((refreshedAccounts2) => {
-          [accountA, accountB, accountC] = refreshedAccounts2;
-          return showCLAWBalances([accountA, accountB, accountC]);
-        })
-        .then(() => {
-          // A claws back 250 CLAW from C
-          return doClawback(accountA, A, accountC, "250");
-        });
-    })
-    .then(() => getAccounts());
-}
-
-// Run the example with proper promise chaining
-function runExample1() {
-  fundAccounts()
-    .then(() => getAccounts())
-    .then(showXLMBalances)
-    .then(preamble)
-    .then(examplePaymentAndThenClawback)
-    .then((finalAccounts) => {
-      console.log("\n--- FINAL BALANCES ---");
-      return showCLAWBalances(finalAccounts);
-    })
-    .then(() => {
-      console.log("\n=== CLAWBACK DEMO COMPLETED ===");
-    })
-    .catch((error) => {
-      console.error("Error in example:", error.message);
-    });
-}
-```
-
-</CodeExample>
-
-Cuando invoques `runExample1()`, deberías ver una salida similar a:
-
-```text
-=== ACCOUNT SETUP ===
-Account A (Issuer): GDYIV7XB5M6OS4S2P3DAGIEKRXNKSYZ4LSS5VBWMFGNAO42WGBOQY2E5
-Account B (Trustor): GA7JEMMG46H6CDXR757ZUZ6HCEXE64RKC4M4DYX5DME2XP2P3LXQFVIM
-Account C (Trustor): GCLJYLVE43A73KV62YVC2H7ZK4CDSGMK7IYV2NC4WHQOFRQDFTBG6ZB7
-
-=== FUNDING ACCOUNTS WITH XLM ===
-All accounts funded with XLM via airdrop
-
-=== XLM BALANCES ===
-GDYIV7XB (Account A): 10000.0 XLM
-GCLJYLVE (Account C): 10000.0 XLM
-GA7JEMMG (Account B): 10000.0 XLM
-
-=== SETTING UP CLAWBACK AND TRUSTLINES ===
-Enabling clawback flags on account GDYIV7XB (Account A)
-Enable Clawback Flags submitted: aa48d5bbf1e3c5b3b3ee6b21f4ab4dfbf52632e0d70b1f6e2a09ee33943093d5
-Enable Clawback Flags completed successfully
-Clawback enabled successfully
-GA7JEMMG (Account B) establishing trustline for CLAW
-GCLJYLVE (Account C) establishing trustline for CLAW
-Establish Trustline (GCLJYLVE (Account C)) submitted: effb33b48f126ddd54237b8942d48fdfb562d7dc07500e9db07a1b223a5ef50e
-Establish Trustline (GA7JEMMG (Account B)) submitted: e05fe02b4da8dff22285da2d927545288160ec8f68c1359cefbabdfd4f0020df
-Establish Trustline (GA7JEMMG (Account B)) completed successfully
-Establish Trustline (GCLJYLVE (Account C)) completed successfully
-All trustlines established successfully
-
-=== PAYMENT AND CLAWBACK EXAMPLE ===
-
-Payment: GDYIV7XB (Account A) → GA7JEMMG (Account B) (1000 CLAW)
-Payment of 1000 CLAW submitted: be5cfda0f1625762b3b3b704affa356ff04e5ab388b7b63ede1fa5ca9873c96a
-Payment of 1000 CLAW completed successfully
-
---- After A → B payment ---
-
-=== CLAW BALANCES ===
-GDYIV7XB (Account A): 0 CLAW
-GA7JEMMG (Account B): 1000.0 CLAW
-GCLJYLVE (Account C): 0 CLAW
-
-Payment: GA7JEMMG (Account B) → GCLJYLVE (Account C) (500 CLAW)
-Payment of 500 CLAW submitted: 8a0d19c8e56487255ffe24f5453ffe78177acc6f39bad204bab2849415032555
-Payment of 500 CLAW completed successfully
-
---- After B → C payment ---
-
-=== CLAW BALANCES ===
-GDYIV7XB (Account A): 0 CLAW
-GA7JEMMG (Account B): 500.0 CLAW
-GCLJYLVE (Account C): 500.0 CLAW
-
-Clawback: GDYIV7XB (Account A) clawing back 250 CLAW from GCLJYLVE (Account C)
-Clawback of 250 CLAW submitted: e63eed593a20fb5571e8189ff549cd1360849749c06294f00596fae30da0f23d
-Clawback of 250 CLAW completed successfully
-
---- FINAL BALANCES ---
-
-=== CLAW BALANCES ===
-GCLJYLVE (Account C): 250.0 CLAW
-GA7JEMMG (Account B): 500.0 CLAW
-GDYIV7XB (Account A): 0 CLAW
-
-=== CLAWBACK DEMO COMPLETED ===
-```
-
-<details>
-  <summary>Diagrama de flujo de Clawback</summary>
-
-![example1](/assets/clawback/example1.png)
-
-</details>
-
-Observa que la Cuenta A (el emisor) no tiene ninguno de los activos a pesar de haber recuperado 250 de la Cuenta C. Esto debe dejar claro que los activos recuperados se queman, no se transfieren.
-
-Puede parecer extraño que A nunca posea tokens de su activo personalizado, pero así es exactamente cómo funciona la emisión: creas valor donde antes no había ninguno. Enviar un activo a su cuenta emisora equivale a quemarlo, y auditar la cantidad total de un activo en existencia es uno de los beneficios de distribuirlo correctamente mediante una cuenta de distribución, lo cual evitamos hacer aquí por brevedad del ejemplo.
-
-### Ejemplo 2: Saldos reclamables
-
-Los pagos directos no son la única forma de transferir activos entre cuentas: los balances reclamables también permiten esto. Como son un mecanismo de pago separado, necesitan un mecanismo de recuperación separado.
-
-En este escenario:
-
-- La Cuenta A pagará a la Cuenta B con 1000 tokens de su activo personalizado.
-- La Cuenta B crea un Saldo Reclamable para la Cuenta C por 300 tokens. (Puedes consultar el Saldo Reclamable vía el endpoint `getLedgerEntries` de RPC.)
-- Luego, la Cuenta A recupera el Saldo Reclamable de la Cuenta C.
-- La entrada del Saldo Reclamable se elimina y ya no es accesible mediante consulta.
-
-<CodeExample>
-
-```js
-function exampleClaimableBalanceClawback() {
-  console.log("\n=== CLAIMABLE BALANCE CLAWBACK EXAMPLE ===");
-  let balanceId;
-
-  return getAccounts()
-    .then(function (accounts) {
-      let [accountA, accountB, accountC] = accounts;
-
-      console.log("\n--- Initial CLAW balances ---");
-      return showCLAWBalances([accountA, accountB, accountC])
-        .then(() => {
-          // A pays 1000 CLAW to B
-          return makePayment(accountB, accountA, A, "1000");
-        })
-        .then(() => {
-          console.log("\n--- After A → B payment ---");
-          return getAccounts();
-        })
-        .then((refreshedAccounts) => {
-          [accountA, accountB, accountC] = refreshedAccounts;
-          return showCLAWBalances([accountA, accountB, accountC]);
-        })
-        .then(() => {
-          // B creates claimable balance for C
-          return createClaimable(accountB, B, accountC, "300");
-        })
-        .then((txResp) => {
-          balanceId = getBalanceId(txResp);
-          console.log(`Claimable balance created with ID: ${balanceId}`);
-
-          console.log("\n--- After claimable balance creation ---");
-          return getAccounts()
-            .then((refreshedAccounts2) => {
-              [accountA, accountB, accountC] = refreshedAccounts2;
-              return showCLAWBalances([accountA, accountB, accountC]);
-            })
-            .then(() => {
-              // Check that the claimable balance exists
-              return fetchClaimableBalance(
-                balanceId,
-                "claimable balance after creation",
-              );
-            })
-            .then(() => {
-              // A claws back the claimable balance
-              return clawbackClaimable(accountA, A, balanceId);
-            })
-            .then(() => {
-              // Check that the claimable balance no longer exists
-              return fetchClaimableBalance(
-                balanceId,
-                "claimable balance after clawback",
-              );
-            });
-        });
-    })
-    .then(() => getAccounts());
-}
-
-// Run the example with proper promise chaining
-function runExample2() {
-  fundAccounts()
-    .then(() => getAccounts())
-    .then(showXLMBalances)
-    .then(preamble)
-    .then(exampleClaimableBalanceClawback)
-    .then((finalAccounts) => {
-      console.log("\n--- FINAL BALANCES ---");
-      return showCLAWBalances(finalAccounts);
-    })
-    .then(() => {
-      console.log("\n=== CLAIMABLE BALANCE CLAWBACK DEMO COMPLETED ===");
-    })
-    .catch((error) => {
-      console.error("Error in example:", error.message);
-    });
-}
-```
-
-</CodeExample>
-
-Cuando invoques `runExample2()`, deberías ver una salida similar a:
-
-```
-=== ACCOUNT SETUP ===
-Account A (Issuer): GBOK4XIKNCKVWKRG27EEMYX2H7H5GP6ZCLYJTORHJVV3ZDJZJXTUPKTJ
-Account B (Trustor): GBI5XUOWLBL44DWJXURGQJX46TUSNEPQ553LZUGLFCVQ6KRRPEEFBPKE
-Account C (Trustor): GANXLMMUIG7G5NT6GQZNE3OPCRCROYJLTR6PGRZHVURUGNURSF3H3ZEZ
-
-=== FUNDING ACCOUNTS WITH XLM ===
-All accounts funded with XLM via airdrop
-
-=== XLM BALANCES ===
-GBI5XUOW (Account B): 10000.0 XLM
-GANXLMMU (Account C): 10000.0 XLM
-GBOK4XIK (Account A): 10000.0 XLM
-
-=== SETTING UP CLAWBACK AND TRUSTLINES ===
-Enabling clawback flags on account GBOK4XIK (Account A)
-Enable Clawback Flags submitted: 4812d2be7e8652dbeb29fd4d9387c71725e09e5f1d3500b3e913eebc9bec03b1
-Enable Clawback Flags completed successfully
-Clawback enabled successfully
-GBI5XUOW (Account B) establishing trustline for CLAW
-GANXLMMU (Account C) establishing trustline for CLAW
-Establish Trustline (GANXLMMU (Account C)) submitted: eb2c17135109408d751cdbab9235c8a833922a66c6576fe76a7930a2ef9e7042
-Establish Trustline (GBI5XUOW (Account B)) submitted: 1ebb5ed64cb1c5c9beb121d56c31b802fab885ef06b771b3d8617371482e115d
-Establish Trustline (GANXLMMU (Account C)) completed successfully
-Establish Trustline (GBI5XUOW (Account B)) completed successfully
-All trustlines established successfully
-
-=== CLAIMABLE BALANCE CLAWBACK EXAMPLE ===
-
---- Initial CLAW balances ---
-
-=== CLAW BALANCES ===
-GANXLMMU (Account C): 0 CLAW
-GBI5XUOW (Account B): 0 CLAW
-GBOK4XIK (Account A): 0 CLAW
-
-Payment: GBOK4XIK (Account A) → GBI5XUOW (Account B) (1000 CLAW)
-Payment of 1000 CLAW submitted: ec852daea2fea4e5b6a1d56530618f30642d9207767f30558d577b4f98e59850
-Payment of 1000 CLAW completed successfully
-
---- After A → B payment ---
-
-=== CLAW BALANCES ===
-GANXLMMU (Account C): 0.0 CLAW
-GBI5XUOW (Account B): 1000.0 CLAW
-GBOK4XIK (Account A): 0 CLAW
-
-Creating claimable balance: GBI5XUOW (Account B) → GANXLMMU (Account C) (300 CLAW)
-Create Claimable Balance of 300 CLAW submitted: 743066775839ef5112fd2b8a26730700a986655c557abcb98b91c6fdbd12abde
-Create Claimable Balance of 300 CLAW completed successfully
-Claimable balance created with ID: 0000000091b5fe84a029c79d409ac88d34b7047a6cc9f95b2c2f965843db122ef70fac2c
-
---- After claimable balance creation ---
-
-=== CLAW BALANCES ===
-GBI5XUOW (Account B): 700.0 CLAW
-GBOK4XIK (Account A): 0 CLAW
-GANXLMMU (Account C): 0 CLAW
-
---- Checking claimable balance after creation ---
-Looking up balance ID: 0000000091b5fe84a029c79d409ac88d34b7047a6cc9f95b2c2f965843db122ef70fac2c
-✅ Found claimable balance
-   Amount: 300.0 CLAW
-   Number of claimants: 1
-   Claimant 1: GANXLMMU (Account C)
-
-Clawback claimable balance: GBOK4XIK (Account A) clawing back balance 0000000091b5fe84a029c79d409ac88d34b7047a6cc9f95b2c2f965843db122ef70fac2c
-Clawback Claimable Balance submitted: a82a0ed067d34361da622a56a3b6d59a7c4a351414a69da4dc9df8a5728e7758
-Clawback Claimable Balance completed successfully
-
---- Checking claimable balance after clawback ---
-Looking up balance ID: 0000000091b5fe84a029c79d409ac88d34b7047a6cc9f95b2c2f965843db122ef70fac2c
-❌ Claimable balance not found (Claimable balance 0000000091b5fe84a029c79d409ac88d34b7047a6cc9f95b2c2f965843db122ef70fac2c not found)
-
---- FINAL BALANCES ---
-
-=== CLAW BALANCES ===
-GBI5XUOW (Account B): 700.0 CLAW
-GBOK4XIK (Account A): 0 CLAW
-GANXLMMU (Account C): 0.0 CLAW
-
-=== CLAIMABLE BALANCE CLAWBACK DEMO COMPLETED ===
-```
-
-### Ejemplo 3: Activar Selectivamente la Recuperación
-
-Cuando habilitas el `AUTH_CLAWBACK_ENABLED_FLAG` en tu cuenta, todos los trustlines futuros tendrán activada la recuperación para cualquiera de los activos que hayas emitido. Esto puede no ser siempre deseable, ya que podrías querer que ciertos activos se comporten como antes. Aunque podrías solucionarlo reemitiendo activos desde una cuenta "dedicada a la recuperación", también puedes simplemente desactivar la recuperación para ciertos trustlines borrando el `TRUST_LINE_CLAWBACK_ENABLED_FLAG` en un trustline.
-
-En este escenario:
-
-- La Cuenta A emite un activo y envía 1000 tokens a una cuenta de distribución (Cuenta B).
-- La Cuenta A recupera 500 tokens de la Cuenta B.
-- Luego, la Cuenta A limpia el trustline para que no pueda recuperar el activo.
-- La Cuenta A intenta entonces recuperar 250 tokens de la Cuenta B y falla.
-
-_Nota que la Cuenta C no es relevante en este ejemplo._
-
-<CodeExample>
-
-```js
-function exampleSelectiveClawbackThenDisableClawback() {
-  console.log("\n=== SELECTIVE CLAWBACK EXAMPLE ===");
-  return getAccounts()
-    .then((accounts) => {
-      let [accountA, accountB] = accounts;
-
-      console.log("\n--- Initial CLAW balances ---");
-      return showCLAWBalances([accountA, accountB])
-        .then(() => {
-          // A pays 1000 CLAW to B
-          return makePayment(accountB, accountA, A, "1000");
-        })
-        .then(() => {
-          console.log("\n--- After A → B payment ---");
-          return getAccounts();
-        })
-        .then((refreshedAccounts) => {
-          [accountA, accountB] = refreshedAccounts;
-          return showCLAWBalances([accountA, accountB]);
-        })
-        .then(() => {
-          // A claws back 500 CLAW from B (should work)
-          return doClawback(accountA, A, accountB, "500");
-        })
-        .then(() => {
-          console.log("\n--- After first clawback ---");
-          return getAccounts();
-        })
-        .then((refreshedAccounts2) => {
-          [accountA, accountB] = refreshedAccounts2;
-          return showCLAWBalances([accountA, accountB]);
-        })
-        .then(() => {
-          // A disables clawback for B's trustline
-          return disableClawback(accountA, A, accountB);
-        })
-        .then(() => {
-          // Try to clawback again (should fail)
-          return doClawback(accountA, A, accountB, "250");
-        })
-        .catch((err) => {
-          console.log("Error:", err.message);
-        });
-    })
-    .then(() => getAccounts());
-}
-
-// Run the example with proper promise chaining
-function runExample3() {
-  fundAccounts()
-    .then(() => getAccounts())
-    .then((accounts) => showXLMBalances([accounts[0], accounts[1]])) // Only show A and B
-    .then(preamble) // This sets up clawback and trustlines for A, B, C
-    .then(exampleSelectiveClawbackThenDisableClawback)
-    .then((finalAccounts) => {
-      console.log("\n--- FINAL BALANCES ---");
-      return showCLAWBalances([finalAccounts[0], finalAccounts[1]]); // Only show A and B
-    })
-    .then(() => {
-      console.log("\n=== SELECTIVE CLAWBACK DEMO COMPLETED ===");
-    })
-    .catch((error) => {
-      console.error("Error in example:", error.message);
-    });
-}
-```
-
-</CodeExample>
-
-Cuando invoques `runExample3()`, deberías ver una salida similar a:
-
-```text
-=== ACCOUNT SETUP ===
-Account A (Issuer): GCTYN2SAMM2SHM5LOCHS2P2I24MEHVYKHKCSO5XPR2H2GQCK6PFCQRK6
-Account B (Trustor): GAWDYTIKQI7J3YSCSLWGAJPN6J62WQKDA3XCAC55DDRH5KCTEZ5IGGWP
-Account C (Trustor): GC5KQ7H5G5E65OVZGKBVCXBJKTEHWBBLQ56L7DK4ATUHUH5VJP4YHQVC
-
-=== FUNDING ACCOUNTS WITH XLM ===
-All accounts funded with XLM via airdrop
-
-=== XLM BALANCES ===
-GCTYN2SA (Account A): 10000.0 XLM
-GAWDYTIK (Account B): 10000.0 XLM
-
-=== SETTING UP CLAWBACK AND TRUSTLINES ===
-Enabling clawback flags on account GCTYN2SA (Account A)
-Enable Clawback Flags submitted: 52e7e15d70e46dc3b551e787ec3be11692d2cc8e0b2fda070cebfa048c67cedd
-Enable Clawback Flags completed successfully
-Clawback enabled successfully
-GAWDYTIK (Account B) establishing trustline for CLAW
-GC5KQ7H5 (Account C) establishing trustline for CLAW
-Establish Trustline (GAWDYTIK (Account B)) submitted: 3cf49bf597085ede004d566d151b9a917b31d1dbbfa81d71a64b615356702da7
-Establish Trustline (GC5KQ7H5 (Account C)) submitted: 9250e62be27e3111924d36c0169f3b08e12565f8f842bf32a8a7a0efb098a080
-Establish Trustline (GAWDYTIK (Account B)) completed successfully
-Establish Trustline (GC5KQ7H5 (Account C)) completed successfully
-All trustlines established successfully
-
-=== SELECTIVE CLAWBACK EXAMPLE ===
-
---- Initial CLAW balances ---
-
-=== CLAW BALANCES ===
-GCTYN2SA (Account A): 0 CLAW
-GAWDYTIK (Account B): 0 CLAW
-
-Payment: GCTYN2SA (Account A) → GAWDYTIK (Account B) (1000 CLAW)
-Payment of 1000 CLAW submitted: 9974f7a8f85dbe437a18364066959718ceeeaa3ae9a84ccd0e91da5f4e6bfaeb
-Payment of 1000 CLAW completed successfully
-
---- After A → B payment ---
-
-=== CLAW BALANCES ===
-GAWDYTIK (Account B): 1000.0 CLAW
-GCTYN2SA (Account A): 0 CLAW
-
-Clawback: GCTYN2SA (Account A) clawing back 500 CLAW from GAWDYTIK (Account B)
-Clawback of 500 CLAW submitted: b1729001fba89198f67bcff2de7fb47ea97c358e902688d88b76c6ff3947cec2
-Clawback of 500 CLAW completed successfully
-
---- After first clawback ---
-
-=== CLAW BALANCES ===
-GAWDYTIK (Account B): 500.0 CLAW
-GCTYN2SA (Account A): 0 CLAW
-
-Disabling clawback for GAWDYTIK (Account B) on asset CLAW
-Disable Clawback on Trustline submitted: a1fe18c12628806bac90936f563978d1f9a3333a1a77482d55d3b7af99e679a7
-Disable Clawback on Trustline completed successfully
-
-Clawback: GCTYN2SA (Account A) clawing back 250 CLAW from GAWDYTIK (Account B)
-Clawback of 250 CLAW submitted: eab31d237832b513ca911cd2b4a4466a7b7b502f274dcc926b9910223fc2043f
-Clawback of 250 CLAW failed: FAILED
-
---- FINAL BALANCES ---
-
-=== CLAW BALANCES ===
-GAWDYTIK (Account B): 500.0 CLAW
-GCTYN2SA (Account A): 0 CLAW
-
-=== SELECTIVE CLAWBACK DEMO COMPLETED ===
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/create-account.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/create-account.mdx
deleted file mode 100644
index 9b7d399622..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/create-account.mdx
+++ /dev/null
@@ -1,716 +0,0 @@
----
-title: Crear una cuenta
-sidebar_position: 5
-description: Aprende sobre cómo crear cuentas Stellar, pares de llaves, financiamiento y conceptos básicos de las cuentas.
----
-
-# Crear una cuenta
-
-_Antes de comenzar a trabajar con Stellar en código, considera revisar los siguientes ejemplos usando el [Stellar Lab](https://lab.stellar.org). El laboratorio te permite crear cuentas, financiar cuentas en la red de prueba Stellar, desarrollar transacciones, ejecutar cualquier operación e inspeccionar respuestas desde Horizon a través del Explorador de Endpoints.
-
-[Las cuentas](../../../learn/fundamentals/stellar-data-structures/accounts.mdx) son un componente fundamental de Stellar: contienen todos tus saldos, te permiten enviar y recibir pagos, y hacer ofertas para comprar y vender activos. Dado que prácticamente todo en Stellar está vinculado a una cuenta, lo primero que generalmente necesitas hacer al comenzar a desarrollar es crear una. Este tutorial para principiantes explica los tres bloques fundamentales que necesitarás: [generar claves](#create-a-keypair), [financiar una cuenta](#create-an-account) y [consultar saldos](#fetch-balances).
-
-## Crear un par de llaves
-
-Stellar usa criptografía de clave pública para asegurar cada transacción: cada cuenta Stellar tiene un par de claves formado por una **clave pública** y una **clave secreta**. La clave pública siempre es segura para compartir: otras personas la necesitan para identificar tu cuenta y verificar que autorizaste una transacción. Es como una dirección de correo electrónico. Sin embargo, la clave secreta es información privada que prueba que eres el dueño y te da acceso a tu cuenta. Es como una contraseña, y nunca deberías compartirla con nadie.
-
-Antes de crear una cuenta, necesitas generar tu propio par de claves; aprenderemos cómo hacerlo en el [ejemplo completo](#full-example), más abajo.
-
-## Crear una cuenta
-
-Un par de claves válido por sí solo no constituye una cuenta. Para evitar que las entradas no usadas inflen el ledger, Stellar requiere que cada cuenta mantenga un [saldo mínimo](../../../learn/fundamentals/lumens.mdx#minimum-balance) de 1 XLM antes de que realmente exista.
-
-En la red de prueba, puedes pedirle a Friendbot — un servicio amable de financiación — que cree y financie la cuenta por ti. En los ejemplos del SDK, abajo, verás que "descubrimos" el endpoint de Friendbot mediante la llamada `getNetwork` del RPC, y luego enviamos una solicitud de financiación.
-
-En la red pública, las cosas son un poco diferentes. Adquirirías lumens en un exchange o harías que alguien cree o patrocine una cuenta en tu nombre. Este es el propósito de la [operación `CreateAccount`](../../../learn/fundamentals/transactions/list-of-operations.mdx#create-account). Veremos en los ejemplos posteriores que dada una cuenta financiada, luego puedes crear una cuenta secundaria en la red con un saldo inicial.
-
-## Consultar saldos
-
-Una vez que tus cuentas existan, puedes consultar su estado. En Stellar, los activos pueden mantenerse en varias formas diferentes:
-
-- tu saldo **nativo** es la cantidad de XLM que posees, el cual está asociado directamente a tu cuenta
-- también puedes establecer **trustlines** a diversos activos para mantener saldo; estos pueden obtenerse tanto mediante operaciones de pago simples como interacciones con contratos inteligentes
-- finalmente, puedes mantener **tokens personalizados de contratos inteligentes**, que son activos no estándar
-
-Aprenderás sobre estos en tutoriales posteriores.
-
-## Ejemplo completo
-
-Combinemos estos cuatro conceptos en un ejemplo único y coherente. Ten en cuenta que siempre verás tu saldo de USDC como cero, ya que en realidad no recibimos ninguno, pero será útil en el futuro cuando poseas más que solo el token nativo.
-
-Para cada uno de estos, asegúrate de seguir las instrucciones de instalación y configuración correspondientes a cada SDK desde su [documentación](../../../tools/sdks/client-sdks.mdx).
-
-<CodeExample>
-
-```js
-import {
-  Keypair,
-  BASE_FEE,
-  Networks,
-  Operation,
-  Asset,
-  humanizeEvents,
-  TransactionBuilder,
-} from "@stellar/stellar-sdk";
-import { Server } from "@stellar/stellar-sdk/rpc";
-
-// See https://developers.stellar.org/docs/data/apis/rpc/providers
-const server = new Server("https://soroban-testnet.stellar.org");
-
-const testnetUsdc = new Asset(
-  "USDC",
-  "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5",
-);
-
-async function main() {
-  //
-  // Generating keypairs
-  //
-  const parent = Keypair.random();
-  console.log("Secret:", parent.secret());
-  console.log("Public:", parent.publicKey());
-
-  //
-  // Account creation via friendbot (does not work on mainnet)
-  //
-  const friendbotResponse = await server.requestAirdrop(parent.publicKey());
-  console.log("SUCCESS! You have a new account:\n", friendbotResponse);
-
-  const parentAccount = await server.getAccount(parent.publicKey());
-  const childAccount = Keypair.random();
-
-  //
-  // Account creation via the CreateAccount operation
-  //
-  const createAccountTx = new TransactionBuilder(parentAccount, {
-    fee: BASE_FEE,
-    networkPassphrase: Networks.TESTNET,
-  })
-    .addOperation(
-      Operation.createAccount({
-        destination: childAccount.publicKey(),
-        startingBalance: "5",
-      }),
-    )
-    .addOperation(Operation.changeTrust({ asset: testnetUsdc }))
-    .setTimeout(180)
-    .build();
-
-  createAccountTx.sign(parent);
-
-  const sendTxResponse = await server.sendTransaction(createAccountTx);
-  if (sendTxResponse.status !== "PENDING") {
-    console.log(`There was an error: ${JSON.stringify(sendTxResponse)}`);
-    throw sendTxResponse;
-  }
-
-  const txResponse = await server.pollTransaction(sendTxResponse.hash);
-  if (txResponse.status !== "SUCCESS") {
-    console.log(
-      `Transaction status: ${txResponse.status}, events: ${humanizeEvents(
-        txResponse.diagnosticEvents,
-      )}`,
-    );
-  }
-
-  console.log("Created the new account", childAccount.publicKey());
-
-  //
-  // Fetching native and USDC balances
-  //
-  const accountEntry = await server.getAccountEntry(parent.publicKey());
-  console.log("Balance for account: " + parent.publicKey());
-  console.log("XLM:", accountEntry.balance().toString());
-
-  const trustlineEntry = await server.getTrustline(
-    parent.publicKey(),
-    testnetUsdc,
-  );
-  console.log("USDC:", trustlineEntry.balance().toString());
-}
-
-main().catch((err) => console.error(err));
-```
-
-```python
-import requests
-from stellar_sdk import *
-from stellar_sdk.soroban_rpc import GetTransactionStatus, SendTransactionStatus
-from stellar_sdk.xdr import *
-
-RPC_URL = "https://soroban-testnet.stellar.org"
-TESTNET_USDC_ISSUER = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-SERVER = SorobanServer(RPC_URL)
-
-
-def main():
-    #
-    # Keypair generation
-    #
-    parent = Keypair.random()
-    print(f"Secret: {parent.secret}")
-    print(f"Public: {parent.public_key}")
-
-    #
-    # Account creation via friendbot
-    #
-    friendbot_url = get_friendbot_url()
-    print(f"Using {friendbot_url} for friendbot funding")
-
-    body = request_funds(friendbot_url, parent.public_key)
-    print(f"SUCCESS! You have a new account:\n{body}")
-
-    #
-    # Account creation via CreateAccount operation
-    #
-    child = Keypair.random()
-    parent_account = SERVER.load_account(parent.public_key)
-    usdc_asset = Asset("USDC", TESTNET_USDC_ISSUER)
-    tx = (
-        TransactionBuilder(
-            source_account=parent_account,
-            network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-            base_fee=TransactionBuilder.BASE_FEE,
-        )
-        .add_time_bounds(0, 0)
-        .append_operation(
-            CreateAccount(destination=child.public_key, starting_balance="5")
-        )
-        .build()
-    )
-    tx.sign(parent)
-
-    ledger_seq = submit_and_confirm(tx)
-    print(f"Transaction confirmed in ledger {ledger_seq}")
-    print(f"Created the new account {child.public_key}")
-
-    #
-    # Fetching native and USDC balances
-    #
-    native_balance = load_native_balance(parent.public_key)
-    print(f"Balance for account {parent.public_key}")
-    print(f"XLM: {native_balance}")
-
-    trustline_balance = get_trustline(parent.public_key, usdc_asset)
-    print(f"USDC trustline balance (raw): {trustline_balance}")
-
-def request_funds(friendbot_url: str, account_id: str) -> str:
-    request_url = f"{friendbot_url}?addr={account_id}"
-    resp = requests.get(request_url, timeout=30)
-    check(resp.ok, f"friendbot returned {resp.status_code}: {resp.text}")
-    return resp.text
-
-
-def get_friendbot_url() -> str:
-    response = SERVER.get_network()
-    if response.friendbot_url:
-        return response.friendbot_url.strip()
-    raise RuntimeError("Friendbot URL not provided by network")
-
-
-def load_native_balance(account_id: str) -> int:
-    key = LedgerKey(
-        LedgerEntryType.ACCOUNT,
-        account=LedgerKeyAccount(
-            account_id=Keypair.from_public_key(account_id).xdr_account_id()
-        ),
-    )
-    response = SERVER.get_ledger_entries([key])
-    check(response.entries, f"account {account_id} not found")
-    ledger_entry = LedgerEntryData.from_xdr(response.entries[0].xdr)
-    account = ledger_entry.account
-    check(account is not None, "ledger entry missing account data")
-    return account.balance.int64
-
-
-def get_trustline(account_id: str, asset: Asset) -> int:
-    key = LedgerKey(
-        LedgerEntryType.TRUSTLINE,
-        trust_line=LedgerKeyTrustLine(
-            account_id=Keypair.from_public_key(account_id).xdr_account_id(),
-            asset=asset.to_trust_line_xdr_object(),
-        ),
-    )
-    response = SERVER.get_ledger_entries([key])
-    if not response.entries:
-        return 0
-    ledger_entry = LedgerEntryData.from_xdr(response.entries[0].xdr)
-    trust_line = ledger_entry.trust_line
-    if trust_line is None:
-        return 0
-    return trust_line.balance.int64
-
-
-def submit_and_confirm(transaction):
-    response = SERVER.send_transaction(transaction)
-    check(
-        response.status == SendTransactionStatus.PENDING,
-        f"Transaction submission failed: {response.status}",
-    )
-
-    tx_resp = SERVER.poll_transaction(response.hash)
-    if tx_resp.status == GetTransactionStatus.SUCCESS:
-        return tx_resp.ledger or tx_resp.latest_ledger
-    raise RuntimeError(f"Transaction failed: {tx_resp.diagnostic_events_xdr}")
-
-
-def check(condition: bool, message: str) -> None:
-    if not condition:
-        raise RuntimeError(message)
-
-
-if __name__ == "__main__":
-    main()
-```
-
-```go
-package main
-
-import (
-  "context"
-  "fmt"
-  "io"
-  "log"
-  "net/http"
-  "net/url"
-  "strings"
-  "time"
-
-  "github.com/stellar/go-stellar-sdk/amount"
-  "github.com/stellar/go-stellar-sdk/keypair"
-  "github.com/stellar/go-stellar-sdk/network"
-  "github.com/stellar/go-stellar-sdk/txnbuild"
-  "github.com/stellar/go-stellar-sdk/xdr"
-
-  "github.com/stellar/stellar-rpc/client"
-  "github.com/stellar/stellar-rpc/protocol"
-)
-
-const (
-  rpcURL            = "https://soroban-testnet.stellar.org"
-  testnetUSDCIssuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-  pollAttempts      = 10
-  pollInitialDelay  = time.Second
-)
-
-func main() {
-  //
-  // Generating keypairs
-  //
-  parent := keypair.MustRandom()
-  log.Printf("Secret: %s", parent.Seed())
-  log.Printf("Public: %s", parent.Address())
-
-  //
-  // Funding via friendbot
-  //
-  ctx := context.Background()
-  cli := client.NewClient(rpcURL, nil)
-  defer cli.Close()
-  networkInfo, err := cli.GetNetwork(ctx)
-  check(err)
-
-  friendbotURL := strings.TrimSpace(networkInfo.FriendbotURL)
-  if friendbotURL == "" {
-    log.Fatal("friendbot URL not provided by network")
-  }
-  log.Printf("Using %s for friendbot funding", friendbotURL)
-
-  body := requestAirdrop(friendbotURL, parent.Address())
-  log.Printf("SUCCESS! You have a new account:\n%s", body)
-
-  //
-  // Funding a new account via CreateAccount operation
-  //
-  child := keypair.MustRandom()
-  parentAccount, err := cli.LoadAccount(ctx, parent.Address())
-  check(err)
-
-  tx, err := txnbuild.NewTransaction(txnbuild.TransactionParams{
-    SourceAccount:        parentAccount,
-    IncrementSequenceNum: true,
-    BaseFee:              txnbuild.MinBaseFee,
-    Preconditions: txnbuild.Preconditions{
-      TimeBounds: txnbuild.NewInfiniteTimeout(),
-    },
-    Operations: []txnbuild.Operation{
-      &txnbuild.CreateAccount{
-        Destination: child.Address(),
-        Amount:      "5",
-      },
-    },
-  })
-  check(err)
-
-  tx, err = tx.Sign(network.TestNetworkPassphrase, parent)
-  check(err)
-
-  resp := submitAndAwait(ctx, cli, tx)
-  log.Printf("Transaction confirmed in ledger %d", resp.Ledger)
-  log.Printf("Created the new account %s", child.Address())
-
-  //
-  // Fetch native and USDC balances for account
-  //
-  accountEntry := getAccountEntry(ctx, cli, parent.Address())
-  log.Printf("Balance for account %s", parent.Address())
-  log.Printf("XLM: %s", amount.String(accountEntry.Balance))
-
-  usdcAsset := txnbuild.CreditAsset{Code: "USDC", Issuer: testnetUSDCIssuer}
-  trustlineEntry := getTrustlineEntry(ctx, cli, parent.Address(), usdcAsset)
-  log.Printf("USDC trustline balance (raw): %d", trustlineEntry.Balance)
-
-}
-
-func requestAirdrop(friendbotURL, address string) string {
-  requestURL := fmt.Sprintf("%s?addr=%s", friendbotURL, url.QueryEscape(address))
-  resp, err := http.Get(requestURL)
-  check(err)
-  defer resp.Body.Close()
-
-  body, err := io.ReadAll(resp.Body)
-  check(err)
-  if resp.StatusCode >= 400 {
-    log.Fatalf("friendbot returned %s: %s", resp.Status, string(body))
-  }
-
-  return string(body)
-}
-
-func submitAndAwait(ctx context.Context, cli *client.Client, tx *txnbuild.Transaction) protocol.GetTransactionResponse {
-  txnB64, err := tx.Base64()
-  check(err)
-
-  sendResp, err := cli.SendTransaction(ctx, protocol.SendTransactionRequest{Transaction: txnB64})
-  check(err)
-  if sendResp.Status != "PENDING" {
-    log.Fatalf("transaction submission failed with status %s", sendResp.Status)
-  }
-
-  return pollTransaction(ctx, cli, sendResp.Hash)
-}
-
-func pollTransaction(ctx context.Context, cli *client.Client, hash string) protocol.GetTransactionResponse {
-  delay := pollInitialDelay
-  for range pollAttempts {
-    resp, err := cli.GetTransaction(ctx, protocol.GetTransactionRequest{Hash: hash})
-    check(err)
-
-    switch resp.Status {
-    case protocol.TransactionStatusSuccess:
-      return resp
-    case protocol.TransactionStatusFailed:
-      log.Fatalf("transaction failed: %s", strings.Join(resp.DiagnosticEventsXDR, "\n"))
-    case protocol.TransactionStatusNotFound:
-      // keep polling
-    default:
-      // unexpected status, continue polling in case it's transient
-    }
-
-    select {
-    case <-ctx.Done():
-      log.Fatalf("context cancelled while polling: %v", ctx.Err())
-    case <-time.After(delay):
-    }
-    delay += pollInitialDelay
-  }
-
-  log.Fatalf("transaction %s not found after polling", hash)
-  return protocol.GetTransactionResponse{}
-}
-
-func getAccountEntry(ctx context.Context, cli *client.Client, address string) *xdr.AccountEntry {
-  ledgerKey := xdr.LedgerKey{
-    Type: xdr.LedgerEntryTypeAccount,
-    Account: &xdr.LedgerKeyAccount{
-      AccountId: xdr.MustAddress(address),
-    },
-  }
-
-  keyB64, err := xdr.MarshalBase64(ledgerKey)
-  check(err)
-
-  resp, err := cli.GetLedgerEntries(ctx, protocol.GetLedgerEntriesRequest{Keys: []string{keyB64}})
-  check(err)
-  if len(resp.Entries) == 0 {
-    log.Fatalf("account %s not found", address)
-  }
-
-  var ledgerData xdr.LedgerEntryData
-  check(xdr.SafeUnmarshalBase64(resp.Entries[0].DataXDR, &ledgerData))
-  if ledgerData.Account == nil {
-    log.Fatalf("ledger entry for %s missing account data", address)
-  }
-
-  return ledgerData.Account
-}
-
-func getTrustlineEntry(ctx context.Context, cli *client.Client, account string, asset txnbuild.CreditAsset) xdr.TrustLineEntry {
-  trustlineAsset, err := asset.MustToTrustLineAsset().ToXDR()
-  check(err)
-
-  ledgerKey := xdr.LedgerKey{
-    Type: xdr.LedgerEntryTypeTrustline,
-    TrustLine: &xdr.LedgerKeyTrustLine{
-      AccountId: xdr.MustAddress(account),
-      Asset:     trustlineAsset,
-    },
-  }
-
-  keyB64, err := xdr.MarshalBase64(ledgerKey)
-  check(err)
-
-  resp, err := cli.GetLedgerEntries(ctx, protocol.GetLedgerEntriesRequest{Keys: []string{keyB64}})
-  check(err)
-  if len(resp.Entries) == 0 {
-    check(fmt.Errorf("trustline for %s:%s not found", asset.Code, asset.Issuer))
-  }
-
-  var ledgerData xdr.LedgerEntryData
-  check(xdr.SafeUnmarshalBase64(resp.Entries[0].DataXDR, &ledgerData))
-  return ledgerData.MustTrustLine()
-}
-
-func check(err error) {
-  if err != nil {
-    log.Fatal(err)
-  }
-}
-```
-
-```java
-// File: main.java
-// Dependencies (Maven coordinates):
-//   org.stellar:java-stellar-sdk:0.43.0-SNAPSHOT
-//   com.fasterxml.jackson.core:jackson-databind:2.17.2
-
-import java.io.IOException;
-import java.net.URI;
-import java.net.http.*;
-import java.time.Duration;
-import java.util.Collections;
-
-import org.stellar.sdk.*;
-import org.stellar.sdk.requests.sorobanrpc.*;
-import org.stellar.sdk.xdr.*;
-
-public final class main {
-  private static final String RPC_URL = "https://soroban-testnet.stellar.org";
-  private static final String TESTNET_USDC_ISSUER = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5";
-  private static final HttpClient HTTP = HttpClient.newBuilder()
-    .connectTimeout(Duration.ofSeconds(20))
-    .build();
-  private static final SorobanServer SERVER = new SorobanServer(RPC_URL);
-
-  public static void main(String[] args) throws Exception {
-    //
-    // Generate keypairs
-    //
-    KeyPair parent = KeyPair.random();
-    log("Secret: %s", new String(parent.getSecretSeed()));
-    log("Public: %s", parent.getAccountId());
-
-    //
-    // Fund a new account via friendbot
-    //
-    GetNetworkResponse networkInfo = SERVER.getNetwork();
-    String friendbotUrl = networkInfo != null ? networkInfo.getFriendbotUrl() : null;
-    check(friendbotUrl != null && !friendbotUrl.isBlank(), "Friendbot URL not provided by network");
-    log("Using %s for friendbot funding", friendbotUrl);
-
-    String friendbotResponse = requestFunds(friendbotUrl, parent.getAccountId());
-    log("SUCCESS! You have a new account:\n%s", friendbotResponse);
-
-    //
-    // Fund a new account via CreateAccount operation
-    //
-    KeyPair child = KeyPair.random();
-    Account parentAccount = SERVER.loadAccount(parent.getAccountId());
-
-    Transaction transaction = new TransactionBuilder(parentAccount, Network.TESTNET)
-      .setBaseFee(Transaction.MIN_BASE_FEE)
-      .setTimeout(TransactionBuilder.TIMEOUT_INFINITE)
-      .addOperation(new CreateAccountOperation.Builder(child.getAccountId(), "5").build())
-      .build();
-    transaction.sign(parent);
-
-    long ledgerSeq = submitAndConfirm(transaction);
-    log("Transaction confirmed in ledger %d", ledgerSeq);
-    log("Created the new account %s", child.getAccountId());
-
-    //
-    // Fetch native and USDC balances for account
-    //
-    long nativeBalance = loadNativeBalance(parent.getAccountId());
-    log("Balance for account %s", parent.getAccountId());
-    log("XLM: %d", nativeBalance);
-
-    AssetTypeCreditAlphaNum12 usdcAsset = Asset.createNonNative("USDC", TESTNET_USDC_ISSUER);
-    long trustlineBalance = getTrustlineBalance(parent.getAccountId(), usdcAsset);
-    log("USDC trustline balance (raw): %d", trustlineBalance);
-  }
-
-  private static String requestFunds(String friendbotUrl, String accountId)
-      throws IOException, InterruptedException {
-    String requestUrl = friendbotUrl + "?addr=" + accountId;
-    HttpRequest request = HttpRequest.newBuilder()
-      .uri(URI.create(requestUrl))
-      .timeout(Duration.ofSeconds(30))
-      .GET()
-      .build();
-    HttpResponse<String> response = HTTP.send(request, HttpResponse.BodyHandlers.ofString());
-    check(response.statusCode() / 100 == 2, "Friendbot returned " + response.statusCode() + ": " + response.body());
-    return response.body();
-  }
-  private static long loadNativeBalance(String accountId) throws IOException {
-    LedgerKey key = new LedgerKey();
-    key.setDiscriminant(LedgerEntryType.ACCOUNT);
-    LedgerKeyAccount accountKey = new LedgerKeyAccount();
-    accountKey.setAccountID(KeyPair.fromAccountId(accountId).getXdrAccountId());
-    key.setAccount(accountKey);
-
-    GetLedgerEntriesResponse response = SERVER.getLedgerEntries(Collections.singletonList(key));
-    check(!response.getEntries().isEmpty(), "Account " + accountId + " not found");
-    LedgerEntryData data = LedgerEntryData.fromXdr(response.getEntries().get(0).getXdr());
-    check(data.getAccount() != null, "Ledger entry missing account data");
-    return data.getAccount().getBalance().getInt64();
-  }
-
-  private static long getTrustlineBalance(String accountId, org.stellar.sdk.Asset asset) throws IOException {
-    LedgerKey key = new LedgerKey();
-    key.setDiscriminant(LedgerEntryType.TRUSTLINE);
-    LedgerKeyTrustLine trustLineKey = new LedgerKeyTrustLine();
-    trustLineKey.setAccountID(KeyPair.fromAccountId(accountId).getXdrAccountId());
-    trustLineKey.setAsset(asset.toXdr());
-    key.setTrustLine(trustLineKey);
-
-    GetLedgerEntriesResponse response = SERVER.getLedgerEntries(Collections.singletonList(key));
-    if (response.getEntries().isEmpty()) {
-      return 0L;
-    }
-    LedgerEntryData data = LedgerEntryData.fromXdr(response.getEntries().get(0).getXdr());
-    TrustLineEntry trustLine = data.getTrustLine();
-    if (trustLine == null) {
-      return 0L;
-    }
-    return trustLine.getBalance().getInt64();
-  }
-
-  private static long submitAndConfirm(Transaction transaction) throws IOException, InterruptedException {
-    SendTransactionResponse sendResp = SERVER.sendTransaction(transaction);
-    check(sendResp.getStatus() == SendTransactionStatus.PENDING,
-        "Transaction submission failed: " + sendResp.getStatus());
-
-    GetTransactionResponse txResp = SERVER.pollTransaction(sendResp.getHash());
-    check(txResp.getStatus() == GetTransactionResponse.Status.SUCCESS,
-        "Transaction failed: " + txResp.getStatus());
-    Long ledger = txResp.getLedger() != null ? txResp.getLedger() : txResp.getLatestLedger();
-    check(ledger != null, "Transaction completed but ledger sequence unavailable");
-    return ledger;
-  }
-
-  private static void check(boolean condition, String message) {
-    if (!condition) {
-      throw new IllegalStateException(message);
-    }
-  }
-
-  private static void log(String format, Object... args) {
-    System.out.println(String.format(format, args));
-  }
-}
-```
-
-```rust
-use std::{cell::RefCell, rc::Rc, time::Duration};
-
-use soroban_client::{
-    account::{Account, AccountBehavior},
-    asset::{Asset, AssetBehavior},
-    keypair::{Keypair, KeypairBehavior},
-    network::{NetworkPassphrase, Networks},
-    operation::{self, Operation},
-    transaction::{TransactionBehavior, TransactionBuilder, TransactionBuilderBehavior},
-    xdr, Options, Server,
-};
-
-const TESTNET_USDC_ISSUER: &str = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5";
-
-#[tokio::main]
-pub async fn main() -> Result<(), Box<dyn std::error::Error>> {
-    let server_url = "https://soroban-testnet.stellar.org";
-    let server = Server::new(server_url, Options::default()).expect("Cannot create server");
-
-    //
-    // Generate keypairs
-    //
-    let parent = Keypair::random()?;
-    println!("Secret: {}", parent.secret_key()?);
-    println!("Public: {}", parent.public_key());
-
-    //
-    // Fund a new account via friendbot
-    //
-    let account_data = server.request_airdrop(&parent.public_key()).await?;
-    println!("SUCCESS! You have a new account:\n{account_data:?}");
-
-    let child = Keypair::random()?;
-    let mut parent_account =
-        Account::new(&parent.public_key(), &account_data.sequence_number()).unwrap();
-
-    //
-    // Fund a new account via CreateAccount operation
-    //
-    let mut builder = TransactionBuilder::new(&mut parent_account, Networks::testnet(), None);
-    builder.fee(1000u32);
-    builder.add_operation(
-        Operation::new()
-            .create_account(&child.public_key(), operation::ONE * 5)
-            .unwrap(),
-    );
-
-    let mut tx = builder.build();
-    tx.sign(&[parent]);
-
-    let response = server.send_transaction(tx).await?;
-    let hash = response.hash;
-    println!("Tx hash: {}", hash);
-
-    //
-    // Polling for transaction completion
-    //
-    server
-        .wait_transaction(&hash, Duration::from_secs(15))
-        .map_err(|_| "Failed to create account")
-        .await?;
-
-    //
-    // Fetch native and USDC balances for account
-    //
-    let account_id = child.xdr_account_id();
-    let ledger_key = xdr::LedgerKey::Account(xdr::LedgerKeyAccount { account_id });
-    let response = server.get_ledger_entries(vec![ledger_key]).await?;
-    if let xdr::LedgerEntryData::Account(account) = response.entries.unwrap()[0].to_data() {
-        // Convert the balance from stroops
-        let balance = account.balance / operation::ONE;
-        println!("XLM: {balance}");
-    }
-
-    let account_id = child.xdr_account_id();
-    let asset = Asset::new("USDC", Some(TESTNET_USDC_ISSUER))?.into();
-    let ledger_key = xdr::LedgerKey::Trustline(xdr::LedgerKeyTrustLine { account_id, asset });
-    let response = server.get_ledger_entries(vec![ledger_key]).await?;
-    let entries = response.entries.unwrap_or_default();
-        let usdc_balance = match entries.first().map(|e| e.to_data()) {
-        Some(xdr::LedgerEntryData::Trustline(t)) => t.balance,
-        _ => 0,
-    };
-    println!("USDC trustline balance (raw): {}", usdc_balance);
-
-    Ok(())
-}
-```
-
-</CodeExample>
-
-Ahora que tienes una cuenta y verificas los saldos de sus activos, puedes [comenzar a enviar y recibir pagos](send-and-receive-payments.mdx) o, si estás listo para enfocarte, puedes avanzar y [desarrollar una billetera](../../apps/wallet/overview.mdx) o [emitir un activo Stellar](../../../tokens/anatomy-of-an-asset.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/fee-bump-transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/fee-bump-transactions.mdx
deleted file mode 100644
index caae8e9641..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/fee-bump-transactions.mdx
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: Transacciones de suplemento de tarifa
-description: Usa transacciones fee-bump para pagar las comisiones de transacción en nombre de otra cuenta sin volver a firmar la transacción.
-sidebar_position: 40
----
-
-Las transacciones de suplemento de tarifa fueron introducidas en [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) y permiten que una cuenta pague las tarifas de una transacción existente sin necesidad de volver a firmar la transacción ni gestionar números de secuencia.
-
-Una transacción fee-bump está compuesta por dos partes:
-
-1. Un sobre de transacción interno con su(s) firma(s)
-2. Un sobre de transacción externo con la transacción de suplemento de tarifa y la firma de la cuenta de tarifa
-
-## Casos de uso comunes
-
-Deberías considerar usar fee bumps cuando:
-
-- Estás construyendo un servicio donde quieres cubrir las tarifas de los usuarios
-- Quieres aumentar la tarifa en una transacción existente para que tenga más posibilidades de llegar al libro mayor durante precios elevados
-- Necesitas ajustar la comisión en una transacción preautorizada para que pueda entrar en el ledger si las comisiones mínimas de la red han aumentado
-
-:::note
-
-Usa la [Calculadora de Patrocinio de Billeteras Stellar](../../../tools/developer-tools/wallets.mdx#stellar-wallet-sponsorship-calculator) para estimar los requisitos de XLM para billeteras que buscan usar reservas patrocinadas y transacciones fee-bump para cubrir la creación de cuentas, comisiones de transacción, líneas de confianza y más.
-
-:::
-
-## Atributos
-
-### Sobre de transacción existente (transacción interna)
-
-Antes de crear una transacción fee-bump, primero debes tener una transacción envuelta con sus firmas en un sobre de transacción. Llamaremos a esta transacción la transacción interna.
-
-### Cuenta de comisión
-
-La cuenta que pagará la tarifa por la transacción de suplemento de tarifa. Esta cuenta incurrirá en la tarifa en lugar de la cuenta origen especificada en la transacción interna. Sin embargo, el número de secuencia aún se toma de la cuenta origen.
-
-### Comisión
-
-La comisión máxima por operación que estás dispuesto a pagar por la transacción fee-bump. La transacción de suplemento de tarifa es una operación. Por lo tanto, el número total de operaciones es igual al número de operaciones en la transacción interna más una.
-
-Lee más sobre las tarifas de transacción en nuestra [sección de Tarifas](../../../learn/fundamentals/fees-resource-limits-metering.mdx).
-
-### Reemplazar por comisión
-
-Puedes aplicar una transacción de suplemento de tarifa para aumentar una tarifa originada desde tu propia cuenta. Sin embargo, si envías dos transacciones distintas con la misma cuenta origen y número de secuencia, siendo la segunda una transacción fee-bump, la segunda transacción reemplazará a la primera en la cola solo si la comisión ofrecida en la segunda transacción es 10 veces la comisión ofrecida en la primera. Este número puede parecer aleatorio, pero es una decisión de diseño deliberada para limitar ataques DOS sin introducir demasiada complejidad al protocolo.
-
-### Sobre de transacción fee-bump
-
-Cuando una transacción de suplemento de tarifa está lista para ser firmada, se envuelve en un sobre de transacción. Este sobre contiene la transacción fee-bump y la firma de la cuenta de comisión especificada.
-
-## Validez de una transacción fee-bump
-
-Una transacción de suplemento de tarifa pasa por una serie de comprobaciones en su ciclo de vida para determinar su validez. Se deben cumplir las siguientes condiciones:
-
-- **Cuenta de tarifa** — la cuenta de tarifa para la transacción de suplemento de tarifa debe existir en el libro mayor.
-- **Tarifa**
-  - La tarifa debe ser mayor o igual a la tarifa mínima de red para el número de operaciones en la transacción interna, más uno por el suplemento de tarifa.
-  - La comisión también debe ser mayor o igual a la comisión especificada en la transacción interna.
-  - Si la transacción fee-bump aprovecha el reemplazo por comisión, la comisión debe ser 10 veces mayor que la de la primera transacción.
-- **Firma de la cuenta de tarifa** — el sobre de la transacción de suplemento de tarifa debe contener una firma válida para la cuenta de tarifa. Además, el peso de esa firma debe alcanzar el umbral bajo para la cuenta de comisión, y la frase de acceso de red adecuada debe formar parte del hash de la transacción firmado por la cuenta de comisión.
-- **Saldo de la cuenta de tarifa** — la cuenta de tarifa debe tener un saldo suficiente de XLM para cubrir la tarifa
-- **Transacción interna** — la transacción interna debe ser válida, lo que significa que debe cumplir con los requisitos descritos en la [sección de Validez de una Transacción](../../../learn/fundamentals/transactions/operations-and-transactions.mdx#transaction-and-operation-validity). Si la validación de la transacción interna es exitosa, el resultado es `FEE_BUMP_INNER_SUCCESS`, y los resultados de validación de la transacción interna aparecen en el resultado interno. Si la transacción interna es inválida, el resultado es `FEE_BUMP_INNER_FAILED`, y la transacción fee-bump es inválida porque la transacción interna es inválida.
-
-## Aplicación
-
-El único propósito de una transacción fee-bump es incluir una transacción interna en un conjunto de transacciones. Dado que la transacción fee-bump no tiene efectos secundarios aparte de pagar una comisión — y en el momento en que se paga la comisión la transacción externa debe haber sido válida (de lo contrario los nodos no la hubieran votado) — no hay razón para verificar la validez de la transacción fee-bump en el momento de su aplicación. Por lo tanto, el número de secuencia de la transacción interna siempre se consume al aplicar. Sin embargo, la transacción interna seguirá siendo verificada en cuanto a su validez al aplicar.
-
-Cada resultado de transacción fee-bump contiene un resultado completo de la transacción interna. Este resultado de la transacción interna es exactamente lo que se hubiera producido si no hubiera existido la transacción de suplemento de tarifa, excepto que la tarifa interna siempre será 0.
-
-## Ejemplo: implementar una transacción de suplemento de tarifa
-
-Este ejemplo muestra cómo crear y enviar una transacción de suplemento de tarifa en la red Stellar. Reemplaza los valores clave secret, `SECREY_KEY_1` y `SECREY_KEY_2` de los keypairs que elijas. Este no es un ejemplo para producción, y debes tener cuidado de no exponer tus claves secretas en la web.
-
-<CodeExample>
-
-```js
-import * as StellarSdk from "@stellar/stellar-sdk";
-
-// Define the network passphrase (use 'Testnet' for testing and 'Public Global Stellar Network ; September 2015' for production)
-const networkPassphrase = StellarSdk.Networks.TESTNET;
-
-// Create keypairs for the source account and the fee account
-const sourceKeypair = StellarSdk.Keypair.fromSecret("SECREY_KEY_1");
-const feeKeypair = StellarSdk.Keypair.fromSecret("SECREY_KEY_2");
-
-// Load the source account (this requires network interaction)
-const server = new StellarSdk.rpc.Server("https://soroban-testnet.stellar.org");
-const sourceAccount = await server.getAccount(sourceKeypair.publicKey());
-
-// Construct the inner transaction, just a example tx, to transfer 10 XLM to a destination account
-const innerTransaction = new StellarSdk.TransactionBuilder(sourceAccount, {
-  fee: StellarSdk.BASE_FEE,
-  networkPassphrase,
-})
-  .addOperation(
-    StellarSdk.Operation.payment({
-      destination: "GDWH3P3MNTCMOY42CA7RVEACUUAUPZ73XDYKPYUL3TWOFRF37FD6OVM6",
-      asset: StellarSdk.Asset.native(),
-      amount: "10",
-    }),
-  )
-  .setTimeout(30)
-  .build();
-
-// Sign the inner transaction with the source account
-innerTransaction.sign(sourceKeypair);
-
-// Build the fee-bump transaction
-const feeBumpTransaction =
-  StellarSdk.TransactionBuilder.buildFeeBumpTransaction(
-    feeKeypair,
-    StellarSdk.BASE_FEE * 2,
-    innerTransaction,
-    networkPassphrase,
-  );
-
-// Sign the fee-bump transaction with the fee account
-feeBumpTransaction.sign(feeKeypair);
-
-// Submit the fee-bump transaction to the Stellar network
-server
-  .sendTransaction(feeBumpTransaction)
-  .then((response) => {
-    if (response.status !== "PENDING") {
-      throw response;
-    }
-
-    return server.pollTransaction(response.hash, {
-      sleepStrategy: StellarSdk.rpc.LinearSleepStrategy,
-      attempts: 5,
-    });
-  })
-  .then((response) => {
-    console.log("transaction response:", response);
-  })
-  .catch((error) => {
-    console.error("Something went wrong!", error);
-  });
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/install-deploy-contract-with-code.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/install-deploy-contract-with-code.mdx
deleted file mode 100644
index c9f65de7d3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/install-deploy-contract-with-code.mdx
+++ /dev/null
@@ -1,248 +0,0 @@
----
-title: Instalar y desplegar un contrato inteligente con código
-description: Instalar y desplegar un contrato inteligente con código.
----
-
-<head>
-  <title>Instalar y desplegar un contrato inteligente con código</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Instalar y desplegar un contrato inteligente con código"
-  />
-  <meta
-    property="og:description"
-    content="Esta guía te guiará a través del proceso de instalar y desplegar un contrato inteligente usando js-stellar-sdk. Cubriremos la configuración de un contrato Rust de ejemplo, crear un proyecto Node.js para gestionar el despliegue, y finalmente, instalar el Wasm del contrato y desplegarlo en la red"
-  />
-</head>
-
-Esta guía te guiará a través del proceso de instalar y desplegar un contrato inteligente usando [js-stellar-sdk](https://github.com/stellar/js-stellar-sdk). Cubriremos la configuración de un contrato Rust de ejemplo, crear un proyecto Node.js para gestionar el despliegue, y finalmente, instalar el Wasm del contrato y desplegarlo en la red
-
-## Requisitos previos
-
-Antes de comenzar, asegúrate de tener lo siguiente instalado:
-
-1. [Rust](https://www.rust-lang.org/) y Cargo (para compilar contratos inteligentes)
-2. [Node.js](https://nodejs.org/en) y npm (para ejecutar scripts de despliegue en JavaScript)
-3. [Soroban CLI](../../smart-contracts/getting-started/setup.mdx#install-the-stellar-cli)
-
-## Inicializar un contrato Rust de ejemplo
-
-```bash
-stellar contract init hello-world
-cd hello-world
-stellar contract build
-```
-
-Esta secuencia de comandos crea un nuevo directorio para tu proyecto, inicializa un nuevo contrato inteligente Soroban dentro de ese directorio y desarrolla el contrato. La compilación genera el archivo .wasm en la ruta `hello-word/target/wasm32v1-none/release/hello_world.wasm`
-
-## Crear un Proyecto Node
-
-1. Crea un nuevo directorio para tu proyecto Node.js y navega a él:
-
-```bash
-mkdir deploy-contract
-cd deploy-contract
-```
-
-2. Inicializa un nuevo proyecto Node.js e instala las dependencias necesarias:
-
-```bash
-npm init -y
-npm install @stellar/stellar-sdk fs
-```
-
-## Configurar Scripts de Despliegue
-
-### Importaciones
-
-Importa los módulos necesarios en tu archivo JavaScript:
-
-```javascript
-import * as StellarSDK from "@stellar/stellar-sdk";
-import fs from "fs";
-```
-
-### Instalando el Wasm en la red
-
-Crea una función para subir el archivo Wasm compilado:
-
-```javascript
-async function uploadWasm(filePath) {
-  const bytecode = fs.readFileSync(filePath);
-  const account = await server.getAccount(sourceKeypair.publicKey());
-  const operation = StellarSDK.Operation.uploadContractWasm({ wasm: bytecode });
-  return await buildAndSendTransaction(account, operation);
-}
-```
-
-Esta función lee el archivo Wasm compilado, recupera los detalles de la cuenta de la red e instala el bytecode usando la operación Stellar `uploadContractWasm`, que cuando se envuelve en una transacción se envía a la red.
-
-### Desplegar contrato
-
-Despliega el contrato haciendo referencia al hash del Wasm:
-
-```javascript
-async function deployContract(response) {
-  const account = await server.getAccount(sourceKeypair.publicKey());
-  const operation = StellarSDK.Operation.createCustomContract({
-    wasmHash: response.returnValue.bytes(),
-    address: StellarSDK.Address.fromString(sourceKeypair.publicKey()),
-    salt: response.hash,
-  });
-  const responseDeploy = await buildAndSendTransaction(account, operation);
-  const contractAddress = StellarSDK.StrKey.encodeContract(
-    StellarSDK.Address.fromScAddress(
-      responseDeploy.returnValue.address(),
-    ).toBuffer(),
-  );
-  console.log(contractAddress);
-}
-```
-
-Esta función utiliza el hash del Wasm para desplegar el contrato usando la operación stellar `createCustomContract`, que cuando se envuelve en una transacción se envía a la red, generando una dirección de contrato.
-
-### Construyendo, Firmando y Enviando la Transacción
-
-Gestionar la construcción, firma y envío de transacciones:
-
-```javascript
-async function buildAndSendTransaction(account, operations) {
-  const transaction = new StellarSDK.TransactionBuilder(account, {
-    fee: StellarSDK.BASE_FEE,
-    networkPassphrase: StellarSDK.Networks.TESTNET,
-  })
-    .addOperation(operations)
-    .setTimeout(30)
-    .build();
-
-  const tx = await server.prepareTransaction(transaction);
-  tx.sign(sourceKeypair);
-
-  console.log("Submitting transaction...");
-  let response = await server.sendTransaction(tx);
-  const hash = response.hash;
-  console.log(`Transaction hash: ${hash}`);
-  console.log("Awaiting confirmation...");
-
-  while (true) {
-    response = await server.getTransaction(hash);
-    if (response.status !== "NOT_FOUND") {
-      break;
-    }
-    await new Promise((resolve) => setTimeout(resolve, 1000));
-  }
-
-  if (response.status === "SUCCESS") {
-    console.log("Transaction successful.");
-    return response;
-  } else {
-    console.log("Transaction failed.");
-    throw new Error("Transaction failed");
-  }
-}
-```
-
-Esta función construye una transacción, la firma y la envía a la red, gestionando cualquier reintento necesario para la confirmación de la transacción.
-
-## Ejecutando el Script
-
-Ejecuta el script de despliegue:
-
-```javascript
-const server = new StellarSDK.rpc.Server(
-  "https://soroban-testnet.stellar.org:443",
-);
-const sourceKeypair = StellarSDK.Keypair.fromSecret("Your_Secret_Key");
-const wasmFilePath =
-  "../hello-world/target/wasm32v1-none/release/hello_world.wasm"; // Adjust this path as necessary
-
-try {
-  let uploadResponse = await uploadWasm(wasmFilePath);
-  await deployContract(uploadResponse);
-} catch (error) {
-  console.error(error);
-}
-```
-
-Reemplaza "Your_Secret_Key" con tu clave secreta real. Este script inicia la subida del archivo Wasm y despliega el contrato, resultando en una dirección de contrato donde el contrato está desplegado.
-
-Este es solo un código de demostración, así que asegúrate de manejar secretos y claves privadas de forma segura en entornos de producción y nunca las expongas en tus repositorios de código. Esta guía debería proporcionarte un camino claro para instalar y desplegar tus contratos inteligentes usando código Javascript.
-
-## Script Completo
-
-Aquí están todos los fragmentos apilados juntos en un solo archivo para conveniencia:
-
-```javascript
-import * as StellarSDK from "@stellar/stellar-sdk";
-import fs from "fs";
-async function uploadWasm(filePath) {
-  const bytecode = fs.readFileSync(filePath);
-  const account = await server.getAccount(sourceKeypair.publicKey());
-  const operation = StellarSDK.Operation.uploadContractWasm({ wasm: bytecode });
-  return await buildAndSendTransaction(account, operation);
-}
-async function deployContract(response) {
-  const account = await server.getAccount(sourceKeypair.publicKey());
-  const operation = StellarSDK.Operation.createCustomContract({
-    wasmHash: response.returnValue.bytes(),
-    address: StellarSDK.Address.fromString(sourceKeypair.publicKey()),
-    salt: response.hash,
-  });
-  const responseDeploy = await buildAndSendTransaction(account, operation);
-  const contractAddress = StellarSDK.StrKey.encodeContract(
-    StellarSDK.Address.fromScAddress(
-      responseDeploy.returnValue.address(),
-    ).toBuffer(),
-  );
-  console.log(contractAddress);
-}
-async function buildAndSendTransaction(account, operations) {
-  const transaction = new StellarSDK.TransactionBuilder(account, {
-    fee: StellarSDK.BASE_FEE,
-    networkPassphrase: StellarSDK.Networks.TESTNET,
-  })
-    .addOperation(operations)
-    .setTimeout(30)
-    .build();
-
-  const tx = await server.prepareTransaction(transaction);
-  tx.sign(sourceKeypair);
-
-  console.log("Submitting transaction...");
-  let response = await server.sendTransaction(tx);
-  const hash = response.hash;
-  console.log(`Transaction hash: ${hash}`);
-  console.log("Awaiting confirmation...");
-
-  while (true) {
-    response = await server.getTransaction(hash);
-    if (response.status !== "NOT_FOUND") {
-      break;
-    }
-    await new Promise((resolve) => setTimeout(resolve, 1000));
-  }
-
-  if (response.status === "SUCCESS") {
-    console.log("Transaction successful.");
-    return response;
-  } else {
-    console.log("Transaction failed.");
-    throw new Error("Transaction failed");
-  }
-}
-
-const server = new StellarSDK.rpc.Server(
-  "https://soroban-testnet.stellar.org:443",
-);
-const sourceKeypair = StellarSDK.Keypair.fromSecret("Your_Secret_Key");
-const wasmFilePath =
-  "../hello-world/target/wasm32v1-none/release/hello_world.wasm"; // Adjust this path as necessary
-
-try {
-  let uploadResponse = await uploadWasm(wasmFilePath);
-  await deployContract(uploadResponse);
-} catch (error) {
-  console.error(error);
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/install-wasm-bytecode.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/install-wasm-bytecode.mdx
deleted file mode 100644
index 7eba61a2b5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/install-wasm-bytecode.mdx
+++ /dev/null
@@ -1,301 +0,0 @@
----
-title: Instalar WebAssembly (Wasm) bytecode usando código
-description: Instala el Wasm del contrato usando js-stellar-sdk.
----
-
-<head>
-  <title>Instalar WebAssembly (Wasm) bytecode usando código</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Instalar WebAssembly (Wasm) bytecode usando código"
-  />
-  <meta
-    property="og:description"
-    content="Esta guía te guiará a través de la instalación del wasm del contrato usando js-stellar-sdk."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Instalar WebAssembly (Wasm) bytecode usando código
-
-Este proceso sube el código del contrato a la Stellar Testnet en una transacción, el blob Wasm subido es una [fuente de contrato](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-02.md#contract-source), que se puede pensar como una 'clase' de un contrato. Varias [instancias de un contrato pueden ser desplegadas](../conventions/deploy-contract.mdx) que comparten la misma fuente, pero tienen su propio estado. Varios [instancias de un contrato pueden ser desplegadas](../conventions/deploy-contract.mdx) que comparten la misma fuente, pero tienen su propio estado.
-
-## Requisitos previos
-
-Antes de comenzar, asegúrate de tener lo siguiente instalado para compilar un contrato inteligente:
-
-1. [Rust](https://www.rust-lang.org/) y Cargo (para compilar contratos inteligentes)
-2. El [Stellar CLI](https://github.com/stellar/stellar-cli)
-
-## Inicializar y construir un contrato Rust de muestra
-
-```bash
-stellar contract init hello-world
-cd hello-world
-
-# use rust compiler to compile Rust project into a WebAssembly (Wasm) dynamic library (cdylib).
-stellar contract build
-# cargo rustc --manifest-path=contracts/hello_world/Cargo.toml --crate-type=cdylib --target=wasm32v1-none --release
-```
-
-Estamos inicializando el contrato `hello_world` por defecto en [soroban_examples](https://github.com/stellar/soroban-examples) al directorio `hello-world`. Puedes usar la opción `-w` para crear con otro ejemplo como `account`.
-
-Después de desarrollar el contrato para la versión, el archivo .wasm generado está en la ruta `hello-word/target/wasm32v1-none/release/hello_world.wasm`
-
-## Subir Wasm a la blockchain Stellar
-
-Podemos usar uno de los [SDKs](https://developers.stellar.org/docs/tools/sdks/library), instala las dependencias necesarias para tu lenguaje de programación elegido:
-
-- SDK de JavaScript: [Node.js](https://nodejs.org/en) y npm
-- SDK de Python: [pip](https://pip.pypa.io/en/stable/installation/)
-
-Crea un nuevo directorio para tu proyecto y navega dentro de él:
-
-```bash
-mkdir install-wasm
-cd install-wasm
-```
-
-### Ejecutando el script de instalación
-
-Se pueden usar diferentes lenguajes de programación para subir el archivo `.wasm`, su hash SHA256 se utiliza para desplegar el contrato.
-
-<Tabs>
-
-<TabItem value="js" label="JavaScript">
-Esta guía te guiará a través de la instalación del Wasm del contrato usando el SDK de JavaScript: [js-stellar-sdk](https://github.com/stellar/js-stellar-sdk).
-
-Crea un nuevo proyecto Node.js con un archivo JavaScript, y instala las dependencias necesarias:
-
-```bash
-touch index.js
-npm init es6 -y
-npm install @stellar/stellar-sdk fs
-```
-
-Ejecuta el script con `node index.js`, lee el archivo Wasm, obtiene los detalles de la cuenta y sube el contrato en una transacción:
-
-```javascript
-// Import necessary modules in your JavaScript file:
-import * as StellarSDK from "@stellar/stellar-sdk";
-import fs from "fs";
-
-async function uploadWasm(filePath) {
-  // reads the compiled Wasm file to buffer
-  const bytecode = fs.readFileSync(filePath);
-
-  // retrieves account details from the network
-  const account = await server.getAccount(sourceKeypair.publicKey());
-
-  // installs the bytecode with a `uploadContractWasm` Stellar operation wrapped in a transaction sent to the network
-  const operation = StellarSDK.Operation.uploadContractWasm({ wasm: bytecode });
-  return await buildAndSendTransaction(account, operation);
-}
-
-// constructs a transaction, signs it, and submits it to the network, handling any necessary retries for transaction confirmation.
-async function buildAndSendTransaction(account, operations) {
-  const transaction = new StellarSDK.TransactionBuilder(account, {
-    fee: StellarSDK.BASE_FEE,
-    networkPassphrase: StellarSDK.Networks.TESTNET,
-  })
-    .addOperation(operations)
-    .setTimeout(30)
-    .build();
-
-  const tx = await server.prepareTransaction(transaction);
-  tx.sign(sourceKeypair);
-
-  console.log("Submitting transaction...");
-  let response = await server.sendTransaction(tx);
-  const hash = response.hash;
-  console.log(`Transaction hash: ${hash}`);
-  console.log("Awaiting confirmation...");
-
-  while (true) {
-    response = await server.getTransaction(hash);
-    if (response.status !== "NOT_FOUND") {
-      break;
-    }
-    await new Promise((resolve) => setTimeout(resolve, 1000));
-  }
-
-  if (response.status === "SUCCESS") {
-    console.log("Transaction successful.");
-    return response;
-  } else {
-    console.log("Transaction failed.");
-    throw new Error("Transaction failed");
-  }
-}
-
-// Upload contract to the testnet
-const server = new StellarSDK.rpc.Server(
-  "https://soroban-testnet.stellar.org:443",
-);
-// Replace `Your_Secret_Key`
-const sourceKeypair = StellarSDK.Keypair.fromSecret("Your_Secret_Key");
-// Adjust this path as necessary
-const wasmFilePath = "../target/wasm32v1-none/release/hello_world.wasm";
-
-try {
-  let uploadResponse = await uploadWasm(wasmFilePath);
-  const byteArray = uploadResponse.returnValue.bytes();
-  const wasmHash = byteArray.toString("hex");
-  console.log(`Wasm hash: ${wasmHash}`);
-} catch (error) {
-  console.error(error);
-}
-```
-
-</TabItem>
-<TabItem value="py" label="Python">
-Esta guía te guiará a través de la instalación del Wasm del contrato usando el SDK de Python: [py-stellar-base](https://stellar-sdk.readthedocs.io/en/soroban/).
-
-Crea un nuevo script en Python y instala las dependencias necesarias:
-
-```bash
-touch install.py
-pip install stellar-sdk
-```
-
-Ejecuta el script con `python3 install.py`, lee el archivo Wasm, obtiene los detalles de la cuenta y sube el contrato en una transacción:
-
-```py
-import asyncio
-import time
-from stellar_sdk import Keypair, Network, SorobanServer, TransactionBuilder, xdr as stellar_xdr
-from stellar_sdk.exceptions import PrepareTransactionException
-from stellar_sdk.soroban_rpc import GetTransactionStatus
-import hashlib
-
-
-def print_wasm_hash(wasm_bytes):
-    # Create a SHA256 hash object
-    sha256_hash = hashlib.sha256()
-
-    # Update the hash object with the WASM bytes
-    sha256_hash.update(wasm_bytes)
-
-    # Get the digest and convert it to a stellar_sdk.xdr.Hash object
-    hash_bytes = sha256_hash.digest()
-    xdr_hash = stellar_xdr.Hash(hash_bytes)
-    hash_hex_str = xdr_hash.hash.hex()
-    print(f"Wasm Hash: {hash_hex_str}")
-
-
-async def upload_wasm(file_path):
-    # Read the compiled Wasm file
-    with open(file_path, 'rb') as file:
-        wasm_bytes = file.read()
-
-    # Retrieve account details from the network
-    account = server.load_account(source_keypair.public_key)
-
-    # print wasm hash for later deployment
-    print_wasm_hash(wasm_bytes)
-
-    # Install the bytes with an 'uploadContractWasm' Stellar operation
-    return await build_and_send_transaction(account, wasm_bytes)
-
-
-async def build_and_send_transaction(account, bytes):
-    transaction = (
-        TransactionBuilder(
-            source_account=account,
-            network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-        )
-        .append_upload_contract_wasm_op(bytes)
-        .set_timeout(30)
-        .build()
-    )
-
-    print("Preparing transaction...")
-    try:
-        tx = server.prepare_transaction(transaction)
-    except PrepareTransactionException as e:
-        print(f"Got exception: {e}")
-        return None
-
-    tx.sign(source_keypair)
-
-    print("Submitting transaction...")
-    response = server.send_transaction(tx)
-    hash = response.hash
-    print(f"Transaction hash: {hash}")
-    print("Awaiting confirmation...")
-
-    while True:
-        response = server.get_transaction(hash)
-        if response.status != GetTransactionStatus.NOT_FOUND:
-            break
-        time.sleep(1)
-
-    if response.status == GetTransactionStatus.SUCCESS:
-        print("Transaction successful.")
-        return response
-    else:
-        print("Transaction failed.")
-        raise Exception("Transaction failed")
-
-# Upload contract to the testnet
-server = SorobanServer("https://soroban-testnet.stellar.org:443")
-# Replace 'Your_Secret_Key' with your actual secret key
-source_keypair = Keypair.from_secret("Your_Secret_Key")
-# Adjust this path as necessary
-wasm_file_path = "../target/wasm32v1-none/release/hello_world.wasm"
-
-
-async def main():
-    try:
-      await upload_wasm(wasm_file_path)
-    except Exception as error:
-        print(f"Error: {error}")
-
-# Run the main function
-asyncio.run(main())
-```
-
-</TabItem>
-</Tabs>
-
-Reemplaza `"Your_Secret_Key"` con tu clave secreta real.
-
-```bash
-stellar keys generate --global hello --network testnet
-stellar keys show hello
-```
-
-El Stellar CLI se puede usar para generar identidades, por ejemplo, `hello`, y mostrar su clave secreta.
-
-:::tip
-
-Asegúrate de manejar las claves secretas y privadas de manera segura en ambientes de producción y nunca las expongas en tus repositorios de código.
-
-:::
-
-```bash
-Submitting transaction...
-Transaction hash: cef7a63667fe5b0ddcde5562d90e0a40bc04c69616916d1d7fa74a8571bbd82f
-Awaiting confirmation...
-Transaction successful.
-Wasm hash: 275405755441e4be59555bb5c5fd81e84ed21659015d8f3594796c1cf3f380db
-```
-
-El hash de la transacción de carga devuelta se puede ver con herramientas en línea: [stellar.expert/explorer/testnet/tx/cef7a63667fe5b0ddcde5562d90e0a40bc04c69616916d1d7fa74a8571bbd82f](https://stellar.expert/explorer/testnet/tx/cef7a63667fe5b0ddcde5562d90e0a40bc04c69616916d1d7fa74a8571bbd82f)
-
-[Los contratos subidos se almacenan en entradas de ledger ContractCodeEntry.](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-02.md#uploading-wasm-sources-using-invokehostfunctionop) Estas entradas están indexadas por el hash del Wasm usado para subirlos.
-
-Puedes usar el hash del Wasm para el despliegue con el Stellar CLI:
-
-```bash
-stellar contract deploy \
-    --source-account hello \
-    --network testnet \
-    --wasm-hash 275405755441e4be59555bb5c5fd81e84ed21659015d8f3594796c1cf3f380db
-# CC6NAQE3ZHRQV3NPQB3F3NYEFBAMEABA4KQTM6A2V5V7PBR5H3UEU3MW
-```
-
-Visualiza el contrato desplegado usando el identificador devuelto con herramientas en línea: [stellar.expert/explorer/testnet/contract/CC6NAQE3ZHRQV3NPQB3F3NYEFBAMEABA4KQTM6A2V5V7PBR5H3UEU3MW](https://stellar.expert/explorer/testnet/contract/CC6NAQE3ZHRQV3NPQB3F3NYEFBAMEABA4KQTM6A2V5V7PBR5H3UEU3MW)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/invoke-contract-tx-sdk.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/invoke-contract-tx-sdk.mdx
deleted file mode 100644
index 256446054d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/invoke-contract-tx-sdk.mdx
+++ /dev/null
@@ -1,449 +0,0 @@
----
-title: Invocar una función de contrato en una transacción usando SDKs
-hide_table_of_contents: true
-description: Usa el Stellar SDK para crear, simular y ensamblar una transacción.
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-Este es un ejemplo simple que utiliza el SDK de Stellar para crear, simular y luego ensamblar una transacción Stellar que invoca una función `increment` del [contrato de ejemplo auth](../../smart-contracts/example-contracts/auth.mdx).
-
-<Tabs>
-<TabItem value="js" label="JavaScript">
-
-:::tip
-
-Por favor, dirígete a [la página de inicio del proyecto](https://github.com/stellar/js-stellar-sdk) del SDK de JavaScript para aprender cómo instalarlo.
-
-:::
-
-Primero, sube los bytes de [el contrato de ejemplo](../../smart-contracts/example-contracts/auth.mdx) a la blockchain usando [Stellar CLI](../../../tools/cli/stellar-cli.mdx). Esto se llama "instalar" porque, desde la perspectiva de la blockchain misma, este contrato ha sido instalado.
-
-```bash
-stellar contract build
-stellar contract upload --wasm target/wasm32v1-none/release/test_auth_contract.wasm --network testnet
-```
-
-Esto devolverá un hash; guárdalo, lo usarás pronto. Para este ejemplo, usaremos `bc7d436bab44815c03956b344dc814fac3ef60e9aca34c3a0dfe358fcef7527f`.
-
-Aún no se ha desplegado ningún contrato con este hash. En Soroban, puedes tener muchos contratos inteligentes que todos referencian el mismo hash de Wasm, definiendo su comportamiento. Lo haremos desde el propio código de JavaScript a continuación.
-
-```ts
-import { Keypair } from "@stellar/stellar-sdk"
-import { Client, basicNodeSigner } from "@stellar/stellar-sdk/contract"
-import { Server } from "@stellar/stellar-sdk/rpc"
-
-// As mentioned, we are using Testnet for this example
-const rpcUrl = "https://soroban-testnet.stellar.org"
-const networkPassphrase = "Test SDF Network ; September 2015"
-const wasmHash = "bc7d436bab44815c03956b344dc814fac3ef60e9aca34c3a0dfe358fcef7527f"
-
-/**
- * Generate a random keypair and fund it
- */
-async function generateFundedKeypair() {
-  const keypair = Keypair.random();
-  const server = new Server(rpcUrl);
-  await server.requestAirdrop(keypair.publicKey());
-  return keypair
-}
-
-(async () => {
-  // The source account will be used to sign and send the transaction.
-  const sourceKeypair = await generateFundedKeypair()
-
-  // If you are using a browser, you can pass in `signTransaction` from your
-  // Wallet extension such as Freighter. If you're using Node, you can use
-  // `signTransaction` from `basicNodeSigner`.
-  const { signTransaction } = basicNodeSigner(sourceKeypair, networkPassphrase)
-
-  // This constructs and simulates a deploy transaction. Once we sign and send
-  // this below, it will create a brand new smart contract instance that
-  // references the wasm we uploaded with the CLI.
-  const deployTx = await Client.deploy(
-    null, // if the contract has a `__constructor` function, its arguments go here
-    {
-      networkPassphrase,
-      rpcUrl,
-      wasmHash,
-      publicKey: sourceKeypair.publicKey(),
-      signTransaction,
-    }
-  )
-  // Like other `Client` methods, `deploy` returns an `AssembledTransaction`,
-  // which wraps logic for signing, sending, and awaiting completion of the
-  // transaction. Once that all completes, the `result` of this transaction
-  // will contain the final `Client` instance, which we can use to invoke
-  // methods on the new contract. Here we are using JS destructuring to get the
-  // `result` key from the object returned by `signAndSend`, and put it in a
-  // local variable called `client`.
-  const { result: client } = await deployTx.signAndSend()
-
-  ...
-```
-
-:::tip Cliente de un contrato existente
-
-Si no necesitas desplegar un contrato, y en su lugar ya conoces el ID de un contrato desplegado, puedes instanciar un Cliente para él directamente. Esto usa argumentos similares a los que se utilizan para `Client.deploy` arriba, con la adición de `contractId`:
-
-```diff
--const deployTx = await Client.deploy(
--  null,
--  {
-+const client = await Client.from({
-+  contractId: "C123abc…",
-   networkPassphrase,
-   rpcUrl,
-   wasmHash,
-   publicKey: sourceKeypair.publicKey(),
-   signTransaction,
- })
-```
-
-:::
-
-Ahora que hemos instanciado un `client`, podemos usarlo para llamar a métodos en el contrato. Retomando donde nos quedamos:
-
-```ts
-  ...
-
-  // This will construct and simulate an `increment` transaction. Since the
-  // `auth` contract requires that this transaction be signed, we will need to
-  // call `signAndSend` on it, like we did with `deployTx` above.
-  const incrementTx = await client.increment({
-    user: sourceKeypair.publicKey(), // who needs to sign
-    value: 1, // how much to increment by
-  })
-
-  // For calls that don't need to be signed, you can get the `result` of their
-  // simulation right away, on a call like `client.increment()` above.
-  const { result } = await incrementTx.signAndSend()
-
-  // Now you can do whatever you need to with the `result`, which in this case
-  // contains the new value of the incrementor/counter.
-  console.log("New incremented value:", result)
-})();
-```
-
-</TabItem>
-
-<TabItem value="py" label="Python">
-
-:::tip
-
-Por favor, dirígete a [la página de inicio del proyecto](https://github.com/StellarCN/py-stellar-base) del SDK de Python para aprender cómo instalarlo.
-
-Además, Python proporciona mucho código de ejemplo, que puedes encontrar [aquí](https://github.com/StellarCN/py-stellar-base/tree/main/examples).
-
-:::
-
-```py
-import time
-
-from stellar_sdk import Keypair, Network, SorobanServer, TransactionBuilder, scval
-from stellar_sdk import xdr as stellar_xdr
-from stellar_sdk.exceptions import PrepareTransactionException
-from stellar_sdk.soroban_rpc import GetTransactionStatus, SendTransactionStatus
-
-secret = "SAAPYAPTTRZMCUZFPG3G66V4ZMHTK4TWA6NS7U4F7Z3IMUD52EK4DDEV"
-rpc_server_url = "https://soroban-testnet.stellar.org:443"
-network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-
-# Here we will use a deployed instance of the `increment` example contract.
-contract_id = "CDOGJBJMRVVXW5K3UJ5BGVJ5RSQXQB4UFVQYVFOIARC2UYXSEPF4YAVR"
-# The source account will be used to sign and send the transaction.
-source_keypair = Keypair.from_secret(secret)
-# Configure SorobanClient to use the `stellar-rpc` instance of your choosing.
-soroban_server = SorobanServer(rpc_server_url)
-# Transactions require a valid sequence number (which varies from one account to another).
-# We fetch this sequence number from the RPC server.
-source = soroban_server.load_account(source_keypair.public_key)
-
-tx = (
-    # The transaction begins as pretty standard. The source account, minimum fee,
-    # and network passphrase are provided.
-    TransactionBuilder(source, network_passphrase, base_fee=100)
-    # This transaction will be valid for the next 30 seconds
-    .set_timeout(30)
-    # The invocation of the `increment` function of our contract is added to the transaction.
-    .append_invoke_contract_function_op(
-        contract_id=contract_id,
-        function_name="increment",
-        parameters=[scval.to_address(source_keypair.public_key), scval.to_uint32(5)],
-    ).build()
-)
-
-print(f"builtTransaction: {tx.to_xdr()}")
-
-try:
-    # We use the RPC server to "prepare" the transaction. This simulating the
-    # transaction, discovering the soroban data, and updating the
-    # transaction to include that soroban data. If you know the soroban data ahead of
-    # time, you could manually use `set_soroban_data` and skip this step.
-    tx = soroban_server.prepare_transaction(tx)
-except PrepareTransactionException as e:
-    print(f"Prepare Transaction Failed: {e.simulate_transaction_response}")
-    raise e
-
-# Sign the transaction with the source account's keypair.
-tx.sign(source_keypair)
-
-# Let's see the base64-encoded XDR of the transaction we just built.
-print(f"Signed prepared transaction XDR: {tx.to_xdr()}")
-
-# Submit the transaction to the Stellar-RPC server. The RPC server will
-# then submit the transaction into the network for us. Then we will have to
-# wait, polling `get_transaction` until the transaction completes.
-send_transaction_data = soroban_server.send_transaction(tx)
-print(f"Sent transaction: {send_transaction_data}")
-if send_transaction_data.status != SendTransactionStatus.PENDING:
-    print(send_transaction_data.error_result_xdr)
-    raise Exception("Send transaction failed")
-
-while True:
-    print("Waiting for transaction to be confirmed...")
-    # Poll `get_transaction` until the status is not "NOT_FOUND"
-    get_transaction_data = soroban_server.get_transaction(send_transaction_data.hash)
-    if get_transaction_data.status != GetTransactionStatus.NOT_FOUND:
-        break
-    time.sleep(3)
-
-print(f"getTransaction response: {get_transaction_data}")
-
-if get_transaction_data.status == GetTransactionStatus.SUCCESS:
-    # The transaction was successful, so we can extract the `result_meta_xdr`
-    transaction_meta = stellar_xdr.TransactionMeta.from_xdr(
-        get_transaction_data.result_meta_xdr
-    )
-    result = transaction_meta.v3.soroban_meta.return_value
-    # Find the return value from the contract and return it
-    print(f"Transaction result: {scval.from_uint32(result)}")
-else:
-    # The transaction failed, so we can extract the `result_xdr`
-    print(f"Transaction failed: {get_transaction_data.result_xdr}")
-    raise Exception("Transaction failed")
-```
-
-</TabItem>
-
-<TabItem value="java" label="Java">
-
-:::tip
-
-Por favor, dirígete a [la página de inicio del proyecto](https://github.com/lightsail-network/java-stellar-sdk) del SDK de Java para aprender cómo instalarlo.
-
-:::
-
-```java
-import org.stellar.sdk.AccountNotFoundException;
-import org.stellar.sdk.InvokeHostFunctionOperation;
-import org.stellar.sdk.KeyPair;
-import org.stellar.sdk.Network;
-import org.stellar.sdk.PrepareTransactionException;
-import org.stellar.sdk.SorobanServer;
-import org.stellar.sdk.Transaction;
-import org.stellar.sdk.TransactionBuilder;
-import org.stellar.sdk.TransactionBuilderAccount;
-import org.stellar.sdk.requests.sorobanrpc.SorobanRpcErrorResponse;
-import org.stellar.sdk.responses.sorobanrpc.GetTransactionResponse;
-import org.stellar.sdk.responses.sorobanrpc.SendTransactionResponse;
-import org.stellar.sdk.scval.Scv;
-import org.stellar.sdk.xdr.SCVal;
-import org.stellar.sdk.xdr.TransactionMeta;
-
-import java.io.IOException;
-import java.util.List;
-
-public class Example {
-    public static void main(String[] args) throws SorobanRpcErrorResponse, IOException, InterruptedException {
-        // The source account will be used to sign and send the transaction.
-        KeyPair sourceKeypair = KeyPair.fromSecretSeed("SAAPYAPTTRZMCUZFPG3G66V4ZMHTK4TWA6NS7U4F7Z3IMUD52EK4DDEV");
-
-        // Configure SorobanClient to use the `stellar-rpc` instance of your choosing.
-        SorobanServer sorobanServer = new SorobanServer("https://soroban-testnet.stellar.org");
-
-        // Here we will use a deployed instance of the `increment` example contract.
-        String contractAddress = "CDOGJBJMRVVXW5K3UJ5BGVJ5RSQXQB4UFVQYVFOIARC2UYXSEPF4YAVR";
-
-        // Transactions require a valid sequence number (which varies from one account to
-        // another). We fetch this sequence number from the RPC server.
-        TransactionBuilderAccount sourceAccount = null;
-        try {
-            sourceAccount = sorobanServer.getAccount(sourceKeypair.getAccountId());
-        } catch (AccountNotFoundException e) {
-            throw new RuntimeException("Account not found, please activate it first");
-        }
-
-        // The invocation of the `increment` function.
-        InvokeHostFunctionOperation operation = InvokeHostFunctionOperation.invokeContractFunctionOperationBuilder(contractAddress, "increment",
-                List.of(
-                        Scv.toAddress(sourceAccount.getAccountId()),
-                        Scv.toUint32(5)
-                )
-        ).build();
-
-        // Create a transaction with the source account and the operation we want to invoke.
-        Transaction transaction = new TransactionBuilder(sourceAccount, Network.TESTNET)
-                .addOperation(operation) // The invocation of the `increment` function of our contract is added to the transaction.
-                .setTimeout(30) // This transaction will be valid for the next 30 seconds
-                .setBaseFee(100)  // The base fee is 100 stroops (0.00001 XLM)
-                .build();
-
-        // We use the RPC server to "prepare" the transaction. This simulating the
-        // transaction, discovering the soroban data, and updating the
-        // transaction to include that soroban data. If you know the soroban data ahead of
-        // time, you could manually use `setSorobanData` and skip this step.
-        try {
-            transaction = sorobanServer.prepareTransaction(transaction);
-        } catch (PrepareTransactionException e) {
-            // You should handle the error here
-            System.out.println("Prepare Transaction Failed: " + e.getMessage());
-            throw new RuntimeException(e);
-        }
-
-        // Sign the transaction with the source account's keypair.
-        transaction.sign(sourceKeypair);
-
-        // Let's see the base64-encoded XDR of the transaction we just built.
-        System.out.println("Signed prepared transaction XDR: " + transaction.toEnvelopeXdrBase64());
-
-        // Submit the transaction to the Stellar-RPC server. The RPC server will then
-        // submit the transaction into the network for us. Then we will have to wait,
-        // polling `getTransaction` until the transaction completes.
-        SendTransactionResponse response = sorobanServer.sendTransaction(transaction);
-        if (!SendTransactionResponse.SendTransactionStatus.PENDING.equals(response.getStatus())) {
-            throw new RuntimeException("Sending transaction failed");
-        }
-
-        // Poll `getTransaction` until the status is not "NOT_FOUND"
-        GetTransactionResponse getTransactionResponse;
-        while (true) {
-            System.out.println("Waiting for transaction confirmation...");
-            // See if the transaction is complete
-            getTransactionResponse = sorobanServer.getTransaction(response.getHash());
-            if (!GetTransactionResponse.GetTransactionStatus.NOT_FOUND.equals(getTransactionResponse.getStatus())) {
-                break;
-            }
-            // Wait one second
-            Thread.sleep(1000);
-        }
-
-        System.out.println("Get transaction response: " + getTransactionResponse);
-
-        if (GetTransactionResponse.GetTransactionStatus.SUCCESS.equals(getTransactionResponse.getStatus())) {
-            // The transaction was successful, so we can extract the `resultMetaXdr`
-            TransactionMeta transactionMeta = TransactionMeta.fromXdrBase64(getTransactionResponse.getResultMetaXdr());
-            SCVal result = transactionMeta.getV3().getSorobanMeta().getReturnValue();
-            long parsedResult = Scv.fromUint32(result);
-            System.out.println("Transaction result: " + parsedResult);
-        } else {
-            // The transaction failed, so we can extract the `resultXdr`
-            System.out.println("Transaction failed: " + getTransactionResponse.getResultXdr());
-        }
-    }
-}
-```
-
-</TabItem>
-<TabItem value="rust" label="Rust">
-
-:::tip
-
-Por favor, visita [la página principal del proyecto](https://github.com/rahul-soshte/rs-soroban-client) de la biblioteca Rust Soroban Client para aprender cómo instalarla.
-
-Otros ejemplos se encuentran en la carpeta [`examples/`](https://github.com/rahul-soshte/rs-soroban-client/tree/main/examples) del repositorio.
-
-:::
-
-Primero, despliega [el contrato de ejemplo](../../smart-contracts/example-contracts/auth.mdx) en la blockchain usando [Stellar CLI](../../../tools/cli/stellar-cli.mdx).
-
-```bash
-stellar contract build
-stellar contract deploy --wasm ./target/wasm32v1-none/release/soroban_auth_contract.wasm --network testnet
-```
-
-Esto devolverá un ID de contrato; en el siguiente ejemplo usaremos `CBU3OHKZ2BHOHK5VMG3HBWIW3PBQHZLNMHNJUGM23W5NBFA75JMMWAVT`.
-
-```rust
-use std::time::Duration;
-
-use soroban_client::{
-    account::{Account, AccountBehavior},
-    address::{Address, AddressTrait},
-    contract::{ContractBehavior, Contracts},
-    keypair::{Keypair, KeypairBehavior},
-    network::{NetworkPassphrase, Networks},
-    soroban_rpc::TransactionStatus,
-    transaction::{TransactionBehavior, TransactionBuilder, TransactionBuilderBehavior},
-    Options, Server,
-};
-
-#[tokio::main]
-pub async fn main() -> Result<(), Box<dyn std::error::Error>> {
-    let server_url = "https://soroban-testnet.stellar.org";
-    let server = Server::new(server_url, Options::default())?;
-
-    let source_keypair = Keypair::random()?;
-    let source_public_key = &source_keypair.public_key();
-    let signers = [source_keypair];
-
-    // Get account information from server
-    let account_data = server.request_airdrop(source_public_key).await?;
-    let mut source_account = Account::new(source_public_key, &account_data.sequence_number())?;
-
-    // Calling the increment method of the contract
-    let contract_addr = "CBU3OHKZ2BHOHK5VMG3HBWIW3PBQHZLNMHNJUGM23W5NBFA75JMMWAVT";
-    let contract = Contracts::new(contract_addr).unwrap();
-    let tx = TransactionBuilder::new(&mut source_account, Networks::testnet(), None)
-        .fee(1000u32)
-        .add_operation(contract.call(
-            "increment",
-            Some(vec![
-                Address::account(signers[0].raw_public_key())?.to_sc_val()?,
-                3u32.into(),
-            ]),
-        ))
-        .build();
-
-    // Preparing the transaction, this will call `server.simulate_transaction` and
-    // `assemble_transaction` to enhance the transaction with the soroban data and auths
-    let ptxr = server.prepare_transaction(&tx).await;
-    let mut ptx = match ptxr {
-        Ok(p) => p,
-        Err(e) => {
-            // Manage errors here
-            return Err(e.into());
-        }
-    };
-
-    // Sign the transaction with the source account
-    ptx.sign(&signers);
-
-    println!("> Calling increment on contract {contract_addr}",);
-    let response = server.send_transaction(ptx).await?;
-
-    let hash = &response.hash;
-    println!(">> Tx hash: {hash}");
-    let counter: u32 = match server.wait_transaction(hash, Duration::from_secs(15)).await {
-        Ok(tx_result) if tx_result.status == TransactionStatus::Success => {
-            // On success we can extract the returned value
-            let (_meta, ret_val) = tx_result.to_result_meta().expect("No result meta");
-            ret_val
-                .expect("None returned value")
-                .try_into()
-                .expect("Return value is not u32")
-        }
-        _ => {
-            return Err("Failed to create contract".into());
-        }
-    };
-    println!(">> Counter: {counter}",);
-    println!();
-
-    Ok(())
-}
-```
-
-</TabItem>
-</Tabs>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/path-payments.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/path-payments.mdx
deleted file mode 100644
index 57b8e63757..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/path-payments.mdx
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: Pagos con rutas
-sidebar_position: 60
-description: Enviar un pago donde el activo recibido sea diferente del activo enviado.
----
-
-En un pago con ruta, el activo recibido es diferente del activo enviado. En lugar de que la operación transfiera activos directamente de una cuenta a otra, los pagos con rutas cruzan a través del SDEX y/o Fondos de Liquidez antes de llegar a la cuenta de destino. Para que el pago con ruta tenga éxito, debe existir una oferta DEX o un camino de exchange mediante Fondos de Liquidez. A veces puede ser necesario realizar varios saltos de conversión para que tenga éxito.
-
-Por ejemplo:
-
-La Cuenta A vende XLM → [compra XLM / vende ETH → compra ETH / vende BTC → compra BTC / vende USDC] → La Cuenta B recibe USDC
-
-Es posible que los pagos con rutas fallen si no existen rutas de exchange viables.
-
-Para más información sobre el Stellar Decentralized Exchange y los Fondos de Liquidez, consulta nuestra [Liquidez en Stellar: Entrada de Enciclopedia sobre SDEX y Fondos de Liquidez](../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx).
-
-## Operaciones
-
-Los pagos con rutas utilizan las operaciones Path Payment Strict Send o Path Payment Strict Receive.
-
-### Path Payment Strict Send
-
-Permite a un usuario especificar la cantidad del activo a enviar. La cantidad recibida variará según las ofertas en los libros de órdenes y/o Fondos de Liquidez.
-
-### Path Payment Strict Receive
-
-Permite a un usuario especificar la cantidad del activo recibido. La cantidad enviada variará según las ofertas en los libros de órdenes y Fondos de Liquidez.
-
-## Pagos con rutas - más información
-
-- Los pagos con rutas no permiten que las ofertas intermedias provengan de la cuenta de origen, ya que esto resultaría en una tasa de exchange peor. Debes dividir el pago con ruta en dos pagos con rutas más pequeños o asegurarte de que las ofertas de la cuenta de origen no estén en la parte superior del libro de órdenes.
-- Los saldos se liquidan al final de la operación.
-  - Esto es especialmente importante cuando (`Destination, Destination Asset) == (Source, Send Asset`) ya que proporciona una funcionalidad equivalente a obtener un préstamo sin intereses durante la duración de la operación.
-- `Destination min` es una medida de protección, que te permite especificar un límite inferior para una conversión aceptable. Si las ofertas en los libros de órdenes no son lo suficientemente favorables para que la operación entregue esa cantidad, la operación fallará.
-
-## Ejemplo
-
-Primero, asegúrate de que el receptor tenga establecida una trustline para el activo que recibirá. En este ejemplo, usaremos USDC como el activo recibido. El remitente enviará XLM, que será convertido a USDC mediante la operación de pago con ruta.
-
-```js
-import {
-  Horizon,
-  Asset,
-  Keypair,
-  TransactionBuilder,
-  Networks,
-  BASE_FEE,
-  Operation,
-  Memo,
-} from "@stellar/stellar-sdk";
-
-const USDC_ISSUER = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"; // USDC issuer on Stellar Testnet
-const USDC_ASSET = new Asset("USDC", USDC_ISSUER); // USDC asset on Stellar Testnet
-const RECEIVER_SECRET = "S..."; // Receiver's secret key
-
-const SENDER_SECRET = "S..."; // Sender's secret key
-const horizonServer = new Horizon.Server("https://horizon-testnet.stellar.org");
-
-// Create a USDC trustline for the receiver
-const receiverKP = Keypair.fromSecret(RECEIVER_SECRET);
-let account = await horizonServer.loadAccount(receiverKP.publicKey());
-let transaction = new TransactionBuilder(account, {
-  fee: BASE_FEE * 100,
-  networkPassphrase: Networks.TESTNET,
-})
-  .addOperation(
-    Operation.changeTrust({
-      asset: USDC_ASSET,
-      limit: "10",
-    }),
-  )
-  .addMemo(Memo.text("Trusting USDC"))
-  .setTimeout(30)
-  .build();
-
-transaction.sign(receiverKP);
-const resp = await SERVER.submitTransaction(transaction);
-console.log("resp", resp);
-```
-
-Ahora enviemos un pago con ruta del remitente al receptor, convirtiendo XLM a USDC.
-
-```js
-// Use path payment to send XLM from the receiver to the sender, who receives USDC
-let senderKP = Keypair.fromSecret(SENDER_SECRET);
-let account = await horizonServer.loadAccount(senderKP.publicKey());
-let transaction = new TransactionBuilder(account, {
-  fee: BASE_FEE * 100,
-  networkPassphrase: Networks.TESTNET,
-})
-  .addOperation(
-    Operation.pathPaymentStrictReceive({
-      sendAsset: Asset.native(), // Sending XLM
-      sendMax: "10", // Maximum amount of XLM to send
-      destAsset: USDC_ASSET, // Receiving USDC
-      destAmount: "1", // Amount of USDC to receive
-      destination: receiverKP.publicKey(), // Receiver's public key
-    }),
-  )
-  .addMemo(Memo.text("XLM to USDC"))
-  .setTimeout(30)
-  .build();
-
-transaction.sign(senderKP);
-const resp = await horizonServer.submitTransaction(transaction);
-console.log("resp", resp);
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
deleted file mode 100644
index 70c3a5726d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
+++ /dev/null
@@ -1,458 +0,0 @@
----
-title: "Cuentas agrupadas: cuentas muxed y memos"
-description: Usa cuentas muxed para diferenciar entre cuentas individuales dentro de una cuenta agrupada.
-sidebar_position: 60
----
-
-Al desarrollar una aplicación o servicio en Stellar, una de las primeras decisiones que debes tomar es cómo manejar las cuentas de los usuarios.
-
-Puedes crear una cuenta Stellar para cada usuario, pero la mayoría de los servicios custodiados, incluyendo los exchanges de criptomonedas, optan por usar una única cuenta Stellar agrupada para gestionar transacciones en nombre de sus usuarios. En estos casos, la función de cuentas muxed puede mapear las transacciones a cuentas individuales a través de una base de datos interna de clientes.
-
-:::note
-
-Antes usábamos memos para este propósito; sin embargo, usar cuentas muxed es mejor a largo plazo. Actualmente, no todas las billeteras, exchanges y anchors soportan cuentas muxed, por lo que probablemente quieras soportar tanto memos como cuentas muxed, al menos por un tiempo.
-
-:::
-
-## Cuentas agrupadas
-
-Una cuenta agrupada permite que un único ID de cuenta Stellar se comparta entre muchos usuarios. Generalmente, los servicios que usan cuentas agrupadas rastrean a sus clientes en una base de datos interna separada y usan la función de cuentas muxed para asociar un pago entrante o saliente con el cliente interno correspondiente.
-
-Los beneficios de usar una cuenta agrupada son costos más bajos — no se necesitan reservas base por cada cuenta — y menor complejidad de claves — solo necesitas administrar un keypair de cuenta. Sin embargo, con una única cuenta agrupada, ahora te corresponde gestionar todos los saldos y pagos de los clientes individuales. Ya no puedes confiar en el ledger de Stellar para acumular valor, gestionar errores y atomicidad, o administrar transacciones en base a cada cuenta individual.
-
-## Cuentas muxed
-
-Las cuentas muxed están integradas en el protocolo por conveniencia y estandarización. Distinguen cuentas individuales que existen bajo una sola cuenta tradicional de Stellar. Combinan la dirección familiar `GABC…` con un ID entero de 64 bits.
-
-Las cuentas muxed no existen en el ledger, pero sí su cuenta base `GABC…` compartida.
-
-Las cuentas muxed están definidas en [CAP-0027](https://stellar.org/protocol/cap-27), introducidas en el Protocolo 13, y su representación en cadena está descrita en [SEP-0023](https://stellar.org/protocol/sep-23).
-
-Es seguro que todas las billeteras implementen el envío a cuentas muxed.
-
-Si deseas recibir depósitos a cuentas muxed, ten en cuenta que aún no todas las billeteras ni exchanges las soportan.
-
-### Formato de dirección
-
-Las cuentas muxed tienen su propio formato de dirección que empieza con el prefijo M. Por ejemplo, partiendo de una dirección tradicional de Stellar: `GA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJVSGZ`, podemos crear nuevas cuentas muxed con diferentes IDs. Los IDs están incrustados en la propia dirección — al analizar las direcciones de cuentas muxed, obtendrás la dirección G mencionada más arriba, más un número adicional.
-
-- `MA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJUAAAAAAAAAAAACJUQ` tiene el ID 0, mientras que
-- `MA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJUAAAAAAAAAABUTGI4` tiene el ID 420.
-
-Ambas direcciones actuarán sobre la dirección subyacente `GA7Q…` cuando se usen con una de las operaciones compatibles.
-
-### Operaciones compatibles
-
-No todas las operaciones se pueden usar con cuentas muxed. Estas son las que puedes usar:
-
-- La cuenta fuente de cualquier operación o transacción;
-- La fuente de pago de una transacción con fee-bump;
-- El destino de los tres tipos de pagos:
-  - `Payment`,
-  - `PathPaymentStrictSend`, y
-  - `PathPaymentStrictReceive`;
-- El destino de un AccountMerge; y
-- El objetivo de una operación `Clawback` (es decir, el campo from).
-
-Demostraremos algunos de estos en la sección de ejemplos.
-
-No hay validación en los IDs y, para la red Stellar, todas las operaciones soportadas funcionan exactamente como si no usaras una cuenta muxed.
-
-## Ejemplos
-
-Los siguientes ejemplos demuestran cómo funcionan las cuentas muxed en la práctica, mostrando los tres escenarios principales de pago: cuenta estándar a cuenta estándar, de muxed a no muxed, y de muxed a muxed.
-
-**_Nota:_** _La implementación completa del código para todos los ejemplos sigue después de esta sección. Puedes ejecutar ejemplos individuales usando sus funciones respectivas o ejecutar los tres secuencialmente usando la función principal._
-
-Las cuentas muxed (M...) son una abstracción del lado del cliente que realmente no existen en el ledger de Stellar; solo la cuenta base G existe on-chain. Esto significa que operaciones como cargar datos de la cuenta siempre deben usar la cuenta base G, mientras que las operaciones de pago pueden proporcionar dirección M o G. El código sólo cambia ligeramente para manejar esta distinción entre la cuenta lógica muxed y la cuenta real.
-
-**Comisiones de transacción:** Todas las transacciones incurren en una comisión (típicamente 100 stroops o 0.0000100 XLM). Dado que la cuenta custodio es la fuente de todas las transacciones en estos ejemplos, las comisiones siempre se debitan del saldo de la cuenta custodio. Verás esto reflejado en las comparaciones de saldo antes y después, donde la cuenta custodio disminuye tanto por el monto del pago como por la comisión de transacción.
-
-### Ejemplo 1 - Pago Básico (G → G)
-
-Este ejemplo establece el comportamiento básico con un pago estándar entre dos cuentas regulares de Stellar. Ambas cuentas existen directamente en el ledger, demostrando el flujo tradicional de pago en Stellar sin abstracciones de cuentas muxed. El saldo de la cuenta custodio disminuye en 10 XLM más las comisiones de transacción, mientras que la cuenta externa aumenta exactamente en 10 XLM.
-
-### Ejemplo 2 - Pago de Muxed a No Muxed (M → G)
-
-Esto demuestra un pago desde una cuenta muxed (que representa un cliente custodio) a una cuenta regular de Stellar. La cuenta custodio subyacente ejecuta el pago, pero la transacción incluye la dirección muxed para identificar qué cliente la inició.
-
-La transacción se firma con las llaves del custodio ya que las cuentas muxed no tienen llaves secretas. El saldo de la cuenta custodio disminuye en 10 XLM más las comisiones.
-
-### Ejemplo 3 - Pago de Muxed a Muxed (M → M)
-
-Cuando dos cuentas muxed comparten la misma cuenta subyacente, los pagos entre ellas son esencialmente la cuenta enviándose a sí misma. El monto del pago (+10 XLM y -10 XLM) se cancela, pero las comisiones de transacción aún se cobran porque la operación queda registrada en el ledger.
-
-El saldo de la cuenta disminuye sólo por la comisión de la transacción. Puede que desees detectar estas transacciones en tu aplicación para evitar comisiones innecesarias. Ten en cuenta que los pagos entre cuentas muxed con diferentes cuentas subyacentes se comportarían como pagos normales de G a G.
-
----
-
-## Implementación del código
-
-_El siguiente código demuestra los tres ejemplos utilizando Stellar RPC. Puedes ejecutar todos los ejemplos secuencialmente con `runAllMuxedExamples()` o ejecutar ejemplos individuales usando sus funciones respectivas._
-
-<CodeExample>
-
-```js
-import * as sdk from "@stellar/stellar-sdk";
-
-const server = new sdk.rpc.Server("https://soroban-testnet.stellar.org");
-
-const custodian = sdk.Keypair.random();
-const outsider = sdk.Keypair.random();
-
-let custodianAcc, outsiderAcc, customers;
-
-// Setup function to fund accounts and create muxed customers
-async function preamble() {
-  console.log("=== FUNDING ACCOUNTS WITH XLM ===");
-  await Promise.all([
-    server.requestAirdrop(custodian.publicKey()),
-    server.requestAirdrop(outsider.publicKey()),
-  ]);
-  console.log("All accounts funded with XLM via airdrop");
-
-  [custodianAcc, outsiderAcc] = await Promise.all([
-    server.getAccount(custodian.publicKey()),
-    server.getAccount(outsider.publicKey()),
-  ]);
-
-  customers = ["1", "22", "333", "4444"].map(
-    (id) => new sdk.MuxedAccount(custodianAcc, id),
-  );
-
-  console.log("\n=== ACCOUNT SETUP ===");
-  console.log("Custodian:\n       ", custodian.publicKey());
-  console.log("Outsider:\n       ", outsider.publicKey());
-  console.log("Customers:");
-  customers.forEach((customer) => {
-    console.log(
-      " " + customer.id().padStart(4, " ") + ":",
-      customer.accountId(),
-    );
-  });
-}
-
-// Example 1: Basic payment between two G accounts
-async function runUnmuxedExample() {
-  console.log("=== BASIC PAYMENT EXAMPLE (G → G) ===");
-
-  console.log("=== INITIAL BALANCES ===");
-  await showBalance(custodianAcc);
-  await showBalance(outsiderAcc);
-
-  await makePayment(
-    custodianAcc,
-    outsiderAcc,
-    "Basic Payment from G to G address",
-  );
-
-  console.log("\n=== FINAL BALANCES ===");
-  const finalCustodianAcc = await server.getAccount(custodian.publicKey());
-  const finalOutsiderAcc = await server.getAccount(outsider.publicKey());
-  await showBalance(finalCustodianAcc);
-  await showBalance(finalOutsiderAcc);
-
-  console.log("\n=== BASIC PAYMENT EXAMPLE COMPLETED ===");
-}
-
-// Example 2: Payment from M account to G account
-async function runMuxedToUnmuxedExample() {
-  console.log("=== MUXED TO UNMUXED PAYMENT EXAMPLE (M → G) ===");
-
-  console.log("=== INITIAL BALANCES ===");
-  await showBalance(custodianAcc);
-  await showBalance(outsiderAcc);
-  const src = customers[0];
-  console.log(
-    `Sending 10 XLM from Customer ${src.id()} to ${formatAccount(
-      outsiderAcc.accountId(),
-    )}.`,
-  );
-
-  await makePayment(src, outsiderAcc, "Payment from M to G address");
-
-  console.log("\n=== FINAL BALANCES ===");
-  const finalCustodianAcc = await server.getAccount(custodian.publicKey());
-  const finalOutsiderAcc = await server.getAccount(outsider.publicKey());
-  await showBalance(finalCustodianAcc);
-  await showBalance(finalOutsiderAcc);
-
-  console.log("\n=== MUXED TO UNMUXED EXAMPLE COMPLETED ===");
-}
-
-// Example 3: Payment between two M accounts
-async function runMuxedToMuxedExample() {
-  console.log("=== MUXED TO MUXED PAYMENT EXAMPLE (M → M) ===");
-
-  console.log("=== INITIAL BALANCES ===");
-  await showBalance(custodianAcc);
-
-  const src = customers[1]; // Customer 22
-  const dest = customers[2]; // Customer 333
-
-  console.log(
-    `Sending 10 XLM from Customer ${src.id()} to Customer ${dest.id()}.`,
-  );
-
-  await makePayment(src, dest, "Payment from M to M address");
-
-  console.log("\n=== FINAL BALANCES ===");
-  const finalCustodianAcc = await server.getAccount(custodian.publicKey());
-  await showBalance(finalCustodianAcc);
-
-  console.log("\n=== MUXED TO MUXED EXAMPLE COMPLETED ===");
-}
-
-// Main function that runs preamble once and then all three examples
-async function runAllMuxedExamples() {
-  try {
-    // Run setup/funding only once
-    await preamble();
-
-    // Show initial state
-    console.log("=== OVERALL INITIAL BALANCES ===");
-    await showBalance(custodianAcc);
-    await showBalance(outsiderAcc);
-    console.log("\n" + "=".repeat(60) + "\n");
-
-    // Run all three examples sequentially
-    await runUnmuxedExample();
-    console.log("\n" + "=".repeat(60) + "\n");
-
-    await runMuxedToUnmuxedExample();
-    console.log("\n" + "=".repeat(60) + "\n");
-
-    await runMuxedToMuxedExample();
-
-    console.log("\n=== ALL MUXED ACCOUNT EXAMPLES COMPLETED ===");
-  } catch (error) {
-    console.error("Error in examples:", error.message);
-  }
-}
-
-// Helper function to format account ID with label
-function formatAccount(accountId) {
-  const shortId = accountId.substring(0, 8);
-  if (accountId === custodian.publicKey()) {
-    return `${shortId} (Custodian)`;
-  } else if (accountId === outsider.publicKey()) {
-    return `${shortId} (Outsider)`;
-  }
-
-  // Check if it's a muxed account by finding the matching customer
-  const matchingCustomer = customers?.find(
-    (customer) => customer.accountId() === accountId,
-  );
-  if (matchingCustomer) {
-    return `${accountId.substring(0, 8)}...${accountId.slice(
-      -6,
-    )} (Customer ${matchingCustomer.id()})`;
-  }
-  return shortId;
-}
-
-function scaleAsset(x) {
-  return Number(x) / 10000000; // Preserves decimal precision
-}
-
-// Helper function to get XLM balance using RPC
-function getXLMBalance(accountId) {
-  return server
-    .getAccountEntry(accountId)
-    .then((accountEntry) => {
-      return scaleAsset(accountEntry.balance().toBigInt()).toFixed(7);
-    })
-    .catch(() => "0");
-}
-
-// Helper function to submit transaction and poll for completion using RPC
-function submitAndPollTransaction(transaction, description = "Transaction") {
-  return server.sendTransaction(transaction).then((submitResponse) => {
-    if (submitResponse.status !== "PENDING") {
-      throw new Error(
-        `Transaction submission failed: ${submitResponse.status}`,
-      );
-    }
-
-    console.log(`${description} submitted: ${submitResponse.hash}`);
-
-    return server.pollTransaction(submitResponse.hash).then((finalResponse) => {
-      if (finalResponse.status === "SUCCESS") {
-        console.log(`${description} completed successfully`);
-        return {
-          hash: submitResponse.hash,
-          status: finalResponse.status,
-          resultXdr: finalResponse.resultXdr,
-        };
-      } else {
-        throw new Error(`${description} failed: ${finalResponse.status}`);
-      }
-    });
-  });
-}
-
-function buildTx(source, signer, ops) {
-  var tx = new sdk.TransactionBuilder(source, {
-    fee: sdk.BASE_FEE,
-    networkPassphrase: sdk.Networks.TESTNET,
-  });
-
-  ops.forEach((op) => tx.addOperation(op));
-  tx = tx.setTimeout(30).build();
-  tx.sign(signer);
-  return tx;
-}
-
-// Helper function to load account, handling muxed accounts
-function loadAccount(account) {
-  if (sdk.StrKey.isValidMed25519PublicKey(account.accountId())) {
-    return loadAccount(account.baseAccount());
-  } else {
-    return server.getAccount(account.accountId());
-  }
-}
-
-// Helper function to display balance of an account
-async function showBalance(acc) {
-  const balance = await getXLMBalance(acc.accountId());
-  console.log(`${formatAccount(acc.accountId())}: ${balance} XLM`);
-}
-
-// Function to make a payment from source to destination account
-async function makePayment(source, dest, description = "Payment") {
-  console.log(
-    `\nPayment: ${formatAccount(source.accountId())} → ${formatAccount(
-      dest.accountId(),
-    )} (10 XLM)`,
-  );
-
-  const accountBeforePayment = await loadAccount(source);
-  console.log("Before payment:");
-  await showBalance(accountBeforePayment);
-
-  let payment = sdk.Operation.payment({
-    source: source.accountId(),
-    destination: dest.accountId(),
-    asset: sdk.Asset.native(),
-    amount: "10",
-  });
-
-  let tx = buildTx(accountBeforePayment, custodian, [payment]);
-
-  await submitAndPollTransaction(tx, description);
-
-  const accountAfterPayment = await loadAccount(source);
-  console.log("After payment:");
-  await showBalance(accountAfterPayment);
-}
-
-// Run the main function
-runAllMuxedExamples();
-```
-
-</CodeExample>
-
-### Ejecutando los Ejemplos
-
-- **Todos los Ejemplos**: `runAllMuxedExamples()` - Ejecuta la configuración una vez y corre los tres ejemplos
-- **Ejemplos Individuales**:
-- `runUnmuxedExample()` - Pago básico G→G
-- `runMuxedToUnmuxedExample()` - Pago Muxed→Unmuxed
-- `runMuxedToMuxedExample()` - Pago Muxed→Muxed
-
-**_Nota:_** _Al ejecutar ejemplos individuales, asegúrate de llamar primero a `preamble()` para configurar y financiar las cuentas._
-
-### Más ejemplos
-
-Como es común en la mayoría de las características a nivel de protocolo, puedes encontrar más ejemplos de uso e inspiración en la suite de pruebas correspondiente para tu SDK favorito. Por ejemplo, [aquí](https://github.com/stellar/js-stellar-base/blob/master/test/unit/muxed_account_test.js) están algunos casos de prueba en JavaScript.
-
-### Preguntas frecuentes
-
-**¿Qué pasa si pago a una dirección muxed, pero el destinatario no las soporta?**
-
-En general, no deberías enviar pagos a direcciones muxed en plataformas que no las soporten. Estas plataformas ni siquiera podrán proporcionar direcciones de destino muxed desde un principio.
-
-Aún así, si esto ocurre, analizar una transacción con un parámetro muxed sin manejarlo puede llevar a una de dos situaciones:
-
-- Si tu SDK está desactualizado, el análisis fallará. Deberías actualizar tu SDK. Por ejemplo, el SDK de JavaScript mostrará un mensaje útil:
-
-```
-
-“destination is invalid; did you forget to enable muxing?”
-
-```
-
-- Si tu SDK está actualizado, verás la dirección muxed (`M...`) analizada correctamente. Lo que sucede a continuación depende de tu aplicación.
-
-No obstante, la operación se ejecutará con éxito en la red. En el caso de los pagos, por ejemplo, la dirección principal del destino seguirá recibiendo los fondos.
-
-**¿Qué pasa si quiero pagar a una cuenta muxed, pero mi plataforma no las soporta?**
-
-En este caso, no uses una dirección muxed. Es probable que la plataforma falle al crear la operación. Probablemente quieras usar el método legado de incluir un memo en la transacción, en su lugar.
-
-**¿Qué hago si recibo una transacción con direcciones muxed y un ID de memo?**
-
-En un mundo ideal, esta situación nunca sucedería. Puedes determinar si los IDs subyacentes son iguales; si no lo son, se trata de una transacción malformada y recomendamos no enviarla a la red.
-
-**¿Qué pasa si obtengo errores al usar cuentas muxed?**
-
-En versiones actualizadas de los SDKs de Stellar, las cuentas muxed son admitidas de forma nativa por defecto. Sin embargo, si estás usando una versión antigua de un SDK, pueden seguir estando ocultas detrás de una característica flag.
-
-Si obtienes errores al usar direcciones muxed en operaciones admitidas como: “destino es inválido; ¿habilitaste muxing?”
-
-Recomendamos actualizar a la última versión de todos los SDKs de Stellar que uses. Sin embargo, si eso no es posible por alguna razón, necesitarás habilitar la característica flag antes de interactuar con cuentas muxed. Consulta la documentación de tu SDK para detalles.
-
-**¿Qué sucede si paso una dirección muxed a una operación incompatible?**
-
-Solo ciertas operaciones permiten cuentas muxed, como se describió anteriormente. Pasar una dirección muxed a un parámetro incompatible con un SDK actualizado debería resultar en un error de compilación o de tiempo de ejecución en el momento de uso.
-
-Por ejemplo, al usar incorrectamente el SDK de JavaScript:
-
-<CodeExample>
-
-```js
-const mAddress =
-  "MA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJUAAAAAAAAAABUTGI4";
-transactionBuilder.addOperation(
-  Operation.setTrustLineFlags({
-    trustor: mAddress, // wrong!
-    asset: someAsset,
-    flags: { clawbackEnabled: false },
-  }),
-);
-```
-
-</CodeExample>
-
-El resultado en tiempo de ejecución sería:
-
-“Error: byte de versión inválido. se esperaba 48, se obtuvo 96”
-
-Este mensaje de error indica que el `trustor` no se pudo analizar como un ID de cuenta Stellar (`G...`). En otras palabras, tu código fallará y la operación inválida nunca llegará a la red.
-
-**¿Cómo valido direcciones Stellar?**
-
-Debes usar los métodos de validación proporcionados por tu SDK o seguir cuidadosamente el [SEP-23](https://stellar.org/protocol/sep-23). Por ejemplo, el SDK de JavaScript proporciona los siguientes métodos para validar direcciones Stellar:
-
-```ts
-namespace StrKey {
-  function isValidEd25519PublicKey(publicKey: string): boolean;
-  function isValidMed25519PublicKey(publicKey: string): boolean;
-}
-```
-
-También hay abstracciones para construir y gestionar tanto cuentas muxed como regulares; consulta la documentación de tu SDK para detalles.
-
-## Memo - cuentas diferenciadas
-
-Antes de la introducción de las cuentas muxed, productos y servicios que dependían de cuentas agrupadas a menudo usaban memos de transacción para diferenciar entre usuarios. Admitir cuentas muxed es mejor a largo plazo, pero por ahora puedes querer admitir tanto memos como cuentas muxed ya que no todos los exchanges, anchors y billeteras admiten cuentas muxed.
-
-Para aprender sobre otros propósitos para los cuales se pueden usar los memos, consulta nuestra [sección de Memos](../../../learn/fundamentals/transactions/operations-and-transactions.mdx#memo).
-
-## ¿Por qué son mejores las cuentas muxed a largo plazo?
-
-Las cuentas muxed son una mejor forma de diferenciar entre individuos en una cuenta agrupada porque tienen mejor:
-
-- Compartibilidad — en lugar de preocuparte por cosas propensas a errores como copiar y pegar IDs de memo, simplemente puedes compartir tu dirección M... dirección.
-- Soporte en SDK — los distintos SDKs admiten esta abstracción de forma nativa, permitiéndote crear, gestionar y trabajar con cuentas muxed fácilmente. Esto significa que pueden aparecer direcciones muxed al analizar cualquiera de los campos que las admiten, por lo que debes estar preparado para manejarlas. Consulta la documentación de tu SDK para detalles; por ejemplo, la [v7.0.0](https://github.com/stellar/js-stellar-base/releases/tag/v7.0.0) de la biblioteca stellar-base del SDK de JavaScript describe todos los campos y funciones relacionados con las cuentas muxed.
-- Eficiencia — al combinar cuentas virtuales relacionadas bajo el paraguas de una sola cuenta, puedes evitar mantener reservas y pagar tarifas por cada una de ellas individualmente en el ledger. También puedes combinar varios pagos a múltiples destinos en una sola transacción ya que ya no necesitas el campo memo por transacción.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/send-and-receive-c-accounts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/send-and-receive-c-accounts.mdx
deleted file mode 100644
index be5c9fba9e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/send-and-receive-c-accounts.mdx
+++ /dev/null
@@ -1,218 +0,0 @@
----
-title: Enviar y recibir pagos de Cuentas de Contrato
-description: Aprende a enviar pagos a y recibir pagos de Cuentas de Contrato en la red Stellar.
-sidebar_position: 7
----
-
-import Details from "@theme/Details";
-
-Los pagos entre Cuentas de Contrato (direcciones C) y Cuentas Clásicas (direcciones G) están admitidos a nivel de protocolo, pero existen diferencias en las implementaciones necesarias para admitirlas. Esta guía cubrirá implementaciones para aplicaciones que usan cuentas clásicas G y desean admitir transacciones con Cuentas de Contrato.
-
-## Recibir pagos de Cuentas de Contrato (de C a G)
-
-Si un remitente está usando una Cuenta de Contrato y envía un [token SAC](../../../tokens/stellar-asset-contract.mdx) (como XLM, USDC, etc.), la transacción será recibida normalmente por la cuenta G ya que está soportada a nivel de protocolo.
-
-### Recibir pagos de Cuentas de Contrato que requieren un memo
-
-Entidades como exchange y emisores de activos suelen usar cuentas omnibus, utilizando una dirección de recepción compartida y un memo identificador único, como:
-
-- **Cuenta:** `GBLVHX33XGOBDOXK7ERDL34NVH6WW7VTT2OBAHPJ7G3D423HBG5NOMY7`
-- **ID de Memo:** `123456789`
-
-Las transacciones que involucran Cuentas de Contrato utilizan invocaciones de contrato para ejecutar una función 'transfer' en el contrato del activo. Este tipo de transacción no permite usar el campo 'memo'; en cambio, la aplicación emisora lo codificará en la dirección, generando una dirección multiplexada única que incluye la cuenta receptora (GBLVHX…) y el id proporcionado en el campo muxed id (123456789).
-
-Para admitir depósitos provenientes de Cuentas de Contrato, no es necesario cambiar la información mostrada a los clientes ni las cuentas de depósito usadas por el exchange. Las billeteras seguirán usando la cuenta G y el memo proporcionado para enviar un pago a la cuenta G del exchange incluyendo el memo con el ID único.
-
-Esa es la principal diferencia entre recibir de clientes usando cuentas G o de Contrato: en lugar de mirar el campo memo para identificar la cuenta individual, observarás el ID multiplexado. Todo lo demás permanece igual.
-
-#### Ejemplo usando Horizon
-
-**Recibiendo de una dirección G**
-
-Usando el endpoint `accounts/{acc_id}/transactions` de Horizon ([ejemplo](https://horizon-testnet.stellar.org/accounts/GBLVHX33XGOBDOXK7ERDL34NVH6WW7VTT2OBAHPJ7G3D423HBG5NOMY7/transactions))
-
-El campo memo estará presente en la respuesta.
-
-**Ejemplo de respuesta desde una dirección G:**
-
-```json
-{
-  "memo": "123456789",
-  "memo_bytes": "MTIzNDU2Nzg5",
-  "source_account": "GCNG5JXJY3LNRMXCX23RIGKTURQACTSV5LL6NKL535BYRGOGWUX6J45Y",
-  "memo_type": "text"
-}
-```
-
-**Recibir desde una Cuenta de Contrato**
-
-Usando el endpoint `accounts/{acc_id}/payments` de Horizon ([ejemplo](https://horizon-testnet.stellar.org/accounts/GBLVHX33XGOBDOXK7ERDL34NVH6WW7VTT2OBAHPJ7G3D423HBG5NOMY7/payments))
-
-Después de que se procesa la transacción, este detalle de pago estará presente en el endpoint '/payments', bajo una sección llamada 'asset_balance_changes', que mostrará el ID codificado y la dirección G subyacente por separado.
-
-Es importante destacar que la sección 'asset_balance_changes' solo soporta activos Stellar y transacciones que usan la función `transfer` en el [Contrato de Activos Stellar (SAC)](../../../tokens/stellar-asset-contract.mdx).
-
-**Respuesta de ejemplo desde una Cuenta de Contrato:**
-
-```json
-{
-  "asset_balance_changes": [
-    {
-      "asset_type": "native",
-      "type": "transfer",
-      "from": "CBP4GFAK4GDKCMVLNIHRZPEAPT7CFYTBKICOXCVMP2FEN3QFKCRZ27KS",
-      "to": "GBLVHX33XGOBDOXK7ERDL34NVH6WW7VTT2OBAHPJ7G3D423HBG5NOMY7",
-      "amount": "1.0000000",
-      "destination_muxed_id": "123456789"
-    }
-  ]
-}
-```
-
-Para un ejemplo de código detallado, consulta la sección 'Monitoreo de Pagos -> Usando la API de Horizon' de [los ejemplos de este repositorio](https://github.com/fazzatti/c-address-payment-examples#monitoring-payments).
-
-#### Ejemplo usando RPC
-
-Desde el lanzamiento de los Eventos de Activos Unificados ([CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)) en el Protocolo 23, varias transacciones que involucran activos Stellar emiten eventos estandarizados que pueden ser ingeridos tanto por la API de Horizon como por el Stellar RPC. Si los fondos se envían a través de una operación 'payment' o invocando la función 'transfer' del contrato de activos, se emite el mismo tipo de evento para ambos casos.
-
-Para monitorear estos pagos, se usa el método '[getEvents](../../../data/apis/rpc/api-reference/methods/getEvents.mdx)' del RPC de Stellar para transmitir eventos emitidos por el Contrato de Activos Stellar. Se puede usar un filtro para especificar el activo objetivo (ID del contrato SAC) y las cuentas.
-
-**Desde una dirección G**
-
-Cuando el receptor es una dirección G normal, la parte valor del evento es simplemente la cantidad recibida.
-
-```json
-{
-  "inSuccessfulContractCall": true,
-  "topicJson": [
-    {
-      "symbol": "transfer"
-    },
-    {
-      "address": "GD6MYLASTCZ3H4UFLH2YSIASHJNBFUCKC5YHGU44VCH2BGHN3WJQX6LG"
-    },
-    {
-      "address": "GA4PDUF3BLBSK47UTNY44AIZAP5EPHW2UIJRKB5HN76HHC55IWKSIHFD"
-    },
-    {
-      "string": "native"
-    }
-  ],
-  "valueJson": {
-    "i128": "10000000"
-  }
-}
-```
-
-**Desde una Cuenta de Contrato**
-
-Cuando la transacción se envía usando una cuenta muxed, la parte valor del evento se desglosa en un objeto que contiene la cantidad y el ID único codificado en la dirección.
-
-```json
-{
-  "inSuccessfulContractCall": true,
-  "topicJson": [
-    {
-      "symbol": "transfer"
-    },
-    {
-      "address": "GD6MYLASTCZ3H4UFLH2YSIASHJNBFUCKC5YHGU44VCH2BGHN3WJQX6LG"
-    },
-    {
-      "address": "GA4PDUF3BLBSK47UTNY44AIZAP5EPHW2UIJRKB5HN76HHC55IWKSIHFD"
-    },
-    {
-      "string": "native"
-    }
-  ],
-  "valueJson": {
-    "map": [
-      {
-        "key": {
-          "symbol": "amount"
-        },
-        "val": {
-          "i128": "10000000"
-        }
-      },
-      {
-        "key": {
-          "symbol": "to_muxed_id"
-        },
-        "val": {
-          "u64": "123456789"
-        }
-      }
-    ]
-  }
-}
-```
-
-Para un ejemplo de código detallado, consulta la sección ‘_Monitoreo de Pagos \-\> Uso del Stellar RPC_’ de [los ejemplos de este repositorio](https://github.com/fazzatti/c-address-payment-examples#using-the-stellar-rpc).
-
-### Envío de pagos desde Cuentas de Contrato a un destinatario que requiere un memo
-
-Si un remitente está usando una Cuenta de Contrato y está enviando un [token SAC](../../../tokens/stellar-asset-contract.mdx) (como XLM, USDC, etc.) a un destinatario que requiere un memo (por ejemplo, un exchange), debe crear una dirección muxed que incluya la cuenta receptora (GBLVHX…) y la id de memo proporcionada en el campo de id muxed (123456789). En la interfaz de usuario, la dirección de memo resultante no necesita mostrarse al usuario, debe usarse directamente en la transacción.
-
-Si la parte receptora ya proporciona una dirección M, debe utilizarse directamente, sin necesitar un campo de memo. Como este es el valor proporcionado por el usuario, debe usarse en la transacción y mostrarse al usuario.
-
-## Envío de pagos a Cuentas de Contrato (de G a C)
-
-### Enviar un ‘transfer’ mediante Stellar RPC
-
-Este método es más sencillo pero requiere el uso de un RPC e implica un flujo de transacciones algo diferente al de una operación nativa tradicional. Para un ejemplo de código detallado, consulta la sección ‘_Enviando pagos a través del SAC \-\> Uso del Stellar RPC_’ de [los ejemplos de este repositorio](https://github.com/fazzatti/c-address-payment-examples#sending-payments-through-the-sac).
-
-**Ensambla la operación y la transacción**
-
-Para realizar un ‘transfer’ a través de un SAC, es necesario ensamblar una operación ‘_InvokeHostFunctionOp_’ con argumentos similares a una operación de ‘payment’, junto con el identificador del contrato y el nombre de la función objetivo (‘transfer’).
-
-Esto puede verse en detalle en la función ‘[assembleTransferOperation](https://github.com/fazzatti/c-address-payment-examples/blob/main/src/core/assemble-transfer-operation.ts)’ del demo. Aunque el ejemplo muestra este proceso con mayor detalle, es posible usar el [js-stellar-sdk](https://github.com/stellar/js-stellar-sdk) y su cliente de Contrato de manera más simple.
-
-Luego la transacción se desarrolla añadiendo esta operación y configurando los parámetros adicionales como en cualquier otra transacción ‘payment’.
-
-**Simular la transacción**
-
-Después de construir la transacción, se utiliza el método RPC ‘simulateTransaction’ para simular la ejecución de esta transacción contra el estado actual de la red, identificar si se espera que tenga éxito y, además, proporcionar varios parámetros adicionales sobre esta ejecución.
-
-Este proceso es completamente manejado por el SDK en un paso muy simple usando la función ‘_prepareTransaction_’ del cliente del servidor RPC. Automáticamente simula y proporciona un objeto de transacción actualizado. Consulta este proceso en detalle [en el demo](https://github.com/fazzatti/c-address-payment-examples/blob/0e1c021e5afbefd5946878d53934b62cf5a8bb68/src/core/rpc-transaction.ts#L43).
-
-**Firmar**
-
-Cuando la misma cuenta se usa como ‘remitente’ de los fondos y también como ‘origen’ de la transacción, el paso de la firma será exactamente el mismo. Una vez que se recibe el objeto de transacción actualizado del paso anterior, solo debes firmarlo con la cuenta fuente/remitente y estará listo.
-
-Cuando la cuenta ‘fuente’ de la transacción difiere de la cuenta ‘remitente’, será necesaria una entrada firmada adicional para autorizar explícitamente la invocación ‘transfer’. Consulta la [documentación del Marco de Autorización Soroban](../../../learn/fundamentals/contract-development/authorization.mdx#soroban-authorization-framework) para más detalles.
-
-**Enviar la transacción para procesamiento**
-
-Cuando una transacción se envía para procesamiento a través del RPC de Stellar, a diferencia de la API Horizon, se resolverá inmediatamente confirmando su envío pero no su procesamiento. Es necesario consultar el estado de la transacción periódicamente hasta obtener una confirmación de que fue procesada exitosamente o una actualización del estatus en caso de falla.
-
-### Envío de un ‘transfer’ vía API Horizon
-
-Al enviar un ‘transfer’ vía API Horizon, este método introduce algunos pasos adicionales en comparación con el uso de un RPC. Para un ejemplo de código detallado, consulta la sección ‘_Enviando pagos a través del SAC \-\> Uso de la API Horizon_’ de [los ejemplos de este repositorio](https://github.com/fazzatti/c-address-payment-examples#using-the-horizon-api-1).
-
-**Ensambla la operación y la transacción**
-
-Este proceso es casi el mismo que se describe en la sección anterior ‘[Enviar un ‘transfer’ mediante Stellar RPC](#sending-a-transfer-via-stellar-rpc)’ con algunas modificaciones menores. Dado que la API de Horizon **no** provee un endpoint para simular la ejecución de una transacción, esto significa que cuando se arma la transacción necesitamos asegurarnos también de que contiene:
-
-- Las **entradas de autorización Soroban** que cumplen con los requisitos de autorización de los contratos inteligentes.
-- El objeto **Soroban data**, que detalla la huella, los recursos y la tarifa de recursos esperada para esta invocación de contrato.
-
-Estos normalmente se completan automáticamente basados en la salida de la simulación y simplemente firmando y agregando las entradas de autorización generadas por el RPC. Aquí, necesitamos incluirlos manualmente.
-
-Las **entradas de autenticación** pueden predecirse y armarse fácilmente según la configuración. Asumiendo que la cuenta ‘remitente’ es la misma que la cuenta ‘fuente’ de la transacción, se necesita agregar una credencial de cuenta fuente a la operación, indicando que esta invocación usará la misma firma del sobre para autorizar el ‘transfer’. Consulta este proceso en detalle en la función [‘assembleSourceAuthEntry’](https://github.com/fazzatti/c-address-payment-examples/blob/main/src/core/assemble-source-auth.ts) del demo.
-
-Una vez que las entradas de autenticación están armadas y firmadas (cuando no son entradas ‘source-account’), deben incluirse en la operación, en el parámetro ‘auth’.
-
-Por otro lado, el proceso para el **Soroban Data** puede ser un poco más difícil de ejecutar manualmente. Considerando que todos los contratos SAC usan la misma implementación nativa, podemos esperar que todas las invocaciones ‘transfer’ sean muy similares.
-
-La cantidad de recursos consumidos no debería variar mucho salvo algunos casos excepcionales como transacciones que involucran entradas archivadas o una autorización personalizada para una billetera inteligente como remitente. Consulta este proceso de armado manual del Soroban Data en la función [’getSorobanData’](https://github.com/fazzatti/c-address-payment-examples/blob/main/src/core/get-sorobandata.ts) del demo.
-
-Una vez armado el **Soroban Data**, se incluye en el **Constructor de Transacciones**.
-
-**Firmar**
-
-Después de construir la transacción, asumiendo que las ‘entradas de autorización’ del paso anterior fueron configuradas correctamente, la transacción puede firmarse normalmente por la cuenta origen.
-
-**Enviar la transacción para procesamiento**
-
-Este paso es el mismo que cualquier transacción enviada a través de la API Horizon.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/send-and-receive-payments.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/send-and-receive-payments.mdx
deleted file mode 100644
index 788fe7a623..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/send-and-receive-payments.mdx
+++ /dev/null
@@ -1,1136 +0,0 @@
----
-title: Enviar y recibir pagos
-description: Aprende a enviar pagos y estar atento a los pagos recibidos en la red Stellar.
-sidebar_position: 7
----
-
-import Details from "@theme/Details";
-
-## Resumen de pagos
-
-Un pago constituye la transferencia de un token de una cuenta a otra. En la red Stellar, un token puede ser un activo Stellar o un token de contrato personalizado que sigue el [estándar de token SEP-41](../../../tokens/stellar-asset-contract.mdx#overview).
-
-Hay dos formas principales en que se realizan los pagos en Stellar:
-
-- Usando las [operaciones](../../../learn/fundamentals/transactions/list-of-operations.mdx) relacionadas con pagos de Stellar
-- [Invocando una función](../../../learn/fundamentals/contract-development/contract-interactions/overview.mdx) en un contrato de token.
-
-El enfoque que debes tomar depende del caso de uso:
-
-- Si deseas hacer un pago de un activo de Stellar entre dos cuentas Stellar, usa las operaciones de pago. Las tarifas de transacción son más económicas al usarlas comparado con las tarifas por invocar directamente el contrato de token del activo, conocido como el [Contrato de Activo Stellar](../../../tokens/stellar-asset-contract.mdx#overview).
-- Si quieres realizar un pago de un activo Stellar entre una cuenta Stellar y una dirección de contrato, o entre dos direcciones de contrato, entonces debe usarse el contrato del activo. Las operaciones de pago de Stellar no pueden tener direcciones de contrato como origen o destino.
-- Si deseas realizar un pago con un token de contrato personalizado que no sea un activo Stellar pero que siga el [estándar de token SEP-41](../../../tokens/stellar-asset-contract.mdx#overview), debes usar el contrato del token. Las operaciones de pago de Stellar solo se pueden usar para transferir activos Stellar.
-
-Para aprender más sobre las diferencias entre activos Stellar y tokens de contrato, consulta la descripción general de [Tokens](../../../tokens/README.mdx).
-
-:::info
-
-En los siguientes ejemplos de código, se omite la comprobación adecuada de errores por brevedad. Sin embargo, debes _siempre_ validar tus resultados, ya que hay muchas formas en que las solicitudes pueden fallar.
-
-:::
-
-## Ejemplo de uso de Pagos
-
-Este ejemplo destaca el enfoque mencionado para realizar pagos usando operaciones y activos, y el uso del [RPC de Stellar](../../../data/apis/rpc/README.mdx) con los [SDKs de cliente Stellar](../../../tools/sdks/client-sdks.mdx#overview) para ejecutar todas las acciones necesarias.
-
-### Enviar un Pago
-
-Demostramos un pago de un activo en Stellar. Construiremos una transacción con una operación de pago para enviar 10 Lummens desde una cuenta emisora a una cuenta receptora, la firmaremos como la cuenta emisora y la enviaremos a la red.
-
-- Enviando la transacción al nodo público de testnet mantenido por SDF del servidor Stellar RPC.
-- Al enviar transacciones al servidor RPC, es posible que no recibas una respuesta debido a las condiciones de la red.
-  - En tal situación, es imposible determinar el estado de tu transacción.
-  - Se recomienda siempre guardar una transacción (o la transacción codificada en formato XDR) en una variable o base de datos y reenviarla si no conoces su estado.
-  - La transacción en formato XDR serializado es idempotente, lo que significa que si la transacción ya fue aplicada con éxito al libro mayor, el RPC simplemente devolverá el resultado guardado y no intentará enviar la transacción de nuevo.
-  - Solo en los casos donde el estado de la transacción sea desconocido (y por lo tanto tenga posibilidad de ser incluida en un ledger) se producirá un reenvío a la red.
-
-<Details summary="Haz clic para ver el código de envío de pagos">
-<CodeExample>
-
-```js
-// send_payment.js
-// follow the https://github.com/stellar/js-stellar-sdk?tab=readme-ov-file#installation
-
-import * as StellarSdk from "@stellar/stellar-sdk";
-import fs from "fs";
-const rpcServer = new StellarSdk.rpc.Server(
-  "https://soroban-testnet.stellar.org",
-);
-
-async function sendPayments() {
-  const { Keypair } = StellarSdk;
-  const senderKeyPair = Keypair.random();
-  const recipientKeyPair = Keypair.random();
-  let senderAccount;
-
-  try {
-    // Request airdrop for the sender account - this creates, funds and returns the Account object
-    senderAccount = await rpcServer.requestAirdrop(senderKeyPair.publicKey());
-    console.log("Sender Account funded with airdrop");
-    console.log("Sender Account ID:", senderAccount.accountId());
-    console.log("Sender Sequence number:", senderAccount.sequence.toString());
-
-    // Note - this persistence of sender id to a file on file system is only done for demo purposes.
-    // It shares the created sender account with the payment monitor example which will run next.
-    // Since this example is using file system it therefore is intended to run only on Node.
-    // In a real application the stellar js sdk can be used in browser or Node.
-    fs.writeFileSync("sender_public.key", senderAccount.accountId());
-
-    console.log("\n\n");
-
-    await rpcServer.requestAirdrop(recipientKeyPair.publicKey());
-    console.log("Recipient Account funded with airdrop");
-    console.log("Recipient Account ID:", recipientKeyPair.publicKey());
-  } catch (err) {
-    console.error("Airdrop / Account loading failed:", err);
-    return;
-  }
-
-  // Now call sendPayment with the funded account, in a loop of once every 30 seconds
-  while (true) {
-    console.log("\n\nSending payment...");
-    await sendPayment(
-      senderKeyPair,
-      senderAccount,
-      recipientKeyPair.publicKey(),
-    );
-    await new Promise((resolve) => setTimeout(resolve, 30000)); // wait for 30 seconds
-  }
-}
-
-async function sendPayment(sender, senderAccount, recipient) {
-  // The next step is to parametrize and build the transaction object:
-  // Using the source account we just loaded we begin to assemble the transaction.
-  // We set the fee to the base fee, which is 100 stroops (0.00001 XLM).
-  // We also set the network passphrase to TESTNET.
-  const transaction = new StellarSdk.TransactionBuilder(senderAccount, {
-    fee: StellarSdk.BASE_FEE,
-    networkPassphrase: StellarSdk.Networks.TESTNET,
-  })
-    // We then add a payment operation to the transaction oject.
-    // This operation will send 10 XLM to the destination account.
-    // Obs.: Not specifying a explicit source account here means that the
-    // operation will use the source account of the whole transaction, which we specified above.
-    .addOperation(
-      StellarSdk.Operation.payment({
-        destination: recipient,
-        asset: StellarSdk.Asset.native(),
-        amount: "10",
-      }),
-    )
-    // We include an optional memo which oftentimes is used to identify the transaction
-    // when working with pooled accounts or to facilitate reconciliation.
-    .addMemo(StellarSdk.Memo.id("1234567890"))
-    // Finally, we set a timeout for the transaction.
-    // This means that the transaction will not be valid anymore after 180 seconds.
-    .setTimeout(180)
-    .build();
-
-  // We sign the transaction with the source account's secret key.
-  transaction.sign(sender);
-
-  // Now we can send the transaction to the network.
-  // The sendTransaction method immediately returns a reply with the transaction hash
-  // and the status "PENDING". This means the transaction was received and is being processed.
-  const sendTransactionResponse = await rpcServer.sendTransaction(transaction);
-
-  // Here we check the status of the transaction as there are
-  // a possible outcomes after sending a transaction that would have
-  // to be handled accordingly, such as "DUPLICATE" or "TRY_AGAIN_LATER".
-  if (sendTransactionResponse.status !== "PENDING") {
-    throw new Error(
-      `Failed to send transaction, status: ${sendTransactionResponse.status}`,
-    );
-  }
-
-  console.log(
-    "Payment Transaction submitted, hash:",
-    sendTransactionResponse.hash,
-  );
-
-  // Here we poll the transaction status to await for its final result.
-  // We can use the transaction hash to poll the transaction status later.
-  const finalStatus = await rpcServer.pollTransaction(
-    sendTransactionResponse.hash,
-  );
-
-  // The pollTransaction method will return the final status of the transaction
-  // after the specified number of attempts or when the transaction is finalized.
-  // We then check the final status of the transaction and handle it accordingly.
-  switch (finalStatus.status) {
-    case StellarSdk.rpc.Api.GetTransactionStatus.FAILED:
-      console.error("Transaction failed, status:", finalStatus.status);
-      if (finalStatus.resultXdr) {
-        console.error(
-          "Transaction Result XDR (decoded):",
-          JSON.stringify(finalStatus.resultXdr, null, 2),
-        );
-      }
-
-      throw new Error(`Transaction failed with status: ${finalStatus.status}`);
-    case StellarSdk.rpc.Api.GetTransactionStatus.NOT_FOUND:
-      throw new Error(`Transaction failed with status: ${finalStatus.status}`);
-    case StellarSdk.rpc.Api.GetTransactionStatus.SUCCESS:
-      console.log("Success! Committed on Ledger:", finalStatus.ledger);
-      break;
-  }
-}
-
-sendPayments().catch((error) => {
-  console.error("Error executing sendPayments function:", error);
-  process.exit(1);
-});
-```
-
-```java
-// SendPaymentExample.java
-// Java 17, Stellar Java SDK (lightsail-network/java-stellar-sdk)
-
-import org.stellar.sdk.Account;
-import org.stellar.sdk.AssetTypeNative;
-import org.stellar.sdk.KeyPair;
-import org.stellar.sdk.MemoId;
-import org.stellar.sdk.Network;
-import org.stellar.sdk.SorobanServer;
-import org.stellar.sdk.Transaction;
-import org.stellar.sdk.TransactionBuilder;
-import org.stellar.sdk.operations.PaymentOperation;
-import org.stellar.sdk.responses.sorobanrpc.GetTransactionResponse;
-import org.stellar.sdk.responses.sorobanrpc.GetTransactionResponse.GetTransactionStatus;
-import org.stellar.sdk.responses.sorobanrpc.SendTransactionResponse.SendTransactionStatus;
-
-import okhttp3.OkHttpClient;
-import okhttp3.Request;
-import okhttp3.Response;
-
-import java.math.BigDecimal;
-import java.net.URLEncoder;
-import java.nio.charset.StandardCharsets;
-import java.nio.file.Files;
-import java.nio.file.Paths;
-import java.nio.file.StandardOpenOption;
-
-public class SendPaymentJavaExample {
-  public static void main(String[] args) throws Exception {
-    final String RPC_URL = "https://soroban-testnet.stellar.org";
-    SorobanServer rpc = new SorobanServer(RPC_URL);
-
-    // Generate sender/recipient and fund via Friendbot (testnet)
-    // get the friendbot url from rpc info
-    var info = rpc.getNetwork();
-    System.out.println("Friendbot URL: " + info.getFriendbotUrl());
-
-    KeyPair sender = KeyPair.random();
-    KeyPair recipient = KeyPair.random();
-    friendbotFund(sender.getAccountId(), info.getFriendbotUrl());
-    friendbotFund(recipient.getAccountId(), info.getFriendbotUrl());
-    Files.writeString(Paths.get("sender_public.key"),
-        sender.getAccountId(),
-        StandardOpenOption.CREATE,
-        StandardOpenOption.TRUNCATE_EXISTING,
-        StandardOpenOption.WRITE);
-
-    // Load sender sequence using RPC getLedgerEntries
-    Account source = new Account(sender.getAccountId(), rpc.getAccount(sender.getAccountId()).getSequenceNumber());
-
-    // do this in a loop, send payment once every 30 seconds
-    while (true) {
-      // Build classic payment: 10 XLM, memo id, 180s timeout
-      Transaction tx = new TransactionBuilder(source, Network.TESTNET)
-          .setBaseFee(Transaction.MIN_BASE_FEE)
-          .addOperation(PaymentOperation.builder().destination(recipient.getAccountId()).asset(new AssetTypeNative())
-              .amount(new BigDecimal("10")).build())
-          .addMemo(new MemoId(1234567890L))
-          .setTimeout(180)
-          .build();
-
-      tx.sign(sender);
-
-      // Submit via RPC
-      var sendResp = rpc.sendTransaction(tx);
-      if (!SendTransactionStatus.PENDING.equals(sendResp.getStatus())) {
-        throw new RuntimeException("Failed to send transaction, status: " + sendResp.getStatus());
-      }
-      System.out.println("Submitted. Hash: " + sendResp.getHash());
-
-      // Poll final status (throws on FAILED/NOT_FOUND)
-      var finalResp = pollTransaction(rpc, sendResp.getHash());
-      System.out.println("Success! Committed on ledger: " + finalResp.getLedger());
-      Thread.sleep(30000L); // wait 30s
-    }
-  }
-
-  // Fund account with Friendbot (testnet)
-  static void friendbotFund(String accountId, String friendbotUrl) throws Exception {
-    OkHttpClient http = new OkHttpClient.Builder().build();
-    String url = friendbotUrl + "?addr=" + URLEncoder.encode(accountId, StandardCharsets.UTF_8);
-
-    Request req = new Request.Builder().url(url).build();
-    Response res = http.newCall(req).execute();
-
-    if (res.code() != 200) {
-      throw new RuntimeException("Friendbot funding failed: " + res.code() + " " + res.body().string());
-    }
-    System.out.println("Funded: " + accountId);
-  }
-
-  // Helper: wrap SorobanServer.pollTransaction and enforce failure handling
-  static GetTransactionResponse pollTransaction(SorobanServer rpc, String txHash) throws Exception {
-    GetTransactionResponse resp = rpc.pollTransaction(txHash);
-
-    if (GetTransactionStatus.SUCCESS.equals(resp.getStatus())) {
-      return resp;
-    }
-    if (GetTransactionStatus.FAILED.equals(resp.getStatus())) {
-      if (resp.getResultXdr() != null) {
-        System.err.println("Failed TX, Result XDR (base64): " + resp.getResultXdr());
-      }
-      throw new RuntimeException("Transaction failed.");
-    }
-    if (GetTransactionStatus.NOT_FOUND.equals(resp.getStatus())) {
-      throw new RuntimeException("Transaction not found.");
-    }
-    throw new RuntimeException("Unexpected status: " + resp.getStatus());
-  }
-}
-
-```
-
-```go
-// sender.go
-package main
-
-import (
-	"context"
-	"crypto/tls"
-	"fmt"
-	"net/http"
-	"net/url"
-	"os"
-	"strings"
-	"time"
-
-	"github.com/stellar/go-stellar-sdk/keypair"
-	"github.com/stellar/go-stellar-sdk/network"
-	"github.com/stellar/go-stellar-sdk/txnbuild"
-	sdk "github.com/stellar/stellar-rpc/client"
-	"github.com/stellar/stellar-rpc/protocol"
-)
-
-// friendbotFund funds an account using the Stellar testnet friendbot
-func friendbotFund(accountID, friendbotURL string) error {
-	// Construct the URL with account parameter
-	fullURL := friendbotURL + "?addr=" + url.QueryEscape(accountID)
-
-	// Make HTTP GET request
-	resp, err := http.Get(fullURL)
-	if err != nil {
-		return fmt.Errorf("failed to make friendbot request: %v", err)
-	}
-	defer resp.Body.Close()
-
-	// Check if response is successful (2xx status code)
-	if resp.StatusCode/100 != 2 {
-		return fmt.Errorf("friendbot funding failed: %d", resp.StatusCode)
-	}
-
-	fmt.Printf("Funded: %s\n", accountID)
-	return nil
-}
-
-// check panics if there's an error
-func check(err error) {
-	if err != nil {
-		panic(err)
-	}
-}
-
-// SignAndSend builds, signs, and submits a transaction with the given operations
-func SignAndSend(
-	ctx context.Context,
-	client *sdk.Client,
-	account txnbuild.Account,
-	signers []*keypair.Full,
-	operations ...txnbuild.Operation,
-) protocol.GetTransactionResponse {
-	// Build, sign, and submit the transaction
-	tx, err := txnbuild.NewTransaction(
-		txnbuild.TransactionParams{
-			SourceAccount:        account,
-			IncrementSequenceNum: true,
-			BaseFee:              txnbuild.MinBaseFee,
-			Preconditions: txnbuild.Preconditions{
-				TimeBounds: txnbuild.NewInfiniteTimeout(),
-			},
-			Operations: operations,
-		},
-	)
-	check(err)
-
-	for _, signer := range signers {
-		tx, err = tx.Sign(network.TestNetworkPassphrase, signer)
-		check(err)
-	}
-
-	txnB64, err := tx.Base64()
-	check(err)
-
-	txSendResp, err := client.SendTransaction(ctx,
-		protocol.SendTransactionRequest{Transaction: txnB64})
-	check(err)
-
-	for i := range 5 {
-		txResp, err := client.GetTransaction(ctx,
-			protocol.GetTransactionRequest{Hash: txSendResp.Hash})
-		check(err)
-
-		switch txResp.Status {
-		case "NOT_FOUND":
-		case "SUCCESS":
-			return txResp
-		case "FAILED":
-			panic(fmt.Errorf("transaction failed: %s",
-				strings.Join(txResp.DiagnosticEventsXDR, "\n")))
-		}
-
-		// Increase delay for each polling request
-		time.Sleep(time.Duration(i) * time.Second)
-	}
-
-	panic(fmt.Errorf("transaction never found: %s", txSendResp.Hash))
-}
-
-// sendPayment creates and submits a payment transaction using the helper function
-func sendPayment(ctx context.Context, rpcClient *sdk.Client, sourceAccount txnbuild.Account, signerKP *keypair.Full, destinationAddr string) error {
-	// Create payment operation
-	paymentOp := txnbuild.Payment{
-		Destination: destinationAddr,
-		Amount:      "10",
-		Asset:       txnbuild.NativeAsset{},
-	}
-
-	// Use the helper function to build, sign, and submit
-	fmt.Printf("Submitting payment of 10 XLM to %s...\n", destinationAddr)
-
-	txResp := SignAndSend(ctx, rpcClient, sourceAccount, []*keypair.Full{signerKP}, &paymentOp)
-
-	fmt.Printf("Success! Committed on ledger: %d\n", txResp.Ledger)
-	return nil
-}
-
-func main() {
-	const RPC_URL = "https://soroban-testnet.stellar.org"
-
-	rpcClient := sdk.NewClient(RPC_URL, nil)
-
-	// Get network info to obtain friendbot URL
-	ctx := context.Background()
-	networkInfo, err := rpcClient.GetNetwork(ctx)
-	if err != nil {
-		panic(fmt.Sprintf("Failed to get network info: %v", err))
-	}
-
-	fmt.Printf("Friendbot URL: %s\n", networkInfo.FriendbotURL)
-
-	// Generate sender and recipient keypairs
-	sender, err := keypair.Random()
-	if err != nil {
-		panic(fmt.Sprintf("Failed to generate sender keypair: %v", err))
-	}
-
-	recipient, err := keypair.Random()
-	if err != nil {
-		panic(fmt.Sprintf("Failed to generate recipient keypair: %v", err))
-	}
-
-	// Fund accounts via friendbot
-	err = friendbotFund(sender.Address(), networkInfo.FriendbotURL)
-	if err != nil {
-		panic(fmt.Sprintf("Failed to fund sender: %v", err))
-	}
-
-	err = friendbotFund(recipient.Address(), networkInfo.FriendbotURL)
-	if err != nil {
-		panic(fmt.Sprintf("Failed to fund recipient: %v", err))
-	}
-
-	// Save sender public key to file
-	err = os.WriteFile("sender_public.key", []byte(sender.Address()), 0644)
-	if err != nil {
-		panic(fmt.Sprintf("Failed to write sender public key: %v", err))
-	}
-
-	// Load sender account info
-	senderAccount, err := rpcClient.LoadAccount(ctx, sender.Address())
-	if err != nil {
-		panic(fmt.Sprintf("Failed to get sender account: %v", err))
-	}
-
-	// Payment loop - send payment every 30 seconds
-	for {
-		err := sendPayment(ctx, rpcClient, senderAccount, sender, recipient.Address())
-		if err != nil {
-			panic(fmt.Sprintf("Payment failed: %v", err))
-		}
-
-		fmt.Println("Waiting 30 seconds before next payment...")
-		time.Sleep(30 * time.Second)
-
-		// Reload account to get updated sequence number
-		senderAccount, err = rpcClient.LoadAccount(ctx, sender.Address())
-		if err != nil {
-			panic(fmt.Sprintf("Failed to reload sender account: %v", err))
-		}
-	}
-}
-```
-
-</CodeExample>
-</Details>
-
-### Monitoreo de pagos como flujo de eventos
-
-Aprovecha el último [Protocolo 23 (Whisk)](https://stellar.org/blog/developers/introducing-whisk-stellar-protocol-23) para capturar la actividad de pagos como eventos puros. Estos eventos pueden ser monitoreados eficazmente usando el método `getEvents` del servidor RPC, que proporciona filtrado del lado del servidor y detección en tiempo real de pagos.
-
-El enfoque RPC ofrece varias ventajas:
-
-- **Filtrado de temas de evento del lado del servidor**: filtra eventos específicos usando patrones de temas
-- **Sondeo eficiente**: usa cursores y paginación para procesamiento confiable de eventos
-- **Modelo de eventos unificado**: soporta [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md), todos los movimientos de activos en la red se emiten como eventos con nombres de temas estandarizados para indicar el tipo de movimiento (p. ej., "transfer" para pagos)
-- **Mejor manejo de errores**: el sondeo HTTP sin estado en RPC es más resistente que protocolos de streaming persistentes como SSE o WebSockets
-
-Demuestra monitoreo casi en tiempo real de transacciones de la red Stellar estableciendo un listener asíncrono para consumir eventos desde RPC y filtrarlos por tema solo para los pagos de ejemplo generados por nuestro script anterior.
-
-<Details summary="Haz clic para ver el código de monitoreo de pagos">
-<CodeExample>
-
-```js
-// monitor_payment.js
-// follow the https://github.com/stellar/js-stellar-sdk?tab=readme-ov-file#installation
-
-import * as StellarSdk from "@stellar/stellar-sdk";
-import fs from "fs";
-
-async function monitorPayments() {
-  // Initialize RPC server for testnet
-  const rpcServer = new StellarSdk.rpc.Server(
-    "https://soroban-testnet.stellar.org",
-  );
-
-  // One-time initialization - everything encapsulated here
-  const monitoredFromAccount = fs
-    .readFileSync("sender_public.key", "utf-8")
-    .trim();
-
-  // create our payment event topic filter values
-  const transferTopicFilter =
-    StellarSdk.xdr.ScVal.scvSymbol("transfer").toXDR("base64");
-  const fromTopicFilter = StellarSdk.nativeToScVal(monitoredFromAccount, {
-    type: "address",
-  }).toXDR("base64");
-
-  // Get starting ledger
-  const latestLedger = await rpcServer.getLatestLedger();
-  console.log(
-    `Starting payment monitoring from ledger ${latestLedger.sequence} and from account ${monitoredFromAccount}`,
-  );
-  let currentStartLedger = latestLedger.sequence;
-  let currentCursor;
-
-  while (true) {
-    // Query for payments from our monitored account
-    const eventsResponse = await rpcServer.getEvents({
-      startLedger: currentStartLedger,
-      cursor: currentCursor,
-      filters: [
-        {
-          type: "contract",
-          topics: [
-            [
-              transferTopicFilter,
-              fromTopicFilter,
-              "**", // filter will match on any 'to' address and any token(SAC or SEP-41)
-            ],
-          ],
-        },
-      ],
-      limit: 10,
-    });
-
-    // Process any events found
-    console.log(`Found ${eventsResponse.events.length} payment(s):`);
-
-    for (const event of eventsResponse.events) {
-      console.log("\n--- Payment Received ---");
-      console.log(`Ledger: ${event.ledger}`);
-      console.log(`Transaction Hash: ${event.txHash}`);
-      console.log(`Closed At: ${event.ledgerClosedAt}`);
-
-      // Decode addresses from topics
-      try {
-        const fromAddress = StellarSdk.scValToNative(event.topic[1]);
-        const toAddress = StellarSdk.scValToNative(event.topic[2]);
-        console.log(`Transfer: ${fromAddress} → ${toAddress}`);
-      } catch (error) {
-        console.log(`From/To: Unable to decode addresses`, error);
-        continue;
-      }
-
-      // Decode transfer amount from the event data
-      try {
-        // Protocol 23+ unified events model per CAP-0067
-        // https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md
-        // Event value field is scMap with {amount: i128, to_muxed_id: u64|bytes|string} (when muxed info present)
-        const amount = StellarSdk.scValToNative(event.value)["amount"];
-        console.log(
-          `Amount: ${amount.toString()} stroops (${(Number(amount) / 10000000).toFixed(7)} XLM)`,
-        );
-      } catch (error) {
-        console.log(`Failed to decode transfer amount:`, error);
-      }
-      // Decode asset from topics[3], this is only present in events from SAC tokens
-      if (event.topic.length > 3) {
-        const asset = StellarSdk.scValToNative(event.topic[3]);
-        console.log(`Asset: ${asset}`);
-      }
-    }
-
-    // Update cursor to drive next query
-    currentCursor = eventsResponse.cursor;
-    currentStartLedger = null;
-
-    // Wait 5 seconds before next iteration
-    await new Promise((resolve) => setTimeout(resolve, 5000));
-  }
-}
-
-// Start the application
-monitorPayments().catch((error) => {
-  console.error("Failed during payment monitoring:", error);
-});
-```
-
-```java
-// MonitorPaymentExample.java
-// Java 17, Stellar Java SDK (lightsail-network/java-stellar-sdk)
-
-import org.stellar.sdk.SorobanServer;
-import org.stellar.sdk.responses.sorobanrpc.GetLatestLedgerResponse;
-
-import org.stellar.sdk.requests.sorobanrpc.EventFilterType;
-import org.stellar.sdk.requests.sorobanrpc.GetEventsRequest;
-import org.stellar.sdk.scval.Scv;
-import org.stellar.sdk.xdr.SCSymbol;
-import org.stellar.sdk.xdr.SCVal;
-
-import java.math.BigDecimal;
-import java.nio.charset.StandardCharsets;
-import java.nio.file.Files;
-import java.nio.file.Paths;
-import java.util.Arrays;
-import java.util.List;
-import java.util.Map;
-
-public class MonitorPaymentsJavaExample {
-  public static void main(String[] args) throws Exception {
-    final String RPC_URL = "https://soroban-testnet.stellar.org";
-    SorobanServer rpc = new SorobanServer(RPC_URL);
-
-    // Load the account we monitor payments FROM (written by send_payment example)
-    String monitoredFromAccount = Files.readString(Paths.get("sender_public.key"), StandardCharsets.UTF_8).trim();
-
-    // Build topic filters using SDK helpers (base64 XDR via toXdrBase64())
-    String transferTopicFilter = Scv.toSymbol("transfer").toXdrBase64();
-    String fromTopicFilter = Scv.toAddress(monitoredFromAccount).toXdrBase64();
-
-    // Starting point: latest ledger
-    GetLatestLedgerResponse latest = rpc.getLatestLedger();
-    Long startLedger = latest.getSequence().longValue();
-    String cursor = null;
-    System.out.printf("Starting payment monitoring from ledger %d and from account %s%n", startLedger,
-        monitoredFromAccount);
-
-    while (true) {
-      // filter will match on any 'to' address and any token(SAC or SEP-41)
-      GetEventsRequest.EventFilter eventFilter = GetEventsRequest.EventFilter.builder()
-          .type(EventFilterType.CONTRACT)
-          .topic(Arrays.asList(transferTopicFilter, fromTopicFilter, "**"))
-          .build();
-      GetEventsRequest.PaginationOptions paginationOptions = GetEventsRequest.PaginationOptions.builder()
-          .limit(10L)
-          .cursor(cursor)
-          .build();
-      GetEventsRequest getEventsRequest = GetEventsRequest.builder()
-          .startLedger(startLedger)
-          .filter(eventFilter)
-          .pagination(paginationOptions)
-          .build();
-
-      var eventsResp = rpc.getEvents(getEventsRequest);
-      var events = eventsResp.getEvents();
-      System.out.println("Found " + events.size() + " payment(s):");
-
-      for (var ev : events) {
-        System.out.println("\n--- Payment Received ---");
-        System.out.println("Ledger: " + ev.getLedger());
-        System.out.println("Transaction Hash: " + ev.getTransactionHash());
-        System.out.println("Closed At: " + ev.getLedgerClosedAt());
-
-        List<String> topics = ev.getTopic();
-        if (topics.size() < 3) {
-          System.out.println("Invalid event, not enough topics.");
-          continue;
-        }
-
-        try {
-          String fromAddr = Scv.fromAddress(SCVal.fromXdrBase64(topics.get(1))).toString();
-          String toAddr = Scv.fromAddress(SCVal.fromXdrBase64(topics.get(2))).toString();
-          System.out.println("Transfer: " + fromAddr + " → " + toAddr);
-        } catch (Exception e) {
-          System.out.println("From/To: Unable to decode addresses: " + e.getMessage());
-        }
-
-        try {
-          // the event value is a map with key of Symbol for 'amount' to i128 value
-          Map<SCVal, SCVal> map = Scv.fromMap(SCVal.fromXdrBase64(ev.getValue()));
-          SCVal amount = map.get(Scv.toSymbol("amount"));
-
-          if (amount != null) {
-            String amountStr = Scv.fromInt128(amount).toString();
-            BigDecimal raw = new BigDecimal(amountStr);
-            System.out.printf("Token Amount Transferred: (%.7f)%n", raw.scaleByPowerOfTen(-7));
-          }
-        } catch (Exception e) {
-          System.out.println("Failed to decode transfer amount: " + e.getMessage());
-        }
-
-        try {
-          if (topics.size() > 3) {
-            // Decode asset from topics[3], this is only present in events from SAC tokens
-            System.out.println("Asset: " + new String(Scv.fromString(SCVal.fromXdrBase64(topics.get(3)))));
-          }
-        } catch (Exception ex) {
-          System.out.println("Asset: Unable to decode asset" + ex.getMessage());
-        }
-      }
-
-      // pagination: update cursor and clear startLedger for subsequent calls
-      cursor = eventsResp.getCursor();
-      startLedger = null;
-      Thread.sleep(5000L);
-    }
-  }
-}
-```
-
-```go
-// monitor.go
-package main
-
-import (
-	"context"
-	"crypto/tls"
-	"encoding/base64"
-	"fmt"
-	"net/http"
-	"os"
-	"strings"
-	"time"
-
-	"github.com/stellar/go-stellar-sdk/strkey"
-	"github.com/stellar/go-stellar-sdk/xdr"
-	sdk "github.com/stellar/stellar-rpc/client"
-	"github.com/stellar/stellar-rpc/protocol"
-)
-
-func main() {
-	const RPC_URL = "https://soroban-testnet.stellar.org"
-
-	rpcClient := sdk.NewClient(RPC_URL, nil)
-	ctx := context.Background()
-
-	// Load the account we monitor payments FROM (written by send_payment example)
-	senderKeyBytes, err := os.ReadFile("sender_public.key")
-	if err != nil {
-		panic(fmt.Sprintf("Failed to read sender_public.key: %v", err))
-	}
-	monitoredFromAccount := strings.TrimSpace(string(senderKeyBytes))
-
-	fmt.Printf("Starting payment monitoring from account: %s\n", monitoredFromAccount)
-
-	// Get latest ledger as starting point
-	latestLedger, err := rpcClient.GetLatestLedger(ctx)
-	if err != nil {
-		panic(fmt.Sprintf("Failed to get latest ledger: %v", err))
-	}
-
-	startLedger := latestLedger.Sequence
-	var cursor string
-
-	fmt.Printf("Starting payment monitoring from ledger %d\n", startLedger)
-
-	for {
-		err := monitorPayments(ctx, rpcClient, monitoredFromAccount, &startLedger, &cursor)
-		if err != nil {
-			fmt.Printf("Error monitoring payments: %v\n", err)
-		}
-
-		time.Sleep(5 * time.Second)
-	}
-}
-
-func monitorPayments(ctx context.Context, client *sdk.Client, fromAccount string, startLedger *uint32, cursor *string) error {
-	// Create a simple event filter for contract events
-	eventFilter := protocol.EventFilter{
-		EventType: protocol.EventTypeSet{protocol.EventTypeContract: nil},
-		// We'll filter by topics in the processing logic instead
-	}
-
-	// Create request
-	request := protocol.GetEventsRequest{
-		Filters: []protocol.EventFilter{eventFilter},
-	}
-
-	// Set startLedger only on first call
-	if *startLedger != 0 {
-		request.StartLedger = *startLedger
-	}
-
-	// Set cursor for pagination
-	if *cursor != "" {
-		parsedCursor, err := protocol.ParseCursor(*cursor)
-		if err != nil {
-			return fmt.Errorf("failed to parse cursor: %v", err)
-		}
-		request.Pagination = &protocol.PaginationOptions{
-			Cursor: &parsedCursor,
-			Limit:  10,
-		}
-	} else {
-		request.Pagination = &protocol.PaginationOptions{
-			Limit: 10,
-		}
-	}
-
-	// Get events
-	eventsResp, err := client.GetEvents(ctx, request)
-	if err != nil {
-		return fmt.Errorf("failed to get events: %v", err)
-	}
-
-	// Filter events that match our criteria
-	relevantEvents := []protocol.EventInfo{}
-	for _, event := range eventsResp.Events {
-		if isPaymentEvent(event, fromAccount) {
-			relevantEvents = append(relevantEvents, event)
-		}
-	}
-
-	fmt.Printf("Found %d payment(s):\n", len(relevantEvents))
-
-	// Process relevant events
-	for _, event := range relevantEvents {
-		err := processPaymentEvent(event)
-		if err != nil {
-			fmt.Printf("Error processing event: %v\n", err)
-			continue
-		}
-	}
-
-	// Update pagination
-	*cursor = eventsResp.Cursor
-	*startLedger = 0 // Clear start ledger for subsequent calls
-
-	return nil
-}
-
-func isPaymentEvent(event protocol.EventInfo, fromAccount string) bool {
-	// Check if this is a transfer event by looking at the first topic
-	if len(event.TopicXDR) < 2 {
-		return false
-	}
-
-	// Try to decode the first topic to see if it's "transfer"
-	if isTransferTopic(event.TopicXDR[0]) && isFromAccount(event.TopicXDR[1], fromAccount) {
-		return true
-	}
-
-	return false
-}
-
-func isTransferTopic(topicXDR string) bool {
-	xdrBytes, err := base64.StdEncoding.DecodeString(topicXDR)
-	if err != nil {
-		return false
-	}
-
-	var scVal xdr.ScVal
-	err = scVal.UnmarshalBinary(xdrBytes)
-	if err != nil {
-		return false
-	}
-
-	return scVal.Type == xdr.ScValTypeScvSymbol &&
-		scVal.Sym != nil &&
-		string(*scVal.Sym) == "transfer"
-}
-
-func isFromAccount(topicXDR, expectedAccount string) bool {
-	decodedAddr, err := decodeAddressFromXDR(topicXDR)
-	return err == nil && decodedAddr == expectedAccount
-}
-
-func createTransferTopicFilter() (string, error) {
-	// Create "transfer" symbol and encode to base64 XDR
-	symbol := xdr.ScSymbol("transfer")
-	scVal := xdr.ScVal{
-		Type: xdr.ScValTypeScvSymbol,
-		Sym:  &symbol,
-	}
-
-	// Use XDR marshaling to base64
-	xdrBytes, err := scVal.MarshalBinary()
-	if err != nil {
-		return "", err
-	}
-
-	return base64.StdEncoding.EncodeToString(xdrBytes), nil
-}
-
-func createAddressTopicFilter(accountID string) (string, error) {
-	// Convert address string to AccountId
-	accountKey, err := xdr.AddressToAccountId(accountID)
-	if err != nil {
-		return "", err
-	}
-
-	// Create SCAddress for account
-	scAddr := xdr.ScAddress{
-		Type:      xdr.ScAddressTypeScAddressTypeAccount,
-		AccountId: &accountKey,
-	}
-
-	scVal := xdr.ScVal{
-		Type:    xdr.ScValTypeScvAddress,
-		Address: &scAddr,
-	}
-
-	// Use XDR marshaling to base64
-	xdrBytes, err := scVal.MarshalBinary()
-	if err != nil {
-		return "", err
-	}
-
-	return base64.StdEncoding.EncodeToString(xdrBytes), nil
-}
-
-func processPaymentEvent(event protocol.EventInfo) error {
-	fmt.Println("\n--- Payment Received ---")
-	fmt.Printf("Ledger: %d\n", event.Ledger)
-	fmt.Printf("Transaction Hash: %s\n", event.TransactionHash)
-	fmt.Printf("Closed At: %s\n", event.LedgerClosedAt)
-
-	// Parse topics
-	if len(event.TopicXDR) < 3 {
-		fmt.Println("Invalid event, not enough topics.")
-		return nil
-	}
-
-	// Decode from and to addresses
-	fromAddr, err := decodeAddressFromXDR(event.TopicXDR[1])
-	if err != nil {
-		fmt.Printf("From/To: Unable to decode from address: %v\n", err)
-	} else {
-		toAddr, err := decodeAddressFromXDR(event.TopicXDR[2])
-		if err != nil {
-			fmt.Printf("From/To: Unable to decode to address: %v\n", err)
-		} else {
-			fmt.Printf("Transfer: %s → %s\n", fromAddr, toAddr)
-		}
-	}
-
-	// Decode amount from event value
-	if event.ValueXDR != "" {
-		amount, err := decodeAmountFromXDR(event.ValueXDR)
-		if err != nil {
-			fmt.Printf("Failed to decode transfer amount: %v\n", err)
-		} else {
-			fmt.Printf("Token Amount Transferred: %.7f\n", float64(amount)/10000000) // Scale by 10^7
-		}
-	}
-
-	// Decode asset if available
-	if len(event.TopicXDR) > 3 {
-		asset, err := decodeAssetFromXDR(event.TopicXDR[3])
-		if err != nil {
-			fmt.Printf("Asset: Unable to decode asset: %v\n", err)
-		} else {
-			fmt.Printf("Asset: %s\n", asset)
-		}
-	}
-
-	return nil
-}
-
-func decodeAddressFromXDR(base64XDR string) (string, error) {
-	xdrBytes, err := base64.StdEncoding.DecodeString(base64XDR)
-	if err != nil {
-		return "", err
-	}
-
-	var scVal xdr.ScVal
-	err = scVal.UnmarshalBinary(xdrBytes)
-	if err != nil {
-		return "", err
-	}
-
-	if scVal.Type != xdr.ScValTypeScvAddress || scVal.Address == nil {
-		return "", fmt.Errorf("not an address type")
-	}
-
-	switch scVal.Address.Type {
-	case xdr.ScAddressTypeScAddressTypeAccount:
-		if scVal.Address.AccountId == nil {
-			return "", fmt.Errorf("account ID is nil")
-		}
-		return scVal.Address.AccountId.Address(), nil
-	case xdr.ScAddressTypeScAddressTypeContract:
-		if scVal.Address.ContractId == nil {
-			return "", fmt.Errorf("contract ID is nil")
-		}
-		return strkey.MustEncode(strkey.VersionByteContract, scVal.Address.ContractId[:]), nil
-	default:
-		return "", fmt.Errorf("unknown address type")
-	}
-}
-
-func decodeAmountFromXDR(base64XDR string) (int64, error) {
-	xdrBytes, err := base64.StdEncoding.DecodeString(base64XDR)
-	if err != nil {
-		return 0, err
-	}
-
-	var scVal xdr.ScVal
-	err = scVal.UnmarshalBinary(xdrBytes)
-	if err != nil {
-		return 0, err
-	}
-
-	// The value should be a map containing an "amount" key
-	if scVal.Type != xdr.ScValTypeScvMap || scVal.Map == nil {
-		return 0, fmt.Errorf("value is not a map")
-	}
-
-	// Look for the "amount" key in the map
-	for _, pair := range **scVal.Map {
-		if pair.Key.Type == xdr.ScValTypeScvSymbol && pair.Key.Sym != nil && string(*pair.Key.Sym) == "amount" {
-			// Found the amount key, extract the value
-			if pair.Val.Type == xdr.ScValTypeScvI128 && pair.Val.I128 != nil {
-				// Convert I128 to int64 (simplified - just use the low part for now)
-				return int64(pair.Val.I128.Lo), nil
-			}
-		}
-	}
-
-	return 0, fmt.Errorf("amount not found in map")
-}
-
-func decodeAssetFromXDR(base64XDR string) (string, error) {
-	xdrBytes, err := base64.StdEncoding.DecodeString(base64XDR)
-	if err != nil {
-		return "", err
-	}
-
-	var scVal xdr.ScVal
-	err = scVal.UnmarshalBinary(xdrBytes)
-	if err != nil {
-		return "", err
-	}
-
-	if scVal.Type == xdr.ScValTypeScvString && scVal.Str != nil {
-		return string(*scVal.Str), nil
-	}
-
-	return "", fmt.Errorf("not a string type")
-}
-```
-
-</CodeExample>
-</Details>
-
-### Ejecutando tu pipeline de pagos con RPC
-
-1. **Ejecuta el script de envío de pagos** en una terminal. Déjalo en ejecución, enviará un pago cada 30 segundos.
-
-<Details summary="Haz clic para ver el comando para ejecutar los pagos">
-<CodeExample>
-
-```bash
-# js
-node send_payment.js
-
-# java
-# JRE 17 or higher should be installed - https://adoptium.net/temurin/releases/?version=17&package=jdk
-# download Stellar Java SDK jar, latest release on maven central
-JAR_REPO='https://repo1.maven.org/maven2/network/lightsail/stellar-sdk'
-JAR_VERSION="2.0.0" # replace with latest version if needed
-JAR_FILE="stellar-sdk-$JAR_VERSION-uber.jar"
-curl -fsSL -o "$JAR_FILE" "$JAR_REPO/$JAR_VERSION/$JAR_FILE"
-
-javac -cp "$JAR_FILE" SendPaymentExample.java
-java -cp ".:$JAR_FILE" SendPaymentExample
-
-# go
-mkdir -p payments_example/sender
-cd payments_example
-go mod init payments_example
-go get github.com/stellar/go-stellar-sdk@latest
-go get github.com/stellar/stellar-rpc@latest
-# save sender.go code to sender/sender.go file
-go build -o sender sender/sender.go
-./sender
-```
-
-</CodeExample>
-</Details>
-
-2. **Ejecuta el script de monitoreo de pagos** en una terminal separada.
-
-<Details summary="Haz clic para ver el comando para ejecutar el monitor de pagos">
-<CodeExample>
-
-```bash
-# js
-node monitor_payments.js
-
-# java
-javac -cp "$JAR_FILE" MonitorPaymentExample.java
-java -cp ".:$JAR_FILE" MonitorPaymentExample
-
-# go
-mkdir -p payments_example/monitor
-# save monitor.go code to monitor/monitor.go file
-go build -o monitor monitor/monitor.go
-./monitor
-```
-
-</CodeExample>
-</Details>
-
-3. **Observa los eventos de pago** a medida que son detectados y mostrados en la consola.
-
-## Resumen
-
-- Los pagos mediante operaciones de transacción o invocaciones de contratos en la red Stellar pueden ser monitoreados aprovechando el modelo unificado de eventos desde el [Protocolo 23 (Whisk)](https://stellar.org/blog/developers/introducing-whisk-stellar-protocol-23) y el método `getEvents` del RPC.
-  - **Los pagos son eventos 'transfer'**: el [modelo unificado de eventos](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) asegura que tanto si un pago ocurrió a través de una operación o una invocación de contrato, se emitirá el mismo evento 'transfer'.
-  - **Tipo de Evento**: `"contract"` indica que los pagos son un evento a nivel de aplicación y no un evento 'sistema'.
-  - **Modelo de temas de transferencia**: un arreglo de cuatro temas, especificados en [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) y resumidos:
-    - `topic[0]` = El nombre del evento 'transfer' determina los siguientes 3 temas
-    - `topic[1]` = Dirección del emisor de la transferencia
-    - `topic[2]` = Dirección del receptor de la transferencia
-    - `topic[3]` = Identificador del activo (presente solo para activos Stellar, a través de sus contratos integrados (SAC))
-
-- RPC proporciona un filtrado preciso de eventos de la red Stellar, incluyendo el modelo de temas de evento definido para eventos unificados en [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md). Ahorras tiempo usando las capacidades de filtrado del servidor RPC para enfocarte solo en procesar los eventos relevantes para tu aplicación, como los pagos de una cuenta específica en este ejemplo.
-  - **Comodines**: el método `getEvents` del RPC permite usar "\*" para coincidir con cualquier valor en una posición de tema
-  - **Filtrado del lado del servidor**: `getEvents` del RPC aplica los filtros y sólo devuelve eventos que coinciden, reduciendo el ancho de banda
-  - **Paginación basada en cursores**: el método `getEvents` del RPC recupera los datos de eventos de forma eficiente con un mecanismo de paginación
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/simulateTransaction-Deep-Dive.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
deleted file mode 100644
index 5919fd3a9e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/simulateTransaction-Deep-Dive.mdx
+++ /dev/null
@@ -1,412 +0,0 @@
----
-title: guía del método RPC simulateTransaction
-description: Guía de ejemplos y tutoriales de simulateTransaction.
----
-
-## Descripción general
-
-El `simulateTransaction` endpoint en Stellar RPC te permite enviar una invocación de contrato de prueba para simular cómo sería ejecutada por la red Stellar. Esta simulación calcula los datos de la transacción efectiva, las autorizaciones requeridas y el costo mínimo de recursos. Proporciona una forma de probar y analizar los resultados potenciales de una transacción sin realmente enviarla a la red. A veces puede ser una buena manera de obtener datos del contrato también. Esta simulación calcula los datos de la transacción efectiva, las autorizaciones requeridas y el costo mínimo de recursos. Proporciona una forma de probar y analizar los resultados potenciales de una transacción sin realmente enviarla a la red. A veces, puede ser una buena manera de obtener datos del contrato.
-
-Si bien llamar al método en el servidor rpc no es la ÚNICA forma de simular una transacción, probablemente será la más común y la más fácil.
-
-Aquí veremos los objetos involucrados y sus definiciones.
-
-## Servicios RPC
-
-La Stellar Development Foundation proporciona un servicio RPC de testnet en `http://soroban-testnet.stellar.org`. Para los proveedores de red pública, consulta la lista de [Ecosystem RPC Providers](../../../data/apis/rpc/providers.mdx).
-
-### Endpoint de Testnet:
-
-https://soroban-testnet.stellar.org:443
-
-**SimulateTransactionParams** es el argumento pasado al endpoint RPC `simulateTransaction`:
-
-```typescript
-interface SimulateTransactionParams {
-  transaction: string; // The Stellar transaction to be simulated, serialized as a base64 string.
-  resourceConfig?: {
-    instructionLeeway: number; // Allow this many extra instructions when budgeting resources.
-  };
-}
-```
-
-**SimulateTransactionResult** es el resultado devuelto de la llamada. ¡Incluye [muchas cosas útiles](../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx)!
-
-## Cosas para las que se usa `simulateTransaction`:
-
-1. **Preparando transacciones `invokeHostFunctionOp`**: Cada vez que necesites enviar una transacción `invokeHostFunctionOp` a la red.
-2. **Determinación de la huella**: Para determinar la huella del ledger, que incluye todas las entradas de datos que la transacción leerá o escribirá.
-3. **Identificación de autorizaciones**: Para identificar las autorizaciones requeridas para la transacción.
-4. **Detección de errores**: Para detectar posibles errores e incidencias antes de la presentación real, ahorrando tiempo y recursos de la red.
-5. **Restauración de entradas de ledger archivadas o código de contrato**: Para preparar y restaurar datos archivados antes de la presentación real de la transacción.
-6. **Simulando llamadas a funciones del contrato**: Para recuperar ciertos datos del contrato sin afectar el estado del ledger. (Vale la pena señalar que también podrías recuperar ciertos datos del contrato directamente de las keys del ledger sin simulación si no requiere ninguna manipulación dentro de la lógica del contrato.)
-7. **Cálculo de recursos**: Para calcular los recursos necesarios (instrucciones de CPU, memoria, etc.) que consumirá una transacción.
-
-## Cómo llamar a `simulateTransaction`
-
-### Usando Fetch
-
-Aquí hay un ejemplo de cómo llamar al endpoint `simulateTransaction` directamente usando `fetch` en JavaScript:
-
-```javascript
-async function simulateTransaction(transactionXDR) {
-  const requestBody = {
-    jsonrpc: "2.0",
-    id: 8675309,
-    method: "simulateTransaction",
-    params: {
-      transaction: transactionXDR,
-      resourceConfig: {
-        instructionLeeway: 50000,
-      },
-    },
-  };
-
-  const response = await fetch("https://soroban-testnet.stellar.org:443", {
-    method: "POST",
-    headers: {
-      "Content-Type": "application/json",
-    },
-    body: JSON.stringify(requestBody),
-  });
-
-  const result = await response.json();
-  console.log(JSON.parse(result));
-}
-
-// Example XDR transaction envelope
-// Replace the following placeholder with your actual XDR transaction envelope
-const transactionXDR =
-  "AAAAAgAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAGQAJsOiAAAAEQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAGAAAAAAAAAABzAP+dP0PsNzYvFF1pv7a8RQXwH5eg3uZBbbWjE9PwAsAAAAJaW5jcmVtZW50AAAAAAAAAgAAABIAAAAAAAAAACDh1sDGwYAYgJ8EbeJPZwoZhDqEriwlbNnqivULm/oYAAAAAwAAAAMAAAAAAAAAAAAAAAA=";
-// An example of where to get the XDR is from TransactionBuilder class from the sdk as shown in the next example.
-simulateTransaction(transactionXDR);
-```
-
-### Usando el SDK de JavaScript
-
-El Stellar SDK proporciona un método conveniente para simular una transacción:
-
-```javascript
-import {
-  Keypair,
-  rpc as StellarRpc,
-  scValToNative,
-  TransactionBuilder,
-  BASE_FEE,
-  Networks,
-  Operation,
-} from "@stellar/stellar-sdk";
-
-const FRIENDBOT_URL = "https://friendbot-testnet.stellar.org/";
-
-const rpc_url = "https://soroban-testnet.stellar.org:443";
-
-// Generate a new keypair for transaction authorization.
-const keypair = Keypair.random();
-const secret = keypair.secret();
-const publicKey = keypair.publicKey();
-console.log("publicKey:", publicKey);
-// you need to fund the account.
-await fetch(`https://friendbot-testnet.stellar.org/?addr=${publicKey}`).then(
-  (res) => {
-    console.log(`funded account: ${publicKey}`);
-  },
-);
-
-// Initialize the rpcServer
-const RpcServer = new StellarRpc.Server(rpc_url, { allowHttp: true });
-
-// Load the account (getting the sequence number for the account and making an account object.)
-const account = await RpcServer.getAccount(publicKey);
-
-// Define the transaction
-const transaction = new TransactionBuilder(account, {
-  fee: BASE_FEE,
-})
-  .setNetworkPassphrase(Networks.TESTNET)
-  .setTimeout(30)
-  .addOperation(
-    Operation.invokeContractFunction({
-      function: "symbol",
-      // the contract function and address need to be set by you.
-      contract: "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
-      args: [],
-    }),
-  )
-  .build();
-// If you want to get this as an XDR string directly, you would use `transaction.toXDR('base64')`
-
-RpcServer.simulateTransaction(transaction).then((sim) => {
-  console.log("cost:", sim.cost);
-  console.log("result:", sim.result);
-  // the result is a ScVal and so we can parse that to human readable output using the sdk's `scValToNative` function:
-  console.log("humanReadable Result:", scValToNative(sim.result?.retval));
-  console.log("error:", sim.error);
-  console.log("latestLedger:", sim.latestLedger);
-});
-```
-
-#### Ejecutando el ejemplo
-
-Para ejecutar el código anterior, necesitarás instalar el Stellar SDK en tu proyecto. Puedes hacer esto ejecutando el siguiente comando en el directorio de tu proyecto:
-
-`npm install @stellar/stellar-sdk`
-
-Una vez que tu proyecto esté configurado, puedes crear un nuevo archivo mjs y pegar el código anterior. Luego puedes ejecutar el archivo usando Node.js ejecutando:
-
-`node <filename>.mjs`
-
-## Entendiendo la Huella
-
-Una huella es un conjunto de keys de ledger que la transacción leerá o escribirá. Estas keys están marcadas como de sólo lectura o lectura-escritura:
-
-- **Keys de solo lectura**: Disponibles solo para lectura.
-- **Keys de lectura-escritura**: Disponibles para lectura y escritura.
-
-La huella garantiza que una transacción sea consciente de todas las entradas de ledger con las que interactuará, previniendo errores inesperados durante la ejecución.
-
-## Montando una transacción
-
-Una vez que hayas simulado la transacción y obtenido los datos necesarios, puedes montar la transacción para la presentación real. La función `assembleTransaction` en el SDK ayuda con este proceso, pero también puedes llamar a `prepareTransaction` para simular y montar la transacción en un solo paso. Usando el SDK de JavaScript podemos llamar a [`assembleTransaction`](https://stellar.github.io/js-stellar-sdk/global.html#assembleTransaction) para montar una transacción fácilmente.
-
-## Manejando entradas de ledger archivadas
-
-Cuando una entrada de ledger está archivada, necesita ser restaurada antes de que la transacción pueda ser enviada. Esto se indica en el campo `restorePreamble` del resultado.
-
-```typescript
-interface RestorePreamble {
-  minResourceFee: string; // Absolute minimum resource fee to add when submitting the RestoreFootprint operation.
-  transactionData: string; // The recommended Soroban Transaction Data to use when submitting the RestoreFootprint operation.
-}
-```
-
-Aquí hay un ejemplo para manejar la restauración usando el `restorePreamble` para restaurar datos archivados:
-
-```typescript
-// Make sure to add the necessary imports:
-import { Contract } from "@stellar/stellar-sdk/contract";
-import {
-  Account,
-  Keypair,
-  Operation,
-  SorobanDataBuilder,
-  rpc as StellarRpc,
-  TimeoutInfinite,
-  Transaction,
-  TransactionBuilder,
-  scValToNative,
-  xdr,
-} from "@stellar/stellar-sdk";
-/**
- * Simulates a restoration transaction to determine if restoration is needed.
- * This function first checks the ledger entry for the given WASM hash. If the entry is found and has expired,
- * it attempts a restoration. If the entry hasn't expired yet but the TTL needs extension, it proceeds with TTL extension.
- * @param contract - The address of the contract to check
- * @param txParams - The transaction parameters including account and signer.
- * @returns A promise that resolves to a simulation response, indicating whether restoration or TTL extension is needed.
- */
-export async function simulateRestorationIfNeeded(
-  contract: ContractAddress,
-  txParams: TxParams,
-): Promise<
-  StellarRpc.Api.SimulateTransactionRestoreResponse | string | undefined
-> {
-  try {
-    const RpcServer = new StellarRpc.Server(
-      "https://soroban-testnet.stellar.org",
-      { allowHttp: true },
-    );
-    const account = await RpcServer.getAccount(txParams.account.accountId());
-    const contract = new Contract(contract);
-    const ledgerKey = contract.getFootprint();
-    const response = await RpcServer.getLedgerEntries(ledgerKey);
-    // Here we parse the response to make sure we got a response and that the liveUntilLedgerSeq parameter is there to make sure it's the response we want before continuing.
-    if (
-      response.entries &&
-      response.entries.length > 0 &&
-      response.entries[0].liveUntilLedgerSeq
-    ) {
-      const expirationLedger = response.entries[0].liveUntilLedgerSeq;
-      const desiredLedgerSeq = response.latestLedger + 500000;
-      // Be very aware of how many ledgers you want to extend it by.  It could quickly become extremely pricey in fees.
-      let extendLedgers = desiredLedgerSeq - expirationLedger;
-      if (extendLedgers < 10000) {
-        extendLedgers = 10000;
-      }
-      console.log("Expiration:", expirationLedger);
-      console.log("Desired TTL:", desiredLedgerSeq);
-      const sorobanData = new SorobanDataBuilder()
-        .setReadWrite([ledgerKey])
-        .build();
-      const restoreTx = new TransactionBuilder(
-        account,
-        txParams.txBuilderOptions,
-      )
-        .setSorobanData(sorobanData)
-        .addOperation(Operation.restoreFootprint({})) // The actual restore operation
-        .build();
-      // Simulate a transaction with a restoration operation to check if it's necessary
-
-      const restorationSimulation: StellarRpc.Api.SimulateTransactionResponse =
-        await RpcServer.simulateTransaction(restoreTx);
-
-      //check if restore is necessary. this code also checks if the simulation was successful.
-      const restoreNeeded = StellarRpc.Api.isSimulationRestore(
-        restorationSimulation,
-      );
-      console.log(`restoration needed: ${restoreNeeded}`);
-      // Check if the simulation indicates a need for restoration
-      if (restoreNeeded) {
-        return restorationSimulation as StellarRpc.Api.SimulateTransactionRestoreResponse;
-      } else {
-        console.log("No restoration needed., bumping the ttl.");
-        const account1 = await RpcServer.getAccount(
-          txParams.account.accountId(),
-        );
-
-        const bumpTTLtx = new TransactionBuilder(
-          account1,
-          txParams.txBuilderOptions,
-        )
-          .setSorobanData(
-            new SorobanDataBuilder().setReadOnly([ledgerKey]).build(),
-          )
-          .addOperation(
-            Operation.extendFootprintTtl({
-              extendTo: desiredLedgerSeq,
-            }),
-          ) // The actual TTL extension operation
-          .build();
-        const ttlSimResponse: StellarRpc.Api.SimulateTransactionResponse =
-          await RpcServer.simulateTransaction(bumpTTLtx);
-        const assembledTx = StellarRpc.assembleTransaction(
-          bumpTTLtx,
-          ttlSimResponse,
-        ).build();
-        const signedTx = new Transaction(
-          await txParams.signerFunction(assembledTx.toXDR()),
-          Networks.TESTNET,
-        );
-        // submit the assembled and signed transaction to bump it.
-        try {
-          const response = await sendTransaction(signedTx, (result) => {
-            console.log(`bump ttl for contract result: ${result}`);
-            return result;
-          });
-          return response;
-        } catch (error) {
-          console.error("Transaction submission failed with error:", error);
-          throw error;
-        }
-      }
-    } else {
-      console.log("No ledger entry found for the given WASM hash.");
-    }
-  } catch (error) {
-    console.error("Failed to simulate restoration:", error);
-    throw error;
-  }
-}
-
-/**
- * Handles the restoration of a Soroban contract.
- * @param {StellarRpc.Api.SimulateTransactionRestoreResponse} simResponse - The simulation response containing restoration information.
- * @param {TxParams} txParams - The transaction parameters.
- * @returns {Promise<void>} A promise that resolves when the restoration transaction has been submitted.
- */
-export async function handleRestoration(
-  simResponse: StellarRpc.Api.SimulateTransactionRestoreResponse,
-  txParams: TxParams,
-): Promise<void> {
-  const RpcServer = new StellarRpc.Server(
-    "https://soroban-testnet.stellar.org",
-    { allowHttp: true },
-  );
-  const restorePreamble = simResponse.restorePreamble;
-  console.log("Restoring for account:", txParams.account.accountId());
-  const account = await RpcServer.getAccount(txParams.account.accountId());
-  // Construct the transaction builder with the necessary parameters
-  const restoreTx = new TransactionBuilder(account, {
-    ...txParams.txBuilderOptions,
-    fee: restorePreamble.minResourceFee, // Update fee based on the restoration requirement
-  })
-    .setSorobanData(restorePreamble.transactionData.build()) // Set Soroban Data from the simulation
-    .addOperation(Operation.restoreFootprint({})) // Add the RestoreFootprint operation
-    .build(); // Build the transaction
-
-  const simulation: StellarRpc.Api.SimulateTransactionResponse =
-    await RpcServer.simulateTransaction(restoreTx);
-  const assembledTx = StellarRpc.assembleTransaction(
-    restoreTx,
-    simulation,
-  ).build();
-
-  const signedTx = new Transaction(
-    await txParams.signerFunction(assembledTx.toXDR()),
-    Networks.TESTNET,
-  );
-
-  console.log("Submitting restoration transaction");
-
-  try {
-    // Submit the transaction to the network
-    const response = await RpcServer.sendTransaction(signedTx);
-    console.log(
-      "Restoration transaction submitted successfully:",
-      response.hash,
-    );
-  } catch (error) {
-    console.error("Failed to submit restoration transaction:", error);
-    throw new Error("Restoration transaction failed");
-  }
-}
-```
-
-## Honorarios y uso de recursos
-
-Los contratos inteligentes de Soroban en Stellar utilizan un modelo de tarifas de recursos multidimensional, cobrando tarifas por varios tipos de recursos:
-
-1. **Instrucciones de CPU**: Número de instrucciones de CPU que usa la transacción.
-2. **Accesos a entradas de ledger**: Leer o escribir cualquier entrada de ledger.
-3. **I/O de ledger**: Número de bytes leídos o escritos en el ledger.
-4. **Tamaño de la transacción**: Tamaño de la transacción presentada a la red en bytes.
-5. **Tamaño de eventos y valor de retorno**: Tamaño de los eventos producidos por el contrato y el valor de retorno de la función de contrato de nivel superior.
-6. **Alquiler de espacio de ledger**: Pago por extensiones de TTL de entradas de ledger y pagos de alquiler por el aumento del tamaño de las entradas de ledger.
-
-Las tarifas se calculan en función del consumo de recursos declarado en la transacción. Las tarifas reembolsables se cobran antes de la ejecución y se reembolsan en función del uso real, mientras que las tarifas no reembolsables se calculan a partir de instrucciones de CPU, bytes leídos, bytes escritos y tamaño de la transacción. [Consulta este documento para una comprensión más profunda de las tarifas y el medidor.](../../../learn/fundamentals/fees-resource-limits-metering.mdx)
-
-## Manejo de Errores
-
-El mecanismo de simulación de transacciones proporciona una estimación del consumo de CPU y memoria de una invocación de contrato durante una transacción. También resalta [errores potenciales y limitaciones de recursos](../../../learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx#1-transaction-simulation) de la invocación antes del envío real.
-
-## Código de backend y flujo de trabajo
-
-El `simulateTransaction` endpoint aprovecha varios componentes de backend para simular la ejecución de una transacción. Aquí hay una breve explicación de cómo funciona:
-
-1. **Invocación de la simulación**:
-   - La simulación se inicia llamando a `simulate_invoke_host_function_op`, que toma parámetros como la transacción a simular, la configuración de recursos y otros detalles necesarios.
-
-2. **Fuente de instantánea y configuración de red**:
-   - La simulación utiliza una fuente de instantánea (`MockSnapshotSource`) y configuración de red (`NetworkConfig`) para imitar el estado del ledger y las condiciones de la red.
-
-3. **Cálculo de recursos**:
-   - La función `simulate_invoke_host_function_op_resources` calcula los recursos (instrucciones de CPU, bytes de memoria) requeridos para la transacción analizando los cambios en el ledger.
-
-4. **Ejecución y gestión de resultados**:
-   - El núcleo de la ejecución está a cargo de `invoke_host_function_in_recording_mode`, que registra el impacto de la transacción en el ledger.
-   - Los resultados son luego procesados, incluyendo cualquier autorización requerida, eventos emitidos y datos de transacción.
-
-5. **Ajustes y tarifas**:
-   - Los ajustes al uso de recursos y tarifas se realizan en función de configuraciones predefinidas (`SimulationAdjustmentConfig`), asegurando una estimación precisa de tarifas.
-
-Estas funciones están definidas en [`rs-soroban-env`](https://github.com/stellar/rs-soroban-env) y también en un [`soroban-simulation`](https://github.com/stellar/rs-soroban-env/tree/main/soroban-simulation) [crate](https://crates.io/crates/soroban-simulation) y manejan la lógica central para simular transacciones.
-
-## Lectura adicional
-
-Para más información y ejemplos, consulta el código y otra documentación:
-
-- [Documentación openRpc](../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx)
-- [Especificación json de openRpc](https://github.com/stellar/stellar-docs/tree/main/openrpc)
-- [preflight.go](https://github.com/stellar/stellar-rpc/blob/release/v22.1.2/cmd/stellar-rpc/internal/preflight/preflight.go)
-- [Código de ejemplo de Soroban](https://github.com/stellar/soroban-examples)
-- [Documentación del SDK de Stellar](https://stellar.github.io/js-stellar-sdk/)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/sponsored-reserves.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/sponsored-reserves.mdx
deleted file mode 100644
index 0cba350f1f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/sponsored-reserves.mdx
+++ /dev/null
@@ -1,596 +0,0 @@
----
-title: Reservas patrocinadas
-description: Utiliza las reservas patrocinadas para pagar las reservas base en nombre de otra cuenta.
-sidebar_position: 50
----
-
-import Details from "@theme/Details";
-
-Las reservas patrocinadas fueron introducidas en [CAP-0033](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md) y permiten que una cuenta (cuenta patrocinadora) pague las reservas base para otra cuenta (cuenta patrocinada). Mientras exista esta relación, los requerimientos de reservas base que normalmente se acumularían en la cuenta patrocinada ahora se acumulan en la cuenta patrocinadora.
-
-Las operaciones Begin Sponsoring Future Reserves y End Sponsoring Future Reserves deben aparecer en la transacción de patrocinio, garantizando que ambas cuentas estén de acuerdo con el patrocinio.
-
-Se puede patrocinar cualquier cosa que aumente el saldo mínimo (creación de cuenta, ofertas, trustlines, entradas de datos, signatarios, saldos reclamables).
-
-Para obtener información sobre reservas base, consulta nuestra sección sobre [Lumens](../../../learn/fundamentals/lumens.mdx#base-reserves).
-
-:::note
-
-Utiliza el [Calculador de Patrocinio de Billeteras Stellar](../../../tools/developer-tools/wallets.mdx#stellar-wallet-sponsorship-calculator) para estimar los requerimientos de XLM para billeteras que busquen usar reservas patrocinadas y transacciones con fee-bump para cubrir la creación de cuentas, tarifas de transacción, trustlines, y más.
-
-:::
-
-## Operaciones de reservas patrocinadas
-
-### Iniciar y finalizar patrocinio
-
-Para crear una reserva patrocinada, debes usar una transacción sándwich que incluya tres operaciones.
-
-- La primera operación: Begin Sponsoring Future Reserves inicia el patrocinio y requiere la firma de la cuenta patrocinadora.
-- La segunda operación: especifica qué se está patrocinando.
-- La tercera operación: End Sponsoring Future Reserves, permite que la cuenta patrocinada acepte el patrocinio y requiere la firma de ésta.
-
-Begin Sponsoring Future Reserves establece la relación is-sponsoring-future-reserves-for donde la cuenta patrocinadora es la cuenta fuente de la operación. La cuenta especificada en la operación es la cuenta patrocinada.
-
-End Sponsoring Future Reserves termina la relación actual de is-sponsoring-future-reserves-for para la cuenta fuente de la operación.
-
-Al final de cualquier transacción, no debe haber relaciones is-sponsoring-future-reserves-for activas, razón por la cual estas dos operaciones deben usarse juntas en una única transacción.
-
-Consulta los detalles de la operación en nuestra [sección Lista de Operaciones](../../../learn/fundamentals/transactions/list-of-operations.mdx).
-
-### Revocar patrocinio
-
-Permite a la cuenta patrocinadora eliminar o transferir patrocinios de ledgerEntries y signatarios existentes. Si el ledgerEntry o signatario no está patrocinado, el propietario del ledgerEntry o signatario puede establecer un patrocinio si es el beneficiario de una relación is-sponsoring-future-reserves-for.
-
-Lógica de la operación
-
-- Entrada/signatario está patrocinado
-  - La cuenta fuente es actualmente el beneficiario de una relación is-sponsoring-future-reserves-for
-    - Transfiere el patrocinio de la entrada/signatario desde la cuenta fuente a la cuenta que es el origen de is-sponsoring-future-reserves-for
-  - La cuenta fuente no es el beneficiario de una relación is-sponsoring-future-reserves-for
-    - Elimina el patrocinio de la entrada/signatario
-- Entrada/signatario no está patrocinado
-  - La cuenta fuente es actualmente el beneficiario de una relación is-sponsoring-future-reserves-for
-    - Establece un patrocinio entre la entrada/signatario y la cuenta que es el origen de is-sponsoring-future-reserves-for
-  - La cuenta fuente no es el beneficiario de una relación is-sponsoring-future-reserves-for
-    - No-Op
-
-Consulta los detalles de la operación en nuestra [sección Lista de Operaciones](../../../learn/fundamentals/transactions/list-of-operations.mdx#begin-sponsoring-future-reserves).
-
-## Efecto en el saldo mínimo
-
-Una vez que se introducen los patrocinios, el cálculo del saldo mínimo es: (2 reservas base + `numSubEntries` + `numSponsoring` - `numSponsored`) \* `baseReserve` + `liabilities.selling`.
-
-Cuando la cuenta A está patrocinando reservas futuras para la cuenta B, cualquier requisito de reserva que normalmente se acumularía en B se acumula en A, mostrado en `numSponsoring`. El hecho de que estas reservas sean proporcionadas por otra cuenta se reflejará en B en `numSponsored`, lo que cancelará el aumento de `numSubEntries`, manteniendo el saldo mínimo sin cambios para B.
-
-Cuando una entrada patrocinada o subentrada es eliminada, `numSponsoring` disminuye en la cuenta patrocinadora y `numSponsored` disminuye en la cuenta patrocinada.
-
-Para saber más sobre los requisitos de saldo mínimo, consulta nuestra sección sobre [Lumens](../../../learn/fundamentals/lumens.mdx#minimum-balance).
-
-## Efecto en los saldos reclamables
-
-Todos los saldos reclamables están patrocinados mediante lógica incorporada en las operaciones de saldo reclamable. La cuenta que crea el saldo reclamable paga la reserva base para obtener el saldo en el ledger. Cuando el saldo reclamable es reclamado por el(los) reclamante(s), el saldo reclamable se elimina del ledger, y la cuenta que lo creó recupera la reserva base.
-
-Lee más sobre saldos reclamables en nuestra [Entrada en la Enciclopedia de Saldos Reclamables](./claimable-balances.mdx).
-
-## Ejemplos
-
-Cada uno de los siguientes ejemplos se basa en el anterior, haciendo referencia a variables de fragmentos previos. Los siguientes ejemplos demostrarán:
-
-1. [Crear línea de confianza patrocinada](#1-sponsoring-trustlines) para otra cuenta
-2. [Transferir la responsabilidad del patrocinio](#2-transferring-sponsorship) de una cuenta a otra
-3. [Revocar el patrocinio](#3-sponsorship-revocation) completamente por una cuenta
-
-Para brevedad en los ejemplos de Golang, asumiremos la existencia de un método `SignAndSend`(...). Un método (definido más abajo) que crea y envía una transacción con los parámetros correctos y una verificación básica de errores.
-
-### Preámbulo
-
-Comenzaremos incluyendo el código básico para la creación de cuenta y activos.
-
-<CodeExample>
-
-```js
-import {
-  Keypair,
-  Asset,
-  TransactionBuilder,
-  Operation,
-  Networks,
-  BASE_FEE,
-} from "@stellar/stellar-sdk";
-import { Server } from "@stellar/stellar-sdk/rpc";
-
-let server = new Server("https://soroban-testnet.stellar.org");
-
-async function main() {
-  // Create & fund the new accounts.
-  let keypairs = [Keypair.random(), Keypair.random(), Keypair.random()];
-
-  for (const keypair of keypairs) {
-    console.log(`Funding:\n ${keypair.secret()}\n ${keypair.publicKey()}`);
-    await server
-      .requestAirdrop(keypair.publicKey())
-      .catch((err) => console.error("  failed:", err));
-  }
-
-  // Arbitrary assets to sponsor trustlines for. Let's assume they make sense.
-  let S1 = keypairs[0],
-    A = keypairs[1],
-    S2 = keypairs[2];
-  let assets = [
-    new Asset("ABCD", S1.publicKey()),
-    new Asset("EFGH", S1.publicKey()),
-    new Asset("IJKL", S2.publicKey()),
-  ];
-
-  // ...
-```
-
-```go
-package main
-
-import (
-  "context"
-  "fmt"
-  "net/http"
-  "strings"
-  "time"
-
-  "github.com/stellar/go-stellar-sdk/keypair"
-  "github.com/stellar/go-stellar-sdk/network"
-  "github.com/stellar/go-stellar-sdk/txnbuild"
-  sdk "github.com/stellar/stellar-rpc/client"
-  protocol "github.com/stellar/stellar-rpc/protocol"
-)
-
-func main() {
-  client := sdk.NewClient("https://soroban-testnet.stellar.org", nil)
-
-  // Both S1 and S2 will be sponsors for A at various points in time.
-  S1, A, S2 := keypair.MustRandom(), keypair.MustRandom(), keypair.MustRandom()
-  addressA := A.Address()
-
-  for _, pair := range []*keypair.Full{S1, A, S2} {
-    resp, err := http.Get("https://friendbot.stellar.org/?addr=" + pair.Address())
-    check(err)
-    resp.Body.Close()
-    fmt.Println("Funded", pair.Address())
-  }
-
-  // Load the corresponding account for both A and C.
-  ctx := context.Background()
-  s1Account, err := client.LoadAccount(ctx, S1.Address())
-  check(err)
-  aAccount, err := client.LoadAccount(ctx, addressA)
-  check(err)
-  s2Account, err := client.LoadAccount(ctx, S2.Address())
-  check(err)
-
-  // Arbitrary assets to sponsor trustlines for. Let's assume they make sense.
-  assets := []txnbuild.CreditAsset{
-    {Code: "ABCD", Issuer: S1.Address()},
-    {Code: "EFGH", Issuer: S1.Address()},
-    {Code: "IJKL", Issuer: S2.Address()},
-  }
-
-  // ...
-```
-
-</CodeExample>
-
-### 1. Patrocinando trustlines
-
-Ahora, patrocinemos trustlines para la Cuenta A. Observa cómo la operación `CHANGE_TRUST` está entre las operaciones de inicio y fin del patrocinio, y que todas las cuentas relevantes deben firmar la transacción.
-
-<Details summary="Patrocinando una sola línea de confianza">
-<CodeExample>
-
-```js
-//
-// 1. S1 will sponsor a trustline for Account A.
-//
-let s1Account = await server.getAccount(S1.publicKey()).catch(accountFail);
-let tx = new TransactionBuilder(s1Account, { fee: BASE_FEE })
-  .addOperation(
-    Operation.beginSponsoringFutureReserves({
-      sponsoredId: A.publicKey(),
-    }),
-  )
-  .addOperation(
-    Operation.changeTrust({
-      source: A.publicKey(),
-      asset: assets[0],
-      limit: "1000", // This limit can vary according with your application;
-      // if left empty, it defaults to the max limit.
-    }),
-  )
-  .addOperation(
-    Operation.endSponsoringFutureReserves({
-      source: A.publicKey(),
-    }),
-  )
-  .setNetworkPassphrase(Networks.TESTNET)
-  .setTimeout(180)
-  .build();
-
-// Note that while either can submit this transaction, both must sign it.
-tx.sign(S1, A);
-let txResponse = await sendTransaction(tx);
-if (!txResponse) {
-  return;
-}
-
-console.log("Sponsored a trustline of", A.publicKey());
-```
-
-```go
-  //
-  // 1. S1 will sponsor a trustline for Account A.
-  //
-  sponsorTrustline := []txnbuild.Operation{
-    &txnbuild.BeginSponsoringFutureReserves{
-      SourceAccount: s1Account.GetAccountID(),
-      SponsoredID:   addressA,
-    },
-    &txnbuild.ChangeTrust{
-      Line:  assets[0].MustToChangeTrustAsset(),
-      Limit: txnbuild.MaxTrustlineLimit,
-    },
-    &txnbuild.EndSponsoringFutureReserves{},
-  }
-
-  // Note that while A can submit this transaction, both sign it.
-  SignAndSend(client, aAccount, []*keypair.Full{S1, A}, sponsorTrustline...)
-  fmt.Println("Sponsored a trustline of", A.Address())
-```
-
-</CodeExample>
-</Details>
-
-<Details summary="Dos cuentas patrocinando diferentes activos para una sola cuenta">
-<CodeExample>
-
-```js
-//
-// 2. Both S1 and S2 sponsor trustlines for Account A for different assets.
-//
-let aAccount = await server.getAccount(A.publicKey()).catch(accountFail);
-tx = new TransactionBuilder(aAccount, { fee: BASE_FEE })
-  .addOperation(
-    Operation.beginSponsoringFutureReserves({
-      source: S1.publicKey(),
-      sponsoredId: A.publicKey(),
-    }),
-  )
-  .addOperation(
-    Operation.changeTrust({
-      asset: assets[1],
-      limit: "5000",
-    }),
-  )
-  .addOperation(Operation.endSponsoringFutureReserves())
-  .addOperation(
-    Operation.beginSponsoringFutureReserves({
-      source: S2.publicKey(),
-      sponsoredId: A.publicKey(),
-    }),
-  )
-  .addOperation(
-    Operation.changeTrust({
-      asset: assets[2],
-      limit: "2500",
-    }),
-  )
-  .addOperation(Operation.endSponsoringFutureReserves())
-  .setNetworkPassphrase(Networks.TESTNET)
-  .setTimeout(180)
-  .build();
-
-// Note that all 3 accounts must approve/sign this transaction.
-tx.sign(S1, S2, A);
-txResponse = await sendTransaction(tx);
-if (!txResponse) {
-  return;
-}
-
-console.log("Sponsored two trustlines of", A.publicKey());
-```
-
-```go
-  //
-  // 2. Both S1 and S2 sponsor trustlines for Account A for different assets.
-  //
-  sponsorTrustline = []txnbuild.Operation{
-    &txnbuild.BeginSponsoringFutureReserves{
-      SourceAccount: s1Account.GetAccountID(),
-      SponsoredID:   addressA,
-    },
-    &txnbuild.ChangeTrust{
-      Line:  assets[1].MustToChangeTrustAsset(),
-      Limit: txnbuild.MaxTrustlineLimit,
-    },
-    &txnbuild.EndSponsoringFutureReserves{},
-
-    &txnbuild.BeginSponsoringFutureReserves{
-      SourceAccount: s2Account.GetAccountID(),
-      SponsoredID:   addressA,
-    },
-    &txnbuild.ChangeTrust{
-      Line:  assets[2].MustToChangeTrustAsset(),
-      Limit: txnbuild.MaxTrustlineLimit,
-    },
-    &txnbuild.EndSponsoringFutureReserves{},
-  }
-
-  // Note that all 3 accounts must approve/sign this transaction.
-  SignAndSend(client, aAccount, []*keypair.Full{S1, S2, A}, sponsorTrustline...)
-  fmt.Println("Sponsored two trustlines of", A.Address())
-```
-
-</CodeExample>
-</Details>
-
-### 2. Transferir patrocinio
-
-Supongamos que ahora el Firmante 1 quiere transferir la responsabilidad de patrocinar las reservas para el trustline al Patrocinador 2. Esto se logra intercalando la transferencia entre las operaciones `BEGIN/END_SPONSORING_FUTURE_RESERVES`. Ambos participantes deben firmar la transacción, aunque cualquiera de ellos puede enviarla.
-
-Una forma intuitiva de pensar en una transferencia de patrocinio es que el acto mismo del patrocinio está siendo patrocinado por una nueva cuenta. Es decir, el nuevo patrocinador asume las responsabilidades del antiguo patrocinador patrocinando una revocación.
-
-<CodeExample>
-
-```js
-//
-// 3. Transfer sponsorship of B's second trustline from S1 to S2.
-//
-tx = new TransactionBuilder(s1Account, { fee: BASE_FEE })
-  .addOperation(
-    Operation.beginSponsoringFutureReserves({
-      source: S2.publicKey(),
-      sponsoredId: S1.publicKey(),
-    }),
-  )
-  .addOperation(
-    Operation.revokeTrustlineSponsorship({
-      account: A.publicKey(),
-      asset: assets[1],
-    }),
-  )
-  .addOperation(Operation.endSponsoringFutureReserves())
-  .setNetworkPassphrase(Networks.TESTNET)
-  .setTimeout(180)
-  .build();
-
-// Notice that while the old sponsor *sends* the transaction, both sponsors
-// must *approve* the transfer.
-tx.sign(S1, S2);
-txResponse = await sendTransaction(tx);
-if (!txResponse) {
-  return;
-}
-
-console.log("Transferred sponsorship for", A.publicKey());
-```
-
-```go
-  //
-  // 3. Transfer sponsorship of B's second trustline from S1 to S2.
-  //
-  transferOps := []txnbuild.Operation{
-    &txnbuild.BeginSponsoringFutureReserves{
-      SourceAccount: s2Account.GetAccountID(),
-      SponsoredID:   S1.Address(),
-    },
-    &txnbuild.RevokeSponsorship{
-      SponsorshipType: txnbuild.RevokeSponsorshipTypeTrustLine,
-      Account:         &addressA,
-      TrustLine: &txnbuild.TrustLineID{
-        Account: addressA,
-        Asset:   assets[1].MustToTrustLineAsset(),
-      },
-    },
-    &txnbuild.EndSponsoringFutureReserves{},
-  }
-
-  // Notice that while the old sponsor *sends* the transaction (in this case),
-  // both sponsors must *approve* the transfer.
-  SignAndSend(client, s1Account, []*keypair.Full{S1, S2}, transferOps...)
-  fmt.Println("Transferred sponsorship for", A.Address())
-```
-
-</CodeExample>
-
-En este punto, el Firmante 1 solo está patrocinando el primer activo (codificado arbitrariamente como ABCD), mientras que el Firmante 2 está patrocinando los otros dos activos. (Recuerda que inicialmente el Firmante 1 también patrocinaba EFGH).
-
-### 3. Revocación de patrocinio
-
-Finalmente, podemos demostrar la revocación completa de patrocinios. A continuación, el Firmante 2 se elimina a sí mismo de toda responsabilidad sobre los dos trustlines de activos. Observa que la Cuenta A no está involucrada en absoluto, ya que la revocación debería poder realizarse únicamente a discreción del patrocinador.
-
-<CodeExample>
-
-```js
-  //
-  // 4. S2 revokes sponsorship of B's trustlines entirely.
-  //
-  let s2Account = await server.getAccount(S2.publicKey()).catch(accountFail);
-  tx = new TransactionBuilder(s2Account, { fee: BASE_FEE })
-    .addOperation(
-      Operation.revokeTrustlineSponsorship({
-        account: A.publicKey(),
-        asset: assets[1],
-      }),
-    )
-    .addOperation(
-      Operation.revokeTrustlineSponsorship({
-        account: A.publicKey(),
-        asset: assets[2],
-      }),
-    )
-    .setNetworkPassphrase(Networks.TESTNET)
-    .setTimeout(180)
-    .build();
-
-  tx.sign(S2);
-  txResponse = await sendTransaction(tx);
-  if (!txResponse) {
-    return;
-  }
-
-  console.log("Revoked sponsorship for", A.publicKey());
-} // ends main()
-```
-
-```go
-  //
-  // 4. S2 revokes sponsorship of B's trustlines entirely.
-  //
-  revokeOps := []txnbuild.Operation{
-    &txnbuild.RevokeSponsorship{
-      SponsorshipType: txnbuild.RevokeSponsorshipTypeTrustLine,
-      Account:         &addressA,
-      TrustLine: &txnbuild.TrustLineID{
-        Account: addressA,
-        Asset:   assets[1].MustToTrustLineAsset(),
-      },
-    },
-    &txnbuild.RevokeSponsorship{
-      SponsorshipType: txnbuild.RevokeSponsorshipTypeTrustLine,
-      Account:         &addressA,
-      TrustLine: &txnbuild.TrustLineID{
-        Account: addressA,
-        Asset:   assets[2].MustToTrustLineAsset(),
-      },
-    },
-  }
-
-  SignAndSend(client, s2Account, []*keypair.Full{S2}, revokeOps...)
-  fmt.Println("Revoked sponsorship for", A.Address())
-} // ends main()
-```
-
-</CodeExample>
-
-### Cuentas fuente de patrocinio
-
-En cuanto a los campos SourceAccount del sándwich de patrocinio, es importante referirse a la sabiduría de [CAP-33](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md#abstract):
-
-> Esta relación es iniciada por `BeginSponsoringFutureReservesOp`, donde la cuenta patrocinadora es la cuenta fuente, y termina con `EndSponsoringFutureReserveOp`, donde la cuenta patrocinada es la cuenta fuente.
-
-Como la cuenta fuente se establece por defecto como el remitente de la transacción si se omite, este campo siempre debe establecerse para el `Begin` o el `End`.
-
-Por ejemplo, la siguiente es una expresión idéntica al ejemplo previo de Golang de patrocinar un trustline, solo que enviada por el patrocinador (Patrocinador 1) en lugar de por la cuenta patrocinada (Cuenta A). Observa las diferencias en dónde se establece `SourceAccount`:
-
-<CodeExample>
-
-```go
-    sponsorTrustline := []txnbuild.Operation{
-        &txnbuild.BeginSponsoringFutureReserves{
-            SponsoredID: addressA,
-        },
-        &txnbuild.ChangeTrust{
-            SourceAccount: aAccount.AccountID,
-            Line:          &assets[0],
-            Limit:         txnbuild.MaxTrustlineLimit,
-        },
-        &txnbuild.EndSponsoringFutureReserves{
-            SourceAccount: aAccount.AccountID,
-        },
-    }
-
-    // Again, both participants must still sign the transaction: the sponsored
-    // account must consent to the sponsorship.
-    SignAndSend(client, s1Account.AccountID, []*keypair.Full{S1, A}, sponsorTrustline...)
-```
-
-</CodeExample>
-
-### Otros ejemplos
-
-Si deseas otros ejemplos o quieres ver un desglose más genérico en pseudo-código de estos escenarios de patrocinio, puedes referirte directamente a [CAP-0033](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md#example-revoke-sponsorship).
-
-### Nota al pie
-
-Para los ejemplos anteriores, una implementación de `SignAndSend` (Golang) y un código (muy) básico para la comprobación de errores (en todos los lenguajes) podrían verse algo así:
-
-<CodeExample>
-
-```js
-async function sendTransaction(tx) {
-  const sendResp = await server.sendTransaction(tx);
-  if (sendResp.status !== "PENDING") throw sendResp;
-
-  const getResp = await server.pollTransaction(sendResp.hash);
-  if (getResp.status !== "SUCCESS") throw getResp;
-
-  return getResp;
-}
-
-function accountFail(err) {
-  console.error(" Failed to load account:", err);
-}
-```
-
-```go
-
-// Builds a transaction containing `operations...`, signed (by `signers`), and
-// submitted using the given `client` on behalf of `account`.
-func SignAndSend(
-  client *sdk.Client,
-  account txnbuild.Account,
-  signers []*keypair.Full,
-  operations ...txnbuild.Operation,
-) protocol.GetTransactionResponse {
-  // Build, sign, and submit the transaction
-  tx, err := txnbuild.NewTransaction(
-    txnbuild.TransactionParams{
-      SourceAccount:        account,
-      IncrementSequenceNum: true,
-      BaseFee:              txnbuild.MinBaseFee,
-      Preconditions: txnbuild.Preconditions{
-        TimeBounds: txnbuild.NewInfiniteTimeout(),
-      },
-      Operations: operations,
-    },
-  )
-  check(err)
-
-  for _, signer := range signers {
-    tx, err = tx.Sign(network.TestNetworkPassphrase, signer)
-    check(err)
-  }
-
-  txnB64, err := tx.Base64()
-  check(err)
-
-  txSendResp, err := client.SendTransaction(context.Background(),
-    protocol.SendTransactionRequest{Transaction: txnB64})
-  check(err)
-
-  for i := range 5 {
-    txResp, err := client.GetTransaction(context.Background(),
-      protocol.GetTransactionRequest{Hash: txSendResp.Hash})
-    check(err)
-
-    switch txResp.Status {
-    case "NOT_FOUND":
-    case "SUCCESS":
-      return txResp
-    case "FAILED":
-      panic(fmt.Errorf("transaction failed: %s",
-        strings.Join(txResp.DiagnosticEventsXDR, "\n")))
-    }
-
-    // Increase delay for each polling request
-    time.Sleep(time.Duration(i) * time.Second)
-  }
-
-  panic(fmt.Errorf("transaction never found: %s", txSendResp.Hash))
-}
-
-func check(err error) {
-  if err != nil {
-    panic(err)
-  }
-}
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/submit-transaction-wait-js.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/submit-transaction-wait-js.mdx
deleted file mode 100644
index 3ee62f3702..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/submit-transaction-wait-js.mdx
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Enviar una transacción a Stellar RPC utilizando el SDK de JavaScript
-hide_table_of_contents: true
-description: Utiliza un mecanismo de repetición para enviar una transacción al RPC.
----
-
-Aquí hay un mecanismo de bucle simple y rudimentario para enviar una transacción a Stellar RPC y esperar un resultado.
-
-```typescript
-import { Transaction, FeeBumpTransaction } from "@stellar/stellar-sdk";
-import { Server, Api } from "@stellar/stellar-sdk/rpc";
-
-const RPC_SERVER = "https://soroban-testnet.stellar.org/";
-const server = new Server(RPC_SERVER);
-
-// Submits a tx and then polls for its status until a timeout is reached.
-async function submitTx(
-  tx: Transaction | FeeBumpTransaction,
-): Promise<Api.GetTransactionResponse> {
-  return server
-    .sendTransaction(tx)
-    .then(async (reply) => {
-      if (reply.status !== "PENDING") {
-        throw reply;
-      }
-
-      return server.pollTransaction(reply.hash, {
-        sleepStrategy: (_iter: number) => 500,
-        attempts: 5,
-      });
-    })
-    .then((finalStatus) => {
-      switch (finalStatus.status) {
-        case Api.GetTransactionStatus.FAILED:
-        case Api.GetTransactionStatus.NOT_FOUND:
-          throw tmpStatus;
-        case Api.GetTransactionStatus.SUCCESS:
-          return status;
-      }
-    });
-}
-```
-
-:::caution
-
-Recuerda: ¡Siempre debes manejar los errores de manera elegante! Este es un enfoque que falla de forma contundente y rápida que solo debe usarse en estos ejemplos.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/upload-wasm-bytecode.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/upload-wasm-bytecode.mdx
deleted file mode 100644
index b97b6f1403..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/transactions/upload-wasm-bytecode.mdx
+++ /dev/null
@@ -1,392 +0,0 @@
----
-title: Subir código byte de WebAssembly (Wasm) usando código
-description: Sube el Wasm del contrato usando js-stellar-sdk.
----
-
-<head>
-  <title>Instalar código byte de WebAssembly (Wasm) usando código</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Instalar código byte de WebAssembly (Wasm) usando código"
-  />
-  <meta
-    property="og:description"
-    content="Esta guía te llevará a través de la instalación del wasm del contrato usando js-stellar-sdk."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Instalar código byte de WebAssembly (Wasm) usando código
-
-Este proceso sube el código del contrato a la Stellar Testnet en una transacción, el blob Wasm subido es una [fuente del contrato](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-02.md#contract-source), que se puede considerar como la 'clase' de un contrato. Se pueden desplegar múltiples [instancias de un contrato](../conventions/deploy-contract.mdx) que comparten la misma fuente, pero tienen su propio estado.
-
-## Prerrequisitos
-
-Antes de comenzar, asegúrate de tener instalado lo siguiente para compilar un contrato inteligente:
-
-1. [Rust](https://www.rust-lang.org/) y Cargo (para compilar contratos inteligentes)
-2. La CLI de Stellar
-
-## Inicializar y desarrollar un contrato Rust de ejemplo
-
-```bash
-stellar contract init hello-world
-cd hello-world
-
-# use rust compiler to compile Rust project into a WebAssembly (Wasm) dynamic library (cdylib).
-stellar contract build
-# cargo rustc --manifest-path=contracts/hello_world/Cargo.toml --crate-type=cdylib --target=wasm32v1-none --release
-```
-
-Estamos inicializando el contrato `hello_world` por defecto en [soroban_examples](https://github.com/stellar/soroban-examples) en el directorio `hello-world`. Puedes usar la opción `-w` para crear con otro ejemplo como `account`.
-
-Después de desarrollar el contrato para producción, el archivo .wasm generado está en la ruta `hello-word/target/wasm32v1-none/release/hello_world.wasm`
-
-## Subir Wasm a la blockchain Stellar
-
-Podemos utilizar uno de los [SDKs del cliente](../../../tools/sdks/client-sdks.mdx), e instalar las dependencias necesarias para el lenguaje de programación que elijas:
-
-- SDK de JavaScript: [Node.js](https://nodejs.org/en) y npm
-- SDK de Python: [pip](https://pip.pypa.io/en/stable/installation/)
-
-Crea un nuevo directorio para tu proyecto y navega dentro de él:
-
-```bash
-mkdir install-wasm
-cd install-wasm
-```
-
-### Ejecutar el script de instalación
-
-Se pueden usar diferentes lenguajes de programación para subir el archivo `.wasm`, su hash SHA256 se usa para desplegar el contrato.
-
-<Tabs>
-
-<TabItem value="js" label="JavaScript">
-Esta guía te llevará a través de la instalación del Wasm del contrato usando el SDK de JavaScript: [js-stellar-sdk](https://github.com/stellar/js-stellar-sdk).
-
-Crea un nuevo proyecto Node.js con un archivo JavaScript e instala las dependencias necesarias:
-
-```bash
-touch index.js
-npm init es6 -y
-npm install @stellar/stellar-sdk fs
-```
-
-Ejecuta el script con `node index.js`, lee el archivo Wasm, obtiene detalles de la cuenta y sube el contrato en una transacción:
-
-```javascript
-// Import necessary modules in your JavaScript file:
-import * as StellarSDK from "@stellar/stellar-sdk";
-import fs from "fs";
-
-async function uploadWasm(filePath) {
-  // reads the compiled Wasm file to buffer
-  const bytecode = fs.readFileSync(filePath);
-
-  // retrieves account details from the network
-  const account = await server.getAccount(sourceKeypair.publicKey());
-
-  // installs the bytecode with a `uploadContractWasm` Stellar operation wrapped in a transaction sent to the network
-  const operation = StellarSDK.Operation.uploadContractWasm({ wasm: bytecode });
-  return await buildAndSendTransaction(account, operation);
-}
-
-// constructs a transaction, signs it, and submits it to the network, handling any necessary retries for transaction confirmation.
-async function buildAndSendTransaction(account, operations) {
-  const transaction = new StellarSDK.TransactionBuilder(account, {
-    fee: StellarSDK.BASE_FEE,
-    networkPassphrase: StellarSDK.Networks.TESTNET,
-  })
-    .addOperation(operations)
-    .setTimeout(30)
-    .build();
-
-  const tx = await server.prepareTransaction(transaction);
-  tx.sign(sourceKeypair);
-
-  console.log("Submitting transaction...");
-  let response = await server.sendTransaction(tx);
-  const hash = response.hash;
-  console.log(`Transaction hash: ${hash}`);
-  console.log("Awaiting confirmation...");
-
-  while (true) {
-    response = await server.getTransaction(hash);
-    if (response.status !== "NOT_FOUND") {
-      break;
-    }
-    await new Promise((resolve) => setTimeout(resolve, 1000));
-  }
-
-  if (response.status === "SUCCESS") {
-    console.log("Transaction successful.");
-    return response;
-  } else {
-    console.log("Transaction failed.");
-    throw new Error("Transaction failed");
-  }
-}
-
-// Upload contract to the testnet
-const server = new StellarSDK.rpc.Server(
-  "https://soroban-testnet.stellar.org:443",
-);
-// Replace `Your_Secret_Key`
-const sourceKeypair = StellarSDK.Keypair.fromSecret("Your_Secret_Key");
-// Adjust this path as necessary
-const wasmFilePath = "../target/wasm32v1-none/release/hello_world.wasm";
-
-try {
-  let uploadResponse = await uploadWasm(wasmFilePath);
-  const byteArray = uploadResponse.returnValue.bytes();
-  const wasmHash = byteArray.toString("hex");
-  console.log(`Wasm hash: ${wasmHash}`);
-} catch (error) {
-  console.error(error);
-}
-```
-
-</TabItem>
-<TabItem value="py" label="Python">
-Esta guía te llevará a través de la instalación del Wasm del contrato usando el SDK de Python: [py-stellar-base](https://stellar-sdk.readthedocs.io/en/soroban/).
-
-Crea un nuevo script en Python e instala las dependencias necesarias:
-
-```bash
-touch install.py
-pip install stellar-sdk
-```
-
-Ejecuta el script con `python3 install.py`, lee el archivo Wasm, obtiene detalles de la cuenta y sube el contrato en una transacción:
-
-```py
-import asyncio
-import time
-from stellar_sdk import Keypair, Network, SorobanServer, TransactionBuilder, xdr as stellar_xdr
-from stellar_sdk.exceptions import PrepareTransactionException
-from stellar_sdk.soroban_rpc import GetTransactionStatus
-import hashlib
-
-
-def print_wasm_hash(wasm_bytes):
-    # Create a SHA256 hash object
-    sha256_hash = hashlib.sha256()
-
-    # Update the hash object with the WASM bytes
-    sha256_hash.update(wasm_bytes)
-
-    # Get the digest and convert it to a stellar_sdk.xdr.Hash object
-    hash_bytes = sha256_hash.digest()
-    xdr_hash = stellar_xdr.Hash(hash_bytes)
-    hash_hex_str = xdr_hash.hash.hex()
-    print(f"Wasm Hash: {hash_hex_str}")
-
-
-async def upload_wasm(file_path):
-    # Read the compiled Wasm file
-    with open(file_path, 'rb') as file:
-        wasm_bytes = file.read()
-
-    # Retrieve account details from the network
-    account = server.load_account(source_keypair.public_key)
-
-    # print wasm hash for later deployment
-    print_wasm_hash(wasm_bytes)
-
-    # Install the bytes with an 'uploadContractWasm' Stellar operation
-    return await build_and_send_transaction(account, wasm_bytes)
-
-
-async def build_and_send_transaction(account, bytes):
-    transaction = (
-        TransactionBuilder(
-            source_account=account,
-            network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-        )
-        .append_upload_contract_wasm_op(bytes)
-        .set_timeout(30)
-        .build()
-    )
-
-    print("Preparing transaction...")
-    try:
-        tx = server.prepare_transaction(transaction)
-    except PrepareTransactionException as e:
-        print(f"Got exception: {e}")
-        return None
-
-    tx.sign(source_keypair)
-
-    print("Submitting transaction...")
-    response = server.send_transaction(tx)
-    hash = response.hash
-    print(f"Transaction hash: {hash}")
-    print("Awaiting confirmation...")
-
-    while True:
-        response = server.get_transaction(hash)
-        if response.status != GetTransactionStatus.NOT_FOUND:
-            break
-        time.sleep(1)
-
-    if response.status == GetTransactionStatus.SUCCESS:
-        print("Transaction successful.")
-        return response
-    else:
-        print("Transaction failed.")
-        raise Exception("Transaction failed")
-
-# Upload contract to the testnet
-server = SorobanServer("https://soroban-testnet.stellar.org:443")
-# Replace 'Your_Secret_Key' with your actual secret key
-source_keypair = Keypair.from_secret("Your_Secret_Key")
-# Adjust this path as necessary
-wasm_file_path = "../target/wasm32v1-none/release/hello_world.wasm"
-
-
-async def main():
-    try:
-      await upload_wasm(wasm_file_path)
-    except Exception as error:
-        print(f"Error: {error}")
-
-# Run the main function
-asyncio.run(main())
-```
-
-</TabItem>
-<TabItem value="rust" label="Rust">
-
-Esta guía te llevará a través de la subida del Wasm del contrato usando el SDK de Rust: [rs-soroban-client](https://github.com/rahul-soshte/rs-soroban-client).
-
-Crea un nuevo proyecto Cargo e instala las dependencias necesarias:
-
-```bash
-cargo init
-cargo add soroban_client
-cargo add tokio -F macros,full
-```
-
-Copia el código abajo en `src/main.rs` y luego ejecuta el programa con `cargo run`, lee el archivo Wasm, obtiene detalles de la cuenta y sube el contrato en una transacción:
-
-```rust
-use std::time::Duration;
-
-use soroban_client::{
-    account::{Account, AccountBehavior},
-    keypair::{Keypair, KeypairBehavior},
-    network::{NetworkPassphrase, Networks},
-    operation::Operation,
-    soroban_rpc::TransactionStatus,
-    transaction::{TransactionBehavior, TransactionBuilder, TransactionBuilderBehavior},
-    Options, Server,
-};
-
-#[tokio::main]
-pub async fn main() -> Result<(), Box<dyn std::error::Error>> {
-    let server_url = "https://soroban-testnet.stellar.org";
-    let server = Server::new(server_url, Options::default())?;
-
-    // Adjust this path as necessary
-    let wasm_file_path = "../target/wasm32v1-none/release/hello_world.wasm";
-
-    // Read the wasm file
-    let wasm_bytes = std::fs::read(wasm_file_path)?;
-
-    // Build the xdr::HostFunction::UploadContractWasm operation
-    let upload_wasm_op = Operation::new()
-        .upload_wasm(&wasm_bytes, None)
-        .expect("Cannot create upload_wasm operation");
-
-    // Replace Your_Secret_Key with your actual secret key
-    let source_keypair = Keypair::from_secret("Your_Secret_Key")?;
-    let source_public_key = &source_keypair.public_key();
-
-    // Get account information from server
-    let account_data = server.get_account(source_public_key).await?;
-
-    // Build the Account to use in the transaction
-    let mut source_account = Account::new(source_public_key, &account_data.sequence_number())?;
-
-    // Build the operation
-    let tx = TransactionBuilder::new(&mut source_account, Networks::testnet(), None)
-        .fee(1000u32)
-        .add_operation(upload_wasm_op)
-        .build();
-
-    let mut ptx = server.prepare_transaction(&tx).await?;
-    ptx.sign(&[source_keypair]);
-
-    println!("> Uploading WASM executable");
-    let response = server.send_transaction(ptx).await?;
-
-    let hash = &response.hash;
-    println!(">> Tx hash: {hash}");
-    let wasm_hash = match server.wait_transaction(hash, Duration::from_secs(15)).await {
-        Ok(tx_result) if tx_result.status == TransactionStatus::Success => {
-            let (_meta, ret_val) = tx_result.to_result_meta().expect("No meta found");
-            if let Some(scval) = ret_val {
-                let bytes: Vec<u8> = scval.try_into().expect("Cannot convert ScVal to Vec<u8>");
-                *bytes.last_chunk::<32>().expect("Not 32 bytes")
-            } else {
-                return Err(">> None return value".into());
-            }
-        }
-        _ => {
-            println!(">> Failed to upload the WASM executable");
-            return Err(">> Failed to upload the wasm".into());
-        }
-    };
-    let hex_wasm_hash: String = wasm_hash.iter().map(|b| format!("{:02x}", b)).collect();
-    println!(">> Wasm hash: {hex_wasm_hash}");
-    println!();
-
-    Ok(())
-}
-```
-
-</TabItem>
-</Tabs>
-
-Reemplaza `"Your_Secret_Key"` con tu clave secreta real.
-
-```bash
-stellar keys generate --global hello --network testnet
-stellar keys show hello
-```
-
-La CLI de Stellar se puede usar para generar identidades, por ejemplo `hello`, y mostrar su clave secreta.
-
-:::tip
-
-Asegúrate de manejar las claves secretas y privadas de forma segura en entornos de producción y nunca las expongas en tus repositorios de código.
-
-:::
-
-```bash
-Submitting transaction...
-Transaction hash: cef7a63667fe5b0ddcde5562d90e0a40bc04c69616916d1d7fa74a8571bbd82f
-Awaiting confirmation...
-Transaction successful.
-Wasm hash: 275405755441e4be59555bb5c5fd81e84ed21659015d8f3594796c1cf3f380db
-```
-
-El hash de la transacción de carga devuelto puede verse con herramientas en línea: [stellar.expert/explorer/testnet/tx/cef7a63667fe5b0ddcde5562d90e0a40bc04c69616916d1d7fa74a8571bbd82f](https://stellar.expert/explorer/testnet/tx/cef7a63667fe5b0ddcde5562d90e0a40bc04c69616916d1d7fa74a8571bbd82f)
-
-[Los contratos cargados se almacenan en entradas ledger ContractCodeEntry.](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-02.md#uploading-wasm-sources-using-invokehostfunctionop) Estas entradas están indexadas por el hash del Wasm usado para cargarlos.
-
-Puedes usar el hash del Wasm para desplegar con la CLI de Stellar:
-
-```bash
-stellar contract deploy \
-    --source-account hello \
-    --network testnet \
-    --wasm-hash 275405755441e4be59555bb5c5fd81e84ed21659015d8f3594796c1cf3f380db
-# CC6NAQE3ZHRQV3NPQB3F3NYEFBAMEABA4KQTM6A2V5V7PBR5H3UEU3MW
-```
-
-Visualiza el contrato desplegado usando el identificador devuelto con herramientas en línea: [stellar.expert/explorer/testnet/contract/CC6NAQE3ZHRQV3NPQB3F3NYEFBAMEABA4KQTM6A2V5V7PBR5H3UEU3MW](https://stellar.expert/explorer/testnet/contract/CC6NAQE3ZHRQV3NPQB3F3NYEFBAMEABA4KQTM6A2V5V7PBR5H3UEU3MW)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/README.mdx
deleted file mode 100644
index a2773b36d0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Prácticas recomendadas de seguridad
-sidebar_position: 60
-sidebar_label: Prácticas recomendadas de seguridad
----
-
-import DocCardList from "@theme/DocCardList";
-
-Una serie de guías y documentación para ayudar a los desarrolladores a desarrollar productos seguros en Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/securing-web-based-projects.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/securing-web-based-projects.mdx
deleted file mode 100644
index c6a7065062..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/securing-web-based-projects.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Asegurar proyectos basados en la web
-sidebar_position: 30
----
-
-Cualquier aplicación que gestione criptomonedas es un objetivo frecuente de actores malintencionados y debe seguir las mejores prácticas de seguridad. La siguiente lista de verificación ofrece orientación sobre las vulnerabilidades más comunes. Sin embargo, incluso si sigues todos los consejos, la seguridad no está garantizada. La seguridad web y los actores maliciosos están en constante evolución, por lo que es bueno mantener una saludable dosis de paranoia.
-
-## SSL/TLS
-
-Asegúrate de que TLS esté habilitado. Redirige HTTP a HTTPS donde sea necesario para garantizar que no ocurran ataques Man in the Middle y que los datos sensibles se transfieran de forma segura entre el cliente y el navegador. Habilita TLS y obtén un certificado SSL gratis en [LetsEncrypt](https://letsencrypt.org/getting-started/).
-
-Si no tienes SSL/TLS habilitado, detén todo y haz esto primero.
-
-## Encabezados de política de seguridad de contenido (CSP)
-
-Los encabezados CSP indican al navegador desde dónde puede descargar recursos estáticos. Por ejemplo, si tu sitio es astralwallet.io y solicita un archivo JavaScript desde myevilsite.com, tu navegador lo bloqueará a menos que haya sido incluido en la lista blanca mediante encabezados CSP. Puedes leer cómo implementar los encabezados CSP [aquí](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP).
-
-La mayoría de los frameworks web tienen un archivo de configuración o extensiones para especificar tu política CSP, y los encabezados se generan automáticamente para ti. Por ejemplo, mira [Helmet](https://www.npmjs.com/package/helmet) para Node.js. Esto habría prevenido el [Blackwallet Hack](https://www.ccn.com/yet-another-crypto-wallet-hack-causes-users-lose-400000/).
-
-## Encabezados HTTP strict-transport-security
-
-Este es un encabezado HTTP que indica al navegador que todas las conexiones futuras a un sitio en particular deben usar HTTPS. Para implementarlo, añade el [encabezado](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) a tu sitio web. Algunos frameworks web (como [Django](https://docs.djangoproject.com/en/2.0/topics/security/#ssl-https)) tienen esto incorporado. Esto habría prevenido el [MyEtherWallet DNS Hack](https://bitcoinmagazine.com/articles/popular-ether-wallet-mew-hijacked-dns-attack/).
-
-## Almacenar datos sensibles
-
-Idealmente, no necesitas almacenar muchos datos sensibles. Si debes hacerlo, asegúrate de proceder con cuidado. Existen muchas estrategias para almacenar datos sensibles:
-
-- Asegúrate de que los datos sensibles estén cifrados usando un cifrado probado como AES-256 y almacenados separadamente de los datos de la aplicación. Siempre elige el modo AEAD.
-- Toda comunicación entre el servidor de la aplicación y el servidor secreto debería estar en una red privada y/o autenticada mediante HMAC. Tu estrategia de cifrado cambiará dependiendo de si enviarás el texto cifrado múltiples veces por la red.
-- Haz respaldos offline de cualquier clave de cifrado que uses y guárdalas solo en la memoria de tu aplicación.
-- Consulta a un buen criptógrafo y estudia las mejores prácticas. Consulta la documentación de tu framework web favorito.
-- Crear tu propia criptografía es una mala idea. Usa siempre librerías probadas y testadas como [NaCI](https://en.wikipedia.org/wiki/NaCl_(software)).
-
-## Monitoreo
-
-Los atacantes a menudo necesitan tiempo para explorar tu sitio en busca de comportamientos inesperados o pasados por alto. Examinar los registros defensivamente puede ayudarte a detectar qué intentan lograr. Al menos puedes bloquear su IP o automatizar el bloqueo basado en comportamientos sospechosos.
-
-También vale la pena configurar un reporte de errores (como [Sentry](https://sentry.io/welcome/)). A menudo, las personas desencadenan errores extraños al intentar hackear.
-
-## Debilidades en la autenticación
-
-Debes construir tu autenticación de manera segura si tienes inicios de sesión para usuarios. La mejor forma de hacerlo es usar algo ya disponible. Tanto Ruby on Rails como Django tienen esquemas robustos y incorporados de autenticación.
-
-Muchas implementaciones de JSON web token están mal hechas, así que asegúrate de que la librería que uses esté auditada.
-
-Hashear contraseñas con un esquema probado es bueno. También vale la pena investigar el Balloon Hashing.
-
-Preferimos firmemente 2FA y requerimos 2FA U2F o [TOTP](https://tools.ietf.org/html/rfc6238) para acciones sensibles. El 2FA es importante ya que las cuentas de correo electrónico suelen no ser muy seguras. Tener un segundo factor de autenticación asegura que los usuarios que accidentalmente se queden conectados o cuyo password sea adivinado sigan protegidos.
-
-Finalmente, requiere contraseñas fuertes. Contraseñas comunes y cortas pueden ser forzadas por ataques de fuerza bruta. Dropbox tiene una gran [herramienta de código abierto](https://blogs.dropbox.com/tech/2012/04/zxcvbn-realistic-password-strength-estimation/) que mide la fortaleza de las contraseñas de manera bastante rápida, haciéndola útil para la interactividad con usuarios.
-
-## Ataques de denegación de servicio (DOS)
-
-Los ataques DOS usualmente se logran sobrecargando tus servidores web con tráfico. Para mitigar este riesgo, limita el ritmo de tráfico desde IPs y huellas digitales del navegador. A veces las personas usarán proxies para evadir la limitación de velocidad de IP. Al final, los actores maliciosos siempre pueden encontrar formas de falsificar su identidad, así que la forma más segura de bloquear ataques DOS es implementar verificaciones de prueba de trabajo en tu cliente o usar un servicio gestionado como [Cloudflare](https://www.cloudflare.com/ddos/).
-
-## Bloquea puertos no usados
-
-Los atacantes a menudo escanean tus puertos para ver si fuiste negligente y dejaste alguno abierto. Servicios como Heroku hacen esto por ti- [lee cómo habilitar esto en AWS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html).
-
-## Phishing e ingeniería social
-
-Los ataques de phishing socavan cualquier infraestructura de seguridad bien creada. Ten políticas claras publicadas en tu sitio web y explícalas a los usuarios cuando se registren (nunca pedirás su contraseña, etc.). Firma mensajes a tus usuarios y pídeles que verifiquen el dominio del sitio web en el que están.
-
-## Escanea tu sitio web y las librerías en busca de vulnerabilidades
-
-Usa una herramienta como [Snyk](https://snyk.io/) para escanear las librerías de terceros de tu cliente en busca de vulnerabilidades. Asegúrate de mantener actualizadas tus librerías de terceros. A menudo, las actualizaciones son provocadas por exploits de seguridad. También puedes usar [Mozilla Observatory](https://observatory.mozilla.org/) para comprobar la seguridad HTTP de tu sitio.
-
-## Protección contra Cross-Site Request Forgery (CSRF), inyecciones SQL
-
-La mayoría de los frameworks web y móviles modernos manejan tanto la protección CSRF como las inyecciones SQL. Asegúrate de que la protección CSRF esté habilitada y de usar un ORM de base de datos en lugar de ejecutar SQL sin procesar basado en la entrada del usuario. Por ejemplo, consulta qué dice la [documentación de Ruby on Rails](http://guides.rubyonrails.org/security.html#sql-injection) sobre las inyecciones SQL.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/README.mdx
deleted file mode 100644
index bf6bc78397..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Guía de preparación para la modelación de amenazas
-sidebar_label: Modelación de amenazas
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Esta guía de modelación de amenazas está destinada a los socios del ecosistema Stellar para financiar una auditoría a través del Banco de Auditorías. Este documento está dirigido a los desarrolladores que están listos para auditar su aplicación.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/STRIDE-template.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/STRIDE-template.mdx
deleted file mode 100644
index a330408168..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/STRIDE-template.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-sidebar_position: 30
-title: Plantilla de modelo de amenazas STRIDE
-description: Utiliza esta plantilla para crear un modelo de amenazas STRIDE para tu proyecto.
----
-
-## ¿En qué estamos trabajando?
-
-**Instrucciones**: completa la información a continuación lo mejor que puedas.
-
-_**Texto de entrada**: descripción general del proyecto y lo que se está diseñando_
-
-_Agrega al menos un diagrama visual de flujo de datos que muestre los flujos de proceso entre diferentes entidades en el sistema_
-
-:::note
-
-Si se necesita información adicional para entender el flujo, incluye diagramas o información adicional aquí. El objetivo de esta sección es capturar la documentación necesaria para lograr desarrollar un modelo de amenazas exitoso. Si se descubre más adelante que se requiere información adicional, asegúrate de que la sección “¿En qué estamos trabajando?” se actualice con la información más reciente.
-
-:::
-
-## ¿Qué puede salir mal?
-
-###  recordatorios de STRIDE
-
-| Amenaza mnémica                | Definición                                                                                                                 | Pregunta                                                                                                                                                                                                                                               |
-| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| **Su**plantación               | La capacidad de hacerse pasar por otro usuario o componente del sistema para obtener acceso no autorizado.                 | ¿Es el usuario quien dice ser?                                                                                                                                                                                                                         |
-| **Alteración**                 | Alteración no autorizada de datos o código.                                                                                | ¿Se ha modificado de alguna manera los datos o el código?                                                                                                                                                                                              |
-| **Repudiación**                | La capacidad de un sistema o usuario de negar haber tomado una acción determinada.                                         | ¿Hay suficiente información para "probar" que el usuario tomó la acción si la negara?                                                                                                                                                                  |
-| **Divulgación de información** | El exceso de compartir datos que se espera mantener privados.                                                              | ¿Hay algún lugar donde se compartan datos excesivos o no se implementen controles adecuadamente para proteger la información privada?                                                                                                                  |
-| **Denegación de Servicio**     | La capacidad de un atacante para afectar negativamente la disponibilidad de un sistema.                                    | ¿Puede alguien, sin autorización, impactar en la disponibilidad del servicio o negocio?                                                                                                                                                                |
-| **Elevación de privilegios**   | La capacidad de un atacante para obtener privilegios y roles adicionales más allá de los que inicialmente se le otorgaron. | ¿Hay formas para que un usuario, sin la correcta autenticación (verificación de identidad) y autorización (verificación de permiso) obtenga acceso a privilegios adicionales, ya sea a través de medios normales (normalmente legítimos) o ilegítimos? |
-
-_Para completar la tabla STRIDE a continuación, aplica las preguntas anteriores a cada una de las interacciones en el diagrama de flujo de datos entre diferentes entidades._ Debería haber al menos un problema identificado para cada uno de S, T, R, I, D y E. Asegúrate de identificarlos de manera única, para que sean más fáciles de rastrear en el siguiente paso._
-
-### Tabla de amenazas
-
-| Amenaza                        | Problemas                                                                                      |
-| ------------------------------ | ---------------------------------------------------------------------------------------------- |
-| **Su**plantación               | **Suplantar.1** - _Descripción de al menos un problema de suplantación_                        |
-| **Alteración**                 | **Alterar.1** - _Descripción de al menos un problema de alteración_                            |
-| **Repudiación**                | **Repudiar.1** - _Descripción de al menos un problema de repudiación_                          |
-| **Divulgación de Información** | **Info.1** - _Descripción de al menos un problema de divulgación de información_               |
-| **Denegación de Servicio**     | **Denegación de Servicio.1** - _Descripción de al menos un problema de denegación de servicio_ |
-| **Elevación de privilegios**   | **Elevación.1** - _Descripción de al menos un problema de elevación de privilegios_            |
-
-## ¿Qué vamos a hacer al respecto?
-
-_Para completar la tabla a continuación, diseña o identifica mitigaciones que puedan abordar cada uno de los problemas identificados._ Alternativamente, el riesgo puede ser documentado y aceptado corporativamente por la empresa._
-
-| Amenaza                        | Problemas                                                                                                                                                                                                                                                                                                                                                                                           |
-| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Su**plantación               | **Suplantar.1.R.1** - _Descripción de la primera remediación para este problema._ A menudo, puede haber más de una remediación singular necesaria para abordar completamente un problema. Asegúrate de proporcionar suficiente detalle para mitigar o remediar completamente el problema._ <br /> **Suplantar.1.R.2** - _Segundo paso de remediación para el primer problema de suplantación, etc._ |
-| **Alteración**                 | **Alterar.1.R.1** - _Descripción de la primera remediación para este problema._ A menudo, puede haber más de una remediación singular necesaria para abordar completamente un problema. Asegúrate de proporcionar suficiente detalle para mitigar o remediar completamente el problema._                                                                                                            |
-| **Repudiación**                | **Repudiar.1.R.1** - _Descripción de la primera remediación para este problema._ A menudo, puede haber más de una remediación singular necesaria para abordar completamente un problema. Asegúrate de proporcionar suficiente detalle para mitigar o remediar completamente el problema._                                                                                                           |
-| **Divulgación de Información** | **Info.1.R.1** - _Descripción de la primera remediación para este problema._ A menudo, puede haber más de una remediación singular necesaria para abordar completamente un problema. Asegúrate de proporcionar suficiente detalle para mitigar o remediar completamente el problema._                                                                                                               |
-| **Denegación de Servicio**     | **Denegación de Servicio.1.R.1** - _Descripción de la primera remediación para este problema._ A menudo, puede haber más de una remediación singular necesaria para abordar completamente un problema. Asegúrate de proporcionar suficiente detalle para mitigar o remediar completamente el problema._                                                                                             |
-| **Elevación de privilegios**   | **Elevación.1.R.1** - _Descripción de la primera remediación para este problema._ A menudo, puede haber más de una remediación singular necesaria para abordar completamente un problema. Asegúrate de proporcionar suficiente detalle para mitigar o remediar completamente el problema._                                                                                                          |
-
-## ¿Hicimos un buen trabajo?
-
-- ¿Se ha hecho referencia al diagrama de flujo de datos desde que fue creado?
-
-- ¿El modelo STRIDE descubrió algún nuevo problema de diseño o preocupaciones que no se habían abordado o pensado anteriormente?
-
-- ¿Los tratamientos identificados en la sección “¿Qué vamos a hacer al respecto?” abordaron adecuadamente los problemas identificados?
-
-- ¿Se han encontrado problemas adicionales después del modelo de amenazas?
-
-- ¿Alguna idea o comentarios adicionales sobre el proceso de modelado de amenazas que podrían ayudar a mejorarlo la próxima vez?
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/pizza-restaurant-example.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/pizza-restaurant-example.mdx
deleted file mode 100644
index dbdd438f2b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/pizza-restaurant-example.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-sidebar_position: 40
-sidebar_label: Ejemplo del Modelo de Amenazas STRIDE
-title: Ejemplo del Modelo de Amenazas STRIDE de un Restaurante de Pizza
-description: Ejemplo de modelo de amenazas STRIDE para ayudarte a entender el proceso.
----
-
-## ¿En qué estamos trabajando?
-
-El proyecto que se está revisando es un restaurante de pizza en línea. Para ayudar a que la experiencia sea más atractiva, incluye un componente social donde las personas pueden ver qué pizzas han sido ordenadas y los clientes pueden rastrear su pizza a lo largo del proceso de creación. Por simplicidad, solo se aceptan tarjetas de crédito como forma de pago, solo se utiliza un procesador de pagos, y todas las pizzas se recogen en la tienda (sin entrega). El flujo típico de "camino feliz" incluye:
-
-1. El cliente construye su pizza en el sitio web a partir de una lista de ingredientes.
-2. Cuando termina de construir, el sitio web calcula el precio de la pizza consultando la base de datos.
-3. El cliente ingresa su información de pago en el sitio web y este se conecta al procesador de tarjetas de crédito para procesar el pago.
-4. El pedido de pizza se agrega a la base de datos.
-5. Para el componente social, una vez que el pedido está en la base de datos, también se muestra en la página de inicio del sitio web con el nombre de usuario del usuario.
-6. Los pizzaiolos en la tienda de pizzas consultan la base de datos y comienzan a construir la pizza a través de varias estaciones, incluyendo masa, salsa, queso, ingredientes, horneado y empaque. Un trabajador de pizza está en cada estación.
-7. En cada paso, el pizzaiolo actualiza la base de datos con el progreso actual. A medida que la base de datos se actualiza, el rastreador de pizzas en el sitio web también se actualiza, mostrando el progreso actual y quién ha completado ese paso.
-8. El cliente recoge su pizza una vez que está lista.
-
-![Modelado de Amenazas](/assets/security/threat-modeling.png)
-
-## ¿Qué puede salir mal?
-
-### Recordatorios de STRIDE
-
-| Amenaza mnemotécnica         | Definición                                                                                                                 | Pregunta                                                                                                                                                                                                                                       |
-| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **S**uplantación             | La capacidad de suplantar a otro usuario o componente del sistema para obtener acceso no autorizado.                       | ¿El usuario es quien dice ser?                                                                                                                                                                                                                 |
-| **T**eviceo                  | Alteración no autorizada de datos o código.                                                                                | ¿Se ha modificado de alguna manera el código o los datos?                                                                                                                                                                                      |
-| **R**epudiación              | La capacidad de un sistema o usuario para negar haber realizado una determinada acción.                                    | ¿Hay suficientes datos para "probar" que el usuario tomó la acción si la negara?                                                                                                                                                               |
-| **I**nformación confidencial | El compartir en exceso datos que se espera que se mantengan en privado.                                                    | ¿Hay algún lugar donde se compartan datos excesivos o no se implementen controles adecuados para proteger la información privada?                                                                                                              |
-| **D**enegación de servicio   | La capacidad de un atacante para afectar negativamente la disponibilidad de un sistema.                                    | ¿Puede alguien, sin autorización, impactar la disponibilidad del servicio o negocio?                                                                                                                                                           |
-| **E**levar privilegios       | La capacidad de un atacante para obtener privilegios y roles adicionales más allá de los que inicialmente se le otorgaron. | ¿Hay formas para que un usuario, sin la autenticación adecuada (verificación de identidad) y autorización (verificación de permiso) obtenga acceso a privilegios adicionales, ya sea por medios estándar (normalmente legítimos) o ilegítimos? |
-
-### Tabla de amenazas
-
-| Amenaza                      | Problemas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **S**uplantación             | **Suplantar.1** - (Paso 1) Un atacante podría enviar un pedido como otro usuario. <br /><br /> **Suplantar.2** - (Paso 3) Si la información de la tarjeta de crédito se almacena en el perfil del usuario, se podría enviar automáticamente un pedido de pizza suplantado al procesador de tarjetas de crédito, haciendo que otro usuario pague por el pedido de pizza. <br /><br /> **Suplantar.3** - (Paso 7) Un atacante "dispara" actualizaciones erróneas de pizza al sitio web, erosionando la confianza en los datos y el proceso.                                                           |
-| **T**ampering                | **Alterar.1** - (Paso 2) Un atacante envía su propia consulta inyectando SQL en la consulta de la base de datos. <br /><br /> **Alterar.2** - (Paso 2) Un atacante modifica los valores devueltos de su consulta de precio de pizza y se otorga un descuento. <br /><br /> **Alterar.3** - (Paso 4) Un atacante construye y cotiza una pizza "barata", pero después del pago, envía un pedido mucho más caro. <br /><br /> **Alterar.4** - (Paso 6) Un pizzaiolo modifica un pedido en la estación de otra persona para hacerlo parecer incompetente.                                               |
-| **R**epudiación              | **Repudiar.1** - (Paso 3) Un atacante coloca un pedido pero refuta el cargo de la tarjeta de crédito. <br /><br /> **Repudiar.2** - (Paso 4) Un atacante envía un pedido para otro usuario directamente a la base de datos sin nunca interactuar con el resto del sistema. <br /><br /> **Repudiar.3** - (Paso 4) Se pueden enviar varios pedidos válidos con el mismo token de procesamiento de tarjeta de crédito.                                                                                                                                                                                |
-| **I**nformación confidencial | **Info.1** - (Paso 4) Un atacante cultiva IDs de pedido secuenciales para interactuar con ellos. <br /><br /> **Info.2** - (Paso 2) Un atacante puede consultar más información y acceder a la información de la tarjeta de crédito almacenada. <br /><br /> **Info.3** - (Paso 4) - Un atacante puede cultivar códigos de cupón secuenciales. <br /><br /> **Info.4** - (Paso 5) - Cuando el sitio web se actualiza con el último pedido de pizza, detrás de escena, devuelve todo el pedido de pizza pero solo muestra la pizza. Un atacante puede cultivar PII de la página del pedido de pizza. |
-| **D**enegación de servicio   | **DoS.1** - Un atacante apunta al sitio web para derribarlo. <br /><br /> **DoS.2** - (Paso 1) Un atacante identifica y llama repetidamente al endpoint de la API para crear un nuevo usuario. <br /><br /> **DoS.3** - (Paso 4) Un atacante envía pedidos en masa para bloquear el proceso de pedidos. <br /><br /> **DoS.4** - (Paso 2) Un atacante envía pedidos en masa para bloquear el proceso de precios.                                                                                                                                                                                    |
-| **E**levar privilegios       | **Elevar.1** - Un atacante puede engañar al sitio web de pizza para que muestre la interfaz de administración en el sitio web. <br /><br /> **Elevar.2** - (Paso 6) Un pizzaiolo usa el acceso de su gerente para eliminar pedidos de pizza para que no tenga que hacerlos.                                                                                                                                                                                                                                                                                                                         |
-
-## ¿Qué vamos a hacer al respecto?
-
-| Amenaza                      | Problemas                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| **S**uplantación             | **Suplantar.1** - (Paso 1) Un atacante podría enviar un pedido como otro usuario. <br /> **S1R1** - Asegúrate de que se requiera autenticación adecuada antes de que un visitante del sitio web esté autorizado a enviar un pedido. Asegúrate de que la información de ubicación del perfil de usuario se utilice para la información del pedido. <br /><br /> **Suplantar.2** - (Paso 3) Si la información de la tarjeta de crédito se almacena en el perfil del usuario, se podría enviar automáticamente un pedido de pizza suplantado al procesador de tarjetas de crédito, haciendo que otro usuario pague por el pedido de pizza. <br /> **S2R1** - Asegúrate de que todos los datos necesarios para procesar un pago con tarjeta de crédito no se almacenen juntos en el perfil del cliente. Todos los datos deben estar encriptados en reposo y en tránsito. Una forma de alcanzar el objetivo final sería usar el CCV como solo datos efímeros y capturarlos cada vez que se use la tarjeta de crédito. El CCV nunca debe ser almacenado. <br /><br /> **Suplantar.3** - (Paso 7) Un atacante "dispara" actualizaciones erróneas de pizza al sitio web, erosionando la confianza en los datos y el proceso. <br /> **S3R1** - Asegúrate de que las actualizaciones de los estados de pizza se realicen a través de un estilo PULL donde el sitio web consulta un servidor en el que confía para obtener actualizaciones del estado de la pizza. <br /> **S3R2** - Alternativamente, permitir actualizaciones de estilo PUSH del servidor de pizza, pero solo exponer ese endpoint de API internamente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| **T**ampering                | **Alterar.1** - (Paso 2) Un atacante envía su propia consulta inyectando SQL en la consulta de la base de datos. <br /> **T1R1** - Asegúrate de que todas las consultas para todas las búsquedas en la base de datos que utilicen datos de usuarios no confiables se realicen con declaraciones preparadas y que todas las entradas estén correctamente codificadas. <br /><br /> **Alterar.2** - (Paso 2) Un atacante modifica los valores devueltos de su consulta de precio de pizza y se otorga un descuento. <br /> **T2R1** - La información de precios devuelta por el servidor de la base de datos solo debe usarse con fines de visualización. El precio debe calcularse en el servidor por separado cuando se aplique el cargo, y la información de seguimiento financiero solo debe confiar en el pedido de pizza específico que sea personalizado. Todos los cálculos para el precio deben realizarse por separado en el back-end. <br /><br /> **Alterar.3** - (Paso 4) Un atacante construye y cotiza una pizza "barata", pero después del pago, envía un pedido mucho más caro. <br /> **T3R1** - El pedido de pizza que se estableció un precio debería hacerse directamente desde el servidor de la base de datos hasta el procesador de tarjeta de crédito. Esto previene cotizar una pizza pero ordenar otra. <br /><br /> **Alterar.4** - (Paso 6) Un pizzaiolo modifica un pedido en la estación de otra persona para hacerlo parecer incompetente. <br /> **T4R1** - Este es un tipo de ataque de "amenaza interna". Cada pizzaiolo debería tener una forma de autenticarse en su estación, de modo que todas las acciones sean rastreables y auditable. Un enfoque podría ser que cada pizzaiolo tuviera una tarjeta de acceso que lo autentique en su estación de pizza. La tarjeta de acceso debe estar conectada al pizzaiolo, de tal manera que si se va, la tarjeta se elimine automáticamente. La tarjeta de acceso debe estar presente para que se puedan enviar cambios al servidor de base de datos.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| **R**epudiación              | **Repudiar.1** - (Paso 3) Un atacante coloca un pedido pero refuta el cargo de la tarjeta de crédito. <br /> **R1R1** - Asegúrate de que cuando se crea un nuevo perfil de usuario, se genere un par de claves públicas/privadas. Estas deben usarse para firmar y validar mensajes entre el usuario y el servidor. Cuando se envía un pedido de pizza al servidor, este calcula el hash del pedido junto con una sal secreta y devuelve el hash salado al usuario original. El usuario original firma el hash salado con su clave privada y envía el paquete firmado de vuelta al servidor. El servidor debe almacenar el pedido, la sal secreta (a través de persistencia en el entorno de proceso), el hash salado y el paquete firmado. Si un usuario refuta el pedido, el servidor puede verificar simplemente que la clave pública del usuario descifra correctamente el paquete firmado. <br /><br /> **Repudiar.2** - (Paso 4) Un atacante envía un pedido para otro usuario directamente a la base de datos sin nunca interactuar con el resto del sistema. <br /> **R2R1** - Asegúrate de que las presentaciones de pedidos requieran un token de sesión JWT activo. Asegúrate de que el tiempo de espera de la sesión refleje los patrones reales de uso esperados (no se tarda 7 horas en pedir una pizza). <br /> **R2R2** - Asegúrate de que un pedido de pizza haya sido correctamente cotizado al recalcular el precio de la pizza en el momento de la presentación. <br /><br /> **Repudiar.3** - (Paso 4) Se pueden presentar múltiples pedidos válidos con el mismo token de procesamiento de tarjeta de crédito. <br /> **R3R1** - Asegúrate de que los tokens de procesamiento de tarjetas de crédito sean lo suficientemente efímeros. <br /> **R3R2** - Trabaja con el procesador de tarjetas de crédito para invalidar el token después de que se confirme la transacción.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| **I**nformación confidencial | **Info.1** - (Paso 4) Un atacante cultiva IDs de orden secuenciales para interactuar con ellos. <br /> **I1R1** - Asegúrate de que todos los IDs (IDs de pedidos, IDs de usuarios, IDs de transacciones, etc.) utilicen GUIDs no secuenciales y difíciles de adivinar. <br /><br /> **Info.2** - (Paso 2) Un atacante puede consultar más información y acceder a la información de la tarjeta de crédito almacenada. <br /> **I2R1** - Utiliza un marco de filtrado como CASL para limitar qué información está disponible a través de consultas. <br /> **I2R2** - Asegúrate de que la información de la tarjeta de crédito se almacene en un contexto separado y no sea de fácil acceso (se segmenta la red para permitir que solo acciones específicas conocidas lleguen al entorno de la tarjeta de crédito). <br /> **I2R3** - Asegúrate de que se utilice la tokenización para ofuscar la información de la tarjeta de crédito. Un ejemplo podría ser el siguiente: <br /> 1. El usuario envía su pedido y se lleva a cabo el proceso de firma. <br /> 2. El sitio web solicita al usuario su CVV y lo envía al servidor de la base de datos. <br /> 3. El servidor de la base de datos luego envía el precio del pedido que han confirmado junto con un CVV y un identificador de número de tarjeta de crédito al endpoint de la API para enviar una solicitud de pago. <br /> 4. La llamada a la API de la solicitud de pago envía una solicitud de pago al procesador de tarjetas de crédito. <br /> 5. Cuando se devuelve el éxito, la llamada de la API se resuelve como pagada. <br /><br /> Este método nunca expone la tarjeta de crédito al servidor de la base de datos o al servidor web. <br /><br /> **Info.3** - (Paso 4) - Un atacante puede cultivar códigos de cupón secuenciales. <br /> **I3R1** - Asegúrate de que los códigos de cupón no sean secuenciales. <br /> **I3R2** - Alternativamente, si la disponibilidad del código de cupón es más importante (es decir, se utiliza para atraer tráfico y hay poca preocupación por la seguridad), asegúrate de incluir el precio de descuento en los modelos de proyección de costos. Además, considera establecer un número máximo de cupones a utilizar para proporcionar un límite superior para los costos en caso de abuso. <br /><br /> **Info.4** - (Paso 5) - Cuando el sitio web se actualiza con el pedido de pizza más reciente, tras bambalinas, devuelve todo el pedido de pizza pero solo muestra la pizza. Un atacante puede obtener PII de la página del pedido de pizza. <br /> **I4R1** - Asegúrate de que la consulta utilizada para presentar los datos en la página del pedido de pizza solo devuelva los datos estrictamente necesarios para llevar a cabo la actualización en la página de estado en contexto. Si la dirección, el correo electrónico o el número de CC no son necesarios para llevar a cabo la actualización del estado de una pizza, no incluyas esos campos en la consulta. |
-| **D**enegación de Servicio   | **DoS.1** - Un atacante apunta al sitio web para derribarlo. <br /> **D1R1** - Asegúrate de que el sitio web siga alguna estrategia de mitigación para la protección contra DDoS. Esto podría incluir CloudFlare DDoS, Cloudflare WAF, F5 DDoS Mitigation, u otros. <br /> **D1R2** - Como alternativa o adicional, se debe aplicar limitación de tasa a nivel del servidor para limitar la capacidad de imponer un ataque DDoS. <br /><br /> **DoS.2** - (Paso 1) Un atacante identifica y llama repetidamente al punto final de la API para crear un nuevo usuario. <br /> **D2R1** - Configura limitación de tasa para llamadas sensibles a la API (como esta). Asegúrate de que CAPTCHA u otras prevenciones contra bots estén en su lugar para dificultar el acceso. <br /><br /> **DoS.3** - (Paso 4) Un atacante envía pedidos masivos para bloquear el proceso de pedido. <br /> **D3R1** - Configura Cloudflare DDoS y Cloudflare WAF. <br /> **D3R2** - Configura limitación de tasa para la llamada a la API para enviar pedidos. <br /> **D3R3** - Configura encabezados X-Forwarded-For en el servidor para habilitar la limitación de tasa por IP de origen. <br /> **D3R4** - Configura limitación de tasa por IP. <br /> **D3R5** - Asegúrate de que el sitio web pueda identificar grandes cantidades de pedidos de un solo usuario y limitarlo a un valor apropiado. <br /><br /> **DoS.4** - (Paso 2) Un atacante envía pedidos masivos para bloquear el proceso de precios. <br /> **D4R1** - Las mismas mitigaciones se aplican aquí que para DoS.3. <br /> **D4R2** - Además, asegúrate de que el sistema de precios también identifique grandes cantidades de búsquedas de precios o re-búsquedas de precios procedentes de las mismas IPs.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| **E**levar privilegio        | **Elevación.1** - Un atacante puede engañar al sitio web de pizza para que muestre la interfaz de administración en el sitio web. <br /> **E1R1** - Asegúrate de que la interfaz administrativa del sitio web se presente en una URI diferente. <br /> **E1R2** - Asegúrate de que la invocación de tareas sensibles o administrativas sea realizada por administradores identificados a partir de una búsqueda de la sesión del usuario en el servidor. <br /><br /> **Elevación.2** - (Paso 6) Un pizzero utiliza el acceso de su gerente para eliminar pedidos de pizza para no tener que hacerlos. <br /> **E2R1** - Asegúrate de que la tarjeta clave que otorga acceso no esté desatendida sin el gerente presente.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-
-## ¿Hicimos un buen trabajo?
-
-- ¿Se ha referenciado el diagrama de flujo de datos desde que fue creado?
-  - Sí, fue invaluable en la construcción del perfil de amenaza.
-
-- ¿El modelo STRIDE descubrió algún nuevo problema o preocupación de diseño que no había sido abordado o pensado anteriormente?
-  - Sí. Nos dimos cuenta de que necesitábamos cambiar el esquema de autenticación de la estación de pizza. Además, reformulamos las consultas para la exhibición social del pedido de pizza para entregar solo la información necesaria.
-
-- ¿Los tratamientos identificados en la sección "¿Qué vamos a hacer al respecto?" abordaron adecuadamente los problemas identificados?
-  - Sí. Estamos continuando monitoreando estos en caso de que se necesiten mitigaciones adicionales.
-
-- ¿Se han encontrado problemas adicionales después del modelo de amenaza?
-  - Aún ninguno. A medida que se agreguen nuevas características, el modelo de amenaza se actualizará para reflejar las nuevas adiciones.
-
-- ¿Algún pensamiento o perspectiva adicional sobre el proceso de modelado de amenazas que podría ayudar a mejorarlo la próxima vez?
-  - Ninguno.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/threat-modeling-description.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/threat-modeling-description.mdx
deleted file mode 100644
index 2203cdbb7b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/threat-modeling-description.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-sidebar_position: 10
-sidebar_label: ¿Qué es la Modellación de Amenazas?
-title: Preparación para la Modellación de Amenazas
-description: La modellación de amenazas es un proceso de identificación de amenazas de seguridad potenciales para un sistema o aplicación, analizando esas amenazas y luego desarrollando estrategias para mitigar o prevenirlas.
----
-
-Este documento explica los procesos de modellación de amenazas considerados como prácticas recomendadas de la industria y que ahora son requeridos como condición previa para las auditorías solicitadas al SDF Audit Bank.
-
-**Antecedentes:** Completar la serie de YouTube de 15 minutos "El Curso de Modellación de Amenazas Más Corto del Mundo" [aquí](https://www.youtube.com/playlist?list=PLCVhBqLDKoOOZqKt74QI4pbDUnXSQo0nf).
-
-**Antecedentes:** Como mínimo, será útil tener un diseño de procedimiento o un diagrama de flujo de datos que documente, con suficiente detalle, el flujo de datos a través del sistema que se va a auditar.
-
-### ¿Qué es la modellación de amenazas?
-
-La modellación de amenazas proporciona una manera estructurada de pensar críticamente sobre los flujos de datos, límites de confianza y procesos internos para el software. Efectivamente, la modellación de amenazas proporciona una forma guiada de pensar sobre las implicaciones de seguridad de las decisiones de diseño y puede ayudar a descubrir amenazas de seguridad o problemas de diseño previamente no identificados o no visibles.
-
-### ¿Por qué es importante la modellación de amenazas?
-
-La modellación de amenazas proporciona un marco y un espacio para pensar críticamente sobre el software que se está diseñando o desarrollando. Al aprovechar completamente los beneficios que proporciona la modellación de amenazas, se pueden identificar amenazas de seguridad y problemas de diseño más temprano en el ciclo de vida del desarrollo, lo que resulta en un código más limpio y seguro cuando los usuarios comienzan a interactuar con él. Al identificar incidencias más temprano en el proceso de desarrollo, se reduce el costo del retrabajo, lo que permite un uso más eficiente de los recursos. Los desarrolladores del ecosistema que han abordado adecuadamente las ideas obtenidas de la modellación de amenazas se beneficiarán de resultados de auditoría más profundos y valiosos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/threat-modeling-how-to.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/threat-modeling-how-to.mdx
deleted file mode 100644
index 3ebd97cf67..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/security-docs/threat-modeling/threat-modeling-how-to.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-sidebar_position: 20
-sidebar_label: Guía paso a paso
-title: Guía paso a paso sobre modelado de amenazas
-description: Cómo realizar un ejercicio de modelado de amenazas para tu proyecto.
----
-
-## ¿Cómo modelamos amenazas?
-
-El modelado de amenazas, en su esencia, trata realmente de hacer cuatro preguntas simples:
-
-1. ¿En qué estamos trabajando?
-2. ¿Qué puede salir mal?
-3. ¿Qué vamos a hacer al respecto?
-4. ¿Hicimos un buen trabajo?
-
-### Cómo responder: “¿En qué estamos trabajando?”
-
-La esencia de esta pregunta es la documentación. Más específicamente, esta pregunta guía al equipo de desarrollo para que comience a pensar en (y documentar) los procesos centrales que se están desarrollando en términos de procesos, flujos de datos, almacenamiento de datos, áreas de control e identificación de lugares donde se están haciendo suposiciones de confianza entre los sistemas y procesos. La respuesta a “¿En qué estamos trabajando?” debe incluir una descripción verbal del caso de uso para la aplicación y un diagrama de flujo de datos que muestre:
-
-- Entidades externas
-  - Entidades fuera del control de la aplicación o empresa.
-- Procesos
-  - Código y sistemas bajo el control de la aplicación o empresa.
-- Flujos de datos
-  - Representación de datos que se mueven de un sistema a otro.
-- Almacenamiento de datos
-  - Representación de datos almacenándose en algún lugar (esto puede incluir el almacenamiento de contratos inteligentes de Stellar (Soroban), bases de datos en línea, servidores de archivos, etc.).
-- Límites de confianza
-  - Esbozar y agrupar áreas donde las interacciones entre sistemas generan o incluyen suposiciones de confianza. Por ejemplo, en un flujo de datos donde un usuario envía datos en una página web y se procesan en el backend, un límite de confianza debería abarcar el proceso de backend, ya que los datos pueden ser enviados al backend fuera de cualquier control de filtrado en el frontend.
-
-### Cómo responder: “¿Qué puede salir mal?”
-
-Comprender el caso de uso y el flujo de datos de “¿En qué estamos trabajando?” puede informar en gran medida el pensamiento sobre lo que puede salir mal. Sin embargo, para garantizar la coherencia y exhaustividad en la revisión, es útil seguir un marco que ayude a guiar el pensamiento en torno a amenazas y lo que puede salir mal. La Stellar Development Foundation (SDF) sigue el modelo STRIDE. Descrito a continuación, el modelo STRIDE ayuda a proporcionar un marco coherente para garantizar modelos de amenazas de alta calidad.
-
-Para cada uno de los acrónimos S, T, R, I, D y E en la tabla a continuación, asegúrate, como mínimo, de identificar al menos una incidencia. A menudo, habrá múltiples incidencias para cada amenaza. Es útil identificar cada incidencia con un identificador que indique tanto la amenaza con la que está conectada como su número. Dado que puede haber múltiples incidencias de suplantación, por ejemplo, puede ser útil identificar las incidencias como Spoof.1, Spoof.2, y así sucesivamente. Para flujos de datos especialmente complejos, incluso puede ser beneficioso aplicar un modelo STRIDE completo a un subproceso en el flujo. Asegúrate de que tu identificación pueda diferenciar entre estos también.
-
-|                            | Definición                                                                                                                                                                                                    | Pregunta a hacer                                                                                                                         | Ejemplo                                                                                                                  |
-| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| **S**uplantación           | La suplantación es la capacidad de un atacante para pretender ser alguien que no es, a menudo aprovechando vacíos en la verificación del usuario final en sistemas posteriores.                               | ¿Podría la acción que se está realizando ser inducida por alguien que no es la persona que se cree que tomó la acción?                   | Llamar y pedir pizza pretendiendo ser otra persona.                                                                      |
-| **T**ampering              | La manipulación es la capacidad de un atacante para modificar datos que se están enviando o enviando para tener un efecto diferente al que se anticipó.                                                       | ¿Podría haber sido modificado de alguna manera la solicitud para tomar una acción diferente a la originalmente prevista?                 | Un error de software cambia todos los ingredientes de pizza seleccionados a “queso.”                                     |
-| **R**epudio                | El repudio es la capacidad de un usuario para afirmar que no tomó la acción que se tomó.                                                                                                                      | ¿Puede el usuario “refutar” la acción, afirmando que no la tomó?                                                                         | El usuario afirma que nunca pidió la pizza que pidió.                                                                    |
-| **I**nformación revelada   | La divulgación de información es el exceso de compartir datos que se espera que se mantengan en privado.                                                                                                      | ¿Hay áreas donde se está compartiendo más información o información limitada se comparte con más personas de lo estrictamente necesario? | La empresa de pizzas muestra el pedido de pizza más reciente, nombre y número de teléfono en su página web.              |
-| **D**enegación de servicio | La denegación de servicio es la capacidad de un atacante para afectar negativamente la disponibilidad de un sistema.                                                                                          | ¿Hay alguna parte de la aplicación que sea susceptible de ser sobrecargada o completamente inhabilitada debido a una demanda excesiva?   | La empresa de pizzas tiene una única línea telefónica que solo devuelve ocupado cuando se llama mientras está en uso.    |
-| **E**levar privilegios     | La elevación de privilegios se refiere a la capacidad de un atacante para obtener privilegios y roles adicionales más allá de los que se le otorgaron inicialmente, ya sea por medios legítimos o ilegítimos. | ¿Puede alguien obtener privilegios adicionales sin la debida autenticación y autorización?                                               | El pizzero inicia sesión en el ordenador con la tarjeta de su jefe y elimina el pedido para no tener que hacer la pizza. |
-
-### Cómo responder: “¿Qué vamos a hacer al respecto?”
-
-Para cada incidencia identificada en el modelo STRIDE, piensa en las formas en que puede suceder y identifica un “tratamiento” o forma de abordar la incidencia. Las respuestas aquí deben ser detalladas en cómo la incidencia abordará la amenaza identificada. Esto podría incluir bloques de código que detallen los cambios o descripciones verbales de cómo se abordará la incidencia.
-
-### Cómo responder: “¿Hicimos un buen trabajo?”
-
-El objetivo de esta sección es entender si el análisis realizado durante las otras secciones fue lo suficientemente profundo y amplio como para proporcionar valor. Algunas preguntas a hacer y responder aquí podrían incluir:
-
-- **¿Se ha consultado el diagrama de flujo de datos desde que fue creado?**
-  - Si es así, felicidades, has creado una herramienta reutilizable que puede seguir agregando valor.
-  - Si no, puede que sea necesario más detalle o una mejor organización. El diagrama de flujo de datos debe ser una herramienta útil que se consulte regularmente.
-
-- **¿El modelo STRIDE descubrió alguna nueva incidencia o preocupación de diseño que no se haya abordado o considerado previamente?**
-  - Si es así, ¡excelente! El modelo STRIDE debe ayudar a orientar el pensamiento hacia incidencias de seguridad que quizá no se pensaron durante la fase inicial de diseño.
-  - Si no, asegúrate de tener al menos una incidencia para cada amenaza. Presta especial atención a los límites de confianza y a los procesos que manejan datos sensibles o realizan acciones particularmente poderosas.
-
-- **¿Las medidas identificadas en la sección “¿Qué vamos a hacer al respecto?” abordaron adecuadamente las incidencias identificadas?**
-  - Si es así, ¡excelente! El ejercicio de modelado de amenazas ha ayudado a desarrollar una aplicación más segura.
-  - Si no, querrás proporcionar mayor detalle y reflexión sobre cómo responder a las incidencias identificadas.
-
-- **¿Se han encontrado incidencias adicionales después del modelo de amenazas?**
-  - Si es así, ¡excelente! El modelo de amenazas es una herramienta en vivo que debe rehacerse cada vez que haya cambios significativos en la arquitectura. Durante la fase de diseño de estos cambios o incorporaciones, asegúrate de analizar el sistema con los cambios recién diseñados para identificar nuevas posibles incidencias tanto en los nuevos cambios como en la interfaz con el sistema antiguo.
-  - Si no, continúa refinando tu modelo de amenazas y diseño conforme se conozca nueva información sobre el sistema. El modelo de amenazas es una herramienta en vivo que puede seguir aportando beneficios conforme se conoce nueva información sobre el sistema.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/README.mdx
deleted file mode 100644
index 47e4ef3bdc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Crear, Probar y Desplegar Contratos Inteligentes en Stellar: Herramientas y Prácticas Recomendadas"
-sidebar_position: 20
-sidebar_label: Desarrollar contratos inteligentes
-description: Aprende cómo crear, probar, desplegar y gestionar contratos inteligentes en la red Stellar. Explora prácticas recomendadas, herramientas, guías y contratos de ejemplo para el desarrollo.
----
-
-# Escribir Contratos Inteligentes
-
-import DocCardList from "@theme/DocCardList";
-
-Esta sección te guiará a través de cómo configurarte para escribir contratos inteligentes en Stellar, además de una introducción a las pruebas, el almacenamiento de datos y el despliegue de tus contratos. También proporciona una variedad de contratos de ejemplo para usar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/README.mdx
deleted file mode 100644
index 7c54f99f8d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: "Ejemplos de contratos inteligentes: Aprende, Desarrolla, Prueba y Despliega en la red"
-sidebar_label: Ejemplos de contratos
-description: Explora ejemplos de contratos inteligentes para aprender conceptos clave, desde funciones básicas hasta casos de uso avanzados. Desarrolla, prueba y despliega contratos en la red Stellar.
-sidebar_position: 30
-hide_table_of_contents: true
----
-
-# Contratos de ejemplo
-
-import DocCardList from "@theme/DocCardList";
-
-El equipo de Stellar ha reunido una gran colección de [ejemplos de contratos] para demostrar el uso de contratos inteligentes en Stellar. Para muchos de estos ejemplos de contratos, hemos escrito un tutorial acompañante que te guiará a través del ejemplo de contrato y describirá un poco más sobre su diseño.
-
-Los ejemplos listados a continuación se proporcionan de manera secuencial. Los primeros ejemplos de contratos listados crean una base sólida de conceptos que serán requeridos durante los ejemplos posteriores. Si bien eres completamente libre de elegir, leer y usar cualquiera de los ejemplos de contratos que desees, ten en cuenta que el orden que ves es intencional.
-
-<DocCardList />
-
-[ejemplos de contratos]: https://github.com/stellar/soroban-examples
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/TEMPLATE.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/TEMPLATE.mdx
deleted file mode 100644
index f646426d26..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/TEMPLATE.mdx
+++ /dev/null
@@ -1,183 +0,0 @@
----
-title: Plantilla de Tutorial
-description: Una descripción del tutorial que se está escribiendo.
-draft: true
-sidebar_position: 1000
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-Nota rápida sobre lo que este [ejemplo demuestra]. Quizás también se base en algún [otro ejemplo].
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-:::tip
-
-Coloca cada definición de enlace al final de la sección en la que se utiliza por primera vez.
-
-:::
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo demuestra]: https://github.com/stellar/soroban-examples/tree/v23.0.0/hello_world
-[otro ejemplo]: ../getting-started/setup.mdx
-
-## Ejecutar el Ejemplo
-
-Primero realiza el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere]
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `hello_world`, y usa `cargo test`.
-
-```sh
-cd hello_world
-cargo test
-```
-
-Deberías ver la salida:
-
-```sh
-running 1 test
-test test::test ... ok
-```
-
-[configuración]: ../getting-started/setup.mdx
-
-## Código
-
-```rust title="hello_world/src/lib.rs"
-#![no_std]
-use soroban_sdk::{contractimpl, vec, Env, Symbol, Vec};
-
-pub struct HelloContract;
-
-#[contractimpl]
-impl HelloContract {
-    pub fn hello(env: Env, to: Symbol) -> Vec<Symbol> {
-        vec![&env, Symbol::short("Hello"), to]
-    }
-}
-
-mod test;
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/hello_world
-
-## Cómo Funciona
-
-Esta es la parte escrita de cada guía. Puedes destacar cada cosa única de este contrato, a veces haciendo referencia a otros conceptos importantes de otros contratos de ejemplo, también.
-
-### Conceptos Principales
-
-Podrías agregar subtítulos para resaltar aún más partes o conceptos importantes que conocer. La guía de ejemplo `events` tiene los siguientes encabezados `h3`:
-
-- Temas de Eventos
-- Datos de Eventos
-- Publicación
-
-Debajo de cada uno de esos encabezados hay una breve discusión sobre cómo ese concepto se relaciona con el código de contrato de ejemplo.
-
-## Pruebas
-
-Abre el archivo [`/hello_world/src/test.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/hello_world/src/test.rs) para seguir el ejemplo.
-
-```rust title="hello_world/src/test.rs"
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(HelloContract, ());
-    let client = HelloContractClient::new(&env, &contract_id);
-
-    let words = client.hello(&String::from_str(&env, "Dev"));
-    assert_eq!(
-        words,
-        vec![
-            &env,
-            String::from_str(&env, "Hello"),
-            String::from_str(&env, "Dev"),
-        ]
-    );
-}
-```
-
-Puedes describir lo que está sucediendo en la prueba anterior aquí. Algunas cosas probablemente serán las mismas de una guía a otra. Parece que, en particular, el siguiente fragmento se comparte entre varios de ellos:
-
-{/* INICIO del fragmento compartido */}
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno de Soroban en el que se ejecutará el contrato.
-
-```rust
-let env = Env::default();
-```
-
-El contrato se registra con el entorno utilizando el tipo de contrato.
-
-```rust
-let contract_id = env.register(IncrementContract, ());
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente se nombrará igual que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato el tipo de contrato es `Contract`, y el cliente se llama `ContractClient`.
-
-{/* FIN del fragmento compartido */}
-
-Luego puedes describir las complejidades de lo que hace tu prueba de contrato de manera única.
-
-## Crear el Contrato
-
-Para crear el contrato, utiliza el comando `cargo build`.
-
-```sh
-cargo build --target wasm32v1-none --release
-```
-
-Un archivo `.wasm` debería generarse en el directorio `target`:
-
-```
-target/wasm32v1-none/release/soroban_hello_world_contract.wasm
-```
-
-## Ejecutar el Contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar funciones del contrato usando esto.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --wasm target/wasm32v1-none/release/soroban_hello_world_contract.wasm \
-    --id 1 \
-    -- \
-    hello \
-    --to Soroban
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --wasm target/wasm32v1-none/release/soroban_hello_world_contract.wasm `
-    --id 1 `
-    -- `
-    hello `
-    --to Soroban
-```
-
-</TabItem>
-</Tabs>
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
-
-## Lectura Adicional
-
-Si tienes algunos enlaces adicionales para compartir o conocimiento de fondo al que puedes vincular, este es el lugar para compartirlo. O, quizás quieras señalar cuán similar o diferente es este ejemplo en comparación con otros ejemplos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/alloc.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/alloc.mdx
deleted file mode 100644
index 55d1abf2cc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/alloc.mdx
+++ /dev/null
@@ -1,132 +0,0 @@
----
-title: Asignador
-description: Utiliza la función de asignador para emular la memoria heap en un contrato inteligente.
-sidebar_position: 80
----
-
-<head>
-  <title>
-    {`Utiliza la función de asignador para emular la memoria heap en un contrato inteligente.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Utiliza la función de asignador para emular la memoria heap en un contrato inteligente."
-  />
-  <meta
-    property="og:description"
-    content="Utiliza la función de asignador en el SDK. El asignador liviano de punteros de aumento se puede usar para emular la asignación de memoria heap en un contrato inteligente Wasm."
-  />
-</head>
-
-El [ejemplo de asignador] demuestra cómo utilizar la función de asignador al escribir un contrato.
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de asignador]: https://github.com/stellar/soroban-examples/tree/v23.0.0/alloc
-
-El crate `soroban-sdk` proporciona un asignador liviano de punteros de aumento que se puede usar para emular la asignación de memoria heap en un contrato inteligente Wasm.
-
-## Ejecutar el Ejemplo
-
-Primero, sigue el proceso de [Configuración] para configurar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `alloc`, y usa `cargo test`.
-
-```sh
-cd alloc
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test ... ok
-```
-
-## Dependencias
-
-Este ejemplo depende de la función `alloc` en `soroban-sdk`. Para incluirlo, añade "alloc" a la lista de "features" de `soroban-sdk` en el archivo `Cargo.toml`:
-
-```rust title="alloc/Cargo.toml"
-[dependencies]
-soroban-sdk = { version = "23.0.1", features = ["alloc"] }
-
-[dev_dependencies]
-soroban-sdk = { version = "23.0.1", features = ["testutils", "alloc"] }
-```
-
-## Código
-
-```rust title="alloc/src/lib.rs"
-#![no_std]
-use soroban_sdk::{contract, contractimpl, Env};
-
-extern crate alloc;
-
-#[contract]
-pub struct AllocContract;
-
-#[contractimpl]
-impl AllocContract {
-    /// Allocates a temporary vector holding values (0..count), then computes and returns their sum.
-    pub fn sum(_env: Env, count: u32) -> u32 {
-        let mut v1 = alloc::vec![];
-        (0..count).for_each(|i| v1.push(i));
-
-        let mut sum = 0;
-        for i in v1 {
-            sum += i;
-        }
-
-        sum
-    }
-}
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/alloc
-
-## Cómo Funciona
-
-```rust
-extern crate alloc;
-```
-
-Importa el crate `alloc`, que es necesario para admitir la asignación bajo `no_std`. Consulta [Dialecto Rust de Contrato] para más información sobre `no_std`.
-
-[dialecto rust del contrato]: ../../../learn/fundamentals/contract-development/rust-dialect.mdx
-
-```rust
-let mut v1 = alloc::vec![];
-```
-
-Crea un arreglo contiguo y de tamaño creciente `v1` con contenidos asignados en la memoria heap.
-
-:::info
-
-La memoria heap en el contexto de un contrato inteligente se refiere en realidad a la memoria lineal Wasm. The `alloc` will use the global allocator provided by the soroban sdk to interact with the linear memory.
-
-:::
-
-:::caution
-
-Usar un arreglo asignado en la memoria heap suele ser lento y costoso en términos computacionales. Intenta evitarlo y, en su lugar, usa un arreglo de tamaño fijo o `soroban_sdk::vec!` siempre que sea posible.
-
-Este es especialmente el caso para un arreglo de gran tamaño. Cada vez que el tamaño del arreglo crece más allá del tamaño actual de la memoria lineal, que es múltiplo del tamaño de la página (64KB), se invoca [`wasm32::memory_grow`](https://doc.rust-lang.org/core/arch/wasm32/fn.memory_grow.html) para aumentar la memoria lineal por más páginas según sea necesario, lo cual es muy costoso en computación.
-
-:::
-
-El código restante empuja valores `(0..count)` a `v1`, luego calcula y devuelve su suma. Este es el ejemplo más simple para ilustrar cómo utilizar el asignador.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/atomic-multi-swap.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/atomic-multi-swap.mdx
deleted file mode 100644
index b91e2c8f28..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/atomic-multi-swap.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Intercambios Atómicos por Lotes
-description: Intercambiar un par de tokens entre grupos de usuarios autorizados.
-sidebar_position: 100
----
-
-<head>
-  <title>Intercambiar un par de tokens entre grupos de usuarios autorizados.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Intercambiar un par de tokens entre grupos de usuarios autorizados."
-  />
-  <meta
-    property="og:description"
-    content="Intercambiar un par de tokens entre dos grupos de usuarios que autorizaron la operación de intercambio."
-  />
-</head>
-
-El [ejemplo de agrupación de intercambios atómicos] intercambia un par de tokens entre los dos grupos de usuarios que autorizaron la operación de `intercambio` del ejemplo de [Intercambio Atómico].
-
-Este contrato básicamente agrupa los múltiples intercambios mientras sigue algunas reglas simples para igualar a los participantes del intercambio.
-
-Sigue los comentarios en el código para más información.
-
-[abrir-en-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[abrir-en-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[intercambio atómico]: atomic-swap.mdx
-[ejemplo de agrupación de intercambios atómicos]: https://github.com/stellar/soroban-examples/tree/v23.0.0/atomic_multiswap
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/atomic-swap.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/atomic-swap.mdx
deleted file mode 100644
index 316d967d99..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/atomic-swap.mdx
+++ /dev/null
@@ -1,265 +0,0 @@
----
-title: Intercambio Atómico
-description: Intercambiar tokens atómicamente entre usuarios autorizados.
-sidebar_position: 90
----
-
-<head>
-  <title>Intercambiar tokens atómicamente entre usuarios autorizados.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Intercambiar tokens atómicamente entre usuarios autorizados."
-  />
-  <meta
-    property="og:description"
-    content="Intercambiar dos tokens entre dos partes autorizadas atómicamente usando el marco de autenticación; el precio mínimo solicitado debe ser respetado por ambas partes."
-  />
-</head>
-
-El [ejemplo de intercambio atómico] intercambia dos tokens entre dos partes autorizadas atómicamente mientras sigue los límites que establecen.
-
-Este ejemplo demuestra el uso avanzado del marco de autenticación de Soroban y asume que el lector está familiarizado con el [ejemplo de autenticación](../example-contracts/auth.mdx) y con el uso de token de Soroban.
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de intercambio atómico]: https://github.com/stellar/soroban-examples/tree/v23.0.0/atomic_swap
-
-## Ejecutar el Ejemplo
-
-Primero completa el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, salta la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo usa `cargo test`.
-
-```sh
-cargo test -p soroban-atomic-swap-contract
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test_atomic_swap ... ok
-```
-
-## Código
-
-```rust title="atomic_swap/src/lib.rs"
-#[contract]
-pub struct AtomicSwapContract;
-
-#[contractimpl]
-impl AtomicSwapContract {
-    // Swap token A for token B atomically. Settle for the minimum requested price
-    // for each party (this is an arbitrary choice; both parties could have
-    // received the full amount as well).
-    pub fn swap(
-        env: Env,
-        a: Address,
-        b: Address,
-        token_a: Address,
-        token_b: Address,
-        amount_a: i128,
-        min_b_for_a: i128,
-        amount_b: i128,
-        min_a_for_b: i128,
-    ) {
-        // Verify preconditions on the minimum price for both parties.
-        if amount_b < min_b_for_a {
-            panic!("not enough token B for token A");
-        }
-        if amount_a < min_a_for_b {
-            panic!("not enough token A for token B");
-        }
-        // Require authorization for a subset of arguments specific to a party.
-        // Notice, that arguments are symmetric - there is no difference between
-        // `a` and `b` in the call and hence their signatures can be used
-        // either for `a` or for `b` role.
-        a.require_auth_for_args(
-            (token_a.clone(), token_b.clone(), amount_a, min_b_for_a).into_val(&env),
-        );
-        b.require_auth_for_args(
-            (token_b.clone(), token_a.clone(), amount_b, min_a_for_b).into_val(&env),
-        );
-
-        // Perform the swap by moving tokens from a to b and from b to a.
-        move_token(&env, &token_a, &a, &b, amount_a, min_a_for_b);
-        move_token(&env, &token_b, &b, &a, amount_b, min_b_for_a);
-    }
-}
-
-fn move_token(
-    env: &Env,
-    token: &Address,
-    from: &Address,
-    to: &Address,
-    max_spend_amount: i128,
-    transfer_amount: i128,
-) {
-    let token = token::Client::new(env, token);
-    let contract_address = env.current_contract_address();
-    // This call needs to be authorized by `from` address. It transfers the
-    // maximum spend amount to the swap contract's address in order to decouple
-    // the signature from `to` address (so that parties don't need to know each
-    // other).
-    token.transfer(from, &contract_address, &max_spend_amount);
-    // Transfer the necessary amount to `to`.
-    token.transfer(&contract_address, to, &transfer_amount);
-    // Refund the remaining balance to `from`.
-    token.transfer(
-        &contract_address,
-        from,
-        &(max_spend_amount - transfer_amount),
-    );
-}
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/atomic_swap
-
-## Cómo Funciona
-
-El contrato de ejemplo requiere dos `Direcciones` para autorizar sus partes de la operación de intercambio: una `Dirección` quiere vender una cantidad dada de token A por token B a un precio dado y otra `Dirección` quiere vender token B por token A a un precio dado. El contrato intercambia los tokens atómicamente, pero solo si se respeta el precio mínimo solicitado para ambas partes.
-
-Abre el archivo `atomic_swap/src/lib.rs` o ve el código anterior para seguir.
-
-### Autorización de intercambio
-
-```rust
-...
-a.require_auth_for_args(
-    (token_a.clone(), token_b.clone(), amount_a, min_b_for_a).into_val(&env),
-);
-b.require_auth_for_args(
-    (token_b.clone(), token_a.clone(), amount_b, min_a_for_b).into_val(&env),
-);
-...
-```
-
-La autorización de la función `swap` aprovecha la función de host de Soroban `require_auth_for_args`. Tanto `a` como `b` necesitan autorizar argumentos simétricos: token que venden, token que compran, cantidad de token que venden, cantidad mínima de token que quieren recibir. Esto significa que `a` y `b` pueden ser intercambiados libremente en los argumentos de invocación (siempre que los argumentos respectivos también sean cambiados).
-
-### Moviendo los tokens
-
-```rust
-...
-// Perform the swap via two token transfers.
-move_token(&env, token_a, &a, &b, amount_a, min_a_for_b);
-move_token(&env, token_b, &b, &a, amount_b, min_b_for_a);
-...
-fn move_token(
-    env: &Env,
-    token: &Address,
-    from: &Address,
-    to: &Address,
-    max_spend_amount: i128,
-    transfer_amount: i128,
-) {
-    let token = token::Client::new(env, token);
-    let contract_address = env.current_contract_address();
-    // This call needs to be authorized by `from` address. It transfers the
-    // maximum spend amount to the swap contract's address in order to decouple
-    // the signature from `to` address (so that parties don't need to know each
-    // other).
-    token.transfer(from, &contract_address, &max_spend_amount);
-    // Transfer the necessary amount to `to`.
-    token.transfer(&contract_address, to, &transfer_amount);
-    // Refund the remaining balance to `from`.
-    token.transfer(
-        &contract_address,
-        from,
-        &(&max_spend_amount - &transfer_amount),
-    );
-}
-```
-
-El intercambio en sí se implementa a través de dos movimientos de tokens: de `a` a `b` y de `b` a `a`. El movimiento de token se implementa a través de la autorización: los usuarios no necesitan conocerse entre sí para realizar el intercambio, y en cambio autorizan al contrato de intercambio a gastar la cantidad necesaria de token en su nombre a través de `transfer`. El marco de autenticación de Soroban se asegura de que las firmas de `transfer` tengan el contexto adecuado y no sean utilizables fuera de la invocación del contrato `swap`.
-
-### Pruebas
-
-Abre el archivo [`atomic_swap/src/test.rs`] para seguir.
-
-[`atomic_swap/src/test.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/atomic_swap/src/test.rs
-
-Consulta otros ejemplos para información general sobre la configuración de pruebas.
-
-La parte interesante de este ejemplo es la verificación de la autorización de `swap`:
-
-```rust
-contract.swap(
-    &a,
-    &b,
-    &token_a.address,
-    &token_b.address,
-    &1000,
-    &4500,
-    &5000,
-    &950,
-);
-
-assert_eq!(
-    env.auths(),
-    std::vec![
-        (
-            a.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    contract.address.clone(),
-                    symbol_short!("swap"),
-                    (
-                        token_a.address.clone(),
-                        token_b.address.clone(),
-                        1000_i128,
-                        4500_i128
-                    )
-                        .into_val(&env),
-                )),
-                sub_invocations: std::vec![AuthorizedInvocation {
-                    function: AuthorizedFunction::Contract((
-                        token_a.address.clone(),
-                        symbol_short!("transfer"),
-                        (a.clone(), contract.address.clone(), 1000_i128,).into_val(&env),
-                    )),
-                    sub_invocations: std::vec![]
-                }]
-            }
-        ),
-        (
-            b.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    contract.address.clone(),
-                    symbol_short!("swap"),
-                    (
-                        token_b.address.clone(),
-                        token_a.address.clone(),
-                        5000_i128,
-                        950_i128
-                    )
-                        .into_val(&env),
-                )),
-                sub_invocations: std::vec![AuthorizedInvocation {
-                    function: AuthorizedFunction::Contract((
-                        token_b.address.clone(),
-                        symbol_short!("transfer"),
-                        (b.clone(), contract.address.clone(), 5000_i128,).into_val(&env),
-                    )),
-                    sub_invocations: std::vec![]
-                }]
-            }
-        ),
-    ]
-);
-```
-
-`env.auths()` devuelve todas las autorizaciones. En el caso de `swap` se esperan cuatro autorizaciones. Dos por cada dirección que autoriza, porque cada dirección autoriza no solo el intercambio, sino también el `approve` total sobre el token que se envía.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/auth.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/auth.mdx
deleted file mode 100644
index 98ff027663..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/auth.mdx
+++ /dev/null
@@ -1,494 +0,0 @@
----
-title: Autenticación
-description: Implementar autenticación y autorización.
-sidebar_position: 50
----
-
-<head>
-  <title>Implementar autenticación y autorización.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Implementar autenticación y autorización."
-  />
-  <meta
-    property="og:description"
-    content="Implementar autenticación y autorización en tu contrato inteligente utilizando el marco de autenticación gestionado por Soroban Host."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de autenticación] demuestra cómo implementar autenticación y autorización utilizando el marco de autenticación gestionado por Soroban Host.
-
-Este ejemplo es una extensión del [ejemplo de almacenamiento de datos].
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de almacenamiento de datos]: ../getting-started/storing-data.mdx
-[ejemplo de autenticación]: https://github.com/stellar/soroban-examples/tree/v23.0.0/auth
-
-## Ejecutar el ejemplo
-
-Primero sigue el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `auth`, y usa `cargo test`.
-
-```
-cd auth
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test ... ok
-```
-
-## Código
-
-```rust title="auth/src/lib.rs"
-#[contracttype]
-pub enum DataKey {
-    Counter(Address),
-}
-
-#[contract]
-pub struct IncrementContract;
-
-#[contractimpl]
-impl IncrementContract {
-    /// Increment increments a counter for the user, and returns the value.
-    pub fn increment(env: Env, user: Address, value: u32) -> u32 {
-        // Requires `user` to have authorized call of the `increment` of this
-        // contract with all the arguments passed to `increment`, i.e. `user`
-        // and `value`. This will panic if auth fails for any reason.
-        // When this is called, Soroban host performs the necessary
-        // authentication, manages replay prevention and enforces the user's
-        // authorization policies.
-        // The contracts normally shouldn't worry about these details and just
-        // write code in generic fashion using `Address` and `require_auth` (or
-        // `require_auth_for_args`).
-        user.require_auth();
-
-        // This call is equilvalent to the above:
-        // user.require_auth_for_args((&user, value).into_val(&env));
-
-        // The following has less arguments but is equivalent in authorization
-        // scope to the above calls (the user address doesn't have to be
-        // included in args as it's guaranteed to be authenticated).
-        // user.require_auth_for_args((value,).into_val(&env));
-
-        // Construct a key for the data being stored. Use an enum to set the
-        // contract up well for adding other types of data to be stored.
-        let key = DataKey::Counter(user.clone());
-
-        // Get the current count for the invoker.
-        let mut count: u32 = env.storage().persistent().get(&key).unwrap_or_default();
-
-        // Increment the count.
-        count += value;
-
-        // Save the count.
-        env.storage().persistent().set(&key, &count);
-
-        // Return the count to the caller.
-        count
-    }
-}
-```
-
-Ref: https://github.com/stellar/soroban-examples/tree/v23.0.0/auth
-
-## Cómo funciona
-
-El contrato de ejemplo almacena un contador por `Address` que solo puede ser incrementado por el dueño de ese `Address`.
-
-Abre el archivo `auth/src/lib.rs` o consulta el código anterior para seguirlo.
-
-### `Address`
-
-```rust
-#[contracttype]
-pub enum DataKey {
-    Counter(Address),
-}
-```
-
-`Address` es un identificador universal de Soroban que puede representar una cuenta Stellar, un contrato o una cuenta de contrato (un contrato que define un esquema de autenticación personalizado y políticas de autorización). Los contratos no necesitan distinguir entre estas representaciones internas. `Address` se puede usar cada vez que se necesite representar alguna identidad de red, como distinguir entre contadores para diferentes usuarios en este ejemplo.
-
-:::tip Las claves de enumeración como `DataKey` son útiles para organizar el almacenamiento del contrato.
-
-Diferentes valores de enumeración crean diferentes 'espacios de nombres' de claves.
-
-En el ejemplo, el contador para cada dirección se almacena contra `DataKey::Counter(Address)`. Si el contrato necesita comenzar a almacenar otros tipos de datos, puede hacerlo añadiendo variantes adicionales a la enumeración.
-
-:::
-
-### `require_auth`
-
-```rust
-impl IncrementContract {
-    pub fn increment(env: Env, user: Address, value: u32) -> u32 {
-        user.require_auth();
-```
-
-El método `require_auth` puede ser llamado para cualquier `Address`. Semánticamente, `user.require_auth()` aquí significa 'requiere que `user` haya autorizado la llamada a la función `increment` de la instancia actual de `IncrementContract` con los argumentos actuales de la llamada, es decir, los valores actuales de `user` y `value'. En términos más simples, esto asegura que el `user\` haya permitido incrementar el valor de su contador y que nadie más pueda incrementarlo.
-
-Al usar `require_auth`, la implementación del contrato no necesita preocuparse por las firmas, la autenticación y la prevención de repetición. Todas estas características son implementadas por el host de Soroban y ocurren automáticamente siempre que se use el tipo `Address`.
-
-`Address` tiene otro método llamado `require_auth_for_args`. Funciona de la misma manera que `require_auth`, pero permite personalizar los argumentos que deben ser autorizados. Sin embargo, esto debe usarse con cuidado para asegurar que haya un mapeo determinista entre los argumentos de invocación del contrato y los argumentos de `require_auth_for_args`.
-
-Las dos llamadas siguientes son funcionalmente equivalentes a `user.require_auth`:
-
-```rust
-// Completely equivalent
-user.require_auth_for_args((&user, value).into_val(&env));
-// The following has less arguments but is equivalent in authorization
-// scope to the above call (the user address doesn't have to be
-// included in args as it's guaranteed to be authenticated).
-user.require_auth_for_args((value,).into_val(&env));
-```
-
-### Pruebas
-
-Abre el archivo [`auth/src/test.rs`] para seguirlo.
-
-[`auth/src/test.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/auth/src/test.rs
-
-```rust title="auth/src/test.rs"
-#![cfg(test)]
-extern crate std;
-
-#[test]
-fn test() {
-    let env = Env::default();
-    env.mock_all_auths();
-
-    let contract_id = env.register(IncrementContract, {});
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    let user_1 = Address::generate(&env);
-    let user_2 = Address::generate(&env);
-
-    assert_eq!(client.increment(&user_1, &5), 5);
-    // Verify that the user indeed had to authorize a call of `increment` with
-    // the expected arguments:
-    assert_eq!(
-        env.auths(),
-        std::vec![(
-            // Address for which authorization check is performed
-            user_1.clone(),
-            // Invocation tree that needs to be authorized
-            AuthorizedInvocation {
-                // Function that is authorized. Can be a contract function or
-                // a host function that requires authorization.
-                function: AuthorizedFunction::Contract((
-                    // Address of the called contract
-                    contract_id.clone(),
-                    // Name of the called function
-                    symbol_short!("increment"),
-                    // Arguments used to call `increment` (converted to the env-managed vector via `into_val`)
-                    (user_1.clone(), 5_u32).into_val(&env),
-                )),
-                // The contract doesn't call any other contracts that require
-                // authorization,
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-
-    // Do more `increment` calls. It's not necessary to verify authorizations
-    // for every one of them as we don't expect the auth logic to change from
-    // call to call.
-    assert_eq!(client.increment(&user_1, &2), 7);
-    assert_eq!(client.increment(&user_2, &1), 1);
-    assert_eq!(client.increment(&user_1, &3), 10);
-    assert_eq!(client.increment(&user_2, &4), 5);
-}
-```
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno Soroban en el que se ejecutará el contrato.
-
-```rust
-let env = Env::default();
-```
-
-La prueba instruye al entorno para simular todas las autenticaciones. Todas las llamadas a `require_auth` o `require_auth_for_args` tendrán éxito.
-
-```rust
-env.mock_all_auths();
-```
-
-El contrato se registra en el entorno usando el tipo de contrato.
-
-```rust
-let contract_id = env.register(IncrementContract, {});
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente llevará el mismo nombre que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato, el tipo de contrato es `IncrementContract`, y el cliente se llama `IncrementContractClient`.
-
-```rust
-let client = IncrementContractClient::new(&env, &contract_id);
-```
-
-Generar `Address`es para dos usuarios. Normalmente, el valor exacto de `Address` no debería importar para las pruebas, por lo que se generan simplemente de forma aleatoria.
-
-```rust
-let user_1 = Address::random(&env);
-let user_2 = Address::random(&env);
-```
-
-Invocar la función `increment` para `user_1`.
-
-```rust
-assert_eq!(client.increment(&user_1, &5), 5);
-```
-
-Para verificar que la(s) llamada(s) a `require_auth` realmente han ocurrido, usa la función `auths` que devuelve un vector de tuplas que contiene las autorizaciones de la más reciente invocación del contrato.
-
-```rust
-assert_eq!(
-    env.auths(),
-    std::vec![(
-        // Address for which auth is performed
-        user_1.clone(),
-        // Identifier of the called contract
-        contract_id.clone(),
-        // Name of the called function
-        symbol_short!("increment"),
-        // Arguments used to call `increment` (converted to the env-managed vector via `into_val`)
-        (user_1.clone(), 5_u32).into_val(&env)
-    )]
-);
-```
-
-Invoca la función `increment` varias veces más para ambos usuarios. Observa que los valores se rastrean por separado para cada usuario.
-
-```rust
-assert_eq!(client.increment(&user_1, &2), 7);
-assert_eq!(client.increment(&user_2, &1), 1);
-assert_eq!(client.increment(&user_1, &3), 10);
-assert_eq!(client.increment(&user_2, &4), 5);
-```
-
-## Construir el contrato
-
-Para construir el contrato en un archivo `.wasm`, utiliza el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-El archivo `.wasm` debe encontrarse en el directorio `target` después de la construcción:
-
-```
-target/wasm32v1-none/release/soroban_auth_contract.wasm
-```
-
-## Ejecutar el contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar funciones sobre el contrato.
-
-Pero dado que estamos tratando con autorización y firmas, necesitamos configurar algunas identidades para usar en las pruebas y obtener sus claves públicas:
-
-```sh
-stellar keys generate acc1
-stellar keys generate acc2
-stellar keys address acc1
-stellar keys address acc2
-```
-
-Salida de ejemplo con dos claves públicas de identidades:
-
-```
-GA6S566FD3EQDUNQ4IGSLXKW3TGVSTQW3TPHPGS7NWMCEIPBOKTNCSRU
-GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B
-```
-
-Ahora el contrato en sí puede ser invocado. Observa que el `--source-account` debe ser el nombre de identidad que igualarán con la dirección pasada al argumento `--user`. Esto permite que `Stellar CLI` firme automáticamente la carga necesaria para la invocación.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --source-account acc1 \
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm \
-    --id 1 \
-    -- \
-    increment \
-    --user GA6S566FD3EQDUNQ4IGSLXKW3TGVSTQW3TPHPGS7NWMCEIPBOKTNCSRU \
-    --value 2
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --source-account acc1 `
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm `
-    --id 1 `
-    -- `
-    increment `
-    --user GA6S566FD3EQDUNQ4IGSLXKW3TGVSTQW3TPHPGS7NWMCEIPBOKTNCSRU `
-    --value 2
-```
-
-</TabItem>
-</Tabs>
-
-Ejecuta unas cuantas incrementaciones más para ambas cuentas.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --source-account acc2 \
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm \
-    --id 1 \
-    -- \
-    increment \
-    --user GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B \
-    --value 5
-```
-
-```sh
-stellar contract invoke \
-    --source-account acc1 \
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm \
-    --id 1 \
-    -- \
-    increment \
-    --user GA6S566FD3EQDUNQ4IGSLXKW3TGVSTQW3TPHPGS7NWMCEIPBOKTNCSRU \
-    --value 3
-```
-
-```sh
-stellar contract invoke \
-    --source-account acc2 \
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm \
-    --id 1 \
-    -- \
-    increment \
-    --user GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B \
-    --value 10
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke \
-    --source-account acc2 \
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm \
-    --id 1 \
-    -- \
-    increment \
-    --user GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B \
-    --value 5
-```
-
-```powershell
-stellar contract invoke \
-    --source-account acc1 \
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm \
-    --id 1 \
-    -- \
-    increment \
-    --user GA6S566FD3EQDUNQ4IGSLXKW3TGVSTQW3TPHPGS7NWMCEIPBOKTNCSRU \
-    --value 3
-```
-
-```powershell
-stellar contract invoke \
-    --source-account acc2 \
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm \
-    --id 1 \
-    -- \
-    increment \
-    --user GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B \
-    --value 10
-```
-
-</TabItem>
-</Tabs>
-
-Ver los datos que han sido almacenados para cada usuario con `stellar contract read`.
-
-```sh
-stellar contract read --id 1
-```
-
-```
-"[""Counter"",""GA6S566FD3EQDUNQ4IGSLXKW3TGVSTQW3TPHPGS7NWMCEIPBOKTNCSRU""]",5
-"[""Counter"",""GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B""]",15
-```
-
-También es posible previsualizar la carga de autorización que se está firmando al proporcionar la bandera `--auth` a la invocación:
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --source-account acc2 \
-    --auth \
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm \
-    --id 1 \
-    -- \
-    increment \
-    --user GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B \
-    --value 123
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --source-account acc2 `
-    --auth `
-    --wasm target/wasm32v1-none/release/soroban_auth_contract.wasm `
-    --id 1 `
-    -- `
-    increment `
-    --user GAJGHZ44IJXYFNOVRZGBCVKC2V62DB2KHZB7BEMYOWOLFQH4XP2TAM6B `
-    --value 123
-```
-
-</TabItem>
-</Tabs>
-
-```json
-Contract auth: [{"address_with_nonce":null,"root_invocation":{"contract_id":"0000000000000000000000000000000000000000000000000000000000000001","function_name":"increment","args":[{"object":{"address":{"account":{"public_key_type_ed25519":"c7bab0288753d58d3e21cc3fa68cd2546b5f78ae6635a6f1b3fe07e03ee846e9"}}}},{"u32":123}],"sub_invocations":[]},"signature_args":[]}]
-```
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
-
-## Lectura adicional
-
-La [documentación de autorización](../../../learn/fundamentals/contract-development/authorization.mdx) ofrece más detalles sobre cómo funciona el marco de autenticación de Soroban.
-
-Los ejemplos de [Timelock](../example-contracts/timelock.mdx) y [Single Offer](../example-contracts/single-offer-sale.mdx) demuestran la autorización de operaciones de tokens en nombre del usuario, que se puede extender a cualquier invocación de contrato anidada.
-
-El ejemplo de [Atomic Swap](../example-contracts/atomic-swap.mdx) demuestra autorización multi-partes donde múltiples usuarios firman sus partes de la invocación del contrato.
-
-El ejemplo de [Simple Account](../example-contracts/simple-account.mdx) demuestra una implementación mínima de cuenta de contrato y cómo funciona `__check_auth` de inicio a fin.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/bls-signature.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/bls-signature.mdx
deleted file mode 100644
index 3aa4128f97..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/bls-signature.mdx
+++ /dev/null
@@ -1,494 +0,0 @@
----
-title: Firma BLS
-description: Una cuenta de contrato con verificación de firma BLS.
-sidebar_position: 17
----
-
-<head>
-  <title>Firma BLS</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Una cuenta de contrato con verificación de firma BLS."
-  />
-  <meta
-    property="og:description"
-    content="Una cuenta de contrato básica que implementa la función `FastAggregateVerify` en el borrador de [BLS Signatures](https://www.ietf.org/archive/id/draft-irtf-cfrg-bls-signature-05.html#name-fastaggregateverify)."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de firma BLS] muestra cómo implementar la verificación de firmas BLS dentro de una cuenta de contrato.
-
-Este ejemplo se basa en el [ejemplo de cuenta compleja]. Aunque el objetivo principal es ilustrar el uso práctico de las funcionalidades de BLS12-381 en un contexto relevante.
-
-Es bueno comprender cómo funciona una cuenta de contrato, por lo que primero recorre el [ejemplo de cuenta simple], aunque no es obligatorio.
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[Ejemplo de firma BLS]: https://github.com/stellar/soroban-examples/tree/v23.0.0/bls_signature
-[Ejemplo de cuenta compleja]: ./complex-account.mdx
-[Ejemplo de cuenta simple]: ./simple-account.mdx
-
-## Contexto sobre la firma BLS
-
-Hay muchos buenos recursos sobre la firma BLS, por ejemplo, el "BLS12-381 Para el resto de nosotros" tiene una sección sobre [firma digital BLS](https://hackmd.io/@benjaminion/bls12-381#BLS-digital-signatures). El [BLS Signature para Personas Ocupadas](https://gist.github.com/paulmillr/18b802ad219b1aee34d773d08ec26ca2) también es un buen recurso para una visión rápida. Para referencia completa, consulta el [borrador de IETF](https://datatracker.ietf.org/doc/draft-irtf-cfrg-bls-signature/).
-
-En resumen, estamos verificando la siguiente relación:
-
-$$
-e(pk, H(m)) = e(g1, \sigma)
-$$
-
-Donde $pk$ es la clave pública, $H(m)$ es el hash del mensaje en el grupo `G2`, $g1$ es el punto generador en el grupo `G1` y $sigma$ es la firma. $e(,)$ denota el emparejamiento bilineal entre un punto en `G1` y un punto en `G2`.
-
-Lo bueno de la firma basada en emparejamiento es que permite la agregación de firmas. Es decir. si tienes múltiples firmantes `pk_0 .. pk_n` sobre un solo mensaje, puedes calcular la clave pública agregada $pk_{agg}$ sumando todas las claves públicas (recuerda que cada clave pública es solo un punto en el grupo G1), la firma agregada $\sigma_{agg}$ sumando las firmas individuales (que es solo un punto en el grupo G2).
-
-Luego la verificación de la firma agregada es solo
-
-$$
-e(pk_{agg}, H(m)) = e(g1, \sigma_{agg})
-$$
-
-Con un solo emparejamiento en cadena, puedes verificar N firmas en el mismo mensaje en tiempo constante. En general, `n` mensajes únicos requieren `n + 1` operaciones de emparejamiento para verificar todas las firmas.
-
-### Hash del mensaje `H(m)`
-
-El mensaje deberá ser hasheado en la curva `H(m)` para que se aplique la operación de emparejamiento. Seguimos el enfoque descrito en [RFC 9380 - Hashing to Elliptic Curves](https://datatracker.ietf.org/doc/rfc9380/).
-
-El método de hash requiere una etiqueta de separación de dominio única (DST), es altamente recomendable que tu aplicación elija un DST único. Para los requisitos del DST, consulta la sección <b>3,1</b> del RFC,
-
-:::tip
-
-Para firmas digitales, los grupos G1 y G2 pueden usarse de manera intercambiable. Las claves públicas pueden elegirse como elementos de G1 con firmas en G2, o viceversa. La elección implica compensaciones entre velocidad de ejecución y tamaño de almacenamiento. G1 ofrece puntos más pequeños y operaciones más rápidas, mientras que G2 tiene puntos más grandes y un rendimiento más lento.
-
-:::
-
-:::caution
-
-El ejemplo presentado a continuación está destinado solo para fines de demostración
-
-- Ha **no** pasado por auditoría de seguridad.
-- No es **seguro** para su uso en entornos de producción.
-
-Implementar un esquema de firma seguro para producción requiere un profundo entendimiento de la criptografía subyacente y consideraciones de seguridad. **Usa esto bajo tu propio riesgo**.
-
-:::
-
-## Ejecutar el ejemplo
-
-Primero, pasa por el proceso de [Configuración] para tener tu entorno de desarrollo configurado, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `bls_signature`, y usa `cargo test`.
-
-```
-cd bls_signature
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test ... ok
-```
-
-## Código
-
-```rust title="bls_signature/src/lib.rs"
-#[contract]
-pub struct IncrementContract;
-
-// `DST `is the domain separation tag, intended to keep hashing inputs of your
-// contract separate. Refer to section 3.1 in the [Hashing to Elliptic
-// Curves](https://datatracker.ietf.org/doc/html/rfc9380) on requirements of
-// DST.
-const DST: &str = "BLSSIG-V01-CS01-with-BLS12381G2_XMD:SHA-256_SSWU_RO_";
-
-#[derive(Clone)]
-#[contracttype]
-pub enum DataKey {
-    Owners,
-    Counter,
-    Dst,
-}
-
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum AccError {
-    InvalidSignature = 1,
-}
-
-#[contractimpl]
-impl IncrementContract {
-    pub fn init(env: Env, agg_pk: BytesN<96>) {
-        // Initialize the account contract essentials: the aggregated pubkey and
-        // the DST. Because the message to be signed (which is
-        // the hash of some call stack) is the same for all signers, we can
-        // simply aggregate all signers (adding up the G1 pubkeys) and store it.
-        env.storage().persistent().set(&DataKey::Owners, &agg_pk);
-        env.storage()
-            .instance()
-            .set(&DataKey::Dst, &Bytes::from_slice(&env, DST.as_bytes()));
-        // initialize the counter, i.e. the business logic this signer contract
-        // guards
-        env.storage().instance().set(&DataKey::Counter, &0_u32);
-    }
-
-    pub fn increment(env: Env) -> u32 {
-        env.current_contract_address().require_auth();
-        let mut count: u32 = env.storage().instance().get(&DataKey::Counter).unwrap_or(0);
-        count += 1;
-        env.storage().instance().set(&DataKey::Counter, &count);
-        count
-    }
-}
-
-#[contractimpl]
-impl CustomAccountInterface for IncrementContract {
-    type Signature = BytesN<192>;
-
-    type Error = AccError;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,
-        signature_payload: Hash<32>,
-        agg_sig: Self::Signature,
-        _auth_contexts: Vec<Context>,
-    ) -> Result<(), AccError> {
-        // The sdk module containing access to the bls12_381 functions
-        let bls = env.crypto().bls12_381();
-
-        // Retrieve the aggregated pubkey and the DST from storage
-        let agg_pk: BytesN<96> = env.storage().persistent().get(&DataKey::Owners).unwrap();
-        let dst: Bytes = env.storage().instance().get(&DataKey::Dst).unwrap();
-
-        // This is the negative of g1 (generator point of the G1 group)
-        let neg_g1 = G1Affine::from_bytes(bytesn!(&env, 0x17f1d3a73197d7942695638c4fa9ac0fc3688c4f9774b905a14e3a3f171bac586c55e83ff97a1aeffb3af00adb22c6bb114d1d6855d545a8aa7d76c8cf2e21f267816aef1db507c96655b9d5caac42364e6f38ba0ecb751bad54dcd6b939c2ca));
-        // Hash the signature_payload i.e. the msg being signed and to be
-        // verified into a point in G2
-        let msg_g2 = bls.hash_to_g2(&signature_payload.into(), &dst);
-
-        // Prepare inputs to the pairing function
-        let vp1 = vec![&env, G1Affine::from_bytes(agg_pk), neg_g1];
-        let vp2 = vec![&env, msg_g2, G2Affine::from_bytes(agg_sig)];
-
-        // Perform the pairing check, i.e. e(pk, msg)*e(-g1, sig) == 1, which is
-        // equivalent to checking `e(pk, msg) == e(g1, sig)`.
-        // The LHS = e(sk * g1, msg) = sk * e(g1, msg) = e(g1, sk * msg) = e(g1, sig),
-        // thus it must equal to the RHS if the signature matches.
-        if !bls.pairing_check(vp1, vp2) {
-            return Err(AccError::InvalidSignature);
-        }
-        Ok(())
-    }
-}
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/bls_signature
-
-## Cómo funciona
-
-El contrato de ejemplo almacena un contador que solo puede ser incrementado si un conjunto de propietarios lo ha aprobado.
-
-Abre el archivo `bls_signature/src/lib.rs` o consulta el código anterior para seguirlo.
-
-### El Contrato
-
-```rust
-#[contract]
-pub struct IncrementContract;
-
-#[derive(Clone)]
-#[contracttype]
-pub enum DataKey {
-    Owners,
-    Counter,
-    Dst,
-}
-
-#[contractimpl]
-impl IncrementContract {
-    pub fn init(env: Env, agg_pk: BytesN<96>) {
-        // Initialize the account contract essentials: the aggregated pubkey and
-        // the DST. Because the message to be signed (which is
-        // the hash of some call stack) is the same for all signers, we can
-        // simply aggregate all signers (adding up the G1 pubkeys) and store it.
-        env.storage().persistent().set(&DataKey::Owners, &agg_pk);
-        env.storage()
-            .instance()
-            .set(&DataKey::Dst, &Bytes::from_slice(&env, DST.as_bytes()));
-        // initialize the counter, i.e. the business logic this signer contract
-        // guards
-        env.storage().instance().set(&DataKey::Counter, &0_u32);
-    }
-
-    pub fn increment(env: Env) -> u32 {
-        env.current_contract_address().require_auth();
-        let mut count: u32 = env.storage().instance().get(&DataKey::Counter).unwrap_or(0);
-        count += 1;
-        env.storage().instance().set(&DataKey::Counter, &count);
-        count
-    }
-}
-```
-
-Este contrato es bastante simple y estándar. En `init()`, inicializa la clave pública agregada de todos los propietarios, la etiqueta de separación de dominio `DST`, e inicializa el contador en 0.
-
-Contiene una única función `incrementar` que llama a `require_auth` que verificará la condición de autorización definida más adelante, y si es exitosa, incrementa y retorna el contador.
-
-### Verificación de firma BLS
-
-```rust
-#[contractimpl]
-impl CustomAccountInterface for IncrementContract {
-    type Signature = BytesN<192>;
-
-    type Error = AccError;
-
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,
-        signature_payload: Hash<32>,
-        agg_sig: Self::Signature,
-        _auth_contexts: Vec<Context>,
-    ) -> Result<(), AccError> {
-        // The sdk module containing access to the bls12_381 functions
-        let bls = env.crypto().bls12_381();
-
-        // Retrieve the aggregated pubkey and the DST from storage
-        let agg_pk: BytesN<96> = env.storage().persistent().get(&DataKey::Owners).unwrap();
-        let dst: Bytes = env.storage().instance().get(&DataKey::Dst).unwrap();
-
-        // This is the negative of g1 (generator point of the G1 group)
-        let neg_g1 = G1Affine::from_bytes(bytesn!(&env, 0x17f1d3a73197d7942695638c4fa9ac0fc3688c4f9774b905a14e3a3f171bac586c55e83ff97a1aeffb3af00adb22c6bb114d1d6855d545a8aa7d76c8cf2e21f267816aef1db507c96655b9d5caac42364e6f38ba0ecb751bad54dcd6b939c2ca));
-        // Hash the signature_payload i.e. the msg being signed and to be
-        // verified into a point in G2
-        let msg_g2 = bls.hash_to_g2(&signature_payload.into(), &dst);
-
-        // Prepare inputs to the pairing function
-        let vp1 = vec![&env, G1Affine::from_bytes(agg_pk), neg_g1];
-        let vp2 = vec![&env, msg_g2, G2Affine::from_bytes(agg_sig)];
-
-        // Perform the pairing check, i.e. e(pk, msg)*e(-g1, sig) == 1, which is
-        // equivalent to checking `e(pk, msg) == e(g1, sig)`.
-        // The LHS = e(sk * g1, msg) = sk * e(g1, msg) = e(g1, sk * msg) = e(g1, sig),
-        // thus it must equal to the RHS if the signature matches.
-        if !bls.pairing_check(vp1, vp2) {
-            return Err(AccError::InvalidSignature);
-        }
-        Ok(())
-    }
-}
-```
-
-La función `CustomAccountInterface::__check_auth` implementa la lógica de verificación de firma personalizada para esta cuenta.
-
-`env.crypto().bls12_381()` inicializa el módulo bls12_381 desde el cual están disponibles las funciones BLS12-381. El `payload_firma` contiene el payload que fue firmado.
-
-`bls.hash_to_g2(&payload_firma.into(), &dst)` hashea el mensaje en el grupo G2. `agg_sig` contiene la firma agregada que es otro punto en G2.
-
-Para realizar la verificación de firma, construimos dos vectores `Vec<G1Affine>` y `Vec<G2Affine>`, y llamamos `bls.pairing_check` sobre ellos. La función de verificación de emparejamiento realiza `e(pk, msg)*e(-g1, sig) == 1` que es equivalente a verificar `e(pk, msg) == e(g1, sig)`.
-
-### Pruebas
-
-Abre el archivo [`bls_signature/src/test.rs`] para seguirlo.
-
-[`bls_signature/src/test.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/bls_signature/src/test.rs
-
-```rust title="bls_signature/src/test.rs"
-#[test]
-fn test() {
-    let env = Env::default();
-    let pk = aggregate_pk_bytes(&env);
-    env.mock_all_auths();
-
-    let client = create_client(&env);
-    client.init(&pk);
-    let payload = BytesN::random(&env);
-    let sig_val = sign_and_aggregate(&env, &payload.clone().into()).to_val();
-
-    env.try_invoke_contract_check_auth::<AccError>(&client.address, &payload, sig_val, &vec![&env])
-        .unwrap();
-    env.cost_estimate().budget().print();
-}
-```
-
-La mayoría de lo que aquí se presenta es necesario para crear el cliente del contrato y asegurar la invocación de su implementación `CustomAccountInterface` para la autorización mediante firma. Después de la configuración, llamar a `env.try_invoke_contract_check_auth` en el cliente invocará la lógica de `__check_auth` que hemos definido en nuestro contrato.
-
-La invocación no retornará nada en caso de éxito, y causará pánico en caso de fallo. `env.cost_estimate().budget().print()` al final muestra el presupuesto.
-
-#### Agregación de firma
-
-Primero declaramos 10 pares de claves aleatorias. Estos serán usados como los firmantes de este contrato de prueba.
-
-```rust
-#[derive(Debug)]
-pub struct KeyPair {
-    pub sk: [u8; 32],
-    pub pk: [u8; 96],
-}
-
-static KEY_PAIRS: &[KeyPair] = &[
-    KeyPair {
-        sk: hex!("18a5ac3cfa6d0b10437a92c96f553311fc0e25500d691ae4b26581e6f925ec83"),
-        pk: hex!("0914e32703bad05ccf4180e240e44e867b26580f36e09331997b2e9effe1f509b1a804fc7ba1f1334c8d41f060dd72550901c5549caef45212a236e288a785d762a087092c769bfa79611b96d73521ddd086b7e05b5c7e4210f50c2ee832e183"),
-    },
-    KeyPair {
-        sk: hex!("738dbecafa122ee3c953f07e78461a4281cadec00c869098bac48c8c57b63374"),
-        pk: hex!("05f4708a013699229f67d0e16f7c2af8a6557d6d11b737286cfb9429e092c31c412f623d61c7de259c33701aa5387b5004e2c03e8b7ea2740b10a5b4fd050eecca45ccf5588d024cbb7adc963006c29d45a38cb7a06ce2ac45fce52fc0d36572"),
-    },
-    KeyPair {
-        sk: hex!("4bff25b53f29c8af15cf9b8e69988c3ff79c80811d5027c80920f92fad8d137d"),
-        pk: hex!("18d0fef68a72e0746f8481fa72b78f945bf75c3a1e036fbbde62a421d8f9568a2ded235a27ad3eb0dc234b298b54dd540f61577bc4c6e8842f8aa953af57a6783924c479e78b0d4959038d3d108b3f6dc6a1b02ec605cb6d789af16cfe67f689"),
-    },
-    KeyPair {
-        sk: hex!("2110f7dae25c4300e1a9681bad6311a547269dba69e94efd342cc208ff50813b"),
-        pk: hex!("1643b04cc21f8af9492509c51a6e20e67fa7923f4fbd52f6fcf73c6a4013f864e3e29eb03f54d234582250ebb5df21140381d0c735e868adfe62f85cf8e85d279864333dbe70656a5f35ebc52c5b497f1c65c7a0144bb0c9a1d843f1a8fb9979"),
-    },
-    KeyPair {
-        sk: hex!("1e4b6d54ac58d317cbe6fb0472c3cbf2e60ea157edea21354cbc198770f81448"),
-        pk: hex!("02286d1a83a93f35c3461dd71d0840e83e1cd3275ee1af1bfd90ec2366485e9f7f18730f5b686f4810480f1ce5c63dca13a2fac1774aa4e22c29abb9280796d72a2bd0ef963dc76fd45090012bae4a727a6dce49550d9bc9776705f825e24731"),
-    },
-    KeyPair {
-        sk: hex!("471145761f5cd9d0a9a511f1a80657edfcddc43424e4a5582040ea75c4649909"),
-        pk: hex!("0b7920a3f2a50cfd6dc132a46b7163d3f7d6b1d03d9fcf450eb05dfa89991a269e707e3412270dc422b664d7adda782c11c973232e975ef0d4b4fb5626b563df542fd1862f80bce17cd09bcbce8884bdda4ac9286bf94854dd29cd511a9103a7"),
-    },
-    KeyPair {
-        sk: hex!("1914beab355b0a86a7bcd37f2e036a9c2c6bff7f16d8bf3e23e42b7131b44701"),
-        pk: hex!("1872237fb7ceccc1a6e85f83988c226cc47db75496e41cf20e8a4b93e8fd5e91d0cdcc3b2946a352223ec2b7817a2aae0dc4e6bb7b97c855828670362fcbd0ad6453f28e4fa4b7a075ac8bb1d69a4a1bb8c6723900fead307239f04a9bcec0ad"),
-    },
-    KeyPair {
-        sk: hex!("46b19b928638068780ba82e76dfeaeaf5c37790cdf37f580e206dc6599c72dc7"),
-        pk: hex!("0fd1a6b1e46b83a197bbf1dc2a854d024caa5ead5a54893c9767392c837d7c070e86a9206ddba1801332f9d74e0f78e9175419ccc40a966bf4c12a7f8500519e2b83cebd61e32121379911925bf7ae6d2c0d8ec4dcc411d4bbcd14763c1a9d31"),
-    },
-    KeyPair {
-        sk: hex!("0ce3cd1dcaecf002715228aeb0645c6a7fd9990ace3d79515c547dac120bb9f7"),
-        pk: hex!("19f7e9dcd4ce2bef92180b60d0c7c7b48b1924a36f9fbb93e9ecb8acb3219e26033b83facd4dc6d2e3f9fa0fffafeca8168bd4824e31dc9dfd977fbf037210508bc807c1a6d20f98a044911f6b689328f3f25dd35a6c05e8c6ac3ac6ef0def91"),
-    },
-    KeyPair {
-        sk: hex!("6b4b27ba3ffc953eff3b974142cdac75f98c8c4ab26f93d5adfd49da5d462c3f"),
-        pk: hex!("15f55ec5572026d6c3c7c62b3ce3c5d7539045e9f492f2b1b0860c0af5f5f6b34531dfe4626a92d5c23ac6ad44330cf40e63a8a7234edbb41539c5484eff2cd23b2f0d502a7fd74501b1a05ffee29b24e79cb1ee9fb9b804d84f486283101ee0"),
-    },
-];
-```
-
-Agregamos las claves públicas de los firmantes, primero convirtiendo los bytes en `G1Affine`, y luego sumándolos todos.
-
-```rust
-fn aggregate_pk_bytes(env: &Env) -> BytesN<96> {
-    let bls = env.crypto().bls12_381();
-    let mut agg_pk = G1Affine::from_bytes(BytesN::from_array(env, &KEY_PAIRS[0].pk));
-    for i in 1..KEY_PAIRS.len() {
-        let pk = G1Affine::from_bytes(BytesN::from_array(env, &KEY_PAIRS[i].pk));
-        agg_pk = bls.g1_add(&agg_pk, &pk);
-    }
-    agg_pk.to_bytes()
-}
-```
-
-Para producir la firma, el mensaje será primero hasheado en G2 a través de `bls.hash_to_g2`. Aquí usamos nuestro propio DST definido.
-
-Para agregar las firmas, primero producimos firmas individuales haciendo que cada firmante firme el mensaje. Esto significa multiplicar la clave secreta por el punto G2 del mensaje. Luego los sumamos todos. Aquí usamos `g2_msm`, mediante un arreglo de puntos de mensaje (`Vec<G2Affine>`) y un arreglo de claves secretas (`Vec<Fr>`) y computa su producto interno que es la firma agregada que queremos.
-
-```rust
-const DST: &str = "BLSSIG-V01-CS01-with-BLS12381G2_XMD:SHA-256_SSWU_RO_";
-
-fn sign_and_aggregate(env: &Env, msg: &Bytes) -> BytesN<192> {
-    let bls = env.crypto().bls12_381();
-    let mut vec_sk: Vec<Fr> = vec![env];
-    for kp in KEY_PAIRS {
-        vec_sk.push_back(Fr::from_bytes(BytesN::from_array(env, &kp.sk)));
-    }
-    let dst = Bytes::from_slice(env, DST.as_bytes());
-    let msg_g2 = bls.hash_to_g2(&msg, &dst);
-    let vec_msg: Vec<G2Affine> = vec![
-        env,
-        msg_g2.clone(),
-        msg_g2.clone(),
-        msg_g2.clone(),
-        msg_g2.clone(),
-        msg_g2.clone(),
-        msg_g2.clone(),
-        msg_g2.clone(),
-        msg_g2.clone(),
-        msg_g2.clone(),
-        msg_g2.clone(),
-    ];
-    bls.g2_msm(vec_msg, vec_sk).to_bytes()
-}
-```
-
-Ejecutar esta prueba generará la siguiente salida del presupuesto (se omite parte de la salida por brevedad), el consumo total de CPU para la verificación de la firma es alrededor de 31M. Y puedes agregar tantas claves públicas adicionales como desees. En general, `pairing_check` es una función que tiene un coste lineal, por lo que cuantas más mensajes únicos necesiten ser firmados, mayor será el coste. Aquí porque todos los firmantes firman el mismo contenido (hash de la pila de llamadas de este contrato), podemos hacerlo en tiempo constante.
-
-```
----- test::test stdout ----
-=================================================================
-Cpu limit: 100000000; used: 31143102
-Mem limit: 41943040; used: 159903
-=================================================================
-CostType                           cpu_insns      mem_bytes
-WasmInsnExec                       0              0
-MemAlloc                           23516          5000
-
-[... previous output omitted for brevity ...]
-
-VerifyEcdsaSecp256r1Sig            0              0
-Bls12381EncodeFp                   2644           0
-Bls12381DecodeFp                   11820          0
-Bls12381G1CheckPointOnCurve        3868           0
-Bls12381G1CheckPointInSubgroup     1461020        0
-Bls12381G2CheckPointOnCurve        11842          0
-Bls12381G2CheckPointInSubgroup     2115644        0
-Bls12381G1ProjectiveToAffine       0              0
-Bls12381G2ProjectiveToAffine       0              0
-Bls12381G1Add                      0              0
-Bls12381G1Mul                      0              0
-Bls12381G1Msm                      0              0
-Bls12381MapFpToG1                  0              0
-Bls12381HashToG1                   0              0
-Bls12381G2Add                      0              0
-Bls12381G2Mul                      0              0
-Bls12381G2Msm                      0              0
-Bls12381MapFp2ToG2                 0              0
-Bls12381HashToG2                   7052263        6816
-Bls12381Pairing                    20447400       148148
-Bls12381FrFromU256                 0              0
-Bls12381FrToU256                   0              0
-Bls12381FrAddSub                   0              0
-Bls12381FrMul                      0              0
-Bls12381FrPow                      0              0
-Bls12381FrInv                      0              0
-=================================================================
-```
-
-## Crear el contrato
-
-Para crear el contrato en un archivo `.wasm`, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-El archivo `.wasm` debería encontrarse en el directorio `target` después de la creación:
-
-```
-target/wasm32v1-none/release/soroban_bls_signature_contract.wasm
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/complex-account.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/complex-account.mdx
deleted file mode 100644
index da8747c39a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/complex-account.mdx
+++ /dev/null
@@ -1,455 +0,0 @@
----
-title: Cuenta Compleja
-description: Implementa una cuenta de contrato con firmas múltiples y políticas de autorización personalizadas.
-sidebar_position: 16
----
-
-<head>
-  <title>
-    {`Implementa una cuenta de contrato con firmas múltiples y políticas de autorización personalizadas.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Implementa una cuenta de contrato con firmas múltiples y políticas de autorización personalizadas."
-  />
-  <meta
-    property="og:description"
-    content="Desarrollada sobre el ejemplo de Cuenta Simple para añadir reglas multisig y lógica de políticas que se ejecutan cada vez que esta cuenta autoriza una llamada."
-  />
-</head>
-
-Comienza con el [ejemplo de Cuenta Simple](./simple-account.mdx) para aprender lo básico de un solo firmante. Esta Cuenta Compleja extiende esa base con firmas múltiples y políticas de autorización personalizables. Cada vez que se utiliza una `Address` que apunta a esta instancia de contrato, la lógica definida aquí se ejecuta dentro del marco de autenticación de Soroban.
-
-Las cuentas de contrato son exclusivas de Soroban y no pueden usarse para realizar otras operaciones de Stellar.
-
-:::danger
-
-Implementar una cuenta de contrato requiere un muy buen entendimiento de autenticación y autorización, y requiere pruebas y revisiones rigurosas. El ejemplo aquí no es un contrato de cuenta completamente desarrollado, úsalo solo como referencia de API.
-
-:::
-
-:::caution
-
-Aunque las cuentas de contrato son compatibles con el protocolo Stellar y el SDK de Soroban, el soporte completo por parte del cliente (como la simulación de transacciones) todavía está en desarrollo.
-
-:::
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de cuenta de contrato]: https://github.com/stellar/soroban-examples/tree/v23.0.0/account
-
-## Ejecutar el Ejemplo
-
-Primero sigue el proceso de [configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, salta la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo usa `cargo test`.
-
-```sh
-cargo test -p soroban-account-contract
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test_token_auth ... ok
-```
-
-## Cómo Funciona
-
-Abre el archivo `account/src/lib.rs` para seguir el ejemplo.
-
-Los contratos de cuenta implementan una función especial llamada `__check_auth` que toma la carga de firma, las firmas y el contexto de autorización. La función debe generar un error si la autenticación es rechazada; de lo contrario, se aprobará la autorización.
-
-Este contrato de ejemplo usa claves ed25519 para la verificación de firmas y soporta múltiples firmantes con el mismo peso. También implementa una política que permite establecer límites de gasto por token. El token puede gastarse más allá del límite solo si se proporcionan todas las firmas.
-
-Por ejemplo, el usuario puede inicializar este contrato con 2 llaves e introducir un límite de gasto de 100 USDC. De este modo, pueden usar una sola llave para firmar sus invocaciones al contrato y estar seguros de que, incluso si firman una transacción maliciosa, no gastarán más de 100 USDC.
-
-### Inicialización
-
-```rust title="account/src/lib.rs"
-#[contract]
-struct AccountContract;
-
-#[contracttype]
-#[derive(Clone)]
-enum DataKey {
-    SignerCnt,
-    Signer(BytesN<32>),
-    SpendLimit(Address),
-}
-
-...
-
-#[contractimpl]
-impl AccountContract {
-    // Initialize the contract with a list of ed25519 public key ('signers').
-    pub fn __constructor(env: Env, signers: Vec<BytesN<32>>) {
-        // In reality this would need some additional validation on signers
-        // (deduplication etc.).
-        for signer in signers.iter() {
-            env.storage().instance().set(&DataKey::Signer(signer), &());
-        }
-        env.storage()
-            .instance()
-            .set(&DataKey::SignerCnt, &signers.len());
-    }
-
-    ...
-}
-```
-
-Este contrato de cuenta necesita trabajar explícitamente con las claves públicas. Aquí inicializamos el contrato con llaves ed25519.
-
-Usamos el constructor para asegurar que la instancia del contrato se cree e inicialice de manera atómica (sin constructor existe el riesgo de que alguien adelante la inicialización del contrato y establezca sus propias claves públicas).
-
-### Modificación de política
-
-```rust
-#[contractimpl]
-impl AccountContract {
-    ...
-
-    // Adds a limit on any token transfers that aren't signed by every signer.
-    // For the sake of simplicity of the example the limit is only applied on
-    // a per-authorization basis; the 'real' limits should likely be time-based
-    // instead.
-    pub fn add_limit(env: Env, token: Address, limit: i128) {
-        // The current contract address is the account contract address and has
-        // the same semantics for `require_auth` call as any other account
-        // contract address.
-        // Note, that if a contract *invokes* another contract, then it would
-        // authorize the call on its own behalf and that wouldn't require any
-        // user-side verification.
-        env.current_contract_address().require_auth();
-        env.storage()
-            .instance()
-            .set(&DataKey::SpendLimit(token), &limit);
-    }
-}
-```
-
-Esta función permite a los usuarios establecer y modificar el límite de gasto por token descrito más arriba. El truco aquí es que `require_auth` puede usarse para la `current_contract_address()`, es decir, el contrato de cuenta puede usarse para verificar la autorización de sus propias funciones administrativas. De esta forma no es necesario escribir lógica duplicada de autorización y autenticación.
-
-### `__check_auth`
-
-```rust
-#[contracttype]
-#[derive(Clone)]
-pub struct AccSignature {
-    pub public_key: BytesN<32>,
-    pub signature: BytesN<64>,
-}
-
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum AccError {
-    NotEnoughSigners = 1,
-    NegativeAmount = 2,
-    BadSignatureOrder = 3,
-    UnknownSigner = 4,
-}
-
-...
-
-#[contractimpl]
-impl CustomAccountInterface for AccountContract {
-    type Signature = Vec<AccSignature>;
-    type Error = AccError;
-
-    // This is the 'entry point' of the account contract and every account
-    // contract has to implement it. `require_auth` calls for the Address of
-    // this contract will result in calling this `__check_auth` function with
-    // the appropriate arguments.
-    //
-    // This should return `()` if authentication and authorization checks have
-    // been passed and return an error (or panic) otherwise.
-    //
-    // `__check_auth` takes the payload that needed to be signed, arbitrarily
-    // typed signatures (`Vec<AccSignature>` contract type here) and authorization
-    // context that contains all the invocations that this call tries to verify.
-    //
-    // `__check_auth` has to authenticate the signatures. It also may use
-    // `auth_context` to implement additional authorization policies (like token
-    // spend limits here).
-    //
-    // Soroban host guarantees that `__check_auth` is only being called during
-    // `require_auth` verification and hence this may mutate its own state
-    // without the need for additional authorization (for example, this could
-    // store per-time-period token spend limits instead of just enforcing the
-    // limit per contract call).
-    //
-    // Note, that `__check_auth` function shouldn't call `require_auth` on the
-    // contract's own address in order to avoid infinite recursion.
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,
-        signature_payload: Hash<32>,
-        signatures: Self::Signature,
-        auth_context: Vec<Context>,
-    ) -> Result<(), AccError> {
-        // Perform authentication.
-        authenticate(&env, &signature_payload, &signatures)?;
-
-        let tot_signers: u32 = env
-            .storage()
-            .instance()
-            .get::<_, u32>(&DataKey::SignerCnt)
-            .unwrap();
-        let all_signed = tot_signers == signatures.len();
-
-        let curr_contract = env.current_contract_address();
-
-        // This is a map for tracking the token spend limits per token. This
-        // makes sure that if e.g. multiple `transfer` calls are being authorized
-        // for the same token we still respect the limit for the total
-        // transferred amount (and not the 'per-call' limits).
-        let mut spend_left_per_token = Map::<Address, i128>::new(&env);
-        // Verify the authorization policy.
-        for context in auth_context.iter() {
-            verify_authorization_policy(
-                &env,
-                &context,
-                &curr_contract,
-                all_signed,
-                &mut spend_left_per_token,
-            )?;
-        }
-        Ok(())
-    }
-}
-```
-
-`__check_auth` es una función especial que implementan los contratos de cuenta. Será llamada por el entorno de Soroban cada vez que se invoque `require_auth` o `require_auth_for_args` para la dirección del contrato de la cuenta.
-
-Aquí se implementa en dos pasos. Primero, se realiza la autenticación usando la carga de firma y un vector de firmas. Luego, se aplica la política de autorización usando el vector `auth_context`. Este vector contiene todas las llamadas de contrato que están siendo autorizadas por las firmas proporcionadas.
-
-`__check_auth` es una función reservada que solo puede ser llamada por el entorno de Soroban en respuesta a una llamada a `require_auth`. Cualquier llamada directa a `__check_auth` fallará. Esto hace que sea seguro escribir en el almacenamiento del contrato de cuenta desde `__check_auth`, ya que se garantiza que no será llamado en contextos inesperados. En este ejemplo es posible persistir los límites de gasto sin preocuparse de que sean agotados mediante un actor malicioso que llame directamente a `__check_auth`.
-
-### Autenticación
-
-```rust
-fn authenticate(
-    env: &Env,
-    signature_payload: &Hash<32>,
-    signatures: &Vec<AccSignature>,
-) -> Result<(), AccError> {
-    for i in 0..signatures.len() {
-        let signature = signatures.get_unchecked(i);
-        if i > 0 {
-            let prev_signature = signatures.get_unchecked(i - 1);
-            if prev_signature.public_key >= signature.public_key {
-                return Err(AccError::BadSignatureOrder);
-            }
-        }
-        if !env
-            .storage()
-            .instance()
-            .has(&DataKey::Signer(signature.public_key.clone()))
-        {
-            return Err(AccError::UnknownSigner);
-        }
-        env.crypto().ed25519_verify(
-            &signature.public_key,
-            &signature_payload.clone().into(),
-            &signature.signature,
-        );
-    }
-    Ok(())
-}
-```
-
-La autenticación aquí simplemente verifica que las firmas proporcionadas son válidas dado el payload y que pertenecen a los firmantes de este contrato de cuenta.
-
-### Política de autorización
-
-```rust
-fn verify_authorization_policy(
-    env: &Env,
-    context: &Context,
-    curr_contract: &Address,
-    all_signed: bool,
-    spend_left_per_token: &mut Map<Address, i128>,
-) -> Result<(), AccError> {
-    // There are no limitations when every signers signs the transaction.
-    if all_signed {
-        return Ok(());
-    }
-    let contract_context = match context {
-        Context::Contract(c) => {
-            // Allow modifying this contract only if every signer has signed for it.
-            if &c.contract == curr_contract {
-                return Err(AccError::NotEnoughSigners);
-            }
-            c
-        }
-        // Allow creating new contracts only if every signer has signed for it.
-        Context::CreateContractHostFn(_) | Context::CreateContractWithCtorHostFn(_) => {
-            return Err(AccError::NotEnoughSigners);
-        }
-    };
-
-    ...
-}
-```
-
-Verificamos la política por cada `Context`. Es decir, por cada llamada a `require_auth` para la dirección de esta cuenta. La política del contrato de cuenta exige que cada firmante haya firmado la llamada al método.
-
-```rust
-fn verify_authorization_policy(
-    env: &Env,
-    context: &Context,
-    curr_contract: &Address,
-    all_signed: bool,
-    spend_left_per_token: &mut Map<Address, i128>,
-) -> Result<(), AccError> {
-    ...
-
-    // Besides the checks above we're only interested in functions that spend tokens.
-    if contract_context.fn_name != TRANSFER_FN
-        && contract_context.fn_name != APPROVE_FN
-        && contract_context.fn_name != BURN_FN
-    {
-        return Ok(());
-    }
-
-    let spend_left: Option<i128> =
-        if let Some(spend_left) = spend_left_per_token.get(contract_context.contract.clone()) {
-            Some(spend_left)
-        } else if let Some(limit_left) = env
-            .storage()
-            .instance()
-            .get::<_, i128>(&DataKey::SpendLimit(contract_context.contract.clone()))
-        {
-            Some(limit_left)
-        } else {
-            None
-        };
-
-    // 'None' means that the contract is outside of the policy.
-    if let Some(spend_left) = spend_left {
-        // 'amount' is the third argument in both `approve` and `transfer`.
-        // If the contract has a different signature, it's safer to panic
-        // here, as it's expected to have the standard interface.
-        let spent: i128 = contract_context
-            .args
-            .get(2)
-            .unwrap()
-            .try_into_val(env)
-            .unwrap();
-        if spent < 0 {
-            return Err(AccError::NegativeAmount);
-        }
-        if !all_signed && spent > spend_left {
-            return Err(AccError::NotEnoughSigners);
-        }
-        spend_left_per_token.set(contract_context.contract.clone(), spend_left - spent);
-    }
-    Ok(())
-}
-```
-
-Luego verificamos los nombres estándar de funciones de token y comprobamos que para estas funciones no se excedan los límites de gasto.
-
-### Pruebas
-
-Abre el archivo [`account/src/test.rs`] para seguir el ejemplo.
-
-[`account/src/test.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/account/src/test.rs
-
-Consulta otros ejemplos para obtener información general sobre la configuración de las pruebas.
-
-Aquí solo observamos algunos puntos específicos de los contratos de cuenta.
-
-```rust
-fn sign(e: &Env, signer: &Keypair, payload: &BytesN<32>) -> Val {
-    AccSignature {
-        public_key: signer_public_key(e, signer),
-        signature: signer
-            .sign(payload.to_array().as_slice())
-            .to_bytes()
-            .into_val(e),
-    }
-    .into_val(e)
-}
-```
-
-A diferencia de la mayoría de los contratos que pueden usar simplemente `Address`, los contratos de cuenta manejan la verificación de firmas y por ello necesitan firmar realmente los payloads.
-
-```rust
-let payload = BytesN::random(&env);
-let token = Address::generate(&env);
-// `__check_auth` can't be called directly, hence we need to use
-// `try_invoke_contract_check_auth` testing utility that emulates being
-// called by the Soroban host during a `require_auth` call.
-env.try_invoke_contract_check_auth::<AccError>(
-    &account_contract.address,
-    &payload,
-    vec![&env, sign(&env, &signers[0], &payload)].into(),
-    &vec![
-        &env,
-        token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1000),
-    ],
-)
-.unwrap();
-```
-
-`__check_auth` no puede llamarse directamente como funciones regulares de contrato, por lo que necesitamos usar la utilidad de prueba `try_invoke_contract_check_auth` que simula ser llamada por el host Soroban durante una llamada a `require_auth`.
-
-```rust
-// Add a spend limit of 1000 per 1 signer.
-account_contract.add_limit(&token, &1000);
-// Verify that this call needs to be authorized.
-assert_eq!(
-    env.auths(),
-    std::vec![(
-        account_contract.address.clone(),
-        AuthorizedInvocation {
-            function: AuthorizedFunction::Contract((
-                account_contract.address.clone(),
-                symbol_short!("add_limit"),
-                (token.clone(), 1000_i128).into_val(&env),
-            )),
-            sub_invocations: std::vec![]
-        }
-    )]
-);
-```
-
-Afirmar el error específico del contrato en `try_invoke_contract_check_auth` permite verificar el código exacto del error y asegura que la verificación haya fallado por no tener suficientes firmantes, y no por otra razón.
-
-Es recomendable que el contrato de cuenta tenga códigos de error detallados y verificar que se devuelvan cuando se esperan.
-
-```rust
-// 1 signer no longer can perform the token operation that transfers more
-// than 1000 units.
-assert_eq!(
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1001)
-        ],
-    )
-    .err()
-    .unwrap()
-    .unwrap(),
-    AccError::NotEnoughSigners
-);
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/cross-contract-call.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/cross-contract-call.mdx
deleted file mode 100644
index 22007322fc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/cross-contract-call.mdx
+++ /dev/null
@@ -1,330 +0,0 @@
----
-title: Llamadas de contratos cruzados
-description: Llama a un contrato inteligente desde otro contrato inteligente.
-sidebar_position: 60
----
-
-<head>
-  <title>Llama a un contrato inteligente desde otro contrato inteligente.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Llama a un contrato inteligente desde otro contrato inteligente."
-  />
-  <meta
-    property="og:description"
-    content="Realiza una llamada de contrato cruzado invocando otro contrato usando su ID de contrato."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de llamada de contrato cruzado] demuestra cómo llamar a un contrato desde otro contrato.
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-:::info
-
-En este ejemplo hay dos contratos que se compilan por separado, se despliegan por separado, y luego se prueban juntos. Hay varias maneras de desarrollar y probar contratos con dependencias en otros contratos, y el SDK y herramientas de Soroban aún están desarrollando las herramientas para admitir estos flujos de trabajo. Se agradece la retroalimentación [aquí](https://github.com/stellar/rs-soroban-sdk/issues/new/choose).
-
-:::
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de llamada de contrato cruzado]: https://github.com/stellar/soroban-examples/tree/v23.0.0/cross_contract
-
-## Ejecutar el ejemplo
-
-Primero sigue el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, primero desarrolla el Contrato A (el contrato a ser llamado) y luego ejecuta `cargo test` desde el directorio del Contrato B. Desarrolla el Contrato A navegando al directorio `cross_contract/contract_a` y utiliza el comando de construcción `stellar contract build`:
-
-```sh
-cd cross_contract/contract_a
-stellar contract build
-```
-
-Cuando el Contrato A ha sido desarrollado, navega al directorio `cross_contract/contract_b`, y utiliza `cargo test`.
-
-```sh
-cd ../contract_b
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test ... ok
-```
-
-## Código
-
-```rust title="cross_contract/contract_a/src/lib.rs"
-#[contract]
-pub struct ContractA;
-
-#[contractimpl]
-impl ContractA {
-    pub fn add(x: u32, y: u32) -> u32 {
-        x.checked_add(y).expect("no overflow")
-    }
-}
-```
-
-```rust title="cross_contract/contract_b/src/lib.rs"
-mod contract_a {
-    soroban_sdk::contractimport!(
-        file = "../contract_a/target/wasm32v1-none/release/soroban_cross_contract_a_contract.wasm"
-    );
-}
-
-#[contract]
-pub struct ContractB;
-
-#[contractimpl]
-impl ContractB {
-    pub fn add_with(env: Env, contract: Address, x: u32, y: u32) -> u32 {
-        let client = contract_a::Client::new(&env, &contract);
-        client.add(&x, &y)
-    }
-}
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/cross_contract
-
-## Cómo funciona
-
-Las llamadas de contratos cruzados se realizan invocando otro contrato por su ID de contrato.
-
-Los contratos a invocar pueden ser importados a tu contrato utilizando `contractimport!(file = "...")`. La importación generará código:
-
-- Un tipo `ContractClient` que se puede usar para invocar funciones en el contrato.
-- Cualquier tipo en el contrato que haya sido anotado con `#[contracttype]`.
-
-:::tip
-
-El macro `contractimport!` generará los tipos en el módulo en el que se utiliza, por lo que es una buena idea usar el macro dentro de un bloque `mod { ...`... }\` o dentro de su propio archivo, para que los nombres de los tipos generados no colisionen con los nombres de los tipos en tu propio contrato.
-
-:::
-
-Abre los archivos anteriores para seguir adelante.
-
-### Contrato A: El contrato a ser llamado
-
-El contrato a ser llamado es el Contrato A. Es un contrato simple que acepta parámetros `x` y `y`, los suma y devuelve el resultado.
-
-```rust title="cross_contract/contract_a/src/lib.rs"
-#[contract]
-pub struct ContractA;
-
-#[contractimpl]
-impl ContractA {
-    pub fn add(x: u32, y: u32) -> u32 {
-        x.checked_add(y).expect("no overflow")
-    }
-}
-```
-
-:::tip
-
-El contrato usa el método `checked_add` para asegurarse de que no haya desbordamiento, y si hay desbordamiento, entra en pánico en lugar de devolver un valor desbordado. Los tipos de enteros primitivos de Rust tienen operaciones verificadas disponibles como funciones con el prefijo `checked_`.
-
-:::
-
-### Contrato B: El contrato que realiza la llamada
-
-El contrato que realiza la llamada es el Contrato B. Acepta un ID de contrato que llamará, así como los mismos parámetros a pasar. En muchos contratos, el contrato a llamar podría haberse almacenado como datos de contrato y ser recuperado, pero en este ejemplo simple se pasa como parámetro cada vez.
-
-El contrato importa el Contrato A en el módulo `contract_a`.
-
-El `contract_a::Client` se construye apuntando al ID de contrato pasado.
-
-El cliente se usa para ejecutar la función `add` con los parámetros `x` y `y` en el Contrato A.
-
-```rust title="cross_contract/contract_b/src/lib.rs"
-mod contract_a {
-    soroban_sdk::contractimport!(
-        file = "../contract_a/target/wasm32v1-none/release/soroban_cross_contract_a_contract.wasm"
-    );
-}
-
-#[contract]
-pub struct ContractB;
-
-#[contractimpl]
-impl ContractB {
-    pub fn add_with(env: Env, contract: Address, x: u32, y: u32) -> u32 {
-        let client = contract_a::Client::new(&env, &contract);
-        client.add(&x, &y)
-    }
-}
-```
-
-### Pruebas
-
-Abre el archivo `cross_contract/contract_b/src/test.rs` para seguir adelante.
-
-```rust title="cross_contract/contract_b/src/test.rs"
-#[test]
-fn test() {
-    let env = Env::default();
-
-    // Register contract A using the imported WASM.
-    let contract_a_id = env.register(contract_a::WASM, ());
-
-    // Register contract B defined in this crate.
-    let contract_b_id = env.register(ContractB, ());
-
-    // Create a client for calling contract B.
-    let client = ContractBClient::new(&env, &contract_b_id);
-
-    // Invoke contract B via its client. Contract B will invoke contract A.
-    let sum = client.add_with(&contract_a_id, &5, &7);
-    assert_eq!(sum, 12);
-}
-```
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno Soroban en el que se ejecutará el contrato.
-
-```rust
-let env = Env::default();
-```
-
-El Contrato A está registrado con el entorno utilizando el Wasm importado.
-
-```rust
-let contract_a_id = env.register(contract_a::WASM, ());
-```
-
-El contrato B está registrado con el entorno utilizando el tipo de contrato y la instancia del contrato se compila en el binario de Rust.
-
-```rust
-let contract_b_id = env.register(ContractB, ());
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente llevará el mismo nombre que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato el tipo de contrato es `ContractB`, y el cliente se llama `ContractBClient`. El cliente puede construirse y usarse de la misma manera en que se puede construir y usar el cliente generado para el Contrato A.
-
-```rust
-let client = ContractBClient::new(&env, &contract_b_id);
-```
-
-El cliente se usa para invocar la función `add_with` en el Contrato B. El Contrato B invocará el Contrato A y el resultado será devuelto.
-
-```rust
-let sum = client.add_with(&contract_a_id, &5, &7);
-```
-
-La prueba verifica que el resultado devuelto sea el que esperamos.
-
-```rust
-assert_eq!(sum, 12);
-```
-
-## Construir los contratos
-
-Para construir el contrato en un archivo `.wasm`, usa el comando `stellar contract build`. Tanto `contract_call/contract_a` como `contract_call/contract_b` deben ser construidos, siendo primero `contract_a`.
-
-```sh
-stellar contract build
-```
-
-Ambos archivos `.wasm` deberían encontrarse en ambos directorios de `target` del contrato después de construir ambos contratos:
-
-```
-target/wasm32v1-none/release/soroban_cross_contract_a_contract.wasm
-```
-
-```
-target/wasm32v1-none/release/soroban_cross_contract_b_contract.wasm
-```
-
-## Ejecutar el contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar funciones de contrato. Ambos contratos deben ser desplegados.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/soroban_cross_contract_a_contract.wasm \
-    --id a
-```
-
-```sh
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/soroban_cross_contract_b_contract.wasm \
-    --id b
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract deploy `
-    --wasm target/wasm32v1-none/release/soroban_cross_contract_a_contract.wasm `
-    --id a
-```
-
-```powershell
-stellar contract deploy `
-    --wasm target/wasm32v1-none/release/soroban_cross_contract_b_contract.wasm `
-    --id b
-```
-
-</TabItem>
-</Tabs>
-
-Invoca la función `add_with` del Contrato B, pasando valores para `x` y `y` (por ejemplo, como `5` y `7`), y luego pasa el ID del contrato del Contrato A.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --id b \
-    -- \
-    add_with \
-    --contract a \
-    --x 5 \
-    --y 7
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --id b `
-    -- `
-    add_with `
-    --contract a `
-    --x 5 `
-    --y 7
-```
-
-</TabItem>
-</Tabs>
-
-La siguiente salida debería ocurrir usando el código anterior.
-
-```
-12
-```
-
-La función `add_with` del Contrato B invocó la función `add` del Contrato A para realizar la suma.
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/custom-account.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/custom-account.mdx
deleted file mode 100644
index ef296709ae..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/custom-account.mdx
+++ /dev/null
@@ -1,455 +0,0 @@
----
-title: Cuenta personalizada
-description: Implementar un contrato de cuenta que admite políticas de autorización multisig y personalizadas.
-sidebar_position: 150
----
-
-<head>
-  <title>
-    {`Implementar un contrato de cuenta que admite políticas de autorización multisig y personalizadas.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Implementar un contrato de cuenta que admite políticas de autorización multisig y personalizadas."
-  />
-  <meta
-    property="og:description"
-    content="Implementar un contrato simple que admite políticas de autorización multisig y personalizables; las cuentas personalizadas se pueden usar con el marco de autenticación y son exclusivas de Soroban."
-  />
-</head>
-
-El [ejemplo de cuenta personalizada] demuestra cómo implementar un contrato de cuenta simple que admite políticas de autorización multisig y personalizables. Este contrato de cuenta se puede usar con el marco de autenticación de Soroban, de modo que cada vez que se usa una `Address` que apunta a esta instancia de contrato, se aplica la lógica personalizada implementada aquí.
-
-Las cuentas personalizadas son exclusivas de Soroban y no se pueden usar para realizar otras operaciones de Stellar.
-
-:::danger
-
-Implementar un contrato de cuenta personalizada requiere un buen entendimiento de autenticación y autorización y requiere pruebas y revisiones rigurosas. El ejemplo aquí _no_ es un contrato de cuenta completo - úsalo solo como referencia de API.
-
-:::
-
-:::caution
-
-Si bien las cuentas personalizadas son admitidas por el protocolo Stellar y el SDK de Soroban, el soporte completo del cliente (como la simulación de transacciones) aún está en desarrollo.
-
-:::
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de cuenta personalizada]: https://github.com/stellar/soroban-examples/tree/v23.0.0/account
-
-## Ejecutar el ejemplo
-
-Primero, sigue el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, evita la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo usa `cargo test`.
-
-```sh
-cargo test -p soroban-account-contract
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test_token_auth ... ok
-```
-
-## Cómo funciona
-
-Abre el archivo `account/src/lib.rs` para seguir adelante.
-
-Los contratos de cuenta implementan una función especial `__check_auth` que toma la carga útil de la firma, firmas y contexto de autorización. La función debería generar un error si la autenticación es rechazada, de lo contrario, se aprobará la autenticación.
-
-Este contrato de ejemplo utiliza claves ed25519 para la verificación de firmas y admite múltiples firmantes de peso igual. También implementa una política que permite establecer límites de gasto por token en las transferencias. El token solo se puede gastar más allá del límite si se proporciona cada firma.
-
-Por ejemplo, el usuario puede inicializar este contrato con 2 claves y establecer un límite de gasto de 100 USDC. De esta manera, pueden usar una sola clave para firmar sus invocaciones de contrato y estar seguros de que incluso si firman una transacción maliciosa, no gastarán más de 100 USDC.
-
-### Inicialización
-
-```rust title="account/src/lib.rs"
-#[contract]
-struct AccountContract;
-
-#[contracttype]
-#[derive(Clone)]
-enum DataKey {
-    SignerCnt,
-    Signer(BytesN<32>),
-    SpendLimit(Address),
-}
-
-...
-
-#[contractimpl]
-impl AccountContract {
-    // Initialize the contract with a list of ed25519 public key ('signers').
-    pub fn __constructor(env: Env, signers: Vec<BytesN<32>>) {
-        // In reality this would need some additional validation on signers
-        // (deduplication etc.).
-        for signer in signers.iter() {
-            env.storage().instance().set(&DataKey::Signer(signer), &());
-        }
-        env.storage()
-            .instance()
-            .set(&DataKey::SignerCnt, &signers.len());
-    }
-
-    ...
-}
-```
-
-Este contrato de cuenta necesita trabajar con las claves públicas de manera explícita. Aquí inicializamos el contrato con claves ed25519.
-
-Utilizamos el constructor para garantizar que la instancia del contrato se cree e inicialice de manera atómica (sin el constructor, existe el riesgo de que alguien adelante la inicialización del contrato y establezca sus propias claves públicas).
-
-### Modificación de política
-
-```rust
-#[contractimpl]
-impl AccountContract {
-    ...
-
-    // Adds a limit on any token transfers that aren't signed by every signer.
-    // For the sake of simplicity of the example the limit is only applied on
-    // a per-authorization basis; the 'real' limits should likely be time-based
-    // instead.
-    pub fn add_limit(env: Env, token: Address, limit: i128) {
-        // The current contract address is the account contract address and has
-        // the same semantics for `require_auth` call as any other account
-        // contract address.
-        // Note, that if a contract *invokes* another contract, then it would
-        // authorize the call on its own behalf and that wouldn't require any
-        // user-side verification.
-        env.current_contract_address().require_auth();
-        env.storage()
-            .instance()
-            .set(&DataKey::SpendLimit(token), &limit);
-    }
-}
-```
-
-Esta función permite a los usuarios establecer y modificar el límite de gasto por token descrito anteriormente. El truco aquí es que `require_auth` se puede usar para la `current_contract_address()`, es decir, el contrato de cuenta puede usarse para verificar la autorización para sus propias funciones administrativas. De esta manera, no hay necesidad de escribir lógica de autorización y autenticación duplicada.
-
-### `__check_auth`
-
-```rust
-#[contracttype]
-#[derive(Clone)]
-pub struct AccSignature {
-    pub public_key: BytesN<32>,
-    pub signature: BytesN<64>,
-}
-
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum AccError {
-    NotEnoughSigners = 1,
-    NegativeAmount = 2,
-    BadSignatureOrder = 3,
-    UnknownSigner = 4,
-}
-
-...
-
-#[contractimpl]
-impl CustomAccountInterface for AccountContract {
-    type Signature = Vec<AccSignature>;
-    type Error = AccError;
-
-    // This is the 'entry point' of the account contract and every account
-    // contract has to implement it. `require_auth` calls for the Address of
-    // this contract will result in calling this `__check_auth` function with
-    // the appropriate arguments.
-    //
-    // This should return `()` if authentication and authorization checks have
-    // been passed and return an error (or panic) otherwise.
-    //
-    // `__check_auth` takes the payload that needed to be signed, arbitrarily
-    // typed signatures (`Vec<AccSignature>` contract type here) and authorization
-    // context that contains all the invocations that this call tries to verify.
-    //
-    // `__check_auth` has to authenticate the signatures. It also may use
-    // `auth_context` to implement additional authorization policies (like token
-    // spend limits here).
-    //
-    // Soroban host guarantees that `__check_auth` is only being called during
-    // `require_auth` verification and hence this may mutate its own state
-    // without the need for additional authorization (for example, this could
-    // store per-time-period token spend limits instead of just enforcing the
-    // limit per contract call).
-    //
-    // Note, that `__check_auth` function shouldn't call `require_auth` on the
-    // contract's own address in order to avoid infinite recursion.
-    #[allow(non_snake_case)]
-    fn __check_auth(
-        env: Env,
-        signature_payload: Hash<32>,
-        signatures: Self::Signature,
-        auth_context: Vec<Context>,
-    ) -> Result<(), AccError> {
-        // Perform authentication.
-        authenticate(&env, &signature_payload, &signatures)?;
-
-        let tot_signers: u32 = env
-            .storage()
-            .instance()
-            .get::<_, u32>(&DataKey::SignerCnt)
-            .unwrap();
-        let all_signed = tot_signers == signatures.len();
-
-        let curr_contract = env.current_contract_address();
-
-        // This is a map for tracking the token spend limits per token. This
-        // makes sure that if e.g. multiple `transfer` calls are being authorized
-        // for the same token we still respect the limit for the total
-        // transferred amount (and not the 'per-call' limits).
-        let mut spend_left_per_token = Map::<Address, i128>::new(&env);
-        // Verify the authorization policy.
-        for context in auth_context.iter() {
-            verify_authorization_policy(
-                &env,
-                &context,
-                &curr_contract,
-                all_signed,
-                &mut spend_left_per_token,
-            )?;
-        }
-        Ok(())
-    }
-}
-```
-
-`__check_auth` es una función especial que implementan los contratos de cuenta. Se llamará por el entorno de Soroban cada vez que se llama a `require_auth` o `require_auth_for_args` para la dirección del contrato de cuenta.
-
-Aquí se implementa en dos pasos. Primero, se realiza la autenticación utilizando la carga útil de la firma y un vector de firmas. En segundo lugar, se aplica la política de autorización utilizando el vector `auth_context`. Este vector contiene todas las llamadas de contrato que están siendo autorizadas por las firmas proporcionadas.
-
-`__check_auth` es una función reservada y solo puede ser llamada por el entorno de Soroban en respuesta a una llamada a `require_auth`. Cualquier llamada directa a `__check_auth` fallará. Esto hace que sea seguro escribir en el almacenamiento del contrato de cuenta desde `__check_auth`, ya que se garantiza que no se llame en un contexto inesperado. En este ejemplo es posible persistir los límites de gasto sin preocuparse de que se agoten debido a que un actor malicioso llame a `__check_auth` directamente.
-
-### Autenticación
-
-```rust
-fn authenticate(
-    env: &Env,
-    signature_payload: &Hash<32>,
-    signatures: &Vec<AccSignature>,
-) -> Result<(), AccError> {
-    for i in 0..signatures.len() {
-        let signature = signatures.get_unchecked(i);
-        if i > 0 {
-            let prev_signature = signatures.get_unchecked(i - 1);
-            if prev_signature.public_key >= signature.public_key {
-                return Err(AccError::BadSignatureOrder);
-            }
-        }
-        if !env
-            .storage()
-            .instance()
-            .has(&DataKey::Signer(signature.public_key.clone()))
-        {
-            return Err(AccError::UnknownSigner);
-        }
-        env.crypto().ed25519_verify(
-            &signature.public_key,
-            &signature_payload.clone().into(),
-            &signature.signature,
-        );
-    }
-    Ok(())
-}
-```
-
-La autenticación aquí simplemente verifica que las firmas proporcionadas son válidas dadas la carga útil y que también pertenecen a los firmantes de este contrato de cuenta.
-
-### Política de autorización
-
-```rust
-fn verify_authorization_policy(
-    env: &Env,
-    context: &Context,
-    curr_contract: &Address,
-    all_signed: bool,
-    spend_left_per_token: &mut Map<Address, i128>,
-) -> Result<(), AccError> {
-    // There are no limitations when every signers signs the transaction.
-    if all_signed {
-        return Ok(());
-    }
-    let contract_context = match context {
-        Context::Contract(c) => {
-            // Allow modifying this contract only if every signer has signed for it.
-            if &c.contract == curr_contract {
-                return Err(AccError::NotEnoughSigners);
-            }
-            c
-        }
-        // Allow creating new contracts only if every signer has signed for it.
-        Context::CreateContractHostFn(_) | Context::CreateContractWithCtorHostFn(_) => {
-            return Err(AccError::NotEnoughSigners);
-        }
-    };
-
-    ...
-}
-```
-
-Verificamos la política por `Context`. es decir, por cada llamada `require_auth` a la dirección de esta cuenta. La política para el contrato de la cuenta en sí exige que cada firmante haya firmado la llamada al método.
-
-```rust
-fn verify_authorization_policy(
-    env: &Env,
-    context: &Context,
-    curr_contract: &Address,
-    all_signed: bool,
-    spend_left_per_token: &mut Map<Address, i128>,
-) -> Result<(), AccError> {
-    ...
-
-    // Besides the checks above we're only interested in functions that spend tokens.
-    if contract_context.fn_name != TRANSFER_FN
-        && contract_context.fn_name != APPROVE_FN
-        && contract_context.fn_name != BURN_FN
-    {
-        return Ok(());
-    }
-
-    let spend_left: Option<i128> =
-        if let Some(spend_left) = spend_left_per_token.get(contract_context.contract.clone()) {
-            Some(spend_left)
-        } else if let Some(limit_left) = env
-            .storage()
-            .instance()
-            .get::<_, i128>(&DataKey::SpendLimit(contract_context.contract.clone()))
-        {
-            Some(limit_left)
-        } else {
-            None
-        };
-
-    // 'None' means that the contract is outside of the policy.
-    if let Some(spend_left) = spend_left {
-        // 'amount' is the third argument in both `approve` and `transfer`.
-        // If the contract has a different signature, it's safer to panic
-        // here, as it's expected to have the standard interface.
-        let spent: i128 = contract_context
-            .args
-            .get(2)
-            .unwrap()
-            .try_into_val(env)
-            .unwrap();
-        if spent < 0 {
-            return Err(AccError::NegativeAmount);
-        }
-        if !all_signed && spent > spend_left {
-            return Err(AccError::NotEnoughSigners);
-        }
-        spend_left_per_token.set(contract_context.contract.clone(), spend_left - spent);
-    }
-    Ok(())
-}
-```
-
-Luego verificamos los nombres de las funciones estándar de tokens y confirmamos que para estas funciones no excedemos los límites de gasto.
-
-### Pruebas
-
-Abre el archivo [`account/src/test.rs`] para seguir el proceso.
-
-[`account/src/test.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/account/src/test.rs
-
-Consulta otros ejemplos para obtener información general sobre la configuración de la prueba.
-
-Aquí solo nos centramos en algunos puntos específicos de los contratos de cuenta.
-
-```rust
-fn sign(e: &Env, signer: &Keypair, payload: &BytesN<32>) -> Val {
-    AccSignature {
-        public_key: signer_public_key(e, signer),
-        signature: signer
-            .sign(payload.to_array().as_slice())
-            .to_bytes()
-            .into_val(e),
-    }
-    .into_val(e)
-}
-```
-
-A diferencia de la mayoría de los contratos que pueden simplemente usar `Address`, los contratos de cuenta se ocupan de la verificación de firmas y, por lo tanto, necesitan realmente firmar las cargas útiles.
-
-```rust
-let payload = BytesN::random(&env);
-let token = Address::generate(&env);
-// `__check_auth` can't be called directly, hence we need to use
-// `try_invoke_contract_check_auth` testing utility that emulates being
-// called by the Soroban host during a `require_auth` call.
-env.try_invoke_contract_check_auth::<AccError>(
-    &account_contract.address,
-    &payload,
-    vec![&env, sign(&env, &signers[0], &payload)].into(),
-    &vec![
-        &env,
-        token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1000),
-    ],
-)
-.unwrap();
-```
-
-`__check_auth` no se puede llamar directamente como funciones de contrato regulares, por lo tanto, necesitamos usar la utilidad de prueba `try_invoke_contract_check_auth` que emula ser llamada por el host de Soroban durante una llamada `require_auth`.
-
-```rust
-// Add a spend limit of 1000 per 1 signer.
-account_contract.add_limit(&token, &1000);
-// Verify that this call needs to be authorized.
-assert_eq!(
-    env.auths(),
-    std::vec![(
-        account_contract.address.clone(),
-        AuthorizedInvocation {
-            function: AuthorizedFunction::Contract((
-                account_contract.address.clone(),
-                symbol_short!("add_limit"),
-                (token.clone(), 1000_i128).into_val(&env),
-            )),
-            sub_invocations: std::vec![]
-        }
-    )]
-);
-```
-
-Afirmar el error específico del contrato a `try_invoke_contract_check_auth` permite verificar el código de error exacto y asegura que la verificación ha fallado debido a la falta de suficientes firmantes y no por ninguna otra razón.
-
-Es una buena idea que el contrato de cuenta tenga códigos de error detallados y verifique que se devuelvan cuando se esperan.
-
-```rust
-// 1 signer no longer can perform the token operation that transfers more
-// than 1000 units.
-assert_eq!(
-    env.try_invoke_contract_check_auth::<AccError>(
-        &account_contract.address,
-        &payload,
-        vec![&env, sign(&env, &signers[0], &payload)].into(),
-        &vec![
-            &env,
-            token_auth_context(&env, &token, Symbol::new(&env, "transfer"), 1001)
-        ],
-    )
-    .err()
-    .unwrap()
-    .unwrap(),
-    AccError::NotEnoughSigners
-);
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/custom-types.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/custom-types.mdx
deleted file mode 100644
index ca0bdf7bbd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/custom-types.mdx
+++ /dev/null
@@ -1,313 +0,0 @@
----
-title: Tipos Personalizados
-description: Define tus propias estructuras de datos en un contrato inteligente.
-sidebar_position: 20
----
-
-<head>
-  <title>Define tus propias estructuras de datos en un contrato inteligente.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Define tus propias estructuras de datos en un contrato inteligente."
-  />
-  <meta
-    property="og:description"
-    content="Define las estructuras de datos que pueden almacenarse en el ledger o usarse como entradas y salidas en las invocaciones de contratos. Pueden ser tanto structs como enums."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de tipos personalizados] muestra cómo definir tus propias estructuras de datos que pueden almacenarse en el ledger o usarse como entradas y salidas en las invocaciones de contratos. Este ejemplo es una extensión del [ejemplo de almacenamiento de datos].
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de tipos personalizados]: https://github.com/stellar/soroban-examples/tree/v23.0.0/custom_types
-[ejemplo de almacenamiento de datos]: ../getting-started/storing-data.mdx
-
-## Ejecutar el Ejemplo
-
-Primero, realiza el proceso de [Configuración] para tener tu entorno de desarrollo configurado, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `custom_types` y usa `cargo test`.
-
-```sh
-cd custom_types
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test ... ok
-```
-
-## Código
-
-```rust title="custom_types/src/lib.rs"
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub struct State {
-    pub count: u32,
-    pub last_incr: u32,
-}
-
-const STATE: Symbol = symbol_short!("STATE");
-
-#[contract]
-pub struct IncrementContract;
-
-#[contractimpl]
-impl IncrementContract {
-    /// Increment increments an internal counter, and returns the value.
-    pub fn increment(env: Env, incr: u32) -> u32 {
-        // Get the current count.
-        let mut state = Self::get_state(env.clone());
-
-        // Increment the count.
-        state.count += incr;
-        state.last_incr = incr;
-
-        // Save the count.
-        env.storage().instance().set(&STATE, &state);
-
-        // Return the count to the caller.
-        state.count
-    }
-    /// Return the current state.
-    pub fn get_state(env: Env) -> State {
-        env.storage().instance().get(&STATE).unwrap_or(State {
-            count: 0,
-            last_incr: 0,
-        }) // If no value set, assume 0.
-    }
-}
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/custom_types
-
-## Cómo Funciona
-
-Los tipos personalizados se definen usando el atributo `#[contracttype]` sobre un `struct` o un `enum`.
-
-Abre el archivo `custom_types/src/lib.rs` para seguir.
-
-### Tipo Personalizado: Estructura
-
-Los structs se almacenan en el ledger como un mapa de pares clave-valor, donde la clave es una cadena de hasta 32 caracteres que representa el nombre del campo y el valor es el valor codificado.
-
-Los nombres de los campos no deben tener más de 32 caracteres.
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub struct State {
-    pub count: u32,
-    pub last_incr: u32,
-}
-```
-
-### Tipo Personalizado: Enumeración
-
-El ejemplo no contiene enumeraciones, pero las enumeraciones también pueden ser tipos de contrato.
-
-Los enums que contienen variantes unitarias y de tupla se almacenan en el ledger como un vector de dos elementos, donde el primer elemento es el nombre de la variante del enum en forma de cadena de hasta 32 caracteres, y el valor es el valor si la variante tiene uno.
-
-Solo se admiten variantes unitarias y variantes de un solo valor, como `A` y `B` en el ejemplo a continuación.
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub enum Enum {
-    A,
-    B(...),
-}
-```
-
-Las enumeraciones que contienen valores enteros se almacenan en el ledger como el valor `u32`.
-
-```rust
-#[contracttype]
-#[derive(Copy, Clone, Debug, Eq, PartialEq)]
-#[repr(u32)]
-pub enum Enum {
-    A = 1,
-    B = 2,
-}
-```
-
-### Uso de Tipos en Funciones
-
-Los tipos que han sido anotados con `#[contracttype]` pueden almacenarse como datos de contrato y recuperarse después.
-
-Los tipos también pueden usarse como entradas y salidas en las funciones del contrato.
-
-```rust
-/// Increment increments an internal counter, and returns the value.
-pub fn increment(env: Env, incr: u32) -> u32 {
-    // Get the current count.
-    let mut state = Self::get_state(env.clone());
-
-    // Increment the count.
-    state.count += incr;
-    state.last_incr = incr;
-
-    // Save the count.
-    env.storage().instance().set(&STATE, &state);
-
-    // Return the count to the caller.
-    state.count
-}
-
-/// Return the current state.
-pub fn get_state(env: Env) -> State {
-    env.storage().instance().get(&STATE).unwrap_or(State {
-        count: 0,
-        last_incr: 0,
-    }) // If no value set, assume 0.
-}
-```
-
-## Pruebas
-
-Abre el archivo `custom_types/src/test.rs` para seguir.
-
-```rust title="custom_types/src/test.rs"
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.increment(&1), 1);
-    assert_eq!(client.increment(&10), 11);
-    assert_eq!(
-        client.get_state(),
-        State {
-            count: 11,
-            last_incr: 10
-        }
-    );
-}
-```
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno Soroban en el que se ejecutará el contrato.
-
-```rust
-let env = Env::default();
-```
-
-El contrato se registra en el entorno usando el tipo de contrato.
-
-```rust
-let contract_id = env.register(IncrementContract, ());
-```
-
-Todas las funciones públicas dentro de un bloque `impl` anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo cliente generado. El tipo cliente tendrá el mismo nombre que el tipo de contrato con "Client" añadido al final. Por ejemplo, en nuestro contrato el tipo de contrato es `IncrementContract`, y el cliente se llama `IncrementContractClient`.
-
-```rust
-let client = IncrementContractClient::new(&env, &contract_id);
-```
-
-La prueba invoca la función `increment` en el contrato registrado, lo que provoca que el tipo `State` se almacene y actualice un par de veces.
-
-```rust
-assert_eq!(client.increment(&1), 1);
-assert_eq!(client.increment(&10), 11);
-```
-
-Luego, la prueba invoca la función `get_state` para obtener el valor `State` almacenado, y puede hacer aserciones sobre sus valores.
-
-```rust
-assert_eq!(
-    client.get_state(),
-    State {
-        count: 11,
-        last_incr: 10
-    }
-);
-```
-
-## Crear el contrato
-
-Para crear el contrato, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-Se debería generar un archivo `.wasm` en el directorio `target`:
-
-```
-target/wasm32v1-none/release/soroban_custom_types_contract.wasm
-```
-
-## Ejecutar el Contrato
-
-Si tienes [`stellar-cli`] instalado, puedes [desplegar] e invocar la función del contrato.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --id CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN \
-    --source-account alice \
-    --network testnet \
-    -- \
-    increment \
-    --incr 5
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --id CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN `
-    --source-account alice `
-    --network testnet `
-    -- `
-    increment `
-    --incr 5
-```
-
-</TabItem>
-</Tabs>
-
-La siguiente salida debería ocurrir al usar el código anterior.
-
-```
-5
-```
-
-Ejecuta varias veces más con diferentes cantidades para incrementar y observa cómo cambia el contador.
-
-Usa el `stellar-cli` para inspeccionar el estado del contador después de varias ejecuciones.
-
-```sh
-stellar contract read --id 1 --key STATE
-```
-
-```
-STATE,"{""count"":25,""last_incr"":15}"
-```
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
-[desplegar]: ../getting-started/deploy-to-testnet
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/deployer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/deployer.mdx
deleted file mode 100644
index a9c4ababd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/deployer.mdx
+++ /dev/null
@@ -1,414 +0,0 @@
----
-title: Desplegador
-description: Desplegar e inicializar un contrato inteligente utilizando otro contrato inteligente.
-sidebar_position: 70
----
-
-<head>
-  <title>
-    {`Desplegar e inicializar un contrato inteligente utilizando otro contrato inteligente.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Desplegar e inicializar un contrato inteligente utilizando otro contrato inteligente."
-  />
-  <meta
-    property="og:description"
-    content="Desplegar un contrato inteligente en nombre de cualquier otra dirección utilizando el SDK `deployer()` e inicializarlo atómicamente."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo del desplegador] demuestra cómo desplegar contratos utilizando un contrato.
-
-Aquí desplegamos un contrato en nombre de cualquier dirección e inicializarlo atómicamente.
-
-:::info
-
-En este ejemplo hay dos contratos que se compilan por separado, y las pruebas despliegan uno con el otro.
-
-:::
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo del desplegador]: https://github.com/stellar/soroban-examples/tree/v23.0.0/deployer
-
-## Ejecutar el Ejemplo
-
-Primero completa el proceso de [Configuración] para tener tu entorno de desarrollo listo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega hasta el directorio `deployer/deployer`, y utiliza `cargo test`.
-
-```sh
-cd deployer/deployer
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test ... ok
-```
-
-## Código
-
-```rust title="deployer/deployer/src/lib.rs"
-#[contract]
-pub struct Deployer;
-
-const ADMIN: Symbol = symbol_short!("admin");
-
-#[contractimpl]
-impl Deployer {
-    /// Construct the deployer with a provided administrator.
-    pub fn __constructor(env: Env, admin: Address) {
-        env.storage().instance().set(&ADMIN, &admin);
-    }
-
-    /// Deploys the contract on behalf of the `Deployer` contract.
-    ///
-    /// This has to be authorized by the `Deployer`s administrator.
-    pub fn deploy(
-        env: Env,
-        wasm_hash: BytesN<32>,
-        salt: BytesN<32>,
-        constructor_args: Vec<Val>,
-    ) -> Address {
-        let admin: Address = env.storage().instance().get(&ADMIN).unwrap();
-        admin.require_auth();
-
-        // Deploy the contract using the uploaded Wasm with given hash on behalf
-        // of the current contract.
-        // Note, that not deploying on behalf of the admin provides more
-        // consistent address space for the deployer contracts - the admin could
-        // change or it could be a completely separate contract with complex
-        // authorization rules, but all the contracts will still be deployed
-        // by the same `Deployer` contract address.
-        let deployed_address = env
-            .deployer()
-            .with_address(env.current_contract_address(), salt)
-            .deploy_v2(wasm_hash, constructor_args);
-
-        deployed_address
-    }
-}
-```
-
-Ref: https://github.com/stellar/soroban-examples/tree/v23.0.0/deployer
-
-## Cómo Funciona
-
-Los contratos pueden desplegar otros contratos utilizando el método `deployer()` del SDK.
-
-La dirección del contrato del contrato desplegado es determinista y se deriva de la dirección del desplegador. El despliegue también debe ser autorizado por el desplegador.
-
-Abre el archivo `deployer/deployer/src/lib.rs` para seguir adelante.
-
-### Carga de Wasm del Contrato
-
-Antes de desplegar las nuevas instancias de contrato, el código Wasm necesita ser cargado en la cadena. Luego se puede usar para desplegar un número arbitrario de instancias de contrato. La carga debería ocurrir típicamente fuera del contrato desplegador, ya que necesita suceder solo una vez. Sin embargo, es posible utilizar la función `env.deployer().upload_contract_wasm()` para cargar Wasm desde un contrato también.
-
-Consulta las [pruebas](#pruebas) para un ejemplo de carga del código del contrato de forma programática. Para la instalación en cadena real, consulta el [tutorial](../../smart-contracts/getting-started/deploy-to-testnet.mdx) de despliegue general.
-
-### Autorización
-
-:::info
-
-Para una introducción a la autorización de Soroban, consulta el [tutorial de autenticación](./auth.mdx).
-
-:::
-
-Comenzamos verificando la autorización del administrador del contrato de despliegue. Sin eso, cualquiera podría llamar a la función `deploy` con cualquier argumento, lo cual no siempre puede ser deseable (sin embargo, hay contratos donde está perfectamente bien tener despliegues sin permisos).
-
-```rust
-let admin: Address = env.storage().instance().get(&ADMIN).unwrap();
-admin.require_auth();
-```
-
-`deployer().with_address()` también realiza la autorización. Sin embargo, como desplegamos en nombre del contrato actual, se considera que la llamada ha sido autorizada implícitamente.
-
-Consulta más detalles sobre las cargas útiles de autorización reales en [tests](#tests).
-
-### `env.deployer()`
-
-La función del SDK `env.deployer()` incluye algunas utilidades relacionadas con el despliegue. Aquí usamos el tipo de 'deployer' más genérico, `with_address(env.current_contract_address(), salt)`.
-
-```rust
-let deployed_address = env
-    .deployer()
-    .with_address(env.current_contract_address(), salt)
-    .deploy_v2(wasm_hash, constructor_args);
-```
-
-`with_address()` recibe la dirección del `deployer` y el `salt`. Ambos se utilizan para derivar la dirección del contrato desplegado de manera determinista. No es posible volver a desplegar un contrato que ya existe.
-
-:::tip
-
-La llamada `env.deployer().with_address(env.current_contract_address(), salt)` puede ser reemplazada por la función `env.deployer().with_current_contract(salt)` para mayor brevedad.
-
-:::
-
-La función `deploy_v2()` realiza el despliegue real usando el `wasm_hash` proporcionado. La implementación del nuevo contrato se define por el archivo Wasm cargado bajo `wasm_hash`. `constructor_args` son los argumentos que se pasarán al constructor del contrato que se está desplegando. Si el contrato desplegado no tiene constructor, se debe pasar un vector de argumentos vacío.
-
-:::tip
-
-Solo el `wasm_hash` en sí se almacena por ID de contrato, lo que ahorra espacio en el ledger y tarifas.
-
-:::
-
-### Pruebas
-
-Abre el archivo [`deployer/deployer/src/test.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/deployer/deployer/src/test.rs) para seguir el contenido.
-
-#### Contrato a desplegar
-
-Empieza importando el contrato de prueba Wasm que se va a desplegar.
-
-```rust title="deployer/deployer/src/test.rs"
-// The contract that will be deployed by the deployer contract.
-mod contract {
-    soroban_sdk::contractimport!(
-        file = "../contract/target/wasm32v1-none/release/soroban_deployer_test_contract.wasm"
-    );
-}
-```
-
-Ese contrato contiene el siguiente código que exporta dos funciones: una función constructor que toma un valor y una función getter para el valor almacenado.
-
-```rust title="deployer/contract/src/lib.rs"
-#[contract]
-pub struct Contract;
-
-const KEY: Symbol = symbol_short!("value");
-
-#[contractimpl]
-impl Contract {
-    pub fn __constructor(env: Env, value: u32) {
-        env.storage().instance().set(&KEY, &value);
-    }
-
-    pub fn value(env: Env) -> u32 {
-        env.storage().instance().get(&KEY).unwrap()
-    }
-}
-```
-
-Ref: https://github.com/stellar/soroban-examples/tree/v23.0.0/deployer
-
-Este contrato de prueba será utilizado al probar el desplegador. El contrato de despliegue desplegará el contrato de prueba e invocará su constructor.
-
-#### Código de prueba
-
-```rust title="deployer/deployer/src/test.rs"
-#[test]
-fn test() {
-    let env = Env::default();
-    let admin = Address::generate(&env);
-    let deployer_client = DeployerClient::new(&env, &env.register(Deployer, (&admin,)));
-
-    // Upload the Wasm to be deployed from the deployer contract.
-    // This can also be called from within a contract if needed.
-    let wasm_hash = env.deployer().upload_contract_wasm(contract::WASM);
-
-    // Deploy contract using deployer, and include an init function to call.
-    let salt = BytesN::from_array(&env, &[0; 32]);
-    let constructor_args: Vec<Val> = (5u32,).into_val(&env);
-    env.mock_all_auths();
-    let contract_id = deployer_client.deploy(&wasm_hash, &salt, &constructor_args);
-
-    // An authorization from the admin is required.
-    let expected_auth = AuthorizedInvocation {
-        // Top-level authorized function is `deploy` with all the arguments.
-        function: AuthorizedFunction::Contract((
-            deployer_client.address,
-            symbol_short!("deploy"),
-            (wasm_hash.clone(), salt, constructor_args).into_val(&env),
-        )),
-        sub_invocations: vec![],
-    };
-    assert_eq!(env.auths(), vec![(admin, expected_auth)]);
-
-    // Invoke contract to check that it is initialized.
-    let client = contract::Client::new(&env, &contract_id);
-    let sum = client.value();
-    assert_eq!(sum, 5);
-}
-```
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno Soroban en el que se ejecutará el contrato.
-
-```rust
-let env = Env::default();
-```
-
-Registra el contrato desplegador con el entorno y crea un cliente para él. El contrato se inicializa con la dirección del administrador durante el registro.
-
-```rust
-let admin = Address::generate(&env);
-let deployer_client = DeployerClient::new(&env, &env.register(Deployer, (&admin,)));
-```
-
-Carga el código del contrato de prueba que hemos importado anteriormente a través de `contractimport!` y obtiene el hash del código Wasm subido.
-
-```rust
-let wasm_hash = env.deployer().upload_contract_wasm(contract::WASM);
-```
-
-El cliente se usa para invocar la función `deploy`. El contrato desplegará el contrato de prueba utilizando el hash de su código Wasm y pasará un único argumento `5u32` a su constructor. También necesitamos el `salt` para pasarlo en la llamada para generar un identificador único del contrato de salida.
-
-```rust
-let salt = BytesN::from_array(&env, &[0; 32]);
-let constructor_args: Vec<Val> = (5u32,).into_val(&env);
-```
-
-Antes de invocar el contrato, necesitamos habilitar la autorización simulada para obtener la carga de autorización registrada que podemos verificar.
-
-```rust
-env.mock_all_auths();
-```
-
-Después de las preparaciones anteriores, realmente podemos llamar a la función `deploy`.
-
-```rust
-let contract_id = deployer_client.deploy(&wasm_hash, &salt, &constructor_args);
-```
-
-El despliegue requiere autorización del administrador. Como se mencionó anteriormente, la autorización necesaria para la función `deploy_v2` se realiza en nombre del contrato de despliegue y es implícita. Esto se puede verificar en la prueba examinando `env.auths()`.
-
-```rust
-// An authorization from the admin is required.
-let expected_auth = AuthorizedInvocation {
-    // Top-level authorized function is `deploy` with all the arguments.
-    function: AuthorizedFunction::Contract((
-        deployer_client.address,
-        symbol_short!("deploy"),
-        (wasm_hash.clone(), salt, constructor_args).into_val(&env),
-    )),
-    sub_invocations: vec![],
-};
-assert_eq!(env.auths(), vec![(admin, expected_auth)]);
-```
-
-La prueba verifica que el contrato de prueba fue desplegado utilizando su cliente para invocarlo y obtener de regreso el valor establecido durante la inicialización.
-
-```rust
-// Invoke contract to check that it is initialized.
-let client = contract::Client::new(&env, &contract_id);
-let sum = client.value();
-assert_eq!(sum, 5);
-```
-
-## Construir los Contratos
-
-Para construir el contrato en un archivo `.wasm`, utiliza el comando `stellar contract build`. Construye tanto el contrato desplegador como el contrato de prueba.
-
-```sh
-stellar contract build
-```
-
-Ambos archivos `.wasm` deberían encontrarse en los directorios `target` de ambos contratos después de construir ambos contratos:
-
-```
-target/wasm32v1-none/release/soroban_deployer_contract.wasm
-```
-
-```
-target/wasm32v1-none/release/soroban_deployer_test_contract.wasm
-```
-
-## Ejecutar el Contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar la función del contrato para desplegar el contrato de prueba.
-
-Antes de desplegar el contrato de prueba con el desplegador, instala el Wasm del contrato de prueba usando el comando `install`. El comando `install` imprimirá el hash derivado del archivo Wasm (no es solo el hash del archivo Wasm en sí) que debería ser utilizado por el desplegador.
-
-```sh
-stellar contract upload --wasm contract/target/wasm32v1-none/release/soroban_deployer_test_contract.wasm
-```
-
-El comando imprime el hash en formato hexadecimal. Debería verse algo así como `7792a624b562b3d9414792f5fb5d72f53b9838fef2ed9a901471253970bc3b15`.
-
-También necesitamos desplegar el contrato `Desplegador`:
-
-```sh
-stellar contract deploy --wasm deployer/target/wasm32v1-none/release/soroban_deployer_contract.wasm --alias 1
-```
-
-Esto devolverá la dirección del desplegador: `CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD2KM`.
-
-Luego el contrato desplegador puede ser invocado con el valor hash de Wasm anterior.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke --id 1 -- deploy \
-    --deployer CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD2KM
-    --salt 123 \
-    --wasm_hash 7792a624b562b3d9414792f5fb5d72f53b9838fef2ed9a901471253970bc3b15 \
-    --constructor_args '[{"u32":5}]'
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke --id 1 -- deploy `
-    --deployer CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD2KM
-    --salt 123 `
-    --wasm_hash 7792a624b562b3d9414792f5fb5d72f53b9838fef2ed9a901471253970bc3b15 `
-    --constructor_args '[{"u32":5}]'
-```
-
-</TabItem>
-</Tabs>
-
-Y luego invoca el contrato de prueba desplegado utilizando el identificador devuelto del comando anterior.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --id ead19f55aec09bfcb555e09f230149ba7f72744a5fd639804ce1e934e8fe9c5d \
-    -- \
-    value
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --id ead19f55aec09bfcb555e09f230149ba7f72744a5fd639804ce1e934e8fe9c5d `
-    -- `
-    value
-```
-
-</TabItem>
-</Tabs>
-
-La siguiente salida debería ocurrir utilizando el código anterior.
-
-```
-5
-```
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/errors.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/errors.mdx
deleted file mode 100644
index ad5dc83257..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/errors.mdx
+++ /dev/null
@@ -1,402 +0,0 @@
----
-title: Errores
-description: Definir y generar errores en un contrato inteligente.
-sidebar_position: 30
----
-
-<head>
-  <title>Definir y generar errores en un contrato inteligente.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Definir y generar errores en un contrato inteligente."
-  />
-  <meta
-    property="og:description"
-    content="Definir y generar errores en un contrato inteligente que los invocadores del contrato pueden entender y manejar."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de errores] demuestra cómo definir y generar errores en un contrato que los invocadores del contrato pueden entender y manejar. Este ejemplo es una extensión del [ejemplo de almacenamiento de datos].
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de errores]: https://github.com/stellar/soroban-examples/tree/v23.0.0/errors
-[ejemplo de almacenamiento de datos]: ../getting-started/storing-data.mdx
-
-## Ejecutar el ejemplo
-
-Primero completa el proceso de [Configuración] para preparar tu entorno de desarrollo y luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `errors`, y usa `cargo test`.
-
-```sh
-cd errors
-cargo test
-```
-
-Deberías ver una salida que comienza así:
-
-```
-running 2 tests
-test test::test ... ok
-test test::test_panic - should panic ... ok
-
-[Diagnostic Event] contract:CAAA..., topics:[log], data:["count: {}", 0]
-[Diagnostic Event] contract:CAAA..., topics:[log], data:["count: {}", 1]
-[Diagnostic Event] contract:CAAA..., topics:[log], data:["count: {}", 2]
-[Diagnostic Event] contract:CAAA..., topics:[log], data:["count: {}", 3]
-[Diagnostic Event] contract:CAAA..., topics:[log], data:["count: {}", 4]
-[Diagnostic Event] contract:CAAA..., topics:[log], data:["count: {}", 5]
-[Failed Diagnostic Event (not emitted)] contract:CAAA..., topics:[log], data:["count: {}", 5]
-
-thread 'test::test_panic' panicked at .../src/host.rs: HostError: Error(Contract, #1)
-
-Event log (newest first):
-   0: [Diagnostic Event] topics:[error, Error(Contract, #1)], data:"escalating error to panic"
-   1: [Diagnostic Event] topics:[error, Error(Contract, #1)], data:["contract call failed", increment, []]
-   2: [Failed Diagnostic Event (not emitted)] contract:CAAA..., topics:[error, Error(Contract, #1)], data:"escalating Ok(ScErrorType::Contract) frame-exit to Err"
-   3: [Failed Diagnostic Event (not emitted)] contract:CAAA..., topics:[fn_return, increment], data:Error(Contract, #1)
-   4: [Failed Diagnostic Event (not emitted)] contract:CAAA..., topics:[log], data:["count: {}", 5]
-   5: [Diagnostic Event] topics:[fn_call, CAAA..., increment], data:Void
-...
-
-successes:
-    test::test
-    test::test_panic
-
-test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.16s
-```
-
-## Código
-
-```rust title="errors/src/lib.rs"
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum Error {
-    LimitReached = 1,
-}
-
-const COUNTER: Symbol = symbol_short!("COUNTER");
-const MAX: u32 = 5;
-
-#[contract]
-pub struct IncrementContract;
-
-#[contractimpl]
-impl IncrementContract {
-    /// Increment increments an internal counter, and returns the value. Errors
-    /// if the value is attempted to be incremented past 5.
-    pub fn increment(env: Env) -> Result<u32, Error> {
-        // Get the current count.
-        let mut count: u32 = env.storage().instance().get(&COUNTER).unwrap_or(0); // If no value set, assume 0.
-        log!(&env, "count: {}", count);
-
-        // Increment the count.
-        count += 1;
-
-        // Check if the count exceeds the max.
-        if count <= MAX {
-            // Save the count.
-            env.storage().instance().set(&COUNTER, &count);
-
-            // Return the count to the caller.
-            Ok(count)
-        } else {
-            // Return an error if the max is exceeded.
-            Err(Error::LimitReached)
-        }
-    }
-}
-```
-
-Ref: https://github.com/stellar/soroban-examples/tree/v23.0.0/errors
-
-## Cómo funciona
-
-Abre el archivo [`errors/src/lib.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/errors/src/lib.rs) para seguir el ejemplo.
-
-### Definiendo un error
-
-Los errores de contrato son enumeraciones Rust u32 donde cada variante de la enumeración tiene un valor entero asignado. El atributo `#[contracterror]` se utiliza para configurar el error para que pueda ser utilizado en el valor de retorno de las funciones del contrato.
-
-La enumeración tiene algunas restricciones:
-
-- Debe tener el atributo `#[repr(u32)]`.
-- Debe tener el atributo `#[derive(Copy)]`.
-- Cada variante debe tener un valor entero explícito asignado.
-
-```rust
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum Error {
-    LimitReached = 1,
-}
-```
-
-Los errores de contrato no pueden ser almacenados como datos de contrato y, por lo tanto, no pueden ser usados como tipos en campos de tipos de contrato.
-
-:::tip
-
-Si se devuelve un error de una función, todo lo que la función ha hecho es revertido. Si las entradas del ledger han sido alteradas o se han almacenado datos del contrato, todos esos cambios son revertidos y no serán persistidos.
-
-:::
-
-### Devolviendo un error
-
-Los errores pueden ser devueltos desde las funciones de contrato devolviendo `Result<_, E>`.
-
-La función de incremento devuelve un `Result<u32, Error>`, lo que significa que devuelve `Ok(u32)` en el caso exitoso y `Err(Error)` en el caso de error.
-
-```rust
-pub fn increment(env: Env) -> Result<u32, Error> {
-    // ...
-    if count <= MAX {
-        // ...
-        Ok(count)
-    } else {
-        // ...
-        Err(Error::LimitReached)
-    }
-}
-```
-
-### Entrando en pánico con un error
-
-Los errores también pueden provocarse en lugar de ser devueltos desde la función.
-
-La función de incremento también podría ser escrita como sigue con un valor de retorno `u32`. El error puede ser pasado al entorno usando el macro `panic_with_error!`.
-
-```rust
-pub fn increment(env: Env) -> u32 {
-    // ...
-    if count <= MAX {
-        // ...
-        count
-    } else {
-        // ...
-        panic_with_error!(&env, Error::LimitReached)
-    }
-}
-```
-
-:::caution
-
-Las funciones que no devuelven un tipo `Result<_, E>` no especifican cuáles son los posibles valores de error. Esto hace que sea más difícil para otros contratos y clientes integrarse con el contrato. Sin embargo, esto podría ser ideal si los errores son diagnósticos y de depuración, y no están destinados a ser manejados.
-
-:::
-
-## Pruebas
-
-Abre el archivo [`errors/src/test.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/errors/src/test.rs) para seguir el ejemplo.
-
-```rust title="errors/src/test.rs"
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.try_increment(), Ok(Ok(1)));
-    assert_eq!(client.try_increment(), Ok(Ok(2)));
-    assert_eq!(client.try_increment(), Ok(Ok(3)));
-    assert_eq!(client.try_increment(), Ok(Ok(4)));
-    assert_eq!(client.try_increment(), Ok(Ok(5)));
-    assert_eq!(client.try_increment(), Err(Ok(Error::LimitReached)));
-
-    std::println!("{}", env.logs().all().join("\n"));
-}
-
-#[test]
-#[should_panic(expected = "HostError: Error(Contract, #1)")]
-fn test_panic() {
-    let env = Env::default();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.increment(), 1);
-    assert_eq!(client.increment(), 2);
-    assert_eq!(client.increment(), 3);
-    assert_eq!(client.increment(), 4);
-    assert_eq!(client.increment(), 5);
-    client.increment();
-}
-```
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno de Soroban en el que el contrato se ejecutará.
-
-```rust
-let env = Env::default();
-```
-
-El contrato se registra con el entorno usando el tipo de contrato.
-
-```rust
-let contract_id = env.register(IncrementContract, ());
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente tendrá el mismo nombre que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato, el tipo de contrato es `IncrementContract`, y el cliente se llama `IncrementContractClient`.
-
-```rust
-let client = IncrementContractClient::new(&env, &contract_id);
-```
-
-Se generan dos funciones para cada función de contrato, una que devuelve un `Result<>`, y la otra que no maneja errores y se bloquea si ocurre un error.
-
-### `try_increment`
-
-En la primera prueba, se llama a la función `try_increment` y devuelve `Result<Result<u32, _>, Result<Error, InvokeError>>`.
-
-```rust
-assert_eq!(client.try_increment(), Ok(Ok(5)));
-assert_eq!(client.try_increment(), Err(Ok(Error::LimitReached)));
-```
-
-- Si la llamada a la función es exitosa, se devuelve `Ok(Ok(u32))`.
-- Si la llamada a la función es exitosa pero devuelve un valor que no es `u32`, se devuelve `Ok(Err(_))`.
-- Si la llamada a la función no tiene éxito y falla con un error en el enum `Error`, se devuelve `Err(Ok(Error))`.
-- Si la llamada a la función no tiene éxito, pero devuelve un código de error que no está en el enum `Error`, o devuelve un código de error del sistema, se devuelve `Err(Err(InvokeError))` y se puede inspeccionar el `InvokeError`.
-
-### `increment`
-
-En la segunda prueba, se llama a la función `increment` y devuelve `u32`. Cuando se realiza la última llamada, la función tiene un pánico.
-
-```rust
-assert_eq!(client.increment(), 5);
-client.increment();
-```
-
-- Si la llamada a la función es exitosa, se devuelve `u32`.
-- Si la llamada a la función es exitosa pero devuelve un valor que no es `u32`, se produce un pánico.
-- Si la llamada a la función no tiene éxito, se produce un pánico.
-
-## Crear el contrato
-
-Para crear el contrato, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-Un archivo `.wasm` debería ser generado en el directorio `target`:
-
-```
-target/wasm32v1-none/release/soroban_errors_contract.wasm
-```
-
-## Ejecutar el contrato
-
-Despliegue el contrato en Testnet para que podamos ejecutarlo. El valor proporcionado como `--source-account` se configuró en nuestra guía Comenzar; por favor, cámbialo en consecuencia si creaste una identidad diferente.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract deploy \
-  --wasm target/wasm32v1-none/release/soroban_errors_contract.wasm \
-  --source-account alice \
-  --network testnet
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract deploy `
-  --wasm target/wasm32v1-none/release/soroban_errors_contract.wasm `
-  --source-account alice `
-  --network testnet
-```
-
-</TabItem>
-</Tabs>
-
-El comando anterior mostrará el ID del contrato, que en nuestro caso es `CA4KWO3HL6M5F5MZ5ITVFLCQ6ZM2GDSP2NOTNXOT4GIRECQOVX3I6CXL`.
-
-Ahora que hemos desplegado el contrato, podemos invocarlo.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --id CA4KWO3HL6M5F5MZ5ITVFLCQ6ZM2GDSP2NOTNXOT4GIRECQOVX3I6CXL \
-    --network testnet \
-    --source-account alice \
-    -- \
-    increment
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --id CA4KWO3HL6M5F5MZ5ITVFLCQ6ZM2GDSP2NOTNXOT4GIRECQOVX3I6CXL `
-    --network testnet `
-    --source-account alice `
-    -- `
-    increment
-```
-
-</TabItem>
-</Tabs>
-
-Ejecuta el comando varias veces y en la sexta invocación deberías ver un error como este:
-
-```
-❌ error: transaction simulation failed: HostError: Error(Contract, #1)
-
-Event log (newest first):
-   0: [Diagnostic Event] contract:CA4KWO3HL6M5F5MZ5ITVFLCQ6ZM2GDSP2NOTNXOT4GIRECQOVX3I6CXL, topics:[error, Error(Contract, #1)], data:"escalating Ok(ScErrorType::Contract) frame-exit to Err"
-   1: [Diagnostic Event] topics:[fn_call, CA4KWO3HL6M5F5MZ5ITVFLCQ6ZM2GDSP2NOTNXOT4GIRECQOVX3I6CXL, increment], data:Void
-```
-
-Para recuperar el valor actual del contador, usa el comando `stellar contract read`.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract read \
-  --id CA4KWO3HL6M5F5MZ5ITVFLCQ6ZM2GDSP2NOTNXOT4GIRECQOVX3I6CXL \
-  --network testnet \
-  --source-account alice \
-  --durability persistent \
-  --output json
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract read `
-  --id CA4KWO3HL6M5F5MZ5ITVFLCQ6ZM2GDSP2NOTNXOT4GIRECQOVX3I6CXL `
-  --network testnet `
-  --source-account alice `
-  --durability persistent `
-  --output json
-```
-
-</TabItem>
-</Tabs>
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/events.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/events.mdx
deleted file mode 100644
index 2b5b21925c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/events.mdx
+++ /dev/null
@@ -1,319 +0,0 @@
----
-title: Eventos
-description: Publicar eventos desde un contrato inteligente.
-sidebar_position: 10
----
-
-<head>
-  <title>Publicar eventos desde un contrato inteligente.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Publicar eventos desde un contrato inteligente." />
-  <meta
-    property="og:description"
-    content="Publicar eventos desde un contrato inteligente. Los eventos del contrato permiten a los contratos emitir información sobre lo que el contrato está haciendo utilizando la función de publicación de eventos del entorno. "
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de eventos] demuestra cómo publicar eventos desde un contrato. Este ejemplo es una extensión del [ejemplo de almacenamiento de datos].
-
-:::tip[Whisk Cambios]
-
-Con el lanzamiento de Whisk, Protocolo 23, la sintaxis para publicar eventos de smart contracts ha cambiado. Para proporcionar la información más actualizada, este ejemplo ha sido actualizado para incluir los nuevos patrones. Encuentra información más detallada en la [documentación del SDK de Rust].
-
-:::
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de eventos]: https://github.com/stellar/soroban-examples/tree/v23.0.0/events
-[ejemplo de almacenamiento de datos]: ../getting-started/storing-data.mdx
-[documentación del SDK de Rust]: https://docs.rs/soroban-sdk/latest/soroban_sdk/_migrating/v23_contractevent/index.html
-
-## Ejecutar el ejemplo
-
-Primero sigue el proceso de [Configuración] para configurar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O bien, puedes evitar la configuración del entorno de desarrollo y abrir este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `events`, y usa `cargo test`.
-
-```sh
-cd events
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test ... ok
-```
-
-## Código
-
-```rust title="events/src/lib.rs"
-const COUNTER: Symbol = symbol_short!("COUNTER");
-
-// Define two static topics for the event: "COUNTER" and "increment".
-// Also set the data format to "single-value", which means that the event data
-// payload will contain a single value not nested into any data structure.
-#[contractevent(topics = ["COUNTER", "increment"], data_format = "single-value")]
-struct IncrementEvent {
-    count: u32,
-}
-
-#[contract]
-pub struct IncrementContract;
-
-#[contractimpl]
-impl IncrementContract {
-    /// Increment increments an internal counter, and returns the value.
-    pub fn increment(env: Env) -> u32 {
-        // Get the current count.
-        let mut count: u32 = env.storage().instance().get(&COUNTER).unwrap_or(0); // If no value set, assume 0.
-
-        // Increment the count.
-        count += 1;
-
-        // Save the count.
-        env.storage().instance().set(&COUNTER, &count);
-
-        // Publish an event about the increment occuring.
-        // The event has two static topics ("COUNTER", "increment") and actual
-        // count as the data payload.
-        IncrementEvent { count }.publish(&env);
-
-        // Return the count to the caller.
-        count
-    }
-}
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/events
-
-## Cómo funciona
-
-Este contrato de ejemplo extiende el ejemplo de incremento publicando un evento cada vez que se incrementa el contador.
-
-Los eventos del contrato permiten a los contratos emitir información sobre lo que su contrato está haciendo. Los contratos pueden publicar eventos creando una `struct` definida y `publicándola` en los entornos de smart contracts.
-
-Primero, debe definirse la estructura `#[contractevent]`
-
-```rust
-#[contractevent(topics = ["COUNTER", "increment"], data_format = "single-value")]
-struct IncrementEvent {
-    count: u32,
-}
-```
-
-Luego, dentro de la función del contrato, podemos crear y publicar el evento con los datos relevantes.
-
-```rust
-IncrementEvent { count }.publish(&env);
-```
-
-### Temas de eventos
-
-Los temas pueden definirse de forma estática o dinámica. En el código de ejemplo se usan dos temas estáticos, que serán del tipo `Symbol`: `COUNTER` e `increment`.
-
-```rust
-#[contractevent(topics = ["COUNTER", "increment"], ...)]
-```
-
-:::tip
-
-Los temas no tienen que estar hechos del mismo tipo.
-
-:::
-
-Los temas también pueden definirse dinámicamente, dentro de la estructura. En este caso, el nombre en `snake_case` de la estructura será el primer tema. Por ejemplo, el siguiente evento tendrá dos temas: el `Symbol` "increment", seguido por una `Address`.
-
-```rust
-#[contractevent]
-pub struct Increment {
-    #[topic]
-    addr: Address,
-    count: u32,
-}
-```
-
-### Datos del evento
-
-Un evento también contiene un objeto de datos de cualquier valor o tipo, incluyendo tipos definidos por contratos utilizando `#[contracttype]`. En el ejemplo, los datos son el conteo `u32`. En el ejemplo, los datos son el conteo `u32`. El `data_format = "single-value"` indica que el evento publique solo los datos, sin estructura adicional alrededor.
-
-```rust
-#[contractevent(..., data_format = "single-value")]
-```
-
-Por defecto, los datos del evento cumplirán con la estructura definida en la `struct`. El `data_format` también puede especificarse como `vec` o `single-value`. Nuevamente, consulta la [documentación del Rust SDK] para más detalles.
-
-### Publicar
-
-Publicar un evento se realiza llamando a la función `publish` sobre la estructura del evento creada. La función no retorna nada si tiene éxito, y causa pánico en caso de falla. Las razones de fallo pueden incluir entradas mal formadas (por ejemplo, el conteo de temas excede el límite) y agotar el presupuesto de recursos (TBD). Una vez publicado exitosamente, el nuevo evento estará disponible para aplicaciones que consuman los eventos.
-
-```rust
-IncrementEvent { count }.publish(&env);
-```
-
-:::caution
-
-Los eventos publicados se descartan si una invocación de contrato falla debido a un pánico, agotamiento del presupuesto, o cuando el contrato retorna un error.
-
-:::
-
-## Pruebas
-
-Abre el archivo [`events/src/test.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/events/src/test.rs) para seguir el ejemplo.
-
-```rust title="events/src/test.rs"
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.increment(), 1);
-    assert_eq!(
-        env.events().all(),
-        vec![
-            &env,
-            (
-                contract_id.clone(),
-                (symbol_short!("COUNTER"), symbol_short!("increment")).into_val(&env),
-                1u32.into_val(&env)
-            ),
-        ]
-    );
-    assert_eq!(client.increment(), 2);
-    assert_eq!(
-        env.events().all(),
-        vec![
-            &env,
-            (
-                contract_id.clone(),
-                (symbol_short!("COUNTER"), symbol_short!("increment")).into_val(&env),
-                2u32.into_val(&env)
-            ),
-        ]
-    );
-    assert_eq!(client.increment(), 3);
-    assert_eq!(
-        env.events().all(),
-        vec![
-            &env,
-            (
-                contract_id,
-                (symbol_short!("COUNTER"), symbol_short!("increment")).into_val(&env),
-                3u32.into_val(&env)
-            ),
-        ]
-    );
-}
-```
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno de Soroban en el que el contrato se ejecutará.
-
-```rust
-let env = Env::default();
-```
-
-El contrato se registra con el entorno utilizando el tipo de contrato.
-
-```rust
-let contract_id = env.register(IncrementContract, ());
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente se llamará igual que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato el tipo de contrato es `IncrementContract`, y el cliente se llama `IncrementContractClient`.
-
-```rust
-let client = IncrementContractClient::new(&env, &contract_id);
-```
-
-El ejemplo invoca el contrato varias veces.
-
-```rust
-assert_eq!(client.increment(), 1);
-```
-
-El ejemplo verifica que el evento fue publicado.
-
-```rust
-assert_eq!(
-    env.events().all(),
-    vec![
-        &env,
-        (
-            contract_id.clone(),
-            (symbol_short!("COUNTER"), symbol_short!("increment")).into_val(&env),
-            1u32.into_val(&env)
-        ),
-    ]
-);
-```
-
-## Construir el contrato
-
-Para construir el contrato, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-Un archivo `.wasm` debería generarse en el directorio `target`:
-
-```
-target/wasm32v1-none/release/soroban_events_contract.wasm
-```
-
-## Ejecutar el contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar funciones del contrato utilizándolo.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --wasm target/wasm32v1-none/release/soroban_events_contract.wasm \
-    --id 1 \
-    -- \
-    increment
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --wasm target/wasm32v1-none/release/soroban_events_contract.wasm `
-    --id 1 `
-    -- `
-    increment
-```
-
-</TabItem>
-</Tabs>
-
-La siguiente salida debería ocurrir utilizando el código anterior.
-
-```
-📅 CAAA... - Success - Event: [{"symbol":"COUNTER"},{"symbol":"increment"}] = {"u32":1}
-1
-```
-
-Se muestra un solo evento, que es el evento del contrato que el contrato publicó. El evento contiene los dos temas, cada uno un `Symbol`, y el objeto de datos que contiene el `u32`.
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/fungible-token.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/fungible-token.mdx
deleted file mode 100644
index f36a3912a4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/fungible-token.mdx
+++ /dev/null
@@ -1,297 +0,0 @@
----
-title: Token Fungible
-description: Contrato desarrollado y auditado por OpenZeppelin para tokens fungibles en Stellar.
-sidebar_position: 141
----
-
-<head>
-  <title>Token Fungible por OpenZeppelin</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Token Fungible por OpenZeppelin" />
-  <meta
-    property="og:description"
-    content="Contrato desarrollado y auditado por OpenZeppelin para tokens fungibles en Stellar"
-  />
-</head>
-
-# Token Fungible
-
-[Código Fuente](https://github.com/OpenZeppelin/stellar-contracts/tree/main/packages/tokens/src/fungible)
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=openzeppelin/stellar-contracts&editor=web
-
-Los tokens fungibles representan activos donde cada unidad es idéntica e intercambiable, como monedas, productos básicos o tokens de utilidad. En Stellar, puedes crear tokens fungibles donde cada token tiene el mismo valor y propiedades, con saldos y propiedad rastreados a través de contratos inteligentes Soroban.
-
-## Resumen
-
-El módulo [fungible](https://github.com/OpenZeppelin/stellar-contracts/tree/main/packages/tokens/src/fungible) ofrece tres variantes diferentes de Token Fungible que difieren en cómo se manejan ciertas funciones como transferencias y aprobaciones de tokens:
-
-El módulo proporciona varias opciones de implementación para adaptarse a diferentes casos de uso:
-
-1. **Implementación base** (`FungibleToken` con tipo de contrato `Base`): Adecuado para la mayoría de casos de uso estándar de tokens.
-2. **Extensión AllowList** (`FungibleToken` con tipo de contrato `AllowList`): Para tokens que requieren un mecanismo de lista de permitidos para controlar quién puede transferir tokens.
-3. **Extensión BlockList** (`FungibleToken` con tipo de contrato `BlockList`): Para tokens que necesitan bloquear direcciones específicas de realizar transferencias.
-
-Estas implementaciones comparten funcionalidad central y una interfaz común, exponiendo funciones de contrato idénticas como puntos de entrada. Sin embargo, las extensiones proporcionan un comportamiento especializado al sobrescribir ciertas funciones para implementar sus requisitos específicos.
-
-## Ejecutar el Ejemplo
-
-Primero pasa por el proceso de [Configuración] para tener tu entorno de desarrollo configurado, luego clona el repositorio OpenZeppelin Stellar Contracts:
-
-```sh
-git clone https://github.com/OpenZeppelin/stellar-contracts
-cd stellar-contracts
-```
-
-O, salta la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces] o [Code Anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `fungible-token-interface` y usa `cargo test`.
-
-```sh
-cd examples/fungible-token-interface
-cargo test
-```
-
-[configuración]: ../getting-started/setup.mdx
-[GitHub Codespaces]: https://github.com/codespaces/new?repo=OpenZeppelin/stellar-contracts&editor=web
-[Code Anywhere]: https://app.codeanywhere.com/#https://github.com/OpenZeppelin/stellar-contracts
-
-## Código
-
-:::note
-
-Este ejemplo muestra cómo usar la biblioteca OpenZeppelin Stellar Contracts para crear un token fungible. La biblioteca proporciona implementaciones desarrolladas y auditadas que siguen las prácticas recomendadas.
-
-:::
-
-```rust title="examples/fungible-token-interface/src/contract.rs"
-use soroban_sdk::{contract, contractimpl, token::Interface as TokenInterface, Address, Env};
-use stellar_access::ownable::{self as ownable, Ownable};
-use stellar_macros::{default_impl, only_owner, when_not_paused};
-use stellar_pausable::pausable::{self as pausable, Pausable};
-use stellar_tokens::fungible::{Base, FungibleToken};
-
-#[contract]
-pub struct FungibleTokenContract;
-
-#[contractimpl]
-impl FungibleTokenContract {
-    pub fn __constructor(e: &Env, owner: Address) {
-        // Set token metadata
-        Base::set_metadata(
-            e,
-            18, // 18 decimals
-            "My Token".into(),
-            "TKN".into(),
-        );
-
-        // Set the contract owner
-        ownable::set_owner(e, &owner);
-    }
-
-    #[only_owner]
-    pub fn mint(e: &Env, to: Address, amount: i128) {
-        Base::mint(e, &to, amount);
-    }
-
-    #[only_owner]
-    pub fn pause(e: &Env) {
-        pausable::pause(e);
-    }
-
-    #[only_owner]
-    pub fn unpause(e: &Env) {
-        pausable::unpause(e);
-    }
-}
-
-#[default_impl]
-#[contractimpl]
-impl FungibleToken for FungibleTokenContract {
-    type ContractType = Base;
-}
-
-#[default_impl]
-#[contractimpl]
-impl TokenInterface for FungibleTokenContract {
-    #[when_not_paused]
-    fn transfer(e: Env, from: Address, to: Address, amount: i128) {
-        Base::transfer(&e, &from, &to, amount);
-    }
-
-    #[when_not_paused]
-    fn transfer_from(e: Env, spender: Address, from: Address, to: Address, amount: i128) {
-        Base::transfer_from(&e, &spender, &from, &to, amount);
-    }
-
-    #[when_not_paused]
-    fn burn(e: Env, from: Address, amount: i128) {
-        Base::burn(&e, &from, amount);
-    }
-
-    #[when_not_paused]
-    fn burn_from(e: Env, spender: Address, from: Address, amount: i128) {
-        Base::burn_from(&e, &spender, &from, amount);
-    }
-
-    #[when_not_paused]
-    fn approve(e: Env, from: Address, spender: Address, amount: i128, expiration_ledger: u32) {
-        Base::approve(&e, &from, &spender, amount, expiration_ledger);
-    }
-
-    fn allowance(e: Env, from: Address, spender: Address) -> i128 {
-        Base::allowance(&e, &from, &spender)
-    }
-
-    fn balance(e: Env, id: Address) -> i128 {
-        Base::balance(&e, &id)
-    }
-
-    fn decimals(e: Env) -> u32 {
-        Base::decimals(&e)
-    }
-
-    fn name(e: Env) -> soroban_sdk::String {
-        Base::name(&e)
-    }
-
-    fn symbol(e: Env) -> soroban_sdk::String {
-        Base::symbol(&e)
-    }
-}
-
-#[default_impl]
-#[contractimpl]
-impl Ownable for FungibleTokenContract {}
-
-#[default_impl]
-#[contractimpl]
-impl Pausable for FungibleTokenContract {}
-```
-
-Referencia: https://github.com/OpenZeppelin/stellar-contracts/tree/main/examples/fungible-token-interface
-
-## Cómo Funciona
-
-Este ejemplo muestra cómo crear un token fungible usando la biblioteca OpenZeppelin Stellar Contracts. La biblioteca ofrece implementaciones desarrolladas y auditadas que siguen las mejores prácticas e estándares de seguridad de la industria.
-
-El contrato implementa varias características clave:
-
-1. **Cumplimiento con la Interfaz de Token**: Implementa completamente la Interfaz estándar de Token para máxima interoperabilidad
-2. **Control de Propiedad**: Usa el patrón Ownable para funciones administrativas
-3. **Funcionalidad de Pausa**: Permite al propietario pausar/despausar operaciones del token en situaciones de emergencia
-4. **Emisión Segura**: Solo el propietario del contrato puede emitir nuevos tokens
-
-Al aprovechar la biblioteca OpenZeppelin, los desarrolladores pueden centrarse en su lógica de negocio específica mientras confían en implementaciones probadas para la funcionalidad central del token.
-
-### Uso de Componentes de la Biblioteca OpenZeppelin
-
-La biblioteca OpenZeppelin Stellar Contracts proporciona componentes modulares que pueden componerse fácilmente juntos:
-
-- **`Base`**: Funcionalidad central del token fungible con operaciones estándar de token
-- **`Ownable`**: Patrón de control de acceso para funciones administrativas
-- **`Pausable`**: Mecanismo de paro de emergencia para operaciones del token
-- **Macros**: `#[only_owner]` y `#[when_not_paused]` para control de acceso declarativo
-
-La macro `#[default_impl]` genera automáticamente las implementaciones estándar, reduciendo el código repetitivo y manteniendo la compatibilidad completa con la Interfaz de Token.
-
-### Características Mejoradas de Seguridad
-
-Este ejemplo muestra varias funciones de seguridad incorporadas en la biblioteca OpenZeppelin:
-
-**Control de Acceso**: La macro `#[only_owner]` asegura que sólo el propietario designado pueda realizar acciones administrativas como emitir tokens o pausar el contrato.
-
-**Operaciones con Pausa**: La macro `#[when_not_paused]` permite que el contrato sea pausado en situaciones de emergencia, impidiendo transferencias, quemas y aprobaciones pero permitiendo consultas de saldo.
-
-**Valores Predeterminados Seguros**: La biblioteca implementa valores predeterminados seguros para todas las operaciones de tokens, incluyendo verificaciones de autorización adecuadas y emisiones de eventos.
-
-:::tip
-
-La biblioteca OpenZeppelin Stellar Contracts ha sido auditada y sigue las prácticas recomendadas de la industria. Usar estos componentes preconstruidos reduce el riesgo de vulnerabilidades de seguridad en tus contratos de tokens.
-
-:::
-
-## Uso
-
-Crearemos un token sencillo para la moneda dentro de un juego. Los jugadores pueden ganar tokens completando tareas, y pueden gastar tokens en objetos dentro del juego. El propietario del contrato puede emitir nuevos tokens según sea necesario, y los jugadores pueden transferir tokens entre cuentas.
-
-Así es como podría verse un contrato básico de token fungible:
-
-```rust
-use soroban_sdk::{contract, contractimpl, Address, Env, String};
-use stellar_tokens::fungible::{burnable::FungibleBurnable, Base, ContractOverrides, FungibleToken};
-use stellar_access::ownable::{self as ownable, Ownable};
-use stellar_macros::{default_impl, only_owner};
-
-#[contract]
-pub struct GameCurrency;
-
-#[contractimpl]
-impl GameCurrency {
-    pub fn __constructor(e: &Env, initial_owner: Address) {
-        // Set token metadata
-        Base::set_metadata(
-            e,
-            8, // 8 decimals
-            String::from_str(e, "Game Currency"),
-            String::from_str(e, "GCUR"),
-        );
-
-        // Set the contract owner
-        ownable::set_owner(e, &initial_owner);
-    }
-
-    #[only_owner]
-    pub fn mint_tokens(e: &Env, to: Address, amount: i128) {
-        // Mint tokens to the recipient
-        Base::mint(e, &to, amount);
-    }
-}
-
-#[default_impl]
-#[contractimpl]
-impl FungibleToken for GameCurrency {
-    type ContractType = Base;
-}
-
-#[default_impl]
-#[contractimpl]
-impl FungibleBurnable for GameCurrency {}
-```
-
-## Pruebas
-
-El ejemplo de OpenZeppelin incluye pruebas integrales que verifican tanto la funcionalidad estándar del token como las características adicionales de seguridad.
-
-Escenarios clave de prueba incluyen:
-
-- **Operaciones de Token**: Pruebas de emisión, transferencia, quema y funciones de aprobación
-- **Control de Acceso**: Verificar que sólo el propietario pueda realizar acciones administrativas
-- **Funcionalidad de Pausa**: Asegurar que las operaciones de token estén correctamente restringidas cuando se encuentren pausadas
-- **Autorización**: Confirmar requisitos de autenticación adecuados para cada función
-- **Casos límite**: Pruebas de condiciones límite y escenarios de error
-
-Para ejecutar las pruebas:
-
-```sh
-cd examples/fungible-token-interface
-cargo test
-```
-
-Las pruebas demuestran cómo la biblioteca OpenZeppelin maneja escenarios complejos manteniendo seguridad y control de acceso adecuados.
-
-## Crear el Contrato
-
-Para crear el contrato, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-Un archivo `.wasm` debería generarse en el directorio `target`:
-
-```sh
-target/wasm32v1-none/release/fungible_token_interface.wasm
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/fuzzing.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/fuzzing.mdx
deleted file mode 100644
index b50a141d41..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/fuzzing.mdx
+++ /dev/null
@@ -1,783 +0,0 @@
----
-title: Pruebas de Fuzz
-description: Aumentar la confianza en la corrección de un contrato con pruebas de fuzz.
-sidebar_position: 160
----
-
-<head>
-  <title>
-    {`Aumentar la confianza en la corrección de un contrato con pruebas de fuzz.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Aumentar la confianza en la corrección de un contrato con pruebas de fuzz."
-  />
-  <meta
-    property="og:description"
-    content="Prueba de fuzz para contratos inteligentes con cargo-fuzz y personaliza la entrada para las pruebas de fuzz con crate arbitrario; demuestra cómo adaptar las pruebas de fuzz a pruebas de propiedad reutilizables."
-  />
-</head>
-
-El [ejemplo de fuzzing] demuestra cómo probar contratos Soroban con [`cargo-fuzz`] y personalizar la entrada para las pruebas de fuzz con crate [`arbitrary`]. También demuestra cómo adaptar las pruebas de fuzz en pruebas de propiedad reutilizables con los crates [`proptest`] y [`proptest-arbitrary-interop`]. Se basa en el [ejemplo de timelock].
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de fuzzing]: https://github.com/stellar/soroban-examples/tree/v23.0.0/fuzzing
-[`cargo-fuzz`]: https://docs.rs/cargo-fuzz
-[`arbitrary`]: https://docs.rs/arbitrary
-[`proptest`]: https://docs.rs/proptest
-[`proptest-arbitrary-interop`]: https://docs.rs/proptest-arbitrary-interop
-[ejemplo de timelock]: https://github.com/stellar/soroban-examples/tree/v23.0.0/timelock
-
-## Ejecutar el Ejemplo
-
-Primero sigue el proceso de [configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../../smart-contracts/getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-También necesitarás la herramienta `cargo-fuzz`, y para ejecutar `cargo-fuzz` necesitarás un toolchain Rust nightly:
-
-```sh
-cargo install cargo-fuzz
-rustup install nightly
-```
-
-Para ejecutar una de las pruebas de fuzz, navega al directorio `fuzzing` y ejecuta el subcomando `cargo fuzz` con el toolchain `nightly`:
-
-```sh
-cd fuzzing
-cargo +nightly fuzz run fuzz_target_1
-```
-
-:::info
-
-Si estás desarrollando en MacOS, puede que necesites añadir el flag `--sanitizer=thread` para corregir algunos [errores de enlace conocidos](https://github.com/stellar/rs-soroban-sdk/issues/1056).
-
-:::
-
-Deberías ver una salida que comienza así:
-
-```sh
-$ cargo +nightly fuzz run fuzz_target_1
-   Compiling soroban-fuzzing-contract v0.0.0 (/home/azureuser/data/stellar/soroban-examples/fuzzing)
-   Compiling soroban-fuzzing-contract-fuzzer v0.0.0 (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz)
-    Finished release [optimized + debuginfo] target(s) in 23.74s
-    Finished release [optimized + debuginfo] target(s) in 0.07s
-     Running `fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1 ...`
-INFO: Running with entropic power schedule (0xFF, 100).
-INFO: Seed: 886588732
-INFO: Loaded 1 modules   (1093478 inline 8-bit counters): 1093478 [0x55eb8e2c7620, 0x55eb8e3d2586),
-INFO: Loaded 1 PC tables (1093478 PCs): 1093478 [0x55eb8e3d2588,0x55eb8f481be8),
-INFO:      105 files found in /home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/corpus/fuzz_target_1
-INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
-INFO: seed corpus: files: 105 min: 32b max: 61b total: 3558b rss: 86Mb
-#2      pulse  ft: 8355 exec/s: 1 rss: 307Mb
-#4      pulse  cov: 8354 ft: 11014 corp: 1/32b exec/s: 2 rss: 313Mb
-#8      pulse  cov: 8495 ft: 12420 corp: 4/128b exec/s: 4 rss: 315Mb
-```
-
-El resto de este tutorial explicará cómo configurar esta prueba de fuzz, interpretar esta salida y resolver fallos de fuzzing.
-
-## Contexto: Pruebas de Fuzz y Rust
-
-El fuzzing es un tipo de prueba donde se alimentan repetidamente nuevos inputs en un programa con la esperanza de encontrar errores inesperados. Este estilo de prueba se emplea comúnmente para aumentar la confianza en la corrección del software sensible a la seguridad.
-
-En Rust, el fuzzing se realiza más a menudo con la herramienta [`cargo-fuzz`], que utiliza [`libfuzzer`] de LLVM, aunque hay otras herramientas de fuzzing disponibles.
-
-[`libfuzzer`]: https://llvm.org/docs/LibFuzzer.html
-
-Soroban tiene soporte integrado para pruebas de fuzz en contratos Soroban con `cargo-fuzz`.
-
-`cargo-fuzz` es un fuzzer basado en mutaciones: ejecuta un programa de prueba, pasándole input generado; mientras el programa se ejecuta, el fuzzer monitorea qué ramas toma el programa y qué funciones ejecuta; tras la ejecución, el fuzzer utiliza esta información para tomar decisiones sobre cómo _mutar_ el input previamente usado para crear nuevo input que podría descubrir más ramas y funciones; luego ejecuta la prueba nuevamente con el nuevo input, repitiendo este proceso durante potencialmente millones de iteraciones. De esta manera, `cargo-fuzz` puede explorar automáticamente los caminos de ejecución a través del programa que pueden nunca ser vistos por otros tipos de pruebas.
-
-Si una prueba de fuzz genera un panic o se cierra de forma abrupta, `cargo-fuzz` lo considera una falla y proporciona instrucciones para repetir la prueba con los inputs fallidos.
-
-Las pruebas de fuzz generalmente son un proceso exploratorio e interactivo, donde el programador desarrolla esquemas para producir inputs que estresen el programa de maneras interesantes, observan el comportamiento de la prueba de fuzz y hacen iteraciones sobre la propia prueba.
-
-Resolver una falla en las pruebas de fuzz generalmente implica capturar el input problemático en una prueba unitaria. La prueba de fuzz puede o no ser mantenida, dependiendo de las determinaciones sobre el costo de mantener el fuzzer frente a la probabilidad de que continúe encontrando errores en el futuro.
-
-Mientras que el fuzzing de software no seguro en memoria tiende a ser más lucrativo que el fuzzing de software en Rust, sigue siendo relativamente común encontrar panics y otros errores lógicos en Rust a través del fuzzing.
-
-En Rust, múltiples fuzzers son mantenidos por la organización de GitHub [`rust-fuzz`], que también mantiene una "vitrina de trofeos" de errores de Rust encontrados a través del fuzzing.
-
-[`rust-fuzz`]: https://github.com/rust-fuzz
-
-## Acerca del Ejemplo
-
-El ejemplo utilizado para este tutorial está basado en el programa de ejemplo [`timelock`], con algunos cambios para demostrar el fuzzing.
-
-[`timelock`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/timelock
-
-El contrato, `ClaimableBalanceContract`, permite que una parte deposite una cantidad arbitraria de un token en el contrato, especificando además: los `claimants`, direcciones que pueden retirar del contrato; y el `time_bound`, una especificación de cuándo esos reclamantes pueden retirar de la cuenta.
-
-El tipo `TimeBound` luce así
-
-```rust
-#[derive(Clone, Debug)]
-#[contracttype]
-pub enum TimeBoundKind {
-    Before,
-    After,
-}
-
-#[derive(Clone, Debug)]
-#[contracttype]
-pub struct TimeBound {
-    pub kind: TimeBoundKind,
-    pub timestamp: u64,
-}
-```
-
-`ClaimableBalanceContract` tiene dos métodos, `deposit` y `claim`:
-
-```rust
-    pub fn deposit(
-        env: Env,
-        from: Address,
-        token: Address,
-        amount: i128,
-        claimants: Vec<Address>,
-        time_bound: TimeBound,
-    );
-
-    pub fn claim(
-        env: Env,
-        claimant: Address,
-        amount: i128,
-    );
-```
-
-`deposit` se puede llamar exitosamente solo una vez, después de lo cual se puede llamar a `claim` múltiples veces hasta que el balance esté completamente agotado, momento en el cual el contrato se vuelve inactivo y ya no puede ser utilizado.
-
-## Configuración de Pruebas de Fuzz
-
-Para estos ejemplos, las pruebas de fuzz han sido creadas para ti, pero normalmente usarías el comando `cargo fuzz init` para crear un proyecto de fuzzing como un subdirectorio del contrato bajo prueba. Para hacer esto, navega al directorio del contrato, en este caso, `soroban-examples/fuzzing`, y ejecuta
-
-```sh
-cargo fuzz init
-```
-
-Un proyecto `cargo-fuzz` es su propia crate, que vive en el subdirectorio `fuzz` de la crate que se está probando. Esta crate tiene su propio `Cargo.toml` y `Cargo.lock`, y otro subdirectorio, `fuzz_targets`, que contiene programas Rust, cada uno con su propia prueba de fuzzing.
-
-Nuestro directorio `soroban-examples/fuzzing` se ve así
-
-- `Cargo.toml` - este es el manifiesto del contrato
-- `Cargo.lock`
-- `src`
-  - `lib.rs` - este es el código del contrato
-- `fuzz` - esta es la crate de fuzzing
-  - `Cargo.toml` - este es el manifiesto de la crate de fuzzing
-  - `Cargo.lock`
-  - `fuzz_targets`
-    - `fuzz_target_1.rs` - esta es una prueba de fuzzing individual
-    - `fuzz_target_2.rs`
-
-Hay consideraciones especiales a tener en cuenta en la configuración tanto del [manifiesto del contrato] como del [manifiesto de la crate de fuzzing].
-
-[manifiesto del contrato]: https://github.com/stellar/soroban-examples/tree/v23.0.0/fuzzing/Cargo.toml
-[manifiesto de la crate de fuzzing]: https://github.com/stellar/soroban-examples/tree/v23.0.0/fuzzing/fuzz/Cargo.toml
-
-Dentro del manifiesto del contrato hay que especificar el tipo de crate como "cdylib" y "rlib":
-
-```toml title="fuzzing/Cargo.toml"
-[package]
-name = "soroban-fuzzing-contract"
-version = "0.0.0"
-edition = "2021"
-publish = false
-rust-version = "1.89.0"
-
-[lib]
-crate-type = ["cdylib", "rlib"]
-doctest = false
-
-[features]
-testutils = []
-```
-
-En la mayoría de ejemplos, un contrato Soroban será solo un "cdylib", una crate Rust compilada como un módulo Wasm cargable dinámicamente. Sin embargo, para el fuzzing, la crate de fuzzing debe poder enlazarse con la crate del contrato como una librería Rust, una "rlib".
-
-:::note
-
-Ten en cuenta que cargo tiene una [característica/error que inhibe LTO][lto] de cdylibs cuando una crate es tanto "cdylib" como "rlib". Esto se puede solucionar compilando el contrato con `soroban contract build` o `cargo rustc --crate-type cdylib` en lugar del típico `cargo build`.
-
-:::
-
-[lto]: https://github.com/stellar/soroban-docs/pull/476
-
-La crate del contrato también debe habilitar la característica "testutils". Cuando "testutils" está activado, el macro [`contracttype`] del SDK Soroban emite código adicional necesario para ejecutar pruebas de fuzzing.
-
-[`contracttype`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/attr.contracttype.html
-
-Dentro del manifiesto de la crate de fuzzing se deben activar las características "testutils" tanto en la crate del contrato como en la crate `soroban-sdk`:
-
-```toml title="fuzzing/fuzz/Cargo.toml"
-[package]
-name = "soroban-fuzzing-contract-fuzzer"
-version = "0.0.0"
-publish = false
-edition = "2021"
-rust-version = "1.79.0"
-
-[package.metadata]
-cargo-fuzz = true
-
-[dependencies]
-libfuzzer-sys = "0.4"
-soroban-sdk = { version = "23.0.1", features = ["testutils"] }
-soroban-env-host = { version = "23.0.1" }
-soroban-ledger-snapshot = { version = "23.0.1" }
-
-[dependencies.soroban-fuzzing-contract]
-path = ".."
-features = ["testutils"]
-```
-
-## Una prueba de fuzzing simple
-
-Primero veamos [`fuzz_target_1.rs`]. Esta prueba de fuzzing hace dos cosas: primero deposita una cantidad arbitraria y luego reclama una cantidad arbitraria.
-
-[`fuzz_target_1.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/fuzzing/fuzz/fuzz_targets/fuzz_target_1.rs
-
-Puedes ejecutar este fuzzer desde el directorio `soroban-examples/fuzzing` con el siguiente comando:
-
-```sh
-cargo +nightly fuzz run fuzz_target_1
-```
-
-El punto de entrada y el código de configuración para pruebas de fuzzing de contratos Soroban típicamente se ven así:
-
-```rust title="fuzzing/fuzz/fuzz_targets/fuzz_target_1.rs"
-#[derive(Arbitrary, Debug)]
-struct Input {
-    deposit_amount: i128,
-    claim_amount: i128,
-}
-
-fuzz_target!(|input: Input| {
-    let env = Env::default();
-
-    env.mock_all_auths();
-
-    env.ledger().set(LedgerInfo {
-        timestamp: 12345,
-        protocol_version: 1,
-        sequence_number: 10,
-        network_id: Default::default(),
-        base_reserve: 10,
-        min_temp_entry_ttl: u32::MAX,
-        min_persistent_entry_ttl: u32::MAX,
-        max_entry_ttl: u32::MAX,
-    });
-
-    // Turn off the CPU/memory budget for testing.
-    env.cost_estimate().budget().reset_unlimited();
-
-    // ... do fuzzing here ...
-}
-```
-
-En lugar de una función `main`, `cargo-fuzz` usa un punto de entrada especial definido por el macro [`fuzz_target!`] Este macro acepta un closure Rust que recibe `input`, cualquier tipo Rust que implemente el trait [`Arbitrary`]. Aquí hemos definido una estructura, `Input`, que deriva de `Arbitrary`.
-
-[`fuzz_target!`]: https://docs.rs/libfuzzer-sys/latest/libfuzzer_sys/macro.fuzz_target.html
-[`arbitrary`]: https://docs.rs/arbitrary/latest/arbitrary/trait.Arbitrary.html
-
-`cargo-fuzz` será responsable de generar `input` y llamar repetidamente a este closure.
-
-Para probar un contrato Soroban, debemos configurar un [`Env`]. Ten en cuenta que hemos deshabilitado el presupuesto de CPU y memoria: esto nos permitirá fuzzear rutas de código arbitrariamente complejas sin preocuparnos por quedarnos sin presupuesto; podemos asumir que quedarse sin presupuesto durante una transacción siempre falla correctamente, cancelando la transacción; no es algo que necesitemos fuzzear.
-
-[`env`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Env.html
-
-Consulta el código fuente de [`fuzz_target_1.rs`] para configuración adicional de este contrato.
-
-Este fuzzer realiza dos pasos: depositar y luego reclamar:
-
-```rust title="fuzzing/fuzz/fuzz_targets/fuzz_target_1.rs"
-    // Deposit, then assert invariants.
-    {
-        let _ = timelock_client.try_deposit(
-            &depositor_address,
-            &token_contract_id,
-            &input.deposit_amount,
-            &vec![&env, claimant_address.clone()],
-            &TimeBound {
-                kind: TimeBoundKind::Before,
-                timestamp: 123456,
-            },
-        );
-
-        assert_invariants(&env, &timelock_contract_id, &token_client, &input);
-    }
-
-    // Claim, then assert invariants.
-    {
-        let _ = timelock_client.try_claim(&claimant_address, &input.claim_amount);
-
-        assert_invariants(&env, &timelock_contract_id, &token_client, &input);
-    }
-```
-
-Hay varias estrategias potenciales para escribir pruebas de fuzzing. La estrategia en esta prueba es hacer llamadas arbitrarias, posiblemente extrañas e irreales, al contrato, sin importar si esas llamadas tienen éxito o fallan, y luego hacer afirmaciones sobre el estado del contrato.
-
-Como hay muchos casos potenciales de fallo para cualquier llamada al contrato, no queremos escribir una prueba de fuzzing intentando interpretar el éxito o fracaso de una llamada dada: ese camino conduce a duplicar la lógica del contrato dentro de la prueba de fuzzing. En lugar de eso, solo queremos asegurar que, sin importar lo que pasó durante la ejecución, el contrato nunca quede en un estado inválido.
-
-Nota el uso de la función cliente `try_` para invocar el contrato. Cada función del contrato puede invocarse con una variante `try_`, que captura cualquier error, incluyendo panics y caídas, y devuelve el valor en caso de éxito o un error en caso contrario. Sin usar la variante `try_`, un panic dentro de un contrato causará que la prueba de fuzzing falle inmediatamente, pero en la mayoría de los casos un panic dentro de un contrato no indica un bug, es simplemente cómo un contrato Soroban cancela una transacción. `try_` devuelve un `Result`, pero aquí lo descartamos.
-
-Finalmente, la función `assert_invariants` es donde hacemos las afirmaciones que podamos sobre el estado del contrato:
-
-```rust title="fuzzing/fuzz/fuzz_targets/fuzz_target_1.rs"
-/// Directly inspect the contract state and make assertions about it.
-fn assert_invariants(
-    env: &Env,
-    timelock_contract_id: &Address,
-    token_client: &TokenClient,
-    input: &Input,
-) {
-    // Configure the environment to access the timelock contract's storage.
-    env.as_contract(timelock_contract_id, || {
-        let storage = env.storage().persistent();
-
-        // Get the two datums owned by the timelock contract.
-        let is_initialized = storage.has(&DataKey::Init);
-        let claimable_balance = storage.get::<_, ClaimableBalance>(&DataKey::Balance);
-
-        // Call the token client to get the balance held in the timelock contract.
-        // This consumes contract execution budget.
-        let actual_token_balance = token_client.balance(timelock_contract_id);
-
-        // There can only be a claimaible balance after the contract is initialized,
-        // but once the balance is claimed there is no balance,
-        // but the contract remains initialized.
-        // This is a truth table of valid states.
-        assert!(match (is_initialized, claimable_balance.is_some()) {
-            (false, false) => true,
-            (false, true) => false,
-            (true, true) => true,
-            (true, false) => true,
-        });
-
-        assert!(actual_token_balance >= 0);
-
-        if let Some(claimable_balance) = claimable_balance {
-            assert!(claimable_balance.amount > 0);
-            assert!(claimable_balance.amount <= input.deposit_amount);
-            assert_eq!(claimable_balance.amount, actual_token_balance);
-
-            assert!(claimable_balance.claimants.len() > 0);
-        }
-    });
-}
-```
-
-## Interpretar la salida de `cargo-fuzz`
-
-Si ejecutas `cargo-fuzz` con `fuzz_target_1`, dentro del directorio `soroban-examples/fuzzing`, verás una salida similar a:
-
-```text
-$ cargo +nightly fuzz run fuzz_target_1
-   Compiling soroban-fuzzing-contract v0.0.0 (/home/azureuser/data/stellar/soroban-examples/fuzzing)
-   Compiling soroban-fuzzing-contract-fuzzer v0.0.0 (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz)
-    Finished release [optimized + debuginfo] target(s) in 25.18s
-    Finished release [optimized + debuginfo] target(s) in 0.08s
-     Running `fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1 -artifact_prefix=/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/artifacts/fuzz_target_1/ /home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/corpus/fuzz_target_1`
-INFO: Running with entropic power schedule (0xFF, 100).
-INFO: Seed: 1384064486
-INFO: Loaded 1 modules   (1122058 inline 8-bit counters): 1122058 [0x561f6ecd4fc0, 0x561f6ede6eca),
-INFO: Loaded 1 PC tables (1122058 PCs): 1122058 [0x561f6ede6ed0,0x561f6ff05f70),
-INFO:      173 files found in /home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/corpus/fuzz_target_1
-INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
-INFO: seed corpus: files: 173 min: 32b max: 61b total: 6039b rss: 83Mb
-#4      pulse  cov: 4848 ft: 10214 corp: 1/32b exec/s: 2 rss: 313Mb
-#8      pulse  cov: 8507 ft: 11743 corp: 4/128b exec/s: 4 rss: 315Mb
-#16     pulse  cov: 8512 ft: 12393 corp: 10/320b exec/s: 8 rss: 319Mb
-thread '<unnamed>' panicked at 'assertion failed: claimable_balance.amount > 0', fuzz_targets/fuzz_target_1.rs:130:13
-note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
-==6102== ERROR: libFuzzer: deadly signal
-    #0 0x561f6ae3a431  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x1c80431) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-    #1 0x561f6e3855b0  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x51cb5b0) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-    #2 0x561f6e35c08a  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x51a208a) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-    #3 0x7fce05f5e08f  (/lib/x86_64-linux-gnu/libc.so.6+0x4308f) (BuildId: 1878e6b475720c7c51969e69ab2d276fae6d1dee)
-    #4 0x7fce05f5e00a  (/lib/x86_64-linux-gnu/libc.so.6+0x4300a) (BuildId: 1878e6b475720c7c51969e69ab2d276fae6d1dee)
-    #5 0x7fce05f3d858  (/lib/x86_64-linux-gnu/libc.so.6+0x22858) (BuildId: 1878e6b475720c7c51969e69ab2d276fae6d1dee)
-    ...
-    #27 0x561f6e3847b9  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x51ca7b9) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-    #28 0x561f6ad98346  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x1bde346) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-    #29 0x7fce05f3f082  (/lib/x86_64-linux-gnu/libc.so.6+0x24082) (BuildId: 1878e6b475720c7c51969e69ab2d276fae6d1dee)
-    #30 0x561f6ad9837d  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x1bde37d) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-
-NOTE: libFuzzer has rudimentary signal handlers.
-      Combine libFuzzer with AddressSanitizer or similar for better crash reports.
-SUMMARY: libFuzzer: deadly signal
-MS: 0 ; base unit: 0000000000000000000000000000000000000000
-0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x5d,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0xff,0x5f,0x5f,0x52,0xff,
-\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000]\000\000\000\000\000\000\000\000\377__R\377
-artifact_prefix='/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/artifacts/fuzz_target_1/'; Test unit written to /home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/artifacts/fuzz_target_1/crash-04704b1542f61a21a4649e39023ec57ff502f627
-Base64: AAAAAAAAAAAAAAAAAAAAAAAAXQAAAAAAAAAA/19fUv8=
-
-────────────────────────────────────────────────────────────────────────────────
-
-Failing input:
-
-        fuzz/artifacts/fuzz_target_1/crash-04704b1542f61a21a4649e39023ec57ff502f627
-
-Output of `std::fmt::Debug`:
-
-        Input {
-            deposit_amount: 0,
-            claim_amount: -901525218878596739118967460911579136,
-        }
-
-Reproduce with:
-
-        cargo fuzz run fuzz_target_1 fuzz/artifacts/fuzz_target_1/crash-04704b1542f61a21a4649e39023ec57ff502f627
-
-Minimize test case with:
-
-        cargo fuzz tmin fuzz_target_1 fuzz/artifacts/fuzz_target_1/crash-04704b1542f61a21a4649e39023ec57ff502f627
-
-────────────────────────────────────────────────────────────────────────────────
-
-Error: Fuzz target exited with exit status: 77
-```
-
-Esto es una falla de fuzzing, indicando un bug en el propio fuzzer o en el programa. Los detalles serán diferentes.
-
-Aquí está la misma salida, con las líneas menos importantes recortadas:
-
-```text
-thread '<unnamed>' panicked at 'assertion failed: claimable_balance.amount > 0', fuzz_targets/fuzz_target_1.rs:130:13
-...
-Failing input:
-
-        fuzz/artifacts/fuzz_target_1/crash-04704b1542f61a21a4649e39023ec57ff502f627
-
-Output of `std::fmt::Debug`:
-
-        Input {
-            deposit_amount: 0,
-            claim_amount: -901525218878596739118967460911579136,
-        }
-
-Reproduce with:
-
-        cargo fuzz run fuzz_target_1 fuzz/artifacts/fuzz_target_1/crash-04704b1542f61a21a4649e39023ec57ff502f627
-
-Minimize test case with:
-
-        cargo fuzz tmin fuzz_target_1 fuzz/artifacts/fuzz_target_1/crash-04704b1542f61a21a4649e39023ec57ff502f627
-```
-
-La primera línea aquí es impresa por nuestro programa Rust, e indica exactamente dónde el fuzzer hizo panic. Las líneas posteriores indican cómo reproducir este caso fallido.
-
-Lo primero que debes hacer cuando obtienes una falla de fuzzing es copiar el comando para reproducir la falla, para que puedas usarlo para depurar:
-
-```sh
-cargo +nightly fuzz run fuzz_target_1 fuzz/artifacts/fuzz_target_1/crash-04704b1542f61a21a4649e39023ec57ff502f627
-```
-
-Observa que necesitamos decirle a `cargo` que use el toolchain nightly con el flag `+nightly`, algo que `cargo-fuzz` no imprime en su versión del comando.
-
-Otra cosa a notar es que por defecto, `cargo-fuzz` / `libfuzzer` no imprime los nombres de funciones en su salida, como en el stack trace:
-
-```text
-==6102== ERROR: libFuzzer: deadly signal
-    #0 0x561f6ae3a431  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x1c80431) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-    ...
-    #28 0x561f6ad98346  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x1bde346) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-    #29 0x7fce05f3f082  (/lib/x86_64-linux-gnu/libc.so.6+0x24082) (BuildId: 1878e6b475720c7c51969e69ab2d276fae6d1dee)
-    #30 0x561f6ad9837d  (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x1bde37d) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-```
-
-Dependiendo de cómo esté configurado tu sistema, puede que tengas o no este problema. Para imprimir los stack traces, `libfuzzer` necesita el programa `llvm-symbolizer`. En sistemas basados en Ubuntu esto se puede instalar con el paquete `llvm-dev`:
-
-```sh
-sudo apt install llvm-dev
-```
-
-Después de esto, `libfuzzer` imprimirá nombres de funciones desmanglados en lugar de direcciones:
-
-```text
-==6323== ERROR: libFuzzer: deadly signal
-    #0 0x557c9da6a431 in __sanitizer_print_stack_trace /rustc/llvm/src/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:87:3
-    #1 0x557ca0fb55b0 in fuzzer::PrintStackTrace() /home/azureuser/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libfuzzer-sys-0.4.5/libfuzzer/FuzzerUtil.cpp:210:38
-    #2 0x557ca0f8c08a in fuzzer::Fuzzer::CrashCallback() /home/azureuser/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libfuzzer-sys-0.4.5/libfuzzer/FuzzerLoop.cpp:233:18
-    #3 0x557ca0f8c08a in fuzzer::Fuzzer::CrashCallback() /home/azureuser/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libfuzzer-sys-0.4.5/libfuzzer/FuzzerLoop.cpp:228:6
-    #4 0x7ff19e84d08f  (/lib/x86_64-linux-gnu/libc.so.6+0x4308f) (BuildId: 1878e6b475720c7c51969e69ab2d276fae6d1dee)
-    #5 0x7ff19e84d00a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3
-    #6 0x7ff19e84d00a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3
-    #7 0x7ff19e82c858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7
-    ...
-    #23 0x557c9daee89a in fuzz_target_1::assert_invariants::hd6d4f9549b01c31c /home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/fuzz_targets/fuzz_target_1.rs:103:5
-    #24 0x557c9daee89a in fuzz_target_1::_::run::hac1117cb3dfecb2b /home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/fuzz_targets/fuzz_target_1.rs:69:9
-    #25 0x557c9daecea6 in rust_fuzzer_test_input /home/azureuser/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libfuzzer-sys-0.4.5/src/lib.rs:297:60
-    ...
-    #37 0x557c9d9c8346 in main /home/azureuser/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libfuzzer-sys-0.4.5/libfuzzer/FuzzerMain.cpp:20:30
-    #38 0x7ff19e82e082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16
-    #39 0x557c9d9c837d in _start (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1+0x1bde37d) (BuildId: 6a95a932984a405ebab8171dddc9f812fdf16846)
-```
-
-Para continuar, nuestro programa tiene un bug que debería ser fácil de corregir inspeccionando el error y haciendo una ligera modificación en el código fuente.
-
-Una vez corregido el bug, el fuzzer se ejecutará continuamente, produciendo una salida que se ve así
-
-```sh
-$ cargo +nightly fuzz run fuzz_target_1
-   Compiling soroban-fuzzing-contract v0.0.0 (/home/azureuser/data/stellar/soroban-examples/fuzzing)
-   Compiling soroban-fuzzing-contract-fuzzer v0.0.0 (/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz)
-    Finished release [optimized + debuginfo] target(s) in 24.91s
-    Finished release [optimized + debuginfo] target(s) in 0.08s
-     Running `fuzz/target/x86_64-unknown-linux-gnu/release/fuzz_target_1 -artifact_prefix=/home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/artifacts/fuzz_target_1/ /home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/corpus/fuzz_target_1`
-INFO: Running with entropic power schedule (0xFF, 100).
-INFO: Seed: 1619748028
-INFO: Loaded 1 modules   (1122061 inline 8-bit counters): 1122061 [0x5647a55b9080, 0x5647a56caf8d),
-INFO: Loaded 1 PC tables (1122061 PCs): 1122061 [0x5647a56caf90,0x5647a67ea060),
-INFO:      173 files found in /home/azureuser/data/stellar/soroban-examples/fuzzing/fuzz/corpus/fuzz_target_1
-INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
-INFO: seed corpus: files: 173 min: 32b max: 61b total: 6039b rss: 85Mb
-#2      pulse  ft: 8067 exec/s: 1 rss: 312Mb
-#4      pulse  cov: 8068 ft: 10709 corp: 1/32b exec/s: 2 rss: 315Mb
-#8      pulse  cov: 8476 ft: 11498 corp: 5/160b exec/s: 4 rss: 317Mb
-#16     pulse  cov: 8512 ft: 12362 corp: 9/288b exec/s: 8 rss: 320Mb
-#32     pulse  cov: 8516 ft: 13290 corp: 19/608b exec/s: 10 rss: 326Mb
-#64     pulse  cov: 8516 ft: 13311 corp: 27/864b exec/s: 21 rss: 340Mb
-#128    pulse  cov: 8540 ft: 13536 corp: 37/1196b exec/s: 25 rss: 365Mb
-#175    INITED cov: 8540 ft: 13580 corp: 42/1387b exec/s: 29 rss: 382Mb
-#177    NEW    cov: 8545 ft: 13821 corp: 43/1419b lim: 48 exec/s: 29 rss: 384Mb L: 32/48 MS: 1 ChangeASCIIInt-
-#178    NEW    cov: 8545 ft: 13824 corp: 44/1451b lim: 48 exec/s: 29 rss: 384Mb L: 32/48 MS: 1 ChangeBinInt-
-#229    NEW    cov: 8545 ft: 13826 corp: 45/1483b lim: 48 exec/s: 38 rss: 401Mb L: 32/48 MS: 1 ChangeByte-
-#256    pulse  cov: 8545 ft: 13826 corp: 45/1483b lim: 48 exec/s: 36 rss: 410Mb
-#361    NEW    cov: 8545 ft: 13830 corp: 46/1521b lim: 48 exec/s: 40 rss: 451Mb L: 38/48 MS: 5 ShuffleBytes-CMP-EraseBytes-CopyPart-ChangeBinInt- DE: "\005\000\000\000"-
-        NEW_FUNC[1/1]: 0x5647a2964640 in rand::rngs::adapter::reseeding::ReseedingCore$LT$R$C$Rsdr$GT$::reseed_and_generate::ha760ded93293681c /home/azureuser/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rand-0.7.3/src/rngs/adapter/reseeding.rs:235
-#368    NEW    cov: 8557 ft: 13842 corp: 47/1566b lim: 48 exec/s: 40 rss: 454Mb L: 45/48 MS: 2 CrossOver-InsertRepeatedBytes-
-#512    pulse  cov: 8557 ft: 13842 corp: 47/1566b lim: 48 exec/s: 46 rss: 502Mb
-#850    NEW    cov: 8557 ft: 13843 corp: 48/1610b lim: 48 exec/s: 53 rss: 591Mb L: 44/48 MS: 2 CopyPart-ChangeBit-
-#1024   pulse  cov: 8557 ft: 13843 corp: 48/1610b lim: 48 exec/s: 56 rss: 645Mb
-#1796   NEW    cov: 8557 ft: 13863 corp: 49/1642b lim: 53 exec/s: 71 rss: 669Mb L: 32/48 MS: 1 ChangeBinInt-
-#1913   NEW    cov: 8557 ft: 13864 corp: 50/1675b lim: 53 exec/s: 73 rss: 669Mb L: 33/48 MS: 2 ShuffleBytes-InsertByte-
-#3749   REDUCE cov: 8557 ft: 13864 corp: 50/1670b lim: 68 exec/s: 98 rss: 669Mb L: 39/48 MS: 1 EraseBytes-
-...
-```
-
-Y esta salida continuará hasta que el fuzzer sea detenido con `Ctrl-C`.
-
-Ahora, veamos una línea única de la salida del fuzzer:
-
-```text
-#177    NEW    cov: 8545 ft: 13821 corp: 43/1419b lim: 48 exec/s: 29 rss: 384Mb L: 32/48 MS: 1 ChangeASCIIInt-
-```
-
-La columna más importante aquí es `cov`. Esta es una medida acumulativa de ramas cubiertas por el fuzzer. Cuando este número deja de aumentar, probablemente el fuzzer ha explorado tanto del programa como puede. Las otras columnas se describen en la documentación de [`libfuzzer`][lfout].
-
-[lfout]: https://llvm.org/docs/LibFuzzer.html#output
-
-Finalmente, veamos esta advertencia:
-
-```text
-INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes.
-```
-
-Por defecto, `libfuzzer` solo genera entradas de hasta 4096 bytes. En muchos casos, esto puede ser razonable, pero `cargo-fuzz` puede aumentar el `max_len` añadiendo el argumento después de `--`:
-
-```sh
-cargo +nightly fuzz run fuzz_target_1 -- -max_len=20000
-```
-
-Todas las opciones de libfuzzer pueden listarse con
-
-```sh
-cargo +nightly fuzz run fuzz_target_1 -- -help=1
-```
-
-Consulta la [documentación de `libfuzzer`] para más información.
-
-[documentación de `libfuzzer`]: https://llvm.org/docs/LibFuzzer.html#output
-
-## Aceptar tipos Soroban como entrada con el trait `SorobanArbitrary`
-
-Las entradas al macro `fuzz_target!` deben implementar el trait [`Arbitrary`], que acepta bytes del driver de fuzzing y los convierte en valores Rust. Sin embargo, los tipos Soroban son gestionados por el entorno host, y por lo tanto deben crearse a partir de un valor [`Env`], que no está disponible para el driver de fuzzing. El trait [`SorobanArbitrary`], implementado para todos los tipos de contrato Soroban, existe para salvar esta diferencia: define un patrón de _prototipo_ por el que el macro `fuzz_target` crea valores prototipo que el programa de fuzzing puede convertir en valores de contrato con los traits estándar de conversión de soroban, [`FromVal`] o [`IntoVal`].
-
-[`sorobanarbitrary`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/testutils/arbitrary/trait.SorobanArbitrary.html
-[`fromval`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/trait.FromVal.html
-[`intoval`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/trait.IntoVal.html
-
-Los tipos de prototipos están identificados por el tipo asociado `SorobanArbitrary::Prototype`:
-
-```rust
-pub trait SorobanArbitrary:
-    TryFromVal<Env, Self::Prototype> + IntoVal<Env, Val> + TryFromVal<Env, Val>
-{
-    type Prototype: for<'a> Arbitrary<'a>;
-}
-```
-
-Los tipos que implementan `SorobanArbitrary` incluyen:
-
-- `i32`, `u32`, `i64`, `u64`, `i128`, `u128`, [`I256`], [`U256`], `()`, y `bool`,
-- [`Error`],
-- [`Bytes`], [`BytesN`], [`Vec`], [`Map`],
-- [`Address`], [`Symbol`],
-- [`Val`],
-
-[`i256`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.I256.html
-[`u256`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.U256.html
-[`error`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/xdr/enum.Error.html
-[`bytes`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Bytes.html
-[`bytesn`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.BytesN.html
-[`vec`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Vec.html
-[`map`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Map.html
-[`address`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Address.html
-[`symbol`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Symbol.html
-[`val`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Val.html
-
-Todos los tipos de contrato definidos por el usuario, aquellos con el atributo [`contracttype`], derivan automáticamente `SorobanArbitrary`. Ten en cuenta que `SorobanArbitrary` solo se deriva cuando la característica Cargo "testutils" está activa. Esto implica que, en general, para hacer un contrato Soroban susceptible de fuzzing, la crate del contrato debe definir una feature Cargo "testutils", esa feature debe activar la feature "soroban-sdk/testutils", y la prueba de fuzzing, que es una crate propia, debe activar esa feature.
-
-## Una prueba de fuzzing más compleja
-
-El ejemplo [`fuzz_target_2.rs`] demuestra el uso de `SorobanArbitrary`, el avance del tiempo, y técnicas de fuzzing más avanzadas.
-
-[`fuzz_target_2.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/fuzzing/fuzz/fuzz_targets/fuzz_target_2.rs
-
-Esta prueba de fuzzing toma una entrada mucho más compleja, donde algunos de los valores son tipos definidos por el usuario exportados desde el contrato en prueba. La prueba está estructurada como un intérprete simple, donde el arnés de fuzzing provee "pasos" generados arbitrariamente, donde cada paso es un comando `deposit` o un comando `claim`. La prueba trata entonces cada uno de estos pasos como una transacción separada: mantiene una imagen del estado del blockchain, y para cada paso crea un ambiente nuevo para ejecutar la llamada al contrato, simulando el avance del tiempo entre pasos. Como en el ejemplo previo, se hacen afirmaciones después de cada paso.
-
-La entrada al fuzzer se ve, en parte, así:
-
-```rust title="fuzzing/fuzz/fuzz_targets/fuzz_target_2.rs"
-#[derive(Arbitrary, Debug)]
-struct Input {
-    addresses: [<Address as SorobanArbitrary>::Prototype; NUM_ADDRESSES],
-    #[arbitrary(with = |u: &mut Unstructured| u.int_in_range(0..=i128::MAX))]
-    token_mint: i128,
-    steps: RustVec<Step>,
-}
-
-#[derive(Arbitrary, Debug)]
-struct Step {
-    #[arbitrary(with = |u: &mut Unstructured| u.int_in_range(1..=u64::MAX))]
-    advance_time: u64,
-    command: Command, // `Command` not shown here - see the full source.
-}
-```
-
-Esto muestra cómo usar el tipo asociado `SorobanArbitrary::Prototype` para definir las entradas al fuzzer. Una [`Address`] Soroban solo puede crearse con un [`Env`], por lo que no puede generarse directamente con el trait `Arbitrary`. En lugar de eso usamos el nombre completamente calificado del prototipo de `Address`, `<Address as SorobanArbitrary>::Prototype`, para pedir el prototipo de `Address`. Cuando el fuzzer necesita la `Address` la instanciamos con el trait [`FromVal`]:
-
-```rust title="fuzzing/fuzz/fuzz_targets/fuzz_target_2.rs"
-let depositor_address = Address::from_val(&env, &input.addresses[cmd.depositor_index]);
-```
-
----
-
-El contrato que estamos fuzzing es un contrato _timelock_, donde el cálculo del tiempo es crucial para la corrección. Así que nuestra prueba debe tener en cuenta el avance del tiempo.
-
-El contrato define un tipo `TimeBound` y lo acepta en el método `deposit`:
-
-```rust title="fuzzing/src/lib.rs"
-#[derive(Clone, Debug)]
-#[contracttype]
-pub struct TimeBound {
-    pub kind: TimeBoundKind,
-    pub timestamp: u64,
-}
-
-#[contractimpl]
-impl ClaimableBalanceContract {
-    pub fn deposit(
-        env: Env,
-        from: Address,
-        token: Address,
-        amount: i128,
-        claimants: Vec<Address>,
-        time_bound: TimeBound,
-    ) {
-        ...
-    }
-}
-```
-
-En nuestro fuzzer, uno de los comandos posibles emitidos en cada paso es un `DepositCommand`:
-
-```rust title="fuzzing/fuzz/fuzz_targets/fuzz_target_2.rs"
-#[derive(Arbitrary, Debug)]
-struct DepositCommand {
-    #[arbitrary(with = |u: &mut Unstructured| u.int_in_range(0..=NUM_ADDRESSES - 1))]
-    depositor_index: usize,
-    amount: i128,
-    // This is an ugly way to get a vector of integers in range
-    #[arbitrary(with = |u: &mut Unstructured| {
-        u.arbitrary_len::<usize>().map(|len| {
-            (0..len).map(|_| {
-                u.int_in_range(0..=NUM_ADDRESSES - 1)
-            }).collect::<Result<RustVec<usize>, _>>()
-        }).and_then(|inner_result| inner_result)
-    })]
-    claimant_indexes: RustVec<usize>,
-    time_bound: <TimeBound as SorobanArbitrary>::Prototype,
-}
-```
-
-Nota que este comando nuevamente usa el tipo asociado `SorobanArbitrary::Prototype` para aceptar un `TimeBound` como entrada.
-
-Para avanzar el tiempo mantenemos una [`LedgerSnapshot`], definido en la crate [`soroban-ledger-snapshot`]. Para cada paso llamamos a [`Env::from_snapshot`] para crear un ambiente nuevo para ejecutar el paso, luego a [`Env::to_snapshot`] para crear una nueva imagen para usar en el paso siguiente.
-
-[`ledgersnapshot`]: https://docs.rs/soroban-ledger-snapshot/latest/soroban_ledger_snapshot/struct.LedgerSnapshot.html
-[`soroban-ledger-snapshot`]: https://docs.rs/soroban-ledger-snapshot
-[`env::from_snapshot`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Env.html#method.from_snapshot
-[`env::to_snapshot`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Env.html#method.to_snapshot
-
-Aquí hay un esquema simplificado de cómo funciona esto. Consulta el código fuente completo para más detalles.
-
-```rust title="fuzzing/fuzz/fuzz_targets/fuzz_target_2.rs"
-let snapshot = {
-    let init_ledger = LedgerInfo {
-        timestamp: 12345,
-        protocol_version: 1,
-        sequence_number: 10,
-        network_id: Default::default(),
-        base_reserve: 10,
-        min_temp_entry_ttl: u32::MAX,
-        min_persistent_entry_ttl: u32::MAX,
-        max_entry_ttl: u32::MAX,
-    };
-
-    LedgerSnapshot::from(init_ledger, None)
-};
-
-let mut prev_env = Env::from_snapshot(init_snapshot);
-
-for step in &config.input.steps {
-    // Advance time and create a new env from snapshot.
-    let curr_env = {
-        let mut snapshot = prev_env.to_snapshot();
-        snapshot.ledger.sequence_number += 1;
-        snapshot.ledger.timestamp = snapshot.ledger.timestamp.saturating_add(step.advance_time);
-        let env = Env::from_snapshot(snapshot);
-        env.cost_estimate().budget().reset_unlimited();
-        env
-    };
-
-    step.command.exec(&config, &curr_env);
-    assert_invariants(&config, &prev_env, &curr_env);
-
-    prev_env = curr_env;
-}
-```
-
-## Convertir una prueba de fuzzing en una prueba de propiedad
-
-Además de las pruebas de fuzzing, Soroban admite pruebas de propiedad al estilo de quickcheck, usando las crates [`proptest`] y [`proptest-arbitrary-interop`] junto con el trait `SorobanArbitrary`.
-
-Las pruebas de propiedad son similares a las pruebas de fuzzing en que generan entradas aleatorias. Sin embargo, las pruebas de propiedad no instrumentan sus casos de prueba ni mutan sus entradas basándose en retroalimentación de pruebas previas. Por lo tanto, son una forma más débil de prueba.
-
-La gran ventaja de las pruebas de propiedad es que pueden incluirse en suites de pruebas Rust estándar y no requieren herramientas adicionales para ejecutarse. Se puede aprovechar esto haciendo fuzzing interactivo para descubrir bugs profundos, y luego convertir las pruebas de fuzzing a pruebas de propiedad para ayudar a prevenir regresiones.
-
-El archivo [`proptest.rs`] es una traducción de `fuzz_target_1.rs` a una prueba de propiedad.
-
-[`proptest.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/fuzzing/src/proptest.rs
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/liquidity-pool.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/liquidity-pool.mdx
deleted file mode 100644
index d3442c33dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/liquidity-pool.mdx
+++ /dev/null
@@ -1,882 +0,0 @@
----
-title: Fondo de Liquidez
-description: Escribir un contrato de fondo de liquidez de producto constante.
-sidebar_position: 130
----
-
-<head>
-  <title>Escribir un contrato de fondo de liquidez de producto constante.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Escribir un contrato de fondo de liquidez de producto constante."
-  />
-  <meta
-    property="og:description"
-    content="Escribir un contrato inteligente de fondo de liquidez de producto constante."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de fondo de liquidez] demuestra cómo escribir un contrato de fondo de liquidez de producto constante. Un fondo de liquidez es una forma automatizada de añadir liquidez para un conjunto de tokens que facilitará la conversión de activos entre ellos. Los usuarios pueden depositar una cierta cantidad de cada token en el fondo, recibiendo un número proporcional de "acciones de token." El usuario recibirá entonces una parte de las tarifas de conversión acumuladas cuando finalmente "cambie" sus acciones de token para recibir de vuelta sus tokens originales.
-
-Los fondos de liquidez de Soroban son exclusivos de Soroban y no pueden interactuar con los fondos de liquidez AMM integrados de Stellar.
-
-:::caution
-
-Implementing a liquidity pool contract should be done cautiously. Los fondos de los usuarios están involucrados, así que se debe tener mucho cuidado para garantizar la seguridad y la transparencia. El ejemplo aquí _no_ debe considerarse un contrato listo para usar. Por favor, utilízalo solo como referencia.
-
-La red Stellar ya tiene funcionalidad de fondo de liquidez integrada en el protocolo base. [Aprende más aquí](../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx).
-
-:::
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de fondo de liquidez]: https://github.com/stellar/soroban-examples/tree/v23.0.0/liquidity_pool
-[código fuente]: https://github.com/stellar/soroban-examples/tree/v23.0.0/liquidity_pool/src/lib.rs#L143
-
-## Ejecutar el Ejemplo
-
-Primero realiza el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `liquidity_pool` y utiliza `cargo test`.
-
-```sh
-cd liquidity_pool
-cargo test
-```
-
-Deberías ver la salida:
-
-```text
-running 3 tests
-test test::deposit_amount_zero_should_panic - should panic ... ok
-test test::swap_reserve_one_nonzero_other_zero - should panic ... ok
-test test::test ... ok
-```
-
-[configuración]: ../getting-started/setup.mdx
-
-## Código
-
-```rust title="liquidity_pool/src/lib.rs"
-#![no_std]
-
-mod test;
-
-use num_integer::Roots;
-use soroban_sdk::{contract, contractimpl, contractmeta, contracttype, token, Address, Env};
-
-#[derive(Clone)]
-#[contracttype]
-pub enum DataKey {
-    TokenA,
-    TokenB,
-    TotalShares,
-    ReserveA,
-    ReserveB,
-    Shares(Address),
-}
-
-fn get_token_a(e: &Env) -> Address {
-    e.storage().instance().get(&DataKey::TokenA).unwrap()
-}
-
-fn get_token_b(e: &Env) -> Address {
-    e.storage().instance().get(&DataKey::TokenB).unwrap()
-}
-
-fn get_total_shares(e: &Env) -> i128 {
-    e.storage().instance().get(&DataKey::TotalShares).unwrap()
-}
-
-fn get_reserve_a(e: &Env) -> i128 {
-    e.storage().instance().get(&DataKey::ReserveA).unwrap()
-}
-
-fn get_reserve_b(e: &Env) -> i128 {
-    e.storage().instance().get(&DataKey::ReserveB).unwrap()
-}
-
-fn get_balance(e: &Env, contract: Address) -> i128 {
-    token::Client::new(e, &contract).balance(&e.current_contract_address())
-}
-
-fn get_balance_a(e: &Env) -> i128 {
-    get_balance(e, get_token_a(e))
-}
-
-fn get_balance_b(e: &Env) -> i128 {
-    get_balance(e, get_token_b(e))
-}
-
-fn get_shares(e: &Env, user: &Address) -> i128 {
-    e.storage()
-        .persistent()
-        .get(&DataKey::Shares(user.clone()))
-        .unwrap_or(0)
-}
-
-fn put_shares(e: &Env, user: &Address, amount: i128) {
-    e.storage()
-        .persistent()
-        .set(&DataKey::Shares(user.clone()), &amount);
-}
-
-fn put_token_a(e: &Env, contract: Address) {
-    e.storage().instance().set(&DataKey::TokenA, &contract);
-}
-
-fn put_token_b(e: &Env, contract: Address) {
-    e.storage().instance().set(&DataKey::TokenB, &contract);
-}
-
-fn put_total_shares(e: &Env, amount: i128) {
-    e.storage().instance().set(&DataKey::TotalShares, &amount)
-}
-
-fn put_reserve_a(e: &Env, amount: i128) {
-    e.storage().instance().set(&DataKey::ReserveA, &amount)
-}
-
-fn put_reserve_b(e: &Env, amount: i128) {
-    e.storage().instance().set(&DataKey::ReserveB, &amount)
-}
-
-fn burn_shares(e: &Env, from: &Address, amount: i128) {
-    let current_shares = get_shares(e, from);
-    if current_shares < amount {
-        panic!("insufficient shares");
-    }
-    let total = get_total_shares(e);
-    put_shares(e, from, current_shares - amount);
-    put_total_shares(e, total - amount);
-}
-
-fn mint_shares(e: &Env, to: &Address, amount: i128) {
-    let current_shares = get_shares(e, to);
-    let total = get_total_shares(e);
-    put_shares(e, to, current_shares + amount);
-    put_total_shares(e, total + amount);
-}
-
-fn transfer(e: &Env, token: Address, to: Address, amount: i128) {
-    token::Client::new(e, &token).transfer(&e.current_contract_address(), &to, &amount);
-}
-
-fn transfer_a(e: &Env, to: Address, amount: i128) {
-    transfer(e, get_token_a(e), to, amount);
-}
-
-fn transfer_b(e: &Env, to: Address, amount: i128) {
-    transfer(e, get_token_b(e), to, amount);
-}
-
-fn get_deposit_amounts(
-    desired_a: i128,
-    min_a: i128,
-    desired_b: i128,
-    min_b: i128,
-    reserve_a: i128,
-    reserve_b: i128,
-) -> (i128, i128) {
-    if reserve_a == 0 && reserve_b == 0 {
-        return (desired_a, desired_b);
-    }
-
-    let amount_b = desired_a * reserve_b / reserve_a;
-    if amount_b <= desired_b {
-        if amount_b < min_b {
-            panic!("amount_b less than min")
-        }
-        (desired_a, amount_b)
-    } else {
-        let amount_a = desired_b * reserve_a / reserve_b;
-        if amount_a > desired_a || amount_a < min_a {
-            panic!("amount_a invalid")
-        }
-        (amount_a, desired_b)
-    }
-}
-
-// Metadata that is added on to the WASM custom section
-contractmeta!(
-    key = "Description",
-    val = "Constant product AMM with a .3% swap fee"
-);
-
-#[contract]
-struct LiquidityPool;
-
-#[contractimpl]
-impl LiquidityPool {
-    pub fn __constructor(e: Env, token_a: Address, token_b: Address) {
-        if token_a >= token_b {
-            panic!("token_a must be less than token_b");
-        }
-
-        put_token_a(&e, token_a);
-        put_token_b(&e, token_b);
-        put_total_shares(&e, 0);
-        put_reserve_a(&e, 0);
-        put_reserve_b(&e, 0);
-    }
-
-    pub fn balance_shares(e: Env, user: Address) -> i128 {
-        get_shares(&e, &user)
-    }
-
-    pub fn deposit(
-        e: Env,
-        to: Address,
-        desired_a: i128,
-        min_a: i128,
-        desired_b: i128,
-        min_b: i128,
-    ) {
-        // Depositor needs to authorize the deposit
-        to.require_auth();
-
-        let (reserve_a, reserve_b) = (get_reserve_a(&e), get_reserve_b(&e));
-
-        // Calculate deposit amounts
-        let (amount_a, amount_b) =
-            get_deposit_amounts(desired_a, min_a, desired_b, min_b, reserve_a, reserve_b);
-
-        if amount_a <= 0 || amount_b <= 0 {
-            // If one of the amounts can be zero, we can get into a situation
-            // where one of the reserves is 0, which leads to a divide by zero.
-            panic!("both amounts must be strictly positive");
-        }
-
-        let token_a_client = token::Client::new(&e, &get_token_a(&e));
-        let token_b_client = token::Client::new(&e, &get_token_b(&e));
-
-        token_a_client.transfer(&to, &e.current_contract_address(), &amount_a);
-        token_b_client.transfer(&to, &e.current_contract_address(), &amount_b);
-
-        // Now calculate how many new pool shares to mint
-        let (balance_a, balance_b) = (get_balance_a(&e), get_balance_b(&e));
-        let total_shares = get_total_shares(&e);
-
-        let zero = 0;
-        let new_total_shares = if reserve_a > zero && reserve_b > zero {
-            let shares_a = (balance_a * total_shares) / reserve_a;
-            let shares_b = (balance_b * total_shares) / reserve_b;
-            shares_a.min(shares_b)
-        } else {
-            (balance_a * balance_b).sqrt()
-        };
-
-        mint_shares(&e, &to, new_total_shares - total_shares);
-        put_reserve_a(&e, balance_a);
-        put_reserve_b(&e, balance_b);
-    }
-
-    // If "buy_a" is true, the swap will buy token_a and sell token_b. This is flipped if "buy_a" is false.
-    // "out" is the amount being bought, with in_max being a safety to make sure you receive at least that amount.
-    // swap will transfer the selling token "to" to this contract, and then the contract will transfer the buying token to "to".
-    pub fn swap(e: Env, to: Address, buy_a: bool, out: i128, in_max: i128) {
-        to.require_auth();
-
-        let (reserve_a, reserve_b) = (get_reserve_a(&e), get_reserve_b(&e));
-        let (reserve_sell, reserve_buy) = if buy_a {
-            (reserve_b, reserve_a)
-        } else {
-            (reserve_a, reserve_b)
-        };
-
-        if reserve_buy < out {
-            panic!("not enough token to buy");
-        }
-
-        // First calculate how much needs to be sold to buy amount out from the pool
-        let n = reserve_sell * out * 1000;
-        let d = (reserve_buy - out) * 997;
-        let sell_amount = (n / d) + 1;
-        if sell_amount > in_max {
-            panic!("in amount is over max")
-        }
-
-        // Transfer the amount being sold to the contract
-        let sell_token = if buy_a {
-            get_token_b(&e)
-        } else {
-            get_token_a(&e)
-        };
-        let sell_token_client = token::Client::new(&e, &sell_token);
-        sell_token_client.transfer(&to, &e.current_contract_address(), &sell_amount);
-
-        let (balance_a, balance_b) = (get_balance_a(&e), get_balance_b(&e));
-
-        // residue_numerator and residue_denominator are the amount that the invariant considers after
-        // deducting the fee, scaled up by 1000 to avoid fractions
-        let residue_numerator = 997;
-        let residue_denominator = 1000;
-        let zero = 0;
-
-        let new_invariant_factor = |balance: i128, reserve: i128, out: i128| {
-            let delta = balance - reserve - out;
-            let adj_delta = if delta > zero {
-                residue_numerator * delta
-            } else {
-                residue_denominator * delta
-            };
-            residue_denominator * reserve + adj_delta
-        };
-
-        let (out_a, out_b) = if buy_a { (out, 0) } else { (0, out) };
-
-        let new_inv_a = new_invariant_factor(balance_a, reserve_a, out_a);
-        let new_inv_b = new_invariant_factor(balance_b, reserve_b, out_b);
-        let old_inv_a = residue_denominator * reserve_a;
-        let old_inv_b = residue_denominator * reserve_b;
-
-        if new_inv_a * new_inv_b < old_inv_a * old_inv_b {
-            panic!("constant product invariant does not hold");
-        }
-
-        if buy_a {
-            transfer_a(&e, to, out_a);
-        } else {
-            transfer_b(&e, to, out_b);
-        }
-
-        let new_reserve_a = balance_a - out_a;
-        let new_reserve_b = balance_b - out_b;
-
-        if new_reserve_a <= 0 || new_reserve_b <= 0 {
-            panic!("new reserves must be strictly positive");
-        }
-
-        put_reserve_a(&e, new_reserve_a);
-        put_reserve_b(&e, new_reserve_b);
-    }
-
-    // transfers share_amount of pool share tokens to this contract, burns all pools share tokens in this contracts, and sends the
-    // corresponding amount of token_a and token_b to "to".
-    // Returns amount of both tokens withdrawn
-    pub fn withdraw(
-        e: Env,
-        to: Address,
-        share_amount: i128,
-        min_a: i128,
-        min_b: i128,
-    ) -> (i128, i128) {
-        to.require_auth();
-
-        let current_shares = get_shares(&e, &to);
-        if current_shares < share_amount {
-            panic!("insufficient shares");
-        }
-
-        let (balance_a, balance_b) = (get_balance_a(&e), get_balance_b(&e));
-        let total_shares = get_total_shares(&e);
-
-        // Calculate withdrawal amounts
-        let out_a = (balance_a * share_amount) / total_shares;
-        let out_b = (balance_b * share_amount) / total_shares;
-
-        if out_a < min_a || out_b < min_b {
-            panic!("min not satisfied");
-        }
-
-        burn_shares(&e, &to, share_amount);
-        transfer_a(&e, to.clone(), out_a);
-        transfer_b(&e, to, out_b);
-        put_reserve_a(&e, balance_a - out_a);
-        put_reserve_b(&e, balance_b - out_b);
-
-        (out_a, out_b)
-    }
-
-    pub fn get_rsrvs(e: Env) -> (i128, i128) {
-        (get_reserve_a(&e), get_reserve_b(&e))
-    }
-}
-```
-
-Ref: https://github.com/stellar/soroban-examples/tree/v23.0.0/liquidity_pool
-
-## Cómo Funciona
-
-Cada activo creado en Stellar comienza con cero liquidez. Lo mismo ocurre con los tokens creados en Soroban (a menos que un activo Stellar con un token de liquidez existente tenga desplegado su [Contrato de Activo Stellar (SAC)](../../../tokens/stellar-asset-contract.mdx) para su uso en Soroban). En términos simples, "liquidez" significa cuántos de un activo en un mercado están disponibles para ser comprados o vendidos. En los "viejos tiempos," podías generar liquidez en un mercado creando órdenes de compra/venta en un libro de órdenes.
-
-Los fondos de liquidez automatizan este proceso sustituyendo las órdenes con matemáticas. Los depositantes en el fondo de liquidez ganan tarifas de las transacciones de `swap`. ¡No se requieren órdenes!
-
-Abre el archivo [`liquidity_pool/src/lib.rs`](https://github.com/stellar/soroban-examples/blob/v23.0.0/liquidity_pool/src/lib.rs) o consulta el código anterior para seguir el ejemplo.
-
-### Inicializar el Contrato
-
-Cuando se despliegue este contrato, la función `__constructor` se invocará de forma automática y atómica, por lo que deben pasarse los siguientes argumentos:
-
-- **`token_a`:** La `Dirección` del contrato para un token **ya desplegado** (o envuelto) que se mantendrá en reserva por el fondo de liquidez.
-- **`token_b`:** La `Dirección` del contrato para un token **ya desplegado** (o envuelto) que se mantendrá en reserva por el fondo de liquidez.
-
-Ten en cuenta que cuál token es `token_a` y cuál es `token_b` no es una distinción arbitraria. De acuerdo con los fondos de liquidez integrados en Stellar, este contrato puede hacer únicamente un fondo de liquidez para un conjunto dado de tokens. Por lo tanto, las direcciones de los tokens deben proporcionarse en [orden lexicográfico] en el momento de la inicialización.
-
-```rust title="liquidity_pool/src/lib.rs"
-pub fn __constructor(e: Env, token_a: Address, token_b: Address) {
-    if token_a >= token_b {
-        panic!("token_a must be less than token_b");
-    }
-
-    put_token_a(&e, token_a);
-    put_token_b(&e, token_b);
-    put_total_shares(&e, 0);
-    put_reserve_a(&e, 0);
-    put_reserve_b(&e, 0);
-}
-```
-
-[creando su propio token `pool`]: #minting-and-burning-lp-shares
-[interactuando con contratos para `token_a` y `token_b`]: #token-transfers-tofrom-the-lp-contract
-[orden lexicográfico]: ../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#liquidity-pool-participation
-
-### Un Fondo de Liquidez de "Producto Constante"
-
-El _tipo_ de fondo de liquidez que implementa este contrato de ejemplo se llama un fondo de liquidez de "producto constante". Aunque este no es el único tipo de fondo de liquidez que existe, es la variedad más común. Estos fondos de liquidez están diseñados para mantener el _valor total_ de cada activo en _equilibrio relativo_. El "producto" en el producto constante (también llamado "invariante") cambiará cada vez que se interactúe con el fondo de liquidez (depósito, retiro o intercambios de tokens). Sin embargo, el invariante **debe** solo aumentar con cada interacción.
-
-Durante un intercambio, lo que debe tenerse en cuenta es que por cada retiro del lado de `token_a`, debes "rellenar" el lado de `token_b` con una cantidad suficiente para mantener el precio del fondo de liquidez equilibrado. La matemática es predecible, pero no es lineal. Cuanto más tomes de un lado, más debes dar en el lado opuesto _exponencialmente_.
-
-Dentro de la función `swap`, la matemática se hace así (sin embargo, esta es una versión simplificada):
-
-```rust title="liquidity_pool/src/lib.rs"
-pub fn swap(e: Env, to: Address, buy_a: bool, out: i128, in_max: i128) {
-    // Get the current balances of both tokens in the liquidity pool
-    let (reserve_sell, reserve_buy) = (get_reserve_a(&e), get_reserve_b(&e));
-
-    // Calculate how much needs to be
-    let n = reserve_sell * out * 1000;
-    let d = (reserve_buy - out) * 997;
-    let sell_amount = (n / d) + 1;
-}
-```
-
-Tenemos información mucho más detallada sobre cómo funciona este tipo de fondo de liquidez disponible en [Stellar Quest: Serie 3, Misión 5]. Esta es una forma muy útil e interactiva de aprender más sobre cómo funcionan los fondos de liquidez integrados en Stellar. Gran parte del conocimiento que podrías obtener de allí se traducirá fácilmente a este contrato de ejemplo.
-
-[stellar quest: serie 3, misión 5]: https://quest.stellar.org/learn/series/3/quest/5
-
-### Interactuar con contratos de tokens en otro contrato
-
-Este contrato de fondo de liquidez funcionará con un total de tres tokens diferentes de Soroban:
-
-- **Participaciones del pool:** Este ejemplo usa un token de participación muy simple entregado a los depositantes de activos a cambio de su depósito. Estos tokens son "cambiados" por el usuario cuando retira alguna cantidad de su depósito original (más cualquier tarifa de intercambio obtenida). En este sistema simplificado, las participaciones simplemente se suman o restan cada vez que un usuario deposita o retira los activos subyacentes. No se utilizará un _contrato de token_ distinto para estas participaciones.
-- **`token_a`** y **`token_b`**: Serán los dos "tokens en reserva" que los usuarios depositarán en el fondo. Estos podrían ser tokens "envueltos" de activos de Stellar preexistentes, o podrían ser tokens nativos de Soroban. A este contrato realmente no le importa, siempre que las funciones que necesita de la [Interfaz de Token] común estén disponibles en el contrato del token.
-
-[interfaz de token]: ../../../tokens/token-interface.mdx
-
-#### Creación y destrucción de participaciones LP
-
-Estamos creando y destruyendo participaciones LP dentro de la lógica del contrato principal, en lugar de usar un contrato de token distinto. Se han creado algunas funciones "auxiliares" para facilitar esta funcionalidad. Estas funciones se utilizan cuando un usuario realiza cualquier acción de depósito o retiro.
-
-```rust title="liquidity_pool/src/lib.rs"
-fn burn_shares(e: &Env, from: &Address, amount: i128) {
-    let current_shares = get_shares(e, from);
-    if current_shares < amount {
-        panic!("insufficient shares");
-    }
-    let total = get_total_shares(e);
-    put_shares(e, from, current_shares - amount);
-    put_total_shares(e, total - amount);
-}
-
-fn mint_shares(e: &Env, to: &Address, amount: i128) {
-    let current_shares = get_shares(e, to);
-    let total = get_total_shares(e);
-    put_shares(e, to, current_shares + amount);
-    put_total_shares(e, total + amount);
-}
-```
-
-¿Cómo se calcula ese número de acciones, preguntas? ¡Excelente pregunta! Si es el primer depósito (ver arriba), es solo la raíz cuadrada del producto de las cantidades de `token_a` y `token_b` depositados. Muy simple.
-
-Sin embargo, si ya ha habido depósitos en el fondo de liquidez, y el usuario solo está añadiendo más tokens al fondo, hay un poco más de matemáticas. Sin embargo, el punto principal es que cada depositante recibe la misma proporción de tokens `POOL` por su depósito que cada otro depositante.
-
-```rust title=liquidity_pool/src/lib.rs
-fn deposit(e: Env, to: Address, desired_a: i128, min_a: i128, desired_b: i128, min_b: i128) {
-    let zero = 0;
-    let new_total_shares = if reserve_a > zero && reserve_b > zero {
-        // Note balance_a and balance_b at this point in the function include
-        // the tokens the user is currently depositing, whereas reserve_a and
-        // reserve_b do not yet.
-        let shares_a = (balance_a * total_shares) / reserve_a;
-        let shares_b = (balance_b * total_shares) / reserve_b;
-        shares_a.min(shares_b)
-    } else {
-        (balance_a * balance_b).sqrt()
-    };
-}
-```
-
-#### Transferencias de Tokens de/a Contrato LP
-
-Como ya hemos discutido, el contrato de fondo de liquidez utilizará la [Interfaz de Token] disponible en los contratos de tokens que se suministraron como argumentos `token_a` y `token_b` en el momento de la inicialización. A lo largo del resto del contrato, el fondo de liquidez utilizará esa interfaz para hacer transferencias de esos tokens de/a sí mismo.
-
-Lo que sucede es que, a medida que un usuario deposita tokens en el fondo, el contrato invoca la función `transfer` para mover los tokens de la dirección `to` (el depositante) para ser mantenidos por la dirección del contrato. Los tokens `POOL` son luego acuñados al depositante (ver sección anterior). ¡Bastante simple, verdad!?
-
-```rust title="liquidity_pool/src/lib.rs"
-fn deposit(e: Env, to: Address, desired_a: i128, min_a: i128, desired_b: i128, min_b: i128) {
-    // Depositor needs to authorize the deposit
-    to.require_auth();
-
-    let token_a_client = token::Client::new(&e, &get_token_a(&e));
-    let token_b_client = token::Client::new(&e, &get_token_b(&e));
-
-    token_a_client.transfer(&to, &e.current_contract_address(), &amount_a);
-    token_b_client.transfer(&to, &e.current_contract_address(), &amount_b);
-
-    mint_shares(&e, to, new_total_shares - total_shares);
-}
-```
-
-En cambio, cuando un usuario retira sus tokens depositados, es un proceso un poco más complejo y ocurre el siguiente procedimiento.
-
-1. Se verifica que el número de participaciones que el usuario "canjea" coincida con la cantidad _real_ de participaciones que posee el usuario.
-2. Se calculan los importes de retiro para los tokens de reserva basándose en la cantidad de tokens de participación que se canjean.
-3. Los tokens de participación se destruyen ahora que se han calculado los importes de retiro y ya no son necesarios.
-4. Las cantidades respectivas de `token_a` y `token_b` se transfieren _desde_ la dirección del contrato a la dirección `to` (el depositante).
-
-```rust title="liquidity_pool/src/lib.rs"
-fn withdraw(e: Env, to: Address, share_amount: i128, min_a: i128, min_b: i128) -> (i128, i128) {
-    to.require_auth();
-
-    // First calculate the specified pool shares are available to the user
-    let current_shares = get_shares(&e, &to);
-    if current_shares < share_amount {
-        panic!("insufficient shares");
-    }
-
-    // ... balances of pool shares and underlying assets are retrieved
-
-    // Now calculate the withdraw amounts
-    let out_a = (balance_a * balance_shares) / total_shares;
-    let out_b = (balance_b * balance_shares) / total_shares;
-
-    burn_shares(&e, balance_shares);
-    transfer_a(&e, to.clone(), out_a);
-    transfer_b(&e, to, out_b);
-}
-```
-
-Notarás que al mantener el saldo de `token_a` y `token_b` en el contrato de fondo de liquidez, se facilita mucho realizar cualquier acción de la [Interfaz de Token] dentro del contrato. Como un bono, cualquier observador externo podría consultar los saldos de `token_a` o `token_b` mantenidos por el contrato para verificar que las reservas están realmente alineadas con los valores que el contrato informa cuando se invoca su propia función `get_rsvs`.
-
-## Pruebas
-
-Abre el archivo [`liquidity_pool/src/test.rs`] para seguir adelante.
-
-```rust title="liquidity_pool/src/test.rs"
-#![cfg(test)]
-extern crate std;
-
-use crate::LiquidityPoolClient;
-
-use soroban_sdk::{
-    symbol_short,
-    testutils::{Address as _, AuthorizedFunction, AuthorizedInvocation},
-    token, Address, Env, IntoVal,
-};
-
-fn create_token_contract<'a>(
-    e: &Env,
-    admin: &Address,
-) -> (token::Client<'a>, token::StellarAssetClient<'a>) {
-    let sac = e.register_stellar_asset_contract_v2(admin.clone());
-    (
-        token::Client::new(e, &sac.address()),
-        token::StellarAssetClient::new(e, &sac.address()),
-    )
-}
-
-fn create_liqpool_contract<'a>(
-    e: &Env,
-    token_a: &Address,
-    token_b: &Address,
-) -> LiquidityPoolClient<'a> {
-    LiquidityPoolClient::new(e, &e.register(crate::LiquidityPool {}, (token_a, token_b)))
-}
-
-#[test]
-fn test() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    let admin1 = Address::generate(&e);
-    let admin2 = Address::generate(&e);
-
-    let (token1, token1_admin) = create_token_contract(&e, &admin1);
-    let (token2, token2_admin) = create_token_contract(&e, &admin2);
-    let user1 = Address::generate(&e);
-
-    let liqpool = create_liqpool_contract(&e, &token1.address, &token2.address);
-
-    token1_admin.mint(&user1, &1000);
-    assert_eq!(token1.balance(&user1), 1000);
-
-    token2_admin.mint(&user1, &1000);
-    assert_eq!(token2.balance(&user1), 1000);
-
-    liqpool.deposit(&user1, &100, &100, &100, &100);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    liqpool.address.clone(),
-                    symbol_short!("deposit"),
-                    (&user1, 100_i128, 100_i128, 100_i128, 100_i128).into_val(&e)
-                )),
-                sub_invocations: std::vec![
-                    AuthorizedInvocation {
-                        function: AuthorizedFunction::Contract((
-                            token1.address.clone(),
-                            symbol_short!("transfer"),
-                            (&user1, &liqpool.address, 100_i128).into_val(&e)
-                        )),
-                        sub_invocations: std::vec![]
-                    },
-                    AuthorizedInvocation {
-                        function: AuthorizedFunction::Contract((
-                            token2.address.clone(),
-                            symbol_short!("transfer"),
-                            (&user1, &liqpool.address, 100_i128).into_val(&e)
-                        )),
-                        sub_invocations: std::vec![]
-                    }
-                ]
-            }
-        )]
-    );
-
-    assert_eq!(liqpool.balance_shares(&user1), 100);
-    assert_eq!(token1.balance(&user1), 900);
-    assert_eq!(token1.balance(&liqpool.address), 100);
-    assert_eq!(token2.balance(&user1), 900);
-    assert_eq!(token2.balance(&liqpool.address), 100);
-
-    liqpool.swap(&user1, &false, &49, &100);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    liqpool.address.clone(),
-                    symbol_short!("swap"),
-                    (&user1, false, 49_i128, 100_i128).into_val(&e)
-                )),
-                sub_invocations: std::vec![AuthorizedInvocation {
-                    function: AuthorizedFunction::Contract((
-                        token1.address.clone(),
-                        symbol_short!("transfer"),
-                        (&user1, &liqpool.address, 97_i128).into_val(&e)
-                    )),
-                    sub_invocations: std::vec![]
-                }]
-            }
-        )]
-    );
-
-    assert_eq!(token1.balance(&user1), 803);
-    assert_eq!(token1.balance(&liqpool.address), 197);
-    assert_eq!(token2.balance(&user1), 949);
-    assert_eq!(token2.balance(&liqpool.address), 51);
-
-    e.cost_estimate().budget().reset_unlimited();
-    liqpool.withdraw(&user1, &100, &197, &51);
-
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    liqpool.address.clone(),
-                    symbol_short!("withdraw"),
-                    (&user1, 100_i128, 197_i128, 51_i128).into_val(&e)
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-
-    assert_eq!(token1.balance(&user1), 1000);
-    assert_eq!(token2.balance(&user1), 1000);
-    assert_eq!(liqpool.balance_shares(&user1), 0);
-    assert_eq!(token1.balance(&liqpool.address), 0);
-    assert_eq!(token2.balance(&liqpool.address), 0);
-}
-
-#[test]
-#[should_panic]
-fn deposit_amount_zero_should_panic() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    // Create contracts
-    let admin1 = Address::generate(&e);
-    let admin2 = Address::generate(&e);
-
-    let (token1, token1_admin) = create_token_contract(&e, &admin1);
-    let (token2, token2_admin) = create_token_contract(&e, &admin2);
-    let liqpool = create_liqpool_contract(&e, &token1.address, &token2.address);
-
-    // Create a user
-    let user1 = Address::generate(&e);
-
-    token1_admin.mint(&user1, &1000);
-    assert_eq!(token1.balance(&user1), 1000);
-
-    token2_admin.mint(&user1, &1000);
-    assert_eq!(token2.balance(&user1), 1000);
-
-    liqpool.deposit(&user1, &1, &0, &0, &0);
-}
-
-#[test]
-#[should_panic]
-fn swap_reserve_one_nonzero_other_zero() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    // Create contracts
-    let admin1 = Address::generate(&e);
-    let admin2 = Address::generate(&e);
-
-    let (token1, token1_admin) = create_token_contract(&e, &admin1);
-    let (token2, token2_admin) = create_token_contract(&e, &admin2);
-
-    let liqpool = create_liqpool_contract(&e, &token1.address, &token2.address);
-
-    // Create a user
-    let user1 = Address::generate(&e);
-
-    token1_admin.mint(&user1, &1000);
-    assert_eq!(token1.balance(&user1), 1000);
-
-    token2_admin.mint(&user1, &1000);
-    assert_eq!(token2.balance(&user1), 1000);
-
-    // Try to get to a situation where the reserves are 1 and 0.
-    // It shouldn't be possible.
-    token2.transfer(&user1, &liqpool.address, &1);
-    liqpool.swap(&user1, &false, &1, &1);
-}
-```
-
-[`liquidity_pool/src/test.rs`]: https://github.com/stellar/soroban-examples/tree/v23.0.0/liquidity_pool/src/test.rs
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno Soroban donde se ejecutará el contrato.
-
-```rust title="liquidity_pool/src/test.rs"
-let e = Env::default();
-```
-
-Simulamos cheques de autenticación en las pruebas, lo que permite que las pruebas avancen como si todos los usuarios/direcciones/contratos, etc. se hubieran autenticado con éxito.
-
-```rust title="liquidity_pool/src/test.rs"
-e.mock_all_auths();
-```
-
-Hemos abstraído en un par de funciones las tareas de crear contratos de tokens y desplegar un contrato de pool de liquidez. Cada una se utiliza luego dentro de la prueba.
-
-```rust title="liquidity_pool/src/test.rs"
-fn create_token_contract<'a>(
-    e: &Env,
-    admin: &Address,
-) -> (token::Client<'a>, token::StellarAssetClient<'a>) {
-    let sac = e.register_stellar_asset_contract_v2(admin.clone());
-    (
-        token::Client::new(e, &sac.address()),
-        token::StellarAssetClient::new(e, &sac.address()),
-    )
-}
-
-fn create_liqpool_contract<'a>(
-    e: &Env,
-    token_a: &Address,
-    token_b: &Address,
-) -> LiquidityPoolClient<'a> {
-    LiquidityPoolClient::new(e, &e.register(crate::LiquidityPool {}, (token_a, token_b)))
-}
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente se nombrará igual que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato, el tipo de contrato es `LiquidityPool`, y el cliente se llama `LiquidityPoolClient`.
-
-Estas pruebas examinan el uso "típico" de un fondo de liquidez, asegurando que los saldos, retornos, etc. sean apropiados en varios puntos durante la prueba.
-
-1. Primero, la prueba configura todo con un `Env`, dos direcciones administrativas, dos tokens en reserva, una dirección generada aleatoriamente para actuar como el usuario del fondo de liquidez, el fondo de liquidez mismo, un contrato de acciones de token del fondo, y acuña los activos de reserva a la dirección del usuario.
-2. El usuario luego deposita algunos de cada activo en el fondo de liquidez. En este momento, se realizan las siguientes comprobaciones:
-   - existen autorizaciones apropiadas para depósitos y transferencias,
-   - los saldos se verifican para cada token (`token_a`, `token_b`, y `POOL`) desde la perspectiva del usuario y de la perspectiva del contrato `liqpool`
-3. El usuario realiza un intercambio, comprando `token_b` a cambio de `token_a`. Ahora se realizan las mismas comprobaciones que en el paso anterior, exceptuando los saldos de `POOL`, ya que un intercambio no tiene efecto sobre los tokens `POOL`.
-4. El usuario luego retira todos los depósitos que realizó, cambiando todos sus tokens `POOL` en el proceso. Aquí se realizan las mismas comprobaciones que se hicieron en el paso de `depósito`.
-
-## Crear el Contrato
-
-Para crear el contrato, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-Un archivo `.wasm` debería ser generado en el directorio `target`:
-
-```
-target/wasm32v1-none/release/soroban_liquidity_pool_contract.wasm
-```
-
-## Ejecutar el Contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar funciones del contrato usándolo.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --wasm target/wasm32v1-none/release/soroban_liquidity_pool_contract.wasm \
-    --id 1 \
-    -- \
-    deposit \
-    --to GBZV3NONYSUDVTEHATQO4BCJVFXJO3XQU5K32X3XREVZKSMMOZFO4ZXR \
-    --desired_a 100 \
-    --min_a 98 \
-    --desired_be 200 \
-    --min_b 196
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --wasm target/wasm32v1-none/release/soroban_liquidity_pool_contract.wasm `
-    --id 1 `
-    -- `
-    deposit `
-    --to GBZV3NONYSUDVTEHATQO4BCJVFXJO3XQU5K32X3XREVZKSMMOZFO4ZXR `
-    --desired_a 100 `
-    --min_a 98 `
-    --desired_be 200 `
-    --min_b 196
-```
-
-</TabItem>
-</Tabs>
-
-[`stellar-cli`]: ../../../tools/cli/stellar-cli.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/logging.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/logging.mdx
deleted file mode 100644
index 571a5c72a9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/logging.mdx
+++ /dev/null
@@ -1,293 +0,0 @@
----
-title: Registro
-description: Depurar un contrato inteligente con registros.
-sidebar_position: 40
----
-
-<head>
-  <title>Depurar un contrato inteligente con registros.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Depurar un contrato inteligente con registros." />
-  <meta
-    property="og:description"
-    content="Utiliza el registro para depurar tus contratos inteligentes."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de registro] demuestra cómo registrar con el propósito de depuración.
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-Los registros en los contratos solo son visibles en las pruebas, o al ejecutar contratos utilizando [`stellar-cli`]. Los registros solo se compilan en el contrato si la opción del compilador Rust `debug-assertions` está habilitada.
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de registro]: https://github.com/stellar/soroban-examples/tree/v23.0.0/hello_world
-
-:::tip
-
-Los registros no son un sustituto para la depuración paso a paso. Las pruebas de Rust para Soroban se pueden depurar paso a paso en tu IDE habilitado para Rust. Consulta [pruebas] para más detalles.
-
-:::
-
-:::caution
-
-Los registros no son accesibles por dapps y otras aplicaciones. Consulta el [ejemplo de eventos] para saber cómo producir eventos estructurados.
-
-:::
-
-[pruebas]: ../getting-started/hello-world.mdx#run-the-tests
-[ejemplo de eventos]: ./events.mdx
-
-## Ejecutar el ejemplo
-
-Primero, sigue el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O bien, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `logging`, y utiliza `cargo test`.
-
-```sh
-cd logging
-cargo test -- --nocapture
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-[Diagnostic Event] contract:CAAA..., topics:[log], data:["Hello {}", Dev]
-[Diagnostic Event] contract:CAAA..., topics:[log], data:["Hello {}", Dev]
-Writing test snapshot file for test "test::test" to "test_snapshots/test/test.1.json".
-test test::test ... ok
-```
-
-## Código
-
-```toml title="logging/Cargo.toml"
-[profile.release-with-logs]
-inherits = "release"
-debug-assertions = true
-```
-
-```rust title="logging/src/lib.rs"
-#![no_std]
-use soroban_sdk::{contract, contractimpl, log, Env, Symbol};
-
-#[contract]
-pub struct Contract;
-
-#[contractimpl]
-impl Contract {
-    pub fn hello(env: Env, value: Symbol) {
-        log!(&env, "Hello {}", value);
-    }
-}
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/logging
-
-## Cómo funciona
-
-El macro [`log!`] registra una cadena. Todos los registros que ocurren durante la ejecución se envían a stdout en [`stellar-cli`] y están disponibles para que las pruebas validen o impriman.
-
-Los registros solo se envían si el contrato se construye con la opción del compilador `debug-assertions` habilitada. Esto hace que sea eficiente dejarlos en el código de forma permanente, ya que una construcción `release` regular los omitirá.
-
-Los registros solo se almacenan en los entornos de Soroban que tienen el registro habilitado. Los únicos entornos de Soroban donde el registro está habilitado son en las pruebas de Rust, y en el [`stellar-cli`].
-
-Abre los archivos anteriores para seguirlo.
-
-### `Cargo.toml` Perfil
-
-Los registros solo se envían si el contrato se construye con la opción del compilador `debug-assertions` habilitada.
-
-El perfil `test` que se activa al ejecutar `cargo test` tiene habilitadas las `debug-assertions`, así que al ejecutar pruebas, los registros están habilitados por defecto.
-
-Se añade un nuevo perfil `release-with-logs` a `Cargo.toml` que hereda del perfil `release`, y habilita `debug-assertions`. Se puede utilizar para construir un archivo `.wasm` que tiene los registros habilitados.
-
-```toml
-[profile.release-with-logs]
-inherits = "release"
-debug-assertions = true
-```
-
-Para construir sin registros utiliza la opción `--release` o `--profile release`.
-
-Para construir con registros utiliza la opción `--profile release-with-logs`.
-
-### Usando el macro `log!`
-
-El macro [`log!`] construye una cadena a partir de la cadena de formato y una lista de argumentos. Los argumentos se sustituyen dondequiera que aparezca el valor `{}` en la cadena de formato.
-
-```rust
-log!(&env, "Hello {}", value);
-```
-
-El registro anterior se representará como sigue si `value` es un `Symbol` que contiene "Dev".
-
-```
-Hello Symbol(Dev)
-```
-
-:::caution
-
-Los valores enviados actualmente son relativamente limitados. Mientras que valores primitivos como `u32`, `u64`, `bool`, y `Symbol`s se representarán claramente en la salida del registro, `Bytes`, `Vec`, `Map`, y tipos personalizados solo representarán su número de identificador. Las capacidades de registro están en desarrollo inicial.
-
-:::
-
-## Pruebas
-
-Abre el archivo [`logging/src/test.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/logging/src/test.rs) para seguir los pasos.
-
-```rust title="logging/src/test.rs"
-extern crate std;
-
-#[test]
-fn test() {
-    let env = Env::default();
-
-    let addr = Address::from_str(
-        &env,
-        "CAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQMCJ",
-    );
-    let contract_id = env.register_at(&addr, Contract, ());
-    let client = ContractClient::new(&env, &contract_id);
-
-    client.hello(&symbol_short!("Dev"));
-
-    let logs = env.logs().all();
-    assert_eq!(logs, std::vec!["[Diagnostic Event] contract:CAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQMCJ, topics:[log], data:[\"Hello {}\", Dev]"]);
-    std::println!("{}", logs.join("\n"));
-}
-```
-
-El crate `std`, que contiene la biblioteca estándar de Rust, se importa para que la prueba pueda usar los macros `std::vec!` y `std::println!`. Dado que los contratos deben usar `#![no_std]`, las pruebas en contratos deben importar manualmente `std` para usar funcionalidades de `std` como imprimir en stdout.
-
-```rust
-extern crate std;
-```
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno de Soroban en el que se ejecutará el contrato.
-
-```rust
-let env = Env::default();
-```
-
-El contrato se registra con el entorno utilizando el tipo de contrato. Estamos especificando exactamente en qué dirección de contrato debe desplegarse el contrato en la prueba, usando la función `env.register_at`. Esto facilita asegurar que la salida de los logs proviene de la dirección de contrato relevante.
-
-```rust
-let addr = Address::from_str(
-    &env,
-    "CAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQMCJ",
-);
-let contract_id = env.register_at(&addr, Contract, ());
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente se nombrará igual que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato, el tipo de contrato es `HelloContract`, y el cliente se llama `HelloContractClient`.
-
-```rust
-let client = ContractClient::new(&env, &contract_id);
-client.hello(&symbol_short!("Dev"));
-```
-
-Los registros están disponibles en las pruebas a través del entorno.
-
-```rust
-let logs = env.logs().all();
-```
-
-Se pueden afirmar igual que cualquier otro valor.
-
-```rust
-assert_eq!(logs, std::vec!["[Diagnostic Event] contract:CAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQCAIBAEAQMCJ, topics:[log], data:[\"Hello {}\", Dev]"]);
-```
-
-También pueden imprimirse en stdout.
-
-```rust
-std::println!("{}", logs.join("\n"));
-```
-
-## Construir el contrato
-
-Para construir el contrato, utiliza el comando `stellar contract build`.
-
-### Sin registros
-
-Para construir el contrato sin registros, utiliza la opción `--release`.
-
-```sh
-stellar contract build
-```
-
-Un archivo `.wasm` debería ser enviado al directorio `target`, en el subdirectorio `release`:
-
-```
-target/wasm32v1-none/release/soroban_logging_contract.wasm
-```
-
-### Con registros
-
-Para construir el contrato con registros, utiliza la opción `--profile release-with-logs`.
-
-```sh
-stellar contract build --profile release-with-logs
-```
-
-Un archivo `.wasm` debería ser enviado al directorio `target`, en el subdirectorio `release-with-logs`:
-
-```
-target/wasm32v1-none/release-with-logs/soroban_logging_contract.wasm
-```
-
-## Ejecutar el contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar funciones del contrato usándolo. Especifica la opción `-v` para habilitar registros detallados.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar -v contract invoke \
-    --wasm target/wasm32v1-none/release-with-logs/soroban_logging_contract.wasm \
-    --id 1 \
-    -- \
-    hello \
-    --value friend
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar -v contract invoke `
-    --wasm target/wasm32v1-none/release-with-logs/soroban_logging_contract.wasm `
-    --id 1 `
-    -- `
-    hello `
-    --value friend
-```
-
-</TabItem>
-</Tabs>
-
-La salida debe incluir la siguiente línea.
-
-```
-📔 CAAA... - Success - Log: {"vec":[{"string":"Hello {}"},{"symbol":"friend"}]}
-```
-
-[`log!`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/macro.log.html
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/mint-lock.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/mint-lock.mdx
deleted file mode 100644
index 5c22f9218a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/mint-lock.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Bloquear creación
-description: Implementar un contrato que puede delegar la creación con límites.
-sidebar_position: 110
----
-
-<head>
-  <title>{`Implementar un contrato que puede delegar la creación con límites.`}</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Implementar un contrato que puede delegar la creación con límites."
-  />
-  <meta
-    property="og:description"
-    content="Implementar un contrato que puede delegar la creación con límites."
-  />
-</head>
-
-El [ejemplo de bloqueo de creación] demuestra cómo escribir un contrato que puede delegar la creación de tokens desde otra dirección con límites sobre cuánto esas direcciones pueden crear en un período de tiempo específico.
-
-El administrador de los contratos de tokens utilizados debe ser el contrato de bloqueo de creación.
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de bloqueo de creación]: https://github.com/stellar/soroban-examples/tree/v23.0.0/mint-lock
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/non-fungible-token.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/non-fungible-token.mdx
deleted file mode 100644
index 00ef67e4b7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/non-fungible-token.mdx
+++ /dev/null
@@ -1,235 +0,0 @@
----
-title: Token No Fungible
-description: Contrato desarrollado y auditado por OpenZeppelin para tokens no fungibles en Stellar.
-sidebar_position: 142
----
-
-<head>
-  <title>Token No Fungible por OpenZeppelin</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Token No Fungible por OpenZeppelin" />
-  <meta
-    property="og:description"
-    content="Contrato desarrollado y auditado por OpenZeppelin para tokens no fungibles en Stellar"
-  />
-</head>
-
-# Token No Fungible
-
-[Código Fuente](https://github.com/OpenZeppelin/stellar-contracts/tree/main/packages/tokens/src/non_fungible)
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=openzeppelin/stellar-contracts&editor=web
-
-En el mundo de los activos digitales, no todos los tokens son iguales. Esto es importante en situaciones como **bienes raíces**, **derechos de voto** o **coleccionables**, donde algunos artículos tienen más valor debido a su utilidad, rareza, etc. En Stellar, puedes crear tokens no fungibles (NFTs), donde cada token es único y representa algo distinto, con la propiedad rastreada mediante contratos inteligentes Soroban.
-
-## Resumen
-
-El módulo [non-fungible](https://github.com/OpenZeppelin/stellar-contracts/tree/main/packages/tokens/src/non_fungible) ofrece tres variantes diferentes de NFT que se diferencian en cómo se manejan ciertas funciones como el seguimiento de la propiedad, la creación y destrucción de tokens:
-
-1. **Base**: Variante de contrato que implementa la lógica base para la interfaz NonFungibleToken. Adecuada para la mayoría de los casos de uso.
-2. **Consecutiva**: Variante de contrato para la creación optimizada de lotes de tokens. Se basa en la variante base y sobrescribe las funciones necesarias de la variante `Base`.
-3. **Enumerada**: Variante de contrato que permite enumerar los tokens on-chain. Se basa en la variante base y sobrescribe las funciones necesarias de la variante `Base`.
-
-Estas tres variantes comparten funcionalidades principales y una interfaz común, exponiendo funciones idénticas del contrato como puntos de entrada. Sin embargo, la composición de flujos personalizados debe manejarse con especial cuidado. Esto es necesario debido a la naturaleza incompatible entre la lógica de negocio de las diferentes variantes de NFT o la necesidad de envolver la funcionalidad base con lógica adicional.
-
-## Ejecutar el Ejemplo
-
-Primero realiza el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona el repositorio OpenZeppelin Stellar Contracts:
-
-```sh
-git clone https://github.com/OpenZeppelin/stellar-contracts
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces] o [Code Anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `nft-sequential-minting` y usa `cargo test`.
-
-```sh
-cd examples/nft-sequential-minting
-cargo test
-```
-
-[configuración]: ../getting-started/setup.mdx
-[GitHub Codespaces]: https://github.com/codespaces/new?repo=OpenZeppelin/stellar-contracts&editor=web
-[Code Anywhere]: https://app.codeanywhere.com/#https://github.com/OpenZeppelin/stellar-contracts
-
-## Código
-
-:::note
-
-Este ejemplo demuestra cómo usar la biblioteca OpenZeppelin Stellar Contracts para crear un token no fungible. La biblioteca proporciona implementaciones desarrolladas y auditadas que siguen las prácticas recomendadas.
-
-:::
-
-```rust title="examples/nft-sequential-minting/src/contract.rs"
-use soroban_sdk::{contract, contractimpl, Address, Env, String};
-use stellar_access::ownable::{self as ownable, Ownable};
-use stellar_macros::{default_impl, only_owner};
-use stellar_tokens::non_fungible::{
-    burnable::NonFungibleBurnable, Base, ContractOverrides, NonFungibleToken,
-};
-
-#[contract]
-pub struct NonFungibleTokenContract;
-
-#[contractimpl]
-impl NonFungibleTokenContract {
-    pub fn __constructor(e: &Env, owner: Address) {
-        // Set token metadata
-        Base::set_metadata(
-            e,
-            String::from_str(e, "www.example.com"),
-            String::from_str(e, "My NFT Collection"),
-            String::from_str(e, "MNFT"),
-        );
-
-        // Set the contract owner
-        ownable::set_owner(e, &owner);
-    }
-
-    #[only_owner]
-    pub fn mint(e: &Env, to: Address) -> u32 {
-        Base::sequential_mint(e, &to)
-    }
-}
-
-#[default_impl]
-#[contractimpl]
-impl NonFungibleToken for NonFungibleTokenContract {
-    type ContractType = Base;
-}
-
-#[default_impl]
-#[contractimpl]
-impl NonFungibleBurnable for NonFungibleTokenContract {}
-
-#[default_impl]
-#[contractimpl]
-impl Ownable for NonFungibleTokenContract {}
-```
-
-Ref: https://github.com/OpenZeppelin/stellar-contracts/tree/main/examples/nft-sequential-minting
-
-## Cómo Funciona
-
-Este ejemplo muestra cómo crear un token no fungible utilizando la biblioteca OpenZeppelin Stellar Contracts. La biblioteca proporciona implementaciones preconstruidas y auditadas que garantizan seguridad y siguen las prácticas recomendadas de la industria.
-
-El contrato implementa varias características clave:
-
-1. **Creación Secuencial**: Asigna automáticamente IDs de token secuenciales comenzando desde 1
-2. **Control de Propiedad**: Usa el patrón Ownable para funciones administrativas
-3. **Tokens Quemables**: Permite que los poseedores de tokens puedan quemarlos
-4. **Creación Segura**: Solo el propietario del contrato puede crear nuevos tokens
-
-Al aprovechar la biblioteca OpenZeppelin, los desarrolladores pueden concentrarse en su lógica de negocio específica mientras confían en implementaciones probadas para la funcionalidad central de los NFT.
-
-### Uso de Componentes de la Biblioteca OpenZeppelin
-
-La biblioteca OpenZeppelin Stellar Contracts proporciona componentes modulares que pueden componerse fácilmente:
-
-- **`Base`**: Funcionalidad central de tokens no fungibles con operaciones estándar de NFT
-- **`Ownable`**: Patrón de control de acceso para funciones administrativas
-- **`NonFungibleBurnable`**: Extensión que permite quemar tokens
-- **Macros**: `#[only_owner]` para control de acceso declarativo
-
-La macro `#[default_impl]` genera automáticamente las implementaciones estándar, reduciendo el código repetitivo y manteniendo la plena compatibilidad con los estándares NFT.
-
-### Características Mejoradas de Seguridad
-
-Este ejemplo muestra varias características de seguridad integradas en la biblioteca OpenZeppelin:
-
-**Control de Acceso**: La macro `#[only_owner]` asegura que solo el propietario designado pueda realizar acciones administrativas como crear nuevos tokens.
-
-**Generación Secuencial de IDs**: La biblioteca maneja la generación segura de IDs de token, evitando colisiones y asegurando unicidad.
-
-**Valores Predeterminados Seguros**: La biblioteca implementa valores predeterminados seguros para todas las operaciones NFT, incluyendo verificaciones apropiadas de autorización y emisión de eventos.
-
-:::tip
-
-La biblioteca OpenZeppelin Stellar Contracts ha sido auditada y sigue las prácticas recomendadas de la industria. Usar estos componentes preconstruidos reduce el riesgo de vulnerabilidades de seguridad en tus contratos NFT.
-
-:::
-
-## Uso
-
-Usaremos un NFT para rastrear elementos de juego, cada uno con sus propios atributos únicos. Cada vez que uno de estos se deba otorgar a un jugador, será creado y enviado a él. Los jugadores pueden conservar, quemar o intercambiar su token como deseen. Ten en cuenta que cualquier cuenta puede llamar a `award_item` y quizás quieras implementar control de acceso para restringir quién puede crear tokens.
-
-Así podría lucir un contrato para objetos tokenizados:
-
-```rust
-use soroban_sdk::{contract, contractimpl, Address, Env, String};
-use stellar_macros::default_impl;
-use stellar_tokens::non_fungible::{
-    burnable::NonFungibleBurnable,
-    Base, ContractOverrides, NonFungibleToken,
-};
-
-#[contract]
-pub struct GameItem;
-
-#[contractimpl]
-impl GameItem {
-    pub fn __constructor(e: &Env) {
-        Base::set_metadata(
-            e,
-            String::from_str(e, "www.mygame.com"),
-            String::from_str(e, "My Game Items Collection"),
-            String::from_str(e, "MGMC"),
-        );
-    }
-
-    pub fn award_item(e: &Env, to: Address) -> u32 {
-        // access control might be needed
-        Base::sequential_mint(e, &to)
-    }
-}
-
-#[default_impl]
-#[contractimpl]
-impl NonFungibleToken for GameItem {
-    type ContractType = Base;
-}
-
-#[default_impl]
-#[contractimpl]
-impl NonFungibleBurnable for GameItem {}
-```
-
-## Pruebas
-
-El ejemplo de OpenZeppelin incluye pruebas completas que verifican tanto la funcionalidad estándar de NFT como las características adicionales de seguridad.
-
-Los escenarios clave de prueba incluyen:
-
-- **Operaciones de Token**: Pruebas de funciones de creación, transferencia, quema y aprobación
-- **Control de Acceso**: Verificación de que solo el propietario puede realizar acciones administrativas
-- **Generación de ID de Token**: Asegurar que se generen IDs secuenciales correctamente
-- **Autorización**: Confirmar los requisitos adecuados de autenticación para cada función
-- **Casos Límite**: Pruebas de condiciones límite y escenarios de error
-
-Para ejecutar las pruebas:
-
-```sh
-cd examples/nft-sequential-minting
-cargo test
-```
-
-Las pruebas demuestran cómo la biblioteca OpenZeppelin maneja escenarios complejos manteniendo la seguridad y el control de acceso apropiado.
-
-## Crear el Contrato
-
-Para crear el contrato, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-Se debe generar un archivo `.wasm` en el directorio `target`:
-
-```sh
-target/wasm32v1-none/release/nft_sequential_minting.wasm
-```
-
-[`stellar-cli`]: ../../../tools/cli/stellar-cli.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/simple-account.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/simple-account.mdx
deleted file mode 100644
index be2dc34906..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/simple-account.mdx
+++ /dev/null
@@ -1,175 +0,0 @@
----
-title: Cuenta Simple
-sidebar_label: Cuenta Simple
-description: Una cuenta de contrato mínima asegurada por una sola clave pública ed25519.
-sidebar_position: 15
----
-
-<head>
-  <title>Cuenta Simple</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Cuenta de contrato mínima asegurada por una sola clave pública ed25519."
-  />
-  <meta
-    property="og:description"
-    content="Sigue el ejemplo simple de cuenta Soroban para ver cómo se puede implementar __check_auth con una clave."
-  />
-</head>
-
-Este ejemplo implementa la cuenta de contrato más pequeña posible [contract account](../../../learn/glossary.mdx#contract-account): cada llamada `require_auth` delega en una clave pública ed25519. Muestra cómo almacenar esa clave, ejecutar `__check_auth` y mostrar fallos de autorización. Usa esto como base antes de pasar al [Ejemplo de Cuenta Compleja](./complex-account.mdx) para firmas múltiples o aplicación de políticas.
-
-:::danger
-
-Implementar una cuenta de contrato requiere un muy buen entendimiento de la autenticación y autorización y exige pruebas rigurosas y revisión. El ejemplo aquí _no_ es un contrato de cuenta completo: úsalo solo como referencia de la API.
-
-:::
-
-:::caution
-
-Aunque las cuentas de contrato son compatibles con el protocolo Stellar y el SDK Soroban, el soporte completo del cliente (como simulación de transacciones) aún está en desarrollo.
-
-:::
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-
-## Ejecutar el Ejemplo
-
-1. Completa la lista de verificación de [Configuración] para instalar Stellar CLI, el objetivo Rust y las variables de entorno necesarias.
-2. Clona el repositorio `soroban-examples` en la etiqueta `v23.0.0`:
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-3. Si prefieres no instalar nada localmente, lanza el repositorio en [GitHub Codespaces][open-in-github-codespaces] o [Codeanywhere][open-in-code-anywhere].
-
-Ejecuta las pruebas desde el directorio `simple_account`:
-
-```sh
-cd simple_account
-cargo test
-```
-
-Salida esperada:
-
-```
-running 1 test
-test test::test_account ... ok
-```
-
-[setup]: ../getting-started/setup.mdx
-
-## Cómo Funciona
-
-Abre `simple_account/src/lib.rs`. El contrato mantiene un único estado: la clave pública ed25519 del propietario.
-
-### Inicializar al propietario
-
-```rust title="simple_account/src/lib.rs"
-#[contracttype]
-#[derive(Clone)]
-pub enum DataKey {
-    Owner,
-}
-
-#[contractimpl]
-impl SimpleAccount {
-    pub fn init(env: Env, public_key: BytesN<32>) {
-        if env.storage().instance().has(&DataKey::Owner) {
-            panic!("owner is already set");
-        }
-        env.storage().instance().set(&DataKey::Owner, &public_key);
-    }
-```
-
-Llama a `init` una vez para guardar la clave pública del propietario. Llamadas posteriores causan un pánico para evitar reemplazar la clave.
-
-### Implementar `__check_auth`
-
-```rust title="simple_account/src/lib.rs"
-    #[allow(non_snake_case)]
-    pub fn __check_auth(
-        env: Env,
-        signature_payload: BytesN<32>,
-        signature: BytesN<64>,
-        _auth_context: Vec<Context>,
-    ) {
-        let public_key: BytesN<32> = env
-            .storage()
-            .instance()
-            .get(&DataKey::Owner)
-            .unwrap();
-        env.crypto()
-            .ed25519_verify(&public_key, &signature_payload.into(), &signature);
-    }
-}
-```
-
-`__check_auth` se ejecuta cada vez que otro contrato invoca `require_auth` en esta dirección de contrato. La implementación carga la clave almacenada, verifica la firma y provoca un pánico en caso de fallo para que la llamada upstream de `require_auth` sea rechazada. Cuando necesites múltiples claves o lógica de políticas, sigue el mismo patrón mostrado en la Cuenta Compleja.
-
-## Pruebas
-
-Abre `simple_account/src/test.rs`. `__check_auth` no está expuesto como un punto de entrada regular, así que las pruebas llaman a `env.try_invoke_contract_check_auth` para emular el host de Soroban y ejecutar la misma ruta que Soroban usa durante `require_auth`.
-
-```rust title="simple_account/src/test.rs"
-#[test]
-fn test_account() {
-    let env = Env::default();
-    let account_contract = SimpleAccountClient::new(&env, &env.register(SimpleAccount, ()));
-
-    let signer = Keypair::generate(&mut thread_rng());
-    account_contract.init(&signer.public.to_bytes().into_val(&env));
-
-    let payload = BytesN::random(&env);
-    env.try_invoke_contract_check_auth::<Error>(
-        &account_contract.address,
-        &payload,
-        sign(&env, &signer, &payload),
-        &vec![&env],
-    )
-    .unwrap();
-
-    assert!(env
-        .try_invoke_contract_check_auth::<Error>(
-            &account_contract.address,
-            &payload,
-            BytesN::<64>::random(&env).into(),
-            &vec![&env],
-        )
-        .is_err());
-}
-```
-
-`try_invoke_contract_check_auth` simula la ruta del host para `require_auth`, permitiendo probar tanto el caso de éxito como un caso de fallo con bytes aleatorios.
-
-Sigue la misma estructura para cualquier cuenta:
-
-- crea un par de claves y guarda el firmante esperado (por ejemplo, con `init`)
-- llama a `try_invoke_contract_check_auth` con una firma válida y verifica que tenga éxito
-- llámalo de nuevo con una firma o carga inválida y verifica que falle
-
-## Compilar el Contrato
-
-Para producir el ejecutable Wasm, ejecuta:
-
-```sh
-stellar contract build
-# add --package soroban-simple-account-contract when building inside the soroban-examples workspace
-```
-
-El archivo compilado aparece en `target/wasm32v1-none/release/simple_account.wasm` (el nombre exacto depende del nombre de tu crate).
-
-## Lecturas Adicionales
-
-- [Ejemplo de cuenta compleja] – añade soporte para multisig y límites de gasto.
-- [Contrato de firma BLS](./bls-signature.mdx) – demuestra esquemas de firma personalizados dentro de `__check_auth`.
-
-[Ejemplo de cuenta compleja]: ./complex-account.mdx
-[ejemplo de cuenta simple]: https://github.com/stellar/soroban-examples/tree/v23.0.0/simple_account
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/single-offer-sale.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/single-offer-sale.mdx
deleted file mode 100644
index 3c061e41ab..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/single-offer-sale.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Venta de oferta única
-description: Haz una oferta permanente para vender un token a cambio de otro token.
-sidebar_position: 120
----
-
-<head>
-  <title>
-    {`Haz una oferta permanente para vender un token a cambio de otro token.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Haz una oferta permanente para vender un token a cambio de otro token."
-  />
-  <meta
-    property="og:description"
-    content="Escribe un contrato inteligente que permita a un vendedor establecer una oferta para vender un token por otro token a varios compradores."
-  />
-</head>
-
-El [ejemplo de venta de oferta única] demuestra cómo escribir un contrato que permite a un vendedor establecer una oferta para vender el token A por el token B a varios compradores. Los comentarios en el [código fuente] explican cómo se debe utilizar el contrato.
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de venta de oferta única]: https://github.com/stellar/soroban-examples/tree/v23.0.0/single_offer
-[código fuente]: https://github.com/stellar/soroban-examples/tree/v23.0.0/single_offer/src/lib.rs
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/storage.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/storage.mdx
deleted file mode 100644
index e2c3f93f50..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/storage.mdx
+++ /dev/null
@@ -1,262 +0,0 @@
----
-title: Almacenamiento
-description: Incrementar un contador y almacenar el valor incrementado
-sidebar_position: 9
----
-
-<head>
-  <title>Incrementar un contador y almacenar el valor incrementado.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Incrementar un contador y almacenar el valor incrementado."
-  />
-  <meta
-    property="og:description"
-    content="Usar almacenamiento para retener el valor de un contador en un contrato inteligente incrementador"
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de incremento] demuestra cómo llamar a un contrato desde otro contrato.
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de incremento]: https://github.com/stellar/soroban-examples/tree/v23.0.0/increment
-
-## Ejecutar el ejemplo
-
-Primero completa el proceso de [Configuración] para tener tu entorno de desarrollo configurado, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-[configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `increment` y usa `cargo test`.
-
-```sh
-cd increment
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 1 test
-test test::test ... ok
-```
-
-## Código
-
-```rust title="increment/src/lib.rs"
-const COUNTER: Symbol = symbol_short!("COUNTER");
-
-#[contract]
-pub struct IncrementContract;
-
-#[contractimpl]
-impl IncrementContract {
-    pub fn increment(env: Env) -> u32 {
-        let mut count: u32 = env.storage().instance().get(&COUNTER).unwrap_or(0);
-        log!(&env, "count: {}", count);
-
-        count += 1;
-        env.storage().instance().set(&COUNTER, &count);
-        env.storage().instance().extend_ttl(50, 100);
-
-        count
-    }
-}
-```
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/increment
-
-## Cómo Funciona
-
-Este contrato obtendrá un valor de contador del almacenamiento (o usará el valor 0 si no se ha almacenado ningún valor todavía), y aumentará este contador cada vez que se llame.
-
-Abre el archivo [`increment/src/lib.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/increment/src/lib.rs) o revisa el código anterior para seguir junto a él.
-
-### Clave de Datos del Contrato
-
-Los datos del contrato están asociados a una clave, que se puede usar en un momento posterior para buscar el valor.
-
-```rust
-const COUNTER: Symbol = symbol_short!("COUNTER");
-```
-
-`Symbol` es un tipo de cadena corto (de hasta 32 caracteres de longitud) con un espacio de caracteres limitado (solo se permiten caracteres `a-zA-Z0-9_`). Los identificadores como los nombres de las funciones del contrato y las claves de los datos del contrato están representados por `Symbols`.
-
-El macro `symbol_short!()` es una forma conveniente de pre-calcular símbolos cortos de hasta 9 caracteres de longitud en tiempo de compilación usando `Symbol::short`. Genera una constante de tiempo de compilación que adhiere al conjunto de caracteres válidos de letras (a-zA-Z), números (0-9) y guiones bajos (\_). Si un símbolo excede el límite de 9 caracteres, se debería utilizar `Symbol::new` para crear símbolos en tiempo de ejecución.
-
-### Acceso a los Datos del Contrato
-
-```rust
-let mut count: u32 = env
-    .storage()
-    .instance()
-    .get(&COUNTER)
-    .unwrap_or(0); // If no value set, assume 0.
-```
-
-La función `env.storage()` se utiliza para acceder y actualizar los datos del contrato. El contrato que se está ejecutando es el único que puede consultar o modificar los datos del contrato que ha almacenado. Los datos almacenados son visibles en el ledger dondequiera que el ledger sea visible, pero los contratos que se ejecutan dentro del entorno Soroban están restringidos a sus propios datos.
-
-La función `get(`) obtiene el valor actual asociado con la clave del contador.
-
-Si no hay ningún valor almacenado actualmente, se devolverá el valor dado a `unwrap_or(...)` en su lugar.
-
-Los valores almacenados como datos del contrato y recuperados son transmitidos desde [el entorno] y se expanden al tipo especificado. En este caso, un `u32`. Si el valor puede ser expandido, el tipo devuelto será un `u32`. De lo contrario, si un desarrollador lo convierte a ser algún otro tipo, se produciría un pánico en el unwrap.
-
-[el entorno]: ../../../learn/fundamentals/contract-development/environment-concepts.mdx
-
-```rust
-env.storage()
-    .instance()
-    .set(&COUNTER, &count);
-```
-
-La función `set()` almacena el nuevo valor de conteo asociado con la clave, reemplazando el valor existente.
-
-### Gestionar TTL de Datos del Contrato con `extend_ttl()`
-
-```rust
-env.storage().instance().extend_ttl(50, 100);
-```
-
-Todos los datos del contrato tienen un Tiempo de Vida (TTL), medido en ledgers, que debe ser extendido periódicamente. Si el TTL de una entrada no se extiende periódicamente, la entrada finalmente se convertirá en "archivada" Puedes aprender más sobre esto en el documento [Archivado de Estado](../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
-
-Por ahora, es bueno saber que hay tres tipos de almacenamiento: `Persistent`, `Temporary` y `Instance`. Este contrato solo utiliza almacenamiento `Instance`: `env.storage().instance()`. Cada vez que se incrementa el contador, el TTL de este almacenamiento se extiende por 100 [ledgers](../../../learn/fundamentals/stellar-data-structures/ledgers.mdx), o alrededor de 500 segundos.
-
-## Pruebas
-
-Abre el archivo [`increment/src/test.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/increment/src/test.rs) para seguir junto a él.
-
-```rust title="increment/src/test.rs"
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.increment(), 1);
-    assert_eq!(client.increment(), 2);
-    assert_eq!(client.increment(), 3);
-}
-```
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno Soroban en el que se ejecutará el contrato.
-
-```rust
-let env = Env::default();
-```
-
-El contrato se registra con el entorno usando el tipo de contrato.
-
-```rust
-let contract_id = env.register(IncrementContract, ());
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente se llamará igual que el tipo de contrato con `Client` agregado.
-
-```rust
-let client = IncrementContractClient::new(&env, &contract_id);
-```
-
-La prueba verifica que el resultado devuelto sea como esperamos.
-
-```rust
-assert_eq!(client.increment(), 1);
-assert_eq!(client.increment(), 2);
-assert_eq!(client.increment(), 3);
-```
-
-## Construir los Contratos
-
-Para crear el contrato en un archivo `.wasm`, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-El archivo `.wasm` debería encontrarse en el directorio `target` del contrato después de crear el contrato:
-
-```
-target/wasm32v1-none/release/soroban_increment_contract.wasm
-```
-
-## Ejecutar el Contrato
-
-Si tienes [`stellar-cli`] instalado, puedes desplegar el contrato y invocar la función del contrato.
-
-### Desplegar
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/soroban_increment_contract.wasm \
-    --id a
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract deploy `
-    --wasm target/wasm32v1-none/release/soroban_increment_contract.wasm `
-    --id a
-```
-
-</TabItem>
-</Tabs>
-
-### Invocar
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --wasm target/wasm32v1-none/release/soroban_events_contract.wasm \
-    --id 1 \
-    -- \
-    increment
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --wasm target/wasm32v1-none/release/soroban_events_contract.wasm `
-    --id 1 `
-    -- `
-    increment
-```
-
-</TabItem>
-</Tabs>
-
-### Resultado
-
-La siguiente salida debería ocurrir la primera vez que se use el código anterior.
-
-```
-1
-```
-
-El valor se incrementará cada vez que se invoque la función del contrato.
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/timelock.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/timelock.mdx
deleted file mode 100644
index fe000f9acc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/timelock.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Tiempo de bloqueo
-description: Bloquear un token para que sea reclamado por otro usuario bajo condiciones establecidas.
-sidebar_position: 110
----
-
-<head>
-  <title>
-    {`Bloquear un token para que sea reclamado por otro usuario bajo condiciones establecidas`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Escribir un tiempo de bloqueo que implemente un saldo reclamable."
-  />
-  <meta
-    property="og:description"
-    content="Escribir un tiempo de bloqueo que implemente una característica de saldo reclamable simplificada que acepte un depósito de una cantidad de un token y permita a otros usuarios reclamarlo."
-  />
-</head>
-
-El [ejemplo de tiempo de bloqueo] demuestra cómo escribir un tiempo de bloqueo e implementa un saldo reclamable muy simplificado similar a la característica de [saldo reclamable] disponible en Stellar.
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-El contrato acepta depósitos de una cantidad de un token y permite a otros usuarios reclamarlo antes o después de un punto en el tiempo.
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de tiempo de bloqueo]: https://github.com/stellar/soroban-examples/tree/v23.0.0/timelock
-[saldo reclamable]: ../../guides/transactions/claimable-balances.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/tokens.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/tokens.mdx
deleted file mode 100644
index dfc8903043..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/tokens.mdx
+++ /dev/null
@@ -1,963 +0,0 @@
----
-title: Tokens
-description: Escribir un contrato de token compatible con CAP-46-6.
-sidebar_position: 140
----
-
-<head>
-  <title>Escribir un contrato de token compatible con CAP-46-6</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Escribir un contrato de token compatible con CAP-46-6"
-  />
-  <meta
-    property="og:description"
-    content="Utiliza la Interfaz de Token para construir un token de contrato inteligente que tenga una interfaz uniforme y predecible para pagos, transferencias de saldo, consultas de saldo, y más."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de token] demuestra cómo escribir un contrato de token que implementa la [Interfaz de Token].
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de token]: https://github.com/stellar/soroban-examples/tree/v23.0.0/token
-[interfaz de token]: ../../../tokens/token-interface.mdx
-
-:::tip[Whisk Cambios]
-
-Con el lanzamiento de Whisk, Protocolo 23, la [interfaz de token] ha sufrido algunos cambios para incorporar el tipo `MuxedAddress` en la función `transfer`. Consulta la [documentación del SDK de Rust](https://docs.rs/soroban-token-sdk/latest/soroban_token_sdk/_migrating/v23_token_transfer/index.html) para más detalles.
-
-:::
-
-## Ejecutar el Ejemplo
-
-Primero realiza el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona la etiqueta `v23.0.0` del repositorio `soroban-examples`:
-
-```sh
-git clone -b v23.0.0 https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo, navega al directorio `hello_world`, y usa `cargo test`.
-
-```sh
-cd token
-cargo test
-```
-
-Deberías ver la salida:
-
-```
-running 6 tests
-test test::decimal_is_over_eighteen - should panic ... ok
-test test::test_zero_allowance ... ok
-test test::transfer_insufficient_balance - should panic ... ok
-test test::transfer_from_insufficient_allowance - should panic ... ok
-test test::test_burn ... ok
-test test::test ... ok
-```
-
-[configuración]: ../getting-started/setup.mdx
-
-## Código
-
-:::note
-
-El código fuente para este [ejemplo de token] está dividido en varios módulos más pequeños. Este es un patrón de diseño común para contratos inteligentes más complejos.
-
-:::
-
-<Tabs>
-<TabItem value="lib" default>
-
-```rust title="token/src/lib.rs"
-#![no_std]
-
-mod admin;
-mod allowance;
-mod balance;
-mod contract;
-mod metadata;
-mod storage_types;
-mod test;
-
-pub use crate::contract::TokenClient;
-```
-
-</TabItem>
-<TabItem value="admin">
-
-```rust title="token/src/admin.rs"
-use soroban_sdk::{Address, Env};
-
-use crate::storage_types::DataKey;
-
-pub fn read_administrator(e: &Env) -> Address {
-    let key = DataKey::Admin;
-    e.storage().instance().get(&key).unwrap()
-}
-
-pub fn write_administrator(e: &Env, id: &Address) {
-    let key = DataKey::Admin;
-    e.storage().instance().set(&key, id);
-}
-```
-
-</TabItem>
-<TabItem value="allowance">
-
-```rust title="token/src/allowance.rs"
-use crate::storage_types::{AllowanceDataKey, AllowanceValue, DataKey};
-use soroban_sdk::{Address, Env};
-
-pub fn read_allowance(e: &Env, from: Address, spender: Address) -> AllowanceValue {
-    let key = DataKey::Allowance(AllowanceDataKey { from, spender });
-    if let Some(allowance) = e.storage().temporary().get::<_, AllowanceValue>(&key) {
-        if allowance.expiration_ledger < e.ledger().sequence() {
-            AllowanceValue {
-                amount: 0,
-                expiration_ledger: allowance.expiration_ledger,
-            }
-        } else {
-            allowance
-        }
-    } else {
-        AllowanceValue {
-            amount: 0,
-            expiration_ledger: 0,
-        }
-    }
-}
-
-pub fn write_allowance(
-    e: &Env,
-    from: Address,
-    spender: Address,
-    amount: i128,
-    expiration_ledger: u32,
-) {
-    let allowance = AllowanceValue {
-        amount,
-        expiration_ledger,
-    };
-
-    if amount > 0 && expiration_ledger < e.ledger().sequence() {
-        panic!("expiration_ledger is less than ledger seq when amount > 0")
-    }
-
-    let key = DataKey::Allowance(AllowanceDataKey { from, spender });
-    e.storage().temporary().set(&key.clone(), &allowance);
-
-    if amount > 0 {
-        let live_for = expiration_ledger
-            .checked_sub(e.ledger().sequence())
-            .unwrap();
-
-        e.storage().temporary().extend_ttl(&key, live_for, live_for)
-    }
-}
-
-pub fn spend_allowance(e: &Env, from: Address, spender: Address, amount: i128) {
-    let allowance = read_allowance(e, from.clone(), spender.clone());
-    if allowance.amount < amount {
-        panic!("insufficient allowance");
-    }
-    if amount > 0 {
-        write_allowance(
-            e,
-            from,
-            spender,
-            allowance.amount - amount,
-            allowance.expiration_ledger,
-        );
-    }
-}
-```
-
-</TabItem>
-<TabItem value="balance">
-
-```rust title="token/src/balance.rs"
-use crate::storage_types::{DataKey, BALANCE_BUMP_AMOUNT, BALANCE_LIFETIME_THRESHOLD};
-use soroban_sdk::{Address, Env};
-
-pub fn read_balance(e: &Env, addr: Address) -> i128 {
-    let key = DataKey::Balance(addr);
-    if let Some(balance) = e.storage().persistent().get::<DataKey, i128>(&key) {
-        e.storage()
-            .persistent()
-            .extend_ttl(&key, BALANCE_LIFETIME_THRESHOLD, BALANCE_BUMP_AMOUNT);
-        balance
-    } else {
-        0
-    }
-}
-
-fn write_balance(e: &Env, addr: Address, amount: i128) {
-    let key = DataKey::Balance(addr);
-    e.storage().persistent().set(&key, &amount);
-    e.storage()
-        .persistent()
-        .extend_ttl(&key, BALANCE_LIFETIME_THRESHOLD, BALANCE_BUMP_AMOUNT);
-}
-
-pub fn receive_balance(e: &Env, addr: Address, amount: i128) {
-    let balance = read_balance(e, addr.clone());
-    write_balance(e, addr, balance + amount);
-}
-
-pub fn spend_balance(e: &Env, addr: Address, amount: i128) {
-    let balance = read_balance(e, addr.clone());
-    if balance < amount {
-        panic!("insufficient balance");
-    }
-    write_balance(e, addr, balance - amount);
-}
-```
-
-</TabItem>
-<TabItem value="contract">
-
-```rust title="token/src/contract.rs"
-//! This contract demonstrates a sample implementation of the Soroban token
-//! interface.
-use crate::admin::{read_administrator, write_administrator};
-use crate::allowance::{read_allowance, spend_allowance, write_allowance};
-use crate::balance::{read_balance, receive_balance, spend_balance};
-use crate::metadata::{read_decimal, read_name, read_symbol, write_metadata};
-#[cfg(test)]
-use crate::storage_types::{AllowanceDataKey, AllowanceValue, DataKey};
-use crate::storage_types::{INSTANCE_BUMP_AMOUNT, INSTANCE_LIFETIME_THRESHOLD};
-use soroban_sdk::{
-    contract, contractevent, contractimpl, token::TokenInterface, Address, Env, MuxedAddress,
-    String,
-};
-use soroban_token_sdk::events;
-use soroban_token_sdk::metadata::TokenMetadata;
-
-fn check_nonnegative_amount(amount: i128) {
-    if amount < 0 {
-        panic!("negative amount is not allowed: {}", amount)
-    }
-}
-
-#[contract]
-pub struct Token;
-
-// SetAdmin is not a standardized token event, so we just define a custom event
-// for our token.
-#[contractevent(data_format = "single-value")]
-pub struct SetAdmin {
-    #[topic]
-    admin: Address,
-    new_admin: Address,
-}
-
-#[contractimpl]
-impl Token {
-    pub fn __constructor(e: Env, admin: Address, decimal: u32, name: String, symbol: String) {
-        if decimal > 18 {
-            panic!("Decimal must not be greater than 18");
-        }
-        write_administrator(&e, &admin);
-        write_metadata(
-            &e,
-            TokenMetadata {
-                decimal,
-                name,
-                symbol,
-            },
-        )
-    }
-
-    pub fn mint(e: Env, to: Address, amount: i128) {
-        check_nonnegative_amount(amount);
-        let admin = read_administrator(&e);
-        admin.require_auth();
-
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-
-        receive_balance(&e, to.clone(), amount);
-        events::MintWithAmountOnly { to, amount }.publish(&e);
-    }
-
-    pub fn set_admin(e: Env, new_admin: Address) {
-        let admin = read_administrator(&e);
-        admin.require_auth();
-
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-
-        write_administrator(&e, &new_admin);
-        SetAdmin { admin, new_admin }.publish(&e);
-    }
-
-    #[cfg(test)]
-    pub fn get_allowance(e: Env, from: Address, spender: Address) -> Option<AllowanceValue> {
-        let key = DataKey::Allowance(AllowanceDataKey { from, spender });
-        let allowance = e.storage().temporary().get::<_, AllowanceValue>(&key);
-        allowance
-    }
-}
-
-#[contractimpl]
-impl TokenInterface for Token {
-    fn allowance(e: Env, from: Address, spender: Address) -> i128 {
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-        read_allowance(&e, from, spender).amount
-    }
-
-    fn approve(e: Env, from: Address, spender: Address, amount: i128, expiration_ledger: u32) {
-        from.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-
-        write_allowance(&e, from.clone(), spender.clone(), amount, expiration_ledger);
-        events::Approve {
-            from,
-            spender,
-            amount,
-            expiration_ledger,
-        }
-        .publish(&e);
-    }
-
-    fn balance(e: Env, id: Address) -> i128 {
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-        read_balance(&e, id)
-    }
-
-    fn transfer(e: Env, from: Address, to_muxed: MuxedAddress, amount: i128) {
-        from.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-
-        spend_balance(&e, from.clone(), amount);
-        let to: Address = to_muxed.address();
-        receive_balance(&e, to.clone(), amount);
-        events::Transfer {
-            from,
-            to,
-            to_muxed_id: to_muxed.id(),
-            amount,
-        }
-        .publish(&e);
-    }
-
-    fn transfer_from(e: Env, spender: Address, from: Address, to: Address, amount: i128) {
-        spender.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-
-        spend_allowance(&e, from.clone(), spender, amount);
-        spend_balance(&e, from.clone(), amount);
-        receive_balance(&e, to.clone(), amount);
-        events::Transfer {
-            from,
-            to,
-            // `transfer_from` does not support muxed destination.
-            to_muxed_id: None,
-            amount,
-        }
-        .publish(&e);
-    }
-
-    fn burn(e: Env, from: Address, amount: i128) {
-        from.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-
-        spend_balance(&e, from.clone(), amount);
-        events::Burn { from, amount }.publish(&e);
-    }
-
-    fn burn_from(e: Env, spender: Address, from: Address, amount: i128) {
-        spender.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage()
-            .instance()
-            .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-
-        spend_allowance(&e, from.clone(), spender, amount);
-        spend_balance(&e, from.clone(), amount);
-        events::Burn { from, amount }.publish(&e);
-    }
-
-    fn decimals(e: Env) -> u32 {
-        read_decimal(&e)
-    }
-
-    fn name(e: Env) -> String {
-        read_name(&e)
-    }
-
-    fn symbol(e: Env) -> String {
-        read_symbol(&e)
-    }
-}
-```
-
-</TabItem>
-<TabItem value="metadata">
-
-```rust title="token/src/metadata.rs"
-use soroban_sdk::{Env, String};
-use soroban_token_sdk::{metadata::TokenMetadata, TokenUtils};
-
-pub fn read_decimal(e: &Env) -> u32 {
-    let util = TokenUtils::new(e);
-    util.metadata().get_metadata().decimal
-}
-
-pub fn read_name(e: &Env) -> String {
-    let util = TokenUtils::new(e);
-    util.metadata().get_metadata().name
-}
-
-pub fn read_symbol(e: &Env) -> String {
-    let util = TokenUtils::new(e);
-    util.metadata().get_metadata().symbol
-}
-
-pub fn write_metadata(e: &Env, metadata: TokenMetadata) {
-    let util = TokenUtils::new(e);
-    util.metadata().set_metadata(&metadata);
-}
-```
-
-</TabItem>
-<TabItem value="storage_types">
-
-```rust title="token/src/storage_types.rs"
-use soroban_sdk::{contracttype, Address};
-
-pub(crate) const DAY_IN_LEDGERS: u32 = 17280;
-pub(crate) const INSTANCE_BUMP_AMOUNT: u32 = 7 * DAY_IN_LEDGERS;
-pub(crate) const INSTANCE_LIFETIME_THRESHOLD: u32 = INSTANCE_BUMP_AMOUNT - DAY_IN_LEDGERS;
-
-pub(crate) const BALANCE_BUMP_AMOUNT: u32 = 30 * DAY_IN_LEDGERS;
-pub(crate) const BALANCE_LIFETIME_THRESHOLD: u32 = BALANCE_BUMP_AMOUNT - DAY_IN_LEDGERS;
-
-#[derive(Clone)]
-#[contracttype]
-pub struct AllowanceDataKey {
-    pub from: Address,
-    pub spender: Address,
-}
-
-#[contracttype]
-pub struct AllowanceValue {
-    pub amount: i128,
-    pub expiration_ledger: u32,
-}
-
-#[derive(Clone)]
-#[contracttype]
-pub enum DataKey {
-    Allowance(AllowanceDataKey),
-    Balance(Address),
-    State(Address),
-    Admin,
-}
-```
-
-</TabItem>
-</Tabs>
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/token
-
-## Cómo Funciona
-
-Los tokens creados en una plataforma de contrato inteligente pueden tomar muchas formas diferentes, incluir una variedad de funcionalidades diferentes, y satisfacer necesidades o casos de uso muy diferentes. Si bien cada token puede cumplir con un nicho único, hay algunas características "normales" que casi todos los tokens necesitarán utilizar (por ejemplo, pagos, transferencias, consultas de saldo, etc.). Con el fin de minimizar la repetición y agilizar las implementaciones de tokens, Soroban implementa la [Interfaz de Token], que proporciona una interfaz uniforme y predecible para desarrolladores y usuarios.
-
-Crear un contrato compatible con Soroban a partir de un activo Stellar existente es muy fácil, requiere desplegar el [Contrato de Activo Stellar] incorporado.
-
-Este contrato de ejemplo, sin embargo, demuestra cómo podría construirse un token de contrato inteligente que no aprovecha el Contrato de Activo Stellar, pero que aún satisface la Interfaz de Token de uso común para maximizar la interoperabilidad.
-
-[contrato de activo stellar]: ../../../tokens/stellar-asset-contract.mdx
-
-### Separación de Funcionalidad
-
-Probablemente hayas notado que este contrato de ejemplo está dividido en módulos discretos, cada uno responsable de un conjunto silo de funcionalidades. Esta práctica común ayuda a organizar el código y hacerlo más mantenible.
-
-Por ejemplo, la mayor parte de la lógica del token existe en el módulo `contract.rs`. Funciones como `mint`, `burn`, `transfer`, etc. están escritas y programadas en ese archivo. La Interfaz de Token describe cómo algunas de estas funciones deberían emitir eventos cuando ocurren. Sin embargo, mantener toda esa lógica de emisión de eventos agrupada con el resto del código del contrato podría dificultar el seguimiento de lo que está sucediendo en el código, y esa confusión podría finalmente llevar a errores.
-
-En cambio, tenemos un módulo separado `soroban_token_sdk::events` que elimina todas las complicaciones de emitir eventos cuando se ejecutan otras funciones. Aquí está el evento emitido cuando se acuña un token:
-
-```rust
-events::MintWithAmountOnly { to, amount }.publish(&e);
-```
-
-Aunque este es un ejemplo simple, construir el contrato de esta manera deja muy claro al desarrollador lo que está sucediendo y dónde. Esta función se utiliza luego por el módulo `contract.rs` cada vez que se invoca la función `mint`:
-
-```rust
-// earlier in `contract.rs`
-use soroban_token_sdk::events;
-
-pub fn mint(e: Env, to: Address, amount: i128) {
-    check_nonnegative_amount(amount);
-    let admin = read_administrator(&e);
-    admin.require_auth();
-
-    e.storage()
-        .instance()
-        .extend_ttl(INSTANCE_LIFETIME_THRESHOLD, INSTANCE_BUMP_AMOUNT);
-
-    receive_balance(&e, to.clone(), amount);
-    // highlight-next-line
-    events::MintWithAmountOnly { to, amount }.publish(&e);
-}
-```
-
-Esta misma convención se utiliza para separar del código del "contrato principal" la metadata para el token, las definiciones de tipos de almacenamiento, etc.
-
-### Interfaz Estandarizada, Comportamiento Personalizado
-
-Este contrato de ejemplo sigue la [Interfaz de Token] estandarizada, implementando todas las mismas funciones que el [Contrato de Activo Stellar] (SAC). Esto le da a las billeteras, usuarios, desarrolladores, etc. una interfaz predecible para interactuar con el token. Aún cuando estamos implementando la misma _interfaz_ de funciones, eso no significa que tengamos que implementar el mismo _comportamiento_ dentro de esas funciones. Aunque este contrato de ejemplo no modifica realmente ninguna de las funciones que estarían presentes en una instancia desplegada del SAC, esa posibilidad sigue abierta para el desarrollador del contrato.
-
-Por ejemplo, quizás tengas un proyecto NFT, y el artista quiere que se pague una pequeña regalía cada vez que su token cambia de manos:
-
-```rust
-// This is mainly the `transfer` function from `token/src/contract.rs`
-fn transfer(e: Env, from: Address, to_muxed: MuxedAddress, amount: i128) {
-    from.require_auth();
-
-    check_nonnegative_amount(amount);
-    spend_balance(&e, from.clone(), amount);
-    let to: Address = to_muxed.address();
-
-    // highlight-start
-    // We calculate some new amounts for payment and royalty
-    let payment = (amount * 997) / 1000;
-    let royalty = amount - payment
-    let artist = read_artist(&e);
-    receive_balance(&e, artist.clone(), royalty);
-    events::TransferWithAmountOnly {
-        to: artist.clone(),
-        amount: royalty,
-    }.publish(&e);
-    // highlight-end
-    receive_balance(&e, to.clone(), payment);
-    events::Transfer {
-        from,
-        to,
-        to_muxed_id: to_muxed.id(),
-        amount,
-    }
-    .publish(&e);
-}
-```
-
-La interfaz `transfer` sigue en uso, y sigue siendo la misma que otros tokens, pero hemos personalizado el comportamiento para abordar una necesidad específica. Otro caso de uso podría ser un token controlado estrictamente que requiere autenticación de un administrador antes de que cualquier función de `transfer`, `allowance`, etc. pueda ser invocada.
-
-:::tip
-
-Por supuesto, querrás que tu token se comporte de manera _intuitiva_ y _transparente_. Si un usuario está invocando un `transfer`, esperará que los tokens se transfieran. Si un emisor de activos necesita invocar un `clawback`, probablemente _requerirá_ que se produzca el comportamiento adecuado.
-
-:::
-
-## Pruebas
-
-Abre el archivo [`token/src/test.rs`](https://github.com/stellar/soroban-examples/tree/v23.0.0/token/src/test.rs) para seguir el ejemplo.
-
-```rust title="token/src/test.rs"
-#![cfg(test)]
-extern crate std;
-
-use crate::{contract::Token, TokenClient};
-use soroban_sdk::{
-    symbol_short,
-    testutils::{Address as _, AuthorizedFunction, AuthorizedInvocation},
-    Address, Env, FromVal, IntoVal, String, Symbol,
-};
-
-fn create_token<'a>(e: &Env, admin: &Address) -> TokenClient<'a> {
-    let token_contract = e.register(
-        Token,
-        (
-            admin,
-            7_u32,
-            String::from_val(e, &"name"),
-            String::from_val(e, &"symbol"),
-        ),
-    );
-    TokenClient::new(e, &token_contract)
-}
-
-#[test]
-fn test() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    let admin1 = Address::generate(&e);
-    let admin2 = Address::generate(&e);
-    let user1 = Address::generate(&e);
-    let user2 = Address::generate(&e);
-    let user3 = Address::generate(&e);
-    let token = create_token(&e, &admin1);
-
-    token.mint(&user1, &1000);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            admin1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    token.address.clone(),
-                    symbol_short!("mint"),
-                    (&user1, 1000_i128).into_val(&e),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-    assert_eq!(token.balance(&user1), 1000);
-
-    token.approve(&user2, &user3, &500, &200);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user2.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    token.address.clone(),
-                    symbol_short!("approve"),
-                    (&user2, &user3, 500_i128, 200_u32).into_val(&e),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-    assert_eq!(token.allowance(&user2, &user3), 500);
-
-    token.transfer(&user1, &user2, &600);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    token.address.clone(),
-                    symbol_short!("transfer"),
-                    (&user1, &user2, 600_i128).into_val(&e),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-    assert_eq!(token.balance(&user1), 400);
-    assert_eq!(token.balance(&user2), 600);
-
-    token.transfer_from(&user3, &user2, &user1, &400);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user3.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    token.address.clone(),
-                    Symbol::new(&e, "transfer_from"),
-                    (&user3, &user2, &user1, 400_i128).into_val(&e),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-    assert_eq!(token.balance(&user1), 800);
-    assert_eq!(token.balance(&user2), 200);
-
-    token.transfer(&user1, &user3, &300);
-    assert_eq!(token.balance(&user1), 500);
-    assert_eq!(token.balance(&user3), 300);
-
-    token.set_admin(&admin2);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            admin1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    token.address.clone(),
-                    symbol_short!("set_admin"),
-                    (&admin2,).into_val(&e),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-
-    // Increase to 500
-    token.approve(&user2, &user3, &500, &200);
-    assert_eq!(token.allowance(&user2, &user3), 500);
-    token.approve(&user2, &user3, &0, &200);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user2.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    token.address.clone(),
-                    symbol_short!("approve"),
-                    (&user2, &user3, 0_i128, 200_u32).into_val(&e),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-    assert_eq!(token.allowance(&user2, &user3), 0);
-}
-
-#[test]
-fn test_burn() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    let admin = Address::generate(&e);
-    let user1 = Address::generate(&e);
-    let user2 = Address::generate(&e);
-    let token = create_token(&e, &admin);
-
-    token.mint(&user1, &1000);
-    assert_eq!(token.balance(&user1), 1000);
-
-    token.approve(&user1, &user2, &500, &200);
-    assert_eq!(token.allowance(&user1, &user2), 500);
-
-    token.burn_from(&user2, &user1, &500);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user2.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    token.address.clone(),
-                    symbol_short!("burn_from"),
-                    (&user2, &user1, 500_i128).into_val(&e),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-
-    assert_eq!(token.allowance(&user1, &user2), 0);
-    assert_eq!(token.balance(&user1), 500);
-    assert_eq!(token.balance(&user2), 0);
-
-    token.burn(&user1, &500);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    token.address.clone(),
-                    symbol_short!("burn"),
-                    (&user1, 500_i128).into_val(&e),
-                )),
-                sub_invocations: std::vec![]
-            }
-        )]
-    );
-
-    assert_eq!(token.balance(&user1), 0);
-    assert_eq!(token.balance(&user2), 0);
-}
-
-#[test]
-#[should_panic(expected = "insufficient balance")]
-fn transfer_insufficient_balance() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    let admin = Address::generate(&e);
-    let user1 = Address::generate(&e);
-    let user2 = Address::generate(&e);
-    let token = create_token(&e, &admin);
-
-    token.mint(&user1, &1000);
-    assert_eq!(token.balance(&user1), 1000);
-
-    token.transfer(&user1, &user2, &1001);
-}
-
-#[test]
-#[should_panic(expected = "insufficient allowance")]
-fn transfer_from_insufficient_allowance() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    let admin = Address::generate(&e);
-    let user1 = Address::generate(&e);
-    let user2 = Address::generate(&e);
-    let user3 = Address::generate(&e);
-    let token = create_token(&e, &admin);
-
-    token.mint(&user1, &1000);
-    assert_eq!(token.balance(&user1), 1000);
-
-    token.approve(&user1, &user3, &100, &200);
-    assert_eq!(token.allowance(&user1, &user3), 100);
-
-    token.transfer_from(&user3, &user1, &user2, &101);
-}
-
-#[test]
-#[should_panic(expected = "Decimal must not be greater than 18")]
-fn decimal_is_over_eighteen() {
-    let e = Env::default();
-    let admin = Address::generate(&e);
-    let _ = TokenClient::new(
-        &e,
-        &e.register(
-            Token,
-            (
-                admin,
-                19_u32,
-                String::from_val(&e, &"name"),
-                String::from_val(&e, &"symbol"),
-            ),
-        ),
-    );
-}
-
-#[test]
-fn test_zero_allowance() {
-    // Here we test that transfer_from with a 0 amount does not create an empty allowance
-    let e = Env::default();
-    e.mock_all_auths();
-
-    let admin = Address::generate(&e);
-    let spender = Address::generate(&e);
-    let from = Address::generate(&e);
-    let token = create_token(&e, &admin);
-
-    token.transfer_from(&spender, &from, &spender, &0);
-    assert!(token.get_allowance(&from, &spender).is_none());
-}
-```
-
-El ejemplo de token implementa ocho pruebas diferentes para cubrir una amplia gama de posibles comportamientos y problemas. Sin embargo, todas las pruebas comienzan con algunas piezas comunes. En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno Soroban en el que se ejecutará el contrato.
-
-```rust
-let e = Env::default();
-```
-
-Simulamos verificaciones de autenticación en las pruebas, lo que permite que las pruebas continúen como si todos los usuarios/direcciones/contratos/etc. se hubieran autenticado con éxito.
-
-```rust
-e.mock_all_auths();
-```
-
-También estamos usando una función `create_token` para facilitar la repetición de tener que registrar nuestro contrato de token. El cliente `token` resultante se utiliza para invocar el contrato durante cada prueba.
-
-```rust
-// It is defined at the top of the file...
-fn create_token<'a>(e: &Env, admin: &Address) -> TokenClient<'a> {
-    let token_contract = e.register(
-        Token,
-        (
-            admin,
-            7_u32,
-            String::from_val(e, &"name"),
-            String::from_val(e, &"symbol"),
-        ),
-    );
-    TokenClient::new(e, &token_contract)
-}
-
-// ... and it is used inside each test
-let token = create_token(&e, &admin);
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que ha sido anotado con el atributo `#[contractimpl]` tendrán una función correspondiente en el tipo de cliente generado de la prueba. El tipo de cliente se llamará igual que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato, el tipo de contrato se llama `Token`, y el tipo de cliente se llama `TokenClient`.
-
-Las seis pruebas creadas para este contrato de ejemplo prueban una variedad de condiciones posibles y aseguran que el contrato responda adecuadamente a cada una:
-
-- **`test()`** - Esta función hace uso de una variedad de las funciones de token incorporadas para probar la forma "predecible" en que un activo podría ser interactuado por un usuario, así como un administrador.
-- **`test_burn()`** - Esta función asegura que una invocación de `burn()` disminuye el saldo de un usuario, y que una invocación de `burn_from()` disminuye el saldo de un usuario así como consume la asignación de otro usuario de ese saldo.
-- **`transfer_insufficient_balance()`** - Esta función garantiza que una invocación de `transfer()` cause pánico cuando el usuario `from` no tiene el saldo suficiente para cubrirlo.
-- **`transfer_from_insufficient_allowance()`** - Esta función asegura que un usuario con una asignación existente para el saldo de otro no pueda hacer una `transfer()` mayor que esa asignación.
-- **`decimal_is_over_eighteen()`** - Esta función prueba que construir un token con una precisión decimal demasiado alta no tendrá éxito.
-- **`test_zero_allowance()`** - Esta función se asegura de que un `transfer_from()` con un saldo cero no cree una asignación vacía.
-
-## Construir el Contrato
-
-Para crear el contrato, utiliza el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-Un archivo `.wasm` debería ser generado en el directorio `target`:
-
-```text
-target/wasm32v1-none/release/soroban_token_contract.wasm
-```
-
-## Ejecutar el Contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar funciones del contrato usando eso.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --wasm target/wasm32v1-none/release/soroban_token_contract.wasm \
-    --id 1 \
-    -- \
-    balance \
-    --id GBZV3NONYSUDVTEHATQO4BCJVFXJO3XQU5K32X3XREVZKSMMOZFO4ZXR
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --wasm target/wasm32v1-none/release/soroban_token_contract.wasm `
-    --id 1 `
-    -- `
-    balance `
-    --id GBZV3NONYSUDVTEHATQO4BCJVFXJO3XQU5K32X3XREVZKSMMOZFO4ZXR
-```
-
-</TabItem>
-</Tabs>
-
-[`stellar-cli`]: ../../../tools/cli/stellar-cli.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/upgradeable-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/upgradeable-contract.mdx
deleted file mode 100644
index 903929cf58..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/upgradeable-contract.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Contrato Actualizable
-description: Actualizando el Bytecode Wasm para un Contrato Desplegado.
-sidebar_position: 120
----
-
-<head>
-  <title>Actualizando el Bytecode Wasm para un Contrato Desplegado</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Actualizando el Bytecode Wasm para un Contrato Desplegado."
-  />
-  <meta
-    property="og:description"
-    content="Actualizando el Bytecode Wasm para un Contrato Desplegado."
-  />
-</head>
-
-La página de [actualización de contratos](../../guides/conventions/upgrading-contracts.mdx) demuestra cómo actualizar el bytecode Wasm utilizando contratos de ejemplo.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/workspace.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/workspace.mdx
deleted file mode 100644
index 4e6ce8f6bb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/example-contracts/workspace.mdx
+++ /dev/null
@@ -1,283 +0,0 @@
----
-title: Espacio de trabajo
-description: Desarrollar múltiples contratos lado a lado.
-sidebar_position: 170
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-El [ejemplo de espacio de trabajo] demuestra cómo se pueden desarrollar, probar y crear múltiples contratos inteligentes lado a lado en el mismo espacio de trabajo de Rust.
-
-[![Abrir en Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Abrir en Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-[ejemplo de espacio de trabajo]: https://github.com/stellar/soroban-examples/tree/v23.0.0/workspace
-
-## Ejecutar el Ejemplo
-
-Primero sigue el proceso de [Configuración] para preparar tu entorno de desarrollo, luego clona el 'tag' `v23.0.0` del repositorio `soroban-examples`:
-
-[Configuración]: ../getting-started/setup.mdx
-
-```sh
-git clone https://github.com/stellar/soroban-examples
-```
-
-O, omite la configuración del entorno de desarrollo y abre este ejemplo en [GitHub Codespaces][open-in-github-codespaces] o en [Code Anywhere][open-in-code-anywhere].
-
-Para ejecutar las pruebas del ejemplo usa `cargo test`.
-
-```sh
-cd workspace
-cargo test
-```
-
-Deberías ver tres conjuntos de salida, uno para `contract_a`, `contract_a_interface`, y `contract_b`. Los dos primeros crates en el espacio de trabajo no contienen pruebas, pero el tercer crate debería darte la siguiente salida:
-
-```text
-running 1 test
-test test::test ... ok
-```
-
-## Código
-
-<Tabs>
-<TabItem value="Contract A Interface" default>
-
-```rust title="workspace/contract_a_interface/src/lib.rs"
-#![no_std]
-
-use soroban_sdk::contractclient;
-
-#[contractclient(name = "ContractAClient")]
-pub trait ContractAInterface {
-    fn add(x: u32, y: u32) -> u32;
-}
-```
-
-</TabItem>
-<TabItem value="Contract A">
-
-```rust title="workspace/contract_a/src/lib.rs"
-#![no_std]
-
-use soroban_sdk::{contract, contractimpl};
-use soroban_workspace_contract_a_interface::ContractAInterface;
-
-#[contract]
-pub struct ContractA;
-
-#[contractimpl]
-impl ContractAInterface for ContractA {
-    fn add(x: u32, y: u32) -> u32 {
-        x.checked_add(y).expect("no overflow")
-    }
-}
-```
-
-</TabItem>
-<TabItem value="Contract B">
-
-```rust title="workspace/contract_b/src/lib.rs"
-#![no_std]
-
-use soroban_sdk::{contract, contractimpl, Address, Env};
-use soroban_workspace_contract_a_interface::ContractAClient;
-
-#[contract]
-pub struct ContractB;
-
-#[contractimpl]
-impl ContractB {
-    pub fn add_with(env: Env, contract: Address, x: u32, y: u32) -> u32 {
-        let client = ContractAClient::new(&env, &contract);
-        client.add(&x, &y)
-    }
-}
-
-mod test;
-```
-
-</TabItem>
-<TabItem value="Contract B Test">
-
-```rust title="workspace/src/contract_b/src/test.rs"
-#![cfg(test)]
-
-use soroban_sdk::Env;
-
-use crate::{ContractB, ContractBClient};
-
-use soroban_workspace_contract_a::ContractA;
-
-#[test]
-fn test() {
-    let env = Env::default();
-
-    // Register contract A using the native contract imported.
-    let contract_a_id = env.register(ContractA, ());
-
-    // Register contract B defined in this crate.
-    let contract_b_id = env.register(ContractB, ());
-
-    // Create a client for calling contract B.
-    let client = ContractBClient::new(&env, &contract_b_id);
-
-    // Invoke contract B via its client. Contract B will invoke contract A.
-    let sum = client.add_with(&contract_a_id, &5, &7);
-    assert_eq!(sum, 12);
-}
-```
-
-</TabItem>
-</Tabs>
-
-Referencia: https://github.com/stellar/soroban-examples/tree/v23.0.0/workspace
-
-## Cómo Funciona
-
-Hay tres crates que son parte del espacio de trabajo.
-
-1. `contract_a_interface` contiene un trait, `ContractAInterface`, que solo sirve como un lugar para definir el trait de interfaz para el Contrato A.
-2. `contract_a` contains a smart contract, `ContractA`, that implements logic, and conforms to the `ContractAInterface` trait.
-3. `contract_b` es otro contrato inteligente, que implementa una interfaz diferente, y hace una llamada a `ContractA`, y cross-calls la función `contract_a`. Este es también el único crate en el espacio de trabajo con pruebas definidas.
-
-Echemos un vistazo a cada crate y veamos cómo trabajan todos juntos.
-
-### Contrato A Interface: El Trait
-
-El crate `contract_a_interface` define un trait que contiene una interfaz de contrato. Esta interfaz está definida separada de la implementación y solo define cuáles son las funciones exportadas de la implementación.
-
-La interfaz define `add` como la única función que contendrá el contrato. La función `add` requiere dos entradas, `x` y `y`, ambos enteros `u32`, y también retorna un entero `u32`.
-
-El uso de `contractclient` como un macro de atributo en `ContractAInterface` significa que se creará un cliente, conformando a esta interfaz, que podrán usar los contratos existentes fuera del crate `contract_a_interface`. Como verás más adelante, el cliente, `ContractAClient`, se utiliza en el crate `contract_b` para llamar a la función `add`.
-
-### Contrato A: La Lógica
-
-El crate `contract_a` contiene la implementación para el Contrato A, definiendo para cada función lo que debería realmente _hacer_.
-
-La implementación toma el valor de `x`, junto con el valor de `y`, y realiza un `checked_add`, retornando la suma de ambos números (evitando un error de desbordamiento).
-
-:::info
-
-La función `add` no requiere un argumento `Env`. ¡Eso está totalmente bien! `Env` tiene muchas características útiles que están disponibles para tus contratos inteligentes, si las necesitas. Pero, no estás en absoluto obligado a usarlo, si no lo necesitas.
-
-:::
-
-Todo lo que se requiere para hacer uso del `ContractAInterface` previamente definido es `usar` la interfaz, definir una estructura `ContractA`, e `impl` la interfaz para esa estructura.
-
-Este crate utiliza el macro de atributo `contractimpl` en la implementación de `ContractA`, haciendo que la función `add` sea pública e invocable por otros en la red Stellar.
-
-### Contrato B: La Invocación
-
-Ahora que hemos creado un trait en `contract_a_interface`, y lo hemos implementado en `contract_a`, podemos usar el crate `contract_b` para invocar la función `add` y obtener la suma de nuestros enteros.
-
-Estamos creando e implementando un contrato completamente nuevo, `ContractB`. Estamos saltando el trait y yendo directamente al contrato en sí.
-
-::: info
-
-Definir la interfaz del contrato con un `trait` por separado es opcional. Es una excelente manera de compartir la interfaz de un contrato y un cliente de contrato, con múltiples contratos en un espacio de trabajo multi-contrato.
-
-:::
-
-`ContractB` tiene una función, `add_with`, que requiere tres argumentos:
-
-- `contract: Address` - La dirección de un contrato que implementa esa interfaz de cliente requerida, `ContractAInterface`.
-- `x: u32` y `y: u32` - Los dos números que queremos (safely) calcular la suma de.
-
-`ContractB` invoca la función `add` de `ContractA`, retornando su valor al invocador original. Es un poco largo el viaje para este ejemplo simple, pero ilustra una manera muy poderosa en la que puedes separar las definiciones de interfaz/trait de la lógica del contrato y compartirla junto con su cliente en un espacio de trabajo multi-contrato.
-
-## Ejemplos de Casos de Uso Prácticos
-
-Más allá de este ejemplo simple, esta técnica es versátil y útil. Por ejemplo, esta estrategia podría usarse para:
-
-- Crear y referenciar una interfaz de token estandarizada y consistente.
-- Reutilizar una única interfaz que deseas incorporar en muchos contratos diferentes.
-
-## Crear los Contratos
-
-Para crear los contratos en un conjunto de archivos `.wasm`, usa el comando `stellar contract build`. Tanto `workspace/contract_a` como `workspace/contract_b` serán creados, y puedes usar un solo comando, ya que nuestro espacio de trabajo define sus `members` en el archivo `Cargo.toml`:
-
-```sh
-stellar contract build
-```
-
-Deberías encontrar dos archivos `.wasm` en el directorio `workspace/target`:
-
-```text
-target/wasm32v1-none/release/soroban_workspace_contract_a.wasm
-target/wasm32v1-none/release/soroban_workspace_contract_b.wasm
-```
-
-El [`stellar-cli`] sabe que el `contract_a_interface` no está destinado a ser compilado en un .wasm, porque el `Cargo.toml` del `contract_a_interface` tiene su `crate-type` configurado como `rlib` (librería rust). ¡Genial!
-
-## Ejecutar el Contrato
-
-Si tienes [`stellar-cli`] instalado, puedes invocar las funciones del contrato. Ambos contratos deben estar desplegados.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/soroban_workspace_contract_a.wasm
-```
-
-```sh
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/soroban_workspace_contract_b.wasm
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract deploy `
-    --wasm target/wasm32v1-none/release/soroban_workspace_contract_a.wasm
-```
-
-```powershell
-stellar contract deploy `
-    --wasm target/wasm32v1-none/release/soroban_workspace_contract_b.wasm
-```
-
-</TabItem>
-</Tabs>
-
-Invoca la función `add_with` de `ContractB`, pasando la dirección de `ContractA` para `contract`, y los valores enteros para `x` y `y` (por ejemplo, como `5` y `7`).
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-    --id CONTRACT_B_ADDRESS \
-    -- \
-    add_with \
-    --contract CONTRACT_A_ADDRESS \
-    --x 5 \
-    --y 7
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-    --id CONTRACT_B_ADDRESS `
-    -- `
-    add_with `
-    --contract CONTRACT_A_ADDRESS `
-    --x 5 `
-    --y 7
-```
-
-</TabItem>
-</Tabs>
-
-[`stellar-cli`]: ../getting-started/setup.mdx#install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/README.mdx
deleted file mode 100644
index 81e78834ac..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Comenzar con contratos inteligentes: Configurar, escribir en Rust y desplegar"
-sidebar_label: Comenzar
-description: Comienza con contratos inteligentes configurando tu entorno, escribiendo código en Rust y desplegando contratos utilizando herramientas de CLI en la red Stellar.
-sidebar_position: 20
----
-
-# Comenzar
-
-import DocCardList from "@theme/DocCardList";
-
-Sumérgete en el desarrollo de contratos inteligentes con este tutorial de Comenzar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/deploy-increment-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/deploy-increment-contract.mdx
deleted file mode 100644
index 17534794e5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/deploy-increment-contract.mdx
+++ /dev/null
@@ -1,137 +0,0 @@
----
-sidebar_position: 40
-title: "Desplegar el Contrato Inteligente de Incremento en Testnet Usando la CLI: Una Guía"
-sidebar_label: 4. Desplegar el Increment Contract
-description: Sigue esta guía paso a paso en la sección final de Comenzar para aprender cómo desplegar el contrato inteligente de incremento en Testnet usando la Stellar CLI.
----
-
-# 4. Desplegar el Contrato de Incremento
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-## Despliegue de dos pasos
-
-Vale la pena saber que `deploy` es en realidad un proceso de dos pasos.
-
-1. **Sube los bytes del contrato a la red.** Soroban actualmente se refiere a esto como _instalando_ el contrato—desde la perspectiva de la blockchain, esta es una metáfora razonable. Esto sube los bytes del contrato a la red, indexándolo por su hash. Este código de contrato ahora puede ser referenciado por múltiples contratos, lo que significa que tendrían exactamente el mismo _comportamiento_ pero un estado de almacenamiento separado.
-
-2. **Instanciar el contrato.** Esto realmente crea lo que probablemente pienses como un Smart Contract. Crea un nuevo ID de contrato y lo asocia con los bytes del contrato que fueron subidos en el paso anterior.
-
-Puedes ejecutar estos dos pasos por separado. Probémoslo con el contrato Increment:
-
-:::info
-
-Si el contrato aún no ha sido desarrollada, ejecuta el comando de construcción `stellar contract build` desde el directorio raíz del contrato.
-
-:::
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract upload \
-  --network testnet \
-  --source-account alice \
-  --wasm target/wasm32v1-none/release/increment.wasm
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract upload `
-  --network testnet `
-  --source-account alice `
-  --wasm target/wasm32v1-none/release/increment.wasm
-```
-
-</TabItem>
-
-</Tabs>
-
-Esto devuelve el hash de los bytes Wasm, como `6ddb28e0980f643bb97350f7e3bacb0ff1fe74d846c6d4f2c625e766210fbb5b`. Ahora puedes usar `--wasm-hash` con `deploy` en lugar de `--wasm.` Asegúrate de reemplazar el ejemplo de hash wasm con el tuyo propio.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract deploy \
-  --wasm-hash 6ddb28e0980f643bb97350f7e3bacb0ff1fe74d846c6d4f2c625e766210fbb5b \
-  --source-account alice \
-  --network testnet \
-  --alias increment
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract deploy `
-  --wasm-hash 6ddb28e0980f643bb97350f7e3bacb0ff1fe74d846c6d4f2c625e766210fbb5b `
-  --source-account alice `
-  --network testnet `
-  --alias increment
-```
-
-</TabItem>
-
-</Tabs>
-
-Este comando devolverá el ID del contrato (por ejemplo, `CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN`), y puedes usarlo para invocar el contrato como hicimos en ejemplos anteriores.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-  --id CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN \
-  --source-account alice \
-  --network testnet \
-  -- \
-  increment
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-  --id CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN `
-  --source-account alice `
-  --network testnet `
-  -- `
-  increment
-```
-
-</TabItem>
-
-</Tabs>
-
-Deberías ver la siguiente salida:
-
-```sh
-1
-```
-
-Ejecuta esto varias veces más para observar cómo cambia el conteo.
-
-## Ejecutar tu propia red/nodo
-
-A veces necesitarás ejecutar tu propio nodo:
-
-- ¡Aplicaciones en producción! Stellar mantiene nodos RPC de prueba públicos para Testnet y Futurenet, pero no para Mainnet. En su lugar, necesitarás ejecutar tu propio nodo y apuntar tu aplicación a ese nodo. Si quieres usar una plataforma de software como servicio para esto, [varios proveedores](../../../data/apis/rpc/providers.mdx) están disponibles.
-- Cuando necesites una red que difiera de la versión desplegada en Testnet.
-
-El equipo de RPC mantiene contenedores Docker que facilitan esto al máximo. Consulta la referencia de [RPC](../../../data/apis/rpc/admin-guide/README.mdx) para obtener más detalles.
-
-## Próximamente
-
-¿Listo para convertir estos contratos desplegados en una aplicación web simple? Dirígete a la [sección Construir un Frontend Dapp](../../apps/dapp-frontend.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/deploy-to-testnet.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/deploy-to-testnet.mdx
deleted file mode 100644
index 3cf338f183..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/deploy-to-testnet.mdx
+++ /dev/null
@@ -1,158 +0,0 @@
----
-sidebar_position: 20
-title: Desplegar y depurar contratos inteligentes en Testnet e interactuar con otros contratos
-sidebar_label: 2. Desplegar en Testnet
-description: Desplegar contratos inteligentes Stellar en Testnet utilizando la CLI, interactuar con otros contratos, probar la funcionalidad, depurar incidencias y prepararse para el despliegue en Mainnet.
----
-
-# 2. Desplegar en Testnet
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-Para recapitular lo que hemos hecho hasta ahora, en [Configuración](setup.mdx):
-
-- configuramos nuestro entorno local para escribir contratos inteligentes en Rust
-- instalamos el stellar-cli
-- configuramos el stellar-cli para comunicarse con el Stellar Testnet a través de RPC
-- y configuramos una identidad para firmar transacciones
-
-En [Hola Mundo](./hello-world.mdx) creamos un proyecto `hello-world`, y aprendimos cómo probar y construir el contrato `HelloWorld`. Ahora estamos listos para desplegar ese contrato en Testnet, e interactuar con él.
-
-## Configurar una Cuenta de Origen
-
-Cuando implementas un contrato inteligente en una red, debes especificar el keypair de una cuenta de origen que se usará para firmar las transacciones.
-
-Generemos un keypair llamado `alice`. Puedes usar cualquier nombre que desees, pero sería útil tener algunas claves nombradas que puedas usar para pruebas, como [`alice`, `bob` y `carol`](https://en.wikipedia.org/wiki/Alice_and_Bob). Ten en cuenta que la cuenta del keypair será financiada utilizando [Friendbot](../../../networks/README.mdx#friendbot).
-
-```sh
-stellar keys generate alice --network testnet --fund
-```
-
-Puedes ver la clave pública de `alice` con:
-
-```sh
-stellar keys address alice
-```
-
-Puedes ver todas las claves que generaste, junto con la ubicación en tu sistema de archivos donde se almacena su información, con:
-
-```sh
-stellar keys ls -l
-```
-
-## Desplegar
-
-Para desplegar tu contrato HelloWorld, ejecuta el siguiente comando:
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract deploy \
-  --wasm target/wasm32v1-none/release/hello_world.wasm \
-  --source-account alice \
-  --network testnet \
-  --alias hello_world
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract deploy `
-  --wasm target/wasm32v1-none/release/hello_world.wasm `
-  --source-account alice `
-  --network testnet `
-  --alias hello_world
-```
-
-</TabItem>
-
-</Tabs>
-
-Esto devuelve el id del contrato, comenzando con una `C`. En este ejemplo, vamos a usar `CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN`, así que reemplázalo con tu id de contrato real.
-
-:::tip
-
-Usamos el flag `--alias` en este comando de despliegue, que creará un archivo `~/.config/stellar/contract-ids/hello_world.json` que asigna el alias `hello_world` al ID del contrato y a la red. Esto nos permite referirnos a este contrato por su alias en lugar del id del contrato.
-
-:::
-
-## Interactuar
-
-Usando el código que escribimos en [Escribir un Contrato](./hello-world.mdx#contract-source-code) y el archivo `.wasm` resultante que construimos en [Construir](hello-world.mdx#build-the-contract), ejecuta el siguiente comando para invocar la función `hello`.
-
-:::info
-
-En el fondo, el CLI está haciendo llamadas RPC. Para obtener información sobre eso, consulta la página de referencia [RPC](../../../data/apis/rpc/admin-guide/README.mdx).
-
-:::
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-  --id CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN \
-  --source-account alice \
-  --network testnet \
-  -- \
-  hello \
-  --to RPC
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-  --id CACDYF3CYMJEJTIVFESQYZTN67GO2R5D5IUABTCUG3HXQSRXCSOROBAN `
-  --source-account alice `
-  --network testnet `
-  -- `
-  hello `
-  --to RPC
-```
-
-</TabItem>
-
-</Tabs>
-
-La siguiente salida debería aparecer.
-
-```json
-["Hello", "RPC"]
-```
-
-:::info
-
-¡El doble guion `--` es obligatorio!
-
-Este es un patrón general de [CLI](https://unix.stackexchange.com/questions/11376/what-does-double-dash-mean) usado por otros comandos como [cargo run](https://doc.rust-lang.org/cargo/commands/cargo-run.html). Todo lo que aparece después del `--`, a veces llamado [slop](https://github.com/clap-rs/clap/issues/971), se pasa a un proceso hijo. En este caso, `stellar contract invoke` construye un _CLI implícito_ sobre la marcha para el método `hello` en tu contrato. Puede hacer esto porque el Soroban SDK incrusta los tipos de esquema / interfaz de tu contrato directamente en el archivo `.wasm` que se despliega en on-chain. También puedes probar:
-
-```sh
-stellar contract invoke ... -- --help
-```
-
-y
-
-```sh
-stellar contract invoke ... -- hello --help
-```
-
-:::
-
-## Resumen
-
-En esta lección, aprendimos a:
-
-- desplegar un contrato en Testnet
-- interactuar con un contrato desplegado
-
-A continuación, añadiremos un nuevo contrato a este proyecto, y veremos cómo nuestro espacio de trabajo puede acomodar un proyecto de múltiples contratos. El nuevo contrato mostrará un poco de las capacidades de almacenamiento de Soroban.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/hello-world-frontend.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/hello-world-frontend.mdx
deleted file mode 100644
index fd8c07b85e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/hello-world-frontend.mdx
+++ /dev/null
@@ -1,178 +0,0 @@
----
-sidebar_position: 50
-sidebar_label: 5. Crear un frontend Hello World
-title: Crear un frontend para el contrato Hello World
-description: Crear un frontend para el contrato Hello World utilizando Stellar CLI para generar enlaces de TypeScript.
-pagination_next: build/apps/dapp-frontend
----
-
-# 5. Crear un frontend Hello World
-
-En los ejemplos anteriores, invocamos los contratos utilizando Stellar CLI, y en esta última parte de la guía vamos a crear una aplicación web que interactúa con el contrato Hello World a través de enlaces de TypeScript.
-
-:::info
-
-Este ejemplo muestra una manera de crear una vinculación entre un contrato y un frontend. Para una guía más completa sobre frontends de Dapp, consulta la documentación [Desarrollar un frontend para Dapp](../../apps/dapp-frontend.mdx). Para herramientas que te ayuden a comenzar rápidamente con contratos inteligentes integrados en un entorno frontend funcional, aprende más sobre [Scaffold Stellar](#using-scaffold-stellar-to-rapidly-develop-dapps).
-
-:::
-
-## Inicializar una cadena de herramientas frontend desde cero
-
-Puedes crear un dapp Stellar con cualquier cadena de herramientas para frontend o integrarlo en cualquier aplicación de stack completo existente. Para este tutorial, vamos a utilizar [Astro](https://astro.build/). Astro trabaja con React, Vue, Svelte, cualquier otra biblioteca de interfaz de usuario o sin biblioteca de interfaz de usuario en absoluto. En este tutorial, no estamos utilizando una biblioteca de interfaz de usuario. Las partes específicas del contrato inteligente de este tutorial serán similares sin importar qué cadena de herramientas para frontend utilices.
-
-Si eres nuevo en el frontend, no te preocupes. No profundizaremos demasiado. Pero será útil para ti ver y experimentar el proceso de desarrollo de frontend utilizado por aplicaciones de contratos inteligentes. Cubriré los aspectos relevantes de JavaScript y Astro, pero enseñar todo el desarrollo de frontend y Astro está más allá del alcance de este tutorial.
-
-Vamos a comenzar.
-
-Vas a necesitar [Node.js](https://nodejs.org/en/download/package-manager/) v20 o superior. Si aún no lo has hecho, instálalo ahora.
-
-Queremos crear un proyecto Astro con el contrato Hello World de las lecciones anteriores integrado. Para hacerlo, instalamos el proyecto Astro por defecto:
-
-```sh
-npm create astro@latest
-```
-
-Este proyecto tiene la siguiente estructura de directorios.
-
-```sh
-extra-escape
-├── astro.config.mjs
-├── package-lock.json
-├── package.json
-├── packages
-├── public
-├── README.md
-├── src
-│   ├── assets
-│   │   ├── astro.svg
-│   │   └── background.svg
-│   ├── components
-│   │   └── Welcome.astro
-│   ├── layouts
-│   │   └── Layout.astro
-│   └── pages
-│       └── index.astro
-└── tsconfig.json
-```
-
-## Generar un paquete NPM para el contrato Hello World
-
-Antes de abrir los nuevos archivos de frontend, generemos un paquete NPM para el contrato Hello World. Esta es nuestra forma sugerida de interactuar con contratos desde frontends. Estas bibliotecas generadas funcionan con cualquier proyecto JavaScript (no con una interfaz específica como React) y facilitan trabajar con algunos de los aspectos más complejos de los contratos inteligentes en Stellar, como la codificación de [XDR](../../../learn/fundamentals/contract-development/types/fully-typed-contracts.mdx).
-
-Esto va a utilizar el comando CLI `stellar contract bindings typescript`:
-
-```sh
-stellar contract bindings typescript \
-  --network testnet \
-  --contract-id hello_world \
-  --output-dir packages/hello_world
-```
-
-:::tip
-
-¡Ten en cuenta que pudimos utilizar el alias del contrato, `hello_world`, en lugar del ID del contrato!
-
-:::
-
-El enlace se creará como un paquete NPM en el directorio `packages/hello_world` como se especifica en el comando CLI. Necesitaremos compilar el paquete de enlaces, ya que (en su estado inicial) el paquete es mayormente tipos y stubs de TypeScript para las diversas funciones del contrato.
-
-```sh
-cd packages/hello_world
-npm install
-npm run build
-cd ../..
-```
-
-Intentamos mantener el código en estas bibliotecas generadas legible, así que ve y explora. Abre el nuevo directorio `packages/hello_world` en tu editor. Si has construido o contribuido a proyectos de Node, todo te parecerá familiar. Verás un archivo `package.json`, un directorio `src`, un `tsconfig.json`, e incluso un README.
-
-## Llamar al contrato desde el frontend
-
-Ahora abramos `src/pages/index.astro` y utilicemos el enlace para llamar a la función del contrato `hello` con un argumento.
-
-El proyecto Astro por defecto consiste en una página (`pages/index.astro`) y un componente de bienvenida (`component/Welcome.astro`), y no necesitamos ninguno de esos códigos. Reemplaza el código de `pages/index.astro` con este código (el componente de bienvenida no será necesario):
-
-```ts title="src/pages/index.astro"
----
-import * as Client from './packages/hello_world';
-
-const contract = new Client.Client({
-   ...Client.networks.testnet,
-   rpcUrl: 'https://soroban-testnet.stellar.org:443'
-});
-
-const { result } = await contract.hello({to: "Devs!"});
-const greeting = result.join(" ");
----
-
-<h1>{greeting}</h1>
-```
-
-Primero importamos la biblioteca de enlaces, y luego necesitamos definir un cliente de contrato que podamos usar para invocar la función del contrato que desplegamos en testnet en un paso anterior.
-
-La función del contrato `hello()` se invoca de forma sincrónica con el argumento `{to: "Devs!"}` y la respuesta esperada es un arreglo que consiste en "Hello" y "Devs!". Unimos el arreglo de resultados y la constante `greeting` debería ahora contener el texto `Hello Devs!`
-
-Bajando a la sección HTML ahora queremos mostrar el texto `greeting` en el navegador. ¡Veámoslo en acción! Inicia el servidor de desarrollo:
-
-```sh
-npm run dev
-```
-
-Y abre [localhost:4321](http://localhost:4321) en tu navegador. ¡Deberías ver el saludo del contrato!
-
-Puedes intentar actualizar el argumento a `{ to: 'Stellar' }`. Cuando guardes el archivo, la página se actualizará automáticamente.
-
-:::info
-
-Cuando inicies el servidor de desarrollo con `npm run dev`, verás una salida similar en tu terminal a cuando ejecutaste `npm run init`. Esto es porque el script `dev` en package.json está configurado para ejecutar `npm run init` y `astro dev`, para que puedas asegurarte de que tu contrato desplegado y tu paquete NPM generado estén siempre sincronizados. Si quieres simplemente iniciar el servidor de desarrollo sin el script initialize.js, puedes ejecutar `npm run astro dev`.
-
-:::
-
-## Usar Scaffold Stellar para desarrollar dapps rápidamente
-
-[Scaffold Stellar](../../../tools/scaffold-stellar.mdx) es un kit de herramientas para desarrolladores para construir aplicaciones descentralizadas y contratos inteligentes en la blockchain Stellar, integrado con una aplicación frontend.
-
-Conseguir un conjunto funcional de contratos inteligentes y un frontend se puede hacer en sólo unos pocos pasos con Scaffold Stellar. Este tutorial te mostrará cómo crear un nuevo proyecto Scaffold Stellar.
-
-Si deseas usar contratos inteligentes existentes en un proyecto Scaffold Stellar, ¡solo tienes que copiarlos a la carpeta `contracts/` en la raíz de tu proyecto!
-
-1. Instalar el CLI de Scaffold Stellar
-
-Como ya tienes instalado el CLI de Stellar, tienes todo lo necesario para instalar Scaffold Stellar:
-
-```sh
-cargo binstall stellar-scaffold-cli
-```
-
-Recomendamos usar [binstall](https://crates.io/crates/cargo-binstall) para instalaciones más rápidas, o usar `cargo install --locked stellar-scaffold-cli`. Scaffold Stellar es un plugin del CLI de Stellar, por lo que usarás `stellar scaffold` desde la línea de comandos.
-
-2. Inicializar un proyecto Scaffold Stellar nuevo
-
-```sh
-stellar scaffold init <my-project>
-```
-
-Scaffold Stellar es un plugin del CLI de Stellar, así que ejecutarás comandos como `stellar scaffold <comando>`. `init` inicializa un proyecto Stellar Scaffold nuevo en la ruta proporcionada.
-
-3. Instalar dependencias de Node y configurar variables de entorno
-
-Asegúrate de tener [Node.js](https://nodejs.org/en/download/package-manager/) instalado, y ejecuta:
-
-```sh
-cd <my-project> # make sure you're in your new project's directory
-npm install # install frontend dependencies
-cp .env.example .env # copies the example frontend environment variable file to your own copy
-```
-
-4. ¡Inicia tu app en modo desarrollo!
-
-```sh
-npm start # or npm run dev
-```
-
-Este comando realiza dos tareas simultáneamente: ejecuta `stellar scaffold watch --build-clients`, que compila tus contratos inteligentes, actualizándolos a medida que los modificas, desplegándolos en tu cadena Stellar local (¡asegúrate de que Docker esté corriendo!), y configura todos estos ajustes vía tu archivo `environments.toml` en la carpeta raíz de tu proyecto.
-
-La segunda tarea que ejecuta es `vite`, una popular herramienta de compilación JavaScript que compila y observa tu frontend React para detectar cambios.
-
-Después de unos momentos de compilación, podrás ver tu app funcionando en [localhost:5173](http://localhost:5173)!
-
-Aprende más sobre [Scaffold Stellar](../../../tools/scaffold-stellar.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/hello-world.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/hello-world.mdx
deleted file mode 100644
index cf88e072fe..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/hello-world.mdx
+++ /dev/null
@@ -1,347 +0,0 @@
----
-sidebar_position: 10
-sidebar_label: 1. Hola Mundo
-title: Escribir, Probar y Desplegar un Contrato Inteligente en Rust
-description: Crear tu primer contrato inteligente en Stellar con esta guía Hola Mundo. Aprende cómo escribir, desplegar y probar tu contrato utilizando Rust y el CLI de Stellar.
----
-
-# Hola Mundo
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-Una vez que hayas [configurado](./setup.mdx) tu entorno de desarrollo, estás listo para crear tu primer contrato inteligente.
-
-## Crear un nuevo proyecto
-
-Crear un nuevo proyecto usando el comando `init` para crear un proyecto `soroban-hello-world`.
-
-```sh
-stellar contract init soroban-hello-world
-```
-
-El comando `init` creará un proyecto de espacio de trabajo en Rust, usando la estructura recomendada para incluir contratos Soroban. Veamos la estructura del proyecto:
-
-```
-.
-├── Cargo.lock
-├── Cargo.toml
-├── README.md
-└── contracts
-    ├── hello_world
-    │   ├── Cargo.toml
-    │   ├── Makefile
-    │   ├── src
-    │   │   ├── lib.rs
-    │   │   └── test.rs
-```
-
-### Cargo.toml
-
-El archivo `Cargo.toml` en la raíz del proyecto está configurado como Espacio de Trabajo en Rust, lo que nos permite incluir múltiples contratos inteligentes en un solo proyecto.
-
-#### Espacio de Trabajo en Rust
-
-El archivo `Cargo.toml` establece los miembros del espacio de trabajo como todo el contenido del directorio `contracts` y establece la versión de la dependencia `soroban-sdk` del espacio de trabajo, incluyendo la característica `testutils`, que permitirá generar utilidades de prueba para llamar al contrato en las pruebas.
-
-```toml title="Cargo.toml"
-[workspace]
-resolver = "2"
-members = [
-  "contracts/*",
-]
-
-[workspace.dependencies]
-soroban-sdk = "22"
-```
-
-:::info
-
-Los `testutils` se habilitan automáticamente dentro de [pruebas unitarias de Rust] dentro del mismo crate que tu contrato. Si escribes pruebas desde otro crate, necesitarás requerir la característica `testutils` para esas pruebas y habilitar la característica `testutils` al ejecutar tus pruebas con `cargo test --features testutils` para poder usar esas utilidades de prueba.
-
-:::
-
-#### Perfil `release`
-
-Configurar el perfil `release` para optimizar la construcción del contrato es fundamental. Los contratos Soroban tienen un tamaño máximo de 64KB. Los programas en Rust, incluso los pequeños, sin estas configuraciones, casi siempre superan este tamaño.
-
-El archivo `Cargo.toml` tiene el siguiente perfil de lanzamiento configurado.
-
-```toml
-[profile.release]
-opt-level = "z"
-overflow-checks = true
-debug = 0
-strip = "symbols"
-debug-assertions = false
-panic = "abort"
-codegen-units = 1
-lto = true
-```
-
-#### Perfil `release-with-logs`
-
-Configurar un perfil `release-with-logs` puede ser útil si necesitas construir un archivo `.wasm` que tenga habilitados los registros para imprimir registros de depuración al usar el [`stellar-cli`]. Nota que esto no es necesario para acceder a registros de depuración en pruebas o para usar un depurador paso a paso.
-
-```toml
-[profile.release-with-logs]
-inherits = "release"
-debug-assertions = true
-```
-
-Consulta el [ejemplo de registro] para más información sobre cómo registrar.
-
-[ejemplo de registro]: ../example-contracts/logging.mdx
-
-### Directorio de contratos
-
-El directorio `contracts` es donde vivirán los contratos Soroban, cada uno en su propio directorio. Ya hay un contrato `hello_world` allí para ayudarte a comenzar.
-
-#### Archivo Cargo.toml específico del contrato
-
-Cada contrato debería tener su propio archivo `Cargo.toml`, que depende del `Cargo.toml` de nivel superior del que acabamos de hablar.
-
-Aquí es donde podemos especificar información del paquete específica del contrato.
-
-```toml title="contracts/hello_world/Cargo.toml"
-[package]
-name = "hello-world"
-version = "0.0.0"
-edition = "2021"
-publish = false
-```
-
-El `crate-type` está configurado como `cdylib`, que es necesario para construir contratos.
-
-```toml
-[lib]
-crate-type = ["cdylib"]
-doctest = false
-```
-
-También hemos incluido la dependencia soroban-sdk, configurada para usar la versión del Cargo.toml del espacio de trabajo.
-
-```toml
-[dependencies]
-soroban-sdk = { workspace = true }
-
-[dev-dependencies]
-soroban-sdk = { workspace = true, features = ["testutils"] }
-```
-
-#### Código fuente del contrato
-
-Crear un contrato Soroban implica escribir código Rust en el archivo `lib.rs` del proyecto.
-
-Todos los contratos deben comenzar con `#![no_std]` para asegurar que no se incluya la biblioteca estándar de Rust en la construcción. La biblioteca estándar de Rust es grande y no se adapta bien a ser desplegada en programas pequeños como los que se despliegan en blockchains.
-
-```rust
-#![no_std]
-```
-
-El contrato importa los tipos y macros que necesita del crate `soroban-sdk`.
-
-```rust
-use soroban_sdk::{contract, contractimpl, vec, Env, String, Vec};
-```
-
-Muchos de los tipos disponibles en programas típicos de Rust, como `std::vec::Vec`, no están disponibles, ya que no hay asignador y no hay memoria en el heap en los contratos Soroban. El `soroban-sdk` proporciona una variedad de tipos como `Vec`, `Map`, `Bytes`, `BytesN`, `Symbol`, que todos utilizan la memoria y las capacidades nativas del entorno Soroban. Los valores primitivos como `u128`, `i128`, `u64`, `i64`, `u32`, `i32`, y `bool` también se pueden usar. No se admiten flotantes y matemáticas de punto flotante.
-
-Las entradas del contrato no deben ser referencias.
-
-El atributo `#[contract]` designa la estructura `Contract` como el tipo al que se asocian las funciones del contrato. Esto implica que la estructura tendrá funciones de contrato implementadas para ella.
-
-```rust
-#[contract]
-pub struct Contract;
-```
-
-Las funciones del contrato se definen dentro de un bloque `impl` para la estructura, que está anotado con `#[contractimpl]`. Es importante notar que las funciones del contrato deben tener nombres con una longitud máxima de 32 caracteres. Además, si una función se pretende invocar desde fuera del contrato, debe estar marcada con el modificador de visibilidad `pub`. Es común que el primer argumento de una función de contrato sea de tipo `Env`, permitiendo acceder a una copia del entorno Soroban, que es típicamente necesario para varias operaciones dentro del contrato.
-
-```rust
-#[contractimpl]
-impl Contract {
-    pub fn hello(env: Env, to: String) -> Vec<String> {
-        vec![&env, String::from_str(&env, "Hello"), to]
-    }
-}
-```
-
-Uniendo esas piezas, un contrato simple se ve así.
-
-```rust title="contracts/hello_world/src/lib.rs"
-#![no_std]
-use soroban_sdk::{contract, contractimpl, vec, Env, String, Vec};
-
-#[contract]
-pub struct Contract;
-
-#[contractimpl]
-impl Contract {
-    pub fn hello(env: Env, to: String) -> Vec<String> {
-        vec![&env, String::from_str(&env, "Hello"), to]
-    }
-}
-
-mod test;
-```
-
-Nota la línea `mod test` al final, esto le dirá a Rust que compile y ejecute el código de prueba, que veremos a continuación.
-
-#### Pruebas unitarias del contrato
-
-Escribir pruebas para contratos Soroban implica escribir código Rust usando las instalaciones de prueba y la cadena de herramientas que usarías para probar cualquier código Rust.
-
-Dado nuestro `Contract`, una prueba simple se verá así.
-
-<Tabs>
-<TabItem value="lib.rs" label="contracts/hello_world/src/lib.rs">
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, vec, Env, String, Vec};
-
-#[contract]
-pub struct Contract;
-
-#[contractimpl]
-impl Contract {
-    pub fn hello(env: Env, to: String) -> Vec<String> {
-        vec![&env, String::from_str(&env, "Hello"), to]
-    }
-}
-
-mod test;
-```
-
-</TabItem>
-<TabItem value="test.rs" label="contracts/hello_world/src/test.rs" default>
-
-```rust
-#![cfg(test)]
-
-use super::*;
-use soroban_sdk::{vec, Env, String};
-
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(Contract, ());
-    let client = ContractClient::new(&env, &contract_id);
-
-    let words = client.hello(&String::from_str(&env, "Dev"));
-    assert_eq!(
-        words,
-        vec![
-            &env,
-            String::from_str(&env, "Hello"),
-            String::from_str(&env, "Dev"),
-        ]
-    );
-}
-```
-
-</TabItem>
-</Tabs>
-
-En cualquier prueba, lo primero que siempre se requiere es un `Env`, que es el entorno Soroban en el que se ejecutará el contrato.
-
-```rust
-let env = Env::default();
-```
-
-El contrato se registra con el entorno usando el tipo de contrato. Los contratos pueden especificar un ID de contrato fijo como el primer argumento, o proporcionar `None` y se generará uno.
-
-```rust
-let contract_id = env.register(Contract, ());
-```
-
-Todas las funciones públicas dentro de un bloque `impl` que está anotado con el atributo `#[contractimpl]` tienen una función correspondiente generada en un tipo de cliente generado. El tipo de cliente se nombrará igual que el tipo de contrato con `Client` añadido. Por ejemplo, en nuestro contrato, el tipo de contrato es `Contract`, y el cliente se llama `ContractClient`.
-
-```rust
-let client = ContractClient::new(&env, &contract_id);
-let words = client.hello(&String::from_str(&env, "Dev"));
-```
-
-Los valores devueltos por las funciones pueden ser afirmados:
-
-```rust
-    assert_eq!(
-        words,
-        vec![
-            &env,
-            String::from_str(&env, "Hello"),
-            String::from_str(&env, "Dev"),
-        ]
-    );
-```
-
-## Ejecutar las pruebas
-
-Ejecuta `cargo test` y observa cómo se ejecuta la prueba unitaria. Deberías ver la siguiente salida:
-
-```sh
-cargo test
-```
-
-```
-running 1 test
-test test::test ... ok
-```
-
-Intenta cambiar los valores en la prueba para ver cómo funciona.
-
-:::note
-
-La primera vez que ejecutes las pruebas, es posible que veas la salida en el terminal de cargo compilando todas las dependencias antes de ejecutar las pruebas.
-
-:::
-
-## Construir el contrato
-
-Para construir un contrato inteligente para desplegar o ejecutar, usa el comando `stellar contract build`.
-
-```sh
-stellar contract build
-```
-
-:::tip
-
-If you get an error like `can't find crate for 'core'`, it means you didn't install the wasm32 target during the [setup step](./setup.mdx#install-the-target). Puedes hacerlo ejecutando `rustup target add wasm32v1-none` (usa `rustup target add wasm32v1-none` para versiones de Rust **anteriores a** `v1.85.0`).
-
-:::
-
-Este es un pequeño envoltorio alrededor de `cargo build` que establece el objetivo en `wasm32v1-none` y el perfil en `release`. Puedes pensarlo como un acceso directo para el siguiente comando:
-
-```sh
-cargo build --target wasm32v1-none --release
-```
-
-Un archivo `.wasm` se generará en el directorio `target`, en `target/wasm32v1-none/release/hello_world.wasm`. El archivo `.wasm` es el contrato construido.
-
-El archivo `.wasm` contiene la lógica del contrato, así como los [tipos de especificación / interfaz](../../../learn/fundamentals/contract-development/types/fully-typed-contracts.mdx) del contrato, que pueden importarse en otros contratos que deseen llamarlo. Este es el único artefacto necesario para desplegar el contrato, compartir la interfaz con otros, o realizar pruebas de integración contra el contrato.
-
-## Optimizing Builds
-
-Usa `stellar contract optimize` para minimizar aún más el tamaño del `.wasm`:
-
-```sh
-stellar contract optimize --wasm target/wasm32v1-none/release/hello_world.wasm
-```
-
-Esto optimizará y generará un nuevo archivo `hello_world.optimized.wasm` en la misma ubicación que el archivo de entrada `.wasm`.
-
-:::tip
-
-Construir contratos optimizados solo es necesario al desplegar en una red con tarifas o al analizar y perfilar un contrato para hacerlo lo más pequeño posible. Si recién estás comenzando a escribir un contrato, estos pasos no son necesarios. Consulta [Construir](#build-the-contract) para obtener detalles sobre cómo construir para desarrollo.
-
-:::
-
-## Resumen
-
-En esta sección, escribimos un contrato simple que se puede despliegar en una red Soroban.
-
-A continuación, aprenderemos a desplegar el contrato HelloWorld en la red Testnet de Stellar e interactuar con él a través de RPC usando el CLI.
-
-[Pruebas unitarias de Rust]: https://doc.rust-lang.org/rust-by-example/testing/unit_testing.html
-[`stellar-cli`]: setup.mdx#install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/setup.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/setup.mdx
deleted file mode 100644
index e4216845f4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/setup.mdx
+++ /dev/null
@@ -1,291 +0,0 @@
----
-title: Configurar y preparar tu entorno para escribir contratos inteligentes
-sidebar_label: Configuración
-description: Aprende a configurar el desarrollo de contratos inteligentes Stellar instalando Rust, configurando tu editor y preparando el CLI de Stellar con esta guía paso a paso.
-sidebar_position: 0
----
-
-# Configuración
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-import { getShell } from "@site/src/helpers/getShell";
-import { latestVersion } from "@site/src/helpers/stellarCli";
-import { getStellarCliLatestReleaseUrl } from "@site/src/helpers/getStellarCliLatestReleaseUrl";
-import { StellarCliVersion } from "@site/src/components/StellarCliVersion";
-import { StellarCliWingetVersion } from "@site/src/components/StellarCliWingetVersion";
-
-Los contratos inteligentes Stellar son pequeños programas escritos en el lenguaje de programación [Rust].
-
-Para crear y desarrollar contratos, necesitas los siguientes requisitos previos:
-
-- Una cadena de herramientas de [Rust]
-- Un editor que admita Rust
-- [Stellar CLI]
-
-## Instalar Rust
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-Si usa macOS, Linux u otro sistema operativo tipo Unix, el método más simple para instalar una toolchain de Rust es instalar `rustup`. Instala `rustup` con el siguiente comando.
-
-```sh
-curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
-```
-
-Luego reinicia la terminal.
-
-</TabItem>
-<TabItem value="windows" label="Windows">
-
-En Windows, descarga y ejecuta [rustup-init.exe](https://static.rust-lang.org/rustup/dist/i686-pc-windows-gnu/rustup-init.exe). Puedes continuar con la configuración predeterminada presionando Enter.
-
-:::tip
-
-El Stellar CLI usa emojis en su salida. Para renderizarlos correctamente en Windows, se recomienda usar el [Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal/). Consulta [cómo instalar Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal/install) en Microsoft Learn. Si se usa la CLI en la ventana de comandos de Windows o en PowerShell, funcionará como se espera, pero los emojis aparecerán como signos de interrogación.
-
-:::
-
-Si ya estás usando [WSL](https://learn.microsoft.com/en-us/windows/wsl/install), también puedes seguir las instrucciones para Linux.
-
-</TabItem>
-<TabItem value="other" label="Otro">
-
-Para otros métodos de instalación de [Rust], consulta: https://www.rust-lang.org/tools/install
-
-</TabItem>
-</Tabs>
-
-Los contratos inteligentes Stellar requieren **Rust toolchain v1.84.0 o superior**, ya que el objetivo `wasm32v1-none` solo está disponible en versiones recientes.
-
-Para comprobar tu versión:
-
-```sh
-rustc --version
-```
-
-Si necesitas actualizar:
-
-```sh
-rustup update stable
-```
-
-## Instalar el objetivo
-
-You'll need a "target" for which your smart contract will be compiled. Para Rust `v1.84.0` o superior, instala el target `wasm32v1-none`.
-
-```sh
-rustup target add wasm32v1-none
-```
-
-:::note
-
-Cuando instalas Rust, el objetivo de WebAssembly se instala por cada toolchain. Si actualizas tu versión de Rust, deberás reinstalar el objetivo `wasm32v1-none` para la nueva toolchain.
-
-:::
-
-Puedes aprender más sobre los detalles que aporta este target en nuestra página dedicada al [dialecto Stellar Rust](../../../learn/fundamentals/contract-development/rust-dialect.mdx#limited-webassembly-features). Esta página describe el subconjunto de funcionalidades de Rust que tienes disponibles dentro del entorno de contratos inteligentes de Stellar.
-
-## Configurar un editor
-
-Many editors have support for Rust. Visit the following link to find out how to configure your editor: https://www.rust-lang.org/tools
-
-Estas son las herramientas que necesitas para configurar tu editor:
-
-1. [Visual Studio Code](https://code.visualstudio.com) como editor de código (u otro editor que soporte Rust)
-2. [Rust Analyzer](https://marketplace.visualstudio.com/items?itemName=rust-lang.rust-analyzer) para soporte del lenguaje Rust
-3. [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) para depuración paso a paso
-
-## Install the Stellar CLI
-
-The [Stellar CLI](https://github.com/stellar/stellar-cli) can execute smart contracts on futurenet, testnet, mainnet, as well as in a local sandbox.
-
-:::info
-
-La última versión estable es [v{latestVersion}](https://github.com/stellar/stellar-cli/releases/latest).
-
-:::
-
-### Install
-
-There are a few ways to install the [latest release](https://github.com/stellar/stellar-cli/releases) of Stellar CLI.
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS">
-
-Instalar usando script (macOS, Linux):
-
-```sh
-curl -fsSL https://github.com/stellar/stellar-cli/raw/main/install.sh | sh
-```
-
-Install with Homebrew (macOS, Linux):
-
-```sh
-brew install stellar-cli
-```
-
-Install with cargo from source:
-
-<StellarCliVersion />
-
-</TabItem>
-<TabItem value="linux" label="Linux">
-
-Instalar usando script (macOS, Linux):
-
-```sh
-curl -fsSL https://github.com/stellar/stellar-cli/raw/main/install.sh | sh
-```
-
-Instalar con Homebrew (macOS, Linux):
-
-```sh
-brew install stellar-cli
-```
-
-Install with cargo from source:
-
-<StellarCliVersion />
-
-:::note
-
-Instalar desde el código fuente requiere un sistema de compilación en C. Para instalar un sistema de compilación en C en Debian/Ubuntu, usa:
-
-```
-sudo apt update && sudo apt install -y build-essential
-```
-
-:::
-
-</TabItem>
-<TabItem value="windows" label="Windows">
-
-Using the installer:
-
-1. Download the installer from the <a href={getStellarCliLatestReleaseUrl()}>latest release</a>.
-2. Go to your Downloads folder, double click the installer and follow the wizard instructions.
-3. Restart your terminal to use the `stellar` command.
-
-Using [winget](https://learn.microsoft.com/en-us/windows/package-manager/winget/):
-
-<StellarCliWingetVersion />
-
-Instalar con cargo desde el código fuente:
-
-<StellarCliVersion />
-
-</TabItem>
-</Tabs>
-
-:::info
-
-Report issues and share feedback about the Stellar CLI [here](https://github.com/stellar/stellar-cli/issues/new/choose).
-
-:::
-
-### Documentation
-
-La documentación de referencia completa autogenerada está disponible [aquí](../../../tools/cli/stellar-cli.mdx).
-
-### Autocompletion
-
-You can use `stellar completion` to generate shell completion for different shells. You should absolutely try it out. It will feel like a super power!
-
-<Tabs id="shell" defaultValue={getShell()}>
-
-<TabItem value="bash" label="Bash">
-
-Para habilitar el autocompletado en la sesión actual del shell:
-
-```sh
-source <(stellar completion --shell bash)
-```
-
-To enable autocomplete permanently, run the following command, then restart your terminal:
-
-```sh
-echo "source <(stellar completion --shell bash)" >> ~/.bashrc
-```
-
-</TabItem>
-
-<TabItem value="zsh" label="ZSH">
-
-Para habilitar el autocompletado en la sesión actual del shell:
-
-```sh
-source <(stellar completion --shell zsh)
-```
-
-To enable autocomplete permanently, run the following commands, then restart your terminal:
-
-```sh
-echo "source <(stellar completion --shell zsh)" >> ~/.zshrc
-```
-
-</TabItem>
-
-<TabItem value="fish" label="fish">
-
-To enable autocomplete on the current shell session:
-
-```sh
-stellar completion --shell fish | source
-```
-
-To enable autocomplete permanently, run the following command, then restart your terminal:
-
-```sh
-echo "stellar completion --shell fish | source" >> ~/.config/fish/config.fish
-```
-
-</TabItem>
-
-<TabItem value="powershell" label="PowerShell">
-
-Para habilitar el autocompletado en la sesión actual del shell:
-
-```powershell
-stellar completion --shell powershell | Out-String | Invoke-Expression
-```
-
-To enable autocomplete permanently, run the following commands, then restart your terminal:
-
-```powershell
-New-Item -ItemType Directory -Path $(Split-Path $PROFILE) -Force
-if (-Not (Test-Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE | Out-Null }
-Add-Content $PROFILE 'Set-PSReadlineKeyHandler -Key Tab -Function MenuComplete'
-Add-Content $PROFILE 'stellar completion --shell powershell | Out-String | Invoke-Expression'
-```
-
-:::tip
-
-If you get an error like `cannot be loaded because running scripts is disabled on this system`, you may need to change your [Execution Policy](https:/go.microsoft.com/fwlink/?LinkID=135170) with `Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser`. **Before running this command, be sure you understand the implications of doing so.**
-
-:::
-
-</TabItem>
-
-<TabItem value="elvish" label="Elvish">
-
-Para habilitar el autocompletado en la sesión actual del shell:
-
-```sh
-source (stellar completion --shell elvish)
-```
-
-Para habilitar el autocompletado de forma permanente, ejecuta los siguientes comandos y luego reinicia tu terminal:
-
-```sh
-echo "source (stellar completion --shell elvish)" >> ~/.elvish/rc.elv
-```
-
-</TabItem>
-
-</Tabs>
-
-[rust]: https://www.rust-lang.org/
-[stellar cli]: #install-the-stellar-cli
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/storing-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/storing-data.mdx
deleted file mode 100644
index 484eef3010..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/getting-started/storing-data.mdx
+++ /dev/null
@@ -1,204 +0,0 @@
----
-sidebar_position: 30
-title: Escribir un contrato inteligente para almacenar y recuperar datos con el ejemplo de incremento
-sidebar_label: 3. Almacenar Datos
-description: Sigue el ejemplo de incremento para escribir un contrato sencillo que almacene y recupere datos en la red Stellar. Aprende sobre el almacenamiento y TTL.
----
-
-# 3. Almacenar datos
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-Ahora que hemos desarrollado un contrato básico de Hola Mundo, escribiremos un contrato simple que almacene y recupere datos. Esto te ayudará a ver los fundamentos del sistema de almacenamiento de Soroban.
-
-Esto va a seguir junto con el [ejemplo de incremento](https://github.com/stellar/soroban-examples/tree/v22.0.1/increment), que tiene una sola función que incrementa un contador interno y devuelve el valor. Si quieres ver un ejemplo en funcionamiento, [pruébalo en Devcontainers](https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web).
-
-Este tutorial asume que ya has completado los pasos anteriores en Comenzar: [Configuración](./setup.mdx), [Hola Mundo](./hello-world.mdx), y [Desplegar en Testnet](./deploy-to-testnet.mdx).
-
-## Agregar el contrato de incremento
-
-Además de crear un nuevo proyecto, el comando `stellar contract init` también nos permite inicializar un nuevo espacio de trabajo de contrato dentro de un proyecto existente. En este ejemplo, vamos a inicializar un nuevo contrato y usar el indicador `--name` para especificar el nombre de nuestro nuevo contrato, `increment`.
-
-Este comando no sobrescribirá archivos existentes a menos que pasemos explícitamente el indicador `--overwrite`. Desde nuestro directorio `soroban-hello-world`, ejecuta:
-
-```sh
-stellar contract init . --name increment
-```
-
-Esto crea un nuevo directorio `contracts/increment` con código de marcador de posición en `src/lib.rs` y `src/test.rs`, que reemplazaremos con nuestro nuevo contrato de incremento y las pruebas correspondientes.
-
-```
-└── contracts
-    ├── increment
-        ├── Cargo.toml
-        ├── Makefile
-        └── src
-            ├── lib.rs
-            └── test.rs
-```
-
-Pasaremos por el código del contrato con más detalle a continuación, pero por ahora, reemplaza el código de marcador de posición en `contracts/increment/src/lib.rs` con lo siguiente.
-
-```rust
-#![no_std]
-use soroban_sdk::{contract, contractimpl, log, symbol_short, Env, Symbol};
-
-const COUNTER: Symbol = symbol_short!("COUNTER");
-
-#[contract]
-pub struct IncrementContract;
-
-#[contractimpl]
-impl IncrementContract {
-    /// Increment increments an internal counter, and returns the value.
-    pub fn increment(env: Env) -> u32 {
-        let mut count: u32 = env.storage().instance().get(&COUNTER).unwrap_or(0);
-        log!(&env, "count: {}", count);
-
-        count += 1;
-        env.storage().instance().set(&COUNTER, &count);
-        env.storage().instance().extend_ttl(50, 100);
-
-        count
-    }
-}
-
-mod test;
-```
-
-### Importaciones
-
-Este contrato comienza de manera similar a nuestro contrato de Hola Mundo, con una anotación para excluir la biblioteca estándar de Rust, e importaciones de los tipos y macros que necesitamos del crate `soroban-sdk`.
-
-```rust title="contracts/increment/src/lib.rs"
-#![no_std]
-use soroban_sdk::{contract, contractimpl, log, symbol_short, Env, Symbol};
-```
-
-### Claves de Datos del Contrato
-
-```rust
-const COUNTER: Symbol = symbol_short!("COUNTER");
-```
-
-Los datos del contrato están asociados con una clave, que se puede usar más tarde para buscar el valor.
-
-`Symbol` es un tipo de cadena corto (de hasta 32 caracteres de longitud) con espacio de caracteres limitado (solo se permiten caracteres `a-zA-Z0-9_`). Los identificadores como nombres de funciones del contrato y claves de datos del contrato están representados por `Symbol`s.
-
-El macro `symbol_short!()` es una forma conveniente de pre-computar símbolos cortos de hasta 9 caracteres de longitud en el tiempo de compilación usando `Symbol::short`. Genera una constante de tiempo de compilación que se adhiere al conjunto de caracteres válidos de letras (a-zA-Z), números (0-9) y guiones bajos (\_). Si un símbolo excede el límite de 9 caracteres, se debe utilizar `Symbol::new` para crear símbolos en tiempo de ejecución.
-
-### Acceso a Datos del Contrato
-
-```rust
-let mut count: u32 = env
-    .storage()
-    .instance()
-    .get(&COUNTER)
-    .unwrap_or(0); // If no value set, assume 0.
-```
-
-La función `Env.storage()` se utiliza para acceder y actualizar los datos del contrato. El contrato que se ejecuta es el único contrato que puede consultar o modificar los datos del contrato que ha almacenado. Los datos almacenados son visibles en el ledger donde sea que el ledger sea visible, pero los contratos que se ejecutan dentro del entorno Soroban están restringidos a sus propios datos.
-
-La función `get()` obtiene el valor actual asociado con la clave del contador.
-
-Si no hay un valor almacenado actualmente, se devuelve el valor dado a `unwrap_or(...)` en su lugar.
-
-Los valores almacenados como datos del contrato y recuperados se transmiten desde [el entorno](../../../learn/fundamentals/contract-development/environment-concepts.mdx) y se expanden al tipo especificado. En este caso, un `u32`. Si el valor se puede expandir, el tipo devuelto será un `u32`. De lo contrario, si un desarrollador lo convierte en algún otro tipo, ocurriría un pánico en el unwrap.
-
-```rust
-env.storage()
-    .instance()
-    .set(&COUNTER, &count);
-```
-
-La función `set()` almacena el nuevo valor del contador contra la clave, reemplazando el valor existente.
-
-### Gestionar TTLs de Datos del Contrato con `extend_ttl()`
-
-```rust
-env.storage().instance().extend_ttl(100, 100);
-```
-
-Todos los datos del contrato tienen un Tiempo de Vida (TTL), medido en ledgers, que debe ser extendido periódicamente. Si el TTL de una entrada no se extiende periódicamente, la entrada finalmente se convertirá en "archivada" Puedes aprender más sobre esto en el documento de [Archivado de Estado](../../../learn/fundamentals/contract-development/storage/state-archival.mdx).
-
-Por ahora, vale la pena saber que hay tres tipos de almacenamiento: `Persistente`, `Temporal`, y `Instancia`. Este contrato solo utiliza almacenamiento `Instance`: `env.storage().instance()`. Cada vez que se incrementa el contador, el TTL de este almacenamiento se extiende por 100 [ledgers](../../../learn/fundamentals/stellar-data-structures/ledgers.mdx), o alrededor de 500 segundos. Cada vez que se incrementa el contador, el TTL de este almacenamiento se extiende por 100 [ledgers](../../../learn/fundamentals/stellar-data-structures/ledgers.mdx), o aproximadamente 500 segundos.
-
-### Construir el contrato
-
-Desde dentro de `soroban-hello-world`, ejecuta:
-
-```sh
-stellar contract build
-```
-
-Verifica que se haya construido:
-
-```bash
-ls target/wasm32v1-none/release/*.wasm
-```
-
-Deberías ver tanto `hello_world.wasm` como `increment.wasm`.
-
-## Pruebas
-
-Reemplaza el código de marcador de posición en `contracts/increment/src/test.rs` con el siguiente código de prueba de incremento.
-
-```rust title="contracts/increment/src/test.rs"
-#![cfg(test)]
-use crate::{IncrementContract, IncrementContractClient};
-use soroban_sdk::Env;
-
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(IncrementContract, ());
-    let client = IncrementContractClient::new(&env, &contract_id);
-
-    assert_eq!(client.increment(), 1);
-    assert_eq!(client.increment(), 2);
-    assert_eq!(client.increment(), 3);
-}
-```
-
-Esto utiliza los mismos conceptos descritos en el ejemplo de Hola Mundo.
-
-Asegúrate de que pase:
-
-```sh
-cargo test
-```
-
-Verás que esto ejecuta pruebas para todo el espacio de trabajo; tanto el contrato de Hola Mundo como el nuevo contrato de Incremento.
-
-Si quieres ver la salida de la llamada a `log!`, ejecuta las pruebas con `--nocapture`:
-
-```
-cargo test -- --nocapture
-```
-
-Deberías ver los eventos de registro de diagnóstico con los datos de conteo en la salida:
-
-```
-running 1 test
-[Diagnostic Event] contract:CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD2KM,
-    topics:[log],
-    data:["count: {}", 1]
-[Diagnostic Event] contract:CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD2KM,
-    topics:[log],
-    data:["count: {}", 2]
-[Diagnostic Event] contract:CAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD2KM,
-    topics:[log],
-    data:["count: {}", 3]
-test test::test ... ok
-```
-
-## Llevarlo más lejos
-
-¿Puedes averiguar cómo agregar la función `get_current_value` al contrato? ¿Qué tal funciones `decrement` o `reset`?
-
-## Resumen
-
-En esta sección, agregamos un nuevo contrato a este proyecto, que utilizó las capacidades de almacenamiento de Soroban para almacenar y recuperar datos. También aprendimos sobre los diferentes tipos de almacenamiento y cómo gestionar sus TTLs.
-
-A continuación aprenderemos un poco más sobre cómo desplegar contratos en la red Testnet de Soroban e interactuar con nuestro contrato incrementador usando la CLI.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/overview.mdx
deleted file mode 100644
index 166a6a9bcf..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/build/smart-contracts/overview.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 10
-title: Una visión general de los contratos inteligentes en Stellar, incluyendo el SDK de Rust y preguntas frecuentes
-sidebar_label: Introducción
-description: Una visión general de los contratos inteligentes de Stellar, incluyendo información sobre el SDK de Rust de Soroban, el entorno de host, y respuestas a preguntas generales que se hacen comúnmente.
----
-
-# Visión general
-
-Soroban es la plataforma de contratos inteligentes en la red Stellar. Estos contratos son pequeños programas escritos en el [lenguaje Rust](https://www.rust-lang.org/) y compilados como [WebAssembly](https://webassembly.org/) (Wasm) para su implementación.
-
-:::note
-
-Para una introducción completa a los smart contracts de Stellar, consulta la [Sección de Aprendizaje sobre Smart Contracts](../../learn/fundamentals/contract-development/overview.mdx).
-
-:::
-
-Escribe tu primer smart contract en Stellar usando la [Guía para Comenzar](./getting-started/setup.mdx).
-
-## Rust en Stellar
-
-Los contratos inteligentes de Stellar tienen varias características (como límites de recursos, consideraciones de seguridad y más) que obligan a los contratos a utilizar solo un subconjunto limitado del lenguaje completo de Rust y deben utilizar bibliotecas especializadas para la mayoría de las tareas.
-
-Aprende más en la [sección sobre el dialecto Rust para contratos](../../learn/fundamentals/contract-development/rust-dialect.mdx).
-
-En particular, la biblioteca estándar de Rust y la mayoría de las bibliotecas de terceros (llamadas [crates](../../learn/migrate/evm/solidity-and-rust-advanced-concepts#crates)) no estarán disponibles para su uso directo en contratos debido a las restricciones mencionadas anteriormente. Algunas crates pueden adaptarse para su uso en contratos, y otras pueden incorporarse al entorno host como objetos o funciones host.
-
-:::note
-
-Otros idiomas pueden ser admitidos en el futuro, pero en este momento, solo se admite Rust.
-
-:::
-
-## SDK de Rust de Soroban
-
-Los contratos se desarrollan utilizando un kit de desarrollo de software (SDK). El [SDK de Soroban Rust](../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk) consiste en un crate de Rust y una herramienta de línea de comandos (CLI).
-
-La crate del SDK actúa como sustituto de la biblioteca estándar de Rust, proporcionando estructuras de datos y funciones de utilidad para contratos, así como acceso a funcionalidades específicas de contratos inteligentes desde el entorno del contrato, como el hash criptográfico y la verificación de firmas, acceso a almacenamiento persistente on-chain, y localización e invocación de contratos secundarios a través de identificadores estables.
-
-La herramienta CLI del SDK de Soroban proporciona una interfaz orientada a desarrolladores para:
-
-- Compilar
-- Probar
-- Inspeccionando
-- Versionado
-- Desplegando
-
-También incluye una implementación completa del entorno host del contrato que es idéntica al que se ejecuta en la cadena, llamado [modo de prueba local](../../learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx#local-testing-mode). Con esta capacidad, los contratos pueden ejecutarse localmente en la estación de trabajo de un desarrollador y pueden ser probados y depurados directamente con un depurador local dentro de un IDE estándar, así como con un arnés de pruebas nativas para pruebas unitarias de retroalimentación rápida y pruebas de fuzz o de propiedades de alta velocidad.
-
-## Entorno host
-
-El entorno de ejecución es un conjunto de crates de Rust compilados en la herramienta SDK CLI y stellar-core. Comprende un conjunto de objetos y funciones host, una interfaz para el almacenamiento on-chain y la invocación de contratos, un sistema de contabilidad de recursos y cobros de tarifas, y un intérprete de Wasm.
-
-La mayoría de los desarrolladores de contratos no necesitarán interactuar frecuentemente con el entorno host directamente: las funciones del SDK envuelven la mayoría de sus instalaciones y proporcionan tipos y funciones más ricos y ergonómicos, pero es útil entender su estructura para comprender el modelo conceptual que presenta el SDK. Es probable que algunas partes del entorno host sean visibles al probar o depurar contratos compilados de forma nativa en una estación de trabajo local.
-
-Aprende más en la [sección Conceptos del Entorno](../../learn/fundamentals/contract-development/environment-concepts.mdx).
-
-## Preguntas frecuentes sobre smart contracts de Stellar
-
-<!-- prettier-ignore-start -->
-
-<details>
-  <summary>
-   **¿Qué es Soroban para Stellar? ¿Es una nueva blockchain?**
-  </summary>
-  Soroban no es una nueva blockchain. Soroban es una plataforma de contratos inteligentes
-  integrada en la blockchain Stellar existente. Es una función aditiva
-  que vive junto a las operaciones existentes de Stellar
-  y no las reemplaza.
-</details>
-<details>
-  <summary>
-   **¿Cómo invoco un contrato de Soroban en Stellar?**
-  </summary>
-  Invoca un contrato de Soroban enviando una transacción que contenga la nueva
-  operación:
-  [`InvokeHostFunctionOp`](../../learn/fundamentals/transactions/list-of-operations.mdx#invoke-host-function).
-</details>
-<details>
-  <summary>
-    **¿Pueden los contratos de Soroban usar cuentas de Stellar para autenticación?​**
-  </summary>
-  Sí. Las cuentas de Stellar se comparten con Soroban. Los contratos inteligentes tienen acceso a la configuración del firmante de la cuenta de Stellar y conocen la cuenta fuente que los invocó directamente en una transacción. Consulta la [sección de Autorización](../../learn/fundamentals/contract-development/authorization.mdx) para obtener más información.
-</details>
-<details>
-  <summary>
-   **¿Pueden los contratos de Soroban interactuar con activos de Stellar?​**
-  </summary>
-  Sí. Soroban contiene un [Contrato de Activos Stellar](../../tokens/stellar-asset-contract.mdx) integrado que puede interactuar con
-  líneas de confianza clásicas.
-</details>
-<details>
-  <summary>
-    **¿Los emisores de activos de Stellar mantienen autorización sobre un activo enviado a
-    un identificador no cuenta en Soroban (`AUTH_REQUIRED`, `AUTH_REVOCABLE`,
-    `AUTH_CLAWBACK`)​?**
-  </summary>
-  Sí. Los emisores retienen el mismo nivel de control en Soroban que tienen
-  regularmente. Esta funcionalidad es accesible a través de un conjunto de funciones de administración
-  (clawback, set_auth) en el Contrato de Activos Stellar integrado.
-</details>
-<details>
-  <summary>
-    **¿Pueden los contratos de Soroban interactuar con otras operaciones de Stellar?​**
-  </summary>
-  No. Aparte de las interacciones con cuentas y activos mencionadas anteriormente. Esto
-  significa que los contratos de Soroban no pueden interactuar con el SDEX, saldos reclamables o patrocinadores.
-</details>
-<details>
-  <summary>
-    **¿Se aplica la reserva base de Stellar a los contratos de Soroban?​**
-  </summary>
-  No. Soroban tiene una [estructura de tarifas](../../learn/fundamentals/fees-resource-limits-metering.mdx) diferente, y
-  las entradas de libro que son asignadas por los contratos de Soroban no se suman al
-  saldo mínimo requerido de una cuenta.
-</details>
-<details>
-  <summary>
-   **¿Necesitas ayuda para encontrar lo que buscas?​**
-  </summary>
-  Pregunta en los canales de Desarrolladores en el [Discord de Desarrolladores Stellar](https://discord.gg/stellardev).
-</details>
-<details>
-  <summary>
-    **¿Debo emitir mi token como un asset de Stellar o como un token de contrato de Soroban?​**
-  </summary>
-  En la mayor medida posible, recomendamos emitir tokens como assets de Stellar. Estos tokens se beneficiarán de ser interoperables con las herramientas existentes en el ecosistema Stellar y son más eficientes porque el
-  Contrato de Activos Stellar está integrado en el host. Lee más en la [Descripción general de los tokens](../../tokens/README.mdx).
-</details>
-<!-- prettier-ignore-end -->
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/CONTRIBUTING.md b/i18n/es/docusaurus-plugin-content-docs/current/data/CONTRIBUTING.md
deleted file mode 100644
index 1888ecb09b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/CONTRIBUTING.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# DETÉN LO QUE ESTÁS HACIENDO
-
-Si estás aquí para hacer algunas correcciones en la documentación de la API de Stellar (¡antes que nada, gracias!), probablemente no quieras estar en esta ubicación. La mayor parte de la documentación de la API ubicada aquí ha sido generada por los archivos `.yml` contenidos en el directorio `/openapi`. A menos que estés trabajando en algo que esté _fuera_ del directorio `/api/resources`, probablemente quieras revisar `/openapi` en lugar de aquí.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/README.mdx
deleted file mode 100644
index 677fb2b629..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/README.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Resumen de Datos
-sidebar_position: 0
----
-
-Hay varias productos para elegir al interactuar con la red Stellar, y cada uno está optimizado para diferentes patrones de acceso, por lo que es importante elegir la herramienta adecuada según tu caso de uso específico. Estas herramientas permiten a los usuarios consultar datos de la red, enviar transacciones e interactuar con contratos inteligentes sin necesidad de entender los detalles de bajo nivel de Stellar Core.
-
-Utiliza los resúmenes a continuación para determinar qué tipos de herramientas de datos son adecuadas para tu caso de uso.
-
-## [Analítica](./analytics/README.mdx)
-
-Explora y analiza los datos de la red Stellar para descubrir tendencias, rastrear actividades y generar conocimientos para la toma de decisiones y la elaboración de informes.
-
-**Por qué usarlo:**
-
-- Quieres información histórica y visualizaciones sobre la actividad de la red y la salud del ecosistema
-- No necesitas enviar transacciones a la red
-- No necesitas datos en tiempo real
-
-## [APIs](./apis/README.mdx)
-
-Conéctate a la red Stellar en tiempo real, permitiendo la recuperación de datos sin interrupciones, la presentación de transacciones y la integración de aplicaciones.
-
-**Por qué usarlo:**
-
-- Quieres desarrollar aplicaciones que interactúen con Stellar
-- Quieres acceso a datos en tiempo real y presentación y procesamiento de transacciones
-
-## [Indexadores](./indexers/README.mdx)
-
-Organiza y optimiza los datos de la blockchain Stellar para consultas eficientes, análisis más profundos y mejor accesibilidad.
-
-**Por qué usarlo:**
-
-- Quieres acceso estructurado y escalable a datos históricos y en tiempo real de la blockchain
-- Quieres acceso fácil a datos de ledger procesados y transformados para realizar consultas
-
-## [Oráculos](./oracles/README.mdx)
-
-Integra datos fuera de la cadena con la red Stellar, permitiendo que los contratos inteligentes y las aplicaciones descentralizadas interactúen con fuentes de información externas.
-
-**Por qué usarlo:**
-
-- Quieres usar datos fuera de la cadena junto con los contratos inteligentes de Stellar para ampliar la funcionalidad y la automatización
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/READ_FIRST.md b/i18n/es/docusaurus-plugin-content-docs/current/data/READ_FIRST.md
deleted file mode 100644
index f88df486f6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/READ_FIRST.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-draft: true
----
-
-# DEJA LO QUE ESTÁS HACIENDO
-
-Si estás aquí para hacer algunas correcciones a la documentación de la API de Stellar (primero, ¡gracias!), probablemente no quieras estar en esta ubicación. La mayor parte de la documentación de la API ubicada aquí ha sido generada por los archivos `.yml` contenidos en el directorio `/openapi`. A menos que estés trabajando en algo que esté _fuera_ del directorio `/api/resources`, probablemente querrás revisar en `/openapi` en lugar de aquí.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/README.mdx
deleted file mode 100644
index 6c33dfe63d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Visión general de análisis
-sidebar_position: 0
----
-
-Aprende sobre análisis y proveedores de análisis en la red Stellar
-
-## [Hubble](./hubble/README.mdx)
-
-Hubble es un almacén de datos BigQuery de solo lectura y de código abierto mantenido por SDF que proporciona un registro histórico completo de la red Stellar, ideal para el análisis a gran escala de transacciones, tarifas y tendencias de la red. No es adecuado para necesidades de datos en tiempo real o búsquedas simples, y su documentación se centra en análisis exploratorios, métodos de conexión y optimización de consultas. Al ofrecer un conjunto de datos estructurado y listo para consultas, Hubble permite a los usuarios explorar datos de la red Stellar sin gestionar tuberías de datos en bruto.
-
-Dentro de Hubble, el producto stellar-etl potencia la extracción y transformación de datos de la red Stellar en BigQuery. Este pipeline de código abierto permite a los desarrolladores extender o personalizar los flujos de trabajo de ingestión de datos según sus necesidades analíticas. Stellar-etl proporciona flexibilidad en cómo se procesan los datos, permitiendo a los usuarios extraer entradas de ledger específicas, operaciones o registros de eventos según sus requisitos.
-
-## [Proveedores de análisis de datos](./analytics-providers/analytics-providers.mdx)
-
-Los proveedores de análisis de datos proporcionan un registro histórico completo de los datos de la red Stellar de Pubnet para análisis y percepciones. Estas plataformas permiten a los usuarios explorar tendencias de la red, pero no están diseñadas para el acceso a datos en tiempo real o ejecución de transacciones. La diferencia clave es que estas plataformas del ecosistema operan de manera independiente de SDF y proporcionan métricas y tableros sobre la red Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/analytics-providers/analytics-providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/analytics-providers/analytics-providers.mdx
deleted file mode 100644
index d36be104c7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/analytics-providers/analytics-providers.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-sidebar_position: 1000
-title: Proveedores de Análisis de Datos
----
-
-La siguiente es una lista de plataformas de análisis de datos que hacen disponible un registro histórico completo de los datos de la red Stellar de Pubnet.
-
-| Plataforma     | Descripción                                                                                                                                                                                                                                                                                                                                                                | Página de inicio y Registro                                                                                                                                                        | Precios                                                                                                                                                                                         | Acceso a Datos                                                                                                                                                                                                                                | Acceso al Panel                                                                                                                                                                                     |
-| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Hubble         | SDF proporciona un conjunto de datos crudo disponible públicamente con un registro histórico completo de los datos de la red Stellar, actualizado cada 15 minutos.                                                                                                                                                                                                         | [Hubble](https://console.cloud.google.com/bigquery?project=crypto-stellar&ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar) <br></br> [Registro](https://cloud.google.com/?hl=en) | Los usuarios finales incurre en el costo de ejecutar consultas. Visita la página de [Precios de BigQuery](https://cloud.google.com/bigquery/pricing#analysis_pricing_models) para aprender más. | Por favor, consulta la [Guía del Analista](./hubble/analyst-guide) para más información.                                                                                                                                                      | N/D                                                                                                                                                                                                 |
-| Duna           | Conjunto de datos crudo para la red Stellar disponible en el portal Dune. Actualizado cada hora. Puedes comparar diferentes cadenas en la plataforma.                                                                                                                                                                                                                      | [Dune](https://dune.com/) <br></br>[Registro](https://dune.com/auth/register)                                                                                                      | Gratis para consultas más simples. Necesitas pagar por consultas complejas.                                                                                                                     | Para acceder a conjuntos de datos, haz clic [aquí](https://dune.com/queries?category=canonical&namespace=stellar).                                                                                                                            | Explora tableros de la comunidad, visión general de la red y conjuntos de datos [aquí](https://dune.com/blockchains/stellar).                                                                       |
-| Artemisa       | Conjunto de datos agregados para la red Stellar disponible en BigQuery así como en el portal Artemis. Proporciona tableros para comparar la actividad de la cadena Stellar con las cadenas del ecosistema.                                                                                                                                                                 | [Artemis](https://www.artemis.xyz/) <br></br>[Registro](https://app.artemisanalytics.com/artemis-terminal-auth?flow=SIGN_UP)                                                       | Tableros gratuitos. Necesitas pagar por acceder al conjunto de datos crudo.                                                                                                                     | Para acceder al conjunto de datos transformado del Stellar por Artemis, actualiza al plan empresarial y luego marca [este conjunto de datos](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1sartemis-bigquery-share!2sshared_us). | Explora los tableros de [comparación de cadenas](https://app.artemisanalytics.com/chains?selectedChains=stellar) y [actividad de aplicación](https://app.artemis.xyz/application-activity/stellar). |
-| Nansen         | Conjunto de datos agregados para la red Stellar disponible en el portal Nansen. Proporciona tableros para comparar la actividad de la cadena Stellar con las cadenas del ecosistema.                                                                                                                                                                                       | [Nansen](https://app.nansen.ai/) <br></br>[Registro](https://app.nansen.ai/auth/signup)                                                                                            | Tableros gratuitos. Necesitas pagar por acceder al conjunto de datos crudo.                                                                                                                     | Para acceder al conjunto de datos transformado del Stellar por Nansen, actualiza al plan Pioneer y luego marca [este conjunto de datos](https://console.cloud.google.com/bigquery?project=nansen-query).                                      | Explora [actividad de cadena, entidad y ecosistema](https://app.nansen.ai/macro/blockchains?chain=stellar&tab=overview).                                                                            |
-| Ortege         | Ortege ofrece servicios de datos para hacer que los datos de blockchain sean más accesibles a través de APIs en tiempo real y un [Lakehouse](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse) gestionado para la exploración analítica. El lakehouse sigue un esquema estandarizado a través de blockchains, lo que permite una integración sencilla entre L1s. | [Ortege](https://www.ortege.ai/) <br></br>[Registro](https://app.ortege.ai/register/form)                                                                                          | Gratis para consultas más simples, para cargas de trabajo más grandes, el usuario debe comprar créditos en el almacén                                                                           | Aquí hay un [enlace](https://docs.ortege.ai/en/ortege-products/ortege-lakehouse/data-catalog/in-house-datasets) a su catálogo de datos para el acceso a los datos.                                                                            | Explora paneles seleccionados [aquí](https://app.ortege.ai/dashboard/list/), o crea el tuyo propio                                                                                                  |
-| Flipside       | Acceso a un conjunto de datos crudo para ejecutar consultas, crear tableros y obtener inteligencia procesable sobre varios ecosistemas de criptomonedas. Flipside patrocina recompensas de análisis para incentivar el compartimiento de insights de código abierto así como misiones para desarrolladores.                                                                | [Flipside](https://flipsidecrypto.xyz/home/) <br></br>[Regístrate](https://flipsidecrypto.xyz/home/sign-up)                                                                        | El acceso completo a datos (crudos, tableros) es gratis.                                                                                                                                        | Para acceder al conjunto de datos, regístrate en Flipside y encuentra la base de datos "Stellar" en el [Flipside studio](https://flipsidecrypto.xyz/studio/).                                                                                 | Explora [tableros de la comunidad](https://flipsidecrypto.xyz/insights/dashboards?search=stellar).                                                                                                  |
-| DefiLlama      | Agregador de TVL para DeFi (Finanzas Descentralizadas).                                                                                                                                                                                                                                                                                                                    | [DefiLlama](https://defillama.com/)                                                                                                                                                | Acceso gratuito (código abierto) al panel de TVL                                                                                                                                                | Para el acceso a datos, consulta [API Docs](https://defillama.com/docs/api)                                                                                                                                                                   | Explora el [Tablero de TVL](https://defillama.com/chain/Stellar).                                                                                                                                   |
-| Messari        | Messari funciona como un centro central para la investigación y datos relacionados con la criptoeconomía. Con funciones personalizables y fáciles de usar.                                                                                                                                                                                                                 | [Messari](https://messari.io/)                                                                                                                                                     | Acceso gratuito a paneles y datos ([suscripción](https://messari.io/account/plan) para acceso avanzado)                                                                                         | Para acceso a datos, consulta la [Documentación de API](https://docs.messari.io/reference/introduction)                                                                                                                                       | Explora el [Portal Stellar](https://stellar.messari.io/).                                                                                                                                           |
-| rwa.xyz        | Información agregada sobre activos del mundo real tokenizados.                                                                                                                                                                                                                                                                                                             | [rwa.xyz](https://www.rwa.xyz/)                                                                                                                                                    | Acceso gratuito a paneles e información general de rwa                                                                                                                                          | Para acceso a datos, consulta la [Plataforma de Datos y API](https://app.rwa.xyz/platform-overview)                                                                                                                                           | Explora el [Panel Stellar](https://app.rwa.xyz/networks/stellar).                                                                                                                                   |
-| Token Terminal | Token Terminal es una plataforma de datos onchain completa enfocada en estandarizar datos financieros y alternativos para las blockchains y aplicaciones descentralizadas más usadas.                                                                                                                                                                                      | [Token Terminal](https://tokenterminal.com/)                                                                                                                                       | Acceso gratuito a paneles. Acceso de pago a la [API](https://tokenterminal.com/explorer/account/api)                                                                                            | Para acceso a datos, consulta la [Documentación de API](https://tokenterminal.com/docs/api-reference/introduction)                                                                                                                            | Explora el [Panel Stellar](https://tokenterminal.com/explorer/projects/stellar).                                                                                                                    |
-| SonarX         | SonarX ofrece un todo en uno para datos indexados de Stellar.                                                                                                                                                                                                                                                                                                              | [SonarX](https://www.sonarx.com/)                                                                                                                                                  | Acceso de pago a conjuntos de datos crudos y seleccionados.                                                                                                                                     | Hay dos productos para acceso a datos, [Datos en Tiempo Real](https://www.sonarx.com/product/realtime) y [Streaming Histórico](https://www.sonarx.com/product/historical)                                                                     | N/A                                                                                                                                                                                                 |
-| Range          | La plataforma de seguridad e inteligencia blockchain; ayudando a los mejores equipos a desarrollar y usar protocolos DeFi, blockchains, rollups y puentes cross-chain con tranquilidad.                                                                                                                                                                                    | [Range](https://www.range.org/)                                                                                                                                                    | Acceso gratuito a análisis. Acceso de pago a APIs y Productos de Seguridad                                                                                                                      | Stellar tiene su propia [Página Principal](https://stellar.range.org/) y también estamos destacados en su explorador de [Stable Coin](https://stable.range.org/).                                                                             | Explora el [Panel de Stellar](https://stellar.range.org/).                                                                                                                                          |
-
-<!-- El inicio de sesión en Allium no funciona al momento de escribir este documento
-| Allium | Acceso a conjuntos de datos crudos de la red Stellar. | [Allium](https://www.allium.so/) | Acceso gratuito a datos y consultas | Para acceso a datos, consulta [Documentación de Allium](https://docs.allium.so/) | N/A | -->
-
-## Ejecutar tu propio Hubble
-
-Si estás interesado en ejecutar tu propio Hubble, por favor consulta la [Guía del Desarrollador](./hubble/developer-guide).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/README.mdx
deleted file mode 100644
index e845e85ae2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/README.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Hubble
-sidebar_position: 0
----
-
-## ¿Qué es Hubble?
-
-Hubble es un conjunto de datos open-source, disponible públicamente, que proporciona un registro histórico completo de la red Stellar. Ingiere y presenta los datos producidos por la red Stellar en un formato que es más fácil de consumir que las representaciones de datos orientadas al rendimiento usadas por Stellar Core. El conjunto de datos se aloja en BigQuery, lo que significa que es adecuado para cargas de trabajo analíticas grandes, recuperación de datos históricos y agregación de datos complejos. **Hubble no debe usarse para la recuperación de datos en tiempo real y no puede enviar transacciones a la red.** Para casos de uso en tiempo real, recomendamos [ejecutar un servidor API](../../apis/rpc/admin-guide/README.mdx).
-
-Esta guía describe cuándo usar Hubble y cómo conectarse. Para ver las estructuras de datos subyacentes, consultas y ejemplos, utiliza los tutoriales de [Visualización de Metadatos](./analyst-guide/viewing-metadata.mdx) y [Optimización de Consultas](./analyst-guide/optimizing-queries.mdx).
-
-## ¿Por qué usar Hubble?
-
-Algunas preguntas son difíciles de responder con la API RPC ya que su API es bastante mínima. Esto se debe a que su infraestructura está optimizada para lecturas y escrituras rápidas para poder procesar transacciones en línea.
-
-Aquí es donde entra Hubble. Está optimizado para ejecutar consultas complejas y escanear grandes cantidades de datos. Hubble puede almacenar órdenes de magnitud más datos que RPC y no enfrentará limitaciones de almacenamiento. Consultas que requieren paginación en RPC o que se agotan pueden ser devueltas en una única consulta. Hubble permite a los usuarios explorar, analizar y obtener conclusiones significativas de los datos sin la carga de mantener una base de datos.
-
-Los usuarios deben estar al tanto de las siguientes limitaciones:
-
-- Hubble es de solo lectura; no puede interactuar con la red Stellar.
-- La base de datos se actualiza en lotes intradía. No hay garantía de disponibilidad de datos el mismo día.
-- El SDF aloja una instancia pública de Hubble, y los usuarios finales incurren en el costo de ejecutar consultas. Visita la [Página de Precios de BigQuery](https://cloud.google.com/bigquery/pricing#analysis_pricing_models) para aprender más.
-
-## Por qué elegimos BigQuery
-
-BigQuery es el almacén de datos de Google Cloud que viene con algunas características clave que satisfacen las necesidades analíticas de Stellar.
-
-Primero, BigQuery permite que cualquier persona ponga un conjunto de datos a disposición del público. Esto significa que el SDF puede contribuir con repositorios open-source para crear y mantener un almacén de datos y también alojar una instancia pública.
-
-BigQuery también separa almacenamiento de computación, lo que lo hace sostenible para alojar una instancia pública. El mantenedor solo tiene que pagar el costo del almacenamiento sin incurrir en el costo del análisis que se ejecuta sobre el conjunto de datos.
-
-Lo más importante es que BigQuery es la plataforma de facto para conjuntos de datos de blockchain. Al seleccionar BigQuery, los datos de la red Stellar se encuentran con otros datos de blockchain, lo que permite análisis entre cadenas.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/README.mdx
deleted file mode 100644
index e8ab0fa24a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Guía del Analista
-sidebar_position: 15
----
-
-import DocCardList from "@theme/DocCardList";
-
-Todo lo que necesitas saber para usar los datos de Hubble para análisis.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/_category_.json
deleted file mode 100644
index 9e3a55f459..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/connecting.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/connecting.mdx
deleted file mode 100644
index 8725532fb0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/connecting.mdx
+++ /dev/null
@@ -1,144 +0,0 @@
----
-title: Conectar
-sidebar_position: 10
----
-
-BigQuery ofrece múltiples métodos de conexión a Hubble. Esta guía detalla tres métodos comunes:
-
-- [Interfaz de usuario de BigQuery](#bigquery-ui) - analistas que necesitan realizar análisis ad hoc usando SQL
-- [SDK de BigQuery](#bigquery-sdk) - desarrolladores que necesitan integrar datos en aplicaciones
-- [Looker Studio](#looker-studio) - personas de negocios que necesitan visualizar datos
-
-## Requisitos previos
-
-Para acceder a Hubble, necesitarás un proyecto de Google Cloud con facturación y la API de BigQuery habilitada. Para más información, sigue las instrucciones proporcionadas por [Google Cloud](https://cloud.google.com/bigquery/docs/quickstarts/query-public-dataset-console).
-
-Google proporciona un Sandbox de BigQuery de forma gratuita que permite a los usuarios explorar conjuntos de datos con capacidad limitada.
-
-## Interfaz de usuario de BigQuery
-
-1. Desde un navegador, abre el conjunto de datos [crypto-stellar.crypto_stellar](http://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar).
-2. Esto abrirá el conjunto de datos público `crypto_stellar`, donde puedes explorar su contenido en el panel de **Explorador**.
-3. Haz clic en el icono de **estrella** en el panel de Explorador. Esto marcará el conjunto de datos como favorito para ti. La información más detallada sobre marcar recursos como favoritos se puede encontrar [aquí](https://cloud.google.com/bigquery/docs/bigquery-web-ui#star_resources).
-
-:::note
-
-¡Hubble no se puede encontrar desde el panel de Explorador! No puedes buscar el conjunto de datos. Para ver el conjunto de datos, **debes** usar el [enlace del conjunto de datos](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar).
-
-:::
-
-Copia y pega la siguiente consulta de ejemplo en el Editor:
-
-<CodeExample>
-
-```sql
-select
-  account_id,
-  balance
-from `crypto-stellar.crypto_stellar.accounts_current`
-order by balance desc;
-```
-
-</CodeExample>
-
-Esta consulta devolverá los saldos de XLM para todas las direcciones de billeteras Stellar, ordenados de mayor a menor cantidad.
-
-## SDK de BigQuery
-
-Hay múltiples [Bibliotecas de clientes de la API de BigQuery](https://cloud.google.com/bigquery/docs/reference/libraries) disponibles.
-
-El siguiente ejemplo utiliza Python para acceder al conjunto de datos Hubble. Usa [esta guía](https://cloud.google.com/python/docs/setup) para ayuda en la configuración de un entorno de desarrollo en Python.
-
-Instala la biblioteca cliente localmente y configura tu entorno para usar tu proyecto de Google Cloud:
-
-<CodeExample>
-
-```bash
-# verify python version
-python3 --version
-# if you do not have pip, install it
-python -m pip install --upgrade pip
-
-# install bigquery client library
-pip install --upgrade google-cloud-bigquery
-gcloud config set project PROJECT_ID
-```
-
-</CodeExample>
-
-Usa el intérprete de Python para ejecutar el siguiente ejemplo y listar las tablas disponibles en Hubble:
-
-<CodeExample>
-
-```python
-from google.cloud import bigquery
-
-# Construct a BigQuery client object.
-client = bigquery.Client()
-
-dataset_id = 'crypto-stellar.crypto_stellar'
-
-# Make an API request
-tables = client.list_tables(dataset_id)
-
-# List the tables found in Hubble
-print(f'Tables contained in {dataset_id}':)
-for table in tables:
-    print(f'{table.project}.{table.dataset_id}.{table.table_id}')
-```
-
-</CodeExample>
-
-Ejecuta el siguiente ejemplo para realizar una consulta y imprimir los resultados:
-
-<CodeExample>
-
-```python
-from google.cloud import bigquery
-
-# Construct a BigQuery client object.
-client = bigquery.Client()
-
-query = """
-SELECT
- account_id,
- balance,
-FROM `crypto-stellar.crypto_stellar.accounts_current`
-ORDER BY balance DESC
-LIMIT 10;
-"""
-
-# Make an API request
-query_job = client.query(query)
-
-print("The query data:")
-for row in query_job:
-    # Row values can be accessed by field name or index.
-    print(f'account_id={row[0]}, balance={row["balance"]}')
-```
-
-</CodeExample>
-
-Hay varias maneras de extraer y cargar datos usando BigQuery. Consulta la [Documentación del cliente de BigQuery](https://cloud.google.com/python/docs/reference/bigquery/latest/google.cloud.bigquery.client) para más información.
-
-## Looker Studio
-
-[Looker Studio](https://cloud.google.com/looker-studio) es una herramienta de inteligencia empresarial que se puede usar para conectar y visualizar datos del conjunto de datos Hubble.
-
-Para conectar Hubble como fuente de datos:
-
-1. Abre [Looker Studio](https://lookerstudio.google.com/)
-2. Haz clic en **Crear** > **Fuente de Datos**
-3. Busca el conector de BigQuery
-4. _(Opcional)_ Cambia el nombre de la fuente de datos en la parte superior de la página web
-5. Haz clic en _Proyectos Compartidos_ > Selecciona tu proyecto de Google Cloud
-6. Introduce `crypto-stellar` como el nombre del Proyecto Compartido
-7. Haz clic en el Conjunto de Datos `crypto_stellar`
-8. Selecciona la tabla deseada para conectar
-9. Haz clic en `CONECTAR` en la parte superior derecha de la página web.
-
-¡Y estás conectado!
-
-Se puede encontrar información general sobre Looker Studio [aquí](https://support.google.com/looker-studio/).
-
-Se puede encontrar información general sobre conectar fuentes de datos [aquí](https://support.google.com/looker-studio/topic/6370331?hl=en&ref_topic=7441382&sjid=14945902445646860578-NA).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/creating-visualizations.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/creating-visualizations.mdx
deleted file mode 100644
index ff19daf19e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/creating-visualizations.mdx
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: Crear Visualizaciones
-sidebar_position: 40
----
-
-import hubble_visualization_demo from "/img/hubble/hubble_visualizatoin_demo.gif";
-import create_data_source from "/img/hubble/create-data-source.png";
-import bq_connector from "/img/hubble/bq-connector.png";
-import add_contract_data from "/img/hubble/add-contract-data.png";
-import create_report from "/img/hubble/create-report.png";
-import select_data_sources from "/img/hubble/select-data-sources.png";
-import add_pie_chart from "/img/hubble/add-pie-chart.png";
-import pie_contract_data from "/img/hubble/pie-contract-data.png";
-import pie_config from "/img/hubble/pie-config.png";
-import pie_chart_durability from "/img/hubble/pie_chart_durability.png";
-import click_add_data from "/img/hubble/click_add_data.png";
-import add_custom_query from "/img/hubble/add-custom-query.png";
-import add_column_chart from "/img/hubble/add-column-chart.png";
-import column_chart_config from "/img/hubble/column-chart-config.png";
-import expired_entry_column_chart from "/img/hubble/expired-entry-column-chart.png";
-import add_quick_filter from "/img/hubble/add-quick-filter.png";
-import filter_contract from "/img/hubble/filter-contract.png";
-import persistent_only from "/img/hubble/persistent-only.png";
-import filtered_report from "/img/hubble/filtered-report.png";
-
-Esta página mostrará cómo puedes crear visualizaciones con Hubble y [Google Looker Studio](https://cloud.google.com/looker-studio?hl=en).
-
-Al final del tutorial, habrás creado dos gráficos que ayudarán a visualizar la distribución de entradas de datos de contrato temporales frente a persistentes y su caducidad.
-
-<img src={hubble_visualization_demo} width="1000" />
-
-Como puedes ver, las entradas de datos de contratos persistentes representan aproximadamente el 25% de todas las entradas de datos de contratos, siendo el resto temporales. También hay muchas más entradas de datos de contrato temporales que han caducado. Esto es esperado porque las entradas temporales no pueden ser reemplazadas, mientras que las persistentes pueden ser reemplazadas/restauradas. Para obtener más información, puedes leer sobre [Archivo de estado y el ciclo de vida de los datos del contrato](../../../../learn/fundamentals/contract-development/storage/state-archival.mdx#contract-data-type-descriptions).
-
-## Condiciones Previas
-
-1. Asegúrate de que te has conectado a Hubble siguiendo las instrucciones en la página de [Conexión](../developer-guide/connecting-to-bigquery/README.mdx)
-2. Tienes acceso a [Google Looker Studio](https://cloud.google.com/looker-studio?hl=en)
-3. Has leído y entiendes las [prácticas recomendadas](./optimizing-queries.mdx#best-practices) generales para consultar datos en BigQuery
-
-## Crear un Informe en Looker Studio
-
-### Adjuntar Fuentes de Datos a Looker Studio
-
-1. Selecciona `Crear --> Fuente de datos`
-
-<img src={create_data_source} width="200" />
-
-2. Encuentra y selecciona el `Conector de Google BigQuery`
-
-<img src={bq_connector} width="300" />
-
-3. Encuentra las tablas deseadas a las que quieras conectar. Para este ejemplo, querrás añadir una fuente de datos para:
-   1. `crypto-stellar.crypto_stellar.contract_data`
-
-<img src={add_contract_data} width="600" />
-
-### Crear un Nuevo Informe (Tablero)
-
-1. Seleccionar `Crear --> Informe`
-
-<img src={create_report} width="200" />
-
-2. Añade tus fuentes de datos de arriba
-
-<img src={select_data_sources} width="300" />
-
-3. Inserta un `Gráfico de Tarta`
-
-<img src={add_pie_chart} width="200" />
-
-4. Elige `contract_data` como la `Fuente de datos`
-
-<img src={pie_contract_data} width="300" />
-
-5. Elige `closed_at` como la `Dimensión de Rango de Fechas` y `contract_durability` como la `Dimensión`
-
-<img src={pie_config} width="300" />
-
-6. Ahora deberías tener un gráfico de tarta que muestra el porcentaje de Durabilidad de Datos de Contrato Temporales frente a Persistentes
-
-<img src={pie_chart_durability} width="500" />
-
-### Usar SQL Personalizado para Crear un Gráfico
-
-1. En tu informe, haz clic en `Añadir Datos`, que estará cerca de la parte inferior derecha de tu ventana
-
-<img src={click_add_data} width="500" />
-
-2. Selecciona `BigQuery` y elige `CONSULTA PERSONALIZADA` y selecciona tu `Proyecto de Facturación` deseado donde se cobrará la consulta
-
-<img src={add_custom_query} width="500" />
-
-3. Añade la siguiente consulta y haz clic en `Añadir`
-
-```sql
--- Find the latest ledger sequence within Hubble.
--- This may be slightly behind the actual Stellar latest ledger
--- because Hubble is scheduled to run and insert data at 10 minute intervals
-with latest_ledger_in_hubble as (
-  select
-    max(sequence) as latest_ledger_sequence
-  from `crypto-stellar.crypto_stellar.history_ledgers`
-),
-
--- Find all the ttl that have expired
-expired_ttl as (
-  select
-    key_hash
-    , live_until_ledger_seq
-    -- Saving the date to aggregate on at the final step of the query
-    , date(closed_at) as ledger_date
-  from `crypto-stellar.crypto_stellar_dbt.ttl_current`
-  where true
-    -- Filter for expired entries only with the use of latest_ledger_sequence
-    and live_until_ledger_seq < (select latest_ledger_sequence from latest_ledger_in_hubble)
-)
-
--- Aggregate based on the month and contract durability type
-select
-  date_trunc(et.ledger_date, month) as month_agg
-  , cd.contract_durability
-  , count(1) as expired_entry_count
-from expired_ttl as et
-  join `crypto-stellar.crypto_stellar_dbt.contract_data_current` as cd
-    on et.key_hash = cd.ledger_key_hash
-where true
-  -- Optionally filter for a specific date/date range
-  and et.ledger_date between '2024-02-01' and '2024-10-31'
-group by 1,2
-order by 1 desc, 2
-```
-
-4. Inserta `Gráfico de Columnas`
-
-<img src={add_column_chart} width="200" />
-
-5. Selecciona lo siguiente:
-
-- `BigQuery SQL Personalizado` como tu `Fuente de datos`
-- `month_agg` como la `Dimensión`
-- `contract_durability` como la `Dimensión de Desglose`
-- `expired_entry_count` como la `Métrica`
-
-<img src={column_chart_config} width="300" />
-
-6. Ahora deberías tener un gráfico de columnas (gráfico de barras) que muestra las entradas de contratos Soroban que han caducado
-
-<img src={expired_entry_column_chart} width="500" />
-
-### Aplicar un Filtro Global
-
-1. Haz clic en `+Añadir filtro rápido` para aplicar un filtro en todo el informe
-
-<img src={add_quick_filter} width="500" />
-
-2. Selecciona `contract_durability` para filtrar por los valores de `contract_durability`
-
-<img src={filter_contract} width="500" />
-
-3. Selecciona solo `ContractDataDurabilityPersistent` y haz clic en `Aplicar`
-
-<img src={persistent_only} width="500" />
-
-4. Tus gráficos deberían ahora estar filtrados y mostrar solo datos de `ContractDataDurabilityPersistent`
-
-<img src={filtered_report} width="500" />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/history-vs-state-tables.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/history-vs-state-tables.mdx
deleted file mode 100644
index 9ac2991abf..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/history-vs-state-tables.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Historia vs Tablas de Estado
-sidebar_position: 60
----
-
-Esta página describe las diferencias entre las tablas de Historia y Estado dentro de Hubble.
-
-## ¿Qué son las tablas de estado?
-
-Estas rastrean los cambios de las entradas de ledger, lo que significa que almacenan cómo evolucionó cada entrada de ledger a lo largo del tiempo en lugar de solo el estado final de la entrada de ledger. Esto significa que las tablas de estado son un registro completo del historial de los estados de las entradas de ledger que han cambiado basado en acciones (operaciones) de la red Stellar.
-
-- Cada fila representa un cambio único en una entrada de ledger
-- Verás múltiples filas del mismo hash de entrada de ledger si ha sido modificado varias veces en diferentes secuencias de ledger
-- Esto no es una tabla tipo snapshot/SCD 2. No hay fechas válidas de inicio/final en estas tablas
-
-Ten en cuenta que este comportamiento es diferente en comparación con el [endpoint `getLedgerEntries` de RPC](../../../apis/rpc/api-reference/methods). RPC devolverá el valor actual de una entrada de libro mayor dada (un solo resultado), mientras que las tablas de estado de Hubble devolverán todos los cambios a lo largo del tiempo para una entrada de libro mayor dada (varios resultados). Para obtener un comportamiento similar al de RPC, puedes filtrar y devolver la última entrada de las tablas de estado de Hubble o puedes usar la versión `_current` de las tablas de estado listadas en el conjunto de datos `crypto-stellar.crypto_stellar_dbt`.
-
-### Ejemplo de contenidos de una tabla de estado
-
-Digamos que solo queremos las entradas de ledger para el balance de `DUMMYACCOUNT`. La tabla de estado `account` devolvería lo siguiente:
-
-| account_id   | ledger_sequence | balance |
-| ------------ | --------------- | ------- |
-| DUMMYACCOUNT | 1               | 10      |
-| DUMMYACCOUNT | 2               | 15      |
-| DUMMYACCOUNT | 3               | 5       |
-
-Como se ve en la tabla, cada fila muestra el `balance` de `DUMMYACCOUNT` en un `ledger_sequence` específico.
-
-```
-
-### List of state tables
-
-- [Accounts](../data-catalog/data-dictionary/accounts.mdx)
-- [Claimable Balances](../data-catalog/data-dictionary/claimable-balances.mdx)
-- [Contract Code](../data-catalog/data-dictionary/contract-code.mdx)
-- [Contract Data](../data-catalog/data-dictionary/contract-data.mdx)
-- [Liquidity Pools](../data-catalog/data-dictionary/liquidity-pools.mdx)
-- [Offers](../data-catalog/data-dictionary/offers.mdx)
-- [Trustlines](../data-catalog/data-dictionary/trustlines.mdx)
-- [TTL](../data-catalog/data-dictionary/ttl.mdx)
-
-## What are history tables?
-
-These tables are a full history log of actions on the network.
-
-- Each row represents some action on the network (ledger closing, transactions, operations, etc...)
-- Encompasses the complete chronological history of activity on the network
-
-### Example contents of a history table
-
-Let's say we operations for a specific transaction. The `history_operations` table would return the following:
-
-| transaction_hash | id | ledger_sequence | type | details_json |
-| --- | --- | --- | --- | --- |
-| TXHASH1 | 1 | 1 | 13 | `{"some": "operation details"}` |
-| TXHASH1 | 2 | 1 | 2 | `{"some": "operation details"}` |
-| TXHASH1 | 3 | 1 | 13 | `{"some": "operation details"}` |
-
-As seen in the table, each row shows the distinct operation with its unique `id`.
-
-### List of history tables
-
-- [History Assets](../data-catalog/data-dictionary/history-assets.mdx)
-- [History Contract Events](../data-catalog/data-dictionary/history-contract-events.mdx)
-- [History Effects](../data-catalog/data-dictionary/history-effects.mdx)
-- [History Ledgers](../data-catalog/data-dictionary/history-ledgers.mdx)
-- [History Operations](../data-catalog/data-dictionary/history-operations.mdx)
-- [History Trades](../data-catalog/data-dictionary/history-trades.mdx)
-- [History Transactions](../data-catalog/data-dictionary/history-transactions.mdx)
-- [Enriched History Operations](../data-catalog/data-dictionary/enriched-history-operations.mdx)
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/optimizing-queries.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/optimizing-queries.mdx
deleted file mode 100644
index 14bc6641d4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/optimizing-queries.mdx
+++ /dev/null
@@ -1,231 +0,0 @@
----
-title: Optimizar Consultas
-sidebar_position: 30
----
-
-Hubble tiene terabytes de datos para explorar&mdash;¡eso es mucho dato! Con acceso a tantos datos al alcance de tu mano, es crucial ajustar el rendimiento de tus consultas.
-
-Una de las fortalezas de BigQuery también es su trampa: tienes acceso a capacidades de computación tremendas, pero pagas por lo que usas. Si ajustas tus consultas, tendrás acceso a poderosos insights a una fracción del costo de mantener un almacén de datos tú mismo. Sin embargo, es fácil incurrir en costos altos si no tienes cuidado.
-
-## Prácticas Recomendadas
-
-### Presta atención a la estructura de la tabla.
-
-Las tablas grandes están particionadas y agrupadas de acuerdo a patrones de acceso comunes. Elimina solo las particiones que necesitas y filtra o agrega por campos agrupados cuando sea posible.
-
-Unir tablas por cadenas es costoso. Evita unir por claves de cadena si puedes utilizar claves enteras en su lugar.
-
-Lee la documentación sobre [Visualización de Metadatos](./viewing-metadata.mdx) para aprender más sobre los metadatos de la tabla.
-
-#### Ejemplo - Tipos de Operaciones de Perfilado
-
-Digamos que quieres perfilar los [tipos de operaciones](../../../../learn/fundamentals/transactions/list-of-operations.mdx) enviadas a la Red Stellar mensualmente. ======== Digamos que quieres perfilar los [tipos de operaciones](../../../../learn/fundamentals/transactions/list-of-operations.mdx) enviadas a la Red Stellar mensualmente.
-
-<CodeExample>
-
-```sql
-# Inefficient query
-select datetime_trunc(batch_run_date, month) as `month`,
-  type_string,
-  count(id) as count_operations
-from `crypto-stellar.crypto_stellar.history_operations`
-group by `month`,
-  type_string
-order by `month`
-```
-
-</CodeExample>
-
-La tabla `history_operations` está particionada por `batch_run_date` y agrupada por `transaction_id`, `source_account` y `type`. Los costos de consulta se reducen considerablemente al eliminar particiones no utilizadas. En este caso, podrías filtrar las operaciones enviadas antes de 2023. Esto reduce el costo de la consulta en 4x.
-
-<CodeExample>
-
-```sql
-# Prune out partitions you do not need
-select datetime_trunc(batch_run_date, month) as `month`,
-  type_string,
-  count(id) as count_operations
-from `crypto-stellar.crypto_stellar.history_operations`
--- batch_run_date is a datetime object, formatted as ISO 8601
-where batch_run_date > '2023-01-01T00:00:00'
-group by `month`,
-  type_string
-order by `month`
-```
-
-</CodeExample>
-
-Cambiar el campo de agregación a `type`, que es un campo agrupado, reducirá los costos en un tercio:
-
-<CodeExample>
-
-```sql
-# Prune out partitions you do not need
-# Aggregate by clustered field, `type`
-select datetime_trunc(batch_run_date, month) as `month`,
-  `type`,
-  count(id) as count_operations
-from `crypto-stellar.crypto_stellar.history_operations`
-where batch_run_date >= '2023-01-01T00:00:00'
-group by `month`,
-  `type`
-order by `month`
-```
-
-</CodeExample>
-
-**Resumen del Rendimiento**
-
-Al eliminar particiones y agregar con un campo agrupado, los costos de procesamiento de consultas se reducen a un factor de 8.
-
-|                     | Bytes Procesados | Costo   |
-| ------------------- | ---------------- | ------- |
-| Consulta Original   | 408,1 GB         | $2,041  |
-| Consulta Mejorada 1 | 83,06 GB         | $0,415  |
-| Consulta Mejorada 2 | 54,8 GB          | $0,274  |
-
-### Sé lo más específico posible.
-
-No escribas declaraciones `SELECT *` a menos que necesites que se devuelvan todas las columnas en la respuesta de la consulta. Dado que BigQuery es una base de datos columnar, puede omitir la lectura de datos por completo si las columnas no están incluidas en la declaración select. Cuanto más amplia sea la tabla, más crucial es seleccionar _solo_ lo que necesitas.
-
-#### Ejemplo - Tarifas de Transacción
-
-Digamos que necesitas ver las tarifas de todas las transacciones enviadas en mayo de 2023. ¿Qué pasa si escribes un `SELECT *`?
-
-<CodeExample>
-
-```sql
-# Inefficient query
-select *
-from `crypto-stellar.crypto_stellar.history_transactions`
-where batch_run_date >= '2023-05-01'
-  and batch_run_date < '2023-06-01'
-```
-
-</CodeExample>
-
-¡Se estima que esta consulta costará casi $4!
-
-Si solo necesitas información de tarifas, puedes filtrar los datos, reduciendo los costos de consulta en un factor de 50x:
-
-<CodeExample>
-
-```sql
-# Select only the columns you need
-select id,
-  transaction_hash,
-  ledger_sequence,
-  account,
-  fee_account,
-  max_fee,
-  fee_charged,
-  new_max_fee
-from `crypto-stellar.crypto_stellar.history_transactions`
-where batch_run_date >= '2023-05-01'
-  and batch_run_date < '2023-06-01'
-```
-
-</CodeExample>
-
-**Resumen del Rendimiento**
-
-Hubble almacena tablas amplias. El rendimiento de las consultas mejora considerablemente al seleccionar solo los datos que necesitas. Este principio es crítico al explorar las tablas de operaciones y transacciones, que son las tablas más grandes de Hubble.
-
-|                   | Bytes Procesados | Costo   |
-| ----------------- | ---------------- | ------- |
-| Consulta Original | 769,45 GB        | $3,847  |
-| Consulta Mejorada | 16,6 GB          | $0,083  |
-
-:::tip
-
-La consola de BigQuery te permite ver datos de la tabla de forma gratuita, lo cual es equivalente a escribir un `SELECT *`. Haz clic en el nombre de la tabla y abre el panel de vista previa.
-
-:::
-
-### Filtrar temprano.
-
-Al escribir consultas complejas, filtra los datos lo antes posible. Empuja las cláusulas `WHERE` y `GROUP BY` hacia arriba en la consulta para reducir la cantidad de datos escaneados.
-
-:::caution
-
-Las cláusulas `LIMIT` aceleran el rendimiento, pero **no** reducen la cantidad de datos escaneados. Solo los _resultados finales_ devueltos al usuario están limitados. Usa con precaución.
-
-:::
-
-Empuja transformaciones y funciones matemáticas al final de la consulta cuando sea posible. Funciones como `TRIM()`, `CAST()`, `SUM()`, y `REGEXP_*` son intensivas en recursos y deben ser aplicadas solo a los resultados finales de la tabla.
-
-## Estimando Costos
-
-Si necesitas estimar costos antes de ejecutar una consulta, tienes varias opciones disponibles:
-
-### Consola de BigQuery
-
-La Consola de BigQuery incluye un validador de consultas incorporado. Verifica la sintaxis de la consulta y proporciona una estimación de la cantidad de bytes procesados. El validador se puede encontrar en la esquina superior derecha del Editor de Consultas, junto al marcado de verificación verde.
-
-Para calcular el costo de la consulta, convierte el número de bytes procesados en terabytes y multiplica el resultado por $5:
-
-`(bytes leídos estimados / 1TB) * $5`
-
-Pega la siguiente consulta en el Editor para ver los bytes procesados estimados.
-
-<CodeExample>
-
-```sql
-select timestamp_trunc(closed_at, month) as month,
-  sum(tx_set_operation_count) as total_operations
-from `crypto-stellar.crypto_stellar.history_ledgers`
-where batch_run_date >= '2023-01-01T00:00:00'
-  and batch_run_date < '2023-06-01T00:00:00'
-  and closed_at >= '2023-01-01T00:00:00'
-  and closed_at < '2023-06-01T00:00:00'
-group by month
-```
-
-</CodeExample>
-
-El validador estima que se leerán 51.95MB de datos.
-
-0,00005195 TB \* $5 = $0,000259. _¡Esa es una consulta barata!_
-
-### Parámetro de configuración dryRun
-
-Si envías una consulta a través de una [biblioteca de clientes de BigQuery](https://cloud.google.com/bigquery/docs/reference/libraries), puedes realizar una ejecución en modo de prueba para estimar el total de bytes procesados antes de enviar el trabajo de consulta.
-
-<CodeExample>
-
-```python
-from google.cloud import bigquery
-
-# Construct a BigQuery client object
-client = bigquery.Client()
-
-# Set dry run to True to get bytes processed
-job_config = bigquery.QueryJobConfig(dry_run=True, use_query_cache=False)
-
-# Pass in job config
-sql = """
-    select timestamp_trunc(closed_at, month) as month,
-      sum(tx_set_operation_count) as total_operations
-    from `crypto-stellar.crypto_stellar.history_ledgers`
-    where batch_run_date >= '2023-01-01T00:00:00'
-      and batch_run_date < '2023-06-01T00:00:00'
-      and closed_at >= '2023-01-01T00:00:00+00'
-      and closed_at < '2023-06-01T00:00:00'
-    group by month
-"""
-
-# Make API request
-query_job = client.query((sql), job_config = job_config)
-
-# Calculate the cost
-cost = (query_job.total_bytes_processed / 1000000000000) * 5
-
-print(f'This query will process {query_job.total_bytes_processed} bytes')
-print(f'This query will cost approximately ${cost}')
-```
-
-</CodeExample>
-
-También hay [plugins de IDE](https://plugins.jetbrains.com/plugin/15884-bigquery-query-size-estimator) que pueden aproximar el costo.
-
-Para más información sobre los costos de consultas, lee la [documentación de BigQuery](https://cloud.google.com/bigquery/docs/estimate-costs).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx
deleted file mode 100644
index ea578eadbc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx
+++ /dev/null
@@ -1,899 +0,0 @@
----
-title: Consultas para datos similares a Horizon/RPC
-sidebar_position: 50
----
-
-[Horizon](../../../apis/horizon/README.mdx) y [RPC](../../../apis/rpc/README.mdx) proporcionan puntos finales de API para recuperar datos de la red Stellar. Los siguientes ejemplos de consultas recuperan los mismos datos utilizando Hubble con el beneficio adicional de poder devolver datos históricos.
-
-## Cuentas
-
-[horizon/accounts](../../../apis/horizon/api-reference/resources/accounts/README.mdx)
-
-Los usuarios interactúan con la red Stellar a través de cuentas. Todo lo demás en el ledger—activos, ofertas, líneas de confianza, etc.—son propiedad de las cuentas, y las cuentas deben autorizar todos los cambios en el ledger a través de transacciones firmadas.
-
-Aprende más sobre [cuentas](../../../../learn/glossary.mdx#account).
-
-### Información general de cuentas y saldo de XLM
-
-```sql
-select
-  account_id
-  , sequence_number as sequence
-  , sequence_ledger
-  , sequence_time
-  , num_subentries
-  , home_domain
-  , last_modified_ledger
-  , balance
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.accounts`
-where true
-  -- equivalent account_id parameter
-  and account_id=<account_id>
-  -- filter to the specific date or date range
-  and batch_run_date between '2024-01-01' and '2024-01-02'
-order by closed_at desc
-```
-
-### Información de saldo de activos no XLM
-
-```sql
-select
-  account_id
-  , asset_code
-  , asset_issuer
-  , asset_type
-  , balance
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.trust_lines`
-where true
-  -- equivalent account_id parameter
-  and account_id=<account_id>
-  -- filter to the specific date or date range
-  and batch_run_date between '2024-01-01' and '2024-01-02'
-order by closed_at desc
-```
-
-### Información del firmante de la cuenta
-
-```sql
-select
-  account_id
-  , signer
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.account_signers`
-where true
-  -- equivalent account_id parameter
-  and account_id=<account_id>
-  -- filter to the specific date or date range
-  and batch_run_date between '2024-01-01' and '2024-01-02'
-order by closed_at desc
-```
-
-### Listar todas las cuentas
-
-```sql
-select
-  account_id
-from `crypto-stellar.crypto_stellar_dbt.accounts_current`
-where true
--- limit does not reduce the amount of data BigQuery queries
-limit 1000
-```
-
-### Recuperar las transacciones de una cuenta
-
-```sql
-select
-  id
-  , transaction_hash
-  , ledger_sequence
-  , operation_count
-  , successful
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_transactions`
-where true
-  -- equivalent account_id parameter
-  and account=<account_id>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at >= timestamp(current_date)
--- limit does not reduce the amount of data BigQuery queries
-limit 1000
-```
-
-### Recuperar las operaciones de una cuenta
-
-```sql
-select
-  op_account_id
-  , op_id
-  , type_string
-  , ledger_sequence
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations`
-where true
-  -- equivalent account_id parameter
-  and op_account_id=<account_id>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at >= timestamp(current_date)
--- limit does not reduce the amount of data BigQuery queries
-limit 1000
-```
-
-### Recuperar los pagos de una cuenta
-
-```sql
-select
-  op_account_id
-  , transaction_id
-  , transaction_hash
-  , op_id
-  , ledger_sequence
-  , `from`
-  , `to`
-  , asset_code
-  , asset_issuer
-  , asset_type
-  , amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations`
-where true
-  -- equivalent account_id parameter
-  and op_account_id=<account_id>
-  and type in (0, 1, 2, 13, 8) -- create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at >= timestamp(current_date)
--- limit does not reduce the amount of data BigQuery queries
-limit 1000
-```
-
-### Recuperar los efectos de una cuenta
-
-```sql
-select
-  eho.op_account_id
-  , he.operation_id
-  , eho.type_string
-  , he.details.asset_code
-  , he.details.asset_issuer
-  , he.details.asset_type
-  , he.details.amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_effects` as he
-  inner join `crypto-stellar.crypto_stellar_dbt.enriched_history_operations` as eho
-    on he.operation_id = eho.op_id
-    and eho.closed_at >= timestamp(current_date)
-where true
-  -- equivalent account_id parameter
-  and op_account_id=<account_id>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and he.closed_at >= timestamp(current_date)
--- limit does not reduce the amount of data BigQuery queries
-limit 1000
-```
-
-### Recuperar las ofertas de una cuenta
-
-```sql
-select
-  seller_id
-  , offer_id
-  , selling_asset_code
-  , buying_asset_code
-  , amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.offers_current`
-where true
-  -- equivalent account_id parameter
-  and seller_id=<account_id>
-```
-
-### Recuperar las operaciones de una cuenta
-
-```sql
-with selling_side as (
-  select
-    selling_account_address as account_id
-    , history_operation_id
-    , selling_asset_code
-    , buying_asset_code
-    , selling_amount as amount
-    -- please see table schema for more available columns and data
-  from `crypto-stellar.crypto_stellar.history_trades`
-  where true
-    -- equivalent account_id parameter
-    and selling_account_address=<account_id>
-    -- highly recommended to provide a date range to reduce amount of data queried
-    and batch_run_date >= current_date
-),
-buying_side as (
-  select
-    buying_account_address as account_id
-    , history_operation_id
-    , selling_asset_code
-    , buying_asset_code
-    , buying_amount as amount
-    -- please see table schema for more available columns and data
-  from `crypto-stellar.crypto_stellar.history_trades`
-  where true
-    -- equivalent account_id parameter
-    and buying_account_address=<account_id>
-    -- highly recommended to provide a date range to reduce amount of data queried
-    and batch_run_date >= current_date
-),
-union_data as (
-  select
-    account_id
-    , history_operation_id
-    , selling_asset_code
-    , buying_asset_code
-    , amount
-  from selling_side
-  union all
-  select
-    account_id
-    , history_operation_id
-    , selling_asset_code
-    , buying_asset_code
-    , amount
-  from buying_side
-)
-
-select * from union_data
-```
-
-## Activos
-
-[horizon/assets](../../../apis/horizon/api-reference/resources/assets/README.mdx)
-
-Los activos son representaciones de valor emitidas en la red Stellar. Un activo consiste en un tipo, código e emisor.
-
-Aprende más sobre [activos](../../../../learn/glossary.mdx#asset).
-
-### Listar todos los activos
-
-```sql
-with assets as (
-  select
-    asset_code
-    , asset_issuer
-    -- please see table schema for more available columns and data
-  from `crypto-stellar.crypto_stellar.history_assets`
-  where true
-    -- equivalent asset_code/asset_issuer parameters
-    and asset_code=<asset code>
-    and asset_issuer=<asset issuer>
-),
-accounts as (
-  select
-    count(ac.account_id) as num_accounts
-    , countif(ac.flags=1) as authorized_accounts
-    , sum(balance) as amount
-  from assets
-    join `crypto-stellar.crypto_stellar_dbt.trust_lines_current` as ac
-      on assets.asset_code = ac.asset_code
-      and assets.asset_issuer = ac.asset_issuer
-  where true
-),
-liquidity_pools as (
-  select
-    count(*) as num_liquidity_pools
-    , sum(lpc.asset_a_amount) as liquidity_pools_amount
-  from assets
-    join `crypto-stellar.crypto_stellar_dbt.liquidity_pools_current` as lpc
-      on assets.asset_code = lpc.asset_a_code
-      and assets.asset_issuer = lpc.asset_a_issuer
-  where true
-),
-current_claimable_balances as (
-  -- TODO: This should be replaced with the claimable_balances_current table when available
-  SELECT
-    cb.balance_id
-    , cb.asset_code
-    , cb.asset_issuer
-    , cb.asset_amount
-    , cb.deleted
-    , cb.last_modified_ledger
-    , row_number() over(partition by cb.balance_id, cb.asset_code, cb.asset_issuer order by last_modified_ledger desc, deleted desc) as rn
-  FROM assets
-    join `crypto-stellar.crypto_stellar.claimable_balances` as cb
-      on assets.asset_code = cb.asset_code
-      and assets.asset_issuer = cb.asset_issuer
-  where true
-  order by last_modified_ledger asc
-),
-claimable_balances as (
-select
-    count(*) as num_claimable_balances
-    , sum(asset_amount) as claimable_balances_amount
-  from current_claimable_balances
-  where true
-    and rn = 1
-    and deleted = false
-)
-
-select
-  *
-from assets
-  join accounts on true
-  join liquidity_pools on true
-  join claimable_balances on true
-```
-
-### Obtener información del contrato de activo en Stellar
-
-```sql
-select
-  count(balance_holder) as num_contracts
-  , sum(parse_bignumeric(balance)) * .0000001 as contracts_amount
-from `crypto-stellar.crypto_stellar_dbt.contract_data_current`
-where true
-  and contract_id = <SAC contract id>
-  and balance != ""
-```
-
-## Saldos reclamables
-
-[horizon/claimable_balances](../../../apis/horizon/api-reference/resources/claimablebalances/README.mdx)
-
-Un saldo reclamable representa la transferencia de propiedad de una cantidad de un activo. Los saldos reclamables brindan un mecanismo para establecer un pago que se puede reclamar en el futuro. Esto te permite hacer pagos a cuentas que actualmente no pueden aceptarlos.
-
-### Listar todos los saldos reclamables
-
-```sql
-current_claimable_balances as (
-  -- TODO: This should be replaced with the claimable_balances_current table when available
-  select
-    balance_id
-    , asset_code
-    , asset_issuer
-    , asset_amount
-    , deleted
-    , last_modified_ledger
-    -- please see table schema for more available columns and data
-    , row_number() over(partition by balance_id, asset_code, asset_issuer order by last_modified_ledger desc, deleted desc) as rn
-  from `crypto-stellar.crypto_stellar.claimable_balances` as cb
-  where true
-    -- equivalent asset_code/asset_issuer parameters
-    and asset_code=<asset code>
-    and asset_issuer=<asset issuer>
-  order by last_modified_ledger asc
-)
-select
-  *
-from current_claimable_balances
-where true
-  and rn = 1
-  and deleted = false
-  -- other filters for sponsor and claimants
-  --and sponsor = <sponsor address>
-  --and claimants.destination = <account address>
-```
-
-### Recuperar un saldo reclamable
-
-```sql
-with assets as (
-  -- Used to filter to a specific asset
-  select
-    asset_code
-    , asset_issuer
-  from `crypto-stellar.crypto_stellar.history_assets`
-  where true
-    -- equivalent asset_code/asset_issuer parameters
-    and asset_code=<asset code>
-    and asset_issuer=<asset issuer>
-),
-current_claimable_balances as (
-  -- TODO: This should be replaced with the claimable_balances_current table when available
-  select
-    cb.balance_id
-    , cb.asset_code
-    , cb.asset_issuer
-    , cb.asset_amount
-    , cb.deleted
-    , cb.last_modified_ledger
-    -- please see table schema for more available columns and data
-    , row_number() over(partition by cb.balance_id, cb.asset_code, cb.asset_issuer order by last_modified_ledger desc, deleted desc) as rn
-  from assets
-    join `crypto-stellar.crypto_stellar.claimable_balances` as cb
-      on assets.asset_code = cb.asset_code
-      and assets.asset_issuer = cb.asset_issuer
-  where true
-  order by last_modified_ledger asc
-)
-select
-  *
-from current_claimable_balances
-where true
-  and rn = 1
-  and deleted = false
-  and balance_id = <claimable balance id>
-```
-
-### Recuperar operaciones y transacciones relacionadas
-
-```sql
-select
-  op_id
-  , transaction_id
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations`
-where true
-  and balance_id = <claimable_balance_id>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-## Efectos
-
-[horizon/effects](../../../apis/horizon/api-reference/resources/effects/README.mdx)
-
-Los efectos representan cambios específicos que ocurren en el ledger como resultado de operaciones exitosas, pero no necesariamente se reflejan directamente en el ledger o el historial, como sí lo hacen las transacciones y operaciones.
-
-### Listar todos los efectos
-
-```sql
-select
-  type
-  , type_string
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_effects`
-where true
-  -- Optional filtering options
-  --and operation_id = <operation id>
-  --and address = <account address>
-  --and details.liquidity_pool_id = <liquidity pool id>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-## Libros de contabilidad
-
-[horizon/ledgers](../../../apis/horizon/api-reference/resources/ledgers/README.mdx)
-
-Cada ledger almacena el estado de la red en un momento dado y contiene todos los cambios - transacciones, operaciones, efectos, etc. - a ese estado.
-
-Aprende más sobre [ledgers](../../../../learn/glossary.mdx#ledger).
-
-### Listar todos los ledgers
-
-```sql
-select
-  sequence
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_ledgers`
-where true
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-### Recuperar transacciones y operaciones de un ledger
-
-```sql
-select
-  ledger_sequence
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations`
-where true
-  and ledger_sequence = <ledger sequence>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-### Recuperar los pagos de un ledger
-
-```sql
-select
-  ledger_sequence
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations` as eho
-where true
-  and type in (0, 1, 2, 8, 13) -- create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge
-  and ledger_sequence = <ledger sequence>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-## Fondos de Liquidez
-
-[horizon/liquidity_pools](../../../apis/horizon/api-reference/resources/liquiditypools/README.mdx)
-
-Los Fondos de Liquidez proporcionan una forma simple y no interactiva de intercambiar grandes cantidades de capital y permiten altos volúmenes de comercio.
-
-### Listar Fondos de Liquidez
-
-```sql
-select
-  liquidity_pool_id
-  , fee
-  , trustline_count
-  , asset_a_code
-  , asset_a_issuer
-  , asset_a_amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.liquidity_pools_current`
-where true
-```
-
-### Recuperar un Fondo de Liquidez
-
-```sql
-select
-  liquidity_pool_id
-  , fee
-  , trustline_count
-  , asset_a_code
-  , asset_a_issuer
-  , asset_a_amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.liquidity_pools_current`
-where true
-  and liquidity_pool_id = <liquidity_pool_id>
-```
-
-### Recuperar las transacciones y operaciones de un Fondo de Liquidez
-
-```sql
-select
-  op_id
-  , transaction_id
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations`
-where true
-  and liquidity_pool_id = <liquidity_pool_id>
-```
-
-### Recuperar las operaciones relacionadas de un Fondo de Liquidez
-
-```sql
-select
-  selling_liquidity_pool_id
-  , selling_amount
-  , buying_amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_trades`
-where true
-  and selling_liquidity_pool_id = <liquidity pool id>
-```
-
-## Ofertas
-
-[horizon/offers](../../../apis/horizon/api-reference/resources/offers/README.mdx)
-
-Las ofertas son declaraciones sobre cuánto de un activo una cuenta desea comprar o vender.
-
-Aprende más sobre [ofertas](../../../../learn/glossary.mdx#decentralized-exchange).
-
-### Listar todas las ofertas
-
-```sql
-select
-  offer_id
-  , seller_id
-  , selling_asset_code
-  , selling_asset_issuer
-  , amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.offers_current`
-where true
-  -- optional filter by account
-  --and seller_id = <account address>
-  and closed_at between <start> and <end>
-```
-
-### Recuperar una oferta
-
-```sql
-select
-  offer_id
-  , seller_id
-  , selling_asset_code
-  , selling_asset_issuer
-  , amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.offers_current`
-where true
-  and offer_id = <offer id>
-  and closed_at between <start> and <end>
-```
-
-### Recuperar las operaciones de una oferta
-
-```sql
-select
-  selling_offer_id
-  , selling_amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_trades`
-where true
-  and selling_offer_id = <offer_id>
-  -- offer_id could also be the buying_offer_id
-  --and buying_offer_id = <offer_id>
-```
-
-## Operaciones
-
-[horizon/operations](../../../apis/horizon/api-reference/resources/operations/README.mdx)
-
-Las operaciones son objetos que representan un cambio deseado en el ledger: pagos, ofertas para intercambiar moneda, cambios realizados a opciones de cuenta, etc. Las operaciones se envían a la red Stellar agrupadas en una transacción.
-
-Cada una de las operaciones de Stellar tiene un objeto de operación único.
-
-### Listar todas las operaciones
-
-```sql
-select
-  op_id
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations`
-where true
-  -- optional filters
-  --and op_source_account = <account address>
-  --and ledger_sequence = <ledger sequence>
-  --and liquidity_pool_id = <liquidity pool id>
-  --and transaction_hash = <transaction hash>
-  --and transaction_id = <transaction id>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-### Listar todos los pagos
-
-```sql
-select
-  op_id
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations` as eho
-where true
-  -- optional filters
-  --and op_source_account = <account address>
-  --and ledger_sequence = <ledger sequence>
-  --and liquidity_pool_id = <liquidity pool id>
-  --and transaction_hash = <transaction hash>
-  --and transaction_id = <transaction id>
-  and type in (0, 1, 2, 8, 13) -- create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-### Recuperar una operación
-
-```sql
-select
-  op_id
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations` as eho
-where true
-  -- op_id = <operation id>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-### Recuperar los efectos de una operación
-
-```sql
-select
-  operation_id
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stella.history_effects`
-where true
-  operation_id = <operation id>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-## Operaciones de Intercambio
-
-[horizon/trades](../../../apis/horizon/api-reference/resources/trades/README.mdx)
-
-Cuando una oferta se cumple total o parcialmente, ocurre un intercambio. Los intercambios también pueden ser causados por pagos de ruta exitosos, ya que los pagos de ruta implican cumplir ofertas.
-
-Un intercambio ocurre entre dos partes—`base` y `contraparte`. Cuál es cuál es arbitrario o determinado por la consulta que se llama.
-
-Aprende más sobre [intercambios](../../../../learn/glossary.mdx#decentralized-exchange).
-
-### Listar todos los intercambios
-
-```sql
-select
-  -- base_asset == selling_asset
-  -- counter_asset == buying_asset
-  selling_asset_code
-  , selling_asset_issuer
-  , selling_amount
-  , buying_asset_code
-  , buying_asset_issuer
-  , buying_amount
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_trades`
-where true
-  -- optional filter columns
-  and selling_offer_id = <offer id>
-  and buying_offer_id = <offer id>
-  and selling_asset_code = <asset code>
-  and selling_asset_issuer = <asset issuer>
-  and selling_liquidity_pool_id = <liquidity pool id>
-  and selling_account_address = <account address>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-## Transacciones
-
-[horizon/transactions](../../../apis/horizon/api-reference/resources/transactions/README.mdx)
-
-Las transacciones son comandos que modifican el estado del ledger y constan de una o más operaciones.
-
-Aprende más sobre [transacciones](../../../../learn/glossary.mdx#transaction).
-
-### Listar todas las transacciones
-
-```sql
-select
-  id
-  , max_fee
-  , operation_count
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_transactions`
-where true
-  -- optional filters
-  --and account = <account address>
-  --and ledger_sequence = <ledger sequence>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-### Recuperar una transacción
-
-```sql
-select
-  id
-  , max_fee
-  , operation_count
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_transactions`
-where true
-  and id = <transaction id>
-  -- transaction_hash is also available
-  --and transaction_hash = <transaction hash>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-### Recuperar las operaciones de una transacción
-
-```sql
-select
-  transaction_id
-  , op_id
-  , max_fee
-  , operation_count
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations`
-where true
-  and transaction_id = <transaction id>
-  -- transaction_hash is also available
-  --and transaction_hash = <transaction hash>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-## Agregaciones de Intercambio
-
-[horizon/trade_aggregations](../../../apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx)
-
-Una agregación de intercambio representa estadísticas agregadas sobre un par de activos (base y contraparte) para un período de tiempo específico. Las agregaciones de intercambio son útiles para los desarrolladores de clientes de intercambio y proporcionan datos históricos de intercambios.
-
-### Listar Agregaciones de Intercambio
-
-```sql
-select
-  date(closed_at)
-  , selling_asset_code
-  , selling_asset_issuer
-  , buying_asset_code
-  , buying_asset_issuer
-  , count(1) as number_of_trades
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_trades`
-where true
-  -- there are various columns to filter by
-  -- and selling_asset_code = <asset code>
-  -- and selling_asset_issuer = <asset issuer>
-  -- and buying_asset_code = <asset code>
-  -- and buying_asset_issuer = <asset issuer>
-  -- and closed_at between <start> and <end>
-group by 1,2,3,4,5
-```
-
-## Estadísticas de tarifas
-
-[horizon/fee-stats](../../../apis/horizon/api-reference/aggregations/fee-stats/README.mdx)
-
-Las estadísticas de tarifas se utilizan para predecir qué tarifa establecer para una transacción antes de enviarla a la red.
-
-### Recuperar estadísticas de tarifas
-
-```sql
-select
-  day_agg
-  , fee_charged_max
-  , fee_charged_min
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.fee_stats_agg`
-where true
-  and day_agg between <start> and <end>
-```
-
-## getEvents
-
-[rpc/getEvents](../../../apis/rpc/api-reference/methods/getEvents.mdx)
-
-Los eventos de contrato y eventos de diagnóstico se utilizan para información suplementaria relacionada con la invocación de un contrato
-
-```sql
-select
-  contract_id
-  , topics_decoded
-  , data_decoded
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar.history_contract_events`
-where true
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
-
-## getLedgerEntries
-
-[rpc/getLedgerEntries](../../../apis/rpc/api-reference/methods/getLedgerEntries.mdx)
-
-Permite la recuperación de varios estados del ledger, como cuentas, líneas de confianza, ofertas, datos, saldos reclamables y fondos de liquidez. También proporciona acceso directo para inspeccionar el estado actual de un contrato, su código o cualquier otra entrada de ledger
-
-### Entradas de datos del contrato
-
-```sql
-select
-  ledger_key_hash
-  , contract_id
-  , balance_holder
-  , balance
-from `crypto-stellar.crypto_stellar_dbt.contract_data_current`
-where true
-  and ledger_key_hash = <ledger_key_hash>
-```
-
-### Entradas de código del contrato
-
-```sql
-select
-  ledger_key_hash
-  , contract_code_hash
-from `crypto-stellar.crypto_stellar_dbt.contract_code_current`
-where true
-  and ledger_key_hash = <ledger_key_hash>
-```
-
-## getTransaction
-
-[rpc/getTransaction](../../../apis/rpc/api-reference/methods/getTransaction.mdx)
-
-Las transacciones son comandos que modifican el estado del ledger y constan de una o más operaciones.
-
-Aprende más sobre [transacciones](../../../../learn/glossary.mdx#transaction).
-
-```sql
-select
-  transaction_id
-  , op_id
-  , max_fee
-  , operation_count
-  -- please see table schema for more available columns and data
-from `crypto-stellar.crypto_stellar_dbt.enriched_history_operations`
-where true
-  and transaction_id = <transaction id>
-  -- transaction_hash is also available
-  --and transaction_hash = <transaction hash>
-  -- highly recommended to provide a date range to reduce amount of data queried
-  and closed_at between <start> and <end>
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/viewing-metadata.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/viewing-metadata.mdx
deleted file mode 100644
index 8b53daea90..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/analyst-guide/viewing-metadata.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Visualizando Metadatos
-sidebar_position: 20
----
-
-Hubble publica metadatos que pueden ayudar a los usuarios a determinar qué tablas consultar, con qué frecuencia se actualiza el conjunto de datos y información general sobre el conjunto de datos.
-
-Hay dos formas de acceder a esta información:
-
-## Explorador de BigQuery
-
-Al acceder a Hubble desde su enlace destacado, el panel del Explorador cargará metadatos sobre el conjunto de datos `crypto-stellar.crypto_stellar`.
-
-Usa el Toggle para ver el contenido del Conjunto de Datos. Hacer clic en el nombre de una tabla cargará lo siguiente:
-
-- _Esquema_ - información detallada sobre el esquema de la tabla, incluyendo definiciones de columnas y tipos de datos. Visualizar el esquema ayuda a escribir una consulta SQL
-- _Detalles_ - información general sobre la propia tabla, incluyendo particionado, agrupamiento y tamaño de la tabla. Visualizar detalles ayuda con la optimización de consultas
-- _Vista previa_ - datos de muestra en bruto de la tabla. Los datos presentados son equivalentes a ejecutar una declaración `SELECT *`
-
-## INFORMATION_SCHEMA
-
-BigQuery admite vistas definidas por el sistema y de solo lectura que proporcionan información de metadatos sobre los objetos de BigQuery. Se pueden consultar las vistas a través de SQL desde la interfaz de usuario de BigQuery o desde las Bibliotecas de Clientes.
-
-:::note
-
-Las consultas ejecutadas contra el `INFORMATION_SCHEMA` no pueden ser almacenadas en caché y **incurrirán** en cargos por procesamiento de datos por cada ejecución.
-
-:::
-
-Desde el Editor de BigQuery, la siguiente consulta listará todas las tablas en Hubble:
-
-<CodeExample>
-
-```sql
-# List all tables in Hubble
-#standardSQL
-select *
-from `crypto-stellar.crypto_stellar`.INFORMATION_SCHEMA.TABLES;
-```
-
-</CodeExample>
-
-Si quieres detalles sobre una tabla en particular, puedes devolver el esquema de la tabla:
-
-<CodeExample>
-
-```sql
-# List all columns for the accounts table
-select table_name,
-  column_name,
-  is_nullable,
-  data_type,
-  is_partitioning_column
-from `crypto-stellar.crypto_stellar`.INFORMATION_SCHEMA.COLUMNS
-where table_name = "accounts";
-```
-
-</CodeExample>
-
-Más sobre el `INFORMATION_SCHEMA` se puede encontrar [aquí](https://cloud.google.com/bigquery/docs/information-schema-intro).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/README.mdx
deleted file mode 100644
index 6b74bd7bff..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Catálogo de Datos
-sidebar_position: 200
----
-
-import DocCardList from "@theme/DocCardList";
-
-Ver toda la información del catálogo de datos de Hubble.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/_category_.json
deleted file mode 100644
index 9e3a55f459..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/README.mdx
deleted file mode 100644
index 0c1e7c8f67..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Diccionario de datos
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Los datos de Hubble están organizados en secciones bronce, plata y oro.
-
-- Bronce 🥉 - datos sin procesar y sin transformar de la red Stellar (por ejemplo, history_contract_events contiene todos los eventos de Stellar)
-- Plata 🥈 - datos decodificados, transformados y filtrados (por ejemplo, token_transfers contiene eventos de Stellar compatibles con SEP-41)
-- Oro 🥇 - análisis seleccionados con tablas agregadas amigables (por ejemplo, tvl_agg agrega las cantidades relevantes en eventos Stellar)
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/accounts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/accounts.mdx
deleted file mode 100644
index 634ae0f7b9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/accounts.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Cuentas
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                           |
-| --------------------- | ------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | account_id, closed_at                                                                                   |
-| Campo(s) de partición | batch_run_date (partición de MES)                                                                       |
-| Campo(s) agrupado(s)  | account_id, last_modified_ledger                                                                        |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.accounts) |
-
-## Detalles de la columna
-
-| Nombre                | Descripción                                                                                                                                                                                                                                                                                                                                                                                                      | Tipo de Dato    | Valores de Dominio                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ¿Requerido? | Notas                                                                                                                                                                                                                                                                                                                                                                                                              |
-| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| account_id            | La dirección de la cuenta. La dirección es la clave pública de la cuenta codificada en base32. Todas las direcciones de cuentas comienzan con una `G`                                                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| saldo                 | El número de unidades de XLM que posee la cuenta                                                                                                                                                                                                                                                                                                                                                                 | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | La tabla `accounts` solo informa saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`.                                                                                                                                                                                                                                                                                  |
-| buying_liabilities    | La suma de todas las ofertas de compra que posee esta cuenta solo para XLM                                                                                                                                                                                                                                                                                                                                       | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | La tabla `accounts` solo informa saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`. Para ofertas de compra, la cuenta debe poseer la cantidad de activo para completar la transacción                                                                                                                                                                                |
-| selling_liabilities   | La suma de todas las ofertas de venta que posee esta cuenta solo para XLM                                                                                                                                                                                                                                                                                                                                        | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | La tabla `accounts` solo informa saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`.                                                                                                                                                                                                                                                                                  |
-| sequence_number       | El número de secuencia actual de la cuenta. El número de secuencia controla las operaciones aplicadas a una cuenta. Las operaciones deben someter un número de secuencia único que se incrementa en 1 para aplicar la operación a la cuenta, de modo que los cambios en la cuenta no colisionen dentro de un ledger                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| num_subentries        | El número total de entradas de ledger conectadas a esta cuenta. Las entradas de ledger incluyen: trustlines, ofertas, firmantes y entradas de datos. (Los saldos reclamables se cuentan bajo las entradas patrocinadoras, no como subentradas). Cualquier trustline, oferta, firmante o entrada de datos recién creada aumentará el número de subentradas en 1. Las cuentas pueden tener hasta 1.000 subentradas | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | Cada entrada en un ledger ocupa espacio, que es costoso de almacenar en el blockchain. Para cada entrada, se requiere que una cuenta mantenga un [saldo mínimo de XLM](https://developers.stellar.org/docs/learn/glossary#minimum-balance). La reserva se calcula mediante (2 + num_subentries - num_sponsoring + num_sponsored) \* 0.5XLM                                                                         |
-| inflation_destination | Obsoleto: La dirección de la cuenta para recibir un pago de inflación cuando se distribuyen en la red.                                                                                                                                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | La inflación se descontinuó en 2019 por voto de los validadores.                                                                                                                                                                                                                                                                                                                                                   |
-| flags                 | Denota la habilitación y deshabilitación de ciertos privilegios del emisor de activos                                                                                                                                                                                                                                                                                                                            | entero          | <ul><li>0 - Ninguno, Predeterminado</li><li>1 - Autenticación Requerida (todas las trustlines por defecto son no confiables y requieren autenticación manual)</li><li>2 - Autenticación Revocable (permite que las trustlines sean revocadas si la cuenta ya no confía en el activo)</li><li>4 - Autenticación Inmutable (todas las flags de autenticación son de solo lectura cuando se establecen)</li><li>8 - Clawback de Autenticación Activado (el activo puede ser recuperado del usuario)</li></ul> | Sí          | Las flags se establecen en las cuentas emisoras de un activo. Cuando las cuentas de usuario confían en un activo, las flags aplicadas al activo provienen de esta cuenta                                                                                                                                                                                                                                           |
-| home_domain           | El dominio que aloja el archivo stellar.toml de esta cuenta                                                                                                                                                                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | Solo aplica a cuentas emisoras de activos. El archivo stellar.toml contiene metadatos sobre el emisor del activo que ayudan a identificar quién es el emisor e instilan confianza en el activo                                                                                                                                                                                                                     |
-| master_weight         | El peso de la clave maestra, que es la clave privada para esta cuenta. Si una clave maestra es `0`, la cuenta está bloqueada y no se puede utilizar.                                                                                                                                                                                                                                                             | entero          | Enteros de 1 a 255                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| threshold_low         | La suma de los pesos de todas las firmas que firman una transacción para la operación de umbral bajo. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | Cada operación cae bajo una categoría de umbral específico: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito (esto es una medida de seguridad) Baja Seguridad: Permitir Confianza, Establecer Flags de Trust Line, Aumentar Secuencia y Reclamar Saldo Reclamable Seguridad Media: Todo lo demás Alta Seguridad: Fusión de Cuentas, Establecer Opciones |
-| threshold_medium      | La suma de los pesos de todas las firmas que firman una transacción para la operación de umbral medio. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                             | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | Cada operación cae bajo una categoría de umbral específico: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito (esto es una medida de seguridad) Baja Seguridad: Permitir Confianza, Establecer Flags de Trust Line, Aumentar Secuencia y Reclamar Saldo Reclamable Seguridad Media: Todo lo demás Alta Seguridad: Fusión de Cuentas, Establecer Opciones |
-| threshold_high        | La suma de los pesos de todas las firmas que firman una transacción para la operación de umbral alto. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | Cada operación cae bajo una categoría de umbral específico: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito (esto es una medida de seguridad) Baja Seguridad: Permitir Confianza, Establecer Flags de Trust Line, Aumentar Secuencia y Reclamar Saldo Reclamable Seguridad Media: Todo lo demás Alta Seguridad: Fusión de Cuentas, Establecer Opciones |
-| last_modified_ledger  | El número de secuencia del ledger cuando se modificó la entrada en el ledger (este firmante único para la cuenta). Las eliminaciones no cuentan como modificaciones y reportarán el número de secuencia de la modificación previa                                                                                                                                                                                | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | Si una cuenta actualiza el peso de un firmante en la secuencia 1234 y luego decide eliminar el firmante en 2345, el registro eliminado aún tendrá una secuencia modificada de 1234.                                                                                                                                                                                                                                |
-| ledger_entry_change   | Código que describe el tipo de cambio de la entrada en el ledger que se aplicó a la entrada del ledger.                                                                                                                                                                                                                                                                                                          | entero          | <ul><li>0 - Entrada de Ledger Creada</li><li>1 - Entrada de Ledger Actualizada</li><li>2 - Entrada de Ledger Eliminada</li><li>3 - Estado de la Entrada de Ledger (valor de la entrada)</li></ul>                                                                                                                                                                                                                                                                                                          | Sí          | Los tipos de cambio de entrada válidos son 0, 1 y 2 para entradas de ledger del tipo `accounts`                                                                                                                                                                                                                                                                                                                    |
-| deleted               | Indica si la entrada del ledger (id de cuenta) ha sido eliminada o no. Una vez que se elimina una entrada, no se puede recuperar.                                                                                                                                                                                                                                                                                | booleano        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| closed_at             | Marca de tiempo en UTC cuando este ledger se cerró y se comprometió a la red. Se espera que los ledgers cierren aproximadamente cada 5 segundos                                                                                                                                                                                                                                                                  | marca de tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ledger_sequence       | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que se incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.                                                                                                                                                   | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| batch_id              | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los ids de lotes son únicos para el lote y ayudan con la monitorización y capacidades de reejecución                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| batch_run_date        | La fecha de inicio del intervalo del lote. Tomado junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de closed_at para un ledger.                                                                                                                                                                               | fecha y hora    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | La tabla está particionada en batch_run_date. Se recomienda siempre incluir el batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta.                                                                                                                                                                                                                                            |
-| batch_insert_ts       | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de una restauración                                                                                                                                                                                                             | marca de tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| sponsor               | La dirección de la cuenta del patrocinador que está pagando las reservas para esta cuenta.                                                                                                                                                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                    |
-| num_sponsored         | El número de reservas patrocinadas para esta cuenta (lo que significa que otra cuenta está pagando el saldo mínimo). Las entradas patrocinadas no incurren en ningún requisito de reserva en la cuenta que posee la entrada.                                                                                                                                                                                     | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Predeterminado a 0 Las cuentas, ofertas, trustlines, datos y firmantes pueden ser opcionalmente patrocinados. Los Saldos Reclamables deben ser patrocinados. Consulta más información sobre el patrocinio [aquí](https://developers.stellar.org/docs/learn/encyclopedia/transactions-specialized/sponsored-reserves).                                                                                              |
-| num_sponsoring        | El número de reservas patrocinadas por esta cuenta. Las entradas patrocinadas por esta cuenta incurren en un requisito de reserva                                                                                                                                                                                                                                                                                | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Por defecto es 0. Las cuentas, ofertas, líneas de confianza, datos y firmantes pueden ser patrocinados opcionalmente. Los saldos reclamables deben ser patrocinados. Consulta más información sobre el patrocinio [aquí](https://developers.stellar.org/docs/learn/encyclopedia/transactions-specialized/sponsored-reserves).                                                                                      |
-| sequence_ledger       | El número de ledger de 32 bits sin firmar de la antigüedad del número de secuencia                                                                                                                                                                                                                                                                                                                               | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Refleja la última vez que una cuenta tocó su número de secuencia. Ten en cuenta que incluso si la operación de Aumento de Secuencia no tiene efecto, es decir, no aumenta el número de secuencia, sigue contando como un "toque"                                                                                                                                                                                   |
-| sequence_time         | La marca de tiempo UNIX de la antigüedad del número de secuencia                                                                                                                                                                                                                                                                                                                                                 | timestamp       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Refleja la última vez que una cuenta tocó su número de secuencia. Ten en cuenta que incluso si la operación de Aumento de Secuencia no tiene efecto, es decir, no aumenta el número de secuencia, sigue contando como un "toque"                                                                                                                                                                                   |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/README.mdx
deleted file mode 100644
index a9ad61c014..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Bronce 🥉
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Datos sin procesar y sin transformar de la red Stellar. Estas tablas desglosan y organizan el ledger Metadata en una serie de tablas útiles como dividir el ledger Metadata en las tablas history_ledgers, history_transactions y history_operations.
-
-## Cuándo usarlo
-
-Estas tablas son las mejores para profundizar en datos sin procesar de Stellar cuando se necesita un filtrado personalizado específico.
-
-Un ejemplo es recuperar y analizar las entradas de datos de un contrato específico usando la tabla `contract_data`.
-
-Por favor, verifica si alguna de las tablas silver y gold funciona para tu caso de uso antes de usar las tablas bronze, ya que pueden generar costos más altos en BigQuery debido a su tamaño.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.mdx
deleted file mode 100644
index ba81b49d32..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/account-signers.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Firmantes de la cuenta
-sidebar_position: 11
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                  |
-| --------------------- | -------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | account_id, signer, closed_at                                                                                  |
-| Campo(s) de partición | batch_run_date (partición MENSUAL)                                                                             |
-| Campo(s) agrupado(s)  | account_id, signer, last_modified_ledger                                                                       |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.account_signers) |
-
-## Detalles de columnas
-
-| Nombre               | Descripción                                                                                                                                                                                                                                              | Tipo de dato | Valores de dominio | ¿Requerido? | Notas |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ | ----------- | ----- |
-| account_id           | El identificador único de la cuenta.                                                                                                                                                                                                                     | string       |                    | Sí          |       |
-| signer               | La dirección de la cuenta autorizada para firmar (autorizar) transacciones en nombre de otra cuenta. Este proceso se denomina multi-sig.                                                                                                                 | string       |                    | Sí          |       |
-| weight               | El peso numérico del firmante. Todos los pesos en una transacción se suman para determinar si la transacción cumple con el umbral requerido para ser completada.                                                                                         | float        |                    | Sí          |       |
-| sponsor              | La dirección de la cuenta del patrocinador que paga las reservas de esta entrada del ledger.                                                                                                                                                             | string       |                    | No          |       |
-| last_modified_ledger | El número de secuencia del ledger cuando se modificó la entrada del ledger (este firmante único para la cuenta). Las eliminaciones no cuentan como modificaciones y mostrarán el número de secuencia de la modificación previa.                          | integer      |                    | Sí          |       |
-| ledger_entry_change  | Código que describe el tipo de cambio aplicado a la entrada del ledger.                                                                                                                                                                                  | integer      |                    | Sí          |       |
-| deleted              | Indica si la entrada del ledger (balance id) ha sido eliminada o no. Una vez eliminada una entrada, no puede recuperarse.                                                                                                                                | boolean      |                    | Sí          |       |
-| batch_id             | Representación en cadena del ID de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los IDs de batch son únicos para cada lote y ayudan en el monitoreo y capacidades de reejecución.                  | string       |                    | Sí          |       |
-| batch_run_date       | La fecha de inicio para el intervalo del batch. Cuando se toma junto con la fecha en batch_id, representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede considerarse un sustituto de closed_at para un ledger.               | datetime     |                    | Sí          |       |
-| batch_insert_ts      | El timestamp en UTC cuando un lote de registros fue insertado en la base de datos. Este campo ayuda a identificar si un lote se ejecutó en tiempo real o como parte de un relleno (backfill).                                                            | timestamp    |                    | Sí          |       |
-| closed_at            | Timestamp en UTC cuando este ledger se cerró y comprometió en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos.                                                                                                              | timestamp    |                    | Sí          |       |
-| ledger_sequence      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto. | integer      |                    | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.mdx
deleted file mode 100644
index 056d62c408..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/accounts.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Cuentas
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                           |
-| --------------------- | ------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | account_id, closed_at                                                                                   |
-| Campo(s) de partición | batch_run_date (partición MENSUAL)                                                                      |
-| Campo(s) agrupado(s)  | account_id, last_modified_ledger                                                                        |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.accounts) |
-
-## Detalles de columnas
-
-| Nombre                | Descripción                                                                                                                                                                                                                                                                                                                                                                                              | Tipo de dato    | Valores de dominio                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | ¿Requerido? | Notas                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| account_id            | La dirección de la cuenta. La dirección es la clave pública de la cuenta codificada en base32. Todas las direcciones de cuenta comienzan con una `G`                                                                                                                                                                                                                                                     | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| balance               | La cantidad de unidades de XLM que posee la cuenta                                                                                                                                                                                                                                                                                                                                                       | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | La tabla `accounts` solo informa saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`.                                                                                                                                                                                                                                                                                          |
-| buying_liabilities    | La suma de todas las ofertas de compra que posee esta cuenta solo para XLM                                                                                                                                                                                                                                                                                                                               | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | La tabla `accounts` solo informa saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`. Para las ofertas de compra, la cuenta debe poseer la cantidad de activo para completar la transacción                                                                                                                                                                                    |
-| selling_liabilities   | La suma de todas las ofertas de venta que posee esta cuenta solo para XLM                                                                                                                                                                                                                                                                                                                                | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | La tabla `accounts` solo informa saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`.                                                                                                                                                                                                                                                                                          |
-| sequence_number       | El número de secuencia actual de la cuenta. El número de secuencia controla las operaciones aplicadas a una cuenta. Las operaciones deben enviar un número de secuencia único que se incremente en 1 para aplicar la operación a la cuenta y evitar colisiones dentro de un ledger.                                                                                                                      | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| num_subentries        | El número total de entradas de ledger vinculadas a esta cuenta. Las entradas de ledger incluyen: trustlines, ofertas, firmantes y entradas de datos. (Los saldos reclamables se cuentan bajo entradas patrocinadas, no subentradas). Cualquier trustline, oferta, firmante o entrada de datos recién creada incrementará el número de subentradas en 1. Las cuentas pueden tener hasta 1,000 subentradas | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | Cada entrada en un ledger ocupa espacio, lo cual es costoso almacenar en la blockchain. Para cada entrada, se requiere que una cuenta mantenga un [saldo mínimo de XLM](../../../../../../learn/glossary.mdx#minimum-balance). La reserva se calcula con (2 + num_subentries - num_sponsoring + num_sponsored) \* 0.5XLM                                                                                                   |
-| inflation_destination | Obsoleto: La dirección de la cuenta que recibe el pago de inflación cuando se distribuye en la red.                                                                                                                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | La inflación fue descontinuada en 2019 por voto de los validadores.                                                                                                                                                                                                                                                                                                                                                        |
-| flags                 | Indica la habilitación y deshabilitación de ciertos privilegios del emisor del activo                                                                                                                                                                                                                                                                                                                    | entero          | <ul><li>0 - Ninguno, por defecto</li><li>1 - Autenticación requerida (todas las trustlines por defecto no son confiables y requieren confianza manual)</li><li>2 - Autenticación revocable (permite revocar trustlines si la cuenta ya no confía en el activo)</li><li>4 - Autenticación inmutable (todas las flags de autenticación son de solo lectura cuando están activadas)</li><li>8 - Autenticación de recuperación habilitada (el activo puede ser recuperado del usuario)</li></ul> | Sí          | Las flags se establecen en las cuentas emisoras para un activo. Cuando las cuentas de usuario confían en un activo, las flags aplicadas al activo se originan en esta cuenta                                                                                                                                                                                                                                               |
-| home_domain           | El dominio que aloja el archivo stellar.toml de esta cuenta                                                                                                                                                                                                                                                                                                                                              | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | Solo aplica a cuentas emisoras de activos. El archivo stellar.toml contiene metadatos sobre el emisor del activo que ayudan a identificar quién es el emisor e infunden confianza en el activo                                                                                                                                                                                                                             |
-| master_weight         | El peso de la clave maestra, que es la clave privada de esta cuenta. Si la clave maestra es `0`, la cuenta está bloqueada y no puede usarse.                                                                                                                                                                                                                                                             | entero          | Enteros del 1 al 255                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| threshold_low         | La suma del peso de todas las firmas que firman una transacción para la operación de umbral bajo. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                          | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | Cada operación corresponde a una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegios que una operación necesita para tener éxito (esto es una medida de seguridad) Seguridad baja: Permitir confianza, establecer flags de trust line, incrementar secuencia y reclamar saldo reclamable Seguridad media: Todo lo demás Seguridad alta: Fusión de cuenta, establecer opciones |
-| threshold_medium      | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                         | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | Cada operación corresponde a una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegios que una operación necesita para tener éxito (esto es una medida de seguridad) Seguridad baja: Permitir confianza, establecer flags de trust line, incrementar secuencia y reclamar saldo reclamable Seguridad media: Todo lo demás Seguridad alta: Fusión de cuenta, establecer opciones |
-| threshold_high        | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                          | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | Cada operación corresponde a una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegios que una operación necesita para tener éxito (esto es una medida de seguridad) Seguridad baja: Permitir confianza, establecer flags de trust line, incrementar secuencia y reclamar saldo reclamable Seguridad media: Todo lo demás Seguridad alta: Fusión de cuenta, establecer opciones |
-| last_modified_ledger  | El número de secuencia del ledger cuando la entrada del ledger (este firmante único para la cuenta) fue modificada. Las eliminaciones no cuentan como una modificación y reportarán el número de secuencia de modificación previo                                                                                                                                                                        | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | Si una cuenta actualiza el peso de un firmante en la secuencia 1234 y luego decide eliminar al firmante en 2345, el registro eliminado todavía tendrá una secuencia modificada de 1234.                                                                                                                                                                                                                                    |
-| ledger_entry_change   | Código que describe el tipo de cambio aplicado a la entrada del ledger.                                                                                                                                                                                                                                                                                                                                  | entero          | <ul><li>0 - Entrada de ledger creada</li><li>1 - Entrada de ledger actualizada</li><li>2 - Entrada de ledger eliminada</li><li>3 - Estado de entrada de ledger (valor de la entrada)</li></ul>                                                                                                                                                                                                                                                                                               | Sí          | Los tipos válidos de cambio de entrada son 0, 1 y 2 para entradas de ledger de tipo `accounts`                                                                                                                                                                                                                                                                                                                             |
-| deleted               | Indica si la entrada del ledger (ID de la cuenta) ha sido eliminada o no. Una vez que una entrada es eliminada, no se puede recuperar.                                                                                                                                                                                                                                                                   | booleano        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| closed_at             | Marca de tiempo en UTC cuando este ledger se cerró y confirmó en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                                                                                                                                                                            | marca de tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| ledger_sequence       | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que se incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.                                                                                                                                           | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| batch_id              | Representación en cadena del ID de ejecución para un DAG dado en Airflow. Tiene la forma `scheduled__<batch_end_date>-<dag_alias>`. Los batch IDs son únicos para el batch y ayudan con el monitoreo y la capacidad de reejecución                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| batch_run_date        | La fecha de inicio para el intervalo del batch. Cuando se combina con la fecha en batch_id, representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede considerarse como un proxy de closed_at para un ledger.                                                                                                                                                                 | fecha y hora    |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta.                                                                                                                                                                                                                                                      |
-| batch_insert_ts       | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de una reposición                                                                                                                                                                                                      | marca de tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| sponsor               | La dirección de la cuenta del patrocinador que está pagando las reservas para esta cuenta.                                                                                                                                                                                                                                                                                                               | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | No          |                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| num_sponsored         | El número de reservas patrocinadas para esta cuenta (es decir, otra cuenta está pagando el saldo mínimo). Las entradas patrocinadas no incurren en ningún requisito de reserva para la cuenta propietaria de la entrada.                                                                                                                                                                                 | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | No          | Por defecto es 0 Las cuentas, ofertas, trustlines, datos y firmantes pueden estar opcionalmente patrocinados. Los saldos reclamables deben ser patrocinados. Consulta más información sobre el patrocinio [aquí](../../../../../../build/guides/transactions/sponsored-reserves.mdx).                                                                                                                                      |
-| num_sponsoring        | El número de reservas patrocinadas por esta cuenta. Las entradas patrocinadas por esta cuenta incurren en un requerimiento de reserva.                                                                                                                                                                                                                                                                   | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | No          | Por defecto es 0 Las cuentas, ofertas, trustlines, datos y firmantes pueden estar opcionalmente patrocinados. Los saldos reclamables deben ser patrocinados. Consulta más información sobre el patrocinio [aquí](../../../../../../build/guides/transactions/sponsored-reserves.mdx).                                                                                                                                      |
-| sequence_ledger       | El número de ledger de 32 bits sin signo de la antigüedad del número de secuencia                                                                                                                                                                                                                                                                                                                        | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | No          | Refleja la última vez que una cuenta tocó su número de secuencia. Ten en cuenta que incluso si la operación de Incrementar Secuencia no tiene efecto, por ejemplo no incrementa el número de secuencia, aún cuenta como un "toque"                                                                                                                                                                                         |
-| sequence_time         | La marca de tiempo UNIX de la antigüedad del número de secuencia                                                                                                                                                                                                                                                                                                                                         | marca de tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | No          | Refleja la última vez que una cuenta tocó su número de secuencia. Ten en cuenta que incluso si la operación de Incrementar Secuencia no tiene efecto, por ejemplo no incrementa el número de secuencia, aún cuenta como un "toque"                                                                                                                                                                                         |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx
deleted file mode 100644
index a23d0cb6d7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/claimable-balances.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Saldos Reclamables
-sidebar_position: 20
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                     |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | balance_id, closed_at                                                                                             |
-| Campo(s) de Partición | batch_run_date (partición MES)                                                                                    |
-| Campo(s) Clustered    | asset_id, last_modified_ledger                                                                                    |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.claimable_balances) |
-
-## Detalles de la Columna
-
-| Nombre                               | Descripción                                                                                                                                                                                                                                                 | Tipo de Datos | Valores del Dominio                                                                                                                                                                            | ¿Requerido? | Notas                                                                                                                                                                                                      |
-| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| balance_id                           | Un identificador único para este saldo reclamable. El Balance id es una compilación de `Balance Type` + `SHA-256 hash history_operation_id`                                                                                                                 | string        |                                                                                                                                                                                                | Sí          | El Balance Type está fijado en V0, `00000000`. Si hay un cambio en el protocolo que impacte materialmente la mecánica de los saldos reclamables, el tipo de balance se actualizaría a V1.                  |
-| claimants                            | La lista de entradas que pueden reclamar el saldo y las precondiciones que deben cumplirse para reclamarlo.                                                                                                                                                 | array[record] |                                                                                                                                                                                                | Sí          | Se pueden especificar varias cuentas en el registro de claimants, incluyendo la cuenta del creador del saldo.                                                                                              |
-| claimants.destination                | La id de cuenta que puede reclamar el saldo                                                                                                                                                                                                                 | string        |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| claimants.predicate                  | La condición que debe cumplirse para que la cuenta destino pueda reclamar el saldo. La condición puede incluir reglas lógicas usando lógica AND, OR y NOT.                                                                                                  | array[record] |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| claimants.predicate.unconditional    | Si es true significa que esta cláusula de la condición siempre se cumple                                                                                                                                                                                    | boolean       |                                                                                                                                                                                                | No          | Cuando la condición es solo unconditional = true, significa que el saldo puede reclamarse bajo cualquier condición                                                                                         |
-| claimants.predicate.abs_before       | Fecha límite para reclamar el saldo. Si un saldo se reclama antes de esa fecha, entonces la cláusula de la condición se cumple.                                                                                                                             | string        |                                                                                                                                                                                                | No          |                                                                                                                                                                                                            |
-| claimants.predicate.rel_before       | Una fecha límite relativa para cuando el saldo reclamable puede ser reclamado. El valor representa el número de segundos desde la hora de cierre del ledger que creó el saldo reclamable                                                                    | integer       |                                                                                                                                                                                                | No          | Esta condición es útil al crear límites basados en condiciones de creación de tiempo. Si el creador quería un saldo solo reclamable una semana después de la creación, esta condición cumpliría esa regla. |
-| claimants.predicate.abs_before_epoch | Un valor de época UNIX en segundos que representa la misma fecha límite que abs_before.                                                                                                                                                                     | integer       |                                                                                                                                                                                                | No          |                                                                                                                                                                                                            |
-| asset_type                           | El identificador del tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                  | string        | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                    | Sí          |                                                                                                                                                                                                            |
-| asset_code                           | La representación del código del activo en la red de 4 o 12 caracteres                                                                                                                                                                                      | string        |                                                                                                                                                                                                | No          |                                                                                                                                                                                                            |
-| asset_issuer                         | La dirección de la cuenta que creó el activo                                                                                                                                                                                                                | string        |                                                                                                                                                                                                | No          |                                                                                                                                                                                                            |
-| asset_amount                         | La cantidad del activo que puede ser reclamada                                                                                                                                                                                                              | float         |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| sponsor                              | La dirección de la cuenta del patrocinador que paga las reservas para este saldo reclamable                                                                                                                                                                 | string        |                                                                                                                                                                                                | No          | Los patrocinadores de los saldos reclamables son los creadores del saldo.                                                                                                                                  |
-| flags                                | Indica la activación y desactivación de ciertos privilegios del emisor del balance                                                                                                                                                                          | integer       | <ul><li>0 - Ninguno, por defecto</li><li>1 - Autorización para Clawback habilitada</li></ul>                                                                                                   | Sí          | Los flags son establecidos por las cuentas de saldos reclamables para un activo. Cuando cuentas de usuarios reclaman un saldo, los flags aplicados al activo se originan en esta cuenta                    |
-| last_modified_ledger                 | El número de secuencia del ledger cuando se modificó la entrada del ledger (este firmante único para la cuenta). Las eliminaciones no cuentan como modificaciones y reportarán el número de secuencia de modificación previo                                | integer       |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| ledger_entry_change                  | Código que describe el tipo de cambio aplicado a la entrada del ledger.                                                                                                                                                                                     | integer       | <ul><li>0 - Entrada de Ledger creada</li><li>1 - Entrada de Ledger actualizada</li><li>2 - Entrada de Ledger eliminada</li><li>3 - Estado de Entrada de Ledger (valor de la entrada)</li></ul> | Sí          | Los tipos válidos de cambio de entrada son 0 y 2 para entradas de tipo `claimable_balances`. Una vez creado, un saldo no puede ser actualizado.                                                            |
-| deleted                              | Indica si la entrada del ledger (balance id) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede recuperarse.                                                                                                                            | boolean       |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| closed_at                            | Marca de tiempo en UTC cuando este ledger se cerró y confirmó en la red. Se espera que los ledgers cierren aproximadamente cada 5 segundos                                                                                                                  | timestamp     |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| ledger_sequence                      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto. | integer       |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| batch_id                             | Representación en cadena del run id para un DAG dado en Airflow. Tiene la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los batch ids son únicos para el lote y ayudan en la monitorización y capacidades de reejecución                              | string        |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| batch_run_date                       | La fecha de inicio para el intervalo del lote. Junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede considerarse como un proxy de closed_at para un ledger.                      | datetime      |                                                                                                                                                                                                | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta.                                      |
-| batch_insert_ts                      | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote fue ejecutado en tiempo real o como parte de una recarga                                                          | timestamp     |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                            |
-| asset_id                             | Identificador único para asset_code, asset_issuer                                                                                                                                                                                                           | integer       |                                                                                                                                                                                                | No          |                                                                                                                                                                                                            |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx
deleted file mode 100644
index 66fee890a2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/config-settings.mdx
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Configuración de ajustes
-sidebar_position: 31
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                  |
-| --------------------- | -------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | config_setting_id, closed_at                                                                                   |
-| Campo(s) de partición | closed_at (partición MENSUAL)                                                                                  |
-| Campo(s) agrupado(s)  | last_modified_ledger                                                                                           |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.config_settings) |
-
-## Detalles de columnas
-
-| Nombre                              | Descripción                                                                                                                                                                                                                                                     | Tipo de dato    | Valores del dominio | ¿Requerido? | Notas |
-| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------- | ----------- | ----- |
-| config_setting_id                   | Tipos de id de configuración                                                                                                                                                                                                                                    | entero          |                     | Sí          |       |
-| contract_max_size_bytes             | Tamaño máximo del contrato                                                                                                                                                                                                                                      | entero          |                     | No          |       |
-| ledger_max_instructions             | Máximo de instrucciones por ledger                                                                                                                                                                                                                              | entero          |                     | No          |       |
-| tx_max_instructions                 | Máximo de instrucciones por transacción                                                                                                                                                                                                                         | entero          |                     | No          |       |
-| fee_rate_per_instructions_increment | Tarifa por incremento de instrucciones                                                                                                                                                                                                                          | entero          |                     | No          |       |
-| tx_memory_limit                     | Límite de memoria por transacción                                                                                                                                                                                                                               | entero          |                     | No          |       |
-| ledger_max_read_ledger_entries      | Máximo de entradas leídas por ledger                                                                                                                                                                                                                            | entero          |                     | No          |       |
-| ledger_max_read_bytes               | Máximo de bytes leídos por ledger                                                                                                                                                                                                                               | entero          |                     | No          |       |
-| ledger_max_write_ledger_entries     | Máximo de entradas escritas por ledger                                                                                                                                                                                                                          | entero          |                     | No          |       |
-| ledger_max_write_bytes              | Máximo de bytes escritos por ledger                                                                                                                                                                                                                             | entero          |                     | No          |       |
-| tx_max_read_ledger_entries          | Máximo de entradas leídas por transacción                                                                                                                                                                                                                       | entero          |                     | No          |       |
-| tx_max_read_bytes                   | Máximo de bytes leídos por transacción                                                                                                                                                                                                                          | entero          |                     | No          |       |
-| tx_max_write_ledger_entries         | Máximo de entradas escritas por transacción                                                                                                                                                                                                                     | entero          |                     | No          |       |
-| tx_max_write_bytes                  | Máximo de bytes escritos por transacción                                                                                                                                                                                                                        | entero          |                     | No          |       |
-| fee_read_ledger_entry               | Tarifa por entrada leída del ledger                                                                                                                                                                                                                             | entero          |                     | No          |       |
-| fee_write_ledger_entry              | Tarifa por entrada escrita del ledger                                                                                                                                                                                                                           | entero          |                     | No          |       |
-| fee_read_1kb                        | Tarifa por cada 1kb leído                                                                                                                                                                                                                                       | entero          |                     | No          |       |
-| bucket_list_target_size_bytes       | Tamaño objetivo de la lista de buckets                                                                                                                                                                                                                          | entero          |                     | No          |       |
-| write_fee_1kb_bucket_list_low       | Tarifa de escritura para la lista de buckets por 1kb                                                                                                                                                                                                            | entero          |                     | No          |       |
-| write_fee_1kb_bucket_list_high      | Tarifa de escritura para la lista de buckets por 1kb                                                                                                                                                                                                            | entero          |                     | No          |       |
-| bucket_list_write_fee_growth_factor | Factor de crecimiento de la tarifa de escritura para la lista de buckets                                                                                                                                                                                        | entero          |                     | No          |       |
-| fee_historical_1kb                  | Tarifa por almacenamiento histórico por 1kb                                                                                                                                                                                                                     | entero          |                     | No          |       |
-| tx_max_contract_events_size_bytes   | Tamaño máximo de evento de contrato por transacción                                                                                                                                                                                                             | entero          |                     | No          |       |
-| fee_contract_events_1kb             | Tarifa por tamaño de evento de contrato por 1kb                                                                                                                                                                                                                 | entero          |                     | No          |       |
-| ledger_max_txs_size_bytes           | Tamaño máximo de transacciones por ledger                                                                                                                                                                                                                       | entero          |                     | No          |       |
-| tx_max_size_bytes                   | Tamaño máximo de transacción                                                                                                                                                                                                                                    | entero          |                     | No          |       |
-| fee_tx_size_1kb                     | Tarifa por tamaño de transacción por 1kb                                                                                                                                                                                                                        | entero          |                     | No          |       |
-| contract_cost_params_cpu_insns      | Parámetros del modelo constante y lineal para costos de CPU                                                                                                                                                                                                     | entero          |                     | No          |       |
-| contract_cost_params_mem_bytes      | Parámetros del modelo constante y lineal para costos de memoria                                                                                                                                                                                                 | entero          |                     | No          |       |
-| contract_data_key_size_bytes        | Tamaño máximo de claves de datos de contrato                                                                                                                                                                                                                    | entero          |                     | No          |       |
-| contract_data_entry_size_bytes      | Tamaño máximo de entradas de datos de contrato                                                                                                                                                                                                                  | entero          |                     | No          |       |
-| max_entry_ttl                       | TTL máximo que se puede establecer para una entrada (secuencia creada en + este)                                                                                                                                                                                | entero          |                     | No          |       |
-| min_temp_entry_ttl                  | TTL mínimo temporal de entrada (secuencia creada en + este)                                                                                                                                                                                                     | entero          |                     | No          |       |
-| min_persistent_entry_ttl            | TTL mínimo persistente de entrada (secuencia creada en + este)                                                                                                                                                                                                  | entero          |                     | No          |       |
-| auto_bump_ledgers                   | Cantidad automática de ledgers para incrementar                                                                                                                                                                                                                 | entero          |                     | No          |       |
-| persistent_rent_rate_denominator    | Denominador de la tasa de renta para entradas persistentes                                                                                                                                                                                                      | entero          |                     | No          |       |
-| temp_rent_rate_denominator          | Denominador de la tasa de renta para entradas temporales                                                                                                                                                                                                        | entero          |                     | No          |       |
-| max_entries_to_ttl                  | Máximo de entradas para TTL                                                                                                                                                                                                                                     | entero          |                     | No          |       |
-| bucket_list_size_window_sample_size | Tamaño de muestra de ventana para el tamaño de la lista de buckets                                                                                                                                                                                              | entero          |                     | No          |       |
-| eviction_scan_size                  | Tamaño del escaneo de desalojo                                                                                                                                                                                                                                  | entero          |                     | No          |       |
-| starting_eviction_scan_level        | Nivel inicial de escaneo de desalojo                                                                                                                                                                                                                            | entero          |                     | No          |       |
-| ledger_max_tx_count                 | Máximo de transacciones en un ledger                                                                                                                                                                                                                            | entero          |                     | No          |       |
-| bucket_list_size_window             | Ventana de tamaño de la lista de buckets                                                                                                                                                                                                                        | entero          |                     | No          |       |
-| min_temporary_ttl                   | Número mínimo de entradas para las que una entrada temporal puede vivir en el ledger                                                                                                                                                                            | entero          |                     | No          |       |
-| min_persistent_ttl                  | Número mínimo de entradas para las que una entrada persistente puede vivir en el ledger                                                                                                                                                                         | entero          |                     | No          |       |
-| max_entries_to_archive              | Número máximo de entradas que generan meta archivística en un solo ledger                                                                                                                                                                                       | entero          |                     | No          |       |
-| last_modified_ledger                | Número de secuencia del ledger cuando la entrada del ledger (este firmante único para la cuenta) fue modificada. Las eliminaciones no se cuentan como modificiación y reportarán el número de secuencia de la modificación anterior.                            | entero          |                     | Sí          |       |
-| ledger_entry_change                 | Código que describe el tipo de cambio aplicado a la entrada del ledger.                                                                                                                                                                                         | entero          |                     | Sí          |       |
-| deleted                             | Indica si la entrada del ledger (id del balance) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede recuperarse.                                                                                                                            | booleano        |                     | Sí          |       |
-| batch_id                            | Representación en cadena del id de ejecución para un DAG dado en Airflow. Tiene la forma `scheduled__<batch_end_date>-<dag_alias>`. Los ids de batch son únicos para el batch y ayudan en la monitorización y las capacidades de reejecución.                   | cadena          |                     | Sí          |       |
-| batch_run_date                      | La fecha de inicio para el intervalo del batch. Cuando se toma junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger.                | datetime        |                     | Sí          |       |
-| batch_insert_ts                     | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un relleno posterior.                                                      | marca de tiempo |                     | Sí          |       |
-| closed_at                           | Marca de tiempo en UTC cuando este ledger se cerró y se confirmó en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos.                                                                                                               | marca de tiempo |                     | Sí          |       |
-| ledger_sequence                     | El número de secuencia de este ledger. Representa el orden del ledger dentro de la cadena de bloques Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto. | entero          |                     | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx
deleted file mode 100644
index 5db744087f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-code.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Código de Contrato
-sidebar_position: 30
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                |
-| --------------------- | ------------------------------------------------------------------------------------------------------------ |
-| Clave Natural(s)      | contract_code_hash, closed_at                                                                                |
-| Campo(s) de Partición | closed_at (partición por MES)                                                                                |
-| Campo(s) Agrupados    | last_modified_ledger, contract_code_hash                                                                     |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.contract_code) |
-
-## Detalles de la Columna
-
-| Nombre               | Descripción                                                                                                                                                                                                                                                 | Tipo de Datos | Valores del Dominio | ¿Requerido? | Notas |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------------------- | ----------- | ----- |
-| contract_code_hash   | Hash del código del contrato Soroban                                                                                                                                                                                                                        | cadena        |                     | Sí          |       |
-| contract_code_ext_v  | Versión de extensión del código del contrato                                                                                                                                                                                                                | entero        |                     |             |       |
-| last_modified_ledger | El número de secuencia del ledger cuando se modificó la entrada del ledger (este firmante único para la cuenta). Las eliminaciones no cuentan como una modificación y reportarán el número de secuencia de modificación anterior                            | entero        |                     | Sí          |       |
-| ledger_entry_change  | Código que describe el tipo de cambio aplicado a la entrada del ledger.                                                                                                                                                                                     | entero        |                     | Sí          |       |
-| deleted              | Indica si la entrada del ledger (id de saldo) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede recuperarse.                                                                                                                           | booleano      |                     | Sí          |       |
-| batch_id             | Representación en cadena del run id para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los batch ids son únicos para el batch y ayudan con el monitoreo y capacidades de reejecución                                  | cadena        |                     | Sí          |       |
-| batch_run_date       | La fecha de inicio para el intervalo del batch. Cuando se combina con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede considerarse como un proxy de closed_at para un ledger.        | datetime      |                     | Sí          |       |
-| batch_insert_ts      | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un relleno posterior                                                   | timestamp     |                     | Sí          |       |
-| closed_at            | Marca de tiempo en UTC cuando este ledger se cerró y se comprometió en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                         | timestamp     |                     | Sí          |       |
-| ledger_sequence      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto. | entero        |                     | Sí          |       |
-| ledger_key_hash      | Hash de la clave del ledger usado para identificar datos de contrato o entradas del ledger de código de contrato que están expirando                                                                                                                        | cadena        |                     | Sí          |       |
-| n_instructions       | Número de instrucciones en el código del contrato                                                                                                                                                                                                           | entero        |                     |             |       |
-| n_functions          | Número de funciones en el código del contrato                                                                                                                                                                                                               | entero        |                     |             |       |
-| n_globals            | Número de variables globales en el código del contrato                                                                                                                                                                                                      | entero        |                     |             |       |
-| n_table_entries      | Número de entradas en la tabla del código del contrato                                                                                                                                                                                                      | entero        |                     |             |       |
-| n_types              | Número de tipos en el código del contrato                                                                                                                                                                                                                   | entero        |                     |             |       |
-| n_data_segments      | Número de segmentos de datos en el código del contrato                                                                                                                                                                                                      | entero        |                     |             |       |
-| n_elem_segments      | Número de segmentos de elementos en el código del contrato                                                                                                                                                                                                  | entero        |                     |             |       |
-| n_imports            | Número de importaciones en el código del contrato                                                                                                                                                                                                           | entero        |                     |             |       |
-| n_exports            | Número de exportaciones en el código del contrato                                                                                                                                                                                                           | entero        |                     |             |       |
-| n_data_segment_bytes | Número de bytes de segmentos de datos en el código del contrato                                                                                                                                                                                             | entero        |                     |             |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx
deleted file mode 100644
index 0a2106d2f5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/contract-data.mdx
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Datos del Contrato
-sidebar_position: 40
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                |
-| --------------------- | ------------------------------------------------------------------------------------------------------------ |
-| Clave(s) Natural(es)  | ledger_key_hash, closed_at                                                                                   |
-| Campo(s) de Partición | closed_at (partición MES)                                                                                    |
-| Campo(s) Agrupado(s)  | last_modified_ledger, contract_id                                                                            |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.contract_data) |
-
-## Detalles de las Columnas
-
-| Nombre               | Descripción                                                                                                                                                                                                                                                                                     | Tipo de Dato   | Valores del Dominio | ¿Requerido? | Notas |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ------------------- | ----------- | ----- |
-| contract_id          | ID del contrato Soroban                                                                                                                                                                                                                                                                         | cadena         |                     | Sí          |       |
-| contract_key_type    | Tipo de clave de contrato que es un ScVal que puede tener los siguientes valores                                                                                                                                                                                                                | cadena         |                     |             |       |
-| contract_durability  | El contrato puede ser temporal o persistente                                                                                                                                                                                                                                                    | cadena         |                     |             |       |
-| asset_code           | La representación del código del activo en la red, de 4 o 12 caracteres.                                                                                                                                                                                                                        | cadena         |                     |             |       |
-| asset_issuer         | La dirección de la cuenta del emisor original del activo que creó el activo.                                                                                                                                                                                                                    | cadena         |                     |             |       |
-| asset_type           | El identificador para el tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                   | cadena         |                     |             |       |
-| balance_holder       | La dirección/cuenta que posee el saldo del activo en los datos del contrato.                                                                                                                                                                                                                    | cadena         |                     |             |       |
-| balance              | La cantidad de unidades de XLM que posee la cuenta.                                                                                                                                                                                                                                             | cadena         |                     |             |       |
-| last_modified_ledger | El número de secuencia del ledger cuando se modificó la entrada del ledger (este firmante único para la cuenta). Las eliminaciones no cuentan como una modificación y mostrarán el número de secuencia de modificación previo.                                                                  | entero         |                     | Sí          |       |
-| ledger_entry_change  | Código que describe el tipo de cambio aplicado a la entrada del ledger.                                                                                                                                                                                                                         | entero         |                     | Sí          |       |
-| deleted              | Indica si la entrada del ledger (identificador del saldo) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede recuperarse.                                                                                                                                                   | booleano       |                     | Sí          |       |
-| batch_id             | Representación en cadena del run id para un DAG dado en Airflow. Tiene la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los ids de lote son únicos para cada lote y ayudan con la monitorización y capacidades de reejecución.                                                            | cadena         |                     | Sí          |       |
-| batch_run_date       | La fecha de inicio para el intervalo del lote. Junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede considerarse como un proxy de closed_at para un ledger.                                                          | fecha y hora   |                     | Sí          |       |
-| batch_insert_ts      | La marca temporal en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de una ejecución retroactiva.                                                                                   | marca temporal |                     | Sí          |       |
-| closed_at            | Marca temporal en UTC cuando este ledger cerró y fue confirmado en la red. Se espera que los ledgers cierren aproximadamente cada 5 segundos.                                                                                                                                                   | marca temporal |                     | Sí          |       |
-| ledger_sequence      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.                                     | entero         |                     | Sí          |       |
-| ledger_key_hash      | Hash de la clave del ledger utilizado para identificar entradas de ledger de datos de contrato o código de contrato caducando.                                                                                                                                                                  | cadena         |                     | Sí          |       |
-| key                  | La clave codificada usada para identificar un dato específico del contrato. La clave codificada tiene dos componentes (tipo y valor), donde tipo describe el tipo de dato y valor describe el valor codificado del tipo de dato para los datos del contrato.                                    | json           |                     |             |       |
-| key_decoded          | La versión legible o decodificada de la clave. Esto proporciona un formato comprensible de la clave, facilitando su interpretación y uso en análisis.                                                                                                                                           | json           |                     |             |       |
-| val                  | El valor codificado asociado con la clave en los datos del contrato. El valor codificado tiene dos componentes (tipo y valor), donde tipo describe el tipo de dato y valor describe el valor codificado del tipo de dato para los datos del contrato.                                           | json           |                     |             |       |
-| val_decoded          | La versión legible o decodificada del valor. Esto proporciona una representación clara y comprensible del valor, facilitando su interpretación y uso en análisis.                                                                                                                               | json           |                     |             |       |
-| contract_data_xdr    | La codificación XDR (Representación Externa de Datos) de los datos del contrato. XDR es un formato estándar usado para serializar y deserializar datos, asegurando interoperabilidad entre sistemas distintos. Este campo contiene los datos serializados en bruto del contrato en formato XDR. | cadena         |                     |             |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx
deleted file mode 100644
index 73124c2246..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/evicted-keys.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Claves desalojadas
-sidebar_position: 80
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                              |
-| --------------------- | ------------------------------------------------------------------------------------------ |
-| Clave(s) natural(es)  | ledger_key_hash, closed_at                                                                 |
-| Campo(s) de partición | N/A                                                                                        |
-| Campo(s) agrupado(s)  | N/A                                                                                        |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.evicted_keys) |
-
-## Detalles de columna
-
-| Nombre          | Descripción                                                                                                                                                                                                                                                                                 | Tipo de dato    | Valores del dominio | ¿Requerido? | Notas |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------- | ----------- | ----- |
-| ledger_key_hash | Hash de clave del libro contable usado para identificar los datos del contrato expirado o las entradas del código del contrato en el libro contable                                                                                                                                         | cadena          |                     | Sí          |       |
-| is_evicted      | Si es verdadero, el hash de clave del libro contable ha sido desalojado                                                                                                                                                                                                                     | booleano        |                     |             |       |
-| closed_at       | La marca de tiempo UNIX de la antigüedad del número de secuencia                                                                                                                                                                                                                            | marca de tiempo |                     | Sí          |       |
-| ledger_sequence | El número de secuencia de este libro contable. Representa el orden del libro contable dentro de la blockchain de Stellar. Cada libro contable tiene un número de secuencia único que incrementa con cada nuevo libro, asegurando que los libros contables se procesen en el orden correcto. | entero          |                     | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx
deleted file mode 100644
index e36d3881b5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-assets.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Historial de Activos
-sidebar_position: 90
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                         |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | asset_code, asset_issuer, asset_type                                                                                  |
-| Campo(s) de Partición | batch_run_date (partición de MES)                                                                                     |
-| Campo(s) Agrupados    | asset_code, asset_issuer, asset_type                                                                                  |
-| Documentación         | [dbt_docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_assets_staging) |
-
-## Detalles de la Columna
-
-| Nombre          | Descripción                                                                                                                                                                                                                                | Tipo de Dato | Valores de Dominio                                                          | ¿Requerido? | Notas                                                                                                                                                                 |
-| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | --------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| id              | Identificador único para la combinación de código de activo, tipo y emisor. Esto no es una clave primaria en la tabla                                                                                                                      | float        |                                                                             | Sí          | Obsoleto                                                                                                                                                              |
-| asset_id        | Identificador único para asset_code, asset_issuer                                                                                                                                                                                          | integer      |                                                                             | No          |                                                                                                                                                                       |
-| asset_type      | El identificador para el tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                             | string       | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul> | Sí          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y se mostrará con un tipo de activo 'native'                             |
-| asset_code      | La representación del código del activo en la red de 4 o 12 caracteres                                                                                                                                                                     | string       |                                                                             | No          | Los códigos de activos no garantizan unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto                                        |
-| asset_issuer    | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                | string       |                                                                             | No          |                                                                                                                                                                       |
-| batch_id        | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los batch ids son únicos para el batch y ayudan con el monitoreo y las capacidades de reejecución    | string       |                                                                             | Sí          |                                                                                                                                                                       |
-| batch_run_date  | La fecha de inicio para el intervalo del batch. Tomada junto con la fecha en el batch_id, esta fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger. | datetime     |                                                                             | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta. |
-| batch_insert_ts | El timestamp en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un relleno de datos (backfill)                              | timestamp    |                                                                             | Sí          |                                                                                                                                                                       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.mdx
deleted file mode 100644
index dc55bc2785..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-contract-events.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Eventos del Contrato de Historial
-sidebar_position: 95
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                          |
-| --------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| Llave(s) natural(es)  |                                                                                                                        |
-| Campo(s) de partición | closed_at (partición MENSUAL)                                                                                          |
-| Campo(s) agrupados    | contract_id                                                                                                            |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_contract_events) |
-
-## Detalles de la Columna
-
-| Nombre                      | Descripción                                                                                                                                                                                                                                                                                         | Tipo de datos   | Valores del Dominio                                                             | ¿Requerido? | Notas                                                                                                                                                                                      |
-| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| transaction_hash            | Un hash SHA-256 codificado en hexadecimal de la forma XDR codificada de esta transacción                                                                                                                                                                                                            | cadena          |                                                                                 |             |                                                                                                                                                                                            |
-| transaction_id              | El identificador de la transacción en la que se ejecutó la operación. Puede haber hasta 100 operaciones en una transacción dada                                                                                                                                                                     | entero          |                                                                                 | Sí          |                                                                                                                                                                                            |
-| successful                  | Indica si esta transacción fue exitosa o no                                                                                                                                                                                                                                                         | booleano        |                                                                                 | No          | El éxito de una transacción no indica si fue incluida y escrita en un ledger. Solo indica si las operaciones en la transacción se aplicaron con éxito para modificar el estado del ledger. |
-| in_successful_contract_call | Indica si el evento está dentro de una llamada de contrato exitosa o no                                                                                                                                                                                                                             | booleano        |                                                                                 | Sí          |                                                                                                                                                                                            |
-| contract_id                 |                                                                                                                                                                                                                                                                                                     | cadena          |                                                                                 |             |                                                                                                                                                                                            |
-| type                        | El tipo numérico del evento                                                                                                                                                                                                                                                                         | entero          | 0, 1, 2                                                                         | Sí          |                                                                                                                                                                                            |
-| type_string                 | El tipo de evento en cadena                                                                                                                                                                                                                                                                         | cadena          | ContractEventTypeSystem, ContractEventTypeDiagnostic, ContractEventTypeContract | Sí          |                                                                                                                                                                                            |
-| topics                      | La parte 'topics' de un evento contiene información identificativa y metadatos del evento y generalmente lo que el evento significa. Por ejemplo, para SAC esto podría ser un evento "transfer" que indica movimiento de valor de token. Los valores dentro de topics son XDR codificados en base64 | json            |                                                                                 | Sí          |                                                                                                                                                                                            |
-| topics_decoded              | Versión decodificada y legible para humanos del topic del evento                                                                                                                                                                                                                                    | json            |                                                                                 | Sí          |                                                                                                                                                                                            |
-| data                        | La parte de datos de un evento es un objeto que contiene el/los valor(es) significativo(s) para un evento. Por ejemplo, para SAC esto podría ser la "cantidad" del movimiento de token de un evento "transfer". Los valores dentro de topics son XDR codificados en base64                          | json            |                                                                                 | Sí          |                                                                                                                                                                                            |
-| data_decoded                | Versión decodificada y legible para humanos del objeto de datos del evento                                                                                                                                                                                                                          | json            |                                                                                 | Sí          |                                                                                                                                                                                            |
-| contract_event_xdr          | El XDR codificado en base64 del evento                                                                                                                                                                                                                                                              | cadena          |                                                                                 | Sí          |                                                                                                                                                                                            |
-| batch_id                    | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_[batch_end_date]-[dag_alias]". Los batch ids son únicos para el lote y ayudan con el monitoreo y las capacidades de reejecución                                                            | cadena          |                                                                                 | Sí          |                                                                                                                                                                                            |
-| batch_run_date              | La fecha de inicio para el intervalo del lote. Cuando se considera con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de closed_at para un ledger.                                                       | fecha y hora    |                                                                                 | Sí          |                                                                                                                                                                                            |
-| batch_insert_ts             | El timestamp en UTC cuando un batch de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de una recuperación                                                                                                    | marca de tiempo |                                                                                 | Sí          |                                                                                                                                                                                            |
-| closed_at                   | Marca de tiempo en UTC cuando este ledger se cerró y confirmó en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                                                                       | marca de tiempo |                                                                                 | Sí          |                                                                                                                                                                                            |
-| ledger_sequence             | El número de secuencia del ledger en el que se incluyó esta transacción                                                                                                                                                                                                                             | entero          |                                                                                 | Sí          |                                                                                                                                                                                            |
-| operation_id                | Identificador único de una operación.                                                                                                                                                                                                                                                               | entero          |                                                                                 | No          |                                                                                                                                                                                            |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.mdx
deleted file mode 100644
index ec02e25264..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-effects.mdx
+++ /dev/null
@@ -1,266 +0,0 @@
----
-title: Efectos de Historial
-sidebar_position: 100
-description: ""
----
-
-| Nombre                                          | Descripción                                                                                                                                                                                                                                                                                                                                                                                                               | Tipo de Dato | Valores del Dominio | ¿Clave Primaria? | ¿Clave Natural? | ¿Campo de Partición o Clúster? | ¿Requerido? | Notas |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------- | ---------------- | --------------- | ------------------------------ | ----------- | ----- |
-| dirección                                       | La dirección de la cuenta. La dirección es la clave pública de la cuenta codificada en base32. Todas las direcciones de cuenta comienzan con una \`G\`                                                                                                                                                                                                                                                                    | cadena       |                     |                  |                 | clúster                        |             |       |
-| address_muxed                                   | Dirección multiplexada                                                                                                                                                                                                                                                                                                                                                                                                    | cadena       |                     |                  |                 |                                |             |       |
-| operation_id                                    | Identificador único para una operación                                                                                                                                                                                                                                                                                                                                                                                    | entero       |                     |                  |                 | clúster                        |             |       |
-| tipo                                            | El número que indica qué tipo de efecto es                                                                                                                                                                                                                                                                                                                                                                                | entero       |                     |                  |                 | clúster                        |             |       |
-| type_string                                     | La cadena que indica qué tipo de efecto es                                                                                                                                                                                                                                                                                                                                                                                | cadena       |                     |                  |                 |                                |             |       |
-| detalles                                        | Objeto JSON no estructurado que contiene detalles según el tipo de efecto. Cada efecto devolverá sus propios detalles relevantes, el resto serán nulos                                                                                                                                                                                                                                                                    | registro     |                     |                  |                 |                                |             |       |
-| details.liquidity_pool                          | Los pools de liquidez proporcionan una forma simple y no interactiva de intercambiar grandes cantidades de capital y permiten altos volúmenes de trading                                                                                                                                                                                                                                                                  | registro     |                     |                  |                 |                                |             |       |
-| details.liquidity_pool.fee_bp                   | El número de puntos básicos cobrados como porcentaje de la operación para completar la transacción. Las tarifas ganadas en todas las operaciones se dividen entre los accionistas del pool y se distribuyen como incentivo para mantener dinero en los pools                                                                                                                                                              | entero       |                     |                  |                 |                                |             |       |
-| details.liquidity_pool.id                       | Identificador único para un pool de liquidez. No puede haber pools duplicados para el mismo par de activos. Una vez creado un pool para el par de activos, no se puede crear otro.                                                                                                                                                                                                                                        | cadena       |                     |                  |                 |                                |             |       |
-| details.liquidity_pool.total_shares             | Número total de acciones emitidas del pool                                                                                                                                                                                                                                                                                                                                                                                | numérico     |                     |                  |                 |                                |             |       |
-| details.liquidity_pool.total_trustlines         | Número de trustlines para las acciones asociadas del pool                                                                                                                                                                                                                                                                                                                                                                 | entero       |                     |                  |                 |                                |             |       |
-| details.liquidity_pool.type                     | El mecanismo que calcula el precio y la división de acciones para el pool. Con el lanzamiento inicial del AMM, el único tipo de pool de liquidez permitido para crear es un pool de producto constante.                                                                                                                                                                                                                   | cadena       |                     |                  |                 |                                |             |       |
-| details.liquidity_pool.reserves                 | Activo reservado en el pool de liquidez                                                                                                                                                                                                                                                                                                                                                                                   | registro     |                     |                  |                 |                                |             |       |
-| details.liquidity_pool.reserves.asset           | Activo de reserva                                                                                                                                                                                                                                                                                                                                                                                                         | cadena       |                     |                  |                 |                                |             |       |
-| details.liquidity_pool.reserves.amount          | Cantidad del activo de reserva                                                                                                                                                                                                                                                                                                                                                                                            | numérico     |                     |                  |                 |                                |             |       |
-| details.reserves_received                       | Cantidad de activo recibida por reservas de retiro de pool de liquidez                                                                                                                                                                                                                                                                                                                                                    | registro     |                     |                  |                 |                                |             |       |
-| details.reserves_received.asset                 | Activo recibido                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.reserves_received.amount                | Cantidad del activo recibido                                                                                                                                                                                                                                                                                                                                                                                              | numérico     |                     |                  |                 |                                |             |       |
-| details.reserves_deposited                      | Cantidad de activo depositada para reservas del depósito del pool de liquidez                                                                                                                                                                                                                                                                                                                                             | registro     |                     |                  |                 |                                |             |       |
-| details.reserves_deposited.asset                | Activo depositado                                                                                                                                                                                                                                                                                                                                                                                                         | cadena       |                     |                  |                 |                                |             |       |
-| details.reserves_deposited.amount               | Cantidad del activo depositada                                                                                                                                                                                                                                                                                                                                                                                            | numérico     |                     |                  |                 |                                |             |       |
-| details.reserves_revoked                        | Cantidad de activo revocada para reservas del retiro del pool de liquidez                                                                                                                                                                                                                                                                                                                                                 | registro     |                     |                  |                 |                                |             |       |
-| details.reserves_revoked.asset                  | Activo revocado                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.reserves_revoked.amount                 | Cantidad de activo revocado                                                                                                                                                                                                                                                                                                                                                                                               | numérico     |                     |                  |                 |                                |             |       |
-| details.reserves_revoked.claimable_balance_id   | Identificador de balance reclamable                                                                                                                                                                                                                                                                                                                                                                                       | cadena       |                     |                  |                 |                                |             |       |
-| details.bought                                  | Activo comprado en la operación                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.bought.asset                            | Activo comprado                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.bought.amount                           | Cantidad del activo comprado                                                                                                                                                                                                                                                                                                                                                                                              | numérico     |                     |                  |                 |                                |             |       |
-| details.sold                                    | Activo vendido en la operación                                                                                                                                                                                                                                                                                                                                                                                            | registro     |                     |                  |                 |                                |             |       |
-| details.sold.asset                              | Activo vendido                                                                                                                                                                                                                                                                                                                                                                                                            | cadena       |                     |                  |                 |                                |             |       |
-| details.sold.amount                             | Cantidad del activo vendido                                                                                                                                                                                                                                                                                                                                                                                               | numérico     |                     |                  |                 |                                |             |       |
-| details.shares_revoked                          | Acciones revocadas del retiro del pool de liquidez                                                                                                                                                                                                                                                                                                                                                                        | numérico     |                     |                  |                 |                                |             |       |
-| details.shares_received                         | Acciones recibidas del depósito del pool de liquidez                                                                                                                                                                                                                                                                                                                                                                      | numérico     |                     |                  |                 |                                |             |       |
-| details.shares_redeemed                         | Acciones redimidas del retiro del pool de liquidez                                                                                                                                                                                                                                                                                                                                                                        | numérico     |                     |                  |                 |                                |             |       |
-| details.liquidity_pool_id                       | Identificador único para un pool de liquidez                                                                                                                                                                                                                                                                                                                                                                              | cadena       |                     |                  |                 |                                |             |       |
-| details.balance_id                              | Identificador único del balance reclamable. El id está compuesto por un código tipo de 8 caracteres + hash SHA-256 del id de la operación del historial que creó el balance. El id del balance puede vincularse con la tabla \`claimable_balances\` para obtener más detalles sobre el balance                                                                                                                            | cadena       |                     |                  |                 |                                |             |       |
-| details.new_seq                                 | Nuevo número de secuencia después de incrementar la secuencia                                                                                                                                                                                                                                                                                                                                                             | entero       |                     |                  |                 |                                |             |       |
-| details.name                                    | La operación gestionar datos permite a una cuenta escribir y almacenar datos directamente en el ledger en un formato de par clave-valor. El nombre es la clave para una entrada de datos.                                                                                                                                                                                                                                 | cadena       |                     |                  |                 |                                |             |       |
-| details.value                                   | Valor de datos del efecto gestionar datos                                                                                                                                                                                                                                                                                                                                                                                 | cadena       |                     |                  |                 |                                |             |       |
-| details.trustor                                 | Dirección de cuenta del otorgante de confianza                                                                                                                                                                                                                                                                                                                                                                            | cadena       |                     |                  |                 |                                |             |       |
-| details.limit                                   | Cantidad máxima de un activo que una cuenta puede tener                                                                                                                                                                                                                                                                                                                                                                   | numérico     |                     |                  |                 |                                |             |       |
-| details.inflation_destination                   | Id de cuenta destino de la inflación                                                                                                                                                                                                                                                                                                                                                                                      | cadena       |                     |                  |                 |                                |             |       |
-| details.authorized_flag                         | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                                                                                                                                                                  | booleano     |                     |                  |                 |                                |             |       |
-| details.auth_immutable_flag                     | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                                                                                                                                                                  | booleano     |                     |                  |                 |                                |             |       |
-| details.authorized_to_maintain_liabilites       | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                                                                                                                                                                  | booleano     |                     |                  |                 |                                |             |       |
-| details.auth_revocable_flag                     | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                                                                                                                                                                  | booleano     |                     |                  |                 |                                |             |       |
-| details.auth_required_flag                      | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                                                                                                                                                                  | booleano     |                     |                  |                 |                                |             |       |
-| details.auth_clawback_enabled_flag              | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                                                                                                                                                                  | booleano     |                     |                  |                 |                                |             |       |
-| details.claimable_balance_clawback_enabled_flag | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                                                                                                                                                                  | booleano     |                     |                  |                 |                                |             |       |
-| details.clawback_enabled_flag                   | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                                                                                                                                                                  | booleano     |                     |                  |                 |                                |             |       |
-| details.high_threshold                          | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.med_threshold                           | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                                          | entero       |                     |                  |                 |                                |             |       |
-| details.low_threshold                           | La suma del peso de todas las firmas que firman una transacción para la operación de umbral bajo. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.home_domain                             | El dominio principal usado para el descubrimiento del archivo stellar.toml                                                                                                                                                                                                                                                                                                                                                | cadena       |                     |                  |                 |                                |             |       |
-| details.asset_issuer                            | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                                                                                                                                               | cadena       |                     |                  |                 |                                |             |       |
-| details.asset                                   | Activo en la red                                                                                                                                                                                                                                                                                                                                                                                                          | cadena       |                     |                  |                 |                                |             |       |
-| details.asset_code                              | La representación en código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                                                                                                                                                     | cadena       |                     |                  |                 |                                |             |       |
-| details.asset_type                              | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                                                                                                                              | cadena       |                     |                  |                 |                                |             |       |
-| details.signer                                  | La dirección de la cuenta que está autorizada para firmar transacciones en nombre de otra cuenta. Este proceso se llama multi-sig                                                                                                                                                                                                                                                                                         | cadena       |                     |                  |                 |                                |             |       |
-| details.sponsor                                 | La dirección de la cuenta del patrocinador que paga las reservas por este firmante                                                                                                                                                                                                                                                                                                                                        | cadena       |                     |                  |                 |                                |             |       |
-| details.new_sponsor                             | La nueva dirección de la cuenta del patrocinador que paga las reservas por este firmante                                                                                                                                                                                                                                                                                                                                  | cadena       |                     |                  |                 |                                |             |       |
-| details.former_sponsor                          | La dirección antigua de la cuenta del patrocinador que paga las reservas por este firmante                                                                                                                                                                                                                                                                                                                                | cadena       |                     |                  |                 |                                |             |       |
-| details.weight                                  | Peso del firmante                                                                                                                                                                                                                                                                                                                                                                                                         | entero       |                     |                  |                 |                                |             |       |
-| details.public_key                              | Clave pública del firmante                                                                                                                                                                                                                                                                                                                                                                                                | cadena       |                     |                  |                 |                                |             |       |
-| details.amount                                  | Cantidad del activo                                                                                                                                                                                                                                                                                                                                                                                                       | numérico     |                     |                  |                 |                                |             |       |
-| details.starting_balance                        | Saldo inicial del activo de la cuenta                                                                                                                                                                                                                                                                                                                                                                                     | numérico     |                     |                  |                 |                                |             |       |
-| details.seller                                  | Cuenta vendedora                                                                                                                                                                                                                                                                                                                                                                                                          | cadena       |                     |                  |                 |                                |             |       |
-| details.seller_muxed                            | Cuenta multiplexada                                                                                                                                                                                                                                                                                                                                                                                                       | cadena       |                     |                  |                 |                                |             |       |
-| details.seller_muxed_id                         | Id multiplexado de la cuenta                                                                                                                                                                                                                                                                                                                                                                                              | entero       |                     |                  |                 |                                |             |       |
-| details.offer_id                                | El id único para la oferta. Este id puede vincularse con la tabla \`offers\`                                                                                                                                                                                                                                                                                                                                              | entero       |                     |                  |                 |                                |             |       |
-| details.sold_amount                             | Cantidad del activo vendido                                                                                                                                                                                                                                                                                                                                                                                               | numérico     |                     |                  |                 |                                |             |       |
-| details.sold_asset_type                         | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                                                                                                                              | cadena       |                     |                  |                 |                                |             |       |
-| details.sold_asset_code                         | La representación en código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                                                                                                                                                     | cadena       |                     |                  |                 |                                |             |       |
-| details.sold_asset_issuer                       | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                                                                                                                                               | cadena       |                     |                  |                 |                                |             |       |
-| details.bought_asset_type                       | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                                                                                                                              | cadena       |                     |                  |                 |                                |             |       |
-| details.bought_asset_code                       | La representación en código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                                                                                                                                                     | cadena       |                     |                  |                 |                                |             |       |
-| details.bought_asset_issuer                     | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                                                                                                                                               | cadena       |                     |                  |                 |                                |             |       |
-| details.bought_amount                           | Cantidad del activo comprado                                                                                                                                                                                                                                                                                                                                                                                              | numérico     |                     |                  |                 |                                |             |       |
-| details.data_name                               | Nombre del dato de la entrada en el ledger                                                                                                                                                                                                                                                                                                                                                                                | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate                               | La condición que debe cumplirse para que el destinatario pueda reclamar el balance. El predicado puede incluir reglas lógicas usando la lógica AND, OR y NOT.                                                                                                                                                                                                                                                             | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.not                           |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.not.abs_before                |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.not.rel_before                |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.not.unconditional             |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.not.and                       |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.not.and.abs_before            |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.not.and.rel_before            |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.not.and.unconditional         |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.not.and.abs_before_epoch      |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.not.or                        |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.not.or.abs_before             |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.not.or.rel_before             |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.not.or.unconditional          |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.not.or.abs_before_epoch       |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.not.not                       |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.not.not.abs_before            |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.not.not.rel_before            |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.not.not.unconditional         |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.not.not.abs_before_epoch      |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.not.abs_before_epoch          |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.type                          |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.and                           |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.and.abs_before                |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.and.rel_before                |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.and.unconditional             |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.and.and                       |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.and.and.abs_before            |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.and.and.rel_before            |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.and.and.unconditional         |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.and.and.abs_before_epoch      |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.and.or                        |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.and.or.abs_before             |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.and.or.rel_before             |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.and.or.unconditional          |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.and.or.abs_before_epoch       |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.and.not                       |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.and.not.abs_before            |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.and.not.rel_before            |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.and.not.unconditional         |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.and.not.abs_before_epoch      |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.and.abs_before_epoch          |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.or                            |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.or.abs_before                 |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.or.rel_before                 |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.or.unconditional              |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.or.and                        |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.abs_before             |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.rel_before             |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.unconditional          |                                                                                                                                                                                                                                                                                                                                                                                                                           | booleano     |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.not                    |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.not.abs_before         |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.not.rel_before         |                                                                                                                                                                                                                                                                                                                                                                                                                           | entero       |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.not.unconditional      |                                                                                                                                                                                                                                                                                                                                                                                                                           | boolean      |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.not.abs_before_epoch   |                                                                                                                                                                                                                                                                                                                                                                                                                           | integer      |                     |                  |                 |                                |             |       |
-| details.predicate.or.and.abs_before_epoch       |                                                                                                                                                                                                                                                                                                                                                                                                                           | integer      |                     |                  |                 |                                |             |       |
-| details.predicate.or.or                         |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.or.or.abs_before              |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.or.or.rel_before              |                                                                                                                                                                                                                                                                                                                                                                                                                           | integer      |                     |                  |                 |                                |             |       |
-| details.predicate.or.or.unconditional           |                                                                                                                                                                                                                                                                                                                                                                                                                           | boolean      |                     |                  |                 |                                |             |       |
-| details.predicate.or.or.abs_before_epoch        |                                                                                                                                                                                                                                                                                                                                                                                                                           | integer      |                     |                  |                 |                                |             |       |
-| details.predicate.or.not                        |                                                                                                                                                                                                                                                                                                                                                                                                                           | registro     |                     |                  |                 |                                |             |       |
-| details.predicate.or.not.abs_before             |                                                                                                                                                                                                                                                                                                                                                                                                                           | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.or.not.rel_before             |                                                                                                                                                                                                                                                                                                                                                                                                                           | integer      |                     |                  |                 |                                |             |       |
-| details.predicate.or.not.unconditional          |                                                                                                                                                                                                                                                                                                                                                                                                                           | boolean      |                     |                  |                 |                                |             |       |
-| details.predicate.or.not.abs_before_epoch       |                                                                                                                                                                                                                                                                                                                                                                                                                           | integer      |                     |                  |                 |                                |             |       |
-| details.predicate.or.abs_before_epoch           |                                                                                                                                                                                                                                                                                                                                                                                                                           | integer      |                     |                  |                 |                                |             |       |
-| details.predicate.abs_before                    | Fecha límite para reclamar el balance. Si se reclama un balance antes de esta fecha, la condición queda satisfecha.                                                                                                                                                                                                                                                                                                       | cadena       |                     |                  |                 |                                |             |       |
-| details.predicate.rel_before                    | Una fecha límite relativa para cuando se puede reclamar el balance reclamable. El valor representa el número de segundos desde el cierre del ledger que creó el balance reclamable \#### Notas: Esta condición es útil al crear límites de tiempo basados en condiciones de creación. Si el creador quería que un balance solo pudiera reclamarse una semana después de la creación, esta condición satisfaría esa regla. | integer      |                     |                  |                 |                                |             |       |
-| details.predicate.unconditional                 | Si es verdadero, significa que esta cláusula de la condición siempre se cumple. \#### Notas: Cuando el predicado es solo unconditional = true, significa que el balance puede reclamarse bajo cualquier condición                                                                                                                                                                                                         | boolean      |                     |                  |                 |                                |             |       |
-| details.predicate.abs_before_epoch              | Un valor de época UNIX en segundos que representa la misma fecha límite que abs_before.                                                                                                                                                                                                                                                                                                                                   | integer      |                     |                  |                 |                                |             |       |
-| batch_id                                        | Representación en cadena del ID de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los IDs de lote son únicos para el lote y ayudan en la monitorización y capacidades de reejecución                                                                                                                                                                                  | cadena       |                     |                  |                 |                                |             |       |
-| batch_run_date                                  | Fecha de inicio para el intervalo del lote. Tomada junto con la fecha en batch_id, representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de closed_at para un ledger.                                                                                                                                                                                                   | datetime     |                     |                  |                 | Partición MES                  |             |       |
-| batch_insert_ts                                 | Marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un backfill                                                                                                                                                                                                                              | timestamp    |                     |                  |                 |                                |             |       |
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad               | Configuración                                                                                                  |
-| ----------------------- | -------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)    | id                                                                                                             |
-| Partición(es) del campo | batch_run_date (partición MES)                                                                                 |
-| Campo(s) agrupado(s)    | address, operation_id, type                                                                                    |
-| Documentación           | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_effects) |
-
-## Detalles de la columna
-
-| Nombre                                          | Descripción                                                                                                                                                                                                                                                                                         | Tipo de dato | Valores del dominio | ¿Requerido? | Notas |
-| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------- | ----------- | ----- |
-| id                                              | Este ID único de efecto es la concatenación del ID de operación y el índice del efecto                                                                                                                                                                                                              | cadena       |                     | Sí          |       |
-| index                                           | El índice del efecto dentro de la transacción. Este índice ayuda a ordenar los efectos que resultan de la misma transacción, indicando la secuencia en que ocurrieron.                                                                                                                              | integer      |                     | Sí          |       |
-| closed_at                                       | Marca de tiempo en UTC cuando este ledger se cerró y confirmó en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                                                                       | timestamp    |                     | Sí          |       |
-| ledger_sequence                                 | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.                                         | integer      |                     | Sí          |       |
-| address                                         | La dirección de la cuenta. La dirección es la clave pública de la cuenta codificada en base32. Todas las direcciones de cuenta comienzan con una `G`                                                                                                                                                | cadena       |                     |             |       |
-| address_muxed                                   | Dirección multiplexada                                                                                                                                                                                                                                                                              | cadena       |                     |             |       |
-| operation_id                                    | Identificador único para una operación                                                                                                                                                                                                                                                              | integer      |                     |             |       |
-| tipo                                            | El número que indica qué tipo de efecto                                                                                                                                                                                                                                                             | integer      |                     |             |       |
-| type_string                                     | La cadena que indica qué tipo de efecto                                                                                                                                                                                                                                                             | cadena       |                     |             |       |
-| details                                         | Objeto JSON no estructurado que contiene detalles basados en el tipo de efecto. Cada efecto devolverá sus propios detalles relevantes, con el resto de los detalles como nulos                                                                                                                      | registro     |                     |             |       |
-| details.liquidity_pool                          | Los liquidity pools proporcionan una manera simple y no interactiva de intercambiar grandes cantidades de capital y permiten altos volúmenes de trading                                                                                                                                             | registro     |                     |             |       |
-| details.liquidity_pool.fee_bp                   | El número de puntos básicos cobrados como un porcentaje del trade para completar la transacción. Las tarifas ganadas en todos los trades se dividen entre los accionistas del pool y se distribuyen como un incentivo para mantener dinero en los pools                                             | integer      |                     |             |       |
-| details.liquidity_pool.id                       | Identificador único para un liquidity pool. No puede haber pools duplicados para el mismo par de activos. Una vez que se ha creado un pool para un par de activos, no se puede crear otro.                                                                                                          | cadena       |                     |             |       |
-| details.liquidity_pool.total_shares             | Número total de acciones emitidas del pool                                                                                                                                                                                                                                                          | numérico     |                     |             |       |
-| details.liquidity_pool.total_trustlines         | Número de trustlines para las acciones asociadas al pool                                                                                                                                                                                                                                            | integer      |                     |             |       |
-| details.liquidity_pool.type                     | El mecanismo que calcula el precio y la división de acciones para el pool. Con el lanzamiento inicial de AMM, el único tipo de liquidity pool permitido para crear es un pool de producto constante.                                                                                                | cadena       |                     |             |       |
-| details.liquidity_pool.reserves                 | Activo reservado en el liquidity pool                                                                                                                                                                                                                                                               | registro     |                     |             |       |
-| details.liquidity_pool.reserves.asset           | Activo de reserva                                                                                                                                                                                                                                                                                   | cadena       |                     |             |       |
-| details.liquidity_pool.reserves.amount          | Cantidad del activo reservado                                                                                                                                                                                                                                                                       | numérico     |                     |             |       |
-| details.reserves_received                       | Cantidad de activo recibida por reservas al retirar del liquidity pool                                                                                                                                                                                                                              | registro     |                     |             |       |
-| details.reserves_received.asset                 | Activo recibido                                                                                                                                                                                                                                                                                     | cadena       |                     |             |       |
-| details.reserves_received.amount                | Cantidad del activo recibido                                                                                                                                                                                                                                                                        | numérico     |                     |             |       |
-| details.reserves_deposited                      | Cantidad de activo depositada para reservas en depositar en el liquidity pool                                                                                                                                                                                                                       | registro     |                     |             |       |
-| details.reserves_deposited.asset                | Activo depositado                                                                                                                                                                                                                                                                                   | cadena       |                     |             |       |
-| details.reserves_deposited.amount               | Cantidad del activo depositada                                                                                                                                                                                                                                                                      | numérico     |                     |             |       |
-| details.reserves_revoked                        | Cantidad de activo revocada para reservas al revocar en el liquidity pool                                                                                                                                                                                                                           | registro     |                     |             |       |
-| details.reserves_revoked.asset                  | Activo revocado                                                                                                                                                                                                                                                                                     | cadena       |                     |             |       |
-| details.reserves_revoked.amount                 | Cantidad del activo revocada                                                                                                                                                                                                                                                                        | numérico     |                     |             |       |
-| details.reserves_revoked.claimable_balance_id   | ID del balance reclamable                                                                                                                                                                                                                                                                           | cadena       |                     |             |       |
-| details.bought                                  | Activo comprado en el trade                                                                                                                                                                                                                                                                         | registro     |                     |             |       |
-| details.bought.asset                            | Activo comprado                                                                                                                                                                                                                                                                                     | cadena       |                     |             |       |
-| details.bought.amount                           | Cantidad del activo comprado                                                                                                                                                                                                                                                                        | numérico     |                     |             |       |
-| details.sold                                    | Activo vendido en el trade                                                                                                                                                                                                                                                                          | registro     |                     |             |       |
-| details.sold.asset                              | Activo vendido                                                                                                                                                                                                                                                                                      | cadena       |                     |             |       |
-| details.sold.amount                             | Cantidad del activo vendido                                                                                                                                                                                                                                                                         | numérico     |                     |             |       |
-| details.shares_revoked                          | Shares revocadas al revocar en el liquidity pool                                                                                                                                                                                                                                                    | numérico     |                     |             |       |
-| details.shares_received                         | Shares recibidas al depositar en el liquidity pool                                                                                                                                                                                                                                                  | numérico     |                     |             |       |
-| details.shares_redeemed                         | Shares redimidas al retirar del liquidity pool                                                                                                                                                                                                                                                      | numérico     |                     |             |       |
-| details.liquidity_pool_id                       | Identificador único para un liquidity pool                                                                                                                                                                                                                                                          | cadena       |                     |             |       |
-| details.balance_id                              | Identificador único del balance reclamable. El ID está compuesto por un código de tipo de 8 caracteres + hash SHA-256 del ID de operación de historial que creó el balance. El ID del balance puede asociarse de nuevo con la tabla `claimable_balances` para obtener más detalles sobre el balance | cadena       |                     |             |       |
-| details.new_seq                                 | Nuevo número de secuencia después de bump sequence                                                                                                                                                                                                                                                  | integer      |                     |             |       |
-| details.name                                    | La operación manage data permite a una cuenta escribir y almacenar datos directamente en el ledger en formato de par clave-valor. El nombre es la clave para una entrada de datos.                                                                                                                  | cadena       |                     |             |       |
-| details.value                                   | Valor de datos del efecto manage data                                                                                                                                                                                                                                                               | cadena       |                     |             |       |
-| details.trustor                                 | Dirección de cuenta del trustor                                                                                                                                                                                                                                                                     | cadena       |                     |             |       |
-| details.limit                                   | Cantidad máxima de un activo que una cuenta puede tener                                                                                                                                                                                                                                             | numérico     |                     |             |       |
-| details.inflation_destination                   | ID de cuenta destino de la inflación                                                                                                                                                                                                                                                                | cadena       |                     |             |       |
-| details.authorized_flag                         | Valor de autorización para set trustline flags                                                                                                                                                                                                                                                      | boolean      |                     |             |       |
-| details.auth_immutable_flag                     | Valor de autorización para set trustline flags                                                                                                                                                                                                                                                      | boolean      |                     |             |       |
-| details.authorized_to_maintain_liabilities      | Valor de autorización para set trustline flags                                                                                                                                                                                                                                                      | boolean      |                     |             |       |
-| details.auth_revocable_flag                     | Valor de autorización para set trustline flags                                                                                                                                                                                                                                                      | boolean      |                     |             |       |
-| details.auth_required_flag                      | Valor de autorización para set trustline flags                                                                                                                                                                                                                                                      | boolean      |                     |             |       |
-| details.auth_clawback_enabled_flag              | Valor de autorización para set trustline flags                                                                                                                                                                                                                                                      | boolean      |                     |             |       |
-| details.claimable_balance_clawback_enabled_flag | Valor de autorización para set trustline flags                                                                                                                                                                                                                                                      | boolean      |                     |             |       |
-| details.clawback_enabled_flag                   | Valor de autorización para set trustline flags                                                                                                                                                                                                                                                      | boolean      |                     |             |       |
-| details.high_threshold                          | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                     | integer      |                     |             |       |
-| details.med_threshold                           | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                    | integer      |                     |             |       |
-| details.low_threshold                           | La suma del peso de todas las firmas que firman una transacción para la operación de umbral bajo. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                     | integer      |                     |             |       |
-| details.home_domain                             | El dominio principal usado para el descubrimiento del archivo stellar.toml                                                                                                                                                                                                                          | cadena       |                     |             |       |
-| details.asset_issuer                            | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                         | cadena       |                     |             |       |
-| details.asset                                   | Activo en la red                                                                                                                                                                                                                                                                                    | cadena       |                     |             |       |
-| details.asset_code                              | La representación del código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                              | cadena       |                     |             |       |
-| details.asset_type                              | El identificador para el tipo de código de activo, puede ser alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                         | cadena       |                     |             |       |
-| details.signer                                  | La dirección de la cuenta que está autorizada para firmar transacciones para otra cuenta. Este proceso se llama multi-sig                                                                                                                                                                           | cadena       |                     |             |       |
-| details.sponsor                                 | La dirección de la cuenta del patrocinador que paga las reservas para este firmante                                                                                                                                                                                                                 | cadena       |                     |             |       |
-| details.new_sponsor                             | La nueva dirección de la cuenta del patrocinador que paga las reservas para este firmante                                                                                                                                                                                                           | cadena       |                     |             |       |
-| details.former_sponsor                          | La antigua dirección de la cuenta del patrocinador que pagaba las reservas para este firmante                                                                                                                                                                                                       | cadena       |                     |             |       |
-| details.weight                                  | Peso del firmante                                                                                                                                                                                                                                                                                   | integer      |                     |             |       |
-| details.public_key                              | Clave pública del firmante                                                                                                                                                                                                                                                                          | cadena       |                     |             |       |
-| details.amount                                  | Cantidad del activo                                                                                                                                                                                                                                                                                 | numérico     |                     |             |       |
-| details.starting_balance                        | Balance inicial del activo de la cuenta                                                                                                                                                                                                                                                             | numérico     |                     |             |       |
-| details.seller                                  | Cuenta vendedora                                                                                                                                                                                                                                                                                    | cadena       |                     |             |       |
-| details.seller_muxed                            | Cuenta multiplexada                                                                                                                                                                                                                                                                                 | cadena       |                     |             |       |
-| details.seller_muxed_id                         | ID de cuenta multiplexada                                                                                                                                                                                                                                                                           | integer      |                     |             |       |
-| details.offer_id                                | ID único para la oferta. Este ID puede asociarse con la tabla `offers`                                                                                                                                                                                                                              | integer      |                     |             |       |
-| details.sold_amount                             | Cantidad de activo vendido                                                                                                                                                                                                                                                                          | numérico     |                     |             |       |
-| details.sold_asset_type                         | El identificador para el tipo de código de activo, puede ser alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                         | cadena       |                     |             |       |
-| details.sold_asset_code                         | La representación del código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                              | cadena       |                     |             |       |
-| details.sold_asset_issuer                       | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                         | cadena       |                     |             |       |
-| details.bought_asset_type                       | El identificador para el tipo de código de activo, puede ser alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                         | cadena       |                     |             |       |
-| details.bought_asset_code                       | La representación del código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                              | cadena       |                     |             |       |
-| details.bought_asset_issuer                     | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                         | cadena       |                     |             |       |
-| details.bought_amount                           | Cantidad de activo comprado                                                                                                                                                                                                                                                                         | numérico     |                     |             |       |
-| details.data_name                               | Nombre de dato de la entrada del ledger                                                                                                                                                                                                                                                             | cadena       |                     |             |       |
-| details.predicate                               | La condición que debe cumplirse para que el destino pueda reclamar el balance. El predicado puede incluir reglas lógicas usando la lógica AND, OR y NOT.                                                                                                                                            | registro     |                     |             |       |
-| batch_id                                        | Representación en cadena del ID de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los IDs de lote son únicos para el lote y ayudan en la monitorización y capacidades de reejecución                                                            | cadena       |                     |             |       |
-| batch_run_date                                  | Fecha de inicio para el intervalo del lote. Tomada junto con la fecha en batch_id, representa el intervalo de ledgers procesados.                                                                                                                                                                   | datetime     |                     |             |       |
-| batch_insert_ts                                 | Marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos.                                                                                                                                                                                                               | timestamp    |                     |             |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.mdx
deleted file mode 100644
index cd4166a08b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-ledgers.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: History Ledgers
-sidebar_position: 110
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                  |
-| --------------------- | -------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | secuencia                                                                                                      |
-| Campo(s) de partición | closed_at (partición de MES)                                                                                   |
-| Campo(s) agrupado(s)  | secuencia, closed_at                                                                                           |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_ledgers) |
-
-## Detalles de columnas
-
-| Nombre                         | Descripción                                                                                                                                                                                                                                                                            | Tipo de dato    | Valores de dominio                            | ¿Requerido? | Notas                                                                                                                                                                                |   |
-| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | --------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | - |
-| secuencia                      | El número de secuencia que corresponde a los ledger individuales. A medida que se escriben los ledgers en la red, la secuencia se incrementa en 1                                                                                                                                      | entero          |                                               | Sí          |                                                                                                                                                                                      |   |
-| ledger_hash                    | El hash SHA-256 codificado en hexadecimal que representa la forma XDR codificada del ledger                                                                                                                                                                                            | cadena          |                                               | Sí          |                                                                                                                                                                                      |   |
-| previous_ledger_hash           | El hash SHA-256 codificado en hexadecimal del ledger que precede inmediatamente a este ledger                                                                                                                                                                                          | cadena          |                                               | No          |                                                                                                                                                                                      |   |
-| transaction_count              | El número de transacciones exitosas enviadas y completadas por la red en este ledger                                                                                                                                                                                                   | entero          |                                               | Sí          | Por defecto es 0                                                                                                                                                                     |   |
-| operation_count                | El número total de operaciones exitosas aplicadas a este ledger                                                                                                                                                                                                                        | entero          |                                               | Sí          | Por defecto es 0                                                                                                                                                                     |   |
-| closed_at                      | Marca de tiempo en UTC cuando este ledger se cerró y se confirmó en la red. Se espera que los ledgers se cierren ~cada 5 segundos                                                                                                                                                      | marca de tiempo |                                               | Sí          |                                                                                                                                                                                      |   |
-| id                             | Identificador único para el ledger                                                                                                                                                                                                                                                     | entero          |                                               | Sí          |                                                                                                                                                                                      |   |
-| total_coins                    | Número total de lumens en circulación                                                                                                                                                                                                                                                  | entero          |                                               | Sí          |                                                                                                                                                                                      |   |
-| fee_pool                       | La suma de todas las tarifas de transacción                                                                                                                                                                                                                                            | entero          |                                               | Sí          |                                                                                                                                                                                      |   |
-| base_fee                       | La tarifa (en stroops) que la red cobra por operación en una transacción para el ledger dado. La tarifa base mínima es 100, con la posibilidad de aumentar si la demanda de transacciones excede la capacidad del ledger. Cuando esto ocurre, el ledger entra en precios de sobrecarga | entero          |                                               | Sí          | El stroop es la representación fraccional de un lumen (XLM). 1 stroop es 0.0000001 XLM.                                                                                              |   |
-| base_reserve                   | La reserva (en stroops) que la red requiere que una cuenta mantenga como saldo mínimo para ser una cuenta válida en la red. La reserva mínima actual es 10 XLM                                                                                                                         | entero          | 5000000 100000000                             | Sí          | El stroop es la representación fraccional de un lumen (XLM). 1 stroop es 0.0000001 XLM.                                                                                              |   |
-| max_tx_set_size                | El número máximo de operaciones que los nodos validadores Stellar han acordado procesar en un ledger dado. Desde el Protocolo 11, la capacidad del ledger se mide en operaciones en lugar de transacciones                                                                             | entero          | 50 - máximo original 500 1000 - máximo actual | Sí          |                                                                                                                                                                                      |   |
-| protocol_version               | La versión del protocolo que la red Stellar estaba ejecutando cuando se confirmó este ledger. Las versiones del protocolo se lanzan aproximadamente cada 6 meses                                                                                                                       | entero          | enteros 1 - 19 (incrementará)                 | Sí          | Por defecto es 0                                                                                                                                                                     |   |
-| ledger_header                  | Una cadena codificada en base64 de la estructura LedgerHeader xdr sin procesar para este ledger                                                                                                                                                                                        | bytes           |                                               | No          |                                                                                                                                                                                      |   |
-| successful_transaction_count   | El número de transacciones exitosas enviadas y completadas por la red en este ledger                                                                                                                                                                                                   | entero          |                                               | No          |                                                                                                                                                                                      |   |
-| failed_transaction_count       | El número de transacciones fallidas enviadas a la red en este ledger. La transacción aún fue pagada pero contenía un error que impidió su ejecución                                                                                                                                    | entero          |                                               | No          |                                                                                                                                                                                      |   |
-| tx_set_operation_count         | El número total de operaciones en el conjunto de transacciones para este ledger, incluyendo transacciones fallidas.                                                                                                                                                                    | entero          |                                               | No          | Las transacciones en Stellar son atómicas. Si una de las operaciones dentro de un conjunto de transacciones falla, toda la transacción fallará, incluyendo cualquier otra operación. |   |
-| batch_id                       | Representación en cadena del run id para un DAG dado en Airflow. Tiene la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los batch ids son únicos para el lote y ayudan con el monitoreo y las capacidades de reejecución                                                         | cadena          |                                               | Sí          |                                                                                                                                                                                      |   |
-| batch_run_date                 | La fecha de inicio para el intervalo del lote. Cuando se toma junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de closed_at para un ledger.                                         | fecha y hora    |                                               | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta.                |   |
-| batch_insert_ts                | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un relleno histórico                                                                               | marca de tiempo |                                               | Sí          |                                                                                                                                                                                      |   |
-| soroban_fee_write_1kb          | Costos de tarifas de escritura Soroban                                                                                                                                                                                                                                                 | entero          |                                               | No          |                                                                                                                                                                                      |   |
-| firma                          | El hash de firma del nodo validador que escribe el conjunto de transacciones en la red. Esta firma asegura la integridad y autenticidad del ledger, confirmando que no ha sido alterado                                                                                                | cadena          |                                               | Sí          |                                                                                                                                                                                      |   |
-| node_id                        | El id del nodo validador ganador que tiene permitido escribir el conjunto de transacciones en la red. El validador ganador es decidido por la red                                                                                                                                      | cadena          |                                               | Sí          |                                                                                                                                                                                      |   |
-| total_byte_size_of_bucket_list | El tamaño, en bytes, de la base de datos Bucketlist para la Red Stellar                                                                                                                                                                                                                | entero          |                                               | Sí          |                                                                                                                                                                                      |   |
-| tipo_de_claves_evicted_ledger  | La lista de tipos de claves que han sido desalojadas en una entrada específica del ledger.                                                                                                                                                                                             | cadena          |                                               | No          |                                                                                                                                                                                      |   |
-| hash_de_claves_evicted_ledger  | La lista de hashes de claves que han sido desalojadas en una entrada específica del ledger.                                                                                                                                                                                            | cadena          |                                               |             | No                                                                                                                                                                                   |   |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.mdx
deleted file mode 100644
index 3cdeb063db..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-operations.mdx
+++ /dev/null
@@ -1,154 +0,0 @@
----
-title: Operaciones de Historial
-sidebar_position: 120
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                     |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | id                                                                                                                |
-| Campo(s) de Partición | batch_run_date (partición de MES)                                                                                 |
-| Campo(s) Agrupado(s)  | transaction_id, source_account, type                                                                              |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_operations) |
-
-## Detalles de Columnas
-
-| Nombre                                     | Descripción                                                                                                                                                                                                                                                                                             | Tipo de Datos   | Valores de Dominio                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | ¿Requerido? | Notas                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| id                                         | Identificador único para una operación                                                                                                                                                                                                                                                                  | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          | El id de la operación es la combinación del id de la transacción + número de orden                                                                                                                                                                                                                                                                                                                                     |
-| source_account                             | La dirección de la cuenta que origina la operación                                                                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          | Por defecto es ''                                                                                                                                                                                                                                                                                                                                                                                                      |
-| source_account_muxed                       | Si una cuenta está multiplexada (muxed), la dirección virtual de la cuenta que origina la operación                                                                                                                                                                                                     | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| transaction_id                             | El identificador de la transacción en la que se ejecutó la operación. Puede haber hasta 100 operaciones en una transacción dada                                                                                                                                                                         | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| ledger_sequence                            | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.                                                | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| type                                       | El número que indica qué tipo de operación ejecuta esta operación                                                                                                                                                                                                                                       | entero          | <ul><li>0 - Crear Cuenta</li><li>1 - Pago</li><li>2 - Pago por Ruta Restrictivo Recibir</li><li>3 - Gestionar Oferta de Venta</li><li>4 - Crear Oferta de Venta Pasiva</li><li>5 - Establecer Opciones</li><li>6 - Cambiar Confianza</li><li>7 - Permitir Confianza</li><li>8 - Fusión de Cuenta</li><li>9 - Inflación</li><li>10 - Gestionar Datos</li><li>11 - Avanzar Secuencia</li><li>12 - Gestionar Oferta de Compra</li><li>13 - Pago por Ruta Restrictivo Enviar</li><li>14 - Crear Saldo Reclamable</li><li>15 - Reclamar Saldo Reclamable</li><li>16 - Comenzar a Patrocinar Reservas Futuras</li><li>17 - Finalizar Patrocinio de Reservas Futuras</li><li>18 - Revocar Patrocinio</li><li>19 - Clawback</li><li>20 - Clawback de Saldo Reclamable</li><li>21 - Establecer flags de Trust Line</li><li>22 - Depósito en Pool de Liquidez</li><li>23 - Retiro de Pool de Liquidez</li></ul> | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| type_string                                | La cadena que indica qué tipo de operación ejecuta esta operación                                                                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details                                    | Objeto JSON no estructurado que contiene detalles basados en el tipo de operación ejecutada                                                                                                                                                                                                             | blob            | ver detalles abajo (E10:E108)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | No          | Bigquery no tiene un tipo de campo JSON (actualmente solo en piloto pre-GA) así que este campo es un registro estructurado y disperso en su lugar. En los datos de origen, este campo es un verdadero blob JSON                                                                                                                                                                                                        |
-| details.account                            | La nueva dirección de la cuenta resultante que se crea y financia (operación de creación) La dirección de la cuenta que se elimina y fusiona con otra cuenta (operación de fusión)                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.account_muxed                      | La dirección virtual de la cuenta si la cuenta está multiplexada                                                                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.account_muxed_id                   | Representación entera de la dirección virtual de la cuenta si la cuenta está multiplexada                                                                                                                                                                                                               | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.account_id                         | La dirección de la cuenta que ya no está patrocinada                                                                                                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.amount                             | Representación flotante de la cantidad de un activo enviado/ofertado/etc                                                                                                                                                                                                                                | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset                              | El activo disponible para reclamar en la forma "asset_code:issuing_address". Si el saldo reclamable está en XLM, se reporta como "native"                                                                                                                                                               | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_code                         | La representación en código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                                   | cadena          | <ul><li>1 - Pago</li><li>2 - Pago por Ruta Restrictivo Recibir</li><li>6 - Cambiar Confianza</li><li>7 - Permitir Confianza</li><li>13 - Pago por Ruta Restrictivo Enviar</li><li>19 - Clawback</li><li>21 - Establecer flags de Trust Line</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | No          | Los códigos de activo no garantizan unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto                                                                                                                                                                                                                                                                                          |
-| details.asset_issuer                       | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                             | cadena          | <ul><li>1 - Pago</li><li>2 - Pago por Ruta Restrictivo Recibir</li><li>6 - Cambiar Confianza</li><li>7 - Permitir Confianza</li><li>13 - Pago por Ruta Restrictivo Enviar</li><li>19 - Clawback</li><li>21 - Establecer flags de Trust Line</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_type                         | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                            | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | No          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y en su lugar se mostrará con tipo de activo 'native'                                                                                                                                                                                                                                                                     |
-| details.authorize                          | Indica si la línea de confianza está autorizada. 0 si la cuenta no está autorizada para transaccionar con el activo de ninguna forma. 1 si la cuenta está autorizada para transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones. | booleano        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.balance_id                         | El identificador único del saldo reclamable. El id se compone de código de tipo de 8 caracteres + el hash SHA-256 del id de la operación de historial que creó el saldo.                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.buying_asset_code                  | La representación en código de 4 o 12 caracteres del activo que se compra o se ofrece comprar en una operación                                                                                                                                                                                          | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.buying_asset_issuer                | La dirección de la cuenta del emisor original del activo que se compró u ofreció comprar                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.buying_asset_type                  | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                            | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | No          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y en su lugar se mostrará con tipo de activo 'native'                                                                                                                                                                                                                                                                     |
-| details.claimable_balance_id               | El id del saldo reclamable que ya no está patrocinado                                                                                                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.claimant                           | La dirección de la cuenta que reclamó el saldo reclamable                                                                                                                                                                                                                                               | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.claimant_muxed                     | Si la cuenta está multiplexada, la dirección virtual de la cuenta que reclamó el saldo reclamable                                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.claimant_muxed_id                  | Si la cuenta está multiplexada, la representación entera de la cuenta multiplexada que reclamó el saldo                                                                                                                                                                                                 | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.claimants                          | Campo no estructurado que lista direcciones de cuentas elegibles para reclamar un saldo y las condiciones que se deben cumplir para reclamar el saldo (normalmente condiciones limitadas por tiempo)                                                                                                    | array[record]   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.data_account_id                    | La dirección de la cuenta cuya entrada de datos ya no está patrocinada                                                                                                                                                                                                                                  | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.data_name                          | El nombre de la entrada de datos que ya no está patrocinada                                                                                                                                                                                                                                             | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.from                               | La dirección de la cuenta desde la que se origina el pago (cuenta emisora)                                                                                                                                                                                                                              | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.from_muxed                         | Si la cuenta está multiplexada, la dirección virtual de la cuenta emisora                                                                                                                                                                                                                               | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.from_muxed_id                      | Si la cuenta está multiplexada, la representación entera de la dirección virtual de la cuenta emisora                                                                                                                                                                                                   | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.funder                             | Cuando se crea una nueva cuenta, una dirección de cuenta "funde" la nueva cuenta                                                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.funder_muxed                       | Si la cuenta está multiplexada, la dirección virtual de la cuenta que financia la nueva cuenta                                                                                                                                                                                                          | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.funder_muxed_id                    | Si la cuenta está multiplexada, la representación entera de la dirección virtual de la cuenta financiadora                                                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.high_threshold                     | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto                                                                                                                                                                                                        | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Cada operación se clasifica en una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que una operación necesita para tener éxito. Seguridad Baja: Permitir Confianza, Establecer flags de Trust Line, Avanzar Secuencia y Reclamar Saldo Reclamable; Seguridad Media: Todo lo Demás; Seguridad Alta: Fusión de Cuenta, Establecer Opciones                               |
-| details.home_domain                        | El dominio principal utilizado para el descubrimiento del archivo stellar.toml                                                                                                                                                                                                                          | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.inflation_dest                     | La dirección de la cuenta que especifica dónde enviar los fondos de inflación. El concepto de inflación en la red ha sido descontinuado                                                                                                                                                                 | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | La inflación fue retirada de la red en 2019.                                                                                                                                                                                                                                                                                                                                                                           |
-| details.into                               | La dirección de la cuenta que recibe los lumenes de la cuenta eliminada. Esta es la cuenta en la que la cuenta eliminada se fusionará                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.into_muxed                         | Si la cuenta está multiplexada, la dirección virtual de la cuenta que recibe los lumenes de la cuenta eliminada                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.into_muxed_id                      | Si la cuenta está multiplexada, la representación entera de la cuenta que recibe los lumenes de la cuenta eliminada                                                                                                                                                                                     | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.limit                              | La cantidad máxima de un activo que una cuenta puede poseer                                                                                                                                                                                                                                             | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.low_threshold                      | La suma del peso de todas las firmas que firman una transacción para la operación de umbral bajo                                                                                                                                                                                                        | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Cada operación se clasifica en una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que una operación necesita para tener éxito. Seguridad Baja: Permitir Confianza, Establecer flags de Trust Line, Avanzar Secuencia y Reclamar Saldo Reclamable; Seguridad Media: Todo lo Demás; Seguridad Alta: Fusión de Cuenta, Establecer Opciones                               |
-| details.master_key_weight                  | La clave privada de una cuenta se llama clave maestra. Para firmar transacciones, el titular de la cuenta puede especificar un peso para la clave maestra, que contribuye a la validación de umbrales al procesar una transacción                                                                       | entero          | Enteros de 1 a 255                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | No          | Por defecto es 1                                                                                                                                                                                                                                                                                                                                                                                                       |
-| details.med_threshold                      | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio                                                                                                                                                                                                       | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Cada operación se clasifica en una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que una operación necesita para tener éxito. Seguridad Baja: Permitir Confianza, Establecer flags de Trust Line, Avanzar Secuencia y Reclamar Saldo Reclamable; Seguridad Media: Todo lo Demás; Seguridad Alta: Fusión de Cuenta, Establecer Opciones                               |
-| details.name                               | La operación gestionar datos permite a una cuenta escribir y almacenar datos directamente en el ledger en formato de par clave-valor. El nombre es la clave para una entrada de datos                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Si el nombre es nuevo, la operación gestionar datos añadirá el par nombre/valor dado a la cuenta. Si el nombre ya está presente, se modificará el valor asociado.                                                                                                                                                                                                                                                      |
-| details.offer_id                           | El id único para la oferta. Este id se puede unir con la tabla `offers`                                                                                                                                                                                                                                 | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.path                               | Los pagos por ruta maximizan el mejor camino de tasa de cambio al enviar dinero de un activo a otro. Los activos intermediarios por los que pasa esta ruta se reportarán en el registro. Esta característica es especialmente útil cuando el mercado entre el par de activos original es ilíquido       | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Se permiten hasta 6 rutas para un solo pago. Ejemplo: enviar EUR -> MXN podría verse como EUR -> BTC -> CNY -> XLM -> MXN para maximizar la mejor tasa de cambio. Los pagos son atómicos, por lo que si un intercambio en medio de un pago por ruta falla, todo el pago fallará, lo que significa que el usuario mantendrá sus fondos originales. No se quedará con un activo intermediario en caso de falla del pago. |
-| details.price                              | La proporción de activo en venta a activo en compra. Este es un número que representa cuántas unidades de un activo en venta se necesitan para obtener 1 unidad del activo en compra                                                                                                                    | array[flotante] |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.price_r                            | Representación precisa del precio de compra y venta de los activos en una oferta. El n es el numerador, el d es el denominador. Calculando la proporción n/d puedes calcular el precio de la oferta de compra o venta                                                                                   | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.selling_asset_code                 | La representación en código de 4 o 12 caracteres del activo que se vende u ofrece vender en una operación                                                                                                                                                                                               | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.selling_asset_issuer               | La dirección de la cuenta del emisor original del activo que se vendió u ofreció vender                                                                                                                                                                                                                 | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.selling_asset_type                 | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                            | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | No          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y en su lugar se mostrará con tipo de activo 'native'                                                                                                                                                                                                                                                                     |
-| details.set_flags                          | Array de valores numéricos de las flags establecidas para una trustline dada en la operación                                                                                                                                                                                                            | array[entero]   | <ul><li>1 - Auth Required</li><li>2 - Auth Revocable</li><li>4 - Auth Immutable</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.set_flags_s                        | Array de valores en cadena de las flags establecidas para una trustline dada en la operación                                                                                                                                                                                                            | array[cadena]   | <ul><li>Auth Required</li><li>Auth Revocable</li><li>Auth Immutable</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.signer_account_id                  | La dirección de la cuenta del firmante que ya no está patrocinado                                                                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.signer_key                         | La dirección del firmante que ya no está patrocinado                                                                                                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.signer_weight                      | El peso del nuevo firmante. Para transacciones, múltiples cuentas pueden firmar una transacción desde una cuenta fuente. Este peso contribuye a calcular si la transacción supera el peso umbral especificado para completar la transacción                                                             | entero          | Enteros de 1 a 255                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.source_amount                      | La cantidad de origen enviada designada en el activo de origen                                                                                                                                                                                                                                          | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.source_asset_code                  | La representación en código de 4 o 12 caracteres del activo que es enviado originalmente                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.source_asset_issuer                | La dirección de la cuenta del emisor original del activo que fue enviado                                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.source_asset_type                  | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                            | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | No          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y en su lugar se mostrará con tipo de activo 'native'                                                                                                                                                                                                                                                                     |
-| details.source_max                         | La cantidad máxima que se enviará, designada en el activo de origen                                                                                                                                                                                                                                     | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Intercambiar un activo causa que una pequeña cantidad del valor del activo se utilice en tarifas y tasas de cambio. El emisor puede especificar una cantidad máxima que está dispuesto a enviar si las tasas entre el par de activos son desfavorables.                                                                                                                                                                |
-| details.starting_balance                   | La cantidad de XLM para enviar a la cuenta recién creada. El saldo inicial de la cuenta deberá superar el saldo mínimo necesario para mantener una cuenta en la red Stellar                                                                                                                             | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.to                                 | La dirección de la cuenta que recibe los fondos del pago                                                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.to_muxed                           | Si la cuenta está multiplexada, la dirección virtual de la cuenta que recibe el pago                                                                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.to_muxed_id                        | Si la cuenta está multiplexada, la representación entera de la dirección virtual de la cuenta receptora                                                                                                                                                                                                 | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustee                            | La dirección de la cuenta emisora (presente solo para tipos de activos `credit`)                                                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustee_muxed                      | Si la dirección de la cuenta emisora está multiplexada, la dirección virtual                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustee_muxed_id                   | Si la dirección de la cuenta emisora está multiplexada, la representación entera de la dirección virtual                                                                                                                                                                                                | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustline_account_id               | La dirección de la cuenta cuya trustline ya no está patrocinada                                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustline_asset                    | El activo de la trustline que ya no está patrocinada                                                                                                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Un patrocinador puede decidir revocar el patrocinio de ciertos activos pero mantener el patrocinio de otros activos                                                                                                                                                                                                                                                                                                    |
-| details.trustor                            | La dirección de la cuenta que confía, o la cuenta que está autorizada o no autorizada                                                                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustor_muxed                      | Si la cuenta que confía está multiplexada, la dirección virtual de la cuenta                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustor_muxed_id                   | Si la cuenta que confía está multiplexada, la representación entera de la dirección virtual                                                                                                                                                                                                             | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.value                              | La operación de gestionar datos permite que una cuenta escriba y almacene datos directamente en el ledger en formato de par clave-valor. El valor es el valor de una clave para una entrada de datos                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.clear_flags                        | Array de valores numéricos de los flags eliminados para una trustline dada en la operación. Si el flag estaba originalmente establecido, esto eliminará el flag                                                                                                                                         | array[entero]   | <ul><li>1 - Auth Required</li><li>2 - Auth Revocable</li><li>4 - Auth Immutable</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.clear_flags_s                      | Array de valores de cadena de los flags eliminados para una trustline dada en la operación. Si el flag estaba originalmente establecido, esto eliminará el flag                                                                                                                                         | array[cadena]   | <ul><li>Auth Required</li><li>Auth Revocable</li><li>Auth Immutable</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.destination_min                    | La cantidad mínima que debe recibirse, designada en el activo esperado de destino                                                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Intercambiar un activo genera un pequeño gasto del valor del activo en tarifas y tasas de intercambio. El remitente puede especificar una cantidad mínima garantizada que desea enviar al destinatario para asegurar que reciba un valor especificado.                                                                                                                                                                 |
-| details.bump_to                            | El nuevo valor deseado del número de secuencia de la cuenta fuente                                                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.authorize_to_maintain_liabilities  | Indica si la trustline está autorizada. 0 si la cuenta no está autorizada para transaccionar con el activo de ninguna manera. 1 si la cuenta está autorizada para transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones.         | booleano        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.clawback_enabled                   | Indica si el activo puede ser recuperado por el emisor del activo                                                                                                                                                                                                                                       | booleano        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.sponsor                            | La dirección de otra cuenta que mantiene el saldo mínimo en XLM para que la cuenta fuente complete operaciones                                                                                                                                                                                          | cadena          | Cualquier Tipo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.sponsored_id                       | La dirección de la cuenta que será patrocinada                                                                                                                                                                                                                                                          | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.begin_sponsor                      | La dirección de la cuenta que inició el patrocinio                                                                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.begin_sponsor_muxed                | Si la cuenta que inició el patrocinio está multiplexada, la dirección virtual                                                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.begin_sponsor_muxed_id             | Si la cuenta que inició el patrocinio está multiplexada, la representación entera de la dirección virtual                                                                                                                                                                                               | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.liquidity_pool_id                  | Identificador único para un pool de liquidez                                                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Los pools de liquidez son mercados automatizados entre un par de activos. Un pool dado solo tendrá dos activos a menos que haya un cambio de protocolo                                                                                                                                                                                                                                                                 |
-| details.reserve_a_asset_type               | El identificador para el tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM                                                                                                                                                           | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_a_asset_code               | La representación en código de 4 o 12 caracteres del activo de uno de los dos pares de activos en un pool de liquidez                                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_a_asset_issuer             | La dirección de la cuenta del emisor original del activo que creó uno de los dos pares en el pool de liquidez                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_a_max_amount               | La cantidad máxima de reserva a que puede ser depositada en el pool                                                                                                                                                                                                                                     | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Las operaciones de depósito calculan mediante fórmula cuánto de ambos activos a y b deben ser depositados desde una cuenta fuente hacia un pool. La cuenta fuente debe depositar un valor equivalente de ambos activos a y b. Como los mercados fluctúan, un monto máximo especifica el límite superior de un activo que la cuenta está dispuesta a depositar                                                          |
-| details.reserve_a_deposit_amount           | La cantidad de reserva a que terminó siendo depositada efectivamente en el pool                                                                                                                                                                                                                         | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_asset_type               | El identificador para el tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM                                                                                                                                                           | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_asset_code               | La representación en código de 4 o 12 caracteres del activo de uno de los dos pares de activos en un pool de liquidez                                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_asset_issuer             | La dirección de la cuenta del emisor original del activo que creó uno de los dos pares en el pool de liquidez                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_max_amount               | La cantidad máxima de reserva b que puede ser depositada en el pool                                                                                                                                                                                                                                     | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Las operaciones de depósito calculan mediante fórmula cuánto de ambos activos a y b deben ser depositados desde una cuenta fuente hacia un pool. La cuenta fuente debe depositar un valor equivalente de ambos activos a y b. Como los mercados fluctúan, un monto máximo especifica el límite superior de un activo que la cuenta está dispuesta a depositar                                                          |
-| details.reserve_b_deposit_amount           | La cantidad de reserva b que terminó siendo depositada efectivamente en el pool                                                                                                                                                                                                                         | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.min_price                          | El valor flotante que indica la tasa mínima de intercambio para esta operación de depósito. Reportado como Reserva A / Reserva B                                                                                                                                                                        | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Las tasas de mercado fluctúan para la fijación de precios y la cuenta fuente puede especificar un precio mínimo que espera recibir como ratio de los dos activos en el pool                                                                                                                                                                                                                                            |
-| details.min_price_r                        | Una representación fraccionaria de los precios de los dos activos en un pool. El n es el numerador (valor del activo a) y la d es el denominador (valor del activo b)                                                                                                                                   | array[registro] |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.max_price                          | El valor flotante que indica la tasa máxima de intercambio para esta operación de depósito. Reportado como Reserva A / Reserva B                                                                                                                                                                        | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Las tasas de mercado fluctúan para la fijación de precios y la cuenta fuente puede especificar un precio máximo que espera recibir como ratio de los dos activos en el pool                                                                                                                                                                                                                                            |
-| details.max_price_r                        | Una representación fraccionaria de los precios de los dos activos en un pool. El n es el numerador (valor del activo a) y la d es el denominador (valor del activo b)                                                                                                                                   | array[registro] |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.shares_received                    | Un número flotante que representa la cantidad de acciones del pool recibidas por este depósito. Una acción del pool es una compilación de ambos activos a y b en reservas. No es posible poseer solo el activo a o el activo b en un pool                                                               | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_a_min_amount               | La cantidad mínima de reserva a que puede retirarse del pool                                                                                                                                                                                                                                            | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_a_withdraw_amount          | La cantidad de reserva a que terminó siendo retirada efectivamente del pool                                                                                                                                                                                                                             | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_min_amount               | La cantidad mínima de reserva b que puede retirarse del pool                                                                                                                                                                                                                                            | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_withdraw_amount          | La cantidad de reserva b que terminó siendo retirada efectivamente del pool                                                                                                                                                                                                                             | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.shares                             | El número de acciones retiradas del pool. No es posible retirar solo el activo a o el activo b; debe retirarse un valor igual del pool                                                                                                                                                                  | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_balance_changes              | Los cambios de saldo aplicados a una cuenta o contrato desde una función host de invocación. Un activo debe ser un activo clásico transferido a través del [SAC](https://soroban.stellar.org/docs/tokens/stellar-asset-contract) para ser incluido.                                                     | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_balance_changes.amount       | La cantidad de token acuñado, transferido o quemado usando el contrato SAC                                                                                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_balance_changes.asset_code   | La representación en código de 4 o 12 caracteres del activo transferido usando el contrato SAC                                                                                                                                                                                                          | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_balance_changes.asset_issuer | La dirección wallet de la cuenta que emitió el activo. Este activo es un activo clásico aunque es enviado a través del contrato SAC                                                                                                                                                                     | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_balance_changes.asset_type   | El identificador para el tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM                                                                                                                                                           | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_balance_changes.from         | La dirección wallet o id de contrato origen desde donde se enviaron los fondos                                                                                                                                                                                                                          | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_balance_changes.to           | La dirección wallet o id de contrato de destino donde van los fondos                                                                                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_balance_changes.type         | El tipo específico de operación SAC que indica el tipo de transferencia de valor que ocurre.                                                                                                                                                                                                            | cadena          | <ul><li>mint</li><li>transfer</li><li>burn</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.parameters                         | Los parámetros pasados a la llamada de función para un contrato Soroban. Estos están codificados en base64 en formato XDR. El registro sigue el formato de par `tipo` + `valor`                                                                                                                         | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.parameters_decoded                 | Los parámetros decodificados legibles por humanos pasados a una llamada de función para un contrato Soroban. El registro sigue el formato de par `tipo` + `valor`                                                                                                                                       | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.function                           | El tipo de función invocada por la operación host                                                                                                                                                                                                                                                       | cadena          | <ul><li>HostFunctionTypeHostFunctionTypeInvokeContract</li><li>HostFunctionTypeHostFunctionTypeCreateContract</li><li>HostFunctionTypeHostFunctionTypeUploadContractWasm</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.address                            | La dirección wallet usada para crear y desplegar una instancia de contrato Soroban                                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.type                               | El tipo de operación Soroban que es invocada dentro de una función host                                                                                                                                                                                                                                 | cadena          | <ul><li>invoke_contract</li><li>create_contract</li><li>upload_wasm</li><li>extend_footprint_ttl</li><li>restore_footprint</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.extend_to                          | El número de ledgers en los cuales la entrada de ledger Soroban se extiende                                                                                                                                                                                                                             | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.contract_id                        | El identificador único de la instancia de contrato desplegada. Cada contrato Soroban personalizado y token SAC desplegado tendrá un contract_id único                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.contract_code_hash                 | El hash SHA-256 codificado en hexadecimal que representa la forma codificada en XDR del código del contrato                                                                                                                                                                                             | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| batch_id                                   | Representación en cadena del run id para un DAG dado en Airflow. Tiene la forma `scheduled__<batch_end_date>-<dag_alias>`. Los batch ids son únicos para el batch y ayudan con el monitoreo y capacidades de reejecución                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| batch_run_date                             | La fecha de inicio para el intervalo del batch. Tomada junto con la fecha en batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger                                                                    | datetime        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta                                                                                                                                                                                                                                                   |
-| batch_insert_ts                            | La marca de tiempo en UTC cuando un batch de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un backfill                                                                                                       | timestamp       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| closed_at                                  | Marca de tiempo en UTC cuando este ledger cerró y se comprometió en la red. Se espera que los ledgers cierren aproximadamente cada 5 segundos                                                                                                                                                           | timestamp       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          | Estamos planeando reparticionar esta tabla sobre closed_at                                                                                                                                                                                                                                                                                                                                                             |
-| operation_result_code                      | El código de resultado devuelto cuando se aplica una operación. Este código es útil para entender operaciones fallidas                                                                                                                                                                                  | cadena          | <ul><li>OperationResultCodeOpInner</li><li>OperationResultCodeOpBadAuth</li><li>OperationResultCodeOpNoAccount</li><li>OperationResultCodeOpNotSupported</li><li>OperationResultCodeOpTooManySubentries</li><li>OperationResultCodeOpExceededWorkLimit</li><li>OperationResultCodeOpTooManySponsoring</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Sí          | Este campo se llenará en una fecha futura                                                                                                                                                                                                                                                                                                                                                                              |
-| operation_trace_code                       | El código de traza devuelto cuando una operación es aplicada a la red Stellar. Este código es útil para entender fallos sutiles por tipo de operación. Este código proporciona el detalle más bajo respecto a por qué una transacción falla                                                             | cadena          | <ul><li>InvokeHostFunctionResultCodeInvokeHostFunctionSuccess</li><li>Malformed</li><li>Trapped</li><li>ResourceLimitExceeded</li><li>EntryArchived</li><li>InsufficientRefundableFee</li><li>ExtendFootprintTtlResultCodeExtendFootprintTtlSuccess</li><li>Malformed</li><li>ResourceLimitExceeded</li><li>InsufficientRefundableFee</li><li>RestoreFootprintResultCodeRestoreFootprintSuccess</li><li>Malformed</li><li>ResourceLimitExceeded</li><li>InsufficientRefundableFee</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                           | Sí          | Consulta la [documentación](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/xdr#OperationResultTr) de XDR para más detalles                                                                                                                                                                                                                                                                                       |
-| details_json                               | Registro que contiene detalles basados en el tipo de operación ejecutada. Cada operación devolverá sus propios detalles relevantes, con el resto de los detalles como nulos                                                                                                                             | json            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |             |                                                                                                                                                                                                                                                                                                                                                                                                                        |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.mdx
deleted file mode 100644
index d475bcc5b6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-trades.mdx
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Operaciones Históricas
-sidebar_position: 130
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad                | Configuración                                                                                                 |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)     | history_operation_id, order                                                                                   |
-| Campo(s) de Partición    | ledger_closed_at (partición MENSUAL)                                                                          |
-| Campo(s) Clusterizado(s) | selling_asset_id, buying_asset_id, trade_type                                                                 |
-| Documentación            | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_trades) |
-
-## Detalles de la Columna
-
-| Nombre                    | Descripción                                                                                                                                                                                                                                                                                                                                                                            | Tipo de Datos | Valores del Dominio                                                                                 | ¿Requerido? | Notas                                                                                                                                                                 |
-| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| history_operation_id      | El identificador de la operación asociada con la operación ejecutada. La cantidad total negociada en una operación puede dividirse en varias operaciones más pequeñas distribuidas en múltiples órdenes por varias partes.                                                                                                                                                             | integer       |                                                                                                     | Sí          | Existe una relación de muchos a uno para history_operation_id con la tabla history_operations.                                                                        |
-| order                     | El número secuencial asignado a la porción de una operación que se ejecuta dentro de una operación. El history_operation_id y el número de orden juntos representan un segmento único de la operación.                                                                                                                                                                                 | integer       |                                                                                                     | Sí          |                                                                                                                                                                       |
-| ledger_closed_at          | La marca de tiempo en UTC cuando se cerró el ledger con esta operación                                                                                                                                                                                                                                                                                                                 | timestamp     |                                                                                                     | Sí          |                                                                                                                                                                       |
-| selling_account_address   | La dirección de cuenta de la parte vendedora                                                                                                                                                                                                                                                                                                                                           | string        |                                                                                                     | No          |                                                                                                                                                                       |
-| selling_asset_code        | El código del activo vendido de 4 o 12 caracteres dentro de una operación                                                                                                                                                                                                                                                                                                              | string        |                                                                                                     | No          | Los códigos de activos no garantizan unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto                                        |
-| selling_asset_issuer      | La dirección de cuenta del emisor original del activo vendido dentro de una operación                                                                                                                                                                                                                                                                                                  | string        |                                                                                                     | No          |                                                                                                                                                                       |
-| selling_asset_type        | El identificador para el tipo de código de activo usado para el activo vendido dentro de la operación                                                                                                                                                                                                                                                                                  | string        | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                         | Sí          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y en cambio se mostrará con un tipo de activo 'native'                   |
-| selling_amount            | La cantidad del activo vendido que se movió de la cuenta del vendedor a la cuenta del comprador, reportada en términos del monto vendido                                                                                                                                                                                                                                               | float         |                                                                                                     | Sí          |                                                                                                                                                                       |
-| buying_account_address    | La dirección de cuenta de la parte compradora                                                                                                                                                                                                                                                                                                                                          | string        |                                                                                                     | No          |                                                                                                                                                                       |
-| buying_asset_code         | El código del activo comprado de 4 o 12 caracteres dentro de una operación                                                                                                                                                                                                                                                                                                             | string        |                                                                                                     | No          | Los códigos de activos no garantizan unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto                                        |
-| buying_asset_issuer       | La dirección de cuenta del emisor original del activo comprado dentro de una operación                                                                                                                                                                                                                                                                                                 | string        |                                                                                                     | No          |                                                                                                                                                                       |
-| buying_asset_type         | El identificador para el tipo de código de activo usado para el activo comprado dentro de la operación                                                                                                                                                                                                                                                                                 | string        | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                         | Sí          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y en cambio se mostrará con un tipo de activo 'native'                   |
-| buying_amount             | La cantidad del activo comprado que se movió de la cuenta del vendedor a la cuenta del comprador, reportada en términos del monto comprado                                                                                                                                                                                                                                             | float         |                                                                                                     | Sí          |                                                                                                                                                                       |
-| price_n                   | La proporción de precio del activo vendido respecto al activo comprado. Junto con price_d, el precio puede calcularse mediante price_n/price_d                                                                                                                                                                                                                                         | integer       |                                                                                                     | No          |                                                                                                                                                                       |
-| price_d                   | La proporción de precio del activo vendido respecto al activo comprado. Junto con price_n, el precio puede calcularse mediante price_n/price_d                                                                                                                                                                                                                                         | integer       |                                                                                                     | No          |                                                                                                                                                                       |
-| selling_offer_id          | El ID de la oferta en el libro de órdenes de la oferta de venta. Si esta oferta fue consumida inmediatamente y en su totalidad, este será un ID sintético.                                                                                                                                                                                                                             | integer       |                                                                                                     | No          |                                                                                                                                                                       |
-| buying_offer_id           | El ID de la oferta en el libro de órdenes de la oferta de compra. Si esta oferta fue consumida inmediatamente y en su totalidad, este será un ID sintético.                                                                                                                                                                                                                            | integer       |                                                                                                     | No          |                                                                                                                                                                       |
-| batch_id                  | Representación en cadena del ID de ejecución para un DAG dado en Airflow. Tiene la forma `scheduled__<batch_end_date>-<dag_alias>`. Los batch IDs son únicos para el batch y ayudan con el monitoreo y las capacidades de re-ejecución                                                                                                                                                 | string        |                                                                                                     | No          |                                                                                                                                                                       |
-| batch_run_date            | La fecha de inicio para el intervalo del batch. Junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger.                                                                                                                                                      | datetime      |                                                                                                     | No          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta. |
-| batch_insert_ts           | La marca de tiempo en UTC cuando un batch de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de una recarga histórica                                                                                                                                                                            | timestamp     |                                                                                                     | No          |                                                                                                                                                                       |
-| selling_liquidity_pool_id | El identificador único para un liquidity pool si la operación se ejecutó contra un liquidity pool en lugar del libro de órdenes                                                                                                                                                                                                                                                        | string        |                                                                                                     | No          |                                                                                                                                                                       |
-| liquidity_pool_fee        | El porcentaje de comisión (en puntos base) de la comisión total recolectada por el liquidity pool al ejecutar la operación. La comisión se acumula y se distribuye de vuelta a los accionistas del liquidity pool para incentivar a los usuarios a apostar dinero en el pool.                                                                                                          | integer       | 30                                                                                                  | No          | Las comisiones de los liquidity pools solo pueden cambiar con cambios de protocolo a la red misma                                                                     |
-| trade_type                | Indica si la operación se ejecutó contra el libro de órdenes (exchange descentralizado) o un liquidity pool                                                                                                                                                                                                                                                                            | integer       | <ul><li>1 - Operación de Exchange Descentralizado</li><li>2 - Operación de Liquidity Pool</li></ul> | No          |                                                                                                                                                                       |
-| rounding_slippage         | Aplica solo a operaciones de liquidity pool. Con cantidades fraccionarias de un activo negociado, la red debe redondear una fracción al número entero más cercano. Esto puede causar que la operación "deslice" el precio un porcentaje comparado con la oferta original. El slippage por redondeo reporta el porcentaje que las operaciones de polvo se deslizan antes de ejecutarse. | integer       |                                                                                                     | No          | Por defecto es 1. El slippage por redondeo siempre es perjudicial para el operador y no es una forma válida de intentar extraer más valor de la red.                  |
-| seller_is_exact           | Indica si la operación de la parte compradora o vendedora fue afectada por el slippage por redondeo. Si es verdadero, el comprador fue afectado. Si es falso, el vendedor fue afectado.                                                                                                                                                                                                | boolean       |                                                                                                     | No          |                                                                                                                                                                       |
-| selling_asset_id          | Identificador único para selling_asset_code, selling_asset_issuer                                                                                                                                                                                                                                                                                                                      | integer       |                                                                                                     | No          |                                                                                                                                                                       |
-| buying_asset_id           | Identificador único para buying_asset_code, buying_asset_issuer                                                                                                                                                                                                                                                                                                                        | integer       |                                                                                                     | No          |                                                                                                                                                                       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.mdx
deleted file mode 100644
index 7358086996..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/history-transactions.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Historial de Transacciones
-sidebar_position: 140
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                       |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | id                                                                                                                  |
-| Campo(s) de Partición | batch_run_date (partición MENSUAL)                                                                                  |
-| Campo(s) Agrupados    | account, ledger_sequence, successful                                                                                |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_transactions) |
-
-## Detalles de Columnas
-
-| Nombre                              | Descripción                                                                                                                                                                                                                                                                                                                                                               | Tipo de Dato    | Valores de Dominio                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | ¿Requerido? | Notas                                                                                                                                                                                          |
-| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| id                                  | Un identificador único para esta transacción                                                                                                                                                                                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          |                                                                                                                                                                                                |
-| transaction_hash                    | Un hash codificado en hexadecimal SHA-256 del formulario codificado en XDR de esta transacción                                                                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |                                                                                                                                                                                                |
-| ledger_sequence                     | El número de secuencia del ledger en el que se incluyó esta transacción                                                                                                                                                                                                                                                                                                   | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          |                                                                                                                                                                                                |
-| account                             | La dirección de la cuenta que origina la transacción                                                                                                                                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          |                                                                                                                                                                                                |
-| account_sequence                    | El número de secuencia de la cuenta origen que esta transacción consumió. Los números de secuencia solo pueden usarse una vez y ayudan a mantener la atomicidad y la idempotencia en la red.                                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          |                                                                                                                                                                                                |
-| max_fee                             | La tarifa máxima (en stroops) que la cuenta origen está dispuesta a pagar para que la transacción se incluya en un ledger. Cuando la red entra en tarificación por congestión, esto ayuda a determinar si una transacción se incluye en el conjunto                                                                                                                       | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          | El stroop es la representación fraccional de un lumen (XLM). 1 stroop es 0.0000001 XLM.                                                                                                        |
-| operation_count                     | El número de operaciones contenidas dentro de esta transacción                                                                                                                                                                                                                                                                                                            | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          | Una transacción puede contener hasta 100 operaciones                                                                                                                                           |
-| created_at                          | La fecha en que se creó la transacción                                                                                                                                                                                                                                                                                                                                    | marca de tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| memo_type                           | El tipo de memo                                                                                                                                                                                                                                                                                                                                                           | cadena          | <ul><li>MemoTypeMemoHash</li><li>MemoTypeMemoId</li><li>MemoTypeMemoNone</li><li>MemoTypeMemoReturn</li><li>MemoTypeMemoText</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Sí          | Por defecto es `MemoTypeMemoNone`                                                                                                                                                              |
-| memo                                | Un campo opcional de texto libre que adjunta un memo a una transacción                                                                                                                                                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          | Los memos son usados ampliamente por las exchanges centralizadas para ayudar en la gestión de cuentas.                                                                                         |
-| time_bounds                         | Una precondición de transacción que puede establecerse para determinar cuándo una transacción es válida. El usuario puede establecer un límite inferior y superior de tiempo, definido como una marca de tiempo UNIX en la que la transacción puede ejecutarse. Si la transacción intenta ejecutarse fuera del rango de tiempo, la transacción fallará                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| successful                          | Indica si esta transacción fue exitosa o no                                                                                                                                                                                                                                                                                                                               | booleano        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          | El éxito de una transacción no indica si fue incluida y escrita en un ledger. Solo indica si las operaciones en la transacción se aplicaron correctamente para modificar el estado del ledger. |
-| fee_charged                         | La tarifa (en stroops) pagada por la cuenta origen para aplicar esta transacción al ledger. Como mínimo, una transacción se cobra número de operaciones \* tarifa base. La tarifa base mínima es 100 stroops                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          | El stroop es la representación fraccional de un lumen (XLM). 1 stroop es 0.0000001 XLM.                                                                                                        |
-| inner_transaction_hash              | Un hash de transacción de una transacción envuelta con sus firmas para transacciones con fee-bump                                                                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| fee_account                         | Una cuenta que no es la cuenta origen de una transacción puede pagar las tarifas de transacción en nombre de la cuenta origen. Estas cuentas se llaman cuentas de tarifa y asumen todos los costos de transacción para la cuenta origen.                                                                                                                                  | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| new_max_fee                         | Si una cuenta tiene una cuenta de tarifa, la cuenta de tarifa puede especificar una tarifa máxima (en stroops) que esté dispuesta a pagar por las tarifas de esta cuenta. Cuando la red está en tarificación por congestión, los validadores considerarán new_max_fee en lugar de max_fee para determinar si la transacción será incluida en el conjunto de transacciones | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| account_muxed                       | Si el usuario ha definido cuentas multiplexadas (muxed), la cuenta existe "virtualmente" bajo una dirección tradicional de cuenta Stellar. Esta dirección distingue entre las cuentas virtuales                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| fee_account_muxed                   | Si la cuenta de tarifa que patrocina la tarifa es una cuenta multiplexada, la dirección virtual se listará aquí                                                                                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| ledger_bounds                       | Una precondición de transacción que puede establecerse para determinar condiciones válidas para que una transacción sea enviada a la red. Los límites del ledger permiten al usuario especificar un número de secuencia mínimo y máximo del ledger en el que la transacción puede ejecutarse exitosamente                                                                 | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| min_account_sequence                | Una precondición de transacción que puede establecerse para determinar condiciones válidas para que una transacción sea enviada a la red. Esta condición contiene una representación entera del número de secuencia mínimo de la cuenta origen para la cual la transacción es válida                                                                                      | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| min_account_sequence_age            | Una precondición de transacción que puede establecerse para determinar condiciones válidas para que una transacción sea enviada a la red. Esta condición contiene una duración mínima de tiempo que debe haber pasado desde que cambió el número de secuencia de la cuenta origen para que la transacción sea válida                                                      | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| min_account_sequence_ledger_gap     | Una precondición de transacción que puede establecerse para determinar condiciones válidas para que una transacción sea enviada a la red. Esta condición contiene una representación entera del número mínimo de ledgers que deben haberse cerrado desde el cambio del número de secuencia de la cuenta origen para que la transacción sea válida                         | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| extra_signers                       | Un arreglo de hasta dos firmantes adicionales que deben tener firmas correspondientes para que esta transacción sea válida                                                                                                                                                                                                                                                | array[cadena]   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| tx_envelope                         | blob XDR codificado en base-64                                                                                                                                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| tx_result                           | blob XDR codificado en base-64                                                                                                                                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| tx_meta                             | blob XDR codificado en base-64                                                                                                                                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| tx_fee_meta                         | blob XDR codificado en base-64                                                                                                                                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| batch_id                            | Representación en cadena del id de ejecución para un DAG dado en Airflow. Tiene la forma "scheduled\_\_[batch_end_date]-[dag_alias]". Los batch ids son únicos para el batch y ayudan con el monitoreo y las capacidades de reejecución                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          |                                                                                                                                                                                                |
-| batch_run_date                      | La fecha de inicio para el intervalo del batch. Cuando se toma junto con la fecha en batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger.                                                                                                                             | datetime        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta.                          |
-| batch_insert_ts                     | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un relleno (backfill)                                                                                                                                                                | marca de tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          |                                                                                                                                                                                                |
-| resource_fee                        | La tarifa cobrada menos la tarifa de inclusión para la transacción de Soroban. Esto se calcula según las operaciones de lectura/escritura y qué tan intensiva en procesos es la transacción Soroban                                                                                                                                                                       | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| soroban_resources_instructions      | Número de instrucciones de CPU que usa la transacción Soroban                                                                                                                                                                                                                                                                                                             | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| soroban_resources_read_bytes        | Número de bytes leídos por la transacción Soroban                                                                                                                                                                                                                                                                                                                         | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| soroban_resources_write_bytes       | Número de bytes escritos por la transacción Soroban                                                                                                                                                                                                                                                                                                                       | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| closed_at                           | Marca de tiempo en UTC cuando este ledger se cerró y se comprometió a la red. Se espera que los ledgers cierren aproximadamente cada 5 segundos                                                                                                                                                                                                                           | marca de tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | Sí          | Planeamos reparticionar la tabla por closed_at                                                                                                                                                 |
-| transaction_result_code             | El código de resultado detallado que explica por qué una transacción falló. Este código es útil solo para transacciones fallidas. La lista completa de valores de dominio se puede encontrar [aquí](https://pkg.go.dev/github.com/stellar/go-stellar-sdk/xdr#TransactionResultCode)                                                                                       | cadena          | <ul><li>TransactionResultCodeTxFeeBumpInnerSuccess</li><li>TransactionResultCodeTxSuccess</li><li>TransactionResultCodeTxFailed</li><li>TransactionResultCodeTxTooEarly</li><li>TransactionResultCodeTxTooLate</li><li>TransactionResultCodeTxMissingOperation</li><li>TransactionResultCodeTxBadSeq</li><li>TransactionResultCodeTxBadAuth</li><li>TransactionResultCodeTxInsufficientBalance</li><li>TransactionResultCodeTxNoAccount</li><li>TransactionResultCodeTxInsufficientFee</li><li>TransactionResultCodeTxBadAuthExtra</li><li>TransactionResultCodeTxInternalError</li><li>TransactionResultCodeTxNotSupported</li><li>TransactionResultCodeTxFeeBumpInnerFailed</li><li>TransactionResultCodeTxBadSponsorship</li><li>TransactionResultCodeTxBadMinSeqAgeOrGap</li><li>TransactionResultCodeTxMalformed</li><li>TransactionResultCodeTxSorobanInvalid</li></ul> | Sí          |                                                                                                                                                                                                |
-| inclusion_fee_bid                   | La puja máxima que el remitente está dispuesto a pagar por la inclusión de la transacción. Esta tarifa se usa para priorizar las transacciones que se incluyen en el ledger.                                                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| inclusion_fee_charged               | La tarifa cobrada para que la transacción sea incluida en el ledger. Esta es una tarifa fija para todo el ledger que comienza en un mínimo de 100 stroops. La tarifa aumenta según la demanda                                                                                                                                                                             | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| resource_fee_refund                 | La cantidad de la tarifa de recurso reembolsada al remitente de la transacción. Las tarifas reembolsables se calculan a partir de renta, eventos y valores de retorno. Las tarifas reembolsables se cargan de la cuenta origen antes de que la transacción se ejecute y luego se reembolsan según el uso real.                                                            | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | No          |                                                                                                                                                                                                |
-| non_refundable_resource_fee_charged | La cantidad cobrada por la transacción que no es reembolsable                                                                                                                                                                                                                                                                                                             | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |                                                                                                                                                                                                |
-| refundable_resource_fee_charged     | La cantidad cobrada por la transacción desde la tarifa reembolsable                                                                                                                                                                                                                                                                                                       | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |                                                                                                                                                                                                |
-| rent_fee_charged                    | La tarifa de renta cobrada para persistir el contrato o el código del contrato                                                                                                                                                                                                                                                                                            | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |                                                                                                                                                                                                |
-| refundable_fee                      | La cantidad de tarifas de recursos que son reembolsables según el uso real de recursos en la transacción                                                                                                                                                                                                                                                                  | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |                                                                                                                                                                                                |
-| tx_signers                          | Las claves públicas de los firmantes que autorizaron la transacción. Este campo lista a todos los signatarios que validaron y aprobaron la transacción, asegurando que cumple con los umbrales de autorización requeridos                                                                                                                                                 | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |             |                                                                                                                                                                                                |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.mdx
deleted file mode 100644
index 37a873bb6b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/liquidity-pools.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Pools de Liquidez
-sidebar_position: 50
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                  |
-| --------------------- | -------------------------------------------------------------------------------------------------------------- |
-| Llave(s) Natural(es)  | liquidity_pool_id, closed_at                                                                                   |
-| Campo(s) de Partición | batch_run_date (partición MENSUAL)                                                                             |
-| Campo(s) Agrupado(s)  | liquidity_pool_id, asset_a_id, asset_b_id, last_modified_ledger                                                |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.liquidity_pools) |
-
-## Detalles de Columnas
-
-| Nombre               | Descripción                                                                                                                                                                                                                                                                   | Tipo de Datos | Valores de Dominio                                                                                                                                                                             | ¿Requerido? | Notas                                                                                                                                                                                                                                                                                                                                                           |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| liquidity_pool_id    | Identificador único para un pool de liquidez. No puede haber pools duplicados para el mismo par de activos. Una vez creado un pool para el par de activos, no se puede crear otro.                                                                                            | string        |                                                                                                                                                                                                | Sí          | Hay una buena introducción sobre AMMs [aquí](../../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#liquidity-pools)                                                                                                                                                                                                                |
-| type                 | El mecanismo que calcula el precio y la división de participaciones para el pool. Con el despliegue inicial del AMM, el único tipo de pool de liquidez permitido es un pool de producto constante                                                                             | string        | constant_product                                                                                                                                                                               | Sí          | Para más información sobre cálculos de precio y depósito, lee [Cap-38.](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md)                                                                                                                                                                                                               |
-| fee                  | El número de puntos base cobrados como porcentaje del intercambio para completar la transacción. Las comisiones ganadas en todas las operaciones se reparten entre los accionistas del pool y se distribuyen como incentivo para mantener fondos en los pools                 | integer       | 30                                                                                                                                                                                             | Sí          | Las comisiones se distribuyen inmediatamente a las cuentas a medida que se completa la transacción. No hay un calendario para la distribución de comisiones                                                                                                                                                                                                     |
-| trustline_count      | Número total de cuentas con trustlines autorizadas al pool. Para crear una trustline, una cuenta debe confiar en ambos activos base antes de confiar en un pool con el par de activos                                                                                         | integer       |                                                                                                                                                                                                | Sí          | Si el emisor de A o B revoca la autorización de la trustline, la cuenta se retirará automáticamente de todos los pools de liquidez que contengan ese activo y esas trustlines del pool serán eliminadas.                                                                                                                                                        |
-| pool_share_count     | La participación en un pool de liquidez se representa mediante una participación en el pool. El número total de participaciones en el pool se calcula con una fórmula de producto constante y es un número arbitrario que representa la cantidad de participación en el pool. | float         |                                                                                                                                                                                                | Sí          | Las participaciones no son transferibles; la única forma de aumentar el número de participaciones en el pool que se tienen es depositar en un pool de liquidez. Por el contrario, disminuir las participaciones del pool solo se puede lograr a través de una operación de retiro. Las participaciones no se pueden enviar en pagos ni vender mediante ofertas. |
-| asset_a_type         | El identificador para el tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                | string        | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                    | Sí          |                                                                                                                                                                                                                                                                                                                                                                 |
-| asset_a_code         | La representación del código de 4 o 12 caracteres del activo de uno de los dos pares de activos en un pool de liquidez                                                                                                                                                        | string        |                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                 |
-| asset_a_issuer       | La dirección de la cuenta del emisor original del activo que creó uno de los dos pares de activos en el pool de liquidez                                                                                                                                                      | string        |                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                 |
-| asset_a_amount       | El número bruto de tokens bloqueados en el pool para uno de los dos pares de activos en el pool de liquidez                                                                                                                                                                   | float         |                                                                                                                                                                                                | Sí          | El monto es una mejor representación de la liquidez en el pool que el conteo de participaciones en el pool.                                                                                                                                                                                                                                                     |
-| asset_b_type         | El identificador para el tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                | string        | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                    | Sí          |                                                                                                                                                                                                                                                                                                                                                                 |
-| asset_b_code         | La representación del código de 4 o 12 caracteres del activo de uno de los dos pares de activos en un pool de liquidez                                                                                                                                                        | string        |                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                 |
-| asset_b_issuer       | La dirección de la cuenta del emisor original del activo que creó uno de los dos pares de activos en el pool de liquidez                                                                                                                                                      | string        |                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                 |
-| asset_b_amount       | El número bruto de tokens bloqueados en el pool para uno de los dos pares de activos en el pool de liquidez                                                                                                                                                                   | float         |                                                                                                                                                                                                | Sí          | El monto es una mejor representación de la liquidez en el pool que el conteo de participaciones en el pool.                                                                                                                                                                                                                                                     |
-| last_modified_ledger | El número de secuencia del ledger cuando la entrada del ledger (este firmante único para la cuenta) fue modificado. Las eliminaciones no cuentan como modificación y reportarán el número de secuencia de modificación previo                                                 | integer       |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                                                                                                                                                                                 |
-| ledger_entry_change  | Código que describe el tipo de cambio en la entrada del ledger que se aplicó a la entrada del ledger.                                                                                                                                                                         | integer       | <ul><li>0 - Entrada de Ledger Creada</li><li>1 - Entrada de Ledger Actualizada</li><li>2 - Entrada de Ledger Eliminada</li><li>3 - Estado de Entrada de Ledger (valor de la entrada)</li></ul> | Sí          | Los tipos válidos de cambio de entrada son 0, 1 y 2 para entradas del ledger de tipo `liquidity_pools`.                                                                                                                                                                                                                                                         |
-| deleted              | Indica si la entrada del ledger (pool de liquidez) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede recuperarse. Los pools de liquidez se eliminan una vez que todas las participaciones del pool son retiradas del pool                                | boolean       |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                                                                                                                                                                                 |
-| batch_id             | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los batch ids son únicos para el batch y ayudan con la monitorización y capacidades de reejecución                                      | string        |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                                                                                                                                                                                 |
-| batch_run_date       | La fecha de inicio para el intervalo del batch. Cuando se combina con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch se puede considerar como un proxy de closed_at para un ledger.                         | datetime      |                                                                                                                                                                                                | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta.                                                                                                                                                                                           |
-| batch_insert_ts      | El sello temporal en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de una reposición de datos                                                                   | timestamp     |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                                                                                                                                                                                 |
-| asset_a_id           | Identificador único para asset_a_code, asset_a_issuer                                                                                                                                                                                                                         | integer       |                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                 |
-| asset_b_id           | Identificador único para asset_b_code, asset_b_issuer                                                                                                                                                                                                                         | integer       |                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                 |
-| closed_at            | Marca temporal en UTC cuando este ledger se cerró y se comprometió en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                                            | timestamp     |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                                                                                                                                                                                 |
-| ledger_sequence      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.                   | integer       |                                                                                                                                                                                                | Sí          |                                                                                                                                                                                                                                                                                                                                                                 |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.mdx
deleted file mode 100644
index c67fb73709..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/offers.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Ofertas
-sidebar_position: 60
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                         |
-| --------------------- | ----------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | offer_id, closed_at                                                                                   |
-| Campo(s) de partición | batch_run_date (partición MES)                                                                        |
-| Campo(s) agrupado(s)  | selling_asset_id, buying_asset_id, last_modified_ledger                                               |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.offers) |
-
-## Detalles de columnas
-
-| Nombre               | Descripción                                                                                                                                                                                                                                              | Tipo de dato    | Valores del dominio                                                                                                                                                                               | ¿Requerido? | Notas                                                                                                                                                                  |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| seller_id            | La dirección de la cuenta que realiza esta oferta                                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| offer_id             | El identificador único de esta oferta                                                                                                                                                                                                                    | entero          |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| selling_asset_type   | El identificador para el tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                            | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                       | Sí          |                                                                                                                                                                        |
-| selling_asset_code   | La representación del código de 4 o 12 caracteres del activo ofrecido para la venta                                                                                                                                                                      | cadena          |                                                                                                                                                                                                   | No          |                                                                                                                                                                        |
-| selling_asset_issuer | La dirección de la cuenta del emisor original del activo que creó el activo que se venderá a cambio de otro activo                                                                                                                                       | cadena          |                                                                                                                                                                                                   | No          |                                                                                                                                                                        |
-| buying_asset_type    | El identificador para el tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                            | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                       | Sí          |                                                                                                                                                                        |
-| buying_asset_code    | La representación del código de 4 o 12 caracteres del activo que se desea comprar                                                                                                                                                                        | cadena          |                                                                                                                                                                                                   | No          |                                                                                                                                                                        |
-| buying_asset_issuer  | La dirección de la cuenta del emisor original del activo que creó el activo que se comprará a cambio de un activo en posesión                                                                                                                            | cadena          |                                                                                                                                                                                                   | No          |                                                                                                                                                                        |
-| amount               | La cantidad de venta que la cuenta que hace esta oferta está dispuesta a vender                                                                                                                                                                          | flotante        |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| pricen               | El numerador de la representación precisa del precio de compra y venta de los activos en oferta (la cantidad deseada de compra)                                                                                                                          | entero          |                                                                                                                                                                                                   | Sí          | Si una oferta quiere vender 10 XLM a cambio de 1 USD, el numerador será 1.                                                                                             |
-| priced               | El denominador de la representación precisa del precio de compra y venta de los activos en oferta (la cantidad ofrecida a la venta)                                                                                                                      | entero          |                                                                                                                                                                                                   | Sí          | Si una oferta quiere vender 10 XLM a cambio de 1 USD, el denominador será 10.                                                                                          |
-| price                | Cuántas unidades del activo a comprar se necesitan para obtener 1 unidad del activo a vender. Este número es la forma decimal de pricen / priced                                                                                                         | flotante        |                                                                                                                                                                                                   | Sí          | Si una oferta quiere vender 10 XLM a cambio de 1 USD, el precio será 0.1                                                                                               |
-| flags                | Indica la activación/desactivación de ciertos privilegios del emisor del activo                                                                                                                                                                          | entero          | <ul><li>0 - Ninguno, Valor predeterminado</li><li>1 - Pasivo (una oferta con esta flag no actuará ni aceptará una oferta inversa con precio igual)</li></ul>                                      | Sí          |                                                                                                                                                                        |
-| last_modified_ledger | El número de secuencia del ledger cuando la entrada del ledger (este firmante único para la cuenta) fue modificada. Las eliminaciones no cuentan como modificaciones y reportarán el número de secuencia de modificación anterior                        | entero          |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| ledger_entry_change  | Código que describe el tipo de cambio aplicado en la entrada del ledger.                                                                                                                                                                                 | entero          | <ul><li>0 - Entrada de ledger creada</li><li>1 - Entrada de ledger actualizada</li><li>2 - Entrada de ledger eliminada</li><li>3 - Estado de la entrada de ledger (valor de la entrada)</li></ul> | Sí          | Los tipos válidos de cambio de entrada son 0, 1 y 2 para entradas de ledger del tipo `offers`.                                                                         |
-| deleted              | Indica si la entrada del ledger (offer id) ha sido eliminada o no. Una vez que una entrada es eliminada, no se puede recuperar                                                                                                                           | booleano        |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| closed_at            | Marca de tiempo en UTC cuando este ledger se cerró y confirmó en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                            | marca de tiempo |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| ledger_sequence      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que aumenta con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto. | entero          |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| sponsor              | La dirección de la cuenta que está patrocinando las reservas base para la oferta                                                                                                                                                                         | cadena          |                                                                                                                                                                                                   | No          |                                                                                                                                                                        |
-| batch_id             | Representación en cadena del ID de ejecución para un DAG dado en Airflow. Toma la forma `scheduled__<batch_end_date>-<dag_alias>`. Los IDs de batch son únicos para cada batch y ayudan con las capacidades de monitoreo y reejecución                   | cadena          |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| batch_run_date       | La fecha de inicio para el intervalo del batch. Cuando se toma junto con la fecha en el batch_id, representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger.                  | fecha y hora    |                                                                                                                                                                                                   | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible, para ayudar a reducir el costo de la consulta. |
-| batch_insert_ts      | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un retroceso                                                        | marca de tiempo |                                                                                                                                                                                                   | Sí          |                                                                                                                                                                        |
-| selling_asset_id     | Identificador único para selling_asset_code, selling_asset_issuer                                                                                                                                                                                        | entero          |                                                                                                                                                                                                   | No          |                                                                                                                                                                        |
-| buying_asset_id      | Identificador único para buying_asset_code, buying_asset_issuer                                                                                                                                                                                          | entero          |                                                                                                                                                                                                   | No          |                                                                                                                                                                        |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.mdx
deleted file mode 100644
index 7e7b51d8f5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/restored-key.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Clave restaurada
-sidebar_position: 61
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                               |
-| --------------------- | ----------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | ledger_key_hash, closed_at                                                                                  |
-| Campo(s) de partición | closed_at (partición MENSUAL)                                                                               |
-| Campo(s) agrupado(s)  | last_modified_ledger, ledger_key_hash                                                                       |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.restored_key) |
-
-## Detalles de columnas
-
-| Nombre               | Descripción                                                                                                                                                                                                                                                                                                                               | Tipo de dato   | Valores de dominio | ¿Requerido? | Notas |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | ------------------ | ----------- | ----- |
-| ledger_key_hash      | Contrato_id o contract_code_hash                                                                                                                                                                                                                                                                                                          | cadena         |                    | Sí          |       |
-| ledger_entry_type    | El tipo de entrada ledger para datos almacenados como datos de contrato o piscinas de liquidez                                                                                                                                                                                                                                            | cadena         |                    | Sí          |       |
-| last_modified_ledger | El número de secuencia del ledger cuando se modificó la entrada ledger (este firmante único para la cuenta). Las eliminaciones no cuentan como una modificación y reportarán el número de secuencia de modificación previo. Las eliminaciones no cuentan como una modificación y reportarán el número de secuencia de modificación previa | entero         |                    | Sí          |       |
-| batch_id             | Representación en cadena del ID de ejecución para un DAG dado en Airflow. Tiene la forma `scheduled__<batch_end_date>-<dag_alias>`. Los IDs de lote son únicos para el lote y ayudan con el monitoreo y las capacidades de reejecución                                                                                                    | cadena         |                    | Sí          |       |
-| batch_run_date       | La fecha de inicio para el intervalo del lote. Tomada junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de closed_at para un ledger.                                                                                                    | fecha y hora   |                    | Sí          |       |
-| batch_insert_ts      | El timestamp en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un backfill                                                                                                                                                 | marca temporal |                    | Sí          |       |
-| closed_at            | Timestamp en UTC cuando este ledger se cerró y comprometió a la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                                                                                                                 | marca temporal |                    | Sí          |       |
-| ledger_sequence      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.                                                                                  | entero         |                    | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.mdx
deleted file mode 100644
index 445654de60..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/trustlines.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Líneas de confianza
-sidebar_position: 70
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                              |
-| --------------------- | ---------------------------------------------------------------------------------------------------------- |
-| Clave natural (s)     | account_id, asset_type, asset_issuer, asset_code, liquidity_pool_id, closed_at                             |
-| Campo(s) de partición | batch_run_date (partición MES)                                                                             |
-| Campo(s) agrupados    | account_id, asset_id, liquidity_pool_id, last_modified_ledger                                              |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.trust_lines) |
-
-## Detalles de columnas
-
-| Nombre               | Descripción                                                                                                                                                                                                                                                 | Tipo de dato | Valores de dominio                                                                                                                                                       | ¿Requerido? | Notas                                                                                                                                                                                    |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| ledger_key           | La clave única del ledger cuando el estado de la línea de confianza cambió por última vez                                                                                                                                                                   | string       |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| account_id           | La dirección de la cuenta                                                                                                                                                                                                                                   | string       |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| asset_type           | El identificador para el tipo de código de activo, puede ser alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                 | integer      | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                              | Sí          |                                                                                                                                                                                          |
-| asset_issuer         | La dirección de la cuenta del emisor original del activo que creó el activo que posee esta cuenta                                                                                                                                                           | string       |                                                                                                                                                                          | No          |                                                                                                                                                                                          |
-| asset_code           | La representación del código de 4 o 12 caracteres del activo que posee esta cuenta                                                                                                                                                                          | string       |                                                                                                                                                                          | No          |                                                                                                                                                                                          |
-| liquidity_pool_id    | Si el activo es parte de una participación en un pool de liquidez, el id único del pool del cual se origina el saldo del activo                                                                                                                             | string       |                                                                                                                                                                          | No          |                                                                                                                                                                                          |
-| balance              | El número de unidades de un activo que posee esta cuenta                                                                                                                                                                                                    | float        |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| trust_line_limit     | La cantidad máxima de este activo que esta cuenta está dispuesta a aceptar. El límite se especifica cuando se abre una línea de confianza                                                                                                                   | integer      |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| buying_liabilities   | La suma de todas las ofertas de compra propiedad de esta cuenta para activos no nativos                                                                                                                                                                     | float        |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| selling_liabilities  | La suma de todas las ofertas de venta propiedad de esta cuenta para activos no nativos                                                                                                                                                                      | float        |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| flags                | Denota la habilitación y deshabilitación de ciertas privilegios del emisor del activo                                                                                                                                                                       | integer      | <ul><li>0 - Ninguno, Predeterminado</li><li>1 - Autorizado</li><li>2 - Autorizado para Mantener Pasivos</li><li>4 - Recuperación Activada</li></ul>                      | Sí          | Las flags se establecen en las cuentas de los emisores para un activo. Cuando las cuentas de los usuarios confían en un activo, las flags aplicadas al activo se originan en esta cuenta |
-| last_modified_ledger | El número de secuencia del ledger cuando la entrada del ledger (este firmante único para la cuenta) fue modificada                                                                                                                                          | integer      |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| ledger_entry_change  | Código que describe el tipo de cambio aplicado a la entrada del ledger                                                                                                                                                                                      | integer      | <ul><li>0 - Entrada de ledger creada</li><li>1 - Entrada de ledger actualizada</li><li>2 - Entrada de ledger eliminada</li><li>3 - Estado de entrada de ledger</li></ul> | Sí          | Los tipos de cambio de entrada válidos son 0, 1 y 2 para entradas de ledger del tipo `trust_lines`.                                                                                      |
-| deleted              | Indica si la entrada del ledger (línea de confianza) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede recuperarse                                                                                                                     | boolean      |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| closed_at            | Marca de tiempo en UTC cuando este ledger se cerró y confirmó en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                               | timestamp    |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| ledger_sequence      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto. | integer      |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| batch_id             | Representación en cadena del id de ejecución para un DAG dado en Airflow                                                                                                                                                                                    | string       |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| batch_run_date       | La fecha de inicio del intervalo de lote. Tomada junto con la fecha en batch_id, la fecha representa el intervalo de ledgers procesados                                                                                                                     | datetime     |                                                                                                                                                                          | Sí          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta.                    |
-| batch_insert_ts      | Marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos                                                                                                                                                                        | timestamp    |                                                                                                                                                                          | Sí          |                                                                                                                                                                                          |
-| sponsor              | La dirección de la cuenta que patrocina las reservas base para la línea de confianza                                                                                                                                                                        | string       |                                                                                                                                                                          | No          |                                                                                                                                                                                          |
-| asset_id             | Identificador único para asset_code, asset_issuer                                                                                                                                                                                                           | integer      |                                                                                                                                                                          | No          |                                                                                                                                                                                          |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.mdx
deleted file mode 100644
index 82a888bed1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/bronze/ttl.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: TTL
-sidebar_position: 80
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                      |
-| --------------------- | -------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | key_hash, closed_at                                                                                |
-| Campo(s) de partición | closed_at (partición MES)                                                                          |
-| Campo(s) agrupado(s)  | last_modified_ledger, key_hash                                                                     |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.ttl) |
-
-## Detalles de columnas
-
-| Nombre                | Descripción                                                                                                                            | Tipo de datos   | Valores del dominio | ¿Requerido? | Notas |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------- | ----------- | ----- |
-| key_hash              | Hash de clave del ledger usado para identificar datos de contrato caducando o entradas de ledger de código de contrato                 | cadena          |                     | Sí          |       |
-| live_until_ledger_seq | Secuencia del ledger hasta la cual el contrato o wasm permanecerá activo                                                               | entero          |                     | Sí          |       |
-| last_modified_ledger  | Número de secuencia del ledger cuando se modificó la entrada de ledger (este firmante único para la cuenta)                            | entero          |                     | Sí          |       |
-| ledger_entry_change   | Código que describe el tipo de cambio aplicado a la entrada del ledger                                                                 | entero          |                     | Sí          |       |
-| deleted               | Indica si la entrada del ledger (ID de balance) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede ser recuperada  | booleano        |                     | Sí          |       |
-| batch_id              | Representación en cadena del ID de ejecución para un DAG dado en Airflow                                                               | cadena          |                     | Sí          |       |
-| batch_run_date        | Fecha de inicio del intervalo por lote. Cuando se usa junto con la fecha en el batch_id, representa el intervalo de ledgers procesados | fecha y hora    |                     | Sí          |       |
-| batch_insert_ts       | Marca de tiempo UTC cuando un lote de registros fue insertado en la base de datos                                                      | marca de tiempo |                     | Sí          |       |
-| closed_at             | Marca de tiempo UNIX de la antigüedad del número de secuencia                                                                          | marca de tiempo |                     | Sí          |       |
-| ledger_sequence       | Número entero sin signo de 32 bits del ledger correspondiente a la antigüedad del número de secuencia                                  | entero          |                     | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/claimable-balances.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/claimable-balances.mdx
deleted file mode 100644
index 871f8627e0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/claimable-balances.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Saldos reclamables
-sidebar_position: 20
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                     |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | balance_id, closed_at                                                                                             |
-| Campo(s) de partición | batch_run_date (partición de MESE)                                                                                |
-| Campo(s) agrupado(s)  | asset_id, last_modified_ledger                                                                                    |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.claimable_balances) |
-
-## Detalles de la columna
-
-| Nombre                               | Descripción                                                                                                                                                                                                                                         | Tipo de dato    | Valores de dominio                                                                                                                                                                                                        | ¿Requerido? | Notas                                                                                                                                                                                                                 |
-| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| balance_id                           | Un identificador único para este saldo reclamable. El Balance id es una compilación de `Tipo de Balance` + `SHA-256 hash history_operation_id`                                                                                                      | cadena          |                                                                                                                                                                                                                           | Sí          | El Tipo de Balance está fijado en V0, `00000000`. Si hay un cambio de protocolo que impacte materialmente en la mecánica de los saldos reclamables, el tipo de balance se actualizaría a V1.                          |
-| reclamantes                          | La lista de entradas que son elegibles para reclamar el saldo y las condiciones que deben cumplirse para reclamar                                                                                                                                   | array[registro] |                                                                                                                                                                                                                           | Sí          | Se pueden especificar múltiples cuentas en el registro de reclamantes, incluyendo la cuenta del creador del saldo.                                                                                                    |
-| claimants.destination                | El id de la cuenta que puede reclamar el saldo                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| claimants.predicate                  | La condición que debe cumplirse para que el destino pueda reclamar el saldo. El predicado puede incluir reglas lógicas utilizando AND, OR y NOT.                                                                                                    | array[registro] |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| claimants.predicate.unconditional    | Si es verdadero, significa que esta cláusula de la condición siempre se cumple                                                                                                                                                                      | booleano        |                                                                                                                                                                                                                           | No          | Cuando el predicado es solo incondicional = verdadero, significa que el saldo se puede reclamar en cualquier condición                                                                                                |
-| claimants.predicate.abs_before       | Fecha límite para cuando se debe reclamar el saldo. Si se reclama un saldo antes de la fecha, entonces se satisface la cláusula de la condición.                                                                                                    | cadena          |                                                                                                                                                                                                                           | No          |                                                                                                                                                                                                                       |
-| claimants.predicate.rel_before       | Una fecha límite relativa para cuando el saldo reclamable puede ser reclamado. El valor representa el número de segundos desde el tiempo de cierre del ledger que creó el saldo reclamable                                                          | entero          |                                                                                                                                                                                                                           | No          | Esta condición es útil al crear un tiempo límite basado en condiciones de creación. Si el creador quería un saldo que solo pueda ser reclamado una semana después de su creación, esta condición cumpliría esa regla. |
-| claimants.predicate.abs_before_epoch | Un valor de época UNIX en segundos que representa la misma fecha límite que abs_before.                                                                                                                                                             | entero          |                                                                                                                                                                                                                           | No          |                                                                                                                                                                                                                       |
-| tipo_de_activo                       | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                        | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                               | Sí          |                                                                                                                                                                                                                       |
-| código_del_activo                    | La representación del código de 4 o 12 caracteres del activo en la red                                                                                                                                                                              | cadena          |                                                                                                                                                                                                                           | No          |                                                                                                                                                                                                                       |
-| emisor_del_activo                    | La dirección de la cuenta que creó el activo                                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                                           | No          |                                                                                                                                                                                                                       |
-| cantidad_del_activo                  | La cantidad del activo que puede ser reclamado                                                                                                                                                                                                      | flotante        |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| patrocinador                         | La dirección de cuenta del patrocinador que está pagando las reservas para este saldo reclamable                                                                                                                                                    | cadena          |                                                                                                                                                                                                                           | No          | Los patrocinadores de los saldos reclamables son los creadores del saldo.                                                                                                                                             |
-| flags                                | Denota la habilitación y desactivación de ciertos privilegios de emisor de saldo                                                                                                                                                                    | entero          | <ul><li>0 - Ninguno, Predeterminado</li><li>1 - Autenticación de Clawback Habilitada</li></ul>                                                                                                                            | Sí          | Las flags son establecidas por las cuentas de saldo reclamable para un activo. Cuando las cuentas de usuario reclaman un saldo, las banderas aplicadas al activo provienen de esta cuenta                             |
-| último_libro_modificado              | El número de secuencia del libro mayor cuando la entrada del libro mayor (este firmante único para la cuenta) fue modificada. Las eliminaciones no cuentan como una modificación y reportarán el número de secuencia de la modificación anterior    | entero          |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| cambio_entrada_libro                 | Código que describe el tipo de cambio de la entrada del libro mayor que fue aplicado a la entrada.                                                                                                                                                  | entero          | <ul><li>0 - Entrada del libro mayor creada</li><li>1 - Entrada del libro mayor actualizada</li><li>2 - Entrada del libro mayor eliminada</li><li>3 - Estado de la entrada del libro mayor (valor de la entrada)</li></ul> | Sí          | Los tipos de cambio de entrada válidos son 0 y 2 para las entradas del libro mayor de tipo `claimable_balances`. Una vez creada, una entrada no puede ser actualizada.                                                |
-| eliminado                            | Indica si la entrada del libro mayor (id de saldo) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede ser recuperada.                                                                                                           | booleano        |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| cerrado_en                           | Marca de tiempo en UTC cuando este libro se cerró y se comprometió a la red. Se espera que los libros se cierren aproximadamente cada 5 segundos                                                                                                    | marca_de_tiempo |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| secuencia_libro                      | El número de secuencia de este libro. Representa el orden del libro dentro de la blockchain Stellar. Cada libro tiene un número de secuencia único que incrementa con cada nuevo libro, asegurando que los libros se procesen en el orden correcto. | entero          |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| identificador_batch                  | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "programada\_\_\<fecha_fin_batch>-\<alias_dag>". Los id de batch son únicos para el batch y ayudan con las capacidades de monitoreo y reejecución        | cadena          |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| fecha_ejecucion_batch                | La fecha de inicio para el intervalo de batch. Cuando se toma junto con la fecha en el id de batch, la fecha representa el intervalo de libros procesados. La fecha de ejecución del batch se puede ver como un proxy de cerrado_en para un libro.  | fecha_hora      |                                                                                                                                                                                                                           | Sí          | La tabla está particionada por fecha_ejecucion_batch. Se recomienda incluir siempre la fecha_ejecucion_batch en el filtro si es posible para ayudar a reducir el costo de la consulta.                                |
-| timestamp_insert_batch               | La marca de tiempo en UTC cuando un batch de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un backfill                                                   | marca_de_tiempo |                                                                                                                                                                                                                           | Sí          |                                                                                                                                                                                                                       |
-| id_activo                            | Identificador único para el código del activo, emisor del activo                                                                                                                                                                                    | entero          |                                                                                                                                                                                                                           | No          |                                                                                                                                                                                                                       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/contract-code.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/contract-code.mdx
deleted file mode 100644
index 96703077b1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/contract-code.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Código del contrato
-sidebar_position: 30
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                |
-| --------------------- | ------------------------------------------------------------------------------------------------------------ |
-| Clave(s) natural(es)  | contract_code_hash, closed_at                                                                                |
-| Campo(s) de partición | closed_at (partición por MES)                                                                                |
-| Campo(s) agrupado(s)  | last_modified_ledger, contract_code_hash                                                                     |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.contract_code) |
-
-## Detalles de la columna
-
-| Nombre                      | Descripción                                                                                                                                                                                                                                                    | Tipo de dato    | Valores de dominio | ¿Requerido? | Notas |
-| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------ | ----------- | ----- |
-| contract_code_hash          | Hash del código de contrato Soroban                                                                                                                                                                                                                            | cadena          |                    | Sí          |       |
-| contract_code_ext_v         | Versión de la extensión del código del contrato                                                                                                                                                                                                                | entero          |                    |             |       |
-| last_modified_ledger        | El número de secuencia del ledger cuando se modificó la entrada del ledger (este firmante único para la cuenta). Las eliminaciones no cuentan como una modificación y reportarán el número de secuencia de modificación anterior                               | entero          |                    | Sí          |       |
-| cambio_de_entrada_en_ledger | Código que describe el tipo de cambio de entrada en el ledger que se aplicó a la entrada en el ledger.                                                                                                                                                         | entero          |                    | Sí          |       |
-| eliminado                   | Indica si la entrada del ledger (id de saldo) ha sido eliminada o no. Una vez que se elimina una entrada, no se puede recuperar.                                                                                                                               | booleano        |                    | Sí          |       |
-| batch_id                    | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los ids de batch son únicos para el batch y ayudan con las capacidades de monitoreo y reejecución                    | cadena          |                    | Sí          |       |
-| batch_run_date              | La fecha de inicio del intervalo del batch. Junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger.                                  | fecha y hora    |                    | Sí          |       |
-| batch_insert_ts             | La marca de tiempo en UTC cuando se insertó un batch de registros en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un reabastecimiento                                                         | marca de tiempo |                    | Sí          |       |
-| closed_at                   | Marca de tiempo en UTC cuando este ledger se cerró y se comprometió a la red. Se espera que los ledgers se cierren ~cada 5 segundos                                                                                                                            | marca de tiempo |                    | Sí          |       |
-| ledger_sequence             | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que se incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto. | entero          |                    | Sí          |       |
-| ledger_key_hash             | Hash de clave del ledger usado para identificar datos de contrato que están caducando o entradas de ledger de código de contrato                                                                                                                               | cadena          |                    | Sí          |       |
-| n_instructions              | Número de instrucciones en el código del contrato                                                                                                                                                                                                              | entero          |                    |             |       |
-| n_functions                 | Número de funciones en el código del contrato                                                                                                                                                                                                                  | entero          |                    |             |       |
-| n_globals                   | Número de variables globales en el código del contrato                                                                                                                                                                                                         | entero          |                    |             |       |
-| n_table_entries             | Número de entradas de tabla en el código del contrato                                                                                                                                                                                                          | entero          |                    |             |       |
-| n_types                     | Número de tipos en el código del contrato                                                                                                                                                                                                                      | entero          |                    |             |       |
-| n_data_segments             | Número de segmentos de datos en el código del contrato                                                                                                                                                                                                         | entero          |                    |             |       |
-| n_elem_segments             | Número de segmentos de elementos en el código del contrato                                                                                                                                                                                                     | entero          |                    |             |       |
-| n_imports                   | Número de imports en el código del contrato                                                                                                                                                                                                                    | entero          |                    |             |       |
-| n_exports                   | Número de exports en el código del contrato                                                                                                                                                                                                                    | entero          |                    |             |       |
-| n_data_segment_bytes        | Número de bytes de segmentos de datos en el código del contrato                                                                                                                                                                                                | entero          |                    |             |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/contract-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/contract-data.mdx
deleted file mode 100644
index 3fc99531ab..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/contract-data.mdx
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Datos del contrato
-sidebar_position: 40
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                |
-| --------------------- | ------------------------------------------------------------------------------------------------------------ |
-| Clave(s) natural(es)  | ledger_key_hash, closed_at                                                                                   |
-| Campo(s) de partición | closed_at (partición por MES)                                                                                |
-| Campo(s) agrupado(s)  | last_modified_ledger, contract_id                                                                            |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.contract_data) |
-
-## Detalles de la columna
-
-| Nombre                           | Descripción                                                                                                                                                                                                                                                                                          | Tipo de dato    | Valores de dominio | ¿Requerido? | Notas |
-| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------ | ----------- | ----- |
-| contract_id                      | ID de contrato de Soroban                                                                                                                                                                                                                                                                            | cadena          |                    | Sí          |       |
-| tipo_de_clave_del_contrato       | Tipo de clave del contrato que es un ScVal que puede tener los siguientes valores                                                                                                                                                                                                                    | cadena          |                    |             |       |
-| durabilidad_del_contrato         | El contrato puede ser temporal o persistente                                                                                                                                                                                                                                                         | cadena          |                    |             |       |
-| código_de_activo                 | El código de representación de 4 o 12 caracteres del activo en la red.                                                                                                                                                                                                                               | cadena          |                    |             |       |
-| emisor_del_activo                | La dirección de cuenta del emisor original del activo que creó el activo.                                                                                                                                                                                                                            | cadena          |                    |             |       |
-| tipo_de_activo                   | El identificador del tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                           | cadena          |                    |             |       |
-| titular_del_balance              | La dirección/cuenta que sostiene el balance del activo en los datos del contrato                                                                                                                                                                                                                     | cadena          |                    |             |       |
-| balance                          | El número de unidades de XLM sostenidas por la cuenta                                                                                                                                                                                                                                                | cadena          |                    |             |       |
-| last_modified_ledger             | El número de secuencia del libro mayor cuando se modificó la entrada del libro mayor (este firmante único para la cuenta). Las eliminaciones no cuentan como una modificación y mostrarán el número de secuencia de modificación anterior                                                            | número entero   |                    | Sí          |       |
-| cambio_de_entrada_en_libro_mayor | Código que describe el tipo de cambio de entrada en el libro mayor que se aplicó a la entrada del libro mayor.                                                                                                                                                                                       | número entero   |                    | Sí          |       |
-| eliminado                        | Indica si la entrada en el libro mayor (id de balance) ha sido eliminada o no. Una vez que se elimina una entrada, no se puede recuperar.                                                                                                                                                            | booleano        |                    | Sí          |       |
-| batch_id                         | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los ids de lote son únicos para el lote y ayudan con las capacidades de monitoreo y reejecución                                                            | cadena          |                    | Sí          |       |
-| batch_run_date                   | La fecha de inicio para el intervalo de lotes. Cuando se toma con la fecha en el batch_id, la fecha representa el intervalo de libros mayores procesados. La fecha de ejecución del lote se puede ver como un proxy de closed_at para un libro mayor.                                                | fecha y hora    |                    | Sí          |       |
-| batch_insert_ts                  | La marca de tiempo en UTC cuando se insertó un lote de registros en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un backfill                                                                                                         | marca de tiempo |                    | Sí          |       |
-| closed_at                        | Marca de tiempo en UTC cuando este libro mayor se cerró y se comprometió a la red. Se espera que los libros mayores se cierren aproximadamente cada 5 segundos                                                                                                                                       | marca de tiempo |                    | Sí          |       |
-| secuencia_del_libro_mayor        | El número de secuencia de este libro mayor. Representa el orden del libro mayor dentro de la blockchain de Stellar. Cada libro mayor tiene un número de secuencia único que se incrementa con cada nuevo libro mayor, asegurando que los libros mayores se procesen en el orden correcto.            | número entero   |                    | Sí          |       |
-| ledger_key_hash                  | Hash de clave del libro mayor utilizado para identificar datos del contrato que están caducando o entradas en el libro mayor del código de contrato                                                                                                                                                  | cadena          |                    | Sí          |       |
-| clave                            | La clave codificada utilizada para identificar un elemento específico de datos del contrato. La clave codificada tiene dos componentes (tipo y valor) donde el tipo describe el tipo de dato y el valor describe el valor codificado del tipo de dato para los datos del contrato                    | json            |                    |             |       |
-| key_decoded                      | La versión legible por humanos o decodificada de la clave. Esto proporciona un formato comprensible de la clave, facilitando su interpretación y uso en el análisis                                                                                                                                  | json            |                    |             |       |
-| val                              | El valor codificado asociado con la clave en los datos del contrato. El valor codificado tiene dos componentes (tipo y valor) donde el tipo describe el tipo de dato y el valor describe el valor codificado del tipo de dato para los datos del contrato                                            | json            |                    |             |       |
-| val_decoded                      | La versión legible por humanos o decodificada del valor. Esto proporciona una representación clara y comprensible del valor, facilitando su interpretación y uso en el análisis                                                                                                                      | json            |                    |             |       |
-| contract_data_xdr                | La codificación XDR (Representación de Datos Externa) de los datos del contrato. XDR es un formato estándar utilizado para serializar y deserializar datos, asegurando la interoperabilidad entre diferentes sistemas. Este campo contiene los datos del contrato en formato XDR crudo y serializado | cadena          |                    |             |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/enriched-history-operations.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/enriched-history-operations.mdx
deleted file mode 100644
index 676a0b156c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/enriched-history-operations.mdx
+++ /dev/null
@@ -1,103 +0,0 @@
----
-title: Operaciones de Historia Enriquecida
-sidebar_position: 150
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                             |
-| --------------------- | --------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | op_id                                                                                                     |
-| Campo(s) de Partición | closed_at (partición MENSUAL)                                                                             |
-| Campo(s) agrupado(s)  | ledger_sequence, transaction_id, op_account_id, type                                                      |
-| Documentación         | [dbt_docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.enriched_history_operations) |
-
-## Detalles de la Columna
-
-| Nombre                          | Descripción                                                                                                                                                                                                                                                                                                         | Tipo de Dato    | Valores de Dominio                                                                                                    | ¿Requerido? | Tabla de Origen       | Notas                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | --------------------------------------------------------------------------------------------------------------------- | ----------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| cuenta                          | La nueva dirección de cuenta resultante que se crea y se financia (operación de crear) La dirección de cuenta que se está eliminando y fusionando en otra cuenta (operación de fusión)                                                                                                                              | cadena          |                                                                                                                       |             | history_operations    | Parte del objeto original `details` en la tabla history_operations                                                                                                                                                                                                                                                                                                                                                                  |
-| cantidad                        | Representación en punto flotante de la cantidad de un activo enviado/ofrecido/etcétera                                                                                                                                                                                                                              | flotante        |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| asset_code                      | El código de 4 o 12 caracteres que representa el activo en la red                                                                                                                                                                                                                                                   | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| asset_issuer                    | La dirección de la cuenta del emisor del activo original que creó el activo                                                                                                                                                                                                                                         | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| asset_type                      | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                        | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                           |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| autorizar                       | Indica si la línea de confianza está autorizada. 0 significa que la cuenta no está autorizada para transaccionar con el activo de ninguna manera. 1 si la cuenta está autorizada para transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones. | booleano        |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| balance_id                      | El identificador único del saldo reclamable. El id está compuesto por código de tipo de 8 caracteres + hash SHA-256 del id de la operación de historia que creó el saldo. El id del saldo puede ser relacionado con la tabla `claimable_balances` para obtener más detalles sobre el saldo                          | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| buying_asset_code               | El código de 4 o 12 caracteres que representa el activo que se compra o se ofrece comprar en una operación                                                                                                                                                                                                          | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| buying_asset_issuer             | La dirección de la cuenta del emisor del activo original que creó el activo comprado o ofrecido para comprar                                                                                                                                                                                                        | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| buying_asset_type               | El identificador para el tipo de código de activo, puede ser un alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                     | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                           |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| de                              | La dirección de la cuenta desde la cual se origina el pago (la cuenta de envío)                                                                                                                                                                                                                                     | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| financiador                     | Cuando se crea una nueva cuenta, una dirección de cuenta "financia" la nueva cuenta                                                                                                                                                                                                                                 | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| high_threshold                  | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                                                     | entero          |                                                                                                                       |             | history_operations    | Cada operación cae bajo una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito (esta es una medida de seguridad) Seguridad Baja: Permitir Confianza, Establecer Banderas de Línea de Confianza, Aumentar Secuencia y Reivindicar Saldo Reclamable Seguridad Media: Todo lo Demás Seguridad Alta: Fusión de Cuenta, Establecer Opciones     |
-| home_domain                     | El dominio principal utilizado para el descubrimiento del archivo stellar.toml                                                                                                                                                                                                                                      | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| inflation_dest                  | La dirección de cuenta que especifica a dónde enviar los fondos de inflación. El concepto de inflación en la red ha sido descontinuado                                                                                                                                                                              | cadena          |                                                                                                                       |             | history_operations    | La inflación fue retirada de la red en 2019.                                                                                                                                                                                                                                                                                                                                                                                        |
-| en                              | La dirección de la cuenta que recibe los lumens de la cuenta eliminada. Esta es la cuenta en la que se fusionará la cuenta que se pretende eliminar                                                                                                                                                                 | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| límite                          | La cantidad límite superior de un activo que una cuenta puede contener                                                                                                                                                                                                                                              | flotante        |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| low_threshold                   | La suma del peso de todas las firmas que firman una transacción para la operación de umbral bajo. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                                                     | entero          |                                                                                                                       |             | history_operations    | Cada operación cae bajo una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito (esta es una medida de seguridad) Seguridad Baja: Permitir Confianza, Establecer Banderas de Línea de Confianza, Aumentar Secuencia y Reivindicar Saldo Reclamable Seguridad Media: Todo lo Demás Seguridad Alta: Fusión de Cuenta, Establecer Opciones     |
-| master_key_weight               | La clave privada de una cuenta se llama la clave maestra. Para firmar transacciones, el titular de la cuenta puede especificar un peso para la clave maestra, lo cual contribuye a la validación de los umbrales al procesar una transacción                                                                        | entero          | Enteros de 1 a 255                                                                                                    |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| med_threshold                   | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                                                    | entero          |                                                                                                                       |             | history_operations    | Cada operación cae bajo una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito (esta es una medida de seguridad) Seguridad Baja: Permitir Confianza, Establecer Banderas de Línea de Confianza, Aumentar Secuencia y Reivindicar Saldo Reclamable Seguridad Media: Todo lo Demás Seguridad Alta: Fusión de Cuenta, Establecer Opciones     |
-| nombre                          | La operación de gestionar datos permite a una cuenta escribir y almacenar datos directamente en el ledger en un formato de clave-valor. El nombre es la clave para una entrada de datos.                                                                                                                            | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| offer_id                        | El id único para la oferta. Este id puede unirse con la tabla `offers`                                                                                                                                                                                                                                              | entero          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| ruta                            | Los pagos por ruta maximizan la mejor ruta de cambio cuando se envía dinero de un activo a otro. Los activos intermedios por los que pasa esta ruta se informarán en el registro. Esta función es especialmente útil cuando el mercado entre el par de activos original es ilíquido                                 | array[record]   |                                                                                                                       |             | history_operations    | Se permiten hasta 6 rutas para un solo pago. Ejemplo: enviar EUR -> MXN podría parecerse a EUR -> BTC -> CNY -> XLM -> MXN para maximizar la mejor ruta de cambio. Los pagos son atómicos, por lo que si un intercambio en medio de un pago de ruta falla, el pago completo fallará, lo que significa que el usuario conservará sus fondos originales. No se quedarán atrapados con un activo intermedio en caso de fallo del pago. |
-| precio                          | La relación del activo vendido al activo comprado. Este es un número que representa cuántas unidades de un activo vendido se necesita para obtener 1 unidad de un activo comprado                                                                                                                                   | flotante        |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| d                               | Representación precisa del precio de compra y venta de un intercambio. El `d` es el denominador. Cuando se toma con n/d obtendrás el precio                                                                                                                                                                         | entero          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| n                               | Representación precisa de los precios de compra y venta de un intercambio. El `n` es el numerador. Cuando se toma con n/d obtendrás el precio.                                                                                                                                                                      | entero          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| selling_asset_code              | El código de 4 o 12 caracteres que representa el activo que se vende o se ofrece vender en un intercambio                                                                                                                                                                                                           | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| selling_asset_issuer            | La dirección de la cuenta del emisor del activo original que creó el activo vendido o ofrecido para vender                                                                                                                                                                                                          | cadena          |                                                                                                                       |             | history_operations    |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| selling_asset_type              | El identificador para el tipo de código de activo, puede ser un alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                     | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                           |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| establecer_banderas             | Array de valores numéricos de las banderas establecidas para una línea de confianza dada en la operación                                                                                                                                                                                                            | array[entero]   | <ul><li>1 - Autenticación Requerida</li><li>2 - Autenticación Revocable</li><li>4 - Autenticación Inmutable</li></ul> |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| establecer_banderas_s           | Array de valores de cadena de las banderas establecidas para una línea de confianza dada en la operación                                                                                                                                                                                                            | array[cadena]   | <ul><li>Autenticación Requerida</li><li>Autenticación Revocable</li><li>Autenticación Inmutable</li></ul>             |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| clave_firmante                  | La dirección del firmante que ya no está patrocinado                                                                                                                                                                                                                                                                | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| peso_firmante                   | El peso del nuevo firmante. Para transacciones, múltiples cuentas pueden firmar una transacción de una cuenta fuente. Este peso contribuye a calcular si la transacción supera el peso de umbral especificado para completar la transacción                                                                         | entero          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| monto_origen                    | El monto de origen enviado designado en el activo de origen                                                                                                                                                                                                                                                         | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| código_activo_origen            | El código de 4 o 12 caracteres que representa el activo que se envió originalmente                                                                                                                                                                                                                                  | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| emisor_activo_origen            | La dirección de la cuenta del emisor de activo original que creó el activo enviado                                                                                                                                                                                                                                  | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| tipo_activo_origen              | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                        | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                           |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| máx_origen                      | El monto máximo que se puede enviar, designado en el activo de origen                                                                                                                                                                                                                                               | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| saldo_inicio                    | La cantidad de XLM a enviar a la cuenta creada recientemente. El saldo inicial de la cuenta debe exceder el saldo mínimo necesario para mantener una cuenta en la red Stellar                                                                                                                                       | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| a                               | La dirección de la cuenta que recibe los fondos del pago                                                                                                                                                                                                                                                            | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| fideicomisario                  | La dirección de la cuenta emisora (solo presente para tipos de activos de `crédito`)                                                                                                                                                                                                                                | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| fideicomitente                  | La dirección de la cuenta de confianza, o la cuenta que está siendo autorizada o no autorizada                                                                                                                                                                                                                      | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| activo_línea_confianza          | El activo de la línea de confianza que ya no está patrocinado                                                                                                                                                                                                                                                       | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| valor                           | La operación de gestionar datos permite a una cuenta escribir y almacenar datos directamente en el ledger en un formato clave-valor. El valor es el valor de una clave para una entrada de datos.                                                                                                                   | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| eliminar_banderas               | Array de valores numéricos de las banderas eliminadas para una línea de confianza dada en la operación. Si la bandera fue originalmente establecida, esto eliminará la bandera                                                                                                                                      | array[entero]   | <ul><li>1 - Autenticación Requerida</li><li>2 - Autenticación Revocable</li><li>4 - Autenticación Inmutable</li></ul> |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| eliminar_banderas_s             | Array de valores de cadena de las banderas eliminadas para una línea de confianza dada en la operación. Si la bandera fue originalmente establecida, esto eliminará la bandera                                                                                                                                      | array[cadena]   | <ul><li>Autenticación Requerida</li><li>Autenticación Revocable</li><li>Autenticación Inmutable</li></ul>             |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| mínimo_destino                  | La cantidad mínima a recibir, designada en el activo de destino esperado                                                                                                                                                                                                                                            | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| incrementar_a                   | El nuevo valor deseado del número de secuencia de la cuenta de origen                                                                                                                                                                                                                                               | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| patrocinador                    | La dirección de la cuenta de otra cuenta que mantiene el saldo mínimo en XLM para que la cuenta de origen complete operaciones                                                                                                                                                                                      | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| id_patrocinado                  | La dirección de la cuenta de la cuenta que será patrocinada                                                                                                                                                                                                                                                         | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| comenzar_patrocinar             | La dirección de la cuenta de la cuenta que inició el patrocinio                                                                                                                                                                                                                                                     | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| autorizar_para_mantener_pasivos | Indica si la línea de confianza está autorizada. 0 si la cuenta no está autorizada para transaccionar con el activo de ninguna manera. 1 si la cuenta está autorizada para transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones.            | booleano        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| recuperación_habilitada         | Indica si el activo puede ser recuperado por el emisor del activo                                                                                                                                                                                                                                                   | booleano        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| id_fondos_de_liquidez           | Identificador único para un fondo de liquidez                                                                                                                                                                                                                                                                       | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_un_tipo_de_activo      | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                        | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                           |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_un_codigo_de_activo    | La representación del código de 4 o 12 caracteres del activo de uno de los dos pares de activos en un fondo de liquidez                                                                                                                                                                                             | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_un_emisor_de_activo    | La dirección de la cuenta del emisor de activo original que creó uno de los dos pares de activos en el fondo de liquidez                                                                                                                                                                                            | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_un_monto_máximo        | La cantidad máxima de reserva a que se puede depositar en el fondo.                                                                                                                                                                                                                                                 | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_un_monto_de_deposito   | La cantidad de reserva a que terminó siendo depositada en el fondo                                                                                                                                                                                                                                                  | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_b_tipo_de_activo       | El identificador para tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                           | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                           |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_b_codigo_de_activo     | La representación del código de 4 o 12 caracteres del activo de uno de los dos pares de activos en un fondo de liquidez                                                                                                                                                                                             | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_b_emisor_de_activo     | La dirección de la cuenta del emisor de activo original que creó uno de los dos pares de activos en el fondo de liquidez                                                                                                                                                                                            | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_b_monto_máximo         | La cantidad máxima de reserva b que se puede depositar en el fondo.                                                                                                                                                                                                                                                 | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| reservar_b_monto_de_deposito    | La cantidad de reserva b que terminó siendo depositada en el fondo.                                                                                                                                                                                                                                                 | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| precio_mínimo                   | El valor en punto flotante que indica la tasa de cambio mínima para esta operación de depósito. Reportado como Reserva A / Reserva B                                                                                                                                                                                | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| precio_mínimo_r                 | Una representación fraccionaria de los precios de los dos activos en un fondo. El n es el numerador (valor de activo a) y el d es el denominador (valor de activo b)                                                                                                                                                | array[registro] |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| precio_máximo                   | El valor en punto flotante que indica la tasa de cambio máxima para esta operación de depósito. Reportado como Reserva A / Reserva B                                                                                                                                                                                | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| max_price_r                     | Una representación fraccionaria de los precios de los dos activos en un grupo. El n es el numerador (valor del activo a) y el d es el denominador (valor del activo b)                                                                                                                                              | array[registro] |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| acciones_recibidas              | Un número de punto flotante que representa el número de acciones del grupo recibidas por este depósito. Una acción del grupo es una recopilación de las reservas de los activos a y b. No es posible poseer solo el activo a o el activo b en un grupo                                                              | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| monto_minimo_reserva_a          | La cantidad mínima de reserva a que se puede retirar del grupo.                                                                                                                                                                                                                                                     | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| monto_minimo_reserva_b          | La cantidad mínima de reserva b que se puede retirar del grupo.                                                                                                                                                                                                                                                     | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| acciones                        | El número de acciones retiradas del grupo. No es posible retirar solo el activo a o el activo b, se debe retirar un valor equivalente del grupo                                                                                                                                                                     | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| monto_retiro_reserva_a          | La cantidad de reserva a que terminó realmente retirada del grupo.                                                                                                                                                                                                                                                  | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| monto_retiro_reserva_b          | La cantidad de reserva b que terminó realmente retirada del grupo.                                                                                                                                                                                                                                                  | flotante        |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| pedido_aplicacion_op            | El número de orden en el conjunto de transacciones en el que se ejecuta la operación. El pedido de aplicación y el id de transacción son una clave natural que comprende el id (operación)                                                                                                                          | entero          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| id_op                           | Identificador único para una operación                                                                                                                                                                                                                                                                              | entero          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| cuenta_salida_op                | La dirección de cuenta que origina la operación                                                                                                                                                                                                                                                                     | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| cuenta_salida_op_muxed          | Si una cuenta está multiplexada (muxed), la dirección de cuenta virtual que origina la operación                                                                                                                                                                                                                    | cadena          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| id_transaccion                  | El identificador de la transacción en la que se ejecutó la operación. Puede haber hasta 100 operaciones en una transacción dada                                                                                                                                                                                     | entero          |                                                                                                                       |             | historial_operaciones |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| tipo                            | El número que indica qué tipo de operación se está ejecutando                                                                                                                                                                                                                                                       | entero          |                                                                                                                       |             |                       |                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/README.mdx
deleted file mode 100644
index b0117324e3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Gold 🥇
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Análisis seleccionados con tablas agregadas amigables. Estas tablas están compuestas por varias agregaciones de datos de Stellar, como el TVL total de la red.
-
-## Cuándo usarlo
-
-Estas tablas son ideales para obtener métricas e información preagregadas de la red Stellar.
-
-Un ejemplo es la tabla `tvl_agg` que contiene el TVL diario de la red Stellar, evitando la necesidad de agregar el TVL de cada cuenta individual, operación, pool de liquidez, etc.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.mdx
deleted file mode 100644
index 5e377cd107..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/asset-balances-daily-agg.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Saldos de Activos Agregados Diariamente
-sidebar_position: 80
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                           |
-| --------------------- | ------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | día, tipo_de_activo, código_de_activo, emisor_de_activo                                                 |
-| Campo(s) de Partición | día (partición DIA)                                                                                     |
-| Campo(s) Clúster      | No Aplica                                                                                               |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.asset_balances__daily_agg) |
-
-## Detalles de Columnas
-
-| Nombre                                     | Descripción                                                                                                                             | Tipo de Datos | Valores del Dominio | ¿Requerido? | Notas                                                                                                                                     |
-| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| día                                        | Fecha hasta la cual se agregan todas las métricas.                                                                                      | FECHA         |                     | Sí          |                                                                                                                                           |
-| tipo_de_activo                             | El identificador del tipo de código de activo, puede ser alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red, XLM. | CADENA        |                     | Sí          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y se mostrará con un tipo de activo 'nativo' |
-| código_de_activo                           | La representación en código de 4 o 12 caracteres del activo en la red.                                                                  | CADENA        |                     | Sí          | Los códigos de activo no garantizan unicidad. La combinación de código de activo, emisor y tipo representa un activo único.               |
-| emisor_de_activo                           | La dirección de cuenta del emisor original del activo que creó el activo.                                                               | CADENA        |                     | Sí          |                                                                                                                                           |
-| liquidity_pool_balance                     | La suma de los saldos en todos los Fondos de Liquidez para un activo dado.                                                              | FLOTANTE      |                     | Sí          |                                                                                                                                           |
-| offer_balance                              | La suma de saldos en todas las obligaciones de venta (solo SDEX) para un activo dado.                                                   | FLOTANTE      |                     | Sí          |                                                                                                                                           |
-| trustline_balance                          | La suma del saldo de la trustline para un activo dado.                                                                                  | FLOTANTE      |                     | Sí          |                                                                                                                                           |
-| total_accounts_with_liquidity_pool_balance | El recuento de titulares con saldo positivo en Fondos de Liquidez para un activo dado.                                                  | ENTERO        |                     | Sí          |                                                                                                                                           |
-| total_accounts_with_offer_balance          | El recuento de titulares con saldo positivo de oferta para un activo dado.                                                              | ENTERO        |                     | Sí          |                                                                                                                                           |
-| total_accounts_with_trustline_balance      | El recuento de titulares con saldo positivo en trustline para un activo dado.                                                           | ENTERO        |                     | Sí          |                                                                                                                                           |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/fee-stats-agg.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/fee-stats-agg.mdx
deleted file mode 100644
index ea2d8a2e84..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/fee-stats-agg.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Estadísticas de Tarifas Agregadas
-sidebar_position: 80
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                               |
-| --------------------- | ------------------------------------------------------------------------------------------- |
-| Clave Natural(s)      | day_agg                                                                                     |
-| Campo(s) de Partición | day_agg (partición MENSUAL)                                                                 |
-| Campo(s) Agrupado(s)  | N/A                                                                                         |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.fee_stats_agg) |
-
-## Detalles de Columnas
-
-| Nombre              | Descripción                                                                                                            | Tipo de Datos | Valores del Dominio | ¿Requerido? | Notas |
-| ------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------- | ------------------- | ----------- | ----- |
-| day_agg             | Día en que se agregaron las estadísticas de tarifas.                                                                   | DATE          |                     | Sí          |       |
-| fee_charged_p10     | Tarifa cobrada en el percentil 10 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p20     | Tarifa cobrada en el percentil 20 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p30     | Tarifa cobrada en el percentil 30 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p40     | Tarifa cobrada en el percentil 40 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p50     | Tarifa cobrada en el percentil 50 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p60     | Tarifa cobrada en el percentil 60 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p70     | Tarifa cobrada en el percentil 70 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p80     | Tarifa cobrada en el percentil 80 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p90     | Tarifa cobrada en el percentil 90 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p95     | Tarifa cobrada en el percentil 95 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_p99     | Tarifa cobrada en el percentil 99 durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_max     | Valor máximo de la tarifa cobrada durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_min     | Valor mínimo de la tarifa cobrada durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| fee_charged_mode    | Moda de la tarifa cobrada durante el día.                                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p10         | Percentil 10 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p20         | Percentil 20 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p30         | Percentil 30 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p40         | Percentil 40 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p50         | Percentil 50 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p60         | Percentil 60 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p70         | Percentil 70 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p80         | Percentil 80 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p90         | Percentil 90 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p95         | Percentil 95 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_p99         | Percentil 99 de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_max         | Máxima tarifa ofertada durante el día.                                                                                 | FLOAT         |                     | Sí          |       |
-| max_fee_min         | Valor mínimo de la máxima tarifa ofertada durante el día.                                                              | FLOAT         |                     | Sí          |       |
-| max_fee_mode        | Moda de la máxima tarifa ofertada durante el día.                                                                      | FLOAT         |                     | Sí          |       |
-| min_ledger_sequence | Secuencia del primer ledger procesado del día agregado.                                                                | INTEGER       |                     | Sí          |       |
-| max_ledger_sequence | Secuencia del último ledger procesado del día agregado.                                                                | INTEGER       |                     | Sí          |       |
-| total_ledgers       | Cantidad total de ledgers cerrados en la red Stellar.                                                                  | INTEGER       |                     | Sí          |       |
-| surge_price_pct     | Porcentaje de ledgers que experimentaron un aumento de precio en comparación con el total de ledgers cerrados ese día. | FLOAT         |                     | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.mdx
deleted file mode 100644
index f722720472..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/trade-agg.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Agregación de Comercio
-sidebar_position: 80
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                           |
-| --------------------- | --------------------------------------------------------------------------------------- |
-| Clave Natural (s)     | day_agg                                                                                 |
-| Campo(s) de partición | day_agg (partición MES)                                                                 |
-| Campo(s) agrupado(s)  | asset_a, asset_b                                                                        |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.trade_agg) |
-
-## Detalles de la Columna
-
-| Nombre                 | Descripción                                                                                                                                                                                                                                                        | Tipo de Datos | Valores de Dominio | ¿Requerido? | Notas |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------- | ------------------ | ----------- | ----- |
-| day_agg                | Fecha desde la cual se agregan todas las métricas. En la tabla de Agregaciones de Comercio, day_agg representa el día en que se construyeron las agregaciones diarias.                                                                                             | FECHA         |                    | Sí          |       |
-| asset_a_type           | El identificador para el tipo de código de activo usado para el activo vendido dentro del comercio. Notas: XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y, en cambio, se mostrará con un tipo de activo 'native'.  | CADENA        |                    | Sí          |       |
-| asset_a_code           | El código de 4 o 12 caracteres del activo vendido dentro de un comercio. Notas: Los códigos de activos no garantizan unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto.                                                    | CADENA        |                    | No          |       |
-| asset_a_issuer         | La dirección de cuenta del emisor original del activo vendido dentro de un comercio.                                                                                                                                                                               | CADENA        |                    | No          |       |
-| asset_a                | ID hash para el selling_asset.                                                                                                                                                                                                                                     | ENTERO        |                    | Sí          |       |
-| asset_b_type           | El identificador para el tipo de código de activo usado para el activo comprado dentro del comercio. Notas: XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y, en cambio, se mostrará con un tipo de activo 'native'. | CADENA        |                    | Sí          |       |
-| asset_b_code           | El código de 4 o 12 caracteres del activo comprado dentro de un comercio. Notas: Los códigos de activos no garantizan unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto.                                                   | CADENA        |                    | No          |       |
-| asset_b_issuer         | La dirección de cuenta del emisor original del activo comprado dentro de un comercio.                                                                                                                                                                              | CADENA        |                    | No          |       |
-| asset_b                | ID hash para el buying_asset.                                                                                                                                                                                                                                      | ENTERO        |                    | Sí          |       |
-| trade_count_daily      | El conteo de operaciones ejecutadas contra la red en un día.                                                                                                                                                                                                       | ENTERO        |                    | Sí          |       |
-| asset_a_volume_daily   | La cantidad total sin procesar del activo vendido en todas las operaciones dentro de ese día.                                                                                                                                                                      | FLOTANTE      |                    | Sí          |       |
-| asset_b_volume_daily   | La cantidad total sin procesar del activo comprado en todas las operaciones dentro de ese día.                                                                                                                                                                     | FLOTANTE      |                    | Sí          |       |
-| avg_price_daily        | La cantidad total del activo comprado en todas las operaciones dividida por la cantidad total del activo vendido en todas las operaciones, dentro de ese día.                                                                                                      | FLOTANTE      |                    | Sí          |       |
-| high_price_daily       | El precio más alto obtenido de la relación entre denominador y numerador para ese día, para el precio activo vendido:comprado.                                                                                                                                     | FLOTANTE      |                    | Sí          |       |
-| low_price_daily        | El precio más bajo obtenido de la relación entre denominador y numerador para ese día, para el precio activo vendido:comprado.                                                                                                                                     | FLOTANTE      |                    | Sí          |       |
-| open_n_daily           | El precio de apertura del numerador dentro de ese día, para la relación de precios activo vendido:comprado.                                                                                                                                                        | ENTERO        |                    | Sí          |       |
-| open_d_daily           | El precio de apertura del denominador dentro de ese día, para la relación de precios activo vendido:comprado.                                                                                                                                                      | ENTERO        |                    | Sí          |       |
-| close_n_daily          | El precio de cierre del numerador dentro de ese día, para la relación de precios activo vendido:comprado.                                                                                                                                                          | ENTERO        |                    | Sí          |       |
-| close_d_daily          | El precio de cierre del denominador dentro de ese día, para la relación de precios activo vendido:comprado.                                                                                                                                                        | ENTERO        |                    | Sí          |       |
-| trade_count_weekly     | El conteo de operaciones ejecutadas contra la red durante los últimos 7 días.                                                                                                                                                                                      | ENTERO        |                    | Sí          |       |
-| asset_a_volume_weekly  | La cantidad total del activo vendido en todas las operaciones durante los últimos 7 días.                                                                                                                                                                          | FLOTANTE      |                    | Sí          |       |
-| asset_b_volume_weekly  | La cantidad total del activo comprado en todas las operaciones durante los últimos 7 días.                                                                                                                                                                         | FLOTANTE      |                    | Sí          |       |
-| avg_price_weekly       | La cantidad total del activo comprado en todas las operaciones dividida por la cantidad total del activo vendido en todas las operaciones, durante los últimos 7 días.                                                                                             | FLOTANTE      |                    | Sí          |       |
-| high_price_weekly      | El precio más alto obtenido de la relación entre denominador y numerador durante los últimos 7 días, para el precio activo vendido:comprado.                                                                                                                       | FLOTANTE      |                    | Sí          |       |
-| low_price_weekly       | El precio más bajo obtenido de la relación entre denominador y numerador durante los últimos 7 días, para el precio activo vendido:comprado.                                                                                                                       | FLOTANTE      |                    | Sí          |       |
-| open_n_weekly          | El precio de apertura del numerador durante los últimos 7 días, para la relación de precios activo vendido:comprado.                                                                                                                                               | ENTERO        |                    | Sí          |       |
-| open_d_weekly          | El precio de apertura del denominador durante los últimos 7 días, para la relación de precios activo vendido:comprado.                                                                                                                                             | ENTERO        |                    | Sí          |       |
-| close_n_weekly         | El precio de cierre del numerador durante los últimos 7 días, para la relación de precios activo vendido:comprado.                                                                                                                                                 | ENTERO        |                    | Sí          |       |
-| close_d_weekly         | El precio de cierre del denominador durante los últimos 7 días, para la relación de precios activo vendido:comprado.                                                                                                                                               | ENTERO        |                    | Sí          |       |
-| trade_count_monthly    | El conteo de operaciones ejecutadas contra la red durante los últimos 30 días.                                                                                                                                                                                     | ENTERO        |                    | Sí          |       |
-| asset_a_volume_monthly | La cantidad total del activo vendido en todas las operaciones durante los últimos 30 días.                                                                                                                                                                         | FLOTANTE      |                    | Sí          |       |
-| asset_b_volume_monthly | La cantidad total del activo comprado en todas las operaciones durante los últimos 30 días.                                                                                                                                                                        | FLOTANTE      |                    | Sí          |       |
-| avg_price_monthly      | La cantidad total del activo comprado en todas las operaciones dividida por la cantidad total del activo vendido en todas las operaciones, durante los últimos 30 días.                                                                                            | FLOTANTE      |                    | Sí          |       |
-| high_price_monthly     | El precio más alto obtenido de la relación entre denominador y numerador durante los últimos 30 días, para el precio activo vendido:comprado.                                                                                                                      | FLOTANTE      |                    | Sí          |       |
-| low_price_monthly      | El precio más bajo obtenido de la relación entre denominador y numerador durante los últimos 30 días, para el precio activo vendido:comprado.                                                                                                                      | FLOTANTE      |                    | Sí          |       |
-| open_n_monthly         | El precio de apertura del numerador durante los últimos 30 días, para la relación de precios activo vendido:comprado.                                                                                                                                              | ENTERO        |                    | Sí          |       |
-| open_d_monthly         | El precio de apertura del denominador durante los últimos 30 días, para la relación de precios activo vendido:comprado.                                                                                                                                            | ENTERO        |                    | Sí          |       |
-| close_n_monthly        | El precio de cierre del numerador durante los últimos 30 días, para la relación de precios activo vendido:comprado.                                                                                                                                                | ENTERO        |                    | Sí          |       |
-| close_d_monthly        | El precio de cierre del denominador durante los últimos 30 días, para la relación de precios activo vendido:comprado.                                                                                                                                              | ENTERO        |                    | Sí          |       |
-| trade_count_yearly     | El conteo de operaciones ejecutadas contra la red durante los últimos 365 días.                                                                                                                                                                                    | ENTERO        |                    | Sí          |       |
-| asset_a_volume_yearly  | La cantidad total del activo vendido en todas las operaciones durante los últimos 365 días.                                                                                                                                                                        | FLOTANTE      |                    | Sí          |       |
-| asset_b_volume_yearly  | La cantidad total del activo comprado en todas las operaciones durante los últimos 365 días.                                                                                                                                                                       | FLOTANTE      |                    | Sí          |       |
-| avg_price_yearly       | La cantidad total del activo comprado en todas las operaciones dividida por la cantidad total del activo vendido en todas las operaciones, durante los últimos 365 días.                                                                                           | FLOTANTE      |                    | Sí          |       |
-| high_price_yearly      | El precio más alto obtenido de la relación entre denominador y numerador durante los últimos 365 días, para el precio activo vendido:comprado.                                                                                                                     | FLOTANTE      |                    | Sí          |       |
-| low_price_yearly       | El precio más bajo obtenido de la relación entre denominador y numerador durante los últimos 365 días, para el precio activo vendido:comprado.                                                                                                                     | FLOTANTE      |                    | Sí          |       |
-| open_n_yearly          | El precio de apertura del numerador durante los últimos 365 días, para la relación de precios activo vendido:comprado.                                                                                                                                             | ENTERO        |                    | Sí          |       |
-| open_d_yearly          | El precio de apertura del denominador durante los últimos 365 días, para la relación de precios activo vendido:comprado.                                                                                                                                           | ENTERO        |                    | Sí          |       |
-| close_n_yearly         | El precio de cierre del numerador durante los últimos 365 días, para la relación de precios activo vendido:comprado.                                                                                                                                               | ENTERO        |                    | Sí          |       |
-| close_d_yearly         | El precio de cierre del denominador durante los últimos 365 días, para la relación de precios activo vendido:comprado.                                                                                                                                             | ENTERO        |                    | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.mdx
deleted file mode 100644
index 95c2497670..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/gold/tvl-agg.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: TVL Agg
-sidebar_position: 80
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración       |
-| --------------------- | ------------------- |
-| Clave natural(s)      | día                 |
-| Campo(s) de partición | No aplica           |
-| Campo(s) agrupado(s)  | No aplica           |
-| Documentación         | No aplica           |
-
-## Detalles de la columna
-
-| Nombre             | Descripción                                                                                                                                                              | Tipo de dato | Valores de dominio | ¿Requerido? | Notas |
-| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------ | ------------------ | ----------- | ----- |
-| día                | La fecha del resultado de la agregación.                                                                                                                                 | fecha        |                    | Sí          |       |
-| accounts_tvl_usd   | El valor total bloqueado (TVL) denominado en USD para una fecha determinada. Agregado a través de cuentas que venden pasivos                                             | flotante     |                    | Sí          |       |
-| trustlines_tvl_usd | El valor total bloqueado (TVL) denominado en USD para una fecha determinada. Agregado a través de trustlines que venden pasivos                                          | flotante     |                    | Sí          |       |
-| total_tvl_usd      | El valor total bloqueado (TVL) denominado en USD para una fecha determinada. Agregado a través de las entradas relevantes del ledger (por ejemplo, cuentas, trustlines). | flotante     |                    | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-assets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-assets.mdx
deleted file mode 100644
index 6517480b91..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-assets.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Historia de Activos
-sidebar_position: 90
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                         |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | asset_code, asset_issuer, asset_type                                                                                  |
-| Campo(s) de Partición | batch_run_date (partición MESES)                                                                                      |
-| Campo(s) agrupado(s)  | asset_code, asset_issuer, asset_type                                                                                  |
-| Documentación         | [dbt_docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_assets_staging) |
-
-## Detalles de las Columnas
-
-| Nombre          | Descripción                                                                                                                                                                                                                               | Tipo de Dato | Valores del Dominio                                                         | ¿Requerido? | Notas                                                                                                                                                                    |
-| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| id              | Identificador único para la combinación de código, tipo e emisor de activo. Esto no es una clave primaria en la tabla                                                                                                                     | float        |                                                                             | Sí          | Obsoleto                                                                                                                                                                 |
-| asset_id        | Identificador único para asset_code, asset_issuer                                                                                                                                                                                         | integer      |                                                                             | No          |                                                                                                                                                                          |
-| asset_type      | El identificador para el tipo de código de activo puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                               | string       | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul> | Sí          | XLM es el activo nativo de la red. XLM no tiene representación de código o emisor de activo y se mostrará con un tipo de activo 'nativo'                                 |
-| asset_code      | La representación en código de 4 o 12 caracteres del activo en la red                                                                                                                                                                     | string       |                                                                             | No          | Los códigos de activos no garantizan la unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto                                        |
-| asset_issuer    | La dirección de cuenta del emisor de activo original que creó el activo                                                                                                                                                                   | string       |                                                                             | No          |                                                                                                                                                                          |
-| batch_id        | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los ids de lotes son únicos para el lote y ayudan con el monitoreo y capacidades de reejecución | string       |                                                                             | Sí          |                                                                                                                                                                          |
-| batch_run_date  | La fecha de inicio para el intervalo de lotes. Tomada con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de closed_at para un ledger.          | datetime     |                                                                             | Sí          | La tabla está particionada por batch_run_date. Se recomienda incluir siempre el batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta. |
-| batch_insert_ts | La marca de tiempo en UTC cuando se insertó un lote de registros en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un backfill                                              | timestamp    |                                                                             | Sí          |                                                                                                                                                                          |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-contract-events.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-contract-events.mdx
deleted file mode 100644
index b73bdcb6d3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-contract-events.mdx
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Eventos del contrato de historial
-sidebar_position: 95
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                          |
-| --------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  |                                                                                                                        |
-| Campo(s) de partición | cerrado_en (partición de MES)                                                                                          |
-| Campo(s) agrupado(s)  | contract_id                                                                                                            |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_contract_events) |
-
-## Detalles de la columna
-
-| Nombre                      | Descripción                                                                                                                                                                                                                                                                                                          | Tipo de dato    | Valores de dominio                                                              | ¿Requerido? | Notas                                                                                                                                                                                     |
-| --------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| transaction_hash            | Un hash SHA-256 codificado en hex de la forma codificada en XDR de esta transacción                                                                                                                                                                                                                                  | cadena          |                                                                                 |             |                                                                                                                                                                                           |
-| transaction_id              | El identificador de la transacción en la que se ejecutó la operación. Puede haber hasta 100 operaciones en una transacción dada                                                                                                                                                                                      | entero          |                                                                                 | Sí          |                                                                                                                                                                                           |
-| exitoso                     | Indica si esta transacción tuvo éxito o no                                                                                                                                                                                                                                                                           | booleano        |                                                                                 | No          | El éxito de una transacción no indica si fue incluida y escrita en un ledger. Solo indica si las operaciones en la transacción se aplicaron exitosamente para mutar el estado del ledger. |
-| in_successful_contract_call | Indica si el evento está en una llamada de contrato exitosa                                                                                                                                                                                                                                                          | booleano        |                                                                                 | Sí          |                                                                                                                                                                                           |
-| contract_id                 |                                                                                                                                                                                                                                                                                                                      | cadena          |                                                                                 |             |                                                                                                                                                                                           |
-| tipo                        | El tipo de evento numérico                                                                                                                                                                                                                                                                                           | entero          | 0, 1, 2                                                                         | Sí          |                                                                                                                                                                                           |
-| tipo_cadena                 | El tipo de evento en cadena                                                                                                                                                                                                                                                                                          | cadena          | ContractEventTypeSystem, ContractEventTypeDiagnostic, ContractEventTypeContract | Sí          |                                                                                                                                                                                           |
-| temas                       | La parte de temas de un evento contiene información identificativa y metadatos para el evento y generalmente lo que significa el evento. Por ejemplo, para SAC esto podría ser un evento de "transferencia" que signifique movimiento de valor de token. Los valores dentro de temas están codificados en base64 XDR | json            |                                                                                 | Sí          |                                                                                                                                                                                           |
-| topics_decoded              | Versión decodificada y legible por humanos del tema del evento                                                                                                                                                                                                                                                       | json            |                                                                                 | Sí          |                                                                                                                                                                                           |
-| datos                       | La parte de datos de un evento es un objeto que contiene los valor(es) significativos para un evento. Por ejemplo, para SAC esto podría ser el "monto" del movimiento de un token de un evento de "transferencia". Los valores dentro de datos están codificados en base64 XDR                                       | json            |                                                                                 | Sí          |                                                                                                                                                                                           |
-| data_decoded                | Versión decodificada y legible por humanos del objeto de datos del evento                                                                                                                                                                                                                                            | json            |                                                                                 | Sí          |                                                                                                                                                                                           |
-| contract_event_xdr          | El XDR del evento codificado en base64                                                                                                                                                                                                                                                                               | cadena          |                                                                                 | Sí          |                                                                                                                                                                                           |
-| batch_id                    | Representación en cadena del id de ejecución para un DAG determinado en Airflow. Toma la forma de "scheduled\_\_[batch_end_date]-[dag_alias]". Los ids de lotes son únicos para el lote y ayudan con las capacidades de monitoreo y reejecución                                                                      | cadena          |                                                                                 | Sí          |                                                                                                                                                                                           |
-| batch_run_date              | La fecha de inicio del intervalo del lote. Cuando se toma con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de cerrado_en para un ledger.                                                                                | fecha y hora    |                                                                                 | Sí          |                                                                                                                                                                                           |
-| batch_insert_ts             | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de una recuperación                                                                                                                 | marca de tiempo |                                                                                 | Sí          |                                                                                                                                                                                           |
-| cerrado_en                  | Marca de tiempo en UTC cuando este ledger cerró y se comprometió a la red. Se espera que los ledgers cierren aproximadamente cada 5 segundos                                                                                                                                                                         | marca de tiempo |                                                                                 | Sí          |                                                                                                                                                                                           |
-| ledger_sequence             | El número de secuencia del ledger en el que se incluyó esta transacción                                                                                                                                                                                                                                              | entero          |                                                                                 | Sí          |                                                                                                                                                                                           |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-effects.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-effects.mdx
deleted file mode 100644
index 2df33696de..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-effects.mdx
+++ /dev/null
@@ -1,266 +0,0 @@
----
-title: Efectos de la Historia
-sidebar_position: 100
-description: ""
----
-
-| Nombre                                          | Descripción                                                                                                                                                                                                                                                                                                                                                                                                        | Tipo de Dato    | Valores de Dominio | ¿Clave Primaria? | ¿Clave Natural? | ¿Campo de Parámetro o de Clúster? | ¿Requerido? | Notas |
-| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------- | ------------------ | ---------------- | --------------- | --------------------------------- | ----------- | ----- |
-| dirección                                       | La dirección de la cuenta. La dirección es la clave pública de la cuenta codificada en base32. Todas las direcciones de cuentas comienzan con una \`G\`                                                                                                                                                                                                                                                            | cadena          |                    |                  |                 | clúster                           |             |       |
-| address_muxed                                   | Dirección multiplexada                                                                                                                                                                                                                                                                                                                                                                                             | cadena          |                    |                  |                 |                                   |             |       |
-| operation_id                                    | Identificador único para una operación                                                                                                                                                                                                                                                                                                                                                                             | entero          |                    |                  |                 | clúster                           |             |       |
-| tipo                                            | El número que indica qué tipo de efecto                                                                                                                                                                                                                                                                                                                                                                            | entero          |                    |                  |                 | clúster                           |             |       |
-| tipo_string                                     | La cadena que indica qué tipo de efecto                                                                                                                                                                                                                                                                                                                                                                            | cadena          |                    |                  |                 |                                   |             |       |
-| detalles                                        | Objeto JSON no estructurado que contiene detalles basados en el tipo de efecto. Cada efecto devolverá sus propios detalles relevantes, con el resto de los detalles como nulos                                                                                                                                                                                                                                     | registro        |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool                          | Los fondos de liquidez proporcionan una forma simple y no interactiva de intercambiar grandes cantidades de capital y permiten grandes volúmenes de comercio                                                                                                                                                                                                                                                       | registro        |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool.fee_bp                   | El número de puntos básicos cobrados como un porcentaje de la operación para completar la transacción. Las tarifas ganadas en todas las operaciones se dividen entre los accionistas del fondo y se distribuyen como un incentivo para mantener el dinero en los fondos                                                                                                                                            | entero          |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool.id                       | Identificador único para un fondo de liquidez. No puede haber fondos duplicados para el mismo par de activos. Una vez que se ha creado un fondo para el par de activos, no se puede crear otro.                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool.total_shares             | Número total de acciones del fondo emitidas                                                                                                                                                                                                                                                                                                                                                                        | numérico        |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool.total_trustlines         | Número de líneas de confianza para las acciones asociadas al fondo                                                                                                                                                                                                                                                                                                                                                 | entero          |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool.type                     | El mecanismo que calcula el precio y la división de acciones para el fondo. Con el lanzamiento inicial de AMM, el único tipo de fondo de liquidez que se puede crear es un fondo de producto constante.                                                                                                                                                                                                            | cadena          |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool.reserves                 | Activo reservado en el fondo de liquidez                                                                                                                                                                                                                                                                                                                                                                           | registro        |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool.reserves.asset           | Activo reservado                                                                                                                                                                                                                                                                                                                                                                                                   | cadena          |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool.reserves.amount          | Cantidad de activos reservados                                                                                                                                                                                                                                                                                                                                                                                     | numérico        |                    |                  |                 |                                   |             |       |
-| details.reserves_received                       | Cantidad de activos recibidos por reservas de la retirada del fondo de liquidez                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| details.reserves_received.asset                 | Activo recibido                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| details.reserves_received.amount                | Cantidad de activos recibidos                                                                                                                                                                                                                                                                                                                                                                                      | numérico        |                    |                  |                 |                                   |             |       |
-| details.reserves_deposited                      | Cantidad de activos depositados para reservas de la entrada del fondo de liquidez                                                                                                                                                                                                                                                                                                                                  | registro        |                    |                  |                 |                                   |             |       |
-| details.reserves_deposited.asset                | Activo depositado                                                                                                                                                                                                                                                                                                                                                                                                  | cadena          |                    |                  |                 |                                   |             |       |
-| details.reserves_deposited.amount               | Cantidad de activos depositados                                                                                                                                                                                                                                                                                                                                                                                    | numérico        |                    |                  |                 |                                   |             |       |
-| details.reserves_revoked                        | Cantidad de activos revocados para reservas de la revocación del fondo de liquidez                                                                                                                                                                                                                                                                                                                                 | registro        |                    |                  |                 |                                   |             |       |
-| details.reserves_revoked.asset                  | Activo revocado                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| details.reserves_revoked.amount                 | Cantidad de activos revocados                                                                                                                                                                                                                                                                                                                                                                                      | numérico        |                    |                  |                 |                                   |             |       |
-| details.reserves_revoked.claimable_balance_id   | ID de balance reclamable                                                                                                                                                                                                                                                                                                                                                                                           | cadena          |                    |                  |                 |                                   |             |       |
-| details.bought                                  | Activo comprado del intercambio                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| details.bought.asset                            | Activo comprado                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| details.bought.amount                           | Cantidad de activos comprados                                                                                                                                                                                                                                                                                                                                                                                      | numérico        |                    |                  |                 |                                   |             |       |
-| details.sold                                    | Activo vendido del intercambio                                                                                                                                                                                                                                                                                                                                                                                     | registro        |                    |                  |                 |                                   |             |       |
-| details.sold.asset                              | Activo vendido                                                                                                                                                                                                                                                                                                                                                                                                     | cadena          |                    |                  |                 |                                   |             |       |
-| details.sold.amount                             | Cantidad de activos vendidos                                                                                                                                                                                                                                                                                                                                                                                       | numérico        |                    |                  |                 |                                   |             |       |
-| details.shares_revoked                          | Acciones revocadas de la revocación del fondo de liquidez                                                                                                                                                                                                                                                                                                                                                          | numérico        |                    |                  |                 |                                   |             |       |
-| details.shares_received                         | Acciones recibidas del depósito del fondo de liquidez                                                                                                                                                                                                                                                                                                                                                              | numérico        |                    |                  |                 |                                   |             |       |
-| details.shares_redeemed                         | Acciones redimidas del retiro del fondo de liquidez                                                                                                                                                                                                                                                                                                                                                                | numérico        |                    |                  |                 |                                   |             |       |
-| details.liquidity_pool_id                       | Identificador único para un fondo de liquidez                                                                                                                                                                                                                                                                                                                                                                      | cadena          |                    |                  |                 |                                   |             |       |
-| details.balance_id                              | El identificador único del saldo reclamable. El id está compuesto por un código de tipo de 8 caracteres + hash SHA-256 del id de operación histórica que creó el saldo. El id de saldo puede unirse de nuevo a la tabla \`claimable_balances\` para obtener más detalles sobre el saldo                                                                                                                            | cadena          |                    |                  |                 |                                   |             |       |
-| details.new_seq                                 | Nuevo número de secuencia después de aumentar la secuencia                                                                                                                                                                                                                                                                                                                                                         | entero          |                    |                  |                 |                                   |             |       |
-| details.name                                    | La operación de gestión de datos permite a una cuenta escribir y almacenar datos directamente en el ledger en un formato de par clave-valor. El nombre es la clave para una entrada de datos.                                                                                                                                                                                                                      | cadena          |                    |                  |                 |                                   |             |       |
-| details.value                                   | Valor de los datos del efecto de gestión de datos                                                                                                                                                                                                                                                                                                                                                                  | cadena          |                    |                  |                 |                                   |             |       |
-| details.trustor                                 | Dirección de cuenta del fideicomitente                                                                                                                                                                                                                                                                                                                                                                             | cadena          |                    |                  |                 |                                   |             |       |
-| details.limit                                   | El límite superior de activos que una cuenta puede poseer                                                                                                                                                                                                                                                                                                                                                          | numérico        |                    |                  |                 |                                   |             |       |
-| details.inflation_destination                   | ID de cuenta del destino de inflación                                                                                                                                                                                                                                                                                                                                                                              | cadena          |                    |                  |                 |                                   |             |       |
-| details.authorized_flag                         | Valor de autorización para establecer los flags de la línea de confianza                                                                                                                                                                                                                                                                                                                                           | booleano        |                    |                  |                 |                                   |             |       |
-| details.auth_immutable_flag                     | Valor de autorización para establecer los flags de la línea de confianza                                                                                                                                                                                                                                                                                                                                           | booleano        |                    |                  |                 |                                   |             |       |
-| details.authorized_to_maintain_liabilites       | Valor de autorización para establecer los flags de la línea de confianza                                                                                                                                                                                                                                                                                                                                           | booleano        |                    |                  |                 |                                   |             |       |
-| details.auth_revocable_flag                     | Valor de autorización para establecer los flags de la línea de confianza                                                                                                                                                                                                                                                                                                                                           | booleano        |                    |                  |                 |                                   |             |       |
-| details.auth_required_flag                      | Valor de autorización para establecer los flags de la línea de confianza                                                                                                                                                                                                                                                                                                                                           | booleano        |                    |                  |                 |                                   |             |       |
-| details.auth_clawback_enabled_flag              | Valor de autorización para establecer los flags de la línea de confianza                                                                                                                                                                                                                                                                                                                                           | booleano        |                    |                  |                 |                                   |             |       |
-| details.claimable_balance_clawback_enabled_flag | Valor de autorización para establecer los flags de la línea de confianza                                                                                                                                                                                                                                                                                                                                           | booleano        |                    |                  |                 |                                   |             |       |
-| details.clawback_enabled_flag                   | Valor de autorización para establecer los flags de la línea de confianza                                                                                                                                                                                                                                                                                                                                           | booleano        |                    |                  |                 |                                   |             |       |
-| details.high_threshold                          | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| details.med_threshold                           | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                                   | entero          |                    |                  |                 |                                   |             |       |
-| detalles.bajo_umbral                            | La suma del peso de todas las firmas que firman una transacción para la operación de bajo umbral. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.dominio_hogar                          | El dominio hogareño utilizado para el descubrimiento del archivo stellar.toml                                                                                                                                                                                                                                                                                                                                      | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.emisor_de_activo                       | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                                                                                                                                        | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.activo                                 | Activo en la red                                                                                                                                                                                                                                                                                                                                                                                                   | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.código_del_activo                      | El código de representación del activo en la red, que puede tener 4 o 12 caracteres                                                                                                                                                                                                                                                                                                                                | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.tipo_de_activo                         | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 o 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                                                                                                                                 | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.firmante                               | La dirección de la cuenta que está autorizada a autorizar (firmar) transacciones para otra cuenta. Este proceso se llama multi-firma                                                                                                                                                                                                                                                                               | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.patrocinador                           | La dirección de la cuenta del patrocinador que está pagando las reservas para este firmante                                                                                                                                                                                                                                                                                                                        | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.nuevo_patrocinador                     | La nueva dirección de la cuenta del patrocinador que está pagando las reservas para este firmante                                                                                                                                                                                                                                                                                                                  | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.ex_patrocinador                        | La dirección anterior de la cuenta del patrocinador que está pagando las reservas para este firmante                                                                                                                                                                                                                                                                                                               | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.peso                                   | Peso del firmante                                                                                                                                                                                                                                                                                                                                                                                                  | entero          |                    |                  |                 |                                   |             |       |
-| detalles.clave_publica                          | Clave pública del firmante                                                                                                                                                                                                                                                                                                                                                                                         | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.cantidad                               | Cantidad del activo                                                                                                                                                                                                                                                                                                                                                                                                | numérico        |                    |                  |                 |                                   |             |       |
-| detalles.saldo_inicial                          | Saldo inicial del activo de la cuenta                                                                                                                                                                                                                                                                                                                                                                              | numérico        |                    |                  |                 |                                   |             |       |
-| detalles.vendedor                               | Cuenta de venta                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.vendedor_multiplexado                  | Cuenta multiplexada                                                                                                                                                                                                                                                                                                                                                                                                | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.id_vendedor_multiplexado               | ID de cuenta multiplexada                                                                                                                                                                                                                                                                                                                                                                                          | entero          |                    |                  |                 |                                   |             |       |
-| detalles.id_oferta                              | El id único para la oferta. Este id se puede unir con la tabla `ofertas`                                                                                                                                                                                                                                                                                                                                           | entero          |                    |                  |                 |                                   |             |       |
-| detalles.cantidad_vendida                       | Cantidad de activo vendido                                                                                                                                                                                                                                                                                                                                                                                         | numérico        |                    |                  |                 |                                   |             |       |
-| detalles.tipo_de_activo_vendido                 | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 o 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                                                                                                                                 | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.código_de_activo_vendido               | El código de representación del activo en la red, que puede tener 4 o 12 caracteres                                                                                                                                                                                                                                                                                                                                | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.emisor_de_activo_vendido               | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                                                                                                                                        | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.tipo_de_activo_comprado                | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 o 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                                                                                                                                                 | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.código_de_activo_comprado              | El código de representación del activo en la red, que puede tener 4 o 12 caracteres                                                                                                                                                                                                                                                                                                                                | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.emisor_de_activo_comprado              | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                                                                                                                                        | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.cantidad_comprada                      | Cantidad de activo comprado                                                                                                                                                                                                                                                                                                                                                                                        | numérico        |                    |                  |                 |                                   |             |       |
-| detalles.nombre_de_datos                        | Nombre de datos de entrada en el ledger                                                                                                                                                                                                                                                                                                                                                                            | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado                              | La condición que debe satisfacerse para que el destino pueda reclamar el saldo. El predicado puede incluir reglas lógicas utilizando AND, OR y NOT.                                                                                                                                                                                                                                                                | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no                           |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.absantes                  |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.relantes                  |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.incondicional             |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.y                         |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.y.absantes                |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.y.relantes                |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.y.incondicional           |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.y.absantes_epoch          |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.o                         |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.o.absantes                |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.o.relantes                |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.o.incondicional           |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.o.absantes_epoch          |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.no                        |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.no.absantes               |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.no.relantes               |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.no.incondicional          |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.no.absantes_epoch         |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.no.absantes_epoch            |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.tipo                         |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y                            |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.absantes                   |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.relantes                   |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.incondicional              |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.y                          |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.y.absantes                 |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.y.relantes                 |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.y.incondicional            |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.y.absantes_epoch           |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.o                          |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.o.absantes                 |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.o.relantes                 |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.o.incondicional            |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.o.absantes_epoch           |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.no                         |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.no.absantes                |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.no.relantes                |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.no.incondicional           |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.no.absantes_epoch          |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.y.absantes_epoch             |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.o                            |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.o.absantes                   |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.o.relantes                   |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicado.o.incondicional              |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.o.y                          |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicado.o.y.absantes                 |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.y.relante                  |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.y.incondicional            |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.y.no                       |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.y.no.absante               |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.y.no.relante               |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.y.no.incondicional         |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.y.no.absante.epoch         |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.y.absante.epoch            |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.o                          |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.o.absante                  |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.o.relante                  |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.o.incondicional            |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.o.absante.epoch            |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.no                         |                                                                                                                                                                                                                                                                                                                                                                                                                    | registro        |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.no.absante                 |                                                                                                                                                                                                                                                                                                                                                                                                                    | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.no.relante                 |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.no.incondicional           |                                                                                                                                                                                                                                                                                                                                                                                                                    | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.no.absante.epoch           |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.o.absante.epoch              |                                                                                                                                                                                                                                                                                                                                                                                                                    | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.absante                      | Plazo para cuando se debe reclamar el saldo. Si se reclama un saldo antes de la fecha, entonces se cumple la cláusula de la condición.                                                                                                                                                                                                                                                                             | cadena          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.relante                      | Un plazo relativo para cuando se puede reclamar el saldo reclamable. El valor representa el número de segundos desde el tiempo de cierre del ledger que creó el saldo reclamable \#### Notas: Esta condición es útil al crear un límite temporal basado en condiciones de creación. Si el creador quería que un saldo solo fuera reclamable una semana después de la creación, esta condición cumpliría esa regla. | entero          |                    |                  |                 |                                   |             |       |
-| detalles.predicate.incondicional                | Si es verdadero, significa que esta cláusula de la condición siempre se cumple. \#### Notas: Cuando el predicado es solo incondicional = true, significa que el saldo se puede reclamar bajo cualquier condición                                                                                                                                                                                                   | booleano        |                    |                  |                 |                                   |             |       |
-| detalles.predicate.absante.epoch                | Un valor de epoch UNIX en segundos que representa la misma fecha límite que absante.                                                                                                                                                                                                                                                                                                                               | entero          |                    |                  |                 |                                   |             |       |
-| id_lote                                         | Representación en texto del id de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<fecha_final_lote>-<alias_dag>`. Los ids de lote son únicos para el lote y ayudan con el monitoreo y las capacidades de reejecución                                                                                                                                                                          | cadena          |                    |                  |                 |                                   |             |       |
-| fecha_ejecución_lote                            | La fecha de inicio para el intervalo de lote. Cuando se toma con la fecha en el id_lote, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de cerrado_en para un ledger.                                                                                                                                                                            | fecha_y_hora    |                    |                  |                 | Partición de MES                  |             |       |
-| fecha_inserción_lote                            | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un llenado retroactivo                                                                                                                                                                                                         | marca_de_tiempo |                    |                  |                 |                                   |             |       |
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                              |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | id                                                                                                                         |
-| Campo(s) de Partición | fecha_ejecución_lote (partición_MES)                                                                                       |
-| Campo(s) agrupado(s)  | dirección, id_operación, tipo                                                                                              |
-| Documentación         | [documentación de dbt](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_effects) |
-
-## Detalles de la Columna
-
-| Nombre                                              | Descripción                                                                                                                                                                                                                                                                            | Tipo de Dato    | Valores de Dominio | ¿Requerido? | Notas |
-| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------ | ----------- | ----- |
-| id                                                  | Este id de efecto único es la concatenación del id de operación y el índice del efecto                                                                                                                                                                                                 | cadena          |                    | Sí          |       |
-| índice                                              | El índice del efecto dentro de la transacción. Este índice ayuda a ordenar los efectos que resultan de la misma transacción, indicando la secuencia en la que ocurrieron.                                                                                                              | entero          |                    | Sí          |       |
-| cerrado_en                                          | Marca de tiempo en UTC cuando este ledger se cerró y se comprometió a la red. Se espera que los ledgers se cierren cada ~5 segundos                                                                                                                                                    | marca_de_tiempo |                    | Sí          |       |
-| número_de_secuencia_del_ledger                      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers sean procesados en el orden correcto.                        | entero          |                    | Sí          |       |
-| dirección                                           | La dirección de la cuenta. La dirección es la clave pública de la cuenta codificada en base32. Todas las direcciones de cuenta comienzan con una `G`                                                                                                                                   | cadena          |                    |             |       |
-| dirección_muxed                                     | Dirección multiplexada                                                                                                                                                                                                                                                                 | cadena          |                    |             |       |
-| id_operación                                        | Identificador único para una operación                                                                                                                                                                                                                                                 | entero          |                    |             |       |
-| tipo                                                | El número que indica qué tipo de efecto                                                                                                                                                                                                                                                | entero          |                    |             |       |
-| tipo_cadena                                         | La cadena que indica qué tipo de efecto                                                                                                                                                                                                                                                | cadena          |                    |             |       |
-| detalles                                            | Objeto JSON no estructurado que contiene detalles basados en el tipo de efecto. Cada efecto devolverá sus propios detalles relevantes, con el resto de los detalles como nulos                                                                                                         | registro        |                    |             |       |
-| detalles.fondos_de_liquidez                         | Los fondos de liquidez proporcionan una forma simple y no interactiva de intercambiar grandes cantidades de capital y permiten altos volúmenes de intercambio                                                                                                                          | registro        |                    |             |       |
-| detalles.fondos_de_liquidez.tasa_bp                 | El número de puntos básicos cobrados como un porcentaje del intercambio para completar la transacción. Las tarifas ganadas en todos los intercambios se dividen entre los accionistas del fondo y se distribuyen como un incentivo para mantener el dinero en los fondos               | entero          |                    |             |       |
-| detalles.fondos_de_liquidez.id                      | Identificador único para un fondo de liquidez. No pueden haber fondos duplicados para el mismo par de activos. Una vez que se ha creado un fondo para el par de activos, no se puede crear otro.                                                                                       | cadena          |                    |             |       |
-| detalles.fondos_de_liquidez.total_acciones          | Número total de acciones emitidas del fondo                                                                                                                                                                                                                                            | numérico        |                    |             |       |
-| detalles.fondos_de_liquidez.total_trustlines        | Número de trustlines para las acciones del fondo asociadas                                                                                                                                                                                                                             | entero          |                    |             |       |
-| detalles.fondos_de_liquidez.tipo                    | El mecanismo que calcula el precio y la división de acciones del fondo. Con el lanzamiento inicial de AMM, el único tipo de fondo de liquidez que se puede crear es un fondo de producto constante.                                                                                    | cadena          |                    |             |       |
-| detalles.fondos_de_liquidez.reservas                | Activo reservado en el fondo de liquidez                                                                                                                                                                                                                                               | registro        |                    |             |       |
-| detalles.fondos_de_liquidez.reservas.activo         | Activo reservado                                                                                                                                                                                                                                                                       | cadena          |                    |             |       |
-| detalles.fondos_de_liquidez.reservas.cantidad       | Cantidad de activo reservado                                                                                                                                                                                                                                                           | numérico        |                    |             |       |
-| detalles.reservas_recibidas                         | Cantidad de activo recibida por reservas desde el retiro del fondo de liquidez                                                                                                                                                                                                         | registro        |                    |             |       |
-| detalles.reservas_recibidas.activo                  | Activo recibido                                                                                                                                                                                                                                                                        | cadena          |                    |             |       |
-| detalles.reservas_recibidas.cantidad                | Cantidad de activo recibido                                                                                                                                                                                                                                                            | numérico        |                    |             |       |
-| detalles.reservas_depositadas                       | Cantidad de activo depositada para reservas desde el depósito del fondo de liquidez                                                                                                                                                                                                    | registro        |                    |             |       |
-| detalles.reservas_depositadas.activo                | Activo depositado                                                                                                                                                                                                                                                                      | cadena          |                    |             |       |
-| detalles.reservas_depositadas.cantidad              | Cantidad de activo depositado                                                                                                                                                                                                                                                          | numérico        |                    |             |       |
-| detalles.reservas_revocadas                         | Cantidad de activo revocada para reservas desde la revocación del fondo de liquidez                                                                                                                                                                                                    | registro        |                    |             |       |
-| detalles.reservas_revocadas.activo                  | Activo revocado                                                                                                                                                                                                                                                                        | cadena          |                    |             |       |
-| detalles.reservas_revocadas.cantidad                | Cantidad de activo revocado                                                                                                                                                                                                                                                            | numérico        |                    |             |       |
-| detalles.reservas_revocadas.claimable_balance_id    | ID de saldo reclamable                                                                                                                                                                                                                                                                 | cadena          |                    |             |       |
-| detalles.comprado                                   | Activo comprado en la operación                                                                                                                                                                                                                                                        | registro        |                    |             |       |
-| detalles.comprado.activo                            | Activo comprado                                                                                                                                                                                                                                                                        | cadena          |                    |             |       |
-| detalles.comprado.cantidad                          | Cantidad de activo comprado                                                                                                                                                                                                                                                            | numérico        |                    |             |       |
-| detalles.vendido                                    | Activo vendido en la operación                                                                                                                                                                                                                                                         | registro        |                    |             |       |
-| detalles.vendido.activo                             | Activo vendido                                                                                                                                                                                                                                                                         | cadena          |                    |             |       |
-| detalles.vendido.cantidad                           | Cantidad de activo vendido                                                                                                                                                                                                                                                             | numérico        |                    |             |       |
-| detalles.acciones_revocadas                         | Acciones revocadas del fondo de liquidez                                                                                                                                                                                                                                               | numérico        |                    |             |       |
-| detalles.acciones_recibidas                         | Acciones recibidas del depósito del fondo de liquidez                                                                                                                                                                                                                                  | numérico        |                    |             |       |
-| detalles.acciones.redimidas                         | Acciones redimidas del retiro del fondo de liquidez                                                                                                                                                                                                                                    | numérico        |                    |             |       |
-| detalles.fondo_de_liquidez_id                       | Identificador único para un fondo de liquidez                                                                                                                                                                                                                                          | cadena          |                    |             |       |
-| detalles.balance_id                                 | El identificador único del saldo reclamable. El id se compone de un código de tipo de 8 caracteres + hash SHA-256 del id de operación de historia que creó el saldo. El id de saldo puede unirse nuevamente a la tabla `claimable_balances` para recopilar más detalles sobre el saldo | cadena          |                    |             |       |
-| detalles.nueva_seq                                  | Nuevo número de secuencia después de aumentar la secuencia                                                                                                                                                                                                                             | entero          |                    |             |       |
-| detalles.nombre                                     | La operación de gestión de datos permite que una cuenta escriba y almacene datos directamente en el ledger en un formato de par clave-valor. El nombre es la clave para una entrada de datos.                                                                                          | cadena          |                    |             |       |
-| detalles.valor                                      | Valor de los datos del efecto de gestión de datos                                                                                                                                                                                                                                      | cadena          |                    |             |       |
-| detalles.fiduciario                                 | Dirección de cuenta del fiduciario                                                                                                                                                                                                                                                     | cadena          |                    |             |       |
-| detalles.límite                                     | La cantidad máxima de un activo que una cuenta puede poseer                                                                                                                                                                                                                            | numérico        |                    |             |       |
-| detalles.destino_inflación                          | ID de cuenta de destino de inflación                                                                                                                                                                                                                                                   | cadena          |                    |             |       |
-| detalles.autorizado_flag                            | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                               | booleano        |                    |             |       |
-| detalles.auth_immutable_flag                        | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                               | booleano        |                    |             |       |
-| detalles.autorizado_para_mantener_responsabilidades | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                               | booleano        |                    |             |       |
-| detalles.auth_revocable_flag                        | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                               | booleano        |                    |             |       |
-| detalles.auth_required_flag                         | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                               | booleano        |                    |             |       |
-| detalles.auth_clawback_enabled_flag                 | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                               | booleano        |                    |             |       |
-| detalles.claimable_balance_clawback_enabled_flag    | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                               | booleano        |                    |             |       |
-| detalles.clawback_enabled_flag                      | Valor de autorización para establecer flags de trustline                                                                                                                                                                                                                               | booleano        |                    |             |       |
-| detalles.high_threshold                             | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                        | entero          |                    |             |       |
-| detalles.med_threshold                              | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                       | entero          |                    |             |       |
-| detalles.low_threshold                              | La suma del peso de todas las firmas que firman una transacción para la operación de umbral bajo. El peso debe exceder el umbral establecido para que la operación tenga éxito.                                                                                                        | entero          |                    |             |       |
-| detalles.home_domain                                | El dominio principal utilizado para el descubrimiento del archivo stellar.toml                                                                                                                                                                                                         | cadena          |                    |             |       |
-| detalles.emisor_activo                              | La dirección de cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                               | cadena          |                    |             |       |
-| detalles.activo                                     | Activo en la red                                                                                                                                                                                                                                                                       | cadena          |                    |             |       |
-| detalles.codigo_activo                              | El código de representación de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                  | cadena          |                    |             |       |
-| detalles.tipo_activo                                | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                           | cadena          |                    |             |       |
-| detalles.firmante                                   | La dirección de la cuenta que puede autorizar (firmar) transacciones para otra cuenta. Este proceso se llama multi-firma                                                                                                                                                               | cadena          |                    |             |       |
-| detalles.sponsor                                    | La dirección de cuenta del patrocinador que está pagando las reservas por este firmante                                                                                                                                                                                                | cadena          |                    |             |       |
-| detalles.nuevo_patrocinador                         | La nueva dirección de cuenta del patrocinador que está pagando las reservas por este firmante                                                                                                                                                                                          | cadena          |                    |             |       |
-| detalles.anterior_patronicador                      | La dirección de cuenta anterior del patrocinador que está pagando las reservas por este firmante                                                                                                                                                                                       | cadena          |                    |             |       |
-| detalles.peso                                       | Peso del firmante                                                                                                                                                                                                                                                                      | entero          |                    |             |       |
-| detalles.clave_publica                              | Clave pública del firmante                                                                                                                                                                                                                                                             | cadena          |                    |             |       |
-| detalles.cantidad                                   | Cantidad de activo                                                                                                                                                                                                                                                                     | numérico        |                    |             |       |
-| detalles.saldo_inicial                              | Saldo inicial del activo de la cuenta                                                                                                                                                                                                                                                  | numérico        |                    |             |       |
-| detalles.vendedor                                   | Cuenta de venta                                                                                                                                                                                                                                                                        | cadena          |                    |             |       |
-| detalles.vendedor_multiplexado                      | Cuenta multiplexada                                                                                                                                                                                                                                                                    | cadena          |                    |             |       |
-| detalles.id_vendedor_multiplexado                   | ID de la cuenta multiplexada                                                                                                                                                                                                                                                           | entero          |                    |             |       |
-| detalles.offer_id                                   | El id único para la oferta. Este id se puede unir con la tabla `offers`                                                                                                                                                                                                                | entero          |                    |             |       |
-| detalles.cantidad_vendida                           | Cantidad de activo vendido                                                                                                                                                                                                                                                             | numérico        |                    |             |       |
-| detalles.tipo_activo_vendido                        | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                           | cadena          |                    |             |       |
-| detalles.código_activo_vendido                      | La representación del código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                 | cadena          |                    |             |       |
-| detalles.emisor_activo_vendido                      | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                            | cadena          |                    |             |       |
-| detalles.tipo_activo_comprado                       | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                           | cadena          |                    |             |       |
-| detalles.código_activo_comprado                     | La representación del código de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                 | cadena          |                    |             |       |
-| detalles.emisor_activo_comprado                     | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                            | cadena          |                    |             |       |
-| detalles.cantidad_comprada                          | Cantidad de activo comprado                                                                                                                                                                                                                                                            | numérico        |                    |             |       |
-| detalles.nombre_datos                               | Nombre de los datos de entrada en el libro mayor                                                                                                                                                                                                                                       | cadena          |                    |             |       |
-| detalles.predicado                                  | La condición que debe cumplirse para que el destino pueda reclamar el saldo. El predicado puede incluir reglas lógicas usando AND, OR y NOT.                                                                                                                                           | registro        |                    |             |       |
-| id_del_lote                                         | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los ids de lote son únicos para el lote y ayudan con la supervisión y las capacidades de reejecución                                         | cadena          |                    |             |       |
-| fecha_de_ejecución_del_lote                         | La fecha de inicio del intervalo de lote. Cuando se toma con la fecha en el batch_id, la fecha representa el intervalo de libros mayores procesados.                                                                                                                                   | fecha_hora      |                    |             |       |
-| marca_de_tiempo_de_inscripción_del_lote             | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos.                                                                                                                                                                                               | marca_de_tiempo |                    |             |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-ledgers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-ledgers.mdx
deleted file mode 100644
index 1bb88eec1d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-ledgers.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Registros de Historia
-sidebar_position: 110
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                              |
-| --------------------- | -------------------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | secuencia                                                                                                                  |
-| Campo(s) de Partición | closed_at (partición por MES)                                                                                              |
-| Campo(s) Agrupado(s)  | secuencia, closed_at                                                                                                       |
-| Documentación         | [documentación de dbt](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_ledgers) |
-
-## Detalles de la Columna
-
-| Nombre                         | Descripción                                                                                                                                                                                                                                                                       | Tipo de Dato    | Valores de Dominio                       | ¿Requerido? | Notas                                                                                                                                                                               |
-| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ---------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| secuencia                      | El número de secuencia que corresponde a los registros individuales. A medida que los registros se escriben en la red, la secuencia se incrementa en 1                                                                                                                            | entero          |                                          | Sí          |                                                                                                                                                                                     |
-| ledger_hash                    | El hash SHA-256 codificado en hexadecimal que representa la forma codificada en XDR del ledger                                                                                                                                                                                    | cadena          |                                          | Sí          |                                                                                                                                                                                     |
-| previous_ledger_hash           | El hash SHA-256 codificado en hexadecimal del ledger que precede inmediatamente a este ledger                                                                                                                                                                                     | cadena          |                                          | No          |                                                                                                                                                                                     |
-| transaction_count              | El número de transacciones exitosas enviadas y completadas por la red en este ledger                                                                                                                                                                                              | entero          |                                          | Sí          | Por defecto es 0                                                                                                                                                                    |
-| operation_count                | El número total de operaciones exitosas aplicadas a este ledger                                                                                                                                                                                                                   | entero          |                                          | Sí          | Por defecto es 0                                                                                                                                                                    |
-| closed_at                      | Marca de tiempo en UTC cuando este ledger se cerró y se comprometió a la red. Se espera que los ledgers se cierren ~cada 5 segundos                                                                                                                                               | marca de tiempo |                                          | Sí          |                                                                                                                                                                                     |
-| id                             | Identificador único para el ledger                                                                                                                                                                                                                                                | entero          |                                          | Sí          |                                                                                                                                                                                     |
-| total_coins                    | Número total de lumens en circulación                                                                                                                                                                                                                                             | entero          |                                          | Sí          |                                                                                                                                                                                     |
-| fee_pool                       | La suma de todas las tarifas de transacción                                                                                                                                                                                                                                       | entero          |                                          | Sí          |                                                                                                                                                                                     |
-| base_fee                       | La tarifa (en stroops) que la red cobra por operación en una transacción para el ledger dado. La tarifa base mínima es 100, con la capacidad de aumentar si la demanda de transacciones supera la capacidad del ledger. Cuando esto ocurre, el ledger entra en tarifas de aumento | entero          |                                          | Sí          | El stroop es la representación fraccionaria de un lumen (XLM). 1 stroop es 0,0000001 XLM.                                                                                           |
-| base_reserve                   | La reserva (en stroops) que la red requiere que una cuenta mantenga como saldo mínimo para ser una cuenta válida en la red. La reserva mínima actual es de 10 XLM                                                                                                                 | entero          | 5000000 100000000                        | Sí          | El stroop es la representación fraccionaria de un lumen (XLM). 1 stroop es 0,0000001 XLM.                                                                                           |
-| max_tx_set_size                | El número máximo de operaciones que los nodos validadores de Stellar han acordado procesar en un ledger dado. Desde el Protocolo 11, la capacidad del ledger se ha medido en operaciones en lugar de transacciones                                                                | entero          | 50 - original max 500 1000 - max actual  | Sí          |                                                                                                                                                                                     |
-| protocol_version               | La versión del protocolo que la red Stellar estaba ejecutando cuando este ledger fue comprometido. Las versiones de protocolo se lanzan ~cada 6 meses                                                                                                                             | entero          | números enteros 1 - 19 (se incrementará) | Sí          | Por defecto es 0                                                                                                                                                                    |
-| ledger_header                  | Una cadena codificada en base64 de la estructura xdr LedgerHeader en bruto para este ledger                                                                                                                                                                                       | bytes           |                                          | No          |                                                                                                                                                                                     |
-| successful_transaction_count   | El número de transacciones exitosas enviadas y completadas por la red en este ledger                                                                                                                                                                                              | entero          |                                          | No          |                                                                                                                                                                                     |
-| failed_transaction_count       | El número de transacciones fallidas enviadas a la red en este ledger. La transacción aún se pagó pero contenía un error que impedía su ejecución                                                                                                                                  | entero          |                                          | No          |                                                                                                                                                                                     |
-| tx_set_operation_count         | El número total de operaciones en el conjunto de transacciones para este ledger, incluyendo transacciones fallidas.                                                                                                                                                               | entero          |                                          | No          | Las transacciones en Stellar son atómicas. Si una de las operaciones dentro de un conjunto de transacciones falla, toda la transacción fallará, incluidas cualquier otra operación. |
-| batch_id                       | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los id de lotes son únicos para el lote y ayudan con el monitoreo y las capacidades de reejecución                                      | cadena          |                                          | Sí          |                                                                                                                                                                                     |
-| batch_run_date                 | La fecha de inicio para el intervalo de lotes. Cuando se toma con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote puede verse como un proxy de closed_at para un ledger.                                          | fecha y hora    |                                          | Sí          | La tabla está particionada por batch_run_date. Se recomienda incluir siempre batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta.               |
-| batch_insert_ts                | La marca de tiempo en UTC cuando un lote de registros se insertó en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un llenado retroactivo                                                                           | marca de tiempo |                                          | Sí          |                                                                                                                                                                                     |
-| soroban_fee_write_1kb          | Costos de la tarifa de escritura de Soroban                                                                                                                                                                                                                                       | entero          |                                          | No          |                                                                                                                                                                                     |
-| firma                          | El hash de firma del nodo validador que escribe el conjunto de transacciones en la red. Esta firma asegura la integridad y autenticidad del ledger, confirmando que no ha sido manipulado                                                                                         | cadena          |                                          | Sí          |                                                                                                                                                                                     |
-| node_id                        | El id del nodo validador ganador que está autorizado a escribir el conjunto de transacciones en la red. El validador ganador es decidido por la red                                                                                                                               | cadena          |                                          | Sí          |                                                                                                                                                                                     |
-| total_byte_size_of_bucket_list | El tamaño, en bytes, de la DB de Bucketlist para la Red Stellar                                                                                                                                                                                                                   | entero          |                                          | Sí          |                                                                                                                                                                                     |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-operations.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-operations.mdx
deleted file mode 100644
index 4c5bb96790..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-operations.mdx
+++ /dev/null
@@ -1,154 +0,0 @@
----
-title: Operaciones de Historia
-sidebar_position: 120
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                     |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | id                                                                                                                |
-| Campo(s) de Partición | batch_run_date (partición por MES)                                                                                |
-| Campo(s) Agrupado(s)  | transaction_id, source_account, type                                                                              |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_operations) |
-
-## Detalles de la Columna
-
-| Nombre                                      | Descripción                                                                                                                                                                                                                                                                                              | Tipo de Dato    | Valores de Dominio                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ¿Requerido? | Notas                                                                                                                                                                                                                                                                                                                                                                                                                                  |
-| ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| id                                          | Identificador único para una operación                                                                                                                                                                                                                                                                   | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | El id de la operación es el id de la transacción + número de orden                                                                                                                                                                                                                                                                                                                                                                     |
-| source_account                              | La dirección de la cuenta que origina la operación                                                                                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | Por defecto es ''                                                                                                                                                                                                                                                                                                                                                                                                                      |
-| source_account_muxed                        | Si una cuenta está multiplexada (muxed), la dirección de la cuenta virtual que origina la operación                                                                                                                                                                                                      | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| transaction_id                              | El identificador de la transacción en la que se ejecutó la operación. Puede haber hasta 100 operaciones en una transacción dada                                                                                                                                                                          | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| ledger_sequence                             | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain Stellar. Cada ledger tiene un número de secuencia único que aumenta con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.                                                    | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| tipo                                        | El número que indica qué tipo de operación ejecuta esta operación                                                                                                                                                                                                                                        | entero          | <ul><li>0 - Crear Cuenta</li><li>1 - Pago</li><li>2 - Pago por Ruta Estricto Recibir</li><li>3 - Ofrecer Venta Administrar</li><li>4 - Crear Oferta de Venta Pasiva</li><li>5 - Establecer Opciones</li><li>6 - Cambiar Confianza</li><li>7 - Permitir Confianza</li><li>8 - Fusión de Cuenta</li><li>9 - Inflación</li><li>10 - Administrar Datos</li><li>11 - Aumentar Secuencia</li><li>12 - Administrar Oferta de Compra</li><li>13 - Pago por Ruta Estricto Enviar</li><li>14 - Crear Saldo Reclamable</li><li>15 - Reclamar Saldo Reclamable</li><li>16 - Comenzar a Patrocinar Reservas Futuras</li><li>17 - Terminar Patrocinio de Reservas Futuras</li><li>18 - Revocar Patrocinio</li><li>19 - Clawback</li><li>20 - Clawback Saldo Reclamable</li><li>21 - Establecer Banderas Línea de Confianza</li><li>22 - Depósito de Fondo de Liquidez</li><li>23 - Retiro de Fondo de Liquidez</li></ul> | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| type_string                                 | La cadena que indica qué tipo de operación ejecuta esta operación                                                                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles                                    | Objeto JSON no estructurado que contiene detalles según el tipo de operación ejecutada                                                                                                                                                                                                                   | blob            | ver detalles a continuación (E10:E108)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          | Bigquery no tiene un tipo de campo JSON (actualmente en piloto pre-GA) así que este campo es en su lugar un campo de registro estructurado y disperso. En los datos ascendentes, este campo es un verdadero blob JSON                                                                                                                                                                                                                  |
-| details.account                             | La nueva dirección de cuenta resultante que se crea y financia (operación de creación) La dirección de cuenta que se está eliminando y fusionando en otra cuenta (operación de fusión)                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.account_muxed                       | La dirección virtual de la cuenta si la cuenta está multiplexada                                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.account_muxed_id                    | Representación entera de la dirección virtual de la cuenta si la cuenta está multiplexada                                                                                                                                                                                                                | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.account_id                          | La dirección de la cuenta que ya no está patrocinada                                                                                                                                                                                                                                                     | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.amount                              | Representación flotante de la cantidad de un activo enviado/ofrecido/etc                                                                                                                                                                                                                                 | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset                               | El activo disponible para reclamar en la forma de "asset_code:issuing_address". Si el saldo reclamable está en XLM, se informa como "nativo"                                                                                                                                                             | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_code                          | El código de representación de 4 o 12 caracteres del activo en la red                                                                                                                                                                                                                                    | cadena          | <ul><li>1 - Pago</li><li>2 - Pago por Ruta Estricto Recibir</li><li>6 - Cambiar Confianza</li><li>7 - Permitir Confianza</li><li>13 - Pago por Ruta Estricto Enviar</li><li>19 - Clawback</li><li>21 - Establecer Banderas Línea de Confianza</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | No          | Los códigos de activos no tienen garantías de unicidad. La combinación del código de activo, emisor y tipo representa un activo distinto                                                                                                                                                                                                                                                                                               |
-| details.asset_issuer                        | La dirección de la cuenta del emisor original del activo que creó el activo                                                                                                                                                                                                                              | cadena          | <ul><li>1 - Pago</li><li>2 - Pago por Ruta Estricto Recibir</li><li>6 - Cambiar Confianza</li><li>7 - Permitir Confianza</li><li>13 - Pago por Ruta Estricto Enviar</li><li>19 - Clawback</li><li>21 - Establecer Banderas Línea de Confianza</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.asset_type                          | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                             | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | No          | XLM es el activo nativo de la red. XLM no tiene representación de código de activo o emisor y se mostrará en su lugar con un tipo de activo 'nativo'                                                                                                                                                                                                                                                                                   |
-| details.authorize                           | Indica si la línea de confianza está autorizada. 0 si la cuenta no está autorizada para transaccionar con el activo de ninguna manera. 1 si la cuenta está autorizada para transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones. | booleano        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.balance_id                          | El identificador único del saldo reclamable. El id se compone de un código de tipo de 8 caracteres + hash SHA-256 del id de la operación histórica que creó el saldo.                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.buying_asset_code                   | El código de representación de 4 o 12 caracteres del activo que se compra o se ofrece para comprar en un comercio                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.buying_asset_issuer                 | La dirección de la cuenta del emisor original del activo comprado u ofrecido para comprar                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.buying_asset_type                   | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                             | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | No          | XLM es el activo nativo de la red. XLM no tiene representación de código de activo o emisor y se mostrará en su lugar con un tipo de activo 'nativo'                                                                                                                                                                                                                                                                                   |
-| details.claimable_balance_id                | El id de saldo reclamable que ya no está patrocinado                                                                                                                                                                                                                                                     | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.claimant                            | La dirección de la cuenta que reclamó el saldo reclamable                                                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.claimant_muxed                      | Si la cuenta está multiplexada, la dirección virtual de la cuenta que reclamó el saldo reclamable                                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.claimant_muxed_id                   | Si la cuenta está multiplexada, una representación entera de la cuenta multiplexada que reclamó el saldo                                                                                                                                                                                                 | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.claimants                           | Un campo no estructurado que lista las direcciones de cuentas elegibles para reclamar un saldo y las condiciones que deben satisfacerse para reclamar el saldo (normalmente condiciones limitadas en el tiempo)                                                                                          | array[registro] |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.data_account_id                     | La dirección de la cuenta cuyo registro de datos ya no está patrocinado                                                                                                                                                                                                                                  | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.data_name                           | El nombre de la entrada de datos que ya no está patrocinada                                                                                                                                                                                                                                              | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.from                                | La dirección de la cuenta desde la que se origina el pago (la cuenta emisora)                                                                                                                                                                                                                            | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.from_muxed                          | Si la cuenta está multiplexada, la dirección virtual de la cuenta emisora                                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.from_muxed_id                      | Si la cuenta está multiplexada, la representación entera de la dirección virtual de la cuenta del remitente                                                                                                                                                                                              | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.funder                             | Cuando se crea una nueva cuenta, una dirección de cuenta "funda" la nueva cuenta                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.funder_muxed                       | Si la cuenta está multiplexada, la dirección virtual de la cuenta que financia la nueva cuenta                                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.funder_muxed_id                    | Si la cuenta está multiplexada, la representación entera de la dirección virtual de la cuenta que financia                                                                                                                                                                                               | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.high_threshold                     | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto                                                                                                                                                                                                         | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Cada operación cae bajo una categoría específica de umbral: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito. Baja Seguridad: Allow Trust, Set Trust Line Flags, Bump Sequence y Claim Claimable Balance; Media Seguridad: Todo lo demás; Alta Seguridad: Account Merge, Set Options                                                                                        |
-| detalles.home_domain                        | El dominio de origen utilizado para el descubrimiento del archivo stellar.toml                                                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.inflation_dest                     | La dirección de cuenta que especifica dónde enviar los fondos de inflación. El concepto de inflación en la red ha sido descontinuado                                                                                                                                                                     | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | La inflación fue retirada de la red en 2019.                                                                                                                                                                                                                                                                                                                                                                                           |
-| detalles.into                               | La dirección de cuenta que recibe los lumens de la cuenta eliminada. Esta es la cuenta en la que se fusionará la cuenta eliminada deseada                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.into_muxed                         | Si la cuenta está multiplexada, la dirección virtual de la cuenta que recibe los lumens de la cuenta eliminada                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.into_muxed_id                      | Si la cuenta está multiplexada, la representación entera de la cuenta que recibe los lumens de la cuenta eliminada                                                                                                                                                                                       | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.limit                              | El monto límite de un activo que una cuenta puede mantener                                                                                                                                                                                                                                               | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.low_threshold                      | La suma del peso de todas las firmas que firman una transacción para la operación de umbral bajo                                                                                                                                                                                                         | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Cada operación cae bajo una categoría específica de umbral: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito. Baja Seguridad: Allow Trust, Set Trust Line Flags, Bump Sequence y Claim Claimable Balance; Media Seguridad: Todo lo demás; Alta Seguridad: Account Merge, Set Options                                                                                        |
-| detalles.master_key_weight                  | La clave privada de una cuenta se llama la clave maestra. Para firmar transacciones, el titular de la cuenta puede especificar un peso para la clave maestra, lo que contribuye a la validación de umbrales al procesar una transacción                                                                  | entero          | Enteros del 1 al 255                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          | Por defecto es 1                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| detalles.med_threshold                      | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio                                                                                                                                                                                                        | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Cada operación cae bajo una categoría específica de umbral: bajo, medio o alto. Los umbrales definen el nivel de privilegio que necesita una operación para tener éxito. Baja Seguridad: Allow Trust, Set Trust Line Flags, Bump Sequence y Claim Claimable Balance; Media Seguridad: Todo lo demás; Alta Seguridad: Account Merge, Set Options                                                                                        |
-| detalles.name                               | La operación de gestionar datos permite a una cuenta escribir y almacenar datos directamente en el ledger en un formato de clave-valor. El nombre es la clave para una entrada de datos                                                                                                                  | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Si el nombre es nuevo, la operación de gestionar datos agregará el par nombre/valor dado a la cuenta. Si el nombre ya está presente, el valor asociado será modificado.                                                                                                                                                                                                                                                                |
-| detalles.offer_id                           | El id único para la oferta. Este id puede unirse con la tabla `offers`                                                                                                                                                                                                                                   | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.path                               | Los pagos de rutas maximizan la mejor tasa de cambio al enviar dinero de un activo a otro activo. Los activos intermedios por los que esta ruta pasa se informarán en el registro. Esta función es especialmente útil cuando el mercado entre el par de activos original es ilíquido                     | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Hasta 6 rutas están permitidas para un solo pago. Ejemplo: enviar EUR -> MXN podría verse como EUR -> BTC -> CNY -> XLM -> MXN para maximizar la mejor tasa de cambio. Los pagos son atómicos, por lo que si un intercambio en medio de un pago de rutas falla, todo el pago fallará, lo que significa que el usuario mantendrá sus fondos originales. No se quedarán atascados con un activo intermedio en caso de que falle el pago. |
-| detalles.price                              | La proporción del activo en venta al activo en compra. Este es un número que representa cuántas unidades de un activo en venta se requieren para obtener 1 unidad de un activo en compra                                                                                                                 | array[flotante] |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.price_r                            | Representación precisa del precio de compra y venta de los activos en una oferta. El n es el numerador, el d es el denominador. Al calcular la proporción de n/d, puedes calcular el precio de la oferta o la demanda                                                                                    | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.selling_asset_code                 | El código de representación de 4 o 12 caracteres del activo que se vende o se ofrece para vender en un intercambio                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.selling_asset_issuer               | La dirección de cuenta del emisor de activo original que creó el activo vendido o ofrecido para vender                                                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.selling_asset_type                 | El identificador para el tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                            | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | No          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación de emisor y se mostrará en su lugar con un tipo de activo de 'nativo'                                                                                                                                                                                                                                                                               |
-| detalles.set_flags                          | Array de valores numéricos de las flags establecidas para una línea de confianza dada en la operación                                                                                                                                                                                                    | array[entero]   | <ul><li>1 - Autorización requerida</li><li>2 - Autorización revocable</li><li>4 - Autorización inmutable</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.set_flags_s                        | Array de valores de cadena de las flags establecidas para una línea de confianza dada en la operación                                                                                                                                                                                                    | array[cadena]   | <ul><li>Autorización requerida</li><li>Autorización revocable</li><li>Autorización inmutable</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.signer_account_id                  | La dirección de la cuenta del firmante que ya no está patrocinada                                                                                                                                                                                                                                        | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.signer_key                         | La dirección del firmante que ya no está patrocinada                                                                                                                                                                                                                                                     | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.signer_weight                      | El peso del nuevo firmante. Para transacciones, múltiples cuentas pueden firmar una transacción desde una cuenta fuente. Este peso contribuye al cálculo de si la transacción excede el peso umbral especificado para completar la transacción                                                           | entero          | Enteros del 1 al 255                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.source_amount                      | El monto de origen enviado designado en el activo fuente                                                                                                                                                                                                                                                 | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.source_asset_code                  | El código de representación de 4 o 12 caracteres del activo que se envió originalmente                                                                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.source_asset_issuer                | La dirección de cuenta del emisor de activo original que creó el activo enviado                                                                                                                                                                                                                          | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.source_asset_type                  | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                             | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | No          | XLM es el activo nativo de la red. XLM no tiene código de activo ni representación del emisor y se mostrará en su lugar con un tipo de activo de 'nativo'                                                                                                                                                                                                                                                                              |
-| detalles.source_max                         | La cantidad máxima a enviar, designada en el activo fuente                                                                                                                                                                                                                                               | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | El intercambio de un activo provoca que se gaste una pequeña cantidad del valor del activo en tarifas y tasas de cambio. El remitente puede especificar una cantidad máxima que está dispuesto a enviar si las tasas entre el par de activos son desfavorables.                                                                                                                                                                        |
-| saldo.inicial                               | La cantidad de XLM a enviar a la cuenta recién creada. El saldo inicial de la cuenta debe superar el saldo mínimo necesario para mantener una cuenta en la red Stellar                                                                                                                                   | float           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.to                                  | La dirección de la cuenta que recibe los fondos del pago                                                                                                                                                                                                                                                 | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.to_muxed                            | Si la cuenta está multiplexada, la dirección virtual de la cuenta que recibe el pago                                                                                                                                                                                                                     | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.to_muxed_id                         | Si la cuenta está multiplexada, la representación entera de la dirección virtual de la cuenta receptora                                                                                                                                                                                                  | integer         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustee                             | La dirección de la cuenta emisora (solo presente para tipos de activos `credit`)                                                                                                                                                                                                                         | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustee_muxed                       | Si la dirección de la cuenta emisora está multiplexada, la dirección virtual                                                                                                                                                                                                                             | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustee_muxed_id                    | Si la dirección de la cuenta emisora está multiplexada, la representación entera de la dirección virtual                                                                                                                                                                                                 | integer         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustline_account_id                | La dirección de la cuenta cuya línea de confianza ya no está patrocinada                                                                                                                                                                                                                                 | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustline_asset                     | El activo de la línea de confianza que ya no está patrocinada                                                                                                                                                                                                                                            | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Un patrocinador puede determinar que desea revocar el patrocinio de ciertos activos pero mantener el patrocinio de otros activos                                                                                                                                                                                                                                                                                                       |
-| details.trustor                             | La dirección de la cuenta confiada, o la cuenta que está siendo autorizada o no autorizada                                                                                                                                                                                                               | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustor_muxed                       | Si la cuenta confiada está multiplexada, la dirección virtual de la cuenta                                                                                                                                                                                                                               | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.trustor_muxed_id                    | Si la cuenta confiada está multiplexada, la representación entera de la dirección virtual                                                                                                                                                                                                                | integer         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.value                               | La operación de gestionar datos permite que una cuenta escriba y almacene datos directamente en el ledger en un formato de clave-valor. El valor es el valor de una clave para una entrada de datos                                                                                                      | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.clear_flags                         | Array de valores numéricos de las banderas desactivadas para una línea de confianza determinada en la operación. Si la bandera fue establecida originalmente, esto eliminará la bandera                                                                                                                  | array[integer]  | <ul><li>1 - Autenticación requerida</li><li>2 - Autenticación revocable</li><li>4 - Autenticación inmutable</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.clear_flags_s                       | Array de valores de cadena de las banderas eliminadas para una línea de confianza determinada en la operación. Si la bandera fue establecida originalmente, esto eliminará la bandera                                                                                                                    | array[string]   | <ul><li>Autenticación requerida</li><li>Autenticación revocable</li><li>Autenticación inmutable</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.destination_min                     | La cantidad mínima a recibir, designada en el activo de destino esperado                                                                                                                                                                                                                                 | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Intercambiar un activo causa que una pequeña cantidad del valor del activo se gaste en comisiones y tipos de cambio. El remitente puede especificar una cantidad mínima garantizada que desea enviar al destinatario para asegurar que reciban un valor específico.                                                                                                                                                                    |
-| details.bump_to                             | El nuevo valor deseado del número de secuencia de la cuenta fuente                                                                                                                                                                                                                                       | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.authorize_to_maintain_liabilities   | Indica si la línea de confianza está autorizada. 0 si la cuenta no está autorizada para transaccionar con el activo de ninguna manera. 1 si la cuenta está autorizada para transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones. | boolean         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.clawback_enabled                    | Indica si el activo puede ser recuperado por el emisor del activo                                                                                                                                                                                                                                        | boolean         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.sponsor                             | La dirección de la cuenta de otra cuenta que mantiene el saldo mínimo en XLM para que la cuenta fuente complete operaciones                                                                                                                                                                              | string          | Cualquier tipo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.sponsored_id                        | La dirección de la cuenta de la cuenta que será patrocinada                                                                                                                                                                                                                                              | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.begin_sponsor                       | La dirección de la cuenta de la cuenta que inició el patrocinio                                                                                                                                                                                                                                          | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.begin_sponsor_muxed                 | Si la cuenta iniciadora del patrocinio está multiplexada, la dirección virtual                                                                                                                                                                                                                           | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.begin_sponsor_muxed_id              | Si la cuenta iniciadora del patrocinio está multiplexada, la representación entera de la dirección virtual                                                                                                                                                                                               | integer         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.liquidity_pool_id                   | Identificador único para un fondo de liquidez                                                                                                                                                                                                                                                            | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Los fondos de liquidez son mercados automáticos entre un par de activos. Un fondo dado solo tendrá dos activos a menos que haya un cambio de protocolo                                                                                                                                                                                                                                                                                 |
-| details.reserve_a_asset_type                | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM                                                                                                                                                              | string          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_a_asset_code                | El código de representación de 4 o 12 caracteres del activo de uno de los dos pares de activos en un fondo de liquidez                                                                                                                                                                                   | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_a_asset_issuer              | La dirección de la cuenta del emisor original del activo que creó uno de los dos pares de activos en el fondo de liquidez                                                                                                                                                                                | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_a_max_amount                | La cantidad máxima de reserva a que puede ser depositada en el fondo                                                                                                                                                                                                                                     | float           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Las operaciones de depósito calculan mediante fórmula cuánto de ambos activos a y b deben ser depositados desde una cuenta fuente e ingresados a un fondo. La cuenta fuente debe depositar un valor equivalente de ambos activos a y b. Dado que los mercados fluctúan, una cantidad máxima especificará el límite superior de un activo que la cuenta está dispuesta a depositar                                                      |
-| details.reserve_a_deposit_amount            | La cantidad de reserva a que terminó siendo efectivamente depositada en el fondo                                                                                                                                                                                                                         | float           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_asset_type                | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM                                                                                                                                                              | string          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_asset_code                | El código de representación de 4 o 12 caracteres del activo de uno de los dos pares de activos en un fondo de liquidez                                                                                                                                                                                   | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_asset_issuer              | La dirección de la cuenta del emisor original del activo que creó uno de los dos pares de activos en el fondo de liquidez                                                                                                                                                                                | string          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| details.reserve_b_max_amount                | La cantidad máxima de reserva b que puede ser depositada en el fondo                                                                                                                                                                                                                                     | float           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Las operaciones de depósito calculan mediante fórmula cuánto de ambos activos a y b deben ser depositados desde una cuenta fuente e ingresados a un fondo. La cuenta fuente debe depositar un valor equivalente de ambos activos a y b. Dado que los mercados fluctúan, una cantidad máxima especificará el límite superior de un activo que la cuenta está dispuesta a depositar                                                      |
-| details.reserve_b_deposit_amount            | La cantidad de reserva b que terminó siendo efectivamente depositada en el fondo                                                                                                                                                                                                                         | float           |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.min_price                          | El valor de punto flotante que indica la tasa de cambio mínima para esta operación de depósito. Informado como Reserva A / Reserva B                                                                                                                                                                     | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Las tasas de mercado fluctúan para la fijación de precios y la cuenta de origen puede especificar un precio mínimo que espera recibir como una proporción de los dos activos en el grupo                                                                                                                                                                                                                                               |
-| detalles.min_price_r                        | Una representación fraccionaria de los precios de los dos activos en un grupo. El n es el numerador (valor del activo a) y el d es el denominador (valor del activo b)                                                                                                                                   | array[registro] |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.max_price                          | El valor de punto flotante que indica la tasa de cambio máxima para esta operación de depósito. Informado como Reserva A / Reserva B                                                                                                                                                                     | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          | Las tasas de mercado fluctúan para la fijación de precios y la cuenta de origen puede especificar un precio máximo que espera recibir como una proporción de los dos activos en el grupo                                                                                                                                                                                                                                               |
-| detalles.max_price_r                        | Una representación fraccionaria de los precios de los dos activos en un grupo. El n es el numerador (valor del activo a) y el d es el denominador (valor del activo b)                                                                                                                                   | array[registro] |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.shares_received                    | Un número en punto flotante que representa el número de acciones de la piscina recibidas por este depósito. Una acción de piscina es una compilación de las reservas del activo a y del activo b. No es posible poseer solo el activo a o el activo b en un grupo                                        | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.reserve_a_min_amount               | La cantidad mínima de la reserva a que se puede retirar del grupo                                                                                                                                                                                                                                        | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.reserve_a_withdraw_amount          | La cantidad de la reserva a que terminó siendo realmente retirada del grupo                                                                                                                                                                                                                              | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.reserve_b_min_amount               | La cantidad mínima de la reserva b que se puede retirar del grupo                                                                                                                                                                                                                                        | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.reserve_b_withdraw_amount          | La cantidad de la reserva b que terminó siendo realmente retirada del grupo                                                                                                                                                                                                                              | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.shares                             | El número de acciones retiradas del grupo. No es posible retirar solo el activo a o el activo b; se debe retirar un valor igual del grupo                                                                                                                                                                | flotante        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.asset_balance_changes              | Los cambios en el saldo aplicados a una cuenta o contrato desde una función de host de invocación. Un activo debe ser un activo clásico transferido a través del [SAC](https://soroban.stellar.org/docs/tokens/stellar-asset-contract) para ser incluido.                                                | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.asset_balance_changes.amount       | La cantidad de tokens creados, transferidos o quemados usando el contrato SAC                                                                                                                                                                                                                            | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.asset_balance_changes.asset_code   | El código de 4 o 12 caracteres que representa el activo transferido usando el contrato SAC                                                                                                                                                                                                               | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.asset_balance_changes.asset_issuer | La dirección de billetera de la cuenta que emitió el activo. Este activo es un activo clásico aunque se envía a través del contrato SAC                                                                                                                                                                  | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.asset_balance_changes.asset_type   | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM                                                                                                                                                              | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>nativo</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.asset_balance_changes.from         | La dirección de billetera o el id del contrato de origen desde donde se enviaron los fondos                                                                                                                                                                                                              | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.asset_balance_changes.to           | La dirección de billetera o el id del contrato de destino donde van los fondos                                                                                                                                                                                                                           | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.asset_balance_changes.type         | El tipo de operación SAC específica que indica el tipo de transferencia de valor que está ocurriendo.                                                                                                                                                                                                    | cadena          | <ul><li>mint</li><li>transferir</li><li>quemar</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.parameters                         | Los parámetros pasados a la llamada de función para un contrato Soroban. Estos son XDR codificados en base64. El registro sigue el formato de par `tipo` + `valor`                                                                                                                                       | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.parameters_decoded                 | Los parámetros decodificados y legibles por humanos que se pasaron a una llamada de función para un contrato Soroban. El registro sigue el formato de par `tipo` + `valor`                                                                                                                               | registro        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.function                           | El tipo de función invocada por la operación del host                                                                                                                                                                                                                                                    | cadena          | <ul><li>HostFunctionTypeHostFunctionTypeInvokeContract</li><li>HostFunctionTypeHostFunctionTypeCreateContract</li><li>HostFunctionTypeHostFunctionTypeUploadContractWasm</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.address                            | La dirección de billetera utilizada para crear y desplegar una instancia de contrato Soroban                                                                                                                                                                                                             | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.type                               | El tipo de operación Soroban que se invoca dentro de una función de host                                                                                                                                                                                                                                 | cadena          | <ul><li>invoke_contract</li><li>create_contract</li><li>upload_wasm</li><li>extend_footprint_ttl</li><li>restore_footprint</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.extend_to                          | El número de ledgers en los que se extiende la entrada del ledger Soroban                                                                                                                                                                                                                                | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.contract_id                        | El identificador único de la instancia de contrato desplegada. Cada contrato Soroban personalizado y token SAC desplegado tendrá un contract_id único                                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| detalles.contract_code_hash                 | El hash codificado en hexadecimal SHA-256 que representa la forma codificada en XDR del código del contrato                                                                                                                                                                                              | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | No          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| batch_id                                    | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los ids de lotes son únicos para el lote y ayudan con las capacidades de monitoreo y reejecución                                                               | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| batch_run_date                              | La fecha de inicio para el intervalo de lotes. Cuando se toma con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del lote se puede ver como un proxy de closed_at para un ledger                                                                 | datetime        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | La tabla está particionada por batch_run_date. Se recomienda incluir siempre el batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta                                                                                                                                                                                                                                                                |
-| batch_insert_ts                             | La marca de tiempo en UTC cuando se insertó un lote de registros en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un backfill                                                                                                             | timestamp       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| closed_at                                   | Marca de tiempo en UTC cuando este ledger se cerró y se comprometió a la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                                                                       | timestamp       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | Estamos buscando reorganizar esta tabla por closed_at                                                                                                                                                                                                                                                                                                                                                                                  |
-| operation_result_code                       | El código de resultado devuelto cuando se aplica una operación. Este código es útil para entender operaciones fallidas                                                                                                                                                                                   | cadena          | <ul><li>OperationResultCodeOpInner</li><li>OperationResultCodeOpBadAuth</li><li>OperationResultCodeOpNoAccount</li><li>OperationResultCodeOpNotSupported</li><li>OperationResultCodeOpTooManySubentries</li><li>OperationResultCodeOpExceededWorkLimit</li><li>OperationResultCodeOpTooManySponsoring</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Sí          | El campo se llenará en una fecha futura                                                                                                                                                                                                                                                                                                                                                                                                |
-| operation_trace_code                        | El código de traza devuelto cuando se aplica una operación a la red Stellar. Este código es útil para comprender fallos matizados por tipo de operación. Este código proporciona el detalle más bajo sobre por qué falla una transacción                                                                 | cadena          | <ul><li>InvokeHostFunctionResultCodeInvokeHostFunctionSuccess</li><li>Malformed</li><li>Trapped</li><li>ResourceLimitExceeded</li><li>EntryArchived</li><li>InsufficientRefundableFee</li><li>ExtendFootprintTtlResultCodeExtendFootprintTtlSuccess</li><li>Malformed</li><li>ResourceLimitExceeded</li><li>InsufficientRefundableFee</li><li>RestoreFootprintResultCodeRestoreFootprintSuccess</li><li>Malformed</li><li>ResourceLimitExceeded</li><li>InsufficientRefundableFee</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                | Sí          | Consulta la [documentación](https://pkg.go.dev/github.com/stellar/go/xdr#OperationResultTr) de XDR para más detalles                                                                                                                                                                                                                                                                                                                   |
-| detalles_json                               | Registro que contiene detalles basados en el tipo de operación ejecutada. Cada operación devolverá sus propios detalles relevantes, y el resto de los detalles como nulos                                                                                                                                | json            |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |             |                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-trades.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-trades.mdx
deleted file mode 100644
index 7cf6dcbf30..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-trades.mdx
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Historial de Trades
-sidebar_position: 130
-description: ""
----
-
-<div className="scoped-data-dictionary-table ">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                 |
-| --------------------- | ------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | history_operation_id, order                                                                                   |
-| Campo(s) de Partición | ledger_closed_at (partición de MES)                                                                           |
-| Campo(s) agrupado(s)  | selling_asset_id, buying_asset_id, trade_type                                                                 |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_trades) |
-
-## Detalles de la Columna
-
-| Nombre                    | Descripción                                                                                                                                                                                                                                                                                                                                                                           | Tipo de Dato    | Valores de Dominio                                                                                | ¿Requerido? | Notas                                                                                                                                                                    |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| history_operation_id      | El id de operación asociado con el trade ejecutado. La cantidad total negociada en una operación puede dividirse en múltiples trades más pequeños distribuidos entre múltiples órdenes por múltiples partes                                                                                                                                                                           | entero          |                                                                                                   | Sí          | Hay una relación muchos a uno para history_operation_id con la tabla history_operations.                                                                                 |
-| orden                     | El número secuencial asignado a la porción de un trade que se ejecuta dentro de una operación. El history_operation_id y el número de orden juntos representan un segmento de trade único                                                                                                                                                                                             | entero          |                                                                                                   | Sí          |                                                                                                                                                                          |
-| ledger_closed_at          | La marca de tiempo en UTC cuando se cerró el ledger con este trade                                                                                                                                                                                                                                                                                                                    | marca de tiempo |                                                                                                   | Sí          |                                                                                                                                                                          |
-| selling_account_address   | La dirección de cuenta de la parte vendedora                                                                                                                                                                                                                                                                                                                                          | cadena          |                                                                                                   | No          |                                                                                                                                                                          |
-| selling_asset_code        | El código de 4 o 12 caracteres del activo vendido en un trade                                                                                                                                                                                                                                                                                                                         | cadena          |                                                                                                   | No          | Los códigos de activos no tienen garantía de unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto                                   |
-| selling_asset_issuer      | La dirección de cuenta del emisor original del activo para el activo vendido en un trade                                                                                                                                                                                                                                                                                              | cadena          |                                                                                                   | No          |                                                                                                                                                                          |
-| selling_asset_type        | El identificador para el tipo de código de activo utilizado para el activo vendido en el trade                                                                                                                                                                                                                                                                                        | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                       | Sí          | XLM es el activo nativo de la red. XLM no tiene representación de código de activo o emisor y en su lugar se mostrará con un tipo de activo 'nativo'                     |
-| selling_amount            | La cantidad de activo vendido que se movió de la cuenta del vendedor a la cuenta del comprador, reportada en términos de la cantidad vendida                                                                                                                                                                                                                                          | float           |                                                                                                   | Sí          |                                                                                                                                                                          |
-| buying_account_address    | La dirección de cuenta de la parte compradora                                                                                                                                                                                                                                                                                                                                         | cadena          |                                                                                                   | No          |                                                                                                                                                                          |
-| buying_asset_code         | El código de 4 o 12 caracteres del activo comprado en un trade                                                                                                                                                                                                                                                                                                                        | cadena          |                                                                                                   | No          | Los códigos de activos no tienen garantía de unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto                                   |
-| buying_asset_issuer       | La dirección de cuenta del emisor original del activo para el activo comprado en un trade                                                                                                                                                                                                                                                                                             | cadena          |                                                                                                   | No          |                                                                                                                                                                          |
-| buying_asset_type         | El identificador para el tipo de código de activo usado para el activo comprado dentro del trade                                                                                                                                                                                                                                                                                      | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                       | Sí          | XLM es el activo nativo de la red. XLM no tiene representación de código de activo o emisor y en su lugar se mostrará con un tipo de activo 'nativo'                     |
-| buying_amount             | La cantidad de activo comprado que se movió de la cuenta del vendedor a la cuenta del comprador, reportada en términos del activo comprado                                                                                                                                                                                                                                            | float           |                                                                                                   | Sí          |                                                                                                                                                                          |
-| price_n                   | La relación de precio del activo vendido: activo comprado. Cuando se toma junto con price_d, el precio puede calcularse mediante price_n/price_d                                                                                                                                                                                                                                      | entero          |                                                                                                   | No          |                                                                                                                                                                          |
-| price_d                   | La relación de precio del activo vendido: activo comprado. Cuando se toma junto con price_n, el precio puede calcularse mediante price_n/price_d                                                                                                                                                                                                                                      | entero          |                                                                                                   | No          |                                                                                                                                                                          |
-| selling_offer_id          | El id de la oferta en el libro de órdenes de la oferta de venta. Si esta oferta fue consumida inmediata y completamente, este será un id sintético.                                                                                                                                                                                                                                   | entero          |                                                                                                   | No          |                                                                                                                                                                          |
-| buying_offer_id           | El id de la oferta en el libro de órdenes de la oferta de compra. Si esta oferta fue consumida inmediata y completamente, este será un id sintético.                                                                                                                                                                                                                                  | entero          |                                                                                                   | No          |                                                                                                                                                                          |
-| batch_id                  | Representación en forma de cadena del id del run para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los ids de batch son únicos al batch y ayudan con la supervisión y capacidades de reejecución                                                                                                                                           | cadena          |                                                                                                   | No          |                                                                                                                                                                          |
-| batch_run_date            | La fecha de inicio para el intervalo del batch. Cuando se toma junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger.                                                                                                                                      | datetime        |                                                                                                   | No          | La tabla está particionada por batch_run_date. Se recomienda siempre incluir el batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta. |
-| batch_insert_ts           | La marca de tiempo en UTC cuando un batch de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un retrollenado                                                                                                                                                                                 | marca de tiempo |                                                                                                   | No          |                                                                                                                                                                          |
-| selling_liquidity_pool_id | El identificador único para un fondo de liquidez si el trade se ejecutó contra un fondo de liquidez en lugar del libro de órdenes                                                                                                                                                                                                                                                     | cadena          |                                                                                                   | No          |                                                                                                                                                                          |
-| liquidity_pool_fee        | El porcentaje de tasa (en puntos básicos) de la tarifa total recaudada por el fondo de liquidez por ejecutar el trade. La tarifa se agrupa y se distribuye nuevamente a los accionistas del fondo de liquidez para incentivar a los usuarios a invertir dinero en el fondo.                                                                                                           | entero          | 30                                                                                                | No          | Las tarifas de los fondos de liquidez solo pueden cambiar con cambios en el protocolo de la red misma                                                                    |
-| trade_type                | Indica si el trade se ejecutó contra el libro de órdenes (intercambio descentralizado) o fondo de liquidez                                                                                                                                                                                                                                                                            | entero          | <ul><li>1 - Trade de Intercambio Descentralizado</li><li>2 - Trade de Fondo de Liquidez</li></ul> | No          |                                                                                                                                                                          |
-| rounding_slippage         | Aplica solo a trades de fondos de liquidez. Con cantidades fraccionarias de un activo negociado, la red debe redondear una fracción al número entero más cercano. Esto puede causar que el trade "resbale" el precio por un porcentaje en comparación con la oferta original. El deslizamiento por redondeo informa el porcentaje que los trades de polvo deslizan antes de ejecutar. | entero          |                                                                                                   | No          | Por defecto es 1. El deslizamiento por redondeo siempre es perjudicial para el trader y no es una forma válida de intentar extraer más valor de la red.                  |
-| seller_is_exact           | Indica si el trade de la parte compradora o vendedora se vio afectado por el deslizamiento por redondeo. Si es verdadero, el comprador fue afectado. Si es falso, el vendedor fue afectado                                                                                                                                                                                            | booleano        |                                                                                                   | No          |                                                                                                                                                                          |
-| selling_asset_id          | Identificador único para selling_asset_code, selling_asset_issuer                                                                                                                                                                                                                                                                                                                     | entero          |                                                                                                   | No          |                                                                                                                                                                          |
-| buying_asset_id           | Identificador único para buying_asset_code, buying_asset_issuer                                                                                                                                                                                                                                                                                                                       | entero          |                                                                                                   | No          |                                                                                                                                                                          |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-transactions.mdx
deleted file mode 100644
index f3032bbf0c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/history-transactions.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Historial de transacciones
-sidebar_position: 140
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de tabla
-
-| Propiedad             | Configuración                                                                                                       |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | id                                                                                                                  |
-| Campo(s) de partición | batch_run_date (partición por MES)                                                                                  |
-| Campo(s) agrupado(s)  | account, ledger_sequence, successful                                                                                |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.history_transactions) |
-
-## Detalles de columna
-
-| Nombre                                 | Descripción                                                                                                                                                                                                                                                                                                                                                             | Tipo de datos   | Valores de dominio                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | ¿Requerido? | Notas                                                                                                                                                                                     |
-| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| id                                     | Un identificador único para esta transacción                                                                                                                                                                                                                                                                                                                            | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                                           |
-| transaction_hash                       | Un hash SHA-256 codificado en hexadecimales de la forma XDR de esta transacción                                                                                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |             |                                                                                                                                                                                           |
-| ledger_sequence                        | El número de secuencia del ledger en el que se incluyó esta transacción                                                                                                                                                                                                                                                                                                 | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                                           |
-| account                                | La dirección de la cuenta que origina la transacción                                                                                                                                                                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                                           |
-| account_sequence                       | El número de secuencia de la cuenta de origen que consumió esta transacción. Los números de secuencia solo se pueden usar una vez y ayudan a mantener la atomicidad y la idempotencia en la red.                                                                                                                                                                        | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                                           |
-| max_fee                                | La tarifa máxima (en stroops) que la cuenta de origen está dispuesta a pagar para que la transacción se incluya en un ledger. Cuando la red entra en precios de sobrecarga, esto ayuda a determinar si una transacción es incluida en el conjunto                                                                                                                       | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          | El stroop es la representación fraccionaria de un lumen (XLM). 1 stroop es 0,0000001 XLM.                                                                                                 |
-| operation_count                        | El número de operaciones contenidas dentro de esta transacción                                                                                                                                                                                                                                                                                                          | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          | Se permite que una transacción tenga hasta 100 operaciones                                                                                                                                |
-| created_at                             | La fecha en que se creó la transacción                                                                                                                                                                                                                                                                                                                                  | timestamp       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| memo_type                              | El tipo de memo                                                                                                                                                                                                                                                                                                                                                         | cadena          | <ul><li>MemoTypeMemoHash</li><li>MemoTypeMemoId</li><li>MemoTypeMemoNone</li><li>MemoTypeMemoReturn</li><li>MemoTypeMemoText</li></ul>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sí          | Predeterminado a `MemoTypeMemoNone`                                                                                                                                                       |
-| memo                                   | Un campo opcional de formato libre que adjunta un memo a una transacción                                                                                                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          | Los memos se utilizan mucho en los exchanges centralizados para ayudar con la administración de cuentas.                                                                                  |
-| time_bounds                            | Una condición previa para la transacción que se puede establecer para determinar cuándo es válida una transacción. El usuario puede establecer un límite temporal inferior y superior, definido como un timestamp UNIX cuando la transacción puede ser ejecutada. Si la transacción intenta ejecutarse fuera del rango temporal, la transacción fallará                 | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| successful                             | Indica si esta transacción fue exitosa o no                                                                                                                                                                                                                                                                                                                             | booleano        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          | El éxito de una transacción no indica si fue incluida y escrita en un ledger. Solo indica si las operaciones en la transacción se aplicaron exitosamente para mutar el estado del ledger. |
-| fee_charged                            | La tarifa (en stroops) pagada por la cuenta de origen para aplicar esta transacción al ledger. Como mínimo, se cobra a la transacción el número de operaciones \* tarifa base. La tarifa base mínima es 100 stroops                                                                                                                                                     | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          | El stroop es la representación fraccionaria de un lumen (XLM). 1 stroop es 0,0000001 XLM.                                                                                                 |
-| inner_transaction_hash                 | Un hash de transacción de una transacción que envuelve sus firmas para transacciones de ajuste de tarifa                                                                                                                                                                                                                                                                | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| fee_account                            | Se permite que una cuenta que no es la cuenta de origen pague las tarifas de transacción en nombre de la cuenta de origen. Estas cuentas se llaman cuentas de tarifa y asumen todos los costos de transacción para la cuenta de origen.                                                                                                                                 | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| new_max_fee                            | Si una cuenta tiene una cuenta de tarifa, la cuenta de tarifa puede especificar una tarifa máxima (en stroops) que está dispuesta a pagar por las tarifas de esta cuenta. Cuando la red está en precios de sobrecarga, los validadores considerarán la new_max_fee en lugar de la max_fee al determinar si la transacción será incluida en el conjunto de transacciones | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| account_muxed                          | Si el usuario ha definido cuentas multiplexadas (muxed), la cuenta existe "virtualmente" bajo una dirección de cuenta Stellar tradicional. Esta dirección distingue entre las cuentas virtuales                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| fee_account_muxed                      | Si la cuenta de tarifa que patrocina la tarifa es una cuenta multiplexada, la dirección virtual se enumerará aquí                                                                                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| ledger_bounds                          | Una condición previa a la transacción que se puede establecer para determinar las condiciones válidas para una transacción que se envíe a la red. Los límites del ledger permiten al usuario especificar un número mínimo y máximo de número de secuencia de ledger en el que la transacción puede ejecutarse exitosamente                                              | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| min_account_sequence                   | Una condición previa a la transacción que se puede establecer para determinar las condiciones válidas para una transacción que se envíe a la red. Esta condición contiene una representación entera del número de secuencia más bajo de la cuenta de origen para la cual la transacción es válida                                                                       | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| min_account_sequence_age               | Una condición previa a la transacción que se puede establecer para determinar las condiciones válidas para una transacción que se envíe a la red. Esta condición contiene una duración mínima de tiempo que debe haber pasado desde que cambió el número de secuencia de la cuenta de origen para que la transacción sea válida                                         | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| min_account_sequence_ledger_gap        | Una condición previa a la transacción que se puede establecer para determinar las condiciones válidas para una transacción que se envíe a la red. Esta condición contiene una representación entera del número mínimo de ledgers que deben haberse cerrado desde que cambió el número de secuencia de la cuenta de origen para que la transacción sea válida            | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| extra_signers                          | Un array de hasta dos firmantes adicionales que deben tener firmas correspondientes para que esta transacción sea válida                                                                                                                                                                                                                                                | array[string]   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| tx_envelope                            | blobb codificado en base-64 XDR                                                                                                                                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| tx_result                              | blobb codificado en base-64 XDR                                                                                                                                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| tx_meta                                | blobb codificado en base-64 XDR                                                                                                                                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| tx_fee_meta                            | blobb codificado en base-64 XDR                                                                                                                                                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| batch_id                               | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_[batch_end_date]-[dag_alias]". Los ids de batch son únicos para el batch y ayudan con la supervisión y capacidades de reejecución                                                                                                                              | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                                           |
-| batch_run_date                         | La fecha de inicio del intervalo por lotes. Cuando se toma con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución por lotes se puede ver como un proxy de closed_at para un ledger.                                                                                                                                 | datetime        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          | La tabla se partitiona por batch_run_date. Se recomienda incluir siempre batch_run_date en el filtro si es posible para ayudar a reducir el costo de consulta.                            |
-| batch_insert_ts                        | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un backfill                                                                                                                                                                         | timestamp       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                                           |
-| resource_fee                           | La tarifa cobrada menos la tarifa de inclusión para la transacción Soroban. Esto se calcula por las operaciones de lectura/escritura y cuán intensiva es la transacción Soroban                                                                                                                                                                                         | entero          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| instrucciones_recursos_soroban         | Número de instrucciones de CPU que usa la transacción Soroban                                                                                                                                                                                                                                                                                                           | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| bytes_leídos_recursos_soroban          | Número de bytes leídos por la transacción Soroban                                                                                                                                                                                                                                                                                                                       | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| bytes_escritos_recursos_soroban        | Número de bytes escritos por la transacción Soroban                                                                                                                                                                                                                                                                                                                     | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| cerrado_en                             | Marca de tiempo en UTC cuando este ledger se cerró y se comprometió a la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                                                                                                                                      | marca_de_tiempo |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Sí          | Tenemos como objetivo reorganizar la tabla por cerrado_en                                                                                                                                 |
-| código_resultado_transacción           | El código de resultado detallado que describe por qué falló una transacción. Este código solo es útil para transacciones fallidas. La lista completa de valores de dominio se puede encontrar [aquí](https://pkg.go.dev/github.com/stellar/go/xdr#TransactionResultCode)                                                                                                | cadena          | <ul><li>CódigoDeResultadoDeTransacciónTxIncrementoDeTarifaInternaÉxito</li><li>CódigoDeResultadoDeTransacciónTxÉxito</li><li>CódigoDeResultadoDeTransacciónTxFallido</li><li>CódigoDeResultadoDeTransacciónTxDemasiadoTemprano</li><li>CódigoDeResultadoDeTransacciónTxDemasiadoTarde</li><li>CódigoDeResultadoDeTransacciónTxOperaciónFaltante</li><li>CódigoDeResultadoDeTransacciónTxMalaSecuencia</li><li>CódigoDeResultadoDeTransacciónTxMalaAutenticación</li><li>CódigoDeResultadoDeTransacciónTxSaldoInsuficiente</li><li>CódigoDeResultadoDeTransacciónTxSinCuenta</li><li>CódigoDeResultadoDeTransacciónTxTarifaInsuficiente</li><li>CódigoDeResultadoDeTransacciónTxMalaAutenticaciónExtra</li><li>CódigoDeResultadoDeTransacciónTxErrorInterno</li><li>CódigoDeResultadoDeTransacciónTxNoSoportado</li><li>CódigoDeResultadoDeTransacciónTxIncrementoDeTarifaInternaFallido</li><li>CódigoDeResultadoDeTransacciónTxMalaSponsorización</li><li>CódigoDeResultadoDeTransacciónTxMalaEdadDeSecuenciaMínimaOIntervalo</li><li>CódigoDeResultadoDeTransacciónTxMalformado</li><li>CódigoDeResultadoDeTransacciónTxSorobanInválido</li></ul> | Sí          |                                                                                                                                                                                           |
-| oferta_tasa_inclusión                  | La oferta máxima que el presentador está dispuesto a pagar por la inclusión de la transacción. Esta tarifa se utiliza para priorizar las transacciones que se incluyen en el ledger.                                                                                                                                                                                    | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| tarifa_inclusión_cobrada               | La tarifa cobrada por la transacción para ser incluida en el ledger. Esta es una tarifa fija para todo el ledger y comienza con un mínimo de 100 stroops. La tarifa aumenta según la demanda                                                                                                                                                                            | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| reembolso_tarifa_recurso               | La cantidad del reembolso de la tarifa del recurso al presentador de la transacción. Las tarifas reembolsables se calculan a partir del alquiler, eventos y valor de retorno. Las tarifas reembolsables se cobran de la cuenta origen antes de que se ejecute la transacción y luego se reembolsan según el uso real.                                                   | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | No          |                                                                                                                                                                                           |
-| tarifa_recurso_no_reembolsable_cobrada | La cantidad cobrada por la transacción que no es reembolsable                                                                                                                                                                                                                                                                                                           | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |             |                                                                                                                                                                                           |
-| tarifa_recurso_reembolsable_cobrada    | La cantidad cargada por la transacción de la tarifa_reembolsable                                                                                                                                                                                                                                                                                                        | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |             |                                                                                                                                                                                           |
-| tarifa_alquiler_cobrada                | La tarifa de alquiler cobrada para persistir el contrato o código del contrato                                                                                                                                                                                                                                                                                          | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |             |                                                                                                                                                                                           |
-| tarifa_reembolsable                    | La cantidad de tarifas de recursos que son reembolsables según el uso real de los recursos en la transacción                                                                                                                                                                                                                                                            | número entero   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |             |                                                                                                                                                                                           |
-| firmantes_tx                           | Las claves públicas de los firmantes que autorizaron la transacción. Este campo lista todos los signatarios que validaron y aprobaron la transacción, asegurando que cumpla con los umbrales de autorización requeridos                                                                                                                                                 | cadena          |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |             |                                                                                                                                                                                           |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/liquidity-pools.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/liquidity-pools.mdx
deleted file mode 100644
index 94072d76fe..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/liquidity-pools.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Fondos de Liquidez
-sidebar_position: 50
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                  |
-| --------------------- | -------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | liquidity_pool_id, closed_at                                                                                   |
-| Campo(s) de Partición | batch_run_date (partición de MES)                                                                              |
-| Campo(s) Agrupado(s)  | liquidity_pool_id, asset_a_id, asset_b_id, last_modified_ledger                                                |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.liquidity_pools) |
-
-## Detalles de la Columna
-
-| Nombre                           | Descripción                                                                                                                                                                                                                                                                               | Tipo de Dato    | Valores del Dominio                                                                                                                                                                                                | ¿Requerido? | Notas                                                                                                                                                                                                                                                                                                                        |
-| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| liquidity_pool_id                | Identificador único para un fondo de liquidez. No pueden existir fondos duplicados para el mismo par de activos. Una vez que se ha creado un fondo para el par de activos, no se puede crear otro.                                                                                        | cadena          |                                                                                                                                                                                                                    | Sí          | Hay un buen manual sobre AMMs [aquí](https://developers.stellar.org/docs/learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools#liquidity-pools)                                                                                                                                                                  |
-| tipo                             | El mecanismo que calcula los precios y la división de acciones para el fondo. Con el despliegue inicial de AMM, el único tipo de fondo de liquidez que se puede crear es un fondo de producto constante                                                                                   | cadena          | producto_constante                                                                                                                                                                                                 | Sí          | Para más información sobre precios y cálculos de depósitos, lee [Cap-38.](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md)                                                                                                                                                                          |
-| tarifa                           | El número de puntos básicos cargados como un porcentaje de la transacción para completar la operación. Las tarifas obtenidas en todas las operaciones se dividen entre los accionistas del fondo y se distribuyen como un incentivo para mantener fondos en los mismos                    | entero          | 30                                                                                                                                                                                                                 | Sí          | Las tarifas se distribuyen inmediatamente a las cuentas al completarse la operación. No hay un calendario para la distribución de tarifas                                                                                                                                                                                    |
-| trustline_count                  | Número total de cuentas con líneas de confianza autorizadas al fondo. Para crear una línea de confianza, una cuenta debe confiar en ambos activos base antes de confiar en un fondo con el par de activos                                                                                 | entero          |                                                                                                                                                                                                                    | Sí          | Si el emisor de A o B revoca la autorización en la línea de confianza, la cuenta se retirará automáticamente de cada fondo de liquidez que contenga ese activo y esas líneas de confianza del fondo serán eliminadas.                                                                                                        |
-| pool_share_count                 | La participación en un fondo de liquidez se representa mediante una acción del fondo. El número total de acciones de fondo se calcula mediante una fórmula de producto constante y es un número arbitrario que representa la cantidad de participación en el fondo.                       | flotante        |                                                                                                                                                                                                                    | Sí          | Las acciones no son transferibles; la única forma de aumentar el número de acciones de fondo es depositar en un fondo de liquidez. Por el contrario, disminuir las acciones en el fondo solo puede lograrse a través de una operación de retiro. Las acciones no pueden ser enviadas en pagos o vendidas utilizando ofertas. |
-| asset_a_type                     | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                              | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                        | Sí          |                                                                                                                                                                                                                                                                                                                              |
-| asset_a_code                     | El código de representación de 4 o 12 caracteres del activo de uno de los dos pares de activos en un fondo de liquidez                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                              |
-| asset_a_issuer                   | La dirección de cuenta del emisor original del activo que creó uno de los dos pares de activos en el fondo de liquidez                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                              |
-| asset_a_amount                   | El número bruto de tokens bloqueados en el fondo para uno de los dos pares de activos en el fondo de liquidez                                                                                                                                                                             | flotante        |                                                                                                                                                                                                                    | Sí          | El monto es una mejor representación de la liquidez en el fondo en comparación con el conteo de acciones del fondo.                                                                                                                                                                                                          |
-| asset_b_type                     | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                              | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                        | Sí          |                                                                                                                                                                                                                                                                                                                              |
-| asset_b_code                     | El código de representación de 4 o 12 caracteres del activo de uno de los dos pares de activos en un fondo de liquidez                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                              |
-| asset_b_issuer                   | La dirección de cuenta del emisor original del activo que creó uno de los dos pares de activos en el fondo de liquidez                                                                                                                                                                    | cadena          |                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                              |
-| asset_b_amount                   | El número bruto de tokens bloqueados en el fondo para uno de los dos pares de activos en el fondo de liquidez                                                                                                                                                                             | flotante        |                                                                                                                                                                                                                    | Sí          | El monto es una mejor representación de la liquidez en el fondo en comparación con el conteo de acciones del fondo.                                                                                                                                                                                                          |
-| last_modified_ledger             | El número de secuencia del libro mayor cuando la entrada del libro mayor (este firmante único para la cuenta) fue modificada. Las eliminaciones no cuentan como una modificación y reportarán el número de secuencia de modificación anterior                                             | entero          |                                                                                                                                                                                                                    | Sí          |                                                                                                                                                                                                                                                                                                                              |
-| cambio_de_entrada_de_libro_mayor | Código que describe el tipo de cambio de entrada de libro mayor que se aplicó a la entrada del libro mayor.                                                                                                                                                                               | entero          | <ul><li>0 - Entrada de Libro Mayor Creada</li><li>1 - Entrada de Libro Mayor Actualizada</li><li>2 - Entrada de Libro Mayor Eliminada</li><li>3 - Estado de Entrada de Libro Mayor (valor de la entrada)</li></ul> | Sí          | Los tipos de cambio de entrada válidos son 0, 1 y 2 para entradas de libro mayor de tipo `liquidity_pools`.                                                                                                                                                                                                                  |
-| eliminado                        | Indica si la entrada del libro mayor (fondo de liquidez) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede ser recuperada. Los fondos de liquidez son eliminados una vez que se retiran todas las acciones del fondo                                                 | booleano        |                                                                                                                                                                                                                    | Sí          |                                                                                                                                                                                                                                                                                                                              |
-| batch_id                         | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de "scheduled\_\_\<batch_end_date>-\<dag_alias>". Los ids de batch son únicos para el batch y ayudan con las capacidades de monitoreo y reejecución                                               | cadena          |                                                                                                                                                                                                                    | Sí          |                                                                                                                                                                                                                                                                                                                              |
-| batch_run_date                   | La fecha de inicio para el intervalo del batch. Cuando se toma con la fecha en el batch_id, la fecha representa el intervalo de libros mayores procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un libro mayor.                                    | datetime        |                                                                                                                                                                                                                    | Sí          | La tabla está particionada por batch_run_date. Se recomienda incluir siempre la fecha de ejecución del batch en el filtro si es posible para ayudar a reducir el costo de la consulta.                                                                                                                                       |
-| batch_insert_ts                  | La marca de tiempo en UTC cuando se insertó un batch de registros en la base de datos. Este campo puede ayudar a identificar si un batch se ejecutó en tiempo real o como parte de un reabastecimiento                                                                                    | marca de tiempo |                                                                                                                                                                                                                    | Sí          |                                                                                                                                                                                                                                                                                                                              |
-| asset_a_id                       | Identificador único para asset_a_code, asset_a_issuer                                                                                                                                                                                                                                     | entero          |                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                              |
-| asset_b_id                       | Identificador único para asset_b_code, asset_b_issuer                                                                                                                                                                                                                                     | entero          |                                                                                                                                                                                                                    | No          |                                                                                                                                                                                                                                                                                                                              |
-| closed_at                        | Marca de tiempo en UTC cuando este libro mayor se cerró y se comprometió a la red. Se espera que los libros mayores se cierren ~cada 5 segundos                                                                                                                                           | marca de tiempo |                                                                                                                                                                                                                    | Sí          |                                                                                                                                                                                                                                                                                                                              |
-| ledger_sequence                  | El número de secuencia de este libro mayor. Representa el orden del libro mayor dentro de la blockchain de Stellar. Cada libro mayor tiene un número de secuencia único que se incrementa con cada nuevo libro mayor, asegurando que los libros mayores se procesen en el orden correcto. | entero          |                                                                                                                                                                                                                    | Sí          |                                                                                                                                                                                                                                                                                                                              |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/offers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/offers.mdx
deleted file mode 100644
index ec17440fb4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/offers.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Ofertas
-sidebar_position: 60
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                  |
-| --------------------- | -------------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | offer_id, closed_at                                                                                            |
-| Campo(s) de partición | batch_run_date (partición por MES)                                                                             |
-| Campo(s) agrupado(s)  | selling_asset_id, buying_asset_id, last_modified_ledger                                                        |
-| Documentación         | [documentos de dbt](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.offers) |
-
-## Detalles de la columna
-
-| Nombre               | Descripción                                                                                                                                                                                                                                                                            | Tipo de dato    | Valores de dominio                                                                                                                                                                                                  | ¿Requerido? | Notas                                                                                                                                                                    |
-| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| seller_id            | La dirección de cuenta que está haciendo esta oferta                                                                                                                                                                                                                                   | cadena          |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| offer_id             | El identificador único para esta oferta                                                                                                                                                                                                                                                | entero          |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| selling_asset_type   | El identificador para el tipo de código de activo, puede ser alfanumérico de 4 o 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                      | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                         | Sí          |                                                                                                                                                                          |
-| selling_asset_code   | El código de 4 o 12 caracteres que representa el activo ofrecido para la venta                                                                                                                                                                                                         | cadena          |                                                                                                                                                                                                                     | No          |                                                                                                                                                                          |
-| selling_asset_issuer | La dirección de cuenta del emisor original del activo que acuñó el activo que se venderá a cambio de otro activo                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                     | No          |                                                                                                                                                                          |
-| buying_asset_type    | El identificador para el tipo de código de activo, puede ser alfanumérico de 4 o 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                      | cadena          | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                                         | Sí          |                                                                                                                                                                          |
-| buying_asset_code    | El código de 4 o 12 caracteres que representa el activo deseado a comprar                                                                                                                                                                                                              | cadena          |                                                                                                                                                                                                                     | No          |                                                                                                                                                                          |
-| buying_asset_issuer  | La dirección de cuenta del emisor original del activo que acuñó el activo que se comprará a cambio de un activo actualmente en posesión                                                                                                                                                | cadena          |                                                                                                                                                                                                                     | No          |                                                                                                                                                                          |
-| cantidad             | La cantidad de activos que la cuenta que hace esta oferta está dispuesta a vender                                                                                                                                                                                                      | flotante        |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| pricen               | El numerador de la representación precisa del precio de compra y venta de los activos en oferta (La cantidad de compra deseada)                                                                                                                                                        | entero          |                                                                                                                                                                                                                     | Sí          | Si una oferta quiere vender 10 XLM a cambio de 1 USD, el numerador será 1.                                                                                               |
-| priced               | El denominador de la representación precisa del precio de compra y venta de los activos en oferta (La cantidad de venta ofrecida)                                                                                                                                                      | entero          |                                                                                                                                                                                                                     | Sí          | Si una oferta quiere vender 10 XLM a cambio de 1 USD, el denominador será 10.                                                                                            |
-| precio               | Cuántas unidades de compra se necesitan para obtener 1 unidad de venta. Este número es la forma decimal de pricen / priced                                                                                                                                                             | flotante        |                                                                                                                                                                                                                     | Sí          | Si una oferta quiere vender 10 XLM a cambio de 1 USD, el precio será 0,1                                                                                                 |
-| flags                | Denota la habilitación/deshabilitación de ciertos privilegios del emisor de activos                                                                                                                                                                                                    | entero          | <ul><li>0 - Ninguno, Predeterminado</li><li>1 - Pasivo (oferta con esta bandera no actuará y tomará una oferta inversa de igual precio)</li></ul>                                                                   | Sí          |                                                                                                                                                                          |
-| last_modified_ledger | El número de secuencia del libro mayor cuando se modificó la entrada del libro mayor (este firmante único para la cuenta). Las eliminaciones no cuentan como una modificación y reportarán el número de secuencia de modificación anterior                                             | entero          |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| ledger_entry_change  | Código que describe el tipo de cambio de entrada del libro mayor que se aplicó a la entrada del libro mayor.                                                                                                                                                                           | entero          | <ul><li>0 - Entrada de libro mayor creada</li><li>1 - Entrada de libro mayor actualizada</li><li>2 - Entrada de libro mayor eliminada</li><li>3 - Estado de entrada del libro mayor (valor de la entrada)</li></ul> | Sí          | Los tipos de cambio de entrada válidos son 0, 1 y 2 para entradas del libro mayor de tipo `offers`.                                                                      |
-| eliminado            | Indica si la entrada del libro mayor (offer id) ha sido eliminada o no. Una vez que una entrada es eliminada, no puede ser recuperada                                                                                                                                                  | booleano        |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| closed_at            | Marca de tiempo en UTC cuando este libro mayor se cerró y se comprometió a la red. Se espera que los libros mayores se cierren aproximadamente cada 5 segundos                                                                                                                         | marca de tiempo |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| ledger_sequence      | El número de secuencia de este libro mayor. Representa el orden del libro mayor dentro de la blockchain Stellar. Cada libro mayor tiene un número de secuencia único que se incrementa con cada nuevo libro mayor, asegurando que los libros mayores se procesen en el orden correcto. | entero          |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| sponsor              | La dirección de cuenta que está patrocinando las reservas básicas para la oferta                                                                                                                                                                                                       | cadena          |                                                                                                                                                                                                                     | No          |                                                                                                                                                                          |
-| batch_id             | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los ids de lote son únicos para el lote y ayudan con las capacidades de monitoreo y reejecución                                                  | cadena          |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| batch_run_date       | La fecha de inicio del intervalo de lotes. Cuando se toma junto con la fecha en el batch_id, la fecha representa el intervalo de libros mayores procesados. La fecha de ejecución del lote se puede ver como un proxy de closed_at para un libro mayor.                                | fecha y hora    |                                                                                                                                                                                                                     | Sí          | La tabla está particionada por batch_run_date. Se recomienda incluir siempre el batch_run_date en el filtro si es posible para ayudar a reducir el costo de la consulta. |
-| batch_insert_ts      | La marca de tiempo en UTC cuando se insertó un lote de registros en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un retroceso                                                                                          | marca de tiempo |                                                                                                                                                                                                                     | Sí          |                                                                                                                                                                          |
-| selling_asset_id     | Identificador único para selling_asset_code, selling_asset_issuer                                                                                                                                                                                                                      | entero          |                                                                                                                                                                                                                     | No          |                                                                                                                                                                          |
-| buying_asset_id      | Identificador único para buying_asset_code, buying_asset_issuer                                                                                                                                                                                                                        | entero          |                                                                                                                                                                                                                     | No          |                                                                                                                                                                          |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/README.mdx
deleted file mode 100644
index 212430526c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/README.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Plata 🥈
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Datos decodificados, transformados y filtrados. Estas tablas transforman las tablas bronce en tablas más fáciles de usar al unir y aplanar tablas y filtrar información para casos de uso específicos.
-
-## Cuándo usar
-
-Estas tablas son ideales para una experiencia más curada mientras se necesita buscar y filtrar para casos de uso específicos, como información sobre un contrato específico.
-
-Un ejemplo es obtener eventos relevantes de Stellar para calcular el suministro circulante usando la tabla `token_transfers_raw`. En teoría, puedes obtener la misma información de la tabla bronce `history_contract_events`, pero la tabla `token_transfers_raw` ya ha procesado, filtrado y aplanado los eventos relevantes para eventos SEP-41 y operaciones clásicas.
-
-## Dimensiones de Cambio Lento (SCD Tipo 2)
-
-Algunas tablas silver están modeladas como tablas [SCD Tipo 2](https://github.com/stellar/stellar-dbt-public/blob/master/docs/snapshot.md). Esto significa que rastrean el historial completo de cambios de un registro en el tiempo manteniendo múltiples versiones con rangos `valid_from` / `valid_to`.
-
-Estas tablas son especialmente útiles para responder preguntas históricas como:
-
-- ¿Cuál era el estado de un contrato en un momento dado?
-- ¿Cómo evolucionó una cuenta, una trustline o un balance a lo largo de diferentes períodos?
-- ¿Qué Fondos de Liquidez estaban activos en una fecha determinada y cómo cambiaron sus propiedades con el tiempo?
-
-> **_NOTA:_** Frecuencia de snapshot diaria: Los snapshots se ejecutan diariamente, lo que significa que capturan cambios interdiarios, pero no múltiples cambios que ocurren dentro del mismo día.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.mdx
deleted file mode 100644
index 5da82c7b3d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/account-signers-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Firmantes de Cuenta Actuales
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                         |
-| --------------------- | ----------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | account_id, signer, closed_at                                                                         |
-| Campo(s) de Partición | batch_run_date (partición MES)                                                                        |
-| Campo(s) Clustered    | account_id, signer, last_modified_ledger                                                              |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.account_signers_current) |
-
-## Detalles de Columnas
-
-Los detalles de columnas son equivalentes a la tabla bronze [Account Signers](../bronze/account-signers.mdx). Filtra solo la información del estado más reciente.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.mdx
deleted file mode 100644
index 0529afaf2e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Cuentas Actuales
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad                | Configuración                                                                                  |
-| ------------------------ | ---------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)     | account_id, closed_at                                                                          |
-| Campo(s) de Partición    | batch_run_date (partición MENSUAL)                                                             |
-| Campo(s) Clusterizado(s) | account_id, last_modified_ledger                                                               |
-| Documentación            | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.accounts_current) |
-
-## Detalles de las Columnas
-
-Los detalles de las columnas son equivalentes a la tabla bronze [Accounts](../bronze/accounts.mdx). Filtra para mostrar solo la información del estado más reciente.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.mdx
deleted file mode 100644
index 48213c15ef..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/accounts-snapshot.mdx
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: Instantánea de Cuentas
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                   |
-| --------------------- | ----------------------------------------------------------------------------------------------- |
-| Clave Natural         | account_id, valid_from                                                                          |
-| Campo(s) de partición | valid_to (partición MENSUAL)                                                                    |
-| Campo(s) agrupados    | account_id                                                                                      |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.accounts_snapshot) |
-
-## Detalles de Columnas
-
-| Nombre                | Descripción                                                                                                                                                                                                                             | Tipo de Datos | Valores del Dominio                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | ¿Requerido? | Notas                                                                                                                                                                                                                                |
-| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| account_id            | El identificador único de la cuenta.                                                                                                                                                                                                    | STRING        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          |                                                                                                                                                                                                                                      |
-| balance               | La cantidad de unidades de XLM que posee la cuenta.                                                                                                                                                                                     | FLOAT         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | La tabla `accounts` solo reporta saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`.                                                                                                    |
-| buying_liabilities    | La suma de todas las ofertas de compra que posee esta cuenta solo para XLM.                                                                                                                                                             | FLOAT         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | La tabla `accounts` solo reporta saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`. Para ofertas de compra, la cuenta debe poseer la cantidad de activo para completar la transacción. |
-| selling_liabilities   | La suma de todas las ofertas de venta que posee esta cuenta solo para XLM.                                                                                                                                                              | FLOAT         |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | La tabla `accounts` solo reporta saldos monetarios para XLM. Cualquier otra clase de activo se informa en la tabla `trust_lines`.                                                                                                    |
-| sequence_number       | El número de secuencia actual de la cuenta. El número de secuencia controla las operaciones aplicadas a una cuenta. Las operaciones deben enviar un número de secuencia único incrementado en 1.                                        | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Clave Natural. Campo Requerido.                                                                                                                                                                                                      |
-| num_subentries        | El número total de entradas ledger vinculadas a esta cuenta. Las entradas ledger incluyen: trustlines, ofertas, signatarios y entradas de datos.                                                                                        | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Cada entrada en un ledger ocupa espacio, que es costoso de almacenar. El saldo mínimo se calcula como (2 + num_subentries - num_sponsoring + num_sponsored) \* 0.5XLM.                                                               |
-| inflation_destination | Obsoleto: La dirección de la cuenta para recibir un pago de inflación cuando se desembolsa.                                                                                                                                             | STRING        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | La inflación se discontinuó en 2019 por voto de los validadores.                                                                                                                                                                     |
-| flags                 | Indica la habilitación/deshabilitación de ciertos privilegios del emisor del activo.                                                                                                                                                    | INTEGER       | <ul><li>0 - Ninguno, por defecto</li><li>1 - Autenticación requerida (todas las trustlines por defecto no son confiables y requieren establecimiento manual de confianza)</li><li>2 - Autenticación revocable (permite revocar trustlines si la cuenta ya no confía en el activo)</li><li>4 - Autenticación inmutable (todas las flags de autenticación son solo lectura cuando se establecen)</li><li>8 - Autenticación con recuperación habilitada (el activo puede ser recuperado del usuario)</li></ul> | Sí          | Las flags pueden tener valores: 0=Ninguno, 1=Autenticación requerida, 2=Autenticación revocable, 4=Autenticación inmutable, 8=Autenticación con recuperación habilitada.                                                             |
-| home_domain           | URL del dominio principal vinculado a la billetera.                                                                                                                                                                                     | STRING        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          |                                                                                                                                                                                                                                      |
-| master_weight         | El peso de la clave maestra, que es la llave privada de esta cuenta.                                                                                                                                                                    | INTEGER       | Enteros desde 1 hasta 255                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Sí          | Si la clave maestra = 0, la cuenta está bloqueada.                                                                                                                                                                                   |
-| threshold_low         | La suma del peso de todas las firmas requeridas para operaciones de umbral bajo.                                                                                                                                                        | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Bajo: Permitir confianza, establecer flags de trust line, incrementar secuencia, reclamar saldo reclutable.                                                                                                                          |
-| threshold_medium      | La suma del peso de todas las firmas requeridas para operaciones de umbral medio.                                                                                                                                                       | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Medio: Todo lo demás.                                                                                                                                                                                                                |
-| threshold_high        | La suma del peso de todas las firmas requeridas para operaciones de umbral alto.                                                                                                                                                        | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Alto: Fusión de cuentas, establecer opciones.                                                                                                                                                                                        |
-| last_modified_ledger  | El número de secuencia ledger cuando la entrada ledger fue modificada por última vez.                                                                                                                                                   | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Clave Natural. Campo agrupado. La eliminación no cuenta como modificación.                                                                                                                                                           |
-| ledger_entry_change   | Código que describe el tipo de cambio aplicado a la entrada ledger.                                                                                                                                                                     | INTEGER       | <ul><li>0 - Entrada ledger creada</li><li>1 - Entrada ledger actualizada</li><li>2 - Entrada ledger eliminada</li><li>3 - Estado de entrada ledger (valor de la entrada)</li></ul>                                                                                                                                                                                                                                                                                                                          | Sí          | Valores: 0=Creada, 1=Actualizada (no válido para saldos reclutables), 2=Eliminada.                                                                                                                                                   |
-| deleted               | Indica si la entrada ledger ha sido eliminada.                                                                                                                                                                                          | BOOLEAN       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Una vez eliminada, no puede recuperarse.                                                                                                                                                                                             |
-| sponsor               | La dirección de la cuenta del patrocinador que paga las reservas para esta entrada ledger.                                                                                                                                              | STRING        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          | Los patrocinadores pueden ser cuentas, firmantes, saldos reclutables o líneas de confianza.                                                                                                                                          |
-| num_sponsored         | El número de reservas patrocinadas para esta cuenta.                                                                                                                                                                                    | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          | Por defecto es 0.                                                                                                                                                                                                                    |
-| num_sponsoring        | El número de reservas patrocinadas por esta cuenta.                                                                                                                                                                                     | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          | Por defecto es 0.                                                                                                                                                                                                                    |
-| sequence_ledger       | El número ledger sin signo de 32 bits que indica la antigüedad del número de secuencia.                                                                                                                                                 | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          | Refleja la última vez que una cuenta tocó su número de secuencia.                                                                                                                                                                    |
-| sequence_time         |                                                                                                                                                                                                                                         | TIMESTAMP     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          |                                                                                                                                                                                                                                      |
-| batch_id              | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los ids de lote son únicos para el lote y ayudan con la supervisión y capacidades de reejecución. | string        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          |                                                                                                                                                                                                                                      |
-| batch_run_date        | La fecha de inicio para el intervalo del lote.                                                                                                                                                                                          | DATETIME      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Representa el intervalo de ledgers procesados.                                                                                                                                                                                       |
-| closed_at             | Marca de tiempo en UTC cuando este ledger se cerró y confirmó.                                                                                                                                                                          | TIMESTAMP     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Los ledgers cierran aproximadamente cada 5 segundos.                                                                                                                                                                                 |
-| ledger_sequence       | El número de secuencia de este ledger.                                                                                                                                                                                                  | INTEGER       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Campo agrupado. Único por ledger.                                                                                                                                                                                                    |
-| batch_insert_ts       | La marca temporal en UTC cuando un lote de registros se insertó en la base de datos.                                                                                                                                                    | TIMESTAMP     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Útil para ingeniería de datos, no para análisis ad hoc.                                                                                                                                                                              |
-| airflow_start_ts      | La marca temporal cuando inicia el trabajo airflow.                                                                                                                                                                                     | STRING        |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Se usa para detectar trabajos de llenado histórico.                                                                                                                                                                                  |
-| valid_from            | La marca temporal cuando esta fila de imagen fue insertada por primera vez y se volvió efectiva.                                                                                                                                        | TIMESTAMP     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Sí          | Ayuda a rastrear cambios en el tiempo.                                                                                                                                                                                               |
-| valid_to              | La marca temporal cuando esta fila deja de ser válida.                                                                                                                                                                                  | TIMESTAMP     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | No          | Si es nulo, la configuración está actualmente activa.                                                                                                                                                                                |
-
-## Ejemplos de Preguntas Comerciales
-
-1. Consulta en un punto en el tiempo (saldo al momento)
-
-```sql
-SELECT account_id, balance
-FROM `crypto-stellar.snapshots.accounts_snapshot`
-WHERE account_id = 'ACC123'
-  DATE('2025-01-15') BETWEEN DATE(valid_from) AND COALESCE(DATE(valid_to), '9999-12-31')
-LIMIT 100
-```
-
-2. Instantánea activa (solo registros actuales)
-
-```sql
-SELECT account_id, balance, home_domain
-FROM `crypto-stellar.snapshots.accounts_snapshot`
-WHERE valid_to IS NULL
-LIMIT 100
-```
-
-3. Cambios en febrero de 2025 (poda de particiones)
-
-```sql
-SELECT account_id, COUNT(*) AS num_changes
-FROM `crypto-stellar.snapshots.accounts_snapshot`
-WHERE DATE_TRUNC(valid_to, MONTH) = '2025-02-01'
-GROUP BY account_id
-LIMIT 100
-```
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.mdx
deleted file mode 100644
index a2638866c0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/claimable-balances-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Saldos Reclamables Actuales
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                            |
-| --------------------- | -------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | balance_id, closed_at                                                                                    |
-| Campo(s) de Partición | batch_run_date (partición MES)                                                                           |
-| Campo(s) Agrupado(s)  | asset_id, last_modified_ledger                                                                           |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.claimable_balances_current) |
-
-## Detalles de la Columna
-
-Los detalles de la columna son equivalentes a la tabla bronze de [Claimable Balances](../bronze/claimable-balances.mdx). Filtra solo la información del estado más reciente.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.mdx
deleted file mode 100644
index 28e8335a1d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/config-settings-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Configuración Actual de Parámetros
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                         |
-| --------------------- | ----------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | config_setting_id, closed_at                                                                          |
-| Campo(s) de Partición | closed_at (partición MENSUAL)                                                                         |
-| Campo(s) Agrupado(s)  | last_modified_ledger                                                                                  |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.config_settings_current) |
-
-## Detalles de Columnas
-
-Los detalles de las columnas son equivalentes a la tabla bronce [Configuración de Parámetros](../bronze/config-settings.mdx). Filtra solo la información del estado más reciente.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.mdx
deleted file mode 100644
index d506eef577..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-code-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Contrato Código Actual
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                       |
-| --------------------- | --------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | contract_code_hash, closed_at                                                                       |
-| Campo(s) de Partición | closed_at (partición MES)                                                                           |
-| Campo(s) Clustered    | last_modified_ledger, contract_code_hash                                                            |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.contract_code_current) |
-
-## Detalles de la Columna
-
-Los detalles de la columna son equivalentes a la tabla bronze [Contract Code](../bronze/contract-code.mdx). Filtra solo para la información del estado más reciente.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.mdx
deleted file mode 100644
index c7317461df..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Datos Actuales del Contrato
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                       |
-| --------------------- | --------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | ledger_key_hash, closed_at                                                                          |
-| Campo(s) de Partición | closed_at (partición MENSUAL)                                                                       |
-| Campo(s) Agrupado(s)  | last_modified_ledger, contract_id                                                                   |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.contract_data_current) |
-
-## Detalles de las Columnas
-
-Los detalles de las columnas son equivalentes a la tabla bronze de [Datos del Contrato](../bronze/contract-data.mdx). Filtra solo la información más reciente del estado.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.mdx
deleted file mode 100644
index 4c1c6f7bd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/contract-data-snapshot.mdx
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Imagen de Datos del Contrato
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                        |
-| --------------------- | ---------------------------------------------------------------------------------------------------- |
-| Clave Natural(s)      | contract_id, ledger_key_hash, valid_from                                                             |
-| Campo(s) de Partición | valid_to (partición MENSUAL)                                                                         |
-| Campo(s) de Clúster   | contract_id, ledger_key_hash                                                                         |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.contract_data_snapshot) |
-
-## Detalles de las Columnas
-
-| Nombre                    | Descripción                                                                                                                                                                                                                           | Tipo de Dato    | Valores del Dominio                                                                                                                                                                            | ¿Requerido? | Notas                                                                                                                           |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| contract_id               | ID del contrato Soroban.                                                                                                                                                                                                              | CADENA          |                                                                                                                                                                                                | Sí          |                                                                                                                                 |
-| contract_key_type         | Tipo de clave del contrato que es un ScVal.                                                                                                                                                                                           | CADENA          | ScValTypeScvContractInstance, ScValTypeScvLedgerKeyContractInstance, ScValTypeScvLedgerKeyNonce                                                                                                | No          |                                                                                                                                 |
-| contract_durability       | El contrato puede ser temporal o persistente.                                                                                                                                                                                         | CADENA          |                                                                                                                                                                                                | No          |                                                                                                                                 |
-| asset_code                | La representación en código de 4 o 12 caracteres del activo en la red.                                                                                                                                                                | CADENA          |                                                                                                                                                                                                | No          | Los códigos de activos no garantizan unicidad. La combinación de código de activo, emisor y tipo representa un activo distinto. |
-| emisor_activo             | La dirección de la cuenta del emisor original del activo que creó el activo.                                                                                                                                                          | CADENA          |                                                                                                                                                                                                | No          |                                                                                                                                 |
-| tipo_activo               | El identificador para el tipo de código de activo, puede ser alfanumérico (4 o 12 caracteres) o el activo nativo de la red, XLM.                                                                                                      | CADENA          | nativo, alfanum4, alfanum12                                                                                                                                                                    | No          | XLM es el activo nativo. XLM no tiene código de activo ni emisor y se muestra con tipo de activo = 'nativo'.                    |
-| titular_balance           | La dirección/cuenta que mantiene el saldo del activo en datos de contrato.                                                                                                                                                            | CADENA          |                                                                                                                                                                                                | No          |                                                                                                                                 |
-| saldo                     | El número de unidades de XLM que posee la cuenta.                                                                                                                                                                                     | CADENA          |                                                                                                                                                                                                | No          | La tabla `accounts` solo reporta saldos para XLM. Cualquier otra clase de activo se reporta en `trust_lines`.                   |
-| last_modified_ledger      | El número de secuencia del ledger cuando la entrada fue modificada por última vez.                                                                                                                                                    | ENTERO          |                                                                                                                                                                                                | Sí          | Clave Natural. Campo de Clúster. La eliminación no cuenta como modificación.                                                    |
-| cambio_entrada_ledger     | Código que describe el tipo de cambio de entrada en el ledger aplicado.                                                                                                                                                               | ENTERO          | <ul><li>0 - Entrada de Ledger Creada</li><li>1 - Entrada de Ledger Actualizada</li><li>2 - Entrada de Ledger Eliminada</li><li>3 - Estado de Entrada de Ledger (valor de la entrada)</li></ul> | Sí          | No todas las entradas pueden ser actualizadas. Actualizaciones no válidas para saldos reclamables.                              |
-| secuencia_ledger          |                                                                                                                                                                                                                                       | ENTERO          |                                                                                                                                                                                                | Sí          |                                                                                                                                 |
-| hash_clave_ledger         |                                                                                                                                                                                                                                       | CADENA          |                                                                                                                                                                                                | Sí          |                                                                                                                                 |
-| clave                     | La clave codificada usada para identificar un dato específico del contrato. Tiene dos componentes: tipo y valor.                                                                                                                      | JSON            |                                                                                                                                                                                                | No          |                                                                                                                                 |
-| clave_decodificada        | La versión legible/humana de la clave decodificada.                                                                                                                                                                                   | JSON            |                                                                                                                                                                                                | No          |                                                                                                                                 |
-| valor                     | El valor codificado asociado con la clave en los datos del contrato. Tiene dos componentes: tipo y valor.                                                                                                                             | JSON            |                                                                                                                                                                                                | No          |                                                                                                                                 |
-| valor_decodificado        | La versión legible/humana del valor decodificado.                                                                                                                                                                                     | JSON            |                                                                                                                                                                                                | No          |                                                                                                                                 |
-| contract_data_xdr         | La codificación XDR (External Data Representation) de los datos del contrato.                                                                                                                                                         | CADENA          |                                                                                                                                                                                                | No          | XDR asegura interoperabilidad entre sistemas.                                                                                   |
-| cerrado_en                | Marca temporal en UTC cuando este ledger se cerró y confirmó.                                                                                                                                                                         | MARCA DE TIEMPO |                                                                                                                                                                                                | Sí          | Los ledgers se cierran aproximadamente cada 5 segundos.                                                                         |
-| eliminado                 | Indica si la entrada del ledger ha sido eliminada.                                                                                                                                                                                    | BOOLEANO        |                                                                                                                                                                                                | Sí          | Una vez eliminada, no puede recuperarse. Se mantiene el historial.                                                              |
-| id_batch                  | Representación en cadena del id de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los id de batch son únicos para el batch y ayudan en el monitoreo y capacidades de reejecución. | cadena          |                                                                                                                                                                                                | Sí          |                                                                                                                                 |
-| fecha_ejecución_batch     | La fecha de inicio para el intervalo del batch.                                                                                                                                                                                       | FECHA Y HORA    |                                                                                                                                                                                                | Sí          | Representa cerrado_en para un ledger.                                                                                           |
-| timestamp_inserción_batch | Marca temporal en UTC cuando un lote de registros fue insertado.                                                                                                                                                                      | MARCA DE TIEMPO |                                                                                                                                                                                                | Sí          | Para propósitos de ingeniería de datos, no para análisis ad hoc.                                                                |
-| airflow_inicio_ts         | Marca temporal cuando comienza el trabajo de airflow.                                                                                                                                                                                 | CADENA          |                                                                                                                                                                                                | No          | Se usa para detectar trabajos de relleno.                                                                                       |
-| válido_desde              | Marca temporal cuando esta fila de imagen fue insertada por primera vez y se volvió efectiva.                                                                                                                                         | MARCA DE TIEMPO |                                                                                                                                                                                                | Sí          | Rastrea cambios a través del tiempo.                                                                                            |
-| válido_hasta              | Marca temporal cuando esta fila ya no es válida.                                                                                                                                                                                      | MARCA DE TIEMPO |                                                                                                                                                                                                | No          | Si es nulo, la configuración está actualmente activa.                                                                           |
-
-## Ejemplos de preguntas de negocio
-
-1. Consulta puntual (saldo/valor a una fecha dada)
-
-```sql
-SELECT contract_id, ledger_key_hash, val_decoded
-FROM `crypto-stellar.snapshots.contract_data_snapshot`
-WHERE contract_id = 'C123'
-  AND ledger_key_hash = 'abc123'
-  DATE('2025-02-10') BETWEEN DATE(valid_from) AND COALESCE(DATE(valid_to), '9999-12-31')
-LIMIT 100
-```
-
-2. Todos los contratos activos (solo estado más reciente)
-
-```sql
-SELECT contract_id, ledger_key_hash, val_decoded, balance, contract_durability
-FROM `crypto-stellar.snapshots.contract_data_snapshot`
-WHERE valid_to IS NULL
-LIMIT 100
-```
-
-3. Actualizaciones recientes
-
-```sql
-SELECT contract_id, ledger_key_hash, closed_at, ledger_entry_change
-FROM `crypto-stellar.snapshots.contract_data_snapshot`
-WHERE closed_at >= TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 2 DAY)
-LIMIT 100
-```
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.mdx
deleted file mode 100644
index 026a607831..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations-soroban.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Operaciones de Historial Enriquecido Soroban
-sidebar_position: 151
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                                     |
-| --------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | op_id                                                                                                             |
-| Campo(s) de Partición | closed_at (partición MES)                                                                                         |
-| Campo(s) Agrupado(s)  | ledger_sequence, transaction_id, op_account_id, type                                                              |
-| Documentación         | [dbt_docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.enriched_history_operations_soroban) |
-
-## Detalles de Columna
-
-Los detalles de la columna son equivalentes a la tabla plateada [Operaciones de Historial Enriquecido](./enriched-history-operations.mdx). Filtra solo los tipos de operación 24, 25 y 26
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.mdx
deleted file mode 100644
index 1d479542f7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/enriched-history-operations.mdx
+++ /dev/null
@@ -1,103 +0,0 @@
----
-title: Operaciones de Historial Enriquecido
-sidebar_position: 150
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                             |
-| --------------------- | --------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | op_id                                                                                                     |
-| Campo(s) de Partición | closed_at (partición MES)                                                                                 |
-| Campo(s) Agrupado(s)  | ledger_sequence, transaction_id, op_account_id, type                                                      |
-| Documentación         | [dbt_docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.enriched_history_operations) |
-
-## Detalles de Columnas
-
-| Nombre                            | Descripción                                                                                                                                                                                                                                                                                      | Tipo de Datos  | Valores del Dominio                                                                       | ¿Requerido? | Tabla de Origen    | Notas                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- | ----------------------------------------------------------------------------------------- | ----------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| account                           | La nueva dirección de la cuenta resultante que se crea y financia (operación de creación) La dirección de la cuenta que se elimina y se fusiona en otra cuenta (operación de fusión)                                                                                                             | string         |                                                                                           |             | history_operations | Parte del objeto `details` original en la tabla history_operations                                                                                                                                                                                                                                                                                                                                                          |
-| amount                            | Representación en coma flotante de la cantidad de un activo enviado/ofrecido/etc.                                                                                                                                                                                                                | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| asset_code                        | La representación del código del activo en la red de 4 o 12 caracteres                                                                                                                                                                                                                           | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| asset_issuer                      | La dirección de la cuenta del emisor original que creó el activo                                                                                                                                                                                                                                 | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| asset_type                        | El identificador para el tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                    | string         | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>               |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| authorize                         | Indica si la trustline está autorizada. 0 si la cuenta no está autorizada a transaccionar con el activo de ninguna manera. 1 si la cuenta está autorizada a transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones.        | boolean        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| balance_id                        | El identificador único del saldo reclamable. El id está compuesto por un código de tipo de 8 caracteres + hash SHA-256 del id de la operación histórica que creó el saldo. El id del saldo puede unirse con la tabla `claimable_balances` para obtener más detalles sobre el saldo               | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| buying_asset_code                 | La representación del código de 4 o 12 caracteres del activo que se compra o se ofrece comprar en una operación                                                                                                                                                                                  | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| buying_asset_issuer               | La dirección de la cuenta del emisor original del activo que se compra o se ofrece comprar                                                                                                                                                                                                       | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| buying_asset_type                 | El identificador para el tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                    | string         | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>               |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| from                              | La dirección de la cuenta desde la que se origina el pago (la cuenta emisora)                                                                                                                                                                                                                    | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| funder                            | Cuando se crea una nueva cuenta, una dirección de cuenta "financia" la nueva cuenta                                                                                                                                                                                                              | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| high_threshold                    | La suma del peso de todas las firmas que firman una transacción para la operación de umbral alto. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                  | integer        |                                                                                           |             | history_operations | Cada operación cae en una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que una operación necesita para tener éxito (esto es una medida de seguridad) Seguridad Baja: Permitir Confianza, Establecer flags de líneas de confianza, Incrementar Secuencia y Reclamar saldo reclamable Seguridad Media: Todo lo demás Seguridad Alta: Fusión de Cuenta, Establecer Opciones |
-| home_domain                       | El dominio principal usado para el descubrimiento del archivo stellar.toml                                                                                                                                                                                                                       | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| inflation_dest                    | La dirección de la cuenta que especifica dónde enviar los fondos de inflación. El concepto de inflación en la red ha sido descontinuado                                                                                                                                                          | string         |                                                                                           |             | history_operations | La inflación se retiró de la red en 2019.                                                                                                                                                                                                                                                                                                                                                                                   |
-| into                              | La dirección de la cuenta que recibe los lumens de la cuenta eliminada. Esta es la cuenta en la que la cuenta eliminada prevista será fusionada                                                                                                                                                  | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| limit                             | El límite superior de la cantidad de un activo que una cuenta puede poseer                                                                                                                                                                                                                       | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| low_threshold                     | La suma del peso de todas las firmas que firman una transacción para la operación de umbral bajo. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                  | integer        |                                                                                           |             | history_operations | Cada operación cae en una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que una operación necesita para tener éxito (esto es una medida de seguridad) Seguridad Baja: Permitir Confianza, Establecer flags de líneas de confianza, Incrementar Secuencia y Reclamar saldo reclamable Seguridad Media: Todo lo demás Seguridad Alta: Fusión de Cuenta, Establecer Opciones |
-| master_key_weight                 | La clave privada de una cuenta se llama clave maestra. Para firmar transacciones, el titular de la cuenta puede especificar un peso para la clave maestra, que contribuye a la validación de umbrales al procesar una transacción                                                                | integer        | Enteros desde 1 hasta 255                                                                 |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| med_threshold                     | La suma del peso de todas las firmas que firman una transacción para la operación de umbral medio. El peso debe superar el umbral establecido para que la operación tenga éxito.                                                                                                                 | integer        |                                                                                           |             | history_operations | Cada operación cae en una categoría de umbral específica: bajo, medio o alto. Los umbrales definen el nivel de privilegio que una operación necesita para tener éxito (esto es una medida de seguridad) Seguridad Baja: Permitir Confianza, Establecer flags de líneas de confianza, Incrementar Secuencia y Reclamar saldo reclamable Seguridad Media: Todo lo demás Seguridad Alta: Fusión de Cuenta, Establecer Opciones |
-| name                              | La operación de gestionar datos permite a una cuenta escribir y almacenar datos directamente en el ledger en un formato de par clave-valor. El nombre es la clave para una entrada de datos.                                                                                                     | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| offer_id                          | El id único para la oferta. Este id puede unirse con la tabla `offers`                                                                                                                                                                                                                           | integer        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| path                              | Los pagos por camino maximizan la mejor ruta de tasa de cambio al enviar dinero de un activo a otro. Los activos intermediarios por los que pasa este camino se reportarán en el registro. Esta función es especialmente útil cuando el mercado entre el par original de activos es poco líquido | array[record]  |                                                                                           |             | history_operations | Se permiten hasta 6 caminos para un solo pago. Ejemplo: enviar EUR -> MXN podría verse como EUR -> BTC -> CNY -> XLM -> MXN para maximizar la mejor tasa de cambio Los pagos son atómicos, así que si una exchange en medio de un pago por camino falla, todo el pago fallará y eso significa que el usuario mantendrá sus fondos originales. No quedarán atrapados con un activo intermediario en caso de fallo de pago.   |
-| price                             | La proporción del activo de venta al activo de compra. Este es un número que representa cuántas unidades de un activo de venta se necesitan para obtener 1 unidad de un activo de compra                                                                                                         | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| d                                 | Representación precisa del precio de compra y venta de una operación. El `d` es el denominador. Cuando se toma con n/d obtendrás el precio                                                                                                                                                       | integer        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| n                                 | Representación precisa de los precios de compra y venta de una operación. El `n` es el numerador. Cuando se toma con n/d obtendrás el precio.                                                                                                                                                    | integer        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| selling_asset_code                | La representación del código de 4 o 12 caracteres del activo que se vende o se ofrece vender en una operación                                                                                                                                                                                    | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| selling_asset_issuer              | La dirección de la cuenta del emisor original del activo que se vende o se ofrece vender                                                                                                                                                                                                         | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| selling_asset_type                | El identificador para el tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                    | string         | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>               |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| set_flags                         | Arreglo de valores numéricos de los flags establecidos para una trustline dada en la operación                                                                                                                                                                                                   | array[integer] | <ul><li>1 - Auth Required</li><li>2 - Auth Revocable</li><li>4 - Auth Immutable</li></ul> |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| set_flags_s                       | Arreglo de valores en cadena de los flags establecidos para una trustline dada en la operación                                                                                                                                                                                                   | array[string]  | <ul><li>Auth Required</li><li>Auth Revocable</li><li>Auth Immutable</li></ul>             |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| signer_key                        | La dirección del firmante que ya no está patrocinado                                                                                                                                                                                                                                             | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| signer_weight                     | El peso del nuevo firmante. Para transacciones, múltiples cuentas pueden firmar una transacción desde una cuenta fuente. Este peso contribuye al cálculo de si la transacción supera el peso del umbral especificado para completar la transacción                                               | integer        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| source_amount                     | La cantidad de origen enviada designada en el activo fuente                                                                                                                                                                                                                                      | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| source_asset_code                 | La representación del código del activo de 4 o 12 caracteres que se envía originalmente                                                                                                                                                                                                          | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| source_asset_issuer               | La dirección de la cuenta del emisor original del activo que se envía                                                                                                                                                                                                                            | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| source_asset_type                 | El identificador para tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                       | string         | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>               |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| source_max                        | La cantidad máxima a enviar, designada en el activo fuente                                                                                                                                                                                                                                       | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| starting_balance                  | La cantidad de XLM para enviar a la cuenta recién creada. El saldo inicial de la cuenta deberá superar el saldo mínimo necesario para mantener una cuenta en la red Stellar                                                                                                                      | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| to                                | La dirección de la cuenta que recibe los fondos del pago                                                                                                                                                                                                                                         | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| trustee                           | La dirección de la cuenta emisora (solo presente para tipos de activos `credit`)                                                                                                                                                                                                                 | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| trustor                           | La dirección de la cuenta confiada, o la cuenta que está siendo autorizada o no autorizada                                                                                                                                                                                                       | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| trustline_asset                   | El activo de la trustline que ya no está patrocinado                                                                                                                                                                                                                                             | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| value                             | La operación de gestionar datos permite a una cuenta escribir y almacenar datos directamente en el ledger en un formato de par clave-valor. El valor es el valor de una clave para una entrada de datos.                                                                                         | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| clear_flags                       | Arreglo de valores numéricos de los flags borrados para una trustline dada en la operación. Si el flag estaba originalmente establecido, esto eliminará el flag                                                                                                                                  | array[integer] | <ul><li>1 - Auth Required</li><li>2 - Auth Revocable</li><li>4 - Auth Immutable</li></ul> |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| clear_flags_s                     | Arreglo de valores en cadena de los flags borrados para una trustline dada en la operación. Si el flag estaba originalmente establecido, esto eliminará el flag                                                                                                                                  | array[string]  | <ul><li>Auth Required</li><li>Auth Revocable</li><li>Auth Immutable</li></ul>             |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| destination_min                   | La cantidad mínima a recibir, designada en el activo destino esperado                                                                                                                                                                                                                            | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| bump_to                           | El nuevo valor deseado del número de secuencia de la cuenta fuente                                                                                                                                                                                                                               | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| sponsor                           | La dirección de la cuenta de otra cuenta que mantiene el saldo mínimo en XLM para que la cuenta fuente complete operaciones                                                                                                                                                                      | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| sponsored_id                      | La dirección de la cuenta que será patrocinada                                                                                                                                                                                                                                                   | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| begin_sponsor                     | La dirección de la cuenta que inició el patrocinio                                                                                                                                                                                                                                               | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| authorize_to_maintain_liabilities | Indica si la trustline está autorizada. 0 si la cuenta no está autorizada a transaccionar con el activo de ninguna manera. 1 si la cuenta está autorizada a transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones.        | boolean        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| clawback_enabled                  | Indica si el activo puede ser recuperado por el emisor del activo                                                                                                                                                                                                                                | boolean        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| liquidity_pool_id                 | Identificador único para un pool de liquidez                                                                                                                                                                                                                                                     | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_a_asset_type              | El identificador para tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                       | string         | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>               |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_a_asset_code              | La representación del código de 4 o 12 caracteres del activo de uno de los dos pares de activos en un pool de liquidez                                                                                                                                                                           | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_a_asset_issuer            | La dirección de la cuenta del emisor original de uno de los dos pares de activos en el pool de liquidez                                                                                                                                                                                          | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_a_max_amount              | La cantidad máxima de reserva a que puede ser depositada en el pool.                                                                                                                                                                                                                             | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_a_deposit_amount          | La cantidad de reserva a que terminó siendo depositada en el pool                                                                                                                                                                                                                                | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_b_asset_type              | El identificador para tipo de código del activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                                                       | string         | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>               |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_b_asset_code              | La representación del código de 4 o 12 caracteres del activo de uno de los dos pares de activos en un pool de liquidez                                                                                                                                                                           | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_b_asset_issuer            | La dirección de la cuenta del emisor original de uno de los dos pares de activos en el pool de liquidez                                                                                                                                                                                          | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_b_max_amount              | La cantidad máxima de reserva b que puede ser depositada en el pool.                                                                                                                                                                                                                             | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_b_deposit_amount          | La cantidad de reserva b que terminó siendo depositada en el pool.                                                                                                                                                                                                                               | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| min_price                         | El valor en punto flotante que indica la tasa mínima de cambio para esta operación de depósito. Reportado como Reserva A / Reserva B                                                                                                                                                             | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| min_price_r                       | Una representación fraccional de los precios de los dos activos en un pool. El n es el numerador (valor del activo a) y el d es el denominador (valor del activo b)                                                                                                                              | array[record]  |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| max_price                         | El valor en punto flotante que indica la tasa máxima de cambio para esta operación de depósito. Reportado como Reserva A / Reserva B                                                                                                                                                             | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| max_price_r                       | Una representación fraccional de los precios de los dos activos en un pool. El n es el numerador (valor del activo a) y el d es el denominador (valor del activo b)                                                                                                                              | array[record]  |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| shares_received                   | Un número en punto flotante que representa la cantidad de acciones del pool recibidas por este depósito. Una acción del pool es una compilación de las reservas de los activos a y b. No es posible poseer solo el activo a o el activo b en un pool                                             | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_a_min_amount              | La cantidad mínima de reserva a que se puede retirar del pool.                                                                                                                                                                                                                                   | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_b_min_amount              | La cantidad mínima de reserva b que se puede retirar del pool.                                                                                                                                                                                                                                   | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| shares                            | El número de acciones retiradas del pool. No es posible retirar solo el activo a o el activo b, se debe retirar un valor igual del pool                                                                                                                                                          | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_a_withdraw_amount         | La cantidad de reserva a que finalmente se retiró del pool.                                                                                                                                                                                                                                      | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| reserve_b_withdraw_amount         | La cantidad de reserva b que finalmente se retiró del pool.                                                                                                                                                                                                                                      | float          |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| op_application_order              | El número de orden en el conjunto de transacciones en el que se ejecuta la operación. El orden de aplicación y la identificación de la transacción son una clave natural que comprende la identificación (id) de la operación                                                                    | integer        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| op_id                             | Identificador único para una operación                                                                                                                                                                                                                                                           | integer        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| op_source_account                 | La dirección de la cuenta que origina la operación                                                                                                                                                                                                                                               | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| op_source_account_muxed           | Si una cuenta está multiplexada (muxed), la dirección de cuenta virtual que origina la operación                                                                                                                                                                                                 | string         |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| transaction_id                    | El identificador de la transacción en la que se ejecuta la operación. Puede haber hasta 100 operaciones en una transacción dada                                                                                                                                                                  | integer        |                                                                                           |             | history_operations |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| type                              | El número que indica qué tipo de operación ejecuta esta operación                                                                                                                                                                                                                                | integer        |                                                                                           |             |                    |                                                                                                                                                                                                                                                                                                                                                                                                                             |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.mdx
deleted file mode 100644
index 8302764a83..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/evicted-keys-snapshot.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Instantánea de claves desalojadas
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                       |
-| --------------------- | --------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | ledger_key_hash, valid_from                                                                         |
-| Campo(s) de partición | valid_to (partición por MES)                                                                        |
-| Campo(s) agrupado(s)  | ledger_key_hash                                                                                     |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.evicted_keys_snapshot) |
-
-## Detalles de columnas
-
-| Nombre          | Descripción                                                                                                                  | Tipo de dato | Valores de dominio | ¿Requerido? | Notas                                                                |
-| --------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ | ----------- | -------------------------------------------------------------------- |
-| ledger_key_hash | Hash de ledgerKey, que es un subconjunto de ledgerEntry. El subconjunto de campos de ledgerEntry depende de ledgerEntryType. | CADENA       |                    | Sí          |                                                                      |
-| closed_at       | Fecha y hora en UTC cuando este libro se cerró y confirmó.                                                                   | FECHA Y HORA |                    | Sí          | Se espera que los libros se cierren aproximadamente cada 5 segundos. |
-| is_evicted      | Indicador de estado que muestra si una entrada está desalojada o no.                                                         | BOOLEANO     | false, true        | Sí          | false = la clave ha sido restaurada.                                 |
-| ledger_sequence | El número de secuencia de este libro, que representa su orden en la blockchain de Stellar.                                   | ENTERO       |                    | Sí          | Campo agrupado. Único por libro.                                     |
-| valid_from      | La fecha y hora en que esta fila de instantánea fue insertada por primera vez y se volvió efectiva.                          | FECHA Y HORA |                    | Sí          | Ayuda a rastrear cambios a lo largo del tiempo.                      |
-| valid_to        | La fecha y hora en que esta fila ya no es válida.                                                                            | FECHA Y HORA |                    | No          | Si es nula, la configuración está actualmente activa.                |
-
-## Ejemplos de preguntas empresariales
-
-1. Claves desalojadas a la fecha
-
-```sql
-SELECT ledger_key_hash, is_evicted
-FROM `crypto-stellar.snapshots.evicted_keys_snapshot`
-WHERE valid_to IS NULL
-  AND is_evicted = TRUE
-LIMIT 100
-```
-
-2. Estado de desalojo en un momento específico
-
-```sql
-SELECT ledger_key_hash, is_evicted
-FROM `crypto-stellar.snapshots.evicted_keys_snapshot`
-WHERE ledger_key_hash = 'abc123'
-  AND AND DATE('2025-03-10') BETWEEN DATE(valid_from) AND COALESCE(DATE(valid_to), '9999-12-31')
-LIMIT 100
-```
-
-3. Restauraciones mensuales de claves
-
-```sql
-WITH with_lag AS (
-  SELECT
-    ledger_key_hash,
-    valid_from,
-    is_evicted,
-    LAG(is_evicted) OVER (
-      PARTITION BY ledger_key_hash
-      ORDER BY valid_from
-    ) AS prev_status
-  FROM `crypto-stellar.snapshots.evicted_keys_snapshot`
-)
-
-SELECT
-  DATE_TRUNC(valid_from, MONTH) AS month,
-  COUNTIF(prev_status = TRUE AND is_evicted = FALSE) AS restorations_count
-FROM with_lag
-GROUP BY month
-ORDER BY month
-LIMIT 100
-```
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.mdx
deleted file mode 100644
index 5c046d4b9c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Pooling de Liquidez Actual
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                         |
-| --------------------- | ----------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | liquidity_pool_id, closed_at                                                                          |
-| Campo(s) de Partición | batch_run_date (partición MENSUAL)                                                                    |
-| Campo(s) Clustered    | liquidity_pool_id, asset_a_id, asset_b_id, last_modified_ledger                                       |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.liquidity_pools_current) |
-
-## Detalles de la Columna
-
-Los detalles de las columnas son equivalentes a la tabla bronze [Liquidity Pools](../bronze/liquidity-pools.mdx). Filtra para mostrar solo la información más reciente del estado.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.mdx
deleted file mode 100644
index da0655e799..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/liquidity-pools-snapshot.mdx
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Imagen de Billeteras de Liquidez Snapshot
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                          |
-| --------------------- | ------------------------------------------------------------------------------------------------------ |
-| Clave Natural(s)      | liquidity_pool_id, valid_from                                                                          |
-| Campo(s) de Partición | valid_to (partición mensual)                                                                           |
-| Campo(s) Agrupado(s)  | liquidity_pool_id                                                                                      |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.liquidity_pools_snapshot) |
-
-## Detalles de Columnas
-
-| Nombre               | Descripción                                                                                                                                                                                                                                 | Tipo de Datos | Valores de Dominio                                                                                                                                                                                | ¿Requerido? | Notas                                                                                                                                                   |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| liquidity_pool_id    | Identificador único para un pool de liquidez.                                                                                                                                                                                               | STRING        |                                                                                                                                                                                                   | Sí          | Clave Natural. Campo Agrupado. No puede duplicarse para el mismo par de activos.                                                                        |
-| type                 | Mecanismo que calcula los precios y la división de las participaciones del pool.                                                                                                                                                            | STRING        | constant_product                                                                                                                                                                                  | Sí          | Inicialmente sólo se soportan pools de producto constante. Consulta [Cap-38](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0038.md). |
-| fee                  | Puntos básicos cobrados como comisión de comercio.                                                                                                                                                                                          | INTEGER       | Por defecto = 30                                                                                                                                                                                  | Sí          | Las comisiones se distribuyen inmediatamente a las cuentas conforme se completan las transacciones.                                                     |
-| trustline_count      | Número total de cuentas con trustlines autorizadas al pool.                                                                                                                                                                                 | INTEGER       |                                                                                                                                                                                                   | Sí          | Revocar la autorización sobre un activo retirará a las cuentas de todos los pools que contienen ese activo.                                             |
-| pool_share_count     | Número total de participaciones del pool que representan participación en el pool de liquidez.                                                                                                                                              | FLOAT         |                                                                                                                                                                                                   | Sí          | Las participaciones no son transferibles. Sólo pueden ajustarse mediante depósito/retiro.                                                               |
-| asset_a_type         | Tipo de activo para un lado del pool (activo vendido).                                                                                                                                                                                      | STRING        | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                       | Sí          | XLM tiene tipo = 'native'. Sin código/issuer de activo.                                                                                                 |
-| asset_a_code         | Código del activo (4 o 12 caracteres) para el activo vendido en el comercio.                                                                                                                                                                | STRING        |                                                                                                                                                                                                   | No          | Los códigos de activos por sí solos no son únicos. La combinación con issuer + tipo es única.                                                           |
-| asset_a_issuer       | Dirección de la cuenta del emisor original del activo vendido.                                                                                                                                                                              | STRING        |                                                                                                                                                                                                   | No          |                                                                                                                                                         |
-| asset_a_id           | Codificación Farm Hash del código del activo + issuer + tipo para el activo A.                                                                                                                                                              | INTEGER       |                                                                                                                                                                                                   | No          |                                                                                                                                                         |
-| asset_a_amount       | Número bruto de tokens bloqueados en el pool para el activo A.                                                                                                                                                                              | FLOAT         |                                                                                                                                                                                                   | Sí          |                                                                                                                                                         |
-| asset_b_type         | Tipo de activo para el otro lado del pool.                                                                                                                                                                                                  | STRING        | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                       | Sí          | XLM tiene tipo = 'native'.                                                                                                                              |
-| asset_b_code         | Código del activo (4 o 12 caracteres) para el otro activo en el comercio.                                                                                                                                                                   | STRING        |                                                                                                                                                                                                   | No          | Los códigos de activos por sí solos no son únicos. La combinación con issuer + tipo es única.                                                           |
-| asset_b_issuer       | Dirección de la cuenta del emisor original del otro activo.                                                                                                                                                                                 | STRING        |                                                                                                                                                                                                   | No          |                                                                                                                                                         |
-| asset_b_id           | Codificación Farm Hash del código del activo + issuer + tipo para el activo B.                                                                                                                                                              | INTEGER       |                                                                                                                                                                                                   | No          |                                                                                                                                                         |
-| asset_b_amount       | Número bruto de tokens bloqueados en el pool para el activo B.                                                                                                                                                                              | FLOAT         |                                                                                                                                                                                                   | Sí          |                                                                                                                                                         |
-| last_modified_ledger | Número de secuencia del ledger cuando se modificó por última vez la entrada del pool.                                                                                                                                                       | INTEGER       |                                                                                                                                                                                                   | Sí          | Clave Natural. Campo Agrupado. La eliminación no cuenta como modificación.                                                                              |
-| ledger_entry_change  | Código que describe el tipo de cambio en la entrada del ledger.                                                                                                                                                                             | INTEGER       | <ul><li>0 - Entrada de Ledger Creada</li><li>1 - Entrada de Ledger Actualizada</li><li>2 - Entrada de Ledger Eliminada</li><li>3 - Estado de la Entrada de Ledger (valor de la entrada)</li></ul> | Sí          | Actualizaciones no válidas para saldos reclamables.                                                                                                     |
-| deleted              | Indica si la entrada del pool de liquidez fue eliminada.                                                                                                                                                                                    | BOOLEAN       | true, false                                                                                                                                                                                       | Sí          | Las entradas eliminadas no pueden recuperarse; el historial se mantiene.                                                                                |
-| batch_id             | Representación en cadena del ID de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los IDs de batch son únicos para el lote y ayudan con la monitorización y capacidades de reejecución. | string        |                                                                                                                                                                                                   | Sí          |                                                                                                                                                         |
-| batch_run_date       | Fecha de inicio para el intervalo del lote.                                                                                                                                                                                                 | DATETIME      |                                                                                                                                                                                                   | Sí          | Equivalente a closed_at.                                                                                                                                |
-| closed_at            | Marca temporal en UTC cuando el ledger se cerró y confirmó.                                                                                                                                                                                 | TIMESTAMP     |                                                                                                                                                                                                   | Sí          | Los ledgers se cierran aproximadamente cada 5 segundos.                                                                                                 |
-| ledger_sequence      | Número de secuencia del ledger.                                                                                                                                                                                                             | INTEGER       |                                                                                                                                                                                                   | Sí          | Representa el orden del ledger dentro de la blockchain Stellar.                                                                                         |
-| batch_insert_ts      | Marca temporal en UTC cuando el lote fue insertado en la base de datos.                                                                                                                                                                     | TIMESTAMP     |                                                                                                                                                                                                   | Sí          | Usado para ingeniería/depuración, no para análisis.                                                                                                     |
-| airflow_start_ts     | Marca temporal cuando comenzó la tarea de airflow.                                                                                                                                                                                          | STRING        |                                                                                                                                                                                                   | Sí          | Ayuda a detectar cargas de relleno retroactivo.                                                                                                         |
-| valid_from           | Marca temporal cuando esta fila de imagen se hizo efectiva.                                                                                                                                                                                 | TIMESTAMP     |                                                                                                                                                                                                   | Sí          | Ayuda a rastrear cambios con el tiempo.                                                                                                                 |
-| valid_to             | Marca temporal cuando esta fila deja de ser válida.                                                                                                                                                                                         | TIMESTAMP     |                                                                                                                                                                                                   | No          | Null = aún activo.                                                                                                                                      |
-
-## Ejemplos de Preguntas de Negocio
-
-1. ¿Cuál fue la liquidez total (asset_a_amount + asset_b_amount) en todos los pools en una fecha dada?
-
-```sql
-SELECT
-  DATE('2025-01-15') AS as_of_date,
-  SUM(asset_a_amount + asset_b_amount) AS total_liquidity
-FROM `crypto-stellar.snapshots.liquidity_pools_snapshot`
-WHERE DATE(valid_from) <= DATE('2025-01-15')
-  AND (DATE(valid_to) > DATE('2025-01-15') OR valid_to IS NULL)
-  AND deleted = FALSE;
-```
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.mdx
deleted file mode 100644
index 011d11ab0d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/offers-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Ofertas Actuales
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                |
-| --------------------- | -------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | offer_id, closed_at                                                                          |
-| Campo(s) de Partición | batch_run_date (partición MENSUAL)                                                           |
-| Campo(s) Agrupado(s)  | selling_asset_id, buying_asset_id, last_modified_ledger                                      |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.offers_current) |
-
-## Detalles de Columnas
-
-Los detalles de las columnas son equivalentes a la tabla bronze [Offers](../bronze/offers.mdx). Filtra solo la información del estado más reciente.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.mdx
deleted file mode 100644
index 0a6ceea05b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/token-transfers-raw.mdx
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Transferencias de tokens
-sidebar_position: 160
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                                      |
-| --------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| Clave(s) natural(es)  | N/A                                                                                                                |
-| Campo(s) de partición | closed_at (partición DAY)                                                                                          |
-| Campo(s) agrupados    | contract_id, asset                                                                                                 |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.token_transfers_raw) |
-
-## Detalles de columnas
-
-| Nombre           | Descripción                                                                                                                                                                                                                                                  | Tipo de datos | Valores del dominio | ¿Obligatorio? | Notas |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------- | ------------------- | ------------- | ----- |
-| transaction_hash | Un hash SHA-256 codificado en hexadecimal de la forma codificada en XDR de esta transacción.                                                                                                                                                                 | STRING        |                     | Sí            |       |
-| transaction_id   | Un identificador único para esta transacción.                                                                                                                                                                                                                | INTEGER       |                     | Sí            |       |
-| operation_id     | Un identificador único para esta transacción.                                                                                                                                                                                                                | INTEGER       |                     | No            |       |
-| event_topic      | El tipo de acción aplicado al token.                                                                                                                                                                                                                         | STRING        |                     | Sí            |       |
-| from             | La dirección fuente para la cantidad del evento de transferencia de tokens.                                                                                                                                                                                  | STRING        |                     | No            |       |
-| to               | La dirección destino para la cantidad del evento de transferencia de tokens.                                                                                                                                                                                 | STRING        |                     | No            |       |
-| asset            | Campo ID para el par código de activo/emisor. Se crea concatenando el código de activo, ':' y los campos asset_issuer.                                                                                                                                       | STRING        |                     | Sí            |       |
-| asset_type       | El identificador para el tipo de código de activo, puede ser un alfanumérico de 4 caracteres, 12 caracteres o el activo nativo de la red (XLM).                                                                                                              | STRING        |                     | Sí            |       |
-| asset_code       | La representación en código de 4 o 12 caracteres del activo en la red.                                                                                                                                                                                       | STRING        |                     | No            |       |
-| asset_issuer     | La dirección de cuenta del emisor original del activo que creó el activo.                                                                                                                                                                                    | STRING        |                     | No            |       |
-| amount           | La cantidad normalizada en formato flotante del activo.                                                                                                                                                                                                      | FLOAT         |                     | Sí            |       |
-| amount_raw       | La cantidad de stroop en bruto del activo.                                                                                                                                                                                                                   | STRING        |                     | Sí            |       |
-| contract_id      | ID del contrato Soroban.                                                                                                                                                                                                                                     | STRING        |                     | Sí            |       |
-| to_muxed         | La representación multiplexada strkey de la dirección `to`.                                                                                                                                                                                                  | STRING        |                     | No            |       |
-| to_muxed_id      | El ID multiplexado usado para generar la representación multiplexada strkey de la dirección `to`.                                                                                                                                                            | STRING        |                     | No            |       |
-| batch_id         | Representación en cadena de caracteres del id de ejecución para un DAG dado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los IDs de batch son únicos para el lote y ayudan con la monitorización y las capacidades de reejecución | string        |                     | Sí            |       |
-| batch_run_date   | La fecha de inicio para el intervalo del batch. Cuando se toma junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados. La fecha de ejecución del batch puede verse como un proxy de closed_at para un ledger.             | datetime      |                     | Sí            |       |
-| batch_insert_ts  | La marca de tiempo en UTC cuando un lote de registros fue insertado en la base de datos. Este campo puede ayudar a identificar si un lote se ejecutó en tiempo real o como parte de un retroceso                                                             | timestamp     |                     | Sí            |       |
-| closed_at        | Marca de tiempo en UTC cuando este ledger se cerró y confirmó en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                                | timestamp     |                     | Sí            |       |
-| ledger_sequence  | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain de Stellar. Cada ledger tiene un número de secuencia único que incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto.  | integer       |                     | Sí            |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.mdx
deleted file mode 100644
index 87d81f8843..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Líneas de confianza actuales
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                     |
-| --------------------- | ------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | account_id, asset_type, asset_issuer, asset_code, liquidity_pool_id, closed_at                    |
-| Campo(s) de partición | batch_run_date (partición por MES)                                                                |
-| Campo(s) agrupado(s)  | account_id, asset_id, liquidity_pool_id, last_modified_ledger                                     |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.trust_lines_current) |
-
-## Detalles de la columna
-
-Los detalles de las columnas son equivalentes a la tabla bronze [Trustlines](../bronze/trustlines.mdx). Filtra únicamente la información del estado más reciente.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.mdx
deleted file mode 100644
index 399e02a960..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/trustlines-snapshot.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Imagen de Trustlines Snapshot
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                                     |
-| --------------------- | ------------------------------------------------------------------------------------------------- |
-| Llave(s) Natural(es)  | account_id, asset_type, asset_issuer, asset_code, liquidity_pool_id, valid_from                   |
-| Campo(s) de partición | valid_to (partición MENSUAL)                                                                      |
-| Campo(s) agrupado(s)  | account_id, asset_id                                                                              |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.trustlines_snapshot) |
-
-## Detalles de columnas
-
-| Nombre               | Descripción                                                                                                                                                                                                                                         | Tipo de dato | Valores del dominio                                                                                                                                                                                   | ¿Requerido? | Notas                                                                |
-| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------- |
-| ledger_key           | Llave única de ledger cuando el estado de la trustline cambió por última vez.                                                                                                                                                                       | STRING       |                                                                                                                                                                                                       | Sí          | Llave natural.                                                       |
-| account_id           | Identificador único de la cuenta.                                                                                                                                                                                                                   | STRING       |                                                                                                                                                                                                       | Sí          |                                                                      |
-| asset_type           | Tipo de código de activo: alfanumérico de 4 caracteres, 12 caracteres, o `native` (XLM).                                                                                                                                                            | STRING       | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                                                           | Sí          | XLM no tiene emisor ni código de activo, se muestra como `native`.   |
-| asset_issuer         | Dirección de cuenta del emisor original del activo.                                                                                                                                                                                                 | STRING       |                                                                                                                                                                                                       | No          |                                                                      |
-| asset_code           | Código de 4 o 12 caracteres del activo.                                                                                                                                                                                                             | STRING       |                                                                                                                                                                                                       | No          | La unicidad del activo = `código + emisor + tipo`.                   |
-| asset_id             | Identificador codificado del activo.                                                                                                                                                                                                                | INTEGER      |                                                                                                                                                                                                       | No          | Derivado de código de activo + emisor + tipo.                        |
-| liquidity_pool_id    | Identificador único para un liquidity pool.                                                                                                                                                                                                         | STRING       |                                                                                                                                                                                                       | Sí          | Llave natural. Campo agrupado.                                       |
-| balance              | Número de unidades del activo que posee esta cuenta.                                                                                                                                                                                                | FLOAT        |                                                                                                                                                                                                       | Sí          |                                                                      |
-| trust_line_limit     | Cantidad máxima de este activo que la cuenta acepta.                                                                                                                                                                                                | INTEGER      |                                                                                                                                                                                                       | Sí          | Establecido al abrir la trustline.                                   |
-| buying_liabilities   | Suma de las ofertas de compra poseídas por esta cuenta (solo XLM).                                                                                                                                                                                  | FLOAT        |                                                                                                                                                                                                       | Sí          | Otros activos reportados en `trust_lines`.                           |
-| selling_liabilities  | Suma de las ofertas de venta poseídas por esta cuenta (solo XLM).                                                                                                                                                                                   | FLOAT        |                                                                                                                                                                                                       | Sí          | Otros activos reportados en `trust_lines`.                           |
-| flags                | Flags de privilegios del emisor aplicados al activo.                                                                                                                                                                                                | INTEGER      | <ul><li>0 - Ninguno, por defecto</li><li>1 - Autorizado</li><li>2 - Autorizado para mantener pasivos</li><li>4 - Clawback habilitado</li></ul>                                                        | Sí          | Los flags provienen de la cuenta del emisor.                         |
-| last_modified_ledger | Número de secuencia del ledger cuando la entrada fue modificada por última vez.                                                                                                                                                                     | INTEGER      |                                                                                                                                                                                                       | Sí          | Llave natural. Campo agrupado. No es un proxy para eliminación.      |
-| ledger_entry_change  | Código para el tipo de cambio de la entrada del ledger.                                                                                                                                                                                             | INTEGER      | <ul><li>0 - Entrada del Ledger creada</li><li>1 - Entrada del Ledger actualizada</li><li>2 - Entrada del Ledger eliminada</li><li>3 - Estado de la entrada del Ledger (valor de la entrada)</li></ul> | Sí          | Algunas entradas del ledger no pueden actualizarse.                  |
-| deleted              | Indica si la entrada del ledger fue eliminada.                                                                                                                                                                                                      | BOOLEAN      | true, false                                                                                                                                                                                           | Sí          | Las entradas eliminadas permanecen en el historial.                  |
-| sponsor              | Cuenta que paga las reservas por esta entrada del ledger.                                                                                                                                                                                           | STRING       |                                                                                                                                                                                                       | No          | Puede patrocinar cuentas, firmantes, saldos reclamables, trustlines. |
-| batch_id             | Representación en cadena del ID de ejecución para un DAG determinado en Airflow. Toma la forma de `scheduled__<batch_end_date>-<dag_alias>`. Los IDs de batch son únicos para el batch y ayudan con la monitorización y capacidades de reejecución. | string       |                                                                                                                                                                                                       | Sí          |                                                                      |
-| batch_run_date       | Fecha de inicio del intervalo del batch.                                                                                                                                                                                                            | DATETIME     |                                                                                                                                                                                                       | Sí          | Proxy para `closed_at`.                                              |
-| closed_at            | Marca temporal del cierre del ledger en UTC.                                                                                                                                                                                                        | TIMESTAMP    |                                                                                                                                                                                                       | Sí          | Los ledgers cierran aproximadamente cada 5 segundos.                 |
-| ledger_sequence      | Número de secuencia de este ledger.                                                                                                                                                                                                                 | INTEGER      |                                                                                                                                                                                                       | Sí          | Campo agrupado. Único, incrementa por cada ledger.                   |
-| batch_insert_ts      | Marca temporal UTC cuando se insertó el lote de registros.                                                                                                                                                                                          | TIMESTAMP    |                                                                                                                                                                                                       | Sí          | Solo para análisis de ingeniería / reejecución.                      |
-| airflow_start_ts     | Marca temporal de inicio de tarea de Airflow.                                                                                                                                                                                                       | STRING       |                                                                                                                                                                                                       | Sí          |                                                                      |
-| valid_from           | Marca temporal cuando la fila se volvió efectiva.                                                                                                                                                                                                   | TIMESTAMP    |                                                                                                                                                                                                       | Sí          | Rastrea cambios históricos.                                          |
-| valid_to             | Marca temporal cuando la fila ya no es válida.                                                                                                                                                                                                      | TIMESTAMP    |                                                                                                                                                                                                       | No          | Nulo = actualmente activo.                                           |
-
-## Ejemplos de preguntas de negocio
-
-1. ¿Cuál era el saldo de las trustlines de cada cuenta en una fecha dada?
-
-```sql
-SELECT
-  account_id,
-  asset_code,
-  asset_issuer,
-  balance
-FROM `crypto-stellar.snapshots.trustlines_snapshot`
-WHERE DATE(valid_from) <= DATE('2025-01-15')
-  AND (DATE(valid_to) > DATE('2025-01-15') OR valid_to IS NULL)
-  AND deleted = FALSE
-  AND liquidity_pool_id = ''
-LIMIT 100;
-```
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.mdx
deleted file mode 100644
index e72b5328ec..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/silver/ttl-current.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: TTL Actualizado
-sidebar_position: 10
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la tabla
-
-| Propiedad             | Configuración                                                                             |
-| --------------------- | ----------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | key_hash, closed_at                                                                       |
-| Campo(s) de partición | closed_at (partición MENSUAL)                                                             |
-| Campo(s) agrupado(s)  | last_modified_ledger, key_hash                                                            |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/model/model.stellar_dbt_public.ttl_current) |
-
-## Detalles de columnas
-
-Los detalles de las columnas son equivalentes a la tabla bronze [TTL](../bronze/ttl.mdx). Filtra para mostrar solo la información del estado más reciente.
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/trustlines.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/trustlines.mdx
deleted file mode 100644
index 31f3dfaad3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/trustlines.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Líneas de Confianza
-sidebar_position: 70
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                              |
-| --------------------- | ---------------------------------------------------------------------------------------------------------- |
-| Clave(s) natural(es)  | account_id, asset_type, asset_issuer, asset_code, liquidity_pool_id, closed_at                             |
-| Campo(s) de Partición | batch_run_date (partición MONTH)                                                                           |
-| Campo(s) agrupado(s)  | account_id, asset_id, liquidity_pool_id, last_modified_ledger                                              |
-| Documentación         | [dbt docs](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.trust_lines) |
-
-## Detalles de la Columna
-
-| Nombre               | Descripción                                                                                                                                                                                                                                                 | Tipo de Dato | Valores de Dominio                                                                                                                                                       | ¿Requerido? | Notas                                                                                                                                                                          |
-| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| ledger_key           | La clave de ledger única cuando el estado de la línea de confianza cambió por última vez                                                                                                                                                                    | string       |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| account_id           | La dirección de la cuenta                                                                                                                                                                                                                                   | string       |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| asset_type           | El identificador para el tipo de código de activo, puede ser alfanumérico con 4 caracteres, 12 caracteres o el activo nativo de la red, XLM.                                                                                                                | integer      | <ul><li>credit_alphanum4</li><li>credit_alphanum12</li><li>native</li></ul>                                                                                              | Sí          |                                                                                                                                                                                |
-| asset_issuer         | La dirección de la cuenta del emisor original de activo que creó el activo mantenido por esta cuenta                                                                                                                                                        | string       |                                                                                                                                                                          | No          |                                                                                                                                                                                |
-| asset_code           | El código de 4 o 12 caracteres que representa el activo mantenido por esta cuenta                                                                                                                                                                           | string       |                                                                                                                                                                          | No          |                                                                                                                                                                                |
-| liquidity_pool_id    | Si el activo mantenido es parte de una participación en un fondo de liquidez, el id único del fondo del que proviene el saldo del activo                                                                                                                    | string       |                                                                                                                                                                          | No          |                                                                                                                                                                                |
-| balance              | El número de unidades de un activo mantenido por esta cuenta                                                                                                                                                                                                | float        |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| trust_line_limit     | La cantidad máxima de este activo que esta cuenta está dispuesta a aceptar. El límite se especifica al abrir una línea de confianza                                                                                                                         | integer      |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| buying_liabilities   | La suma de todas las ofertas de compra poseídas por esta cuenta para activos no nativos                                                                                                                                                                     | float        |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| selling_liabilities  | La suma de todas las ofertas de venta poseídas por esta cuenta para activos no nativos                                                                                                                                                                      | float        |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| flags                | Denota la habilitación y desactivación de ciertos privilegios del emisor de activo                                                                                                                                                                          | integer      | <ul><li>0 - Ninguno, Predeterminado</li><li>1 - Autorizado</li><li>2 - Autorizado a Mantener Pasivos</li><li>4 - Recaudación Habilitada</li></ul>                        | Sí          | Las banderas se configuran en las cuentas emisoras de un activo. Cuando las cuentas de usuario confían en un activo, las banderas aplicadas al activo provienen de esta cuenta |
-| last_modified_ledger | El número de serie de ledger cuando la entrada de ledger (este firmante único para la cuenta) fue modificada                                                                                                                                                | integer      |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| ledger_entry_change  | Código que describe el tipo de cambio de entrada de ledger que fue aplicado a la entrada de ledger                                                                                                                                                          | integer      | <ul><li>0 - Entrada de Ledger Creada</li><li>1 - Entrada de Ledger Actualizada</li><li>2 - Entrada de Ledger Eliminada</li><li>3 - Estado de Entrada de Ledger</li></ul> | Sí          | Los tipos de cambio de entrada válidos son 0, 1 y 2 para entradas de ledger del tipo `trust_lines`.                                                                            |
-| eliminado            | Indica si la entrada de ledger (línea de confianza) ha sido eliminada o no. Una vez que una entrada es eliminada, no se puede recuperar                                                                                                                     | boolean      |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| closed_at            | Marca de tiempo en UTC cuando este ledger se cerró y fue confirmado en la red. Se espera que los ledgers se cierren aproximadamente cada 5 segundos                                                                                                         | timestamp    |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| ledger_sequence      | El número de secuencia de este ledger. Representa el orden del ledger dentro de la blockchain Stellar. Cada ledger tiene un número de secuencia único que se incrementa con cada nuevo ledger, asegurando que los ledgers se procesen en el orden correcto. | integer      |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| batch_id             | Representación en cadena del id de ejecución para un DAG dado en Airflow                                                                                                                                                                                    | string       |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| batch_run_date       | La fecha de inicio para el intervalo de batch. Cuando se toma junto con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados                                                                                                     | datetime     |                                                                                                                                                                          | Sí          | La tabla se particiona por batch_run_date. Se recomienda incluir siempre el batch_run_date en el filtro si es posible para ayudar a reducir el costo de las consultas.         |
-| batch_insert_ts      | La marca de tiempo en UTC cuando se insertó un batch de registros en la base de datos                                                                                                                                                                       | timestamp    |                                                                                                                                                                          | Sí          |                                                                                                                                                                                |
-| sponsor              | La dirección de la cuenta que patrocina las reservas básicas para la línea de confianza                                                                                                                                                                     | string       |                                                                                                                                                                          | No          |                                                                                                                                                                                |
-| asset_id             | Identificador único para asset_code, asset_issuer                                                                                                                                                                                                           | integer      |                                                                                                                                                                          | No          |                                                                                                                                                                                |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/ttl.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/ttl.mdx
deleted file mode 100644
index 39edd8e94e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-dictionary/ttl.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: TTL
-sidebar_position: 80
-description: ""
----
-
-<div className="scoped-data-dictionary-table">
-
-## Metadatos de la Tabla
-
-| Propiedad             | Configuración                                                                                               |
-| --------------------- | ----------------------------------------------------------------------------------------------------------- |
-| Clave(s) Natural(es)  | key_hash, closed_at                                                                                         |
-| Campo(s) de Partición | closed_at (partición por MES)                                                                               |
-| Campo(s) Agrupado(s)  | last_modified_ledger, key_hash                                                                              |
-| Documentación         | [documentos de dbt](http://www.stellar-dbt-docs.com/#!/source/source.stellar_dbt_public.crypto_stellar.ttl) |
-
-## Detalles de la Columna
-
-| Nombre                   | Descripción                                                                                                                                  | Tipo de Datos   | Valores de Dominio | ¿Requerido? | Notas |
-| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------ | ----------- | ----- |
-| key_hash                 | Hash de clave del ledger usado para identificar datos de contratos caducados o entradas de código de contrato del ledger                     | cadena          |                    | Sí          |       |
-| live_until_ledger_seq    | Número de secuencia del ledger hasta el cual vivirá el contrato o wasm                                                                       | entero          |                    | Sí          |       |
-| last_modified_ledger     | El número de secuencia del ledger cuando la entrada del ledger (este firmante único para la cuenta) fue modificada                           | entero          |                    | Sí          |       |
-| cambio_de_entrada_ledger | Código que describe el tipo de cambio de entrada del ledger que se aplicó a la entrada del ledger                                            | entero          |                    | Sí          |       |
-| eliminado                | Indica si la entrada del ledger (id de saldo) ha sido eliminada o no. Una vez que una entrada es eliminada, no se puede recuperar            | booleano        |                    | Sí          |       |
-| batch_id                 | Representación en cadena del id de ejecución para un DAG dado en Airflow                                                                     | cadena          |                    | Sí          |       |
-| batch_run_date           | La fecha de inicio del intervalo de lote. Cuando se toma con la fecha en el batch_id, la fecha representa el intervalo de ledgers procesados | fecha y hora    |                    | Sí          |       |
-| batch_insert_ts          | La marca de tiempo en UTC cuando un lote de registros se insertó en la base de datos                                                         | marca de tiempo |                    | Sí          |       |
-| closed_at                | La marca de tiempo UNIX de la edad del número de secuencia                                                                                   | marca de tiempo |                    | Sí          |       |
-| ledger_sequence          | El número de ledger no firmado de 32 bits de la edad del número de secuencia                                                                 | entero          |                    | Sí          |       |
-
-</div>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-lineage.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-lineage.mdx
deleted file mode 100644
index fa8a39c22f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-lineage.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Línea de Datos
----
-
-import RedirectPage from "@site/src/components/RedirectPage";
-
-<RedirectPage to="http://www.stellar-dbt-docs.com/#!/overview" />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-model-diagram.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-model-diagram.mdx
deleted file mode 100644
index 6e69235188..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/data-catalog/data-model-diagram.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Diagrama del Modelo de Datos
-sidebar_position: 0
----
-
-:::info
-
-Para obtener información más detallada, consulta el [Diagrama Completo del Modelo de Datos de Hubble](https://dbdiagram.io/d/Hubble-Public-Data-Model-66671e056bc9d447b1501801) o el [Diagrama Comprimido del Modelo de Datos de Hubble](https://dbdiagram.io/d/Hubble-Public-Data-Model-Compressed-666730996bc9d447b151a181).
-
-:::
-
-El siguiente diagrama muestra las relaciones entre las tablas de historial y estado dentro de Hubble.
-
-![Diagrama del Modelo de Datos de Hubble](/img/hubble/data_model_diagram.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/README.mdx
deleted file mode 100644
index d942e309ef..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Guía del desarrollador
-sidebar_position: 15
-sidebar_key: guía-del-desarrollador-hubble
----
-
-import DocCardList from "@theme/DocCardList";
-
-Todo lo que necesitas saber sobre cómo ejecutar una plataforma de análisis Hubble.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx
deleted file mode 100644
index c04736c7d9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/JS-UDF.mdx
+++ /dev/null
@@ -1,158 +0,0 @@
----
-title: Rellenar utilizando JS UDF
-sidebar_position: 0
----
-
-Este documento describe métodos para extraer los campos requeridos del XDR de datos en bruto.
-
-Casos de Uso:
-
-- Corrección para un arreglo de errores
-- Corrección para una nueva columna añadida
-- Extracción temporal de campos no analizados por stellar-etl
-
-Tomaremos el ejemplo de extraer el campo `fee_account_muxed` de un sobre de transacción (`tx_meta` XDR). Sin embargo, este método se puede adaptar a otros campos también. Vale la pena mencionar que la mayoría de los usuarios no necesitarán levantar y ejecutar su propio Hubble. La Stellar Development Foundation proporciona acceso público a los datos a través de los conjuntos de datos y tablas públicos en GCP BigQuery. Las instrucciones sobre cómo acceder a estos datos se pueden encontrar en la sección [Conectar](../../developer-guide/connecting-to-bigquery/README.mdx).
-
-Utilizaremos la biblioteca [js-stellar-base](https://github.com/stellar/js-stellar-base) para analizar el XDR y emplear UDFs de JavaScript (Funciones Definidas por el Usuario) en BigQuery para aplicar la transformación al conjunto de datos.
-
-Para una comprensión más profunda, consulta el [artículo de Medium](https://medium.com/analytics-vidhya/using-npm-library-in-google-bigquery-udf-8aef01b868f4) sobre el uso de bibliotecas de NPM en UDFs de Google BigQuery.
-
-## Paso 1: Configurar JS UDF en BigQuery
-
-Para configurar el JS UDF en BigQuery, sigue estos pasos:
-
-### 1. Clona el repositorio `js-stellar-base`
-
-Primero, clona el repositorio en tu máquina local e instala las dependencias:
-
-```bash
-git clone https://github.com/stellar/js-stellar-base.git
-cd js-stellar-base
-yarn
-yarn build:prod
-```
-
-Este proceso generará el siguiente archivo en el directorio js-stellar-base/dist/:
-
-- stellar-base.min.js
-
-### 2. Sube el archivo JS a Google Cloud Storage (GCS)
-
-Una vez completado el proceso de construcción, sube el archivo stellar-base.min.js a un bucket de Google Cloud Storage para ser utilizado en el UDF.
-
-## Paso 2: Escribir la Función en JavaScript
-
-Aquí hay un ejemplo de función en JavaScript para extraer el campo fee_account_muxed del sobre de transacción (tx_meta):
-
-```JavaScript
-let tx_meta =
-  "AAAABQAAAQAAABYMYQ4r9W/uB9X6q6VU6feQhS2kQoRy9CjvwtYXdPRSih2hZeSSAAAAAAAAAZAAAAACAAAAAJwLL0Ul/CyRZdXuenmdXrzVyX9X56m4kYPYmgppVIj8AAAAZAAF9PwAAAABAAAAAAAAAAAAAAABAAAAAQAAAQAAAFj7+8N85JwLL0Ul/CyRZdXuenmdXrzVyX9X56m4kYPYmgppVIj8AAAAAAAAAADN5igtu93OKhkj2NrSHuPEJktU+0gJ0LiNavJirLAmRwAAAAAF9eEAAAAAAAAAAAFpVIj8AAAAQElnt70S4sGicHyhsN1S29DEREZ7i2HU96+8DfyshlFLCoQudDIxThnVEg2KQDrW61R19M7Ms9IAsznURc5y3wIAAAAAAAAAAaFl5JIAAABAIf9/ecA3id1mbHzJ2S9W5bRVqrjQr/c2+jHEuDNZevt3LDVSc+DmRMYie0eQ+vE7B3D+fRPb9yFzpfx4meTfBg==";
-
-let txe = StellarBase.xdr.TransactionEnvelope.fromXDR(tx_meta, "base64");
-let tx = txe.feeBump();
-let sourceAccount = StellarBase.encodeMuxedAccountToAddress(
-  tx.tx().feeSource(),
-);
-console.log(sourceAccount);
-```
-
-Este script devolverá el valor de `fee_account_muxed`: `MBX64B6V7KV2KVHJ66IIKLNEIKCHF5BI57BNMF3U6RJIUHNBMXSJEAAACYGGCDRL6UFO2`
-
-## Paso 3: Envolver la Función de JavaScript como un UDF
-
-```sql
-CREATE TEMP FUNCTION getFeeBumpAccountIfExists(tx_meta STRING)
-RETURNS STRING
-LANGUAGE js
-OPTIONS (
-  library=["gs://stellar-test-js-udf/stellar-base.min.js"]  -- Path to JS library in GCS
-)
-AS r"""
-    return StellarBase.encodeMuxedAccountToAddress(
-        StellarBase.xdr.TransactionEnvelope.fromXDR(tx_meta, 'base64')
-          .feeBump()
-          .tx()
-          .feeSource()
-    );
-""";
-
-WITH fee_bump_transactions AS (
-    SELECT batch_run_date, transaction_hash, tx_envelope AS tx_meta
-    FROM `test_crypto_stellar.history_transactions`
-    WHERE batch_run_date BETWEEN DATETIME("2024-07-01") AND DATETIME_ADD("2024-07-20", INTERVAL 1 MONTH)
-    AND inner_transaction_hash IS NOT NULL -- filter in fee bump transactions
-),
-calculated_fee_account AS (
-    SELECT batch_run_date, transaction_hash, getFeeBumpAccountIfExists(tx_meta) AS fee_account
-    FROM fee_bump_transactions
-),
-calculated_fee_muxed_account AS (
-    SELECT batch_run_date, transaction_hash, fee_account
-    FROM calculated_fee_account
-    WHERE fee_account LIKE 'M%' -- muxed accounts
-)
-SELECT batch_run_date, transaction_hash, fee_account AS fee_account_muxed
-FROM calculated_fee_muxed_account
-```
-
-### Salida de ejemplo para el JS UDF
-
-Después de ejecutar la consulta anterior, deberías recibir una salida similar a la siguiente:
-
-| Fila | transaction_hash                                                 | fee_account_muxed                                                     |
-| ---- | ---------------------------------------------------------------- | --------------------------------------------------------------------- |
-| 1    | f5f5b0aaf758896ef8c5b4807f41c77d15c11977eecf2b0e4769d777324a2d11 | MCBD54KAHHA4AK4DOZWOSX5O5OZ4OI54N24QITDSFLPD7EG2WY2AMAAACYGGCDRL6UBUA |
-| 2    | a9e49dff6202663633b83f3645fbf8c2cfeb915db99b2b884a86791b9f8eae2f | MBX64B6V7KV2KVHJ66IIKLNEIKCHF5BI57BNMF3U6RJIUHNBMXSJEAAACYGGCDRL6UFO2 |
-| 3    | 00dba50c8689477e6990103338a0eb326725e07a7b7ff187359abf11c23c582a | MC5BEU3DCIMHOHRQDVDAPEPZGMBBALPJ3IQY23VTXC3454SQMNWVSAAACYGGCDRL6UX42 |
-| 4    | 2e1c53a9fe1d48ddc493febe467178994e669e3eebf3a4cca646b3cb666616de | MAMYAUW45TC54C3QORQP7OOFYKOXCJTXOG2WIV5LP2HDMR67MWP6IAAACYGGCDRL6VCZM |
-
-## Paso 4: Actualizando Valores de Columna Usando UDF
-
-También puedes usar este UDF para actualizar valores en una tabla de BigQuery. Aquí tienes un ejemplo de cómo hacerlo:
-
-```sql
-CREATE TEMP FUNCTION getFeeBumpAccountIfExists(tx_meta STRING)
-RETURNS STRING
-LANGUAGE js
-OPTIONS (
-  library=["gs://stellar-test-js-udf/stellar-base.min.js"]
-)
-AS r"""
-    let txe = StellarBase.xdr.TransactionEnvelope.fromXDR(tx_meta, 'base64');
-    let tx = txe.feeBump();
-    let sourceAccount = StellarBase.encodeMuxedAccountToAddress(tx.tx().feeSource());
-    return sourceAccount
-""";
-
-MERGE `crypto_stellar.history_transactions` AS target
-USING (
-  WITH fee_bump_transactions AS (
-    SELECT batch_run_date, transaction_hash, tx_envelope AS tx_meta
-    FROM `crypto_stellar.history_transactions`
-    WHERE batch_run_date > '2020-08-03'
-      AND batch_run_date < '2020-08-05'
-      AND inner_transaction_hash IS NOT NULL
-  ),
-  calculated_fee_account AS (
-    SELECT batch_run_date, transaction_hash, getFeeBumpAccountIfExists(tx_meta) AS fee_account
-    FROM fee_bump_transactions
-  ),
-  calculated_fee_muxed_account AS (
-    SELECT batch_run_date, transaction_hash, fee_account
-    FROM calculated_fee_account
-    WHERE fee_account LIKE 'M%' -- muxed accounts
-  )
-  SELECT batch_run_date, transaction_hash, fee_account AS fee_account_muxed
-  FROM calculated_fee_muxed_account
-) AS source
-ON target.batch_run_date = source.batch_run_date
-   AND target.transaction_hash = source.transaction_hash
-WHEN MATCHED THEN
-  UPDATE SET target.fee_account_muxed = source.fee_account_muxed;
-```
-
-Esta consulta actualizará el campo `fee_account_muxed` en la tabla crypto_stellar.history_transactions utilizando valores calculados desde el UDF.
-
-## Conclusión
-
-Al seguir estos pasos, podrás extraer y manipular efectivamente los campos de datos XDR en BigQuery utilizando UDFs de JavaScript, facilitando el procesamiento y análisis de los datos de tu red Stellar. También puedes aplicar la corrección para el conjunto de datos existente.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/README.mdx
deleted file mode 100644
index aa53ab1e32..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Rellenar
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Una vez que hayas configurado tu programación y orquestación, es posible que encuentres los siguientes escenarios:
-
-| Caso de Uso                          | Descripción                                                                                                                              | Solución                                                                                                                                                                                                                                                                                           |
-| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Relleno Inicial                      | Acabas de configurar Hubble y te gustaría ingerir datos históricos                                                                       | - Opción 1. [Importación de Datos](../../developer-guide/backfill/data-import.mdx) <br></br> **Pros:** Barato y rápido <br></br>- Opción 2: Reactivar los DAG para fechas pasadas <br></br> **Contras:** Lento y caro                                                                              |
-| Corrección de Errores                | Has resuelto un error y necesitas reingerir una columna de datos específica o corregir una columna de datos                              | - Opción 1. [JS UDF](../../developer-guide/backfill/JS-UDF.mdx) <br></br> **Pros:** Barato y rápido <br></br> **Contras:** Puede necesitar escritura de consultas optimizadas y ejecución en lotes <br></br> - Opción 2: Reactivar los DAG para fechas pasadas <br></br> **Contras:** Lento y caro |
-| Extracción de nueva columna de datos | Has añadido una nueva columna de datos como parte de una solicitud de funciones y necesitas rellenar datos para la nueva columna añadida | - Opción 1. [JS UDF](../../developer-guide/backfill/JS-UDF.mdx) <br></br> **Pros:** Barato y rápido <br></br> **Contras:** Puede necesitar escritura de consultas optimizadas y ejecución en lotes <br></br> - Opción 2: Reactivar los DAG para fechas pasadas <br></br> **Contras:** Lento y caro |
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/data-import.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/data-import.mdx
deleted file mode 100644
index cc912beed8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/backfill/data-import.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Importación de Datos
-sidebar_position: 0
----
-
-Este documento describe métodos para realizar un respaldo inicial al configurar hubble.
-
-# Usar SDF ETL Data como Fuente
-
-## 1. Exportar Datos a Almacenamiento en la Nube y Cargar Datos en BigQuery
-
-- Usa el comando [EXPORT](https://cloud.google.com/bigquery/docs/reference/standard-sql/export-statements) proporcionado por Google Cloud Platform (GCP) para exportar tu conjunto de datos en el formato requerido (por ejemplo, Avro, Parquet).
-- Usa el comando [LOAD](https://cloud.google.com/bigquery/docs/reference/standard-sql/load-statements) para cargar los archivos exportados en tu conjunto de datos de BigQuery.
-
-#### Ejemplo:
-
-```sql
-EXPORT DATA OPTIONS(
-  uri='gs://my-bucket/history-transactions/*',
-  format='PARQUET',
-  overwrite=true) AS
-SELECT * FROM crypto-stellar.crypto_stellar.history_transactions;
-
-LOAD DATA INTO mydataset.transactions
-  FROM FILES(
-    format='PARQUET',
-    uris = ['gs://my-bucket/history-transactions/*']
-  )
-  WITH PARTITION COLUMNS;
-```
-
-## 2. Usa la API / Consola de BigQuery para reflejar el conjunto de datos de SDF
-
-La Stellar Development Foundation proporciona acceso público a los datos totalmente transformados de la red Stellar a través de los conjuntos de datos y tablas públicas en GCP BigQuery. Las instrucciones sobre cómo acceder a estos datos se pueden encontrar en la sección de [Conexión](../../developer-guide/connecting-to-bigquery/README.mdx).
-
-Usa la declaración [Create Table Copy](https://cloud.google.com/bigquery/docs/reference/standard-sql/data-definition-language#create_table_copy) para copiar datos entre conjuntos de datos.
-
-```sql
-CREATE [ OR REPLACE ] TABLE [ IF NOT EXISTS ] table_name
-COPY source_table_name
-...
-[OPTIONS(table_option_list)]
-```
-
-# Usar Galexie como fuente
-
-[Galexie](../../../../indexers/build-your-own/galexie/README.mdx) es una herramienta para extraer, procesar y exportar metadatos del ledger Stellar a almacenamiento externo, creando un lago de datos de metadatos del ledger preprocesados. Esta es una fuente de datos ascendente para Hubble, útil cuando tienes un pipeline personalizado de Stellar-ETL.
-
-**Pasos**
-
-1. Asegúrate de proporcionar el valor correcto para datastore-path en los [flags de comando](https://github.com/stellar/stellar-etl/tree/master?tab=readme-ov-file#common-flags) de Stellar-ETL. Esto representa el nombre del bucket donde tu instancia de Galexie genera metadatos de cierre del ledger.
-2. Configura un [sistema de orquestación como Airflow](../../developer-guide/scheduling-and-orchestration/getting-started.mdx).
-3. En tu instancia de Airflow, activa el DAG history_table_export para fechas anteriores.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx
deleted file mode 100644
index bc7b4a3609..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/connecting-to-bigquery/README.mdx
+++ /dev/null
@@ -1,144 +0,0 @@
----
-title: Conectando
-sidebar_position: 10
----
-
-BigQuery ofrece múltiples métodos de conexión a Hubble. Esta guía detalla tres métodos comunes:
-
-- [BigQuery UI](#bigquery-ui) - analistas que necesitan realizar análisis ad hoc usando SQL
-- [BigQuery SDK](#bigquery-sdk) - desarrolladores que necesitan integrar datos en aplicaciones
-- [Looker Studio](#looker-studio) - personas de negocios que necesitan visualizar datos
-
-## Requisitos previos
-
-Para acceder a Hubble, necesitarás un Proyecto de Google Cloud con facturación y la API de BigQuery habilitada. Para más información, sigue las instrucciones proporcionadas por [Google Cloud](https://cloud.google.com/bigquery/docs/quickstarts/query-public-dataset-console).
-
-Google ofrece una Sandbox de BigQuery de forma gratuita que permite a los usuarios explorar conjuntos de datos en una capacidad limitada.
-
-## Interfaz de usuario de BigQuery
-
-1. Desde un navegador, abre el conjunto de datos [crypto-stellar.crypto_stellar](http://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar).
-2. Esto abrirá el conjunto de datos público `crypto_stellar`, donde podrás navegar por su contenido en el panel **Explorer**.
-3. Haz clic en el ícono de **estrella** en el panel Explorer. Esto marcará el conjunto de datos como favorito para ti. Puedes encontrar más información detallada sobre cómo marcar recursos [aquí](https://cloud.google.com/bigquery/docs/bigquery-web-ui#star_resources).
-
-:::note
-
-¡Hubble no se encuentra en el panel Explorer! No puedes buscar el conjunto de datos. Para ver el conjunto de datos, **debes** usar el [enlace del conjunto de datos](https://console.cloud.google.com/bigquery?ws=!1m4!1m3!3m2!1scrypto-stellar!2scrypto_stellar).
-
-:::
-
-Copia y pega la siguiente consulta de ejemplo en el Editor:
-
-<CodeExample>
-
-```sql
-select
-  account_id,
-  balance
-from `crypto-stellar.crypto_stellar.accounts_current`
-order by balance desc;
-```
-
-</CodeExample>
-
-Esta consulta devolverá los saldos de XLM para todas las direcciones de billeteras Stellar, ordenados de mayor a menor cantidad.
-
-## SDK de BigQuery
-
-Existen múltiples [Bibliotecas de Clientes de BigQuery API](https://cloud.google.com/bigquery/docs/reference/libraries) disponibles.
-
-El siguiente ejemplo utiliza Python para acceder al conjunto de datos Hubble. Utiliza [esta guía](https://cloud.google.com/python/docs/setup) para obtener ayuda sobre cómo configurar un entorno de desarrollo en Python.
-
-Instala la biblioteca cliente localmente y configura tu entorno para usar tu Proyecto de Google Cloud:
-
-<CodeExample>
-
-```bash
-# verify python version
-python3 --version
-# if you do not have pip, install it
-python -m pip install --upgrade pip
-
-# install bigquery client library
-pip install --upgrade google-cloud-bigquery
-gcloud config set project PROJECT_ID
-```
-
-</CodeExample>
-
-Utiliza el intérprete de Python para ejecutar el siguiente ejemplo y listar las tablas disponibles en Hubble:
-
-<CodeExample>
-
-```python
-from google.cloud import bigquery
-
-# Construct a BigQuery client object.
-client = bigquery.Client()
-
-dataset_id = 'crypto-stellar.crypto_stellar'
-
-# Make an API request
-tables = client.list_tables(dataset_id)
-
-# List the tables found in Hubble
-print(f'Tables contained in {dataset_id}':)
-for table in tables:
-    print(f'{table.project}.{table.dataset_id}.{table.table_id}')
-```
-
-</CodeExample>
-
-Ejecuta el siguiente ejemplo para realizar una consulta y mostrar los resultados:
-
-<CodeExample>
-
-```python
-from google.cloud import bigquery
-
-# Construct a BigQuery client object.
-client = bigquery.Client()
-
-query = """
-SELECT
- account_id,
- balance,
-FROM `crypto-stellar.crypto_stellar.accounts_current`
-ORDER BY balance DESC
-LIMIT 10;
-"""
-
-# Make an API request
-query_job = client.query(query)
-
-print("The query data:")
-for row in query_job:
-    # Row values can be accessed by field name or index.
-    print(f'account_id={row[0]}, balance={row["balance"]}')
-```
-
-</CodeExample>
-
-Hay varias formas de extraer y cargar datos usando BigQuery. Consulta la [Documentación del Cliente de BigQuery](https://cloud.google.com/python/docs/reference/bigquery/latest/google.cloud.bigquery.client.Client) para más información.
-
-## Looker Studio
-
-[Looker Studio](https://cloud.google.com/looker-studio) es una herramienta de inteligencia empresarial que se puede utilizar para conectarse y visualizar datos del conjunto de datos Hubble.
-
-Para conectar Hubble como fuente de datos:
-
-1. Abre [Looker Studio](https://lookerstudio.google.com/)
-2. Haz clic en **Crear** > **Fuente de datos**
-3. Busca el conector de BigQuery
-4. _(Opcional)_ Cambia el nombre de la fuente de datos en la parte superior de la página web
-5. Haz clic en _Proyectos compartidos_ > Selecciona tu Proyecto de Google Cloud
-6. Introduce `crypto-stellar` como el nombre del Proyecto compartido
-7. Haz clic en el Conjunto de datos `crypto_stellar`
-8. Selecciona la tabla deseada para conectar
-9. Haz clic en `CONECTAR` en la parte superior derecha de la página web.
-
-¡Y ya estás conectado!
-
-Puedes encontrar información general sobre Looker Studio [aquí](https://support.google.com/looker-studio/).
-
-Puedes encontrar información general sobre cómo conectar fuentes de datos [aquí](https://support.google.com/looker-studio/topic/6370331?hl=en&ref_topic=7441382&sjid=14945902445646860578-NA).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/README.mdx
deleted file mode 100644
index 4d16d01231..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Curación de Datos
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Ejecutando stellar-dbt-public para transformar datos en bruto de la red Stellar en algo mejor.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/architecture.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/architecture.mdx
deleted file mode 100644
index 6a227a1d5e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/architecture.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Arquitectura
-sidebar_position: 10
----
-
-import stellar_dbt_arch from "/img/hubble/stellar_dbt_architecture.png";
-
-## Descripción general de la arquitectura
-
-<img src={stellar_dbt_arch} width="300" />
-
-En general, stellar-dbt-public se ejecuta por:
-
-- Seleccionar un modelo de dbt para ejecutar
-- Dentro de la ejecución del modelo:
-  - Las fuentes se referencian y se utilizan para crear tablas de preparación
-  - Las tablas de preparación luego pasan por varias transformaciones y se almacenan en tablas intermedias
-  - Los toques finales y las uniones se realizan en las tablas intermedias, que producen las tablas finales amigables para el análisis
-
-Tratamos de adherirnos a las prácticas recomendadas establecidas por la [dbt docs](https://docs.getdbt.com/docs/build/projects)
-
-Información más detallada sobre stellar-dbt-public y ejemplos se puede encontrar en el repositorio de [stellar-dbt-public](https://github.com/stellar/stellar-dbt-public/tree/master).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/getting-started.mdx
deleted file mode 100644
index 00f1570e0d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/getting-started.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-title: Comenzar
-sidebar_position: 20
----
-
-[repositorio de GitHub stellar-dbt-public](https://github.com/stellar/stellar-dbt-public/tree/master)
-
-## Uso Recomendado
-
-### Importar stellar-dbt-public como un paquete de dbt
-
-Si necesitas crear tus propios modelos sobre stellar-dbt-public, puedes importar stellar-dbt-public como un paquete dbt en un proyecto dbt separado.
-
-Instrucciones de ejemplo:
-
-- Crea un nuevo archivo `packages.yml` en tu proyecto dbt (no en el proyecto stellar-dbt-public) con el siguiente yml
-
-```
-packages:
-  - git: "https://github.com/stellar/stellar-dbt-public.git"
-    revision: v0.0.28
-```
-
-- (Opcional) Actualiza tu profiles.yml para incluir configuraciones de perfil para stellar-dbt-public
-
-```
-new_project:
-  target: test
-  outputs:
-    test:
-      project: <project>
-      dataset: <dataset>
-      <other configurations>
-
-stellar_dbt_public:
-  target: test
-  outputs:
-    test:
-      project: <project>
-      dataset: <dataset>
-      <other configurations>
-```
-
-- (Opcional) Actualiza tu dbt_project.yml para incluir configuraciones del proyecto para stellar-dbt-public
-
-```
-name: 'stellar_dbt'
-version: '1.0.0'
-config-version: 2
-
-profile: 'new_project'
-
-model-paths: ["models"]
-analysis-paths: ["analyses"]
-test-paths: ["tests"]
-seed-paths: ["seeds"]
-macro-paths: ["macros"]
-snapshot-paths: ["snapshots"]
-
-target-path: "target"
-clean-targets:
-  - "target"
-  - "dbt_packages"
-
-models:
-  new_project:
-    staging:
-      +materialized: view
-    intermediate:
-      +materialized: ephemeral
-    marts:
-      +materialized: table
-
-  stellar_dbt_public:
-    staging:
-      +materialized: ephemeral
-    intermediate:
-      +materialized: ephemeral
-    marts:
-      +materialized: table
-```
-
-- Los modelos del paquete/repositorio stellar-dbt-public estarán ahora disponibles en tu nuevo proyecto dbt
-
-## Construir y Ejecutar Localmente
-
-### Clonar el repositorio
-
-```
-git clone https://github.com/stellar/stellar-dbt-public
-```
-
-### Instalar paquetes de python requeridos
-
-```
-pip install --upgrade pip && pip install -r requirements.txt
-
-```
-
-### Instalar paquetes de dbt requeridos
-
-```
-dbt deps
-```
-
-### Ejecutar dbt
-
-- Hay muchos comandos útiles que vienen con dbt que se pueden encontrar en la [documentación de dbt](https://docs.getdbt.com/reference/dbt-commands#available-commands)
-- stellar-dbt-public está diseñado para usar el comando `dbt build`, que `ejecutará` el modelo y `probará` la salida de la tabla del modelo
-- (Opcional) ejecutar con la opción `--full-refresh`
-
-```
-dbt build --full-refresh
-```
-
-- Las ejecuciones subsiguientes pueden hacerse en modo incremental (solo inserta los datos más recientes en lugar de reconstruir toda la historia cada vez)
-
-```
-dbt build
-```
-
-- También puedes especificar solo un modelo si no quieres ejecutar todos los modelos de stellar-dbt-public
-
-```
-dbt build --select <model name or tag>
-```
-
-Por favor, consulta el directorio [stellar-dbt-public/modles/marts](https://github.com/stellar/stellar-dbt-public/tree/master/models/marts) para ver una lista completa de los modelos disponibles que dbt puede ejecutar
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/overview.mdx
deleted file mode 100644
index 38366cad92..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/data-curation/overview.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Descripción general
-sidebar_position: 0
----
-
-La curaduría de datos en Hubble se realiza a través de [stellar-dbt-public](https://github.com/stellar/stellar-dbt-public). stellar-dbt-public transforma los datos de la red Stellar desde conjuntos y tablas de BigQuery en agregados para análisis más amigables para el usuario.
-
-Vale la pena mencionar que la mayoría de los usuarios no necesitarán levantar y ejecutar su propia instancia de stellar-dbt-public. La Stellar Development Foundation proporciona acceso público a datos de la red Stellar completamente transformados a través de los conjuntos y tablas públicas en GCP BigQuery. Las instrucciones sobre cómo acceder a estos datos se pueden encontrar en la sección de [Conectar](../../developer-guide/connecting-to-bigquery/README.mdx).
-
-## ¿Por qué ejecutar stellar-dbt-public?
-
-Ejecutar stellar-dbt-public dentro de tu propia infraestructura ofrece una serie de beneficios. Puedes:
-
-- Tener control operacional total sin depender de la Stellar Development Foundation para obtener datos de la red
-- Ejecutar pipelines ETL/ELT modificados que se ajusten a tus necesidades comerciales individuales
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/README.mdx
deleted file mode 100644
index 521bd3b13f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Programación y Orquestación
-sidebar_position: 100
----
-
-import DocCardList from "@theme/DocCardList";
-
-Uniendo todos los componentes.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.mdx
deleted file mode 100644
index 038f30dbc8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/architecture.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Arquitectura
-sidebar_position: 10
----
-
-import stellar_etl_airflow_arch from "/img/hubble/stellar_etl_airflow_architecture.png";
-
-## Resumen de la Arquitectura
-
-<img src={stellar_etl_airflow_arch} width="300" />
-
-En general, stellar-etl-airflow se ejecuta mediante:
-
-- Planificación de DAGs para ejecutar `stellar-etl` y subir los datos generados a BigQuery
-- Planificación de DAGs para ejecutar `stellar-dbt-public` utilizando los datos en BigQuery
-  - Intentamos adherirnos a las prácticas recomendadas establecidas por la [documentación de dbt](https://docs.getdbt.com/docs/build/projects)
-
-Información más detallada sobre stellar-etl-airflow se puede encontrar en el repositorio de [stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow/tree/master).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.mdx
deleted file mode 100644
index e62334e05d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/getting-started.mdx
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Comenzar
-sidebar_position: 20
----
-
-import history_table_export from "/img/hubble/history_table_export.png";
-import state_table_export from "/img/hubble/state_table_export.png";
-import dbt_enriched_base_tables from "/img/hubble/dbt_enriched_base_tables.png";
-
-[repositorio de GitHub stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow/tree/master)
-
-## Configuración de cuenta de GCP
-
-La Stellar Development Foundation ejecuta Hubble en GCP utilizando Composer y BigQuery. Para seguir el mismo despliegue, necesitarás tener acceso al proyecto de GCP. Las instrucciones se pueden encontrar en la documentación de [Comenzar](https://cloud.google.com/docs/get-started) de Google.
-
-Nota: BigQuery y Composer deberían estar disponibles por defecto. Si no lo están, puedes encontrar instrucciones para habilitarlos en la documentación de Google sobre [BigQuery](https://cloud.google.com/bigquery?hl=en) o [Composer](https://cloud.google.com/composer?hl=en).
-
-## Crear instancia de GCP Composer para ejecutar Airflow
-
-Las instrucciones para crear una instancia de GCP Composer para ejecutar Hubble se pueden encontrar en la sección de [Instalación y Configuración](https://github.com/stellar/stellar-etl-airflow?tab=readme-ov-file#installation-and-setup) en el repositorio [stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow).
-
-:::note
-
-Los requisitos de hardware pueden variar considerablemente dependiendo de los datos de la red Stellar que requieras. La configuración por defecto de GCP puede ser más alta/baja de lo realmente necesario.
-
-:::
-
-## Configurando GCP Composer Airflow
-
-Se requieren dos cosas para la configuración y el establecimiento de GCP Composer Airflow:
-
-- Subir DAGs al Bucket de Composer Airflow
-- Configurar las variables de Airflow para tu configuración de GCP
-
-Para instrucciones más detalladas, consulta la documentación de [Instalación y Configuración de stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow?tab=readme-ov-file#installation-and-setup).
-
-### Subiendo DAGs
-
-Dentro del repositorio [stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow) hay un script de shell [upload_static_to_gcs.sh](https://github.com/stellar/stellar-etl-airflow/blob/master/upload_static_to_gcs.sh) que subirá todos los DAGs y esquemas a tu bucket de Composer Airflow.
-
-Esto también se puede hacer utilizando el [CLI de gcloud o la consola](https://cloud.google.com/storage/docs/uploading-objects) y seleccionando manualmente los DAGs y esquemas que deseas subir.
-
-### Configurando Variables de Airflow
-
-Por favor, consulta la documentación de [Explicación de Variables de Airflow](https://github.com/stellar/stellar-etl-airflow?tab=readme-ov-file#airflow-variables-explanation) para más información sobre qué debería y necesita configurarse.
-
-## Ejecutando los DAGs
-
-Para ejecutar un DAG, solo tienes que alternar el DAG encendido/apagado como se ve a continuación
-
-![Alternar DAGs](/img/hubble/airflow_dag_toggle.png)
-
-Se puede encontrar más información sobre cada DAG en la documentación de [Diagramas de DAG](https://github.com/stellar/stellar-etl-airflow?tab=readme-ov-file#dag-diagrams).
-
-## DAGs Disponibles
-
-Más información se puede encontrar [aquí](https://github.com/stellar/stellar-etl-airflow/blob/master/README.md#public-dags)
-
-### DAG de Exportación de Tabla de Historial
-
-[Este DAG](https://github.com/stellar/stellar-etl-airflow/blob/master/dags/history_tables_dag.py):
-
-- Exporta parte de las fuentes: ledgers, operaciones, transacciones, intercambios, efectos y activos desde Stellar utilizando el lago de datos de archivos LedgerCloseMeta
-  - Opcionalmente, esto puede ingerir datos utilizando captive-core pero eso no es ideal ni recomendado para uso con Airflow
-- Inserta en BigQuery
-
-<img src={history_table_export} width="300" />
-
-### DAG de Exportación de Tabla de Estado
-
-[Este DAG](https://github.com/stellar/stellar-etl-airflow/blob/master/dags/state_table_dag.py)
-
-- Exporta cuentas, firmantes de cuentas, ofertas, balances reclamables, fondos de liquidez, líneas de confianza, datos de contratos, código de contrato, configuraciones y ttl.
-- Inserta en BigQuery
-
-<img src={state_table_export} width="300" />
-
-### DAG de Tablas Base Enriquecidas con DBT
-
-[Este DAG](https://github.com/stellar/stellar-etl-airflow/blob/master/dags/dbt_enriched_base_tables_dag.py)
-
-- Crea las vistas de staging de DBT para modelos
-- Actualiza la tabla enriched_history_operations
-- Actualiza las tablas de estado actuales
-- (Opcional) advertencias y errores se envían a slack.
-
-<img src={dbt_enriched_base_tables} width="300" />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx
deleted file mode 100644
index 0ff2b0e4f6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/scheduling-and-orchestration/overview.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Descripción general
-sidebar_position: 0
----
-
-Hubble utiliza [stellar-etl-airflow](https://github.com/stellar/stellar-etl-airflow) para programar y orquestar todos sus flujos de trabajo. Esto incluye la programación y ejecución de stellar-etl y stellar-dbt.
-
-Es importante tener en cuenta que la mayoría de los usuarios no necesitarán montar y ejecutar su propio Hubble. La Stellar Development Foundation proporciona acceso público a los datos a través de los conjuntos y tablas de datos públicos en GCP BigQuery. Las instrucciones sobre cómo acceder a estos datos se pueden encontrar en la sección de [Conexión](../../developer-guide/connecting-to-bigquery/README.mdx).
-
-## ¿Por qué ejecutar stellar-etl-ariflow?
-
-Ejecutar stellar-etl-airflow dentro de tu propia infraestructura proporciona una serie de beneficios. Puedes:
-
-- Tener control operativo completo sin depender de la Stellar Development Foundation para datos de red
-- Ejecutar tuberías ETL/ELT modificadas que se ajusten a tus necesidades comerciales individuales
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/README.mdx
deleted file mode 100644
index 6e420d115c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Ingesta del Sistema Fuente
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Ejecutando stellar-etl para la ingesta de datos de la red Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.mdx
deleted file mode 100644
index 7abfab3af3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/architecture.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Arquitectura
-sidebar_position: 10
----
-
-import stellar_arch from "/img/hubble/stellar_overall_architecture.png";
-import stellar_etl_arch from "/img/hubble/stellar_etl_architecture.png";
-
-## Descripción general de la arquitectura
-
-<img src={stellar_arch} width="600" />
-
-<img src={stellar_etl_arch} width="300" />
-
-En general, stellar-etl se ejecuta mediante:
-
-- Leer datos en bruto de la red Stellar
-- Esto se puede hacer ejecutando un comando de exportación de stellar-etl para exportar datos entre un ledger de inicio y uno de fin
-  - stellar-etl tiene la capacidad de leer de dos fuentes diferentes:
-    - Captive-core directamente para obtener LedgerCloseMeta
-    - Un lago de datos de archivos comprimidos LedgerCloseMeta del Ledger Exporter
-- Transforma el LedgerCloseMeta XDR en un formato JSON fácil de analizar
-- Opcionalmente, sube los archivos JSON a GCS o a cualquier otro servicio de almacenamiento en la nube
-
-Se puede encontrar información más detallada sobre stellar-etl y ejemplos en el repositorio [stellar-etl](https://github.com/stellar/stellar-etl/tree/master).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.mdx
deleted file mode 100644
index dc95a8134c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/getting-started.mdx
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Comenzar
-sidebar_position: 20
----
-
-[repositorio de GitHub de stellar-etl](https://github.com/stellar/stellar-etl/tree/master)
-
-[imágenes de docker de stellar/stellar-etl](https://hub.docker.com/r/stellar/stellar-etl)
-
-## Uso Recomendado
-
-Generalmente, si no necesitas modificar ningún código de stellar-etl, se recomienda utilizar las [imágenes de docker de stellar/stellar-etl](https://hub.docker.com/r/stellar/stellar-etl).
-
-Ejemplo para ejecutar localmente con docker:
-
-```
-docker run --platform linux/amd64 -ti stellar/stellar-etl:latest <parameters>
-```
-
-## Desarrollar y Ejecutar Localmente
-
-### Instalar Golang
-
-- Asegúrate de que tu versión de golang sea >= `1.22.1`
-  - Las instrucciones para instalar golang se pueden encontrar en [go.dev/doc/install](https://go.dev/doc/install)
-
-### Clona el repositorio
-
-```
-git clone https://github.com/stellar/stellar-etl
-```
-
-### Construir stellar-etl
-
-- Ejecuta `go build` en el repositorio clonado de stellar-etl
-
-```
-go build
-```
-
-### Ejecuta stellar-etl
-
-- Un ejecutable de `stellar-etl` debería haberse creado en tu repositorio de stellar-etl
-- Ejemplo de comando stellar-etl:
-
-```
-./stellar-etl export_ledgers -s 10 -e 11
-```
-
-Esto debería crear un archivo `exported_ledgers.txt` con la salida de los ledgers del 10 al 11:
-
-```
-{"base_fee":100,"base_reserve":100000000,"closed_at":"2024-02-06T17:34:12Z","failed_transaction_count":0,"fee_pool":0,"id":42949672960,"ledger_hash":"f7c89b35c50f74dc69eacd9dda8e9ec9f1af36b6a2928b77619c1beb5f5ca8d4","ledger_header":"AAAAAIGFrRh+oCo2QcAjG6IzWTlil89DNwYIwx6PrrmehujNf44MwMJZxPz3DJYHciV9ligoKwbmeiue4eM29CRWBJgAAAAAZcJtlAAAAAAAAAABAAAAANVyadliUPdJbQeb4ug1Ejbv/+jTnC4Gv6uxQh8X/GccAAAAQBW0ICM/1C7CML6ngZijKycAOIhzwGN6yUsznHznfJunIDyLLVF9/oqvLzP1vaGOhBf3Rmtm5WgGVgeLjlyJSAHfP2GYBKkv20BXGS3EPddI6neK3FK8SYzoBSTAFLgRGfBr+YHFQTIEJ0Y81WEOYClgyjOER8vd4qMQb3gM9nRvAAAACg3gtrOnZAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABkBfXhAAAAAGQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=","max_tx_set_size":100,"operation_count":0,"previous_ledger_hash":"8185ad187ea02a3641c0231ba23359396297cf43370608c31e8faeb99e86e8cd","protocol_version":0,"sequence":10,"soroban_fee_write_1kb":0,"successful_transaction_count":0,"total_coins":1000000000000000000,"transaction_count":0,"tx_set_operation_count":"0"}
-{"base_fee":100,"base_reserve":100000000,"closed_at":"2024-02-06T17:34:17Z","failed_transaction_count":0,"fee_pool":0,"id":47244640256,"ledger_hash":"5b9ac11c6040f4e2fa6a120b3dee9a4b338b7a25bcb8437dab0c0a5c557a41f5","ledger_header":"AAAAAPfImzXFD3TcaerNndqOnsnxrza2opKLd2GcG+tfXKjUK858NP5gM0pneHF0nRowsJBAzMwWDx0+tmbYIZkIT+8AAAAAZcJtmQAAAAAAAAABAAAAANVyadliUPdJbQeb4ug1Ejbv/+jTnC4Gv6uxQh8X/GccAAAAQDhZKPKBdeD4Sthcu+EsuzEtSyiXzXkHboOsgYT1tuV/juZyKqgrsVmg+RmMoRun+NKCdcB8LV9gaehiFm+XDgnfP2GYBKkv20BXGS3EPddI6neK3FK8SYzoBSTAFLgRGfBr+YHFQTIEJ0Y81WEOYClgyjOER8vd4qMQb3gM9nRvAAAACw3gtrOnZAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABkBfXhAAAAAGQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=","max_tx_set_size":100,"operation_count":0,"previous_ledger_hash":"f7c89b35c50f74dc69eacd9dda8e9ec9f1af36b6a2928b77619c1beb5f5ca8d4","protocol_version":0,"sequence":11,"soroban_fee_write_1kb":0,"successful_transaction_count":0,"total_coins":1000000000000000000,"transaction_count":0,"tx_set_operation_count":"0"}
-```
-
-## Comandos de stellar-etl
-
-### export_ledgers
-
-```
-stellar-etl export_ledgers --start-ledger 1000 --end-ledger 500000 --output exported_ledgers.txt
-```
-
-Este comando exporta ledgers dentro del rango proporcionado.
-
-### export_transactions
-
-```
-stellar-etl export_transactions --start-ledger 1000 --end-ledger 500000 --output exported_transactions.txt
-```
-
-Este comando exporta transacciones dentro del rango proporcionado.
-
-### export_operations
-
-```
-stellar-etl export_operations --start-ledger 1000 --end-ledger 500000 --output exported_operations.txt
-```
-
-Este comando exporta operaciones dentro del rango proporcionado.
-
-### export_effects
-
-```
-stellar-etl export_effects --start-ledger 1000 --end-ledger 500000 --output exported_effects.txt
-```
-
-Este comando exporta efectos dentro del rango proporcionado.
-
-### export_assets
-
-```
-stellar-etl export_assets --start-ledger 1000 --end-ledger 500000 --output exported_assets.txt
-```
-
-Exporta los activos que se crean a partir de operaciones de pago sobre un rango de ledger especificado.
-
-### export_trades
-
-```
-stellar-etl export_trades --start-ledger 1000 --end-ledger 500000 --output exported_trades.txt
-```
-
-Exporta datos de comercio dentro del rango especificado a un archivo de salida
-
-### export_diagnostic_events
-
-```
-stellar-etl export_diagnostic_events --start-ledger 1000 --end-ledger 500000 --output export_diagnostic_events.txt
-```
-
-Exporta datos de eventos de diagnóstico dentro del rango especificado a un archivo de salida
-
-### export_ledger_entry_changes
-
-```
-stellar-etl export_ledger_entry_changes --start-ledger 1000 --end-ledger 500000 --output exported_changes_folder/
-```
-
-Este comando exporta los cambios en ledgers dentro del rango de ledger proporcionado.
-
-Nota que este comando también exportará cada cambio de estado para cada tipo de entrada de ledger. [Información](https://github.com/stellar/stellar-etl?tab=readme-ov-file#export_ledger_entry_changes) sobre opciones para solo exportar tipos de entrada de ledger específicos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx
deleted file mode 100644
index 74aca3a688..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/source-system-ingestion/overview.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Resumen
-sidebar_position: 0
----
-
-La ingesta de datos de la red Stellar en Hubble se realiza a través de [stellar-etl](https://github.com/stellar/stellar-etl/tree/master). stellar-etl lee y transforma datos de la red Stellar en archivos JSON compatibles con OLAP.
-
-| Caso de uso                                                                                               | Solución recomendada                                                                                                                                          | Razón                                                                                                                                                                                                                                                                                                                              |
-| --------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Necesitas campos de datos comúnmente requeridos y no deseas asumir la carga de configurar toda la tubería | Usa la salida de la instancia stellar-etl de SDF, es decir, [Conectar a Bigquery y acceder a Hubble](../../developer-guide/connecting-to-bigquery/README.mdx) | Vale la pena notar que la mayoría de los usuarios no necesitarán levantar y ejecutar su propia instancia stellar-etl. La Stellar Development Foundation proporciona acceso público a datos de la red Stellar completamente transformados a través de los conjuntos de datos y tablas públicas en GCP BigQuery.                     |
-| Necesitas datos personalizados pero no quieres asumir la carga de configurar toda la tubería              | Usa [JS-UDF](../../developer-guide/backfill/JS-UDF.mdx)                                                                                                       | Stellar-ETL no analiza cada campo disponible en crudo XDR, pero guarda la metadata de la transacción cruda. JS-UDF ayuda a extraer un campo directamente de XDR                                                                                                                                                                    |
-| Necesitas datos personalizados y operativamente independientes                                            | Ejecuta [stellar-etl](https://github.com/stellar/stellar-etl/tree/master)                                                                                     | Ejecutar stellar-etl dentro de tu propia infraestructura ofrece una serie de beneficios. Puedes: <br></br> - Tener control operativo total sin depender de la Stellar Development Foundation para obtener datos de red <br></br> - Ejecutar tuberías ETL/ELT modificadas que se ajusten a las necesidades de tu negocio individual |
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/README.mdx
deleted file mode 100644
index fb725daa5f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Visualización
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Visualizando datos de la red Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/getting-started.mdx
deleted file mode 100644
index 41d8ddf478..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/getting-started.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Comenzar
-sidebar_position: 20
----
-
-Esta sección trata sobre el uso de [Google's Looker Studio](https://lookerstudio.google.com/u/0/navigation/reporting) como una herramienta de visualización gratuita y fácil de usar a la que puedes conectar los datos de tu red Stellar en BigQuery.
-
-Hay muchas otras herramientas de visualización gratuitas/de pago disponibles. Hubble es compatible con cualquier herramienta de visualización que tenga un conector de BigQuery.
-
-## Crear tu primera visualización
-
-- Sigue la [Guía de Inicio Rápido de Google](https://support.google.com/looker-studio/answer/9171315?hl=en)
-
-## Conectar Fuentes de Datos
-
-A continuación, se utilizarán los conjuntos de datos y tablas públicas de la Stellar Development Foundation como ejemplo para conectar fuentes de datos a Looker Studio
-
-- Haz clic en `Crear` en [Google's Looker Studio](https://lookerstudio.google.com/u/0/navigation/reporting)
-- Haz clic en `Fuente de Datos`
-- Encuentra el conector de `BigQuery`
-- Usa el proyecto `crypto-stellar`
-- Usa el conjunto de datos `crypto_stellar`
-- Selecciona la tabla de interés
-- Haz clic en `CONECTAR`
-
-Cuando crees un nuevo informe, deberías poder acceder a los datos de `crypto-stellar.crypto_stellar.<nombre de la tabla>`
-
-## Hacer tu primer gráfico de pastel
-
-- Haz clic en `Crear` en [Google's Looker Studio](https://lookerstudio.google.com/u/0/navigation/reporting)
-- Haz clic en `Informe`
-- Haz clic en `Mis fuentes de datos`
-- Haz clic en la fuente de datos que agregaste arriba
-- Una tabla de los datos debería aparecer en un nuevo informe
-- Haz clic en la tabla
-- Haz clic en `Gráfico` en la barra lateral derecha
-- Haz clic en la imagen de `Gráfico de pastel`
-
-Ahora has creado un nuevo informe con un gráfico de pastel.
-
-Looker Studio tiene muchos recursos para ayudar a visualizar y explorar datos. Aprende más [aquí](https://support.google.com/looker-studio?sjid=9035399711189270749-NA#topic=6267740)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/overview.mdx
deleted file mode 100644
index 3e07c411e0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/analytics/hubble/developer-guide/visualization/overview.mdx
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Resumen
-sidebar_position: 0
----
-
-Hay varias maneras de visualizar datos de Hubble. La siguiente sección describirá los pasos para usar [Google's Looker Studio](https://cloud.google.com/looker-studio?hl=en) para ayudar a visualizar datos de la red Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/README.mdx
deleted file mode 100644
index 67d75aab73..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/README.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Descripción general de las APIs
-sidebar_position: 0
----
-
-Conoce los servicios que proporcionan acceso a datos en tiempo real de la red Stellar
-
-| Características                | RPC | Horizon |
-| ------------------------------ | --- | ------- |
-| Datos en tiempo real           | ✅   | ✅       |
-| Datos históricos               | ❌   | ❌\*     |
-| Contratos inteligentes         | ✅   | ❌       |
-| Simulación de transacciones    | ✅   | ❌       |
-| Datos curados y procesados     | ❌   | ✅       |
-
-\*_Ten en cuenta que Horizon puede proporcionar datos históricos completos pero no es la herramienta recomendada para el acceso completo a datos históricos. Por favor utiliza [Hubble](../analytics/hubble/README.mdx) o [Galexie](../indexers/build-your-own/galexie/README.mdx) en su lugar._
-
-## [RPC](./rpc/README.mdx)
-
-El RPC proporciona acceso en tiempo real al estado actual de la red Stellar, incluyendo saldos de cuentas, estados de contratos inteligentes y consultas de transacciones recientes (dentro de una ventana de retención de siete días), mientras también permite la presentación de transacciones. Está diseñado para ser simple, mínimo y escalable, lo que lo hace ideal para aplicaciones y billeteras que requieren disponibilidad de datos en vivo.
-
-:::note
-
-RPC es la API recomendada para acceder e interactuar con los datos de la red Stellar en tiempo real.
-
-:::
-
-## [Horizon](./horizon/README.mdx)
-
-:::warning
-
-Horizon se considera obsoleta en favor de Stellar RPC. Aunque seguirá recibiendo actualizaciones para mantener la compatibilidad con las próximas versiones del protocolo, no recibirá un desarrollo significativo de nuevas funciones.
-
-:::
-
-Horizon es una API para acceder e interactuar con los datos de la red Stellar.
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
deleted file mode 100644
index 9a800b8226..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-sidebar_position: 60
-title: Proveedores
----
-
-:::info
-
-El 1 de agosto de 2024, los datos históricos en Horizon alojado por SDF y accesible públicamente fueron truncados a un año. Esa actualización optimizó el rendimiento del Horizon accesible públicamente y aseguró una experiencia fluida para todos los usuarios. Considera proveedores de ecosistemas de terceros de Horizon, que pueden proporcionar una ventana de retención de historial más larga así como otras características.
-
-:::
-
-:::warning
-
-Horizon se considera obsoleto en favor de Stellar RPC. Aunque seguirá recibiendo actualizaciones para mantener la compatibilidad con las próximas versiones del protocolo, no recibirá desarrollo de nuevas funcionalidades significativas.
-
-:::
-
-Múltiples proveedores de infraestructura han puesto a disposición los servicios de Stellar RPC y Horizon, y ofrecen planes que van desde gratuitos hasta instancias dedicadas. Estos proveedores pueden ser utilizados para desarrollo, pruebas y producción.
-
-Estos proveedores permiten acceder a la red Futurenet, Testnet y Mainnet.
-
-| Proveedor                                                       | Futurenet | Testnet | Mainnet | Horizon | RPC |
-| --------------------------------------------------------------- | --------- | ------- | ------- | ------- | --- |
-| [Blockdaemon\*†](https://www.blockdaemon.com/apply/soroban)     | ❌         | ✅       | ✅       | ✅       | ✅   |
-| [Validation Cloud\*†](https://www.validationcloud.io/stellar)   | ❌         | ✅       | ✅       | ✅       | ✅   |
-| [QuickNode\*](https://www.quicknode.com/docs/stellar)           | ❌         | ✅       | ✅       | ✅       | ✅   |
-| [NowNodes](https://nownodes.io/nodes/stellar-xlm)               | ✅         | ✅       | ✅       | ❌       | ✅   |
-| [Gateway](https://gateway.fm/public-rpc/)                       | ❌         | ✅       | ✅       | ❌       | ✅   |
-| [Ankr](https://www.ankr.com/rpc/advanced-api/)                  | ❌         | ✅       | ✅       | ✅       | ✅   |
-| [Infstones](https://infstones.com/)                             | ❌         | ❌       | ✅       | ❌       | ✅   |
-| [Obsrvr](https://www.withObsrvr.com/)                           | ❌         | ✅       | ✅       | ✅       | ✅   |
-| [GetBlock](https://getblock.io/nodes/xlm/)                      | ❌         | ❌       | ✅       | ❌       | ✅   |
-| [Nodies](https://nodies.org)                                    | ❌         | ✅       | ✅       | ✅       | ✅   |
-| [OnFinality](https://onfinality.io/networks/stellar)            | ❌         | ❌       | ✅       | ❌       | ✅   |
-| [Lightsail Network - Quasar](https://quasar.lightsail.network/) | ❌         | ❌       | ✅       | ❌       | ✅   |
-
-\*_Blockdaemon, Validation Cloud y Quicknode combinan Horizon y RPC en el mismo endpoint._
-
-†_Blockdaemon y Validation Cloud proporcionan datos históricos completos para Horizon._
-
-### APIs accesibles públicamente
-
-| Proveedor                                                       | Red           | URL                                                                                              |
-| --------------------------------------------------------------- | ------------- | ------------------------------------------------------------------------------------------------ |
-| [Liquify](https://www.liquify.io/)                              | Futurenet     | RPC: `https://stellar.liquify.com/api=41EEWAH79Y5OCGI7/futurenet`                                |
-|                                                                 | Testnet       | RPC: `https://stellar.liquify.com/api=41EEWAH79Y5OCGI7/testnet`                                  |
-|                                                                 | Mainnet       | RPC: `https://stellar-mainnet.liquify.com/api=41EEWAH79Y5OCGI7/mainnet`                          |
-| [Gateway](https://gateway.fm/)                                  | Testnet       | RPC: `https://soroban-rpc.testnet.stellar.gateway.fm`                                            |
-|                                                                 | Mainnet       | RPC: `https://soroban-rpc.mainnet.stellar.gateway.fm`                                            |
-| [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` <br /> Horizon: `https://horizon-futurenet.stellar.org` |
-|                                                                 | Testnet       | RPC: `https://soroban-testnet.stellar.org` <br /> 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`                                                  |
-| [Lightsail Network - Quasar](https://quasar.lightsail.network/) | Red principal | RPC `https://rpc.lightsail.network/`                                                             |
-|                                                                 | Red principal | RPC completo de archivo: `https://archive-rpc.lightsail.network/`                                |
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
deleted file mode 100644
index 2de4d2300a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: "Acceder a datos de Blockchain con la API de Horizon: Consultar transacciones, cuentas y más"
-sidebar_label: Horizonte
-sidebar_position: 10
-description: Aprende cómo Horizon, la API para la red Stellar, permite el acceso a datos de blockchain. Descubre los endpoints para consultar transacciones, cuentas y más.
----
-
-# Introducción a Horizon
-
-:::info
-
-El 1 de agosto de 2024, los datos históricos del Horizon alojado por el SDF accesibles públicamente fueron truncados a un año. Esa actualización optimizó el rendimiento del Horizon accesible públicamente y aseguró una experiencia fluida para todos los usuarios. Considera a los proveedores de ecosistemas de terceros de Horizon, que pueden ofrecer una ventana de retención de historial más larga así como otras características.
-
-:::
-
-Horizon proporciona una API HTTP para datos en la red Stellar. Recoge y vuelve a servir los datos producidos por la red Stellar en una forma que es más fácil de consumir para la aplicación promedio en relación con las representaciones de datos orientadas al rendimiento utilizadas por Stellar Core. Esta API sirve como puente entre aplicaciones y [Stellar Core](../../../validators/README.mdx). Proyectos como billeteras, intercambios descentralizados y emisores de activos utilizan Horizon para enviar transacciones, consultar el saldo de una cuenta o transmitir eventos como transacciones a una cuenta.
-
-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).
-
-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").
-
-## ¿Por qué correr Horizon?
-
-Correr Horizon dentro de tu propia infraestructura proporciona una serie de beneficios. Puedes:
-
-- Tener control operativo total sin depender de la Stellar Development Foundation para datos de red y envío de transacciones a las redes;
-- Correr múltiples instancias para redundancia y escalabilidad.
-
-La Stellar Development Foundation (SDF) ejecuta dos instancias de Horizon:
-
-- [horizon-testnet.stellar.org](https://horizon-testnet.stellar.org/) para interactuar con la [testnet](../../../networks/README.mdx)
-- [horizon-futurenet.stellar.org](https://horizon-futurenet.stellar.org/) para interactuar con la [futurenet](../../..//README.mdx)
-
-## En Estos Documentos
-
-- [Guía Administrativa](./admin-guide/README.mdx): cómo configurar tu propia instancia de Horizon.
-- [Estructura](./api-reference/structure/README.mdx): cómo está estructurado Horizon.
-- [Recursos](./api-reference/resources/README.mdx): descripciones de recursos y sus endpoints.
-- [Agregaciones](./api-reference/aggregations/README.mdx): descripciones de endpoints especializados.
-- [Errores](./api-reference/errors/README.mdx): errores potenciales y lo que significan.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/README.mdx
deleted file mode 100644
index 11d2baf146..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Guía de administración
-sidebar_position: 15
-sidebar_key: horizon-admin-guide
----
-
-import DocCardList from "@theme/DocCardList";
-
-Todo lo que necesitas saber sobre cómo configurar, ejecutar y usar Horizon.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/configuring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/configuring.mdx
deleted file mode 100644
index 59b94007c6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/configuring.mdx
+++ /dev/null
@@ -1,170 +0,0 @@
----
-title: Configurar
-sidebar_position: 30
----
-
-## Requisitos previos
-
-- Has identificado el método de [instalación](./installing.mdx) para el sistema host:
-  - Para bare-metal, tienes dos ejecutables instalados en la ruta del sistema operativo del host: `stellar-horizon` y `stellar-core`.
-  - Para ejecutar la imagen de Horizon con el demonio de Docker, usarás el [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon) alojado en Docker Hub. Ya has descargado la imagen stellar/stellar-horizon a través de `docker pull stellar/stellar-horizon:<tag_version>` en el host. Esta imagen contiene `stellar-horizon` y `stellar-core` en su interior.
-  - Para Kubernetes con el [Horizon Helm Chart](https://github.com/stellar/helm-charts/tree/main/charts/horizon), has seguido la [Instalación de Horizon con Helm Chart](./installing.mdx#helm-chart-installation).
-
-- [Inicializar base de datos](#initialize-horizon-database)
-
-Ahora estás listo para identificar los parámetros de configuración necesarios para desempeñar tres roles importantes:
-
-- **Atender solicitudes API de solo lectura** a través de una API HTTP basada en la web;
-- **Ingerir ledgers** de nodos Core de la red Stellar para mantener su visión del mundo actualizada;
-- **Enviar transacciones** a través de una API HTTP basada en la web, reenviando la solicitud de envío de transacción a la red Stellar.
-
-Para realizar estos roles, puedes elegir entre uno de los dos modos de despliegue a continuación (despliegue de instancia única o despliegue de múltiples instancias). Cada uno tiene sus propios parámetros de configuración.
-
-## Despliegue de Instancia Única
-
-Ejecuta `stellar-horizon` en un solo proceso de o/s y realizará los tres roles simultáneamente.
-
-| variable de entorno       | ejemplo                             |
-| ------------------------- | ----------------------------------- |
-| `DATABASE_URL`            | postgres://localhost/horizon_pubnet |
-| `NETWORK`                 | pubnet                              |
-| `HISTORY_RETENTION_COUNT` | 518400                              |
-
-## Despliegue de Múltiples Instancias
-
-En esta variante de despliegue escalable, ejecutas múltiples instancias de `stellar-horizon`, cada una realizando un subconjunto de los roles. Esto te permite escalar horizontalmente cada una de las funciones de rol de forma independiente.
-
-### Instancia de Rol de Ingestión
-
-Debes asignar **al menos** una instancia para realizar la ingesta continua y capturar la actividad de la red. Esto por defecto limitará el almacenamiento de la actividad de red ingerida en la base de datos a nuestra recomendación de una ventana deslizante de los últimos 30 días.
-
-| variable de entorno       | ejemplo                             |
-| ------------------------- | ----------------------------------- |
-| `DATABASE_URL`            | postgres://localhost/horizon_pubnet |
-| `NETWORK`                 | pubnet                              |
-| `HISTORY_RETENTION_COUNT` | 518400                              |
-| `DISABLE_TX_SUB`          | true                                |
-
-### Instancia de Rol de API
-
-Puedes ejecutar ninguna o múltiples instancias para atender solicitudes API de solo lectura. Ten en cuenta que no hay necesidad de definir configuraciones de red aquí, ya que Horizon solo lee de la base de datos.
-
-| variable de entorno  | ejemplo                             |
-| -------------------- | ----------------------------------- |
-| `DATABASE_URL`       | postgres://localhost/horizon_pubnet |
-| `INGEST`             | false                               |
-| `DISABLE_TX_SUB`     | true                                |
-
-### Instancia de Rol de Envío de Transacciones
-
-Puedes ejecutar ninguna o múltiples instancias para atender solicitudes de envío de transacciones. Si ejecutas una instancia con envío de transacciones habilitado, el despliegue de Horizon requiere tener al menos una instancia que realice el rol de ingestión en la misma base de datos. La presentación de transacciones de Horizon depende de que este **en vivo** proceso de ingestión se lleve a cabo contra la base de datos para confirmar el estado de envío de tx.
-
-Si la ingestión está planificada para hacerse en una instancia separada, agrega `INGEST=false` en esta instancia, de lo contrario no incluyas el parámetro, Horizon predeterminará a `INGEST=true`. Cuando una instancia de envío de transacciones habilitada tiene `INGEST=true` efectivo, configurará automáticamente el parámetro relacionado `STELLAR_CORE_URL` para utilizar la instancia cautiva de core lanzada internamente y el despliegue no necesita establecer el valor de configuración explícitamente.
-
-Si estableces `INGEST=false`, entonces **debes** definir la variable `STELLAR_CORE_URL` en esta instancia habilitada para envío de transacciones, ya que no habrá ninguna instancia de core cautiva alojada internamente como parte de la ingestión disponible para referencia, en cambio, el `STELLAR_CORE_URL` proporciona la capacidad de definir la URL de un puerto HTTP de instancia de core a la que Horizon enviará los envíos de transacciones.
-
-| variable de entorno  | ejemplo                             |
-| -------------------- | ----------------------------------- |
-| `DATABASE_URL`       | postgres://localhost/horizon_pubnet |
-| `STELLAR_CORE_URL`   | http://example.watcher.core:11626   |
-| `INGEST`             | false                               |
-
-## Notas
-
-### Ingestión
-
-Si has configurado tu despliegue para realizar el rol de ingestión, entonces se recomienda **encarecidamente** revisar primero [Ingestión](./ingestion.mdx) y segundo [Filtrado](./ingestion-filtering.mdx) y tener eso en cuenta en los parámetros de configuración para lograr el mejor rendimiento relacionado con los requisitos de tu aplicación antes de proceder más adelante.
-
-- Horizon creará un subdirectorio bajo el directorio de trabajo actual del proceso de o/s para almacenar los archivos de datos de tiempo de ejecución de core cautivo. Consulta [Requisitos previos](./prerequisites.mdx) para el tipo y cantidad de almacenamiento recomendado. Puedes sobrescribir esta ubicación con la variable de entorno opcional `CAPTIVE_CORE_STORAGE_PATH`, establecida en un directorio en el sistema de archivos donde core cautivo almacenará los archivos de tiempo de ejecución.
-
-### `DISABLE_TX_SUB`
-
-Este parámetro de configuración es opcional, establecido como FALSO por defecto. Controla si Horizon aceptará solicitudes HTTP al endpoint de API `/tx` y las reenviará a la red. Consulta [Cuentas de Canal](../../../../build/guides/transactions/channel-accounts.mdx) para algunas recomendaciones sobre optimizaciones opcionales para la presentación de transacciones del cliente.
-
-- Cuando se establece en FALSO, requiere que el proceso de ingestión **en vivo** esté funcionando en la misma base de datos porque Horizon depende de nuevos ledgers de la red para confirmar un estado de envío de transacción, Horizon informará un error de inicio si detecta que no hay ingestión **en vivo**. Requiere que `INGEST=true` o que `STELLAR_CORE_URL` se definan para acceder a una instancia de Core.
-- Cuando el envío de transacciones está deshabilitado al establecerlo en VERDADERO, Horizon devolverá 405 en POSTs a /tx.
-
-### `NETWORK`
-
-Este parámetro de configuración es opcional, puede ser una de las redes públicas de Stellar, 'pubnet', o 'testnet'. Activa a Horizon para configurar automáticamente las configuraciones para los restantes ajustes de Horizon y generar los correctos ajustes de core toml/cfg. Si solo necesitas que Horizon se conecte a una de esas redes públicas de Stellar, esto se encargará de todas las configuraciones relacionadas.
-
-- Si deseas conectar Horizon a una red Stellar diferente a pubnet o testnet o sobrescribir cualquiera de los predeterminados que el uso de `NETWORK` iniciará, las variables de entorno clave que se pueden establecer son: `HISTORY_ARCHIVE_URLS`, `CAPTIVE_CORE_CONFIG_PATH`, `NETWORK_PASSPHRASE`, `CAPTIVE_CORE_STORAGE_PATH`, `STELLAR_CORE_URL`.
-
-### `DB_URL`
-
-Este parámetro de configuración es requerido, especifica la base de datos de Horizon. Su valor sigue este formato: `dbname=<pg_dbname> user=<pg_user_name> password=<pg_user_pwd> host=<host_address>`
-
-### `LOG_LEVEL`
-
-Este parámetro de configuración es opcional, puede ser uno de 'info', 'error', 'debug'.
-
-### `HISTORY_RETENTION_COUNT`
-
-Este parámetro de configuración es opcional, determina la ventana deslizante máxima de datos históricos de red a retener en la base de datos desde la ingestión. El valor se expresa como un conteo absoluto de ledgers, que es una manera indirecta de definir una duración de tiempo, cada ledger siendo aproximadamente 5 segundos. Se predetermina a 0, lo que significa que no se purgará ninguna historia de la base de datos. Para aplicar la ventana deslizante recomendada de un mes, establece esto en 518400, que es el número aproximado de ledgers en 30 días. Consulta [Recursos Computacionales](./prerequisites.mdx) sobre cómo el espacio de almacenamiento de la base de datos está estrechamente relacionado con este ajuste.
-
-## Pasando Configuraciones a Horizon
-
-El binario `stellar-horizon` busca variables de entorno del proceso para la configuración. Dependiendo de cómo se instaló Horizon, el método que realices para configurar el entorno de proceso variará:
-
-### Bare-metal
-
-- Sin gestor de paquetes: usa variables de entorno de o/s para pasar configuraciones. Hay muchas herramientas que puedes usar para gestionarlas, como [direnv](http://direnv.net/) o [dotenv](https://github.com/bkeepers/dotenv).
-- [Gestor de paquetes](./installing.mdx#package-manager): el wrapper proporcionado `stellar-horizon-cmd` iniciará un nuevo proceso y creará variables de entorno en el proceso desde `/etc/default/stellar-horizon` y luego lanzará el 'stellar-horizon'. Para establecer configuraciones, edita el archivo en `/etc/default/stellar-horizon`.
-
-  :::info
-
-  Este script invoca Horizon con el usuario `stellar`, así que asegúrate de que los permisos para el usuario estén configurados en consecuencia. El directorio de trabajo actual debe ser escribible para este usuario y el usuario debe poder ejecutar los binarios `stellar-horizon` y `stellar-core`; etc.
-
-  :::
-
-### En contenedores
-
-- No Helm: pasa todos los parámetros de configuración a la imagen docker de horizon como [variables de entorno de docker](https://docs.docker.com/engine/reference/commandline/run/#env).
-- Helm: pasa todos los parámetros de configuración en el [comando de instalación de Helm](https://helm.sh/docs/helm/helm_install/) mediante un archivo de valores.
-
-## Inicializar la base de datos de Horizon
-
-Antes de ejecutar el servidor de Horizon por primera vez, debes inicializar la base de datos de Horizon. Esta base de datos se usará para toda la información que genera Horizon, especialmente la información histórica sobre las transacciones que han ocurrido en la red Stellar.
-
-Para preparar una base de datos para el uso de Horizon, primero asegúrate de que esté vacía. Lo más sencillo es crear una base de datos nueva en tu servidor PostgreSQL específicamente para el uso de Horizon. Recomendamos crear un nuevo usuario(rol) en postgres dedicado a la base de datos de Horizon y asignar ese usuario(rol) como propietario de esta base de datos.
-
-Para ilustrar un ejemplo usando `psql`, primero inicia sesión en el servidor de bases de datos con la herramienta de línea de comandos `psql` como superusuario, y luego crea el nuevo usuario(rol) y la base de datos para Horizon:
-
-```
-postgres=#
-postgres=# CREATE ROLE horizon WITH LOGIN;
-CREATE ROLE
-postgres=#
-postgres=# CREATE DATABASE horizon OWNER horizon;
-CREATE DATABASE
-postgres=#
-```
-
-Además, puedes establecer una contraseña para tu nuevo usuario postgres `horizon` con `ALTER USER`.
-
-Una vez completado, puedes componer el valor completo del parámetro de configuración para el acceso a db `DATABASE_URL="dbname=horizon user=horizon password=<value_here> host=<address_of_pg_server>"`.
-
-A continuación, ejecuta el binario de Horizon para instalar el esquema en la base de datos vacía desde la línea de comandos. En este ejemplo, supongamos que la shell actual no tiene `DATABASE_URL` en el entorno aún, así que primero asígnalo a la shell:
-
-```
-$ export DATABASE_URL="dbname=horizon user=horizon password=<value_here> host=<address_of_pg_server>"
-$ stellar-horizon db init
-```
-
-### Configuraciones opcionales de Postgres
-
-Basándonos en observaciones de rendimiento a lo largo del tiempo, recomendamos configuraciones adicionales para Postgres (postgresql.conf), aunque no son obligatorias:
-
-- Establece `random_page_cost=1` si usas almacenamiento SSD. Con esta configuración, el Planificador de Consultas hará un mejor uso de los índices, especialmente para consultas `JOIN`. Hemos notado una gran mejora en la velocidad de algunas consultas con esta configuración.
-
-\_ Para mejorar la disponibilidad de los servidores de ingestión, api y envío de transacciones se recomienda establecer los siguientes valores:
-
-- `tcp_keepalives_idle`: 10 segundos
-- `tcp_keepalives_interval`: 1 segundo
-- `tcp_keepalives_count`: 5
-
-Con la configuración anterior, si no hay consultas de un cliente dado durante 10 segundos, Postgres debe comenzar a enviar paquetes TCP keepalive. Intentará 5 veces cada segundo. Si no hay respuesta del cliente después de ese tiempo, se cerrará la conexión.
-
-## Siguiente paso
-
-Después de completar la configuración, ahora estás listo para proceder a [Ejecutar Horizon](./running.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/ingestion-filtering.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/ingestion-filtering.mdx
deleted file mode 100644
index 176d33d648..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/ingestion-filtering.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Filtrado de Ingesta
-order: 46
----
-
-## Resumen
-
-El Filtrado de Ingesta permite a los operadores de Horizon reducir drásticamente la huella de almacenamiento de los datos históricos en la base de datos de Horizon mediante la inclusión en una lista blanca de Activos y/o Cuentas que son relevantes para sus operaciones.
-
-### ¿Por qué es útil:
-
-Anteriormente, la única forma de limitar el almacenamiento de datos era restringiendo el rango temporal de la historia mediante retención temporal (por ejemplo, los últimos 30 días). La función de filtrado permite a los usuarios almacenar un período histórico más largo en la base de datos de Horizon solo para activos, cuentas y sus entidades históricas relacionadas (transacciones, operaciones, intercambios, etc.) que estén en la lista blanca.
-
-Para más contexto, ejecutar una instancia de Horizon con historial `completo` no filtrado actualmente requiere más de 30TB de espacio en disco (hasta junio de 2023) con un crecimiento de almacenamiento de aproximadamente 1TB/mes. Como referencia, filtrar incluso por 100 de las cuentas y activos más activos reduce el almacenamiento en más del 90%. Para la mayoría de las aplicaciones que están interesadas en un conjunto aún más limitado de activos y cuentas, los ahorros de almacenamiento deberían ser superiores al 99%. Otros beneficios incluyen la reducción de los costos operativos asociados al mantenimiento del almacenamiento, mejores métricas de salud de la base de datos y un rendimiento de consultas mejorado.
-
-### ¿Cómo funciona:
-
-La función de filtrado opera durante la ingestión en procesos **en vivo** y de **rango histórico**. Indica al proceso de ingesta que solo acepte transacciones de ledger entrantes que coincidan con una regla de filtrado; cualquier transacción que no cumpla con las reglas de filtrado es omitida por la ingesta y, por lo tanto, no se almacena en la base de datos.
-
-Algunos aspectos clave a tener en cuenta sobre el comportamiento de filtrado:
-
-- Si tanto los filtros de activos como de cuentas están habilitados y cada filtro está provisto de al menos una regla, las transacciones se almacenan en la base de datos cuando alguna regla de cualquiera de los filtros coincide con la transacción dada.
-- El filtrado se aplica únicamente a la ingesta de datos históricos en la base de datos; no afecta cómo el proceso de ingesta mantiene los datos del estado actual almacenados en la base de datos, que es la última entrada de ledger conocida para cada entidad única dentro de cuentas, líneas de confianza, fondos de liquidez y ofertas. Sin embargo, los datos del estado actual consumen una cantidad relativamente pequeña de la capacidad total de almacenamiento.
-- Cuando se cambian las reglas de filtrado, solo se aplican a los procesos de ingesta existentes y en ejecución (**en vivo** y de **rango histórico**). No desencadenan ningún filtrado retroactivo ni llenado retrospectivo de datos históricos existentes en la base de datos.
-  - Cuando se actualizan las reglas de filtrado para incluir cuentas o activos adicionales en la lista blanca, las transacciones relacionadas de la ingesta **en vivo** solo aparecerán en los datos históricos de la base de datos una vez que las reglas de filtrado se hayan actualizado utilizando la API administrativa. Lo mismo se aplica a la ingesta de **rango histórico**, donde las nuevas reglas de filtrado solo afectarán los datos del ledger actual dentro de su rango configurado en el momento de la actualización.
-  - Actualizar las reglas de filtrado para incluir cuentas o activos adicionales no activa ningún llenado automático relacionado con nuevas entidades en la base de datos histórica. Para incluir la historia previa de entidades recién enlistadas en la base de datos, puedes ejecutar manualmente un nuevo [Rango de Ingesta Histórica](./ingestion.mdx#ingesting-historical-data) después de actualizar las reglas de filtrado.
-  - Cuando se actualizan las reglas de filtrado para eliminar cuentas o activos previamente definidos en la lista blanca, los datos históricos en la base de datos no se purgan ni filtran de manera retroactiva en base a las reglas actualizadas. Los datos se almacenan en las tablas de historial durante la duración de la base de datos o hasta que se exceda el `HISTORY_RETENTION_COUNT`. Una vez que se alcanza el límite de retención, Horizon eliminará todos los datos históricos relacionados con los ledgers más antiguos, independientemente de las reglas de filtrado.
-- El filtrado no afectará el rendimiento o la tasa de rendimiento de un proceso de ingesta, seguirá siendo consistente ya sea que las reglas de filtrado estén presentes o no.
-
-Las reglas de filtrado definen listas blancas de las siguientes entidades admitidas:
-
-- ID de cuenta
-- ID de activo (canónico)
-
-Dado que se incluyen todas las transacciones relacionadas con las entidades en la lista blanca, todos los datos históricos de series temporales relacionados con esas transacciones se guardan en la base de datos histórica de Horizon, incluyendo la transacción misma, todas las operaciones en la transacción y las referencias a cualquier entidad auxiliar de las operaciones.
-
-## Configuración:
-
-El filtrado está habilitado por defecto sin ninguna regla de filtrado definida. Cuando no se definen reglas de filtrado, eso significa que no ocurre ningún filtrado de los datos ingeridos. Para comenzar a filtrar la ingesta, necesitas definir al menos una regla de filtrado:
-
-- habilitar el puerto de administración de Horizon con el parámetro de configuración ambiental `ADMIN_PORT=XXXXX`, esto te permitirá acceder al puerto.
-- definir listas blancas de filtrado. enviar solicitudes a la API HTTP de Admin para ver y actualizar las reglas de filtrado:
-
-  Consulta la [Documentación del API de administración de Horizon](https://github.com/stellar/stellar-horizon/blob/main/internal/httpx/static/admin_oapi.yml) que también está publicada en las instancias de Horizon en ejecución como documento Open API 3.0 en el Puerto de Administración cuando está habilitado en `http://localhost:<admin_port>/`. Puedes pegar el contenido de esa URL en cualquier herramienta OAPI como [Swagger](https://editor.swagger.io/) que generará un explorador visual de los puntos finales de la API. En el editor de Swagger también puedes cargar directamente la publicación de Horizon admin.oapi.yml como una URL, elige `Archivo->Importar URL`:
-
-  ```
-   https://raw.githubusercontent.com/stellar/stellar-horizon/main/internal/httpx/static/admin_oapi.yml
-  ```
-
-  Sigue los detalles y ejemplos de las cargas útiles de solicitud/respuesta para leer y actualizar las reglas de filtrado para estos puntos finales:
-
-  ```
-  /ingestion/filters/account
-  /ingestion/filters/asset
-  ```
-
-  Elegir el botón `Probar` de cualquiera de los puntos finales mostrará ejemplos completos de solicitudes HTTP en formato `curl`.
-
-## Caso de Uso de Ejemplo:
-
-Como emisor de activos, he emitido 4 activos y estoy interesado en todos los datos de transacciones relacionadas con esos activos, incluyendo cuentas de clientes que interactúan con esos activos a través de las siguientes operaciones:
-
-- Operaciones
-- Efectos
-- Pagos
-- Saldos reclamables
-- Intercambios
-
-Me gustaría almacenar el historial completo de todas las transacciones relacionadas desde el génesis de esos activos.
-
-### Requisitos previos:
-
-Has instalado Horizon con una base de datos vacía y tiene la ingestión **en vivo** habilitada.
-
-### Pasos:
-
-1. Configura una regla de filtrado con 4 activos en la lista blanca haciendo una solicitud POST a la API ADMIN de Horizon `<horizon_host>:<ADMIN_PORT>/ingestion/filters/asset`.
-
-```
-curl -X 'PUT' \
-  'http://localhost:4200/ingestion/filters/asset' \
-  -H 'accept: application/json' \
-  -H 'Content-Type: application/json' \
-  -d '{
-  "whitelist": [
-    "USDC:GAFRNZHK4DGH6CSF4HB5EBKK6KARUOVWEI2Y2OIC5NSQ4UBSN4DR456U",
-    "DOTT:GAFRNZHK4DGH6CSF4HB5EBKK6KARUOVWEI2Y2OIC5NSQ4UBSN4DR456U",
-    "ABCD:GAFRNZHK4DGH6CSF4HB5EBKK6KARUOVWEI2Y2OIC5NSQ4UBSN4DR456U",
-    "EFGH:GAFRNZHK4DGH6CSF4HB5EBKK6KARUOVWEI2Y2OIC5NSQ4UBSN4DR456U"
-  ],
-  "enabled": true
-}'
-```
-
-2. Dado que esta es una nueva base de datos de Horizon, y las primeras reglas de filtrado, no hay nada más que hacer y efectivamente construyes aquí.
-
-3. Sin embargo, para fines de ejercicio, supongamos que ya tuviste a Horizon funcionando durante un tiempo y la base de datos se pobló con base en algunas reglas de filtrado, y estas nuevas reglas eran listados adicionales que acabas de añadir. En este caso, decides si deseas rellenar retroactivamente los datos históricos en la base de datos de Horizon para estas nuevas entidades en la lista blanca desde un tiempo anterior hasta el presente, ya que originalmente se omitieron en la ingestión anterior y no se incluyeron en la base de datos. Si decides que deseas rellenar, entonces ejecutas un proceso separado de ingestión de **rango histórico**, consulta [Rango de Ingesta Histórica](./ingestion.mdx#ingesting-historical-data) para los pasos:
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/ingestion.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/ingestion.mdx
deleted file mode 100644
index 6d6b8ea0f1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/ingestion.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: Ingestión
-sidebar_position: 45
----
-
-La API de Horizon proporciona la mayor parte de su utilidad a través de datos ingeridos, y tu servidor Horizon puede configurarse para escuchar e ingresar los resultados de transacciones de la red Stellar. La ingestion permite el acceso a la API tanto al estado actual (por ejemplo, el saldo de alguien) como al estado histórico (por ejemplo, el historial de transacciones de alguien).
-
-## Tipos de Ingestión
-
-Hay dos casos de uso principales de ingesta para operaciones de Horizon:
-
-- Ingresar datos **en vivo** para mantenerse actualizado con los últimos ledgers de la red, acumulando una ventana de deslizamiento de ledgers antiguos;
-- Ingresar datos **históricos** para agregar retroactivamente datos de la red de un rango de tiempo en el pasado a la base de datos.
-
-## Determinar el Espacio de Almacenamiento
-
-Debes pensar cuidadosamente sobre el marco temporal histórico de los datos ingeridos que deseas conservar en la base de datos de Horizon. Los requisitos de almacenamiento para transacciones en la red Stellar son sustanciales y están creciendo sin límites con el tiempo. Esto es algo que puedes necesitar monitorear y reevaluar continuamente a medida que la red sigue creciendo. Hemos encontrado que la mayoría de las organizaciones solo necesitan una pequeña fracción de datos históricos recientes para satisfacer sus casos de uso. A través del análisis de los patrones de tráfico en la instancia de Horizon de SDF, vemos que la mayoría de las solicitudes son para datos muy recientes.
-
-Para mantener tu huella de almacenamiento pequeña, recomendamos lo siguiente:
-
-- Usa la ingesta **en vivo**, utiliza la ingesta **histórica** solo en casos excepcionales limitados.
-- Si tu aplicación requiere acceso a todos los datos de la red, no se puede realizar filtrado, recomendamos limitar la retención histórica de los datos ingeridos a una ventana deslizante de 1 mes (HISTORY_RETENTION_COUNT=518400) que es el valor por defecto establecido por Horizon.
-- Si tu aplicación puede trabajar con un [conjunto de datos de red filtrado](./ingestion-filtering.mdx) basado en cuentas y activos específicos, entonces recomendamos aplicar reglas de filtrado de ingesta. Al usar reglas de filtrado, se obtiene el beneficio de la opción de una mayor retención histórica durante un periodo de tiempo ya que el filtrado reduce el tamaño general de la base de datos, de tal manera que la retención histórica (HISTORY_RETENTION_COUNT) puede establecerse en términos de años en lugar de meses o incluso desactivarse (HISTORY_RETENTION_COUNT=0).
-- Si no puedes limitar tu ventana de retención de historia a 30 días y no puedes usar reglas de filtrado, te recomendamos considerar el [Almacén de Datos de Stellar Hubble](../../../analytics/hubble/README.mdx) para cualquier dato histórico.
-
-### Ingresar Datos en Vivo
-
-Esta opción está habilitada por defecto y es el modo de ingesta recomendado para ejecutar. Se controla con la configuración de entorno con la bandera `INGEST`. Consulta [Configuración](./configuring.mdx) para ver cómo una instancia de Horizon realiza el papel de ingesta.
-
-Para requisitos de alta disponibilidad, **recomendamos desplegar más de una instancia de ingesta en vivo**, ya que esto facilita evitar el tiempo de inactividad durante las actualizaciones y agrega resistencia, asegurando que siempre tengas los últimos datos de la red (consulta [Instancia de Papel de Ingesta](./configuring.mdx#multiple-instance-deployment)).
-
-### Ingresar Datos Históricos
-
-Importar datos de la red de un rango de fechas pasadas a la base de datos:
-
-<CodeExample>
-
-```
-stellar-horizon db reingest range <start> <end>
-```
-
-</CodeExample>
-
-Ejecutar cualquier rango de ingesta histórica requiere coordinación con la configuración de retención de datos elegida. Al establecer un límite temporal en la historia con `HISTORY_RETENTION_COUNT=<LEDGER_COUNT>`, el límite temporal tiene prioridad, y cualquier dato ingresado más allá de ese límite será purgado automáticamente.
-
-Normalmente, la única vez que necesitas ejecutar la ingesta histórica es una vez al inicializar un sistema después del primer despliegue, a partir de ese punto, la ingesta **en vivo** mantendrá la base de datos completada con la ventana de deslizamiento esperada de datos históricos rezagados. Quizás una excepción es si piensas que tienes un vacío en la base de datos causado por la ingesta **en vivo** que está caída, en cuyo caso puedes ejecutar un rango de ingesta histórica para llenar esencialmente el vacío.
-
-Puedes ejecutar la ingesta histórica en paralelo en segundo plano mientras tu servidor principal de Horizon realiza la ingesta **en vivo** por separado. Si el rango especificado se superpone con los datos ya en la base de datos, está bien y simplemente será sobrescrito, de manera efectiva idempotente.
-
-#### Trabajadores de Ingestión Paralelos
-
-Puedes paralelizar la ingesta del rango de ledger histórico objetivo dividiéndolo en porciones secuenciales de rangos más pequeños y ejecutar el comando de rango de reingesto de db para cada sub-rango en paralelo como un proceso separado en la misma máquina o en una diferente. La regla abreviada para el mejor rendimiento es identificar la cantidad de núcleos de CPU disponibles por máquina objetivo, si es multi-core, entonces agrega `--parallel-workers <num de núcleos>` al comando, esto habilitará el comando para paralelizar aún más internamente dentro de un solo proceso utilizando múltiples hilos y rangos más pequeños subdivididos.
-
-<CodeExample>
-
-```
-# target range 1 30000, on single machine with 1 CPU core
-horizon1> stellar-horizon db reingest range 1 30000
-
-# target range 1 30000, on single machine with 4 CPU cores
-horizon1> stellar-horizon db reingest range 1 30000 --parallel-workers 4
-
-# target range 1 30000, on two machines, each has 2 CPU cores
-horizon1> stellar-horizon db reingest range 1 15000 --parallel-workers 2
-horizon2> stellar-horizon db reingest range 15001 30000 --parallel-workers 2
-```
-
-</CodeExample>
-
-### Notas
-
-#### Algunos endpoints pueden informar no disponibles durante la ingesta **en vivo**
-
-- Los endpoints que muestran información de estado actual de la ingesta **en vivo** pueden devolver el error `503 Servicio No Disponible`/`Aún Ingresando`. Un ejemplo es el endpoint `/paths` (desarrollado con ofertas). Tales endpoints estarán disponibles después de que la ingesta **en vivo** haya terminado la sincronización de la red y alcanzado (generalmente dentro de un par de minutos).
-
-#### Si han pasado más de cinco minutos sin nuevos datos ingeridos:
-
-- Verifica que la máquina host cumpla con los [Requisitos previos](./prerequisites.mdx) recomendados.
-
-- Revisa la salida del log de Horizon.
-  - Si hay muchos mensajes de `nivel=error`, puede indicar un problema ambiental, incapacidad para acceder a la base de datos.
-  - La ingesta **en vivo** emitirá dos líneas de log clave aproximadamente cada 5 segundos basadas en el último ledger emitido por la red. Sigue la salida del log de Horizon y busca la presencia de estas líneas con un filtro:
-    ```
-    tail -f horizon.log | | grep -E 'Processed ledger|Closed ledger'
-    ```
-    Si no ves salida de este pipeline cada pocos segundos para un nuevo ledger, entonces la ingesta no está avanzando, revisa los registros completos y verifica si hay mensajes alternativos que indiquen lo contrario. Puede que veas líneas que mencionen 'sincronizándose' al conectarte a pubnet, ya que puede tardar hasta 5 minutos para que el proceso de núcleo cautivo iniciado por Horizon se sincronice con la red pubnet.
-  - Verifica el uso de RAM en la máquina, es posible que el sistema se haya quedado sin RAM y esté utilizando memoria swap, lo que resultará en un rendimiento lento. Verifica que la máquina host cumpla con los requisitos mínimos de RAM [requisitos previos](./prerequisites.mdx).
-  - Verifica las velocidades de rendimiento de lectura/escritura en el volumen que el directorio de trabajo actual para el proceso de horizon está utilizando. Según los [requisitos previos](./prerequisites.mdx), el volumen debe tener al menos 10mb/s, una forma de verificar esto bridamente en la máquina host (línea de comando linux/mac):
-    ```
-    sudo dd if=/dev/zero of=/tmp/test_speed.img bs=1G count=1
-    ```
-
-#### Monitoreando el Proceso de Ingestión
-
-Para despliegues de alta disponibilidad, se recomienda implementar monitoreo del proceso de ingesta para visibilidad sobre el rendimiento/salud. Consulta [Monitoreo](./monitoring.mdx) para acceder a los logs y métricas de Horizon. Stellar publica el ejemplo del [Tablero de Grafana de Horizon](https://grafana.com/grafana/dashboards/13793-stellar-horizon/), que demuestra consultas contra métricas clave de ingesta de Horizon, específicamente mira la `Demora de Ingesta Local [Ledgers]` y la `Edad del Último ledger` en el panel `Resumen de Salud`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/installing.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/installing.mdx
deleted file mode 100644
index 4378faf8fb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/installing.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Instalando
-sidebar_position: 20
----
-
-Para instalar Horizon en entornos de producción o no de desarrollo, recomendamos lo siguiente según la infraestructura de destino:
-
-### Bare-Metal
-
-- Si el host es Debian Linux, instala los binarios precompilados [desde los repositorios](#package-manager) utilizando un gestor de paquetes.
-- Para cualquier otro host, descarga los [binarios precompilados de la versión](#prebuilt-releases) de Stellar Horizon y Core para la arquitectura del host y sistema operativo objetivo o [compílalos desde el código fuente](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md).
-
-### Containerizado
-
-- No Orquestado: si el entorno de despliegue objetivo no incluye un orquestador de contenedores como Kubernetes, esto significa que tienes la intención de ejecutar la imagen de versión de Horizon desde [dockerhub.com/stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon) como un contenedor directamente con el daemon de Docker en el host. Elige la etiqueta de la imagen de Horizon para la versión específica y luego extrae la imagen usando `docker pull stellar/stellar-horizon:<tag_version>` para obtenerla localmente en el host.
-- Orquestado: cuando el entorno objetivo tiene orquestación de contenedores, como un clúster de Kubernetes, recomendamos usar el [Chart de Helm de Horizon](https://github.com/stellar/helm-charts/tree/main/charts/horizon) para gestionar el ciclo de vida de instalación y despliegue de la imagen de Horizon como contenedor(es) en el clúster.
-
-Para instalar Horizon en entornos de desarrollo, consulta el [README de Horizon](https://github.com/stellar/stellar-horizon) en el repositorio del código fuente para conocer las opciones disponibles.
-
-### Notas sobre la Instalación
-
-#### Gestor de Paquetes
-
-SDF publica nuevas versiones en sus repositorios personalizados de Ubuntu. Sigue [esta guía](https://github.com/stellar/packages/blob/master/docs/adding-the-sdf-stable-repository-to-your-system.md#adding-the-sdf-stable-repository-to-your-system) para agregar el repositorio estable de SDF a tu sistema host. Si estás interesado en instalar versiones candidatas de versiones de software que aún no han alcanzado la estabilidad, consulta [Añadiendo el Repositorio de Pruebas de la Última Versión](https://github.com/stellar/packages/blob/master/docs/adding-the-sdf-stable-repository-to-your-system.md#adding-the-bleeding-edge-testing-repository). Por último, [instala el paquete](https://github.com/stellar/packages/blob/master/docs/installing-individual-packages.md#installing-individual-packages) que describe los diversos comandos que estos paquetes ponen a disposición.
-
-Para proceder con la instalación:
-
-<CodeExample>
-
-```bash
-sudo apt update
-sudo apt install stellar-horizon stellar-core
-```
-
-</CodeExample>
-
-#### Versiones Precompiladas
-
-Consulta la lista de [versiones de Horizon](https://github.com/stellar/stellar-horizon/releases) y [versiones de Core](https://github.com/stellar/stellar-core/releases). Copia los binarios al PATH del host.
-
-#### Verificar Instalaciones Bare-Metal
-
-Ejecuta `stellar-horizon --help` desde una terminal. Si se muestra la ayuda de Horizon, tu instalación fue exitosa.
-
-Algunos shells (como [zsh](https://www.zsh.org/)) almacenan en caché las búsquedas de PATH. Puede que necesites limpiar tu caché (utilizando `rehash` en zsh, por ejemplo) o reiniciar tu shell antes de intentar ejecutar el comando anterior.
-
-#### Instalación del Chart de Helm
-
-Si el despliegue se puede realizar en Kubernetes, hay un [Chart de Helm de Horizon](https://github.com/stellar/helm-charts/blob/main/charts/horizon) disponible. Instala la [herramienta CLI de Helm](https://helm.sh/docs/intro/install/), si aún no lo has hecho en tu estación de trabajo, mínimo de versión 3. A continuación, agrega el repositorio de Stellar a la lista de repositorios del cliente de Helm y confirma que puedes ver la lista de versiones de chart disponibles para el repositorio:
-
-<CodeExample>
-
-```bash
-helm repo add stellar https://helm.stellar.org/charts
-helm repo update stellar
-helm search repo stellar/horizon --versions --devel
-```
-
-</CodeExample>
-
-Espera para instalar el Chart de Helm de Horizon, se realizará una vez que se complete [Configurando](./configuring.mdx) y en [Ejecutándolo](./running.mdx).
-
-Si Kubernetes no es una opción, los charts de Helm aún pueden ser una buena referencia para mostrar cómo configurar y ejecutar el contenedor Docker de Horizon. Solo ejecuta el comando de helm con `template` para mostrar los manifiestos generados de Kubernetes, que demuestran todas las configuraciones de contenedores necesarias:
-
-<CodeExample>
-
-```bash
-git clone https://github.com/stellar/helm-charts; cd helm-charts
-helm template -f charts/horizon/values.yaml charts/horizon/
-```
-
-</CodeExample>
-
-## Próximo Paso
-
-¡Después de que la instalación esté completa, ahora estás listo para proceder a [Configurar Horizon](./configuring.mdx)!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/monitoring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/monitoring.mdx
deleted file mode 100644
index 85ba30cdec..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/monitoring.mdx
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: Monitoreo
-sidebar_position: 60
----
-
-## Métricas
-
-Las métricas se emiten desde Horizon a través de HTTP en [el formato de exposición de texto basado en de facto](https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exposition_formats.md#text-based-format). Las métricas se publican en la ruta _privada_ `/metrics` del puerto de administración de Horizon, que es un servicio opcional que debe ser iniciado y se vinculará por el proceso de Horizon en la red de bucle local de la máquina anfitriona (localhost o 127.0.0.1). Para habilitar el puerto de administración, añade el parámetro de configuración del entorno `ADMIN_PORT=XXXXX`, el endpoint de métricas será accesible en la máquina anfitriona como `localhost:<ADMIN_PORT>/metrics`. Puedes verificar esto apuntando cualquier navegador que pueda acceder a esta dirección, mostrará todas las claves de métricas.
-
-### Exportando
-
-Una vez que se habilite el puerto de administración, el endpoint de métricas de Horizon puede ser 'scrapeado' por infraestructura de monitoreo externa. Dado que la salida de las métricas está codificada en [un formato de texto estándar](https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exposition_formats.md#text-based-format), será compatible para su uso con muchos tipos de infraestructura de monitoreo que interoperan con el mismo formato estándar.
-
-En el caso de Horizon, las métricas se publican en el puerto HTTP de administración que está vinculado a la interfaz de red de bucle local de la máquina anfitriona (127.0.0.1), por lo que los sistemas o servicios de monitoreo externos no pueden acceder al puerto directamente. Para exponer las métricas de manera segura, recomendamos seguir el patrón del exportador, que es una estrategia común de 'scraping' de métricas.
-
-Un ejemplo del mundo real para exportar desde una instalación de Horizon en hardware (Horizon ha sido instalado directamente en un sistema operativo), usa [FluentBit y el exportador de Prometheus](https://docs.fluentbit.io/manual/pipeline/outputs/prometheus-exporter) en la misma máquina anfitriona donde se ejecuta Horizon. FluentBit realizará un simple reenvío de puertos en la máquina anfitriona. Configura la entrada para que sea `localhost:<ADMIN_PORT>/metrics` de Horizon y la salida para que represente la `máquina anfitriona` y el `puerto` que representan la interfaz de red y el puerto en la máquina anfitriona, y luego configura tu infraestructura de monitoreo para 'scrapear' esa dirección de la máquina anfitriona.
-
-En entornos orquestados por contenedores como Kubernetes, puedes usar la misma estrategia de exportador. Asumimos que ya tienes una implementación de infraestructura de métricas como Prometheus y Grafana configurada en el clúster a través del [Operador de Prometheus](https://github.com/prometheus-operator/prometheus-operator), y solo necesitarás configurar esa infraestructura para scrapear el pod de Horizon basado en el `ADMIN_PORT`.
-
-### Modelo de datos
-
-Hay numerosas claves de métricas de aplicación emitidas por Horizon en tiempo de ejecución, codificadas en cuatro tipos de formatos de exposición: `contador`, `gauge`, `histograma`, `resumen`. Cada clave se califica además con etiquetas para mayor granularidad. Para resumir, podemos resaltar los agrupamientos de claves de métricas por función común denotada en el prefijo de su nombre:
-
-- `go_`: rendimiento específico de golang en tiempo de ejecución
-- `horizon_txsub_`: atributos del subsistema de envío de transacciones de Horizon si está habilitado.
-- `horizon_stellar_core_`: atributos de tiempo de ejecución de la red Stellar reportados por el núcleo cautivo.
-- `horizon_order_book_`: atributos de tiempo de ejecución del libro de órdenes en memoria mantenido por Horizon de la red Stellar actual
-- `horizon_log_`: contadores de cuántos mensajes de registro se imprimieron en cada nivel de severidad
-- `horizon_ingest_`: mediciones de rendimiento y aspectos de estado del subsistema de ingestión interna de Horizon
-- `horizon_http_`: estadísticas y mediciones del servicio API HTTP de Horizon, todos los aspectos de la carga y tiempos de solicitudes/respuestas.
-- `horizon_history_`: estadísticas sobre los ledgers históricos ingeridos por Horizon
-- `horizon_db_`: mediciones sobre el rendimiento de la base de datos, tiempos de consulta por endpoints, estadísticas de agrupamiento
-- `process_`: mediciones de computación genérica en la máquina host
-
-Y para cada clave, habrá una posibilidad de 0 o más etiquetas, el formato de salida serializada (exposición) sigue esta plantilla:
-
-```
-<metrics_key_name>{label_1="value",label_2="value",,,} <value>
-```
-
-En lugar de enumerar todas las claves de métricas individuales en la documentación, ya que cambian con frecuencia, se recomienda realizar un HTTP GET contra el endpoint de métricas de Horizon, `localhost:<ADMIN_PORT>/metrics`, utilizando cualquier cliente HTTP (navegador, curl, wget, etc.) y la respuesta tendrá las claves de métricas y meta información adicional sobre cada clave de métrica para descripción y tipo (contador, gauge, histograma, resumen), como ejemplo para una clave, `horizon_http_requests_duration_seconds`:
-
-```
-# HELP horizon_http_requests_duration_seconds HTTP requests durations, sliding window = 10m
-# TYPE horizon_http_requests_duration_seconds summary
-horizon_http_requests_duration_seconds{method="GET",route="/",status="200",streaming="false",quantile="0.5"} 0.000186958
-horizon_http_requests_duration_seconds{method="GET",route="/",status="200",streaming="false",quantile="0.9"} 0.00043625
-horizon_http_requests_duration_seconds{method="GET",route="/",status="200",streaming="false",quantile="0.99"} 0.000645
-...
-
-```
-
-### Consultas
-
-Construir consultas contra el modelo de datos de métricas para resaltar el rendimiento de una implementación de Horizon dada. Consulta el [Tablero de Grafana Horizon de Stellar](https://grafana.com/grafana/dashboards/13793-stellar-horizon/) para ejemplos de consultas de métricas para derivar el rendimiento de la aplicación:
-
-- Número de solicitudes por minuto.
-- Número de solicitudes por ruta (las rutas más populares).
-- Tiempo de respuesta promedio por ruta.
-- Tiempo de respuesta máximo para solicitudes no streaming.
-- Número de solicitudes streaming vs. no streaming.
-- Número de solicitudes limitadas por tasa.
-- Lista de IPs limitadas por tasa.
-- IPs únicas.
-- Los SDKs/apps más populares que envían solicitudes a un nodo de Horizon dado.
-- Tiempo de ingestión promedio de un ledger.
-- Tiempo de ingestión promedio de una transacción.
-
-Elige la [pestaña de revisiones](https://grafana.com/grafana/dashboards/13793-stellar-horizon/?tab=revisions), y descarga el archivo fuente del tablero para tener acceso al código fuente del tablero de Grafana y a las consultas de métricas que construyen cada panel en los tableros.
-
-### Alertas
-
-Una vez que se desarrollan consultas en un tablero de Grafana, permite un paso conveniente para agregar [reglas de alerta](https://grafana.com/docs/grafana/latest/alerting/alerting-rules/create-grafana-managed-rule/) basadas en consultas específicas para activar notificaciones cuando se exceden los umbrales.
-
-Aquí hay algunos ejemplos de alertas a considerar con posibles causas y soluciones.
-
-| Alerta                                                  | Causa                                                                                                                | Solución                                                                                                               |
-| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
-| Pico en el número de solicitudes                        | Posible ataque DoS                                                                                                   | configuraciones de carga balanceada de red o conmutación de contenido                                                  |
-| La ingestión es lenta                                   | los recursos de computación del servidor anfitrión son bajos                                                         | aumentar las especificaciones de computación                                                                           |
-| Las respuestas de la API HTTP están devolviendo errores | los recursos de computación del servidor anfitrión son bajos o la conexión de red con la base de datos se ha perdido | revisa los [registros de Horizon](#logs) para ver qué errores se están emitiendo, reduce la causa raíz a partir de ahí |
-
-## Registros
-
-Horizon generará registros a la salida estándar del sistema operativo. Registrarás en todos los aspectos del tiempo de ejecución, incluyendo solicitudes HTTP y ingestión. Normalmente, hay muy pocos mensajes emitidos de severidad nivel `warn` o `error`. El nivel de severidad predeterminado registrado en Horizon está configurado como `LOG_LEVEL=info`, este parámetro de configuración de entorno puede ser establecido en uno de `trace, debug, info, warn, error`. La verbosidad de la salida de registros es inversa al nivel de severidad elegido. Es decir. para los registros más verbosos usa 'trace', para los registros menos verbosos usa 'error'.
-
-Para implementaciones en producción, recomendamos usar la configuración de severidad predeterminada del nivel `info` y elegir una estrategia de captura de registros dependiendo de la implementación.
-
-- Implementación en metal desnudo directa al sistema operativo, redirige la salida estándar del proceso de Horizon a un archivo en disco y aplica una herramienta de rotación de registros al archivo como [logrotate](https://man7.org/linux/man-pages/man8/logrotate.8.html) para gestionar el uso del espacio en disco.
-- Implementación orquestada en Kubernetes, usa un stack EFK/ELK en el clúster y se puede configurar para capturar la salida estándar del pod de Horizon.
-
-## Perfilado en tiempo de ejecución
-
-Horizon está escrito en Golang, por lo tanto, se ha habilitado opcionalmente para emitir los diagnósticos y la salida de perfilado de tiempo de ejecución de Golang [pprof](https://go.dev/doc/diagnostics). Los endpoints HTTP pprof están alojados en el puerto HTTP de administración de Horizon, se puede habilitar agregando el parámetro de configuración del entorno `ADMIN_PORT=XXXXX`, ya que el enlace del puerto de administración está deshabilitado por defecto.
-
-Se publican dos de los perfiles predefinidos estándar:
-
-`localhost:<ADMIN_PORT>/debug/pprof/heap` - perfilado de heap
-
-`localhost:<ADMIN_PORT>/debug/pprof/profile` - perfilado de CPU
-
-Usa la herramienta de línea de comandos pprof de Go para acceder a los endpoints publicados y visualizar los datos diagnósticos perfilados que se emiten. Un breve ejemplo de uso de la herramienta pprof desde la línea de comandos para comenzar, usando `web` para mostrar una representación gráfica de las asignaciones de heap actuales:
-
-```
-$ go tool pprof http://localhost:6060/debug/pprof/heap
-Fetching profile over HTTP from http://localhost:6060/debug/pprof/heap
-Saved profile in ./pprof/pprof.stellar-horizon.alloc_objects.alloc_space.inuse_objects.inuse_space.022.pb.gz
-File: stellar-horizon
-Type: inuse_space
-Entering interactive mode (type "help" for commands, "o" for options)
-(pprof) web
-```
-
-## ¡Estoy Atascado! ¡Ayuda!
-
-Si alguno de los pasos anteriores no funciona o no puedes configurar correctamente Horizon, por favor únete a nuestra comunidad y háznoslo saber. O publica una pregunta en [nuestro Stack Exchange](https://stellar.stackexchange.com/) o chatea con nosotros en [Horizon Discord](https://discord.com/channels/897514728459468821/912466080960766012) para pedir ayuda.
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
deleted file mode 100644
index ab5befc0a2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Resumen
-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).
-
-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").
-
-## ¿Por qué ejecutar Horizon?
-
-Ejecutar Horizon dentro de tu propia infraestructura proporciona una serie de beneficios. Puedes:
-
-- Tener control operativo total sin depender de la Stellar Development Foundation para datos de red y la presentación de transacciones a las redes;
-- Ejecutar múltiples instancias para redundancia y escalabilidad.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/prerequisites.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/prerequisites.mdx
deleted file mode 100644
index 47ad16b209..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/prerequisites.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Requisitos previos
-sidebar_position: 10
----
-
-El servicio Horizon es responsable de sincronizarse con la red Stellar y procesar los datos del ledger. Para entender el alcance de los servicios de Horizon, por favor lee la sección de [configuración](./configuring.mdx) antes de pasar a los requisitos previos para la computación.
-
-El servicio Horizon se puede [instalar](./installing.mdx) en hardware físico o en una máquina virtual. Está admitido de forma nativa en sistemas operativos Linux y Windows.
-
-## Modelo de Despliegue de Instancia Única
-
-Para una configuración básica utilizando el [modelo de Despliegue de Instancia Única](./configuring.mdx#single-instance-deployment), necesitarás la suma de dos perfiles de computación distintos:
-
-- Uno para alojar el servicio Horizon
-- Otro para alojar el servidor PostgreSQL
-
-### Requisitos de hardware
-
-Las especificaciones mínimas de hardware para ejecutar Horizon de manera efectiva son las siguientes:
-
-#### Instancia de Computación de Horizon:
-
-| Tipo de Nodo            | CPU    | RAM   | Disco                 | AWS SKU      | Google Cloud SKU |
-| ----------------------- | ------ | ----- | --------------------- | ------------ | ---------------- |
-| Servicio API de Horizon | 4 vCPU | 16 GB | 100 GB SSD >= 3K IOPS | [c5d.xlarge] | [n4-standard-4]  |
-
-_\* Asumiendo una ventana de retención de 30 días para el almacenamiento de datos._
-
-#### Instancia de Computación de Servidor de Base de Datos PostgreSQL:
-
-| Tipo de Nodo          | CPU    | RAM   | Disco                                                 | AWS SKU      | Google Cloud SKU |
-| --------------------- | ------ | ----- | ----------------------------------------------------- | ------------ | ---------------- |
-| PostgreSQL de Horizon | 4 vCPU | 32 GB | 2 TB\* SSD (NVMe o Almacenamiento Directo) >= 7K IOPS | [i4g.xlarge] | [c3-highmem-8]   |
-
-_\* Asumiendo una ventana de retención de 30 días para el almacenamiento de datos._
-
-Ten en cuenta que se requiere un mínimo de la versión 12 de PostgreSQL.
-
-Estas especificaciones suponen una ventana de retención de 30 días para el almacenamiento de datos. Para una ventana de retención más larga, los requisitos del sistema serán más altos. Para más información sobre la ingestión de datos, retención de histórico y gestión del almacenamiento, consulta la sección de [ingestión](./ingestion.mdx).
-
-## Despliegue de Múltiples Instancias
-
-Para lograr alta disponibilidad, redundancia y alto rendimiento, consulta la documentación de [escalado](./scaling.mdx). Proporciona una descripción detallada de varias estrategias de despliegue que puedes emplear, dependiendo del SLA que necesites que tu instancia de Horizon logre.
-
-## Acceso a la Red
-
-- Asegúrate de que la instancia de Horizon pueda establecer una conexión con la instancia de base de datos PostgreSQL. El puerto predeterminado para PostgreSQL es 5432.
-
-- Se requiere una conexión de red estable y rápida con Internet para cualquier instancia de Horizon que ejecute el rol de ingestión. Esto es para asegurar que tenga conectividad saliente eficiente con hosts remotos en el [quorum set](../../../../validators/admin-guide/configuring.mdx#choosing-your-quorum-set) y [archivos de historial](../../../../validators/admin-guide/environment-preparation.mdx#history-archives) para la red Stellar elegida. Durante la ingestión, la instancia de Horizon se comunica con estos hosts, recibiendo datos de transacciones de red a través de su subproceso cautivo local core.
-
-:::note
-
-Los requisitos de hardware pueden aumentar a medida que la red Stellar crece y/o si compartes recursos o usas configuraciones personalizadas.
-
-:::
-
-[c5d.2xlarge]: https://aws.amazon.com/ec2/instance-types/c5/
-[n4-standard-4]: https://cloud.google.com/compute/docs/general-purpose-machines#n4-standard
-[i4g.xlarge]: https://aws.amazon.com/ec2/instance-types/i4g/
-[c3-highmem-8]: https://cloud.google.com/compute/docs/general-purpose-machines#c3_machine_types
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/running.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/running.mdx
deleted file mode 100644
index 8350c1c7c8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/running.mdx
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: Ejecutando
-sidebar_position: 40
----
-
-Una vez que hayas [establecido la base de datos de Horizon](./configuring.mdx#initialize-horizon-database) y hayas [identificado la configuración de tiempo de ejecución de Horizon por host](./configuring.mdx#prerequisites), estás listo para ejecutar Horizon.
-
-## Instalación en bare-metal
-
-Ejecuta el binario `stellar-horizon` con los [parámetros de entorno apropiados](./configuring.mdx#passing-configurations-to-horizon) establecidos (o `stellar-horizon-cmd serve` si [instalaste a través del gestor de paquetes](./installing.mdx#package-manager), que importará automáticamente tu configuración desde `/etc/default/stellar-horizon`).
-
-## Instalación en contenedor
-
-No ejecutas el binario de Horizon directamente, en su lugar, la imagen [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon) tiene un entrypoint predefinido que comenzará a ejecutar Horizon al iniciar la imagen. El proceso de Horizon obtendrá todos los ajustes de configuración de las variables de entorno del contenedor.
-
-### Daemon de Docker
-
-Usa `docker run stellar/stellar-horizon:<tag_version> --env-file <env_filename>`, y especifica cada bandera de configuración de Horizon identificada durante [Configurando](./configuring.mdx) como una línea separada en `<env_filename>` de `HORIZON_CONFIG_PARAM=value`.
-
-### Kubernetes usando Helm Chart
-
-Asegúrate de haber seguido el [prerrequisito](./installing.mdx#helm-chart-installation) de instalar la herramienta Helm CLI y agregar el repositorio de gráficos de Stellar al cliente de Helm.
-
-El proceso de Horizon [requiere acceso a una base de datos Postgres 12](./prerequisites.mdx#postgresql-database-server-compute-instance). Primero, usa la herramienta común de CLI de Kubernetes `kubectl` desde tu estación de trabajo para crear un secreto de Kubernetes en el namespace previsto del clúster de Kubernetes que contendrá la URL de la base de datos de Horizon.
-
-<CodeExample>
-
-```bash
-# copy your horizon DATABASE_URL into a secure file, no line breaks.
-echo -n 'database_url_here' > my_creds.txt
-
-# now generate the kubernetes secret from the file
-kubectl create secret generic \
--n my-namepsace\
-my-db-secret \
---from-file=DATABASE_URL=my_creds.txt
-```
-
-</CodeExample>
-
-Ahora despliega Horizon en el clúster usando el Helm Chart:
-
-<CodeExample>
-
-```bash
-helm install my-horizon stellar/horizon \
---namespace my-horizon-namespace-on-cluster \
---set ingest.persistence.enabled=true \
---set web.replicaCount=1 \
---set web.enabled=true \
---set ingest.enabled=true \
---set ingest.replicaCount=1 \
---set web.existingSecret=my-db-secret \
---set global.image.horizon.tag=2.26.1 \
---set global.network=testnet \
---set ingest.existingSecret=my-db-secret \
---set ingest.horizonConfig.captiveCoreUseDb=true \
---set ingest.resources.limits.cpu=1 \
---set ingest.resources.limits.memory=6Gi
-```
-
-</CodeExample>
-
-Este ejemplo de uso de Helm Chart destaca algunos aspectos clave:
-
-- Usa el parámetro `global.network=[testnet|pubnet]`, esto automatiza la generación de todos los parámetros de configuración de Horizon específicos para la red, como las URLs de archivo, la configuración de núcleo cautivo y otros parámetros mencionados en [Configurando](./configuring.mdx).
-- `global.image.horizon.tag` debe establecerse en uno de los tags de Docker Hub publicados en [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon)
-- Habilita todos los roles en la instancia de despliegue: ingestión y API web (incluye la presentación de transacciones). Si eliges tener un despliegue multi-instancia con cada instancia realizando un solo rol de solo API web o ingestión, entonces harás dos instalaciones de Helm, una para cada rol: `my-horizon-ingestion-installation` y `my-horizon-api-installation`. Cada una de estas instalaciones de Helm establecerá `ingest.enabled`, `web.enabled`, `ingest.replicaCount`, `web.replicaCount` respectivamente para el rol que están realizando.
-- Para personalizar aún más, el mejor enfoque es descargar los [valores.yaml de Helm Chart de Horizon](https://github.com/stellar/helm-charts/blob/main/charts/horizon/values.yaml), actualizar los ajustes en tu copia local de values.yaml, y pasar a Helm install, en lugar de tener muchos `--set` individuales en Helm install:
-
-<CodeExample>
-
-```bash
-helm install myhorizon stellar/horizon \
---namespace my-horizon-namespace-on-cluster \
---values values.yaml
-```
-
-</CodeExample>
-
-- Personalizando parámetros de configuración de red, si deseas conectarte a una red diferente de las presets de `testnet` o `pubnet`, entonces no usarás `global.network`, en su lugar, usa una copia local de [values.yaml](https://github.com/stellar/helm-charts/blob/main/charts/horizon/values.yaml) y establece `ingest.coreConfig`, y consulta [\_core-config.tpl](https://github.com/stellar/helm-charts/blob/main/charts/horizon/templates/_core-config.tpl) para ejemplos de todos los pares clave/valor que incluir.
-
-- Límites mínimos de recursos, verifica si los valores predeterminados de `LimitRange` están definidos en el namespace de destino en Kubernetes para el despliegue, si es así, asegúrate de que los valores predeterminados proporcionen al menos límites mínimos de recursos de `6Gi` de memoria y `1` cpu. De lo contrario, define los límites explícitamente en la instalación de helm a través de `ingest.resources.limits.*` mostrados en el ejemplo, para asegurar que los pods desplegados tengan recursos adecuados.
-
-<br />
-
-Una vez que el proceso de Horizon comience, emitirá registros a la salida estándar. Al ejecutarse, debes ver una salida similar a:
-
-<CodeExample>
-
-```
-INFO[...] Starting horizon on :8000                     pid=29013
-```
-
-</CodeExample>
-
-Ten en cuenta que los números pueden ser naturalmente diferentes para tu instalación. La línea de registro anterior anuncia que Horizon está listo para atender solicitudes de clientes.
-
-A continuación, puedes confirmar que Horizon está respondiendo correctamente cargando el recurso raíz. En el ejemplo anterior, esa URL sería http://127.0.0.1:8000/, y simplemente ejecutando `curl http://127.0.0.1:8000/` te mostraría que el recurso raíz carga correctamente:
-
-<CodeExample>
-
-```json
-{
-  "_links": {
-    "account": {
-      "href": "http://127.0.0.1:8000/accounts/{account_id}",
-      "templated": true
-    },
-    "accounts": {
-      "href": "http://127.0.0.1:8000/accounts{?signer,sponsor,asset,cursor,limit,order}",
-      "templated": true
-    }
-  }
-  // etc.
-}
-```
-
-</CodeExample>
-
-Consulta [Monitoreo](./monitoring.mdx) para más detalles sobre el registro y las métricas en tiempo de ejecución de Horizon disponibles.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/scaling.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/scaling.mdx
deleted file mode 100644
index 1c1a3a7bcf..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/scaling.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Escalando
-sidebar_position: 70
----
-
-Horizon permite diferentes niveles lógicos que pueden escalarse independientemente para aumentar el rendimiento, la separación y la disponibilidad. Los siguientes componentes pueden escalarse de forma independiente:
-
-- API de servicio web (sirviendo)
-- Núcleo cautivo (ingestión y envío de transacciones)
-- Base de datos (almacenamiento)
-
-## Despliegue de una sola instancia
-
-Se recomienda comenzar con un [despliegue de una sola instancia](./prerequisites.mdx), y escalar según las necesidades de tu caso de uso particular.
-
-Este [despliegue](./configuring.mdx#single-instance-deployment) está destinado a usarse con retención mínima de historial (\<= 30 días) y volumen mínimo de solicitudes.
-
-En esta configuración, una sola instancia de Horizon realiza los tres [roles](./configuring.mdx#multiple-instance-deployment); ingestión, envío de transacciones y solicitudes de API de usuario final.
-
-![](/assets/horizon-scaling/Topology-single.png)
-
-## Escalando a múltiples instancias
-
-Hay varias razones por las que puedes optar por escalar a múltiples instancias de Horizon.
-
-- El escalado horizontal te permite atender más solicitudes de API y a un ritmo más rápido
-- La redundancia permite cero tiempo de inactividad en los casos donde Horizon requiere tiempo de inactividad para la actualización (migraciones, reconstrucción de estado, etc.)
-- Protección contra posibles retrasos en la ingestión, que podrían resultar en tiempo de inactividad para los usuarios finales
-
-Se pueden configurar múltiples instancias de Horizon para apuntar a la misma base de datos, y el proceso de ingestión no realizará trabajo redundante en estos casos.
-
-Al escalar Horizon, es importante tener en cuenta que se debe deshabilitar el [control de tasa](../api-reference/structure/rate-limiting.mdx) de Horizon y que el control de tasa debe ser gestionado externamente a Horizon dentro de la infraestructura. La implementación del control de tasa de Horizon se gestiona en memoria, por lo que no funciona con múltiples instancias.
-
-![](/assets/horizon-scaling/Topology-multiple.png)
-
-## Aislamiento lógico de la ingestión
-
-La ingestión es el proceso por el cual los nuevos ledgers se propagan en la base de datos de Horizon. Su salud es crítica, ya que las degradaciones en el rendimiento pueden resultar en retrasos con respecto al último ledger cerrado, dejando a tus usuarios finales sin conocer el estado actual de la red, y sin poder enviar nuevas transacciones con éxito. Cualquier retraso en la ingestión probablemente se consideraría tiempo de inactividad para tu servicio
-
-Horizon te permite configurar de manera independiente los diferentes [roles](./configuring.mdx#multiple-instance-deployment) que desempeña, incluida la ingestión. El diagrama a continuación ilustra cómo podrías separar lógicamente las instancias que atienden solicitudes de API de las instancias que realizan la ingestión, e introducir una base de datos de réplica de solo lectura para aislar aún más estos componentes. Esta configuración tiene varias ventajas:
-
-- Cada "rol" que juega Horizon puede escalarse de forma independiente
-- Las instancias de API son significativamente más ligeras desde la perspectiva de los requisitos de hardware, ya que no necesitan ejecutar el núcleo cautivo
-- Las instancias de API pueden escalarse horizontalmente o escalarse dinámicamente, en función de las necesidades específicas de tus usuarios finales
-- La ingestión y su rendimiento están aislados de la actividad de la API, por lo que los picos en la actividad del usuario no pueden degradarla ni causar retrasos en la ingestión. La salud de la ingestión es crítica, ya que las degradaciones en el rendimiento pueden resultar en retrasos con respecto al último ledger cerrado, dejando a tus usuarios finales sin conocer el estado actual de la red, y sin poder enviar nuevas transacciones con éxito
-
-El rol de la API de Horizon requiere solo permisos de solo lectura a una base de datos para todas las acciones que realiza. Sin embargo, las instancias de API necesitarán delegar todas las solicitudes de envío de transacciones a una instancia que ejecute el núcleo cautivo. Se podrían agregar más réplicas de base de datos si es necesario para admitir más solicitudes.
-
-![](/assets/horizon-scaling/Topology-ingestion-isolation.png)
-
-## Aislamiento lógico de la presentación de transacciones
-
-En el ejemplo anterior, la ingestión está aisladamente separada de la mayor parte del tráfico de la API, que históricamente ha sido la gran mayoría del tráfico. Sin embargo, la presentación de transacciones aún necesita ser atendida por una instancia principal, por lo que las instancias de API deben pasar sus solicitudes de presentación de transacciones a una instancia de ingestión.
-
-El diagrama a continuación ilustra cómo podríamos aislar (y escalar) aún más la presentación de transacciones, utilizando instancias de observadores del núcleo, en lugar de instancias de Horizon que ejecuten el núcleo cautivo. Esto nos permite proteger aún más la ingestión, previniendo el tiempo de inactividad y el retraso en la ingestión. También hace posible escalar horizontalmente la presentación de transacciones en sí, independientemente del resto del tráfico de la API.
-
-![](/assets/horizon-scaling/Topology-txsub.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/upgrading.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/upgrading.mdx
deleted file mode 100644
index a326e470eb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/upgrading.mdx
+++ /dev/null
@@ -1,139 +0,0 @@
----
-title: Actualizar
-sidebar_position: 80
----
-
-Aquí describiremos los pasos recomendados para actualizar una instalación de Horizon 2.x.
-
-### Requisitos previos
-
-- Una implementación existente de Horizon que consiste en una o más instancias de Horizon.
-- Todas las instancias están en la misma versión 2.x para comenzar.
-- Si la instalación es [bare-metal](./installing.mdx#bare-metal), tienes acceso a la shell o línea de comandos en cada host que tiene una instalación de Horizon.
-- Si está [desplegado directamente en el demonio de Docker](./installing.mdx#containerized), tienes acceso a la línea de comandos en el host que está ejecutando el demonio de Docker.
-- Si está [desplegado en Kubernetes con el gráfico de Helm](./installing.mdx#helm-chart-installation), tienes las herramientas de línea de comandos kubectl y helm en tu estación de trabajo y un inicio de sesión de usuario con los niveles de acceso apropiados para cambiar los recursos en el espacio de nombres objetivo de la implementación de Horizon en el clúster.
-
-### Evaluar la instalación actual
-
-- Identifica la lista de todas las instancias de Horizon que necesitan ser actualizadas.
-
-  - Instalaciones bare-metal: la lista de hosts es gestionada por ti.
-  - Despliegues del demonio de Docker: la lista de hosts y contenedores en ejecución es gestionada por ti.
-  - Despliegues en Kubernetes: obtén la lista de pods que están desplegados desde tu instalación anterior de Helm, tendrán una anotación para `release=your_helm_horizon_installation_name`:
-
-    <CodeExample>
-
-    ```bash
-    kubectl get pods -l release=your_helm_horizon_installation_name -n <your_horizon_namespace>
-    ```
-
-    </CodeExample>
-
-- Identifica tu versión actual del software Horizon:
-  - Obtén acceso a la línea de comandos del sistema operativo de cada instancia de Horizon:
-    - Instalaciones bare-metal, esto es típicamente ssh en Linux o Powershell en Windows.
-    - Despliegues del demonio de Docker, usa `docker exec -it <containerid> /bin/bash`
-    - Para despliegues en Kubernetes, usa `kubectl exec -it <pod_name> -n <horizon_namespace> -- /bin/bash`
-  - En la línea de comandos de cada instancia, ejecuta `stellar-horizon version`
-
-- Todas las instancias deberían informar la misma versión, si no, el sistema puede estar inconsistente, usa esta actualización como una oportunidad para establecer consistencia y lograr que todas estén en la misma versión.
-
-### Determina la versión objetivo para la actualización
-
-Ahora que sabes la versión actual de Horizon que tienes, visita [Horizon Releases](https://github.com/stellar/stellar-horizon/releases) y elige la siguiente versión mayor a la que tienes para actualizar. Sigue los pasos [recomendados por GitHub para comparar versiones](https://docs.github.com/en/repositories/releasing-projects-on-github/comparing-releases), haz clic en el menú desplegable `Comparar` de la versión elegida, y luego selecciona tu versión actual y GH mostrará las diferencias entre versiones, selecciona la pestaña `Archivos cambiados`, y ve a `services/horizon/CHANGELOG.md`, destacará las nuevas notas de publicación sobre los cambios que han ocurrido entre tu versión actual y la nueva versión seleccionada. Revisa esto y busca cualquier sección de `Cambios Críticos`, `Reconstrucción de Estado` y `Migración de Esquema de DB` para considerarlo, ya que estas últimas también mencionarán el tiempo esperado para que se aplique la reconstrucción del estado o la migración de la base de datos respectivamente.
-
-### Instalar la nueva versión
-
-Ahora que has identificado la nueva versión y eres consciente de los posibles impactos al actualizar a la nueva versión según las notas de publicación, como las reconstrucciones de estado y las migraciones de bases de datos, estás informado y listo para continuar con la actualización.
-
-Actualizar las implementaciones en producción debe aprovechar una implementación secundaria, de respaldo caliente, también conocida como un [modelo azul/verde](./scaling.mdx#scaling-to-multiple-instances) y realizar la actualización en la implementación inactiva primero. Esto evitará el tiempo de inactividad del sistema para tus usuarios externos, ya que la actualización tiene lugar en la implementación inactiva.
-
-Una buena estrategia para actualizar Horizon, aplicable a implementaciones de una sola o múltiples instancias: apaga todas las instancias, instala la nueva versión de Horizon en una de las instancias de ingestión primero. La razón es que el software de Horizon solo iniciará acciones de `Reconstrucción de Estado` y `Migración de Esquema de DB` relacionadas con una actualización en una instancia donde detecta que la ingestión ha sido habilitada con el parámetro de configuración `INGEST=true`. Esto reduce la complejidad durante la actualización, ya que solo necesitas concentrarte en una instancia y evita potenciales procesos de ingestión concurrentes de Horizon que intenten la misma actualización en la base de datos.
-
-- Instalaciones bare-metal, detén el proceso de Horizon en todas las instancias primero, luego accede a una instancia que esté configurada para la ingestión y usa el gestor de paquetes apt en Linux.
-
-  <CodeExample>
-
-  ```bash
-  sudo apt update
-  sudo apt install stellar-horizon=new_horizon_debian_pkg_version
-  ```
-
-  </CodeExample>
-
-  Reinicia Horizon usando la configuración ya existente, pero incluye la variable de entorno `APPLY_MIGRATIONS=true`, esto hará que Horizon ejecute automáticamente cualquier migración de base de datos que detecte que son necesarias.
-
-- Despliegues en el demonio de Docker, detén primero todos los contenedores de Docker, luego elige un contenedor que tenga habilitada la ingestión, establece la nueva etiqueta para la imagen basada en la versión publicada en Docker Hub - [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon/tags), y reinicia el contenedor en el demonio de Docker, incluyendo la variable de entorno `APPLY_MIGRATIONS=true`, esto hará que Horizon ejecute automáticamente cualquier migración de base de datos que detecte que son necesarias.
-
-- Para las instalaciones de Helm en Kubernetes, primero usa tu herramienta cli de Helm para detener todas las instancias de Horizon escalando todas tus instalaciones de Horizon (para ingestión y web) a 0 réplicas, que has creado previamente en [pasos de ejecución](./running.mdx).
-
-  <CodeExample>
-
-  ```bash
-  helm upgrade all-my-horizon-installations \
-  --namespace my-horizon-namespace-on-cluster \
-  --set ingest.replicaCount=0 \
-  --set web.replicaCount=0
-  ```
-
-  </CodeExample>
-
-  Ahora, usa Helm para iniciar solo una instancia de Horizon desde una instalación de Helm que tenga la ingestión habilitada en el clúster de Kubernetes, establecerás `global.image.horizon.tag` en la etiqueta de versión publicada en [stellar/stellar-horizon](https://hub.docker.com/r/stellar/stellar-horizon/tags)
-
-  <CodeExample>
-
-  ```bash
-  helm upgrade my-horizon \
-  --namespace my-horizon-namespace-on-cluster  \
-  --set global.image.horizon.tag=new_horizon_release_number \
-  --set ingest.horizonConfig.applyMigrations=True \
-  --set ingest.replicaCount=1
-  ```
-
-  </CodeExample>
-
-### Confirmar la actualización en una sola instancia de ingestión primero
-
-Si tienes infraestructura de [monitoreo](./monitoring.mdx) en su lugar, entonces tienes dos opciones para evaluar el estado de la actualización:
-
-- Ver los resultados de métricas utilizando tableros de Grafana que aprovechan las consultas sobre el [modelo de datos de métricas de Horizon](./monitoring.mdx#data-model) para comprobar estadísticas clave como la ingestión y los ledgers de red que están avanzando y en sincronía.
-
-- Ver la URL de 'estado' del servidor web de Horizon en la instancia actualizada:
-
-  <CodeExample>
-
-  ```bash
-  curl http://localhost:8000/
-  ```
-
-  </CodeExample>
-
-  La respuesta será un código de estado HTTP 200 y el cuerpo de la respuesta será una estructura de datos JSON basada en texto con información diagnóstica sobre la versión actual del software Horizon y los números de ledger para la ingestión y la red, actualiza la URL cada 5 segundos aproximadamente, y deberías ver los números de ledger de ingestión y de red avanzando y sincronizados, indicando una buena conexión a la red y la ingestión.
-
-Si las métricas y/o la respuesta de la URL de 'estado' de Horizon no indican un estado saludable basado en el avance de la ingestión del ledger, hay dos pasos para investigar más:
-
-- Un retraso en que Horizon logre un estado saludable tras una actualización es esperado y legítimo para cualquier caso de actualización donde se haya señalado `Reconstrucción de Estado` o `Migración de DB` en el delta de la versión como parte del paso previo [Determinar la versión objetivo para la actualización](#determine-the-target-version-for-upgrade). Generalmente las notas también mencionarán las expectativas de tiempo relativas para que esas tareas se completen, lo que puede ser considerado sobre cuánto esperar ante un retraso.
-- Revisa los registros de la instancia actualizada para confirmar qué está pasando. Cualquier `Reconstrucción de Estado` o `Migración de DB` iniciada será mencionada. Por ejemplo, una migración de base de datos será mencionada en los registros con las siguientes líneas para el inicio y el final:
-  ```
-  2023/09/22 18:27:01 Applying DB migrations...
-  2023/09/22 18:27:01 successfully applied 5 Horizon migrations
-  ```
-
-### Actualizar todas las instancias restantes
-
-En este punto, has actualizado una instancia de ingestión a la nueva versión de Horizon, se ha actualizado automáticamente la base de datos si era necesario y la instancia está funcionando con un estado saludable. Ahora, instala la misma versión de software de Horizon en el resto de las instancias, reiniciando cada una después de la actualización. Para instalaciones bare-metal y del demonio de Docker, eso probablemente será autoexplicativo sobre cómo lograrlo para el resto de las instancias, en instalaciones de gráficos Helm, ejecuta de nuevo la actualización de Helm, configurando la etiqueta de la imagen y también restaurando los `replicaCount` originales:
-
-<CodeExample>
-
-```bash
-helm upgrade all-my-horizon-installations \
---namespace my-horizon-namespace-on-cluster \
---set ingest.replicaCount=1 \
---set web.replicaCount=1 \
---set global.image.horizon.tag=new_horizon_release_number \
---set ingest.horizonConfig.applyMigrations=False
-```
-
-</CodeExample>
-
-Para implementaciones en producción siguiendo el modelo de respaldo caliente o azul/verde, esta es la oportunidad de confirmar que la implementación inactiva ha tomado correctamente la actualización y es estable, en este punto, cambia los balanceadores de carga para dirigir el tráfico a la implementación inactiva, haciendo que sea la implementación activa. Ahora, puede tomar tiempo realizar la misma actualización en la otra implementación que ahora está inactiva.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/README.mdx
deleted file mode 100644
index aae7952326..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Referencia de API
-sidebar_position: 20
-sidebar_key: horizon-api-reference
----
-
-import DocCardList from "@theme/DocCardList";
-
-Ver toda la información de la API de Horizon.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/_category_.json
deleted file mode 100644
index 9e3a55f459..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/README.mdx
deleted file mode 100644
index 63f5c5ff81..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Agregaciones
-sidebar_position: 30
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Puntos finales que agregan datos sobre el ledger.
-
-<MethodTable title="Tipos de Recursos">
-
-|                                                                     |   |
-| ------------------------------------------------------------------- | - |
-| [Libros de Pedidos](./order-books/README.mdx)                       |   |
-| [Rutas](./paths/README.mdx)                                         |   |
-| [Agregaciones de Comercio](./trade-aggregations/README.mdx)         |   |
-| [Estadísticas de Tarifas](./fee-stats/README.mdx)                   |   |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/fee-stats/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/fee-stats/README.mdx
deleted file mode 100644
index 962878af1c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/fee-stats/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Estadísticas de tarifas
-sidebar_position: 50
----
-
-Las estadísticas de tarifas se utilizan para predecir qué tarifa establecer para una transacción antes de enviarla a la red.
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                |
-| ------- | ---------------------------------------------- |
-| OBTENER | [/fee-stats](../../retrieve-fee-stats.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/fee-stats/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/fee-stats/object.mdx
deleted file mode 100644
index 81c2e971b0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/fee-stats/object.mdx
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: El objeto de estadísticas de tarifas
-sidebar_position: 20
----
-
-Cuando Horizon devuelve estadísticas de tarifas, utiliza el siguiente formato.
-
-Nota: El `fee_charged` representa la tarifa real pagada por la transacción, mientras que `max_fee` representa la oferta máxima que el creador de la transacción estaba dispuesto a pagar por la transacción.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- last_ledger
-  - cadena
-  - El número de secuencia del último ledger.
-- last_ledger_base_fee
-  - cadena
-  - La tarifa base definida en el último ledger.
-- ledger_capacity_usage
-  - cadena
-  - El uso promedio de capacidad durante los últimos 5 ledgers (0 es sin uso, <b>1.0</b> son ledgers completamente llenos).
-- fee_charged
-  - objeto
-  - Información sobre la tarifa cobrada por transacciones en los últimos 5 ledgers.
-    - min
-      - cadena
-      - La tarifa mínima cobrada durante los últimos 5 ledgers.
-    - modo
-      - cadena
-      - Tarifa de modo cobrada durante los últimos 5 ledgers.
-    - p10
-      - cadena
-      - La tarifa del percentil 10 cobrada durante los últimos 5 ledgers.
-    - p20
-      - cadena
-      - La tarifa del percentil 20 cobrada durante los últimos 5 ledgers.
-    - p30
-      - cadena
-      - La tarifa del percentil 30 cobrada durante los últimos 5 ledgers.
-    - p40
-      - cadena
-      - La tarifa del percentil 40 cobrada durante los últimos 5 ledgers.
-    - p50
-      - cadena
-      - La tarifa del percentil 50 cobrada durante los últimos 5 ledgers.
-    - p60
-      - cadena
-      - La tarifa del percentil 60 cobrada durante los últimos 5 ledgers.
-    - p70
-      - cadena
-      - La tarifa del percentil 70 cobrada durante los últimos 5 ledgers.
-    - p80
-      - cadena
-      - La tarifa del percentil 80 cobrada durante los últimos 5 ledgers.
-    - p90
-      - cadena
-      - La tarifa del percentil 90 cobrada durante los últimos 5 ledgers.
-    - p95
-      - cadena
-      - La tarifa del percentil 95 cobrada durante los últimos 5 ledgers.
-    - p99
-      - cadena
-      - La tarifa del percentil 99 cobrada durante los últimos 5 ledgers.
-- max_fee
-  - objeto
-  - Información sobre la oferta de tarifa máxima para transacciones en los últimos 5 ledgers.
-    - min
-      - cadena
-      - Valor mínimo (más bajo) de la oferta de tarifa máxima durante los últimos 5 ledgers.
-    - modo
-      - cadena
-      - Máximo modo de tarifa durante los últimos 5 ledgers.
-    - p10
-      - cadena
-      - La tarifa del percentil 10 máxima cobrada durante los últimos 5 ledgers.
-    - p20
-      - cadena
-      - La tarifa del percentil 20 máxima cobrada durante los últimos 5 ledgers.
-    - p30
-      - cadena
-      - La tarifa del percentil 30 máxima cobrada durante los últimos 5 ledgers.
-    - p40
-      - cadena
-      - La tarifa del percentil 40 máxima cobrada durante los últimos 5 ledgers.
-    - p50
-      - cadena
-      - La tarifa del percentil 50 máxima cobrada durante los últimos 5 ledgers.
-    - p60
-      - cadena
-      - La tarifa del percentil 60 máxima cobrada durante los últimos 5 ledgers.
-    - p70
-      - cadena
-      - La tarifa del percentil 70 máxima cobrada durante los últimos 5 ledgers.
-    - p80
-      - cadena
-      - La tarifa del percentil 80 máxima cobrada durante los últimos 5 ledgers.
-    - p90
-      - cadena
-      - La tarifa del percentil 90 máxima cobrada durante los últimos 5 ledgers.
-    - p95
-      - cadena
-      - La tarifa del percentil 95 máxima cobrada durante los últimos 5 ledgers.
-    - p99
-      - cadena
-      - La tarifa del percentil 99 máxima cobrada durante los últimos 5 ledgers.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "last_ledger": "28444678",
-  "last_ledger_base_fee": "100",
-  "ledger_capacity_usage": "0.2",
-  "min_accepted_fee": "100",
-  "mode_accepted_fee": "100",
-  "p10_accepted_fee": "100",
-  "p20_accepted_fee": "100",
-  "p30_accepted_fee": "100",
-  "p40_accepted_fee": "100",
-  "p50_accepted_fee": "100",
-  "p60_accepted_fee": "100",
-  "p70_accepted_fee": "100",
-  "p80_accepted_fee": "100",
-  "p90_accepted_fee": "100",
-  "p95_accepted_fee": "100",
-  "p99_accepted_fee": "10000",
-  "fee_charged": {
-    "max": "100",
-    "min": "100",
-    "mode": "100",
-    "p10": "100",
-    "p20": "100",
-    "p30": "100",
-    "p40": "100",
-    "p50": "100",
-    "p60": "100",
-    "p70": "100",
-    "p80": "100",
-    "p90": "100",
-    "p95": "100",
-    "p99": "100"
-  },
-  "max_fee": {
-    "max": "16000",
-    "min": "100",
-    "mode": "100",
-    "p10": "100",
-    "p20": "100",
-    "p30": "100",
-    "p40": "100",
-    "p50": "100",
-    "p60": "100",
-    "p70": "100",
-    "p80": "100",
-    "p90": "100",
-    "p95": "100",
-    "p99": "10000"
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/order-books/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/order-books/README.mdx
deleted file mode 100644
index 1acb436039..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/order-books/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Ordenar Libros
-sidebar_position: 10
----
-
-Un libro de órdenes es una colección de ofertas para un par específico de activos.
-
-El [último ledger](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-Aprende más sobre [libros de órdenes](../../../../../../learn/glossary.mdx#decentralized-exchange).
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                     |
-| ------- | --------------------------------------------------- |
-| OBTENER | [/order_book](../../retrieve-an-order-book.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/order-books/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/order-books/object.mdx
deleted file mode 100644
index 519f0f32f3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/order-books/object.mdx
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: El Objeto del Libro de Órdenes
-sidebar_position: 10
----
-
-Cuando Horizon devuelve información sobre un libro de órdenes, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- ofertas
-  - objeto
-  - Los precios y las cantidades del lado comprador del par de activos.
-    - precio_r
-      - objeto
-      - Una representación precisa del precio de la oferta del par de activos.
-        - n
-          - número
-          - El numerador.
-        - d
-          - número
-          - El denominador.
-    - precio
-      - cadena
-      - El precio de la oferta del activo base expresado en el activo contra. Un número que representa la forma decimal de `precio_r`.
-    - cantidad
-      - cadena
-      - La cantidad del activo contra que la cuenta que realiza esta oferta está dispuesta a comprar a este precio.
-- ofertas
-  - objeto
-  - Los precios y las cantidades del lado vendedor del par de activos.
-    - precio_r
-      - objeto
-      - Una representación precisa del precio de la oferta del par de activos.
-        - n
-          - número
-          - El numerador.
-        - d
-          - número
-          - El denominador.
-    - precio
-      - cadena
-      - El precio de la oferta del activo base expresado en el activo contra. Un número que representa la forma decimal de `precio_r`.
-    - cantidad
-      - cadena
-      - La cantidad del activo contra que la cuenta que realiza esta oferta está dispuesta a vender a este precio.
-- base
-  - objeto
-  - Detalles sobre el activo base.
-    - tipo_de_activo
-      - cadena
-      - El tipo para el activo base. Ya sea `nativo`, `credito_alphanum4`, o `credito_alphanum12`.
-    - código_de_activo
-      - cadena
-      - El código para el activo base.
-    - emisor_de_activo
-      - cadena
-      - La dirección Stellar del emisor del activo base.
-- contra
-  - objeto
-  - Detalles sobre el activo contra.
-    - tipo_de_activo
-      - cadena
-      - El tipo para el activo contra. Ya sea `nativo`, `credito_alphanum4`, o `credito_alphanum12`.
-    - código_de_activo
-      - cadena
-      - El código para el activo contra.
-    - emisor_de_activo
-      - cadena
-      - La dirección Stellar del emisor del activo contra.
-
-</AttributeTable>
-
-El [último libro mayor](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-<ExampleResponse>
-
-```json
-{
-  "bids": [
-    {
-      "price_r": {
-        "n": 6014600,
-        "d": 102275119
-      },
-      "price": "0.0588080",
-      "amount": "0.1722469"
-    },
-    {
-      "price_r": {
-        "n": 1250000,
-        "d": 21831117
-      },
-      "price": "0.0572577",
-      "amount": "0.2991796"
-    }
-  ],
-  "asks": [
-    {
-      "price_r": {
-        "n": 118163,
-        "d": 2000000
-      },
-      "price": "0.0590815",
-      "amount": "8057.2710223"
-    },
-    {
-      "price_r": {
-        "n": 60627,
-        "d": 1000000
-      },
-      "price": "0.0606270",
-      "amount": "10000.0000000"
-    }
-  ],
-  "base": {
-    "asset_type": "native"
-  },
-  "counter": {
-    "asset_type": "credit_alphanum4",
-    "asset_code": "USD",
-    "asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/paths/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/paths/README.mdx
deleted file mode 100644
index 1f7a5e5d7d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/paths/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Rutas
-sidebar_position: 20
----
-
-Las rutas proporcionan información sobre pagos de ruta potenciales. Una ruta se puede usar para completar los campos necesarios para una operación de pago de ruta.
-
-El [ledger más reciente](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-Aprende más sobre los dos tipos de pagos de ruta: [`pago de ruta estricto enviar`](../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-send) y [`pago de ruta estricto recibir`](../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-receive)
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                                          |
-| ------- | ------------------------------------------------------------------------ |
-| OBTENER | [/rutas/strict-receive](../../list-strict-receive-payment-paths.api.mdx) |
-| OBTENER | [/rutas/strict-send](../../list-strict-send-payment-paths.api.mdx)       |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/paths/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/paths/object.mdx
deleted file mode 100644
index 0422d7129d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/paths/object.mdx
+++ /dev/null
@@ -1,135 +0,0 @@
----
-title: El Objeto de Ruta
-sidebar_position: 10
----
-
-Cuando Horizon devuelve información sobre una ruta, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- tipo_de_activo_origen
-  - cadena
-  - El tipo para el activo fuente. Puede ser `native`, `credit_alphanum4`, o `credit_alphanum12`.
-- código_de_activo_origen
-  - cadena
-  - El código para el activo fuente.
-- emisor_de_activo_origen
-  - cadena
-  - La dirección Stellar del emisor del activo fuente.
-- monto_origen
-  - cadena
-  - Un costo estimado para realizar un pago de destination_amount en esta ruta. Adecuado para usar en el campo `sendMax` de una operación de pago por ruta.
-- tipo_de_activo_destino
-  - cadena
-  - El tipo para el activo de destino. Puede ser `native`, `credit_alphanum4`, o `credit_alphanum12`.
-- código_de_activo_destino
-  - cadena
-  - El código para el activo de destino.
-- emisor_de_activo_destino
-  - cadena
-  - La dirección Stellar del emisor del activo de destino.
-- monto_destino
-  - cadena
-  - La cantidad de destino especificada en la búsqueda que encontró esta ruta.
-- ruta
-  - array de objetos
-  - Los activos intermedios por los que pasa esta ruta.
-    - código_de_activo
-      - cadena
-      - El código para este activo intermedio.
-    - emisor_de_activo
-      - cadena
-      - La dirección Stellar del emisor del activo intermedio.
-    - tipo_de_activo
-      - cadena
-      - El tipo para el activo intermedio. Puede ser `native`, `credit_alphanum4`, o `credit_alphanum12`.
-
-</AttributeTable>
-
-El [último libro mayor](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-<ExampleResponse>
-
-```json
-{
-  "_embedded": {
-    "records": [
-      {
-        "source_asset_type": "credit_alphanum4",
-        "source_asset_code": "USD",
-        "source_asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX",
-        "source_amount": "4.1900246",
-        "destination_asset_type": "credit_alphanum4",
-        "destination_asset_code": "BB1",
-        "destination_asset_issuer": "GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN",
-        "destination_amount": "5.0000000",
-        "path": [
-          {
-            "asset_type": "credit_alphanum4",
-            "asset_code": "NGNT",
-            "asset_issuer": "GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD"
-          },
-          {
-            "asset_type": "native"
-          }
-        ]
-      },
-      {
-        "source_asset_type": "native",
-        "source_amount": "162.0291692",
-        "destination_asset_type": "credit_alphanum4",
-        "destination_asset_code": "BB1",
-        "destination_asset_issuer": "GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN",
-        "destination_amount": "5.0000000",
-        "path": [
-          {
-            "asset_type": "credit_alphanum4",
-            "asset_code": "EURT",
-            "asset_issuer": "GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"
-          }
-        ]
-      },
-      {
-        "source_asset_type": "native",
-        "source_amount": "162.3284659",
-        "destination_asset_type": "credit_alphanum4",
-        "destination_asset_code": "BB1",
-        "destination_asset_issuer": "GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN",
-        "destination_amount": "5.0000000",
-        "path": [
-          {
-            "asset_type": "credit_alphanum4",
-            "asset_code": "USD",
-            "asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
-          },
-          {
-            "asset_type": "credit_alphanum4",
-            "asset_code": "EURT",
-            "asset_issuer": "GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"
-          }
-        ]
-      },
-      {
-        "source_asset_type": "native",
-        "source_amount": "367.4324508",
-        "destination_asset_type": "credit_alphanum4",
-        "destination_asset_code": "BB1",
-        "destination_asset_issuer": "GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN",
-        "destination_amount": "5.0000000",
-        "path": [
-          {
-            "asset_type": "credit_alphanum4",
-            "asset_code": "BTC",
-            "asset_issuer": "GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx
deleted file mode 100644
index 33f0701652..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/trade-aggregations/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Agregaciones de Comercio
-sidebar_position: 40
----
-
-Una agregación de comercio representa estadísticas agregadas sobre un par de activos (base y contrapartida) para un período de tiempo específico. Las agregaciones de comercio son útiles para los desarrolladores de clientes de comercio y proporcionan datos históricos de comercio.
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                              |
-| ------- | ------------------------------------------------------------ |
-| OBTENER | [/trade_aggregations](../../list-trade-aggregations.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.mdx
deleted file mode 100644
index 83e3f2fa80..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/aggregations/trade-aggregations/object.mdx
+++ /dev/null
@@ -1,236 +0,0 @@
----
-title: El objeto de agregación de operaciones
-sidebar_position: 10
----
-
-Cuando Horizon devuelve información sobre una agregación de operaciones, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- marca de tiempo
-  - cadena
-  - Hora de inicio para esta agregación de operaciones. Representado como milisegundos desde la época.
-- contador_de_operaciones
-  - entero
-  - Número total de operaciones agregadas.
-- volumen_base
-  - cadena
-  - Volumen total del activo base.
-- volumen_contraparte
-  - cadena
-  - Volumen total del activo contra.
-- promedio
-  - cadena
-  - Precio promedio ponderado del activo contra en términos del activo base.
-- alto
-  - cadena
-  - El precio más alto durante este período de tiempo.
-- alto_r
-  - objeto
-  - El precio más alto durante este período de tiempo como número racional.
-    - n
-      - número
-      - El numerador.
-    - d
-      - número
-      - El denominador.
-- bajo
-  - cadena
-  - El precio más bajo durante este período de tiempo.
-- bajo_r
-  - objeto
-  - El precio más bajo durante este período de tiempo como número racional.
-    - n
-      - número
-      - El numerador.
-    - p
-      - número
-      - El denominador.
-- abrir
-  - cadena
-  - El precio como se ve en la primera operación agregada.
-- abrir_r
-  - objeto
-  - El precio como se ve en la primera operación agregada como número racional.
-    - n
-      - número
-      - El numerador.
-    - p
-      - número
-      - El denominador.
-- cerrar
-  - cadena
-  - El precio como se ve en la última operación agregada.
-- cerrar_r
-  - objeto
-  - El precio como se ve en la última operación agregada como número racional.
-    - n
-      - número
-      - El numerador.
-    - p
-      - número
-      - El denominador.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/trade_aggregations?base_asset_type=native\u0026counter_asset_code=NGNT\u0026counter_asset_issuer=GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD\u0026counter_asset_type=credit_alphanum4\u0026limit=200\u0026order=asc\u0026resolution=3600000\u0026start_time=1582156800000\u0026end_time=1582178400000"
-    },
-    "next": {
-      "href": "https://horizon-testnet.stellar.org/trade_aggregations?base_asset_type=native\u0026counter_asset_code=NGNT\u0026counter_asset_issuer=GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD\u0026counter_asset_type=credit_alphanum4\u0026end_time=1582178400000\u0026limit=200\u0026order=asc\u0026resolution=3600000\u0026start_time=1582178400000"
-    },
-    "prev": {
-      "href": ""
-    }
-  },
-  "_embedded": {
-    "records": [
-      {
-        "timestamp": 1582156800000,
-        "trade_count": 9,
-        "base_volume": "3487.4699458",
-        "counter_volume": "88675.3982178",
-        "avg": "25.4268566",
-        "high": "25.7603393",
-        "high_r": {
-          "N": 257603393,
-          "D": 10000000
-        },
-        "low": "25.3804530",
-        "low_r": {
-          "N": 25380453,
-          "D": 1000000
-        },
-        "open": "25.3990186",
-        "open_r": {
-          "N": 2500000,
-          "D": 98429
-        },
-        "close": "25.7090558",
-        "close_r": {
-          "N": 1250000,
-          "D": 48621
-        }
-      },
-      {
-        "timestamp": 1582160400000,
-        "trade_count": 1,
-        "base_volume": "0.1058787",
-        "counter_volume": "2.7155348",
-        "avg": "25.6476024",
-        "high": "25.6476019",
-        "high_r": {
-          "N": 100000,
-          "D": 3899
-        },
-        "low": "25.6476019",
-        "low_r": {
-          "N": 100000,
-          "D": 3899
-        },
-        "open": "25.6476019",
-        "open_r": {
-          "N": 100000,
-          "D": 3899
-        },
-        "close": "25.6476019",
-        "close_r": {
-          "N": 100000,
-          "D": 3899
-        }
-      },
-      {
-        "timestamp": 1582164000000,
-        "trade_count": 15,
-        "base_volume": "3992.1321821",
-        "counter_volume": "99702.0620798",
-        "avg": "24.9746395",
-        "high": "25.6764460",
-        "high_r": {
-          "N": 5000000,
-          "D": 194731
-        },
-        "low": "24.9291379",
-        "low_r": {
-          "N": 249291379,
-          "D": 10000000
-        },
-        "open": "25.6764460",
-        "open_r": {
-          "N": 5000000,
-          "D": 194731
-        },
-        "close": "25.0055050",
-        "close_r": {
-          "N": 5001101,
-          "D": 200000
-        }
-      },
-      {
-        "timestamp": 1582167600000,
-        "trade_count": 4,
-        "base_volume": "278.4950271",
-        "counter_volume": "7047.6740325",
-        "avg": "25.3062832",
-        "high": "25.3844475",
-        "high_r": {
-          "N": 5000000,
-          "D": 196971
-        },
-        "low": "25.2923181",
-        "low_r": {
-          "N": 252923181,
-          "D": 10000000
-        },
-        "open": "25.2923181",
-        "open_r": {
-          "N": 252923181,
-          "D": 10000000
-        },
-        "close": "25.3844475",
-        "close_r": {
-          "N": 5000000,
-          "D": 196971
-        }
-      },
-      {
-        "timestamp": 1582174800000,
-        "trade_count": 1,
-        "base_volume": "9.9379734",
-        "counter_volume": "252.7685174",
-        "avg": "25.4346140",
-        "high": "25.4346140",
-        "high_r": {
-          "N": 254346140,
-          "D": 10000000
-        },
-        "low": "25.4346140",
-        "low_r": {
-          "N": 254346140,
-          "D": 10000000
-        },
-        "open": "25.4346140",
-        "open_r": {
-          "N": 254346140,
-          "D": 10000000
-        },
-        "close": "25.4346140",
-        "close_r": {
-          "N": 254346140,
-          "D": 10000000
-        }
-      }
-    ]
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/cb-retrieve-related-operations.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/cb-retrieve-related-operations.api.mdx
deleted file mode 100644
index 7ed4192712..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/cb-retrieve-related-operations.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: cb-retrieve-related-operations
-title: "Retrieve Related Operations"
-description: "This endpoint represents successful operations referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time."
-sidebar_label: "Retrieve Related Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXOtSGzkWfhVV/5hJUu0bBmNcNTXLLYEZBgiQ3ZohlCNLp90K3VKPpMYwlKv2Nfb19km2jvriNjQEQjJJNuYPZbd0dO7nqK1P156lY+MNTr3NiIqYjiIgGzSikoHxznyPg2FaJFYo6Q28k1AYApInSkhLNCQaDEhriEkZA2OCNCIqAU1xvCEaAtAgmZBjQslYXIAkrFxmlC1DqOSEUUlGQFIDnAhJjNVAY5wWKw5Ncjz3mdAoUhNDrlRKrCKRMBYkCZQmEiZ3rW+R9ZrFDbEhXBGqgVDOgSNFGwI5thBFVJMI+Bh0k+wGhNEoquPPJztKi7+UJBMRRcRYqi2h1pEBqiMBxpJzqSZyxhxJZQTGEEpYqo3SRBhiwPpIfRIKFhJGDRBhqzQDrWJiQ2rzSU2ycYWzbCYgFLQuaJQCCiLVxHdqQv1mTFf1wzRQC5wYgaq4UqkmGv5MkV0rYmh6vleO3uXewNvcOAKrBVzAEUQ49aAk5vleQjWNwYJGf7r2JI3BG3ilzoe5zoeCe74n0J8SakPP93BRoYF7A6tTuOl06ySV4s8UiOAgrQgEaGfseosi04aFEFNvcO3ZqwR5MFYLOfamU3/GllNVwcifKeirOU4CGpkaVmQaj0BnRnBRYFDPlJgEmAgEI5FimYGFROOqKALmPquAaDCJkgaM83lhSJI6j8rtCiShYyHHQ6vOQeZWVAGhRANTmteKJqSFMaAgcEnjJAJv0Ou1e73O6vJqf21lrdNeqYqtNIfHS83BiLGkhRzIqiM089aMQ0NMqNKIE5okQHWTHCSZpwnJopQDeUcNe0eeUcNAciHHz4nS5B0u9448w3/51y7enIGpHqcxSEuEkf/9939sHiWWcAhoGmX6d2Tvs7zvgUxjTHPUMC8T0DurKiYSsbCPVMxJCCSmlyJO48IxnJUzVWiwqZbAmwTHOfouDjWVY8hs3kHml9pt0iBUkjRJQOcDnYMJQ0KqOVM8SztFmkHvT0AHSscuiWmgRklzj9IKAwK/pbtO+6F+1WlXFZabdBhQEQF/pOaOwbpEq7M8VbhHRquaooTEqEFebzuTm42R5JaolWKkVARUzuzvEowbP2f990rIjxWBSkNZxllFFIyRuWd5Vs9TLlAWlqE0Jy5+UySKpjc9873LhkmTRGlrGmXhKVJlmVJQ6KV2G//d4DMrzZ7vMSUtSItDaJJEIktUrfcGx11XlEej6CBwOTxXoxq9B4bRkWhk1opsvWEk5LmpqPuOcQai4MOjQg1BXeQ6N7cuROW5N/U9C3Hiqk+NoafTquFOM6JnvmeFjaBCQ8Kl/cpYSjRcfFUsTXFY8dWeMzWGjJLw/+4dlcD9yjiDIABmH6DVv5Ur1/4D/9rYSjQw4PB1sXVjkPP+eY+bWbmi2Yo0Z1PfE7yO3WIlwZ34lW6yphmeW3Q428HVSeZ7RqWawZAyplJp6xZPqLWgseS8Ol1v/NFurJ1dr6xMK2xRzjWWIlzaTa5p04pmw8sqZblgPmcoKrOynqs6qz3184l8SGu4vCF0SE1YO8jtt1B5+a6idlCQSmymn6qKT6PSG27l9lhzDnCnuW/ZNrdOqfA5ldYosEZdpXJm4lUCYdORWy8t+8FKAvEIcHP+4UDOm+/KQKo1xXZOWIgfkAkWVWtRtRZVa1G1PrJqJfQKN9615WomwqcoUdQYsMN6jsrH+OoAHxdvP/AdzgVkGZ0LO6RRElKZxsu3v+osOZNldIQx6ScodfjS4+lGUE8vuXG9O3zZKlqxaK4qJ2zJ7tl0fkt2WPraoqgtitqiqC2K2mcrajYc5pVtiM+ZHaIGsJQ8bF+29DcUPf/JVa6olncs+70UQT/7Xe6jt1DfvpFcmS3C7G41cTBWZD+LDWNRH9gFlfu7tblRd0o4N+rTCPol+52aFscvfhKeV/5tVZ9V2yAb5q3QsctNR2VqWvRFi75o0Rct+qK/sS8yIPkDm6JOd9EVLbqib8dID+yK8hExvVw0RJ+vIbqtxvtaouMsKy36oUU/tOiHFv3QZ+qH8pWGMejxQ98M9T9VD/SJpBTyyU3El/0RoZzpJKn4cv57+2+Zcc6m6JO5GVxA3Xe4e3DtuePI80WiKANZKHqhtYkZtFphdky1YcFYCbZpsqP0TaXHrVunwU2rnf91Vvv9pV4wCqDbXYNOsMJWusudVdYLgAewxNor0B8B6yx3293OchfYcm/U7a/1O6P2GusGa63ZOcqfs9PdP/3gDtP+1P3BnVb+Cc/+Vs7+fbVsd5bbveV+b2Wtv9zpt3vd7mq9IMWJwW9XEHcOGwNm7ohHeYjj9IneNuOodZuVmq7hEaSrZ3tbAVuha/2Adfu9NR4st/sw4suUddgSdAMIgPVHbdpf6UN/KQg6vLMM3d5Sb7W32u6P1jrQv9EmfCoJWwXNG/X+EfRzCj/PzPXDnba9Wb8/ehl6/yp5LfVqnt2soPVj7iqi2ZHqm2XTe7W1+cvuzla3t9Q92Px9f6e38ubN683u/t6rpa3e75v7m1uHf7zZO9rb3DtYX+2dbLw+2uutd09eFtm7PMt2K/hmiX3QWZ6vg95Se6nd6HQaS92TTm/QXhp0+3/UpfyB92Tv8z13iFzppwnr9iLewNs42NrZHTyFUL659NrNTpabsPA55UmbpYXK+2BkemP7zdav6/u7Lw9PXu4c/uuXlZPuUe9o96DbO3q98fLVzu+H6697xyc7q7/+tr+1s37S7e3tHOxtZS0ax5PwrrSlkinJBVKluT9MXaXM/7BgWpAmq4mn1945XHmD+gP6flExHZUz34vBhgr9dgzlvm7g1WXk6zrM1LQS62gx0BcF0irV0cPizKtDsJxk48g+2InS526bWE8xSG2q4SE0XxYjiSyonmFHEmS9Vd6R5HgWVBVok81uN9vNjuui45jqq9kokmh1IbgDT5Gdk5NDsn64i4gLTi0tgBMFai9ftUl2LRFyDMZmmCsNDac4h/rLZiZa8ZQBJ6OrOhIZjgs3FSUmB6hBDJpVhClp0hiKqfQCNB0DqaAriMZeSlxAgSus4HYaSguQiAZxjJRwyhwL4sCQo6uSoU2lAbFEwjjJK3KMtOBjICOwEwCJy2fSzs881Ao3UoZE4hzIBMGM1viEAwNpNY3EX4hLuWQh4pOM7yi4kCbZmxXHUYlBsoqYdOSgSpVK6BOHnkET5fmzwOX5iPTKIYhw4UCjjo+b+JnZzOYtz/rePeG0atCzZ0V4criACJODmaupOdstpjQ0pOLw/LvynrfyrSyWy+HF1JV64ORCUMLeHO35hJKRVhMD2q2gJBSgrFLXx1u/mg/qmitmWlapyLQMPzeoaUU0oDtlwFyF26xLYa+QvkPaJplCfTIBBxmMY5DcgXVRUVTiwkRIY4FynBTTc4T5cqGBWWdDxCMbJ6cz6zgVHEgWMSMwJFQTpxIeC4kQaU0KF3fuWOgGl3AowmcOLl145+lWKemPZCNS45kOJpPJvPDlyMYoUuMWbUiYNEwqG1iFQmjk9eO5Ay4ahWFC2flYq1RyouTNaMh8R7NQWGA21TQiIsaYh9hZXuUox5i+R7BzVjrIKI2T503yErHUMnsJhF/TkUoR8OhYRAXm65WuoTiMqAGfsBDYOcHRVfkdjPIVqnamgLGwYTpqMhW3cj20xqo1itSoFVPUdAvDS2Apz0VvIZxSSxplnvLqze7W9vDlwdFwa/uf23sHh9tHx82YP3fG3IBAaUC3GMFYSARs/mjIRGmLMFthXROQA74xSQjHIrBQZShRxz0GLdlX/GPSBOGKOfio0+CAvHgxAcIRTW4R/K+0AaJTKZGJQo1o0CxJUQSrS04jDKZqDik97cWLLD2AA03TKLpypN3c4QWNBHcCDm9VPsDA0EDsRBEDCDe3GFqSgZZ5yuHAVJpEuX5iTNIixtaMSuvcb6ScGiNBRyLCeMRZFedrzgUGxl5MJR2DIQJdbyJ9klANvMERz184nwrmRVWJFbFLibhmPhNTHiZEFRCJWzHybAI/RhGpxB1id/FSgLfeJk1csUByb71Sd+giuAsAHZuD4Dhzs0qrNrdFxUENFTRyb8whoJS5tx858rVgu+ruLzEwaf5ic74VnG/8IKbCPYUoUv+oPpv6XiQYSAOVtdYTykIgS03s52do/vJJI3syWzFPNtQ9dTLlRE1rb3dze/94G6c0QxtHbluYKGNjKitLFq+0SP5Oi8zdWDDXXlzPALKLiy6+u4su8p26hUvbSiIq3Bt054nX+Vbt9PZVFuhDgzsuuKjs1s58L1TGIonrayw2b3Q0neLXGdbcbWiFQRp3oM2rvvnlL6Go1VW2FS6v1cg3v57bTj5GuG/mrol7tFDcsvGRSvg/ulfiHiUVN258pJI+0xUS9zB868aLec4/yOhnvSjiXs7z6y1m/J7hBy1Q1Y/MPs+O8p+2npPHX8xTy2JxnEZeVVksE0pddnW/XYVAHfy2fA23zhgkVY+6dcvF3Gu4V9sn3nT6PzNA8fQ=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/claimable_balances/{claimable_balance_id}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful operations referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"claimable_balance_id","in":"path","required":true,"description":"A unique identifier for this claimable balance.","schema":{"type":"string"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"oneOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"create_account"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"starting_balance":{"type":"string"},"funder":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","starting_balance","funder","account"],"title":"CreateAccount"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_receive"},"type_i":{"type":"number","example":2},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"destination_min":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","destination_min"],"title":"PathPaymentStrictReceive"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_send"},"type_i":{"type":"number","example":13},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"source_max":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","source_asset_type"],"title":"PathPaymentStrictSend"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"account_merge"},"type_i":{"type":"number","example":8},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"into":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","account","into"],"title":"AccountMerge"}]}]},"examples":{"CBRetrieveRelatedOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/operations?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/operations?cursor=140648659841806337&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/operations?cursor=140648659841806337&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/140648659841806337"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/140648659841806337/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=140648659841806337"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=140648659841806337"}},"id":"140648659841806337","paging_token":"140648659841806337","transaction_successful":true,"source_account":"GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","type":"create_claimable_balance","type_i":14,"created_at":"2020-11-23T16:02:38Z","transaction_hash":"fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8","sponsor":"GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","asset":"BODHI:GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","amount":"0.1000000","claimants":[{"destination":"GBEUDKANIFPTFHPWJ5T3R6RIO36RQBFGHYPAQ6STH7KMNDHAT36LHOLD","predicate":{"unconditional":true}}]}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/cb-retrieve-related-transactions.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/cb-retrieve-related-transactions.api.mdx
deleted file mode 100644
index be36bca423..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/cb-retrieve-related-transactions.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: cb-retrieve-related-transactions
-title: "Retrieve Related Transactions"
-description: "This endpoint represents successful transactions referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time."
-sidebar_label: "Retrieve Related Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ly27iWfhUUf3QnbcnaZclVqXslS/ISx7uT2GmXGiQPJUQkwACgFrtUdV9jXm+e5NYBKYla7NjJnWn39PBHHIlYvrMCOPrwYGnaU9buF2vPpyygtg+kSX3KHVDWXcZyQTmShZoJbu1aV32mCHA3FIxrIiGUoIBrRVTkOKCUF/lES8oVdbCHIhI8kMAdxnuEkh4bAifOfCI7nohQ7hKHcmIDiRS4hHGitAQaYLdAuLBNLpc+E+r7YqTIREREC+IzpYETT0jCYfQ4Ao3wN0yviO7DhFAJhLouuDim7gO51OD7VBIf3B7IbXLoEYf6/iaEGXIgJLsXnIyY7xOlqdSEajMMUOkzUJoMuBjxNDwScR+UIpQ4kVRCEqaIAp3B8Ud95vSJQxUQptOjelIERPepTjptk+YEe+lYRJiNNaR+BCgKF6OMURXqOIa9rCNHAtXgEsVQHRMRSSLhW4SQNQtg28pYIgRJsfWha+1ae80L0JLBEC7Ax65XqeGsjBVSSQPQINGzHixOA7B2rbnmu4nmu8y1MhZDzwqp7lsZC6dlElxrV8sIVt2vQSLOvkVAmAtcM4+BNEbfbFeErZw+BNTafbD0JEQMSkvGe9Z0mlnAMuqaAfkWgZwsIfGorzZA4VFgg4wNYeJBoa4pUSE4zGMO8YVjNIbGpMQRvg+x0YVHJKhQcAXK+D5TJIyMXyW2BRLSHuO9rhYD4IklhUcokeAI6W4UjXENPUBBYEyD0Adrt1rNV6uFnfJOrV6pF/KVtNhCuvByqV1QrMfpTA6EagZaeGyMUBHVF5HvEhqGQOU2OQ1jX2Pc8SMXyB9UOX+QN1Q5wF3Ge2+JkOQPnO4P8gb/JF+bqDMGprIXBcA1YYr/97/+SyeRookLHo38WP9m2Kcsn7GARwEmPKocKxbQuksrxmcB0y9UzFUfSEDHLIiCmWMYK8eqkKAjycHdJtjOjG9iUVLeg9jmBQRfzOdJllBOojAEmTQ0DsYU6VPpOsKNk88s2aD3hyA9IQOTyiRQJbh6QmkzA4K7prtC/rl+VcinFZaYtOtR5oP7Qs1dgjbpVsa5auYe8VhknnbQcTBqEOu6M5neGElmio1S2EL4QPnC/ibBmPZ30+ldxhpnVRSGQmqVnaf2WRqahysOWMzn8c+KGPECaGUsR3ANXGMTGoY+i5NA7qvCdg8pYNT3Tz2THxOIwv4KDnpeKFFuzeL5uj7jA5US5ZF2Cnzv+636ErxNUWFcSBv35wNrmrE0BKHJ7RuUOJ2m7folHvQuY2mmfUiNwWGsXxmkUMLwVUGaYrPZV8fG1Bhb3/EJCGzArcr3RUmSUKohlZJiZDINwTP8KoBAbFhBM39lx6SOIyL+2nwz3me+MlCLFPzKgIHngaNfG6pQggMuvDZY5oAG7muDlTqGvCpkK41MBltkjXmkLkXHwiNTXpDS/LK0d9OMxdxN4syQMNf4U+ogsDELL47em6TNWH2q+hs7rmWbxUZvrlHGdamIjZMjYpfqzSBEJB3orqfVuVQh1RokbpX2vzSyt/ls/e6hUpmm5KWuK3ELtUjP3SAawwYdrbboblLkGqquwjMtd2BjWw/+c/BTYz0mws+O+JjI2NDpU9l7RG8BHXc92KyCuS93V9XwlGcAH4IvQuiOXblx2HjX/r3XAWj6aBuU6skGuEfpxt9u8gNz4okkPGcX9F0DpbZrqYGT1C+4y565WGJpxRYRf05SDhjvYvtHbfrIyxTWVInmLA30agFjnhReAmstjSwDe/T1M6Adp8HgeIw/L5g3NezS3gsax7C7PRo+HQbRIg7GWtIueoQpez3Xz6bPUcQsBuwoCLsvWzM3Zv/FjOb9/1aIpL7uADSjIEwJjJ0Y5yD/wgI+lV9TXQ5RzCXRV/Ybpi66tPIvrfPJop7ahqSW57XF+PF1cHnVW148FqKsLwwrSX8pxa8n9HR2XrLD3XT6mPdb07vpvN5kLPN0yXn3wTJF0uV6yezgGW8crb7WodrN5fpx8SyrQWkOelvFZf5tIXu5tRq1yuWTp7BTqxWrnu1BqVSHgldxKqVyYcepeuB6UHTyFajZ4BTKpXypUC6BU67apVq9VrDzdafk1XPpmvs/4qrzu19Mke9d8RdTRX2HNclU3eQVAy+U89VyrVqp18qFWr5aKlU3izKrt/yVRTE1YvTUpbLLvLDy5Sd9Lo0p5zkVWq95TqlWrbteOV8D2y1Tp+AUoeSBB07NztNapQa1oucV3EIZStVidae6k6/Z9QLUVqobL4CR9FK5/dbe0eFBq1Qtlk73bk4OqpXr6/O90snxfrFVvdk72Wud3V4fXxzvHZ82dqpXzfOL42qjdNVZPlS8YOa4k8qVijvlnVKhtl52+LO0mVvAeEjcJWN8I2M8w+zWF4dNLBYvFyb+NNwJhueDTtctfhD1P+aB/8ujkbVai/i5qTAwn55rZS/x50Vlcty3fnqk1ZKAtUHw5apA/BtGvFH6T8w/i/FZuC5XB6xivpjPFgrZYumqUN3NF3dLtdv1Xcmu9cNp5omDfayMaq28U6pWKoVSsVBb2eX81LxLp2urkM+ntkmzz2un6MLqGdlq4NPDf1ptvzneqUu7f0O9Er3uHdsfg/xZsXnSPtmix0xdlhq56s3NxecyNt8/b9aqxfNF/3bj6WfxvmXaH+1d5S8OL8+XW42Pzh3I0WL50z6vF/3DvWLhVrfqvauLlhewsmzr0dlWsN/+uDXrUd87Xxm/0fab3xqF5uf79259UOfRmRDuMH/TfH+zddDrV6/vc9djcd/jw8n9CsjmXL52yysXJoNPW/CtdvgxPDo5dcqsRfu60gTm107C82bt04eDwen4U0kK57rZKbUP3n+7/tw6VK363v39zc5nWTiz7z8OKp3bMmu+P+mUP3xY3qEm+o/1uUCx+O9pCttntmfv5L6ewkFhfHX+eTzc8cqqCWxrdP2h1WnttOk9u9kf8dZW3P/dhg1w2uCHxhYN73R40vsJAzh872Pj4F7exgrcZPpW0Q3dwI9ui0fD2/1+eBzUJ7ejzW1jBRzcy/ubxecPl9cHB8Oijjr9MOeGlw2tP9nnuZt2/rxUEdH78bHTyoX9fsdLJDk4GvmrDrr61Dn9fBvagcvs4oWgl5WhEzhp5a887Vhf+IxeJb5mrVorLj6/MKAbjebEObpueKd6YD4ebprk7LboF+mnCr8J6gO6P4js0hFfC/5HMTb2VvS5/sz9MR6kU+4FW7nyPe/Xnet8p2ZvlbaOG5/FUHVajfH51nhflYOmOhrlDOqUTzWPzmnv5PxjbcK927Pbna/V9wd2fb9xGZz1y4fgf8gVPtAP5aOdmhot8J0P6u3L9mAZ04vt2zg7Tw9xvpD35QkOn3fvrNXSYyqSPzRr1er1ovWPWP59eWH5jZZ5nuVT6n9tmWXp9L9rccFXigC7X6zS1okTdob823CvQy+vrvjpYa8obDj/LEKvRa8bXudrs9JSH3W1etBpXLjj5uSb3xlNjhu5c1Urnhaq9atirXB7evEJDnuXXy+g1ULr3W2qyS5VXRd1VSuPpbi4JGGqEjDWwFXc7cuDNYCJtbuZJJKZ1R7MVvoOJdZ9gTuEHui4iIQ7r03n2odNnLjp0t4T1QVyOOPSRdJ/3gbW2sRRuorbkRPQIyEHhmmweUQvQvs8Z8zOrCXhs1HvsJTnxayBpLiTMJZQWSBV3Du/nd8umM1qEFA5WbQioRRD5hp6HDm4ujojjbNDpAe5VFNkAqXZmcms2+RQE8Z7oHTMqpOQNYoz7M64ZyiFGzngEnuyaYiYqYe13TnrCqhClqEWxBFcRQHMutIhSNoDkuL4EImVKTaEGX80xczKCsmAI8nSAJlTZxNyk6G92pM5oD0hAdliTBnJU3LYkrk9IDboEQDH6WNpl3ueSYHVUkV8NgAyQtKqVhniggNcS+qze3AJjJ0+MtBUxoxAlQKUWUUgDaI5y0wLoiLbkNFSjpkhhuKFJko21zPmZQa5fAnRFIaGIGxwLJFOkSw577m95ll/d0/4kjbo3ZtZeLoQnySkWjqsJrBzjpCQ5cKFt38r7/md/85n0yVEcmrOv+CSIaPEub44zhBKbClGCqSZQXCYMVjnur5svVff1bUrHJXTQvgqp9yBQk0LIgHdKaZfCyxaj5me4PiGTR3GCs2QERhSaBAAdw0lGxVFOU5MGFcaqIudAjpAMrfLJDja2BB558rIaczai5gLJI4YGxTpi5FRiRswjmR4SWYubtxxphucwvBE3xha/Mw7v7Tmkv5Kmr7oLXQwGo2WhZ+3zNq+6OVolsMoqyKexVWoD9lk/XhrqKlKYJhQZ9CTuOQSwVejIfYd6fSZBkdHkvqEBRjzEBjLi4THGtCvSGmPlw6Cv4O93SYdZMzz+Lc4/JraIkJKq4GICkzmm7uGcMGmCjLE6YMzINg6Lb8hyu6jahcK6DHdj+xtRwS5RA+5nsjZvrBzAUVN5zC8GC7mieg5/JlQcurHnrJ/fdhqdzunF91W+2P7+PSsfXG5HbhvjTGb4AkJ6BY29BhHSu6vioyE1EikZtqUEhJaPyYJZiCC0xcxD9igx6AlJ8L9kTRBXOEYgrDR4C757bcREBfvDGi86CGkAiIjzhHETI1o0DhJUbySwF3qYzClc8jc0377LU4PYGjx1PcnZmjTtzukPnONgN21lQ8wMCQQPRJEAV4o0Bha3AHJk5TjgiOi0E/0E2CSZgFuzijXxv1sYdToM2ozH+MRe6Wcb3spMDD2AsppDxRh6HojniEhleBmXby3MXM+4S2LKkLNApMScc6kJ6Y8TIjCIxxrneTNCH71fZKKO2Rn49WP3609GprFAof73ZrrDl3E1GploE69y9jNUlu1pWolNsoKL5t4Y0JEpo75FSAhas9gp929g4FpjG9lVraCyxs/CCgzb8H3xT/T77DszxzgClJzNULq9IEUt7EmtrivMX+Tjd8sZkySDTVv458F4kFV7vhwr31y2cYu230d+KaaGgqlA8pTU85+ICTJL4Rk5VbK0gbjYUHU/v9rTX/ba03JsVTDWOdCnzLDQjA++ZAc276sX1tCX9p95DLT0sntLmP1hdI4yMMDLjzX0p9O8ev4cgSe51ymcJRHrkekvfTPv3K0UVvxwXh+iSo5ClvmaPkS4f4yN4ue0MLsTtUPKuH/0C2iJ5Q0u1/1g0r6H7ow9ATgtftNC+R3+EEyhP7CaH5zkfB93pKXX2vcCHbGaeKTNMR5gG7KV4Zl0weKXrsocjUcB8K0hdbuMS0VufbbV9Z0+m9dzaBX
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/claimable_balances/{claimable_balance_id}/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful transactions referencing a given claimable balance and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this claimable balance as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"claimable_balance_id","in":"path","required":true,"description":"A unique identifier for this claimable balance.","schema":{"type":"string"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"CBRetrieveRelatedTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/transactions?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/transactions?cursor=140648659841806336&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000178826fbfe339e1f5c53417c6fedfe2c05e8bec14303143ec46b38981b09c3f9/transactions?cursor=140648659841806336&limit=2&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/32747318"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=140648659841806336"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=140648659841806336"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8"}},"id":"fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8","paging_token":"140648659841806336","successful":true,"hash":"fc5a98fc3869df408ebd4ac1c2e3fefec8b0a858e82ff1d14e362676708b91e8","ledger":32747318,"created_at":"2020-11-23T16:02:38Z","source_account":"GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","source_account_sequence":"140646847365513218","fee_account":"GDCJIHD3623OCYNH65UUQC3NLG2D6YCNCDPZULRLCLOA76TBQRL6A3TF","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAgAAAADElBx79rbhYaf3aUgLbVm0P2BNEN+aLisS3A/6YYRX4AAAAGQB862QAAAAAgAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAADgAAAAJCT0RISQAAAAAAAAAAAAAAxJQce/a24WGn92lIC21ZtD9gTRDfmi4rEtwP+mGEV+AAAAAAAA9CQAAAAAEAAAAAAAAAAElBqA1BXzKd9k9nuPoodv0YBKY+Hgh6Uz/UxozgnvyzAAAAAAAAAAAAAAABYYRX4AAAAEDf41ykW+eq8IVpJNOc4iDaht5Beil8NpQB8WMHkOxW3rocUBF3EHKqUXDIsD9CzzY7Xr1PbzVk5FZ4iBKNF4MM","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAOAAAAAAAAAAAXiCb7/jOeH1xTQXxv7f4sBei+wUMDFD7EaziYGwnD+QAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAfOvNgAAAAAAAAAAxJQce/a24WGn92lIC21ZtD9gTRDfmi4rEtwP+mGEV+AAAAAAAcnCVAHzrZAAAAABAAAAAAAAAAAAAAAAAAAAD2dpdmluZ2JvZGhpLm9yZwABAAAAAAAAAAAAAAAAAAAAAAAAAQHzrzYAAAAAAAAAAMSUHHv2tuFhp/dpSAttWbQ/YE0Q35ouKxLcD/phhFfgAAAAAAHJwlQB862QAAAAAgAAAAAAAAAAAAAAAAAAAA9naXZpbmdib2RoaS5vcmcAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAADAAAAAwHzrzYAAAAAAAAAAMSUHHv2tuFhp/dpSAttWbQ/YE0Q35ouKxLcD/phhFfgAAAAAAHJwlQB862QAAAAAgAAAAAAAAAAAAAAAAAAAA9naXZpbmdib2RoaS5vcmcAAQAAAAAAAAAAAAAAAAAAAAAAAAEB8682AAAAAAAAAADElBx79rbhYaf3aUgLbVm0P2BNEN+aLisS3A/6YYRX4AAAAAABycJUAfOtkAAAAAIAAAAAAAAAAAAAAAAAAAAPZ2l2aW5nYm9kaGkub3JnAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAACAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAfOvNgAAAAQAAAAAF4gm+/4znh9cU0F8b+3+LAXovsFDAxQ+xGs4mBsJw/kAAAABAAAAAAAAAABJQagNQV8ynfZPZ7j6KHb9GASmPh4IelM/1MaM4J78swAAAAAAAAACQk9ESEkAAAAAAAAAAAAAAMSUHHv2tuFhp/dpSAttWbQ/YE0Q35ouKxLcD/phhFfgAAAAAAAPQkAAAAAAAAAAAQAAAAEAAAAAxJQce/a24WGn92lIC21ZtD9gTRDfmi4rEtwP+mGEV+AAAAAAAAAAAA==","fee_meta_xdr":"AAAAAgAAAAMB866UAAAAAAAAAADElBx79rbhYaf3aUgLbVm0P2BNEN+aLisS3A/6YYRX4AAAAAABycK4AfOtkAAAAAEAAAAAAAAAAAAAAAAAAAAPZ2l2aW5nYm9kaGkub3JnAAEAAAAAAAAAAAAAAAAAAAAAAAABAfOvNgAAAAAAAAAAxJQce/a24WGn92lIC21ZtD9gTRDfmi4rEtwP+mGEV+AAAAAAAcnCVAHzrZAAAAABAAAAAAAAAAAAAAAAAAAAD2dpdmluZ2JvZGhpLm9yZwABAAAAAAAAAAAAAAAAAAAA","memo_type":"none","signatures":["3+NcpFvnqvCFaSTTnOIg2obeQXopfDaUAfFjB5DsVt66HFARdxByqlFwyLA/Qs82O169T281ZORWeIgSjReDDA=="],"preconditions":{"timebounds":{"min_time":"0"}}}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/README.mdx
deleted file mode 100644
index d1dcfbfb47..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Errores
-sidebar_position: 40
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Después de procesar una solicitud, Horizon devuelve una respuesta de éxito o de error al cliente. Una respuesta de éxito devolverá un código de estado de 200, y una respuesta de error devolverá un código de estado en el rango de 4XX - 5XX junto con información adicional sobre por qué la solicitud no pudo completarse con éxito.
-
-Hay dos categorías de errores: [Códigos de Estado HTTP](./http-status-codes/README.mdx) y [Códigos de Resultado](./result-codes/README.mdx). Los Códigos de Resultado solo siguen un Código de Estado HTTP de Transacción Fallida (400).
-
-<MethodTable title="Categorías de Error">
-
-|                                                          |                                                   |
-| -------------------------------------------------------- | ------------------------------------------------- |
-| [Códigos de Estado HTTP](./http-status-codes/README.mdx) | Errores que ocurren a nivel del Servidor Horizon. |
-| [Códigos de Resultado](./result-codes/README.mdx)        | Errores que ocurren a nivel del Stellar Core.     |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/error-handling.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/error-handling.mdx
deleted file mode 100644
index d4f41bddfb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/error-handling.mdx
+++ /dev/null
@@ -1,230 +0,0 @@
----
-title: Manejo de Errores
----
-
-Es importante anticipar errores que tus usuarios pueden encontrar mientras desarrollas en Stellar. En muchos tutoriales a lo largo de nuestra documentación para desarrolladores, omitimos el código de manejo de errores para centrarnos en el ejemplo. En esta sección, haremos lo contrario y hablaremos específicamente sobre los errores. Al final de esta sección, deberías ser capaz de categorizar errores y entender la mejor manera de manejarlos en tu aplicación.
-
-Muchísimas acciones interactúan con la red Stellar a través de la API de Horizon, y estas acciones posibles se dividen en dos categorías principales:
-
-1. Consultas (cualquier solicitud `GET`, como a `/accounts`)
-2. Presentaciones de transacciones (una `POST /transactions`, `POST /transactions_async`).
-
-Existen muchos códigos de error posibles al ejecutar estas acciones, y generalmente puedes manejar estos códigos de error utilizando las siguientes estrategias:
-
-- Ajustes en la solicitud: ajustando la solicitud para resolver errores estructurales con consultas o presentaciones de transacciones. Supongamos que has incluido un parámetro incorrecto, malformado tu XDR, o de otra manera no seguiste la especificación del endpoint. En estos casos, resuelve el error consultando los detalles o códigos de resultado de la respuesta de error.
-- Polling y reintentos: esta es la manera recomendada para sortear problemas de latencia o congestión encontrados a lo largo del canal entre tu ordenador y la red Stellar, que a veces puede ocurrir debido a la naturaleza de los sistemas distribuidos.
-
-## Manejo de Errores para Consultas
-
-Muchas solicitudes `GET` tienen requisitos específicos de parámetros, y mientras que los SDK pueden ayudar a hacer cumplir estos requisitos, aún puedes pasar argumentos inválidos (por ejemplo, una cadena de activo que no es compatible con [SEP-11](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md#asset-trustlineasset)) que generen errores cada vez. En este escenario, no hay nada que puedas hacer, salvo seguir la especificación de la API. El campo `extras` de la respuesta de error a menudo te indicará dónde mirar y qué buscar.
-
-<CodeExample>
-
-```bash
-curl -s https://horizon-testnet.stellar.org/claimable_balances/0000 | jq '.extras'
-{
-    "invalid_field": "id",
-    "reason": "Invalid claimable balance ID"
-}
-```
-
-</CodeExample>
-
-Nota que los SDK hacen hincapié en distinguir una solicitud inválida (como se ha mencionado anteriormente) de un recurso faltante (un `404 Not Found`) (por ejemplo, el genérico `NetworkError` frente a un `NotFoundError` en el SDK de JavaScript), donde este último podría no ser considerado un error dependiendo de tu situación.
-
-## Manejo de Errores para Presentaciones de Transacciones
-
-Horizon actualmente admite dos tipos de endpoints para la presentación de transacciones:
-
-1. `/transactions_async`: Horizon presenta una transacción a Stellar-Core de forma asíncrona y pasa la respuesta relevante de Stellar-Core de inmediato al cliente. Luego, es responsabilidad del cliente hacer polling para verificar el estado de esa transacción.
-2. `/transactions`: Horizon presenta una transacción a Stellar-Core y luego espera a que sea ingresada en su base de datos. Devolverá ya sea un éxito (200), fallo (400) o un timeout (504), después de lo cual es responsabilidad del cliente hacer polling para verificar el estado de la transacción.
-
-Nota que hacer polling del hash de la transacción devolverá un 404 hasta que sea incluido en el ledger, o hasta que falle en hacerlo. En ambos casos, recibirás una respuesta cuando Horizon la haya ingresado en la base de datos.
-
-Existen algunas estrategias de resolución que son comunes entre los 2 endpoints mientras que otras son más específicas de cada endpoint.
-
-### Ajustes en la Solicitud
-
-Ciertos errores en presentaciones de transacciones también requieren ajustes para tener éxito.
-
-- Si el XDR está malformado, o si la transacción es de otro modo inválida, encontrarás un `400 Bad Request` (por ejemplo, una cuenta fuente inválida). Tanto las transacciones como sus operaciones pueden estar fácilmente malformadas o ser inválidas: consulta el campo `extras.result_codes` para obtener detalles y contrástalos con la documentación de códigos de resultados correspondiente para determinar especificaciones.
-- Las tarifas de transacción también se pueden ajustar de manera segura modificando las tarifas a través de una [transacción fee-bump](../../../../../build/guides/transactions/fee-bump-transactions.mdx) si recibes un error `tx_insufficient_fee`. Consulta la sección [Costos Insuficientes y Precios Altos](#insufficient-fees-and-surge-pricing) más adelante en este documento para obtener más información sobre la gestión de costos y estrategias al respecto.
-
-### Polling y Reintento de Transacciones
-
-#### Presentación de Transacciones Asíncronas
-
-Las presentaciones usando el endpoint `/transactions_async` devuelven una respuesta inmediata de Stellar-Core. Existen diferentes acciones que los clientes pueden tomar según el `tx_status` específico devuelto:
-
-1. `PENDING`: La presentación es exitosa pero la transacción aún está esperando ser incluida en un ledger. Deberías usar el endpoint [GET /transactions/:transaction_hash](../retrieve-a-transaction.api.mdx) para hacer polling de la transacción presentada y verificar si se incluye en el ledger. Nota que aunque la presentación fue exitosa, aún puede fallar en ser incluida en el ledger.
-2. `DUPLICATE`: La presentación fue un duplicado de una transacción previamente presentada. Esto podría suceder si el cliente presentó la misma transacción múltiples veces.
-3. `ERROR`: La presentación no se completó debido a un error en Stellar-Core. Consulta el mensaje de error adjunto para más detalles, modifica tu transacción si es necesario y vuelve a presentar.
-4. `TRY_AGAIN_LATER`: Esto indica que la instancia de Stellar-Core actualmente no puede procesar la presentación de esta transacción particular. Los clientes deberían esperar un tiempo antes de volver a presentar la transacción. Esto podría suceder por diferentes razones:
-   - Hay otra transacción del mismo cuenta fuente en memoria
-   - Ha sido rechazada debido a una tarifa de inclusión demasiado baja y se ha vuelto a enviar demasiado pronto
-
-<CodeExample>
-
-```js
-let server = sdk.Server("https://horizon-testnet.stellar.org");
-let contractId = "CA3D5KRYM6CB7OWQ6TWYRR3Z4T7GNZLKERYNZGGA5SOAOPIFY6YQGAXE";
-let contract = new StellarSdk.Contract(contractId);
-
-// Right now, this is just the default fee for this example.
-const fee = StellarSdk.BASE_FEE;
-
-let transaction = new StellarSdk.TransactionBuilder(account, { fee })
-  .setNetworkPassphrase(StellarSdk.Networks.TESTNET)
-  .setTimeout(30) // valid for the next 30s
-  // Add an operation to call increment() on the contract
-  .addOperation(contract.call("increment"))
-  .build();
-
-// Sign this transaction with the secret key
-// NOTE: signing is transaction is network specific. Test network transactions
-// won't work in the public network. To switch networks, use the Network object
-// as explained above (look for StellarSdk.Network).
-let sourceKeypair = StellarSdk.Keypair.fromSecret(sourceSecretKey);
-transaction.sign(sourceKeypair);
-
-server.submitAsyncTransaction(transaction).then((result) => {
-  console.log("hash:", result.hash);
-  console.log("status:", result.tx_status);
-  console.log("errorResultXdr:", result.error_result_xdr);
-});
-
-// Add a small sleep duration before polling the transaction.
-time.sleep(5 * time.Second);
-server
-  .transactions()
-  .transaction(result.hash)
-  .call()
-  .then((txResult) => {
-    console.log("Transaction status:", txResult);
-  });
-```
-
-</CodeExample>
-
-#### Presentación de Transacciones Sincrónicas
-
-Debido a la naturaleza bloqueante de este endpoint, las cosas son un poco diferentes en comparación con la estrategia asíncrona. Existen 3 escenarios posibles que los clientes pueden encontrar:
-
-1. La presentación es exitosa y Horizon devuelve la respuesta de la transacción. Este es el camino feliz y los clientes no necesitan hacer nada más que esperar la respuesta de Horizon.
-2. Stellar-Core envía de vuelta una respuesta `ERROR` desde la presentación. Los clientes deberían consultar el mensaje de error adjunto e intentar la presentación nuevamente.
-3. Timeouts: Horizon puede responder con un código HTTP `504`. Esta respuesta no es un error, sino una advertencia de que tu transacción aún no ha sido aceptada por la red. Pueden existir muchas razones posibles para el timeout, la más común es la congestión de la red, pero también podría deberse a otros problemas transitorios.
-   1. **Haciendo polling del hash de la transacción**: Usa el hash de la transacción en la respuesta de timeout y haz polling al endpoint [GET /transactions/:transaction_hash](../retrieve-a-transaction.api.mdx) para ver si se incluyó exitosamente en el ledger.
-   2. **Reenviando la transacción**: Antes de intentar cualquier reenvío, necesitas asegurarte de que tu transacción ha caducado según los límites de tiempo que especificaste. Después de que tu transacción haya caducado, puedes confirmarlo haciendo polling de la transacción nuevamente y obteniendo una respuesta `tx_too_late` de Horizon. Reconstruye la transacción actualizando los límites de tiempo y reenvía la transacción.
-
-:::caution
-
-Ten en cuenta que reenviar una transacción solo es seguro cuando no ha cambiado: mismas operaciones, firmas, número de secuencia, etc... Ten cuidado al sortear un error que requiere cambios en la transacción. Puede provocar transacciones duplicadas, lo que puede causar problemas: pagos duplicados, líneas de confianza incorrectas, y más. Si continúas enfrentando timeouts en los reintentos, considera usar una transacción de fee-bump para ingresar al ledger (después de que el tiempo de la transacción inicial expire) o aumentar la tarifa máxima que estás dispuesto a pagar. Lee sobre [Precios Altos y Estrategias de Costos](../../../../../learn/fundamentals/fees-resource-limits-metering.mdx) para más detalles.
-
-:::
-
-### Ejemplo: Uso de Límites de Tiempo
-
-Los límites de tiempo son opcionales pero **altamente** recomendados, ya que establecen un límite de tiempo definitivo sobre la finalización de la transacción - después de que expire, sabrás con seguridad si se incluyó en el ledger. Por ejemplo, envías una transacción, y entra en la cola de la red Stellar, pero Horizon se bloquea mientras te da una respuesta. Incierto sobre el estado de la transacción, vuelves a enviar la transacción (sin cambios!) hasta que (a) Horizon vuelva a estar operativo para darte una respuesta o (b) tus límites de tiempo se superen.
-
-Solo hay dos resultados posibles para este escenario: bien la transacción se incluye en el ledger (exactamente una vez) y Horizon te da la respuesta, o la transacción nunca sale de la cola, y recibes la correspondiente respuesta `tx_too_late`.
-
-Ejemplo de implementación:
-
-<CodeExample>
-
-```js
-import { Horizon } from "@stellar/stellar-sdk";
-
-let server = Horizon.Server("https://horizon-testnet.stellar.org");
-
-function submitTransaction(tx, timeout) {
-  if (!tx.timeBounds || tx.timeBounds.maxTime === 0) {
-    throw new Error("Always set a reasonable timebound!");
-  }
-  const expiration = parseInt(tx.timeBounds.maxTime);
-
-  return server.submitTransaction(tx).catch(function (error) {
-    if (isNonRetryErrorCase(error)) {
-      // ...do other error handling...
-      return;
-    }
-
-    // the tx no longer has a chance of making it into a ledger
-    if (Date.now() >= expiration) {
-      return new Error("The transaction timed out.");
-    }
-
-    timeout = timeout || 1; // start the (linear) back-off process
-    return sleep(timeout).then(function () {
-      return submitTransaction(tx, timeout + 5);
-    });
-  });
-}
-```
-
-</CodeExample>
-
-Asumimos la existencia de una implementación de espera similar a la de [aquí](https://stackoverflow.com/a/39914235). Asegúrate de integrar backoff en tu mecanismo de reintento. En nuestro código de manejo de errores de ejemplo anterior, implementamos un simple backoff lineal, pero hay [muchas recomendaciones](https://backoff-utils.readthedocs.io/en/latest/strategies.html#why-are-backoff-strategies-useful) para varias otras estrategias. El backoff es importante tanto para mantener el rendimiento como para evitar problemas de limitación de frecuencia.
-
-### Ejemplo: Números de Secuencia Inválidos
-
-Estos errores ocurren típicamente cuando tienes una vista desactualizada de una cuenta. Esto podría deberse a que múltiples dispositivos están usando esta cuenta, tienes envíos concurrentes ocurriendo, o otras razones. La solución es relativamente simple: recupera los detalles de la cuenta e intenta nuevamente con un número de secuencia actualizado.
-
-<CodeExample>
-
-```js
-// suppose `account` is an outdated `AccountResponse` object
-let tx = sdk.TransactionBuilder(account, ...)/* etc */.build();
-server.submitTransaction(tx).catch(function (error) {
-  if (error.response && error.status == 400 && error.extras &&
-      error.extras.result_codes.transaction == sdk.TX_BAD_SEQ) {
-    return server.loadAccount(account.accountId())
-      .then(function (response) {
-        let tx = sdk.TransactionBuilder(response, ...)/* etc */.build()
-        return server.submitTransaction(tx);
-      });
-  }
-  // ...other error conditions...
-})
-```
-
-</CodeExample>
-
-A pesar de la simplicidad de la solución, las cosas pueden salir mal rápido si no entiendes por qué ocurrió el error.
-
-Supongamos que envías transacciones desde múltiples lugares en tu aplicación simultáneamente, y tu usuario presiona rápidamente un botón _Enviar Pago_ varias veces por impaciencia. Si envías la misma transacción de pago exacta para cada pulsación, naturalmente, solo una tendrá éxito. Las otras fallarán con un número de secuencia inválido (`tx_bad_seq`), y si vuelves a enviar sin pensar con un número de secuencia actualizado (como hacemos anteriormente), estos pagos también tendrán éxito, resultando en más de un pago cuando solo se pretendía uno. Así que **ten mucho cuidado al reenviar transacciones** que han sido modificadas para sortear un error.
-
-## Manejando Errores Específicos
-
-Aquí, cubriremos errores específicos comúnmente encontrados durante la presentación de transacciones y te indicaremos la resolución adecuada.
-
-| Resultado               | Código | Descripción                                                                                                                                                                             |
-| ----------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `FAILED`                | \-1    | Una de las operaciones falló (consulta la [Lista de Operaciones](../../../../../learn/fundamentals/transactions/list-of-operations.mdx) para errores)                                   |
-| `TOO_EARLY`             | \-2    | `closeTime` del ledger antes del valor `minTime` en la transacción                                                                                                                      |
-| `TOO_LATE`              | \-3    | `closeTime` del ledger después del valor `maxTime` en la transacción                                                                                                                    |
-| `MISSING_OPERATION`     | \-4    | No se especificó ninguna operación                                                                                                                                                      |
-| `BAD_SEQ`               | \-5    | El número de secuencia no coincide con la cuenta fuente                                                                                                                                 |
-| `BAD_AUTH`              | \-6    | Muy pocas firmas válidas / red incorrecta                                                                                                                                               |
-| `INSUFFICIENT_BALANCE`  | \-7    | La tarifa reduciría la cuenta por debajo del balance mínimo; consulta nuestra sección sobre [Lumens](../../../../../learn/fundamentals/lumens.mdx#minimum-balance) para más información |
-| `NO_ACCOUNT`            | \-8    | Cuenta fuente no encontrada                                                                                                                                                             |
-| `INSUFFICIENT_FEE`      | \-9    | La tarifa es demasiado pequeña; consulta nuestra sección sobre [Costos](../../../../../learn/fundamentals/fees-resource-limits-metering.mdx) para más información                       |
-| `BAD_AUTH_EXTRA`        | \-10   | Firmas no utilizadas añadidas a la transacción                                                                                                                                          |
-| `INTERNAL_ERROR`        | \-11   | Ocurrió un error desconocido                                                                                                                                                            |
-| `NOT_SUPPORTED`         | \-12   | El tipo de transacción no está soportado                                                                                                                                                |
-| `FEE_BUMP_INNER_FAILED` | \-13   | La transacción interna de una transacción de fee-bump falló                                                                                                                             |
-| `BAD_SPONSORSHIP`       | \-14   | La patrocinación no está confirmada                                                                                                                                                     |
-
-### Costos insuficientes y precios altos
-
-Consulta la sección [Costos](../../../../../learn/fundamentals/fees-resource-limits-metering.mdx)
-
-### Limitación de frecuencia
-
-Horizon puede limitar la frecuencia de las solicitudes y devolver un error `429 Too Many Requests` al exceder los límites de frecuencia. Si utilizas tu propia instancia, puedes querer aumentar o desactivar la limitación de frecuencia. Si estás utilizando una instancia de Horizon de terceros, puedes querer desplegar la tuya para tener más control sobre esta configuración o enviar solicitudes con menos frecuencia.
-
-### Saldo XLM insuficiente
-
-Cualquier transacción que reduzca el saldo de una cuenta a menos del mínimo será rechazada con un error `INSUFFICIENT_BALANCE`. Del mismo modo, las obligaciones de venta de lumen que reducirían el saldo de una cuenta a menos del mínimo más las obligaciones de venta de lumen serán rechazadas con un error `INSUFFICIENT_BALANCE`.
-
-Para más información sobre balances mínimos, consulta nuestra sección sobre [Lumens](../../../../../learn/fundamentals/lumens.mdx#minimum-balance).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/README.mdx
deleted file mode 100644
index 3ad53460c6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/README.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Códigos de Estado HTTP
-order: 30
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Algunos errores solo ocurren a nivel de Horizon y no se lanzan en Stellar Core. Estos suelen ser incidencias con la forma en que se formó la transacción o un conflicto entre la composición de la transacción y cómo está configurado el servidor de Horizon.
-
-Stellar utiliza códigos de respuesta HTTP convencionales para indicar el éxito o fracaso de una solicitud de API. En general:
-
-- Los códigos en el rango 2xx indican éxito.
-- Los códigos en el rango 4xx indican un error que falló dada la información proporcionada
-- Los códigos en el rango 5xx indican un error con el servidor de Horizon.
-
-Hay dos tipos de Códigos de Estado: [Códigos de Estado Estándar](./standard.mdx) y [Códigos de Estado Específicos de Horizon](./horizon-specific/README.mdx).
-
-<MethodTable title="Tipos de Código de Estado HTTP">
-
-|                                                                           |                                    |
-| ------------------------------------------------------------------------- | ---------------------------------- |
-| [Códigos de Estado Estándar](./standard.mdx)                              | Respuestas HTTP genéricas.         |
-| [Códigos de Estado Específicos de Horizon](./horizon-specific/README.mdx) | Errores que son únicos de Horizon. |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/README.mdx
deleted file mode 100644
index d67935ec70..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/README.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Códigos de Estado Específicos de Horizon
-sidebar_position: 20
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Estas respuestas son específicas de cómo está configurado un servidor Horizon y cómo deben formarse las transacciones.
-
-<MethodTable title="Códigos de Estado Específicos de Horizon">
-
-|                                                               |   |
-| ------------------------------------------------------------- | - |
-| [Transacción Fallida](./transaction-failed.mdx)               |   |
-| [Transacción Malformada](./transaction-malformed.mdx)         |   |
-| [Antes del Historial](./before-history.mdx)                   |   |
-| [Historial Obsoleto](./stale-history.mdx)                     |   |
-| [Tiempo de Espera](./timeout.mdx)                             |   |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx
deleted file mode 100644
index f7fe6d8eec..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/before-history.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Antes de la historia
-sidebar_position: 30
----
-
-Un servidor Horizon puede configurarse para conservar solo una parte del historial de la red estelar almacenado en su base de datos.
-
-El error `before_history` devuelve un [código de error `410`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410) y ocurre cuando un cliente solicita una pieza de información (como una página de transacciones o una sola operación) que el servidor puede identificar positivamente como fuera del rango de historial grabado.
-
-<ExampleResponse title="Respuesta de ejemplo para un código de estado 'Antes de la Historia'">
-
-```json
-{
-  "type": "https://stellar.org/horizon-errors/before_history",
-  "title": "Data Requested Is Before Recorded History",
-  "status": 410,
-  "detail": "This horizon instance is configured to only track a portion of the stellar network's latest history. This request is asking for results prior to the recorded history known to this horizon instance."
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.mdx
deleted file mode 100644
index a8d012ec7a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/stale-history.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Historia Obsoleta
-sidebar_position: 40
----
-
-Un servidor Horizon puede estar configurado para rechazar solicitudes históricas cuando se sabe que la historia está más desactualizada que el umbral configurado.
-
-En tales casos, ocurre el error `stale_history` y devuelve un [código de error `503`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/503). Para resolver este error (si eres el operador de la instancia de Horizon), asegúrate de que el sistema de ingestión esté funcionando correctamente e importando nuevos ledgers.
-
-<ExampleResponse title="Ejemplo de Respuesta para un Código de Estado 'Historia Obsoleta'">
-
-```json
-{
-  "type": "https://stellar.org/horizon-errors/stale_history",
-  "title": "Historical DB Is Too Stale",
-  "status": 503,
-  "detail": "This horizon instance is configured to reject client requests when it can determine that the history database is lagging too far behind the connected instance of stellar-core.  If you operate this server, please ensure that the ingestion system is properly running."
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.mdx
deleted file mode 100644
index eb6415309b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/timeout.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Tiempo de espera
-sidebar_position: 50
----
-
-El error `timeout` devuelve un [código de error `504`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/504) y ocurre cuando:
-
-- Horizon no ha recibido una confirmación del servidor Stellar Core de que la transacción que estás intentando enviar a la red fue incluida en un ledger de manera oportuna, o
-- Horizon no ha enviado una respuesta a un proxy inverso antes de que transcurriera un tiempo especificado.
-
-El primer caso puede ocurrir porque no hubo espacio para tu transacción durante 3 ledgers consecutivos. Esto se debe a que Stellar Core elimina cada transacción enviada de una cola. Para resolver esto puedes:
-
-- Seguir reenvíando la misma transacción (con el mismo número de secuencia) y esperar hasta que finalmente se agregue a un nuevo ledger, o
-- Aumentar la tarifa para priorizar la transacción.
-
-<ExampleResponse title="Ejemplo de Respuesta para un Código de Estado 'Timeout'">
-
-```json
-{
-  "type": "https://stellar.org/horizon-errors/timeout",
-  "title": "Timeout",
-  "status": 504,
-  "detail": "Your request timed out before completing.  Please try your request again. If you are submitting a transaction make sure you are sending exactly the same transaction (with the same sequence number)."
-}
-```
-
-</ExampleResponse>
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
deleted file mode 100644
index 60b788f28d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Transacción fallida
-sidebar_position: 10
----
-
-El error `transaction_failed` devuelve un [código de error `400`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400) y ocurre cuando un cliente envía una transacción que estaba bien formada pero no fue incluida en el ledger debido a otra falla.
-
-Por ejemplo, una transacción puede fallar si:
-
-1. La cuenta fuente de la transacción no puede pagar la tarifa mínima.
-2. El número de secuencia es incorrecto.
-3. Una de las operaciones contenidas ha fallado, como una operación de pago que sobrepasa el saldo de la cuenta que paga.
-
-En casi todos los casos, este error indica que la transacción enviada en la solicitud inicial nunca tendrá éxito. Hay una excepción: una transacción que falla con el código de resultado `tx_bad_seq` (como se expresa en el campo `result_code` del error) puede volverse válida en el futuro si el número de secuencia que utilizó fue demasiado alto.
-
-<ExampleResponse title="Ejemplo de respuesta para un código de estado 'Transacción fallida'">
-
-```json
-{
-  "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",
-  "extras": {
-    "envelope_xdr": "AAAAAgAAAADdfhHDs4Vaug6p8Oxb1QRjNRdJt3pYKKBVhFHrEgd9QAAAAAoAEi4YAAAAAwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACwAAAAAAAAAAAAAAAAAAAAESB31AAAAAQFhc/liVXbLk3NtB2BtweFJ064JdDIfrTSrqKMhb1oIRK+0PSyvjzZTkRCJmQY3bHNXYNuepa2TF7aBdibrb1gI=",
-    "result_codes": {
-      "transaction": "tx_insufficient_fee"
-    },
-    "result_xdr": "AAAAAAAAAAr////3AAAAAA=="
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.mdx
deleted file mode 100644
index abf8f008e5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-malformed.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Transacción Malformada
-sidebar_position: 20
----
-
-El error `transaction_malformed` devuelve un [código de error `400`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400) y ocurre cuando un cliente envía una transacción malformada.
-
-Hay muchas maneras en las que una transacción podría estar malformada, incluyendo:
-
-1. Enviaste una cadena vacía.
-2. Tu cadena codificada en base64 no es válida.
-3. Tu estructura [XDR](../../../structure/xdr.mdx) no es válida.
-4. Tienes bytes sobrantes en tu estructura [XDR](../../../structure/xdr.mdx).
-
-<ExampleResponse title="Ejemplo de Respuesta para un Código de Estado 'Transacción Malformada'">
-
-```json
-{
-  "type": "https://stellar.org/horizon-errors/transaction_malformed",
-  "title": "Transaction Malformed",
-  "status": 400,
-  "detail": "Horizon could not decode the transaction envelope in this request. A transaction should be an XDR TransactionEnvelope struct encoded using base64.  The envelope read from this request is echoed in the `extras.envelope_xdr` field of this response for your convenience.",
-  "extras": {
-    "envelope_xdr": "BBBBBPORy3CoX6ox2ilbeiVjBA5WlpCSZRcjZ7VE9Wf4QVk7AAAAZAAAQz0AAAACAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAA85HLcKhfqjHaKVt6JWMEDlaWkJJlFyNntUT1Z/hBWTsAAAAAAAAAAAL68IAAAAAAAAAAARN17BEAAABAA9Ad7OKc7y60NT/JuobaHOfmuq8KbZqcV6G/es94u9yT84fi0aI7tJsFMOyy8cZ4meY3Nn908OU+KfRWV40UCw=="
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/standard.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/standard.mdx
deleted file mode 100644
index b1fc8edd45..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/standard.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Códigos de Estado Estándar
-sidebar_position: 10
----
-
-Estas respuestas son códigos de protocolo de Internet que describen problemas básicos con una transacción enviada.
-
-<AttributeTable>
-
-- CÓDIGO DE ESTADO
-  - VALOR
-  - DESCRIPCIÓN
-- Aceptar
-  - 200
-  - La solicitud ha tenido éxito.
-- Solicitud Incorrecta
-  - 400
-  - La solicitud es inválida de alguna manera.
-- No Encontrado
-  - 404
-  - El recurso solicitado no existe.
-- No Implementado
-  - 404
-  - La solicitud no tiene un tipo de contenido de respuesta aceptable.
-- No Aceptable
-  - 406
-  - La solicitud no tiene un tipo de contenido de respuesta aceptable.
-- Error Interno del Servidor
-  - 500
-  - Algo salió mal en el servidor de Horizon.
-
-</AttributeTable>
-
-<ExampleResponse title="Respuesta de Ejemplo para un Código de Estado de Solicitud Incorrecta">
-
-```json
-{
-  "type": "https://stellar.org/horizon-errors/bad_request",
-  "title": "Bad Request",
-  "status": 400,
-  "detail": "The request you sent was invalid in some way",
-  "extras": {
-    "invalid_field": "limit",
-    "reason": "unparseable value"
-  }
-}
-```
-
-</ExampleResponse>
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
deleted file mode 100644
index e03543eea9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/response.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Respuesta de error
-sidebar_position: 10
----
-
-Cuando ocurre un error, Horizon responde con un documento JSON que contiene los atributos a continuación.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- tipo
-  - URL
-  - El tipo de código de estado devuelto.
-- título
-  - cadena
-  - Un breve título que describe el código de estado, que se puede usar para buscar más información sobre un error.
-- estado
-  - número
-  - Un breve título que describe el código de estado, que se puede usar para buscar más información sobre un error.
-- detalle
-  - cadena
-  - Un breve título que describe el código de estado, que se puede usar para buscar más información sobre un error.
-- extras
-  - mapa
-  - Si el código de estado es `Transacción fallida`, este campo de extras muestra el código de resultado devuelto por Stellar Core que describe por qué falló la transacción.
-    - envelope_xdr
-      - cadena
-      - Una representación codificada en base64 del TransactionEnvelope XDR cuya falla provocó esta respuesta.
-    - result_xdr
-      - cadena
-      - Una representación codificada en base64 del TransactionResult XDR devuelto por stellar-core al enviar esta transacción.
-    - result_codes.transaction
-      - cadena
-      - El código de resultado de la transacción devuelto por Stellar Core, que se puede usar para buscar más información sobre un error en la documentación.
-    - result_codes.operations
-      - array
-      - Un array de códigos de resultado de la operación devueltos por Stellar Core, que se pueden usar para buscar más información sobre un error en la documentación.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "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",
-  "extras": {
-    "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAADAAAAAAAAAAAAAAABAAAAAQAAAACuSL9OciKkFztj4d3zuadl20HHObu+7qJenBxHPrMayQAAAAUAAAABAAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtJBKRwAAABA1N0iqDAgqS6+3RIZGoNB9OXrY3wd/nLruXYi+eiTt4jn94fLVLwAw6jJCaK+qxStwO7c4kP6u5k0RPbuYC55CT6zGskAAABAiUGCNCS4pGlfcRmi82kbralzcFlTQAFzLyfUrYGn3RtQ4p/7TUwAqIanVoWGfEqzIJo64ZT+mYtJ72BfI+FiDg==",
-    "result_codes": {
-      "transaction": "tx_failed",
-      "operations": ["op_no_source_account"]
-    },
-    "result_xdr": "AAAAAAAAAGT/////AAAAAf////4AAAAA"
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/README.mdx
deleted file mode 100644
index f59fce750b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/README.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Códigos de Resultado
-order: 40
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Los Códigos de Resultado describen por qué una transacción u operación falló en Stellar Core y se comunican en el campo “extras” de una respuesta de Horizon cuando se devuelve el Código de Estado “Transacción Fallida”.
-
-En el campo “extras”, los errores devueltos se denominan “Códigos de Resultado” y son la abstracción de Horizon de los “Códigos del Protocolo Stellar”, que son códigos más específicos disponibles en el XDR. Los Códigos de Resultado son la forma en que Horizon normaliza los Códigos del Protocolo Stellar.
-
-Hay tres tipos de Códigos de Resultado: [Códigos de Resultado de Transacción](./transactions.mdx), [Códigos de Resultado de Operación](./operations.mdx) y [Códigos de Resultado Específicos de Operación](./operation-specific/README.mdx).
-
-<MethodTable title="Tipos de Códigos de Resultado">
-
-|                                                                                  |                                                |
-| -------------------------------------------------------------------------------- | ---------------------------------------------- |
-| [Códigos de Resultado de Transacción](./transactions.mdx)                        | Errores genéricos sobre fallos de transacción. |
-| [Códigos de Resultado de Operación](./operations.mdx)                            | Errores genéricos sobre fallos de operación.   |
-| [Códigos de Resultado Específicos de Operación](./operation-specific/README.mdx) | Errores específicos de cada tipo de operación. |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/README.mdx
deleted file mode 100644
index 431b9ef07e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/README.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Códigos de Resultado Específicos de la Operación
-order: 30
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Estos son Códigos de Resultado que comunican respuestas de éxito (200) o fracaso (400) que son específicos para cada tipo de operación.
-
-Cada una de las operaciones de Stellar tiene causas únicas de fracaso, y estos códigos de resultado te ayudarán a diagnosticar y abordar los orígenes de las incidencias.
-
-<MethodTable title="Tipos de Códigos de Resultado Específicos de la Operación">
-
-|                                                                              |   |
-| ---------------------------------------------------------------------------- | - |
-| [Crear Cuenta](./create-account.mdx)                                         |   |
-| [Pago](./payment.mdx)                                                        |   |
-| [Recepción de Pago Estricto por Rutas](./path-payment-strict-receive.mdx)    |   |
-| [Envío de Pago Estricto por Rutas](./path-payment-strict-send.mdx)           |   |
-| [Administrar Oferta de Venta](./manage-sell-offer.mdx)                       |   |
-| [Administrar Oferta de Compra](./manage-buy-offer.mdx)                       |   |
-| [Crear Oferta de Venta Pasiva](./create-passive-sell-offer.mdx)              |   |
-| [Configurar Opciones](./set-options.mdx)                                     |   |
-| [Cambiar Confianza](./change-trust.mdx)                                      |   |
-| [Permitir Confianza](./allow-trust.mdx)                                      |   |
-| [Fusión de Cuentas](./account-merge.mdx)                                     |   |
-| [Administrar Datos](./manage-data.mdx)                                       |   |
-| [Aumentar Secuencia](./bump-sequence.mdx)                                    |   |
-
-</MethodTable>
-
-Para las operaciones que no están en esta lista, generalmente puedes referirte a sus entradas correspondientes en la [Lista de Operaciones](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx) que enumerará los casos de fracaso y los códigos de resultado correspondientes.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.mdx
deleted file mode 100644
index 495ed62fab..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/account-merge.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Códigos de Resultado de Fusión de Cuenta
-sidebar_position: 110
----
-
-Estos son códigos de resultado que comunican éxito (200) o error (400) específicos para la operación de `Fusión de Cuenta`.
-
-Aprende más sobre la [operación de `Fusión de Cuenta`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#account-merge).
-
-<AttributeTable>
-
-- OpÉxito
-  - CUENTA_MERGE_EXITOSA
-  - Cuenta fusionada con éxito.
-- OpMalformada
-  - ACCOUNT_MERGE_MALFORMED
-  - La operación está malformada porque la cuenta de origen no puede fusionarse consigo misma. El destino debe ser una cuenta diferente.
-- op_no_cuenta
-  - ACCOUNT_MERGE_NO_ACCOUNT
-  - La cuenta de destino no existe.
-- op_conjunto_inmutable
-  - ACCOUNT_MERGE_IMMUTABLE_SET
-  - La cuenta de origen tiene el flag AUTH_IMMUTABLE establecido.
-- op_tiene_subentradas
-  - ACCOUNT_MERGE_HAS_SUB_ENTRIES
-  - La cuenta de origen tiene líneas de confianza y/o ofertas.
-- op_numero_sec_too_far
-  - ACCOUNT_MERGE_SEQNUM_TOO_FAR
-  - El número de secuencia de la cuenta de origen es demasiado alto.
-- op_destino_lleno
-  - ACCOUNT_MERGE_DEST_FULL
-  - La cuenta de destino no puede recibir el saldo de la cuenta de origen y aún satisfacer sus obligaciones de compra de lumen.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.mdx
deleted file mode 100644
index 47bcad79cc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/allow-trust.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Permitir códigos de resultado de confianza
-sidebar_position: 100
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos para la operación `Permitir confianza`.
-
-Obtén más información sobre la operación [`Permitir confianza`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#allow-trust).
-
-<AttributeTable>
-
-- OpÉxito
-  - ALLOW_TRUST_SUCCESS
-  - La operación de confianza fue exitosa.
-- OpMalformado
-  - ALLOW_TRUST_MALFORMED
-  - El activo especificado en el tipo es inválido. Además, este error ocurre cuando se especifica el activo nativo.
-- op_no_trustline
-  - ALLOW_TRUST_NO_TRUST_LINE
-  - El fideicomisario no tiene una línea de confianza con el emisor que realiza esta operación.
-- op_not_required
-  - ALLOW_TRUST_TRUST_NOT_REQUIRED
-  - La cuenta fuente (el emisor realizando esta operación) no requiere confianza. En otras palabras, no necesita tener el flag AUTH_REQUIRED_FLAG establecido.
-- op_cant_revoke
-  - ALLOW_TRUST_CANT_REVOKE
-  - La cuenta fuente está intentando revocar la línea de confianza del fideicomisario, pero no puede hacerlo.
-- op_self_not_allowed
-  - ALLOW_TRUST_SELF_NOT_ALLOWED
-  - La cuenta fuente intentó permitir una línea de confianza para sí misma, lo cual no está permitido porque una cuenta no puede crear una línea de confianza con ella misma.
-- op_low_reserve
-  - ALLOW_TRUST_LOW_RESERVE
-  - Los saldos reclamables no pueden ser creados al revocar debido a reservas bajas
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.mdx
deleted file mode 100644
index 79ef67b6de..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/bump-sequence.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Códigos de resultado de aumento de secuencia
-sidebar_position: 130
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos de la operación `Aumentar Secuencia`.
-
-Obtén más información sobre la operación [`Aumentar Secuencia`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#bump-sequence).
-
-<AttributeTable>
-
-- Éxito de operación
-  - BUMP_SEQUENCE_SUCCESS
-  - El número de secuencia ha sido aumentado.
-- op_bad_seq
-  - BUMP_SEQUENCE_BAD_SEQ
-  - El número de secuencia bumpTo especificado no es un número de secuencia válido. Debe estar entre 0 e INT64_MAX (9223372036854775807 o 0x7fffffffffffffff).
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.mdx
deleted file mode 100644
index 9eebe9c364..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/change-trust.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Códigos de Resultado de Cambio de Confianza
-sidebar_position: 90
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos de la operación de `Cambio de Confianza`.
-
-Aprende más sobre la [operación de `Cambio de Confianza`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#change-trust)
-
-<AttributeTable>
-
-- Éxito de Operación
-  - CAMBIO_DE_CONFIANZA_EXITO
-  - La confianza ha sido cambiada exitosamente
-- Operación Malformada
-  - CHANGE_TRUST_MALFORMED
-  - La entrada a esta operación es inválida.
-- Operación Sin Emisor
-  - CHANGE_TRUST_NO_ISSUER
-  - No se puede encontrar el emisor del activo.
-- operación_límite_inválido
-  - CHANGE_TRUST_INVALID_LIMIT
-  - El límite no es suficiente para mantener el saldo actual de la línea de confianza y aún así satisfacer sus obligaciones de compra.
-- Operación de Reserva Baja
-  - CHANGE_TRUST_LOW_RESERVE
-  - Esta cuenta no tiene suficiente XLM para satisfacer el aumento mínimo de reserva de XLM causado por agregar una subentrada y aún satisfacer sus obligaciones de venta de XLM. Por cada nueva línea de confianza agregada a una cuenta, la reserva mínima de XLM que esa cuenta debe mantener aumenta.
-- operación_autoconfianza_no_permitida
-  - CHANGE_TRUST_SELF_NOT_ALLOWED
-  - La cuenta fuente intentó crear una línea de confianza para sí misma, lo cual no está permitido.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.mdx
deleted file mode 100644
index 98006f7342..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-account.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Códigos de Resultado de la Cuenta
-sidebar_position: 10
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos para la operación `Crear Cuenta`, que a menudo falla porque la nueva cuenta no cumple con la reserva mínima.
-
-Aprende más sobre la operación [`Crear Cuenta`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#create-account).
-
-<AttributeTable>
-
-- CÓDIGO DE RESULTADO
-  - CÓDIGO DEL PROTOCOLO STELLAR
-  - DESCRIPCIÓN
-- OpSuccess
-  - CREATE_ACCOUNT_SUCCESS
-  - El resultado del objeto interno es válido, la operación fue un éxito y se creó una cuenta.
-- OpMalformed
-  - CREATE_ACCOUNT_MALFORMED
-  - El destino no era válido.
-- OpUnderfunded
-  - CREATE_ACCOUNT_UNDERFUNDED
-  - La cuenta fuente que realiza el comando no tiene suficientes fondos para otorgar a la cuenta de destino la reserva mínima necesaria y aún mantener su propia reserva mínima.
-- OpLowReserve
-  - CREATE_ACCOUNT_LOW_RESERVE
-  - La operación crearía una cuenta por debajo de la reserva mínima.
-- OpAlreadyExists
-  - CREATE_ACCOUNT_ALREADY_EXIST
-  - La cuenta de destino ya existe.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.mdx
deleted file mode 100644
index 5193d7b2ca..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/create-passive-sell-offer.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Crear Códigos de Resultado de Oferta de Venta Pasiva
-sidebar_position: 70
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos de la operación `Crear Oferta de Venta Pasiva`.
-
-Conoce más sobre la [operación `Crear Oferta de Venta Pasiva`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#create-passive-sell-offer).
-
-<AttributeTable>
-
-- OpSuccess
-  - CREAR_OFERTA_DE_VENTA_PASSIVA_EXITO
-  - La oferta de venta pasiva se ha colocado con éxito.
-- OpMalformed
-  - MANAGE_SELL_OFFER_MALFORMED
-  - La entrada es incorrecta y resultaría en una oferta inválida.
-- op_sell_no_trust
-  - MANAGE_SELL_OFFER_SELL_NO_TRUST
-  - La cuenta que crea la oferta no tiene un trustline para el activo que está vendiendo.
-- op_buy_no_trust
-  - MANAGE_SELL_OFFER_BUY_NO_TRUST
-  - La cuenta que crea la oferta no tiene un trustline para el activo que está comprando.
-- sell_not_authorized
-  - MANAGE_SELL_OFFER_SELL_NOT_AUTHORIZED
-  - La cuenta que crea la oferta no está autorizada para vender este activo.
-- buy_not_authorized
-  - MANAGE_SELL_OFFER_BUY_NOT_AUTHORIZED
-  - La cuenta que crea la oferta no está autorizada para comprar este activo.
-- OpLineFull
-  - MANAGE_SELL_OFFER_LINE_FULL
-  - La cuenta que crea la oferta no tiene los límites suficientes para recibir compras y cumplir con sus responsabilidades de compra.
-- OpUnderfunded
-  - MANAGE_SELL_OFFER_UNDERFUNDED
-  - La cuenta que crea la oferta no tiene los límites suficientes para enviar ventas y cumplir con sus responsabilidades de venta. Ten en cuenta que si estás vendiendo XLM, la cuenta también debe mantener su reserva mínima de XLM, que se calcula asumiendo que esta oferta no se ejecutará completamente de inmediato.
-- op_cross_self
-  - MANAGE_SELL_OFFER_CROSS_SELF
-  - La cuenta tiene una oferta opuesta de precio igual o menor activa, por lo que la cuenta que crea esta oferta inmediatamente se cruzaría a sí misma.
-- op_sell_no_issuer
-  - MANAGE_SELL_OFFER_SELL_NO_ISSUER
-  - El emisor del activo de venta no existe.
-- buy_no_issuer
-  - MANAGE_SELL_OFFER_BUY_NO_ISSUER
-  - El emisor del activo de compra no existe.
-- op_offer_not_found
-  - MANAGE_SELL_OFFER_NOT_FOUND
-  - No se puede encontrar una oferta con ese offerID.
-- OpLowReserve
-  - MANAGE_SELL_OFFER_LOW_RESERVE
-  - La cuenta que crea esta oferta no tiene suficiente XLM para satisfacer el aumento mínimo de reserva de XLM causado por agregar una subentrada y aún cumplir con sus responsabilidades de venta de XLM. Por cada oferta que crea una cuenta, la cantidad mínima de XLM que esa cuenta debe mantener aumentará.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.mdx
deleted file mode 100644
index 4552b9c165..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-buy-offer.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Gestionar los códigos de resultado de la oferta de compra
-sidebar_position: 60
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos para la operación de `Gestionar oferta de compra`.
-
-Obtén más información sobre la [operación `Gestionar oferta de compra`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-buy-offer).
-
-<AttributeTable>
-
-- Éxito de operación
-  - MANAGE_BUY_OFFER_SUCCESS
-  - La oferta se realizó con éxito.
-- Operación malformada
-  - MANAGE_BUY_OFFER_MALFORMED
-  - La entrada es incorrecta y resultaría en una oferta inválida.
-- op_sell_no_trust
-  - MANAGE_BUY_OFFER_SELL_NO_TRUST
-  - La cuenta que crea la oferta no tiene una línea de confianza para el activo que está vendiendo.
-- op_buy_no_trust
-  - MANAGE_BUY_OFFER_BUY_NO_TRUST
-  - La cuenta que crea la oferta no tiene una línea de confianza para el activo que está comprando.
-- no autorizado para vender
-  - MANAGE_BUY_OFFER_SELL_NOT_AUTHORIZED
-  - La cuenta que crea la oferta no está autorizada para vender este activo.
-- no autorizado para comprar
-  - MANAGE_BUY_OFFER_BUY_NOT_AUTHORIZED
-  - La cuenta que crea la oferta no está autorizada para comprar este activo.
-- Operación de línea completa
-  - MANAGE_BUY_OFFER_LINE_FULL
-  - La cuenta que crea la oferta no tiene límites suficientes para recibir compras y aún satisfacer sus obligaciones de compra.
-- Operación subfundada
-  - MANAGE_BUY_OFFER_UNDERFUNDED
-  - La cuenta que crea la oferta no tiene límites suficientes para enviar ventas y aún satisfacer sus obligaciones de venta. Ten en cuenta que si vendes XLM, entonces la cuenta debe mantener adicionalmente su reserva mínima de XLM, que se calcula asumiendo que esta oferta no se ejecutará completamente de inmediato.
-- op_cross_self
-  - MANAGE_BUY_OFFER_CROSS_SELF
-  - La cuenta tiene una oferta opuesta de precio igual o menor activa, por lo que la cuenta que crea esta oferta se cruzaría a sí misma inmediatamente.
-- op_sell_no_issuer
-  - MANAGE_BUY_OFFER_SELL_NO_ISSUER
-  - El emisor del activo que se vende no existe.
-- buy_no_issuer
-  - MANAGE_BUY_OFFER_BUY_NO_ISSUER
-  - El emisor del activo que se compra no existe.
-- op_offer_not_found
-  - MANAGE_BUY_OFFER_NOT_FOUND
-  - No se puede encontrar una oferta con ese ID de oferta.
-- Operación de reserva baja
-  - MANAGE_BUY_OFFER_LOW_RESERVE
-  - La cuenta que crea esta oferta no tiene suficientes XLM para satisfacer el aumento mínimo de reserva de XLM causado por la adición de una subentrada y aún satisfacer sus obligaciones de venta de XLM. Por cada oferta que una cuenta crea, la cantidad mínima de XLM que esa cuenta debe mantener aumentará.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.mdx
deleted file mode 100644
index 208f9c9744..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-data.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Administrar Códigos de Resultado de Datos
-sidebar_position: 120
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos para la operación de `Administrar Datos`.
-
-Aprende más sobre la operación de [`Administrar Datos`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-data).
-
-<AttributeTable>
-
-- OpSuccess
-  - Éxito de operación
-  - La operación de administrar datos se ha ejecutado con éxito.
-- op_no_soportado_aun
-  - MANAGE_DATA_NOT_SUPPORTED_YET
-  - La red aún no ha realizado este cambio de protocolo. Este fallo significa que la red aún no admite esta función.
-- op_nombre_datos_no_encontrado
-  - MANAGE_DATA_NAME_NOT_FOUND
-  - Intentando eliminar una Entrada de Datos que no está presente. Esto ocurrirá si el Nombre está establecido (y el Valor no) pero la Cuenta no tiene una Entrada de Datos con ese Nombre.
-- op_bajo_reserva
-  - MANAGE_DATA_LOW_RESERVE
-  - Esta cuenta no tiene suficiente XLM para satisfacer el aumento de reserva mínima de XLM causado por agregar una subentrada y aún cumplir con sus responsabilidades de venta de XLM. Por cada nueva Entrada de Datos añadida a una cuenta, la reserva mínima de XLM que esa cuenta debe mantener aumenta.
-- op_nombre_datos_no_válido
-  - MANAGE_DATA_INVALID_NAME
-  - Nombre no es una cadena válida.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.mdx
deleted file mode 100644
index 7e9f85e8be..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/manage-sell-offer.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Códigos de Resultado de la Oferta de Venta Administrada
-sidebar_position: 50
----
-
-Estos son códigos de resultado que comunican éxito (200) o fallo (400) específicos de la operación `Administrar Oferta de Venta`.
-
-Aprende más sobre la operación [`Administrar Oferta de Venta`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-sell-offer).
-
-<AttributeTable>
-
-- Éxito de la operación
-  - MANAGE_SELL_OFFER_SUCCESS
-  - La oferta se colocó con éxito.
-- Operación mal formada
-  - MANAGE_SELL_OFFER_MALFORMED
-  - La entrada es incorrecta y resultaría en una oferta inválida.
-- op_sell_no_trust
-  - MANAGE_SELL_OFFER_SELL_NO_TRUST
-  - La cuenta que crea la oferta no tiene una línea de confianza para el activo que está vendiendo.
-- op_buy_no_trust
-  - MANAGE_SELL_OFFER_BUY_NO_TRUST
-  - La cuenta que crea la oferta no tiene una línea de confianza para el activo que está comprando.
-- no autorizado para vender
-  - MANAGE_SELL_OFFER_SELL_NOT_AUTHORIZED
-  - La cuenta que crea la oferta no está autorizada para vender este activo.
-- no autorizado para comprar
-  - MANAGE_SELL_OFFER_BUY_NOT_AUTHORIZED
-  - La cuenta que crea la oferta no está autorizada para comprar este activo.
-- Línea llena de operación
-  - MANAGE_SELL_OFFER_LINE_FULL
-  - La cuenta que crea la oferta no tiene límites suficientes para recibir compras y aún satisfacer sus obligaciones de compra.
-- Operación subfinanciada
-  - MANAGE_SELL_OFFER_UNDERFUNDED
-  - La cuenta que crea la oferta no tiene límites suficientes para enviar ventas y aún satisfacer sus obligaciones de venta. Ten en cuenta que si vendes XLM, entonces la cuenta debe mantener además su reserva mínima de XLM, que se calcula asumiendo que esta oferta no se ejecutará completamente de inmediato.
-- op_cross_self
-  - MANAGE_SELL_OFFER_CROSS_SELF
-  - La cuenta tiene una oferta opuesta de precio igual o inferior activa, por lo que la cuenta que crea esta oferta se cruzaría a sí misma de inmediato.
-- op_sell_no_issuer
-  - MANAGE_SELL_OFFER_SELL_NO_ISSUER
-  - El emisor del activo vendido no existe.
-- buy_no_issuer
-  - MANAGE_SELL_OFFER_BUY_NO_ISSUER
-  - El emisor del activo comprado no existe.
-- op_offer_not_found
-  - MANAGE_SELL_OFFER_NOT_FOUND
-  - No se puede encontrar una oferta con ese offerID.
-- Reserva baja de operación
-  - MANAGE_SELL_OFFER_LOW_RESERVE
-  - La cuenta que crea esta oferta no tiene suficiente XLM para satisfacer el aumento de reserva mínima de XLM causado por agregar una subentrada y aún satisfacer sus obligaciones de venta de XLM. Por cada oferta que crea una cuenta, la cantidad mínima de XLM que debe mantener aumentará.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.mdx
deleted file mode 100644
index cf8962e055..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-receive.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Códigos de Resultado de Recepción Estricta de Pago por Ruta
-sidebar_position: 30
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos de la operación `Recepción Estricta de Pago por Ruta`.
-
-Aprender más sobre la operación [`Recepción Estricta de Pago por Ruta`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-receive).
-
-<AttributeTable>
-
-- CÓDIGO DE RESULTADO
-  - CÓDIGO DEL PROTOCOLO STELLAR
-  - DESCRIPCIÓN
-- Éxito de operación
-  - PATH_PAYMENT_STRICT_RECEIVE_SUCCESS
-  - El pago se completó con éxito.
-- Operación malformada
-  - PATH_PAYMENT_STRICT_RECEIVE_MALFORMED
-  - La entrada para este pago por ruta es inválida.
-- Operación no financiada
-  - PATH_PAYMENT_STRICT_RECEIVE_UNDERFUNDED
-  - La cuenta de origen (remitente) no tiene suficientes lúmenes para enviar el monto del pago mientras mantiene su propia reserva mínima.
-- Operación de origen sin confianza
-  - PATH_PAYMENT_STRICT_RECEIVE_SRC_NO_TRUST
-  - La cuenta de origen carece de la línea de confianza adecuada.
-- Operación de origen no autorizada
-  - PATH_PAYMENT_STRICT_RECEIVE_SRC_NOT_AUTHORIZED
-  - La cuenta de origen no está autorizada para enviar este activo.
-- Operación sin destino
-  - PATH_PAYMENT_STRICT_RECEIVE_NO_DESTINATION
-  - La cuenta de destino no existe.
-- Operación sin confianza
-  - PATH_PAYMENT_STRICT_RECEIVE_NO_TRUST
-  - La cuenta de destino no tiene una línea de confianza para el activo que se está enviando.
-- Operación no autorizada
-  - PATH_PAYMENT_STRICT_RECEIVE_NOT_AUTHORIZED
-  - La cuenta de destino no está autorizada para poseer este activo.
-- Operación de línea completa
-  - PATH_PAYMENT_STRICT_RECEIVE_LINE_FULL
-  - La cuenta de destino (receptor) no tiene límites suficientes para recibir el monto y seguir satisfaciendo sus obligaciones de compra.
-- Operación sin emisor
-  - PATH_PAYMENT_STRICT_RECEIVE_NO_ISSUER
-  - Falta el emisor de uno de los activos.
-- Operación con pocas ofertas
-  - PATH_PAYMENT_STRICT_RECEIVE_TOO_FEW_OFFERS
-  - No hay un camino de ofertas que conecte el activo de envío y el activo de destino. Stellar solo considera caminos de longitud 5 o más cortos.
-- Operación de cruce propio
-  - PATH_PAYMENT_STRICT_RECEIVE_OFFER_CROSS_SELF
-  - Este pago por ruta cruzaría una de sus propias ofertas.
-- Operación sobre límite de origen
-  - PATH_PAYMENT_STRICT_RECEIVE_OVER_SENDMAX
-  - Los caminos que podrían enviar la cantidad de destino del activo de destino excederían el máximo de envío.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.mdx
deleted file mode 100644
index 563c62a451..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/path-payment-strict-send.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Códigos de Resultado de Envío Estricto de Pago por Ruta
-sidebar_position: 40
----
-
-Estos son códigos de resultado que comunican éxito (200) o fallo (400) específicos de la operación `Envío Estricto de Pago por Ruta`.
-
-Conoce más sobre la operación [`Envío Estricto de Pago por Ruta`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-send).
-
-<AttributeTable>
-
-- CÓDIGO DE RESULTADO
-  - CÓDIGO DE PROTOCOLO DE STELLAR
-  - DESCRIPCIÓN
-- Éxito de operación
-  - PATH_PAYMENT_STRICT_SEND_SUCCESS
-  - El pago se completó con éxito.
-- Operación malformada
-  - PATH_PAYMENT_STRICT_SEND_MALFORMED
-  - La entrada para este envío por ruta es inválida.
-- Operación subfinanciada
-  - PATH_PAYMENT_STRICT_SEND_UNDERFUNDED
-  - La cuenta fuente (remitente) no tiene suficientes lúmenes para enviar el monto del pago manteniendo su propia reserva mínima.
-- Operación sin confianza en el origen
-  - PATH_PAYMENT_STRICT_SEND_SRC_NO_TRUST
-  - La cuenta fuente no tiene la línea de confianza apropiada.
-- Operación no autorizada desde el origen
-  - PATH_PAYMENT_STRICT_SEND_SRC_NOT_AUTHORIZED
-  - La cuenta fuente no está autorizada para enviar este activo.
-- Operación sin destino
-  - PATH_PAYMENT_STRICT_SEND_NO_DESTINATION
-  - La cuenta de destino no existe.
-- Operación sin confianza
-  - PATH_PAYMENT_STRICT_SEND_NO_TRUST
-  - La cuenta de destino no tiene una línea de confianza para el activo que se envía.
-- Operación no autorizada
-  - PATH_PAYMENT_STRICT_SEND_NOT_AUTHORIZED
-  - La cuenta de destino no está autorizada para poseer este activo.
-- Operación línea llena
-  - PATH_PAYMENT_STRICT_SEND_LINE_FULL
-  - La cuenta de destino (receptor) no tiene límites suficientes para recibir el monto y aún satisfacer sus obligaciones de compra.
-- Operación sin emisor
-  - PATH_PAYMENT_STRICT_SEND_NO_ISSUER
-  - Falta el emisor de uno de los activos.
-- Operación ofrece muy pocas
-  - PATH_PAYMENT_STRICT_SEND_TOO_FEW_OFFERS
-  - No hay un camino de ofertas que conecte el activo de envío con el activo de destino. Stellar solo considera caminos de longitud 5 o cortos.
-- Operación cruzar a sí mismo
-  - PATH_PAYMENT_STRICT_SEND_OFFER_CROSS_SELF
-  - Este envío por ruta cruzaría una de sus propias ofertas.
-- Operación bajo el mínimo de destino
-  - PATH_PAYMENT_STRICT_SEND_UNDER_DESTMIN
-  - Los caminos que podrían enviar el monto de destino del activo de destino no cumplirían con el mínimo de destino.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.mdx
deleted file mode 100644
index ea2800f6df..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/payment.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Códigos de Resultado de Pago
-sidebar_position: 20
----
-
-Estos son códigos de resultado que comunican éxito (200) o fracaso (400) específicos de la operación `Payment`, que a menudo falla porque la cuenta receptora no confía en el emisor del activo que se envía.
-
-Obtén más información sobre la operación [`Payment`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#payment).
-
-<AttributeTable>
-
-- CÓDIGO DE RESULTADO
-  - CÓDIGO DEL PROTOCOLO STELLAR
-  - DESCRIPCIÓN
-- Éxito de operación
-  - ÉXITO_DE_PAGO
-  - El pago se completó con éxito.
-- Operación malformada
-  - PAYMENT_MALFORMED
-  - La entrada del pago no es válida.
-- Operación subfinanciada
-  - PAYMENT_UNDERFUNDED
-  - La cuenta de origen (remitente) no tiene suficientes lumens para enviar la cantidad del pago y mantener su propia reserva mínima.
-- Operación sin confianza en la fuente
-  - PAYMENT_SRC_NO_TRUST
-  - La cuenta de origen no tiene una línea de confianza para el activo que está intentando enviar.
-- Operación no autorizada en la fuente
-  - PAYMENT_SRC_NOT_AUTHORIZED
-  - La cuenta de origen no está autorizada para enviar este activo.
-- Operación sin destino
-  - PAYMENT_NO_DESTINATION
-  - La cuenta de destino no existe.
-- Operación sin confianza
-  - PAYMENT_NO_TRUST
-  - La cuenta de destino no tiene una línea de confianza para el activo que se está enviando.
-- Operación no autorizada
-  - PAYMENT_NOT_AUTHORIZED
-  - La cuenta de destino no está autorizada para poseer este activo.
-- Operación de línea llena
-  - PAYMENT_LINE_FULL
-  - La cuenta de destino (receptor) no tiene límites suficientes para recibir la cantidad y aún satisfacer sus obligaciones de compra.
-- Operación sin emisor
-  - PAYMENT_NO_ISSUER
-  - El emisor del activo no existe.
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.mdx
deleted file mode 100644
index 74b441ca63..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operation-specific/set-options.mdx
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Códigos de Resultado para Establecer Opciones
-sidebar_position: 80
----
-
-Estos son códigos de resultado que comunican éxito (200) o fallo (400) específicos para la operación `Establecer Opciones`.
-
-Aprende más sobre la [operación `Establecer Opciones`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#set-options).
-
-<AttributeTable>
-
-- OpÉxito
-  - Éxito en la configuración de opciones
-  - Opciones establecidas con éxito.
-- OpBajoReserva
-  - SET_OPTIONS_LOW_RESERVE
-  - Esta cuenta no tiene suficiente XLM para satisfacer el incremento de reserva mínima de XLM causado por agregar un subentrada y seguir satisfaciendo sus responsabilidades de venta de XLM. Por cada nuevo firmante agregado a una cuenta, la reserva mínima de XLM que esa cuenta debe mantener aumenta.
-- op_demasiados_firmantes
-  - SET_OPTIONS_TOO_MANY_SIGNERS
-  - 20 es el número máximo de firmantes que una cuenta puede tener, y agregar otro firmante excedería eso.
-- op_flags_malos
-  - SET_OPTIONS_BAD_FLAGS
-  - Las flags establecidas y/o eliminadas son inválidas por sí solas o en combinación.
-- op_inflación_inválida
-  - SET_OPTIONS_INVALID_INFLATION
-  - La cuenta de destino establecida en el campo de inflación no existe.
-- op_no_se_puede_cambiar
-  - SET_OPTIONS_CANT_CHANGE
-  - Esta cuenta ya no puede cambiar la opción que desea cambiar.
-- op_bandera_desconocida
-  - SET_OPTIONS_UNKNOWN_FLAG
-  - La cuenta está intentando establecer una bandera que es desconocida.
-- op_umbral_fuera_de_rango
-  - SET_OPTIONS_THRESHOLD_OUT_OF_RANGE
-  - El valor para el peso de una clave o umbral es inválido.
-- op_firmante_malo
-  - SET_OPTIONS_BAD_SIGNER
-  - Cualquier firmante adicional agregado a la cuenta no puede ser la clave maestra.
-- op_dominio_hogar_inválido
-  - SET_OPTIONS_INVALID_HOME_DOMAIN
-  - El dominio hogar está mal formado.
-
-</AttributeTable>
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
deleted file mode 100644
index 0856c4a6d3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operations.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title: Códigos de Resultado de la Operación
-sidebar_position: 20
----
-
-Estos son los Códigos de Resultado que comunican éxito (200) o fracaso (400) a nivel de operación: sin cuenta de origen, demasiadas subentradas, etc.
-
-<AttributeTable>
-
-- CÓDIGO DE RESULTADO
-  - CÓDIGO DEL PROTOCOLO STELLAR
-  - DESCRIPCIÓN
-- op_inner
-  - opINNER
-  - El resultado del objeto interno es válido y la operación fue un éxito.
-- op_bad_auth
-  - opBAD_AUTH
-  - Hay muy pocas firmas válidas, o la transacción fue enviada a la red equivocada.
-- op_no_source_account
-  - opNO_ACCOUNT
-  - No se encontró la cuenta de origen.
-- op_not_supported
-  - opNOT_SUPPORTED
-  - La operación no es admitida en este momento.
-- op_too_many_subentries
-  - opTOO_MANY_SUBENTRIES
-  - Número máximo de subentradas (1000) ya alcanzado
-- op_exceeded_work_limit
-  - opEXCEEDED_WORK_LIMIT
-  - La operación hizo demasiado trabajo
-
-</AttributeTable>
-
-<ExampleResponse title="Respuesta de Ejemplo para un Código de Resultado 'op_no_source_account'">
-
-```json
-{
-  "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",
-  "extras": {
-    "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAADAAAAAAAAAAAAAAABAAAAAQAAAACuSL9OciKkFztj4d3zuadl20HHObu+7qJenBxHPrMayQAAAAUAAAABAAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtJBKRwAAABA1N0iqDAgqS6+3RIZGoNB9OXrY3wd/nLruXYi+eiTt4jn94fLVLwAw6jJCaK+qxStwO7c4kP6u5k0RPbuYC55CT6zGskAAABAiUGCNCS4pGlfcRmi82kbralzcFlTQAFzLyfUrYGn3RtQ4p/7TUwAqIanVoWGfEqzIJo64ZT+mYtJ72BfI+FiDg==",
-    "result_codes": {
-      "transaction": "tx_failed",
-      "operations": ["op_no_source_account"]
-    },
-    "result_xdr": "AAAAAAAAAGT/////AAAAAf////4AAAAA"
-  }
-}
-```
-
-</ExampleResponse>
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
deleted file mode 100644
index 468966e6f0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Códigos de Resultado de Transacción
-sidebar_position: 10
----
-
-Estos son los Códigos de Resultado que comunican éxito (200) o fracaso (400) a nivel de transacción: números de secuencia erróneos, saldos insuficientes, tarifas insuficientes, etc.
-
-<AttributeTable>
-
-- CÓDIGO DE RESULTADO
-  - CÓDIGO DEL PROTOCOLO STELLAR
-  - DESCRIPCIÓN
-- tx_success
-  - txSUCCESS
-  - La transacción se completó con éxito.
-- tx_failed
-  - txFAILED
-  - Una de las operaciones falló (ninguna fue aplicada).
-- tx_too_early
-  - txTOO_EARLY
-  - El closeTime del ledger fue antes del minTime.
-- tx_too_late
-  - txTOO_LATE
-  - El closeTime del ledger fue después del maxTime.
-- tx_missing_operation
-  - txMISSING_OPERATION
-  - No se especificó ninguna operación
-- tx_bad_seq
-  - txBAD_SEQ
-  - el número de secuencia no iguala a la cuenta de origen
-- tx_bad_auth
-  - txBAD_AUTH
-  - muy pocas firmas válidas / red incorrecta
-- tx_insufficient_balance
-  - txINSUFFICIENT_BALANCE
-  - la tarifa dejaría la cuenta por debajo de la reserva
-- tx_no_source_account
-  - txNO_ACCOUNT
-  - no se encontró la cuenta de origen
-- tx_insufficient_fee
-  - txINSUFFICIENT_FEE
-  - la tarifa es demasiado baja
-- tx_bad_auth_extra
-  - txBAD_AUTH_EXTRA
-  - firmas no utilizadas adjuntas a la transacción
-- tx_internal_error
-  - txINTERNAL_ERROR
-  - se produjo un error desconocido
-
-</AttributeTable>
-
-<ExampleResponse title="Respuesta de Ejemplo para un Código de Resultado 'tx_bad_seq'">
-
-```json
-{
-  "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",
-  "extras": {
-    "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAArki/TnIipBc7Y+Hd87mnZdtBxzm7vu6iXpwcRz6zGskAAAAAAAAAAAAHoSAAAAAAAAAAAdJBKRwAAABANWeKuRYFmBm1lrMQqMvhbSouwL270SnxcTtv1XI4Y+uVe4yw4Jq7/43EoxwLbRh/pC3V4WfOZRzDqwsTyEztAA==",
-    "result_codes": {
-      "transaction": "tx_bad_seq"
-    },
-    "result_xdr": "AAAAAAAAAAD////7AAAAAA=="
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-all-offers.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-all-offers.api.mdx
deleted file mode 100644
index 81e7b7848c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-all-offers.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-all-offers
-title: "List All Offers"
-description: "This endpoint lists all currently open offers and can be used in streaming mode. Streaming mode allows you to listen for new offers as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time. When filtering by buying or selling arguments, you must use a combination of selling_asset_type, selling_asset_issuer, and selling_asset_code for the selling asset, or a combination of buying_asset_type, buying_asset_issuer, and buying_asset_code for the buying asset."
-sidebar_label: "List All Offers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ly27iWfhUUf6STLu2rrarUjGwtli1vWrwo7bIh8khCmwR4AdCKr8tV8xrzevMkUwckZWqJ7Ti5naTvzR/bJHg2fAc4OPjyYGk6VVbtk3U8mYBU1lXKckDZkvmaCW7VrMGMKQLc8QXjmrhMaUWo6xI7kBK4du+J8IETYT4nlDvEppyMgQQKHMI4UVoC9RifEk84kCH9pb9Rlpgrci8CooWRD5xMhCQc5gupiugZ3BMqgVDHAQeH6hmQvgbXpZK44ExBZkhnQmzqupsUp8iekOyfgpM5c12iNJWaUG3EAJUuA6XJLRfzyBcScBeUIhQ9VUISpogCnULJ8xmzZ8SmCgjTSXkTKTyiZ1RHH2XIzj1+pdEK1BTJuqNuAOgEF/OU8R2DFhocO21LoBocohi3AcdIIuEfAZqpmQcZcj7DSDFXg0Tx43syDu7xNyGJAtfFX6mcBh5wrUItXqA0Tgx6Jbwx4xRnmYhJ/ME1VQr0tb73IbXyjCkVgEyZKV5+Y+M84pShhwvNykRLyHVdoZlLqpYeJTUtvVhSFDlr3mSslCV8kEZFx7FqVht03XUjUKcsn0rqgcY/ap8eLE49sGqW8gVXIK2UxRDq/whA3lspC8PMJDhWbUJdBasZUbdtEXBNOg10xviMcnC2m3cg7wmNBjBu3koI9YRAAaZnIDFBoq/AwanDgVN2B3zxNYqXZEbvcLZUMAau5T15r2WgtMs4pEKgmBA7VFNiBnyIwIlofUk+Rk3ZM/CoVXuwcCIwJhrRZKUs+Ew938VH7cbh6enR/mFp2K2eduqVykm1VzgZ7R2edo7ORzuH1epOc+dwr9u6aJT3m8P6Xnu/2ivtj6zHx9RTrMF1vzrUgxksxSMMd5ifJj+EzFgrSpah9QaF+NlmOGdIM5w9xPIdpNAGh+lr6vozygOvZCZj5WG+8EKceeDhAhzKtFLWqtD1R/mCdbUa29X0eYPj8WpKHUfi0heFO5QX/2V0kDFgUJRwHfJ+jOugefwhQ3qRGsLC4TfrU3KD4ORCk5vQ5ZvX43B4cNgethuj04PK5d5lvTyq1C8L7dJFoz866Y+K/fPy8KhY750dHldO+73G+Un5stu8WMPh8oryhkgtLUQ/MCLDfmPJubWV9Vvhn/RtLILpTJP3Jh1BLhyMciK2PUVuVhF8Y/Ji9XG+8JKf354ZG/aVvyIxvhSqNSysTdiPTY613fZ75sYPCEpz2FvyLyy/vna/JzzwxiDDws7UwQprN0qUDzabMJu4wg6rG8ZNueO6YMfVTrz9h8UxU8QPTIUa1YpAfDpFd7W4BR5VhmJCKJFgC+lsdJVxDVMD5YWvlUquUslXS9Wt7fJ2PldOui2k8/VVDnFAselT1WZ2XhT0VAGHFiqiZiJwHUJ9H6jMkGMjQxHGbTdwgNxQZd+Q91TZwB3Gpx/MaoDqbsh7/BE9NvW7xvNGXLYSpvj//c//6qjy1sSBCQ3cMP5G7OtWEKpsK3RweXlwmcf0GzDu0c/MC7wYGGaWw1BI0IHk4GQIjjPyTW0vKZ9COOd5NL6Qy5E0oZwEvg8yGmgAxhSZUelgGpljTHxswZTyQU6E9CieCCRQJbh6JmjxBIKzFrt87rW4yuceH69S1ue0CnxfSK3Si3OVVdMyAAxYhHCUVMjl8MdyzPqBbYPCQtwWXAPXOIT6vsvCvMn+qXDcQ8IiitW7KdYj28T4T7BxsnyJpb5mob5rl/FblfDhC+MUuJOXR80kTDYByURdG8TwW+sxZWnwfBdDmxg9FsIFynHFSYDoUyj0KmVppl1IyODwWf9kJvkS7n4qkx5xWPyoa6Ya8/cFTIA3BuwTvOxKlLeJgVRKissA0+C9Ale/MP7MOerao7cgfyrLVgaZyC1be/WYspizyZxYEnMMnBNb6/rox1R8Kt0gyKdag8TFq/2pnh7l0ttXD+XyY0JFVA3GYsyC+FIUE5X5JnMShdeXX0dl7PqAlbgldCVCvEMV1PENCgwrrV/ObOphCblRly+ZDdevwHMSD0/b3gLNjOtiAQU6rxqXWKRO0IKFKRuNdKnS155w2ISBcx02L59XE4R6EpmyScSaaGwUbsZ91Pl6cTaYY62kUeqplRPDfgGkxdQ8TUQchy94vdHiq8fldd+08axHzPqoLjFTuNTjqz1YpnZeXpPjVTdcvayZ1r6qZbOzsKZKa1Cag86o8ICXEXKaDduv/xUeFT6+M5XZx+I7U/p+pMp+t95B+DjsN95tasJ8fOup7N16k+Dj2uk3UUK82b+trWKpnC8XfnI/47rkzX5W85VqsVSorviJZepP5Ohjarl2WVQnn74LqLNxFDbs/l8hLOrIqmx7Z//kvNlpXVQOjkt75cJOq3i637js7XYvdgonxVHxdHBwPmy3jo9be+XDfm90Vjrv9kZV4yju37E9qzu1tTD0aYu23qxtaX9ObmWbGkrJvcz011b3r2/otCQ33K+yY2ewu8GO+nAwvLwsDPa6rWq/3Rk0WocX+2eXe8XuXqN/2G7WD/o7w0Klelg4qNaL5+VScfdg2Gwld1CrUM5UyqVytVq2ljZPbtUKW9uV7UquWjSbYKFcKZeq1crTxmbl85nCdiG3nS9+aXWvFSrbW/lKqbJ5Y7IKufx2Op9PFyqDfLFWKtTyuZGp778H2Le2ioWtQm7ru4G9f3nY3WuXB+3T0nHxqH/SOS41+rv9Un23ctnbPz49P90tNs+rx4VytVcf7nXK/Xqp3FuAPbZnDewLQ5fA/kZtf1ew75wddyvVweHwdKfdLQ1Gl0eHl8XRafm8fXrZOmk1ymf7vfOLXrVwVi8Wz1pH3UKhfNItL4M9U6pUSlvbxTWsl3M5g/J8oVhMIDyXKeXK5Xw592WAF7e2KpVK7jmA58rpfHWQy9WKxVq+8l0Bbvbu7wXw+u7g9KQ8qJ93LlqF7lmpfd7eP+8Mj/YOGuejQmew22qcFKutTvu4ddIrHvcOT3u9SnGYBLixZxPAQ0OTAH+rtl8f4Jvt2BleDuudavni4rwxah50LyuV3dblwelJc1De75WazaOL0c5wVLy8GFUb/XJlVDo+OG4NlwCez2Vy4b81hOfzIcBzyQU8k1+M/jK8q9Xq1ivgXajlt2v57RHW6dE/LNc1cIXdYFPD3MK9VdvcS0zF5Tv2FLHj6IGeCbzKn4IOz+Mzq2ZF2DcokHfxfX4g3deh3drUzR2E48gR6LmQtyY/N0ucBDqQ8BqZrXgk4bHUK+wzT4Q5c0UHm6i3i86DVOHXuUwuk0f/As+j8v5pFPGluGOOuUgge4PBCamfdLCZa27/I7JBfFUVac2QDvIQpmBoO9whEtImcIZRE37pS+EE9hNNYEVEeKeBJ9FFfxqoYngfIogtuAo8iD+ldyDpFEiitUskuObSJubsJHrYaSEZcCS5GEMk+BIUcE3D+wPDIBrfLwzaFRKwr86U8Tzhx1gyZwpkDHoOSHHw/dDb5S9PpMBWgCIuuwUyR6IQEmMcsJE6QV32T3AIfLZn2KtXIf8kvMAKs9RYtOjHa4GsDNO2l5Qrai58VIqYawScopi4MKYuOmvuQCOKD9whJye0I/m1uVZafJlZQ9a/OxI+JSf06n2cng7cgYvNHbW0s0VmZ20hIc2FAx/+rdDzB/+Dx+oiTh411zDgkDtGiT3sdVOEkrEUcxURiQSH+K5vEet+40C9GGtH2CqrhXBVVjm3CiMtiASEU0h8E9i2+cz0Pco3bDY/DGiKzMFcn3kecMfQ1AxDjaNiwrjSQB38yKO3eI3sMAm2NnOIXD9l/DTTOg2YAyTMmDEoMhNzExLHYxx5hUhFCyFu4BjHBlWYG7X3EiYhmI3/jYWnv5EdV0yfYjCfz5edX4xMj10xzdI0h3laBTyNu9AM0tH+8cFc4imBaULt26kUAXeI4KvZEGJH2jOmwdaBpC5hHuY8GC5fOENMEY/+iWTCcOsg48DzP2RIC7mKPOwc4mM6FgFe/hkTDT0w1LeAhnAACSspYs/AviU4Oum/uVJsY2ifAjBlehaMM7bwslEcslORHbtinPUoRjqL6cVsUPHWmcWmpuTUDZHSHnYazevWce+60Txrdo9Pmr1+xnM+mMncgYmQgLAYw5RxvLz8TZG5kBqvnJk2PL+IUImLBDMmgj0T4Y2psR6TlhwJ5y3LBHGEba5STQRr5Pff50AcYSgIwB0hFRAZcI5GxGHECQ0XKYpkUO5QF5MpuYYskPb77+HyAIZAQF333og2317fUZc5xsHrtZ0PMDEkED0XRAGSGjWmFrdB8mjJccAWge9G8fFwkWYeFluUawO/sTBhdBkdMxfzEb9KgC+zlBiYex7ldAqKMITenKeITyU4aQe5sjH4xGTZVeFr5pklEXVGX+KShwuimBAO4Cjyfg6/uS5J5B0zbF9K/rB2qW82CxT3h7WIHUIE++AgPXU86YcwS5RqyZk1g9Jiko7QGN0/U9v0TCMOQGx2Eu4tTEwz+VZqpRRcLvzAo8y8BdcV/518h714ZgNXkNBV96k9A1LIYMXNHMTuhJnyP3yTDt88aYwWG2reGp8ioSrb7ew2j/pN/CQz055rjmG+UNqjPKGyy5QmddclCy7sUknx8HQj/x+q93+o3r8G1Ts6Z2v4rLO+SxnHbDNJ8xCdEz9ZYvH/GWZCaXzy8IDb3FC6j4/4OKT74OnRYYqO3S8RfpIZ8reifm+MYnhCfyLGR4dyyxyKn1k5XsHTfl5jfKe4rPDVM/MvI26/YPMa3fYb7P+R/OtXu7kg0X6Do38FffrVDkU01++Fu7+AMf2Ma5sI4H8lIr8zx/e1nv5LQfmDfPo2XP540vIzfi5o2G927pfhJj8ThZiV/Q2Y/ZvwkJ8JUszQfgrSFf4hGUbJqn1CTtAMKEby6YKhbtvgJ79aoxovXTC0mwPr8fH/AVsHdrw=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Offers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/offers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all currently open offers and can be used in streaming mode. Streaming mode allows you to listen for new offers as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time. When filtering by buying or selling arguments, you must use a combination of selling_asset_type, selling_asset_issuer, and selling_asset_code for the selling asset, or a combination of buying_asset_type, buying_asset_issuer, and buying_asset_code for the buying asset.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"sponser","in":"query","required":false,"description":"Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"seller","in":"query","required":false,"description":"The account ID of the offer creator."},{"name":"selling_asset_type","in":"query","required":false,"description":"The type for the selling asset. Either native, credit_alphanum4, or credit_alphanum12.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"selling_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the asset being sold (base asset). Required if the `selling_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"selling_asset_code","in":"query","required":false,"description":"The code for the asset being sold (base asset). Required if the `selling_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"buying_asset_type","in":"query","required":false,"description":"The type for the asset being bought (counter asset). Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"buying_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the asset being bought (counter asset). Required if the `buying_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"buying_asset_code","in":"query","required":false,"description":"The code for the asset being bought (counter asset). Required if the `buying_asset_type` is not `native`.","schema":{"type":"string","example":"EUR"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offer_maker":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","offer_maker"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"seller":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"selling":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"buying":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"amount":{"type":"string"},"price_r":{"type":"object","properties":{"n":{"type":"integer","format":"int32"},"d":{"type":"integer","format":"int32"}},"title":"Price"},"price":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"sponser":{"type":"string"}},"required":["id","paging_token","seller","selling","buying","amount","price_r","price","last_modified_ledger","last_modified_time"]}}}}},"title":"Offer"}]},"examples":{"GetAllOffers":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers?cursor=&limit=3&order=asc&selling_asset_code=USD&selling_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&selling_asset_type=credit_alphanum4"},"next":{"href":"https://horizon-testnet.stellar.org/offers?cursor=88345152&limit=3&order=asc&selling_asset_code=USD&selling_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&selling_asset_type=credit_alphanum4"},"prev":{"href":"https://horizon-testnet.stellar.org/offers?cursor=71673427&limit=3&order=desc&selling_asset_code=USD&selling_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&selling_asset_type=credit_alphanum4"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/71673427"},"offer_maker":{"href":"https://horizon-testnet.stellar.org/accounts/GBJPWEIFX6KO4H52BF3QJDYRCLXB2P3Z3QTKWUGFOOFH5MSRZV4WLRZ7"}},"id":71673427,"paging_token":"71673427","seller":"GBJPWEIFX6KO4H52BF3QJDYRCLXB2P3Z3QTKWUGFOOFH5MSRZV4WLRZ7","selling":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},"buying":{"asset_type":"credit_alphanum4","asset_code":"BTC","asset_issuer":"GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF"},"amount":"25.6545775","price_r":{"n":289696073,"d":25654776},"price":"11.2920913","last_modified_ledger":26981646,"last_modified_time":"2019-11-26T13:42:10Z"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/88328208"},"offer_maker":{"href":"https://horizon-testnet.stellar.org/accounts/GBSYMLHG5TGQ4O3NSPIO4DSCS4AC6YRJOQWQC3EW7O257RAUHI5SA45R"}},"id":88328208,"paging_token":"88328208","seller":"GBSYMLHG5TGQ4O3NSPIO4DSCS4AC6YRJOQWQC3EW7O257RAUHI5SA45R","selling":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},"buying":{"asset_type":"credit_alphanum4","asset_code":"BTC","asset_issuer":"GBVOL67TMUQBGL4TZYNMY3ZQ5WGQYFPFD5VJRWXR72VA33VFNL225PL5"},"amount":"2.4664893","price_r":{"n":500,"d":1233},"price":"0.4055150","last_modified_ledger":23886660,"last_modified_time":"2019-05-17T00:33:16Z"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/88345152"},"offer_maker":{"href":"https://horizon-testnet.stellar.org/accounts/GACTQP5TAWIXF2LV4GWGJWIUNHKDWZ2ITCFDP37FIGOFPR3ORMQRR63U"}},"id":88345152,"paging_token":"88345152","seller":"GACTQP5TAWIXF2LV4GWGJWIUNHKDWZ2ITCFDP37FIGOFPR3ORMQRR63U","selling":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},"buying":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"},"amount":"10.0000000","price_r":{"n":11,"d":10},"price":"1.1000000","last_modified_ledger":23887778,"last_modified_time":"2019-05-17T02:19:19Z"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-all-trades.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-all-trades.api.mdx
deleted file mode 100644
index 4a07d98e07..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-all-trades.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-all-trades
-title: "List All Trades"
-description: "This endpoint lists all trades and can be used in streaming mode. Streaming mode allows you to listen for new trades as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time. When filtering for a specific orderbook, you must use use all six of these arguments: base_asset_type, base_asset_issuer, base_asset_code, counter_asset_type, counter_asset_issuer, and counter_asset_code. If the base or counter asset is XLM, you only need to indicate the asset type as native and do not need to designate the code or the issuer."
-sidebar_label: "List All Trades"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ty27YSfhUMf6RJRxfqQsnSTOYc2fItdmzHsnxLPTZEriTUJMACoGXX45m+Rl+vT3JmQVKmJPpSxzlN02amk0ZcALsfvgV2gcWtpelIWe3P1oGkHijrrGB5oFzJQs0Et9rWwZgpAtwLBeOa+ExpRajvE23kCeUecSknAyCRAo8wTpSWQAPGRyQQHpRIb+bf2FhMFLkREdHCdAicDIUkHCbTXhXRY7ghVAKhngceiuoxkJ4G36eS+OCNQJbI5pC41PfzBi6QDSHZr4KTCfN9ojSVmlBtugEqfQZKk0suJjwelUTcB6UIJW4klZCEKaJAF7DnyZi5Y+JSBYTpbH9DKQKix1QnjUpk+QZbadQCR0r6uqJ+BGgEF5OCsR1BixVOjXYlUA0eUYy7gDKSSPglQjU1C6BEjsaIFPM1SOweMaNEheCyIXOJkB7IgRCXcf9BpDROifkPJ0yxayKGqBT+IEdRAFyrNhlQBedUKdDn+iaEQvYHplQEcuYn10DriohrkDPtZn9LmxqCzHxxDSs2jSqmZyJkKkKMCEJ/vP0xNkRw/4ZwiDnAuMdcqsG0jWVxcCQMp5pdgRnPQ5z1tJEHio142gqHxxHx/2MlS1bBEiFIipTf9Ky2tQ664/uJSxSskEoagAaJnnJrcRqA1bbEcAjynHlWwWLoKb9EIG+sgoWTxiR4VntIfQWLDgXENCWb3RLpq1jHeFrNnCZ0EJKNGBqFU400y841ti9Zd4WpMnOz+AKdDI7DBBgzLaa7ElllegySXMQAXxTIhSvBY/qc+uGY8iioXxQQ0PmfK9ULRFa5Ywio1b61jGJtS2mkr1WwgEcBLj1xx1bBmu938adK1Tq7yzc7nssXGJ6uKdTzJC4AYjgHwR+//a5SqpD9pEPCYrGLOeQvkLzIvhSvJzC4pkHo40/r3f7Wx/X+evf001bjZOOk45w2OifV9fpxt3e61zut9Y6c/k6ts3/4cbfxqbffPdpzTrZXj60H8ECevwAN4x55NPhqhvd73RkbFteWL2XzzOIyJXSsZoHMs86QeYF3X53Kecvn67F5BoLHCb2I/1/L6cXd40tpPceHr4nAPLnN4v4SUq/EQZbZ8QRu6IXsji8k8dkvEfOYvjkPhfBVZlMxO2iyq8A1uBFGGdSVwkQ7I3YFnATgjilnKngez6nv46aZKmAVrLnh57htoqA/aXGH8CgYgIzjKxN/Gqsy+6AvXLNpY4xGiSt8H1zzbzEkElQouEpiVKZIGJlAMQnZgIR0xPjoXItL4EmAJoaEEgmukF4uDoxrGBm3nM5wo2E3GpVmvbnUcloV28mabfD501an4UpiB6pqOroPRGMNFVFjEfkeoWEIVJbIrulDEcZdP/KAXFDlXpC3VLnAPcZH78wujcNdkLf4V/JzEowxNQ0LCVP8j99+10kArIkHQxr5Mf6m22fSRLlWbOAsH3wWMP0CLw7oNQuiICWGmeUYCgk6khy8EkE5078JsSXlI4jnvILKV22bFAnlJApDkImgIRhTZEylhwuFySbS7AEXjRDkUMiAYmAugSrB1SOgTeNNbwG7iv1cXlXsu7uzgnVdVFEYCqlVcZreWG0tI0DAEoZjT1Xbxr9mMetFrgsKQ1hXcA1cowgNQ5/FflP+WaHcbUYj6vu7QxPmJrqJwc/g4mSFEoNkzeLxzn3GL1XGhgfkFPjDp6XGEoZ5RDKoa8MYfmndFSwNQegjtBnpgRA+UI7rbIZEn+NOzwqWZtqHTB8crvU3plIo4eqbUukOxdKfts1Uo/8+wQkIBoDp+tOmJH6bEaRSUlwGmIbgGbz6G/MPA+dvTKUk4vnGtJom5d+UXnNChmDJpN4DmVX+7K5gMS9Pu7Rj5plFIBOQPCY9I3dXsOLDsHPXFwrO8ahosTGCmR5X5H3MhKV5n2eDu/MhwPkgzEjG+3EW7ohxXaumbD+f6+ABLYzoo3rGOadrUM6DKKRag8Stb/1zp3hqF1tnt45zlwEvyYvuOwvy+5p+v89Cn5AxmckTMklalyeVJh3PgyqVfhStaR7zSoBN+3sYs5zk/WmxB5HLzYlfZdqZOlfg+zPdTZcBXFyYC/E+de/p5qhvxvnyfK8wm+NlSbZIqQVMcxFc0BnXpEeXw5z1465g5bEks80bvfeM5Xfxn/tv5izUusOlLAlRzTgzB6XtW8ukUbPbc7oBxyu0NdY6VO1yeRyH10UNSnPQJRWfW5SEHJXjXPU/c771vt/rvlnwpfcvPWN4MzcX7+ePbN4szsT7OPt/E+ez79+Y9OF97Y3Jz95jtpMJL79Dg5dqttOwbbvasBv1pVajUrTzMUjj2e8Rg+qSU28sNRyn5jQrtZq9gIHJd9F5ZuLhacT7+RHvyIaHfwK7ZIFX5fVuvfmx6nzc7q30Tvbqvc3DnU/Hh5/qW0c724frx716r9o53js4Wf2w1dg9qR92tj8cbdWXe3Mx4IuGXl7Z2HKq/eNOd+XTym5zbbnjHC6f7K2vfFg73ljZ6Rx+OPjYX93aXVnZ2fqw4azVnP5p3zlYCPT+xODTdqq8MC1mBnBjtHJmbH4hf0goJ7SyqnZlqWgvFW3nwLbbjtOu1U+tbHxlVWt2s960a9ZCSLPwabo1Wy+eurlAxqpWS61Ks96qV3I2nHbeyfRCEGOOLXMDl5cf6ebFLFa90ao7dbtp11tLdstpVWt1KydusV5MrsWgxWo1S61Wq7Vk2/m7bfv+FH8+VIjPXabBAfKmYjdatlO1W5bZX62qY5s/8anvd+no3f7+YW2z0Xd2D/qHTefoqLNe3Tg6Pfi0sfNxZb+2s1/dc9b3trorm71qZ/VoZa23u3241n8tR6/ZtlOtOhWnWV1qtmrNjKPPf8p19FyhRx29eWBX23al7dQWHL1u2/V7R3vk01dw9ErJTrj2t/DzRqtSrdecpXqj6SwZYHL8/KXcyvHzeqlm46JSew03r8d9VSuJm1ds+7v38+Wd7nK9v7Hd3V/e3q85H3b69U73ZL32wTnq1Lc/nO7uLR9/3Nk43TrY6m3Xmsvd43p/+dPJ6/n5bKw54+fzYWiun+cIPeHnlaV2tdmu/evnX+DnzToC2lhasmsYTz2wn7+QW3+ln5/dTdNiuNbAFfLUxPOXcGO18+9qCmlOjIPhjU4Aeiyw6xHo+OhibLWtJP3ByyGQV2mlUST95zmOlXdbdhDLkR3QEyEvzQF+fo/DSEcSntPnWipJeNrrGd7jDYU5W0hOC5K7MzQepIpb2yW7hKiqKAiovLmXIqEUVywuJiQbBwd7pLO3aeq2qKZ4E5ct/EtGLZFNTRgfgSlH5B6RUDTAmcLBuGUohRe54JHBTV4X8Z0xHlhO7/+AKob3zYK4gqsogLQpvQJJR0AyV2dEgh9XnCWliZk7wqKQDDjeshtFJIQSFHAdr2xxoeTgZqrQipCA95ZMGcszdgwk80ZABqAnAByHj62dbbknBR4CKeKzSyATrIfUqkA8cIFrSX32K3gErvGCfwQqLslL6+xwFTAaTe87tSAqGphrUUm5ouZCXRWIuabFKUq8mAyoj8aa4oOkkhGusKYw1iPb2lzbT1uWFpj1T2fC5+yEnr1N3dODK/BxS1Qzm2SidtkVEopcePDuH8Wen/hPPB0uKT2m5pobPHLFKHH7+9sFQslAionCElSBJTCQ1lJMse51t9STWHvCVWWNFS1l5V0qRFoQCUinpJQIz0Kvmb7B/k3RbhgDWiATMOUJQQDcM6WsphSX48CEcaWBetgooJdY4+kxCa42c4glzcrYaaZ1FDEPSOwxA1BkLCYGEi9gHMunsQw4prihY4oNDmEqFt5KGMZkNvZ3p5b+QJZ9MbrHYDKZzBo/lSwOfDEq0yKHSVFFvIi70BiKyf7xzhRJKIFuQt3LkRQR94jg894Qc0e6Y6bB1ZGkPmEB+jyYWuR4hpgiAf0Za6bjrYMMoiB8VyJrWJLN4wsm/JkORITFFUZFBDAZb0oN4QFu+AXijsG9JCidtd+UbKwjtPcAjJgeR4OSK4JygkN5JMoDXwzKAUWky+hezAWVbp1lLN2QnPoxU9b7m93V87Xd/fPu6uHq9u7e6n6vFHjvzGQuw1BIQFoMYMQ4Fof8oMhESI0lPUyb0DepG8dFghkVwR2LuCLFaI9OS3aE95JlgnjCNaUqBsE2+fHHCaTF0sA9IRUQGXGOSqQw4oTGixTFmnfuUR+dKbuGTJn244/x8gCmQIv6WLgtdNz2/Ir6zDMGni/sfHFJOhA9EUQBlltrdC3uguTJkuOBK6LQT/AJcJFmAQZblGtDv4EwMPqMDpiP/oitMuQrzTgG+l5AOR2BIgypN+EFElIJXtHDJwEp+cRw1lQRahaYJRHHTFrikocLohiamnNF3k7gB98nGb9j5lEDJT9ZKzQ0mwV295M1xQ4pgndHIAO1O+zFNMuEajNH5ShUFMNiwsakvoe65t4hqbFK1c7SfQ0dM87LCnOh4GzgBwFl5iv4vvhv9pu5DXaBxyltMlYnpO4YSLWEKQrzkLtDZtKL+Esx/nI/YrLYUPPV2JR0qsrbmyurO71VbFIa68A3aV8olA4ozwy5zZQmHd8n0yr9mZDi9r7i6d8nLP8+YfknPGFJsl0N17oc+pSZi2zjcrdJlvnZ0tNXXmOhNP5ye4v696V/d4c/x8WYmHs+4k6v9oDlAaXjdDrzviZJoS2TwnpM0YH/UJ3ovKZf61nLI4ovXvJ/gf7/h9cpzzNl+iLhC4x53cclz9M7eTDwWhR6rbckjyifWwHy+hR6/Schz7bp1bn0Si86nm3Al5Hq//mW4xGTZuqUXmjKX/9I47E5S5+dvNi4v81bjMf20eQVyhf42nfy7uIRkNIXKfcgneE/JEOUrPZnLHwbA0Uk7w/8O64LYbbVwtOKmQP/9dUD6+7uf3Dw4XQ=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Trades"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/trades"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all trades and can be used in streaming mode. Streaming mode allows you to listen for new trades as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time. When filtering for a specific orderbook, you must use use all six of these arguments: base_asset_type, base_asset_issuer, base_asset_code, counter_asset_type, counter_asset_issuer, and counter_asset_code. If the base or counter asset is XLM, you only need to indicate the asset type as native and do not need to designate the code or the issuer.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"offer_id","in":"query","required":false,"description":"The offer ID. Used to filter for trades originating from a specific offer."},{"name":"base_asset_type","in":"query","required":false,"description":"The type for the base asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"base_asset_issuer","in":"query","required":false,"description":"The Stellar address of the base asset’s issuer. Required if the `base_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"base_asset_code","in":"query","required":false,"description":"The code for the base asset. Required if the `base_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"counter_asset_type","in":"query","required":false,"description":"The type for the counter asset. Either native, credit_alphanum4, or credit_alphanum12.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"counter_asset_issuer","in":"query","required":false,"description":"The Stellar address of the counter asset’s issuer. Required if the `counter_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"counter_asset_code","in":"query","required":false,"description":"The code for the counter asset. Required if the `counter_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"trade_type","in":"query","required":false,"description":"Can be set to all, orderbook, or liquidity_pools to filter only trades executed across a given mechanism.","schema":{"type":"string","enum":["all","orderbook","liquidity_pools"]}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"base":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"counter":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","base","counter","operation"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"ledger_close_time":{"type":"string"},"offer_id":{"type":"string"},"trade_type":{"type":"string"},"liquidity_pool_fee_bp":{"type":"number","format":"uint32"},"base_liquidity_pool_id":{"type":"string"},"base_offer_id":{"type":"string"},"base_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_amount":{"type":"string"},"base_asset_type":{"type":"string"},"base_asset_code":{"type":"string"},"base_asset_issuer":{"type":"string"},"counter_liquidity_pool_id":{"type":"string"},"counter_offer_id":{"type":"string"},"counter_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"counter_amount":{"type":"string"},"counter_asset_type":{"type":"string"},"counter_asset_code":{"type":"string"},"counter_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_is_seller":{"type":"boolean"},"price":{"required":["id","paging_token","ledger_close_time","trade_type","base_amount","base_asset_type","counter_amount","counter_asset_type","base_is_seller"],"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"Trade"}]},"examples":{"GetAllTrades":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/trades?base_asset_code=USD&base_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&base_asset_type=credit_alphanum4&counter_asset_type=native&cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/trades?base_asset_code=USD&base_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&base_asset_type=credit_alphanum4&counter_asset_type=native&cursor=83056000260648961-0&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/trades?base_asset_code=USD&base_asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&base_asset_type=credit_alphanum4&counter_asset_type=native&cursor=82854686553571330-0&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GBCHK52UXADCQCO7FBA5VBYPGCJFXHCNAVJTMUEKOCCNKJH5F35UZU5T"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/82854686553571330"}},"id":"82854686553571330-0","paging_token":"82854686553571330-0","ledger_close_time":"2018-08-05T00:55:34Z","offer_id":"23074703","base_offer_id":"23074703","base_account":"GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS","base_amount":"22.9174941","base_asset_type":"credit_alphanum4","base_asset_code":"USD","base_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","counter_offer_id":"4694540704980959234","counter_account":"GBCHK52UXADCQCO7FBA5VBYPGCJFXHCNAVJTMUEKOCCNKJH5F35UZU5T","counter_amount":"97.9999800","counter_asset_type":"native","base_is_seller":true,"price":{"n":"106905209","d":"25000000"}},{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GDURV3I6U5OTUV75WWAG2HWZTQHNMCR3NR2P5GPKDCIS2AEWCFSOLVFU"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/83005225157287937"}},"id":"83005225157287937-0","paging_token":"83005225157287937-0","ledger_close_time":"2018-08-07T02:01:53Z","offer_id":"23400441","base_offer_id":"23400441","base_account":"GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS","base_amount":"1.0000000","base_asset_type":"credit_alphanum4","base_asset_code":"USD","base_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","counter_offer_id":"4694691243584675841","counter_account":"GDURV3I6U5OTUV75WWAG2HWZTQHNMCR3NR2P5GPKDCIS2AEWCFSOLVFU","counter_amount":"4.3080953","counter_asset_type":"native","base_is_seller":true,"price":{"n":"430809521","d":"100000000"}},{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GBNDB4UHLDRBLR35JNU4ADYG3J5WA4LJZOPBXMNHZKTKSL37BDX4UBQY"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/83056000260648961"}},"id":"83056000260648961-0","paging_token":"83056000260648961-0","ledger_close_time":"2018-08-07T18:27:33Z","offer_id":"23400441","base_offer_id":"23400441","base_account":"GD47M25MLSCSYP4SIVNQXVQ4KWNLVGXS4S2AXPTYEJK6OY4VALJWK4BS","base_amount":"1.0000000","base_asset_type":"credit_alphanum4","base_asset_code":"USD","base_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","counter_offer_id":"4694742018688036865","counter_account":"GBNDB4UHLDRBLR35JNU4ADYG3J5WA4LJZOPBXMNHZKTKSL37BDX4UBQY","counter_amount":"4.3080953","counter_asset_type":"native","base_is_seller":true,"price":{"n":"430809521","d":"100000000"}}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-data-by-account-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-data-by-account-id.api.mdx
deleted file mode 100644
index e3ce54b49e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-data-by-account-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-data-by-account-id
-title: "Retrieve an Account's Data"
-description: "This endpoint represents a single data for a given account."
-sidebar_label: "Retrieve an Account's Data"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlV21vG7kR/isDfkkcrLRuej0DAg6oHcsvOdvxa1vEMYxZcqRlzCX3SK4UnSCgf6N/r7+kGO6uLMVBe0377b7YwnI4L888M5xZiojTIEb3Yl9K19gYxEMmFAXpdR21s2IkbksdgKyqnbYRPNWeAtkYACFoOzUECiPCxHlAmOoZWcBW2VBkwtXkkTWdKjESxxQPMeLBojN3qkQmavRYUSTPjiyFxYrESHQ6HjWLaHakxliKTHj6pdGelBhF39A3ve3u/vPv/whQN4XREp5oAWSlU6RAW0AoMNAf30KIXtvpc1jJV3Y8yJIqFKOliIuaHWolRSboC1a14U/Hh+dXVxfvz3+4O9u7Ot3/8cfLveu3lx9Pzq9OL/768eB8b+9gfHB+cnb0t8M/vR/f7Z8cv9+7/uH9R7FaZetAn2jxX0ZIKRq+nlCPHDLn4Le6LZ2d6Omwoso9rm2tVg9sOdTOBgqs4O3uLv/btn7TSEkhiIy1RLKRRbCujZYJuvxzYLnlS0dc8Zlk5Hx7JkXUrZUZmoZe+rtardYuJ7lril7TjPZtT1Vm0paG7oc4v/rpJ1awSkoqiqVj8k0pWWeMRyLvOBLy5TPTVjnDmC+faLFiLMnPelY23oiRKGOswyjPS+f1r84OIoVoKQ5DJGPQD51npF/m67aVgwuKc+efBKf/2xonTWw8/RadR70k2F7rA/No4hKaOqZcn7R6RSY4lPb27nB3+AeOr6kq9ItnKai9m2lFAdDCye3tJexfnkJ0bYVrC7EkuGn96q0O4TSCtlMK3BKsAk+DBFxI0ulm7Z1qJCkoFt9S0RbkxPkKYokRuN9g0OTZtHQ2NBX1V3FGHqcEG5QDTwajnhGLs0xNnpWhlTRwXpONpFpHtss8QBNap3qH3jlPQ0g9hCPfiKPwWk0JCopz4g5X12202zcvvWOSBzD6iWCOxlAMGSiSZKNHo38lBfRFlsiAZUkDhkAcc2jIJ4+gz0Z0EJqi0hGiRxtQJqcz+KUhv+AUdcyFAg0Hm4Hz3NAIK6BZ6tHJj83brBS3OvQ2s37vTLjfTOjD6748Fc3IcNsKm3WZd27n0nkaWKdo53fFnk/2k+3NSbRQEB9RYCxnGkHeXZ9l/NZ6Nw/kkwVnCdwkobLG+ubw5/AfsVZOhjw6Z0Ie1FNgpB14YjolbdLxW/FFxwXrX7jGM9sY0AzmBJ6kqyqyio8SUGjZMGgbIqHiSxU+8TCgtCcZUw4lGhNSnCmt00YrgrZiCgpQunmCRFXa6hCJR6CW4omOPTZsgiGG154mLZlT/IfrSF/BgXHTZwzm8/l28GvJQWHcNMeBpfkgNHbAr1BJg+792EkTQXBcJiifpt41VoGzX1dDyx0vSx1JxsajAV1xzVOVMp8ypANU+Nl56J4OKJqq3hnCkfPA74yv2qrDwjUROhcZwM7emhpOEY9bGciS5BOw9Gb8bBKOGdpnAKY6lk0xlK7KOxzyqcsL44q8QkY65/LSkkL/dObaRvIWTcuU47vTw/Hj0Yfrx8PxX8ZnHy7H1zfDSu2kZB7QxHliWhQ01TYDHV8FmDsfS/CkY5pZ7TR5yU1CJxdJlq4dH5P3XLRw4dT3tAlQTjZV335G8ObNnEA5sC7yrO18IPCNtexEDyMntG1SCMwnhYaLabOHrJn25k3bHijUJDUas0iq093HGRqtUoCPL14+4sLwBHHuIBCP5pFLy0rytms5iqRratPhU3GT1lXtfEQbE/0Kl2A0GgttuB751gb5hluFwbVXocUpBdBMvbnNoEZPaqDc3K7J5ybbobo66iq1RLbZ3eSWxw3RTcASqQCv5/TKGNioO94PeHn5JN5hnR4LVvdJrLFjiohMRPJV+DC5aWm2MaptZjYJDdxk0LGxm4tRprm4m/B7tzfpfsSFmZIvsq9Gwe3BjyrU6ZSMcX/ePFtlwmhJNtCGrf0aZUnwdrjLS4Vi7k40+fXJoD15ttg1G0ynKaZOacjPTt+NL27GfGVYxsrw2iJqF2KFdsNkP5lzQ+1m81cB0nT+1XSxfF4a/se1slsWIn2JeW1QW0YjBbXsJvz7foPkXWW0tU2q1rURb14PmShdiCy/XHKTuvNmteLP6Z0Uo/uHTMzQayx4nr5fCqUD/1ZiNEETvl7PNkN8fd0tVzvwf1tLvxl49xEtb5L9FiSytFpubdK8d3yn//9u6fwOp/jv6mGViZJQMT/vl93JvpRUx407L7ZL3nPWW93x+FasVv8CDuH1tA==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Data"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/data/{key}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents a single data for a given account.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"key","in":"path","required":true,"description":"The key name for this data.","schema":{"type":"string","example":"config.memo_required"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"value":{"type":"string"}}},"examples":{"RetrieveAnAccountsData":{"value":{"value":"MQ=="}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-effects-by-account-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-effects-by-account-id.api.mdx
deleted file mode 100644
index 075a58d0a6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-effects-by-account-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-effects-by-account-id
-title: "Retrieve an Account's Effects"
-description: "This endpoint returns the effects of a specific account and can be used in streaming mode. Streaming mode allows you to listen for new effects for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time."
-sidebar_label: "Retrieve an Account's Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXOly2zgSfhUUf8wkUzp46K6a2rVjx3bi+4rjjMsDkS0JYxLgAqBlr8tV+xr7evskWw2SEmUxjnMozszIf1wScXQ3vj5AQN+dpelQWb0P1orvi4RrZV1UrACUL1msmeBWzzoeMUWAB7FgXBMJOpFcET0CAoMB+FoRMSCUqBh8NmA+oelIhPKA+JSTPpBEQUAYJ0pLoBHjQxKJAGrkaOYzoWEoxorcioRoQUKmNHAyEJJwGE8mw88aRZrMY4S5JVQCoUEAAXZG8Y40hCGVJIRgCLJGtgbEp2FYJkqFbArJ/i04GbMwJEpTqQnVqZZUhgyUJldcjHkmB0l4CEoRSvxEKiEJU0SBruDQ4xHzR8SnCgjTxQEHUkREj6jOOtXI6i320igGTpWNdU3DBFALLsYVYw60YyrxxA6+BKohIIpxH7CRJBL+laCgmkVQsyqWiEFSXMWtwOpZG6DX076rt9lqbwVWxYqppBFokIiDO4vTCKyelVn3kmEThjiIqR5ZFQsnYRICq6dlAqVgyfr+7z//VSRO+iHzyRXcEuC+CFLrU9KnCjwXlULlJcQSFHBtxEXZlT+CiFq9O0vfxihQ2tKqWHBDozjErzbWdg4Odt/sNE622wdbK63WfvvQ3T/f3DnY2n13vrrTbq+ur+5sbr8+W2u+WT9Z2dx40z5svDm37u8rE0VTm+dK/isBeTuj5YCGak7NFcKTqA8yXU3jGQoXrOAGofCNMqm6vghD8M1nMSASVCy4AmWchKGVDC4zgACJ6ZDx4aUWV8AzOBgnk+ALGZTah3ENQ5BFA7VadqvltBvtTrfZdexmUW0hA/h8rQNQbMhprgeKagaawj6VUBE1EkkYEBrHQGWN7JkxFGHcD5MAyO9U+b+TF1T5wAPGhy+JkOR3nO538gL/ZV8br03dXQ6TCLgmTPH//ee/OnM3TQIY0CRM7W+G/QR8eBJhwKPKt1IFrYuiYUIWMf2ZhjkeAYnoDYuSKAeGWeXUFGnIhKBGsJ0Z3zi0pHwI6Zo7KLxr26RKKCdJHIPMGhqAMUVGVAYT98mDFcbCGORAyIhiFJBAleDqEaPlCwjBnO0c+6m4cuz7+4uKdVNVSRwLqVV1Ek3zqDBBOI7k2jb+m7XZUeL7oJRVsXzBNXCNTWgchyz1m/ofCtvdFSSiYbg3MEEqk030/wAfFyuWGOs0S+e7DBm/UgUdPtJOQTj4dKuRhEEZkIzVtUEMv7LuK5aGKA7RtIXWfSFCoBwjTgFEH9JBLyqWZjqEwhgcbvQPJlIs4fqHEukem+VfbZulRv8VHP7q6NCSckX91IN+KMmyquQHk0phjIHgRxMrluBDAD+WWA8aGfTPIm66ygXLFrS5uK9YLCgTN5+JBUb9QnEz33oW5pcqTRODJCzTrGIpkUgfLrOSs2zymGoNElPOxoeV6rld7V7cNZv3BbFoEEhMRTi16fxY0ZnW3ZMJsz6XrNArLQGKvez7StYxuKQlUj5QekTVqLSR2Ueg8fo0xIxf2miQcKztvtYU38akD2DF0h1HAQAfXe65tc1WZ2LwGZOWGLDEXBPjTNUrOMIrM9zKZGU/mUkg6gPuOD/tyFktWGhIpaRYWjIN0RMiwTJrLbPWMmsts9YXZq2Y3uI+sDRdTVX4FimKKgX6slyiyWPcyeLjfDOOrxSuIY3oAdOXNIxHlCdRY/4rxzVLlo7DlEq+QarDPfjXL4L4+pQblcPhebNoYUUzUxllJ+Je3M9uyfYnWFsmtWVSWya1ZVJbWFLTo8sss13ic19fogUwlTxtX+Z+h6RX+eosl2fLj0z7d0mClfQI6ou3UH/+RTJpNnezj5spAKVZekpzGbFyx85Hebxam2n1UQ1nWn0bRZ+z3ikpcSr56ees8edNfVEsg/QoK4WOTGw6nISmZV20rIuWddGyLvqOdZECHjyxKHK8ZVW0rIr+PIv0xKooaxHRm2VBtLiCaN6Mj5VER2lUWtZDy3poWQ8t66EF1UP5XdYI5PCpb4Y636oG+kZaMv7VRcTzHiJMehpNCljOztt30sW5uEdMZstgHOoQtGRwDSs8v6O+Po1c5m7sbIrIk0DqiNZI61j16vVRemeyqkFpDrqm0tvhNSGH9Uw4Vd94tbvdbG69Od50N8/c1ub27tbG+zX3zdbB9vHqysG2d3S6v3u+0to/e9veXTndPGm43ru94/V65mb/SG8T//qTubz5q2P/ZK7H/oqXTQu3+55TNKfR9pp2o+N1Wnan1XWaTtX5iLj5zb9nFdexW92GbbcbXsttdj23Oy+uucSL8J65kDG5cvGhiI7JnfjPVGzST9XnRXqYuD5j3FzdqSY/PaL5w1T0xRPRT82TJQbLLnls53/OwwjSs0pHK4RB60uBkcecaTjPQs40CvXs2ZhtubbTrdrdquMcO17PafUajfOya0E9y6llKplq9C8CF+87wcV7Ily8J8HF+8ZwwQvvIEvQ4jwRLmNgw5G2ek7FSn/NcnkFt18nWjrA4rHm2d8Fa55ddb8H1tJ5Poo1z55izf001sxoCwtNAZtFm/s0sBXfP0zfuuSvNSyv2ay5XbvR9rqLQE/TazacbttttzzX6zScBaHn4TSLSmxl8xTQM/f48cRWMtrzosdxqk7n2On2mt1ew34CelqdTq1ht5qNZmMR6Gl7zVbDtTtes+m5HXtR6Hk4zaLQUzZPAT1zjx9HT8loz4weF9Fjd3qu1/OaT4w9XqfTbnY7i0BP1+t2O57neHbHcbyutyD0PJxmUegpm6eAnrnHj6OnZLRvix4tE6VDxqGkUHLnCyXXriKE28eu3XO8nuvO4afkoKD41tw6OVqzHh4DWBtrJ293Nk421s4P3rbeb75faZ63Vt67G42ztaPz/aNz7+hd82TXWzk83dlrHRwdrr3bb77fXj+zKtnvNntW13U9r+3aXqvTrDXa7eaCivoHK9L4PnBtfCe4Nh6Ha+Pz4NpYAFxpUHj/1PO8p0FUQRimSHu109g/bp2tna++29tb3107ar3eO3HdjTcH22/2T92NV+3Tw9Otrcbx643z1RXv/Gx3p9k8OsWf1Q8GIC+NZZxGu+U23UbXvCILg8n5k9X0ujXbc23H7kyelYbXvkiGIz3t6Lm1TqNrt1y78PATjjXTbMa/Zp58vZv9hfxoQZvjsnme5Eelm+OS0X40P1pdO3277nkbp6c7q2dnbW9vc2v1cL91uLL5dnPznbvf2D84PW2d7O69PXi1d3bS3tg92WkcbM37kdPpOM6cH3WajVq36bVbHffz/Kjp1uyua7vNzt/Ej3Bn63jNbtd12q1Wc1F+9GCaRW38y+Yp+tHDx49v/EtGW0zxHUD/Qe39uEN5bs/rPHvtNPW2Rq3bcOxOexEV/tzBw2IgWnK+sRCIls4zhej840dLprLRnnF/6DpV26vaLXy74LZ7nveE/aFdy9W7T38SZC7mwI0GrhAB5iQmffNZSh1SyU/zkEIECUYi0COB1hzC5MZJz5qeMd1NSYru64WDbpDXOZtRIsOnLbRVxulynLYju6DHQl4ZnygfcZDoRMJTxnydtyQ8H/UCD0UH6fFudiiaMbygTUCqtLdds2smQSZRROXttBWJpbhmgaETIpvHx/tkZX8LKV0CqinyxRTZsLJZa2RLE8aHoHTKQiShagyXUnuZnrEUQeJDQPq3ZUOkzEZ4r2HCUgNUMWRFEsQXXCUR5F3pNUg6BFIgeCESQoOhnK+rwGRTFZIBR3orI8gsPZRK+cT6txOBXgkJyK7DlNG8oEdfsmAIpA96DMBx+lTb2Z77UvxhSLVCdgVkjCRhWlVIAD5wLWnI/g0BgRt/hIw9qmJGMM5A0uhrJJqw8mhBVNI35D3Tc3BVIYZMCJcoZy7Ljp8qyH2Us3tdA8/lKPY25FKTnrU5ZP3dkfChuKAXL3L3DOAaQsxBaiaoZ2LXfSGhykUAL/9W6PmN/8bz6TKGPmruekBArhkl/snhdgU52qQYK5BmBsEhZ/ya2Ppo7a36pK0D4au6FiJUdRVcKbS0IBIQTinnncCbHjdM3+L4hscuTg1aIWMwJFpRBDwwPHhoKMpxYsK40kAD7BTRKySRC5hEZj5cQ+T5U0ZPs6zDhAVAUo/pgyIjMTYmCSLGkWVQkhziBo65bXAKw6v1QsIgBbPRf22i6c9kNRTDqQ3G4/Gs8pOW1X4ohnVa5TCuqoRXMQuNoJrlj5eGyksJdBPqXw2lSHhABH/oDSl2pD9iGnydSBoSFqHPQ2RWXmS8XxH9A3kE09RB+kkUv6yR10hTyNN7aPg17YsEKcCMiGjAbL4JNEQASNNXIf4I/CuCrYv6G2KxDTTt1ABDpkdJv+aLqJ7ZoT4U9X4o+vWIoqXr6F7MB5WnzjoSjElOwxQpGydba+uXr/cOL9fWT9e39/bXD49qUfDSLOYqDIQEhEUfhowjhdnPioyF1Eg8x7SpNTMuRQwSzIgI/kikvGlGenRasiuCLwkTJBC+IVQzFuyRX34ZAwmQqFEjRaaQCohMOEchcjPigqZBiiIPJA9oiM5UjCETpP3ySxoewNAI0jC8NUObvpfXNGSBUfByLvMBOoYEoseCKEBKR42uxX2QPAs5AfgiicPMPhEGaRZhDUa5NvDrC2PGkNE+C9EfsVcBfLUZx0DfiyinQ1CEIfTGvEJiKiGoBsiTmYNPDGZVFbFmkQmJOGfWE0MeBkQxIBx3A+TFGH4OQ1LwO2SzQ77N36xXNDbJAof7zZrYDiGCNS3ISO0NjlKYFUq14sqaRlUxqGZozFjoqG+uZ2VMgLnYRbi/Rsek2d3K2VJwtvCDiDLzFMJQ/LP47B7fVfvAFRTmWompPwLi1vCtHwsQuwNmtnXpk2r6ZDpjFmyoeWp0ygZV9e2tV+u7R+vYpTbSUWh2JbFQOqK8MGV+rw4Danaz7mdF1idl9EyBcTdl6VsSwv5pCWHzl35wo+txSJm5jmswdZftrj7k20REQG+GBDbfYF1UrJFQGtve3WF+OJHh/T1+nbJl4rYrYIr2w4/xZRbB9PxMqqVGSbepE27YbGOa3tj5HOX+NISpj1ghp4r9QiP8hchRHzFSThs7NdIFfpAMrfSZPvHiMLum/ZJ8Mz7lUtHzN0P8tih5rlLB+82l7BFQwys3eYuz4vsQF5Weo2+deYuzsX5s3d//H934HKc=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the effects of a specific account and can be used in streaming mode. Streaming mode allows you to listen for new effects for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"oneOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"create_account"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"starting_balance":{"type":"string"},"funder":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","starting_balance","funder","account"],"title":"CreateAccount"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_receive"},"type_i":{"type":"number","example":2},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"destination_min":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","destination_min"],"title":"PathPaymentStrictReceive"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_send"},"type_i":{"type":"number","example":13},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"source_max":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","source_asset_type"],"title":"PathPaymentStrictSend"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"account_merge"},"type_i":{"type":"number","example":8},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"into":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","account","into"],"title":"AccountMerge"}]}]},"examples":{"RetrieveAnAccountsEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/effects?cursor=147350483860869151-1&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/effects?cursor=110694007436259329-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259329"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259329-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259329-1"}},"id":"0110694007436259329-0000000001","paging_token":"110694007436259329-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_created","type_i":0,"created_at":"2019-09-11T13:16:44Z","starting_balance":"1.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259329"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259329-3"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259329-3"}},"id":"0110694007436259329-0000000003","paging_token":"110694007436259329-3","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"signer_created","type_i":10,"created_at":"2019-09-11T13:16:44Z","weight":1,"public_key":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","key":""},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259330"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259330-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259330-2"}},"id":"0110694007436259330-0000000002","paging_token":"110694007436259330-2","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_credited","type_i":2,"created_at":"2019-09-11T13:16:44Z","asset_type":"native","amount":"355.2904739"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/115354197276323841"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=115354197276323841-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=115354197276323841-1"}},"id":"0115354197276323841-0000000001","paging_token":"115354197276323841-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_credited","type_i":2,"created_at":"2019-11-18T19:59:40Z","asset_type":"native","amount":"688.4065454"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/117356420835532801"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=117356420835532801-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=117356420835532801-1"}},"id":"0117356420835532801-0000000001","paging_token":"117356420835532801-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_credited","type_i":2,"created_at":"2019-12-18T08:23:35Z","asset_type":"native","amount":"355.3887598"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/119399833130811393"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119399833130811393-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119399833130811393-1"}},"id":"0119399833130811393-0000000001","paging_token":"119399833130811393-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"trustline_created","type_i":20,"created_at":"2020-01-17T20:13:22Z","asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","limit":"922337203685.4775000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/119399833130811394"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119399833130811394-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119399833130811394-1"}},"id":"0119399833130811394-0000000001","paging_token":"119399833130811394-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"trade","type_i":33,"created_at":"2020-01-17T20:13:22Z","seller":"GCM4PT6XDZBWOOENDS6FOU22GJQLJPV2GC7VRVII4TFGZBA3ZXNM55SV","offer_id":"147625249","sold_amount":"539.0320108","sold_asset_type":"native","bought_amount":"32.8490620","bought_asset_type":"credit_alphanum4","bought_asset_code":"USD","bought_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/119399833130811394"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119399833130811394-3"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119399833130811394-3"}},"id":"0119399833130811394-0000000003","paging_token":"119399833130811394-3","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"trade","type_i":33,"created_at":"2020-01-17T20:13:22Z","seller":"GBDVKE33GVVMBXX73OHIBRP6RAHKHHW2P4PQVV6UNOKQCOXU7GNUM4QI","offer_id":"147618811","sold_amount":"854.9537682","sold_asset_type":"native","bought_amount":"52.0920258","bought_asset_type":"credit_alphanum4","bought_asset_code":"USD","bought_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/119400713599217665"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119400713599217665-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119400713599217665-2"}},"id":"0119400713599217665-0000000002","paging_token":"119400713599217665-2","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_debited","type_i":3,"created_at":"2020-01-17T20:32:38Z","asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","amount":"84.9410878"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/147350483860869151"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=147350483860869151-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=147350483860869151-1"}},"id":"0147350483860869151-0000000001","paging_token":"147350483860869151-1","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"account_credited","type_i":2,"created_at":"2021-03-06T19:27:33Z","asset_type":"native","amount":"0.0000001"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-offer-by-offer-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-offer-by-offer-id.api.mdx
deleted file mode 100644
index b83e053600..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-offer-by-offer-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-offer-by-offer-id
-title: "Retrieve an Offer"
-description: "The single offer endpoint provides information on a specific offer."
-sidebar_label: "Retrieve an Offer"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWVtzGrkS/itdesmlBrAxkISnY8c28caxHWM7iR0XJUYNo1gjTSQNxEvx30+1hoHBJhufrfOQrX2CQn3vr1vqZsY8HzvWvWGnoxFax24jJtDFVmZeGs267CJBcFKPFYIhEkAtMiO1h8yaiRToQOqRsSknBjAaOLgMYzmSccFRZxEzGdpAcCRYl/XQB3V79+HjSLCIZdzyFD3Z0L2ZMc1TZF0WBAwkEUiyJuM+YRGz+D2XFgXrepvjQ5N3Idfye44gBWovRxItjIwFn0hXmjS/JSkuM9qhY90Za25t0ce6pH4ex+gci1hstEftiYRnmZJx8KbxzRHdjLk4wZSHU6VOR8EFf58FF4bfMPbkoaUoeFnoGyip78K3v6ZzqEa/pkosVqmct1KPWcSKxLAuI21sHjGPaaa4p9AtqYfGKOSazefVyN4UQm8j5qVXWJGh8Yf/zUzKLE5+K5PmRFb+dBxSPY9+iQlMhyjEmtqfkFqMjRVV/HBr+T3Vicf0Cbj6B+OvaAopv0P7W1n2gChEbt3a23nEpNhkTilJigBnPpZ6PPDmDvVj6nlEstWa90tBGfceLTWv3s1u7Xqr9uZ21m7PKyq4EJaa2kIMsf0yitw59IOCZoM5xXFsxF8dS+fyTTY/jFtFVyXEe9zhLp2QwGF+/080m6cm136jrszKGAdPwHMVD1J7HKOtollqv9MkgeJJdJUmdUYWLE3ZaKTizg9SI+hKFQOFYrwWmA1q8kJPpVI2iXgk2st0swXFhf2EbMjiTVEpo2XRrGC/BNIyNatElHH4idcbLb6dr/f98Lphc6p6/MHTTBUpfPz86c7YhKsc1xtz2XqLFsYS7zPXbTQSY+WfRtc8Oq/R151HpbitGztuhGbjGtuddruzs/W6vaFd/g/SeBxTVFyj9/ZD6+yi83n/eu/T6enByX6/c3h62Wz2/vh4/MfZVbP39tXV+dXRUevisHe9t7tz/fnkQ7vdvwppoYa3NOhhb2MrU1ddjf1tfWstrVr9LLYopB9wlSVc52mLrZc/u+zvs4clz3r7l+8/9C57+9cf33e+vPuy277u7H5p9lqf9/vXZ/3rnf6n9uXJzu751YfTzsf++f6ns/aX44PP6z1qzQ7NvZxgtRuwZqe+vfWqvfP6NVtrBJp1t1utN9vtzqtmO1T061an1dxpdVZVyrZf1bebW29azZ2fQbXbfN3abm61mpurTOdKzecL5KboE0NP9DH64jJJWJeVsJqVz/F5CLSdlK/13KqnQYptGi8uCjo4QT819i48lDZLHOU+t/gUmYclJehS6i3NECMTeseiQN8VclnEyJWCe6u+Vd8m//I05fZ+RbUaeLiGdxcXZ7B7dgTegOCeg9TgE4R+YVeptQ5HHqQeo/PEJsBiLQTOBerAmVkj8hgFDO83iSDJnOaXFHzCPUgHyB3NNN5AbLTLUyxZ+QQtHyNURhSwqALkiJxoMrShPesYa8ZK1B5FYYjFzKJD7QOjg9wVRpUGvTUW63BBUxR5XvFjaKUYIwzRTxE1qS+8Xec8s4auNAdK3iFMuVLoXQQCY9TeciX/RAH4I044BSwKEkLtQFGQwSIos+ENuHyYSg/ecu14HIyO4HuO9p5StOheMOSKnI3AWHDeIk8BJ6hLO6rcJHTFWX+ErH87Em6qCb19XpanwAkqeqS4tetjYXYjNhZr2gh88a9Cz1f9VZfqYq5hiHSEjmI5kRziy/PjCDgMrZk6tEGD0bRmCVFZxrq//979MtbCxK7hjVGu4cSdo0gbsEhwCtJiQ8+PH9Lfk/x7k1tCGwU0gikCjZNpilrQUQgU16QYpHYeuSCmlN9JPQYhLcY+5DDmSrngZ0jrOJcCoaiYITpIzDSERKRSS+fRQgnxAMcyNqSCQgzPLY4KMAf/95eePoM9ZcarGEyn03Xnl5S1oTLjBq9pnNZcrmt0CyVYW9wfL8IayBkqEx7fja3JtaCV1YNqKLBj40R6jH1uuQKZUs1jGjIfMiQdpPybsbC4OmCYp9mLOhwau7YR40OTe1iYSAFc6FtCwwgccocRxAnGd0DUVf9JJfQotKsAjKVP8mE9NmljEYfG2DSGygwbKadIN6i8ZIyuvDob9Di3mqsCKb3Lo/2DweHp+WD/4Org+PTs4LxfT8WLkMw9HBmLBIshjqWOQPpnDqbG+gQsSh9WeXocrKQmIYOJGCcGRdn9bqho4cSIv9MmQJg4T8v204WXL6cIwoA2ntaPxjoEm2tNRpRhpIQWTYoD4UlwRcVU7SFLpL18WbQHDItKrtR9EB14BxOupAgODh7dfEiFYRH81IBDWll6Ki0do9WLliMwNnmmFvFJqUnLNDPWc+0D/IYmhFFJPpSK6pG4KuCrrxUG1V7KNR/TnpWgN9URZNyiqAkz1UvwmdG6qybzMg0tkXQuOKnlUUM0I9CIwsHzKT5TCip1Jx1wBxy+src8C5cFifvKlrEjiNA8hzZ1p6N+AbPKU62a2UBUM6PaAo2LPSqPwwy8WPGWZlfhfkiFGZLPogdPwfWHH6ZchlNUyvynekYzpYxRO6zo2s14nCA061u0KFtuh5cnteJkpXHRbHg4DT4thLrG8dHbg5P+AbHUE5+qMOtkxvmU64rKc/RW4iQ01GIefPComK12y/+nZfti0vD4wzcyxaWmYASfZosX/U0xFNJiu7tcsd9GLDHO0+lsRh3p0qr5nH4OlyLr3txGbMKt5EN6PN/MmJCOvgvWHXHlHu7hq449P1/M5i/gKdv5n/hQbjo17TkXAzNjEbvD++p/BWHgTpALyuzNbHG8G8eY+Qrjoz0+TQjLAah3cMHm8/8CGTHCig==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Offer"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/offers/{offer_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single offer endpoint provides information on a specific offer.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"offer_id","in":"path","required":true,"description":"A unique identifier for this offer."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offer_maker":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","offer_maker"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"seller":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"selling":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"buying":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"amount":{"type":"string"},"price_r":{"type":"object","properties":{"n":{"type":"integer","format":"int32"},"d":{"type":"integer","format":"int32"}},"title":"Price"},"price":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"sponser":{"type":"string"}},"required":["id","paging_token","seller","selling","buying","amount","price_r","price","last_modified_ledger","last_modified_time"]}}}}},"title":"Offer"}]},"examples":{"GetOfferByOfferId":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/165563085"},"offer_maker":{"href":"https://horizon-testnet.stellar.org/accounts/GCM4PT6XDZBWOOENDS6FOU22GJQLJPV2GC7VRVII4TFGZBA3ZXNM55SV"}},"id":165563085,"paging_token":"165563085","seller":"GCM4PT6XDZBWOOENDS6FOU22GJQLJPV2GC7VRVII4TFGZBA3ZXNM55SV","selling":{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},"buying":{"asset_type":"native"},"amount":"26.1075388","price_r":{"n":1449156725,"d":84642346},"price":"17.1209423","last_modified_ledger":28412042,"last_modified_time":null}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-offers-by-account-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-offers-by-account-id.api.mdx
deleted file mode 100644
index 287c6e2cb4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-offers-by-account-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-offers-by-account-id
-title: "Retrieve an Account's Offers"
-description: "This endpoint represents all offers a given account has currently open and can be used in streaming mode. Streaming mode allows you to listen for new offers for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time."
-sidebar_label: "Retrieve an Account's Offers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWulyGzcSfpWu+REfxVs8RFaldiXrtizJknzJVsngoMlBhAEmAEY0o2JVXiOvlyfZaswMObRo2c5mEydZ/pHIARrdja/vuQ0cG9tg8DbYCEOdKmeDy0rA0YZGJE5oFQyC80hYQMUTLZQDg4lBi8pZYFKCHo3QWGAwFjeogGVUIGIWwtQYVE5OQSf0SHEImYIhQmqRg1BgnUEWCzWGWHOswdnSd6KvJxamOgWnQQrrUMFIG1A4KQ6mr44YLE5mFlyEU2AGgXGOnPa6COHMoZTMgEQ+RlOD/RGETMpVnFRgTxvxk1YwEVKCdcw4YM6TQWakQOvgWumJytiAVEm0pIUwNVYbEBYsugpRnkQijCBkFkG4Mr2R0TG4iLl8Uw02p7TLERd0Uk7rhskUSQilJxWvDNJixnChhdAgc8jBChUirTFg8MeU2HQixlpQCXSChtGN7vNgEOyiO/ZbN6f5xe/zoBIkzLAYHRqCxG2gWIzBIMhVeyVoiSBIJMxFQSWgM4RBHgycSXElbvK9v/78i4UkHUoRwjVOAVWoeaZ6BkNmca1FIpHoc4B5bol1G0YYs2BwG7hpQgxlK4NKgB9YnEj6aXfr2fPnRwfP2i8Oe8/3N7rdk95p6+Ri79nz/aNXF5vPer3N7c1ne4c7r7c6B9svNvZ2D3qn7YOLYDarzAXNNF4I+WOKZrok5YhJe0fMDVBpPEST3aU3EkvXxcAmGIqRCEHq0AuTiRtqKTH03/UIDNpEK4vWG4ggLXlQ5vBASNhYqPGV09eocjDoETAwGGrDV+pHKIdjNGUFdbuNbrfZa/fW+51+s9Epi60Nx6+XmqMVY8UKOYhVT2gB+oxDCzbSqeTAkgSZqcGxp2FBqFCmHOE9s+F7eMhsiIoLNX4E2sB7Ou49PKQ/+c/eZDNbN+M0RuVAWPXrz7+43NgccByxVGb692Q/Ax+VxuT7mA2DTMDgsqwYKWLhvlIx5xFCzD6IOI0LYPhbzlRh0KVGIa8BrfP0vTkbpsaY3XmTmG81GlAFpiBNEjT5Qg8wYSFihs/Np/BU5AgTNCNtYkZOwCCzWtl7lFZcIPI7ums2vhRXzcZsdlkJPlRtmiTaOFudu9LCK8wRTpRajQb9WdbZWRqGaG1QCUKtHCpHS1iSSJHZTf0HS+tuSxwxKY9H3knlvOnhDxjSZSWGXJ0T2XlXUqhrW5LhE+ssytHnV0UGR6uA5LXuPGLUdTCrBA7jRJJqS6uHWktkijxOCURvM6KXlcAJJ7FEQ+EH942xlBi8+aZYmtGy4qdDf9Vkv5/BBMZDpNTg86LkdltayIxh5AaEw/gLcPUXxp/PLa5ido3mm+Lso0Vec8vcXs4qgeCr2CkoCe7hXAqtd1fPKkRbLkk/J5Qw59CQ89p9u1G9aFT7l7edzqx0BOPckFPLyXiH+DktMmvRXWVrVrCTPSbXf89jYW26iueP9VY6q6TiTWZxg54QwWE6/SuyzWJKOVeelRgR4tUX4LmMh0XYm6NZKLfWIoL8i9aVnNQJcTBnZSWTkll3FWsuRgL5VVav3H9Mmp1TspRVJO6QptpgNe59wP6C2xBZ1VAyo7nRLGA/B9L8ahYXUejhE1Kv5Phytuz3fSUTzMjq87zEX+EpOiPwBjdUUdtmJQ8983n0sn8uPHDmyYLIucQO6vV3LsoyrKpD6xS6ms0KyZo243pe3tj67tbak4M3L84vNt50D57vtJ9s73cvei9fdY67L492n16cb755sf3k/PjgZHvrfLO339q7ODvZbz2tZxXcv7LS4/vvfKb3fbPxnc+lv6fMtJQK/Km8Nbvtfnut1ex+gskiOfizmex0Ov1W72MmfXZPqFmK/vP4/va/hkLGR33OwIoQ+sdqxktLYXDO0scRL1gwu4h1wW8+bynQlWNCQGXiDS6HlKUFoUEu3BWTScRUGreD5agRbG42g48jRbC71Tno7h3udLrd7uv2xsXh+c7568M37e5B5+xVb/v16dPNw+03Jwcna2tna2vPXl/svuw+ebVzVI4RQavZrvXps9YPluKDouIm+3g3v971/zcXrjto1JrNbqvXb37KfQ1a62vra812b7XnDVqNVqPaaFVb7fNWa9BZH6ytX/gE9nfDYmax3xQWM5ZWYTFn9n+LxT8cap+A/MImFljModhv3IHiWqvVavf7TQ/FVsdDsYTEZqu2vt7v97vt+6DYbzfb/c9BsXPe7Aza/UGnd0ExNf9QaHWoLHVuvLe8xmkwWF33V4rwSvU/dQdidJGmtuMYXZY7R8EgWKDqdtFhnOXY9RdobopOZGpkCaz3QDVY1Y85z9bBEbqJNtfewlZTHKUuNfglNHeKlaAKqpfUKRppnzXlqUnenSGVoLHZ7katUSOI2TSOmZkuVkFi9I3gvhUIe+fnJ7Bxsk/tGM4co15PuY2dn1qDfQdCjdG6rINosOoV59vg2c7EaJ6GyGE4XUUi60pSLjnvMCGzgjqaGkKtbBpjsZXdoGFjhFJzBgxKD+Wi0V7qQlW1EaioM+0ZWW7t2mwOMJzOGXqiDVJnTFgveUmOoRF8jDBEN0GaJSRJJu3yzhOjKZm3IMU1woS6+85WgGOIyhkmxU/IAT+EEXXbbMVT8DYJmaF7juYdNafBpkPfeDNMWeZbtrYCvhFIV1SMHIZMkrAV6lvmfXm88RMSz0d5t28Mz3fW7iDrn46Et+ULvXxYmCfHG5RUntmlsJSzXQ+1warSHB/9o9DzTr1TxXH5ZI35RipyuBEMwhenhxWarxg9sWj8CVph0a2f6/ps66n9rK65Dm3daS1t3fJrS5rWYJDglE2rNBVeH4SbEn0/gkoyhVZggr4BHseouJ9gkaKYooNBKOuQcdoUs2saAHFhMHT+DmlAZ72c/lrHqeAImcUM0UKkJ14lPBaKpoMGCoh7OBa6oSN8T/yhwVEGZi//1lzSB7Ap9Xihg8lksiz8fGV1KPW4zqoKJ1WbqipFoQirefx45NvwVpOZsPB6bHSqOGj1sTVk2DFhJByGLjVMgojJ5jH2N6/znn3MfqAJYBY6YJjGyaMa7NCAUWW1P/3Mhjql9r1nkRSYnzeHhuZII7YKhBGG10Cry/L7ocAuqXahgLFwUTqshTqu53qoj3V9KPWwHjPSdJ3MS4Roi9BZp7aEUUxmSNl9sb+1fbVzfHq1tf1y+/D4ZPv0rBbzR/4yN3GkDRIshjgWisYPDyxMtHE0NBLOTyrzKSg5CeFZxDDS2czDc09GC0ea/xY3AVyHfhjiNTiAx48nCJxGrI4m3dpYBJMqRUwUaqQLzZwUowmu4kySMZV9yBxpjx9n7gH9CJBJOfWk/d6rGyYF9wJe3Yl8SIZhENxEg0UaxzoyLRWiUbnL4RjqNJG5fmJy0iKmFIwp5+E31F6NUrChkGSPtKsEvtqSYZDtxUyxMVoQBL2JqkDCDPIqpwF3AT49WhZVJ07E3iXSmflOcnnkEPUIFCK38HCCD6SEkt3RJIom5e+CJyzxwYLIvQvmuiOIUCcLTWyPR2cZzEqpWvlm/aKqHlVzNOYTJBb6bkk+xSvYLsN9hwzTX35Q+SgVXE78MGbCP0Up9b/Lz6ibJkJUFktnbSQsjBBaNcrgBSfsjoSvILIn1ezJ4sTc2TD/1MuUE7X1w/0n20dn27SlFrlY+hoq0dbFTJWOLNpc5FDzRtcDC8dFFr2UX9wuBmz/f63jb/FaR15MOvzg6olkQhEuPbxu8zrrbfH+BqFhsPQuR15qXVaCSFtHS29vKVK8MHI2o5+zmTcVYFxYNpSfmnqXcfXnvw+xUidZvTp/wyOvUANfC36NcH+Z1x7u0ULxwsdvVMLf6BWHe5RUvPyxUNIlfTGCtPSVNvHwNJ+ZPILf7a2olawXQ2o1LXNeiFQyfj8tiZAREBbtnI0wxKQs9J2XMJbaObvb58Fs9h/Zz/MB
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Offers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/offers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents all offers a given account has currently open and can be used in streaming mode. Streaming mode allows you to listen for new offers for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known offer unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream offers created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offer_maker":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","offer_maker"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"seller":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"selling":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"buying":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string"}},"required":["asset_type"],"title":"BaseAsset"},"amount":{"type":"string"},"price_r":{"type":"object","properties":{"n":{"type":"integer","format":"int32"},"d":{"type":"integer","format":"int32"}},"title":"Price"},"price":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"sponser":{"type":"string"}},"required":["id","paging_token","seller","selling","buying","amount","price_r","price","last_modified_ledger","last_modified_time"]}}}}},"title":"Offer"}]},"examples":{"RetrieveAnAccountsOffers":{"value":{"_links":{"self":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/offers?cursor=&limit=10&order=asc"},"next":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/offers?cursor=164943216&limit=10&order=asc"},"prev":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/offers?cursor=164555927&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://\thorizon-testnet.stellar.org/offers/164555927"},"offer_maker":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"}},"id":164555927,"paging_token":"164555927","seller":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","selling":{"asset_type":"native"},"buying":{"asset_type":"credit_alphanum4","asset_code":"BB1","asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN"},"amount":"214.9999939","price_r":{"n":10000000,"d":86000001},"price":"0.1162791","last_modified_ledger":28383147,"last_modified_time":"2020-02-24T22:58:38Z"},{"_links":{"self":{"href":"https://\thorizon-testnet.stellar.org/offers/164943216"},"offer_maker":{"href":"https://\thorizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"}},"id":164943216,"paging_token":"164943216","seller":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","selling":{"asset_type":"credit_alphanum4","asset_code":"BB1","asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN"},"buying":{"asset_type":"native"},"amount":"24.9999990","price_r":{"n":32224991,"d":2500000},"price":"12.8899964","last_modified_ledger":28394149,"last_modified_time":"2020-02-25T15:49:57Z"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-operations-by-account-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-operations-by-account-id.api.mdx
deleted file mode 100644
index e2bc6bf98a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-operations-by-account-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-operations-by-account-id
-title: "Retrieve an Account's Operations"
-description: "This endpoint represents successful operations for a given account and can be used in streaming mode. Streaming mode allows you to listen for new operations for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time."
-sidebar_label: "Retrieve an Account's Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXftSG7nSfxXV/LGbbBkz9wtVW+czYAyJuQRzz1KsRuqxZ5mLz0iGcFJUndc4r3ee5CtpZuwZY5MAhpA95J8U1q271f3rlkZSf1U47jNl5bPSIiQdJZwp5w2FAiNZOORhmigrysEgZAgSOkzDhKMMhhkwSDhDbEQIMBaMIpQOIcOiPkNBmiGM+uEVJAjnnSKcUERwgnxAIwYUhQliPAMch0kfxSmFJurV/kY4itJrhm7SEeIpikLGIZFdJ3A9PRoXBI6HYogP4AbhDBCmFKhozweAehyiCGcoAtqHrIm2AkRwFM2ipoE20yz8V5qg6zCKEOM44whz2Q3gLAqBcXSZpNfJhBQ0SiJgDGFERhlLMxQyxIA3RO/Xg5AMEMEMUMirfQZZGiM+wLxo1ESrN6IVF5SI0Yq+rnA0AsFIkl43pFCENHOiq9IgGWAOFLEwISDqZSiDf44EuTyMoak0lHHtLaqsKB3gu+PmqzeFEmxRpaEMcYZj4JAJ9fiqJDgGZUUpxHwRiiqhUI8h5gOloYhxwgyossKzEczUoaLtf//9H4aGIz8KCbqEGwQJSWk+DRj5mIGhC9aECMbKJgkU5DMygBgrK18VfjMUBOU1lYYCX3A8jMRPnfXtT592Pmybh13n01bLtvecfX3vbHP709bO8dnqtuOstle3N7sbJ+vWh/Zha7Pzwdk3P5wpt7eNMaO55Esm/zmC7KbGZYAjdofNFkpGsQ9ZPqfSYJiYNozYEEgYhARFKcn1RbJL0igCIv9OA5QBG6YJAyYNJhRSkgpaqAmgIe6HSf+Cp5eQFEqRBgijDEia0ZnyCRMOfciqArJt1bY1x3Rcz/I01aqynWYUHs41BRb2E1zyIUiVHU2UP6eQITZIRxFFeDgEnDXR7jBX3DAh0YgC+hMz8id6hxmBhIZJ/z1KM/SnGO5P9E78V/wszTe3+6w/iiHhKGTJf//9H14YHUcUAjyKcvnLbr+hPskoFjiIGVFyBpXzqmCiMA75AwVzMAAU4y9hPIpLxZCznIsiAz7KEqBNJOrJ/qVZZzjpQz7nmiBeV1W0hHCCRsMhZEVFqWAhQwOc0bH5lKglQHEIWZBmMRZAkAFmacLuEVo5gUDvyE5Tv1evNLUqsGJKLwIcRkAfKLkecInbWQ57pXrkfVURL0yE1Qha7yqTbC0sSQ4xkws/TSPAyWT+JXjJ+rXZ/ysNk8eygBOGSU5ZhRVhI7WywkkUCA6YDMamVGNX/FICRVO5PW8oX5bYaDhMM86Wxn6shOExpAimdVUV/03RmXtxpaGQNOGQcFEFD4dRmAPV8l9M1PtaER6Oot1AeoVCjKn/FxBhHcNMEMvDfLyLKEwuWUXcc+oxiIJv1xpkEMyyXKnmXJpocqncNhQO8TASUpwx0be31Yn7nHd63lB4yCOo9JHAF/7KSBpmcPWqSLoV1cqfunKqhcmkCfzdtaNiuK+MMggCIPw7pPqiVMmVAtDXRtYwAwIUXhdZU5Wk9tc1bjLLFclWuDm/bSghnUVuOVJIJfuVaPJu7bqaX0wWe7M4aygsHWUELooYf9bgQ8w5ZMLldD63ls7UJe/8q2XdVsjClGbCFYmhZeP7ovzcU44HLNpchJVWecxVbaXeNoqG9ALPoHKK6QFmg5mV5PJNCM/HkQixZlYKRokIpp8qisWIdEqtwnyJV1GAudN9Z26L2RkLvCbSGQKcIa6xcCbsVQxhTXbXGs/sNz0JxD6Itf63DbkIvisVcZZhEc6FHOLvQII3r/Xmtd681pvXeqTXGuIbsfCe6a4mLCzCRWHGgF/MpmhcLLYORHG5+yH2cK4gR3Qa8gscDQc4GcXm3Z80XU5Z3k/I2GgBrk5sejx9EtKnu9x4tjr8WC9amdFCVJLZMbnnt/Ul2d5Y196c2ptTe3Nqb07t2ZwaH1wUnu1ClBN+ISQgXMn3rcv0F3B6jSd7udJbzhn2f8UJNvJvfo9eQv38kyTdbGlm88VEgfEw/yx2EYezDbvs5f5orVZrLoe1Woth9EfGOzNCnEb5ubku/LuiPq+GQXxQhEI9iU37Y2h6i4ve4qK3uOgtLnrBuIhBQr8zKNKMt6joLSr6eSbpO6OiokaMv7wFRM8XEN0V430hUS9Hpbd46C0eeouH3uKhZ4qHysPDMWT9790ZchcVAy2IyzB5chDxYz8ijFtKTiq6XHxv384n5/xW6GQxDdKg9oFnIVxBKynvCkyOjotyeR657iVKP5DbojLgfMhWlpcH+TnVJQ6MJ8CbLD+a30yz/nJBH1vutE53u93u4dZZ21w/215d1c9WP3ZWD1fPulu7p4f2yUb32HA6q3v60dm60VrdOVk7NlePWsuT45L/yA9x//6LPDP7u6b+Ik8l/y7O+FbO+P1g6jRd1TzTtG1LtTTH0wxnDr3lAcDXQK9umKag1TQ01ZqmV56eFmpeO5gxPnrx+YkqMiFp+S4tM3z9A7qunshdhkANQDUxMYhDwdF1l2Dd8lzXtVXLc20XU9Uium5i1dTA9XXqAejYxR6ltuuZU859URwul31OeekH9F/08I/JdP0yd3Knve6jh8H3j1J4QGVG2bTfm11nnuvLD0JPOzuls3q0cXDWtTa39g7MvY1PRwdnR1vH+45z5HSPT9dODs217unx8ebmbvtk1TZP9jpWd3374LDE3Dsn0CbuTK27LEVXdXVJ1ZZ070DzVkxjxfLOZqHzivJklZt1NE3Rm2r+b3Lu6kn8V4T4SFiRa40Fg4CjWram66qtegsEAaIR37XUwNQMMFXDJaamqz71fEyJ6vi+C4FrYdO2TQ+b1CIe0WywHBfr1FAt11skCFQ4fAkQmBLoM4FAbZQpEKiWzQOBep0XB4HyQM/E+rX7rd9cMew51v9kXatv9U02i/LNsydxmz7F2ifbZuIOyhiNFg8CpqVrtmVZqupqCwQBFWyfGGqg+3pgqQSr0hICC1u6Y6gecUzPNsGhGNuq5nqOTahObNcmFg1MH4wFgkCVwxcAgWmBPg8I1Eepg0CtbA4ITNV5KAg8Xq3LSGAg7uxd8GzEqkhg348E9oquzkGCJyvcFBLM2C2ubp0qh711ZXovWOmsH37c7hx21s8+fbRPN09b1pndOtU75sl672yvd2b0jq3DHaO1f7S9a3/q7a8f71mn3faJ0ihuS64onq4bhqOrhu1aTdNxLFd1JMcjxgGeNobsJM1eVxRiOo5nWLqlmZazyKUIMTXNtjzLpwF2iaYaHjFVHJi6BabnEE8LSGC4DtGxjlUSYC0w/MA2HcMItEBfKABVOHwJAJoS6DMBUG2UKQCqls0DoHqdnwaALGveQuSpCvdAANrp7BzMQKDW8e56a393+4NhHFmn6xunxs7e6cHm0emnjrP94eTog76zbrR2O1ubp/vHWzvtnt1aW9tbfxACPX6M14lAnurqqm67qmEsEIFcLdB913KIbzrUIbZBsKaDDsQwbTuwA83xTc9T/cD0dAgcSycesamuGhbBmhYEi0SgCocvgUBTAn0mBKqNMoVA1bJ5CFSv85MgkLOiaXMQ6MkK90AEah/uz0SgPavbPtg9sk+32rZ+2tq27N7Bemtnb3991znbWF/t9HY2P3zaOu10Pva2d89am7u7Pb33MAR69BivFIE8U1NVR7OsRSKQYfq6SwPX04iNVc+zXawHKrZ9U1MNVfVV11c9YgWWS6imB2CbAcWWR3XPdt3AhoUi0ITDF0GgukCfC4Gqo0wjUKVsLgLV6vw0CKTrcxDoyQr3QARaXdVmLcKsD/Zmd8OybfvEbJ11DzYOTrqnpv3B6h077ZP9j6vd9unehz3D6BnG9slZ58heO97Yedgi7NFjvEoAslRX7C+ZzmK/B2k6dsENNA3bngOgCqXQwVcdVSW672hGAKpDdS8IsK95que61PJ93XQJDjRPcxYIQFUOXwCApgX6PABUH6UOQLWyOQA0VeenASDDmANAT1a4BwLQ2s7prAhov93uHq6axtb+5nG71VvbWO1+3DzcX+tsb7atrQ37pNd22ifr3dba6WZnf3PbNPY3dh+2C/T4MV4nAJm6Ib7aGY6zyF0gw/Y94mFsEBPrOtbA1R0zsD1f8/2AUsuxTbAs31Vd1cQu9YjtGxbRTDA1Uwh9kQBU4fAlAGhKoM8EQLVRpgCoWjYPgOp1XhyAYpzgPlz4o5uLNAjkOarxRyn9fhRyV7R5X6WerHWVrz9G5Uv0MAvl12nNbWqq63qaVv54IU/pJsqK5hYlDYWK9+Xyf7cNxR/dCPF/C91q1errvFrRIpZ7DKLoDk3jL3ByPi6kPj3Hdy/LdjXdczxTNRf58TtQDVt3XYfqvue7lgGOb9qmrzkmpgEB3ySOEQS+jU0LNNV3iG/4QeCRALuqa5gLBZwKhy8BOFMCfSbAqY0yBTjVsnmAU6/zcwGOZc4BnCdr3ZzPzRPIUZuqaXmuZ9xBnPznBcJNsbE9D24evff8I+GmdlhxgXCDTUcNTNXHKtECqjnE9ywHVN80XJ+6juFrmhoEwtP4rmYY2NJMkwA2AgvbNlXp4uCmxuHzw80dgT4L3EyNUoObetlsuJmu8xMssHR1xdBWdHcO0jxZ4V7JAquKca9mVZU/RyMvhcEXDgnLD4p//qpcwo2yMvvZ2kZ5jFwokXjcNgY+SIWa9mF822lFmRxs/jp5kfy2YsYSIbOr8vXyURZ9nwkps95wPsjroR3g12l2KQF1do/BiI8y+J4+N8qaKCl7PRdn8oP8dkFxJr940VmIBTKWt1abalOT90jiGGc3k1pomKVXIZXPh6PNg4M91NrbEm8OU8xx+XRw+Qx+MWoTbXEUJn1gPH91PIMlKTj5jH7ecpildESAIv9mVhf5S+biWs34VWrALBSvoKeIpAkbxVA2xVeQ4T6gyvvCKINIuq3yof7Ky9VLaRZCIt5DloTUn4NneS4B/2ZM0FqagXhNO2SS8woffhbSPiAf+DWIvATDYc5tveVeloqrRAxF4SWga5EdgLMGokAg4RmOwn+Jl5m/5DDEGrIHacwoN2ZJ0fgVbp4iNvLlY90VJ9dA8v1oMUVlyoLioG5DvHVevOkPVzLDgqRj+gXpScvmHc36X9eEz9UJPX9XmieFK4gEOLCauyzIXiZpBktJSuH9/5T2/JH8kZTDFdk5sPTiQNFViBE53O82RE6GLL1mkMkR0gTKZ8nHsu6tf2TflDVNCVvmaRqxZUYvmZB0ijIQ6pRnukjFRaMvIb8R/cvUFcNcoA10DfLR/DiGhMrsF0JQOBEDozBhHDAVjWJ8KZJG0DADwuUcigQfTPIpp7U/Cimg3GJ8YGiQXkuR0DhMRIYRkbgkV3GpjqVsxBDyHf13GQS5Mkv+18ec/opWo7Q/kcH19XWd+XHNJT9K+8t4KYHrJTZKloQXGsBS4T/ey6f7WSrMBJPLfpaOEorSZNoact3JyCDkQPgowxEKY2HzEMuZT4t3/mP8l8gekrsO5I/i4fsm2hDJSZL8GqT4GfvpSDz5L0kUAizGG6tGSkGk5WggMgByiUTtKv8ykUBHiHYigH7IByO/SdJ4uZDDcj9d9qPUX46xkPSyMK+QACtd57JIKJAlOMo1pXO4td6+2Njdv1hvH7W7u3vt/V4zpu/lZK5CkGYg1MKHfpiIlAW/MnSdZlwkmgi5DAKKDCoCJEJJIpBBmudJkNQLo0U7KX0MTCCaEplAQUpwBf322zUgKtKzcJEpJ80YoGyUJIKIUoxiQnOQwiL7S0JxJIypiiFjTfvttxweQKYNwVF0I7uWbS+ucBRSyeDFHc8HwjAyQPw6RQxEChcuTCshkCUF5FAg6WgYFfKJBUiHsQjDcMKl+vmpFGMUYj+MhD2KVhXla9YMQ9hevg3AUChU7zppoCHOgC5RkSCnVL40qLOaDnkYS0gUYxYtBeQJQEwDlIhVFnp3Db9GEarYncheIbLs/KGs4aF0FqK7P5Sx7ISKiAgWspjtBr1czSqhWm31KSotpcFSoY1FEgRM5L3AIvdDSXZV3TeEYeLiam89FKwHfhDjUJZCFKX/Vy27FeE7gYRBZazWEJMBIL0pIvmQCt0NQrlKyEuW8pLJiAXYYFkqeSo6ZcvdrbX2Tq8tmjQHPI7kim+YMh7jpDJkea1TAGpxsfNXhnarkXQtxvg6yRPxlhrqb5UaqljEcvjCl4cRDuUlcalqX4t11+fy6pfQipVaLqjK0uu8oQxSxkX1r1+F5zjMottb8XOeOkUsyGjIsB/NS55S1bEfn1NpplzyNew4S1SxalXk2vAhzP00qZPukUKZNOqRQvgbpUm6R0hlAqlHCumZMiLdQ/CdBE51yr9J6LPmPbqX8iJb04Tec/FHFgpRPxB93u0XLzW8RwvLYTeT8vLRqOSmSnnJUQVq5bsMA8DyFu94M61FCAyr6nUng1NtM63TPlBub/8f6oks2Q==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful operations for a given account and can be used in streaming mode. Streaming mode allows you to listen for new operations for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"oneOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"create_account"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"starting_balance":{"type":"string"},"funder":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","starting_balance","funder","account"],"title":"CreateAccount"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_receive"},"type_i":{"type":"number","example":2},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"destination_min":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","destination_min"],"title":"PathPaymentStrictReceive"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_send"},"type_i":{"type":"number","example":13},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"source_max":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","source_asset_type"],"title":"PathPaymentStrictSend"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"account_merge"},"type_i":{"type":"number","example":8},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"into":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","account","into"],"title":"AccountMerge"}]}]},"examples":{"RetrieveAnAccountsOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/operations?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/operations?cursor=120194466505179137&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/operations?cursor=120192344791343105&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192344791343105"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192344791343105/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192344791343105"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192344791343105"}},"id":"120192344791343105","paging_token":"120192344791343105","transaction_successful":true,"source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","type":"create_account","type_i":0,"created_at":"2020-01-29T19:43:59Z","transaction_hash":"ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894","starting_balance":"2.0000000","funder":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192370561220609"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192370561220609/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192370561220609"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192370561220609"}},"id":"120192370561220609","paging_token":"120192370561220609","transaction_successful":true,"source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","type":"payment","type_i":1,"created_at":"2020-01-29T19:44:36Z","transaction_hash":"c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589","asset_type":"native","from":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","to":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","amount":"200.0000000"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192452165550081"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/0e6bc30f2b2f50ca0ecedef5a527309c74964e7daa6018976cd2c686c5df4be3"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192452165550081/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192452165550081"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192452165550081"}},"id":"120192452165550081","paging_token":"120192452165550081","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:46:20Z","transaction_hash":"0e6bc30f2b2f50ca0ecedef5a527309c74964e7daa6018976cd2c686c5df4be3","asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","limit":"922337203685.4775807","trustee":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192477935251457"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ec4116595bdfa8c1039c40af425e497c91fcf387c2a2a0cfa1f3bf64733f1f23"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192477935251457/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192477935251457"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192477935251457"}},"id":"120192477935251457","paging_token":"120192477935251457","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:46:55Z","transaction_hash":"ec4116595bdfa8c1039c40af425e497c91fcf387c2a2a0cfa1f3bf64733f1f23","asset_type":"credit_alphanum4","asset_code":"NGNT","asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","limit":"922337203685.4775807","trustee":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192490820268033"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/81f2b857cb47d7c63ca12e2ec3466f6f17b4990bf492ef752c9c6d2035ca11ff"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192490820268033/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192490820268033"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192490820268033"}},"id":"120192490820268033","paging_token":"120192490820268033","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:47:11Z","transaction_hash":"81f2b857cb47d7c63ca12e2ec3466f6f17b4990bf492ef752c9c6d2035ca11ff","asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","limit":"922337203685.4775807","trustee":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192499410071553"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/34b28df891c6a09968a2f0a6b410300b08b09c5f58cd12fe64fda59d29688f6e"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192499410071553/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192499410071553"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192499410071553"}},"id":"120192499410071553","paging_token":"120192499410071553","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:47:22Z","transaction_hash":"34b28df891c6a09968a2f0a6b410300b08b09c5f58cd12fe64fda59d29688f6e","asset_type":"credit_alphanum4","asset_code":"BB1","asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","limit":"922337203685.4775807","trustee":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192508000047105"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/12a8e8f11a697ee06a092eb0700c2b713fe07d29ffab190988d5bb248caf1917"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192508000047105/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192508000047105"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192508000047105"}},"id":"120192508000047105","paging_token":"120192508000047105","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T19:47:33Z","transaction_hash":"12a8e8f11a697ee06a092eb0700c2b713fe07d29ffab190988d5bb248caf1917","asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","limit":"922337203685.4775807","trustee":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192542359883777"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/36b9c9aa3c4a22a1e8274f69b1bbfdd5764e55b80804a8d9c6b35c14e4147580"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192542359883777/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192542359883777"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192542359883777"}},"id":"120192542359883777","paging_token":"120192542359883777","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-29T19:48:16Z","transaction_hash":"36b9c9aa3c4a22a1e8274f69b1bbfdd5764e55b80804a8d9c6b35c14e4147580","amount":"3.0000000","price":"18.1088911","price_r":{"n":181088911,"d":10000000},"buying_asset_type":"credit_alphanum4","buying_asset_code":"EURT","buying_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","selling_asset_type":"native","offer_id":"0"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120192568129794049"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/f0362887d2b9b853e7b464b174adfceb4c73ffb6a45e10b7cb3bff9cfa808340"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120192568129794049/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120192568129794049"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120192568129794049"}},"id":"120192568129794049","paging_token":"120192568129794049","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-29T19:48:54Z","transaction_hash":"f0362887d2b9b853e7b464b174adfceb4c73ffb6a45e10b7cb3bff9cfa808340","amount":"200.0000000","price":"0.0459893","price_r":{"n":459893,"d":10000000},"buying_asset_type":"credit_alphanum4","buying_asset_code":"NGNT","buying_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","selling_asset_type":"native","offer_id":"0"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120194466505179137"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/a470f40ba0c1fd17cb957e0b438bd873b110ffb808b8133a5144cea3f5a66d0d"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120194466505179137/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120194466505179137"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120194466505179137"}},"id":"120194466505179137","paging_token":"120194466505179137","transaction_successful":true,"source_account":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"change_trust","type_i":6,"created_at":"2020-01-29T20:31:28Z","transaction_hash":"a470f40ba0c1fd17cb957e0b438bd873b110ffb808b8133a5144cea3f5a66d0d","asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","limit":"0.0000000","trustee":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","trustor":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx
deleted file mode 100644
index ebdda3d4c5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-payments-by-account-id
-title: "Retrieve an Account's Payments"
-description: "This endpoint represents successful payments for a given account and can be used in streaming mode. Streaming mode allows you to listen for new payments for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time."
-sidebar_label: "Retrieve an Account's Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXOty2ziyfhUUf8wkU5LMG3hR1dQe+SbfJMuWfFPG5QGJpsQxRWoByo435ap9jX29fZItgKSudDy25Zlk5uRPKiIIdDe+/tCNsPuLkpIBV+qflIbvJ5M45cp1RaHAfRaO0zCJlbrSG4YcQUzHSRiniMGYAYc45YhPfB84DyYRGpOHkfwtSBgiaBDeQYxINiUiMUU+iZEHaMKBojBGPGVARmE8QKOEQg11F/6NSBQl9xw9JBOUJigKeQqxnDqG+8W1UiHcdCGO0iE8IMIAEUqBirfTIaBuClFEGIqADoDV0H6AfBJFZbJU0F7Cwn8lMboPowjxlLAUkVROA4RFIfAU3cbJfVwIgiZxBJwjgvwJ4wlDIUcc0oqY+34Y+kPkEw4oTOdnDFgyQumQpPlLNbT5IN5KhRxirXyuOxJNQKgRJ/cVaRBhyUzkmSV8BiQFingY+yBGMcTgnxMhahqOoKZUlGQMjIgd3adKXWlC2slf3nzIt36fKhVlTBgZQQpMgOKLEpMRKHUlN/BNKIaEAhRjkg6ViiJWCRlQpZ6yCZQiJ3/3v//+D0fjiReFPrqFBwSxn9BsAwjyCAdDF2oJ9acQk/IK4bk/hBFR6l+U9GEsBMpGKhUFPpPROBI/NbdbJyftg5Z5dmSf7Dcsq2Of6p3+Xutkv33R32zZ9ubOZmvvaPdyGx/snDX2mgf2qXnQVx4fK1NFM6sXSv5zAuxhQcuARHxFzQaKJyMPWLaf0k242DKC+Bj8MAh9FCW+VCZT10+iCHz57yRADPg4iTlw6SihsJKEZg4RQGMyCOPBTZrcQpwDIgkQQQz8hNFS+4RxCgNg8wayLNWyNNu0HRe7morn1U4YhZdrTYGHg5gUeghR5UQz4GcScsSHySSiiIzHQFgNHcs5OApjP5pQQL8S7v+KPhDuQ0zDePARJQz9Kpb7FX0Qf+U/S8fNPJ4NJtL3Qh7/99//SXOHSxGFgEyizP5y2mfgE09Ggv0I95VMQeV63jBROArTFxqmNwQ0Ip/D0WRUAEPucmYKBumExUBrSIyT80uXZiQeQLbnmhBeV1VURSRGk/EYWD5QAizkaEgYnbpPwVeCDsfAgoSNiKABBoQnMf+K0YoNBLpiO039vbjS1HmD5Vt6E5AwAvpCy3UhlYzNMsor4JHNhaYMJoAjvEbIugom+bbwJLlEqRZekkRA4tn+S/KS4xd2/7ckjF+rAok58TPJ5lQRPrLwLD8gcv4G4g+nrrSgrvilIIqa8nhdUT5X+WQ8TljKq9MTrKDhKaUIpXVVFX8tyZmd3UpF8ZM4hTgVQ8h4HIUZUW38xsW4L3PGI1F0HMhTITdj4v0GvvCOMRPCpmG23k0Uxrd8ztxPjOMQBc+PGjIIyjxXwjyVLhrfKo8VJYXROBJWLNnox8f5jfuUTXpdUdIwjWBujhg+p9+YSGMGd9+USI9iWPHTkdxq4TLPYAJGHoiI7HlVcqKcG0gYI8L1whRGvwNX3zH+5qjhG5MMggD89HdY9Q+VSmYgQL81scYMfKDwbYm1NEiifxFxs12es+ycNtePFSWkZeIWK4VUqj8Xr66OXoT5zSyJLNOsovBkwny4ybOIssXHJE2BiUOt+alR7atV9/oLxo9zYhFKmTjsxNLy5a/lEXlSVQy+CUtVyE/sG1Ii0pKGQ8KHpYMI55DelEs0fSzCPPG4iFRFvH0HipSAhukNicZDEk9G5upPmi63LJsn5HwC7M32EwHq2zchefMUZFQOh2WYh1lSOwfIJ+G3grUcLVMcLOx6yR4v7GhuKqnsVNzrx8Xjs1NgTexTDkHJC6eQshDuoBEX9zJFui6eyhxw8agrDrOMUJRhmo55fWNjmOUG1RR4GkNa49lFSC1hg41cTb7R3GofYbx/0NvT9y51a++ovd+82tYP9k+OepuNkyOje95p9xtW5/LQbjfO985M3bg47u1sFPcP/8jS5p9/kFnKz5r6g8wDfxZZ1VxU9afKppmO7ri6bWDN0VzVcswnpC0Crj9XWk21XFNVbdOwdOwaurssrcxVBZYWQqtp8PTpjeCYZR8bq7KUhCovmHo+/9nQLd91LUIsEni663qWbWmBbhhYt23NtWwNa5ZKKFiEqKpGbIw1zTJNx9NMTA1iL8Um69Jwo5hzKch4wfz5DP+YbdcPT27uctDw6mXI11fJD3Cl5NnysV0+5qmTO0s7l89qpblpmmetYwt3DnH7onXaMbv6cbffwJvbZmPr+AIfnli9i6OjY73Vsbt2G7cO9NbB+X5BvfWccZcoWZzJ6uIZrOiq5lZVt6ppPc2oa1bdNPtlJF1X3gy5iiLvcIWxPBKJuxZhrpqa/RHMP4nFfdqb9J8z4itJRaZl70UChvpXJwFD/UNJIDPoe5OAWOUpEjDU50lAjvnDSaD474cRsMFcPFZ3/kwOWIuCYSxi4W/FxbGBTc21ddsydMMxtTW6uK+61PQBXNeglkptw3fUQDUsy7Jcy7INh+iW5wSGp2Nq6zb2XCOgrouxij0M2FuTiy9r+M4uXmbQ9bv46iozF195VuLiJWNe6uLb5+bhztZRt390eHq+Z/Z7F+eNrrlvXOhHnUbn3LIa27u7Z/3D5v75ce/QarYOmwc9bMxcvMi6Z86tlTm3plU1p6e5dezWTfUJ534z1hZT81nKnSW/b9L2Td4+S3sVy3FqpmphE5trJgHbwJapq46BsaE76lpJQMeUOqbtOqptAThANN3ybcdUbWppvg1OYEBAA8c2XN02A2x5qk1sVXexqnqquiYSWNbwnUmgzKDrJ4HVVWYksPKshARKxnyzJKALElCdum7UDfwUCbwVa98BCRgY1wzHsbHrrJkEZMynGdh1dc22LLxGEvBcavvYMD0cEM1ysK0S7AUBqIGuOi4FDatUVb3A8T2queC7Bjiu7WMLu9gJjGBNJLCs4TuTQJlB108Cq6vMSGDlWQkJlIx5KQm8HtYvIAFdrapaVbN7ulo39LrhPEECb8baEgmU3LnP39IrZ91tZfnCXWlunx22mmfN7f7JoXW1d9XAfatxpTfNy+1uv9PtG90LfNY2GqfnrWPrpHu6fdHBV0c7l3Nc8wajSq5pdC8OLnZPr3YwPtyyW81Gu99qnW4e4nbnsmfstTrbJ1Z357Lftvqdi6vL8/Orzd3TRa5xzJpraqpjr5lqTNvAqukYjqU6lqvhdcYbHjZ8qlGDuJhQPaC2Zmqe4TmqCo5PDRJoFnaoTm3d03XbpJpHNc3yAxWwE2iusR6qWdHwfamm1KBrp5qSVaZUs/pslWrKxrz4XmG7e7DXaLZPto/0iz4+2jzt7p/vW62zvYNja+vocBdf7p6fHdrNVufsxGxvHnWvzht7ly+kGq2qGlXVEkmHbtcN4ymqeSvWnos33qDtuuINNb/j1NZPAabmaI6IO1VVW2e0oXngBjgwqE91xzcDYqsBDjBQ26W2YeiUaKZtaoAxwcQDUzN0avqqSYntWYEG66OABQ3fnwJWDPouFLC0ygIFLD4rp4DlMS+ONs77uLO3vds8O7euLtv2vm3g0x3cOOjuHh9fdHpmQ7/Y22r2mpfHJ9bh+UXL6F3tnGy9kgJ0tW66deOpS8U3Y+05CniDtt8BBWDsqti2dcNRTXudUQCxPJ9Y1AfVVzXqUtcHz/dt17Qs33UsT3OI43uGZ9mqoQaWqZuehS3Dth3iueaa/ndhRcP3p4AVg74LBSytskABi8/KKWB5zLcdBehaXXPrpvtUFPBWrP2NowBHdyzb0U3DMi3dcvQ1UoBtkgA02yYW+IFpWY7reh71qGG4xHYt0FwXE8N3fFN1TB9jyzFdcRdkY9fzbF9bEwUsa/jOFFBm0PVTwOoqMwpYeVZCASVjXnzx2Ljcutg+aVx19PMt/exUPzw9Ot+2D06u9q9aJ/Zmc/fKMu3Nraa5tdto9+yDq3b32Oy+hgJ0tafpddOp609FAW/G2rMXj6/X9juggIVPtNZIARSwapkW+GBpGnEDj4pETPdcTQ1UXQ1cEyxsqpZJLTOg2AywamCHGlQzwA5Md30UsKDh+1PAikHfhQKWVlmggMVn5RSwPObFiYB+1LX72DJ7zYvT8639vV53Z7+/eYwvzvrd9qneamDT3N0xDzqXrcZZa/tkXz84tdqvpQCjbup11X6CAt6MtWcTgddr+w4UkH3VKj9shc8pxFxgXX6CeAsPSr28UqlSfMUqdlTUM40gHSYCMwNIs6+BhSln31Z+mRWhPk6/lxTfYgG7K8pVJyz6fWhWyor2etk41Ib0PmG3ktvKZwwm6YTB75lztxiJ4mLWa/HZR5B9Ap1/B5yX8AmjAOPZ22pNrWnyS/zRiLCH2Sg0ZsldSGW9KNrr9Tqo0dkXRWaUpKSoFSsqnvNVa2g/RWE8AJ5mZaYMqtJwsmI6e3PMEjrxgSLvoWyKrHRVFCZMyxCB8FCUvSbIT2I+GUHxKrkDRgaA5grKEINIwrioyZ4rVawmLIRYFMBJQRbrf3lWNO49TAXaShiI8smQS83n9PBYSAeAPEjvQRSgj8eZtotvdlgiijE4isJbQPeiEDzlFUTBhzhlJAr/JUrxPvtDUZLJK3IG6Y8ou9OXEk3LLtME8YknqzPnzpsKkgWDYouK6vT8W8GKKG7NC7jhTpZvSzmWSwZnb9ZWkPV3R8Kn+Q29/lC4J4U7iMRxyxdOrlzsDT9hUI0TCh//Vuj5Jf4lLpbL2zAQeaACRXchQf7Z6VFFFOGz5J4DkyskMRR1qFNbd7cP+bO2ponPN9IkifgGp7dcWDpBDAScsrYGiahx+BymD2J+2algnBm0gu5BVkmPRhBT2epAGIrEYmEUxjwFQsVLI3IrugTQkIGfyj0UvRy41FNu62ASUkCZx3jA0TC5lyahozAWrSREh4oM4hKOhW3EErJw+gODIAOz1H97qumPaDNKBjMb3N/fLyo/HVn1omSwQaox3Ff5JK6KU2gI1fz8+ChrtXki3IT4twOWTGKKknjZGzLsMH8YpuCnE0YiFI6Ez0PW9iHJC7tH5DfRKiI7OpA3GY0/1tCu6EQRZ4Vk4mfiJRNR4y1FFAbM15tCI6Eg+jBUkD8E/xaJ0fP6y8rxpjDtzACDMB1OvJqfjDZyO2wMkg0vSryNERGW3hDuFfrAi6NzQ1SQs5hEGVKaZ/vbOze7x6c32zvnO0fHnZ3Tbm1EP8rN3IQgYSBg4cEgjEWN+o8c3ScsFZ0FwlSG1Xm7DEESoRQR/GGSFcZL6YXTonZCX0MTiCa+rJiXFqyjn366B0RFL45UNERJGAfEJnEshCjMKDY0IykiWn3ElETCmeY5ZIq0n37K6AFknwgSRQ9yavnuzR2JQioVvFk5+UA4BgOU3ieIg+jZkQrXin1gcU45FPxkMo5y+4wESYcjEYSROJXw8xJpxigkXhgJfxRvzYGvtuAYwvdGJCYD4CgU0LuPK2hMGNAqFb1QCvAlwaKqyTgNR5ISxZr5m4LyBCEmAYpFwoM+3MOPUYTm/E60KxAtVX5RtshYHhZiul+Uqe0EREQ8C2zEj4NuBrO5UG0hERSDqklQzdGYV70TX5Yl5cX+hdjzcN8Vjkny4sjFUHAx8IMRCeVTiKLk/+afPVaUKPQh5jC3VmNM/CEgvSY+MwqpwG4Qyo8FsifV7MlsxZxsiHwqdcon5RtH+1s77e6OeKU2TEeRTL7GCU9HJJ5bsqgoE4Sa15T9yFFnFkcvRBhfZm0B/r//z1+i/0+eSqbwOd0YRySUxbUSYF/yXOtT8Um7QEN9oeXPNN26rijDhKdi8Jcv4rQ4Y9Hjo/g5648hkjAacuJFT3XImEfWn984p9QqWdY6bQWU56mKzAdfotx30x/nK1YoOgO90gh/oV44XzFS0SXolUZ6p7Y3XxF4pUvPouTPCvquzW2+Knnekmcm77X4BwuFqV/IPh9O8zrxj2htjcpKJS+qmOKHeckLjeaIVpaBD4HI4sHp9VnD92E8D6+VNj0L12fNnZ7y+Pg/UgZ4VQ==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful payments for a given account and can be used in streaming mode. Streaming mode allows you to listen for new payments for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"}]},"examples":{"RetrieveAnAccountsPayments":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/payments?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/payments?cursor=148289273518190684&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE/payments?cursor=110694007436259329&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259329"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/26c996aa6afb299b6761f2335277196715160ade6aa001a755116448b145d3a7"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259329/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259329"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259329"}},"id":"110694007436259329","paging_token":"110694007436259329","transaction_successful":true,"source_account":"GB44UMO65PK5NWMRP4S2OSZA5BD4ACOW5KQ6TWLLO2MP7S7N5MJ2MJVI","type":"create_account","type_i":0,"created_at":"2019-09-11T13:16:44Z","transaction_hash":"26c996aa6afb299b6761f2335277196715160ade6aa001a755116448b145d3a7","starting_balance":"1.0000000","funder":"GB44UMO65PK5NWMRP4S2OSZA5BD4ACOW5KQ6TWLLO2MP7S7N5MJ2MJVI","account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259330"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/26c996aa6afb299b6761f2335277196715160ade6aa001a755116448b145d3a7"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/110694007436259330/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=110694007436259330"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=110694007436259330"}},"id":"110694007436259330","paging_token":"110694007436259330","transaction_successful":true,"source_account":"GB44UMO65PK5NWMRP4S2OSZA5BD4ACOW5KQ6TWLLO2MP7S7N5MJ2MJVI","type":"account_merge","type_i":8,"created_at":"2019-09-11T13:16:44Z","transaction_hash":"26c996aa6afb299b6761f2335277196715160ade6aa001a755116448b145d3a7","account":"GB44UMO65PK5NWMRP4S2OSZA5BD4ACOW5KQ6TWLLO2MP7S7N5MJ2MJVI","into":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/115354197276323841"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/c09d4cee993d60d73c80f036666966738a26b8f3b25d7275b93fd995505b5e5b"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/115354197276323841/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=115354197276323841"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=115354197276323841"}},"id":"115354197276323841","paging_token":"115354197276323841","transaction_successful":true,"source_account":"GDV4KECLSZLKRVH4ZTWVAS4I3W2LPAPV66ADFFUZKGIVOTK6GMKGJT53","type":"payment","type_i":1,"created_at":"2019-11-18T19:59:40Z","transaction_hash":"c09d4cee993d60d73c80f036666966738a26b8f3b25d7275b93fd995505b5e5b","asset_type":"native","from":"GDV4KECLSZLKRVH4ZTWVAS4I3W2LPAPV66ADFFUZKGIVOTK6GMKGJT53","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"688.4065454"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/117356420835532801"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/c25dd84798076ee8ea126c78407d61c7e8f3efdf8739274f56b07a7029500b00"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/117356420835532801/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=117356420835532801"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=117356420835532801"}},"id":"117356420835532801","paging_token":"117356420835532801","transaction_successful":true,"source_account":"GDV4KECLSZLKRVH4ZTWVAS4I3W2LPAPV66ADFFUZKGIVOTK6GMKGJT53","type":"payment","type_i":1,"created_at":"2019-12-18T08:23:35Z","transaction_hash":"c25dd84798076ee8ea126c78407d61c7e8f3efdf8739274f56b07a7029500b00","asset_type":"native","from":"GDV4KECLSZLKRVH4ZTWVAS4I3W2LPAPV66ADFFUZKGIVOTK6GMKGJT53","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"355.3887598"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/119400713599217665"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/b9d7c534b5fa168570a5bffe0f2089de150d00bf8cbd19ec93e897c565958f3f"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/119400713599217665/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=119400713599217665"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=119400713599217665"}},"id":"119400713599217665","paging_token":"119400713599217665","transaction_successful":true,"source_account":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","type":"payment","type_i":1,"created_at":"2020-01-17T20:32:38Z","transaction_hash":"b9d7c534b5fa168570a5bffe0f2089de150d00bf8cbd19ec93e897c565958f3f","asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","from":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","to":"GASWJWFRYE55KC7MGANZMMRBK5NPXT3HMPDQ6SEXZN6ZPWYXVVYBFRTE","amount":"84.9410878"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/147350483860869151"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/b53cd1d3a95ad2fd7141b3b800e8cd3af1658d2d72b2274d1bd116cf0e58f193"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/147350483860869151/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=147350483860869151"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=147350483860869151"}},"id":"147350483860869151","paging_token":"147350483860869151","transaction_successful":true,"source_account":"GBDSJHAGNQDL2WZ5LBRSIVI6MUHJO6CLKF5XFVUK7GMPUQ4NBLSYVAHX","type":"payment","type_i":1,"created_at":"2021-03-06T19:27:33Z","transaction_hash":"b53cd1d3a95ad2fd7141b3b800e8cd3af1658d2d72b2274d1bd116cf0e58f193","asset_type":"native","from":"GBDSJHAGNQDL2WZ5LBRSIVI6MUHJO6CLKF5XFVUK7GMPUQ4NBLSYVAHX","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/147354181828010015"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/1be9f5f3dcd28c4fa70f5f5ed79d7332da14741e55a5abe4132d4c04da7b6f1e"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/147354181828010015/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=147354181828010015"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=147354181828010015"}},"id":"147354181828010015","paging_token":"147354181828010015","transaction_successful":true,"source_account":"GCVZ5PHDFGUV6YXN7I735RE5AJSFOOWPT4A2WHCGTGXOQ6KVWM3TYEQC","type":"payment","type_i":1,"created_at":"2021-03-06T20:49:34Z","transaction_hash":"1be9f5f3dcd28c4fa70f5f5ed79d7332da14741e55a5abe4132d4c04da7b6f1e","asset_type":"native","from":"GCVZ5PHDFGUV6YXN7I735RE5AJSFOOWPT4A2WHCGTGXOQ6KVWM3TYEQC","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/147355590577238047"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ba6bca6dce0c01d9d9cebcc79466c986b18a8cb3b67030f6424b6563778ab947"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/147355590577238047/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=147355590577238047"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=147355590577238047"}},"id":"147355590577238047","paging_token":"147355590577238047","transaction_successful":true,"source_account":"GBDSJHAGNQDL2WZ5LBRSIVI6MUHJO6CLKF5XFVUK7GMPUQ4NBLSYVAHX","type":"payment","type_i":1,"created_at":"2021-03-06T21:19:49Z","transaction_hash":"ba6bca6dce0c01d9d9cebcc79466c986b18a8cb3b67030f6424b6563778ab947","asset_type":"native","from":"GBDSJHAGNQDL2WZ5LBRSIVI6MUHJO6CLKF5XFVUK7GMPUQ4NBLSYVAHX","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/148286782436462682"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/74afe177a6ecf466899bbdbd339a796e1995a3c8c4084c556849a702759bb7c1"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/148286782436462682/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=148286782436462682"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=148286782436462682"}},"id":"148286782436462682","paging_token":"148286782436462682","transaction_successful":true,"source_account":"GDAXCWDQAYP2VC2UR2KRLVD7JQYIYMQ7BGFY647BCG4CFANT7JYNSO4S","type":"payment","type_i":1,"created_at":"2021-03-20T12:48:24Z","transaction_hash":"74afe177a6ecf466899bbdbd339a796e1995a3c8c4084c556849a702759bb7c1","asset_type":"native","from":"GDAXCWDQAYP2VC2UR2KRLVD7JQYIYMQ7BGFY647BCG4CFANT7JYNSO4S","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/148289273518190684"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/de50646ece611a9fbd2b222b910f020f94e654064d64fd54f50358d3d13e7f49"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/148289273518190684/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=148289273518190684"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=148289273518190684"}},"id":"148289273518190684","paging_token":"148289273518190684","transaction_successful":true,"source_account":"GC2LS7Z564TGWRVCIHTSEIZBO5WUZSNR2MA544FE4JPXMAUMDQI2JR6N","type":"payment","type_i":1,"created_at":"2021-03-20T13:42:07Z","transaction_hash":"de50646ece611a9fbd2b222b910f020f94e654064d64fd54f50358d3d13e7f49","asset_type":"native","from":"GC2LS7Z564TGWRVCIHTSEIZBO5WUZSNR2MA544FE4JPXMAUMDQI2JR6N","to":"GCNL55IJTH2HX26HLNIGYD2JIQLTBAQL3SVPNZA6PXK7NAVHU423WOTE","amount":"0.0000001"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-trades-by-account-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-trades-by-account-id.api.mdx
deleted file mode 100644
index aca4b1515b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-trades-by-account-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-trades-by-account-id
-title: "Retrieve an Account's Trades"
-description: "This endpoint represents all trades for a given account and can be used in streaming mode. Streaming mode allows you to listen for trades for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time."
-sidebar_label: "Retrieve an Account's Trades"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWuly4zYSfhUUf2SO0n3LValdybJl+ZRlyYdmXBqIbEmISYABQMuOS1V5jbxenmSrQVKmLNkz4002M8n6j0tko9H9oS+w+8HSdKqsrQ9Ww7ZFwLWyrlOWA8qWzNdMcGvL6s+YIsAdXzCuiQRfggKuFaGuS7SkDigyEZJQMmW3wAkNORHKHWJTTsZAAgUOYZwoLYF6jE+JJxzIkLOV38hQzBW5FwHRgrhMaeCGdWIXjdIst1BEz+CeUAmEOg44uE7PgJxpcF0qiQvOFGSGdCbEpq67SYoU2ROS/SI4mTPXJUpTqQnVhg1Q6TJQmtxwMeehGCTgLihFKLEDqYQkTBEFOoWc5zNmz4hNFRCmk/wmUnhEz6iOFmVI8x5XaZQCd4p43VI3AFSCi3nKAIEIhgLHKNgSqAaHKMZtQBpJJPwcoJiaeZCxUpbwQVI8vo5jbVlt0H2ztHkfnXLHsVKWTyX1QIPE83+wOPXA2rIiaEcMSRiev0/1zEpZuAeT4FhbWgaw0Uiitb//+psifjB2mU1u4J4At4UTQk/JmCooFlAlVH1pTUZaFF3ZM/CotfVg6XsfBQoprZQFd9TzXXzUbh2dnh7vH5UGh9XTTqNS6VZ7he5w7+i0c3wxbB5Vq82d5tHe4e5lq7y/M2jstfervdL+0FosUktFQ8RjJX8OQN6vaDmhrlpTs0F44I1BhmdpPELhcVGifLDZhNnEFbZRJlTXFq4LtvktJkSC8gVXoIxzMETJGGVkHkB8OmV8OtLiBnhkDGJCKJFgC+lsxIdxDVOQSYAqlVylkq+WqrV6uZ7PlZNqC+nA12vtgGJTTmM9UFTD6NHoQwkVUTMRuA6hvg9UZsiJ4aEI47YbOEA+UWV/Im+psoE7jE/fESHJJ9zuE3mL/6LHxmVDX5fTwAOuCVP8919/05GzaeLAhAZuiL9h+xnz4YGHgY4q2woVtK6TwLjMY/orgenPgHj0jnmBFxuGOeUQCgk6kBycDEE6w9+4s6R8CuGZ51H4Qi5H0oRyEvg+yIjQGBhTZEals3SfOFJhIPRBToT0KAYBCVQJrl4ALT5AcNawy+e+1K7yucXiOmXdpVXg+0JqlV6G0jgqLC0cORVyOfy3itlZYNuglJWybME1cI0k1PddFvpN9ieFdA8JiajrnkxMkIpkE+OfwMbD8iWGOs3C/UYu4zcqocMzdArcyeepZhImmwzJoK6NxfAba5GyNHi+i9AmqMdCuEA5RpyEEX0ImV6nLM20CwkeHO70NyaSL+H2mxJpgWTxo0Nz1Oi/n7EJ8MaApcHnVYn8NkFIpaQYBpgG7wvs6ju2P0zL35hIppYA+Y1JtSytvim5nhAZA4sO9RHIpPDXi5TFnE3SxYyZY4JAoiB5iXqFbpGywsJ7ZLtCwQjL0vXFCOZkAnK0SQ5EBWvWUfh4w2uX/Rwwh+n7kS+EO5oAjMZ+gjLMx0m4A8Z1sRBb++gJg2ekMKQvymkootJ3E0Q+1Rokpr72h0Z6mEvXrx/K5UUCPOo4ElPikpm3mdfyvVKgn0cmQYOVw+domFLBips9UkWW84VQxdQvohUT/VGALfk9j9mS5GXYVsmeRW6V7DnwXnPsTI0UuO4Ku2UYwODCbAjz1KOns/Aml3C+Tb634kyrRrZuUmuYbkRwTWaMSS+Gww3xY5GyNllJIs0bubtG80X49/jOXGqtBYayqEQ1+/RASwa30ODxN43w9ovvzJVqNVXHyTiM1tZMa19tZbOzsNROa1Cag86o8ItCRshpNrJdlW23itv7V4P+sHFV2T/dLW3vdCrD6vlF+aRyftw+GPabV4Od7f7Jfnen1W9WO4W94Vm3UzjIhlf5f4V30B9/MCX/j8UfzJ3qR7yhJErCv1CwfK5aKtXLtVKtVK7nS/l8MZ3bLGxcLP7lwpYqtVotXy1X8pX8mrDm1ocmtFIVLuu+Dy/YRbJIepWS2yfVk4tyt9DtVi9ax5WrQetyMDjpNnql4d7+Wau1Pex3Gqe9fm+4d3B6cV4qXwy6zYvLJ5XQ/xLftXLnKzZfrlPZ9XMxR4D5wdp0Zk8D2rNUG2oMq5DL19O5arpQ6efqW/nqVq4wXA1/0SeQsRA31lp6t/K5Uq5aK1Qr1tPEbr36BJ9kdatUKhYzhZz52xB/tyz80HKbDMQJAUvVfD1fLJdq1WKuni+VcpWytSGrWq8+9PWUigJnioVY3k3p1LIlOEyPqOvPKA+80hpdmE+tZjO/9irOoVa7Vd6v7B3uliuVymWpMTzs7/YvD69Klf3y2UV157J30Dzcuerud4vFs2Lx6HLYPq9sX+weryej6GvEMmUaK7JMtrHyufA74J/o6qetk36nc9hrV4qlTu+icdLqD84qe5XT6vlgcHww7Bw3W/snl+393V71aliu7ravzqvNv42r1yq5Sr5SqtcL666eePeCqz+l+iJXL5S/1tUL1WK9WNvk6q88waeuns9lcv+do5dzpVKtnitWa4U/39HzCWn/7+af87XG0aDcP90dHLXa5wdXp91ua7tVODo4GAwudg7PThs7B8fHg1Jv93T7Yves1+zuNwpHjfbp38XNk2XhUzdfLRmfc/M1qi9w8/pWMffVbl6vFwrFDW7+2hN86ubVUi1TLhZr9VL5q/08lK9cqv3p3l0tZWooZa36Pbv3Y4RyEj8x0VwvlldEuNPAFRqrqepv4N7a2ty3SMV3QtwLuxse6JlA1lPQ4TV+Zm1Zj7738NghXUQ3EGyfgLyNO6mBdL/Mp6xN/aR+SEeOQc+FvDGfuDdznAQ6kPAlPHdjSsJjrtfY6ZoIc/uO7tNRdwkhAanC1blMLoNnrQLPo/L+kYr4Utwyx7QyyV6/3yWNbgfbSQ7VFHtVyTZ8tGuGdDRhfApKhx1QCWkDnGnjhyt9KZzABoeM7zexCLuq+Elv2SEDqhh2ZAWxBVeBB/FSeguSToEkmktEgmt8MR4USHTR0kIy4NhZN4KstqZVOMMwvl8KtC0kYGePKaN5Qo+xZM4UyBj0HHAewvdDbVdXdqXAzySKuOwGyBynE7RKEQds4FpSl/0CDoE7e4bdQpUyHIynkdDTjETLjqAWRAVj0ziUlCtqWs4qRUwjE48oHpkYUxeVTWHfNZorgFszzmHkSK42je3lysyaZf3TLeFD8kCv38bu6cAtuJgt1Ur+jMTO2kJCmgsH3v2jrOcj/8jj7aKpIGoaweCQW0aJPegdpnA+RIq5Aml2EBziaYMl1metA/VZrB1hq6wWwlVZ5dwoRFoQCWhO4bSNwK+Fd0zfI38zQuOHgKbIHEwD3/OAO2YCB4GiHDcmjCsN1MFFHr3BARaHSbC1OUMcMFJGT3Os04A5QEKPGYMiMzE3kDge4zjZhANToYkbc4yxwS1MT/+thElozEb/1lLTN6TpiukjBvP5fFX5JWV67IpplqY5zNMq4GnMQjNIR/njnRkjUALdhNo3UykC7hDBn3pDaDvSnjENtg4kdQnz0OfBMycvopkDj/6EE0xh6iDjwPPfZcguDkjxsAWDj+lYBDh+YEREAKP9lqYhHMAqIEXsGdg3BKmT+puhhjZC+wjAlOlZMM7YwstGOGSnIjt2xTjrUUQ6i+7FbFBx6szicIPk1A0tpT3otHZGuye9UWvnfOfwpLvTO8t4zjtzmE2YCAloFmOYMo7jE28UmQupceiFaVMVR1NcGCSYERHsmQhnNoz06LTkWDivCRPEEbYZ5jAIbpH37+dAHBwR0ziWJ6QCIgPOUYgYRjzQMEhRnEDjDnXRmZIxZGlp79+H4QHMCBN13XvD2qwd3VKXOUbB0VrmA3QMCUTPBVGA42QaXYvbIHkUchywReC7ET4eBmnmYQlGuTbmNxYGRpfRMXPRH3FVwvgyK46BvudRTqegCEPTm/MU8akEJ+3ggF5sfGKyqqrwNfNMSMQ9o5UY8jAgignhAI4ib+fwxnVJwu9wkgYn/T5a29Q3yQLZfbSW2KGJ4GUEpKdOJmehmSVKteTJGqK0mKQja4wmYKhtvvJHU0ix2Elz30XHDK9sqSel4GrhBx5l5i24rvh38p3pl9rAw9tutFfDp/YMSCGDxTRz0HYnzJTw4Zt0+OZxxyjYUPPW6BQxVdnDzvbO8dkOLsnMtOeaC6EvlPYoT2wZ92YwoEbdmTeK9OMqeqW+eHgcEPr/DOr3N4MaXSk13Oms71JmepjGlh6iS9WHeNgUj35rZfA0ulddp6yZUBpJHx4wLQyku1jg43BAD29bDlN07D43opc0or9+eHMjJuHldDmOGl1HLXPx+xrlvpsZzRdQiKdTXwnC32ge8wWQ4knVR5Cu8YdkiNJX+sTbXjRM8I78YSPcG0WPJ+r4fVLyWKWE85t+/gwoGsLjt5uGbYOfVHptYnTl2017p28tFv8Bhke2FA==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Trades"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/trades"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents all trades for a given account and can be used in streaming mode. Streaming mode allows you to listen for trades for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"base":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"counter":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","base","counter","operation"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"ledger_close_time":{"type":"string"},"offer_id":{"type":"string"},"trade_type":{"type":"string"},"liquidity_pool_fee_bp":{"type":"number","format":"uint32"},"base_liquidity_pool_id":{"type":"string"},"base_offer_id":{"type":"string"},"base_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_amount":{"type":"string"},"base_asset_type":{"type":"string"},"base_asset_code":{"type":"string"},"base_asset_issuer":{"type":"string"},"counter_liquidity_pool_id":{"type":"string"},"counter_offer_id":{"type":"string"},"counter_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"counter_amount":{"type":"string"},"counter_asset_type":{"type":"string"},"counter_asset_code":{"type":"string"},"counter_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_is_seller":{"type":"boolean"},"price":{"required":["id","paging_token","ledger_close_time","trade_type","base_amount","base_asset_type","counter_amount","counter_asset_type","base_is_seller"],"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"Trade"}]},"examples":{"RetrieveAnAccountsTrades":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/trades?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/trades?cursor=107449584845914113-0&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K/trades?cursor=107449468881756161-0&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GCO7OW5P2PP7WDN6YUDXUUOPAR4ZHJSDDCZTIAQRTRZHKQWV45WUPBWX"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/107449468881756161"}},"id":"107449468881756161-0","paging_token":"107449468881756161-0","ledger_close_time":"2019-07-26T09:17:02Z","trade_type":"orderbook","base_offer_id":"104078276","base_account":"GCO7OW5P2PP7WDN6YUDXUUOPAR4ZHJSDDCZTIAQRTRZHKQWV45WUPBWX","base_amount":"4433.2000000","base_asset_type":"native","counter_offer_id":"4719135487309144065","counter_account":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","counter_amount":"443.3200000","counter_asset_type":"credit_alphanum4","counter_asset_code":"BB1","counter_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","base_is_seller":true,"price":{"n":"1","d":"10"}},{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GCQDOTIILRG634IRWAODTUS6H6Q7VUUNKZINBDJOXGJFR7YZ57FGYV7B"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/107449486061649921"}},"id":"107449486061649921-0","paging_token":"107449486061649921-0","ledger_close_time":"2019-07-26T09:17:25Z","trade_type":"orderbook","base_offer_id":"104273938","base_account":"GCQDOTIILRG634IRWAODTUS6H6Q7VUUNKZINBDJOXGJFR7YZ57FGYV7B","base_amount":"10.0000000","base_asset_type":"native","counter_offer_id":"4719135504489037825","counter_account":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","counter_amount":"1.0000000","counter_asset_type":"credit_alphanum4","counter_asset_code":"BB1","counter_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","base_is_seller":true,"price":{"n":"1","d":"10"}},{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GAMU5TQFUMDGVKYQPPDCD2MKKUUWELSQAEKNNU4RFQCWFSRBPJA2MAGQ"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/107449584845914113"}},"id":"107449584845914113-0","paging_token":"107449584845914113-0","ledger_close_time":"2019-07-26T09:19:30Z","trade_type":"orderbook","base_offer_id":"104299223","base_account":"GAMU5TQFUMDGVKYQPPDCD2MKKUUWELSQAEKNNU4RFQCWFSRBPJA2MAGQ","base_amount":"748.5338945","base_asset_type":"native","counter_offer_id":"104299548","counter_account":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","counter_amount":"74.8533887","counter_asset_type":"credit_alphanum4","counter_asset_code":"BB1","counter_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","base_is_seller":true,"price":{"n":"10000000","d":"100000001"}}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-trades-by-offer-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-trades-by-offer-id.api.mdx
deleted file mode 100644
index c436d3b10b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-trades-by-offer-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-trades-by-offer-id
-title: "Retrieve an Offer's Trades"
-description: "This endpoint represents all trades for a given offer and can be used in streaming mode. Streaming mode allows you to listen for trades for this offer as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time."
-sidebar_label: "Retrieve an Offer's Trades"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWntTGzkS/ypd+mOTbPkJtgFXbd3xDgkXWDAhIaEcedS2tWikiaTBsJSr7mvc17tPctWaGTPGhjxqqy57e/xDeabVav36qe65Y56PHOt+YEfDIVrHLitMoIusTLw0mnVZbywdoBaJkdqDxcSiQ+0dcKXAWy7QwdBY4DCS16jBEB/gWkDENQwQUocCpAbnLfJY6hHERmANTud+EzszcXBrUvAGlHQedWBc2sOTLPkGDvwYb4FbBC4EClrlxwinHpXiFhSKEdoaHAwh4kotk6ECL42VvxsNE6kUOM+tB+4DG+RWSXQerrSZ6EwISLVC54BDlFpnLEgHDn2FOE/GMhpDxB2C9GV+Q2ti8GPu80U12LqlVZ6koJ1yXtdcpUiH0GZSCTAQfpnABQaRRe5RgJM6QqKxYPFzSmJ6GWONVZhJ0HJS3YFgXbaPvheWbt0G/R4IVmEJtzxGT9rufrhjmsfIuizA2pdEIEnvCfdjVmHEX1oUrOttig+NYxNSLT+nCFKg9nIo0T5QVI1NK7M9sqMWO3xO0d7ObTHkyi3ZQ6fxAG0GYjBDRzhxcAlGcigjUCYKZyZFcIiMUhiF32YIFl1itEMXbFI6SNJgDbleEBI+knrU9+YKda4FMwQOFiNjBWHqojHGnHXvmL9N6BxSexwhHQRveJwoZN1Op9HpNNdaa+sb7Y1moz0tHdtYgd9+aoFOjjQvzkGiBkb31pZJ6MCNTaoE8CRBbmtwFHg4kDpSqUD4xF30CZ5zF6EWUo9egLHwibb7BM/pX/44+ErQHLejNEbtQTr973/+y+dW7kHgkKcqwz+wXQqP81bqEaGj05hiC3cRyw7ILsvAKBlL/43A9MYIMb+RcRoXhhG0nEFh0adWo6gB0QX+wY8s1yPMdN4k4VcaDagC15AmCdqcMBiYdDDmVkRGZCGjCBFk1gnaobExJ++zyJ3R7gnQCgWiWMCu2fhau2o2ptPLCrupujRJjPWuOothhUvOLJw4rTQa9G8es9M0itA5VmGR0R61JxKeJEpmflP/zRHdXUkirtTRMMSHXDYz+A0jUlZiKcZ4me3XV1JfudIZHqFzqIZfphpbHC4zpIC6Dxajr9i0wjzGiSJoS9QDYxRyzabTshF9yJheVpiXXmGJh8Yb/4OJlFi8/qFEmhJZ8egwqJr89ws2gfEAKSd/+Si535YIubWcwoD0GH+FXf2J7W/AHf5gIkUm1R7tDybVrKb5oeR6QBQMLFfqPZBl4S+nFSbFMukKxlKEIFAqSJ6inqObVlhW8fYjZRz2qR5cXExgFnXespehzuxnj5e8VvJzKoX0t/3EGNUfIvYHSYkyy8dluFOp/epKYe39BwwekSKQPilnoOBRQHkZRAn3Hi2lvv0Pm9WLRnXj8q7dnpbA40JYSokzZvFyXrP3zqF/HJkSDVUOX6KRzqVzbnZPlVvOV0JVUD+JVkH0RwE24/c4ZjOSp2GbJ3sUuXmyx8D7HrVL13eo1By7WRig4CIjzPLUvafL7BJVcr5lvjfnTPNGtmhSC5guRXBBZopJT4bDJfFjWmHLrKSU5oPcx+Hk0+zv/l24TbIphbK8RA37LLlndu9YuEzNJ+kiDWdxmo29T1y3Xh9nRXbVo/Mafc1ll/iasaN6MG1XbzZajbX1lbVOPbsM/y27TP7yU6jdf1n9KVyOfqGrRqm2++P2aTbWWq2N9nprvdXeaLaazdVqY/neRRH3R+/d6qyvrzfX2p1mp7mwd7hckabmiq9ZefXhCSWUa5FvkDmPJq6+v320dnTePl45Pl4733nTeX+28+7s7Oh486R18fLV6c7O9kXvYPPXk97JxcvXv56/bbXPz463zt89KDi+a+ud1e1X7896F5vvO69+3Wtt7x50LtbenrePOm/f7L++6G29P9vd7h29Ot7d6W2tHay8vDg9Plh5vVBVfIuuinWkr4d6CSqgMMyW6exh3HiUakkqZyuN5ka1sVZd6fQaG93mWrexcsHK+ZzNzIct5NDFd7NkwL5bfw9SJ2u1VldrK43wtyTIdRl1M67L0a4kYGutudFcbbfW11YbG81Wq9FpsyWpi323yhfzFglcW10p5F2Ws1hkUUjf5yoZc53GrQW6LGmxra3mwqsiUbH9nfarzsvDvXan03nX2rw47O313h2+b3VetU/P13bfnbzeOtx9f/zqeHX1dHX1H+8u9t92ts/33ixG/PzKP8tLmnWbIaCHPsF0Fq/xxqN2ZKTB96/wlnWXNxEqRZgmztRqiNGPDWlkhD7LqWPWZUWIuitUNs1jFPUx0F4X3cTUqq/zI7assdPL6OAN+omxV+GuuZzjMPWpxa/huVdQgi64XlLLaWhCGswTW97mITjQumx1o9aokVZdGsfc3t5TQWLNtRShpwgve71j2Dw+oL6O4J5T06jciM53rcGBB6lH6HzWirRYDcCFRna2MrFGpBEKGNwuY5G1N6m2nrWqkDvquXoDkdEujbFYyq/R8hFCqcsDFlVwwKJVXmpnVY2VqKm3HASZtfmzQJf18Ae3M4G2jUVqsUkXTl46x8BKMUIYoJ8gato+O+38ymNrqF5xoOQVwoT6895VQGCE2luu5O8oAG+iMbXtXCVwCD4FmU8FiWatOW/ApYPQwbNcOx56v64CoaNIKsqjBwy4osNWqAGad9bxOgwzghzl1aHDPFtZW7Csv7olfCgr9PJ54Z4Cr1FRhnRzOTMXux4Zi1VtBL74S1nPR/1RF9vlUzEeOrIo4FpyiM5ODivAYWDNxKENOxiNRdt/hvXpzmv3RayFiVzdG6Nc3YkrR0gbsEjmlM2bDJXtN9LfEv8wREoyQCswwdBJj2PUIsygCCiuaWOQ2nnkghbF/IqmV0JajHzQIY3YXDhnUOsolQIh85gBOhibSYBExFLTZI/GhZmJB3MssKEtQnP9ucVhZszh/Duzkz6DLWVG9xhMJpP5w88oqwNlRnVe1TipulRXKQuNsZrnjxehn+8MuQmPrkbWpFqA0Q+9IbMdG42lx8inliuQMfk8xkHzJm/+x/w3muFlqQMGaZy8qMEejQh11guhx3xgUpoDBBEJwHy/mWkYgZTvKxCNMboCoi6fP0wX9gnaewBG0o/TQS0ycT3HoT4y9YEyg3rMCek6uZeM0BWps05TBqu5yixl/+xgZ7e/d3TS39l9u3t4dLx7clqLxYugzC0cGotkFgMcSU1zjGcOJsZ6mj5JHyrhfI5JQUIGETEam2x4EqQnp4U3RnxPmABhojBVCQh24eefJwiChqSehtLGOgSbak1CFDCSQrMgxWkGqwVX5EzlGDKztJ9/zsIDhlkiV+o2sA5r+9dcSREO2F/IfEiOYRH8xIBDGql6ci0dodV5yBEYmTRROT4xBWkZU/nFtQ/mNzABRiX5QCryR1pVMr7anGOQ78Vc8xE6kGR6E12BhFsUVUEj6sL4zHD+qCbxMg4hkfbMV1LIo4BohqARhYPnE3ymFJT8jkZaNOv+yLZ5EpIFsfvIZtiRiVCbA23sjoanmZmVSrWyZgNR1QyruTXmoygehVt6Pg4sxC6b+x45ZnZNqzwoBecLP4y5DG9RKfP38rvQuIxQZzfcfK/NhEdjhJUaVf730+vZm2r25n7HPNjw8DacKWfq6ocH27tvTndpSW3sYxUugYlxPua6tOUJeivxOgTU0CV55qBX1NBz1cXd/Zzu/99f/Lm+v8ivjR5vfD1RXIY2YrCiu/wq9SG7spPSu6WPLvLb1GWFjY3zRHZ3R8ngzKrplB5n83G6Ywnp+EA9NiEvG89//9uJpXhk19HZ1yD5BZSF6963HO5P84nEEygUH4d8Jwj/Q59DPAFS8aHIPUiX9MNKQukbfeL5Sd7LfwFf8/nSI3IV02p9WxZrptTCr0OnfIycdHzfiNmMIkzK51n4FmOuEbO/22PT6X8AenjP1w==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Offer's Trades"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/offers/{offer_id}/trades"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents all trades for a given offer and can be used in streaming mode. Streaming mode allows you to listen for trades for this offer as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trades created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"offer_id","in":"path","required":true,"description":"A unique identifier for this offer."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"base":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"counter":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","base","counter","operation"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"ledger_close_time":{"type":"string"},"offer_id":{"type":"string"},"trade_type":{"type":"string"},"liquidity_pool_fee_bp":{"type":"number","format":"uint32"},"base_liquidity_pool_id":{"type":"string"},"base_offer_id":{"type":"string"},"base_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_amount":{"type":"string"},"base_asset_type":{"type":"string"},"base_asset_code":{"type":"string"},"base_asset_issuer":{"type":"string"},"counter_liquidity_pool_id":{"type":"string"},"counter_offer_id":{"type":"string"},"counter_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"counter_amount":{"type":"string"},"counter_asset_type":{"type":"string"},"counter_asset_code":{"type":"string"},"counter_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_is_seller":{"type":"boolean"},"price":{"required":["id","paging_token","ledger_close_time","trade_type","base_amount","base_asset_type","counter_amount","counter_asset_type","base_is_seller"],"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"Trade"}]},"examples":{"GetTradesByOfferId":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/offers/104078276/trades?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/offers/104078276/trades?cursor=107449584845914113-0&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/offers/104078276/trades?cursor=107449468881756161-0&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GCO7OW5P2PP7WDN6YUDXUUOPAR4ZHJSDDCZTIAQRTRZHKQWV45WUPBWX"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/107449468881756161"}},"id":"107449468881756161-0","paging_token":"107449468881756161-0","ledger_close_time":"2019-07-26T09:17:02Z","offer_id":"104078276","base_offer_id":"104078276","base_account":"GCO7OW5P2PP7WDN6YUDXUUOPAR4ZHJSDDCZTIAQRTRZHKQWV45WUPBWX","base_amount":"4433.2000000","base_asset_type":"native","counter_offer_id":"4719135487309144065","counter_account":"GD3CJYUTZAY6JQF4CEI6Z7VW5O6VNGKZTBYUECTOJPEDTB7I2HZSPI2K","counter_amount":"443.3200000","counter_asset_type":"credit_alphanum4","counter_asset_code":"BB1","counter_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","base_is_seller":true,"price":{"n":1,"d":10}}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-transactions-by-account-id.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-transactions-by-account-id.api.mdx
deleted file mode 100644
index 29f2908405..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/get-transactions-by-account-id.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: get-transactions-by-account-id
-title: "Retrieve an Account's Transactions"
-description: "This endpoint represents successful transactions for a given account and can be used in streaming mode. Streaming mode allows you to listen for new transactions for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time."
-sidebar_label: "Retrieve an Account's Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlfdlu40jS7qskdDHTPbIt7ouBxn+077J2yeopVCfJpESJm5KktoKBuTkPMcB5unmSgyQli5Zll22q2tXz68JVkpL5RURGRMYXSdrfUj6ceqnb31NZVXUC2/dSX65SGvJUbLi+4dip21R/ZngA2ZrrGLYPMHIx8pDte8ALVBV5nh6YwMfQ9qBKrvCA7mAAwdRYIRvAaFoAbQ2o0AYKAoGHNGDYwPMxgpZhT4HlaOgG9J68B9A0nbUHtk4AfAeYhucjO5zaRuvneD4R8hHMA/4MbQHECEBNQxqZwZ8h0PORaUIMTKRNEb4BVR2o0DTPyXMFKg42do4N1oZpAs+H2AfQD6dBEJsG8nywsJ21HRcGBLaJPA9AoAbYczAwPOAh/4rMv54Z6gyo0EPA8OOz6tixgD+D/v6iG5Dbkqt8IgvB28+1gmaAiCq2s74KDUMsGon91CIqRtBHGvAMW0VkJAYYLQMism9Y6CZ1lXJchCEZXdVSt6ky8vuxCXLbvTtUtdRVyoUYWshHmDjKt5QNLZS6Te2N/dUgQwziKC70Z6mrFEEyMNJStz4O0Flv2l/7n3/92wNuoJiGChZoC5CtOlq0GBAo0EMsQ9QjZnh0u1BmooCnzpAFU7ffUv7WJQJFI1NXKbSBlmuSj8qFZqfTqjW5QUPsVLOC0Ba7THtSaXaqrdEk1xTFXDHXrDRK4wJfKw6ylXJN7HK1Serh4epR0cj6ByWXAcLbJ1rq0PSeqZkFdmApCEfrGoaOR5YOAs9FqqEbKjAdNVQmUld1TBNFPuToACPPdWwPeWHgGMRKoZvuXQUBF04Ne/rVdxbI3juGowMIMFIdrJ21j2H7aIpw3ECCQAkCLXKiJPMyTfFxtR2sofdrrSHPmNrwoAcRNZzoGACRhB7wZk5gagC6LoL4Bty5kesatmoGGgJ/QE/9A/wCPRXZmmFPfwUOBn8QuD/AL+Sf/cdhEEfRj6eBhWwfGJ79n3/9298Hng80pMPAjOwfTvsd97EDi2RE6KmpSMHUl7hhTMMy/Hcapj9DwIIbwwqsg2OEqxyZAiM/wDbSbgAZF84fhjaG9hRFa04T4RmKAtcA2iBwXYT3A0MHMzwwg1h7DJ9D7iKp0UVYd7AFSSrACHqO7b1itMMCIu2Z7WjqrX5FU3GD7Zf0qw4NE2nvtFwP+WH2xlHqO7hHNBd4zGLEcUjUEFmfO1N4NYmkEOKsForjmAjax/UPk1c4/svDw5er1ObaC1zXwb53/bhTHFLcY7iSCRmKIv+cqBHtlamrlOrYPrJ9MgS6rmlESSAz98i4bzHBoGne6WHG3YvoKHOkEs9zMdHbNyK8r6ZhL7yYKi+M85Cpf3/UDCP9XFSELuSH7m8vUg9XKR9Zrkn85IwRHx7i6/p7NOmXq5Rv+CaKzWGjjf+TieRitPqpRHogww4fNcKlJrH1HZ9AloJI5fN9VfZJKDYQYgxJZBo+st7gVxaynOe2eLj6KzvmvkD5yaSKytafTKhjCv7JBEO6jlT/Z5PKxUhFGvrZxAq5HNJ+NrFirOankuxkUJjBjlnjMVKfRMfRI2NeELP8U22/PFylDO2cOgdJDC30pxgROJuFjyz9nLZXqRn0ZmcvfJZtjoXeo0UN22cZMnjPOL9C/7wQToBV9PV5Wn3UyoW+jzAplcq/Z68n1LX85RvPP8T0hZqGSQl1TM9frWCDztjodMTXc4Z8JtVXj1BkW0Vnx+rocuLH5npJhaQzvqQyGajOIJ6+YDcLbr7q6LwJHn3566kZXvMMZK+Q6bjo60bDZ6eNqvbvfW0hH744hmj16gBSo3yNPj3nByHjCTB6SxX03QWKlWuxifep37E1442bJenUKE5gvyUpW4b9lYx/cU1f+DIma6z/044L2j+K8ZgU3iPWszTyVLAXv36DaI24MGQ+w35bMJ8b+BVO3zE4EvvrFLqvh0FwjIONj+FX4hFhI+2tfvbwFkMcYkAJLPfr+/bMs9n/iBh+/2eFSOzjEkK5wHJjCpOLDNtG+C+s4Gv5NXZJlaj5RPWTesOI2rKxnf/JPr/f1GNlSGx7frYZv7wPPt31nm4eR1WebwwnSf9Jin+e0OPZ+ck6fHl4eMn7Uw9fHh77TeHKdJGPDbRCWftwkhFvaJMRYZf0acPkwDyjyjE1833Xu81kZlH37NpHnm8j/8aLjg1uHDzN7K3hZcq5Yak/afCVarvPtUudYX8yrI66ojgUG6P7/HjA5Rv3o1Glclcc5wRu3C7zjUKzP8jEO/X/EzWXf/tb2Mv7jab+FnZLfyO9x1h/5NPloxmG5hlZ4jhRZBiZ4oUXJD60Tz5dYpkTeEliRYalZIYVxWcCh41d4l5PeiWP3ZDfD42N1MFBla1PXI28T+RBcWkznMQIkNU4GvJQlHlFF2VeFESN0hUesbLKQUVRdUHmVV2SJIXlRQlCmhEUXmF4EaGTZsXHzH7fu8s2xQLHdJuDFtfI1/Ol+9Z4MmBLYr82rBeYVrMriEyNY0Uml68IhSKXq3efcoR3IEcXeRmGoViZE6XnXYTPsmbmKMa3vSNdhW5zFfpMWHwfuSPp/T7tM3ya3HsZ3i50vA3xQan/5zHw//ZSzJ12FpIhkYh9FeqkMPi8mNxz91TimU75feq53k8ZfnQeERU9l4A/BPghVp8y/RRD0fI1RV/TUp/mbjnqlhMnzyuM29SHc8wrJD0lU4wsiCzPUjRNiSJDnxQsiWCfEOUUTVGxiufw/hkhpk/pbipLXpWinZ1Ieqs76a5KxqAalNldf6Lv+sOO3JpUWLnGr9JTo81N7sjwSbaU3ZVV8t9aeH0n+/RV2uR4tUn+lzt+WDwZlFuO0FC+m0npdiPvSXQXtjN0OmByY3fdk0aeKhrjgmiyluBF8+fTq3zs+uKjPJ07jqHXqpKp3es5174v1nYVt7nt2Lgp4YrGtQfOtjJ22+aqkx2Ud9nucq2MpZna6DU531zwdHatBJM7ONFHeVjq6LvSpBZks789LQz3tiKvckzhU92j129n6sj9BFPyo0p+FLLDXMOfHq9Se2rO3kh0ySxLo1rH4BS91TIzrdawQNELXadsKyPkq5nZggvHV+VmMbYY1VNji62NK5rWUPThsqMvnV477ZvL+V1lhLIt2LkvLWeFRb5T7E7iWpwu1HHFLixv7YfLS15r8qOZGxQDJvbVprYu65XdYDRQNvdmvjHzJYoZSxQ9aPdHXTnTQ0rGqc7T5X6k75xadxfZQaE5CedbHKcKRSl4bNkORpNxQC/dXHo5q2YEZrRsctqEy9JubjpaFu86tWy3ZMYlPO88RKek8k6ZXPtPlDd7Ku/HgvvEv569Xsb/LXXaZYtFWzM3yCMrgTXn1LpfPVozJuLPufon3voj5f3ttycE+TblE074tF/xe0qcK+PcZiWZM6lsadOO3USLXS2PvN3W09ip3JtXNbRIj+RsrqM0c2Wc8/Vtae1XdwYz6tuDQi7gF7xryvc1Z5jLNIcLiwuxv5xrWz5pTB5bj6nDHrl/S/OcKDEMz9JhFysh8X5SoiFV0nhNQAKnqZym04oqaZLKUBSiOEkTRI7SaCTrgkQJNKNApEFKFyVBlFRZhYIgXII2ZRsCUy4Wmp3SqNtpTMa1ep8blbqlfrXebvfzTLbRK3D8sFkXJ4PBZJgbj0bjQXacnDax0d1al6NNSa35WbQpsdw/B22iKUZgGZqnZV6iRVniqB/Hm85jXYg4JY/KA3FKPNMz4nRG8VeY0wXwH5nTPlzPMif+mhZD5sTe8ux55vTRNPMqc2JpjmV4mWEFRqQoiX3OnD4Oe0nmlNP9crW1yDPzHFLcYds0No1W3l5ZjU5pW9n5o3rGMpt0AdE4GzGnujCgwj347JZa2qGtFitoj99HxWzZnfBjSqjsOMmr73bDkpPJjAXxvoTsXGMDN7ugpraDMVKWm+MkjUZnHK+qio/ydBql0n1dxuUsM7CY4XoazLkuZPvCFJJbPnWus85QDbWcWcKMM56gQPDECc6x6+GwFlAWzbATcWfge8fhRaHak+B016h3Ou9lTjGW+FbmNNrqk5hOpTR1P2U6Ddgs8YE5SI8aRY+qo/S9nx1X9Tv6HqfhYDdoiSOPDM/T+rpBHxcjzivjhjr/MRH4sviFd+M/Wu0Zs/mTK+9iTqnJ8dr6nfiNu3bZSIDfPMHPjsWuUZhkfWc9toRhn7/3eruOK/IGlVNnkjg0Vrzbb3VYH4a1cWOYya4G2QF2+yFGM6H+78XP1gO3nQD/e8ynl5bayayz5o7SVc/L8MOsc7o678F/xkxsx0bPmIk3GE4x490XJj1lMs7nhfashLX2MucKjOBnZoVCpuOvlbSL0zPNFMTlzre8ip4bDiyxp4wVzV7d1X3DmNsrZ9bYLAtNz80lZya8RFMcz8gXZyY8x4gaI9KypsgqZFmREpCsUoJKcbpMKxrLs4hCgs7TEq8KOicqPC0qLCspkibRCnORA52PnaMlZyYiTXO8SF+OmSS15mcxk8Ry/yTMhBY4XqBlXpApWuAYhvuBzOQs1oWYSfKoPDCTxDM9ZybPFX+FmVwA/5GZ7MP1HDOhmWuK6zPMLcXecvQLZzofTDOvMpPY+RZNc5J85kznw7CXZCbvZAqTbKnTE++zj3XlM2bCOo1JrDh5Vr13C1JngoU1lEXD4GsIBc1acbxVh17xjtZyaDHv9tWqnIVabNZcs0fF3pYf5em0Cmkr2LGSxDaditX3g5lXUDi4LtEDtlioMaWOLVUhk5cb6e5OYCZycVWRsCnRGuu0N3g+sJE2seZ3tuvbQnZq8dCsrNU/gZlMGKm3Pl4FTdvU+47enm/XuN0ajOYZWcf+dCioxVUJV+44c53mNT7AYbWf3803TuW4GC+8XmEGl8XPnYd5GzOxlXW89ix2MsUyTHvlFeKcoDe28TzfLUl2SckV/HFn7FapAZtvd8p2uAC5zaTTMrITH8PwrXce8ZXa01Y2jQT4W3OeS4DfPMH/CDOaqkdm9ILN36z/u/Fb+Z2XAP97zORzeWNi65ysznvw38ZMqLYAxba+26nbKZrcMUJ53VrNcHY87Kudpn0/zOvrGb5vUCu+0sYTm+pJ+jYY74YsmmbKQaun8bQFmwKyGN3J5xVzOdBz68TMROQ5WaQpcc9M9jehzZBpOiCwjRXCHjq9JQ2Wh55SlqbaiHc1a7hVmcFvF71NDemUjigOqqwqakhkGEmFDC9LkiRQvCwJEtQoXmUYDlIcjSSF0WSEGChBWdMESeb+2qyG3PcoXJDVJLXmp523JJX7J2E1pMJlWI4TZZrlWJr6kazmLNalzlsSR+XjeUvSmZ6zmueKv3bekhz/yGqicH3GahiK3KnGyH1aDs9b5E9jNTL138dq8me34xK34VrHQrdgzUylvFlVK8MAjiemarcOd0A8K4SbdyNfK05qazTKFXB1WC507oaOZtjYHCv6Lqcvg66YLfmbUXTzU7Zf9GOX5x5LiWJhrRVMt7Piq/oa9ReN+dZ3R1WYVtzOSsxlK92S28xXPLXJTtOjXH0+bg+Ldq9N56azRrBlg9lquuIadn5RTU9LxcJksx5m7ks//u416OX7sQnezTQ6nhAkYRqXxX//GVD2eHfZcl1rxb76QKW95I615Pu77AnxG8yUSYCfPcHPrnlIU92FnePvi3febHDfyvKjGVNHwVDzM81SeslXvOyILSlR7Ry1AU7W8x3432Ean8uDEq/OiXe8B/9td2dJlQ4PB410ryJVFnyekzAcGuWVJQwa6XUnR3VhPzsTK4UW1zanPYfe0d0aNZc799We6Pmio3CNdJ5fu/m2k+tmGVUt6Uyuk5hpSBTLiDQjXPwMRKVVReIpnaNZxFGspHI0QymarEBNpURFkZAu8ZATBE6GnMarskoLiNx8zmgsxUvyfwFbEC/HFpJa87PYQmK5fyq2IFK8QDMMJVDSD2cLJ1gXYgvJo/LAFhLP9BJbiCv+Clu4AP4JWxBfZwvcLSt8Hls491zLX5wtvHB3Frfh2s65LTcqBgsFE4+75Z5aMacdYVvqTqmCCSv3rsAPGVZajwW8QOucog6DWDnAtp48zhA7A2nutGqgYEcedwb9xUyn7pVCrtXk/WU+s+uJelmhco3SMt3ZjPviMNsTtULTduQso9Oaztn2FlWWQzOdD+qqu16vexRX602Lf8IZCPTygwRnEFvZaQ2TVOaXxU90d9bnVsZh7dn/OH6Om3jFBPjNE/yPMBN6cKx93393VjL82sCtmAnwv8dMPpe3JbXO6epc/u6sXYsy+CCY01que9crZbozr1mkdhbjNDKthi9NVp2iN8J8oaS1/UGu4VPNLZpThUlmSGcMpNc45I7GXJ1zt3ahkGv0p2Y9eylmIjCXf26E0llNQCwjQkFDFM0wLJR0CjGKJCFZhAqCOq3zNKfLvC4hUeV5nZYUmad1StaUyzxu/1nMRKIoSqD5C55jJLTmp51jJJX7p2EmjECLDC/ILM0KkvwDn7c/j3Wpc4zEUfl4jpF0pnPM5FTx184xkuM/MpN9uL7ATFiqz9C3HH9LvfTE/Z/ATJj/PmZSPLullrhdH58+5hnt6dHP2QI2JplyBc+4FYS4vkB1sT1mVF6iW6um3l75/W22Hwx3RnxWGcWL3BgzycnjXECLd+YKb0VVyi8btfFyVedVb8tg1iwbbbay7fI1FW8bUqcz7wXrMs40iqVSvdrjs7qTmc9kPb8r72q7SYcrtOh6e+r9GczEz00SMINhvctJSZjBZfFfAHojM6GKcTe6n5QNRt/MBA41GGu5dStGsKNl+05v9ZVdZSeKA2laFE2Vi/wsf2/OB0SfwmuYr9WeVMlOgF8dFewE+M0T/I8wg/n6WPu+APRm/d+Nf4ddPQH+G5jJJ/KmxNY5WZ334L+NmVRotSyOPWGUXjX83brueCZaStjc7hpwhQawmlH1WmVhblfV1SaXb9XFLFxJXmcwcGaNRS49T99VaKnRVJp2yyxMm+zASeeT350lURxDifLlmQnLyBBxkkRzEDEy0gRNVilFERArSzLLIAHSoqRClaEFhlUEVld0XpMYjmcEWqU4+r+AmciXYyZJrflZzCSx3D8VM+EYSWRkRmL4H89MTrAuxEySR+WBmSSe6SVmElf8FWZyAfwTZiJ/j5kwn3iH1Zkn2v/qzKR0dkslzMR/5Yn2jzGTOx7XY29jzKQEB1VnNBo3AjzplvytYOQqliXwdWbNFydzU+uoTS+XqaOOSXdn1GAxETscV8sX8ivbt6uzkb4w6Y7hYmE+WWSqnJp252vpz2EmMAEz6C+F8TwJM7gsfund+E+YyWcyg7D2xAnwx+1gk5SZxPA/wgxQ81j7DhLq/178amaTHiTA/y4z+VTelNQ6p6vzHvy3MZOh2zFmk4kaCL5ZHLGNZbWIoIIXWCksutbdkM6tt+uK5PL58bBc6fa6tl+YTxfVZj2NGNUoTdK98TBft1bLltWX5rOdYLULF2ImEi1enJkwigRFURURx8iyyEiUInE8h1hZ0URVkGiVl6DCK6KqMpKk6xIrqLTKKQLNM5qq6n/xMxOGpij5gs9+JLXmZzGTxHL/LMyEpgWaoyVGYDiaZWnmRzKTc1gXYibJo/LATBLPdIaZPFP8FWZyAfwjM4nC9SwzYa5ptk9Ltzx3y1Ofx0y4/z5mUj67pZb4kiWfZSbRq1CfY39cgi6e+5ozlKx7tOF4XtSL5eH9wpXYOrXSB+vidrgvR1Z4HX8UdHIojnPZev6OqmatjjQb1IbNpl7dBHQnU5hOkGLZlKx17/KlfL1XHEzK98Fuaeq19n0Tq3e1rq9z9HrdLNWl0ZyeilQxu05PCrP6rFaIyoEf/YwHv1smYAVtSV8sk7CCy+KX342fPT7jge27hFVxzznWfS883f9K3ZkQf8fm6wnwsyf42a0jiMPNaAk5cQxLes2qeOgOIXaTM0e1ut7a+g2Wbuaa5v68qyFI1ezper4D//us4BM5S+LVOfGO9+C/jRX8sBSUkBXQAkPR4tmnydcONrUXHyVn5K1S7lz2MXKRkRHH0ZLMUiKvI45SBChoCgVVBbGSprEyw7EcLaqqJNKiLgsSR3p5HMvSUGAE6q9OJWhBvOCDIUmt+VlUIrHcPxGVkBiWoiSKZXlJ/NFU4hnWhahE8qg8UInEM52nEk8Vf4VKXAA/TiVIuL5MJRj6lqFvqc/75Vgy/99HJSpn9+ESX1pNw8e8w4oxzxweI9dWqrXZ//GF0yqzIKLNqD2C+WHd2E6dubgqOgNnw1a1cpfKlYvrKdZXgbiZc3JEK6IK6vEVO/Rot2q97mxZtIqwvvSN6Yht99uWRfXaJUZB+jo9q6Tn4mxWGMkNcVPICqXCxCyuSsVePdvZjHLNDhrKmC1kxHvJ3/DBiBmtO4s/hV7wbIJHuJvy2ugmKe8vi195N342Ti/s2G9G+0h5XyseC0j1POKrBWwifFsq5xLgZ0/wPxgcJ+v5Dvzv0IvPJV+JV+fEO96D/8ZHyCmzVi47vfuus1wy9Zyiys00VLpVaTzx+UxBKOpCOygXWwq1WhWbBWfQsgY9adCtOrlC6b64yfFjZqW2M/58y1YsXpkoufwFHtSgBUaSOeYpvcgaWMOOCwx7ZfjoP//v/25Ma4p8Unmc0o3OyNxOKrWVms+5ij1xtfLYsKtDTinT9mTcCRS2Zl+UgkicrKs8z0KNgjyPRB4yItR4KFEUJ0KOVyDkOZVlaIpjBUlQFVHneR3KSGd1UeMv82x6d8SPSz2+nW0Nc6PhXWXc7woFoT5psfliPcvUqt27Lt/q3nealT5fF8Qc27sfiBegIBxHyfwF/+BiUmt+FgVJLPfPQkFO/yzrj6Qg57AuREGSR+WBgiSe6QwFeab4KxTkAvhHChKF6wsUhJH6tHDLSLcc8wIF+WCaeY2CEGOwkkzxvMjRNMdK0hkO8mHci3KQVsA2GnjdWpbpcWV1156lh2awKQ4KvUFXq+B7brqW0ktZuuOzIQcpb8Twt9h0Y83BsLRU3rJJxcbHNvt3/7WI/atcjj0Gn1uu9EIQ/iqr/K4uIamR1irL8mTkOXfrVmPat0uF9J0VsAV1WOPKa0WkJ3XPWcBKmpm1G7rAV4XytDrmXHW7o3vTbiuYGdTAn3J+eaGXB9kff/OVUuH12NnNPSOqXrDKMo4yVJHEpSv8aCQWu51WrVuikD83CoWdgNm1uNib404cHBco/sB17PUKD7gs/gvd47fdfPW5PKCY83QznQgfKYuP4zdP8eeKv90KUgHO/OFG3M053ZwoXreUpcziuCswd9Vmu/0YANns/b3od7JKxSO/LjhXev/tRYnx5731x/G/x4M83ZSSWSegjtK9/7GQy65OosdCzvIgb7uqrPIZuyvMrCGuF7xCjyvym05m7mJ/zZZ6KOeV0/Koh+u18izjO/0tmw56dzMnX0rXx01PHjjFvuLc+6XG/V2j61Y2ZvSHDh++POxfVym08ZHtRcXx799SC7RN3aY2117gug72vWvPxwhahk3ozAqaAdqXeV+IBv7MIbvXFPlhLeGTquBY/H87bKqG9vCkBiKqIkx+vW+IGWDzbYVU6ipFyjRsuFERlurPEOhH40AL+WsHL1KEnJ2fUQ+Ibd8yZ+kwEtiHWb9cpQxbdyLO6Jtk1SrRvMQwCHvR1dQNdUOHRZNlQbw9jgIudlaGhjwAbVDp99sg264C3wEa9CEwbODPEOhFch1Qb0DVB4Y9RZ5PLtMARteh4bxwdHilix0tUJEGlO25KcjMEOgOtoA/gz4wPICgZyBMoFXH9gILHS6FK4ThFAHouqahhoUHwMiEvrFCZDgZ4yJMJoO2iq4dbCDbR1okCEYuRh6y/YjjgMCLhDoIlHcwugH9meGFmsf0ULChTRFQkL9GyCbwkbZPr2xjZ054CDCNBQJraJrI966AhlRk+xiaxg5pAG3UGSQGuwpngJ6HiM5egHAoETishu8AL1Aswwdxx7wCywDhLVmive8CBZpE2SvgYBDFAkArZB/kiF9NJj1eefPMs/63e8Lv8QX98sshPDUUVbTYe0Ka9mJnVAeja9vR0K//q7znn/Y/7QOcCm2gIPIV8ogtVwYE6qDbuAIQKNhZewiHCI6NgKOHVnm0da9Q975ra81RvYzvOKaX8bSFRyztAIyIO4WzqY7lmmhj+Fsy/9YJMPE2YtArsEaANNUsC9ka+So0FLQJMDBsz0dQIxdZcGHYU6AZGKl+uIYqNE0v1DNc1mlgaAhEEaMgD8ycdWgSzTJsw/MRBgcXD93xYBsCQUwMfsFIj5w51L/wqOnfQc50pkcbrNfrp8o/jrxWTGeagdc2Wl97gX1NdqEZut7vH7+S4AGeQ8IEqospJm1D4Nin0RD5DlZnho9UP8DQBIZFYh5Z4cqHK2R4wIJzB4P91gGUwHJ/vQElBwOyz2ArijqoOIEP9iISA+7xHl3D0ZACPXQF1BlSF4CMjutPIEGZmPZogKnhzwLlRnWszN4OmamTUUxHyViQWDpDwstQkXfYOjOG7SNsQzPylPKgWih+Ld11vxaKw2Ljrl3s9m4s7ddwMXNIdzAibqGgqWFfAcP/u0duwPBnACPDDymtPQ2lJEnCCEVE6sxB2iH7/U6CFrQc7SNpAmiOGliH9HML/vGPNQKaA2zHB8jWHOwhgAPbJkIczEgWNEpSEBB/0qBJgimeQx497R//iNID8lykGtA0t+HU4bVfV9A0tFDBr892PkQCAyPgrx3gIRdi6JPQslWE7X3K0ZDqBK65t49FkrRhkUIM2n7ofooTmtE0oGKYJB7JVTHnu3kSGCT2LGjDKfKAQVxvbV8BF2KkXWvO2n50Pkd/qqrj+oYVpkSCub+SpDySEB0d2KTnBn5Zo7+bJojFneEB6AEI/pnKQzfcLMh0/0w92o64SNgzxJZ3p/ciN4uVak+6ZmTQtaNf770xdZVSHduHatiNtmHYlz+IHXf3EgnMcPFTVyel4NPCD1nQMA/3CP2f+Hek/WyoyPZQDCvrQnWGAHNDejOGRnxXNxB+/OY6+uaIuE82MPw2ak9Hk3qZRjVfbPWK5JKbmW+ZYVfPdTzfgnYMsot8bKBVmFCz0c7wdw/0n9bST6qMb6GRUNieCvMqsjXXMWz/uC174NjSe7oFkdWGYGqs0HELIw6234DCjdywwSMnAJajoRvQe/IeQNN01l64F/gOMEnytsOpbbR+jhd5zQEs3NO3YZhATUPaIZ8f1jlqGN6Aqh7uH+fkuXoMgbVhmiScsQ9glBYRxKaBPB8sbOLRMWFAYJvII84bNYFJ6HnIvyLzr2eGOgMq9BAw/PisOnb21VR00Q3IbclVjwluP1dInIgqtrO+Cg1DLLovCJ5YZN/+BJ5BdpJwp8WkJen5gGRKUlTGOGPGNaFhE28Nne7bnoP9fji2Id5xe2RhqSdNbI8ciM0czycXfPtGdpEBNh8eyMdhIROSM83woGKSJqUOTQ+94m1ZYAeWQlIBMUjoc1FRA8JEqRsqMJ19MRnWoqpjmigyvqMDjDzXIbERepzhATcI13dvYwTiveq9RR0dwLD6wNqLlokYbbQQRw6bCnnie5TTUETP9+ISicKTg6ODRIJ4wJs5gamRShRBfAPu3GhpDVs1Aw2BP6Cn/gF+gZ6KbM2wp7+S0u0PgvwH+IX8s/84dPIoOvA03NCA4dn/+de//b1jkrpAh4EZmTmc9jtWCAX+uBEINbbgxrAC67DW4cJFamPyd55tpIVbHQhPiUI3x6SkjpaRJoIyFAWuSUILXBfh/cADJZlBrJGaJozrQxyTNBEvsDCCnmN7rxjosFhIe2YnmvqOkUKBPm6kHvLDpIWjiD+sug4N4s3HQ0CiYNRO9p77SHg1iYMQ7TsC7y/6GkE8kfwLeYMNIvo7o/mXLloGBkbarxHr2meR//zr3yQyFdNQwQJtAbIfVwsCkkJYhuQ1kv+e0sAXddh/CO1tXPKDbrHk9fDl4So1Q5C48LFVlVVV5MaXK8ZZM3PPsVNPWlXlYj/18PD/AS7XQEI=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account's Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful transactions for a given account and can be used in streaming mode. Streaming mode allows you to listen for new transactions for this account as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"RetrieveAnAccountsTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU/transactions?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU/transactions?cursor=122152984477229056&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU/transactions?cursor=94658837230923776&limit=10&order=desc"}},"_embedded":{"records":[{"memo":"","memo_bytes":"","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBYSOAM7D42RMUN4LCKCFYNXZU3F7TJVKD2NMR672J4372BCH6DE4BKR"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/22039478"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=94658837230923776"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=94658837230923776"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee"}},"id":"4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee","paging_token":"94658837230923776","successful":true,"hash":"4826a3d41a5a795bf795767d0fb5e39c4abbcf695cf888b3578aa126b5b257ee","ledger":22039478,"created_at":"2019-01-18T14:40:47Z","source_account":"GBYSOAM7D42RMUN4LCKCFYNXZU3F7TJVKD2NMR672J4372BCH6DE4BKR","source_account_sequence":"90296735301107721","fee_account":"GBYSOAM7D42RMUN4LCKCFYNXZU3F7TJVKD2NMR672J4372BCH6DE4BKR","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAHEnAZ8fNRZRvFiUIuG3zTZfzTVQ9NZH39J5v+giP4ZOAAAAZAFAzGcAAAAJAAAAAQAAAAAAAAAAAAAAAFxB5cMAAAABAAAAAAAAAAEAAAAAAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAAC+vCAAAAAAAAAAAEiP4ZOAAAAQO421wcb/JYfBpnYEJzHpMyQnrM8rHd4PUoyHXpPlvQAUGzARqwbX8hcLSM4tlk51AwbuZOaZfWCaFQfzFZJuAA=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAVBLtgAAAAAAAAAAcScBnx81FlG8WJQi4bfNNl/NNVD01kff0nm/6CI/hk4AAAAAI9MEZAFAzGcAAAAIAAAAAAAAAAEAAAAA7Nxp7lmV7taqQfqoSP+tlqjOHWeANaQYFqhDkCQERZQAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAVBLtgAAAAAAAAAAcScBnx81FlG8WJQi4bfNNl/NNVD01kff0nm/6CI/hk4AAAAAI9MEZAFAzGcAAAAJAAAAAAAAAAEAAAAA7Nxp7lmV7taqQfqoSP+tlqjOHWeANaQYFqhDkCQERZQAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMBUEu2AAAAAAAAAABxJwGfHzUWUbxYlCLht802X801UPTWR9/Seb/oIj+GTgAAAAAj0wRkAUDMZwAAAAkAAAAAAAAAAQAAAADs3GnuWZXu1qpB+qhI/62WqM4dZ4A1pBgWqEOQJARFlAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBUEu2AAAAAAAAAABxJwGfHzUWUbxYlCLht802X801UPTWR9/Seb/oIj+GTgAAAAAg2BPkAUDMZwAAAAkAAAAAAAAAAQAAAADs3GnuWZXu1qpB+qhI/62WqM4dZ4A1pBgWqEOQJARFlAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAABUEu2AAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAAC+vCAAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBUCemAAAAAAAAAABxJwGfHzUWUbxYlCLht802X801UPTWR9/Seb/oIj+GTgAAAAAj0wTIAUDMZwAAAAgAAAAAAAAAAQAAAADs3GnuWZXu1qpB+qhI/62WqM4dZ4A1pBgWqEOQJARFlAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBUEu2AAAAAAAAAABxJwGfHzUWUbxYlCLht802X801UPTWR9/Seb/oIj+GTgAAAAAj0wRkAUDMZwAAAAgAAAAAAAAAAQAAAADs3GnuWZXu1qpB+qhI/62WqM4dZ4A1pBgWqEOQJARFlAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["7jbXBxv8lh8GmdgQnMekzJCeszysd3g9SjIdek+W9ABQbMBGrBtfyFwtIzi2WTnUDBu5k5pl9YJoVB/MVkm4AA=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1547822531"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GAL62GEDMQFWRQLZXJKT4WFRFTIKPPTC2ALSD45VMK7ZUUZVBXWWXUAX"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/23895910"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=102632151958179840"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=102632151958179840"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666"}},"id":"ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666","paging_token":"102632151958179840","successful":true,"hash":"ec8d5d6e64dc4df1bc8d8c200e048d6740d1e9f680612baeda0f78678c9ca666","ledger":23895910,"created_at":"2019-05-17T14:43:53Z","source_account":"GAL62GEDMQFWRQLZXJKT4WFRFTIKPPTC2ALSD45VMK7ZUUZVBXWWXUAX","source_account_sequence":"93143259236270083","fee_account":"GAL62GEDMQFWRQLZXJKT4WFRFTIKPPTC2ALSD45VMK7ZUUZVBXWWXUAX","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAABftGINkC2jBebpVPlixLNCnvmLQFyHztWK/mlM1De1rAAAAZAFK6U0AAAADAAAAAQAAAAAAAAAAAAAAAFzeydEAAAAAAAAAAQAAAAAAAAABAAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAAAAAAALLQXgAAAAAAAAAAAE1De1rAAAAQLFFYK9rGA2Um2Vwguj4Ra3T6gaeturf4Qw/0LcG/qa/oXZeu6s7ZrB3wVVJu0m123Z7zirYoo576IS8agzLKQQ=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAWyfZgAAAAAAAAAAF+0Yg2QLaMF5ulU+WLEs0Ke+YtAXIfO1Yr+aUzUN7WsAAAAC1fwL1AFK6U0AAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAWyfZgAAAAAAAAAAF+0Yg2QLaMF5ulU+WLEs0Ke+YtAXIfO1Yr+aUzUN7WsAAAAC1fwL1AFK6U0AAAADAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBUEu2AAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAAC+vCAAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBbJ9mAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALOPGiAAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBbJ9mAAAAAAAAAAAX7RiDZAtowXm6VT5YsSzQp75i0Bch87Viv5pTNQ3tawAAAALV/AvUAUrpTQAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBbJ9mAAAAAAAAAAAX7RiDZAtowXm6VT5YsSzQp75i0Bch87Viv5pTNQ3tawAAAAAKupPUAUrpTQAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBS+8PAAAAAAAAAAAX7RiDZAtowXm6VT5YsSzQp75i0Bch87Viv5pTNQ3tawAAAALV/Aw4AUrpTQAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBbJ9mAAAAAAAAAAAX7RiDZAtowXm6VT5YsSzQp75i0Bch87Viv5pTNQ3tawAAAALV/AvUAUrpTQAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["sUVgr2sYDZSbZXCC6PhFrdPqBp626t/hDD/Qtwb+pr+hdl67qztmsHfBVUm7SbXbdnvOKtiijnvohLxqDMspBA=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1558104529"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27114571"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=116456195690164224"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=116456195690164224"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2"}},"id":"5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2","paging_token":"116456195690164224","successful":true,"hash":"5427d2719db9ca33706e9c06c04f91bd353e0e6f5185c6f47b517b338b8d81b2","ledger":27114571,"created_at":"2019-12-04T22:03:41Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911489","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAABAAAAAQAAAAAAAAAAAAAAAF3oLZMAAAAAAAAAAQAAAAAAAAABAAAAAARD8QZr6wa97ii5JeeuMJEXycVsEO1dBekjRTcI9AadAAAAAAAAAAABMS0AAAAAAAAAAAGXebqxAAAAQND+muz3883MoHmTtuhsDb4awF1U3EDJ2FQn8Ia2C9L+Rz62Z9EvH8rl81d3oPxrjUnedZmjOnptn6Agm5alHwc=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAZ28SwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACzjxoHAFQS7YAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAZ28SwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACzjxoHAFQS7YAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBnbwPAAAAAAAAAAAEQ/EGa+sGve4ouSXnrjCRF8nFbBDtXQXpI0U3CPQGnQAAAABxZQNiAZtraAAAABsAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnbxLAAAAAAAAAAAEQ/EGa+sGve4ouSXnrjCRF8nFbBDtXQXpI0U3CPQGnQAAAAByljBiAZtraAAAABsAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBnbxLAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALOPGgcAVBLtgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnbxLAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALNCzscAVBLtgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBbJ9mAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALOPGiAAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnbxLAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALOPGgcAVBLtgAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["0P6a7PfzzcygeZO26GwNvhrAXVTcQMnYVCfwhrYL0v5HPrZn0S8fyuXzV3eg/GuNSd51maM6em2foCCblqUfBw=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1575497107"}}},{"memo":"hello universe","memo_bytes":"aGVsbG8gdW5pdmVyc2U=","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27984461"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120192344791343104"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120192344791343104"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894"}},"id":"ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894","paging_token":"120192344791343104","successful":true,"hash":"ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894","ledger":27984461,"created_at":"2020-01-29T19:43:59Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911490","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAACAAAAAQAAAAAAAAAAAAAAAF4x4NYAAAABAAAADmhlbGxvIHVuaXZlcnNlAAAAAAABAAAAAAAAAAAAAAAAMOWtdEZJweWBDrIVGDQOVodinrlXbfzBfquR7AFtxW4AAAAAATEtAAAAAAAAAAABl3m6sQAAAEDwdDlpQv5IfweTkLjytpWIa+bpQv7BAHRFpMCHscM3g+WBKjXPVEnSP1BghLuy3uhvgv4LnCkI+gFEDZxwV/YF","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAasCTQAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACzQs6uAFQS7YAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAasCTQAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACzQs6uAFQS7YAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMBqwJNAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALNCzq4AVBLtgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJNAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALL2g24AVBLtgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAABqwJNAAAAAAAAAAAw5a10RknB5YEOshUYNA5Wh2KeuVdt/MF+q5HsAW3FbgAAAAABMS0AAasCTQAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBnbxLAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALNCzscAVBLtgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJNAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALNCzq4AVBLtgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["8HQ5aUL+SH8Hk5C48raViGvm6UL+wQB0RaTAh7HDN4PlgSo1z1RJ0j9QYIS7st7ob4L+C5wpCPoBRA2ccFf2BQ=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1580327126"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27984467"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120192370561220608"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120192370561220608"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589"}},"id":"c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589","paging_token":"120192370561220608","successful":true,"hash":"c1cb850f413e4038c4120bd9badc07bb8ef85a46649a4d5c9c16e578a2d30589","ledger":27984467,"created_at":"2020-01-29T19:44:36Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911491","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAADAAAAAQAAAAAAAAAAAAAAAF4x4PoAAAAAAAAAAQAAAAAAAAABAAAAADDlrXRGScHlgQ6yFRg0DlaHYp65V238wX6rkewBbcVuAAAAAAAAAAB3NZQAAAAAAAAAAAGXebqxAAAAQMzdIubro9XQUTkhf0YbDBNM5tqC/zS7fGb0BLFq+QxXT7VAS7dDMno9A2f1df4nnyeHqVl+CuKcpwwwS04JSgE=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAasCUwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACy9oNVAFQS7YAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAasCUwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACy9oNVAFQS7YAAAADAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBqwJNAAAAAAAAAAAw5a10RknB5YEOshUYNA5Wh2KeuVdt/MF+q5HsAW3FbgAAAAABMS0AAasCTQAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJTAAAAAAAAAAAw5a10RknB5YEOshUYNA5Wh2KeuVdt/MF+q5HsAW3FbgAAAAB4ZsEAAasCTQAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBqwJTAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALL2g1UAVBLtgAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJTAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJUpHlUAVBLtgAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBqwJNAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALL2g24AVBLtgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqwJTAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAALL2g1UAVBLtgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["zN0i5uuj1dBROSF/RhsME0zm2oL/NLt8ZvQEsWr5DFdPtUBLt0Myej0DZ/V1/iefJ4epWX4K4pynDDBLTglKAQ=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1580327162"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28000615"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120261725693136896"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120261725693136896"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe"}},"id":"e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe","paging_token":"120261725693136896","successful":true,"hash":"e0f3d6e327a6de01223a8f0e2b88e97abeaf1f514f95f8e7c55f18b951f09dbe","ledger":28000615,"created_at":"2020-01-30T21:45:07Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911492","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAAEAAAAAQAAAAAAAAAAAAAAAF4zTrgAAAAAAAAAAQAAAAAAAAABAAAAABhkaLZ/GHrh4vaarKkeK7PX2c581NvMfPvtTyATuVziAAAAAAAAAAAF9eEAAAAAAAAAAAGXebqxAAAAQB9XBu17Olvry7c8CqLJXqvK5csy2r3lGiP3HyR5JcryL8QQjSuwGr/LEFFKIS5Afo/jh9fCzGzJzZQ4DN1KPgs=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAatBZwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACVKR48AFQS7YAAAADAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAatBZwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACVKR48AFQS7YAAAAEAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBq0EQAAAAAAAAAAAYZGi2fxh64eL2mqypHiuz19nOfNTbzHz77U8gE7lc4gAAAAACYljUAatBDAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FnAAAAAAAAAAAYZGi2fxh64eL2mqypHiuz19nOfNTbzHz77U8gE7lc4gAAAAAIWDnUAatBDAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBq0FnAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJUpHjwAVBLtgAAAAQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FnAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJOrpfwAVBLtgAAAAQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBqwJTAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJUpHlUAVBLtgAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FnAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJUpHjwAVBLtgAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["H1cG7Xs6W+vLtzwKosleq8rlyzLaveUaI/cfJHklyvIvxBCNK7Aav8sQUUohLkB+j+OH18LMbMnNlDgM3Uo+Cw=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1580420792"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28000619"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120261742872928256"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120261742872928256"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041"}},"id":"329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041","paging_token":"120261742872928256","successful":true,"hash":"329ae48814ae29ed6d9c0bb6e398932e6a178cac21623b63fbf5d8245261c041","ledger":28000619,"created_at":"2020-01-30T21:45:29Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911493","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAAFAAAAAQAAAAAAAAAAAAAAAF4zTtEAAAAAAAAAAQAAAAAAAAABAAAAABhkaLZ/GHrh4vaarKkeK7PX2c581NvMfPvtTyATuVziAAAAAAAAAAAO5rKAAAAAAAAAAAGXebqxAAAAQFaUIoWWXLurZRFty6iBHmm65K2w5EZjldQcMsB/KeQl1Rh0UkZ7Q44JCDCvntnIhWfkl1Qipr6jZk/I4c+pjw8=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAatBawAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACTq6XjAFQS7YAAAAEAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAatBawAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACTq6XjAFQS7YAAAAFAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBq0FnAAAAAAAAAAAYZGi2fxh64eL2mqypHiuz19nOfNTbzHz77U8gE7lc4gAAAAAIWDnUAatBDAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FrAAAAAAAAAAAYZGi2fxh64eL2mqypHiuz19nOfNTbzHz77U8gE7lc4gAAAAAXPuxUAatBDAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBq0FrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJOrpeMAVBLtgAAAAUAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAI/x+UMAVBLtgAAAAUAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBq0FnAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJOrpfwAVBLtgAAAAQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBq0FrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAJOrpeMAVBLtgAAAAQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["VpQihZZcu6tlEW3LqIEeabrkrbDkRmOV1BwywH8p5CXVGHRSRntDjgkIMK+e2ciFZ+SXVCKmvqNmT8jhz6mPDw=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1580420817"}}},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28210091"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=121161418262413312"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=121161418262413312"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe"}},"id":"2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe","paging_token":"121161418262413312","successful":true,"hash":"2b8a77c7e42997280b8454e39bd7c681c58ab5b7cc288ff836c1c4b6152dccfe","ledger":28210091,"created_at":"2020-02-13T18:54:50Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911494","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAAGAAAAAQAAAAAAAAAAAAAAAF5Fm9EAAAAAAAAAAQAAAAAAAAAAAAAAADKjrtXFaprjtdoV8mYex4557fEGVYkp83K0vfUwEyVnAAAAAAvrwgAAAAAAAAAAAZd5urEAAABAKCO0IAmQ8hUJVMMfIxu1Q/DgZebmn09dROCFCKSEUZGYuzqlfJPYMrcOJRtf41wwMFK8Wj1g70EAw+ZDhKhJDA==","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAa5zqwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACP8fkqAFQS7YAAAAFAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAa5zqwAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACP8fkqAFQS7YAAAAGAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMBrnOrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAI/x+SoAVBLtgAAAAYAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBrnOrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIz3CKoAVBLtgAAAAYAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAABrnOrAAAAAAAAAAAyo67VxWqa47XaFfJmHseOee3xBlWJKfNytL31MBMlZwAAAAAL68IAAa5zqwAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBq0FrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAI/x+UMAVBLtgAAAAUAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBrnOrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAI/x+SoAVBLtgAAAAUAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["KCO0IAmQ8hUJVMMfIxu1Q/DgZebmn09dROCFCKSEUZGYuzqlfJPYMrcOJRtf41wwMFK8Wj1g70EAw+ZDhKhJDA=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1581620177"}}},{"memo":"hello world","memo_bytes":"aGVsbG8gd29ybGQ=","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28211677"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=121168230080335872"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=121168230080335872"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260"}},"id":"729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260","paging_token":"121168230080335872","successful":true,"hash":"729e441893075fe40b6a6db0acbe38dd39243417cc8717f968414934331a6260","ledger":28211677,"created_at":"2020-02-13T21:21:01Z","source_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","source_account_sequence":"94658837230911495","fee_account":"GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGpZ5X06Hz48sKzzVFo//X67YFenBLxaxzuJcPuXebqxAAAAZAFQS7YAAAAHAAAAAQAAAAAAAAAAAAAAAF5Fvg4AAAABAAAAC2hlbGxvIHdvcmxkAAAAAAEAAAAAAAAAAAAAAAD7exWPWaCVKiygoj7vEoUox3IdGR0BGEwgrfvu7xj49gAAAAAL68IAAAAAAAAAAAGXebqxAAAAQPNJSRhqEmEaKqtigW3PTPmm0SPF2befw+hH+j7hhDW9L7xDA6FDZlEvFESKAQxWBMQeV9r3D/7Y8tx5uW2WwQk=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAa553QAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACM9wiRAFQS7YAAAAGAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAa553QAAAAAAAAAAalnlfTofPjywrPNUWj/9frtgV6cEvFrHO4lw+5d5urEAAAACM9wiRAFQS7YAAAAHAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMBrnndAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIz3CJEAVBLtgAAAAcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBrnndAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIn8GBEAVBLtgAAAAcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAABrnndAAAAAAAAAAD7exWPWaCVKiygoj7vEoUox3IdGR0BGEwgrfvu7xj49gAAAAAL68IAAa553QAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBrnOrAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIz3CKoAVBLtgAAAAYAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBrnndAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIz3CJEAVBLtgAAAAYAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["80lJGGoSYRoqq2KBbc9M+abRI8XZt5/D6Ef6PuGENb0vvEMDoUNmUS8URIoBDFYExB5X2vcP/tjy3Hm5bZbBCQ=="],"preconditions":{"timebounds":{"min_time":"0","max_time":"1581628942"}}},{"memo":"Airdrop invite✅xlmget.org","memo_bytes":"QWlyZHJvcCBpbnZpdGXinIV4bG1nZXQub3Jn","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBRW5XFS5PANVBWVOHXTR6D6KZN3CEKA2JIROR5NRYQMHT5K67B3SYU7"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/28440958"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=122152984477229056"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=122152984477229056"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59"}},"id":"849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59","paging_token":"122152984477229056","successful":true,"hash":"849fc553ad0a55e75a27ad5a80047a45baa54c321043686cb7f55fa9ef3f7d59","ledger":28440958,"created_at":"2020-02-28T16:28:42Z","source_account":"GBRW5XFS5PANVBWVOHXTR6D6KZN3CEKA2JIROR5NRYQMHT5K67B3SYU7","source_account_sequence":"122138905574114388","fee_account":"GBRW5XFS5PANVBWVOHXTR6D6KZN3CEKA2JIROR5NRYQMHT5K67B3SYU7","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAGNu3LLrwNqG1XHvOPh+VluxEUDSURdHrY4gw8+q98O5AAAAZAGx7LAAAARUAAAAAAAAAAEAAAAbQWlyZHJvcCBpbnZpdGXinIV4bG1nZXQub3JnAAAAAAEAAAAAAAAAAQAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAAAAAAAAAGGoAAAAAAAAAABqvfDuQAAAECzK8e8L+dHqGZWsoOwNLgTnFD+Omu3DcVJ4Gwb71ZKsokaH+2hPLf65I6GgIX4pcyz1SgRNuhi0Utg4tGkfGUA","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAbH5fgAAAAAAAAAAY27csuvA2obVce84+H5WW7ERQNJRF0etjiDDz6r3w7kAAAAAGGO7UAGx7LAAAARTAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAbH5fgAAAAAAAAAAY27csuvA2obVce84+H5WW7ERQNJRF0etjiDDz6r3w7kAAAAAGGO7UAGx7LAAAARUAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBrnndAAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIn8GBEAVBLtgAAAAcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBsfl+AAAAAAAAAABqWeV9Oh8+PLCs81RaP/1+u2BXpwS8Wsc7iXD7l3m6sQAAAAIn8ebkAVBLtgAAAAcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBsfl+AAAAAAAAAABjbtyy68DahtVx7zj4flZbsRFA0lEXR62OIMPPqvfDuQAAAAAYY7tQAbHssAAABFQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBsfl+AAAAAAAAAABjbtyy68DahtVx7zj4flZbsRFA0lEXR62OIMPPqvfDuQAAAAAYYjSwAbHssAAABFQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMBsfl8AAAAAAAAAABjbtyy68DahtVx7zj4flZbsRFA0lEXR62OIMPPqvfDuQAAAAAYY7u0AbHssAAABFMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBsfl+AAAAAAAAAABjbtyy68DahtVx7zj4flZbsRFA0lEXR62OIMPPqvfDuQAAAAAYY7tQAbHssAAABFMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["syvHvC/nR6hmVrKDsDS4E5xQ/jprtw3FSeBsG+9WSrKJGh/toTy3+uSOhoCF+KXMs9UoETboYtFLYOLRpHxlAA=="]}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-accounts.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-accounts.api.mdx
deleted file mode 100644
index eaeaaa5578..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-accounts.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-all-accounts
-title: "List all Accounts"
-description: "This endpoint lists accounts by one of four filters : signer, asset, liquidity pool  or sponsor."
-sidebar_label: "List all Accounts"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+lyG7eyfhXU/Ejs3OEiiovNqtS9kkhrsfbFsiWrGHCmyUGEASYARpSuilV5jVN17svlSW41ZtFwkURZjqKcc/zH9hBodH+9AOhG3zqGDrXTPndWPE/GwmjnwnV80J5ikWFSOG3nOGCagPAjyYQhnGmjCU1Hk/4NkQKIHJCBjBUZMG5AadImmg0FKJdQrcG4hLPfYuYzc0MiKTkhUhEdSaGlKjuuIyNQFJfb9J22s820WeE858h1IqpoCEjZaZ/fOoKG4LQdSwCU4zoM+fwtBnXjuI6C32KmwHfaA8o1TIuTkiWbHeTaBJAzQrpXoG4y2QgT9lcFyTpkxDgnwEwAivTzWeAjBjhwyK5A5LORvCIBvQJCiY77IIy6IW+MirXhTIBL5GCAAElFfGoosQPeklHAvIAw/Th9BE57AYTUad865iaymBjFxNBxHbimYcTx03pn5+Bgd2unfrLdOthcaTb3W4e1/bONnYPN3dOz1Z1Wa7W7urOx/eFzp7HVPVnZWN9qHda3zpzx2M2xtmp8KtKCMK1j8BMjIAoiBRqEsV/IH7//c0360N7EMSpVy2bnj9//byFNpNDmgJKBVEWccMmyUxAhscjnW4slsziLc02DarSKhNJLqhHdEL2wh174RChOmQmIwWCQu6ObCR1zoxOZmfB47AORgt/chYnEqhM8MoVpYmTqf+CxAQN/KkpMaM+LlZZP1h4RcdgHtAtqiA1gdlWarekRLj0beVCDlHiSc/Ds/+Ug16YmVPjok1HMOfhkoGRoOY/okIlhz8hLEOSK8thGQkoUeFL5czXLhIGhNcNctc1mtdlcatVb79433i9VG0WFSeU/3WaJD2hbNJMDWbWEUMhEFQmHmuhAxtwnNIqAqjLZszR0rsVfqPZ+IW+o9kD4TAzfYrj6BZf7hbzBv9LPZbI5SGyDqmEcAnqEFn/8/g9DbPhnhvgwoNZMjEzIPmL4Ig5xX6LacxIBnYtJSw7ZUwPScQAkpNcsjMPMMKyWEygUmFgJ8MsEx1n6xKOCKCqGkOh8CZmvVaukRKggcRSBSgdaA2OaBFT5nvTBR6g3pGL/K4WNTBGogVQhFR46DNVS6AdAyxQI/gx2S9VF7WqpOh5fuM51ScdRJJXRJW0U0BABbhsVAwKWWjhSqlWr+NckZocWleKOTzX4RAoSKXnFUNJk08+2fJLv+en+jCYz6diO63hSGBAG16NRxFnihJVfNS56WxCPcr43sLt+Kqjs/woeaj5SeGwwLGG+x5m41AVA7hmngQ8eHxUoGMyzSqtCY81PXDpj1zEQRhz1VBjdl5IDFRh4CxZ5nhC9cB3DDIcCDQHX5pWxFCm4elUsjXFY9mnbqhqDwSM2AWEffH9i2XuGpkGgMJAqRTGmMAPhAnb1N7Y/o6jQ1O56CwjwoqzlF4PXxlhEbzBgvza2YDAA79VxZW86r40po6gPr40pvAm+KpamBtnoNRUxJry04Bl31phbQI56KunF2HWYP0+UjAvmoxzp4aM3f2xEjQGFh5X185XSWbX0/uK20RgXqFDfV6Bxy3A0/BaD8OBhQudI5L8KFPJpBRI9Dj4eueYdwnJVxEyY5docStnsIkHDwjmM4Yg0gdCzODy84syCk3MRcjHgVl89H7RhyUXh2cgGMoSeL0PK5tAauw6n2vRC6dur3rdhN5fEDOl7UTSBAh1I7i/g9lyOevn4OWyOXSfEtR4eErBh8PCYwrGmwN7YdQbcZuYe45PGJujdueism7vZkCvp0T6HB8awMIzNI2M8Tkd96l32QODI+yJLJlMixdh1+pTj3efBExYVNwud9VNai7jw169l+4/bVtFqvVgpEN6NtZ3samJzInNDjB2F183vsmA/vsGkAWe0zzgzE5A8g6wGzv8UummW9YVdmuke2hveoO+z64khPSN7GHoMZWI+BpMzF7FjN0l79pLv9+coMIBegc1PTOyWmZ26ebaiQG+eIczV4j0wT0O0IB7zhS/s+6sJ09tMwG4i1+MXre/skP9xteftxP9xy6Jbuo6nwGemR3kUUBGH9dlPSzV7Fk3oYv5ubrhLfrY1jecq6WmRosDXFBd/gyiyYktHjweRxTbixVQ/RUsHVIG2Kn6toepP9NnvFVZeg+9P+c2szbiP+dJf5QbbGav7mAEf28NCkjF/RtbxEm6erdYRsGGw0J0Sz/WPOB74tUZj6X0vivuceT3kz3V0QGuNZi+gOrASgL1JmGvrkN/HOqfsIlk3lSzluqCWDPfxvSkXTMvHYS8twtuKybz7XT4GJm9fhSHfy/uKtcY5kXEKAOsJhbRJIfExk0241yfmXKsnLtHZJbVwu7uz6RTZGRynQZuS7GI8metPC/DoMHlpy5r+9CuR9q1jK7CTyfgs3Z6kzJzAmEi3K5UgqcyVDGgjwJS1Ac6pKks1rGSVrv9OSs4//2DDyM9L1R9sDfVnqr0fEiF/Xu9stpZPt+pHn1vbe+vLn886W2vLH9c+NrudZrexu/rlY23rZPXgaH91bXf3tLu+fLbbOm41TopVn2dw9q3L/0kSZUWjVyAR1jCfL9LYnSwh5UWi8+9kYpXnwD1dtnnJ9SvFxW9T7blWCa7VgA1id9lnrDbPlHNelOG7pRdnt1jkeVFms4UXZ7VQ+HlRTtN1n2ACeS3oZdVvl12czbvq0Eu7lQ9PYDM7vLwok7ho5fYSbubxlFZ0nG+ObJPVnufQuSv1OLV6a/l99X2rUasvV5v1Vn32FNRevrcw8hwmJqoiFi1ZhrjsyfC+c1e7Xq226s1Wc35dw6lVa7VSdbm01DquLbeXltuN+pkzXdyYKl80ZqoV1dniRLVYdZiqK6TvqaZLCckrouniQXHw7KXO/jpRETgvZBCdarma/MkvcG3nfa22vNyqVZeb7xrleqvVeFdtzaY+7J1oYv50HmR2xIMaqM7ceRN5H78b2oVScAoJi3mZqGLOyemeHB5Pp3jazvrKfmO7e7z3qflls9usfVnZaTSPjjsru/uHnb3W2YfO6vrR7sbWweaX9fWPRzt7Zysbe3tHtSObdHldyNaqtaXld/XGiyO7u747B9i1tfqX7bXDVqdz+mFtc//4cO9gp9VdrR3sfOgsNz4fnnYPPm0efNk62Ph02vzUbexsnX3eXD99hcC23rVa9XprBtfUFxcENvPcpyC7v7E/B9nVk4PT/eXVvZOzz8v1473dTu3gU+vgoPWx9WnreL356ajbOt3ZXj3e6Wxtb6+ctr58XD9pdvenkH1XLb97X683lt59H+wmBEvzw/hGMk/EnN/m+ZClqpvkV54T/tOl5qRFcNl0+56TbKhOfIIkYE+mAL6drXFyybb3bLg2IHRyJD9PE0rzn4y62f3a7vMXuKOYQOIePbStARE1gdN28gOGVYi6ymCNFV/shOLMe7Z7nIwju2BGUl1aM5lPcRCbWMEiND9kI4nIqF7YM4C0+ZU0AZE+4kXxQelkdrVcLS/ZI0QYUnVzNyp7FIsvxsnG8fE+WdnfxFe7tsUjbRI4SvjKVi2TTewfGIJtrBE+UVCywGk72s6MlPRj764XZIpE8ngds3X5Q2SgmuHDd0k8KXQcQjaVXoGiQyCFZ7dEAbe+kL3ILzxWLknFkpYNy0jew5HcpUisE6YyhtakAnxAzbSVvCBHXzF/CKQPZgTYDBFFibSTM/eVxPybJpxdAhlRzsFol/jg4VmNcgxfBK69AB9la9dSSLpLktBjOcofXhuJrTf2fXbhvuoS+14cVZS1ZKQRx3bjJBZP4ApvYAkfxdm2fyCfWZ6xrH93SzgvKvTiTeaePlwBx0u4nriNpGxXPKmgJKQPb/+trOer+Cqy5bDXoA/4E2jE8opR4p0cbruEkr6SI512i6X9dohKjvVR56N+FGtferpipOS6ov1LjUhLogDNyVLzJCZXr/GVvhyQG+znixJAXTIC2ycRhiB8/MkCRQUuTJjQBqiPk0J6ycSQ+EyBZ6wOPcq5tnJatQ5j5gNJPKYPmgRyZCHxQyaYNqBIZuLWHDNscAnbOvFGwSAxZit/J5f0R7LK5fAOg9FoNCl8PrLU53JYoSUBo5KORQl3oQBK6f7x1nZraIluQr3LoZKxsO0OU96Q2I7yAmbAM7GinLAQfR5s5ibRENMkpL9KRdKtg/TjMHpbJh8ktuIk1RX8TPsyxi4PyyICmK6Xm4b0AfsuXOIF4F0SHF2U3/aOrCO0dwAMmQniPl40KykOlaGs9LnsV0KKSFfQvZgHOts6K1i1UILyxFLWTzY73d6HvcNep/upu7233z08Kof+W6vMVRhIBWgWfRgygV0qP2oykspgbxEzNtkmhkl/Fwi8ugpDwAtk0hpjuUenJbvS/5YwQXzp2Z4Zi2Cb/PTTCIgviZAGm1Wl0kBULAQykcGICk2CFCVoTz7l6EzFGJJb2k8/JeEBbKcY5fzGkrZze1eUM98K2JvZ+QAdQwExI0k0YKucQdcSHiiRhhwfPBlHPMUnxCDNQjxuUWGs+fWlhTE7x97YWQXjK084BvpeSAUdgiYMTW8kXOzRA7/ky5HIjU8OJkWVkWGhDYm4ZjoTQx4GRDkgAsDX5M0IfuScFPwOG5awf/Grs0Yju1kgua9Ojh2aiE0NqVDvDY4SMysc1YqatYNKclBKrTHtDaKeLY6kzV4Z20Vz/4COmSRo3Kmj4OTBD0LK7K/Aufyf4m+2gu+B0FBYayWiXgCkVsb7AvPRdgfM3mmSX0rJL3crpsGG2l+tTClRXdneXOvuHnVxSjkwIbclhUhqE1JRWBJLWYRyTgotzxOHitu7fqmXaMdOLy0Grk0l4pi5GqcC36an/HMnP+VfYI5LG/x2e4tB6kTx8Rg/J115ePb3mS4mfx6Q7l+qO3sujskN6653Pb1UOfZKcz8ur6CX+kGBsgbxSXGeo/c/oc/6IYVk3eGL6eMvaIZ+kP3pxu5vVcNf3jD9gIx5C/g3C/e36Yt+AIWsI/wbQfgX6oF+0B2Sl193IF3gfxRLChTn+JgkAIpI3mW9VjwPouKsmc7kiazXevfYGY//H9OZ3V8=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List all Accounts"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists accounts by one of four filters : signer, asset, liquidity pool  or sponsor.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"sponser","in":"query","required":false,"description":"Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"asset","in":"query","required":false,"description":"An issued asset represented as “Code:IssuerAccountID”. Every account in the response will have a trustline for the given asset."},{"name":"signer","in":"query","required":false,"description":"Account ID of the signer. Every account in the response will have the given account ID as a signer.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"liqudity_pool","in":"query","required":false,"description":"With this parameter, the results will include only accounts which have trustlines to the specified liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns accounts based on provided filter: signer , asset, sponser or liquidity pool","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"payments":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offers":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"trades":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"data":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transactions","operations","payments","effects","offers","trades","data"]},"id":{"type":"string","title":"id"},"account_id":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"sequence":{"type":"string","pattern":"[0-9]+","title":"sequence"},"sequence_ledger":{"type":"integer","format":"uint32","title":"sequence_ledger"},"sequence_time":{"type":"string"},"subentry_count":{"type":"integer","format":"int32","title":"subentry_count"},"inflation_destination":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"home_domain":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"thresholds":{"type":"object","properties":{"low_threshold":{"type":"integer"},"med_threshold":{"type":"integer"},"high_threshold":{"type":"integer"}},"title":"thresholds"},"flags":{"type":"object","properties":{"auth_required":{"type":"boolean"},"auth_revocable":{"type":"boolean"},"auth_immutable":{"type":"boolean"},"auth_clawback_enabled":{"type":"boolean"}},"title":"flags"},"balances":{"type":"array","items":{"anyOf":[{"type":"object","properties":{"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"liquidity_pool_id":{"type":"string"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"buying_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"selling_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"sponser":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"},"asset_type":{"type":"string","enum":["native"]}},"required":["balance","limit","asset_type","buying_liabilites","selling_liabilites","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineNative"},{"type":"object","properties":{"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"buying_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"selling_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["balance","limit","asset_type","asset_code","asset_issuer","buying_liabilites","selling_liabilites","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineAsset"},{"type":"object","properties":{"liquidity_pool_id":{"type":"string"},"asset_type":{"type":"string","enum":["liquidity_pool_shares"]},"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"}},"required":["liquidity_pool_id","balance","limit","asset_type","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineLiquidityPool"}]}},"signers":{"type":"array","items":{"type":"object","properties":{"key":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"weight":{"type":"integer","format":"int32"},"type":{"type":"string","enum":["ed25519_public_key","sha256_hash","preauth_tx"]},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["key","weight","type"],"title":"signers"}},"data":{"type":"object"},"num_sponsoring":{"type":"integer"},"num_sponsered":{"type":"integer"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"paging_token":{"type":"string"}},"required":["id","account_id","sequence","subentry_count","last_modified_ledger","last_modified_time","thresholds","flags","balances","signers","data","num_sponsoring","num_sponsered","paging_token"]}}}}},"title":"Account"}]},"examples":{"ListAllAccounts":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts?cursor=&limit=10&order=asc&signer=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"},"next":{"href":"https://horizon-testnet.stellar.org/accounts?cursor=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U&limit=10&order=asc&signer=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"},"prev":{"href":"https://horizon-testnet.stellar.org/accounts?cursor=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U&limit=10&order=desc&signer=GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"},"transactions":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/operations{?cursor,limit,order}","templated":true},"payments":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/payments{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/effects{?cursor,limit,order}","templated":true},"offers":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/offers{?cursor,limit,order}","templated":true},"trades":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/trades{?cursor,limit,order}","templated":true},"data":{"href":"https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/data/{key}","templated":true}},"id":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U","account_id":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U","sequence":"24739097524306474","subentry_count":3,"inflation_destination":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U","home_domain":"tempo.eu.com","last_modified_ledger":40074676,"last_modified_time":"2022-03-17T23:13:54Z","thresholds":{"low_threshold":5,"med_threshold":0,"high_threshold":0},"flags":{"auth_required":false,"auth_revocable":true,"auth_immutable":false,"auth_clawback_enabled":false},"balances":[{"balance":"0.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":40074670,"is_authorized":true,"is_authorized_to_maintain_liabilities":true,"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"balance":"0.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":20213845,"is_authorized":true,"is_authorized_to_maintain_liabilities":true,"asset_type":"credit_alphanum4","asset_code":"NGN","asset_issuer":"GCC4YLCR7DDWFCIPTROQM7EB2QMFD35XRWEQVIQYJQHVW6VE5MJZXIGW"},{"balance":"0.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":7877447,"is_authorized":false,"is_authorized_to_maintain_liabilities":false,"asset_type":"credit_alphanum4","asset_code":"PHP","asset_issuer":"GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"},{"balance":"80.8944518","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","asset_type":"native"}],"signers":[{"weight":10,"key":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U","type":"ed25519_public_key"}],"data":{},"num_sponsoring":0,"num_sponsored":0,"paging_token":"GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-assets.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-assets.api.mdx
deleted file mode 100644
index 7ff8a8838d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-assets.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-all-assets
-title: "List all Assets"
-description: "This endpoint lists all assets."
-sidebar_label: "List all Assets"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWntzG7kN/yoY/nGXZPTySzl7JtPKbyWu7cRO7hzHo1AkJPHMJfdIrmXXo5l+jX69fpIOuLvSyq84bq7N9fSPx0uQAH4EQBDgNQt86NnaKet4j8GzsxqT6IVTaVDWsDV2PFIe0MjUKhNAKx88cK2BR/oGqzGbouNE3ZVsje0pHzpaF8vVWModTzCgIy7XzPAE2RqLs3vCSmQ1pojPbxm6K1ZjDn/LlEPJ1gZce7wtDgJNAzuAMMJcDLiyGYxtpiVodY4QLAyUDuigf9Vgk9oNtsr7DN0TGB8F1Jo74FI69L6UIV8PBtY9QSSROW+/VpgOmCzpI/HjAeLWeGLBwaco1EAJ0FbETQFlgIOwWqOI/9sBOPSpNR49cCNBeUgzrVHCwNkkqpDyoTLDXrDnaOCC6yzizcGhsE7SpnsxwoSztWsWrlLSQ5mAw4gqXvIk1cjW2u1Wu73wcvnlT6srqwutlUlFbevkV29BByR6NTS81INEjQuRkuOREqNCQg9+FLHnaYrcNeAgruFBGaEzifCZe/EZnnEv0Ehlhs/BOvhM7D7DM/pTfG5Al9goD9wNswRNAOXNv/7xzwAeQw1UAIkDnukc/7jsnfD44JQZEjomS8jfuBcsV5CdVYHRKlHhCbaZ8EuVZElpGHGXcygchswZlA0gurg+CG7AcTPEfM8XSPjFVgvqwA1kaYquIIwGpjyMuJPkd5Kg3rVO/d2aaPEpuoF1CTcCwSH31vgHQCs3EOUt7BZaj7WrhdZkclZjl3Wfpal1wdd9cMgTAngtuAwJsMLCaaXFVov+zGN2lAmBniKUsCagCUTC01Sr3G+av3qiu65IxLU+GMQoVshm+7+ioM1KHQXBoHJ+Pa3Mua/ocA+dRz34MtXI4eAuQ4qoh2gx5pxNaixgkmqCtkLdt1YjN2wyqRrRab7oWY0FFTRW1jB4Gb4zkVKHF9+VSBMiKz/txa0m//2CTWDSRynn2N5DWvhthZA7xykMqIDJI+zqsfYXbKK/M2RrxRGdT7/JdDpcnOB3SJXyENCRg++cduofW/XVs+uVlQmbsSoO72halWPubm5C2MyER2DJszCiqDinfRm7aKXpeC/YXsKVCVyZnla8r7Sa7siteZl5eGWCzGRJT2iuEt7X2OtzTcH4nvUirTXBcREeINHqt0xJFa56qbX6HsI7OH0NOhWYvwac2bR7sCkJCJrbsPR4Qlt654JTYB4iugHNQ6QDHZPrx6DTm3nHbeeplSQXVpAyD9CoJMnCfTTlb+YMMU1nk7PJ9HiNEs0n8WvXLOaA87GlPL3y+MBGIaR+rdkc5blBPaAPBkPD5zlzw7phM78z/GWW/L/a2D/5Ic+AX/0QE45XSz/EjO4V5UeVA+lbcdnYP+ntdNZ31l+f7HU3Fg92Ose7S5sffl5cfL+13m4fb//t542lD2+OO4fb3YPu/oeto3cf97bfdHc7y92ecChV6HGdjrjJkuW7RS4PrG8rcvvDL8dH7eVf3h9svP14tN452d1cXP548vrkcH996c3rxY0Pb45OulvLS4eLm2/fdn95ufz+eLHzJZFj/kkGMXc+TU+g07nDpDgubujlx8p7kflg5ZWP2jTGqHX93NixaZZaxsk34zu7KR2rVW+Ga2xj/4TdjPnsqViwmwGffVNk2f2BuHUr7rbuCbOt+TOnGt8WWo8LlK2bgbH1cBxkrUYr/7G7IuDc8H2xb46oeixU5WA/ra6urrZzugr9Y5SaYzCvXmWoGnJvBNXi3nQzjlY/V0Jn9bPQfNzn4ryHhgbLteKd7YvOUVQM8kAanWNw+fv7R+focLe7t9He3Fg/PFw8XD5ut9/uH51stzfaBzv77c03S+39k+WdlaP1dy87P+++XDl+vfNy/z7/eNpq/3X/WF76o/vHwnfiFPkV+ut8guY8ziUS7qkaWNi9sMnv7w9PO+7v84dvlDz87ufFH90d2iut8vedOMZ/clqczZJvvAxoPNUjY4Z1jlds7e5qVq1MvKN7ndVYgmFkSY0hhvy2O2JrrMgfqXyG7qIstWdOPy79ZHfVE49zOtjHMLbuPJY47l5xkIXM4WPW3C4pwZSrnlGlc2BjvCjuJEV1kZRH5/PZrUarsUD6ZUnC3dWMClJnL5SMpWzYPT4+hM5hl8qJkgdOtcpQqdsXXBvQDaDMEGMvw0hwWI/A+UgdZ6bOykyghP7VXUvkVXUqgUwrpMi9ooq8BWGNzxIsp/ILdHyIUCkugkPNg7qIfYFYcJ9VUevWKTQBZS6Iw9ShRxN4XsHOfC5UKdCGdUiVXeWj5hU9+k7JIUIfwxjREPtc2/mZh87SpdTnbYox1xqDr4FEgeTbmtwG8FKMqFrsa3GFvMORB9go0bQiHCz4rB8Lx44bz2PLwdcgFrJpi4poBYXX16junts74AWaUo7q7NjYmM5s3LKsP7slnFY39OxZ6Z4SL1BTmcHPXTULsZvCOqwbK/H5n8p6PplPpmRHTZA+0hB6wvJCcRDv3+3VgEPf2bFHFzlYM203TrE+2nzjv4i1tMI3Ax19TS/PPSFtwSGZU1xNWKq4XKpwRetf2cyRtRGgNRhjbOAkCRoZm4kEFDfEGJTxAbmkSQk/V2YIUjkUIe6h4Fr7qGfc1mGmJELuMX30MLLjCIlMlFGUiUFp4tEcS2yIRezpPHM4yI056r851fRHWNd2OMNgPB7PKz+lrPe1HTZ53eC47jNTp1NohPXi/Hge20jekptwcT50NjMSrLnpDbntODFSAUXIHNegEvJ5TOLO26LnlPBfrYPi6IB+lqTPG7BtqUeYl6zpM+/bjNpPUUQCsOA3NQ0rsc891kCMUJwDUVf1j02tHYJ2BsBQhVHWjxltgUNzaJt9bftFztsk91ICfXl0NqmY6gzXuaXsvO9ubvW2D971Nrc+bO0dHG69O2ok8nnczHUcWIdkFn0cKkPtsx89jK0L1PRUIfbgzTBKSUFCRRFRjGzes4vSk9PCvpVPCRMgrYjNvIjgGrx4MUaQFowN9D7AOo/gMmNIiBJG2tA8SHEge5JckzNVY8jU0l68yMMDxhY21/oqLh3n9i64VjIq2Lt18iE5hkMIYwse6b1BINcyAp0pQo5EYbNUF/gkFKRVQskWNyGaX99GGMss8irOqhhfY84xyPcSbvgQPSgyvbGpQcodyrq0YzM1PjuYV9WmQSUxJBLPYiaFPAqIdgAGUXp4NsYftYaK31En1QOHT2yDp/GwoOU+sSl2ZCLU4kCX+IPBUW5m1RpdZWcjUd0O6oU1Fmk8F7HOWnShS7Gr5r5Njhk3n7LquVRwPvHDhKs4ilrbv1bHYvlcoPFY4dVJuRghLDYoW1eSbHeg4s0tH6nnIzOORbDhcTTqVCzqm3vdja39oy2a0hiF4gqZWh8Sbiosqb4dX7FMn6nMpRTXs57wI96/FHfTgJehmWquYjE+SntdJOinjE9f14ysD/Tl+priy3unJxP6nHf6KW1/QJKvfvpyj3D5jWPuDU5xz2Axz39QhG/2COYRwk1f6syLp3z1bvXA5v3v38k8oOL05c+TlfvDPId5AIXyIdATQfg/evryAEjlo6AZSGf0j1N5AeKU+ncj5ITkrKLQEQLT6qxbr1vmKgo7W8dsMvk3OBz/5Q==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List all Assets"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/assets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all assets.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"asset_code","in":"query","required":false,"description":"The code of the asset you would like to filter by."},{"name":"asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer for the asset you would like to filter by."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"toml":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"asset_type":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"paging_token":{"type":"string"},"accounts":{"type":"object","properties":{"authorized":{"type":"integer"},"authorized_to_maintain_liabilities":{"type":"integer"},"unauthorized":{"type":"integer"}}},"num_claimable_balances":{"type":"integer"},"num_contracts":{"type":"integer"},"num_liquidity_pools":{"type":"integer"},"balances":{"type":"object","properties":{"authorized":{"type":"string"},"authorized_to_maintain_liabilities":{"type":"string"},"unauthorized":{"type":"string"}}},"claimable_balances_amount":{"type":"string"},"contracts_amount":{"type":"string"},"liquidity_pools_amount":{"type":"string"},"flags":{"type":"object","properties":{"auth_required":{"type":"boolean"},"auth_revocable":{"type":"boolean"},"auth_immutable":{"type":"boolean"}}}}}}}}},"title":"Asset"}]},"examples":{"ListAllAssets":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/assets?asset_code=CNY&cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/assets?asset_code=CNY&cursor=CNY_GABGBJYLIC2OGATH3DVW22UEB66TFMWC3VKTAPFIOINVESRZLFKIHA4I_credit_alphanum4&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/assets?asset_code=CNY&cursor=CNY_GA6VXTS64XUOCQZSBAYHD24ZYJYPNB3KJ2CVKSYIE43P2DQQIX74UT2A_credit_alphanum4&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"toml":{"href":"https://swisscustodys.org/.well-known/stellar.toml"}},"asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GA6VXTS64XUOCQZSBAYHD24ZYJYPNB3KJ2CVKSYIE43P2DQQIX74UT2A","paging_token":"CNY_GA6VXTS64XUOCQZSBAYHD24ZYJYPNB3KJ2CVKSYIE43P2DQQIX74UT2A_credit_alphanum4","num_claimable_balances":0,"num_contracts":0,"num_liquidity_pools":0,"accounts":{"authorized":10,"authorized_to_maintain_liabilities":0,"unauthorized":0},"claimable_balances_amount":"0.0000000","contracts_amount":"0.0000000","liquidity_pools_amount":"0.0000000","balances":{"authorized":"899996000000.0000000","authorized_to_maintain_liabilities":"0.0000000","unauthorized":"0.0000000"},"flags":{"auth_required":false,"auth_revocable":false,"auth_immutable":false,"auth_clawback_enabled":false}},{"_links":{"toml":{"href":"https://StellarAssets.org/fx/.well-known/stellar.toml"}},"asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GAASPHILC6DCBPP2P4T66QNSYF6C6OGN6DK36NY4G5SBR7AWH75TJG7N","paging_token":"CNY_GAASPHILC6DCBPP2P4T66QNSYF6C6OGN6DK36NY4G5SBR7AWH75TJG7N_credit_alphanum4","num_claimable_balances":0,"num_contracts":0,"num_liquidity_pools":0,"accounts":{"authorized":43,"authorized_to_maintain_liabilities":0,"unauthorized":0},"claimable_balances_amount":"0.0000000","contracts_amount":"0.0000000","liquidity_pools_amount":"0.0000000","balances":{"authorized":"1.0000000","authorized_to_maintain_liabilities":"0.0000000","unauthorized":"0.0000000"},"flags":{"auth_required":false,"auth_revocable":true,"auth_immutable":false,"auth_clawback_enabled":true}},{"_links":{"toml":{"href":"https://masterstellar.com/.well-known/stellar.toml"}},"asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GABGBJYLIC2OGATH3DVW22UEB66TFMWC3VKTAPFIOINVESRZLFKIHA4I","paging_token":"CNY_GABGBJYLIC2OGATH3DVW22UEB66TFMWC3VKTAPFIOINVESRZLFKIHA4I_credit_alphanum4","num_claimable_balances":0,"num_contracts":0,"num_liquidity_pools":0,"accounts":{"authorized":1,"authorized_to_maintain_liabilities":0,"unauthorized":0},"claimable_balances_amount":"0.0000000","contracts_amount":"0.0000000","liquidity_pools_amount":"0.0000000","balances":{"authorized":"65000000000.0000000","authorized_to_maintain_liabilities":"0.0000000","unauthorized":"0.0000000"},"flags":{"auth_required":false,"auth_revocable":false,"auth_immutable":false,"auth_clawback_enabled":false}}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-claimable-balances.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-claimable-balances.api.mdx
deleted file mode 100644
index 29391ac766..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-claimable-balances.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-all-claimable-balances
-title: "List All Claimable Balances"
-description: "This endpoint lists all available claimable balances."
-sidebar_label: "List All Claimable Balances"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlXOty4siSfpUK/ZjpngBbKt0QERNnuYMBA+ZqehyeUlUKNC0kjiTs7uNwxLzGRuy+3DzJRpUExjZtu43Z4+nTfzoaZWXl9asstTJvpJjMIin/SSp5xF0Q2wNUJB7xKUTSRUZiENHQXcZu4Et5aTB3IwQ+WwauHyPPjeIIEc9D5Iq4nlhLN1zslMuRlJGCJYSE82gwKS+13CgueN5mw81+GWlJQrKAGEIu0o3kkwVIeSlaBn4EoZSRXC7FP1cQfpUyUgj/XLkhMCnvEC+Ch8IWKA1WfowaZRQ4KJ4DEnyC8AhVriD8ikhK4PriaQjJPuja9TwEbjyHENmbVcCQ/VUQztwr8DerOfsQzckVIIKilQ1+HH5FH+JwFcWe60MGBY4DYYZTMRITJAg+ouu5S+fIjZ7nzy0Y0TksiJS/keKvS2GTOHT9mZSR4AtZLD3+U63c7vVOT9rasGX2GgXD6JpnuDutt3uN0/G02DbNYqXYrreqk7J+UhkW6rUT80w7mUq3t5mNrUkUQfy9lvaRG0UrYEisRiEsQ4jAj8Uv6K8//6cUMMg3OE2YuqVR/uvP/32RJ1LTbgyKnCDcthPf8kjaUiGJQf+7tXgULwyi2PVF4CLCWAhRdIQ6vvcVuT71VmxXuKd+pcTnsSOeP+XZbbFXYRR8d5Ajf7WwgRuExEjkZYTigIfiEqjruBR5AU1UcH1EEA08D6j4d+BsLB0h4jMejMuV5wFDThgshMRLMnP92WUcfAYfXRFvBXwZQSHQIGQ7I9P1Y5iJbN2EpmHIhqGYmpmzdEuR9e2AC0L2/anNXePOUtek3hKMuJKJBxIJIxTNg5XHEFkugYRHqCN4RBsP/k4i+jv6QCIKPnP92Ueep7/z7X5HH/hf6c9HqMG3cSNEwtlqATxaI/+vP/87RhHEGeTGiIFDVl5if8H2mcT1VwsOvCSiUqKgdLFtGM9duN8bw4M5oAX54i5Wi3VgCC8npgghXoU+sCPE6QR/Eagh8WeQ+FzhwmNZRllEfLRaLiFMCUWAuRGak5DRgAHjpq4HofuvwBcpuYTQCcIFzwIUAokCP3rCaGsHAntkO0V+aVwp8u3tBTdKGsWcGssy/+u+XforSiHiJwwN/Bj8mJOQ5dJzk9w4/iPidDdbuxLP6zjiFEr3D+w/gHKHLEN+nsVust+l5/qfoy05v0EXgec8TzUPwdkVLMKysYgK/7N0m5FiWCw9br4tajsIPCA+x/OtQPmUML3ISLEbe7DFw4cv8TsTaRnC1bsS6ZaTrX9qCVfzHH0mJmBhA2P3tv0GaZqbW4QkDAlPdTeGxQvi6m8cf5uy8AXi/78KFofEjwh9f6I9IBI+vWfHB7Jf3GYkl+0Sbs3XZSLtto75x9S3mbQs3PlkwYuZnY/SynbnM49E8eUiYK7jArv0gHFof54wdvnZuINsXfTtkUlb5d4uiy1JHEPIT5Pap0J2Kmetixtdv92yZVojpjjG+NkCz29LfPZ6me9Z9zvXhuAVwQnC3QYldvSSp5VlQOc7SARu+sELzpeVTwOfudzsxNuVGZmDS5r+yUiOJ27Dj2qOh4nnMulB0mQ2N6c0Ib4R4jsD+uL2/jnz+Gp8yzM5rXuEgN+8ROdvJFGn3z8b1uifYJU0j+NllD8+nif1WzaGKPYhPopi8DwSHgXh7Hhzt7lc323+IVT8lafIFfyU3Fd+/UmUh78q8k+iAP+Vl7NbtcXbb6jqlppTZTkrp38U07aIpQPWCTFkLMu2jimVNcfUqWYZjBLTYFSxHKBYoZaGmWOrOqWAVaqCTb6hwboUOYAGqoo1RTY2GhiWYuZMK6faVAWiYNVQZAs7oFkEciq1bVDNnKwBKLolO4Bty1ZBzRmyQ3PYUJyHGojLBA+oe4XIptT49OaRcfxWmuw6fd+HZMfbYt38I3FlRhg+I6wuToK7Ez4OV/CoxnknqtwJ9VJF0jpCejM/b0oKKcmNO+DMS/KRkuwibdUQUq3cmbYn40a/W9TNamMw7DVqg2odN09Px2ZvUK30J1W9PK0U2tOm0atX1Oaoow/OBt9C4vw6DXfXGBKWsZxVcFaVB1jNyzivG1PpXqHx6UHNINVKZXVgDBu91vm0WzsrnY/6FbPV7BX1+vn56WhgVk7PjbNSv3pW7Z2f6SeDYrlUKXVU6UHBIEqCTzf87Lq006PtoTxqKs8dzSUkJ5ykGLKlGpamGsn7peQUfoqZ/iwzXTek29sLcd/enJLUI9c2oZ8vweeRun4r8aiglN4c8YRihwIxlVhEzqkapkTTmWUQm8qKgs2coWkspzLFVHLEVgzQNCxbDlEsHeewZRuGrJgU5w4HYvtK9o5AbG9V9gexvf38FIgpR/IuECvohdJ5v1it64XquD3VB6pWbQ30sToxplp1oHXbp+rpsDxQa/ikdH4yOa+VTVypPgFiuqxbuv5tEFOyspJV8AArHMRk+XkQmxSGrYZ6WqhWhs3GZNgblNX6pFYaDFptozmqNQfD4rRRHw3LXWM8qVTNs/HJyDAfgtiDuj7xwCvRI9Ex+4YJesASSJVVg1GHaGqO2rqi5GQbiGKAauR0GVTDssChlqrppmnLpooxzSk5RTdBY7qmKAcsgfaU7B2hx96qvEEJtK+fny6BZFl5jB7FRqPXxsbJSd80tYFZ6nfVcbE6Gk7qw9JgWhrp026t3WzpZrczble77dZ5p9mZ9r6NHhrWNUNRn0QPNSurA0XOq0Ye555Fj9eLeCj0SHXMvmGCHg49mGwaDmDmqGBQqoNOcQ5M28G6SRUFbCxbzJRVYuQUqudsO2eYtpmzDROrOjUs7XDosa9k7wg99lZlf/TY28+vQI/C6WgyxeUerlZbo1KxP2oXi6ejcX/SN85HlXIXa2blVCuppbbaUPHkTBuqnSFuPIkeOtatF6CHklf1vKo8ix6vF/GA6MF1zL5hgh4QPUgOWI7JjFIiXnCZVFctHWzZtO2cpjNs25ahYZ0pOaYYOaarumyoqmIwywLzgK9f9pXsPaHHvqq8AXrs6+dX3FyKZue8V+01zFrdwLjULFXH3bo27k+Htc5kcnqOJ+OR3sRmX+2P8Um9My6VxpUT7dvooctYNY0nXr8oWVnLYnmgWHlZzsva8+gxwsN+Wau0aq2zcXFgmCPzVDV7hZNmp9uqD09aamFUHeun9XG5Ppq0tEqv2x9P9QOiR6pj9g0T9HDoQXVdIZZmMdmxdcWybFmndg5j2dZsYjLCNMpMy8jRnGYRWxA5pqYxQuycoTlwOPTYV7J3hB57q7I/euzt56drDyxbio6th+89xuPW8Lx0pk1Omn1tet4cFwbNkllRC6O2Wp22xpNxv9kpTseFWvmsU9Xbw96k8MTLW11XZVWVn0QPPYvxQDHzsvaS2qPUn5YLw2Zlojamk8mwUmlXzhrng1GzXh6MBuOm2apP6pXWtKIXNRP32rXapNeql1+EHpnHWPVqgxwMqxKLZt8QDg5Y6SgOJsyiiuNYCtYYGNixTKwA03OK4iiOzExT1g1DpjoXlhDF1AjTFVmmhq2xA1Y6e0r2jrBqb1XeoNLZ188/JlYVO1q1ZWqd6aBTGhSK42ofd+taq9bApXq1UCxPcavYPasbw0ppUiw0hnpr2OhU8Q+LVW8AB4fDKsXWVUM1CLYowTrDOaZQ3bYVQ3d0HedkxTCZrlIHHFumgC2TWTlZxbaKHdPETD4cVu0r2TvCqr1V2R+r9vbzU1ilHWHDMmRDOTRWGTlDx7knscrIyspAUfPYyuvWs1hV1rXKtNvslYrTZrdhVLVm8/y8VWuVx8XOqNmdFFtqsVWtnZ+WWoNitVadTmuj9tnL0ONvgVWJRbNvCAeHwyrHUWxbI7JiK0wDA9sEqzZ1mAaYYpyzqKE6oBOQVSPn5HTbtJipEYyx5uSIbdDDYdW+kr0jrNpblf2xam8/P4VV2DrK5UysYf1vB1ZF3OuNOwUV184arUJnqpt1faq3Ozpung476rh+Mh5Np/Vx/9QwWq1yd9Jr9xutH+gS+ACs3gAPDlhY7fnl5wELqz0le0dgtbcqb1BY7evn5/6zTJa1R6+7jfJpZTzu97u9wsTsn+nt0ng4OBv1uifFQuXsZDDsFaad0WRyUh7iitFttJu1dgc/gVXJZ8vPYJViiv9qN/Oy+vwLK1xqtzs9XBxWG6ra7XZapyfNdu/8pFaYDLu42Z5OKpOKMahVVPOkP+l16w1tWKi89GtDJSubWcUQHw7J6YdDOz8QxIZmWLzvjuf6Di65l3GxFM00OJdXf2X41l+GC1HWvQELiOcBj8qZ+Mx/SWIu947M4XEE4dW6iX0Vei9LQmlXN+cgoUOnEF8H4Wdh4t0cnVW8CuElPKtrSuSvuV7wPlMnEK0PaRNC2tspZSSuSrJaPpKPxAVktViQ8OsdFVqGwZXLRCMxqg8GXVToNngzp2h5T/u6+4lc612PUIO3fM9AjBHwGQohKwwXJd3XfOUyDNiK3nVQP2CR9DTzRqtNfyqQyOX90AGigR+tFrBeSq4gJDNAW22fKARP4AEnF+3Odz2s2SB0kxZ2Icimpz1BMrSKEqHWApWCEHhfrRsJzbf0sEOXzQDZEF8D7/5eLhNt76/shgHvjomQ534GdE08D+IogxhQPi+AeO6/gCH4Que8VzfKCA5Jt71ovQ+FRJt+3DjgowhE2+7WOZJBoo2Yu2jdg57GrJhOEMUhkAWCK/DXcmyvFm3lm5VHjyLrPz0SPm079OLDOj0ZXIHHj8Do3oGbin1MgxCyfsDg439U9Pzm/+avt0tnJRDRog0MXbkE0eFZK4MIssPgOkqnZwQ+rHv9N7bul5vRs7ZmAY2O4yDwouOIfY64pQMUAg8nwY0GvK3qixt/5fy/BquQRxs3aAZdg2ifXyzAZ/yRMBTx+cbI9aMYCOOLFuSz688Qc0OgsfAhJZ4XCT2FW2crl4mJEjR0bYjQPLgWJmEL13ejGEK0DnERjmvb8C1ER/2HEJwkmIX+5Y2mP6OiF8zubHB9fX1f+Q1l1vaC2THJ+nCdjVZ+lp9Cc8im58dH0cQfBTxNCP08C4OVz1DgP8yGJHZCOndjoPEqJB5yFzznYSE8H6Qd/wvyRxCi9OhA9mqx/HiEqgGf0JA0xoqpGnaw4s3/QkRuwHS/TWgEDGwSQQbROdDPiFNv6y9GCtS4ae8MMHPj+co+osHiOLXD8Sw4tr3APl4Qbuljnl4uL3FT1Y95m1/oEy+JlNqwUa5cVjtnl+XKqNLqdCtn/aMF+yicmfQS8rCwYeb6fHjBzxG6DsKYj5xwY1Hq+rNk3gz4vLrzYwR0HiQTE4T0PGnRacBeAxOIBVSMUhAWzKNffrkGxALkBzEfzROEEaBw5ftciLUZuUMTkCKIxxMjHk+mbQzZRNovvyTwAGKACPG8r4K1WHt5RTyXCQUvH518wBMjBBRfBygCPskn5qnlUwj9FHIY0GC19FL7LDhIu4tlEMbEj0X42YEwo+cS2/V4PvJVW8F3dC8xeO4tiE9mECGXh961n0FLEgLLsuDa3wRf4NxXNVjG7kJAIt8zXckhjwNi4CAfgEXowzX87HloK+/4HIsIEfSbVCJLcVhwdr9JG9vxEBHXmXARdZx+EmZbpdq2ZwVRNnCyaTSmsykIFc066QyQtdjb4V7liZncATIPSsH7hR8siCuegucF/7X9jLdVuxT8CLb2KiwJnQPCR/wi5DIeu47Lby7pk2zy5G7HFGyIeCp0SplGx61GqXLar/AlR/N44YlmxGUQxQvib23Jm1hRwfPQjuFTD8qLm7vJHa8eQ5U29cbwJT5eesQVvcVCn5u0nP8k7SjnLzLSPIhi/vTmhqPRMPRub/nPyVQWcTNzo+27yRPC/1BjqXZa9DN8vTe0K21HlqT0Bdg37PIOhkg9qdC6v/uF6vw7pkk9Kf/WWKz7Krw8dP/tw6aeUm89PuvVyv1tZko9YYX1NK1XGuEHmh/1hJHWk7XujHTB/xG63EpS/hOftTAHwi3JsT1ZVKAUlturHo2P4lw2L4lqlYF0e/t/zFPskg==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Claimable Balances"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/claimable_balances"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all available claimable balances.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"sponser","in":"query","required":false,"description":"Account ID of the sponsor. Every account in the response will either be sponsored by the given account ID or have a subentry (trustline, offer, or data entry) which is sponsored by the given account ID.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"asset","in":"query","required":false,"description":"An issued asset represented as “Code:IssuerAccountID”. Every account in the response will have a trustline for the given asset."},{"name":"claimant","in":"query","required":false,"description":"Account ID of the destination address. Only include claimable balances which can be claimed by the given account ID."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","operations","transactions"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"asset":{"type":"string"},"amount":{"type":"string"},"sponsor":{"type":"string"},"last_modified_ledger":{"type":"string"},"last_modified_time":{"type":"string"},"claimants":{"type":"array","items":{"type":"object","properties":{"destination":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"predicate":{"type":"object","properties":{"and":{"type":"array","items":{"type":"object","properties":{"or":{"type":"array","items":{"type":"object","properties":{"relBefore":{"type":"string"},"absBefore":{"type":"string"},"absBeforeEpoch":{"type":"string"}}}},"not":{"type":"object","properties":{"unconditional":{"type":"boolean"},"relBefore":{"type":"string"},"absBefore":{"type":"string"},"absBeforeEpoch":{"type":"string"}}}}}}}}}}},"flags":{"type":"integer"}},"required":["id","paging_token","asset","amount","last_modified_ledger","last_modified_time"]}}}}},"title":"ClaimableBalances"}]},"examples":{"ListAllClaimableBalances":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances?asset=native&cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/claimable_balances?asset=native&cursor=35938300-0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/claimable_balances?asset=native&cursor=33324106-00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f/operations{?cursor,limit,order}","templated":true}},"id":"00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f","asset":"native","amount":"0.1000000","sponsor":"GDOZMXWISPB57FITUQIGTFH2KNNW7QTFESXF5DZEAMZK6QHE3KVO5TRT","last_modified_ledger":33324106,"last_modified_time":"2020-12-30T23:02:56Z","claimants":[{"destination":"GCD3T6UIQLYZPGRCYVSE7LKQB5HYYNVT7ENY6RCSFRFQYR5JTBDCECO3","predicate":{"and":[{"abs_before":"2020-12-30T23:03:56Z","abs_before_epoch":"1609369436"},{"not":{"abs_before":"2020-12-30T23:05:56Z","abs_before_epoch":"1609369556"}}]}}],"flags":{"clawback_enabled":false},"paging_token":"33324106-00000000691787983bc3ea12361092fe49ae83cbbe37804ee1590fe2b9b3e3860fc8261f"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28/operations{?cursor,limit,order}","templated":true}},"id":"000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28","asset":"native","amount":"1.0000000","sponsor":"GA5ACYSBFH5AFWMZ5T34FLT5W3X6Z4FT4PMN3NUDT3G2JCYJXYGD72EF","last_modified_ledger":33505955,"last_modified_time":"2021-01-12T21:02:00Z","claimants":[{"destination":"GCXAULI3NAFEUKIXUQTD3HXGCTTLM6KVGKTUBZIHVUDP6WXEF7RWJV67","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"33505955-000000003a9a08342ca45d96abc011278644d83d1718ab16e44209fa1952829b66017c28"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411/operations{?cursor,limit,order}","templated":true}},"id":"0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411","asset":"native","amount":"0.0010000","sponsor":"GBIIQM26JJS774T7CSP3WBFVUXHUCTZCV5ZPGMKL57POWMFPMLYOKOZQ","last_modified_ledger":34254613,"last_modified_time":"2021-03-03T10:36:28Z","claimants":[{"destination":"GBIIQM26JJS774T7CSP3WBFVUXHUCTZCV5ZPGMKL57POWMFPMLYOKOZQ","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"34254613-0000000063036dcfa438cb51180bea16e36850e3699efc934577b07322c818157e4d5411"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694/operations{?cursor,limit,order}","templated":true}},"id":"00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694","asset":"native","amount":"0.0010000","sponsor":"GANVXZ2DQ2FFLVCBSVMBBNVWSXS6YVEDP247EN4C3CM3I32XR4U3OU2I","last_modified_ledger":34255259,"last_modified_time":"2021-03-03T11:35:31Z","claimants":[{"destination":"GANVXZ2DQ2FFLVCBSVMBBNVWSXS6YVEDP247EN4C3CM3I32XR4U3OU2I","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"34255259-00000000d076fe2df3e6cc5e5c28e7bf257c11eb209d703a681c58bb867b78b67235c694"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f/operations{?cursor,limit,order}","templated":true}},"id":"00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f","asset":"native","amount":"1.0000000","sponsor":"GB7OYQFQI7GH622CKCFWPH4WSZUGOXXNY2XWV5K27S3SW2JHOWCCWEJ4","last_modified_ledger":35023766,"last_modified_time":"2021-04-20T19:00:04Z","claimants":[{"destination":"GAV2USD4ELGLRWBT67V7N37QAJKOPLHUJL3AVFW5NHWDHVXL4EQPSWZ5","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35023766-00000000da8ed8d0dccacce237c5395eb07bb845d2bb96425d18d168d535063316d99e7f"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe/operations{?cursor,limit,order}","templated":true}},"id":"00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe","asset":"native","amount":"0.2091529","sponsor":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","last_modified_ledger":35530330,"last_modified_time":"2021-05-22T17:04:31Z","claimants":[{"destination":"GCSZDAUKEX3IZXXUEEMERIYTVKHDTVTWK7LHXHELZE5B472QMGGXQLHD","predicate":{"unconditional":true}},{"destination":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35530330-00000000c551a949d0fb5199b05cb8220b4ba7dad4cd7968c849ab0fb51f744daab864fe"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d/operations{?cursor,limit,order}","templated":true}},"id":"00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d","asset":"native","amount":"0.2091529","sponsor":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","last_modified_ledger":35530330,"last_modified_time":"2021-05-22T17:04:31Z","claimants":[{"destination":"GBO4FL74OZTOCTABWFS2PH4LGI2CHFABDZ2LBPRH6UECXBAIU5LUIOF2","predicate":{"unconditional":true}},{"destination":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35530330-00000000d1f2ad9c1ff9124de62f9721ed5811f1f0d7705660c5a7daaa174ad5100c6b4d"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0/operations{?cursor,limit,order}","templated":true}},"id":"000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0","asset":"native","amount":"4.2696061","sponsor":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","last_modified_ledger":35686528,"last_modified_time":"2021-06-01T13:29:59Z","claimants":[{"destination":"GD54EZPKQCBZKPI6F4KKYYLGLDWBOVKPXBL3BLFGYNCLTBFGFZZGVMRT","predicate":{"unconditional":true}},{"destination":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35686528-000000001b53636a29ca25d28d1c5bb165f55280167d53cfefb0ce297d98032b32f772d0"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c/operations{?cursor,limit,order}","templated":true}},"id":"00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c","asset":"native","amount":"29.8872425","sponsor":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","last_modified_ledger":35686528,"last_modified_time":"2021-06-01T13:29:59Z","claimants":[{"destination":"GB2QQWOA32GRILAOZ57H5Z5MO52KNUO3WHJWVZZHWSN66LLDPXQMSILD","predicate":{"unconditional":true}},{"destination":"GA5WWLUYCR4XJKS4ZYKWATKC7E3AVM3FZLWXWSKOBZWAGDROF5MUQXAT","predicate":{"unconditional":true}}],"flags":{"clawback_enabled":false},"paging_token":"35686528-00000000ff1bb4a01b1d4e62ba23bcfd4e2c2289c63fe5ae0368f85b79d74a2224f8ab6c"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba"},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba/operations{?cursor,limit,order}","templated":true}},"id":"0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba","asset":"native","amount":"0.0000400","sponsor":"GB6DNEWWSSPQAX7SR5MCWUTRVQPJBAERJTUQAZOVXXJDU2E6PIMKGMO2","last_modified_ledger":35938300,"last_modified_time":"2021-06-17T10:37:03Z","claimants":[{"destination":"GC2CMMOQ2BUFI33PPOLNJKMQYJGAXUP2KMZXEXE6TGE37JSXQPHI4UAE","predicate":{"and":[{"abs_before":"2021-07-16T21:00:00Z","abs_before_epoch":"1626469200"},{"abs_before":"2021-08-16T21:00:00Z","abs_before_epoch":"1629147600"}]}}],"flags":{"clawback_enabled":false},"paging_token":"35938300-0000000017b9a95e25aa60200b52cc04f75c496dca76dc19fec21c942dfb35cce23c3eba"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-effects.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-effects.api.mdx
deleted file mode 100644
index 9e5fa422c3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-effects.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-all-effects
-title: "List All Effects"
-description: "This endpoint lists all effects and can be used in streaming mode. Streaming mode allows you to listen for new effects as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time."
-sidebar_label: "List All Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+tSGzkWfhVV/5hJpnwFYwdXTe2CIcGGAMEmDCQUkVvHbgW11COpcVjKVfsa+3r7JFtH3W23LyEOM85kZpY/lLulc9N3zpG6v37wLB0ar/nO2x8MwLfGuy54DIyveWS5kl7T6wXcEJAsUlxaIrixhlAhCCQTCJWM+FSSPpDYACNcEmM10JDLIQkVgxLpzvzG2WpkyL2KiVVOIkgyUJpIGE3FGmIDuCdUA6GMAcOxNgDStSAE1UQAG4IukfaA+FSIZZoL5EBp/i8lyYgLQYyl2hJqnRigWnAwltxKNZKpWhJLAcYQSvxYG6UJN8SALaDoUcD9gPjUAOE2L3CgVUhsQG06qUR273GWRTNQVSrrjooY0AupRgXnPYYtsXjitq+BWmDEcOkDDtJEw68xGmp5CCWv4KkINMXFaTOv6R1xY3eEyJav4EVU0xAsaFzWB0/SELyml9jgFTyOa/prDPreK3gommtgXnNAhYH5pd8hMg77oBPvHAAMOkCJicDnA+4ToXxnC0aIEl8JAb77rQZEg4mUNJBghBsSxW6d0oABieiQy+GNVbcg0/CoAaFEg680Q1+NH0BIveaDZ+8j9INLC0NAR+ATDSMBXrNer9Tr1Uat8WJ7a7ta2RqPCxO3lWbw9V4zMHwoaeYHmuoETWGQWGiICVQsGKFRBFSXyImTYQiXvogZkA/U+B/IM2p8kIzL4XOiNPmA6j6QZ/gvvexQbDHRqB7GIUhLuJH//fd/bAo/SxgMaCyS+DuxS8NjrOZyiNGRcYhpTY3vJQ561/nACB5y+5WB6QVAQvqJh3GYAcOtchIKDTbWEliJ4Dgn3wFcUzmEZM2raPxGpUKKhEoSRxHodKADGDckoJr5iiXJnCUvloYI9EDpkGJWaKBGSfNI0LIFBLYQu2plVVxVK+PxdcH7VDRxFCltTXFSXbym1TFgwFKEo6SNSgX/zcasG/s+GMxLX0kL0uIQGkWCJ3lT/mhw3EPOIirEycDlbmqb6n8EHxcr0pj7lif6bgSXtybnw2fGGRCDL48KNAyWAclF3TrEyFtvXPAshJHA0OZG95USQKU3HudB9C4Rel3wLLcCcjIkfLLfmUmRhrvvyqQxDssuHbmlxvz9AiYg7AN2yy+7kuZtbiDVmmIZ4BbCFXC1Kv4m/eq7Cm/BM5iawFbw4FsD0QcG35dZOIqzZcqycZw543Md/bHRM+PGBY/6voqlXTYlotaCxlr66t1O8apS3L5+2Noa54RRxjTWWPTUTf58O9xJ9JBWss3yCpMrZxCqu5krLQ2Mzw7ag/7clV6gwQRKMEPOIzYn80CFQPZUSLlccveloMNls9pyIJK9xx4Yy9N9yHRclw8l6JwL6YWpB+mF6ZSejo0VXEJu1vTadOL02rK5O7ENsCXPXd4Dmr9xMhjMWJf8nupIfuflUwZewdujluamuZ/TWe7ndFJLUB7SvgCyS4XbFExnLrnnrsws+2cGzSxEF3u70ibg0RLA5O8uLmL+7rL4Lpe9/P6ytVguf4JTjNbj5i8MWfRhYchU0WL4lmt7fNxj6/m4gynCv7BCi4OWLNTioKm6I/5rzBm39+RUKZFTMXfjszPO4E7dLruxB5EyfKmwC24Dpulo8U6WKl08EWKQduMwAuZdp5XvhudqX7JDn9nQjgteer68oUtq7TjZc+S7AWfeXFGf1uq02k5Uzwi/zu9eksOpN0Y7U2tcA5s7uzYfPHcInN1cZNvXpNt5gbWRaZbLQXI4KFowVoItmeSxQEnpYTk9TP8jOfT+/IM7Y/xcrfzgTnE/45kotwl9uuDNzXqj/mLzxVZjo7JZK1Y/oyjbWj5dUXXjxYvadmVr+8XWohZ3uMNwz2z+Jtu7d/lgzuzFvsKeyTxTztkyv4t6goNTF35Y5uv8hujJGuhnFaQ7G6+S/uVvVyYX59Og6c2KyW1hvFc7R6et1tVx7fKXnc3L152Dw6N66217v3V4etTptHpvX3ePLy92e4edi9rh1sGbo8ujvddXvd0so5qZrBt/UnCy9K7MprC3UaluFSvbxc1Kr9poVreaW7UrPN/ikym0tp+UUzeylDrjzhF/WkxsrBsTGytiYuNxTGzMYWLnql3rtc42e5dbJ52DVq/T2tipvele1ludi87BVnun03t12D7e2D9rHO0evz08abUujhuLmGCTPWiGic3VMEGNAXuTdQdq+R0WbxqmFv5V8LG5bnxsroiPzcfxsfk71wzjNjJLSkZ1xZoxAj4MrNesFrwo7gvu39zC/W8zLRGwTjzV14yn+rp7UP3xHlRfsQfV19mD2FzB2fhdCs529re1XcJ/jfVWnvUjZc2dqf54Z6qv2Jnqf7rO9I2B0lgzUBrrLimNx0tKY8WS0lgoKb8VKGmL0pPT8qRFVb+uRVUWWtSTTVtXi5o5G26uBVKzKtaDqkUdM8Cau/0YsBYkzWLrdOPw4OL89cnBZaN9stk471w2uvu77Xav09676m7tnbXbb85O9897tbfnhwdXb161zy66tScfmaqVYqXaq9QQW5XqH3Bk+vb4WEt7WtSxEj6WdKgFSevZzqzYpBbx8Qcen749VtZyiFrUsRJWlpyjFiT9vrXkK49Si1j5/FHqyaZ9kz5VWz+2at+gT9Ue71O11ftUbb5Pta56u5cH9Xq727s6PD9927novT642D2odWuddqdxcXz0pvNLq/emc3hxufmy3dus7V5ctTrfrk9dj9M/fNRuQRpcZfcUOEHQUjpLIXvwjrQWJL2EYAOF0RuCTd7BBl7Ty8KPVoC+yyhmsRarLZ+3jFHUS8aRY7AjpW8dwpdLHMQ21rCKzJfZSCIzqdfIdRoo99YjfS2R8ovQe9AmmV0pVUq45CYOQ6rvp6NIpNUdZ47MRg56vVOyc9pGQhHDt2RcznATU60l0raEyyGYlCepoegC57iNycxIKxb7wEj/fpmIhFeHb/QnHCmghiMnTxFfSROHkE2ld6DpEEiOXkQ0CNeqMvZkjkdVVJqDRLKhM0RDpMGAtElhSMic/fuJQS2lAbld3DjPc370NWdDIH2wIwCJ6hNvZ2eeavXRURwFvwUyQsqmNQXCwAdpNRX4+pjAJz9AvpgpOAmu5xJuTAzaWTThhFlFTNx31DFNpaGOdGgKxFHZcInSPCNplhSQeZdxLe9AZnbkZztq42RmaQFZf3ckvMsv6PWzLD0Z3IHAjmJmSnVqdtlXGopSMXj+t0LPe/leZupSejR1VEBg5I5T4p+fHRUIJX2tRga006AkZHzTSay7e4fmi7Fmyjdlq5QwZcNuDUZaEQ0Ip4SBrPCd6yd8kawGCas4SgJaICNwFM4wBMkcKxkDRSUqJlwaC5ThpJDeIp+ZcY08aVxDZF0b56db1mHMGZAkY/pgSKBGLiQs5BIp3ppkEHdwzGKDKtwL/2caBgmYnf97E09/JLtCDacxGI1Gs85PRhb7Qg3LtChhVDSxLGIXCqCY9o/njkhqkJPTp/7tUKtYMqLkfDYk2NF+wC34NtZUEB5izkPoVl6lrNOQfkRWd9I6SD8Oo+cl8hJJ4zJhYOFl2lcxElCdiRjAVN8EGopBnxooED8A/5bg6Lz/jtb6CkM7DcCQ2yDul3wVltM4lIeq3BeqXw4pRrqM6cV9MFnrLCO9VUsqEqS8Om/v7d+8PDm72dt/u390crp/1i2F7LlbzF0YKA0Iiz4MuUQC7Y+GjJS2SHvm1u0cU2Y7FgnuTAQ/UAlr11mPSUuOFXtKmSBM+Y7O6yLYJD/9NALCkDZv8TsEpQ0QHUuJRmRhxAVNihRFVr5kVGAy5WvIBGk//ZSUB3AkdirEvRPt5t7cUcGZc/BmofMBJoYGYkeKGECevcXUkj5omZYcBr6KI5HGJ8QizUPcbSH7COHXVy6MgtM+F5iPOCsHvtJMYmDuhVTSIRjCEXojWSAR1cCKDL9ayMCnBrOuqsjy0JVE1JnOxJKHBVENiMT9PXk2gh+FILm84+67C0reey0auWaB4t57k9ghRHDLCjo0J4NuArPcVi2/sm5QUQ2KKRpTDjT1Hesi5aFnZufh/hITMznWFOa2grMbPwgpd3dBCPXP/L1xwRPcB2kgp2snon4AZKNUQZIrQ+wOOOjJnWJyZ6oxLTbU3XU+pUJN+ajd2j/u7uOUUmBD4c4bkTI2pDKnEhkuZEcIMv0+Y2ZP8TClhf//Q5vv7UOb9MRm4ZMtR4Jyx1R16HhIT0TvvOxEdF3wAmUsXnp4wIJ+rsV4jJeTjyvwnMS4QYrbZz6vyEPhj//wZqnvyQly8ilRemZMHkp8jXN/mu9rHolC9mXRE4PwF/qW5pEgZV8ZTYN0jT80xyh5zXdICAyAYiSnTyh2fB+i/KyFz2VmnlC82u954/H/AASfK+E=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all effects and can be used in streaming mode. Streaming mode allows you to listen for new effects as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"ListAllEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/effects?cursor=33676838572034-1&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/effects?cursor=12884905985-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-1"}},"id":"0000000012884905985-0000000001","paging_token":"12884905985-1","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"account_created","type_i":0,"created_at":"2015-09-30T17:15:54Z","starting_balance":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-2"}},"id":"0000000012884905985-0000000002","paging_token":"12884905985-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"account_debited","type_i":3,"created_at":"2015-09-30T17:15:54Z","asset_type":"native","amount":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-3"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-3"}},"id":"0000000012884905985-0000000003","paging_token":"12884905985-3","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"signer_created","type_i":10,"created_at":"2015-09-30T17:15:54Z","weight":1,"public_key":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","key":""},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905986"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905986-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905986-1"}},"id":"0000000012884905986-0000000001","paging_token":"12884905986-1","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"account_credited","type_i":2,"created_at":"2015-09-30T17:15:54Z","asset_type":"native","amount":"99999999959.9999700"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905986"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905986-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905986-2"}},"id":"0000000012884905986-0000000002","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"account_debited","type_i":3,"created_at":"2015-09-30T17:15:54Z","asset_type":"native","amount":"99999999959.9999700"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905987"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905987-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905987-1"}},"id":"0000000012884905987-0000000001","paging_token":"12884905987-1","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"signer_removed","type_i":11,"created_at":"2015-09-30T17:15:54Z","weight":0,"public_key":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","key":""},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572033-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572033-1"}},"id":"0000033676838572033-0000000001","paging_token":"33676838572033-1","account":"GAP2KHWUMOHY7IO37UJY7SEBIITJIDZS5DRIIQRPEUT4VUKHZQGIRWS4","type":"account_created","type_i":0,"created_at":"2015-10-01T04:15:01Z","starting_balance":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572033-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572033-2"}},"id":"0000033676838572033-0000000002","paging_token":"33676838572033-2","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"account_debited","type_i":3,"created_at":"2015-10-01T04:15:01Z","asset_type":"native","amount":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572033-3"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572033-3"}},"id":"0000033676838572033-0000000003","paging_token":"33676838572033-3","account":"GAP2KHWUMOHY7IO37UJY7SEBIITJIDZS5DRIIQRPEUT4VUKHZQGIRWS4","type":"signer_created","type_i":10,"created_at":"2015-10-01T04:15:01Z","weight":1,"public_key":"GAP2KHWUMOHY7IO37UJY7SEBIITJIDZS5DRIIQRPEUT4VUKHZQGIRWS4","key":""},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/33676838572034"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572034-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572034-1"}},"id":"0000033676838572034-0000000001","paging_token":"33676838572034-1","account":"GCZTBYH66ISTZKUPVJWTMHWBH4S4JIJ7WNLQJXCTQJKWY3FIT34BWZCJ","type":"account_created","type_i":0,"created_at":"2015-10-01T04:15:01Z","starting_balance":"20.0000000"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-ledgers.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-ledgers.api.mdx
deleted file mode 100644
index 83d4a4259c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-ledgers.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-all-ledgers
-title: "List All Ledgers"
-description: "This endpoint lists all ledgers and can be used in streaming mode. Streaming mode allows you to listen for new ledgers as they close. If called in streaming mode, Horizon will start at the earliest known ledger unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream ledgers since your request time."
-sidebar_label: "List All Ledgers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWu9uGzcSf5XBfmiTYCWtFEu2BBS9tHHS4IImqN37cI6hcMlZLWsuuSW5kl1DwL3Gvd49yWG4u9LKlh0nl+vlrmcYEKTlDOffbzic2evIs4WLZmfRaxQLtC46jyOBjltZeml0NItOc+kAtSiN1B6UdN4BUwpUTQBMC+BMQ4pQORQgNThvkRVSL6AwAvtwsvOdqM3KwZWpwJvAETVkxoLG1ZatA5/jFXBlHPbhVQacKbWPfww/GCt/MxpWUilwnlkPzBM5ILNKovNwoc1KN8yh0gqdAwa8ss5YkA4c+phYr3LJc+DMIUjfZZhZU4DPmW+I+vDdFVF5EoO2angtmaqQ9NJmFQcdyTi1xBvlnNQc6aEFi79WJKCXBfajODIlWkamfyWiWfRaOv9MqdY5cVQyywr09GV2dh1pVmA0i+q9oziS5LFfK7RXURwRa2lRRLOMKYc3HfsMdFWkaGutgnsdCc7AlchlJjkow4MsZBkG3CiFPHw3GVh0pdEO6wiQDsoq+KcxFELJFlIv5t5coG7MYjJgYJEbK0hXx3MsWDS7jvxVSXpI7XGBpAhesqJUGM0mk2QyGR4eHB5Nx9NhMl6v443axgr8eK0FOrnQrNWDRA2Mtu6vJXTgclMpAawskdk+vAk8HEjNVSUQ3jPH38Mj5jhqIfXiMRgL72m79/CIPpqfQ/R6ghGzi6pA7UE6/Y+//d03YedBYMYqVds/sN1rHuet1Auyjq4KAi1zPKoVjM67hlGykP4jDXOaIxTsUhZV0QZG8HJtCou+shpFH2hd4B8C2zK9wNrnQxJ+lCTQA6ahKku0zcIQYNJBzqzgRtQgbkFLwC/RZsYWjFBhkTmj3T1Gax2I4pbthslD42qYrNfncXTZc1VZGutdb5NVopm3FZLBmggnTqMkoY9dm51UnKMjXHKjPWpPS1hZKlnjZvCLo3XXtyUy6S/IyUWlJcR7We8yxyJFIchJH1raeKazkFnLyNHSY+EesJeS+uIB6xyq7MOrcovZvlANfvUhJvVFtI4jj0WpyHmd1akxCpmO1utumJ7VTM/jyEuvsMvDMu1YSEUPUOB3FW2Tv780wUp2RSj60sTCLEP+hUl1Y1EAwI2g23H0VovzdRxJsU/Mdgcpamdsz8b7Vu+sW8dRzlx+3/rwnPhbnD90raMKRHPcmy831pXaPx2F5XXOyyo171hkzk1Vp78HsMiYVCg+mXxj+Y+i8pdzh37+acShChVz5m8blFgbz9ScG7kD+u3zDHFeGqP2PkyZwzmtkHruvDWmdA8UKlBadGiXn0BdsMt5YxMnf3uo90trvOFGzZdonTT6gWQ5MoF2finsHhvQ3y7ipIhuYKQJ/U60fiAS74my2xF0Z3R0Pb/r545X9/vwbv/ctv0eu+7YjIq7DW7ry0DInXUxEzx+46Ywu45CyX2rqNiUDWfdCqCThes8Gw2au8pgOGgeDq6/re8Zcajq4lA0r6OdhEuF061D8DbH7fOPYNrWIbfY7asIbu/ZXfHgXZt0HuERDpPp8Cib8iRJ+OHT4XDKUhwf8Cw5mmbjaTZNhmPOp0/5wZTzLEnSMR6lU5alE5ykw5vhPIsORtOD6eRwNJ20sf1Zdtkm8+GOUdpsl3wogSf3pedkT/JN7k6tyU7ijIbTw6SXDHvJ8DRJZuH/rzdQNYuGyfav33x2wTaLuj/vTZ7DJLknOW422JMCxwldoh4Ei9Fnh8Xo88Ji9BBYjP5FWAxHOD5Kpiw94uOpOBqNJziZDnl6cMSS0YEQB0+nkyTlw/E0GYnpZDLkYjI6nE5G6Sjlh3tgcTQ+mk6fHoynow4sPsMuFpfzfwfKRr8fyrpQGiXDcS857A0np6Ons4PplwelYZKsqRregknjpd8Tg9+GKPuGOf5ViLpvRl/VQfhNJxbqknZ5Nzndy2/Sd1Ls3Ti5e/u6MKmLE7z0qF2NorPr6AKvotn+3kHcnrsBKOdxVKDPDYFlgeFSw3ze2T4Ek122/bzKklty70s3GwzyukXS8+i8Rt93HpVitm/sItrXvjmt18GP6FfG0mXoLo5Z5SuLD+H5ol0JuuV6To2lzIRKrqlJmmYOad/WhRRc/QCWqiiYvdqugtKapRShcwg/nJ6+hWdvX1H3RjDPqDVELbmTWq521z688iD1AkP7WQuw2AuGC23imrK0RlQcBaRX+1jUTUyqTTcNKWROUgPUADfaVQW2pGyJli0QOr0csKiYl8vQ3A39zW3TqmesRO1R1IJYLAku2tfJvO6Lp1cbgb43FqmRJl3QvKNHaqVYIKToV4iatq+13aV8aw1dkR0oeYGwor64dzEI5Ki9ZUr+hgLwkufUnHNx4MCcQ9LZVdSArhxuGnDegKvS0KfrnAUxhL4huYjxkIQgZYqUjanN2TS0cUkthVqOLnXoI28o+7ci648eCWddh54/auEpcImKcr/r4nLQiD3gxmJPG4GP/1DR806/0+12zaSJhcMVBSwlA/7zT69jYJBas3Joww5GY9vc39j65Pmf3QdtLQx3A2+McgMnLhxZ2oBFCqd6zGPoynUp/RXxDyOcsjZoDCsM/fKiQC3C6IcMxTRtDFI7j0wQUcEuaGgkpEXugw9ptOWCnsGti0oKhBoxKTrIzSqYRBRS07TMQhviIRxb29AWoYX+yGJWB3PQ//lG06/hO2UWWxusVqtd5Tcre6kyiwHraVz1XKV7dArl2GvOj8eha+8MwYTxi4U1lRZg9E001LFjeS49cl9ZpkAWhHkMrcjaQ9JBwX6h0Vl9dEBaFeXjPrygyZyuewn0M0tNRd3+ICIZsNlvExpGIJUqMfAc+QXQ6q7+YYbwkky7NcBC+rxK+9wUg8YOg4UZpMqkg4KRpQcEL8nRtUfngNocVjNVR8rLn189P56/ePPT/PnxX45fv3l7/NNJvxCPgzO/w8xYpLBIcSE1TSu+drAy1tOMSfpQ4zXjQ0oSMoiIPDf1iCRIT6CFH434lDQBwvAwOwkWnMGTJysEQbNJTyNdYx2CrbQmIVozkkPrJMVo9KkFUwSmbg7ZRNqTJ3V6wDAxZEpdBdaBdr5kSoqg4PzWyYcEDIvgVwYc0lDTE7Q0R6ublCOQm6pUjX0KStKyoGqLaR/CLzXBjEqyVCrCI1F1gq+/AwzCXsE0W6ADSaG30jGUzKLoCRoNt8Fnsl1VTellEVIi7dlQUsqjhGgy0IjCwaMVfq0UdHAnwwibwbvoe1aGw4LYvYs2tqMQCVcrW7g32UkdZp1SrevZsKhnsl4Tjc3AifFQUDdDv1bsbri/IGAG50fxjVJwt/DDgsnwFJUyf+o+W8eRkhy1w85ez0rGc4RRn24OUlDsZhLt5kmvfrLdsUk2LDwNOjVM3eD1q++Pfzw5JpJ+7gsV+u+lcb5gurMlNbjgmVKwHYbv1BTX2xnc/99Z+H3fWWj6uR4v/aBUTIZRRfD9dXPfOYvU9v2S3DhPP11fU7r+2ar1mn6u59R0CxLSsVTdNanuOvo//w7DXt3r++HmrYzmRhiFC9nHKPdf86rCPVZoX9L4RCP8D72WcI+R2hc2tkY6py9WkpWi2dn5ZobS6T884xzLLtWtNw92+g8vj0+j9fqfa8U7Qw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Ledgers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all ledgers and can be used in streaming mode. Streaming mode allows you to listen for new ledgers as they close. If called in streaming mode, Horizon will start at the earliest known ledger unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream ledgers since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"payments":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transactions","operations","effects"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"hash":{"type":"string","title":"hash"},"pre_hash":{"type":"string","title":"hash"},"sequence":{"type":"integer","format":"int32"},"successful_transaction_count":{"type":"integer","format":"int32"},"failed_transaction_count":{"type":"integer","format":"int32"},"operation_count":{"type":"integer","format":"int32"},"tx_set_operation_count":{"type":"integer","format":"int32"},"closed_at":{"type":"string"},"total_coins":{"type":"string"},"fee_pool":{"type":"string"},"base_fee_in_stroops":{"type":"integer","format":"int32"},"base_reserve_in_stroops":{"type":"integer","format":"int32"},"max_tx_set_size":{"type":"integer","format":"int32"},"protocol_version":{"type":"integer","format":"int32"},"header_xdr":{"type":"string"}}}}},"required":["id","paging_token","hash","sequence","successful_transaction_count","failed_transaction_count","operation_count","tx_set_operation_count","closed_at","total_coins","fee_pool","base_fee_in_stroops","base_reserve_in_stroops","max_tx_set_size","protocol_version","header_xdr"]}},"title":"Ledger"},"examples":{"ListAllLedgers":{"value":{"_embedded":{"records":[{"_links":{"effects":{"href":"/ledgers/1/effects/{?cursor,limit,order}","templated":true},"operations":{"href":"/ledgers/1/operations/{?cursor,limit,order}","templated":true},"self":{"href":"/ledgers/1"},"transactions":{"href":"/ledgers/1/transactions/{?cursor,limit,order}","templated":true}},"id":"e8e10918f9c000c73119abe54cf089f59f9015cc93c49ccf00b5e8b9afb6e6b1","paging_token":"4294967296","hash":"e8e10918f9c000c73119abe54cf089f59f9015cc93c49ccf00b5e8b9afb6e6b1","sequence":1,"transaction_count":0,"successful_transaction_count":0,"failed_transaction_count":0,"operation_count":0,"tx_set_operation_count":0,"closed_at":"1970-01-01T00:00:00Z","total_coins":"100000000000.0000000","fee_pool":"0.0000000","base_fee_in_stroops":100,"base_reserve_in_stroops":100000000,"max_tx_set_size":50},{"_links":{"effects":{"href":"/ledgers/2/effects/{?cursor,limit,order}","templated":true},"operations":{"href":"/ledgers/2/operations/{?cursor,limit,order}","templated":true},"self":{"href":"/ledgers/2"},"transactions":{"href":"/ledgers/2/transactions/{?cursor,limit,order}","templated":true}},"id":"e12e5809ab8c59d8256e691cb48a024dd43960bc15902d9661cd627962b2bc71","paging_token":"8589934592","hash":"e12e5809ab8c59d8256e691cb48a024dd43960bc15902d9661cd627962b2bc71","prev_hash":"e8e10918f9c000c73119abe54cf089f59f9015cc93c49ccf00b5e8b9afb6e6b1","sequence":2,"transaction_count":0,"successful_transaction_count":0,"failed_transaction_count":0,"operation_count":0,"closed_at":"2015-07-16T23:49:00Z","total_coins":"100000000000.0000000","fee_pool":"0.0000000","base_fee_in_stroops":100,"base_reserve_in_stroops":100000000,"max_tx_set_size":100}]},"_links":{"next":{"href":"/ledgers?order=asc&limit=2&cursor=8589934592"},"prev":{"href":"/ledgers?order=desc&limit=2&cursor=4294967296"},"self":{"href":"/ledgers?order=asc&limit=2&cursor="}}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-operations.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-operations.api.mdx
deleted file mode 100644
index 04931aa310..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-operations.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-all-operations
-title: "List All Operations"
-description: "This endpoint lists all Successful operations and can be used in streaming mode. Streaming mode allows you to listen for new operations as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time."
-sidebar_label: "List All Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWulyGzcSfpWu+ZHYLp6SSEqsSmVlWbZ1RHIsxl4fKhoEejiwMMAEwIhWVKza19jX2yfZaswMNZQYxWfsZFd/VCSBRvfXBxrdfRl5NnXR8FV0nKFlXhrtotNGJNBxKzP6HA2jUSIdoBaZkdqDks47YErBSc45OhfnCsxiOzAtgDMNE4TcoQCpwXmLLJV6CqkR2IKTpc9Ey8wcXJgcvAn0UUNsLGicLVF24BO8AGYRmBAoaLlPEE48KsUsKBRTtC3Yi4EzpVYd3oDHxsrfjIaZVAqcZ9YD84EMMqskOg9n2sz01cmQa4XOAQOeW2csSAcOfYOozxLJE+DMIUhfpxlbk4JPmC83teD+Be3yxAmdVtI6ZypHEkSbWSNgQOAVTNeF5xaZRwFOao60zoLFX3Ni18sUW1EjWqzeE9EwOpTObytVU2wjyphlKXq0pPPLSLMUo2FUcBI1Ikna/jVHexE1IqIuLYpoGDPl8LpRbIPO0wnaQsZgGo7EYOAy5DKWHJThBX5SE3ZGKeThs4nBosuMdljYi3SQ5UFhJWwIGZtKPR17c4a6BMnEwMAiN1aQuI4nmLJoeBn5i4zkkNrjFEkQfMfSTGE07Pc7/X53sDHY3OptdTu9+byxENtYgR8utUAnp5pVchCrgdCVMRQcOnCJyZUAlmXIbAuOs0KRUnOVC4Q3zPE3cIc5jlpIPb0LxsIbOu4N3KF/5dfBnD25ILPTPEXtQTr9n3/925dG6EFgzHJV4B/IroTHeSv1lNDReUo+zxyPCgGj0zowSqbSfyAwowQhZe9kmqeVYQQtF1BY9LnVKFpA6wL9YOaW6SkWOu8S82udDjSBacizDG25MBiYdJAwK7gRhVdXXkxhIkMbG5sycgyLzBntbgGtUiCKG9h1O+9rV91OHbBSpeOYSYXiA5E7QR/imC3CQGUeBa16BJCavIZ4vWlMYTd5UjhipRQTYxQyfaV/2tMI65e0/9ZI/bEiMO0YLziriUI+svRbGTTLiIaMJwtXWhKXvqkCRSuanzaid02XZ5mx3jUXcT0aBkmiRUghodc6Hfp3jc/iwooaETfao/a0hGWZkkWgar91tO6yBh5T6jgOwbKE0UzeIifvyCwx62Vx3lhJfeZqcP/OOocq/uNVicV4lecGM/fBRfVZNG9EHtNMEYorFD2f1xX3qiB62oi89AprNDS+898YS5nF82+KpTktq746DKoml/k8NoFxjNy/x8I/WwccBX5rbH2DDuQorIhvDahaxP2mOKNVUqw6rFonRbC/WgJ42+qldcThRYZjWdtRpCP127tTLluZHFWLouJ+GjPOTa59VI8Ai6Q6mp/OF3sCkjfT7uFlFPLX5ZBQ2XGBfJR4n7lhu50UeU3To/MafcsVT5uWsdP21eX4Y5Gy//BdyJB+WP8upKA/UEJXC+ifRLq7trm5sdXpbW0OVp9SxejPdErv2ikhLSXMx5hOkF57dFiZUIYL+TNh2a7xsMJvPoBmPcdpr69vbuFW3Im7rN+Lu1uD9T5nPO5tbPA13FzrrXfXcXNjYxD3+ltr6+uTyaaYrG8x1u8M+Obm5haxUrsYPlm0dkWsClhlxPoAwiWFH68U9N1NNV6/Oj6aPvsd8mX4iOpfXo8W136sKWbsFkWLKm90Jrf8ys+H0aPt7Zd7G6Odp+ujF73j/cc7o/2dte2Nn09e9Hf2n+8/7u1t748eHewdre0+HRzeP3p2cLyz8/xoEFVR5XrouApKnUb5mxiHsLrW6faana3memfUHQy7vWFv4+U1hhPmkmgYfbI9NaJQmCCUJkzRYymc3+oUfxTsc00v4k8CoI7i4ZOdnZdHGy/+ub3+4qf9xweH/Z1ne7s7B08O9/d3Rs9+Ojl68fz+6GD/+cZB7/HPhy8OH/z0cnQ/JFaf37f7f1/f7v9Jvt3/sr7dX+Xb/dt8u/81fDtjF1RPqDl192s6NXMO/bhKdZiX50iubE36idKaT/HhRsTSEvGt6q+31aJ/g07nC7n44O/r4oM/ycUHX9bFB6tcfHCbiw++houTR5msKppXbt77mm6eMufRjs/wYjxDOU08vWJO5+UfPUE8ale8N15dRmd4EQ1XV8sa1WuE4KOaWoo+MaSSKYaHIfPEc80OKXVAe151DXKr3s8iolVF4lGxDo7Qz4w9C6FgNcU497nF96H5sFoJuqJ6ShXM2IQXXvloK0vGBABaV+zutDqtLsmXpymzF1erILPmXIrQn4DHo9ET2H6yR0VNwTyrapNV36k8tQV7HqSeYmiQaQEWmwG40LcqdmbWiJyjgMnFKhJFq4Re3YuyNzInqc1igBvt8hSrrewcLZsi1AqYYFGFK6DqjNVK401jJWoquAZGLGYWHWpflltDr25ysWBox1ikcr10QfKaHBMrxRRhgn6GqOn4QtrlnU+soUqDAyXPEGbUjvOuAQI5am+Zkr9R6fcdT6gF4BqBQrjLQDqXow0cLcr83oDLJ6EbUIvSDQgFalJR6f5QprYNaqaUTTQ8R13xcb1EfbWzdcOy/tct4VVdoad3KvcUeI6KgoNbiv4l221uLDa1EXj3f8p6XuvXujqu7H6zcFOhgHPJgP/y9LABDCbWzBzacILRWPU9FlifPDhwf4i1MNy1vTHKtZ04c4S0AYtkTkVr2VA56p30F0Q/9IqzAtAGzDB05dIUtQjtZgKKaToYpHYemaBNKTujRrWQFrkPOqSOugtyBrVOcykQCo+ZoIPEzAIkIpWaOvgWKhMP5lhhQ0eERt0di3FhzEH+BwtJv4f7ykyvMJjNZsvCL1Y2J8pM26ypcdZ0uW7SLZRgs7w/7obeoDPkJoyfTa3JtQCjr3tDYTuWJ9Ij97llCmRKPo9p0LwpG4kpe0vt+uLqgEmeZndb8JCmAXRRJaWv2cTk1FMMLBKA5XkL0zACJ8xhA3iC/AxodV3+0Kl8RNBeATCVPsknLW7SdolDe2raE2Um7SIraJN7SY6uujrb1LG0mqnCUh79svdgd/zw+On4we6z3cPjJ7tPT1qpuBuUeR9jY5HMYoJTqakn+r2DmbGeOtnShySgHFmgICEDi8gTUzRiA/fktHBkxMeECRCGhw5tQHAI9+7NEATNQ3gaOjHWIdhca2KigpEUWgQpRuMWWjBFzlSPIQtLu3evCA8Y5hKYUheBdNg7PmdKiiDg+MbNh+QYFsHPDDik0QlPrqU5Wl2GHIHc5Jkq8UkpSMuUEi6mfTC/iQkwKskmUpE/0q6a8bWWHIN8L2WaTdGBJNOb6QZkzKJoCppIqYzPxMuiUq6ahpBIZ5Y7KeRRQDQxaHotwJ0Zfq8U1PxOhpkaBq+jHZaFy4LIvY4W2JGJUEqLNnXH8UlhZrVUben5RIuaJm6W1lh2WRkPteiyuVyxXTf3h+SYRTW9cS0VXE78MGUy/IpKmX/Uf5s3IiU5aoe1s7YzxhOEtRbVtqQg241lqG8VvzSLX65OLIMNC78GmUqirn24t7N7dLJLW1qJT1V4x2TG+ZTp2pFU/IdtpWBp6mYprbi86j3/f7DqLzJYVT4LPb7z7UwxGfpMwW4uy+fSq8gsDdAlxnn69vKSov0vVs3n9HUxT0GPKCEdm6jfm6ioG8nXH7RaKX7xwlyMjpVvyii85z5EuL/MPNUtKFSTZB8Jwt9oduoWkKqpso8E6QuNSd3C8I2prmXO/5DRLzoMdSvn5QjXFb+n9MFKgjoavqKWdYIs9HoWtaJtzjGr6+fGXNRSrejR7iiaz/8LIOZHkA==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all Successful operations and can be used in streaming mode. Streaming mode allows you to listen for new operations as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"}]},"examples":{"ListAllOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/operations?cursor=12884905987&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/operations?cursor=12884905985&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905985/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985"}},"id":"12884905985","paging_token":"12884905985","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"create_account","type_i":0,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","starting_balance":"20.0000000","funder":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905986"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905986/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905986"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905986"}},"id":"12884905986","paging_token":"12884905986","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"payment","type_i":1,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","asset_type":"native","from":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","to":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","amount":"99999999959.9999700"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905987"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905987/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905987"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905987"}},"id":"12884905987","paging_token":"12884905987","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"set_options","type_i":5,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","master_key_weight":0}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-payments.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-payments.api.mdx
deleted file mode 100644
index 03a9010f62..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-payments.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-all-payments
-title: "List All Payments"
-description: "This endpoint lists all Successful payment-related operations and can be used in streaming mode. Streaming mode allows you to listen for new payments as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time. Operations that can be returned by this endpoint include: create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge ."
-sidebar_label: "List All Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXOty27iSfhUUf8wkU7rfLKlq6qzjOLFsJ/bYSrJJxqWBgKaEMQnwAKAVH5eq9jX29fZJthokJUqmE99ymRn5j20Sl+6vu9ENkviuPEsnxut/9I7pZQjSGu+s5HEwTIvICiW9vjecCkNA8kgJaUkgjDWEBgE5jRkDY/w4IFHSuawhoBY4URFoit0NoZITRiUZA4kNcCIkMVYDDYWckFBxqJDTlf9xbDUz5FLFxCo3H0jiK00kzLKZDKGG2ClcEqqBUM6BY2M7BXJqIQioJgHwCegKGfiE0SAomrpE9pQW/1GSzEQQEGOptoRaNwxQHQgwlpxLNZPZvCSWARhDKGGxNkoTYYgBW8KxZ1PBpoRRA0TY/Ii+ViGxU2rTThXy7BJ7WZQD50rHuqBBDKiGVLOS0x+BS0ReKs40OIyNkAywlSYa/h2jqFaEUCFHS/CTSRP0NdhYS+BkfEnsikmFZEHMoZ8OPaKMqVjaUjYn/mGno/S/kbFaMDvSwARcQPFNA5KXnO3TwUYh6AmQilfyFs4x4F7fOxTGbgfBwv1KXkQ1DcGCRr+88iQNwet7CUZeyRPok/+OQV96JQ81Fxq41/dpYGDddbeJjMMx6AQIp61BgCkxETDhC0YCxZwwaEFKmAoCYO5/5RMNJlLSQOLFwpAodo6UGhRIRCdCTkZWnYNMzad8QokGpjRHZQ2bQki9/pVnLyPUQ0gLE0BF4BMNowC8fqdT63TqW62tbq/dq9fa83lpobbSHO6uNQcjJpJmeqCobqClmyYSGmKmKg44oVEEVKPvJI6TugT5gxr2B3lCDQPJhZw8JUqTP3C6P8gT/JVedmHmvIrqSewiRRj5f//zvzYND0s4+DQOEvzdsIXwoP/ICaIj4xDXJWqYlyjoneWBCUQo7B2BGU6BhPSTCOMwcwxn5QSKLEAqBNu58V3saConkNi8jsI3ajVSJlSSOIpApw2dgwlDplRzpniy2mSrCy5eEWhf6ZBi0GqgRknzGdAyAwK/hl29dlu/qtfygKUmHflUBMDviNwpWLe+6mSBytwjGSu/3AuJUYOyXncm1xsjyU1RqMVYqQCoXNof+5Rc+xXr/6mEvK8KVBrK0vVxqQrGyMq9dDlPV1ugbLoIpRV18Uq2UFS8+VnJ+1Q2cRQpbU15kW+8vtPEWywpqHSjVsNfa3ImadUreUxJC9JiExpFgUgWquqfBttd5cCjQXDku8UyhVGN/wSG0RFpFNaKZL5RIOS5ycF9QzsDgf/lVlMNflHkOje3LkTluTcveRbCyNUFBYaez/OG+5gMelbyrLAB5MaQ8Mn+YCJFGi5+KJHm2Cy7dOhMjSGjJPzdvSMXuD+YZOD7wOwtUP2mUhlcY4D/aGJFGhhw+LHEWmvkvH/V45ZWziGb0+ZsXvIELxI3m0lwp36umrzeetXNR2ax+yrSrOQZFWu2qOWLJo+otaAx5bz8uF3+UCv3zq7a7XlOLMq5xlSEU7vOBWVaVmx4q5uHrM9I5HolNVe+V21eSjvyES2Qck3pKTXTwkZuo4XgjWmAJVZhIz+WWEw/FIrHgXTNrQT31hzgRnNfs21qnQXgK5AWAFgA1wKcpXq5QNhxw20vLPvFTALhGHBP/uVATovvXEOqNcVyTlgIb7ESbLLWJmttstYma90za6XPrQrT1VKFx0hR1Biwo2KJFrfx0QHezp5+4DOcC0hWdC7siAbRlMo4bF2/VG84kyXjCGPiR0h1+NDj4UZQD0+5YbE7fN8smrNoCpVTdiHu2Xx1S3a88LVNUtsktU1S2yS1r5bUCl/XAKaS2+3LGt8g6ZUenOWybHnDtP+UJOjGyeN/xy3UX99ILs1mYXYzTByMFclrsVEoigM7G+Xz1dpKqxs1XGn1OIp+z3qnoMRJXW8d/OtQn+XLIDtNS6FTtzadLJamTV20qYs2ddGmLvqGdRF+qXLLoqje3FRFm6ror2OkW1ZFaYuQftoURF+vILoO4+dKotNkVdrUQ5t6aFMPbeqhr1QPrXybe8siqPtYNdAjaSnkg4uI7/sSYdHTaZLz5fR9+6vUOJtcsMkFm1ywyQVfKRcIeaHOYTRVxo78WCbQfNuPuBbTFm/mlqdC7rulcyc0iuUr3tesOU/SP22d87QV0EYLSV3/zAiF2yEaFMOV7BLSj7NGbIonEB6g91/x04MvbbydR/nOEUPh8icL6GxM2blX8saxlk6k4qcUNzx5uMOHBiuv/tNf2Vv/nDoFZvTm33nPmgVZTs6Bi/09ZeyLReSfzRG/NMadF62f1MoH1LL4yMqLZIn3ptZGpl+tTpOjMGULxkqwFZOc0qsoPalmR9v+lZzx+vUnd6Tm1+ZP7szSr3gCKHcC4AEDN5udrU632W1vNWrNZvE02Vf9D5im3uh2W71au9dtr83hjjGh/Ve+kFx8A/nxgUAuD6ZUczIUVFh3GDN/JqbabHZ70PNrfp122n69t9XsMMr8dqvFGtBttJv1JnRbrS2/3ek1ms3xuMvHzR6lndoW63a7vbWS6sGqVbPB1oqiOwycjvCvpYF+um7G9erm3uPTG4ZPSwwvf3G9oli7eVM1kZwzWq8fvJfb2x8GreHOSXP4vn20v7cz3N9pbLd+O33f2dl/t7/XHmzvD18eDF43dk+2Dp+9fntwtLPz7vVWtsRc+8B7WRrUVtO/16jV2+Var9ysDetb/Xq73259KFqM+t6D/anoy2+vUavUkp/ld80PAiCP4uHxzs6H1633/73dfP9qf+/gsLPzdrC7c3B8uL+/M3z76vT1+3fPhgf771oH7b3fDt8fPn/1YfjM7d8eP7Y7f9/Y7nyj2O583djuFMV253Ox3fkesZ19BrsM6vr3DOp8wbosRJNi7kHaqofE8LI89HrZT7tXwV9btdqjhvhqpfKIUd7g49a40WC0Vu/W6z3WrjW2aLfW3up2603fZ36722CctijtQbPOeK8xbjWZXx9z2vJZmz5KlK9q91UD/TqQjx3r6zNk4b52/VrEX7t/56C/txvfK6HXa+VafVhrYezX6jfE/oPd604J/f5xnEPxuHGw9+7Nq6O991uDo+bWm/33W6e7zwaD4f7g+YfT9vOTweC3k+PdN8PW2zcHex9+ezk4eXfawg1S+oO7JAvSoGu7Gv4cLr1+8SnwUrZlQqPiWfEQ7FShu0xg8fKw7y22FIgH6IuMCyPWwe3c1SuiPhgm7chrsDOlz92CVTyiH9tYw23GfJG1JDIb9QwfZfvJ/jrdYKZECKg+aJP0rlVqlbp75BaGVF8uW5FIqwvBHesG2RsOj8n28QCP6nNqaXbiPmN5SWetkAHymEzAkdNITjSUHXCOJSbpGWnFY5YRoFwbIiEAwSeQCzIHoEYgeYgiTEkTh5B1pReg6QRI7lg+cdw34gIyHpoc4UNZaQESaQScIBoiDQakTUkEHC/O+HIh0I7SgCQUwjjNc3qMteATIGOwMwCJ0yfarvY81gofAxkSiHMgMyS/saZEODCQVtNA/AcJDT6lj5VSmhbMuCR5duMkWpBXWEVMPHYcF7lEUiKOdgFNlAYTSeO1hBQhKWkNXDjKGifHOvHCsmflmmf90z3hY96gZ0+y8ORwAQHmUbOSmlKxq0xpKEvF4ek/ynt+l7/LbLqU64i67AmcXAhK2JuTwxKhZKzVzIB2MygJGZvHAuvT5wfmi1hzxUzVKhWYquHnBpFWRAO6U0LlpPB52SdhL3F8x84UJYCWyAwc10wYguSO3gmBohInJkIaC5Rjp5CeIzEUFxqYdTZE/irj9HRmncSCA0kiZgyGTNXMQcJDIZEtS5PMxZ07ZtjgFI5+5okGP3Fmp//zhaY/k2eBmiwxmM1mq8ovWpbHgZpUaVnCrGxiWcYsNIVymj+eOsYbozBMKDufaBVLTpRcj4bEdzSbCgvMxpoGRIQY85BQXamUHiekfyI9VpI6yDgOo6cV8gLZt2Tyxggv07GKkSnHiYgApvMtXENxGFMDJcKmwM4Jts7r7/h3XiK0SwAmwk7jcYWpsJriUJ2o6jhQ42pIEekqhpdgYLLUWUUeHi1pkHjKyzeD57ujF0cno+e7b3cPj453T04rIX/qjPkMfKUB3WIMEyGR6ednQ2ZKW+RnEtbVyylFGC4SwokIbKoSeiEnPQYtea34fZYJwhVzvEMOwT755ZcZEI78YxbZwZQ2QHQsJQqRwYgGTRYpivRmktMAgym/hiw87ZdfkuUBHNsWDYJLN7TrO7qggeBOwdG1zAcYGBqInSliAF+oWAwtyUDLdMnhwFQcBSk+IS7SIsRyi0rr3G+sHIyBoGMRYDxir5zzVVYCA2MvpJJOwBCBrjeTyGymgZc58r9lzqf8VVVVZEXolkScM+2JSx4uiMonEncz5MkMfg4Ckos74RjsKPnd26GRSxY43O/eAjt0EayxQYfmyD9N3CxXqq3s8LBRWfnl1BtT7iDK3APzlDIpEzvv7i8wMGn6FnS1FFwt/CCkwt2FIFD/lb83L3mBYCAN5ObajiibAmlUsGAXHH3XF65oT+6UkzvLGdPFhrq7Tqd0UFM9HOzsvj7dxS6VqQ0Dt8OKlLEhlbkp8e0E2Q4CkmOSWykqrpZ8ShtKww2l4aNSGqYbagufbDUKqHBvzp13X6Vbuo9elCPYxBfGeO3qCjPSGx3M53g5YTLDjR4Xho6Dm7jM8q78/SkOC5VP9sAL0sZ01+u5PeddlPvLMBl+BoWMw/GeIPyNWAs/A1LG53hPkL4SQeFnBL7Gp7gq+RcF/ao0hJ+VPCVPXMp7hv9ogVB7/Y/43n8K1D1kWzzN2mYMorx9rjESrjzNerk79Obz/wc9V3AY
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all Successful payment-related operations and can be used in streaming mode. Streaming mode allows you to listen for new payments as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known payment unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream payments created since your request time. Operations that can be returned by this endpoint include: create_account, payment, path_payment_strict_recieve, path_payment_strict_send, and account_merge .
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"oneOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"create_account"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"starting_balance":{"type":"string"},"funder":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","starting_balance","funder","account"],"title":"CreateAccount"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_receive"},"type_i":{"type":"number","example":2},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"destination_min":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","destination_min"],"title":"PathPaymentStrictReceive"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"path_payment_strict_send"},"type_i":{"type":"number","example":13},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"source_amount":{"type":"string"},"source_max":{"type":"string"},"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","from","to","amount","path","source_amount","source_asset_type"],"title":"PathPaymentStrictSend"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"account_merge"},"type_i":{"type":"number","example":8},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"into":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","account","into"],"title":"AccountMerge"},{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"invoke_host_function"},"type_i":{"type":"number","example":0},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"function":{"type":"string"},"parameters":{"type":"array","items":{"type":"object","properties":{"value":{"type":"string"},"type":{"type":"string"}},"required":["value","type"],"title":"host_function_parameter"}},"address":{"type":"string"},"salt":{"type":"string"},"asset_balance_changes":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["transfer","mint","clawback","burn"]},"from":{"type":"string"},"to":{"type":"string"},"amount":{"type":"string"}},"required":["asset_type","type","amount"],"title":"asset_balance_change"}}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","function"],"title":"InvokeHostFunction"}]}]},"examples":{"ListAllPayments":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/payments?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/payments?cursor=33676838572033&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/payments?cursor=12884905985&limit=3&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905985/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985"}},"id":"12884905985","paging_token":"12884905985","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"create_account","type_i":0,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","starting_balance":"20.0000000","funder":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/12884905986"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/12884905986/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905986"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905986"}},"id":"12884905986","paging_token":"12884905986","transaction_successful":true,"source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"payment","type_i":1,"created_at":"2015-09-30T17:15:54Z","transaction_hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","asset_type":"native","from":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","to":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","amount":"99999999959.9999700"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/33676838572033/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=33676838572033"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=33676838572033"}},"id":"33676838572033","paging_token":"33676838572033","transaction_successful":true,"source_account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"create_account","type_i":0,"created_at":"2015-10-01T04:15:01Z","transaction_hash":"2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a","starting_balance":"20.0000000","funder":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","account":"GAP2KHWUMOHY7IO37UJY7SEBIITJIDZS5DRIIQRPEUT4VUKHZQGIRWS4"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-transactions.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-transactions.api.mdx
deleted file mode 100644
index 828e72c046..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-all-transactions.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-all-transactions
-title: "List All Transactions"
-description: "This endpoint lists all Successful transactions and can be used in streaming mode. Streaming mode allows you to listen for new transactions as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time."
-sidebar_label: "List All Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztPOty4jqTr6Lyj3MLCTbmmqqpXa4BQiAXciFzUjmy3QYH2zKSjCFTqfpeY19vn2RLMhdDSCaZzNmZs9/6R2awpb6pu9XdduuLwvGQKYeflT7FPsMmd4jPlLuUYgEzqROI38qh0h85DIFvBcTxOXIdxhnCrosuQtMExuzQRTwBAGHfQib2kQEoZGAhx0eMU8Ce4w+RRyw4QBcbvwU0EjE0JyHiRGIAH9mEIh+iLdgM8RHMEaaAsGWBJSbwEaALDq6LKXLBGgI9QC0bmdh1d6FPoSahziPxUeS4LmIcU44wl2AAU9cBxtHYJ5GfxI1C3wXGEEZmSBmhyGGIAU8J+NHIMUfIxAyQw5NQbUo8xEeYLyYdoMpczOKCFoFvAWuK3RAEKz6JUlIOQoAx2ZsCMClgDhZijm+CGEkRhUkoSOaOBwdKSiEBUCxGtyzlUOk4jJddd2OJU0qAKfaAAxXr/0XxsQfKoRJTo6QUR6z7JAQ6V1KKgO9QsJRDG7sMttWjjPzQM4DGfEolYYIVjFgApmM7JnKJKQkSssLIJK4LsUyJjSiwgPgMYr1xGApCuWwL0QEK8NDxh/ecjMFfCIrYCCMKJqGWYJiZI/CwcvhF4fNA8OH4HIYgGIEZ9gIXlMN8Xs3ntUK2UCzlSpqae3pKrdgm1IL3c20Bc4Y+XvIhSJWA1goRU8gQG5HQtRAOAsD0APWCeCkd33RDC9BfmJl/od8wM8G3HH/4OyIU/SXQ/YV+E/8sbkul5sIYMR2GHvgcOcz/73/9F18oIkcW2Dh0Y/lLsDvFwzh1/KGQjh96wv4xM5WYQeUuKRjX8Rz+TsH0R4A8PHO80FsqhlzlWBQUeEh9sA6QGCfhS1Wn2B9CvOaaID6jqmgfYR+FQQB0MVAqmMPQCFPLJFZs20tbFu4iAGoT6mFhGhQwIz57RWjLBQTrmew09a16palJgS2W9N7GjgvWOyV3AVx6Mxq7gqV6xLDQyqqF4girEbQ+VyY5W1iSRLGTC4MQF7C/Xn8xJyXH3z093aWU2T4Lg4BQzvZXnlM5lKOUlbkKgBlVFf9ssRFvC0pKMYnPwediCA4C14mdQPqBiXFfEoRh1+3Z0hEtSCTGA5hC8wIq+OZOjO/edfwxS7DywjgGrv31USMK9i6rkCrEpfr7Y+UppXDwAlfoyQ4hPj0l1/VzDPQupXCHu5CA4cOM/2QkBRSmPxVJT2LY8lZHLrWwra/oBHgGiEjg66wsnFBiIKYUC8t0OHhv0CsPPPJcFk+pf7JiYtMkof+z6WYcxv1kRK1d8E9GGNg2mPxnoyqgYIIFPxtZTOxPYP1sZCWi/J+Ksq1B0oOtvcbKUjesY62RCS1ISH6T27unlOJYu9hZUuJYUp8SicBOL8xWCekublPKCLPRzonPvM060FtJ1PG5nhGDFxnYPea7iSAhNeH+uVtdcRVgzoGKUOnoc3n/Vt0v3X3J5Z4S/GLLoiKEWrvney+cwQ4ZbY+43yXIZ1TdM5Ey+ibsHGvD9yM/AeslFj4K8SWWxUBzhOnwBbl5eHZvw24RrHT5flsMr2kG+FNwSQD3M4vuBBtH7V977AHHL44RXL06QMQo9/HdXXogM56QwluioK8uUCJcSwBeuH7iW84bN0tRuTBI6L/FKXuOfy/Gv7imLzxM0JqohZwmCe2vyVg5hfeQ9cyNbBL24uM3kNZJEiPgOf7bjHnXwHs8fMfgmOz7IQ5eN4NwbQczTvG90AhZX3qrnj29RRBLGzBCL7h/35650/uvMcrn/1smkrjdAKiEXpBgWExyfB/oP5jB1/xrYkpLsLnB+la84VjK1s6/sc8vNvVEGJLYnp9txi/vg5u73ubmsWbl+caw5fQ3XPxzh570zhvrcPf09JL2K093T6t6k1yZXRXdwy+KLI1uVkmW6WYcLiojzgN2mE6P4pLZPgfGfeAHLK6dHxA6TCeLzf8R14M//SLLb5/0X2R985OoFiYqGh8ErusFPV/KFzUtqxXyu1EtKxUfRKVlisVsSc2VitktPLL0KRZgo5qwqhd8Xqb+yghcl6CIUFfoxXeTdFrXiyUo2aqt4XzO1koFPW9i085ls2YGipmcrulQzGYLdi5fyui6YRQtQy9hnFcLZrFYLG1l8u8gYzGLpY/K5dtWtl891/uDXK/drPbb1Uw5e3YxyFfb1+1mrlVu94+OW91M/bzQqXSvjnvV6nW3sBlAvwNzPIml9ee59Y8SY3pNxpeF1qSkpqSknsiQdJ1RiYroZvb9w+he0PB2opPJ+bea1cpGf3luYNuZ9sdwCPvciWSROioftp/t9FJJotlMLeNCeLzbfg/ES+PRN3NLJaNquX21tK+rfa1wqOUOc9nb53vaofLNhvtKWqhoW5vgoa6qiT1d/nqWJenbOZBSltfRpekd93LZfK496190znpn7kM0zlzYk3Lbu704yreb+YhPgmhULpcrnfLqqqz/Wxd/OvjoihlHxaGVKc2No7P4UVTevCrGrDrXvc5QHzn9yU326rJeD/Jq0OjRdnc2ONHafHbTj25Gg0w8YUqjYWJ+DPa6eMZ4zsl2s4Nx3t1rXFUqx8CPz/uTed+8rnUvDPNKLTay1914bjfbwY8P2VleW0NqlHddZzvv7roqHTwxW2J8vXIcTa7neh/3ZuTIt70SXD7Y/fPK9NTWs9a0Vla79l6l+Jh9rBCjpF7e8LA68c4m0Ul13twj415LN9WcQfXxaNxU56fZcTUy65sRy3K9yuXyRUKo2/JN0Lf1O8nvpx0BUAJB+UT8qW79XoD95gWsvSbMF5+cbeF/h8LWoJphOZ497Z5twXsHfing+jb9FbfZdh5C6IUX5qXqqLVxe1Bsd8d+fli99S5HoXO+x1YKUi538sVWYnr9FV53XSfb+N9rAGv8LyvMK/if8f8O/PqQ054BtcfLD+KvPJt/ez4fkIL/QMd+o9vi5Vz1+rTav23vkbJ367YMMrZpNTPxq7G8q3vThE6/subPr0/KdnknthYp3ZNtaO/QDikd//YtNLx9dd6Nf5AuXG7BeyP+T582MqdDhYvUYzOR/axcsGOXcTXzwHAl0HPTG7elq+qZ8aiX9ppGFHVrN+mhfbJ3EuGjtNVoFIzhJBgfs1qZjdKTds3p6t3edb6Ua91WSicPe+0ya1YE7jvxEnIR/4t4JSDETdk4NIGnmGV/1zwgYxlZI5MxsaoVNa1k5tRMARfVXKFY1HTbNu1cMWNaOItxCXTNtEoZI6ubtmZYOGubOfxd8oDOabV6280Obsr64KTdPO7kq1etevX4tNNuV/tXJxfdwXWlf9y+zh7nmmedQad2ctuvfDgPKBSz2vdLBT4qyR+VCnyY7p8jFdD1fCFf1Iu5QkaNq4J/TzawjWeZEHzYkJ4lBFuYXskJvgPupSEJm9iVFmjqvqr11axIC1TthbTgG+341bQgzoq0Ykn9jgnC++K9RYKwHT/KHaVvHV09Ws3K1MhE7NZraIPMldppdse3L8SHzfwlaEe904d800if907nrUa1HZydnoQPzqjemrYv7GP10j6ptWIAW/t7fHVOouxpYd7uzycP+YB3R4XK6fymTvp7j1dR37zMtq+Moznxp0MjnrCVcMRCaLtRqOZ6QTo308I5jWDA5uf5oN8nTNdH591byLUaecP1H+P4ZCvea67i4bPaRaWSg279eHzdImfGrTY4w0Y7rOe863T5eESb/VlUaupemmGnpA5MfOuyMugh9EoP9dnDxW0jUyzdmufZqalGjUgL0tfzsvnpg8nCa9f7koXmJBE+VPbcJj9/eMjujTJptf9QdCpnDr6sPXZIlpxXO/NLf84bzcfyvLUh/Ep+9ApBryYLm/jfrrwyWcjunUBTSilWxmeK8BX8y/Eb9FcfT3q1vaJzWZyQvYnRH0DUL7qz43qaaWZdb/SqV9czNmkXskebygPktWz0tXBwU37vDdZrpHNblDMlPa3daF7Evxq/Qf/Frdnhvf7E3jMtg02KTa9zMobJpZrvdEvZy/71TXhRAS93W4xRL415Yz138br7qmzjb0zrnQ4MwhoctXuBPbo6O7vw6cX4Ms/GemP4eOnpDeu0Ao2HgawWWIW+asuZ287sq/i/lixUcrnE6G9IpUIiZ0YvUvB3aocBteAbteNtyUK3VW+6WfVscj5wRhXuX40qAfOyfe/WKJYnR8w6bdZUG4y92aSjn49mgXcdVQqQyxYyJ/2jbnt8Yzxq7qzplB775ZvatV8yWpVoK1n4vm8ITMhgE2dssPS8hTM2Bqxrei5jFvJmDrJaRs8Wi8UCzpqaVjI0KKkWFC3NKOkFvZT/h2cGudx3fEnwQUn+sJcEH6X7Z8kMki/8/s7MYBPP6lXBRw1pR2awgem1twUfx73ODHK51zOD/KH2QzKDZ68OtI3MQNuZGWjfIzMoxzWu7UpmYvtabxmNxG87OC9cDrJ7p8SalurZdGt42fLccnGe7x3Xz5yi2y7S8/NidOK8tOO9eiUi865RM6/Zuc70x+LZ4wRz0zLT40wn27m5bp+U83CDzaJl3IzLlpkNgmYm57Cjaq4XTY/U/FU0NfUq6GmaoQOzcqpPZ6OZViwXX47Mj3ZWpd9Tpk+URWXkW1w/em/kq4NaqgzXi7NOFWL4747kE3O3rq9FRx+JTro6Pz3/QOwqo6Ppx/CfDdb4T3aj+UB0pLHuDM+a8Gifzmq9YKLNtMe9/mA65NZgHNWCnBU8zjQOZxXt0fHGtuEdR4POuFAtGv3gplp6NNsFe2+K+SiqpyF91GzeRLU4Ooq/dJEfu8CMg8/i3fzzF2UMc+Vwd+9Ravlxi9yX7gQHfESEMx8Cj79NEt51Y0cQTAGdLjscQ+q+bVtRdjW09eNxqAs8InQs21J2Q7RDIcW3wGwsRyJ/CfVOfPdlxy0miy+BFu1tQgRAWTxbPVAPNLnNeB6m8/UoFFAydSzZS4ma/f4pKp+2RC+ZhTkWbWPJTtkF1gPU4sjxhyDben0LUdiXgpOdtvHMgBIrNMFCxnwXiLitU3wIuGrRA8wc0RJKkEl8FnqwnIqnQPEQUKIhDFFwMXemsOzlTbTx7RPqgC8aXiUhFAIKDHy+6IST/cXGfEVQlVAQrYUOk5wn+DCoYw0BGcAjAF+gj7ndnHlKifi0jiHXGQOKRAMxZylkgQk+p9h1HsFCMDNHol2RpSQEzBgInlkIVFK0aknkBLHQkJ2LCcVMIdkPKJZosY0iA7uC2ZRo/Fw0/cIU/CUdGw3AorN2NfPgmWb9u2vC5+SC3v22NE8L4tiCso0QckF22iQU9n1iwe//Vtrzp/+nv0S36NjHMnIFC00djMzL804KYWRQEjGgEgPxYdnuvJL1Re2YfVXWFjFZmhPisjSzxkxImiAKQp3iVngivnCcOXwu4MvO9iAWaApFIDuIPQ98S7bHC0FhXyBGjs84YEtM8vBYNNZbDgWTyzUUZwAwyadc1mHoWIBiizGAoRGJpEgsz/HFqQMULVVcquNSNgKFbCr+jYIdK7Pkv7bi9FdUcclwLYMoijaZX43cN1wyTON9H6J9Fvr7Yhcawf5i//hd9jEzIswEm+MhFV98I+JvW0OsO9QcORxMHlLsIscTNg+eXHmyaHr28IM4XiDeOpD4aPr3A9QQpxf48Yfb4jY2SCj6nyWJQoALfCvVIBYYmEEKmSMwx0iMTvIvu6qPhGjXAhg6fBQaBybx0gs5pIckbbjESHtYSDotzMsxgS23zrT4ppz62I015eiyVavfN3rn97X6Vb3TO62fXxx41u9yMStgEwpCLQwYOr7o3/6Vic8yuei6d7hMLhZHLAgn4UgSwRyRuGlcUi+MFnWJ9S1uAlnElN3kUoKH6I8/IkCWOL+Bi6MyCGWAaOj7goilGMWCxk4Ki+MhfAu7wpiSPmSlaX/8EbsHkGcoYNedS9By7v0Uu44lGbx/tvOBMAwKiEcEMRDHPHBhWr4J1F+4HAtMEgbuQj6ecNKOJ0Iu7HOpfgaRYnQdbDiusEcxK6F8BxuGIWzPwz4eAkOOUL3IT6EAU7D2LXGGxlL5iL3JKgm440mXKHAuZgqXJxwisZEvSgLotwh+dV2UsDtHngKC0Z9KFQdysxDg/lRWshMqIssZ1GM9+yJWs0SotlFDEIP2ib2/0MZF1zo2ZZFs0dW/JDup7g1hmHLxldRWKLgZ+IGHHXf55fB/Jp+Jqphjgs8ggascYHMEKHMg3q85ltBd2wG6erIfP1ljXDgbLJ/GVbMYKEt3WtV696IuphyMuOfKGkhAGPewn0ApvidHZddFW2eEbAQWX9bd/P9/IMw/7ECYRKqXDlzsyAYTqUFfFqnTZ2UjdbpLKSPCuLj/5Yvw/JfUfXoSt+OjLERCZTkMG+5Lh1kk1eXHHxCzUwBxvrk68maRYSoyt3sPc/+Yc2BekcLyBJxvFML/oTNfXhHS8jScbxTS33S8yysEPzuNZk35nfhBHUG6cvhZdBiNAAsdWFdiyqYJQZLfZ2e4bFRijup95enpfwC9o4Qq
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all Successful transactions and can be used in streaming mode. Streaming mode allows you to listen for new transactions as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"ListAllTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/transactions?cursor=33736968114176&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/transactions?cursor=12884905984&limit=3&order=desc"}},"_embedded":{"records":[{"memo":"hello world","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/3"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=12884905984"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=12884905984"}},"id":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","paging_token":"12884905984","successful":true,"hash":"3389e9f0f1a65f19736cacf544c2e825313e8447f569233bb8db39aa607c8889","ledger":3,"created_at":"2015-09-30T17:15:54Z","source_account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","source_account_sequence":"1","fee_charged":300,"max_fee":300,"operation_count":3,"envelope_xdr":"AAAAAAGUcmKO5465JxTSLQOQljwk2SfqAJmZSG6JH6wtqpwhAAABLAAAAAAAAAABAAAAAAAAAAEAAAALaGVsbG8gd29ybGQAAAAAAwAAAAAAAAAAAAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2AAAAAAvrwgAAAAAAAAAAAQAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNgAAAAAN4Lazj4x61AAAAAAAAAAFAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABLaqcIQAAAEBKwqWy3TaOxoGnfm9eUjfTRBvPf34dvDA0Nf+B8z4zBob90UXtuCqmQqwMCyH+okOI3c05br3khkH0yP4kCwcE","result_xdr":"AAAAAAAAASwAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAFAAAAAAAAAAA=","result_meta_xdr":"AAAAAAAAAAMAAAACAAAAAAAAAAMAAAAAAAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2AAAAAAvrwgAAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAMAAAAAAAAAAAGUcmKO5465JxTSLQOQljwk2SfqAJmZSG6JH6wtqpwhDeC2s5t4PNQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAwAAAAEAAAADAAAAAAAAAAABlHJijueOuScU0i0DkJY8JNkn6gCZmUhuiR+sLaqcIQAAAAAL68IAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMAAAADAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNgAAAAAL68IAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAADAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrObeDzUAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAABAAAAAwAAAAAAAAAAAZRyYo7njrknFNItA5CWPCTZJ+oAmZlIbokfrC2qnCEAAAAAC+vCAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMAAAABAAAAAAAAAAABlHJijueOuScU0i0DkJY8JNkn6gCZmUhuiR+sLaqcIQ3gtrOnZAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAAADAAAAAAAAAAABlHJijueOuScU0i0DkJY8JNkn6gCZmUhuiR+sLaqcIQ3gtrOnY/7UAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["SsKlst02jsaBp35vXlI300Qbz39+HbwwNDX/gfM+MwaG/dFF7bgqpkKsDAsh/qJDiN3NOW695IZB9Mj+JAsHBA=="]},{"memo":"testpool,faucet,sdf","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/7841"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=33676838572032"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=33676838572032"}},"id":"2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a","paging_token":"33676838572032","successful":true,"hash":"2db4b22ca018119c5027a80578813ffcf582cda4aa9e31cd92b43cf1bda4fc5a","ledger":7841,"created_at":"2015-10-01T04:15:01Z","source_account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","source_account_sequence":"12884901890","fee_charged":300,"max_fee":300,"operation_count":3,"envelope_xdr":"AAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2AAABLAAAAAMAAAACAAAAAAAAAAEAAAATdGVzdHBvb2wsZmF1Y2V0LHNkZgAAAAADAAAAAAAAAAAAAAAAH6Ue1GOPj6Hb/ROPyIFCJpQPMujihEIvJSfK0UfMDIgAAAAAC+vCAAAAAAAAAAAAAAAAALMw4P7yJTyqj6ptNh7BPyXEoT+zVwTcU4JVbGyonvgbAAAAAAvrwgAAAAAAAAAAAAAAAABJlwu05Op/5x1uyrweYsyR6pTTos33hRNZe5IF6blnzwAAAAAL68IAAAAAAAAAAAHwXhY2AAAAQDSBB5eNEKkWIoQbZ1YQabJuE5mW/AKhrHTxw9H3m/sai90YcaZlsAe3ueO9jExjSZF289ZcR4vc0wFw1p/WyAc=","result_xdr":"AAAAAAAAASwAAAAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=","result_meta_xdr":"AAAAAAAAAAMAAAACAAAAAAAAHqEAAAAAAAAAAB+lHtRjj4+h2/0Tj8iBQiaUDzLo4oRCLyUnytFHzAyIAAAAAAvrwgAAAB6hAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAQAAHqEAAAAAAAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2DeC2s4+MeHwAAAADAAAAAgAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAB6hAAAAAAAAAACzMOD+8iU8qo+qbTYewT8lxKE/s1cE3FOCVWxsqJ74GwAAAAAL68IAAAAeoQAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAB6hAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrODoLZ8AAAAAwAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAeoQAAAAAAAAAASZcLtOTqf+cdbsq8HmLMkeqU06LN94UTWXuSBem5Z88AAAAAC+vCAAAAHqEAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAeoQAAAAAAAAAAFvELLeYuDeGJOpfhVQQSnrSkU6sk3FgzUm3FdPBeFjYN4Lazd7T0fAAAAAMAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMAAB55AAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrObeDuoAAAAAwAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAB6hAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrObeDp8AAAAAwAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["NIEHl40QqRYihBtnVhBpsm4TmZb8AqGsdPHD0feb+xqL3RhxpmWwB7e5472MTGNJkXbz1lxHi9zTAXDWn9bIBw=="]},{"memo":"","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/7855"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=33736968114176"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=33736968114176"}},"id":"3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a","paging_token":"33736968114176","successful":true,"hash":"3ce2aca2fed36da2faea31352c76c5e412348887a4c119b1e90de8d1b937396a","ledger":7855,"created_at":"2015-10-01T04:16:11Z","source_account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","source_account_sequence":"12884901891","fee_charged":100,"max_fee":100,"operation_count":1,"envelope_xdr":"AAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2AAAAZAAAAAMAAAADAAAAAAAAAAEAAAAAAAAAAQAAAAAAAAAFAAAAAQAAAAAfpR7UY4+Podv9E4/IgUImlA8y6OKEQi8lJ8rRR8wMiAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHwXhY2AAAAQNbDcWsR3s3z8Qzqatcdc/k2L4LXWJMA6eXac8dbXkAdc4ppH25isGC5OwvG06Vwvc3Ce3/r2rYcBP3vxhx18A8=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAAFAAAAAAAAAAA=","result_meta_xdr":"AAAAAAAAAAEAAAABAAAAAQAAHq8AAAAAAAAAABbxCy3mLg3hiTqX4VUEEp60pFOrJNxYM1JtxXTwXhY2DeC2s3e09BgAAAADAAAAAwAAAAAAAAABAAAAAB+lHtRjj4+h2/0Tj8iBQiaUDzLo4oRCLyUnytFHzAyIAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAA","fee_meta_xdr":"AAAAAgAAAAMAAB6hAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrN3tPR8AAAAAwAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAB6vAAAAAAAAAAAW8Qst5i4N4Yk6l+FVBBKetKRTqyTcWDNSbcV08F4WNg3gtrN3tPQYAAAAAwAAAAMAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["1sNxaxHezfPxDOpq1x1z+TYvgtdYkwDp5dpzx1teQB1zimkfbmKwYLk7C8bTpXC9zcJ7f+vathwE/e/GHHXwDw=="]}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-liquidity-pools.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-liquidity-pools.api.mdx
deleted file mode 100644
index ec7f62240d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-liquidity-pools.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: list-liquidity-pools
-title: "List Liquidity Pools"
-description: "This endpoint lists all available liquidity pools."
-sidebar_label: "List Liquidity Pools"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWely2zgSfhUUf8wkKR0kdatqateJHdsbT+xETrKZxOWAQFPEGAQ4AGjF41LVvsa+3j7JVoOkLCnK/WNmd/LHFbHRx9cHuhu3gaNzG0zfBCfit1Jw4W7ImdbSBhetgINlRhROaBVMg/NMWAKKF1ooR6SwzhIqJaHXVEiaSCByxaJAFp2gFegCDEUGxzyYBifCupWcSkwrKKihOTgwqMZtoGgOwTQwYMFcAxIIlP5bCeYmaAUGfiuFAR5MUyotbCv5SOc5bVtApg64V5PolFBrwVkiFGFUaSUYlSTVJif3HmkO02NrSzB7jOlSueP9+y3iNNFK3hChmCz5B7aRRSZYRjJ6DaRRleTUsUyouYcFJQOvBXeCZWtlGq3EfKVle2TmQEpqSH2eHO9/Xk2hak0deq85KSwpqHGCiYI6VFgock90oEMyLbn1Z4nNqAFLnL6/oT0rjdXmq5VXZZ6AIS6jjvgIQs6EElsAE6lgRGrmAwV1oYRpKYH5/+sUES60smAJVdxrX0oJnKRG58RlQAo6F2p+6fQVKHJNZQne6cQA04ZjIFqWQU6D6W3gbgq0QygHc0BD4D3NCwnBdDgMh8No1B+NJ4NJFA6Wa2Zrw+HrreZgxVzRxg5U1TO680uloSU206XkhBYFUNMhp56HXfn1HbXsHblHLQPFhZrfJ9qQdyjuHbmHf+qfO+Q4rX1t5mUO3tnqP//6tyMWXIsIRziktJQV/p7tTnisM0LNER1V5lgfqGVBZWBwsQ6MFLn42lg+z4Dk9L3Iy7wJDO/lCgoDrjQKeIcgneePWUsMVXOofB6h8nEYkjahipRFAaYm9AEmLMmo4Uxz4Aj1kTbid60w40kBBhOfKoaZS61W9hOgNQ4E/gF2UfilcRWFy+UFglJHMVLHYYh/NnGZlYyBxZrHtHKgHJLQopCiyo3urxbpbtekUilPU184a/k6+RUYOqQwWHydqORdSqGu7JqeH6GzINPPU2UG0l3B4pF1PirUVbBsBQ7yQiJ8a9SJ1hKoCpbL9UB5UzG9aAVOOAlrPBS8d38ylQoD138qlZZI1vx04l2NOfqZmIA8Ac43xH6EtM7NNUJqDMVUFw7yL4grwXch0WgsuEd1rYp/inqDbtkKUoDLpNiZgyuoS6FcL/Zge5pt7vhBOyovnSmtk0KB/QRRdTfuJFg1Lp+FxLcGO3nQ3DcIH35CL0tq3WWuuUgF8EsJHC3dxWWT0Il8l9lb0SV4sOWHFbw1cjtw2kKltd687dR2p24Xy+0o3mgUlxfLVUn18O1oJqe3gb/8NwteU9KqdAwy5wo77Xaz6lJoO7BOgevYqr3qaDPvrtqoS99G/a1qen76wd8xP0XhD/4W/wnvxLUC9f0ChsNxb9AO639sMI6Hk1EyHLEE2CidMBj20z5nw1GSJnGS8njYi8ZJMkkn/sMohF7aj9LhIEwiGH5E3aZ4fb+6vfF4PF6pO4knSRwmoxgG40lIk0HE4n4aMdYfpjSMWD/tRWM+5r1ebzjicZ/zYdRnKU8H/UkUjuJtdX2vgRGxUadWlehNVVSC4SgehqzPonE4SuJhnKbjQZSEtJdC1I+iSX/SGyZJGEeDJE5Ho35/lEY8jaLJZAw0SSbbAT8Noqg3igdxf9KL++PRZDzq3WXBtBc2JQQvaeuocpeF0bz0Gf5hDQl6YbidIdNgEPpf74rFm9tV1gdRGIadCtNB0GrqRHDw4vn59HDvbHBycH76cvj6+GAYv977eTCcne/vPT17vn86+uXx/sPD2dOjfzw7fn14+GT28+kve0enp7N45q+DlYT4TkK4JuHs6Ow7BFygCO+SqJ/AgA6SHu+lA4hg1O+NQ4o+SdIJi0ZxMor7w5Sno9Ggl0SjmCWU8T4fDqN+j4XjL3BJ/3tcEu9ySW/wh7okine65MVs/9H08NHgVe/hUfzzs+fPnsRH/b3hyVlv9s/92d7e6/hV/GrYP3315MnLp8+O905fvprtHT3eP8CD6JOqrPrKmoPLNPpnDv42oi4LpsF2cmNTiwjU83hp5JcViWBXl39e0ZGn4BbaXHmTd3NMS1ca+BKejxtKohquFzh/pNrfb/X1Uff8QStAU6rTYSfsRGhfmefU3NxRkcLoa8H9gEmOzs/PyN7ZMTb5nDqKEwRObs38XUvtkGNHhJqDX4QoTgy060UAUvuTVRQCJ8nNLhbVrOv3EM3cAtQKnJM1wVAuc2iO0mswdA5kbRwgBiR14hqQ3I/Bd7NNWxsBCjcQXhEDBQa2crSaK0tbKdUo9EgbwHlLWG/5mh2JEXwOJAG3AFAovrJ28+SZ0djjWCLFFZAFlRKcbREODJQzVIrfgRN4zzKc4WzLc/AhToRfvXiNVnOa08SWiR/nDFWW+kWAbRE/XqKLmkVGQiUa28Jp2DoDNCdwDarRY/20XzesTnY+iKy/eiS8WXfoxb0mPTlcg8Su1W40BLXaXaYNtJXmcP8vFT1v1VvViMPVRAL4CSxieS0oYS+en7QIJYnRCwvGS9AKmh3QCuvZ/hP7Way5ZrbrsDR3Lb+yiLQmBjCcPDemsSd+j0s/nZIbXRqMNgS0RRbg1yp5DorjJw8UVSiYCGUdUI6HcnqFa0AuDDDnfciolNbb6d06LwUHUmVMApZkeuEh4blQuOg0pAlxH44NNsLfxgzIPQNpFcze/v2VpT+Sh1LP7zBYLBabxq8o24nU8y5tK1i0banaeAtl0K7vj/t+uWM1pgllV3OjS8WJVtvZUMWOYZlwwFxpqCQix5yH3Hte15ugnP6qDamvDpKUeXG/Qx5r3NxVMyX+TBNd4lLIq4gA1vJWoaE5JNRCi7AM2BVB6nX7/arpEKG9A2AuXFYmHabzbo1Dd667idRJN6eIdBfTSzCwzdXZxXHXKCqrSDl8cbx/cPn49Pnl/sHLg5PTs4Pns07O73tnPoRUG8CwSGAuFC61frRkoY3DVaRwfluv5l5LLBLCqwgs09UmzWuPSUueav4tZYJwzfyKzSM4JQ8eLIBwTZR2+LigjQViSqVQiQZGdGhVpCjBeOJUYjKt15BVpD14UJUH8ItlKuWNZ+3PXl5TKbg38PKDmw8wMQwQt9CkeT/AysvAqLrkcGC6LGSNT45FWuSFNthw+vBLtIdRCpoIifmIp9aCr7ORGJh7OVV0DpYIDL2FauFeHnib64VaBZ9ON03VhRO5L4kosz6JJQ8Lok6JAuCW3FvAj1KStbzD/aYllLwNHtHCXxbI7m2wwg5DBPtiMLk9TWdVmK21auue9URtnbbraKx3lpT5SbjeDTdqr4f7Y0xM7/ygtdUKbjZ+kFPhv4KU+u/r33C3IRgoC2uy9grKMiBxB7tnwTF2U4GbkfpLu/pyJ7EuNtR/radcz9R2T44fHTydHeCRTuZy6afQQluXU7UmEjcQZPvdbKuvuL1b5X7bC1o92Dh477qFpMJvvLwVt3UH/ybY7uAvWkGmrcNPt7dYgF4YuVziz9WCHvv6j2r5p31C+wgWV3Cz+V5Yr4ACP2x81Mw/9D3tk6bcvQ9uWiIsxshH3lQ2TfujX9s+Yd3q/fCbjfufeVT7BArNc+I3gvB/9ID2CZCap8U7kC7wP0YgSsH0DW6EM6CIJFa06tAeY1Csn/rg/Qy5rFYhhwfnwXL5X6r9daM=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Liquidity Pools"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint lists all available liquidity pools.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"reserves","in":"query","required":false,"description":"Comma-separated list of assets in canonical form (Code:IssuerAccountID), to only include liquidity pools which have reserves matching all listed assets."},{"name":"account","in":"query","required":false,"description":"A Stellar account ID, to only include liquidity pools in which this account is participating in (i.e. holds pool shares to)."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"fee_bp":{"type":"integer","format":"uint32"},"type":{"type":"string"},"total_trustlines":{"type":"string"},"total_shares":{"type":"string"},"reserves":{"type":"object","properties":{"asset":{"type":"string"},"amount":{"type":"string"}}},"last_modified_ledger":{"type":"string"},"last_modified_time":{"type":"string"}},"required":["id","paging_token","fee_bp","type","total_trustlines","total_shares","reserves","last_modified_ledger","last_modified_time"]}}}}},"title":"LiquidityPools"}]},"examples":{"ListLiquidityPools":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools?cursor=66835-00000000c582697b67cbec7f9ce64f4dc67bfb2bfd26318bb9f964f4d70e3f41f650b1e6&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools?cursor=38888-00000000929b20b72e5890ab51c24f1cc46fa01c4f318d8d33367d24dd614cfdf5491072&limit=10&order=desc"}},"_embedded":{"records":[{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","paging_token":"113725249324879873","fee_bp":30,"type":"constant_product","total_trustlines":"300","total_shares":"5000","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"2000.0000000","asset":"PHP:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]},{"id":"14be5a5b3d3f5e1e74380ab0a3bf9c172b7246fdf7753b172cbacd4d66143c08","paging_token":"113725249324879874","fee_bp":30,"type":"constant_product","total_trustlines":"200","total_shares":"3500","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"1200.0000000","asset":"USDC:GC5W3BH2MQRQK2H4A6LP3SXDSAAY2W2W64OWKKVNQIAOVWSAHFDEUSDC"}]}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-strict-receive-payment-paths.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-strict-receive-payment-paths.api.mdx
deleted file mode 100644
index 40d5fb920b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-strict-receive-payment-paths.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-strict-receive-payment-paths
-title: "List Strict Receive Payment Paths"
-description: "The strict receive payment path endpoint lists the paths a payment can take based on the amount of an asset you want the recipient to receive. The destination asset amount stays constant, and the type and amount of an asset sent varies based on offers in the order books."
-sidebar_label: "List Strict Receive Payment Paths"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWm1T4zgS/isqf7iFrbwwQAKTLeo277wEEhIyJCEUKHYn1mJLXkkmw1L571ct2yEhYWCY3bvbmZ0vGWyp1Xr66Zbc3Y+WphNlFa6sFtWusq5TlgPKlizQTHCrYF24QJSWzNZEgg3sHkhAH3zgmgRUuwS4EwjGNfGY0opoF8xzReh8nE050fQOyIgqcIjgZhT1Rcg1EWNCOaFKgSYPIiRTyrV5L8FmAcP5WiRLZwiq44DSjFNUMJ4Yy1KaPihiC6405TpFKHeMKP0QgPljzZoKV7inkoF60k+MxyAVYZGmQjogyUiIO5UZ8iGvCUm0yxRRQKXtpsihkOwPwYknqIMbRyjMIriCIvSeMo+OPMCdoEAFHCVuzNe7VSKUNtxQ20YFb4mQT8+MkNtNswGHqcDDTRqchVIMxUaAj6XwzXOHofq4r0hEoke8+gp8GdLk3kMsRbtUE0U1U+MHM/x2YfxNBOAtoRINpEPJwckMuZWyRADSjDlyrILVYEp3DGvakeVaERcikqWsgErqgwaJ1Hu0OPXBKljLKFgpiyEDfw9BPlgpS8LvIZPgWIUx9RSsI2pHg+dRSajjSFAKbfCEd4YU+cNc64i9fqgMbaQmU6bdJ1oYGBZs5QrPURnSVYxPCDDtgnyL1QhVRqachMYVmCLJNshYyFXP0m7iNipjpSxlu+BTq/BoIYcRIi0Zn1gpCz5TP/DwUb1yen5+dny6223snR8V8/nWXnu7NTg8PT86uxyUTvf2StXS6WGj1qvkjqvd4mH9eK+9ezywZrPUCvRG7a9Evkhs4fs0rQDNqsF5owN8lUGMLzJlRGdIldpu8kIhkj7VuDBV5LbcrFQLR51Ot9q+KZbLze7ZxW2GoNPGmBXIbbdTKdQr3ZPTerdeGZyf5PuH/WJukC/2t+u7vUpn0OoMdjqXue7ZTrH96bSZP++0K5etXL9R7d3+f9KgfNYv1IvtarXRLe3uHLUPL6vFTrlWapwcdtvl+ulhNXdUy/c61b1qr9IolvuH9fbh6e5Ou9bsLVFhyd9R/xuz6Iuc0DJc64wm6o5NrFwbdKoxfPj0Hm5T5NaW4DB9Q73ApTz0d29TBstnjz9s376CCQ99PNEiwVbKei539dGHbev6yxgwpUKQf15MiuQlf62Bp50QhI3XxOG5XW6RTFzoOY5vDxvvo/8rXLGF8wWuvIgSTvsSWf5qNLqdyssb8798HL3kAE+3jbWbio9aV4SeQ0aQeL/zVpVz1mx2nbI+p1UYBEJqlVZaAvVxXKyTBBUIrkChpO2tLfxZ1rMT2jYojPi24Bq4xiE0CDxmG1Wzvykc97iqkRj9BjaiEkg8+zWLVrkBfwSOg7i8NlSCLaSjFgZSKSliyzT46nUBi0E2ClIrgM1Sy6MMPV8dFTv7GvgDPGckIle/KqYHW+mP14+53MxKWZppY5bYzxdlRvxZt+oLsfZtQ1/cy4vR61s3tMYr1q2P59f7rfoKDq/s/U/c72zRya8W9bp+Gh35hUoX8a01mz2ftcrR57x4kQVr8Y7RvY5WSrTAezXuPo4OBselOziDZ3fwwqN1T70QVnx27pVXax1s3WG6xsPwOvL8TWIU693XlBWXsrb3Mx/39z582PnwMo5rdX7JnaxSab2oJ+0rueP8YaOWy+fzvd3ioHFRu+g1+rv541zncq/aa5+UGtV+67i1s9PZ2TntDeqf8uXL2tl6exasXGYr+pfYFpF/Tf0llXvlM+s58616+ayfa/b6nf5u7eSw2brY7rSa54Nis3pU75VyjVL/cufwU3enedm5OD+66ORzp7k2Wg1PwaXl43vU7Brf/A0o8TGztbe9vbe/3sw/BiW6jYt1lNjLt09rZ2e9Uq3SOW6XeuVi6bJx2Kuc7B5dfDrvnB7l8pXy9uD4U3mn32w0WuWTE5T0HVBi1+C5/R1T4m9mk50Pmf2Pudz+/v53bJNX3bRTWeOmpW6/Wzzay/V6l5VB9aTRz+fLtf7Jeat6kTtu71arZ71BqTvY6fcGe5VOLj/YbZ40a92/vZvu7Gb2tvbzWz925F5LiXd/rL9MCXOFjK6Rn9O4eCe5O149Wh7Fr0ir44LnzS2F2ofSI67WgSpks26U905rUJqDzqgo1ZERcpI12eRslNhKx5+2/x4Oh3wpM3bwLVmrf6G49TQ5eI7yC2Nx2wel0ocXXkf4H7yXJKtSDU0OckNuDBODfEzvacd8k1spy6Mj8KyC9WsMZjb+TSvnbtEQ91QmqaWOc0cOkoTixtBamDG0Nn8ZchyrQN6DJAeEw3RhYiauXWQ65v3GkBMytN5g4KGVGnIUPuSRaJyZUcs5f+0qI5GQq+iHPF/efDZtJC9x7fJZ38h+evJefiyI2Yz/dx3/flGLIYaNhcnDd0eJuZBk/aGVi59tGrxs6nkb0X+1C3xjHHLbZIg2MHWzSR6jaVjSEh5kPDGJXvyCz2eJDG27CzNBypWJIKWQ5k0885dlCrYetCv4Av1iS988Y52pMS28I8zH1BOJ2JMiBsiEEeSAJKx6G6M2kU1JzoocxJyNSXUTB5GbYIFWkWIHV090iU0Z0+ib2LO5zJmV8HCwSt5l4nwbdZaZsyaMGDIN+eacRUMeSMb1RgLhJhr5GrMCGrhigkex/Q4erML6vGEqSQpg/hCn+qBdgRW9CcxzDwVrbXRHnhiDRauEEnn0Brtb63KnF9E4cgZ6KuSd4ep6ieNQhxLeIrOWjCQ8kXqNSd2xMImiOJUSB0SEAqSKZm9ltjJ4kVCh71P58DSKBFLcMwdMeefw4qJFiq0jrHI5VNOkfpxUAOJVM+QIy1kTwHo5FnUlpA1wUVXXzAykcEIbHDJ6WCcCJVNT9oqSyEwRoIqBxKXR50Mfkqn0HiSdAFlI6hIJnrkGJPW4AKSpoXEb0kJi0R2cSBEJgQSskZuJioQqUipRqCykqcozZXa+sI+RZM4EyAj0FIDj8tFul2e2pMAkINb17oBMqeeBVinigA1cS+qxP8Ah8Nl2KQIWlfSTuh+ezUajeQFeC6LCkc800ZJyRU1EVClicvamAhfV6MiIerhZU1+K2E/gHqttkR6Ls1Ho08zMCrN+dCZcLRr0eiNxTwfuwcO0rlq6FsZqZ20hIc2FA5s/FHswRifLYVvMCPAVKMTynlFid9uNFKFkJMVU4YEqJBEckhrSHOtO5US9irUjbJXVQngqq5w7hUhjJw3SyUizBd73PzP9gPIfRCiRbQhoikxNPUr4PnDH9OUgUJTjwoRxpYE6OMmnd1gJd5gEWxsb4lkUtckYs05C5pjaly3ZCBRxxdRA4viMM6VBkoTiho4JNsy08NiA96BxRGaz/8p8pz+RkicmTxhMp9Plzc9HpkeemGRpmsM0rUKexlPIhXR8fmxGBXiBbkLtu4kUIZ/3KC14Q8QdabtMg61DST28+0hxD6ZKH1mIKeLT34Qk8dFBRqEfbEbNB3jOYJuCqf+NRKhJrCICGK83p4ZwAJuDUsR2wb4jOHpx/6aJoI7QPgEwYdoNRxlb+MknQ3YisiNPjLI+RaSz6F7MBpUcnVnGsRRCvYgp9e5RpXpTa7ZvKtVP1UazVW13Mr6zaYxZgrGQgLQYwYTxFGH6J0WmQmqXSGDaNP/wSdLdoZlREWxXYM022t0VOi05E857wgRxhG2aJwyCBfLzz1MgjjDFXuCOkAqIDDlHJRIY0aBRkKLYU8Id6qEzLcaQOdN+/jkKD6ACsBn1vAcj2sy9uacec8wGb1ZOPkDHkED0VJCkAwYjrw2SxyHHAVuEgRfj42OQju7N2OuG9BsJA6PH6Ih56I84a4F8mSXHQN/zKacTUIQh9aY8RQIqwUk7Ysrn5BPj5a2KQDPfhERcM56JIQ8DohgTDuAosjGFnzyPLPgdU6Z/Bb/NaGAOCxQ3tObYbUYtYBqkr5rjTkSzhavaomXNoLQYp2M2xpVnaptSYlx9T9RepHsNHdMY30o9uwouX/zAp8y8Bc8Tvy6+m6Usj9nAFSysVQyo7QLZzmDKhjnI3TEzSZfoTTp687RiHGyoeWv2FAtV2cZRuXrWqeKUjKt9z9QQA6G0T/nCkliZI1FpjsTfyiQuzpGkQ27pkvH4VJ3/pyHzn4bMNzVkxvk+DZ91NvAow+/9iMWPSWbS/CLZnn3IXacsVyiNIx4fEZOu9GYzfBw1v+DnncMUIvhCT89zwn53jZlr0Y0+rFe6WONPast8xL4dt3/aKv8PjJj0w77ThhtJ39om+S+0RH5hPy+2mLxzY/+rzsav2uK8Z/MbNvlXNiZ+1Wbixso/h4jf0Jr4VqX9leh3jX9IhhpbhavrWcpygTp41ZonJYu2DcHirJVWxKWkZL16Yc1m/wGy75s6
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Strict Receive Payment Paths"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/paths/strict-receive"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The strict receive payment path endpoint lists the paths a payment can take based on the amount of an asset you want the recipient to receive. The destination asset amount stays constant, and the type and amount of an asset sent varies based on offers in the order books.
-
-For this search, Horizon loads a list of assets available to the sender (based on `source_account` or `source_assets`) and displays the possible paths from the different source assets to the destination asset. Only paths that satisfy the `destination_amount` are returned.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"source_account","in":"query","required":false,"description":"The Stellar address of the sender. Any returned path must start with an asset that the sender holds. Using either `source_account` or `source_assets` as an argument is required for strict receive path payments.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"source_assets","in":"query","required":false,"description":"A comma-separated list of assets available to the sender. Any returned path must start with an asset in this list. Each asset is formatted as `CODE:ISSUER_ACCOUNT`. For example: `USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX`. Using either `source_account` or `source_assets` as an argument is required for strict receive path payments.","schema":{"type":"string","example":"CNY:GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX"}},{"name":"destination_asset_type","in":"query","required":true,"description":"The type for the destination asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"destination_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the destination asset. Required if the `destination_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"destination_asset_code","in":"query","required":false,"description":"The code for the destination asset. Required if the `destination_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"destination_amount","in":"query","required":true,"description":"The amount of the destination asset that should be received.","schema":{"type":"string","example":"5"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"source_amount":{"type":"string"},"destination_asset_type":{"type":"string"},"destination_asset_code":{"type":"string"},"destination_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"destination_amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["asset_type"],"title":"schemas-Asset"}}}},"required":["source_asset_type","source_amount","destination_asset_type","destination_amount","path"]}}}},"title":"Path"},"examples":{"ListStrictRecievePaymentPaths":{"value":{"_embedded":{"records":[{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"28.9871131","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"credit_alphanum4","asset_code":"XCN","asset_issuer":"GCNY5OXYSY4FKHOPT2SPOQZAOEIGXB5LBYW3HVU3OWSTQITS65M5RCNY"},{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"29.0722784","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"credit_alphanum4","asset_code":"ULT","asset_issuer":"GC76RMFNNXBFDSJRBXCABWLHXDK4ITVQSMI56DC2ZJVC3YOLLPCKKULT"},{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"29.4000002","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"31.8955888","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"},{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"CNY","source_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","source_amount":"34.7086084","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"5.0000000","path":[{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},{"asset_type":"native"}]}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-strict-send-payment-paths.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-strict-send-payment-paths.api.mdx
deleted file mode 100644
index d84502a664..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-strict-send-payment-paths.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-strict-send-payment-paths
-title: "List Strict Send Payment Paths"
-description: "The strict send payment path endpoint lists the paths a payment can take based on the amount of an asset you want to send. The source asset amount stays constant, and the type and amount of an asset received varies based on offers in the order books."
-sidebar_label: "List Strict Send Payment Paths"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXGtz4rqy/Ssqf7h7sgscgh9AdqXuwbwJr2DeQyoRthK8YyyOJJLJSeW/32rZEAhkksnOSc3cYb5ksKSWunt1SzL0elAEvubK8VelhcWUK+cxxSXcYd5ceDRQjpXOlCAumOcIxEngojm+n5FAoDkWU0QCd069QCDf44IjMSXyOUd41c/BARL4hqAJ5sRFNJC98IwuAoHoFcIBwpwTge7pAt3hQCBB5UwqklPTBXNI1CUaxQW+58ihARc4EDGEA1cKFfdzIj/skM6IQ7xb4qJbzDzCn1ZDr64I48gL10WZSxiaUHrD1XEwDoqUITH1OOIEM2caQ2XKvP/QAPkUu6AmKC4nglnAAlhIQYw43txbGiCaHX1ZTXvpEi68AIOVL7DjwIIvEWXPGqTUywOplevxuQ+aSzNTzr2Jv7T3FaMz+dz1QB+Yd91yHIwqm5+Ehy0qagb+fSRFrp5j4fGre9n9MhRyERr0EmEGmokFC4irjgMlptA5YVJcxVWOlZrHhS3BYpPAbYUQCIEVU+aY4RkRhAHcHpQAz4hyrCxngMVcgAeVmOIB8P69IOxeiSmM/HvhMeIqx4ItyC54Sr9fSU9tAkZFBU9MCUOXoPItuYyhS4cR1xMX2J9PcbCY6ZcxafVnj4+Sl6oSU7gzJTOsHD8ocmXHCkRCcK3EFBIsZhA1oWAlpjyXu/3oKKmcPz7Gdmvucb4g7GXdr7DPdypvC+L7mCHsuoxwDlgEM4Tylp82jdKOpCLvatPLKx9cIo+jgIqV4V4xxjc8m/vwqJSvn501qnW9W0udVbKm2Uq1k61RuX5WafRHVj2VsgpWvVwrDvJGtdDNlkvVVFuvjpQXDeNQ9zuQeNEsMOwFTPwX1e/a+Z2ayPD5cWA/5bHnWkShOqUL30UTAglTvHWRxsYSd+Shj0NhlPeYirLB/SpzhHvHbMEFbCDozhPTp0T9/Qyqoi73gmtEorheGng9ga67k18izKVwdr2Q+5HH0VIfiY/NvU1MlxsX/1TIbyf9H3RCFjl0NsNxTiDNCuL+2M70Aw6SO6XHpXwVFbAzXTZwMOgMC5gdc3SZa+YLxxXb7hbaF9lcrtltdC5VBFtqZL1jdNm188elfPe0XuqW8qOzU3NYHmaNkZkdJkv6IG+PWvZIs/tGt6Fl27160zyz2/l+yxjWCoPLnxANucbwuJRtFwq1rqVrlXa5X8jauaJVOy1327lSvVwwKkVzYBdShUG+ls0Ny6V2ua5r7WJzoDw+nseUb3G+mM8pEzzOBSN4BlNEKYIRPqcBJxwWkUwk4M8mDuyF4xAO6HFoIEggoAuez33Pkeg6/JtDv4dtZejkb+JA7M8ZbOrCC2e5ILMJcV0A3mtdGXEoc/laR8wYBvB6gsz46wK2zwJbtn6M7dgeXu0V7a47PDcHuDKwXOlrNj5KxDPnD4bxqMQU4Qnp0SilrcsM0/muWbfi+GU1tru+qMt21w9SaEPwy1pBJLzfq6/Y4RXdP1Dfx/Us+nV9XedPvcO44PEstCqPj89H7TqvPt/mX0DBTntH1j0PZ1quAs7MoH2UWKQdv3O4Pn5QbrG/IFsBuwrJrzuja9epdUd4KVa79rxl6RGllO+dDpOlbjLfHvQ7VmFYrfbt4qBSskY9MztqWL2e3S0XWqOKodcqtmllU/lez25t2e1Y0RMJNRH+e9mKOxf9UjAplnW0s3lt+UbVLNeKhmmaAz07qnWKnUFtqJtVw+6nCoP2qVUrDFvVlqbZmlYfjEo9M9cvNnZ781hJp1RTS2mmnlm6Fmy/sf7ozvB4DgeAvVc+wyuaqSbS+pGRSb3qldiz5zv02tCl0G13lOd5SillW0at0Gn2zGGlYCaH2bph2p18ttFq55upUTFvlexGuXpWGZZKp3a9OcqWm007ae9R8YmoODLVZNLUQxU+FhVWJ7cDFFavWTNTnXr3zCrV9M5o2KgPtdGZ0S+dDYutYt7oVdv9QTuV7GU1rVds1JJJo1Uz9qD4TFBoakZP6inj40EBrwe2QfHO28/vDIpcY/gKKN57BXsBFHomo6a1tH6U1D4eFbVd+0cuZbbrxUZjYBXzdrVtDXJZq18rD/KneqXTO7PrFcPM55Kjai+nDZu1Wit3egqS9qj4TFSk1aOEmUm84Vixd8snukVXjXTaNPTkhwfrINfYFayNodEcDO2hXjwtN1udpN1qno2yzUKlNLCMmjXsa+VeV2v27c5ZpWObRt1og1n2qPhMVCTURCqdMDLp/ca+R0WkQzKdUJOZRCad1D8JFVZ32M1WUsZg0M+PCqe1oWnmisPTs1ahY1TbeqHQGIys7kgbDkapvG2YI7152ix2f2dURFfs78LindftF2BhaupROq0lkq+/xdnnit8KFXoqmcqY++Pez+SWpJrR0mY6Y3x4sDZKjZ0v9/rNfLbdrFc1rWcM88Wh1mgNO+Xe8KyUqlcHvWqykdeyzVKlPGz3K42CbWZzuVZ+D4tPhYWaMvVM+g0v4n8UFf3dKdzu9QvZ1KBn1o1Bo9bM9zqtXKmerXYaVm1kDZrFxllesxqtxjBbKwytRsfMFZK9PSg+ExQJNaFn0keJ1zP4j4IiPLp+1HH1NwZFlHO/C4p35t+XLgHGkWGomm4kE9pnXQP2B75fAxi6qaaOEmlt/4rv5/KMnkmbato8Mo30x7+S3/3tXbbb6Q6HyU65VkzZpUonX6wPqr1hWauV83a9VMie2lY3aabqydNUVusbupY77RaKe2B8MjD0tJpJpfW0/vHA2L/+/ZWBoSXUVNrQU0f7X4H8vMgIj0vf/cL/nUenl+6JGTV1lNRSxuvfFu298nlekUncyGQ+PonvY/VXRoWZ0o7Sxsdf0/av+n5dVGiqoWX0o+Rn/WRr/x3ezw8KLaOaZuZIMz8eFGU569YtoGTZIy1v22Wz1S7nmnm9Oig2GqNBrnNq5Yvtjl5tJ8uVbM4sno26+vA0VWqV//+90QmWFbG7f12ZTJpqJqkdJTJr7+XPH2X9Q1gD8S0OetnLwoevD4qPoQRKsafE91cLA/ssmI+mQsz58eHhNKzMjgvCRUCEysOSRJWy60NZ3nwYFnfFobjrf8fjcbBl8pPnBv+frW6wtBOrXdtuCU1+8l6DbwiU1jrREwn5dEeJ5kkpCz/6q3Uro4KeH9UtKzmyTktW1xrVKs1h1xwUa30tVbJayd4or2WtxiDX161edhxIuEcWreJbbMvqMSWm+HhCfOVY+VdkucPob5y7N+tWv8VsWe9puzfoZFlB92W8c+hYOfhrHMAgTtgtYegEBeRuTYIa1dSrtmz/Mg4QGitvcOtYiY0DED4OQtEwUuVrJTJiyqU49HxKWd0TNcFsVrsmpS0/v9eLKyEH0d8xhM3q6Vh5t99CEQdSRQf7/pfwv2JKgi9Xi8ABdKAvUCB4gB7C2YAhgfpE9el12PAXPH9cyhDOdG0kYWxrIGGMMtkSjfxrEz6tezGlwRp0IudcPEOMZCdYa0PeDAocUejwGJLeWDoRnaAlEN4GggMAwLIyEp1EMItwcAHRfjFfQ8J60J5s4mAbCf8MC5tQ2AzuTWCshfjJPwHJODhYoWMczJkXiC9L0xyA886hpkyQgHs0CJPrDblXjndXncaWVWVQfQpDZ0RMKRA9XJNV5dqxsp1ewfnSC+EUCwbgeIMzlV215Z2wH2oQcUfZjQTgbolXC7Fg5C0yi8ueKFhKPYeC6ysqawyjKrwoMYEdCOPh6ISaUKEigS9mM8zun3qhOaO3nktkgXG502mhbKsCvBsuFnjJL7Ksk49mVVEFCqqvCbCnAMcHI3FpuJDkQ46cM+ouHOKiyf0uESAZy8LrsMTb44hg7hEGU0MgL2ZkORTfEoavCVqrB0aM+HLDXjKEzAmTVdyBQ+KUQZ04ccOFMDJnBIgG5ECOFjxc1HJBOcoIkLZ4XGq+pseEee41QRMi7ggJYPpQ282RLUahfhQqy28IusO+TwSPIZc4JBAM+95/iIvIN2eKwWAh7YuM4ojsQq5oRdACLDKLycwTSDAccCzTHI8hWU8va8DDnRRNsA/KShqQEPqI3ELJd7iO9dEg9GmkuoWs3x0JX9cdev5lGZ4uuSU+VATzjUNZtOxDhzISD6hLDn4r9ECCXk4HTAwTAk2Egy1vPYycbrsWQxhNGL3jsEtShmhAltQaK1vb+VP+qq1d6vBDQanPD7l7w8HSFDECcJLSHAqn7W+euAf593TBAG1g0Bi6k5wRdDYDUgRgaQJD4QAmRl7ABcEuDJrhG+BicD1GHCF9CBtRSKMk3Xq98FzJQOQwb0I4mtI7aRJ35gUeF4ShJcQlHJe28STNk0PgcHMVglnqn19p+geyfHr9ZIO7u7tN5Vc94xOfXh/ieEDu4nwRxGEXmpJ4tH8chBQQFMIEOzfXjC6CFWPVWjSE2GHO1BPEEQuGfTjQMHpLJFVE6CGPoxn+mzIUbR1ospjND0L6C9hngChDsjBN6EKgaIlgwGi+FTSoS4A1KoacKXFuEPRe11/SWJTAtE8GuPbEdDFRHTpbHsQPr+nhxKeTwxkGSx9CeHkO4cut89ALoIoe+yFSSt1KvnBRbLYv8oVeodZsFdq2OnMPpDMtckUZAVhMyLUXxJAn/uDojjIxRYx4QhJCBdchZw0JhCeXSJwpBc6dULuvELSoQd33pAnkUkfSd0gLHqM//7wjyKWSsYcELmWcILYIAljE0ozg0DBJYeAPC1zsQzCt55AV0v78M0wPhM+J42Hfv5ei5diLW+x7rlTwYmvnIxAYjCBxBxRmIRELZF6HsCBKOS5x6GLuR/aZQZIOD8PAfAbwm1BpRt/DE8+HeIRRa+BTNwIDYm+GA3xNOPIAendBDM0xI27cpXfBCnz0alNVOhfeTKZEmDMaCSkPEiK9QgEhLkdf7sgfvo/W4s7jkkEFjZUcnsvNAsSNlZXtDkJaMEHYjDev7BBma0e1dc/KTnF6FY/QGJGWYEeyUETMOMtlr8O9CIEpna/Enh0FNw9+ZIY92Up8n/5rve0xpvieQwJO1ubKzrEzJSipwgsOzwXsXnnyNUrYEg9bnmaMkg2WrVKnSCg/rFVyhYZdgCHqVMx8ST8xp1zMcLA2JZA6oJDVAcGdFUW8DmjJmrZxwnh4YnXZE/Ptifm+R8wXvY0T5Js4nPvYg4t7iNyH5Vs3+Rcwtn5zO48pU8oFND88gFW6zH98hMchExXc51yP44n/EhfVOki/LMnWDtB/l6lvp7rh1XYXY0t0r1XkZfLt6nwu4d5bdVpxB/4DrT6eL++tq48I/t659mcA+3HGvDcsc0nU8/Gg+dX58b5jvN28gu804Z7d7ufxJY/YCZ9ceQ4fmAe+lN/lxJQpwS6cm1avF7OOQ+brANiipNt4vVgqdJTHx/8DtVgWyA==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Strict Send Payment Paths"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/paths/strict-send"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The strict send payment path endpoint lists the paths a payment can take based on the amount of an asset you want to send. The source asset amount stays constant, and the type and amount of an asset received varies based on offers in the order books.
-
-For this search, Horizon loads a list of assets that the recipient can receive (based on `destination_account` or `destination_assets`) and displays the possible paths from the different source assets to the destination asset. Only paths that satisfy the `source_amount` are returned.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"source_asset_type","in":"query","required":true,"description":"The type for the source asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"source_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the source asset. Required if the `source_asset_type` is not `native`.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"source_asset_code","in":"query","required":false,"description":"The code for the source asset. Required if the `source_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"source_amount","in":"query","required":true,"description":"The amount of the source asset that should be sent.","schema":{"type":"string","example":"5"}},{"name":"destination_account","in":"query","required":false,"description":"The Stellar address of the receiver. Any returned path must end with an asset that the recipient can receive. Using either `source_account` or `source_assets` as an argument is required for strict send path payments.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}},{"name":"destination_assets","in":"query","required":false,"description":"A comma-separated list of assets that the recipient can receive. Any returned path must end with an asset in this list. Each asset is formatted as `CODE:ISSUER_ACCOUNT`. For example: `USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX`. Using either `source_account` or `source_assets` as an argument is required for strict send path payments.","schema":{"type":"string","example":"CNY:GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"source_asset_type":{"type":"string"},"source_asset_code":{"type":"string"},"source_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"source_amount":{"type":"string"},"destination_asset_type":{"type":"string"},"destination_asset_code":{"type":"string"},"destination_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"destination_amount":{"type":"string"},"path":{"type":"array","items":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["asset_type"],"title":"schemas-Asset"}}}},"required":["source_asset_type","source_amount","destination_asset_type","destination_amount","path"]}}}},"title":"Path"},"examples":{"ListStrictSendPaymentPaths":{"value":{"_embedded":{"records":[{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"87.6373649","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"36.0841597","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"16.2264000","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"BTC","asset_issuer":"GBVOL67TMUQBGL4TZYNMY3ZQ5WGQYFPFD5VJRWXR72VA33VFNL225PL5"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"BB1","destination_asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN","destination_amount":"13.9424750","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"499.8384123","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"ULT","asset_issuer":"GC76RMFNNXBFDSJRBXCABWLHXDK4ITVQSMI56DC2ZJVC3YOLLPCKKULT"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"498.1069097","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"494.5886542","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"XCN","asset_issuer":"GCNY5OXYSY4FKHOPT2SPOQZAOEIGXB5LBYW3HVU3OWSTQITS65M5RCNY"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"490.0780598","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"CNY","destination_asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX","destination_amount":"280.2909824","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"63.1883029","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"63.1472796","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"62.9386895","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"NGNT","asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"6.7649849","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"WSD","asset_issuer":"GDSVWEA7XV6M5XNLODVTPCGMAJTNBLZBXOFNQD3BNPNYALEYBNT6CE2V"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"EURT","destination_asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","destination_amount":"0.0498106","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"CNY","asset_issuer":"GAREELUB43IRHWEASCFBLKHURCGMHE5IF6XSE7EXDLACYHGRHM43RFOX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"25155.3452034","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"25146.7108397","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"24986.8616583","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"BTC","asset_issuer":"GAUTUYY2THLF7SGITDFMXJVYH3LHDSMGEAKSBU267M2K7A3W543CKUEF"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"24948.9784843","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"XCN","asset_issuer":"GCNY5OXYSY4FKHOPT2SPOQZAOEIGXB5LBYW3HVU3OWSTQITS65M5RCNY"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"NGNT","destination_asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD","destination_amount":"24930.7854717","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"69.7123752","path":[{"asset_type":"native"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"68.9785993","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"68.6731854","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"NGNT","asset_issuer":"GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"63.5394120","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"credit_alphanum4","destination_asset_code":"USD","destination_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","destination_amount":"39.6691360","path":[{"asset_type":"native"},{"asset_type":"credit_alphanum4","asset_code":"HEX","asset_issuer":"GCGBSZ3DSSH6PRHCOD4JXFNNZXCTKBDFRT4JR2HIAC6FQZU4YK7GPHEX"}]},{"source_asset_type":"credit_alphanum4","source_asset_code":"BRL","source_asset_issuer":"GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP","source_amount":"400.0000000","destination_asset_type":"native","destination_amount":"1226.9231099","path":[]}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-trade-aggregations.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-trade-aggregations.api.mdx
deleted file mode 100644
index a827117c70..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/list-trade-aggregations.api.mdx
+++ /dev/null
@@ -1,78 +0,0 @@
----
-id: list-trade-aggregations
-title: "List Trade Aggregations"
-description: "This endpoint displays trade data based on filters set in the arguments."
-sidebar_label: "List Trade Aggregations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWv1yGzcOfxUM/0jlzlqW/G11PHdu7Thp09iNnN4lsceidiEtay65R3Kt6Dye6Wv09e5JbkDuSqsPO07i5q7Xyz+OlgQI/AiABIgb5vjQss47dmZ4gnAwHBoccie0suwiYgna2IicfrMOO0uFBVRJroVykAibSz624Dxpwh2HPreYgFYwENKhsWDRgVDgUgRuhkWGytnmuTpXnpewkGiF0B9DIq5FItQQOAzFNSpwIkMwXA0RhHIaLA49NXCVAK/kVEOwjjthnYhtBANtJgy4pcVzLgw0SK4IYl0oh2YF9DUaQB6noAckm8UJ+1I4hKQwHodyynR9YcHmGIuBwARGwqV+uGfQalkQRQ9ybniGDk0TiJV13DgvN6qk4lfTjxssZe6Poednn4kMe56khyoJvwzSuk5coxxHMEpFnHrSvnYpGF2oBBNw2nNXyA1aB1khncgl0qozIlqhYgTMdZxOVBbK70LBZQ1tg8Cl1cClGKpK44qtvZcvPB/AWBcw4sqRYHHq1XW09Z4dLRHNohtzBX2Enh4MLLoeIRLQHtNe09QwUsP4XLGI6RzDfj1PWIe9ENZ5i54x6IhNiMjmb5jiGbIO84hf0oawiAmy9H8UaMYsYgb/UQiDCesMuLS46BAIUo/QhN3s0x5wMwaDuUGLymEC3EImpBQWY60SOwMQi5iNU8w469wwN85JGKEcDtGwiA20ybhjHSa1GrLb22giMKrkU8Ut8vyLizu1j08QuLSMqT/eI20TukWea0ND11wWGOy3DZlQhUNobLdardZKBFvlFwuNjVb5rV37uDf5CKkuDDQ2tqdfEj6Gxu72ZvjinbQNI8Qr4r+5Gz5/FFgR0wpPBt4mY62sYx2/3jwelSKMwC0nBvnnZ050qU/dWzq1vXRuqfCiBIRHfWIFxOLMhI/rEyfYLM4k8NjtRd1mgpd/pL1056JIGSoKG2KHsPXIfPSe7IjOK6HmrOg7rkArOSYehZ8RYvbUkOkUGBrkjpwp5ao0lCb8TGYHWWEdEQsFo1RL9IM2AonWhvnELjf6WlDQnvKNvDlNp61vBtKl5qSKrP8B16OD79KfhJee6E48nSmWuh9R+WOVBCZu4VxtwpFwKRroKU4nUi+CXmwwEe6Syzzlqsg2exFos/C5vd5bqox1RnhXQFVkdCMJjFnE5vkufmqvs4s7tBbWFh6jj407XYdScgM8SchMqmN7CsG/fv2NLgPEvgmvSoaVpfTmgO+RwSjtJnh9AIP3PMslfTo+fP3Dj8evjw/f/vTD9ptnbw623m4fvFk/3vz7YfftafftRvdvW69fbhy8+vnHk+2fuq8O/3a69ebF0d/vsoJYJ59ybBDZUjP43RR/3T2c0aG8vD2eMZcM/wj2PKv7Y5v0DBD3W/XiJvxnDXtWnsew7Tmr+D0RmLdwbZKP3tYDSNCKoZpJVTyjcPZQjmAw1oaucqkuZAI8z5GbJpx4HhaEimWRIPS4jXvQ4DZGRZnYird2Wq4HDfpTfvbX+nCHLzM6EFb969ffHGV7EQgHCQ54IZ2lS79n+zAP4TZmQcFZ85ciEx97FaCNzfh7kRUZhHOS0KmgMOgKozAJ+Znn7+8MIR8bGJ1Bm4Rfb7VgFbgqr81hoks5qQwpNwnZjr9APNNG/JMSX20gR+NPZLo5G+RWK3sPaNUGYrKAXbv1gWvkxJjardvbCwLF5lpZtDR7vdWiP3NXpCKO0VIuFGvlUDmawvNcitjb0NovlubdLK6q+79gTNuQG0q2nAirXGLWxyShjfjQ1BL92kRuDKfNFA4z+2EGlLZYx7N80YpuI+brEJfeQZeO+5PpWsuCjGrJeOXa90zh18Ol31MxTO8cuDQf1kwtpU6WfCVFhfMBxCt8akRMCQGTerSUidSjLySBznE5Fxr4QjLEUts7tpdGvogU4d90bL4SQexKz/ULLq9WdG6Yz2G9k0mhrvwni3JAf1ODA9ZhqXO57aytpSH8rDq0TqFr2nDUN7UZrgW/4DXef5m7pO2Hk+vJ4nG6f/T61dmTZfeP/eOD060XR2cnP2+/eX60vf7m4Met7e7Z4cHL01eHJztvnx5+e9x9+ez7n56/OT7+ofvjyduDZycn3fXuk8UjdH/+SvRkmhHtl5nok2mVZr+9tbve3toO6eSTqhoSPu/s+ny0TSArfO/+BGAtB+AhGO601/0AgZUbvK6B5a17JrhPwve7mUjsGZVFgNZcFN6Yi7psY2+vubG7s0Fn02LEZetbza2N7d3W7jorgy1rNVvbG3ubfn4Is/7T1np7e4/VA+xL1glfI3ZIB2L4VwXGwGd3Y2OX1ULiS9bZbbd2trZagWh9p9VubextTILZzFrTMHbnWmX4mVmtFnjuXI9uOwuY7mwvw7Q9j2l7c6+5u9ne2lhfiulec6e9ubfb2pyBdHN3Y2sO0vqnibhb1b4ess7OTru9u9vamMG0oqpjegdRDdKKagbSO8jqmFZ0s5guJaR6UhWJ36+Sf3arkPvuhkmuCIpuilLSHUsXJvYZRWEkzAWKDwWI8/NzdUeQoKG7AsXi2OcGi0WOywMGzVsSHejznVGWBpcGmta58mW+EtHv+TXv+gsnGQXvo2Qd9tcSwbXy76pNruqoX3NTZafd5Ar2obzdN86Xkp6zlW/OFRFZNPSWsw8KRzUOzfI63uz68ca5Ajh/SPw/Z9G5IuaBva90LDA/8Llh2OFGJUmVOC6fXUpA++6XoB+fus0TGT0A1WsR7MPMhpXj5etRNVrtWTlaK2juQ2kG5VBZO92HlkcjAE2CN93cVWX2dS2aihRVq0czFc7AecXzirmUjfBfl6JqDAoVe3EalMqswA0NAVAJWUtsSj0MA9/Q99uKh4vTGiUas0CIxmjjR0rKb8hqLyKWoUs1PRkNfbU5547C4RIvJ3P1GIT4URj5sBsFW5aZnoV58BLdSJsr7z/LOQ4KVxh8CM+n1UxQFdcLypkHOqRO4S5aOgaLGKkSqFvNVrNN+hVZxs14OquqUNOjKzw7OzuFg9PnlJj6x97yXbeqKpWrNuE5PfkO0ZZvtQZXPXDWz/aUudFJEWNCr3tLWBBnTpl0Nsm1kVtBpXbtd7TIsCLl12g4vaFOU1gwKL1vVo+htXx8VRsRno68IJO3pLDHodjfH08E+k4bpBqBsF7zmh59I5IhQh/dCOmxOc+DtrOUp0ZTimFBiiuEEZcSnY0gwRiVM1yKf2IC+D48jNpQ/A/v1uEo8BJNagv0Cl70fQnCcGW5t3cbgS+J0Bbx2Dsh9LkkZX290jqDPAO89g8jXo46NTGdUjYXLOvPbgnv6ht60ajcM8FrlJQ02pnLQSn2WqwNriqd4MqfynrooKiWK5/guC830Xus4BC/fvUiAg59o0eWjgptgPo/yrrlBOvu4Q/2g1gnOrZrTmtp12xyZQlpDQbJnMpKLt323gs3Jv5jesbNA6ARjNCXArOMGjKoRYGA4ooWBqGsQ+77NDJ+RS+HiTAYO7+HdF7VGliGhaDWF+8xfbSQ6pGHJMmEEtbXkUsT9+ZYYUNL+Opgw+AgGLPX/3Ci6VfwrdTDKQaj0WhW+cnM1b7UwzW+qnC0agu1SqdQiqvl+bHiC5JWk5vw+Gro20SoQWfOG4LtmDgVDmNXGC5BZOTzGB5UdVm9zPgv2kB5dEC/yPKVJjzVVG0Oj5D0mfd1QYVMLyIBWK43MQ2dYHlnSDG+Appd19+XR48J2ikAQ+HSot+MdVZdBNeGeq0vdX8t44T0GrmXiNFWR+calUmN4jJYyvHr54dHl09PXl0eHv189OLk9OhVt5klK34zv8WBNkhm0cehUFSI/crCSBvqrEHhfG9J2X9CQUJ4ETFOdaj+eunJaeGlTj4lTECiY18W9gh24OuvRwiJ9u8KqBJtLIIplCIhKhhpQ0OQ4nTnUgmX5Ez1GDKxtK+/DuHBtxAJLuXYs/a0l9dcisQreLlw8lFvFPVQuBG1YNHzuSPXUjEaVYacBGNd5LLEJ6MgLTLqwqC2HzK/0KCEUvC+kOSPRFUzvuaMY5DvZVzxIVoQZHojFdG7PSariR6pifHpwayqOnci8yGR1iwpKeRRQNQDUIiJhcYIv5ISan5HNXkLHM7Zdzz3hwWxO2cT7FZCh5FDk9mTQTeYWe2qNpMd0qRVPVgtrbGss/PY16HK94xK7Lq5P/XNOGWPzOxVcPbihxkXfhSl1H+tj1FaLmJUof5ZrnWQ8zhFWG9S1iwSst2BQDMZWQ0j0xXLYMP9qNepZGrXXjz/7uhl94hImqnLpC8R5dq6jKvaklTOhCX9hHNXi5vpC8T/Owv/31n4X9tZWNb8Hb53a7nkwpfvvb/clOniO7YkXbyIWKqp7+kdu7khK3lt5O0tfQ4vmJREJsLyvrzrDXPWQT6703CpHlc4nm+ALB8dmE9KP07Cz2wuvEfCWsfjZ8j3B+4lvAebmfbKT0Tnf7tz7h7wJn2Gnwhco+oQWYHfs13uHg0WW/w+w0O+QNfbw1SZNDl9hjKP27T2MLnLHqTfwZoet1/tHm2Wdto9vk09ftvZg3V6dON6pK6xByvweVb2B2oauy9yl+1yn7GH/yMNYveAVLXOTUG6oB9GEEqs8+6CepSQE5J0IQ1EB3GMeZ1qoT9s5uXk+OiM3d7+G9f9x7M=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List Trade Aggregations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/trade_aggregations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint displays trade data based on filters set in the arguments.
-
-This is done by dividing a given time range into segments and aggregating statistics, for a given asset pair (base, counter) over each of these segments.
-
-The duration of the segments is specified with the `resolution` parameter. The start and end of the time range are given by `startTime` and `endTime` respectively, which are both rounded to the nearest multiple of `resolution` since epoch.
-
-The individual segments are also aligned with multiples of `resolution` since epoch. If you want to change this alignment, the segments can be `offset` by specifying the offset parameter.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"start_time","in":"query","required":false,"description":"The lower time boundary represented as milliseconds since epoch.","schema":{"type":"integer","format":"long"}},{"name":"end_time","in":"query","required":false,"description":"The upper time boundary represented as milliseconds since epoch.","schema":{"type":"integer","format":"long"}},{"name":"resolution","in":"query","required":false,"description":"The segment duration represented as milliseconds. Supported values are 1 minute (60000), 5 minutes (300000), 15 minutes (900000), 1 hour (3600000), 1 day (86400000) and 1 week (604800000).","schema":{"type":"integer","format":"long","oneOf":[{"const":60000,"description":"1 minute"},{"const":300000,"description":"5 minutes"},{"const":900000,"description":"15 minutes"},{"const":3600000,"description":"1 hour"},{"const":86400000,"description":"1 day"},{"const":604800000,"description":"1 week"}]}},{"name":"offset","in":"query","required":false,"description":"Segments can be offset using this parameter. Expressed in milliseconds. Can only be used if the resolution is greater than 1 hour. Value must be in whole hours, less than the provided resolution, and less than 24 hours.","schema":{"type":"number","format":"long"}},{"name":"base_asset_type","in":"query","required":true,"description":"The type for the base asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"base_asset_issuer","in":"query","required":false,"description":"The Stellar address of the base asset’s issuer. Required if the `base_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"base_asset_code","in":"query","required":false,"description":"The code for the base asset. Required if the `base_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"counter_asset_type","in":"query","required":true,"description":"The type for the counter asset. Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"counter_asset_issuer","in":"query","required":false,"description":"The Stellar address of the counter asset’s issuer. Required if the `counter_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"counter_asset_code","in":"query","required":false,"description":"The code for the counter asset. Required if the `counter_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"timestamp":{"type":"string"},"trade_count":{"type":"string"},"base_volume":{"type":"string"},"counter_volume":{"type":"string"},"avg":{"type":"string"},"high":{"type":"string"},"high_r":{"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"},"low":{"type":"string"},"low_r":{"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"},"open":{"type":"string"},"open_r":{"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"},"close":{"type":"string"},"close_r":{"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"TradeAggregation"},"examples":{"ListTradeAggregations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/trade_aggregations?base_asset_type=native&counter_asset_code=EURT&counter_asset_issuer=GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S&counter_asset_type=credit_alphanum4&resolution=3600000&start_time=1582156800000&end_time=1582178400001"},"next":{"href":"https://horizon-testnet.stellar.org/trade_aggregations?base_asset_type=native&counter_asset_code=EURT&counter_asset_issuer=GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S&counter_asset_type=credit_alphanum4&end_time=1582178400001&resolution=3600000&start_time=1582171200000"},"prev":{"href":""}},"_embedded":{"records":[{"timestamp":1582164000000,"trade_count":3,"base_volume":"399.3873200","counter_volume":"25.5368082","avg":"0.0639400","high":"0.0652169","high_r":{"N":652169,"D":10000000},"low":"0.0638338","low_r":{"N":8107550,"D":127010393},"open":"0.0652169","open_r":{"N":652169,"D":10000000},"close":"0.0638338","close_r":{"N":8107550,"D":127010393}},{"timestamp":1582167600000,"trade_count":1,"base_volume":"149.8415320","counter_volume":"9.7149804","avg":"0.0648350","high":"0.0648350","high_r":{"N":5000000,"D":77118803},"low":"0.0648350","low_r":{"N":5000000,"D":77118803},"open":"0.0648350","open_r":{"N":5000000,"D":77118803},"close":"0.0648350","close_r":{"N":5000000,"D":77118803}}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/lp-retrieve-related-operations.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/lp-retrieve-related-operations.api.mdx
deleted file mode 100644
index bb0cdd60aa..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/lp-retrieve-related-operations.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: lp-retrieve-related-operations
-title: "Retrieve Related Operations"
-description: "This endpoint represents successful operations referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time."
-sidebar_label: "Retrieve Related Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWv1y2zYSfxUM/2iTjj5I6lsznTs7VmwnbuxaTnpJ6lFAYCkhJgEGAK24Hs3ca9zr3ZPcLEhKlK2kSdvc5a7nfzySFovd335gsYtbz9K58cavvRPxLhdc2BtyplRivMuGx8EwLTIrlPTG3sVCGAKSZ0pISzRkGgxIa4jJGQNj4jwhKgNNkd4QDTFokEzIOaFkLq5BkmS9R6ZUQqjkhFFJIiC5AU6EJMZqoCmuSRWHFplufSY0SdTSkBuVE6tIIowFSWKliYTlhza3KPfdnQ2xC7ghVAOhnANHdnYBZGohSagmCfA56BY5jgmjSbJLuAY5Ulr8oiRZiiQhxlJtCbWODVCdCDCWXEm1lBvJSC4TMIZQwnJtlCbCEAO2gdyXC8EWhFEDRNg6z1irlNgFteWiFtm/wVW20A4qXtc0yQEVkWrZcBghuIXQdXCYBmqBEyMkA6TTRMO7HMW1IoWW1/DW1MfcG3snZ+dgtYBrOIcEl56umXkNL6OapmBBoxvdepKm4I29NeAzBHwmuNfwBLpRRu3Ca3i4o9DAvbHVOdz1tT2SS/EuByI4SCtiAdqZeYctW96qsd61QKLa6l0O+mZrr5gmZsdmMk8j0AXGzr0NwkiJyYCJWDCSKFbYT0i0nUoSYO6ziokGkylpwDh/FoZkuXOY0mxAMjoXcj6z6gpkaSQVE0o0MKU5wm3YAlLqjW89e5OhHkJamAMqAu9pmiXgjft9v98PBt3BcNQbBX5vVVNbaQ6frzUHI+aSVnqgqI7RxhkLCQ0xC5UnnNAsA6pb5DQrHElIluQcyBtq2BvygBoGkgs5f0iUJm9wuzfkAf4rv3bh5ExI9TxPQVoijPzn3/9hyyCwhENM86TA37HdCY+xWsg5oiPzFJMXNcwrFPQu68AkIhX2M4G5WABJ6XuR5mnlGM7KBRQabK4l8BZBOsffhZmmcg6FzQMUPvR90iRUkjzLQJeEzsGEIQuqOVO8yCpVFkH/zkDHSqcUA1MDNUqaj4BWGRD4PewC/1P9KvDrgJUmncVUJMA/E7kpWJdHdZGGKvcoeNUzkJAYNSjrfWdyqzGS3BY7tYiUSoDKjf1dCnH0W9Z/q4T8rSpQaSgrJKupgjGy9VuZtMuMCpQt1qG0pS5+UyWKlre6bHjvmybPMqWtaa7PlSoZrlMKKh36Pv67I2dx5noNjylpQVokoVmWiCJRtd8apLutgUeT5DR2KbqEUUVvgWF0ZBqFtaLYb5YIeWVqcH+AzkAS/zrVQkO8K3Kdm1sXovLKWzU8C2nmDpcdhl6t6oZ7XTC9bHhW2ARqPCS8t1+ZSJmG669KpBWSVV+dOFNjyPwxPgFxDMx+AuG/2wYMOHxtYn2FAeRKef61AVXLuF+VZEgl+K7NKjrBnf/VCsCPUW/RoYQ3GcxEbUVRjtRPb78k21kcVURecT7NKGMql9arZ4B1Ke+tLlfrNQ7Jj5X941vPVbLbyaHy6MIG3sLazIzb7UVR4TQtGCvBtkxxyWopPW9v3xNMuz8I+z7rsmDoD6KwH8bxsBdEPu3EEHSDYNQddfpR5IdBLwrjwaDbHcQBj4NgNBoCjaJRe3Pu/qW4DXz/jSu+vu9846rb77FWrJ0VX5esQegHo7DbC4N+r9fz/WGwW/rqWPkape90u4NR0Ol2Ar93R3pXoaP7zSCNAC/eqERZW7vaBOPJ6/RHg+4gHIV+Pwz83sC7G0O7KGpZYrZpSVQllVG5ZpsQGHuH+/vdJ9OLTvj8p6enJ4cvX04fTV7uH+0/On18El4c7h8dvDj94dVZtx9OLrqvzg+6z0/2BtPwxKsC7u4Vdynsgmu69DaBG3YaZezxmcs9oR8GzSBoBsMLvzPuDsbdwas7oi+oWXhjr9sB3mMQjIKRPwxDYP7Qj/oD1mEsolGnT3v9iHW6gR9GAQ0D3gHoj3zgnYiFnc5g6DV2XMHH3u81uqugDehrMLMUC+vXtx41BlC5yfPzi/Hh3lnvZHJx+qL/8njSD1/u/dDrTy8O9p6dnR+cDl49Ptg/nD47evLj8cvDw6fTH05f7R2dnk7DqdfwHD8v8H2/5bu/nqtMKvZnR2e/n3tni/tlwzMLqjHduTK7phyWDOLaZf8/TkOals43GnW+hI5r/mF3MKypiVs48we9Qb8zGgSDUX/UCfv+MLgfWjtpPj+4fjoeXExe/Lh/Nnn+t6cvnx0edw73944Gk6PHk/PJ6bOnTzvPn/b6r6YnT44Pjl8e/fjk0Yvp4Sa42AIv1DOrc2NrEdXfFVD+sOl3L0J/7AfjsPuBgBp1gziMaRj4AQ/Cfq8/6tMOG/BODwb94ZDxMPA7YTcIujDqR/0u7Qz7NOr14n4PusNhjPCilWa7o7/0oy8WdUUnowgPp2BurNK/B+rV5ar8w2PfgjTFyf761ruCG2+8+4baqM59tDwGUAp2oVDJObhiDNt7Y+/eaXN7D5dV7QDBWz7GXdlDzHXyaYeat6t5c1HQkWdgl0pfuQDbzTHOba7hU3g+riiJrLheYmchVq7yKoupspWDIIE2xWq/5bcwgkyeplTfbKhIptW14K5vSI4uLs7I3tkxNhs4tbTqGVT96HLXFjm2RMg5GFu0GzU0i4TlqN3KTCueM+AkutnFomhhYjW8bkcBNdhgtYowJU2eQrWUXoOmcyC1xgLRWAuKa6g65rWWVVNpARIbIU6Q9YigbIO4Hn90sxbokdKAbTRhnOY1PSIt+BxIBHYJIHH7QtvtlWda4Q0AG8JXQJbYpremQTgwkFbTRPyCLZn3RSYxDcfBhTARxuSgnUTr9ptVxOSR69LVGjwN4hpHaKIyu5GIJqhsA5ucZXMdrt0gxMlxt3W0Wdm651l/dk94XTfo5YMqPDlcQ4LJwWwVsKXYbaY0NKXi8PBP5T0/y59ltV05NaPuIAZOrgUl7Pn5SYNQEmm1NKDdDkpC1Y9cYz09eGp+FWuumGlbl7kNvzKItCIa0J2KkZPCa+J7HMKouJghZQWgDbIE1y1PU5DcjaEQKCpxYyKksUA5LkrpFQ6wuNDArLMhTtqM09OZdZ4LDqSImAgMWailg4SnQuLkT5PKxZ07VtjgFq6B/sBNASvvfH2w1vRbsp+o+QaD5XK5rfyashklat6mTQnLpsllE0+hBTTL8+Oh69kbhWFC2dVcq1xyouTdaCh8R7OFsMBsrmlCRIoxD6mzvCob/Cl9i2O84uggUZ5mD1vkMU4JZdG9wK9ppHLs9TsREcByv7VrKA4RNdAgbAHsiiB1XX83QThEaDcAzIVd5FGLqbRd4tCeq3aUqKidUkS6jeElGJjq6GzjJEFLmhSecvj8+GAye3x6PjuYvJicnJ5NzqetlD90xtyHWGlAt4hgLiTOKr41ZKm0xQmTsK4IKEeZmCSEExHYQhUDEic9Bi15pvhvSROEK+YmJw7BMfnuuyUQjnNSiwNtpQ0QnUuJQlQwokGLJEVxDCs5TTCY6jlk7WnffVekB3DzQpokN461Wzu7pongTsHZvZMPMDA0ELtUxAAOUi2GlmSgZZlyODCVZ0mJT4pJWqRYlFFpnftFysGYCBqJBOMRV9Wcr7UVGBh7KZV0DoYIdL2lbJCMauBNjpPqyvlUvK2qyqxIXUrEPcuVmPIwIaqYSABuyIMlfJskpBZ3OLbCcffP3iOaucMC2f3srbFDF8F6FnRqTuNp4Wa1Uq1uWUfUVHGz9MZy+kGZa+SUQ59K7Lq7P8bALLpcjTul4HbhBykV7ldIEvXX+m8rLMEZSAO1vfYyyhZAwhaW5JtR9fqXZvHLZscy2VD3a9mVcUxN++T40eTZdIJLWgubJq5NkiljUyprW1YtOVL25MjWLH6rvLjdzIb+/3jjT/R4o7ygWnhv21lCheslOx+8La9nr+/cUtF1xrtebNRuaJcNb6GMxcW3t3jAPNfJaoVfF6NVvLdxYWiUfGi4WvfH//ybi50oFRff9SuS8qrruSvk5yj3X/O04iMoVI9KfiMI/0PPKD4CUvXA5DeC9IVeTHxE4HsPPLYl/1VBv+i7iI9KXr7m2Mh7iR+0QKg/M/s8OC9new/JZ700+4B85ZdU3tTl27jI3bzqJm0LoBhfm3bbHmOQ1X3p3nOOrXbb4eTCW63+BcJVaQo=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful operations referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new operations referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known operation unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream operations created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"}]},"examples":{"LPRetrieveRelatedOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/operations?cursor=&limit=3&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/operations?cursor=120192452165550081&limit=3&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/operations?cursor=120192344791343105&limit=3&order=desc"}},"_embedded":{"records":[{"id":"3697472920621057","paging_token":"3697472920621057","transaction_successful":true,"source_account":"GBB4JST32UWKOLGYYSCEYBHBCOFL2TGBHDVOMZP462ET4ZRD4ULA7S2L","type":"liquidity_pool_withdraw","type_i":23,"created_at":"2021-11-18T03:47:47Z","transaction_hash":"43ed5ce19190822ec080b67c3ccbab36a56bc34102b1a21d3ee690ed3bc23378","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","reserves_min":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","min":"1000.0000005"},{"asset":"PHP:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","min":"3000.0000005"}],"shares":"200","reserves_received":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"993.0000005"},{"asset":"PHP:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2478.0000005"}]},{"id":"157639717969326081","paging_token":"157639717969326081","transaction_successful":true,"source_account":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG","type":"change_trust","type_i":6,"created_at":"2021-08-04T20:01:24Z","transaction_hash":"941f2fa2101d1265696a3c7d35e7688cd210324114e96b64a386ab55f65e488f","asset_type":"liquidity_pool_shares","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","limit":"1000","trustor":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/lp-retrieve-related-transactions.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/lp-retrieve-related-transactions.api.mdx
deleted file mode 100644
index 364353efec..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/lp-retrieve-related-transactions.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: lp-retrieve-related-transactions
-title: "Retrieve Related Transactions"
-description: "This endpoint represents successful transactions referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time."
-sidebar_label: "Retrieve Related Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ty2ziyfhUUf8wkM7rf5arUHjm+x3F8T+KMSwOCTQkRCTAAaFlxqWpf47zeeZJTDVISKcmOnczueHZWP3KRAHT3h+4GuvnxzjF0oJ2NT84h/xJzj5sJOZYy0M51wfFAM8Ujw6VwNpzzIdcEhBdJLgxRECnQIIwmOmYMtPbjgBhFhaYMZ2iiwAcFgnExIJQM+A0IEsylRFIGhAqPMCqICyTW4BEuiDYKaIhzQulBiZzl/k9oEMixJhMZEyNJwLUBQXypiIDx/eIN6r4sWxMzhAmhCgj1PPBwQTMEcmYgCKgiAXgDUCWy7xNGg2CdegWyJxX/KgUZ8yAg2lBlCDV2GaAq4KANGQk5FlndSCwC0JpQwmKlpSJcEw2mgOuPh5wNCaMaCDfZVX0lQ2KG1KSTSmRzgrNMYh/M1rqhQQxoipDjgsUJAU7UzgPEFFADHtFcMMCRiij4EqPKhodQcgqOjEBRHL3vORvO4fEpGMXhBk4hwKnnmeWcghNRRUMwoNCh7hxBQ3A2nDnsfYS9zz2n4HB0qIiaoVNwUCZX4DkbRsWw7HU9Egv+JQbCPRCG+xyU3e41O1pypoW51ASNmagvMahJTpZPA71GmIhDF1SCs3V0jVBSoiNg3OeMBJJZQHCvKGEyCCDZU+kTBTqSQoO2fs01iWLrNunWAYnogItB38gRiHSjpE8oUcCk8hBwzYYQUmfjzjGTCO3gwsAA0BC4pWEUgLPRalVarWq70e50m91qpTnNmC2VB0+32gPNB4LO7EBV7UILh0w01EQPZRx4hEYRUFUi76LElbhgQewB+Z1q9jt5QTUD4XExeEmkIr+juN/JC/wr/doGld1CqgZxCMIQrsX//fN/TRoIhnjg0zhI8LfLroVHG8XFANERcYhpjGrmJAY611lgAh5y80RgzodAQnrLwzicOYbd5QQKBSZWArwSwXF2fRtqiooBJHteReVrlQopEipIHEWg0oHWwbgmQ6o8Jr0kt8xyCfp3BMqXKqQYmgqolkI/ANpsA8Fbwa5aeaxfVStZwNIt7fuUB+A9EbkzMDabqiQVzdwjWYvMswo6DkYN6rrqTHY2RpIVsdYKV8oAqFjsv00hdvz1dHpdcG6LOo4iqYwuzjP3LNHMwxUXrFUq+NeSGcnJ5hQcJoUBYXAIjaKAJ0mg/FnjuLuMYjQI3vk2/aUqSvczMPS8SKHdhify+gEXI50x5Z5xGgL/26OGCvx1UWFdyFj3FyNnWnAMhJFN3WtAnE6z+/opWfS64BhuAsisIeDWPDOVIgU3z0qlKQ6bfXVotxpj6xs+AaELeBP5tilpEsoMpEpRjExuIHyEX4UQylUspoW/smNSxmQsnptvJtfIZ6bUIgU/M8XA94GZ56ZVpICBB89NLVt5gffc1MpUGc9Ks6VBNoMtssY8UnPRsfDIjBdkkM9bez0tONxbZ85ME+5Zf8oUAmuz8KKmXmdtwRlSPVw7cSXbLC56c0S5MPUaDk4rwD4165WQsWLQX02rc6siagwovCrtfuoVryrF7vVdsznN2Es9T+EVapGe+2F8C2swWh7RXwfkilZ9jSWrYLB2rA9/nPqZte4z4UdXvM9kHMiGVA3uwS2kt30f1kMw9+X+MgwPeQaIGwhkBP1bT61dNrm1f+vnEAy9dwxa9eAAvKP0k2/X+YGteGIFj7kFfXODMte1zMJp6pfC4488LLFz4spYPCYph1z0cfy9e3rPjxldMx2Y46yi5ws15knhKWqtpJG8Yvf+/AjVDrPK4HpcPC6Y1w3s08ETBidq9wc0ejgM4kUc3BpF++gRtqv1WD+bPgaIWQy4cRj1n3Zmrs3+C4n2939XiGS+3gHYjMMoYzBO4kKA+gsb+FB+zUzZRzNzpi/dN2znM3fy58759FDPXEMyx/PKYXz/OZg/9fKHx8KU1YNhKennUvxqQs9m59w+XE+n93m/M72ezvtNdmce7ihv3Dm2SZrvl8wKz+Ti6AyNifRGuTxMmmdFA9oIMCWddPFLUg3K+Ra0LtfdRrtFfb9DG5UWbQGru62q12SVeqdS6TLwO02/5nk+9VvVVqdW81jDB9atdRrNaqPrNsrZPvo/klbzq59sZ+9V7SfbOn2FjchMs+S5aVutVardWr1dabaqtVqlVems13/WWXmm+jca7W613qhXK40l/W0LGB0x11WZ900+/aBLZXUq13y/0YaqS31odVr1bq3dcmu04/kV2q43u22ACqu0ar7LWLvmVWtV6terDR/anWaVdSudpebFE9RIZ+nybm/v5Kj18ejjVuvqvH1+2LvcbpzWW2/Prt6fHFzVah826++3GqeHZ3sXp28/7L1vXO4d7G/ttPM1w1N22U7S5U632e50VnsKfxaW5VzxlikasembbzD8aSouSspV/bKthu9U8B/zCP4pjZZ6p9GudyrVVqPaqjbrreXmwY8JwlB7SNLS0f/nRVlanTs/vNJyBe+smJ0v4ZMHDsmt5o+QPovYJPjyhbxTq9SqxUqnWOme1yobzfpGtXq1eoHYcL47ZTxQgydAtKvNdqNWbbSanaXryA9JzZXBTrVSqVQyN5rkm+qam81GdbmgdXr4Gdg/jzdv9NH4uHZVDvXOGft88/Xgymy+82i85w07PD5tnV6xbnz5Luj1ege3270tqr9k5i8+J/jHtv3n1thtb7Gtbug31eaF2G93Ju/dk3PxXg3rH/19NYLR+w/HbnAe2Um7dtLl0c7JOFkqbH3YoZfa77w7i8+6r7uDt1EwOf9MB9vdzz0hvoxvz7YOWj4Xrf2epm86h/oiq8nmTN/e9usP4amWH8JTfvD5Qhl3tHX18VR8paypq68vLxuD2mmwP9jcj0/MpFYV0dd6r3o5vGBnYe/2191QT3ZvL3du9hXztDmn44MgnHRHO/nrYYqnxWcZj97CvuTzas1tMrsh+xa/Xq+mDjOznghob9ccHG31ekdfJtIC0lv72V7/tR3/h8p//XT5vV7POsNbdDid+e1JDtvr9WhlVHmL9rxZ4Lv6OVn/Ner4L5C/uh/3yu8t5J98j/yd89OLt8lCB3Fw+z5w98pbIzW6Obn5uPXmio0aNbl5/HF80GzptxeDCYhG9CvPys8H2MqevXKWe1kZb7a7p34IPXHCFujd4zH/tt17ivxXr3Jl4oYjpFiqFjc+OUFz5L7ZaY4+8o/VN+33zV7t/fZVpybeuUcnwSXsH42uzvZ7Z4ejQ2bMVYt1x0eXHy/3tqPBW38YqbdDfXnqTt7U99zDi5p+fXWlb642T169cq6nSS1qy1G4NSB0cjn9dOeMYOJsrGcHFGZFp72QXaMFZijxxBmASboHeIqvlDl3K0Snae7+goaDupmxo2IVPO4S5KyjpZwn48gRmLFUI/twef2KfoxIP2bNndlIImarXmP3xk8eFKf1fEpSQZhA6WR2pVQpVe2VJwypmixGkUjJG+5ZRhTZOz8/Jr3jfWSEeNRQJH9k+Xap1BLZN4SLAWiTEKkUFC1wlq+XzIyU9GIGHnEn65ZIyFnYzpsTbYBqpI4ZSZgUOg5hNpXegKIDIBlaB1HYjOA3MGMEZsg4Rak4CKTNWUXmNMiUz2JZjO5krtBrqQAJQlxbyzN2uIp7AyAumDGAQPGJtfmZx0pigwypbiMgY6QhGl0gHjAQRtGAfwWPwC0bIulIF+wKVGtAm3UMymo0JxYZSXTsWv5RxjELxLJ6cIvSaxpxaYDGFpC+lVIH4caSPa0eORoh8uPmM0srnvV394RP2Q29fjELTw+S+6jSuYInVbvMpIKikB68/Ft5z2/iNzETl/KCqa2iwCM3nBJ2cXpYIJS4So41KCtBCpiRFudYn2290d/E2pNMl43N3dobaURaEgXoTgmhVmKf8hbppdJP+LFRAmiBjMHyAMMQhGdJtggUFSiYcKENUA8nhXSE9FyPK2DG7iEyibW1027rIOYekCRiXNBkKMcWEi/kArnNisxc3LrjDBsUYamBLyzLeeadn7bmlv5MNgM5WGAwHo/zxs9HFt1ADsq0KGBc1LEo4ik0hGJ6fry0bEQtMUwoGw0UPrchUixHQ+I7ig25AWZiRQPCQ4x5CO3Oy5S6GNLPSFJOjg6Cjz5elsgOcqBF8vgFv6aujJHFaFVEAFN5c9eQHrhUQ4GwIbARwdFZ+y03chehXQAw4GYYuyUmw3KKQ3kgy24g3XJIEekyhhdnoGdHZxmfDClBg8RTdi/2t7b7O+9O+1vbl9uH7463T89KoffSbuYm+FIBuoULAy6QhfmzJmOpDHJnubEFaUrUxiTBrYrAhjKhflrtMWjJkfS+J00QTzLLCbUIbpBffhkD8ZAFbpC0L5UGomIhUIkZjLihSZKiSDIXHg0wmLI5ZO5pv/ySpAewTGgaBBO7tJ3bv6EB96yB/ZWTDzAwFBAzlkQDUsQNhpZgoESacjxgMo6CFJ8QkzQP8VpGhbHu50oLY8CpywOMR5yVcb5SLjAw9kIq6AA04eh6Y1EgEVXgFT1k4s+cT/p5U2VkeGhTIspMZ2LKw4QofSKwW0ZejOHnICCZuENCLpL5f3Ne08geFrjcb84cO3QR2+tToX7nnyVulrmq5TpeOKgo/WLqjSn3lDLbGU65uTO1s+6+g4FpN98pLF0F8xc/CCm3v0IQyP/J/oatYM5AaMjI6kWUDYHUSthrWZDw578Uk18WEtNkQ+2v6QMBu6guH+6/3j4628YppaEJA9uRi6Q2IRUZkbNnQiR9KESW3jPIXTDuFtzc/76i8jd8RSUtLQ3cmnIUUG4fOVtvvEtLtU9Lr6CgC22seyslV61dF5yh1Aan393hYXOhgukUv0448FjDeVxTN7iPBZ/1zD//zZK1OCVl8PxdmbTwdWw5+RTj/jIvkDyAwuzVme8E4T/oZZEHQJq9RvOdIP2L3gt5QOGV11gWml/jfxRH1Z8YzS9OU1rHS/Kk99Pu0XTGWxGTrH4LyJczlaVRDIGivy6aWT3GIMruzcqLKrlm1u72uTOd/j+dn/n4
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful transactions referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new transactions referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known transaction unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream transactions created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"LPRetrieveRelatedTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=120192370561220608&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/transactions?cursor=120192344791343104&limit=2&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/895788"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908/operations","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908/effects","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=3847380164161536"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=3847380164161536"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908"}},"id":"2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908","paging_token":"3847380164161536","successful":true,"hash":"2ff47e1bafe68639276b2a8df0a73597ee0c062fbcc72d121af314fe7851c908","ledger":895788,"created_at":"2021-08-09T20:53:11Z","source_account":"GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7","source_account_sequence":"3847371574214658","fee_account":"GAHQN6YNYD6ZT7TLAVE4R36MSZWQJZ22XB3WD4RLSHURMXHW4VHJIDF7","fee_charged":"10000","max_fee":"10001","operation_count":1,"envelope_xdr":"AAAAAgAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAJxEADasqAAAAAgAAAAAAAAAAAAAAAQAAAAEAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAGAAAAAVNFQwAAAAAAm6XFaVsf8OSuS9C9gMplyTjagE9jAnnqwxSDJ6fin6IAsaK8LsUAAAAAAAAAAAAB9uVOlAAAAECXmRsoXmRiJjUrtbkDZYRnzac5s1CVV4g2RlIgBIuQty21npz3A1VhUcSmAx+GmsyGxVFvIrcdstTawJlmy9kF","result_xdr":"AAAAAAAAJxAAAAAAAAAAAQAAAAAAAAAGAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAA2rLAAAAAAAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAAGtJNDAANqyoAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAA2rLAAAAAAAAAAADwb7DcD9mf5rBUnI78yWbQTnWrh3YfIrkekWXPblTpQAAAAAGtJNDAANqyoAAAACAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAwAAAAMADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAIAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAIAAAABAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAADassAAAAAQAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAFTRUMAAAAAAJulxWlbH/DkrkvQvYDKZck42oBPYwJ56sMUgyen4p+iAAAAAAAAAAAAsaK8LsUAAAAAAAEAAAAAAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMADasrAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0nQcAA2rKgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEADassAAAAAAAAAAAPBvsNwP2Z/msFScjvzJZtBOdauHdh8iuR6RZc9uVOlAAAAAAa0k0MAA2rKgAAAAEAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["l5kbKF5kYiY1K7W5A2WEZ82nObNQlVeINkZSIASLkLcttZ6c9wNVYVHEpgMfhprMhsVRbyK3HbLU2sCZZsvZBQ=="]}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/README.mdx
deleted file mode 100644
index 880edcf664..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/README.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Recursos
-sidebar_position: 20
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Los datos en el ledger de Stellar están organizados según los recursos. Cada recurso tiene varios endpoints diferentes.
-
-<MethodTable title="Tipos de Recursos">
-
-|                                                                     |   |
-| ------------------------------------------------------------------- | - |
-| [Libros de contabilidad](./ledgers/README.mdx)                      |   |
-| [Transacciones](./transactions/README.mdx)                          |   |
-| [Operaciones](./operations/README.mdx)                              |   |
-| [Efectos](./effects/README.mdx)                                     |   |
-| [Cuentas](./accounts/README.mdx)                                    |   |
-| [Ofertas](./offers/README.mdx)                                      |   |
-| [Balances Reclamables](./claimablebalances/README.mdx)              |   |
-| [Intercambios](./trades/README.mdx)                                 |   |
-| [Activos](./assets/README.mdx)                                      |   |
-| [Fondos de Liquidez](./liquiditypools/README.mdx)                   |   |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/_category_.json
deleted file mode 100644
index 9e3a55f459..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/accounts/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/accounts/README.mdx
deleted file mode 100644
index f0de831509..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/accounts/README.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Cuentas
-order: 0
----
-
-Los usuarios interactúan con la red Stellar a través de cuentas. Todo lo demás en el ledger—activos, ofertas, líneas de confianza, etc.—pertenece a las cuentas, y las cuentas deben autorizar todos los cambios en el ledger a través de transacciones firmadas.
-
-El [ledger más reciente](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-Aprende más sobre [cuentas](../../../../../../learn/glossary.mdx#account).
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                                                    |
-| ------- | ---------------------------------------------------------------------------------- |
-| OBTENER | [/accounts](../../list-all-accounts.api.mdx)                                       |
-| OBTENER | [/accounts/:account_id](../../retrieve-an-account.api.mdx)                         |
-| OBTENER | [/accounts/:account_id/transactions](../../get-transactions-by-account-id.api.mdx) |
-| OBTENER | [/accounts/:account_id/operations](../../get-operations-by-account-id.api.mdx)     |
-| OBTENER | [/accounts/:account_id/payments](../../get-payments-by-account-id.api.mdx)         |
-| OBTENER | [/accounts/:account_id/effects](../../get-effects-by-account-id.api.mdx)           |
-| OBTENER | [/accounts/:account_id/offers](../../get-offers-by-account-id.api.mdx)             |
-| OBTENER | [/accounts/:account_id/trades](../../get-trades-by-account-id.api.mdx)             |
-| OBTENER | [/accounts/:account_id/data](../../get-data-by-account-id.api.mdx)                 |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/accounts/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/accounts/object.mdx
deleted file mode 100644
index 4ab2ccf4ff..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/accounts/object.mdx
+++ /dev/null
@@ -1,248 +0,0 @@
----
-title: El Objeto de Cuenta
-order: 10
----
-
-Cuando Horizon devuelve información sobre una cuenta, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- id
-  - cadena
-  - Un identificador único para esta cuenta.
-- account_id
-  - cadena
-  - La clave pública de esta cuenta codificada en una representación de cadena base32.
-- secuencia
-  - número
-  - El número de secuencia actual de esta cuenta. Para usar al enviar la próxima transacción de esta cuenta.
-- secuencia_ledger
-  - número
-  - El número del ledger de 32 bits sin firmar del [edad](../../../../../../learn/glossary.mdx#sequence-number) del número de secuencia.
-- secuencia_tiempo
-  - cadena
-  - La marca de tiempo UNIX de 64 bits sin firmar de la [edad](../../../../../../learn/glossary.mdx#sequence-number) del número de secuencia.
-- count_subentradas
-  - número
-  - El número de subentradas en esta cuenta.
-- dominio_principal
-  - cadena
-  - El dominio que aloja el archivo `stellar.toml` de esta cuenta.
-- ledger_última_modificación
-  - número
-  - La ID del último ledger que incluyó cambios en esta cuenta.
-- num_sponsoring
-  - número
-  - El número de reservas patrocinadas por esta cuenta.
-- num_sponsored
-  - número
-  - El número de reservas patrocinadas para esta cuenta.
-- patrocinador
-  - cadena (opcional)
-  - La ID de cuenta del patrocinador que está pagando las reservas por esta cuenta.
-- thresholds
-  - objeto
-  - Las operaciones tienen diferentes niveles de acceso. Este campo especifica los umbrales para diferentes niveles de acceso, así como el peso de la clave maestra.
-    - umbral_bajo
-      - número
-      - El peso requerido para una transacción válida que incluye las operaciones Permitir Confianza y Aumentar Secuencia.
-    - umbral_medio
-      - número
-      - El peso requerido para una transacción válida que incluye las operaciones Crear Cuenta, Pago, Pago por Ruta, Gestionar Oferta de Compra, Gestionar Oferta de Venta, Crear Oferta de Venta Pasiva, Cambiar Confianza, Inflación y Gestionar Datos.
-    - umbral_alto
-      - número
-      - El peso requerido para una transacción válida que incluye las operaciones Fusionar Cuenta y Establecer Opciones.
-- flags
-  - objeto
-  - Los flags indican la habilitación/deshabilitación de ciertos privilegios del emisor de activos.
-    - auth_inmutable
-      - booleano
-      - Si se establece en `true`, ninguno de los siguientes flags puede ser cambiado.
-    - auth_requerido
-      - booleano
-      - Si se establece en `true`, cualquiera que quiera poseer un activo emitido por esta cuenta debe ser aprobado primero por esta cuenta.
-    - auth_revocable
-      - booleano
-      - Si se establece en `true`, esta cuenta puede congelar el saldo de un propietario de un activo emitido por esta cuenta.
-    - auth_clawback_enabled
-      - booleano
-      - Si se establece en `true`, las líneas de confianza creadas para activos emitidos por esta cuenta tienen habilitados los [clawbacks](../../../../../../learn/glossary.mdx#clawback).
-- saldos
-  - objeto
-  - Los activos que posee esta cuenta.
-    - saldo
-      - cadena
-      - El número de unidades de un activo que posee esta cuenta.
-    - pasivos_de_compra
-      - cadena (opcional)
-      - La suma de todas las ofertas de compra que posee esta cuenta para este activo.
-    - pasivos_de_venta
-      - cadena (opcional)
-      - La suma de todas las ofertas de venta que posee esta cuenta para este activo.
-    - límite
-      - número (opcional)
-      - La cantidad máxima de este activo que esta cuenta está dispuesta a aceptar. Especificado al abrir una línea de confianza.
-    - tipo_de_activo
-      - cadena
-      - Ya sea `nativo`, `crédito_alphanum4`, `crédito_alphanum12`, o `liquidity_pool_shares`.
-    - codigo_de_activo
-      - cadena (opcional)
-      - El código para este activo.
-    - emisor_de_activo
-      - cadena (opcional)
-      - La dirección Stellar del emisor de este activo.
-    - patrocinador
-      - cadena (opcional)
-      - La ID de cuenta del patrocinador que está pagando las reservas por esta línea de confianza.
-- firmantes
-  - array de objetos
-  - Las claves públicas y los pesos asociados que se pueden usar para autorizar transacciones de esta cuenta. Usado para multi-firma.
-    - clave_publica
-      - cadena
-      - **ELIMINADO en 0.17.0: USE `key` EN SU LUGAR.**
-    - peso
-      - número
-      - El peso numérico de un firmante. Usado para determinar si una transacción cumple con los requisitos de `umbral`.
-    - patrocinador
-      - cadena (opcional)
-      - La ID de cuenta del patrocinador que está pagando las reservas por este firmante.
-    - clave
-      - cadena
-      - Un hash de caracteres dependiente del tipo de firmante.
-    - tipo
-      - cadena
-      - El tipo de hash para este firmante.
-        - clave_publica_ed25519
-          - saltar
-          - Una clave pública Stellar normal.
-        - hash_sha256
-          - saltar
-          - El hash SHA256 de algún `x` arbitrario. Agregar una firma de este tipo permite a cualquiera que conozca x firmar una transacción de esta cuenta. _Nota: Una vez que esta transacción sea transmitida, x será conocido públicamente._
-        - transacción_auth_preautorizada
-          - saltar
-          - El hash de una transacción preautorizada. Este firmante se elimina automáticamente de la cuenta cuando una transacción coincidente se aplica correctamente.
-- datos
-  - objeto
-  - Un arreglo de campos de datos de cuenta.
-
-</AttributeTable>
-
-El [último ledger](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U"
-    },
-    "transactions": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/transactions{?cursor,limit,order}",
-      "templated": true
-    },
-    "operations": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/operations{?cursor,limit,order}",
-      "templated": true
-    },
-    "payments": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/payments{?cursor,limit,order}",
-      "templated": true
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/effects{?cursor,limit,order}",
-      "templated": true
-    },
-    "offers": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/offers{?cursor,limit,order}",
-      "templated": true
-    },
-    "trades": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/trades{?cursor,limit,order}",
-      "templated": true
-    },
-    "data": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U/data/{key}",
-      "templated": true
-    }
-  },
-  "id": "GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U",
-  "account_id": "GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U",
-  "sequence": "24739097524306468",
-  "subentry_count": 3,
-  "inflation_destination": "GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U",
-  "home_domain": "tempo.eu.com",
-  "last_modified_ledger": 23569316,
-  "num_sponsoring": 0,
-  "num_sponsored": 0,
-  "thresholds": {
-    "low_threshold": 5,
-    "med_threshold": 0,
-    "high_threshold": 0
-  },
-  "flags": {
-    "auth_required": false,
-    "auth_revocable": true,
-    "auth_immutable": false,
-    "auth_clawback_enabled": true
-  },
-  "balances": [
-    {
-      "balance": "1.0000005",
-      "limit": "922337203685.4775807",
-      "buying_liabilities": "0.0000000",
-      "selling_liabilities": "0.0000000",
-      "last_modified_ledger": 22651481,
-      "is_authorized": true,
-      "is_clawback_enabled": false,
-      "asset_type": "credit_alphanum4",
-      "asset_code": "EURT",
-      "asset_issuer": "GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"
-    },
-    {
-      "balance": "0.0000000",
-      "limit": "922337203685.4775807",
-      "buying_liabilities": "0.0000000",
-      "selling_liabilities": "0.0000000",
-      "last_modified_ledger": 7877447,
-      "is_authorized": false,
-      "is_clawback_enabled": false,
-      "asset_type": "credit_alphanum4",
-      "asset_code": "PHP",
-      "asset_issuer": "GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"
-    },
-    {
-      "balance": "0.0000000",
-      "limit": "922337203685.4775807",
-      "buying_liabilities": "0.0000000",
-      "selling_liabilities": "0.0000000",
-      "last_modified_ledger": 20213845,
-      "is_authorized": true,
-      "is_clawback_enabled": false,
-      "asset_type": "credit_alphanum4",
-      "asset_code": "NGN",
-      "asset_issuer": "GCC4YLCR7DDWFCIPTROQM7EB2QMFD35XRWEQVIQYJQHVW6VE5MJZXIGW"
-    },
-    {
-      "balance": "198.8944970",
-      "buying_liabilities": "0.0000000",
-      "selling_liabilities": "0.0000000",
-      "asset_type": "native"
-    }
-  ],
-  "signers": [
-    {
-      "weight": 10,
-      "key": "GDI73WJ4SX7LOG3XZDJC3KCK6ED6E5NBYK2JUBQSPBCNNWEG3ZN7T75U",
-      "type": "ed25519_public_key"
-    }
-  ],
-  "data": {},
-  "paging_token": ""
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/assets/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/assets/README.mdx
deleted file mode 100644
index dcb9db0a84..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/assets/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Activos
-order: 0
----
-
-Los activos son representaciones de valor emitidas en la red Stellar. Un activo consiste en un tipo, un código y un emisor.
-
-El [último ledger](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-Aprende más sobre [activos](../../../../../../learn/glossary.mdx#asset).
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                          |
-| ------- | ---------------------------------------- |
-| OBTENER | [/assets](../../list-all-assets.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/assets/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/assets/object.mdx
deleted file mode 100644
index 14dcf89c96..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/assets/object.mdx
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: El Objeto de Activo
-order: 10
----
-
-Cuando Horizon devuelve información sobre un activo, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- tipo_de_activo
-  - cadena
-  - El tipo de este activo. Ya sea `credit_alphanum4` o `credit_alphanum12`.
-- código_de_activo
-  - cadena
-  - El código de este activo
-- emisor_de_activo
-  - cadena
-  - La dirección Stellar del emisor de este activo.
-- cuentas
-  - objeto
-  - El número de cuentas agrupadas por cada estado de la bandera de la línea de confianza.
-- num_saldos_reclamables
-  - número
-  - El número actual de saldos_reclamables para este activo.
-- num_contratos
-  - número
-  - El número actual de contratos de Soroban que poseen este activo.
-- num_fondos_de_liquidez
-  - número
-  - El número actual de fondos de liquidez que poseen este activo.
-- saldos
-  - objeto
-  - El número de unidades emitidas para este activo agrupadas por cada estado de la bandera de la línea de confianza.
-- monto_de_saldos_reclamables
-  - cadena
-  - El número de unidades para este activo que posee todos los saldos reclamables.
-- monto_de_contratos
-  - cadena
-  - El número de unidades para este activo que poseen todos los contratos de Soroban.
-- monto_de_fondos_de_liquidez
-  - cadena
-  - El número de unidades para este activo que poseen todos los fondos de liquidez.
-- banderas
-  - objeto
-  - Las banderas indican el habilitar/deshabilitar ciertos privilegios del emisor de activos.
-    - auth_inmutable
-      - booleano
-      - Si se establece en `true`, ninguna de las siguientes banderas puede ser cambiada.
-    - auth_requerido
-      - booleano
-      - Si se establece en `true`, cualquier persona que desee poseer un activo emitido por esta cuenta debe ser aprobada primero por esta cuenta.
-    - auth_revocable
-      - booleano
-      - Si se establece en `true`, esta cuenta puede congelar el saldo de un poseedor de un activo emitido por esta cuenta.
-- token_de_paginación
-  - número
-  - Un valor de cursor para usar en [paginación](../../structure/pagination/README.mdx).
-
-</AttributeTable>
-
-El [último ledger](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/assets?asset_code=USD\u0026asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX\u0026cursor=\u0026limit=10\u0026order=asc"
-    },
-    "next": {
-      "href": "https://horizon-testnet.stellar.org/assets?asset_code=USD\u0026asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX\u0026cursor=USD_GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX_credit_alphanum4\u0026limit=10\u0026order=asc"
-    },
-    "prev": {
-      "href": "https://horizon-testnet.stellar.org/assets?asset_code=USD\u0026asset_issuer=GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX\u0026cursor=USD_GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX_credit_alphanum4\u0026limit=10\u0026order=desc"
-    }
-  },
-  "_embedded": {
-    "records": [
-      {
-        "_links": {
-          "toml": {
-            "href": "https://www.anchorusd.com/.well-known/stellar.toml"
-          }
-        },
-        "asset_type": "credit_alphanum4",
-        "asset_code": "USD",
-        "asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX",
-        "paging_token": "USD_GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX_credit_alphanum4",
-        "accounts": {
-          "authorized": 9390,
-          "authorized_to_maintain_liabilities": 1240,
-          "unauthorized": 5
-        },
-        "num_claimable_balances": 253,
-        "balances": {
-          "authorized": "1347404.4083346",
-          "authorized_to_maintain_liabilities": "177931.9984610",
-          "unauthorized": "717.4677360"
-        },
-        "claimable_balances_amount": "36303.8674450",
-        "flags": {
-          "auth_required": false,
-          "auth_revocable": false,
-          "auth_immutable": false
-        }
-      }
-    ]
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx
deleted file mode 100644
index 3d5454b1d4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/claimablebalances/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Saldos reclamables
-order: 0
----
-
-Un saldo reclamable representa la transferencia de propiedad de una cierta cantidad de un activo. Los saldos reclamables proporcionan un mecanismo para configurar un pago que puede ser reclamado en el futuro. Esto te permite hacer pagos a cuentas que actualmente no pueden aceptarlos.
-
-El [último ledger](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-<EndpointsTable title="Puntos de extremidad">
-
-|         |                                                                                                          |
-| ------- | -------------------------------------------------------------------------------------------------------- |
-| OBTENER | [/claimable_balances](../../list-all-claimable-balances.api.mdx)                                         |
-| OBTENER | [/claimable_balances/:claimable_balance_id](../../retrieve-a-claimable-balance.api.mdx)                  |
-| OBTENER | [/claimable_balances/:claimable_balance_id/transactions](../../cb-retrieve-related-transactions.api.mdx) |
-| OBTENER | [/claimable_balances/:claimable_balance_id/operations](../../cb-retrieve-related-operations.api.mdx)     |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx
deleted file mode 100644
index 9aee952804..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/claimablebalances/object.mdx
+++ /dev/null
@@ -1,118 +0,0 @@
----
-title: El Objeto de Saldo Reclamable
-order: 10
----
-
-Cuando Horizon devuelve información sobre un saldo reclamable, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATOS
-  - DESCRIPCIÓN
-- id
-  - cadena
-  - Un identificador único para este saldo reclamable.
-- token_de_paginación
-  - número
-  - Un valor de cursor para usar en [paginación](../../structure/pagination/README.mdx).
-- activo
-  - cadena
-  - El activo disponible para ser reclamado en el [formulario SEP-11](https://github.com/stellar/stellar-protocol/blob/0c675fb3a482183dcf0f5db79c12685acf82a95c/ecosystem/sep-0011.md#values) `asset_code:issuing_address` o `nativo` (para XLM)
-- cantidad
-  - cadena
-  - La cantidad de `activo` que puede ser reclamada.
-- patrocinador
-  - cadena (opcional)
-  - El id de cuenta del patrocinador que está pagando las reservas para este saldo reclamable.
-- último_libro_modificado
-  - entero
-  - El número de secuencia del último libro en el que se modificó este saldo reclamable.
-- último_tiempo_modificado
-  - cadena
-  - Una cadena formateada en ISO 8601 de la última hora de modificación.
-- reclamantes
-  - array de objetos
-  - La lista de entradas que podrían reclamar el saldo reclamable.
-    - destino
-      - cadena
-      - El ID de cuenta que puede reclamar el saldo.
-    - predicado
-      - objeto
-      - La condición que debe ser satisfecha para que `destino` pueda reclamar el saldo.
-        - incondicional
-          - booleano (opcional)
-          - Si es verdadero, significa que esta cláusula de la condición siempre se satisface.
-        - y
-          - array de objetos (opcional)
-          - El array siempre contendrá dos elementos que también son predicados. Esta cláusula de la condición se satisface si ambos de los dos elementos en el array se satisfacen.
-        - o
-          - array de objetos (opcional)
-          - El array siempre contendrá dos elementos que también son predicados. Esta cláusula de la condición se satisface si al menos uno de los dos elementos en el array se satisface.
-        - no
-          - objeto (opcional)
-          - El valor también es un predicado. Esta cláusula de la condición se satisface si el valor _no_ se satisface.
-        - absAntes
-          - cadena (opcional)
-          - Una cadena personalizada formateada en ISO 8601 que representa un plazo para cuándo se puede reclamar el saldo reclamable. Si el saldo es reclamado antes de la fecha, entonces esta cláusula de la condición se satisface. El formato de esta cadena de fecha es una extensión personalizada sobre el formato ISO 8601. Permite que los años estén fuera del rango 0000-9999. Las fechas se derivan de un valor de época unix en el rango de un entero firmado de 64 bits. Esto significa que la fecha expresa un rango de calendario mucho más grande de 292277026596 años hacia el futuro y -292471206707 años hacia el pasado. Este formato de extensión personalizada añadirá un prefijo `'+'` en los valores que superen el año 9999 en el futuro y para los años que están antes del año 0 (A.C. según el calendario gregoriano) se añadirá un prefijo `'-'`. Aquí hay ejemplos de valores de cadenas de fecha que son posibles: `'2022-02-10T15:30:22Z'` `'+39121901036-03-29T15:30:22Z'` `'-7025-12-23T00:00:00Z'`
-        - absAntesÉpoca
-          - cadena (opcional)
-          - Un valor de época unix en segundos que representa la misma fecha de plazo para cuándo se puede reclamar el saldo reclamable. Es el mismo valor de fecha/hora que representa absAntes, solo expresado en segundos enteros de época unix dentro del rango de un entero firmado de 64 bits.
-        - relAntes
-          - cadena (opcional)
-          - Un plazo relativo para cuándo se puede reclamar el saldo reclamable. El valor representa el número de segundos desde el tiempo de cierre del libro que creó el saldo reclamable.
-
-</AttributeTable>
-
-El [último libro](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000"
-    },
-    "operations": {
-      "href": "https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000/operations{?cursor,limit,order}",
-      "templated": true
-    },
-    "transactions": {
-      "href": "https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000/transactions{?cursor,limit,order}",
-      "templated": true
-    }
-  },
-  "id": "000000000102030000000000000000000000000000000000000000000000000000000000",
-  "paging_token": "000000000102030000000000000000000000000000000000000000000000000000000000",
-  "asset": "native",
-  "amount": "10.0000000",
-  "claimants": [
-    {
-      "destination": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML",
-      "predicate": {
-        "and": [
-          {
-            "or": [
-              {
-                "relBefore": "12"
-              },
-              {
-                "absBefore": "2020-08-26T11:15:39Z",
-                "absBeforeEpoch": "1598440539"
-              }
-            ]
-          },
-          {
-            "not": { "unconditional": true }
-          }
-        ]
-      }
-    }
-  ],
-  "last_modified_ledger": 28411995,
-  "last_modified_time": "2020-02-26T19:29:16Z"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/effects/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/effects/README.mdx
deleted file mode 100644
index 799ef93e17..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/effects/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Efectos
-order: 0
----
-
-Los efectos representan cambios específicos que ocurren en el ledger como resultado de operaciones exitosas, pero no se reflejan necesariamente directamente en el ledger o en la historia, como lo hacen las transacciones y operaciones.
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                            |
-| ------- | ------------------------------------------ |
-| OBTENER | [/effects](../../list-all-effects.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/effects/types.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/effects/types.mdx
deleted file mode 100644
index 7738497fa2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/effects/types.mdx
+++ /dev/null
@@ -1,240 +0,0 @@
----
-title: Tipos de Efecto
-order: 10
----
-
-Hay ocho grupos de tipos de efecto. Cada tipo de efecto tiene su propio conjunto de atributos.
-
-### Efectos de Cuenta
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Cuenta creada
-  - saltar
-  - crear_cuenta
-- Cuenta eliminada
-  - saltar
-  - fusionar_cuenta
-- Cuenta acreditada
-  - saltar
-  - crear_cuenta, pago, pago_por_ruta, fusionar_cuenta
-- Cuenta debitada
-  - saltar
-  - crear_cuenta, pago, pago_por_ruta, fusionar_cuenta
-- Umbrales de Cuenta Actualizados
-  - saltar
-  - establecer_opciones
-- Dominio de Casa de Cuenta Actualizado
-  - saltar
-  - establecer_opciones
-- Banderas de Cuenta Actualizadas
-  - saltar
-  - establecer_opciones
-- Destino de Inflación de Cuenta Actualizado
-  - saltar
-  - establecer_opciones
-
-</AttributeTable>
-
-### Efectos de Firmante
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Firmante creado
-  - saltar
-  - establecer_opciones
-- Firmante eliminado
-  - saltar
-  - establecer_opciones
-- Firmante actualizado
-  - saltar
-  - establecer_opciones
-
-</AttributeTable>
-
-### Efectos de Línea de Confianza
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Línea de Confianza creada
-  - saltar
-  - cambiar_confianza
-- Línea de Confianza eliminada
-  - saltar
-  - cambiar_confianza
-- Línea de Confianza actualizada
-  - saltar
-  - cambiar_confianza, permitir_confianza
-- Línea de Confianza autorizada
-  - saltar
-  - permitir_confianza
-- Línea de Confianza desautorizada
-  - saltar
-  - permitir_confianza
-
-</AttributeTable>
-
-### Efectos de Comercio
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Oferta creada
-  - saltar
-  - gestionar_oferta_de_compra, gestionar_oferta_de_venta, crear_oferta_de_venta_pasiva
-- Oferta eliminada
-  - saltar
-  - gestionar_oferta_de_compra, gestionar_oferta_de_venta, crear_oferta_de_venta_pasiva, pago_por_ruta
-- Oferta actualizada
-  - saltar
-  - gestionar_oferta_de_compra, gestionar_oferta_de_venta, crear_oferta_de_venta_pasiva, pago_por_ruta
-- Intercambio
-  - saltar
-  - gestionar_oferta_de_compra, gestionar_oferta_de_venta, crear_oferta_de_venta_pasiva, pago_por_ruta
-
-</AttributeTable>
-
-### Efectos de Datos
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Datos creados
-  - saltar
-  - gestionar_datos
-- Datos eliminados
-  - saltar
-  - gestionar_datos
-- Datos actualizados
-  - saltar
-  - gestionar_datos
-
-</AttributeTable>
-
-### Efectos de Saldo Reclamable
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Saldo Reclamable creado
-  - saltar
-  - crear_saldo_reclamable
-- Reclamante de Saldo Reclamable creado
-  - saltar
-  - crear_saldo_reclamable
-- Saldo Reclamable reclamado
-  - saltar
-  - reclamar_saldo_reclamable
-
-</AttributeTable>
-
-### Efectos de Patrocinio
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Patrocinio de Cuenta creado
-  - saltar
-  - crear_cuenta
-- Patrocinio de Cuenta actualizado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Cuenta eliminado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Línea de Confianza creado
-  - saltar
-  - cambiar_confianza
-- Patrocinio de Línea de Confianza actualizado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Línea de Confianza eliminado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Datos de Cuenta creado
-  - saltar
-  - gestionar_datos
-- Patrocinio de Datos de Cuenta actualizado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Datos de Cuenta eliminado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Saldo Reclamable creado
-  - saltar
-  - crear_saldo_reclamable
-- Patrocinio de Saldo Reclamable actualizado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Saldo Reclamable eliminado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Firmante de Cuenta creado
-  - saltar
-  - establecer_opciones
-- Patrocinio de Firmante de Cuenta actualizado
-  - saltar
-  - revocar_patrocinio
-- Patrocinio de Firmante de Cuenta eliminado
-  - saltar
-  - revocar_patrocinio
-
-</AttributeTable>
-
-### Efectos de Fondos de Liquidez
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Fondo de Liquidez creado
-  - saltar
-  - cambiar_confianza
-- Fondo de Liquidez eliminado
-  - saltar
-  - cambiar_confianza
-- Fondo de Liquidez Revocado
-  - saltar
-  - cambiar_confianza, permitir_confianza
-- Fondo de Liquidez Depositado
-  - saltar
-  - deposito_fondo_liquidez
-- Retirar Fondo de Liquidez
-  - saltar
-  - retirar_fondo_liquidez
-- Intercambio de Fondo de Liquidez
-  - saltar
-  - pago_por_ruta
-
-</AttributeTable>
-
-### Efectos Varios
-
-<AttributeTable>
-
-- TIPO
-  - saltar
-  - OPERACIÓN(ES)
-- Secuencia Aumentada
-  - saltar
-  - aumentar_secuencia
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/ledgers/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/ledgers/README.mdx
deleted file mode 100644
index a3524133e6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/ledgers/README.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Libros de contabilidad
-order: 0
----
-
-Cada libro de contabilidad almacena el estado de la red en un momento dado y contiene todos los cambios: transacciones, operaciones, efectos, etc. - a ese estado.
-
-Aprende más sobre los [libros de contabilidad](../../../../../../learn/glossary.mdx#ledger).
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                                                         |
-| ------- | --------------------------------------------------------------------------------------- |
-| OBTENER | [/ledgers/:ledger_sequence](../../retrieve-a-ledger.api.mdx)                            |
-| OBTENER | [/ledgers/:ledger_sequence/transactions](../../retrieve-a-ledgers-transactions.api.mdx) |
-| OBTENER | [/ledgers/:ledger_sequence/operations](../../retrieve-a-ledgers-operations.api.mdx)     |
-| OBTENER | [/ledgers/:ledger_sequence/payments](../../retrieve-a-ledgers-payments.api.mdx)         |
-| OBTENER | [/ledgers/:ledger_sequence/effects](../../retrieve-a-ledgers-effects.api.mdx)           |
-| OBTENER | [/ledgers](../../list-all-ledgers.api.mdx)                                              |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/ledgers/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/ledgers/object.mdx
deleted file mode 100644
index cfe0d7e442..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/ledgers/object.mdx
+++ /dev/null
@@ -1,112 +0,0 @@
----
-title: El objeto Ledger
-order: 10
----
-
-Cuando Horizon devuelve información sobre un ledger, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATOS
-  - DESCRIPCIÓN
-- id
-  - cadena
-  - Un identificador único para este ledger.
-- token_de_paginación
-  - número
-  - Un valor de cursor para usar en [paginación](../../structure/pagination/README.mdx).
-- hash
-  - cadena
-  - Un hash SHA-256 codificado en hexadecimal de la forma codificada en [XDR](../../../../../../learn/fundamentals/data-format/xdr.mdx) de este libro mayor.
-- prev_hash
-  - cadena
-  - El hash del ledger inmediatamente anterior a este ledger.
-- secuencia
-  - número
-  - El número de secuencia de este ledger y el parámetro usado en las llamadas de Horizon que requieren un número de ledger.
-- cuenta_de_transacciones_exitosas
-  - número
-  - El número de transacciones exitosas en este ledger.
-- cuenta_de_transacciones_fallidas
-  - número
-  - El número de transacciones fallidas en este ledger.
-- cuenta_de_operaciones
-  - número
-  - El número de operaciones aplicadas en este ledger.
-- cuenta_de_operaciones_tx_set
-  - número
-  - El número total de operaciones en el conjunto de transacciones (incluidas las transacciones fallidas).
-- cerrado_en
-  - cadena
-  - Una cadena formateada según [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) que indica cuándo se cerró este ledger.
-- monedas_totales
-  - cadena
-  - El número total de lumens en circulación.
-- pool_de_comisiones
-  - cadena
-  - La suma de todas las tarifas de transacción.
-- comisión_base_en_stroops
-  - número
-  - La tarifa que la red cobra por operación en una transacción.
-- reserva_base_en_stroops
-  - número
-  - La reserva que la red utiliza al calcular el saldo mínimo de una cuenta.
-- tamaño_max_tx_set
-  - número
-  - El número máximo de operaciones que los validadores han acordado procesar en un ledger dado. Desde el Protocolo 11, la capacidad del ledger se ha medido en operaciones en lugar de transacciones. Para más información sobre esa decisión, consulta [CAP-5](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0005.md#repurposing-ledgerheadermaxtxsetsize).
-- versión_del_protocolo
-  - número
-  - La versión del protocolo que la red Stellar estaba ejecutando cuando se comprometió este ledger.
-- header_xdr
-  - cadena
-  - Una cadena codificada base64 de la estructura xdr `LedgerHeader` raw para este ledger.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/26857634"
-    },
-    "transactions": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/26857634/transactions{?cursor,limit,order}",
-      "templated": true
-    },
-    "operations": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/26857634/operations{?cursor,limit,order}",
-      "templated": true
-    },
-    "payments": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/26857634/payments{?cursor,limit,order}",
-      "templated": true
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/26857634/effects{?cursor,limit,order}",
-      "templated": true
-    }
-  },
-  "id": "548393ec23959e1959a62f003029ecf96be89e13df036073bf64918996ec4227",
-  "paging_token": "115352659677937664",
-  "hash": "548393ec23959e1959a62f003029ecf96be89e13df036073bf64918996ec4227",
-  "prev_hash": "446d6eca81dd6db6daf50d93ca9d297bd60b1233b91de3765cccdf503cfffcb0",
-  "sequence": 26857634,
-  "successful_transaction_count": 27,
-  "failed_transaction_count": 1,
-  "operation_count": 133,
-  "tx_set_operation_count": 134,
-  "closed_at": "2019-11-18T19:27:21Z",
-  "total_coins": "105443902087.3472865",
-  "fee_pool": "1807038.9789761",
-  "base_fee_in_stroops": 100,
-  "base_reserve_in_stroops": 5000000,
-  "max_tx_set_size": 1000,
-  "protocol_version": 12,
-  "header_xdr": "AAAADERtbsqB3W222vUNk8qdKXvWCxIzuR3jdlzM31A8//ywoQieYsSc05/BpgEqnLR7fKXz7t0K42V7NOjbGZA/wTEAAAAAXdLwmQAAAAAAAAAAplf68mTg/Z/DDyEZeLCoNbJnMZm4SYsYWjUjuDOSfPeRNFE4n9Hm19yKutjwVurFjk72JKVHI8J+ELwLZgWsywGZ0KIOoh6z7HlbYQAAEG9XKhRBAAABFgAAAAAH9M6YAAAAZABMS0AAAAPop9+CeMs1/7BHgFltiQPH+VT+ACYb5P0lSXh7RpBLtd34kEpeL8qKJxYz4ufmkQ2lEv/HMR/i3bi1Rt0PYj185/0kAZ3ZRbmm2mVRMzmaCOak1rn2vejHXDh+MGlr6D6vI2tc/M6VIumTKUa7SgumWDyW0r5FcJTbu/FXDQ/6C4YAAAAA"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx
deleted file mode 100644
index fd85de0f31..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/liquiditypools/README.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Fondos de Liquidez
-order: 0
----
-
-Los Fondos de Liquidez proporcionan una forma simple y no interactiva de intercambiar grandes cantidades de capital y permiten altos volúmenes de negociación.
-
-El [ledger más reciente](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                                                                    |
-| ------- | -------------------------------------------------------------------------------------------------- |
-| OBTENER | [/liquidity_pools](../../list-liquidity-pools.api.mdx)                                             |
-| OBTENER | [/liquidity_pools/:liquidity_pool_id](../../retrieve-a-liquidity-pool.api.mdx)                     |
-| OBTENER | [/liquidity_pools/:liquidity_pool_id/effects](../../retrieve-related-effects.api.mdx)              |
-| OBTENER | [/liquidity_pools/:liquidity_pool_id/trades](../../retrieve-related-trades.api.mdx)                |
-| OBTENER | [/liquidity_pools/:liquidity_pool_id/transactions](../../lp-retrieve-related-transactions.api.mdx) |
-| OBTENER | [/liquidity_pools/:liquidity_pool_id/operations](../../lp-retrieve-related-operations.api.mdx)     |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/offers/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/offers/README.mdx
deleted file mode 100644
index c32ffb058b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/offers/README.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Ofertas
-order: 0
----
-
-Las ofertas son declaraciones sobre cuánto de un activo una cuenta desea comprar o vender.
-
-El [último ledger](../../structure/consistency.mdx) conocido por Horizon se incluye como un encabezado HTTP en la respuesta.
-
-Aprende más sobre [ofertas](../../../../../../learn/glossary.mdx#decentralized-exchange).
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                                     |
-| ------- | ------------------------------------------------------------------- |
-| OBTENER | [/ofertas](../../get-all-offers.api.mdx)                            |
-| OBTENER | [/ofertas/:offer_id](../../get-offer-by-offer-id.api.mdx)           |
-| OBTENER | [/ofertas/:offer_id/comercio](../../get-trades-by-offer-id.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/offers/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/offers/object.mdx
deleted file mode 100644
index a0af9dbaf8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/offers/object.mdx
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: El Objeto de Oferta
-order: 10
----
-
-Cuando Horizon devuelve información sobre una oferta, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- id
-  - cadena
-  - Un identificador único para esta oferta.
-- token_de_paginación
-  - número
-  - Un valor de cursor para usar en [paginación](../../structure/pagination/README.mdx).
-- vendedor
-  - cadena
-  - El ID de la cuenta que hace esta oferta.
-- vendiendo
-  - código de activo
-  - El activo que esta oferta quiere vender.
-- comprando
-  - código de activo
-  - El activo que esta oferta quiere comprar.
-- cantidad
-  - cadena
-  - La cantidad de `vendiendo` que la cuenta que hace esta oferta está dispuesta a vender.
-- precio_r
-  - objeto
-  - Una representación precisa del precio de compra y venta de los activos ofrecidos.
-    - n
-      - número
-      - El numerador.
-    - d
-      - número
-      - El denominador.
-- precio
-  - cadena
-  - Cuántas unidades de `comprando` se necesitan para obtener 1 unidad de `vendiendo`. Un número que representa la forma decimal de `precio_r`.
-- último_libro_de_ledger_modificado
-  - entero
-  - El número de secuencia del último libro de ledger en el que se modificó esta oferta.
-- último_tiempo_de_modificación
-  - cadena
-  - Una cadena formateada en ISO 8601 de la última hora de modificación.
-- patrocinador
-  - cadena (opcional)
-  - El ID de la cuenta del patrocinador que está pagando las reservas para esta oferta.
-
-</AttributeTable>
-
-El [último libro de ledger](../../structure/consistency.mdx) que se conoce en Horizon se incluye como un encabezado HTTP en la respuesta.
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/offers/165561423"
-    },
-    "offer_maker": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GCK4WSNF3F6ZNCMK6BU77ZCZ3NMF3JGU2U3ZAPKXYBKYYCJA72FDBY7K"
-    }
-  },
-  "id": 165561423,
-  "paging_token": "165561423",
-  "seller": "GCK4WSNF3F6ZNCMK6BU77ZCZ3NMF3JGU2U3ZAPKXYBKYYCJA72FDBY7K",
-  "selling": {
-    "asset_type": "credit_alphanum4",
-    "asset_code": "NGNT",
-    "asset_issuer": "GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD"
-  },
-  "buying": {
-    "asset_type": "native"
-  },
-  "amount": "18421.4486092",
-  "price_r": {
-    "n": 45112058,
-    "d": 941460545
-  },
-  "price": "0.0479171",
-  "last_modified_ledger": 28411995,
-  "last_modified_time": "2020-02-26T19:29:16Z"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/README.mdx
deleted file mode 100644
index 900bfee5f2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Operaciones
-order: 0
----
-
-Las operaciones son objetos que representan un cambio deseado en el ledger: pagos, ofertas para intercambiar divisas, cambios realizados en las opciones de la cuenta, etc. Las operaciones se envían a la red Stellar agrupadas en una Transacción.
-
-Cada una de las operaciones de Stellar tiene un objeto de operación único.
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                                                                   |
-| ------- | --------------------------------------------------------------------------------- |
-| OBTENER | [/operations/:operation_id](../../retrieve-an-operation.api.mdx)                  |
-| OBTENER | [/operations/:operation_id/effects](../../retrieve-an-operations-effects.api.mdx) |
-| OBTENER | [/operations](../../list-all-operations.api.mdx)                                  |
-| OBTENER | [/payments](../../list-all-payments.api.mdx)                                      |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/README.mdx
deleted file mode 100644
index 3e6d9eec47..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/README.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: El Objeto de Operación
-order: 0
----
-
-Cada una de las operaciones de Stellar tiene formas de respuesta únicas. A continuación se presentan los atributos que son comunes en los objetos de operación individuales.
-
-Consulta los [errores genéricos de Operación](../../../errors/result-codes/operations.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- id
-  - número
-  - El número de identificación de la operación.
-- token_de_paginación
-  - cadena
-  - Un valor de cursor para usar en [paginación](../../../structure/pagination/README.mdx).
-- tipo_i
-  - número
-  - Un número que indica el tipo de operación.
-- tipo
-  - cadena
-  - El nombre del tipo de operación.
-- hash_de_transacción
-  - cadena
-  - Un identificador único para la transacción a la que pertenece esta operación.
-- transacción_exitosa
-  - booleano
-  - Indica si esta operación fue parte de una transacción exitosa.
-- cuenta_origen
-  - cadena
-  - La cuenta que origina la operación.
-- creado_en
-  - cadena
-  - La fecha en que se creó esta operación.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "effects": {
-      "href": "/operations/402494270214144/effects/{?cursor,limit,order}",
-      "templated": true
-    },
-    "precedes": {
-      "href": "/operations?cursor=402494270214144&order=asc"
-    },
-    "self": {
-      "href": "/operations/402494270214144"
-    },
-    "succeeds": {
-      "href": "/operations?cursor=402494270214144&order=desc"
-    },
-    "transactions": {
-      "href": "/transactions/402494270214144"
-    }
-  },
-  "id": 402494270214144,
-  "paging_token": "402494270214144",
-  "type_i": 0,
-  "type": "create_account"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/account-merge.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/account-merge.mdx
deleted file mode 100644
index 7d862db755..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/account-merge.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Objeto de Fusión de Cuenta
-order: 110
----
-
-Elimina la cuenta origen del Stellar y transfiere los lumens de la cuenta origen a otra cuenta.
-
-Consulta los [errores de `Fusión de Cuenta`](../../../errors/result-codes/operation-specific/account-merge.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- cuenta
-  - cadena
-  - La dirección Stellar que se está eliminando.
-- en
-  - cadena
-  - La dirección Stellar que recibe los lumens de la cuenta eliminada.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/121887714411839489"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/02077009a551ec94c776f83529293dcfc1c2cd5b38af043ef7f3699bf5a71f0a"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/121887714411839489/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=121887714411839489"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=121887714411839489"
-    }
-  },
-  "id": "121887714411839489",
-  "paging_token": "121887714411839489",
-  "transaction_successful": true,
-  "source_account": "GCVLWV5B3L3YE6DSCCMHLCK7QIB365NYOLQLW3ZKHI5XINNMRLJ6YHVX",
-  "type": "account_merge",
-  "type_i": 8,
-  "created_at": "2020-02-24T17:03:00Z",
-  "transaction_hash": "02077009a551ec94c776f83529293dcfc1c2cd5b38af043ef7f3699bf5a71f0a",
-  "account": "GCVLWV5B3L3YE6DSCCMHLCK7QIB365NYOLQLW3ZKHI5XINNMRLJ6YHVX",
-  "into": "GATL3ETTZ3XDGFXX2ELPIKCZL7S5D2HY3VK4T7LRPD6DW5JOLAEZSZBA"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/allow-trust.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/allow-trust.mdx
deleted file mode 100644
index f8ee82c848..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/allow-trust.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Permitir Objeto de Confianza
-order: 100
----
-
-Actualiza el indicador “autorizado” de una línea de confianza existente. Esto debe ser llamado por el emisor del activo.
-
-Consulta los [errores de `Permitir Confianza`](../../../errors/result-codes/operation-specific/allow-trust.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- tipo_de_activo
-  - cadena
-  - El tipo de activo. Puede ser `nativo`, `credit_alphanum4`, o `credit_alphanum12`.
-- código_de_activo
-  - cadena
-  - La dirección Stellar del activo.
-- emisor_de_activo
-  - cadena
-  - El código del activo.
-- autorizar
-  - int
-  - Indicador que indica si la línea de confianza está autorizada. 0 si la cuenta no está autorizada para transaccionar con el activo de ninguna manera. 1 si la cuenta está autorizada para transaccionar con el activo. 2 si la cuenta está autorizada para mantener órdenes, pero no para realizar otras transacciones.
-- fiduciario
-  - cadena
-  - La cuenta emisor, o cuenta origen en este caso.
-- fiduciario
-  - cadena
-  - La cuenta fideicomitente, o la cuenta que está siendo autorizada o no autorizada.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/120497059836067841"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/ac8dd0ddf1d047081c8e4c2a7ef9cc38a1a8af6c211184e1b16ebf2e32915d7f"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/120497059836067841/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=120497059836067841"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=120497059836067841"
-    }
-  },
-  "id": "120497059836067841",
-  "paging_token": "120497059836067841",
-  "transaction_successful": true,
-  "source_account": "GCRZQVBBDAWVOCO5R2NI34YR55RO2GQXPTDUE5OZESXGZRRTAEQLKEKN",
-  "type": "allow_trust",
-  "type_i": 7,
-  "created_at": "2020-02-03T14:30:52Z",
-  "transaction_hash": "ac8dd0ddf1d047081c8e4c2a7ef9cc38a1a8af6c211184e1b16ebf2e32915d7f",
-  "asset_type": "credit_alphanum4",
-  "asset_code": "LSV1",
-  "asset_issuer": "GCRZQVBBDAWVOCO5R2NI34YR55RO2GQXPTDUE5OZESXGZRRTAEQLKEKN",
-  "trustee": "GCRZQVBBDAWVOCO5R2NI34YR55RO2GQXPTDUE5OZESXGZRRTAEQLKEKN",
-  "trustor": "GDSYBYRG6NIBJWR7BLY72HYV7VM4A7WWHUJ45FI7H4Q2U2RPR3BB3CFR",
-  "authorize": true
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.mdx
deleted file mode 100644
index b75e3c1ea3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/begin-sponsoring-future-reserves.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Comenzar a patrocinar reservas futuras
-order: 160
----
-
-Iniciar un patrocinio.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- sponsored_id
-  - cadena
-  - El id de la cuenta que será patrocinada.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124922916260433921"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124922916260433921"
-    }
-  },
-  "id": "124922916260433921",
-  "paging_token": "124922916260433921",
-  "transaction_successful": true,
-  "source_account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA",
-  "type": "begin_sponsoring_future_reserves",
-  "type_i": 16,
-  "created_at": "2020-04-09T00:14:11Z",
-  "transaction_hash": "f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1",
-  "sponsored_id": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.mdx
deleted file mode 100644
index 750e211bad..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/bump-sequence.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Incrementar objeto de secuencia
-order: 130
----
-
-Incrementa el número de secuencia de la cuenta de origen, permitiéndole invalidar cualquier transacción con un número de secuencia menor.
-
-Consulta los [`errores de Incrementar Secuencia`](../../../errors/result-codes/operation-specific/bump-sequence.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- bump_to
-  - cadena
-  - El nuevo valor deseado para el número de secuencia de la cuenta de origen.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124922916260433921"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124922916260433921"
-    }
-  },
-  "id": "124922916260433921",
-  "paging_token": "124922916260433921",
-  "transaction_successful": true,
-  "source_account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA",
-  "type": "bump_sequence",
-  "type_i": 11,
-  "created_at": "2020-04-09T00:14:11Z",
-  "transaction_hash": "f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1",
-  "bump_to": "120192344968520085"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx
deleted file mode 100644
index 24e31910df..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Gestionar objeto de oferta de compra
-order: 60
----
-
-Crea, actualiza o elimina una oferta de compra para intercambiar activos. Una oferta de compra especifica una cierta cantidad del activo comprado que debe ser vendida a cambio de la cantidad mínima del activo vendido.
-
-Consulta los [`errores de Gestionar Oferta de Compra`](../../../errors/result-codes/operation-specific/manage-buy-offer.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- cantidad
-  - cadena
-  - La cantidad de `buying_asset` que la cuenta que realiza esta oferta está dispuesta a comprar.
-- precio
-  - cadena
-  - Cuántas unidades de `buying_asset` se necesitan para obtener 1 unidad de `selling_asset`. Un número que representa la forma decimal de `price_r`.
-- precio_r
-  - objeto
-  - Una representación precisa del precio de compra y venta de los activos en oferta.
-    - n
-      - número
-      - El numerador.
-    - d
-      - número
-      - El denominador.
-- tipo_de_activo_compra
-  - cadena
-  - El tipo del activo comprado. Puede ser `native`, `credit_alphanum4` o `credit_alphanum12`.
-- emisora_de_activo_compra
-  - cadena
-  - La dirección Stellar del emisor del activo comprado. Aparece si el `buying_asset_type` no es `native`.
-- código_de_activo_compra
-  - cadena
-  - El código del activo comprado. Aparece si el `buying_asset_type` no es `native`.
-- tipo_de_activo_venta
-  - cadena
-  - El tipo del activo vendido. Puede ser `native`, `credit_alphanum4` o `credit_alphanum12`.
-- emisora_de_activo_venta
-  - cadena
-  - La dirección Stellar del emisor del activo vendido. Aparece si el `selling_asset_type` no es `native`.
-- código_de_activo_venta
-  - cadena
-  - El código para el activo vendido. Aparece si el `selling_asset_type` no es `native`.
-- id_de_oferta
-  - cadena
-  - Un identificador único para esta oferta.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124893981065674756"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/3b41ec1411ed67ed47c96c34067c9fcfadf6e7cc013effa0b10f3df5ed758ffc"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124893981065674756/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124893981065674756"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124893981065674756"
-    }
-  },
-  "id": "124893981065674756",
-  "paging_token": "124893981065674756",
-  "transaction_successful": true,
-  "source_account": "GDT7WYNV6YBFJH3G6TX5K3ALBZY7A7A7CLIGXK4XZ6H5SROPS4UFGEMC",
-  "type": "manage_buy_offer",
-  "type_i": 12,
-  "created_at": "2020-04-08T14:03:03Z",
-  "transaction_hash": "3b41ec1411ed67ed47c96c34067c9fcfadf6e7cc013effa0b10f3df5ed758ffc",
-  "amount": "20.4521401",
-  "price": "0.0300003",
-  "price_r": {
-    "n": 9000190,
-    "d": 300003333
-  },
-  "buying_asset_type": "native",
-  "selling_asset_type": "credit_alphanum4",
-  "selling_asset_code": "EURT",
-  "selling_asset_issuer": "GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S",
-  "offer_id": "0"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx
deleted file mode 100644
index c9002b51c8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Cambiar Objeto de Confianza
-order: 90
----
-
-Crea, actualiza o elimina una línea de confianza de la cuenta de origen a un activo emitido de otra cuenta.
-
-Consulta los [`errores de Cambiar Confianza`](../../../errors/result-codes/operation-specific/change-trust.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- tipo_de_activo
-  - cadena
-  - El tipo de activo que se está confiando, uno de `nativo`, `credit_alphanum4`, `credit_alphanum12` o `fondos_de_liquidez`.
-- código_de_activo
-  - cadena
-  - La dirección Stellar del activo que se está confiando. (Solo presente para activos de crédito.)
-- emisor_de_activo
-  - cadena
-  - El código del activo que se está confiando. (Solo presente para activos de crédito.)
-- límite
-  - cadena
-  - Limita la cantidad de un activo que puede poseer la cuenta de origen.
-- fiduciario
-  - cadena
-  - La cuenta emisora. (Solo presente para activos de crédito.)
-- fiduciante
-  - cadena
-  - La cuenta de origen.
-- id_de_fondos_de_liquidez
-  - cadena
-  - El fondo de liquidez cuya línea de confianza se está modificando. (Solo presente para `asset_type == liquidity_pool_shares`.)
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/120192477935251457"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/ec4116595bdfa8c1039c40af425e497c91fcf387c2a2a0cfa1f3bf64733f1f23"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/120192477935251457/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=120192477935251457"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=120192477935251457"
-    }
-  },
-  "id": "120192477935251457",
-  "paging_token": "120192477935251457",
-  "transaction_successful": true,
-  "source_account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA",
-  "type": "change_trust",
-  "type_i": 6,
-  "created_at": "2020-01-29T19:46:55Z",
-  "transaction_hash": "ec4116595bdfa8c1039c40af425e497c91fcf387c2a2a0cfa1f3bf64733f1f23",
-  "asset_type": "credit_alphanum4",
-  "asset_code": "NGNT",
-  "asset_issuer": "GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD",
-  "limit": "922337203685.4775807",
-  "trustee": "GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD",
-  "trustor": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.mdx
deleted file mode 100644
index fd74329428..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/claim-claimable-balance.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Reclamar saldo reclamable
-order: 150
----
-
-Reclama un saldo reclamable.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATOS
-  - DESCRIPCIÓN
-- balance_id
-  - cadena
-  - El id del saldo reclamable.
-- reclamante
-  - cadena
-  - El id de la cuenta que reclamó el saldo.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124922916260433921"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124922916260433921"
-    }
-  },
-  "id": "124922916260433921",
-  "paging_token": "124922916260433921",
-  "transaction_successful": true,
-  "source_account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA",
-  "type": "claim_claimable_balance",
-  "type_i": 15,
-  "created_at": "2020-04-09T00:14:11Z",
-  "transaction_hash": "f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1",
-  "id": "000000000102030000000000000000000000000000000000000000000000000000000000",
-  "claimant": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/create-account.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/create-account.mdx
deleted file mode 100644
index 4c57f492d9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/create-account.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Crear objeto de cuenta
-order: 10
----
-
-Crea y financia una nueva cuenta con el saldo inicial especificado.
-
-Consulta los [`errores de crear cuentas`](../../../errors/result-codes/operation-specific/create-account.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- saldo_inicial
-  - cadena
-  - La cantidad de XLM a enviar a la cuenta recién creada.
-- financista
-  - cadena
-  - La cuenta que financia la nueva cuenta.
-- cuenta
-  - cadena
-  - Una nueva cuenta que está financiada.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/120192344791343105"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/120192344791343105/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=120192344791343105"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=120192344791343105"
-    }
-  },
-  "id": "120192344791343105",
-  "paging_token": "120192344791343105",
-  "transaction_successful": true,
-  "source_account": "GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU",
-  "type": "create_account",
-  "type_i": 0,
-  "created_at": "2020-01-29T19:43:59Z",
-  "transaction_hash": "ef0fe04ac3c7de7228ca2598886059868ad05c224a041e8b2d9ee2a8a9dd6894",
-  "starting_balance": "2.0000000",
-  "funder": "GBVFTZL5HIPT4PFQVTZVIWR77V7LWYCXU4CLYWWHHOEXB64XPG5LDMTU",
-  "account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
deleted file mode 100644
index 252b74d5df..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: Crear saldo reclamable
-order: 140
----
-
-Crea un nuevo saldo reclamable.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- activo
-  - cadena
-  - El activo disponible para ser reclamado en el [formulario SEP-11](https://github.com/stellar/stellar-protocol/blob/0c675fb3a482183dcf0f5db79c12685acf82a95c/ecosystem/sep-0011.md#values) `asset_code:issuing_address` o `nativo` (para XLM)
-- cantidad
-  - cadena
-  - La cantidad disponible para ser reclamada.
-- reclamantes
-  - array de objetos
-  - La lista de entradas que podrían reclamar el saldo reclamable.
-    - destino
-      - cadena
-      - El ID de la cuenta que puede reclamar el saldo.
-    - predicado
-      - objeto
-      - La condición que debe cumplirse para que `destino` pueda reclamar el saldo.
-        - incondicional
-          - booleano (opcional)
-          - Si es verdadero, significa que esta cláusula de la condición siempre se cumple.
-        - y
-          - array de objetos (opcional)
-          - El array siempre contendrá dos elementos que también son predicados. Esta cláusula de la condición se cumple si ambos de los dos elementos en el array se cumplen.
-        - o
-          - array de objetos (opcional)
-          - El array siempre contendrá dos elementos que también son predicados. Esta cláusula de la condición se cumple si al menos uno de los dos elementos en el array se cumple.
-        - no
-          - objeto (opcional)
-          - El valor también es un predicado. Esta cláusula de la condición se cumple si el valor _no_ se cumple.
-        - absBefore
-          - cadena (opcional)
-          - Una cadena formateada en ISO 8601 personalizada que representa una fecha límite para cuando se puede reclamar el saldo reclamable. Si el saldo es reclamado antes de la fecha, entonces esta cláusula de la condición se cumple. El formato de esta cadena de fecha es una extensión personalizada sobre el formato ISO 8601. Permite que los años estén fuera del rango 0000-9999. Las fechas se derivan de un valor de época Unix en el rango de un entero de 64 bits con signo. Esto significa que la fecha expresa un rango de calendario mucho más amplio de 292277026596 años en el futuro y -292471206707 años en el pasado. Este formato de extensión personalizada agregará un prefijo `'+'` a los valores que superen el año 9999 en el futuro y para los años que son anteriores al año 0 (A.C según el calendario gregoriano) se agregará un prefijo `'-'`. \
-            Aquí hay ejemplos de valores de cadenas de fechas que son posibles: \
-            `'2022-02-10T15:30:22Z'` \
-            `'+39121901036-03-29T15:30:22Z'` \
-            `'-7025-12-23T00:00:00Z'`
-        - absBeforeEpoch
-          - cadena (opcional)
-          - Un valor de época Unix en segundos que representa la misma fecha límite para cuando se puede reclamar el saldo reclamable. Es el mismo valor de fecha/hora que absBefore representa, solo expresado en segundos de época Unix integrales dentro del rango de un entero de 64 bits con signo.
-        - relBefore
-          - cadena (opcional)
-          - Una fecha límite relativa para cuando se puede reclamar el saldo reclamable. El valor representa el número de segundos desde el tiempo de cierre del ledger que creó el saldo reclamable.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124922916260433921"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124922916260433921"
-    }
-  },
-  "id": "124922916260433921",
-  "paging_token": "124922916260433921",
-  "transaction_successful": true,
-  "source_account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA",
-  "type": "create_claimable_balance",
-  "type_i": 14,
-  "created_at": "2020-04-09T00:14:11Z",
-  "transaction_hash": "f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1",
-  "asset": "NGNT:GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD",
-  "amount": "200.0000000",
-  "claimants": [
-    {
-      "destination": "GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML",
-      "predicate": {
-        "and": [
-          {
-            "or": [
-              {
-                "relBefore": "12"
-              },
-              {
-                "absBefore": "2020-08-26T11:15:39Z",
-                "absBeforeEpoch": "1598440539"
-              }
-            ]
-          },
-          {
-            "not": { "unconditional": true }
-          }
-        ]
-      }
-    }
-  ]
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.mdx
deleted file mode 100644
index d4f44bf613..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/end-sponsoring-future-reserves.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Finalizar el patrocinio de reservas futuras
-order: 170
----
-
-Finalizar un patrocinio.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- comenzar_patrocinador
-  - cadena
-  - El id de la cuenta que inició el patrocinio.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124922916260433921"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124922916260433921"
-    }
-  },
-  "id": "124922916260433921",
-  "paging_token": "124922916260433921",
-  "transaction_successful": true,
-  "source_account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA",
-  "type": "end_sponsoring_future_reserves",
-  "type_i": 17,
-  "created_at": "2020-04-09T00:14:11Z",
-  "transaction_hash": "f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1",
-  "begin_sponsor": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.mdx
deleted file mode 100644
index 9e5e20a134..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/extend-footprint-ttl.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Extender el objeto TTL de huella
-order: 230
----
-
-[Extiende](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#extend-footprint-ttl) el TTL para un conjunto dado de entradas de ledger.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- extender_a
-  - número
-  - El nuevo ledger live until que se aplicará a las entradas de ledger.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "id": "1109896858714113",
-  "paging_token": "1109896858714113",
-  "transaction_successful": true,
-  "source_account": "GBVAL7WM2G3NUTDIT5EYE4BMDRNLRQWI4RDGSVFCPXHPQRSSPEUQ2PNK",
-  "type": "extend_footprint_ttl",
-  "type_i": 25,
-  "created_at": "2024-02-22T10:50:50Z",
-  "transaction_hash": "1768d762bedf3129a00ec095d1aaed4c378dc3f55250758ed5008992b303303b",
-  "extend_to": 100
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.mdx
deleted file mode 100644
index e696e848f5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/invoke-host-function.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: Invocar objeto de función de host
-order: 220
----
-
-[Invoca](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#invoke-host-function) una función de contrato inteligente Soroban.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- función
-  - cadena
-  - El tipo de `InvokeHostFunctionOp`, que puede ser uno de `HostFunctionTypeHostFunctionTypeInvokeContract`, `HostFunctionTypeHostFunctionTypeCreateContract`, o `HostFunctionTypeHostFunctionTypeUploadContractWasm`.
-- parámetros
-  - arreglo
-  - Un arreglo de parámetros pasados a la función de contrato inteligente Soroban (solo presente cuando el tipo de `InvokeHostFunctionOp` es `HostFunctionTypeHostFunctionTypeInvokeContract`).
-    - tipo
-      - cadena
-      - El [tipo](../../../../../../../learn/fundamentals/contract-development/types/built-in-types.mdx) del parámetro de la función.
-    - valor
-      - cadena
-      - La codificación en base64 del valor XDR del parámetro.
-- dirección
-  - cadena
-  - La dirección del contrato recién creado (solo presente cuando el tipo de `InvokeHostFunctionOp` es `HostFunctionTypeHostFunctionTypeCreateContract`).
-- sal
-  - cadena
-  - La sal utilizada para crear el contrato (solo presente cuando el tipo de `InvokeHostFunctionOp` es `HostFunctionTypeHostFunctionTypeCreateContract`).
-- cambios_en_balance_de_activo
-  - arreglo
-  - Un arreglo de eventos de actualización de balance del [Stellar Asset Contract](../../../../../../../tokens/stellar-asset-contract) que ocurrieron como un efecto secundario de `InvokeHostFunctionOp` (solo presente cuando el tipo de `InvokeHostFunctionOp` es `HostFunctionTypeHostFunctionTypeInvokeContract` _y_ la invocación es sobre un Stellar Asset Contract).
-    - tipo_de_activo
-      - cadena
-      - El tipo de activo que se está enviando. Puede ser `nativo`, `credit_alphanum4`, o `credit_alphanum12`.
-    - código
-      - cadena
-      - El código del activo que se está enviando. Aparece si el `tipo_de_activo` no es `nativo`.
-    - emisor
-      - cadena
-      - La dirección Stellar del emisor del activo que se está enviando. Aparece si el `tipo_de_activo` no es `nativo`.
-    - tipo
-      - cadena
-      - El tipo del [evento de Stellar Asset Contract](../../../../../../../tokens/stellar-asset-contract). Puede ser uno de `transfer`, `mint`, `clawback`, o `burn`.
-    - desde
-      - cadena
-      - La dirección Stellar del remitente (puede ser un contrato o una cuenta Stellar). Este campo no está presente cuando el `tipo` es `mint`.
-    - a
-      - cadena
-      - La dirección Stellar del destinatario (puede ser un contrato o una cuenta Stellar). Este campo solo está presente cuando el `tipo` es `transfer` o `mint`.
-    - cantidad
-      - cadena
-      - La cantidad enviada.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "id": "1109896858714113",
-  "paging_token": "1109896858714113",
-  "transaction_successful": true,
-  "source_account": "GBVAL7WM2G3NUTDIT5EYE4BMDRNLRQWI4RDGSVFCPXHPQRSSPEUQ2PNK",
-  "type": "invoke_host_function",
-  "type_i": 24,
-  "created_at": "2024-02-22T10:50:50Z",
-  "transaction_hash": "1768d762bedf3129a00ec095d1aaed4c378dc3f55250758ed5008992b303303b",
-  "function": "HostFunctionTypeHostFunctionTypeInvokeContract",
-  "parameters": [
-    {
-      "value": "AAAAEgAAAAHJOCa1uNUk//1ibktaJMY8Q0o5+CSWzWTw16NBiWFiGA==",
-      "type": "Address"
-    },
-    {
-      "value": "AAAADwAAAAtzZXRfcmVjb3JkcwA=",
-      "type": "Sym"
-    },
-    {
-      "value": "AAAAEAAAAAEAAAACAAAAEAAAAAEAAAACAAAADwAAAAVPdGhlcgAAAAAAAA8AAAADVVNEAAAAABAAAAABAAAAAgAAAA8AAAAFT3RoZXIAAAAAAAAPAAAAA0VVUgA=",
-      "type": "Vec"
-    },
-    {
-      "value": "AAAAEAAAAAEAAAACAAAAEQAAAAEAAAACAAAADwAAAAVwcmljZQAAAAAAAAoAAAAAAAAAAAAAAAAAEcMIAAAADwAAAAl0aW1lc3RhbXAAAAAAAAAFAAAAAGXXJpwAAAARAAAAAQAAAAIAAAAPAAAABXByaWNlAAAAAAAACgAAAAAAAAAAAAAAAAAQXTQAAAAPAAAACXRpbWVzdGFtcAAAAAAAAAUAAAAAZdcmnA==",
-      "type": "Vec"
-    }
-  ],
-  "address": "",
-  "salt": "",
-  "asset_balance_changes": []
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.mdx
deleted file mode 100644
index 4cd73e1402..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-deposit.mdx
+++ /dev/null
@@ -1,113 +0,0 @@
----
-title: Objeto de Depósito en Fondos de Liquidez
-order: 200
----
-
-Depositar reservas de activos en un fondo de liquidez.
-
-Consulta la [operación `Depósito en Fondo de Liquidez`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#liquidity-pool-deposit) para parámetros, errores, etc.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- liquidity_pool_id
-  - cadena
-  - El fondo de liquidez asociado con este depósito
-- reserves_max
-  - arreglo
-  - Un arreglo de objetos que corresponden a la cantidad máxima de cada reserva que podría haberse depositado
-    - activo
-      - cadena
-      - El activo en forma canónica (`Código:Emisor`)
-    - cantidad
-      - cadena
-      - Un valor de punto flotante codificado como una cadena
-- min_price
-  - cadena
-  - Un valor de punto flotante codificado como una cadena que indica la tasa de cambio mínima para esta operación de depósito
-- min_price_r
-  - objeto
-  - Una representación precisa (fraccional) del precio de compra y venta de los activos ofrecidos.
-    - n
-      - número
-      - El numerador.
-    - d
-      - número
-      - El denominador.
-- max_price
-  - cadena
-  - Un valor de punto flotante codificado como una cadena que indica la tasa de cambio máxima para esta operación de depósito
-- max_price_r
-  - objeto
-  - Una representación precisa (fraccional) del precio de compra y venta de los activos ofrecidos.
-    - n
-      - número
-      - El numerador.
-    - d
-      - número
-      - El denominador.
-- reserves_deposited
-  - arreglo
-  - Un arreglo de objetos que representan cuánto de cada reserva terminó siendo realmente depositado en el fondo
-    - activo
-      - cadena
-      - El activo en forma canónica (`Código:Emisor`)
-    - cantidad
-      - cadena
-      - Un valor de punto flotante codificado como una cadena
-- shares_received
-  - cadena
-  - Un valor de punto flotante codificado como una cadena que representa el número de acciones del fondo recibidas por este depósito
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "id": "3697472920621057",
-  "paging_token": "3697472920621057",
-  "transaction_successful": true,
-  "source_account": "GBB4JST32UWKOLGYYSCEYBHBCOFL2TGBHDVOMZP462ET4ZRD4ULA7S2L",
-  "type": "liquidity_pool_deposit",
-  "type_i": 22,
-  "created_at": "2021-11-18T03:47:47Z",
-  "transaction_hash": "43ed5ce19190822ec080b67c3ccbab36a56bc34102b1a21d3ee690ed3bc23378",
-  "liquidity_pool_id": "abcdef",
-  "reserves_max": [
-    {
-      "asset": "JPY:GBVAOIACNSB7OVUXJYC5UE2D4YK2F7A24T7EE5YOMN4CE6GCHUTOUQXM",
-      "amount": "1000.0000005"
-    },
-    {
-      "asset": "EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S",
-      "amount": "3000.0000005"
-    }
-  ],
-  "min_price": "0.2680000",
-  "min_price_r": {
-    "n": 67,
-    "d": 250
-  },
-  "max_price": "0.3680000",
-  "max_price_r": {
-    "n": 73,
-    "d": 250
-  },
-  "reserves_deposited": [
-    {
-      "asset": "JPY:GBVAOIACNSB7OVUXJYC5UE2D4YK2F7A24T7EE5YOMN4CE6GCHUTOUQXM",
-      "amount": "983.0000005"
-    },
-    {
-      "asset": "EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S",
-      "amount": "2378.0000005"
-    }
-  ],
-  "shares_received": "1000"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.mdx
deleted file mode 100644
index 669c1366a6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/liquidity-pool-withdraw.mdx
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: Objeto de Retirada de Fondos de Liquidez
-order: 210
----
-
-Retira reservas de activos de un fondo de liquidez al canjear acciones del fondo.
-
-Consulta la operación [`Retirada de Fondos de Liquidez`](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#liquidity-pool-withdraw) para parámetros, errores, etc.
-
-<AttributeTable>
-
-- ATRIBUTE
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- liquidity_pool_id
-  - cadena
-  - El fondo de liquidez asociado a esta retirada de fondos
-- reserves_min
-  - arreglo
-  - Un arreglo de objetos que corresponden a la cantidad mínima de cada reserva que debería haber sido retirada
-    - activo
-      - cadena
-      - El activo en forma canónica (`Código:Emisor`)
-    - cantidad
-      - cadena
-      - Un valor de punto flotante codificado como cadena
-- acciones
-  - cadena
-  - El número de acciones que fueron canjeadas por esta operación de retirada de fondos
-- reserves_received
-  - arreglo
-  - Un arreglo de objetos que representan cuánto de cada reserva terminó siendo efectivamente retirada del fondo
-    - activo
-      - cadena
-      - El activo en forma canónica (`Código:Emisor`)
-    - cantidad
-      - cadena
-      - Un valor de punto flotante codificado como cadena
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "id": "3697472920621057",
-  "paging_token": "3697472920621057",
-  "transaction_successful": true,
-  "source_account": "GBB4JST32UWKOLGYYSCEYBHBCOFL2TGBHDVOMZP462ET4ZRD4ULA7S2L",
-  "type": "liquidity_pool_deposit",
-  "type_i": 22,
-  "created_at": "2021-11-18T03:47:47Z",
-  "transaction_hash": "43ed5ce19190822ec080b67c3ccbab36a56bc34102b1a21d3ee690ed3bc23378",
-  "liquidity_pool_id": "abcdef",
-  "reserves_max": [
-    {
-      "asset": "JPY:GBVAOIACNSB7OVUXJYC5UE2D4YK2F7A24T7EE5YOMN4CE6GCHUTOUQXM",
-      "amount": "1000.0000005"
-    },
-    {
-      "asset": "EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S",
-      "amount": "3000.0000005"
-    }
-  ],
-  "min_price": "0.2680000",
-  "min_price_r": {
-    "n": 67,
-    "d": 250
-  },
-  "max_price": "0.3680000",
-  "max_price_r": {
-    "n": 73,
-    "d": 250
-  },
-  "reserves_deposited": [
-    {
-      "asset": "JPY:GBVAOIACNSB7OVUXJYC5UE2D4YK2F7A24T7EE5YOMN4CE6GCHUTOUQXM",
-      "amount": "983.0000005"
-    },
-    {
-      "asset": "EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S",
-      "amount": "2378.0000005"
-    }
-  ],
-  "shares_received": "1000"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx
deleted file mode 100644
index ba56083bf1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/manage-data.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Gestionar Objeto de Datos
-order: 120
----
-
-Establecer, modificar o eliminar una entrada de datos (par de nombre/valor) para una cuenta.
-
-Consulta los [errores de `Gestionar Datos`](../../../errors/result-codes/operation-specific/manage-data.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- nombre
-  - cadena
-  - La clave para esta entrada de datos. Puede tener hasta 64 bytes de longitud. Si este es un nuevo `Nombre`, se agregará el par nombre/valor dado a la cuenta. Si este `Nombre` ya está presente, entonces se modificará el valor asociado.
-- valor
-  - cadena
-  - Si está presente, entonces este valor se establecerá en el DataEntry. Puede tener hasta 64 bytes de longitud. Si no está presente, entonces se eliminará el `Nombre` existente.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/121957408846438401"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/1e1b8f628c338a0306cbcb512bd89473a0c6b25df67ad77cfc1478437a575665"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/121957408846438401/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=121957408846438401"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=121957408846438401"
-    }
-  },
-  "id": "121957408846438401",
-  "paging_token": "121957408846438401",
-  "transaction_successful": true,
-  "source_account": "GCAXBKU3AKYJPLQ6PEJ6L47KOATCYCBJ2NFRGAK7FUUA2DCEUC265SU2",
-  "type": "manage_data",
-  "type_i": 10,
-  "created_at": "2020-02-25T17:47:32Z",
-  "transaction_hash": "1e1b8f628c338a0306cbcb512bd89473a0c6b25df67ad77cfc1478437a575665",
-  "name": "config.memo_required",
-  "value": "MQ=="
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.mdx
deleted file mode 100644
index 7ef4cb35ea..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/passive-sell-offer.mdx
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: Crear Objeto de Oferta de Venta Pasiva
-order: 70
----
-
-Crea una oferta que no consumirá una contraoferta que iguale exactamente esta oferta. Esto es útil para ofertas destinadas a ser intercambios 1:1 para pagos de ruta. Utiliza Gestionar Oferta de Venta para gestionar esta oferta después de usar esta operación para crearla.
-
-Consulta los [`errores de Crear Oferta de Venta Pasiva`](../../../errors/result-codes/operation-specific/create-passive-sell-offer.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- cantidad
-  - cadena
-  - La cantidad de `selling_asset` que la cuenta que hace esta oferta está dispuesta a vender.
-- precio
-  - cadena
-  - Cuántas unidades de `selling_asset` se necesitan para obtener 1 unidad de `buying_asset`. Un número que representa la forma decimal de `price_r`.
-- precio_r
-  - objeto
-  - Una representación precisa del precio de compra y venta de los activos en oferta.
-    - n
-      - número
-      - El numerador.
-    - d
-      - número
-      - El denominador.
-- tipo_de_activo_compra
-  - cadena
-  - El tipo para el activo de compra. Puede ser `native`, `credit_alphanum4` o `credit_alphanum12`.
-- emisor_de_activo_compra
-  - cadena
-  - La dirección Stellar del emisor del activo de compra. Aparece si el `tipo_de_activo_compra` no es `native`.
-- código_de_activo_compra
-  - cadena
-  - El código para el activo de compra. Aparece si el `tipo_de_activo_compra` no es `native`.
-- tipo_de_activo_venta
-  - cadena
-  - El tipo para el activo de venta. Puede ser `native`, `credit_alphanum4` o `credit_alphanum12`.
-- emisor_de_activo_venta
-  - cadena
-  - La dirección Stellar del emisor del activo de venta. Aparece si el `tipo_de_activo_venta` no es `native`.
-- código_de_activo_venta
-  - cadena
-  - El código para el activo de venta. Aparece si el `tipo_de_activo_venta` no es `native`.
-- id_de_oferta
-  - cadena
-  - Un identificador único para esta oferta.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124895183656849409"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/20afb7f9613efe9e851579190c80758ee101550e85740f71274c3eb3f0cb0418"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124895183656849409/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124895183656849409"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124895183656849409"
-    }
-  },
-  "id": "124895183656849409",
-  "paging_token": "124895183656849409",
-  "transaction_successful": true,
-  "source_account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA",
-  "type": "create_passive_sell_offer",
-  "type_i": 4,
-  "created_at": "2020-04-08T14:28:15Z",
-  "transaction_hash": "20afb7f9613efe9e851579190c80758ee101550e85740f71274c3eb3f0cb0418",
-  "amount": "1.0000000",
-  "price": "1.0000000",
-  "price_r": {
-    "n": 1,
-    "d": 1
-  },
-  "buying_asset_type": "credit_alphanum4",
-  "buying_asset_code": "USD",
-  "buying_asset_issuer": "GBNLJIYH34UWO5YZFA3A3HD3N76R6DOI33N4JONUOHEEYZYCAYTEJ5AK",
-  "selling_asset_type": "credit_alphanum4",
-  "selling_asset_code": "USD",
-  "selling_asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
deleted file mode 100644
index 341a337b54..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: Objeto de Pago por Ruta Estricto Recibir
-order: 30
----
-
-Envía un pago de una cuenta a otra a través de un camino en los libros de órdenes, comenzando como un activo y terminando como otro. Los pagos por ruta que son `Recibir Estricto` designan la cantidad de pago en el activo recibido.
-
-Consulta los [errores de `Pago por Ruta Estricto Recibir`](../../../errors/result-codes/operation-specific/path-payment-strict-receive.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- tipo_de_activo
-  - cadena
-  - El tipo de activo que se recibe. Puede ser `nativo`, `credito_alphanum4`, o `credito_alphanum12`.
-- codigo_de_activo
-  - cadena
-  - El código del activo que se recibe. Aparece si el `tipo_de_activo` no es `nativo`.
-- emisor_de_activo
-  - cadena
-  - La dirección Stellar del emisor del activo que se recibe. Aparece si el `tipo_de_activo` no es `nativo`.
-- de
-  - cadena
-  - La clave pública del remitente del pago.
-- a
-  - cadena
-  - La clave pública del destinatario del pago.
-- cantidad
-  - cadena
-  - Cantidad recibida designada en el activo de destino.
-- ruta
-  - array de objetos
-  - Los activos intermedios por los que pasa este camino.
-    - codigo_de_activo
-      - cadena
-      - El código para este activo intermedio.
-    - emisor_de_activo
-      - cadena
-      - La dirección Stellar del emisor del activo intermedio.
-    - tipo_de_activo
-      - cadena
-      - El tipo del activo intermedio. Puede ser `nativo`, `credito_alphanum4`, o `credito_alphanum12`.
-- cantidad_fuente
-  - cadena
-  - Cantidad enviada designada en el activo fuente.
-- maximo_fuente
-  - cadena
-  - La cantidad máxima a enviar designada en el activo fuente.
-- tipo_de_activo_fuente
-  - cadena
-  - El tipo del activo fuente. Puede ser `nativo`, `credito_alphanum4`, o `credito_alphanum12`.
-- codigo_de_activo_fuente
-  - cadena
-  - El código del activo fuente.
-- emisor_de_activo_fuente
-  - cadena
-  - La dirección Stellar del emisor del activo fuente.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124018825644490753"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/2624935eefedc195562623d982e501ba2a183382959fa0b9d03cf66dced3b332"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124018825644490753/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124018825644490753"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124018825644490753"
-    }
-  },
-  "id": "124018825644490753",
-  "paging_token": "124018825644490753",
-  "transaction_successful": true,
-  "source_account": "GBZH7S5NC57XNHKHJ75C5DGMI3SP6ZFJLIKW74K6OSMA5E5DFMYBDD2Z",
-  "type": "path_payment_strict_receive",
-  "type_i": 2,
-  "created_at": "2020-03-26T19:33:55Z",
-  "transaction_hash": "2624935eefedc195562623d982e501ba2a183382959fa0b9d03cf66dced3b332",
-  "asset_type": "credit_alphanum4",
-  "asset_code": "BRL",
-  "asset_issuer": "GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP",
-  "from": "GBZH7S5NC57XNHKHJ75C5DGMI3SP6ZFJLIKW74K6OSMA5E5DFMYBDD2Z",
-  "to": "GBZH7S5NC57XNHKHJ75C5DGMI3SP6ZFJLIKW74K6OSMA5E5DFMYBDD2Z",
-  "amount": "0.1000000",
-  "path": [
-    {
-      "asset_type": "credit_alphanum4",
-      "asset_code": "USD",
-      "asset_issuer": "GBUYUAI75XXWDZEKLY66CFYKQPET5JR4EENXZBUZ3YXZ7DS56Z4OKOFU"
-    },
-    {
-      "asset_type": "native"
-    }
-  ],
-  "source_amount": "0.0198773",
-  "source_max": "0.0198774",
-  "source_asset_type": "credit_alphanum4",
-  "source_asset_code": "USD",
-  "source_asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.mdx
deleted file mode 100644
index d3760f38f7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-send.mdx
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: Objeto de envío estricto de pago de rutas
-order: 40
----
-
-Envía un pago de una cuenta a otra a través de la ruta a través de los libros de órdenes, comenzando como un activo y terminando como otro. Los pagos de rutas que son `Envío Estricto` designan la cantidad del pago en el activo enviado.
-
-Consulta los [errores de `Envío Estricto de Pago de Rutas`](../../../errors/result-codes/operation-specific/path-payment-strict-send.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- tipo_de_activo
-  - cadena
-  - El tipo de activo que se está recibiendo. Puede ser `nativo`, `crédito_alphanum4` o `crédito_alphanum12`.
-- código_de_activo
-  - cadena
-  - El código del activo que se está recibiendo. Aparece si el `tipo_de_activo` no es `nativo`.
-- emisor_de_activo
-  - cadena
-  - La dirección Stellar del emisor del activo que se está recibiendo. Aparece si el `tipo_de_activo` no es `nativo`.
-- de
-  - cadena
-  - La clave pública del remitente del pago.
-- a
-  - cadena
-  - La clave pública del destinatario del pago.
-- cantidad
-  - cadena
-  - Cantidad recibida designada en el activo de destino.
-- ruta
-  - array de objetos
-  - Los activos intermedios que se atraviesan en esta ruta.
-    - código_de_activo
-      - cadena
-      - El código de este activo intermedio.
-    - emisor_de_activo
-      - cadena
-      - La dirección Stellar del emisor del activo intermedio.
-    - tipo_de_activo
-      - cadena
-      - El tipo del activo intermedio. Puede ser `nativo`, `crédito_alphanum4` o `crédito_alphanum12`.
-- cantidad_fuente
-  - cadena
-  - Cantidad enviada designada en el activo fuente.
-- mín_destino
-  - cadena
-  - La cantidad mínima del activo de destino que se espera recibir.
-- tipo_de_activo_fuente
-  - cadena
-  - El tipo del activo fuente. Puede ser `nativo`, `crédito_alphanum4` o `crédito_alphanum12`.
-- código_de_activo_fuente
-  - cadena
-  - El código del activo fuente. Aparece si el `tipo_de_activo` no es `nativo`.
-- emisor_de_activo_fuente
-  - cadena
-  - La dirección Stellar del emisor del activo fuente. Aparece si el `tipo_de_activo` no es `nativo`.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124624072438579201"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/2b863994825fe85b80bfdff433b348d5ce80b23cd9ee2a56dcd6ee1abd52c9f8"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124624072438579201/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124624072438579201"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124624072438579201"
-    }
-  },
-  "id": "124624072438579201",
-  "paging_token": "124624072438579201",
-  "transaction_successful": true,
-  "source_account": "GBZH7S5NC57XNHKHJ75C5DGMI3SP6ZFJLIKW74K6OSMA5E5DFMYBDD2Z",
-  "type": "path_payment_strict_send",
-  "type_i": 13,
-  "created_at": "2020-04-04T13:47:50Z",
-  "transaction_hash": "2b863994825fe85b80bfdff433b348d5ce80b23cd9ee2a56dcd6ee1abd52c9f8",
-  "asset_type": "credit_alphanum4",
-  "asset_code": "BRL",
-  "asset_issuer": "GDVKY2GU2DRXWTBEYJJWSFXIGBZV6AZNBVVSUHEPZI54LIS6BA7DVVSP",
-  "from": "GBZH7S5NC57XNHKHJ75C5DGMI3SP6ZFJLIKW74K6OSMA5E5DFMYBDD2Z",
-  "to": "GBZH7S5NC57XNHKHJ75C5DGMI3SP6ZFJLIKW74K6OSMA5E5DFMYBDD2Z",
-  "amount": "26.5544244",
-  "path": [
-    {
-      "asset_type": "credit_alphanum4",
-      "asset_code": "EURT",
-      "asset_issuer": "GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"
-    },
-    {
-      "asset_type": "native"
-    }
-  ],
-  "source_amount": "5.0000000",
-  "destination_min": "26.5544244",
-  "source_asset_type": "credit_alphanum4",
-  "source_asset_code": "USD",
-  "source_asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.mdx
deleted file mode 100644
index 3d45c5ebd8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/restore-footprint.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: Restaurar objeto de huella
-order: 240
----
-
-[Restaura](../../../../../../../learn/fundamentals/transactions/list-of-operations.mdx#restore-footprint) entradas archivadas y las hace accesibles.
-
-<ExampleResponse>
-
-```json
-{
-  "id": "1109896858714113",
-  "paging_token": "1109896858714113",
-  "transaction_successful": true,
-  "source_account": "GBVAL7WM2G3NUTDIT5EYE4BMDRNLRQWI4RDGSVFCPXHPQRSSPEUQ2PNK",
-  "type": "restore_footprint",
-  "type_i": 26,
-  "created_at": "2024-02-22T10:50:50Z",
-  "transaction_hash": "1768d762bedf3129a00ec095d1aaed4c378dc3f55250758ed5008992b303303b"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.mdx
deleted file mode 100644
index ba6eb7bd74..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/revoke-sponsorship.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Revocar Patrocino
-order: 190
----
-
-Revocar el patrocinio de una entrada del ledger.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATOS
-  - DESCRIPCIÓN
-- account_id
-  - string (opcional)
-  - El id de la cuenta que ya no está patrocinada.
-- claimable_balance_id
-  - string (opcional)
-  - El id del saldo reclamable que ya no está patrocinado.
-- data_account_id
-  - string (opcional)
-  - El id de la cuenta cuya entrada de datos ya no está patrocinada.
-- data_name
-  - string (opcional)
-  - El nombre de la entrada de datos que ya no está patrocinada.
-- offer_id
-  - string (opcional)
-  - El id de la oferta que ya no está patrocinada.
-- trustline_account_id
-  - string (opcional)
-  - El id de la cuenta cuya trustline ya no está patrocinada.
-- trustline_asset
-  - string (opcional)
-  - El activo de la trustline que ya no está patrocinado.
-- signer_account_id
-  - string (opcional)
-  - El id de la cuenta del firmante que ya no está patrocinado.
-- signer_key
-  - string (opcional)
-  - El tipo de firmante que ya no está patrocinado.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124922916260433921/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124922916260433921"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124922916260433921"
-    }
-  },
-  "id": "124922916260433921",
-  "paging_token": "124922916260433921",
-  "transaction_successful": true,
-  "source_account": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA",
-  "type": "revoke_sponsorship",
-  "type_i": 19,
-  "created_at": "2020-04-09T00:14:11Z",
-  "transaction_hash": "f94c338370839a598753221714de0b0193d4fc56ea369db6efe88f18669cc5a1",
-  "account_id": "GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx
deleted file mode 100644
index 6f16427725..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Gestionar objeto de oferta de venta
-order: 50
----
-
-Crea, actualiza o elimina una oferta de venta para intercambiar activos. Una oferta de venta especifica una cierta cantidad del activo en venta que debe ser vendida a cambio de la máxima cantidad del activo en compra.
-
-Consulta los [`errores de gestionar oferta de venta`](../../../errors/result-codes/operation-specific/manage-sell-offer.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- cantidad
-  - cadena
-  - La cantidad de `selling_asset` que la cuenta que hace esta oferta está dispuesta a vender.
-- precio
-  - cadena
-  - Cuántas unidades de `selling_asset` se necesitan para obtener 1 unidad de `buying_asset`. Un número que representa la forma decimal de `price_r`.
-- precio_r
-  - objeto
-  - Una representación precisa del precio de compra y venta de los activos en oferta.
-    - n
-      - número
-      - El numerador.
-    - d
-      - número
-      - El denominador.
-- tipo_de_activo_compra
-  - cadena
-  - El tipo del activo en compra. Puede ser `native`, `credit_alphanum4` o `credit_alphanum12`.
-- emisor_activo_compra
-  - cadena
-  - La dirección Stellar del emisor del activo en compra. Aparece si el `buying_asset_type` no es `native`.
-- código_activo_compra
-  - cadena
-  - El código del activo en compra. Aparece si el `buying_asset_type` no es `native`.
-- tipo_de_activo_venta
-  - cadena
-  - El tipo del activo en venta. Puede ser `native`, `credit_alphanum4` o `credit_alphanum12`.
-- emisor_activo_venta
-  - cadena
-  - La dirección Stellar del emisor del activo en venta. Aparece si el `selling_asset_type` no es `native`.
-- código_activo_venta
-  - cadena
-  - El código del activo en venta. Aparece si el `selling_asset_type` no es `native`.
-- id_de_oferta
-  - cadena
-  - Un identificador único para esta oferta.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/124892722640347138"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/ef8ffb54ff5990a686fda3ebfc07b8162f042ff0fcdb4f7ff141531e386f0a18"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/124892722640347138/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=124892722640347138"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=124892722640347138"
-    }
-  },
-  "id": "124892722640347138",
-  "paging_token": "124892722640347138",
-  "transaction_successful": true,
-  "source_account": "GCM4PT6XDZBWOOENDS6FOU22GJQLJPV2GC7VRVII4TFGZBA3ZXNM55SV",
-  "type": "manage_sell_offer",
-  "type_i": 3,
-  "created_at": "2020-04-08T13:36:39Z",
-  "transaction_hash": "ef8ffb54ff5990a686fda3ebfc07b8162f042ff0fcdb4f7ff141531e386f0a18",
-  "amount": "1336.0326986",
-  "price": "0.0559999",
-  "price_r": {
-    "n": 559999,
-    "d": 10000000
-  },
-  "buying_asset_type": "credit_alphanum4",
-  "buying_asset_code": "USD",
-  "buying_asset_issuer": "GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX",
-  "selling_asset_type": "native",
-  "offer_id": "0"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/set-options.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/set-options.mdx
deleted file mode 100644
index 1c86c71189..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/operations/object/set-options.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Configurar el objeto de opciones
-order: 80
----
-
-Establece las banderas de una cuenta, el destino de inflación, los firmantes y el dominio principal.
-
-Consulta los [errores de `Configurar opciones`](../../../errors/result-codes/operation-specific/set-options.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- clave_firmante
-  - cadena
-  - La clave pública del nuevo firmante.
-- peso_firmante
-  - número
-  - El peso del nuevo firmante. Puede ir de `1` a `255`.
-- peso_clave_maestra
-  - número
-  - El peso de la clave maestra. Puede ir de `1` a `255`.
-- umbral_bajo
-  - número
-  - El peso total para el umbral bajo.
-- umbral_medio
-  - número
-  - El peso total para el umbral medio.
-- umbral_alto
-  - número
-  - El peso total para el umbral alto.
-- dominio_principal
-  - cadena
-  - El dominio principal utilizado para el descubrimiento del archivo stellar.toml.
-- establecer_bandas
-  - arreglo
-  - El arreglo de valores numéricos de las banderas que se han establecido en esta operación. Las opciones incluyen `1` para `AUTH_REQUIRED_FLAG`, `2` para `AUTH_REVOCABLE_FLAG` y `4` para `AUTH_IMMUTABLE_FLAG`.
-- establecer_bandas_s
-  - arreglo
-  - El arreglo de valores de cadena de las banderas que se han establecido en esta operación. Las opciones incluyen `AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG` y `AUTH_IMMUTABLE_FLAG`.
-- borrar_bandas
-  - arreglo
-  - El arreglo de valores numéricos de las banderas que se han eliminado en esta operación. Las opciones incluyen `1` para `AUTH_REQUIRED_FLAG`, `2` para `AUTH_REVOCABLE_FLAG` y `4` para `AUTH_IMMUTABLE_FLAG`.
-- borrar_bandas_s
-  - arreglo
-  - El arreglo de valores de cadena de las banderas que se han eliminado en esta operación. Las opciones incluyen `AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG` y `AUTH_IMMUTABLE_FLAG`.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/102125410241826819"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/e020277cf755a1c29234d34f123f546a2c4805d7b4ca9303e253667b0ff4d846"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/102125410241826819/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=102125410241826819"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=102125410241826819"
-    }
-  },
-  "id": "102125410241826819",
-  "paging_token": "102125410241826819",
-  "transaction_successful": true,
-  "source_account": "GABMKJM6I25XI4K7U6XWMULOUQIQ27BCTMLS6BYYSOWKTBUXVRJSXHYQ",
-  "type": "set_options",
-  "type_i": 5,
-  "created_at": "2019-05-08T21:20:34Z",
-  "transaction_hash": "e020277cf755a1c29234d34f123f546a2c4805d7b4ca9303e253667b0ff4d846",
-  "home_domain": "www.stellar.org"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/payments/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/payments/README.mdx
deleted file mode 100644
index 43247cf1ce..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/payments/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Pagos
-order: 0
----
-
-Los pagos son objetos que representan la transferencia de saldo de una dirección a otra. Los pagos se envían a la red Stellar agrupados en una transacción.
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                           |
-| ------- | ----------------------------------------- |
-| OBTENER | [/pagos](../../list-all-payments.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/payments/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/payments/object.mdx
deleted file mode 100644
index b39b411d3e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/payments/object.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: El Objeto de Pago
-order: 20
----
-
-Envía una cantidad en un activo específico a una cuenta de destino.
-
-Consulta los [`Payment` errores](../../errors/result-codes/operation-specific/payment.mdx).
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATOS
-  - DESCRIPCIÓN
-- tipo_de_activo
-  - cadena
-  - El tipo de activo que se envía. Puede ser `nativo`, `credit_alphanum4` o `credit_alphanum12`.
-- código_de_activo
-  - cadena
-  - El código del activo que se envía. Aparece si el `tipo_de_activo` no es `nativo`.
-- emisor_de_activo
-  - cadena
-  - La dirección Stellar del emisor del activo enviado. Aparece si el `tipo_de_activo` no es `nativo`.
-- de
-  - cadena
-  - La clave pública del remitente del pago.
-- a
-  - cadena
-  - La clave pública del destinatario del pago.
-- cantidad
-  - cadena
-  - Cantidad enviada.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/operations/122511124621283329"
-    },
-    "transaction": {
-      "href": "https://horizon-testnet.stellar.org/transactions/452a180790caf4dbe658d996316cd727ce5573f5f0a77790da540cc49214fe80"
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/operations/122511124621283329/effects"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=122511124621283329"
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=122511124621283329"
-    }
-  },
-  "id": "122511124621283329",
-  "paging_token": "122511124621283329",
-  "transaction_successful": true,
-  "source_account": "GCAXBKU3AKYJPLQ6PEJ6L47KOATCYCBJ2NFRGAK7FUUA2DCEUC265SU2",
-  "type": "payment",
-  "type_i": 1,
-  "created_at": "2020-03-04T22:46:47Z",
-  "transaction_hash": "452a180790caf4dbe658d996316cd727ce5573f5f0a77790da540cc49214fe80",
-  "asset_type": "credit_alphanum4",
-  "asset_code": "NGNT",
-  "asset_issuer": "GAWODAROMJ33V5YDFY3NPYTHVYQG7MJXVJ2ND3AOGIHYRWINES6ACCPD",
-  "from": "GCAXBKU3AKYJPLQ6PEJ6L47KOATCYCBJ2NFRGAK7FUUA2DCEUC265SU2",
-  "to": "GC2QCKFI3DOBEYVBONPVNA2PMLU225IKKI6XPENMWR2CTWSFBAOU7T34",
-  "amount": "5.0000000"
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/trades/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/trades/README.mdx
deleted file mode 100644
index c11c0bbcb1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/trades/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Comerciar
-order: 0
----
-
-Cuando una oferta se cumple total o parcialmente, ocurre un comercio. Los comercios también pueden ser causados por pagos de ruta exitosos, ya que los pagos de ruta implican cumplir ofertas.
-
-Un comercio ocurre entre dos partes—`base` y `contraparte`. Cuál es cuál es arbitrario o determinado por la consulta que llama.
-
-Aprende más sobre [operaciones](../../../../../../learn/glossary.mdx#decentralized-exchange) con intercambio descentralizado.
-
-<EndpointsTable title="Puntos finales">
-
-|         |                                         |
-| ------- | --------------------------------------- |
-| OBTENER | [/trades](../../get-all-trades.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/trades/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/trades/object.mdx
deleted file mode 100644
index 30823bea4f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/trades/object.mdx
+++ /dev/null
@@ -1,119 +0,0 @@
----
-title: El Objeto de Comercio
-order: 10
----
-
-Cuando Horizon devuelve información sobre un comercio, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATOS
-  - DESCRIPCIÓN
-- id
-  - cadena
-  - Un identificador único para este comercio.
-- token_de_paginación
-  - número
-  - Un valor de cursor para usar en [paginación](../../structure/pagination/README.mdx).
-- hora_de_cierre_del_libro
-  - cadena
-  - Una cadena formateada en ISO 8601 de cuándo se cerró el ledger con este comercio.
-- cuenta_base
-  - cadena (opcional)
-  - El ID de cuenta de la parte base para este comercio.
-- id_de_oferta_base
-  - cadena (opcional)
-  - El ID de la oferta base. Si esta oferta fue consumida inmediata y completamente, este será un ID sintético.
-- id_de_pool_de_liquidez_base
-  - cadena (opcional)
-  - El ID del fondo de liquidez base. Si este comercio se ejecutó contra un fondo de liquidez.
-- monto_base
-  - cadena
-  - La cantidad del activo base que fue transferido de `base_account` a `counter_account`.
-- tipo_de_activo_base
-  - cadena
-  - El tipo del activo base. Puede ser `native`, `credit_alphanum4`, o `credit_alphanum12`.
-- código_de_activo_base
-  - cadena
-  - El código del activo base.
-- emisor_de_activo_base
-  - cadena
-  - La dirección Stellar del emisor del activo base.
-- cuenta_contraparte
-  - cadena (opcional)
-  - El ID de cuenta de la parte base para este comercio.
-- id_de_oferta_contraparte
-  - cadena (opcional)
-  - El ID de la oferta en contra. Si esta oferta fue consumida inmediata y completamente, este será un ID sintético.
-- id_de_pool_de_liquidez_contraparte
-  - cadena (opcional)
-  - El ID del fondo de liquidez en contra. Si este comercio se ejecutó contra un fondo de liquidez.
-- monto_contraparte
-  - cadena
-  - La cantidad del activo en contra que fue transferido de `counter_account` a `base_account`.
-- tipo_de_activo_contraparte
-  - cadena
-  - El tipo del activo en contra. Puede ser `native`, `credit_alphanum4`, o `credit_alphanum12`.
-- código_de_activo_contraparte
-  - cadena
-  - El código del activo en contra.
-- emisor_de_activo_contraparte
-  - cadena
-  - La dirección Stellar del emisor del activo en contra.
-- precio
-  - objeto
-  - Un objeto de un numerador y un denominador que representa el precio de la oferta original. Para derivar el precio, divide `n` entre `d`. `n` y `d` están representados como cadenas porque pueden ser enteros de 64 bits.
-    - n
-      - cadena
-      - El numerador.
-    - d
-      - cadena
-      - El denominador.
-- base_es_vendedor
-  - booleano
-  - Indica qué parte es el vendedor.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": ""
-    },
-    "base": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GA23DVJUJVXUQ45SKQMZR7KH2ZOOBFWGWSEXHCT7VVKP2TYIMCQTQGNQ"
-    },
-    "counter": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GAFGG7CRFRCJLBHGI5L4IZD4QYR4GDX5NKB46CE4KZMNBILBTP3L4M75"
-    },
-    "operation": {
-      "href": "https://horizon-testnet.stellar.org/operations/100089067462524929"
-    }
-  },
-  "id": "100089067462524929-0",
-  "paging_token": "100089067462524929-0",
-  "ledger_close_time": "2019-04-07T11:30:03Z",
-  "offer_id": "79502917",
-  "base_offer_id": "4711775085889912833",
-  "base_account": "GA23DVJUJVXUQ45SKQMZR7KH2ZOOBFWGWSEXHCT7VVKP2TYIMCQTQGNQ",
-  "base_amount": "99.9999996",
-  "base_asset_type": "native",
-  "counter_offer_id": "79502917",
-  "counter_account": "GAFGG7CRFRCJLBHGI5L4IZD4QYR4GDX5NKB46CE4KZMNBILBTP3L4M75",
-  "counter_amount": "11.4722884",
-  "counter_asset_type": "credit_alphanum4",
-  "counter_asset_code": "EURT",
-  "counter_asset_issuer": "GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S",
-  "base_is_seller": false,
-  "price": {
-    "n": "10000000",
-    "d": "87166567"
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/transactions/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/transactions/README.mdx
deleted file mode 100644
index 084b9aa233..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/transactions/README.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Transacciones
-order: 0
----
-
-:::info
-
-El meta de transacción `result_meta_xdr` será eliminado de la API Horizon alojada por SDF (`horizon.stellar.org`) en el tercer trimestre de 2024. En lugar de usar Horizon para acceder a los metadatos de las transacciones, los desarrolladores pueden acceder a ellos mediante el punto final [`getTransactions`](../../../../rpc/api-reference/methods/getTransactions.mdx) en el RPC de Stellar.
-
-:::
-
-Las transacciones son comandos que modifican el estado del ledger y consisten en una o más operaciones.
-
-Obtén más información sobre [transacciones](../../../../../../learn/glossary.mdx#transaction).
-
-<EndpointsTable title="Puntos finales">
-
-|          |                                                                                              |
-| -------- | -------------------------------------------------------------------------------------------- |
-| OBTENER  | [/transactions/:transaction_id](../../retrieve-a-transaction.api.mdx)                        |
-| OBTENER  | [/transactions/:transaction_id/operations](../../retrieve-a-transactions-operations.api.mdx) |
-| OBTENER  | [/transactions/:transaction_id/effects](../../retrieve-a-transactions-effects.api.mdx)       |
-| OBTENER  | [/transactions](../../list-all-transactions.api.mdx)                                         |
-| PUBLICAR | [/transactions](../../submit-a-transaction.api.mdx)                                          |
-| PUBLICAR | [/transactions_async](../../submit-async-transaction.api.mdx)                                |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/transactions/object.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/transactions/object.mdx
deleted file mode 100644
index 44bf12a1ea..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/resources/transactions/object.mdx
+++ /dev/null
@@ -1,161 +0,0 @@
----
-title: El Objeto de Transacción
-order: 10
----
-
-:::info
-
-La meta de transacción `result_meta_xdr` será eliminada de la API de Horizon hospedada en SDF (`horizon.stellar.org`) en el tercer trimestre de 2024. En lugar de usar Horizon para acceder a los metadatos de transacción, los desarrolladores podrían acceder a ellos mediante el endpoint [`getTransactions`](../../../../rpc/api-reference/methods/getTransactions.mdx) en el RPC de Stellar.
-
-:::
-
-Cuando Horizon devuelve información sobre una transacción, utiliza el siguiente formato:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- id
-  - cadena
-  - Un identificador único para esta transacción.
-- paging_token
-  - número
-  - Un valor de cursor para usar en la [paginación](../../structure/pagination/README.mdx).
-- exitoso
-  - booleano
-  - Indica si esta transacción fue exitosa o no.
-- hash
-  - cadena
-  - Un hash SHA-256 codificado en hexadecimal de la forma codificada en [XDR](../../../../../../learn/fundamentals/data-format/xdr.mdx) de esta transacción.
-- ledger
-  - número
-  - El número de secuencia del ledger en el cual se incluyó esta transacción.
-- created_at
-  - cadena ISO8601
-  - La fecha en que se creó esta transacción.
-- source_account
-  - cadena
-  - La cuenta que origina la transacción.
-- source_account_sequence
-  - cadena
-  - El número de secuencia de la cuenta que esta transacción consumió.
-- fee_charged
-  - número
-  - La tarifa (en [stroops](../../../../../../learn/fundamentals/lumens.mdx)) pagada por la cuenta fuente para aplicar esta transacción al ledger.
-- max_fee
-  - número
-  - La tarifa máxima (en [stroops](../../../../../../learn/fundamentals/lumens.mdx)) que la cuenta fuente estaba dispuesta a pagar.
-- operation_count
-  - número
-  - El número de operaciones contenidas dentro de esta transacción.
-- envelope_xdr
-  - cadena
-  - Una cadena codificada en base64 del `TransactionEnvelope` de este XDR para esta transacción.
-- result_xdr
-  - cadena
-  - Una cadena codificada en base64 del `TransactionResult` de este XDR para esta transacción.
-- result_meta_xdr
-  - cadena
-  - **_[Para ser desaprobada en el tercer trimestre]_** Una cadena codificada en base64 de la estructura `TransactionMeta` para esta transacción
-- fee_meta_xdr
-  - cadena
-  - Una cadena codificada en base64 de la estructura `LedgerEntryChanges` producida por las tarifas de esta transacción.
-- memo
-  - cadena
-  - El memo opcional adjunto a una transacción.
-- memo_type
-  - cadena
-  - El tipo de memo. Los valores potenciales incluyen `MEMO_TEXT`, `MEMO_ID`, `MEMO_HASH`, `MEMO_RETURN`.
-- firmas
-  - cadena
-  - Un arreglo de firmas utilizadas para firmar esta transacción.
-- preconditions
-  - objeto
-  - Un conjunto de precondiciones de transacción que afectan su validez.
-    - time_bounds
-      - objeto
-      - El rango de tiempo para el cual esta transacción es válida, con límites como marcas de tiempo UNIX sin firmar de 64 bits
-        - min_time
-          - cadena
-          - el límite inferior
-        - max_time
-          - cadena
-          - el límite superior
-    - ledger_bounds
-      - objeto
-      - El rango de ledger para el cual esta transacción es válida, en forma de enteros sin firmar de 32 bits.
-        - min_ledger
-          - número
-          - el límite inferior
-        - max_ledger
-          - número
-          - el límite superior
-    - min_account_sequence
-      - cadena
-      - Contiene un entero positivo firmado de 64 bits que representa el número de secuencia de la mínima cuenta fuente para la cual la transacción es válida.
-    - min_account_sequence_age
-      - número
-      - La duración mínima de tiempo (en segundos como un entero sin firmar de 64 bits) que debe haber pasado desde que cambió el número de secuencia de la cuenta fuente para que la transacción sea válida.
-    - min_account_sequence_ledger_gap
-      - número
-      - Un entero sin firmar de 32 bits que representa el número mínimo de ledgers que deben haberse cerrado desde que cambió el número de secuencia de la cuenta fuente para que la transacción sea válida.
-    - extra_signers
-      - arreglo de cadenas
-      - La lista de hasta dos signatarios adicionales que deben tener las firmas correspondientes para que esta transacción sea válida.
-
-</AttributeTable>
-
-<ExampleResponse>
-
-```json
-{
-  "memo": "298424",
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/transactions/132c440e984ab97d895f3477015080aafd6c4375f6a70a87327f7f95e13c4e31"
-    },
-    "account": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GCO2IP3MJNUOKS4PUDI4C7LGGMQDJGXG3COYX3WSB4HHNAHKYV5YL3VC"
-    },
-    "ledger": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/27956256"
-    },
-    "operations": {
-      "href": "https://horizon-testnet.stellar.org/transactions/132c440e984ab97d895f3477015080aafd6c4375f6a70a87327f7f95e13c4e31/operations{?cursor,limit,order}",
-      "templated": true
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/transactions/132c440e984ab97d895f3477015080aafd6c4375f6a70a87327f7f95e13c4e31/effects{?cursor,limit,order}",
-      "templated": true
-    },
-    "precedes": {
-      "href": "https://horizon-testnet.stellar.org/transactions?order=asc\u0026cursor=120071205238677504"
-    },
-    "succeeds": {
-      "href": "https://horizon-testnet.stellar.org/transactions?order=desc\u0026cursor=120071205238677504"
-    }
-  },
-  "id": "132c440e984ab97d895f3477015080aafd6c4375f6a70a87327f7f95e13c4e31",
-  "paging_token": "120071205238677504",
-  "successful": true,
-  "hash": "132c440e984ab97d895f3477015080aafd6c4375f6a70a87327f7f95e13c4e31",
-  "ledger": 27956256,
-  "created_at": "2020-01-27T22:13:17Z",
-  "source_account": "GCO2IP3MJNUOKS4PUDI4C7LGGMQDJGXG3COYX3WSB4HHNAHKYV5YL3VC",
-  "source_account_sequence": "64034663849209932",
-  "fee_charged": 100,
-  "max_fee": 100,
-  "operation_count": 1,
-  "envelope_xdr": "AAAAAJ2kP2xLaOVLj6DRwX1mMyA0mubYnYvu0g8OdoDqxXuFAAAAZADjfzAACzBMAAAAAQAAAAAAAAAAAAAAAF4vYIYAAAABAAAABjI5ODQyNAAAAAAAAQAAAAAAAAABAAAAAKdeYELovtcnTxqPEVsdbxHLMoMRalZsK7lo/+3ARzUZAAAAAAAAAADUFJPYAAAAAAAAAAHqxXuFAAAAQBpLpQyh+mwDd5nDSxTaAh5wopBBUaSD1eOK9MdiO+4kWKVTqSr/Ko3kYE/+J42Opsewf81TwINONPbY2CtPggE=",
-  "result_xdr": "AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=",
-  "result_meta_xdr": "AAAAAQAAAAIAAAADAaqUIAAAAAAAAAAAnaQ/bEto5UuPoNHBfWYzIDSa5tidi+7SDw52gOrFe4UAAkRg8uGCXADjfzAACzBLAAAAAAAAAAEAAAAAnaQ/bEto5UuPoNHBfWYzIDSa5tidi+7SDw52gOrFe4UAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAaqUIAAAAAAAAAAAnaQ/bEto5UuPoNHBfWYzIDSa5tidi+7SDw52gOrFe4UAAkRg8uGCXADjfzAACzBMAAAAAAAAAAEAAAAAnaQ/bEto5UuPoNHBfWYzIDSa5tidi+7SDw52gOrFe4UAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBqoicAAAAAAAAAACnXmBC6L7XJ08ajxFbHW8RyzKDEWpWbCu5aP/twEc1GQAAAAAAmwWMAaVkEgAAAC0AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqpQgAAAAAAAAAACnXmBC6L7XJ08ajxFbHW8RyzKDEWpWbCu5aP/twEc1GQAAAADUr5lkAaVkEgAAAC0AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAMBqpQgAAAAAAAAAACdpD9sS2jlS4+g0cF9ZjMgNJrm2J2L7tIPDnaA6sV7hQACRGDy4YJcAON/MAALMEwAAAAAAAAAAQAAAACdpD9sS2jlS4+g0cF9ZjMgNJrm2J2L7tIPDnaA6sV7hQAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqpQgAAAAAAAAAACdpD9sS2jlS4+g0cF9ZjMgNJrm2J2L7tIPDnaA6sV7hQACRGAezO6EAON/MAALMEwAAAAAAAAAAQAAAACdpD9sS2jlS4+g0cF9ZjMgNJrm2J2L7tIPDnaA6sV7hQAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==",
-  "fee_meta_xdr": "AAAAAgAAAAMBqpQYAAAAAAAAAACdpD9sS2jlS4+g0cF9ZjMgNJrm2J2L7tIPDnaA6sV7hQACRGDy4YLAAON/MAALMEsAAAAAAAAAAQAAAACdpD9sS2jlS4+g0cF9ZjMgNJrm2J2L7tIPDnaA6sV7hQAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBqpQgAAAAAAAAAACdpD9sS2jlS4+g0cF9ZjMgNJrm2J2L7tIPDnaA6sV7hQACRGDy4YJcAON/MAALMEsAAAAAAAAAAQAAAACdpD9sS2jlS4+g0cF9ZjMgNJrm2J2L7tIPDnaA6sV7hQAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==",
-  "memo_type": "text",
-  "signatures": [
-    "GkulDKH6bAN3mcNLFNoCHnCikEFRpIPV44r0x2I77iRYpVOpKv8qjeRgT/4njY6mx7B/zVPAg0409tjYK0+CAQ=="
-  ]
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-claimable-balance.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-claimable-balance.api.mdx
deleted file mode 100644
index 8df656332e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-claimable-balance.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-claimable-balance
-title: "Retrieve a Claimable Balance"
-description: "The single claimable balance endpoint provides information on a claimable balance."
-sidebar_label: "Retrieve a Claimable Balance"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWVlvGzkS/isFvuRA6/KRjfWy69iO440n9tpOZjaOYFBkSc2YTXZIthSPoP++KHa31DqCeIKZRYDpFxtm3az6ilWescDHnvVv2ZHmKuNDjfCKa24EejZImEQvnMqDsob12U2K4JUZawSxIB+W5IBG5laZALmzEyXRgzIj6zJOzGAN8E2mNkuYzdFFmjPJ+uwKg1M4wcOFPZU5LGE5dzzDgI4MnjHDM2R9thB6Vwm9U5IlTJHBOQ8pS5jDL4VyKFk/uALXvTqEwqgvBYKSaIIaKXQwsg5Cqvx2k71IMeOsP2PhIScbfHDKjNl8PiBlPrfGo6fznW6XfqwqvC6EQO9ZwoQ1AU0gEp7nWokYiM5nT3SzTT12+BlFoFA4CltQpZY7rcy9/z6dRz36PlXqcLTpW8LKy2R9RtrYPGEBs1zzQHFdUA+t1cgNm8+bYb8thQ4SFlTQ2JCxuP1HmP9/NSw4bjwXP59pa0TxTlfiuGb7YJ4wJbcZV8tVkizj3mPYktMJ45ktzPajmOrWbT3T3Ie7zEqqKHmnUY7xMYRBUVlvIStL0YTmdXDn+ANVe8DsEdck0QdleFmHmwHJeQjoqERPbw9bH7utg8Fsf3/eCBWX0lHpzkkySipY/L5abuSP27wS3T/I61C/wpF12wPKh/4xpye5Fek2sKNUNDZ834zCCGukorBzvS3xk7/c0upL2EjHhregUSYgJSbdKB8rM74L9h63pMd64cUus8JS19CiYr5RA1szvlHnG61vnjD8yrNcl+H8do/sz9iE6wJXm0IN+yVIsTSE3Pc7ndQ69bs1rYA+GAxtH1Br7trWjTsbTdV3uvXX6+50d7s//G2i/s9hV2dp1OyfonDeukSrTIXEOokuosASvOkhsaVL/CSuNM16rDNVm2B/lhHr1fGnSq6aFSMsn+Cy4vqs120vyRot43YN/dnp0e7R3uHbq1f/OX9z8e+9/fd7v53u7p9cf/j16vjk6NeL/d/Oj0//e3h88eL48mr3/B9vz44/vP/ll3O2Bv0R3G9LnL5dgVzW22HzZNZEL7bT3em2ui9bOy9uer1+b7+/e/CRbUIY6+0fvNzb6+7vHrD5gIRUQLsGpeXNDeLDc3u/3Xm51+sdHOxvb7OVPTvRnoP+zkG/9+IjW4BlhiG1lBTjCGvxOd1n21J3tu0ZTmnm0U3qF3vh9OOKg22bPG5KOniHYWrdfQztdomjIhQOHyPzdU0JppY6oNlhZGMDqAD5TSmXJYxcKbm77W67R/4VWcbdw5JqOf9wA29ubi7h8PIMggXJAwdlIKQI16VdtdY2nAVQZow+EJsEh60YOB+pI2furCwEShg+bBNBkjnNLRmElAdQHpB7mmWCBWGNLzKsWfkEHR8jNGYOcKhjLRE50eTo4uPVCGxZp9AElKUhDnOHHk0owRIKXxpVG3RkHbbhhqYn8rzhx9ApOUYYYpgiGlJfervKeeksvSI8aHWPMOVaY/AJSBRoguNa/Y4S8KtIOQUsiRIiHoDyvkAXLYL6NoIFXwwzFaAJigl8KdA90BVxIQg66vkuAevAB4c8A5ygqe1ocpPQJWd7I7P+7plw27zQwdO6PCVOUFOX9SuNsDK7I6zDlrESn/2tsueT+WRqdYIbGCIdoadYThQH8f7qPAEOQ2enHl3UYA2CHcWoLGJ9ffzWfzfW0grfCdZq3/Hy3lOkLTikdIrShKVX5lcVHkj+gy0cZRsFNIEpgkNhswyNpKMYKG5IMSjjA3JJTBm/V2YMUjkUId6h4Fr76Ge81nGhJEJZMUP0kNppDInMlFE+oIM6xWM61rEhFXHR9NThqEzm6P/xwtMn8Erb8TIG0+l01fkFZWuo7bjDWwanLV+YFnWhFFtV/3gW1z/eUplwcT92tjCSNlhr1VDmjhOpCihC4bgGlVHNYxZvPt6Q8pDxz9ZB1TpgWGT5sza8tm5lQcaHtghQmUgBrPQtUsNKHHKPCYgUxT0QddN/UgmnFNplAMYqpMWwLWzWqeLQGdvOUNthJ+MU6Q6Vl6L+XbneoXHIGa7LTDl9f3Z8cvf64uru+OTDyfnF5cnVdTuTz+Jllg8WSoshjpVJQIUnHqbWhRQcqhBf02YcrSSQUNFEFKlFWaPfLRUtvLPyR2ACpBVFVsNPH54/nyJIC8YG2kZa5xFcYQwZUYeRLrQEKQ6UT5JrKqYmhiwy7fnzEh7Q5ygU1/ohio68dxOulYwO3m10PqTCcAhhasEjrS0DlZYR6EwFORKFLXJdxScjkFZZbl3gJsT0G9oYRq34UGmqR+JqJF97pTCo9jJu+JjWrpR6U5NAzh3KlrRTs0g+O1p11eZBZRESSWfFSZBHgGhHYBClh6dTfKI1NOpOeeAeOHxiRzyPzYLEfWKL2FGKxCHDZf5idF2mWeOp1rzZSNSyo1aVjdVilIv44q3WvLXZzXR/TYVZvueTtafg6sMPM67iKWpt/9U8o/WTEmg8NnQd5lykCDttmiGWW+HFSas8WWqswIbH0+hTJdR3zs+OTt5dnxBLOw2ZjnuE3PqQcdNQWc/0wGFjE7/+vpgt98Z/zUq+WnwE/Bo6ueYqbmiit7NqBrjdXLvT4rG/dRk/SFhqfSCu2Yww7L3T8zn9ObZR1r8dJGzCnSLGclJTnn6XrD/i2q9v7Jv+P72qVjLP4I/v8bf6WW/aDO3Zqm0KYwm7x4dv/beBJjSWIpdYzoAl6aEQmIeGkI0VP80aixHr9OSGzef/AyBdyX0=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Claimable Balance"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/claimable_balances/{claimable_balance_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single claimable balance endpoint provides information on a claimable balance.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"claimable_balance_id","in":"path","required":true,"description":"A unique identifier for this claimable balance.","schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","operations","transactions"]},"id":{"type":"string","title":"id"},"asset":{"type":"string"},"amount":{"type":"string"},"sponsor":{"type":"string"},"last_modified_ledger":{"type":"string"},"last_modified_time":{"type":"string"},"claimants":{"type":"array","items":{"type":"object","properties":{"destination":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"predicate":{"type":"object","properties":{"and":{"type":"array","items":{"type":"object","properties":{"or":{"type":"array","items":{"type":"object","properties":{"relBefore":{"type":"string"},"absBefore":{"type":"string"},"absBeforeEpoch":{"type":"string"}}}},"not":{"type":"object","properties":{"unconditional":{"type":"boolean"},"relBefore":{"type":"string"},"absBefore":{"type":"string"},"absBeforeEpoch":{"type":"string"}}}}}}}}}}},"flags":{"type":"integer"},"paging_token":{"type":"string"}},"required":["id","paging_token","asset","amount","last_modified_ledger","last_modified_time"],"title":"ClaimableBalance"},"examples":{"RetrieveAClaimableBalance":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000"},"operations":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000/operations{?cursor,limit,order}","templated":true},"transactions":{"href":"https://horizon-testnet.stellar.org/claimable_balances/000000000102030000000000000000000000000000000000000000000000000000000000/transactions{?cursor,limit,order}","templated":true}},"id":"000000000102030000000000000000000000000000000000000000000000000000000000","paging_token":"000000000102030000000000000000000000000000000000000000000000000000000000","asset":"native","amount":"10.0000000","claimants":[{"destination":"GC3C4AKRBQLHOJ45U4XG35ESVWRDECWO5XLDGYADO6DPR3L7KIDVUMML","predicate":{"and":[{"or":[{"relBefore":"12"},{"absBefore":"2020-08-26T11:15:39Z","absBeforeEpoch":"1598440539"}]},{"not":{"unconditional":true}}]}}],"last_modified_ledger":28411995,"last_modified_time":"2020-02-26T19:29:16Z"}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledger.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledger.api.mdx
deleted file mode 100644
index c2e4387a81..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledger.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-ledger
-title: "Retrieve a Ledger"
-description: "The single ledger endpoint provides information on a specific ledger."
-sidebar_label: "Retrieve a Ledger"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWVlTG7kW/isqvUwS2kt7t1/uNWsgBAjLEEwol1o67RaopUZSe4Hyf7+lbtu0gSRMMnVrqoYXKHTW76wtPWJLRgb3rvEhsBFog288zMBQzRPLlcQ9fB4BMlyOBCCR0SCQLFFcWpRoNeYMDOIyVDomjgMpiQgyCVAecrpgKWMPqwR0RrHPcA+fgtUcxtDP9WIPJ0STGKyzoXf9iCWJAfewgfsUJAXsYe6sSYiNsIc13KdcA8M9q1N41eQFI5JpHIBGKnzdLEMjiAnuPWI7S5xGLi3kFsGUxIkA3KvO5zdOp0mUNGAcca1adb/W9Z6llIIx2MNUSQvSOhKSJILTzPPKrXF0jy+VquAWqHUoaIeT5bmWIcQBMOb8/BmpBqo0MwVCojWZOdwsxOYNugSXd2+gMyDCn1NFGopUxmouR9jDeZ7gHnba8NzDFuJEELvmYqCUACLxfF6M9HUu9MbDllsXlicZmkhDqIP4DQ78X01bZf0/zbCEzGKQ9p9mFoQh0H+YVc+IsgJ4lnRrgX7y4mbuYc5eM3OpgbM8GCMuR0Or7kD+iHqNbu7hiJjoR/TZuZOvYfhW2lXHfa0lrtDl0tZrGXne88JUDAuIDKlK8/b3BhEh4QLYL7OvkP9LXHY6NGCHv8ZMhTLAhsS+BNSJVpaIIVV8reifzkOAYaKUePUwIAaGjoLLobFaqcS80aiMU4MBPf4F7phMhwtMDH94a/QTrayiSgzHoA1X8o1sERAGejhl+hUM3M96xXGGn9XIIvW94n7ww0z8QZa9zKDvZkcx8utxLkT19Rh+Pz4vsX8F1zXMbhxAy7pdLFDz1b6SRfz5ftV7xGMiUlif9MtZnjdTHFmbmF6lEinNH5QsWTBWgi0bC0IQXVZ6VMk3J1Optf1Gq1uvvzZ/f0NcpSjr8T801UZpT/CYW09pBnqO11q6W/9ejNnf0f8k6e3ai7P0d3Qv5bxdc2Fc/o7ihZi36l1MNQx+ze+Qer1NgTJSbTZrrTAg3WqNtnxWZ22/Xg0IaXZYhwUNP2w2GkHYbNXDdrsbtOq17vOq7mHfbzW7Tb/TbdT8drXutzrLUv97tGkYLwYh7gKhfisEyjqdpt9oV1vtoNkJ2q1OI2xVWc1vhd26H3T8ethq+rVWMwhot82gQYHU/TorNp/eEsmfzcNa60fjrvvKMGu118YNrlX9bsmvlaqt81qtV+/26rXBs17Uw3612WjUu9VatdMu1xvtWqfVLLaoHvY71Xat1Si3m9Vuq+V/p2n1/Gr1B4OlWc1+Xhkefvbvl9PBr603f9zv9/vbBy2zO24f8d3dj5vSXtladHJ1tH+5cb7X2KkMTg9E2hHd5ufW7U43MOOHfbaxZ1NRi48+XzYuBl82Pt2fBRUZHHV2/a3zaT/8YmYXs44T3f8K+irpP/18/XKUnHUY+bQ3uICr5n16dUH3+cFg8/Nm+5AfmsGB2Zl27yftbjjtdjfTirjbMPtwcnRxRNPjrRqkNnoIo8P08sCXg81Ufdndvh3twbG+OFZR66H9UQRXX/r9nb0KG28R1u/3N3dHmer940n/3v0x6G9+Pqu6v06UOjuyH78eHB18+nQpNu3orv/ZP9ycPoiHq9t9cVadTpLbk410i7db4ZfbZncyOp9VN6Z22j7278+DjcvWA92vPVwOpL64qHTGndPBx93NUKla9cvVp6jb3Jhc6nqjMxv0YTpImL6NZlvTYCuaij/PB8dfW3IQ7o/o1eZnOTi9Oz7fOmQnx+3WDO6T7eg+7X7SJ1C/Ojk/rk8yJ/Lx7DpADDZSrguMINvO3Yd5D696y+OyOOZZoejx8sM+1eJtbQq/9ll/ntOhI7ATpd2C/z2JYWpTDW+RubukRHIp9cZdN4Qq204Wc/ZjLhd7eJXNuFqulv1s9YhjomdPVE9XI0Sij+fnJ6h/so+sQoxYgrhENgJ0ltu11FpG+xZxOQJjHRtDGkoZcCajzjgTrVhKgaFg9poIJ5kgt28hGxGLuEFADAftVFMlTRrDkpWMQZMRoML9BNIgiOVjcOSOJgGdLW+SQklpDtICyw3RkLiOIG0+K1FqcqOWBm0pDWV0HnGTeV7wI9CcjQAFYCcA0qnPvV3nPNHKffYZJPgdoAkRAqzxEAMK0moi+AMwBFMaEQeYl0kgxoDz2aSgM4vQMhpWIZMGMbeouF546D4FPXMhIjRrtyggwjnrIaWRsRpIjGDsRnJuR5HbCX3iLL/IrH97JlwXA3rzblmeDMYg3JQzayvJwuwKVRpKUjF4/6/Knm/ym1yqo0SiANwRGIflmBNEL04PPURQoNXEgM40KAnuVtOhssL6bPuT+SnWTFFTsUoJUzHszjikFdLg0imTRpX7jJhyO3PyZyrVLtscoB6aAHI3jXEMkrmjDCginWLEpbFAmGOKyR2XI8S4BmqzGFIihMn8zMI6SjkDlFdMAAZFapJBwmIuubGg0TLFs3RcYuNUOIjROw1hnsyZ/9srT/9Am0KNnjCYTCbrzq8oS4FQowopSZiUTCpLbgpFUFrMj/eueJBRrkwIvRtplUrmLrefVUOeO5pG3AK1qSYC8djVPGSrfB4hblBMbpVGi9GBgjRO3pfRrtJrd+ckUKlFCxMdgAt9q9RQDNw25iEaAb1Djrrov1OJ9hy0TwCMuI3SoExVXFngUBmpSiBUUImJQ7riyotTMMvRWXGf7loSkWfK3sX+9s5w9/h0uL3z587h8cnO6Vk5Zu+zYG5CqDS4tAhgxKWHuP3DoInSNkIauM22WTnKrHRNgmcmAo0UsGX3u3ZFi44U+5U2gZiiabxsPz304cMEEFNIKuseKpQ2gHQqpTNiCaMLaN6kCHL5xIhwxVTsIatM+/Ahbw+QvR0QIWaZ6Ix3OCaCs8zB4YvJB64wNCA7UciAe92wrrQkBS0XLYcBVWkiFvjErknzOFHaEmmz9AtUBqPgJODC1aPjKiRfea0wXO3FRJKRe5FxqTeRHkqIBlZiaiJXyafCdVdVYnmctUSnc8HpWp5riCpEEoAZ9G4CfwiBCnXHDSIGEfQNb5EkGxZO3De8ws6lSPb5qGNzHJ7laVZY1YqRzYhKKiwtsnHxiEJodse2eA1aml1M911XmFnwsfdsFVxf/CAmPDsFIdR/i2dzDwtOQRoo6OonhEaAauWqe0NhLndDDnp1UspPnjQumg3JTvPv7FyoqRzub+0cne04lnJkY5HdKSfK2JjIgsrlpQ0iaPUstrZUPD49LP1t73KL2zcLU1tJBOHZxXLm1eNiqb/Gi6Uee7i3+ua98XCkjHXHj4+uKV1oMZ+7f2dzEfeubzw8JpqTwO3P14+YceP+ZrgXEmGev9oVfXt3urj9e4/+ylveq64sX8Okewtb3IFh7OE7mBXfF+c3q3vJzNj8uE8pJLbA+OI1z30qrD6F9nbO8Xz+P3YMOiY=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledger"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single ledger endpoint provides information on a specific ledger.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"payments":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transactions","operations","effects"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"hash":{"type":"string","title":"hash"},"pre_hash":{"type":"string","title":"hash"},"sequence":{"type":"integer","format":"int32"},"successful_transaction_count":{"type":"integer","format":"int32"},"failed_transaction_count":{"type":"integer","format":"int32"},"operation_count":{"type":"integer","format":"int32"},"tx_set_operation_count":{"type":"integer","format":"int32"},"closed_at":{"type":"string"},"total_coins":{"type":"string"},"fee_pool":{"type":"string"},"base_fee_in_stroops":{"type":"integer","format":"int32"},"base_reserve_in_stroops":{"type":"integer","format":"int32"},"max_tx_set_size":{"type":"integer","format":"int32"},"protocol_version":{"type":"integer","format":"int32"},"header_xdr":{"type":"string"}}}}},"required":["id","paging_token","hash","sequence","successful_transaction_count","failed_transaction_count","operation_count","tx_set_operation_count","closed_at","total_coins","fee_pool","base_fee_in_stroops","base_reserve_in_stroops","max_tx_set_size","protocol_version","header_xdr"]}},"title":"Ledger"},"examples":{"RetrieveALedger":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933"},"transactions":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933/operations{?cursor,limit,order}","templated":true},"payments":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933/payments{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/ledgers/27146933/effects{?cursor,limit,order}","templated":true}},"id":"e1218a337cecda05526fba902c61d3d7130baa58d8db41f544bf563f779b6329","paging_token":"116595189421703168","hash":"e1218a337cecda05526fba902c61d3d7130baa58d8db41f544bf563f779b6329","prev_hash":"9eac16fecd885147067b58b7684f60d216f931b813f651265bbc97de4cea313d","sequence":27146933,"successful_transaction_count":26,"failed_transaction_count":9,"operation_count":67,"closed_at":"2019-12-06T22:39:32Z","total_coins":"105443902087.3472865","fee_pool":"1807264.7509661","base_fee_in_stroops":100,"base_reserve_in_stroops":5000000,"max_tx_set_size":1000,"protocol_version":12,"header_xdr":"AAAADJ6sFv7NiFFHBntYt2hPYNIW+TG4E/ZRJlu8l95M6jE9bsvzId+Gtul2mNMW4UZQ+KqSb/nbN8F1CTxAfQsyUy8AAAAAXerYpAAAAAAAAAAAXQNpS8daKGZUeY5quYUcIiJZBMB7LiLsZJsEx9qw79fx99Bu/lk+sIePNUNcuOC2euthzfhLuWJ1nZBuoQFDjgGeOrUOoh6z7HlbYQAAEG/dvCadAAABFgAAAAAIOwAqAAAAZABMS0AAAAPooSNtHXJNJKKWlBtgkAM1LBxzlzYjIlS0xwpjP+uCi76fQj59wgTy0+xtx7O1qTb+W6zcI2zWZnrUU/8v8RZHFBfoo20QYKh95+wWr348yZAexZpdrjhyCxbChxlVTZOX6nZfIgcYBMnZRkOTCLdPO76yeqpDhqu9KrPe3YPTO3wAAAAA"}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.api.mdx
deleted file mode 100644
index f5ff51859b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-effects.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-ledgers-effects
-title: "Retrieve a Ledgers's Effects"
-description: "This endpoint returns the effects of a specific ledger."
-sidebar_label: "Retrieve a Ledgers's Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWulyG7kRfpUu/FgfNTx026zaSmRKtq6VtBJtx5ZVMjhocmBhgDGAEa2oWJXXyOvlSVKNmSGHIiVLm03iTfRHRaDRF75uNBpzwzwfOtY5YwcohmgdO4+YQBdbmXlpNOuwXiIdoBaZkdqDRZ9b7cAnCDgYYOwdmAFwcBnGciBjUIFRk0XMZGg5cdkVrMNO0FuJV7hZStouVrOIZdzyFD1J75zdMM1TZB3m8GuOOkYWMUl6ZNwnLGIWv+bSomAdb3OcVxahWgg6T/to71TPxQmmnHVumL/OSKLUHodoWcTwG08zhazTHo+jiUZxbp2xlT5fc7TXMwoNuHJzGm1WaviEewhOdODNjEomDm4CqYFDbJTCOPw2A7DoMqMdOuBagHSQ5UqhgIE1adiEjA+lHl54c4karrjKsTDYYmyseKid6+vt9fWljdWNFy/XXi611+pmGyvw8VYLdHKoeWUHqRoYkZGjRMZJqaEDl5hcCeBZhtw24SjwcCB1rHKB8Jm7+DM85S5GLaQePgNj4TOJ+wxP6V853IRdEiMdcDvMU9QepNP/+NvfPTj0EUgPAgc8V4X/A9uF7nHeSj0k7+g8pdDgLmaFgey87hglU+kf6RgCaMq/yTRPa/isXFFEF4omEF3gDzHXYLkeYrHnS6T8crsNDeAa8ixDWxIGgEkHCbciNgIFuXrHWPlXo2FgLGRoB8amnGLDIndGu3ucVm0gijnfLbUfiqul9nh8Tk4pUUzUy+02/Zv1y2kex+goG8RGe9SeSHiWKVnERuuLI7qbmlSu1NEgZIxSvul/wZg2JLOUerws5F0oqS9dTc876ByqwfepEouDRWAJnvUBFfqSjSPmMc0Uua9G3TdGIddsPK4D5axgeh4xL73CGg+N3/wPplJm8eqHUmlMZNXQQdhqitHvYALTPgoxI/YO0jI2a4TcWk6hLj2mD8DVQ/E3OS5/KPdGzFFooniABf9pIMYo8MdSi6ikWCSsopMiKF87te+jnqEbR4zHscm1X7Qk496jpVz65myz8bHdeHl+s7Y2rjHjQljKsWRpWHz3kbdZyIGuxeCPaDJygqm5mhnpWhRylmgL+7dGeolFlxglHLzNxC2eOyZF2DIpl3rB7GvFh4tW7eqBKuqLLXRelrXGlO5UDjXamgnlwNSCcmC6pGdz55XUWFs1HZsunI4tWruZ+4SO3VvDW8jrE0eDwYx2xe+pjOJ3nT8XVAxvcc9ry8LP6arwc7qoq7hMeV8hvOIqHPzTlQvmwsjMtt9BNLMRp3S2G+sSmS0ATH12fhPrs4v8u5j34vlFe7GY/wSn5K371Z8jmbdhjmQqaN59i6XdT3ffft5vYInw7+zQPNGCjZonmoo7kF9zKaS/hmNjVE3ErYk7V5zglblcNLGFmXFyIbP30ifC8tH8TBUqp9VN8FWeZijYeZn5LmQt9xVV+EzROo5YXJhwwRfk2nFRc9RPAynYraQ+zdVltp2InmF+Xq9eiisxG5OepTbhALvr6ty5YeHGN1tlVHVsceyxxPvMdVqtpLgJNDw6r9E3nUeluG0aO2wVl2LXarfKO/2firvuzz+Fq8XPS+2fwuXtZ7oK1erS30PEysr6xvqLlRdrG8vtldXG0h0iq7rz9xC5tPzixerL9trLF2vz8sI9j3ZlpkacVIFndVfPlGyP0GyyzrVqutwuth7BsDJwasJPi2y9XTf9Zgn8TgFlAcTa5V99uj0ZvB0tHTbLplbpsDebB8fd7sfD1Q9/2Vz58Mvezv7Bevfd7nZ3//hgb6/be/fL6eGH9696+3vvV/fXdn49+HCw9cvH3qsq8DoVr4t4kpeqLNCejXS23F5aa7RfNlbavaWNztJaZ231I111PbeetO0XWTdQNktjwnXjD4uJ5X83JpYfiInl+zGxfAsTmx93V3vdk5Xeh7WjvZ1ub6+7vLn66+mH9e7e+72dtd3Nvd6b/d3D5e2TjYNXh+/2j7rd94cb85gQk1K1wsTKwzDBnUN/UR0i3MsryvE8LTWs4+N8XP5FLEWfGPLFEH1RtCeswyap6qZqXo4r5xL60F5VzdHcqodtDlvUeeoVdHCIfmTsZUDuYo6D3OcWH8LzdUUJuuJ6Tj2xgQknZ3m0lX0oFjEypVjdbrabFOouT1Nur6dUkFlzJUVoesJOr3cMm8e71HgSVGlJHbqJp4VeldQm7HqQeojOF71Si43guKJXHVZm1og8RgH960Usiv4r3QonvTTkTlLv1kBstMtTrJbyK7R8iFBrUYFFFWBA5KE1O+23NYyVqD2KQhGLmUWH2hcBD7krlKoU6hqL1AOULlhes6NvpRgi9NGPEDWJL6ydXXlszZfQmlfyEmHElULvIhAYo/aWK7qCAH6LE+oruihwCHgG6VyONmg06R16Ay7vhxaj5drx0Jx2EYSWJ21RGUtQZseIOrTOW+Qp4BXqSo/66tACn6xsziHr/x0JZ/UNPX9ahafAK1R0UriZRFyq3YqNxYY2Ap/9X6Hnk/6kK3HULu8jTaEjX15JDvHbk4MIOPStGTm0QYLRWL1LTHx9urXvvutrYWLX8sYo13Li0pGnDVgkOAVusaG6/RtdRswArk1uCW3k0AhGGFr9aYpa0FRwFNckGKR2HrmgRSm/lHoIQlqMfdjDmCvlgp1hW4e5FAhFxPTRQWJGwSUilVo6jxYqiAc4Vr4hEeHS+NTioABzsH9rYukTeKXMcOqD0Wg0a/yEstFXZtjiDY2jhst1g06hBBvl+fEsPDg46uv0eXw5tCbXAoy+HQ0FdmycSI+xzy1XIFOKeUzDzpvydSLlX4yF8uiAfp5mz5rw2tBrUtHFo2HeNzk9VAQVyYGlvAk0jMA+dxhBnGB8CURdtz88f7wh104dMJQ+yfvN2KSt0g+toWn1lem3Uk6eblF4yRhddXS26BnEaq4KpLx5u7u1ffH66ORia/vd9sHR8fbJaTMVz8JmvsKBsUiw6ONQanpoeeJgZKyn5zHpQ0Woh0FLShIyqIhxYorXnaA9BS0cGvFb0gQIE4dnn+DBDjx/PkIQBrTx9OZrrEOwudakROVG2tAiSXEgPAmuKJjqOWSCtOfPi/SA4bGTK3UdWIe1F1dcSREMvJg7+ZACwyL4kQGH9ELsKbR0jFaXKUdgbPJMlf5JKUnLNDPWUweL4Nc3wY1K8r5UFI+0qga+5kxgUOylXPMhOpAEvZGOIOMWRUOYkZ6AzwxmTTWZl2lIiSSzXEkpjxKiGYCm0h2ejvCJUlCLO3pzc8DhE+vyLBwWxO4Tm/iOIEJlKdrUHQ1OC5jVSrX6zgaihhk0SjSW72g8Dtf08r2yUrsO99cUmMV1JbpVCs4WfphyGWZRKfPn+tw4YkrGqB3WZG1mPE4QlptteigRhN2BRDuZaRQzU4llsuFhtri+F0xd62C3u314uk1LmolPVbhQZMb5lOuayKpLAhzKPskTB9OvDGbqi5vpM+O/8IFDWfx7/OZbmeIytOiDSTdlZX/GysqeRaxT+6KhKu7PI5YY54nw5oZy01urxmMaLt6TqeQX0lHH744X5bol//1vDRZ65BKv619PlC0rFm4fjzHuD/NJwT1eqD6m+I1O+B/6fOAeJ1UfVkyddE4/rCQvPTImnp6Ubdpn8JiPgxZqV7UO9HVduUrrSXiH/m2CnHaalC2mN+MYs7pVc183kJWT/sCb7R4bj/8Jmv4Vqw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledgers's Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the effects of a specific ledger.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"RetrieveALedgersEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/0/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/ledgers/0/effects?cursor=33676838572034-1&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/ledgers/0/effects?cursor=12884905985-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-1"}},"id":"0000000012884905985-0000000001","paging_token":"12884905985-1","account":"GALPCCZN4YXA3YMJHKL6CVIECKPLJJCTVMSNYWBTKJW4K5HQLYLDMZTB","type":"account_created","type_i":0,"created_at":"2015-09-30T17:15:54Z","starting_balance":"20.0000000"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/12884905985"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=12884905985-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=12884905985-2"}},"id":"0000000012884905985-0000000002","paging_token":"12884905985-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"account_debited","type_i":3,"created_at":"2015-09-30T17:15:54Z","asset_type":"native","amount":"20.0000000"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.api.mdx
deleted file mode 100644
index d496e94ba1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-operations.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-ledgers-operations
-title: "Retrieve a Ledger's Operations"
-description: "This endpoint returns successful operations in a specific ledger."
-sidebar_label: "Retrieve a Ledger's Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWuly2zgSfhUUfkySKZ3UZalqata25NuWD8VX4lJAsikhJgEOAFrxuFS1r7Gvt0+y1SCpw9Y4cY7d7K7/qEw00F83uj80G3ygho007byjB+CPQGl6U6A+aE/x2HApaIcOxlwTEH4suTBEgUmU0EQnngdaB0lIZAyKobAmXBBGdAweD7hHQrtkiRboTGTXpx16CkZxuIP1TGd/tgAt0JgpFoFBKJ13D1SwCGiHavgjAeEBLVCOoGJmxrRAFfyRcAU+7RiVwFPkQPKJRCSRC4rIYDVC7Y0hYrTzQM19jBq5MDACRQsUPrEoDoF2KtNpYYbIS5SWKsfzRwLqfglQwEL9BNF6DsOMmSHWo5oYuQRJetYXqS89GYbg2f9lQBToWAoNmjDhE65JnIQh+CRQMiJmDCRmIy5GQyNvQZA7FiaQGqzAk8r/UjubzUqzWW3VW2vtRrtaaSyaLZUPL7faB81HguV2IFS7EBo5GXNvnCHURI9lEvqExTEwVSL9OA8sL0x8IB+Y9j6Q10x7IHwuRm+IVOQDqvtAXuNP9rhEdlEN14SpURKBMIRr8c+//8MQDaZAuCE+BCwJU//bZVe6RxvFxQi9I5II84Rpj6YG0ptFx4Q84uaFjsEAjdgnHiXRQnzmrkhTDfwSQTm7PvGYIIqJEaR7XkXwTqVCioQJksQxqEzQBhjXZMyU70kffHT1jlT8TylIIBWJQQVSRQxzQwHTUuhnnJZvIPhPfFetfGlcVZcSKNvSYcB4CP4LPXcGBnVj1uNvHh7pWo8YSYFGrE+Dyc7GTLIqVlrhShkCE/P9tzxj5Zd2/6Pk4mtNYEIzL0W2YArmyNJYmieeAtwFAswbz1JpyVx8khNFiU5vEEhGG2iYU6ngzyMsKZvTAvWkMCAMirA4DnlKRuWPGuUenjpIuh/Bw7iPFcIwPNUyDLm41Z+XgyAAz3yB4FhBsCotbQwbm3/ilk4L1EAUh+iiFbs4nS7uyrt00ZsCNdyEsLBGrMADH342WBrC4GeDhIHj/2yOWsibnwoZSnF/lbJcjvs2/haO8eekl+QQ4X0MQ74wIz1UlmuYQja44ojLhWjKMkPmeTIRxlqX65wVa6gwm2H9+ExV13mgthhZZoY8nNMNoGNjYt0pl8fpIVU0oI0AU9IGwpCpklSjclqv6bLTqtZbjuOU59T3e1qQ/faLPf9+c36xBcZveFxPC1TAJ/P9dVWrzUa7Wa9Vms2W02i3K43V2mMFdz9ae2Ot0n6k3RYpuHdDiFzw/TRys/LCVtfftBlzROWnUFak4QuWXjz4yjXWrNdra23XBa9Z833HrVZarFLzqs1Wtdpo1gKvUW/7jLXcVtBoBu1GlTlQb1WCtWrgQMUG6vyc+V4WlvM1cxrMePAF62cr/D7frl/+cm8fn0tfrYY9ryWjKLpi7DExrZZZ2Lvh/C0xf0PTMlHenFk6dLt7crHb3NrfaDnd4/5er765fbW5dXK9f3p8crLbv7o8Pbxu7PfOty8Pt5tv3w629w43NtfPdmjOYzRm91ir0jn/VQsZg/lDy+BOpdouVp1ipTlwap1Ko1Nbu36EdMz0mHboN8dagTKtwQwzbJ4Cn5shC+MxE0lUn41jTU479KjfPZg941onoNAnG85Vbf3i8vy0f+hs7Gyd7J8cDy72d/u7tcF1b2OjWzsY7A/OTwb7vePL7f5Gr1V3spXwteAbvSpx/nq31rhqrfdOrs7qF0fXR91G/7y1c9JcP9jodo8GR1t9Z3DkbB7We6e91vV5fWtv4+jyuom2RNnOVkoV/Gu1KBbKP4ZqkHO/I9Ws1YC5AVtz6m6jVa81wWf1tuu2meesNVsNZ60RNP12vVFzGkGz7bv1aqvtVFprbK3m1+qt9g+gGrTw30g1uUN/LNWkWlZTjR37DNVkMi+lmo1es7a7c7xzubN/srO71TpoHDcOt/vn9cPD7lWvebp9vbl3dbF3vHF6ct3daxz214/7l631OdVETLARDGUQ2Koq55vaV/PNNwfc03xzarbE5R6kz+pr9aZTzZ8NFe6ooJ30cYH6+F6e/k0L1E3u0etLHIZ9mzvsvGkIwyejKxhuWS5jutPDwZOhOeF1e9v9y+PNncuLrasrp1bvOlfXZ8e9Pae+cVl3emd7R+c7V42d1uDi4uTs6vSocb1/3asdYWsR92KIcVSZ3kyzvwKNwIwlBtcIbMmP/cIOnZVVD3lfcLqQeRafustbj4kKvyzq6aq+ziCVI0dgJlLdWg5cvWKQmETBl6y5lUsSka96g02HQNpyPqvQsy4PLVA0JZ1dKVVKGAM6iSKm7udSJFbyjvu2pUh2BoNjsn68i30InxmWtxPOUly51hLZNYSLEWiTdiIVFK3jtJW2M2Ml/cQDn7j3q5ZIu5v4ijXrVAHTHDujknhS6CSCfCq7A8VGQBb6EURBaKPSdlCw8TnvZhWl4iCwR2KBKIgVaBAm65AkOgWVA9qUCrDDxrW1fMEOV3F/BMQFMwEQqD61dnnmsZL4WqlJyG+BTFgYgtEF4oMHwigW8j+xW/PJG2PXThfsCjb6SRr9FtGsM2ck0YlrG3gL51KB2J4SblHGZsRlIRpbwP6nNgpYROAORI7jcVdpPrP0JLL+3yPh3eKG3rzO09OHOwiRHPTSCZfBLntSQVFIH978X0XPe/Fe5OqwGe0CDoFGX95xRry3pwcFwoir5ESDshqkgLxVOfP1WXdff9bXvvR02UgZ6rL2bzV6WhIFGE52NU9i9+ETN/e4/r1MFEYbOrRAJmAb6VEEwsch6ygmUDHhQhtgPk6K2C0XI+JzBZ6xe+ixMNTWTruto4T7QNKMcUGTsZxYl/gRF1wbUCQPcRuOuW9Qhe2tv1YQpMFs7e/OLH1FNkI5mvtgMpksGz+TLLqhHJVZUcCkqBNRxFNoDMXs/Hhj2/laYpow73akZCJ8IsXjbEhjR3ljbsAziWIh4RHmPER252XW+4/YR6lIdnQQN4niNyWyJfGuJm2J4WPmygSvASxEdGCmbxYa0geXaSgQbwzeLUHpRfvt5cI2unbugBE348QteTIqZ34oj2TZDaVbjhh6uozpxT3Q+dFZxksGJViYRsr2291ub7jVPx12e+e9g/5x7/SsFPlv7GZuQCAVYFi4MOICrzFeaTKRyuDlEze2CBAjixJJgluI4I1lendi0WPSkiPpfw1NEF969lLFerBDfv11AsSXREiD16tSaSAqEQJB5G7EDU1JihGMJ5+FmEyLHDKLtF9/TekB7FUiC8N7u7SdO7xjIfetgcMnJx9gYiggZiKJBrx/NZhawgMlMsrxwZNJHGb+iZCkeRRLZZgwNvxcad0YcubyEPMRZy0EX2kpMTD30lJaE46hNxEFEjMFftGXEzELPhksmypjwyNLiagzm4mUh4QoAyLwxYi8nsCrMCQLeYc3Wpow8p5ustgeFrjcezrzHYYIFuigIt0PztIwWyjVll4YUagog2IWjdmlCfNsgzG7D8phL4b7FiZm2jotPCoFlws/iBi3oxCG8m+LY9MCDbkHQsOCrvWYeWMgTgm7D9zH2A24LavTkWI6MteYkQ2zo2m3MV1Ulw92N3tHZz2cUhqbKLQvabHUJmJiQWXe6yWMpN3eV5os3eIvVRgP81ul7/I1QfbmYeCTKcch47YVbc17yAr9dzQr9GmBdha+HVio9W8KdCy1QdmHB6SqtyqcTvFxen+HbwA+18wN/+oGb9Gs//zF/kqn3ML94qcKWROe2peRlxj3X3N//4wX8i8XvtIJ/0N39c84Kf+K4Sud9IOu5Z8B/OQrgmXknwX6Qy/fn0WefTIwx3uD/yiOrn4h+7w+za4e35CXfPO0Elz2kIn7RXA56BmXTm+mBToGhjmFYNPhdc+DeDF+nnxDgFbOejPbvQGdTv8FiSw/rw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledger's Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns successful operations in a specific ledger.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"},"examples":{"RetrieveALedgersOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/operations?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/operations?cursor=116596430667259905&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/operations?cursor=116596430667255809&limit=2&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/116596430667255809"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/116596430667255809/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=116596430667255809"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=116596430667255809"}},"id":"116596430667255809","paging_token":"116596430667255809","transaction_successful":true,"source_account":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","type":"payment","type_i":1,"created_at":"2019-12-06T23:05:38Z","transaction_hash":"3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0","asset_type":"credit_alphanum4","asset_code":"NODL","asset_issuer":"GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL","from":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","to":"GAD35Y7AEQYS4WNZND5OV7HQ6ALBDDNTNFO2TN2CM4ERE7ZV4FJBNXZ6","amount":"0.0000077"},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/116596430667259905"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/116596430667259905/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=116596430667259905"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=116596430667259905"}},"id":"116596430667259905","paging_token":"116596430667259905","transaction_successful":true,"source_account":"GBE63IHPHXHKQHIF7L5P5MGOV4MMDYE6RGZCJYWJPBRQZDJ5MOAPOX7A","type":"manage_offer","type_i":3,"created_at":"2019-12-06T23:05:38Z","transaction_hash":"83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479","amount":"0.0000023","price":"0.0484621","price_r":{"n":484621,"d":10000000},"buying_asset_type":"native","selling_asset_type":"credit_alphanum4","selling_asset_code":"RMT","selling_asset_issuer":"GDEGOXPCHXWFYY234D2YZSPEJ24BX42ESJNVHY5H7TWWQSYRN5ZKZE3N","offer_id":0}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.api.mdx
deleted file mode 100644
index 20646e86f1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-payments.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-ledgers-payments
-title: "Retrieve a Ledger's Payments"
-description: "This endpoint returns all payment-related operations in a specific ledger. Operation types that can be returned by this endpoint include: create_account, payment, path_payment, and account_merge."
-sidebar_label: "Retrieve a Ledger's Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWuly2zgSfhUUfkyO0u1DtqqmZn3IjmMnPuMkTlwKSDRFxCDAAUArHpeq9jX29fZJthokJUqWkziZmc3M+I8sEUB3f/11N9DgLXVsaGnvHT0APgRj6WWNcrChEakTWtEePYuFJaB4qoVyxIDLjLKESUlSdpOAcnUDkjngRKdgGM6yRCjCiE0hFJEIifRrN8hhOYC4mxQscTFzJGSKBFAsDJwEN8TNiBQqlBmHHgkNMAcDFoY6U65Wysd/XDyYfGOKk2LMIAEzhAat0Ylue5z26Ak4I+AaNgqrj/K5ltZoygxLwCEUvXe3VLEEaI9a+DUDFQKtUYGgoERaowZ+zYQBTnvOZHAXOSDlRKKyJABDdLQAGFqjNowhYbR3SxEa2qNCORiCoTUKn1iSSqC91nhcm2gUZsZqU+rzawbmZkahiEl7R6ONUg2PvIfXEqdnVNJh7iLvwlBLCaH/riNiwKZaWbAeY2FJmkkJnERGJ8TFQFI2FGo4cPoKFLlmMoPcYAOhNvxr7Vxdba2utrvL3bX1lfV2a6VqtjYcHm41ByuGipV2oKp+ITRyFIswLjS0xMY6k5ywNAXmGVvy2XOQfGA2/EAeMxuC4kINnxBtyAcU94E8xo/i5wbZi3IaMzPMkFtEWPXff//HEQuuRoQjHCKWyRx/v+xCeKwzQg0RHZUlGKfMhjQ3kF5WgZEiEe6BwCBBE/ZJJFlS4WcJRRmRDYLj/Po+WA1TQ8h93kblO60WqROmSJamYIqBnmDCkpgZHmoOHKF+po34TSsSaUNSMJE2CcPYMMCsVvYzoJUOBH4Hu3bra3nVngmgwqWDiAkJ/IHInYJD2Rj1+FnSI19rLhEasKjrXTL52RhJXsRCKwKtJTA19b/PM378jPc/aqG+1QSmLAtzzSqmYIzMPMvjJM/BnAAL40kozZiLv5SJokHHl6hIkTbQsE6rhR9zumRhCBbTb6iVA+VwCEtTKfJk1PxocdxtBSAm5WHkU3QBlQ4+QogRkBpUyIlc3kAKdWUrkN4zzoKMvjwqNhAtik5PZefDUF3RcY06SFJfFRc4czyuOuddvuhljTrhJFTWUPDJ/WAqpQaufyiVxjis/OnAuxrD4gucgCQAzmfE3jO0SIaVgcwYhuElHCRfwau/MP8q4f+DaQZRBKH7ClT/VK0sZjHgP5paqYEQOPxYas0N8uyfZdzUyxVkK9ZcjmtU8EXqlpIE9+ZX9qR3R8/SfGDzQhRlcpFlNWp1ZsLJEWSR8JQ5BwaL2u67jfpFq75+ebuyMq6oxTg3WOxQtJ+8YLNXbllocaopBw/EQhOKqjxgC1SaszBmNl44iFkLbrBYo8lj3Mrh43I3invqazwVhQa4cAMm05ipLFm++1O7412WryOszcB8N364Cf1+J+jvXoIli+kwT3PB6Rwh76XfHa4VbJnwYMbrC3w849ECKm/sRN3L8Wz5PCq5hn4qKOjzwr3H5d4t9ae82UJXlrI8ndDYudT2ms043/3XHVinwDWsAymZaWgzbOYHYdvsdFc67XZ3tVnw3v6Sn3N//skfK35u/+TPbT/jKaiyQ/o9JbXba51WZ2WltbbaXe6uLq+1F8sut0J/qmx/7kOfzWxhJpuUd9/phulOvnlXlQVbggcsXT1LNNe77eWV5WBtma11AsaW1ljE1rsrsA7BchR1Vpc6a512sMKWoBt119eXWBc6rSDg67y7urQEbG4P8HtZ2CzXnCvmD1i/WOGXqbt+ute388X5m8Wwz0spCiVd8Gy+PC4ec1+FzJte8zWR7m4fv95b3dnf7Ha2jw6f95e3dt9u7Rxf7J8cHR/vHb59c/LiYmW/f7775sXu6qtXZ7vPX2xubZw+K1PctOpNi157tsjRTqu9Xm936kuts06nt7TSW16/WJQFe/S7uTZbGhdVumptpC8Ptw/ofJ2ju5udt0sbr9+cnxy+6Gw+2znePz46e72/d7i3dHbR39zcXjo42z87Pz7b7x+92T3c7HeXO8VKeZH7LlS1n7/7/LS78Wbj1c72xcbJ3sn2+cXKeXdr5/Xqm7fL3denm/3O4fnB1tbu1vbrw3537+X+25dLR6fTetGjrUYL/9pdrBHFX40m4GKNBBuCyysn4j7JdrdlD3Q8yXdY3cBcl03WzMiv4z1d1ME6y8eRl+BG2lz589/iFaPMZQa+Zs2dciRR5aqX2F6J8r1CUTCLfhatUTQln91qtBptv2VNEmZupqNIavS14L55Sp6dnR2RjaM97Lhw5ljZODnN9SqlNsge9r+HYF3eczVQ98BZP9rPTI3mWVg2zu8skfdxcQc/6ckBswJ7wJqEWtksgXIquwbDhkAqnRfim/vi2re5fIt32rerayNAYTfIK2IgNWBBuaIXlNlcqVKhLW0Ae4nCessrdgRG8CGQANwIQKH43NrZmUdG46nFEimugIyYlOBsjXAIQTnDpPgN+1Kfwhj7k7a4B8AoJHkUeo0mPUinic0C36qsVKYa8d0zdFGRz0jAJBpbw06vdQZYQuAaSZzrMd8/m85s3GHWP50J76oOvXxchieHa5BYmO1MjSvUbobaQF1pDk/+Uex5r96rUlxxR8Z86QVOrgUj4auTgxphJDB6ZMF4CVpB2ZSdYH26vW+/iDXXoW06raVtWn5lEWlNDCCd/GqhxsPAJ+FucP0bnRlkGwJaIyPwVwZJAorjIw8UUyiYCGUdMI6TEnYl1JBwYSB03ochk9J6O71bh5ngQPKICcCSWI88JDwRSlgHhpQU93QssUER/hbhsYEoJ7O3f3ti6SOyKfVwisFoNJo1fjKyHkg9bLK6glHdZqqOVSiGelE/nviLC6sxTFh4NTQ6U5xoNR8NOXdMGAsHocsMk0QkGPPgi1/uIWFJwj5qQ4rSQYIsSZ80yI7GW6m844I/s0BneOHhVUQAC3kTamgOAbNQI2EM4RXB0VX7/TXKLkI7BWAoXJwFjVAnzQKH5lA3A6mDZsIQ6SaGlwjBlqWzidcpRjGZM2X31d52f7BzeDLY7p/3Dw6P+ienjYQ/8c7chEgbQFoEMBQKL2weWTLSxuE1m3B+A66GXktMEsKrCGGs81sirz0GLXmp+bekCcJ16K+PPII98vTpCAjXRGmHt8raWCAmUwqVKGFEh+ZJihHkE2cSg6maQyZMe/o0Tw/gL02ZlDd+aT93cM2k4N7AwZ3KBxgYBogbaWIBb5odhpYKwagi5XAIdZbKAp8Ek7RIUm0cU87TL9AeRilYICTGI86qkK8xExgYewlTbAiWCKTeSOF1uQFe53qkJuTT0aypOnUi8SkRZRYzMeVhQtQRUXg0Io9H8EhKUok7vLuzhJH3dIulvljgcu/pBDukCO5IwST2MDrNaVbZqs0cGXFQXUf1go3F9RAL/Zm/uPkq1a7SfQcDkxVdxNmt4OzGDxIm/FOQUv+r+mxco1KEoCxUZG2kLIyBdBot7P9z5G4k/PY+f1LPn0wlFsmG+ad5CyBf1DYP9rb6L0/7OKURu0T6Y1qqrUuYqogsWy+Ekbz58siSytsKM/uL2+nt2d/krY3iyOXgk2umkgnfg/Xw3hbHjHe0OGbQGu1V3tKYnDQuazTW1uHI21tMlK+MHI/x5/yeFM8fXFgWyPtuSquw/v9foFgIyRXcVF8JKXpy1B+FHmLcX+Y9ic+gUL4h8o0g/I3eifgMSOXbIt8I0h/0+sNnFL7ztsas5l9U9A99yeGzmhevZkz1vcQvRiDUD8w+j0+Ku4Qn5CHvli1UrrzNVjdV5UqlJ5nU3wXEwDCmUNn88UYYQlrlz513NdDKSV9ot39Gx+P/AX+MCwU=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledger's Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns all payment-related operations in a specific ledger. Operation types that can be returned by this endpoint include: create_account, payment, path_payment, and account_merge.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"}]},"examples":{"RetrieveALedgersPayments":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=&limit=1&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=118202550867476481&limit=1&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/ledgers/27521176/payments?cursor=118202550867476481&limit=1&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/118202550867476481"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/971454b84a82baa38afa975e9eb4ff2632821b5a3e7f7993a7e20bbd9d7633ea"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/118202550867476481/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=118202550867476481"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=118202550867476481"}},"id":"118202550867476481","paging_token":"118202550867476481","transaction_successful":true,"source_account":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","type":"payment","type_i":1,"created_at":"2019-12-30T22:35:49Z","transaction_hash":"971454b84a82baa38afa975e9eb4ff2632821b5a3e7f7993a7e20bbd9d7633ea","asset_type":"credit_alphanum4","asset_code":"NODL","asset_issuer":"GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL","from":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","to":"GDGJS7AXAUFDZARIRDVZ5V7CFW6XY47WSBE2OVLCCGCDWOE7INKYN3PS","amount":"0.0000017"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx
deleted file mode 100644
index 5b810b2326..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-ledgers-transactions
-title: "Retrieve a Ledger's Transactions"
-description: "This endpoint represents successful transactions in a given ledger."
-sidebar_label: "Retrieve a Ledger's Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlXOty4rqyfhWVf+x1CQlgc03V1D7cr+FOCMxKZcm2sB1syUgykEyl6rzGeb3zJKckczEJySQzs9eafTZ/mGBJ/XWru9XdVs8XhUOLKZeflTYyLUSZchtTTMQM6vjcIVi5VEa2wwDCpk8czAFFPkUMYc4ACwwDMTYPXMApxAwaYgYDDgYQWM4KYeDKRS+UmEJ8RKF43jCVS2WAOHXQChW2VEeR+UpM8SGFHuICzuXnLwqGHlIuFYaWAcIGUmKKI4D5kNtKTKFoGTgUmcolpwF6iR6B3USAA09HFJA5gID5yHDmjhHByAwbeVC5/KLwB19QdDBHFqJKTEEb6PkuUi4TT0+xPSIjoIzQHZ5lgOjDEaA5dNkLRIUdDG5DDqRUGeDkCBIxpKxCURrEdZGUjUBOEfMJZogBiE3gMOAHrotMMKfEA9xGwIeWg607ThYIgxV0AxQyTJFBqPlePjOZRCaTzKayuXw6n0yko2wTaqKPc20i5lgY7vgQUOVCgsm17Rj2FiEDzCaBawLo+wjSC9D1d3pluIGJwJ+QGX+CXyEzEDYdbP0GCAV/CnJ/gl/F1/bnC9AQZBwGILUCD2EOHIb/97//hwOGeAw4HJhoDgM3lL9c9qR4GKcOtoR0cOAJW4HMUEIGlduoYFzHc/gHBSMU1IMbxwu8iH7uREERDyhG5gUQ4+T6wIAYUIgtFO55UoBXEwlwDiAGge8juh0oFcxhwIbUNIiJTCHqOqHOI8FgTijwEZ0T6kFhGxRBRjB7Q2i7DUTmC9klE+/Vq+SRAW239G4OHReZH5TcEHFBW1i9+N6pR7gW2Dsc6ZAoYgLrS2WSs4UlSRInudAJcRHEh/2XfkaOv316uhU4tyYpJqmJhPh6BjV0lUpMMQjmCHMxBPq+64SGHr9nYtyXCHHout25dH9bGES/R4bQLp8K3rgT0rtzHbxgEbivjGPInX99lE3R/JTmSzXhUsXxQnmKKRx5vit04YSgnp6ie/c5XPQ2pnCHuyiyBkYb/pNB8ila/VSQnsSw3U9tudXCfr6iE8jTkWkekX1l6NbRRAZCSqGwPocj7x165SGPvJTFU+zfWTGhYZAA/2y6GQYqPxmog5v9yYCh+RwZ/GdD5VNkIBP9bLBkKI/Mnw1WJK34qZA9GyQ92MFr7C31yDoOGhnRgojkj7m9fYopjnmKnR0Sx5T6FAn2T3rhQ5J2ituYYkNmn5z4wtscgrm9RB3MNVUMNigSAr2D/DQIElAD3b10q3uufMg5oiJUqn0unM8S5/nbL+n0U4RfaJpUhFAH93znBRt0QkbPR9ydEuQLVHf79PLU2Dn6cfAja73Gwveu+BrLYqBhQ2q9IjcPbu7m6LQI9rp891wMb2kGwivkEh/dbUx6ctkwMv/aYw9x+OoYwdWbA0SMchf+ekoPZFYTUPSeKOirGxQJ1yILb10/wabzzsOSOx7SSYDf45Q9B9+J8a/u6SsPI1gjFZheFOjoAGPvFD4C64UbOQb26uN3QGtHwYj1HPw+Yz418A5aHxgcwr6zoP+2GQQHO9hwCu+ERsiq1nv17Ok9gtjZgB54/t3HzsyT3v9AUT7/q0wk8nMVoWLg+RGGxSQHY0T/jRl8y79GpjQEm0esP4s3HFN5dvIfnfPbQz0ShkSO5xeH8evn4PGpd3x4HFh5eTA8c/pHLv6lQ49656N9uH16ek37lafbp31NSe7MmwXlyy+KrIMel0t2eWcYNyo25z67jMftsD52zhHjGPELxpHrQnpBqBUPBcriajaZyqqqGo/Wvf8ZVoM//UMW3z6p/5DVzU+iVhipdfxoaslkJp3PpLREJpNV0/l8InWa/q6w8a+ln84lcs/oyyqp2MejosS+7PB5V0FQqtAsGtcJsq5T1u478/i1OtrMWrWCOnVuzq6IM29kSTE+vm9efVJi37eRUU7iGsykUlour+vIyGimqerJRBYmNCOZySaT6Yw2N9KpvAlhVs/O05l5Pp2EKkplE/Nccq6ixLOKwQdgbGexeK3YGlUKw85NoVhTO6XUaJrpaI1CelwtZaaTtDZNtUaN1lQrjSutvjpJVxrTwdX0ungcqH/H3r5M5f8uacYPML5slSwmNSom9UlGwIcETpRij5P9vw33FsP7QUdrAd+I+p97G//Hq/b4PL//PlLCnN+itc1ble82que5rXKC2nF6G77+C0/8H0F/Z1g7GzlOcxU1kcyfJ9XzRGakapeJ9KWWm708Xi+Vb7btNzJUJZnU8iktmciqqXQ+l08m1WcH9GUykYjEG/KvFxlc8nl+phTEpzp+KCzUVMFLJG6aqZwGCyYZ37BJdlWvjvq0thk3ljVqNu4rEzF8VqiNH5dGoVB9TMn5/cJrn/IHnLwYXzysV7ZndWdZjve1YDiy7qeVSe16MC+V6tNV1UPL5jip1vLDxWNzWpHjK3JqMZu9T5X6m7brpWGPLuO98rpq1zpMdc2lbpZm68Vw/nhjj+2pHD5a5CujcGbyftq+odXHTrE7KZEeng3rDa3XLNh1biRHtASdXjBbD+dp39qxV+wcWG2v8yNXlfDbwzZuazcjrZoxl2lPndRnWV7X6kXaiqMzX61l69TVJjf9ERkza9NqDOoZ3a6P4l5jssZ03p7lsXt9f1Wqkllved2iDdW12nv590t0lm/o9+VCMZXIXVt9uOz465ucfUPj3TEjFbRZTGqLTr53bxRrKp6n9NbE1O8duKzPztp0dXVWNj17wwtaO68/eiUH5TpW4dNx5LbVDfGpRTb48M9iZJ8/nQj0tgvICQ25o4VZKpu0DrOuR43SSLdK+mhg4PtHkxRVe4A2epAzrjslplf7DoE84VwNpiHFNB+Rg/Jpp3Wu8poyFn8w/dSH6e+ldlXE98FZRKD1VdCzmuVKMNFdchbQXK5XmFSm6iO8Vn2eaOLSoBnvoOqwKvFXu6PE4CqcOelYHLGbq0QlPW1ZZ6bbMO6N3KJUQcnH6y5rLhtnaVxsxj1vi6PR03KFoc/v7YrzCuZKEd+vJn8bvtz6K/iE/FbXB3wfdRbfjq9dsZdX/iy+/6zfI7+/GN/CfQPfp0/K8xJaaKnWXrKtiNJeX1nNTlBo8k71AfU6qlWH1Wq2GmQ3m3GitWHXpZa91IaNTbjzhbqX7FcKs1HXXxcKNz3jtC28emREJPfN9LvWt9GXkonUDnd5dbRY8FnhjcBYmWbPuPFV6umzqYmDxNwwaozmsxk81RkKbsyZWezaw4dyhdiVuR9UzN7Z1NZLiOc4VtH15GrdmNiLM3+8ZPdwUrAk7RbHCTu4uirU70ebSbG4JCouzh+qaJVLDx+sQbY2mMK+ljjrrCs6NOM282fJoNtcEhOngiD3mOqosF5LlI1VctWdtprZtSrZuhXvkH9cBpXTENTnMKem9HQ2pWWQCVN5Xc9DQ81lsmk1l55nzHwqranpeSZv6qlkNq8msjmY00wtlc3/iAyqPK5PCymtXelPbtrNdK1f65Sb9dk0M5p11G5LaxVS0/5NP5UtDq4G5UFjPC6lGuP0T5hBfa80/64M6rtx/4wZlKio/FUZVEhrl0F9t1F9JYOS1N7IoH4A/R+VQX2rbX8lg9JyWiaf0VLpTCKlaZkfmEF17VwhzWeNScB7o/5VAo7SmwyaZAwKLWNTynXn5episBkMraAQZlDDhJkrFErl9cnjqKottcfps+MqPMSHSLWyj1p3WUxUz1b0jF1lVrWruoWJ99DstpuodnV1P0reW+HRV5aTrpud6+1SDzXTTN1r7KbW0VO9ydUDGnSD4upx0Gzq47MujneTZLiprozl+hhT0SgU1XGn0HQmVuHUp7nnr1+LL1h3oWLYiPdoIZ5ZIqYZiYZNuj4uWraZ0HLDjErhg0N8uzdkWv1hrFt6t+JP+6VFEz3SeVLvnTF1Xr25LlVudGuF+ov8NFXWQnE0Oj1zU7tOXjdQP9kdl8vuktPhQ65KJ/34WYkPNsvrulG38rnh1E4bJG6ZOW2QatTKm2BRKj6M9Cn0F3TcLSduys1WKW4bVuqjGVD5mQBKkTDi49lQpr4ue8mFDTOJfKfwOPB7uO6ndf+BL4uPlfY6nbuaDOrVaqu0TTxaZHV1UKTVyT35QDb0nfTXp8m8nQ29JxoNFodJZTIvdPXJsErpKJEod2qLMwNhN8AtldSv+qsyXm9mFWM8Ju0tZ0vnbFyYtQfaulBodHOnsbw7Gv0W+rn1t9F/EY1igtGLaFQ/G64zI2iS+9wZK8eXfubRfOw7NSvjGbVSVRvNN20KOW21HK+Sbz0a8+YgKLLU0LULrb6b7fL4NYtnHme5a3PcGJhBKZ8u9SXtgpXIa5XZzfXYTpfH6f5Vd7JUebu9nvBZOZ5qJes1f2yuUVnbNJ26+3B/VtQezbplTXu1TL9Rb3a4vfSGvJ/qDYyrBWmfVR/KloxGw3c98nWPh7hNxPlnIR6+YhOH0T7c+rJz4U9HZ6uQA6KrXcdAQN33HdDKqevYo3Ac6CC+JnQhL1yeXnEeCMG/Z83qbiTAu1VvxRvNeXh5cvuOa3s5W4kpgpVwduIicZGUB7XnQfpwGAV8SlaOKTsBQH006oFCryFuQpuQQ3HpWVyxH4a4dlQvQIMDB1uI8bCBgKJzKTgmR8uZPiVmYCAT6A+nlgibEsQr7v0FcwSZIxoaCDAIZoGHdlPhClFoIRC56gwociF3VvLOtuxXOFxCPyfUQZgjMwSy7zXZ3uMOWAhqB6hEKBIX4x0mOY/woVPHtBDQEV8jhAX5kNvjmT1KxEtjBlxngcAaui7iLAZMZCDMKXSdR2QCtDFscdmexeQKkDEkeGYBohLR/kI9J4AFurx3H1HMGJC32cUWbYMQoENXMBsTbQuMUwQ9gFayo0biOOqlEX0h+5kXLzTrP10TPkc39PbXnXmaKAzJKDsKxrew4wah6BwTE/32H6U9f+A/8I6c6CHRkXiEmJDlyoHAGA/aMQCBTsmaISopEIx2zTp7WQ/LLfZVWZvEYHFOiMvizFwwIWkCKBLqJFcziHh3v3H4g1j/gQRUaJsQaAyskex/8TyETfFICgpiQRg4mHEETTHJgwsHW8B0KDK43EMDui6TfMpttQLHRCC0GB0xYJO1FInpOdhhHFGwU3GpjjvZCBKyJeZXiuahMkv+y3tOfwFFl1gHGazX62Pm9yPPdZdYcXiO0fqcBfhcnEI2Ot+eH7/JLhxGhJlAY2FRcZcJEPzcGkLdoYbtcGTwgEIXOJ6weeTJnSfblh0P3hMKtkcHENeBfrsAVSJarMIrSeJnqJNAdO9IiEKAW3p71SAm0iFDMWDYyFgAMTrKv+wJqgnRHgRgOdwO9AuDePGtHOIWiesu0eMeFJKOC/NyDMR2R2dc3JaiGLqhptTGjXLlrtod3JUr15V2t1cZDC888ze5mUU0JxQJtdCR5WDRffQLA2tCuegZc7jMybAlUQon4UiIyLBJ2PIk0QujBR1ifoubACYxZC+UlOAl+P33NQImAZhw0RlJKEOABhgLEDsxig0NnRQEQp9M6ApjivqQvab9/nvoHpDsAISu+yCXlnPvVtB1TMng3YuTDwnDoAjwNQEMibZJLkwLG4jircsxkUEC393KxxNO2vF8QjnEXKqfTqQYXQfqjivsUcyKKN/FkWEI2/MghhZiwBGqt8Yx4EOKzHOTrPFe+cj8mFXic8eTLlHQ3M4ULk84RDIHWBRXwK9r9IvrgojdiUY0BiD4QylBXx4WYrk/lL3shIrI4hD1WHc+DNUsEqodVWPEoHMyP99q47YfCxqy7LjtSdvBjqp7VRim3Hwl9iwUPA78kAcd+RS5Lvmv6DNRZ3QMhBmK0Cr40LARUC/E+2bHFLo7dxDdPzkPnxwobp0NlE/DOmS4KIu3G6VKZ1gRUy5s7rmykuQTxj2IIyR3N6UABOFdqV8YeNZ+exRjfDm0rP2gVuBt+sLRhsd9Fzrybp9k8cs23P+8rRwJMJeR+2hHEf9tTLEJ42L0ly/CYY2p+/Qkfg77B0UeYDoM6u5rHYRR1v7+rtyTYlmgh2if8fYamyJTko8w92/TfPuGFHZtx98ohP9HjbZvCGnXgvyNQvoX9dS+AfhFC/AB+a34gzoC+get+dfB9rrsb+Aj/wHASZi7y8D4IQpuB3/vneSVVBtBoaMCbPi4YBjIj+7Hi6ZfweW+5lGrjJSnp/8Do1cb7A==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Ledger's Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/ledgers/{sequence}/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful transactions in a given ledger.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"sequence","in":"path","required":true,"description":"The sequence number of a specific ledger.","schema":{"type":"integer","example":0}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"Transaction"}]},"examples":{"RetrieveALedgersTransactions":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/transactions?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/transactions?cursor=116596430667259904&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222/transactions?cursor=116596430667255808&limit=2&order=desc"}},"_embedded":{"records":[{"memo":"FadBcV0owHrsLQif/V2TxZKGA2YiX+MoifI7oB/UjJM=","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GBKTEASNXABG2NC4TY6N3IA5UFC6YW53Y4KTIKY3CUEKQ2W5EIYRMYVB"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=116596430667255808"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=116596430667255808"}},"id":"3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0","paging_token":"116596430667255808","successful":true,"hash":"3a644389bbec63dd2b107a03c16711563fc549daa7b7f56f951a2e470f81f2e0","ledger":27147222,"created_at":"2019-12-06T23:05:38Z","source_account":"GBKTEASNXABG2NC4TY6N3IA5UFC6YW53Y4KTIKY3CUEKQ2W5EIYRMYVB","source_account_sequence":"113943107245989112","fee_charged":100,"max_fee":100,"operation_count":1,"envelope_xdr":"AAAAAFUyAk24Am00XJ483aAdoUXsW7vHFTQrGxUIqGrdIjEWAAAAZAGUzqcAAFz4AAAAAQAAAAAAAAAAAAAAAAAAAAAAAAADFadBcV0owHrsLQif/V2TxZKGA2YiX+MoifI7oB/UjJMAAAABAAAAAQAAAADhZHiqD/Q3uSTgjYEWGVRfCCHYvFmeqJU12G9SkzJYEQAAAAEAAAAAB77j4CQxLlm5aPrq/PDwFhGNs2ldqbdCZwkSfzXhUhYAAAABTk9ETAAAAAB1jYLXrFzNBOWCoPnZSHI3PJAhHtc1TrCaiPuZwSf5pgAAAAAAAABNAAAAAAAAAALw9Tl2AAAAQLSLnL3XT3F6dq5m2WHZ7tH3HBrK/e+p2G7Hrl3WXQToUsgxKIRH6bhHT/mIWwnrfLZ9nlVjMCFoZPqVKrI2lgLdIjEWAAAAQCrZ9IbjDAB408VgQaqNpwX8hXr/OUsoEexkWGkN9PjcBG2nf4bKWdbjiaqHZ+LrvM+DdmhxtA3L9bzmCie8NgA=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAQAAAAIAAAADAZ471gAAAAAAAAAAVTICTbgCbTRcnjzdoB2hRexbu8cVNCsbFQioat0iMRYAAAAAB5tToAGUzqcAAFz3AAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAZ471gAAAAAAAAAAVTICTbgCbTRcnjzdoB2hRexbu8cVNCsbFQioat0iMRYAAAAAB5tToAGUzqcAAFz4AAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAABAAAAAMBnju+AAAAAQAAAAAHvuPgJDEuWblo+ur88PAWEY2zaV2pt0JnCRJ/NeFSFgAAAAFOT0RMAAAAAHWNgtesXM0E5YKg+dlIcjc8kCEe1zVOsJqI+5nBJ/mmAAAAAAAIP38ASptjhEiAAAAAAAEAAAAAAAAAAAAAAAEBnjvWAAAAAQAAAAAHvuPgJDEuWblo+ur88PAWEY2zaV2pt0JnCRJ/NeFSFgAAAAFOT0RMAAAAAHWNgtesXM0E5YKg+dlIcjc8kCEe1zVOsJqI+5nBJ/mmAAAAAAAIP8wASptjhEiAAAAAAAEAAAAAAAAAAAAAAAMBnjvVAAAAAQAAAADhZHiqD/Q3uSTgjYEWGVRfCCHYvFmeqJU12G9SkzJYEQAAAAFOT0RMAAAAAHWNgtesXM0E5YKg+dlIcjc8kCEe1zVOsJqI+5nBJ/mmAAAALEhqMpZ//////////wAAAAEAAAAAAAAAAAAAAAEBnjvWAAAAAQAAAADhZHiqD/Q3uSTgjYEWGVRfCCHYvFmeqJU12G9SkzJYEQAAAAFOT0RMAAAAAHWNgtesXM0E5YKg+dlIcjc8kCEe1zVOsJqI+5nBJ/mmAAAALEhqMkl//////////wAAAAEAAAAAAAAAAA==","fee_meta_xdr":"AAAAAgAAAAMBnjvKAAAAAAAAAABVMgJNuAJtNFyePN2gHaFF7Fu7xxU0KxsVCKhq3SIxFgAAAAAHm1QEAZTOpwAAXPcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnjvWAAAAAAAAAABVMgJNuAJtNFyePN2gHaFF7Fu7xxU0KxsVCKhq3SIxFgAAAAAHm1OgAZTOpwAAXPcAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"hash","signatures":["tIucvddPcXp2rmbZYdnu0fccGsr976nYbseuXdZdBOhSyDEohEfpuEdP+YhbCet8tn2eVWMwIWhk+pUqsjaWAg==","Ktn0huMMAHjTxWBBqo2nBfyFev85SygR7GRYaQ30+NwEbad/hspZ1uOJqodn4uu8z4N2aHG0Dcv1vOYKJ7w2AA=="]},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GDUHYA43LEQWXLJ5GQGNDJHZY6TZN2OK3KA4YQXQ47BRMRDRIUUC4IU5"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27147222"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=116596430667259904"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=116596430667259904"}},"id":"83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479","paging_token":"116596430667259904","successful":true,"hash":"83eabfa824b57436eda49bb9ac28675285f6d945325f69db41792078a83d3479","ledger":27147222,"created_at":"2019-12-06T23:05:38Z","source_account":"GDUHYA43LEQWXLJ5GQGNDJHZY6TZN2OK3KA4YQXQ47BRMRDRIUUC4IU5","source_account_sequence":"113383696345604336","fee_charged":100,"max_fee":100,"operation_count":1,"envelope_xdr":"AAAAAOh8A5tZIWutPTQM0aT5x6eW6cragcxC8OfDFkRxRSguAAAAZAGS0d8AACDwAAAAAQAAAAAAAAAAAAAAAF3q3zYAAAAAAAAAAQAAAAEAAAAASe2g7z3OqB0F+vr+sM6vGMHgnomyJOLJeGMMjT1jgPcAAAADAAAAAVJNVAAAAAAAyGdd4j3sXGNb4PWMyeROuBvzRJJbU+On/O1oSxFvcqwAAAAAAAAAAAAAABcAB2UNAJiWgAAAAAAAAAAAAAAAAAAAAAJxRSguAAAAQG/ksOk2naI/PrA/6qes3c0IhoOpnBghd038S62rayiophPSs3HyUbgbOEpYQCkJezrf1bP+s2fFXVCEXbgveQk9Y4D3AAAAQAINPdxGV1VIeQ1OUDDlqtrSy8FrWQ/+CtRxqVHcHg98SYh5co/gd83R4IGDxukCByTbYapkrUOD0XDJKC/hcg4=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAADAAAAAAAAAAAAAAACAAAAAA==","result_meta_xdr":"AAAAAQAAAAIAAAADAZ471gAAAAAAAAAA6HwDm1kha609NAzRpPnHp5bpytqBzELw58MWRHFFKC4AAAAAAKovMAGS0d8AACDvAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAZ471gAAAAAAAAAA6HwDm1kha609NAzRpPnHp5bpytqBzELw58MWRHFFKC4AAAAAAKovMAGS0d8AACDwAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAA==","fee_meta_xdr":"AAAAAgAAAAMBnjukAAAAAAAAAADofAObWSFrrT00DNGk+cenlunK2oHMQvDnwxZEcUUoLgAAAAAAqi+UAZLR3wAAIO8AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEBnjvWAAAAAAAAAADofAObWSFrrT00DNGk+cenlunK2oHMQvDnwxZEcUUoLgAAAAAAqi8wAZLR3wAAIO8AAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"none","signatures":["b+Sw6Tadoj8+sD/qp6zdzQiGg6mcGCF3TfxLratrKKimE9KzcfJRuBs4SlhAKQl7Ot/Vs/6zZ8VdUIRduC95CQ==","Ag093EZXVUh5DU5QMOWq2tLLwWtZD/4K1HGpUdweD3xJiHlyj+B3zdHggYPG6QIHJNthqmStQ4PRcMkoL+FyDg=="]}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.api.mdx
deleted file mode 100644
index e553abef7c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-liquidity-pool.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-liquidity-pool
-title: "Retrieve a Liquidity Pool"
-description: "The single liquidity pool endpoint provides information on a liquidity pool."
-sidebar_label: "Retrieve a Liquidity Pool"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWG1v2zgS/isDfukL5Ne8Nf5ylzZpmttuk4vTBbppYFDiyOKGIlWSsps1/N8PQ0m27Ljb3O3hesDmS4JwOC/PzDwczYJ5PnVsdMveyy+lFNI/wJUxyrG7iAl0iZWFl0azEbvJEJzUU4WgVrKFMQpQi8JI7aGwZiYFOpA6NTbndBOMBr51o8siZgq0QeBCsBG7Rm8lzvBk5QZ5wSJWcMtz9GjJyQXTPEc2Yit1E1I3kYJFTJKTBfcZi5jFL6W0KNjI2xK3IzmBUssvJYIUqL1MJVpIjQWfSffI0+UdqXOF0Q4dGy3YsN+nX5sqx2WSoHMsYonRHrUnEV4USiYhyN5vjuQWzCUZ5pz+8g8FhWLi3zDxFKklSLysrEyU1Pfu+3IOVfp9qcxiW8p5K/WURazKUgBU37NlxDzmheKekFtJx8Yo5Jotl21gbyuldxHz0its67BcO55Q2E8I4H/q2qro/r8c2xIKOd1wdgvUu2XEpNjlXKNXCvKs4FOppxNv7lH/kfSG3DJiKeIkLlo3pPY4RduOvpTa7w1D/EFmWzsdGM/VxNvSeSU1uj8Qchm33xCw6NDO8AkZ486h36mD56bUu44IesWdn+RGEBGIiUJBke7SsinoZb4r7K1cBmrawHcFb43cDpy2UGlh8A1vd/rWKrNNVl1GDL/yvFAVbN/g3tGCzbgqcZONGr6puoNl3hdu1Otlxsrfje54dF6j7zqPSnHbNXba2yRr1zs8Gh72k/1k8Kp/FA8Ph2n66mAQ9/leioP9weB4/3jvMI77w8FBPEyPjvb3j9KBSAeD4+NXyOP4OPifpph494M96dVuLP6WlNYZGymZSx8ZK9Au2QYz0Dv0iIB+pOtrT57u/Taz/0j/2748NYKaNtmfrsBtamWDwd7R8GC4f7w33H91dPzqaG/d56O9fkOSNB04z7WfFNaIMnDYY5Zke/3+NgeM2EE//HdNh7eLFa+xQb/f7/bDzwGLGiZkZx+vb0bnJ1cH789uLn85/HRxdjj8dPLzweH45vTkw9X16eXRr29PX5+PP7z7xz8vPp2f/zT++fLXk3eXl+PhmC2jloXh2kK/ZeHq3dWfMHC3rH4ilqPPDOVmioHYaY4bsUdls3g0+VGeAyL1hFha9bSSZLsG3JtKDj6gnxt7HyDYrTEtfWnxKTrfNpKgG613NK6mJjwfNUW/q/SyiFEo1e1+t98dUHxlnnP7sJZaT9pcw7ubmys4uboAb0Bwz0Fq8BnCuPKrsdqFCw9ST9F5uibAYqcqpSAdblZViQLih10qSDOnUTkHn3EP0gFyR+OzN0ClXebYXOUztHyK0BqCwaLiXs6QxEmmQBvmCZ1gx1iJ2qOoHLFYUKFrX1EUlK5yqnHojbHYhRsa2CnyVhyxlWKKEKOfI2oyX0W7efPKGhohaNy/R5hzpdC7CAQmqL3lSv6OAvBrknECLAoaQsmDdK5EGzyCJhvegCvjXHpos1IEX0q0D5QiniTURhBzRcFGYCw4b5HngDPUjR/t26R0fbP7qLL+6pVw207o3fOmPQXOUNHb5jaen9rtXmIsdrQR+OIvVT2f9WfdmEu4hhjpCB1hOZMcko/X7yPgEFszd2iDBaMRTBpQWWE9Pv3JfRdrYRLX84Gunbh3hLQBi1ROQVtiaPT8Sp/YJoUHU1qqNgI0gjmCxcTkOWpBRwEorskwSO08ckGXcn4v9RSEtJj4kMOEK+VCnCGt01IKhKpjYnSQmXmARORSS+fRQlPioRwbbGR4nROE5xbTqphD/KerSJ/Ba2Wmawzm8/lm8CvJTqzMtMc7GucdV+oOvUIZdur340XYODhDbcKT+6k1pRa0K9nqhqp2bJJJj4kvLVcgc+p5zEPmQ4akg5z/ZizUTwfEZV686MJbYzdWMTw2pYfaRQKwtrcqDSMw5g4jSDJM7oGk2/GTSTgnaNcATKXPyribmLxX49Cbml6sTNzLOSHdo/aSCbrm6ezR16TVXFWVcv7x4vRs8vbyenJ69svZ+8urs+txNxcvQjJfY2osUlnEOJU6AumfOZgb6zOwKH2YYfU0eEkkIYOLmGQGRcN+t9S08MGI/4QmQJikzBv6GcHLl3MEYUAbT3svYx2CLbUmJxoYKaEVSXGgehJcUTO1OWRVaS9fVvSArsBEcqUegupwdzLjSooQ4OTRy4fUGBbBzw04pDWZp9bSCVpdU47AxJSFqvHJiaRlXhhLA2gov9gEGJXksVTUj3SrVXzdjcag3su55lNa8FHpzXUEBbcoOsLM9ar4TLoZqim8zAMlks36JlEeEaJJQSMKB8/n+EwpaPWddMAdcPjM3vAiPBak7jNbYUclEqZ8m7vLdFyVWWtUa2c2CHVM2qmrsd7U8SRsBeq1YuN2u9zfUmOG5LNoaxTcHPww5zKcolLm7+0zWh3IBLXDlq2TgicZwrBL0/R6Ebk66VQna4s12fBwWn9TBaWu9/7izdmH8Rld6WY+V2ELURjnc65bJpsPfeCwue3dHi4W6y3mf3vtW38Hefzqe4XiMuybQpCLeui/3dru0tJj9HjhexexzDhP8osFkdZHq5ZL+nd4N9no9i5iM24lj2m+vl0wIR39Ldgo5cptb4XbMT+/rjc4L+Df2hV/I7z6n1w/0HRf7VQYi9g9PuzcZS9pv5chF1QOt4ta7iRJsPAtDY/Wy/RZsfqOOj+7YcvlvwCJiFnp
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Liquidity Pool"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single liquidity pool endpoint provides information on a liquidity pool.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","operations","transactions"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"fee_bp":{"type":"integer","format":"uint32"},"type":{"type":"string"},"total_trustlines":{"type":"string"},"total_shares":{"type":"string"},"reserves":{"type":"object","properties":{"asset":{"type":"string"},"amount":{"type":"string"}}},"last_modified_ledger":{"type":"string"},"last_modified_time":{"type":"string"}},"required":["id","paging_token","fee_bp","type","total_trustlines","total_shares","reserves","last_modified_ledger","last_modified_time"],"title":"LiquidityPool"},"examples":{"RetrieveALiquidityPool":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9"},"effects":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/effects{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/operations{?cursor,limit,order}","templated":true},"transactions":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/transactions{?cursor,limit,order}","templated":true}},"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","paging_token":"113725249324879873","fee_bp":30,"type":"constant_product","total_trustlines":"300","total_shares":"5000","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"2000.0000000","asset":"PHP:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"}]}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transaction.api.mdx
deleted file mode 100644
index ea23973c91..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transaction.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-transaction
-title: "Retrieve a Transaction"
-description: "The single transaction endpoint provides information on a specific transaction."
-sidebar_label: "Retrieve a Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWulz4rgS/1dU/vB2ZgPBnCGpmtpnwhEI4SaTY1MpYbexgi0ZScaQVP73V7I5TMLsHLv7dqrWHxLAre5ft7pbLbVeNImnQju710YcU4FNSRgV2kNKs0CYnPjqu3amjRxAgtCpC0juCBFQy2eESuRztiAWCESozbiHo7eMIoyEDyaxiZkcd6ylNOYDj8ialnamDUByAgswEjC0lOZjjj2QwBXEF41iD7QzLcHp0cHC0VIaUSB9LNVnDvOAcLC0M8kDeKdJQk+EOSCTeR6mlkDSwRJ5zCL2CkkHkAvWFDgSEktAmFrIZFQQIRGzEaOAGEce44C2mgillzAd8LB29qLJla/QCskJnWopDZbY8131UxEmVtHUsV3Il4tFXZ8U85ZVyk90sIt2Cco2gJ3FJ5A1y6XT8ukE8qZlmlDOFe28qZum9vr6oPQUPqMChBKW03X1b1/XYWCaIISW0kxGJVCpSLDvu8SMAGeehKJ7eQ+aTZ7AlGoGuFJPkljKo0voTHydToBrf53K4WAfMlTsQdqZpqRprylNgue7WKop3VJPGHMBU+31NTnj9zHTh5QmiYxsveGBTZMFsQV+IlSxj/1koHYO/ZMBA9sGU/5sqHwOJljws8ESKvjB+rlgvSGK8sQuNrfxsOeDu3lP2Dqh38NrSiPWIQU2sokVzROeEjp9lGwG9D31xmJC2IF7SL+UFq01hwa+i2JCJcR6bG1IqMznFLHJQZnwEcvDIFjATXh8n662WvlYSuAqvzfujfSdnj59eCkWXxP6YsviKu/v0t6jFyzhgI3eUjweMuQ7VI8C5gFQEw7S2vDXwU/w+pIKf5bjl1RWhKaD+fQLdvPw8tGGwybYeu/jWzP8kWcAXYDLfHhcWvwgWw4icOXXXnsg8RdplFZ/SOCBxx7jXw/5AZlSLAO+l+0w53ilijAJnvieCXrdzVCC8Wvy56gwEelkWfi6LaUiYQdLx7MXbYHdAPaLlk1ZEic8zZHSF2eZjMM4eWY0LUFICvJYSHBdzI8Zn2YStabI/Pm6ba8O+Q4Y61Ei06g2i7XLwkXnqnLRavUbvXxjfNNvNZvdi3HuvNXNt41K73O19Pl22Gvd9YqdXulkdNXp7Kep75AcDxKZ3MlpKX9SLr4vEP4pa2Z2MF5+MwMuGE+5xCMyxbgFPIr/3YKl9gL7JcQ/hnuN4dtBJyuMH0T9W8T+Exbmf2Kpn7I5Pavni4WcXjgp6OVsrvy2avhzotRW5I9krVftP78Zeruyawek7S/u8b4wXs7/CvmbwNrEyP4ir+X0nJ7Ws+lceZTVz/T8WT5/p71f6bUfju0/WJ+1UlEvlLK5cqlQKpWL+XJee7O0ZXU9sZhF394tX9m3i5NmqKdzMbwsWNygQ69CTzrDco31C6ed8+EJDiv2rc1vZ6fdm1OcyRcV+Z1RpfVlaBhG+8LYfyrR3776Ux3oJLjAYUv3p3dHz+NF5bLW7Y36syAnjJvcRSnX6o3czOfF6VFEX4uGHs193DPEOHPeMIcwLFzSxbx2ujqqmE/Oimfd0hMJyXIgFkE5kjeaWd3rWLYo3DaDWwql0/Aq6Eib3JUK08lJLT+no8GJUVhVC0931eGwHOGzGv6QJKFfbPXrXxXbwwqpD/qXsn476PkdPAmvg0XTuRteD6oYP9n65fMtnre8Kb4x3DoedW9Xt2Y2exssx1fZ+rObvR4VxrVJM5erLLqZ8sXzeNr/pO2v/NpWdKO/g7H7WEmAS4zdrfrabkAzsriB50uS4KVbTe7kxLl1eduwRbYdDp3qk6632pIb9VPnSJKRXrSzPGPP4gHO5767m9zGjn88OU61XGmLu3q/Vs/n+eWwdMv8/niUn5RIu9IoUOFDqZypVjqV2wT22r6L9I1veGqVOW+0dt+/15mM8/rd+djomjeRhwrT2HfO81ovrAXL2bXRv7FB+G2fELcy6FmLeVPUJgRW7gl/Ll/V9Pr0i9grxrc8/e2fqoFpKTc1/v/OHj9tO7N5ym/s8R3zEatSmrusfL4clZt3y1axPZ3DERvl24X6qntxufh8M++2z9v1xuroRLmSUe8O9OI4nplnZ0qKxDrheWNVyGWPWpSTykKMYG51LkT1qdkjnVmn1Q4VvoqO3cumIbfIM+HWft9m/7DhH5US9N+Z7Ixx8WLkxkZqdxvnba+VDxZmtf00uSl4EDQbR8tOydd1CLtX06Nmrq/PFhG+Wb8fDm6eb3bQd/arfRFu4qns4jmm/854/mF/qTyX7oInu/Nj/vLpk/Z2fxJnqsjzrypzO3B21D8S2dXCLrJvjX8ushtzcTvbff9ezzKa17NW3yguTZWezpe7zBDLb/YzxvCkMRhXKtZpaTULvMvLcb12mjtiJBwErZPLm2DRC8NR//OXsX/V09RsJTaLGmUUtP0d4r32PJPNRvO6bsz1a6d2NMv6i8rnUpnU3dZ1rePPO5k+7zhz5uGKb56Pr/2r4lPLeb65Jif1/vP4pntzfd1z+gPxNLltlE8yod0ZVpSnPLzGj8IgHaYKySnIeK+pqrr9kv3lbctA1dkC+GLTWQi4+22VrnaoMzKK6VAHZMi4Oir7Ekc7UKb5Fp71DSWiG64Pqs9hs2iHvd4fX8R8tZSmVIlH68f6cTaqeD0P89WOatelwRRdjEY9ZPSaSDJkYYkRoVHXYxjj2kg9Rk2JCJ2CkCJqgnBIR4YTEXU00ufMCkyw0GR1iIXijJE67ohbLEQgwIIAV6JVTyXwYDMUL4DjKaBEkwJxcLEkC1DkisYHHp2dUBPSjBOgEqwYCAefgwAq410hCkQMagPonHE4RiOHiEjzhB4TTqwpoAnIEIAq8bG2+yN7nKkDVIFcMgMUYtcFKVLIAhOo5Nglz2AhWJoOVgZLRRywEKB0FgHwCBHazIZkSAQTj8hka0yk0DwAvlJTtK7m0QS7StmU6jgJyQF7CBZANziSoxXT3cjjd571b/eE++SEPnzYhKcF8eaGi71d7Rp2xmQc0pRZ8PFf5T2/09/pRpyJKZqAegVC2XJBMDLHg3YKYTThLBTAIwlRY9SOrLK19bB6Kb5qa4uZIiMZc0VGWDOhLM0QB+VOETeTqRO/JZErxX/FAq68TRk0hUJAHFQfF6ilXkWGwlQJRoQKCdhSgzw8I3SKLMLBlNEcmth1RaRnNK3TgFiA4oiZgEAOCyOTWB6hREjgaOPikTtubKNEKBOjDxzs2Jkj/atbTX9BFZdNdzYIw3Bf+S1leuKyaQanKYRpEdC0WoUcSK/Xj48qeJBgKkywOZtyFlBL9dnfREPsO9x0iARTBhy7iHgq5sGLZj6aISKQh58YR+ulA00Cz/94jOqM77Xx8YQFEq0hKgOu5W1dg1kwwQJSyHTAnCFFndRfiUQNZdqdAaZEOsHk2GReZm2HzJRlJi6bZDysLJ1R4UVMEJulM6NOzjnFbuwpjXGzWnusdweP1dp1rd3t1QbDY8/6GE1mBWzVmA9VSE4JTSEifxEoZFw6iAOR0ekGnUYoVZIgEUQwHQbWJvvdq6BFHWb9SJpAFjMDb5N+ztCvv4aALIYok+rOBOMCEA8oVSA2ZlQTGicprO4cUAu7KpiSOWTrab/+GqcHiG5XYNddRayjsY8L7BIrUvDx3coHKjA4IBkyJEBdr5AqtKgJnK5TjgUmC3x3bR9PJWni+YxLTGXkfhMWmdEleEJcFY9qVML5jvcCQ8WehymeqsshyvVCmkI+5mClLRbSrfMxe19V5kviRSlRyVyPVClPJURmI6pOKdGHEH5xXZSIOyIQFgij37Vz7EeLhWL3u7a1nXKR6JSVe6JrD2M3S5Rqe8eaiijN7PTaG9c3KbAZnd+vr6NsYCfdva4CE69vseyXgvuFH3iYRG/Bddl/k+/UgT0xgQpIyDJ8bDqAcse66rdYyndtAnz7Jh2/2UlcJxscvY0P9GOmItNuntc6w5oacuxIz42OZH0mpIdpQuSmv4Iw2r+cs1dZvOyumPwNl4XWWwwJS5nxXUyiJlCk5Mu64L9P3gpS7eGzd7eEHlKaw4RUtC8vKmGNufv6qn6O1kzt7P4hpS0wJ3iiauv7F80iQn22tDMbu+LtVaKkyh8G6672R/R3XzA6aItNJ46qPty686VpKW0Gq0MXpl5Vz9wBbCnXuX9ZkxmmCb5MMHh3VUhtQbb7rUZtpL2+/g/D1ugu
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{transaction_hash}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single transaction endpoint provides information on a specific transaction.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"transaction_hash","in":"path","required":true,"description":"Transactions are commands that modify the ledger state and consist of one or more operations.","schema":{"type":"string","example":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"schemas-Transaction"},"examples":{"RetrieveATransaction":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GDI5EK4HNMBHJJQGP3GUXQJIIOHU2CJO3LABPWD6WYSPJZP5NP67TMNN"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/27963785"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=120103542047408128"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=120103542047408128"}},"id":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc","paging_token":"120103542047408128","successful":true,"hash":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc","ledger":27963785,"created_at":"2020-01-28T10:03:33Z","source_account":"GDI5EK4HNMBHJJQGP3GUXQJIIOHU2CJO3LABPWD6WYSPJZP5NP67TMNN","source_account_sequence":"65046128646685383","fee_charged":100,"max_fee":100,"operation_count":1,"envelope_xdr":"AAAAANHSK4drAnSmBn7NS8EoQ49NCS7awBfYfrYk9OX9a/35AAAAZADnFxwAAALHAAAAAAAAAAAAAAABAAAAAQAAAADR0iuHawJ0pgZ+zUvBKEOPTQku2sAX2H62JPTl/Wv9+QAAAAEAAAAA+qpaPAsU/CGcSeS4KnvqE9y+Bcjhyr1l6jiwixRsvu8AAAABTkdOVAAAAAAs4YIuYne69wMuNtfiZ64gb7E3qnTR7A4yD4jZDSS8AQAAAdGpSiAAAAAAAAAAAAH9a/35AAAAQM5LSBiFRQKtFYRPpNabwVuvIhZSVRDaajf0KzYaqJmgaXAlFaTOYyYc11YuxUM1Fzl1VT4UEbI22BvO/8HzUgQ=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAQAAAAIAAAADAaqxiQAAAAAAAAAA0dIrh2sCdKYGfs1LwShDj00JLtrAF9h+tiT05f1r/fkAAAAAAhWQlADnFxwAAALGAAAAAQAAAAEAAAAAhD8BLsZFQEF33rKS6YopQUT3b6iLBG4nspe68/DBNBYAAAAAAAAAAAEAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBqrGJAAAAAAAAAADR0iuHawJ0pgZ+zUvBKEOPTQku2sAX2H62JPTl/Wv9+QAAAAACFZCUAOcXHAAAAscAAAABAAAAAQAAAACEPwEuxkVAQXfespLpiilBRPdvqIsEbieyl7rz8ME0FgAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAQAAAADAan62gAAAAEAAAAA+qpaPAsU/CGcSeS4KnvqE9y+Bcjhyr1l6jiwixRsvu8AAAABTkdOVAAAAAAs4YIuYne69wMuNtfiZ64gb7E3qnTR7A4yD4jZDSS8AQAAAAAAAAALf/////////8AAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBqrGJAAAAAQAAAAD6qlo8CxT8IZxJ5Lgqe+oT3L4FyOHKvWXqOLCLFGy+7wAAAAFOR05UAAAAACzhgi5id7r3Ay421+JnriBvsTeqdNHsDjIPiNkNJLwBAAAB0alKIAt//////////wAAAAEAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAwGp+6EAAAABAAAAANHSK4drAnSmBn7NS8EoQ49NCS7awBfYfrYk9OX9a/35AAAAAU5HTlQAAAAALOGCLmJ3uvcDLjbX4meuIG+xN6p00ewOMg+I2Q0kvAEAAAkQQwRXzX//////////AAAAAQAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAaqxiQAAAAEAAAAA0dIrh2sCdKYGfs1LwShDj00JLtrAF9h+tiT05f1r/fkAAAABTkdOVAAAAAAs4YIuYne69wMuNtfiZ64gb7E3qnTR7A4yD4jZDSS8AQAABz6ZujfNf/////////8AAAABAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==","fee_meta_xdr":"AAAAAgAAAAMBqfuhAAAAAAAAAADR0iuHawJ0pgZ+zUvBKEOPTQku2sAX2H62JPTl/Wv9+QAAAAACFZD4AOcXHAAAAsYAAAABAAAAAQAAAACEPwEuxkVAQXfespLpiilBRPdvqIsEbieyl7rz8ME0FgAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQGqsYkAAAAAAAAAANHSK4drAnSmBn7NS8EoQ49NCS7awBfYfrYk9OX9a/35AAAAAAIVkJQA5xccAAACxgAAAAEAAAABAAAAAIQ/AS7GRUBBd96ykumKKUFE92+oiwRuJ7KXuvPwwTQWAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=","memo_type":"none","signatures":["zktIGIVFAq0VhE+k1pvBW68iFlJVENpqN/QrNhqomaBpcCUVpM5jJhzXVi7FQzUXOXVVPhQRsjbYG87/wfNSBA=="]}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-effects.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-effects.api.mdx
deleted file mode 100644
index aca9a2bb5a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-effects.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-transactions-effects
-title: "Retrieve a Transaction's Effects"
-description: "This endpoint returns the effects of a specific transaction."
-sidebar_label: "Retrieve a Transaction's Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWuly3LgRfhUUf6yPmvuSNFVbiaTRtZItRYcdHyoZBJpDWCBAA6DGimqq8hp5vTxJqkFyhqMZyfKmduPs+o88QKOPD41Go5t3gaNjGww/BOeGKkuZE1rZ4LIWcLDMiBR/B8PgPBaWgOKpFsoRAy4zyhIXA4EoAuYs0RGhxKbARCQYcXNujaAW6BQMxR8HPBgGp+CMgBvYrMrcyfkEtSClhibgwKBed4GiCQTDoMLxKqY2DmqBQM1S6vD/Br5kwgAPhs5ksKR+RRChBgjTSUIVRxOoI4nmIrr15kjgYzDEOuqAUMUJ08oK69A+rYBoQxJtgMwssmifZTEkNBjeBe42RW2tM0KNg1oAX2mSShzqQ8j7rEWjXne932+1wn6X80E3bEHUjwawHgFEbboGbbY+2FjfCKHLOGOw3ulHXdZiLJhOazM0WGasNiUGXzIwtwsgRFTaJRQ2icqSEExutN9KS5yu7pvUzFtFhCKUMC0leNTQfAM21cqC9bgIS9JMSuAkMjrx2KV0LNT4yulrUOSGygxyrzDAtOErcRLKwRhMFajBoDUYtNd6a+sb/Y12q181WxsO3281ByvGipZ2oKqeERo5iQWLCw0tsbHOJCc0TYGaBjlOc48RismMA/lELftEnlPLQHGhxi/QHT6huE/kOf4phhvkAMUI9LVxloByRFj173/+yxELrkaEIxwimskcf8/2G26ksgRPKbUsyA0MLqvASJEI953AnMdAEvpVJFlSOobf5RyK/IwDbxCk8/wJo4oYqsaQ73kble+0WqROqCJZmoIpCL2DCUtiajjTHDhCva+N+IdWJNKGpGAibRKqGBAD1OI5ehi0cgOBL2HXbj3Vr9qt6fQSQSm8GKk7rRb+WcTlLGMMLEYippUD5ZCEpqkU+dlofrZId1eRSqU8jny0KuTr8DMw3JDUYKRwIpd3JYW6thU9H6CzIKNvU8UGolXO4pF13ivUdTCtBQ6SVCJ8FepQawlUYVSpOMqHnOllLXDCSajwUPDV/WAqpQZufiiVpkhWDh35rcYz+g2fgCQEzhfEPkBanM0KITWG4lEXDpIn+NVT/W92u/1Q8NYCi0cT+BMs+L0dkQGHH0stpBJ8lbCSTnCvfOXWfox6gW5aCyhjOlNu1ZKUOgcGY+neh836+1Z94/Ku359WmFHODcZYtNQvfvjK28zlkG0DHo/abOQUEn2zMLJtgItFohGE90bOYwM21pJbcpHyezz3dQJkpBMq1IrZXUnHq1YdqEjm+cUIrBNFrjGnOxNjBaZiQjEwt6AYmC85N5l1UiiorJqPzRfOx1at3cxcjNfuveER0OrEcRQtaJf/nsvIf1f5Uw5BLRhRRyvL/M/5Kv9zvmhbUpHQUALZotJf/POVK+b8yMK2P0C0sBFneLdrY2ORrnCY6uzyJlZnV+G7mvfq+VV7sZr/zE8RrcfVXyJZtmGJZC5oGb7V0h6ne2w/Hzew8PBv7NAy0YqNWiaaizsSXzLBhbslJ1rLioh7Ew+uOIUbfb1qYgSptmIls7fCxdzQyfJMeVTO4EsGCNJWlqTAg8si8l2JSuzLs/CFpHVaC1huwhVdEWunec5RvQ0ED+4F9XmsLqLtTPQC88tq9pI/x4Mp6llo4y+wR9/uw7vAP/sWU40ymc3vviB2LrXDZjPOnwN1B9YpcA3rQEpqGtqMm5XHvm322x26sdEbhGwtinq0O+h2Njaidi9a24BWCOFGuMF4yFvtVhe6dLBBe71eb0BblA56a2263ixKFH/JH80//+TfKD+3Wz/5V+DP+KaqJLg/iprtTnvQWR8M1tb6vW57Y32tW+88oHqZCP/Aqrfvq+7fsOhxC/nvLMP9UPWghXT0O4ycF2mayyrdzye/g29p7tySnx6x/H6G+KsF0W/JKTK+oLViulX+a98PD8NgJbdKhhfsbe4fru3s7HXevt1/czh6fd7b3vnb7vu9w93O0d7o7G3n4M2r3ll/dNLrnG697R4Ots6PR1u9zTLgDEteV2yeoZXhr7MY4oJOq9Oqtzr1Tuu80x6214fd7nvUxlpwV2WkpE7cYCCjSaFiu7/WbfTb7c6gPfCvrj+I+3R+J/fpPNF9Ok9yn8499+n8/aR3+Opd7/Dt65O3vcOL7YvDdxe7nV/W3g32j/v7RycXO5vdNydvzl69237VPd97vfP+pH+27D58ls2X3tP9Dbznclr8qwUJuFgjKGNw+csmDobBYvi8u1+bnpbIY2kKzE1Zys6MfNrOBatqdec5HXkNbqLNtXfy1RyjzGUGnsJzt6QkquR6iVXESPtco0gGispdUAvQlHx1q9FqYJCwWZJQczunIqnRN4L7MjHZPz8/IZsnB1iq45ibCuXrr2e5XqXUBjlwRKgxWJdXlw3UPXB5j8GvTI3mGQNOwttVLPKKNb6jZ9VHoFZgtVv7In6WQLmU3oChYyCVoh4xIL1XILkvZs8rlHVtBCgHPFfEQGrAgnJ5bCCZzZUqFdrWBrBqKqy3vGJHaAQfAwnBTQAUis+tXVx5YvRn31KR4hrIhEoJztYIBwbKGSrx0UbgK4uxEmtrnoN3byKszcB4jWbVVqeJzUJflK34bI34IjFuUXG0SJhn8TWsaVtngCYEbkCVelRX+6bBbGVjybP+7J7wobqhl8/L48nhBiReKnYhShdqN5k2UFeaw4s/lfd8VB9VKQ4bDCHgFFjE8kZQwi5Oj2qEktDoiQXjJfhOXN7JmWF9Njq038Saa2abTmtpm5ZfW0RaEwPoTp4b0/jS+YrPNx2RW50Z9DYEtEYm4JsjSQKK45QHiioUTISyDijHRQm9FmpMuDDAnN9DRqW03k6/reNMcCD5iQnBklhPPCQ8EUpYB4aULu7dscQGRfhn9nMDUe7M3v7RzNJnZEvq8RyDyWSyaPyMsh5KPW7SuoJJ3WaqjrdQDPXi/njhWzQWK2EhZddjozPFiVb3T0PuO4bFwgFzmaGSiATPPCR+53XRz0noZ21IcXWQMEvSFw2yq7H/ltc9cZiGOsPWjlcRASzkzVxDcwiphRphMbBrgtRV+33DaA+hnQMwFi7OwgbTSbPAoTnWzVDqsJlQRLqJx0swsOXV2cTGkVFU5p6yd3Ew2rnaPT69Gu282Tk6Ptk5PWsk/IXfzC2IsBM8wSM5FgpbU88smWjjsKEonE8e1dhriUFCeBWBxTrvh3nt8dCS15r/mjBBuGa+UeYRHJKXLydAuCZKO+zVa2OBmEwpVKKEETc0D1IUm9yKU4mHqRpDZp728mUeHsC3h6mUt561X3t1Q6Xg3sCrpZsP8GAYIG6iiQXs5zs8WoqBUUXI4cB0lsoCnwSDtEhSbRzW/ND9Qu1hlIKGQuJ5xFUV52ssHAw8ewlVdAyWCHS9iaqRlBrgda4nauZ8Olo0VadOJD4kosxiJYY8DIg6IgrTe/J8As+kJJVzh11KSyj5GGzT1F8WyO5jMMMOXQSzVDCJPY7OcjerpGoLb3EkquuoXnhj0XmkzNcjig5vqXbV3XfxYOYvm9q9VHAx8YOECj8LUuq/VuemtUAKBspCRdZmSlkMpNNoYWuJo+9GAsxspp7PzCUWwYb6WW9TwdQ2jw62d16f7eCSRuwS6Z8ZqbYuoaoisqwrEUoqlaVnlsy/C1nIMe7mzdn/9uOU4lHg4KtrppIK393wtt0V+f6H6tcnqMpwxdcoZcp/WQtibR2uurvDiHVh5HSKw3lfHh8CXFisnD7Qma/a9r//ZmMlPNdwW/0Kpaj6Bf5N8j3G/d98mvEICuVHKb8ShD/QZxiPgFR+oDIH6RJ/GIEofeeZeH5alLtfkN/6w66VFpU1CXVbNai0dCk0+Bp6DBS9BA3NyTYZg7SKyNIXJojQrPywt3MeTKf/AWiHuzg=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction's Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{transaction_hash}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the effects of a specific transaction.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"transaction_hash","in":"path","required":true,"description":"Transactions are commands that modify the ledger state and consist of one or more operations.","schema":{"type":"string","example":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"RetrieveATransactionsEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/512a9946bc7ff4a363299f14f79e0beb9b9cdbd0103e3a69a44446a0aa6471a8/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/transactions/512a9946bc7ff4a363299f14f79e0beb9b9cdbd0103e3a69a44446a0aa6471a8/effects?cursor=121628667754319873-2&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/transactions/512a9946bc7ff4a363299f14f79e0beb9b9cdbd0103e3a69a44446a0aa6471a8/effects?cursor=121628667754319873-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/121628667754319873"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121628667754319873-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121628667754319873-1"}},"id":"0121628667754319873-0000000001","paging_token":"121628667754319873-1","account":"GAHK7EEG2WWHVKDNT4CEQFZGKF2LGDSW2IVM4S5DP42RBW3K6BTODB4A","type":"account_credited","type_i":2,"created_at":"2020-02-20T21:18:33Z","asset_type":"native","amount":"1573.5112616"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/121628667754319873"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121628667754319873-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121628667754319873-2"}},"id":"0121628667754319873-0000000002","paging_token":"121628667754319873-2","account":"GA2XP4KMY4KWNPW4KUCUKYUF2J7Y6HO5HLPUEA3VPVSMYCM3TGNEZP5S","type":"account_debited","type_i":3,"created_at":"2020-02-20T21:18:33Z","asset_type":"native","amount":"1573.5112616"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-operations.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-operations.api.mdx
deleted file mode 100644
index a5845ef863..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-operations.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-transactions-operations
-title: "Retrieve a Transaction's Operations"
-description: "This endpoint returns Successful operations for a specific transaction."
-sidebar_label: "Retrieve a Transaction's Operations"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ty1LgSfhWVfyywNRfP/VK1tQdIgACbABnYC6QGWWrPiMiSV5IzZFNTdV7jvN55klMt2zOezBAuC2yWs/kTYuvS/XX3J8n6uAgcndlg/DKYGKosZU5oZYOTWsDBMiNS/DsYB5O5sAQUT7VQjhhwmVGWHGeMgbVxJolOwVDfmcTaEEpsCkzEghG3HrgR1IJVwwMejINn4IyAM7hdnf5oNVZQC1JqaAIODFp5ESiaQDAOKoNO59TOg1og0M6UOvy3gd8zYYAHY2cy2HKmMhehBgjTSUIVt8TNqSOJ5iI+J24ORAKfgSHWUQeEKk6YVlZYR3RMtAKiDUm0gYr36KJlc0hoML4I3HmK1lpnhJoFtQDe0iSV+KgHEe+xkMbdzrDXC8Oo1+G834lCiHtxH4YxQNyiA2ixYX80HEXQYZwxGLZ7cYeFjAXLZW2FBsuM1abE4PcMzPkGCDGVdguF20RlSQQmd9oH1hKnq6GTmnmviFCEEqalBI8aum/AplpZsB4XYUmaSQmcxEYnHruUzoSaTZ0+BUXOqMwAu1FigGnDd+IklIMZmCpQ/X7Y77cG3cFw1Bu1wl7VbW04fLzXHKyYKVr6gab6gdDJxVyweWGhJXauM8kJTVOgpkGO0jxjhGIy40BeU8tek5vUMlBcqNktTIfXON1rchN/FY8b5ACnEZhrsywB5Yiw6r///o8jFlyNCEc4xDSTOf5+2PekkcoSrFlqWZA7GJxUgZEiEe4jgZnMgST0rUiypEwMH+UcirzigTcItvPjE0YVMVTNII95C41vhyGpE6pIlqZgioY+wYQlc2o40xw4Qv1AG/GHVp4tUjCxNglVDIgBarGO3g1aGUDgW9i1wg/Nq1ZYBawI6TSmQgL/SOSOweHcyDT4u0yPfKwqMQqFVYO2bieT742V5KfY6UWktQSq1vH33Obbb0T/jRbqU12oEGPFFayRjXd5nTADGAUClM1XpbThLj4piaIRLE/QkII20LF2GOKvS7bki0pQC5hWDpTDJjRNpcjJqPnGYruLCkBUyqPYLw8FVDp6AwwrIDVokBP5fFMp1KmtQPqOdhZk/P5WcwPxrur0qex8GarTYFkLHCSpRKR2BHO5rAbnZT7oSS1wwkmojKHgrbtmJqUGzq6VSUtsVj567EONZfF5cgLiGJj7gIZfOwYMOFw3s65hAVmkFX7dgKqw6rWyDFsJvmuysp3gPv8qm7yrWm+0QwvPU5iKSo98y1FdocOi2dX76HwNmlLGdKZcUGWA1TEiWJ4sV308ku87dowvAr9j3SSIMqvzOARz51I7bjbn+U6m7sA6Ba5hHUhJTUObWbO6ajb70WjYoV0IOeuwsBt3I96PRmFnwHq9eBDScMS6nS6PedjqjtoRtMLBgMUDoP0ha0OXNteL64/5lv+H7/wO64dW+J3fw/6AO8LKanGNLG21w1an0xmMWsNeu93qd/rvsL1cVq6z7Z3Ltvs9OCbfFJIIOM9Lr9g9+53Jn0qjtUnNbVt28MhfhR2aUlkoP5eHzXLMkscLIv+I8YsRflyH67t3BvfywvrJ09CrZyk4Ntjx7jKz7m5T/QpiV99iyo8eVmeGralxHNzfe/hLf3B879f24aDzYNCe/PzTo0d3nj7pPX9y5/DRncPnPx3utw/u33t0uH/c7Rx3O+3BL/29B/eDkoiDhCo6g2mUnU91HHu+Lpm81a4VZMynfjFqh+2wHrbq7eGk3Rq3uuPe6LdLNvsvN+PgT2ddLaBJ4WPYCPMfv3oKBuWzVuXZ1GBYVTBu1QKOZ8EwxNUmys4RcmotuGm5LlEnziDwWxq59ZYZ4MJNqUznVGVJd6sdHneDcbA/ebD1SlibgcGw3Nnbf/G83/m1fzh58PDp098OHr2Y3G13Dn9+/PTFk87PD9vPDtpHk+OHk8Nfjw7uH9w9nvT3nv/yDD+mYRCmmESt7mg07LRaQ9zxfjGu6X7zXNP9ulzT/Spc072Ca7ofwDXdf7jmH67Z5prRF+Wa3jfPNb2vyzW9r8I1vSu4pvcBXNP7C7nmMs90rgXNjIaNXhj2Br32ZZ7pdEfdbZ4ZdAc51/QKenoH3ewglI1mG3yy8eZz0MlOjlsx4Jpswi9KMv1vnmT6X5dk+l+FZPpXkEz/A0im/8+GZhfTtEetxjDsDUbDrS1Nu9fvbVFNuxeGnZHnmtGgdyXZ/F32NuHyZFn81IIE3Fxjks3Af41FccE42Kz6i8sxWVbK0RtrzkrxQmbkh5VCsOt2dpK3I4fgFtqc+ruN3SPGmcsMfMiY98qWRJWjnuDVYaz9Z9fiS2pxVxvUAnQl7x02wkYL/cuShJrzdSuSGn0muBcGkAeTyRNy+8kB3iZy6mh5KXic21XO2iAHjgg1A+tyPYGBugfO+ta+Z2o0zxhwEp3vGiLXKOCn8NV9M1ArUN+gvWwjS6DsSs/A0BmQyq0iMSB9ivp7UJQvrO+k69oIUHjT6Q0xkBqwoFxxz5nZ3KjSoLvaAN6TC+s9r/gRGcFnQCJwCwCF0+febvZ8YjR+/rdEilMgCyolOFsjHBgoZ6gUf+Cd61s2x7t3W/Mj+FIgeSl4i1b3604Tm0X+Gr6StjXib4YxRAXFkYhKdLaGKgbrDNCEwBmo0o7Ld8Prno2tzPp/z4SX1YCe3CzLk8MZSCQHu7HsFWY3mTZQV5rDrf+r7HmlXqlyOpSURICvwCKWZ4IS9vzZ4xqhJDJ6YcH4Gbz2KhccrLA+3ntk34s118w2ndbSNi0/tYi0JgYwnfxoTOMd0VvhznH8c50ZzDYEtEYW4OUwSQKK4ysPFFU4MRHKOqAcOyX0VKgZ4cIAcz6GjEppvZ8+rLNMcCB5xURgyVwvPCQ8EUpYB6iey1Pcp2OJDU7hFTI3DcR5Mnv/91ae3iB3pJ6tMVgsFpvOr1rWI6lnTVpXsKjbTNVxFZpDvVg/bnlRjtVYJpSdzozOFCdaXa6GPHcMmwsHzGWGSiISrHlIfOR1oeBJ6BttSLF0kChL0lsNck+j4iq/usTHNNIZinm8iQhgMd8qNTSHiFqoETYHdkqwddV/LxG6j9CuAZgJN8+iBtNJs8ChOdPNSOqomVBEuonlJRjYculsolTIKCrzTLn//GBvf3rv6Nl0b//F/uOjJ/vPjhsJv+WDeQdi1P4tsCRnQqEY6YYlC20cSsiE85sANfNWIkkIbyKwuc4VUN56LFpyqPmn0AThmnlplEdwTL7/fgGEa6K0Q62mNhaIyZRCI0oYMaA5SVGUNSpOJRZTlUNWmfb99zk9gBcEUinP/dC+7/SMSsG9g9OtlQ+wMAwQt9DEAio4HZaWYmBUQTkcmM5SWeCTIEmLJNXGUeV8+kXawygFjYTEesReleRrbBQG1l6+v7ZEYOotVI2k1ACvc71Qq+TT8aarOnUi8ZSIcxY9kfKQEHVMFJ6WyM0F3JCSVOoOdWmWUPIquEtTv1jgcK+CFXaYIrhhB5PYo/g4T7PKVm3jFImN6jquF9lYSJ8o83e4haqrNLua7vewMPMr7tqlreDmxg8SKvxbkFL/q/puWQukYKAsVOa6nVI2B9Ju4DFAcMzdWPg9dv6mnr9Zz1iQDfVvvU/FoLb5+ODu/uHxPnZpzF0i/ckt1dYlVFWmLG/kCSWVO/kblmyIgTe2GRdrgdhn1CcXJxIHb10zlVR4uYL39KI4ALysHsPQqvEONXLlDHBSC+baOux4cYEU9tzI5RIf5+o8PBlwYWkk36XPq3r618t2dyJ0CudVIXKhngj8IeVjnPvbqHOvQKHUJX8iCN+QEvcKkEqN8ieC9IVEt1cYvKUR3rT8vYZ+UWntlZYXguC1vSf4hxEI9Ueyz81nhXTsFvnS/4tip0PFQ6rOqw6Vjm7xsBd+zYFiPaKjebPbjEFazb0tdTEitPr4c39/EiyX/wNkQF9T
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction's Operations"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{transaction_hash}/operations"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns Successful operations for a specific transaction.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"transaction_hash","in":"path","required":true,"description":"Transactions are commands that modify the ledger state and consist of one or more operations.","schema":{"type":"string","example":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}},{"name":"include_failed","in":"query","required":false,"description":"Set to true to include failed operations in results. Options include true and false.","schema":{"type":"boolean","enum":[true,false]}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"}]},"examples":{"RetrieveATransactionsOperations":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a/operations?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a/operations?cursor=120133379185221636&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a/operations?cursor=120133379185221633&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221633"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221633/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120133379185221633"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120133379185221633"}},"id":"120133379185221633","paging_token":"120133379185221633","transaction_successful":true,"source_account":"GDJX67SFY2N73H72TWMKKBQP5UPBNKBNUMNE2IGFKNES43S4327X6DHG","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-28T21:14:59Z","transaction_hash":"6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a","amount":"0.0000000","price":"0.0001000","price_r":{"n":1,"d":10000},"buying_asset_type":"native","selling_asset_type":"credit_alphanum4","selling_asset_code":"ETH","selling_asset_issuer":"GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR","offer_id":149983118},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221634"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221634/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120133379185221634"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120133379185221634"}},"id":"120133379185221634","paging_token":"120133379185221634","transaction_successful":true,"source_account":"GDJX67SFY2N73H72TWMKKBQP5UPBNKBNUMNE2IGFKNES43S4327X6DHG","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-28T21:14:59Z","transaction_hash":"6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a","amount":"0.0000000","price":"0.0001000","price_r":{"n":1,"d":10000},"buying_asset_type":"native","selling_asset_type":"credit_alphanum4","selling_asset_code":"ETH","selling_asset_issuer":"GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR","offer_id":149983119},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221635"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221635/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120133379185221635"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120133379185221635"}},"id":"120133379185221635","paging_token":"120133379185221635","transaction_successful":true,"source_account":"GDJX67SFY2N73H72TWMKKBQP5UPBNKBNUMNE2IGFKNES43S4327X6DHG","type":"manage_offer","type_i":3,"created_at":"2020-01-28T21:14:59Z","transaction_hash":"6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a","amount":"98.5005752","price":"0.0003494","price_r":{"n":17471,"d":50000000},"buying_asset_type":"credit_alphanum4","buying_asset_code":"ETH","buying_asset_issuer":"GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR","selling_asset_type":"native","offer_id":0},{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221636"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/120133379185221636/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=120133379185221636"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=120133379185221636"}},"id":"120133379185221636","paging_token":"120133379185221636","transaction_successful":true,"source_account":"GDJX67SFY2N73H72TWMKKBQP5UPBNKBNUMNE2IGFKNES43S4327X6DHG","type":"manage_buy_offer","type_i":12,"created_at":"2020-01-28T21:14:59Z","transaction_hash":"6b983a4e0dc3c04f4bd6b9037c55f70a09c434dfd01492be1077cf7ea68c2e4a","amount":"291.8057980","price":"0.0002565","price_r":{"n":250039,"d":975000000},"buying_asset_type":"native","selling_asset_type":"credit_alphanum4","selling_asset_code":"ETH","selling_asset_issuer":"GBDEVU63Y6NTHJQQZIKVTC23NWLQVP3WJ2RI2OTSJTNYOIGICST6DUXR","offer_id":0}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-payments.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-payments.api.mdx
deleted file mode 100644
index 329df8c079..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-a-transactions-payments.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-a-transactions-payments
-title: "Retrieve a Transaction's Payments"
-description: "This endpoint returns the payments of a specific transaction."
-sidebar_label: "Retrieve a Transaction's Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlWulyGzcSfpWu+REfxUukSJGsSmVlWZJlK7JsyUp8qGQM0EMiwgATACNaUbFqX2Nfb59kqzEz1FCifMTZjbP5RWmmAXR/+PpAY64izyYuGr+NDtllitq76LQRCXTcysxLo6NxdDyVDlCLzEjtwaLPrXbgpwhZOQZMAgxchlwmkoO3TDvGaXgrakQmQ8vonz0RjaOX6K3EC9w8vpZyi8UbUcYsS9GjJa2uIs1SjMZRbcqzKXPTqBFJ0i1jnv62+GsuLYpo7G2OtwyorQTMInCTpkwLMoJ5SI2QyWUwSKGYoAXnmUdgWgA32knnyUCjEYyF1FiEhUmODHR8iimLxleRv8xIW+et1JOoEeEHlmaKHvUxFn3eYcl6b9jvdzpxvyfEoBd3MOknAxwmiMka28A1PhyMhqMYe1xwjsNuP+nxDufRfN5YoMFz64ytMPg1R3u5BELClLuFwiboPI3RFkaHzXTgTX3jlOHBKpAaGHCjFAbUyHyLLjPaoQu4SAdZrhQKSKxJSzJMpJ6ceXOOGi6YyrGghUVurFiJk9QeJ2jrQA0GncFgbWN9Yzjqj9Y6/brZxgr8cqsFOjnRrLKDVA0TkZGzqeTTUkMHbmpyJYBlGTLbgudZwRipucoFwnvm+Hu4zxxHLaSePCA6vKfl3sN9+ikft2CPlpHEtUlOvAbp9L//+S8PDn0DpAeBCctVgX+Y9hM00nlKPsocjwoDo9M6MEqm0n8hMMdThJR9kGmeVsQIu1xAUXg5ihaQXJgfONNgmZ5gsedrpHy304EmMA15lqEtBQPBpIMps4IbgYKgfmKs/M1oSIyFDG1ibMo0R7DIHPnR3aBVG4jiFnZrnc/l1VpnPj8lUEoWk3S306GfZVyOcs7RUSTiRnvUnkRYlilZ+Eb7F0dyV7VVmVLPkxCtyvVN/Aty2pDMUqTwsljvTEl97mp63iHnUCWflppaTFaRJSDrAyv0eTRvRB7TTBF8NenYGIVMU1SpEeVtMelpI/LSK6zNofGD/8ZUyixefFMqzUmserQftpp89BOcwDRGIZaWvUO09M2aILOWkatLj+ln8OovzL9a/v/GNMMkQe4/A9X/qVaOohiKb02tzCJHgd+WWjeEAvuXGXe9yzVka9aczhuRFKvUrVaSIphfK5FuSy/T/MwViSjJ1SrLGpEzueV4xjg3ufarFs+Y92gpqe2+3Wy+6TRHp1f9/rymFhPCUrKjpcPgj5WwZbVfCZ/JlSZwi7QbZ2yFSjcsDIX8KiHmHPqz1RotXlNlQa+r4ohKvAuMggZC+jOmsinTebp++9FaN2xZMY90Lkf71fhRTfT1m2C+egqWrqbDTZpLEd0g5J30u8W1ki0LHizt+oo9XtrREqpg7ELd0/ly+jysuEb7VFIwxIWPHx/HV1E4eSxnuyqfFTElmnqfuXG7PS0q0qZH5zX6lvOoFLMtYyftmgmunQxH3dFwuC4S3h8kyUgMY97tdvhGnMRshP1htzMcrfcwZqNB0uvhkHU2hhusH8dDtj7ojtrVOfmH4uD2/XehTv5+rfNdOIl8T3V9rcj6ZvTs9Ybd4XpnYzToDfvd4dodeleV2F9G73CCIrotVV+1+uqruHPdHGjfVGRFKfNngXajdvlj7GtXM94oQb5g9nKGH6536rs7dvVmQfG7F2EfW6NM7dGtNzfT+SqJu/J50aW6mcGj3a2D7d399b3XT9d/ftLdPRl0XzxbP3zRf7z++qej128OH231Dk52Bic/HhztvPrx0c5PvZPe42fPXlcBeRyVc52laCe1AD0eLifmqNvprjc7G83u6HhtNO71xt3em1WRexx9Nc8a0R9ioNSUHKPdRzube0/6Pz3bfPpiY+Ngd/Doze7G8e7J7s9PDn9eP3qxv/d049H2wdMft0623hy9enN4tHe0tf+qH45nZZJJ0U8N7ekEfZFeydBl97q6CcV8EWUoH6K9qDqUuVWfx7poVQvmuJCDA/QzY8/DiXH1jEnuc4ufM+dOJQm6mvWUAEyK6qJMsWVDJmpEZEoxutPqtNZCkZumzF5eS0FmzYUUofsHT46PD2HzcI86MIJ5Ru0daqsdFXpVq7Zgz4PUE3S+aBpabAbgiuZxGJlZI3KOAuLLVVMUjUiq+RdNJWROUhPThN5snmI1lF2gZROEWq8GLKpQFZJ46FFeN56axkrUHkWhiMXMokPti8gGuSuUqhTaMhapGSZdsLxmR2ylmCDE6GeImpYvrF0eeWgNnXMcKHmOMGNKoXcNEMhRe8uU/A0F4Ac+pQaba4QZQtEERX0aNFo00bwBl8eh11YjbQNC74+2qHQ5iJkiYxvUqnTeIksBL0LLPuhRHx16wYuRrVvM+rsz4W19Q0/vV+4p8AIVpUS3lGFKtdvcWGxqI/DB34o97/Q7XS1HfeMY6RU6wvJCMuCvXu43gEFszcyhDSuEC5aiQb/A+ujxM/dJrIXhru2NUa7txLkjpA1YJDqF2bih48MH6S9p/kuTW2IbAdqAGYaed5qiFvQqAMU0LQxSO49M0KCUnUs9ASEtch/2kDOlXLAzbOsklwKh8JgYHUzNLEAiUqml82ihonigY4UNLRHa4PctJgWZg/2PF5beg0fKTK4xmM1my8YvJJuxMpM2a2qcNV2um5SFptgs88eD0Hl3htyE8fOJNbkWYPRNbyi4Y/lUeuQ+t0yBTMnncXHVF9r0KfvFWChTB8R5mj1owY6ha5WiR0OPWWxy6tgHFQnAcr0FNYzAmDlsAJ8iPweSrtsf7gF2CdprACbST/O4xU3aLnFoT0w7ViZup4yQbpN7SY6uSp1tug+wmqmCKbuv9h5vn+08f3n2ePtke//54fbLo1YqHoTNfIQJXfDNyCUnUtONwz0HM2M93RNJH0pfPQlaUpCQQUXkU1NccwTtyWnhwIjfEyZAGB7uPwKCY3j4cIYgDGjj6RLWWIdgc61JiQpG2tAiSDG6u9SCKXKmegxZMO3hwyI8YLj1Y0pdhqnD2LMLpqQIBp7dynxIjmER/MyAQ7qm9eRamqPVZcgRyE2eqRKflIK0TDNjPdM+0C82AUYlWSwV+SONqpGvteQY5Hsp02yCDiRRb6YbkDGLoinMTC/IZ5JlU03mZRpCIq1ZjqSQRwHRJKDpWAL3Z3hPKaj5HV0+OWDwLtpiWUgWNN27aIEdUYSqZLSpe54cFTSrlWpLhzUSapqkWbKxvFBiPBzxy4u7Su063XfIMVnZd1wuBZcLP0yZDG9RKfOP+rt5I1KSo3ZYW2szY3yK0G11qJoWxN1EUuOrfNMs3lyvWAYbFt4Gm8pJXXt/b2v74GibhrSmPlXhmJQZ51Oma0tWzRpgUGvX3HNQu+9fKjKuri/dvvqzg/JE5PGDb2eKydA0DdZdlSX/2/p5h3QZr+hcZbXvIqbGeRp2dUVB65VV8zk9Lm5c6SwgpGOxuuvOtW7dn38bvxKfc7ysf19QNtOicCz5EuP+MpfuH0Gh+tzgd4Lwf3TB/hGQqk8PrkE6pX+sJJS+0Cfuvyz70w/gv/3JzkqLqh6KvqwbVFl6KzaE3vQUGbGEDC3ENjnHrI7IrW8HCKFFC2J3+ziaz/8Deg0DFA==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction's Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{transaction_hash}/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the payments of a specific transaction.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"transaction_hash","in":"path","required":true,"description":"Transactions are commands that modify the ledger state and consist of one or more operations.","schema":{"type":"string","example":"5ebd5c0af4385500b53dd63b0ef5f6e8feef1a7e1c86989be3cdcce825f3c0cc"}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transaction","effects","succeeds","precedes"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"transaction_successful":{"type":"boolean"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","example":"payment"},"type_i":{"type":"string"},"created_at":{"type":"string"},"transaction_hash":{"type":"string"},"asset_type":{"type":"string"},"asset_code":{"enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"from":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"to":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"amount":{"type":"string"}},"required":["id","paging_token","transaction_successful","source_account","type","type_i","created_at","transaction_hash","asset_type","from","to","amount"]}}}}},"title":"Payment"}]},"examples":{"RetrieveATransactionsPayments":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=3382840796385281&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629/payments?cursor=3382840796385281&limit=10&order=desc"}},"_embedded":{"records":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/3382840796385281"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/3382840796385281/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=3382840796385281"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=3382840796385281"}},"id":"3382840796385281","paging_token":"3382840796385281","transaction_successful":true,"source_account":"GCNEGL4IYJ4XH2GV62QK4PQ5D4YWSYZPBC3NVF6VMNSFUMBFW3V3DKKY","type":"account_merge","type_i":8,"created_at":"2024-07-29T19:33:23Z","transaction_hash":"f8929884dfc56ff9d8bc220c7bfba9e58208943eba96f33e8a0787a5bb8a4629","account":"GCNEGL4IYJ4XH2GV62QK4PQ5D4YWSYZPBC3NVF6VMNSFUMBFW3V3DKKY","into":"GBFAIH5WKAJQ77NG6BZG7TGVGXHPX4SQLIJ7BENJMCVCZSUZPSISCLU5"}}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-account.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-account.api.mdx
deleted file mode 100644
index c22e1454ff..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-account.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-an-account
-title: "Retrieve an Account"
-description: "The single account endpoint provides information on a specific account. The balances section in the response will also list all the trustlines this account has established, including trustlines that haven’t been authorized yet."
-sidebar_label: "Retrieve an Account"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ty27YSfhUM/jTpoSVZtqzEf86RI8d2Il/iSxLb8WggciWiBgEGAK3oaDTT1+jr9UnOLEhKpCTHSpP6uNPmjzPkYi8fdhfY5WpMLRsYun1NW76vEmkNvfFoAMbXPLZcSbpNz0MghsuBAMJSIgIyiBWXlsRa3fEADOGyr3TEcAlRkjBiYvB5n/v5mgpBPj0mmPTBEAO+o+WS2BCIBhMraYAMuRCECaOI4MYSJoR7b3VirOASDLEhN1NFQmYIGMt6gpsQAo9w6Ysk4HJQXsKQ9A7k77/+ZkkPQBKW2FBp/l8IyAhshXpUxaCdAQcB3aanYDWHO2jJDBnq0ZhpFoEFjYiNqWQR0G2a6dLlAfUoR8RiZkPqUQ2fE64hoNtWJ7AI68yO33/9zZA46Qnuk1sYEZC+CiBAdBjpMQMbdWKsRrM0xBoMSOtURb2NH0LE6PaY2lGMCqWU1KPwhUWxwEd77cN3747eHG5edJrvDlpbWyfN0/rJ1f7hu4OjD1c7h83mzu7O4X7n9cd2483uRWt/703zdPPNFZ1MbtCQdHcMCqnXavinbMwp2ERLQwKwjAtDBL+dbbZH0uXahDw2BKxfIaynEkuYnLoH9aivpAVpkTuLY8F9Z2L1F4MixgU7mRDHfbcFmcWq9wv4boc07qLlqapdweWtKSBzD50B0X+YKtTQX4Zy6vh0m6I0OvGohSgWzOLGT6l7Sglgkk4mRb+4TpneeNRy6zYq5yHhi31iKsUa7p6UShMkyx913FZPvAd9AqIeBEFJ7D2kGnylg6L/MK3ZCKPcQrSCX/2F/c9qJg1zOXoFAx5VtWmefmqKxWwUAR6hT0st6PfBf3JaqX7fnaNPSimrWQBPTamAWfakVJojctlrLmOUorQQGTNvnHrAFPXM0puJR3mwzJRcCx6gHYVr1xLamFkLGq8me9ettava2subcaMxKXBhQaDB4JFBDXxOQPrwdUbXyORfBQ7TZQUWXQHBAHSBE5cW8ElhKxIu7UZ9Cad8dZGh5dESxZAi6YG0etRNr6dflbggsLwWIZd94farG4CxXLL0ZvedyIYqgm6gIsaX8Jp4VDBju5EKeJ9D8MewW8pigfW9KNpQgwmVCFYIe6GG3Sn9EjUnHo1Q1tdJQj4Iv05TuNYU1Jt4tC9ctfaQnljbdGchuhjmXk5yp3zWE/AVGh5FiX2Axhds2GP+bRckUt6XWXKbUismHs0LhK/dsJgcrXTXz3itEsKfPlXcf8bNotf6idYg/ZHzHf454QG3o26slFiaYhxVxO2PEdhLRlwOuoKzHhfcliD5DrYGhPhT+Kb13GOHNDfdWdm+3B9LJF2ruph6LONyOQbllav4sUeZMWC76fMlNbdMIjwVMYHeAb2ZPy1zP83dp8RvmSMs3cV7YJ6HaEU8lhtfOPd3UqU7XMJRatfDhdYPDsh/Qu37TuJ/wrIYlh71NQTcdpmIQyaTaHPx0Xrd3UVTvtiPW5ru0tfcmOS7N+nbMkVBrzkt/gJZpIX6rpBEVjuIV9v6OV4mZBqM2+Knmqr+xJj9UWnlKcT+XNws+oz3UCz9v8Kgk6t6opSgE3dZMHwgy52Rb+w63sLou7d1CHwQrlRT4r3+gcCDoN5orL/sph84uqifR03I6o2tbshM6CwAV0nYLy4gf4x3zvlFKjezLNO6sC057pN7Wy7Ylk+irlNOOXWW1ndTGihXXwWSHxV9MRtgSrfqFpbV13MAuEgofa2adjAWugn3xsSSsrpUROdFaqG6m/l0huwCjvOgzVl2Myn3+vMvchP0lewjl3P9xY9222N6x0QC5XZ83nBPm2Y0tDY229Wqi2wl1ywYK8FWjAUhmK4oPahmuJnqXuvyuNPpXBxc7W62rw53dupXO2/3di52rjoHx5cXWx9fdz5sNPd2Turvr9obrZ2jj68+bO68by3rqj+m/GpR+PjffqKN0p5Lh57SAWjnY7PmIH6zXOi2P6rCM9Grq1vswT+qsrng1VUt9OUfVdNM7je4wLRV/7jb78Suruasef/YYRXAN6iZny2PqiQKrY5vYbRMp6zhTv9wZis347+Hz6wTT9frtfWX9Y3NzebL9fUXzc1mbfGU2m7cd0muv1ivNV6s1xeP7FrpEYJQm+8Cz/V5awtt3dpiF7dWbM/ONWD7TBhY7LkWHxfarMXHi9df97bUO70u9FroRqWW/ptedbfpy3p9Y6NZr21svWhUNpvNxotac7FIdLdHWiusn68YFynuwb758sVmo9ZcqA7SMZilt/rc6EIlt6xELxbjdPfi9Hy+9kXvO2l0ds+P329dHuxu1S9bh42ts/N26+jktH3cvHrd3tk7O9p/8+7gcm/v7dnh8VVr//j4rH7mqtEZkJtPBMjG+sb6twCZvvomHC/O2ktgbF+8Pdy72GtfvXu7dbl/2WpcbbUu63ubH9tnVydnVxtnHxoXRxut0/eHx1vvzk7bH04al53dj3MwNuuVF42tjebL+o8BqmRY1szBEaVp1XQ9nhYv615aC31PQsokLSlhUGqWyxdu4tQNp7g7awQ2VJgVB5COkNmQbtNZSh/PUufEIaDvcjsSLVY7IOiykb3zlI4cgR0qfev2ZTnHfmITDavwfJ1TEplzvXGfDpWrPrLr+X7Kl3oUTUlX1yq1yrpL4FHE9GhGNRshZJLsn5+fkNbJAbGKILb5eOBZqlcutUIOLOFyAMbisoBoWHPAGUftVsZaBYkPAemNlrFIR+uwlk2nA7khwAwHjaJ9JU0SQb6U3YFmAyCFoTSiQTjnQ3KkiUG7wlj6sKY0B2khSBUpD+wZkphUqVyhV0oDDkdy4ywv2NHTPBgA6YEduonFOE6tLa880Qqr02zmbsiEAGs8EoCPJyUTbsQRvvghQ8A8x8FFEUlj3WlE8t2wipikF3FLiuWCRz4noEeFeb18uM8jSuNoIrCIwB1egFM9iquRaXnSr+xZf3dPuC5u6M2zPDwDuAOBNZApXQYztau+0rAmVQDP/1be80l+krk4n0nSc1PJYBDLO86If3Ha8XBqVquhAe0kKAlE9R0qU6zP2m/Ng1gHyjdVq5QwVRPcGkRaEQ3oTo6br7D18IXbEfIfqUSjtyGgHhniVLOvoghkgK8cUEyiYMKlscACXBSxWxzrDbgG37o99JkQxtnptnWQ8ABIGjE9MCRUQwdJEHHJjQVNchd37phjgyIQYvJMQz91Zmd/e2rpT2RHqMEMg+FwWDZ+SrnWE2pQZWsShmsmkWt4CoWwlp0fzzF4iFEYJsy/HWiVyACHwOeiIfUd7Yfcgm8TzQThEcY8uMI53SFuSMR+UZpkRwfpJVH8vEJeK12aMU/nhzMVEcBM3tQ1VAA4OO0RPwT/liB10X4USfYQ2hkAA27DpFfxVVTNcKgOVLUnVK8aMUS6iuHFfTD50VnFnp6WTKSesndx0N7tvj4+7bZ33+92jk92T88qUfDcbeYO9JUGdIseDLj0CLc/GTJU2oZEA7eu14Fz6zhuDxI7azhp74cqHQR32mPQkiMV/JE0QQLlJ1GefrbJzz8PgQSKSOUG+pU2QHQiJSqRw4gbmiYpRtCfAiYwmIo5ZOppP/+cpgdwo/9MiJFj7dZ275jggTOwu3DyAQaGBmKHihjAIXuLoSV90DJLOQH4KolFhk+ESZpHsdKWSevcr6ccjPnFceRWFZyvUgoMjL2ISTbAXy6g6w2lR2KmIVgL1FBOnU/1y6aq2PLIpUSUma3ElIcJUfWJBAgMeTaEn4QghbjDSX9DGPlEX7HYHRbI7hOdYocu4ipzHZnj/lnqZoWrWnFnHdGa6q9l3phNzjPfdTuzHyXkahfd/TUGZjrX5c1dBcsXP4gYd29BCPWf4jv3fcsHaaAgqxUzPwRSr+AFnQfou33uioj0zVr6ZiYxSzbMvXU2ZUxNtXPwavfobBeXVEIbCdfEjpWxEZMFkXmjFxPq7PcZpWvFePZ7gr/NT1iyasXCF1uNBQ7dTTLcx1nlcZ23arAZv11o29zgsJ6xSDEeY+a80GIywcfu8Kbb1zcevWOap02K6zENuCkX7/fC/+w0a4U8Jz/sVy9LTc0/mEn80pP1/SnNy8CCte7LQQgsQDe9zr6Z4XcFiG1h6cLPULDcmVZ0e7vndDL5H1H1c/M=
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Account"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/accounts/{account_id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single account endpoint provides information on a specific account. The balances section in the response will also list all the trustlines this account has established, including trustlines that haven’t been authorized yet.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account_id","in":"path","required":true,"description":"This account’s public key encoded in a base32 string representation.","schema":{"type":"string","example":"GDMQQNJM4UL7QIA66P7R2PZHMQINWZBM77BEBMHLFXD5JEUAHGJ7R4JZ"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns details like balances, sponserships etc. about an account.","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transactions":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"payments":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"offers":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"trades":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"data":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","transactions","operations","payments","effects","offers","trades","data"]},"id":{"type":"string","title":"id"},"account_id":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"sequence":{"type":"string","pattern":"[0-9]+","title":"sequence"},"sequence_ledger":{"type":"integer","format":"uint32","title":"sequence_ledger"},"sequence_time":{"type":"string"},"subentry_count":{"type":"integer","format":"int32","title":"subentry_count"},"inflation_destination":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"home_domain":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"last_modified_time":{"type":"string"},"thresholds":{"type":"object","properties":{"low_threshold":{"type":"integer"},"med_threshold":{"type":"integer"},"high_threshold":{"type":"integer"}},"title":"thresholds"},"flags":{"type":"object","properties":{"auth_required":{"type":"boolean"},"auth_revocable":{"type":"boolean"},"auth_immutable":{"type":"boolean"},"auth_clawback_enabled":{"type":"boolean"}},"title":"flags"},"balances":{"type":"array","items":{"anyOf":[{"type":"object","properties":{"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"liquidity_pool_id":{"type":"string"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"buying_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"selling_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"sponser":{"type":"string"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"},"asset_type":{"type":"string","enum":["native"]}},"required":["balance","limit","asset_type","buying_liabilites","selling_liabilites","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineNative"},{"type":"object","properties":{"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"buying_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"selling_liabilites":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"},"asset_type":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["balance","limit","asset_type","asset_code","asset_issuer","buying_liabilites","selling_liabilites","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineAsset"},{"type":"object","properties":{"liquidity_pool_id":{"type":"string"},"asset_type":{"type":"string","enum":["liquidity_pool_shares"]},"balance":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"limit":{"type":"string","pattern":"[0-9]+\\.[0-9]{7}","title":"currency"},"last_modified_ledger":{"type":"integer","format":"uint32","title":"last_modified_ledger"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"is_authorized":{"type":"boolean"},"is_authorized_to_maintain_liabilites":{"type":"boolean"},"is_clawback_enabled":{"type":"boolean"}},"required":["liquidity_pool_id","balance","limit","asset_type","last_modified_ledger","is_authorized","is_authorized_to_maintain_liabilites","is_clawback_enabled"],"title":"BalanceLineLiquidityPool"}]}},"signers":{"type":"array","items":{"type":"object","properties":{"key":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"weight":{"type":"integer","format":"int32"},"type":{"type":"string","enum":["ed25519_public_key","sha256_hash","preauth_tx"]},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}},"required":["key","weight","type"],"title":"signers"}},"data":{"type":"object"},"num_sponsoring":{"type":"integer"},"num_sponsered":{"type":"integer"},"sponser":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"paging_token":{"type":"string"}},"required":["id","account_id","sequence","subentry_count","last_modified_ledger","last_modified_time","thresholds","flags","balances","signers","data","num_sponsoring","num_sponsered","paging_token"]}}}}},"title":"Account"}]},"examples":{"RetrieveAnAccount":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA"},"transactions":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/transactions{?cursor,limit,order}","templated":true},"operations":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/operations{?cursor,limit,order}","templated":true},"payments":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/payments{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/effects{?cursor,limit,order}","templated":true},"offers":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/offers{?cursor,limit,order}","templated":true},"trades":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/trades{?cursor,limit,order}","templated":true},"data":{"href":"https://horizon-testnet.stellar.org/accounts/GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA/data/{key}","templated":true}},"id":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","account_id":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","sequence":"120192344791187470","subentry_count":5,"last_modified_ledger":28105812,"num_sponsoring":0,"num_sponsored":0,"thresholds":{"low_threshold":0,"med_threshold":0,"high_threshold":0},"flags":{"auth_required":false,"auth_revocable":false,"auth_immutable":false,"auth_clawback_enabled":false},"balances":[{"balance":"3.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":27984507,"is_authorized":true,"is_clawback_enabled":false,"asset_type":"credit_alphanum4","asset_code":"EURT","asset_issuer":"GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"balance":"4.0000000","limit":"922337203685.4775807","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","last_modified_ledger":27985131,"is_authorized":true,"is_clawback_enabled":true,"asset_type":"credit_alphanum4","asset_code":"USD","asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"},{"balance":"72.8563792","buying_liabilities":"0.0000000","selling_liabilities":"0.0000000","asset_type":"native"}],"signers":[{"weight":1,"key":"GAYOLLLUIZE4DZMBB2ZBKGBUBZLIOYU6XFLW37GBP2VZD3ABNXCW4BVA","type":"ed25519_public_key"}],"data":{},"paging_token":""}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-operation.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-operation.api.mdx
deleted file mode 100644
index b249aa344d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-operation.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-an-operation
-title: "Retrieve an Operation"
-description: "The single operation endpoint provides information about a specific operation."
-sidebar_label: "Retrieve an Operation"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGdlu27j2Vwg+3C6QbXmJ0xoY3Js2aRKkTdJsXdLCoMkjiw1FakjKbibwvw8OJdly6nY6cweDAOOXROLh2XfdUc+mjo6u6UkOlnlptKOfIyrAcStzfKYjepECcVJPFRBTgxHQIjdSe5JbM5MCHJE6MTYrT9nEFJ4w4nLgMpF8dbFNI7p8OBR0RM/AWwkz2NFLJmhEc2ZZBh4ssndHNcuAjqgUNKISmcqZT2lELfxaSAuCjrwtYBPnh7tEF9kELEmMJT6Vbp0Zx1PIGB3dUX+bIw3nrdRTGlH4yrJcAR11e93h815v63k8iLvd4fYgXiyiJU9fjNQ1V78WYG/X2EqYct/wdQ6eeEO8ZdoxHtSOz1JzVQggPoX1s3kqeUq4BeZBEGA8JSYJYEtRUP/hjQWXG+2gTRefkZHyyaGAvTjGP/d4KTgH52hEudEetEcQludK8oC488Uh3F1DUUypkySYpVKZmXwB7tFqFhnysqQ3VlLfuIZqvwPnQCV/DJVaSDaZqfQ6OqJIjS4i6iHLFWqqAT0xRgHTdLFoGue6RPo5ol56tPQSh4av/oGxlFuYPSiWFghWv3odTI1h8ff4BCQJcP8TgP+0DTgIeGhsPcAAcphWxENTVCOrPijOEEqKTcRqOCmC/7Gp1NOxNzegfwS9Bocc3uYwlo0bZUlsFrm4AvthJaRlDRozzk2hPW1mgFX1XnxeLO8ETW4q8aM7OmOqgPWkUHtyqXuaep+7UaeTGit/M7rlwXkNvu08KMVs29hpZ1UCO/cLdX97g9H/BOpmEe4kz3vs+XDwjHfjZwPRFRAnYvvZMGGMb4kt6A7722LQ7W3zYfxs0BW9/nDIt2PRg+1ke3vybAtZaWS1v0vCTo2zDroq6v4E/grDf40VYH/B9uA/vLDO2F82K7SZBf8yGfZjKlVA0A1n98NgM0zDdmNX9jhJoeo+0ZnC8pUfj+j+i92ro71+f//q6s2L9++3+ycHhy/OTodnOwdHBwfveqeD07dXV8PL45Ojty9P3l9u7x9fvhm8PaR11NCMaTaFsUmSEFh1yPWjKmjEOCSNXtyLW3Gv1ete9OJRNx71uh/vsZsyl9IR/b8dLqIsq8TrxnEct+PyFzKd5Mh03I6340G/P6zfjS1aVdPRYBD3uhEVdDTsbcUxpodJcYtqZ86BH1dScwtC+jFTecp0kQ3oPTBuBIJdnu/eP5HOFWBR9buXR2/2L/d3P749Gn44+LCz9XG486G3P3i/e/7x9Pxj//zd1uVxf+fs6s3J8O352e67060Pr/fe01D41DcsaeblDHDOQFOM0Y26w+5WfzjoDxflL6IZ+NSgg00hZH4cJ0a0GWp3UiwCCTurp5DCqp/zdbppErko4cgx+LmxN6FZ2owxKXxh4Wdwvqohia6xfsZZJDEhj1ep+aDESyOKopS343bc7qJ8RZYxe7uCWk10TJODi4tTsnN6iOOJYJ7VU8Z5yVdNtU0OPZF6Cs7jNUEstILiXIAON3NrRMFBkMntJhSImeGMlhGfMk+kI8CcBIukudGuyKC+ymZg2RRIY0whFlSwexisUiA52FCoNYeWsRI0jk6BEQu5BQfaV4NT4UqmaoZeGgttcoGTIkrekGNipZgCmYCfA2gkX0q7fvPUGuwnHFHyBsicKQXeRUQAB+0tU/I3HOK+8pShwqKAITgwKUMicERqa3hDXDHJpF8bCSMSRk00UZXDyIQpFDYixhLnLbCMwAx0zcf9YXN1s/2NZ/3bPeG6adDPj+vwFDADhRnCrdW1iu0ONxZa2gh48q/ynk/6k67JcabJBPAIHOpyJhnhl2evI8LIxJq5AxsoGA31BmOp6/PdI/eHuhaGu443RrmOEzcONW2IBXSngI0bbDq/Sn+L+G9NYdHbUKERmeNyhJssAy3wKCiKaSRMpHYemMBLGbuRekqEtMB9sCFnSrkgZzDrtJACSBkxE3AkNfOgEpFJLZ0HS2oXD+5Y6wZJoIrJYwtJ6cxB/t2lpI/IC2WmKx3M5/N14ZeQrYky0w5raZi3XKFbWIVSaFX140lYdTmDYcL4zdSaQgti9P1oKH3H8lR64L6wTBGZYcxDFiwfLCQdydgXY0lVOsikyPInbfLK2A0rv4pFVGBFb+kaRsCEOYgIT4HfEIRuyo8kyT6qdqWAqfRpMWlzk3UqPXSmpjNRZtLJGGq6g+ElObi6dHak9mA1U6Wn7F8e7u6NX52cjXf3rvZen5zunZ23M/EkGPMFJMYCusUEplJHRPpHjsyN9SmxIH3oBPQ0cIlJQgYWgacGRJ39rjFoybERfyVNEGF4kdXpZ0SePp0DEYZo43G/aqwDYgutkYlajWjQMkkxgv4kmMJgauaQpac9fVqmBwhrWKbUbUAd7o5nTEkRBBx/U/kAA8MC8XNDHOAq1mNoaQ5WVylHADdFrir9ZJikZZYb65n2wf0mJqhRSTaRCuMRbzWcr70WGBh7ZQPtiETXm+uI5MyCaAkz10vnM8m6qCb3MgspEWlWNzHlYUI0CdE4DpHHc3ikFGnEnXSEOcLIJ/qS5aFYILpPdKk7dBFsy8Fm7iQ5L92s0aqtjYkI1DJJq/LGapfKeFghVmvimu2mu7/CwKw33uut4HrjBxmT4RSUMv9rni0iqiQH7aBBaydnPAXSa2OrLwX6biJDr12etMqTFcUq2bBwGmSqkLrO68OXe8fne3ilnfpMhdEsN85nTDdI1iM+JtTmHn+tsbhb7Zj//q8KVffv4avv5IrJsPgIIt5V7f316ssD7rtHUuAmJjXO49ndHaanS6sWC3xdrvKx6/+uCP/MGv87kt3A7erjQ7VJoaH7nzEr2QQbf2ReOvz/O18imtI8PqvWVE/Iz3w32chU9ZLp2yZTNbO4w8LVUApMoDde31UHO5xD7htXvvn+gHItR7b9vQu6WPwO+GJEAw==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Operation"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/operations/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The single operation endpoint provides information about a specific operation.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","required":true,"description":"The ID number for this operation.","schema":{"type":"string","example":121692259040116740}},{"name":"join","in":"query","required":false,"description":"Set to transactions to include the transactions which created each of the operations in the response."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_links":{"type":"object","properties":{"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"type_i":{"type":"number","example":0},"type":{"type":"string","example":"create_account"}},"title":"Operation"}]},"examples":{"RetrieveAnOperation":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/121692259040116737"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/f92a9648c1084d1de0fd786faac5d5e1637d4127c60841d2366c70d2e7f77b85"},"effects":{"href":"https://horizon-testnet.stellar.org/operations/121692259040116737/effects"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121692259040116737"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121692259040116737"}},"id":"121692259040116737","paging_token":"121692259040116737","transaction_successful":true,"source_account":"GBDVKE33GVVMBXX73OHIBRP6RAHKHHW2P4PQVV6UNOKQCOXU7GNUM4QI","type":"manage_offer","type_i":3,"created_at":"2020-02-21T20:10:21Z","transaction_hash":"f92a9648c1084d1de0fd786faac5d5e1637d4127c60841d2366c70d2e7f77b85","amount":"10000.0000000","price":"0.0704336","price_r":{"n":44021,"d":625000},"buying_asset_type":"credit_alphanum4","buying_asset_code":"USD","buying_asset_issuer":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX","selling_asset_type":"native","offer_id":161536436}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-operations-effects.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-operations-effects.api.mdx
deleted file mode 100644
index e78a457437..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-operations-effects.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-an-operations-effects
-title: "Retrieve an Operation's Effects"
-description: "This endpoint returns the effects of a specific operation."
-sidebar_label: "Retrieve an Operation's Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGttSGzvyV1R6OLnU+EqAjatO7QIGQiDYgCE5JBSRRz0eBY00kTQ4LOWq/Y39vf2SrdbM2GNsCMnuZnPO4YWy1Oqbult9mVvq2MjSznvaS8EwJ7Sy9CKgHGxoRIq/aYcOYmEJKJ5qoRwx4DKjLHExEIgiCJ0lOiKM2BRCEYmQ6BJXnQZ0+mOP0w49BmcEXMOGmhHczpHQgKbMsAQcGGTpliqWAO1QwWlABTKSMhfTgBr4nAkDnHacyWCRWyB7XaKyZAiGRNoQh/zPMWXDGBJGO7fU3aRIwzoj1IgGFL6wJJVAO612a+1lu736svmi2Wqtrb9oTibBlKcwM1abkq/PGZibOcYiJu0CZxslUy5mjnhtWuJ0VXVSh55JIhRhJNRSQuh/64gYsKlWFixhihNhSZpJCZxERif+NlI2Emp06fQVKHLNZAb5xRgIteFL5RbKwQhMVfC1tebaWmv9xfpfXq6+bDVXq2Jrw+HbpeZgxUixUg5k1SNCIcexCOOCQ0tsrDPJCUtTYKZOeh6HJUKFMuNAPjIbfiRPmQ1BcaFGz4g25COS+0ie4r9iuU72ovzWmRllCShHhFX/+sc/HbHgAiIc4RCxTOb692i/YhYqS9BNmA1pLiC9qCpGikS4b1QMGmrCvogkS0rD8LecqyJ3M+B1gnAePwmZIoapEeR33kLm280mqRGmSJamYApAb2DCkpgZHmoOHFX9Shvxd628S6RgIm0SpkIgBpjVyj6gtPICgS/ortV8rF21mpPJBSqlsGKEbjeb+G9eLydZGILFeBBq5UA5BGFpKkXuG41PFuFuK1SZlL3Ix4yCvh5+ghAvJDXo+E7k9C6lUFe2wuc9cBZk9HWo2EC0zFi8Zp23CnVFJwF1kKQS1VeBHmotgSk6mVQN5X2O9CKgTjgJFRwKvrifjKXUwPVPxdIEwcqlA3/V6KNfsQlIhsD5HNl7QAvfrAAyYxi6unCQPMKuHmt/08fqp1JvQC26JvBHSPCjDTEEDj8XWwgl+DJiJZzgnvnKq/0Q9BzcJKAsDHWm3LIjKXMODMbS3fcbtfNm7eXF7erqpIKMcW4wxqKk/vD9T95GTodsGfD6CKYrx5Do67mVLQNczAN1YXhnZRAbsLGW3JLTlN/B+UonQLo6YUIt2d2RbLTs1J6KZJ5fdME6UeQaM7gTMVJgKiIUCzMJioXZkYHJrJNCQeXUbG12cLa27OxG5mJ8du8sd4FVN3pRNMdd/ntGI/9dxc840IB2mWOVY/7n7JT/OTu0JZlI2FAC2WTSP/yzk0v2/Mrctd8DNHcRJ/i2a2NjkS4xmOru4iVWd5fpdznu5fvL7mI5/qmdorYeZn8BZFGGBZAZoUX1Laf2MNxD9/mwgIWFf+WGFoGWXNQi0IzcgficCS7cDelrLSsk7mzce+IYrvXVso0upNqKpcjeChdzw8aLO6WrnMDnDFBJm1mSAqcXReS7FJXYl2fhc0nrJKBhLsIlWxJrJ3nOUX0NfLk6F6xnsbqItlPSc8gvqtlLXhTTCfJZcOMfsIcK6M4t9VXffKZR5rL500dj51LbaTTivBqoObBOgatbB1IyU9dm1JimH7bhy+CV5uo61sHt1mpztVEU/X/Na+Bff/Elx6+t5i++qPsVS6RKvvq/IrsIUWvfw0qZp/5AVlp3WfElI17wXLo5TSjfV29sLvv7bzF9N337BryluDNJfnlA8rsJ2XcTYl+jUyRYtLlku1n+te56Y4cuxVZJqOjuxsFJ//Bsf/fw+PXK2V7vqL12tN8/3+xuDc5e76+/6x+c9HdWTs/Oz1Zev363tX+29erwpL+1X/p3p8R1Gc4SojLatOcjCm03281as11rtwbtZqe93llpniM31oK7LNDlaC6ZTGOmsuTFdB+Le9qhh73uwXRNWJuBQTE227+tbLx9d3bce9PefLVztH/UH7zd3+vtrQzOtzc3uysHg/3B2dFgf7v/bre3ub3+ol1iSgpVNOtei+11X0n9QWy0/YNstP1IG20/ykbb8zbaPXq7t7azv7ne7vZ7r7dfbO3+trVzdL5/3D862uv99u74zfnq/vbZ7rs3u2unp4Pd1282tzZOXi3aKJ9m6KWJrvxeTfRiUvwFNAEXa9T8CFxeEsW0Q6v2dyv4pLxO7GGBuS47z5mRjzMHuqypN8jhyCG4sTZX3nOWY4wylxl4DM6dEpKoEusFthsj7ZOSImsoWnw0oChKfrpZb9YxvNksSZi5mUGR1OhrwX0/mbwaDPpko7+HPT2OSaxQvlF7kvNVUq2TPUeEGoF1eRvaQM0rLp8H+JOp0TwLgZPhzTIUeWsbC+5pmxKYFdgW1yTUymYJlEfZNRg2AlLp/hEDWOpdA4L7rveslVnTRoBywHNGDKQGLCiXXzjJbM5UydCWNoDtVWG95BU5hkbwEZAhuDGAQvK5tPMn+0Z/8uMPKa6AjJmU4GxAOISgnGESqzsCX8IYW7Y28Bi8/ZPc/j1H07as08RmQ9+9NUxZ5vv+NiC+m4xXVPgrGebpfoDNb+sMsITANaiSj+ppP12YnqwvWNaf3RLeVy/04mnpnhyuQWKksHOhv2C7EWoDNaU5PPtTWc8H9UGV5HASMQTcAou6vBaMhKfHBwFhZGj02ILxFLSCcuQz1fVJd99+Vddch7bhtJa2YfmVRU1rYgDNyWMLNZZEX7DO0xG50ZlBa0OFBmQMfoqSJKA4bnlFMYWEiVDWAeN4KGFXQo0IFwZC5+8wZFJaL6e/1lEmOJDcY4ZgSazHXiU8EUpYB4aUJu7NsdQNkvD1+FMDUW7MXv7uVNInZFPq0UwH4/F4XvgpZG0o9ajBagrGNZupGr5CMdSK9+OZn+VYbJkNWXg1MjpTnGh11xty2zFhLByELjNMEpGgz0Pib14Xg5+EfdKGFE8HGWZJ+qxOdjQO6vIGKS6zoc5wBuRZRAUW9KamoTkMmYWAhDGEVwShq/L7ydIuqnamgJFwcTashzppFHpojHRjKPWwkTDUdAPdS4Rgy6ezgRMmo5jMLWX3dK+7fbnTO77sbp9tH/T628cn9YQ/85e5CZE2gGYxhJFQOMN6YslYG4eTR+F8RqBGnksMEsKzCGGs88GZ5x6dlhxq/j1hgnAd+oma12CHPH8+BsI1UdrhXF0bC8RkSiETpRrxQvMgxQjaE2cSnakaQ6aW9vx5Hh7Az5GZlDcetT97ec2k4F7Ay4WXD9AxDBA31sQCjt8dupYKwagi5HAIdZbKQj8JBmmRpNo4bA6i+Q21V6MUbCgk+iOeqhhffc4x0PcSptgILBFoemMVkJQZ4DWux2pqfDqaF1WnTiQ+JCLN4iSGPAyIOiIKawbydAxPpCQVv8NxpiWMfKBbLPWPBaL7QKe6QxPB1BdMYnvRSW5mlVSterMeqKajWmGNxYiShb7TUYyCS7ar5r6DjpmXS8GdVHA+8YOECb8LUuq/VfcmAZUiBGWhQmsjZWEMpF1v4gyKo+1GwifW+U4t35lRLIIN87tepgKpbRzsbW0fnmzjkXrsEulrl1RblzBVIVk2oDCgTltQTyyZfcUxl2Lczoa4/9l3JEWZ4eCLa6SSCT8D8YLdFsn9+1lRimx0fCOuzO8vAhpr6xDq9hbD06mRkwku59N6zPq5sNhPvWdeX5Xk//8lx1J1XMFN9duUohlIfQHyLcL9bj7YeEAL5acq36mEP9DHGQ8oqfxsZaakC/xhBGrpG33i6XHRBH9GHvMJ1lKuys6EuqkyVXKL81Lsh8fA8G6RvXxjIwwhrcqx8LUIyjXtCOxuD+hk8m/8OnPQ
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Operation's Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/operations/{id}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the effects of a specific operation.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","required":true,"description":"The ID number for this operation.","schema":{"type":"string","example":121692259040116740}},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"RetrieveAnOperationsEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505/effects?cursor=&limit=10&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505/effects?cursor=121693057904021505-2&limit=10&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505/effects?cursor=121693057904021505-1&limit=10&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121693057904021505-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121693057904021505-1"}},"id":"0121693057904021505-0000000001","paging_token":"121693057904021505-1","account":"GALSPNVKGNRJ3VIOQ26QKPZBDCTVJK7XPLSPF3UVZV3JJXCKVCHNSPCK","type":"account_credited","type_i":2,"created_at":"2020-02-21T20:27:30Z","asset_type":"credit_alphanum4","asset_code":"NODL","asset_issuer":"GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL","amount":"0.0000027"},{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/121693057904021505"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=121693057904021505-2"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=121693057904021505-2"}},"id":"0121693057904021505-0000000002","paging_token":"121693057904021505-2","account":"GDQWI6FKB72DPOJE4CGYCFQZKRPQQIOYXRMZ5KEVGXMG6UUTGJMBCASH","type":"account_debited","type_i":3,"created_at":"2020-02-21T20:27:30Z","asset_type":"credit_alphanum4","asset_code":"NODL","asset_issuer":"GB2Y3AWXVROM2BHFQKQPTWKIOI3TZEBBD3LTKTVQTKEPXGOBE742NODL","amount":"0.0000027"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx
deleted file mode 100644
index d5417fe305..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-an-order-book.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-an-order-book
-title: "Retrieve an Order Book"
-description: "The order book endpoint provides an order book's bids and asks and can be used in [streaming](https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/streaming) mode."
-sidebar_label: "Retrieve an Order Book"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWutSG7kSfhWVfpxAajw2vpDEW9RZCJdwSWAxJFxMgTxq2woz0qykwbCUq/Yhzp/zevskp1oa22NsFirZTU7trqtS2JK61d36Wt3qzj21rGdo85zuaw6arCl1behFQDmYSIvUCiVpkx71gSi3oKPUNQHJUyWkJalWN4KDIUwW5l8Y0hEcBzlh5tp/iZgkHSCZAU6EJOfGamCJkL2Lhb61qWmWyxxuIFYpaBMaC3HMdKh0r8xVZMqcWVZmqTDlvtLiFyXxR0lDFzTICMrG6iyymXbfPONFkigOYVu25ac+SNIVsQUtZI90lSaMmBQi0RVRQfKA3KmMJJmxKKj7x+KYGHFLVJfYPuCA7mUJSGua5KrDDFwyY8Be2rsUroKpIWFMBvrBYKS4WxepTFrQD6inR8cM0IAP5hyfkGw7sQhuQJQm+Rri1hBhyMnee6+UkvEdkQCcWEWE5CJiFhytX4sSEGbIlWRW3MCV25MrIpUdk3EwoidHdCgB7onfvaRhW9KA4gkyBM42p016CFYLuIFV6RCGAKMBTZlmCVjQiL17KlkCtEkNxLGQvYJNaEAFAvDnDPQdDaiGnzOhgdOm1RnMg6nTo5uL5VXrAB66UTEnC85QbngxJBvC9kGPVUb7a+DCXrI47TOZJfWrADV8OLxUvQppQE3Uh4TR5j11ojapsQgvGlCQWYJO5RnTgD7kOzu0VKUXw2HwiC28fR+3RpfFZq45Wt6RCONcgzE5jPPzGv16wkyH+TZE+OVXs+d0hVhDqIxs+YR9blmSxji0tX68+37reGv97Kfd5dN3p6uNs+XV0+pW/WS9dXbQOqu1PjWOP9RWDz++31/+qXW4/umgcbq3cUIftxXi8gss5eD8TOD8mRY5bq1PKdfJ7p7rE4/q9qhTdFTW61uyMHVv/J97xpRBvp1jPGaqGSzMHNj3dY4pcf5o3/gORtk4PpzSLxaJsF+gU8JuRZIlRGZJx5+4hkhpbogGm2kJPCS4zvF36Ytmsgekq1VCljAcVisV8tuv/8HkJ0tT0PlS22cu9PaZ5mg4l++881mLM2IKuqt0wmQERAMzSpo8kAszTi+IMPK3X/9rJ0GXB0Tgzy7LYmu8AI7fJH8xc40opIWec5KxFauV4fAioLclk6Wp0taUxmnTKLRqMKmSBgxyqlYq+Gfaiq0sisAY9FglLUiLS1iaxphbCCXLnw2uu5+VSHU+Q4SHlmrMFqzwu2DWWFjFtGZ4mMJCYp6mTrWI4FI/vVDOsc0woHze8HAYeMazoBwGlCWI+zlTjg5z37+QOhgBn5amEKfm8UGsuKviKzkFtHChPT6dh4c5F0rKrAWNMN46Xy2dVUpvLu4bjSENqBXWXTR5ZMi1H41Ostjh2J+cuPMS3eY9vWFxBhNwn08drKTNpYr/uANbqr3xn8kx0UpYebVUr75eppMDotV66BdWKF6FD1h6XvWnmCy9fh3muz/OpTHNZRk/r6ZEqVXCWvUJLssPuFQbuLzApVGZiHIxcp0ZYzUKtvI8KkvTnF97HgXO9fBN3S2cJ92U8T3DpzlWG0vLYWOpUa9VX81hWnXcqo2n2NSWqo3fsX/dsak/gMLrpWXctahf400tfNWY2G7kp0X/GeVb0/43tWJOIlZ0Mbq2tkQfuhXdWm/sLL/b22wsLy+f1FfP9o42j072TuvLO43Wp1cbJ4e7a3sbpwc7B7Vaq1Z7f3K29XH57afND86pvGPdlnCD1siRzu9pzDAK0VYf4hjjmcq0Uz/KdExGxYK8DFCyYKwEO1UxcAHxEgPiv9vttpxNzle8Of6FszOZycpDS8wuQ4lXjlvrb2envGlWtlYbZ62NndO12qudw7eN1Y9vt1cb7/cP6ofvjt7Xao2T6u7WSW373f7O6sFB43CjVt+t7559/OAYujxipd6WDha5OXbYDWu56EsDGrMOxLRJf8zVLud/S4ZfF012w/Qo023xa7JC8sRooT2XtE0Xf2hLJDKgb0CTFSJhUOAQ5nlM2HLzC21JSJs+40zaNGhLZI7HgaRIGbqDwnNyjMjDzVbRoqE/q4XF4PE1OTnKsra25PYa/f5ShI6Z+H0XnbwRi+MF/9X2QS50MxlhpkMWMFtaJPeeJFLSqBjCWPX8xA84PhzxsFG/QAlazxCC1kq7mZzyB8TCBQYcC9IIJb2nXMMdbc7P4oJR5MFsDkkTsH2FFZkeWB//+rRJC76CuHFH43lnGgH2jKOl87LrI7+OfAA7UPraAXk+x26GZbvn8NwcrSRyxPUC8/6ucgE+D9A5QtEAoI2nroSVEG8vkyUJ03eTVVMVzHdHRwdk9WDblbqYZZi328JTMd81JNuWCNkDY31pU0PJGc641Y4y1YpnEXDSuZvHAjkzzN2T8WsBmBGgcWsEQZbAiJTdgGY9IIXEmmiInVPgclxTeFGUlBYgLXAviIZUgwFpHaHx9dfO3Vigt0oDvnOEcZoX9OhowXtAOmAHABK399pOUx5ohcmbIbG4BjJgcQzWBIRDBNJqFotfgBO4jfr4djJBXhP2xUm8KJ1E49eRVcRkHfeI0kwa5lzEBMQ96/CIWOTCF+mwGJV1NQiPeQI3WJT1chSpkemEMpxB1t8dCefFA32yGJ+LXY6UhpJUHBb/VujB+DXaLu9oMPcIBk5uBCPR8eFeQBjpaDUwoN0OSsKonjS2dWt91zyv8WGVik3Z8GuDllZEA8IpL8BjznQr7B3yv1OZRrShQQMyAFfOSBKQ3NX/XS9D4sZESGOBcSRK2DWWcbjQEFl3hhjijNPTHWsvExyI95gOGNJXA2cSnggpjCv55BB3cBzZBrdw9Y0F16IZofN8fazpC7IWq0LzZzAYTCs/XlnqxKpXZiUJg5LJZAmjUB9KefxYdCUQo9BNWHTd0yqTnCj50Bs8dnTUFxawUcRiIhL0eXDNHH9CwpCEfVaa5KGDdLIkXQzJptIE44xOvNexjsqwFONERAPm+42hoThgGh6QqA/RNcHVRf1dgWcLTTsxQE/YftYJI5WMMrJyT5U7seqUE4aWLqN7iQgmLTB81mvJYo+UrePt9Y3Lzf3Dy/WNjxt7+wcbh60w4YvuMNegqzQgLDrQExJLSS8MGSht+0SDsK5lI3tOSrwkhBMRor7y9SsnPTot+aD4l1wThKvIFbacBZvk5csBjPpLILnSBojOpEQhRmbEA/WXFCOIJ85idKbiHTJG2suX/noA19ZjMXa7lPW0lzcsFtwpeDkT+XxPD4gdKGIAG1MWXUtGoGV+5XCIVJbGuX0SvKRFggkXk9bBr6OcGWPBOiJGf0SqAvjCKcdA30uYZD0wRCD0BjIgKdPAS1wN5Bh8qjutqkqtSNyViHvmlHjl4YWouq5NZ8jCAF7EMSn4HVYVDWGkTd+y1AULZNemY9st+sadBZ2Y/W7Lw6yQqhVP1i0qqW4pR2Ne/WORqxvlNdmR2EW4b6JjusOnwYNUcDrxg4QJNwtxrH4szg0DGosIpH/f5nutpizqA6mG+LgWHLHbFe5x6mdKfmayY37ZMDfrdMqZmvLe9tuND60NJAn7Nompq5cpYxMmC1uOSj14oU765g8zi/tJWfSfBvo/DfTnN9DzgoyFW1tOYyawDODxe58/285p4dl2EdC+MhZH7+9Rj2MdD4c47Lsh+JjjwrBO/Fg/pIjUhVHrZpF843b6XLX9C3fufwzI37fUvS2fr+D37oo/W81xa/MrFP0WTe1nK5Q3H79CnW/dx/4d1ea15b8lIv/gzutzNf1TQfmddPp6XP5le8m/Y8JR331itgv8oQXajTbPL4YB7QPjmIqNS5WrUQRpkWqmXTxVqtzaOKLD4f8AQkwk1g==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve an Order Book"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/order_book"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The order book endpoint provides an order book's bids and asks and can be used in [streaming](https://developers.stellar.org/docs/data/apis/horizon/api-reference/structure/streaming) mode.
-
-When filtering for a specific order book, you must use use all six of these arguments: `base_asset_type`, `base_asset_issuer`, `base_asset_code`, `counter_asset_type`, `counter_asset_issuer`, and `counter_asset_code`. If the base or counter asset is XLM, you only need to indicate the asset type as `native` and do not need to designate the code or the issuer.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"selling_asset_type","in":"query","required":true,"description":"The type for the asset being sold (base asset). Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"selling_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the asset being sold (base asset). Required if the `selling_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"selling_asset_code","in":"query","required":false,"description":"The code for the asset being sold (base asset). Required if the `selling_asset_type` is not `native`.","schema":{"type":"string","example":"USD"}},{"name":"buying_asset_type","in":"query","required":false,"description":"The type for the asset being bought (counter asset). Either `native`, `credit_alphanum4`, or `credit_alphanum12`.","schema":{"type":"string","enum":["native","credit_alphanum4","credit_alphanum12"]}},{"name":"buying_asset_issuer","in":"query","required":false,"description":"The Stellar address of the issuer of the asset being bought (counter asset). Required if the `buying_asset_type` is not `native`.","schema":{"type":"string","example":"GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX"}},{"name":"buying_asset_code","in":"query","required":false,"description":"The code for the asset being bought (counter asset). Required if the `buying_asset_type` is not `native`.","schema":{"type":"string","example":"EUR"}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 — an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 20 for order books.","schema":{"type":"integer","example":20}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"bids":{"type":"array","items":{"type":"object","properties":{"price_r":{"type":"object","properties":{"n":{"type":"integer"},"d":{"type":"integer"}}},"price":{"type":"string"},"amount":{"type":"string"}}}},"asks":{"type":"array","items":{"type":"object","properties":{"price_r":{"type":"object","properties":{"n":{"type":"integer"},"d":{"type":"integer"}}},"price":{"type":"string"},"amount":{"type":"string"}}}},"base":{"type":"object","properties":{"asset_type":{"type":"string"}}},"counter":{"type":"object","properties":{"asset_type":{"type":"string"},"asset_code":{"type":"string"},"asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"}}}},"title":"OrderBook"},"examples":{"RetrieveAnOrderBook":{"value":{"bids":[{"price_r":{"n":10000000,"d":139999999},"price":"0.0714286","amount":"24.9999990"},{"price_r":{"n":1,"d":14},"price":"0.0714286","amount":"188.0000000"},{"price_r":{"n":1,"d":15},"price":"0.0666667","amount":"230.3200000"},{"price_r":{"n":1,"d":16},"price":"0.0625000","amount":"50.0000000"}],"asks":[{"price_r":{"n":5000000,"d":62500001},"price":"0.0800000","amount":"4.9400001"},{"price_r":{"n":10000000,"d":125000001},"price":"0.0800000","amount":"2516.5154327"},{"price_r":{"n":2,"d":25},"price":"0.0800000","amount":"3125.0000000"},{"price_r":{"n":4,"d":49},"price":"0.0816327","amount":"4593.7500000"}],"base":{"asset_type":"native"},"counter":{"asset_type":"credit_alphanum4","asset_code":"BB1","asset_issuer":"GD5J6HLF5666X4AZLTFTXLY46J5SW7EXRKBLEYPJP33S33MXZGV6CWFN"}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-fee-stats.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-fee-stats.api.mdx
deleted file mode 100644
index 9ce26f94e4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-fee-stats.api.mdx
+++ /dev/null
@@ -1,63 +0,0 @@
----
-id: retrieve-fee-stats
-title: "Retrieve Fee Stats"
-description: "The fee stats endpoint provides information about per-operation fee stats over the last 5 ledgers."
-sidebar_label: "Retrieve Fee Stats"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWVlvGzkS/isFvsQOWocP2bGCASaHnfFsJgliZ19sw2CTJTVjNtkh2ZI9hv77otjdUsuWZrUKsA876xeZR32su1jsRxb42LPhFTtDhIvAg2c3CZPohVNFUNawIbvMEEaI4GkZ0MjCKhOgcHaiJHpQZmRdzmk38NSWAQp0HVugq+YWtHaCDkKGoLkPMACNcozOd1nC5tvPJRuyrxicwgmeIVZMJcyhL6zx6Nnwke33+/SzzOdFKQR62iusCWgCbeFFoZWIyL3vnvY9Mi8yzDn9Fx4KZENm0+8oAktY4YiPoKpTiMvbisfWZh+cMmO2SktRrIrghQePP0o0AsGUeYquy2ZJG/I25R5vR4ibYdPuqEruQeJIGZSgzEKbFWh1SIUveMGFCg+3pefjDU/hE3R8jNDQQqRdZzjY6YPyYGy1LYG9bpwQNi80BtQPMCq1brbvRu5GiLci426MMhpI688jNrx6as3zZ14Vaj+siWFkHQTHjeeCdvkldbSca5a0T/lrk+f8/rmiZgnLlVk9b+UKzc4SVuz1V8/vr5k/WDN/uGZ+sGb+aM388Zr5V2vmT9bND9bMn6yYnyUsqKBp6i33FM7vFa2lZbQyWWYjeyy7xh/8XuVlDjuZGmfow+6SW6xNMgszPoFTpoLTdvqfodXGfwJnJcJOrqTUuDlW7S/LUHv9kFEyFWiC0rg52P4KsP1twQ5WgB1sC3a4AuxwW7DBCrDBtmBHK8COtgU7XgF2vC3YqxVgr7YFO1kBdrI12GAF2GBbsJMVYCfbgM1mN4vE867a/iz33FAE8/umAm9eh3J+H/lI1Yoa9BcS/r8K/Y9XoQnXJYIdRfvn9XLjKT9flraH36BObQ2+UeHaHn2TSrY9+ialbXv0TWrd9uibFL/t0Tephtujb1Iet0ffpF5uj75JAf0J9A0q6k+gb1Bit0Rfqrl/8PsV9baVh+eN/SxheM+pXYyZ9lnjP3xkkaFn/Tg7PNg/Pj7YO2Drumq21++ztd0w22PPetGY59lgEOliUmaDfjWIKbQZxZw3H+y3BwftwWF7MKgHdG4Mr/nguBocHbHaeeeDk/6Cn+gai8FJM1i+xlQiHO0d9Y8Gh/2jNXLs9fv9g7kgNFpIMl87WBpFWfb7/f5gLsx81Eiz32+JU4+iPHuD5oiTRiVtmRZDkmrv8CSOZ/Vfwu47wkq8aNzkilzBjNmQ/c4n/CL6cvSCFDUbsl99QK2569W/HS/vWMK8LZ0g4SfcwUW1dCHv4Bdw+KNUDneuV5Jes93X14aIPDpy/1/A4LSF0P3NOvWnNd2LuL5zbQCuWRZC4Ye9XlYtdgL6YDB0a+SudeNrllwbAr82FTRRdke16+/sxmHI0OyMShPvl7BDz2C78EhLAMIabzV2tR1XC69pflYRCh5E1qJE554RonPWxZWa8vU1RWrCcgyZpZe4McbrEA8ZG7IexYuvH+QqlitzlI4Uv4HIKx+dLqt98AnD1Lq7eCFbjTgqQ+lwE8yzZieYBvUmYfRUGS+IdRqqLccSRqJU1P1uv0th6cs85+5hsWvx4skN/HZ5+QXefDmHYEHywJvHp9otmlO7cB5AmTH6QGQSHHai4nzcHSkLZ2UpUEL6sAqCkDk1GjmEjAd6X0PuFeVhGw1Z5tiQNs93rVdPcKh5UBOk7bSnQBc7GiOwY51CE1BWjDgsHHo0gVe9TOkrphqG3lmHXbjMlI+St+RInZJjhBTDFNHQ8ZW0y5RfnKXrtQet7hCmXGsMPgGJVHoc1+pPlID3IuOksCQicO+RZPYlvTeWHqGxRrDgyzRXYakBS+BHie6BTMSFsKUJkHJNwiZgHfjgkOeAEzQNH0vtW7Atyu4zz/q7e8JV26A3O014SpygpobJt+OyV7PdE9Zhx1iJu38r76G83hwnuIEUaQk96XKiOIhvXz8mwCF1durRxROsmV+95rq+eP8P/291La3wvWCt9j0v7zxp2oJDcqeIVj3J39OTvh3Bgy0deRspNIEpgkNh8xyNpKWoKG7oYFDGB+SSiHJ+p8wYpHIoQrSh4Fr7KGc067hUEqGKmBQ9ZHYaVSJzZZQP6KBx8eiOjW7oCFIxFbdR5cxR/vdzSV/AW23HCx1Mp9Nl4ec7O6m24x7vGJx2fGk6VIUy7NT1Yze+13hLYcLF3djZ0kiw5mk0VL7jRKYCilA6rkHlFPOYR8tHCykPOf9uHdSlA9IyL3a7cGbdik9iNYukwPq8uWtYiXRpTUBkKO6g+dTRyE9HwgdS7UIBYxWyMu0Kmzc3ld7Y9lJt017OSdM9Ci8l0Dels6dMQGe4rjzlw7fz96e3Z5+/3r4//efpx89fTr9edHO5G435FkfWIblFimNlElDhhYepdSEDhyrEL3VmHLmkJKEiiygyu/gmdUVBC5+s3CZNgLSizJv0M4SXL6cI0oKxgb4/WucRXGkMMdGokQxaJSlOXxuN5JqCqZ1D5p728mWVHtAXKBTX+iFCR9rbCddKRgFvn1U+pMBwCGFqwWPBHQ8UWkagM3XKkShsWehaPzklaZUX1gVuQnS/1EY1asVTpSkeiarlfN2lwKDYy7nhY/rQSq43NQkU3KHsSDs1c+ezo2VRbRFUHlMinVlTUsqjhGhHYBClh50pvtAaWnGnPH1g5HDN3vEiFguCu2Zz3ZGLsIQFdLn/PLqo3Kx1VWtbNm7q2FGn9sb60ywX8dOs4TkRNmy33f2MAjManyVProLLFz/MuYqrqLX9tb1G30GVQOOxddabgosMYb9L3YaS5LsjFbvJaqVTrSxOrJMNj6tRphrU9z6evzv9dHFKJN0s5Dq+MxbWh5yb1pFNRwuLL+xPbhWPi+/V/51v7fVjZ8D70Cs0V/QEWsn8WN/0r9jipn+TsMz6QJOPj5Sovjk9m9F0rJVseHWTUE+leEp36it6V8+QS1Lr1SO7Q7pCvxECY5NWN/PPv8svdR0fTi/ZbPYvVystPQ==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Fee Stats"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/fee_stats"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The fee stats endpoint provides information about per-operation fee stats over the last 5 ledgers.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"last_ledger":{"type":"string","description":"The last ledger's sequence number."},"last_ledger_base_fee":{"type":"string","description":"The base fee as defined in the last ledger."},"ledger_capacity_usage":{"type":"string","description":"The average capacity usage over the last 5 ledgers (0 is no usage, 1.0 is completely full ledgers)."},"fee_charged":{"allOf":[{"description":"Information about the fee charged for transactions in the last 5 ledgers."},{"allOf":[{"type":"object","properties":{"max":{"type":"string"},"min":{"type":"string"},"mode":{"type":"string"},"p10":{"type":"string"},"p20":{"type":"string"},"p30":{"type":"string"},"p40":{"type":"string"},"p50":{"type":"string"},"p60":{"type":"string"},"p70":{"type":"string"},"p80":{"type":"string"},"p90":{"type":"string"},"p95":{"type":"string"},"p99":{"type":"string"}},"title":"BaseFeeDistribution"},{"type":"object","properties":{"max":{"description":"Maximum (highest) fee charged over the last 5 ledgers."},"min":{"description":"Minimum (lowest) fee charged over the last 5 ledgers."},"mode":{"description":"Mode (middle) fee charged over the last 5 ledgers."},"p10":{"description":"10th percentile fee charged over the last 5 ledgers."},"p20":{"description":"20th percentile fee charged over the last 5 ledgers."},"p30":{"description":"30th percentile fee charged over the last 5 ledgers."},"p40":{"description":"40th percentile fee charged over the last 5 ledgers."},"p50":{"description":"50th percentile fee charged over the last 5 ledgers."},"p60":{"description":"60th percentile fee charged over the last 5 ledgers."},"p70":{"description":"70th percentile fee charged over the last 5 ledgers."},"p80":{"description":"80th percentile fee charged over the last 5 ledgers."},"p90":{"description":"90th percentile fee charged over the last 5 ledgers."},"p95":{"description":"95th percentile fee charged over the last 5 ledgers."},"p99":{"description":"99th percentile fee charged over the last 5 ledgers."}}}],"title":"ChargedFeeDistribution"}]},"max_fee":{"allOf":[{"description":"Information about max fee bid for transactions over the last 5 ledgers."},{"allOf":[{"type":"object","properties":{"max":{"type":"string"},"min":{"type":"string"},"mode":{"type":"string"},"p10":{"type":"string"},"p20":{"type":"string"},"p30":{"type":"string"},"p40":{"type":"string"},"p50":{"type":"string"},"p60":{"type":"string"},"p70":{"type":"string"},"p80":{"type":"string"},"p90":{"type":"string"},"p95":{"type":"string"},"p99":{"type":"string"}},"title":"BaseFeeDistribution"},{"type":"object","properties":{"max":{"description":"Maximum (highest) value of the maximum fee bid over the last 5 ledgers."},"min":{"description":"Minimum (lowest) value of the maximum fee bid over the last 5 ledgers."},"mode":{"description":"Mode (middle) value of the maximum fee bid over the last 5 ledgers."},"p10":{"description":"10th percentile value of the maximum fee bid over the last 5 ledgers."},"p20":{"description":"20th percentile value of the maximum fee bid over the last 5 ledgers."},"p30":{"description":"30th percentile value of the maximum fee bid over the last 5 ledgers."},"p40":{"description":"40th percentile value of the maximum fee bid over the last 5 ledgers."},"p50":{"description":"50th percentile value of the maximum fee bid over the last 5 ledgers."},"p60":{"description":"60th percentile value of the maximum fee bid over the last 5 ledgers."},"p70":{"description":"70th percentile value of the maximum fee bid over the last 5 ledgers."},"p80":{"description":"80th percentile value of the maximum fee bid over the last 5 ledgers."},"p90":{"description":"90th percentile value of the maximum fee bid over the last 5 ledgers."},"p95":{"description":"95th percentile value of the maximum fee bid over the last 5 ledgers."},"p99":{"description":"99th percentile value of the maximum fee bid over the last 5 ledgers."}}}],"title":"MaxFeeDistribution"}]}},"title":"FeeStats"},"examples":{"RetrieveFeeStats":{"value":{"last_ledger":"43277313","last_ledger_base_fee":"100","ledger_capacity_usage":"1","fee_charged":{"max":"5500","min":"5000","mode":"5000","p10":"5000","p20":"5000","p30":"5000","p40":"5000","p50":"5001","p60":"5001","p70":"5066","p80":"5066","p90":"5500","p95":"5500","p99":"5500"},"max_fee":{"max":"616065406","min":"5000","mode":"10003","p10":"10000","p20":"10003","p30":"10003","p40":"20005","p50":"20005","p60":"50020","p70":"50020","p80":"150000","p90":"500000","p95":"500000","p99":"1490000"}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-related-effects.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-related-effects.api.mdx
deleted file mode 100644
index 3e92f8e0ee..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-related-effects.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-related-effects
-title: "Retrieve Related Effects"
-description: "This endpoint represents effects referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new effects referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time."
-sidebar_label: "Retrieve Related Effects"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+ty2ziyfhUUf+wkU7qQulqq2toj24qvYzuWnGyScXlAoiVhTAIcALTi41LVeY19vX2SrQYvoizZseeMN8nO+o9LJIDu/tDdaIAf7hxDp9rpf3KO+W8JZ9zckjMpQ+1cVhwGOlA8NlwKp++MZ1wTECyWXBiiIFagQRhNYDKBwGiiYAIKRMDFlFAy5TcgSFiMGksZEioYCaggPpBEAyNcEG0U0Aj7RJJBjYxWfhMahnKuya1MiJEk5NqAIBOpiID5RskG1bwvVhMzg1tCFRDKGDAcy8yAjAyEIVUkBDYFVSMHExLQMNykWYXsS8X/Vwoy52FItKHKEGrsMEBVyEEbci3kXGRqkUSEoDWhJEiUlopwTTSYCg49n/FgRgKqgXBTHnCiZETMjJqsU41s32Ivk5oG+Vg3NEwArRByXrHoIKypxgUsgQJqgBHNRQDYSBEFvyWoqOER1JyKI2NQFCf4gDl95xyM4nAD5xBix2E6jlNxYqpoBAYUusqdI2gETt8pUL5ClK84cyoOR1eJqZk5FQeFcQXM6RuVwH1/GpBE8N8SIJyBMHzCQdmJ3TCBNWdRKaSmCOSifktA3a7ImtBQbxAmksgHlWJrXVgjfJToGAI+4QEJZWCRwPmhJJBhCIH9LSdEgY6l0KCtB3NN4sR6STZdQGI65WJ6ZeQ1iGxy5IRQoiCQiiHSOphBRJ3+nWNuY7SDCwNTQEPgM43iEJx+p+N2Ol631d3qtXue216UzJaKwfOtZqD5VNDcDlTVDrR0wlRDTfRMJiEjNI6Bqho5tWNowkUQJgzIL1QHv5BXVAcgGBfT10Qq8guK+4W8wn/ZYxtDdgqpmiYRCEO4Fv/8v3+YzPkNYTChSZjib4fdCI82iospoiOSCBMU1YGTGuhcloEJecTNM4EZz4BE9DOPkih3DDvLKRQKTKIEsBrBdnZ8G16Kiimkc+6h8g3XJVVCBUniGFTW0DoY12RGFQskS1NJnjrQv2NQE6kiijGpgGop9COg5RMIbA07z32qX3nuYnFZcT5XdRLHUhldLXJbHpuFh+NIDdfFf6uYjZIgAI3ZIJDCgDDYhMZxyNO4qf+qsd1dSSMahqcTmzEy3aT/KwQ4WbHCzGN4Ku8q5OJal2x4oJ2GcPLlVjMFk02OZFE31mPEtbOoOAai2Ca6UmtfyhCocBaLshN9Sge9rDiGmxBKYwj4bL4xlWIFN9+USgtslj86tlON8fsFn4DIB1yrv2xKFrelhlQpimmAG4ie4FdP9b9itfym4K04GkMT2BMs+Hc7YgAMvi21sBVnm4Tl7TizypdW9Mdar7RbVBwaBDIRZlOXmBoDCnPp3qdB9aNb7V3etduL0mCUMYU5Fi21nR9eDgepHLKTFnlOpXhyDpG8WXmyo4Dx1Ua74N97Mp4p0DMZMk0uYnZvzH0ZAdmVEeViw9s3IZ1u6nUgJmFae+yCNjyrQ5btRnwqQJVMyB4sLcgeLLuMVaJNyAWUei2fLTsun23qO0jMDJfke493gZZfnE4mK9qlv5cy0t/l8SkDp+LsUkNL3ezPZS/7c9lpJ6Q8on4IZJuGtihY9tzwzj5ZmfYHGq1MxAjXdqn0jMcbHKb8dn0Sy2834bt57M3vN83F5vELP0W0Hld/rcm6DWtNloLW4dss7fF2j83n4wZmHv6FGVpvtGGi1hstxa1u70si7r14sMc53MjrTS92IZaabxzsPTczpuh8/U0eKiPcjyJI20kUA3Mus8x3xUu5L63QVwraRcXJdrdXdEOuXaQ1R3k1sLvTlWS9zNVZti1Erwx+Wa5e0i2xs0A9M23sAvbAzrl/59jN4GqRkZex6arnzIyJdb9en6WbhKoBbQSYmk4PJ2pSTeurW21d73QbHTdoBd6W2/UbncZkstX2fJc2J+C1PK/X6jU7vu82vLbfmHS7rVZ34rGJ5/V6W0B9v1fPzgj+lu6m//oXuyv8K+6xSkXtN6Sg13C9XqPZddsdr9FwO+7Wqsp50fvtqdxqdXtes9X03Famst3Dolet1LhFFfup7CsrJeczjCv66Xpzq9Vzt9qNTsfruc1m937F+IxRcwuXdvwlM/a+kKp3vwL83WLo41Kyes5xsz+vsYWt2r2tTtUtHt4P/r5TbtcoJYO+szcYfDxojXfOm+MP7dPD/Z3x4U5j0Ho7+tDZOXx/uN8+GByO944OThrD8+7x9sm7o9Odnfcn3TyPrJ2MsVKKzLPblreawpyG2/Cqnlf1tsZus++1++3WR6dybygE0lr7/3VWLK4BrvzY6TfdQu9ACm2oMFexkiyxhbqRhoZXJl+utdN3mq5bvNAzquzDtmuf4qGwuoHUjWmUIeq5rltLZ6KNUGsN+Hh4cT7u7w3O2sfD8em7zoeDYafxYfBTuzMa7w5Ozs53T7sf3+xu741O9g/fHnzY2zsa/XT6cbB/ejpqjOwespDQWEpwSxLO9s/6e9sXb9+fNbdPLz7+vdkan57sNt6+67592z3qvjsc73XejYbd9z8db49/2j08Ph6873442rvoDM/SLJ8bVJpEa9ofYkKlZECzu1VAZE37I0woCehtNZfjX1acdOauMEI5rvjpLFnRX46nxleNp7mtK2BeDqfGdxtOjV5vPZxaj4VT92VjyXvZQFp63IvEUeul46j3QBwxgOi5cdT8qnFksiq8CKLmdxtEf6o1ScvQlowvukRUHF8m05kpC3qh1e5psdL6qrESFDvmIlpa3220eOux8nCguC8THX9kSDzNgdpf1YFUcbJSOFD79zjQ1R/jPU+DrPOVIcvPnArIOt9tzP35yrx08l6+yqs4QX7oeuWnh65pkHAW+MxrNFsvXgg+qELgc9TgXqmYIfOcSrG7IRLb3U6z1/W6vU6v2ei4W17VWw3I7e33B93x8N3b7bPhxd+PPpzsHTT3tgf73eH+m+H58PTk6Kh5cdTufBwdHx7sHnzYf3u48260twzIwoM3rH8Nd1MsultVtzVuuH3X6zdsLFrcrzZHeBYIL5TjKhk55FlAb31loJPiYL8AeuPe9tsEuvF0oHtfGej1Bbmx8Uzu2wR6ubPA+meRffGAzwaExmNfm3ev4dbpb+b9VPIvE8j/weQUgZlJVHIKJv1YPXP6ztop+d2aXYv8vBbZSJj7M5ZgosKnnfc6m+hZ47QdOQEzl+ra+tTmESeJSRQ8Zcw3eUsi8lEvkTg2kfYTUvaNJyNrIUKgdNrbrbk19ESdRBFVt8tWJFbyhjPLDCT74/EZGZwdIDuL4SdHLlZoppnUGjkwhIspaJMSChVU00XTtrY901ICGPFvNw2RkhSRHlEQzoBqpFAaSbAeSSLIu9IbUHQKpMTVIgq/U/EbyImwJVJaVSoOAnmjVpGC6Jt+TUh5u/5todCOVIBEOa6t5SU7fMXZFIgPZg4gUHxq7WrPMyV/tWzVkF8DmSP71ugKYRCAMIqG+C2ewOdghuQ7XbEj2PgjXOsElNWoINgZSXTiWx6eokJTy+DUFWJ5gThFWSoh2SJdQRpjTpu9sXRmq0e5t+WJFj1ra571Z/eET+UJvXyVhyeDGwjxM5Re+baTqV0PpIKqkAxe/6m852fxs8jFZUx4anmVwMgNpyS4OD+uEEp8JecalJUgBeTk3QLr0e6R/iLWTAa6bmza1uxaI9KSKEB3SsnkEj9gf8av8nKSEsTjFNAKmYPlw0YRCGYJ5ggUFSiYcKENUIadInqN1HTGFVLecQ6RQK+tnXZapwlnQNKI8UGTmZxbSFjEBbL5Fcld3Lpjjg23W6oAyCtL7s+989NuYekPZDuU0yUG8/l81fiiZdUP5bROqwLmVZ2IKq5CM6hm68dry8rVSHDyaXA9VTIRjEhxPxpS31HBjBsITKJoSHiEMQ+RnXmZUXgj+isS9NOlg/hJFL+ukTfI/xcpnQ0fU18myOa1KiKAmbzCNSQDn2qokGAGwTXB1mX7LUd4D6FdAjDlZpb4tUBG9QyH+lTW/VD69Ygi0nUMLx6AzpfOOnKFlaBh6il7Fwe7w6s3p+dXu8N3w+PTs+H5qBax13Yyt2EiFaBb+DDlAtnIP2gyl8ogh5wb+7k5u6SASYJbFSGYyZQCbbXHoCUnkv2eNEGYDCw32iLYJz/+OAfC8AaEwWspUmkgKhEClchhxAlNkxTFCxaC0RCDqZxDCk/78cc0PYC9EUDD8NYObfte3dCQM2vg1drKBxgYCoiZS6IBr0oYDC0RgBJZymEQyCQOM3wiTNI8wooMqVzofr60MIac+jzEeMReJeerrQQGxl5EBZ2CJhxdby4qJKYKWJXhBZTc+eRk1VQZGx7ZlIgys56Y8jAhygkRSAkgr+bwQxiSUtwhMR0vsvzs7NDYLhY43M9OgR26CNbRoCJ9OhmlblYq1cozaxtV5aSaeWNGKKeBPWnOSP252mV3f4OBmXIhKvdKwdXCDyLK7VsIQ/k/5XcLrJ8DEBpKsgYxDWZAGjU8CFleRineVNM3S4lZsqH2bUYlsYPq+vHBzvBkNMQutZmJQktPiKU2ERUlkTldiGR8IbK8arNSW9wtufb/vX/1n3j/Kt+UwmdTj0PKLYXYetpdtgP7dG8jiT7S33TzKt+EXVacmdQGe97d4RpyocLFAh+nl2Nwa8a4xqOqB67HlL3u61+c2ghRurEtroJlW1nH7hKfY9x3cz/qERTym2G/E4T/oLtQj4CU3xJbgnSJPxRHlJ4ZE6/OM17pa/KsS4wPKJjfWRG3Zf2Wit8PdXvMPgOKs7485BkEAcRlC9euZq0c8uwNx85i8S/wRc17
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Effects"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}/effects"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents effects referencing a given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new effects referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known effect unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream effects created since your request time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"type":{"type":"string","enum":["Account Created","Account Removed","Account Credited","Account Debited","Account Thresholds Updated","Account Home Domain Updated","Account Flags Updated","Account Inflation Destination Updated","Signer Created","Signer Removed","Signer Updated","Trustline Created","Trustline Removed","Trustline Updated","Trustline Authorized","Trustline Deauthorized","Offer Created","Offer Removed","Offer Updated","Trade","Data Created","Data Removed","Data Updated","Claimable Balance Created","Claimable Balance Claimant Created","Claimable Balance Claimed","Account Sponsorship Created","Account Sponsorship Updated","Account Sponsorship Removed","Trustline Sponsorship Created","Trustline Sponsorship Updated","Trustline Sponsorship Removed","Account Data Sponsorship Created","Account Data Sponsorship Updated","Account Data Sponsorship Removed","Claimable Balance Sponsorship Created","Claimable Balance Sponsorship Updated","Claimable Balance Sponsorship Removed","Account Signer Sponsorship Created","Account Signer Sponsorship Updated","Account Signer Sponsorship Removed","Liquidity Pool Created","Liquidity Pool Removed","Liquidity Pool Revoked","Liquidity Pool Deposited","Liquidity Pool Withdraw","Liquidity Pool Trade","Sequence Bumped"]},"type_i":{"type":"number","example":1},"created_at":{"type":"string"}}}}},"required":["id","paging_token","account","type","type_i","created_at"]}},"title":"Effect"}]},"examples":{"RetrieveRelatedEffects":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/effects?cursor=&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/effects?cursor=120192370561220608&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9/effects?cursor=120192344791343104&order=desc"}},"_embedded":{"records":[{"_links":{"operation":{"href":"https://horizon-testnet.stellar.org/operations/3849085266190337"},"succeeds":{"href":"https://horizon-testnet.stellar.org/effects?order=desc&cursor=3849085266190337-1"},"precedes":{"href":"https://horizon-testnet.stellar.org/effects?order=asc&cursor=3849085266190337-1"}},"id":"0000000012884905986-0000000001","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_deposited","type_i":81,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"300","total_shares":"5000","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"2000.0000000","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]},"reserves_deposited":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2378.0000005"},{"asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP","amount":"983.0000005"}],"shares_received":"1000"},{"id":"0000000012884905986-0000000002","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_withdrew","type_i":82,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"299","total_shares":"4000","reserves":[{"amount":"7.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"1.0000000","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]},"reserves_received":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2478.0000005"},{"asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP","amount":"993.0000005"}],"shares_redeemed":"1000"},{"id":"0000000012884905986-0000000003","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_trade","type_i":83,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"300","total_shares":"5000","reserves":[{"amount":"1000.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"2000.0000000","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]},"sold":{"asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP","amount":"983.0000005"},"bought":{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2378.0000005"}},{"id":"0000000012884905986-0000000004","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_created","type_i":84,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"1","total_shares":"0","reserves":[{"amount":"0","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"0","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]}},{"id":"0000000012884905986-0000000005","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_removed","type_i":85,"created_at":"2021-11-18T03:15:54Z","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9"},{"id":"0000000012884905986-0000000006","paging_token":"12884905986-2","account":"GAAZI4TCR3TY5OJHCTJC2A4QSY6CJWJH5IAJTGKIN2ER7LBNVKOCCWN7","type":"liquidity_pool_revoked","type_i":86,"created_at":"2021-11-18T03:15:54Z","liquidity_pool":{"id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","fee_bp":30,"type":"constant_product","total_trustlines":"299","total_shares":"4000","reserves":[{"amount":"7.0000005","asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S"},{"amount":"1.0000000","asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP"}]},"reserves_revoked":[{"asset":"EURT:GAP5LETOV6YIE62YAM56STDANPRDO7ZFDBGSNHJQIYGGKSMOZAHOOS2S","amount":"2478.0000005","claimable_balance_id":"idcbd1234"},{"asset":"PHP:GBUQWP3BOUZX34TOND2QV7QQ7K7VJTG6VSE7WMLBTMDJLLAW7YKGU6EP","amount":"993.0000005","claimable_balance_id":"cbid1235"}],"shares_revoked":"1000"},{"id":"0000000012884905986-0000000007","paging_token":"157639717969326081-1","account":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG","type":"trustline_created","type_i":20,"created_at":"2021-08-04T20:01:24Z","asset_type":"liquidity_pool_shares","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","limit":"1000"},{"id":"0000000012884905986-0000000008","paging_token":"157639717969326081-1","account":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG","type":"trustline_updated","type_i":22,"created_at":"2021-08-04T20:01:24Z","asset_type":"liquidity_pool_shares","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","limit":"2000"},{"id":"0000000012884905986-0000000009","paging_token":"157639717969326081-1","account":"GBBWI7TEVQBPEUXKYNGI3GBAH7EHFEREONKK3UK56ZSLJIDIYHQJCVSG","type":"trustline_removed","type_i":21,"created_at":"2021-08-04T20:01:24Z","asset_type":"liquidity_pool_shares","liquidity_pool_id":"67260c4c1807b262ff851b0a3fe141194936bb0215b2f77447f1df11998eabb9","limit":"0.0000000"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-related-trades.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-related-trades.api.mdx
deleted file mode 100644
index eec7be12c8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/retrieve-related-trades.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: retrieve-related-trades
-title: "Retrieve Related Trades"
-description: "This endpoint represents successful trades fulfilled by the given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new trades referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trade created since your request time."
-sidebar_label: "Retrieve Related Trades"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWuluGzkSfpUCf8wkgW7Lki1gsOsrThw7dnxk4ySGQjWrJY67yQ7JtuwxBMxr7OvtkyyK3S21DjvHLrCZmc2fwOoiq+pjXaziPXN8aFnvAzuUn1MppLuDE60jy64qTKANjEyc1Ir12PlIWkAlEi2VA4OJQYvKWbBpEKC1YRqBM1yghTCNQhlFKGBwB26EMJQ3qCCaski0joArAQFXMEBILQqQCqwzyGOphhBrgTU4m/sbeBTpsYU7nYLTEEnrUEGoDSgcF7wNhmhQBbTIkciLXC1JdAfcIHAhUNBWJOOZwyjiBiIUQzQ1eBlCwL0SS4JV4IU28jetYCyjCKzjxgF3fhvkJpJoHVwrPVaZVJCqCK0FDkFqrDYgLVh0Fdp5PJLBCAJuEaQr7xcaHYMbcZcvqsH2Ha1ymWZY7HXDoxRJCaXHFY8NgZoJnLMPDHKHAqxUARKJAYOfU5LSyRhrwCpMJ2g4HfVLwXrsFJ2ReIOnGNHKc48tq7CEGx6jQ0M2c88Uj5H12BTiPkHcl4JVmCSbSbgbsQojZtKgYD1nUlw0rC1IlfycIkiByslQovGHuuL0amxSmXLN9C9YfU7R3M3xCnlkVzBTaTxAkyHrbdkSeBxsgoEMZQCRDjwQdDocAh1FGPi/dQgGbaKVReutV1pIUm8i+WEhJHwo1bDv9DWq/Gh0CBwMBtqIGqswG4ww5qx3z9xdQnpI5XCIpAje8jiJkPU6nUan0+y2uxub65vNxvqkpLY2Ar9da4FWDhUv9CBR/UYzE8wktGBHOo0E8CRBbmpw7PewIFUQpQLhE7fBJ3jCbYBKSDV8CtrAJ2L3CZ7Qf/nP3oH8EXIzTGNUDqRV//r9ny43fQcCQ55GGf5+25XwWGekGhI6Ko0pUnEbsExBdlUGJpKxdN8IzPkIIea3Mk7jwjD8KWdQGHSpUShqQHR+f+9chqshZmfeJOFbjQZUgStIkwRNTugNTFoYcSMCLbI4UsQNsu8ETahNzMknDXKrlX0EtOIAUSxh12x8rV01G5PJVYXdVm2aJNo4W50GtsI3pxZOO7UaDfpvHrOzLN6zCgu0cqgckfAkiWTmN/VfLdHdlyTiUXQc+oiRy6YHv2JAh5UYCjxOZvz6kVTXtqTDA3QWo/DLVCOD4SpD8qg7bzHqmk0qzGGc+DhXoh5oHSFXbDIpG9GHbNOrCnPSRVjaQ+Gt+8FESgze/FAiTYis+OnQHzX57xdsAuMBUqL+siq535YIuTGcwoB0GH+FXf2B7W/ALf5gIgU6VQ7NDybVtND5oeRaIPIGlh/qDMiy8FeTCpNilXTFxlL4IFAqSB6jnqObVFhWBveDSFvsU5W4vJjADEM0/VVyECpUNfazn1d8XqgaQ8T+IClRZvm4DHcqlVtrFdbeXy47V7HxpI/K6Sl44FFeBVHCnUNDqW//w1b1faO6eXW/vj4pgceFMJQSp5vFq/eafrcW3cPIlGiocvgSjbQ2nXOzGVVuOV8JVUH9KFoF0X8LsOl+D2M2JXkctnmyB5GbJ3sIvO85dmn7FqNobrtpGKDgIgPM8tTM0/1lac75VvnenDPNG9mySS1huhLBJZkpJj0aDlfEj0mFrbKSUpr3cp94zSfZv9k3f61kEwpleYnq+ay+fPbumb9PzefpIhNnoZqNnEtsr14fZXV21aF1Cl3NZpf7mjbD+rwv2PraoN3t8DDc4O1Gh3cwWBt0mmI9aKxtNBqbAYYb62FLiJCHnWZno9USQTvEYLO10V5vtjcH7XrWefhbdh/95Sdf/v/S+snfr36h20qpPPxx5Gy2Gs3N1lq3sd5ptlqNTmNjteRFFfnDSd5udzeba+21ZqO9ILm/G5KhzdWO0+rwwyMGVC6lvkHjPBja+v7W2xfrB0frx6/e7R+92T3rXp6cHrSP3uycvDu42H/R6hxevjl5c9A+Oz46Pmifvbtsd1vvj7r7C/XSd7He3m4fnJ2vtS7+8er4cP/y8mxn73L7xfbO8fPD1vn+9ovdt8dH70/andbeefv96W774nCre9Y6XCqKvoH5dJ2tr3U2u+1ua7PV6LSajfWuPwDKIWzxS7WxGPIeoFlRg7BWo7lebTarzY3zxlqv3e21u+9ZuRBhm2wp6c9+m2Yt9t0ntZDjWbNRa2T/VsTiHqOmy005KM97B+n+H7oHe7CWYmuN5WzQY61ap1sIvCq3ssCgkK7Po2TEVRq3l+iy5MoOTi6XPhUJle1vv906frm18/psu3v89uLdweXO+sVea7d9+ar1vLvVap939/bWL4+PXrd39jr7Oy8uzo8v3rw7Ws5MeWtimj/JYFqdLvPJhzVJkYVycwEQyjHT7IO3DpUlm/Wh4BrvWG91S6RSZBziT42TGN1IE88huqxCGLEeW4p390vl1iQPYdSnQXNT9E9TE32do7FVjavzjA5eoxtrc+3v0qt3DFOXGvyaPZ8XlKCKXa+opRZqn+bzxJ23sQggNDZb3ag1ak3SL41jbu5mVJAYfSOF75nCi/PzE9g6eUl9K8Edp6ZYufuec63BSwdSDdG6rNVqsOqB8937bGVitEiD2ZBhYYusfUt3h2krDrml5rLTEGhl0xiLpfwGDR8ilLpYYKj6kDdYzAdK7bqqNhIVddS9INNZSBYJs2nG4G4q0I42SC1Eab3mJT0GRoohwgDdGFER+0zb+ZUnRlM9Rs3wa4QxDSWcrYDAAJUzPJK/oQC8DUbUlrQVv4P3Rch80Us0bT06DTYd+A6l4cpy39u2FfAdUzqiPETCgEekbIUavPk4AW/8xMfLUV7tO+jTlbUly/qrW8KH8oFePSncU+ANRpRC7VxSzcWuB9pgVWmBT/9S1vNRfVQFu3w+yH3HGQXcSA7BxelhBTgMjB5bNJ6DVliMNaZYn+2+sl/EWujA1p2P2lZcW0Jag0Eyp2zIpulacksDKB1mo7MkA7QCY/STgjhGJfzgjYDiihiDVNYhF7Qo5tc0shPSYOD8GdJc0Xo9/bEOUykQMo8ZoIWRHntIRCwVzTgNFCbuzbHAhlj44cETP/MsrPPD7lTTn2E70sMZBuPxeF75KWV1EOlhnVcVjqs2VVXKQiOs5vnjqZ9XWE1uwoProdGpEqDVojdktmOCkXQYuNTwCGRMPo+xP3mdDzdi/isNLrPUAYM0Tp7W4DnNRVXW66Gf+UCnNOfwIhKAOb+paWiBVCdUIBhhcA1EXdbfT0/2CdoZAEPpRumgFui4nuNQH+r6INKDeswJ6Tq5lwzQFqmzTlMUo3iUWcr+xcvdvf7z49P+7t7bvcPjk73Ts1osnvrD3MZQGySzGOBQKprT/GxhrI2j6Zp0vlTOh7cUJKQXEYORzoZDXnpyWnitxfeECRA68FMjj2APnj0bIwiaDDua3GtjEUyqFAlRwEgHmgUpToNnJXhEzlSOIVNLe/YsCw/oZ6U8iu781n5t/4ZHUngF+0uZD8kxDIIba7BIQ2RHrqUCNCoPOQIDnSZRjk9MQVrGVJBx5bz5DbSHMZJ8ICPyR1pVMr7anGOQ78Vc8SFakGR6Y1WBhBsUVUFz+cL4dDivqk6cjH1IJJ75Sgp5FBB1CApRWHgyxp+jCEp+RyM7GvB/ZDs88cmCtvvIptiRiVAbB01sj8OzzMxKpVr5ZD1RVYfV3BrzURsPfAshH3cWYpfN/Tk5ZnaPqyyUgvOFH8Zc+q8YRfrv5W++MRugyq7AOa+thAcjhFaNbgyzMf30SzX7MuOYBxvuv+Y9Ab+prR++3Nl7fbZHS2ojF0f+npho62KuSiyLJhDkXSCYvkGYKy3uZ0PI/79Q+XO/UMlvdg5vXT2JuPQ9VW9y9/lN7MPCtY+spbfqcUp+GbuqsJG2jhbe31MuuTDRZEI/Z88H6IompOWD6KEHBGXz+98/LVmJUHa/nT6WyW+0zN8Wv0W5P8wLkkdQKN7OfCcIf6LXIo+AVLyjmYF0RX8YSSh9o088Oc1HHU/hm555PSBgMdVXd2X5ZoIverofLYyQ06nPej1bQYBJWcOlxytzvZ79vXM2mfwb93Re8Q==
-sidebar_class_name: "get api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Related Trades"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/liquidity_pools/{liquidity_pool_id}/trades"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint represents successful trades fulfilled by the given liquidity pool and can be used in streaming mode. Streaming mode allows you to listen for new trades referencing this liquidity pool as they are added to the Stellar ledger. If called in streaming mode, Horizon will start at the earliest known trade unless a cursor is set, in which case it will start from that cursor. By setting the cursor value to now, you can stream trade created since your request time. 
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"liquidity_pool_id","in":"path","required":true,"description":"A unique identifier for this liquidity pool."},{"name":"cursor","in":"query","required":false,"description":"A number that points to a specific location in a collection of responses and is pulled from the paging_token value of a record.","schema":{"type":"integer","example":6606617478959105}},{"name":"order","in":"query","required":false,"description":"A designation of the order in which records should appear. Options include `asc` (ascending) or `desc` (descending). If this argument isn’t set, it defaults to `asc`.","schema":{"type":"string","enum":["asc","desc"]}},{"name":"limit","in":"query","required":false,"description":"The maximum number of records returned. The limit can range from 1 to 200 - an upper limit that is hardcoded in Horizon for performance reasons. If this argument isn’t designated, it defaults to 10.","schema":{"type":"integer","example":10}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"allOf":[{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"next":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"prev":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}}}},"title":"Links"},{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"base":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"counter":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operation":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","base","counter","operation"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string","title":"paging_token"},"ledger_close_time":{"type":"string"},"offer_id":{"type":"string"},"trade_type":{"type":"string"},"liquidity_pool_fee_bp":{"type":"number","format":"uint32"},"base_liquidity_pool_id":{"type":"string"},"base_offer_id":{"type":"string"},"base_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_amount":{"type":"string"},"base_asset_type":{"type":"string"},"base_asset_code":{"type":"string"},"base_asset_issuer":{"type":"string"},"counter_liquidity_pool_id":{"type":"string"},"counter_offer_id":{"type":"string"},"counter_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"counter_amount":{"type":"string"},"counter_asset_type":{"type":"string"},"counter_asset_code":{"type":"string"},"counter_asset_issuer":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"base_is_seller":{"type":"boolean"},"price":{"required":["id","paging_token","ledger_close_time","trade_type","base_amount","base_asset_type","counter_amount","counter_asset_type","base_is_seller"],"type":"object","properties":{"n":{"type":"string"},"d":{"type":"string"}},"title":"tradePrice"}}}}}}},"title":"Trade"}]},"examples":{"RetrieveRelatedTrades":{"value":{"_links":{"self":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/trades?cursor=&limit=2&order=asc"},"next":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/trades?cursor=120192370561220608&limit=2&order=asc"},"prev":{"href":"https://horizon-testnet.stellar.org/liquidity_pools/3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4/trades?cursor=120192344791343104&limit=2&order=desc"}},"_embedded":{"records":[{"_links":{"self":{"href":""},"base":{"href":"https://horizon-testnet.stellar.org/accounts/GAVH5JM5OKXGMQDS7YPRJ4MQCPXJUGH26LYQPQJ4SOMOJ4SXY472ZM7G"},"counter":{"href":"https://horizon-testnet.stellar.org/accounts/GBB4JST32UWKOLGYYSCEYBHBCOFL2TGBHDVOMZP462ET4ZRD4ULA7S2L"},"operation":{"href":"https://horizon-testnet.stellar.org/operations/3697472920621057"}},"id":"3697472920621057-0","paging_token":"3697472920621057-0","ledger_close_time":"2015-11-18T03:47:47Z","offer_id":"9","base_offer_id":"9","base_account":"GAVH5JM5OKXGMQDS7YPRJ4MQCPXJUGH26LYQPQJ4SOMOJ4SXY472ZM7G","base_amount":"10.0000000","base_asset_type":"native","counter_liquidity_pool":"3b476aff8a406a6ec3b61d5c038009cef85f2ddfaf616822dc4fec92845149b4","liquidity_pool_fee_bp":"30","counter_amount":"2.6700000","counter_asset_type":"credit_alphanum4","counter_asset_code":"JPY","counter_asset_issuer":"GBVAOIACNSB7OVUXJYC5UE2D4YK2F7A24T7EE5YOMN4CE6GCHUTOUQXM","base_is_seller":true,"price":{"n":"267","d":"1000"},"trade_type":"liquidity_pool"}]}}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/sidebar.ts b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/sidebar.ts
deleted file mode 100644
index ca27eb7a42..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/sidebar.ts
+++ /dev/null
@@ -1,318 +0,0 @@
-import type { SidebarsConfig } from "@docusaurus/plugin-content-docs";
-const sidebar: SidebarsConfig = {
-  apisidebar: [{
-    type: "categoría",
-    label: "Recursos",
-    collapsible: true,
-    collapsed: true,
-    items: [{
-      type: "doc",
-      id: "data/apis/horizon/api-reference/horizon"
-    }, {
-      type: "categoría",
-      label: "Cuentas",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-all-accounts",
-        label: "Listar todas las Cuentas",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-an-account",
-        label: "Recuperar una Cuenta",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-transactions-by-account-id",
-        label: "Recuperar las Transacciones de una Cuenta",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-operations-by-account-id",
-        label: "Recuperar las Operaciones de una Cuenta",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-payments-by-account-id",
-        label: "Recuperar los Pagos de una Cuenta",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-effects-by-account-id",
-        label: "Recuperar los Efectos de una Cuenta",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-offers-by-account-id",
-        label: "Recuperar las Ofertas de una Cuenta",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-trades-by-account-id",
-        label: "Recuperar las Negociaciones de una Cuenta",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-data-by-account-id",
-        label: "Recuperar los Datos de una Cuenta",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Activos",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-all-assets",
-        label: "Listar todos los Activos",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Balances Dignos de Reclamo",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-all-claimable-balances",
-        label: "Listar Todos los Balances Dignos de Reclamo",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-claimable-balance",
-        label: "Recuperar un Balance Digno de Reclamo",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/cb-retrieve-related-transactions",
-        label: "Recuperar Transacciones Relacionadas",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/cb-retrieve-related-operations",
-        label: "Recuperar Operaciones Relacionadas",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Efectos",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-all-effects",
-        label: "Listar Todos los Efectos",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Fondos de Liquidez",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-liquidity-pools",
-        label: "Listar Fondos de Liquidez",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-liquidity-pool",
-        label: "Recuperar un Fondo de Liquidez",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-related-effects",
-        label: "Recuperar Efectos Relacionados",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-related-trades",
-        label: "Recuperar Negociaciones Relacionadas",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/lp-retrieve-related-transactions",
-        label: "Recuperar Transacciones Relacionadas",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/lp-retrieve-related-operations",
-        label: "Recuperar Operaciones Relacionadas",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Leds",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-ledger",
-        label: "Recuperar un Ledger",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-ledgers-transactions",
-        label: "Recuperar las Transacciones de un Ledger",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-ledgers-payments",
-        label: "Recuperar los Pagos de un Ledger",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-ledgers-operations",
-        label: "Recuperar las Operaciones de un Ledger",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-ledgers-effects",
-        label: "Recuperar los Efectos de un Ledger",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-all-ledgers",
-        label: "Listar Todos los Ledgers",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Ofertas",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-all-offers",
-        label: "Listar Todas las Ofertas",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-offer-by-offer-id",
-        label: "Recuperar una Oferta",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-trades-by-offer-id",
-        label: "Recuperar las Negociaciones de una Oferta",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Operaciones",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-an-operation",
-        label: "Recuperar una Operación",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-an-operations-effects",
-        label: "Recuperar los Efectos de una Operación",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-all-operations",
-        label: "Listar Todas las Operaciones",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Pagos",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-all-payments",
-        label: "Listar Todos los Pagos",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-transactions-payments",
-        label: "Recuperar los Pagos de una Transacción",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Negociaciones",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/get-all-trades",
-        label: "Listar Todas las Negociaciones",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Transacciones",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-transaction",
-        label: "Recuperar una Transacción",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-transactions-operations",
-        label: "Recuperar las Operaciones de una Transacción",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-a-transactions-effects",
-        label: "Recuperar los Efectos de una Transacción",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-all-transactions",
-        label: "Listar Todas las Transacciones",
-        className: "api-método get"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/submit-a-transaction",
-        label: "Enviar una Transacción",
-        className: "api-método post"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/submit-async-transaction",
-        label: "Enviar una Transacción Asincrónicamente",
-        className: "api-método post"
-      }]
-    }]
-  }, {
-    type: "categoría",
-    label: "Agregaciones",
-    collapsible: true,
-    collapsed: true,
-    items: [{
-      type: "doc",
-      id: "data/apis/horizon/api-reference/horizon"
-    }, {
-      type: "categoría",
-      label: "Estadísticas de Tarifas",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-fee-stats",
-        label: "Recuperar Estadísticas de Tarifas",
-        className: "api-método get"
-      }]
-    }, {
-      type: "categoría",
-      label: "Libros de Órdenes",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/retrieve-an-order-book",
-        label: "Recuperar un Libro de Órdenes",
-        className: "método-api obtener"
-      }]
-    }, {
-      type: "categoría",
-      label: "Rutas",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-strict-receive-payment-paths",
-        label: "Listar rutas de pago de recepción estricta",
-        className: "método-api obtener"
-      }, {
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-strict-send-payment-paths",
-        label: "Listar rutas de pago de envío estrictas",
-        className: "método-api obtener"
-      }]
-    }, {
-      type: "categoría",
-      label: "Agregaciones de comercio",
-      items: [{
-        type: "doc",
-        id: "data/apis/horizon/api-reference/list-trade-aggregations",
-        label: "Listar agregaciones de comercio",
-        className: "método-api obtener"
-      }]
-    }]
-  }]
-};
-export default sidebar.apisidebar;
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/README.mdx
deleted file mode 100644
index 9c847e5f72..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/README.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Referencia de la API de Horizon
-sidebar_position: 20
-sidebar_label: Estructura
-description: Horizon es una API para interactuar con la red Stellar.
-sidebar_key: horizon-api-structure
----
-
-import DocCardList from "@theme/DocCardList";
-
-Cómo está estructurado Horizon.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/consistency.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/consistency.mdx
deleted file mode 100644
index 1eb51eef5b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/consistency.mdx
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Consistencia
-sidebar_position: 70
----
-
-Para los endpoints que sirven datos que pueden cambiar de ledger a ledger (por ejemplo, un saldo de cuenta), Horizon incluye un encabezado HTTP `Latest-Ledger` en su respuesta. El valor del encabezado HTTP `Latest-Ledger` es el número de secuencia del último ledger conocido por Horizon en el momento en que se procesó la solicitud. Horizon garantizará que todos los datos incluidos en la respuesta sean consistentes con ese ledger. Este mecanismo previene condiciones de carrera donde una solicitud se procesa en el límite de dos ledgers y asegura que la respuesta sea consistente con el ledger incluido en el encabezado HTTP `Latest-Ledger`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/pagination/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/pagination/README.mdx
deleted file mode 100644
index 76a34bad29..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/pagination/README.mdx
+++ /dev/null
@@ -1,271 +0,0 @@
----
-title: Paginación
-position: 60
----
-
-Para hacer posible explorar los millones de registros de recursos como transacciones y operaciones, Horizon paginación los datos que devuelve para puntos finales basados en colecciones.
-
-Cada transacción, operación, ledger, etc. se devuelve como un registro, y un grupo de registros se llama colección. Los registros se devuelven como una matriz bajo el atributo `_embedded`.
-
-Para moverte entre páginas de una colección de registros, utiliza los enlaces en los atributos `next` y `prev` anidados bajo el atributo de nivel superior `_links`.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- \_links
-  - matriz
-  - Proporciona enlaces para navegar a otras páginas.
-    - \_links.self
-      - matriz
-      - Una clave `href` con un enlace a la respuesta en sí misma como valor.
-    - \_links.next
-      - matriz
-      - Una clave `href` con un enlace a la siguiente página para este punto final como valor.
-    - \_links.prev
-      - matriz
-      - Una clave `href` con un enlace a la siguiente página para este punto final como valor.
-- \_embedded
-  - matriz
-  - Una clave `href` con un enlace a la siguiente página para este punto final como valor.
-    - \_embedded.records
-      - matriz
-      - Devuelve una matriz de registros.
-
-</AttributeTable>
-
-<CodeExample title="Ejemplo de Solicitud">
-
-```js
-var StellarSdk = require("stellar-sdk");
-var server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-
-server
-  .transactions()
-  .call()
-  .then(function (resp) {
-    // page 1
-    console.log(resp);
-    return resp.next();
-  })
-  .then(function (resp) {
-    // page 2
-    console.log(resp);
-  })
-  .catch(function (err) {
-    console.error(err);
-  });
-```
-
-</CodeExample>
-
-<ExampleResponse title="Ejemplo de Respuesta Paginada">
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=&limit=5&order=asc"
-    },
-    "next": {
-      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=113928152169844741&limit=5&order=asc"
-    },
-    "prev": {
-      "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906/operations?cursor=113928152169844737&limit=5&order=desc"
-    }
-  },
-  "_embedded": {
-    "records": [
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844737"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844737/effects"
-          }
-        },
-        "id": "113928152169844737",
-        "paging_token": "113928152169844737",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229445
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844738"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844738/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844738"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844738"
-          }
-        },
-        "id": "113928152169844738",
-        "paging_token": "113928152169844738",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229446
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844739"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844739/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844739"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844739"
-          }
-        },
-        "id": "113928152169844739",
-        "paging_token": "113928152169844739",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229447
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844740"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844740/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844740"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844740"
-          }
-        },
-        "id": "113928152169844740",
-        "paging_token": "113928152169844740",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229448
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844741"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113928152169844741/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113928152169844741"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113928152169844741"
-          }
-        },
-        "id": "113928152169844741",
-        "paging_token": "113928152169844741",
-        "transaction_successful": true,
-        "source_account": "GDO2BIMNH7T6MOJVPKEJHWAGMYGOQU5QMK5BKT5XMVWPZKHAGA4JNAQZ",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-28T19:44:09Z",
-        "transaction_hash": "2a09c3d79027721f2b8a78e2a936cbeda484bfe98a6e34856c1fee743b7e8906",
-        "amount": "0.0000000",
-        "price": "0.0001000",
-        "price_r": {
-          "n": 1,
-          "d": 10000
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "SLT",
-        "selling_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "offer_id": 126229449
-      }
-    ]
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx
deleted file mode 100644
index cc2da2d69a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/pagination/page-arguments.mdx
+++ /dev/null
@@ -1,269 +0,0 @@
----
-title: Argumentos de la Página
-sidebar_position: 20
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-<MethodTable>
-
-|     |                                                                    |
-| --- | ------------------------------------------------------------------ |
-| GET | `/{endpoint}?cursor={paging_token}&order={asc,desc}&limit={1-200}` |
-
-</MethodTable>
-
-<AttributeTable>
-
-- ARGUMENTO
-  - ¿REQUERIDO?
-  - DESCRIPCIÓN
-- cursor
-  - opcional
-  - Un número que apunta a una ubicación específica en una colección de respuestas y se obtiene del valor `paging_token` de un registro.
-- orden
-  - opcional
-  - Una designación del orden en que deben aparecer los registros. Las opciones incluyen `asc` (ascendente) o `desc` (descendente). Si este argumento no está establecido, por defecto es `asc`.
-- límite
-  - opcional
-  - El número máximo de registros devueltos. El límite puede variar de 1 a 200, un límite superior que está codificado en Horizon por razones de rendimiento. Si este argumento no está designado, por defecto es 10.
-
-</AttributeTable>
-
-<CodeExample title="Ejemplo de Solicitud">
-
-```curl
-curl "https://horizon-testnet.stellar.org/ledgers/26478723/operations?cursor=113725249324879872&limit=5&order=asc"
-```
-
-```js
-var StellarSdk = require("stellar-sdk");
-var server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-
-server
-  .operations()
-  .forLedger("26478723")
-  .cursor("113725249324879872")
-  .limit(5)
-  .order("asc")
-  .call()
-  .then(function (resp) {
-    console.log(resp);
-  })
-  .catch(function (err) {
-    console.error(err);
-  });
-```
-
-</CodeExample>
-
-<ExampleResponse title="Ejemplo de Respuesta">
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/26478723/operations?cursor=113725249324879872\u0026limit=5\u0026order=asc"
-    },
-    "next": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/26478723/operations?cursor=113725249324916737\u0026limit=5\u0026order=asc"
-    },
-    "prev": {
-      "href": "https://horizon-testnet.stellar.org/ledgers/26478723/operations?cursor=113725249324879873\u0026limit=5\u0026order=desc"
-    }
-  },
-  "_embedded": {
-    "records": [
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324879873"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/6adab48bbc0a38b9d40938b63a8ae0f5b334948c2d5acfb755dea616f98720d1"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324879873/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113725249324879873"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113725249324879873"
-          }
-        },
-        "id": "113725249324879873",
-        "paging_token": "113725249324879873",
-        "transaction_successful": true,
-        "source_account": "GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ",
-        "type": "manage_offer",
-        "type_i": 3,
-        "created_at": "2019-10-25T20:45:51Z",
-        "transaction_hash": "6adab48bbc0a38b9d40938b63a8ae0f5b334948c2d5acfb755dea616f98720d1",
-        "amount": "5048.0792092",
-        "price": "0.0000079",
-        "price_r": {
-          "n": 79,
-          "d": 10000000
-        },
-        "buying_asset_type": "credit_alphanum4",
-        "buying_asset_code": "BTC",
-        "buying_asset_issuer": "GATEMHCCKCY67ZUCKTROYN24ZYT5GK4EQZ65JJLDHKHRUZI3EUEKMTCH",
-        "selling_asset_type": "native",
-        "offer_id": 125121197
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324888065"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/c4de60af4815d94b6f3aa9947403f96dd0e8c3ba7d84eccce9c2c798470381ed"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324888065/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113725249324888065"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113725249324888065"
-          }
-        },
-        "id": "113725249324888065",
-        "paging_token": "113725249324888065",
-        "transaction_successful": true,
-        "source_account": "GCFKS7EBBZQTBBM7HHOASGZBE3L2TADWG6OJBVJXYIS44LQFXFL766UB",
-        "type": "manage_offer",
-        "type_i": 3,
-        "created_at": "2019-10-25T20:45:51Z",
-        "transaction_hash": "c4de60af4815d94b6f3aa9947403f96dd0e8c3ba7d84eccce9c2c798470381ed",
-        "amount": "103.0721239",
-        "price": "0.0655000",
-        "price_r": {
-          "n": 131,
-          "d": 2000
-        },
-        "buying_asset_type": "credit_alphanum4",
-        "buying_asset_code": "USD",
-        "buying_asset_issuer": "GDSRCV5VTM3U7Y3L6DFRP3PEGBNQMGOWSRTGSBWX6Z3H6C7JHRI4XFJP",
-        "selling_asset_type": "native",
-        "offer_id": 0
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324892161"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/6d0fe444dd346e05742776305f5e90dd102bd83dfa00a54cfd79bd94753beba0"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324892161/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113725249324892161"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113725249324892161"
-          }
-        },
-        "id": "113725249324892161",
-        "paging_token": "113725249324892161",
-        "transaction_successful": true,
-        "source_account": "GB44WLYD6HQXZHLRCPARIAMBASN35TDHXU5Q3I3DRHQMLLB3CBMIZLY5",
-        "type": "manage_buy_offer",
-        "type_i": 12,
-        "created_at": "2019-10-25T20:45:51Z",
-        "transaction_hash": "6d0fe444dd346e05742776305f5e90dd102bd83dfa00a54cfd79bd94753beba0",
-        "amount": "2942.0268642",
-        "price": "6.7000000",
-        "price_r": {
-          "n": 67,
-          "d": 10
-        },
-        "buying_asset_type": "credit_alphanum4",
-        "buying_asset_code": "SLT",
-        "buying_asset_issuer": "GCKA6K5PCQ6PNF5RQBF7PQDJWRHO6UOGFMRLK3DYHDOI244V47XKQ4GP",
-        "selling_asset_type": "native",
-        "offer_id": 0
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324908545"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/36907ac7f802a079fa1d7e7fddeb31decbed1218b47924243daaa508af8b1bbe"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324908545/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113725249324908545"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113725249324908545"
-          }
-        },
-        "id": "113725249324908545",
-        "paging_token": "113725249324908545",
-        "transaction_successful": true,
-        "source_account": "GBVI7F7QBE3ZEHP7HUAXAEKENITQKCXR5CML5JMOCHJN6EOQXLTSJYJI",
-        "type": "payment",
-        "type_i": 1,
-        "created_at": "2019-10-25T20:45:51Z",
-        "transaction_hash": "36907ac7f802a079fa1d7e7fddeb31decbed1218b47924243daaa508af8b1bbe",
-        "asset_type": "credit_alphanum4",
-        "asset_code": "TFC",
-        "asset_issuer": "GDS3XDJAA4VY6MJYASIGSIMPHZ7AQNZ54RKLWT7MWCOU5YKYEVCNLVS3",
-        "from": "GBVI7F7QBE3ZEHP7HUAXAEKENITQKCXR5CML5JMOCHJN6EOQXLTSJYJI",
-        "to": "GAMKXMT23OMMOFJMZIHT5T3C65JI5YGAOHJMDYBBS4JJBB3X2CVLT3GO",
-        "amount": "0.0380000"
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324916737"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/785058d3363b448c95943a40230333b8d523607c9617089bb17c9202a2e7384a"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/113725249324916737/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=113725249324916737"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=113725249324916737"
-          }
-        },
-        "id": "113725249324916737",
-        "paging_token": "113725249324916737",
-        "transaction_successful": true,
-        "source_account": "GDD7ABRF7BCK76W33RXDQG5Q3WXVSQYVLGEMXSOWRGZ6Z3G3M2EM2TCP",
-        "type": "manage_offer",
-        "type_i": 3,
-        "created_at": "2019-10-25T20:45:51Z",
-        "transaction_hash": "785058d3363b448c95943a40230333b8d523607c9617089bb17c9202a2e7384a",
-        "amount": "0.0000000",
-        "price": "1.0000000",
-        "price_r": {
-          "n": 1,
-          "d": 1
-        },
-        "buying_asset_type": "native",
-        "selling_asset_type": "credit_alphanum4",
-        "selling_asset_code": "BTC",
-        "selling_asset_issuer": "GBVOL67TMUQBGL4TZYNMY3ZQ5WGQYFPFD5VJRWXR72VA33VFNL225PL5",
-        "offer_id": 125126043
-      }
-    ]
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/rate-limiting.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/rate-limiting.mdx
deleted file mode 100644
index e4d70f86d3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/rate-limiting.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Limitación de tasa
-sidebar_position: 40
----
-
-Los límites de tasa de Horizon se aplican por dirección IP. Se puede configurar a través de la opción `PER_HOUR_RATE_LIMIT` y, por defecto, se establece en 3600 solicitudes por hora. Se recomienda que los operadores de Horizon ajusten este valor según sus capacidades infraestructurales individuales y necesidades de uso.
-
-Este límite se puede desactivar completamente estableciendo el parámetro en `0`.
-
-Cuando un cliente excede este límite, Horizon devolverá un error `429 Too Many Requests`.
-
-Mientras se transmite, cada actualización del flujo cuenta como una solicitud y contra el límite de tasa asignado a un cliente.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/response-format.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/response-format.mdx
deleted file mode 100644
index 62565c4d50..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/response-format.mdx
+++ /dev/null
@@ -1,211 +0,0 @@
----
-title: Formato de respuesta
-sidebar_position: 20
----
-
-Horizon entrega respuestas como objetos JSON formateados según [HAL](https://en.wikipedia.org/wiki/Hypertext_Application_Language). El formato HAL hace que Horizon sea más explorables, paginando respuestas y conectando recursos padres e hijos. Consumir este formato es sencillo usando una de las muchas [bibliotecas de código abierto disponibles](https://github.com/mikekelly/hal_specification/wiki/Libraries) para la mayoría de los lenguajes de programación principales.
-
-HAL es solo JSON con dos nombres de atributos reservados:
-
-- `_links`
-- `_embedded`
-
-Si una respuesta es un único registro, la sección `_links` proporcionará enlaces a los registros padres o hijos, y no habrá propiedad `_embedded`.
-
-Si una respuesta es una colección, la sección `_links` proporcionará enlaces de [paginación](./pagination/README.mdx), y la lista de registros de la respuesta estará anidada debajo de la propiedad `_embedded`.
-
-<AttributeTable>
-
-- ATRIBUTOS
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- \_links
-  - array
-  - Proporciona enlaces para navegar a otras páginas o a padres e hijos.
-- \_embedded
-  - array
-  - Presente al consultar un endpoint que responde con una colección de registros.
-
-</AttributeTable>
-
-<ExampleResponse title="Respuesta de ejemplo">
-
-```json
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ/payments?cursor=&limit=5&order=asc"
-    },
-    "next": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ/payments?cursor=111764193027313665&limit=5&order=asc"
-    },
-    "prev": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ/payments?cursor=111720727958269953&limit=5&order=desc"
-    }
-  },
-  "_embedded": {
-    "records": [
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/111720727958269953"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/4034838d5b47e4f8c23776faca4d9403637b1f037e436759b57fc892ae5cd96c"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/111720727958269953/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=111720727958269953"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=111720727958269953"
-          }
-        },
-        "id": "111720727958269953",
-        "paging_token": "111720727958269953",
-        "transaction_successful": true,
-        "source_account": "GAR4S3ASZ4HTJ6GQ2DEDLVL4YE6D64UPIOQI4I67L5VPYBGEZDGOI462",
-        "type": "create_account",
-        "type_i": 0,
-        "created_at": "2019-09-26T12:34:24Z",
-        "transaction_hash": "4034838d5b47e4f8c23776faca4d9403637b1f037e436759b57fc892ae5cd96c",
-        "starting_balance": "20.0000000",
-        "funder": "GAR4S3ASZ4HTJ6GQ2DEDLVL4YE6D64UPIOQI4I67L5VPYBGEZDGOI462",
-        "account": "GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ"
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/111721376498331649"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/cbf92ce9e2b75b0182597acb1e7c0b58695ec6f69e84a8625c5ab1dda8df31bc"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/111721376498331649/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=111721376498331649"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=111721376498331649"
-          }
-        },
-        "id": "111721376498331649",
-        "paging_token": "111721376498331649",
-        "transaction_successful": true,
-        "source_account": "GAR4S3ASZ4HTJ6GQ2DEDLVL4YE6D64UPIOQI4I67L5VPYBGEZDGOI462",
-        "type": "payment",
-        "type_i": 1,
-        "created_at": "2019-09-26T12:47:50Z",
-        "transaction_hash": "cbf92ce9e2b75b0182597acb1e7c0b58695ec6f69e84a8625c5ab1dda8df31bc",
-        "asset_type": "native",
-        "from": "GAR4S3ASZ4HTJ6GQ2DEDLVL4YE6D64UPIOQI4I67L5VPYBGEZDGOI462",
-        "to": "GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ",
-        "amount": "5000.0000000"
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/111722218311925761"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/9fcf20d23862f40cd8a59f0ad0247a7d56a1b38cb79e4953b5aad8df5f2608a7"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/111722218311925761/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=111722218311925761"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=111722218311925761"
-          }
-        },
-        "id": "111722218311925761",
-        "paging_token": "111722218311925761",
-        "transaction_successful": true,
-        "source_account": "GBSIPZRLSM2KMLUZYEGKU2WMA6HPEE3NGB47YY4MLK43ISLLCJKFA2F2",
-        "type": "payment",
-        "type_i": 1,
-        "created_at": "2019-09-26T13:05:12Z",
-        "transaction_hash": "9fcf20d23862f40cd8a59f0ad0247a7d56a1b38cb79e4953b5aad8df5f2608a7",
-        "asset_type": "native",
-        "from": "GBSIPZRLSM2KMLUZYEGKU2WMA6HPEE3NGB47YY4MLK43ISLLCJKFA2F2",
-        "to": "GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ",
-        "amount": "10.0000000"
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/111747107647434753"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/44af49d32061cdb352d131559560559e7be815b16c45412b7682600c71224623"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/111747107647434753/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=111747107647434753"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=111747107647434753"
-          }
-        },
-        "id": "111747107647434753",
-        "paging_token": "111747107647434753",
-        "transaction_successful": true,
-        "source_account": "GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ",
-        "type": "payment",
-        "type_i": 1,
-        "created_at": "2019-09-26T21:43:41Z",
-        "transaction_hash": "44af49d32061cdb352d131559560559e7be815b16c45412b7682600c71224623",
-        "asset_type": "credit_alphanum4",
-        "asset_code": "BTC",
-        "asset_issuer": "GATEMHCCKCY67ZUCKTROYN24ZYT5GK4EQZ65JJLDHKHRUZI3EUEKMTCH",
-        "from": "GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ",
-        "to": "GBSIPZRLSM2KMLUZYEGKU2WMA6HPEE3NGB47YY4MLK43ISLLCJKFA2F2",
-        "amount": "0.0000709"
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/111764193027313665"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/7bd57f8cc75ce2d9740568eade9700cd7b19491a2c938232e5b3f0768f3e588a"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/111764193027313665/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc\u0026cursor=111764193027313665"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc\u0026cursor=111764193027313665"
-          }
-        },
-        "id": "111764193027313665",
-        "paging_token": "111764193027313665",
-        "transaction_successful": true,
-        "source_account": "GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ",
-        "type": "payment",
-        "type_i": 1,
-        "created_at": "2019-09-27T03:37:57Z",
-        "transaction_hash": "7bd57f8cc75ce2d9740568eade9700cd7b19491a2c938232e5b3f0768f3e588a",
-        "asset_type": "credit_alphanum4",
-        "asset_code": "BTC",
-        "asset_issuer": "GATEMHCCKCY67ZUCKTROYN24ZYT5GK4EQZ65JJLDHKHRUZI3EUEKMTCH",
-        "from": "GCRGHKY6RBFVQLF2JCHB7TK7A5BIABITFKVIEOXK4BPEIDE446OEFYXZ",
-        "to": "GBSIPZRLSM2KMLUZYEGKU2WMA6HPEE3NGB47YY4MLK43ISLLCJKFA2F2",
-        "amount": "0.0107156"
-      }
-    ]
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/streaming.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/streaming.mdx
deleted file mode 100644
index 610b8cb9a3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/streaming.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Transmisión
-sidebar_position: 30
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Horizon proporciona un mecanismo de transmisión para recibir eventos en casi tiempo real. En lugar de enviar repetidamente solicitudes a Horizon para actualizaciones por lotes, se establece una conexión entre un cliente y Horizon con actualizaciones a una respuesta de endpoint transmitiéndose a medida que se cierran nuevos ledgers y ocurren actualizaciones.
-
-Esto reduce las solicitudes que no devuelven datos y permite actualizaciones casi instantáneas del lado del cliente.
-
-Todos los atributos para los endpoints que permiten transmisión son los mismos que las respuestas regulares. Un llamador puede iniciar la transmisión estableciendo ‘Accept: text/event-stream’ en el encabezado HTTP al realizar la solicitud.
-
-<MethodTable title="Endpoints con Transmisión">
-
-|                                                                      |
-| -------------------------------------------------------------------- |
-| [Libros contables](../resources/ledgers/README.mdx)                  |
-| [Transacciones](../resources/transactions/README.mdx)                |
-| [Operaciones](../resources/operations/README.mdx)                    |
-| [Pagos](../resources/payments/README.mdx)                            |
-| [Efectos](../resources/effects/README.mdx)                           |
-| [Cuentas](../resources/accounts/README.mdx)                          |
-| [Operaciones de Cambio](../resources/trades/README.mdx)              |
-| [Libros de Órdenes](../aggregations/order-books/README.mdx)          |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/xdr.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/xdr.mdx
deleted file mode 100644
index 27502ec75a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/structure/xdr.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: XDR
-sidebar_position: 50
----
-
-En la red Stellar, las transacciones se codifican utilizando un protocolo estándar llamado [Representación de Datos Externos](https://en.wikipedia.org/wiki/External_Data_Representation) (XDR).
-
-En Horizon, solo encontrarás XDR al [publicar](../submit-a-transaction.api.mdx) y [obtener](../retrieve-a-transaction.api.mdx) transacciones y en el encabezado del [ledger](../resources/ledgers/README.mdx).
-
-Cuando publicas una transacción, un cliente codificará la transacción como XDR antes de enviarla a Horizon.
-
-Cuando solicitas una transacción, Horizon devuelve algunos datos sobre la transacción en JSON legible por humanos. Los datos canónicos completos sobre la transacción están codificados en XDR legible por máquina, disponibles en los atributos XDR al final de la respuesta.
-
-Puedes decodificar este XDR en la [página XDR](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;) de Stellar Lab.
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO
-  - DESCRIPCIÓN
-- envelope_xdr
-  - cadena
-  - La transacción codificada en XDR tal como la ve stellar-core.
-- result_xdr
-  - cadena
-  - Los efectos de una transacción codificados en XDR.
-- result_meta_xdr
-  - cadena
-  - Los detalles sobre los efectos de una transacción codificados en XDR.
-- fee_meta_xdr
-  - cadena
-  - Las tarifas asociadas con la transacción codificadas en XDR.
-
-</AttributeTable>
-
-<ExampleResponse title="Ejemplo de respuesta de transacción con XDR">
-
-```json
-{
-  // Response truncated to highlight XDR-related attributes
-  "envelope_xdr": "AAAAAPewD+/6X8o0bx3bp49Wf+mUhG3o+TUrcjcst717DWJVAAAAyAFvzscADTkNAAAAAAAAAAAAAAACAAAAAAAAAAYAAAACWE1BVEsAAAAAAAAAAAAAAAPvNOuztX4IjvV8pztsEc1/ZnTz0G3p5Cx4vcf04+xUAAONfqTGgAAAAAAAAAAABQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAD2NyeXB0b21hcmluZS5ldQAAAAAAAAAAAAAAAAF7DWJVAAAAQK3vfUCZ8mbjW3ssMd0n1tJTF9Fv6EbuJ6cWKkYXBqG5itqanPbFzIQoZEHbPS8nr2vo4dROvKI0uQzNcfExKwM=",
-  "result_xdr": "AAAAAAAAAMgAAAAAAAAAAgAAAAAAAAAGAAAAAAAAAAAAAAAFAAAAAAAAAAA=",
-  "result_meta_xdr": "AAAAAQAAAAIAAAADAZU3mQAAAAAAAAAA97AP7/pfyjRvHdunj1Z/6ZSEbej5NStyNyy3vXsNYlUAAAAABlxskAFvzscADTkMAAAAAgAAAAAAAAAAAAAAD2NyeXB0b21hcmluZS5ldQABAAAAAAAAAAAAAAAAAAAAAAAAAQGVN5kAAAAAAAAAAPewD+/6X8o0bx3bp49Wf+mUhG3o+TUrcjcst717DWJVAAAAAAZcbJABb87HAA05DQAAAAIAAAAAAAAAAAAAAA9jcnlwdG9tYXJpbmUuZXUAAQAAAAAAAAAAAAAAAAAAAAAAAAIAAAACAAAAAwGVN5gAAAABAAAAAPewD+/6X8o0bx3bp49Wf+mUhG3o+TUrcjcst717DWJVAAAAAlhNQVRLAAAAAAAAAAAAAAAD7zTrs7V+CI71fKc7bBHNf2Z089Bt6eQseL3H9OPsVAAATfBgJfPoAAONfqTGgAAAAAABAAAAAAAAAAAAAAABAZU3mQAAAAEAAAAA97AP7/pfyjRvHdunj1Z/6ZSEbej5NStyNyy3vXsNYlUAAAACWE1BVEsAAAAAAAAAAAAAAAPvNOuztX4IjvV8pztsEc1/ZnTz0G3p5Cx4vcf04+xUAABN8GAl8+gAA41+pMaAAAAAAAEAAAAAAAAAAAAAAAIAAAADAZU3mQAAAAAAAAAA97AP7/pfyjRvHdunj1Z/6ZSEbej5NStyNyy3vXsNYlUAAAAABlxskAFvzscADTkNAAAAAgAAAAAAAAAAAAAAD2NyeXB0b21hcmluZS5ldQABAAAAAAAAAAAAAAAAAAAAAAAAAQGVN5kAAAAAAAAAAPewD+/6X8o0bx3bp49Wf+mUhG3o+TUrcjcst717DWJVAAAAAAZcbJABb87HAA05DQAAAAIAAAAAAAAAAAAAAA9jcnlwdG9tYXJpbmUuZXUAAQAAAAAAAAAAAAAAAAAAAA==",
-  "fee_meta_xdr": "AAAAAgAAAAMBlTeXAAAAAAAAAAD3sA/v+l/KNG8d26ePVn/plIRt6Pk1K3I3LLe9ew1iVQAAAAAGXG1YAW/OxwANOQwAAAACAAAAAAAAAAAAAAAPY3J5cHRvbWFyaW5lLmV1AAEAAAAAAAAAAAAAAAAAAAAAAAABAZU3mQAAAAAAAAAA97AP7/pfyjRvHdunj1Z/6ZSEbej5NStyNyy3vXsNYlUAAAAABlxskAFvzscADTkMAAAAAgAAAAAAAAAAAAAAD2NyeXB0b21hcmluZS5ldQABAAAAAAAAAAAAAAAAAAAA"
-  // Response truncated to highlight XDR-related attributes
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/submit-a-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/submit-a-transaction.api.mdx
deleted file mode 100644
index c3570cc6a7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/submit-a-transaction.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: submit-a-transaction
-title: "Submit a Transaction"
-description: "This endpoint actually submits a transaction to the Stellar network. It only takes a single, required parameter: the signed transaction. Refer to the Transactions page for details on how to craft a proper one. If you submit a transaction that has already been included in a ledger, this endpoint will return the same response as would’ve been returned for the original transaction submission. This allows for safe resubmission of transactions in error scenarios, as highlighted in the error-handling guide."
-sidebar_label: "Submit a Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztGmlv2zryrxD6sK+HHV+JXQco3to5HLdpDidp2qSFQVEjiQ1FKiRlJw0C7N/Yv7e/ZDGSD8l20rR9eK+Lt/6QwOZwLs7B4cydY2lgnM1L51RTaSizXEnjfC45HhimeYzfnU3nNOSGgPRixaUllNmECnFLTOJG3BpCiZ1vJ1YRGwI5sSAE1USCHSt9tUb6ligpbomlV4B7DJeBgBLRcJ1wDR6JqaYRWNCbKQLDAwleHvUaGYAPekohzzOJaQDEV5p4YCkXhihJQjVGWKapbwklsVYxaKIkrJG+T25VMpFgUYCQWhJSQ6jQQL1b4gJIwiUTiQce4ZJQIsALQJeILWhmzIUgGmyiZSYCjYBoMLGSBgg1ZKwS4f3nX/8eQYY0gwUv5Rx3KM0DLqkoMJRyaUyqgfQoqBBqbNJNhvopiRkIUX5+s0F+QWsEZSCp5sqUkJWQB6HgQWgzkZB4ClYOqfQElwEJEu7BmlNyUG0UkfU9Z9M5SXXWyWnfKTmzs0NrunM4Ws11AvrWKTmSRuBsOvbGKTmGhRBRZ/POsbcx/mqs5jJwli0OiEsNNNfLIJlCvX/YHqSyhVCwCee+5ExNyNm0OoH7z/hLpnSDpOrVKv4rUjhJGANjnJLDlLQgLYLQOBacpbJWvhiEu1tmWblfgFkUOjUoyzMqQ4hc8Dzk4lugGpjSnskBUq0p6opbiMy3EUQQqWUl3pfShaF7a8GsXB4KLq+egN+A8L8NFWrwVx2lr3RErbPpIDUkayGKBbUF1bhKCaDSuS+c32WG9HPJsdwKyOGgjKkkO6VfiKssDvxiTM389Qkn/acyBr4PzP5qXMUaGHjwq7FlMECB96uxlYu9vxRnC0BpBJtHjZmnFrxjbpE5K8hpvijt5/uSw71V4kw54V5qTzTgMhhadQVyGXp6ssb4iVglbckJqQlXblyKNlxayKSaaZRL26gjMNOACh1Su5oJlWgGw+WwOpMqptaCxlzZu+yUL6rl9ue7jY37nLzU8zTm0Hl4HkbJDazQ0SLEcJUil7gaGrhOQDJYCevDH8d+DtdDIvwsxodERkAWUh08oLeI3gx9WK2CmS0PF9XwmGWAHIFQMQxvPL0SLd4nhf3WcgSWPgiDUj0KkN5Usl9X2QEPJLWJhqdckr55QPfzE8ohnoR+JT3+xGRpeQSuSuRTgnLE5RDhHzzTBxZzvOau2Ed5Rk/nbMyCwvewtRRGiow9uPwE1vbzzCA+Lp/mzKsAhzT4DuCM7WFA48fdIJn7wY3VdJjWmfo77Oz+KYqY+oCbRPHw+3Lmyug/p5iu/1kukvt5F6CbRHG+7sOEKCXo/2EBH4uvuS19FLMg+sJ9g3vOQuYv5PlJUs9dQ3LpeSkZP5wHi1mvmDzmoiwnhoWgXwjxywE9H50L5/D5/r5g/dlbwIJJwA2NYpGdWgZAT4v2MaIigXkd65yCsaT4oJAvZJ33vfdfva3uGYt2E1bf/eL1xMgNXr928hXttGbN7pxOaG1sNiuVUGn+VcmyBWMl2DWTvUutKR1U8u8klVfgV1nTa1YbGy3Xb9fcqlv1Wq+qVbe13vL9at31W41areU1oFprNdtV5vp+c73GaLPl1+rrC0Xqd7Ax2WUqva3+Xuf4/fnFXr3T3eh2Nw6Omo3d7kl/sNNrtfaPLy4Ozt6/3a7vH9T7h1v7h6fNg1b93ZuD4t3wOyhnm0yl1mhvtDaWa8e/SpeVORt3v7NEG6VLgkfclpT2QKdXrnnFkD76FKrLv4zvCQ9PZzpffP4g17+n6F9Tw/6RUX290W6vt6rVZrWx3mq064vV5M/RwWe0RwgtpIK/zhsn1Zrz05gWKzpnUepiRYcHO63h/gjiU8fOfLRY1zn1ar1WrjbK9Y3Tem2ztr5Zq10s55NN54cjyyMlGeqh0Wi2a83GRqNa31hITj9FtFAUObVqNZfdpt+Xip/aYmnjdPAT4J+tY7bztn7rH3faW3v6w8v62burQd+t1MZfhX17vRe7Xp+9ceOXbuW40+n0jjsdvvMx3Y/fOzud4qcbfDhqHM/Wu92ziw8H1f7u4Pbj+cbXj+cHVXreTub7s03p3zfd8bF237Q729U+WL91cXw72AlHlQ/bh+fVawXCVsOxSOTGqJ0juNuGPA+7s/Xjt94b2Xt1POCj9k0vrh1etzpbo8rNoN6VB9df/LM93TtIaCtat+euTmTjZS/qfGky2rj5+nL9Io7PB6fu6PSMbd2MYndvZ3DxauM4+Pi6eEmY6LIz0c30syhb9nm94k6RP4w+/tnudPrhwXi+62qvu2WNrHaOjsNmrWLF9pudk16lzd5tuCfXYfO8cbK3dd70o0oVwT+c7LlSdjpb/UHQefizeHB5hv9Q+t3VZB6jX1BYsWLOaevd3BTTz3eactfrewki6oe9R/SUO8plCfhO4+foA/sx+ukdL/dU4Fi4scU76ealE1cj5t50e28rjR0qz5radN5WKrt7H3usfn3QPgbzsb6hE5fXLpKk6fvr9OPWUXyj/b2jVhhF4mL3IGkfDMb7vZfCsMGu/Cq2uni/zO679+lzhQ0VxqJYGZuVGRjfC0kL+QI9mjbBEi2elvlWdr9OMzhykPVPnfvSQxj9BBXxFJy7U8hpV9bBXhmXftZMmlzq9zK8TslBUbLd1bXqWi1NdFFE9e0cCruqI+5hR1eSvdPTI9I56mPX1aOWThuLq3rBXAZgsHksPaKhnCrOpNDpzlgrL2HgEfd2FYqsC4s1fdauxS4sNTxrDjMlTRLBdCsdgcbucK65RzQIavkIpr3kGHT6QCAZlJXmILEtmjKiIdZgQNrsOkoSkzE1ZWhLaZi0ZVHynByu5l6AjV47xl4vjeNM2uLOI62wSjZE8CsgYyoEWFMiHjCQVlPBv4JH4IaFFBVWSjFQYwBlNgnolCMyPQ2rpj3tvGGWSNqLxSOaZGfiUoHClgg2hq0GGhEYgZzyUeggW5XbubZkWX93S7jMH+jnZ1P39CC7imhTuOVO2K4wpaEslQfP/1bW80l+klNyjEriAi6BQV2OOCXsbLBfIpS4Wo0NTliodGJj2vmf6fpk+635pq49xUzFKiVMxXhXBjWtiAY0pxQbU/hQccPtLeK/VYlGa0OFlsgYxyqYiiKQXjorgoqiEgkTLo0F6uGmiF7hrITHNTCbniGjQphUzvRY0ykKknmMC2Y6lEK9iEtuLGgyNfHUHKe6QRKoYvJM52deLrdnkv5GukIFcx2Mx+Oi8DPIsitUUKFlCeOySWQZs1AI5Un+eJ7NkSh0E8quAo2Pt0TJRW/IbEezkFtgNtFUEB6hz0OUnnx6QtyQiH5RmkxSB8H3z+drZFdpgnkG32DxZ+qqxJIJi6jACb2ZaSgPcP6jRFgI7IogdF5+JEl6qNq5AgJuw8RdYyqqTPRQCVTFFcqtRBQ1XUH34gzMNHVW8HlYSyoyS+md9bd3hruHg+H2zvud/cOjncHJWuQ9Tw+zC77SgGbhQsBliXD7Gw70aBsSDdymtYgMsrkfkPi6Ly0BFqr5gM0lOi05UN6PhAniKZZE0/CzSV68GAPxFJHK4gSS0gaITqREJqZqxAPNghQlaE8eFehM+Rgys7QXL7LwACYGxtMBL0Sd7h2OqOBeKuBwKfMBOoYGYseKGMBJIIuuJRloOQk5HjCVxGKinwiDNI9ipS2VNjU/V6VqFJy6XKA/4q6c8a0VHAN9L6KSBmAIDqCpsSzh+Bh4ZU+N5cz4lF8UVcWWR2lIRJqTnRjyMCAqn0h8ISHPxvBbOsc18zscucKRtU/OFo3TZIHoPjkz3aGJpM87OjKH/klmZrmrWuGZA4HKyi9PrHEygURZ+mw4GZaasp039110TDp5Hy1eBYsXP4goT1dBCPXP/Bq+E3IG0kCOViemLARSX8Oimntouz4HPVspZytzipNgQ9PV7B0xQ2oq+/2tnYOTHdyyFtpIpM8weGWOqMyLN527Kz76Fu4Vd/PBrP8PIP69BxBztV8lFpSnbYbUHu8mhdilUyjEPpecEOu0zUvn7g7zyJkW9/f4czaUiOWZxw11Bb4v+VQYeMT6ng0mFvKcPMTMFdxORxwnzQ0nra1GVHOk4mxe4vhICNRDz7q8m+zoMAaxze1amkBELLPi8+jw5NS5v/8vko4IoA==
-sidebar_class_name: "post api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Submit a Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint actually submits a transaction to the Stellar network. It only takes a single, required parameter: the signed transaction. Refer to the Transactions page for details on how to craft a proper one. If you submit a transaction that has already been included in a ledger, this endpoint will return the same response as would’ve been returned for the original transaction submission. This allows for safe resubmission of transactions in error scenarios, as highlighted in the error-handling guide.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"query","name":"tx","schema":{"type":"string","description":"The base64-encoded XDR of the transaction."},"required":true}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success","content":{"application/json":{"schema":{"type":"object","properties":{"_embedded":{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","properties":{"memo":{"type":"string"},"memo_bytes":{"type":"string"},"_links":{"type":"object","properties":{"self":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"account":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"ledger":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"operations":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"effects":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"precedes":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"succeeds":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"},"transaction":{"type":"object","properties":{"href":{"type":"string","format":"link"},"templated":{"type":"boolean"}},"required":["href"],"title":"link"}},"required":["self","account","ledger","operations","effects","precedes","succeeds","transaction"]},"id":{"type":"string","title":"id"},"paging_token":{"type":"string"},"successful":{"type":"boolean"},"hash":{"type":"string"},"ledger":{"type":"integer","format":"int32"},"created_at":{"type":"string"},"source_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"account_muxed":{"type":"string"},"account_muxed_id":{"type":"string"},"source_account_sequence":{"type":"string"},"fee_account":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed":{"type":"string","pattern":"G[A-Z0-9]{55}","title":"address"},"fee_account_muxed_id":{"type":"string"},"fee_charged":{"type":"string"},"max_fee":{"type":"string"},"operation_count":{"type":"integer","format":"int32"},"envelope_xdr":{"type":"string"},"result_xdr":{"type":"string"},"result_meta_xdr":{"type":"string"},"fee_meta_xdr":{"type":"string"},"memo_type":{"type":"string"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"preconditions":{"type":"object","properties":{"timebounds":{"type":"object","properties":{"min_time":{"type":"string"},"max_time":{"type":"string"}},"title":"TransactionPreconditionsTimebounds"},"ledgerbounds":{"type":"object","properties":{"min_ledger":{"type":"string"},"max_ledger":{"type":"string"}},"title":"TransactionPreconditionsLedgerbounds"},"min_account_sequence":{"type":"string"},"min_account_sequence_age":{"type":"string"},"min_account_sequence_ledger_gap":{"type":"integer","format":"uint32"},"extra_signers":{"type":"array","items":{"type":"string"}}},"title":"TransactionPreconditions"},"fee_bump_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"}},"title":"FeeBumpTransaction"},"inner_transaction":{"type":"object","properties":{"hash":{"type":"string","title":"hash"},"signatures":{"type":"array","items":{"type":"string","pattern":"G[A-Z0-9]{55}"},"title":"signatures"},"max_fee":{"type":"string"}},"title":"InnerTransaction"}},"required":["id","paging_token","successful","hash","ledger","created_at","source_account","source_account_sequence","fee_account","fee_charged","max_fee","operation_count","envelope_xdr","result_xdr","result_meta_xdr","memo_type","signatures"]}}}}},"title":"SubmitTransaction"},"examples":{"SubmitaTransaction":{"value":{"memo":"Test Transaction","memo_bytes":"VGVzdCBUcmFuc2FjdGlvbg==","_links":{"self":{"href":"https://horizon-testnet.stellar.org/transactions/8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124"},"account":{"href":"https://horizon-testnet.stellar.org/accounts/GCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72MJN"},"ledger":{"href":"https://horizon-testnet.stellar.org/ledgers/139575"},"operations":{"href":"https://horizon-testnet.stellar.org/transactions/8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124/operations{?cursor,limit,order}","templated":true},"effects":{"href":"https://horizon-testnet.stellar.org/transactions/8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124/effects{?cursor,limit,order}","templated":true},"precedes":{"href":"https://horizon-testnet.stellar.org/transactions?order=asc&cursor=599470060347392"},"succeeds":{"href":"https://horizon-testnet.stellar.org/transactions?order=desc&cursor=599470060347392"},"transaction":{"href":"https://horizon-testnet.stellar.org/transactions/8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124"}},"id":"8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124","paging_token":"599470060347392","successful":true,"hash":"8ef0c6d60357bf91b0b0d7800b747ff02bf73117d3e017690cbff641ca67f124","ledger":139575,"created_at":"2021-03-25T21:14:11Z","source_account":"GCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72MJN","source_account_sequence":"599336916353025","fee_account":"GCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72MJN","fee_charged":"100","max_fee":"100","operation_count":1,"envelope_xdr":"AAAAAgAAAACQcEK2yfQA9CHrX+2UMkRIb/1wzltKqHpbdIcJbp+b/QAAAGQAAiEYAAAAAQAAAAEAAAAAAAAAAAAAAABgXP3QAAAAAQAAABBUZXN0IFRyYW5zYWN0aW9uAAAAAQAAAAAAAAABAAAAAJBwQrbJ9AD0Ietf7ZQyREhv/XDOW0qoelt0hwlun5v9AAAAAAAAAAAF9eEAAAAAAAAAAAFun5v9AAAAQKdJnG8QRiv9xGp1Oq7ACv/xR2BnNqjfUHrGNua7m4tWbrun3+GmAj6ca3xz+4ZppWRTbvTUcCxvpbHERZ85QgY=","result_xdr":"AAAAAAAAAGQAAAAAAAAAAQAAAAAAAAABAAAAAAAAAAA=","result_meta_xdr":"AAAAAgAAAAIAAAADAAIhNwAAAAAAAAAAkHBCtsn0APQh61/tlDJESG/9cM5bSqh6W3SHCW6fm/0AAAAXSHbnnAACIRgAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAIhNwAAAAAAAAAAkHBCtsn0APQh61/tlDJESG/9cM5bSqh6W3SHCW6fm/0AAAAXSHbnnAACIRgAAAABAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAA=","fee_meta_xdr":"AAAAAgAAAAMAAiEYAAAAAAAAAACQcEK2yfQA9CHrX+2UMkRIb/1wzltKqHpbdIcJbp+b/QAAABdIdugAAAIhGAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAEAAiE3AAAAAAAAAACQcEK2yfQA9CHrX+2UMkRIb/1wzltKqHpbdIcJbp+b/QAAABdIduecAAIhGAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAAAAAA==","memo_type":"text","signatures":["p0mcbxBGK/3EanU6rsAK//FHYGc2qN9QesY25rubi1Zuu6ff4aYCPpxrfHP7hmmlZFNu9NRwLG+lscRFnzlCBg=="]}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/submit-async-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/submit-async-transaction.api.mdx
deleted file mode 100644
index aae379ebbc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/submit-async-transaction.api.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-id: submit-async-transaction
-title: "Submit a Transaction Asynchronously"
-description: "This endpoint submits transactions to the Stellar network asynchronously. It is designed to allow users to submit transactions without blocking them while waiting for a response from Horizon. At the same time, it also provides clear response status codes from stellar-core to help understand the status of the submitted transaction. You can then use Horizon's [GET transaction endpoint](https://developers.stellar.org/docs/data/apis/horizon/api-reference/resources/retrieve-a-transaction) to wait for the transaction to be included in a ledger and ingested by Horizon."
-sidebar_label: "Submit a Transaction Asynchronously"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW1tvG7cS/isDviQOVpLdXOuiwFFiJzGOT2JYykELJ1C53JGWDZfcklzJruH/fjDkrnZ1ceTmpA9F7BdDWnI4M/zmuqNrlqETVpZeGs0O2TiXDlBnpZHag6vSQnoH3nLtuKA1DrwBnyOMPCrFLWj0C2M/A3dXWuTWaFM5ddWHEw/SQYZOzjRmtIsrZRZQObSBSCS+SnshfW4qD6ky4rPUMzqpgEUuFcKCS09fTY0FDhZdabRDmFpTwFtj5Z9G92HoA3OOFwheFpiA9MCVM1BaM5cZOhAKuW33O8995UAYehaIuShZTxiLxGiOqoRKZ2id5zqLB8RdZho/BVE8idlK04dfTQWCa1qiSe6GzQcOLt4cj7uLlzr/9DD3vnSHg0GGc1SmROv6NUd9Y2eDzAg3yLjnA15KN8gjSfrQszhFi1rgwKIzlRXoBha9lTjHHu91jtsjuUihQZskQpcXbyBFkFqoKsMMpAYOCrMZWiD5pZ6hI2HTq6XiWcKIVU77TzJ2yEZBJUMCxbglzRLm+cyxwwvW+daxTwkrueUFerT09JpJQuMfFdorljDNC2SHzF+yhDmRY8HZ4TXzVyV967yVesaSDSQjpNzhsyc91HS7GfxydN7cWPee2E3CLP5RSYsZO/S2wptP9E0EiKOjftg/oH9rJ3RUlnMHKaIGiwLlPConAChozJESS9QZAThih1QmjPaoPZHmZamkCPob/O6I/vWmqCb9HYVnCSstadvLyB1aa+zEoquUn1xmdptydKUUTxVGATeU1YpyHsgEXcXNZH4iJxlKiw61B6PVFcgO9J0jHdQ2EWwoiC4dcA3H5+fvz4OS/eUkrtnGIOqqIFyE5SxhZ8fvjk7evWEJO/pwdnryajg+Zgkbn/86Gb4ZnrybnA7Hx+cEnFVJRiuG2UV1y2lgJucu342it9zl2zFD8khPCmXrKB8tTzqvQUQH4iUvShVvrLP4LKIi3HdVFNxerUGrWZCwOVcVBp5bRXb0FCViz0SaPp8+P3iSZvsvBPLn4vG+4OnzFwcv+OOn4unBvkjTqdjnzzjff3bw/Ad+gD8+OXjyDMV0/+DZU3YT/hL2ZH//y6CXDgqupsYWmP0U73kDBH8J5kbj+2kw/3vA/+MBv+sS49Nd/JxkqL2cSnSBpdKaVGEBtCmqOLK0i8wQXG6sTyCvCq57FnlG4IDa5BqJN8hvXJ/UHmdot4abt+PxWTefqIOrdGCEqGwIzWsnhUMy9Fyquwixxj1eloprHm+7RCGnUsT8bOeZeOktd9tiC88ySRS5Ouvc1zYjGi5XQhSB7oh7KOQs9zFtomOFkmREaxlUsOGHbi9uqZnNVnF2FhlmN59u95//aTzQ7R60XdL1oVHsDsYnRWddw8JtdBpgPNnfby+Q1ekQCFOpDLTxkGFAwrptoo7JHeUF4bYoAUHn+zBcteE8UEopjwguqsPPcUPDeVsJD02aUzlyYjH36QMBc3kaISf6q+6h5LdQ5CbmesTqbxEe/WYjOdnfYCpRZRFMYXOTgRsLV6ayIIyeo5YEOXL7LcS6ZNghYyG8dCUhLKzeX4wmozUP273AzSDAhs3fm/FgMBg8jx9+/pmtuOKlx/32AfPxlwNmJ3YsE8ZMOrLlLKixk05/o9zw3svee9m7etlbfWwb349qtN7ubNu1sFz8ZbfbWsUka3dsc8Dbabeu+HHHFX+V3cHYAOpw69Q3mHGpE7BYmHlwojDnVoanRyej4cvT48n4l8now8ud3q7xDz/uTKg5ZFW09gAoTjnoXIaeyi1thvs68rtKq2+z0aMGNrebZrvkllqyq6FvHRyf7qomOwiYcqkqiwngpcCwFowFqedcyez/KzHvo+V9tPybo+VrLu8aIeuld46P02b9jui4pNtg5elKmfJqWZ5sNuFDa77TAY8VxLIgIA0tKwG9VgmQFXKpHUwr63O0zRX04ai9pOBUkYs84pEa5CnBstIZcH8IO/rfvJSDwIUb0MpelLAX+vdNN7zXAG/QEazX6rEXXlYMdin59pCexFhJtQT9X0ItR4ub1U3jxO4EiXb1nVGBnS07gNGlvh0b500Du/W9G29Fvj9MdFV8J1gslfdFaJzEkDZaevSd8Kh31JXx3TFSB88m1u8EysY5O9CyLTh/e8j8ozCzofKv9ydNCrWlv/BWOm/sFRy9pDzZea7wp2XaXGk+5zIk7DHw35LH3vfov89i4j4fvs+H/64efe2Yjl6OyCetBrf4TAquyG+dOBgbA3HdZkQLPm2SR3KdyPVFIm24WmkKkdJr5w5Sk6QiuARh9FTOKhsnVSySnhul1F1yBwua45A+hJqMRhUKqTHqhrRVcwg0nEHdd6Kr+GwW5liMgSm3kGIua+UKozUKH2JnzYiZNmM1vVfkq4yNHXuLwSPTUM0DV4+zGOck4Sscv7KLcFV5IkYuoA9nCokbb69iRwsU92j/Wod+bK+GtPeUtq4lKqve74s9+26zYd1rfuuWw03CCvS5oWmU0rjg3LinA7oB201CDCfEoJ030yeVJbQ0GUSTDXh0XqPvphFbfcw4roN3cTQq+NntFKeVryzehebrZmUzcMVoSEXqqQl6bUwi0iWVo3Vx935/v39A8rXWVxvAciSK6+gXh2cnBH8CcPMmaG3MK851hQEgF0ZbLPaC4qLrDztLa7JKxBGYbZNiYZ6IXqRF7NLLJ+4kWjpaGO2qAputfI6WzxA6KQlYVNzLOTaDaCVaIkYG1DOWLBazyIjFOjngMV+sXGSqYehVnZdKFyTvyJFamc0QUvQL6hXzsozSru48s4b8hAMlP9N8mlLoXUKv/FB7y5X8M5ZROSeFJYECdw5JZlfRGFxnKOyWkbgEwhAUXREXwlTaQ8oVCZuQe3DeIi8A56gbPtaH9dqd/c1M4jtHwkX3QneO3tVsD8ir9bTJcO+7Qs9H/VEvX3DHaosLgY50OZccxIfz0wQ4pNYsHNpwgtHLzGap69HRv93dxhy9McoNXPbZ7YVXMxYJTnX0pETjUvqQF4bXz2VUaAILetEtTFGgzuhRUBTXdHCItRRSzRQKHkZMM2kp2NMdCq6UC3KGa51VMkOIFpMiJQ6LoJKskFo6T+OQNcQDHN+u5xUPw0Bmg86Lo6WkD+ClMrNWB4vFYlX45cpeqsxswHsaFz1X6R5FoRx7dfzYC9mrM2QmXHye2VD8Gr1uDRE7VuTSo/CV5QpkQTaPRbj55pV+wX83FurQAWlVlHt9eB1a74FUEJOnlF3ULJIC6/Pa2YcMKf1JQOQoPodcpCs/HQlvSLWtAmbS51XaF6YY1HoYzMwgVSYdFJw0PSDzkqItzQeU5FvNVUTKmw8nR8eT1+/PJ0fH/z0+fX92fD7qF9leuMyXOKW8aEEmOaM3epLSqIWxPgeL0oe51ThsDOQkZGBxdSLiIqRW70z2NW4CMiOqonE/h/Do0QIhM6EDizoz1iHYSmtiolEjXWh0UhxCRs4VGVPXhyyR9uhRdA8YCgyu1FUgHfZOQhMiCDjZiHxIhkFTzgsDDmkE14fEVKDVtcuhARZ6b9QMY9Msa1Ea67mO08OpCWpUkqdSkT3Srg74+iuGQbZXcM1n6IBGy81CJ1Byi1kvMwu9BF+bCkdRTellEVwinVnvJJdHDtFMQSNmDh4u8IFS0LE7KvfprepH9oqXIVgQuY9sqTuCCBUVaAv3fjqKMOukat2bDYt6Ztqr0Vj3TbgIfZN6Srlhuwv312SYvO4frqaCq4kfFrFQyVEp86/us5uEKSmQ6vb2rGHJRY7wQ3+fJUw2ZbhdPunFJ+2JtbPh4WmQqSbqBqcnr47fjY5pSz/3hQpVHiXOBddd8WKU4d1JJBiuDP+vpxnXbXfp/gcG9z8w+NofGDQNbrz0g1JxqckmArSv68rugm2p7D4lLKfy7/CCXV9TYPpg1c0NfR1/XkD13nLu5HDKlVtvonTx+/C8/qXAHtzG0me8an6sUBe+LBRrzfAIO7ygXkmOPCNTvbiudwwFvTPo7NpoxBKVZU179n40Zjc3/wOaIngT
-sidebar_class_name: "post api-method"
-info_path: docs/data/apis/horizon/api-reference/horizon
-custom_edit_url: null
----
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Submit a Transaction Asynchronously"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/transactions_async"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint submits transactions to the Stellar network asynchronously. It is designed to allow users to submit transactions without blocking them while waiting for a response from Horizon. At the same time, it also provides clear response status codes from stellar-core to help understand the status of the submitted transaction. You can then use Horizon's [GET transaction endpoint](https://developers.stellar.org/docs/data/apis/horizon/api-reference/resources/retrieve-a-transaction) to wait for the transaction to be included in a ledger and ingested by Horizon.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"query","name":"tx","schema":{"type":"string","description":"The base64-encoded XDR of the transaction."},"required":true}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Transaction has been received by core and is in pending status.","content":{"application/json":{"schema":{"type":"object","properties":{"error_result_xdr":{"type":"string","nullable":true,"description":"TransactionResult XDR string which is present only if the submission status from core is an ERROR."},"tx_status":{"type":"string","enum":["ERROR","PENDING","DUPLICATE","TRY_AGAIN_LATER"],"description":"Status of the transaction submission."},"hash":{"type":"string","description":"Hash of the transaction."}},"title":"AsyncTransactionSubmissionResponse"},"examples":{"TransactionPending":{"summary":"Transaction Pending","value":{"tx_status":"PENDING","hash":"6cbb7f714bd08cea7c30cab7818a35c510cbbfc0a6aa06172a1e94146ecf0165"}}}}}},"400":{"description":"Transaction is malformed; ERROR status from core.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","properties":{"error_result_xdr":{"type":"string","nullable":true,"description":"TransactionResult XDR string which is present only if the submission status from core is an ERROR."},"tx_status":{"type":"string","enum":["ERROR","PENDING","DUPLICATE","TRY_AGAIN_LATER"],"description":"Status of the transaction submission."},"hash":{"type":"string","description":"Hash of the transaction."}},"title":"AsyncTransactionSubmissionResponse"},{"type":"object","properties":{"type":{"type":"string","description":"Identifies the problem type."},"title":{"type":"string","description":"A short, human-readable summary of the problem type."},"status":{"type":"integer","description":"The HTTP status code for this occurrence of the problem."},"detail":{"type":"string","description":"A human-readable explanation specific to this occurrence of the problem."},"extras":{"type":"object","additionalProperties":true,"description":"Additional details that might help the client understand the error(s) that occurred."}},"title":"Problem"}]},"examples":{"TransactionMalformed":{"summary":"Transaction Malformed","value":{"type":"transaction_malformed","title":"Transaction Malformed","status":400,"detail":"Horizon could not decode the transaction envelope in this request. A transaction should be an XDR TransactionEnvelope struct encoded using base64. The envelope read from this request is echoed in the `extras.envelope_xdr` field of this response for your convenience.","extras":{"envelope_xdr":""}}},"TransactionError":{"summary":"ERROR Status from core","value":{"error_result_xdr":"AAAAAAAAAGT////7AAAAAA==","tx_status":"ERROR","hash":"6cbb7f714bd08cea7c30cab7818a35c510cbbfc0a6aa06172a1e94146ecf0165"}}}}}},"403":{"description":"Transaction submission has been disabled for Horizon.","content":{"application/json":{"schema":{"type":"object","properties":{"type":{"type":"string","description":"Identifies the problem type."},"title":{"type":"string","description":"A short, human-readable summary of the problem type."},"status":{"type":"integer","description":"The HTTP status code for this occurrence of the problem."},"detail":{"type":"string","description":"A human-readable explanation specific to this occurrence of the problem."},"extras":{"type":"object","additionalProperties":true,"description":"Additional details that might help the client understand the error(s) that occurred."}},"title":"Problem"},"examples":{"TransactionSubmissionDisabled":{"summary":"Transaction Submission Disabled","value":{"type":"transaction_submission_disabled","title":"Transaction Submission Disabled","status":403,"detail":"Transaction submission has been disabled for Horizon. To enable it again, remove env variable DISABLE_TX_SUB.","extras":{"envelope_xdr":""}}}}}}},"409":{"description":"Transaction is a duplicate of a previously submitted transaction.","content":{"application/json":{"schema":{"type":"object","properties":{"error_result_xdr":{"type":"string","nullable":true,"description":"TransactionResult XDR string which is present only if the submission status from core is an ERROR."},"tx_status":{"type":"string","enum":["ERROR","PENDING","DUPLICATE","TRY_AGAIN_LATER"],"description":"Status of the transaction submission."},"hash":{"type":"string","description":"Hash of the transaction."}},"title":"AsyncTransactionSubmissionResponse"},"examples":{"TransactionDuplicate":{"summary":"Transaction Duplicate","value":{"tx_status":"DUPLICATE","hash":"6cbb7f714bd08cea7c30cab7818a35c510cbbfc0a6aa06172a1e94146ecf0165"}}}}}},"500":{"description":"Transaction submission failure, exception or invalid status from core.","content":{"application/json":{"schema":{"type":"object","properties":{"type":{"type":"string","description":"Identifies the problem type."},"title":{"type":"string","description":"A short, human-readable summary of the problem type."},"status":{"type":"integer","description":"The HTTP status code for this occurrence of the problem."},"detail":{"type":"string","description":"A human-readable explanation specific to this occurrence of the problem."},"extras":{"type":"object","additionalProperties":true,"description":"Additional details that might help the client understand the error(s) that occurred."}},"title":"Problem"},"examples":{"TransactionFailed":{"summary":"Transaction Submission Failed","value":{"type":"transaction_submission_failed","title":"Transaction Submission Failed","status":500,"detail":"Could not submit transaction to stellar-core. The `extras.error` field on this response contains further details. Descriptions of each code can be found at: https://developers.stellar.org/api/errors/http-status-codes/horizon-specific/transaction-submission-async/transaction_submission_failed","extras":{"envelope_xdr":"","error":"Error details here"}}},"TransactionException":{"summary":"Transaction Submission Exception","value":{"type":"transaction_submission_exception","title":"Transaction Submission Exception","status":500,"detail":"Received exception from stellar-core. The `extras.error` field on this response contains further details. Descriptions of each code can be found at: https://developers.stellar.org/api/errors/http-status-codes/horizon-specific/transaction-submission-async/transaction_submission_exception","extras":{"envelope_xdr":"","error":"Exception details here"}}},"TransactionInvalidStatus":{"summary":"Transaction Submission Invalid Status","value":{"type":"transaction_submission_invalid_status","title":"Transaction Submission Invalid Status","status":500,"detail":"Received invalid status from stellar-core. The `extras.error` field on this response contains further details.  Descriptions of each code can be found at: https://developers.stellar.org/api/errors/http-status-codes/horizon-specific/transaction-submission-async/transaction_submission_invalid_status","extras":{"envelope_xdr":"","error":"Error details here"}}}}}}},"503":{"description":"History DB is stale; core is unavailable for transaction submission.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","properties":{"error_result_xdr":{"type":"string","nullable":true,"description":"TransactionResult XDR string which is present only if the submission status from core is an ERROR."},"tx_status":{"type":"string","enum":["ERROR","PENDING","DUPLICATE","TRY_AGAIN_LATER"],"description":"Status of the transaction submission."},"hash":{"type":"string","description":"Hash of the transaction."}},"title":"AsyncTransactionSubmissionResponse"},{"type":"object","properties":{"type":{"type":"string","description":"Identifies the problem type."},"title":{"type":"string","description":"A short, human-readable summary of the problem type."},"status":{"type":"integer","description":"The HTTP status code for this occurrence of the problem."},"detail":{"type":"string","description":"A human-readable explanation specific to this occurrence of the problem."},"extras":{"type":"object","additionalProperties":true,"description":"Additional details that might help the client understand the error(s) that occurred."}},"title":"Problem"}]},"examples":{"HistoryDBStale":{"summary":"Historical DB Is Too Stale","value":{"type":"stale_history","title":"Historical DB Is Too Stale","status":503,"detail":"This horizon instance is configured to reject client requests when it can determine that the history database is lagging too far behind the connected instance of Stellar-Core or read replica. It's also possible that Stellar-Core is out of sync. Please try again later.","extras":{"envelope_xdr":""}}},"TransactionTryAgainLater":{"summary":"TRY_AGAIN_LATER Status from core","value":{"tx_status":"TRY_AGAIN_LATER","hash":"6cbb7f714bd08cea7c30cab7818a35c510cbbfc0a6aa06172a1e94146ecf0165"}}}}}}}}
->
-  
-</StatusCodes>
-
-
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/providers.mdx
deleted file mode 100644
index f088dea605..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/providers.mdx
+++ /dev/null
@@ -1,31 +0,0 @@
----
-sidebar_position: 60
-title: Proveedores
----
-
-:::info
-
-El 1 de agosto de 2024, el Horizon alojado por SDF con acceso público tuvo sus datos históricos truncados a un año. Esa actualización optimizó el rendimiento del Horizon con acceso público y garantizó una experiencia fluida para todos los usuarios. Considera los proveedores externos del ecosistema de Horizon, que pueden ofrecer un período de retención histórica más largo además de otras funciones.
-
-:::
-
-Varios proveedores de infraestructura han puesto a disposición servicios de Horizon y ofrecen planes que van desde gratuitos hasta instancias dedicadas. Estos proveedores pueden usarse para desarrollo, pruebas y producción.
-
-Estos proveedores permiten el acceso a las redes Futurenet, Testnet y Mainnet.
-
-| Proveedor                                                  | Futurenet | Testnet | Mainnet | Historial completo |
-| ---------------------------------------------------------- | --------- | ------- | ------- | ------------------ |
-| [Blockdaemon\*](https://www.blockdaemon.com/apply/soroban) | ❌         | ✅       | ✅       | ✅                  |
-| [Validation Cloud\*](https://app.validationcloud.io/)      | ❌         | ✅       | ✅       | ✅                  |
-| [QuickNode](https://www.quicknode.com/docs/stellar)        | ❌         | ✅       | ✅       | ❌                  |
-| [Ankr](https://www.ankr.com/rpc/advanced-api/)             | ❌         | ✅       | ✅       | ❌                  |
-| [Obsrvr](https://www.withObsrvr.com/)                      | ❌         | ✅       | ✅       | ❌                  |
-| [Nodies](https://nodies.org)                               | ❌         | ✅       | ✅       | ❌                  |
-
-\*Blockdaemon y Validation Cloud proporcionan datos históricos completos para Horizon.
-
-### APIs de acceso público
-
-| Proveedor                   | Red     | URL                                          |
-| --------------------------- | ------- | -------------------------------------------- |
-| [LOBSTR](https://lobstr.co) | Mainnet | Horizon: `https://horizon.stellar.lobstr.co` |
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc.mdx
deleted file mode 100644
index ff8ebad8e6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc.mdx
+++ /dev/null
@@ -1,134 +0,0 @@
----
-title: Migrar de Horizon a RPC
-sidebar_position: 100
-hide_table_of_contents: true
----
-
-Las aplicaciones que usan la [API REST-like de Horizon] necesitarán actualizarse para usar la [API JSON-RPC RPC] al migrar de [Horizon] a [RPC]. Esta guía ofrece una visión general de las principales diferencias entre las dos APIs y cómo migrar tu aplicación.
-
-## Formato de solicitud / respuesta
-
-La API tipo REST de Horizon utiliza métodos HTTP y códigos de estado para comunicarse con los clientes. Las respuestas están en formato JSON HAL. Consulta [El formato de respuesta de Horizon].
-
-La API JSON-RPC de RPC utiliza JSON-RPC 2.0 para comunicarse con los clientes. Las solicitudes a la API son objetos JSON que contienen una o más invocaciones de métodos. Las respuestas también son objetos JSON que contienen un resultado para cada invocación en la solicitud. Consulta [JSON-RPC].
-
-Ambos formatos utilizan JSON para la estructura general, son relativamente simples y no requieren código cliente especial, aunque hay [SDKs] cliente disponibles. Algunos valores que contienen están codificados en XDR y pueden decodificarse usando los [SDKs] de Stellar.
-
-## Mapeo de endpoint
-
-Las aplicaciones que utilizan los siguientes endpoints de Horizon normalmente pueden migrar directamente a RPC usando los métodos referenciados.
-
-Los endpoints sin asignaciones no tienen un reemplazo directo en la API RPC. Para crear una funcionalidad similar en una aplicación, considera asociarte con un indexador o usar la información a continuación para crear tu propia representación indexada de los endpoints de Horizon. Considera usar otros productos [Data] para casos de uso analíticos.
-
-| Endpoint de Horizon                           | Método(s) RPC correspondiente(s)                                                      | Equivalente en Indexer                                                                                                                                                                                                                                                | Recursos de análisis                                                                                         |
-| --------------------------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
-| [`GET /`]                                     | [`getLatestLedger`] [`getVersionInfo`] [`getHealth`] [`getNetwork`]                   | No aplicable                                                                                                                                                                                                                                                          | [Guía para analistas](../analytics/hubble/analyst-guide/README.mdx)                                          |
-| [`GET /ledgers`]                              | [`getLedgers`]                                                                        | Crea un [`getLedgers`] con historial completo, usando [Galexie](../indexers/build-your-own/galexie/README.mdx), para crear una vista histórica del ledger.                                                                                                            | [Ledgers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#ledgers)                       |
-| [`GET /ledgers/{seq}`]                        | [`getLedgers`] (con filtro para secuencia)                                            | Usa una vista [`getLedgers`] con historial completo, filtrada por secuencia del ledger                                                                                                                                                                                | [Ledgers](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#ledgers)                       |
-| [`GET /ledgers/{seq}/transactions`]           | [`getTransactions`] (con filtro por secuencia del ledger)                             | Usa [`getTransactions`] con filtro por secuencia del ledger para obtener las transacciones de un ledger específico                                                                                                                                                    | [Transacciones](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#transactions)            |
-| [`GET /ledgers/{seq}/operations`]             | [`getTransactions`]                                                                   | Usa [`getTransactions`] para el ledger dado, luego analiza el XDR de la transacción para operaciones individuales.                                                                                                                                                    | [Operaciones](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#operations)                |
-| [`GET /ledgers/{seq}/payments`]               | [`getEvents`] [`getTransactions`] ⚠️                                                  | Usa [`getEvents`] (específicamente eventos CAP-67 cuando estén disponibles) y analiza el meta XDR de [`getTransactions`] para identificar operaciones parecidas a pagos.                                                                                              | [Pagos](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#payments)                        |
-| [`GET /ledgers/{seq}/effects`]                | [`getEvents`] [`getTransactions`] ⚠️                                                  | Usa [`getEvents`] (cuando se amplíe para cubrir todos los efectos con CAP-67) y analiza el meta XDR de [`getTransactions`] para obtener datos relevantes.                                                                                                             | [Efectos](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#effects)                       |
-| [`POST /transactions`]                        | [`sendTransaction`]                                                                   | No aplicable                                                                                                                                                                                                                                                          | No aplicable                                                                                                 |
-| [`POST /transactions_async`]                  | [`sendTransaction`]                                                                   | No aplicable                                                                                                                                                                                                                                                          | No aplicable                                                                                                 |
-| [`GET /transactions`]                         | [`getTransactions`]                                                                   | Usa [`getTransactions`] para crear una lista histórica de transacciones                                                                                                                                                                                               | [Transacciones](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#transactions)            |
-| [`GET /transactions/{hash}`]                  | [`getTransaction`]                                                                    | Usa getTransaction para recuperar una transacción específica por su hash                                                                                                                                                                                              | [Transacciones](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#transactions)            |
-| [`GET /transactions/{hash}/operations`]       | [`getTransaction`]                                                                    | Filtra [`getTransaction`] por hash y luego analiza su XDR para obtener operaciones                                                                                                                                                                                    | [Operaciones](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#operations)                |
-| [`GET /transactions/{hash}/payments`]         | No existe equivalente directo en RPC; usa [`getEvents`] o analiza [`getTransactions`] | Filtra [`getTransaction`] por hash y analiza sus eventos y tipos de operación para identificar pagos.                                                                                                                                                                 | [Pagos](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#payments)                        |
-| [`GET /transactions/{hash}/effects`]          | No existe equivalente directo en RPC; usa [`getEvents`] o analiza [`getTransactions`] | Filtra [`getTransaction`] por hash y analiza sus eventos y metadata para obtener datos relevantes.                                                                                                                                                                    | [Efectos](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#effects)                       |
-| [`GET /operations`]                           | [`getTransactions`]                                                                   | Ingiere todos los ledgers/transacciones históricas y crea y crea una vista de operaciones para filtrar.                                                                                                                                                               | [Operaciones](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#operations)                |
-| [`GET /operations/{id}`]                      | No existe equivalente directo en RPC                                                  | Almacena el ID de operación de Horizon y mapea de vuelta a la secuencia del ledger y al índice de la transacción para recuperar la transacción relevante vía [`getTransactions`].                                                                                     | [Operaciones](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#operations)                |
-| [`GET /operations/{id}/effects`]              | No existe equivalente directo en RPC                                                  | Recupera la operación por ID (como arriba) y luego analiza su transacción asociada y eventos para obtener efectos.                                                                                                                                                    | [Efectos](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#effects)                       |
-| [`GET /fee_stats`]                            | [`getFeeStats`] [`simulateTransaction`]                                               | Datos indexados no recomendados.                                                                                                                                                                                                                                      | [Estadísticas de tarifas](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#fee-stats)     |
-| [`GET /accounts`]                             | No existe equivalente directo en RPC                                                  | Ingiere todo el historial de ledger vía [`getLedgers`] para crear y mantener una lista completa de cuentas.                                                                                                                                                           | [Cuentas](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#accounts)                      |
-| [`GET /accounts/{address}`]                   | [`getLedgerEntries`]                                                                  | Usa [`getLedgerEntries`] para una dirección específica de cuenta. Nota: RPC no proporcionará información de líneas de confianza asociadas con la cuenta directamente, como lo hace Horizon. Necesitarás derivar esta información a partir de las entradas del ledger. | [Cuentas](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#accounts)                      |
-| [`GET /claimable_balances`]                   | No existe equivalente directo en RPC                                                  | Ingiere todo el historial del ledger vía [`getLedgers`] para crear y mantener una lista completa de saldos reclamables.                                                                                                                                               | [Saldos reclamables](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#claimable-balances) |
-| [`GET /claimable_balances/{id}`]              | [`getLedgerEntries`]                                                                  | Usa [`getLedgerEntries`] para recuperar un saldo reclamable específico por ID.                                                                                                                                                                                        | [Saldos reclamables](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#claimable-balances) |
-| [`GET /claimable_balances/{id}/transactions`] | No existe equivalente directo en RPC                                                  | Rastrea las transacciones que interactúan con un saldo reclamable específico a partir de sus datos históricos de ledger.                                                                                                                                              | [Saldos reclamables](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#claimable-balances) |
-| [`GET /claimable_balances/{id}/operations`]   | No existe equivalente directo en RPC                                                  | Rastrea las operaciones relacionadas con un saldo reclamable específico a partir de los datos históricos del ledger.                                                                                                                                                  | [Saldos reclamables](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#claimable-balances) |
-| [`GET /liquidity_pools`]                      | No existe equivalente directo en RPC                                                  | Ingiere todo el historial del ledger vía [`getLedgers`] para crear y mantener una lista completa de fondos de liquidez.                                                                                                                                               | [Fondos de Liquidez](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools)    |
-| [`GET /liquidity_pools/{id}`]                 | [`getLedgerEntries`]                                                                  | Usa [`getLedgerEntries`] para recuperar un fondo de liquidez específico por ID.                                                                                                                                                                                       | [Fondos de Liquidez](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools)    |
-| [`GET /liquidity_pools/{id}/transactions`]    | No existe equivalente directo en RPC                                                  | Rastrea las transacciones que interactúan con un fondo de liquidez específico a partir de sus datos históricos de ledger.                                                                                                                                             | [Fondos de Liquidez](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools)    |
-| [`GET /liquidity_pools/{id}/operations`]      | No existe equivalente directo en RPC                                                  | Rastrea las operaciones relacionadas con un fondo de liquidez específico a partir de los datos históricos del ledger.                                                                                                                                                 | [Fondos de Liquidez](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools)    |
-| [`GET /liquidity_pools/{id}/effects`]         | No existe equivalente directo en RPC                                                  | Rastrea efectos relacionados con un fondo de liquidez específico a partir de los datos históricos del ledger.                                                                                                                                                         | [Fondos de Liquidez](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools)    |
-| [`GET /liquidity_pools/{id}/trades`]          | No existe equivalente directo en RPC                                                  | Infiera operaciones relacionadas con un fondo de liquidez específico a partir de los datos históricos del ledger (por ejemplo, de [`getEvents`] y metadatos de [`getTransactions`]).                                                                                  | [Fondos de Liquidez](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#liquidity-pools)    |
-| [`GET /offers`]                               | No existe equivalente directo en RPC                                                  | Ingiere todo el historial del ledger vía [`getLedgers`] para crear y mantener una lista completa de ofertas.                                                                                                                                                          | [Ofertas](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#offers)                        |
-| [`GET /offers/{id}`]                          | [`getLedgerEntries`]                                                                  | Usa [`getLedgerEntries`] para recuperar una oferta específica por ID.                                                                                                                                                                                                 | [Ofertas](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#offers)                        |
-| [`GET /offers/{id}/trades`]                   | No existe equivalente directo en RPC                                                  | Infiera operaciones relacionadas con una oferta específica a partir de los datos históricos del ledger (por ejemplo, de [`getEvents`] y metadatos de [`getTransactions`]).                                                                                            | [Ofertas](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#offers)                        |
-| [`GET /payments`]                             | [`getEvents`] [`getTransactions`] ⚠️                                                  | Usa [`getEvents`] (eventos CAP-67) y procesa metadatos de [`getTransactions`] para operaciones parecidas a pagos a lo largo de toda la historia.                                                                                                                      | [Pagos](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#payments)                        |
-| [`GET /effects`]                              | [`getEvents`] [`getTransactions`] ⚠️                                                  | Usa [`getEvents`] (cuando se amplíe) y procesa metadatos de [`getTransactions`] para derivar efectos a lo largo de toda la historia.                                                                                                                                  | [Efectos](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#effects)                       |
-| [`GET /trades`]                               | [`getEvents`] [`getTransactions`] ⚠️                                                  | Infiera operaciones a partir de metadatos de [`getEvents`] y [`getTransactions`] a lo largo de toda la historia, ya que no existe un "evento de operación" directo en RPC.                                                                                            | [Operaciones](../analytics/hubble/analyst-guide/queries-for-horizon-like-data.mdx#trades)                    |
-
-:::tip
-
-El método [`getTransactions`] puede usarse para recuperar eventos agrupados por transacción. Los eventos están contenidos en el meta XDR de la transacción (campo `resultMetaXdr`).
-
-:::
-
-:::warning
-
-El método [`getEvents`] no es un reemplazo directo de los endpoints de Horizon.
-
-El método devuelve un flujo de eventos que actualmente solo incluye eventos de contratos en el protocolo actual. En un futuro cercano, como resultado de [CAP-67], este método se ampliará para incluir eventos de operaciones no relacionadas con contratos.
-
-Mientras tanto, el método [`getTransactions`] puede usarse para recuperar el meta XDR de transacciones que contienen operaciones no relacionadas con contratos para determinar qué movimientos de valor han ocurrido. El meta XDR también contiene eventos de contratos.
-
-:::
-
-[CAP-67]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md
-[Horizon]: ./horizon/README.mdx
-[RPC]: ./rpc/README.mdx
-[REST-like API de Horizon]: ./horizon/api-reference/README.mdx
-[Formato de respuesta de Horizon]: ./horizon/api-reference/structure/response-format.mdx
-[API JSON-RPC RPC]: ./rpc/api-reference/README.mdx
-[JSON-RPC]: ./rpc/api-reference/structure/json-rpc.mdx
-[Data]: ../analytics/README.mdx
-[SDKs]: ../../tools/sdks/README.mdx
-[`GET /`]: ./horizon/api-reference/README.mdx
-[`GET /ledgers`]: ./horizon/api-reference/list-all-ledgers.api.mdx
-[`GET /ledgers/{seq}`]: ./horizon/api-reference/retrieve-a-ledger.api.mdx
-[`GET /ledgers/{seq}/transactions`]: ./horizon/api-reference/retrieve-a-ledgers-transactions.api.mdx
-[`GET /ledgers/{seq}/operations`]: ./horizon/api-reference/retrieve-a-ledgers-operations.api.mdx
-[`GET /ledgers/{seq}/payments`]: ./horizon/api-reference/retrieve-a-ledgers-payments.api.mdx
-[`GET /ledgers/{seq}/effects`]: ./horizon/api-reference/retrieve-a-ledgers-effects.api.mdx
-[`POST /transactions`]: ./horizon/api-reference/submit-a-transaction.api.mdx
-[`POST /transactions_async`]: ./horizon/api-reference/submit-async-transaction.api.mdx
-[`GET /transactions`]: ./horizon/api-reference/list-all-transactions.api.mdx
-[`GET /transactions/{hash}`]: ./horizon/api-reference/retrieve-a-transaction.api.mdx
-[`GET /transactions/{hash}/operations`]: ./horizon/api-reference/retrieve-a-transactions-operations.api.mdx
-[`GET /transactions/{hash}/payments`]: ./horizon/api-reference/retrieve-a-transactions-payments.api.mdx
-[`GET /transactions/{hash}/effects`]: ./horizon/api-reference/retrieve-a-transactions-effects.api.mdx
-[`GET /operations`]: ./horizon/api-reference/list-all-operations.api.mdx
-[`GET /operations/{id}`]: ./horizon/api-reference/retrieve-an-operation.api.mdx
-[`GET /operations/{id}/effects`]: ./horizon/api-reference/retrieve-an-operations-effects.api.mdx
-[`GET /fee_stats`]: ./horizon/api-reference/README.mdx
-[`GET /accounts`]: ./horizon/api-reference/list-all-accounts.api.mdx
-[`GET /accounts/{address}`]: ./horizon/api-reference/retrieve-an-account.api.mdx
-[`GET /claimable_balances`]: ./horizon/api-reference/list-all-claimable-balances.api.mdx
-[`GET /claimable_balances/{id}`]: ./horizon/api-reference/retrieve-a-claimable-balance.api.mdx
-[`GET /claimable_balances/{id}/transactions`]: ./horizon/api-reference/cb-retrieve-related-transactions.api.mdx
-[`GET /claimable_balances/{id}/operations`]: ./horizon/api-reference/cb-retrieve-related-operations.api.mdx
-[`GET /liquidity_pools`]: ./horizon/api-reference/list-liquidity-pools.api.mdx
-[`GET /liquidity_pools/{id}`]: ./horizon/api-reference/retrieve-a-liquidity-pool.api.mdx
-[`GET /liquidity_pools/{id}/transactions`]: ./horizon/api-reference/lp-retrieve-related-transactions.api.mdx
-[`GET /liquidity_pools/{id}/operations`]: ./horizon/api-reference/lp-retrieve-related-operations.api.mdx
-[`GET /liquidity_pools/{id}/effects`]: ./horizon/api-reference/retrieve-related-effects.api.mdx
-[`GET /liquidity_pools/{id}/trades`]: ./horizon/api-reference/retrieve-related-trades.api.mdx
-[`GET /offers`]: ./horizon/api-reference/get-all-offers.api.mdx
-[`GET /offers/{id}`]: ./horizon/api-reference/get-offer-by-offer-id.api.mdx
-[`GET /offers/{id}/trades`]: ./horizon/api-reference/get-trades-by-offer-id.api.mdx
-[`GET /payments`]: ./horizon/api-reference/list-all-payments.api.mdx
-[`GET /effects`]: ./horizon/api-reference/list-all-effects.api.mdx
-[`GET /trades`]: ./horizon/api-reference/get-all-trades.api.mdx
-[`getLatestLedger`]: ./rpc/api-reference/methods/getLatestLedger.mdx
-[`getVersionInfo`]: ./rpc/api-reference/methods/getVersionInfo.mdx
-[`getHealth`]: ./rpc/api-reference/methods/getHealth.mdx
-[`getNetwork`]: ./rpc/api-reference/methods/getNetwork.mdx
-[`getLedgers`]: ./rpc/api-reference/methods/getLedgers.mdx
-[`getTransactions`]: ./rpc/api-reference/methods/getTransactions.mdx
-[`getTransaction`]: ./rpc/api-reference/methods/getTransaction.mdx
-[`getEvents`]: ./rpc/api-reference/methods/getEvents.mdx
-[`sendTransaction`]: ./rpc/api-reference/methods/sendTransaction.mdx
-[`getFeeStats`]: ./rpc/api-reference/methods/getFeeStats.mdx
-[`simulateTransaction`]: ./rpc/api-reference/methods/simulateTransaction.mdx
-[`getLedgerEntries`]: ./rpc/api-reference/methods/getLedgerEntries.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc/migrate-from-horizon-to-rpc.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc/migrate-from-horizon-to-rpc.mdx
deleted file mode 100644
index 5548ea4f9a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/migrate-from-horizon-to-rpc/migrate-from-horizon-to-rpc.mdx
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: Migrar de Horizon a RPC
-sidebar_position: 100
----
-
-Las aplicaciones que utilizan la [API REST-like de Horizon] necesitarán ser actualizadas para usar la [API JSON-RPC de RPC] al migrar de [Horizon] a [RPC]. Esta guía proporciona una visión general de las principales diferencias entre las dos APIs y cómo migrar tu aplicación.
-
-## Formato de Solicitud / Respuesta
-
-La API REST-like de Horizon utiliza métodos HTTP y códigos de estado para comunicarse con los clientes. Las respuestas son JSON en el formato HAL. Consulta el [Formato de Respuesta de Horizon].
-
-La API JSON-RPC de RPC utiliza JSON-RPC 2.0 para comunicarse con los clientes. Las solicitudes a la API son objetos JSON que contienen una o más invocaciones de métodos. Las respuestas también son objetos JSON que contienen un resultado para cada invocación en la solicitud. Consulta [JSON-RPC].
-
-Ambos formatos utilizan JSON para la estructura general, que es relativamente simple y no requiere ningún código especial del cliente, aunque hay [SDKs] de cliente disponibles. Algunos valores contenidos dentro están codificados en XDR y se pueden decodificar utilizando [SDKs] de Stellar.
-
-## Mapeo de Puntos Finales
-
-Las aplicaciones que utilizan los siguientes puntos finales de Horizon pueden típicamente migrar directamente a RPC usando los métodos referenciados.
-
-Los puntos finales sin mapeos no tienen un reemplazo directo en la API de RPC. Para crear una funcionalidad similar en una aplicación, echa un vistazo a otros productos de [Data].
-
-| Punto Final de Horizon                        | Método RPC                                                          |
-| --------------------------------------------- | ------------------------------------------------------------------- |
-| [`GET /`]                                     | [`getLatestLedger`] [`getVersionInfo`] [`getHealth`] [`getNetwork`] |
-| [`GET /ledgers`]                              | [`getLedgers`]                                                      |
-| [`GET /ledgers/{seq}`]                        | [`getLedgers`]                                                      |
-| [`GET /ledgers/{seq}/transactions`]           | [`getTransactions`]                                                 |
-| [`GET /ledgers/{seq}/operations`]             | [`getTransactions`]                                                 |
-| [`GET /ledgers/{seq}/payments`]               | [`getEvents`] [`getTransactions`] ⚠️                                |
-| [`GET /ledgers/{seq}/effects`]                | [`getEvents`] [`getTransactions`] ⚠️                                |
-| [`POST /transactions`]                        | [`sendTransaction`]                                                 |
-| [`POST /transactions_async`]                  | [`sendTransaction`]                                                 |
-| [`GET /transactions`]                         | [`getTransactions`]                                                 |
-| [`GET /transactions/{hash}`]                  | [`getTransaction`]                                                  |
-| [`GET /transactions/{hash}/operations`]       | [`getTransaction`]                                                  |
-| [`GET /transactions/{hash}/payments`]         | -                                                                   |
-| [`GET /transactions/{hash}/effects`]          | -                                                                   |
-| [`GET /operations`]                           | [`getTransactions`]                                                 |
-| [`GET /operations/{id}`]                      | -                                                                   |
-| [`GET /operations/{id}/effects`]              | -                                                                   |
-| [`GET /fee_stats`]                            | [`getFeeStats`] [`simulateTransaction`]                             |
-| [`GET /accounts`]                             | -                                                                   |
-| [`GET /accounts/{address}`]                   | [`getLedgerEntries`]                                                |
-| [`GET /claimable_balances`]                   | -                                                                   |
-| [`GET /claimable_balances/{id}`]              | [`getLedgerEntries`]                                                |
-| [`GET /claimable_balances/{id}/transactions`] | -                                                                   |
-| [`GET /claimable_balances/{id}/operations`]   | -                                                                   |
-| [`GET /liquidity_pools`]                      | -                                                                   |
-| [`GET /liquidity_pools/{id}`]                 | [`getLedgerEntries`]                                                |
-| [`GET /liquidity_pools/{id}/transactions`]    | -                                                                   |
-| [`GET /liquidity_pools/{id}/operations`]      | -                                                                   |
-| [`GET /liquidity_pools/{id}/effects`]         | -                                                                   |
-| [`GET /liquidity_pools/{id}/trades`]          | -                                                                   |
-| [`GET /offers`]                               | -                                                                   |
-| [`GET /offers/{id}`]                          | [`getLedgerEntries`]                                                |
-| [`GET /offers/{id}/trades`]                   | -                                                                   |
-| [`GET /payments`]                             | [`getEvents`] [`getTransactions`] ⚠️                                |
-| [`GET /effects`]                              | [`getEvents`] [`getTransactions`] ⚠️                                |
-| [`GET /trades`]                               | [`getEvents`] [`getTransactions`] ⚠️                                |
-
-:::tip
-
-El método [`getTransactions`] puede utilizarse para recuperar eventos agrupados por transacción. Los eventos están contenidos en el meta XDR de la transacción (campo `resultMetaXdr`).
-
-:::
-
-:::warning
-
-El método [`getEvents`] no es un reemplazo directo para los puntos finales de Horizon.
-
-El método devuelve un flujo de eventos que en el protocolo actual solo incluye eventos de contratos. En un futuro cercano como resultado de [CAP-67], este método se ampliará para incluir eventos de operaciones no contractuales.
-
-Mientras tanto, el método [`getTransactions`] puede utilizarse para recuperar el meta XDR de las transacciones que contienen operaciones no contractuales para determinar qué movimientos de valor han ocurrido. El meta XDR también contiene eventos de contratos.
-
-:::
-
-[CAP-67]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md
-[Horizon]: ./horizon
-[RPC]: ./rpc
-[API REST-like de Horizon]: ./horizon/api-reference
-[Formato de Respuesta de Horizon]: ./horizon/api-reference/structure/response-format
-[API JSON-RPC de RPC]: ./rpc/api-reference
-[JSON-RPC]: ./rpc/api-reference/structure/json-rpc
-[Data]: ../analytics
-[SDKs]: ../../tools/sdks
-[`GET /`]: ./horizon/api-reference
-[`GET /ledgers`]: ./horizon/api-reference/list-all-ledgers
-[`GET /ledgers/{seq}`]: ./horizon/api-reference/retrieve-a-ledger
-[`GET /ledgers/{seq}/transactions`]: ./horizon/api-reference/retrieve-a-ledgers-transactions
-[`GET /ledgers/{seq}/operations`]: ./horizon/api-reference/retrieve-a-ledgers-operations
-[`GET /ledgers/{seq}/payments`]: ./horizon/api-reference/retrieve-a-ledgers-payments
-[`GET /ledgers/{seq}/effects`]: ./horizon/api-reference/retrieve-a-ledgers-effects
-[`POST /transactions`]: ./horizon/api-reference/submit-a-transaction
-[`POST /transactions_async`]: ./horizon/api-reference/submit-async-transaction
-[`GET /transactions`]: ./horizon/api-reference/list-all-transactions
-[`GET /transactions/{hash}`]: ./horizon/api-reference/retrieve-a-transaction
-[`GET /transactions/{hash}/operations`]: ./horizon/api-reference/retrieve-a-transactions-operations
-[`GET /transactions/{hash}/payments`]: ./horizon/api-reference/retrieve-a-transactions-payments
-[`GET /transactions/{hash}/effects`]: ./horizon/api-reference/retrieve-a-transactions-effects
-[`GET /operations`]: ./horizon/api-reference/list-all-operations
-[`GET /operations/{id}`]: ./horizon/api-reference/retrieve-an-operation
-[`GET /operations/{id}/effects`]: ./horizon/api-reference/retrieve-an-operations-effects
-[`GET /fee_stats`]: ./horizon/api-reference
-[`GET /accounts`]: ./horizon/api-reference/list-all-accounts
-[`GET /accounts/{address}`]: ./horizon/api-reference/retrieve-an-account
-[`GET /claimable_balances`]: ./horizon/api-reference/list-all-claimable-balances
-[`GET /claimable_balances/{id}`]: ./horizon/api-reference/retrieve-a-claimable-balance
-[`GET /claimable_balances/{id}/transactions`]: ./horizon/api-reference/cb-retrieve-related-transactions
-[`GET /claimable_balances/{id}/operations`]: ./horizon/api-reference/cb-retrieve-related-operations
-[`GET /liquidity_pools`]: ./horizon/api-reference/list-liquidity-pools
-[`GET /liquidity_pools/{id}`]: ./horizon/api-reference/retrieve-a-liquidity-pool
-[`GET /liquidity_pools/{id}/transactions`]: ./horizon/api-reference/lp-retrieve-related-transactions
-[`GET /liquidity_pools/{id}/operations`]: ./horizon/api-reference/lp-retrieve-related-operations
-[`GET /liquidity_pools/{id}/effects`]: ./horizon/api-reference/retrieve-related-effects
-[`GET /liquidity_pools/{id}/trades`]: ./horizon/api-reference/retrieve-related-trades
-[`GET /offers`]: ./horizon/api-reference/get-all-offers
-[`GET /offers/{id}`]: ./horizon/api-reference/get-offer-by-offer-id
-[`GET /offers/{id}/trades`]: ./horizon/api-reference/get-trades-by-offer-id
-[`GET /payments`]: ./horizon/api-reference/list-all-payments
-[`GET /effects`]: ./horizon/api-reference/list-all-effects
-[`GET /trades`]: ./horizon/api-reference/get-all-trades
-[`getLatestLedger`]: ./rpc/api-reference/methods/getLatestLedger
-[`getVersionInfo`]: ./rpc/api-reference/methods/getVersionInfo
-[`getHealth`]: ./rpc/api-reference/methods/getHealth
-[`getNetwork`]: ./rpc/api-reference/methods/getNetwork
-[`getLedgers`]: ./rpc/api-reference/methods/getLedgers
-[`getTransactions`]: ./rpc/api-reference/methods/getTransactions
-[`getTransaction`]: ./rpc/api-reference/methods/getTransaction
-[`getEvents`]: ./rpc/api-reference/methods/getEvents
-[`sendTransaction`]: ./rpc/api-reference/methods/sendTransaction
-[`getFeeStats`]: ./rpc/api-reference/methods/getFeeStats
-[`simulateTransaction`]: ./rpc/api-reference/methods/simulateTransaction
-[`getLedgerEntries`]: ./rpc/api-reference/methods/getLedgerEntries
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/README.mdx
deleted file mode 100644
index 8658e5ff3f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/README.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Usa el Stellar RPC para acceder a datos de Blockchain, consultar transacciones y más
-sidebar_label: RPC
-description: Aprende a usar los métodos RPC para ver el estado actual, acceder a los datos de Blockchain, interactuar con contratos inteligentes, consultar transacciones y más en la red Stellar.
-sidebar_position: 5
----
-
-# Introducción al RPC
-
-:::info
-
-Stellar-RPC fue renombrado de Soroban-RPC en Noviembre de 2024. Más contexto sobre esta decisión se puede encontrar en nuestro [blog de desarrolladores].
-
-:::
-
-Stellar RPC es una herramienta ligera que proporciona acceso en tiempo real a los datos de la red Stellar. Al igual que los nodos RPC en otros ecosistemas de Blockchain, permite a los desarrolladores consultar la red de manera eficiente. Ya sea que estés construyendo una billetera no custodiada, emitiendo activos o monitoreando la actividad de la red, Stellar RPC está diseñado para proporcionar una infraestructura confiable y estable que cualquiera puede operar.
-
-Para cualquier nuevo constructor que venga a Stellar, Stellar RPC debe ser tu punto de partida: está diseñada para alinearse con las crecientes necesidades del ecosistema. El RPC se puede acceder a través de cURL o uno de los [Stellar SDKs](../../../tools/sdks/README.mdx).
-
-## ¿Por qué ejecutar RPC?
-
-Ejecutar RPC dentro de tu propia infraestructura proporciona una serie de beneficios. Puedes:
-
-- Tener control operativo total sin depender de ningún proveedor externo para los datos de red y la presentación de transacciones. ¡La única forma de aprovechar el verdadero poder de un blockchain descentralizado!
-- Evita la sobrecarga adicional de interactuar directamente con [Stellar Core], cuyo enfoque principal es el rendimiento y, por lo tanto, proporciona una API muy limitada
-- Evita el sobrecoste añadido de almacenar muchos más datos de los que tu aplicación realmente necesita, como sería el caso al ejecutar [Horizon]
-
-Lo que Stellar RPC no es:
-
-- Un indexador para datos históricos. El RPC mantiene como máximo 7 días de datos históricos.
-- Un servicio backend principal para tu aplicación. Usa RPC como tu puerta de entrada a la Blockchain, pero ingiere e indexa solo los datos que te interesan.
-- Un reemplazo directo de Horizon. Horizon proporciona varias características de indexación que no son comúnmente admitidas por los nodos RPC. Creemos que estas oportunidades comerciales deberían ser transferidas a aplicaciones de terceros (indexadores, proveedores de análisis, etc.) y alejadas de la SDF.
-
-## En Estos Documentos
-
-- [Guía del Administrador](./admin-guide/README.mdx): cómo configurar y operar tu propia instancia de RPC.
-- [Métodos RPC](./api-reference/methods/README.mdx): descripciones de los métodos RPC, incluidos sus inputs y outputs esperados.
-- [Estructura](./api-reference/structure/README.mdx): cómo está estructurada la API de RPC.
-- [Proveedores del Ecosistema](./providers.mdx): proveedores externos que ofrecen instancias RPC como servicio.
-
-[inicio rápido]: https://github.com/stellar/quickstart
-[blog de desarrolladores]: https://stellar.org/blog/foundation-news/stellar-rpc-has-arrived
-[Stellar Core]: ../../validators
-[Horizon]: ./horizon
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/README.mdx
deleted file mode 100644
index 4cf92b919c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Guía del Administrador
-sidebar_position: 15
-sidebar_key: rpc-admin-guide
----
-
-import DocCardList from "@theme/DocCardList";
-
-Todo lo que necesitas saber sobre cómo configurar, ejecutar y utilizar Stellar RPC.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/configuring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/configuring.mdx
deleted file mode 100644
index 7a545f201b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/configuring.mdx
+++ /dev/null
@@ -1,264 +0,0 @@
----
-title: Configurar
-sidebar_position: 25
----
-
-Para producción, recomendamos ejecutar Stellar RPC con un archivo de configuración [TOML](https://toml.io/en/) en lugar de banderas del CLI. Esto es similar a crear un archivo de configuración para Stellar-Core como hicimos anteriormente. Por ejemplo, utilizando [nuestra imagen de docker](https://hub.docker.com/r/stellar/stellar-rpc):
-
-```bash
-docker run -p 8001:8001 -p 8000:8000 \
--v <CONFIG_FOLDER>:/config stellar/stellar-rpc \
---config-path <RPC_CONFIG_FILENAME>
-```
-
-Usa este [subcomando de Stellar RPC](https://github.com/stellar/stellar-rpc/blob/main/cmd/stellar-rpc/README.md#configuring-and-running-rpc-server) para generar un archivo de configuración inicial:
-
-```bash
-docker run stellar/stellar-rpc:latest gen-config-file > stellar-rpc-config.toml
-```
-
-La configuración resultante debería verse así:
-
-```toml
-# Admin endpoint to listen and serve on. WARNING: this should not be accessible
-# from the Internet and does not use TLS. "" (default) disables the admin server
-# ADMIN_ENDPOINT = ""
-
-# path to additional configuration for the Stellar Core configuration file used
-# by captive core. It must, at least, include enough details to define a quorum
-# set
-# CAPTIVE_CORE_CONFIG_PATH = ""
-
-# Storage location for Captive Core bucket data
-CAPTIVE_CORE_STORAGE_PATH = "/"
-
-# establishes how many ledgers exist between checkpoints, do NOT change this
-# unless you really know what you are doing
-CHECKPOINT_FREQUENCY = 64
-
-# configures classic fee stats retention window expressed in number of ledgers
-CLASSIC_FEE_STATS_RETENTION_WINDOW = 10
-
-# SQLite DB path
-DB_PATH = "stellar_rpc.sqlite"
-
-# Default cap on the amount of events included in a single getEvents response
-DEFAULT_EVENTS_LIMIT = 100
-
-# Default cap on the amount of ledgers included in a single getLedgers response
-DEFAULT_LEDGERS_LIMIT = 50
-
-# Default cap on the amount of transactions included in a single getTransactions
-# response
-DEFAULT_TRANSACTIONS_LIMIT = 50
-
-# Endpoint to listen and serve on
-ENDPOINT = "localhost:8000"
-
-# The friendbot URL to be returned by getNetwork endpoint
-# FRIENDBOT_URL = ""
-
-# comma-separated list of stellar history archives to connect with
-HISTORY_ARCHIVE_URLS = []
-
-# configures history retention window for transactions and events, expressed in
-# number of ledgers, the default value is 120960 which corresponds to about 7
-# days of history
-HISTORY_RETENTION_WINDOW = 120960
-
-# Ingestion Timeout when bootstrapping data (checkpoint and in-memory
-# initialization) and preparing ledger reads
-INGESTION_TIMEOUT = "50m0s"
-
-# format used for output logs (json or text)
-# LOG_FORMAT = "text"
-
-# minimum log severity (debug, info, warn, error) to log
-LOG_LEVEL = "info"
-
-# Maximum amount of events allowed in a single getEvents response
-MAX_EVENTS_LIMIT = 10000
-
-# The maximum duration of time allowed for processing a getEvents request. When
-# that time elapses, the rpc server would return -32001 and abort the request's
-# execution
-MAX_GET_EVENTS_EXECUTION_DURATION = "10s"
-
-# The maximum duration of time allowed for processing a getFeeStats request.
-# When that time elapses, the rpc server would return -32001 and abort the
-# request's execution
-MAX_GET_FEE_STATS_EXECUTION_DURATION = "5s"
-
-# The maximum duration of time allowed for processing a getHealth request. When
-# that time elapses, the rpc server would return -32001 and abort the request's
-# execution
-MAX_GET_HEALTH_EXECUTION_DURATION = "5s"
-
-# The maximum duration of time allowed for processing a getLatestLedger request.
-# When that time elapses, the rpc server would return -32001 and abort the
-# request's execution
-MAX_GET_LATEST_LEDGER_EXECUTION_DURATION = "5s"
-
-# The maximum duration of time allowed for processing a getLedgers request. When
-# that time elapses, the rpc server would return -32001 and abort the request's
-# execution
-MAX_GET_LEDGERS_EXECUTION_DURATION = "5s"
-
-# The maximum duration of time allowed for processing a getLedgerEntries
-# request. When that time elapses, the rpc server would return -32001 and abort
-# the request's execution
-MAX_GET_LEDGER_ENTRIES_EXECUTION_DURATION = "5s"
-
-# The maximum duration of time allowed for processing a getNetwork request. When
-# that time elapses, the rpc server would return -32001 and abort the request's
-# execution
-MAX_GET_NETWORK_EXECUTION_DURATION = "5s"
-
-# The maximum duration of time allowed for processing a getTransactions request.
-# When that time elapses, the rpc server would return -32001 and abort the
-# request's execution
-MAX_GET_TRANSACTIONS_EXECUTION_DURATION = "5s"
-
-# The maximum duration of time allowed for processing a getTransaction request.
-# When that time elapses, the rpc server would return -32001 and abort the
-# request's execution
-MAX_GET_TRANSACTION_EXECUTION_DURATION = "5s"
-
-# The maximum duration of time allowed for processing a getVersionInfo request.
-# When that time elapses, the rpc server would return -32001 and abort the
-# request's execution
-MAX_GET_VERSION_INFO_EXECUTION_DURATION = "5s"
-
-# maximum ledger latency (i.e. time elapsed since the last known ledger closing
-# time) considered to be healthy (used for the /health endpoint)
-MAX_HEALTHY_LEDGER_LATENCY = "30s"
-
-# Maximum amount of ledgers allowed in a single getLedgers response
-MAX_LEDGERS_LIMIT = 200
-
-# The max request execution duration is the predefined maximum duration of time
-# allowed for processing a request. When that time elapses, the server would
-# return 504 and abort the request's execution
-MAX_REQUEST_EXECUTION_DURATION = "25s"
-
-# The maximum duration of time allowed for processing a sendTransaction request.
-# When that time elapses, the rpc server would return -32001 and abort the
-# request's execution
-MAX_SEND_TRANSACTION_EXECUTION_DURATION = "15s"
-
-# The maximum duration of time allowed for processing a simulateTransaction
-# request. When that time elapses, the rpc server would return -32001 and abort
-# the request's execution
-MAX_SIMULATE_TRANSACTION_EXECUTION_DURATION = "15s"
-
-# Maximum amount of transactions allowed in a single getTransactions response
-MAX_TRANSACTIONS_LIMIT = 200
-
-# Network passphrase of the Stellar network transactions should be signed for.
-# Commonly used values are "Test SDF Future Network ; October 2022", "Test SDF
-# Network ; September 2015" and "Public Global Stellar Network ; September 2015"
-# NETWORK_PASSPHRASE = ""
-
-# Enable debug information in preflighting (provides more detailed errors). It
-# should not be enabled in production deployments.
-PREFLIGHT_ENABLE_DEBUG = true
-
-# Number of workers (read goroutines) used to compute preflights for the
-# simulateTransaction endpoint. Defaults to the number of CPUs.
-PREFLIGHT_WORKER_COUNT = 8
-
-# Maximum number of outstanding preflight requests for the simulateTransaction
-# endpoint. Defaults to the number of CPUs.
-PREFLIGHT_WORKER_QUEUE_SIZE = 8
-
-# Maximum number of outstanding GetEvents requests
-REQUEST_BACKLOG_GET_EVENTS_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding GetFeeStats requests
-REQUEST_BACKLOG_GET_FEE_STATS_QUEUE_LIMIT = 100
-
-# Maximum number of outstanding GetHealth requests
-REQUEST_BACKLOG_GET_HEALTH_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding GetLatestsLedger requests
-REQUEST_BACKLOG_GET_LATEST_LEDGER_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding getLedgers requests
-REQUEST_BACKLOG_GET_LEDGERS_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding GetLedgerEntries requests
-REQUEST_BACKLOG_GET_LEDGER_ENTRIES_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding GetNetwork requests
-REQUEST_BACKLOG_GET_NETWORK_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding GetTransactions requests
-REQUEST_BACKLOG_GET_TRANSACTIONS_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding GetTransaction requests
-REQUEST_BACKLOG_GET_TRANSACTION_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding GetVersionInfo requests
-REQUEST_BACKLOG_GET_VERSION_INFO_QUEUE_LIMIT = 1000
-
-# Maximum number of outstanding requests
-REQUEST_BACKLOG_GLOBAL_QUEUE_LIMIT = 5000
-
-# Maximum number of outstanding SendTransaction requests
-REQUEST_BACKLOG_SEND_TRANSACTION_QUEUE_LIMIT = 500
-
-# Maximum number of outstanding SimulateTransaction requests
-REQUEST_BACKLOG_SIMULATE_TRANSACTION_QUEUE_LIMIT = 100
-
-# The request execution warning threshold is the predetermined maximum duration
-# of time that a request can take to be processed before a warning would be
-# generated
-REQUEST_EXECUTION_WARNING_THRESHOLD = "5s"
-
-# configures soroban inclusion fee stats retention window expressed in number of
-# ledgers
-SOROBAN_FEE_STATS_RETENTION_WINDOW = 50
-
-# HTTP port for Captive Core to listen on (0 disables the HTTP server)
-STELLAR_CAPTIVE_CORE_HTTP_PORT = 11626
-
-# path to stellar core binary
-STELLAR_CORE_BINARY_PATH = "/usr/bin/stellar-core"
-
-# Timeout used when submitting requests to stellar-core
-STELLAR_CORE_TIMEOUT = "2s"
-
-# URL used to query Stellar Core (local captive core by default)
-# STELLAR_CORE_URL = ""
-
-# Enable strict toml configuration file parsing. This will prevent unknown
-# fields in the config toml from being parsed.
-# STRICT = false
-
-```
-
-Ten en cuenta que la configuración generada anteriormente contiene los valores predeterminados y necesitas sustituirlos por valores adecuados para ejecutar la imagen. Por ejemplo, al usar un contenedor, se recomienda crear un volumen para el almacenamiento persistente de Captive Core y RPC y dirigir `CAPTIVE_CORE_STORAGE_PATH` y `DB_PATH` a ello en consecuencia.
-
-Luego, deberías crear un archivo de configuración para [Stellar Core](https://github.com/stellar/stellar-core). Puedes encontrar archivos de configuración de ejemplo para [Testnet](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/configs/captive-core-testnet.cfg) y [Pubnet](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/configs/captive-core-pubnet.cfg)
-
-Al usar Docker, deberías crear y montar un volumen [montar un volumen](https://docs.docker.com/storage/volumes/) en tu contenedor donde se almacene la configuración anterior.
-
-Si estas ejecutando localmente en una máquina estilo unix, podrías crear una carpeta en tu directorio personal llamada `~/rpc-config`
-
-```
-cd ~
-mkdir rpc-config
-```
-
-Luego agregarías los siguientes archivos de configuración a ese directorio local:
-
-- soroban-rpc-config.toml
-- stellar-captive-core.cfg
-
-Luego montarías ese volumen añadiendo el siguiente parámetro: `-v /Users/<USERNAME>/test-rpc-config:/opt/stellar` a tu comando `docker run`.
-
-Tu contenedor en ejecución montaría ese volumen en la ruta `/opt/stellar`
-
-## Siguiente Paso
-
-¡Después de completar la instalación, ya estás listo para continuar a [Ejecutar RPC](./running.mdx)!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/data-lake-integration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/data-lake-integration.mdx
deleted file mode 100644
index dfb9ff25ab..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/data-lake-integration.mdx
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: Integración con Data Lake
-sidebar_position: 65
----
-
-Amplía las capacidades de tu nodo RPC conectándolo a un data lake para acceder al ledger histórico completo.
-
-#### Resumen de la integración
-
-La versión 23.0 de RPC introduce la integración del data lake para el punto final `getLedgers`, lo que permite acceder a los ledgers históricos fuera del período de retención local de tu nodo (generalmente 7 días). Todos los demás puntos finales RPC seguirán funcionando según la configuración `HISTORY_RETENTION_WINDOW` de tu nodo.
-
-El proceso implica configurar un data lake para el ledger y luego configurar tu nodo RPC para usarlo.
-
-:::info
-
-La metadata de un ledger devuelta por `getLedgers` puede variar dependiendo de su origen. Cuando un ledger se obtiene del almacén de datos local del RPC, su metadata está sujeta a la configuración de tu RPC. Sin embargo, los ledgers obtenidos del data lake generalmente se almacenan con toda la metadata incluida.
-
-:::
-
-### 1. Acceder a un Data Lake
-
-Tienes dos opciones para utilizar un data lake:
-
-- **Data Lake público:** La manera más sencilla es usar un data lake disponible públicamente. Por ejemplo, el data lake del ledger Stellar está disponible a través del programa AWS Open Data en `s3://aws-public-blockchain/v1.1/stellar/ledgers/pubnet`.
-- **Data Lake autohospedado:** Este método te permite tener más control sobre la integridad, disponibilidad y acceso a los datos, pero requiere que crees y administres tu propio data lake. La herramienta **Galexie** puede ayudarte a desplegar un data lake en AWS S3 o Google Cloud Storage (GCS). Para instrucciones detalladas, consulta la [Guía del administrador de Galexie](../../../../data/indexers/build-your-own/galexie/README.mdx).
-
-### 2. Configuración de RPC para Integración con Data Lake
-
-#### Prerrequisito
-
-Antes de comenzar, configura tu nodo RPC con las credenciales del proveedor en la nube y asegúrate de que tenga permisos de lectura para el bucket del data lake.
-
-#### Pasos de configuración
-
-Actualiza el archivo de configuración de tu nodo RPC con las siguientes opciones:
-
-1. **Especificar ruta de almacenamiento:** Define el backend de almacenamiento (`GCS` o `S3`) y proporciona la ruta completa al bucket (por ejemplo, `my-bucket/path/to/data`).
-2. **Habilita el Feature Flag:** Establece `SERVE_LEDGERS_FROM_DATASTORE` en `true`.
-3. **Configurar backend de Ledger:** Configura cómo se lee la información del almacenamiento de datos a través de [BufferedStorageBackend](../../../../data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx).
-
-#### Ejemplos de configuración
-
-A continuación, algunos ejemplos para configurar los backends GCS y S3.
-
-A. Ejemplo de Configuración GCS
-
-```toml
-# Enable fetching historical ledgers from the datastore when not available locally
-SERVE_LEDGERS_FROM_DATASTORE = true
-
-# External datastore configuration for GCS
-[datastore_config]
-  type = "GCS"
-
-[datastore_config.params]
-  destination_bucket_path = "your-bucket/path/to/data"
-
-[datastore_config.schema]
-  ledgers_per_file = 1
-  files_per_partition = 64000
-
-[buffered_storage_backend_config]
-  buffer_size = 100
-  num_workers = 10
-  retry_limit = 3
-  retry_wait = "5s"
-```
-
-B. Ejemplo de Configuración S3
-
-```toml
-# Enable fetching historical ledgers from the datastore when not available locally
-SERVE_LEDGERS_FROM_DATASTORE = true
-
-# External datastore configuration for S3
-[datastore_config]
-  type = "S3"
-
-[datastore_config.params]
-  destination_bucket_path = "your-bucket/path/to/data`"
-  region = "your_s3_region" # e.g., "us-east-1"
-
-[datastore_config.schema]
-  ledgers_per_file = 1
-  files_per_partition = 64000
-
-[buffered_storage_backend_config]
-  buffer_size = 100
-  num_workers = 10
-  retry_limit = 3
-  retry_wait = "5s"
-```
-
-### 3. Verificación de la Configuración
-
-Después de configurar tu nodo RPC, puedes verificar que la integración funciona haciendo una solicitud `GetLedgers` para un número de secuencia del ledger que sea anterior a la ventana estándar de retención de tu nodo. El RPC debería devolver con éxito los datos del ledger desde el data lake.
-
-Solicitud de Ejemplo:
-
-```
-curl -X POST https://<rpc-host>/ \
--H "Content-Type: application/json" \
--d '{
-    "jsonrpc": "2.0",
-    "id": "1",
-    "method": "getLedgers",
-    "params": {
-        "startLedger": 100,
-        "pagination": {
-            "limit": 1
-        }
-    }
-}'
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/development.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/development.mdx
deleted file mode 100644
index 44c355c11a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/development.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: Desarrollo
-sidebar_position: 45
----
-
-Para el desarrollo local, recomendamos [descargar](https://hub.docker.com/r/stellar/quickstart) y ejecutar una instancia local a través de [Docker Quickstart](https://github.com/stellar/quickstart) y ejecutar una red local o comunicarte con un [Testnet] de desarrollo en vivo.
-
-:::caution
-
-No recomendamos ejecutar la imagen de Quickstart en producción. Consulta la sección [implementa tu propia instancia RPC](./installing.mdx).
-
-:::
-
-### Independiente
-
-Para ejecutar una red independiente local con la imagen Docker de Stellar Quickstart, ejecuta el siguiente comando:
-
-```bash
-docker run --rm -it \
-    -p 8000:8000 \
-    --name stellar \
-    stellar/quickstart:testing \
-    --local \
-    --enable-stellar-rpc
-```
-
-Una vez que la imagen esté iniciada, puedes comprobar el estado de RPC consultando el punto final de verificación de salud:
-
-```bash
-curl --location 'http://localhost:8000/rpc' \
---header 'Content-Type: application/json' \
---data '{
-      "jsonrpc":"2.0",
-      "id":2,
-      "method":"getHealth"
-      }'
-```
-
-Puedes interactuar con este nodo local usando la CLI de Stellar. Primero, añádelo como una red configurada:
-
-```bash
-stellar network add local \
-    --rpc-url "http://localhost:8000/rpc" \
-    --network-passphrase "Standalone Network ; February 2017"
-```
-
-Luego genera una identidad única (keypair público/privado) y finánciala usando:
-
-```bash
-stellar keys generate alice
-```
-
-:::tip Identidades solo para pruebas
-
-Es una buena práctica no usar las mismas claves para pruebas y desarrollo que las que usas para la red pública de Stellar. Genera nuevas claves para pruebas y desarrollo y evita usarlas para otros propósitos.
-
-:::
-
-Ahora que tienes una red configurada y una identidad financiada, puedes usar estas dentro de otros comandos de la CLI de Stellar. Por ejemplo, implementar un contrato:
-
-```bash
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/[project_name].wasm \
-    --source-account alice \
-    --network local
-```
-
-O invocar un contrato:
-
-```bash
-stellar contract invoke \
-    --id C... \
-    --source-account alice \
-    --network local \
-    -- \
-    hello \
-    --to friend
-```
-
-Cuando termines con tu nodo local, puedes cerrarlo con <kbd>ctrl</kbd><kbd>c</kbd> (no <kbd>cmd</kbd>). Esto eliminará completamente el contenedor (eso es lo que hace la opción `--rm` del comando `docker`), lo que significa que necesitarás reimplementar tu contrato y volver a financiar tu identidad la próxima vez que lo inicies. Si trabajas frecuentemente con nodos locales, puede que quieras crear scripts para hacer más fáciles estos pasos de inicialización. Por ejemplo, consulta el [initialize.sh del ejemplo de dapp](https://github.com/stellar/soroban-example-dapp/blob/abdac3afdb6c410cc426831ece93371c1a27347d/initialize.sh).
-
-[Testnet]: ../../../../networks/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/installing.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/installing.mdx
deleted file mode 100644
index a82bfa3020..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/installing.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Instalando
-sidebar_position: 20
----
-
-Ofrecemos tres alternativas para implementar tu propia instancia de RPC:
-
-1. Ejecuta la [imagen de docker stellar-rpc](https://hub.docker.com/r/stellar/stellar-rpc)
-2. Instala un paquete de Debian.
-3. Instala desde la fuente.
-
-### Imagen de Docker
-
-Esta es la forma preferida de implementar tu propia instancia de RPC.
-
-:::caution
-
-Aunque tenemos una [Imagen de inicio rápido](https://github.com/stellar/quickstart), es solo para desarrollo y pruebas locales. No es adecuada para implementaciones de grado de producción.
-
-:::
-
-Descarga la imagen en la versión que deseas ejecutar de [las etiquetas](https://hub.docker.com/r/stellar/stellar-rpc/tags):
-
-```bash
-docker pull stellar/stellar-rpc
-```
-
-### Paquete de Debian
-
-```
-apt-get update && apt-get install -y --no-install-recommends ca-certificates curl jq wget gnupg apt-utils gpg && \
-    curl -sSL https://apt.stellar.org/SDF.asc | gpg --dearmor >/etc/apt/trusted.gpg.d/SDF.gpg && \
-    echo "deb https://apt.stellar.org focal stable" >/etc/apt/sources.list.d/SDF.list && \
-    echo "deb https://apt.stellar.org focal testing" >/etc/apt/sources.list.d/SDF-testing.list && \
-    echo "deb https://apt.stellar.org focal unstable" >/etc/apt/sources.list.d/SDF-unstable.list && \
-    apt-get update && \
-    apt-get install -y stellar-core stellar-rpc && \
-    apt-get clean
-```
-
-### Desarrollar desde la fuente
-
-Las instrucciones para desarrollar Stellar RPC desde la fuente se pueden encontrar [aquí](https://github.com/stellar/stellar-rpc/blob/main/cmd/stellar-rpc/README.md).
-
-## Próximo paso
-
-¡Después de completar la instalación, ahora estás listo para proceder a [Configurar RPC](./configuring.mdx)!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/monitoring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/monitoring.mdx
deleted file mode 100644
index 7ddc07f300..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/monitoring.mdx
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: Monitoreo
-sidebar_position: 60
----
-
-Si ejecutas Stellar RPC con el `--admin-endpoint` configurado y [expones el puerto](https://docs.docker.com/engine/reference/commandline/run/#publish), tendrás acceso a las métricas de [Prometheus](https://prometheus.io/) a través del endpoint `/metrics`. Por ejemplo, si el admin endpoint es `0.0.0.0:8001` y estás ejecutando la imagen Docker de Stellar RPC:
-
-```bash
-curl localhost:8001/metrics
-```
-
-Verás muchas de las métricas predeterminadas de Go y Process (prefijadas por `go_` y `process_` respectivamente) como uso de memoria, uso de CPU, número de hilos, etc.
-
-También exponemos métricas relacionadas con Stellar RPC (prefijadas por `soroban_rpc`). Hay muchas, pero algunas notables son:
-
-- `soroban_rpc_transactions_count` - conteo de transacciones ingeridas con una ventana dinámica de 10m
-- `soroban_rpc_events_count` - conteo de eventos ingeridos con una ventana dinámica de 10m
-- `soroban_rpc_ingest_local_latest_ledger` - último ledger ingerido
-- `soroban_rpc_db_round_trip_time_seconds` - tiempo requerido para ejecutar la consulta `SELECT 1` en la BASE DE DATOS
-
-Stellar RPC también proporciona registro en consola para:
-
-- Actividad de inicio
-- Ingerir, aplicar y cerrar ledgers
-- Manejar solicitudes JSON RPC
-- Cualquier error
-
-Los registros tienen el formato:
-
-```
-time=<timestamp in YYYY-MM-DDTHH:MM:SS.000Z format> level=<debug|info|error> msg=<Actual message> pid=<process ID> subservice=<optional if coming from subservice>
-```
-
-## Dashboard de Grafana
-
-Proporcionamos un [dashboard de Grafana](https://grafana.com/grafana/dashboards/19229-soroban-rpc/) con diferentes métricas para monitorear tu instancia de RPC.
-
-## Verificar la instancia de RPC
-
-Después de la instalación, valdrá la pena verificar que la instalación de Stellar RPC esté saludable. Hay dos métodos:
-
-1. Accede al endpoint de estado de salud del servicio JSON RPC usando un cliente HTTP
-2. Usa nuestra [imagen Docker de prueba del sistema](https://hub.docker.com/r/stellar/system-test/tags) como herramienta para ejecutar un conjunto de pruebas en vivo contra Stellar RPC
-
-### Endpoint de estado de salud
-
-Si envías una solicitud HTTP JSON RPC a tu instancia de Stellar RPC en ejecución:
-
-```bash
-curl --location 'http://localhost:8000' \
---header 'Content-Type: application/json' \
---data '{
-"jsonrpc":"2.0",
-"id":2,
-"method":"getHealth"
-}'
-```
-
-Deberías recibir una respuesta de estado HTTP 200 si la instancia está saludable:
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 2,
-  "result": {
-    "status": "healthy"
-  }
-}
-```
-
-### Imagen Docker de prueba del sistema
-
-Esta prueba compilará, desplegará e invocará contratos de ejemplo a la red a la que tu instancia de RPC está conectada. Aquí hay un ejemplo para verificar tu instancia si está conectada a Testnet:
-
-```bash
-# checkout https://github.com/stellar/system-test repo first, and build the image locally with release component versions
-system-test$ make  \
-  CORE_IMAGE=stellar/stellar-core:22 \
-  CORE_IMAGE_BIN_PATH=/usr/bin/stellar-core \
-  SOROBAN_RPC_GIT_REF=https://github.com/stellar/soroban-rpc.git#v22.1.2 \
-  SOROBAN_CLI_GIT_REF=https://github.com/stellar/soroban-cli.git#v22.2.0 \
-  RS_XDR_GIT_REF=v22.1.0 \
-  JS_STELLAR_SDK_NPM_VERSION=13.1.0 \
-  build
-# run the local system test image
-$ docker run --rm -t --name e2e_test \
-stellar/system-test:dev \
---VerboseOutput true \
---TargetNetworkRPCURL <your rpc url here> \
---TargetNetworkPassphrase "Test SDF Network ; September 2015" \
---TargetNetworkTestAccountSecret <your test account StrKey encoded key here > \
---TargetNetworkTestAccountPublic <your test account StrKey encoded pubkey here> \
-```
-
-Asegúrate de configurar correctamente la prueba del sistema:
-
-- Establece `--TargetNetworkRPCURL` en tu URL HTTP RPC
-- Establece `--TargetNetworkPassphrase` en la misma red a la que está conectada tu instancia de RPC:
-- `"Test SDF Network ; Septiembre 2015"` para Testnet
-- `"Test SDF Future Network ; Octubre 2022"` para Futurenet
-- Establece `--SorobanExamplesGitHash` en la etiqueta de lanzamiento correspondiente en el [repositorio de Ejemplos de Soroban](https://github.com/stellar/soroban-examples/tags)
-- Crea y financia una cuenta que se utilizará para propósitos de prueba en la misma red a la que está conectada tu instancia de RPC
-- Esta cuenta necesita un pequeño saldo de XLM para enviar transacciones Soroban
-- Las pruebas se pueden realizar repetidamente con la misma cuenta
-- Establece `--TargetNetworkTestAccountPublic` en la clave pública codificada `StrKey` de la cuenta
-- Establece `--TargetNetworkTestAccountSecret` en el secreto codificado `StrKey` para la cuenta
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/prerequisites.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/prerequisites.mdx
deleted file mode 100644
index 41acbc0454..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/prerequisites.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Requisitos previos
-sidebar_position: 10
----
-
-El servicio RPC se puede instalar en hardware físico o en una máquina virtual. Es admitido nativamente en ambos sistemas operativos: Linux y Windows.
-
-### Requisitos de hardware
-
-| Tipo de nodo   | CPU    | RAM  | Disco                                    | SKU de AWS  | SKU de Google Cloud |
-| -------------- | ------ | ---- | ---------------------------------------- | ----------- | ------------------- |
-| RPC de Stellar | 2 vCPU | 16GB | Volumen persistente de 250 GB >= 3K IOPS | [c5.xlarge] | [n4-highcpu-4]      |
-
-_\* Disco: Suponiendo la ventana de retención predeterminada de 7 días para el almacenamiento de datos. De lo contrario, 20 GB + 20 GB por día de retención_ _\* RAM/CPU: Suponiendo que RPC atenderá hasta 1000 solicitudes por segundo. Para implementaciones que esperan entre 1000 y más de 10000 solicitudes por segundo al RPC de Stellar, recomendamos al menos 16 GB de RAM y al menos una CPU de cuatro núcleos con una velocidad de reloj de 2,4 GHz._
-
-Te recomendamos encarecidamente utilizar un disco SSD local para almacenamiento. RPC es compatible con sistemas de archivos basados en la red como AWS EBS, pero impactará negativamente en su rendimiento.
-
-[c5.xlarge]: https://aws.amazon.com/ec2/instance-types/c5/
-[n4-highcpu-4]: https://cloud.google.com/compute/docs/general-purpose-machines#n4-highcpu
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/running.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/running.mdx
deleted file mode 100644
index 9bd7d91461..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/admin-guide/running.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: En ejecución
-sidebar_position: 40
----
-
-Puedes ejecutar el contenedor `stellar/stellar-rpc` con el siguiente comando:
-
-```bash
-docker run -p 8001:8001 -p 8000:8000 \
--v $HOME/rpc-config:/opt/stellar stellar/stellar-rpc \
---captive-core-config-path=/opt/stellar/stellar-captive-core.cfg \
---config-path=/opt/stellar/soroban-rpc-config.toml
-```
-
-## Siguiente paso
-
-Consulta [Monitoreo](./monitoring.mdx) para más detalles sobre el registro de ejecución de RPC y las métricas disponibles.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/README.mdx
deleted file mode 100644
index 113032b15b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Referencia de API
-sidebar_position: 20
-sidebar_key: rpc-api-reference
----
-
-import DocCardList from "@theme/DocCardList";
-
-Ver toda la información de la API RPC.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/_category_.json
deleted file mode 100644
index 9e3a55f459..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/README.mdx
deleted file mode 100644
index 8130258d40..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/README.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Métodos
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Todo lo que necesitas saber sobre los métodos RPC disponibles, parámetros y respuestas, y cómo hacer solicitudes RPC.
-
-<DocCardList />
-
-¿No sabes cuál endpoint necesitas para obtener lo que quieres? Muchos de los campos devueltos son estructuras [XDR](../../../../../learn/fundamentals/data-format/xdr.mdx#more-about-xdr) profundamente anidadas, por lo que puede ser difícil saber qué tipo de información está disponible en cada una de ellas. Aquí tienes un vistazo a lo que proporcionan los endpoints "caballo de batalla", en orden decreciente de granularidad:
-
-- [`getLedgers`](./getLedgers.mdx) opera a nivel de bloque, proporcionándote los detalles completos de lo que ocurrió durante la aplicación de ese ledger (conocido como "metadatos del ledger", definido en el protocolo por la unión [`LedgerCloseMeta`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger.x#L539), específicamente la iteración `V1`). Cada uno de los endpoints subsiguientes es solo un microscopio a un subconjunto de los datos disponibles proporcionados por este endpoint. Los metadatos incluyen cosas como:
-  - Detalles para recrear el estado de la blockchain (consulta [Ledger Headers](../../../../../learn/fundamentals/stellar-data-structures/ledgers.mdx#ledger-headers) para más información).
-  - La información del consenso que condujo al cierre del bloque (ver [Stellar Consensus Protocol](../../../../../learn/fundamentals/stellar-consensus-protocol.mdx)).
-  - El conjunto de transacciones, sus respectivas operaciones y los resultados de aplicar esas transacciones en este bloque (ver [Transacciones](../../../../../learn/fundamentals/transactions/operations-and-transactions.mdx)).
-- [`getTransaction(s)`](./getTransactions.mdx) opera a través de un rango de ledgers o en un solo hash de transacción dependiendo de la variante. Los datos estructurados aquí incluyen detalles tales como:
-  - La estructura exacta de la transacción ("sobre") que fue enviada.
-  - Resultados para cada una de las operaciones dentro de la transacción.
-  - Todos los efectos secundarios en el estado del ledger que ocurrieron como resultado de esta transacción.
-- [`getEvents`](./getEvents.mdx) te permite buscar eventos que ocurrieron en un rango de ledgers. Los eventos son emitidos por el sistema y por los contratos inteligentes para comunicar cambios significativos de estado a los indexadores fuera de la cadena (consulta [Eventos](../../../../../learn/fundamentals/stellar-data-structures/events.mdx) para más información). Cada evento está compuesto por temas (sobre los que puedes filtrar) y datos que son `ScVal`s, el tipo "valor" genérico de Stellar (consulta [Desarrollo de Contratos](../../../../../learn/fundamentals/contract-development/types/built-in-types.mdx) para más información).
-- [`getLedgerEntries`](./getLedgerEntries.mdx), en contraste con los endpoints anteriores, proporciona información sobre el estado **en vivo** on-chain en lugar de acciones históricas. La página [getLedgerEntries](./getLedgerEntries.mdx) en sí misma detalla los diferentes tipos de estado almacenado en la cadena y cómo recuperarlos.
-
-Si aún no estás seguro de lo que estás buscando, recuerda que puedes pasar `xdrFormat: "json"` como parámetro a cada uno de estos endpoints para obtener una versión en JSON completamente desempacada y legible por humanos de las estructuras XDR devueltas. Puedes navegar a través de estos hasta que encuentres lo que necesitas y volver a la variación Base64+desempacar en tu aplicación. Equipado con una comprensión de cómo atravesar XDR, la estructura del protocolo y tu [SDK favorito](../../../../../tools/sdks/README.mdx), deberías poder encontrar cualquier cosa que desees sobre la red Stellar con estos endpoints.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/_category_.json
deleted file mode 100644
index 9e3a55f459..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getEvents.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getEvents.mdx
deleted file mode 100644
index 4286f34cf8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getEvents.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-hide_title: true
-description: Devuelve eventos de contrato
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getEvents")[0]}
-/>
-
-### Usar el Laboratorio
-
-Pongamos a prueba la solicitud de ejemplo para **Eventos de Transferencia Nativa de XLM** directamente en [el Laboratorio Stellar](https://laboratory.stellar.org/).
-
-El nuevo Laboratorio admite **URLs compartibles** que completan automáticamente los campos de entrada basándose en los parámetros de consulta. Esto facilita compartir y volver a visitar configuraciones específicas.
-
-👉 [Ver ejemplo de Eventos de Transferencia Nativa de XLM en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-events?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$startLedger=572089&filters=%7B%22type%22:%22contract%22,%22contract_ids%22:%5B%22CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC%22%5D,%22topics%22:%5B%22%5B%5C%22AAAADwAAAAh0cmFuc2Zlcg==%5C%22,%5C%22*%5C%22,%5C%22*%5C%22,%5C%22*%5C%22%5D%22%5D%7D;;)
-
-![Laboratorio: Obtener Eventos](/assets/api/rpc/getevents.jpg)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getFeeStats.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getFeeStats.mdx
deleted file mode 100644
index 870be0285a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getFeeStats.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-hide_title: true
-description: Devuelve estadísticas sobre las tarifas de inclusión cobradas para transacciones de Soroban y transacciones de Stellar
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getFeeStats")[0]}
-/>
-
-### Usar el Laboratorio
-
-Puedes ver las **estadísticas actuales de tarifas de mainnet** usando [`mainnet.sorobanrpc.com`](https://sorobanrpc.com), impulsado por el servicio RPC de Overcat, directamente en el [Laboratorio Stellar](https://laboratory.stellar.org/).
-
-👉 [Ver estadísticas de tarifas de Mainnet en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-fee-stats?$=network$id=mainnet&label=Mainnet&horizonUrl=https:////horizon.stellar.org&rpcUrl=https:////mainnet.sorobanrpc.com&passphrase=Public%20Global%20Stellar%20Network%20/;%20September%202015;;)
-
-![Laboratorio: Obtener estadísticas de tarifas](/assets/api/rpc/getfeestats.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getHealth.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getHealth.mdx
deleted file mode 100644
index d81440c52b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getHealth.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-hide_title: true
-description: Devuelve la salud del nodo
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getHealth")[0]}
-/>
-
-### Usar el Laboratorio
-
-Puedes verificar el **estado de salud del nodo** tanto en **Testnet** como en **Mainnet** usando el método RPC `getHealth` directamente en el [Stellar Laboratory](https://laboratory.stellar.org/).
-
-👉 [Ver estado de salud del nodo en Testnet en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-health?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
-
-![Lab: getHealth](/assets/api/rpc/gethealth.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLatestLedger.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
deleted file mode 100644
index 505ff2998c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLatestLedger.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-hide_title: true
-description: Devuelve el ledger conocido más reciente
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getLatestLedger")[0]}
-/>
-
-### Usar el Laboratorio
-
-Puedes consultar el **ledger más reciente conocido** en **Testnet** y **Mainnet** utilizando el método RPC `getLatestLedger` directamente en el [Stellar Laboratory](https://laboratory.stellar.org/).
-
-👉 [Ver el Ledger Más Reciente de Testnet en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-latest-ledger?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
-
-![Laboratorio: getLatestLedger](/assets/api/rpc/getlatestledger.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx
deleted file mode 100644
index 2cfd3f1608..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLedgerEntries.mdx
+++ /dev/null
@@ -1,468 +0,0 @@
----
-hide_title: true
-description: Devuelve las entradas del ledger
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getLedgerEntries")[0]}
-/>
-
-# Creando claves del ledger
-
-El ledger de Stellar es, en cierto modo, esencialmente un almacén de pares clave-valor. Las claves son instancias de [`LedgerKey`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger-entries.x#L600) y los valores son instancias de [`LedgerEntry`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger-entries.x#L560). Un producto interesante del diseño interno del almacén es que la clave es un _subconjunto_ de la entrada: más adelante veremos más sobre esto.
-
-El método `getLedgerEntries` devuelve los "valores" (o "entradas") para un conjunto dado de "claves". Las claves del ledger vienen en muchas formas, y repasaremos las más comúnmente utilizadas en esta página junto con tutoriales sobre cómo crear y usarlas.
-
-## Tipos de `LedgerKey`
-
-La fuente de verdad siempre debe ser el XDR definido en el protocolo. `LedgerKey` son un tipo de unión definido en [Stellar-ledger-entries.x](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger-entries.x#L600). Hay 10 formas diferentes que puede tomar una clave de ledger:
-
-1. **Cuenta:** define de forma integral una cuenta Stellar, incluyendo su saldo, firmantes, etc. (ver [Cuentas](../../../../../learn/fundamentals/stellar-data-structures/accounts.mdx))
-2. **Línea de confianza:** define una línea de saldo para un activo no nativo emitido en la red (ver [`changeTrustOp`](../../../../../learn/fundamentals/transactions/list-of-operations.mdx#change-trust))
-3. **Oferta:** define una oferta realizada en el Stellar DEX (ver [Liquidez en Stellar](../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx))
-4. **Datos de cuenta:** define entradas de datos clave-valor adjuntas a una cuenta (ver [`manageDataOp`](../../../../../learn/fundamentals/transactions/list-of-operations.mdx#manage-data))
-5. **Saldo reclamable:** define un saldo que puede estar o no activo para ser reclamado (ver [Saldos reclamables](../../../../../build/guides/transactions/claimable-balances.mdx))
-6. **Pool de liquidez:** define la configuración de un pool de liquidez constante nativo entre dos activos (ver [Liquidez en Stellar](../../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx))
-7. **Datos de Contrato:** define un conjunto de datos que se almacena en un contrato bajo una clave
-8. **Código de Contrato:** define el bytecode Wasm de un contrato
-9. **Ajuste de Configuración:** define la configuración de red actualmente activa
-10. **TTL:** define el tiempo de vida de una entrada de datos de contrato o código asociada
-
-Nos enfocaremos en un subconjunto de estos para obtener el máximo valor, pero una vez que entiendas cómo crear y analizar algunas claves y entradas, puedes extrapolar a todas ellas.
-
-### Cuentas
-
-Para obtener una cuenta, todo lo que necesitas es su clave pública:
-
-<CodeExample>
-
-```typescript
-import { Keypair, xdr } from "@stellar/stellar-sdk";
-
-const publicKey = "GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO";
-const accountLedgerKey = xdr.LedgerKey.ledgerKeyAccount(
-  new xdr.LedgerKeyAccount({
-    accountId: Keypair.fromPublicKey(publicKey).xdrAccountId(),
-  }),
-);
-console.log(accountLedgerKey.toXDR("base64"));
-```
-
-```python
-from stellar_sdk import Keypair, xdr
-
-public_key = "GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO"
-account_ledger_key = xdr.LedgerKey(
-    type=xdr.LedgerEntryType.ACCOUNT,
-    account=xdr.LedgerKeyAccount(
-        account_id=Keypair.from_public_key(public_key).xdr_account_id()
-    ),
-)
-print(account_ledger_key.to_xdr())
-```
-
-</CodeExample>
-
-Esto te dará todos los detalles de la cuenta.
-
-<CodeExample>
-
-```typescript
-const accountEntryData = (
-  await s.getLedgerEntries(accountLedgerKey)
-).entries[0].account();
-```
-
-```python
-account_entry_data = xdr.LedgerEntryData.from_xdr(
-    server.get_ledger_entries([account_ledger_key]).entries[0].xdr
-).account
-```
-
-</CodeExample>
-
-Si solo quieres echar un vistazo a la estructura, puedes pasar el valor base64 en crudo que registramos anteriormente al [Laboratorio](https://lab.stellar.org/endpoints/rpc/get-ledger-entries?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$xdrFormat=json;;) (o mediante `curl` si pasas `"xdrFormat": "json"` como un parámetro adicional a `getLedgerEntries`) y ver todos los posibles campos. También puedes profundizar en ellos en el código, por supuesto:
-
-<CodeExample>
-
-```typescript
-console.log(
-  `Account ${publicKey} has ${accountEntryData
-    .balance()
-    .toString()} stroops of XLM and is on sequence number ${accountEntryData
-    .seqNum()
-    .toString()}`,
-);
-```
-
-```python
-print(
-    f"Account {public_key} has {account_entry_data.balance.int64} stroops of XLM and is on sequence number {account_entry_data.seq_num.sequence_number.int64}"
-)
-```
-
-</CodeExample>
-
-### Líneas de confianza
-
-Una trustline es una entrada de saldo para cualquier activo no nativo (como [USDC de Circle](https://stellar.expert/explorer/public/asset/USDC-GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN)). Para obtener una, necesitas el propietario de la línea de confianza (una clave pública como para [Cuentas](#accounts)) y el activo en cuestión:
-
-<CodeExample>
-
-```typescript
-const trustlineLedgerKey = xdr.LedgerKey.ledgerKeyTrustLine(
-  new xdr.LedgerKeyTrustLine({
-    accountId: Keypair.fromPublicKey(publicKey).xdrAccountId(),
-    asset: new Asset(
-      "USDC",
-      "GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN",
-    ).toTrustLineXDRObject(),
-  }),
-);
-```
-
-```python
-trustline_ledger_key = xdr.LedgerKey(
-    type=xdr.LedgerEntryType.TRUSTLINE,
-    trust_line=xdr.LedgerKeyTrustLine(
-        account_id=Keypair.from_public_key(public_key).xdr_account_id(),
-        asset=Asset(
-            "USDC", "GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN"
-        ).to_trust_line_asset_xdr_object(),
-    ),
-)
-
-trustline_entry_data = xdr.LedgerEntryData.from_xdr(
-    server.get_ledger_entries([trustline_ledger_key]).entries[0].xdr
-).trust_line
-```
-
-</CodeExample>
-
-Al igual que una [cuenta](#accounts), la entrada resultante tiene un saldo, pero también tiene un límite y banderas para controlar cuánto de ese activo se puede mantener. El activo, sin embargo, puede ser un activo emitido o un fondo de liquidez:
-
-<CodeExample>
-
-```typescript
-let asset: string;
-let rawAsset = trustlineEntryData.asset();
-
-switch (rawAsset.switch().value) {
-  case AssetType.assetTypeCreditAlphanum4().value:
-    asset = Asset.fromOperation(
-      xdr.Asset.assetTypeCreditAlphanum4(rawAsset.alphaNum4()),
-    ).toString();
-    break;
-
-  case AssetType.assetTypeCreditAlphanum12().value:
-    asset = Asset.fromOperation(
-      xdr.Asset.assetTypeCreditAlphanum12(rawAsset.alphaNum12()),
-    ).toString();
-    break;
-
-  case AssetType.assetTypePoolShare().value:
-    asset = rawAsset.liquidityPoolId().toXDR("hex");
-    break;
-}
-
-console.log(
-  `Account ${publicKey} has ${trustlineEntryData
-    .balance()
-    .toString()} stroops of ${asset} with a limit of ${trustlineEntryData
-    .limit()
-    .toString()}`,
-);
-```
-
-```python
-raw_asset = trustline_entry_data.asset
-asset: str = ""
-
-if (
-    raw_asset.type == xdr.AssetType.ASSET_TYPE_CREDIT_ALPHANUM4
-    or raw_asset.type == xdr.AssetType.ASSET_TYPE_CREDIT_ALPHANUM12
-):
-    asset_obj = Asset.from_xdr_object(raw_asset)
-    asset = f"{asset_obj.code}:{asset_obj.issuer}"
-elif raw_asset.type == xdr.AssetType.ASSET_TYPE_POOL_SHARE:
-    asset_obj = LiquidityPoolId.from_xdr_object(raw_asset)
-    asset = f"{asset_obj.liquidity_pool_id}"
-else:
-    raise ValueError("Invalid asset type")
-
-print(
-    f"Account {public_key} has {trustline_entry_data.balance.int64} stroops of {asset} with a limit of {trustline_entry_data.limit.int64}"
-)
-```
-
-</CodeExample>
-
-### Datos del contrato
-
-Supongamos que hemos desplegado el [`increment` example contract] y queremos averiguar qué valor está almacenado en la clave de ledger `COUNTER`. Para crear la clave:
-
-<CodeExample>
-
-```typescript
-import { xdr, Address } from "@stellar/stellar-sdk";
-
-const getLedgerKeySymbol = (
-  contractId: string,
-  symbolText: string,
-): xdr.LedgerKey => {
-  return xdr.LedgerKey.contractData(
-    new xdr.LedgerKeyContractData({
-      contract: new Address(contractId).toScAddress(),
-      key: xdr.ScVal.scvSymbol(symbolText),
-      // The increment contract stores its state in persistent storage,
-      // but other contracts may use temporary storage
-      // (xdr.ContractDataDurability.temporary()).
-      durability: xdr.ContractDataDurability.persistent(),
-    }),
-  );
-};
-
-const ledgerKey = getLedgerKeySymbol(
-  "CCPYZFKEAXHHS5VVW5J45TOU7S2EODJ7TZNJIA5LKDVL3PESCES6FNCI",
-  "COUNTER",
-);
-```
-
-```python
-from stellar_sdk import xdr, scval, Address
-
-def get_ledger_key_symbol(contract_id: str, symbol_text: str) -> str:
-    ledger_key = xdr.LedgerKey(
-        type=xdr.LedgerEntryType.CONTRACT_DATA,
-        contract_data=xdr.LedgerKeyContractData(
-            contract=Address(contract_id).to_xdr_sc_address(),
-            key=scval.to_symbol(symbol_text),
-            durability=xdr.ContractDataDurability.PERSISTENT
-        ),
-    )
-    return ledger_key.to_xdr()
-
-print(
-    get_ledger_key_symbol(
-        "CCPYZFKEAXHHS5VVW5J45TOU7S2EODJ7TZNJIA5LKDVL3PESCES6FNCI",
-        "COUNTER"
-    )
-)
-```
-
-</CodeExample>
-
-### Código Wasm del contrato
-
-Para entender esto, necesitamos comprender cómo funciona la implementación de contratos inteligentes:
-
-- Cuando despliegas un contrato, primero el código se "instala" (es decir, se sube a la blockchain), creando una `LedgerEntry` con el byte-código Wasm que se puede identificar de manera única por su hash (es decir, el hash del código subido).
-- Luego, cuando una _instancia_ de contrato se "instancia," creamos una `LedgerEntry` con una referencia al hash de ese código. Esto significa que muchos contratos pueden apuntar al mismo código Wasm.
-
-Por lo tanto, obtener el código del contrato es un proceso de dos pasos:
-
-1. Primero, buscamos el contrato en sí, para ver qué hash de código está referenciando.
-2. Luego, podemos buscar el código de bytes Wasm sin procesar usando ese hash.
-
-#### 1. Encuentra la clave del ledger para la instancia del contrato
-
-<CodeExample>
-
-```typescript
-import { Contract } from "@stellar/stellar-sdk";
-
-function getLedgerKeyContractCode(contractId): xdr.LedgerKey {
-  return new Contract(contractId).getFootprint();
-}
-
-console.log(
-  getLedgerKeyContractCode(
-    "CCPYZFKEAXHHS5VVW5J45TOU7S2EODJ7TZNJIA5LKDVL3PESCES6FNCI",
-  ),
-);
-```
-
-```python
-from stellar_sdk import xdr, Address
-
-def get_ledger_key_contract_code(contract_id: str) -> xdr.LedgerKey:
-  return xdr.LedgerKey(
-    type=xdr.LedgerEntryType.CONTRACT_DATA,
-    contract_data=xdr.LedgerKeyContractData(
-      contract=Address(contract_id).to_xdr_sc_address(),
-      key=xdr.SCVal(xdr.SCValType.SCV_LEDGER_KEY_CONTRACT_INSTANCE),
-      durability=xdr.ContractDataDurability.PERSISTENT
-    )
-  )
-
-print(get_ledger_key_contract_code(
-  "CCPYZFKEAXHHS5VVW5J45TOU7S2EODJ7TZNJIA5LKDVL3PESCES6FNCI"
-))
-```
-
-</CodeExample>
-
-Una vez que tengamos la entrada del ledger (a través de `getLedgerEntries`, ver [abajo](#actually-fetching-the-ledger-entry-data)), podemos extraer el hash de Wasm:
-
-#### 2. Solicita el `ContractCode` utilizando el `LedgerKey` recuperado
-
-Ahora toma el campo `xdr` del objeto `result` de la respuesta anterior y crea un `LedgerKey` a partir del hash contenido dentro.
-
-<CodeExample>
-
-```typescript
-import { xdr } from "@stellar/stellar-sdk";
-
-function getLedgerKeyWasmId(
-  contractData: xdr.ContractDataEntry,
-): xdr.LedgerKey {
-  const wasmHash = contractData.val().instance().executable().wasmHash();
-
-  return xdr.LedgerKey.contractCode(
-    new xdr.LedgerKeyContractCode({
-      hash: wasmHash,
-    }),
-  );
-}
-```
-
-```python
-from stellar_sdk import xdr
-
-def get_ledger_key_wasm_id(
-  # received from getLedgerEntries and decoded
-  contract_data: xdr.ContractDataEntry
-) -> xdr.LedgerKey:
-  # First, we dig the wasm_id hash out of the xdr we received from RPC
-  wasm_hash = contract_data.val.instance.executable.wasm_hash
-
-  # Now, we can create the `LedgerKey` as we've done in previous examples
-  ledger_key = xdr.LedgerKey(
-    type=xdr.LedgerEntryType.CONTRACT_CODE,
-    contract_code=xdr.LedgerKeyContractCode(
-      hash=wasm_hash
-    ),
-  )
-  return ledger_key
-```
-
-</CodeExample>
-
-Ahora, finalmente tenemos un `LedgerKey` que corresponde al código de bytes Wasm que ha sido implementado bajo el `contractId` con el que comenzamos hace tanto tiempo. Este `LedgerKey` puede ser utilizado en una solicitud final a `getLedgerEntries`. En esa respuesta obtendremos un `LedgerEntryData` correspondiente a un `ContractCodeEntry` que contendrá el código de bytes del contrato real implementado:
-
-<CodeExample>
-
-```typescript
-const theHashData: xdr.ContractDataEntry = await getLedgerEntries(
-  getLedgerKeyContractCode("C..."),
-).entries[0].contractData();
-
-const theCode: Buffer = await getLedgerEntries(getLedgerKeyWasmId(theHashData))
-  .entries[0].contractCode()
-  .code();
-```
-
-```python
-the_hash_data = xdr.LedgerEntryData.from_xdr(
-    server.get_ledger_entries([get_ledger_key_contract_code("C...")]).entries[0].xdr
-).contract_data
-
-the_code = xdr.LedgerEntryData.from_xdr(
-    server.get_ledger_entries([get_ledger_key_wasm_id(the_hash_data)]).entries[0].xdr
-).contract_code.code
-```
-
-</CodeExample>
-
-## Realmente obteniendo los datos de entrada del ledger
-
-Una vez que hemos aprendido a _crear_ y _analizar_ estos (lo cual ya hemos hecho anteriormente), el proceso para realmente obtenerlos es siempre idéntico. Si conoces el tipo de clave que has obtenido, aplicas el método de acceso correspondiente una vez que los has recibido del método `getLedgerEntries`:
-
-<CodeExample>
-
-```typescript
-const s = new Server("https://soroban-testnet.stellar.org");
-
-// assume key1 is an account, key2 is a trustline, and key3 is contract data
-const response = await s.getLedgerEntries(key1, key2, key3);
-
-const account = response.entries[0].account();
-const trustline = response.entries[1].trustline();
-const contractData = response.entries[2].contractData();
-```
-
-```python
-server = SorobanServer("https://soroban-testnet.stellar.org")
-
-# assume key1 is an account, key2 is a trustline, and key3 is contract data
-response = server.get_ledger_entries([key1, key2, key3])
-account = xdr.LedgerEntryData.from_xdr(response.entries[0].xdr).account
-trustline = xdr.LedgerEntryData.from_xdr(response.entries[1].xdr).trust_line
-contract_data = xdr.LedgerEntryData.from_xdr(response.entries[2].xdr).contract_data
-```
-
-</CodeExample>
-
-Ahora, finalmente tenemos un `LedgerKey` que corresponde al código de bytes Wasm que ha sido implementado bajo el `ContractId` con el que comenzamos hace tanto tiempo. Este `LedgerKey` puede ser usado en una solicitud final al punto final de Stellar-RPC.
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": 12345,
-  "method": "getLedgerEntries",
-  "params": {
-    "keys": [
-      "AAAAB+QzbW3JDhlUbDVW/C+1/5SIQDstqORuhpCyl73O1vH6",
-      "AAAABgAAAAGfjJVEBc55drW3U87N1Py0Rw0/nlqUA6tQ6r28khEl4gAAABQAAAAB"
-      "AAAABgAAAAAAAAABn4yVRAXOeXa1t1POzdT8tEcNP55alAOrUOq9vJIRJeIAAAAUAAAAAQAAABMAAAAA5DNtbckOGVRsNVb8L7X/lIhAOy2o5G6GkLKXvc7W8foAAAAA"
-    ]
-  }
-}
-```
-
-Luego puedes inspeccionarlos en consecuencia. Cada una de las entradas anteriores sigue el XDR para esa estructura `LedgerEntryData` con precisión. Por ejemplo, el `AccountEntry` está en [`Stellar-ledger-entries.x#L191`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-ledger-entries.x#L191) y puedes usar `.seqNum()` para acceder a su número de secuencia actual, como hemos mostrado. En JavaScript, puedes ver los métodos apropiados en la [definición de tipo](https://github.com/stellar/js-stellar-base/blob/6930a70d7fbde675514b5933baff605d97453ba7/types/curr.d.ts#L3034).
-
-## Ver y comprender XDR
-
-Si no quieres analizar el XDR programáticamente, también puedes utilizar tanto el [Stellar CLI](../../../../../tools/cli/stellar-cli.mdx) como el [Stellar Lab](https://lab.stellar.org/xdr/view) para obtener una vista legible para humanos de las claves y entradas del libro mayor. Por ejemplo,
-
-```bash
-echo 'AAAAAAAAAAAL76GC5jcgEGfLG9+nptaB9m+R44oweeN3EcqhstdzhQ==' | stellar xdr decode --type LedgerKey --output json-formatted
-{
-  "account": {
-    "account_id": "GAF67IMC4Y3SAEDHZMN57J5G22A7M34R4OFDA6PDO4I4VINS25ZYLBZZ"
-  }
-}
-```
-
-[contrato de ejemplo `increment`]: ../../../../../build/smart-contracts/getting-started/storing-data
-[Página de "Ver XDR" del Stellar Lab]: https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;
-
-## Usar el Lab
-
-El método `getLedgerEntries` te permite **leer datos en vivo del ledger directamente** de la red. Esto incluye entradas como **cuentas**, **líneas de confianza**, **ofertas**, **datos**, **saldos reclamables**, **fondos de liquidez** y más.
-
-Es especialmente útil para inspeccionar el **estado actual** de un contrato, el **código desplegado** o cualquier otra entrada del ledger vinculada a tu aplicación. Este método es a menudo la **forma principal de recuperar datos relacionados con el contrato** que pueden no aparecer a través de eventos o `simulateTransaction`.
-
-Para recuperar el código de bytes WASM de un contrato, usa la clave de entrada del ledger `ContractCode`.
-
-👉 [Ver getLedgerEntries en el Lab](https://lab.stellar.org/endpoints/rpc/get-ledger-entries?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
-
-Usando la [biblioteca Stellar XDR a JSON](https://github.com/stellar/js-stellar-xdr-json), el método `getLedgerEntries` puede generar dinámicamente campos de entrada basados en datos codificados en XDR. Por ejemplo, considera la siguiente cadena XDR:
-
-`AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=`
-
-Pruébalo en [el Lab](https://lab.stellar.org/endpoints/rpc/get-ledger-entries?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$ledgerKeyEntries=%5B%22AAAABgAAAAHMA//50//Q+w3Ni8UXWm//trxFBfAfl6De5kFttaMT0//ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=%22%5D;;)
-
-![Lab: getledgerentries](/assets/api/rpc/getledgerentries-01.gif)
-
-Vamos a enviar `getLedgerEntries` para la siguiente cadena XDR:
-
-`AAAABgAAAAGUvl2TPOjIsxuZgSyt3Lf0d6R2iNYu4rKDuULTaMKUSgAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAAAAAABdOuyYDwLteYrby3aOykd5c12LYrui/nhbXOgtejCSYAAAAAE=`
-
-Pruébalo en [el Lab](https://lab.stellar.org/endpoints/rpc/get-ledger-entries?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$ledgerKeyEntries=%5B%22AAAABgAAAAGUvl2TPOjIsxuZgSyt3Lf0d6R2iNYu4rKDuULTaMKUSgAAABAAAAABAAAAAgAAAA8AAAAHQmFsYW5jZQAAAAASAAAAAAAAAABdOuyYDwLteYrby3aOykd5c12LYrui//nhbXOgtejCSYAAAAAE=%22%5D&xdrFormat=json;;)
-
-![Lab: getledgerentries-02](/assets/api/rpc/getledgerentries-02.gif)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLedgers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLedgers.mdx
deleted file mode 100644
index bf4f4b0130..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getLedgers.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-hide_title: true
-description: Devuelve la lista de ledgers
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getLedgers")[0]}
-/>
-
-### Usar el Laboratorio
-
-Puedes recuperar una lista de **ledger anteriores** utilizando el método `getLedgers` en el [Stellar Laboratory](https://laboratory.stellar.org/). Este endpoint devuelve datos detallados del ledger comenzando desde un punto específico, con soporte para paginación—siempre que el rango solicitado se encuentre dentro de la retención histórica del proveedor de RPC.
-
-El método también admite un parámetro opcional de `formato XDR`, que permite a los desarrolladores elegir entre **JSON descompuesto** o **cadenas XDR codificadas en base64** para el formato de respuesta.
-
-👉 [Ver getLedgers en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-ledgers?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$startLedger=573041&xdrFormat=json;;)
-
-![Laboratorio: getLedgers](/assets/api/rpc/getledgers.gif)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getNetwork.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getNetwork.mdx
deleted file mode 100644
index 2512f8a708..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getNetwork.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-hide_title: true
-description: Devuelve la configuración de red
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getNetwork")[0]}
-/>
-
-### Usar el Laboratorio
-
-Puedes consultar **información general sobre la red configurada actualmente** en tanto **Testnet** como **Mainnet** utilizando el método RPC `getNetwork` directamente en el [Stellar Laboratory](https://laboratory.stellar.org/).
-
-👉 [Ver Testnet getNetwork en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-network?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
-
-![Laboratorio: getnetwork](/assets/api/rpc/getnetwork.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getTransaction.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getTransaction.mdx
deleted file mode 100644
index 9afc165eb9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getTransaction.mdx
+++ /dev/null
@@ -1,86 +0,0 @@
----
-hide_title: true
-description: Devuelve los detalles de la transacción
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getTransaction")[0]}
-/>
-
-### Guía del SDK
-
-El ejemplo anterior está consultando detalles de una transacción utilizando métodos RPC directamente. Si estás usando el SDK de Stellar para crear aplicaciones, puedes usar las funciones nativas para obtener la misma información.
-
-<CodeExample>
-
-```python
-# pip install --upgrade stellar-sdk
-from stellar_sdk import SorobanServer, soroban_rpc
-
-
-def get_transaction(hash: str) -> soroban_rpc.GetTransactionResponse:
-    server = SorobanServer(server_url='https://soroban-testnet.stellar.org', client=None)
-    tx = server.get_transaction(hash)
-    return tx
-
-tx = get_transaction("6bc97bddc21811c626839baf4ab574f4f9f7ddbebb44d286ae504396d4e752da")
-
-print("result", tx.status)
-```
-
-```js
-// yarn add @stellar/stellar-sdk
-import { Server } from "@stellar/stellar-sdk/rpc";
-
-const server = new Server("https://soroban-testnet.stellar.org");
-
-// Fetch transaction details
-async function getTransactionDetails(hash) {
-  try {
-    server.getTransaction(hash).then((tx) => {
-      console.log({ result: tx });
-    });
-  } catch (error) {
-    console.error("Error fetching transaction:", error);
-  }
-}
-
-getTransactionDetails(
-  "6bc97bddc21811c626839baf4ab574f4f9f7ddbebb44d286ae504396d4e752da",
-);
-```
-
-```java
-// implementation 'network.lightsail:stellar-sdk:0.44.0'
-
-import org.stellar.sdk.SorobanServer;
-import org.stellar.sdk.responses.sorobanrpc.GetTransactionResponse;
-
-public class GetTransactionExample {
-  public static void main(String[] args) {
-	SorobanServer server = new SorobanServer("https://soroban-testnet.stellar.org");
-	try {
-	  GetTransactionResponse tx = server.getTransaction("6bc97bddc21811c626839baf4ab574f4f9f7ddbebb44d286ae504396d4e752da");
-	  System.out.println("result: " + tx);
-	} catch (Exception e) {
-	  System.err.println("An error has occurred:");
-	  e.printStackTrace();
-	}
-  }
-}
-```
-
-</CodeExample>
-
-### Usar el Laboratorio
-
-Puedes usar el método `getTransaction` en el [Laboratorio Stellar](https://laboratory.stellar.org/) para **recuperar detalles sobre una transacción específica**. Esto es especialmente útil para verificar el estado de una transacción y determinar si ha sido grabada correctamente en la blockchain.
-
-La **ventana de retención del historial de transacciones por defecto** en `stellar-rpc` es de **24 horas**, pero esto se puede ajustar (hasta 7 días) para instancias privadas de RPC de Soroban usando la configuración `transaction-retention-window`. Para la depuración de transacciones más allá de esa ventana, considera indexar los datos tú mismo, usar un indexador de terceros o consultar **Hubble**—el conjunto de datos público de BigQuery de Stellar.
-
-👉 [Ver getTransaction en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-transaction?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
-
-(El siguiente hash de transacción es uno aleatorio que elegí de los últimos en el momento de escribir este documento) ![Laboratorio: getTransaction](/assets/api/rpc/gettransaction.gif)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getTransactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getTransactions.mdx
deleted file mode 100644
index 2ab267ec04..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getTransactions.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-hide_title: true
-description: Devuelve la lista de transacciones
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getTransactions")[0]}
-/>
-
-### Usar el Laboratorio
-
-El método `getTransactions` devuelve una **lista paginada de transacciones** comenzando desde un punto definido por el usuario. Puedes continuar paginando a través de los resultados siempre que el rango solicitado esté dentro de la **ventana de retención de historial** del proveedor RPC correspondiente.
-
-Usa este método en el [Laboratorio Stellar](https://laboratory.stellar.org/) para explorar la actividad reciente dentro de un marco temporal o rango de libro mayor dado.
-
-👉 [Ver Transacciones en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-transactions?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$startLedger=573331;;)
-
-![Laboratorio: gettransactions](/assets/api/rpc/gettransactions.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getVersionInfo.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getVersionInfo.mdx
deleted file mode 100644
index 4dd7e0f8c8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/getVersionInfo.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-hide_title: true
-description: Devuelve información de la versión
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "getVersionInfo")[0]}
-/>
-
-### Usar el Laboratorio
-
-El método `getVersionInfo` proporciona **detalles de versión** sobre el servicio RPC y su **Captive Core** subyacente, una versión reducida y embebida de Stellar Core optimizada específicamente para operaciones de RPC de Soroban.
-
-Esto es útil para depuración, admitir o asegurar la compatibilidad entre diferentes componentes en tus entornos de desarrollo o producción.
-
-👉 [Ver Información de Versión en el Laboratorio](https://lab.stellar.org/endpoints/rpc/get-version-info?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
-
-![Laboratorio: getVersionInfo](/assets/api/rpc/getversioninfo.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/sendTransaction.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/sendTransaction.mdx
deleted file mode 100644
index 2447114c37..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/sendTransaction.mdx
+++ /dev/null
@@ -1,197 +0,0 @@
----
-hide_title: true
-description: Envía una transacción
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "sendTransaction")[0]}
-/>
-
-### Guía del SDK
-
-El ejemplo anterior está enviando una transacción utilizando métodos RPC directamente. Si estás utilizando el SDK de Stellar para crear aplicaciones, puedes usar las funciones nativas para obtener la misma información.
-
-<CodeExample>
-
-```python
-# pip install --upgrade stellar-sdk
-from stellar_sdk import SorobanServer, soroban_rpc, Keypair, Network, TransactionBuilder, scval
-
-def send_transaction() -> soroban_rpc.SendTransactionResponse:
-    server = SorobanServer(server_url='https://soroban-testnet.stellar.org', client=None)
-
-    root_keypair = Keypair.from_secret(
-        "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
-    )
-    root_account = server.load_account(root_keypair.public_key)
-    # native token contract (XLM)
-    contract_id = "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC"
-    transaction = (
-        TransactionBuilder(
-            source_account=root_account,
-            network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-            base_fee=100,
-        )
-        # Transfer 1 native token to GBRPYHIL2CI3FNQ4BXLFMNDLFJUNPU2HY3ZMFSHONUCEOASW7QC7OX2H
-        # https://developers.stellar.org/docs/tokens/token-interface
-        .append_invoke_contract_function_op(contract_id, "transfer", [
-            scval.to_address(root_keypair.public_key),  # from
-            scval.to_address("GBRPYHIL2CI3FNQ4BXLFMNDLFJUNPU2HY3ZMFSHONUCEOASW7QC7OX2H"),  # to
-            scval.to_int128(1 * 10 ** 7)  # amount, 1 XLM, decimal places are 7
-        ])
-        .set_timeout(30)
-        .build()
-    )
-
-    transaction = server.prepare_transaction(transaction)
-    transaction.sign(root_keypair)
-    return server.send_transaction(transaction)
-
-
-response = send_transaction()
-
-print("status", response.status)
-print("hash:", response.hash)
-print("status:", response.status)
-print("errorResultXdr:", response.error_result_xdr)
-```
-
-```js
-// yarn add @stellar/stellar-sdk
-import * as StellarSdk from "@stellar/stellar-sdk";
-
-import { Server } from "@stellar/stellar-sdk/rpc";
-const server = new Server("https://soroban-testnet.stellar.org");
-
-async function sendTransaction() {
-  try {
-    // native token contract (XLM)
-    const contractId =
-      "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC";
-    const sourceSecretKey =
-      "SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
-    const contract = new StellarSdk.Contract(contractId);
-    const sourceKeypair = StellarSdk.Keypair.fromSecret(sourceSecretKey);
-    const accountId = sourceKeypair.publicKey();
-
-    const account = await server.getAccount(accountId);
-    const fee = StellarSdk.BASE_FEE;
-    // Transfer 1 native token to GBRPYHIL2CI3FNQ4BXLFMNDLFJUNPU2HY3ZMFSHONUCEOASW7QC7OX2H
-    // https://developers.stellar.org/docs/tokens/token-interface
-    const transaction = new StellarSdk.TransactionBuilder(account, { fee })
-      .setNetworkPassphrase(StellarSdk.Networks.TESTNET)
-      .setTimeout(30)
-      .addOperation(
-        contract.call(
-          "transfer",
-          StellarSdk.nativeToScVal(accountId, { type: "address" }), // from
-          StellarSdk.nativeToScVal(
-            "GBRPYHIL2CI3FNQ4BXLFMNDLFJUNPU2HY3ZMFSHONUCEOASW7QC7OX2H",
-            { type: "address" },
-          ), // to
-          StellarSdk.nativeToScVal("10000000", { type: "i128" }), // amount, 1 XLM, decimal places are 7
-        ),
-      )
-      .build();
-
-    server
-      .prepareTransaction(transaction)
-      .then((result) => {
-        result.sign(sourceKeypair);
-        return server.sendTransaction(result);
-      })
-      .then((result) => {
-        console.log("hash:", result.hash);
-        console.log("status:", result.status);
-        console.log("errorResultXdr:", result.errorResultXdr);
-      });
-  } catch (error) {
-    console.error("Error fetching transaction:", error);
-  }
-}
-
-sendTransaction();
-```
-
-```java
-// https://github.com/lightsail-network/java-stellar-sdk?tab=readme-ov-file#installation
-import org.stellar.sdk.KeyPair;
-import org.stellar.sdk.Network;
-import org.stellar.sdk.SorobanServer;
-import org.stellar.sdk.Transaction;
-import org.stellar.sdk.TransactionBuilder;
-import org.stellar.sdk.TransactionBuilderAccount;
-import org.stellar.sdk.operations.InvokeHostFunctionOperation;
-import org.stellar.sdk.responses.sorobanrpc.SendTransactionResponse;
-import org.stellar.sdk.scval.Scv;
-
-import java.math.BigInteger;
-import java.util.Arrays;
-
-public class SendTransactionExample {
-
-  public static void main(String[] args) {
-    SorobanServer server = new SorobanServer("https://soroban-testnet.stellar.org");
-    try {
-      KeyPair sourceKeyPair =
-          KeyPair.fromSecretSeed("SXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX");
-      TransactionBuilderAccount sourceAccount = server.getAccount(sourceKeyPair.getAccountId());
-      // native token contract (XLM)
-      String contractId = "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC";
-
-      // Transfer 1 native token to GBRPYHIL2CI3FNQ4BXLFMNDLFJUNPU2HY3ZMFSHONUCEOASW7QC7OX2H
-      // https://developers.stellar.org/docs/tokens/token-interface
-      org.stellar.sdk.operations.InvokeHostFunctionOperation operation =
-          InvokeHostFunctionOperation.invokeContractFunctionOperationBuilder(
-                  contractId,
-                  "transfer",
-                  Arrays.asList(
-                      Scv.toAddress(sourceKeyPair.getAccountId()), // from
-                      Scv.toAddress(
-                          "GBRPYHIL2CI3FNQ4BXLFMNDLFJUNPU2HY3ZMFSHONUCEOASW7QC7OX2H"), // to
-                      Scv.toInt128(
-                          BigInteger.valueOf(10000000)) // amount, 1 XLM, decimal places are 7
-                      ))
-              .build();
-      Transaction transaction =
-          new TransactionBuilder(sourceAccount, Network.TESTNET)
-              .setBaseFee(100)
-              .addOperation(operation)
-              .setTimeout(30)
-              .build();
-
-      transaction = server.prepareTransaction(transaction);
-
-      // Sign the transaction
-      transaction.sign(sourceKeyPair);
-
-      // Send the transaction using the SorobanServer
-      SendTransactionResponse response = server.sendTransaction(transaction);
-      System.out.println(response.getStatus());
-      System.out.println(response.getHash());
-      System.out.println(response.getLatestLedger());
-      System.out.println(response.getLatestLedgerCloseTime());
-    } catch (Exception e) {
-      System.err.println("An error has occurred:");
-      e.printStackTrace();
-    }
-  }
-}
-```
-
-</CodeExample>
-
-### Usar el laboratorio
-
-El método `sendTransaction` se utiliza para **enviar una transacción real a la red Stellar**, siendo la única forma de ejecutar **cambios en la cadena** a través de RPC.
-
-A diferencia de Horizon, este método **no espera confirmación**. En cambio, **valida y encola** la transacción. Para rastrear su resultado final, los clientes deben realizar un seguimiento mediante una llamada a [`getTransaction`](../methods/getTransaction.mdx).
-
-Este método admite **todas las transacciones de Stellar**, incluyendo, pero no limitándose a, invocaciones de contratos inteligentes.
-
-👉 [Enviar (Presentar) una transacción en el laboratorio](https://lab.stellar.org/endpoints/rpc/send-transaction?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
-
-![Laboratorio: sendTransaction](/assets/api/rpc/sendtransaction.gif)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/simulateTransaction.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/simulateTransaction.mdx
deleted file mode 100644
index e0ea2d4617..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/methods/simulateTransaction.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-hide_title: true
-description: Envía una transacción de invocación de contrato de prueba
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "@site/static/stellar-rpc.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "simulateTransaction")[0]
-  }
-/>
-
-:::note
-
-`simulateTransaction` también puede invocar funciones de solo lectura de forma gratuita.
-
-:::
-
-### Usar el Laboratorio
-
-El método `simulateTransaction` te permite **simular una invocación de contrato inteligente** sin realmente enviarlo a la red. Es una herramienta poderosa para probar y depurar transacciones de forma segura.
-
-Este punto final devuelve los **datos de transacción calculados**, **autorizaciones requeridas** y la **tarifa mínima de recursos**, ayudándote a entender cómo la red procesaría la transacción antes de que la envíes.
-
-👉 [Simular una Transacción en el Laboratorio](https://lab.stellar.org/endpoints/rpc/simulate-transaction?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;)
-
-![Laboratorio: simulateTransaction](/assets/api/rpc/simulatetransaction.gif)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/README.mdx
deleted file mode 100644
index 92b2f618e3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/README.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Referencia de la API RPC
-sidebar_position: 31
-sidebar_label: Estructura
-description: RPC proporciona una API para interactuar con la red Stellar.
-sidebar_key: rpc-api-structure
----
-
-import DocCardList from "@theme/DocCardList";
-
-Cómo está estructurada la API RPC.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/_category_.json
deleted file mode 100644
index 6b391f4e50..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-  }  
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/data-format.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/data-format.mdx
deleted file mode 100644
index cae36bfe43..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/data-format.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-sidebar_position: 60
-title: Formatos de datos
----
-
-### Formato XDR
-
-En la red Stellar, las transacciones se codifican utilizando un protocolo estandarizado llamado [External Data Representation](../../../../../learn/fundamentals/data-format/xdr.mdx) (XDR).
-
-En RPC, encontrarás XDR cuando [simules](../methods/simulateTransaction) y [envíes](../methods/sendTransaction) transacciones, así como cuando recuperes [transacciones](../methods/getTransactions), [ledger](../methods/getLedgers) y [entradas de ledger](../methods/getLedgerEntries).
-
-Por defecto, RPC devolverá todos los atributos XDR como cadenas codificadas en base64 legibles por máquina. Los campos de respuesta codificados en XDR suelen tener el sufijo `Xdr`. Puedes decodificar este XDR en la página de [XDR de Stellar Lab](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;).
-
-### Formato JSON
-
-Todos los puntos finales RPC que devuelven campos codificados en XDR aceptan el atributo `xdrFormat`. Esto permite a un cliente cambiar el formato de respuesta a JSON, haciéndolo más legible para las personas. Ten en cuenta que no deberías confiar en ningún esquema para el JSON, ya que cambiará cuando se modifique el XDR subyacente.
-
-En caso de solicitar un formato de salida `json`, se omitirán los campos de respuesta con sufijo `Xdr` y se reemplazarán por sus equivalentes con sufijo `Json`.
-
-<ExampleResponse title="Respuesta de ejemplo de getTransaction">
-
-```json
-{
-  // xdrFormat = 'base64'
-  "resultMetaXdr": "AAAAAwAAAAAAAAACAAAAAwAWuFYAAAAAAAAAAEBQYAimx5waQHaAptKgy2a/IAHMSe96ETt5wiMOSpKXAAAAF0JZ4rAAACHUAAekYwAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAAAAAAAAAAAAAMAAAAAABa4VAAAAABnyjD0AAAAAAAAAAEAFrhWAAAAAAAAAABAUGAIpsecGkB2gKbSoMtmvyABzEnvehE7ecIjDkqSlwAAABdCWeKwAAAh1AAHpGQAAAAAAAAAAAAAAAAAAAAAAQAAAAAAAAAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAAAAAAAAAAADAAAAAAAWuFYAAAAAZ8ow/gAAAAAAAAAAAAAAAAAAAAA=",
-  // xdrFormat = 'json'
-  "resultMetaJson": {
-    "tx": {
-      "tx": {
-        "source_account": "GCW2NGRNWISFIXSGCBXPU23GDBAMHIOQOWO52LZWEWNELRC4XDQMDWNT",
-        "fee": 100,
-        "seq_num": 58248347706520,
-        "cond": {
-          "time": {
-            "min_time": 0,
-            "max_time": 1741309515
-          }
-        },
-        "memo": {
-          "text": "6764203ea0bcd7058f922d32"
-        },
-        "operations": [
-          {
-            "source_account": null,
-            "body": {
-              "payment": {
-                "destination": "GBZA3UPYFIFXXPH4QPQSFL73TZND7MEN744BLU4DPBR4T2XS526PRRN2",
-                "asset": "native",
-                "amount": 635808330
-              }
-            }
-          }
-        ],
-        "ext": "v0"
-      },
-      "signatures": [
-        {
-          "hint": "5cb8e0c1",
-          "signature": "cfcfc8192be1448b6c1e06265bd89b7375fdd818927f5167071d1e4f383522e6968771c91272fc248b4984f3f8c3ea7089396ab63c5dc557a45130c307f1840a"
-        }
-      ]
-    }
-  }
-}
-```
-
-</ExampleResponse>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/json-rpc.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/json-rpc.mdx
deleted file mode 100644
index 2865d32252..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/json-rpc.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-sidebar_position: 40
-title: JSON-RPC
----
-
-Stellar-RPC aceptará solicitudes HTTP POST utilizando la especificación [JSON-RPC <b>2.0</b>]. Los errores se devuelven a través del [jsonrpc error object] siempre que sea posible (y tenga sentido).
-
-Para instancias de producción y otras accesibles públicamente, el endpoint JSON-RPC debería servirse a través de SSL en el puerto 443, siempre que sea posible, por seguridad y facilidad de uso. Sin embargo, stellar-rpc no termina SSL por sí mismo, por lo que necesitará un balanceador de carga u otro servicio para terminar SSL para él.
-
-Para interactuar con stellar-rpc desde dentro de una aplicación JavaScript, utiliza el paquete [JavaScript SDK], que ofrece una interfaz conveniente para los métodos RPC dentro de su módulo `rpc`.
-
-Cuando se pasa XDR como parámetro o se devuelve, siempre es una cadena codificada utilizando base64 estándar.
-
-:::info
-
-Por favor, ten en cuenta que la estructura del parámetro debe contener parámetros nombrados como un objeto con nombre, y no como argumentos posicionales en un arreglo por posición. Los argumentos posicionales en un arreglo por posición serán desaprobados en futuras versiones de RPC.
-
-:::
-
-## Códigos de error
-
-<div>
-
-| Código de error | Significado                                          |
-| :-------------- | :--------------------------------------------------- |
-| \-32600         | El JSON enviado no es un objeto Request válido       |
-| \-32601         | El método no existe / no está disponible             |
-| \-32602         | Parámetro(s) del método inválido(s)                  |
-| \-32603         | Error interno de JSON-RPC                            |
-
-</div>
-
-## Ejemplo de Solicitud
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": "1",
-  "method": "getTransaction",
-  "params": {
-    "hash": "5ee7e055afb3b0b13fd6ac6d8adb11f799df8593448e23ad93454fefc387bbfa"
-  }
-}
-```
-
-## Ejemplo de Respuesta
-
-```js
-{
-  "jsonrpc": "2.0",
-  "id": "1",
-  "result": {
-    "status": "SUCCESS",
-    // ...
-  }
-}
-```
-
-## Especificación Open-RPC
-
-Stellar-RPC proporciona un documento de especificación [OpenRPC] que se puede utilizar para simular, construir y/o validar las implementaciones de software tanto del servidor como del cliente. Este documento se utiliza para generar todas nuestras páginas de documentación [methods]. Puedes ver el documento completo de [especificación aquí]. Además, puedes experimentar con este documento de especificación en el [OpenRPC Playground].
-
-[JSON-RPC <b>2.0</b>]: https://www.jsonrpc.org/specification
-[jsonrpc error object]: https://www.jsonrpc.org/specification#error_object
-[JavaScript SDK]: https://github.com/stellar/js-stellar-sdk
-[OpenRPC]: https://open-rpc.org/
-[métodos]: ../métodos
-[documento de especificación aquí]: https://raw.githubusercontent.com/stellar/stellar-docs/main/static/stellar-rpc.openrpc.json
-[OpenRPC Playground]: https://playground.open-rpc.org/?schemaUrl=https://raw.githubusercontent.com/stellar/stellar-docs/main/static/stellar-rpc.openrpc.json
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/pagination.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/pagination.mdx
deleted file mode 100644
index c4c368a041..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/api-reference/structure/pagination.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-sidebar_position: 50
-title: Paginación
----
-
-Para los métodos que lo admiten, los argumentos de paginación se pasan como un último argumento objeto con dos valores:
-
-- `cursor`: cadena - (opcional) Una cadena opaca que actúa como un token de paginación. Cada respuesta incluirá un campo `cursor` que se puede incluir en una solicitud subsiguiente para obtener la siguiente página de resultados.
-- `limit`: número - (opcional) El número máximo de registros devueltos. El límite para [getEvents](../methods/getEvents.mdx) puede oscilar entre 1 y 10000, un límite superior codificado en Stellar-RPC por razones de rendimiento. Si este argumento no se designa, por defecto es 100.
-
-Por ejemplo, al llamar a un método con el parámetro de paginación establecido:
-
-```json
-{
-  "jsonrpc": "2.0",
-  "id": "1",
-  "method": "exampleMethod",
-  "params": {
-    "some": "argument",
-    "pagination": {
-      "cursor": "1234-1",
-      "limit": 100
-    }
-  }
-}
-```
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
deleted file mode 100644
index ef277693db..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx
+++ /dev/null
@@ -1,45 +0,0 @@
----
-sidebar_position: 60
-title: Proveedores
----
-
-Múltiples proveedores de infraestructura han puesto a disposición servicios RPC de Stellar y ofrecen planes que van desde gratuitos hasta instancias dedicadas. Estos proveedores pueden usarse para desarrollo, pruebas y producción.
-
-Estos proveedores permiten el acceso a las redes Futurenet, Testnet y Mainnet.
-
-| Proveedor                                                         | Futurenet | Testnet | Mainnet | Nodos dedicados | Archivo RPC |
-| ----------------------------------------------------------------- | --------- | ------- | ------- | --------------- | ----------- |
-| [Blockdaemon](https://www.blockdaemon.com/apply/soroban)          | ❌         | ✅       | ✅       | ✅               | ❌           |
-| [Validation Cloud](https://app.validationcloud.io/)               | ❌         | ✅       | ✅       | ❌               | ❌           |
-| [QuickNode](https://www.quicknode.com/docs/stellar)               | ❌         | ✅       | ✅       | ✅               | ❌           |
-| [NowNodes](https://nownodes.io/nodes/stellar-xlm)                 | ✅         | ✅       | ✅       | ✅               | ❌           |
-| [Gateway\*](https://gateway.fm/public-rpc/)                       | ❌         | ✅       | ✅       | ✅               | ✅           |
-| [Ankr](https://www.ankr.com/rpc/advanced-api/)                    | ❌         | ✅       | ✅       | ❌               | ❌           |
-| [Infstones](https://infstones.com/)                               | ❌         | ❌       | ✅       | ✅               | ❌           |
-| [Obsrvr\*](https://www.withObsrvr.com/)                           | ❌         | ✅       | ✅       | ❌               | ✅           |
-| [Nodies](https://nodies.org)                                      | ❌         | ✅       | ✅       | ❌               | ❌           |
-| [OnFinality\*](https://onfinality.io/networks/stellar)            | ❌         | ❌       | ✅       | ✅               | ✅           |
-| [Lightsail Network - Quasar\*](https://quasar.lightsail.network/) | ❌         | ❌       | ✅       | ❌               | ✅           |
-| [Uniblock](https://www.uniblock.dev/)                             | ❌         | ✅       | ✅       | ❌               | ❌           |
-| [Exaion](https://crypto.exaion.com)                               | ❌         | ❌       | ✅       | ✅               |             |
-
-\*_RPC Archive es una nueva opción para quienes buscan recuperar el historial completo del ledger. Actualmente, solo el método RPC [getLedgers](./api-reference/methods/getLedgers.mdx) soporta esta característica. Puedes elegir uno de los proveedores anteriores o crear tu propio archivo getLedgers siguiendo [estos pasos](./admin-guide/data-lake-integration.mdx).
-
-_La columna "Dedicated Nodes" representa proveedores que alojan nodos completos como servicio._
-
-### APIs accesibles públicamente
-
-| Proveedor                                                       | Red       | URL                                                                     |
-| --------------------------------------------------------------- | --------- | ----------------------------------------------------------------------- |
-| [Liquify](https://www.liquify.io/)                              | Futurenet | RPC: `https://stellar.liquify.com/api=41EEWAH79Y5OCGI7/futurenet`       |
-|                                                                 | Testnet   | RPC: `https://stellar.liquify.com/api=41EEWAH79Y5OCGI7/testnet`         |
-|                                                                 | Mainnet   | RPC: `https://stellar-mainnet.liquify.com/api=41EEWAH79Y5OCGI7/mainnet` |
-| [Gateway](https://gateway.fm/)                                  | Testnet   | RPC: `https://soroban-rpc.testnet.stellar.gateway.fm`                   |
-|                                                                 | Mainnet   | RPC: `https://soroban-rpc.mainnet.stellar.gateway.fm`                   |
-| [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`                                |
-| [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/data/indexers/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/README.mdx
deleted file mode 100644
index cb87ece368..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/README.mdx
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: Resumen de indexadores
-sidebar_label: Indexadores
-sidebar_position: 0
----
-
-## ¿Qué es un indexador y por qué lo necesitarías?
-
-Cuando empiezas a desarrollar en una plataforma de contratos inteligentes como Stellar, al principio puedes obtener todo lo que necesitas con llamadas RPC. Escribes un contrato, o lanzas un Stellar Classic Asset y [lo envuelves en un contrato inteligente](../../tokens/stellar-asset-contract.mdx), y haces un conjunto de llamadas RPC desde tu aplicación frontend directamente a tus contratos inteligentes.
-
-Sin embargo, en algún momento probablemente te enfrentarás a limitaciones con este enfoque.
-
-1. Podrías necesitar hacer _demasiadas_ llamadas RPC. Imagina: tu aplicación muestra 20 NFTs de un usuario por página. Primera llamada RPC: obtener una lista de IDs de NFT para este usuario. Luego: 20 llamadas RPC simultáneas para obtener datos de cada NFT. Y posiblemente: para cada uno de esos, hacer solicitudes HTTP adicionales a buckets S3 o nodos IPFS para obtener datos de imagen, etc. Esto puede hacer que tu aplicación sea lenta, o incluso que un proveedor RPC te limite la tasa de peticiones.
-2. Quizás quieras mostrar datos _históricos_, como cada vez que un NFT cambió de propietario. Este tipo de datos vive _en la historia de la blockchain_, pero no es accesible mediante llamadas RPC a la versión más actualizada de un contrato específico. Eso sólo devolvería el propietario actual.
-
-Además, incluso alguna información que actualmente está disponible en [Horizon] requerirá servicios de indexación en el futuro, ya que Horizon será descontinuado.
-
-## ¿Qué es exactamente la indexación?
-
-La palabra "indexación" ha llegado a englobar una gran variedad de casos de uso. Lo que todos tienen en común es que procesan y estructuran datos de la blockchain. Pensemos en ello en el orden de lo que tú, un desarrollador o pequeño equipo, necesitarás:
-
-### 1. APIs listas para usar para datos comunes {#portfolio-apis}
-
-Esto es el tipo de cosas que podrías obtener de Horizon hoy, pero puede incluir más que eso. Por ejemplo, muchos servicios de indexación en esta categoría también proporcionan el tipo de datos "cada vez que un NFT cambia de propietario" mencionado arriba.
-
-Muchas aplicaciones necesitan este tipo de datos, y tienden a tener una forma estándar. Esto hace rentable para las empresas crear productos SaaS, ofreciendo acceso a API por un precio (a menudo con un nivel gratuito, apropiado para tu startup en fase inicial o proyecto de hackathon).
-
-En el negocio, a estos se les llama _APIs de Portafolio_. Empresas reconocidas que los ofrecen:
-
-- [Alchemy]: la opción más popular en Ethereum; ahora en conversaciones para expandir su servicio a Stellar, con lanzamiento previsto para la primera mitad de 2026.
-
-- [Allium]: actualmente desarrollando soporte para Stellar, lanzamiento en el primer trimestre de 2026
-
-- [OBSRVR]: una oferta nativa de Stellar creada internamente, que proporciona servicios RPC y [Obsrvr Gateway](https://www.withobsrvr.com/products/gateway), prometiendo "APIs potentes para la obtención de datos en tiempo real, procesamiento de transacciones e integración sencilla en sistemas existentes."
-
-- [Horizon]: como se mencionó anteriormente, Horizon pronto será dado de baja, pero por ahora es la única manera de obtener algunos de estos datos.
-
-### 2. Transmitir y transformar datos a una base de datos personalizada para la aplicación {#custom-transformations}
-
-No todas las aplicaciones tienen datos que encajen en una forma estándar. Probablemente la mayoría necesite transformaciones de datos personalizadas.
-
-Considera de nuevo el ejemplo del NFT. ¿No sería genial obtener todos los datos necesarios del NFT en _una_ solicitud, en lugar de N+1? Eso es lo que ofrece este estilo de indexación. Y aún mejor: puedes (a menudo) usar estas soluciones de indexación para agregar datos de múltiples fuentes. Si tu aplicación de NFT almacena información adicional en IPFS, también podrías consolidar todos esos datos fuera de la cadena en tu base de datos. Esto hace que tu aplicación sea mucho más rápida, ahorra solicitudes de red y RPC, y crea nuevas posibilidades de arquitectura.
-
-Opciones conocidas:
-
-- [The Graph]: una de las opciones pioneras y más populares en Ethereum en su momento. Ahora ofrecen tres productos principales:
-
-  1. [Subgraphs](https://thegraph.com/docs/en/subgraphs/developing/subgraphs/): su oferta principal y más famosa, que proporciona un [enfoque descentralizado](https://thegraph.com/docs/en/subgraphs/developing/publishing/publishing-a-subgraph/) para la transformación y hospedaje personalizado de datos. El uso de APIs GraphQL de The Graph popularizó GraphQL para toda esta categoría de indexación.
-  2. **Token API**, para el Caso de Uso de Indexación [#1](#portfolio-apis) descrito arriba
-  3. **Substreams**, para el Caso de Uso [#3](#analytics) descrito abajo
-
-  The Graph ofrece soporte para Stellar en Substreams, sin planes actuales de expandir el soporte para Subgraph o Token API a Stellar.
-
-- [Goldsky]: una de las opciones más populares actualmente en Ethereum para este caso de uso. Goldsky provee [dos productos principales](https://docs.goldsky.com/subgraph-vs-mirror):
-  1. **Subgraphs**: similares a los ofrecidos por The Graph, pero los datos viven en la infraestructura propia de Goldsky en lugar de una red descentralizada. Goldsky sólo ofrece esto para cadenas basadas en EVM, sin planes de ofrecer soporte Subgraph para Stellar.
-  2. **Mirror**, también llamado **Pipelines**: una herramienta altamente eficiente para Extraer, Transformar y Cargar (ETL) datos en tu propia base de datos. Goldsky Mirrors ya soporta Stellar; consulta [su documentación](https://docs.goldsky.com/chains/stellar).
-
-- [Mercury]: un equipo nativo de Stellar que ofrece soporte optimizado para Soroban (Smart Contract) a través de su producto [Retroshades](https://docs.mercurydata.app/retroshades/introduction-to-retroshades). Ten en cuenta que este soporte optimizado para Soroban viene con la limitación de _solo_ soportar Soroban. Mercury también ofrece [Mercury "Classic"](https://docs.mercurydata.app/mercury-classic/introduction), que da acceso a eventos de contratos y transacciones Stellar mediante una interfaz GraphQL, que podría ajustarse mejor al Caso de Uso de Indexación #1.
-
-- [SubQuery]: SDK descentralizado para Indexer, RPCs descentralizados y Apps de IA. Soporta más de 300 cadenas. Al igual que The Graph, usa un modelo descentralizado.
-
-- [OnFinality]: un gran actor en el ecosistema Polkadot, ahora expandiéndose a otras blockchains. OnFinality provee servicios de hospedaje de datos para tu lógica SubQuery. SubQuery es el _software_, OnFinality es la _infraestructura_, que hospeda 1. los datos crudos pretransformados de Stellar, 2. tu procesador Extract, Transform and Load (ETL) desarrollado con el SDK SubGraph y 3. tus datos transformados finales.
-
-- [Allium]: además de su oferta de APIs de Portafolio, Allium también está bajo contrato con SDF para crear herramientas tanto para el Caso de Uso de Indexación #2 (este) como para el Caso de Uso #3 (ver abajo), con fecha de lanzamiento objetivo en el primer trimestre de 2026.
-
-- [Space and Time]: un desafío con la mayoría de enfoques de indexación es la reintroducción de terceros confiables en lo que por lo demás es una Stack de software verificable y sin confianza. Space and Time pretende corregir esto con "Proof of Indexing" y "Proof of SQL", usando pruebas de conocimiento cero para ofrecer computación a prueba de manipulaciones para empresas y dapps. El soporte de Space and Time para Stellar [se lanzó](https://www.spaceandtime.io/blog/space-and-time-enables-new-sophisticated-financial-apps-for-the-stellar-ecosystem) en el cuarto trimestre de 2025.
-
-- [OBSRVR Flow]: "Datos estructurados de ledger y eventos de contrato directamente a tu app o warehouse—sin necesidad de ETL." Actualmente en beta privada.
-
-### 3. Analítica Big-Data con sabor a Blockchain {#analytics}
-
-Para inteligencia de negocio, cumplimiento, rastreo de operaciones sospechosas, seguimiento de métricas DeFi, análisis de flujo de transacciones, etc. Cuando tu empresa alcanza cierta escala, vale la pena pagar a Ingenieros de Datos para configurar canalizaciones ETL personalizadas y gestionar bases de datos/lagos de datos, y luego pagar a Analistas de Datos para responder preguntas sobre cómo interactúan las personas con tus sistemas.
-
-Las empresas que crean herramientas para el Caso de Uso de Indexación #2 arriba (The Graph, Goldsky, Allium, etc.) suelen tener también herramientas para el Caso de Uso #3.
-
-Aunque a menudo se les llama _indexación_, también puedes pensar en esta categoría como _analítica_. Consulta la [documentación de analítica](../analytics/README.mdx) para soluciones diseñadas a medida para este caso de uso.
-
-## Crear la tuya propia
-
-Si ninguno de los proveedores de indexación mencionados arriba satisface tus necesidades, también puedes crear la tuya propia. Comienza con este [tutorial sobre cómo crear tu propia canalización personalizada de ingestión de red](../../build/apps/ingest-sdk/overview.mdx). En el camino, usarás las siguientes herramientas y servicios:
-
-### [Galexie](./build-your-own/galexie/README.mdx)
-
-Galexie es una herramienta para adquirir metadatos de ledger de Stellar desde la red y exportarlos a almacenamiento externo, un lago de datos. Galexie es la base del Composable Data Pipeline (CDP) y sirve como el primer paso para extraer metadatos crudos del ledger de Stellar y hacerlos accesibles. Aprende más sobre los beneficios y aplicaciones del CDP en [esta publicación de blog](https://stellar.org/blog/developers/composable-data-platform).
-
-**Por qué usarlo:**
-
-- Quieres mantener un lago de datos de metadatos de ledger precomputados para ledgers históricos y actualmente cerrados de la red.
-
-### [Ingest SDK](./build-your-own/ingest-sdk/README.mdx)
-
-Un conjunto de paquetes Golang que pueden usarse dentro de una aplicación como un modelo de dominio programático para interactuar con la red Stellar.
-
-**Por qué usarlo:**
-
-- Quieres desarrollar rápidamente aplicaciones en Golang que puedan adquirir y analizar metadatos de ledger y entradas del ledger de la red Stellar.
-- Quieres una experiencia de desarrollador de aplicaciones intuitiva, segura en tiempo de compilación y con tipado seguro.
-- Quieres acceder programáticamente a Historias de Archivos para recuperar entradas de ledger.
-
-### [Processors](./build-your-own/processors/README.mdx)
-
-Un conjunto de paquetes Go que te ayudan a analizar datos de la blockchain de Stellar.
-
-[Horizon]: ../apis/horizon/README.mdx
-[Allium]: https://www.allium.so/
-[Alchemy]: https://www.alchemy.com/
-[Goldsky]: https://goldsky.com/
-[OBSRVR]: https://www.withobsrvr.com/
-[The Graph]: https://thegraph.com/docs/en/about/
-[Mercury]: https://docs.mercurydata.app/
-[SubQuery]: https://subquery.network/
-[OnFinality]: https://onfinality.io/
-[Space and Time]: https://www.spaceandtime.io/
-[OBSRVR Flow]: https://www.withobsrvr.com/products/flow
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/README.mdx
deleted file mode 100644
index 4168e7e723..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/README.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Crear tu propio
-sidebar_position: 0
----
-
-Si ninguno de los proveedores de indexación mencionados [en la descripción general](../README.mdx) satisface tus necesidades, también puedes crear el tuyo propio. Comienza con este [tutorial sobre cómo crear tu propia canalización personalizada de ingestión de red](../../../build/apps/ingest-sdk/overview.mdx). Durante el proceso, usarás las siguientes herramientas y servicios:
-
-## [Galexie](./galexie/README.mdx)
-
-Galexie es una herramienta para adquirir metadatos del ledger Stellar de la red y exportarlos a un almacenamiento externo, un lago de datos. Galexie es la base de la Composable Data Pipeline (CDP) y sirve como el primer paso para extraer metadatos del ledger de Stellar crudos y ponerlos al alcance. Aprende más sobre los beneficios y aplicaciones de la CDP en [esta entrada de blog](https://stellar.org/blog/developers/composable-data-platform).
-
-**¿Por qué usarlo:**
-
-- Quieres mantener un lago de datos de metadatos del ledger precomputados para ledgers históricos y actualmente cerrados de la red.
-
-## [Ingestar SDK](./ingest-sdk/README.mdx)
-
-Un conjunto de paquetes de Golang que se pueden utilizar dentro de la aplicación como un modelo de dominio programático para interactuar con la red Stellar.
-
-**¿Por qué usarlo:**
-
-- Quieres un desarrollo rápido de aplicaciones en Golang que puedan adquirir y analizar metadatos del ledger y entradas de ledger de la red Stellar.
-- Quieres una experiencia de desarrollo de aplicaciones intuitiva, segura en tiempo de compilación y con tipos.
-- Quieres acceder programáticamente a los Archivos de Historial para recuperar las entradas del libro mayor.
-
-## [Procesadores](./processors/README.mdx)
-
-Un conjunto de paquetes Go que te ayudan a analizar los datos de la cadena de bloques Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/README.mdx
deleted file mode 100644
index ca798600e8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/README.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Galexie
-sidebar_position: 0
----
-
-## ¿Qué es Galexie?
-
-Galexie es una herramienta para extraer, procesar y exportar metadatos del ledger Stellar a almacenamiento externo, y crear un lago de datos con metadatos de ledger preprocesados. Galexie es la base de la Composable Data Pipeline (CDP) y sirve como el primer paso para extraer metadatos del ledger Stellar en su forma cruda y hacerlos accesibles. Aprende más sobre los beneficios y aplicaciones de la CDP en este [blog](https://stellar.org/blog/developers/composable-data-platform).
-
-## ¿Cuáles son las características clave de Galexie?
-
-Galexie está diseñada para hacer la exportación de metadatos del ledger de manera fluida y eficiente a través de una interfaz simple y amigable. Sus características clave incluyen:
-
-- Exportar metadatos del ledger Stellar a almacenamiento en la nube
-- Configurable para exportar un rango específico de ledgers o transmitir continuamente nuevos ledgers a medida que se crean en la red Stellar
-- Exportar metadatos del ledger en XDR, que es el formato nativo de Stellar Core.
-- Comprimir datos antes de la exportación para optimizar la eficiencia del almacenamiento en el lago de datos.
-
-![](/assets/galexie/galexie-architecture.png)
-
-## ¿Por qué formarnos en formato XDR?
-
-Exportar datos en XDR—el formato nativo de Stellar Core—permite a Galexie preservar todos los metadatos de las transacciones, asegurando la integridad de los datos mientras mantiene el almacenamiento eficiente. El formato XDR mantiene la compatibilidad con todos los componentes de Stellar, proporcionando una sólida base para aplicaciones que requieren acceso constante a datos históricos. Consulta la documentación de [XDR](../../../../learn/fundamentals/data-format/xdr.mdx) para obtener más información sobre este formato.
-
-## ¿Por qué ejecutar Galexie?
-
-Galexie te permite hacer una copia de los metadatos del ledger Stellar sobre los que tienes control total. Galexie puede sincronizar continuamente tu lago de datos con los últimos datos del ledger, liberándote de la tediosa ingestión de datos y permitiéndote concentrarte en construir aplicaciones personalizadas que consuman y analicen los datos exportados.
-
-## ¿Qué puedes hacer con el lago de datos creado por Galexie?
-
-Una vez que los datos están almacenados en la nube, se vuelven fácilmente accesibles para su integración con herramientas modernas de procesamiento de datos y análisis, habilitando diversos flujos de trabajo y perspectivas.
-
-Los datos de ledger preprocesados exportados por Galexie pueden ser utilizados en diversas aplicaciones, tales como:
-
-- Herramientas de análisis: Analiza tendencias a lo largo del tiempo.
-- Aplicaciones de auditoría: Recupera datos de transacciones históricas para auditoría y cumplimiento.
-- Sistemas de monitoreo: Crea herramientas para rastrear métricas de la red.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/README.mdx
deleted file mode 100644
index 0894a84244..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/README.mdx
+++ /dev/null
@@ -1,6 +0,0 @@
----
-title: Guía del Administrador
-sidebar_position: 15
----
-
-Esta guía proporciona instrucciones paso a paso sobre la instalación y ejecución de Galexie.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/_category_.json
deleted file mode 100644
index 9e3a55f459..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/configuring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/configuring.mdx
deleted file mode 100644
index 9c06bb057a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/configuring.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Configurando
-sidebar_position: 20
----
-
-# Configurando
-
-## Pasos para configurar Galexie
-
-### Configuraciones Clave Incluyen
-
-#### Servicio de Almacenamiento en la Nube
-
-Especifica el servicio de almacenamiento en la nube que se usará para exportar los metadatos del libro mayor. Actualmente solo se admiten `GCS` y `S3`
-
-```toml
-type = "GCS"
-```
-
-#### Depósito de Almacenamiento en la Nube
-
-Especifica el bucket de almacenamiento en la nube donde Galexie exportará los datos del libro mayor de Stellar. Actualiza `destination_bucket_path` con la ruta completa de tu bucket, incluyendo subrutas si corresponde.
-
-```toml
-destination_bucket_path = "stellar-network-data/testnet"
-```
-
-#### Red Stellar
-
-Establece la red de Stellar que se utilizará para crear el lago de datos.
-
-```toml
-network = "testnet"
-```
-
-#### Organización de Datos (Opcional)
-
-Configura cómo se organiza la información exportada en el bucket de almacenamiento. El ejemplo siguiente añade 1 ledger por archivo y los organiza en un directorio de 64000 archivos.
-
-```toml
-# Number of ledgers stored in each file
-ledgers_per_file = 1
-
-# Number of files per partition/directory
-files_per_partition = 64000
-```
-
-#### Usar una Configuración Core Personalizada (Opcional)
-
-Puedes especificar un archivo personalizado `core.cfg` en el archivo `config.toml` de Galexie que anulará los parámetros core predeterminados usados con la Red Stellar especificada en el parámetro `network`.
-
-Copia un archivo `core.cfg` existente como el `captive-core-pubnet.cfg` proporcionado [aquí](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/configs/captive-core-pubnet.cfg) y añade lo siguiente a tu `config.toml`
-
-```toml
-captive_core_toml_path = "my-captive-core.cfg"
-```
-
-- Consulta [Cómo Elegir Tu Quorum Set](../../../../../validators/admin-guide/configuring.mdx#choosing-your-quorum-set) para más información sobre la configuración de quorum set en `core.cfg`.
-- Una lista de parámetros core personalizables se encuentra [aquí](https://github.com/stellar/stellar-core/blob/master/src/main/Config.h).
-
-El `core.cfg` predeterminado que usa Galexie habilitará los siguientes parámetros core:
-
-- **BACKFILL_RESTORE_META -** los metadatos del ledger se completarán con cambios de LedgerEntryChange de tipo RESTAURAR para versiones de protocolo anteriores a la 23.
-- **ENABLE_SOROBAN_DIAGNOSTIC_EVENTS -** se generarán eventos diagnósticos adicionales de Soroban que no forman parte del protocolo mientras se aplican transacciones de Soroban.
-- **EMIT_SOROBAN_TRANSACTION_META_EXT_V1 -** se emitirán los datos de la extensión V1 de Soroban.
-- **EMIT_LEDGER_CLOSE_META_EXT_V1 -** se emitirán los datos de la extensión V1 de los metadatos de cierre del ledger.
-- **EMIT_CLASSIC_EVENTS -** se habilitarán y emitirán eventos clásicos para protocolo `>= 23`.
-- **BACKFILL_STELLAR_ASSET_EVENTS -** se habilitarán y emitirán eventos clásicos para protocolo `<= 22`. Este parámetro también requiere que `EMIT_CLASSIC_EVENTS` esté habilitado.
-
-:::warning
-
-Cuando proporcionas un archivo de configuración core personalizado, reemplaza completamente la configuración core predeterminada de Galexie. Esto significa que debes establecer explícitamente cualquier parámetro que desees habilitar, incluyendo los que están habilitados por defecto en Galexie. Cualquier parámetro que no esté listado en tu configuración personalizada se establecerá en false.
-
-:::
-
-### Ejecutar Galexie en una Instancia
-
-#### 1. Copiar la Configuración de Ejemplo
-
-Comienza con el archivo de ejemplo proporcionado, [`config.example.toml`](https://github.com/stellar/stellar-galexie/blob/main/config/config.example.toml).
-
-#### 2. Renombrar y Actualizar la Configuración
-
-Renombra el archivo a `config.toml` y ajusta la configuración según sea necesario.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.mdx
deleted file mode 100644
index 26ac0368b8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/full-history-exporting.mdx
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: Exportación de Historial Completo
-sidebar_position: 60
----
-
-Esta página describe las prácticas recomendadas para usar Galexie y crear un data lake con el historial completo de los metadatos del ledger.
-
-## ¿Por qué Exportar el Historial Completo?
-
-Exportar el historial completo de los metadatos del ledger de Stellar proporciona un data lake completo de todo lo que ha ocurrido on-chain. Esto facilita y agiliza la recuperación de datos en cualquier punto de la historia de la red.
-
-Esto permite:
-
-- **Analítica** - ejecutar análisis de tendencias históricas con `stellar-etl`
-- **RPC de Historial Completo** - backend del data lake que suministra metadatos del ledger a instancias RPC para habilitar el acceso a datos del historial completo
-- **Datos en Tiempo Real** - acceso a datos en tiempo real sobre el acceso completo a datos históricos
-
-## Costos y Requisitos de Almacenamiento
-
-Las estimaciones están basadas en los costos de GCP Compute Engine y Google Cloud Storage
-
-- **Costo Total** ~= $1,100 USD
-  - Costos de Cómputo ~= $500 USD
-  - Costos de Operaciones Clase A de GCS (escrituras) ~= $600 USD
-- **Tamaño Total de Almacenamiento** ~= 3 TB
-
-## Estrategia de Exportación
-
-La mejor forma de exportar el historial completo con Galexie es ejecutando múltiples instancias individuales de Galexie en paralelo. Como referencia, se estima que se tarda aproximadamente 150 días en exportar el historial completo usando una sola instancia de Galexie. Ejecutar en paralelo con 40-50 instancias de Galexie toma aproximadamente 4-5 días.
-
-1. Asegúrate de haber configurado un sistema de almacenamiento y contar con el hardware adecuado según lo definido en los [Requisitos Previos](./prerequisites.mdx) de Galexie
-2. Determina cuántas instancias paralelas de Galexie quieres ejecutar
-3. Recuerda pasar rangos de ledger no solapados a cada una de tus instancias de Galexie
-
-Nota que los ledgers anteriores en la historia son más pequeños y se exportan más rápido que los ledgers más recientes. Esta diferencia de desempeño se hace evidente alrededor del ledger 30,000,000. Debido a esta diferencia de desempeño, generalmente es mejor asignar más instancias de Galexie para los ledgers más recientes.
-
-### Cómo se Ve Esto en la Práctica
-
-Supongamos que hay 50,000,000 de ledgers que Galexie necesita exportar.
-
-- Para 50 instancias, la división podría ser:
-  - 15 instancias para procesar desde genesis hasta 29,999,999
-  - 35 instancias para procesar de 30,000,000 a 50,000,000
-
-Cada instancia seguirá las mismas instrucciones de [Ejecutar Galexie](./running.mdx)
-
-```
-galexie append --start <start_ledger> --end <end_ledger>
-```
-
-Donde se ejecutaría tu primera instancia
-
-```
-galexie append --start 2 --end 1999999
-```
-
-La segunda se ejecutaría
-
-```
-galexie append --start 2000000 --end 3999999
-```
-
-y así sucesivamente
-
-### Métodos para ejecutar múltiples instancias de Galexie
-
-Existen diferentes formas de iniciar múltiples instancias de Galexie que pueden variar según tu proveedor de la nube o hardware local.
-
-#### GCP Batch
-
-Dentro de GCP puedes usar [Batch](https://cloud.google.com/batch/docs/get-started), que acepta un archivo JSON o YAML de `job` que puede parametrizar los rangos de inicio y fin del ledger para cada instancia de Galexie
-
-Ejemplo de archivo YAML para job de GCP Batch
-
-```yaml
-job:
-  taskGroups:
-  - taskSpec:
-      computeResource:
-        cpuMilli: 2000
-        memoryMib: 8000
-      maxRetryCount: 1
-      container:
-        imageUri: "stellar/stellar-galexie:23.0.0"
-        entrypoint: "galexie"
-        commands: ["append", "--start", "${START}", "--end", "#{END}"]
-      tasks:
-      # It is possible to use the GCP batch index instead of manually naming each task
-      - name: "galexie-1"
-        environments:
-          START: "2"
-          END: "1999999"
-      - name: "galexie-2"
-        environments:
-          START: "2000000"
-          END: "3999999"
-      ...
-
-    requireHostsFile: true
-    requireTaskHostsFile: true
-  allocationPolicy:
-    instances:
-    - policy:
-        machineType: "e2-standard-2"
-        disks:
-        - newDisk:
-            type: "pd-standard"
-            sizeGb: 100
-          mountPoint: "/mnt/shared"
-```
-
-#### Instancias de cómputo en GCP
-
-Puedes iniciar manualmente múltiples instancias individuales de cómputo
-
-Ejemplo de instancia de cómputo en GCP
-
-```yaml
-#container-declaration-0.yaml
-spec:
-  restartPolicy: Always
-  containers:
-    - name: galexie
-      image: stellar/stellar-galexie:23.0.0
-      command:
-        - galexie
-      args:
-        - append
-        - --start
-        - "2"
-        - --end
-        - "1999999"
-      securityContext:
-        privileged: true
-```
-
-Luego crea la instancia ejecutando el siguiente comando `gcloud`
-
-```sh
-gcloud compute instances create "galexie-0" \
-  --zone=us-central1-a \
-  --machine-type=e2-standard-2 \
-  --image-family=cos-stable \
-  --image-project=cos-cloud \
-  --boot-disk-size=100GB \
-  --boot-disk-type=pd-standard \
-  --boot-disk-device-name="galexie-0" \
-  --tags=http-server,https-server \
-  --scopes=https://www.googleapis.com/auth/cloud-platform \
-  --service-account=<service-account> \
-  --metadata-from-file=gce-container-declaration="container-declaration-0.yaml"
-```
-
-Repite el proceso para tantas instancias paralelas de Galexie como desees
-
-#### Instancias locales de Galexie
-
-Puedes ejecutar múltiples instancias de Galexie localmente con un ejecutable de Galexie desarrollado localmente
-
-```sh
-./galexie append --start 2 --end 1999999 & \
-./galexie append --start 2000000 --end 3999999 & \
-./galexie append --start 4000000 --end 5999999 &
-
-...
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/installing.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
deleted file mode 100644
index b1795bc362..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/installing.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: Instalando
-sidebar_position: 30
----
-
-# Instalando
-
-## Kubernetes
-
-Para instalar Galexie en un clúster de Kubernetes, sigue estos pasos:
-
-- Ejecuta `helm repo add stellar https://helm.stellar.org/charts`
-- Ejecuta `helm install <RELEASE_NAME> stellar/galexie --set datastore.params.path=<FULL_PATH_TO_GALEXIE_OBJECTS>`
-
-La configuración adicional se puede establecer con las opciones `--set` o utilizando un [archivo de valores helm](https://helm.sh/docs/chart_template_guide/values_files/) con el chart.
-
-## Instalar el contenedor en un host
-
-Para descargar la imagen del contenedor Galexie desde el [registro Stellar Docker Hub](https://hub.docker.com/r/stellar/stellar-galexie) usa el siguiente comando docker o un comando similar compatible con OCI:
-
-```shell
-docker pull stellar/stellar-galexie
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
deleted file mode 100644
index 0bed15bdd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/monitoring.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Monitoreo
-sidebar_position: 50
----
-
-# Monitoreo
-
-### Métricas
-
-Galexie publica métricas a través de un punto final administrativo basado en HTTP, lo que facilita la supervisión de su rendimiento. Los datos se exponen en formato Prometheus, lo que permite una fácil integración con los sistemas de monitoreo y alerta existentes.
-
-El puerto de administración donde se sirven estas métricas puede configurarse estableciendo la variable `admin_port`. Por defecto, el `admin_port` está configurado en `6061`
-
-```toml
-# Admin port configuration
-# Specifies the port for hosting the HTTP service that publishes metrics.
-admin_port = 6061
-```
-
-Con esta configuración, la URL para acceder al punto final de métricas será:
-
-```
-http://<host>:6061/metrics
-```
-
-Galexie emite varias métricas específicas de la aplicación para ayudar a rastrear el proceso de exportación:
-
-- `galexie_last_exported_ledger`: El número de secuencia del ledger exportado más recientemente.
-- `galexie_uploader_put_duration_seconds`: El tiempo tomado para cargar objetos al lago de datos.
-- `galexie_uploader_object_size_bytes`: Tamaños comprimidos y no comprimidos de los objetos que se están subiendo.
-- `galexie_upload_queue_length`: Número de objetos actualmente en cola y esperando para ser subidos.
-
-Además de estas métricas específicas de la aplicación, Galexie también exporta métricas del sistema (por ejemplo, CPU, memoria, descriptores de archivo abiertos) y métricas de ingestión de Stellar Core como `galexie_ingest_ledger_fetch_duration_seconds`
-
-Utiliza estas métricas para crear consultas que monitoreen el rendimiento y el proceso de exportación de Galexie. Aquí hay varias ejemplos de consultas útiles:
-
-- Tiempos de Exportación: Consulta `galexie_uploader_put_duration_seconds` para monitorear los tiempos de carga promedio.
-- Longitud de la Cola: Utiliza `galexie_upload_queue_length` para ver el número de objetos esperando ser subidos.
-- Último Ledger Exportado: Realiza un seguimiento de `galexie_last_exported_ledger` para asegurarte de que las exportaciones de ledger estén actualizadas.
-
-Para un inicio rápido, descarga nuestro tablero preconstruido de Grafana para Galexie [aquí](https://grafana.com/grafana/dashboards/22285-stellar-galexie/). Este tablero proporciona consultas y visualizaciones preconfiguradas para ayudarte a monitorear la salud de Galexie. Puedes personalizarlo para adaptarlo a tus necesidades específicas.
-
-### Registro
-
-Galexie emite logs a stdout y genera una línea de log para cada objeto que se exporta para ayudar a monitorear el progreso.
-
-Ejemplo de logs:
-
-```
-INFO[2024-11-07T17:40:37.795-08:00] Uploading: FFFFFF37--200-299/FFFFFF37--200.xdr.zstd  pid=98734 service=galexie
-INFO[2024-11-07T17:40:37.892-08:00] Uploaded FFFFFF37--200-299/FFFFFF37--200.xdr.zstd successfully  pid=98734 service=galexie
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
deleted file mode 100644
index b58be69673..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/prerequisites.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Requisitos previos
-sidebar_position: 10
----
-
-# Requisitos previos
-
-## 1. Cuenta de la Plataforma en la Nube
-
-Galexie exporta los metadatos del ledger de Stellar a Google Cloud Storage (GCS) o Amazon Simple Storage Service (S3). Necesitarás la cuenta y las credenciales correspondientes para el servicio de almacenamiento en la nube que elijas usar.
-
-### Cuenta de Google Cloud Platform (GCP) para GCS
-
-- Permisos para crear un nuevo bucket de GCS, o
-- Acceso a un bucket existente con permisos de lectura/escritura.
-
-### Cuenta de Amazon Web Services (AWS) para S3
-
-- Permisos para crear un nuevo bucket S3, o
-- Acceso a un bucket existente con permisos de lectura y escritura.
-
-## 2. Tiempo de ejecución de contenedores (Recomendado)
-
-### Kubernetes
-
-- Kubernetes 1.19+
-
-### Ejecutar el contenedor Galexie en una Instancia
-
-- Instancia como AWS EC2 o VM de GCP
-- Cualquier máquina host con un tiempo de ejecución de contenedores compatible con OCI instalado como Docker ([Guía de instalación de Docker](https://docs.docker.com/engine/install/)).
-
-> **_NOTA:_** Aunque es posible instalar Galexie de forma nativa (sin un tiempo de ejecución de contenedores), esto requiere la gestión manual de dependencias y se recomienda solo para usuarios avanzados.
-
-## Requisitos de Hardware
-
-Los requisitos mínimos de hardware para ejecutar Galexie son:\
-**RAM**: 16 GB\
-**CPU**: 4 vCPUs\
-**Disco persistente**: 100 GB con al menos 5K IOPS
-
-### Exportación Completa de Historial
-
-Por favor, consulta la guía de [Exportación completa de historial](./full-history-exporting.mdx) para más información.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/running.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/running.mdx
deleted file mode 100644
index 7c0aea8397..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/running.mdx
+++ /dev/null
@@ -1,223 +0,0 @@
----
-title: Ejecutando
-sidebar_position: 40
----
-
-# Ejecutando
-
-Los comandos y argumentos descritos en este documento pueden configurarse en el helm chart así como ejecutarse en una instancia según se describe a continuación. El helm chart maneja internamente la ruta del archivo de configuración para el chart. El argumento `--config-file` no debe añadirse a la variable de argumentos en el helm chart.
-
-Con la imagen Docker disponible y el archivo de configuración preparado, ya estás listo para ejecutar Galexie y comenzar a exportar datos del ledger Stellar al depósito de almacenamiento.
-
-## Uso de la Línea de Comandos
-
-### Comando Append
-
-Esta es la forma principal de ejecutar Galexie. El comando `append` opera en dos modos distintos:
-
-- En modo continuo/infinito, comienza a exportar desde el ledger de inicio especificado y exporta continuamente nuevos ledgers que aparecen en la red hasta que el proceso sea interrumpido.
-- En modo de rango fijo, exporta el rango especificado de ledgers y sale cuando ha terminado.
-
-Sintaxis:
-
-```shell
-stellar-galexie append --start <start_ledger> [--end <end_ledger>] [--config-file <config_file>]
-```
-
-Argumentos:
-
-`--start <start_ledger>` (requerido)
-
-- El número de secuencia del ledger de inicio del rango que se está exportando.
-
-`--end <end_ledger>` (opcional)
-
-- El número de secuencia del ledger de fin del rango que se está exportando. Si no se especifica o se establece en 0, el exportador exportará continuamente nuevos ledgers a medida que aparezcan en la red.
-
-`--config-file <config_file_path>` (opcional)
-
-- La ruta al archivo de configuración. Si no se especifica, la aplicación buscará un archivo llamado `config.toml` en el directorio actual.
-
-Ejemplo de uso:
-
-```shell
-docker run --platform linux/amd64 -d \
--v "$HOME/.config/gcloud/application_default_credentials.json":/.config/gcp/credentials.json:ro \
--e GOOGLE_APPLICATION_CREDENTIALS=/.config/gcp/credentials.json \
--v ${PWD}/config.toml:/config.toml \
-stellar/stellar-galexie \
-append --start 350000 --end 450000 --config-file config.toml
-```
-
-`--platform linux/amd64`
-
-- Especifica la arquitectura de la plataforma (ajusta si es necesario para tu sistema).
-
-`-v` Monta volúmenes para mapear tus credenciales locales de GCP y el archivo config.toml en el contenedor:
-
-- `$HOME/.config/gcloud/application_default_credentials.json`: Tu archivo de credenciales locales de GCP.
-- `${PWD}/config.toml`: Tu archivo de configuración local.
-
-`-e GOOGLE_APPLICATION_CREDENTIALS=/.config/gcp/credentials.json`
-
-- Establece la variable de entorno para credenciales dentro del contenedor.
-- Por favor, usa el equivalente de AWS si utilizas S3 como tu servicio de almacenamiento en la nube.
-
-`stellar/stellar-galexie`
-
-- El nombre de la imagen de Docker.
-
-#### Integridad de los Datos y Reanudación:
-
-El comando append mantiene una estricta integridad secuencial dentro de cada sesión de exportación. Si se interrumpe y luego se reinicia con el mismo rango, automáticamente reanuda desde donde se detuvo antes de la interrupción, asegurando que no se pierda ningún ledger dentro de una sesión.
-
-### Comando Scan-and-fill
-
-El comando `scan-and-fill` es útil en casos donde hay huecos en los ledgers exportados en el lago de datos. El comando funciona escaneando todos los ledgers en el rango especificado, identificando los ledgers faltantes y exportando solo los ledgers que faltan mientras omite los ledgers existentes en el lago de datos.
-
-El comando append asegura que no haya huecos en el rango exportado. Sin embargo, los huecos pueden ocurrir en el lago de datos debido a ciertos eventos, a menudo debido a intervención del usuario, como:
-
-- Eliminación manual de ledgers del lago de datos. Por ejemplo, eliminar los ledgers 80-90 del rango 1-100.
-- Ejecutando rangos de exportación no contiguos. Por ejemplo, exportando los rangos 1-50 y 60-100, dejando un hueco entre 50-60. En este caso, ejecutar el comando `append` con el rango 1-500 hace que Galexie reanude la exportación desde 101, sin llenar el hueco.
-
-Sintaxis:
-
-```shell
-stellar-galexie scan-and-fill --start <start_ledger> --end <end_ledger> [--config-file <config_file>]
-```
-
-Argumentos:
-
-`--start <start_ledger>` (requerido)
-
-- El número de secuencia del ledger de inicio del rango que se está exportando.
-
-`--end <end_ledger>` (requerido)
-
-- El número de secuencia del ledger de fin del rango que se está exportando.
-
-`--config-file <config_file_path>` (opcional):
-
-- La ruta al archivo de configuración. Si no se especifica, el exportador buscará un archivo llamado “config.toml” en el directorio actual.
-
-Ejemplo de uso:
-
-```shell
-docker run --platform linux/amd64 -d \
--v "$HOME/.config/gcloud/application_default_credentials.json":/.config/gcp/credentials.json:ro \
--e GOOGLE_APPLICATION_CREDENTIALS=/.config/gcp/credentials.json \
--v ${PWD}/config.toml:/config.toml \
-stellar/stellar-galexie \
-scan-and-fill --start 64000 --end 68000 --config-file config.toml
-```
-
-### Reemplazar comando
-
-El comando `replace` es una nueva incorporación en Galexie v24.1.0 que simplifica la reexportación de ledgers que fueron procesados previamente.
-
-A diferencia de `append` o `scan-and-fill`, que omiten los archivos existentes, `replace` sobrescribirá los archivos existentes dentro de un rango especificado.
-
-Se utiliza principalmente cuando Stellar Core comienza a emitir metadatos nuevos o actualizados para ledgers procesados anteriormente (por ejemplo, la introducción de [CAP-0067](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md) Stellar Events). Esto permite a los operadores reexportar los ledgers afectados para asegurar que el data lake contenga los metadatos más recientes y completos.
-
-Sintaxis:
-
-```shell
-stellar-galexie replace --start <start_ledger> --end <end_ledger> [--config-file <config_file>]
-```
-
-Argumentos:
-
-`--start <start_ledger>` (obligatorio)
-
-- El número de secuencia inicial del ledger en el rango que se está exportando.
-
-`--end <end_ledger>` (obligatorio)
-
-- El número de secuencia final del ledger en el rango que se está exportando.
-
-`--config-file <config_file_path>` (opcional):
-
-- La ruta al archivo de configuración. Si no se especifica, el exportador buscará un archivo llamado “config.toml” en el directorio actual.
-
-Ejemplo de uso:
-
-```shell
-docker run --platform linux/amd64 -d \
--v "$HOME/.config/gcloud/application_default_credentials.json":/.config/gcp/credentials.json:ro \
--e GOOGLE_APPLICATION_CREDENTIALS=/.config/gcp/credentials.json \
--v ${PWD}/config.toml:/config.toml \
-stellar/stellar-galexie \
-replace --start 64000 --end 68000 --config-file config.toml
-```
-
-### Comando detect-gaps
-
-El comando `detect-gaps` es una nueva incorporación en Galexie v25.0.0. Realiza una auditoría de solo lectura del data lake y reporta cualquier secuencia faltante en el ledger ("agujeros") dentro de un rango dado.
-
-Durante la operación diaria normal, el comando `append` mantiene una integridad secuencial estricta. Sin embargo, los operadores suelen paralelizar las exportaciones completas de historial inicial al dividir el rango total del ledger en múltiples subrangos y ejecutar varias instancias de Galexie simultáneamente. Rangos mal configurados, trabajos fallidos o intervención manual pueden dejar huecos (archivos faltantes) en el almacén de datos.
-
-El comando `detect-gaps` está diseñado para verificar la integridad de un data lake recién creado tras una exportación completa inicial o como auditoría periódica. Este comando no exporta ni modifica ningún dato. Solo escanea el almacén de datos existente y reporta los rangos faltantes.
-
-Sintaxis:
-
-```shell
-stellar-galexie detect-gaps --start <start_ledger> \
---end <end_ledger> \
-[--config-file <config_file>] \
-[--output-file <output_file>]
-```
-
-Argumentos:
-
-`--start <start_ledger>` (requerido)
-
-Número de secuencia inicial del ledger del rango que se escaneará en busca de agujeros.
-
-`--end <end_ledger>` (requerido)
-
-Número de secuencia final del ledger del rango que se escaneará en busca de agujeros.
-
-`--config-file <config_file_path>` (opcional)
-
-La ruta al archivo de configuración. Si no se especifica, la aplicación busca un archivo llamado "config.toml" en el directorio actual.
-
-`--output-file <output_file_path>` (opcional)
-
-Si se proporciona, el informe de agujeros se escribe en formato JSON en este archivo. Si se omite, el informe JSON se escribe en la salida estándar.
-
-Ejemplo de uso:
-
-```shell
-docker run --platform linux/amd64 -d \
--v "$HOME/.config/gcloud/application_default_credentials.json":/.config/gcp/credentials.json:ro \
--e GOOGLE_APPLICATION_CREDENTIALS=/.config/gcp/credentials.json \
--v ${PWD}/config.toml:/config.toml \
--v ${PWD}:/reports \
-stellar/stellar-galexie \
-detect-gaps \
---start 2 \
---end 200000 \
---config-file config.toml \
---output-file gaps_report.json
-```
-
-Ejemplo de salida:
-
-```shell
-{
-  "scan_from": 2,
-  "scan_to": 200000,
-  "duration_seconds": 3.42ms,
-  "report": {
-    "gaps": [
-      { "start": 144320, "end": 144383 },
-      { "start": 180000, "end": 180063 }
-    ],
-    "total_ledgers_found": 199871,
-    "total_ledgers_missing": 128,
-    "min_sequence_found": 2,
-    "max_sequence_found": 200000
-  }
-}
-
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/setup.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
deleted file mode 100644
index dd1ab4296c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/admin_guide/setup.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Configurar
-sidebar_position: 10
----
-
-# Configurar
-
-Galexie se ejecuta como un publicador y escribe archivos en buckets, por lo que necesita tener asignados los permisos correctos de cuenta en el bucket para permitir escrituras. Para las aplicaciones cliente que serán consumidoras de archivos en el bucket, se necesitará un conjunto menor de permisos de cuenta para permitir únicamente la actividad de lectura.
-
-## Google Cloud Platform (GCP) para GCS
-
-### Bucket de Google Cloud Storage (GCS)
-
-Si ya tienes un bucket GCS listo para que Galexie envíe datos, puedes omitir esta sección. Si no, sigue estos pasos:
-
-1. Visita la sección de Almacenamiento de la consola de GCP (https://console.cloud.google.com/storage) y crea un nuevo bucket.
-2. Elige un nombre descriptivo para el bucket, como `stellar-ledger-data`. Consulta la [Guía de Nomenclatura de Buckets de Google Cloud Storage](https://cloud.google.com/storage/docs/buckets#naming) para las convenciones de nomenclatura de buckets. Anota el nombre del bucket, lo necesitarás más tarde durante el proceso de configuración.
-
-### Autenticación de Google Cloud Platform (GCP)
-
-#### Clúster de Google Kubernetes Engine
-
-Cuando ejecutes Galexie dentro de un clúster GKE, sigue la documentación de Google Cloud sobre la [identidad de carga de trabajo](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) para asegurarte de que Galexie tenga el acceso correcto al bucket.
-
-#### VM de GCP
-
-1. [Crear una Cuenta de Servicio](https://docs.cloud.google.com/iam/docs/service-accounts-create)
-2. Usa esa Cuenta de Servicio al crear la VM de GCP.
-3. Asegúrate de que la Cuenta de Servicio tenga el acceso correcto al bucket.
-
-#### Credenciales (No Recomendado)
-
-Para usar credenciales estáticas, encuentra la ruta de autenticación que mejor funcione en el entorno de Galexie y sigue la documentación de Google Cloud sobre [crear credenciales](https://developers.google.com/workspace/guides/create-credentials), asegurándote de que el principal de las credenciales tenga acceso al bucket correcto.
-
-#### Permisos del Rol IAM
-
-Al usar IAM de GCP para autenticar a Galexie para acceder a un bucket, se requieren los siguientes permisos:
-
-- storage.buckets.get
-- storage.buckets.list
-- storage.multipartUploads.abort
-- storage.multipartUploads.create
-- storage.multipartUploads.list
-- storage.multipartUploads.listParts
-- storage.objects.create
-- storage.objects.delete
-- storage.objects.get
-- storage.objects.list
-- storage.objects.restore
-- storage.objects.update
-
-## Amazon Web Services (AWS) para S3
-
-### Bucket de Amazon Simple Storage Service (S3)
-
-Si ya tienes un bucket S3 listo para que Galexie envíe datos, puedes omitir esta sección. Si no es así, sigue estos pasos:
-
-1. Visita la sección de Storage de la consola de AWS (https://console.aws.amazon.com/s3/) y crea un nuevo bucket.
-2. Elige un nombre descriptivo para el bucket, como `stellar-ledger-data`. Consulta las [reglas generales para nombrar buckets en S3](https://cloud.google.com/storage/docs/buckets#naming). Anota el nombre del bucket, lo necesitarás más adelante durante el proceso de configuración.
-
-### Autenticación de Amazon Web Services (AWS)
-
-#### Clúster EKS
-
-Cuando ejecutes Galexie dentro de un clúster EKS, sigue la documentación de AWS sobre [roles IAM para cuentas de servicio](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html) o [identidad de pod](https://docs.aws.amazon.com/eks/latest/userguide/pod-identities.html).
-
-#### AWS EC2
-
-1. [Crear un Rol IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions_create-policies.html)
-2. Usa ese rol en un [perfil de instancia](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html).
-3. Usa ese perfil de instancia para la creación de la instancia EC2.
-4. Asegúrate de que el perfil de instancia tenga el acceso correcto al bucket.
-
-#### Credenciales (No Recomendado)
-
-Para usar credenciales estáticas, [crea un usuario IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started-workloads.html) para Galexie asegurándote de que el principal de las credenciales tenga acceso al bucket correcto y genera las credenciales de seguridad.
-
-#### Permisos del Rol IAM
-
-Al usar AWS IAM para autenticar a Galexie para acceder a un bucket, usa esta política de ejemplo asegurándote de usar el destino correcto del bucket:
-
-```json
-{
-  "Version": "2012-10-17",
-  "Statement": [
-    {
-      "Sid": "AllowS3BucketOperations",
-      "Effect": "Allow",
-      "Action": [
-        "s3:ListBucket",
-        "s3:GetBucketLocation",
-        "s3:ListBucketMultipartUploads"
-      ],
-      "Resource": "arn:aws:s3:::my-galexie-bucket-example"
-    },
-    {
-      "Sid": "AllowS3ObjectAccess",
-      "Effect": "Allow",
-      "Action": [
-        "s3:PutObject",
-        "s3:GetObject",
-        "s3:DeleteObject",
-        "s3:AbortMultipartUpload",
-        "s3:ListMultipartUploadParts"
-      ],
-      "Resource": ["arn:aws:s3:::my-galexie-bucket-example/*"]
-    }
-  ]
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/examples/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/examples/README.mdx
deleted file mode 100644
index b4373bf4dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/examples/README.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: Ejemplos de Uso
-sidebar_position: 20
-sidebar_key: galexie-example-usages
----
-
-Esta sección muestra casos de uso del mundo real de Galexie.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/examples/gcs-export.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/examples/gcs-export.mdx
deleted file mode 100644
index cc84529989..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/examples/gcs-export.mdx
+++ /dev/null
@@ -1,143 +0,0 @@
----
-title: Exportar a GCS
-sidebar_position: 20
----
-
-# Exportar a GCS
-
-## Objetivos
-
-- Los metadatos del libro mayor se almacenan en Google Cloud Storage (GCS).
-- Los consumidores descendentes necesitan acceso a los datos más recientes de la red con una latencia mínima.
-  - Los metadatos del libro mayor para cada libro mayor recién cerrado en Stellar Testnet deben exportarse rápidamente a GCS.
-- La implementación se realizará completamente en la nube, utilizando GCP para todas las necesidades de almacenamiento y computación.
-
-## Solución - Canal del Publicador
-
-Ejecuta la imagen de Dockerhub Galexie, [stellar/stellar-galexie](https://hub.docker.com/r/stellar/stellar-galexie) como una instancia en [GCP Compute Engines](https://cloud.google.com/run/docs/create-jobs) y exporta los metadatos del libro mayor al almacenamiento [de almacenamiento en GCS](https://cloud.google.com/storage/docs/json_api/v1/buckets).
-
-[Galexie](../README.mdx) en este ejemplo, realiza los roles principales del pipeline de datos. Actúa como el `origin` y `publisher` de los metadatos del libro mayor hacia el bucket de Google Cloud Storage que es el `sink`.
-
-### Prepara el archivo de configuración de Galexie localmente
-
-#### `testnet-config.toml`
-
-<CodeExample>
-
-```
-[datastore_config]
-type = "GCS"
-
-[datastore_config.params]
-destination_bucket_path = "galexie-data/ledgers/testnet"
-
-[datastore_config.schema]
-ledgers_per_file = 1
-files_per_partition = 10
-
-[stellar_core_config]
-  network = "testnet"
-```
-
-</CodeExample>
-
-### Establece la zona y el proyecto predeterminados en gcloud
-
-Haz esto una vez, para que no tengas que repetirlo en todos los comandos posteriores. Los comandos de ejemplo suponen que esto está hecho, asegurando que todos los recursos creados estén en el mismo proyecto y zona de GCP, si corresponde, como para computación.
-
-<CodeExample>
-
-```
-gcloud config set compute/zone {your zone here}
-gcloud config set project {your GCP project name}
-```
-
-</CodeExample>
-
-### Almacena el archivo de configuración de galexie en un disco de cómputo
-
-Crea un nuevo disco de cómputo de GCP que solo contenga el archivo de configuración para Galexie. Se utilizará en el siguiente paso como un montaje de volumen para que el contenedor de Galexie pueda acceder a él.
-
-<CodeExample>
-
-```
-// create the raw disk in GCP project
-$ gcloud compute disks create galexie-config-disk \
-  --size=10GB \
-  --type=pd-standard
-
-// need to format this raw disk
-// create a temp instance, attach the new galexie disk to the instance
-$ gcloud compute instances create temp-instance \
-  --machine-type=e2-medium \
-  --disk=name=galexie-config-disk,device-name=galexie-config-disk,mode=rw,auto-delete=no
-
-// shell into the temp instance
-$ gcloud compute ssh temp-instance
-
-// find the unformatted, attached disk device
-// it will be listed with no mountpoint and 10GB
-temp-instance:~$ lsblk
-
-// format the empty disk
-temp-instance:~$ sudo mkfs.ext4 -F /dev/sda
-
-// mount the formatted disk in the instance
-temp-instance:~$ sudo mkdir -p /mnt/my-disk; chmod a+rw /mnt/my-disk
-temp-instance:~$ sudo mount /dev/sda /mnt/my-disk
-temp-instance:~$ exit
-
-// copy the local testnet-config.toml file onto the formatted galexie-config-disk
-$ gcloud compute scp testnet-config.toml temp-instance:/mnt/my-disk
-
-// discard the temp instance, no longer needed, the disk will remain.
-$ gcloud compute instances delete temp-instance
-
-```
-
-</CodeExample>
-
-### Crea un nuevo bucket de gcloud para el almacenamiento de metadatos del libro mayor exportado
-
-<CodeExample>
-
-```
-$ gcloud storage buckets create gs://galexie-data
-```
-
-</CodeExample>
-
-### Usa gcloud para implementar y ejecutar Galexie como instancia de cómputo.
-
-Configura el montaje del volumen en la instancia para que Galexie cargue el archivo de configuración desde el disco de cómputo existente creado en el paso anterior. Especifica la secuencia de libro mayor inicial para que Galexie comience a exportar los metadatos de libro mayor. Los requisitos para esta implementación son comenzar con lo más reciente de la red, que se puede obtener inicialmente de cualquier explorador de bloques, como lo reportado por [stellar.expert/explorer/testnet](https://stellar.expert/explorer/testnet).
-
-En este ejemplo, el tipo de máquina `e2-medium`, debería ser suficiente para los [Requisitos Previos de Galexie](../admin_guide/prerequisites.mdx).
-
-<CodeExample>
-
-```
-gcloud compute instances create-with-container galexie-instance \
-  --scopes=cloud-platform \
-  --machine-type=e2-medium \
-  --container-image=stellar/stellar-galexie \
-  --disk=name=galexie-config-disk,device-name=galexie-config-disk,mode=ro,auto-delete=no \
-  --container-mount-disk=mount-path=/mnt/config,mode=ro,name=galexie-config-disk \
-  --container-arg="append" \
-  --container-arg="--start" \
-  --container-arg="1554952" \
-  --container-arg="--config-file" \
-  --container-arg="/mnt/config/testnet-config.toml"
-```
-
-</CodeExample>
-
-### Monitorea el estado de exportación de Galexie
-
-Accede a la consola de GCP:
-
-- `Cloud Storage->Buckets`, ver el contenido del bucket de GCS `galexie-data`, deberías ver nuevos archivos que representan los metadatos del libro mayor más recientes de Testnet llegando al bucket cada minuto.
-- `Compute Engine->Virtual Machines`, verifica la salida del registro de `galexie-instance`, verás líneas `level=info msg="Uploaded ..` que indican cada vez que se carga un nuevo archivo de metadatos del libro mayor en el bucket de GCS.
-
-## Siguiente paso - Canal del Consumidor
-
-Los metadatos del libro mayor ahora se están acumulando como archivos en tu bucket de GCS. Puedes comenzar a explorar las opciones para que las aplicaciones consuman estos datos de red precomputados utilizando el [Ingest SDK](../../ingest-sdk/README.mdx) para ensamblar canalizaciones de datos impulsadas por el consumidor capaces de importar y analizar los datos para derivar modelos de datos personalizados y enriquecidos. Consulta [el pipeline consumidor de bucket GCS](../../../../../build/apps/ingest-sdk/overview.mdx#ledger-metadata-consumer-pipeline) para el código de ejemplo relevante.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/providers.mdx
deleted file mode 100644
index e1ec7ebea5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/galexie/providers.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-sidebar_position: 1000
-title: Proveedores
----
-
-Varios proveedores de infraestructura han puesto a disposición el servicio y el lago de datos de Galexie, y ofrecen planes que van desde acceso gratuito hasta acceso de pago. Estos proveedores pueden usarse para desarrollo, pruebas y producción.
-
-Estos proveedores permiten acceso a las redes Futurenet, Testnet y Mainnet.
-
-| Proveedor                                                                       | Futurenet | Testnet | Mainnet | URI                                                |
-| ------------------------------------------------------------------------------- | --------- | ------- | ------- | -------------------------------------------------- |
-| [AWS Public Blockchain\*](https://registry.opendata.aws/aws-public-blockchain/) | ❌         | ✅       | ✅       | `s3://aws-public-blockchain/v1.1/stellar/ledgers/` |
-| [Lightsail Network - Quasar](https://quasar.lightsail.network/)                 | ❌         | ❌       | ✅       | `https://galexie.lightsail.network/v1/`            |
-
-\*AWS Public Blockchain poblado por Goldsky
-
-## Ejecutar tu propio Galexie
-
-Si te interesa ejecutar tu propio servicio y lago de datos Galexie, por favor consulta la [Guía del administrador](./admin_guide/README.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/README.mdx
deleted file mode 100644
index 7b53301be5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/README.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Ingestar SDK
-sidebar_position: 0
----
-
-## ¿Qué es el Ingestar SDK?
-
-El SDK está compuesto por varios paquetes publicados en Golang bajo `github.com/stellar/go-stellar-sdk` para adquirir y analizar datos de la red Stellar. Proporciona enlaces a nivel de lenguaje que convierten las secuencias [XDR codificadas en binario](../../../../learn/fundamentals/data-format/xdr.mdx) emitidas por la red en modelos de datos programáticos fluidos.
-
-## ¿Por qué usar el Ingestar SDK?
-
-Las aplicaciones pueden aprovechar el SDK para desarrollar rápidamente canalizaciones de ingestión capaces de adquirir datos de la red Stellar en tiempo real o históricos y derivar modelos de datos personalizados. El SDK permite que las aplicaciones recorran las estructuras de datos jerárquicas de la red: [archivos de historial](../../../../validators/admin-guide/environment-preparation.mdx#history-archives), [ledgers](../../../../learn/fundamentals/stellar-data-structures/ledgers.mdx), transacciones, operaciones, cambios en el estado del ledger y eventos.
-
-Usa el SDK para tener una experiencia de desarrollador intuitiva, segura en tiempo de compilación, y con tipos de datos de la red:
-
-### Entradas de Ledger
-
-Obtén el estado final de [las entradas de ledger](../../../../learn/fundamentals/stellar-data-structures/ledgers.mdx) en la red al cierre de cualquier secuencia de ledger de punto de control reciente o históricamente envejecida. Un ledger de punto de control ocurre una vez cada 64 ledgers, durante el cual la red publicará estos datos en [archivos de historial](../../../../validators/admin-guide/environment-preparation.mdx#history-archives) en el formato de archivos comprimidos que contienen listas de `BucketEntry`, en las cuales cada una contiene una `LedgerEntry` y la `LedgerKey`.
-
-Las entradas del libro mayor están firmadas criptográficamente como parte de cada libro mayor y, por lo tanto, representan el estado acumulado y confiable en un momento dado para los [activos](../../../../learn/fundamentals/stellar-data-structures/assets.mdx) relacionados con una [cuenta](../../../../learn/fundamentals/stellar-data-structures/accounts.mdx) o un [contrato](../../../../learn/fundamentals/contract-development/storage/persisting-data.mdx). Ejemplos de tipos de activos:
-
-- líneas de confianza que mantienen saldos de tokens
-- ofertas que mantienen órdenes de compra y venta en el [stellar network DEX](../../../../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#sdex)
-- datos de contrato que mantienen almacenamiento clave/valor para contratos
-
-### Metadatos de Ledger
-
-Accede a todas las transacciones y sus operaciones anidadas que se incluyeron en cada ledger cerrado. También contiene los cambios (antes y después) para cada entrada del libro mayor cuando se modifican debido a la actividad de la transacción y todos los [eventos de contrato Soroban](../../../../learn/fundamentals/stellar-data-structures/events.mdx) emitidos como resultado de las invocaciones de [contrato](../../../../learn/fundamentals/stellar-data-structures/contracts.mdx) durante la ejecución de la transacción. Es, efectivamente, un registro de confirmación para las entradas de ledger.
-
-Usa los metadatos para detectar cambios incrementales en las entradas de ledger que ocurren como resultado de cada transacción. Estos cambios y los eventos emitidos después de cada transacción representan modelos de datos valiosos específicos de un momento en el tiempo (expresados como una secuencia de ledger en la red), algunos ejemplos del mundo real:
-
-- un pago en forma de transferencia de token entre cuentas
-- se realiza una oferta para intercambiar un token por otro token a un precio determinado en el dex
-- transferencias de token entre cuentas y contratos
-
-El SDK proporciona paquetes que los clientes pueden usar para adquirir y analizar los metadatos en formato de datos de transmisión, con lectores y funciones de devolución de llamada.
-
-Los flujos de metadatos de ledger pueden obtenerse de manera ilimitada a medida que se cierran los ledgers en tiempo real en la red Stellar, y también en un modo de repetición histórica con un rango limitado de secuencias de ledger pasadas.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/README.mdx
deleted file mode 100644
index bfb0190fef..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/README.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Guía para desarrolladores
-sidebar_position: 0
-sidebar_key: guía-del-desarrollador-sdk-ingest
----
-
-El [SDK de ingestión](https://github.com/stellar/go-stellar-sdk/tree/main/ingest) de Stellar es un conjunto de paquetes para recuperar y procesar metadatos del ledger de la red Stellar. Los desarrolladores pueden utilizar este SDK para crear motores de ingestión personalizados.
-
-Esta guía explica cómo configurar, configurar y utilizar el SDK de ingestión de manera efectiva.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.mdx
deleted file mode 100644
index d45a2a0995..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/architecture.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Arquitectura
-sidebar_position: 0
----
-
-![](/assets/ingest-sdk/architecture.png)
-
-## Estructura del SDK de Ingesta
-
-El SDK de Ingesta está organizado en tres componentes principales:
-
-1. **[Ledger Backends](./ledgerbackends/README.mdx)**: Se usan para transmitir los ledgers desde la red Stellar. `https://github.com/stellar/go-stellar-sdk/tree/main/ingest/ledgerbackend`
-2. **[Ledger Readers](./ledgerreaders.mdx)**: Iteradores para extraer cambios individuales o transacciones de un ledger. `https://github.com/stellar/go-stellar-sdk/tree/main/ingest`
-3. **[Procesadores de ledger](https://github.com/stellar/go-stellar-sdk/tree/main/ingest/processors)**: Funciones para procesar cambios o transacciones individuales y extraer datos significativos como cuentas, ofertas, saldo reclammable, etc. Se utilizan junto con `Lector de Ledger` para interpretar y transformar datos de ledger.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/README.mdx
deleted file mode 100644
index 335d22b3db..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/README.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Backend de Ledgers
-sidebar_position: 10
----
-
-Un backend de ledger es una fuente de datos del ledger de la red Stellar. El SDK de ingestión admite dos backends principales de ledger, ambos implementando la interfaz [ledgerbackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/ledger_backend.go). Esta interfaz siempre devuelve datos del libro mayor como un objeto de metadatos del libro mayor codificado en XDR [LedgerCloseMeta](#ledgerclosemeta-structure).
-
-1. **[Captive Core](./captivecore.mdx)** – Invoca el binario `stellar-core` como un proceso secundario que se conecta a la red Stellar en vivo y obtiene datos de la red (es decir, libros mayores).
-2. **[BufferedStorageBackend](./bufferedstoragebackend.mdx)** – Recupera metadatos del libro mayor desde almacenamiento en la nube.
-3. **[RPCLedgerBackend](./rpcledgerbackend.mdx)** – Recupera metadatos del libro mayor desde un servidor RPC.
-
-Cada backend tiene sus propios requisitos de configuración y configuración, los cuales se cubren en las siguientes secciones.
-
-### Estructura de LedgerCloseMeta
-
-`xdr.LedgerCloseMeta` captura un registro detallado de todos los cambios de estado durante el cierre de un ledger Stellar. Incluye:
-
-- `LedgerHeader` – Metadatos sobre el ledger, incluyendo:
-  - Número de secuencia del ledger
-  - Hash del ledger anterior
-  - Hora de cierre
-  - Hash de la bucketlist
-
-- `TxSet` – El conjunto de transacciones incluidas en el ledger.
-
-- `TxProcessing` – Resultados de la ejecución de cada transacción, incluyendo:
-  - Éxito o fracaso de operaciones dentro de las transacciones
-  - `OperationMeta`, que rastrea los `LedgerEntryChanges` causados por las transacciones
-
-- `UpgradesProcessing` – Cualquier actualización de protocolo aplicada en este ledger.
-
-- `ScpInfo` – Detalles del proceso de consenso que finalizó este ledger.
-
-- `EvictedLedgerKeys` – Claves de las entradas del ledger eliminadas debido a la caducidad.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx
deleted file mode 100644
index 5f1594fa67..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/bufferedstoragebackend.mdx
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: AlmacenamientoEnCaché
-sidebar_position: 5
----
-
-[BufferedStorageBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/buffered_storage_backend.go) es un ledger backend en Stellar [ingest SDK](https://github.com/stellar/go-stellar-sdk/tree/main/ingest) que recupera metadatos del ledger desde un data lake basado en la nube, típicamente poblado por [Galexie](../../../galexie/README.mdx). Aunque Galaxie actualmente solo soporta [GCS](../../../galexie/admin_guide/configuring.mdx), `BufferedStorageBackend` está diseñado para funcionar con cualquier datastore que implemente la [interfaz datastore](https://github.com/stellar/go-stellar-sdk/blob/main/support/datastore/datastore.go). Devuelve metadatos del ledger en formato [XDR](../../../../../../learn/fundamentals/data-format/xdr.mdx).
-
-![](/assets/ingest-sdk/bufferedstoragebackend_architecture.png)
-
-## Características Clave
-
-- **Descargas Paralelas**: Descarga múltiples ledgers de forma concurrente y los almacena en memoria para un acceso rápido. Esto es particularmente útil para obtener grandes rangos históricos de ledger.
-- **Consciente del Esquema**: Lee archivos de múltiples ledgers basados en el esquema del datastore, extrayendo un ledger a la vez.
-- **Reintentos Automáticos**: Maneja las fallas de las solicitudes volviendo a intentar las solicitudes fallidas.
-- **Salida XDR**: Devuelve metadatos del ledger en formato XDR, facilitando la integración con otros paquetes en ingest SDK (por ejemplo, [processors](https://github.com/stellar/go-stellar-sdk/tree/main/ingest/processors)).
-
-## Requisitos Previos
-
-### Instalación y Configuración
-
-- Ejecuta Galaxie para exportar datos del ledger al almacenamiento en la nube de GCS. Sigue la [guía de administración de Galaxie](../../../galexie/README.mdx) para instrucciones sobre cómo ejecutar Galaxie.
-
-- Para los propósitos del código de ejemplo, asegúrate de tener acceso a un lago de datos completado por Galaxie, configurado como un bucket de GCS. Para instrucciones sobre cómo crear un data lake, consulta la [guía de administración de Galaxie](../../../galexie/README.mdx).
-
-## Configuración
-
-### Configuración del Datastore
-
-Configura el datastore para igualar el esquema utilizado durante la exportación de Galexie. Este esquema define cuántos ledgers por archivo y cuántos archivos por partición.
-
-```go
-// Datastore configuration structure
-type DataStoreConfig struct {
-    Type   string            `toml:"type"`   // Data storage type (e.g., GCS)
-    Params map[string]string `toml:"params"` // Configuration parameters for the datastore
-    Schema DataStoreSchema   `toml:"schema"` // Defines the ledger storage schema
-}
-```
-
-**Ejemplo de Configuración**
-
-```go
-datastoreConfig := datastore.DataStoreConfig{
-    Type: "GCS", // Using Google Cloud Storage as the backend
-    Params: map[string]string{
-        "destination_bucket_path": "your-gcs-bucket/data", // GCS bucket path to the data
-    },
-    Schema: datastore.DataStoreSchema{
-        LedgersPerFile:    1,     // 1 ledger per file
-        FilesPerPartition: 64000, // Number of files per partition
-    },
-}
-```
-
-### Configuración de BufferedStorageBackend
-
-Configura el `BufferedStorageBackend` para controlar la concurrencia de descargas, el almacenamiento en búfer y el comportamiento de reintento.
-
-```go
-// BufferedStorageBackend configuration structure
-type BufferedStorageBackendConfig struct {
-    BufferSize uint32        `toml:"buffer_size"`  // Number of files to buffer in memory
-    NumWorkers uint32        `toml:"num_workers"`  // Number of concurrent workers for downloading ledgers
-    RetryLimit uint32        `toml:"retry_limit"`  // Number of retry attempts on failure
-    RetryWait  time.Duration `toml:"retry_wait"`   // Time to wait between retry attempts
-}
-```
-
-**Ejemplo de Configuración**
-
-```go
-// BufferedStorageBackend configuration instance
-backendConfig := ledgerbackend.BufferedStorageBackendConfig{
-    BufferSize: 100,             // Buffer upto 100 files in memory
-    NumWorkers: 10,              // 10 parallel download workers
-    RetryLimit: 3,               // Retry up to 3 times on failure
-    RetryWait:  5 * time.Second, // Wait 5 seconds between retries
-
-}
-```
-
-Puedes especificar estos valores individualmente o usar la [configuración predeterminada](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/cdp/producer.go#L29-L46). La configuración predeterminada ajusta automáticamente el número de trabajadores de descarga paralelos y el tamaño del buffer según el tamaño del objeto (número de ledgers por archivo). _Estos valores se basan en pruebas empíricas, pero la configuración óptima puede variar según las condiciones de hardware y red._
-
-### Uso
-
-BufferedStorageBackend se puede usar para el procesamiento por lotes de un rango histórico de ledgers así como para obtener nuevos ledgers en tiempo real a medida que están disponibles.
-
-Aquí hay un código de ejemplo que utiliza `BufferedStorageBackend` para el procesamiento por lotes de rangos históricos de ledger.
-
-```go
-package main
-
-import (
-	"context"
-	"log"
-	"time"
-
-	"github.com/stellar/go-stellar-sdk/ingest/ledgerbackend"
-	"github.com/stellar/go-stellar-sdk/support/datastore"
-	"github.com/stellar/go-stellar-sdk/support/errors"
-)
-
-func main() {
-	ctx := context.Background()
-
-	// Configure the datastore
-	datastoreConfig := datastore.DataStoreConfig{
-		Type: "GCS", // Google Cloud Storage as the backend
-		Params: map[string]string{
-			"destination_bucket_path": "your-gcs-bucket/data", // Replace with actual GCS bucket path
-		},
-	}
-
-	// Initialize the datastore
-	dataStore, err := datastore.NewDataStore(ctx, datastoreConfig)
-	if err != nil {
-		log.Fatal(errors.Wrap(err, "failed to create datastore"))
-	}
-	defer dataStore.Close()
-
-	// Configure the BufferedStorageBackend
-	backendConfig := ledgerbackend.BufferedStorageBackendConfig{
-		BufferSize: 100,             // Number of files to buffer in memory
-		NumWorkers: 10,              // Concurrent download workers
-		RetryLimit: 3,               // Maximum retry attempts on failure
-		RetryWait:  5 * time.Second, // Wait time between retries
-	}
-
-	// Per SEP-54 (https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0054.md),
-	// the schema is stored in the datastore; LoadSchema retrieves it.
-	schema, err := datastore.LoadSchema(context.Background(), dataStore, datastoreConfig)
-	if err != nil {
-		log.Fatal(errors.Wrap(err, "failed to retrieve datastore schema"))
-	}
-
-	// Initialize the backend
-	backend, err := ledgerbackend.NewBufferedStorageBackend(backendConfig, dataStore, schema)
-	if err != nil {
-		log.Fatal(errors.Wrap(err, "failed to create buffered storage backend"))
-	}
-	defer backend.Close()
-
-	// Define the ledger range to process
-	ledgerRange := ledgerbackend.BoundedRange(1000, 2000)
-
-	log.Printf("Starting ledger retrieval for range: %d - %d", ledgerRange.From(), ledgerRange.To())
-
-	// Iterate through the ledger sequence
-	for ledgerSeq := ledgerRange.From(); ledgerSeq <= ledgerRange.To(); ledgerSeq++ {
-		ledgerCloseMeta, err := backend.GetLedger(ctx, ledgerSeq)
-		if err != nil {
-			log.Printf("Warning: Failed to retrieve ledger %d: %v", ledgerSeq, err)
-			continue
-		}
-
-		log.Printf("Successfully retrieved ledger %d. Ledger sequence: %d", ledgerSeq, ledgerCloseMeta.LedgerSequence())
-
-		// Add your logic to process the XDR data
-		// Example: Parsing transactions, operations, etc.
-	}
-
-	log.Println("Ledger retrieval process completed successfully.")
-}
-```
-
-Para la transmisión en tiempo real de nuevos ledgers usando `BufferedStorageBackend`, consulta el [Código de la Pipeline de Ingesta](../../../../../../build/apps/ingest-sdk/ingestion-pipeline-code.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.mdx
deleted file mode 100644
index ce9c59dc96..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/captivecore.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Core cautivo
-sidebar_position: 0
----
-
-Core cautivo invoca el binario `stellar-core` como un subproceso para transmitir ledgers desde la red Stellar. Se puede utilizar para transmitir un rango de ledgers del pasado o para transmitir nuevos ledgers siempre que sean confirmados por la red.
-
-## Requisitos previos
-
-Usar captive Core requiere que el binario stellar-core esté [instalado](../../../../../../validators/admin-guide/installation.mdx) primero.
-
-### Instalación
-
-1. Instalar Stellar Core:
-   - Opción 1: Compilar desde el código fuente siguiendo la [Guía de Instalación](../../../../../../validators/admin-guide/installation.mdx#installing-from-source)
-   - Opción 2: Instalar mediante un gestor de paquetes consultando la [Guía de Instalación basada en paquetes](../../../../../../validators/admin-guide/installation.mdx#package-based-installation)
-
-2. Verificar instalación:
-
-   ```bash
-   ./stellar-core version
-   ```
-
-## Configuración y uso
-
-Establece la configuración del core cautivo para la red Stellar objetivo en formato TOML. Esta configuración requiere como mínimo:
-
-- La **frase de paso** de la red Stellar a la que deseas conectarte.
-- La ruta a los **archivos de historial**, necesarios para la inicialización.
-
-**Paso 1: Generar una configuración `CaptiveCoreToml`**
-
-```go
-captiveCoreToml, err := ledgerbackend.NewCaptiveCoreTomlFromData(
-    ledgerbackend.PubnetDefaultConfig,
-    ledgerbackend.CaptiveCoreTomlParams{
-        NetworkPassphrase:  network.PublicNetworkPassphrase,
-        HistoryArchiveURLs: network.PublicNetworkhistoryArchiveURLs,
-    },
-)
-
-if err != nil {
-    // Handle error
-}
-```
-
-**Paso 2: Construir un objeto `CaptiveCoreConfig`**
-
-A continuación, crea un objeto CaptiveCoreConfig. Este objeto combina la configuración CaptiveCoreToml con la ruta a tu binario stellar-core y otros parámetros necesarios.
-
-```go
-config := ledgerbackend.CaptiveCoreConfig{
-    BinaryPath:         "/usr/local/bin/stellar-core", // Adjust to your stellar-core binary path
-    NetworkPassphrase:  network.PublicNetworkPassphrase,
-    HistoryArchiveURLs: network.PublicNetworkhistoryArchiveURLs,
-    Toml:               captiveCoreToml,
-}
-```
-
-**Paso 3: Instanciar `CaptiveStellarCore`**
-
-Finalmente, crea una instancia de `CaptiveStellarCore` utilizando la función `NewCaptive`. Esta función gestiona el ciclo de vida completo del proceso stellar-core, incluida la comunicación con tu aplicación.
-
-```go
-captiveStellarCoreBackend, err := ledgerbackend.NewCaptive(config)
-if err != nil {
-    // Handle error
-}
-```
-
-El `captiveStellarCoreBackend` ahora se puede usar para recuperar datos de ledger dentro de un rango especificado. Para un uso detallado, consulta los [ejemplos de código](../../examples/README.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.mdx
deleted file mode 100644
index db767018a5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerbackends/rpcledgerbackend.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Backend de ledger RPC
-sidebar_position: 10
----
-
-El [RPCLedgerBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/rpc_backend.go) es una implementación de [LedgerBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/ledger_backend.go) en Stellar [Ingest SDK](https://github.com/stellar/go-stellar-sdk/tree/main/ingest) que utiliza un servidor RPC como fuente base de metadatos del ledger.
-
-Las aplicaciones pueden usar este backend de ledger para obtener metadatos del ledger desde la red Stellar a través de los métodos estándar de la interfaz [LedgerBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/ledger_backend.go). Este backend de ledger se considera el más ligero entre los disponibles ya que solo requiere un cliente HTTP para acceder a un servidor RPC remoto.
-
-El uso de RPCLedgerBackend implica conocer la ventana de retención y la configuración del data lake en el servidor RPC remoto, ya que estos aspectos determinan el rango de ledgers accesibles a través de RPCLedgerBackend.
-
-- `HISTORY_RETENTION_WINDOW` - Esta es una configuración en el servidor RPC que determina el rango de ledgers retenidos por el RPC en una ventana deslizante desde el más reciente en la red Stellar. Por defecto, se retienen los datos del ledger correspondientes a los últimos 7 días de la red Stellar.
-- [Integración con Data Lake](../../../../../apis/rpc/admin-guide/data-lake-integration.mdx) - Si el RPC tiene la integración con Data Lake habilitada, entonces el rango de los libros contables disponibles será como mínimo la Ventana de Retención del RPC y se extenderá más atrás en el tiempo hasta el rango mayor proporcionado por el data lake.
-
-## Ejemplo de uso del SDK
-
-### Requisitos previos
-
-1. Una URL de un Servidor RPC.
-2. Entorno de ejecución Go 1.2x
-
-### Código
-
-Un ejemplo funcional que muestra el uso programático de [RPCLedgerBackend](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledgerbackend/rpc_backend.go) para imprimir un flujo de los últimos ledgers emitidos desde la Red de Pruebas Stellar. Observa el uso adicional del [Cliente RPC Go](https://github.com/stellar/stellar-rpc/blob/main/client/main.go) que usa la misma URL RPC para obtener el último ledger del servidor RPC. Esto se usa para preparar nuestro ejemplo de streaming en vivo para usar el ledger conocido más reciente en RPC como el ledger inicial cuando se solicita el rango ilimitado.
-
-Requisitos previos:
-
-1. Crea un directorio vacío llamado `rpc-backend` y entra en el directorio con `cd`.
-2. Ejecuta `go mod init example/rpc-backend`
-3. Ejecuta `go get github.com/stellar/go-stellar-sdk@latest`
-4. Copia este fragmento de código en `rpc_ledger_backend_demo.go`
-
-```go
-package main
-
-import (
-    "context"
-    "fmt"
-    "log"
-
-    "github.com/stellar/go-stellar-sdk/ingest/ledgerbackend"
-    client "github.com/stellar/go-stellar-sdk/clients/rpcclient"
-)
-
-func main() {
-    ctx := context.Background()
-
-    // Use the public SDF Testnet RPC for demo purpose
-    endpoint := "https://soroban-testnet.stellar.org"
-
-    // Create a new RPC client
-    rpcClient := client.NewClient(endpoint, nil)
-
-    // Get the latest ledger sequence from the RPC server
-    health, err := rpcClient.GetHealth(ctx)
-    if err != nil {
-            log.Fatalf("Failed to get RPC health: %v", err)
-    }
-    startSeq := health.LatestLedger
-
-    // Configure the RPC Ledger Backend
-    backend := ledgerbackend.NewRPCLedgerBackend(ledgerbackend.RPCLedgerBackendOptions{
-            RPCServerURL: endpoint,
-    })
-    defer backend.Close()
-
-    fmt.Printf("Prepare unbounded range starting with Testnet ledger sequence %d: \n", startSeq)
-    // Prepare an unbounded range starting from the latest ledger
-    if err := backend.PrepareRange(ctx, ledgerbackend.UnboundedRange(startSeq)); err != nil {
-            log.Fatalf("Failed to prepare range: %v", err)
-    }
-
-    fmt.Println("Iterating over Testnet ledgers:")
-    seq := startSeq
-    for {
-            ledger, err := backend.GetLedger(ctx, seq)
-            if err != nil {
-                    fmt.Printf("No more ledgers or error at sequence %d: %v\n", seq, err)
-                    break
-            }
-            fmt.Printf("Ledger %d: Hash=%x, CloseTime=%d\n", ledger.LedgerSequence(), ledger.LedgerHash(), ledger.LedgerCloseTime())
-            seq++
-    }
-
-    fmt.Println("Done.")
-}
-```
-
-5. Ejecuta `go mod tidy`
-6. Ejecuta `go run rpc_ledger_backend_demo.go`
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.mdx
deleted file mode 100644
index b79ea79a20..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/ledgerreaders.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Lectores de Ledger
-sidebar_position: 15
----
-
-Estos lectores están diseñados para extraer datos del ledger de Stellar de una manera estructurada y permiten iterar sobre los cambios del ledger.
-
-- [LedgerTransactionReader](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledger_transaction_reader.go): Extrae transacciones de una secuencia específica del libro mayor. Recupera el conjunto de transacciones de `LedgerCloseMeta` y proporciona un iterador para acceder a cada transacción individual.
-
-- [LedgerChangeReader](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/ledger_change_reader.go): Proporciona un registro completo de todos los cambios en las entradas del libro mayor dentro de un libro, incluidos los de transacciones, tarifas, actualizaciones y otras operaciones a nivel de red. Procesa `LedgerCloseMeta` para extraer `LedgerEntryChanges`.
-
-- [CheckpointChangeReader](https://github.com/stellar/go-stellar-sdk/blob/main/ingest/checkpoint_change_reader.go): Lee las entradas del libro mayor de los buckets del archivo histórico en un libro de punto de control, permitiendo a los desarrolladores reconstruir el estado (cuentas, líneas de confianza, etc.) en un momento específico.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.mdx
deleted file mode 100644
index d4c350e33c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/developer_guide/prerequisites.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Requisitos previos
-sidebar_position: 5
----
-
-Para crear utilizando el SDK de ingest, necesitas:
-
-- **Compilador y tiempo de ejecución de Go (>=1,23)** – para crear y ejecutar los paquetes
-- **Git** – para descargar el código fuente _(no necesario si se instala a través del gestor de paquetes)_
-- **IDE** (por ejemplo, VS Code, Goland) _(opcional)_
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/README.mdx
deleted file mode 100644
index f41caf3aba..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/README.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Ejemplos de uso
-sidebar_position: 10
-sidebar_key: ingest-sdk-example-usages
----
-
-Esta sección muestra casos de uso reales del Ingest SDK, enfocándose en componentes clave como `ingest.LedgerTransaction`, `ingest.LedgerChange`, `ingest.LedgerTransactionReader` y `ingest.ChangeReader`.
-
-Estos ejemplos toman un Stellar Ledger (`xdr.LedgerCloseMeta`) o un rango de secuencias de ledger (inicio-fin) como entrada. Cada uno de los ejemplos aquí listados es completo y puede compilarse y ejecutarse tal cual en tu IDE/desarrollo local.
-
-## Requisitos previos
-
-Algunos de los ejemplos listados aquí podrían invocar el binario `stellar-core`. Consulta la "guía de administración" para más detalles sobre cómo compilar `stellar-core` para tu plataforma.
-
-El [Stellar Ingest SDK](https://github.com/stellar/go-stellar-sdk) es un módulo de go e incluye varios paquetes además del SDK de ingestión. Necesitarás incluir el módulo en tu proyecto go `go.mod`.
-
-```bash
-go get github.com/stellar/go-stellar-sdk@latest
-go mod tidy
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/changes.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/changes.mdx
deleted file mode 100644
index 38dbdcfc8c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/changes.mdx
+++ /dev/null
@@ -1,209 +0,0 @@
----
-title: Recuperar cambios de las entradas del ledger dentro de un rango
-sidebar_position: 30
----
-
-Este código invoca el binario `stellar-core` (según lo configurado en `ledgerbackend.CaptiveCoreConfig`) para reproducir ledgers desde un rango de ledger dado. Utiliza el `ingest.LedgerChangeReader` para leer cambios de cada ledger (`xdr.LedgerCloseMeta`) y categoriza los cambios según si representan entradas de ledger creadas, actualizadas o eliminadas. La estructura `ingest.Change` se utiliza para capturar cambios individuales, y el código rastrea varios tipos de cambios, como los relacionados con tarifas, transacciones u operaciones.
-
-```go
-// Filename: change_entries.go
-
-package main
-
-import (
-	"context"
-	"encoding/json"
-	"fmt"
-	"github.com/stellar/go-stellar-sdk/ingest"
-	"github.com/stellar/go-stellar-sdk/ingest/ledgerbackend"
-	"github.com/stellar/go-stellar-sdk/network"
-	"github.com/stellar/go-stellar-sdk/xdr"
-	"io"
-)
-
-func panicIf(err error) {
-	if err != nil {
-		panic(fmt.Errorf("An error occurred, panicking: %s\n", err))
-	}
-}
-
-func getChangesFromLedger(passphrase string, ledger xdr.LedgerCloseMeta) []ingest.Change {
-	changeReader, err := ingest.NewLedgerChangeReaderFromLedgerCloseMeta(passphrase, ledger)
-	panicIf(err)
-	defer changeReader.Close()
-
-	changes := make([]ingest.Change, 0)
-	for {
-		change, err := changeReader.Read()
-		if err == io.EOF {
-			break
-		}
-		panicIf(err)
-		changes = append(changes, change)
-	}
-	return changes
-}
-
-func getLedgers(config ledgerbackend.CaptiveCoreConfig, startingLedger uint32, endLedger uint32) []xdr.LedgerCloseMeta {
-	captiveCore, err := ledgerbackend.NewCaptive(config)
-	panicIf(err)
-
-	ctx := context.Background()
-	err = captiveCore.PrepareRange(ctx, ledgerbackend.BoundedRange(startingLedger, endLedger))
-	panicIf(err)
-	defer captiveCore.Close()
-
-	var ledgers []xdr.LedgerCloseMeta
-	for ledgerSeq := startingLedger; ledgerSeq <= endLedger; ledgerSeq++ {
-		ledger, err := captiveCore.GetLedger(ctx, ledgerSeq)
-		panicIf(err)
-		ledgers = append(ledgers, ledger)
-	}
-	return ledgers
-}
-
-type ChangesInfo struct {
-	LedgerEntriesCreated    int32
-	LedgerEntriesUpdated    int32
-	LedgerEntriesDeleted    int32
-	FeeRelatedChanges       int32
-	TxRelatedChanges        int32
-	OperationRelatedChanges int32
-}
-
-func changeCausedBy(change ingest.Change) xdr.LedgerEntryChangeType {
-	if change.Pre == nil && change.Post != nil {
-		return xdr.LedgerEntryChangeTypeLedgerEntryCreated
-	} else if change.Pre != nil && change.Post == nil {
-		return xdr.LedgerEntryChangeTypeLedgerEntryRemoved
-	} else if change.Pre != nil && change.Post != nil {
-		return xdr.LedgerEntryChangeTypeLedgerEntryUpdated
-	}
-	// this should not happen
-	panic(fmt.Errorf("unable to dertermine LedgerEntryChangeType from change"))
-}
-
-func main() {
-	archiveURLs := network.PublicNetworkhistoryArchiveURLs
-	networkPassphrase := network.PublicNetworkPassphrase
-	captiveCoreToml, err := ledgerbackend.NewCaptiveCoreToml(ledgerbackend.CaptiveCoreTomlParams{
-		NetworkPassphrase:  networkPassphrase,
-		HistoryArchiveURLs: archiveURLs,
-	})
-	panicIf(err)
-
-	config := ledgerbackend.CaptiveCoreConfig{
-		// Change these based on your environment:
-		BinaryPath:         "/usr/local/bin/stellar-core",
-		NetworkPassphrase:  networkPassphrase,
-		HistoryArchiveURLs: archiveURLs,
-		Toml:               captiveCoreToml,
-	}
-
-	startingLedger := uint32(28921599) // Replace with your desired ledger number
-	endLedger := startingLedger + 5
-
-	// NOTE: connecting to pubnet and getting ledgers might take a while.
-	ledgers := getLedgers(config, startingLedger, endLedger)
-
-	for seq, ledgerMeta := range ledgers {
-		fmt.Printf("Processing ledger: %d\n", startingLedger+uint32(seq))
-		changes := getChangesFromLedger(config.NetworkPassphrase, ledgerMeta)
-		info := ChangesInfo{}
-		for _, change := range changes {
-
-			/* Uncomment this code to print the change struct
-			jsonData, err := json.MarshalIndent(change, "", "  ")
-			panicIf(err)
-			fmt.Println(string(jsonData))
-			*/
-
-			switch changeCausedBy(change) {
-			case xdr.LedgerEntryChangeTypeLedgerEntryCreated:
-				info.LedgerEntriesCreated++
-			case xdr.LedgerEntryChangeTypeLedgerEntryRemoved:
-				info.LedgerEntriesDeleted++
-			case xdr.LedgerEntryChangeTypeLedgerEntryUpdated:
-				info.LedgerEntriesUpdated++
-			}
-
-			switch change.Reason {
-			case ingest.LedgerEntryChangeReasonFee:
-				info.FeeRelatedChanges++
-			case ingest.LedgerEntryChangeReasonTransaction:
-				info.TxRelatedChanges++
-			case ingest.LedgerEntryChangeReasonOperation:
-				info.OperationRelatedChanges++
-			default:
-			}
-
-		}
-		jsonData, err := json.MarshalIndent(info, "", "  ")
-		panicIf(err)
-		fmt.Println(string(jsonData))
-	}
-}
-```
-
-**Respuesta de Ejemplo:**
-
-```bash
->> go run ./change_entries.go
-
-// Log lines truncated for clarity
-
-Processing ledger: 28921599
-{
-  "LedgerEntriesCreated": 59,
-  "LedgerEntriesUpdated": 907,
-  "LedgerEntriesDeleted": 62,
-  "FeeRelatedChanges": 227,
-  "TxRelatedChanges": 227,
-  "OperationRelatedChanges": 574
-}
-Processing ledger: 28921600
-{
-  "LedgerEntriesCreated": 58,
-  "LedgerEntriesUpdated": 679,
-  "LedgerEntriesDeleted": 58,
-  "FeeRelatedChanges": 120,
-  "TxRelatedChanges": 120,
-  "OperationRelatedChanges": 555
-}
-Processing ledger: 28921601
-{
-  "LedgerEntriesCreated": 61,
-  "LedgerEntriesUpdated": 885,
-  "LedgerEntriesDeleted": 63,
-  "FeeRelatedChanges": 224,
-  "TxRelatedChanges": 224,
-  "OperationRelatedChanges": 561
-}
-Processing ledger: 28921602
-{
-  "LedgerEntriesCreated": 57,
-  "LedgerEntriesUpdated": 609,
-  "LedgerEntriesDeleted": 56,
-  "FeeRelatedChanges": 106,
-  "TxRelatedChanges": 106,
-  "OperationRelatedChanges": 510
-}
-Processing ledger: 28921603
-{
-  "LedgerEntriesCreated": 62,
-  "LedgerEntriesUpdated": 922,
-  "LedgerEntriesDeleted": 59,
-  "FeeRelatedChanges": 230,
-  "TxRelatedChanges": 230,
-  "OperationRelatedChanges": 583
-}
-Processing ledger: 28921604
-{
-  "LedgerEntriesCreated": 61,
-  "LedgerEntriesUpdated": 670,
-  "LedgerEntriesDeleted": 58,
-  "FeeRelatedChanges": 119,
-  "TxRelatedChanges": 119,
-  "OperationRelatedChanges": 551
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.mdx
deleted file mode 100644
index 9f4b727fea..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/ledger_entry_statistics.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: Obtener el conteo de cada tipo de entrada del ledger del archivo de historial
-sidebar_position: 20
----
-
-Este ejemplo se conecta al Stellar History Archive e inicializa un lector de cambios de punto de control con `ingest.NewCheckpointChangeReader` para leer los cambios de entradas del ledger de una imagen del archivo de historial que ocurre en un ledger de punto de control dado. Itera sobre los cambios del ledger, procesando diferentes tipos de entrada como `Account`, `ClaimableBalance`, `Trustline` y `Offer`, utilizando la estructura `ingest.Change`. El código rastrea estadísticas en una estructura `entriesInfo`, contando las entradas totales y tipos específicos.
-
-```go
-// Filename: ledger_entries.go
-
-package main
-
-import (
-	"context"
-	"encoding/json"
-	"fmt"
-	"github.com/stellar/go-stellar-sdk/historyarchive"
-	"github.com/stellar/go-stellar-sdk/ingest"
-	"github.com/stellar/go-stellar-sdk/network"
-	"github.com/stellar/go-stellar-sdk/support/storage"
-	"github.com/stellar/go-stellar-sdk/xdr"
-	"io"
-)
-
-func panicIf(err error) {
-	if err != nil {
-		panic(fmt.Errorf("An error occurred, panicking: %s\n", err))
-	}
-}
-
-// It helps to have a type to distinguish between the type of key and value, when defining a map
-type AccountIdStr string
-
-type entriesInfo struct {
-	TotalEntries              int32
-	NumAccounts               int32
-	NumAccountsWithTrustlines int32
-	NumClaimableBalances      int32
-	NumOffers                 int32
-}
-
-func main() {
-	archiveURLs := network.PublicNetworkhistoryArchiveURLs
-	networkPassphrase := network.PublicNetworkPassphrase
-
-	// Open a history archive using our existing configuration details.
-	historyArchive, err := historyarchive.NewArchivePool(
-		archiveURLs,
-		historyarchive.ArchiveOptions{
-			NetworkPassphrase: networkPassphrase,
-			ConnectOptions: storage.ConnectOptions{
-				S3Region:         "us-west-1",
-				UnsignedRequests: false,
-			},
-		},
-	)
-	panicIf(err)
-
-	// We pass 48921599 because given a checkpoint frequency of 64 ledgers (the
-	// default in `ConnectOptions`, above), 48921599+1 mod 64 == 0. Incompatible
-	// sequence numbers will likely result in 404 errors.
-	// Ledger seq 48921599 corresponds to about 8 years
-	var reader *ingest.CheckpointChangeReader
-
-	// NOTE: Connecting to pubnet and reading the checkpoint might take a while.
-	reader, err = ingest.NewCheckpointChangeReader(context.Background(), historyArchive, 48921599)
-	panicIf(err)
-	defer reader.Close()
-
-	trustlinesPerAccount := make(map[AccountIdStr]int32)
-
-	info := entriesInfo{}
-	for {
-		var entry ingest.Change
-		entry, err = reader.Read()
-		if err == io.EOF {
-			break
-		}
-		panicIf(err)
-
-		info.TotalEntries++
-
-		switch entry.Type {
-		case xdr.LedgerEntryTypeClaimableBalance:
-			info.NumClaimableBalances++
-		case xdr.LedgerEntryTypeAccount:
-			info.NumAccounts++
-		case xdr.LedgerEntryTypeTrustline:
-			accountId := entry.Post.Data.MustTrustLine().AccountId
-			trustlinesPerAccount[AccountIdStr(accountId.Address())]++
-		case xdr.LedgerEntryTypeOffer:
-			info.NumOffers++
-		default:
-			// there are other types as well, but we are not including them in this example
-		}
-		// Print progress after every 1000 entries are read
-		if info.TotalEntries%1000 == 0 {
-			fmt.Printf("Processed %d ledger entry changes...\r", info.TotalEntries)
-		}
-	}
-	info.NumAccountsWithTrustlines = int32(len(trustlinesPerAccount))
-
-	fmt.Println()
-	// Marshal the struct into JSON with indentation
-	jsonData, err := json.MarshalIndent(&info, "", "    ")
-	panicIf(err)
-	// Print the indented JSON
-	fmt.Println(string(jsonData))
-}
-```
-
-**Respuesta de ejemplo:**
-
-```bash
->> go run  ./ledger_entries.go
-Processed 40123000 ledger entry changes...
-{
-    "TotalEntries": 40123409,
-    "NumAccounts": 7699007,
-    "NumAccountsWithTrustlines": 3414587,
-    "NumClaimableBalances": 7559287,
-    "NumOffers": 1053870
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.mdx
deleted file mode 100644
index 2cabca7ca3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/ingest-sdk/examples/transaction_statistics.mdx
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Obtener transacciones exitosas/fallidas de un rango de ledgers
-sidebar_position: 10
----
-
-Este ejemplo ilustra cómo ejecutar y conectarte a un nodo observador de la red Stellar, conocido como 'captive core' utilizando `ledgerbackend.CaptiveStellarCore`. Luego solicita que se reproduzca un rango histórico limitado de ledgers. La instancia de captive core emitirá un flujo de metadatos de ledger (`xdr.LedgerCloseMeta`) que contiene las transacciones por ledger en el rango. Lee las transacciones de cada ledger utilizando `ingest.LedgerTransactionReader`, las categoriza como exitosas o fallidas, y rastrea las operaciones asociadas con cada transacción.
-
-```go
-// Filename: transaction_statistics.go
-
-package main
-
-import (
-	"context"
-	"fmt"
-	"github.com/stellar/go-stellar-sdk/network"
-	"io"
-
-	"github.com/sirupsen/logrus"
-	"github.com/stellar/go-stellar-sdk/ingest"
-	"github.com/stellar/go-stellar-sdk/ingest/ledgerbackend"
-	"github.com/stellar/go-stellar-sdk/support/log"
-)
-
-func panicIf(err error) {
-	if err != nil {
-		panic(fmt.Errorf("An error occurred, panicking: %s\n", err))
-	}
-}
-
-func main() {
-	archiveURLs := network.PublicNetworkhistoryArchiveURLs
-	networkPassphrase := network.PublicNetworkPassphrase
-	captiveCoreToml, err := ledgerbackend.NewCaptiveCoreToml(ledgerbackend.CaptiveCoreTomlParams{
-		NetworkPassphrase:  networkPassphrase,
-		HistoryArchiveURLs: archiveURLs,
-	})
-	panicIf(err)
-
-	config := ledgerbackend.CaptiveCoreConfig{
-		// Change these based on your environment:
-		BinaryPath:         "/usr/local/bin/stellar-core",
-		NetworkPassphrase:  networkPassphrase,
-		HistoryArchiveURLs: archiveURLs,
-		Toml:               captiveCoreToml,
-	}
-
-	ctx := context.Background()
-	// Only log errors from the backend to keep output cleaner.
-	lg := log.New()
-	lg.SetLevel(logrus.ErrorLevel)
-	config.Log = lg
-
-	backend, err := ledgerbackend.NewCaptive(config)
-	panicIf(err)
-	defer backend.Close()
-
-	// Prepare a range to be ingested:
-	var startingSeq uint32 = 7000000 // can't start with genesis ledger
-	var ledgersToRead uint32 = 10000
-
-	fmt.Printf("Preparing range (%d ledgers)...\n", ledgersToRead)
-	ledgerRange := ledgerbackend.BoundedRange(startingSeq, startingSeq+ledgersToRead)
-	err = backend.PrepareRange(ctx, ledgerRange)
-	panicIf(err)
-
-	// These are the statistics that we're tracking.
-	var successfulTransactions, failedTransactions int
-	var operationsInSuccessful, operationsInFailed int
-
-	for seq := startingSeq; seq <= startingSeq+ledgersToRead; seq++ {
-		fmt.Printf("Processed ledger %d...\r", seq)
-
-		var txReader *ingest.LedgerTransactionReader
-		var err error
-		txReader, err = ingest.NewLedgerTransactionReader(
-			ctx, backend, config.NetworkPassphrase, seq,
-		)
-		panicIf(err)
-
-		// Read each transaction within the ledger, extract its operations, and
-		// accumulate the statistics we're interested in.
-		for {
-			var tx ingest.LedgerTransaction
-			tx, err = txReader.Read()
-			if err == io.EOF {
-				break
-			}
-			panicIf(err)
-
-			envelope := tx.Envelope
-			operationCount := len(envelope.Operations())
-			if tx.Result.Successful() {
-				successfulTransactions++
-				operationsInSuccessful += operationCount
-			} else {
-				failedTransactions++
-				operationsInFailed += operationCount
-			}
-		}
-        	panicIf(txReader.Close())
-	}
-
-	fmt.Println("\nDone. Results:")
-	fmt.Printf("  - total transactions: %d\n", successfulTransactions+failedTransactions)
-	fmt.Printf("  - succeeded / failed: %d / %d\n", successfulTransactions, failedTransactions)
-	fmt.Printf("  - total operations:   %d\n", operationsInSuccessful+operationsInFailed)
-	fmt.Printf("  - succeeded / failed: %d / %d\n", operationsInSuccessful, operationsInFailed)
-}
-```
-
-**Ejemplo de respuesta:**
-
-```bash
->> go run ./transaction_statistics.go
-Preparing range (10000 ledgers)...
-Processed ledger 7010000...
-Done. Results:
-  - total transactions: 108
-  - succeeded / failed: 107 / 1
-  - total operations:   175
-  - succeeded / failed: 174 / 1
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/README.mdx
deleted file mode 100644
index 9fc05d2699..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Procesadores
-sidebar_position: 0
----
-
-Aprende más sobre la biblioteca de procesadores en el [Stellar Go SDK](https://github.com/stellar/go)
-
-## [Procesador de Transferencia de Tokens](./token-transfer-processor/README.mdx)
-
-Rastrea todo movimiento de activos en la blockchain Stellar
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx
deleted file mode 100644
index 9133bf9d84..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/README.mdx
+++ /dev/null
@@ -1,235 +0,0 @@
----
-title: Procesador de Transferencia de Tokens
-sidebar_position: 0
----
-
-## Descripción general
-
-El Procesador de Transferencia de Tokens (TTP) es un [paquete Go](https://github.com/stellar/go-stellar-sdk/tree/main/ingest/processors/token_transfer) que utiliza el [ingest-sdk](../../ingest-sdk/README.mdx) para analizar datos de transacciones en la red Stellar y derivar eventos de transferencia de tokens. Antes del TTP, los desarrolladores tenían que analizar manualmente datos complejos del ledger, resultados de operaciones y cambios en las entradas del ledger para entender cuándo y cómo se movía el valor entre cuentas, contratos y otras entidades en la red.
-
-Antes de [CAP-67 Eventos Unificados][cap67], rastrear transferencias de tokens requería lógica personalizada significativa para manejar distintos tipos de operaciones, interpretar cambios en el ledger y reconstruir el flujo de activos. CAP-67 introdujo un formato estandarizado de eventos que simplifica este proceso al proporcionar una manera unificada de representar todas las actividades de transferencia de tokens.
-
-TTP funciona como una fachada para CAP-67, generando automáticamente estos eventos estandarizados a partir de los datos del ledger Stellar. Puede operar en dos modos:
-
-- **Modo independiente**: TTP analiza operaciones, resultados de operaciones y cambios en las entradas del ledger para derivar eventos de transferencia
-- **Modo de eventos unificados**: TTP lee directamente de eventos unificados compatibles con CAP-67 cuando están disponibles en los datos del ledger
-
-Para más detalles sobre los modos de operación, consulta la sección [Modos de Operación](#modes-of-operation).
-
-## Características clave
-
-- Captura movimientos de tokens resultantes de:
-  - Pagos simples
-  - Pagos con rutas
-  - Operaciones en DEX
-  - Fusiones de cuentas
-  - Revocaciones de trustline
-  - Operaciones de saldo reclamable
-  - Operaciones con Fondos de Liquidez
-  - Operaciones de recuperación forzosa (Clawback)
-  - Eventos de Stellar Asset Contract
-  - Eventos de token compatibles con [SEP-41][sep41]
-
-- Genera eventos de tokens estandarizados CAP-67:
-  - Transferencia: Movimiento de tokens entre cuentas
-  - Creación: Creación de nuevos tokens
-  - Eliminación: Destrucción de tokens
-  - Recuperación forzosa (Clawback): Reclamación de tokens por el emisor del activo
-  - Tarifa: Pago de tarifas de red
-
-- Gestiona información de cuentas muxed conforme al soporte de multiplexación de CAP-67
-
-- Conciliación para versiones antiguas del protocolo para asegurar consistencia entre cambios de operaciones y eventos generados
-
-## Eventos
-
-TTP genera eventos en enlaces Go basándose en las [definiciones protobuf](https://github.com/stellar/go-stellar-sdk/blob/main/protos/ingest/processors/token_transfer/token_transfer_event.proto). Las definiciones codifican un IDL para los modelos estandarizados de eventos de transferencia de tokens propuestos en CAP-67. Cada evento contiene metadatos e información específica del tipo estructurada de la siguiente manera:
-
-| Tipo de evento           | Descripción                                   | Campos clave                                   | Cuándo se genera                                                                   |
-| ------------------------ | --------------------------------------------- | ---------------------------------------------- | ---------------------------------------------------------------------------------- |
-| **Transferencia**        | Movimiento de activo entre dos entidades      | `from`, `to`, `amount`, `asset`, `toMuxedInfo` | Cuando los activos se mueven entre cuentas, contratos u otras entidades            |
-| **Creación**             | Creación del activo por el emisor             | `to`, `amount`, `asset`, `toMuxedInfo`         | Cuando un emisor crea nuevos tokens o cuando los activos se envían desde el emisor |
-| **Eliminación**          | Destrucción del activo para el emisor         | `from`, `amount`, `asset`                      | Cuando los activos son devueltos al emisor para su destrucción                     |
-| **Recuperación forzosa** | Recuperación forzada de activos por el emisor | `from`, `amount`, `asset`                      | Cuando un emisor usa operaciones de clawback para recuperar activos                |
-| **Tarifa**               | Pago o reembolso de tarifa de red             | `account`, `amount`                            | Para todas las tarifas de transacción y reembolsos de tarifas de Soroban           |
-
-### Eventos de Tarifa
-
-TTP genera eventos de tarifas para rastrear las tarifas de red asociadas con el procesamiento de transacciones. Es importante entender los diferentes tipos de eventos de tarifas para una contabilidad precisa:
-
-Los eventos de tarifa se generan para todas las transacciones, ya sea que tengan éxito o fallen. Estos representan las tarifas de red que las cuentas pagan para enviar transacciones a la red Stellar.
-
-- **Presentes en**: Todas las transacciones
-- **Representación del monto**: Valores positivos que indican tarifas pagadas
-- **Activo**: Siempre XLM (el activo nativo de Stellar)
-
-Los eventos de reembolso de tarifas se generan solo para transacciones Soroban (contratos inteligentes) y solo cuando hay recursos no usados que califican para un reembolso.
-
-- **Presentes en**: Transacciones Soroban con tarifas de recursos no usados
-- **Representación del monto**: Valores negativos para indicar dinero que se devuelve
-- **Activo**: Siempre XLM
-- **Tipo de evento**: Usa el mismo tipo de evento `Fee`, distinguido por el monto negativo
-
-:::note
-
-TTP usa montos negativos en eventos de tarifa para representar reembolsos en vez de crear un tipo separado de evento de reembolso. Este enfoque mantiene la consistencia con la especificación CAP-67 mientras indica claramente la dirección de la transacción de tarifa.
-
-:::
-
-### Metadatos del Evento
-
-Cada evento de transferencia de tokens incluye metadatos completos para proporcionar contexto sobre cuándo y dónde ocurrió el evento:
-
-| Campo             | Tipo      | Descripción                                                                                                                                                                                                                                                                                   |
-| ----------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ledgerSequence`  | `uint32`  | El número del ledger donde ocurrió este evento. Esto proporciona un orden cronológico en toda la red.                                                                                                                                                                                         |
-| `txHash`          | `string`  | El hash de transacción que generó este evento. Esto permite rastrear eventos hasta su transacción de origen.                                                                                                                                                                                  |
-| `operationIndex`  | `uint32*` | El índice uno basado en la operación dentro de la transacción que causó este evento según se define en [SEP-35][sep35]. Este campo es `nil` para eventos a nivel de transacción como las tarifas.                                                                                             |
-| `contractAddress` | `string`  | La dirección del contrato asociada con el activo/token que se está moviendo. Para operaciones clásicas o eventos de Stellar Asset Contract, este campo será el contractId del activo clásico subyacente. Esto habilita la integración con el ecosistema de contratos inteligentes de Stellar. |
-
-:::note
-
-El campo `toMuxedInfo` está incluido en eventos de Transferencia y Creación cuando el destino usa una cuenta muxed (dirección M) y/o cuando se establece un memo a nivel de transacción (en el caso de transacciones no de contratos inteligentes), proporcionando información adicional para la ruta.
-
-:::
-
-Por favor, consulta [esta](../../../../../build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx) sección para obtener más información sobre el uso de cuentas muxed/memo.
-
-Consulta [esta](https://stellar.org/protocol/cap-67#prohibit-the-transaction-memo-and-muxed-source-accounts-from-being-set-on-soroban-transactions) sección en CAP-67 para saber más sobre qué esperar en el campo `toMuxedInfo`.
-
-:::note
-
-El campo `contractAddress` es particularmente importante para aplicaciones DeFi ya que provee el puente entre los activos clásicos de Stellar y sus representaciones en contratos inteligentes.
-
-Para eventos de transacciones clásicas y eventos SAC de transacciones de contratos inteligentes, el campo `contractAddress` refleja la dirección SAC para el activo.
-
-:::
-
-## Resumen de la API en Go
-
-TTP proporciona tres funciones distintas que derivan eventos de diferentes niveles de granularidad a partir de los datos subyacentes de la red Stellar.
-
-### EventsFromLedger
-
-```go
-func (p *EventsProcessor) EventsFromLedger(lcm xdr.LedgerCloseMeta) ([]*TokenTransferEvent, error)
-```
-
-Esta función procesa un ledger completo y devuelve una lista aplanada de objetos `TokenTransferEvent`. El orden de los eventos en la lista retornada representa el orden cronológico de débitos, créditos y tarifas como fueron aplicados a cuentas, trustlines y contratos durante el procesamiento del ledger.
-
-El orden cronológico es crucial para aplicaciones que necesitan mantener seguimiento preciso de saldos o auditorías. Para información detallada sobre cómo se ordenan los eventos, consulta la sección [Ordenamiento de Eventos](#event-ordering).
-
-### EventsFromTransaction
-
-```go
-func (p *EventsProcessor) EventsFromTransaction(tx ingest.LedgerTransaction) (TransactionEvents, error)
-```
-
-Esta función procesa una única transacción y devuelve una estructura `TransactionEvents` que separa eventos relacionados con tarifas de eventos relacionados con operaciones:
-
-- `FeeEvents`: Contiene cargos y reembolsos de tarifas asociados con la transacción
-- `OperationEvents`: Contiene todos los eventos generados por las operaciones de la transacción
-
-Esta separación es útil cuando necesitas manejar las tarifas de manera diferente a las transferencias operacionales, como para contabilidad o análisis.
-
-### EventsFromOperation
-
-```go
-func (p *EventsProcessor) EventsFromOperation(
-	tx ingest.LedgerTransaction,
-	opIndex uint32,
-	op xdr.Operation,
-	opResult xdr.OperationResult
-	) ([]*TokenTransferEvent, error)
-```
-
-Esta función procesa una única operación dentro de una transacción y devuelve una lista de eventos generados por esa operación específica. Este enfoque granular es útil para aplicaciones que necesitan analizar o reaccionar a tipos específicos de operaciones.
-
-## Modos de Operación
-
-TTP puede operar en dos modos distintos según cómo se generaron los datos del ledger y qué información esté disponible.
-
-### Modo por defecto (Recomendado)
-
-En modo por defecto, TTP analiza tres fuentes de información para derivar eventos de transferencia de tokens:
-
-- **Operaciones**: Las operaciones enviadas en transacciones
-- **Resultados de Operación**: Los resultados de éxito/falla de cada operación
-- **Cambios en las Entradas del Ledger**: Los cambios realizados al estado del ledger
-
-Este modo funciona con todos los ledgers Stellar independientemente de cómo fueron generados o qué versión de stellar-core los produjo. Es la opción más segura y compatible.
-
-```go
-// Default mode - works with all ledgers
-processor := token_transfer.NewEventsProcessor(networkPassphrase)
-```
-
-### Modo de flujo de eventos unificados
-
-En modo de flujo de eventos unificados, TTP lee eventos de transferencia de tokens directamente del flujo de eventos unificados incrustado en los datos del ledger. Este modo es más eficiente pero requiere que los ledgers hayan sido generados con flags de configuración específicos de stellar-core.
-
-```go
-// Unified events mode - only for specially configured ledgers
-processor := token_transfer.NewEventsProcessorForUnifiedEvents(networkPassphrase)
-```
-
-Solo usa el modo de flujo de eventos unificados si estás seguro de que tus ledgers contienen eventos unificados. Estos ledgers deben ser generados por stellar-core con las flags de configuración `EMIT_CLASSIC_EVENTS=true` y `BACKFILL_STELLAR_ASSET_EVENTS=true` activadas. TTP no puede determinar dinámicamente si un ledger contiene eventos unificados o no.
-
-:::caution
-
-Si configuras TTP en modo de eventos unificados y luego proporcionas ledgers sin eventos unificados, TTP no generará eventos sin notificarlo.
-
-:::
-
-**Cuando tengas dudas, siempre usa el modo por defecto**, ya que funciona de manera confiable con todos los tipos de ledgers.
-
-## Orden de eventos
-
-El orden de los eventos que devuelve TTP depende de la versión del protocolo Stellar que estaba activa cuando se creó el ledger. Este ordenamiento es crucial para mantener registros cronológicos precisos de movimientos de activos.
-
-### Ordenamiento antes del Protocolo 23
-
-Antes de Whisk, Protocolo 23, los eventos siguen este patrón cronológico:
-
-```
-All Fee Events (from all transactions)
-↓
-For each transaction in ledger:
-  - Operation Events (from all operations in the transaction)
-  - Fee Refund Event (if applicable, immediately after operation events)
-```
-
-En este orden, los reembolsos de tarifas aparecen inmediatamente después de los eventos de operación de cada transacción individual.
-
-### Orden del Protocolo 23+
-
-A partir de Whisk, Protocolo 23, los eventos siguen este patrón cronológico:
-
-```
-All Fee Events (from all transactions)
-↓
-All Operation Events (from all transactions, maintaining transaction and operation order)
-↓
-All Fee Refund Events (from all transactions)
-```
-
-En este orden más reciente, todos los reembolsos de tarifas se agrupan juntos al final, después de que se hayan procesado todas las transacciones.
-
-:::note
-
-TTP detecta automáticamente la versión del protocolo y aplica las reglas de orden correctas. No necesitas configurar esto manualmente, pero entender las diferencias en el orden es importante para las aplicaciones que dependen de la secuencia de eventos.
-
-:::
-
-El orden cronológico asegura que cuando procesas eventos en el orden que devuelve TTP, sigues la secuencia exacta en la que débitos y créditos se aplicaron a cuentas durante el procesamiento del ledger. Esto es esencial para mantener cálculos precisos de saldos y registros de auditoría.
-
-## Referencias
-
-- [CAP-67: Eventos unificados][cap67]
-- [SEP-41: Especificación de Contrato de Token de Activo][sep41]
-- [CAP-38: Creadores de Mercado Automatizados](https://stellar.org/protocol/cap-38)
-- [SEP-35: Esquema de ID para operaciones Stellar][sep35]
-
-[sep41]: https://stellar.org/protocol/sep-41
-[cap67]: https://stellar.org/protocol/cap-67
-[sep35]: https://stellar.org/protocol/sep-35
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/README.mdx
deleted file mode 100644
index 577a87f4b6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/README.mdx
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Ejemplos de uso
-sidebar_position: 10
-sidebar_key: token-transfer-processor-example-usages
----
-
-Esta sección contiene ejemplos de cómo puede usarse Token Transfer Processor en la lógica de tu aplicación
-
-## Requisitos previos
-
-Tienes un módulo go existente en el directorio actual o crea un nuevo módulo localmente para este ejercicio de ejemplo.
-
-```bash
-go mod init example/ttp_processor
-```
-
-Incluye el SDK de Stellar Ingest en el módulo de tu aplicación Go que contiene el Procesador de Transferencias de Token.
-
-```bash
-go get github.com/stellar/go-stellar-sdk@latest
-go mod tidy
-```
-
-## Código auxiliar
-
-Esta sección contiene algo de código auxiliar que se usará en todos los ejemplos.
-
-```go
-package main
-
-import (
-	"context"
-	"fmt"
-
-	"github.com/stellar/go-stellar-sdk/ingest/ledgerbackend"
-	"github.com/stellar/go-stellar-sdk/processors/token_transfer"
-	"github.com/stellar/go-stellar-sdk/support/log"
-	"github.com/stellar/go-stellar-sdk/xdr"
-
-	"google.golang.org/protobuf/encoding/protojson"
-)
-
-func panicIf(err error) {
-	if err != nil {
-		panic(err)
-	}
-}
-
-// fetchLedgerFromRPC retrieves a ledger using RPCLedgerBackend
-func fetchLedgerFromRPC(ledgerSeq uint32) xdr.LedgerCloseMeta {
-	ctx := context.Background()
-
-	// Using a publicly hosted RPC instance
-	endpoint := "https://mainnet.sorobanrpc.com"
-
-	// Configure the RPC Ledger Backend
-	backend := ledgerbackend.NewRPCLedgerBackend(ledgerbackend.RPCLedgerBackendOptions{
-		RPCServerURL: endpoint,
-	})
-	defer backend.Close()
-
-	// Prepare an unbounded range starting from the latest ledger
-	if err := backend.PrepareRange(ctx, ledgerbackend.BoundedRange(ledgerSeq, ledgerSeq)); err != nil {
-		log.Fatalf("Failed to prepare range: %v", err)
-	}
-
-	ledger, err := backend.GetLedger(ctx, ledgerSeq)
-	panicIf(err)
-	return ledger
-}
-
-func printProtoEvent(event *token_transfer.TokenTransferEvent) {
-	jsonBytes, _ := protojson.MarshalOptions{
-		Multiline:         true,
-		EmitDefaultValues: true,
-		Indent:            "  ",
-	}.Marshal(event)
-	fmt.Printf("### Event Type : %v\n", event.GetEventType())
-	fmt.Println(string(jsonBytes))
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.mdx
deleted file mode 100644
index 5b66098f0f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/event_stats.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: Recuperar eventos de transferencia de tokens de un ledger
-sidebar_position: 10
----
-
-Este ejemplo obtiene un ledger específico de Stellar y usa el Procesador de Transferencia de Tokens para extraer todos los eventos de movimiento de tokens de él. El código procesa cada evento, los categoriza por tipo (transferencias, creaciones, quemas, recuperaciones, tarifas) e imprime tanto los detalles individuales de cada evento como estadísticas resumidas. Esto demuestra el uso básico de EventsFromLedger() para analizar toda la actividad de activos dentro de un solo ledger.
-
-```go
-package main
-
-import (
-	"fmt"
-	"strings"
-
-	"github.com/stellar/go-stellar-sdk/network"
-	"github.com/stellar/go-stellar-sdk/processors/token_transfer"
-)
-
-func main() {
-	ledgerSeq := uint32(58155263)
-	ledger := fetchLedgerFromRPC(ledgerSeq)
-	ttp := token_transfer.NewEventsProcessor(network.PublicNetworkPassphrase)
-
-	// Process events from a single ledger
-	events, err := ttp.EventsFromLedger(ledger)
-	panicIf(err)
-
-	// Statistics counters
-	var transferCount, mintCount, burnCount, clawbackCount, feeCount, refundCount int
-
-	// Process events to analyze token transfers
-	for _, event := range events {
-		switch {
-		case event.GetTransfer() != nil:
-			transfer := event.GetTransfer()
-			fmt.Printf("Transfer: %s -> %s, Amount: %s, Asset: %s\n",
-				transfer.From, transfer.To, transfer.Amount, transfer.Asset)
-			transferCount++
-
-		case event.GetMint() != nil:
-			mint := event.GetMint()
-			fmt.Printf("Mint: %s, Amount: %s, Asset: %s\n",
-				mint.To, mint.Amount, mint.Asset)
-			mintCount++
-
-		case event.GetBurn() != nil:
-			burn := event.GetBurn()
-			fmt.Printf("Burn: %s, Amount: %s, Asset: %s\n",
-				burn.From, burn.Amount, burn.Asset)
-			burnCount++
-
-		case event.GetClawback() != nil:
-			clawback := event.GetClawback()
-			fmt.Printf("Clawback: %s, Amount: %s, Asset: %s\n",
-				clawback.From, clawback.Amount, clawback.Asset)
-			clawbackCount++
-
-		case event.GetFee() != nil:
-			fee := event.GetFee()
-			if strings.HasPrefix(fee.Amount, "-") {
-				fmt.Printf("Fee Refund: %s, Amount: %s, Asset: %s\n",
-					fee.From, fee.Amount, fee.Asset)
-				refundCount++
-			} else {
-				fmt.Printf("Fee: %s, Amount: %s, Asset: %s\n",
-					fee.From, fee.Amount, fee.Asset)
-				feeCount++
-			}
-		}
-	}
-
-	// Print statistics
-	fmt.Printf("\n--- Ledger %d Statistics ---\n", ledgerSeq)
-	fmt.Printf("Total Events: %d\n", len(events))
-	fmt.Printf("Transfers: %d\n", transferCount)
-	fmt.Printf("Mints: %d\n", mintCount)
-	fmt.Printf("Burns: %d\n", burnCount)
-	fmt.Printf("Clawbacks: %d\n", clawbackCount)
-	fmt.Printf("Fees: %d\n", feeCount)
-	fmt.Printf("Refunds: %d\n", refundCount)
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.mdx
deleted file mode 100644
index 5e022a8325..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/processors/token-transfer-processor/examples/filter_events.mdx
+++ /dev/null
@@ -1,220 +0,0 @@
----
-title: Filtrar eventos de la transacción
-sidebar_position: 20
----
-
-Este código demuestra una implementación práctica del filtrado de eventos usando la función `EventsFromTransaction` del Procesador de Transferencia de Tokens.
-
-El código procesa cada transacción individualmente llamando a ttp.EventsFromTransaction(tx), que devuelve una estructura TransactionEvents que contiene:
-
-- `FeeEvents`: Tarifas y reembolsos de la transacción
-- `OperationEvents`: Todos los eventos de transferencia de tokens generados por las operaciones de la transacción
-
-Los eventos de ambas categorías se combinan en una sola lista (allEvents) para un filtrado unificado, permitiéndote aplicar los mismos criterios de filtro a todos los tipos de eventos dentro de cada transacción.
-
-## Filtrado
-
-El sistema de filtrado usa tipos de datos Stellar del SDK Go de Stellar para una coincidencia precisa:
-
-- **Coincidencia de activos**: Convierte los criterios de filtro en objetos `xdr.Asset` y usa `assetPkg.NewProtoAsset()` para una comparación exacta de assets protobuf mediante `event.GetAsset().Equals(protoAsset)`
-- **Coincidencia por tipo de evento**: Usa las constantes reales del tipo de evento del paquete token_transfer (por ejemplo, `token_transfer.TransferEvent`)
-- **Filtrado por contrato**: Coincide con direcciones exactas de contrato de los metadatos del evento
-
-```go
-package main
-
-import (
-	"fmt"
-	"io"
-	"log"
-	"strings"
-
-	assetPkg "github.com/stellar/go-stellar-sdk/asset"
-	"github.com/stellar/go-stellar-sdk/ingest"
-	"github.com/stellar/go-stellar-sdk/network"
-	"github.com/stellar/go-stellar-sdk/processors/token_transfer"
-	"github.com/stellar/go-stellar-sdk/xdr"
-)
-
-// FilterOptions defines the filtering criteria
-type FilterOptions struct {
-	EventType  string // "transfer", "mint", "burn", "clawback", "fee", or "" for all
-	AssetCode  string // Asset code like "USDC", "XLM", or "" to ignore
-	Issuer     string // Issuer address or "" to ignore
-	ContractId string // Contract address or "" to ignore
-}
-
-// filterEvents processes a ledger and returns events matching the filter criteria
-func filterEvents(ledger xdr.LedgerCloseMeta, filter FilterOptions) {
-
-	ttp := token_transfer.NewEventsProcessor(network.PublicNetworkPassphrase)
-
-	// Create transaction reader
-	txReader, err := ingest.NewLedgerTransactionReaderFromLedgerCloseMeta(
-		network.PublicNetworkPassphrase, ledger)
-	if err != nil {
-		log.Fatal("Error creating transaction reader:", err)
-	}
-
-	// Print filter configuration
-	fmt.Printf("Filtering ledger %d with criteria:\n", ledger.LedgerSequence())
-	if filter.EventType != "" {
-		fmt.Printf("  Event Type: %s\n", filter.EventType)
-	}
-	if filter.AssetCode != "" {
-		fmt.Printf("  Asset Code: %s\n", filter.AssetCode)
-	}
-	if filter.Issuer != "" {
-		fmt.Printf("  Issuer: %s\n", filter.Issuer)
-	}
-	if filter.ContractId != "" {
-		fmt.Printf("  Contract ID: %s\n", filter.ContractId)
-	}
-	fmt.Println()
-
-	var matchedEvents, totalEvents int
-
-	// Process each transaction
-	for {
-		tx, err := txReader.Read()
-		if err == io.EOF {
-			break
-		}
-		if err != nil {
-			log.Fatal("Error reading transaction:", err)
-		}
-
-		// Save information about tx, if needed in DB
-
-		// Process events from this transaction
-		txEvents, err := ttp.EventsFromTransaction(tx)
-		if err != nil {
-			log.Printf("Error processing transaction: %v", err)
-			continue
-		}
-
-		// Combine all events from the transaction
-		allEvents := append(txEvents.FeeEvents, txEvents.OperationEvents...)
-		totalEvents += len(allEvents)
-
-		// Apply filter to each event
-		for _, event := range allEvents {
-			if matchesFilter(event, filter) {
-				printProtoEvent(event)
-				matchedEvents++
-			}
-		}
-	}
-
-	// Print summary
-	fmt.Printf("\n--- Filter Results ---\n")
-	fmt.Printf("Total events: %d\n", totalEvents)
-	fmt.Printf("Matched events: %d\n", matchedEvents)
-}
-
-// matchesFilter checks if an event matches the specified filter criteria
-func matchesFilter(event *token_transfer.TokenTransferEvent, filter FilterOptions) bool {
-	// Check event type filter
-	if filter.EventType != "" {
-		if !matchesEventType(event, filter.EventType) {
-			return false
-		}
-	}
-
-	// Check contract ID filter
-	if filter.ContractId != "" {
-		meta := event.GetMeta()
-		if meta.ContractAddress != filter.ContractId {
-			return false
-		}
-	}
-
-	// Check asset filters
-	if filter.AssetCode != "" || filter.Issuer != "" {
-		var asset xdr.Asset
-		if filter.AssetCode == "native" {
-			asset = xdr.MustNewNativeAsset()
-		} else {
-			asset = xdr.MustNewCreditAsset(filter.AssetCode, filter.Issuer)
-		}
-
-		if !matchesAsset(event, asset) {
-			return false
-		}
-	}
-
-	return true
-}
-
-// matchesEventType checks if event matches the specified event type
-func matchesEventType(event *token_transfer.TokenTransferEvent, eventType string) bool {
-	switch strings.ToLower(eventType) {
-	case token_transfer.TransferEvent:
-		return event.GetTransfer() != nil
-	case token_transfer.MintEvent:
-		return event.GetMint() != nil
-	case token_transfer.BurnEvent:
-		return event.GetBurn() != nil
-	case token_transfer.ClawbackEvent:
-		return event.GetClawback() != nil
-	case token_transfer.FeeEvent:
-		return event.GetFee() != nil
-	default:
-		return false
-	}
-}
-
-// matchesAsset checks if xdr.Asset specified matches the protobuf asset
-func matchesAsset(event *token_transfer.TokenTransferEvent, asset xdr.Asset) bool {
-	protoAsset := assetPkg.NewProtoAsset(asset)
-	return event.GetAsset().Equals(protoAsset)
-}
-
-func main() {
-	ledgerSeq := uint32(58155263)
-
-	ledger := fetchLedgerFromRPC(ledgerSeq)
-
-	// Example 1: Filter by event type only
-	fmt.Println("=== Example 1: Only Transfer Events ===")
-	filterEvents(ledger, FilterOptions{
-		EventType: "transfer",
-	})
-
-	// Example 2: Filter by custom token (asset code + issuer)
-	fmt.Println("\n=== Example 2: Only USDC Events ===")
-	filterEvents(ledger, FilterOptions{
-		AssetCode: "USDC",
-		Issuer:    "GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN",
-	})
-
-	// Example 3: Filter by event type + contract ID
-	fmt.Println("\n=== Example 3: Transfer Events from Specific Contract (USDC in this case) ===")
-	filterEvents(ledger, FilterOptions{
-		EventType: "transfer",
-		// This is the SAC id for the USDC asset on pubnet
-		// https://stellar.expert/explorer/public/contract/CCW67TSZV3SSS2HXMBQ5JFGCKJNXKZM7UQUWUZPUTHXSTZLEO7SJMI75
-		ContractId: "CCW67TSZV3SSS2HXMBQ5JFGCKJNXKZM7UQUWUZPUTHXSTZLEO7SJMI75",
-	})
-
-	// Example 4: Filter by event type + asset code + issuer
-	fmt.Println("\n=== Example 4: Only KALE mints ===")
-	filterEvents(ledger, FilterOptions{
-		EventType: "mint",
-		AssetCode: "KALE",
-		Issuer:    "GBDVX4VELCDSQ54KQJYTNHXAHFLBCA77ZY2USQBM4CSHTTV7DME7KALE",
-	})
-
-	// Example 5: Filter by XLM events only
-	fmt.Println("\n=== Example 5: Only XLM Events ===")
-	filterEvents(ledger, FilterOptions{
-		AssetCode: "native",
-	})
-
-	// Example 6: Filter by fee events only
-	fmt.Println("\n=== Example 6: Only Fee Events ===")
-	filterEvents(ledger, FilterOptions{
-		EventType: "fee",
-	})
-}
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/tutorials/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/tutorials/README.mdx
deleted file mode 100644
index 1950b23e91..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/build-your-own/tutorials/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Tutoriales
-sidebar_position: 10
----
-
-Tutoriales para desarrollar tu propio indexador.
-
-## [Desarrollar Canal de Ingesta de Red Personalizado](../../../../build/apps/ingest-sdk/overview.mdx)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/indexer-providers/indexer-providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/indexer-providers/indexer-providers.mdx
deleted file mode 100644
index 988a4f97df..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/indexers/indexer-providers/indexer-providers.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 20
-title: Proveedores de Indexador de Datos
----
-
-## Indexadores de Datos
-
-Para potenciar tus aplicaciones, estará disponible una gama de servicios de datos desde indexadores de datos con interfaces de consulta. Estos indexadores te permitirán almacenar y recuperar fácilmente datos de ledger decodificados, emisiones de eventos de contratos, y más. Puedes enfocar más energía en hacer que tu proyecto tenga éxito y perder menos tiempo descubriendo cómo obtener precisamente los datos importantes de la red.
-
-### [Goldsky](https://goldsky.com/)
-
-Goldsky es un proveedor de indexación para Stellar que facilita extraer, transformar y cargar datos on-chain para impulsar tanto aplicaciones. Una herramienta de canalización de datos que te permite combinar datos on-chain y off-chain como desees, transmitidos directamente a tu propia base de datos personalizada. Para más información, por favor consulta la [documentación relevante](https://docs.goldsky.com/chains/stellar) y el [video tutorial](https://docs.goldsky.com/chains/stellar#1-deploying-stellar-transactions-using-goldsky-flow).
-
-Selecciona la fuente de datos: ![Goldsky Datasets](/assets/api/indexer/goldsky1.png)
-
-Selecciona un handler o un sumidero de datos: ![Goldsky DataSink](/assets/api/indexer/goldsky2.png)
-
-Selecciona un tipo de sumidero de datos: ![Goldsky Yaml](/assets/api/indexer/goldsky3.png)
-
-### [Mercury](https://docs.mercurydata.app)
-
-Un servicio de indexación de red que proporciona un conjunto de herramientas para ayudarte a comenzar a trabajar con datos de la red Stellar.
-
-### [SubQuery](https://subquery.network/)
-
-Un indexador de datos open-source para Stellar que permite la creación de APIs personalizadas para dapps y contratos inteligentes con datos limpios e indexados. Admite la indexación de ledgers, transacciones, operaciones y efectos de Stellar, así como transacciones y eventos de Soroban en una base de datos Postgres.
-
-### [The Graph](https://thegraph.com/)
-
-Un protocolo de indexación descentralizado para consultar datos de blockchain. The Graph permite a los desarrolladores crear y publicar APIs abiertas, llamadas subgráficas, que hacen que los datos on-chain sean fácilmente accesibles y buscables para sus aplicaciones.
-
-### [OnFinality](https://onfinality.io)
-
-Servicio líder en la industria de alojamiento y gestión de indexadores de datos para tus proyectos Stellar SubQuery y Subgraph
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/oracles/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/oracles/README.mdx
deleted file mode 100644
index 882a6733b5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/oracles/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Oráculos
-description: Aprender sobre oráculos y fuentes de datos fuera de la cadena
-sidebar_label: Oráculos
-sidebar_position: 10
----
-
-# Oráculos
-
-Los oráculos son servicios que conectan sistemas de blockchain con fuentes de datos externas y fuera de la cadena, permitiendo que los contratos inteligentes interactúen con información del mundo real. Actúan como intermediarios, obteniendo y verificando datos como precios de mercado, condiciones climáticas o resultados de eventos, y luego entregándolos a la blockchain de manera segura y confiable. Esto permite que las aplicaciones descentralizadas (dApps) se ejecuten en base a eventos del mundo real, ampliando su funcionalidad más allá de los datos en la cadena.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/oracles/oracle-providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/oracles/oracle-providers.mdx
deleted file mode 100644
index e9139065a1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/data/oracles/oracle-providers.mdx
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title: Proveedores de Oracle
-description: Explora datos en cadena y precios utilizando oráculos.
-sidebar_label: Proveedores de Oracle
-sidebar_position: 20
----
-
-Los oráculos existen en la red Stellar para llevar datos fuera de cadena a la blockchain. Por ejemplo, un caso de uso popular de los oráculos es la inclusión de precios de tokens en la lógica de contratos inteligentes. Dado que un contrato inteligente no puede acceder a datos de fuera de la red Stellar, los oráculos proporcionan un medio por el cual los datos pueden ser accedidos en cadena.
-
-## [Red Reflector](https://reflector.network)
-
-El protocolo de oráculos Reflector es una combinación de contratos inteligentes especializados y consenso entre pares de nodos proveedores de datos mantenidos por organizaciones de confianza del ecosistema Stellar. Los feeds incluyen precios de activos on-chain y off-chain, tasas de exchange de CEX y DEX, tasas de cambio de divisas, etc. Los nodos reflector procesan, normalizan, agregan y almacenan la información de operaciones del Stellar Classic DEX, los protocolos Soroban, así como de fuentes externas.
-
-Los oráculos de precios gratuitos disponibles públicamente son compatibles con la interfaz estándar del ecosistema [SEP40](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0040.md). Aprende a integrar los flujos Reflector [en su documentación](https://reflector.network/docs).
-
-[Las suscripciones Reflector](https://reflector.network/subscription) ofrecen un servicio de disparadores personalizados definidos por el usuario, que se activan automáticamente una vez que el cambio de precio de un símbolo especificado alcanza un umbral determinado. Cuando se cumple la condición, los nodos del clúster envían simultáneamente una notificación a la URL WebHook proporcionada en la suscripción y publican una prueba on-chain del evento activado.
-
-### Integraciones
-
-- [Blend](https://www.blend.capital) [Lending]
-- [OrbitCDP](https://orbitcdp.finance) [Collateralized Stablecoin]
-- [DeFindex](https://www.defindex.io) [Yield Aggregator]
-- [Laina](https://laina-de.fi) [Lending]
-- [EquitX](https://equitx.com) [Synthetics]
-- [Slender](https://slender.fi) [Lending]
-- [SorobanDomains](https://sorobandomains.org) [Infrastructure]
-
-### Oráculos públicos Reflector desplegados
-
-| Dirección                                                                                                                                                               | Fuente de Datos              | Red     |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- | ------- |
-| [`CALI2BYU2JE6WVRUFYTS6MSBNEHGJ35P4AVCZYF3B6QOE3QKOB2PLE6M`](https://stellar.expert/explorer/public/contract/CALI2BYU2JE6WVRUFYTS6MSBNEHGJ35P4AVCZYF3B6QOE3QKOB2PLE6M)  | DEX de Stellar Mainnet       | Mainnet |
-| [`CAFJZQWSED6YAWZU3GWRTOCNPPCGBN32L7QV43XX5LZLFTK6JLN34DLN`](https://stellar.expert/explorer/public/contract/CAFJZQWSED6YAWZU3GWRTOCNPPCGBN32L7QV43XX5LZLFTK6JLN34DLN)  | CEXs y DEXs externos         | Mainnet |
-| [`CBKGPWGKSKZF52CFHMTRR23TBWTPMRDIYZ4O2P5VS65BMHYH4DXMCJZC`](https://stellar.expert/explorer/public/contract/CBKGPWGKSKZF52CFHMTRR23TBWTPMRDIYZ4O2P5VS65BMHYH4DXMCJZC)  | Tasas de exchange fiduciario | Mainnet |
-|                                                                                                                                                                         |                              |         |
-| [`CAVLP5DH2GJPZMVO7IJY4CVOD5MWEFTJFVPD2YY2FQXOQHRGHK4D6HLP`](https://stellar.expert/explorer/testnet/contract/CAVLP5DH2GJPZMVO7IJY4CVOD5MWEFTJFVPD2YY2FQXOQHRGHK4D6HLP) | DEX de Stellar Mainnet       | Testnet |
-| [`CCYOZJCOPG34LLQQ7N24YXBM7LL62R7ONMZ3G6WZAAYPB5OYKOMJRN63`](https://stellar.expert/explorer/testnet/contract/CCYOZJCOPG34LLQQ7N24YXBM7LL62R7ONMZ3G6WZAAYPB5OYKOMJRN63) | CEXs y DEXs externos         | Testnet |
-| [`CCSSOHTBL3LEWUCBBEB5NJFC2OKFRC74OWEIJIZLRJBGAAU4VMU5NV4W`](https://stellar.expert/explorer/testnet/contract/CCSSOHTBL3LEWUCBBEB5NJFC2OKFRC74OWEIJIZLRJBGAAU4VMU5NV4W) | Tasas de exchange fiduciario | Testnet |
-
-## [Band](https://www.bandprotocol.com/)
-
-Band es un oracle de datos entre cadenas que agrega y conecta datos del mundo real y APIs con contratos inteligentes.
-
-El protocolo está desarrollado sobre BandChain, una blockchain basada en Cosmos-SDK diseñada para ser compatible con la mayoría de los marcos de desarrollo de contratos inteligentes y blockchain.
-
-La red está diseñada para modularizar y descargar la tarea de monitorear constantemente los datos de precios y reaccionar a los cambios de precios en todas las clases de activos desde las plataformas de contratos inteligentes hacia sí misma. Esto no solo evita que tales tareas congestionen o causen altas tarifas de transacción en la red de destino, sino que los mismos puntos de datos pueden ser empaquetados, utilizados y verificados eficientemente a través de múltiples blockchains.
-
-| Dirección                                                                                                                                                               | Red     |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
-| [`CCQXWMZVM3KRTXTUPTN53YHL272QGKF32L7XEDNZ2S6OSUFK3NFBGG5M`](https://stellar.expert/explorer/public/contract/CCQXWMZVM3KRTXTUPTN53YHL272QGKF32L7XEDNZ2S6OSUFK3NFBGG5M)  | Mainnet |
-| [`CBRV5ZEQSSCQ4FFO64OF46I3UASBVEJNE5C2MCFWVIXL4Z7DMD7PJJMF`](https://stellar.expert/explorer/testnet/contract/CBRV5ZEQSSCQ4FFO64OF46I3UASBVEJNE5C2MCFWVIXL4Z7DMD7PJJMF) | Testnet |
-
-Para aprender más sobre este oracle, consulta sus [documentación](https://docs.bandchain.org/) o visita su [GitHub](https://github.com/bandprotocol/band-std-reference-contracts-soroban).
-
-## [Oráculos DIA](https://www.diadata.org/)
-
-DIA es un proveedor de oráculos cruzados que obtiene datos de mercado granulares de diversos exchanges, incluidos CEXs y DEXs. Su obtención de datos es exhaustiva, lo que permite una transparencia y personalización sin igual para flujos de precios resilientes para más de 20.000 activos. Su procesamiento y entrega de datos versátiles aseguran adaptabilidad y confiabilidad para cualquier aplicación descentralizada.
-
-Las dapps que se construyan en Soroban pueden utilizar oráculos DIA para obtener información actualizada sobre los precios de los activos. Estos oráculos desplegados son adecuados para su uso en entornos de producción. Vienen con una lista de activos admitidos y configuraciones. Sin embargo, están disponibles oráculos personalizados con un conjunto diferente de activos y configuraciones. Si necesitas algo que se ajuste más a tus necesidades, puedes [contactar a DIA](https://docs.diadata.org/introduction/request-an-oracle) para hacer una solicitud.
-
-### Contratos DIA desplegados
-
-| Dirección                                                                                                                                                               | Fuente de datos      | Red     |
-| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- | ------- |
-| [`CAEDPEZDRCEJCF73ASC5JGNKCIJDV2QJQSW6DJ6B74MYALBNKCJ5IFP4`](https://stellar.expert/explorer/testnet/contract/CAEDPEZDRCEJCF73ASC5JGNKCIJDV2QJQSW6DJ6B74MYALBNKCJ5IFP4) | CEXs y DEXs externos | Testnet |
-
-Aprende más sobre la [obtención de datos](https://docs.diadata.org/use-nexus-product/nexus/data-sourcing) y la [computación de datos](https://docs.diadata.org/use-nexus-product/nexus/data-computation) de DIA.
-
-### Especificación del oráculo
-
-#### Flujos de precios incluidos
-
-El oráculo DIA en Stellar incluye flujos de precios para los siguientes activos:
-
-| Activo | Blockchain | Dirección                                  | Visión General de los Mercados                                                                                         |
-| ------ | ---------- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
-| USDC   | Ethereum   | 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 | [Información sobre USDC](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
-| BTC    | Bitcoin    | 0x0000000000000000000000000000000000000000 | [Información sobre BTC](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
-| DIA    | Ethereum   | 0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419 | [Información sobre DIA](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |
-
-#### Metodología de precios
-
-El punto de precio final para cada activo se calcula computando la información de comercio de los activos a través de múltiples DEXs y CEXs. Esto se hace utilizando una metodología de Precio Promedio Ponderado por Volumen con Rango Intercuartil (VWAPIR). [Aprende más sobre VWAPIR](https://docs.diadata.org/products/token-price-feeds/exchangeprices/vwapir-volume-weighted-average-price-with-interquartile-range-filter).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/README.mdx
deleted file mode 100644
index 5a5efe32b9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Enciclopedia
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Explicaciones y artículos detallados sobre temas específicos de interés.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/README.mdx
deleted file mode 100644
index 3261ecf8e3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/README.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Configuración de Red
-sidebar_position: 80
-draft: true
----
-
-import DocCardList from "@theme/DocCardList";
-
-Explicaciones y artículos detallados sobre temas específicos de interés.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/federation.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/federation.mdx
deleted file mode 100644
index c4770d054f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/federation.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Federación
-sidebar_position: 20
-draft: true
----
-
-El [Stellar federation protocol](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0002.md) mapea direcciones Stellar a un identificador similar a un correo electrónico que proporciona más información sobre un usuario dado. Es una manera para que el software cliente Stellar resuelva direcciones similares a correos electrónicos como `nombre*tu dominio.com` en IDs de cuenta como: `GCCVPYFOHY7ZB7557JKENAX62LUAPLMGIWNZJAFV2MITK6T32V37KEJU`. Las direcciones federadas proporcionan una manera fácil para que los usuarios compartan detalles de pago utilizando una sintaxis que interopera entre diferentes dominios y proveedores.
-
-## Direcciones federadas
-
-Las direcciones federadas Stellar se dividen en dos partes separadas por el carácter asterisco (`*`): el nombre de usuario y el dominio. Por ejemplo: `jed*stellar.org:`
-
-- `jed` es el nombre de usuario
-- `stellar.org` es el dominio
-
-El dominio puede ser cualquier nombre de dominio válida según el RFC 1035. El nombre de usuario está limitado a UTF-8 imprimible con espacios en blanco y los siguientes caracteres excluidos: `<*,>`.
-
-Nota que el símbolo `@` está permitido en el nombre de usuario. Esto significa que puedes usar direcciones de correo electrónico en el nombre de usuario de una dirección federada. Por ejemplo: `maria@gmail.com*stellar.org`.
-
-## Admitir federación
-
-Para admitir la federación, primero, crea un archivo stellar.toml y publícalo en `https://TU_DOMINIO/.well-known/stellar.toml`. Instrucciones completas para hacer eso se pueden encontrar en la especificación de stellar.toml (también conocida como SEP-1).
-
-En general, querrás incluir cualquier y toda la información sobre tu integración Stellar en tu stellar.toml. Para admitir la federación específicamente, necesitas añadir una sección `FEDERATION_SERVER` a tu archivo stellar.toml que indique a otras personas la URL de tu endpoint de federación.
-
-Por ejemplo: `FEDERATION_SERVER="https://api.tudominio.com/federation"`
-
-**Nota:** tu servidor de federación debe usar el protocolo https
-
-Una vez que hayas publicado la ubicación de tu servidor de federación, implementa un endpoint HTTP de federación que acepte una solicitud HTTP GET y emita respuestas de la forma detallada a continuación:
-
-Para facilitar la configuración de un servidor de federación, puedes usar la [implementación de referencia](https://github.com/stellar/go/tree/master/services/federation) diseñada para ser integrada en tu infraestructura existente.
-
-## Solicitudes de federación
-
-Puedes usar el endpoint de federación para buscar un ID de cuenta si tienes una dirección Stellar. También puedes hacer federación inversa y buscar una dirección Stellar desde un ID de cuenta o un ID de transacción. Esto es útil para ver quién te ha enviado un pago.
-
-Las solicitudes de federación son solicitudes HTTP GET con la siguiente forma:
-
-`?q=<string to look up>&type=<name,forward,id,txid>`
-
-Tipos admitidos:
-
-- Ejemplo de nombre: https://TU_SERVIDOR_DE_FEDERACION/federation?q=jed\*stellar.org&type=name
-- Reenvío Utilizado para reenviar el pago a una red diferente o institución financiera diferente. Los otros parámetros de la consulta variarán dependiendo de qué tipo de institución es el destino final del pago y qué es lo que admite tu anchor de reenvío. Tu archivo stellar.toml debe especificar qué parámetros esperas en una solicitud de federación de reenvío. Si no puedes reenviar o los otros parámetros en la solicitud son incorrectos, deberías devolver un error al respecto. Ejemplo de solicitud: https://TU_SERVIDOR_DE_FEDERACION/federation?type=forward&forward_type=bank_account&swift=BOPBPHMM&acct=2382376
-- Id Not supported by all federation servers. La federación inversa devolverá el registro de federación de la dirección Stellar asociada con el ID de cuenta dado. En algunos casos, esto es ambiguo. For instance, if an anchor sends transactions on behalf of its users, the account id will be of the anchor, and the federation server won’t be able to resolve the particular user that sent the transaction. En casos como ese, puede que necesites usar txid en su lugar. Ejemplo: https://TU_SERVIDOR_DE_FEDERACION/federation?q=GD6WU64OEP5C4LRBH6NK3MHYIA2ADN6K6II6EXPNVUR3ERBXT4AN4ACD&type=id
-- Txid No admitido por todos los servidores de federación. Devolverá el registro de federación del remitente de la transacción si lo conoce el servidor. Ejemplo: https://TU_SERVIDOR_DE_FEDERACION/federation?q=c1b368c00e9852351361e07cc58c54277e7a6366580044ab152b8db9cd8ec52a&type=txid
-
-## Respuesta de federación
-
-El servidor de federación debe responder con un código de estado HTTP apropiado, encabezados, y una respuesta JSON.
-
-Debes habilitar CORS en el servidor de federación para que los clientes puedan enviar solicitudes desde otros sitios. El siguiente encabezado HTTP debe ser establecido para todas las respuestas del servidor de federación.
-
-`Access-Control-Allow-Origin: *`
-
-Cuando se haya encontrado un registro, la respuesta debe devolver un código de estado http 200 OK y el siguiente cuerpo JSON:
-
-```json
-{
-  "stellar_address": <username*domain.tld>,
-  "account_id": <account_id>,
-  "memo_type": <"text", "id" , or "hash"> *optional*
-  "memo": <memo to attach to any payment. if "hash" type then will be base64 encoded> *optional*
-}
-```
-
-Si se necesita una redirección, el servidor de federación debe devolver un código de estado http 3xx y redirigir inmediatamente al usuario a la URL correcta utilizando el encabezado Location.
-
-Cuando no se haya encontrado un registro, se debe devolver un código de estado http 404 Not Found. Cualquier otro código de estado http será considerado un error. El cuerpo debe contener detalles de error:
-
-```json
-{
-  "detail": "extra details provided by the federation server"
-}
-```
-
-## Buscar proveedor de federación a través de una entrada de dominio principal
-
-Las cuentas pueden tener un dominio principal especificado opcionalmente. Esto permite que una cuenta especifique programáticamente el proveedor de federación principal para esa cuenta.
-
-## Almacenamiento en caché
-
-No deberías almacenar en caché las respuestas de los servidores de federación. Algunas organizaciones pueden generar IDs aleatorios para proteger la privacidad de sus usuarios. Esos IDs pueden cambiar con el tiempo.
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
deleted file mode 100644
index 7f4c3eefea..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/inflation.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Inflación
-sidebar_position: 40
-draft: true
----
-
-La operación de inflación está obsoleta. Aquí está el porqué:
-
-Antes del Protocolo 12, Stellar tenía un mecanismo de inflación integrado diseñado para permitir a los titulares de cuentas dirigir colectivamente los lumens generados por la inflación hacia proyectos desarrollados en Stellar.
-
-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)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/ledger-headers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/ledger-headers.mdx
deleted file mode 100644
index 44d005c0c7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/ledger-headers.mdx
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: Encabezados de Ledger
-sidebar_position: 30
-draft: true
----
-
-Cada ledger tiene un encabezado que hace referencia a los datos en ese ledger y en el ledger anterior. Estas referencias son hashes criptográficos del contenido que se comportan como punteros en estructuras de datos típicas, pero con garantías de seguridad adicionales. Piensa en una cadena de ledger histórica como una lista vinculada de encabezados de ledger. El tiempo fluye hacia adelante de izquierda a derecha, los hashes apuntan hacia atrás en el tiempo, de derecha a izquierda. Cada hash en la cadena vincula un ledger a su ledger anterior, lo que autentica toda la historia de ledgers en su pasado:
-
-```mermaid
-flowchart RL
-    subgraph genesis["Genesis"]
-        direction LR
-        prev1["Prev: none"]
-        state1["Genesis state"]
-    end
-
-    subgraph block2["Ledger 2"]
-        prev2["Prev: hash(Genesis)"]
-        state2["Ledger 2<br/>transactions<br/>and state"]
-    end
-
-    subgraph block3["Ledger 3"]
-        prev3["Prev: hash(Ledger 2)"]
-        state3["Ledger 3<br/>transactions<br/>and state"]
-    end
-
-    subgraph dotdot["..."]
-    end
-
-    subgraph blockn["Ledger N"]
-        prevn["Prev: hash(Ledger N-1)"]
-        staten["Ledger N<br/>transactions<br/>and state"]
-    end
-
-
-    genesis ~~~ block2 ~~~ block3 ~~~ dotdot ~~~ blockn
-    prev2 --> genesis
-    prev3 --> block2
-    dotdot --> block3
-    prevn --> dotdot
-
-```
-
-El ledger génesis tiene un número de secuencia de 1. El ledger que sigue directamente a un ledger con número de secuencia `N` tiene un número de secuencia de `N+1`. El ledger `N+1` contiene un hash del ledger `N` en su campo de ledger anterior.
-
-## Campos del encabezado del ledger
-
-### Versión
-
-La versión del protocolo de este ledger.
-
-### Hash del ledger anterior
-
-Hash del ledger anterior.
-
-### Valor SCP
-
-Durante el consenso, todos los nodos validadores en la red ejecutan SCP y acuerdan un valor particular, que es un conjunto de transacciones que aplicarán a un ledger. Este valor se almacena aquí y en los siguientes tres campos (hash del conjunto de transacciones, tiempo de cierre y actualizaciones).
-
-### Hash del conjunto de transacciones
-
-Hash del conjunto de transacciones aplicado al ledger anterior.
-
-### Tiempo de cierre
-
-El tiempo de cierre es una marca de tiempo UNIX que indica cuándo se cierra el ledger. Su precisión depende del reloj del sistema del validador que propone el bloque. En consecuencia, SCP puede confirmar un tiempo de cierre que se retrasa unos segundos o que está hasta 60 segundos adelantado. Es estrictamente monótono: está garantizado que sea mayor que el tiempo de cierre de un ledger anterior.
-
-### Actualizaciones
-
-Cómo la red ajusta valores generales (como la tarifa base) y acuerda cambios a nivel de red (como cambiar a una nueva versión del protocolo). Este campo suele estar vacío. Cuando hay una actualización a nivel de red, el SDF informará y ayudará a coordinar a los participantes utilizando el canal #validators en el Dev Discord y el grupo de Google Stellar Validators.
-
-### Hash del resultado del conjunto de transacciones
-
-Hash de los resultados de aplicar el conjunto de transacciones. Estos datos no son necesarios para validar los resultados de las transacciones. Sin embargo, facilita a las entidades la validación del resultado de una transacción dada sin tener que aplicar el conjunto de transacciones al ledger anterior.
-
-### Hash de la lista de objetos
-
-Hash de todos los objetos en este ledger. La estructura de datos que contiene todos los objetos se llama la lista de objetos.
-
-### Secuencia de ledger
-
-El número de secuencia de este ledger.
-
-### Total de monedas
-
-Número total de lumens en existencia.
-
-### Fondo de tarifas
-
-Número de lumens que se han pagado en tarifas. Nota que esto está denominado en lumens, a pesar de que el campo de tarifa de una transacción está en stroops.
-
-### Secuencia de inflación
-
-Número de veces que se ha ejecutado la inflación. Nota: la operación de inflación fue desaprobada cuando los validadores votaron para actualizar la red a Protocolo 12 el 28/10/2019. Por lo tanto, la inflación ya no se ejecuta, por lo que este número de secuencia ya no cambia.
-
-### Fondo de ID
-
-El último ID global utilizado. Estos IDs se utilizan para generar objetos.
-
-### Número máximo de transacciones
-
-El número máximo de operaciones que los validadores han acordado procesar en un ledger dado. Si se envían más transacciones que este número, la red entrará en modo de precios de sobrecarga. Para más información sobre precios de sobrecarga y estrategias de tarifas, consulta nuestra [sección de tarifas](../../fundamentals/fees-resource-limits-metering.mdx).
-
-### Tarifa base
-
-La tarifa que la red cobra por operación en una transacción. Calculada en stroops. Consulta la [sección de tarifas](../../fundamentals/fees-resource-limits-metering.mdx) para más información.
-
-### Reserva base
-
-La reserva que la red utiliza al calcular el saldo mínimo de una cuenta.
-
-### Lista de salto
-
-Hashes de ledgers en el pasado. Intencionado para acelerar el acceso a ledgers pasados sin retroceder ledger por ledger. Actualmente no utilizado.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/network-passphrases.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/network-passphrases.mdx
deleted file mode 100644
index 15892d3016..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/network-passphrases.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Frases de la Red
-sidebar_position: 10
-draft: true
----
-
-La Mainnet, Testnet y Futurenet de Stellar tienen cada una su propia frase única. Estas se utilizan al validar firmas en una transacción dada. Si firmas una transacción para una red pero la envías a otra, no se considerará válida. Por convención, el formato de una frase es ‘`[Nombre de la Red] ; [Mes de Creación] [Año de Creación]`’.
-
-Las frases actuales para la Mainnet, Testnet y Futurenet de Stellar son:
-
-- Mainnet: '`Public Global Stellar Network ; Septiembre 2015`'
-- Testnet: '`Test SDF Network ; Septiembre 2015`'
-- Futurenet: '`Test SDF Future Network ; Octubre 2022`'
-
-Las frases sirven para dos propósitos principales: (1) utilizadas como la semilla para la cuenta raíz (clave maestra de la red) en el génesis y (2) utilizadas para crear hashes de transacciones, que son finalmente lo que se firma con la clave secreta de cada firmante en un sobre de transacción; esto te permite verificar que una transacción fue destinada para una red específica por sus firmantes.
-
-Muchos SDK tienen las frases codificadas para las redes de Stellar. Si estás ejecutando una red privada, tendrás que pasar manualmente una frase que se usará cada vez que se generen hashes de transacciones. Todos los SDK oficiales de Stellar permiten usar una red con una frase personalizada.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/sdex/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/sdex/README.mdx
deleted file mode 100644
index 6d2c6c906e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/sdex/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: SDEX
-sidebar_position: 90
----
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools.mdx
deleted file mode 100644
index 9e14550e62..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools.mdx
+++ /dev/null
@@ -1,624 +0,0 @@
----
-title: "Fondos de Liquidez en el DEX de Stellar: Proporcionar Liquidez y Habilitar Intercambios de Activos"
-sidebar_label: "Liquidez en Stellar: SDEX y Fondos de Liquidez"
-description: Aprende cómo los fondos de liquidez habilitan el comercio en el DEX de Stellar. Entiende cómo funcionan, proporcionan liquidez y habilitan intercambios de activos descentralizados en la red.
----
-
-# Liquidez en Stellar: SDEX y Fondos de Liquidez
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-:::note
-
-Esta sección está específicamente dirigida a la liquidez respecto al AMM y SDEX incorporados en el protocolo Stellar y no incluye información sobre contratos inteligentes.
-
-:::
-
-Los usuarios pueden negociar y convertir activos en la red Stellar mediante el uso de pagos por rutas a través del exchange descentralizado de Stellar y los fondos de liquidez.
-
-En esta sección, hablaremos sobre el SDEX y los fondos de liquidez. Para aprender cómo funcionan juntos para ejecutar transacciones, consulta nuestra [Entrada de Enciclopedia de Pagos por Rutas](../transactions-specialized/path-payments.mdx).
-
-## SDEX
-
-La red Stellar actúa como un exchange descentralizado distribuido que permite a los usuarios comerciar y convertir activos con las operaciones de [Administrar Oferta de Compra](../../../data/apis/horizon/api-reference/resources/operations/object/buy-offer.mdx) y [Administrar Oferta de Venta](../../../data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx). El ledger de Stellar almacena tanto los saldos mantenidos por las cuentas de usuario como las órdenes que crean las cuentas de usuario para comprar o vender activos.
-
-### Libros de órdenes
-
-Stellar utiliza libros de órdenes para operar su exchange descentralizado.
-
-Un libro de órdenes es un registro de órdenes pendientes en una red, y cada registro se encuentra entre dos activos (trigo y ovejas, por ejemplo). El libro de órdenes para este par de activos registra cada cuenta que quiere vender trigo por ovejas y cada cuenta que quiere vender ovejas por trigo. En finanzas tradicionales, la compra se expresa como una orden de «oferta» y la venta se expresa como una orden de «demanda» (las órdenes de demanda también se llaman ofertas).
-
-Un par de notas sobre los libros de órdenes en Stellar:
-
-- El término “ofertas” generalmente se refiere específicamente a las órdenes de demanda. En Stellar, sin embargo, todas las órdenes se almacenan como ventas, es decir, el sistema convierte automáticamente las órdenes de oferta en órdenes de demanda. Debido a esto, los términos “oferta” y “orden” se utilizan de manera intercambiable en el ecosistema de Stellar.
-- Los libros de órdenes contienen todas las órdenes que son aceptables para las partes de ambos lados para realizar un intercambio.
-- Algunos activos tendrán un libro de órdenes pequeño o inexistente entre ellos. En estos casos, Stellar facilita pagos por rutas, de los cuales hablaremos más adelante.
-
-Para ver un gráfico de libro de órdenes, consulta la [Página de Wikipedia sobre Libros de Órdenes](https://en.wikipedia.org/wiki/Order_book). Además, hay muchos tutoriales en video y artículos que pueden ayudarte a entender cómo funcionan los libros de órdenes con mayor detalle.
-
-### Órdenes
-
-Una cuenta puede crear órdenes para comprar o vender activos utilizando las operaciones Gestionar Oferta de Compra, Gestionar Oferta de Venta o Orden Pasiva. La cuenta debe poseer el activo que desea intercambiar y debe confiar en el emisor del activo que está tratando de comprar.
-
-Las órdenes en Stellar se comportan como órdenes limitadas en los mercados tradicionales. Cuando una cuenta inicia una orden, se verifica en relación con el libro de órdenes existente para ese par de activos. Si la orden enviada es una orden comercial (para una orden de compra comercial, el precio límite está a o por encima del precio de venta; para una orden de venta comercial, el precio límite está a o por debajo del precio de oferta), se llena al precio de orden existente por la cantidad disponible a ese precio. Si la orden no es comercial (es decir, no cruza una orden existente), la orden se guarda en el libro de órdenes hasta que sea consumida por otra orden, consumida por un pago por ruta, o cancelada por la cuenta que creó la orden.
-
-Cada orden constituye una obligación de venta para el activo que se vende y una obligación de compra para el activo que se compra. Estas obligaciones se almacenan en la cuenta (para lumens) o en la línea de confianza (para otros activos) que posee la cuenta creando la orden. Cualquier operación que cause que una cuenta no pueda cumplir sus obligaciones, como enviar demasiado saldo, fallará. Esto garantiza que cualquier orden en el libro de órdenes se pueda ejecutar por completo.
-
-Las órdenes se ejecutan bajo la prioridad de precio y tiempo, lo que significa que las órdenes se ejecutarán primero por precio; para las órdenes colocadas al mismo precio, se da prioridad a la orden que se ingresó primero y se ejecuta antes que la más nueva.
-
-### Precio y operaciones
-
-Cada orden en Stellar se cotiza con un precio asociado y se representa como una proporción de los dos activos en la orden, uno siendo el “activo de cotización” y el otro el “activo base”. Esto es para asegurar que no haya pérdida de precisión al representar el precio de la orden (en oposición a almacenar la fracción como un número de punto flotante).
-
-Los precios se especifican como un par {`numerador`, `denominador`} con ambos componentes de la fracción representados como enteros con signo de 32 bits. El numerador se considera el activo base, y el denominador se considera el activo de cotización. Al expresar un precio de “Activo A en términos de Activo B”, la cantidad de B es el denominador (y por lo tanto el activo de cotización) y A es el numerador (y por lo tanto el activo base). Como una buena regla general, es generalmente correcto pensar en el activo base que se está comprando/vendiendo (en términos del activo de cotización).
-
-#### Gestionar Oferta de Compra
-
-Al crear una orden de compra en Stellar a través de la operación Gestionar Oferta de Compra, el precio se especifica como 1 unidad de la moneda base (el activo que se compra), en términos del activo de cotización (el activo que se está vendiendo). Por ejemplo, si estás comprando 100 XLM a cambio de 20 USD, especificarías el precio como {20, 100}, que equivaldría a 5 XLM por 1 USD (o \$.20 por XLM).
-
-#### Gestionar Oferta de Venta
-
-Al crear una orden de venta en Stellar a través de la operación Gestionar Oferta de Venta, el precio se especifica como 1 unidad de la moneda base (el activo que se vende), en términos del activo de cotización (el activo que se está comprando). Por ejemplo, si estás vendiendo 100 XLM a cambio de 40 USD, especificarías el precio como {40, 100}, que equivaldría a <b>2,5</b> XLM por 1 USD (o \$.40 por XLM).
-
-#### Orden Pasiva
-
-Las órdenes pasivas permiten que los mercados tengan un diferencial cero. Si deseas intercambiar USD del ancla A por USD del ancla B a un precio de 1:1, puedes crear dos órdenes pasivas para que las dos órdenes no se llenen entre sí.
-
-Una orden pasiva es una orden que no se ejecuta contra una orden de contraparte comercial con el mismo precio. Solo se llenará si los precios no son iguales. Por ejemplo, si la mejor orden para comprar BTC por XLM tiene un precio de 100XLM/BTC, y haces una oferta pasiva para vender BTC a 100XLM/BTC, tu oferta pasiva no toma esa oferta existente. Si en su lugar haces una oferta pasiva para vender BTC a 99XLM/BTC, esta cruzaría la oferta existente y se llenaría a 100XLM/BTC.
-
-Una cuenta puede realizar una orden de venta pasiva a través de la operación Crear Oferta de Venta Pasiva.
-
-### Comisiones
-
-El precio de orden que establezcas es independiente de la tarifa que pagas por presentar esa orden en una transacción. Las tarifas siempre se pagan en XLM, y las especificas como un parámetro separado al presentar la orden a la red.
-
-Para aprender más sobre las tarifas de transacción, consulta nuestra sección sobre [Tarifas](../../fundamentals/fees-resource-limits-metering.mdx).
-
-## Fondos de liquidez
-
-Los fondos de liquidez permiten la creación automática de mercados en la red Stellar. La liquidez se refiere a cuán fácilmente y de manera económica se puede convertir un activo en otro.
-
-### Creadores de Mercados Automatizados (AMMs)
-
-En lugar de depender de las órdenes de compra y venta de exchanges descentralizados, los AMMs mantienen activos en un ecosistema líquido 24/7 utilizando fondos de liquidez.
-
-Los creadores de mercados automatizados proporcionan liquidez utilizando una ecuación matemática. Los AMMs mantienen dos activos diferentes en un fondo de liquidez, y las cantidades de esos activos (o reservas) son entradas para esa ecuación (Activo A \* Activo B = k). Si un AMM mantiene más de los activos de reserva, los precios de los activos se moverán menos en respuesta a un intercambio.
-
-#### Precios de AMM
-
-Los AMMs están dispuestos a realizar algunas operaciones y no están dispuestos a realizar otras. Por ejemplo, si 1 EUR = 1.17 USD, entonces el AMM podría estar dispuesto a vender 1 EUR por 1.18 USD y no estar dispuesto a vender 1 EUR por 1.16 USD. Para determinar qué operaciones son aceptables, el AMM hace cumplir un invariante. Hay muchos invariantes posibles, y Stellar hace cumplir un invariante de producto constante, por lo que se conoce como un creador de mercados de producto constante. Esto significa que los AMMs en Stellar nunca deben permitir que el producto de las reservas disminuya.
-
-Por ejemplo, supongamos que las reservas actuales en el fondo de liquidez son 1000 EUR y 1170 USD, lo que implica un producto de <b>1.170.000</b>. Vender 1 EUR por 1.18 USD sería aceptable porque eso dejaría reservas de 999 EUR y 1171.18 USD, lo que implica un producto de <b>1.170.008,82</b>. Pero vender 1 EUR por 1.16 USD no sería aceptable porque eso dejaría reservas de 999 EUR y 1171.16 USD, lo que implica un producto de <b>1.169.988,84</b>.
-
-Los AMMs deciden tasas de cambio en base a la proporción de reservas en el fondo de liquidez. Si esta proporción es diferente a la verdadera tasa de cambio, los arbitrajistas intervendrán y comerciarán con el AMM a un precio favorable. Este comercio de arbitraje mueve la proporción de las reservas de regreso hacia la verdadera tasa de cambio.
-
-Los AMMs cobran tarifas en cada operación, que son un porcentaje fijo del monto comprado por el AMM. Por ejemplo, si un creador de mercados automatizado vende 100 EUR por 118 USD, entonces la tarifa se cobra sobre los USD. La tarifa es de 30 bps, que equivale a <b>0,30%</b>. Si realmente quisieras realizar este exchange, necesitarías pagar alrededor de <b>118,355</b> USD por 100 EUR. El creador de mercados automatizado tiene en cuenta las tarifas en el invariante de producto constante, por lo que en realidad el producto de las reservas crece después de cada operación.
-
-### Participación en el fondo de liquidez
-
-Cualquier participante elegible puede depositar activos en un fondo de liquidez y, a cambio, recibirá acciones del fondo que representan su propiedad de ese activo. Si hay 150 acciones totales del fondo y un usuario posee 30, tiene derecho a retirar el 20% del activo del fondo de liquidez en cualquier momento.
-
-Las acciones del fondo son similares a otros activos en Stellar, pero no pueden ser transferidas. Solo puedes aumentar el número de acciones del fondo que posees depositando en un fondo de liquidez con el `LiquidityPoolDespositOp` y disminuir el número de acciones del fondo que posees retirándote de un fondo de liquidez con `LiquidityPoolWithdrawOp`.
-
-Una acción del fondo tiene dos representaciones. La representación completa se utiliza con `ChangeTrustOp` y la representación hash se utiliza en todos los demás casos. Al construir la representación del activo de una acción del fondo, los activos deben estar en orden lexicográfico. Por ejemplo, A-B está en el orden correcto, pero B-A no. Esto resulta en una representación canónica de una acción del fondo.
-
-Los AMMs cobran una tarifa en todas las operaciones y los participantes en el fondo de liquidez reciben una parte de la tarifa proporcional a su participación de los activos en el fondo de liquidez. Los participantes recogen estas tarifas cuando retiran sus activos del fondo. La tasa de tarifa en Stellar es 30 bps, que equivale a <b>0,30%</b>. Estas tarifas son completamente independientes de las tarifas de la red.
-
-### Líneas de confianza
-
-Los usuarios necesitan establecer líneas de confianza para tres activos diferentes para participar en un fondo de liquidez: ambos activos de reserva (a menos que uno de ellos sea XLM) y la acción del fondo.
-
-Una cuenta necesita una línea de confianza para cada acción del fondo que desea poseer. No es posible depositar en un fondo de liquidez sin una línea de confianza para la acción correspondiente del fondo. Las líneas de confianza de acciones del fondo difieren de las líneas de confianza de otros activos en algunas maneras:
-
-1. Una línea de confianza para acciones del fondo no puede ser creada a menos que la cuenta ya tenga líneas de confianza que estén autorizadas o autorizadas para mantener obligaciones por los activos en el fondo de liquidez. Consulta a continuación para más información sobre cómo la autorización impacta las líneas de confianza de acciones del fondo.
-2. Una línea de confianza para acciones del fondo requiere 2 reservas base en vez de 1. Por ejemplo, una cuenta (2 reservas base) con una línea de confianza para el activo A (1 reserva base), una línea de confianza para el activo B (1 reserva base), y una línea de confianza para la acción A-B (2 reservas base) tendría un requerimiento de reserva de 6 reservas base.
-
-### Autorización
-
-Las líneas de confianza de acciones del fondo no pueden ser autorizadas o desautorizadas de forma independiente. En cambio, la autorización de una línea de confianza de acciones del fondo se deriva de las líneas de confianza para los activos en el fondo de liquidez. Este diseño es necesario porque un fondo de liquidez puede contener activos de dos emisores diferentes, y ambos emisores deberían tener voz sobre si la línea de confianza de acciones del fondo es autorizada o no.
-
-Hay algunas posibilidades con respecto a la autorización. El comportamiento de la línea de confianza de acciones A-B se determina de acuerdo con la siguiente tabla:
-
-| ESCENARIO                                                                                                                                | COMPORTAMIENTO                                                                  |
-| ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
-| Las líneas de confianza para A y B están completamente autorizadas                                                                       | Sin restricciones en el depósito y retirada                                     |
-| La línea de confianza para A está completamente autorizada, pero la línea de confianza para B está autorizada para mantener obligaciones | Las líneas de confianza para A y B están autorizadas para mantener pasivos      |
-| La línea de confianza para B está completamente autorizada, pero la línea de confianza para A está autorizada para mantener obligaciones | Las líneas de confianza para A y B están autorizadas para mantener obligaciones |
-| Las líneas de confianza para A y B están autorizadas para mantener obligaciones                                                          | Las líneas de confianza para A y B están autorizadas para mantener obligaciones |
-| La línea de confianza para A no está autorizada o no existe                                                                              | La línea de confianza de acciones del fondo no existe                           |
-| La línea de confianza para B no está autorizada o no existe                                                                              | La línea de confianza de acciones del fondo no existe                           |
-
-Si el emisor de A o B revoca la autorización, entonces la cuenta se retirará automáticamente de todos los fondos de liquidez que contengan ese activo y esas líneas de confianza de acciones del fondo se eliminarán. Decimos que estas acciones del fondo han sido canjeadas. Por ejemplo, si la cuenta participa en los fondos de liquidez A-B, A-C y B-C, y el emisor de A revoca la autorización, entonces la cuenta canjeará de A-B y A-C pero no de B-C. Por cada línea de confianza de acción del fondo canjeada, se creará un Balance Reclamable para cada activo contenido en el fondo si hay un saldo que se está retirando y el reclamante no es el emisor de ese activo. El reclamante del Balance Reclamable será el propietario de la línea de confianza de acción del fondo eliminada, y el patrocinador del Balance Reclamable será el patrocinador de la línea de confianza de acción del fondo eliminada. El BalanceID de cada Balance Reclamable es el hash SHA-256 del `revokeID`.
-
-### Operaciones
-
-Hay dos operaciones que facilitan la participación en un fondo de liquidez: `LiquidityPoolDeposit` y `LiquidityPoolWithdraw`. Utiliza `LiquidityPoolDeposit` para comenzar a proporcionar liquidez al mercado. Utiliza `LiquidityPoolWithdraw` para dejar de proporcionar liquidez al mercado.
-
-Sin embargo, los usuarios no necesitan participar en el fondo para aprovechar lo que ofrece: una forma fácil de intercambiar dos activos. Para eso, solo usa `PathPaymentStrictReceive` o `PathPaymentStrictSend`. Si tu aplicación ya está utilizando pagos por rutas, entonces no necesitas cambiar nada para que los usuarios aprovechen los precios disponibles en los fondos de liquidez.
-
-### Ejemplos
-
-Aquí cubriremos la participación básica en fondos de liquidez y la consulta.
-
-#### Prólogo
-
-Para todos los ejemplos siguientes, estaremos trabajando con tres cuentas financiadas de Testnet. Si deseas seguir, genera algunos keypairs y financíalos a través del friendbot.
-
-El siguiente código configura las cuentas y define algunas funciones auxiliares. Estos deberían ser familiares si has experimentado con otros ejemplos como los clawbacks.
-
-<CodeExample>
-
-```js
-const sdk = require("stellar-sdk");
-const BigNumber = require("bignumber.js");
-
-let server = new sdk.Server("https://horizon-testnet.stellar.org");
-
-/// Helps simplify creating & signing a transaction.
-function buildTx(source, signer, ...ops) {
-  let tx = new sdk.TransactionBuilder(source, {
-    fee: sdk.BASE_FEE,
-    networkPassphrase: sdk.Networks.TESTNET,
-  });
-  ops.forEach((op) => tx.addOperation(op));
-  tx = tx.setTimeout(30).build();
-  tx.sign(signer);
-  return tx;
-}
-
-/// Returns the given asset pair in "protocol order."
-function orderAssets(A, B) {
-  return sdk.Asset.compare(A, B) <= 0 ? [A, B] : [B, A];
-}
-
-/// Returns all of the accounts we'll be using.
-function getAccounts() {
-  return Promise.all(kps.map((kp) => server.loadAccount(kp.publicKey())));
-}
-
-const kps = [
-  "SBGCD73TK2PTW2DQNWUYZSTCTHHVJPL4GZF3GVZMCDL6GYETYNAYOADN",
-  "SAAQFHI2FMSIC6OFPWZ3PDIIX3OF64RS3EB52VLYYZBX6GYB54TW3Q4U",
-  "SCJWYFTBDMDPAABHVJZE3DRMBRTEH4AIC5YUM54QGW57NUBM2XX6433P",
-].map((s) => sdk.Keypair.fromSecret(s));
-
-// kp0 issues the assets
-const kp0 = kps[0];
-const [A, B] = orderAssets(
-  ...[new sdk.Asset("A", kp0.publicKey()), new sdk.Asset("B", kp0.publicKey())],
-);
-
-/// Establishes trustlines and funds `recipientKps` for all `assets`.
-function distributeAssets(issuerKp, recipientKps, ...assets) {
-  return server.loadAccount(issuerKp.publicKey()).then((issuer) => {
-    const ops = recipientKps
-      .map((recipientKp) =>
-        assets.map((asset) => [
-          sdk.Operation.changeTrust({
-            source: recipientKp.publicKey(),
-            limit: "100000",
-            asset: asset,
-          }),
-          sdk.Operation.payment({
-            source: issuerKp.publicKey(),
-            destination: recipientKp.publicKey(),
-            amount: "100000",
-            asset: asset,
-          }),
-        ]),
-      )
-      .flat(2);
-
-    let tx = buildTx(issuer, issuerKp, ...ops);
-    tx.sign(...recipientKps);
-    return server.submitTransaction(tx);
-  });
-}
-
-function preamble() {
-  return distributeAssets(kp0, [kps[1], kps[2]], A, B);
-}
-```
-
-```python
-from decimal import Decimal
-from typing import List, Any, Dict
-
-from stellar_sdk import *
-
-server = Server("https://horizon-testnet.stellar.org")
-
-
-# Preamble
-def new_tx_builder(source: str) -> TransactionBuilder:
-    network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-    base_fee = 100
-    source_account = server.load_account(source)
-    builder = TransactionBuilder(
-        source_account=source_account, network_passphrase=network_passphrase, base_fee=base_fee
-    ).set_timeout(30)
-    return builder
-
-
-# Returns the given asset pair in "protocol order."
-def order_asset(a: Asset, b: Asset) -> List[Asset]:
-    return [a, b] if LiquidityPoolAsset.is_valid_lexicographic_order(a, b) else [b, a]
-
-
-secrets = [
-    "SBGCD73TK2PTW2DQNWUYZSTCTHHVJPL4GZF3GVZMCDL6GYETYNAYOADN",
-    "SAAQFHI2FMSIC6OFPWZ3PDIIX3OF64RS3EB52VLYYZBX6GYB54TW3Q4U",
-    "SCJWYFTBDMDPAABHVJZE3DRMBRTEH4AIC5YUM54QGW57NUBM2XX6433P",
-]
-kps = [Keypair.from_secret(secret=secret) for secret in secrets]
-
-# kp0 issues the assets
-kp0 = kps[0]
-asset_a, asset_b = order_asset(Asset("A", kp0.public_key), Asset("B", kp0.public_key))
-
-
-def distribute_assets(
-        issuer_kp: Keypair, recipient_kp: Keypair, assets: List[Asset]
-) -> Dict[str, Any]:
-    builder = new_tx_builder(issuer_kp.public_key)
-    for asset in assets:
-        builder.append_change_trust_op(
-            asset=asset, limit="100000", source=recipient_kp.public_key
-        ).append_payment_op(
-            destination=recipient_kp.public_key,
-            asset=asset,
-            amount="100000",
-            source=issuer_kp.public_key,
-        )
-
-    tx = builder.build()
-    tx.sign(issuer_kp)
-    tx.sign(recipient_kp)
-    resp = server.submit_transaction(tx)
-    return resp
-
-
-def preamble() -> None:
-    resp1 = distribute_assets(kp0, kps[1], [asset_a, asset_b])
-    resp2 = distribute_assets(kp0, kps[2], [asset_a, asset_b])
-    # ...
-```
-
-</CodeExample>
-
-Aquí, utilizamos `distributeAssets()` para establecer líneas de confianza y configurar saldos iniciales de dos activos personalizados (`A` y `B`, emitidos por `kp0`) para dos cuentas (`kp2` y `kp3`). Para que alguien participe en el fondo, debe establecer líneas de confianza con cada uno de los emisores de activos y con el activo de la acción del fondo (explicado a continuación).
-
-Nota la función auxiliar `orderAssets()` aquí. Las operaciones relacionadas con los fondos de liquidez se refieren arbitrariamente al par de activos como `A` y `B`; sin embargo, deben ser “ordenados” de modo que `A` < `B`. Este orden se define por el protocolo, pero sus detalles no deberían ser relevantes (si tienes curiosidad, está ordenado lexicográficamente por tipo de activo, código y luego emisor). Podemos utilizar los métodos de comparación integrados en los SDK (como `Asset.compare`) para asegurarnos de pasarlos en el orden correcto y evitar errores.
-
-#### Participación: Creación
-
-Primero, vamos a crear un fondo de liquidez para el par de activos definido en el prólogo. Esto implica establecer una línea de confianza hacia el fondo en sí:
-
-<CodeExample>
-
-```js
-const poolShareAsset = new sdk.LiquidityPoolAsset(
-  A,
-  B,
-  sdk.LiquidityPoolFeeV18,
-);
-
-function establishPoolTrustline(account, keypair, poolAsset) {
-  return server.submitTransaction(
-    buildTx(
-      account,
-      keypair,
-      sdk.Operation.changeTrust({
-        asset: poolAsset,
-        limit: "100000",
-      }),
-    ),
-  );
-}
-```
-
-```python
-pool_share_asset = LiquidityPoolAsset(asset_a=asset_a, asset_b=asset_b)
-
-
-def establish_pool_trustline(source: Keypair, pool_asset: LiquidityPoolAsset) -> Dict[str, Any]:
-    tx = (
-        new_tx_builder(source.public_key)
-            .append_change_trust_op(asset=pool_asset, limit="100000")
-            .build()
-    )
-    tx.sign(source)
-    return server.submit_transaction(tx)
-```
-
-</CodeExample>
-
-Esto permite a los participantes mantener acciones del fondo, lo que significa que ahora pueden realizar depósitos y retiradas.
-
-#### Participación: Depósitos
-
-Para trabajar con un fondo de liquidez, necesitas conocer su ID de antemano. Es un valor determinista, y solo puede existir un único fondo de liquidez para un par de activos particular, por lo que puedes calcularlo localmente a partir de los parámetros del fondo.
-
-<CodeExample>
-
-```js
-const poolId = sdk
-  .getLiquidityPoolId(
-    "constant_product",
-    poolShareAsset.getLiquidityPoolParameters(),
-  )
-  .toString("hex");
-
-function addLiquidity(source, signer, poolId, maxReserveA, maxReserveB) {
-  const exactPrice = maxReserveA / maxReserveB;
-  const minPrice = exactPrice - exactPrice * 0.1;
-  const maxPrice = exactPrice + exactPrice * 0.1;
-
-  return server.submitTransaction(
-    buildTx(
-      source,
-      signer,
-      sdk.Operation.liquidityPoolDeposit({
-        liquidityPoolId: poolId,
-        maxAmountA: maxReserveA,
-        maxAmountB: maxReserveB,
-        minPrice: minPrice.toFixed(7),
-        maxPrice: maxPrice.toFixed(7),
-      }),
-    ),
-  );
-}
-```
-
-```python
-pool_id = pool_share_asset.liquidity_pool_id
-
-
-def add_liquidity(
-        source: Keypair,
-        pool_id: str,
-        max_reserve_a: Decimal,
-        max_reserve_b: Decimal,
-) -> dict[str, Any]:
-    exact_price = max_reserve_a / max_reserve_b
-    min_price = exact_price - exact_price * Decimal("0.1")
-    max_price = exact_price + exact_price * Decimal("0.1")
-    tx = (
-        new_tx_builder(source.public_key)
-            .append_liquidity_pool_deposit_op(
-            liquidity_pool_id=pool_id,
-            max_amount_a=f"{max_reserve_a:.7f}",
-            max_amount_b=f"{max_reserve_b:.7f}",
-            min_price=min_price,
-            max_price=max_price,
-        )
-            .build()
-    )
-    tx.sign(source)
-    return server.submit_transaction(tx)
-```
-
-</CodeExample>
-
-Al depositar activos en un fondo de liquidez, necesitas definir tus límites de precio aceptables. En la función anterior, permitimos un margen de error de +/-10% respecto al “precio de mercado”. Este margen no es en modo alguno una recomendación y se elige solo para demostración.
-
-Ten en cuenta que también especificamos el monto máximo de cada reserva que estamos dispuestos a depositar. Esto, junto con los precios mínimos y máximos, ayuda a definir límites para el depósito, ya que siempre puede haber un cambio en la tasa de cambio entre el envío de la operación y su aceptación por la red.
-
-#### Participación: Retiros
-
-Si posees acciones de un fondo particular, puedes retirar reservas de él. La estructura de la operación refleja de cerca el depósito:
-
-<CodeExample>
-
-```js
-function removeLiquidity(source, signer, poolId, sharesAmount) {
-  return server
-    .liquidityPools()
-    .liquidityPoolId(poolId)
-    .call()
-    .then((poolInfo) => {
-      let totalShares = poolInfo.total_shares;
-      let minReserveA =
-        (sharesAmount / totalShares) * poolInfo.reserves[0].amount * 0.95;
-      let minReserveB =
-        (sharesAmount / totalShares) * poolInfo.reserves[1].amount * 0.95;
-
-      return server.submitTransaction(
-        buildTx(
-          source,
-          signer,
-          sdk.Operation.liquidityPoolWithdraw({
-            liquidityPoolId: poolId,
-            amount: sharesAmount,
-            minAmountA: minReserveA.toFixed(7),
-            minAmountB: minReserveB.toFixed(7),
-          }),
-        ),
-      );
-    });
-}
-```
-
-```python
-def remove_liquidity(
-        source: Keypair, pool_id: str, shares_amount: Decimal
-) -> dict[str, Any]:
-    pool_info = server.liquidity_pools().liquidity_pool(pool_id).call()
-    total_shares = Decimal(pool_info["total_shares"])
-    min_reserve_a = (
-            shares_amount
-            / total_shares
-            * Decimal(pool_info["reserves"][0]["amount"])
-            * Decimal("0.95")
-    ) #
-    min_reserve_b = (
-            shares_amount
-            / total_shares
-            * Decimal(pool_info["reserves"][1]["amount"])
-            * Decimal("0.95")
-    )
-    tx = (
-        new_tx_builder(source.public_key)
-            .append_liquidity_pool_withdraw_op(
-            liquidity_pool_id=pool_id,
-            amount=f"{shares_amount:.7f}",
-            min_amount_a=f"{min_reserve_a:.7f}",
-            min_amount_b=f"{min_reserve_b:.7f}",
-        )
-            .build()
-    )
-    tx.sign(source)
-    return server.submit_transaction(tx)
-```
-
-</CodeExample>
-
-Notar aquí que especificamos el monto mínimo. Al igual que con un pago de ruta de recepción estricta, especificamos que no estamos dispuestos a recibir menos de esta cantidad de cada activo del fondo. Esto define efectivamente un precio mínimo de retiro.
-
-#### Uniendo todo
-
-Finalmente, podemos combinar estas piezas para simular alguna participación en un fondo de liquidez. Haremos que todos depositen montos crecientes en el fondo, luego un participante retira sus acciones. Entre cada paso, recuperaremos el precio de mercado.
-
-<CodeExample>
-
-```js
-function main() {
-  return getAccounts()
-    .then((accounts) => {
-      return Promise.all(
-        kps.map((kp, i) => {
-          const acc = accounts[i];
-          const depositA = ((i + 1) * 1000).toString();
-          const depositB = ((i + 1) * 3000).toString(); // maintain a 1:3 ratio
-
-          return establishPoolTrustline(acc, kp, poolShareAsset)
-            .then(() => addLiquidity(acc, kp, poolId, depositA, depositB))
-            .then(() => getSpotPrice());
-        }),
-      ).then(() => accounts);
-    })
-    .then((accounts) => {
-      // kp1 takes all his/her shares out
-      return server
-        .accounts()
-        .accountId(kps[1].publicKey())
-        .call()
-        .then(({ balances }) => {
-          let balance = 0;
-          balances.every((bal) => {
-            if (
-              bal.asset_type === "liquidity_pool_shares" &&
-              bal.liquidity_pool_id === poolId
-            ) {
-              balance = bal.balance;
-              return false;
-            }
-            return true;
-          });
-          return balance;
-        })
-        .then((balance) =>
-          removeLiquidity(accounts[1], kps[1], poolId, balance),
-        );
-    })
-    .then(() => getSpotPrice());
-}
-
-function getSpotPrice() {
-  return server
-    .liquidityPools()
-    .liquidityPoolId(poolId)
-    .call()
-    .then((pool) => {
-      const [a, b] = pool.reserves.map((r) => r.amount);
-      const spotPrice = new BigNumber(a).div(b);
-      console.log(`Price: ${a}/${b} = ${spotPrice.toFormat(2)}`);
-    });
-}
-
-preamble().then(main);
-```
-
-```python
-def main():
-    deposit_a = Decimal(1000)
-    deposit_b = Decimal(3000)  # maintain a 1:3 ratio
-    establish_pool_trustline(kps[1], pool_share_asset)
-    add_liquidity(kps[1], pool_id, deposit_a, deposit_b)
-    get_spot_price()
-
-    deposit_a = Decimal(2000)
-    deposit_b = Decimal(6000)  # maintain a 1:3 ratio
-    establish_pool_trustline(kps[2], pool_share_asset)
-    add_liquidity(kps[2], pool_id, deposit_a, deposit_b)
-    get_spot_price()
-
-    # kp1 takes all his/her shares out
-    balance = 0
-    for b in server.accounts().account_id(kps[1].public_key).call()["balances"]:
-        if (
-                b["asset_type"] == "liquidity_pool_shares"
-                and b["liquidity_pool_id"] == pool_id
-        ):
-            balance = Decimal(b["balance"])
-            break
-    if not balance:
-        raise
-    remove_liquidity(kps[1], pool_id, balance)
-    get_spot_price()
-
-def get_spot_price():
-    resp = server.liquidity_pools().liquidity_pool(pool_id).call()
-    amount_a = resp["reserves"][0]["amount"]
-    amount_b = resp["reserves"][1]["amount"]
-    spot_price = Decimal(amount_a) / Decimal(amount_b)
-    print(f"Price: {amount_a}/{amount_b} = {spot_price:.7f}")
-
-if __name__ == '__main__':
-    preamble()
-    main()
-```
-
-</CodeExample>
-
-#### Observando la actividad del fondo de liquidez
-
-Puedes acceder a las transacciones, operaciones y efectos relacionados con un fondo de liquidez si deseas rastrear su actividad. Veamos cómo podemos rastrear los últimos depósitos en un fondo (supongamos que `poolId` se define como antes):
-
-<CodeExample>
-
-```js
-server
-  .operations()
-  .forLiquidityPool(poolId)
-  .call()
-  .then((ops) => {
-    ops.records
-      .filter((op) => op.type == "liquidity_pool_deposit")
-      .forEach((op) => {
-        console.log("Reserves deposited:");
-        op.reserves_deposited.forEach((r) =>
-          console.log(`    ${r.amount} of ${r.asset}`),
-        );
-        console.log("  for pool shares: ", op.shares_received);
-      });
-  });
-```
-
-```python
-def watch_liquidity_pool_activity():
-    for op in (
-        server.operations()
-        .for_liquidity_pool(liquidity_pool_id=pool_id)
-        .cursor("now")
-        .stream()
-    ):
-        if op["type"] == "liquidity_pool_deposit":
-            print("Reserves deposited:")
-            for r in op["reserves_deposited"]:
-                print(f"    {r['amount']} of {r['asset']}")
-            print(f"    for pool shares: {op['shares_received']}")
-        # ...
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/README.mdx
deleted file mode 100644
index 683d24c1a6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Transacciones (especializadas)
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/channel-accounts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
deleted file mode 100644
index 31443b6d98..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Cuentas de Canal
-sidebar_position: 10
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Las cuentas de canal proporcionan un método para enviar transacciones a la red a alta velocidad.
-
-Las transacciones de una cuenta siempre deben ser enviadas a la red en incrementos de un número de secuencia (a menos que se establezcan condiciones previas de número de secuencia mínimo). Esto puede causar problemas si estás enviando transacciones a alta velocidad, ya que pueden llegar a Stellar Core fuera de orden y luego rebotarán con un error de secuencia incorrecta.
-
-Para evitar esto, puedes crear cuentas de canal separadas que se pueden usar como la cuenta de origen para la transacción y usar la cuenta que posee los activos como la cuenta base o la cuenta de origen para las operaciones individuales en la transacción. En este escenario, los activos saldrán de la cuenta base, y el número de secuencia y las tarifas serán consumidos por la cuenta de canal.
-
-Los canales aprovechan el hecho de que la cuenta de origen de una transacción puede ser diferente a la cuenta de origen de las operaciones dentro de la transacción. Con esta configuración, puedes hacer tantos canales como necesites para mantener tu tasa de transacción deseada.
-
-Por supuesto, tendrás que firmar la transacción con ambas claves, la de la cuenta base y la de la cuenta de canal.
-
-Por ejemplo:
-
-<CodeExample>
-
-```js
-// channelAccounts[] is an array of accountIDs, one for each channel
-// channelKeys[] is an array of secret keys, one for each channel
-// channelIndex is the channel you want to send this transaction over
-
-// create payment from baseAccount to customerAddress
-var transaction = new StellarSdk.TransactionBuilder(
-  channelAccounts[channelIndex],
-  {
-    fee: StellarSdk.BASE_FEE,
-    networkPassphrase: StellarSdk.Networks.TESTNET,
-  },
-)
-  .addOperation(
-    StellarSdk.Operation.payment({
-      source: baseAccount.address(),
-      destination: customerAddress,
-      asset: StellarSdk.Asset.native(),
-      amount: amountToSend,
-    }),
-  )
-  // Wait a maximum of three minutes for the transaction
-  .setTimeout(180)
-  .build();
-
-transaction.sign(baseAccountKey); // base account must sign to approve the payment
-transaction.sign(channelKeys[channelIndex]); // channel must sign to approve it being the source of the transaction
-```
-
-```python
-# channelAccounts[] is an array of accountIDs, one for each channel
-# channelKeys[] is an array of secret keys, one for each channel
-# channelIndex is the channel you want to send this transaction over
-
-transaction = (
-    TransactionBuilder(
-      source_account=channelAccounts[channelIndex],
-      network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-      base_fee=base_fee,
-    )
-    .append_payment_op(
-      source=baseAccount.public_key,
-      destination=customerAddress,
-      asset=Asset.native(),
-      amount=amountToSend,
-    )
-    .set_timeout(180) # Wait a maximum of three minutes for the transaction
-    .build()
-)
-
-transaction.sign(baseAccountKey) # base account must sign to approve the payment
-transaction.sign(channelKeys[channelIndex]) # channel must sign to approve it being the source of the transaction
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/claimable-balances.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/claimable-balances.mdx
deleted file mode 100644
index e1bf787616..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/claimable-balances.mdx
+++ /dev/null
@@ -1,436 +0,0 @@
----
-title: Saldos Reclamables
-sidebar_position: 20
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Los saldos reclamables se introdujeron en [CAP-0023](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0023.md) y se utilizan para dividir un pago en dos partes.
-
-- Parte 1: la cuenta emisora crea un pago, o ClaimableBalanceEntry, utilizando la operación Crear Saldo Reclamable
-- Parte 2: la(s) cuenta(s) de destino, o reclamante(s), acepta(n) el ClaimableBalanceEntry utilizando la operación Reclamar Saldo Reclamable
-
-Los saldos reclamables permiten a una cuenta enviar un pago a otra cuenta que no necesariamente está preparada para recibir el pago. Se pueden utilizar cuando envías un activo no nativo a una cuenta que aún no ha establecido una línea de confianza, lo que puede ser útil para los anclajes que incorporan nuevos usuarios. Se debe establecer una línea de confianza por parte del reclamante al activo antes de que pueda reclamar el saldo reclamable, de lo contrario, la reclamación resultará en un error `op_no_trust`.
-
-Es importante notar que si un saldo reclamable no se reclama, permanece en el ledger para siempre, ocupando espacio y, en última instancia, haciendo que la red sea menos eficiente. **Por esta razón, es una buena idea poner una de tus propias cuentas como reclamante para un saldo reclamable.** Entonces puedes aceptar tu propio saldo reclamable si es necesario, liberando espacio en la red.
-
-Cada ClaimableBalanceEntry es una entrada en el ledger, y cada reclamante en esa entrada aumenta el saldo mínimo de la cuenta fuente por una reserva base.
-
-Una vez que se ha reclamado un ClaimableBalanceEntry, se elimina.
-
-## Operaciones
-
-### Crear Saldo Reclamable
-
-Para parámetros básicos, consulta la entrada Crear Saldo Reclamable en nuestra [Lista de la sección de Operaciones](../../fundamentals/transactions/list-of-operations.mdx#create-claimable-balance).
-
-#### Parámetros adicionales
-
-`Claim_Predicate_` Reclamante — un objeto que contiene tanto la cuenta de destino que puede reclamar el ClaimableBalanceEntry como un ClaimPredicate que debe evaluarse como verdadero para que la reclamación tenga éxito.
-
-Un ClaimPredicate es una estructura de datos recursiva que se puede utilizar para construir condicionales complejos utilizando diferentes ClaimPredicateTypes. A continuación se presentan algunos ejemplos con el prefijo `Claim_Predicate_` eliminado para facilitar la lectura. Ten en cuenta que los SDK esperan que las marcas de tiempo de Unix se expresen en segundos.
-
-- Puede reclamar en cualquier momento - `UNCONDITIONAL`
-- Puede reclamar si el tiempo de cierre del ledger, incluyendo la reclamación, es antes de X segundos + el tiempo de cierre del ledger en el que se creó el ClaimableBalanceEntry - `BEFORE_RELATIVE_TIME(X)`
-- Puede reclamar si el tiempo de cierre del ledger, incluyendo la reclamación, es antes de X (marca de tiempo de Unix) - `BEFORE_ABSOLUTE_TIME(X)`
-- Puede reclamar si el tiempo de cierre del ledger, incluyendo la reclamación, es a o después de X segundos + el tiempo de cierre del ledger en el que se creó el ClaimableBalanceEntry - `NOT(BEFORE_RELATIVE_TIME(X))`
-- Puede reclamar si el tiempo de cierre del ledger, incluyendo la reclamación, es a o después de X (marca de tiempo de Unix) - `NOT(BEFORE_ABSOLUTE_TIME(X))`
-- Puede reclamar entre X y Y marcas de tiempo de Unix (dado que X < Y) - `AND(NOT(BEFORE_ABSOLUTE_TIME(X))`, `BEFORE_ABSOLUTE_TIME(Y))`
-- Puede reclamar fuera de las marcas de tiempo de Unix X e Y (dado que X < Y) - `OR(BEFORE_ABSOLUTE_TIME(X)`, `NOT(BEFORE_ABSOLUTE_TIME(Y))`
-
-`ClaimableBalanceID` ClaimableBalanceID es una unión con un posible tipo (`CLAIMABLE_BALANCE_ID_TYPE_V0`). Contiene un hash SHA-256 del OperationID para Saldo Reclamables.
-
-Una operación de Crear Saldo Reclamable exitosa devolverá un ID de saldo, que es necesario al reclamar el ClaimableBalanceEntry con la operación Reclamar Saldo Reclamable.
-
-### Reclamar Saldo Reclamable
-
-Para parámetros básicos, consulta la entrada Reclamar Saldo Reclamable en nuestra [Lista de la sección de Operaciones](../../fundamentals/transactions/list-of-operations#claim-claimable-balance).
-
-Esta operación cargará el ClaimableBalanceEntry que corresponde al ID de saldo y luego buscará la cuenta fuente de esta operación en la lista de reclamantes en la entrada. Si se encuentra una coincidencia en el reclamante, y el ClaimPredicate se evalúa como verdadero, entonces se puede reclamar el ClaimableBalanceEntry. El saldo en la entrada se moverá a la cuenta fuente si no hay problemas de límite o línea de confianza (para activos no nativos), lo que significa que el reclamante debe establecer una línea de confianza al activo antes de reclamarlo.
-
-### Recuperar Saldo Reclamable
-
-Esta operación recupera un saldo reclamable, devolviendo el activo a la cuenta emisora, quemándolo. Debes recuperar el saldo reclamable completo, no solo una parte de él. Una vez que se ha reclamado un saldo reclamable, utiliza la operación de recuperación regular para recuperarlo.
-
-Las recuperaciones de saldos reclamables requieren el ID de saldo reclamable.
-
-Aprende más sobre las recuperaciones en nuestra [Entrada de la Enciclopedia de Recuperaciones](./clawbacks.mdx).
-
-## Ejemplo
-
-El siguiente código demuestra a través de los SDK de JavaScript y Go cómo una cuenta (Cuenta A) crea un ClaimableBalanceEntry con dos reclamantes: Cuenta A (ella misma) y Cuenta B (otro destinatario).
-
-Cada una de estas cuentas solo puede reclamar el saldo bajo condiciones únicas. La Cuenta B tiene un minuto completo para reclamar el saldo antes de que la Cuenta A pueda recuperar el saldo de vuelta para sí misma.
-
-**Nota:** no hay un mecanismo de recuperación para un saldo reclamable en general: si ninguno de los predicados puede cumplirse, el saldo no puede recuperarse. El ejemplo de recuperación a continuación actúa como una red de seguridad para esta situación.
-
-<CodeExample>
-
-```js
-const sdk = require("stellar-sdk");
-
-async function main() {
-  let server = new sdk.Server("https://horizon-testnet.stellar.org");
-
-  let A = sdk.Keypair.fromSecret(
-    "SAQLZCQA6AYUXK6JSKVPJ2MZ5K5IIABJOEQIG4RVBHX4PG2KMRKWXCHJ",
-  );
-  let B = sdk.Keypair.fromPublicKey(
-    "GAS4V4O2B7DW5T7IQRPEEVCRXMDZESKISR7DVIGKZQYYV3OSQ5SH5LVP",
-  );
-
-  // NOTE: Proper error checks are omitted for brevity; always validate things!
-
-  let aAccount = await server.loadAccount(A.publicKey()).catch(function (err) {
-    console.error(`Failed to load ${A.publicKey()}: ${err}`);
-  });
-  if (!aAccount) {
-    return;
-  }
-
-  // Create a claimable balance with our two above-described conditions.
-  let soon = Math.ceil(Date.now() / 1000 + 60); // .now() is in ms
-  let bCanClaim = sdk.Claimant.predicateBeforeRelativeTime("60");
-  let aCanReclaim = sdk.Claimant.predicateNot(
-    sdk.Claimant.predicateBeforeAbsoluteTime(soon.toString()),
-  );
-
-  // Create the operation and submit it in a transaction.
-  let claimableBalanceEntry = sdk.Operation.createClaimableBalance({
-    claimants: [
-      new sdk.Claimant(B.publicKey(), bCanClaim),
-      new sdk.Claimant(A.publicKey(), aCanReclaim),
-    ],
-    asset: sdk.Asset.native(),
-    amount: "420",
-  });
-
-  let tx = new sdk.TransactionBuilder(aAccount, { fee: sdk.BASE_FEE })
-    .addOperation(claimableBalanceEntry)
-    .setNetworkPassphrase(sdk.Networks.TESTNET)
-    .setTimeout(180)
-    .build();
-
-  tx.sign(A);
-  let txResponse = await server
-    .submitTransaction(tx)
-    .then(function () {
-      console.log("Claimable balance created!");
-    })
-    .catch(function (err) {
-      console.error(`Tx submission failed: ${err}`);
-    });
-}
-```
-
-```go
-package main
-
-import (
-    "fmt"
-    "time"
-
-    sdk "github.com/stellar/go/clients/horizonclient"
-    "github.com/stellar/go/keypair"
-    "github.com/stellar/go/network"
-    "github.com/stellar/go/txnbuild"
-)
-
-
-func main() {
-    client := sdk.DefaultTestNetClient
-
-    // Suppose that these accounts exist and are funded accordingly:
-    A := "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4"
-    B := "GA2C5RFPE6GCKMY3US5PAB6UZLKIGSPIUKSLRB6Q723BM2OARMDUYEJ5"
-
-    // Load the corresponding account for A.
-    aKeys := keypair.MustParseFull(A)
-    aAccount, err := client.AccountDetail(sdk.AccountRequest{
-        AccountID: aKeys.Address(),
-    })
-    check(err)
-
-    // Create a claimable balance with our two above-described conditions.
-    soon := time.Now().Add(time.Second * 60)
-    bCanClaim := txnbuild.BeforeRelativeTimePredicate(60)
-    aCanReclaim := txnbuild.NotPredicate(
-        txnbuild.BeforeAbsoluteTimePredicate(soon.Unix()),
-    )
-
-    claimants := []txnbuild.Claimant{
-        txnbuild.NewClaimant(B, &bCanClaim),
-        txnbuild.NewClaimant(aKeys.Address(), &aCanReclaim),
-    }
-
-    // Create the operation and submit it in a transaction.
-    claimableBalanceEntry := txnbuild.CreateClaimableBalance{
-        Destinations: claimants,
-        Asset:        txnbuild.NativeAsset{},
-        Amount:       "420",
-    }
-
-    // Build, sign, and submit the transaction
-    tx, err := txnbuild.NewTransaction(
-        txnbuild.TransactionParams{
-            SourceAccount:        aAccount.AccountID,
-            IncrementSequenceNum: true,
-            BaseFee:              txnbuild.MinBaseFee,
-            // Use a real timeout in production!
-            Timebounds: txnbuild.NewInfiniteTimeout(),
-            Operations: []txnbuild.Operation{&claimableBalanceEntry},
-        },
-    )
-    check(err)
-    tx, err = tx.Sign(network.TestNetworkPassphrase, aKeys)
-    check(err)
-    txResp, err := client.SubmitTransaction(tx)
-    check(err)
-
-    fmt.Println(txResp)
-    fmt.Println("Claimable balance created!")
-}
-```
-
-```python
-import time
-from stellar_sdk.xdr import TransactionResult, OperationType
-from stellar_sdk.exceptions import NotFoundError, BadResponseError, BadRequestError
-from stellar_sdk import (
-    Keypair,
-    Network,
-    Server,
-    TransactionBuilder,
-    Transaction,
-    Asset,
-    Operation,
-    Claimant,
-    ClaimPredicate,
-    CreateClaimableBalance,
-    ClaimClaimableBalance
-)
-
-server = Server("https://horizon-testnet.stellar.org")
-
-A = Keypair.from_secret("SANRGB5VXZ52E7XDGH2BHVBFZR4S25AUQ4BR7SFXIQYT5J6W2OES2OP7")
-B = Keypair.from_public_key("GAAPSRMYNFAO3TDQTLNLKN76IQ3E6IQAKU23PSQX3BIV7RTEBXHQIWU6")
-
-# NOTE: Proper error checks are omitted for brevity; always validate things!
-
-try:
-    aAccount = server.load_account(A.public_key)
-except NotFoundError:
-    raise Exception(f"Failed to load {A.public_key}")
-
-# Create a claimable balance with our two above-described conditions.
-soon = int(time.time() + 60)
-bCanClaim = ClaimPredicate.predicate_before_relative_time(60)
-aCanClaim = ClaimPredicate.predicate_not(
-    ClaimPredicate.predicate_before_absolute_time(soon)
-)
-
-# Create the operation and submit it in a transaction.
-claimableBalanceEntry = CreateClaimableBalance(
-    asset = Asset.native(),
-    amount = "420",
-    claimants = [
-        Claimant(destination = B.public_key, predicate = bCanClaim),
-        Claimant(destination = A.public_key, predicate = aCanClaim)
-    ]
-)
-
-tx = (
-    TransactionBuilder (
-        source_account = aAccount,
-        network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE,
-        base_fee = server.fetch_base_fee()
-    )
-    .append_operation(claimableBalanceEntry)
-    .set_timeout(180)
-    .build()
-)
-
-tx.sign(A)
-try:
-    txResponse = server.submit_transaction(tx)
-    print("Claimable balance created!")
-except (BadRequestError, BadResponseError) as err:
-    print(f"Tx submission failed: {err}")
-```
-
-</CodeExample>
-
-En este punto, el `ClaimableBalanceEntry` existe en el ledger, pero necesitaremos su ID de saldo para reclamarlo, lo cual se puede hacer de varias maneras:
-
-1. El presentador de la entrada (Cuenta A en este caso) puede recuperar el ID de saldo antes de enviar la transacción;
-2. El presentador analiza el XDR de las operaciones del resultado de la transacción; o
-3. Alguien consulta la lista de saldos reclamables.
-
-Cualquiera de las partes también podría verificar los [`/effects`](../../../data/apis/horizon/api-reference/resources/effects/README.mdx) de la transacción o consultar los [`/claimable_balances`](../../../data/apis/horizon/api-reference/resources/claimablebalances/README.mdx) con diferentes filtros en Horizon. Ten en cuenta que mientras (1) puede no estar disponible en algunos SDKs ya que es solo una ayuda, los otros métodos son universales.
-
-<CodeExample>
-
-```js
-// Method 1: Suppose `txResponse` comes from the transaction submission
-// above on testnet.
-const builder = sdk.TransactionBuilder(
-  txResponse.envelope_xdr,
-  Networks.TESTNET,
-);
-console.log("Balance ID (1):", builder.build().getClaimableBalanceId(0));
-
-// Method 2:
-let txResult = sdk.xdr.TransactionResult.fromXDR(
-  txResponse.result_xdr,
-  "base64",
-);
-let results = txResult.result().results();
-
-// We look at the first result since our first (and only) operation
-// in the transaction was the CreateClaimableBalanceOp.
-let operationResult = results[0].value().createClaimableBalanceResult();
-let balanceId = operationResult.balanceId().toXDR("hex");
-console.log("Balance ID (2):", balanceId);
-
-// Method 3: Account B could alternatively do something like:
-let balances = await server
-  .claimableBalances()
-  .claimant(B.publicKey())
-  .limit(1) // there may be many in general
-  .order("desc") // so always get the latest one
-  .call()
-  .catch(function (err) {
-    console.error(`Claimable balance retrieval failed: ${err}`);
-  });
-if (!balances) {
-  return;
-}
-
-balanceId = balances.records[0].id;
-console.log("Balance ID (3):", balanceId);
-```
-
-```go
-// Method 1: Suppose `tx` comes from the transaction built above.
-//           Notice that this can be done *before* submission.
-balanceId, err := tx.ClaimableBalanceID(0)
-check(err)
-
-// Method 2: Suppose `txResp` comes from the transaction submission above.
-var txResult xdr.TransactionResult
-err = xdr.SafeUnmarshalBase64(txResp.ResultXdr, &txResult)
-check(err)
-
-if results, ok := txResult.OperationResults(); ok {
-    // We look at the first result since our first (and only) operation in the
-    // transaction was the CreateClaimableBalanceOp.
-    operationResult := results[0].MustTr().CreateClaimableBalanceResult
-    balanceId, err := xdr.MarshalHex(operationResult.BalanceId)
-    check(err)
-    fmt.Println("Balance ID:", balanceId)
-}
-
-// Method 3: Account B could alternatively do something like:
-balances, err := client.ClaimableBalances(sdk.ClaimableBalanceRequest{Claimant: B})
-check(err)
-balanceId := balances.Embedded.Records[0].BalanceID
-```
-
-```python
-# Method 1: Not available in the Python SDK yet.
-
-# Method 2: Suppose `txResponse` comes from the transaction submission
-# above.
-txResult = TransactionResult.from_xdr(txResponse["result_xdr"])
-results = txResult.result.results
-
-# We look at the first result since our first (and only) operation
-# in the transaction was the CreateClaimableBalanceOp.
-operationResult = results[0].tr.create_claimable_balance_result
-balanceId = operationResult.balance_id.to_xdr_bytes().hex()
-print(f"Balance ID (2): {balanceId}")
-
-# Method 3: Account B could alternatively do something like:
-try:
-    balances = (
-        server
-        .claimable_balances()
-        .for_claimant(B.public_key)
-        .limit(1)
-        .order(desc = True)
-        .call()
-    )
-except (BadRequestError, BadResponseError) as err:
-    print(f"Claimable balance retrieval failed: {err}")
-
-balanceId = balances["_embedded"]["records"][0]["id"]
-print(f"Balance ID (3): {balanceId}")
-```
-
-</CodeExample>
-
-Con el ID de Saldo Reclamable adquirido, ya sea la Cuenta B o A pueden realmente enviar una reclamación, dependiendo de qué predicado se cumpla. Supongamos aquí que ha pasado un minuto, por lo que la Cuenta A simplemente reclama la entrada del saldo.
-
-<CodeExample>
-
-```js
-let claimBalance = sdk.Operation.claimClaimableBalance({
-  balanceId: balanceId,
-});
-console.log(A.publicKey(), "claiming", balanceId);
-
-let tx = new sdk.TransactionBuilder(aAccount, { fee: sdk.BASE_FEE })
-  .addOperation(claimBalance)
-  .setNetworkPassphrase(sdk.Networks.TESTNET)
-  .setTimeout(180)
-  .build();
-
-tx.sign(A);
-await server.submitTransaction(tx).catch(function (err) {
-  console.error(`Tx submission failed: ${err}`);
-});
-```
-
-```go
-claimBalance := txnbuild.ClaimClaimableBalance{BalanceID: balanceId}
-tx, err = txnbuild.NewTransaction(
-    txnbuild.TransactionParams{
-        SourceAccount:        aAccount.AccountID, // or Account B, depending on the condition!
-        IncrementSequenceNum: true,
-        BaseFee:              txnbuild.MinBaseFee,
-        Timebounds:           txnbuild.NewInfiniteTimeout(),
-        Operations:           []txnbuild.Operation{&claimBalance},
-    },
-)
-check(err)
-tx, err = tx.Sign(network.TestNetworkPassphrase, aKeys)
-check(err)
-txResp, err = client.SubmitTransaction(tx)
-check(err)
-```
-
-```python
-claimBalance = ClaimClaimableBalance(balance_id = balanceId)
-print(f"{A.public_key} claiming {balanceId}")
-
-tx = (
-    TransactionBuilder (
-        source_account = aAccount,
-        network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE,
-        base_fee = server.fetch_base_fee()
-    )
-    .append_operation(claimBalance)
-    .set_timeout(180)
-    .build()
-)
-
-tx.sign(A)
-try:
-    txResponse = server.submit_transaction(tx)
-except (BadRequestError, BadResponseError) as err:
-    print(f"Tx submission failed: {err}")
-```
-
-</CodeExample>
-
-¡Y eso es todo! Dado que optamos por el camino de recuperación, la Cuenta A debería tener el mismo saldo que tenía al principio (menos tarifas), y la Cuenta B debería permanecer sin cambios.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/clawbacks.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/clawbacks.mdx
deleted file mode 100644
index 623e0c53b9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/clawbacks.mdx
+++ /dev/null
@@ -1,396 +0,0 @@
----
-title: Recuperaciones
-sidebar_position: 30
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Las recuperaciones se introdujeron en CAP-0035 y permiten que un emisor de activos queme una cantidad específica de un activo habilitado para recuperaciones de una línea de confianza o saldo recuperable, destruyéndolo efectivamente y removiéndolo del saldo de un destinatario.
-
-Están diseñadas para permitir que los emisores de activos cumplan con las regulaciones de valores, que en muchas jurisdicciones requieren que los emisores de activos (o agentes de transferencia designados) tengan la capacidad de revocar activos en caso de una transacción errónea o fraudulenta u otra acción regulatoria relacionada con una persona o activo específico.
-
-Las recuperaciones son útiles para:
-
-- Recuperar activos que han sido obtenidos fraudulentamente
-- Responder a acciones regulatorias
-- Permitir a las personas con identidad verificada recuperar un activo habilitado en caso de pérdida de custodia de claves o robo
-
-## Operaciones
-
-### Establecer opciones
-
-El emisor configura su cuenta para habilitar las recuperaciones utilizando la bandera `AUTH_CLAWBACK_ENABLED`. Esto hace que cada trustline subsiguiente establecido a cualquier activo emitido por esa cuenta tenga la `TRUSTLINE_CLAWBACK_ENABLED_FLAG` configurada automáticamente.
-
-Si una cuenta emisora quiere establecer la `AUTH_CLAWBACK_ENABLED_FLAG`, debe tener configurada la `AUTH_REVOCABLE_FLAG`. Esto permite a un emisor de activos recuperar saldos bloqueados en ofertas revocando primero la autorización de una línea de confianza, lo que retira todas las ofertas que involucran esa línea de confianza. Luego el emisor puede realizar la recuperación.
-
-### Recuperación
-
-La cuenta emisora utiliza esta operación para recuperar parte o la totalidad de un activo. Una vez que una cuenta posee un activo particular para el cual se han habilitado las recuperaciones, la cuenta emisora puede recuperarlo, quemándolo. Necesitas proporcionar el activo, una cantidad y la cuenta desde la cual estás recuperando el activo. Para más detalles, consulta la [operación de Clawback](../../fundamentals/transactions/list-of-operations.mdx#clawback).
-
-### Recuperación de saldo recuperable
-
-Esta operación recupera un saldo recuperable, devolviendo el activo a la cuenta emisora, quemándolo. Debes recuperar el saldo recuperable completo, no solo una parte de él. Una vez que un saldo recuperable ha sido reclamado, utiliza la operación de recuperación regular para recuperarlo. Las recuperaciones de saldos recuperables requieren el ID de saldo recuperable. Para más detalles, consulta la [operación de Clawback Claimable Balance](../../fundamentals/transactions/list-of-operations.mdx#clawback-claimable-balance).
-
-### Establecer bandera de línea de confianza
-
-La cuenta emisora utiliza esta operación para eliminar las capacidades de clawback en un trustline específico al eliminar la `TRUSTLINE_CLAWBACK_ENABLED_FLAG` a través de la operación [**SetTrustLineFlags**](../../fundamentals/transactions/list-of-operations.mdx#set-trustline-flags).
-
-Solo puedes limpiar una bandera, no configurarla. Por lo tanto, limpiar una bandera de recuperación en una línea de confianza es irreversible. Esto se hace para que no cambies retroactivamente las reglas para tus titulares de activos. Si deseas habilitar recuperaciones nuevamente, los titulares deben volver a emitir sus líneas de confianza.
-
-## Ejemplos
-
-Aquí cubriremos los siguientes enfoques para recuperar un activo.
-
-**Ejemplo 1:** La cuenta emisora (Cuenta A) crea un activo habilitado para recuperación y lo envía a la Cuenta B. La Cuenta B envía ese activo a la Cuenta C. La Cuenta A luego recuperará el activo de C. **Ejemplo 2:** La Cuenta B crea un saldo recuperable para la Cuenta C, y la Cuenta A recupera el saldo recuperable. **Ejemplo 3:** La Cuenta A emite un activo habilitado para recuperación a la Cuenta B. A recupera parte del activo de B, luego elimina la bandera habilitada para recuperación de la línea de confianza y ya no puede recuperar el activo.
-
-### Preámbulo: Emisión de un activo recuperable
-
-Primero, configuraremos una cuenta para habilitar recuperaciones y emitir un activo en consecuencia.
-
-Emitir adecuadamente un activo (con cuentas de emisión y distribución separadas) es un poco más complicado, pero utilizaremos un método más simple aquí.
-
-También, ten en cuenta que primero necesitamos habilitar recuperaciones y luego establecer líneas de confianza, ya que no puedes habilitar recuperaciones retroactivamente en líneas de confianza existentes.
-
-<CodeExample>
-
-```js
-const sdk = require("stellar-sdk");
-
-let server = new sdk.Server("https://horizon-testnet.stellar.org");
-
-const A = sdk.Keypair.fromSecret(
-  "SAQLZCQA6AYUXK6JSKVPJ2MZ5K5IIABJOEQIG4RVBHX4PG2KMRKWXCHJ",
-);
-const B = sdk.Keypair.fromSecret(
-  "SAAY2H7SANIS3JLFBFPLJRTYNLUYH4UTROIKRVFI4FEYV4LDW5Y7HDZ4",
-);
-const C = sdk.Keypair.fromSecret(
-  "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4",
-);
-
-const ASSET = new sdk.Asset("CLAW", A.publicKey());
-
-/// Enables AuthClawbackEnabledFlag on an account.
-function enableClawback(account, keys) {
-  return server.submitTransaction(
-    buildTx(account, keys, [
-      sdk.Operation.setOptions({
-        setFlags: sdk.AuthClawbackEnabledFlag | sdk.AuthRevocableFlag,
-      }),
-    ]),
-  );
-}
-
-/// Establishes a trustline for `recipient` for ASSET (from above).
-const establishTrustline = function (recipient, key) {
-  return server.submitTransaction(
-    buildTx(recipient, key, [
-      sdk.Operation.changeTrust({
-        asset: ASSET,
-        limit: "5000", // arbitrary
-      }),
-    ]),
-  );
-};
-
-/// Retrieves latest account info for all accounts.
-function getAccounts() {
-  return Promise.all([
-    server.loadAccount(A.publicKey()),
-    server.loadAccount(B.publicKey()),
-    server.loadAccount(C.publicKey()),
-  ]);
-}
-
-/// Enables clawback on A, and establishes trustlines from C, B -> A.
-function preamble() {
-  return getAccounts().then(function (accounts) {
-    let [accountA, accountB, accountC] = accounts;
-    return enableClawback(accountA, A).then(
-      Promise.all([
-        establishTrustline(accountB, B),
-        establishTrustline(accountC, C),
-      ]),
-    );
-  });
-}
-
-/// Helps simplify creating & signing a transaction.
-function buildTx(source, signer, ops) {
-  var tx = new StellarSdk.TransactionBuilder(source, {
-    fee: 100,
-    networkPassphrase: StellarSdk.Networks.TESTNET,
-  });
-  ops.forEach((op) => tx.addOperation(op));
-  tx = tx.setTimeout(30).build();
-  tx.sign(signer);
-  return tx;
-}
-
-/// Prints the balances of a list of accounts.
-function showBalances(accounts) {
-  accounts.forEach((acc) => {
-    console.log(`${acc.accountId().substring(0, 5)}: ${getBalance(acc)}`);
-  });
-}
-```
-
-</CodeExample>
-
-### Ejemplo 1: Pagos
-
-Con el código de configuración compartido fuera del camino, ahora podemos demostrar cómo funciona la recuperación para pagos. Este ejemplo destacará cómo el emisor de activos mantiene el control sobre su activo independientemente de cómo se distribuya al mundo.
-
-En nuestro escenario, la Cuenta A pagará a la Cuenta B con 1000 tokens de su activo personalizado; luego, B pagará a la Cuenta C 500 tokens a su vez. Finalmente, A recuperará la mitad del saldo de C, quemando 250 tokens para siempre. Vamos a sumergirnos en las funciones auxiliares:
-
-<CodeExample>
-
-```js
-/// Make a payment to `toAccount` from `fromAccount` for `amount`.
-function makePayment(toAccount, fromAccount, fromKey, amount) {
-  return server.submitTransaction(
-    buildTx(fromAccount, fromKey, [
-      sdk.Operation.payment({
-        destination: toAccount.accountId(),
-        asset: ASSET, // defined in preamble
-        amount: amount,
-      }),
-    ]),
-  );
-}
-
-/// Perform a clawback by `byAccount` of `amount` from `fromAccount`.
-function doClawback(byAccount, byKey, fromAccount, amount) {
-  return server.submitTransaction(
-    buildTx(byAccount, byKey, [
-      sdk.Operation.clawback({
-        from: fromAccount.accountId(),
-        asset: ASSET, // defined in preamble
-        amount: amount,
-      }),
-    ]),
-  );
-}
-
-/// Retrieves the balance of ASSET in `account`.
-function getBalance(account) {
-  const balances = account.balances.filter((balance) => {
-    return (
-      balance.asset_code == ASSET.code && balance.asset_issuer == ASSET.issuer
-    );
-  });
-  return balances.length > 0 ? balances[0].balance : "0";
-}
-```
-
-</CodeExample>
-
-Estos fragmentos nos ayudarán con la composición final: haciendo algunos pagos para distribuir el activo al mundo y recuperando parte de él.
-
-<CodeExample>
-
-```js
-function examplePaymentClawback() {
-  return getAccounts()
-    .then(function (accounts) {
-      let [accountA, accountB, accountC] = accounts;
-      return makePayment(accountB, accountA, A, "1000")
-        .then(makePayment(accountC, accountB, B, "500"))
-        .then(doClawback(accountA, A, accountC, "250"));
-    })
-    .then(getAccounts)
-    .then(showBalances);
-}
-
-preamble().then(examplePaymentClawback);
-```
-
-</CodeExample>
-
-Después de ejecutar nuestro ejemplo, deberíamos ver que los saldos reflejan el flujo del ejemplo:
-
-```
-GCIHA: 0
-GDS5N: 500
-GC2BK: 250
-```
-
-Nota que `GCIHA` (Cuenta A, el emisor) no posee ninguno de los activos a pesar de haber recuperado 250 de la Cuenta C. Esto debería resaltar el hecho de que los activos recuperados son quemados, no transferidos.
-
-(Puede parecer extraño que A nunca posea tokens de su activo personalizado, pero así es como funciona la emisión: creas valor donde antes no existía. Enviar un activo a su cuenta emisora es equivalente a quemarlo, y auditar la cantidad total de un activo existente es uno de los beneficios de distribuir un activo correctamente a través de una cuenta de distribución, lo cual evitamos hacer aquí por brevedad del ejemplo.)
-
-### Ejemplo 2: Saldos Recuperables
-
-Los pagos directos no son la única forma de transferir activos entre cuentas: los saldos recuperables también lo hacen. Dado que son un mecanismo de pago separado, necesitan un mecanismo de recuperación separado.
-
-Necesitamos algunos métodos adicionales de ayuda para comenzar a trabajar de manera eficiente con saldos recuperables:
-
-<CodeExample>
-
-```js
-function createClaimable(fromAccount, fromKey, toAccount, amount) {
-  return server.submitTransaction(
-    buildTx(fromAccount, fromKey, [
-      sdk.Operation.createClaimableBalance({
-        asset: ASSET,
-        amount: amount,
-        claimants: [new sdk.Claimant(toAccount.accountId())],
-      }),
-    ]),
-  );
-}
-
-// https://developers.stellar.org/docs/encyclopedia/claimable-balance/#example
-function getBalanceId(txResponse) {
-  const txResult = sdk.xdr.TransactionResult.fromXDR(
-    txResponse.result_xdr,
-    "base64",
-  );
-  const operationResult = txResult.result().results()[0];
-
-  let creationResult = operationResult.value().createClaimableBalanceResult();
-  return creationResult.balanceId().toXDR("hex");
-}
-
-function clawbackClaimable(issuerAccount, issuerKey, balanceId) {
-  return server.submitTransaction(
-    buildTx(issuerAccount, issuerKey, [
-      sdk.Operation.clawbackClaimableBalance({ balanceId }),
-    ]),
-  );
-}
-```
-
-</CodeExample>
-
-Ahora, podemos cumplir con el flujo: A paga a B, quien envía un saldo recuperable a C, quien es recuperado por A. (Ten en cuenta que dependemos del ayudante `makePayment` del ejemplo anterior.)
-
-<CodeExample>
-
-```js
-function exampleClaimableBalanceClawback() {
-  return getAccounts()
-    .then(function (accounts) {
-      let [accountA, accountB, accountC] = accounts;
-
-      return makePayment(accountB, accountA, A, "1000")
-        .then(() => createClaimable(accountB, B, accountC, "500"))
-        .then((txResp) => clawbackClaimable(accountA, A, getBalanceId(txResp)));
-    })
-    .then(getAccounts)
-    .then(showBalances);
-}
-```
-
-</CodeExample>
-
-Después de ejecutar `preamble().then(examplePaymentClawback)`, deberíamos ver que los saldos reflejan nuestro flujo:
-
-```
-GCIHA: 0
-GDS5N: 500
-GC2BK: 0
-```
-
-### Ejemplo 3: Habilitación Selectiva de Recuperación
-
-Cuando habilitas la `AUTH_CLAWBACK_ENABLED_FLAG` en tu cuenta, hará que todas las futuras líneas de confianza tengan habilitada la recuperación para cualquiera de tus activos emitidos. Esto puede no ser siempre deseable ya que puede que quieras que ciertos activos se comporten como lo hacían antes. Aunque podrías encontrar una solución emitiendo activos desde una cuenta de "recuperación dedicada", también puedes simplemente deshabilitar las recuperaciones para ciertas líneas de confianza limpiando la `TRUST_LINE_CLAWBACK_ENABLED_FLAG` en una línea de confianza.
-
-En el siguiente ejemplo, tendremos una cuenta (Cuenta A, como antes) que emitirá un nuevo activo y lo distribuirá a una segunda cuenta (Cuenta B). Luego, demostraremos cómo A recupera algunos de los activos de B, luego limpia la línea de confianza y ya no puede recuperar el activo.
-
-Primero, prepararemos las cuentas (ten en cuenta que estamos dependiendo aquí de funciones auxiliares definidas en los ejemplos anteriores):
-
-<CodeExample>
-
-```js
-function getAccounts() {
-  return Promise.all([
-    server.loadAccount(A.publicKey()),
-    server.loadAccount(B.publicKey()),
-  ]);
-}
-
-function preambleRedux() {
-  return getAccounts().then((accounts) => {
-    return enableClawback(accounts[0], A).then(() =>
-      establishTrustline(accounts[1], B),
-    );
-  });
-}
-```
-
-</CodeExample>
-
-Ahora, distribuyamos algunos de nuestros activos a la Cuenta B, solo para recuperarlos. Luego, limpiaremos la bandera de la línea de confianza y mostraremos que otra recuperación no es posible:
-
-<CodeExample>
-
-```js
-function disableClawback(issuerAccount, issuerKeys, forTrustor) {
-  return server.submitTransaction(
-    buildTx(issuerAccount, issuerKeys, [
-      sdk.Operation.setTrustLineFlags({
-        trustor: forTrustor.accountId(),
-        asset: ASSET, // defined in the (original) preamble
-        flags: {
-          clawbackEnabled: false,
-        },
-      }),
-    ]),
-  );
-}
-
-function exampleSelectiveClawback() {
-  return getAccounts()
-    .then((accounts) => {
-      let [accountA, accountB] = accounts;
-      return makePayment(accountB, accountA, A, "1000")
-        .then(getAccounts)
-        .then(showBalances)
-        .then(() => doClawback(accountA, A, accountB, "500"))
-        .then(getAccounts)
-        .then(showBalances)
-        .then(() => disableClawback(accountA, A, accountB))
-        .then(() => doClawback(accountA, A, accountB, "500"))
-        .catch((err) => {
-          if (err.response && err.response.data) {
-            // Note that this is a *very* specific way to check for an error, and
-            // you should probably never do it this way.
-            // We do this here to demonstrate that the clawback error *does*
-            // occur as expected.
-            const opErrors = err.response.data.extras.result_codes.operations;
-            if (
-              opErrors &&
-              opErrors.length > 0 &&
-              opErrors[0] === "op_not_clawback_enabled"
-            ) {
-              console.info("Clawback failed, as expected!");
-            } else {
-              console.error(
-                "Uh-oh, some other failure occurred:",
-                err.response.data.extras,
-              );
-            }
-          } else {
-            console.error("Uh-oh, unknown failure:", err);
-          }
-        });
-    })
-    .then(getAccounts)
-    .then(showBalances);
-}
-```
-
-</CodeExample>
-
-Ejecuta el ejemplo (por ejemplo, `via preambleRedux().then(exampleSelectiveClawback)`) y observa su resultado:
-
-```
-GCIHA: 0
-GDS5N: 1000
-GCIHA: 0
-GDS5N: 500
-Clawback failed, as expected!
-GCIHA: 0
-GDS5N: 500
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/fee-bump-transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/fee-bump-transactions.mdx
deleted file mode 100644
index db917b318c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/fee-bump-transactions.mdx
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Transacciones de aumento de tarifas
-sidebar_position: 40
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Las transacciones de aumento de tarifas se introdujeron en [CAP-0015](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0015.md) y permiten que una cuenta pague las tarifas de transacción de una transacción existente sin tener que volver a firmar la transacción o gestionar los números de secuencia.
-
-Una transacción de aumento de tarifas se compone de dos partes:
-
-1. Un sobre de transacción interno con su(s) firma(s)
-2. Un sobre de transacción externo con la transacción de aumento de tarifas y la firma de la cuenta de tarifas
-
-## Casos de uso comunes
-
-Podrías considerar usar aumentos de tarifas cuando:
-
-- Estás construyendo un servicio donde deseas cubrir las tarifas de los usuarios
-- Deseas aumentar la tarifa en una transacción existente para que tenga una mejor oportunidad de llegar al ledger durante el aumento de precios
-- Necesitas ajustar la tarifa en una transacción preautorizada para que pueda llegar al ledger si las tarifas mínimas de la red han aumentado
-
-## Atributos
-
-### Sobre de transacción existente (transacción interna)
-
-Antes de crear una transacción de aumento de tarifas, primero debes tener una transacción envuelta con sus firmas en un sobre de transacción. Llamaremos a esta transacción la transacción interna. Llamaremos a esta transacción la transacción interna.
-
-### Cuenta de tarifa
-
-La cuenta que pagará la tarifa por la transacción de aumento de tarifas. Esta cuenta incurrirá en la tarifa en lugar de la cuenta fuente especificada en la transacción interna. Sin embargo, el número de secuencia aún se toma de la cuenta fuente.
-
-### Tarifa
-
-La tarifa máxima por operación que estás dispuesto a pagar por la transacción de aumento de tarifas. La transacción de aumento de tarifas es una operación. Por lo tanto, el número total de operaciones es igual al número de operaciones en la transacción interna más uno.
-
-Lee más sobre las tarifas de transacción en nuestra [sección de tarifas](../../fundamentals/fees-resource-limits-metering.mdx).
-
-### Reemplazar por tarifa
-
-Puedes aplicar una transacción de aumento de tarifas para aumentar una tarifa que proviene de tu propia cuenta. Sin embargo, si envías dos transacciones distintas con la misma cuenta fuente y número de secuencia, siendo la segunda transacción una transacción de aumento de tarifas, la segunda transacción reemplazará la primera transacción en la cola si y solo si la oferta de tarifa de la segunda transacción es 10 veces la oferta de tarifa de la primera transacción. Este número puede parecer aleatorio, es una decisión de diseño deliberada para limitar los ataques DOS sin introducir demasiada complejidad en el protocolo.
-
-### Sobre de transacción de aumento de tarifas
-
-Cuando una transacción de aumento de tarifas esté lista para ser firmada, se envuelve en un sobre de transacción. Este sobre contiene la transacción de aumento de tarifas y la firma de la cuenta de tarifas especificada.
-
-## Validez de una transacción de aumento de tarifas
-
-Una transacción de aumento de tarifas pasa por una serie de verificaciones en su ciclo de vida para determinar su validez. Las siguientes condiciones deben cumplirse:
-
-- **Cuenta de tarifas** — la cuenta de tarifas para la transacción de aumento de tarifas debe existir en el ledger.
-- **Tarifa**
-  - La tarifa debe ser mayor o igual a la tarifa mínima de la red para el número de operaciones en la transacción interna, más uno por el aumento de tarifas.
-  - La tarifa también debe ser mayor o igual a la tarifa especificada en la transacción interna.
-  - Si la transacción de aumento de tarifas está aprovechando el reemplazo por tarifa, la tarifa debe ser 10 veces más alta que la primera transacción.
-- **Firma de cuenta de tarifas** — el sobre de transacción de aumento de tarifas debe contener una firma válida para la cuenta de tarifas. Además, el peso de esa firma debe cumplir con el umbral bajo para la cuenta de tarifas, y el pasphrase de red apropiado debe ser parte del hash de transacción firmado por la cuenta de tarifas.
-- **Saldo de cuenta de tarifas** — la cuenta de tarifas debe tener un saldo suficiente de XLM para cubrir la tarifa
-- **Transacción interna** — la transacción interna debe ser válida, lo que significa que debe cumplir con los requisitos descritos en la [Sección de validez de una transacción](../../fundamentals/transactions/operations-and-transactions.mdx#transaction-and-operation-validity). Si la validación de la transacción interna es exitosa, el resultado es `FEE_BUMP_INNER_SUCCESS`, y los resultados de la validación de la transacción interna aparecen en el resultado interno. Si la transacción interna es inválida, el resultado es `FEE_BUMP_INNER_FAILED`, y la transacción de aumento de tarifas es inválida porque la transacción interna es inválida. Si la validación de la transacción interna es exitosa, entonces el resultado es `FEE_BUMP_INNER_SUCCESS`, y los resultados de la validación de la transacción interna aparecen en el resultado interno. Si la transacción interna es inválida, el resultado es `FEE_BUMP_INNER_FAILED`, y la transacción de aumento de tarifa es inválida porque la transacción interna es inválida.
-
-## Aplicación
-
-El único propósito de una transacción de aumento de tarifas es incluir una transacción interna en un conjunto de transacciones. Dado que la transacción de aumento de tarifas no tiene efectos secundarios además de pagar una tarifa — y en el momento en que se paga la tarifa, la transacción externa debe haber sido válida (de lo contrario, los nodos no habrían votado por ella) — no hay razón para verificar la validez de la transacción de aumento de tarifas en el momento de aplicar. Por lo tanto, el número de secuencia de la transacción interna siempre se consume en el momento de aplicar. Sin embargo, la transacción interna todavía tendrá su validez verificada en el momento de aplicar.
-
-Cada resultado de transacción de aumento de tarifas contiene un resultado completo de transacción interna. Este resultado de la transacción interna es exactamente lo que se hubiera producido si no hubiera habido una transacción de aumento de tarifas, excepto que la tarifa interna siempre será 0.
-
-## Ejemplo: implementación de una transacción de aumento de tarifas
-
-Este ejemplo muestra cómo crear y enviar una transacción de aumento de tarifas en la red Stellar. Reemplaza los valores de clave secreta, `SECREY_KEY_1` y `SECREY_KEY_2` de keypairs de tu elección. Este no es un ejemplo de producción, y debes tener cuidado de nunca exponer tus claves secretas en la web.
-
-<CodeExample>
-
-```js
-import * as StellarSDK from "@stellar/stellar-sdk";
-
-// Define the network passphrase (use 'Testnet' for testing and 'Public Global Stellar Network ; September 2015' for production)
-const networkPassphrase = StellarSDK.Networks.TESTNET;
-
-// Create keypairs for the source account and the fee account
-const sourceKeypair = StellarSDK.Keypair.fromSecret("SECREY_KEY_1");
-const feeKeypair = StellarSDK.Keypair.fromSecret("SECREY_KEY_2");
-
-// Load the source account (this requires network interaction)
-const server = new StellarSDK.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-const sourceAccount = await server.loadAccount(sourceKeypair.publicKey());
-
-// Construct the inner transaction, just a example tx, to transfer 10 XLM to a destination account
-const innerTransaction = new StellarSDK.TransactionBuilder(sourceAccount, {
-  fee: StellarSDK.BASE_FEE,
-  networkPassphrase,
-})
-  .addOperation(
-    StellarSDK.Operation.payment({
-      destination: "GDWH3P3MNTCMOY42CA7RVEACUUAUPZ73XDYKPYUL3TWOFRF37FD6OVM6",
-      asset: StellarSDK.Asset.native(),
-      amount: "10",
-    }),
-  )
-  .setTimeout(30)
-  .build();
-
-// Sign the inner transaction with the source account
-innerTransaction.sign(sourceKeypair);
-
-// Build the fee-bump transaction
-const feeBumpTransaction =
-  StellarSDK.TransactionBuilder.buildFeeBumpTransaction(
-    feeKeypair,
-    StellarSDK.BASE_FEE * 2,
-    innerTransaction,
-    networkPassphrase,
-  );
-
-// Sign the fee-bump transaction with the fee account
-feeBumpTransaction.sign(feeKeypair);
-
-// Submit the fee-bump transaction to the Stellar network
-server
-  .submitTransaction(feeBumpTransaction)
-  .then((response) => {
-    console.log("Success! Results:", response);
-  })
-  .catch((error) => {
-    console.error("Something went wrong!", error);
-  });
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/memos.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/memos.mdx
deleted file mode 100644
index 0385aa8288..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/memos.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Memorandos
-sidebar_position: 50
----
-
-Los memorandos son un campo de datos opcional y no estructurado que se puede utilizar para incrustar cualquier información identificativa adicional sobre la transacción relevante para el remitente o el receptor.
-
-Anteriormente se utilizaban para diferenciar entre cuentas individuales en una cuenta agrupada, algo para lo que ahora usamos cuentas multiplexadas.
-
-Para más información sobre cuentas multiplexadas, consulta nuestra [Entrada de enciclopedia de Cuentas Agrupadas - Cuentas Multiplexadas y Memorandos](./pooled-accounts-muxed-accounts-memos.mdx)
-
-Los memorandos pueden ser uno de los siguientes tipos:
-
-`MEMO_TEXT`: Una cadena codificada utilizando ASCII o UTF-8, de hasta 28 bytes de longitud.\
-`MEMO_ID`: Un entero sin signo de 64 bits.\
-`MEMO_HASH`: Un hash de 32 bytes.\
-`MEMO_RETURN`: Un hash de 32 bytes destinado a ser interpretado como el hash de la transacción que el remitente está reembolsando.
-
-## Ejemplos de contenido de memorandos
-
-- Notificando que la transacción es un reembolso o reintegro
-- Referencia a una factura que la transacción está pagando
-- Cualquier información adicional de enrutamiento interno
-- Enlaces a datos relevantes
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/path-payments.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/path-payments.mdx
deleted file mode 100644
index 6dc9c409cc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/path-payments.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Pagos por Ruta
-sidebar_position: 60
----
-
-En un pago por ruta, el activo recibido difiere del activo enviado. En lugar de que la operación transfiera activos directamente de una cuenta a otra, los pagos por ruta atraviesan el SDEX y/o fondos de liquidez antes de llegar a la cuenta de destino. Para que el pago por ruta tenga éxito, debe existir una oferta DEX o un camino de intercambio de fondos de liquidez. A veces puede tomar varias conversiones para tener éxito.
-
-Por ejemplo:
-
-La Cuenta A vende XLM → [comprar XLM / vender ETH → comprar ETH / vender BTC → comprar BTC / vender USDC] → La Cuenta B recibe USDC
-
-Es posible que los pagos por ruta fallen si no existen caminos de intercambio viables.
-
-Para más información sobre el Stellar Decentralized Exchange y los Fondos de Liquidez, consulta nuestra [Entrada de Enciclopedia sobre Liquidez en Stellar: SDEX y Fondos de Liquidez](../sdex/liquidity-on-stellar-sdex-liquidity-pools.mdx)
-
-## Operaciones
-
-Los pagos por ruta utilizan las operaciones de Envío Estricto de Pago por Ruta o Recepción Estricta de Pago por Ruta.
-
-### Envío Estricto de Pago por Ruta
-
-Permite a un usuario especificar la cantidad del activo a enviar. La cantidad recibida variará según las ofertas en los libros de órdenes y/o fondos de liquidez.
-
-### Recepción Estricta de Pago por Ruta
-
-Permite a un usuario especificar la cantidad del activo recibido. La cantidad enviada variará según las ofertas en los libros de órdenes/fondos de liquidez.
-
-## Pagos por Ruta - más información
-
-- Los pagos por ruta no permiten que las ofertas intermedias provengan de la cuenta de origen ya que esto resultaría en un peor tipo de cambio. Deberás dividir el pago por ruta en dos pagos por ruta más pequeños o asegurarte de que las ofertas de la cuenta de origen no estén en la parte superior del libro de órdenes.
-- Los saldos se liquidan al final de la operación.
-  - Esto es especialmente importante cuando (`Destino, Activo de Destino) == (Origen, Activo a Enviar`) ya que esto proporciona una funcionalidad equivalente a obtener un préstamo sin interés durante la duración de la operación.
-- `Destino mínimo` es una medida protectora, permite especificar un límite inferior para una conversión aceptable. Si las ofertas en los libros de órdenes no son lo suficientemente favorables para que la operación entregue esa cantidad, la operación fallará.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos.mdx
deleted file mode 100644
index 24176123a6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos.mdx
+++ /dev/null
@@ -1,348 +0,0 @@
----
-title: "Cuentas agrupadas: cuentas muxed y memos"
-sidebar_position: 70
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Al crear una aplicación o servicio en Stellar, una de las primeras cosas que debes decidir es cómo manejar las cuentas de usuario.
-
-Puedes crear una cuenta Stellar para cada usuario, pero la mayoría de los servicios de custodia, incluidos los exchanges de criptomonedas, eligen usar una sola cuenta Stellar agrupada para manejar las transacciones en nombre de sus usuarios. En estos casos, la función de cuenta muxed puede asignar transacciones a cuentas individuales a través de una base de datos interna de clientes.
-
-:::note
-
-En el pasado, utilizamos memorandos para este propósito; sin embargo, usar cuentas muxed es mejor a largo plazo. En este momento, no hay soporte para cuentas muxed por todas las billeteras, exchanges y anchors, por lo que puede que quieras admitir tanto memorandos como cuentas muxed, al menos por un tiempo.
-
-:::
-
-## Cuentas agrupadas
-
-Una cuenta agrupada permite que un solo ID de cuenta Stellar sea compartido entre muchos usuarios. Generalmente, los servicios que utilizan cuentas agrupadas rastrean a sus clientes en una base de datos interna separada y usan la función de cuentas muxed para mapear un pago entrante y saliente al cliente interno correspondiente.
-
-Los beneficios de usar una cuenta agrupada son costos más bajos – no se requieren reservas base por cada cuenta – y menor complejidad de keys – solo necesitas gestionar una keypair. Sin embargo, con una sola cuenta agrupada, ahora es tu responsabilidad gestionar todos los saldos y pagos de los clientes individuales. Ya no puedes depender del ledger de Stellar para acumular valor, manejar errores y atomicidad, o gestionar transacciones de manera individual por cuenta.
-
-## Cuentas muxed
-
-Las cuentas muxed están incrustadas en el protocolo para conveniencia y estandarización. Distinguen cuentas individuales que todos existen bajo una sola cuenta Stellar tradicional. Combinan la dirección familiar `GABC…` con un ID entero de 64 bits.
-
-Las cuentas muxed no existen en el ledger, pero su cuenta subyacente compartida `GABC…` sí existe.
-
-Las cuentas muxed están definidas en [CAP-0027](https://stellar.org/protocol/cap-27), introducidas en el Protocolo 13, y su representación de cadena se describe en [SEP-0023](https://stellar.org/protocol/sep-23).
-
-Es seguro que todas las billeteras implementen el envío a cuentas muxed.
-
-Si deseas recibir depósitos a cuentas muxed, ten en cuenta que aún no son admitidas por todas las billeteras y exchanges.
-
-### Formato de dirección
-
-Las cuentas muxed tienen su propio formato de dirección que comienza con un prefijo M. Por ejemplo, a partir de una dirección de cuenta Stellar tradicional: `GA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJVSGZ`, podemos crear nuevas cuentas muxed con diferentes IDs. Los IDs están incrustados en la dirección misma: cuando analizas las direcciones de cuentas muxed, obtienes la dirección G de arriba más otro número.
-
-- `MA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJUAAAAAAAAAAAACJUQ` tiene el ID 0, mientras que
-- `MA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJUAAAAAAAAAABUTGI4` tiene el ID 420.
-
-Ambas direcciones actuarán en relación a la dirección subyacente `GA7Q…` al usarse con una de las operaciones admitidas.
-
-### Operaciones admitidas
-
-No todas las operaciones se pueden usar con cuentas muxed. Aquí está lo que puedes usar:
-
-- La cuenta fuente de cualquier operación o transacción;
-- La fuente de tarifas de una transacción de aumento de tarifa;
-- El destino de los tres tipos de pagos:
-  - `Pago`,
-  - `PathPaymentStrictSend`, y
-  - `PathPaymentStrictReceive`;
-- El destino de un AccountMerge; y
-- El objetivo de una operación `Clawback` (es decir, el campo from).
-
-Demostraremos algunos de estos en la sección de ejemplos.
-
-No hay validación en los IDs y, en lo que respecta a la red Stellar, todas las operaciones admitidas funcionan exactamente como si no usaras una cuenta muxed. Por ejemplo, si realizas dos pagos de dos cuentas muxed que comparten una cuenta Stellar subyacente (misma dirección G… dirección pero diferentes M… direcciones), esto es exactamente lo mismo que si esa cuenta Stellar única enviara dos pagos según lo indique el ledger. A pesar de que solo la cuenta subyacente `G…` existe realmente en el ledger de Stellar, la API de Horizon hará un esfuerzo por interpretar y rastrear las cuentas muxed responsables de ciertas acciones.
-
-### Ejemplos
-
-En esta sección, demostraremos cómo crear cuentas muxed y cómo se interfazan con sus operaciones admitidas. Dado que los métodos de trabajo de cuentas custodiales basados en memorandos de transacción ya no son necesarios, usaremos eso como esqueleto para nuestra estructura de ejemplo.
-
-Después de preparar algo de código de soporte, demostraremos tres ejemplos:
-
-Ejemplo 1: Pagos normales, "completos" de cuentas Stellar (es decir, G a G)\
-Ejemplo 2: Pagos mezclados (es decir, M a G)\
-Ejemplo 3: Pagos completamente muxed (es decir, M a M)
-
-Pero utiliza una función compartida para todos ellos que hace el trabajo real, destacando la facilidad de implementar soporte para cuentas muxed.
-
-#### Preámbulo
-
-Primero, vamos a crear dos cuentas y luego un puñado de cuentas virtuales que representan "clientes custodiales" que la cuenta principal gestiona:
-
-<CodeExample>
-
-```js
-const sdk = require("stellar-sdk");
-
-const passphrase = "Test SDF Network ; September 2015";
-const url = "https://horizon-testnet.stellar.org";
-let server = new sdk.Server(url);
-
-const custodian = sdk.Keypair.fromSecret(
-  "SAQLZCQA6AYUXK6JSKVPJ2MZ5K5IIABJOEQIG4RVBHX4PG2KMRKWXCHJ",
-);
-const outsider = sdk.Keypair.fromSecret(
-  "SAAY2H7SANIS3JLFBFPLJRTYNLUYH4UTROIKRVFI4FEYV4LDW5Y7HDZ4",
-);
-
-async function preamble() {
-  [custodianAcc, outsiderAcc] = await Promise.all([
-    server.loadAccount(custodian.publicKey()),
-    server.loadAccount(outsider.publicKey()),
-  ]);
-
-  customers = ["1", "22", "333", "4444"].map(
-    (id) => new sdk.MuxedAccount(custodianAcc, id),
-  );
-
-  console.log("Custodian:\n       ", custodian.publicKey());
-  console.log("Customers:");
-  customers.forEach((customer) => {
-    console.log(
-      " " + customer.id().padStart(4, " ") + ":",
-      customer.accountId(),
-    );
-  });
-  console.log();
-}
-```
-
-</CodeExample>
-
-Asumimos que estas cuentas existen en el testnet; puedes reemplazarlas con tus propias claves y usar friendbot si lo deseas.
-
-Cuando ejecutemos esta función, veremos la similitud en las direcciones de cuentas muxed entre los clientes, destacando el hecho de que comparten una clave pública:
-
-```
-Custodian:
-       GCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72MJN
-Customers:
-    1: MCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72AAAAAAAAAAAAEDB4
-   22: MCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72AAAAAAAAAAAC3IHY
-  333: MCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72AAAAAAAAAABJV72I
- 4444: MCIHAQVWZH2AB5BB5NP63FBSIREG77LQZZNUVKD2LN2IOCLOT6N72AAAAAAAAAARLQOKK
-```
-
-Con las cuentas fuera del camino, veamos cómo podemos gestionar la diferencia entre cuentas Stellar tradicionales (G...) y estas cuentas muxed virtuales (M...).
-
-#### Modelo de operaciones muxed
-
-La introducción de direcciones muxed como una abstracción de alto nivel—y su naturaleza experimental, optativa—significa que hay ramas de código ligeramente divergentes dependiendo de si la fuente es una cuenta muxed o no. Todavía necesitamos, por ejemplo, cargar cuentas por su dirección subyacente, porque las versiones muxed no existen realmente en el ledger de Stellar:
-
-<CodeExample>
-
-```js
-function loadAccount(account) {
-  if (StellarSdk.StrKey.isValidMed25519Address(account.accountId())) {
-    return loadAccount(account.baseAccount());
-  } else {
-    return server.loadAccount(account.accountId());
-  }
-}
-
-function showBalance(acc) {
-  console.log(`${acc.accountId().substring(0, 5)}: ${acc.balances[0].balance}`);
-}
-```
-
-</CodeExample>
-
-Para los pagos—nuestro enfoque para este conjunto de ejemplos—la divergencia solo importa porque queremos mostrar los saldos de la cuenta custodial.
-
-#### Pagos
-
-El código real para crear pagos es prácticamente el mismo que sería sin la situación muxed:
-
-<CodeExample>
-
-```js
-function doPayment(source, dest) {
-  return loadAccount(source)
-    .then((accountBeforePayment) => {
-      showBalance(accountBeforePayment);
-
-      let payment = sdk.Operation.payment({
-        source: source.accountId(),
-        destination: dest.accountId(),
-        asset: sdk.Asset.native(),
-        amount: "10",
-      });
-
-      let tx = new sdk.TransactionBuilder(accountBeforePayment, {
-        networkPassphrase: StellarSdk.Networks.TESTNET,
-        fee: StellarSdk.BASE_FEE,
-      })
-        .addOperation(payment)
-        .setTimeout(30)
-        .build();
-
-      tx.sign(custodian);
-      return server.submitTransaction(tx);
-    })
-    .then(() => loadAccount(source))
-    .then(showBalance);
-}
-```
-
-</CodeExample>
-
-Podemos usar este bloque para hacer un pago entre cuentas Stellar normales con facilidad: doPayment("GCIHA...", "GDS5N..."). La principal divergencia del código de pagos estándar, aparte de los stubs para mostrar los saldos de XLM antes y después, es la inclusión de la opción con el flag de muxing optativo.
-
-#### Muxed a Unmuxed
-
-El bloque de código anterior cubre todas las operaciones de pago, abstraiendo cualquier necesidad de diferenciar entre muxed (M...) y no demuxido (G...) direcciones. Desde un nivel alto, entonces, sigue siendo trivial hacer pagos entre uno de nuestros “clientes” y alguien fuera de la organización del “custodio”.
-
-<CodeExample>
-
-```js
-preamble.then(() => {
-  const src = customers[0];
-  console.log(
-    `Sending 10 XLM from Customer ${src.id()} to ${outsiderAcc
-      .accountId()
-      .substring(0, 5)}.`,
-  );
-  return doPayment(src, outsiderAcc);
-});
-```
-
-</CodeExample>
-
-Ten en cuenta que todavía firmamos la transacción con las claves del custodio, porque las cuentas muxed no tienen un concepto de clave secreta. En última instancia, todo sigue pasando por la cuenta principal, así que deberíamos ver disminuir el saldo de la cuenta principal en 10 XLM en consecuencia:
-
-```
-Sending 10 XLM from Customer 1 to GDS5N.
-GCIHA: 9519.9997700 XLM
-GCIHA: 9509.9997600 XLM
-```
-
-Por supuesto, también hay una tarifa cobrada por la transacción en sí.
-
-#### Muxed a Muxed
-
-Como hemos mencionado, las acciones de cuentas muxed no están representadas explícitamente en el ledger de Stellar. Cuando dos cuentas muxed que comparten una cuenta Stellar subyacente se comunican, es como si la cuenta subyacente se estuviera hablando a sí misma. Un pago entre dos cuentas de este tipo, entonces, es esencialmente un no-op.
-
-<CodeExample>
-
-```js
-preamble().then(() => {
-  const [src, dst] = customers.slice(0, 2);
-  console.log(
-    `Sending 10 XLM from Customer ${src.id()} to Customer ${dst.id()}.`,
-  );
-  return doPayment(src, dst);
-});
-```
-
-</CodeExample>
-
-La salida debería ser algo como lo siguiente:
-
-```
-Sending 10 XLM from Customer 1 to Customer 22.
-GCIHA: 9579.9999800 XLM
-GCIHA: 9579.9999700 XLM
-```
-
-Ten en cuenta que el saldo de la cuenta está esencialmente sin cambios, sin embargo se le cobró una tarifa ya que esta transacción sigue estando registrada en el ledger (a pesar de no hacer casi nada). Es posible que desees detectar este tipo de transacciones en tu aplicación para evitar pagar tarifas de transacción innecesarias.
-
-Si hiciéramos un pago entre dos cuentas muxed que tuvieran diferentes cuentas Stellar subyacentes, esto sería equivalente a un pago entre esas dos respectivas G... cuentas.
-
-#### Más ejemplos
-
-Como ocurre con la mayoría de las funciones a nivel de protocolo, puedes encontrar más ejemplos de uso e inspiración en la suite de pruebas relevante para tu SDK favorito. Por ejemplo, [aquí](https://github.com/stellar/js-stellar-base/blob/master/test/unit/muxed_account_test.js) hay algunos de los casos de prueba de JavaScript.
-
-### Preguntas frecuentes
-
-**¿Qué pasa si pago una dirección muxed, pero el destinatario no las admite?**
-
-En general, no debes enviar pagos a direcciones muxed en plataformas que no las admitan. Estas plataformas no podrán proporcionar direcciones destino muxed en primer lugar.
-
-Aun así, si esto ocurre, parsear una transacción con un parámetro muxed sin manejarlos llevará a una de dos cosas:
-
-- Si tu SDK está desactualizado, el parsing fallará. Debes actualizar tu SDK. Por ejemplo, el SDK de JavaScript mostrará un mensaje útil:
-
-```
-“destination is invalid; did you forget to enable muxing?”
-```
-
-- Si tu SDK está actualizado, verás la dirección muxed (`M...`) parseada. Lo que pase después depende de tu aplicación.
-
-Ten en cuenta, sin embargo, que la operación tendrá éxito en la red. En el caso de pagos, por ejemplo, la dirección principal del destinatario seguirá recibiendo los fondos.
-
-**¿Qué pasa si quiero pagar una cuenta muxed, pero mi plataforma no las admite?**
-
-En este caso, no uses una dirección muxed. Es probable que la plataforma falle al crear la operación. Probablemente quieras usar el método legado de incluir un memo de transacción, en su lugar.
-
-**¿Qué debo hacer si recibo una transacción con direcciones muxed y un ID de memo?**
-
-En un mundo ideal, esta situación nunca debería ocurrir. Puedes determinar si los IDs subyacentes son iguales o no; si no lo son, esta es una transacción malformada y recomendamos no enviarla a la red.
-
-**¿Qué pasa si obtengo errores al usar cuentas muxed?**
-
-En las versiones actualizadas de los SDK de Stellar, las cuentas muxed son admitidas de forma nativa por defecto. Sin embargo, si estás usando una versión antigua de un SDK, es posible que aún estén ocultas detrás de una bandera de función.
-
-Si obtienes errores al usar direcciones muxed en operaciones admitidas como: “¿el destino es inválido; ¿has habilitado el muxing?
-
-Recomendamos actualizar a la última versión de todos los SDK de Stellar que uses. Sin embargo, si eso no es posible por alguna razón, necesitarás habilitar la bandera de función antes de interactuar con cuentas muxed. Consulta la documentación de tu SDK para más detalles.
-
-**¿Qué pasa si paso una dirección muxed a una operación incompatible?**
-
-Solo ciertas operaciones permiten cuentas muxed, como se describe arriba. Pasar una dirección muxed a un parámetro incompatible con un SDK actualizado debería resultar en un error de compilación o en tiempo de ejecución en el momento de su uso.
-
-Por ejemplo, al usar incorrectamente el SDK de JavaScript:
-
-<CodeExample>
-
-```js
-const mAddress =
-  "MA7QYNF7SOWQ3GLR2BGMZEHXAVIRZA4KVWLTJJFC7MGXUA74P7UJUAAAAAAAAAABUTGI4";
-transactionBuilder.addOperation(
-  Operation.setTrustLineFlags({
-    trustor: mAddress, // wrong!
-    asset: someAsset,
-    flags: { clawbackEnabled: false },
-  }),
-);
-```
-
-</CodeExample>
-
-El resultado en tiempo de ejecución sería:
-
-“Error: byte de versión inválido. se esperaba 48, se obtuvo 96”
-
-Este mensaje de error indica que el `trustor` no se pudo parsear como un ID de cuenta Stellar (`G...`). En otras palabras, tu código fallará y la operación inválida nunca alcanzará la red.
-
-**¿Cómo valido direcciones Stellar?**
-
-Debes usar los métodos de validación proporcionados por tu SDK o adherirte cuidadosamente a [SEP-23](https://stellar.org/protocol/sep-23). Por ejemplo, el SDK de JavaScript proporciona los siguientes métodos para validar direcciones Stellar:
-
-```ts
-namespace StrKey {
-  function isValidEd25519PublicKey(publicKey: string): boolean;
-  function isValidMed25519PublicKey(publicKey: string): boolean;
-}
-```
-
-También hay abstracciones para construir y gestionar cuentas tanto muxed como regulares; consulta la documentación de tu SDK para más detalles.
-
-## Memo - cuentas diferenciadas
-
-Antes de la introducción de cuentas muxed, los productos y servicios que dependían de cuentas agrupadas a menudo usaban memos de transacción para diferenciar entre usuarios. Admitir cuentas muxed es mejor a largo plazo, pero por ahora puedes querer admitir tanto memos como cuentas muxed, ya que no todos los exchanges, anchors y billeteras pueden admitir cuentas muxed.
-
-Para aprender sobre otros propósitos para los que se pueden usar memos, consulta nuestra [Entrada de Enciclopedia de Memos](./memos.mdx).
-
-## ¿Por qué son mejores las cuentas muxed a largo plazo?
-
-Las cuentas muxed son un mejor enfoque para diferenciar entre individuos en una cuenta agrupada porque tienen mejor:
-
-- Compartibilidad: en lugar de preocuparte por cosas propensas a errores como copiar y pegar IDs de memos, simplemente puedes compartir tu M... dirección.
-- Soporte del SDK: los diversos SDK admiten esta abstracción de forma nativa, lo que te permite crear, gestionar y trabajar con cuentas muxed fácilmente. Esto significa que puedes ver aparecer direcciones muxed al parsear cualquiera de los campos que las admiten, así que deberías estar listo para manejarlas. Consulta la documentación de tu SDK para más detalles; por ejemplo, [v7.0.0](https://github.com/stellar/js-stellar-base/releases/tag/v7.0.0) de la biblioteca de SDK de JavaScript stellar-base describe todos los campos y funciones que se relacionan con cuentas muxed.
-- Eficiencia: al combinar cuentas virtuales relacionadas bajo el mismo paraguas de una sola cuenta, puedes evitar mantener reservas y pagar tarifas por todas ellas para que existan en el ledger individualmente. También puedes combinar múltiples pagos a múltiples destinos dentro de una única transacción ya que ya no necesitas el campo de memo por transacción.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/sponsored-reserves.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/sponsored-reserves.mdx
deleted file mode 100644
index fe17f0b93f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/transactions-specialized/sponsored-reserves.mdx
+++ /dev/null
@@ -1,550 +0,0 @@
----
-title: Reservas Patrocinadas
-sidebar_position: 80
----
-
-import { CodeExample } from "@site/src/components/CodeExample";
-
-Las reservas patrocinadas se introdujeron en [CAP-0033](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md) y permiten que una cuenta (cuenta patrocinadora) pague las reservas base para otra cuenta (cuenta patrocinada). Mientras esta relación exista, los requisitos de reserva base que normalmente se acumularían en la cuenta patrocinada ahora se acumulan en la cuenta patrocinadora.
-
-Ambas operaciones Comenzar a Patrocinar Reservas Futuras y Terminar Patrocinio de Reservas Futuras deben aparecer en la transacción de patrocinio, garantizando que ambas cuentas acuerden el patrocinio.
-
-Cualquier cosa que incremente el saldo mínimo puede ser patrocinada (creación de cuentas, ofertas, líneas de confianza, entradas de datos, firmantes, saldos reclamables).
-
-Para aprender sobre las reservas base, consulta nuestra sección sobre [Lumens](../../fundamentals/lumens.mdx#base-reserves).
-
-## Operaciones de reservas patrocinadas
-
-### Comenzar y finalizar patrocinios
-
-Para crear una reserva patrocinada, debes utilizar una transacción tipo sándwich que incluya tres operaciones.
-
-- La primera operación: Comenzar a Patrocinar Reservas Futuras inicia el patrocinio y requiere la firma de la cuenta patrocinadora.
-- La segunda operación: especifica qué está siendo patrocinado.
-- La tercera operación: Terminar Patrocinio de Reservas Futuras permite que la cuenta patrocinada acepte el patrocinio y requiere la firma de la cuenta patrocinada.
-
-Comenzar a Patrocinar Reservas Futuras establece la relación is-sponsoring-future-reserves-for donde la cuenta patrocinadora es la cuenta fuente de la operación. La cuenta especificada en la operación es la cuenta patrocinada.
-
-Terminar Patrocinio de Reservas Futuras finaliza la actual relación is-sponsoring-future-reserves-for para la cuenta fuente de la operación.
-
-Al final de cualquier transacción, no debe haber relaciones is-sponsoring-future-reserves-for en curso, por lo que estas dos operaciones deben usarse juntas en una sola transacción.
-
-Consulta los detalles de la operación en nuestra [sección de Lista de Operaciones](../../fundamentals/transactions/list-of-operations.mdx).
-
-### Revocar patrocinio
-
-Permite que la cuenta patrocinadora elimine o transfiera patrocinios de ledgerEntries y firmantes existentes. Si el ledgerEntry o firmante no está patrocinado, el propietario del ledgerEntry o firmante puede establecer un patrocinio si es el beneficiario de una relación is-sponsoring-future-reserves-for.
-
-Lógica de operación
-
-- Entry/firman está patrocinado
-  - La cuenta fuente es actualmente beneficiaria de una relación is-sponsoring-future-reserves-for
-    - Transferir patrocinio de entry/firman de la cuenta fuente a la cuenta que está patrocinando la cuenta fuente
-  - La cuenta fuente no es beneficiaria de una relación is-sponsoring-future-reserves-for
-    - Eliminar el patrocinio de la entry/firman
-- Entry/firman no está patrocinado
-  - La cuenta fuente es actualmente beneficiaria de una relación is-sponsoring-future-reserves-for
-    - Establecer patrocinio entre entry/firman y la cuenta que está patrocinando la cuenta fuente
-  - La cuenta fuente no es beneficiaria de una relación is-sponsoring-future-reserves-for
-    - No-Op
-
-Consulta los detalles de la operación en nuestra [sección de Lista de Operaciones](../../fundamentals/transactions/list-of-operations.mdx#begin-sponsoring-future-reserves).
-
-## Efecto en el saldo mínimo
-
-Una vez que se introducen los patrocinios, el cálculo del saldo mínimo es: (2 reservas base + `numSubEntries` + `numSponsoring` - `numSponsored`) \* `baseReserve` + `liabilities.selling`.
-
-Cuando la cuenta A está patrocinando reservas futuras para la cuenta B, cualquier requerimiento de reserva que normalmente se acumularía en B se acumulará en A, mostrado en `numSponsoring`. El hecho de que estas reservas sean proporcionadas por otra cuenta se reflejará en B en `numSponsored`, lo que cancela el aumento en `numSubEntries`, manteniendo el saldo mínimo sin cambios para B.
-
-Cuando una entry o subentry patrocinada es eliminada, `numSponsoring` disminuye en la cuenta patrocinadora y `numSponsored` disminuye en la cuenta patrocinada.
-
-Para aprender más sobre los requisitos de saldo mínimo, consulta nuestra sección sobre [Lumens](../../fundamentals/lumens.mdx#minimum-balance).
-
-## Efecto en los saldos reclamables
-
-Todos los saldos reclamables son patrocinados a través de la lógica incorporada en las operaciones de saldo reclamable. La cuenta que crea el saldo reclamable paga la reserva base para obtener el saldo reclamable en el ledger. Cuando el saldo reclamable es reclamado por el/los reclamante(s), el saldo reclamable se elimina del ledger, y la cuenta que lo creó recupera la reserva base.
-
-Lee más sobre los saldos reclamables en nuestra [Entrada de Enciclopedia sobre Saldos Reclamables](./claimable-balances.mdx).
-
-## Ejemplos
-
-Cada uno de los siguientes ejemplos se basa en sí mismo, haciendo referencia a variables de fragmentos anteriores. Los siguientes ejemplos demostrarán:
-
-1. Patrocinar la creación de una línea de confianza para otra cuenta
-2. Patrocinar dos líneas de confianza para una cuenta a través de dos patrocinadores diferentes
-3. Transferir la responsabilidad del patrocinio de una cuenta a otra
-4. Revocar el patrocinio de una cuenta por completo
-
-Para mayor brevedad en los ejemplos de Golang, asumiremos la existencia de un `SignAndSend`(...) método (definido a continuación) que crea y envía una transacción con los parámetros adecuados y una verificación básica de errores.
-
-### Preámbulo
-
-Comenzaremos incluyendo el boilerplate de creación de cuentas y activos.
-
-<CodeExample>
-
-```js
-const sdk = require("stellar-sdk");
-const http = require("got");
-
-let server = new sdk.Server("https://horizon-testnet.stellar.org");
-
-async function main() {
-  // Create & fund the new accounts.
-  let keypairs = [
-    sdk.Keypair.random(),
-    sdk.Keypair.random(),
-    sdk.Keypair.random(),
-  ];
-
-  for (const keypair of keypairs) {
-    const base = "https://friendbot.stellar.org/?";
-    const path = base + "addr=" + encodeURIComponent(keypair.publicKey());
-
-    console.log(`Funding:\n ${keypair.secret()}\n ${keypair.publicKey()}`);
-
-    // We use the "got" library here to do the HTTP request synchronously, but
-    // you can obviously use any method you'd like for this.
-    const response = await http(path).catch(function (error) {
-      console.error("  failed:", error.response.body);
-    });
-  }
-
-  // Arbitrary assets to sponsor trustlines for. Let's assume they make sense.
-  let S1 = keypairs[0], A = keypairs[1], S2 = keypairs[2];
-  let assets = [
-    new sdk.Asset("ABCD", S1.publicKey()),
-    new sdk.Asset("EFGH", S1.publicKey()),
-    new sdk.Asset("IJKL", S2.publicKey()),
-  ];
-
-  // ...
-```
-
-```go
-package main
-
-import (
-    "fmt"
-    "net/http"
-
-    sdk "github.com/stellar/go/clients/horizonclient"
-    "github.com/stellar/go/keypair"
-    "github.com/stellar/go/network"
-    protocol "github.com/stellar/go/protocols/horizon"
-    "github.com/stellar/go/txnbuild"
-)
-
-func main() {
-    client := sdk.DefaultTestNetClient
-
-    // Both S1 and S2 will be sponsors for A at various points in time.
-    S1, A, S2 := keypair.MustRandom(), keypair.MustRandom(), keypair.MustRandom()
-    addressA := A.Address()
-
-    for _, pair := range []*keypair.Full{S1, A, S2} {
-        resp, err := http.Get("https://friendbot.stellar.org/?addr=" + pair.Address())
-        check(err)
-        resp.Body.Close()
-        fmt.Println("Funded", pair.Address())
-    }
-
-    // Load the corresponding account for both A and C.
-    s1Account, err := client.AccountDetail(sdk.AccountRequest{AccountID: S1.Address()})
-    check(err)
-    aAccount, err := client.AccountDetail(sdk.AccountRequest{AccountID: addressA})
-    check(err)
-    s2Account, err := client.AccountDetail(sdk.AccountRequest{AccountID: S2.Address()})
-    check(err)
-
-    // Arbitrary assets to sponsor trustlines for. Let's assume they make sense.
-    assets := []txnbuild.CreditAsset{
-        txnbuild.CreditAsset{Code: "ABCD", Issuer: S1.Address()},
-        txnbuild.CreditAsset{Code: "EFGH", Issuer: S1.Address()},
-        txnbuild.CreditAsset{Code: "IJKL", Issuer: S2.Address()},
-    }
-
-    // ...
-```
-
-</CodeExample>
-
-### 1. Patrocinio de líneas de confianza
-
-Ahora, vamos a patrocinar líneas de confianza para la Cuenta A. Nota cómo la operación `CHANGE_TRUST` está enmarcada entre las operaciones de inicio y finalización de patrocinio y que todas las cuentas relevantes deben firmar la transacción.
-
-<CodeExample>
-
-```js
-//
-// 1. S1 will sponsor a trustline for Account A.
-//
-let s1Account = await server.loadAccount(S1.publicKey()).catch(accountFail);
-let tx = new sdk.TransactionBuilder(s1Account, { fee: sdk.BASE_FEE })
-  .addOperation(
-    sdk.Operation.beginSponsoringFutureReserves({
-      sponsoredId: A.publicKey(),
-    }),
-  )
-  .addOperation(
-    sdk.Operation.changeTrust({
-      source: A.publicKey(),
-      asset: assets[0],
-      limit: "1000", // This limit can vary according with your application;
-      // if left empty, it defaults to the max limit.
-    }),
-  )
-  .addOperation(
-    sdk.Operation.endSponsoringFutureReserves({
-      source: A.publicKey(),
-    }),
-  )
-  .setNetworkPassphrase(sdk.Networks.TESTNET)
-  .setTimeout(180)
-  .build();
-
-// Note that while either can submit this transaction, both must sign it.
-tx.sign(S1, A);
-let txResponse = await server.submitTransaction(tx).catch(txCheck);
-if (!txResponse) {
-  return;
-}
-
-console.log("Sponsored a trustline of", A.publicKey());
-
-//
-// 2. Both S1 and S2 sponsor trustlines for Account A for different assets.
-//
-let aAccount = await server.loadAccount(A.publicKey()).catch(accountFail);
-let tx = new sdk.TransactionBuilder(aAccount, { fee: sdk.BASE_FEE })
-  .addOperation(
-    sdk.Operation.beginSponsoringFutureReserves({
-      source: S1.publicKey(),
-      sponsoredId: A.publicKey(),
-    }),
-  )
-  .addOperation(
-    sdk.Operation.changeTrust({
-      asset: assets[1],
-      limit: "5000",
-    }),
-  )
-  .addOperation(sdk.Operation.endSponsoringFutureReserves())
-
-  .addOperation(
-    sdk.Operation.beginSponsoringFutureReserves({
-      source: S2.publicKey(),
-      sponsoredId: A.publicKey(),
-    }),
-  )
-  .addOperation(
-    sdk.Operation.changeTrust({
-      asset: assets[2],
-      limit: "2500",
-    }),
-  )
-  .addOperation(sdk.Operation.endSponsoringFutureReserves())
-  .setNetworkPassphrase(sdk.Networks.TESTNET)
-  .setTimeout(180)
-  .build();
-
-// Note that all 3 accounts must approve/sign this transaction.
-tx.sign(S1, S2, A);
-let txResponse = await server.submitTransaction(tx).catch(txCheck);
-if (!txResponse) {
-  return;
-}
-
-console.log("Sponsored two trustlines of", A.publicKey());
-```
-
-```go
-    //
-    // 1. S1 will sponsor a trustline for Account A.
-    //
-    sponsorTrustline := []txnbuild.Operation{
-        &txnbuild.BeginSponsoringFutureReserves{
-            SourceAccount: s1Account.AccountID,
-            SponsoredID:   addressA,
-        },
-        &txnbuild.ChangeTrust{
-            Line:  &assets[0],
-            Limit: txnbuild.MaxTrustlineLimit,
-        },
-        &txnbuild.EndSponsoringFutureReserves{},
-    }
-
-    // Note that while A can submit this transaction, both sign it.
-    SignAndSend(client, aAccount.AccountID, []*keypair.Full{S1, A}, sponsorTrustline...)
-    fmt.Println("Sponsored a trustline of", A.Address())
-
-    //
-    // 2. Both S1 and S2 sponsor trustlines for Account A for different assets.
-    //
-    sponsorTrustline = []txnbuild.Operation{
-        &txnbuild.BeginSponsoringFutureReserves{
-            SourceAccount: s1Account.AccountID,
-            SponsoredID:   addressA,
-        },
-        &txnbuild.ChangeTrust{
-            Line:          &assets[1],
-            Limit:         txnbuild.MaxTrustlineLimit,
-        },
-        &txnbuild.EndSponsoringFutureReserves{},
-
-        &txnbuild.BeginSponsoringFutureReserves{
-            SourceAccount: s2Account.AccountID,
-            SponsoredID:   addressA,
-        },
-        &txnbuild.ChangeTrust{
-            Line:          &assets[2],
-            Limit:         txnbuild.MaxTrustlineLimit,
-        },
-        &txnbuild.EndSponsoringFutureReserves{},
-    }
-
-    // Note that all 3 accounts must approve/sign this transaction.
-    SignAndSend(client, aAccount.AccountID, []*keypair.Full{S1, S2, A}, sponsorTrustline...)
-    fmt.Println("Sponsored two trustlines of", A.Address())
-```
-
-</CodeExample>
-
-### 2. Transferencia de patrocinio
-
-Supongamos que ahora el Firmante 1 quiere transferir la responsabilidad de patrocinar reservas para la línea de confianza al Patrocinador 2. Esto se logra enmarcando la transferencia entre las operaciones `BEGIN/END_SPONSORING_FUTURE_RESERVES`. Ambos participantes deben firmar la transacción, aunque cualquiera de los dos puede enviarla.
-
-Una forma intuitiva de pensar en una transferencia de patrocinio es que el propio acto de patrocinio está siendo patrocinado por una nueva cuenta. Es decir, el nuevo patrocinador asume las responsabilidades del antiguo patrocinador al patrocinar una revocación.
-
-<CodeExample>
-
-```js
-//
-// 3. Transfer sponsorship of B's second trustline from S1 to S2.
-//
-let tx = new sdk.TransactionBuilder(s1Account, { fee: sdk.BASE_FEE })
-  .addOperation(
-    sdk.Operation.beginSponsoringFutureReserves({
-      source: S2.publicKey(),
-      sponsoredId: S1.publicKey(),
-    }),
-  )
-  .addOperation(
-    sdk.Operation.revokeTrustlineSponsorship({
-      account: A.publicKey(),
-      asset: assets[1],
-    }),
-  )
-  .addOperation(sdk.Operation.endSponsoringFutureReserves())
-  .setNetworkPassphrase(sdk.Networks.TESTNET)
-  .setTimeout(180)
-  .build();
-
-// Notice that while the old sponsor *sends* the transaction, both sponsors
-// must *approve* the transfer.
-tx.sign(S1, S2);
-let txResponse = await server.submitTransaction(tx).catch(txCheck);
-if (!txResponse) {
-  return;
-}
-
-console.log("Transferred sponsorship for", A.publicKey());
-```
-
-```go
-    //
-    // 3. Transfer sponsorship of B's second trustline from S1 to S2.
-    //
-    transferOps := []txnbuild.Operation{
-        &txnbuild.BeginSponsoringFutureReserves{
-            SourceAccount: s2Account.AccountID,
-            SponsoredID:   S1.Address(),
-        },
-        &txnbuild.RevokeSponsorship{
-            SponsorshipType: txnbuild.RevokeSponsorshipTypeTrustLine,
-            Account:         &addressA,
-            TrustLine: &txnbuild.TrustLineID{
-                Account: addressA,
-                Asset:   assets[1],
-            },
-        },
-        &txnbuild.EndSponsoringFutureReserves{},
-    }
-
-    // Notice that while the old sponsor *sends* the transaction (in this case),
-    // both sponsors must *approve* the transfer.
-    SignAndSend(client, s1Account.AccountID, []*keypair.Full{S1, S2}, transferOps...)
-    fmt.Println("Transferred sponsorship for", A.Address())
-```
-
-</CodeExample>
-
-En este punto, el Firmante 1 solo está patrocinando el primer activo (categóricamente codificado como ABCD), mientras que el Firmante 2 está patrocinando los otros dos activos. (Recuerda que al principio el Firmante 1 también estaba patrocinando EFGH.)
-
-### 3. Revocación de patrocinio
-
-Finalmente, podemos demostrar la revocación completa de los patrocinios. A continuación, el Firmante 2 se elimina de toda responsabilidad sobre las dos líneas de confianza de activos. Observa que la Cuenta A no está involucrada en absoluto, ya que la revocación debe ser realizable puramente a discreción del patrocinador.
-
-<CodeExample>
-
-```js
-  //
-  // 4. S2 revokes sponsorship of B's trustlines entirely.
-  //
-  let s2Account = await server.loadAccount(S2.publicKey()).catch(accountFail);
-  let tx = new sdk.TransactionBuilder(s2Account, {fee: sdk.BASE_FEE})
-    .addOperation(sdk.Operation.revokeTrustlineSponsorship({
-      account: A.publicKey(),
-      asset: assets[1],
-    }))
-    .addOperation(sdk.Operation.revokeTrustlineSponsorship({
-      account: A.publicKey(),
-      asset: assets[2],
-    }))
-    .setNetworkPassphrase(sdk.Networks.TESTNET)
-    .setTimeout(180)
-    .build();
-
-  tx.sign(S2);
-  let txResponse = await server.submitTransaction(tx).catch(txCheck);
-  if (!txResponse) { return; }
-
-  console.log("Revoked sponsorship for", A.publicKey());
-} // ends main()
-```
-
-```go
-    //
-    // 4. S2 revokes sponsorship of B's trustlines entirely.
-    //
-    revokeOps := []txnbuild.Operation{
-        &txnbuild.RevokeSponsorship{
-            SponsorshipType: txnbuild.RevokeSponsorshipTypeTrustLine,
-            Account:         &addressA,
-            TrustLine: &txnbuild.TrustLineID{
-                Account: addressA,
-                Asset:   assets[1],
-            },
-        },
-        &txnbuild.RevokeSponsorship{
-            SponsorshipType: txnbuild.RevokeSponsorshipTypeTrustLine,
-            Account:         &addressA,
-            TrustLine: &txnbuild.TrustLineID{
-                Account: addressA,
-                Asset:   assets[2],
-            },
-        },
-    }
-
-    SignAndSend(client, s2Account.AccountID, []*keypair.Full{S2}, revokeOps...)
-    fmt.Println("Revoked sponsorship for", A.Address())
-} // ends main()
-```
-
-</CodeExample>
-
-### Cuentas de Origen de Patrocinio
-
-Cuando se trata de los campos SourceAccount de la transacción tipo sándwich de patrocinio, es importante referirse a la sabiduría de [CAP-33](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md#abstract):
-
-> Esta relación es iniciada por `BeginSponsoringFutureReservesOp`, donde la cuenta patrocinadora es la cuenta fuente, y es terminada por `EndSponsoringFutureReserveOp`, donde la cuenta patrocinada es la cuenta fuente.
-
-Dado que la cuenta fuente por defecto es la del remitente de la transacción cuando se omite, este campo siempre debe establecerse para ya sea el `Begin` o el `End`.
-
-Por ejemplo, la siguiente es una expresión idéntica del ejemplo anterior de Golang de patrocinio de una línea de confianza, solo que presentada por el patrocinador (Patrocinador 1) en lugar de la cuenta patrocinada (Cuenta A). Nota las diferencias en donde se establece `SourceAccount`:
-
-<CodeExample>
-
-```go
-    sponsorTrustline := []txnbuild.Operation{
-        &txnbuild.BeginSponsoringFutureReserves{
-            SponsoredID: addressA,
-        },
-        &txnbuild.ChangeTrust{
-            SourceAccount: aAccount.AccountID,
-            Line:          &assets[0],
-            Limit:         txnbuild.MaxTrustlineLimit,
-        },
-        &txnbuild.EndSponsoringFutureReserves{
-            SourceAccount: aAccount.AccountID,
-        },
-    }
-
-    // Again, both participants must still sign the transaction: the sponsored
-    // account must consent to the sponsorship.
-    SignAndSend(client, s1Account.AccountID, []*keypair.Full{S1, A}, sponsorTrustline...)
-```
-
-</CodeExample>
-
-### Otros ejemplos
-
-Si deseas otros ejemplos o quieres ver un desglose de pseudo-código más genérico de estos escenarios de patrocinio, puedes referirte directamente a [CAP-0033](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0033.md#example-revoke-sponsorship).
-
-### Nota al pie
-
-Para los ejemplos anteriores, una implementación de SignAndSend (Golang) y algún código (muy) rudimentario de verificación de errores (todos los idiomas) podría parecerse a esto:
-
-<CodeExample>
-
-```js
-function txCheck(err) {
-  console.error("Transaction submission failed:", err);
-  if (err.response != null && err.response.data != null) {
-    console.error("More details:", err.response.data.extras);
-  } else {
-    console.error("Unknown reason:", err);
-  }
-}
-
-function accountFail(err) {
-  console.error(" Failed to load account:", err.response.body);
-}
-```
-
-```go
-// Builds a transaction containing `operations...`, signed (by `signers`), and
-// submitted using the given `client` on behalf of `account`.
-func SignAndSend(
-    client *sdk.Client,
-    account txnbuild.Account,
-    signers []*keypair.Full,
-    operations ...txnbuild.Operation,
-) protocol.Transaction {
-    // Build, sign, and submit the transaction
-    tx, err := txnbuild.NewTransaction(
-        txnbuild.TransactionParams{
-            SourceAccount:        account,
-            IncrementSequenceNum: true,
-            BaseFee:              txnbuild.MinBaseFee,
-            Timebounds:           txnbuild.NewInfiniteTimeout(),
-            Operations:           operations,
-        },
-    )
-    check(err)
-
-    for _, signer := range signers {
-        tx, err = tx.Sign(network.TestNetworkPassphrase, signer)
-        check(err)
-    }
-
-    txResp, err := client.SubmitTransaction(tx)
-    if err != nil {
-        if prob := sdk.GetError(err); prob != nil {
-            fmt.Printf("  problem: %s\n", prob.Problem.Detail)
-            fmt.Printf("  extras: %s\n", prob.Problem.Extras["result_codes"])
-        }
-        check(err)
-    }
-
-    return txResp
-}
-
-func check(err error) {
-    if err != nil {
-        panic(err)
-    }
-}
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/README.mdx
deleted file mode 100644
index 0c17461dd3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Fundamentos de la red; datos, tarifas, consenso, anclas y más
-sidebar_label: Conceptos Clave
-description: Aprende los fundamentos y conceptos clave de la blockchain de Stellar, incluyendo estructuras de datos, tarifas, consenso, anclas, Propuestas del Ecosistema Stellar y más.
-sidebar_position: 10
----
-
-# Conceptos clave
-
-import DocCardList from "@theme/DocCardList";
-
-Desarrolla tu comprensión fundamental de lo que hace funcionar a la red Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/anchors.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/anchors.mdx
deleted file mode 100644
index 223870ae13..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/anchors.mdx
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: "Aprender sobre anclas: Ramps de entrada/salida para conectar las finanzas tradicionales con Blockchain"
-sidebar_position: 90
-sidebar_label: Anclajes
-description: Aprender sobre las ramps de entrada y salida en Stellar llamadas anclas y su papel en conectar el sistema financiero tradicional con redes de blockchain.
----
-
-# Anclas
-
-## Resumen
-
-Un ancla es un término específico de Stellar para las vías de acceso y salida que conectan la red Stellar con las vías de pago tradicionales, como instituciones financieras o empresas fintech. Los anclajes aceptan depósitos de monedas fiat (como el dólar estadounidense, el peso argentino o el naira nigeriano) a través de vías existentes (como depósitos bancarios o puntos de efectivo), luego envía al usuario los tokens digitales equivalentes en la red Stellar. Los tokens digitales equivalentes pueden representar esa misma moneda fiat o un token digital diferente. Alternativamente, los anclajes permiten a los tenedores de tokens canjear sus tokens por los activos del mundo real que representan.
-
-Stellar tiene servicios de anclaje operando en todo el mundo. View the [Anchor Directory](https://resources.stellar.org/anchors?) para más información sobre los anclajes de Stellar existentes.
-
-Los anclajes pueden emitir sus propios activos en la red Stellar, o pueden honrar activos que ya existen.
-
-Puedes configurar un anchor utilizando la [Anchor Platform](../../platforms/anchor-platform/README.mdx) mantenida por SDF, que es la forma más sencilla de desplegar un servicio de anchor compatible con las Propuestas del Ecosistema Stellar (SEP).
-
-Aprende cómo integrar servicios de anclaje en tu aplicación basada en blockchain consultando la [sección Construir Apps](../../build/apps/overview.mdx). Si buscas MoneyGram Ramps, consulta el tutorial de integración con [MoneyGram Ramps](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps).
-
-## Propuestas del Ecosistema Stellar (SEPs)
-
-Stellar es una red open-source diseñada para interoperar con instituciones financieras tradicionales, varios tipos de activos y otras redes. Los participantes de la red implementan las Propuestas del Ecosistema Stellar (SEPs) para asegurar que puedan interoperar con otros productos y servicios en la red. Las SEPs son documentos de open-source creados públicamente que viven en un [repositorio de GitHub](https://github.com/stellar/stellar-protocol/tree/master/ecosystem#stellar-ecosystem-proposals-seps.mdx) y definen cómo deben interactuar e interoperar los anclajes, emisores de activos, aplicaciones, exchanges y otros proveedores de servicios.
-
-Lee más sobre las SEPs en la [sección de SEPs](../fundamentals/stellar-ecosystem-proposals.mdx).
-
-Para los anclajes, las SEPs más importantes son [SEP-6]: Depósito y Retirada Programáticos, [SEP-24]: Depósito y Retirada Alojados, y [SEP-31]: API de Pagos Transfronterizos. También trabajarás con [SEP-10]: Autenticación Stellar, [SEP-12]: API de KYC, y [SEP-38]: API de RFQ de Ancla.
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[sep-12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-
-### Usar SEP-6: Depósito y retirada de fondos programáticos versus SEP-24: Depósito y retirada de fondos alojados
-
-Un usuario típicamente debe decidir si quiere configurar un ancla usando [SEP-6: Depósito y retirada de fondos programáticos](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) o [SEP-24: Depósito y retirada de fondos alojados](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md). Aquí están las diferencias y qué considerar al elegir uno u otro.
-
-#### SEP-6: Depósito y retirada de fondos programáticos
-
-Define la forma estándar en que los anclajes y billeteras interactúan en nombre de los usuarios. Con la guía de este SEP, las billeteras y otros clientes pueden interactuar directamente con los anclajes sin que el usuario necesite salir de la billetera para ir al sitio del ancla. Con SEP-6, el cliente recopila información KYC del usuario.
-
-Las billeteras (clientes) deben tener en cuenta al usar SEP-6:
-
-- Los clientes deben recopilar información KYC que pueden no necesitar
-- Los clientes deben saber qué información recopilar por ancla
-- Los clientes deben enviar la información en un formato estandarizado [(SEP-12: API KYC)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)
-- Los anclajes deben recibir la información a través de la API de SEP-12
-
-#### SEP-24: Depósito y retirada de fondos alojados
-
-Define la forma estándar en que los anclajes y las billeteras interactúan en nombre de los usuarios de forma interactiva. Esto significa que la aplicación del usuario debe abrir una vista web alojada por un ancla de terceros para que el usuario proporcione la información necesaria para completar la transacción. Con SEP-24, el ancla recopila información KYC del usuario.
-
-Las billeteras (clientes) deben tener en cuenta al usar SEP-24:
-
-- Los clientes no tienen que recopilar la información KYC requerida por el ancla
-- Los clientes y los anclajes no tienen que implementar [SEP-12: API KYC](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)
-- Los anclajes deben crear una interfaz de usuario que sea renderizada por muchos clientes
-- Los clientes deben permitir que los anclajes controlen temporalmente la experiencia de usuario
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/README.mdx
deleted file mode 100644
index 58e32cd9b3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Contratos inteligentes
-sidebar_position: 84
----
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/authorization.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/authorization.mdx
deleted file mode 100644
index 9a420e37b4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/authorization.mdx
+++ /dev/null
@@ -1,169 +0,0 @@
----
-title: Autorización
-sidebar_position: 30
----
-
-La autorización es el proceso de juzgar qué operaciones "deben" o "no deben" permitirse; se trata de juzgar el _permiso_.
-
-La autorización difiere de la _autenticación_, que es el problema más específico de juzgar si una persona "es quien dice ser" o si un mensaje que afirma provenir de una persona "realmente" vino de ella.
-
-La autorización a menudo usa autenticación criptográfica (a través de firmas) para respaldar sus juicios, pero es un proceso más amplio y general.
-
-Consulta la [guía inicial de autorización](../../../build/guides/auth/contract-authorization.mdx) para aprender más sobre la autorización de contratos inteligentes en Stellar.
-
-## Marco de Autorización Soroban
-
-Soroban tiene como objetivo proporcionar un marco liviano, pero flexible y extensible que permita a los contratos implementar reglas de autorización arbitrariamente complejas, mientras ofrece una implementación integrada para algunas tareas comunes (como la prevención de reproducción). El marco consta de los siguientes componentes:
-
-- Autorización específica de contratos: reglas de autorización personalizadas implementadas por contratos usando el almacenamiento privado del contrato y cuentas abstractas.
-- Abstracción de cuenta: permite a los usuarios personalizar sus reglas de autenticación y definir políticas universales de autorización mediante cuentas contrato. Esto incluye el soporte incorporado para cuentas Stellar.
-- Biblioteca de autorización basada en host: garantiza la integridad entre cuentas contrato y contratos regulares. También define el formato estructurado de la carga útil de la firma, asegura la prevención de reproducción y se encarga de proporcionar los contextos de firma correctos.
-
-El host de Soroban también proporciona algunas funciones criptográficas (verificación de firmas, hashing) que pueden ser útiles para implementaciones de cuentas contrato.
-
-Los contratos que usan el marco de autorización Soroban son interoperables entre sí. Además, es más fácil para las aplicaciones cliente escribir código genérico para interactuar con el marco de autorización Soroban. Por ejemplo, las billeteras pueden implementar una forma generalizada de presentar y firmar cargas útiles Soroban.
-
-Somos conscientes de que no es posible cubrir todos los casos, pero esperamos que la gran mayoría de los contratos puedan operar dentro del marco y así contribuir a construir un ecosistema más cohesivo. Todavía es posible implementar marcos de autorización personalizados, pero no se recomienda (a menos que no haya alternativas).
-
-### Autorización Específica de Contratos
-
-#### Almacenamiento de Contratos
-
-Los contratos tienen acceso exclusivo de lectura y escritura a su [almacenamiento](../../../build/smart-contracts/getting-started/storing-data.mdx) en el libro mayor. Esto permite que los contratos controlen y gestionen de forma segura el acceso de los usuarios a sus datos. Por ejemplo, un contrato de tokens puede asegurarse de que sólo el administrador pueda acuñar más tokens almacenando la identidad del administrador en su almacenamiento. De manera similar, puede asegurarse de que sólo un propietario del saldo pueda transferir ese saldo.
-
-#### `Address`
-
-El enfoque basado en almacenamiento descrito en la sección anterior requiere una manera de representar las identidades de usuario y de autenticarlas. El tipo `Address` es un tipo gestionado por el host que realiza estas funciones.
-
-Desde la perspectiva del contrato, `Address` es un tipo de identificador opaco. La lógica del contrato no necesita depender de la representación interna de `Address` (ver sección [Abstracción de cuenta](#account-abstraction) abajo para más detalles).
-
-El tipo `Address` tiene dos métodos similares en Soroban SDK: `require_auth` y `require_auth_for_args` (estos métodos llaman a la función respectiva del host Soroban). La única diferencia entre las funciones es la capacidad de personalizar los argumentos de invocación. Consulta el [ejemplo de autorización] que demuestra cómo usar estas funciones.
-
-Ambas funciones aseguran que el `Address` haya autorizado la llamada de la función actual dentro del contexto actual (donde contexto está definido por llamadas a `require_auth` en la pila de llamadas actual; ver definición más formal en la [sección abajo](#require_auth-implementation-details)). Las reglas de autenticación para esta autorización están definidas por el `Address` y son aplicadas por el host Soroban. La protección contra reproducción también está implementada en el host, es decir, normalmente no hay necesidad de que un contrato gestione sus propios nonces.
-
-[ejemplo de autorización]: ../../../build/smart-contracts/example-contracts/auth.mdx
-
-#### Autorizar llamadas a sub-contratos
-
-Una de las características clave del Marco de Autorización Soroban es la capacidad de realizar fácilmente llamadas autorizadas a sub-contratos. Por ejemplo, es posible que un contrato llame a `require_auth` para un `Address` y luego llame a `token.xfer` autorizado para el mismo `Address` (ver el [ejemplo de timelock] que demuestra este patrón).
-
-Los contratos no necesitan hacer nada especial para beneficiarse de esta función. Simplemente llamar a un sub-contrato que llame a `require_auth` asegurará que la llamada al sub-contrato haya sido correctamente autorizada.
-
-[ejemplo de timelock]: ../../../build/smart-contracts/example-contracts/timelock.mdx
-
-#### Cuándo usar `require_auth`
-
-La decisión principal relacionada con la autorización que el desarrollador de un contrato debe tomar para cualquier `Address` dado es si necesita llamar a `require_auth` para él. Aunque la decisión debe tomarse caso por caso, aquí hay algunas reglas generales:
-
-- Si el acceso a los datos de la `Address` en este contrato es sólo de lectura, entonces probablemente no se necesita `require_auth`.
-- Si los datos del `Address` en este contrato se están modificando de una manera que no es estrictamente beneficiosa para el usuario, entonces probablemente se necesita `require_auth` (por ejemplo, reducir el saldo de un usuario de tokens necesita autorización, mientras que aumentarlo no necesita autorización).
-- Si un contrato llama a otro contrato que llamará `require_auth` para el `Address` (por ejemplo, `token.xfer`), entonces añadir `require_auth` en el llamador aseguraría que la autorización para la llamada interna no pueda reutilizarse fuera de tu contrato. Por ejemplo, si quieres hacer algo positivo para el usuario, pero solo cuando hayan transferido algún token a tu contrato, entonces la llamada al contrato misma debe `require_auth`.
-
-#### Autorizar Múltiples `Address`es
-
-No hay ninguna restricción explícita sobre cuántas entidades `Address` usa el contrato y cuántos `Address`es han llamado `require_auth`.  Eso significa que es posible autorizar una llamada a contrato en nombre de varios usuarios, que pueden incluso tener diferentes contextos de autorización (personalizados a través de argumentos en `require_auth_for_args`). [Atomic swap] es un ejemplo que trata con la autorización de dos `Address`es.
-
-[intercambio atómico]: ../../../build/smart-contracts/example-contracts/atomic-swap.mdx
-
-Ten en cuenta que los contratos que manejan múltiples `Address`es autorizados necesitan un soporte un poco más complejo en el lado del cliente (para recolectar y adjuntar las firmas adecuadas).
-
-### Abstracción de cuenta
-
-La abstracción de cuenta es una forma de desacoplar la lógica de autenticación de las reglas de autorización específicas del contrato. El `Address` definido arriba es en realidad un identificador de una cuenta 'abstracta'. Es decir, los contratos conocen el `Address` y pueden exigir autorización de éste, pero no saben cómo está implementado exactamente.
-
-Por ejemplo, imagina un contrato de tokens. Sus responsabilidades son gestionar los saldos de múltiples usuarios (transferir, acuñar, quemar, etc.). Realmente no hay nada en estas responsabilidades que tenga que ver con _cómo exactamente_ el usuario autorizó la transacción que modifica el saldo. Los usuarios pueden querer usar alguna clave hardware que soporte una nueva generación de algoritmos criptográficos (que ni siquiera tienen que existir hoy) o pueden querer tener un esquema multisig personalizado y nada de esto realmente tiene que ver con la lógica del token.
-
-La abstracción de cuenta proporciona un punto de extensión conveniente para cada contrato que usa `Address` para autorización. No resuelve todos los problemas automáticamente: las herramientas del lado del cliente todavía pueden necesitar adaptarse para soportar diferentes esquemas de autenticación o diferentes billeteras. Pero el estado en cadena no necesita ser modificado, y modificar el estado en cadena es un problema mucho más difícil.
-
-#### Tipos de Implementaciones de Cuenta
-
-Conceptualmente, cada cuenta abstracta es un contrato especial que define reglas de autenticación y potencialmente algunas políticas adicionales de autorización específicas de cuenta. Sin embargo, por optimización e integración con las cuentas Stellar existentes, Soroban soporta 4 tipos diferentes de implementaciones de cuenta.
-
-A continuación se describen las implementaciones generales. Consulta la [guía](../contract-development/contract-interactions/stellar-transaction.mdx) de transacciones para la información concreta de cómo se representan las diferentes cuentas.
-
-##### Cuenta Stellar
-
-Corresponde a `Address::Account`.
-
-Este es un 'contrato de cuenta' especial incorporado que maneja todas las cuentas Stellar. No es un contrato real y no necesita ser desplegado.
-
-Esto soporta la multisig Stellar con umbral medio. Consulta la [documentación] de Stellar para más detalles sobre multisig y umbrales.
-
-[documentación]: ../transactions/signatures-multisig.mdx
-
-##### Invocador de Transacción
-
-Corresponde a `Address::Account`.
-
-Esta es también una cuenta Stellar, pero su firma se infiere de la cuenta fuente de la transacción Stellar (o de la operación, si tiene una).
-
-Esto es puramente una optimización de la [Cuenta Stellar](#stellar-account) que puede omitir una firma en caso de que la cuenta fuente de la transacción también autorice la invocación del contrato.
-
-##### Invocador de Contrato
-
-Corresponde a `Address::Contract`.
-
-Este es un caso especial de 'cuenta' que puede aparecer sólo cuando un contrato llama a otro contrato. Consideramos que dado que el contrato hace la llamada, debe estar autorizándola (de lo contrario, no debería haber hecho esa llamada). Por lo tanto, todas las llamadas a `require_auth` hechas en nombre del contrato invocador **directo** `Address` se consideran autorizadas (pero no las llamadas en nombre de contratos más profundos en la pila).
-
-##### Cuenta contrato
-
-Corresponde a `Address::Contract`.
-
-Este es el punto de extensión de la abstracción de cuentas. Un contrato que implementa la `CustomAccountInterface` y `__check_auth` se convierte en una cuenta contrato. Si algún contrato llama a `require_auth` para la `Address` de este contrato, el host de Soroban llamará a `__check_auth` con los argumentos correspondientes.
-
-`__check_auth` recibe una carga útil de firma, una lista de firmas (en cualquier formato definido por el usuario) y una lista de las invocaciones de contrato que están siendo autorizadas por estas firmas. Su responsabilidad es realizar la autenticación verificando las firmas y también (opcionalmente) aplicar una política de autorización personalizada. Por ejemplo, se puede implementar un sistema de pesos de firmas similar al de Stellar, pero también puede tener reglas personalizables para los pesos, por ejemplo, permitir gastar más de X unidades del token Y solo dado un peso de firma Z.
-
-Las cuentas contrato también pueden considerarse como una billetera custodial. Mantiene los fondos del usuario (saldos de tokens, NFTs, etc.) y brinda a los usuarios formas de autorizar operaciones sobre estos fondos. Nada impide que las cuentas contrato autoricen operaciones no relacionadas con los saldos; por ejemplo, pueden realizar funciones administrativas para tokens (las cuentas contrato definen qué hacer cuando se llama a `require_auth`).
-
-Para la interfaz exacta y más detalles, consulta el [ejemplo de cuenta simple].
-
-[Ejemplo de cuenta simple]: ../../../build/smart-contracts/example-contracts/simple-account.mdx
-
-### Secp256r1, passkeys y cuentas contrato
-
-Después de una exitosa votación de validadores públicos para actualizar la red principal Stellar al Protocolo 21, se habilitó el esquema de firma secp256r1 para transacciones de contratos inteligentes. Esto permite a los desarrolladores implementar passkeys para firmar transacciones en lugar de usar claves secretas o frases semilla. Para orientación, consulta la [guía de billetera passkey](../../../build/guides/contract-accounts/smart-wallets.mdx).
-
-### Conceptos Avanzados
-
-La mayoría de los contratos no necesitarán los conceptos descritos en esta sección. Consulta esto al desarrollar contratos complejos que manejan árboles profundos de llamadas y/o múltiples `Address`es.
-
-#### Detalles de implementación de `require_auth`
-
-Cuando una transacción Soroban se ejecuta en cadena, el host recopila una lista de entradas `SorobanAuthorizationEntry` de la transacción ([XDR][soroban-auth-entry]). Estas entradas contienen credenciales firmadas del autorizador y árboles de invocaciones autorizadas. El host utiliza estas entradas para verificar la autorización durante la ejecución del contrato.
-
-Cada vez que la función del host `require_auth`/`require_auth_for_args` es llamada para una cuenta que no es invocador de contrato, se realizan los siguientes pasos:
-
-- Encontrar un árbol de invocación autorizado que coincida con la llamada `require_auth`. El proceso de coincidencia es bastante complejo y se describe en la sección siguiente.
-- Si la autenticación aún no ha ocurrido para este árbol, entonces realizarla:
-  - Verificar la expiración de la firma. Las firmas expiradas no son válidas.
-  - Verificar y consumir el nonce. El nonce es un número arbitrario que debe ser único entre todas las firmas no expiradas de la dirección.
-  - Construir la preimagen esperada de la [carga útil de firma] y calcular su hash SHA-256 para obtener la carga útil final de la firma.
-  - Llamar a `__check_auth` del contrato de cuenta correspondiente al `Address` usando la carga útil de firma y las invocaciones del árbol de autorización.
-- Marcar la invocación como 'agotada' en su árbol de invocación autorizado. Las invocaciones 'agotadas' se omitirán al coincidir con futuras llamadas a `require_auth`.
-
-Si alguno de los pasos anteriores falla, la autorización se considera no exitosa.
-
-Nota que la autenticación ocurre sólo una vez por árbol, ya que todo el árbol debe estar firmado.
-
-[soroban-auth-entry]: https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-transaction.x#L570
-[preimagen de carga útil de firma]: https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-transaction.x#L703
-
-#### Coincidencia de Árboles de Invocación Autorizados
-
-Para que las autorizaciones tengan éxito, todas las llamadas a `require_auth`/`require_auth_for_args` deben estar cubiertas por los correspondientes árboles `SorobanAuthorizedInvocation` en una transacción (definidos en la [XDR][invocation-xdr] de la transacción).
-
-Formalmente, esta correspondencia se define de la siguiente manera.
-
-Dada una invocación de contrato de nivel superior `I`, podemos construir un 'árbol de invocación de contrato' `T` rastreando todas las llamadas a sub-contratos (un borde dirigido `A->B` en el árbol significa 'la función de contrato A llama a la función de contrato B'). Nota que sólo consideramos las funciones que se implementan en diferentes contratos, es decir, cualquier llamada de función que no involucre una invocación de contrato a través del host `call` se considera que pertenece al mismo nodo.
-
-Supongamos que se requiere autorización de las direcciones `A_1..A_N`. Entonces para cada dirección `A_i` hay dos tipos de nodos en el árbol de invocación `T`: nodos `R` que tuvieron una llamada `require_auth` para `A_i` y nodos `N` que no tuvieron tal llamada. Luego eliminamos todos los nodos `N` y todos los bordes de `T` y añadimos los bordes dirigidos que conectan los nodos `R` restantes de tal manera que el borde vaya de `R_j` a `R_k` si hubo un camino entre `R_j` y `R_k` en `T` que no contiene ningún otro nodo `R`. Como resultado obtenemos un bosque de árboles `SorobanAuthorizedInvocation` para `A_i`. Observa que estos árboles no tienen que tener como raíz al nodo `I` (es decir, la llamada de contrato de nivel superior), por lo tanto es posible, por ejemplo, agrupar la llamada autorizada sin requerir la firma de la función de agrupación.
-
-En términos más simples, los árboles `SorobanAuthorizedInvocation` para un `Address` son subconjuntos del árbol completo de invocación que están 'condensados' para contener solo invocaciones que tienen la llamada `require_auth` para ese `Address`.
-
-Durante el proceso de coincidencia que ocurre para cada `require_auth` el host intenta coincidir el camino actual en `T` con un árbol `SorobanAuthorizedInvocation` para el `Address` correspondiente. El camino se considera coincidente sólo cuando existe un camino correspondiente de nodos `R` _agotados_ que llevan a la llamada actual. Esto significa que si el `Address` firma una secuencia de llamadas `A.foo->B.bar->C.baz`, entonces su verificación de autorización fallará en caso de que `A.foo` llame directamente a `C.baz` porque `C.baz` debe ser llamado estrictamente desde `B.bar`.
-
-##### Direcciones duplicadas
-
-En caso de que la misma función de contrato llame a `require_auth` para el mismo `Address` múltiples veces (por ejemplo, cuando se agrupan varias operaciones del mismo usuario), cada llamada a `require_auth` aún debe tener un nodo correspondiente en el árbol `SorobanAuthorizedInvocation`. Por ello, puede haber múltiples árboles válidos que permitan pasar todas las verificaciones de autorización. No hay nada malo en esto: la dirección debe haber autorizado todas las invocaciones. El único requisito para que tales casos se manejen correctamente es asegurar que las llamadas a `require_auth` para un `Address` ocurran antes de las llamadas a sub-contratos correspondientes.
-
-[invocation-xdr]: https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-transaction.x#L537
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/README.mdx
deleted file mode 100644
index 4b9224966b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Interacciones con contratos
-sidebar_position: 8
----
-
-import DocCardList from "@theme/DocCardList";
-
-Conoce los métodos disponibles para que desarrolladores y usuarios interactúen con los contratos implementados.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx
deleted file mode 100644
index 1c1004eeef..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/cross-contract.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-sidebar_position: 10
-title: Contrato cruzado
-description: Interactuar con un contrato Soroban desde otro contrato Soroban.
----
-
-Una invocación entre contratos es un tipo de interacción poderosa (aunque costosa) con contratos. Una invocación de contrato es similar a iniciar un nuevo proceso porque el código que se ejecuta estará en un espacio de direcciones separado, lo que significa que no comparten ningún dato excepto el que se pasó en la invocación. Aunque una invocación de contrato normalmente transfiere el control a un contrato _diferente_, es posible transferir el control al contrato que se está ejecutando actualmente. Independientemente de si el contrato que recibe el control es un contrato diferente o el contrato que se está ejecutando actualmente, el valor devuelto por `get_invoking_contract` será el valor anterior de `get_current_contract`. Una invocación de contrato solo puede acceder a los métodos públicos de un contrato.
-
-Si un contrato contiene una función pública `f`, entonces invocar `f` se puede hacer llamando a la función Rust `f::invoke`.
-
-Algunos contratos, como el contrato de tokens, solo exportan las funciones de invocación de contrato. Al hacerlo, pueden asignar nombres amigables a esas funciones. Por ejemplo, [initialize](https://github.com/stellar/soroban-token-contract/blob/42380647bb817bf01c739c19286f18be881e0e41/src/contract.rs#L55-L57)
-
-```rust
-#[contractimpl(export_if = "export")]
-impl TokenTrait for Token {
-    fn initialize(e: Env, admin: Identifier, decimal: u32, name: Binary, symbol: Binary) {
-```
-
-se [exporta](https://github.com/stellar/soroban-token-contract/blob/42380647bb817bf01c739c19286f18be881e0e41/src/lib.rs#L26) como
-
-```rust
-pub use crate::contract::initialize::invoke as initialize;
-```
-
-Esta función luego es fácilmente [llamada por el contrato del pool de liquidez](https://github.com/stellar/soroban-examples/blob/4060d3bd5ee7846020b68ee583665a4d4cf4b315/liquidity_pool/src/lib.rs#L164-L171).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/overview.mdx
deleted file mode 100644
index 155e9034d1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/overview.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Resumen
-description: Interactuar con contratos inteligentes.
-sidebar_position: 5
----
-
-<head>
-  <title>Interactuar con contratos inteligentes.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Interactuar con contratos inteligentes." />
-  <meta
-    property="og:description"
-    content="Interactúa con contratos inteligentes mediante llamadas a funciones, invocación de contratos y operaciones en la blockchain."
-  />
-</head>
-
-Los contratos se invocan mediante un par de funciones host `call` y `try_call`:
-
-- `try_call(contract, function, args)` llama a la `function` exportada desde el `contract`, pasando `args` y devolviendo un `Error` en caso de cualquier error.
-- `call(contract, function, args)` simplemente llama a `try_call` con sus argumentos y atrapa el `Error`, propagando esencialmente el error.
-
-En ambos casos, `contract` es un objeto host `Binary` que contiene el ID del contrato, `function` es un `Symbol` que guarda el nombre de una función exportada a llamar, y `args` es un `Vector` de valores para pasar como argumentos.
-
-Estas funciones host pueden invocarse de dos maneras separadas:
-
-- Desde fuera del host, como cuando un usuario envía una transacción que llama a un contrato.
-- Desde dentro del host, cuando un contrato llama a otro.
-
-Ambos casos siguen la misma lógica:
-
-- El bytecode Wasm del contrato se obtiene desde una entrada `CONTRACT_DATA` del libro mayor en el sistema de almacenamiento del host.
-- Se instancia una VM Wasm por la duración de la invocación.
-- Se busca la función y se invoca, pasando los argumentos del llamador al llamado.
-
-Cuando la llamada ocurre desde fuera del host, normalmente los argumentos se proveen en forma serializada XDR que acompaña a la transacción, y se deserializan y convierten automáticamente a objetos host antes de invocar el contrato.
-
-Cuando la llamada ocurre desde dentro del host, los contratos llamador y llamado _comparten el mismo host_ y el llamador puede pasar referencias a objetos host directamente al llamado sin necesidad de serializar o deserializar.
-
-Dado que los objetos host son inmutables, hay un riesgo limitado al pasar una referencia compartida de un contrato a otro: el llamado no puede modificar el objeto de forma que sorprenda al llamador, solo crear nuevos objetos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
deleted file mode 100644
index d7fb44c57d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx
+++ /dev/null
@@ -1,629 +0,0 @@
----
-sidebar_position: 30
-title: Transacción Stellar
-description: Invocar y desplegar contratos inteligentes con la operación InvokeHostFunctionOp.
-toc_max_heading_level: 4
----
-
-<head>
-  <title>
-    {`Invocar y desplegar contratos inteligentes con la operación InvokeHostFunctionOp.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Invocar y desplegar contratos inteligentes con la operación InvokeHostFunctionOp."
-  />
-  <meta
-    property="og:description"
-    content="Invocar y desplegar contratos inteligentes con la operación InvokeHostFunctionOp."
-  />
-</head>
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-## Ejemplo de uso del SDK
-
-Algunos (pero no todos todavía) de los SDKs de Stellar tienen funciones integradas para gestionar la mayor parte del proceso de construir una transacción Stellar para interactuar con un contrato inteligente Soroban. A continuación, mostramos en JavaScript y Python cómo construir y enviar una transacción Stellar que invocará una instancia del contrato inteligente del [ejemplo increment](../../../../build/smart-contracts/getting-started/storing-data.mdx).
-
-<Tabs>
-<TabItem value="js" label="JavaScript">
-
-:::tip
-
-El existente [JavaScript SDK](https://github.com/stellar/js-stellar-sdk) ahora incorpora todos los elementos necesarios para Soroban. Solo necesitas instalarlo usando tu gestor de paquetes preferido.
-
-```bash
-npm install --save @stellar/stellar-sdk
-```
-
-:::
-
-```js
-(async () => {
-  const {
-    Keypair,
-    Contract,
-    rpc as StellarRpc,
-    TransactionBuilder,
-    Networks,
-    BASE_FEE,
-  } = require("@stellar/stellar-sdk");
-
-  // The source account will be used to sign and send the transaction.
-  // GCWY3M4VRW4NXJRI7IVAU3CC7XOPN6PRBG6I5M7TAOQNKZXLT3KAH362
-  const sourceKeypair = Keypair.fromSecret(
-    "SCQN3XGRO65BHNSWLSHYIR4B65AHLDUQ7YLHGIWQ4677AZFRS77TCZRB",
-  );
-
-  // Configure the SDK to use the `stellar-rpc` instance of your choosing.
-  const server = new StellarRpc.Server(
-    "https://soroban-testnet.stellar.org:443",
-  );
-
-  // Here we will use a deployed instance of the `increment` example contract.
-  const contractAddress =
-    "CBEOJUP5FU6KKOEZ7RMTSKZ7YLBS5D6LVATIGCESOGXSZEQ2UWQFKZW6";
-  const contract = new Contract(contractAddress);
-
-  // Transactions require a valid sequence number (which varies from one
-  // account to another). We fetch this sequence number from the RPC server.
-  const sourceAccount = await server.getAccount(sourceKeypair.publicKey());
-
-  // The transaction begins as pretty standard. The source account, minimum
-  // fee, and network passphrase are provided.
-  let builtTransaction = new TransactionBuilder(sourceAccount, {
-    fee: BASE_FEE,
-    networkPassphrase: Networks.TESTNET,
-  })
-    // The invocation of the `increment` function of our contract is added
-    // to the transaction. Note: `increment` doesn't require any parameters,
-    // but many contract functions do. You would need to provide those here.
-    .addOperation(contract.call("increment"))
-    // This transaction will be valid for the next 30 seconds
-    .setTimeout(30)
-    .build();
-
-  // We use the RPC server to "prepare" the transaction. This simulating the
-  // transaction, discovering the storage footprint, and updating the
-  // transaction to include that footprint. If you know the footprint ahead of
-  // time, you could manually use `addFootprint` and skip this step.
-  let preparedTransaction = await server.prepareTransaction(builtTransaction);
-
-  // Sign the transaction with the source account's keypair.
-  preparedTransaction.sign(sourceKeypair);
-
-  // Let's see the base64-encoded XDR of the transaction we just built.
-  console.log(
-    `Signed prepared transaction XDR: ${preparedTransaction
-      .toEnvelope()
-      .toXDR("base64")}`,
-  );
-
-  // Submit the transaction to the Stellar-RPC server. The RPC server will
-  // then submit the transaction into the network for us. Then we will have to
-  // wait, polling `getTransaction` until the transaction completes.
-  try {
-    let sendResponse = await server.sendTransaction(preparedTransaction);
-    console.log(`Sent transaction: ${JSON.stringify(sendResponse)}`);
-
-    if (sendResponse.status === "PENDING") {
-      let getResponse = await server.getTransaction(sendResponse.hash);
-      // Poll `getTransaction` until the status is not "NOT_FOUND"
-      while (getResponse.status === "NOT_FOUND") {
-        console.log("Waiting for transaction confirmation...");
-        // See if the transaction is complete
-        getResponse = await server.getTransaction(sendResponse.hash);
-        // Wait one second
-        await new Promise((resolve) => setTimeout(resolve, 1000));
-      }
-
-      console.log(`getTransaction response: ${JSON.stringify(getResponse)}`);
-
-      if (getResponse.status === "SUCCESS") {
-        // Make sure the transaction's resultMetaXDR is not empty
-        if (!getResponse.resultMetaXdr) {
-          throw "Empty resultMetaXDR in getTransaction response";
-        }
-        // Find the return value from the contract and return it
-        let transactionMeta = getResponse.resultMetaXdr;
-        let returnValue = getResponse.returnValue;
-        console.log(`Transaction result: ${returnValue.value()}`);
-      } else {
-        throw `Transaction failed: ${getResponse.resultXdr}`;
-      }
-    } else {
-      throw sendResponse.errorResultXdr;
-    }
-  } catch (err) {
-    // Catch and report any errors we've thrown
-    console.log("Sending transaction failed");
-    console.log(JSON.stringify(err));
-  }
-})();
-```
-
-</TabItem>
-<TabItem value="py" label="Python">
-
-:::tip
-
-El SDK de Python [`py-stellar-base`](https://stellar-sdk.readthedocs.io/en/soroban/) tiene soporte estable para interactuar con contratos inteligentes Soroban desde [v9.0.0](https://github.com/StellarCN/py-stellar-base/releases/tag/9.0.0).
-
-```bash
-pip install stellar-sdk
-```
-
-:::
-
-```py
-from typing import Optional, Union
-
-from stellar_sdk import scval, MuxedAccount, Keypair, Network
-from stellar_sdk.contract import AssembledTransaction, ContractClient
-
-
-# `IncrementContractClient` is automatically generated by stellar-contract-bindings, and you do not need to write it manually.
-# See https://github.com/lightsail-network/stellar-contract-bindings
-# stellar-contract-bindings python --contract-id CDMARRPKAZEZMASLYONRI4LJI6X3QLDJQ647YGQANG2PDCP746BD5U73 --rpc-url https://soroban-testnet.stellar.org
-class IncrementContractClient(ContractClient):
-    def increment(
-            self,
-            source: Union[str, MuxedAccount],
-            signer: Optional[Keypair] = None,
-            base_fee: int = 100,
-            transaction_timeout: int = 300,
-            submit_timeout: int = 30,
-            simulate: bool = True,
-            restore: bool = True,
-    ) -> AssembledTransaction[int]:
-        """Increment increments an internal counter, and returns the value."""
-        return self.invoke(
-            "increment",
-            [],
-            parse_result_xdr_fn=lambda v: scval.from_uint32(v),
-            source=source,
-            signer=signer,
-            base_fee=base_fee,
-            transaction_timeout=transaction_timeout,
-            submit_timeout=submit_timeout,
-            simulate=simulate,
-            restore=restore,
-        )
-
-
-# The source account will be used to sign and send the transaction.
-# GCWY3M4VRW4NXJRI7IVAU3CC7XOPN6PRBG6I5M7TAOQNKZXLT3KAH362
-source_keypair = Keypair.from_secret('SCQN3XGRO65BHNSWLSHYIR4B65AHLDUQ7YLHGIWQ4677AZFRS77TCZRB')
-
-rpc_server_url = "https://soroban-testnet.stellar.org:443"
-network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-contract_address = 'CDMARRPKAZEZMASLYONRI4LJI6X3QLDJQ647YGQANG2PDCP746BD5U73'
-
-client = IncrementContractClient(contract_address, rpc_server_url, network_passphrase)
-result = client.increment(source_keypair.public_key).sign_and_submit(source_keypair)
-print(result)
-```
-
-</TabItem>
-<TabItem value="java" label="Java">
-
-:::tip
-
-[java-stellar-sdk](https://github.com/stellar/java-stellar-sdk) ofrece soporte para Soroban, por favor visita la página principal del proyecto para más información.
-
-:::
-
-```java
-import java.io.IOException;
-import org.stellar.sdk.AccountNotFoundException;
-import org.stellar.sdk.InvokeHostFunctionOperation;
-import org.stellar.sdk.KeyPair;
-import org.stellar.sdk.Network;
-import org.stellar.sdk.PrepareTransactionException;
-import org.stellar.sdk.SorobanServer;
-import org.stellar.sdk.Transaction;
-import org.stellar.sdk.TransactionBuilder;
-import org.stellar.sdk.TransactionBuilderAccount;
-import org.stellar.sdk.requests.sorobanrpc.SorobanRpcErrorResponse;
-import org.stellar.sdk.responses.sorobanrpc.GetTransactionResponse;
-import org.stellar.sdk.responses.sorobanrpc.SendTransactionResponse;
-import org.stellar.sdk.scval.Scv;
-import org.stellar.sdk.xdr.TransactionMeta;
-
-public class SorobanExample {
-  public static void main(String[] args)
-      throws SorobanRpcErrorResponse, IOException, InterruptedException {
-
-    // The source account will be used to sign and send the transaction.
-    KeyPair sourceKeypair =
-        KeyPair.fromSecretSeed("SCQN3XGRO65BHNSWLSHYIR4B65AHLDUQ7YLHGIWQ4677AZFRS77TCZRB");
-
-    // Configure SorobanClient to use the `stellar-rpc` instance of your choosing.
-    SorobanServer sorobanServer = new SorobanServer("https://soroban-testnet.stellar.org");
-
-    // Here we will use a deployed instance of the `increment` example contract.
-    String contractAddress = "CBEOJUP5FU6KKOEZ7RMTSKZ7YLBS5D6LVATIGCESOGXSZEQ2UWQFKZW6";
-
-    // Transactions require a valid sequence number (which varies from one account to
-    // another). We fetch this sequence number from the RPC server.
-    TransactionBuilderAccount sourceAccount = null;
-    try {
-      sourceAccount = sorobanServer.getAccount(sourceKeypair.getAccountId());
-    } catch (AccountNotFoundException e) {
-      throw new RuntimeException("Account not found, please activate it first");
-    }
-
-    // The invocation of the `increment` function of our contract is added to the
-    // transaction. Note: `increment` doesn't require any parameters, but many
-    // contract functions do. You would need to provide those here.
-    InvokeHostFunctionOperation operation =
-        InvokeHostFunctionOperation.invokeContractFunctionOperationBuilder(
-                contractAddress, "increment", null)
-            .build();
-
-    // Create a transaction with the source account and the operation we want to invoke.
-    Transaction transaction =
-        new TransactionBuilder(sourceAccount, Network.TESTNET)
-            .addOperation(operation)
-            .setTimeout(30) // This transaction will be valid for the next 30 seconds
-            .setBaseFee(100) // The base fee is 100 stroops (0.00001 XLM)
-            .build();
-
-    // We use the RPC server to "prepare" the transaction. This simulating the
-    // transaction, discovering the storage footprint, and updating the transaction
-    // to include that footprint. If you know the footprint ahead of time, you could
-    // manually use `addFootprint` and skip this step.
-    try {
-      transaction = sorobanServer.prepareTransaction(transaction);
-    } catch (PrepareTransactionException e) {
-      // You should handle the error here
-      throw new RuntimeException(e);
-    }
-
-    // Sign the transaction with the source account's keypair.
-    transaction.sign(sourceKeypair);
-
-    // Let's see the base64-encoded XDR of the transaction we just built.
-    System.out.println("Signed prepared transaction XDR: " + transaction.toEnvelopeXdrBase64());
-
-    // Submit the transaction to the Stellar-RPC server. The RPC server will then
-    // submit the transaction into the network for us. Then we will have to wait,
-    // polling `getTransaction` until the transaction completes.
-    SendTransactionResponse response = sorobanServer.sendTransaction(transaction);
-    if (!SendTransactionResponse.SendTransactionStatus.PENDING.equals(response.getStatus())) {
-      throw new RuntimeException("Sending transaction failed");
-    }
-
-    // Poll `getTransaction` until the status is not "NOT_FOUND"
-    GetTransactionResponse getTransactionResponse;
-    while (true) {
-      System.out.println("Waiting for transaction confirmation...");
-      // See if the transaction is complete
-      getTransactionResponse = sorobanServer.getTransaction(response.getHash());
-      if (!GetTransactionResponse.GetTransactionStatus.NOT_FOUND.equals(
-          getTransactionResponse.getStatus())) {
-        break;
-      }
-      // Wait one second
-      Thread.sleep(1000);
-    }
-
-    System.out.println("get_transaction response: " + getTransactionResponse);
-
-    if (GetTransactionResponse.GetTransactionStatus.SUCCESS.equals(
-        getTransactionResponse.getStatus())) {
-      // Find the return value from the contract and return it
-      TransactionMeta transactionMeta =
-          TransactionMeta.fromXdrBase64(getTransactionResponse.getResultMetaXdr());
-      long returnValue = Scv.fromUint32(transactionMeta.getV3().getSorobanMeta().getReturnValue());
-      System.out.println("Transaction result: " + returnValue);
-    } else {
-      System.out.println("Transaction failed: " + getTransactionResponse.getResultXdr());
-    }
-  }
-}
-```
-
-</TabItem>
-</Tabs>
-
-## Uso de XDR
-
-Stellar soporta invocar y desplegar contratos con una nueva operación llamada `InvokeHostFunctionOp`. El [`stellar-cli`] abstrae estos detalles para el usuario, pero no todos los SDKs lo hacen todavía. Si estás desarrollando una dapp, probablemente te tocará construir la transacción XDR para enviar a la red.
-
-El `InvokeHostFunctionOp` puede usarse para realizar las siguientes operaciones Soroban:
-
-- Invocar funciones de contrato.
-- Subir Wasm de los nuevos contratos.
-- Desplegar nuevos contratos usando el Wasm subido o implementaciones incorporadas (esto actualmente incluye solo el [contrato token](../../../../tokens/stellar-asset-contract.mdx)).
-
-[`stellar-cli`]: ../../../../build/smart-contracts/getting-started/setup.mdx#install-the-stellar-cli
-
-Solo se permite un único `InvokeHostFunctionOp` por transacción. Los contratos deben usarse para realizar múltiples acciones atómicamente, por ejemplo, para desplegar un nuevo contrato e inicializarlo atómicamente.
-
-### InvokeHostFunctionOp
-
-El XDR de `HostFunction` e `InvokeHostFunctionOp` se encuentra [aquí][xdr].
-
-[xdr]: https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-transaction.x#L581
-
-```cpp
-union HostFunction switch (HostFunctionType type)
-{
-case HOST_FUNCTION_TYPE_INVOKE_CONTRACT:
-    InvokeContractArgs invokeContract;
-case HOST_FUNCTION_TYPE_CREATE_CONTRACT:
-    CreateContractArgs createContract;
-case HOST_FUNCTION_TYPE_UPLOAD_CONTRACT_WASM:
-    opaque wasm<>;
-};
-
-struct InvokeHostFunctionOp
-{
-    // Host function to invoke.
-    HostFunction hostFunction;
-    // Per-address authorizations for this host function.
-    SorobanAuthorizationEntry auth<>;
-};
-```
-
-#### Función
-
-El `hostFunction` en `InvokeHostFunctionOp` será ejecutado por el entorno host Soroban. Las funciones soportadas son:
-
-1. `HOST_FUNCTION_TYPE_INVOKE_CONTRACT`
-
-   - Esto invocará una función del contrato desplegado con los argumentos especificados en la estructura `invokeContract`.
-
-   ```cpp
-   struct InvokeContractArgs {
-    SCAddress contractAddress;
-    SCSymbol functionName;
-    SCVal args<>;
-   };
-   ```
-
-   `contractAddress` es la dirección del contrato a invocar, `functionName` es el nombre de la función a invocar y `args` son los argumentos a pasar a esa función.
-
-2. `HOST_FUNCTION_TYPE_UPLOAD_CONTRACT_WASM`
-   - Esto subirá el Wasm del contrato usando el blob `wasm` proporcionado.
-   - El Wasm subido puede identificarse por el hash SHA-256 del Wasm subido.
-
-3. `HOST_FUNCTION_TYPE_CREATE_CONTRACT`
-
-   - Esto desplegará una instancia de contrato en la red usando el `executable` especificado. El identificador del contrato de 32 bytes se basa en el valor `contractIDPreimage` y el identificador de red (así cada red tiene un espacio de nombres separado para identificadores de contratos).
-
-   ```cpp
-   struct CreateContractArgs
-   {
-       ContractIDPreimage contractIDPreimage;
-       ContractExecutable executable;
-   };
-   ```
-
-   - `executable` puede ser el hash SHA-256 del Wasm previamente subido o puede especificar que debe usarse un contrato incorporado:
-
-   ```cpp
-   enum ContractExecutableType
-   {
-       CONTRACT_EXECUTABLE_WASM = 0,
-       CONTRACT_EXECUTABLE_TOKEN = 1
-   };
-
-   union ContractExecutable switch (ContractExecutableType type)
-   {
-   case CONTRACT_EXECUTABLE_WASM:
-       Hash wasm_hash;
-   case CONTRACT_EXECUTABLE_TOKEN:
-       void;
-   };
-   ```
-
-   - `contractIDPreimage` se define de la siguiente manera:
-
-     ```cpp
-     union ContractIDPreimage switch (ContractIDPreimageType type)
-     {
-     case CONTRACT_ID_PREIMAGE_FROM_ADDRESS:
-         struct
-         {
-             SCAddress address;
-             uint256 salt;
-         } fromAddress;
-     case CONTRACT_ID_PREIMAGE_FROM_ASSET:
-         Asset fromAsset;
-     };
-     ```
-
-     - El identificador final del contrato se crea calculando el SHA-256 de esto junto con el identificador de red como parte de [`HashIDPreimage`]:
-
-     [`hashidpreimage`]: https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-transaction.x#L697
-
-     ```cpp
-     union HashIDPreimage switch (EnvelopeType type)
-     {
-     ...
-     case ENVELOPE_TYPE_CONTRACT_ID:
-         struct
-         {
-             Hash networkID;
-             ContractIDPreimage contractIDPreimage;
-         } contractID;
-     ...
-     ```
-
-     - `CONTRACT_ID_PREIMAGE_FROM_ADDRESS` especifica que el contrato será creado usando la dirección y la sal proporcionadas. Esta operación debe ser autorizada por `address` (ver la sección siguiente para más detalles).
-     - `CONTRACT_ID_FROM_ASSET` especifica que el contrato será creado usando el activo Stellar. Esto solo se soporta cuando `executable == CONTRACT_EXECUTABLE_TOKEN`. Ten en cuenta que el activo no necesita existir cuando esto se aplica, sin embargo, el emisor del activo será el administrador inicial del token. Cualquiera puede desplegar contratos de activos.
-
-##### Uso en JavaScript
-
-Cada una de estas variaciones de invocación de función host tiene métodos de conveniencia en el [JavaScript SDK](../../../../tools/sdks/client-sdks.mdx#javascript-sdk):
-
-- [`Operation.invokeHostFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeHostFunction) es el método de más bajo nivel que corresponde directamente al XDR.
-- [`Operation.invokeContractFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeContractFunction) es una abstracción para invocar el método de un contrato particular, similar a [`Contract.call`](https://stellar.github.io/js-stellar-sdk/Contract.html#call).
-- [`Operation.createStellarAssetContract`](https://stellar.github.io/js-stellar-sdk/Operation.html#.createStellarAssetContract) y [`Operation.createCustomContract`](https://stellar.github.io/js-stellar-sdk/Operation.html#.createCustomContract) son abstracciones para instanciar contratos: la primera es para envolver un [activo Stellar](../../../../tokens/how-to-issue-an-asset.mdx) existente en un contrato inteligente; la segunda es para desplegar tu propio contrato.
-- [`Operation.uploadContractWasm`](https://stellar.github.io/js-stellar-sdk/Operation.html#.uploadContractWasm) corresponde a la variante `HOST_FUNCTION_TYPE_UPLOAD_CONTRACT_WASM` antes mencionada, permitiéndote subir el buffer WASM crudo al ledger.
-
-#### Datos de autorización
-
-El [marco de autorización](../authorization.mdx) de Soroban provee una forma estandarizada de pasar datos de autorización a las invocaciones del contrato mediante estructuras `SorobanAuthorizationEntry`.
-
-```cpp
-struct SorobanAuthorizationEntry
-{
-    SorobanCredentials credentials;
-    SorobanAuthorizedInvocation rootInvocation;
-};
-
-union SorobanCredentials switch (SorobanCredentialsType type)
-{
-case SOROBAN_CREDENTIALS_SOURCE_ACCOUNT:
-    void;
-case SOROBAN_CREDENTIALS_ADDRESS:
-    SorobanAddressCredentials address;
-};
-```
-
-`SorobanAuthorizationEntry` contiene un árbol de invocaciones con `rootInvocation` como raíz. Este árbol es autorizado por un usuario especificado en `credentials`.
-
-`SorobanAddressCredentials` tiene dos opciones:
-
-- `SOROBAN_CREDENTIALS_SOURCE_ACCOUNT` - esto simplemente usa la firma de la cuenta fuente de la transacción (o la operación si existe) y por lo tanto no requiere ninguna carga adicional.
-- `SOROBAN_CREDENTIALS_ADDRESS` - contiene `SorobanAddressCredentials` con la siguiente estructura:
-  ```cpp
-  struct SorobanAddressCredentials
-  {
-      SCAddress address;
-      int64 nonce;
-      uint32 signatureExpirationLedger;
-      SCVal signature;
-  };
-  ```
-  Los campos de esta estructura tienen las siguientes semánticas:
-  - Cuando `address` es la dirección que autoriza la invocación.
-  - `signatureExpirationLedger` es el número de secuencia del ledger en el que la firma expira. La firma aún se considera válida en `signatureExpirationLedger`, pero no es válida en `signatureExpirationLedger + 1`. Se recomienda mantener esto lo más pequeño posible, ya que hace la transacción más económica.
-  - `nonce` es un valor arbitrario que es único para todas las firmas realizadas por `address` hasta `signatureExpirationLedger`. Una buena práctica para generar esto es simplemente usar un valor aleatorio.
-  - `signature` es una estructura que contiene la(s) firma(s) que firmaron el hash SHA-256 de 32 bytes del preimagen `ENVELOPE_TYPE_SOROBAN_AUTHORIZATION` ([XDR][envelope-xdr]). La estructura de la firma está definida por el contrato de cuenta correspondiente a la `Address` (ver más abajo la estructura de firma de las cuentas Stellar).
-
-`SorobanAuthorizedInvocation` define un nodo en el árbol de invocaciones autorizadas:
-
-```cpp
-struct SorobanAuthorizedInvocation
-{
-    SorobanAuthorizedFunction function;
-    SorobanAuthorizedInvocation subInvocations<>;
-};
-
-union SorobanAuthorizedFunction switch (SorobanAuthorizedFunctionType type)
-{
-case SOROBAN_AUTHORIZED_FUNCTION_TYPE_CONTRACT_FN:
-    SorobanAuthorizedContractFunction contractFn;
-case SOROBAN_AUTHORIZED_FUNCTION_TYPE_CREATE_CONTRACT_HOST_FN:
-    CreateContractArgs createContractHostFn;
-};
-
-struct SorobanAuthorizedContractFunction
-{
-    SCAddress contractAddress;
-    SCSymbol functionName;
-    SCVec args;
-};
-```
-
-`SorobanAuthorizedInvocation` consiste en la `function` que está siendo autorizada (ya sea función de contrato o función host) y las sub-invocaciones autorizadas que `function` realiza (si las hay).
-
-`SorobanAuthorizedFunction` tiene dos variantes:
-
-- `SOROBAN_AUTHORIZED_FUNCTION_TYPE_CONTRACT_FN` es una función de contrato que incluye la dirección del contrato, el nombre de la función que se invoca y los argumentos de `require_auth`/`require_auth_for_args` realizados en nombre de la dirección. Ten en cuenta que si no se llamó a `require_auth[_for_args]`, no debería haber una entrada `SorobanAuthorizedInvocation` en la transacción.
-- `SOROBAN_AUTHORIZED_FUNCTION_TYPE_CREATE_CONTRACT_HOST_FN` es autorización para `HOST_FUNCTION_TYPE_CREATE_CONTRACT` o para la función host `create_contract` llamada desde un contrato. Solo contiene la estructura XDR `CreateContractArgs` correspondiente al contrato creado.
-
-La construcción de árboles `SorobanAuthorizedInvocation` puede simplificarse usando el modo de grabación de autorización en el mecanismo `simulateTransaction` de Soroban (ver los [docs][simulate-transaction-doc] para más detalles).
-
-[envelope-xdr]: https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-transaction.x#L703
-[simulate-transaction-doc]: transaction-simulation.mdx#authorization
-
-##### Firmas de cuentas Stellar
-
-El formato `signatureArgs` es definido por el usuario para las [custom accounts], pero está definido por el protocolo para las cuentas Stellar.
-
-Las firmas para la cuenta Stellar son un vector de las siguientes estructuras Soroban en formato Soroban SDK:
-
-```rust
-#[contracttype]
-pub struct AccountEd25519Signature {
-    pub public_key: BytesN<32>,
-    pub signature: BytesN<64>,
-}
-```
-
-[structures]: https://github.com/stellar/rs-soroban-env/blob/99d8c92cdc7e5cd0f5311df8f88d04658ecde7d2/soroban-env-host/src/native_contract/account_contract.rs#L51
-[custom accounts]: ../authorization.mdx#account-abstraction
-
-##### Uso en JavaScript
-
-Hay un par de métodos útiles en el SDK para facilitar el manejo de autorizaciones:
-
-- Una vez que hayas obtenido las entradas de autorización de [`simulateTransaction`](https://soroban.stellar.org/api/methods/simulateTransaction), puedes usar el ayudante [`authorizeEntry`](https://stellar.github.io/js-stellar-sdk/global.html#authorizeEntry) para "completar" la entrada vacía correctamente. Por supuesto, necesitarás el firmante apropiado para cada una de las entradas si estás en una situación multiusuario.
-
-```typescript
-const signedEntries = simTx.auth.map(async (entry) =>
-  // In this case, you can authorize by signing the transaction with the
-  // corresponding source account.
-  entry.switch() ===
-  xdr.SorobanCredentialsType.sorobanCredentialsSourceAccount()
-    ? entry
-    : await authorizeEntry(
-        entry,
-        // The `signer` here will be unique for each entry, perhaps reaching out
-        // to a separate entity.
-        signer,
-        currentLedger + 1000,
-        Networks.TESTNET,
-      ),
-);
-```
-
-- Si en cambio deseas _construir_ una entrada de autorización desde cero en lugar de depender de la simulación, puedes usar [`authorizeInvocation`](https://stellar.github.io/js-stellar-sdk/global.html#authorizeInvocation), que generará la estructura con los campos apropiados.
-
-### Recursos de la transacción
-
-Cada transacción Soroban debe tener un [extension] `SorobanTransactionData` poblado. Esto es necesario para calcular la [tarifa de recursos Soroban](../../../fundamentals/fees-resource-limits-metering.mdx).
-
-[extension]: https://github.com/stellar/stellar-xdr/blob/c2e702c70951ff59a1eff257f08cf38d47210e5f/Stellar-transaction.x#L874
-
-Los datos de la transacción Soroban se definen como sigue:
-
-```cpp
-struct SorobanResources
-{
-    // The ledger footprint of the transaction.
-    LedgerFootprint footprint;
-    // The maximum number of instructions this transaction can use
-    uint32 instructions;
-
-    // The maximum number of bytes this transaction can read from ledger
-    uint32 readBytes;
-    // The maximum number of bytes this transaction can write to ledger
-    uint32 writeBytes;
-};
-
-struct SorobanTransactionData
-{
-    SorobanResources resources;
-    // Portion of transaction `fee` allocated to refundable fees.
-    int64 refundableFee;
-    ExtensionPoint ext;
-};
-```
-
-Estos datos comprenden dos partes: recursos Soroban y `refundableFee`. `refundableFee` es la parte de la tarifa de transacción que es elegible para reembolso. Incluye las tarifas por los eventos de contrato emitidos por la transacción, el valor devuelto de la invocación de la función host, y las tarifas por el [alquiler de espacio en ledger](../storage/state-archival.mdx).
-
-La estructura `SorobanResources` incluye la huella del ledger y los valores de recursos, que juntos determinan el límite de consumo de recursos y la tarifa por recursos. La huella debe contener los `LedgerKey`s que serán leídos y/o escritos.
-
-El método más sencillo para determinar los valores en `SorobanResources` y `refundableFee` es usar el mecanismo [`simulateTransaction`](transaction-simulation.mdx).
-
-#### Uso en JavaScript
-
-Puedes usar [`SorobanDataBuilder`](https://stellar.github.io/js-stellar-sdk/SorobanDataBuilder.html) para aprovechar el [patrón Builder](https://en.wikipedia.org/wiki/Builder_pattern) y obtener/configurar todos los recursos mencionados arriba adecuadamente. Luego, llamas a `.build()` y pasas la estructura resultante al método [`setSorobanData`](https://stellar.github.io/js-stellar-sdk/TransactionBuilder.html#setSorobanData) del correspondiente [`TransactionBuilder`](https://stellar.github.io/js-stellar-sdk/TransactionBuilder.html).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/tests.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/tests.mdx
deleted file mode 100644
index bac8c84f32..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/tests.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-sidebar_position: 20
-title: Pruebas
-description: Interactuar con contratos en pruebas
----
-
-[Depurar contratos](../errors-and-debugging/debugging.mdx) explica que es mucho más conveniente depurar usando código nativo que Wasm. Dado que estás probando código nativo, es tentador interactuar directamente con tu contrato usando llamadas a funciones. Si intentas este enfoque, descubrirás que no siempre funciona. Las interacciones mediante llamadas a funciones no configuran el entorno en el estado correcto para la ejecución del contrato, por lo que las funciones que involucran datos del contrato y la determinación del contrato actual o invocador no funcionarán.
-
-Al escribir pruebas, es importante interactuar siempre con los contratos mediante invocación de contratos. En un entorno de producción, la invocación de contratos ejecutará bytecode Wasm cargado desde el libro mayor. ¿Entonces cómo funciona esto si estás probando código nativo? Debes registrar tu contrato con el entorno para que sepa qué funciones están disponibles y cómo llamarlas. Aunque esto suena complejo, el macro procedural `contractimpl` genera automáticamente casi todo el código para hacerlo. Todo lo que tienes que hacer es escribir un pequeño [stub](https://github.com/stellar/soroban-token-contract/blob/42380647bb817bf01c739c19286f18be881e0e41/src/testutils.rs#L12-L15) para llamar realmente al código generado, como
-
-```rust title="test.rs"
-pub fn register_test_contract(e: &Env, contract_id: &[u8; 32]) {
-    let contract_id = FixedBinary::from_array(e, *contract_id);
-    e.register(crate::contract::Token {}, &contract_id);
-}
-```
-
-Algunos contratos, como el contrato de token, también proporcionan una [interfaz más amigable](https://github.com/stellar/soroban-token-contract/blob/42380647bb817bf01c739c19286f18be881e0e41/src/testutils.rs#L26-L191) para facilitar las pruebas. Existen muchas maneras en que estas interfaces pueden facilitar las pruebas, pero una común es permitir la firma automática de mensajes pasando un [ed25519_dalek::Keypair](https://docs.rs/ed25519-dalek/latest/ed25519_dalek/).
-
-Ten en cuenta que todo lo descrito en esta sección sólo está disponible si la característica `testutils` está habilitada.
-
-### Ejemplo
-
-Esta maquinaria también puede usarse para probar múltiples contratos juntos. Por ejemplo, el caso de prueba del contrato de oferta única [crea un token](https://github.com/stellar/soroban-examples/blob/56fef787395b5aed7cd7b19772cca28e21b3feb5/single_offer/src/test.rs#L22).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
deleted file mode 100644
index 39494fea9b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-interactions/transaction-simulation.mdx
+++ /dev/null
@@ -1,215 +0,0 @@
----
-sidebar_position: 40
-title: Simulación de transacciones
-description: Simula una interacción con un contrato contenida en una transacción Stellar.
----
-
-## Footprint
-
-Como se menciona en la sección de [persistencia de datos](../storage/persisting-data.mdx), un contrato sólo puede cargar o almacenar entradas `CONTRACT_DATA` que estén declaradas en una _footprint_ asociada a su invocación.
-
-Un footprint es un conjunto de claves del libro mayor (ledger), cada una marcada como sólo lectura o lectura-escritura. Las claves sólo de lectura están disponibles para la transacción para lectura; las claves de lectura-escritura están disponibles para lectura, escritura o ambas.
-
-Cualquier transacción Soroban enviada por un usuario debe ir acompañada de esta footprint. Un único footprint abarca _todos_ los datos leídos y escritos por _todos_ los contratos invocados transitivamente por la transacción: no solo el contrato inicial que la transacción llama, sino también todos los contratos que llama, y así sucesivamente.
-
-Como puede ser difícil para un usuario saber qué entradas del libro mayor intentará leer o escribir una llamada a contrato dada (especialmente las entradas causadas por otros contratos profundos en una transacción), el host proporciona un mecanismo auxiliar `simulateTransaction` que ejecuta una transacción contra una _instantánea_ temporal y posiblemente desactualizada del libro mayor. El mecanismo `simulateTransaction` _no_ está restringido solo a leer o escribir el contenido de una footprint; más bien _registra_ una footprint que describe la ejecución de la transacción, descarta los efectos de la ejecución y luego devuelve la footprint registrada a su llamante.
-
-Esta footprint proporcionada por la simulación puede usarse para acompañar una "verdadera" presentación de la misma transacción a la red para su ejecución real. Si el estado del libro mayor ha cambiado demasiado entre el momento de la simulación y la presentación real, la footprint puede estar demasiado obsoleta y dejar de identificar con precisión las _claves_ que la transacción necesita leer y/o escribir, en cuyo caso la simulación debe repetirse para actualizar la footprint.
-
-En cualquier caso (ya sea que tenga éxito o falle), la transacción real se ejecutará de forma atómica, determinista y con semánticas de consistencia serializable. Una footprint incorrecta simplemente causa un fallo determinista de la transacción, no una anomalía de lectura obsoleta. Todos los efectos de dicha transacción fallida se descartan, como sucedería con cualquier otro error.
-
-## Autorización
-
-Consulta la [visión general de autorizaciones](../authorization.mdx) y la sección de autorización de transacciones [auth-data] para información general sobre la autorización en Soroban: esta sección se refiere específicamente a cómo funciona la simulación junto con los requisitos de autorización.
-
-El [mecanismo de simulación de transacciones][sim-tx] de Soroban puede usarse para precomputar los árboles de [`SorobanAuthorizedInvocation`][auth-invoke] que deben ser autorizados por las `Address` para que todas las comprobaciones `require_auth` pasen. Puede invocarse de dos formas diferentes:
-
-### Modo de Grabación
-
-El entorno host de Soroban proporciona un modo de simulación que registra el contexto completo (dirección, ID del contrato, función, argumentos, etc.) involucrado en las llamadas a `require_auth`.
-
-Estos registros se agregan a un árbol de [`SorobanAuthorizedInvocation`][auth-invoke] y se marcan como exitosos. Luego, tras terminar la invocación, la simulación de transacciones devuelve todos los árboles registrados, así como valores nonce generados aleatoriamente para las firmas esperadas.
-
-Con esta información desde la simulación, el cliente solo necesita proporcionar estos árboles y nonces a las `Address` involucradas en la invocación para firmar, y luego construir la transacción final combinando la salida de la simulación con las firmas correspondientes.
-
-Nota que el modo de autenticación "grabación" _nunca_ emula fallos de autorización. Esto ocurre porque un fallo en la autorización siempre es una situación "excepcional" (es decir, las `Address` para las cuales no esperas que la autorización tenga éxito no deberían usarse desde el principio). Es similar a cómo, por ejemplo, el mecanismo [`simulateTransaction`][sim-tx] no emula fallos causados por una footprint incorrecta.
-
-Si quieres validar firmas, debes usar [`simulateTransaction`][sim-tx] en modo de autorización ["enforcement"](#enforcing-mode), que verificará las firmas antes de ejecutar la transacción en la cadena.
-
-### Modo de Enforcement
-
-El modo de grabación de autenticación es una opción para [`simulateTransaction`][sim-tx]. Sin embargo, al tratar con contratos de cuenta personalizados, por ejemplo, puede ser necesario simular el código `__check_auth` de la cuenta personalizada (que simplemente se _omite_ en el modo de grabación), para obtener su footprint del libro mayor.
-
-Esto se denomina ejecutar la simulación en modo de autenticación "enforcement". Esto es básicamente equivalente a ejecutar la transacción en la cadena (con posiblemente un estado del libro ligeramente desactualizado); por lo tanto, requiere que todas las firmas sean válidas.
-
-Desde la perspectiva del desarrollador, la diferencia entre estos modos es si las entradas de autorización están presentes en la operación [`InvokeHostFunction`](../../../../learn/fundamentals/transactions/list-of-operations.mdx#invoke-host-function) enviada a [`simulateTransaction`][sim-tx]. Los [ejemplos a continuación](#typescript-utilities) detallan esta distinción, pero en resumen, pasar `auth` a [`Operation.invokeContractFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeContractFunction) (que es una envoltura conveniente para [`invokeHostFunction`](https://stellar.github.io/js-stellar-sdk/Operation.html#.invokeHostFunction)) implicará el modo enforcement.
-
-### Uso del SDK
-
-A continuación, demostraremos las diferentes formas en que puedes invocar la simulación de transacciones y destacaremos algunas utilidades disponibles en el [SDK de TypeScript](https://stellar.github.io/js-stellar-sdk/) para autorización.
-
-Cubriremos tres tipos de invocaciones:
-
-- Una invocación simple en la que la cuenta fuente de la transacción es el único firmante para el árbol de invocación.
-- Una invocación en la que se necesitan las firmas de dos cuentas para el árbol de invocación.
-- Una invocación en modo enforcement para confirmar que las firmas son correctas.
-
-#### Ejemplo 1: autorización de la cuenta fuente.
-
-En esta variante, usaremos la variante de "autorización de cuenta fuente": es cuando la cuenta fuente en la transacción es la única que necesita firmar la invocación (ver la variante "cuenta fuente" de [`SorobanCredentials`](https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-transaction.x#L586-L595)). En este escenario, la firma en la transacción en sí implica directamente la firma de la invocación.
-
-<CodeExample>
-
-```javascript
-import {
-  Asset,
-  Keypair,
-  Networks,
-  Operation,
-  authorizeEntry,
-  TransactionBuilder,
-  xdr,
-} from "@stellar/stellar-sdk";
-import { Server, assembleTransaction } from "@stellar/stellar-sdk/rpc";
-
-const s = Server("https://soroban-testnet.stellar.org");
-
-// Pretend is is a real, funded account.
-const signer = Keypair.random();
-const xlmContract = Asset.native().contractId(Networks.TESTNET);
-
-async function main() {
-  const tx = new TransactionBuilder(await s.loadAccount(signer.publicKey()), {
-    networkPassphrase: Networks.TESTNET,
-    fee: BASE_FEE,
-  })
-    .addOperation(
-      Operation.invokeContractFunction(
-        xlmContract,
-        [
-          ["balance", "symbol"],
-          [signer.publicKey(), "address"],
-        ].map((val, type) => nativeToScVal(val, { type })),
-      ),
-    )
-    .build();
-
-  const preppedTx = s.prepareTransaction(tx);
-  preppedTx.sign(signer);
-
-  const sendTx = await s.sendTransaction(preppedTx);
-  return s.pollTransaction(sendTx.hash);
-}
-
-main().catch((e) => console.error(e));
-```
-
-</CodeExample>
-
-Observa que, en contraste con el ejemplo siguiente, no necesitamos hacer la simulación por separado. Esto es porque podemos firmar la transacción tal cual en lugar de inspeccionar sus entradas de autorización.
-
-#### Ejemplo 2: autenticación multipartita.
-
-En esta variante, extenderemos las firmas requeridas a más de una parte, de modo que la cuenta fuente ya no sea suficiente. Usaremos el [helper `authorizeEntry`](https://stellar.github.io/js-stellar-sdk/global.html#authorizeEntry), diseñado específicamente para facilitar la firma de las entradas devueltas por la simulación de transacciones.
-
-<CodeExample>
-
-```typescript
-import {
-  Asset,
-  Keypair,
-  Networks,
-  Operation,
-  authorizeEntry,
-  TransactionBuilder,
-  xdr,
-} from "@stellar/stellar-sdk";
-import { Server, assembleTransaction } from "@stellar/stellar-sdk/rpc";
-
-const s = Server("https://soroban-testnet.stellar.org");
-
-// Pretend these are real, funded accounts.
-const signers = [Keypair.random(), Keypair.random()];
-const xlmContract = Asset.native().contractId(Networks.TESTNET);
-
-async function main() {
-  // Notice that the source account is the first keypair, but the transfer
-  // occurs *from* the second keypair, which means the second keypair will
-  // need to sign for an authorization entry to approve the transfer.
-  const tx = new TransactionBuilder(
-    await s.loadAccount(signers[0].publicKey()),
-    {
-      networkPassphrase: Networks.TESTNET,
-      fee: BASE_FEE,
-    },
-  )
-    .addOperation(
-      Operation.invokeContractFunction(
-        xlmContract,
-        [
-          ["transfer", "symbol"],
-          [signers[1].publicKey(), "address"], // from
-          [signers[0].publicKey(), "address"], // to
-          [1000, "i128"], // amount
-        ].map((val, type) => nativeToScVal(val, { type })),
-      ),
-    )
-    .build();
-
-  const simResult = s.simulateTransaction(tx);
-
-  // For every auth entry that needs signing, sign it with the correct keypair.
-  //
-  // Inject the auths back into the simulation result so they
-  // get assembled into our transaction.
-  simResult.result.auth = simResult.result.auth.map((entry) =>
-    authorizeEntry(
-      entry,
-      // Ignore source account entries, which is handled as a no-op.
-      entry.credentials().switch() !==
-        xdr.SorobanCredentialsType.sorobanCredentialsSourceAccount()
-        ? signers.find(
-            // Find the keypair that matches the entry's address.
-            (signer) =>
-              Address.fromScAddress(
-                entry.credentials().address().address(),
-              ).toString() === signer.publicKey(),
-          )
-        : null,
-      response.latestLedger + 12, // signature is valid for ~1m
-      Networks.TESTNET,
-    ),
-  );
-
-  const preppedTx = assembleTransaction(tx, simResult);
-  preppedTx.sign(signers[0]);
-
-  const sendTx = await s.sendTransaction(preppedTx);
-  return s.pollTransaction(sendTx.hash);
-}
-
-main().catch((e) => console.error(e));
-```
-
-</CodeExample>
-
-Alternativamente, podríamos ir un nivel más bajo en la pila y construir nosotros mismos las entradas de autorización usando [`authorizeInvocation`](https://stellar.github.io/js-stellar-sdk/global.html#authorizeInvocation), dándonos control total sobre la "pila de llamadas" que se está invocando. Esto puede ser útil si quieres autorizar invocaciones específicas, construir las invocaciones tú mismo, o reducir el ancho de banda que usas al compartir entradas para que otros firmen.
-
-#### Ejemplo 3: modo enforcement.
-
-En este ejemplo, usaremos el modo de autorización ["enforcement"](#enforcing-mode) de la simulación de transacciones [simulation][sim-tx], que, al recibir entradas de autorización firmadas, asegura que sean las firmas necesarias y suficientes para la ejecución de la transacción.
-
-Para mantener las cosas muy simples, no haremos mucha codificación. En cambio, sólo mostraremos la diferencia con el ejemplo anterior: todo lo que necesitamos es ejecutar la simulación una vez más.
-
-```diff
--  preppedTx.sign(signers[0]);
--
--  const sendTx = await s.sendTransaction(preppedTx);
-+  const resimTx = await s.prepareTransaction(preppedTx);
-+  resimTx.sign(signers[0]);
-+  const sendTx = await s.sendTransaction(resimTx);
-```
-
-[auth-data]: stellar-transaction.mdx#authorization-data
-[auth-invoke]: https://github.com/stellar/stellar-xdr/blob/v22.0/Stellar-transaction.x#L558
-[sim-tx]: ../../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-lifecycle.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-lifecycle.mdx
deleted file mode 100644
index 5b614f5499..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/contract-lifecycle.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-sidebar_position: 50
-title: Ciclo de vida del contrato
-description: El proceso de desarrollar, desplegar y mantener contratos inteligentes.
----
-
-<head>
-  <title>
-    {`El proceso de desarrollar, desplegar y mantener contratos inteligentes.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="El proceso de desarrollar, desplegar y mantener contratos inteligentes."
-  />
-  <meta
-    property="og:description"
-    content="Aprende cómo funcionan los contratos inteligentes desde el desarrollo, despliegue y ejecución hasta cómo monitorearlos y actualizarlos."
-  />
-</head>
-
-## Desarrollo
-
-El desarrollo de contratos puede realizarse en un ordenador local con tan solo 3 componentes necesarios: un IDE, una copia del conjunto de herramientas Rust y una copia del SDK de Soroban.
-
-El SDK contiene una copia funcional completa del entorno host, así como una versión "mock" del ledger para el almacenamiento persistente de datos del contrato. Por lo tanto, es posible (y recomendable) editar, compilar, probar y depurar contratos directamente contra esta copia "local" del host, completamente sin conexión y sin siquiera acceder a una test net.
-
-Para hacer que el proceso de desarrollo local sea aún más conveniente y rápido, el contrato que se está desarrollando puede (y debe) ser compilado como código nativo y vinculado directamente al host local, en lugar de compilarse a Wasm y ejecutarse en una sandbox de VM local. Ambas configuraciones son posibles, pero la configuración nativa es la más rápida y ofrece la experiencia más completa de prueba y depuración.
-
-El host de contrato local provisto por el SDK también contiene un servidor web local que ofrece el endpoint HTTP necesario para que las aplicaciones cliente interactúen con un contrato. Esto puede usarse para el desarrollo local de aplicaciones, nuevamente sin necesidad de desplegar contratos en ninguna red de prueba o red activa.
-
-## Despliegue
-
-Una vez que un contrato ha sido probado y depurado localmente, puede desplegarse. Para hacerlo, debe compilarse a código Wasm y luego incluirse por valor en una transacción enviada a la red de despliegue prevista.
-
-El SDK proporciona una utilidad de línea de comandos que invoca al compilador Rust con la configuración correcta para producir un paquete Wasm para su implementación, pero los desarrolladores también pueden construir esto por sí mismos.
-
-Antes de enviarlo a la red, los desarrolladores deben inspeccionar el binario Wasm resultante emitido por el compilador Rust para asegurarse de que contenga únicamente el código y los datos previstos y que sea lo más pequeño posible. La utilidad de línea de comandos del SDK contiene comandos de diagnóstico para asistir en este proceso.
-
-La utilidad de línea de comandos del SDK también puede construir y enviar la transacción que despliega un contrato Wasm en la red. La implementación requiere credenciales suficientes en la red para firmar una transacción que realice la implementación y pague sus tarifas. Los contratos deben implementarse en redes de prueba y probarse exhaustivamente allí antes de ser implementados en la red activa.
-
-:::note
-
-[Verifica tu contrato en StellarExpert](https://stellar.expert/explorer/public/contract/validation).
-
-Este proceso de GitHub Actions compila y optimiza tu contrato Stellar, publica una versión en GitHub con los artefactos desarrollados y los hashes SHA256, y envía el hash, nombre del repositorio y commit a StellarExpert.
-
-Una vez validado, StellarExpert muestra un enlace al commit exacto de GitHub para que cualquiera pueda revisar el código fuente original y confirmar que igualarán con el contrato desplegado.
-
-:::
-
-## Ejecución
-
-Los contratos implementados viven en cadena dentro de una entrada del ledger CONTRACT_DATA. Se ejecutan dentro de una sandbox de VM gestionada por un entorno host dentro de stellar-core. Cada transacción que conduce a la ejecución de un contrato se ejecuta en un entorno host separado, y cada contrato llamado por dicha transacción (ya sea directamente o indirectamente desde otro contrato) se ejecuta en una VM Wasm invitada separada contenida dentro del entorno host de la transacción.
-
-La ejecución se inicia mediante una función host llamada "call". La función host "call" puede ser invocada de dos maneras diferentes: bien por alguien que envía una transacción a la red que invoca "call" directamente, o indirectamente por otro contrato que invoca "call".
-
-En cualquiera de los dos casos, a la función host "call" se le proporciona el ID de un contrato para invocar, el nombre de una función dentro del contrato, y un vector de valores para pasar como argumentos. Luego, la función host "call" configura una sandbox de VM para el contrato invocado, carga e instancia su bytecode Wasm, e invoca la función nombrada pasando los argumentos proporcionados.
-
-Cada ejecución de contrato continúa hasta que el contrato se completa con éxito o genera un error (trap). Si la ejecución termina con éxito, todas las entradas del ledger modificadas durante la ejecución se escribirán de nuevo en el ledger atómicamente. Si la ejecución genera un error (trap), todas las entradas modificadas del ledger serán descartadas y el contrato no tendrá efecto en el ledger.
-
-Diversas condiciones en los entornos host o invitado pueden provocar que un contrato genere un error (trap). Por ejemplo, si se llama a una función host con argumentos inválidos, el host generará un error (trap). Del mismo modo, si el contrato ejecuta un bytecode Wasm erróneo como una división por cero o acceso a memoria fuera de límites, la VM Wasm generará un error (trap). Además, si el contrato utiliza más recursos de los que ha pagado su transacción contenedora, el contrato generará un error (trap).
-
-## Monitoreo
-
-Los contratos pueden ser monitoreados de dos maneras principales: observando los eventos emitidos durante su ejecución y examinando las entradas del ledger que escriben.
-
-## Actualizar contratos
-
-Consulta la [página de actualización de contratos](../../../build/guides/conventions/upgrading-contracts.mdx) para más detalles al respecto.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/environment-concepts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/environment-concepts.mdx
deleted file mode 100644
index 4f798c66f7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/environment-concepts.mdx
+++ /dev/null
@@ -1,68 +0,0 @@
----
-sidebar_position: 7
-title: Conceptos del entorno
-description: La interfaz que define los objetos, funciones y datos disponibles para los contratos inteligentes.
----
-
-<head>
-  <title>
-    {`La interfaz que define los objetos, funciones y datos disponibles para los contratos inteligentes.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="La interfaz que define los objetos, funciones y datos disponibles para los contratos inteligentes."
-  />
-  <meta
-    property="og:description"
-    content="Aprende sobre la interfaz de entorno que define los objetos, funciones, fuentes de datos y más que están disponibles en los contratos inteligentes."
-  />
-</head>
-
-El entorno del contrato es una _interfaz_ que define las facilidades -- objetos, funciones, fuentes de datos, etc. -- disponibles para los contratos.
-
-## Host y Guest
-
-Como interfaz, el entorno tiene dos lados, a los que nos referimos como el **entorno host** y el **entorno guest**. El código en el entorno host _implementa_ la interfaz del entorno; el código en el entorno guest _utiliza_ la interfaz del entorno.
-
-El **entorno host** está provisto por un conjunto conocido de crates de Rust, compilados una vez en stellar-core (o el SDK). Múltiples contratos interactúan con el mismo entorno host, y el entorno host tiene acceso a cualquier facilidad de su sistema operativo alojante: archivos, red, memoria, etc.
-
-En contraste, se establece un nuevo **entorno guest** para cada invocación de cada contrato inteligente. Cada contrato ve una única interfaz de entorno, y solo puede llamar a funciones proporcionadas por la interfaz del entorno. En otras palabras, el entorno guest es un sandbox para ejecutar código arbitrario dentro de parámetros seguros.
-
-## WebAssembly (Wasm)
-
-El entorno guest on-chain está aislado dentro de una máquina virtual WebAssembly (Wasm) ("VM"). Esto significa que el código desplegado del contrato se compila a bytecode Wasm en lugar de código máquina nativo. El entorno host incluye un intérprete para la VM, y se instancia una VM de corta duración para cada llamada a un contrato, ejecutando el bytecode de dicho contrato y luego cerrándose.
-
-El uso de una VM ayuda a proporcionar seguridad contra cualquier comportamiento indebido del código guest, tanto para el host como para otros entornos guest, además de garantizar la portabilidad del código guest entre hosts que ejecutan diferentes tipos de hardware.
-
-Cuando desarrollas y pruebas código de contrato fuera de cadena, es posible compilar el código del contrato a código máquina nativo en lugar de bytecode Wasm, y [ejecutar pruebas y depurar contratos](./errors-and-debugging/debugging.mdx) contra una copia local del entorno host enlazando directamente a él, en lugar de ejecutar dentro de una VM. Esta configuración funciona mucho más rápido y proporciona mejor información para depuración, pero solo es posible localmente, fuera de cadena. Los contratos desplegados on-chain son siempre Wasm.
-
-WebAssembly es una VM relativamente de bajo nivel, lo que significa que no proporciona un conjunto muy rico de operaciones estándar o "incorporadas". A diferencia de VMs como la JVM, no tiene recolector de basura (ni siquiera asignador de memoria), ni facilidades de IO, ni estructuras de datos estándar como listas, arreglos, mapas o cadenas, ni conceptos de objetos o tipos salvo los tipos básicos de máquina como enteros de 32 y 64 bits.
-
-Como resultado, los programas compilados a bytecode Wasm a menudo enfrentan un dilema: si quieren funcionalidad estándar rica, a menudo deben incluir una copia de todo el "código soporte" para esa funcionalidad dentro de ellos mismos. Pero si lo hacen, aumentan dramáticamente el tamaño de su código, lo que genera costos y limita el desempeño. Además, incluir tal código soporte limita su capacidad para interoperar con otros programas que pueden incluir código soporte diferente e incompatible.
-
-La solución a este dilema es que el entorno mismo proporcione código soporte para funcionalidad estándar rica, en forma de objetos y funciones host que el código guest puede usar por referencia. Cada contrato se refiere a la misma funcionalidad implementada en el host, asegurando un tamaño de código mucho menor, mayor rendimiento y mejor interoperabilidad entre contratos. Esto es lo que Soroban hace.
-
-## Objetos y funciones host
-
-La funcionalidad estándar compartida, disponible para todo el código guest de contratos, se provee a través de la interfaz del entorno en términos de objetos host y funciones host.
-
-El entorno soporta un pequeño número de tipos de objetos host que cubren estructuras de datos como vectores, mapas, blobs binarios, direcciones, cadenas y enteros grandes. Los objetos host son todos inmutables, se asignan y residen dentro del entorno host, y solo están disponibles en el entorno guest por referencia. El código guest se refiere a objetos host mediante manejadores con valores enteros.
-
-También existe un conjunto un poco mayor de funciones host que actúan sobre objetos host: creándolos, modificándolos, inspeccionándolos y manipulándolos. Algunas funciones host permiten copiar bloques de datos binarios dentro y fuera de la memoria VM del guest, y algunas funciones host realizan operaciones criptográficas sobre objetos host.
-
-También hay funciones host para interactuar con componentes selectos del entorno host más allá del repertorio de objetos host, como leer y escribir entradas del ledger, emitir eventos, llamar a otros contratos y acceder a información sobre el contexto de la transacción en la que se ejecuta el código guest.
-
-### Serialización
-
-Los objetos host pueden ser pasados (por manejador) directamente a rutinas de almacenamiento o entre contratos que colaboran. **No se necesita que exista código de serialización o deserialización en el guest**: el host sabe cómo serializar y deserializar todos sus tipos de objeto y lo hace de forma transparente cuando es necesario.
-
-## Valores y tipos
-
-Todas las funciones host pueden aceptar como argumentos y devolver valores, a lo sumo, del repertorio limitado de tipos máquina del Wasm VM. Para simplificar, Soroban limita aún más todas las funciones host a pasar y devolver valores dentro de una forma especializada de enteros de 64 bits llamada "value" o "el tipo valor". Mediante un empaquetado cuidadoso de bits, el tipo valor puede codificar cualquiera de varios tipos separados que tienen más significado para los usuarios que solo "enteros".
-
-Específicamente, el tipo valor puede codificar directamente enteros pequeños (hasta 56 bits), además de booleanos true y false, enteros firmados o sin signo de 32 bits, manejadores de objetos host tipados, códigos de error tipados, símbolos pequeños (hasta 9 caracteres alfanuméricos latinos), o un valor void único. Los bits individuales en un valor se asignan para etiquetar y alternar entre estos casos dinámicamente, y las funciones u objetos host que requieran casos específicos pueden rechazar valores de otros casos.
-
-Dado que el tipo valor puede contener un manejador a un objeto host, cualquier objeto contenedor que pueda contener el tipo valor en realidad puede contener cualquier objeto. Por lo tanto, los tipos de mapas y vectores host -- estructuras de datos contenedoras -- se definen simplemente como contenedores para el tipo valor, donde el caso específico de cada valor puede variar de contenedor a contenedor o incluso entre los elementos de un contenedor. De esta manera, los tipos contenedores host son más parecidos a los contenedores de lenguajes de tipado dinámico como JavaScript o Python. El SDK también proporciona envoltorios estáticos y uniformemente tipados cuando se desea esto, prohibiendo que se agreguen valores fuera del caso designado al contenedor.
-
-![](/assets/diagrams/environment-concepts.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/README.mdx
deleted file mode 100644
index e2e365a023..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Errores y Depuración
-sidebar_position: 40
----
-
-import DocCardList from "@theme/DocCardList";
-
-Explicaciones detalladas y artículos sobre temas específicos de interés.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx
deleted file mode 100644
index 875ae47b05..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors.mdx
+++ /dev/null
@@ -1,101 +0,0 @@
----
-sidebar_position: 30
-title: Depuración de errores en contratos
-description: Depurar y comprender errores de Soroban mediante el ciclo general de una transacción.
----
-
-Para entender cómo depurar errores de Soroban, primero debemos comprender cómo se asocian los errores con cada paso del flujo de la transacción, así como los errores más probables y comunes en cada paso del flujo de la transacción.
-
-## Flujo general de la transacción
-
-El proceso típico de envío de una transacción puede dividirse en los siguientes pasos secuenciales, excluyendo interacciones externas como las interacciones con carteras. Cada paso tiene su propio conjunto de posibles errores:
-
-1. **Simulación de transacción (opcional):**
-   - **Qué sucede:** Este paso implica ejecutar el punto final RPC [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx). El endpoint ejecuta una transacción en modo "simulación" del host y registra las entradas necesarias del libro mayor, las instrucciones de CPU y las autorizaciones requeridas. El resultado final es similar a ejecutar transacciones en Core con recursos máximos, acceso irrestricto al libro mayor y sin tarifas.
-   - **Fallos comunes:** Los errores suelen implicar superar el límite de la red o problemas de lógica en el contrato.
-
-2. **Core acepta la transacción:**
-   - **Qué sucede:** Core evalúa cada transacción para decidir si aceptarla o rechazarla. Las transacciones rechazadas suelen ser inválidas o tener tarifas insuficientes, especialmente durante períodos de alto tráfico.
-   - **Fallos comunes:** Se rechazan transacciones inválidas, como aquellas con tarifas de recursos incorrectas o valores de recursos demasiado altos, y huellas inválidas. Otros errores comunes incluyen firmas de transacción incorrectas o fondos insuficientes en la cuenta fuente. Las transacciones válidas pueden ser rechazadas solo debido a una tarifa de inclusión baja.
-
-3. **Core incluye la transacción en el libro mayor:**
-   - **Qué sucede:** Las transacciones aceptadas permanecen en la memoria de Core hasta que son incluidas en el libro mayor o eliminadas.
-   - **Fallos comunes:** Las transacciones pueden no ser incluidas en el libro mayor si tienen una tarifa de inclusión baja y necesitan ser eliminadas durante picos de tráfico para dar cabida a más transacciones.
-
-4. **Core aplica la transacción al libro mayor:**
-   - **Qué sucede:** Core ejecuta la transacción incluida.
-   - **Fallos comunes:** Este paso tiene la gama más amplia de errores potenciales. Los fallos pueden incluir acceso a entradas archivadas, agotamiento de recursos, acceso a entradas fuera de la huella especificada o fallos lógicos dentro del contrato.
-
-_Para obtener más información sobre las tarifas, visita [Tarifas, límites de recursos y medición](../../fees-resource-limits-metering.mdx#inclusion-fee)._
-
-## Errores detallados de Soroban
-
-### 1. Simulación de transacción
-
-Los errores aquí son devueltos por el host y se propagan a través del RPC. Esto no cubre otros posibles errores (por ejemplo, errores de red, errores en el RPC mismo, etc.).
-
-| Error                              | Explicación                                                                                                                                                                                                                                                                                                                      | Solución                                                                                                                                                                                                                                                         |
-| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `HostError(Budget, LimitExceeded)` | Se ha superado un límite de recursos definido por la red (ya sea de instrucciones o memoria). Consulta los eventos diagnósticos para verificar cuál límite ha sido superado (el 99% de las veces será el de instrucciones).                                                                                                      | Optimiza el contrato para consumir menos recursos.                                                                                                                                                                                                               |
-| `HostError(Storage, MissingValue)` | Se intenta acceder a una entrada del libro mayor que no existe. El 99.9% de las veces esto significa que el contrato o Wasm no existen en el libro mayor (los casos restantes solo pueden ocurrir si el desarrollador no utiliza el SDK de Soroban para contratos). Los eventos diagnósticos deberían indicar qué entrada falta. | Despliega el contrato o Wasm correspondiente.                                                                                                                                                                                                                    |
-| `HostError(WasmVm, InvalidAction)` | Ha habido un fallo en algún contrato Wasm, típicamente un `panic!()`. Los eventos diagnósticos pueden proporcionar información más detallada, pero no siempre, ya que los mensajes `panic!()` no se incluyen en las compilaciones Wasm.                                                                                          | Corrige la lógica del contrato o los argumentos de invocación. Dado que la razón más común para este error es `panic!()`, podría ser buena idea usar `panic_with_error!()` en lugar de `panic!()` en todas partes. Se recomienda escribir más pruebas unitarias. |
-| `HostError(<some other code>)`     | Un error arbitrario de ejecución, como acceder a un valor fuera de los límites del contenedor, desbordamiento en aritmética i128, tipo de argumento de invocación incorrecto, etc. El código de error debería dar una idea general de qué está fallando, pero consulta los eventos diagnósticos para detalles.                   | Corrige la lógica del contrato o los argumentos de invocación. Se puede hacer una depuración adicional mediante pruebas unitarias.                                                                                                                               |
-
-### 2. Core acepta la transacción
-
-El error es devuelto inmediatamente por Core como respuesta al envío de la transacción y se muestra al usuario a través del RPC. Hay varios campos relacionados con errores en la respuesta de Core:
-
-- `status` contiene uno de los pocos códigos generales: es "ERROR" para cualquier error de validación de transacción, o uno de los pocos estados especiales no relacionados con la validación.
-- `result` contiene el TransactionResult codificado en XDR que, en caso de estado "ERROR", contendrá el código de error a nivel de transacción comenzando con "tx", como `txMALFORMED`.
-- Los errores de transacción `txFAILED` en esta etapa corresponden a los errores de validación específicos de operación, por lo que se debe examinar el código de resultado de la operación.
-- `diagnostics` contendrá información adicional del error en el formato de eventos diagnósticos de Soroban. Esto típicamente se devolverá para errores de transacción `txSOROBAN_INVALID` pero puede ser utilizado más extensivamente en el futuro.
-
-| Error de Core                                                                                                                                              | Explicación                                                                                                                                                                                                                                                                                                                                                                                                   | Solución                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| status: `TRY_AGAIN_LATER`                                                                                                                                  | Ya hay una transacción de la misma cuenta fuente en memoria. La transacción ha sido rechazada por tener una tarifa de inclusión demasiado baja y ha sido reenviada demasiado pronto.                                                                                                                                                                                                                          | Espera a que la transacción anterior se aplique y reenvía, o cambia a cuentas de canal si necesitas mayor rendimiento. Espera más tiempo antes de reenviar la transacción. Construye una transacción dentro de los límites de la red.                                                                                                                                                                                                                              |
-| status: `ERROR`, error: `txMALFORMED`                                                                                                                      | La transacción es fundamentalmente incorrecta: la operación Soroban no es la única operación en la transacción; falta la extensión Soroban; la tarifa o la tarifa por recursos es negativa; la tarifa por recursos es mayor que la tarifa de la tx; los recursos declarados superan los límites de red (ejemplo: quiere usar 200M de instrucciones, mientras el límite general del libro mayor es solo 100M). | Asegúrate de que la transacción esté bien formada y de que la tarifa total de la transacción sea lo suficientemente alta.                                                                                                                                                                                                                                                                                                                                          |
-| status: `ERROR`, error: `txINSUFFICIENT_FEE`                                                                                                               | Probablemente: la tarifa de inclusión es demasiado baja durante un aumento del tráfico. Poco probable: la tarifa de inclusión es menor que el mínimo de la red (es decir, menor a 100 stroops).                                                                                                                                                                                                               | Incrementa la tarifa de la transacción o espera a que haya menos tráfico.                                                                                                                                                                                                                                                                                                                                                                                          |
-| status: `ERROR`, error: `txSOROBAN_INVALID`, diagnostics: “los recursos transaction $RESOURCE_NAME exceden el límite de configuración de la red” o similar | Algún valor de recurso especificado en la transacción supera el límite de la red. Por ejemplo, esto se activaría si la transacción especifica 200M instrucciones, mientras el límite de red es solo 100M. Ten en cuenta que esto no tiene nada que ver con lo que hace la transacción realmente. Solo se examinan las declaraciones de recursos en este punto.                                                | Optimiza el contrato para ajustarlo al límite de recursos y especifica el valor respectivo en la transacción (típicamente ejecutando [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction)). En caso de que exista un 'margen de seguridad' demasiado grande para los recursos (ejemplo: +20% dado que la transacción ya necesita el 90% del límite de la red), reduce la declaración de recursos para ajustarla al límite. |
-| status: `ERROR`, error: `txSOROBAN_INVALID`, diagnostics: mensaje relacionado con la huella                                                                | Hay una serie de requisitos para la huella, como que no debe contener claves duplicadas, ni entradas no soportadas por Soroban, etc. El mensaje diagnóstico especificará los detalles sobre cuál requisito se ha violado.                                                                                                                                                                                     | Corrige la huella. Esto solo debería ocurrir si la huella fue construida o modificada manualmente; las huellas incluidas en la respuesta de [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) siempre deberían pasar todas las verificaciones.                                                                                                                                                                          |
-| status: `ERROR`, error: `txSOROBAN_INVALID`, diagnostics: "transaction sorobanData.resourceFee es menor que la tarifa real del recurso Soroban"            | La tarifa de recurso especificada en la transacción no es suficiente para cubrir los recursos especificados en la transacción. Ten en cuenta que esto no tiene nada que ver con lo que hace la transacción realmente. Solo se examinan las declaraciones de recursos en este punto.                                                                                                                           | Aumenta la tarifa de recurso. Esto normalmente solo ocurre cuando los recursos se calculan o modifican manualmente. [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) siempre calcula la tarifa suficiente para recursos.                                                                                                                                                                                               |
-| status: `ERROR`, error: `txFAILED`, error de operación: `EXTEND_FOOTPRINT_TTL_MALFORMED`                                                                   | Uno de los requisitos de la huella para la operación ExtendFootprintTTL no se ha cumplido: - Solo se pueden ampliar entradas de libro mayor de Soroban. - Solo debe estar poblada la huella de solo lectura. - La extensión TTL no debe ser mayor que la extensión TTL máxima permitida.                                                                                                                      | Asegúrate de que las huellas cumplan con los requisitos. Idealmente, las librerías del lado cliente deberían garantizar que las transacciones de extensión TTL estén bien formadas.                                                                                                                                                                                                                                                                                |
-| status: `ERROR`, error: `txFAILED`, error de operación: `RESTORE_FOOTPRINT_MALFORMED`                                                                      | Uno de los requisitos de la huella para la operación RestoreFootprint no se ha cumplido: Solo se pueden restaurar entradas persistentes de libro mayor Soroban; Solo debe estar poblada la huella de lectura-escritura.                                                                                                                                                                                       | Asegúrate de que las huellas cumplan con los requisitos. Idealmente, las librerías del lado cliente deberían garantizar que las transacciones de restauración estén bien formadas.                                                                                                                                                                                                                                                                                 |
-| status: `ERROR`, error: `tx$CODE`                                                                                                                          | Los códigos de error restantes tienen la misma semántica para Soroban que para Stellar; incluyen errores como saldo insuficiente, número de secuencia incorrecto, etc. Estos errores suelen ser fáciles de interpretar según su nombre.                                                                                                                                                                       | Corrige el problema correspondiente al código. No hay nada específico de Soroban aquí.                                                                                                                                                                                                                                                                                                                                                                             |
-
-### 3. Core incluye la transacción en el libro mayor
-
-Hay casos en los que Core parece no incluir la transacción en el libro mayor. Se recomienda la siguiente mejor práctica:
-
-| Error                                                    | Explicación                                                                                                                                                                                                                                                                                                                                      | Solución                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| La transacción parece estar 'atascada' y nunca se aplica | Aquí no hay un reporte de error directo porque la red no puede comunicar razonablemente qué transacción elimina (Por ejemplo, que el Nodo A haya eliminado la transacción no significa necesariamente que otro Nodo B también la haya eliminado). Al consultar contra un endpoint de datos, la transacción puede ser reportada como 'pendiente'. | Introduce límites de tiempo para la transacción en el lado cliente. Si una transacción no se ha aplicado en 1-2 minutos, es muy poco probable que la red aún la recuerde. _Se recomienda encarecidamente que todas las transacciones incluyan un límite de tiempo o límite de libro mayor._ Tener un límite permite al desarrollador reenviar la transacción después de que se supere el límite de tiempo y opcionalmente aumentar la tarifa si el error persiste. |
-
-:::info
-
-Se recomienda encarecidamente que todas las transacciones incluyan un límite de tiempo o límite de libro mayor.
-
-:::
-
-### 4. Core aplica la transacción al libro mayor
-
-Los errores y eventos diagnósticos se registran en el flujo meta de la transacción emitido por la instancia de Core cuando se cierra el libro mayor. Luego, el RPC ingiere los metadatos de la transacción (tx meta) y permite a los desarrolladores consultar el tx meta.
-
-Cuando ocurre un error, Core almacena algunos campos relacionados con el error en el meta resultado de la transacción:
-
-- El resultado de la transacción (error) será `txFAILED` para fallos relacionados con Soroban (o cualquier fallo de operación en general). A veces es posible obtener otros errores `tx$ERROR` (como `txBAD_AUTH`), pero no están relacionados con Soroban y son más casos extremos.
-- El error de operación será uno de `INVOKE_HOST_FUNCTION_$ERROR`, `RESTORE_FOOTPRINT_$ERROR` y `EXTEND_FOOTPRINT_TTL_$ERROR` (correspondientes a las operaciones InvokeHostFunction, RestoreFootprint y ExtendFootprintTTL). Los errores de operación no son muy granulares, y típicamente se deberían usar eventos diagnósticos para entender el error exacto.
-- Si la instancia Core que produce meta tiene diagnósticos Soroban habilitados (que normalmente debería tener), los meta también contendrán eventos diagnósticos con información de error más detallada.
-- Ten en cuenta que puede haber algunas lagunas en la cobertura de eventos diagnósticos. Dado que esto no es un cambio de protocolo, Core puede añadir más eventos diagnósticos en futuras versiones.
-
-Nota: $OPERATION aquí se refiere a cualquiera de las operaciones Soroban: `INVOKE_HOST_FUNCTION`, `RESTORE_FOOTPRINT` y `EXTEND_FOOTPRINT_TTL`.
-
-| Error y diagnósticos                                                                                                                         | Explicación                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | Solución                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `$OPERATION_RESOURCE_LIMIT_EXCEEDED`, diagnostics: mensaje que especifica qué límite de recurso ha sido superado                             | La transacción ha superado el límite de recursos durante la ejecución. Para la mayoría de recursos (instrucciones, bytes de lectura, bytes de escritura), esto no tiene que ver con el límite general de red; es el límite especificado en la transacción. Por ejemplo, una transacción tiene especificadas 10M instrucciones pero consume al menos 10M + 1 instructión y falla inmediatamente. Los eventos diagnósticos especifican qué límite se ha superado y contienen tanto el límite como el valor que la transacción intentó consumir.                                                                                                                                                                                                          | Si superas el límite especificado en la transacción, aumenta el recurso respectivo declarado en la transacción. Si [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) determinó los límites de recurso, lo más probable es que la razón de superarlos dependa de la lógica respecto al estado volátil del libro mayor (por ejemplo, RNG o secuencia del libro mayor). Asegúrate de que la lógica esté estimada suficientemente por [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction). Si superas los límites de red (tamaño de entrada, memoria), modifica u optimiza el contrato. |
-| `$OPERATION_INSUFFICIENT_REFUNDABLE_FEE`                                                                                                     | La tarifa de recurso reembolsable no fue suficiente para cubrir los recursos reembolsables consumidos, es decir, no suficiente para pagar los eventos emitidos o extensiones TTL.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | La solución más sencilla es aumentar la tarifa de recurso de forma incondicional; las tarifas no gastadas se reembolsan. [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) estima tarifas reembolsables pero no puede predecir el costo real de las extensiones TTL debido a la volatilidad del estado del libro mayor. Por lo tanto, [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) no siempre puede predecir la tarifa que se cobrará realmente.                                                                                                                             |
-| `INVOKE_HOST_FUNCTION_ENTRY_ARCHIVED`                                                                                                        | La transacción intenta acceder a una entrada archivada del libro mayor, por ejemplo, cuando la huella contiene una clave para una entrada persistente archivada de Soroban. Este fallo ocurre antes de que se cree el host de Soroban, por lo que no está relacionado con la lógica del contrato.                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Restaura la entrada archivada utilizando la operación RestoreFootprintOp. [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) normalmente informa entradas archivadas, pero una entrada puede archivarse después de que ocurrió la simulación de la transacción.                                                                                                                                                                                                                                                                                                                                                               |
-| `INVOKE_HOST_FUNCTION_TRAPPED`, diagnostics: HostError(Storage, LimitExceeded).                                                              | La función host intentó acceder a una entrada del libro mayor fuera de la huella. Los eventos diagnósticos especifican la entrada faltante exacta. [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) normalmente debería devolver la huella válida, por lo que si se usa [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction), probablemente: a) el contrato genera claves no deterministas (ej., derivadas de RNG o secuencia del libro mayor), b) el contrato tiene lógica no determinista que resulta en el acceso a un conjunto diferente de entradas (ej., un contrato 'lotería' que transfiere de forma no determinista a la dirección A o a la direccion B). | Si no se usa [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction), corrige el código cliente para construir la huella correcta. Si usas [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction), corrige el contrato o la huella: evita claves no deterministas y añade todas las claves que puedan ser accedidas en cualquier escenario (ej., las entradas de saldo para A y B en el ejemplo del contrato 'lotería').                                                                                                                                                                     |
-| `INVOKE_HOST_FUNCTION_TRAPPED`, diagnostics: HostError(WasmVm, InvalidAction)                                                                | Fallo en un contrato Wasm, típicamente un `panic!()`. Los eventos diagnósticos pueden proporcionar información más detallada, pero no siempre, ya que los mensajes `panic!()` no se incluyen en las compilaciones Wasm.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Corrige la lógica del contrato. Considera usar `panic_with_error!()` y aumentar las ejecuciones de [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) y las pruebas unitarias.                                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| `INVOKE_HOST_FUNCTION_TRAPPED`, diagnostics: HostError(Auth, InvalidAction) "Llamada a función no autorizada para la dirección \<'ADDRESS'>" | La transacción no tenía la carga de autorización necesaria para satisfacer la llamada a la función `require_auth` para una \<’ADDRESS’> dada. Es poco probable que esto ocurra cuando se usa [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction), pero aún es posible si los argumentos de `require_auth` dependen del estado volátil del libro mayor (ej., si `require_auth` contiene el número de secuencia del libro mayor).                                                                                                                                                                                                                                                                               | Adjunta la carga de autorización adecuada a la transacción, usualmente a través de [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction). Asegura que las cargas de autorización sean deterministas y dependan solo de los argumentos de invocación.                                                                                                                                                                                                                                                                                                                                                                             |
-| `INVOKE_HOST_FUNCTION_TRAPPED`, diagnostics: HostError(Auth, \<'error code'>)                                                                | Error de autenticación, como firma faltante/expirada/incorrecta o nonce reutilizado. Estos errores no siempre aparecen en la respuesta de [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) a menos que la carga de autorización firmada completa se use en la solicitud de [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction). Los eventos diagnósticos también tendrán una explicación más detallada del error.                                                                                                                                                                                                                                                 | Corrige la carga de autenticación de acuerdo con el error (ej., usa la firma adecuada, nonce nuevo, etc.). Considera ejecutar [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) con todas las firmas para una depuración más rápida.                                                                                                                                                                                                                                                                                                                                                                                         |
-| `INVOKE_HOST_FUNCTION_TRAPPED`, HostError(\<'some other code'>)                                                                              | Un error arbitrario de ejecución, como acceder a un valor fuera de los límites del contenedor, desbordamiento en aritmética i128, tipo de argumento de invocación incorrecto, etc. El código de error debería proporcionar una idea general de qué está fallando, pero consulta los eventos diagnósticos para más detalles.                                                                                                                                                                                                                                                                                                                                                                                                                            | Corrige la lógica del contrato o los argumentos de invocación. Se puede hacer una depuración adicional con más ejecuciones de [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction) y pruebas unitarias.                                                                                                                                                                                                                                                                                                                                                                                                                         |
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
deleted file mode 100644
index 1d05b7db27..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/debugging.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-sidebar_position: 20
-title: Modos de depuración
-description: Depura contratos inteligentes de forma nativa y como WASM.
----
-
-<head>
-  <title>Depura contratos inteligentes de forma nativa y como WASM.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Depura contratos inteligentes de forma nativa y como WASM."
-  />
-  <meta
-    property="og:description"
-    content="Compila contratos inteligentes de forma nativa para pruebas locales o en WASM para despliegue, a fin de depurar."
-  />
-</head>
-
-Los contratos Soroban son, en la medida de lo posible, programas regulares en Rust y pueden ser depurados usando las mismas herramientas que normalmente usarías.
-
-Las facilidades de depuración disponibles difieren significativamente dependiendo de si un contrato se compila de forma nativa para pruebas locales, o si se compila en WASM para despliegue.
-
-Decidir entre estos dos modos y sacarles el máximo provecho durante la depuración requiere una **comprensión cuidadosa** de qué código está compilado en los contratos desplegados y qué código solo está disponible para pruebas locales.
-
-## Modo de pruebas locales
-
-Es posible (y se recomienda durante el desarrollo) compilar los contratos Soroban **de forma nativa** (p. ej., como código x86-64 o AArch64) y enlazarlos directamente contra el entorno host, de modo que el contrato no sea un invitado corriendo en una máquina virtual WASM en absoluto: es simplemente una biblioteca nativa llamando a otra - su host - y ambos, host y contrato, están enlazados juntos como un solo programa, junto con un arnés de pruebas.
-
-Esta configuración se denomina **"modo de pruebas locales"** y, dado que elimina la máquina virtual WASM de la experiencia de depuración, tiene muchas ventajas:
-
-- Las pruebas se ejecutan mucho más rápido porque no hay una VM interpretándolas y, por defecto, se ejecutan en paralelo en múltiples hilos.
-- Las pruebas pueden usar numerosas técnicas estándar de prueba y depuración:
-  - [El arnés estándar de Rust `#[test]`](https://doc.rust-lang.org/reference/attributes/testing.html), incluyendo soporte en IDE con un botón para ejecutar y volver a ejecutar pruebas individuales.
-  - [Depuradores estándar con soporte en IDE](https://code.visualstudio.com/docs/languages/rust#_debugging), incluido soporte para establecer puntos de interrupción e inspeccionar valores tanto en el contrato como en el host.
-  - Depuración ligera mediante [registro estándar](https://docs.rs/log/latest/log/) o [tracing](https://docs.rs/tracing/latest/tracing/).
-  - Pruebas sistemáticas como [fuzzing](https://crates.io/crates/cargo-fuzz), [pruebas de propiedades](https://crates.io/crates/proptest), o incluso [verificación modelo](https://crates.io/crates/kani-verifier) o [verificación formal](https://github.com/xldenis/creusot).
-  - El enfoque más simple de depuración, [imprimir en la salida de error estándar](https://doc.rust-lang.org/std/macro.eprintln.html).
-
-El modo de pruebas locales es la configuración **predeterminada** cuando se compila código dirigido a la CPU y sistema operativo de tu computadora local, que es lo que cargo hará si configuras un nuevo proyecto Rust y no especificas un destino.
-
-## Modo Wasm
-
-Por otro lado, si deseas compilar para despliegue, debes indicarle a cargo que construya para el target Wasm.
-
-Compilar para Wasm _deshabilitará_ muchas de las facilidades de depuración descritas arriba, típicamente por una de tres razones:
-
-- La VM Wasm simplemente no puede proporcionarlas (o la VM que hemos elegido no lo hace).
-- La VM Wasm _podría_ proporcionarlas, pero hacerlo violaría las restricciones del [dialecto Rust para contratos](../rust-dialect.mdx).
-- La VM Wasm _podría_ proporcionarlas, pero hacerlo haría que el código WASM resultante fuera imprácticamente grande.
-
-Aunque recomendamos que la mayoría de las pruebas ocurran en modo de pruebas locales, algunos problemas surgirán únicamente en despliegue, y algunas facilidades de depuración permanecen disponibles incluso allí:
-
-- Un host "sandbox" con un ledger simulado que puede leer y escribir entradas de ledger `CONTRACT_DATA` en el sistema de archivos local.
-- Un sistema de registro general que permite a los contratos registrar valores del [tipo "value" compartido entre host/invitado](../environment-concepts.mdx), incluso en producción.
-- Códigos `Error` extensibles por el usuario que pueden ser retornados desde cualquier llamada al contrato para indicar problemas.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/errors.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/errors.mdx
deleted file mode 100644
index 7e2963030c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/errors-and-debugging/errors.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-sidebar_position: 10
-title: Generar errores de contrato
-description: Generando errores a partir de contratos inteligentes.
----
-
-<head>
-  <title>Generando errores a partir de contratos inteligentes.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Generando errores a partir de contratos inteligentes." />
-  <meta
-    property="og:description"
-    content="Generando errores a partir de contratos inteligentes."
-  />
-</head>
-
-Hay varias formas de generar errores en los contratos.
-
-Una forma son los tipos enum de error, que son definidos por los contratos y que asignan errores a valores enteros sin signo de 32 bits. Se pueden usar como valores de error en los tipos de retorno de funciones de contrato.
-
-:::info
-
-El [ejemplo de errores] demuestra cómo definir tus propios tipos de error.
-
-:::
-
-[ejemplo de errores]: ../../../../build/smart-contracts/example-contracts/errors.mdx
-
-## Enumeraciones de errores
-
-Los errores son un tipo especial de tipo enum entero que se almacenan en el libro mayor como valores `Error` que contienen un código `u32`.
-
-```rust
-#[contracterror]
-#[derive(Copy, Clone, Debug, Eq, PartialEq, PartialOrd, Ord)]
-#[repr(u32)]
-pub enum Error {
-    AnError = 1,
-}
-```
-
-Cuando se convierten a XDR, el valor se convierte en un `ScVal`, que contiene un `ScError`, que contiene el valor entero del error como error de contrato.
-
-```json
-{ "error": { "contractError": 1 } }
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/events.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/events.mdx
deleted file mode 100644
index 3e2516b71f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/events.mdx
+++ /dev/null
@@ -1,235 +0,0 @@
----
-sidebar_position: 11
-title: Eventos
-description: Monitorea los cambios de contratos inteligentes fuera de cadena.
----
-
-Los eventos son el mecanismo que las aplicaciones fuera de cadena pueden usar para monitorear cambios y eventos en contratos en cadena.
-
-## ¿Cómo se emiten los eventos?
-
-Los `ContractEvents` se emiten en el `TransactionMeta` de Stellar Core. Puedes ver en el XDR [TransactionMetaV3] a continuación que hay una lista de `OperationEvents` llamada `events`. Cada `OperationEvent` corresponde a una operación en una transacción y contiene a su vez una lista de `ContractEvents`. Ten en cuenta que `events` solo se llenarán si la transacción tiene éxito.
-
-[transactionmetav3]: #transactionmetav3
-
-### ContractEvent
-
-Los temas de un evento no tienen que ser del mismo tipo: puedes mezclar diferentes tipos.
-
-Un evento también contiene un objeto de datos de cualquier valor o tipo, incluidos [tipos personalizados](./types/custom-types.mdx) definidos por contratos utilizando `#[contracttype]`:
-
-```cpp
-struct ContractEvent
-{
-    // We can use this to add more fields, or because it
-    // is first, to change ContractEvent into a union.
-    ExtensionPoint ext;
-
-    Hash* contractID;
-    ContractEventType type;
-
-    union switch (int v)
-    {
-    case 0:
-        struct
-        {
-            SCVec topics;
-            SCVal data;
-        } v0;
-    }
-    body;
-};
-```
-
-### OperationEvents
-
-```cpp
-struct OperationEvents
-{
-    ContractEvent events<>;
-};
-```
-
-### TransactionMetaV3
-
-```cpp
-struct TransactionMetaV3
-{
-    LedgerEntryChanges txChangesBefore; // tx level changes before operations
-                                        // are applied if any
-    OperationMeta operations<>;         // meta for each operation
-    LedgerEntryChanges txChangesAfter;  // tx level changes after operations are
-                                        // applied if any
-    OperationEvents events<>;           // custom events populated by the
-                                        // contracts themselves. One list per operation.
-    TransactionResult txResult;
-
-    Hash hashes[3];                     // stores sha256(txChangesBefore, operations, txChangesAfter),
-                                        // sha256(events), and sha256(txResult)
-
-    // Diagnostics events that are not hashed. One list per operation.
-    // This will contain all contract and diagnostic events. Even ones
-    // that were emitted in a failed contract call.
-    OperationDiagnosticEvents diagnosticEvents<>;
-};
-```
-
-[Enlace](https://github.com/stellar/stellar-xdr/blob/eab1622f18b8101aa0cea76361c08beaeaa8d715/Stellar-ledger.x#L444) al XDR anterior.
-
-### Tipos de eventos
-
-Hay tres `ContractEventType` -
-
-1. Los eventos `CONTRACT` son eventos emitidos por contratos que usan la función de host `contract_event` para transmitir cambios de estado.
-2. Los eventos `SYSTEM` son eventos emitidos por el host. Actualmente, solo hay un evento del sistema emitido por el host. Se emite cuando se llama a la función del host `update_current_contract_wasm`, donde `topics = ["executable_update", old_executable: ContractExecutable, old_executable: ContractExecutable]` y `data = []`.
-3. Los eventos `DIAGNOSTIC` están destinados a la depuración y no se emitirán a menos que la instancia del host los habilite explícitamente. Puedes leer más sobre esto a continuación.
-
-## ¿Qué son los diagnosticEvents?
-
-Al observar la estructura XDR `TransactionMetaV3` anterior, puede que hayas notado el campo `diagnosticEvents`. Esta lista estará vacía por defecto a menos que tu instancia de stellar-core tenga `ENABLE_SOROBAN_DIAGNOSTIC_EVENTS=true` en su archivo de configuración. Si los eventos de diagnóstico están habilitados, esta lista no solo incluirá todos los ContractEvents en `events`, sino también eventos de llamadas fallidas a contratos, errores del host, eventos para rastrear la pila de llamadas del contrato y registros de la función del host `log_from_linear_memory`. Estos eventos se pueden identificar porque `type == DIAGNOSTIC`. Los eventos de diagnóstico emitidos por el host para rastrear la pila de llamadas se definen a continuación.
-
-### fn_call
-
-El evento de diagnóstico `fn_call` se emite cuando se llama a un contrato y contiene -
-
-- Temas
-  1. El símbolo "fn_call".
-  2. El id del contrato que está a punto de ser llamado.
-  3. Un símbolo que contiene el nombre de la función que se está llamando.
-- Datos
-  1. Un vector de los argumentos pasados a la función que se está llamando.
-
-### fn_return
-
-El evento de diagnóstico `fn_return` se emite cuando una llamada a contrato finaliza y contiene -
-
-- Temas
-  1. El símbolo "fn_return".
-  2. Un símbolo que contiene el nombre de la función que está a punto de retornar.
-- Datos
-  1. El valor retornado por la función del contrato.
-
-### ¿Cuándo se deben habilitar los eventos de diagnóstico?
-
-Los `events` contienen `ContractEvents` que deberían transmitir información sobre cambios de estado. Los `diagnosticEvents`, por otro lado, contienen eventos que no son útiles para la mayoría de los usuarios, pero pueden ser útiles para depurar problemas o construir la pila de llamadas del contrato. Como no serán utilizados por la mayoría de los usuarios, se pueden habilitar opcionalmente porque no se incluyen en el hash del libro mayor y, por lo tanto, no son parte del protocolo. Esto se hace para que un nodo stellar-core pueda mantenerse sincronizado con la red mientras emite estos eventos que normalmente no serían útiles para la mayoría de los usuarios.
-
-Debido a que un nodo con eventos de diagnóstico habilitados ejecutará caminos de código que divergen de un nodo regular, recomendamos encarecidamente usar esta función solo en un nodo de observación (es decir, nodos donde `NODE_IS_VALIDATOR=false`).
-
-## Leer eventos
-
-Puedes usar el endpoint [`getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents.mdx) de cualquier servicio RPC para obtener y filtrar eventos por tipo, contrato y tema.
-
-:::warning
-
-Los eventos son efímeros: los proveedores RPC normalmente solo conservan fragmentos breves (menos de una semana) del historial.
-
-:::
-
-Para aprender más sobre cómo trabajar con eventos, echa un vistazo a las [guías de eventos](../../../build/guides/events/README.mdx) y [este contrato ejemplo](../../../build/smart-contracts/example-contracts/events.mdx).
-
-Para una demostración rápida y de alto nivel, usaremos el [SDK de TypeScript](../../../tools/sdks/README.mdx) para recuperar infinitamente todos los eventos `transfer` (definidos por la [Interfaz Soroban Token](https://stellar.org/protocol/sep-41#interface)) que involucren el [contrato XLM](https://stellar.expert/explorer/testnet/contract/CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC) y mostrarlos en un formato amigable para humanos.
-
-<CodeExample>
-
-```javascript
-import {
-  humanizeEvents,
-  nativeToScVal,
-  scValToNative,
-  Address,
-  Networks,
-  Asset,
-  xdr,
-} from "@stellar/stellar-sdk";
-import { Server } from "@stellar/stellar-sdk/rpc";
-
-const s = new Server("https://soroban-testnet.stellar.org");
-
-async function main() {
-  const response = await s.getLatestLedger();
-  const xlmFilter = {
-    type: "contract",
-    contractIds: [Asset.native().contractId(Networks.TESTNET)],
-    topics: [
-      // Defined in https://stellar.org/protocol/sep-41#interface
-      // for all compatible transfer events.
-      [
-        nativeToScVal("transfer", { type: "symbol" }).toXDR("base64"),
-        "*", // from anyone
-        "*", // to anyone
-        "*", // any asset (it'll be XLM anyway)
-      ],
-    ],
-  };
-  let page = await s.getEvents({
-    startLedger: response.sequence - 120, // start ~10m in the past
-    filters: [xlmFilter],
-    limit: 10,
-  });
-
-  // Run forever until Ctrl+C'd by user
-  while (true) {
-    if (!page.events.length) {
-      await new Promise((r) => setTimeout(r, 2000));
-    } else {
-      //
-      // Two ways to output a human-friendly version:
-      //  1. the RPC response itself for human-readable text
-      //  2. a helper for the XDR structured-equivalent for human-readable JSON
-      //
-      console.log(cereal(simpleEventLog(page.events)));
-      console.log(cereal(fullEventLog(page.events)));
-    }
-
-    // Fetch the next page until events are exhausted, then wait.
-    page = await s.getEvents({
-      filters: [xlmFilter],
-      cursor: page.cursor,
-      limit: 10,
-    });
-  }
-}
-
-function simpleEventLog(events) {
-  return events.map((event) => {
-    return {
-      topics: event.topic.map((t) => scValToNative(t)),
-      value: scValToNative(event.value),
-    };
-  });
-}
-
-function fullEventLog(events) {
-  return humanizeEvents(
-    events.map((event) => {
-      // rebuild the decomposed response into its original XDR structure
-      return new xdr.ContractEvent({
-        contractId: event.contractId.address().toBuffer(),
-        type: xdr.ContractEventType.contract(), // since we filtered on 'contract'
-        body: new xdr.ContractEventBody(
-          0,
-          new xdr.ContractEventV0({
-            topics: event.topic,
-            data: event.value,
-          }),
-        ),
-      });
-    }),
-  );
-}
-
-// A custom JSONification method to handle bigints.
-function cereal(data) {
-  return JSON.stringify(
-    data,
-    (k, v) => (typeof v === "bigint" ? v.toString() : v),
-    2,
-  );
-}
-
-main().catch((e) => console.error(e));
-```
-
-</CodeExample>
-
-También puedes aprovechar los [formatos alternativos de codificación XDR](../../../data/apis/rpc/api-reference/structure/data-format) del RPC, como JSON, para ver eventos legibles para humanos directamente desde la línea de comandos, por ejemplo, pasando `xdrFormat: "json"` como parámetro adicional al [ejemplo](../../../data/apis/rpc/api-reference/methods/getEvents#examples) de `getEvents`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/overview.mdx
deleted file mode 100644
index 7a87de339f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/overview.mdx
+++ /dev/null
@@ -1,131 +0,0 @@
----
-sidebar_position: 5
-title: Resumen
----
-
-Esta sección ofrece una visión general de los contratos Stellar, describiendo sus conceptos clave sobre contratos inteligentes en la red Stellar.
-
-Aprende a escribir tu primer contrato inteligente Stellar en la [Guía para comenzar](../../../build/smart-contracts/getting-started/setup.mdx).
-
-## Contrato inteligente en WebAssembly (Wasm)
-
-Un contrato inteligente en Stellar es un conjunto programable de binarios ejecutables en WebAssembly (Wasm). WebAssembly (Wasm) es un formato de instrucción binaria ligero y portátil diseñado para ejecución de alto rendimiento en diversos entornos, incluyendo blockchains, navegadores web y servicios en la nube. En Stellar, Wasm funciona como la base para los contratos inteligentes al proporcionar un entorno de ejecución seguro y eficiente.
-
-- **Compilación**: Una vez que el contrato inteligente está escrito en un lenguaje soportado, como Rust, se compila en un archivo ejecutable Wasm. Este archivo contiene un bytecode de bajo nivel que puede ejecutarse eficientemente dentro de un entorno aislado.
-- **Carga y almacenamiento**: Tras la compilación, el ejecutable Wasm se carga primero en la red Stellar, donde se almacena en una entrada de libro mayor `CONTRACT_DATA`. La entrada de libro mayor `CONTRACT_DATA` se crea para almacenar los datos binarios Wasm.
-- **Se crea un hash único**: Un identificador único para esta entrada `CONTRACT_DATA` es el hash del archivo ejecutable, llamado `Wasm hash`. Cabe señalar que este ejecutable binario se almacena de forma independiente de su contrato(s) desplegado(s).
-- **Múltiples instancias de contratos**: Se pueden desplegar múltiples instancias de contratos que referencian el mismo bytecode Wasm, con cada instancia manteniendo su propio almacenamiento, estado y configuraciones del contrato.
-
-## Instancias de contrato
-
-Después de que el bytecode ejecutable se carga en la cadena, se pueden desplegar instancias de contratos que referencian ese mismo bytecode. **Un ejecutable Wasm de contrato puede tener una relación uno a muchos con sus instancias de contrato que funcionan de manera independiente.** Esto significa que el mismo código ejecutable puede usarse en múltiples instancias de contrato que se comportan de manera idéntica debido al código compartido, mientras mantienen datos de estado separados y distintos porque los datos están vinculados a la instancia del contrato. Una instancia de contrato se almacena como su propia entrada en el libro mayor, y cualquier almacenamiento de la instancia del contrato se guarda en esa misma entrada junto con la instancia del contrato. Por lo tanto, los datos almacenados en el almacenamiento de la instancia del contrato tienen un TTL igual al de la propia instancia del contrato. Si un contrato está activo y no ha expirado, el almacenamiento de la instancia también estará garantizado.
-
-```mermaid
-flowchart LR
-    A[my instance] & B[your instance]--> C[contract Wasm]
-```
-
-:::info Conclusión importante
-
-El bytecode Wasm se almacena por separado de las instancias del contrato desplegado. Esta separación permite que múltiples instancias de contrato referencien el mismo ejecutable Wasm mientras mantienen su propio almacenamiento, estado y configuraciones del contrato.
-
-:::
-
-## Almacenamiento del contrato
-
-Adicionalmente a las entradas del libro mayor creadas durante el proceso de carga/despliegue del contrato, cada contrato puede crear y acceder a su propio conjunto de entradas del libro mayor. Estas entradas del libro mayor (así como el código del contrato y las entradas de la instancia del contrato) están sujetas a los períodos de [archivado de estado](./storage/state-archival.mdx), o comportamiento TTL (tiempo de vida). Cada tipo de almacenamiento tiene estructuras de tarifas distintas, comportamiento TTL (tiempo de vida) y está diseñado para almacenar tipos específicos de datos. Usar el almacenamiento incorrecto puede llevar a errores lógicos en tu aplicación, además de impactar en los costos.
-
-| **Atributo**     | **Almacenamiento temporal**                                                                                                                   | **Almacenamiento persistente**                                                                                             | **Almacenamiento de instancia**                                                                                                   |
-| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| **Tarifas**      | El más barato                                                                                                                                 | El más caro (igual que Instancia)                                                                                          | El más caro (igual que Persistente)                                                                                               |
-| **Persistencia** | Eliminado permanentemente cuando se alcanza el TTL del libro mayor                                                                            | Puede archivarse aunque la instancia del contrato esté activa. La vida útil es independiente de la instancia del contrato. | Comparte la vida útil de la instancia del contrato. Datos accesibles si no se alcanza el TTL de la instancia.                     |
-| **Recuperación** | No puede restaurarse                                                                                                                          | `RestoreFootprintOp`                                                                                                       | `extendFootprintTTLOp`                                                                                                            |
-| **Capacidad**    | Ilimitada                                                                                                                                     | Ilimitado                                                                                                                  | Limitada                                                                                                                          |
-| **Casos de uso** | Datos acotados en el tiempo o fácilmente recreables (por ejemplo, precios de oráculos, firmas). No adecuado para verificaciones de corrección | Datos de usuario a largo plazo que deben persistir más allá del TTL (por ejemplo, balances)                                | Estado compartido del contrato ligado a la instancia del contrato (por ejemplo, cuentas de administrador, metadatos del contrato) |
-
-## Invocar contratos
-
-Ahora que aprendiste los conceptos básicos de un contrato Stellar, comprendamos algunos conceptos sobre la invocación de contratos. Cuando una transacción intenta invocar una función del contrato, primero se recupera el bytecode Wasm del libro mayor y se instancia una máquina virtual ("VM") segura y aislada para ejecutar el bytecode del contrato y luego salir. Este enfoque ofrece varias ventajas, incluida la seguridad, ya que la máquina virtual (VM) opera en un entorno aislado y proporciona ejecución determinista.
-
-Para probar la invocación de contratos en Testnet, visita el [explorador de contratos de Stellar Lab](https://lab.stellar.org/smart-contracts/contract-explorer?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&smartContracts$explorer$contractId=CB2RXGQVNGOMHW3XYCPKREXHD45M4DMJ2PTBETV6P3EMV22QLJFUQHWB;;).
-
-## Información del contrato
-
-El Wasm de un contrato Stellar contiene secciones personalizadas dedicadas. Proporcionan metadatos útiles que las implementaciones pueden usar para mejorar la experiencia del usuario.
-
-- Meta del entorno
-- Meta del contrato
-- Especificación del contrato
-
-![Contract Info Meta](/assets/contract/contract-info-meta.png) ![Contract Info Spec](/assets/contract/contract-info-spec.png)
-
-_Explora la información del contrato en el [Explorador de Contratos de Stellar Lab](https://lab.stellar.org/smart-contracts/contract-explorer)._
-
-### Meta del entorno
-
-Los contratos deben contener una sección personalizada Wasm llamada `contractenvmetav0` que incluya una `SCEnvMetaEntry` serializada. La versión de interfaz almacenada debe coincidir con la versión de las funciones host soportadas. Para referencia, consulta [CAP-46-1 Env Meta](https://github.com/stellar/stellar-protocol/blob/603a55b018a8ce12ac16aa8621d189d5b78d0d02/core/cap-0046-01.md?plain=1#L508).
-
-Para ver la Meta del Entorno, considera usar el Explorador de Contratos de Stellar Lab o el comando de Stellar CLI `stellar contract info env-meta --contract-id <contract-id>`.
-
-### Meta del contrato
-
-Los contratos pueden incluir opcionalmente una sección personalizada Wasm llamada `contractmetav0`, que contiene un `SCMetaEntry` serializado. Esta sección no es utilizada por la red, pero permite que los contratos incluyan metadatos arbitrarios, incluyendo nombre del contrato, versión, autor, interfaces soportadas, repositorio fuente o dominio principal. Aplicaciones y herramientas pueden leer estos metadatos para ofrecer experiencias de desarrollo más ricas, mejor indexación o mayor descubrimiento de contratos. Para referencia, consulta [SEP-46 Contract Meta](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0046.md).
-
-Para añadir metadatos a la Meta del Contrato, utiliza el comando Stellar CLI `stellar contract build --meta <meta>`, o usa el SDK de Rust (por ejemplo, `contractmeta!(key="name", val="Defi Swap Contract")`).
-
-Para ver la Meta del Contrato, usa el Explorador de Contratos de Stellar Lab o el comando Stellar CLI `stellar contract info meta --contract-id <contract-id>`.
-
-### Especificación del contrato
-
-Los contratos deben contener una sección personalizada Wasm llamada `contractspecv0` que incluya una secuencia serializada de [`SCSpecEntry`]. Debe haber un [`SCSpecEntry`] por cada función, estructura y unión exportada por el contrato. Para referencia, consulta [SEP-48 Contract Interface Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0048.md).
-
-Una especificación de contrato es comparable a una ABI (Interfaz Binaria de Aplicación) en Ethereum. Es una descripción estandarizada de la interfaz de un contrato inteligente, típicamente en formato JSON o XDR. Define las funciones del contrato, estructuras de datos, eventos y errores de manera que aplicaciones externas puedan entender y usar.
-
-Cuando compilas un contrato inteligente usando el SDK de Rust, el archivo Wasm resultante incluye una sección especial que contiene una descripción completa de los tipos de interfaz del contrato. Esto se conoce comúnmente como la `spec` del contrato o "especificación de contrato". La especificación del contrato Stellar, conocida como `contract spec`, es un elemento fundamental para interactuar con contratos y crear dApps en la red Stellar. La especificación del contrato proporciona definiciones sólidas y completamente tipadas para interactuar con contratos inteligentes, ofreciendo funcionalidad equivalente a la ABI de Ethereum, abordando sus limitaciones.
-
-La especificación del contrato sirve como una interfaz estandarizada para interactuar con contratos inteligentes Stellar. Similar a las ABIs de Ethereum, pero con ventajas clave:
-
-- Disponibilidad en cadena: Cada especificación de contrato está almacenada en cadena
-- Comentarios de desarrollador: Se preservan los comentarios del autor del contrato
-- Comunicación fluida entre contratos y aplicaciones externas
-- Compatibilidad con el ecosistema completo en herramientas como wallets, exploradores y SDKs
-
-Esta estandarización simplifica las integraciones y acelera el proceso de desarrollo.
-
-#### Definiciones de contrato completamente tipadas
-
-La especificación del contrato garantiza definiciones completamente tipadas para todas las funciones del contrato, entradas y salidas. Esto asegura que:
-
-- Los desarrolladores pueden definir el comportamiento del contrato explícitamente, reduciendo ambigüedad.
-- Se minimizan incompatibilidades de tipos y errores en tiempo de ejecución, dando como resultado contratos inteligentes más confiables.
-- Las herramientas pueden ofrecer sugerencias y validaciones inteligentes durante el desarrollo.
-
-Al incorporar seguridad de tipos a nivel de protocolo, la especificación del contrato de Stellar crea un entorno de desarrollo más predecible y robusto.
-
-#### Comparación con ABI de Ethereum
-
-La especificación del contrato de Stellar comparte muchas similitudes con la ABI de Ethereum pero también introduce mejoras:
-
-| Característica                    | ABI de Ethereum       | Especificación del contrato Stellar       |
-| --------------------------------- | --------------------- | ----------------------------------------- |
-| Contratos completamente tipados   | Parcial               | Sí                                        |
-| Decodificación y validación       | Manual o externa      | Incorporada                               |
-| Enfoque de seguridad              | Moderado              | Alto (seguridad de tipos aplicada)        |
-
-#### Generación de especificaciones de contrato
-
-[El Stellar CLI](https://github.com/stellar/stellar-cli) proporciona un comando para generar una especificación de contrato a partir del código fuente de un contrato. Este proceso es sencillo pero requiere que tengas el binario Wasm del contrato.
-
-A veces, puede que no tengas acceso al código fuente del contrato o la capacidad de compilarlo. En tales casos, debes usar el comando [`stellar contract fetch`](../../../tools/cli/stellar-cli.mdx#stellar-contract-fetch) para descargar el binario Wasm del contrato y generar la especificación.
-
-Finalmente, usamos el comando [`stellar bindings`](../../../tools/cli/stellar-cli.mdx#stellar-contract-bindings-json) para generar la especificación del contrato a partir del binario Wasm.
-
-El Stellar Lab ofrece un [Explorador de Contratos](https://lab.stellar.org/smart-contracts/contract-explorer) que también permite ver y descargar la especificación del contrato.
-
-:::note
-
-Habiendo leído la introducción a un contrato Stellar, intentemos escribir un contrato inteligente siguiendo la [Guía para comenzar](../../../build/smart-contracts/getting-started/README.mdx).
-
-:::
-
-[`scspecentry`]: https://github.com/stellar/stellar-xdr/blob/next/Stellar-contract-spec.x
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/rust-dialect.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/rust-dialect.mdx
deleted file mode 100644
index cf6abbef5f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/rust-dialect.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
----
-sidebar_position: 6
-title: Dialecto Rust para Contratos
-description: Diferencias entre Soroban Rust y la programación típica en Rust.
----
-
-El desarrollo de contratos se realiza en el lenguaje de programación Rust, pero varias características del lenguaje Rust no están disponibles en el entorno huésped de despliegue, o no se recomiendan porque su uso implicaría costos inaceptables en tiempo de ejecución.
-
-Por esta razón, tiene sentido considerar el código escrito para contratos como un _dialecto_ o variante especial del lenguaje de programación Rust, con ciertas restricciones y prioridades inusuales, como el determinismo y el tamaño del código.
-
-Estas restricciones y prioridades son _similares_ a las que se encuentran al escribir código Rust para "sistemas embebidos", y las herramientas, bibliotecas y técnicas usadas en el "dialecto de contratos" a menudo se toman prestadas de la [comunidad Rust de sistemas embebidos](https://docs.rust-embedded.org/book/index.html), y por defecto se recomienda construir contratos con el modo [`#[no_std]`](https://docs.rust-embedded.org/book/intro/no-std.html) que excluye completamente la biblioteca estándar de Rust, confiando en la biblioteca subyacente más pequeña `core`.
-
-Nota: estas restricciones y prioridades **no se aplican cuando se compila en modo de pruebas locales**, y de hecho las pruebas locales de contratos _frecuentemente_ usan facilidades —para generar entradas de prueba, inspeccionar salidas de prueba y guiar la prueba— que no son compatibles en el entorno huésped de despliegue. Los desarrolladores **deben entender** la diferencia entre código que se compila en módulos Wasm para despliegue y código que se compila condicionalmente para pruebas. Consulta [depuración de contratos](./errors-and-debugging/debugging.mdx) para más detalles.
-
-El "dialecto de contratos" tiene las siguientes características:
-
-## No hay punto flotante
-
-La aritmética de punto flotante en el huésped está completamente prohibida. Las operaciones de punto flotante en Wasm tienen algunos aspectos no deterministas o específicos de plataforma: principalmente patrones de bits NaN, así como configuraciones del entorno de punto flotante como el modo de redondeo.
-
-Aunque teóricamente es posible forzar que todo el código de punto flotante tenga un comportamiento determinista en todas las implementaciones de Wasm, hacerlo en algunas implementaciones de Wasm puede ser difícil, costoso o propenso a errores. Para evitar esta complejidad, todo código de punto flotante es rechazado en tiempo de instancia.
-
-Esta restricción podría revisarse en una versión futura.
-
-## Asignación dinámica de memoria limitada (idealmente cero)
-
-La asignación dinámica de memoria dentro del huésped está **fuertemente** desaconsejada, pero no completamente prohibida.
-
-El objeto huésped y el repertorio de funciones huésped están diseñados para liberar al huésped de tener que realizar asignación dinámica dentro de su propia memoria lineal; en cambio, se espera e intenta que el huésped asigne estructuras dinámicas _dentro de objetos huésped_ e interactúe con ellos usando manejadores ligeros.
-
-Usar objetos huésped en lugar de estructuras de datos en la memoria huésped trae numerosos beneficios: mucho mayor rendimiento, tamaño de código mucho más pequeño, interoperabilidad entre contratos, soporte compartido del huésped para serialización, depuración e introspección de estructuras de datos.
-
-Sin embargo, el huésped dispone de una pequeña memoria lineal en casos donde la asignación dinámica de memoria sea necesaria. Usar esta memoria conlleva costes: el huésped debe incluir en su código una copia completa de un asignador de memoria y debe pagar el costo de tiempo de ejecución de ejecutar el código del asignador dentro de la máquina virtual.
-
-Esta restricción se debe a la limitada capacidad de Wasm para soportar compartir código: no existe una forma estándar para que la caja de arena Wasm proporcione código compartido de "biblioteca estándar" dentro de un huésped, como un asignador de memoria, ni el huésped tiene suficiente información sobre el contenido de la memoria del huésped para proporcionar un asignador él mismo. Por lo tanto, cada contrato que desee usar asignación dinámica debe llevar su propia copia de un asignador.
-
-Muchos casos donde parecería requerirse asignación dinámica de memoria también pueden atenderse igual de bien con una biblioteca como [heapless](https://docs.rs/heapless/latest/heapless/). Esta biblioteca (y otras semejantes) ofrecen estructuras de datos con APIs familiares que _parecen_ dinámicas, pero en realidad se implementan en términos de una única asignación en pila o estática, con un tamaño máximo fijo establecido en la construcción: intentos de crecer más allá del tamaño máximo simplemente fallan. En el contexto de un contrato, este comportamiento a veces puede ser preferible y evita por completo la cuestión de la asignación dinámica.
-
-## Entrada/salida no estándar
-
-Se prohíben todas las facilidades estándar de entrada/salida y el acceso al sistema operativo que un programa típico de Rust esperaría realizar usando la biblioteca estándar de Rust; los programas que intenten importar tales funciones del huésped a través de (por ejemplo) la interfaz WASI fallarán en la instancia, ya que se refieren a funciones no proporcionadas por el huésped.
-
-No hay sistema operativo, ni ninguna simulación del mismo, presente en la caja de arena del contrato. De nuevo, el repertorio de objetos huésped y funciones huésped está destinado a reemplazar y en gran parte obviar la necesidad de tales facilidades de la biblioteca estándar.
-
-Esta restricción surge del hecho de que los contratos necesitan ejecutarse con garantías más sólidas que las que proporcionan las APIs típicas de sistemas operativos. Específicamente, los contratos deben realizar entrada/salida con semánticas transaccionales de todo o nada (relativas a la ejecución exitosa o fallo) así como consistencia serializable. Esto elimina la mayoría de las APIs relacionadas con la entrada/salida típica de archivos. Además, los contratos deben estar aislados de todas las fuentes de no determinismo, como redes o control de procesos, lo que elimina la mayoría de APIs restantes. Una vez que se eliminan los archivos, la red y el control de procesos, simplemente no queda suficiente en las facilidades de E/S del sistema operativo estándar para intentar proveerlas.
-
-## Sin multihilo
-
-No está disponible el multihilo. Al igual que con las funciones de entrada/salida, intentar importar cualquier API relacionada con multihilo del huésped fallará en el tiempo de instancia.
-
-Esta restricción se basa igualmente en la necesidad de ejecutar contratos en un entorno con fuertes garantías de determinismo y consistencia serializable.
-
-## Pánico inmediato
-
-La función `panic!()` de Rust para errores irrecuperables hará que la máquina virtual Wasm se detenga inmediatamente, parando la ejecución en la instrucción que provoca el trap en lugar de hacer un desenvuelto de pila. Esto significa que el código `Drop` en tipos Rust no se ejecutará durante un pánico. Este comportamiento es similar al perfil `panic = "abort"` con el que el código Rust puede (y a menudo es) compilado.
-
-Esta no es una restricción estricta impuesta por el huésped, sino una configuración suave establecida mediante una mezcla de funciones del SDK y flags usados al compilar, en interés de minimizar el tamaño del código y limitar los costes de ejecución. Se puede eludir con cierto esfuerzo si se desea código de desenvuelto y `Drop`, a costa de un tamaño de código muy aumentado.
-
-## Colecciones puramente funcionales
-
-Los objetos huésped tienen una semántica significativamente diferente a las estructuras de datos típicas de Rust, especialmente aquellas que implementan _colecciones_ como mapas y vectores.
-
-En particular: los objetos huésped son **inmutables**, y cualquier "modificación" a un objeto huésped devuelve una **copia nueva completa** del objeto, dejando el inicial sin cambios. En gran medida, esta distinción está oculta mediante envoltorios en el SDK, de modo que objetos como `Map` o `Vec` parecen para el programador de contratos valores mutables de propiedad única similares a los tipos de la biblioteca estándar de Rust, pero los objetos huésped subyacentes son inmutables, por lo que tienen características de rendimiento diferentes. Específicamente: clonar un objeto así es O(1), mientras cualquier modificación es O(N). Dado que la mayoría de los objetos huésped suelen ser muy pequeños, el coste O(N) de la modificación típicamente es más barato que cualquier implementación alternativa que implique subestructuras compartidas.
-
-:::note
-
-Estos tipos de contenedores `Vec` y `Map` no deberían usarse para gestionar colecciones grandes o ilimitadas de datos. Para esos casos, los contratos deben almacenar datos en múltiples entradas separadas del libro mayor, cada una con su propia clave única definida por el contrato. Hacerlo también limita el costo de E/S de un contrato solo a las entradas que accede, y además permite la modificación concurrente de entradas con claves separadas desde transacciones separadas.
-
-:::
-
-## Funciones limitadas de WebAssembly
-
-La especificación de WebAssembly ha crecido significativamente desde su introducción inicial y ahora admite muchas _funciones_ que pueden o no estar disponibles en una implementación determinada de WebAssembly.
-
-Soroban limita intencionadamente las funciones de WebAssembly que admite, para minimizar la superficie crítica de seguridad y mantener la flexibilidad en la elección de implementaciones de WebAssembly. A partir de Rust 1.84, se añadió un nuevo objetivo `wasm32v1-none` a Rust que se restringe intencionadamente al subconjunto "WebAssembly 1.0" de funciones, todas las cuales Soroban admite.
-
-Los nuevos contratos Soroban deben ser desarrollados con Rust `v1.84.0` o posterior, y usar el objetivo `wasm32v1-none`.
-
-:::note
-
-El objetivo `wasm32v1-none` no incluye, por defecto, ninguna versión de la librería `std`. Al añadir el objetivo `wasm32v1-none`, se decidió que ese tipo de simulacros no ofrecían beneficio alguno a los usuarios.
-
-El objetivo `wasm32v1-none` _sí_ incluye una copia del paquete `alloc`, que contiene la mayoría de los _contenedores_ (como vectores y mapas) que son reexportados por `std`. Por ejemplo, en lugar de usar `std::vec::Vec` se puede usar `alloc::vec::Vec`, que es el mismo código con un nombre diferente. Pero como se mencionó antes en la sección sobre asignación dinámica de memoria, generalmente los contratos Soroban deberían evitar también `alloc`: un paquete como `heapless` usualmente tendrá mejor desempeño.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/README.mdx
deleted file mode 100644
index 87217a0ffd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Almacenamiento
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/persisting-data.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/persisting-data.mdx
deleted file mode 100644
index 12d50b7aca..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/persisting-data.mdx
+++ /dev/null
@@ -1,98 +0,0 @@
----
-sidebar_position: 10
-title: Persistir datos
-description: Almacenar y acceder a datos de contratos inteligentes.
----
-
-<head>
-  <title>Almacenar y acceder a datos de contratos inteligentes.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Almacenar y acceder a datos de contratos inteligentes." />
-  <meta
-    property="og:description"
-    content="Almacenar y acceder a datos de contratos inteligentes."
-  />
-</head>
-
-## Entradas del ledger
-
-Los contratos pueden acceder a las entradas del ledger del tipo `CONTRACT_DATA`. Se proporcionan funciones del host para sondear, leer, escribir y eliminar entradas del ledger de tipo `CONTRACT_DATA`.
-
-Cada entrada del ledger `CONTRACT_DATA` está identificada en el ledger por el ID del contrato que la posee, su tipo de almacenamiento (`Persistent`, `Temporary`, `Instance`) y un único valor elegido por el usuario, de tipo valor estándar. Esto significa que la clave elegida por el usuario puede ser un valor simple como un símbolo, número o bloque binario, o un valor estructurado más complejo como un vector o mapa con múltiples subvalores.
-
-Cada entrada del ledger `CONTRACT_DATA` también contiene (además de su clave) un único valor asociado con la clave. De nuevo, este valor puede ser simple como un símbolo o número, o complejo como un vector o mapa con muchos subvalores.
-
-No se requiere serialización ni deserialización en el código del contrato al acceder a entradas del ledger `CONTRACT_DATA`: el host serializa y deserializa automáticamente cualquier entrada del ledger accedida, intercambiándolas con el contrato como valores deserializados. Si un contrato desea usar un formato de serialización personalizado, puede almacenar una entrada del ledger `CONTRACT_DATA` con valor binario y proporcionar su propio código para serializar y deserializar, pero Soroban está diseñado para minimizar la necesidad de que los contratos hagan esto.
-
-## Control de acceso
-
-Los contratos sólo pueden leer y escribir entradas del ledger `CONTRACT_DATA` que sean propiedad del contrato: aquellas con el mismo ID de contrato que realiza la lectura o escritura. Intentar acceder a otras entradas del ledger `CONTRACT_DATA` causará que la transacción falle.
-
-No hay control de acceso para las operaciones de extensión TTL. Cualquier usuario puede invocar `ExtendFootprintTTLOp` en cualquier LedgerEntry.
-
-## Granularidad
-
-Una entrada del ledger `CONTRACT_DATA` se lee o escribe en su totalidad; no hay manera de leer o escribir "solo una parte" de una entrada `CONTRACT_DATA`. También existe un costo fijo para acceder a cualquier entrada del ledger `CONTRACT_DATA`. Por lo tanto, los contratos son responsables de dividir estructuras de datos "grandes" lógicamente en "piezas" con una granuralidad apropiada para la lectura y escritura. Si las piezas son demasiado grandes, se pagarán costos innecesarios por leer y escribir datos sin usar, así como contención innecesaria en la ejecución paralela; si son demasiado pequeñas, habrá costos innecesarios por la carga fija de cada entrada.
-
-## Huellas y contención paralela
-
-Los contratos sólo pueden acceder a las entradas del ledger especificadas en la huella de su transacción. Las transacciones con huellas superpuestas se dicen que compiten, y sólo se ejecutarán secuencialmente entre sí, en un solo hilo. Las transacciones con huellas no superpuestas pueden ejecutarse en paralelo. Esto significa que una granularidad más fina de las entradas del ledger `CONTRACT_DATA` puede reducir la contención artificial entre transacciones que usan un contrato y aumentar el paralelismo.
-
-## Buenas prácticas para datos de contrato
-
-### Estado de cuenta vs. estado compartido
-
-Aunque no existe distinción entre estado "de cuenta" y estado "compartido" a nivel de protocolo, puede ser útil pensar en los datos en estos términos al decidir qué tipo de almacenamiento y estrategia de extensión TTL usar para un caso concreto. Como guía, el estado de cuenta y el estado compartido se pueden describir así:
-
-- La mayoría del estado del contrato puede estar asociado a una cuenta específica o compartido entre múltiples personas interesadas (“bien público”).
-  - Estado específico de cuenta
-    - Saldos, posiciones, asignaciones, etc.
-  - Estado compartido
-    - Entrada de administrador, valores del pool, etc.
-- Hay dos subcategorías de estado compartido
-  - Estado "global" compartido por todos los usuarios del contrato
-    - Instancia de contrato, wasm del contrato o un administrador global
-  - Estado compartido solo por un subconjunto específico de usuarios
-    - Valores del pool AMM en un contrato monolítico AMM (estilo Uniswap V4)
-- Nota: A veces el estado de cuenta y el estado compartido pueden fusionarse cuando el ámbito del contrato es pequeño
-  - Es decir, una cuenta de contrato o un solo NFT, donde se genera una nueva instancia de contrato para cada cuenta
-
-### Contratos propiedad vs. contratos autónomos
-
-Además de los tipos de estado, también es útil considerar el tipo de instancia de contrato que se está usando. De nuevo, estos tipos no están impuestos a nivel de protocolo, pero pueden ser útiles.
-
-- Contratos propiedad
-  - Instancias de contratos que tienen un propietario claro
-    - Una cuenta de contrato o un solo NFT, donde se genera una nueva instancia de contrato para cada cuenta
-    - Activos respaldados por reservas personalizadas (USDC, etc.)
-- Contratos autónomos
-  - Instancias de contratos que no tienen un propietario claro o tienen un grupo descentralizado de propietarios
-    - La mayoría de los protocolos DeFi, especialmente los no actualizables
-
-### Buenas prácticas
-
-- Preferir almacenamiento `Temporary` sobre `Persistent` e `Instance`
-  - Cualquier cosa que pueda tener un tiempo de espera debería ser `Temporary` con TTL configurado al tiempo de espera. Consulta la [tabla de límites de recursos](../../../../networks/resource-limits-fees.mdx) para el TTL/tiempo de espera máximo actual.
-  - Idealmente, las entradas `Temporary` deberían estar asociadas a un límite absoluto del ledger y por lo tanto no necesitar nunca una extensión TTL
-    - Ejemplo: las firmas Soroban Auth tienen un ledger de expiración absoluta, por lo que los nonces pueden almacenarse en entradas `Temporary` sin riesgos de seguridad
-    - Ejemplo: asignación SAC que solo vive hasta un ledger dado (para que una firma de asignación antigua no pueda usarse en el futuro si no se agota)
-- Todo el estado global que no pueda ser `Temporary` debería estar en almacenamiento `Instance`.
-  - Esto garantiza que el TTL de la instancia del contrato y todos los globals relevantes estén vinculados.
-  - Como se usa frecuentemente el estado global, esto asegura que el estado global nunca necesitará ser restaurado, conduciendo a invocaciones de contrato más baratas y eficientes.
-- Los contratos autónomos deberían extender el TTL de cualquier estado compartido tocado por una invocación vía la función host `extend_ttl()`.
-  - Dado que estos contratos no tienen propietarios, dejar las extensiones TTL a clientes benevolentes podría llevar a una situación de “tragedia de los comunes”.
-  - La mayoría de usuarios no extienden el TTL porque no es necesario, pero aún se benefician del cliente benevolente que sí extiende el TTL.
-- Los propietarios de contratos propiedad deberían subsidiar las tarifas de extensión de TTL del estado compartido enviando manualmente operaciones de extensión.
-  - Los propietarios deberían llevar un control de los TTLs para todo el estado compartido.
-  - Esto se podría implementar con algo como un trabajo cron donde se envíe periódicamente una `ExtendFootprintTTLOp` para todo el estado compartido relevante (por ejemplo, una vez al mes).
-  - Alternativamente, esto también se podría implementar mediante una función administrativa en un contrato inteligente llamada rutinariamente por el propietario.
-- Los clientes (carteras/Dapps) deberían identificar el estado que corresponde a su cuenta respectiva, presentar información de TTL a los usuarios y sugerir extensiones de TTL cuando sea necesario.
-- Nunca se debería depender de las extensiones TTL para funcionalidades o seguridad.
-  - Ejemplo inseguro: una entrada debe ser permanente, pero en lugar de usar almacenamiento `Persistent`, un contrato usa almacenamiento `Temporary` y extiende continuamente la entrada para que siempre esté activa.
-    - Como no existe interfaz automática para la extensión TTL, y cada extensión TTL debe provenir de una invocación de contrato inteligente o `ExtendFootprintTTLOp`, debe asumirse que el TTL de una entrada puede llegar a 0 y que la entrada puede ser eliminada.
-    - Las tarifas de extensión TTL son variables y podría volverse demasiado costoso extender el TTL de entradas `Temporary` pseudo “persistentes” si las tarifas aumentan inesperadamente.
-    - Si el proceso de extensión TTL es automático (es decir, un trabajo cron), la cuenta que envía automáticamente `ExtendFootprintTTLOps` podría quedarse sin fondos inesperadamente si las tarifas de extensión TTL aumentan, haciendo que la entrada `Temporary` agote su TTL y sea eliminada permanentemente.
-- No se debería depender del agotamiento del TTL de la entrada para funcionalidades o seguridad.
-  - Ejemplo inseguro: un nonce debe expirar en 7 días, por lo que un contrato crea una entrada `Temporary` y extiende el TTL a 7 días sin ninguna otra aplicación de tiempo de vida.
-  - Cualquiera puede enviar una operación de extensión TTL en cualquier entrada sin autorización, lo que significa que el nonce puede tener su TTL extendido indefinidamente por cualquier usuario.
-  - Si una entrada necesita ser invalidada tras cierto tiempo, esto debe implementarse manualmente en el contrato.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/state-archival.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/state-archival.mdx
deleted file mode 100644
index 6f03b64443..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/storage/state-archival.mdx
+++ /dev/null
@@ -1,387 +0,0 @@
----
-sidebar_position: 20
-title: Archivado de estado
-description: Archivado del estado de contratos inteligentes.
----
-
-<head>
-  <title>Archivado del estado de contratos inteligentes.</title>
-  <meta charSet="utf-8" />
-  <meta property="og:title" content="Archivado del estado de contratos inteligentes." />
-  <meta
-    property="og:description"
-    content="Aprende cómo funciona el archivado de estado en la plataforma de contratos inteligentes Soroban."
-  />
-</head>
-
-Los datos del contrato están compuestos por tres tipos diferentes: `Persistent`, `Temporary` e `Instance`. En un contrato, se acceden con `env.storage().persistent()`, `env.storage().temporary()` y `env.storage().instance()` respectivamente; consulta la [documentación de `storage()`](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html).
-
-Aprende a elegir el almacenamiento adecuado para tu caso de uso en esta [Guía práctica](../../../../build/guides/storage/choosing-the-right-storage.mdx) y en otras guías relacionadas con el archivado de estado [aquí](../../../../build/guides/archival).
-
-Todos los datos del contrato tienen un Tiempo de Vida (TTL) que debe extenderse periódicamente. Si el TTL de una entrada no se extiende regularmente, eventualmente llegará a 0 y la entrada será "archivada" o eliminada permanentemente dependiendo del tipo de almacenamiento. Cada tipo de almacenamiento funciona de forma similar, pero con diferentes tarifas y comportamientos de archivado:
-
-- Cuando el TTL de una entrada `Temporary` es 0, se elimina del libro mayor y queda permanentemente inaccesible
-- Cuando el TTL de una entrada `Persistent` o `Instance` es 0, se "archiva" y no puede accederse a ella hasta que se "restaure". Hay dos formas de restaurar entradas:
-  - (generalmente) Automáticamente cuando una entrada archivada es accedida mediante la operación `InvokeHostFunction`
-  - (rara vez) Construyendo manualmente la operación `RestoreFootprintOp`
-
-## Descripciones de tipos de datos de contrato
-
-El uso general e interfaz son idénticos para todos los tipos de almacenamiento. Sólo difieren en tarifas y comportamiento de archivado de la siguiente manera:
-
-### `Temporary`
-
-- Tarifas más económicas.
-- Eliminado permanentemente cuando el TTL llega a 0, no puede ser restaurado.
-- Adecuado para datos con límite temporal (por ejemplo, oráculos de precios, firmas, etc.) y datos que pueden ser fácilmente recreados.
-- Cantidad ilimitada de almacenamiento.
-
-### `Instance`
-
-- Tarifas más costosas (igual precio que almacenamiento `Persistent`).
-- Archivada cuando el TTL llega a 0, se restaura automáticamente a través de la operación `InvokeHostFunction` (o se restaura manualmente usando la operación `RestoreFootprintOp` en casos raros).
-- Comparte el mismo TTL que la instancia del contrato. Si la instancia del contrato no ha sido archivada, los datos de instancia garantizan estar accesibles y no archivados.
-- Cantidad limitada de almacenamiento disponible.
-- Adecuado para estados "compartidos" de contrato que no pueden ser `Temporary` (por ejemplo, cuentas de administrador, metadatos del contrato, etc.).
-
-### `Persistent`
-
-- Tarifas más costosas (igual precio que almacenamiento `Instance`).
-- Archivada cuando el TTL llega a 0, se restaura automáticamente a través de la operación `InvokeHostFunction` (o se restaura manualmente usando la operación `RestoreFootprintOp` en casos raros).
-- No comparte el mismo TTL que la instancia del contrato. Si la instancia del contrato no está archivada, los datos `Persistent` pueden estar archivados y deben restaurarse antes de invocar el contrato.
-- Cantidad ilimitada de almacenamiento.
-- Adecuado para datos de usuario que no pueden ser `Temporary` (por ejemplo, balances).
-
-## Restauración Automática de Datos de Contrato
-
-A partir del Protocolo 23 ([CAP-0066: Recurso de Lectura en Memoria de Soroban](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md#automatic-entry-restoration)), las entradas de contrato `Persistent` o `Instance` archivadas pueden restaurarse automáticamente antes de que se ejecute una función host, pero solo si están incluidas en la lista de restauración de la transacción. En la práctica, esta lista suele completarse mediante la simulación de la invocación del contrato (a través del RPC de Stellar): si la simulación detecta acceso a una entrada archivada, la añade a la lista de restauración. Cuando se ejecuta la operación `InvokeHostFunction` resultante, esas entradas se restauran primero y luego se ejecuta la función host; los alquileres y tarifas normales aún se aplican.
-
-:::important
-
-Si construyes una transacción manualmente sin ejecutar la simulación (y por lo tanto no incluyes todas las entradas archivadas necesarias en la lista de restauración), la restauración automática no ocurrirá y la transacción fallará al intentar acceder a esas entradas archivadas.
-
-:::
-
-## Buenas prácticas para datos de contrato
-
-Como regla general, el almacenamiento `Temporary` sólo debe usarse para datos que puedan recrearse fácilmente o sean válidos sólo por un tiempo limitado, mientras que el almacenamiento `Persistent` o `Instance` debe usarse para datos que no pueden recrearse y deben conservarse permanentemente, como el balance de tokens de un usuario.
-
-Cada tipo de almacenamiento está en un espacio de clave separado. Para demostrar esto, mira el siguiente fragmento de código:
-
-```rust
-const EXAMPLE_KEY: Symbol = symbol_short!("KEY");
-env.storage().persistent().set(&EXAMPLE_KEY, 1);
-env.storage().temporary().set(&EXAMPLE_KEY, 2);
-
-env.storage().persistent().get(&EXAMPLE_KEY); // Returns Ok(1)
-env.storage().temporary().get(&EXAMPLE_KEY); // Returns Ok(2)
-```
-
-Todo el almacenamiento `Instance` se guarda en una sola `LedgerEntry` de instancia de contrato y comparte un único TTL. Esto significa que una llamada a `env.storage().instance().extend_ttl()` extenderá el TTL de todas las entradas `Instance`, así como de la propia instancia del contrato. También extenderá la entrada del código del contrato, sobre lo que profundizaremos en la siguiente sección. Para los almacenamientos `Temporary` y `Persistent`, cada entrada tiene su propio TTL y debe extenderse individualmente. La interfaz es un poco diferente y requiere la clave de la entrada a extender junto con el valor de extensión del TTL.
-
-Una llamada a `extend_ttl(N)` asegura que el TTL actual de la entrada de la instancia del contrato sea _al menos_ N libros mayores. Por ejemplo, si se llama a `extend_ttl(100)` y la entrada de la instancia del contrato tiene un TTL actual de 50 libros mayores, el TTL se extenderá hasta 100 libros mayores. Si se llama a `extend_ttl(100)` y la entrada de la instancia del contrato tiene un TTL actual de 150 libros mayores, el TTL no se extenderá y la llamada a `extend_ttl()` no tendrá efecto.
-
-Además de las extensiones de TTL definidas por el contrato usando la función `extend_ttl()`, el TTL de una entrada de datos de contrato puede extenderse mediante la operación [`ExtendFootprintTTLOp`](#extendfootprintttlop).
-
-## Duración del código y de la instancia del contrato
-
-Las entradas de código de contrato y de instancia tienen duraciones, y hay varias formas de extenderlas. Métodos como `env.storage().instance().extend_ttl()` y `env.deployer().extend_ttl()` extienden tanto el código como la instancia del contrato. La verificación del umbral y las extensiones se realizan de forma independiente tanto para el código como para la instancia del contrato, por lo que es posible que uno se extienda y el otro no, dependiendo de los TTL actuales.
-
-Si deseas extender el código o la instancia por separado, puedes usar `env.deployer().extend_ttl_for_code()` y `env.deployer().extend_ttl_for_contract_instance()` respectivamente. Llamar a ambos con los mismos parámetros es equivalente a llamar sólo a `env.deployer().extend_ttl()`.
-
-## Comportamiento de transacciones que intentan acceder a una entrada Persistent archivada
-
-Aquí algunos puntos importantes que debes tener en cuenta respecto a las entradas archivadas:
-
-1. Una transacción Soroban que tiene una clave de una entrada Persistent archivada en la huella fallará inmediatamente durante la etapa de aplicación antes de la ejecución del contrato. No importa si el contrato iba a acceder a la entrada.
-2. Debido al punto anterior de que las entradas archivadas nunca llegan a la lógica del contrato inteligente, no hay razón para escribir código en tu contrato para manejar entradas archivadas. Lo mismo aplica para los casos de prueba del contrato: aunque puedas querer escribir pruebas que verifiquen si tu lógica de extensión es correcta, no necesitas escribir pruebas de archivado porque la transacción fallará antes de llegar al contrato. No obstante, es posible acceder a una entrada archivada en un caso de prueba Soroban, caso en el que el host entrará en pánico. Puedes leer más sobre esto en [Pruebas de extensiones TTL](../../../../build/guides/archival/test-ttl-extension.mdx).
-3. Las entradas persistentes archivadas nunca se pueden volver a crear. En cambio, deben ser restauradas. Una vez restauradas, pueden ser modificadas o eliminadas.
-
-## Términos y semántica
-
-### Vivir hasta el libro mayor
-
-Cada entrada `ContractData` y `ContractCode` tiene un campo `liveUntilLedger` almacenado en su `LedgerEntry`. La entrada ya no está viva (es decir, está archivada o eliminada dependiendo del tipo de almacenamiento) cuando `current_ledger > liveUntilLedger`.
-
-### TTL
-
-El Tiempo de Vida (TTL) de una entrada se define como cuántos libros restantes quedan hasta que la entrada deje de estar viva. Por ejemplo, si el libro actual es 5 y una entrada tiene `liveUntilLedger` en 15, entonces su TTL es de 10 libros.
-
-### TTL mínimo
-
-Para cada tipo de entrada, existe un TTL mínimo que la entrada tendrá al crearse o restaurarse. Este mínimo TTL se aplica automáticamente a nivel de protocolo.
-
-TTL mínimo es un parámetro de la red. Consulta la [referencia de recursos](../../../../networks/resource-limits-fees.mdx) para conocer los valores actuales.
-
-### TTL máximo
-
-En cualquier libro, el TTL de una entrada puede extenderse hasta el TTL máximo. Este es un parámetro de red (consulta la [tabla de límites de recursos](../../../../networks/resource-limits-fees.mdx) para conocer el TTL máximo actual). El TTL máximo no se aplica basándose en la fecha de creación de la entrada, sino en el libro actual. Por ejemplo, si una entrada se crea el 1 de enero de 2024, su TTL inicial podría extenderse hasta el 1 de enero de 2025. Después de esta extensión inicial, si la entrada recibe otra extensión el 10 de enero de 2024, el TTL podría extenderse hasta el 10 de enero de 2025. La función `max_ttl()` puede usarse para determinar el TTL máximo permitido actual.
-
-## Operaciones
-
-### ExtendFootprintTTLOp
-
-#### Semántica
-
-XDR:
-
-```
-/*
-    Threshold: low
-    Result: ExtendFootprintTTLResult
-*/
-struct ExtendFootprintTTLOp
-{
-    ExtensionPoint ext;
-    uint32 extendTo;
-};
-```
-
-`ExtendFootprintTTLOp` es una operación Soroban que extenderá el valor de live until ledger de las entradas especificadas en el _conjunto de sólo lectura de la huella_. El conjunto de lectura-escritura debe estar vacío. La extensión asegurará que el TTL de las entradas sea al menos extendTo libros mayores a partir de ahora.
-
-Veamos este ejemplo a continuación.
-
-```
-Ex. Last closed ledger (LCL) = 5, Current Ledger = 6, liveUntilLedger = 8
-
-entry1.liveUntilLedger = 10
-entry2.liveUntilLedger = 14
-entry3.liveUntilLedger = 10000
-
-entry1.liveUntilLedger will be updated to 14 so it will live for 8 more ledgers, including
-the current ledger, and the entry can be accessed in ledgers [6, 13].
-
-entry2 and entry3 will not be updated because they already have an
-liveUntilLedger that is large enough.
-```
-
-#### Recursos de la transacción
-
-`ExtendFootprintTTLOp` es una operación Soroban y, por lo tanto, debe ser la única operación en una transacción. La transacción también debe completar la extensión de transacción `SorobanTransactionData` explicada [aquí](../contract-interactions/stellar-transaction.mdx#transaction-resources). Para completar `SorobanResources`, usa la simulación de la transacción mencionada en el enlace proporcionado, o asegúrate de que `readBytes` incluya la clave y tamaño de entrada de cada entrada en el conjunto `readOnly`.
-
-### RestoreFootprintOp
-
-`RestoreFootprintOp`, en general, ya no es necesario a partir del Protocolo 23, ya que las entradas archivadas se restauran automáticamente cuando aparecen en una huella durante `InvokeHostFunctionOp`.
-
-`RestoreFootprintOp` todavía puede usarse en casos de uso raros, tales como:
-
-- Si la restauración automática hace que una transacción sea demasiado grande para ajustarse a los límites de la red, la restauración puede realizarse por separado mediante `RestoreFootprintOp`
-- Si los desarrolladores de contratos quieren asegurarse de pagar las tarifas de restauración (en lugar de sus usuarios), pueden restaurar sus entradas bajo demanda con `RestoreFootprintOp`
-
-XDR:
-
-```
-/*
-    Threshold: low
-    Result: RestoreFootprintOp
-*/
-struct RestoreFootprintOp
-{
-    ExtensionPoint ext;
-};
-```
-
-`RestoreFootprintOp` es una operación Soroban que restaurará las entradas archivadas especificadas en el _conjunto de lectura-escritura de la huella_ y las hará accesibles nuevamente. El conjunto de sólo lectura de la huella debe estar vacío. Una entrada archivada es aquella cuyo liveUntilLedger es menor que el número de libro actual. **Sólo las entradas persistent y instance pueden ser restauradas.**
-
-La entrada restaurada tendrá su live until ledger extendido al [mínimo] que la red permite para entradas recién creadas, que es `current_ledger_number + 4095` para entradas persistent. El valor mínimo de TTL es un parámetro de configuración de la red y puede actualizarse (probablemente aumentado) mediante actualizaciones de red.
-
-[mínimo]: https://github.com/stellar/stellar-core/blob/2109a168a895349f87b502ae3d182380b378fa47/src/ledger/NetworkConfig.h#L77-L78
-
-#### Recursos de la transacción
-
-`RestoreFootprintOp` es una operación Soroban y, por lo tanto, debe ser la única operación en una transacción. La transacción también debe completar la extensión de transacción `SorobanTransactionData` explicada [aquí](../contract-interactions/stellar-transaction.mdx#transaction-resources). Para completar `SorobanResources`, usa la simulación de la transacción mencionada en el enlace proporcionado, o asegúrate de que `writeBytes` incluya la clave y tamaño de entrada de cada entrada en el conjunto `readWrite` y que `extendedMetaDataSizeBytes` sea al menos el doble de `writeBytes`.
-
----
-
-## Ejemplos
-
-Hemos hecho lo posible para construir herramientas alrededor del archivado de estado tanto en el servidor RPC de Stellar como en el SDK de JavaScript para facilitar su uso, y este conjunto de ejemplos demuestra cómo aprovecharlo.
-
-### Resumen
-
-:::info
-
-La operación manual (`RestoreFootprintOp`) ya no es necesaria en la mayoría de los casos a partir del Protocolo 23, ya que las entradas archivadas se restauran automáticamente cuando aparecen en una huella durante `InvokeHostFunctionOp`. `RestoreFootprintOp` puede usarse en casos raros descritos [arriba](#restorefootprintop).
-
-:::
-
-Tanto restaurar como extender el TTL de entradas del libro sigue un proceso de tres pasos, sin importar su naturaleza (datos de contrato, instancias, etc.):
-
-1. **Identificar las entradas del libro.** Esto generalmente significa obtenerlas desde un servidor RPC Stellar como parte de la simulación inicial de tu transacción (consulte la [documentación de simulación de transacciones](../contract-interactions/transaction-simulation.mdx) y el método RPC [`simulateTransaction`](../../../../data/apis/rpc/api-reference/methods/simulateTransaction.mdx)).
-
-2. **Preparar tu operación.** Esto implica describir las entradas del libro mayor dentro de la operación correspondiente (es decir, `ExtendFootprintTTLOp` o `RestoreFootprintOp`) y su huella del libro mayor (el campo `SorobanTransactionData`), y luego simularla para completar la información de tarifas y uso de recursos (al restaurar, normalmente ya se tienen los resultados de la simulación).
-
-3. **Enviar la transacción** y empezar de nuevo con lo que querías hacer en primer lugar.
-
-Cada uno de los ejemplos siguientes seguirá una estructura similar. Trabajaremos con dos escenarios diferentes:
-
-1. [un dato persistent en mi contrato está archivado](#example-my-data-is-archived)
-2. [mi instancia de contrato o el WASM están archivados](#example-my-contract-is-archived)
-
-Recuerda que, sin embargo, cualquier combinación de estos escenarios puede ocurrir en la realidad.
-
-### Preparación
-
-Para facilitar la estructuración del código, reutilizaremos la función básica de sondeo de transacciones con reintentos habilitados `submitTx`, que describimos en [otra guía](../../../../build/guides/transactions/submit-transaction-wait-js.mdx).
-
-En el siguiente código, también aprovecharemos [`Server.prepareTransaction`](https://stellar.github.io/js-stellar-sdk/module-rpc.Server.html#prepareTransaction). Este es un método útil que, dado un transaction, lo simula, luego modifica la transacción con los resultados de la simulación (tarifas, etc.) y devuelve eso. Luego, sólo puede firmarse y enviarse. También usaremos [`SorobanDataBuilder`](https://stellar.github.io/js-stellar-sdk/SorobanDataBuilder.html), una abstracción conveniente que nos permite usar un [patrón Builder](https://es.wikipedia.org/wiki/Patr%C3%B3n_builder) para establecer las huellas de almacenamiento apropiadas para una transacción.
-
-### Ejemplo: ¡Mis datos están archivados!
-
-Comenzaremos con la ocurrencia más probable: mi dato persistent está archivado porque no he interactuado con mi contrato en un tiempo. ¿Cómo puedo hacerlo accesible de nuevo?
-
-En este ejemplo, asumiremos dos cosas: el contrato en sí sigue activo (es decir, otros han estado extendiendo su TTL mientras no estabas) y no sabes cómo se representa tu dato archivado en el libro mayor. Si lo supieras, podrías saltarte los pasos a continuación donde lo averiguamos y simplemente preparar la huella de restauración directamente. El proceso involucra tres pasos discretos:
-
-1. Simula nuestra transacción como normalmente lo harías.
-2. Si la simulación lo indica, realizamos la restauración a través de [`Operation.restoreFootprint`](https://stellar.github.io/js-stellar-sdk/Operation.html#.restoreFootprint) usando sus sugerencias.
-3. Reintentos para ejecutar nuestra transacción inicial.
-
-Veamos eso en código:
-
-```typescript
-import {
-  BASE_FEE,
-  Networks,
-  Keypair,
-  TransactionBuilder,
-  SorobanDataBuilder,
-  rpc as StellarRpc,
-  xdr,
-} from "@stellar/stellar-sdk"; // add'l imports to preamble
-const { Api, assembleTransaction } = StellarRpc;
-
-// assume that `server` is the Server() instance from the preamble
-
-async function submitOrRestoreAndRetry(
-  signer: Keypair,
-  tx: Transaction,
-): Promise<Api.GetTransactionResponse> {
-  // We can't use `prepareTransaction` here because we want to do
-  // restoration if necessary, basically assembling the simulation ourselves.
-  const sim = await server.simulateTransaction(tx);
-
-  // Other failures are out of scope of this tutorial.
-  if (!Api.isSimulationSuccess(sim)) {
-    throw sim;
-  }
-
-  // If simulation didn't fail, we don't need to restore anything! Just send it.
-  if (!Api.isSimulationRestore(sim)) {
-    const prepTx = assembleTransaction(tx, sim);
-    prepTx.sign(signer);
-    return submitTx(prepTx);
-  }
-
-  //
-  // Build the restoration operation using the RPC server's hints.
-  //
-  const account = await server.getAccount(signer.publicKey());
-  let fee = parseInt(BASE_FEE);
-  fee += parseInt(sim.restorePreamble.minResourceFee);
-
-  const restoreTx = new TransactionBuilder(account, { fee: fee.toString() })
-    .setNetworkPassphrase(Networks.TESTNET)
-    .setSorobanData(sim.restorePreamble.transactionData.build())
-    .addOperation(Operation.restoreFootprint({}))
-    .build();
-
-  restoreTx.sign(signer);
-
-  const resp = await submitTx(restoreTx);
-  if (resp.status !== Api.GetTransactionStatus.SUCCESS) {
-    throw resp;
-  }
-
-  //
-  // now that we've restored the necessary data, we can retry our tx using
-  // the initial data from the simulation (which, hopefully, is still
-  // up-to-date)
-  //
-  const retryTxBuilder = TransactionBuilder.cloneFrom(tx, {
-    fee: (parseInt(tx.fee) + parseInt(sim.minResourceFee)).toString(),
-    sorobanData: sim.transactionData.build(),
-  });
-  // because we consumed a sequence number when restoring, we need to make sure
-  // we set the correct value on this copy
-  retryTxBuilder.source.incrementSequenceNumber();
-
-  const retryTx = retryTxBuilder.build();
-  retryTx.sign(signer);
-
-  return submitTx(retryTx);
-}
-```
-
-Observa que cuando la restauración es necesaria, **la simulación aún tiene éxito**. La forma en que sabemos que algo debe restaurarse es la presencia de la estructura `restorePreamble` en la respuesta del RPC. Esto contiene tanto la huella como la tarifa necesarias para la restauración, mientras que el resto de la respuesta contiene la simulación de la invocación **como si** la restauración se hubiera hecho primero.
-
-Esto es genial, ya que significa menos viajes para comenzar de nuevo.
-
-### Ejemplo: ¡Mi contrato está archivado!
-
-Como puedes imaginar, si la instancia de contrato desplegada o el código que la respalda están archivados, no pueden cargarse para ejecutar tus invocaciones. Recuerda que hay una relación distinta de uno a muchos en la cadena entre el código de un contrato y las instancias desplegadas de ese contrato:
-
-```mermaid
-flowchart LR
-    A[my instance] & B[your instance]--> C[contract WASM]
-```
-
-Necesitamos que **ambos** estén activos para que nuestras llamadas al contrato funcionen.
-
-Veamos cómo se pueden recuperar. El proceso de recuperación es un poco diferente: mientras que no necesitamos simulación para determinar las huellas, sí necesitamos hacer una consulta adicional a la entrada del libro mayor. Podemos usar [`Contract.getFootprint()`](https://stellar.github.io/js-stellar-sdk/Contract.html#getFootprint) para obtener la clave del libro usada por una instancia de contrato dada, pero eso no nos dará su código WASM de respaldo. Para eso, recrearemos [este ejemplo](../../../../data/apis/rpc/api-reference/methods/getLedgerEntries.mdx#requesting-a-contracts-wasm-code) aquí.
-
-También necesitamos la simulación para conocer las tarifas de nuestra restauración. Esto, sin embargo, puede cubrirse fácilmente con el ayudante [`Server.prepareTransaction`](https://stellar.github.io/js-stellar-sdk/module-rpc.Server.html#prepareTransaction) del SDK, que hace la simulación y el ensamblado por nosotros:
-
-```typescript
-import {
-  BASE_FEE,
-  Contract,
-  Keypair,
-  Networks,
-  TransactionBuilder,
-  SorobanDataBuilder,
-  Operation,
-  rpc as StellarRpc,
-} from "@stellar/stellar-sdk";
-
-async function restoreContract(
-  signer: Keypair,
-  c: Contract,
-): Promise<StellarRpc.Api.GetTransactionResponse> {
-  const instance = c.getFootprint();
-
-  const account = await server.getAccount(signer.publicKey());
-  const wasmEntry = await server.getLedgerEntries(
-    getWasmLedgerKey(instance)
-  );
-
-  const restoreTx = new TransactionBuilder(account, { fee: BASE_FEE })
-    .setNetworkPassphrase(Networks.TESTNET)
-    .setSorobanData(
-      // Set the restoration footprint (remember, it should be in the
-      // read-write part!)
-      new SorobanDataBuilder().setReadWrite([
-        instance,
-        wasmEntry
-      ]).build(),
-    )
-    .addOperation(Operation.restoreFootprint({}))
-    .build();
-
-  const preppedTx = await server.prepareTransaction(restoreTx);
-  preppedTx.sign(signer);
-  return submitTx(preppedTx);
-}
-
-function getWasmLedgerKey(entry: xdr.ContractDataEntry):  {
-  return xdr.LedgerKey.contractCode(
-    new xdr.LedgerKeyContractCode({
-      hash: entry.val().instance().wasmHash()
-    })
-  );
-}
-```
-
-Lo bueno de este método es que restaurará tanto la instancia como el código WASM subyacente si es necesario, omitiendo cualquiera si ya están en el estado del libro mayor.
-
-[`restorefootprintop`]: #RestoreFootprintOp
-[`extendfootprintttlop`]: #ExtendFootprintTTLOp
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/transaction-lifecycle.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/transaction-lifecycle.mdx
deleted file mode 100644
index 172991026d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/transaction-lifecycle.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-sidebar_position: 50
-title: Ciclo de vida de la transacción
-description: aquí se explica cómo funciona una transacción y esas cosas.
-draft: true
----
-
-Consulta [GH issue #532](https://github.com/stellar/soroban-docs/issues/532) para más detalles.
-
-Estamos recibiendo muchas preguntas relacionadas con el ciclo de vida de la transacción y no tenemos un buen recurso para compartir.
-
-Los recursos habituales de Stellar son confusos porque:
-
-1. no incluyen información sobre la pre-ejecución y
-2. la presentación de tx en stellar-rpc es asíncrona
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/README.mdx
deleted file mode 100644
index a6a371091d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Tipos
-sidebar_position: 9
----
-
-import DocCardList from "@theme/DocCardList";
-
-Aprende sobre los tipos y las estructuras de datos disponibles para desarrolladores en los contratos inteligentes de Soroban.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/built-in-types.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/built-in-types.mdx
deleted file mode 100644
index fe9757758f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/built-in-types.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
----
-sidebar_position: 10
-title: Tipos incorporados
-description: Tipos incorporados usados como entradas y salidas de contratos inteligentes.
----
-
-<head>
-  <title>Tipos incorporados usados como entradas y salidas de contratos inteligentes.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Tipos incorporados usados como entradas y salidas de contratos inteligentes."
-  />
-  <meta
-    property="og:description"
-    content="Conoce los tipos incorporados disponibles en contratos inteligentes Soroban, incluyendo tipos primitivos, símbolos, bytes, cadenas, vecs, mapas y direcciones."
-  />
-</head>
-
-Los tipos incorporados están disponibles para todos los contratos para usarse como entradas y salidas de funciones del contrato, y son definidos por el [entorno] y el [SDK de Rust].
-
-[entorno]: ../environment-concepts.mdx
-[sdk de rust]: ../../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk
-
-:::tip
-
-También se soportan tipos personalizados como structs, enums y unions. Consulta Tipos personalizados.
-
-:::
-
-## Tipos primitivos
-
-Se soportan los siguientes tipos primitivos:
-
-### Entero sin signo de 32 bits (`u32`)
-
-### Entero con signo de 32 bits (`i32`)
-
-### Entero sin signo de 64 bits (`u64`)
-
-### Entero con signo de 64 bits (`i64`)
-
-### Entero sin signo de 128 bits (`u128`)
-
-### Entero con signo de 128 bits (`i128`)
-
-### Booleano (`bool`)
-
-## Símbolo (`Symbol`)
-
-Los símbolos son cadenas pequeñas y eficientes de hasta 32 caracteres limitados a `a-z`, `A-Z`, `0-9`, `_` y codificados en enteros de 64 bits.
-
-Los símbolos se usan principalmente para nombres de funciones y otros identificadores que se exportan en la API pública de un contrato. También pueden usarse donde se necesitan cadenas cortas para mantener bajos los costos de recursos.
-
-## Bytes, Cadenas (`Bytes`, `BytesN`, `String`)
-
-Arrays de bytes y cadenas pueden pasarse a contratos y almacenes usando el tipo `Bytes`.
-
-Para arrays de bytes de longitud fija, se puede usar `BytesN`. Por ejemplo, los IDs de contrato son arrays de bytes de 32 bytes fijos, representados como `BytesN<32>`.
-
-Ten en cuenta que los bytes contenidos en `String`s no necesariamente cumplen con ninguna codificación de texto estándar como ASCII o Unicode UTF-8. Son bytes simples sin interpretar, y los usuarios que esperen una codificación específica deben hacer que esa codificación se aplique manualmente.
-
-## Vec (`Vec`)
-
-Vec es un tipo de colección secuencial, indexable y ampliable.
-
-Los valores se almacenan en el entorno y están disponibles para el contrato a través de las funciones definidas en Vec. Los valores almacenados en el Vec se transmiten al entorno como RawVals, y cuando se recuperan del Vec, se transmiten de vuelta y se convierten de RawVal a su tipo.
-
-No se garantiza que los valores en un Vec sean de un tipo específico y la conversión fallará si no son del tipo esperado. Por eso, la mayoría de las funciones en Vec devuelven un Result.
-
-## Map (`Map`)
-
-Map es un diccionario clave-valor ordenado.
-
-El mapa está ordenado por sus claves. Iterar un mapa es estable y siempre devuelve las claves y valores en el orden de las claves.
-
-El mapa se almacena en el Host y está disponible para el Guest a través de las funciones definidas en Map. Los valores almacenados en el Map se transmiten al Host como RawVals, y cuando se recuperan del Map se transmiten de vuelta y se convierten de RawVal a su tipo.
-
-No se garantiza que las claves y valores en un Map sean del tipo K/V y la conversión fallará si no lo son. Por eso, la mayoría de las funciones en Map devuelven un Result.
-
-Los mapas tienen a lo sumo una entrada por clave. Establecer un valor para una clave en el mapa que ya tiene un valor para esa clave reemplaza el valor.
-
-## Dirección (`Address`)
-
-Address es un identificador opaco universal para usar en contratos. Puede representar una cuenta 'clásica' Stellar, una cuenta personalizada implementada en Soroban o simplemente un contrato arbitrario.
-
-Address puede usarse como argumento de entrada de función de contrato (por ejemplo, para identificar al receptor de pago), como clave de datos (por ejemplo, para almacenar el saldo), como fuente de autenticación y autorización (por ejemplo, para autorizar una transferencia de token), etc.
-
-Consulta la [documentación de autorización](../authorization.mdx) para más detalles sobre cómo usar el tipo `Address`.
-
-## Opción (`Option`)
-
-Option representa un valor opcional.
-
-El tipo Option se usa para valores que pueden estar presentes o no. El tipo Option es un enum y puede ser `Some` (existe algún valor) o `None` (no existe valor).
-
-Aunque Option actúa como el `Option<T>` de Rust, el tipo Option no se representa explícitamente en XDR. El tipo Option se representa en el XDR por el valor `ScVal` `ScVoid` cuando no existe valor (None), y por cualquier otro valor `ScVal` cuando el valor existe (Some).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/custom-types.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/custom-types.mdx
deleted file mode 100644
index fd5c67f3fe..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/custom-types.mdx
+++ /dev/null
@@ -1,125 +0,0 @@
----
-sidebar_position: 20
-title: Tipos personalizados
-description: Tipos struct, union y enum definidos por contratos.
----
-
-<head>
-  <title>Tipos struct, union y enum definidos por contratos.</title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Tipos struct, union y enum definidos por contratos."
-  />
-  <meta
-    property="og:description"
-    content="Consulta los tipos struct, union y enum que se pueden usar como entradas de contrato, salidas de contrato o para almacenamiento."
-  />
-</head>
-
-Los tipos personalizados son tipos struct, union y enum definidos por contratos. Se pueden usar en todos los lugares donde se usen tipos primitivos: como entradas de contratos, salidas o para almacenamiento.
-
-:::info
-
-El [ejemplo de tipos personalizados] muestra cómo definir tus propios tipos.
-
-[ejemplo de tipos personalizados]: ../../../../build/smart-contracts/example-contracts/custom-types.mdx
-
-:::
-
-:::info
-
-Los tipos enum de error son otro tipo que los contratos pueden definir y que tienen comportamientos únicos. Consulta [Errores](../errors-and-debugging/errors.mdx) para más información.
-
-:::
-
-## Structs (con campos nombrados)
-
-Los structs con campos nombrados se almacenan en el libro mayor como un mapa de pares clave-valor, donde la clave es una cadena de 32 caracteres que representa el nombre del campo y el valor es el valor codificado.
-
-Los nombres de campos no deben tener más de 32 caracteres. Los campos con nombres de no más de 9 caracteres son un poco más eficientes en tiempo de ejecución, aunque la diferencia debería ser mínima la mayoría de las veces.
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub struct State {
-    pub count: u32,
-    pub last_incr: u32,
-}
-```
-
-Cuando se convierte a XDR, el valor se convierte en un `ScVal`, que contiene un `ScMap`, el cual contiene un arreglo de pares clave-valor.
-
-```json
-{
-  "map": [
-    { "key": { "symbol": "count" }, "val": { "u32": 0 } },
-    { "key": { "symbol": "last_incr" }, "val": { "u32": 0 } }
-  ]
-}
-```
-
-## Structs (con campos sin nombre)
-
-Los structs con campos sin nombre se almacenan en el libro mayor como un vector de valores, y son intercambiables con tuplas y vectores. Los elementos se colocan en el vector en el orden en que aparecen en la lista de campos.
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub struct State(pub u32, pub u32);
-```
-
-Cuando se convierte a XDR, el valor se convierte en un `ScVal`, que contiene un `ScVec`, el cual contiene un arreglo de valores.
-
-```json
-{ "vec": [{ "u32": 0 }, { "u32": 0 }] }
-```
-
-## Enum (variantes unitarias y de tupla)
-
-Los enums que contienen variantes unitarias y de tupla se almacenan en el libro mayor como un vector de dos elementos, donde el primer elemento es el nombre de la variante del enum como una cadena de hasta 32 caracteres, y el valor es el valor si la variante tiene uno.
-
-Solo se admiten variantes unitarias y variantes de tupla, como `A` y `B` a continuación.
-
-```rust
-#[contracttype]
-#[derive(Clone, Debug, Eq, PartialEq)]
-pub enum Enum {
-    A,
-    B(u32),
-}
-```
-
-Cuando una variante unitaria, como `Enum::A`, se convierte a XDR, el valor se convierte en un `ScVal`, que contiene un `ScVec`, con un arreglo de un solo valor, el símbolo que contiene el nombre de la variante.
-
-```json
-{ "vec": [{ "symbol": "A" }] }
-```
-
-Cuando una variante de tupla, como `Enum::B`, se convierte a XDR, el valor se convierte en un `ScVal`, que contiene un `ScVec`, con un arreglo de dos valores, el símbolo que contiene el nombre de la variante y el valor de la tupla.
-
-```json
-{ "vec": [{ "symbol": "B" }, { "u32": 0 }] }
-```
-
-Cuando se implementen variantes de tupla que contengan múltiples valores, los valores se incluirán en el vector.
-
-## Enum (variantes enteras)
-
-Los enums que contienen valores enteros se almacenan en el libro mayor como el valor `u32`.
-
-```rust
-#[contracttype]
-#[derive(Copy, Clone, Debug, Eq, PartialEq)]
-#[repr(u32)]
-pub enum Enum {
-    A = 1,
-    B = 2,
-}
-```
-
-Cuando se convierte a XDR, el valor se convierte en un `ScVal`, que contiene un `U32`.
-
-```json
-{ "u32": 1 }
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
deleted file mode 100644
index 45739e7a7f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/contract-development/types/fully-typed-contracts.mdx
+++ /dev/null
@@ -1,117 +0,0 @@
----
-sidebar_position: 30
-title: Contratos completamente tipados
-desctiption: Los archivos WASM de contratos inteligentes contienen una descripción legible por máquina del tipo de interfaz.
-sidebar_label: Contratos completamente tipados
----
-
-<head>
-  <title>
-    {`Los archivos WASM de contratos inteligentes contienen una descripción legible por máquina del 
-    tipo de interfaz.`}
-  </title>
-  <meta charSet="utf-8" />
-  <meta
-    property="og:title"
-    content="Los archivos WASM de contratos inteligentes contienen una descripción legible por máquina del tipo de interfaz."
-  />
-  <meta
-    property="og:description"
-    content="Todos los tipos de interfaz de contratos inteligentes estarán disponibles en la cadena inmediatamente, sin llamadas secundarias a APIs externas, sin gestión secundaria de APIs y mucho más."
-  />
-</head>
-
-Cuando compilas un contrato creado con [soroban-sdk](../../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk), el archivo Wasm termina con una [sección personalizada](https://webassembly.github.io/spec/core/appendix/custom.html) que contiene una descripción legible por máquina de los tipos de interfaz de tu contrato, a veces llamada su [especificación](https://github.com/stellar/rs-soroban-sdk/tree/main/soroban-spec) o su [API](https://github.com/stellar/soroban-docs/pull/381#issuecomment-1507283476). Esto es similar a las [ABIs](https://www.quicknode.com/guides/ethereum-development/smart-contracts/what-is-an-abi/) en Ethereum, excepto que Soroban almacenará cada una de ellas en la cadena desde el primer día, e incluyen comentarios del autor del contrato.
-
-Estos tipos de interfaz están formateados usando [XDR](../../../fundamentals/data-format/xdr.mdx), un formato de datos ampliamente utilizado en Stellar. Puede ser complicado crear o consumir XDR manualmente, pero las herramientas pueden obtener estos tipos de interfaz para facilitarte la vida. [Stellar CLI](../../../../tools/cli/README.mdx#cli) y [Stellar SDK](../../../../tools/sdks/client-sdks.mdx#javascript-sdk) son dos herramientas que pueden hacerlo. Veamos cada una.
-
-## Stellar CLI: `stellar contract invoke`
-
-En realidad, cada contrato inteligente es un programa propio y merece su propia CLI.
-
-Eso es justo lo que te ofrece Stellar CLI.
-
-Una CLI única para cada contrato inteligente. Construida dinámicamente, directamente desde los tipos de interfaz en la cadena. Incluyendo los comentarios del autor. Una _CLI implícita_.
-
-Por ejemplo, llamando al contrato del activo nativo en la red de prueba:
-
-```bash
-$ stellar contract invoke --network testnet --id CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC -- --help
-Usage: CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC [COMMAND]
-
-Commands:
-  balance         Returns the balance of `id`.
-
-                      # Arguments
-
-                      * `id` - The address for which a balance is being queried. If the
-                      address has no existing balance, returns 0.
-  ...
-  transfer        Transfer `amount` from `from` to `to`.
-
-                      # Arguments
-
-                      * `from` - The address holding the balance of tokens which will be
-                      withdrawn from.
-                      * `to` - The address which will receive the transferred tokens.
-                      * `amount` - The amount of tokens to be transferred.
-
-                      # Events
-
-                      Emits an event with topics `["transfer", from: Address, to: Address],
-                      data = amount: i128`
-  ...
-
-Options:
-  -h, --help  Print help
-```
-
-Como cualquier otra CLI, también puedes obtener ayuda para cualquiera de estos subcomandos. Omitiendo todo antes del `--` en el comando anterior, esto se vería así: `… -- balance --help`. Stellar CLI vuelve a obtener los tipos de interfaz de la cadena, esta vez usándolos para generar una lista completa de todos los argumentos de la función e incluso genera ejemplos.
-
-:::tip
-
-Si no estás familiarizado con el separador `--` de doble guion, es un patrón usado por otras CLIs. Todo lo que viene después del doble guion, a veces llamado [slop](https://github.com/clap-rs/clap/issues/971), se pasa al proceso hijo. Ejemplos de otras CLIs que usan esto son `npm run` y `cargo run`.
-
-:::
-
-## Stellar JS SDK: `contract.Client`
-
-Para crear un cliente de contrato para el mismo contrato mostrado con `contract invoke` arriba, usarías este JavaScript:
-
-```js
-import { contract } from "@stellar/stellar-sdk";
-const xlm = contract.Client.from({
-  contractId: "CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC",
-  networkPassphrase: "Test SDF Network ; September 2015",
-  rpcUrl: "https://soroban-testnet.stellar.org",
-});
-```
-
-Como la CLI, esto obtendrá el contrato de la red activa y analizará los tipos/especificaciones del contrato. Generará automáticamente una clase que te permite llamar ergonómicamente a los métodos del contrato:
-
-```js
-xlm.balance({ id: "G123…" });
-```
-
-Ten en cuenta que todo lo mostrado arriba funciona dinámicamente desde un navegador. Sin embargo, a veces es útil tener este comportamiento disponible como una biblioteca al construir aplicaciones. Y en este caso, es realmente útil tener TypeScript, que permite autocompletado de todos los métodos del contrato, e incluye los comentarios del autor original del contrato. Para eso sirve el comando `contract bindings typescript` de la CLI:
-
-```bash
-stellar contract bindings typescript \
-  --network testnet \
-  --output-dir xlm --overwrite \
-  --id CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC
-```
-
-Esto crea un módulo NPM completamente tipado para el contrato dado.
-
-## Ya es lo mejor; apenas comenzando
-
-Nos encanta que Soroban tuviera todos los tipos de interfaz de contrato disponibles en la cadena desde el primer día. Sin llamadas secundarias a APIs externas, sin gestión secundaria de tokens API, sin iniciar sesión ni crear cuentas en otros lugares, y con una fiabilidad casi perfecta. Es un cambio radical en el espacio blockchain.
-
-Stellar CLI y JS SDK ya muestran cómo esto puede integrarse en herramientas fundamentales para ofrecer experiencias satisfactorias a desarrolladores. Y esto es solo el comienzo. En todos los niveles de la pila, puedes esperar—y [construir](https://stellar.org/foundation/grants-and-funding)—herramientas que hagan la interacción con cualquier contrato predecible y fluida.
-
-Pronto tendremos interfaces gráficas que se adapten a cualquier contrato en tiempo real, funcionando como documentación interactiva. Si escribes contratos que hagan llamadas entre contratos, la mayoría del código que necesitas también puede autogenerarse.
-
-Y todo eso sigue siendo solo el principio. Con esos como fundamentos, ¿qué más podemos construir? ¿Qué más puedes imaginar? ¿Cuál es el futuro de los componentes, ahora que un pequeño programa, es decir, un contrato inteligente, puede ser fácilmente interactuado en todas las capas de la pila de software? Considerando la combinación con Wasm—en la cadena, en el navegador y en [otros lugares](https://en.wikipedia.org/wiki/WebAssembly#Implementations)—¿qué posibilidades de interoperabilidad podemos imaginar y co-crear?
-
-Estamos deseando ver lo que construyes.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/README.mdx
deleted file mode 100644
index 769e5d9420..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/README.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Formato de datos
-sidebar_position: 85
----
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/xdr-json.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/xdr-json.mdx
deleted file mode 100644
index 08796e406a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/xdr-json.mdx
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: XDR-JSON
-sidebar_position: 2
----
-
-El esquema XDR-JSON está definido por la [biblioteca stellar-xdr](https://docs.rs/stellar-xdr) y proporciona un método reversible para convertir valores Stellar [XDR] a JSON y convertir ese JSON de vuelta al XDR idéntico.
-
-La conversión con el esquema también está disponible en las siguientes herramientas y bibliotecas.
-
-El esquema JSON para el formato XDR-JSON se puede encontrar usando el comando [`stellar xdr types schema`].
-
-## Herramientas
-
-- [Stellar CLI > `stellar xdr`](../../../tools/cli/stellar-cli.mdx#stellar-xdr)
-- [Laboratorio > Ver XDR](../../../tools/lab/README.mdx)
-
-## Bibliotecas
-
-- biblioteca rust [stellar-xdr](https://docs.rs/stellar-xdr)
-- paquete npm [@stellar/stellar-xdr-json](https://www.npmjs.com/package/@stellar/stellar-xdr-json)
-- paquete go [github.com/stellar/go-stellar-xdr-json](https://github.com/stellar/go-stellar-xdr-json)
-
-## Características clave del esquema de conversión JSON y XDR
-
-- **Convertible sin pérdida:** El formato JSON permite convertir de XDR a JSON y volver a XDR sin pérdida de información.
-
-- **Autodescriptivo:** El formato JSON describe el interior del tipo pero no identifica el tipo que está codificado. Esto es similar a XDR, que tampoco identifica el tipo codificado.
-
-- **Enteros de 64 bits:** El formato JSON incluye enteros de hasta 64 bits de tamaño. Los entornos de ejecución JavaScript no admiten enteros de 64 bits, por lo que debe usarse un decodificador personalizado, como [lossless-json](https://www.npmjs.com/package/lossless-json).
-
-- **Cadenas ASCII escapadas:** El formato JSON incluye cadenas que son seguras en UTF-8, cadenas ASCII escapadas. Esto se debe a que las cadenas XDR no están codificadas en UTF-8, sino que son flujos de bytes que pueden contener cualquier valor. Los caracteres no ASCII están escapados.
-
-:::info[backwards-incompatible]
-
-El esquema definido (enlazado arriba) **no** es compatible con versiones anteriores entre una versión de protocolo dada y versiones previas. La práctica recomendada es almacenar los datos del ledger requeridos en formato XDR, no en formato JSON.
-
-:::
-
-[XDR]: xdr
-[`stellar xdr types schema`]: ../../../tools/cli/stellar-cli.mdx#stellar-xdr-types-schema
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/xdr.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/xdr.mdx
deleted file mode 100644
index 91a32a2521..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/data-format/xdr.mdx
+++ /dev/null
@@ -1,223 +0,0 @@
----
-title: XDR
-sidebar_position: 1
----
-
-Stellar almacena y comunica datos del libro mayor, transacciones, resultados, historial y mensajes en un formato binario llamado External Data Representation (XDR). XDR está definido en [RFC4506]. XDR está optimizado para el rendimiento en la red pero no es legible para humanos. Los SDKs de Stellar convierten los XDR en formatos más amigables.
-
-## .X files
-
-Las estructuras de datos en XDR se especifican en archivos `.x`. Estos archivos contienen _solo_ definiciones de estructuras de datos, sin operaciones ni código ejecutable. Los archivos `.x` para las estructuras XDR usadas en la Red Stellar están disponibles en [GitHub](https://github.com/stellar/stellar-xdr).
-
-:::tip
-
-Stellar XDR puede codificarse en JSON usando el esquema [XDR-JSON].
-
-:::
-
-## Más sobre XDR
-
-XDR es similar a herramientas como Protocol Buffers o Thrift. XDR ofrece algunas características importantes:
-
-- Es muy compacto, por lo que puede transmitirse rápidamente y almacenarse con un espacio mínimo en disco.
-- Los datos codificados en XDR se almacenan de forma fiable y predecible. Los campos siempre están en el mismo orden, lo que facilita la firma y verificación criptográfica de mensajes XDR.
-- Las definiciones XDR incluyen descripciones detalladas de tipos y estructuras de datos, lo cual no es posible en formatos más simples como JSON, TOML o YAML.
-
-## Analizando XDR
-
-Como XDR es un formato binario y no tan conocido como formatos más simples como JSON, los SDK de Stellar incluyen herramientas para analizar XDR y lo hacen automáticamente al recuperar datos.
-
-Los datos XDR aún se incluyen (codificados como una cadena base64) dentro del JSON por si necesitas acceso directo a ellos.
-
-## Profundizando en estructuras XDR
-
-Dado que el formato XDR es una base fundamental de la Red Stellar, a menudo es necesario profundizar en estas estructuras de datos binarios para que los clientes interactúen con transacciones y entradas de autorización. Puede ser complicado de entender por su estructura, pero esta sección pretende aclararte las formas de interactuar con él en varios lenguajes populares. El esquema del Protocolo se define en el repositorio [`stellar/stellar-xdr`](https://github.com/stellar/stellar-xdr/), aunque contiene mucho más de lo que necesitaremos para nuestros fines.
-
-### Formas comunes de XDR
-
-En el Protocolo Stellar, XDR adopta varias formas importantes de entender y distinguir:
-
-#### Primitivas básicas
-
-Son las más fáciles de entender para cualquiera familiarizado con un lenguaje de programación e incluyen enteros, cadenas y arreglos de bytes. Interaccionar con ellas es bastante sencillo, aunque las cosas pueden complicarse con los alias.
-
-Por ejemplo, tienes el alias `Uint64` en el Protocolo Stellar (definido en [Stellar-types.x](https://github.com/stellar/stellar-xdr/blob/70180d5e8d9caee9e8645ed8a38c36a8cf403cd9/Stellar-types.x#L14)), definido para mayor claridad en lugar del valor nativo "unsigned hyper" de XDR. Puedes usarlo justo como esperarías:
-
-```typescript
-import { xdr } from "@stellar/stellar-sdk";
-
-const u64 = new xdr.Uint64(12345678);
-```
-
-Algunas variantes del lenguaje permiten instanciarlo de varias formas. Por ejemplo, como los enteros de 64 bits son un poco... [complicados](https://stackoverflow.com/a/9643650) en JavaScript, también puedes inicializarlo con un [`BigInt`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt) o incluso una cadena:
-
-```typescript
-import { xdr } from "@stellar/stellar-sdk";
-
-let u64 = new xdr.Uint64("1_000_000_000_000_000");
-u64 = new xdr.Uint64(1_000_000_000_000_000n);
-```
-
-Puedes ver el conjunto completo de opciones para construir un `Uint64` en la definición de `UnsignedHyper` en la definición de TypeScript aquí: [curr.d.ts](https://github.com/stellar/js-stellar-base/blob/master/types/curr.d.ts#L127-L136). De hecho, este archivo debe ser tu guía principal para navegar el XDR si usas JavaScript.
-
-Otros lenguajes, como Python (ver la documentación [uint64.html](https://stellar-sdk.readthedocs.io/en/stable/_modules/stellar_sdk/xdr/uint64.html) de `stellar-sdk`), soportan enteros de tamaño arbitrario por defecto, sin tales variaciones:
-
-```python
-import xdr from stellar_sdk;
-
-u64 = xdr.Uint64(1_000_000_000_000_000)
-```
-
-Como resultado, muchas de las primitivas básicas pueden inicializarse de la forma "intuitiva" para tu lenguaje respectivo.
-
-#### Uniones
-
-Aquí las cosas se complican un poco más. Un _tipo unión_ es un tipo genérico que alterna entre diferentes "brazos", cada uno con un tipo interno distinto. Al analizar un tipo unión XDR, es importante determinar qué brazo se está usando antes de intentar analizar su contenido.
-
-Tomemos un [`SCAddress`](https://github.com/stellar/stellar-xdr/blob/70180d5e8d9caee9e8645ed8a38c36a8cf403cd9/Stellar-contract.x#L185-L191) como ejemplo. En la definición de tipo vemos que es o una cuenta (es decir, `SC_ADDRESS_TYPE_ACCOUNT`) o el hash de un contrato (`SC_ADDRESS_TYPE_CONTRACT`). Justo encima, ves que estos son constantes del enum `SCAddressType` definidas como 0 o 1, respectivamente.
-
-En general, las uniones siguen un patrón particular: cambiar según el tipo y coincidir con el valor enum apropiado. Así que cuando tienes una de estas uniones, debes determinar cuál es:
-
-<CodeExample>
-
-```typescript
-import { xdr } from "@stellar/stellar-sdk";
-import Buffer from "buffer";
-
-// suppose `scAddr` is an instance of `xdr.ScAddress` we're parsing
-switch (scAddr.switch()) {
-  case xdr.ScAddressType.scAddressTypeAccount().value:
-    console.log("The account is:", scAddr.accountId());
-    break;
-
-  case xdr.ScAddressType.scAddressTypeContract().value:
-    console.log("The contract is:", scAddr.contractId());
-    break;
-
-  default:
-    throw new Error(`Unexpected address type: ${scAddr.switch()}`);
-}
-```
-
-```python
-import SCAddressType, SCAddress from stellar_sdk.xdr.sc_address_type
-
-if scAddr.type == SCAddressType.SC_ADDRESS_TYPE_ACCOUNT:
-    print("The account is:", scAddr.account_id);
-    break
-
-elif scAddr.type == SCAddressType.SC_ADDRESS_TYPE_CONTRACT:
-    print("The contract is:", scAddr.contract_id);
-    break
-
-else:
-    raise Exception(f"Unexpected address type: {scAddr.type}")
-```
-
-</CodeExample>
-
-Puedes ver las referencias en la documentación ([Python](https://stellar-sdk.readthedocs.io/en/stable/api.html#scaddress) y [JavaScript](https://github.com/stellar/js-stellar-base/blob/master/types/curr.d.ts#L13881-L13886) respectivamente).
-
-Vale la pena notar que _podrías_ usar los constantes del enum definidos directamente, por ejemplo:
-
-```typescript
-import { xdr } from "@stellar/stellar-sdk";
-import Buffer from "buffer";
-
-// suppose `scAddr` is an instance of `xdr.ScAddress` we're parsing
-switch (scAddr.switch().value) {
-  case 0:
-    console.log("The account is:", scAddr.accountId());
-    break;
-
-  case 1:
-    console.log("The contract is:", scAddr.contractId());
-    break;
-
-  default:
-    throw new Error(`Unexpected address type: ${scAddr.switch()}`);
-}
-```
-
-Sin embargo, esto suele ser más propenso a errores y más difícil de leer. También puedes referirte a ellos por su _nombre_ (`.name` en JS y `str(...)` en Python): esto es un poco mejor para la legibilidad, pero peor para el rendimiento, pues haces comparaciones de cadenas. Es muy útil para registros, visualización para el usuario u otras tareas de depuración.
-
-Las uniones aparecen en _muchos_ lugares a lo largo del XDR y pueden ser un solo brazo o todo un _montón_ de brazos. Por ejemplo, el valor de **s**mart **c**ontract **val** `ScVal` tiene 22 valores posibles, ya que es la representación universal para un valor dentro de un contrato inteligente. Puedes ver todos ellos siendo inspeccionados en la utilidad JavaScript [`scValToNative`](https://stellar.github.io/js-stellar-sdk/js-stellar-base_src_scval.js.html#line279).
-
-Recuerda que XDR es el nivel más bajo de comunicación en la Red Stellar. Hablando en general, hay abstracciones de alto nivel que deberían ayudar con estas estructuras. Por ejemplo, la rutina de análisis vista es exactamente el propósito de las abstracciones [`Address.fromScAddress`](https://stellar.github.io/js-stellar-sdk/Address.html#.fromScAddress) y [`Address.from_xdr_sc_address`](https://stellar-sdk.readthedocs.io/en/stable/api.html#stellar_sdk.address.Address) en los SDKs de JavaScript y Python, respectivamente. Esto simplifica mucho tu código:
-
-<CodeExample>
-
-```typescript
-import { Address } from "@stellar/stellar-sdk";
-
-// suppose `scAddr` is an instance of `xdr.ScAddress` we're parsing
-const address = Address.fromScAddress(scAddr);
-```
-
-```python
-import Address from stellar_sdk;
-
-# suppose `scAddr` is an instance of `xdr.ScAddress` we're parsing
-addr = Address.from_xdr_sc_address(scAddr)
-```
-
-</CodeExample>
-
-Siempre intenta encontrar una abstracción de más alto nivel antes de profundizar en la estructura cruda.
-
-#### Estructuras
-
-Como en cualquier lenguaje tipo C, una estructura es un objeto compacto que contiene un conjunto de campos de tipos arbitrarios. Las estructuras pueden contener otras estructuras, así que asegúrate de recorrer todo el árbol de campos al construir una.
-
-Tomemos, por ejemplo, la estructura [`ContractEvent`](https://github.com/stellar/stellar-xdr/blob/c1a58e2f81a4d1b02adc6db9914e6f51960e1ce3/Stellar-ledger.x#L339-L358). Su definición es un poco complicada, así que la desglosaremos:
-
-- Un `ExtensionPoint` es una forma de extender el protocolo manteniendo compatibilidad binaria hacia atrás.
-
-Básicamente, es un espacio vacío en el que se pueden añadir variaciones en el futuro. La [estructura `SorobanTransactionMeta`](https://github.com/stellar/stellar-xdr/blob/c1a58e2f81a4d1b02adc6db9914e6f51960e1ce3/Stellar-ledger.x#L410) es un excelente ejemplo de esto en acción: cuando esta estructura se añadió inicialmente al protocolo, solo contenía detalles de una invocación (eventos y un valor de retorno). Después, se necesitaron más detalles sobre la invocación en los metadatos resultantes, así que `SorobanTransactionMetaExt` se inyectó en el `ExtensionPoint` con una variante [`V1`](https://github.com/stellar/stellar-xdr/blob/c1a58e2f81a4d1b02adc6db9914e6f51960e1ce3/Stellar-ledger.x#L368C8-L368C35) que contiene metadatos sobre las tarifas cobradas como resultado de la invocación.
-
-- El `contractID` debería ser autoexplicativo: es el hash del ID del contrato que causó este evento. Sin embargo, es un puntero, porque no todos los eventos están relacionados con un contrato específico. Algunos pueden provenir del sistema, diagnósticos, etc.
-
-No debería sorprender que el campo se almacene como un `Hash`: aunque en la capa del ecosistema nos referimos a los contratos por su "strkey" o representación en cadena (en la forma `C...`), en realidad son representaciones "más amigables" de un hash SHA-256 en bruto. Esto es común en la capa de protocolo: siempre se usará la representación más simple y compacta. Generalmente hay herramientas en el SDK para traducir estas a tipos más amigables para el usuario (como se muestra en el ejemplo a continuación).
-
-- El `ContractType` es esencialmente una forma de diferenciar qué campos en la estructura se espera que estén presentes y no merece mayor explicación.
-
-- Finalmente, tenemos el curioso campo unión `v`.
-
-A menudo verás uniones dentro de estructuras y viceversa. Si entiendes cómo se recorren individualmente, puedes manejarlas entrelazadas. Como demostración de cómo se hace esto con un SDK, incluso específicamente para esta estructura, podemos ver el código fuente del método auxiliar [`humanizeEvents`](https://stellar.github.io/js-stellar-sdk/global.html#humanizeEvents) en el SDK de JavaScript. Específicamente, revisaremos los detalles de la subrutina [`extractEvent`](https://stellar.github.io/js-stellar-sdk/js-stellar-base_src_events.js.html), replicada aquí para conveniencia:
-
-```js
-function extractEvent(event) {
-  return {
-    ...(typeof event.contractId === "function" &&
-      event.contractId() != null && {
-        contractId: StrKey.encodeContract(event.contractId()),
-      }),
-    type: event.type().name,
-    topics: event
-      .body()
-      .value()
-      .topics()
-      .map((t) => scValToNative(t)),
-    data: scValToNative(event.body().value().data()),
-  };
-}
-```
-
-En este ejemplo breve podemos ver muchas de las sutilezas que hemos discutido en esta guía en práctica:
-
-- Al diferenciar si `contractId` devuelve un valor o no (es un puntero, recuerda), decidimos si convertir el hash crudo en un ID de contrato compatible con el ecosistema.
-- Accedemos al campo `.name` del tipo de evento, que lo transforma en una cadena legible para humanos en lugar de una estructura opaca, como mencionamos en [Uniones](#uniones), antes.
-- Inspeccionamos _detenidamente_ el miembro `body` para extraer separadamente los campos `topics` y `data`, convirtiendo cada uno de esos `ScVal` opacos en equivalentes amigables para JavaScript.
-
-En la última parte, "abusamos" del hecho de que solo hay una variación del `body` union discutida: solo existe la versión inicial (un brazo con `v == 0`), así podemos usar el accesor `.value()` para obtener directamente el valor subyacente sin diferenciar los casos. Llamar `.v0()` sería equivalente, pero la ventaja aquí es que si se introduce una variación `v == 1` que _también_ tenga un arreglo `topics` y un campo `data` (es decir, que añade campos en lugar de cambiar la estructura v0), ¡este código seguirá funcionando!
-
-Hay muchos casos en los que diferentes brazos de la unión comparten estructura, y `.value()` te permite aprovechar eso.
-
----
-
-Esta visión general te debería dar una buena base para entender cómo inspeccionar XDR en tu SDK respectivo y profundizar en los campos que te interesan. Los detalles, por supuesto, dependerán del lenguaje, pero si comienzas por lo fundamental—los archivos [.x](#.x-files) en sí—obtendrás una comprensión de la estructura y deberías poder acceder a esa misma estructura directamente en tu lenguaje preferido, como mostramos aquí.
-
-{/* TODO: Espacio para expandir mucho más: Herramientas -> Visualización CLI, Visualización JSON, Stellar Lab */}
-
-[RFC4506]: http://tools.ietf.org/html/rfc4506.html
-[XDR-JSON]: ./xdr-json.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/fees-resource-limits-metering.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/fees-resource-limits-metering.mdx
deleted file mode 100644
index b21c94cdfb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/fees-resource-limits-metering.mdx
+++ /dev/null
@@ -1,218 +0,0 @@
----
-title: Comprender las tarifas, los límites de recursos y la medición para transacciones
-sidebar_label: Tarifas, límites de recursos y medición
-description: Aprende cómo funcionan las tarifas, los límites de recursos y la medición en la red Stellar. Entiende las estructuras de costos, la fijación de precios de transacciones y los límites de recursos de contratos inteligentes.
-sidebar_position: 70
----
-
-# Tarifas, Límites de Recursos y Medición
-
-## Resumen de tarifas
-
-Stellar requiere una tarifa por todas las transacciones para que lleguen al ledger. Esto ayuda a prevenir spam y prioriza las transacciones durante picos de tráfico. Todas las tarifas se pagan utilizando el token nativo de Stellar, el [lumen (o XLM)](./lumens.mdx).
-
-Hay dos tipos de tarifas en Stellar:
-
-**Tarifa de recursos: _aplica sólo a transacciones de contratos inteligentes_**. La cantidad que el remitente debe pagar por su transacción para ser ejecutada. Esta cantidad se basa en el consumo de recursos de una transacción y el estado del almacenamiento de la red (descrito en la [sección de precios dinámicos para almacenamiento](#dynamic-pricing-for-storage)). Lee sobre las tarifas de recursos [a continuación](#resource-fee).
-
-**Tarifa de inclusión:** el máximo que el remitente está dispuesto a pagar para que la transacción sea incluida en el ledger. Lee más [a continuación](#inclusion-fee).
-
-Al competir por espacio en el ledger, las transacciones de contratos inteligentes _sólo_ compiten con otras transacciones de contratos inteligentes, y las transacciones que no ejecutan un contrato inteligente _sólo_ compiten con otras transacciones que no ejecutan un contrato inteligente.
-
-Los lumens recolectados de las tarifas de transacción van a una cuenta bloqueada y no se entregan ni utilizan por nadie.
-
-## Tarifa de recursos
-
-Todas las transacciones de contratos inteligentes requieren una tarifa de recursos además de una tarifa de inclusión:
-
-`Tarifa de Transacción (Tx.fee) = Tarifa de Recursos (sorobanData.resourceFee) + Tarifa de Inclusión`
-
-Las transacciones que no ejecutan un contrato inteligente pueden entenderse como si tuvieran una tarifa de recursos de cero (`resourceFee == 0`). Por el contrario, para las transacciones de contratos inteligentes, puedes restar la tarifa de recursos de la tarifa total de la transacción para obtener el componente equivalente de la tarifa clásica, que es la tarifa de inclusión.
-
-![Tarifas de Soroban](/assets/diagrams/soroban_fees.png) _\* Diagrama: Las cajas de línea sólida son lo que realmente está presente en la transacción, mientras que las líneas punteadas son derivables._
-
-Los contratos inteligentes en Stellar utilizan un modelo de tarifa de recursos multidimensional que cobra tarifas por varios tipos de recursos utilizando [tarifas definidas por la red](../../networks/resource-limits-fees.mdx). La tarifa de recursos se calcula en función del consumo de recursos declarado en la transacción y puede fluctuar según una tarifa de escritura de almacenamiento mutable (más sobre eso en la [sección de precios dinámicos para almacenamiento](#dynamic-pricing-for-storage) a continuación). Si la transacción intenta exceder los límites de recursos declarados, fallará. Si la transacción utiliza menos recursos de los declarados, no habrá reembolsos [(con un par de excepciones)](#refundable-and-non-refundable-resource-fees).
-
-La tarifa de recursos depende de los siguientes recursos:
-
-- **Instrucciones:** el número de instrucciones CPU que utiliza la transacción, medida por el entorno host;
-- **Accesos a entradas del ledger:** leer o escribir cualquier entrada de ledger única (cualquier clave de almacenamiento en el contexto del contrato);
-- **I/O del ledger:** el número de bytes leídos o escritos en el ledger;
-- **Tamaño de la transacción:** el tamaño de la transacción enviada a la red en bytes;
-- **Tamaño de eventos y retorno de valor:** el tamaño de los eventos producidos por el contrato y el valor de retorno de la función del contrato de nivel superior — tanto los eventos como el valor de retorno se incluyen en los metadatos de la transacción;
-- **Alquiler del espacio del ledger:** el pago por las extensiones TTL de entradas del ledger (es decir, pagos de alquiler) y pagos de alquiler por aumentar el tamaño de la entrada del ledger. Consulta la sección de [archivado de estado](../fundamentals/contract-development/storage/state-archival.mdx) para obtener más información sobre el arrendamiento de contratos inteligentes.
-
-:::note
-
-Los detalles de implementación para el cálculo de tarifas son proporcionados por la siguiente [biblioteca](https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-host/src/fees.rs). Esta biblioteca es utilizada por el protocolo para calcular las tarifas y, por lo tanto, puede considerarse canónica. Las tarifas de recursos pueden ser actualizadas basadas en el consenso de los validadores de la red. Por ejemplo, el tamaño de la transacción se cobra por la propagación de la red (ya que el ancho de banda de la red es limitado) y por el almacenamiento histórico (ya que almacenar el historial del ledger no es gratis).
-
-:::
-
-Los detalles de implementación para el cálculo de tarifas son proporcionados por la siguiente [biblioteca](https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-host/src/fees.rs). Esta biblioteca es utilizada por el protocolo para calcular las tarifas y, por lo tanto, puede considerarse canónica. Las tarifas de recursos pueden ser actualizadas en base al consenso de los validadores de la red.
-
-Encuentra las tarifas de recursos actuales en la página de [Límites y Tarifas de Recursos](../../networks/resource-limits-fees.mdx) en la sección de Redes.
-
-Para ayuda en el análisis de costos y eficiencia de contratos inteligentes, consulta esta [Guía Práctica](../../build/guides/fees/analyzing-smart-contract-cost.mdx).
-
-### Tarifas de recursos reembolsables y no reembolsables
-
-La tarifa de recursos se calcula con una porción de tarifas no reembolsables y una porción de tarifas reembolsables: `ResourceFee(sorobanData.resourceFee) = Tarifa de recursos no reembolsable + Tarifas de recursos reembolsables`.
-
-**Tarifas no reembolsables:** calculadas a partir de instrucciones CPU, bytes leídos, bytes escritos y ancho de banda (tamaño de la transacción, incluyendo sus firmas).
-
-**Tarifas reembolsables:** calculadas a partir de alquiler, eventos y valor de retorno. Las tarifas reembolsables se cargan desde la cuenta fuente antes de que se ejecute la transacción y luego se reembolsan en función del uso real. Sin embargo, la transacción fallará si `refundableFee` no es suficiente para cubrir el uso real de recursos. Las tarifas reembolsables se cobran de la cuenta de origen antes de que se ejecute la transacción y luego se reembolsan según el uso real. Sin embargo, la transacción fallará si `refundableFee` no es suficiente para cubrir el uso real de recursos.
-
-### Encuentra la tarifa de recursos de una transacción
-
-La mejor forma de encontrar la tarifa de recursos necesaria para cualquier transacción de contrato inteligente es usar el [`simulateTransaction endpoint`](../fundamentals/contract-development/contract-interactions/transaction-simulation.mdx) del RPC, que te permite ejecutar en seco la transacción para calcular los valores de recursos y las tarifas necesarias.
-
-### Limitaciones de recursos
-
-:::note
-
-Sólo las transacciones de contratos inteligentes están sujetas a limitaciones de recursos.
-
-:::
-
-El tiempo de cierre del ledger de Stellar está limitado a unos pocos segundos, impidiendo la ejecución de transacciones arbitrariamente grandes, independientemente de las tarifas de recursos involucradas. Todos los recursos mencionados en la sección anterior están sujetos a un límite por transacción. La memoria (RAM) de una transacción también está limitada, aunque no está sujeta a ningún cargo.
-
-Los límites de recursos son determinados por una votación de validadores y pueden ser ajustados según el uso de la red y las necesidades del ecosistema con un consenso de validadores.
-
-Encuentra los límites de recursos actuales en la página de [Límites y Tarifas de Recursos](../../networks/resource-limits-fees.mdx) en la sección de Redes.
-
-## Tarifa de inclusión
-
-La tarifa de inclusión es la máxima oferta (una oferta denota una tarifa dinámica, lo que significa que varía según ciertas condiciones de la red) que el remitente está dispuesto a pagar para que la transacción sea incluida en el ledger. La tarifa de inclusión es igual al número de operaciones en la transacción multiplicado por la tarifa base efectiva para el ledger dado: `tarifa de inclusión = # de operaciones * tarifa base efectiva`
-
-**Tarifa base efectiva:** la tarifa requerida por operación para que una transacción llegue al ledger. Esto no puede ser menor de 100 stroops por operación (el mínimo de la red). Esto no puede ser inferior a 100 stroops por operación (el mínimo de la red).
-
-**Stroop:** la unidad más pequeña de un lumen, una diez millonésima parte de un lumen (.0000001 XLM).
-
-:::note
-
-Las transacciones pueden tener hasta 100 operaciones por transacción excepto para las transacciones que ejecutan un contrato inteligente. Las transacciones de smart contract solo permiten una operación por transacción (a menos que la transacción reciba un [fee-bump](../../build/guides/transactions/fee-bump-transactions.mdx); esto añadiría otra operación), y los límites se especifican en instrucciones de CPU y otros límites de recursos.
-
-:::
-
-Cuando estableces una tarifa base para una transacción, estás especificando el máximo que estás dispuesto a pagar por operación en esa transacción. Esto no significa necesariamente que pagarás esa cantidad. Sólo se te cobrará la menor cantidad necesaria para que tu transacción llegue al ledger. Si el tráfico de la red es ligero y el número de operaciones o transacciones enviadas está por debajo del límite del ledger de la red (configurado por los validadores: actualmente 1,000 operaciones que no son de contrato inteligente y 100 transacciones de contratos inteligentes), sólo pagarás el mínimo de la red (configurado por los validadores, actualmente 100 stroops).
-
-Alternativamente, tu transacción puede no llegar al ledger si la tarifa base efectiva es mayor que tu oferta de tarifa base. Cuando el tráfico de la red supera el límite del ledger, la red entra en [modo de precios de picos](#surge-pricing), y tu tarifa base efectiva se convierte en tu oferta máxima.
-
-Las tarifas se deducen de la cuenta fuente a menos que haya una transacción de incremento de tarifas que indique lo contrario. Aprende sobre las transacciones fee-bump en la [sección de Fee-Bump Transaction](../../build/guides/transactions/fee-bump-transactions.mdx).
-
-## Precios de picos y dinámicos
-
-### Precios de picos
-
-La red puede entrar en modo de precios de picos bajo dos circunstancias: 1. cuando el número de operaciones sometidas a un ledger excede la capacidad de la red (1,000 operaciones para transacciones que no ejecutan contratos inteligentes), o 1. si hay competencia entre transacciones de contratos inteligentes por un recurso particular (instrucciones, accesos a entradas del ledger (lecturas y escrituras), I/O del ledger (bytes leídos y bytes escritos), y el tamaño total de las transacciones a aplicar). Durante este tiempo, la red utiliza dinámicas de mercado para decidir qué transacciones incluir en el ledger. Durante el modo de precios de picos, las transacciones se ordenan según su monto de tarifa de inclusión, y el usuario paga la tarifa de inclusión mínima en su conjunto de transacciones.
-
-Durante el modo de precios de picos, las transacciones se ordenan según la cantidad de su tarifa de inclusión, y el usuario paga la tarifa de inclusión mínima en su conjunto de transacciones. Por ejemplo, si hay cinco transacciones con tarifas de inclusión respectivas de 2, 3, 4, 4 y 5 XLM, y sólo cuatro de ellas pueden llegar al ledger, entonces todas las transacciones incluidas pagan la tarifa de inclusión de 3 XLM. Si las cinco transacciones pueden llegar al ledger (lo que significaría que la red no está en modo de precios de sobrecarga), cada una pagaría la tarifa mínima de inclusión de 100 stroops (.00001 XLM).
-
-Si hay múltiples transacciones ofreciendo la misma tarifa de inclusión, pero no pueden todas caber en el ledger, las transacciones se eligen al azar para que el total de operaciones para el conjunto completo no exceda 1,000. Las demás transacciones se empujan al siguiente ledger o se descartan si han estado esperando demasiado tiempo. Si tu transacción es descartada, nunca aparecerá en un libro mayor recuperado desde RPC.
-
-:::note
-
-Se recomienda aplicar [límites de ledger](./transactions/operations-and-transactions.mdx#ledger-bounds) o [límites de tiempo](./transactions/operations-and-transactions.mdx#time-bounds) a las transacciones — ya sea que tu transacción llegue al ledger o falle, dependiendo de tus parámetros de tiempo y/o ledger.
-
-:::
-
-**Es más probable que pagues una tarifa de inclusión más alta al enviar transacciones de contratos inteligentes.** Las transacciones de contratos inteligentes tienen límites de ledger más estrictos que las transacciones que no interactúan con contratos inteligentes y, por lo tanto, experimentarán precios de picos más a menudo. Es más probable que pagues tu oferta máxima de tarifa de inclusión o, al menos, la oferta mínima de tarifa de inclusión en tu conjunto de transacciones. Por lo tanto, debes planear tu estrategia de oferta de tarifas en consecuencia.
-
-### Precios dinámicos para almacenamiento
-
-El tamaño de la base de datos de almacenamiento de Stellar está determinado por dos fuerzas: la tasa de adiciones (escrituras) y la tasa de eliminaciones (desalojos). Stellar ha establecido un umbral de crecimiento del ledger a un valor constante (el parámetro de red `BucketListTargetSizeBytes`, implementado para prevenir el crecimiento explosivo de estado y sujeto a cambios basado en la votación de validadores). Debido a que hay una capacidad fija, las tarifas de escritura se basan en el tamaño del ledger y pueden cambiar dinámicamente según ese tamaño.
-
-Cuando el tamaño del ledger es grande, hay una mayor demanda de espacio de almacenamiento, lo que provoca una mayor tarifa de escritura. Con el tiempo, las entradas se archivan, reduciendo el tamaño total del ledger y, por ende, reduciendo el precio de almacenamiento. Este modelo de tarifas está diseñado como si el tamaño de la base de datos representara la demanda actual de almacenamiento en cualquier instante dado.
-
-Las tarifas de escritura crecerán gradualmente con el tiempo cuando el tamaño de la base de datos esté por debajo del umbral de crecimiento del ledger y crecerán linealmente, pero con un factor de 1,000x después de superar ese umbral. Esto es una salvaguarda contra el spam y no se anticipa en circunstancias normales.
-
-## Medición
-
-La medición es un mecanismo en el entorno host que contabiliza los costos de recursos incurridos durante la ejecución de un contrato inteligente. Los resultados de la medición actúan como la verdad canónica del costo de ejecución de un contrato inteligente y sirven como entrada para los cálculos de tarifas.
-
-El entorno de ejecución de contratos inteligentes de Stellar comprende un host y un invitado. El host encapsula funcionalidades compartidas para todos los contratos, incluyendo objetos del host, funciones y un intérprete de Wasm (VM). El entorno del invitado es donde se interpreta y ejecuta el contrato Wasm compilado. Un análisis detallado de estos entornos se encuentra en [Conceptos de entorno](../fundamentals/contract-development/environment-concepts.mdx).
-
-La división entre los entornos host y del invitado y sus funcionalidades compartidas requiere un enfoque único para la contabilidad de recursos. En particular, los recursos requeridos para ejecutar instrucciones Wasm y ejecutar funciones del host deben contabilizarse uniformemente, con costos en términos de instrucciones CPU y bytes de memoria.
-
-Considera dos contratos: A y B, ambos que comprenden el mismo número de instrucciones Wasm. Si el Contrato A llama repetidamente a funciones del host para cálculos complejos mientras que el Contrato B ejecuta operaciones aritméticas puras dentro de la VM, el Contrato A debería ser más costoso, y esta diferencia debería ser representada con precisión en el proceso de medición.
-
-La medición asegura equidad, impide la manipulación de recursos y ataques, y genera una medida determinista y reproducible de los costos de recursos en tiempo de ejecución.
-
-### Metodología
-
-Para mantener la equivalencia en la medición entre el host y el invitado, los costos de computación en ambos lados se expresan en términos de instrucciones CPU y bytes de memoria (representando el uso de CPU y RAM). La medición y la verificación de límites ocurren dentro del entorno host, y modelos numéricos pre-calibrados aseguran que los resultados sean deterministas.
-
-### Tipos de costo
-
-La medición se segmenta en componentes del host, conocidos como **tipos de costo**. Cada tipo de costo se puede ver como una “meta instrucción” que simboliza una operación específica del host con una complejidad conocida que depende de una entrada en tiempo de ejecución. Por ejemplo, el tipo de costo `ComputeSha256Hash` representa el costo de calcular el hash SHA256 de un array de bytes.
-
-:::info
-
-La ejecución de instrucciones Wasm se contabiliza como un tipo de costo del host `WasmInsnExec`, que tiene un costo CPU constante por instrucción Wasm. Esta metodología trata las instrucciones del invitado y las ejecuciones del host de manera equivalente.
-
-:::
-
-Encuentra una lista completa de tipos de costo del host y sus definiciones aquí: [`ContractCostType`](https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-contract-config-setting.x#L92-L155).
-
-### Parámetros de costo
-
-Los tipos de costo son cuidadosamente seleccionados para:
-
-1. Servir como bloques de construcción integrales para todos los costos significativos de ejecución de contratos;
-2. Asegurar que cada costo componente incremente como máximo linealmente (es decir, constante o lineal) con respecto a su entrada. Es decir, `y = a + bx`, donde `y` es la salida de costo, `x` es la entrada, y `a` y `b` son los parámetros del modelo constante y lineal, respectivamente.
-
-Cada tipo de costo tiene un modelo separado para ambos tipos de recursos (CPU y memoria).
-
-Los parámetros para cada modelo, `a` y `b`, son calibrados y ajustados fuera de línea contra entradas de varios tamaños. La colección de todos los parámetros de costo de modelo de las entradas configurables de la red (ver [`ConfigSettingsEntry`](https://github.com/stellar/stellar-xdr/blob/e372df9f677961aac04c5a4cc80a3667f310b29f/Stellar-contract-config-setting.x#L223-L226) puede actualizarse a través del consenso de la red.
-
-### Proceso de medición
-
-Antes de la ejecución del contrato, el entorno host se prepara con los parámetros de costo y un presupuesto que define los límites de recursos. La medición se implementa entonces para medir el consumo acumulado de recursos durante la ejecución del host.
-
-Durante la ejecución, cada vez que se encuentra un componente (un bloque de código que define un tipo de costo), el modelo correspondiente calcula la salida de recursos a partir de la entrada en tiempo de ejecución y aumenta el medidor en consecuencia. El medidor verifica el consumo acumulativo contra el límite del presupuesto. Si se supera el límite, se produce un error y la ejecución se termina.
-
-Si la ejecución del contrato concluye dentro de los límites de recursos especificados, el total medido de instrucciones CPU se registra y se utiliza como entrada para el cálculo de tarifas. Mientras que el uso de memoria no se incluye en el cálculo de tarifas, sigue estando sujeto a los límites de recursos.
-
-## Estrategias de precios de tarifas de inclusión
-
-Hay dos métodos principales para tratar las fluctuaciones de tarifas de inclusión y precios de picos:
-
-- [**Método 1:**](#set-the-highest-fee-youre-comfortable-paying) establece la tarifa más alta que estés dispuesto a pagar. Esto no significa que pagarás esa cantidad en cada transacción — solo pagarás lo que sea necesario para entrar en el ledger. En circunstancias normales (no de picos), solo pagarás la tarifa estándar incluso con una tarifa máxima más alta establecida. Este método es simple, conveniente y eficiente, pero aún puede fallar.
-- [**Método 2:**](#fee-bumps-on-past-transactions) reenvía una transacción con una tarifa más alta usando una transacción de aumento de tarifas
-
-### Establece la tarifa más alta que estés dispuesto a pagar​
-
-En general, es una buena idea elegir la tarifa más alta que estás dispuesto a pagar por operación para que tu transacción llegue al ledger. Los desarrolladores de billeteras pueden querer ofrecer a los usuarios la oportunidad de especificar su propia tarifa base, aunque puede tener más sentido establecer una tarifa base global persistente que esté por encima de la tarifa de mercado, ya que el usuario promedio probablemente no se preocupe si está pagando 0.8 céntimos o 0.00008 céntimos.
-
-Recuerda que es más probable que pagues tu oferta máxima de tarifa con transacciones de contratos inteligentes.
-
-### Aumentos de tarifas en transacciones pasadas​
-
-Incluso con una política liberal de pago de tarifas, tu transacción puede fallar al llegar al ledger debido a fondos insuficientes o aumentos de tarifas intempestivos. Las transacciones de aumento de tarifas pueden resolver este problema. El siguiente fragmento te muestra cómo reenviar una transacción con una tarifa más alta (siempre que tengas el sobre de transacción original):
-
-<CodeExample>
-
-```js
-// Let `lastTx` be some transaction that fails submission due to high fees, and
-// `lastFee` be the maximum fee (expressed as an int) willing to be paid by
-// `account` for `lastTx`.
-server.submitTransaction(lastTx).catch(function (error) {
-  if (isFeeError(error)) {
-    let bump = sdk.TransactionBuilder.buildFeeBumpTransaction(
-      account,      // account that will PAY the new fee
-      lastFee * 10, // new fee
-      lastTx,       // the (entire) failing transaction
-      server.networkPassphrase
-    );
-    bump.sign(someAccount);
-    return server.submitTransaction(bump);
-  }
-  // ...other error conditions...
-}).then(...);
-```
-
-</CodeExample>
-
-Supón que envías dos transacciones distintas con la misma cuenta fuente y número de secuencia; la segunda transacción es una transacción de aumento de tarifas. En ese caso, la segunda transacción será incluida en la cola de transacciones, reemplazando la primera transacción si y solo si la oferta de tarifa de la segunda transacción es al menos 10 veces la oferta de tarifa de la primera transacción.
-
-Este valor se puede encontrar típicamente en el campo `fee_charged` de la respuesta de la transacción bajo el caso de error `tx_insufficient_fee`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx
deleted file mode 100644
index b4daa6be82..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx
+++ /dev/null
@@ -1,623 +0,0 @@
----
-title: "Fondos de Liquidez en el Stellar DEX: Proporcionar Liquidez y Permitir Intercambios de Activos"
-sidebar_label: SDEX
-description: Aprende cómo los fondos de liquidez permiten el trading en el Stellar DEX. Comprende cómo funcionan, proporciona liquidez y permite intercambios descentralizados de activos en la red.
-sidebar_position: 100
----
-
-# Liquidez en Stellar: SDEX y Fondos de Liquidez
-
-:::note
-
-Esta sección se enfoca específicamente en la liquidez relacionada con el AMM y el SDEX desarrollados en el protocolo Stellar y no incluye información sobre contratos inteligentes.
-
-:::
-
-Los usuarios pueden comerciar y convertir activos en la red Stellar mediante pagos por rutas a través del exchange descentralizado Stellar y los fondos de liquidez.
-
-En esta sección hablaremos sobre el SDEX y los fondos de liquidez. Para aprender cómo funcionan juntos para ejecutar transacciones, consulta nuestra [Guía de Pagos por Rutas](../../build/guides/transactions/path-payments.mdx).
-
-## SDEX
-
-La red Stellar funciona como un exchange distribuido descentralizado que permite a los usuarios comerciar y convertir activos con las operaciones [Manage Buy Offer](./transactions/list-of-operations#manage-buy-offer) y [Manage Sell Offer](./transactions/list-of-operations#manage-sell-offer). El ledger de Stellar almacena tanto los saldos de las cuentas de usuario como las órdenes que estas cuentas hacen para comprar o vender activos.
-
-### Libro de órdenes
-
-Stellar utiliza libros de órdenes para operar su exchange descentralizado.
-
-Un libro de órdenes es un registro de órdenes pendientes en una red, y cada registro se sitúa entre dos activos (trigo y ovejas, por ejemplo). El libro de órdenes de este par de activos registra cada cuenta que quiere vender trigo por ovejas y cada cuenta que quiere vender ovejas por trigo. En finanzas tradicionales, comprar se expresa como una orden de “compra” (bid), y vender se expresa como una orden de “venta” (ask) (las órdenes ask también se llaman ofertas).
-
-Un par de notas sobre los libros de órdenes en Stellar:
-
-- El término “ofertas” generalmente se refiere específicamente a las órdenes ask. Sin embargo, en Stellar, todas las órdenes se almacenan como órdenes de venta, es decir, el sistema convierte automáticamente las órdenes de compra en órdenes ask. Por eso, los términos “oferta” y “orden” se usan indistintamente en el ecosistema Stellar.
-- Los libros de órdenes contienen todas las órdenes aceptables para las partes de cualquiera de los lados para realizar una operación.
-- Algunos activos tendrán un libro de órdenes pequeño o inexistente entre ellos. En estos casos, Stellar facilita pagos por rutas, que discutiremos más adelante.
-
-Para ver un gráfico de libro de órdenes, consulta la [página de Wikipedia sobre libros de órdenes](https://en.wikipedia.org/wiki/Order_book). Además, hay muchos tutoriales en vídeo y artículos que pueden ayudarte a entender en mayor detalle cómo funcionan los libros de órdenes.
-
-### Órdenes
-
-Una cuenta puede crear órdenes para comprar o vender activos usando las operaciones Gestionar oferta de compra, Gestionar oferta de venta u Orden pasiva. La cuenta debe tener el activo que desea exchangear, y debe confiar en el emisor del activo que está intentando comprar.
-
-Las órdenes en Stellar funcionan como órdenes límite en mercados tradicionales. Cuando una cuenta inicia una orden, esta se verifica contra el libro de órdenes existente para ese par de activos. Si la orden enviada es una orden marketable (para una orden límite de compra marketable, el precio límite está en o por encima del precio ask; para una orden límite de venta marketable, el precio límite está en o por debajo del precio bid), se cumple al precio existente de la orden para la cantidad disponible a ese precio. Si la orden no es marketable (es decir, no cruza una orden existente), la orden se guarda en el libro de órdenes hasta que sea consumida por otra orden, consumida por un pago por ruta, o cancelada por la cuenta que creó la orden.
-
-Cada orden constituye una obligación de venta para el activo que se vende y una obligación de compra para el activo que se compra. Estas obligaciones se almacenan en la cuenta (para lumens) o en la trustline (para otros activos) propiedad de la cuenta que crea la orden. Cualquier operación que cause que una cuenta no pueda cumplir con sus obligaciones — como enviar un saldo demasiado alto — fallará. Esto garantiza que cualquier orden en el libro de órdenes pueda ejecutarse en su totalidad.
-
-Las órdenes se ejecutan con prioridad precio-tiempo, lo que significa que las órdenes se ejecutan primero según el precio; para órdenes colocadas al mismo precio, se da prioridad a la orden que se ingresó antes y se ejecuta antes que la más reciente.
-
-### Precio y operaciones
-
-Cada orden en Stellar se cotiza con un precio asociado y está representada como una proporción de los dos activos en la orden, siendo uno el “activo cotizado” y el otro el “activo base”. Esto asegura que no haya pérdida de precisión al representar el precio de la orden (en lugar de almacenar la fracción como un número de punto flotante).
-
-Los precios se especifican como un par {`numerador`, `denominador`} con ambos componentes de la fracción representados como enteros con signo de 32 bits. El numerador se considera el activo base, y el denominador se considera el activo cotizado. Al expresar un precio de “Activo A en términos de Activo B”, la cantidad de B es el denominador (y por tanto el activo cotizado), y A es el numerador (y por tanto el activo base). Por regla general, es correcto pensar en el activo base que se está comprando/vendiendo (en términos del activo cotizado).
-
-#### Gestionar oferta de compra
-
-Al crear una orden de compra en Stellar mediante la operación Gestionar oferta de compra, el precio se especifica como 1 unidad de la moneda base (el activo que se compra), en términos del activo cotizado (el activo que se vende). Por ejemplo, si compras 100 XLM a cambio de 20 USD, especificarías el precio como {20, 100}, que equivale a 5 XLM por 1 USD (o \$.20 por XLM).
-
-#### Gestionar oferta de venta
-
-Al crear una orden de venta en Stellar mediante la operación Gestionar oferta de venta, el precio se especifica como 1 unidad de la moneda base (el activo que se vende), en términos del activo cotizado (el activo que se compra). Por ejemplo, si vendes 100 XLM a cambio de 40 USD, especificarías el precio como {40, 100}, que equivale a 2.5 XLM por 1 USD (o \$.40 por XLM).
-
-#### Orden pasiva
-
-Las órdenes pasivas permiten que los mercados tengan un spread cero. Si quieres exchangear USD de anchor A por USD de anchor B a un precio 1:1, puedes crear dos órdenes pasivas para que las dos órdenes no se ejecuten entre sí.
-
-Una orden pasiva es una orden que no se ejecuta contra una orden contraria marketable con el mismo precio. Solo se ejecutará si los precios no son iguales. Por ejemplo, si la mejor orden para comprar BTC por XLM tiene un precio de 100XLM/BTC, y haces una oferta pasiva para vender BTC a 100XLM/BTC, tu oferta pasiva no toma esa oferta existente. Si en cambio haces una oferta pasiva para vender BTC a 99XLM/BTC, cruzaría la oferta existente y se ejecutaría a 100XLM/BTC.
-
-Una cuenta puede colocar una orden de venta pasiva mediante la operación Crear oferta pasiva de venta.
-
-### Comisiones
-
-El precio de la orden que estableces es independiente de la comisión que pagas por enviar esa orden en una transacción. Las comisiones siempre se pagan en XLM, y las especificas como un parámetro separado al enviar la orden a la red.
-
-Para saber más sobre tarifas de transacción, consulta nuestra sección sobre [tarifas](./fees-resource-limits-metering.mdx).
-
-## Fondos de Liquidez
-
-Los Fondos de Liquidez permiten la creación automática de mercados en la red Stellar. La liquidez se refiere a la facilidad y eficiencia con que un activo puede ser convertido en otro.
-
-### Creadores de Mercado Automatizados (AMMs)
-
-En lugar de depender de las órdenes de compra y venta de los exchanges descentralizados, los AMMs mantienen activos líquidos dentro del ecosistema 24/7 usando fondos de liquidez.
-
-Los creadores de mercado automatizados proporcionan liquidez usando una ecuación matemática. Los AMMs retienen dos activos diferentes en un fondo de liquidez, y las cantidades de esos activos (o reservas) son entradas para esa ecuación (Activo A \* Activo B = k). Si un AMM tiene más reservas de los activos, los precios de activos se mueven menos en respuesta a una operación.
-
-#### Fijación de precios en AMM
-
-Los AMMs están dispuestos a hacer algunas operaciones y no a hacer otras. Por ejemplo, si 1 EUR = 1.17 USD, entonces el AMM podría estar dispuesto a vender 1 EUR por 1.18 USD y no dispuesto a vender 1 EUR por 1.16 USD. Para determinar qué operaciones son aceptables, el AMM aplica un invariante. Existen muchos invariantes posibles, y Stellar aplica un invariante de producto constante y por eso es conocido como un creador de mercado de producto constante. Esto significa que los AMMs en Stellar nunca deben permitir que el producto de las reservas disminuya.
-
-Por ejemplo, supón que las reservas actuales en el fondo de liquidez son 1000 EUR y 1170 USD, lo que implica un producto de 1,170,000. Vender 1 EUR por 1.18 USD sería aceptable porque dejaría reservas de 999 EUR y 1171.18 USD, lo que implica un producto de 1,170,008.82. Pero vender 1 EUR por 1.16 USD no sería aceptable porque dejaría reservas de 999 EUR y 1171.16 USD, lo que implica un producto de 1,169,988.84.
-
-Los AMMs deciden tasas de exchange basándose en la proporción de reservas en el fondo de liquidez. Si esta proporción es diferente de la tasa de exchange verdadera, los arbitrajistas entrarán y tradearán con el AMM a un precio favorable. Esta operación de arbitraje mueve la proporción de reservas de vuelta hacia la tasa de exchange verdadera.
-
-Los AMMs cobran comisiones en cada operación, que es un porcentaje fijo de la cantidad comprada por el AMM. Por ejemplo, si un creador de mercado automatizado vende 100 EUR por 118 USD, la comisión se cobra sobre los USD. La comisión es de 30 bps, que equivale a 0.30%. Si realmente quisieras hacer esta operación, tendrías que pagar aproximadamente 118.355 USD por 100 EUR. El creador de mercado automatizado incorpora las comisiones en el invariante de producto constante, por lo que en realidad, el producto de las reservas crece después de cada operación.
-
-### Participación en fondos de liquidez
-
-Cualquier participante elegible puede depositar activos en un fondo de liquidez y, a cambio, recibir participaciones del fondo que representan su propiedad sobre ese activo. Si hay 150 participaciones totales en el fondo y un usuario posee 30, tiene derecho a retirar el 20% del activo del fondo en cualquier momento.
-
-Las participaciones del fondo son similares a otros activos en Stellar, pero no pueden transferirse. Solo puedes aumentar el número de participaciones que posees depositando en un fondo de liquidez con `LiquidityPoolDepositOp` y disminuir el número de participaciones retirando del fondo con `LiquidityPoolWithdrawOp`.
-
-Una participación del fondo tiene dos representaciones. La representación completa se usa con `ChangeTrustOp`, y la representación en hash se usa en todos los demás casos. Al construir la representación del activo de una participación del fondo, los activos deben estar en orden lexicográfico. Por ejemplo, A-B está en el orden correcto, pero B-A no. Esto resulta en una representación canónica de una participación del fondo.
-
-Los AMMs cobran una comisión en todas las operaciones y los participantes en el fondo de liquidez reciben una parte proporcional de la comisión según su participación en los activos del fondo. Los participantes recogen estas comisiones cuando retiran sus activos del fondo. La tasa de comisión en Stellar es de 30 bps, que equivale a 0.30%. Estas comisiones son completamente independientes de las comisiones de la red.
-
-### Trustlines
-
-Los usuarios necesitan establecer trustlines a tres activos diferentes para participar en un fondo de liquidez: ambos activos de reserva (a menos que uno de ellos sea XLM) y la participación del fondo en sí.
-
-Una cuenta necesita una trustline para cada participación del fondo que quiera poseer. No es posible depositar en un fondo de liquidez sin una trustline para la participación del fondo correspondiente. Las trustlines de participaciones de fondos difieren de las trustlines de otros activos en algunos aspectos:
-
-1. Una trustline de participación de fondo no puede ser creada a menos que la cuenta ya tenga trustlines que estén autorizadas o autorizadas para mantener responsabilidades para los activos en el fondo de liquidez. Consulta más abajo para información adicional sobre cómo la autorización impacta las trustlines de participaciones de fondos.
-2. Una trustline de participación de fondo requiere 2 reservas base en lugar de 1. Por ejemplo, una cuenta (2 reservas base) con una trustline para el activo A (1 reserva base), una trustline para el activo B (1 reserva base), y una trustline para la participación A-B del fondo (2 reservas base) tendría un requerimiento de reservas de 6 reservas base.
-
-### Autorización
-
-Las trustlines de participaciones de fondo no pueden autorizarse o desautorizarse de forma independiente. En cambio, la autorización de una trustline de participación de fondo se deriva de las trustlines para los activos en el fondo de liquidez. Este diseño es necesario porque un fondo de liquidez puede contener activos de dos emisores diferentes, y ambos emisores deben tener voz para decidir si la trustline de participación del fondo está autorizada.
-
-Hay varias posibilidades respecto a la autorización. El comportamiento de la trustline de participación A-B se determina según la siguiente tabla:
-
-| ESCENARIO                                                                                                               | COMPORTAMIENTO                                                              |
-| ----------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
-| Las trustlines para A y B están totalmente autorizadas                                                                  | Sin restricciones para depósito y retirada de fondos                        |
-| La trustline para A está totalmente autorizada pero la trustline para B está autorizada para mantener responsabilidades | Las trustlines para A y B están autorizadas para mantener responsabilidades |
-| La trustline para B está totalmente autorizada pero la trustline para A está autorizada para mantener responsabilidades | Las trustlines para A y B están autorizadas para mantener responsabilidades |
-| Las trustlines para A y B están autorizadas para mantener pasivos                                                       | Las trustlines para A y B están autorizadas para mantener pasivos           |
-| La trustline para A no está autorizada o no existe                                                                      | La trustline de participación del fondo no existe                           |
-| La trustline para B no está autorizada o no existe                                                                      | La trustline de participación del fondo no existe                           |
-
-Si el emisor de A o B revoca la autorización, entonces la cuenta retirará automáticamente de todos los fondos de liquidez que contengan ese activo y esas trustlines de participación serán eliminadas. Decimos que estas participaciones han sido redimidas. Por ejemplo, si la cuenta participa en los fondos A-B, A-C y B-C, y el emisor de A revoca la autorización, la cuenta redimirá en A-B y A-C pero no en B-C. Para cada trustline de participación redimida, se creará un Balance Reclamable para cada activo contenido en el fondo si hay un saldo a retirar y el redimidor no es el emisor de ese activo. El reclamante del Balance Reclamable será el propietario de la trustline de participación eliminada, y el patrocinador del Balance Reclamable será el patrocinador de la trustline de participación eliminada. El BalanceID de cada Balance Reclamable es el hash SHA-256 del `revokeID`.
-
-### Operaciones
-
-Existen dos operaciones que facilitan la participación en un fondo de liquidez: `LiquidityPoolDeposit` y `LiquidityPoolWithdraw`. Usa `LiquidityPoolDeposit` para empezar a proveer liquidez al mercado. Usa `LiquidityPoolWithdraw` para dejar de proveer liquidez al mercado.
-
-Sin embargo, los usuarios no necesitan participar en el fondo para aprovechar lo que ofrece: una forma fácil de exchangear dos activos. Para eso, solo utiliza `PathPaymentStrictReceive` o `PathPaymentStrictSend`. Si tu aplicación ya está usando pagos por rutas, entonces no necesitas cambiar nada para que los usuarios aprovechen los precios disponibles en los fondos de liquidez.
-
-### Ejemplos
-
-Aquí cubriremos la participación básica en fondos de liquidez y cómo consultarlos.
-
-#### Preámbulo
-
-Para todos los siguientes ejemplos, trabajaremos con tres cuentas de Testnet con fondos. Si quieres seguir el ejemplo, genera algunos keypairs y fínáncialos mediante el friendbot.
-
-El siguiente código prepara las cuentas y define algunas funciones auxiliares. Estas deberían ser familiares si has probado otros ejemplos como clawbacks.
-
-<CodeExample>
-
-```js
-const sdk = require("stellar-sdk");
-const BigNumber = require("bignumber.js");
-
-let server = new sdk.Server("https://horizon-testnet.stellar.org");
-
-/// Helps simplify creating & signing a transaction.
-function buildTx(source, signer, ...ops) {
-  let tx = new sdk.TransactionBuilder(source, {
-    fee: sdk.BASE_FEE,
-    networkPassphrase: sdk.Networks.TESTNET,
-  });
-  ops.forEach((op) => tx.addOperation(op));
-  tx = tx.setTimeout(30).build();
-  tx.sign(signer);
-  return tx;
-}
-
-/// Returns the given asset pair in "protocol order."
-function orderAssets(A, B) {
-  return sdk.Asset.compare(A, B) <= 0 ? [A, B] : [B, A];
-}
-
-/// Returns all of the accounts we'll be using.
-function getAccounts() {
-  return Promise.all(kps.map((kp) => server.loadAccount(kp.publicKey())));
-}
-
-const kps = [
-  "SBGCD73TK2PTW2DQNWUYZSTCTHHVJPL4GZF3GVZMCDL6GYETYNAYOADN",
-  "SAAQFHI2FMSIC6OFPWZ3PDIIX3OF64RS3EB52VLYYZBX6GYB54TW3Q4U",
-  "SCJWYFTBDMDPAABHVJZE3DRMBRTEH4AIC5YUM54QGW57NUBM2XX6433P",
-].map((s) => sdk.Keypair.fromSecret(s));
-
-// kp0 issues the assets
-const kp0 = kps[0];
-const [A, B] = orderAssets(
-  ...[new sdk.Asset("A", kp0.publicKey()), new sdk.Asset("B", kp0.publicKey())],
-);
-
-/// Establishes trustlines and funds `recipientKps` for all `assets`.
-function distributeAssets(issuerKp, recipientKps, ...assets) {
-  return server.loadAccount(issuerKp.publicKey()).then((issuer) => {
-    const ops = recipientKps
-      .map((recipientKp) =>
-        assets.map((asset) => [
-          sdk.Operation.changeTrust({
-            source: recipientKp.publicKey(),
-            limit: "100000",
-            asset: asset,
-          }),
-          sdk.Operation.payment({
-            source: issuerKp.publicKey(),
-            destination: recipientKp.publicKey(),
-            amount: "100000",
-            asset: asset,
-          }),
-        ]),
-      )
-      .flat(2);
-
-    let tx = buildTx(issuer, issuerKp, ...ops);
-    tx.sign(...recipientKps);
-    return server.submitTransaction(tx);
-  });
-}
-
-function preamble() {
-  return distributeAssets(kp0, [kps[1], kps[2]], A, B);
-}
-```
-
-```python
-from decimal import Decimal
-from typing import List, Any, Dict
-
-from stellar_sdk import *
-
-server = Server("https://horizon-testnet.stellar.org")
-
-
-# Preamble
-def new_tx_builder(source: str) -> TransactionBuilder:
-    network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-    base_fee = 100
-    source_account = server.load_account(source)
-    builder = TransactionBuilder(
-        source_account=source_account, network_passphrase=network_passphrase, base_fee=base_fee
-    ).set_timeout(30)
-    return builder
-
-
-# Returns the given asset pair in "protocol order."
-def order_asset(a: Asset, b: Asset) -> List[Asset]:
-    return [a, b] if LiquidityPoolAsset.is_valid_lexicographic_order(a, b) else [b, a]
-
-
-secrets = [
-    "SBGCD73TK2PTW2DQNWUYZSTCTHHVJPL4GZF3GVZMCDL6GYETYNAYOADN",
-    "SAAQFHI2FMSIC6OFPWZ3PDIIX3OF64RS3EB52VLYYZBX6GYB54TW3Q4U",
-    "SCJWYFTBDMDPAABHVJZE3DRMBRTEH4AIC5YUM54QGW57NUBM2XX6433P",
-]
-kps = [Keypair.from_secret(secret=secret) for secret in secrets]
-
-# kp0 issues the assets
-kp0 = kps[0]
-asset_a, asset_b = order_asset(Asset("A", kp0.public_key), Asset("B", kp0.public_key))
-
-
-def distribute_assets(
-        issuer_kp: Keypair, recipient_kp: Keypair, assets: List[Asset]
-) -> Dict[str, Any]:
-    builder = new_tx_builder(issuer_kp.public_key)
-    for asset in assets:
-        builder.append_change_trust_op(
-            asset=asset, limit="100000", source=recipient_kp.public_key
-        ).append_payment_op(
-            destination=recipient_kp.public_key,
-            asset=asset,
-            amount="100000",
-            source=issuer_kp.public_key,
-        )
-
-    tx = builder.build()
-    tx.sign(issuer_kp)
-    tx.sign(recipient_kp)
-    resp = server.submit_transaction(tx)
-    return resp
-
-
-def preamble() -> None:
-    resp1 = distribute_assets(kp0, kps[1], [asset_a, asset_b])
-    resp2 = distribute_assets(kp0, kps[2], [asset_a, asset_b])
-    # ...
-```
-
-</CodeExample>
-
-Aquí usamos `distributeAssets()` para establecer trustlines y configurar saldos iniciales de dos activos personalizados (`A` y `B`, emitidos por `kp0`) para dos cuentas (`kp2` y `kp3`). Para que alguien participe en el fondo, debe establecer trustlines hacia cada emisor de activo y hacia el activo de la participación del fondo (explicado abajo).
-
-Observa la función auxiliar `orderAssets()` aquí. Las operaciones relacionadas con fondos de liquidez se refieren al par de activos arbitrariamente como `A` y `B`; sin embargo, deben estar “ordenados” tal que `A` < `B`. Este orden lo define el protocolo, pero sus detalles no deberían ser relevantes (si tienes curiosidad, es esencialmente orden lexicográfico por tipo de activo, código y emisor). Podemos usar los métodos de comparación integrados en los SDKs (como `Asset.compare`) para asegurarnos de pasarlos en el orden correcto y evitar errores.
-
-#### Participación: Creación
-
-Primero, vamos a crear un fondo de liquidez para el par de activos definido en el preámbulo. Esto implica establecer una trustline hacia el fondo en sí:
-
-<CodeExample>
-
-```js
-const poolShareAsset = new sdk.LiquidityPoolAsset(
-  A,
-  B,
-  sdk.LiquidityPoolFeeV18,
-);
-
-function establishPoolTrustline(account, keypair, poolAsset) {
-  return server.submitTransaction(
-    buildTx(
-      account,
-      keypair,
-      sdk.Operation.changeTrust({
-        asset: poolAsset,
-        limit: "100000",
-      }),
-    ),
-  );
-}
-```
-
-```python
-pool_share_asset = LiquidityPoolAsset(asset_a=asset_a, asset_b=asset_b)
-
-
-def establish_pool_trustline(source: Keypair, pool_asset: LiquidityPoolAsset) -> Dict[str, Any]:
-    tx = (
-        new_tx_builder(source.public_key)
-            .append_change_trust_op(asset=pool_asset, limit="100000")
-            .build()
-    )
-    tx.sign(source)
-    return server.submit_transaction(tx)
-```
-
-</CodeExample>
-
-Esto permite que los participantes posean participaciones del fondo, lo que significa que ahora pueden realizar depósitos y retiradas de fondos.
-
-#### Participación: Depósitos
-
-Para trabajar con un fondo de liquidez, necesitas conocer su ID de antemano. Es un valor determinista, y solo puede existir un fondo de liquidez para un par de activos particular, así que puedes calcularlo localmente usando los parámetros del fondo.
-
-<CodeExample>
-
-```js
-const poolId = sdk
-  .getLiquidityPoolId(
-    "constant_product",
-    poolShareAsset.getLiquidityPoolParameters(),
-  )
-  .toString("hex");
-
-function addLiquidity(source, signer, poolId, maxReserveA, maxReserveB) {
-  const exactPrice = maxReserveA / maxReserveB;
-  const minPrice = exactPrice - exactPrice * 0.1;
-  const maxPrice = exactPrice + exactPrice * 0.1;
-
-  return server.submitTransaction(
-    buildTx(
-      source,
-      signer,
-      sdk.Operation.liquidityPoolDeposit({
-        liquidityPoolId: poolId,
-        maxAmountA: maxReserveA,
-        maxAmountB: maxReserveB,
-        minPrice: minPrice.toFixed(7),
-        maxPrice: maxPrice.toFixed(7),
-      }),
-    ),
-  );
-}
-```
-
-```python
-pool_id = pool_share_asset.liquidity_pool_id
-
-
-def add_liquidity(
-        source: Keypair,
-        pool_id: str,
-        max_reserve_a: Decimal,
-        max_reserve_b: Decimal,
-) -> dict[str, Any]:
-    exact_price = max_reserve_a / max_reserve_b
-    min_price = exact_price - exact_price * Decimal("0.1")
-    max_price = exact_price + exact_price * Decimal("0.1")
-    tx = (
-        new_tx_builder(source.public_key)
-            .append_liquidity_pool_deposit_op(
-            liquidity_pool_id=pool_id,
-            max_amount_a=f"{max_reserve_a:.7f}",
-            max_amount_b=f"{max_reserve_b:.7f}",
-            min_price=min_price,
-            max_price=max_price,
-        )
-            .build()
-    )
-    tx.sign(source)
-    return server.submit_transaction(tx)
-```
-
-</CodeExample>
-
-Cuando depositas activos en un fondo de liquidez, necesitas definir los límites de precio aceptables. En la función anterior, permitimos un margen de error de +/-10% respecto al “precio spot”. Este margen no es una recomendación, solo se eligió para demostración.
-
-También especificamos la cantidad máxima de cada reserva que estás dispuesto a depositar. Esto, junto con los precios mínimos y máximos, ayuda a definir los límites para el depósito, ya que siempre puede haber un cambio en la tasa de exchange entre enviar la operación y que ésta sea aceptada por la red.
-
-#### Participación: Retiradas de fondos
-
-Si posees participaciones de un fondo en particular, puedes retirar reservas de él. La estructura de la operación es similar a la del depósito:
-
-<CodeExample>
-
-```js
-function removeLiquidity(source, signer, poolId, sharesAmount) {
-  return server
-    .liquidityPools()
-    .liquidityPoolId(poolId)
-    .call()
-    .then((poolInfo) => {
-      let totalShares = poolInfo.total_shares;
-      let minReserveA =
-        (sharesAmount / totalShares) * poolInfo.reserves[0].amount * 0.95;
-      let minReserveB =
-        (sharesAmount / totalShares) * poolInfo.reserves[1].amount * 0.95;
-
-      return server.submitTransaction(
-        buildTx(
-          source,
-          signer,
-          sdk.Operation.liquidityPoolWithdraw({
-            liquidityPoolId: poolId,
-            amount: sharesAmount,
-            minAmountA: minReserveA.toFixed(7),
-            minAmountB: minReserveB.toFixed(7),
-          }),
-        ),
-      );
-    });
-}
-```
-
-```python
-def remove_liquidity(
-        source: Keypair, pool_id: str, shares_amount: Decimal
-) -> dict[str, Any]:
-    pool_info = server.liquidity_pools().liquidity_pool(pool_id).call()
-    total_shares = Decimal(pool_info["total_shares"])
-    min_reserve_a = (
-            shares_amount
-            / total_shares
-            * Decimal(pool_info["reserves"][0]["amount"])
-            * Decimal("0.95")
-    ) #
-    min_reserve_b = (
-            shares_amount
-            / total_shares
-            * Decimal(pool_info["reserves"][1]["amount"])
-            * Decimal("0.95")
-    )
-    tx = (
-        new_tx_builder(source.public_key)
-            .append_liquidity_pool_withdraw_op(
-            liquidity_pool_id=pool_id,
-            amount=f"{shares_amount:.7f}",
-            min_amount_a=f"{min_reserve_a:.7f}",
-            min_amount_b=f"{min_reserve_b:.7f}",
-        )
-            .build()
-    )
-    tx.sign(source)
-    return server.submit_transaction(tx)
-```
-
-</CodeExample>
-
-Aquí especificamos la cantidad mínima. Al igual que con un pago por ruta de recepción estricta, especificamos que no estamos dispuestos a recibir menos que esta cantidad de cada activo del fondo. Esto define efectivamente un precio mínimo de retirada.
-
-#### Uniéndolo todo
-
-Finalmente, podemos combinar estas piezas para simular cierta participación en un fondo de liquidez. Haremos que todos depositen cantidades crecientes en el fondo, luego un participante retirará sus participaciones. Entre cada paso, recuperaremos el precio spot.
-
-<CodeExample>
-
-```js
-function main() {
-  return getAccounts()
-    .then((accounts) => {
-      return Promise.all(
-        kps.map((kp, i) => {
-          const acc = accounts[i];
-          const depositA = ((i + 1) * 1000).toString();
-          const depositB = ((i + 1) * 3000).toString(); // maintain a 1:3 ratio
-
-          return establishPoolTrustline(acc, kp, poolShareAsset)
-            .then(() => addLiquidity(acc, kp, poolId, depositA, depositB))
-            .then(() => getSpotPrice());
-        }),
-      ).then(() => accounts);
-    })
-    .then((accounts) => {
-      // kp1 takes all his/her shares out
-      return server
-        .accounts()
-        .accountId(kps[1].publicKey())
-        .call()
-        .then(({ balances }) => {
-          let balance = 0;
-          balances.every((bal) => {
-            if (
-              bal.asset_type === "liquidity_pool_shares" &&
-              bal.liquidity_pool_id === poolId
-            ) {
-              balance = bal.balance;
-              return false;
-            }
-            return true;
-          });
-          return balance;
-        })
-        .then((balance) =>
-          removeLiquidity(accounts[1], kps[1], poolId, balance),
-        );
-    })
-    .then(() => getSpotPrice());
-}
-
-function getSpotPrice() {
-  return server
-    .liquidityPools()
-    .liquidityPoolId(poolId)
-    .call()
-    .then((pool) => {
-      const [a, b] = pool.reserves.map((r) => r.amount);
-      const spotPrice = new BigNumber(a).div(b);
-      console.log(`Price: ${a}/${b} = ${spotPrice.toFormat(2)}`);
-    });
-}
-
-preamble().then(main);
-```
-
-```python
-def main():
-    deposit_a = Decimal(1000)
-    deposit_b = Decimal(3000)  # maintain a 1:3 ratio
-    establish_pool_trustline(kps[1], pool_share_asset)
-    add_liquidity(kps[1], pool_id, deposit_a, deposit_b)
-    get_spot_price()
-
-    deposit_a = Decimal(2000)
-    deposit_b = Decimal(6000)  # maintain a 1:3 ratio
-    establish_pool_trustline(kps[2], pool_share_asset)
-    add_liquidity(kps[2], pool_id, deposit_a, deposit_b)
-    get_spot_price()
-
-    # kp1 takes all his/her shares out
-    balance = 0
-    for b in server.accounts().account_id(kps[1].public_key).call()["balances"]:
-        if (
-                b["asset_type"] == "liquidity_pool_shares"
-                and b["liquidity_pool_id"] == pool_id
-        ):
-            balance = Decimal(b["balance"])
-            break
-    if not balance:
-        raise
-    remove_liquidity(kps[1], pool_id, balance)
-    get_spot_price()
-
-def get_spot_price():
-    resp = server.liquidity_pools().liquidity_pool(pool_id).call()
-    amount_a = resp["reserves"][0]["amount"]
-    amount_b = resp["reserves"][1]["amount"]
-    spot_price = Decimal(amount_a) / Decimal(amount_b)
-    print(f"Price: {amount_a}/{amount_b} = {spot_price:.7f}")
-
-if __name__ == '__main__':
-    preamble()
-    main()
-```
-
-</CodeExample>
-
-#### Vigilando la actividad del Fondo de Liquidez
-
-Puedes acceder a las transacciones, operaciones y efectos relacionados con un fondo de liquidez si deseas seguir su actividad. Veamos cómo podemos rastrear los últimos depósitos en un fondo (supongamos que `poolId` está definido como antes):
-
-<CodeExample>
-
-```js
-server
-  .operations()
-  .forLiquidityPool(poolId)
-  .call()
-  .then((ops) => {
-    ops.records
-      .filter((op) => op.type == "liquidity_pool_deposit")
-      .forEach((op) => {
-        console.log("Reserves deposited:");
-        op.reserves_deposited.forEach((r) =>
-          console.log(`    ${r.amount} of ${r.asset}`),
-        );
-        console.log("  for pool shares: ", op.shares_received);
-      });
-  });
-```
-
-```python
-def watch_liquidity_pool_activity():
-    for op in (
-        server.operations()
-        .for_liquidity_pool(liquidity_pool_id=pool_id)
-        .cursor("now")
-        .stream()
-    ):
-        if op["type"] == "liquidity_pool_deposit":
-            print("Reserves deposited:")
-            for r in op["reserves_deposited"]:
-                print(f"    {r['amount']} of {r['asset']}")
-            print(f"    for pool shares: {op['shares_received']}")
-        # ...
-```
-
-</CodeExample>
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
deleted file mode 100644
index f0674d1b80..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/lumens.mdx
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Comprender Lumens, la moneda nativa de la red
-sidebar_label: Lumens
-description: Aprende sobre lumens (XLM), el activo digital nativo de la red Stellar. Entiende su papel en las transacciones, las tarifas de la red y el alquiler de contratos inteligentes.
-sidebar_position: 30
----
-
-# Lumens (XLM)
-
-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)
-
-## Tarifas de transacción
-
-Stellar requiere una pequeña tarifa para todas las transacciones para prevenir spam en el ledger y priorizar las transacciones durante los precios de auge. Las tarifas de transacción se pagan en lumens.
-
-Para aprender sobre las tarifas en Stellar, consulta nuestra [sección de Tarifas](./fees-resource-limits-metering.mdx).
-
-Las transacciones de contratos inteligentes en Stellar emplean una estructura de tarifas diferente basada en una tarifa de inclusión y consumo de recursos (que incluye [alquiler](#rent)). Lee más en la [sección de Tarifas y Medición](./fees-resource-limits-metering.mdx).
-
-## Reservas base
-
-Una unidad de medida utilizada para calcular el saldo mínimo de una cuenta. Una reserva base actualmente equivale a 0,5 XLM.
-
-Los validadores pueden votar para cambiar la reserva base, pero eso es poco común y solo debería ocurrir cada pocos años.
-
-## Saldo mínimo
-
-Las cuentas de Stellar deben mantener un saldo mínimo para existir, que se calcula utilizando la reserva base. Una cuenta debe siempre mantener un saldo mínimo de dos reservas base (actualmente 1 XLM). Cada subentrada después de eso requiere una reserva base adicional (actualmente 0,5 XLM) y aumenta el saldo mínimo de la cuenta. Las subentradas incluyen líneas de fideicomiso (para activos tradicionales y participaciones en fondos), ofertas, firmantes y entradas de datos. Una cuenta debe mantener siempre un saldo mínimo de dos reservas base (actualmente 1 XLM).
-
-Los datos también residen en el ledger como entradas de ledger. Las entradas de ledger incluyen saldos reclamables (que requieren una reserva base por reclamante) y depósitos y retiradas de fondos de liquidez.
-
-Por ejemplo, una cuenta con una línea de fideicomiso, dos ofertas y un saldo reclamable con un reclamante tiene un saldo mínimo de:
-
-2 reservas base (1 XLM) + 3 subentradas/reservas base (1,5 XLM) + 1 entrada de ledger/reserva base (1 XLM) = 3,5 XLM
-
-Cuando cierras una subentrada, la reserva base asociada se añadirá a tu saldo disponible. Una cuenta siempre debe pagar su propio saldo mínimo a menos que una subentrada esté siendo patrocinada por otra cuenta. Para obtener información al respecto, consulta nuestra [entrada del enciclopedia sobre reservas patrocinadas](../../build/guides/transactions/sponsored-reserves.mdx).
-
-## Alquiler
-
-Los datos de contratos inteligentes no requieren reservas base para residir en el ledger, por lo que cada entrada de contrato inteligente debe pagar alquiler en su lugar. La renta cobrada por que una entrada exista en el ledger se basa en el tamaño de la entrada y en cuánto tiempo debe estar en vivo en el ledger antes de ser archivada. Existen diferentes requisitos de renta para cada tipo de almacenamiento `Persistent`, `Temporary` e `Instance`, sobre los cuales puedes leer en la [sección de Archivo del Estado](../fundamentals/contract-development/storage/state-archival.mdx).
-
-## Métricas de Suministro de Lumens
-
-Esta sección explica cómo se calculan las métricas de suministro de lumens y se ponen a disposición a través de API. Esta información puede ser útil para productos y servicios que rastrean la distribución de XLM, incluidos los agregadores de capitalización de mercado y algunos exchanges, o para cualquiera que desee investigar la distribución de XLM definida por el mandato del SDF.
-
-A diferencia de muchas otras blockchains, la moneda nativa de la red no se crea mediante minería: todos los XLM que han existido y existirán se crearon cuando la red Stellar se puso en vivo.
-
-[El endpoint de la API del Dashboard del SDF](https://dashboard.stellar.org/api/v2/lumens) siempre tendrá los totales en vivo para los números esenciales relacionados con los lumens. Esta guía explica métricas de suministro importantes como Suministro Original, Suministro Total y Suministro Circulante incluidos en esos datos.
-
-### API del Dashboard
-
-A partir del 28 de mayo de 2024, la API del Dashboard muestra:
-
-<CodeExample>
-
-```json
-{
-  "updatedAt": "2024-05-28T16:11:14.622Z",
-  "originalSupply": "100000000000",
-  "inflationLumens": "5443902087.3472865",
-  "burnedLumens": "55442115112.9537534",
-  "totalSupply": "50001786974.3935331",
-  "upgradeReserve": "259580243.9842749",
-  "feePool": "4690537.8610771",
-  "sdfMandate": "20761482987.7713113",
-  "circulatingSupply": "28976033204.7768698",
-  "_details": "https://www.stellar.org/developers/guides/lumen-supply-metrics.html"
-}
-```
-
-</CodeExample>
-
-### Definiciones
-
-**originalSupply** Se crearon cien mil millones de lumens [cuando la red Stellar se puso en vivo](https://stellar.expert/explorer/public/ledger/2). Ese es el Suministro Original para la red. Ese es el Suministro Original para la red.
-
-**inflationLumens** Durante los primeros cinco años de existencia de Stellar, el suministro de lumens aumentó un 1 % anualmente. Esta “inflación de red” fue detenida por voto de los validadores el 28 de octubre de 2019. El número total de lumens generados por inflación fue de 5.443.902.087,3472865.
-
-Sumando este número al Suministro Original, obtienes el total de lumens que han existido: 105.443.902.087,3472865. Este número 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.total_coins`. Consulta todos los proveedores de datos de Horizon de Stellar Mainnet [aquí](../../data/apis/horizon/providers.mdx).
-
-**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).
-
-**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.
-
-**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:
-
-- [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)
-- [Escrow del 1 de enero de 2022](https://stellar.expert/explorer/public/account/GD2D6JG6D3V52ZMPIYSVHYFKVNIMXGYVLYJQ3HYHG5YDPGJ3DCRGPLTP)
-- [Escrow del 1 de enero de 2023](https://stellar.expert/explorer/public/account/GA2VRL65L3ZFEDDJ357RGI3MAOKPJZ2Z3IJTPSC24I4KDTNFSVEQURRA)
-- [Desarrollo Directo (Hot 1)](https://stellar.expert/explorer/public/account/GCEZYB47RSSSR6RMHQDTBWL4L6RY5CY2SPJU3QHP3YPB6ALPVRLPN7OQ)
-- [Desarrollo Directo (Hot 2)](https://stellar.expert/explorer/public/account/GATL3ETTZ3XDGFXX2ELPIKCZL7S5D2HY3VK4T7LRPD6DW5JOLAEZSZBA)
-- [Desarrollo Directo (Hot 3)](https://stellar.expert/explorer/public/account/GCVLWV5B3L3YE6DSCCMHLCK7QIB365NYOLQLW3ZKHI5XINNMRLJ6YHVX)
-- [Soporte para Desarrolladores](https://stellar.expert/explorer/public/account/GCVJDBALC2RQFLD2HYGQGWNFZBCOD2CPOTN3LE7FWRZ44H2WRAVZLFCU)
-- [Soporte para Desarrolladores (Hot)](https://stellar.expert/explorer/public/account/GCKJZ2YVECFGLUDJ5T7NZMJPPWERBNYHCXT2MZPXKELFHUSYQR5TVHJQ)
-- [Soporte para Monedas](https://stellar.expert/explorer/public/account/GAMGGUQKKJ637ILVDOSCT5X7HYSZDUPGXSUW67B2UKMG2HEN5TPWN3LQ)
-- [Nuevos Productos](https://stellar.expert/explorer/public/account/GCPWKVQNLDPD4RNP5CAXME4BEDTKSSYRR4MMEL4KG65NEGCOGNJW7QI2)
-- [Enterprise Fund](https://stellar.expert/explorer/public/account/GDUY7J7A33TQWOSOQGDO776GGLM3UQERL4J3SPT56F6YS4ID7MLDERI4)
-- [Soporte de Marketing](https://stellar.expert/explorer/public/account/GBEVKAYIPWC5AQT6D4N7FC3XGKRRBMPCAMTO3QZWMHHACLHTMAHAM2TP)
-- [Distribución en la Aplicación](https://stellar.expert/explorer/public/account/GDKIJJIKXLOM2NRMPNQZUUYK24ZPVFC6426GZAEP3KUK6KEJLACCWNMX)
-- [Distribución en la Aplicación (Hot)](https://stellar.expert/explorer/public/account/GAX3BRBNB5WTJ2GNEFFH7A4CZKT2FORYABDDBZR5FIIT3P7FLS2EFOZZ)
-
-**circulatingSupply** El Suministro Circulante son los lumens en manos de individuos y empresas independientes. Estos son lumens que están en el mundo, utilizados para pagar tarifas de red y financiar cuentas de Stellar. También se utilizan como un medio general de exchange. Esperamos que el Suministro Circulante de Stellar crezca constantemente a medida que el SDF gaste y distribuya lumens según su mandato. Los lumens en el Suministro Total, pero no en el Mandato del SDF, Reserva de Mejora o Fondo de Tarifas se asumen como circulantes.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/networks.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/networks.mdx
deleted file mode 100644
index 30b52a0757..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/networks.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
----
-title: Rol y uso de Mainnet, Testnet y Futurenet de Stellar
-sidebar_label: Redes
-description: "Conoce las tres redes de Stellar: Mainnet, Testnet y Futurenet. Entiende sus roles, características y cómo interactuar con cada una para el desarrollo."
-sidebar_position: 20
----
-
-# Redes
-
-Stellar tiene tres redes: la red pública (Mainnet, también llamada Pubnet o la Red Pública), la red de pruebas (Testnet) y una red de desarrollo (Futurenet).
-
-- **Mainnet** es la red principal utilizada por las aplicaciones en producción. Se conecta a vías de pago reales y requiere XLM para cubrir los saldos mínimos, las tarifas de transacción y el alquiler.
-- **Testnet** es una red más pequeña, gratuita y mantenida por SDF que funciona como Mainnet pero no se conecta a dinero real. Se reinicia con regularidad, siendo el mejor lugar para que los desarrolladores prueben aplicaciones en un entorno estable que refleja la funcionalidad de Mainnet.
-- **Futurenet** es una red de desarrollo para probar funciones de última generación. Se reinicia cuando es necesario, por lo que es menos predecible que Testnet, pero es donde se introducen nuevas funciones antes de las versiones estables.
-
-## Comparación de Redes
-
-| Función                                                | Mainnet                                                                | Testnet                                                                          | Futurenet                                                                        |
-| ------------------------------------------------------ | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
-| **Propósito**                                          | Red de producción                                                      | Entorno de prueba estable                                                        | Pruebas de funciones de última generación                                        |
-| **Nodos Validadores**                                  | Operada por el público                                                 | SDF opera tres nodos validadores principales                                     | SDF opera nodos validador centrales                                              |
-| **Financiación**                                       | XLM real requerido de otra cuenta                                      | Gratis vía Friendbot                                                             | Gratis a través de Friendbot                                                     |
-| **Instancia de Horizon**                               | [Múltiples proveedores disponibles](../../data/apis/api-providers.mdx) | [Instancia gratuita de SDF](https://horizon-testnet.stellar.org/)                | [Instancia gratuita de SDF](https://horizon-futurenet.stellar.org)               |
-| **Endpoints RPC**                                      | [Solo proveedores terceros](../../data/apis/api-providers.mdx)         | [Endpoints gratuitos de SDF](../../data/apis/api-providers.mdx#sdf-provided-rpc) | [Endpoints gratuitos de SDF](../../data/apis/api-providers.mdx#sdf-provided-rpc) |
-| **Operaciones por Ledger**                             | 1,000                                                                  | 100                                                                              | 100                                                                              |
-| **Transacciones de contratos inteligentes por Ledger** | Máx 100\*                                                              | 1                                                                                | 1                                                                                |
-| **Reinicios de red**                                   | Nunca                                                                  | Cadencia regular                                                                 | Según sea necesario (imprevisible)                                               |
-| **Friendbot disponible**                               | No                                                                     | Sí (10,000 XLM)                                                                  | Sí (10,000 XLM)                                                                  |
-
-\*La cantidad precisa puede variar según los [límites de recursos](./fees-resource-limits-metering.mdx#resource-limitations). Consulta [Tarifas y Medición](./fees-resource-limits-metering.mdx) para la configuración detallada de la red de contratos inteligentes.
-
-## Friendbot
-
-Friendbot es un bot que financia cuentas con XLM falso en Testnet o Futurenet. Puedes solicitar XLM a Friendbot usando el [Stellar Lab](../../tools/lab/account.mdx#fund-account) o con varios SDK.
-
-**Detalles clave:**
-
-- Las solicitudes están limitadas por tasa, por lo que úsalas de manera inteligente
-- Proporciona 10,000 XLM falsos al financiar una cuenta nueva
-- Para múltiples cuentas: financia tu primera cuenta con Friendbot, luego usa esa cuenta para financiar las siguientes usando la operación Crear Cuenta
-
-## Comenzar
-
-**Para producción:** Usa Mainnet con XLM real e infraestructura preparada para producción.
-
-**Para pruebas:** Usa Testnet para desarrollo estable y pruebas que reflejan el comportamiento de producción.
-
-**Para funciones experimentales:** Usa Futurenet para probar las últimas funciones antes de su lanzamiento.
-
-## Restablecimiento de datos de Testnet y Futurenet
-
-Testnet y Futurenet se reinician periódicamente al libro mayor génesis para desordenar la red, eliminar spam, reducir el tiempo necesario para ponerse al día con el último libro mayor y ayudar a mantener el sistema. Los reinicios borran todas las entradas de ledger (cuentas, líneas de confianza, ofertas, datos de contrato inteligente, etc.), transacciones y datos históricos de Stellar Core, Horizon y el Stellar RPC, que es la razón por la que los desarrolladores no deben confiar en la persistencia de las cuentas o el estado de cualquier saldo al usar Testnet o Futurenet.
-
-Los reinicios de Futurenet son menos regulares que los reinicios de Testnet y no tienen un horario establecido.
-
-Los reinicios de Testnet típicamente ocurren una vez por trimestre a las 17:00 UTC y se anuncian al menos dos semanas antes en el [Panel de Stellar](http://dashboard.stellar.org/) y a través de varios canales de la comunidad de desarrolladores.
-
-Aquí están las fechas programadas de 2025:
-
-- 19 de marzo de 2025
-- 18 de junio de 2025
-- 14 de agosto de 2025
-- 17 de diciembre de 2025
-
-Si ejecutas una instancia de Horizon Testnet o Futurenet, necesitas volver a unirte y re-sincronizarte con la red después de un reinicio. Consulta cómo hacerlo aquí: [Reinicio de Testnet](https://github.com/stellar/packages/blob/master/docs/testnet-reset.md).
-
-Consulta [esta Guía](../../build/guides/basics/automate-reset-data.mdx) sobre cómo automatizar los datos de reinicio de Testnet y Futurenet.
-
-## Automatización de datos de prueba
-
-Se recomienda que tengas una infraestructura de prueba que pueda repoblar el Testnet y Futurenet con datos útiles después de un reinicio. Esto hará que la prueba sea más confiable y te ayudará a escalar tu infraestructura de prueba a una red privada si decides hacerlo. Por ejemplo, puede que quieras:
-
-- Generar emisores de activos para probar el desarrollo de una billetera;
-- Generar órdenes en el libro de órdenes (tanto actuales como históricas) para probar el desarrollo de un cliente de trading;
-- Recrear fondos de liquidez;
-- Volver a implementar contratos inteligentes.
-
-Si mantienes una aplicación, deberías pensar en crear un conjunto de datos que sea lo suficientemente representativo para probar tus casos de uso principales y permitir pruebas robustas incluso cuando Testnet o Futurenet no estén disponibles.
-
-Un script puede automatizar todo este proceso creando una cuenta con Friendbot y enviando un conjunto de transacciones que están predefinidas como parte de tu infraestructura de prueba.
-
-## Frases de contraseña de la red
-
-Mainnet, Testnet y Futurenet de Stellar tienen cada una su frase de contraseña única. Estas se usan al validar firmas en una transacción dada. Si firmas una transacción para una red, pero la envías a otra, no se considerará válida. Por convención, el formato de una frase de contraseña es ‘`[Nombre de la red] ; [Mes de creación] [Año de creación]`’.
-
-The current passphrases for the Stellar Mainnet, Testnet, and Futurenet are:
-
-- Mainnet: '`Public Global Stellar Network ; September 2015`'
-- Testnet: '`Test SDF Network ; September 2015`'
-- Futurenet: '`Test SDF Future Network ; October 2022`'
-
-Las frases de contraseña sirven para dos propósitos principales: (1) se usan como Seed para la cuenta raíz (clave maestra de la red) en el génesis y (2) se usan para crear hashes de transacciones, que son finalmente los que se firman con la clave secreta de cada firmante en un sobre de transacción; esto permite verificar que una transacción fue destinada a una red específica por sus firmantes.
-
-Muchos SDK tienen las frases de contraseña codificadas para las redes de Stellar. Si ejecutas una red privada, tendrás que pasar manualmente una frase de contraseña que se usará siempre que se generen hashes de transacciones. Todos los SDK oficiales de Stellar te permiten usar una red con una frase de contraseña personalizada.
-
-## What Testnet and Futurenet should and should not be used for
-
-### Testnet and Futurenet are good for
-
-- Creating test accounts (with funding from Friendbot);
-- Developing applications and contracts and exploring tutorials on Stellar without the potential to lose any assets;
-- Testing existing applications against new releases or release candidates of Stellar Core, Horizon, and the Stellar RPC;
-- Performing data analysis on a smaller, non-trivial data set compared to the Mainnet.
-
-### Testnet and Futurenet are bad for
-
-- Load and stress testing;
-- High availability test infrastructure- SDF does not guarantee Testnet availability;
-- Long-term storage of data on the network since the network resets periodically;
-- A testing infrastructure that requires more control over the test environment, such as:
-  - The ability to control the data reset frequency;
-  - The need to secure private or sensitive data (before launching on the Mainnet). You can always run your own test network for use cases that don’t work well with SDF’s Testnet.
-
-## Moving your project from Testnet or Futurenet to production
-
-Mainnet, Testnet, and Futurenet each have their own unique passphrase, which is used to validate signatures on a given transaction.
-
-The current passphrases for the Stellar Mainnet, Testnet, and Futurenet are:
-
-**Mainnet (Pubnet)**: `Public Global Stellar Network ; September 2015`
-
-**Testnet**: `Test SDF Network ; September 2015`
-
-**Futurenet**: `Test SDF Future Network ; October 2022`
-
-For applications that don’t rely on the state of the network (such as specific accounts needing to exist), you move to production by changing the network passphrase and ensuring your Horizon instance is connected to Mainnet.
-
-If you’ve been running a Stellar Core or Horizon instance against the Testnet and want to switch to production, changing the passphrase will require both respective databases to be completely reinitialized. If you run your own RPC on Testnet or Futurenet, you may want to use an RPC service when you move to Mainnet. Consulta los proveedores del servicio RPC [aquí](../../data/apis/api-providers.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-consensus-protocol.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-consensus-protocol.mdx
deleted file mode 100644
index c2891d2213..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-consensus-protocol.mdx
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: Descripción general del Stellar Consensus Protocol (SCP) y la validación de transacciones
-sidebar_label: Protocolo de Consenso Stellar
-description: Una breve descripción de cómo el Stellar Consensus Protocol (SCP), un protocolo de prueba de acuerdo, permite el consenso y valida las transacciones en la red.
-sidebar_position: 40
----
-
-# Protocolo de Consenso Stellar
-
-El consenso es de suma importancia en un sistema de pagos descentralizado. Distribuye la supervisión y aprobación de transacciones entre muchos nodos individuales (ordenadores) en lugar de depender de un sistema central cerrado. Los nodos son administrados por organizaciones o individuos, y el objetivo es que todos los nodos actualicen el ledger de la misma manera, asegurando que cada ledger alcance el mismo estado. El consenso es vital para la seguridad de la blockchain, permitiendo que los nodos lleguen a un acuerdo de manera segura y evitando ataques de doble gasto.
-
-La red Stellar alcanza el consenso usando el Protocolo de Consenso Stellar (SCP), que es una construcción del Acuerdo Bizantino Federado (FBA). El FBA difiere de otros mecanismos de consenso bien conocidos como Prueba de Trabajo (que depende de la potencia computacional de un nodo) y Prueba de Participación (que depende del poder de participación de un nodo) al confiar, en cambio, en el acuerdo de nodos de confianza.
-
-En el SCP, cada nodo Stellar Core participante (también llamado validador o nodo validador) decide qué conjunto de otros nodos desea confiar. La flexibilidad de la confianza definida por el usuario permite una membresía de red abierta (lo que significa que cualquiera puede convertirse en un nodo Core) y control descentralizado (lo que significa que ninguna autoridad central dicta de quién se requiere el voto para el consenso).
-
-No hay recompensas monetarias por ser un validador en la red Stellar. En cambio, se anima a los usuarios a convertirse en validadores porque contribuyen a la seguridad y resiliencia de la red, lo que beneficia a los productos y servicios construidos sobre Stellar.
-
-Hay tres propiedades deseadas de los mecanismos de consenso: tolerancia a fallos, seguridad y vitalidad.
-
-- Fault tolerance - the system can continue operating despite node failures or malfunctions
-- Safety - no two nodes ever agree on different values, guarantees nodes will produce the same block
-- Liveness - a node can output a value without the participation of any misbehaving nodes
-
-Los mecanismos de consenso típicamente solo pueden priorizar dos de estas tres propiedades. El SCP prioriza la tolerancia a fallos y la seguridad sobre la vitalidad. Debido a la priorización de la seguridad, los bloques pueden quedar atascados mientras esperan que los nodos lleguen a un acuerdo.
-
-## Componentes del SCP
-
-### Conjunto de quorum
-
-Como se mencionó anteriormente, cada nodo Core decide en qué otros nodos le gustaría confiar para alcanzar un acuerdo. El conjunto de nodos de confianza de un nodo se llama **conjunto de quorum**. Los validadores pueden añadirse mutuamente a sus conjuntos de quorum debido a la confianza innata asociada con identidades del mundo real.
-
-### Umbrales y segmentos de quorum
-
-Además de elegir un conjunto de quorum, los nodos Core también deben elegir un **umbral**. El umbral es el número mínimo de nodos en un conjunto de quorum que deben acordar para alcanzar consenso. Por ejemplo, digamos que el nodo B tiene los nodos [A, C, D] en su conjunto de quorum y establece el umbral en 2. Esto significa que cualquier combinación de 2 nodos en el conjunto de quorum que acuerde es válida: ya sea [A,C], [C,D] o [A,D] deben estar de acuerdo para que el nodo continúe. La combinación de nodos que acuerdan dentro del conjunto de quorum se llama **segmentos de quorum**.
-
-### Conjuntos de bloqueo de nodos
-
-Los nodos pueden ser bloqueados para alcanzar consenso por **conjuntos de bloqueo de nodos**. Los conjuntos de bloqueo de nodos son cualquier conjunto de nodos en un conjunto de quorum que impide que un nodo alcance un acuerdo. Por ejemplo, si un nodo requiere que 3 de los 4 nodos en su conjunto de quorum estén de acuerdo, cualquier combinación de dos nodos se considera un conjunto de bloqueo de nodos.
-
-### Quorum
-
-Un **quorum** es un conjunto de nodos suficiente para alcanzar un acuerdo donde cada nodo es parte de un segmento de quorum.
-
-### Declaración
-
-Las **declaraciones** válidas sobre Stellar expresan las diferentes opiniones de los nodos sobre los conjuntos de transacciones a los que llegar a un acuerdo para un ledger dado. Por ejemplo: “Propongo este conjunto de transacciones para el ledger número 800”.
-
-La opinión de un nodo sobre una declaración depende de las opiniones de su conjunto de quorum.
-
-## Votación federada
-
-En el SCP, el acuerdo se logra mediante votación federada. Un nodo razona sobre el estado de la red en función de lo que aprende de su conjunto de quorum; antes de que una declaración sea acordada al 100% por cada nodo honesto en la red, pasa por tres pasos de votación federada: (1) Votar, (2) Aceptar y (3) Confirmar.
-
-A node can have four opinions on a statement (let’s call the statement “A”)
-
-- I don’t know anything about A and have no opinion
-- I vote for A, it’s valid, but I don’t know if it’s safe to act on it yet
-- I accept A, because enough nodes supported this statement, but I don’t know if it’s safe to act on it yet
-- Confirmo A, es seguro actuar sobre ella. Incluso si cada nodo en mi quorum no ha confirmado A, no podrán confirmar nada más que A.
-
-Para transitar entre los estados anteriores, la votación federada tiene las siguientes reglas:
-
-- Vote for A if it is consistent with my previous votes
-
-- Acepta A si alguna de estas opciones:
-
-  - Cada nodo en mi Quorum Slice votó o aceptó A
-
-    O
-
-  - My blocking set accepted A (even if I voted for something that contradicts A in the past, I forget about that vote, and proceed with accepting A)
-
-- Confirm A if every node in a quorum slice accepted A
-
-## Rondas de consenso
-
-Cada ronda de consenso se separa en dos etapas:
-
-### Protocolo de nominación
-
-En el protocolo de nominación, se seleccionan conjuntos de transacciones candidatas para ser incluidos en un ledger. Una vez que un nodo confirma su primer candidato, deja de votar para nominar nuevos conjuntos de transacciones. Aún puede aceptar o confirmar declaraciones nominadas previamente. Esto garantiza que, en algún momento, todos los nodos convergerán en un conjunto candidato. Si cada nodo en la red deja de introducir nuevos valores pero continúa confirmando lo que otros nodos confirmaron, finalmente, todos terminarán con la misma lista de candidatos.
-
-Un nodo puede comenzar el protocolo de votación tan pronto como confirme un candidato. Después de confirmar su primer candidato y comenzar el protocolo de votación, la nominación sigue funcionando en segundo plano.
-
-### Protocolo de votación
-
-El protocolo de votación garantiza que la red pueda confirmar unánimemente y aplicar conjuntos de transacciones nominadas. Consta de dos pasos:
-
-1. Prepare - verifies that a node’s quorum slice has the right value and is willing to commit it
-2. Commit - ensures that a node’s quorum slice actually commits the value
-
-## Libro blanco
-
-Accede al libro blanco de SCP [aquí](https://stellar.org/learn/stellar-consensus-protocol).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/README.mdx
deleted file mode 100644
index 0446e4a6c9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: "Estructuras de Datos de Blockchain: Cuentas, Contratos Inteligentes, Activos y Ledgers"
-sidebar_label: Estructuras de Datos Stellar
-description: Aprende sobre las estructuras de datos de blockchain, incluyendo cuentas, transacciones, activos y ledgers. Entiende cómo trabajan juntos para hacer funcionar la red.
-sidebar_position: 50
----
-
-# Estructuras de Datos de Stellar
-
-import DocCardList from "@theme/DocCardList";
-
-Las estructuras de datos fundamentales y los bloques de construcción presentes en la red Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/accounts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/accounts.mdx
deleted file mode 100644
index 55203fb2a0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/accounts.mdx
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: "Entender Cuentas: Saldo, Transacciones y Relaciones en la Red"
-sidebar_label: Cuentas
-description: Aprende sobre cuentas en la red Stellar, incluyendo cómo almacenan saldos, firman transacciones e interactúan con activos, contratos inteligentes y otras funciones.
-sidebar_position: 20
----
-
-# Cuentas
-
-Las cuentas son la estructura de datos central en Stellar: mantienen saldos, firman transacciones y emiten activos. Las cuentas solo pueden existir con un keypair válido y el saldo mínimo requerido de XLM.
-
-Para aprender sobre los requisitos de saldo mínimo, [consulta nuestra sección sobre Lumens](../lumens.mdx#minimum-balance).
-
-:::note
-
-Hay dos tipos de cuentas en Stellar: cuentas Stellar (direcciones que comienzan con `G...`) y cuentas de contrato (direcciones que comienzan con `C...`). Para una introducción mínima a las cuentas de contrato, comienza con el [ejemplo de Cuenta Simple](../../../build/smart-contracts/example-contracts/simple-account.mdx). Esta sección se centra en las cuentas `G...` de Stellar.
-
-:::
-
-Las cuentas `G...` están formadas por los siguientes campos. Haz clic en el campo para obtener más información al respecto.
-
-- [ID de Cuenta](../../glossary.mdx#account-id)
-- [Saldos](../../glossary.mdx#balance)
-- [Flags](../../glossary.mdx#flags)
-- [Dominio principal (hasta 32 caracteres)](../../glossary.mdx#home-domain)
-- [Pasivos](../../glossary.mdx#liability)
-- [Número de entradas patrocinadas por esta cuenta](../../../build/guides/transactions/sponsored-reserves.mdx)
-- [Número de reservas patrocinadas](../../../build/guides/transactions/sponsored-reserves.mdx)
-- [Número de subentradas](./accounts.mdx#subentries)
-- [Número de secuencia](../../glossary.mdx#sequence-number)
-- [Firmantes](../../fundamentals/transactions/signatures-multisig.mdx)
-- [Umbrales](../../fundamentals/transactions/signatures-multisig.mdx#thresholds)
-
-## Reservas base y subentradas
-
-Las cuentas almacenan datos en subentradas, y cada subentrada aumenta el saldo mínimo requerido de la cuenta.
-
-### Reservas base
-
-Una reserva base es una unidad de medida utilizada para calcular el saldo mínimo de una cuenta. Una reserva base es actualmente <b>0,5</b> XLM.
-
-### Subentradas
-
-Los datos de la cuenta se almacenan en subentradas, cada una de las cuales aumenta el saldo mínimo de una cuenta en una reserva base (<b>0,5</b> XLM). Una cuenta no puede tener más de <b>1.000</b> subentradas. Las subentradas posibles son:
-
-- Líneas de confianza (incluye activos tradicionales y acciones en pool)
-- Ofertas
-- Firmantes adicionales
-- Entradas de datos (incluye datos realizados con la operación `manageData`, no entradas del libro de contabilidad de contratos inteligentes)
-
-## Líneas de confianza
-
-Las trustlines son una opción explícita para que una cuenta mantenga un activo particular. Para mantener un activo específico, una cuenta debe establecer una línea de confianza con la cuenta emisora utilizando la [operación `change_trust`](../transactions/list-of-operations.mdx#change-trust). Las líneas de confianza rastrean el saldo de un activo y también pueden limitar la cantidad de un activo que una cuenta puede mantener.
-
-Se debe establecer una línea de confianza para que una cuenta reciba cualquier activo excepto lumens (XLM). Puedes crear un saldo reclamable para enviar activos a una cuenta sin una línea de confianza, pero el destinatario tiene que crear una línea de confianza para reclamar ese saldo. Aprende más aquí: [Entrada de la Enciclopedia de Saldos Reclamables](../../../build/guides/transactions/claimable-balances.mdx)
-
-Una línea de confianza también rastrea pasivos. Los pasivos por compra son igual al monto total del activo ofrecido para comprar, agregado sobre todas las ofertas que posee una cuenta, y los pasivos por venta son igual al monto total del activo ofrecido para vender, agregado sobre todas las ofertas que posee una cuenta. Una línea de confianza debe siempre tener un saldo suficientemente grande para satisfacer sus pasivos por venta y un saldo suficientemente bajo en su límite para acomodar sus pasivos por compra.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/assets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/assets.mdx
deleted file mode 100644
index 83f7a39a10..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/assets.mdx
+++ /dev/null
@@ -1,118 +0,0 @@
----
-title: "Activos en Stellar: Explora las líneas de confianza, la integración de contratos inteligentes y más"
-sidebar_label: Activos
-description: Aprende cómo funcionan los activos en la red Stellar, incluyendo la emisión, transferencia y gestión de tokens. Explora las líneas de confianza, utilizando activos en contratos inteligentes, y más.
-sidebar_position: 30
----
-
-:::info
-
-El término "custom token" ha sido reemplazado por "contract token". Ve la conversación en el [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
-
-:::
-
-# Activos
-
-Las cuentas en la red Stellar pueden ser utilizadas para rastrear, mantener y transferir cualquier tipo de activo. Los activos pueden representar muchas cosas: criptomonedas (como bitcoin o ether), monedas fiduciarias (como dólares o pesos), otros tokens de valor (como NFTs), participaciones en fondos o bonos y acciones.
-
-:::note
-
-Los activos existen en dos formas en Stellar:
-
-Activos "Clásicos" emitidos por cuentas de Stellar (direcciones `G...`) y su implementación integrada del Contrato de Activos de Stellar (SAC), y tokens de contrato emitidos por un contrato Wasm desplegado (direcciones `C...`).
-
-Aprende más sobre las diferencias en la [sección de Activos y Tokens](../../../tokens/README.mdx).
-
-:::
-
-Los activos clásicos en Stellar tienen dos características identificadoras: el código del activo y el emisor. Dado que más de una organización puede emitir un crédito que representa el mismo activo, los códigos de activo a menudo se superponen (por ejemplo, múltiples empresas ofrecen un token USD en Stellar). Los activos se identifican de manera única por la combinación de su código de activo y emisor.
-
-## Componentes del activo
-
-### Código de activo
-
-El código identificador de un activo. Existen tres formatos diferentes: Alfanumérico 4, Alfanumérico 12 y participaciones en fondos de liquidez.
-
-Aprende sobre las participaciones en fondos de liquidez en la [sección de Fondos de Liquidez](../liquidity-on-stellar-sdex-liquidity-pools.mdx).
-
-Aprende más sobre los códigos de activos en la [sección Nombrando un Activo](../../../tokens/control-asset-access.mdx#naming-an-asset)
-
-### Emisor
-
-No existe una operación dedicada para crear un activo en Stellar. En su lugar, los activos se crean con una operación de pago: una cuenta emisora realiza un pago utilizando el activo que está emitiendo, y ese pago crea el activo en la red.
-
-La clave pública de la cuenta emisora está vinculada en el ledger al activo. La responsabilidad y el control sobre un activo residen en la cuenta emisora. Dado que los ajustes se almacenan a nivel de cuenta en el ledger, la cuenta emisora es donde utilizas las operaciones set_options para vincular a la meta-información sobre un activo y establecer los flags de autorización.
-
-Aprende a emitir un activo en el [Tutorial de Emisión de Activos](../../../tokens/how-to-issue-an-asset.mdx).
-
-## Representación
-
-En Horizon, los activos se representan en un objeto JSON:
-
-<CodeExample>
-
-```json5
-{
-  asset_code: "AstroDollar",
-  asset_issuer: "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF",
-  // `asset_type` is used to determine how asset data is stored.
-  // It can be `native` (lumens), `credit_alphanum4`, or `credit_alphanum12`.
-  asset_type: "credit_alphanum12",
-}
-```
-
-</CodeExample>
-
-En los SDK de Stellar, se representan con la clase de activo:
-
-<CodeExample>
-
-```js
-var astroDollar = new StellarSdk.Asset(
-  "AstroDollar",
-  "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF",
-);
-```
-
-```java
-KeyPair issuer = KeyPair.fromAccountId("GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF");
-Asset astroDollar = Asset.createNonNativeAsset("AstroDollar", issuer.getAccountId());
-```
-
-```python
-from stellar_sdk import Asset
-
-astro_dollar = Asset("AstroDollar", "GC2BKLYOOYPDEFJKLKY6FNNRQMGFLVHJKQRGNSSRRGSMPGF32LHCQVGF")
-```
-
-</CodeExample>
-
-## Precisión de monto
-
-Cada cantidad de activo está codificada como un entero firmado de 64 bits en las estructuras XDR que Stellar utiliza para codificar transacciones. The asset amount unit seen by end-users is scaled down by a factor of ten million (10,000,000) to arrive at the native 64-bit integer representation.
-
-For example, the integer amount value 25,123,456 equals 2.5123456 units of the asset. Esta escala permite siete lugares decimales de precisión en unidades de cantidad amigables para humanos.
-
-The smallest non-zero amount unit, also known as a stroop, is 0.0000001 (one ten-millionth) represented as an integer value of one. The largest amount unit possible is $\frac{2^{63}-1}{10^7}$ (derived from the maximum 64-bit integer, scaled down) which is 922,337,203,685.4775807.
-
-Los números se representan como int64s. Los valores de cantidad se almacenan solo como enteros firmados para evitar errores que surgen de mezclar enteros firmados y no firmados.
-
-## Relevancia en las bibliotecas cliente de Stellar
-
-En bibliotecas del lado del cliente como js-stellar-sdk, el valor codificado como entero está abstraído. Muchas API esperan un monto en valor de unidad (la cantidad aumentada que se muestra a los usuarios finales). Algunos lenguajes de programación (como JavaScript) tienen problemas para mantener la precisión en un monto numérico. Se recomienda utilizar bibliotecas de “números grandes” que pueden registrar números decimales de precisión arbitraria sin pérdida de precisión.
-
-## Eliminando o quemando activos
-
-Para eliminar, o "burn", un activo, debes enviarlo de vuelta a la cuenta que lo emitió.
-
-## Uso de los activos Stellar en contratos inteligentes
-
-Los activos emitidos en la red Stellar son accesibles a contratos inteligentes. Cada activo de Stellar tiene reservado un Contrato de Activo de Stellar (SAC) que puede ser desplegado por cualquiera que quiera poder interactuar con el activo desde un contrato.
-
-El CLI de Stellar puede desplegar un Contrato de Activo Stellar para un activo Stellar. Desplegar el Contrato de Activo Stellar para un activo Stellar permite que ese activo se utilice con contratos inteligentes.
-
-Aprende más en la [sección SAC](../../../tokens/stellar-asset-contract.mdx).
-
-## Token contracts
-
-Token contracts can be deployed on Stellar by deploying a contract that implements the [Token Interface](../../../tokens/token-interface.mdx), which is the same interface implemented by the [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) for Stellar assets.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/contracts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/contracts.mdx
deleted file mode 100644
index b763bca0dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/contracts.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Contratos Inteligentes
-sidebar_position: 50
----
-
-Un smart contract es un conjunto programado de código ejecutable y estado que puede invocarse en la red Stellar. Los smart contracts almacenan datos y también definen reglas sobre cómo se pueden usar esos datos. Stellar ha integrado una plataforma de smart contracts llamada "Soroban" en el protocolo principal. Estos contratos son programas escritos en el lenguaje Rust y compilados en WebAssembly (Wasm) para su despliegue.
-
-Aprende sobre conceptos de smart contracts en Stellar como almacenamiento, autorización, depuración y más en la [Sección de Aprendizaje de Smart Contracts](../contract-development/overview.mdx).
-
-Escribe tu primer smart contract en Stellar siguiendo la [Guía para Comenzar](../../../build/smart-contracts/getting-started/README.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/events.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/events.mdx
deleted file mode 100644
index 4afa98aea2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/events.mdx
+++ /dev/null
@@ -1,296 +0,0 @@
----
-sidebar_position: 11
-title: Eventos
-description: Monitorear el movimiento de valor fuera de la cadena y los cambios en contratos inteligentes.
----
-
-Los eventos son el mecanismo que las aplicaciones fuera de la cadena pueden usar para monitorear el movimiento de valor de cualquier operación Stellar, así como eventos personalizados en contratos dentro de la cadena.
-
-## ¿Cómo se emiten los eventos?
-
-Los `ContractEvents` se emiten en el `TransactionMeta` de Stellar Core. La ubicación de los eventos dependerá de la versión de `TransactionMeta` emitida. Puedes ver en el XDR [TransactionMetaV3] abajo que para las transacciones Soroban, existe un campo `sorobanMeta` que contiene `SorobanTransactionMeta` e incluye tanto `events` (eventos personalizados de contratos) como `diagnosticEvents`. Ten en cuenta que `events` solo se poblarán si la transacción tiene éxito.
-
-[TransactionMetaV4] es más complejo porque soporta eventos no solo para Soroban, sino también para operaciones clásicas, comisiones y reembolsos. El vector `events` de nivel superior se usa para los eventos a nivel de transacción, y actualmente contiene eventos de `fee` tanto para la comisión inicial cobrada como para el reembolso (si aplica). Los eventos relacionados con operaciones se encuentran bajo `OperationMetaV2`.
-
-[transactionmetav3]: #transactionmetav3
-[transactionmetav4]: #transactionmetav4
-
-### ContractEvent
-
-Los temas de un evento no tienen que ser del mismo tipo: puedes mezclar diferentes tipos.
-
-Un evento también contiene un objeto de datos de cualquier valor o tipo, incluyendo [tipos personalizados](../contract-development/types/custom-types.mdx) definidos por contratos usando `#[contracttype]`:
-
-```cpp
-struct ContractEvent
-{
-    // We can use this to add more fields, or because it
-    // is first, to change ContractEvent into a union.
-    ExtensionPoint ext;
-
-    ContractID* contractID;
-    ContractEventType type;
-
-    union switch (int v)
-    {
-    case 0:
-        struct
-        {
-            SCVal topics<>;
-            SCVal data;
-        } v0;
-    }
-    body;
-};
-```
-
-`ContractEvent` puede ser emitido en las siguientes versiones de `TransactionMeta` -
-
-### TransactionMetaV3
-
-```cpp
-struct SorobanTransactionMeta
-{
-    SorobanTransactionMetaExt ext;
-
-    ContractEvent events<>;             // custom events populated by the
-                                        // contracts themselves.
-    SCVal returnValue;                  // return value of the host fn invocation
-
-    // Diagnostics events that are not hashed.
-    // This will contain all contract and diagnostic events. Even ones
-    // that were emitted in a failed contract call.
-    DiagnosticEvent diagnosticEvents<>;
-};
-
-struct TransactionMetaV3
-{
-    ExtensionPoint ext;
-
-    LedgerEntryChanges txChangesBefore;  // tx level changes before operations
-                                         // are applied if any
-    OperationMeta operations<>;          // meta for each operation
-    LedgerEntryChanges txChangesAfter;   // tx level changes after operations are
-                                         // applied if any
-    SorobanTransactionMeta* sorobanMeta; // Soroban-specific meta (only for
-                                         // Soroban transactions).
-};
-```
-
-### TransactionMetaV4
-
-```cpp
-struct OperationMetaV2
-{
-    ExtensionPoint ext;
-
-    LedgerEntryChanges changes;
-
-    ContractEvent events<>;
-};
-
-// Transaction-level events happen at different stages of the ledger apply flow
-// (as opposed to the operation events that all happen atomically after
-// a transaction is applied).
-// This enum represents the possible stages during which an event has been
-// emitted.
-enum TransactionEventStage {
-    // The event has happened before any one of the transactions has its
-    // operations applied.
-    TRANSACTION_EVENT_STAGE_BEFORE_ALL_TXS = 0,
-    // The event has happened immediately after operations of the transaction
-    // have been applied.
-    TRANSACTION_EVENT_STAGE_AFTER_TX = 1,
-    // The event has happened after every transaction had its operations
-    // applied.
-    TRANSACTION_EVENT_STAGE_AFTER_ALL_TXS = 2
-};
-
-// Represents a transaction-level event in metadata.
-// Currently this is limited to the fee events (when fee is charged or
-// refunded).
-struct TransactionEvent {
-    TransactionEventStage stage;  // Stage at which an event has occurred.
-    ContractEvent event;  // The contract event that has occurred.
-};
-
-struct TransactionMetaV4
-{
-    ExtensionPoint ext;
-
-    LedgerEntryChanges txChangesBefore;  // tx level changes before operations
-                                         // are applied if any
-    OperationMetaV2 operations<>;        // meta for each operation
-    LedgerEntryChanges txChangesAfter;   // tx level changes after operations are
-                                         // applied if any
-    SorobanTransactionMetaV2* sorobanMeta; // Soroban-specific meta (only for
-                                           // Soroban transactions).
-
-    TransactionEvent events<>; // Used for transaction-level events (like fee payment)
-    DiagnosticEvent diagnosticEvents<>; // Used for all diagnostic information
-};
-```
-
-[Enlace](https://github.com/stellar/stellar-xdr/blob/4b7a2ef7931ab2ca2499be68d849f38190b443ca/Stellar-ledger.x#L440-L522) al XDR arriba.
-
-### Tipos de eventos
-
-Hay tres `ContractEventType` -
-
-1. Los eventos `CONTRACT` son eventos emitidos por contratos que usan la función host `contract_event` para comunicar cambios de estado.
-2. Los eventos `SYSTEM` son eventos emitidos por el host. Por el momento, solo hay un evento del sistema emitido por el host. Se emite cuando se llama a la función host `update_current_contract_wasm`, donde `topics = ["executable_update", old_executable: ContractExecutable, old_executable: ContractExecutable]` y `data = []`.
-3. Los eventos `DIAGNOSTIC` están destinados para depuración y no se emitirán a menos que la instancia del host los habilite explícitamente. Puedes leer más sobre esto a continuación.
-
-## ¿Qué son los diagnosticEvents?
-
-Al observar el XDR anterior, puede que hayas notado el campo `diagnosticEvents`. Esta lista estará vacía por defecto a menos que tu instancia stellar-core tenga `ENABLE_SOROBAN_DIAGNOSTIC_EVENTS=true` en su archivo de configuración. Si los eventos de diagnóstico están habilitados, esta lista incluirá eventos de llamadas fallidas a contratos, errores del host, eventos para rastrear la pila de llamadas del contrato y registros de la función host `log_from_linear_memory`. Estos eventos pueden identificarse por `type == DIAGNOSTIC`. Si la transacción es para una invocación Soroban, la lista también contendrá los eventos no diagnósticos emitidos por el contrato. Los eventos de diagnóstico emitidos por el host para rastrear la pila de llamadas están definidos a continuación.
-
-### fn_call
-
-El evento de diagnóstico `fn_call` se emite cuando se llama un contrato y contiene -
-
-- Temas
-  1. El símbolo "fn_call".
-  2. El id del contrato que está a punto de ser llamado.
-  3. Un símbolo que contiene el nombre de la función que se está llamando.
-- Datos
-  1. Un vector con los argumentos pasados a la función que se está llamando.
-
-### fn_return
-
-El evento de diagnóstico `fn_return` se emite cuando una llamada a contrato finaliza y contiene -
-
-- Temas
-  1. El símbolo "fn_return".
-  2. Un símbolo que contiene el nombre de la función que va a devolver.
-- Datos
-  1. El valor devuelto por la función del contrato.
-
-### ¿Cuándo deberían habilitarse los eventos de diagnóstico?
-
-Los `ContractEvents` regulares deben transmitir información sobre cambios de estado. Por otro lado, los `diagnosticEvents` contienen eventos que no son útiles para la mayoría de los usuarios, pero pueden ser de ayuda para depurar problemas o construir la pila de llamadas del contrato. Como no serán usados por la mayoría, pueden habilitarse opcionalmente porque no se incluyen en el hash del libro mayor y, por lo tanto, no forman parte del protocolo. Esto permite que un nodo stellar-core se mantenga sincronizado con la red mientras emite estos eventos que normalmente no serían útiles para la mayoría.
-
-Debido a que un nodo con eventos de diagnóstico habilitados ejecutará caminos de código que difieren de un nodo regular, recomendamos usar esta función solo en nodos observadores (nodos donde `NODE_IS_VALIDATOR=false` está configurado).
-
-## Rastreo del movimiento de valor
-
-A partir del protocolo 23, las operaciones clásicas pueden emitir eventos `transfer`, `mint`, `burn`, `clawback`, `fee` y `set_authorized` para que el movimiento de activos y las actualizaciones de trustline puedan rastrearse usando un solo flujo de datos. Estos eventos se emitirán si un nodo tiene `EMIT_CLASSIC_EVENTS=true` configurado. Si también se configura `BACKFILL_STELLAR_ASSET_EVENTS=true`, entonces se emitirán eventos para cualquier libro mayor, independientemente de la versión del protocolo.
-
-## Lectura de eventos
-
-Puedes usar el endpoint [`getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents.mdx) de cualquier servicio RPC para obtener y filtrar eventos por tipo, contrato y tema.
-
-:::warning
-
-Los eventos son efímeros: los proveedores RPC típicamente solo mantienen fragmentos cortos (menos de una semana) de historial.
-
-:::
-
-Para saber más sobre cómo trabajar con eventos, consulta las [guías de eventos](../../../build/guides/events/README.mdx) y [este contrato de ejemplo](../../../build/smart-contracts/example-contracts/events.mdx).
-
-Para una demostración rápida y a alto nivel, usaremos el [SDK de TypeScript](../../../tools/sdks/README.mdx) para obtener infinitamente todos los eventos `transfer` (definidos por la [Interfaz de Token Soroban](https://stellar.org/protocol/sep-41#interface)) que involucren el [contrato XLM](https://stellar.expert/explorer/testnet/contract/CDLZFC3SYJYDZT7K67VZ75HPJVIEUVNIXF47ZG2FB2RMQQVU2HHGCYSC) y mostrarlos en un formato amigable para humanos.
-
-<CodeExample>
-
-```javascript
-import {
-  humanizeEvents,
-  nativeToScVal,
-  scValToNative,
-  Address,
-  Networks,
-  Asset,
-  xdr,
-} from "@stellar/stellar-sdk";
-import { Server } from "@stellar/stellar-sdk/rpc";
-
-const s = new Server("https://soroban-testnet.stellar.org");
-
-async function main() {
-  const response = await s.getLatestLedger();
-  const xlmFilter = {
-    type: "contract",
-    contractIds: [Asset.native().contractId(Networks.TESTNET)],
-    topics: [
-      // Defined in https://stellar.org/protocol/sep-41#interface
-      // for all compatible transfer events.
-      [
-        nativeToScVal("transfer", { type: "symbol" }).toXDR("base64"),
-        "*", // from anyone
-        "*", // to anyone
-        "*", // any asset (it'll be XLM anyway)
-      ],
-    ],
-  };
-  let page = await s.getEvents({
-    startLedger: response.sequence - 120, // start ~10m in the past
-    filters: [xlmFilter],
-    limit: 10,
-  });
-
-  // Run forever until Ctrl+C'd by user
-  while (true) {
-    if (!page.events.length) {
-      await new Promise((r) => setTimeout(r, 2000));
-    } else {
-      //
-      // Two ways to output a human-friendly version:
-      //  1. the RPC response itself for human-readable text
-      //  2. a helper for the XDR structured-equivalent for human-readable JSON
-      //
-      console.log(cereal(simpleEventLog(page.events)));
-      console.log(cereal(fullEventLog(page.events)));
-    }
-
-    // Fetch the next page until events are exhausted, then wait.
-    page = await s.getEvents({
-      filters: [xlmFilter],
-      cursor: page.cursor,
-      limit: 10,
-    });
-  }
-}
-
-function simpleEventLog(events) {
-  return events.map((event) => {
-    return {
-      topics: event.topic.map((t) => scValToNative(t)),
-      value: scValToNative(event.value),
-    };
-  });
-}
-
-function fullEventLog(events) {
-  return humanizeEvents(
-    events.map((event) => {
-      // rebuild the decomposed response into its original XDR structure
-      return new xdr.ContractEvent({
-        contractId: event.contractId.address().toBuffer(),
-        type: xdr.ContractEventType.contract(), // since we filtered on 'contract'
-        body: new xdr.ContractEventBody(
-          0,
-          new xdr.ContractEventV0({
-            topics: event.topic,
-            data: event.value,
-          }),
-        ),
-      });
-    }),
-  );
-}
-
-// A custom JSONification method to handle bigints.
-function cereal(data) {
-  return JSON.stringify(
-    data,
-    (k, v) => (typeof v === "bigint" ? v.toString() : v),
-    2,
-  );
-}
-
-main().catch((e) => console.error(e));
-```
-
-</CodeExample>
-
-También puedes aprovechar los [formatos alternativos de codificación XDR](../../../data/apis/rpc/api-reference/structure/data-format) de RPC como JSON para ver eventos legibles desde la línea de comandos directamente, por ejemplo pasando `xdrFormat: "json"` como parámetro adicional al ejemplo `getEvents` (../../../data/apis/rpc/api-reference/methods/getEvents#examples).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/ledgers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/ledgers.mdx
deleted file mode 100644
index f8d079126d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-data-structures/ledgers.mdx
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: Los ledgers almacenan cuentas, saldos, órdenes, datos de contratos inteligentes y más
-sidebar_position: 10
-sidebar_label: Libros de contabilidad
-description: Un ledger captura el estado de la red Stellar en un momento dado, almacenando cuentas, saldos, órdenes, datos de contratos inteligentes y otra información persistente.
----
-
-# Lederes
-
-Un libro de contabilidad representa el estado de la red Stellar en un momento determinado. Se comparte entre todos los nodos principales de la red y contiene la lista de cuentas y saldos, órdenes en el exchange distribuido, datos de contratos inteligentes, y cualquier otro dato que persista.
-
-:::note
-
-Las blockchains suelen referirse al **ledger** como el registro completo de todas las transacciones en la blockchain y a los **blocks** como unidades individuales de datos que contienen una colección de transacciones. En Stellar, "ledger" puede referirse a ambos.
-
-:::
-
-En cada ronda del Stellar Consensus Protocol, la red alcanza consenso sobre qué conjunto de transacciones aplicar al último libro de contabilidad cerrado, y cuando se aplica el nuevo conjunto, se define un nuevo “último libro de contabilidad cerrado”. Cada libro de contabilidad está vinculado criptográficamente al libro de contabilidad anterior único, creando una cadena histórica que se remonta al libro de contabilidad génesis.
-
-Los datos se almacenan en el libro de contabilidad como entradas de libro de contabilidad. Las posibles entradas de libro de contabilidad incluyen:
-
-- [Cuentas](./accounts.mdx)
-- [Saldos reclamables](../../../build/guides/transactions/claimable-balances.mdx)
-- [Pools de liquidez](../../fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx)
-- [Datos del contrato](../../fundamentals/contract-development/storage/persisting-data.mdx#ledger-entries)
-
-## Encabezados del ledger
-
-Cada ledger tiene un encabezado que hace referencia a los datos de ese ledger y del ledger anterior. Estas referencias son hashes criptográficos del contenido que funcionan como punteros en estructuras típicas de datos, pero con garantías de seguridad añadidas. Piensa en una cadena histórica de ledgers como una lista enlazada de encabezados de ledgers. El tiempo avanza de izquierda a derecha, los hashes apuntan hacia atrás en el tiempo, de derecha a izquierda. Cada hash en la cadena vincula un ledger con su ledger anterior, lo que autentica toda la historia de ledgers en su pasado:
-
-```mermaid
-flowchart RL
-    subgraph genesis["Genesis"]
-        direction LR
-        prev1["Prev: none"]
-        state1["Genesis state"]
-    end
-
-    subgraph block2["Ledger 2"]
-        prev2["Prev: hash(Genesis)"]
-        state2["Ledger 2<br/>transactions<br/>and state"]
-    end
-
-    subgraph block3["Ledger 3"]
-        prev3["Prev: hash(Ledger 2)"]
-        state3["Ledger 3<br/>transactions<br/>and state"]
-    end
-
-    subgraph dotdot["..."]
-    end
-
-    subgraph blockn["Ledger N"]
-        prevn["Prev: hash(Ledger N-1)"]
-        staten["Ledger N<br/>transactions<br/>and state"]
-    end
-
-
-    genesis ~~~ block2 ~~~ block3 ~~~ dotdot ~~~ blockn
-    prev2 --> genesis
-    prev3 --> block2
-    dotdot --> block3
-    prevn --> dotdot
-
-```
-
-El ledger génesis tiene un número de secuencia de 1. El ledger que sigue directamente a un ledger con número de secuencia `N` tiene un número de secuencia de `N+1`. El ledger `N+1` contiene un hash del ledger `N` en su campo del ledger anterior.
-
-## Campos del encabezado del ledger
-
-### Versión
-
-La versión del protocolo de este ledger.
-
-### Hash del ledger anterior
-
-Hash del ledger anterior.
-
-### Valor SCP
-
-Durante el consenso, todos los nodos validadores en la red ejecutan SCP y acuerdan un valor particular, que es un conjunto de transacciones que aplicarán a un ledger. Este valor se almacena aquí y en los siguientes tres campos (hash del conjunto de transacciones, tiempo de cierre y actualizaciones).
-
-### Hash del conjunto de transacciones
-
-Hash del conjunto de transacciones aplicado al ledger anterior.
-
-### Tiempo de cierre
-
-El tiempo de cierre es una marca temporal UNIX que indica cuándo cierra el ledger. Su precisión depende del reloj del sistema del validador que propone el bloque. Consecuentemente, SCP puede confirmar un tiempo de cierre que se retrasa unos segundos o que puede adelantarse hasta 60 segundos. Es estrictamente monótono: se garantiza que es mayor que el tiempo de cierre de un ledger anterior.
-
-### Actualizaciones
-
-Cómo la red ajusta valores generales (como la tarifa base) y acuerda cambios a nivel de red (como el cambio a una nueva versión del protocolo). Este campo suele estar vacío. Cuando hay una actualización a nivel de red, el SDF informa y ayuda a coordinar a los participantes usando el canal #validators en el Discord de desarrolladores y el Grupo de Google Stellar Validators.
-
-### Hash del resultado del conjunto de transacciones
-
-Hash de los resultados de la aplicación del conjunto de transacciones. Estos datos no son necesarios para validar los resultados de las transacciones. Sin embargo, facilitan a las entidades validar el resultado de una transacción dada sin tener que aplicar el conjunto de transacciones al ledger anterior.
-
-### Hash de la lista de buckets
-
-Hash de todos los objetos en este ledger. La estructura de datos que contiene todos los objetos se llama lista de buckets.
-
-### Secuencia del ledger
-
-El número de secuencia de este ledger.
-
-### Total de monedas
-
-Número total de lumens en existencia.
-
-### Fondo de tarifas
-
-Número de lumens que se han pagado en tarifas. Nota que esto está denominado en lumens, aunque el campo de tarifa de una transacción está en stroops.
-
-### Secuencia de inflación
-
-Número de veces que se ha ejecutado la inflación. Nota: la operación de inflación fue descontinuada cuando los validadores votaron para actualizar la red al Protocolo 12 el 28/10/2019. Por lo tanto, la inflación ya no se ejecuta y este número de secuencia ya no cambia.
-
-### Fondo de IDs
-
-El último ID global usado. Estos ID se utilizan para generar objetos.
-
-### Número máximo de transacciones
-
-El número máximo de operaciones que los validadores han acordado procesar en un ledger determinado. Si se envían más transacciones que este número, la red entrará en modo de precios dinámicos. Para más información sobre precios dinámicos y estrategias de tarifas, consulta nuestra [sección de tarifas](../../fundamentals/fees-resource-limits-metering.mdx).
-
-### Tarifa base
-
-La tarifa que la red cobra por operación en una transacción. Calculado en stroops. Consulta la [sección de tarifas](../../fundamentals/fees-resource-limits-metering.mdx) para más información.
-
-### Reserva base
-
-La reserva que la red usa al calcular el saldo mínimo de una cuenta.
-
-### Lista de omisión
-
-Hashes de ledgers anteriores. Diseñada para acelerar el acceso a ledgers anteriores sin tener que retroceder ledger por ledger. Actualmente no se utiliza.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-ecosystem-proposals.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-ecosystem-proposals.mdx
deleted file mode 100644
index 157c158f4b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-ecosystem-proposals.mdx
+++ /dev/null
@@ -1,182 +0,0 @@
----
-title: "Propuestas del Ecosistema Stellar (SEPs): Normas para la Interoperabilidad y el Desarrollo"
-sidebar_label: Propuestas del ecosistema Stellar
-description: Aprende sobre las Propuestas del Ecosistema Stellar (SEPs), normas que mejoran la interoperabilidad, mejoran la funcionalidad y amplían las capacidades de la red.
-sidebar_position: 80
----
-
-# Propuestas del Ecosistema Stellar (SEPs)
-
-Cada SEP es un plano distinto destinado a ayudar a los usuarios a construir un producto o servicio que interopera con otros productos y servicios en la red Stellar.
-
-:::note
-
-Esta página cubre las Propuestas del Ecosistema Stellar (SEPs), que definen estándares y protocolos para proyectos que construyen sobre la red Stellar. Los SEPs se diferencian de las Propuestas de Avance del Núcleo (CAPs), que proponen cambios en el protocolo núcleo de la red Stellar. Puedes aprender más sobre los CAPs en [GitHub](https://github.com/stellar/stellar-protocol/tree/master/core).
-
-:::
-
-Cuando desarrollas en Stellar, generalmente usas la API RPC de Stellar para interactuar con la red. Sin embargo, cada vez que deseas que tu producto o servicio interopere con otros productos o servicios en el ecosistema, debes crear infraestructura adicional para manejar esos componentes de una interacción.
-
-Los SEPs definen estándares para construir esa infraestructura sobre la red Stellar. Están diseñados para ayudar a diferentes entidades, como emisores de activos, billeteras, exchanges y otros proveedores de servicios a interoperen usando una única integración común. Generalmente, definen dos lados de una interacción — a menudo un lado servidor y un lado cliente — y usarlos como un plano te permite conectarte a múltiples contrapartes sin comenzar de cero cada vez.
-
-Los SEPs son documentos de código abierto creados públicamente que viven en el [repositorio de GitHub](https://github.com/stellar/stellar-protocol/tree/master/ecosystem) y tienen un proceso de aprobación liviano. Los nuevos SEPs y mejoras se discuten constantemente. Animamos a participar en estas discusiones para ayudar a construir nuevos estándares y hacer los servicios de Stellar más accesibles.
-
-## SEPs Notables
-
-Hay muchos SEPs, y cubren una gran variedad de estándares para la interoperabilidad (consulta la lista completa de SEPs activos [más abajo](#complete-list-of-active-proposals)). Cualquiera que estés construyendo, querrás echar un vistazo a la lista completa para ver si hay un estándar para tu caso de uso.
-
-Esta sección cubrirá algunos SEPs notables que definen los estándares para algunos casos de uso comunes de Stellar.
-
-### SEP-0001 - Archivo de Información Stellar
-
-Define cómo crear y alojar un archivo stellar.toml: un lugar común donde Internet puede encontrar información sobre tu integración Stellar. Puedes almacenar mucha información en tu archivo stellar.toml, incluida información sobre la organización, información sobre la moneda y información de contacto. TOML es un formato de archivo de configuración simple y comúnmente utilizado diseñado para ser legible tanto por humanos como por máquinas.
-
-Usando la operación `set_options`, puedes vincular tu cuenta Stellar al dominio que aloja tu stellar.toml, creando una conexión on-chain entre esta información y esa cuenta.
-
-**Usado por anchors, emisores y validadores.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)
-
-### SEP-0005 - Métodos de Derivación de Claves para Cuentas Stellar
-
-Describe métodos para la derivación de claves para Stellar, mejorando el almacenamiento de claves y moviendo claves entre billeteras y aplicaciones. La guía en este SEP mejora el ecosistema Stellar al:
-
-- Hacer que la derivación de claves sea la misma en billeteras y aplicaciones
-- Permitir a los usuarios mantener claves en billeteras de hardware
-- Permitir a los usuarios mantener claves en almacenamiento en frío de manera más confiable (usando códigos mnemotécnicos)
-- Permitir a los usuarios generar múltiples claves a partir de una sola semilla (por ejemplo, primero para almacenar fondos y segundo como firmante para una cuenta compartida)
-
-**Usado por billeteras y otras aplicaciones.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md)
-
-### SEP-0006 - API de Depósito y Retirada
-
-Define la forma estándar en que los anchors y billeteras interactúan en nombre de los usuarios. Con la guía de este SEP, las billeteras y otros clientes pueden interactuar directamente con los anchors sin que el usuario necesite salir de la billetera para ir al sitio del anchor.
-
-Este SEP define un protocolo estándar que permite las siguientes características dentro de una billetera u otro cliente Stellar:
-
-- Depositar activos externos con un anchor
-- Retirar activos de un anchor
-- Ejecutar depósito/retirada entre activos no equivalentes
-- Comunicar la estructura de tarifas de depósito y retirada para un anchor al usuario
-- Manejar las necesidades de KYC del anchor, incluyendo transmitir información de KYC sobre el usuario al anchor a través de SEP-12
-- Comprobar el estado de los depósitos o retiradas en curso que involucran al usuario
-- Ver el historial de depósitos y retiradas que involucran al usuario
-
-El SEP-0024 es la alternativa al SEP-0006 que soporta depósitos y retiradas alojadas.
-
-**Usado por anchors, billeteras y otras aplicaciones.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md)
-
-### SEP-0007 - Esquema URI para Facilitar la Firma Delegada
-
-Define el esquema URI estándar que se puede usar para generar un URI que servirá como solicitud para firmar una transacción. Con la guía de este SEP, las aplicaciones no billeteras pueden permitir que sus usuarios firmen una transacción sin ver la clave secreta del usuario de la billetera de ninguna forma, ya que el URI (solicitud) normalmente será firmado por la billetera de confianza del usuario donde se almacenan las claves secretas.
-
-Este SEP define un protocolo estándar que permite las siguientes características dentro de una billetera u otro cliente Stellar:
-
-- Pagos mediante Deep Links (en línea)
-- Pagos con código QR (en línea y fuera de línea)
-- Transacciones en punto de venta (fuera de línea)
-- Pagos entre pares (en línea y fuera de línea)
-
-**Usado por billeteras y otras aplicaciones.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md)
-
-### SEP-0010 - Autenticación Stellar
-
-Define una forma estándar para que los clientes (como billeteras o exchanges) creen sesiones web autenticadas para usuarios que poseen una cuenta Stellar. Este SEP también admite la autenticación de usuarios de cuentas Stellar compartidas o agrupadas. Los clientes pueden usar cuentas muxed para distinguir usuarios o subcuentas de cuentas compartidas.
-
-Prueba que el usuario tiene una cuenta Stellar y que controla la cuenta con una clave maestra única o los firmantes suficientes necesarios.
-
-**Usado por billeteras y exchanges.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md)
-
-### SEP-0012 - API de KYC
-
-Permite compartir datos de KYC y define una forma estándar para que los clientes Stellar suban información de KYC y otros datos a los anchors y otros servicios. Este SEP fue creado con estos objetivos en mente:
-
-- Permitir a un cliente ingresar su información de KYC en su billetera una vez y usarla en muchos servicios sin volver a ingresar información manualmente
-- Manejar imagen y datos binarios
-- Soportar el conjunto de campos definidos en SEP-9
-- Soportar autenticación a través de SEP-10
-- Soportar la provisión de datos para SEP-6, SEP-24, SEP-31 y otros
-- Dar a los clientes control sobre sus datos al soportar la eliminación completa de datos
-
-**Usado por anchors, billeteras y otras aplicaciones.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)
-
-### SEP-0020 - Auto-Verificación de Nodos Validadores
-
-Define cómo los validadores se auto-verifican al establecer el dominio de su cuenta Stellar en su sitio web, donde publican información on-chain sobre su nodo y organización en un archivo stellar.toml. Esto permite a otros participantes descubrir otros nodos y agregarlos a sus conjuntos de quorum sin necesidad de una base de datos centralizada.
-
-**Usado por validadores.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md)
-
-### SEP-0024 - Depósito y Retirada Alojados
-
-Define la forma estándar para que los anchors y billeteras interactúen de manera interactiva en nombre de los usuarios. Esto significa que la aplicación del usuario debe abrir una vista web alojada por un anchor de terceros para que el usuario proporcione la información necesaria para completar la transacción.
-
-Los usuarios utilizan aplicaciones que implementan SEP-0024 para conectarse a negocios que aceptarán valor fuera de la cadena (como USD) a cambio de valor en la cadena (como USDC) y viceversa.
-
-El SEP-0006 es la alternativa al SEP-0024 que admite una solución de estilo API para el mismo caso de uso.
-
-**Usado por anchors, billeteras y otras aplicaciones.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md)
-
-### SEP-0030 - Recuperación de Cuenta: Recuperación Multipartita de Cuentas Stellar
-
-Define la API estándar que permite a un individuo (por ejemplo, un usuario o billetera) recuperar el acceso a una cuenta Stellar que posee después de que el individuo haya perdido su clave privada sin proporcionar ningún control de terceros sobre la cuenta. Usando este protocolo, el usuario o billetera registrará previamente la cuenta y un número de teléfono, correo electrónico u otra forma de autenticación con uno o más servidores que implementen el protocolo y agregará esos servidores como firmantes de la cuenta. Si se utilizan dos o más servidores con la configuración de firmantes adecuada, ningún servidor individual tendrá control sobre la cuenta, pero colectivamente, pueden ayudar al individuo a recuperar el acceso a la cuenta.
-
-El protocolo también permite a los individuos pasar el control de una cuenta Stellar a otro individuo.
-
-Este SEP permite los siguientes casos de uso para un usuario:
-
-- Recuperar: Recuperar acceso a cuentas Stellar para las que pueden haber perdido claves.
-- Compartir: Obtener acceso a cuentas Stellar que otro usuario tiene la intención de compartir con ellos.
-
-**Usado por billeteras y otras aplicaciones.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md)
-
-### SEP-0031 - API de Pagos Transnacionales
-
-Define el protocolo para que dos cuentas financieras que existen fuera de la red Stellar (anchors) interactúen entre sí.
-
-**Usado por anchors.**
-
-[Enlace a GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md)
-
-## Lista completa de propuestas activas
-
-| Número                                                                                    | Título                                                                                | Categoría |
-| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | --------- |
-| [SEP-0001](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) | Archivo de Información Stellar                                                        | Estándar  |
-| [SEP-0002](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0002.md) | Protocolo de Federación                                                               | Estándar  |
-| [SEP-0004](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0004.md) | Endpoint de Estado de Tx                                                              | Estándar  |
-| [SEP-0005](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md) | Métodos de Derivación de Claves para Cuentas Stellar                                  | Estándar  |
-| [SEP-0006](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) | API de depósito y retirada de fondos                                                  | Estándar  |
-| [SEP-0007](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) | Esquema URI para facilitar firmas delegadas                                           | Estándar  |
-| [SEP-0008](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) | Activos Regulados                                                                     | Estándar  |
-| [SEP-0009](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md) | Campos Estándar de KYC                                                                | Estándar  |
-| [SEP-0010](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) | Autenticación Stellar                                                                 | Estándar  |
-| [SEP-0011](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) | Txrep: Representación de Bajo Nivel Legible para Humanos de las Transacciones Stellar | Estándar  |
-| [SEP-0012](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md) | API de KYC                                                                            | Estándar  |
-| [SEP-0014](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0014.md) | Metadatos Dinámicos de Activos                                                        | Estándar  |
-| [SEP-0018](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0018.md) | Espacios de nombres para entradas de datos                                            | Estándar  |
-| [SEP-0020](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) | Autoverificación de nodos validador                                                   | Estándar  |
-| [SEP-0023](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md) | Strkeys de cuenta muxed                                                               | Estándar  |
-| [SEP-0024](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md) | Depósito y retirada de fondos alojados                                                | Estándar  |
-| [SEP-0028](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0028.md) | Codificación XDR Base64                                                               | Estándar  |
-| [SEP-0029](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0029.md) | Requisitos de memo de cuenta                                                          | Estándar  |
-| [SEP-0031](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md) | API de pagos transnacionales                                                          | Estándar  |
-| [SEP-0033](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0033.md) | Identicons para cuentas Stellar                                                       | Estándar  |
-| [SEP-0046](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0046.md) | Meta de contrato                                                                      | Estándar  |
-| [SEP-0048](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0048.md) | Especificación de interfaz de contrato                                                | Estándar  |
-| [SEP-0050](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0050.md) | Tokens No Fungibles                                                                   | Estándar  |
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-stack.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-stack.mdx
deleted file mode 100644
index c0ec79a2b2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/stellar-stack.mdx
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Aprender sobre los componentes principales y la arquitectura de la red Stellar
-sidebar_label: Stellar Stack
-description: Explorar los componentes principales y la arquitectura del Stack de Stellar, y ver cómo trabajan juntos para impulsar una red rápida, escalable y descentralizada.
-sidebar_position: 10
----
-
-# Stack de Stellar
-
-La Stack Stellar está compuesta por los siguientes componentes: las redes (Mainnet, Testnet y Futurenet), Stellar Core, Stellar RPC y los SDK, cada uno de los cuales desempeña un papel específico en proporcionar una infraestructura financiera resistente a fallos, accesible para cualquiera y lo suficientemente rápida y económica para atender casos de uso reales.
-
-![Stellar Stack](/assets/diagrams/stellar-tech-stack.png)
-
-## Redes
-
-Stellar tiene tres redes: la red pública (Mainnet, también llamada Pubnet o la red pública), la red de prueba (Testnet) y una red de desarrollo (Futurenet). Mainnet es la red principal utilizada por aplicaciones en producción. El Testnet es una red más pequeña, gratuita, mantenida por SDF, que funciona como el Mainnet pero no se conecta a dinero real y es el mejor lugar para que los desarrolladores prueben sus aplicaciones. Futurenet es una red de desarrollo que puedes usar para probar características más innovadoras.
-
-Lee más sobre las diferentes redes en la [sección de Redes](../../networks/README.mdx).
-
-## Stellar Core
-
-Stellar Core es el programa utilizado por los nodos individuales (o ordenadores) que componen la red. Stellar Core mantiene un libro mayor distribuido común y participa en un consenso para validar y procesar transacciones. Generalmente, los nodos alcanzan consenso, aplican un conjunto de transacciones y actualizan el ledger cada 5 a 7 segundos.
-
-Los nodos alcanzan consenso utilizando el Stellar Consensus Protocol, del cual puedes aprender más aquí: [Stellar Consensus Protocol](./stellar-consensus-protocol.mdx)
-
-Cualquiera puede ejecutar un nodo Stellar Core, pero no tienes que hacerlo para crear en Stellar. Te recomendamos que lo hagas si emites un activo y quieres asegurar la exactitud del libro mayor, si deseas participar en la gobernanza de la red votando sobre la versión del protocolo, tarifas mínimas y límites de recursos y libro mayor, y/o si deseas contribuir a la salud general y descentralización de Stellar. Consulta nuestro tutorial sobre cómo instalar, configurar y mantener tu propio nodo aquí: [Tutorial para Ejecutar un Nodo Validador](../../validators/README.mdx).
-
-## RPC
-
-El RPC de Stellar es un servidor JSON RPC que proporciona una interfaz para que los usuarios y aplicaciones interactúen con los contratos inteligentes en la blockchain de Stellar. Cuando una aplicación desea interactuar con contratos inteligentes, envía una solicitud al servidor RPC. El servidor interpreta estas solicitudes, las traduce a un formato comprensible por los nodos de la blockchain y las reenvía. Después de procesar las solicitudes, los nodos de la blockchain envían de vuelta los resultados. El servidor RPC recibe estos resultados y los envía de vuelta a la aplicación que los solicitó.
-
-SDF tiene puntos finales de RPC disponibles para Futurenet y Testnet. Estos servicios son gratuitos y son adecuados para el desarrollo y las pruebas.
-
-SDF no proporciona un punto final de RPC disponible públicamente para Mainnet. Los desarrolladores deben [seleccionar un proveedor del ecosistema](../../data/apis/rpc/providers.mdx) que funcione para su proyecto antes de migrar a Mainnet. En algunos casos, los proyectos pueden elegir ejecutar su propia instancia de RPC.
-
-## Horizon
-
-:::warning
-
-Horizon se acerca al final de su vida útil y finalmente será relegado en favor de Stellar RPC y las [APIs de Portfolio](../../data/indexers/README.mdx#portfolio-apis). Aunque continuará recibiendo actualizaciones para mantener la compatibilidad con los próximos lanzamientos del protocolo, no recibirá desarrollo de nuevas funcionalidades.
-
-:::
-
-Horizon es el servidor API RESTful HTTP orientado al cliente en la capa de plataforma que permite el acceso programático para enviar transacciones y consultar los datos históricos de la red. Actúa como la interfaz para las aplicaciones que quieren acceder a la red Stellar. Puedes comunicarte con Horizon usando un SDK, un navegador web o herramientas de comando simples como cURL.
-
-## SDKs
-
-Los SDKs simplifican parte del trabajo de acceder a Horizon y al RPC de Stellar convirtiendo los datos en formatos más amigables y permitiéndote programar en el lenguaje de tu elección. Los SDKs de Stellar te muestran cómo solicitar datos y crear y enviar transacciones. Los SDKs de Soroban te permiten escribir contratos inteligentes en Rust e interactuar con contratos inteligentes en una multitud de otros lenguajes.
-
-Mira la [biblioteca SDK](../../tools/sdks/README.mdx) de Stellar para acceder a nuestros SDK y su documentación.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/README.mdx
deleted file mode 100644
index de3cec3df7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Aprender sobre las transacciones en Stellar: ciclo de vida, operaciones y más"
-sidebar_position: 60
-sidebar_label: Operaciones y Transacciones
-description: "Aprender sobre las transacciones en Stellar: cómo funcionan, el ciclo de vida de la transacción, una lista de operaciones y cómo transfieren activos y ejecutan contratos inteligentes."
----
-
-# Operaciones y transacciones
-
-import DocCardList from "@theme/DocCardList";
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/list-of-operations.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/list-of-operations.mdx
deleted file mode 100644
index 377d6e133c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/list-of-operations.mdx
+++ /dev/null
@@ -1,773 +0,0 @@
----
-title: "Explorar Operaciones de Stellar: Cuentas, Pagos, Líneas de Confianza y Más"
-sidebar_label: Lista de Operaciones
-description: Explora la lista completa de operaciones de Stellar, incluyendo la creación de cuentas, la realización de pagos, la creación de líneas de confianza, todas las operaciones de contratos inteligentes y más.
-sidebar_position: 20
----
-
-# Lista de Operaciones
-
-Las operaciones son objetos que representan un cambio deseado en el ledger y se envían a la red agrupadas en una transacción. Para cada operación, hay un tipo de resultado exitoso o fallido. En caso de éxito, el usuario puede reunir información sobre el efecto de la operación. En caso de fallo, el usuario puede aprender más sobre el error.
-
-Aprende más sobre transacciones y operaciones en nuestra [sección de Operaciones y Transacciones](./operations-and-transactions.mdx).
-
-Actualmente hay 26 operaciones que puedes utilizar en la red Stellar, estas operaciones, sus definiciones, SDKs, umbrales, parámetros y errores se enumeran a continuación.
-
-:::note
-
-Todas estas operaciones tienen un parámetro opcional de cuenta fuente. Si el parámetro de cuenta fuente se omite, se considera que la cuenta fuente de la transacción es la cuenta fuente de la operación.
-
-:::
-
-## Crear cuenta
-
-Crea y financia una nueva cuenta con el saldo inicial especificado
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.createAccount) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/CreateAccountOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#CreateAccount)\
-**Umbral**: Medio\
-**Resultado**: `CreateAccountResult`\
-**Parámetros**:
-
-| Parámetro     | Tipo         | Descripción                                                                                |
-| ------------- | ------------ | ------------------------------------------------------------------------------------------ |
-| Destino       | ID de cuenta | Nueva dirección de cuenta que se crea y se financia.                                       |
-| Saldo inicial | entero       | Cantidad de XLM a enviar a la cuenta recién creada. Este XLM proviene de la cuenta fuente. |
-
-**Posibles errores**:
-
-| Error                       | Código | Descripción                                                                                                                                                                                                        |
-| --------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `CREAR_CUENTA_MALFORMADA`   | \-1    | El `destino` es inválido.                                                                                                                                                                                          |
-| `CREAR_CUENTA_BAJO_FONDO`   | \-2    | La cuenta fuente que realiza el comando no tiene suficientes fondos para darle al `destino` el `saldo inicial` de XLM y todavía mantener su reserva mínima de XLM más satisfacer sus obligaciones de venta de XLM. |
-| `CREAR_CUENTA_BAJO_RESERVA` | \-3    | Esta operación crearía una cuenta con menos del número mínimo de XLM que una cuenta debe mantener.                                                                                                                 |
-| `CREAR_CUENTA_YA_EXISTE`    | \-4    | La cuenta `destino` ya existe.                                                                                                                                                                                     |
-
-## Pago
-
-Envía una cantidad en un activo específico a una cuenta de destino
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.payment) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/PaymentOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#Payment)\
-**Umbral**: Medio\
-**Resultado**: `PaymentResult`\
-**Parámetros**:
-
-| Parámetros    | Tipo         | Descripción                                 |
-| ------------- | ------------ | ------------------------------------------- |
-| Destino       | ID de cuenta | Dirección de cuenta que recibe el pago.     |
-| Activo        | activo       | Activo a enviar a la cuenta de destino.     |
-| Cantidad      | entero       | Cantidad del activo mencionado a enviar.    |
-
-**Posibles errores**:
-
-| Error                    | Código | Descripción                                                                                                                                                                                                                                                                                                                 |
-| ------------------------ | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `PAGO_MALFORMADO`        | \-1    | La entrada para el pago es inválida.                                                                                                                                                                                                                                                                                        |
-| `PAGO_BAJO_FONDO`        | \-2    | La cuenta fuente (remitente) no tiene suficientes fondos para enviar `cantidad` y todavía satisfacer sus obligaciones de venta. Ten en cuenta que si envías XLM, entonces el remitente debe además mantener su reserva mínima de XLM. Nota que si se envía XLM, el remitente debe además mantener su reserva mínima de XLM. |
-| `PAGO_SRC_SIN_CONFIANZA` | \-3    | La cuenta fuente no confía en el emisor del activo que está tratando de enviar.                                                                                                                                                                                                                                             |
-| `PAGO_SRC_NO_AUTORIZADO` | \-4    | La cuenta fuente no está autorizada para enviar este pago.                                                                                                                                                                                                                                                                  |
-| `PAGO_SIN_DESTINO`       | \-5    | La cuenta receptora no existe. Nota que este error **no** se devolverá si la cuenta receptora es el emisor de `asset` (es decir, cuando el activo está siendo _quemado_).                                                                                                                                                   |
-| `PAGO_SIN_CONFIANZA`     | \-6    | El receptor no confía en el emisor del activo que se envía. Para más información, consulta la [sección de Activos](../stellar-data-structures/assets.mdx).                                                                                                                                                                  |
-| `PAGO_NO_AUTORIZADO`     | \-7    | La cuenta de destino no está autorizada por el emisor del activo para mantener el activo.                                                                                                                                                                                                                                   |
-| `PAGO_LÍNEA_LLENA`       | \-8    | La cuenta de destino (receptora) no tiene suficientes límites para recibir `cantidad` y aún satisfacer sus obligaciones de compra.                                                                                                                                                                                          |
-
-## Pago estricto de ruta
-
-Un pago en el que el activo enviado puede ser diferente del activo recibido; permite al usuario especificar la cantidad del activo a enviar
-
-Obtén más información sobre pagos por rutas: [Guía de Pagos por Rutas](../../../build/guides/transactions/path-payments.mdx)
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.pathPaymentStrictSend) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/PathPaymentStrictSendOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#PathPaymentStrictSend)\
-**Umbral**: Medio\
-**Resultado**: `PathPaymentStrictSendResult`\
-**Parámetros**:
-
-| Parámetros        | Tipo             | Descripción                                                                                                                                                                                                                                                                   |
-| ----------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Enviar activo     | activo           | El activo descontado de la cuenta del remitente.                                                                                                                                                                                                                              |
-| Enviar cantidad   | entero           | La cantidad de `enviar activo` a descontar (excluyendo tarifas).                                                                                                                                                                                                              |
-| Destino           | ID de cuenta     | ID de cuenta del destinatario.                                                                                                                                                                                                                                                |
-| Activo de destino | activo           | El activo que recibe la cuenta de destino.                                                                                                                                                                                                                                    |
-| Mínimo de destino | entero           | La cantidad mínima de `activo de destino` que la cuenta de destino puede recibir.                                                                                                                                                                                             |
-| Ruta              | lista de activos | Los activos (además de `enviar activo` y `activo de destino`) involucrados en las ofertas que toma la ruta. Por ejemplo, si solo puedes encontrar una ruta de USD a EUR a través de XLM y BTC, la ruta sería USD -> XLM -> BTC -> EUR y el campo `ruta` contendría XLM y BTC. |
-
-**Posibles errores**:
-
-| Error                                | Código | Descripción                                                                                                                                                                                                                                                                                                  |
-| ------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `PAGO_RUTA_ENVIAR_MALFORMADO`        | \-1    | La entrada a este pago de ruta es inválida.                                                                                                                                                                                                                                                                  |
-| `PAGO_RUTA_ENVIAR_BAJO_FONDO`        | \-2    | La cuenta fuente (remitente) no tiene suficientes fondos para enviar y aún satisfacer sus obligaciones de venta. Ten en cuenta que si envías XLM, entonces el remitente debe además mantener su reserva mínima de XLM. Nota que si se envía XLM, el remitente debe además mantener su reserva mínima de XLM. |
-| `PAGO_RUTA_ENVIAR_SRC_SIN_CONFIANZA` | \-3    | La cuenta fuente no confía en el emisor del activo que está tratando de enviar.                                                                                                                                                                                                                              |
-| `PAGO_RUTA_ENVIAR_SRC_NO_AUTORIZADO` | \-4    | La cuenta fuente no está autorizada para enviar este pago.                                                                                                                                                                                                                                                   |
-| `PAGO_RUTA_ENVIAR_SIN_DESTINO`       | \-5    | La cuenta de destino no existe.                                                                                                                                                                                                                                                                              |
-| `PAGO_RUTA_ENVIAR_SIN_CONFIANZA`     | \-6    | La cuenta de destino no confía en el emisor del activo que se envía. Para más información, consulta la [sección de Activos](../stellar-data-structures/assets.mdx).                                                                                                                                          |
-| `PAGO_RUTA_ENVIAR_NO_AUTORIZADO`     | \-7    | La cuenta de destino no está autorizada por el emisor del activo para mantener el activo.                                                                                                                                                                                                                    |
-| `PAGO_RUTA_ENVIAR_LÍNEA_LLENA`       | \-8    | La cuenta de destino no tiene límites suficientes para recibir `importe de destino` y aún satisfacer sus obligaciones de compra.                                                                                                                                                                             |
-| `PAGO_RUTA_ENVIAR_MUY_POCAS_OFERTAS` | \-10   | No hay una ruta de ofertas conectando el `enviar activo` y el `activo de destino`. Stellar solo considera rutas de longitud 5 o más cortas.                                                                                                                                                                  |
-| `PAGO_RUTA_ENVIAR_OFERTA_CROSS_SELF` | \-11   | El pago cruzaría una de sus propias ofertas.                                                                                                                                                                                                                                                                 |
-| `PAGO_RUTA_ENVIAR_BAJO_DESTMIN`      | \-12   | Las rutas que podrían enviar `importe de destino` de `activo de destino` serían insuficientes para `mínimo de destino`.                                                                                                                                                                                      |
-
-## Pago estricto de ruta recibir
-
-Un pago en el que el activo recibido puede ser diferente del activo enviado; permite al usuario especificar la cantidad del activo recibido
-
-Obtén más información sobre pagos por rutas: [Guía de Pagos por Rutas](../../../build/guides/transactions/path-payments.mdx)
-
-**SDKs**: [JavaScript](https://stellar.github.io/js-stellar-sdk/Operation.html#.pathPaymentStrictReceive) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/PathPaymentStrictReceiveOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#PathPaymentStrictReceive)\
-**Umbral**: Medio\
-**Resultado**: `PathPaymentStrictReceiveResult`\
-**Parámetros**:
-
-| Parámetros          | Tipo             | Descripción                                                                                                                                                                                                                                                                        |
-| ------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Enviar activo       | activo           | El activo descontado de la cuenta del remitente.                                                                                                                                                                                                                                   |
-| Enviar máximo       | entero           | La cantidad máxima de `enviar activo` a descontar (excluyendo tarifas).                                                                                                                                                                                                            |
-| Destino             | ID de cuenta     | ID de cuenta del destinatario.                                                                                                                                                                                                                                                     |
-| Activo de destino   | activo           | El activo que recibe la cuenta de destino.                                                                                                                                                                                                                                         |
-| Cantidad de destino | entero           | La cantidad de `activo de destino` que recibe la cuenta de destino.                                                                                                                                                                                                                |
-| Ruta                | lista de activos | Los activos (además de `activo de envío` y `activo de destino`) involucrados en las ofertas que toma la ruta. Por ejemplo, si solo puedes encontrar una ruta desde USD a EUR a través de XLM y BTC, la ruta sería USD -> XLM -> BTC -> EUR y el campo `ruta` contendría XLM y BTC. |
-
-**Posibles errores**:
-
-| Error                                 | Código | Descripción                                                                                                                                                                                                   |
-| ------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `PAGO_RUTA_RECIBIR_MALFORMADO`        | \-1    | La entrada a este pago de ruta no es válida.                                                                                                                                                                  |
-| `PAGO_RUTA_RECIBIR_BAJO_FONDO`        | \-2    | La cuenta de origen (remitente) no tiene suficientes fondos para enviar y aún así satisfacer sus obligaciones de venta. Nota que si se envía XLM, el remitente debe además mantener su reserva mínima de XLM. |
-| `PAGO_RUTA_RECIBIR_SRC_SIN_CONFIANZA` | \-3    | La cuenta de origen no confía en el emisor del activo que está tratando de enviar.                                                                                                                            |
-| `PAGO_RUTA_RECIBIR_SRC_NO_AUTORIZADO` | \-4    | La cuenta de origen no está autorizada para enviar este pago.                                                                                                                                                 |
-| `PAGO_RUTA_RECIBIR_SIN_DESTINO`       | \-5    | La cuenta de destino no existe.                                                                                                                                                                               |
-| `PAGO_RUTA_RECIBIR_SIN_CONFIANZA`     | \-6    | La cuenta de destino no confía en el emisor del activo que se está enviando. Para más información, consulta la [sección de Activos](../stellar-data-structures/assets.mdx).                                   |
-| `PAGO_RUTA_RECIBIR_NO_AUTORIZADO`     | \-7    | La cuenta de destino no está autorizada por el emisor del activo para mantener el activo.                                                                                                                     |
-| `PAGO_RUTA_RECIBIR_LÍNEA_LLENA`       | \-8    | La cuenta de destino no tiene límites suficientes para recibir `cantidad de destino` y aún así satisfacer sus obligaciones de compra.                                                                         |
-| `PAGO_RUTA_RECIBIR_MUY_POCAS_OFERTAS` | \-10   | No hay ninguna ruta de ofertas que conecte el `activo de envío` y el `activo de destino`. Stellar solo considera rutas de longitud 5 o menor.                                                                 |
-| `PAGO_RUTA_RECIBIR_OFERTA_CROSS_SELF` | \-11   | El pago cruzaría una de sus propias ofertas.                                                                                                                                                                  |
-| `PAGO_RUTA_RECIBIR_SOBRE_SENDMAX`     | \-12   | Las rutas que podrían enviar `cantidad de destino` de `activo de destino` excederían `máx. de envío`.                                                                                                         |
-
-## Gestionar oferta de compra
-
-Crea, actualiza o elimina una oferta para comprar una cantidad específica de un activo por otro
-
-Obtén más información sobre ofertas de venta pasivas: [Fondos de Liquidez en Stellar: SDEX y Fondos de Liquidez](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.manageBuyOffer) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/ManageBuyOfferOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#ManageBuyOffer)\
-**Umbral**: Medio\
-**Resultado**: `ManageBuyOfferResult`\
-**Parámetros**:
-
-| Parámetros   | Tipo                      | Descripción                                                                                                                                |
-| ------------ | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| Venta        | activo                    | Activo que el creador de la oferta está vendiendo.                                                                                         |
-| Compra       | activo                    | Activo que el creador de la oferta está comprando.                                                                                         |
-| Cantidad     | entero                    | Cantidad de `compras` que se está comprando. Establecer en `0` si deseas eliminar una oferta existente.                                    |
-| Precio       | \{numerador, denominador} | Precio de 1 unidad de `compras` en términos de `ventas`. Por ejemplo, si quisieras comprar 30 XLM y vender 5 BTC, el precio sería \{5,30}. |
-| ID de oferta | entero sin signo          | El ID de la oferta. `0` para nueva oferta. Establecer en el ID de oferta existente para actualizar o eliminar.                             |
-
-**Posibles errores**:
-
-| Error                                           | Código | Descripción                                                                                                                                                                                                                                                                                                      |
-| ----------------------------------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `GESTIONAR_OFERTA_COMPRA_MALFORMADA`            | \-1    | La entrada es incorrecta y resultaría en una oferta no válida.                                                                                                                                                                                                                                                   |
-| `GESTIONAR_OFERTA_COMPRA_VENDER_SIN_CONFIANZA`  | \-2    | La cuenta que crea la oferta no tiene una línea de confianza para el activo que está vendiendo.                                                                                                                                                                                                                  |
-| `GESTIONAR_OFERTA_COMPRA_COMPRAR_SIN_CONFIANZA` | \-3    | La cuenta que crea la oferta no tiene una línea de confianza para el activo que está comprando.                                                                                                                                                                                                                  |
-| `GESTIONAR_OFERTA_COMPRA_COMPRAR_NO_AUTORIZADO` | \-4    | La cuenta que crea la oferta no está autorizada a vender este activo.                                                                                                                                                                                                                                            |
-| `GESTIONAR_OFERTA_COMPRA_VENDER_NO_AUTORIZADO`  | \-5    | La cuenta que crea la oferta no está autorizada a comprar este activo.                                                                                                                                                                                                                                           |
-| `GESTIONAR_OFERTA_COMPRA_LÍNEA_LLENA`           | \-6    | La cuenta que crea la oferta no tiene suficientes límites para recibir `compras` y aún así satisfacer sus obligaciones de compra.                                                                                                                                                                                |
-| `GESTIONAR_OFERTA_COMPRA_BAJO_FONDO`            | \-7    | La cuenta que crea la oferta no tiene suficientes límites para enviar `ventas` y aún satisfacer sus obligaciones de venta. Ten en cuenta que si vendes XLM, la cuenta debe además mantener su reserva mínima de XLM, que se calcula asumiendo que esta oferta no se ejecutará completamente de inmediato.        |
-| `GESTIONAR_OFERTA_COMPRA_CROSS_SELF`            | \-8    | La cuenta tiene una oferta opuesta de precio igual o menor activa, por lo que la cuenta que crea esta oferta cruzaría inmediatamente.                                                                                                                                                                            |
-| `GESTIONAR_OFERTA_COMPRA_NO_ENCONTRADA`         | \-11   | No se puede encontrar una oferta con ese `ID de oferta`.                                                                                                                                                                                                                                                         |
-| `GESTIONAR_OFERTA_COMPRA_BAJA_RESERVA`          | \-12   | La cuenta que crea esta oferta no tiene suficiente XLM para satisfacer el aumento de la reserva mínima de XLM causado por agregar una subentrada y seguir satisfaciendo sus obligaciones de venta de XLM. Por cada oferta que una cuenta crea, la cantidad mínima de XLM que esa cuenta debe mantener aumentará. |
-
-## Gestionar oferta de venta
-
-Crea, actualiza o elimina una oferta para vender una cantidad específica de un activo por otro
-
-Obtén más información sobre ofertas de venta pasivas: [Fondos de Liquidez en Stellar: SDEX y Fondos de Liquidez](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.manageSellOffer) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/ManageSellOfferOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#ManageSellOffer)\
-**Umbral**: Medio\
-**Resultado**: `ManageSellOfferResult`\
-**Parámetros**:
-
-| Parámetros   | Tipo                      | Descripción                                                                                                                                |
-| ------------ | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| Venta        | activo                    | Activo que el creador de la oferta está vendiendo.                                                                                         |
-| Compra       | activo                    | Activo que el creador de la oferta está comprando.                                                                                         |
-| Cantidad     | entero                    | Cantidad de `ventas` que se está vendiendo. Establecer en `0` si deseas eliminar una oferta existente.                                     |
-| Precio       | \{numerador, denominador} | Precio de 1 unidad de `ventas` en términos de `compras`. Por ejemplo, si quisieras vender 30 XLM y comprar 5 BTC, el precio sería \{5,30}. |
-| ID de oferta | entero sin signo          | El ID de la oferta. `0` para nueva oferta. Establecer en el ID de oferta existente para actualizar o eliminar.                             |
-
-**Posibles errores**:
-
-| Error                                          | Código | Descripción                                                                                                                                                                                                                                                                                                    |
-| ---------------------------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `GESTIONAR_OFERTA_VENTA_MALFORMADA`            | \-1    | La entrada es incorrecta y resultaría en una oferta no válida.                                                                                                                                                                                                                                                 |
-| `GESTIONAR_OFERTA_VENTA_VENDER_SIN_CONFIANZA`  | \-2    | La cuenta que crea la oferta no tiene una línea de confianza para el activo que está vendiendo.                                                                                                                                                                                                                |
-| `GESTIONAR_OFERTA_VENTA_COMPRAR_SIN_CONFIANZA` | \-3    | La cuenta que crea la oferta no tiene una línea de confianza para el activo que está comprando.                                                                                                                                                                                                                |
-| `GESTIONAR_OFERTA_VENTA_VENDER_NO_AUTORIZADO`  | \-4    | La cuenta que crea la oferta no está autorizada a vender este activo.                                                                                                                                                                                                                                          |
-| `GESTIONAR_OFERTA_VENTA_COMPRAR_NO_AUTORIZADO` | \-5    | La cuenta que crea la oferta no está autorizada a comprar este activo.                                                                                                                                                                                                                                         |
-| `GESTIONAR_OFERTA_VENTA_LÍNEA_LLENA`           | \-6    | La cuenta que crea la oferta no tiene suficientes límites para recibir `compras` y aún así satisfacer sus obligaciones de compra.                                                                                                                                                                              |
-| `GESTIONAR_OFERTA_VENTA_BAJO_FONDO`            | \-7    | La cuenta que crea la oferta no tiene suficientes límites para enviar `ventas` y aún así satisfacer sus obligaciones de venta. Ten en cuenta que si vendes XLM, la cuenta debe además mantener su reserva mínima de XLM, que se calcula asumiendo que esta oferta no se ejecutará completamente de inmediato.  |
-| `GESTIONAR_OFERTA_VENTA_CROSS_SELF`            | \-8    | La cuenta tiene una oferta opuesta de precio igual o menor activa, por lo que la cuenta que crea esta oferta cruzaría inmediatamente.                                                                                                                                                                          |
-| `GESTIONAR_OFERTA_VENTA_NO_ENCONTRADA`         | \-11   | No se puede encontrar una oferta con ese `ID de oferta`.                                                                                                                                                                                                                                                       |
-| `ADMINISTRAR_OFERTA_DE_VENTA_BAJO_RESERVA`     | \-12   | La cuenta que crea esta oferta no tiene suficiente XLM para satisfacer el aumento de la reserva mínima de XLM causado por agregar una subentrada y aún así satisfacer sus obligaciones de venta de XLM. Por cada oferta que una cuenta crea, la cantidad mínima de XLM que esa cuenta debe mantener aumentará. |
-
-## Crear oferta de venta pasiva
-
-Crea una oferta para vender un activo por otro sin aceptar una oferta inversa de precio igual
-
-Obtén más información sobre ofertas de venta pasivas: [Fondos de Liquidez en Stellar: SDEX y Fondos de Liquidez](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
-
-**SDKs**: [JavaScript](https://stellar.github.io/js-stellar-sdk/Operation.html#.createPassiveSellOffer) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/CreatePassiveSellOfferOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#CreatePassiveSellOffer)\
-**Umbral**: Medio\
-**Resultado**: `ManageSellOfferResult`\
-**Parámetros**:
-
-| Parámetros | Tipo                      | Descripción                                                                                                                                |
-| ---------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| Venta      | activo                    | Activo que el creador de la oferta está vendiendo.                                                                                         |
-| Compra     | activo                    | Activo que el creador de la oferta está comprando.                                                                                         |
-| Cantidad   | entero                    | Cantidad de `ventas` que se está vendiendo.                                                                                                |
-| Precio     | \{numerador, denominador} | Precio de 1 unidad de `ventas` en términos de `compras`. Por ejemplo, si quisieras vender 30 XLM y comprar 5 BTC, el precio sería \{5,30}. |
-
-**Posibles errores**:
-
-| Error                                              | Código | Descripción                                                                                                                                                                                                                                                                                                    |
-| -------------------------------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ADMINISTRAR_OFERTA_DE_VENTA_MAL_FORMADA`          | \-1    | La entrada es incorrecta y resultaría en una oferta no válida.                                                                                                                                                                                                                                                 |
-| `ADMINISTRAR_OFERTA_DE_VENTA_NO_CONFIABLE`         | \-2    | La cuenta que crea la oferta no tiene una línea de confianza para el activo que está vendiendo.                                                                                                                                                                                                                |
-| `ADMINISTRAR_OFERTA_DE_VENTA_NO_CONFIABLE_COMPRA`  | \-3    | La cuenta que crea la oferta no tiene una línea de confianza para el activo que está comprando.                                                                                                                                                                                                                |
-| `ADMINISTRAR_OFERTA_DE_VENTA_NO_AUTORIZADA`        | \-4    | La cuenta que crea la oferta no está autorizada para vender este activo.                                                                                                                                                                                                                                       |
-| `ADMINISTRAR_OFERTA_DE_VENTA_NO_AUTORIZADA_COMPRA` | \-5    | La cuenta que crea la oferta no está autorizada para comprar este activo.                                                                                                                                                                                                                                      |
-| `ADMINISTRAR_OFERTA_DE_VENTA_LÍNEA_LLENA`          | \-6    | La cuenta que crea la oferta no tiene límites suficientes para recibir `buying` y aún así satisfacer sus obligaciones de compra.                                                                                                                                                                               |
-| `ADMINISTRAR_OFERTA_DE_VENTA_FONDOS_INSUFICIENTES` | \-7    | La cuenta que crea la oferta no tiene límites suficientes para enviar `selling` y aún así satisfacer sus obligaciones de venta. Ten en cuenta que si vendes XLM, la cuenta debe mantener además su reserva mínima de XLM, que se calcula asumiendo que esta oferta no se ejecutará completamente de inmediato. |
-| `ADMINISTRAR_OFERTA_DE_VENTA_CRUZARSE_A_SÍ_MISMO`  | \-8    | La cuenta tiene una oferta opuesta de igual o menor precio activa, por lo que la cuenta que crea esta oferta se cruzaría inmediatamente a sí misma.                                                                                                                                                            |
-| `ADMINISTRAR_OFERTA_DE_VENTA_NO_ENCONTRADA`        | \-11   | No se puede encontrar una oferta con ese `offerID`.                                                                                                                                                                                                                                                            |
-| `ADMINISTRAR_OFERTA_DE_VENTA_BAJO_RESERVA`         | \-12   | La cuenta que crea esta oferta no tiene suficiente XLM para satisfacer el aumento de la reserva mínima de XLM causado por agregar una subentrada y aún satisfacer sus obligaciones de venta de XLM. Por cada oferta que crea una cuenta, la cantidad mínima de XLM que esa cuenta debe mantener aumentará.     |
-
-## Establecer opciones
-
-Establecer opciones para una cuenta como flags, destino de inflación, firmantes, dominio principal y peso de la clave maestra
-
-Obtén más información sobre flags: [Sección de Flags](../../../tokens/control-asset-access.mdx#controlling-access-to-an-asset-with-flags)\
-Obtén más información sobre el dominio principal: [Propuestas del Ecosistema Stellar SEP-0001](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)\
-Obtén más información sobre operaciones de signatarios y peso de claves: [Sección de Firma y Multifirma](../../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)\
-**Umbral**: Alto (cuando se actualizan los signatarios u otros umbrales) o Medio (cuando se actualiza todo lo demás)\
-**Resultado**: `SetOptionsResult`\
-**Parámetros**:
-
-| Parámetros           | Tipo                  | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| -------------------- | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Destino de Inflación | ID de cuenta          | Cuenta del destino de inflación.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| Eliminar flags       | entero                | Indica qué [cuenta](../stellar-data-structures/accounts.mdx) flags eliminar. Estas banderas a nivel de cuenta son utilizadas principalmente por los emisores de activos. Para detalles sobre las banderas, consulta la [página de Consideraciones de Diseño de Activos](../../../tokens/control-asset-access.mdx). La máscara de bits entera se resta de los flags existentes de la cuenta. Esto permite establecer bits específicos sin conocimiento de los flags existentes.                                              |
-| Establecer flags     | entero                | Indica qué [cuenta](../stellar-data-structures/accounts.mdx) flags establecer. Estas banderas a nivel de cuenta son utilizadas principalmente por los emisores de activos. Para detalles sobre las banderas, consulta la [página de Consideraciones de Diseño de Activos](../../../tokens/control-asset-access.mdx#controlling-access-to-an-asset-with-flags). La máscara de bits entero se suma a las banderas existentes de la cuenta. Esto permite establecer bits específicos sin conocimiento de los flags existentes. |
-| Peso maestro         | entero                | Un número del 0 al 255 (inclusive) que representa el peso de la clave maestra. Si el peso de la clave maestra se actualiza a 0, se desactiva efectivamente.                                                                                                                                                                                                                                                                                                                                                                 |
-| Umbral bajo          | entero                | Un número del 0 al 255 (inclusive) que representa el umbral que esta cuenta establece para todas las operaciones que realiza y que tienen [un umbral bajo](../../fundamentals/transactions/signatures-multisig.mdx).                                                                                                                                                                                                                                                                                                        |
-| Umbral medio         | entero                | Un número del 0 al 255 (inclusive) que representa el umbral que esta cuenta establece para todas las operaciones que realiza y que tienen [un umbral medio](../../fundamentals/transactions/signatures-multisig.mdx).                                                                                                                                                                                                                                                                                                       |
-| Umbral alto          | entero                | Un número del 0 al 255 (inclusive) que representa el umbral que esta cuenta establece para todas las operaciones que realiza y que tienen [un umbral alto](../../fundamentals/transactions/signatures-multisig.mdx).                                                                                                                                                                                                                                                                                                        |
-| Dominio de casa      | cadena                | Establece el dominio de casa de una cuenta. See [Federation](../../glossary.mdx#federation).                                                                                                                                                                                                                                                                                                                                                                                                                                |
-| Firmante             | \{Public Key, weight} | Agregar, actualizar o eliminar un firmante de una cuenta. El peso del firmante es un número del 0 al 255 (inclusive). El firmante se elimina si el peso es 0.                                                                                                                                                                                                                                                                                                                                                               |
-
-**Posibles errores**:
-
-| Error                                                 | Código | Descripción                                                                                                                                                                                                                                                                                    |
-| ----------------------------------------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ESTABLECER_OPCIONES_BAJO_RESERVA`                    | \-1    | Esta cuenta no tiene suficiente XLM para satisfacer el aumento de la reserva mínima de XLM causado por agregar una subentrada y aún satisfacer sus obligaciones de venta de XLM. Por cada nuevo firmante agregado a una cuenta, la reserva mínima de XLM que esa cuenta debe mantener aumenta. |
-| `ESTABLECER_OPCIONES_DE_MÁS_FIRMANTES`                | \-2    | 20 es el número máximo de firmantes que una cuenta puede tener, y agregar otro firmante excedería eso.                                                                                                                                                                                         |
-| `ESTABLECER_OPCIONES_FLAJOS_ERRÓNEOS`                 | \-3    | Los flags establecidos y/o eliminados son inválidos por sí mismos o en combinación.                                                                                                                                                                                                            |
-| `ESTABLECER_OPCIONES_INFLACIÓN_INVÁLIDA`              | \-4    | La cuenta de destino establecida en el campo `inflation` no existe.                                                                                                                                                                                                                            |
-| `ESTABLECER_OPCIONES_NO_SE_PUEDE_CAMBIAR`             | \-5    | Esta cuenta ya no puede cambiar la opción que desea cambiar.                                                                                                                                                                                                                                   |
-| `ESTABLECER_OPCIONES_FLAJO_DESCONOCIDO`               | \-6    | La cuenta está tratando de establecer un flag que es desconocido.                                                                                                                                                                                                                              |
-| `ESTABLECER_OPCIONES_LIMITE_DE_UMBRAL_FUERA_DE_RANGO` | \-7    | El valor para un peso de clave o umbral es inválido.                                                                                                                                                                                                                                           |
-| `ESTABLECER_OPCIONES_FIRMANTE_ERRÓNEO`                | \-8    | Cualquier firmante adicional agregado a la cuenta no puede ser la clave maestra.                                                                                                                                                                                                               |
-| `ESTABLECER_OPCIONES_DOMINIO_HOGAR_INVÁLIDO`          | \-9    | El dominio de casa está mal formado.                                                                                                                                                                                                                                                           |
-
-## Cambiar confianza
-
-Crea, actualiza o elimina una línea de confianza
-
-Aprende más sobre líneas de confianza: [sección de líneas de confianza](../stellar-data-structures/accounts.mdx#trustlines)
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.changeTrust) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/ChangeTrustOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#ChangeTrust)\
-**Umbral**: Medio\
-**Resultado**: `ChangeTrustResult`\
-**Parámetros**:
-
-| Parámetros | Tipo             | Descripción                                                                                                                                           |
-| ---------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Línea      | ChangeTrustAsset | El activo de la línea de confianza. Por ejemplo, si un usuario extiende una línea de confianza de hasta 200 USD a un anchor, la `line` es USD:anchor. |
-| Límite     | entero           | El límite de la línea de confianza. En el ejemplo anterior, el `limit` sería 200.                                                                     |
-
-**Posibles errores**:
-
-| Error                                                     | Código | Descripción                                                                                                                                                                                                                                                                                                             |
-| --------------------------------------------------------- | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `CAMBIO_DE_CONFIANZA_MAL_FORMADO`                         | \-1    | La entrada a esta operación es inválida.                                                                                                                                                                                                                                                                                |
-| `CAMBIO_DE_CONFIANZA_NO_HAY_EMISOR`                       | \-2    | No se puede encontrar al emisor del activo.                                                                                                                                                                                                                                                                             |
-| `CAMBIO_DE_CONFIANZA_LIMITE_INVÁLIDO`                     | \-3    | El `limit` no es suficiente para mantener el saldo actual de la línea de confianza y aún satisfacer sus obligaciones de compra. Este error ocurre al intentar eliminar una línea de confianza con un saldo de activo distinto de cero.                                                                                  |
-| `CAMBIO_DE_CONFIANZA_BAJO_RESERVA`                        | \-4    | Esta cuenta no tiene suficiente XLM para satisfacer el aumento de la reserva mínima de XLM causado por la adición de una subentrada y aún así satisfacer sus responsabilidades de venta de XLM. Por cada nueva línea de confianza agregada a una cuenta, la reserva mínima de XLM que esa cuenta debe mantener aumenta. |
-| `CAMBIO_DE_CONFIANZA_NO_SE_PUEDE_AUTOCONFIANZAR`          | \-5    | La cuenta de origen intentó crear una línea de confianza para sí misma, lo cual no está permitido.                                                                                                                                                                                                                      |
-| `CAMBIO_DE_CONFIANZA_FILA_DE_CONFIANZA_FALTANTE`          | \-6    | Falta la línea de confianza del activo para el fondo de liquidez.                                                                                                                                                                                                                                                       |
-| `CAMBIO_DE_CONFIANZA_NO_SE_PUEDE_ELIMINAR`                | \-7    | La línea de confianza del activo todavía está referenciada por un fondo de liquidez.                                                                                                                                                                                                                                    |
-| `CAMBIO_DE_CONFIANZA_NO_AUTORIZADO_MANTENER_LIABILIDADES` | \-8    | La línea de confianza del activo está desautorizada.                                                                                                                                                                                                                                                                    |
-
-## Permitir confianza
-
-Actualiza la bandera autorizada de una línea de confianza existente. Esta operación solo puede ser realizada por el emisor del activo
-
-:::warning
-
-Esta operación está obsoleta a partir del Protocolo 17; prefiere la operación [_SetTrustlineFlags_](#set-trustline-flags).
-
-:::
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.allowTrust) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/AllowTrustOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#AllowTrust)\
-**Umbral**: Bajo\
-**Resultado**: `AllowTrustResult`\
-**Parámetros**:
-
-| Parámetros | Tipo             | Descripción                                                                                                                                                                                                                                 |
-| ---------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Confiador  | ID de cuenta     | La cuenta que tiene una línea de confianza establecida para el activo.                                                                                                                                                                      |
-| Tipo       | código de activo | El código de activo de un máximo de 4 o 12 caracteres de la línea de confianza que la cuenta de origen está autorizando. Por ejemplo, si una cuenta emisora quiere permitir que otra cuenta mantenga su crédito en USD, el `tipo` es `USD`. |
-| Autorizar  | entero           | Bandera que indica si la línea de confianza está autorizada. `1` si la cuenta está autorizada para transaccionar con el activo. `2` si la cuenta está autorizada para mantener ofertas, pero no para realizar otras transacciones           |
-
-**Posibles errores**:
-
-| Error                                           | Código | Descripción                                                                                                                                                                          |
-| ----------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `PERMITIR_CONFIANZA_MAL_FORMADA`                | \-1    | El activo especificado en `tipo` no es válido. Además, este error ocurre cuando se especifica el activo nativo.                                                                      |
-| `PERMITIR_CONFIANZA_NO_HAY_LINEA_DE_CONFIANZA`  | \-2    | El `confiador` no tiene una línea de confianza con el emisor que realiza esta operación.                                                                                             |
-| `PERMITIR_CONFIANZA_NO_REQUERIDA`               | \-3    | La cuenta de origen (emisor que realiza esta operación) no requiere confianza. En otras palabras, no tiene la bandera `AUTH_REQUIRED_FLAG` establecida.                              |
-| `PERMITIR_CONFIANZA_NO_SE_PUEDE_REVOKAR`        | \-4    | La cuenta de origen está intentando revocar la línea de confianza del `confiador`, pero no puede hacerlo.                                                                            |
-| `PERMITIR_CONFIANZA_NO_SE_PUEDE_AUTOCONFIANZAR` | \-5    | La cuenta de origen intentó permitir una línea de confianza para sí misma, lo cual no está permitido porque una cuenta no puede crear una línea de confianza consigo misma.          |
-| `PERMITIR_CONFIANZA_BAJO_RESERVA`               | \-6    | Los saldos reclamables no pueden ser creados tras la revocación de líneas de confianza de activos (o acciones de fondos) asociadas con un fondo de liquidez debido a reservas bajas. |
-
-## Fusión de cuentas
-
-Transfiere el saldo de XLM de una cuenta a otra cuenta y elimina la cuenta de origen del ledger.
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.accountMerge) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/AccountMergeOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#AccountMerge)\
-**Umbral**: Alto\
-**Resultado**: `AccountMergeResult`\
-**Parámetros**:
-
-| Parámetros | Tipo         | Descripción                                                           |
-| ---------- | ------------ | --------------------------------------------------------------------- |
-| Destino    | ID de cuenta | La cuenta que recibe el saldo restante de XLM de la cuenta de origen. |
-
-**Posibles errores**:
-
-| Error                                                   | Código | Descripción                                                                                                                                                                        |
-| ------------------------------------------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `FUSIÓN_DE_CUENTA_MAL_FORMADA`                          | \-1    | La operación está malformada porque la cuenta de origen no puede fusionarse consigo misma. La `destino` debe ser una cuenta diferente. El `destino` debe ser una cuenta diferente. |
-| `FUSIÓN_DE_CUENTA_NO_HAY_CUENTA`                        | \-2    | La cuenta `destino` no existe.                                                                                                                                                     |
-| `FUSIÓN_DE_CUENTA_CONJUNTO_INMUTABLE`                   | \-3    | La cuenta de origen tiene la bandera `AUTH_IMMUTABLE` establecida.                                                                                                                 |
-| `FUSIÓN_DE_CUENTA_TIENE_SUBENTRADAS`                    | \-4    | La cuenta de origen tiene líneas de confianza/ofertas.                                                                                                                             |
-| `FUSIÓN_DE_CUENTA_NUMERO_DE_SECUENCIA_DEMASIADO_LEJANO` | \-5    | El número de secuencia de la cuenta de origen es demasiado alto. Debe ser menor que `(ledgerSeq << 32) = (ledgerSeq * 0x100000000)`.                                               |
-| `FUSIÓN_DE_CUENTA_DESTINO_LLENO`                        | \-6    | La cuenta `destino` no puede recibir el saldo de la cuenta de origen y aún así satisfacer sus responsabilidades de compra de lumen.                                                |
-| `FUSIÓN_DE_CUENTA_ES_ESPATOS`                           | \-7    | La cuenta de origen es un patrocinador.                                                                                                                                            |
-
-## Administrar datos
-
-Establece, modifica o elimina una entrada de datos (par nombre/valor) que está adjunta a una cuenta.
-
-Aprende más sobre entradas y subentradas: [Sección de cuentas](../stellar-data-structures/accounts.mdx#subentries)
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.manageData) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/ManageDataOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#ManageData)\
-**Umbral**: Medio\
-**Resultado**: `ManageDataResult`\
-**Parámetros**:
-
-| Parámetros | Tipo           | Descripción                                                                                                                                                                                     |
-| ---------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Nombre     | cadena         | Cadena de hasta 64 bytes de longitud. Si este es un nuevo nombre, se añadirá el par nombre/valor dado a la cuenta. Si este nombre ya está presente, entonces el valor asociado será modificado. |
-| Valor      | datos binarios | (opcional) Si no está presente, entonces el nombre existente será eliminado. Si está presente, entonces este valor será establecido en la entrada de datos. De hasta 64 bytes de longitud.      |
-
-**Posibles errores**:
-
-| Error                                    | Código | Descripción                                                                                                                                                                                                                                                                                                           |
-| ---------------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ADMINISTRAR_DATOS_NO_SOPORTADOS_AÚN`    | \-1    | La red aún no ha cambiado a este cambio de protocolo. Este error significa que la red no soporta esta función todavía.                                                                                                                                                                                                |
-| `ADMINISTRAR_DATOS_NOMBRE_NO_ENCONTRADO` | \-2    | Intentando eliminar una entrada de datos que no está allí. Esto sucederá si el nombre está establecido (y el valor no) pero la cuenta no tiene una entrada de datos con ese nombre.                                                                                                                                   |
-| `ADMINISTRAR_DATOS_BAJO_RESERVA`         | \-3    | Esta cuenta no tiene suficiente XLM para satisfacer el aumento de la reserva mínima de XLM causado por la adición de una subentrada y aún así satisfacer sus responsabilidades de venta de XLM. Por cada nueva entrada de datos agregada a una cuenta, la reserva mínima de XLM que esa cuenta debe mantener aumenta. |
-| `ADMINISTRAR_DATOS_NOMBRE_INVÁLIDO`      | \-4    | Nombre no es una cadena válida.                                                                                                                                                                                                                                                                                       |
-
-## Aumentar secuencia
-
-Aumenta hacia adelante el número de secuencia de la cuenta de origen al número de secuencia dado, invalidando cualquier transacción con un número de secuencia más pequeño.
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.bumpSequence) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/BumpSequenceOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#BumpSequence)\
-**Umbral**: Bajo\
-**Resultado**: `BumpSequenceResult`\
-**Parámetros**:
-
-| Parámetros | Tipo                | Descripción                                                                       |
-| ---------- | ------------------- | --------------------------------------------------------------------------------- |
-| bumpTo     | Número de secuencia | valor deseado para el número de secuencia de la cuenta de origen de la operación. |
-
-**Posibles errores**:
-
-| Error                                  | Código | Descripción                                                                                                                                                    |
-| -------------------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `AUMENTAR_SECUENCIA_SECUENCIA_ERRÓNEA` | \-1    | El número de secuencia `bumpTo` especificado no es un número de secuencia válido. Debe estar entre 0 y `INT64_MAX` (9223372036854775807 o 0x7fffffffffffffff). |
-
-## Crear saldo reclamable
-
-Mueve una cantidad de activo de la cuenta fuente de la operación a una nueva ClaimableBalanceEntry.
-
-Obtén más información sobre balances reclamables: [Guía de Balances Reclamables](../../../build/guides/transactions/claimable-balances.mdx)
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/CreateClaimableBalanceOperation.java)\
-**Umbral**: Medio\
-**Resultado**: `CreateClaimableBalanceResult`\
-**Parámetros**:
-
-| Parámetros  | Tipo                 | Descripción                                                                                                        |
-| ----------- | -------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| Activo      | activo               | Activo que se mantendrá en la ClaimableBalanceEntry en la forma `asset_code:issuing_address` o `native` (XLM).     |
-| Cantidad    | entero               | Cantidad de `activo` almacenada en la ClaimableBalanceEntry.                                                       |
-| Reclamantes | lista de reclamantes | Lista de reclamantes (dirección de la cuenta y par ClaimPredicate) que pueden reclamar esta ClaimableBalanceEntry. |
-
-**Posibles errores**:
-
-| Error                                         | Código | Descripción                                                                                                                                                                                                                                                                  |
-| --------------------------------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `CREAR_SALDO_RECLAMABLE_MAL_FORMADO`          | \-1    | La entrada a esta operación no es válida.                                                                                                                                                                                                                                    |
-| `CREAR_SALDO_RECLAMABLE_BAJO_RESERVA`         | \-2    | La cuenta que crea esta entrada no tiene suficientes XLM para satisfacer el mínimo aumento de reserva de XLM causado por agregar una ClaimableBalanceEntry. Por cada reclamante en la lista, la cantidad mínima de XLM que esta cuenta debe tener aumentará por baseReserve. |
-| `CREAR_SALDO_RECLAMABLE_NO_CONFIABLE`         | \-3    | La cuenta de origen no confía en el emisor del activo que está tratando de incluir en la ClaimableBalanceEntry.                                                                                                                                                              |
-| `CREAR_SALDO_RECLAMABLE_NO_AUTORIZADO`        | \-4    | La cuenta de origen no está autorizada para transferir este activo.                                                                                                                                                                                                          |
-| `CREAR_SALDO_RECLAMABLE_FONDOS_INSUFICIENTES` | \-5    | La cuenta de origen no tiene suficientes fondos para transferir la cantidad de este activo a la ClaimableBalanceEntry.                                                                                                                                                       |
-
-## Reclamar saldo reclamable
-
-Reclama una ClaimableBalanceEntry que corresponde al BalanceID y agrega la cantidad de un activo de la entrada a la cuenta de origen
-
-Obtén más información sobre balances reclamables y consulta más parámetros: [Guía de Balances Reclamables](../../../build/guides/transactions/claimable-balances.mdx)
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/ClaimClaimableBalanceOperation.java)\
-**Umbral**: Bajo\
-**Resultado**: `ClaimClaimableBalanceResult`\
-**Parámetros**:
-
-| Parámetros | Tipo               | Descripción                                                                                                                                                                                                                                                                                                       |
-| ---------- | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| BalanceID  | claimableBalanceID | BalanceID en la ClaimableBalanceEntry que la cuenta de origen está reclamando. El balanceID se puede recuperar de un `CreateClaimableBalanceResult` exitoso. Consulta la [Guía de Balances Reclamables](../../../build/guides/transactions/claimable-balances.mdx#create-claimable-balance) para más información. |
-
-**Posibles errores**:
-
-| Error                                            | Código | Descripción                                                                                                                                                        |
-| ------------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `RECLAMAR_SALDO_RECLAMABLE_NO_EXISTE`            | \-1    | No hay una ClaimableBalanceEntry existente que coincida con el BalanceID de entrada.                                                                               |
-| `RECLAMAR_SALDO_RECLAMABLE_NO_SE_PUEDE_RECLAMAR` | \-2    | No hay un reclamante que coincida con la cuenta de origen, o el predicado de los reclamantes no está satisfecho.                                                   |
-| `RECLAMAR_SALDO_RECLAMABLE_LÍNEA_LLENA`          | \-3    | La cuenta que reclama la ClaimableBalanceEntry no tiene límites suficientes para recibir la cantidad del activo y seguir satisfaciendo sus obligaciones de compra. |
-| `RECLAMAR_SALDO_RECLAMABLE_NO_CONFIABLE`         | \-4    | La cuenta de origen no confía en el emisor del activo que está tratando de reclamar en la ClaimableBalanceEntry.                                                   |
-| `RECLAMAR_SALDO_RECLAMABLE_NO_AUTORIZADO`        | \-5    | La cuenta de origen no está autorizada para reclamar el activo en la ClaimableBalanceEntry.                                                                        |
-
-## Comenzar a patrocinar reservas futuras
-
-Permite a una cuenta pagar las reservas básicas para otra cuenta; la cuenta patrocinadora establece la relación de que está patrocinando reservas futuras
-
-También debe haber una operación de fin de patrocinio de reservas futuras en la misma transacción
-
-Obtén más información sobre reservas patrocinadas: [Guía de Reservas Patrocinadas](../../../build/guides/transactions/sponsored-reserves.mdx)
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/BeginSponsoringFutureReservesOperation.java)\
-**Umbral**: Medio\
-**Resultado**: `BeginSponsoringFutureReservesResult`\
-**Parámetros**:
-
-| Parámetros  | Tipo       | Descripción                                    |
-| ----------- | ---------- | ---------------------------------------------- |
-| SponsoredID | account ID | Cuenta que tendrá sus reservas patrocinadas.   |
-
-**Posibles errores**:
-
-| Error                            | Código | Descripción                                                                                             |
-| -------------------------------- | ------ | ------------------------------------------------------------------------------------------------------- |
-| `COMENZAR_A_ESPATOS_MAL_FORMADO` | \-1    | La cuenta de origen es igual a sponsoredID.                                                             |
-| `COMENZAR_A_ESPATOS_YA_ESPATOS`  | \-2    | La cuenta de origen ya está patrocinando sponsoredID.                                                   |
-| `COMENZAR_A_ESPATOS_RECURSIVO`   | \-3    | O la cuenta de origen está siendo patrocinada actualmente, o sponsoredID está patrocinando otra cuenta. |
-
-## Finalizar patrocinio de reservas futuras
-
-Termina la relación actual de patrocinio de reservas futuras en la que la cuenta de origen está patrocinada
-
-Obtén más información sobre reservas patrocinadas: [Guía de Reservas Patrocinadas](../../../build/guides/transactions/sponsored-reserves.mdx)
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/EndSponsoringFutureReservesOperation.java)\
-**Umbral**: Medio\
-**Resultado**: `EndSponsoringFutureReservesResult`\
-**Parámetros**:
-
-| Parámetros    | Tipo       | Descripción                                  |
-| ------------- | ---------- | -------------------------------------------- |
-| begin_sponsor | account ID | El ID de la cuenta que inició el patrocinio. |
-
-**Posibles errores**:
-
-| Error                          | Código | Descripción                              |
-| ------------------------------ | ------ | ---------------------------------------- |
-| `FINALIZAR_ESPATOS_NO_ESPATOS` | \-1    | La cuenta de origen no está patrocinada. |
-
-## Revocar patrocinio
-
-La cuenta patrocinadora puede eliminar o transferir patrocinios de ledgerEntries y signatarios existentes; la lógica de esta operación depende del estado de la cuenta de origen
-
-Obtén más información sobre reservas patrocinadas: [Guía de Reservas Patrocinadas](../../../build/guides/transactions/sponsored-reserves.mdx)
-
-**Umbral**: Medio\
-**Resultado**: `RevokeSponsorshipResult`
-
-Esta operación es una unión con **dos** tipos posibles:
-
-| Tipo de unión                         | Parámetros | Tipo      | Descripción                                                                                                                                                                                                  |
-| ------------------------------------- | ---------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `REVOCAR_ESAMIENTOS_ENTRADA_DE_LIBRO` | LedgerKey  | ledgerKey | Clave de ledger que contiene información para identificar una entrada de ledger específica cuya patrocinación puede ser modificada. Consulta [LedgerKey](../../glossary.mdx#ledgerkey) para más información. |
-
-O
-
-| Tipo de unión                 | Parámetros | Tipo                      | Descripción                                        |
-| ----------------------------- | ---------- | ------------------------- | -------------------------------------------------- |
-| `REVOCAR_ESAMIENTOS_FIRMANTE` | Firmante   | \{account ID, Signer Key} | Firmante que puede tener su patrocinio modificado. |
-
-**Posibles errores**:
-
-| Error                                  | Código | Descripción                                                                                                                                                                                                                                                                                                                                  |
-| -------------------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `REVOCAR_ESAMIENTOS_NO_EXISTE`         | \-1    | La ledgerEntry para LedgerKey no existe, el ID de la cuenta en el firmante no existe, o la Signer Key no existe en la cuenta del ID de cuenta.                                                                                                                                                                                               |
-| `REVOCAR_ESAMIENTOS_NO_ESPATOS`        | \-2    | Si la ledgerEntry/firmante está siendo patrocinado, entonces la cuenta de origen debe ser el patrocinador. Si la ledgerEntry/firmante no está patrocinado, la cuenta de origen debe ser el propietario. Este error se lanzará de lo contrario.                                                                                               |
-| `REVOCAR_ESAMIENTOS_BAJO_RESERVA`      | \-3    | La cuenta patrocinada no tiene suficientes XLM para satisfacer el aumento mínimo de saldo causado por revocar el patrocinio de una ledgerEntry/firmante que posee, o el patrocinador de la cuenta de origen no tiene suficientes XLM para satisfacer el aumento mínimo de saldo causado por patrocinar una ledgerEntry/firmante transferido. |
-| `REVOCAR_ESAMIENTOS_SOLO_TRANSFERIBLE` | \-4    | No se puede eliminar el patrocinio de esta ledgerEntry. Este error ocurrirá si el usuario intenta quitar el patrocinio de una ClaimableBalanceEntry.                                                                                                                                                                                         |
-| `REVOCAR_ESAMIENTOS_MAL_FORMADO`       | \-5    | Uno o más de los insumos para la operación estaban mal formados.                                                                                                                                                                                                                                                                             |
-
-## Recuperación
-
-Quema una cantidad en un activo específico de una cuenta. Solo la cuenta emisora del activo puede realizar esta operación.
-
-Obtén más información sobre devoluciones: [Guía de Devoluciones](../../../build/guides/transactions/clawbacks.mdx)
-
-**SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.clawback) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/ClawbackOperation.java) | [Go](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild#Clawback)\
-**Umbral**: Medio\
-**Resultado**: `ClawbackResult`\
-**Parámetros**:
-
-| Parámetros | Tipo       | Descripción                                                       |
-| ---------- | ---------- | ----------------------------------------------------------------- |
-| Desde      | account ID | Dirección de cuenta de la cual el activo necesita ser recuperado. |
-| Activo     | activo     | Activo en posesión de la cuenta de destino.                       |
-| Cantidad   | entero     | Cantidad del activo mencionado para destruir.                     |
-
-**Posibles errores**:
-
-| Error                             | Código | Descripción                                                                                                        |
-| --------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------ |
-| `RETROCEDER_MAL_FORMADO`          | \-1    | La entrada a la recuperación no es válida.                                                                         |
-| `RETROCEDER_NO_HA_SIDO_ACTIVADO`  | \-2    | La línea de confianza entre Desde y la cuenta emisora para este activo no tiene recuperación habilitada.           |
-| `RETROCEDER_NO_CONFIABLE`         | \-3    | La cuenta Desde no confía en el emisor del activo.                                                                 |
-| `RETROCEDER_FONDOS_INSUFICIENTES` | \-4    | La cuenta Desde no tiene un saldo disponible suficiente del activo (teniendo en cuenta las obligaciones de venta). |
-
-## Recuperación de saldo reclamable
-
-Recupera un ClaimableBalanceEntry no reclamado, quemando la cantidad pendiente del activo. Solo la cuenta emisora del activo puede realizar esta operación.
-
-Obtén más información sobre devoluciones: [Guía de Devoluciones](../../../build/guides/transactions/clawbacks.mdx)
-
-Obtén más información sobre balances reclamables: [Guía de Balances Reclamables](../../../build/guides/transactions/claimable-balances.mdx)
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/ClawbackClaimableBalanceOperation.java)\
-**Umbral**: Medio\
-**Resultado**: `ClaimClaimableBalanceResult`\
-**Parámetros**:
-
-| Parámetros | Tipo               | Descripción                                                                                                                                            |
-| ---------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| BalanceID  | claimableBalanceID | El BalanceID en la ClaimableBalanceEntry que la cuenta de origen está reclamando, que se puede recuperar de un `CreateClaimableBalanceResult` exitoso. |
-
-**Posibles errores**:
-
-| Error                                             | Código | Descripción                                                                                    |
-| ------------------------------------------------- | ------ | ---------------------------------------------------------------------------------------------- |
-| `RETROCEDER_SALDO_RECLAMABLE_NO_EXISTE`           | \-1    | No hay una ClaimableBalanceEntry existente que coincida con el BalanceID de entrada.           |
-| `RETROCEDER_SALDO_RECLAMABLE_NO_ES_EMISOR`        | \-2    | La cuenta de origen no es el emisor del activo en el saldo reclamable.                         |
-| `RETROCEDER_SALDO_RECLAMABLE_NO_HA_SIDO_ACTIVADO` | \-3    | `El CLAIMABLE_BALANCE_CLAWBACK_ENABLED_FLAG` no está configurado para esta línea de confianza. |
-
-## Configurar las banderas de la línea de confianza
-
-Permite a la cuenta emisora configurar la autorización y las banderas de la línea de confianza para un activo
-
-El parámetro Activo es del tipo `TrustLineAsset`. Si estás modificando una línea de confianza a un activo regular (es decir, uno en formato Code:Issuer), esto es equivalente al tipo de Activo. Si estás modificando una línea de confianza a una participación de pool, sin embargo, esto se compone del ID único del pool de liquidez.
-
-Aprende más sobre banderas: [Entrada del Glosario sobre Banderas](../../glossary.mdx#flags)
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/SetTrustlineFlagsOperation.java)\
-**Umbral**: Bajo\
-**Resultado**: `SetTrustLineFlagsResult`\
-**Parámetros**:
-
-| Parámetros      | Tipo           | Descripción                                                                                                                                                                                                                                                                          |
-| --------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Fiduciario      | ID de cuenta   | La cuenta que estableció esta línea fiduciaria.                                                                                                                                                                                                                                      |
-| Activo          | TrustLineAsset | La línea fiduciaria del activo cuyos flags están siendo modificados.                                                                                                                                                                                                                 |
-| EstablecerFlags | entero         | Uno o más flags (combinados a través de OR a nivel de bits) indicando qué flags establecer. Los posibles flags son: 1 si el fiduciario está autorizado a transaccionar con el activo o 2 si el fiduciario está autorizado a mantener ofertas pero no a realizar otras transacciones. |
-| BorrarFlags     | entero         | Uno o más flags (combinados a través de OR a nivel de bits) indicando qué flags borrar. Las posibilidades incluyen las de EstablecerFlags así como 4, que impide que el emisor recupere su activo (tanto de cuentas como de saldos reclamables).                                     |
-
-**Posibles errores**:
-
-| Error                                                              | Código | Descripción                                                                                                                                                                                                                                                                                                           |
-| ------------------------------------------------------------------ | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `ESTABLECER_FLAGS_DE_LINEA_DE_CONFIANZA_MAL_FORMADO`               | \-1    | Esto puede suceder por varias razones: el activo especificado por AssetCode y AssetIssuer es inválido; el emisor del activo no es la cuenta fuente; el Fiduciario es la cuenta fuente; el activo nativo está especificado; o los flags que se están estableciendo/borrando son conflictivos o de otro modo inválidos. |
-| `ESTABLECER_FLAGS_DE_LINEA_DE_CONFIANZA_NO_HAY_LINEA_DE_CONFIANZA` | \-2    | El Fiduciario no tiene una línea fiduciaria con el emisor que está realizando esta operación.                                                                                                                                                                                                                         |
-| `ESTABLECER_FLAGS_DE_LINEA_DE_CONFIANZA_NO_SE_PUEDE_REVOKAR`       | \-3    | El emisor está intentando revocar la autorización de la línea fiduciaria de Fiduciario, pero no puede hacerlo porque AUTH_REVOCABLE_FLAG no está establecido en la cuenta.                                                                                                                                            |
-| `ESTABLECER_FLAGS_DE_LINEA_DE_CONFIANZA_ESTADO_INVÁLIDO`           | \-4    | Si el estado final de la línea fiduciaria tiene tanto AUTHORIZED_FLAG (1) como AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG (2) establecidos, lo cual es mutuamente exclusivo.                                                                                                                                             |
-| `ESTABLECER_FLAGS_DE_LINEA_DE_CONFIANZA_BAJO_RESERVA`              | \-5    | No se pueden crear saldos reclamables al revocar líneas fiduciarias de activos (o de participación en el pool) asociadas con un fondo de liquidez debido a reservas bajas.                                                                                                                                            |
-
-## Depósito en el fondo de liquidez
-
-Deposita activos en un fondo de liquidez, aumentando las reservas de un fondo de liquidez a cambio de participaciones del pool
-
-Los parámetros de esta operación dependen del orden de los activos en el fondo de liquidez: “A” se refiere al primer activo en el fondo de liquidez, y “B” se refiere al segundo activo en el fondo de liquidez.
-
-Si el pool está vacío, entonces esta operación deposita maxAmountA de A y maxAmountB de B en el pool. Si el pool no está vacío, entonces esta operación deposita como máximo maxAmountA de A y maxAmountB de B en el pool. Los montos reales depositados se determinan utilizando las reservas actuales del pool. Puedes usar estos parámetros para controlar un porcentaje de deslizamiento.
-
-Obtén más información sobre fondos de liquidez: [Sección de Fondos de Liquidez](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/LiquidityPoolDepositOperation.java)\
-**Umbral**: Mediano\
-**Resultado**: `LiquidityPoolDepositResult`\
-**Parámetros**:
-
-| Parámetros               | Tipo                      | Descripción                                              |
-| ------------------------ | ------------------------- | -------------------------------------------------------- |
-| ID del Fondo de Liquidez | liquidityPoolID           | El PoolID para el Fondo de Liquidez en el que depositar. |
-| Máximo Monto A           | entero                    | Monto máximo del primer activo a depositar.              |
-| Máximo Monto B           | entero                    | Monto máximo del segundo activo a depositar.             |
-| Precio Mínimo            | \{numerador, denominador} | Depósito mínimo A/deposito B.                            |
-| Precio Máximo            | \{numerador, denominador}  | Depósito máximo A/deposito B.                            |
-
-**Posibles errores**:
-
-| Error                                               | Código | Descripción                                                                      |
-| --------------------------------------------------- | ------ | -------------------------------------------------------------------------------- |
-| `DEPÓSITO_DE_POOL_DE_LIQUIDEZ_MAL_FORMADO`          | \-1    | Uno o más de los insumos de la operación estaban mal formados.                   |
-| `DEPÓSITO_DE_POOL_DE_LIQUIDEZ_NO_CONFIABLE`         | \-2    | No existe una línea fiduciaria para uno de los activos que se están depositando. |
-| `DEPÓSITO_DE_POOL_DE_LIQUIDEZ_NO_AUTORIZADO`        | \-3    | La cuenta no tiene autorización para uno de los activos.                         |
-| `DEPÓSITO_DE_POOL_DE_LIQUIDEZ_FONDOS_INSUFICIENTES` | \-4    | No hay suficiente saldo de uno de los activos para realizar el depósito.         |
-| `DEPÓSITO_DE_POOL_DE_LIQUIDEZ_LÍNEA_LLENA`          | \-5    | La línea fiduciaria de participación del pool no tiene un límite suficiente.     |
-| `DEPÓSITO_DE_POOL_DE_LIQUIDEZ_PRECIO_ERRÓNEO`       | \-6    | El precio de depósito está fuera de los límites dados.                           |
-| `DEPÓSITO_DE_POOL_DE_LIQUIDEZ_POOL_LLENO`           | \-7    | Las reservas del fondo de liquidez están completas.                              |
-
-## Retiro de fondo de liquidez
-
-Retira activos de un fondo de liquidez, reduciendo el número de participaciones del pool a cambio de reservas de un fondo de liquidez
-
-Los parámetros de minAmountA y minAmountB se pueden usar para controlar un porcentaje de deslizamiento desde el "precio de mercado" en el pool.
-
-Obtén más información sobre fondos de liquidez: [Sección de Fondos de Liquidez](../liquidity-on-stellar-sdex-liquidity-pools.mdx)
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/LiquidityPoolWithdrawOperation.java)\
-**Umbral**: Mediano\
-**Resultado**: `LiquidityPoolWithdrawResult`\
-**Parámetros**:
-
-| Parámetros               | Tipo            | Descripción                                          |
-| ------------------------ | --------------- | ---------------------------------------------------- |
-| ID del Fondo de Liquidez | liquidityPoolID | El PoolID para el Fondo de Liquidez del que retirar. |
-| Monto                    | entero          | Monto de participaciones del pool a retirar.         |
-| Monto Mínimo A           | entero          | Cantidad mínima del primer activo a retirar.         |
-| Monto Mínimo B           | entero          | Cantidad mínima del segundo activo a retirar.        |
-
-**Posibles errores**:
-
-| Error                                              | Código | Descripción                                                                   |
-| -------------------------------------------------- | ------ | ----------------------------------------------------------------------------- |
-| `RETIRAR_DE_POOL_DE_LIQUIDEZ_MAL_FORMADO`          | \-1    | Uno o más de los insumos de la operación estaban mal formados.                |
-| `RETIRAR_DE_POOL_DE_LIQUIDEZ_NO_CONFIABLE`         | \-2    | No hay línea fiduciaria para uno de los activos.                              |
-| `RETIRAR_DE_POOL_DE_LIQUIDEZ_FONDOS_INSUFICIENTES` | \-3    | Saldo insuficiente para las participaciones del pool.                         |
-| `RETIRAR_DE_POOL_DE_LIQUIDEZ_LÍNEA_LLENA`          | \-4    | El retiro excedería el límite de la línea fiduciaria para uno de los activos. |
-| `RETIRAR_DE_POOL_DE_LIQUIDEZ_INFERIOR_A_MÍNIMO`    | \-5    | No se puede retirar lo suficiente para satisfacer el precio mínimo.           |
-
-## Invocar función del host
-
-Invoca e implementa contratos inteligentes de Soroban con `InvokeHostFunctionOp`.
-
-`InvokeHostFunctionOp` se puede usar para realizar las siguientes operaciones de Soroban:
-
-- Invocar funciones del contrato: `HOST_FUNCTION_TYPE_INVOKE_CONTRACT`
-- Subir Wasm de los contratos: `HOST_FUNCTION_TYPE_UPLOAD_CONTRACT_WASM`
-- Desplegar nuevos contratos usando el Wasm subido o implementaciones integradas: `HOST_FUNCTION_TYPE_CREATE_CONTRACT`
-
-Ten en cuenta que las transacciones de Soroban solo pueden contener una operación por transacción.
-
-Aprende más [aquí](../../fundamentals/contract-development/contract-interactions/stellar-transaction.mdx#invokehostfunctionop).
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/InvokeHostFunctionOperation.java)\
-**Umbral**: Mediano\
-**Resultado**: `InvokeHostFunctionResult`\
-**Parámetros**:
-
-| Parámetros       | Tipo                               | Descripción                                              |
-| ---------------- | ---------------------------------- | -------------------------------------------------------- |
-| Función del Host | FunciónDelHost                     | La función del host a invocar                            |
-| Autenticación    | Entrada de Autorización de Soroban | Autorizaciones por dirección para esta función del host. |
-
-**Errores posibles**:
-
-| Error                                                   | Código | Descripción                                                                                                                                              |
-| ------------------------------------------------------- | ------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `INVOCAR_FUNCION_HOSPEDADA_MAL_FORMADO`                 | \-1    | Uno o más de los inputs de la operación estaban malformados.                                                                                             |
-| `INVOCAR_FUNCION_HOSPEDADA_ATASCADA`                    | \-2    | La invocación de la función se atrapó en la ejecución de Soroban.                                                                                        |
-| `INVOCAR_FUNCION_HOSPEDADA_LIMITE_DE_RECURSOS_EXCEDIDO` | \-3    | La invocación de la función no pudo completarse dentro de las restricciones de recursos actualmente configuradas de la red.                              |
-| `INVOCAR_FUNCION_HOSPEDADA_ENTRADA_ARCHIVADA`           | \-4    | Una entrada de ledger requerida para la huella de esta función está en estado archivado y debe ser restaurada.                                           |
-| `INVOCAR_FUNCION_HOSPEDADA_FEE_DEVOLUTIVO_INSUFICIENTE` | \-5    | La tarifa reembolsable de Soroban proporcionada no fue suficiente para pagar por los recursos computacionales requeridos por esta invocación de función. |
-
-## Extender TTL de Huella
-
-Extender el tiempo de vida (TTL) de las entradas para contratos inteligentes de Soroban con la `ExtendFootprintTTLOp`. Esta operación extiende el TTL de las entradas especificadas en la huella `readOnly` de la transacción para que vivan al menos hasta que se alcance el número de secuencia del ledger `extendTo`.
-
-Ten en cuenta que las transacciones de Soroban solo pueden contener una operación por transacción.
-
-Aprende más en la [sección de Archivado de Estado](../../fundamentals/contract-development/storage/state-archival.mdx).
-
-**SDKs**: [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/ExtendFootprintTTLOperation.java)\
-**Umbral**: Medio\
-**Resultado**: `ExtendFootprintTTLResult`\
-**Parámetros**:
-
-| Parámetros     | Tipo               | Descripción                                                          |
-| -------------- | ------------------ | -------------------------------------------------------------------- |
-| Ext            | Punto de Extensión | Reservado para uso futuro.                                           |
-| Extender Hasta | entero             | El número de secuencia del ledger hasta el que las entradas vivirán. |
-
-**Errores posibles**:
-
-| Error                                                | Código | Descripción                                                                                                                                 |
-| ---------------------------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| `EXTENDER_TTL_DE_HUELLA_MAL_FORMADO`                 | \-1    | Uno o más de los inputs de la operación estaban malformados.                                                                                |
-| `EXTENDER_TTL_DE_HUELLA_LIMITE_DE_RECURSOS_EXCEDIDO` | \-2    | La extensión TTL no pudo completarse dentro de las restricciones de recursos actualmente configuradas de la red.                            |
-| `EXTENDER_TTL_DE_HUELLA_FEE_DEVOLUTIVO_INSUFICIENTE` | \-3    | La tarifa reembolsable de Soroban proporcionada no fue suficiente para pagar por la extensión TTL de las entradas del ledger especificadas. |
-
-## Restaurar Huella
-
-Hacer que las entradas archivadas de contratos inteligentes de Soroban sean accesibles nuevamente restaurándolas con `RestoreFootprintOp`. Esta operación restaura las entradas archivadas especificadas en la huella `readWrite`.
-
-Ten en cuenta que las transacciones de Soroban solo pueden contener una operación por transacción.
-
-Aprende más en la [sección de Archivado de Estado](../../fundamentals/contract-development/storage/state-archival.mdx).
-
-**SDKs**: [JavaScript](https://stellar.github.io/js-stellar-sdk/Operation.html#.restoreFootprint) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/RestoreFootprintOperation.java)\
-**Umbral**: Medio\
-**Resultado**: `RestoreFootprintResult`\
-**Parámetros**:
-
-| Parámetros | Tipo               | Descripción                |
-| ---------- | ------------------ | -------------------------- |
-| Ext        | Punto de Extensión | Reservado para uso futuro. |
-
-**Errores posibles**:
-
-| Error                                            | Código | Descripción                                                                                                                                            |
-| ------------------------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `RESTABLECER_HUELLA_MAL_FORMADO`                 | \-1    | Uno o más de los inputs de la operación estaban malformados.                                                                                           |
-| `RESTABLECER_HUELLA_LIMITE_DE_RECURSOS_EXCEDIDO` | \-2    | La restauración del archivo no pudo completarse dentro de las restricciones de recursos actualmente configuradas de la red.                            |
-| `RESTABLECER_HUELLA_FEE_DEVOLUTIVO_INSUFICIENTE` | \-3    | La tarifa reembolsable de Soroban proporcionada no fue suficiente para pagar por la restauración del archivo de las entradas del ledger especificadas. |
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/operations-and-transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/operations-and-transactions.mdx
deleted file mode 100644
index 9e58b914a4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/operations-and-transactions.mdx
+++ /dev/null
@@ -1,184 +0,0 @@
----
-title: "Operaciones y Transacciones: Cómo se Ejecutan las Acciones de Blockchain"
-sidebar_label: Operaciones y transacciones
-description: Aprende cómo funcionan las operaciones y las transacciones en la red Stellar. Comprende cómo se agrupan varias operaciones en transacciones para ejecutar acciones de blockchain.
-sidebar_position: 10
----
-
-# Operaciones y Transacciones
-
-:::note
-
-Encuentra guías prácticas sobre transacciones con o sin contratos inteligentes en la [sección Guías Prácticas de Transacciones](../../../build/guides/transactions/README.mdx).
-
-:::
-
-## Operaciones y transacciones: cómo funcionan
-
-Para realizar acciones con una cuenta en la red Stellar, compones operaciones, las agrupar en una transacción y luego firmas y envías la transacción a la red. Las transacciones de contratos inteligentes (aquellas con operaciones `InvokeHostFunctionOp`, `ExtendFootprintTTLOp` o `RestoreFootprintOp`) pueden tener solo una operación por transacción.
-
-### Operaciones
-
-Las operaciones son comandos individuales que modifican el ledger. Las operaciones se usan para enviar pagos, invocar una función de contrato inteligente, ingresar órdenes en el exchange descentralizado, cambiar configuraciones en cuentas y autorizar cuentas para mantener activos.
-
-Todas las operaciones caen en una de tres categorías de umbral: bajo, medio o alto, y cada categoría de umbral tiene un peso entre 0 y 255 (que se puede determinar usando set_options). Los umbrales determinan qué peso de firma se requiere para que la operación sea aceptada. Por ejemplo, digamos que una cuenta establece el peso de umbral medio en 5. Si la cuenta quiere establecer con éxito una línea de confianza con la operación `changeTrust`, el peso de la firma debe ser mayor o igual a 5.
-
-Para obtener más información sobre el peso de la firma, consulta la [entrada del enciclopedia sobre firma y multisisgnature](../../fundamentals/transactions/signatures-multisig.mdx).
-
-Consulta una lista completa de las operaciones de Stellar y sus niveles de umbral en la [sección de Lista de Operaciones](./list-of-operations.mdx).
-
-### Transacciones
-
-La red Stellar codifica transacciones usando un protocolo estandarizado llamado Representación de Datos Externos (XDR). Puedes leer más sobre esto en nuestra [Sección XDR](../data-format/xdr.mdx).
-
-Las cuentas solo pueden realizar una transacción a la vez.
-
-Las transacciones comprenden un paquete de entre 1 y 100 operaciones (excepto las transacciones de contratos inteligentes, que solo pueden tener una operación por transacción) y son firmadas y enviadas al ledger por las cuentas. Las transacciones siempre necesitan ser autorizadas por la clave pública de la cuenta de origen para ser válidas, lo que implica firmar el objeto de la transacción con la clave secreta asociada a la clave pública. Una transacción más su(s) firma(s) se llama sobre de transacción.
-
-Una transacción puede necesitar más de una firma: esto ocurre si tiene operaciones que afectan a más de una cuenta o si tiene un peso de umbral alto. Consulta la [Sección de Firma y Multifirma](../../fundamentals/transactions/signatures-multisig.mdx) para obtener más información.
-
-Las transacciones son atómicas. Esto significa que si una operación en una transacción falla, todas las operaciones fallan y la transacción completa no se aplica al ledger.
-
-Las operaciones se ejecutan para la cuenta de origen de la transacción a menos que se defina una anulación de operación.
-
-Las transacciones de contratos inteligentes también pasan por un proceso de simulación donde los desarrolladores pueden probar cómo se ejecutaría la transacción en la red usando el punto final RPC `simulateTransaction`. Lee más en la [documentación de Soroban](../../fundamentals/contract-development/contract-interactions/transaction-simulation.mdx).
-
-## Memo
-
-Los memos son un campo opcional de datos no estructurados que se puede usar para incluir cualquier información adicional que identifique la transacción y sea relevante para el emisor o receptor.
-
-Anteriormente se usaban para diferenciar entre cuentas individuales en una cuenta agrupada; ahora usamos cuentas muxed para eso.
-
-Para más información sobre cuentas muxed, consulta nuestra [Guía de Cuentas Agrupadas - Cuentas Muxed y Memos](../../../build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx)
-
-Los memos pueden ser uno de los siguientes tipos:
-
-`MEMO_TEXT`: Una cadena codificada usando ASCII o UTF-8, de hasta 28 bytes de longitud.\
-`MEMO_ID`: Un entero sin signo de 64 bits.\
-`MEMO_HASH`: Un hash de 32 bytes.\
-`MEMO_RETURN`: Un hash de 32 bytes destinado a interpretarse como el hash de la transacción que el emisor está reembolsando.
-
-## Ejemplos de contenido de memo
-
-- Notificación de que la transacción es un reembolso o indemnización
-- Referencia a una factura que la transacción está pagando
-- Cualquier información adicional de enrutamiento interno
-- Enlaces a datos relevantes
-
-#### Atributos de la transacción
-
-- [Tarifa](../fees-resource-limits-metering.mdx)
-- [Lista de operaciones](./list-of-operations.mdx)
-- [Lista de firmas](../../fundamentals/transactions/signatures-multisig.mdx)
-- [Memo o cuenta muxed](../../../build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx)
-- [Número de secuencia](../../glossary.mdx#sequence-number)
-- [Cuenta de origen](../../glossary.mdx#source-account)
-- [Precondiciones (opcional)](#preconditions)
-
-## Validez de la transacción y operación
-
-Antes de ser enviadas con éxito a la red Stellar, las transacciones pasan por varias verificaciones de validez. Estas verificaciones se agrupan en tres categorías:
-
-### Precondiciones (opcional) {#preconditions}
-
-Las precondiciones se verifican primero.
-
-Todas las precondiciones son opcionales. Se recomienda establecer límites de tiempo, pero las otras precondiciones se utilizan en circunstancias más especializadas. Puedes establecer múltiples precondiciones siempre que la combinación tenga sentido lógicamente.
-
-#### Límites de tiempo
-
-Válido si está dentro de los límites de tiempo establecidos de la transacción
-
-Los límites de tiempo son una marca de tiempo UNIX opcional (en segundos), determinada por el tiempo del ledger, de un límite inferior y superior de cuándo será válida una transacción. Si una transacción se presenta demasiado temprano o demasiado tarde, no podrá entrar en el conjunto de transacciones.
-
-Establecer límites de tiempo en las transacciones se recomienda encarecidamente, y muchos SDK los imponen.
-
-Si `maxTime` es 0, no se establecen límites de tiempo superiores. En este caso, si una transacción no llega al conjunto de transacciones, se mantiene en memoria y trata de llegar continuamente al siguiente conjunto de transacciones. Debido a esto, recomendamos que todas las transacciones se creen con límites de tiempo para invalidar transacciones después de un cierto período, especialmente si planeas reenviar tu transacción más tarde.
-
-#### Límites del ledger
-
-Válido si está dentro de los límites del ledger establecidos de la transacción
-
-Los límites del ledger se aplican a los números del ledger. Con estos definidos, una transacción solo será válida para los números del ledger que caigan dentro del rango determinado.
-
-El límite inferior es inclusivo (menor o igual a) mientras que el límite superior no lo es (solo mayor que).
-
-Si el límite superior se establece en 0, esto indica que no hay límite superior.
-
-#### Número de secuencia mínimo
-
-Si se establece un número de secuencia mínimo, la transacción solo será válida cuando el número de secuencia de su cuenta de origen (llámalo S) sea lo suficientemente grande. Específicamente, es válida cuando S satisface `minSeqNum <= S < tx.seqNum`.
-
-Si se omite esta precondición, se aplicará el comportamiento predeterminado: el número de secuencia de la transacción debe ser exactamente uno mayor que el número de secuencia de la cuenta.
-
-Ten en cuenta que después de que se ejecute una transacción, la cuenta siempre establecerá su número de secuencia en el número de secuencia de la transacción.
-
-#### Edad mínima de secuencia
-
-La transacción es válida después de que transcurra una duración particular (expresada en segundos) desde que se tocó la edad del número de secuencia de la cuenta.
-
-La edad de secuencia mínima es una precondición relacionada con el tiempo, pero a diferencia de los límites de tiempo, que expresan tiempos absolutos, la edad de secuencia mínima es relativa a cuándo se tocó el número de secuencia de la cuenta de origen de la transacción.
-
-#### Gap mínimo de secuencia
-
-Válido si se presenta en un ledger que cumpla o exceda la edad del número de secuencia de la cuenta de origen
-
-Esto es similar a la edad mínima de secuencia, excepto que se expresa como un número de ledgers en lugar de una duración de tiempo.
-
-#### Firmantes adicionales
-
-Válido si se presenta con firmas que cumplan con cada uno de los firmantes adicionales
-
-Una transacción puede especificar hasta dos firmantes adicionales como precondición, lo que significa que debe tener firmas que correspondan a esos firmantes adicionales, incluso si esas firmas no serían requeridas de otra manera para autorizar la transacción (es decir, para su cuenta de origen u operaciones).
-
-Los firmantes adicionales pueden ser de cualquier tipo además del firmante preautorizado de la transacción, ya que para preautorizar una transacción, necesitas conocer su hash, pero el hash debe incluir a los firmantes adicionales. Esta relación Catch-22 significa que incluir este tipo de firmante adicional devolverá un error.
-
-### Validez de la operación
-
-Cuando se presenta una transacción a un nodo, el nodo verifica la validez de cada operación en la transacción antes de intentar incluirla en un conjunto de transacciones candidatas. Estas verificaciones iniciales de validez de operaciones están destinadas a ser rápidas y simples, con verificaciones más intensivas después de que se hayan consumido las tarifas. Para que una operación pase esta verificación de validez, debe cumplir con las siguientes condiciones:
-
-#### Las firmas en la transacción deben ser válidas para la operación
-
-Las firmas son de firmantes válidos para la cuenta de origen de la operación. El peso combinado de todas las firmas para la cuenta de origen de la operación cumple con el umbral para la operación.
-
-#### La operación debe estar bien formada
-
-Normalmente esto significa verificar los parámetros de la operación para ver si están en un formato válido. Por ejemplo, solo se pueden establecer valores positivos para el monto de una operación de pago.
-
-#### La operación debe ser válida en la versión actual del protocolo de la red
-
-Las operaciones obsoletas, como la inflación, son inválidas por diseño.
-
-### Validez de la transacción
-
-Finalmente, se llevan a cabo las siguientes verificaciones de transacción:
-
-#### Cuenta de origen
-
-La cuenta de origen debe existir en el ledger.
-
-#### Tarifa
-
-La tarifa debe ser mayor o igual a la tarifa mínima de la red para el número de operaciones presentadas como parte de la transacción. Esto no garantiza que la transacción se aplique, solo que es válida. Además, la cuenta de origen debe poder pagar la tarifa especificada.
-
-#### Aumento de tarifa (si corresponde)
-
-Consulta la Validez de una [Guía de Transacción Fee-Bump](../../../build/guides/transactions/fee-bump-transactions.mdx) para obtener más información.
-
-#### Número de secuencia
-
-El número de secuencia debe ser uno mayor que el número de secuencia almacenado en la entrada de la cuenta de origen cuando se aplica la transacción, a menos que se establezcan precondiciones del número de secuencia. Una cuenta solo puede tener una transacción (y, por lo tanto, un número de secuencia) consumida por ledger.
-
-#### Lista de operaciones
-
-Cada operación debe pasar todas las verificaciones de validez para una operación, descritas en la sección de Validez de Operación anterior.
-
-#### Lista de firmas
-
-- Cumplir con los requisitos de firma para cada operación en la transacción
-- La frase secreta de la red apropiada es parte del hash de la transacción firmado por cada firmante
-- El peso combinado de las firmas para la cuenta de origen de la transacción cumple con el umbral bajo para la cuenta de origen.
-
-#### Memo (si corresponde)
-
-El tipo de memo debe ser un tipo válido, y el memo mismo debe adherirse al formato del tipo de memo.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/signatures-multisig.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/signatures-multisig.mdx
deleted file mode 100644
index 889b97aea6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/signatures-multisig.mdx
+++ /dev/null
@@ -1,155 +0,0 @@
----
-title: Firmas y Multisig
-sidebar_position: 20
----
-
-:::note
-
-Esta sección detalla la firma de transacciones que no son contratos inteligentes. Para la autenticación relacionada con transacciones de contratos inteligentes, consulta [autorización](../../fundamentals/contract-development/authorization.mdx).)
-
-:::
-
-Las firmas son la autorización para transacciones en la red. Las transacciones siempre necesitan autorización de al menos una clave pública para ser válidas y generalmente, la firma proviene de la cuenta de origen. A veces las transacciones requieren más firmas, lo que abordaremos en la sección de multisig.
-
-Las firmas de transacciones se crean firmando el contenido del objeto de la transacción con una clave secreta. Stellar utiliza el esquema de firma ed25519, pero también existe un mecanismo para añadir tipos adicionales de esquemas de clave pública y privada. Una transacción con una firma adjunta se considera que tiene autorización de esa clave pública.
-
-### Umbrales
-
-Cada operación cae bajo una categoría de umbral específica: bajo, medio o alto, con un nivel numérico entre 0-255 (para leer más sobre esto, consulta nuestra sección sobre [Operaciones y Transacciones](../../fundamentals/transactions/operations-and-transactions.mdx#operations)). Este umbral determina qué peso de firma es necesario para autorizar una operación.
-
-Para ver el umbral de cada operación, consulta nuestra [lista de operaciones](../../fundamentals/transactions/list-of-operations.mdx).
-
-Las cuentas pueden establecer su propio peso de firma, valores de umbral y claves adicionales de firma con la operación Set Options. Por defecto, todos los niveles de umbral de operación están establecidos en 0, y la clave maestra está establecida con peso 1. En la mayoría de los casos, se recomienda establecer los umbrales de manera que `bajo <= medio <= alto`.
-
-Si el peso de la clave maestra se establece en 0, no puede usarse para firmar transacciones, incluso para operaciones con un valor de umbral de 0. Ten mucho cuidado al establecer el peso de tu clave maestra en 0. Hacerlo puede bloquearte permanentemente el acceso a tu cuenta (aunque si hay otros firmantes listados en la cuenta, ellos todavía podrán continuar firmando transacciones).
-
-### Autorización
-
-Para determinar si una transacción tiene la autorización necesaria para ejecutarse, se suman los pesos de todas las firmas en el sobre de la transacción. Si esta suma es igual o mayor al umbral para ese tipo de operación, entonces la operación está autorizada.
-
-Este esquema es muy flexible. Puedes requerir que muchos firmantes autoricen los pagos desde una cuenta en particular. Puedes tener una cuenta que cualquier número de personas pueda autorizar. Puedes tener una clave maestra que conceda o revoque el acceso a otros. Admite cualquier configuración de m de n.
-
-## Multisig
-
-En algunos casos, una transacción puede necesitar más de una firma:
-
-- Si la transacción tiene operaciones con múltiples cuentas de origen, requiere la firma de cada cuenta de origen para cada operación
-- Se requieren firmas adicionales si la cuenta asociada a la transacción tiene múltiples claves públicas
-
-Cada firmante adicional más allá de la clave maestra incrementa el saldo mínimo de la cuenta en una reserva base. Hasta 20 firmas pueden ser adjuntadas a una transacción. Una vez que se cumple el umbral de firmas, si quedan firmas sobrantes, la transacción fallará. Por ejemplo, si tu transacción requiere tres firmas, proporcionar más de tres firmas, incluso si todas son válidas, resultará en un error de transacción fallida: `TX_BAD_AUTH_EXTRA`. Este diseño se debe a que la verificación innecesaria de firmas tiene un gran impacto en el rendimiento antes de aceptar transacciones en consenso.
-
-### Tipos alternativos de firma
-
-Para habilitar algunas funciones avanzadas de contratos inteligentes existen un par de tipos adicionales de firma. Estos tipos de firma también tienen pesos y pueden agregarse y eliminarse de manera similar a los tipos normales de firma. Pero en lugar de verificar una firma criptográfica para la autorización, tienen un método diferente para probar validez a la red.
-
-#### Transacción pre-autorizada
-
-Es posible que una cuenta preautorice una transacción particular añadiendo el hash de la futura transacción como firmante en la cuenta. Para eso, necesitas preparar la transacción previamente con el número de secuencia adecuado. Luego puedes obtener el hash de esta transacción y agregarlo como firmante a la cuenta.
-
-Los firmantes de este tipo se eliminan automáticamente de la cuenta cuando una transacción coincidente es aplicada, independientemente de si la transacción tiene éxito o falla. En caso de que una transacción coincidente nunca se envíe, el firmante permanece y debe ser eliminado manualmente usando la operación Set Options.
-
-Este tipo de firmante es especialmente útil en cuentas en custodia. Puedes preautorizar dos transacciones diferentes. Ambas pueden tener el mismo número de secuencia pero destinos distintos. Esto significa que solo una de ellas puede ejecutarse.
-
-#### Hash(x)
-
-:::note
-
-La firma Hash(x) es un concepto diferente de los hashes de transacción. Los hashes de transacción son identificadores únicos generados al aplicar una función hash criptográfica a los datos de una transacción en una blockchain. Sirven como una huella digital y permiten a los usuarios verificar y referenciar transacciones en la red. Hash(x) es un tipo de firma.
-
-:::
-
-Agregar una firma de tipo hash(x) permite a cualquiera que conozca x firmar la transacción. Este tipo de firmante es especialmente útil en [intercambios atómicos entre cadenas](https://en.bitcoin.it/wiki/Atomic_cross-chain_trading) que se necesitan para protocolos inter-blockchain como las [lightning networks](https://lightning.network/).
-
-Primero, crea un valor aleatorio de 256 bits, al que llamamos x. El hash SHA256 de ese valor puede añadirse como un firmante de tipo hash(x). Luego, para autorizar una transacción, x se añade como una de las firmas de la transacción. Ten en cuenta que x será conocido públicamente tan pronto como una transacción sea enviada a la red con x como firma. Esto significa que cualquiera podrá firmar por esa cuenta con el firmante hash(x) a partir de ese momento. A menudo querrás que haya firmantes adicionales para que alguien deba tener una clave secreta particular y conocer x para alcanzar el umbral de peso requerido para autorizar transacciones en la cuenta.
-
-## Ejemplos
-
-A continuación, mostraremos algunos ejemplos de lo potente que son los umbrales y pesos. Si quieres aprender más sobre el uso de firmantes avanzados como `hash(x)`, consulta [esta publicación en el blog](https://stellar.org/blog/developers/messing-around-with-multi-sig) para algunos ejemplos divertidos.
-
-- Ejemplo 1: Anchors
-- Ejemplo 2: Cuentas conjuntas
-- Ejemplo 3: Cuentas de gastos
-- Ejemplo 4: Cuentas de empresa
-
-### Ejemplo 1: Anchors
-
-Gestionas un anchor que quiere mantener su clave emisora fuera de línea. De esa manera, es menos probable que un actor malintencionado consiga la clave del anchor y comience a emitir crédito de manera indebida. Sin embargo, tu anchor necesita autorizar a las personas que poseen crédito ejecutando la operación `Set Trust Line Flags`. Antes de emitir crédito a una cuenta, necesitas verificar que esa cuenta sea válida.
-
-Multisig te permite hacer todo esto sin exponer la clave maestra de tu anchor. Puedes añadir otra clave de firma a tu cuenta con la operación `Set Options`. Esta clave adicional debería tener un peso por debajo del umbral medio de la cuenta de tu anchor. Dado que `Set Trust Line Flags` es una operación de umbral bajo, esta clave extra autoriza a los usuarios a poseer el crédito de tu anchor. Pero, como `Payment` es una operación de umbral medio, esta clave no permite que nadie que comprometa tu anchor emita crédito.
-
-Tu configuración de cuenta:
-
-<CodeExample>
-
-```
-Master Key Weight: 2
-Additional Signing Key Weight: 1
-Low Threshold: 0
-Medium Threshold: 2
-High Threshold: 2
-```
-
-</CodeExample>
-
-### Ejemplo 2: Cuentas conjuntas
-
-Quieres configurar una cuenta conjunta con Bilal y Carina de modo que cualquiera de ustedes pueda autorizar un pago. También quieres configurar la cuenta para que, si decides cambiar firmantes (por ejemplo, eliminar o añadir a alguien), una operación de umbral alto, los 3 deban estar de acuerdo. Añades a Bilal y Carina como firmantes de la cuenta conjunta. También aseguras que se necesiten todos los pesos de tus claves para superar el umbral alto, pero solo uno para superar el umbral medio.
-
-Configuración de cuenta conjunta:
-
-<CodeExample>
-
-```
-Master Key Weight: 1
-Low Threshold: 0
-Medium Threshold: 0
-High Threshold: 3
-Bilal's Signing Key Weight: 1
-Carina's Signing Key Weight: 1
-```
-
-</CodeExample>
-
-### Ejemplo 3: Cuentas de gastos
-
-Controlas totalmente una cuenta de gastos, pero quieres que tus dos compañeros de trabajo Diyuan y Emil puedan autorizar transacciones desde esta cuenta. Añades las claves de firma de Diyuan y Emil a la cuenta de gastos. Si Diyuan o Emil dejan la empresa, puedes eliminar su clave de firma, lo cual es una operación de umbral alto.
-
-Configuración de cuenta de gastos:
-
-<CodeExample>
-
-```
-Master Key Weight: 3
-Low Threshold: 0
-Medium Threshold: 0
-High Threshold: 3
-Diyuan's Key Weight: 1
-Emil's Key Weight: 1
-```
-
-</CodeExample>
-
-### Ejemplo 4: Cuentas de empresa
-
-**Advertencia**: este ejemplo implica establecer el peso de la clave maestra de una cuenta en 0. Ten mucho cuidado si decides hacer eso: esa clave ya no podrá firmar ningún tipo de transacción, por lo que corres el riesgo de bloquearte permanentemente fuera de tu cuenta. Asegúrate de haber pensado bien lo que haces, que entiendas las implicaciones y que cambies los pesos en el orden correcto.
-
-Tu empresa quiere configurar una cuenta que requiera que 3 de 6 empleados estén de acuerdo para cualquier transacción desde esa cuenta.
-
-Configuración de cuenta de empresa:
-
-<CodeExample>
-
-```
-Master Key Weight: 0 (Turned off so this account can't do anything without an employee.)
-Low Threshold: 3
-Medium Threshold: 3
-High Threshold: 3
-Employee 1 Key Weight: 1
-Employee 2 Key Weight: 1
-Employee 3 Key Weight: 1
-Employee 4 Key Weight: 1
-Employee 5 Key Weight: 1
-Employee 6 Key Weight: 1
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/transaction-lifecycle.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/transaction-lifecycle.mdx
deleted file mode 100644
index 0d32ceaa14..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/transaction-lifecycle.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Ciclo de vida de la transacción
-sidebar_position: 30
----
-
-### 1. Creación (Creador de la transacción)
-
-Un usuario crea una transacción configurando la cuenta fuente, el número de secuencia, la lista de operaciones y sus respectivos parámetros, la tarifa o tarifa adicional, y opcionalmente un memo y/o precondiciones.
-
-#### 1b. Simulación de transacciones
-
-Las transacciones de contratos inteligentes pasan por una simulación de transacciones, donde la transacción se ejecuta en un entorno simulado para verificar errores y asegurar que pueda ejecutarse con éxito. Lee más en la [sección de simulación de transacciones](../contract-development/contract-interactions/transaction-simulation.mdx).
-
-### 2. Firma (Firmantes de la transacción)
-
-Una vez que la transacción está completa, se convierte en un sobre de transacción que contiene la transacción en sí y una lista de firmantes. Todas las firmas requeridas deben ser recolectadas y añadidas a la lista de firmantes del sobre de transacción. Comúnmente, es solo la firma de la cuenta que realiza la transacción, pero configuraciones más complicadas pueden requerir recolectar firmas de múltiples partes. Todas las firmas requeridas deben ser recolectadas y agregadas a la lista de firmantes del sobre de la transacción. Comúnmente, es solo la firma de la cuenta que realiza la transacción, pero configuraciones más complicadas pueden requerir recoger firmas de múltiples partes. Lee más sobre firmas en la [sección de Firmas y Multisig](./signatures-multisig.mdx).
-
-### 3. Presentación (Presentador de la transacción)
-
-Después de firmar, la transacción ahora puede ser presentada a la red Stellar. Si la transacción es inválida, será rechazada inmediatamente por Stellar Core, el número de secuencia de la cuenta no se incrementará, y no se consumirá ninguna tarifa de la cuenta fuente. Si la transacción es inválida, será rechazada inmediatamente por Stellar Core, el número de secuencia de la cuenta no se incrementará, y no se consumirá ninguna tarifa de la cuenta fuente. Solo se puede consumir una transacción (y un número de secuencia) para la misma cuenta por ledger. Las transacciones normalmente se envían usando Stellar RPC, pero también puedes enviar la transacción directamente a una instancia de Stellar Core.
-
-### 4. Propagando (Validador)
-
-Una vez que Stellar Core ha determinado que una transacción es válida, propagará la transacción a todos los demás servidores a los que está conectado. De esta manera, una transacción válida se inunda a toda la red Stellar. De este modo, una transacción válida se inunda en toda la red Stellar.
-
-### 5. Creando un conjunto de transacciones candidato (Validador)
-
-Cuando es el momento de cerrar el ledger, cada validador de Stellar Core toma todas las transacciones válidas que conoce desde el último cierre del ledger y las recopila en un conjunto de transacciones candidato. Si escucha sobre alguna transacción entrante ahora, la pone a un lado para el próximo cierre del ledger. Si el número de operaciones en el conjunto de transacciones candidato es mayor que el número máximo de operaciones por ledger, las transacciones serán priorizadas por su tarifa para inclusión en el conjunto. Si escucha sobre cualquier transacción entrante ahora, las aparta para el próximo cierre de ledger. Si el número de operaciones en el conjunto de transacciones candidato es mayor que el número máximo de operaciones por ledger, las transacciones se priorizarán por su tarifa para inclusión en el conjunto.
-
-### 6. Nominando un conjunto de transacciones (Validador)
-
-Una vez que cada validador ha creado un conjunto de transacciones candidato, el conjunto es nominado a la red.
-
-### 7. El Protocolo de Consenso Stellar (SCP) determina el conjunto final de transacciones (Red de Validadores)
-
-SCP resuelve cualquier diferencia entre los conjuntos de transacciones candidato y finalmente determina un único conjunto de transacciones para aplicar, el tiempo de cierre del ledger y cualquier actualización al protocolo que necesite aplicarse en toda la red al momento de aplicar.
-
-Si una transacción no llega al conjunto de transacciones, se mantiene en memoria para ser añadida al siguiente conjunto de transacciones en base a un esfuerzo de mejor intento.
-
-Si una transacción se mantiene en memoria después de un cierto número de cierres del ledger, será prohibida para varios ledgers adicionales. Esto significa que no se intentará incluirla en un conjunto de transacciones candidato de ledgers adicionales durante este tiempo. Esto significa que no se hará ningún intento por incluirlo en un conjunto candidato de transacciones en ledgers adicionales durante este tiempo.
-
-### 8. El orden de aplicación de las transacciones se determina (Red de Validadores)
-
-Una vez que SCP acuerda un conjunto de transacciones particular, se calcula el orden de aplicación para el conjunto de transacciones. Esto mezcla el orden del conjunto para crear incertidumbre para las transacciones competidoras.
-
-### 9. Se recogen las tarifas (Validador)
-
-Las tarifas se recogen para todas las transacciones simultáneamente.
-
-### 10. Aplicación (Validador)
-
-Cada transacción se aplica en el orden previamente determinado. Para cada transacción, el número de secuencia de la cuenta se consume (aumentado en 1), se vuelve a verificar la validez de la transacción y se aplica cada operación en el orden en que ocurren en la transacción. Las operaciones pueden fallar en esta etapa debido a errores que pueden ocurrir fuera de la verificación de validez de la transacción y la operación. Por ejemplo, un saldo insuficiente para un pago no se verifica en la presentación y fallaría en este momento. La transacción completa fallará si alguna operación falla, y todas las operaciones anteriores serán revertidas.
-
-### 11. Actualizaciones del Protocolo (Validador)
-
-Finalmente, se ejecutan actualizaciones si se llevó a cabo una actualización. Esto puede incluir lógica arbitraria para actualizar el estado del ledger para actualizaciones del protocolo, junto con modificaciones de encabezado del ledger, incluyendo la versión del protocolo, la tarifa base, el número máximo de operaciones por ledger, etc. Una vez que esto se ha completado, el ciclo de vida comienza de nuevo.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/glossary.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/glossary.mdx
deleted file mode 100644
index c6aa133804..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/glossary.mdx
+++ /dev/null
@@ -1,400 +0,0 @@
----
-title: "Glosario de Blockchain: Términos y conceptos clave para comprender Stellar"
-sidebar_label: Glosario
-sidebar_position: 40
-description: Explora un glosario completo de términos de blockchain. Aprende conceptos clave, definiciones y términos técnicos para comprender mejor la red y el ecosistema Stellar.
----
-
-# Glosario
-
-### Cuenta
-
-Una estructura de datos central de Stellar para mantener saldos, firmar transacciones e emitir activos.
-
-Consulta la [sección de Cuentas](./fundamentals/stellar-data-structures/accounts.mdx) para aprender más.
-
-### ID de Cuenta
-
-La clave pública utilizada para crear una cuenta. Esta clave persiste a través de diferentes asignaciones de claves. Está [representada](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md) en base32.
-
-### Ancla
-
-Las rampas de entrada y salida en la red Stellar que facilitan la conversión uno a uno de representaciones fuera de cadena hacia y desde activos tokenizados, por ejemplo, tokens digitales que representan depósitos bancarios.
-
-Lee más en la [entrada de la Enciclopedia de Anchor](./fundamentals/anchors.mdx)
-
-### Aplicación (app)
-
-Un programa de software diseñado para que los usuarios realicen una tarea específica (además de operar el ordenador en sí).
-
-### Activo
-
-Fiat, físico u otros tokens de valor que son rastreados, mantenidos o transferidos por la red distribuida de Stellar.
-
-Consulta la [sección de Activos](./fundamentals/stellar-data-structures/assets.mdx) para aprender más.
-
-### Saldo
-
-La cantidad de un activo dado que una cuenta posee. Cada activo tiene su propio saldo y estos saldos se almacenan en líneas de confianza para cada activo, excepto XLM, que es poseído directamente por la cuenta.
-
-### BalanceID
-
-Parámetro requerido al reclamar una nueva entrada creada a través de la operación de reclamación de saldo recuperable. Consulta [ClaimableBalanceID](#claimablebalanceid).
-
-### Tasa base
-
-La tarifa que estás dispuesto a pagar por operación en una transacción.
-
-Esto difiere de la Tasa Base Efectiva, que es la tarifa real pagada por cada operación para que una transacción se registre en el ledger. Cuando la red está en modo de precios por auge, la tasa base efectiva varía en función de un mecanismo de subasta. Cuando no está así, la tasa base efectiva se establece por defecto en el mínimo de la red, que actualmente es de 100 stroops por operación.
-
-Aprende más en nuestra [sección de Tarifas](./fundamentals/fees-resource-limits-metering.mdx).
-
-### Reserva base
-
-Una unidad de medida utilizada para calcular el saldo mínimo de una cuenta. Una reserva base actualmente es <b>0,5</b> XLM.
-
-Aprende más en nuestra [sección de Lumens](./fundamentals/lumens.mdx#base-reserves).
-
-### Eliminar
-
-Remueve un activo de circulación, lo que puede ocurrir de dos maneras: 1) un poseedor envía el activo de vuelta a la cuenta emisora 2) un emisor recupera un activo habilitado para recuperación de la cuenta de un poseedor.
-
-### CAPs (Propuestas de Avance Core)
-
-Propuestas de estándares para mejorar el protocolo Stellar. Los CAPs tratan sobre cambios en el protocolo core de la red Stellar.
-
-Encuentra una lista de todos los CAPs en borrador, aceptados, implementados y rechazados en [GitHub](https://github.com/stellar/stellar-protocol/tree/master/core).
-
-### Predicado de Reclamación
-
-Una estructura de datos recursiva utilizada para construir condicionales complejos con diferentes valores de ClaimPredicateType.
-
-### ClaimableBalanceID
-
-Un hash SHA-256 del OperationID para saldos recuperables.
-
-### Reclamante
-
-Un objeto que contiene tanto la cuenta de destino que puede reclamar el ClaimableBalanceEntry como un ClaimPredicate que debe evaluarse como verdadero para que la reclamación tenga éxito.
-
-### Recuperación
-
-Una cantidad de activo de una línea de confianza o saldo recuperable eliminado (recuperado) del balance de un destinatario.
-
-Consulta la [Guía de recuperación (Clawback)](../build/guides/transactions/clawbacks.mdx) para más información.
-
-### Cuenta de contrato
-
-Una cuenta implementada como un contrato inteligente, que permite al contrato definir una lógica de autorización personalizada y la aplicación de políticas en cadena antes de que la autorización tenga éxito, en lugar de depender de las funciones integradas del protocolo.
-
-### Token de contrato
-
-Tokens creados y gestionados a través de contratos inteligentes. Estos activos son programables y están gobernados por la lógica on-chain en lugar de características de protocolo integradas.
-
-:::note
-
-Los tokens de contrato solían llamarse "tokens personalizados", término que ha quedado obsoleto.
-
-:::
-
-### Crear operación de cuenta
-
-Realiza un pago a una clave pública con saldo 0 (dirección Stellar), creando así la cuenta. Debes usar esta operación para inicializar una cuenta en lugar de una operación de pago estándar.
-
-### Pagos cruzados de activos
-
-Un pago que maneja automáticamente la conversión de activos disímiles.
-
-### Token personalizado
-
-Este término ha quedado obsoleto en favor de [tokens de contrato](#contract-token).
-
-### Intercambio descentralizado
-
-Un intercambio distribuido que permite el comercio y la conversión de activos en la red.
-
-Aprende más en nuestra sección de [Liquidez en Stellar](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#sdex).
-
-### Representación de Datos Externos (XDR)
-
-El tipo de codificación utilizada para las operaciones y datos que se ejecutan en stellar-core.
-
-### Federación
-
-El protocolo de federación Stellar asigna direcciones Stellar a un identificador similar a un correo electrónico que proporciona más información sobre un usuario dado. Es una forma para que el software cliente Stellar resuelva direcciones similares a correos electrónicos como name\*yourdomain.com en IDs de cuenta `G...`. Las direcciones federadas ofrecen una manera fácil para que los usuarios compartan detalles de pago usando una sintaxis que interoperar entre diferentes dominios y proveedores.
-
-Lee más en [GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0002.md).
-
-### Banderas
-
-Los flags controlan el acceso a un activo a nivel de cuenta. Aprende más sobre flags en nuestra [sección sobre Controlar el Acceso a un Activo](../tokens/control-asset-access.mdx#controlling-access-to-an-asset-with-flags).
-
-### Fuzzing
-
-Una prueba automatizada que rápidamente introduce enormes cantidades de datos aleatorios y mal formados en un sistema para revelar resultados adversos o inesperados que indican vulnerabilidades.
-
-Lee más en el [Tutorial de Pruebas de Fuzzing](../build/smart-contracts/example-contracts/fuzzing.mdx).
-
-### GitHub
-
-Un repositorio en línea para documentos que pueden ser accedidos y compartidos entre múltiples usuarios; anfitrión del código fuente de la plataforma Stellar, documentación y otros repositorios open-source.
-
-### Dominio principal
-
-Un nombre de dominio totalmente calificado (FQDN) vinculado a una cuenta Stellar, usado para generar un enlace on-chain a un archivo de información Stellar, que contiene metadatos fuera de cadena. Consulta la operación Establecer Opciones. Puede tener hasta 32 caracteres.
-
-### Stellar RPC
-
-Un nodo que proporciona una interfaz para enviar transacciones y leer datos de la red Stellar.
-
-### Inflación
-
-La operación de inflación está obsoleta porque no funcionaba como se esperaba. La mayoría de los usuarios la ignoraban o la usaban para beneficio personal, y los costos seguían aumentando, por lo que la red votó para desactivarla en el Protocolo 12 mediante [CAP-26: Deshabilitar el mecanismo de inflación](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0026.md).
-
-Lee sobre la implementación [aquí](https://github.com/stellar/stellar-core/releases/tag/v12.0.0).
-
-Lee el blog relacionado [aquí](https://stellar.org/blog/foundation-news/our-proposal-to-disable-inflation).
-
-### JSON
-
-Un formato estándar legible por humanos y máquinas para el intercambio de datos estructurados.
-
-### Keypair
-
-Una clave pública y privada combinada utilizada para asegurar transacciones. Puedes usar cualquier billetera Stellar, SDK o el Stellar Lab para generar un keypair válido.
-
-### Almacenamiento de claves
-
-Un almacén o archivo cifrado que sirve como un repositorio de claves privadas, certificados y claves públicas.
-
-### Ledger
-
-Una representación del estado del universo Stellar en un momento dado, compartida entre todos los nodos de la red.
-
-Aprende más en la [sección de Ledgers](./fundamentals/stellar-data-structures/ledgers.mdx).
-
-### LedgerKey
-
-LedgerKey contiene información para identificar un ledgerEntry específico. Es una unión que puede ser cualquiera de los LedgerEntryTypes (CUENTA, LÍNEA DE CONFIANZA, OFERTA, DATOS, SALDO RECLAMABLE, Fondos de Liquidez, Datos de Contrato, Código de Contrato, Configuración o TTL).
-
-### Responsabilidad
-
-Una obligación de compra o venta, requerida para satisfacer (vender) o acomodar (comprar) transacciones.
-
-### Lumen (XLM)
-
-El token nativo integrado en la red Stellar.
-
-Aprende más sobre lumens en nuestra [sección de Lumens](./fundamentals/lumens.mdx).
-
-### Clave maestra
-
-La clave privada utilizada en la creación inicial de la cuenta.
-
-### Saldo mínimo
-
-El saldo mínimo permitido en lumens para una cuenta Stellar, actualmente 1 lumen.
-
-Aprende más en nuestra [sección de Lumens](./fundamentals/lumens.mdx#minimum-balance).
-
-### Capacidad de la red
-
-El número máximo de operaciones por ledger, según lo determinado por el voto de los validadores. Actualmente <b>1.000</b> operaciones para la mainnet y <b>100</b> operaciones para la testnet.
-
-### Número de subentradas
-
-El número de entradas que posee una cuenta, utilizado para calcular el saldo mínimo de la cuenta.
-
-### Operación
-
-Un comando individual que modifica el ledger.
-
-Aprende más en nuestra [sección de Operaciones y Transacciones](./fundamentals/transactions/operations-and-transactions.mdx).
-
-### OperationID
-
-Contiene la cuenta de origen de la transacción, el número de secuencia y el índice de operación de la operación CreateClaimableBalance en una transacción.
-
-### Orden
-
-Una oferta para comprar o vender un activo.
-
-Aprende más en nuestra sección de [Liquidez en Stellar: SDEX y Pools de Liquidez](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#orders).
-
-### Libro de órdenes
-
-Un registro de órdenes pendientes en la red Stellar.
-
-Aprende más en nuestra sección de [Liquidez en Stellar: SDEX y Pools de Liquidez](./fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx#order-books).
-
-### Orden pasiva
-
-Una orden que no se ejecuta contra una orden de contraparte comercializable con el mismo precio; se completa solo si los precios no son iguales.
-
-### Frase de contraseña
-
-La Mainnet y la Testnet tienen cada una su propia frase de contraseña única, que se utilizan para validar firmas en una transacción dada.
-
-Aprende más sobre los passphrases de red en la [sección de Redes](../networks/README.mdx#network-passphrases).
-
-### Búsqueda de rutas
-
-El proceso de determinar el mejor camino para un pago, evaluando los libros de órdenes actuales y encontrando la serie de conversiones para lograr la mejor tasa.
-
-### Canal de pago
-
-Permite que dos partes que transaccionan frecuentemente entre sí muevan la mayor parte de su actividad fuera de la cadena, mientras aún registran los saldos iniciales y el asentamiento final en la cadena.
-
-### Precondición
-
-Requisitos opcionales que puedes añadir para controlar la validez de una transacción.
-
-Consulta la [sección de Validez de Operaciones y Transacciones](./fundamentals/transactions/operations-and-transactions.mdx#preconditions) para más información.
-
-### Precio
-
-La relación del activo cotizado y el activo base en una orden.
-
-### Clave pública
-
-La parte pública de un keypair que identifica una cuenta Stellar. La clave pública es pública; es visible en el ledger, cualquiera puede buscarla y se utiliza cuando se envían pagos a la cuenta, identificando al emisor de un activo y verificando que una transacción está autorizada.
-
-### Mainnet o Pubnet
-
-La Red Pública Stellar, también conocida como mainnet, es la principal red utilizada por aplicaciones en producción.
-
-Lee más en nuestra [sección de Redes](../networks/README.mdx).
-
-### Número de secuencia
-
-Utilizado para identificar y verificar el orden de las transacciones con la cuenta de origen.
-
-El número de secuencia de una transacción siempre debe aumentar en uno (a menos que se establezcan precondiciones de número de secuencia mínimo o se use una operación de incremento de secuencia). Los SDK y el Stellar Lab incrementan automáticamente el número de secuencia de la cuenta en uno cuando construyes una transacción.
-
-### Clave secreta (privada)
-
-La clave privada es parte de un keypair, que está asociado con una cuenta. No compartas tu clave secreta con nadie.
-
-### SEPs (Propuestas del Ecosistema Stellar)
-
-Estándares y protocolos para permitir que el ecosistema Stellar sea interoperable.
-
-Aprende más en nuestra [sección de SEPs](./fundamentals/stellar-ecosystem-proposals.mdx).
-
-### Firmante
-
-Se refiere a la clave maestra o a cualquier otra clave de firma añadida posteriormente. Un firmante se define como el par: clave pública + peso. Los firmantes pueden ser establecidos con la operación de Establecer Opciones.
-
-Consulta nuestra [Entrada de Enciclopedia sobre firma y firmas múltiples](./fundamentals/transactions/signatures-multisig.mdx) para más información.
-
-### Contrato inteligente
-
-Contratos autoejecutables con los términos del acuerdo escritos directamente en código, automáticamente exigibles sin necesidad de intermediarios.
-
-### Soroban
-
-La plataforma de contratos inteligentes en la red Stellar. El nombre "Soroban" proviene del ábaco japonés, que es una herramienta tradicional de conteo utilizada para cálculos matemáticos. El ábaco Soroban es un instrumento ligero conocido por su eficiencia y precisión en la realización de operaciones aritméticas.
-
-### Cuenta de origen
-
-La cuenta que origina una transacción. Esta cuenta también proporciona la tarifa y el número de secuencia para la transacción.
-
-### Starlight
-
-El protocolo de capa 2 de Stellar que permite canales de pago bidireccionales.
-
-### Stellar
-
-Una red descentralizada y federada de pares que permite a la gente enviar pagos en cualquier activo en cualquier parte del mundo de forma instantánea y con tarifas mínimas.
-
-### Protocolo de Consenso Stellar (SCP)
-
-Proporciona una forma de alcanzar consenso sin depender de un sistema cerrado para registrar con precisión las transacciones financieras.
-
-Consulta nuestra [sección de SCP](./fundamentals/stellar-consensus-protocol.mdx) para aprender más.
-
-### Stellar Core
-
-Una máquina de estado replicada que mantiene una copia local de un ledger criptográfico y procesa transacciones contra él, en consenso con un conjunto de usuarios; también, la implementación de referencia para el agente de igual a igual que gestiona la red Stellar.
-
-### Stellar Development Foundation (SDF)
-
-Una organización sin fines de lucro fundada para apoyar el desarrollo y el crecimiento de la red Stellar.
-
-### Stellar.toml
-
-Un archivo de configuración formateado que contiene información publicada sobre un nodo y una organización. Para más información, consulta el [especificación del archivo de información Stellar (SEP-0001)](https://stellar.org/protocol/sep-1)
-
-### Stroop
-
-Así como los céntimos son a los dólares, los stroops son a los activos: la unidad más pequeña de un activo, una diez-millonésima parte.
-
-### Testnet
-
-La Red de Pruebas Stellar es mantenida por la Stellar Development Foundation, que los desarrolladores pueden usar para probar aplicaciones. Testnet es gratis de usar y proporciona la misma funcionalidad que la red principal (pública).
-
-Lee más en nuestras [Redes](../networks/README.mdx).
-
-### Umbral
-
-El nivel de acceso para una operación.
-
-También se utiliza para describir la relación de nodos validadores en un quorum set que deben estar de acuerdo para alcanzar consenso como parte del Protocolo de Consenso Stellar.
-
-Lee más sobre umbrales de operación en la [sección de Operaciones y Transacciones](./fundamentals/transactions/operations-and-transactions.mdx#operations).
-
-Aprende más sobre validadores de quorum set en nuestra [sección del Protocolo de Consenso Stellar](./fundamentals/stellar-consensus-protocol.mdx).
-
-### Límites de tiempo
-
-Una característica opcional que puedes aplicar a una transacción para imponer un límite de tiempo en la transacción; ya sea que la transacción llegue al ledger o expire (falle) dependiendo de tus parámetros de tiempo.
-
-Lee más sobre los límites de tiempo en nuestra [sección de Validez de Operaciones y Transacciones](./fundamentals/transactions/operations-and-transactions.mdx#transaction-and-operation-validity).
-
-### Transacción
-
-Un grupo de 1 a 100 operaciones que modifican el estado del ledger.
-
-Lee más en la [sección de Operaciones y Transacciones](./fundamentals/transactions/operations-and-transactions.mdx#transactions).
-
-### Sobre
-
-Un envoltorio para una transacción que lleva las firmas.
-
-### Tasa de transacción
-
-Stellar requiere una pequeña tarifa por todas las transacciones para prevenir el spam en el ledger y priorizar las transacciones durante la escalada de tarifas.
-
-Aprende más en nuestra [sección de Lumens](./fundamentals/lumens.mdx#transaction-fees).
-
-### Línea de confianza
-
-Una opción explícita para que una cuenta mantenga un activo particular que rastrea pasivos, el saldo del activo y también puede limitar la cantidad de un activo que una cuenta puede mantener.
-
-Aprende más en nuestra [sección de Cuentas](./fundamentals/stellar-data-structures/accounts.mdx#trustlines).
-
-### TTL (Tiempo de Vida)
-
-El TTL de un contrato inteligente es cuántos ledgers permanecen hasta que la entrada de datos ya no esté activa.
-
-Lee más en la [sección de archivo de estado](./fundamentals/contract-development/storage/state-archival.mdx#ttl).
-
-### Tipo
-
-La clasificación de datos que dicta el tipo de datos que se puede almacenar y cómo se puede manipular dentro de un contrato inteligente.
-
-### Sello de tiempo UNIX
-
-Un número entero que representa una fecha y hora dadas, como se utiliza en computadoras UNIX y Linux.
-
-### Validador
-
-Un validador básico realiza un seguimiento del ledger y envía transacciones para posible inclusión. Asegura el acceso confiable a la red y la aprobación de las transacciones. Un validador completo realiza las funciones de un validador básico, pero también publica un archivo de historia que contiene instantáneas del ledger, incluidas todas las transacciones de la red y sus resultados. Asegura un acceso confiable a la red y la aprobación de las transacciones. La moneda nativa de la red Stellar.
-
-### XLM (lumens)
-
-Una interfaz que le da a un usuario acceso a una cuenta almacenada en el ledger; ese acceso está controlado por la clave secreta de la cuenta. La billetera permite a los usuarios almacenar y gestionar sus activos.
-
-### Billetera
-
-Una interfaz que da acceso a un usuario a una cuenta almacenada en el ledger; ese acceso está controlado por la clave secreta de la cuenta. La billetera permite a los usuarios almacenar y gestionar sus activos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/README.mdx
deleted file mode 100644
index 8b59737a21..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Aprendizaje Interactivo
-sidebar_position: 60
----
-
-import DocCardList from "@theme/DocCardList";
-
-Aprende haciendo con esta colección de recursos diseñados para que comiences a usar la red Stellar en poco tiempo.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/dapp-world.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/dapp-world.mdx
deleted file mode 100644
index 636b6b22d1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/dapp-world.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Dominar el desarrollo de contratos inteligentes en Rust en Stellar
-sidebar_position: 30
----
-
-Aprende a desarrollar contratos inteligentes seguros y eficientes en la red Stellar utilizando Rust. Este curso práctico es perfecto para desarrolladores de blockchain que buscan aprovechar el ecosistema descentralizado de Stellar.
-
-¡Consulta el curso en App World [Dominar el desarrollo de contratos inteligentes en Rust en Stellar](https://dapp-world.com/course/master-rust-smart-contract-development-on-stellar)!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/fca00c.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/fca00c.mdx
deleted file mode 100644
index 299a7d9044..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/fca00c.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-title: Rápido, Barato y Fuera de Control
-sidebar_position: 20
----
-
-Rápido, Barato y Fuera de Control (FCA00C) es una colección de juegos y tutoriales diseñados para familiarizarte con los contratos inteligentes en la red Stellar. El Tutorial te guía a través de los conceptos básicos del desarrollo de contratos inteligentes en una serie de seis misiones. Este es un excelente lugar para comenzar a aprender sobre contratos inteligentes de Stellar y el desarrollo de contratos inteligentes.
-
-Aprende más y juega todos los juegos en el [sitio fca00c](https://fastcheapandoutofcontrol.com).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/quest.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/quest.mdx
deleted file mode 100644
index bab3d4756d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/interactive/quest.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Stellar Quest
-sidebar_position: 10
----
-
-Stellar Quest te enseña sobre las operaciones y fundamentos de Stellar en una experiencia gamificada. Incluye tres conjuntos de cinco misiones junto con tres misiones secundarias adicionales (aumento de tarifas, creación de NFTs y cuentas muxed) y una misión pionera que te enseña sobre cómo configurar una billetera.
-
-Stellar Quest se puede jugar utilizando [el Stellar Lab](https://lab.stellar.org/?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;;) para no programadores o usando código manual.
-
-Learn more and play the games by going to the [Stellar Quest site](https://quest.stellar.org)!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/README.mdx
deleted file mode 100644
index 05832b7f6d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Migrar de Otra Cadena
-sidebar_position: 50
----
-
-import DocCardList from "@theme/DocCardList";
-
-Adapta tus proyectos existentes para trabajar con Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/cosmos.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/cosmos.mdx
deleted file mode 100644
index 7818138997..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/cosmos.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-sidebar_position: 30
-title: Cosmos
-description: Migra tu código de contrato inteligente de Cosmos a Soroban
-draft: true
----
-
-No sé, ¿como copiar/pegarlo?
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/README.mdx
deleted file mode 100644
index 1793ba3709..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Redes EVM
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Adapta tus contratos inteligentes existentes compatibles con Ethereum para que funcionen con Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/introduction-to-solidity-and-rust.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/introduction-to-solidity-and-rust.mdx
deleted file mode 100644
index 300c17de80..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/introduction-to-solidity-and-rust.mdx
+++ /dev/null
@@ -1,40 +0,0 @@
----
-sidebar_position: 0
-title: Introducción a Solidity, Rust y Soroban
-description: Explora los fundamentos de Solidity, Rust y Soroban.
----
-
-# Introducción
-
-Estamos emocionados de presentarte Soroban, una poderosa plataforma de contratos inteligentes diseñada para ser sensata, desarrollada a gran escala y amigable para desarrolladores, con un enfoque en los beneficios de rendimiento y seguridad de Rust. Con su interfaz amigable y características poderosas, Soroban ofrece una plataforma ideal para desarrolladores que buscan una manera más eficiente y efectiva de crear aplicaciones descentralizadas y hacer la transición de Solidity a Rust. En este artículo, exploraremos los fundamentos de Solidity, Rust y Soroban, y te guiaremos a través de la configuración del entorno de desarrollo para comenzar tu viaje con la compatibilidad de contratos inteligentes de Rust en Soroban.
-
-## Solidity y Desarrollo de Dapps
-
-Solidity es un lenguaje de programación de alto nivel y tipado estático, utilizado principalmente para desarrollar contratos inteligentes en la Máquina Virtual de Ethereum (EVM). Permite la creación de aplicaciones descentralizadas (dapps) que pueden ejecutarse en diversas plataformas de blockchain, automatizando transacciones e interacciones complejas sin la necesidad de una autoridad central.
-
-## Rust: Rendimiento y Seguridad
-
-Rust es un lenguaje de programación de sistemas que enfatiza la seguridad, la concurrencia y el rendimiento. Sus características únicas, como un fuerte sistema de tipos estáticos, modelo de propiedad y garantías de seguridad de memoria, lo convierten en una opción ideal para desarrollar aplicaciones de alto rendimiento y seguras, incluidos contratos inteligentes.
-
-## Soroban: Lógica Programable
-
-Soroban, una plataforma de contratos inteligentes sensata y desarrollada a gran escala, ofrece una experiencia amigable para desarrolladores e incluye todo lo necesario. Si bien comparte los mismos principios de escalabilidad y practicidad que Stellar, Soroban también puede funcionar como una plataforma independiente e integrarse con otros procesadores de transacciones, como L2s, ledgers autorizados e incluso otras blockchains. Con Soroban, Classic Stellar gana la funcionalidad adicional de lógica programable en forma de operaciones personalizadas encapsuladas en contratos inteligentes.
-
-Puedes aprender más sobre las características y beneficios de Soroban en la [Descripción General de Soroban](../../../build/smart-contracts).
-
-## Configuración del Entorno de Desarrollo para Rust y Soroban
-
-Para comenzar con Rust y Soroban, sigue los pasos en la [Página de Configuración](../../../build/smart-contracts/getting-started/setup.mdx).
-
-O si quieres comenzar de inmediato, puedes abrir nuestros ejemplos en un entorno de desarrollo listo para usar en Devcontainers haciendo clic en el botón de abajo:
-
-[![Open in Codespaces](https://github.com/codespaces/badge.svg)][open-in-github-codespaces]
-
-[![Open in Codeanywhere](https://codeanywhere.com/img/open-in-codeanywhere-btn.svg)][open-in-code-anywhere]
-
-[open-in-github-codespaces]: https://github.com/codespaces/new?repo=stellar/soroban-examples&editor=web
-[open-in-code-anywhere]: https://app.codeanywhere.com/#https://github.com/stellar/soroban-examples
-
-# Resumen
-
-A medida que emprendas tu viaje con Soroban, recuerda que la plataforma está diseñada para proporcionar una experiencia fluida, eficiente y agradable para los desarrolladores que hacen la transición de Solidity a Rust. Aprovechando los beneficios de rendimiento y seguridad de Rust, junto con las herramientas avanzadas de Soroban, estarás bien equipado para desarrollar contratos inteligentes de alta calidad, eficientes y seguros.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/smart-contract-deployment.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/smart-contract-deployment.mdx
deleted file mode 100644
index 23246e81ef..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/smart-contract-deployment.mdx
+++ /dev/null
@@ -1,1293 +0,0 @@
----
-sidebar_position: 3
-title: Smart Contract Development with Soroban and Hardhat
-description: Explore advanced Solidity and Soroban concepts, craft secure and efficient Soroban smart contracts and deploy and test your contracts in a testnet environment.
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Smart Contract Development with Soroban and Hardhat
-
-In this tutorial, we will discover the similarities in smart contract deployment by examining workflows with Soroban and [Hardhat](https://hardhat.org/). We will dive into the intricacies of each framework, learn to write secure and efficient smart contract code, and harness the power of Rust and Soroban to create customized contract logic.
-
-## Table of Contents
-
-1. [Soroban and Hardhat Comparison](#soroban-and-hardhat-comparison)
-2. [Hardhat vs Soroban SDKs](#hardhat-vs-soroban-sdks)
-3. [Using Rust and Soroban for Smart Contract Development](#developing-smart-contracts-with-rust-and-soroban)
-4. [Vault Contract Deployment and Interaction](#vault-contract-deployment-and-interaction)
-
-## Soroban and Hardhat Comparison
-
-### Introduction
-
-Soroban and Hardhat are both frameworks that enable developers to build, test, and deploy smart contracts. In this section, we will delve into the similarities and distinctions between these two frameworks.
-
-### Soroban Framework
-
-Soroban es un marco basado en Rust diseñado para desarrollar contratos inteligentes en la red Stellar. Diseñado como un marco ligero, con [herramientas para admitir a los desarrolladores](../../../tools/developer-tools/README.mdx), Soroban permite a los desarrolladores crear contratos inteligentes a través de un flujo de trabajo simple e intuitivo.
-
-### Hardhat
-
-Hardhat sirve como un entorno de desarrollo para compilar, desplegar, probar y depurar contratos inteligentes para la EVM. Asiste a los desarrolladores en la gestión y automatización de tareas recurrentes inherentes a la construcción de contratos inteligentes.
-
-### Similaridades
-
-Soroban y Hardhat son marcos potentes diseñados para agilizar el proceso de construir, probar y desplegar contratos inteligentes. Equipadas con una suite integral de herramientas, estos marcos facilitan el desarrollo de contratos inteligentes y su despliegue en sus respectivas máquinas virtuales.
-
-### Diferencias
-
-Soroban, con su diseño ligero, ofrece a los desarrolladores una plataforma excepcional para escribir contratos inteligentes basados en Rust y desplegarlos sin esfuerzo en la red Stellar. En contraste, Hardhat sirve principalmente como un entorno de desarrollo diseñado para la Máquina Virtual de Ethereum, proporcionando un enfoque y audiencia objetivo diferentes.
-
-## Hardhat vs. Soroban SDKs
-
-Hardhat ofrece un flujo de trabajo optimizado para desplegar contratos inteligentes en la Máquina Virtual de Ethereum, con componentes clave como `ethers.js`, `scripts`, y `testing` desempeñando roles cruciales.
-
-Por otro lado, Soroban presenta una alternativa convincente, con potentes SDKs que facilitan el desarrollo y despliegue de contratos inteligentes. En la próxima sección, profundizaremos en [SDKs de Soroban](../../../tools/sdks/README.mdx), comparando componentes de Hardhat y destacando las ventajas únicas que cada plataforma aporta.
-
-### Ethers.js
-
-`Ethers.js` es una biblioteca de `JavaScript` ampliamente utilizada diseñada para la interacción sin problemas con la EVM. Ofrece una interfaz amigable que simplifica la conexión a nodos de Ethereum, la gestión de cuentas y el envío de transacciones. Además, `Ethers.js` proporciona una API robusta para la comunicación eficiente con contratos inteligentes. Esta biblioteca es un componente central del marco Hardhat y puede ser importada en scripts para agilizar el despliegue de contratos inteligentes.
-
-```javascript
-const { ethers } = require("hardhat");
-
-async function main() {
-  const [deployer] = await ethers.getSigners();
-
-  console.log("Deploying contracts with the account:", deployer.address);
-}
-```
-
-### Soroban Client
-
-Soroban ofrece una biblioteca comparable, [`stellar-sdk`](../../../tools/sdks/client-sdks.mdx#javascript-sdk), que permite la interacción sin problemas con contratos inteligentes desplegados en la Red Stellar. Esta biblioteca proporciona una API completa de capa de red para los métodos RPC de Stellar, así como para la API Horizon obsoleta, simplificando el proceso de desarrollar y firmar transacciones. Además, `stellar-sdk` agiliza la comunicación con instancias RPC y admite enviar transacciones o consultar el estado de la red con facilidad.
-
-### Scripts
-
-Los scripts de Hardhat agilizan la automatización de tareas rutinarias, como desplegar y gestionar contratos inteligentes. Los desarrolladores pueden crear estos scripts usando JavaScript o TypeScript, adaptándose a su estilo de programación preferido. Se almacenan en el directorio `scripts` de un proyecto Hardhat y pueden ejecutarse utilizando el comando `npx hardhat run`.
-
-```javascript
-// scripts/deploy.js
-
-async function main() {
-  // Compile and deploy the smart contract
-  const MyContract = await ethers.getContractFactory("MyContract");
-  const myContract = await MyContract.deploy();
-
-  console.log("MyContract deployed to:", myContract.address);
-}
-
-main()
-  .then(() => process.exit(0))
-  .catch((error) => {
-    console.error(error);
-    process.exit(1);
-  });
-```
-
-### Soroban Scripts
-
-Soroban ofrece una amplia colección de SDKs que incluyen capacidades de scripting, asegurando un flujo de trabajo fluido para desplegar y gestionar contratos inteligentes. Los desarrolladores pueden automatizar tareas como compilar, desplegar e interactuar con contratos inteligentes utilizando una variedad de SDKs que admiten la escritura de scripts en lenguajes como [`JavaScript`, `TypeScript`, `Python` y otros](../../../tools/sdks/client-sdks.mdx).
-
-```python
-# This example shows how to deploy a compiled contract to the Stellar network.
-# https://github.com/stellar/soroban-quest/blob/main/quests/6-asset-interop/py-scripts/deploy-contract.py
-
-import time
-
-from stellar_sdk import Network, Keypair, TransactionBuilder
-from stellar_sdk import xdr as stellar_xdr
-from stellar_sdk.soroban import SorobanServer
-from stellar_sdk.soroban.soroban_rpc import TransactionStatus
-
-# TODO: You need to replace the following parameters according to the actual situation
-secret = "SAAPYAPTTRZMCUZFPG3G66V4ZMHTK4TWA6NS7U4F7Z3IMUD52EK4DDEV"
-rpc_server_url = "https://soroban-testnet.stellar.org"
-network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-contract_file_path = "/path/to/compiled/soroban_contract.wasm"
-
-kp = Keypair.from_secret(secret)
-soroban_server = SorobanServer(rpc_server_url)
-
-print("installing contract...")
-source = soroban_server.load_account(kp.public_key)
-
-# with open(contract_file_path, "rb") as f:
-#     contract_bin = f.read()
-
-tx = (
-    TransactionBuilder(source, network_passphrase)
-    .set_timeout(300)
-    .append_install_contract_code_op(
-        contract=contract_file_path,  # the path to the contract, or binary data
-        source=kp.public_key,
-    )
-    .build()
-)
-...
-```
-
-### Testing
-
-Hardhat proporciona un marco de pruebas que permite a los desarrolladores escribir pruebas para sus contratos inteligentes. Estas pruebas pueden escribirse en JavaScript o TypeScript y ejecutarse utilizando el comando `npx hardhat test`.
-
-```javascript
-// test/my-contract.js
-
-const { expect } = require("chai");
-
-describe("MyContract", function () {
-  it("Should return the correct name", async function () {
-    const MyContract = await ethers.getContractFactory("MyContract");
-    const myContract = await MyContract.deploy();
-
-    await myContract.deployed();
-    expect(await myContract.name()).to.equal("MyContract");
-  });
-});
-```
-
-### Soroban Testing
-
-Soroban permite a los usuarios aprovechar el poder del marco de pruebas de Rust para escribir pruebas para sus contratos inteligentes. Estas pruebas pueden escribirse en Rust y ejecutarse usando el comando `cargo test`.
-
-```rust
-#![cfg(test)]
-
-use super::*;
-use soroban_sdk::{vec, Env, Symbol, symbol_short};
-
-#[test]
-fn test() {
-    let env = Env::default();
-    let contract_id = env.register(HelloContract, ());
-    let client = HelloContractClient::new(&env, &contract_id);
-
-    let words = client.hello(&symbol_short!("Dev"));
-    assert_eq!(
-        words,
-        vec![&env, symbol_short!("Hello"), symbol_short!("Dev"),]
-    );
-}
-```
-
-En resumen, mientras Hardhat proporciona un excelente entorno para desplegar contratos inteligentes en la EVM, el marco basado en Rust de Soroban ofrece ventajas significativas en términos de rendimiento, lo que lo convierte en una opción ideal para construir contratos inteligentes seguros y eficientes.
-
-## Desarrollar Contratos Inteligentes con Rust y Soroban
-
-### Introducción
-
-Ahora que hemos examinado el flujo de trabajo de despliegue con Hardhat, exploremos el desarrollo y despliegue de contratos inteligentes con Rust y Soroban. La principal ventaja de utilizar Soroban es su capacidad para aprovechar las características de seguridad y rendimiento de Rust, lo que lo convierte en una excelente opción para desarrollar contratos inteligentes seguros y eficientes.
-
-Hemos aprendido que los contratos inteligentes son contratos autoejecutables que pueden programarse para hacer cumplir automáticamente las reglas y regulaciones de un acuerdo particular. Son un componente central de las aplicaciones descentralizadas (dApps) y la tecnología blockchain. En esta sección, aprenderemos cómo usar Rust y Soroban para desarrollar y desplegar lógica de contrato inteligente personalizada.
-
-### Configuración
-
-Si aún no has configurado el entorno de desarrollo para Soroban, puedes comenzar siguiendo los pasos en la [Página de Configuración](../../../build/smart-contracts/getting-started/setup.mdx).
-
-Este proyecto requiere el uso del archivo `soroban_token_contract.wasm` que necesitarás importar manualmente.
-
-Primero, necesitarás clonar la etiqueta `v22.0.1` del repositorio `soroban-examples`:
-
-```bash
-git clone -b v22.0.1 https://github.com/stellar/soroban-examples
-```
-
-Luego, navega al directorio `soroban-examples/token`
-
-```bash
-cd soroban-examples/token
-```
-
-A continuación, construye el contrato Token usando el siguiente comando:
-
-```bash
-stellar contract build
-```
-
-Esto construirá el archivo `soroban_token_contract.wasm` que necesitarás importar en tu proyecto. El archivo `soroban_token_contract.wasm` se encuentra en el directorio `soroban-examples/target/wasm32v1-none/release`.
-
-```
-soroban-examples
-├── target
-│   └── wasm32v1-none
-│       └── release
-│           └── soroban_token_contract.wasm
-└──
-```
-
-Una vez que tengamos el Token, vamos a crear un nuevo contrato inteligente que lo use.
-
-### Escribir un Contrato Inteligente
-
-Comencemos escribiendo un ejemplo simple de un contrato de vault que permite a los usuarios depositar fondos y retirar sus fondos con rendimiento generado.
-
-Aquí hay un desglose de la mecánica del contrato
-
-- Las acciones son creadas cuando un usuario realiza un depósito.
-- El protocolo DeFi utiliza los depósitos de los usuarios para generar rendimiento.
-- El usuario quema acciones para retirar sus tokens + rendimiento.
-
-En una nueva terminal, vamos a crear un nuevo proyecto en Rust ejecutando el siguiente comando:
-
-```bash
-cargo new --lib vault
-```
-
-Esto creará un nuevo proyecto de Rust llamado `vault`.
-
-Ahora vamos a agregar el archivo `soroban_token_contract.wasm` al proyecto `vault`. Para hacer esto, podemos arrastrar y soltar el archivo en el directorio del proyecto `vault`.
-
-![vault-project](/img/migrating/vault-project.png)
-
-A continuación, necesitaremos agregar el SDK de Soroban como una dependencia. Para hacer esto, abre el archivo `Cargo.toml` en tu proyecto y asegúrate de que coincide con lo siguiente:
-
-```toml
-[package]
-name = "vault"
-version = "0.0.0"
-edition = "2021"
-publish = false
-
-[lib]
-crate-type = ["cdylib"]
-
-[dependencies]
-soroban-sdk = { version = "20.0.0" }
-num-integer = { version = "0.1.45", default-features = false, features = ["i128"] }
-
-[dev_dependencies]
-soroban-sdk = { version = "20.0.0", features = ["testutils"] }
-
-[profile.release]
-opt-level = "z"
-overflow-checks = true
-debug = 0
-strip = "symbols"
-debug-assertions = false
-panic = "abort"
-codegen-units = 1
-lto = true
-
-[profile.release-with-logs]
-inherits = "release"
-debug-assertions = true
-```
-
-En este proyecto necesitaremos crear 3 archivos:
-
-- `src/lib.rs` - Aquí es donde escribiremos nuestra lógica de contrato inteligente de vault.
-- `src/test.rs` - Aquí es donde escribiremos nuestras pruebas.
-- `src/token.rs` - Este archivo hereda el contrato de token que importamos anteriormente. También es donde escribiremos nuestra lógica de creación de tokens.
-
-Para interactuar con el contrato de token, utilizaremos una interfaz incorporada que puedes encontrar en la pestaña `token_interface.rs`. Esta interfaz incluye las funciones `initialize` y `mint` que utilizaremos para crear y acuñar tokens para usar en nuestro contrato de vault. Si quieres ver el código completo del contrato de token, puedes verlo [aquí](https://github.com/stellar/soroban-examples/tree/main/token/src).
-
-<Tabs>
-<TabItem value="lib.rs" label="src/lib.rs">
-
-```rust
-#![no_std]
-
-mod test;
-mod token;
-
-use soroban_sdk::{
-    contract, contractimpl, contractmeta, Address, BytesN, ConversionError, Env, IntoVal,
-    TryFromVal, Val,
-};
-use token::create_contract;
-
-#[derive(Clone, Copy)]
-#[repr(u32)]
-pub enum DataKey {
-    Token = 0,
-    TokenShare = 1,
-    TotalShares = 2,
-    Reserve = 3,
-}
-
-impl TryFromVal<Env, DataKey> for Val {
-    type Error = ConversionError;
-
-    fn try_from_val(_env: &Env, v: &DataKey) -> Result<Self, Self::Error> {
-        Ok((*v as u32).into())
-    }
-}
-
-fn get_token(e: &Env) -> Address {
-    e.storage().instance().get(&DataKey::Token).unwrap()
-}
-
-fn get_token_share(e: &Env) -> Address {
-    e.storage().instance().get(&DataKey::TokenShare).unwrap()
-}
-
-fn get_total_shares(e: &Env) -> i128 {
-    e.storage().instance().get(&DataKey::TotalShares).unwrap()
-}
-
-fn get_reserve(e: &Env) -> i128 {
-    e.storage().instance().get(&DataKey::Reserve).unwrap()
-}
-
-fn get_balance(e: &Env, contract: Address) -> i128 {
-    token::Client::new(e, &contract).balance(&e.current_contract_address())
-}
-
-fn get_token_balance(e: &Env) -> i128 {
-    get_balance(e, get_token(e))
-}
-
-fn get_balance_shares(e: &Env) -> i128 {
-    get_balance(e, get_token_share(e))
-}
-
-fn put_token(e: &Env, contract: Address) {
-    e.storage().instance().set(&DataKey::Token, &contract);
-}
-
-fn put_token_share(e: &Env, contract: Address) {
-    e.storage().instance().set(&DataKey::TokenShare, &contract);
-}
-
-fn put_total_shares(e: &Env, amount: i128) {
-    e.storage().instance().set(&DataKey::TotalShares, &amount)
-}
-
-fn put_reserve(e: &Env, amount: i128) {
-    e.storage().instance().set(&DataKey::Reserve, &amount)
-}
-
-fn burn_shares(e: &Env, amount: i128) {
-    let total = get_total_shares(e);
-    let share_contract_id = get_token_share(e);
-
-    token::Client::new(e, &share_contract_id).burn(&e.current_contract_address(), &amount);
-    put_total_shares(e, total - amount);
-}
-
-fn mint_shares(e: &Env, to: Address, amount: i128) {
-    let total = get_total_shares(e);
-    let share_contract_id = get_token_share(e);
-
-    token::Client::new(e, &share_contract_id).mint(&to, &amount);
-
-    put_total_shares(e, total + amount);
-}
-
-// Metadata that is added on to the Wasm custom section
-contractmeta!(
-    key = "Description",
-    val = "A Vault with a 1% return on investment per deposit."
-);
-
-pub trait VaultTrait {
-    // Sets the token contract addresses for this vault
-    fn initialize(e: Env, token_wasm_hash: BytesN<32>, token: Address);
-
-    // Returns the token contract address for the vault share token
-    fn share_id(e: Env) -> Address;
-
-    // Deposits token. Also mints vault shares for the `from` Identifier. The amount minted
-    // is determined based on the difference between the reserves stored by this contract, and
-    // the actual balance of token for this contract.
-    fn deposit(e: Env, from: Address, amount: i128);
-
-    // transfers `amount` of vault share tokens to this contract, burns all pools share tokens in this contracts, and sends the
-    // corresponding amount of token to `to`.
-    // Returns amount of token withdrawn
-    fn withdraw(e: Env, to: Address, amount: i128) -> i128;
-
-    fn get_rsrvs(e: Env) -> i128;
-}
-#[contract]
-struct Vault;
-
-#[contractimpl]
-impl VaultTrait for Vault {
-    fn initialize(e: Env, token_wasm_hash: BytesN<32>, token: Address) {
-        let share_contract_id = create_contract(&e, token_wasm_hash, &token);
-        token::Client::new(&e, &share_contract_id).initialize(
-            &e.current_contract_address(),
-            &7u32,
-            &"Vault Share Token".into_val(&e),
-            &"VST".into_val(&e),
-        );
-
-        put_token(&e, token);
-        put_token_share(&e, share_contract_id.try_into().unwrap());
-        put_total_shares(&e, 0);
-        put_reserve(&e, 0);
-    }
-
-    fn share_id(e: Env) -> Address {
-        get_token_share(&e)
-    }
-
-    fn deposit(e: Env, from: Address, amount: i128) {
-        // Depositor needs to authorize the deposit
-        from.require_auth();
-
-        let token_client = token::Client::new(&e, &get_token(&e));
-
-        token_client.transfer(&from, &e.current_contract_address(), &amount);
-
-        let balance = get_token_balance(&e);
-
-        mint_shares(&e, from, amount);
-        put_reserve(&e, balance);
-    }
-
-    fn withdraw(e: Env, to: Address, amount: i128) -> i128 {
-        to.require_auth();
-
-        // First transfer the vault shares that need to be redeemed
-        let share_token_client = token::Client::new(&e, &get_token_share(&e));
-        share_token_client.transfer(&to, &e.current_contract_address(), &amount);
-
-        let token_client = token::Client::new(&e, &get_token(&e));
-        token_client.transfer(
-            &e.current_contract_address(),
-            &to,
-            &(&amount + (&amount / &100)),
-        );
-
-        let balance = get_token_balance(&e);
-        let balance_shares = get_balance_shares(&e);
-
-        burn_shares(&e, balance_shares);
-        put_reserve(&e, balance - amount);
-
-        amount
-    }
-
-    fn get_rsrvs(e: Env) -> i128 {
-        get_reserve(&e)
-    }
-}
-```
-
-</TabItem>
-<TabItem value="test.rs" label="src/test.rs" default>
-
-```rust
-#![cfg(test)]
-extern crate std;
-
-use crate::{token, VaultClient};
-
-use soroban_sdk::{
-    symbol_short,
-    testutils::{Address as _, AuthorizedFunction, AuthorizedInvocation},
-    Address, BytesN, Env, IntoVal,
-};
-
-fn create_token_contract<'a>(e: &Env, admin: &Address) -> token::Client<'a> {
-    token::Client::new(e, &e.register_stellar_asset_contract_v2(admin.clone()).address())
-}
-
-fn create_vault_contract<'a>(
-    e: &Env,
-    token_wasm_hash: &BytesN<32>,
-    token: &Address,
-) -> VaultClient<'a> {
-    let vault = VaultClient::new(e, &e.register(crate::Vault {}, ()));
-    vault.initialize(token_wasm_hash, token);
-    vault
-}
-
-fn install_token_wasm(e: &Env) -> BytesN<32> {
-    soroban_sdk::contractimport!(file = "./soroban_token_contract.wasm");
-    e.deployer().upload_contract_wasm(WASM)
-}
-
-#[test]
-fn test() {
-    let e = Env::default();
-    e.mock_all_auths();
-
-    let admin1 = Address::random(&e);
-
-    let token = create_token_contract(&e, &admin1);
-
-    let user1 = Address::random(&e);
-
-    let vault = create_vault_contract(&e, &install_token_wasm(&e), &token.address);
-
-    let contract_share = token::Client::new(&e, &vault.share_id());
-
-    let token_share = token::Client::new(&e, &contract_share.address);
-
-    token.mint(&user1, &200);
-    assert_eq!(token.balance(&user1), 200);
-    token.mint(&vault.address, &100);
-    assert_eq!(token.balance(&vault.address), 100);
-
-    vault.deposit(&user1, &100);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    vault.address.clone(),
-                    symbol_short!("deposit"),
-                    (&user1, 100_i128).into_val(&e)
-                )),
-                sub_invocations: std::vec![AuthorizedInvocation {
-                    function: AuthorizedFunction::Contract((
-                        token.address.clone(),
-                        symbol_short!("transfer"),
-                        (&user1, &vault.address, 100_i128).into_val(&e)
-                    )),
-                    sub_invocations: std::vec![]
-                }]
-            }
-        )]
-    );
-
-    assert_eq!(token_share.balance(&user1), 100);
-    assert_eq!(token_share.balance(&vault.address), 0);
-    assert_eq!(token.balance(&user1), 100);
-    assert_eq!(token.balance(&vault.address), 200);
-
-    e.budget().reset_unlimited();
-    vault.withdraw(&user1, &100);
-    assert_eq!(
-        e.auths(),
-        std::vec![(
-            user1.clone(),
-            AuthorizedInvocation {
-                function: AuthorizedFunction::Contract((
-                    vault.address.clone(),
-                    symbol_short!("withdraw"),
-                    (&user1, 100_i128).into_val(&e)
-                )),
-                sub_invocations: std::vec![AuthorizedInvocation {
-                    function: AuthorizedFunction::Contract((
-                        token_share.address.clone(),
-                        symbol_short!("transfer"),
-                        (&user1, &vault.address, 100_i128).into_val(&e)
-                    )),
-                    sub_invocations: std::vec![]
-                }]
-            }
-        )]
-    );
-    assert_eq!(token.balance(&user1), 201);
-    assert_eq!(token_share.balance(&user1), 0);
-    assert_eq!(token.balance(&vault.address), 99);
-    assert_eq!(token_share.balance(&vault.address), 0);
-}
-```
-
-</TabItem>
-
-<TabItem value="token.rs" label="src/token.rs">
-
-```rust
-#![allow(unused)]
-use soroban_sdk::{xdr::ToXdr, Address, Bytes, BytesN, Env};
-
-soroban_sdk::contractimport!(file = "./soroban_token_contract.wasm");
-
-pub fn create_contract(e: &Env, token_wasm_hash: BytesN<32>, token: &Address) -> Address {
-    let mut salt = Bytes::new(e);
-    salt.append(&token.to_xdr(e));
-    let salt = e.crypto().sha256(&salt);
-    e.deployer()
-        .with_current_contract(salt)
-        .deploy(token_wasm_hash)
-}
-```
-
-</TabItem>
-
-<TabItem value="token_interface.rs" label="src/token_interface.rs">
-
-```rust
-//! This contract demonstrates a sample implementation of the Soroban token
-//! interface.
-use crate::admin::{has_administrator, read_administrator, write_administrator};
-use crate::allowance::{read_allowance, spend_allowance, write_allowance};
-use crate::balance::{is_authorized, write_authorization};
-use crate::balance::{read_balance, receive_balance, spend_balance};
-use crate::event;
-use crate::metadata::{read_decimal, read_name, read_symbol, write_metadata};
-use crate::storage_types::INSTANCE_TTL_EXTEND_AMOUNT;
-use soroban_sdk::{contract, contractimpl, Address, Env, String};
-use soroban_token_sdk::TokenMetadata;
-
-pub trait TokenTrait {
-    fn initialize(e: Env, admin: Address, decimal: u32, name: String, symbol: String);
-
-    fn allowance(e: Env, from: Address, spender: Address) -> i128;
-
-    fn approve(e: Env, from: Address, spender: Address, amount: i128, expiration_ledger: u32);
-
-    fn balance(e: Env, id: Address) -> i128;
-
-    fn spendable_balance(e: Env, id: Address) -> i128;
-
-    fn authorized(e: Env, id: Address) -> bool;
-
-    fn transfer(e: Env, from: Address, to: Address, amount: i128);
-
-    fn transfer_from(e: Env, spender: Address, from: Address, to: Address, amount: i128);
-
-    fn burn(e: Env, from: Address, amount: i128);
-
-    fn burn_from(e: Env, spender: Address, from: Address, amount: i128);
-
-    fn clawback(e: Env, from: Address, amount: i128);
-
-    fn set_authorized(e: Env, id: Address, authorize: bool);
-
-    fn mint(e: Env, to: Address, amount: i128);
-
-    fn set_admin(e: Env, new_admin: Address);
-
-    fn decimals(e: Env) -> u32;
-
-    fn name(e: Env) -> String;
-
-    fn symbol(e: Env) -> String;
-}
-
-fn check_nonnegative_amount(amount: i128) {
-    if amount < 0 {
-        panic!("negative amount is not allowed: {}", amount)
-    }
-}
-
-#[contract]
-pub struct Token;
-
-#[contractimpl]
-impl TokenTrait for Token {
-    fn initialize(e: Env, admin: Address, decimal: u32, name: String, symbol: String) {
-        if has_administrator(&e) {
-            panic!("already initialized")
-        }
-        write_administrator(&e, &admin);
-        if decimal > 18 {
-            panic!("Decimal must not be greater than 18");
-        }
-
-        write_metadata(
-            &e,
-            TokenMetadata {
-                decimal,
-                name,
-                symbol,
-            },
-        )
-    }
-
-    fn allowance(e: Env, from: Address, spender: Address) -> i128 {
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-        read_allowance(&e, from, spender).amount
-    }
-
-    fn approve(e: Env, from: Address, spender: Address, amount: i128, expiration_ledger: u32) {
-        from.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        write_allowance(&e, from.clone(), spender.clone(), amount, expiration_ledger);
-        event::approve(&e, from, spender, amount, expiration_ledger);
-    }
-
-    fn balance(e: Env, id: Address) -> i128 {
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-        read_balance(&e, id)
-    }
-
-    fn spendable_balance(e: Env, id: Address) -> i128 {
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-        read_balance(&e, id)
-    }
-
-    fn authorized(e: Env, id: Address) -> bool {
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-        is_authorized(&e, id)
-    }
-
-    fn transfer(e: Env, from: Address, to: Address, amount: i128) {
-        from.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        spend_balance(&e, from.clone(), amount);
-        receive_balance(&e, to.clone(), amount);
-        event::transfer(&e, from, to, amount);
-    }
-
-    fn transfer_from(e: Env, spender: Address, from: Address, to: Address, amount: i128) {
-        spender.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        spend_allowance(&e, from.clone(), spender, amount);
-        spend_balance(&e, from.clone(), amount);
-        receive_balance(&e, to.clone(), amount);
-        event::transfer(&e, from, to, amount)
-    }
-
-    fn burn(e: Env, from: Address, amount: i128) {
-        from.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        spend_balance(&e, from.clone(), amount);
-        event::burn(&e, from, amount);
-    }
-
-    fn burn_from(e: Env, spender: Address, from: Address, amount: i128) {
-        spender.require_auth();
-
-        check_nonnegative_amount(amount);
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        spend_allowance(&e, from.clone(), spender, amount);
-        spend_balance(&e, from.clone(), amount);
-        event::burn(&e, from, amount)
-    }
-
-    fn clawback(e: Env, from: Address, amount: i128) {
-        check_nonnegative_amount(amount);
-        let admin = read_administrator(&e);
-        admin.require_auth();
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        spend_balance(&e, from.clone(), amount);
-        event::clawback(&e, admin, from, amount);
-    }
-
-    fn set_authorized(e: Env, id: Address, authorize: bool) {
-        let admin = read_administrator(&e);
-        admin.require_auth();
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        write_authorization(&e, id.clone(), authorize);
-        event::set_authorized(&e, admin, id, authorize);
-    }
-
-    fn mint(e: Env, to: Address, amount: i128) {
-        check_nonnegative_amount(amount);
-        let admin = read_administrator(&e);
-        admin.require_auth();
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        receive_balance(&e, to.clone(), amount);
-        event::mint(&e, admin, to, amount);
-    }
-
-    fn set_admin(e: Env, new_admin: Address) {
-        let admin = read_administrator(&e);
-        admin.require_auth();
-
-        e.storage().instance().extend_ttl(INSTANCE_TTL_EXTEND_AMOUNT);
-
-        write_administrator(&e, &new_admin);
-        event::set_admin(&e, admin, new_admin);
-    }
-
-    fn decimals(e: Env) -> u32 {
-        read_decimal(&e)
-    }
-
-    fn name(e: Env) -> String {
-        read_name(&e)
-    }
-
-    fn symbol(e: Env) -> String {
-        read_symbol(&e)
-    }
-}
-```
-
-</TabItem>
-</Tabs>
-
-Now that we've added these files to our project, let's break down what happens in the `lib.rs` file above and discover how "yield" is generated from our vault contract
-
-Primero, echemos un vistazo a lo que sucede cuando un usuario deposita tokens en el contrato de vault.
-
-```rust
-fn deposit(e: Env, from: Address, amount: i128) {
-    // Depositor needs to authorize the deposit
-    from.require_auth();
-
-    let token = token::Client::new(&e, &get_token(&e));
-
-    token.transfer(&from, &e.current_contract_address(), &amount);
-
-    // Now calculate how many new vault shares to mint
-    let balance = get_token_balance(&e);
-
-    let shares = amount;
-
-    mint_shares(&e, from, shares);
-    put_reserve(&e, balance + shares);
-}
-```
-
-- La función `deposit` es llamada por el depositante para depositar tokens en el contrato de vault.
-- El método `transfer` de la instancia `token_client` transfiere tokens del depositante al contrato de vault.
-- El saldo actual de tokens y el total de acciones emitidas por el contrato de vault se obtienen utilizando las funciones `get_token_balance` y `get_total_shares`, respectivamente.
-- `mint_shares` se llama para emitir nuevas acciones al depositante y actualiza el total de acciones emitidas por el contrato de vault.
-- `put_reserve` almacena el saldo actual de tokens en una ubicación reservada.
-
-Si el usuario llamara al método `deposit` con 100 tokens, sucedería lo siguiente:
-
-- 100 tokens se transferirían del depositante al contrato de vault.
-- El saldo actual de tokens se almacenaría en una ubicación reservada.
-- El total de acciones emitidas por el contrato de vault se actualizaría a 100.
-- 100 acciones se emitirían al depositante.
-
-Ahora veamos qué sucede cuando un usuario retira tokens del vault.
-
-```rust
-fn withdraw(e: Env, to: Address, amount: i128) -> i128 {
-    to.require_auth();
-
-    // First transfer the vault shares that need to be redeemed
-    let share_token_client = token::Client::new(&e, &get_token_share(&e));
-    share_token_client.transfer(&to, &e.current_contract_address(), &amount);
-
-    // Calculate total amount including yield
-    let total_amount = amount + (amount / 100);
-
-    let token_client = token::Client::new(&e, &get_token(&e));
-    token_client.transfer(&e.current_contract_address(), &to, &total_amount);
-
-    let balance = get_token_balance(&e);
-    let balance_shares = get_balance_shares(&e);
-
-    burn_shares(&e, balance_shares);
-    put_reserve(&e, balance); // Update the reserve with the actual balance
-
-    total_amount
-}
-```
-
-- La función `withdraw` es llamada por el retirador para retirar tokens del contrato de vault.
-- El método `transfer` de la instancia `share_token_client` transfiere acciones del retirador al contrato de vault.
-- El método `transfer_token` de la instancia `token_client` transfiere tokens del contrato de vault al retirador.
-- `burn_shares` se llama para quemar las acciones que fueron transferidas al contrato de vault.
-- `put_reserve` almacena el saldo actual de tokens en una ubicación reservada.
-- Devuelve el total de tokens retirados por el usuario.
-
-> _Nota_ : En la función de retirada, notarás que la cantidad de transferencia se define como `&(&amount + (&amount / &100))`. Este es un cálculo de rendimiento simple que asume que el rendimiento es el 1% de la cantidad que se está retirando. Sin embargo, es importante notar que este es un enfoque muy simplista y puede no ser adecuado para sistemas de producción. En realidad, los cálculos de rendimiento son más complejos e involucran varios factores como condiciones de mercado, gestión de riesgos y tarifas.
-
-Si el usuario llamara al método `withdraw` con 100 acciones, sucedería lo siguiente:
-
-- 100 acciones se transferirían del retirador al contrato de vault.
-- El saldo actual de tokens se almacenaría en una ubicación reservada.
-- 100 acciones se quemarían.
-- 100 + (100/100) tokens se transferirían del contrato de vault al retirador.
-
-### Testing
-
-Para probar el contrato de vault, podemos simplemente ejecutar el siguiente comando en nuestra terminal desde el directorio de nuestro contrato de vault:
-
-```bash
-#cd vault
-cargo test
-```
-
-Esto ejecutará las pruebas que hemos escrito en el archivo `src/test.rs`.
-
-```bash
-running 1 test
-test test::test ... ok
-```
-
-### Despliegue e Interacción del Contrato de Vault
-
-Ahora que tenemos un contrato de vault operativo, podemos desplegarlo en una red e interactuar con él.
-
-Esta sección requiere que tengas un Keypair financiado para usar con el Testnet de Stellar. Puedes crear y financiar uno usando el [Stellar Lab](https://lab.stellar.org/account/create).
-
-A continuación, encontrarás una serie de comandos que te ayudarán a construir, desplegar e interactuar con los contratos de vault y de token. Puedes usarlos para seguir mientras pasamos por el proceso de construir, desplegar e interactuar con los contratos. Puede serte útil mantener estos comandos en un directorio `scripts` en tu proyecto. De esta manera, puedes ejecutarlos fácilmente desde tu terminal.
-
-> _Nota_ : Si decides usar scripts, asegúrate de verificar tus rutas de importación.
-
-<Tabs>
-<TabItem value="build" label="build.sh">
-
-```bash
-stellar contract build
-```
-
-</TabItem>
-
-<TabItem value="deploy token" label="deploy_token.sh">
-
-```bash
-stellar contract deploy \
-    --wasm soroban_token_contract.wasm \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015'
-```
-
-</TabItem>
-
-<TabItem value="initialize token" label="initialize_token.sh">
-
-```bash
-stellar contract invoke \
-    --id <TOKEN_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    initialize \
-    --admin <USER_ADDRESS> \
-    --decimal 18 \
-    --name <TOKEN_NAME> \
-    --symbol <TOKEN_SYMBOL>
-```
-
-</TabItem>
-
-<TabItem value="mint" label="mint.sh">
-
-```bash
-stellar contract invoke \
-    --id <TOKEN_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    mint \
-    --to <USER_OR_VAULT_ADDRESS> \
-    --amount 100
-```
-
-</TabItem>
-
-<TabItem value="balance" label="balance.sh">
-
-```bash
-stellar contract invoke \
-    --id <TOKEN_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-        balance \
-    --id <USER_OR_VAULT_ADDRESS>
-```
-
-</TabItem>
-
-<TabItem value="insatll wasm" label="install.sh">
-
-```bash
-stellar contract install \
-    --wasm soroban_token_contract.wasm \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015'
-```
-
-</TabItem>
-
-<TabItem value="deploy vault" label="deploy_vault.sh">
-
-```bash
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/vault.wasm \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015'
-```
-
-</TabItem>
-
-<TabItem value="initialize vault" label="initialize_vault.sh">
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    initialize \
-    --token_wasm_hash 73593275ee3bcacc2aef8d641a1d5108618064bdfff84a826576b8caff395add \
-    --token <TOKEN_CONTRACT_ADDRESS>
-```
-
-</TabItem>
-
-<TabItem value="get share" label="share_id.sh">
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    share_id
-```
-
-</TabItem>
-
-<TabItem value="deposit" label="deposit.sh">
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    deposit \
-    --from <USER_ADDRESS> \
-    --amount 100
-```
-
-</TabItem>
-
-<TabItem value="reserve" label="get_rsrv.sh">
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    get_rsrvs
-```
-
-</TabItem>
-
-<TabItem value="withdraw" label="withdraw.sh">
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    withdraw \
-    --to <USER_ADDRESS> \
-    --amount 100
-```
-
-</TabItem>
-
-</Tabs>
-
-Primero, necesitamos construir el contrato de vault. Podemos hacer esto ejecutando el script `build.sh` desde nuestro directorio de vault.
-
-```bash
-##cd vault
-stellar contract build
-```
-
-A continuación, necesitamos desplegar el contrato de token. Podemos hacer esto ejecutando el script `deploy_token.sh`.
-
-```bash
-stellar contract deploy \
-    --wasm soroban_token_contract.wasm \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015'
-```
-
-Deberíamos recibir una salida con el ID del contrato de token. Necesitaremos este ID para el siguiente paso.
-
-```bash
-CBYMG7OPIT67AG4S2FZU7LAYCXUSXEHRGHLDE6H26VCVWNOV7QUQTGNU
-```
-
-A continuación, necesitamos inicializar el contrato de token. Podemos hacer esto ejecutando el script `initialize_token.sh`.
-
-```bash
-stellar contract invoke \
-    --id <TOKEN_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    initialize \
-    --admin <USER_ADDRESS> \
-    --decimal 18 \
-    --name <TOKEN_NAME> \
-    --symbol <TOKEN_SYMBOL>
-```
-
-A continuación, necesitamos desplegar el contrato de vault. Podemos hacer esto ejecutando el script `deploy_vault.sh`.
-
-```bash
-stellar contract deploy \
-    --wasm target/wasm32v1-none/release/vault.wasm \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015'
-```
-
-Deberíamos recibir una salida con el ID del contrato del vault. Necesitaremos este ID para el siguiente paso.
-
-```bash
-CBBPLE6TGYOMO5HUF2AMYLSYYXM2VYZVAVYI5QCCM5OCFRZPBE2XA53F
-```
-
-Ahora necesitamos obtener el hash Wasm del contrato del token. Podemos hacer esto ejecutando el script `get_token_wasm_hash.sh`.
-
-```bash
-stellar contract install \
-    --wasm soroban_token_contract.wasm \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015'
-```
-
-Deberíamos recibir el hash Wasm del contrato del token.
-
-```bash
-6b7e4bfbf47157a12e24e564efc1f9ac237e7ae6d7056b6c2ab47178b9e7a510
-```
-
-Ahora necesitamos inicializar el contrato del vault. Podemos hacer esto ejecutando el script `initialize_vault.sh` y pasando el ID del contrato del token y el hash Wasm del contrato del token.
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    initialize \
-    --token_wasm_hash 6b7e4bfbf47157a12e24e564efc1f9ac237e7ae6d7056b6c2ab47178b9e7a510 \
-    --token <TOKEN_CONTRACT_ADDRESS>
-```
-
-Después de recibir que la transacción ha sido enviada, mintamos algunos tokens a **ambas** nuestras cuentas de usuario y direcciones del contrato del vault. Podemos hacer esto ejecutando el script `mint.sh`.
-
-```bash
-stellar contract invoke \
-    --id <TOKEN_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    mint \
-    --to <USER_OR_VAULT_ADDRESS> \
-    --amount 100
-```
-
-Después de enviar la transacción, podemos verificar el saldo de la cuenta. Podemos hacer esto ejecutando el script `balance.sh`.
-
-```bash
-stellar contract invoke \
-    --id <TOKEN_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-        balance \
-    --id <USER_ADDRESS>
-```
-
-Deberíamos recibir una salida con el saldo de la cuenta.
-
-```bash
-100
-```
-
-Ahora podemos depositar algunos tokens en nuestro vault. Podemos hacer esto ejecutando el script `deposit.sh`.
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <ACCOUNT_SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    deposit \
-    --from <USER_ADDRESS> \
-    --amount 100
-```
-
-Después de enviar la transacción, podemos verificar las reservas del vault. Podemos hacer esto ejecutando el script `reserves.sh`.
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    get_rsrvs
-```
-
-Deberíamos recibir una salida con las reservas del vault.
-
-```bash
-"200"
-```
-
-100 de la depósito y 100 de la mint.
-
-Ahora podemos retirar algunos tokens del vault. Podemos hacer esto ejecutando el script `withdraw.sh`.
-
-```bash
-stellar contract invoke \
-    --id <VAULT_CONTRACT_ID> \
-    --source-account <SECRET_KEY> \
-    --rpc-url https://soroban-testnet.stellar.org:443 \
-    --network-passphrase 'Test SDF Network ; September 2015' \
-    -- \
-    withdraw \
-    --to <USER_ADDRESS> \
-    --amount 100
-```
-
-Deberíamos recibir una salida con el monto de la retirada.
-
-```bash
-"100"
-```
-
-Ahora es un buen momento para verificar nuestro saldo de cuenta de nuevo. Podemos hacer esto ejecutando el script `balance.sh`.
-
-Deberíamos ver que nuestro saldo ha aumentado el monto que retiramos más el rendimiento (monto/100) o %1 de nuestro monto de retiro.
-
-```bash
-101
-```
-
-Y finalmente, podemos verificar las reservas del vault de nuevo. Podemos hacer esto ejecutando el script `get_rsrv.sh`.
-
-Deberíamos ver que las reservas del vault han disminuido por el monto que retiramos + rendimiento.
-
-```bash
-"99"
-```
-
-¡Y ahí lo tienes! ¡Has desplegado e interactuado con éxito con el contrato del vault!
-
-Es importante notar que este no es un contrato listo para producción y solo está destinado a demostrar las capacidades de la plataforma de contratos inteligentes Soroban. ¡Esperamos ver contratos de rendimiento mucho más complejos desplegados con Soroban en el futuro, y esperamos que tú seas parte de ello!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-and-rust-advanced-concepts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-and-rust-advanced-concepts.mdx
deleted file mode 100644
index 661bcb9061..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-and-rust-advanced-concepts.mdx
+++ /dev/null
@@ -1,907 +0,0 @@
----
-sidebar_position: 2
-title: Advanced Smart Contract Concepts with Solidity and Rust
-description: Learn advanced Solidity and Rust concepts and write safe and efficient smart contracts.
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-# Advanced Smart Contract Concepts with Solidity and Rust
-
-In this tutorial, we will cover advanced Solidity and Rust concepts such as inheritance, interfaces, libraries, and modifiers. Additionally, we will learn how to write safe and efficient Rust code for smart contracts. Finally, we will learn how to convert common Solidity concepts to Rust.
-
-## Table of Contents
-
-1. [Advanced Solidity Concepts](#advanced-solidity-concepts)
-2. [Advanced Rust Concepts](#advanced-rust-concepts)
-3. [Writing Safe and Efficient Rust Code for Smart Contracts](#writing-safe-and-efficient-rust-code-for-smart-contracts)
-4. [Solidity to Soroban: Common Concepts and Best Practices](#solidity-to-soroban-common-concepts-and-best-practices)
-
-## Advanced Solidity Concepts
-
-### Inheritance
-
-En Solidity, los contratos inteligentes pueden heredar propiedades y funciones de otros contratos. Esto se logra utilizando la palabra clave `is`.
-
-Aquí hay un ejemplo de un contrato padre que define una función llamada `messageFromParent` que devuelve una cadena:
-
-```solidity
-contract Parent {
-    function messageFromParent() public pure returns (string memory) {
-        return "Hello from Parent";
-    }
-}
-contract Child is Parent {
-    function messageFromChild(string memory newMessage) public pure returns (string memory) {
-        string memory messageFromParent = messageFromParent();
-        return string(abi.encodePacked(messageFromParent,', ', newMessage));
-    }
-}
-```
-
-En este ejemplo, el contrato `Child` hereda la función `messageFromParent` del contrato `Parent`. El contrato `Child` puede entonces llamar a la función `messageFromParent` directamente.
-
-### Interfaces
-
-Las interfaces son similares a los contratos, pero no pueden tener implementaciones de funciones. Solo contienen firmas de funciones. Los contratos pueden implementar interfaces utilizando la palabra clave `is`, similar a la herencia.
-
-Aquí hay un ejemplo de una interfaz que define una función llamada `doSomething` que retorna un `uint256`:
-
-```solidity
-interface SomeInterface {
-    function doSomething() external returns (uint256);
-}
-
-contract SomeContract is SomeInterface {
-    uint256 private counter;
-
-    function doSomething() external override returns (uint256) {
-        counter += 1;
-        return counter;
-    }
-}
-```
-
-En este ejemplo, el contrato `SomeContract` implementa la interfaz `SomeInterface`. Su implementación devuelve un `u256` que se incrementa cada vez que se llama a la función `doSomething`.
-
-### Bibliotecas
-
-Las bibliotecas son similares a los contratos, pero no pueden tener variables de estado. Se utilizan para almacenar código reutilizable que puede ser utilizado por otros contratos. Las bibliotecas se implementan una vez y pueden ser usadas por múltiples contratos. Se definen utilizando la palabra clave `library`. Se invocan utilizando la palabra clave `using`.
-
-```solidity
-library SafeMath {
-    function add(uint256 a, uint256 b) internal pure returns (uint256) {
-        uint256 c = a + b;
-        require(c >= a, "Addition overflow");
-
-        return c;
-    }
-}
-
-contract MyContract {
-    using SafeMath for uint256;
-
-    uint256 public value;
-
-    function increment(uint256 amount) public {
-        value = value.add(amount);
-    }
-}
-```
-
-En este ejemplo, la biblioteca `SafeMath` se utiliza en la función `increment`. La función `increment` utiliza la función `add` de la biblioteca `SafeMath` para incrementar la variable `value`.
-
-### Modificadores
-
-Los modificadores se utilizan para cambiar el comportamiento de las funciones de manera declarativa. Se definen utilizando la palabra clave `modifier`. Los modificadores pueden ser utilizados para realizar chequeos comunes tales como validar entradas, verificar permisos, y más.
-
-```solidity
-contract Ownable {
-    address public owner;
-
-    constructor() {
-        owner = msg.sender;
-    }
-
-    modifier onlyOwner() {
-        require(msg.sender == owner, "Caller is not the owner");
-        _;
-    }
-}
-
-contract MyContract is Ownable {
-    function doSomething() public onlyOwner {
-        // This function can only be called by the owner of the contract
-    }
-}
-```
-
-En este ejemplo, el modificador `onlyOwner` se utiliza para restringir el acceso a la función `doSomething`. La función `doSomething` solo puede ser llamada por el `owner` del contrato que fue definido durante la implementación como `msg.sender`.
-
-## Conceptos Avanzados de Rust
-
-### Crates
-
-Un crate en Rust es una colección de programas precompilados, scripts o rutinas que pueden ser fácilmente reutilizados por programadores cuando escriben código. Esto les permite evitar reinventar la rueda al no tener que implementar la misma lógica o programa múltiples veces. Hay dos tipos de crates en Rust: [Crates Binarios y Crates de Biblioteca](https://doc.rust-lang.org/book/ch07-01-packages-and-crates.html).
-
-Los crates binarios son crates que pueden ser ejecutados como programas independientes. Los crates de biblioteca son crates que están destinados a ser utilizados por otros programas. Los crates de biblioteca pueden ser importados en otros programas usando la palabra clave `use`.
-
-Aquí hay un ejemplo de un flujo de trabajo que implementa la lógica de asignación (`alloc`) dentro de un contrato inteligente:
-
-Primero, un usuario incluiría el crate `alloc` en su archivo `Cargo.toml`:
-
-```toml
-[dependencies]
-soroban-sdk = { workspace = true, features = ["alloc"] }
-
-[dev_dependencies]
-soroban-sdk = { workspace = true, features = ["testutils", "alloc"] }
-```
-
-Luego, importaría el crate `alloc` en su contrato inteligente:
-
-```rust
-// Imports
-#![no_std]
-use soroban_sdk::{contractimpl, Env};
-
-extern crate alloc;
-
-#[contract]
-pub struct AllocContract;
-
-#[contractimpl]
-impl AllocContract {
-    /// Allocates a temporary vector holding values (0..count), then computes and returns their sum.
-    pub fn sum(_env: Env, count: u32) -> u32 {
-        let mut v1 = alloc::vec![];
-        (0..count).for_each(|i| v1.push(i));
-
-        let mut sum = 0;
-        for i in v1 {
-            sum += i;
-        }
-
-        sum
-    }
-}
-```
-
-En este ejemplo, el crate `alloc` es importado en el contrato inteligente usando la declaración `extern crate alloc;`. El crate `alloc` se utiliza para crear un vector temporal que contiene valores de 0 a `count`. Los valores en el vector son luego sumados y devueltos.
-
-Para más detalles sobre cómo usar el crate `alloc`, incluyendo un ejercicio práctico, visita el [contrato de ejemplo de alloc](../../../build/smart-contracts/example-contracts/alloc.mdx#how-it-works).
-
-#### Heredando Funcionalidad de Otros Crates
-
-Podemos ilustrar otro ejemplo de herencia al importar funcionalidad a un crate desde otros crates en el mismo proyecto en el siguiente ejemplo:
-
-A continuación se muestra una función del archivo [`event.rs`](https://github.com/stellar/soroban-examples/tree/main/events/src) de nuestro ejemplo [Token](https://github.com/stellar/soroban-examples/tree/main/token).
-
-```rust
-use soroban_sdk::{Address, Env, Symbol};
-...
-pub(crate) fn mint(e: &Env, admin: Address, to: Address, amount: i128) {
-    let topics = (symbol_short!("mint"), admin, to);
-    e.events().publish(topics, amount);
-}
-```
-
-Esta función publicará un evento de acuñación en la blockchain con la siguiente salida:
-
-```
-Emit event with topics = ["mint", admin: Address, to: Address], data = amount: i128
-```
-
-También utilizaremos una función de nuestro archivo [`admin.rs`](https://github.com/stellar/soroban-examples/blob/main/token/src/admin.rs).
-
-```rust
-// Metering: covered by components
-pub fn read_administrator(e: &Host) -> Result<Address, HostError> {
-    let key = DataKey::Admin;
-    let rv = e.get_contract_data(key.try_into_val(e)?)?;
-    Ok(rv.try_into_val(e)?)
-}
-```
-
-Esta función devuelve un objeto `Result` que contiene la dirección del administrador.
-
-Por último, implementaremos una función de nuestro archivo [`balance.rs`](https://github.com/stellar/soroban-examples/blob/main/token/src/balance.rs).
-
-```rust
-pub fn receive_balance(e: &Env, addr: Address, amount: i128) {
-    let balance = read_balance(e, addr.clone());
-    if !is_authorized(e, addr.clone()) {
-        panic!("can't receive when deauthorized");
-    }
-    write_balance(e, addr, balance + amount);
-}
-```
-
-Esta función escribe un monto en el saldo de una dirección.
-
-El `event.rs` es importado en el archivo [`contract.rs`](https://github.com/stellar/soroban-examples/blob/main/token/src/contract.rs) que contiene la lógica para nuestro contrato de token.
-
-```rust
-//contract.rs
-
-//imports
-use crate::event;
-use crate::admin::{read_administrator};
-use crate::balance::{receive_balance};
-
-// trait logic
-pub trait TokenTrait {
-fn mint(e: Env, to: Address, amount: i128);
-}
-
-// struct logic
-#[contract]
-pub struct Token;
-
-// impl logic
-
-#[contractimpl]
-impl TokenTrait for Token {
-fn mint(e: Env, to: Address, amount: i128) {
-        check_nonnegative_amount(amount);
-        let admin = read_administrator(&e);
-        admin.require_auth();
-        receive_balance(&e, to.clone(), amount);
-        event::mint(&e, admin, to, amount);
-    }
-}
-```
-
-Como puedes ver, los archivos `event.rs`, `admin.rs`, y `balance.rs` son importados en el archivo `contract.rs` usando la palabra clave `use`. Esto nos permite usar las funciones de esos archivos en la función `mint` de nuestro archivo `contract.rs`.
-
-#### Heredando Funcionalidad usando `contractimport!`
-
-El SDK de Soroban Rust proporciona un poderoso macro, [`contractimport`](https://docs.rs/soroban-sdk/latest/soroban_sdk/macro.contractimport.html), que permite a un usuario importar un contrato desde su archivo Wasm, generando un cliente, tipos y constantes que contienen el archivo del contrato.
-
-Aquí tienes un ejemplo de cómo usar la macro `contractimport` extraído del archivo token.rs de nuestro [ejemplo de Fondo de Liquidez](https://github.com/stellar/soroban-examples/blob/main/liquidity_pool):
-
-Primero, vemos que el archivo wasm del [ejemplo de token construído previamente](https://github.com/stellar/soroban-examples/blob/main/token) es importado en el archivo `token.rs` usando el macro `contractimport`:
-
-```rust
-//token.rs
-soroban_sdk::contractimport!(
-    file = "../token/target/wasm32v1-none/release/soroban_token_contract.wasm"
-);
-```
-
-Luego vemos que nuestro contrato de token es importado en nuestro archivo [`lib.rs`](https://github.com/stellar/soroban-examples/blob/main/liquidity_pool/src/lib.rs) y se genera un `Client` para que podamos acceder a la funcionalidad del contrato de token:
-
-```rust
-//lib.rs
-mod token;
-
-fn get_balance(e: &Env, contract_id: BytesN<32>) -> i128 {
-    token::Client::new(e, &contract_id).balance(&e.current_contract_address())
-}
-
-fn transfer(e: &Env, contract_id: BytesN<32>, to: Address, amount: i128) {
-    token::Client::new(e, &contract_id).transfer(&e.current_contract_address(), &to, &amount);
-}
-
-struct LiquidityPool;
-
-#[contractimpl]
-impl LiquidityPoolTrait for LiquidityPool {
-    let token_a_client = token::Client::new(&e, &get_token_a(&e));
-}
-```
-
-En el ejemplo anterior, usamos `contractimport` para interactuar con el archivo de token a través de un `Client` que fue generado para el módulo `token`. Este `Client` fue creado usando un trait de contrato que coincide con la interfaz del contrato, una estructura ContractClient que contiene funciones para cada función en el contrato, y tipos para todos los tipos de contrato definidos en el contrato.
-
-#### Una Nota sobre Herencia y Composición
-
-Aunque hemos estado usando el término "herencia" para ayudar a hacer la transición de Solidity más suave, aclaremos un aspecto importante de Rust: no soporta la herencia como la entendemos tradicionalmente. En su lugar, Rust practica la "composición", lo que significa que utiliza funciones de diferentes crates, que son similares a paquetes, de manera modular. Así que, cuando hablamos de `contractimport!`, en realidad estamos observando la composición en acción, no "herencia". Rust no fomenta la relación "es un" inherente en los lenguajes OOP. En su lugar, permite reutilizar y ensamblar código de manera efectiva a través de diferentes ámbitos. Esta es una verdad técnica que es importante entender; sin embargo, vale la pena señalar que este hecho no impacta el uso práctico de Soroban a lo largo de esta guía.
-
-### Módulos
-
-En Rust, los módulos consisten en un conjunto cohesivo de funciones relacionadas y tipos que a menudo están organizados juntos para una mejor organización y reutilización. Estos módulos pueden ser reutilizados en múltiples proyectos al publicarlos como crates.
-
-Aquí hay un ejemplo de un módulo que implementa la lógica de `SafeMath` con una función `add`:
-
-```rust
-#![no_std]
-
-mod safe_math
-
-// mod safe_math {
-//     pub fn add(a: u32, b: u32) -> Result<u32, &'static str> {
-//          a.checked_add(b).ok_or("Addition overflow")
-//      }
-// }
-
-
-// Imports
-use soroban_sdk::{contractimpl, Env};
-use safe_math::add;
-
-pub trait MathContract {
-    fn add(&self, env: Env, a: u32, b: u32) -> u32;
-}
-
-#[contract]
-pub struct Adder;
-
-impl MathContract for Adder {
-    fn add(&self, _env: Env, a: u32, b: u32) -> u32 {
-        add(a, b).unwrap()
-    }
-}
-
-#[contractimpl]
-impl Adder {}
-
-// test module
-#[cfg(test)]
-mod test;
-```
-
-Nota que usamos la función `checked_add` de la biblioteca estándar para asegurarnos de que la suma no se desborde. Esto es importante porque si la suma se desborda, podría llevar a un comportamiento inesperado en el contrato.
-
-Incluso cuando el código Rust es compilado con el flag `#![no_std]`, todavía es posible utilizar algunas características de la biblioteca estándar, como la función `checked_add`. Esto se debe a que Rust ofrece la opción de importar selectivamente módulos y funciones de la biblioteca estándar, lo que permite a los desarrolladores usar solo las características específicas que necesitan.
-
-### Traits
-
-Rust no tiene un sistema de modificadores incorporado como Solidity. Sin embargo, puedes lograr una funcionalidad similar usando `traits` y sus implementaciones.
-
-En el ejemplo a continuación, ilustraremos la herencia de traits usando el trait `Ownable`.
-
-```rust
-#![no_std]
-
-// Imports
-use soroban_sdk::{contracttype, Address};
-
-// Define the `Ownable` trait
-trait Ownable {
-    fn is_owner(&self, owner: &Address) -> bool;
-}
-
-// Implement the `Ownable` trait for the `OwnableContract` struct
-impl Ownable for OwnableContract {
-    fn is_owner(&self, owner: &Address) -> bool {
-        self.owner == *owner
-    }
-}
-
-// Define a modifier that requires the caller to be the owner of the contract
-fn only_owner(contract: &OwnableContract, owner: &Address) -> bool {
-    contract.is_owner(owner)
-}
-
-// Implement the contract for the `OwnableContract` struct
-#[contracttype]
-
-// Define the `OwnableContract` struct
-pub struct OwnableContract {
-    owner: Address,
-    number: u32,
-}
-
-impl OwnableContract {
-    // Define a public method that requires the caller to be the owner of the contract
-    pub fn change_number(&mut self, new_number: u32) {
-        if only_owner(self, &self.owner) {
-            self.number = new_number;
-        }
-    }
-}
-
-#[cfg(test)]
-mod test;
-```
-
-Aquí hay un desglose del código anterior:
-
-- Primero, definimos el trait `Ownable`, que define un único método llamado `is_owner`. Este método toma un `Address` como argumento y devuelve un valor booleano que indica si la dirección es o no el propietario del contrato.
-- A continuación, implementamos el trait `Ownable` para la estructura `OwnableContract`. Esto nos permite usar el método `is_owner` en instancias de la estructura `OwnableContract`.
-- Luego, definimos un "modificador" llamado `only_owner` que toma una instancia de la estructura `OwnableContract` y una `Address` como argumentos. Este "modificador" devuelve un valor booleano que indica si la dirección es o no el propietario del contrato.
-- Finalmente, implementamos el contrato para la estructura `OwnableContract`. Esto permite que solo el `owner` del contrato use el método `change_number` en instancias de la estructura `OwnableContract`.
-
-Es importante mencionar que el SDK de Soroban Rust viene con varios requisitos incorporados que los desarrolladores pueden usar, como el método [`require_auth`](https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Address.html#method.require_auth) provisto por la estructura `Address`.
-
-### Interfaces
-
-Las interfaces son una parte esencial de la construcción de contratos inteligentes con Soroban.
-
-Hay muchos tipos de interfaces de contratos inteligentes, y cada una tiene un propósito específico. Un ejemplo de una interfaz construida con Soroban es la [Interfaz de Token](../../../tokens/token-interface.mdx). Esta interfaz asegura que los tokens desplegados en Soroban sean interoperables con los tokens incorporados de Soroban (como el Contrato de Activos Stellar). La Interfaz de Token consiste en tres requerimientos de compatibilidad:
-
-- `function interface`
-- `authorization`
-- `events`
-
-Para más información sobre las interfaces de contratos inteligentes construidas con Soroban, incluyendo la Interfaz de Token, visita la [sección de tokens](../../../tokens/README.mdx) de la documentación.
-
-## Escribir Código Seguro y Eficiente en Rust para Contratos Inteligentes
-
-Al escribir código Rust para contratos inteligentes, es importante enfocarse en la seguridad y la eficiencia. Algunos consejos incluyen:
-
-- Usa el tipo [`Result`](https://doc.rust-lang.org/book/ch09-02-recoverable-errors-with-result.html) para manejar errores de una manera segura y predecible. En los contratos inteligentes, es importante evitar pánicos, ya que esto puede llevar a comportamientos impredecibles. En su lugar, `Result` puede ser utilizado para manejar errores y asegurar que el contrato se comporte como se espera.
-
-En el ejemplo a continuación, la función `add` regresa un tipo `Result`, que puede ser `Ok` o `Err`. Si la suma no desborda, la función devuelve `Ok`, de lo contrario, devuelve `Err`.
-
-```rust
-pub fn add(a: u32, b: u32) -> Result<u32, &'static str> {
-    a.checked_add(b).ok_or("Addition overflow")
-}
-```
-
-- Usa la familia de funciones `checked_`, como `checked_add`, `checked_sub`, etc., para realizar operaciones aritméticas de manera segura y eficiente. Estas funciones verifican si hay desbordamientos y subdesbordamientos y devuelven un error si ocurre uno.
-
-En el ejemplo a continuación, la función `add` utiliza la función `checked_add` para realizar la suma. Si la suma se desborda, la función devuelve un error.
-
-```rust
-pub fn add(a: u32, b: u32) -> u32 {
-    a.checked_add(b).expect("Addition overflow")
-}
-```
-
-- Usa `cargo` y `clippy` para exigir la calidad, el estilo y la eficiencia del código en Rust. `cargo` es el administrador de paquetes de Rust y proporciona una serie de herramientas para construir y probar el código Rust. `clippy` es un linter que puede ayudar a identificar problemas potenciales en el código, como variables no utilizadas o funciones que podrían ser optimizadas.
-
-Para usar clippy con cargo, primero necesitarás instalarlo. Puedes hacerlo ejecutando el siguiente comando en tu terminal:
-
-```bash
-cargo install clippy
-```
-
-Una vez que clippy esté instalado, puedes ejecutarlo ejecutando el siguiente comando en tu terminal:
-
-```bash
-cargo clippy
-```
-
-Esto ejecutará clippy en todo tu proyecto, revisando posibles problemas y proporcionando sugerencias para mejorar. Clippy mostrará cualquier problema que encuentre, junto con sugerencias sobre cómo corregirlos.
-
-- Usa `cargo` y `rustfmt` para exigir el estilo del código. `rustfmt` es una herramienta que puede formatear automáticamente el código Rust de acuerdo con la guía de estilo de Rust. Esto puede ayudar a asegurar que el código sea consistente y fácil de leer.
-
-Para usar rustfmt con cargo, primero necesitarás instalarlo. Puedes hacerlo ejecutando el siguiente comando en tu terminal:
-
-```bash
-cargo install rustfmt
-```
-
-Una vez que rustfmt esté instalado, puedes ejecutarlo ejecutando el siguiente comando en tu terminal:
-
-```bash
-cargo fmt
-```
-
-Antes:
-
-```rust
-fn main()
-{
-let x=5;
-if x==5 {
-println!("Hello, world!");
-}
-}
-```
-
-Después:
-
-```rust
-fn main() {
-    let x = 5;
-    if x == 5 {
-        println!("Hello, world!");
-    }
-}
-```
-
-## Solidity a Soroban: Conceptos Comunes y Prácticas Recomendadas
-
-En esta sección exploraremos conceptos clave de Solidity y proporcionaremos sus equivalentes en Soroban. Discutiremos los siguientes temas:
-
-- Propiedades del Mensaje
-- Manejo de Errores
-- Funcionalidad relacionada con Direcciones
-- Especificadores de visibilidad de funciones
-- Variables basadas en tiempo
-
-### Propiedades del Mensaje
-
-El SDK de Soroban Rust y Solidity proporcionan una serie de propiedades de mensaje que pueden ser utilizadas para acceder a información sobre la transacción actual. Estas propiedades incluyen:
-
-#### Solidity
-
-- `msg.sender`: La dirección de la cuenta que envió la transacción.
-- `msg.value`: La cantidad de Ether enviada con la transacción.
-- `msg.data`: Los datos enviados con la transacción.
-
-Here's a simple example of a smart contract that demonstrates the use of each
-
-```solidity
-pragma solidity ^0.8.0;
-
-contract SimpleContract {
-    address public sender;
-    uint public value;
-    bytes public data;
-
-    // Caller must send Ether and data to this function.
-    // This function will store the sender, value, and data.
-    function sendData(bytes calldata _data) external payable {
-        sender = msg.sender;
-        value = msg.value;
-        data = _data;
-    }
-}
-```
-
-Estas son parte de las variables globales de Solidity, que son accesibles desde cualquier función en el contrato.
-
-#### Soroban
-
-A diferencia de las variables globales de Solidity, Soroban se basa en pasar un argumento [`Env`](https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Env.html) a todas las funciones que proporciona acceso al entorno en el que se está ejecutando el contrato.
-
-El `Env` proporciona acceso a la información sobre el contrato que se está ejecutando actualmente, quién lo invocó, datos del contrato, funciones para firmar, hashear, etc.
-
-Por ejemplo, usarías `env.storage().persistent().get(key)` para acceder a un valor de objetivo `persistent` del [almacenamiento](https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Env.html) del contrato. Lee más acerca de los diferentes tipos de almacenamiento [aquí](../../fundamentals/contract-development/storage/persisting-data.mdx).
-
-- `env.storage()` se usa para obtener una estructura para acceder y actualizar datos de contrato que han sido almacenados.
-- Usado como `env.storage().persistent().get()` o `env.persistent().storage().set()`.
-- Adicionalmente, utilizamos el método `clone()`, una característica prevalente en Rust que permite la duplicación explícita de un objeto.
-
-Consulta el ejemplo a continuación para implementaciones de `env.storage()` y `clone()`
-
-- `env.storage().persistent().set()`
-
-```rust
-use soroban_sdk::{Env, Symbol};
-
-    pub fn set_storage(env: Env) {
-        let key = symbol_short!("key");
-        let value = symbol_short!("value");
-        env.storage().persistent().set(&key, &value);
-}
-```
-
-- `env.storage().persistent().get()`
-
-```rust
-use soroban_sdk::{Env};
-
-    pub fn get_storage(env: Env) -> value {
-        env.storage().persistent().get(&key);
-}
-```
-
-- `clone()`
-
-```rust
-use soroban_sdk::{Env, Address};
-
-    pub fn return_user(user: Address) -> Address {
-        let user_address: Address = user.clone();
-        user_address
-}
-```
-
-### Manejo de Errores
-
-El SDK de Soroban Rust y Solidity proporcionan varias maneras de manejar errores. Estas incluyen:
-
-#### Solidity
-
-Solidity proporciona una función `require` que se puede utilizar para verificar ciertas condiciones y revertir la transacción si no se cumplen. Por ejemplo, el siguiente código establece un valor mínimo para la cantidad de Ether enviado con la transacción:
-
-```solidity
-
-function deposit() public payable {
-    require(msg.value >= 1 ether, "Not enough Ether sent");
-    // ...
-}
-```
-
-#### Soroban
-
-El macro [panic!](https://doc.rust-lang.org/book/ch09-00-error-handling.html) actúa como el mecanismo de manejo de errores de Rust, que se asemeja estrechamente a la función `require` en Solidity.
-
-```rust
-pub fn simple_deposit(amount: u32) {
-    if amount < 1_000_000 {
-        panic!("amount too low");
-    }
-        // ...
-    }
-```
-
-### Funcionalidad Relacionada con Direcciones
-
-Tanto Soroban como Solidity proporcionan varias funciones para trabajar con direcciones. Estas funciones incluyen:
-
-#### Solidity
-
-- `address(this)`: Devuelve la dirección del contrato actual.
-- `address payable(this)`: Devuelve la dirección del contrato actual como una dirección pagadera.
-- `address(address)`: Devuelve la dirección de la cuenta especificada.
-- `address payable(address)`: Devuelve la dirección de la cuenta especificada como una dirección pagadera.
-
-A continuación se muestra un ejemplo de un contrato inteligente que ilustra cómo se pueden recuperar contratos
-
-```solidity
-pragma solidity ^0.8.0;
-
-contract SimpleContract {
-    address public contractAddress = address(this);
-    address public randomAddress = 0x1234567890123456789012345678901234567890;
-
-    address public payableAddress = payable(address(this));
-    address public payableRandomAddress = payable(0x1234567890123456789012345678901234567890);
-}
-```
-
-No habría diferencia en la apariencia entre una dirección normal y una dirección pagadera en Solidity.
-
-#### Soroban
-
-- `e.current_contract_address()`: Devuelve el objeto Address correspondiente al contrato que se está ejecutando actualmente.
-
-El `Env` no solo proporciona información esencial sobre el contrato que se está ejecutando actualmente y su invocador, sino que también ofrece acceso a datos de contratos y funciones para firmar, hash, y más. La construcción o conversión de la mayoría de los tipos en Soroban requiere acceso a una instancia de `Env`.
-
-Aquí hay un ejemplo de un contrato inteligente que ilustra cómo se pueden recuperar contratos:
-
-```rust
-#![no_std]
-use soroban_sdk::{contractimpl, log, Address, Env, Symbol};
-
-#[contract]
-pub struct SimpleContract;
-
-#[contractimpl]
-impl SimpleContract {
-    ///Example contract for returning a contract Address.
-    pub fn return_address(env: Env) -> Address {
-        let current_contract_address = env.current_contract_address();
-        current_contract_address
-    }
-}
-```
-
-#### Por qué Soroban es Diferente
-
-Soroban tiene algunas diferencias con Solidity en términos de direcciones y otras funcionalidades. Estas diferencias surgen debido a los principios de diseño y objetivos de Soroban.
-
-Una diferencia significativa es el uso del objeto `Env` en Soroban. El objeto `Env` encapsula diversas funcionalidades relacionadas con la ejecución de contratos, acceso a datos, y más. Proporciona una interfaz unificada para interactuar con el entorno de Soroban dentro del contexto de un contrato. Al utilizar el objeto `Env`, Soroban permite un enfoque más modular y flexible para el desarrollo de contratos.
-
-Para explicar más, el tipo `Env` ofrece una puerta de entrada al entorno en el que opera el contrato. Proporciona información sobre el contrato en curso, la entidad que lo invoca, los datos del contrato, y funciones para firmar, hacer hash, etc. La mayoría de los tipos demandan acceso a un `Env` para su construcción o conversión.
-
-Mientras tanto, el objeto `Address` sirve como una herramienta potente para la autenticación y [autorización](#authorization). Por ejemplo, se puede usar para autorizar transferencias de tokens, actuando como un guardián de seguridad dentro del sistema. Esta característica amplifica la funcionalidad de las direcciones en Soroban, haciéndolas no solo un medio de identificación o almacenamiento, sino también un actor clave en la verificación y autorización de transacciones.
-
-### Especificadores de Visibilidad de Funciones
-
-El SDK de Soroban Rust y Solidity proporcionan varios especificadores de visibilidad de funciones que se pueden utilizar para controlar quién puede llamar a una función. Estos especificadores incluyen:
-
-#### Solidity
-
-- `public`: Cualquiera puede llamar a la función.
-- `external`: Solo otros contratos pueden llamar a la función.
-- `internal`: Solo el contrato actual y los contratos que heredan de él pueden llamar a la función.
-- `private`: Solo el contrato actual puede llamar a la función.
-
-Aquí hay un ejemplo de un contrato inteligente que ilustra cómo se utiliza la visibilidad de funciones en Solidity:
-
-```solidity
-pragma solidity ^0.8.0;
-
-contract SimpleContract {
-    function publicFunction() public {}
-    function externalFunction() external {}
-    function internalFunction() internal {}
-    function privateFunction() private {}
-}
-```
-
-#### Soroban
-
-- `pub`: El ítem (función, estructura, etc.) es accesible desde cualquier módulo o ámbito.
-- `pub(crate)`: El ítem es accesible solo dentro del crate actual.
-- `pub(super)`: El ítem es accesible solo dentro de su módulo padre.
-- `pub(in path::to::module)`: El ítem es accesible solo dentro de la ruta de módulo especificada.
-- `private`: El ítem no está marcado como pub y, por lo tanto, es privado para su propio módulo, lo que significa que solo se puede acceder dentro del mismo módulo y no es accesible desde fuera del módulo.
-
-Aquí hay un ejemplo de un módulo que ilustra cómo se utiliza la visibilidad de funciones en Soroban:
-
-```rust
-#![no_std]
-use soroban_sdk::{contractimpl, Env};
-
-mod outer {
-    pub struct PublicStruct {
-        pub field: u32,
-    }
-
-    pub(crate) struct CrateStruct {
-        pub(crate) field: u32,
-    }
-
-    // This struct is private because it is not marked as `pub`.
-    struct PrivateStruct {
-        field: u32,
-    }
-
-    mod inner {
-        pub(super) struct SuperStruct {
-            pub(super) field: u32,
-        }
-    }
-
-    pub fn get_all_fields() -> u32 {
-        let public_struct = PublicStruct { field: 1 };
-        let crate_struct = CrateStruct { field: 2 };
-        let private_struct = PrivateStruct { field: 3 };
-        let super_struct = inner::SuperStruct { field: 4 };
-        public_struct.field + crate_struct.field + private_struct.field + super_struct.field
-    }
-}
-
-#[contract]
-pub struct NewContract;
- trait OuterTrait {
-    fn get_all_fields() -> u32;
-    fn get_public_fields() -> u32;
-}
-
-#[contractimpl]
-impl OuterTrait for NewContract {
-    fn get_public_fields() -> u32 {
-        let public_struct = outer::PublicStruct { field: 1 };
-        let crate_struct = outer::CrateStruct { field: 2 };
-        // private structs cannot be accessed from outside the crate
-        public_struct.field + crate_struct.field
-    }
-
-    fn get_all_fields() -> u32 {
-        outer::get_all_fields()
-    }
-}
-```
-
-### Variables Basadas en el Tiempo
-
-El SDK de Soroban Rust y Solidity proporcionan varias variables basadas en el tiempo que se pueden utilizar para acceder a información sobre el bloque actual(EVM) o ledger(Soroban). Estas variables incluyen:
-
-#### Solidity
-
-- `block.timestamp`: La marca de tiempo del bloque actual.
-- `block.number`: El número del bloque actual.
-
-Aquí hay un ejemplo de un contrato inteligente que ilustra cómo se utilizan las variables basadas en el tiempo en Solidity:
-
-```solidity
-pragma solidity ^0.8.0;
-
-contract SimpleContract {
-    function getTimestamp() public view returns (uint256) {
-        return block.timestamp;
-    }
-
-    function getBlockNumber() public view returns (uint256) {
-        return block.number;
-    }
-}
-```
-
-#### Soroban
-
-- `env.ledger().timestamp()`: Devuelve una marca de tiempo unix para cuando se cerró el ledger más reciente.
-- `env.ledger().sequence()`: Devuelve el número de secuencia del ledger cerrado más recientemente.
-
-Aquí hay un ejemplo de un contrato inteligente que ilustra cómo se utilizan las variables basadas en el tiempo en Rust:
-
-```rust
-#![no_std]
-use soroban_sdk::{contractimpl, Address, Env};
-
-#[contract]
-pub struct SimpleContract;
-
-#[contractimpl]
-impl SimpleContract {
-    pub fn get_timestamp(env: Env) {
-        let timestamp = env.ledger().timestamp();
-        let sequence = env.ledger().sequence();
-    }
-}
-```
-
-### Autorización
-
-Soroban difiere de Solidity en su enfoque hacia la autorización y los modificadores. Mientras que Solidity tiene un sistema de modificadores incorporado, Soroban no. En su lugar, Soroban aprovecha traits, sus implementaciones, y características centrales para lograr una funcionalidad similar.
-
-#### Solidity
-
-En Solidity, el estándar de token ERC20 incluye la función `approve`, que permite a un tenedor de tokens autorizar a otra dirección a gastar una cierta cantidad de tokens en su nombre. Esta función se usa comúnmente en intercambios descentralizados y otros escenarios de transferencia de tokens. Además, nos aseguramos de que el gastador esté autorizado para gastar la cantidad de tokens solicitada por el tenedor de tokens.
-
-Aquí hay un ejemplo de cómo la función approve actúa como un mecanismo de autorización en Solidity:
-
-```solidity
-pragma solidity ^0.8.0;
-
-contract ERC20Token {
-
-    constructor() {
-        address owner = msg.sender;
-        ownerAddress = owner;
-    }
-
-    mapping(address => uint256) public balances;
-    mapping(address => mapping(address => uint256)) public allowances;
-    mapping(address => bool) public isAuthorized;
-
-    address public ownerAddress;
-
-    function approve(address spender, uint256 amount) public returns (bool) {
-        allowances[msg.sender][spender] = amount;
-        return true;
-    }
-
-    function setAuthorization(address newAuth) public returns (bool) {
-        require(msg.sender == ownerAddress);
-        isAuthorized[newAuth] = true;
-        return true;
-    }
-
-    function transfer(address to, uint256 amount) public returns (bool) {
-        require(allowances[msg.sender][to] >= amount, "Not enough allowance");
-        require(isAuthorized[to] == true, "Not authorized");
-        balances[msg.sender] -= amount;
-        balances[to] += amount;
-        return true;
-    }
-}
-```
-
-La función approve permite al tenedor de tokens autorizar al gastador para gastar tokens de cantidad en su nombre. La función transfer luego verifica si el gastador está autorizado para gastar la cantidad de tokens solicitada por el tenedor de tokens. Si es así, la transferencia se ejecuta.
-
-Estos ejemplos de Solidity ilustran algunos patrones comunes de autorización utilizados en contratos inteligentes de Ethereum. Soroban proporciona enfoques alternativos para lograr una funcionalidad similar, aprovechando la funcionalidad central derivada directamente del SDK de Soroban.
-
-#### Soroban
-
-Los principios de diseño de Soroban priorizan la flexibilidad, seguridad y capacidad de prueba, lo que ha llevado a diferencias en cómo se maneja la autorización en comparación con Solidity.
-
-Soroban proporciona funciones incorporadas como `require_auth` y `require_auth_for_args` a través de la estructura `Address`. Estas funciones ayudan a hacer cumplir las reglas de autorización dentro de los contratos. Durante la ejecución on-chain, el host de Soroban realiza la autenticación necesaria, incluyendo la verificación de firmas y **asegurando la prevención de replays**. Esto alivia la carga de autenticación de los mismos contratos, promoviendo la seguridad y reduciendo vulnerabilidades potenciales.
-
-Aquí hay un ejemplo de un contrato inteligente que ilustra cómo se maneja la autorización en Soroban:
-
-```rust
-#![no_std]
-use soroban_sdk::{contractimpl, testutils::Address as _, Address, Symbol, Env, IntoVal};
-
-#[contract]
-pub struct Contract;
-
-#[contractimpl]
-impl Contract {
-    pub fn transfer(env: Env, address: Address, amount: i128) {
-        address.require_auth();
-    }
-    pub fn transfer2(env: Env, address: Address, amount: i128) {
-        address.require_auth_for_args((amount / 2,).into_val(&env));
-    }
-}
-```
-
-En este ejemplo, tenemos un contrato de Soroban que incluye dos funciones públicas: `transfer` y `transfer2`, ambas de las cuales implican verificaciones de autorización.
-
-Dentro de la función Transfer, se invoca el método `require_auth` en el objeto de dirección. Este método asegura que el llamador del contrato tenga la autorización necesaria para ejecutar la transferencia.
-
-La función `transfer2` sigue un patrón similar, pero utiliza el método `require_auth_for_args` en su lugar. Toma los mismos parámetros que transfer, pero proporciona una tupla (cantidad / 2,) como argumento para `require_auth_for_args`. Este método verifica que el llamador haya autorizado la invocación del contrato con los argumentos específicos.
-
-Al utilizar estos métodos de autorización proporcionados por el objeto `Address` del SDK de Soroban Rust, el contrato exige que solo los llamadores autorizados puedan realizar las transferencias. Este enfoque mejora la seguridad del contrato al asegurar que las operaciones sensibles solo pueden ser ejecutadas por partes autorizadas.
-
-El enfoque de Soroban hacia la autorización en este ejemplo ofrece varias ventajas sobre el modelo de ERC20 de Solidity al eliminar la necesidad de gestionar aprobaciones por separado. En su lugar, las verificaciones de autorización se pueden incorporar directamente en cualquier función de Soroban. Esto simplifica la base de código del contrato y reduce la complejidad asociada con la gestión de estados de aprobación separados.
-
-La autorización de Soroban proporciona autorización a nivel de contrato, funcionalidad de abstracción de cuentas, y más verificaciones avanzadas de autorización. Para conocer más sobre estas ventajas, visita la [sección de Autorización](../../fundamentals/contract-development/authorization.mdx) de la documentación.
-
-## Resumen
-
-En general, los equivalentes de Soroban de los conceptos de Solidity son muy similares. Sin embargo, hay diferencias notables que vale la pena resaltar. Soroban utiliza `env` en lugar de `msg` para acceder a información sobre todo el entorno de ejecución del contrato, incluyendo el estado del contrato, direcciones involucradas, y más. La autorización también se maneja de manera diferente en Soroban, ya que está integrada en la funcionalidad central del SDK y es más robusta que depender únicamente del código del contrato inteligente.
-
-Para más información sobre los conceptos de Solidity y sus equivalentes en Soroban, se recomienda consultar tanto la [documentación del SDK de Soroban Rust](https://docs.rs/soroban-sdk/latest/soroban_sdk/struct.Env.html) como la [documentación de Solidity](https://docs.soliditylang.org/en/v0.8.19/cheatsheet.html).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-and-rust-basics.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-and-rust-basics.mdx
deleted file mode 100644
index c23502ded6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-and-rust-basics.mdx
+++ /dev/null
@@ -1,642 +0,0 @@
----
-sidebar_position: 1
-title: Sintaxis de Solidity y Rust, Tipos de Datos y Estructuras Básicas
-description: Explorar los fundamentos de la sintaxis de Solidity y Rust, los tipos de datos y las estructuras básicas.
----
-
-# Comenzar con Rust y Solidity
-
-En este tutorial, exploraremos Rust y Solidity, dos poderosos lenguajes de programación. Rust, un lenguaje de programación de sistemas, es conocido por sus características de seguridad, concurrencia y rendimiento, que pueden ser ventajosas al crear contratos inteligentes. Por otro lado, Solidity es un lenguaje de alto nivel específicamente diseñado para crear contratos inteligentes en la Máquina Virtual de Ethereum. Esta sección tiene como objetivo proporcionar una visión general de alto nivel de las similitudes y diferencias entre los dos lenguajes.
-
-## Tabla de Contenidos
-
-1. [Sintaxis de Solidity, Tipos de Datos y Estructuras Básicas](#solidity-syntax)
-2. [Sintaxis de Rust, Tipos de Datos y Modelo de Propiedad](#rust-syntax)
-3. [Escribir e Interactuar con Contratos Inteligentes Simples](#writing-and-interacting-with-simple-smart-contracts)
-
-### Sintaxis de Solidity
-
-Solidity es un lenguaje de programación diseñado específicamente para crear contratos inteligentes en la Máquina Virtual de Ethereum (EVM). Tiene una sintaxis similar a JavaScript y admite una variedad de tipos de datos y estructuras.
-
-```solidity
-pragma solidity ^0.8.0;
-
-contract HelloWorld {
-  function sayHello() public pure returns (string memory) {
-    return "Hello, World!";
-  }
-}
-```
-
-### Tipos de Datos
-
-Solidity admite varios tipos de datos, tales como:
-
-- Booleano: `bool`
-- Entero: `int` (con signo) y `uint` (sin signo)
-- Dirección: `address`
-- Cadena: `string`
-- Bytes: `bytes` (de tamaño dinámico) y `bytes32` (de tamaño fijo)
-- Matrices: de tamaño dinámico o de tamaño fijo y pueden ser declaradas con varios tipos.
-- Estructuras: `struct`
-- Enumeraciones: `enum`
-- Mapeo: `mapping`
-
-Aquí hay ejemplos de implementaciones para cada tipo de dato:
-
-```solidity
-pragma solidity ^0.8.0;
-
-contract DataTypesExample {
-    // Boolean
-    bool public isCompleted = false;
-
-    // Integer (signed and unsigned)
-    int256 public signedInteger = -10;
-    uint256 public unsignedInteger = 10;
-
-    // Address
-    address public userAddress = 0x742d35Cc6634C0532925a3b844Bc454e4438f44e;
-
-    // String
-    string public greeting = "Hello, World!";
-
-    // Bytes (dynamic-size and fixed-size)
-    bytes public dynamicBytes = "hello, solidity";
-    bytes32 public fixedBytes = "hello, solidity";
-
-    // Arrays (dynamic-size and fixed-size)
-    uint[] public dynamicArray = [1, 2, 3];
-    uint[5] public fixedArray = [1, 2, 3, 4, 5];
-
-    address[] public dynamicAddressArray = [0xd41d1744871f42Bb724D777A2d0Bf53FB43a0040, 0x1f514ae9834aEAF6c2c3eb6D20E27e865F419010];
-    address[3] public fixedAddressArray = [0xC90cd0D820D6dc447B3cD9545185B046873786A6, 0x401997E856CE51e0D4A8f26ce64952313BEA0E25, 0x221d3b9821f3Cc49B42E7dd487E2a6d1b3ed0E05];
-
-    bool[] public dynamicBoolArray = [true, false, true];
-    bool[2] public fixedBoolArray = [true, false];
-
-    // Struct
-    struct Person {
-        string name;
-        uint age;
-    }
-    Person public person = Person("Alice", 30);
-
-    // Enums
-    enum Status { Open, Closed, Pending }
-    Status public currentStatus = Status.Open;
-    Status public nextStatus = Status.Closed;
-    Status public previousStatus = Status.Pending;
-
-    // Mapping
-    mapping(address => uint) public balances;
-
-    constructor() {
-        balances[msg.sender] = 100;
-    }
-}
-```
-
-### Estructuras Básicas
-
-Algunas de las estructuras básicas en Solidity incluyen:
-
-1. `Variables`: Declaradas con un tipo de dato y un identificador.
-2. `Funciones`: Definidas con la palabra clave `function`.
-3. `Modificadores`: Utilizados para modificar el comportamiento de las funciones.
-4. `Eventos`: Utilizados para registrar cambios en el estado del contrato.
-5. `Herencia`: Solidity admite herencia simple y múltiple.
-
-Exploraremos algunas de estas estructuras con más detalles en el próximo artículo, [Conceptos Avanzados de Solidity](./solidity-and-rust-advanced-concepts.mdx#advanced-solidity-concepts).
-
-### Sintaxis de Rust
-
-Rust es un lenguaje de programación que es muy adecuado para construir contratos inteligentes debido a su énfasis en la seguridad, la concurrencia y el rendimiento. Impone estrictas reglas de propiedad y préstamo para prevenir condiciones de carrera y otros errores comunes.
-
-```rust
-fn main() {
-    println!("Hello, world!");
-}
-```
-
-### Tipos de Datos
-
-El [Soroban Rust SDK](https://docs.rs/soroban-sdk/latest/soroban_sdk/index.html) admite una variedad de [Tipos Incorporados](../../fundamentals/contract-development/types/built-in-types.mdx) que consisten tanto en Tipos Primitivos como en [Tipos Personalizados](../../fundamentals/contract-development/types/custom-types.mdx), tales como:
-
-#### Tipos de Datos Primitivos
-
-- Enteros de 32 bits: con signo (`i32`) y sin signo (`u32`)
-- Enteros de 64 bits: con signo (`i64`) y sin signo (`u64`)
-- Enteros de 128 bits: con signo (`i128`) y sin signo (`u128`)
-- Bool (`bool`)
-- Bytes, Cadenas (`Bytes`, `BytesN`): arreglos de bytes y cadenas que pueden ser pasados a contratos y almacenados
-- Vec (`Vec`): tipo de colección secuencial y indexable que puede crecer
-- Mapa (`Map`): diccionario clave-valor ordenado
-- Dirección (`Address`): identificador opaco universal utilizado en contratos
-- Cadena (`String`): un tipo de arreglo que crece de forma contigua y contiene u8s y requiere que se pase un entorno
-- Símbolo:
-
-  - (`Symbol::new`): cadenas pequeñas y eficientes de hasta 32 caracteres de longitud y requieren que se pase un entorno
-  - (`symbol_short!`) cadenas pequeñas y eficientes de hasta 9 caracteres de longitud
-
-  Ambos están limitados a los caracteres `a-zA-Z0-9_` y están codificados en enteros de 64 bits.
-
-#### Tipos de Datos Personalizados
-
-- `Estructuras` (con Campos Nombrados): Un tipo personalizado que consiste en campos nombrados almacenados en el ledger como un `map` de pares clave-valor.
-- `Estructuras` (con Campos Sin Nombre): Un tipo personalizado que consiste en campos sin nombre almacenados en el ledger como un vector de valores.
-- `Enumeración` (Variantes Unitarias y de Tupla): Un tipo personalizado que consiste en variantes unitarias y de tupla almacenadas en el ledger como un vector de dos elementos, donde el primer elemento es el nombre de la variante y el segundo es el valor.
-- `Enumeración` (Variantes Enteras): Un tipo personalizado que consiste en variantes enteras almacenadas en el ledger como el valor `u32`.
-
-Los siguientes son ejemplos de implementaciones para cada tipo de dato:
-
-```rust
-// Integer (signed and unsigned)
-let unsigned_32_bit: u32 = 42;
-let signed_32_bit: i32 = -42;
-let unsigned_64_bit: u64 = 42;
-let signed_64_bit: i64 = -42;
-let unsigned_128_bit: u128 = 42;
-let signed_128_bit: i128 = -42;
-
-// Boolean
-let boolean: bool = true;
-
-// String
-let msg: &str = "Hello";
-String::from_slice(&env, msg)
-
-// Symbols (short and new)
-let symbol_short = symbol_short!("Sample"); // up to 9 chars
-// env is &Env
-let symbol_new = Symbol::new(env, "SampleSymbolExpression");
-
-// Bytes (Bytes and BytesN)
-let bytes = Bytes::from_slice(&env, &[1; 32]);
-let bytes_n = BytesN::from_array(&env, &[0; 32]);
-
-// Vec
-let vec = vec![&env, 0, 1, 2, 3];
-
-// Map
-let map = map![&env, (2, 20), (1, 10)];
-
-// Address
-let address = Address::new([0u8; 32]);
-
-// Struct (named fields)
-pub struct State {
-    pub count: u32,
-    pub last_incr: u32,
-}
-
-struct Tuple(u32, String);
-
-// Struct (unnamed fields)
-pub struct State(pub u32, pub u32);
-
-// Enum (unit and tuple variants)
-pub enum Enum {
-    A,
-    B(u32),
-}
-
-// Enum (integer variants)
-pub enum Enum {
-    A = 0,
-    B = 1,
-}
-```
-
-### Una Breve Introducción a Módulos, Macros, Estructuras, Traits y Macros de Atributo
-
-En esta sección, proporcionaremos una introducción concisa a algunos conceptos fundamentales en Rust: `Módulos`, `Macros`, `Estructuras`, `Traits`, y `Macros de Atributo`.
-
-Estos conceptos son esenciales para entender y escribir código Rust eficiente, y te ayudarán en tu camino como desarrollador de contratos inteligentes.
-
-#### 1. Módulos
-
-Los módulos en Rust se utilizan para organizar y separar el código en diferentes espacios de nombres. Permiten una mejor organización del código, reutilización y encapsulamiento. Para definir un módulo, utiliza la palabra clave `mod` seguida de un bloque que contenga el contenido del módulo.
-
-```rust
-mod my_module {
-    pub fn my_function() {
-        println!("Hello from my_module!");
-    }
-}
-```
-
-#### 2. Macros
-
-[Macros](https://doc.rust-lang.org/book/ch19-06-macros.html) en Rust son herramientas poderosas que te permiten hacer metaprogramación, permitiendo construir bloques de código reutilizables en tiempo de compilación.
-
-Existen dos tipos básicos: macros [declarativas](https://doc.rust-lang.org/book/ch19-06-macros.html#declarative-macros-with-macro_rules-for-general-metaprogramming) y [procedurales](https://doc.rust-lang.org/book/ch19-06-macros.html#procedural-macros-for-generating-code-from-attributes). La más común es la macro declarativa, o simplemente "macro", que se define con `macro_rules!`. La más común es la macro declarativa, o simplemente "macro", que se define con `macro_rules!`.
-
-```rust
-macro_rules! my_macro {
-    () => {
-        println!("Hello from my_macro!");
-    };
-}
-
-fn main() {
-    my_macro!();
-}
-```
-
-#### 3. Estructuras
-
-Las estructuras son tipos de datos personalizados en Rust que permiten agrupar datos juntos. Proporcionan una forma de definir y crear estructuras de datos más complejas.
-
-```rust
-struct MyStruct {
-    field1: i32,
-    field2: String,
-}
-
-fn main() {
-    let my_instance = MyStruct {
-        field1: 42,
-        field2: String::from("Hello"),
-    };
-}
-```
-
-#### 4. Rasgos
-
-Los traits en Rust definen un conjunto compartido de comportamientos que los tipos pueden usar tal como están (implementaciones predeterminadas) o implementar ellos mismos. Se pueden considerar como interfaces en otros lenguajes. Los traits se definen con la palabra clave `trait`, y sus métodos pueden implementarse para diferentes tipos usando la palabra clave `impl`.
-
-```rust
-trait MyTrait {
-    fn my_method(&self);
-}
-
-struct MyStruct;
-
-impl MyTrait for MyStruct {
-    fn my_method(&self) {
-        println!("Hello from MyTrait's my_method!");
-    }
-}
-```
-
-#### 5. Macros de Atributo
-
-Las macros de atributo en Rust son una forma de macros procedurales que te permiten definir atributos personalizados para diversos elementos del lenguaje, como funciones, estructuras y enumeraciones. Pueden modificar o generar código basado en los ítems anotados.
-
-```rust
-// To use an attribute macro, first import it with `use`
-use my_attribute_macro::my_attribute;
-
-// Then apply the attribute to an element in your code
-#[my_attribute]
-fn my_function() {
-    println!("Hello from my_function!");
-}
-```
-
-Durante tu viaje como desarrollador de contratos inteligentes, encontrarás frecuentemente la macro de atributo [`#[contractimpl]`](https://docs.rs/soroban-sdk/latest/soroban_sdk/index.html) que exporta funciones accesibles públicamente al entorno de Soroban.
-
-Las funciones que son accesibles públicamente en la implementación pueden ser invocadas por otros contratos, o directamente por transacciones, al ser desplegadas.
-
-```rust
-#[contractimpl]
-impl HelloContract {
-    pub fn hello(env: Env, to: Symbol) -> Vec<Symbol> {
-        vec![&env, symbol_short!("Hello"), to]
-    }
-}
-```
-
-### Modelo de Propiedad
-
-Rust impone [**reglas estrictas de propiedad**](https://doc.rust-lang.org/book/ch04-00-understanding-ownership.html) para manejar la memoria y los recursos:
-
-- Cada valor tiene un único propietario.
-- Cuando el propietario sale del alcance, el valor se desaloja automáticamente.
-- [`Préstamo`](https://doc.rust-lang.org/book/ch04-02-references-and-borrowing.html): Los valores pueden ser prestados como referencias inmutables o mutables.
-- [`Duraciones`](https://doc.rust-lang.org/rust-by-example/scope/lifetime.html): Se utilizan para asegurar que las referencias sigan siendo válidas.
-
-### Dialectos de Contrato Inteligente
-
-El desarrollo de contratos en Rust implica ciertas restricciones debido a características no disponibles en el entorno de despliegue o altos costos de ejecución. Por lo tanto, el código escrito para contratos puede verse como un _dialecto_ distinto de Rust, centrándose en un comportamiento determinista y un tamaño de código minimizado.
-
-Para aprender más sobre el Dialecto de Contrato de Rust, visita la [Página del Dialecto de Contrato Rust](../../fundamentals/contract-development/rust-dialect.mdx).
-
-## Escribir e Interactuar con Contratos Inteligentes Simples
-
-En esta sección, aprenderemos a escribir e interactuar con contratos inteligentes simples en Solidity y Rust.
-
-### Escribir un Contador Inteligente en Solidity
-
-Aquí hay un ejemplo de un simple contrato inteligente de Solidity para un contador:
-
-```solidity
-// SPDX-License-Identifier: UNLICENSED
-pragma solidity ^0.8.0;
-
-contract Counter {
-    uint256 private _count;
-
-    function getCount() public view returns (uint256) {
-        return _count;
-    }
-
-    function increment() public {
-        _count += 1;
-    }
-}
-```
-
-Desglosemos el diseño del código línea por línea:
-
-```solidity
-// SPDX-License-Identifier: UNLICENSED
-```
-
-Este es un comentario que identifica la [licencia](https://docs.soliditylang.org/en/v0.8.19/layout-of-source-files.html#spdx-license-identifier) para el código. No es necesario para que el código se ejecute, pero es una buena práctica incluir información sobre la licencia.
-
-```solidity
-pragma solidity ^0.8.0;
-```
-
-Esto especifica la versión de Solidity para la que se escribió este código. En este caso, es la versión `0.8.0` o superior.
-
-```solidity
-contract Counter {}
-```
-
-Esto define un nuevo contrato de Solidity llamado `Counter`.
-
-```solidity
-uint256 private _count;
-```
-
-Esta es una [`variable privada`](https://docs.soliditylang.org/en/v0.8.19/cheatsheet.html#function-visibility-specifiers) llamada `_count` de tipo `uint256` (entero sin signo). Esta variable se utilizará para almacenar el valor actual del contador. Está marcada como `private`, lo que significa que solo puede ser accesible desde dentro del contrato.
-
-```solidity
-function getCount() public view returns (uint256) {
-    return _count;
-}
-```
-
-Esta es una función llamada `getCount()` que devuelve el valor actual del contador. La función está marcada como `public`, lo que significa que puede ser llamada desde fuera del contrato. La palabra clave `view` indica que esta función no modifica el estado del contrato. La palabra clave `returns` especifica el tipo de retorno de la función.
-
-```solidity
-function increment() public {
-    _count += 1;
-}
-```
-
-Esta es una función llamada `increment()` que incrementa el contador en 1. No devuelve nada, pero modifica el estado del contrato. Al igual que `getCount()`, está marcada como `public`, lo que significa que puede ser llamada tanto desde dentro como desde fuera del contrato.
-
-### Interactuar con el Contador Inteligente de Solidity
-
-Podemos interactuar con el contrato inteligente utilizando el `Remix IDE`. Para hacerlo, sigue estos pasos:
-
-1. Haz clic en el siguiente enlace para [abrir el Gist en Remix](https://remix.ethereum.org/#version=soljson-v0.8.18+commit.87f61d96.js&optimize=false&runs=200&gist=416ab15a6beed9d91cf2f615625ffe48&lang=en&evmVersion=null).
-
-2. Navega al archivo `Counter.sol` en el explorador de archivos.
-
-![Contador](/img/migrating/counter.png)
-
-3. Presiona `Ctrl/Cmd + s` para compilar el contrato.
-4. Navega a la pestaña `Deploy & Run Transactions` y haz clic en el botón `Deploy`.
-
-![Desplegar](/img/migrating/deploy-counter.png)
-
-El contrato debería aparecer bajo la pestaña `Deployed Contracts`:
-
-![Desplegado](/img/migrating/deployed-contracts.png)
-
-5. Haz clic en el botón `increment` para incrementar el contador.
-6. Haz clic en el botón `getCount` para obtener el conteo actual.
-
-![Incrementar](/img/migrating/increment.png)
-
-Hasta este punto, hemos cubierto los conceptos básicos de escribir, desplegar en una EVM de sandbox y interactuar con un contrato inteligente simple utilizando Solidity. En la siguiente sección, ampliaremos nuestro conocimiento aprendiendo cómo lograr los mismos resultados usando Rust.
-
-### Escribir un Contador Inteligente en Rust
-
-En esta sección, crearemos un programa en Rust que simule la funcionalidad del contrato inteligente Counter. Aquí hay un ejemplo de un contador simple en Rust:
-
-```rust
-#![no_std]
-use soroban_sdk::{contractimpl, log, Env, Symbol};
-
-const COUNTER: Symbol = symbol_short!("COUNTER");
-
-#[contract]
-pub struct IncrementContract;
-
-#[contractimpl]
-impl IncrementContract {
-    /// Increment increments an internal counter, and returns the value.
-    pub fn increment(env: Env) -> u32 {
-        // Get the current count.
-        let mut count: u32 = env.storage().instance().get(&COUNTER).unwrap_or(0); // If no value set, assume 0.
-        log!(&env, "count: {}", count);
-
-        // Increment the count.
-        count += 1;
-
-        // Save the count.
-        env.storage().instance().set(&COUNTER, &count);
-
-        // Return the count to the caller.
-        count
-    }
-
-    /// get_count returns the current value of the counter.
-    pub fn get_count(env: Env) -> u32 {
-        env.storage().instance().get(&COUNTER).unwrap_or(0)
-    }
-}
-```
-
-Este código es una implementación de un contrato inteligente escrito en Rust utilizando el [`Soroban Rust SDK`](../../../tools/sdks/contract-sdks.mdx#soroban-rust-sdk), un conjunto de herramientas para el desarrollo de contratos inteligentes basado en Rust desarrollado por la [Stellar Development Foundation (SDF)](https://stellar.org/foundation). El Soroban Rust SDK proporciona un poderoso conjunto de herramientas para escribir contratos inteligentes que se ejecutan en la Máquina Virtual Soroban.
-
-Aquí hay una explicación línea por línea de lo que hace el código:
-
-```rust
-#![no_std]
-```
-
-Este es un atributo de Rust que le dice al compilador de Rust que no enlace la [biblioteca estándar de Rust](https://doc.rust-lang.org/std/). La biblioteca estándar es extensa, y al desplegar aplicaciones Soroban, queremos simplificar el proceso tanto como sea posible. Al usar `no_std`, establecemos un punto de partida más ligero y "esquelético" para los proyectos, que abarca solo el núcleo de Rust y algunos otros componentes esenciales, en lugar de toda la amplitud de la biblioteca estándar.
-
-```rust
-use soroban_sdk::{contractimpl, log, Env, Symbol};
-```
-
-Este código importa elementos necesarios del Soroban Rust SDK para escribir un contrato inteligente. La `contractimpl` [macro](https://doc.rust-lang.org/book/ch19-06-macros.html) se utiliza para implementar el contrato inteligente, mientras que la macro `log` se utiliza para registrar mensajes. La estructura `Env` representa el entorno en el que se está ejecutando el contrato, y el tipo `Symbol` es un tipo de cadena pequeño y eficiente.
-
-```rust
-const COUNTER: Symbol = symbol_short!("COUNTER");
-```
-
-Esto crea un nuevo valor de `Symbol` con la cadena "COUNTER". La constante `COUNTER` se utiliza luego como clave para identificar el valor de conteo almacenado en el `storage` del contrato.
-
-```rust
-#[contract]
-pub struct IncrementContract;
-```
-
-Esto define una estructura pública, `IncrementContract`, que contendrá la implementación del contrato inteligente.
-
-```rust
-#[contractimpl]
-impl IncrementContract {}
-```
-
-Esta es una macro que implementa la estructura `IncrementContract` como un contrato inteligente.
-
-Como se mencionó anteriormente, el atributo `#[contractimpl]` exporta funciones públicas al entorno de Soroban. Esto significa que estas funciones se vuelven accesibles dentro de la implementación y pueden ser invocadas por otros contratos o directamente por transacciones al ser desplegadas.
-
-```rust
-pub fn increment(env: Env) -> u32 {}
-```
-
-Esta es una función pública llamada `increment` que toma una estructura `Env` como argumento y devuelve un `u32`. `Env` es el entorno en el que se está ejecutando el contrato, y `u32` es el tipo del valor devuelto por la función.
-
-```rust
-let mut count: u32 = env.storage().instance().get(&COUNTER).unwrap_or(0)); // If no value set, assume 0.
-```
-
-En esta línea de código, se está creando una variable mutable llamada `count` de tipo entero sin signo de 32 bits (`u32`). El entorno de almacenamiento se accede utilizando `env.storage()`, y se recupera el valor asociado con la clave `COUNTER` usando el método `get`. Si no hay un valor establecido para la clave `COUNTER`, se utiliza un valor predeterminado de 0.
-
-```rust
-log!(&env, "count: {}", count);
-```
-
-Esto registra el conteo actual utilizando la macro `log` proporcionada por el Soroban Rust SDK.
-
-```rust
-count += 1;
-```
-
-Esto incrementa el conteo en 1.
-
-```rust
-env.storage().instance().set(&COUNTER, &count);
-```
-
-Esto guarda el conteo actualizado de nuevo en el almacenamiento del contrato utilizando el método `set` en el objeto de almacenamiento.
-
-```rust
-count
-```
-
-Esto devuelve el conteo actualizado al llamador de la función.
-
-```rust
-pub fn get_count(env: Env) -> u32 {}
-```
-
-Esta es una función pública llamada `get_count` que toma una estructura `Env` como argumento y devuelve un `u32`. Una vez más vemos el `Env`, que es el entorno en el que se está ejecutando el contrato, y `u32` como el tipo del valor devuelto por la función.
-
-```rust
-env.storage().instance().get(&COUNTER).unwrap_or(0)
-```
-
-Esta es una repetición del código que vimos anteriormente, que recupera el valor asociado con la clave `COUNTER` del almacenamiento del contrato. Si no hay un valor establecido para la clave `COUNTER`, se utiliza un valor predeterminado de 0. Finalmente, se llama al método `unwrap()` para extraer el valor real del envoltorio `Ok`, que luego se devuelve al llamador de la función.
-
-Ahora que hemos escrito nuestro contrato inteligente, es hora de explorar cómo podemos interactuar con él utilizando el [Stellar CLI](../../../tools/cli/stellar-cli.mdx), una de las muchas robustas [Herramientas para Desarrolladores](../../../tools/developer-tools/README.mdx) disponibles. Esta poderosa herramienta de línea de comandos nos permite interactuar con la Máquina Virtual Soroban desde una máquina local, brindándonos una forma eficiente y flexible de gestionar nuestro contrato inteligente.
-
-### Interaccionar con el Rust Smart Counter
-
-Para interactuar con el contador de Rust, crea una nueva biblioteca de Rust usando el comando cargo new.
-
-```bash
-cargo new --lib increment
-```
-
-Una vez creado el proyecto, reemplaza el archivo `src/lib.rs` con el [ejemplo de código anterior](#writing-a-smart-counter-in-rust).
-
-```rust
-// Remember to replace your lib.rs file with the code example above.
-// This is just a reference to point you in the right direction.
-#[contractimpl]
-impl IncrementContract {...}
-```
-
-Luego, añade las siguientes dependencias al archivo `Cargo.toml`:
-
-```toml
-[package]
-name = "increment"
-version = "0.1.0"
-edition = "2021"
-
-[lib]
-crate-type = ["cdylib"]
-
-[features]
-testutils = ["soroban-sdk/testutils"]
-
-[dependencies]
-soroban-sdk = "20.0.0"
-
-[dev_dependencies]
-soroban-sdk = { version = "20.0.0", features = ["testutils"] }
-
-[profile.release]
-opt-level = "z"
-overflow-checks = true
-debug = 0
-strip = "symbols"
-debug-assertions = false
-panic = "abort"
-codegen-units = 1
-lto = true
-
-[profile.release-with-logs]
-inherits = "release"
-debug-assertions = true
-```
-
-> _Nota_: Para una explicación detallada de la configuración de `Cargo.toml` utilizada en este tutorial, consulta el [Ejemplo Hola Mundo](../../../build/smart-contracts/getting-started/hello-world.mdx).
-
-A continuación, construye el proyecto utilizando el comando `stellar contract build`.
-
-```bash
-cd increment
-stellar contract build
-```
-
-El contrato compilado se ubicará en el directorio `target/wasm32v1-none/release`.
-
-Para interactuar con el contrato, podemos usar el comando `stellar contract invoke` de la herramienta `stellar-cli`. Aquí hay un ejemplo de invocar la función `increment` en un contrato con ID 1:
-
-```bash
-stellar contract invoke \
-    --wasm target/wasm32v1-none/release/increment.wasm \
-    --id 1 \
-    -- \
-    increment
-```
-
-La salida debería ser el valor actual del contador, que en este caso es:
-
-```bash
-1
-```
-
-Puedes utilizar el mismo comando `stellar contract invoke` para incrementar el contador varias veces.
-
-Para obtener el valor actual del contador, puedes usar el siguiente comando:
-
-```bash
-stellar contract invoke \
-    --wasm target/wasm32v1-none/release/increment.wasm \
-    --id 1 \
-    -- \
-    get_count
-```
-
-La salida debería ser el valor actual del contador, suponiendo que el contador se ha incrementado 3 veces, la salida será:
-
-```bash
-3
-```
-
-And that's it! Has aprendido cómo escribir e interactuar con contratos inteligentes simples en Solidity y Rust. En las próximas secciones, aprenderemos sobre conceptos avanzados de contratos inteligentes, las similitudes y diferencias entre Solidity y Rust, y cómo desarrollar y desplegar contratos inteligentes con Soroban.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-support-via-solang.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-support-via-solang.mdx
deleted file mode 100644
index 2d9e3f782e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/evm/solidity-support-via-solang.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-sidebar_position: 4
-title: Admitir Solidity mediante Solang
-description: Compilar contratos Solidity a Wasm para Stellar usando el compilador Solang.
----
-
-Aprovecha el compilador Hyperledger Solang para compilar contratos Solidity a Soroban.
-
-- Aprende sobre el SDK de Solidity y enlaces a Solang en Herramientas: [SDKs de Contratos](../../../tools/sdks/contract-sdks.mdx)
-- Documentación de Solang (objetivo Soroban): https://solang.readthedocs.io/en/latest/targets/soroban.html
-- Repositorio de Solang y ejemplos: https://github.com/hyperledger/solang/tree/main/examples/soroban
-- IDE Web de Solang: https://solang.io/
-
-:::caution
-
-La admitancia de Solidity mediante Solang para Stellar es experimental y está en evolución. No todas las funcionalidades de Solidity están admitidas aún, y pueden ocurrir cambios incompatibles. No recomendamos usar Solang para contratos en producción en este momento.
-
-:::
-
-- La forma más sencilla de usar Solang es mediante el IDE Web, pero también puedes construir Solang desde el código fuente o usar binarios precompilados.
-- Para despliegue e interacción, usa el CLI de Stellar y los SDKs cliente después de compilar tu artefacto Wasm.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/near.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/near.mdx
deleted file mode 100644
index 4dc198d451..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/near.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-sidebar_position: 40
-title: Cerca
-description: Migra tu código de contrato inteligente de Near a Soroban
-draft: true
----
-
-No lo sé, ¿como copiar/pegar?
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/solana.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/solana.mdx
deleted file mode 100644
index 013a26961d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/learn/migrate/solana.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
----
-sidebar_position: 20
-title: Solana
-description: Migra tu código de contrato inteligente de Solana a Soroban
-draft: true
----
-
-No sé, ¿como copiar/pegarlo?
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/networks/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/networks/README.mdx
deleted file mode 100644
index 61fa5bd8a2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/networks/README.mdx
+++ /dev/null
@@ -1,140 +0,0 @@
----
-sidebar_position: 20
-sidebar_label: Resumen de redes
-title: "Explorar Mainnet, Testnet y Futurenet: Roles, Casos de Uso y Conectividad"
-description: Explora las diferentes redes, incluyendo Mainnet, Testnet y Futurenet. Aprende sus roles, casos de uso y cómo conectarte para desarrollo y pruebas.
----
-
-# Redes
-
-Stellar tiene tres redes: la red pública (Mainnet, también llamada Pubnet o la Red Pública), la red de prueba (Testnet) y una red de desarrollo (Futurenet).
-
-- **Mainnet** es la red principal usada por las aplicaciones en producción. Se conecta a redes financieras reales y requiere XLM para cubrir saldos mínimos, tarifas de transacción y alquiler.
-- **Testnet** es una red más pequeña, gratuita y mantenida por SDF que funciona igual que Mainnet pero no se conecta a dinero real. Se restablece periódicamente, siendo el mejor lugar para que los desarrolladores prueben aplicaciones en un entorno estable que refleja la funcionalidad de Mainnet.
-- **Futurenet** es una red de desarrollo para probar funciones de vanguardia. Se restablece cuando es necesario, por lo que es menos predecible que Testnet, pero es donde se introducen nuevas funciones antes de los lanzamientos estables.
-
-## Comparación de redes
-
-| Característica                                              | Mainnet                                                                                                                                                                         | Testnet                                                                                                                                                                                                                                                                                               | Futurenet                                                                                                                                                                                                     |
-| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Propósito**                                               | Red de producción                                                                                                                                                               | Entorno de prueba estable                                                                                                                                                                                                                                                                             | Pruebas de funciones de vanguardia                                                                                                                                                                            |
-| **Frase de paso de red**                                    | `Red Global Pública de Stellar ; Septiembre 2015`                                                                                                                               | `Red SDF de Prueba ; Septiembre 2015`                                                                                                                                                                                                                                                                 | `Red Futura de SDF de Prueba ; Octubre 2022`                                                                                                                                                                  |
-| **ID de red**                                               | <code style={{overflowWrap:'anywhere'}}>7ac33997544e3175d266bd022439b22cdb16508c01163f26e5cb2a3e1045a979</code>                                                                 | <code style={{overflowWrap:'anywhere'}}>cee0302d59844d32bdca915c8203dd44b33fbb7edc19051ea37abedf28ecd472</code>                                                                                                                                                                                       | <code style={{overflowWrap:'anywhere'}}>a3a1c6a78286713e29be0e9785670fa838d13917cd8eaeb4a3579ff1debc7fd5</code>                                                                                               |
-| **Nodos validadores**                                       | Operados por el público                                                                                                                                                         | SDF opera tres nodos validadores principales                                                                                                                                                                                                                                                          | SDF opera nodos validadores principales                                                                                                                                                                       |
-| **Validador**                                               | `core-live-a.stellar.org` `core-live-b.stellar.org` `core-live-c.stellar.org`                                                                                                   | `core-live-testnet.stellar.org`                                                                                                                                                                                                                                                                       | `core-live-futurenet.stellar.org`                                                                                                                                                                             |
-| **Financiación**                                            | Se requiere XLM real desde otra cuenta                                                                                                                                          | Gratis mediante Friendbot                                                                                                                                                                                                                                                                             | Gratis mediante Friendbot                                                                                                                                                                                     |
-| **API Horizon**                                             | [Varios proveedores disponibles](../data/apis/horizon/providers.mdx)                                                                                                            | https://horizon-testnet.stellar.org                                                                                                                                                                                                                                                                   | https://horizon-futurenet.stellar.org                                                                                                                                                                         |
-| **RPC de Stellar**                                          | [Solo proveedores externos](../data/apis/rpc/providers.mdx)                                                                                                                     | `https://soroban-testnet.stellar.org`                                                                                                                                                                                                                                                                 | `https://rpc-futurenet.stellar.org`                                                                                                                                                                           |
-| **Operaciones por libro mayor**                             | 1,000                                                                                                                                                                           | 100                                                                                                                                                                                                                                                                                                   | 100                                                                                                                                                                                                           |
-| **Transacciones de contratos inteligentes por libro mayor** | Máximo 100\*                                                                                                                                                                    | 1                                                                                                                                                                                                                                                                                                     | 1                                                                                                                                                                                                             |
-| **Reinicios de red**                                        | Nunca                                                                                                                                                                           | Cadencia regular                                                                                                                                                                                                                                                                                      | Cuando es necesario (impredecible)                                                                                                                                                                            |
-| **Friendbot disponible**                                    | No                                                                                                                                                                              | Sí (10,000 XLM)                                                                                                                                                                                                                                                                                       | Sí (10,000 XLM)                                                                                                                                                                                               |
-| **API Friendbot**                                           | N/A                                                                                                                                                                             | `https://friendbot.stellar.org`                                                                                                                                                                                                                                                                       | `https://friendbot-futurenet.stellar.org`                                                                                                                                                                     |
-| **Archivo de historial**                                    | `http://history.stellar.org/prd/core-live/core_live_001/`, `http://history.stellar.org/prd/core-live/core_live_002/`, `http://history.stellar.org/prd/core-live/core_live_003/` | `http://history.stellar.org/prd/core-testnet/core_testnet_001`, `http://history.stellar.org/prd/core-testnet/core_testnet_002`, `http://history.stellar.org/prd/core-testnet/core_testnet_003` ([más información](https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_testnet.cfg)) | `http://history.stellar.org/dev/core-futurenet/core_futurenet_001/`, `http://history.stellar.org/dev/core-futurenet/core_futurenet_002/`, `http://history.stellar.org/dev/core-futurenet/core_futurenet_003/` |
-
-\*La cantidad precisa puede variar según los [límites de recursos](../learn/fundamentals/fees-resource-limits-metering.mdx#resource-limitations). Consulta [Tarifas y Medición](../learn/fundamentals/fees-resource-limits-metering.mdx) para detalles sobre la configuración de contratos inteligentes en la red.
-
-## Friendbot
-
-Friendbot es un bot que financia cuentas y contratos con XLM falso en Testnet o Futurenet. Puedes solicitar XLM a Friendbot usando el [Stellar Lab](../tools/lab/account.mdx#fund-account) o con varios SDKs.
-
-**Detalles clave:**
-
-- Las solicitudes tienen límite de frecuencia, úsalo con prudencia
-- Proporciona 10,000 XLM falsos al fundar una cuenta nueva
-- Puede financiar tanto direcciones de cuentas (G...) como direcciones de contratos (C...)
-- Para varias cuentas: financia la primera con Friendbot y luego usa esa cuenta para financiar las siguientes mediante la operación Crear Cuenta
-
-## Comenzar
-
-**Para producción:** Usa Mainnet con XLM real e infraestructura lista para producción.
-
-**Para pruebas:** Usa Testnet para desarrollo y pruebas estables que reflejan el comportamiento de producción.
-
-**Para funciones experimentales:** Usa Futurenet para probar las últimas funciones antes de su lanzamiento.
-
-## Reinicio de datos en Testnet y Futurenet
-
-Testnet y Futurenet se reinician periódicamente al libro mayor de génesis para limpiar la red, eliminar spam, reducir el tiempo requerido para ponerse al día con el último libro mayor, y ayudar a mantener el sistema. Los reinicios borran todas las entradas del libro mayor (cuentas, líneas de confianza, ofertas, datos de contratos inteligentes, etc.), transacciones y datos históricos de Stellar Core, Horizon y Stellar RPC, por lo que los desarrolladores no deben confiar en la persistencia de cuentas o el estado de los saldos cuando usan Testnet o Futurenet.
-
-Los reinicios de Futurenet ocurren con menos regularidad que los de Testnet y no tienen un horario fijo.
-
-Los reinicios típicos de Testnet ocurren una vez por trimestre a las 17:00 UTC y se anuncian con al menos dos semanas de antelación en el [Panel de Stellar](http://dashboard.stellar.org/) y mediante varios canales de la comunidad de desarrolladores.
-
-Estas son las fechas programadas para 2025:
-
-- 19 de marzo de 2025
-- 18 de junio de 2025
-- 14 de agosto de 2025
-- 17 de diciembre de 2025
-
-Si ejecutas una instancia de Horizon para Testnet o Futurenet, debes volver a unirte y sincronizarte con la red después de un reinicio. Consulta cómo hacerlo aquí: [Reinicio de Testnet](https://github.com/stellar/packages/blob/master/docs/testnet-reset.md).
-
-Consulta [esta guía práctica](../build/guides/basics/automate-reset-data.mdx) para automatizar el reinicio de datos en Testnet y Futurenet.
-
-## Automatización de datos de prueba
-
-Se recomienda tener infraestructura de prueba que pueda repoblar Testnet y Futurenet con datos útiles después de un reinicio. Esto hará que las pruebas sean más confiables y te ayudará a escalar tu infraestructura de prueba a una red privada si decides hacerlo. Por ejemplo, podrías:
-
-- Generar emisores de activos para probar el desarrollo de una billetera;
-- Crear órdenes en el libro de órdenes (tanto actuales como históricas) para probar el desarrollo de un cliente de trading;
-- Recrear pools de liquidez;
-- Reimplementar contratos inteligentes.
-
-Si mantienes una aplicación, deberías pensar en crear un conjunto de datos lo suficientemente representativo para probar tus casos de uso principales y permitir pruebas robustas incluso cuando Testnet o Futurenet no estén disponibles.
-
-Un script puede automatizar todo este proceso creando una cuenta con Friendbot y enviando un conjunto de transacciones que forman parte de tu infraestructura de prueba.
-
-## Frases de paso de red
-
-Cada una de las redes de Stellar, Mainnet, Testnet y Futurenet, tiene su propia frase de paso única. Se usan al validar firmas en una transacción determinada. Si firmas una transacción para una red pero la envías a otra, esta no será considerada válida. Por convención, el formato de una frase de paso es ‘`[Nombre de la Red] ; [Mes de Creación] [Año de Creación]`’.
-
-Las frases de contraseña para Stellar Mainnet, Testnet y Futurenet son:
-
-- Mainnet: '`Public Global Stellar Network ; September 2015`'
-- Testnet: '`Test SDF Network ; September 2015`'
-- Futurenet: '`Test SDF Future Network ; October 2022`'
-
-Las frases de paso tienen dos propósitos principales: (1) se usan como semilla para la cuenta raíz (clave maestra de la red) en el génesis y (2) se usan para construir los hashes de transacciones, que son los que se firman finalmente con la clave secreta de cada firmante en un sobre de transacción; esto permite verificar que una transacción fue destinada para una red específica por sus firmantes.
-
-Muchos SDKs tienen las frases de paso codificadas para las redes de Stellar. Si ejecutas una red privada, tendrás que pasar manualmente una frase de paso para que se use al generar hashes de transacciones. Todos los SDKs oficiales de Stellar permiten usar una red con una frase de paso personalizada.
-
-## IDs de red
-
-Cada red Stellar también tiene un ID de red, que es el hash SHA-256 de la frase de contraseña de la red. El ID de red se utiliza para la firma de transacciones y la generación de direcciones de contrato y asegura que los hashes e IDs generados sean diferentes en cada red.
-
-Los IDs para Stellar Mainnet, Testnet y Futurenet son:
-
-| Red       | ID de red                                                          |
-| --------- | ------------------------------------------------------------------ |
-| Mainnet   | `7ac33997544e3175d266bd022439b22cdb16508c01163f26e5cb2a3e1045a979` |
-| Testnet   | `cee0302d59844d32bdca915c8203dd44b33fbb7edc19051ea37abedf28ecd472` |
-| Futurenet | `a3a1c6a78286713e29be0e9785670fa838d13917cd8eaeb4a3579ff1debc7fd5` |
-
-## Para qué deben y no deben usarse Testnet y Futurenet
-
-### Testnet y Futurenet son adecuadas para
-
-- Crear cuentas de prueba (con financiamiento de Friendbot);
-- Desarrollar aplicaciones y contratos y explorar tutoriales en Stellar sin riesgo de perder activos;
-- Probar aplicaciones existentes con nuevas versiones o candidatas de lanzamiento de Stellar Core, Horizon y Stellar RPC;
-- Realizar análisis de datos en conjuntos de datos menores pero significativos en comparación con Mainnet.
-
-### Testnet y Futurenet no son adecuadas para
-
-- Pruebas de carga y estrés;
-- Infraestructura de prueba con alta disponibilidad – SDF no garantiza la disponibilidad de Testnet;
-- Almacenamiento de datos a largo plazo en la red debido a que la red se reinicia periódicamente;
-- Infraestructura de prueba que requiera mayor control sobre el entorno de prueba, como:
-  - La capacidad de controlar la frecuencia de reinicio de datos;
-  - La necesidad de proteger datos privados o sensibles (antes de lanzar en Mainnet). Siempre puedes ejecutar tu propia red de prueba para casos de uso que no funcionan bien con Testnet de SDF.
-
-## Mover tu proyecto de Testnet o Futurenet a producción
-
-Mainnet, Testnet y Futurenet tienen cada uno su propia frase de paso única, que se usa para validar firmas en una transacción dada.
-
-Consulta las secciones anteriores para la frase de contraseña de cada red.
-
-Para aplicaciones que no dependen del estado de la red (como que existan cuentas específicas), se pasa a producción cambiando la frase de paso de la red y asegurando que tu instancia de Horizon esté conectada a Mainnet.
-
-Si ejecutas una instancia de Stellar Core o Horizon contra Testnet y quieres cambiar a producción, cambiar la frase de paso requerirá que ambas bases de datos se reinicien completamente. Si ejecutas tu propio RPC en Testnet o Futurenet, puede que quieras usar un servicio RPC cuando pases a Mainnet. Consulta los proveedores del servicio RPC [aquí](../data/apis/rpc/providers.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/networks/resource-limits-fees.mdx b/i18n/es/docusaurus-plugin-content-docs/current/networks/resource-limits-fees.mdx
deleted file mode 100644
index 61bb4677cc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/networks/resource-limits-fees.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-sidebar_position: 30
-title: Límites de Recursos y Tarifas
----
-
-## Límites de Recursos
-
-:::note
-
-Las limitaciones y tarifas de recursos solo se aplican a las transacciones de contratos inteligentes. Lee más sobre el funcionamiento interno de las tarifas en Stellar en la [sección de Tarifas](../learn/fundamentals/fees-resource-limits-metering.mdx).
-
-:::
-
-### Límites por transacción
-
-Estos definen la cantidad máxima de trabajo que puede realizar una sola transacción de Smart contract.
-
-| Configuración de la Red                                                                 | Valor               |
-| --------------------------------------------------------------------------------------- | ------------------- |
-| Instrucciones máximas de CPU                                                            | 100 millones        |
-| Memoria máxima (RAM)                                                                    | 40 MB               |
-| Número máximo de claves en la huella                                                    | 100                 |
-| Lecturas de disco\*                                                                     | 100 entradas/200 KB |
-| Escrituras de disco                                                                     | 50 entradas/132 KB  |
-| Tamaño de la transacción                                                                | 132 KB              |
-| Tamaño de bytes de eventos + valor de retorno                                           | 16 KB               |
-| Tamaño de la clave del libro mayor individual (clave de almacenamiento de contrato)     | 250 bytes           |
-| Tamaño de la entrada del libro mayor individual (incluyendo entradas de Wasm)           | 128 KiB             |
-
-\* La mayoría de las transacciones no realizan lecturas de disco, ya que solo se consideran lecturas de disco las entradas archivadas y las entradas 'clásicas' (cuentas G, trustlines). El estado del smart contract En vivo está en memoria y no se cuenta para este límite.
-
-### Parámetros de extensión TTL
-
-Estos definen los parámetros de extensión TTL.
-
-| Configuración de la Red                            | Valor    |
-| -------------------------------------------------- | -------- |
-| TTL de entrada persistente al crearla              | 120 días |
-| TTL de entrada temporal al crearla                 | 1 día    |
-| Extensión máxima del TTL de entrada en el ledger   | 6 meses  |
-
-### Límites en todo el ledger
-
-Estos definen la cantidad máxima de trabajo realizado por todas las transacciones en un solo ledger (bloque único).
-
-| Configuración de red                              | Valor                 |
-| ------------------------------------------------- | --------------------- |
-| Máximo de instrucciones CPU                       | 600 millones          |
-| Máximo de memoria (RAM)                           | sin límite explícito  |
-| Número máximo de claves en el footprint           | sin límite explícito  |
-| Lecturas de disco                                 | 1000 entradas/7 MB    |
-| Escrituras de disco                               | 500 entradas/143 KB   |
-| Tamaño de las transacciones                       | 133 KB                |
-| Eventos+tamaño del valor de retorno en bytes      | sin límite explícito  |
-
-## Tarifas de Recursos
-
-| Configuración de red                                       | Costo (stroops)            |
-| :--------------------------------------------------------- | :------------------------- |
-| 10,000 instrucciones CPU                                   | 25 (250.000/max tx)        |
-| Leer 1 entrada del ledger desde disco                      | 6,250 (625,000/máx. tx)    |
-| Leer 1KB desde disco                                       | 1,786 (357,200/máx. tx)    |
-| Escribir 1 entrada del ledger                              | 10,000 (500,000/máx. tx)   |
-| Escribir 1KB en disco                                      | 3,500 (462,000/máx. tx)    |
-| 1KB de tamaño de transacción (ancho de banda)              | 1,624 (214,368/máx. tx)    |
-| 1KB de tamaño de transacción (historia)                    | 16,235 (2,143,020/máx. tx) |
-| 1KB de Eventos/valor de retorno                            | 10,000 (160,000/máx. tx)   |
-| 30 días de alquiler por 1 KB de almacenamiento persistente | ~427,000                   |
-| 30 días de alquiler por 1 KB de almacenamiento temporal    | ~213,500                   |
-
-Ten en cuenta que las tarifas de renta indicadas aquí pueden aumentar si se escribe mucha información de contratos en el ledger en un corto periodo. Esto sucede porque las tarifas de renta están diseñadas de tal manera que, cuanto más se acerque el tamaño del estado a un umbral definido por el validador, más costoso será escribir nuevos datos o extender los TTL.
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
deleted file mode 100644
index 0b946e6a88..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx
+++ /dev/null
@@ -1,1939 +0,0 @@
----
-sidebar_position: 20
-title: Versiones de software
-description: Publicaciones de software Soroban y registros de cambios.
----
-
-:::caution
-
-Las versiones candidatas son publicaciones de software que también se lanzan a la red de prueba [Testnet]. Las publicaciones de software pueden ocurrir entre lanzamientos de Testnet. Si interactúas con Testnet, las versiones de software recomendadas para usar en desarrollo se proporcionan a continuación. Las publicaciones a Testnet pueden incluir reinicios de red y cambios en la frase secreta de red.
-
-:::
-
-[testnet]: ./README.mdx
-
-## Protocolo 24 (Mainnet, 22 de octubre de 2025)
-
-### Software
-
-| Software                                  | Versión                                           |
-| ----------------------------------------- | ------------------------------------------------- |
-| XDR                                       | `v24.0`                                           |
-| Rust XDR                                  | `24.0.1`                                          |
-| Entorno de host de contratos inteligentes | `24.0.0`                                          |
-| Stellar Core                              | `24.0.0`                                          |
-| SDK de Rust para Contratos Inteligentes   | `23.0.3`                                          |
-| CLI de Stellar                            | `23.1.4`                                          |
-| Stellar RPC                               | `v24.0.0`                                         |
-| Horizonte de Stellar                      | `v24.0.0`                                         |
-| Stellar Galexie                           | `v24.0.0`                                         |
-| Inicio rápido de Stellar                  | `docker pull stellar/quickstart`                  |
-| Base Stellar JS                           | `v14.0.0`                                         |
-| SDK de Stellar JS                         | `v14.3.0`                                         |
-| Cliente Stellar Horizon y TxnBuild        | `v24.0.0`                                         |
-| Cliente RPC Stellar                       | `v24.0.0`                                         |
-| Freighter                                 |                                                   |
-| Laboratorio                               | `N/A`                                             |
-| Frase secreta de la red Futurenet         | `Test SDF Future Network ; octubre 2022`          |
-| Frase secreta de la red Testnet           | `Test SDF Network ; septiembre 2015`              |
-| Frase secreta de la red Mainnet           | `Public Global Stellar Network ; septiembre 2015` |
-
-### Notas de publicación
-
-El Protocolo 24 es una actualización de estabilidad tras Whisk (Protocolo 23). Lee más sobre la actualización aquí:
-
-- [Notas de publicación](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0076.md)
-- [Actualización de Estabilidad tras Whisk](https://stellar.org/blog/developers/addressing-state-archival-inconsistencies-protocol-upgrade-vote-next-week)
-
-## Protocolo 24 (Testnet, 21 de octubre de 2025)
-
-### Software
-
-| Software                               | Versión                                           |
-| -------------------------------------- | ------------------------------------------------- |
-| XDR                                    | `v24.0`                                           |
-| Rust XDR                               | `24.0.1`                                          |
-| Entorno host para contrato inteligente | `23.0.0`                                          |
-| Stellar Core                           | `24.0.0`                                          |
-| SDK Rust para contrato inteligente     | `23.0.3`                                          |
-| CLI de Stellar                         | `23.1.4`                                          |
-| Stellar RPC                            | `v24.0.0`                                         |
-| Horizonte de Stellar                   | `v24.0.0`                                         |
-| Stellar Galexie                        | `v24.0.0`                                         |
-| Inicio rápido de Stellar               | `docker pull stellar/quickstart`                  |
-| Base Stellar JS                        | `v14.0.0`                                         |
-| SDK de Stellar JS                      | `v14.3.0`                                         |
-| Cliente Stellar Horizon y TxnBuild     | `v24.0.0`                                         |
-| Cliente RPC de Stellar                 | `v24.0.0`                                         |
-| Freighter                              |                                                   |
-| Laboratorio                            | `N/A`                                             |
-| Frase secreta de la red Futurenet      | `Test SDF Future Network ; octubre 2022`          |
-| Frase secreta de la red Testnet        | `Test SDF Network ; septiembre 2015`              |
-| Frase secreta de la red Mainnet        | `Public Global Stellar Network ; septiembre 2015` |
-
-### Notas de publicación
-
-El protocolo 24 es una actualización de estabilidad tras Whisk (Protocolo 23). Lee más sobre la actualización aquí:
-
-- [Actualización de estabilidad después de Whisk](https://stellar.org/blog/developers/addressing-state-archival-inconsistencies-protocol-upgrade-vote-next-week)
-
-## Whisk, Protocolo 23 (Mainnet, 3 de septiembre de 2025)
-
-### Software
-
-| Software                                | Versión                                           |
-| --------------------------------------- | ------------------------------------------------- |
-| XDR                                     | `v23.0`                                           |
-| Rust XDR                                | `v23.0.0`                                         |
-| Entorno de Ejecución del Smart Contract | `v23.0.2`                                         |
-| Stellar Core                            | `v23.0.1`                                         |
-| SDK de Rust para Smart Contract         | `v23.0.2`                                         |
-| Stellar CLI                             | `v23.1.1`                                         |
-| Stellar RPC                             | `v23.0.2`                                         |
-| Horizonte de Stellar                    | `v23.0.0`                                         |
-| Stellar Galexie                         | `v23.0.0`                                         |
-| Inicio rápido de Stellar                | `docker pull stellar/quickstart`                  |
-| Base Stellar JS                         | `v14.0.0`                                         |
-| SDK de Stellar JS                       | `v14.1.1`                                         |
-| Cliente de Stellar Horizon y TxnBuild   | `v23.0.0`                                         |
-| Cliente RPC Rust Stellar                | `v23.0.0`                                         |
-| Freighter                               | `v5.34.1`                                         |
-| Laboratorio                             | `N/A`                                             |
-| Frase secreta de la red Futurenet       | `Test SDF Future Network ; octubre 2022`          |
-| Frase secreta de la red Testnet         | `Test SDF Network ; septiembre 2015`              |
-| Frase secreta de la red Mainnet         | `Public Global Stellar Network ; septiembre 2015` |
-
-### Notas de publicación
-
-Nuevas características en Whisk, Protocolo 23:
-
-- [Notas de publicación](https://github.com/stellar/stellar-core/releases/tag/v23.0.1)
-- Eventos unificados: [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-- Archivado de estado: [CAP-62](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md) e [CAP-66](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md)
-
-## Protocolo 23 (Testnet, 14 de agosto de 2025)
-
-### Software
-
-| Software                                | Versión                                              |
-| --------------------------------------- | ---------------------------------------------------- |
-| XDR                                     | `v23.0`                                              |
-| XDR de Rust                             | `23.0.0`                                             |
-| Entorno host de contrato inteligente    | `23.0.0`                                             |
-| Stellar Core                            | `23.0.0`                                             |
-| SDK de Rust para contratos inteligentes | `23.0.0-rc.2.4`                                      |
-| CLI de Stellar                          | `23.0.1`                                             |
-| Stellar RPC                             | `v23.0.0`                                            |
-| Stellar Horizon                         | `v23.0.0`                                            |
-| Stellar Galexie                         | `v23.0.0`                                            |
-| Inicio rápido de Stellar                | `docker pull stellar/quickstart`                     |
-| Stellar JS Stellar Base                 | `v14.0.0`                                            |
-| Stellar JS Stellar SDK                  | `v14.0.0`                                            |
-| Cliente Stellar Horizon y TxnBuild      | `v23.0.0`                                            |
-| Cliente Stellar RPC                     | `v23.0.0`                                            |
-| Freighter                               |                                                      |
-| Laboratorio                             | `N/A`                                                |
-| Frase de red de Futurenet               | `Test SDF Future Network ; octubre de 2022`          |
-| Frase de red de Testnet                 | `Test SDF Network ; septiembre de 2015`              |
-| Frase de red de Mainnet                 | `Public Global Stellar Network ; septiembre de 2015` |
-
-### Notas de publicación
-
-Nuevas funciones en Whisk, Protocolo 23:
-
-- [Notas de publicación](https://github.com/stellar/stellar-core/releases/tag/v23.0.0rc4)
-- Eventos Unificados: [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-- Archivado de Estado: [CAP-62](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md) e [CAP-66](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md)
-
-## Whisk, versión candidata del Protocolo 23 (solo Testnet, 17 de julio de 2025)
-
-### Software
-
-| Software                     | Versión         | Paquete                                                                                                |
-| ---------------------------- | --------------- | ------------------------------------------------------------------------------------------------------ |
-| XDR                          | `v23.0`         | `n/a`                                                                                                  |
-| Rust XDR                     | `23.0.0-rc.2`   | `rust crate: stellar-xdr:23.0.0-rc.2`                                                                  |
-| Entorno host de Stellar Rust | `23.0.0-rc.2`   | `rust crate: soroban-env-host:23.0.0-rc.2.1`                                                           |
-| Stellar Core                 | `23.0.0rc4`     | `debian: stellar-core:23.0.0-2587.rc4`                                                                 |
-| SDK Stellar Rust             | `23.0.0-rc.2.2` | `rust crate: soroban-sdk:23.0.0-rc.2.1`                                                                |
-| Stellar CLI                  | `23.0.0`        | `rust crate: stellar-cli:23.0.0`                                                                       |
-| RPC de Stellar               | `v23.0.0-rc.2`  | `debian: stellar-rpc:23.0.0~rc2-127`                                                                   |
-| Stellar Horizon              | `v23.0.0-rc2`   | `debian: stellar-horizon:23.0.0~rc2-508`                                                               |
-| Inicio rápido de Stellar     | `main`          | `docker.io/stellar/quickstart:sha256:d4f752eece1e8780d19f4bd2726845996c413c0f4c4f57d1e4a9ff450442fc29` |
-| Stellar JS Stellar Base      | `v14.0.0-rc.2`  | `NPM: 14.0.0-rc.2`                                                                                     |
-| Stellar JS Stellar SDK       | `v14.0.0-rc.3`  | `NPM: 14.0.0-rc.3`                                                                                     |
-| Freighter                    | `n/a`           | `n/a`                                                                                                  |
-| Laboratorio                  | `n/a`           | `n/a`                                                                                                  |
-| Frase de red de Futurenet    | `n/a`           | `Test SDF Future Network ; octubre de 2022`                                                            |
-| Frase de red de Testnet      | `n/a`           | `Test SDF Network ; septiembre de 2015`                                                                |
-| Frase de red de Mainnet      | `n/a`           | `Public Global Stellar Network ; septiembre de 2015`                                                   |
-
-### Notas de publicación
-
-Nuevas características en Whisk, Protocolo 23:
-
-- [Notas de publicación](https://github.com/stellar/stellar-core/releases/tag/v23.0.0rc4)
-- Eventos Unificados: [CAP-67](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0067.md)
-- Archivado del Estado: [CAP-62](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0062.md) y [CAP-66](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0066.md)
-
-## Protocolo 22 (Mainnet, 5 de diciembre de 2024)
-
-### Software
-
-| Software                     | Versión                                                                                                            |
-| ---------------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| XDR                          | `v22.0`                                                                                                            |
-| Rust XDR                     | `v22.0.0`                                                                                                          |
-| Entorno Soroban              | `v22.1.2`                                                                                                          |
-| Stellar Core                 | `v22.0.0`                                                                                                          |
-| SDK de Rust Soroban          | `v22.0.3`                                                                                                          |
-| CLI de Stellar               | `v22.0.1`                                                                                                          |
-| Stellar RPC                  | `v22.1.0`                                                                                                          |
-| Stellar Horizon              | `v22.0.1`                                                                                                          |
-| Inicio rápido de Stellar     | `docker.io/stellar/quickstart:v455-latest@sha256:bbd4cea64c5428381ac5ace7c380ed7c3b72f12488aeb1f1bf19c48e74244af8` |
-| Stellar JS Stellar Base      | `v13.0.1`                                                                                                          |
-| Stellar JS Stellar SDK       | `v13.1.0`                                                                                                          |
-| Freighter                    |                                                                                                                    |
-| Laboratorio                  |                                                                                                                    |
-| Futurenet Network Passphrase | `Test SDF Future Network ; October 2022`                                                                           |
-| Testnet Network Passphrase   | `Test SDF Network ; September 2015`                                                                                |
-| Mainnet Network Passphrase   | `Public Global Stellar Network ; September 2015`                                                                   |
-
-### Notas de publicación
-
-#### Núcleo
-
-Nuevas funcionalidades en el Protocolo 22:
-
-- Soporte para constructores en Soroban: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0058.md.
-- Funciones host de Soroban para BLS12-381: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0059.md.
-
-#### SDK de Rust Soroban
-
-Cambios clave relacionados con el protocolo:
-
-- Soporte para constructores
-- Soporte para funciones host BLS12-381
-
-#### CLI de Stellar (anteriormente CLI de Soroban)
-
-## Protocolo 21 (Mainnet, 18 de junio de 2024)
-
-### Software
-
-| Software                         | Version                                                                                                                                             |
-| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                              | `v21.1`                                                                                                                                             |
-| Rust XDR                         | `v21.0.1`                                                                                                                                           |
-| Entorno Soroban                  | `v21.0.2`                                                                                                                                           |
-| Stellar Core                     | `v21.0.0`                                                                                                                                           |
-| SDK de Rust Soroban              | `21.0.1-preview.3`                                                                                                                                  |
-| Stellar CLI                      | `v21.0.0`                                                                                                                                           |
-| RPC de Soroban                   | `v21.3.0`                                                                                                                                           |
-| Stellar Horizon                  | `v2.30.0`                                                                                                                                           |
-| Stellar Quickstart               | `https://hub.docker.com/layers/stellar/quickstart/v426-latest-amd64/images/sha256-274395daab6fa8033b9213f152d56699358917fb01d7c7e95392a37fc00c9d01` |
-| Stellar JS Stellar Base          | `v12.0.0-rc1`                                                                                                                                       |
-| Stellar JS Stellar SDK           | `v12.1.0`                                                                                                                                           |
-| Freighter                        |                                                                                                                                                     |
-| Laboratorio                      |                                                                                                                                                     |
-| dapp de pago de React de Soroban | `TBD`                                                                                                                                               |
-| dapp de token Mint de Soroban    | `TBD`                                                                                                                                               |
-| dapp de token Swap de Soroban    | `TBD`                                                                                                                                               |
-| Futurenet Network Passphrase     | `Test SDF Future Network ; October 2022`                                                                                                            |
-| Testnet Network Passphrase       | `Test SDF Network ; September 2015`                                                                                                                 |
-| Mainnet Network Passphrase       | `Public Global Stellar Network ; September 2015`                                                                                                    |
-
-### Notas de publicación
-
-#### Núcleo
-
-Nuevas funcionalidades en el Protocolo 21:
-
-- Soporte secp256r1 en el host Soroban: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md
-- Función host de Soroban para extender TTL de la instancia del contrato y el código por separado: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md
-- Usar un modelo de costo refinado para la instanciación de VM para reducir los costos de medición de la instanciación de VM: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0054.md
-- Caching en el módulo VM intra-transacción para una posterior reducción de costos de Soroban: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0055.md, https://github.com/stellar/stellar-protocol/blob/master/core/cap-0056.md
-
-#### SDK de Rust Soroban
-
-Cambios clave relacionados con el protocolo:
-
-- Soporte para verificación de firmas secp256r1
-- Soporte para extender TTL de la instancia del contrato y el código por separado
-
-#### CLI de Stellar (anteriormente CLI de Soroban)
-
-Nota: la CLI de Soroban se ha renombrado a CLI de Stellar.
-
-- Añadir el paquete stellar-cli junto a soroban-cli
-- Agregar crate stellar-cli junto a soroban-cli
-- Renombrar a stellar-cli
-- Actualizar los términos para usar stellar en lugar de soroban
-- Actualizar los términos para usar stellar en lugar de soroban
-- Actualizar otras referencias a stellar-cli
-- Agregar soporte para el nombre del alias del id del contrato al desplegar e invocar contratos
-- Extraer la lógica del alias en su propia implementación
-- Incorporar la lista de contratos de ejemplos en la fuente y eliminarla del script de construcción
-- Agregar subcomandos de caché y permitir el registro adecuado de datos de transacción
-- Añadir opción sin-compilación para fee::Args
-- No agregar automáticamente la cuenta de prueba a las claves
-- Salida de TransactionEnvelope en lugar de Transaction para --build-only
-- Firma de ledger
-- Usar desenvuelto seguro en la opción unwrap
-- Excluir funciones solo de host del cliente
-- Agregar cmd de seguimiento de registro de contenedor
-- Actualizar el comando de inicio del contenedor de red para usar banderas de habilitación actualizadas
-- Agregar libudev-dev como dependencia
-- Aumentar versiones de dependencias
-- Actualizar a la versión más reciente de soroban-rpc y copiar la antigua lógica de firma
-- Eliminar el comando de token de laboratorio obsoleto
-- Eliminar el comando de configuración obsoleto
-- Eliminar el comando de xdr de laboratorio
-- Agregar comando xdr a la raíz
-
-## Protocolo 21 (Testnet solo, 20 de mayo de 2024)
-
-### Software
-
-| Software                         | Versión                                                                                                                                             |
-| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                              | `v21.1`                                                                                                                                             |
-| Rust XDR                         | `v21.0.1`                                                                                                                                           |
-| Entorno Soroban                  | `v21.0.2`                                                                                                                                           |
-| Stellar Core                     | `v21.0.0`                                                                                                                                           |
-| SDK de Rust Soroban              | `21.0.1-preview.3`                                                                                                                                  |
-| CLI de Stellar                   | `v21.0.0`                                                                                                                                           |
-| RPC de Soroban                   | `v21.2.0`                                                                                                                                           |
-| Stellar Horizon                  | `v2.30.0`                                                                                                                                           |
-| Stellar Quickstart               | `https://hub.docker.com/layers/stellar/quickstart/v426-latest-amd64/images/sha256-274395daab6fa8033b9213f152d56699358917fb01d7c7e95392a37fc00c9d01` |
-| Stellar JS Stellar Base          | `v12.0.0-rc1`                                                                                                                                       |
-| Stellar JS Stellar SDK           | `v12.0.0-rc.3`                                                                                                                                      |
-| Freighter                        |                                                                                                                                                     |
-| Laboratorio                      |                                                                                                                                                     |
-| dapp de pago de React de Soroban | `TBD`                                                                                                                                               |
-| dapp de token Mint de Soroban    | `TBD`                                                                                                                                               |
-| dapp de token Swap de Soroban    | `TBD`                                                                                                                                               |
-| Frase de red de Futurenet        | `Test SDF Future Network ; octubre 2022`                                                                                                            |
-| Frase de red de Testnet          | `Test SDF Network ; septiembre 2015`                                                                                                                |
-| Frase de paso de la red Mainnet  | `Red pública global Stellar; septiembre de 2015`                                                                                                    |
-
-### Notas de publicación
-
-#### Núcleo
-
-Esta es la primera versión estable del Núcleo que admite el protocolo 21. Nuevas funcionalidades en el protocolo 21:
-
-- Soporte secp256r1 en el host Soroban: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md
-- Función host de Soroban para extender TTL de la instancia del contrato y el código por separado: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md
-- Utiliza un modelo de costos refinado para la instanciación de VM para reducir los costos medidos de instanciación de VM: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0054.md
-- Caché de módulo VM intra-transacción para la posterior reducción de costos de Soroban: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0055.md, https://github.com/stellar/stellar-protocol/blob/master/core/cap-0056.md
-
-#### SDK de Rust de Soroban
-
-Esta es la primera versión del SDK de Soroban que admite el protocolo 21. Está marcada como 'vista previa' porque los contratos desarrollados con el SDK v21 solo serán compatibles con las redes actualizadas al protocolo 21. Cambios clave relacionados con el protocolo:
-
-- Admitir la verificación de firmas secp256r1
-- Admitir la extensión de TTL de la instancia de contrato y el código por separado
-
-## Protocolo 21: Vista previa 1 (solo Testnet, 12 de abril de 2024)
-
-### Software
-
-| Software                                                       | Versión                                          |
-| -------------------------------------------------------------- | ------------------------------------------------ |
-| XDR                                                            | `v21.1`                                          |
-| Rust XDR                                                       | `v21.0.1`                                        |
-| Entorno de Soroban                                             | `v21.0.1`                                        |
-| Stellar Core                                                   | `v21.0.0rc1`                                     |
-| SDK de Rust de Soroban                                         | `21.0.1-preview.1`                               |
-| Soroban CLI                                                    | `v21.0.0-preview.1`                              |
-| Soroban RPC                                                    | `v21.0.1`                                        |
-| Stellar Horizon                                                | `v2.30.0`                                        |
-| Stellar Quickstart                                             | \`\`                                             |
-| Stellar JS Stellar Base                                        | `v11.1.0`                                        |
-| Stellar JS Stellar SDK                                         | `v12.0.0-rc.1`                                   |
-| Freighter                                                      | \`\`                                             |
-| Laboratorio                                                    | \`\`                                             |
-| Aplicación descentralizada de pagos de Soroban React           | `TBD`                                            |
-| Aplicación descentralizada de emisión de tokens de Soroban     | `TBD`                                            |
-| Aplicación descentralizada de intercambio de tokens de Soroban | `TBD`                                            |
-| Frase de red de Futurenet                                      | `Test SDF Future Network ; octubre 2022`         |
-| Frase de red de Testnet                                        | `Test SDF Network ; septiembre 2015`             |
-| Frase de red Mainnet                                           | `Public Global Stellar Network ; September 2015` |
-
-### Notas de publicación
-
-#### Core
-
-Esta es la primera versión estable de Core que admite el protocolo 21. Nuevas características en el protocolo 21:
-
-- Admitir secp256r1 en el host de Soroban: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0051.md
-- Función de host de Soroban para extender el TTL de la instancia de contrato y el código por separado: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0053.md
-- Utiliza un modelo de costos refinado para la instanciación de VM para reducir los costos medidos de instanciación de VM: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0054.md
-- Caché del módulo VM intra-transacción para la posterior reducción de costos de Soroban: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0055.md, https://github.com/stellar/stellar-protocol/blob/master/core/cap-0056.md
-
-#### SDK de Rust de Soroban
-
-Esta es la primera versión del SDK de Soroban que admite el protocolo 21. Está marcada como 'vista previa' porque los contratos desarrollados con el SDK v21 solo serán compatibles con las redes actualizadas al protocolo 21. La API en sí puede considerarse estable. Cambios clave:
-
-- Admitir la verificación de firmas secp256r1
-- Admitir la extensión de TTL de la instancia de contrato y el código por separado
-
-## Protocolo 20: Soroban Fase 2 (19 de marzo de 2024)
-
-### Software
-
-| Software                                                       | Versión                                                                                                                               |
-| -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                                                            | [3da6ebcbd8afa01d5c94dbc7f0475f4c00089420](https://github.com/stellar/rs-stellar-xdr/commit/3da6ebcbd8afa01d5c94dbc7f0475f4c00089420) |
-| Entorno de Soroban                                             | `v20.2.2`                                                                                                                             |
-| Versión de la interfaz Soroban                                 | `0`                                                                                                                                   |
-| Límites de recursos de Soroban                                 | [Límites de la fase 2](./resource-limits-fees.mdx#resource-limits)                                                                    |
-| Tarifas de recursos de Soroban                                 | [Tarifas de la fase 2](./resource-limits-fees.mdx#resource-fees)                                                                      |
-| Stellar Core                                                   | `v20.3.0`                                                                                                                             |
-| SDK de Rust de Soroban                                         | `v20.4.0`                                                                                                                             |
-| Soroban CLI                                                    | `v20.3.1`                                                                                                                             |
-| Soroban RPC                                                    | `v20.3.3`                                                                                                                             |
-| Stellar Horizon                                                | `v2.28.3`                                                                                                                             |
-| Stellar Friendbot                                              | `TBD`                                                                                                                                 |
-| Stellar Quickstart                                             | `docker.io/stellar/quickstart:latest@sha256:1a82b17a4fae853d24189dd25d4e6b774fa7a1b6356a993e618c6e9bd2f3e04c`                         |
-| Stellar JS Stellar Base                                        | [`v11.0.0`](https://github.com/stellar/js-stellar-base/releases/tag/v11.0.0)                                                          |
-| Stellar JS Stellar SDK                                         | [`v11.2.2`](https://github.com/stellar/js-stellar-sdk/releases/tag/v11.2.2)                                                           |
-| Freighter                                                      | `v5.17.0`                                                                                                                             |
-| Laboratorio                                                    | `v4.1.0`                                                                                                                              |
-| Aplicación descentralizada de pagos de Soroban React           | `Por determinar`                                                                                                                      |
-| Aplicación descentralizada de emisión de tokens de Soroban     | `TBD`                                                                                                                                 |
-| Aplicación descentralizada de intercambio de tokens de Soroban | `TBD`                                                                                                                                 |
-| Frase de paso de la red Futurenet                              | `Test SDF Future Network ; October 2022`                                                                                              |
-| Frase de paso de la red Testnet                                | `Test SDF Network ; September 2015`                                                                                                   |
-| Frase de paso de la red Mainnet                                | `Public Global Stellar Network ; September 2015`                                                                                      |
-
-### Registro de cambios
-
-#### Core
-
-- Eliminar el uso de C99 que parece inicializadores designados de Cxx20
-- Reducir el tamaño de escaneo en fase1
-- Agregar subcomando simulate al script de encuesta de red
-- Continuar capturando mensajes SCP para el ledger anterior en la base de datos
-- Reescribir la ruta de carga del estado al inicio
-- Agregar soporte para debug-tx-set en dump-xdr
-- Limpieza de cubos
-- Actualizar configuraciones de fase1
-- Corregir error de compilación (Visual C++)
-- Actualizar archivos de configuración de soroban y utilidades
-- Agregar nuevas métricas de limitación
-- Agregar herramienta CLI para imprimir estadísticas de archivo de BucketList
-- Actualizar denominadores
-- Configurar el tamaño de la clave al valor inicial
-- Actualizar max_entries_to_archive para ser 1000.
-- Restringir la prueba "prev" solo al camino de votación, para permitir la recuperación.
-- Actualización de Strkey
-- Agregar scripts/extract-wasms.sh
-- Aumentar la versión mínima de overlay a 32
-- Corregir advertencias ruidosas de escaneo de desalojo
-- Inicialización temprana de métricas de soroban
-
-#### SDK de Rust de Soroban
-
-- Mostrar contenidos de String en implementación Debug
-- Agregar Bytes a_buffer y to_alloc_vec
-- Mover los tipos internos de prueba de Env a un solo tipo
-- Agregar opción para deshabilitar los snapshots de prueba en Env
-- Aumentar la versión a 20.4.0
-
-## Protocolo 20: Soroban Fase 1 (27 de febrero de 2024)
-
-### Software
-
-| Software                        | Versión                                                                                                                               |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                             | [8b9d623ef40423a8462442b86997155f2c04d3a1](https://github.com/stellar/rs-stellar-xdr/commit/8b9d623ef40423a8462442b86997155f2c04d3a1) |
-| Entorno de Soroban              | `v20.2.2`                                                                                                                             |
-| Versión de la interfaz Soroban  | `0`                                                                                                                                   |
-| Límites de recursos de Soroban  | [Límites de la fase 1](./resource-limits-fees.mdx#resource-limits)                                                                    |
-| Tarifas de recursos de Soroban  | [Tarifas de la fase 1](./resource-limits-fees.mdx#resource-fees)                                                                      |
-| Stellar Core                    | `v20.2.0`                                                                                                                             |
-| SDK de Rust de Soroban          | `v20.3.2`                                                                                                                             |
-| CLI de Soroban                  | `v20.3.1`                                                                                                                             |
-| Soroban RPC                     | `v20.3.3`                                                                                                                             |
-| Stellar Horizon                 | `v2.28.3`                                                                                                                             |
-| Stellar Friendbot               | `TBD`                                                                                                                                 |
-| Stellar Quickstart              | `docker.io/stellar/quickstart:latest@sha256:8d6f6520ad3842042bfe4e271f8b2324ec2f128564487abedd3876cea83af4f1`                         |
-| Stellar JS Stellar Base         | [`v11.0.0`](https://github.com/stellar/js-stellar-base/releases/tag/v11.0.0)                                                          |
-| Stellar JS Stellar SDK          | [`v11.2.2`](https://github.com/stellar/js-stellar-sdk/releases/tag/v11.2.2)                                                           |
-| Freighter                       | `v5.17.0`                                                                                                                             |
-| Laboratorio                     | `v4.1.0`                                                                                                                              |
-| Soroban React Payment dapp      | `Por determinar`                                                                                                                      |
-| Soroban Mint Token dapp         | `TBD`                                                                                                                                 |
-| Soroban Swap Token dapp         | `TBD`                                                                                                                                 |
-| Frase de red de Futurenet       | `Prueba SDF Future Network ; octubre 2022`                                                                                            |
-| Frase de paso de la red Testnet | `Red Test SDF; septiembre de 2015`                                                                                                    |
-| Frase de red de Mainnet         | `Public Global Stellar Network ; September 2015`                                                                                      |
-
-### Changelog
-
-#### Soroban RPC
-
-- (tag: v20.3.3) Bump version to 20.3.3
-- Update Dockerfile and Makefile to refer rpc instead of tools
-- Fix publish-dry-run failures
-- Revert "soroban-rpc: Remove publish-dry-run Workflow"
-- Perform fee padding in a larger bit width of integers
-- (tag: v20.3.2) Bump version to 20.3.2
-- Merge pull request #68 from stellar/add-spec-tools-crate
-- Merge branch 'main' into add-spec-tools-crate
-- Change module from soroban-tool to rpc in go.mod
-- Add hardcoded WASM file and reference it in tests
-- Uncomment install_rust
-- Add prometheus hook to count different log levels
-- Remove build-test-wasms from makefile
-
-#### Soroban CLI
-
-- (tag: v20.3.1) Bump version to 20.3.1
-- Update references in end-to-end tests to point to the latest releases
-- Bump version of soroban rpc and spec tools
-- Repoint soroban-spec-tools to the moved one in stellar/soroban-rpc
-- Rename Cargo.toml in the init template files
-- soroban-cli: Remove ALL RPC Related Code and Workflows
-- Use soroban-rpc crate from the RPC repo
-- fix: embed the init template files in the build
-- [Epic] Separating soroban-rpc to prepare for repo change
-- Soroban contract init followup
-- Merge pull request #1190 from stellar/release/v20.3.0
-- Merge branch 'main' into release/v20.3.0
-- Revert "[Epic] Separating soroban-rpc to prepare for repo change"
-- [Epic] Separating soroban-rpc to prepare for repo change
-
-## Protocol 20: Soroban Phase 1 (Mainnet Edition) (February 5, 2024)
-
-### Software
-
-| Software                        | Versión                                                                                                                               |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                             | [8b9d623ef40423a8462442b86997155f2c04d3a1](https://github.com/stellar/rs-stellar-xdr/commit/8b9d623ef40423a8462442b86997155f2c04d3a1) |
-| Soroban Environment             | `v20.2.2`                                                                                                                             |
-| Soroban Interface Version       | `0`                                                                                                                                   |
-| Soroban Resource Limits         | [Phase 0 Limits](./resource-limits-fees.mdx#resource-limits)                                                                          |
-| Soroban Resource Fees           | [Phase 0 Fees](./resource-limits-fees.mdx#resource-fees)                                                                              |
-| Stellar Core                    | `v20.2.0`                                                                                                                             |
-| Soroban Rust SDK                | `v20.3.2`                                                                                                                             |
-| Soroban CLI                     | `v20.3.0`                                                                                                                             |
-| Soroban RPC                     | `v20.3.1`                                                                                                                             |
-| Stellar Horizon                 | `v2.28.3`                                                                                                                             |
-| Stellar Friendbot               | `TBD`                                                                                                                                 |
-| Stellar Quickstart              | `docker.io/stellar/quickstart:latest@sha256:8d6f6520ad3842042bfe4e271f8b2324ec2f128564487abedd3876cea83af4f1`                         |
-| Base de Stellar JS              | [`v11.0.0`](https://github.com/stellar/js-stellar-base/releases/tag/v11.0.0)                                                          |
-| SDK Stellar JS                  | [`v11.2.2`](https://github.com/stellar/js-stellar-sdk/releases/tag/v11.2.2)                                                           |
-| Freighter                       | `5.16.0`                                                                                                                              |
-| Laboratorio                     | `v4.1.0`                                                                                                                              |
-| Soroban React Payment dapp      | `v3.0.0`                                                                                                                              |
-| Soroban Mint Token dapp         | `v3.0.0`                                                                                                                              |
-| Soroban Swap Token dapp         | `TBD`                                                                                                                                 |
-| Frase de red de Futurenet       | `Test SDF Future Network ; octubre de 2022`                                                                                           |
-| Frase de red Testnet            | `Test SDF Network ; September 2015`                                                                                                   |
-| Frase de paso de la red Mainnet | `Public Global Stellar Network ; September 2015`                                                                                      |
-
-### Changelog
-
-#### XDR
-
-- Run CI for the msrv and latest rust version
-- Backfill changes to next for json rendering
-- Bump XDR
-- Bump version to 20.1.0
-
-#### Soroban Environment
-
-- Allow small version-range wiggle room on curve25519-dalek to enable docs.rs nightly build
-- Bump version to 20.2.2
-- Enable publish of soroban-simulation crate
-- Add a function to invoke host function 'end-to-end' in recording mode.
-- Bug 1283 asset code rendering
-- Use strkeys for contract IDs and addresses in diagnostic events.
-- Turn off wasm_reference_types in Wasmi
-- Prng tests
-- Remove ConversionError from ScVal/Val conversions
-- Tightening up metering in auth
-- Bump XDR to 20.1
-- Allow negative fee1 kb low
-- Bump version to 20.2.0
-- Cover various Symbol conversion code paths with various valid/invalid cases
-- Run CI for the msrv and latest rust version
-- Add protocol version method to invoke_contract
-- Enable VM execution in a WASM environment by guarding time track behind time feature
-- Add test for checking VM stack depth.
-- Migrate preflight computations from soroban-rpc
-- soroban-simulate: Misc fixes
-- Add CI job to run cargo-semver-checks
-- Tracing
-- Add some basic test coverage for e2e_invoke.
-- Add test vectors for ed25519 edge cases
-- Trace should not emit diagnostic errors
-- Bump wasmi to 0.31.1-soroban.20.0.1
-- Bump version to 20.1.1
-
-#### Soroban Rust SDK
-
-- Update soroban-env-\*
-- Bump version to 20.3.2
-- Update extend_ttl docs
-- Bug 1076 conversion error flattening
-
-#### Soroban RPC
-
-- Migrate Soroban Tools to Soroban RPC
-- Use soroban-tools Crates
-- Pull in Recent Soroban RPC changes from soroban-tools
-- Mirror Last Remaining PRs from soroban-tools Repo
-- Add Workflow to Publish soroban-rpc Crate
-- added user agent config on ha archive pool
-- Update getTxn rpc with events data
-- Remove publish-dry-run Workflow
-- Use external soroban-simulation library for preflight computations
-- Store and serve the event transaction ID
-- Reduce event memory footprint
-- Add diagnostic events to sendTransaction response
-- Remove panics from internal codebase
-
-#### Soroban CLI
-
-- feat: soroban init command
-- Actualizar dependencias para el lanzamiento de pubnet
-- Actualizar Ubuntu a 22.04 desde 20.04
-- Actualizar dependencias de Go, Rust y Core
-- feat/cli: Mover comandos de configuración a nivel superior
-- bindings-ts: actualizar a la última SDK y TypeScript, añadir prueba CI
-- Las vinculaciones de TypeScript se han actualizado para usar la última stellar-sdk
-- Admitir flujos de trabajo multi-autenticación en las vinculaciones de TypeScript
-- Reemplazar comando cli xdr con stellar-xdr cli
-- Actualizar vinculaciones de TypeScript para las versiones más recientes
-- Advertir sobre versiones RC solo al usar pubnet
-
-## Estable v20.1.0 (11 de enero de 2024)
-
-### Software
-
-| Software                          | Versión                                                                                                                            |
-| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                               | [bb54e505f814386a3f45172e0b7e95b7badbe969](https://github.com/stellar/stellar-xdr/commit/bb54e505f814386a3f45172e0b7e95b7badbe969) |
-| Entorno Soroban                   | `v20.1.0`                                                                                                                          |
-| Versión de la interfaz de Soroban | `0`                                                                                                                                |
-| Stellar Core                      | `v20.1.0`                                                                                                                          |
-| Soroban Rust SDK                  | `v20.2.0`                                                                                                                          |
-| CLI de Soroban                    | `v20.2.0`                                                                                                                          |
-| Soroban RPC                       | `v20.2.0`                                                                                                                          |
-| Stellar Horizon                   | `v2.27.0`                                                                                                                          |
-| Stellar Friendbot                 | `TBD`                                                                                                                              |
-| Stellar Quickstart                | `docker.io/stellar/quickstart:soroban-dev@sha256:64b2d14b8a531c534560e287768846f538b2f063fc776aa9ca016c788e86c782`                 |
-| Base de Stellar JS                | [`v10.0.1`](https://github.com/stellar/js-stellar-base/releases/tag/v10.0.1)                                                       |
-| Stellar JS Stellar SDK            | [`v11.2.0`](https://github.com/stellar/js-stellar-sdk/releases/tag/v11.2.0)                                                        |
-| Freighter                         | `5.9.0`                                                                                                                            |
-| Laboratorio                       | `Por determinar`                                                                                                                   |
-| Soroban React Payment dapp        | `TBD`                                                                                                                              |
-| Soroban Mint Token dapp           | `TBD`                                                                                                                              |
-| Soroban Swap Token dapp           | `TBD`                                                                                                                              |
-| Frase de red de Futurenet         | `Test SDF Future Network ; octubre de 2022`                                                                                        |
-| Frase de paso de la red Testnet   | `Test SDF Network ; September 2015`                                                                                                |
-
-### Registro de cambios
-
-#### Soroban Rust SDK
-
-- Corregir error relacionado con Timepoint/Duración como parámetros/retornos
-- Añadir funciones de actualización de almacenamiento
-- Exportar funciones para crear Timepoint/Duración
-- Permitir `&Env` en funciones de contrato
-
-## Estable v20.0.0 (18 de diciembre de 2023)
-
-### Software
-
-| Software                          | Versión                                                                                                                            |
-| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                               | [bb54e505f814386a3f45172e0b7e95b7badbe969](https://github.com/stellar/stellar-xdr/commit/bb54e505f814386a3f45172e0b7e95b7badbe969) |
-| Entorno Soroban                   | `v20.0.0`                                                                                                                          |
-| Versión de la interfaz de Soroban | `0`                                                                                                                                |
-| Stellar Core                      | `v20.0.1`                                                                                                                          |
-| Soroban Rust SDK                  | `v20.0.0`                                                                                                                          |
-| CLI de Soroban                    | `v20.0.2`                                                                                                                          |
-| Soroban RPC                       | `v20.0.2`                                                                                                                          |
-| Stellar Horizon                   | `v2.27.0`                                                                                                                          |
-| Stellar Friendbot                 | `TBD`                                                                                                                              |
-| Stellar Quickstart                | `docker.io/stellar/quickstart:testing@sha256:3c7947f65db493f2ab8ca639753130ba4916c57d000d4a1f01ec530e3423853b`                     |
-| Stellar JS Stellar Base           | [`v10.0.0`](https://github.com/stellar/js-stellar-base/releases/tag/v10.0.0)                                                       |
-| SDK JS Stellar de Stellar         | [`v11.0.1`](https://github.com/stellar/js-stellar-sdk/releases/tag/v11.0.1)                                                        |
-| Cliente Soroban de Stellar JS     | [`v1.0.0`](https://github.com/stellar/js-soroban-client/releases/tag/v1.0.0) (obsoleto, preferir la Stellar SDK)                   |
-| Freighter                         | `5.12.0`                                                                                                                           |
-| Laboratorio                       | `4.11.0`                                                                                                                           |
-| Soroban React Payment dapp        | `3.0.0`                                                                                                                            |
-| Soroban Mint Token dapp           | `3.0.0`                                                                                                                            |
-| Soroban Swap Token dapp           | `TBD`                                                                                                                              |
-| Frase secreta de la red Futurenet | `Test SDF Future Network ; octubre 2022`                                                                                           |
-| Frase de red de Testnet           | `Test SDF Network ; September 2015`                                                                                                |
-
-### Registro de cambios
-
-#### XDR
-
-- Actualizar la documentación para las operaciones extendTTL/restaurar para coincidir con el cambio de umbral
-
-#### Entorno Soroban
-
-- Hacer que RecordedAuthPayload devuelva consistentemente None para invocador.
-- Correcciones relacionadas con la caducidad
-- Convertir pánicos de préstamos dinámicos en HostErrors
-- Usar la función Ed25519 verify_strict en lugar de solo verificar, corregir #857
-- Problemas misceláneos int32
-- Hacer cumplir la integridad del identificador de objeto al insertar en contenedores, corregir #569
-- Añadir caso de prueba para scmaps desordenados, corregir #223.
-- Añadir una función para calcular la tarifa de alquiler.
-- Usar host.err para error de autenticación
-- Añadir una prueba de humo para grabar autenticación para crear la función de host del contrato.
-- Dejar de tratar errores de almacenamiento como entradas faltantes
-- Reorganizar el administrador de autorización para mantener préstamos mutables solo en la cantidad mínima de campos
-- Actualizar xdr
-- Añadir aumentos de alquiler al SAC
-- Añadir la función is_admin
-- Actualizar xdr
-- Añadir una función para calcular la tarifa de escritura según el tamaño del libro mayor.
-- Prohibir el uso de firmas disjuntas para cubrir el árbol de autenticación.
-- Hacer cumplir DepthLimiter en el Host para evitar el desbordamiento de pila
-- Objetos relativos en wasm
-- Adaptarse a ResourceLimiter, reemplazando la medición de combustible de memoria
-- Hacer que del_contract_data no efectúe operaciones para eliminar clave de almacenamiento de instancia que no existe.
-- Añadir la función "tracy" para habilitar el perfilador Tracy, con algunas anotaciones básicas
-- Actualizar el host para tener en cuenta los cambios en el XDR.
-- Actualizar versión de rust
-- Adaptarse al cambio de SCError para que sea un enum, con ContractError(u32)
-- Hacer que algunos errores del host no sean recuperables en try_call.
-- Corregir la ruta de código de panic-string-logging rota por la reciente corrección de dynamic-borrow.
-- Añadir soroban-bench-utils, añadir pruebas de referencia para medir la precisión de medición
-- Actualizar xdr del entorno y realizar los cambios de la biblioteca de tarifas correspondientes a los cambios de configuración
-- Actualizar xdr del entorno
-- Eliminar límites en el tema del evento
-- Actualizar xdr del entorno
-- Unificar/arreglar la lógica de aumento de caducidad en el host.
-- Añadir nuevas pruebas para la escalación de errores de llamadas a contratos.
-- Añadir un ayudante que invoque una función del host 'de inicio a fin'
-- Añadir ayudantes para la inicialización masiva de contenedores; se aplica a la mediación de autenticación
-- Cambiar algunos errores de autenticación de Internos a InvalidInput.
-- Habilitar operaciones en WASM posteriores a MVP (sign-ext y mutable-globals), corregir #968.
-- Más pruebas de token
-- Ejemplo de asignación
-- Limpiar algunos usos residuales de cadenas de formato en errores (ya no son compatibles)
-- Añadir wasm para actualizar el contrato write-bytes
-- Escalar el coeficiente del modelo de costo lineal; mejorar el ajuste del modelo
-- Error si se supera el max_entry_expiration y función del host para recuperar max_entry_expiration
-- Hacer que las verificaciones sean para poblar adecuadamente el mapa de almacenamiento en modo de grabación
-- Limpiar tipos de costos de presupuesto
-- Añadir eventos de depuración para el informe de errores de almacenamiento.
-- Cambiar a rust-analyzer estable en CI
-- Añadir algunos comentarios y pruebas a env-common/symbol.rs
-- Actualizar crates dalek a nuevas versiones estables.
-- Añadir una opción para devolver un error al encontrar autenticación no raíz en modo de grabación.
-- Rechazar env.json si hay nombres de exportación duplicados, corregir #189
-- Ajustar firma de unchecked_visit_val_obj, corregir #595
-- Ajustar aún más las dependencias
-- Corregir el nombre de argumento incorrecto
-- Actualizar xdr del entorno
-- Optimizar Map y Vector y cobertura de medición
-- Almacenar instancia ficticia para contratos de prueba.
-- Actualizar XDR para tomar en cuenta el cambio que elimina SCSpecTypeSet
-- Corregir comparación en Tag::is_object
-- Corregir calibración debido al cambio de dalek
-- Cobrar tarifas de escritura para aumentos de entrada de caducidad.
-- Reducir el tamaño de escritura de entrada de caducidad.
-- Refactor host to support the new expiration ledger approach.
-- Add lifetime threshold
-- Enable build workflow for merge groups
-- Remove key size from rent change computation.
-- Take change from txSOROBAN_RESOURCE_LIMIT_EXCEEDED to txSOROBAN_INVALID
-- Add ExpirationEntry support
-- Add git rev dep check to ci
-- Fix encode contract events metering
-- Trim deps
-- Reject vals with invalid tags, fix #1029
-- Fix EXPIRATION_ENTRY_SIZE constant
-- Avoid iloop externalizing diagnostics for invalid references
-- Add "coverage" Makefile target for lcov.info, add a test that extends coverage
-- Fix asset-code rendering in native contract.
-- Fix rent changes extraction bug
-- Graydon code review
-- Jay code review
-- Bump xdr and use curr instead of next
-- Trivial xdr bump
-- Tighten wasm interface version checks, and do on upload.
-- Update wasmi to 0.31.0-soroban
-- Bump version to 20.0.0-rc1
-- Add "next" feature to crates using xdr directly or indirectly
-- Move out-slice len adjustment from symbol_copy_to_slice to its caller.
-- Bump interface and regenerate wasms to handle symbol semantics change.
-- No-op rename: remove metered from metered_scan_slice_of_slices
-- Get rid of an unnecessary vector allocation in map_new_from_slices
-- Remove metered map iterator functions.
-- Small vec cleanup
-- Code cleanup around PRNG
-- Factor Tag::is_object to let Val::is_object delegate to it
-- Set LedgerEntry extensions on existing entries
-- Attach the auth in recording mode to any valid tracker.
-- Improve storage error reporting for token contract.
-- Env-common cleanups and dead code removal
-- More cleanups, comments and fixes from code review.
-- Make the 'unknown' wasmi error to be InvalidAction instead of InternalError
-- Error improvements
-- Small update for the default budget limits.
-- Calibration for PRNG and charge budget
-- Code review, cleanup, removal of dead/dangerous host functions
-- Add redundant "next" dependencies
-- Host code review, minor cleanups and code reorganization
-- Fix the instance storage update logic.
-- Feature: Expose rem_euclid functions on 256 bit numbers
-- Replace address bytes conversions with strkey conversions.
-- Use Address for call_account_contract_check_auth test helper.
-- More code review and cleanup of host.rs module
-- Budget fiddling
-- Bump env XDR
-- State expiration renames
-- Cost type cleanup, bug fix, improve calibration
-- Code review on fees, crypto, prng, dispatch
-- Storage code review
-- Setup bench framework to run experiments
-- Decorate error for nonce missing from the footprint.
-- Remove bad LEs
-- Add missing fixed-size metering in comparison.rs, clean up a bit
-- Properly dispatch test contracts based on the executable.
-- Tighten up metering for linear memory routines
-- conversion.rs code review fixes
-- Review fixes for declared_size and metered_clone
-- Gate recording auth behind the feature.
-- Fix test wasms for latest sdk
-- Cackle gate
-- Remove spendable_balance from SAC.
-- Extend upgrade contract from 30 to 60 days
-- Bug 1042 internal renames
-- Remove panic
-- Stop caching authorization tracker verification status.
-- Overhaul "free budget" and migrate non-metered code
-- Clarify (and add redundant defensive code) in check_val_integrity
-- Remove a panic and be more conservative about depth limit
-- Add conceptual overview comment to auth module
-- Fix fuzz-found panic in Prng::u64_in_inclusive_range
-- Fix fuzzer-found frame stack corruption in rollback if instance storage fails
-- Arbitrary-compatible expr generation and host fuzzing
-- Improve auth test coverage a bit
-- Rollback tests
-- Add a test that ensures that SAC reentry is not possible.
-- Remove vnext test wasms
-- Add fn to find out if Host can be finished
-- Add tests for more wasmi trap conditions
-- Storage tests
-- Add tests that try to build a deep host stack.
-- More events and diagnostics testing
-- Fix #1174 fuzzer-found deserialization of non-representable ScVal bug.
-- tighten up handling of debug mode
-- Update rust-version
-- Adapt to rs-stellar-xdr Limits change
-- Add tests that cover fees for each individual resource.
-- Cover non-existent Wasm in test for updating Wasm.
-- Adds loadgen test WASM
-- Add wasm test for excessive initial memory and table size
-- Initial cut at bug 872, observe side effects of tests
-- Remove unnecessary copy of value
-- Test update_contract_wasm with rollbacks.
-- Bug 1146 test invalid val bit patterns
-- Add @dmkozh as code owner of soroban-env-host
-- Hook envbase and vec slices
-- Update stellar-xdr
-- Don't block merges on rust-analyzer compat check
-- Observe most of the remainder of the testsuite
-- Update deps, fix #1200
-- Test nested extend_ttl
-- Fix #1175 error code spoofing
-- Do not error if no authorizations
-- Add a contract that allows materializing arbitrarily large values.
-- Updated loadgen Wasm
-- Cap persistent extension to max
-- Error on issuer for mint, burn, clawback, and burn_from
-- Add a very simple hook for tracking top-level contract invocations.
-- Macro for testing host function dispatch with bad inputs
-- Check val integrity more
-- Adapt to Rust 1.74
-- Improve test coverage for crypto functions.
-- Pub ContractInvocationEvent
-- Pass ref to host to contract invocation hook
-- Fix top contract invocation hook and auth interaction
-- XDR limits updates
-- Run user seeds to PRNGs through HMAC-SHA256 to unbias
-- Add size_hint methods to Arbitrary impls
-- Add tests for de-serializing deep XDR in deep call stack.
-- Generate combinational tests for linear memory functions
-- Add tests that grow containers until running out of memory budget.
-- Observe more things
-- Setting pre_release_version to zero in meta.rs in preparation of Soroban launch
-- Add Host::has_frame
-- Validated TTLentries
-- Budget subsystem code review
-- Rename extend host functions
-- Fuzz fixes
-- Cap number of args to wasm functions
-- Cargo version pinning
-- Pass --locked to publish as well
-- Tighten up saturating\_ math checks
-- Auth code review
-- Remove unused publish scripts/make targets
-- Write tests for unrecoverable errors with try_call
-- Fix the invoker contract auth rollback logic and cover it in the tests.
-- Re-calibration on x86 and update cost parameters
-- Add tests for invalid maps, oversized maps/vecs/bytes from various paths
-- Frame code review
-- Improve XDR conversion coverage
-- Add more error tests
-- Improve budget tracker
-- Validate assets when trying to create SAC instance.
-- Conversion tests
-- Update stellar-xdr
-- Change string_new_from_slice to use &[u8] instead of &str.
-- Update stellar-xdr
-- Initial SAC review
-- Derive debug, eq, ord on CostTracker for SDK
-- Noop auth fix
-- Test bad WASMs
-- Add time tracker
-- Bump wasmi and xdr to release versions
-- SAC final code review
-- Add fuzz target that runs wasmi on wasm-smith output
-- Remaining host code review
-- Bump version to 20.0.0
-
-#### Soroban Rust SDK
-
-- Token events
-- Actualizar versión de Rust
-- Update SDK to recent env
-- Add admin function
-- fix: use uppercase const name
-- Fix allocator
-- Add Arbitrary impl for Duration and Timepoint
-- Fix Budget::memory_bytes_cost
-- Bump env to c5607a2e9e296b2636b46dc910387aa3446b3e29
-- Bump env
-- Update dalek, remove non-syn2 exemptions, tighten deps
-- Actualizar el iterador de mapas para que sea basado en índices
-- Eliminar el soporte de ScSpecTypeSet, que ya estaba prácticamente obsoleto.
-- Proporcionar una manera de permitir la autenticación no raíz en modo de grabación.
-- Actualizar la versión del entorno en el SDK.
-- Actualizar el SDK para admitir la reestructuración de entradas de caducidad.
-- Actualizar el entorno para los cambios de interfaz
-- Corregir comentario en String::copy_into_slice
-- Agregar comentarios en la documentación sobre por qué symbol_short!
-- Agregar vector de prueba para configuraciones de espacio de trabajo donde los tipos de contrato viven en una biblioteca
-- Actualizar rust-version
-- Habilitar flujo de trabajo de compilación para grupos de fusión
-- Rehabilitar compilaciones para linux arm64
-- Corregir/criadoperez
-- Correcciones de texto
-- Actualizar versión de Rust
-- Actualizar el entorno
-- Corregir el nombre del cliente administrador del activo Stellar
-- Agregar verificación de dependencia git en ci
-- Eliminar autorizado de la interfaz estándar del token
-- Actualizar el entorno
-- Adaptarse a la eliminación de ConversionError de las conversiones de tipos numéricos.
-- Actualizar versión a 20.0.0-rc1
-- Implementar funciones de desplegador que devuelvan el id del contrato desplegado.
-- Agregar Vec::to_vals
-- Exponer funciones de PRNG
-- Exponer secp256k1 y keccak256 en el SDK
-- Actualizar el entorno a v20.0.0-rc2
-- Elaborar más en el comentario sobre las fortalezas y debilidades de PRNG
-- Actualizar versión a 20.0.0-rc2
-- Comentarios sobre PRNG más explícitos
-- Adaptarse a cambios menores en el entorno a partir de la revisión de código
-- Adaptarse a cambios recientes en el entorno
-- docs: Corregir un enlace roto en el archivo lib.rs del SDK
-- Corregir errores tipográficos en documentos arbitrarios
-- Cambiar Storage::get a pub(crate)
-- Agregar función para exponer la máxima caducidad disponible
-- Update rust-version
-- corregir(snapshot): establecer información sobre la caducidad de entrada en set_ledger_info
-- Agregar soporte del SDK para conversiones de Address/StrKey.
-- actualizar entorno y xdr para renombrar exp de estado
-- actualizar entorno
-- Función: exponer funciones rem_euclid y agregar conversiones de 128/256 bits
-- Corregir tipo de firma en autenticación
-- Agregar testutils para acceder a todo el almacenamiento de un contrato
-- Eliminar balance gastable
-- Corregir lints nocturnos en exportaciones internas no utilizadas
-- Generar todos los tipos de direcciones al realizar pruebas de fuzzing.
-- Usar aleatoriedad determinística en pruebas arbitrarias
-- Generar contenedores arbitrarios con elementos heterogéneos
-- Agregar implementaciones de SorobanArbitrary para tuplas.
-- Actualizar versión del entorno
-- Corregir documentación sobre la semilla de prng
-- Refactorizar funciones Prng
-- Agregar generación de prng para slices y matrices
-- Facilitar agregar mezcla a otros tipos
-- Hacer que Env::default y Env::from_snapshot configuren el entorno de la misma manera
-- Testutils arbitrarios
-- Eliminar el uso de rand de las direcciones generadas, nonces, sales y pks de emisores
-- Reemplazar String::from_slice con from_str
-- Actualizar dependencias soroban-env-\*
-- Codificar ID de red como hex en imágenes del ledger
-- Guardar automáticamente un archivo de instantánea de prueba en cada salida de prueba
-- Permitir incrementar otras instancias
-- Actualizar entorno
-- Hacer que Option funcione con el tipo de contrato
-- Renombrar token::Interface/Client a TokenInterface/Client
-- No escribir instantánea de prueba si no hay nombre de hilo
-- Pequeñas mejoras y organización de instantáneas de prueba
-- No bloquear fusiones debido a la verificación de compatibilidad de rust-analyzer
-- Expandir prueba Env para verificar que se escriban pruebas separadas para múltiples Envs
-- No registrar instantáneas de prueba para pruebas de documentación
-- Verificar que no existan diferencias después de la ejecución de la prueba debido a instantáneas de prueba no confirmadas
-- Agregar autenticación a la instantánea de Env
-- Actualizar entorno y xdr
-- Instantánea de todas las autorizaciones durante una prueba, no solo las últimas invocaciones
-- Actualizar versión de rust
-- Mejoras a Opciones Arbitrarias
-- Ocultar EnvBase y otros tipos internos
-- Restaurar estado de autenticación anterior en el cliente
-- Hacer que try\_ fns devuelva un tipo de error de SDK más pequeño
-- Eliminar nextest de Makefile
-- Actualizar el entorno
-- Funciones de host de extensión renombradas
-- Actualizar entorno
-- Actualizar versión a 20.0.0
-
-#### Soroban RPC
-
-- aumentar el relleno de la tarifa de instrucción de preflight a 3 millones
-- Reforzar la habilitación de eventos de diagnóstico
-- Agregar referencia de rendimiento y prueba para getPreflight
-- Agregar caché de escritura a través para entradas de ledger de configuración
-- Almacenar en caché todas las entradas de ledger consultadas de DB en la transacción de lectura
-- simulateTransaction detecta automáticamente entradas de ledger que requieren restauración
-- Agregar puntos finales de perfilado de heap
-- Intentar devolver eventos de diagnóstico en caso de fallo en simulateTransaction
-- Agregar manejo genérico de pánicos
-- Limitar el tamaño de la solicitud a 10MB
-- getLedgerEntries puede consultar múltiples entradas de ledger a la vez
-- Transmitir ledgers en inicialización
-- Establecer el número máximo de claves a consultar para getLedgerEntries
-- Agregar soporte para nuevas entradas de ledger de caducidad de estado
-- Ingerir desalojo de entradas temporales de ledger
-- Reducir el tamaño máximo de la solicitud http
-- Establecer base de prng a cero en preflight e invocar
-- Excluir entradas caducadas temporales de SnapshotSource en preflight
-- Incluir eventos del sistema en el cálculo de tarifas en preflight
-- Obtener secuencia de ledger de caducidad en la fuente
-- Agregar un README.md "Construyendo desde la Fuente"
-- Aplanar la estructura de respuesta de getEvents
-- Habilitar depuración de forma predeterminada para preflight
-- Optimizar almacenamiento de transacciones en memoria
-- Forzar Modo en Disco
-- Corregir carrera de datos en bufferedResponseWriter.WriteOut
-- Corregir bug de upsert en caché de DB
-- Corregir bug de visibilidad de entradas del ledger
-- Corregir errores unwrap() en libpreflight debido a errores en la interfaz Go/Rust
-- Corregir número de secuencia de simulación para operaciones de aumento/restauración
-- Mejorar el mensaje de argumentos de línea de comando faltantes
-- Corregir caché de GetLatestLedgerSequence
-- Asegurarse de que los eventos sim se registren; mejorar el formato de los registros principales
-- Validar cargas útiles xdr en las solicitudes de soroban-rpc
-- Corregir bug de conteo doble en preflight
-- Corregir posible desbordamiento
-- Corregir respuestas de múltiples entradas para el método getLedgerEntries
-- Actualizar versión de jrpc2 para habilitar application/json; charset=utf-8
-- Unificar todos los tipos de secuencia de ledger a uint32 y dejar de stringify números < 53 bits de ancho
-- Restaurar soporte CORS
-
-#### Soroban CLI
-
-- Permitir recuperación del contrato de la red
-- Cada método de contrato generado agrega -file-path
-- Agregar dos nuevos tipos de salida para inspección de contratos
-- Agregar fondo de identidad de configuración para financiar cuentas en redes
-- Agregar soporte para firma Auth-next
-- Agregar dotenv para que los directorios ahora puedan establecer argumentos CLI
-- Agregar key::Args y FullLedgerEntry/FullLedgerEntries
-- Eliminar sandbox
-- Agregar Transacción Ensamblada que maneje la preparación de transacciones después de la simulación
-- Hacer visibles los alias en la documentación de ayuda
-- Corregir el --cost flag
-- Establecer el código de salida en 1 en caso de un error
-- Devolver un error cuando la lectura del contrato no puede leer ninguna entrada
-- El token envuelto ya no falla con entradas válidas en modo sandbox
-- El comando fund ahora puede aceptar una strkey pública
-- Advertir o Error al Desplegar Contratos Compilados con Versión RC de Soroban SDK
-- Imprimir ayuda si el CLI personalizado está vacío y reemplazar unwrap donde sea posible
-- Corregir varios enlaces de typescript
-- Hacer la salida consistente para todas las maneras de obtener la versión
-
-## Vista previa 11 (11 de septiembre de 2023): Edición Testnet y Futurenet
-
-### Software
-
-| Software                          | Versión                                                                                                                            |
-| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                               | [9ac02641139e6717924fdad716f6e958d0168491](https://github.com/stellar/stellar-xdr/commit/9ac02641139e6717924fdad716f6e958d0168491) |
-| Entorno Soroban                   | `v20.0.0-rc2`                                                                                                                      |
-| Versión de la Interfaz Soroban    | `57`                                                                                                                               |
-| Stellar Core                      | `20.0.0-1504.rc2.22088c1f2.focal`                                                                                                  |
-| SDK de Soroban Rust               | `v20.0.0-rc2`                                                                                                                      |
-| CLI de Soroban                    | `v20.0.0-rc4`                                                                                                                      |
-| RPC de Soroban                    | `v20.0.0-rc4`                                                                                                                      |
-| Stellar Horizon                   | `2.27.0~rc2-384`                                                                                                                   |
-| Stellar Friendbot                 | `soroban-v0.0.2-alpha`                                                                                                             |
-| Inicio Rápido de Stellar          | `docker.io/stellar/quickstart:testing@sha256:0c756150e7b3c53603fe36bb932c4e7d7ceaef691906b2d3d952771ccc195559`                     |
-| Stellar JS Stellar Base           | [`v10.0.0-beta.3`](https://github.com/stellar/js-stellar-base/releases/tag/v10.0.0-beta.3)                                         |
-| Stellar JS Stellar SDK            | [`v11.0.0-beta.5`](https://github.com/stellar/js-stellar-sdk/releases/tag/v11.0.0-beta.5)                                          |
-| Cliente Stellar JS Soroban        | [`v1.0.0-beta.3`](https://github.com/stellar/js-soroban-client/releases/tag/v1.0.0-beta.3) (obsoleto, prefiere el SDK de Stellar)  |
-| Freighter                         | `5.6.1`                                                                                                                            |
-| Laboratorio                       | `2.12.0`                                                                                                                           |
-| Soroban React Payment dapp        | `2.0.0`                                                                                                                            |
-| Soroban Mint Token dapp           | `2.0.0`                                                                                                                            |
-| Soroban Swap Token dapp           | `2.0.0`                                                                                                                            |
-| Frase secreta de la red Futurenet | `Test SDF Future Network ; octubre 2022`                                                                                           |
-| Frase de paso de la red Testnet   | `Test SDF Network ; September 2015`                                                                                                |
-
-:::note
-
-La versión de RPC de Soroban para la Vista previa 11 se encuentra actualmente en los repositorios inestables y de prueba de Stellar. Además, su lanzamiento de imagen de Docker puede accederse en [docker.io/stellar/soroban-rpc:20.0.0-rc3-39](https://hub.docker.com/layers/stellar/soroban-rpc/20.0.0-rc3-39/images/sha256-227170869bca74998e1b6cc1e07deb3aca8d03e36154b3da700d6669e19d485b?context=explore).
-
-:::
-
-### Registro de cambios
-
-#### XDR
-
-- Generar error por entrada caducada
-- Aumentar XDR
-- Generar límite de profundidad XDR y lectura/escritura Xdr limitada por profundidad
-- Aumentar XDR
-- Hacer que SCError sea una unión para permitir que los errores de usuario sean u32
-- Actualizar versión de rust
-- Aumentar XDR
-- Aumentar XDR
-- Aumentar XDR
-- Regenerar para recoger cambios en ContractCostType
-- Aumentar XDR
-- Actualizar para reflejar eliminación de SCSpecTypeSet
-- Tomar cambio de txSOROBAN_RESOURCE_LIMIT_EXCEEDED a txSOROBAN_INVALID
-- Take change from txSOROBAN_RESOURCE_LIMIT_EXCEEDED to txSOROBAN_INVALID
-- Actualizar versión de rust
-- Aumentar curr y next
-- Actualizar curr y siguiente
-- Aumentar XDR
-- Aumentar versión a 20.0.0-rc1
-
-#### Ambiente Soroban
-
-- Adjuntar la autenticación en modo de grabación a cualquier rastreador válido cuando sea posible
-- Hacer que RecordedAuthPayload devuelva consistentemente None para el invocador
-- Correcciones relacionadas con la caducidad
-- Convertir pánicos de préstamos dinámicos en HostErrors
-- Usar la función Ed25519 verify_strict en lugar de solo verificar, corregir #857
-- Problemas varios de int32
-- Hacer cumplir la integridad del manejo de objetos al insertar en los contenedores, corregir #569
-- Agregar caso de prueba para scmaps fuera de orden, corregir #223
-- Agregar una función para calcular la cuota de alquiler
-- Usar host.err para errores de autenticación
-- Agregar una prueba de humo para grabación de autenticación para crear función de contrato de host
-- Dejar de tratar errores de almacenamiento como entradas faltantes
-- Refactorizar el administrador de autorización para mantener solo el préstamo mutable en la cantidad mínima de campos
-- Aumentar xdr
-- Agregar aumentos de alquiler al SAC
-- Agregar función is_admin
-- Aumentar xdr
-- Agregar función para calcular la cuota de escritura según el tamaño del libro mayor
-- Prohibir el uso de firmas disjuntas para cubrir el árbol de autenticación
-- Hacer cumplir DepthLimiter en el Host para evitar desbordamiento de pila
-- Objetos relativos en wasm
-- Adaptar a ResourceLimiter, reemplazando la medición de combustible de memoria
-- Hacer que del_contract_data no haga nada cuando se elimina la clave de almacenamiento de instancia que no existe
-- Agregar función 'tracy' para habilitar el profiler Tracy, con algunas anotaciones básicas…
-- Actualizar host para tener en cuenta los cambios en el XDR
-- Actualizar versión de rust
-- Adaptar el cambio de SCError para que sea un enum, con ContractError(u32)
-- Hacer que algunos errores del host sean no recuperables en try_call
-- Corregir el camino del código de panic-string-logging roto por la reciente corrección de dynamic-borrow
-- Agregar utilidades de evaluación de rendimiento de soroban, agregar pruebas de referencia para medir la precisión de la medición
-- Aumentar env xdr y realizar los cambios correspondientes en la biblioteca de tarifas relacionados con los cambios de configuración
-- Aumentar env xdr
-- Eliminar límites de tema de eventos
-- Aumentar env xdr
-- Unificar/arreglar la lógica de aumento de caducidad en el host
-- Agregar nuevas pruebas para la escalación de errores de llamadas de contrato
-- Agregar una ayuda que invoque una función de host 'de inicio a fin'
-- Agregar ayudas para la inicialización a granel de contenedores; se aplica a la medición de autenticación
-- Cambiar algunos errores de autenticación de Internos a InvalidInput
-- Habilitar operaciones WASM posteriores al MVP (sign-ext y mutable-globals), corregir #968
-- Más pruebas de tokens
-- Ejemplo de asignación
-- Recoger algunos usos residuales de cadenas de formato en errores (ya no compatibles)
-- Agregar wasm para la actualización del contrato write-bytes
-- Escalar el modelo de costo lineal; mejorar el ajuste del modelo
-- Error al aumentar más allá de max_entry_expiration y función de host para recuperar max_entry_expiration
-- Hacer verificaciones para poblar correctamente el mapa de almacenamiento en modo de grabación
-- Limpiar tipos de costo del presupuesto
-- Agregar eventos de depuración a la información de errores de almacenamiento
-- Cambiar a rust-analyzer estable en CI
-- Agregar algunos comentarios y pruebas a env-common/symbol.rs
-- Actualizar las bibliotecas de dalek a nuevas versiones estables
-- Agregar una opción para devolver un error al encontrar autenticaciones que no son de root en modo de grabación
-- Rechazar env.json si hay nombres de exportación duplicados, corregir #189
-- Ajustar la firma de unchecked_visit_val_obj, corregir #595
-- Ajustar más las dependencias
-- Corregir nombre de argumento incorrecto
-- Aumentar env xdr
-- Ajustar Map y Vector y cobertura de medición
-- Almacenar instancia ficticia para contratos de prueba
-- Actualizar XDR para incluir el cambio que elimina SCSpecTypeSet
-- Corregir comparación en Tag::is_object
-- Corregir calibración debido a la modificación de dalek
-- Cargar tarifas de escritura para aumentos de entrada de caducidad
-- Reducir el tamaño de escritura de entrada de caducidad
-- Refactorizar el host para soportar el nuevo enfoque de libro mayor de caducidad
-- Agregar umbral de vida útil
-- Habilitar flujo de trabajo de compilación para grupos de fusión
-- Eliminar tamaño de clave del cálculo de cambio de alquiler
-- Tomar cambio de txSOROBAN_RESOURCE_LIMIT_EXCEEDED a txSOROBAN_INVALID
-- Agregar soporte de ExpirationEntry
-- Agregar verificación de dependencia git a ci
-- Corregir la medición de eventos de contrato de codificación
-- Recortar dependencias
-- Rechazar vals con etiquetas inválidas, corregir #1029
-- Host: corregir constante EXPIRATION_ENTRY_SIZE
-- Evitar la externalización de diagnósticos de iloop para referencias inválidas
-- Agregar objetivo de Makefile 'coverage' para lcov.info, agregar una prueba que extienda la cobertura
-- Corregir la representación del código de activo en el contrato nativo
-- Corregir error en la extracción de cambios de alquiler
-- Revisión de código de Graydon
-- Revisión de código de Jay
-- Aumentar xdr y usar curr en lugar de next
-- Aumento xdr trivial
-- Ajustar comprobaciones de versión de interfaz wasm y realizarlo en la carga, corregir #1052
-- Actualizar wasmi a 0.31.0-soroban
-- Aumentar versión a 20.0.0-rc1
-
-#### SDK de Soroban Rust
-
-- Implementar funciones de implementador que devuelvan el id del contrato implementado
-- Agregar Vec::to_vals
-- Exponer funciones PRNG
-- Exponer secp256k1 y keccak256 en el SDK
-- Actualizar entorno a v20.0.0-rc2
-- Elaborar más en el comentario sobre las fortalezas y debilidades de PRNG
-- Aumentar versión a 20.0.0-rc2
-- Eventos de tokens
-- Actualizar versión de rust
-- Actualizar SDK a reciente entorno
-- Agregar función de administrador
-- corregir: usar el nombre de constante en mayúsculas
-- Corregir asignador
-- Agregar implementación arbitraria para Duration y Timepoint
-- Corregir Budget::memory_bytes_cost
-- Aumentar entorno a c5607a2e9e296b2636b46dc910387aa3446b3e29
-- Aumentar entorno
-- Actualizar dalek, eliminar exenciones no-syn2, ajustar dependencias
-- Actualizar iterador de mapa para que sea basado en índices
-- Eliminar soporte de ScSpecTypeSet, que ya estaba mayormente muerto
-- Proporcionar una manera de permitir la autenticación que no es de root en modo de grabación
-- Actualizar versión del entorno en el SDK
-- Actualizar SDK para soportar la reestructuración de entradas de caducidad
-- Actualizar el entorno para cambios en la interfaz de actualización
-- Corregir comentario en String::copy_into_slice
-- Agregar comentarios de documentación sobre por qué simbolo_corto!
-- Agregar vector de prueba para configuraciones de espacio de trabajo donde los tipos de contrato viven en una lib
-- Actualizar la versión de rust
-- Habilitar flujo de trabajo de construcción para grupos de merge
-- Reactivar construcciones linux arm64
-- Corregir/criadoperez
-- Correcciones de texto
-- Actualizar la versión de rust
-- Actualizar el entorno
-- Corregir nombre del cliente administrador de Stellar Asset
-- Agregar verificación de dependencia de rev de git al ci
-- Eliminar autorizado de la interfaz de token estándar
-- Actualizar entorno
-- Adaptar a la eliminación de ConversionError de las conversiones de tipos numéricos
-- Actualizar versión a 20.0.0-rc1
-
-#### Soroban RPC
-
-- Listar --network bajo opciones RPC
-- Habilitar eventos de diagnóstico
-- simulateTransaction automáticamente detectará entradas de ledger que requieren restauración
-- simulateTransaction intentará devolver eventos de diagnóstico en caso de fallo
-- getLedgerEntries puede consultar múltiples entradas de ledger a la vez
-- getLedgerEntries puede establecer el número máximo de claves a consultar
-- Las expulsiones temporales de entradas de ledger son ingeridas
-- Admitir formato StrKey para el campo contractIds en la solicitud getEvents
-- Limitar la duración de ejecución de las solicitudes jrpc
-- Correcciones de rendimiento y mejoras: agregar caché de acceso directo para las entradas de ledger de configuración y mejorar los resultados de la base de datos caché
-- Corregir el error de visibilidad de ledgerentry
-- Corregir número de secuencia de simulación para operaciones de actualización/restauración
-- Mejorar el mensaje de argumentos de línea de comando faltantes
-- Agregar configuraciones de configuración que faltan en la caché de entradas de ledger al leer
-- Corregir la caché de GetLatestLedgerSequence
-- Limitar el tamaño de la solicitud a 10MB
-- Limitar el número de solicitudes concurrentes
-- Mejorar HTTPRequestDurationLimiter agregando un manejo de recuperación
-- Transmitir ledgers en la inicialización
-- Incrementar margen de instrucción al 20% en la simulación de transacciones
-- Validar cargas xdr en solicitudes de soroban-rpc
-- Corregir error de conteo doble
-- Corregir race de datos en bufferedResponseWriter.WriteOut
-- Corregir el error set_authorization_entries en la simulación de transacciones
-- Restaurar el soporte CORS
-
-#### Soroban CLI
-
-- Agregar soporte de autorización + firma de múltiples partes
-- Agregar dos nuevos tipos de salida para la inspección de contratos
-- Agregar fondo de identidad de configuración para financiar cuentas en redes
-- Agregar soporte de restauración/actualización con --wash_hash
-- Permitir el paso de verdadero y falso a tipos booleanos
-- Cada método de contrato generado agrega `<contract-arg>-file-path`
-- Agregar dotenv para que los directorios puedan establecer argumentos CLI
-- Los enlaces de TypeScript generados han mejorado significativamente
-- Hacer que Wallet sea inyectable
-- Corregir README generado
-- Permitir la recuperación de contratos de la red
-- Eliminar --contract-name, agregar --overwrite
-- Requerir la configuración de la red
-- Aprovechando el último soroban-client (v1.0.0-beta)
-- Hacer que los alias sean visibles en el documento de ayuda
-- Asegúrese de que los eventos de simulación sean registrados; mejorar el formato de los registros principales
-- Corregir --cost flag
-- Establecer el código de salida a 1 en caso de error
-- Devolver un error una vez que la lectura de contrato no pueda leer ninguna entrada
-- wrap token ya no falla con entradas válidas en modo sandbox
-
-## Vista previa 10 (13 de julio de 2023)
-
-### Software
-
-| Software                                 | Versión                                                                                                                            |
-| ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                                      | [e372df9f677961aac04c5a4cc80a3667f310b29f](https://github.com/stellar/stellar-xdr/commit/e372df9f677961aac04c5a4cc80a3667f310b29f) |
-| Entorno Soroban                          | `v0.0.17`                                                                                                                          |
-| Versión de la Interfaz de Soroban        | `51`                                                                                                                               |
-| Stellar Core                             | `19.12.1-1406.b7d3a8f8d.focal~soroban`                                                                                             |
-| Soroban Rust SDK                         | `v0.9.2`                                                                                                                           |
-| Soroban CLI                              | `v0.9.1`                                                                                                                           |
-| Soroban RPC                              | `v0.9.2`                                                                                                                           |
-| Stellar Horizon                          | `stellar-horizon:2.26.1~soroban-373`                                                                                               |
-| Stellar Friendbot                        | `soroban-v0.0.2-alpha`                                                                                                             |
-| Stellar Quickstart                       | `stellar/quickstart:soroban-dev@sha256:8a99332f834ca82e3ac1418143736af59b5288e792d1c4278d6c547c6ed8da3b`                           |
-| Stellar JS Stellar Base                  | `10.0.0-soroban.3`                                                                                                                 |
-| Stellar JS Soroban Client                | `0.9.2`                                                                                                                            |
-| Freighter                                | `5.2.3`                                                                                                                            |
-| Laboratorio                              | `2.11.0`                                                                                                                           |
-| Aplicación dapp de pago de Soroban React | `1.1.0`                                                                                                                            |
-| Aplicación dapp de token Mint de Soroban | `1.1.0`                                                                                                                            |
-| Frase de paso de la red Futurenet        | `Test SDF Future Network ; October 2022`                                                                                           |
-
-### Registro de cambios
-
-#### XDR
-
-- Eliminar TransactionResultV2
-- Regenerar para una revisión completa de los códigos de error
-- Actualizar xdr
-- Actualizar XDR
-- Actualizar cambios de expiración de estado de XDR
-- Actualizar la versión de rust
-- Actualizar XDR
-- Regenerar para nuevos tipos de costo de cripto
-- Actualizar XDR
-- Actualizar op
-- Generar para la eliminación de tipos de almacenamiento
-- Eliminar ContractCostType::VerifyEcdsaSecp256k1Sig
-- Actualizar el siguiente para recoger los tipos de costo int256
-- Regenerar renombrar
-- Regenerar por error tipográfico
-- Actualizar xdr con cambios de almacenamiento de instancia de contrato
-- Regenerar para la eliminación de ScVal::StorageType
-- Regenerar para RestoreFootprintOp
-- Generar renombre
-- Actualizar crate-git-revision
-
-#### Entorno Soroban
-
-- Mover un montón de código fuera del host, reorganizar módulos ligeramente.
-- Eliminar almacenamiento temporal, soluciona #758
-- Actualizar xdr
-- Características anti
-- Reforma Err
-- Algunas limpiezas adicionales a los eventos de diagnóstico
-- Actualizar xdr
-- Habilitar AUTH_REVOCABLE en los saldos de contrato
-- Implementar subsistema PRNG (ronda 2)
-- Eliminar debug_assert incorrecto de ed25519_pub_key_from_bytes
-- Soporte Auth Next para funciones de host
-- Actualizar xdr
-- Actualizar versión de rust
-- Cambiar a la medición de combustible nativa wasmi
-- Corregir la utilidad de prueba get_authenticated_authorizations.
-- Cambiar errores de contrato de autenticación a errores de autenticación.
-- Mejorar la calibración de VmInstantiation
-- Actualizar la interfaz de almacenamiento para la caducidad del estado
-- Actualizar README.md
-- Implementar aumentos de caducidad de contrato
-- Calibrar el combustible wasmi y las instrucciones wasm en niveles escalonados
-- Actualizar el entorno XDR
-- Implementar `TryFrom<&Error>` para ScVal
-- Proporcionar función de host para autorizar llamadas de contrato profundas del contrato actual
-- Cambiar la autenticación de nonces auto-incrementales a valores aleatorios temporales.
-- Corregir la medición para eventos internos
-- Devolver cadenas para nombre/símbolo y usar strkey para emisor.
-- Eliminar Mergeable y renombrar Exclusive a Persistent
-- Agregar funciones de host para secp256k1 y keccak256
-- Agregar funciones de host para devolver identificaciones de contrato
-- Corregir comparaciones
-- Renombrar rawval a val
-- Imponer huella de solo lectura en el bump
-- Agregar funciones de host para aritméticas `{u,i}256`
-- Más raw a val
-- Soportar Timepoint, Duration
-- Actualizar xdr
-- Comprobar el orden del mapa al reconstruir de iteraciones exactas
-- Actualizaciones para cambios relacionados con la instancia de contrato XDR.
-- Cambiar StorageType a solo ser un Enum
-- Actualizar xdr para RestoreFootprintOp
-- Actualizar xdr para renombrar
-- Agregar función de host para aumentar la instancia del contrato
-- Implementar almacenamiento de instancia de contrato en el host de Soroban.
-- Cambiar las funciones de host aritméticas `[IU]256` para tomar _Val, no _Object.
-- Reemplazar funciones de aumento y disminución con aprobar
-- Exponer aumentos
-- Corregir pruebas de calibración
-- Cambiar las funciones de bytes `[IU]256` `[from,to]_bytes` para trabajar con Val
-- Actualizar versión de wasmi
-
-#### SDK de Rust Soroban
-
-- Corregir comentario de almacenamiento
-- Noop en incremento de instancia para pruebas
-
-#### Soroban RPC
-
-- Actualizar dependencia js-soroban-client de 0.9.0 a 0.9.1
-
-#### Soroban CLI
-
-- Actualizar dependencia js-soroban-client de 0.9.0 a 0.9.1
-
-## Vista previa 9 (24 de mayo de 2023)
-
-### Software
-
-| Software                       | Versión                                                                                                                            |
-| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                            | [2f16687fdf6f4bcfb56805e2035f69997f4b34c4](https://github.com/stellar/stellar-xdr/commit/2f16687fdf6f4bcfb56805e2035f69997f4b34c4) |
-| Entorno Soroban                | `v0.0.16`                                                                                                                          |
-| Versión de interfaz Soroban    | `37`                                                                                                                               |
-| Núcleo Stellar                 | `19.10.1-1310.6649f5173.focal~soroban`                                                                                             |
-| SDK Soroban Rust               | `v0.8.4`                                                                                                                           |
-| Soroban CLI                    | `v0.8.0`                                                                                                                           |
-| Soroban RPC                    | `v0.8.0`                                                                                                                           |
-| Horizon Stellar                | `stellar-horizon:2.25.1~soroban-346`                                                                                               |
-| Stellar Friendbot              | `soroban-v0.0.2-alpha`                                                                                                             |
-| Inicio Rápido de Stellar       | `stellar/quickstart:soroban-dev@sha256:57e8ab498bfa14c65595fbb01cb94b1cdee9637ef2e6634e59d54f6958c05bdb`                           |
-| Stellar JS Stellar Base        | `9.0.0-soroban.1`                                                                                                                  |
-| Stellar JS Soroban Client      | `0.7.0`                                                                                                                            |
-| Freighter                      | `5.0.1`                                                                                                                            |
-| Laboratorio                    | `2.10.0`                                                                                                                           |
-| Frase de Paso de Red Futurenet | `Test SDF Future Network ; octubre de 2022`                                                                                        |
-
-### Registro de cambios
-
-#### XDR
-
-Ver https://github.com/stellar/rs-stellar-xdr/releases v0.0.16 para más detalles.
-
-#### Entorno de Soroban
-
-Ver https://github.com/stellar/rs-soroban-env/releases v0.0.16 para más detalles.
-
-#### SDK Soroban Rust
-
-Ver https://github.com/stellar/rs-soroban-sdk/releases v0.8.4 para más detalles.
-
-#### RPC de Soroban
-
-Ver https://github.com/stellar/soroban-tools/releases v0.8.0 para más detalles.
-
-#### CLI de Soroban
-
-Ver https://github.com/stellar/soroban-tools/releases v0.8.0 para más detalles.
-
-## Vista previa 8 (4 de abril de 2023)
-
-### Software
-
-| Software                          | Versión                                                                                                                            |
-| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                               | [7356dc237ee0db5626561c129fb3fa4beaabbac6](https://github.com/stellar/stellar-xdr/commit/7356dc237ee0db5626561c129fb3fa4beaabbac6) |
-| Entorno de Soroban                | `v0.0.15`                                                                                                                          |
-| Versión de la interfaz de Soroban | `32`                                                                                                                               |
-| Núcleo Stellar                    | `19.8.1-1246.064a2787a.focal~soroban`                                                                                              |
-| SDK Rust de Soroban               | `v0.7.0`                                                                                                                           |
-| CLI de Soroban                    | `v0.7.0`                                                                                                                           |
-| RPC de Soroban                    | `v0.7.0`                                                                                                                           |
-| Horizon Stellar                   | `stellar-horizon:2.24.62~soroban-338`                                                                                              |
-| Stellar Friendbot                 | `soroban-v0.0.2-alpha`                                                                                                             |
-| Stellar Quickstart                | `stellar/quickstart:soroban-dev@sha256:a057ec6f06c6702c005693f8265ed1261e901b153a754e97cf18b0962257e872`                           |
-| Stellar JS Stellar Base           | `8.2.2-soroban.12`                                                                                                                 |
-| Cliente Stellar JS Soroban        | `v0.5.0`                                                                                                                           |
-| Freighter                         | `v2.12.2`                                                                                                                          |
-| Laboratorio                       | `v2.8.0`                                                                                                                           |
-| Frase de Paso de Red Futurenet    | `Test SDF Future Network ; octubre de 2022`                                                                                        |
-
-### Nota de cambios importantes
-
-Esta versión incluye una revisión importante de la representación del valor a nivel de XDR, que potencialmente rompe contratos que dependen de las antiguas definiciones de tipo, aquí hay un resumen de los cambios:
-
-- Se eliminó la división objeto/valor a nivel de XDR
-- Se amplió el tamaño de la etiqueta de valor de 8 a 128 casos
-- Se eliminaron los tipos: `U63`, `Static`, `Bitset`
-- Se añadieron `U256`, `I256` y subtipos de caso especial u64 `Timepoint` y `Duration`
-- Se añadió `String`, que es un objeto similar a `Bytes` pero se muestra como texto
-- Se mejoró `Symbol` para tener un tamaño máximo de 32 bytes (ya no hay un límite de 10 caracteres)
-
-El soporte de SDK también se ha añadido/actualizado para estos tipos. Ver [xdr](https://github.com/stellar/stellar-xdr/pull/70), [env](https://github.com/stellar/rs-soroban-env/pull/682) y [sdk](https://github.com/stellar/rs-soroban-sdk/pull/879) cambios para más detalles.
-
-### Registro de cambios
-
-#### XDR
-
-- Hacer que los tipos que envuelven Strings ya no sean alias
-- Revisión de representación del valor
-- Eventos de diagnóstico
-
-Ver https://github.com/stellar/rs-stellar-xdr/releases v0.0.15 para más detalles.
-
-#### Entorno de Soroban
-
-- Eliminar los eventos de error innecesarios que aparecieron en escenarios no relacionados con errores.
-- Reformar el metering para la clonación de valores y la asignación de memoria.
-- Proporcionar más cobertura de prueba para Auth Next.
-- Verificar la bandera de clawback del emisor cuando se crea un nuevo saldo de contrato.
-- Agregar una prueba que cubra las llamadas a require_auth fuera de orden.
-- Nombre del token en los eventos.
-- Adaptar Almacenamiento y SnapshotSource para usar solo Rc.
-- Agregar funciones de host para convertir direcciones de/para ids de cuenta/contrato.
-- Revisión integral de la representación de valores y objetos.
-- Mover InvokerType de env común a implementación interna del host.
-- Corregir error tipográfico en vec_new_from_linear_memory.
-- Mejorar la seguridad de contratos de cuentas personalizados.
-- Separar DeclaredSizeForMetering de MeteredClone y usarlo para Comparar.
-- Eventos de depuración estructurados.
-- Corregir un error de conversión i128.
-- Utilizar nuevas operaciones de memoria en bloque para tuplas.
-- Medición del presupuesto del host, modelo de costo, cambios de calibración.
-- Aumentar el presupuesto de memoria a 50MB.
-
-Ver https://github.com/stellar/rs-soroban-env/releases v0.0.15 para más detalles.
-
-#### SDK Rust de Soroban
-
-- Agregar documentación en especificaciones para tipos.
-- Renombrar Serialize/Deserialize a To/FromXdr.
-- Utilizar la interfaz source_account() actualizada.
-- Actualizar la documentación de almacenamiento.
-- Exponer funciones de presupuesto de reinicio a testutils.
-- Adaptar la interfaz de almacenamiento y de instantáneas a los cambios del entorno.
-- Agregar utilidades para convertir de/a ids de contrato/cuenta.
-- Revisión integral de la representación de valores y objetos.
-- Agregar un getter para la dirección de un cliente de contrato generada.
-- Utilizar String para log_fmt_values.
-- Agregar una utilidad para llamar a \_\_check_auth en pruebas.
-- Agregar más soporte para los nuevos tipos en soroban-spec.
-- Utilizar inicialización masiva de vectores en Vec.
-- Actualizar el entorno y actualizar por cambios en el evento.
-- corregir(macro): añadir nuevos tipos XDR al analizador.
-- Actualizar prueba de presupuesto.
-- aumentar el entorno y actualizar la impresión del presupuesto.
-
-Ver https://github.com/stellar/rs-soroban-sdk/releases v0.7.0 para más detalles.
-
-#### Soroban RPC
-
-- Establecer una latencia máxima del libro mayor en el método /health.
-- Agregar resultMetaXdr y envelopeXdr de vuelta a la respuesta de getTransaction().
-- Soporte para nuevos eventos de contrato `diagnostic`.
-  - soroban-rpc: añadir soporte de filtrado para eventos de diagnóstico.
-  - soroban-rpc: ingerir eventos de diagnóstico.
-- Eliminar el subcomando 'soroban serve'.
-- Limitar la concurrencia de computación preflight a través de un grupo de trabajadores.
-- Correciones diversas.
-- Mejoras generales en la compilación y pruebas.
-- Agregar eventos de contrato a la respuesta de simulateTransaction.
-
-Ver https://github.com/stellar/soroban-tools/releases v0.7.0 para más detalles.
-
-#### CLI de Soroban
-
-- Documentación mejorada y texto `--help`
-  - feat: documentación CLI completa generada automáticamente.
-- Al usar `invoke`, los nombres de funciones de contrato ahora vienen después del `--`, como `soroban invoke --id <contract_id> -- hello --to "world"`
-- Mejoras en la gestión de identidad
-  - corregir: permitir el uso de ENV para añadir identidad y pasar secreto.
-  - Reemplazados `--identity`, `--secret-key` y `--account` flags. Reemplázalo por un único `--source-account`, que comprende identidades y claves secretas.
-  - característica: añadir mejor documentación para UDT y añadir ejemplos para cada argumento.
-- Añadido `soroban --version`
-- Mejores errores, reemplazando `Desconocido`
-- Refactor, so that the cli can be imported via the new `soroban-test` crate. Esto facilita las pruebas y el uso de soroban-cli como biblioteca.
-  - característica: reorganizar en una biblioteca adecuada.
-  - característica: añadir nuevo crate soroban-test.
-- Actualizar a Clap v4.
-- corregir(CLI): análisis de cadenas/u/i256 XDR.
-- Admitir nuevos eventos de tipo `diagnóstico`
-
-Ver https://github.com/stellar/soroban-tools/releases v0.7.0 para más detalles.
-
-## Preview 7 (February 16th, 2023)
-
-### Software
-
-| Software                          | Versión                                                                                                                            |
-| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                               | [df18148747e807618acf4639db41c4fd6f0be9fc](https://github.com/stellar/stellar-xdr/commit/df18148747e807618acf4639db41c4fd6f0be9fc) |
-| Entorno Soroban                   | `v0.0.14`                                                                                                                          |
-| Versión de la interfaz de Soroban | `29`                                                                                                                               |
-| Stellar Core                      | `19.7.1-1204.871accefc.focal~soroban`                                                                                              |
-| SDK de Rust de Soroban            | `v0.6.0`                                                                                                                           |
-| CLI de Soroban                    | `v0.6.0`                                                                                                                           |
-| RPC de Soroban                    | `0.6.1-13`                                                                                                                         |
-| Stellar Horizon                   | `stellar-horizon:2.24.61~soroban-335`                                                                                              |
-| Stellar Friendbot                 | `soroban-v0.0.2-alpha`                                                                                                             |
-| Stellar Quickstart                | `stellar/quickstart:soroban-dev@sha256:81c23da078c90d0ba220f8fc93414d0ea44608adc616988930529c58df278739`                           |
-| Stellar JS Stellar Base           | `8.2.2-soroban.11`                                                                                                                 |
-| Stellar JS Soroban Client         | `v0.4.0`                                                                                                                           |
-| Freighter                         | `v2.10.0`                                                                                                                          |
-| Laboratorio                       | `v2.7.0`                                                                                                                           |
-| Frase de paso de la red Futurenet | `Red Test SDF Futuro; octubre de 2022`                                                                                             |
-
-### Nota sobre cambios importantes
-
-Esta versión incluye una revisión del enfoque de autorización que afecta a la mayoría de los contratos que realizaban algún tipo de lógica de autorización o utilizaban tokens. [ejemplo](../build/smart-contracts/example-contracts/auth.mdx) y [resumen de la autorización](../learn/fundamentals/contract-development/authorization.mdx) para más detalles.
-
-### Registro de cambios
-
-#### XDR
-
-- Actualizar Rust XDR para Auth Next.
-
-Ver https://github.com/stellar/rs-stellar-xdr/releases v0.0.13 y v0.0.14 para más detalles.
-
-#### Entorno Soroban
-
-- Permitir un presupuesto personalizado fuera de las pruebas
-- Reestructurar el evento para que sea barato de clonar y permitir que se revierta
-- Añadir soporte auth_required para balances que no son de cuentas
-- Reformar TryFromVal para reducir el número de impls
-- Corregir la anulación del hook de pánico durante la prueba cruzada entre contratos
-- Añadir EnvBase::Error, eliminar CheckedEnv, hacer que los métodos de Env devuelvan Error
-- Implementación inicial de Auth Next en Soroban Host
-- Añadir conversiones de 13-tuplas
-- No incluir el estado como el primer argumento de un DebugEvent
-- Añadir una versión más simple de require_auth
-- Usar errores específicos de auth
-- Emular la autenticación clásica de cuentas en el modo de grabación de auth.
-- Cambiar la interfaz para la utilidad de pruebas de autenticación.
-
-Ver https://github.com/stellar/rs-soroban-env/releases v0.0.13 y v0.0.14 para más detalles.
-
-#### Soroban Rust SDK
-
-- Soporte para variantes con múltiples campos en UDTs
-- Error en enumeraciones UDT con variantes de tupla de 0 elementos
-- Permitir actualizaciones del saldo xlm
-- Corregir la inserción de vec
-- Adaptar el SDK a los cambios en `{Try,From,Into}Val` en los crates de env
-- Corregir pop_front de vec
-- Usar un mejor error de almacenamiento en pruebas
-- Adaptarse a la introducción de Env::Error
-- Mejorar errores de compilador para UDTs
-- Permitir tipos y funciones con el mismo nombre
-- Hacer que soroban_token_spec::spec_xdr sea más fácil de mantener actualizado
-- Eliminar el objetivo de makefile optimizado para la construcción
-- Cambios en Auth Next en el SDK
-- Añadir documentación a las entradas de especificación del contrato
-- Soporte del SDK para require_auth simplificado
-
-Ver https://github.com/stellar/rs-soroban-sdk/releases v0.5.0 y v0.6.0 para más detalles.
-
-#### RPC de Soroban
-
-- Configurar límite predeterminado, actualizar la validación de cursor / startLedger, e incluir el último libro mayor para obtener eventos
-- Añadir soporte para AuthNext
-- Corregir error de reversión en los registros
-- Añadir comando getNetwork
-- Implementar almacenamiento de eventos
-- Implementar almacenamiento de entradas del libro mayor
-- Refactorizar paquetes de base de datos e ingestión, añadir ingestión de LedgerCloseMeta
-- Implementar simulateTransaction utilizando rust en lugar de preflight
-- Simplificar la coincidencia de temas para la búsqueda de eventos
-
-Ver https://github.com/stellar/soroban-tools/releases v0.5.0 v0.6.0 para más detalles.
-
-#### CLI de Soroban
-
-- Añadir opción para ejecutar el contrato con presupuesto ilimitado
-- Añadir soporte para AuthNext
-- Añadir comando config
-- Añadir soporte para getNetwork
-- Reorganizar comandos del CLI
-
-Ver https://github.com/stellar/soroban-tools/releases v0.5.0 v0.6.0 para más detalles.
-
-## Preview 6 (January 9th, 2023)
-
-### Software
-
-| Software                          | Versión                                                                                                                          |
-| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                               | [026c9cd074bdb28ddde8ee52f2a4502d9e518a09](https://github.com/stellar/stellar-xdr/tree/026c9cd074bdb28ddde8ee52f2a4502d9e518a09) |
-| Entorno Soroban                   | `v0.0.12`                                                                                                                        |
-| Versión de la interfaz de Soroban | `27`                                                                                                                             |
-| Stellar Core                      | `19.6.1-1158.c0ad35aa1.focal~soroban`                                                                                            |
-| SDK de Rust de Soroban            | `v0.4.2`                                                                                                                         |
-| CLI de Soroban                    | `v0.5.0`                                                                                                                         |
-| RPC de Soroban                    | `0.4.0-10`                                                                                                                       |
-| Stellar Horizon                   | `stellar-horizon:2.22.0~soroban-323`                                                                                             |
-| Stellar Friendbot                 | `soroban-v0.0.2-alpha`                                                                                                           |
-| Stellar Quickstart (amd64)        | `stellar/quickstart:soroban-dev@sha256:c4429def497ed78ca99ae40c8e2522ec932081b4428df992900b5bc8d53bd642`                         |
-| Stellar Quickstart (arm64)        | `stellar/quickstart:soroban-dev@sha256:37205510329845f5fe533bb7c4c182d8f35b3a3515f0a6729889067663e1ec97`                         |
-| Stellar JS Stellar Base           | `8.0.1-soroban.6`                                                                                                                |
-| Stellar JS Soroban Client         | `v0.3.0`                                                                                                                         |
-| Frase de red Futurenet            | `Test SDF Future Network ; October 2022`                                                                                         |
-
-### Registro de cambios
-
-#### Entorno Soroban
-
-- Calibración a nivel de instrucción de Wasm
-- Reemplazar contenedores `im` con `Vec`
-- Eliminar EnvVal
-- Corregir funciones first/last_index_of para usar comparación profunda de objetos
-- Exportar alias de tipo para Almacenamiento y Huella
-- Añadir env.json
-- Eliminar token soroban incorporado
-- Actualizar rust-version
-- Usar saldos individuales en el contrato de activos de Stellar
-- Eliminar clonación innecesaria de i128
-
-Ver https://github.com/stellar/rs-soroban-env/releases v0.0.12 para más detalles.
-
-#### SDK de Rust de Soroban
-
-- Corregir contractimpl para bloques de implementación vacíos
-- actualizar el entorno y corregir la interfaz de token
-- Eliminar init de la interfaz de token
-- Actualizar rust-version
-- Requerir solo un préstamo del Host al actualizar la instantánea del libro mayor
-- Corregir comentarios de documentos y advertencias de clippy en la instantánea del libro mayor
-- Añadir LedgerSnapshot::update(Host)
-- revertir la eliminación de la implementación de token
-- Revertir implementación y actualizar el entorno
-- Eliminar implementación de token en anticipación a la eliminación del token incorporado solo de soroban
-- Hacer que la instantánea del libro mayor cree la ruta del archivo
-- Hacer explícitos los errores en las funciones de la instantánea del libro mayor
-- Actualizar el entorno para incluir cambios de delete-im, remove-EnvVal
-
-Ver https://github.com/stellar/rs-soroban-sdk/releases v0.4.0, v0.4.1, v0.4.2 para más detalles.
-
-#### RPC de Soroban
-
-- Añadir linting de GitHub para código GO
-
-Ver https://github.com/stellar/soroban-tools/releases v0.4.0 para más detalles.
-
-#### CLI de Soroban
-
-- Actualizar la versión de rust
-- StrValError --> Error e implementado usando thiserror
-- Usar soroban-ledger-snapshot para gestionar ledger.json
-- Usa LedgerSnapshot::update para actualizar la imagen en lugar de desempaquetar el host y actualizar la información y las entradas del ledger por separado.
-- Agregar el subcomando de eventos para la visualización de eventos locales y remotos
-- Eliminar el comando de creación de tokens
-
-Ver https://github.com/stellar/soroban-tools/releases v0.4.0 para más detalles.
-
-## Vista previa 5 (8 de diciembre de 2022)
-
-### Software
-
-| Software                          | Versión                                                                                                                          |
-| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
-| XDR                               | [026c9cd074bdb28ddde8ee52f2a4502d9e518a09](https://github.com/stellar/stellar-xdr/tree/026c9cd074bdb28ddde8ee52f2a4502d9e518a09) |
-| Entorno Soroban                   | `v0.0.11`                                                                                                                        |
-| Versión de la Interfaz Soroban    | `26`                                                                                                                             |
-| Stellar Core                      | `stellar-core_19.5.1-1137.b3a6bc281.focal~soroban`                                                                               |
-| SDK de Rust para Soroban          | `v0.3.2`                                                                                                                         |
-| CLI de Soroban                    | `v0.3.3`                                                                                                                         |
-| RPC de Soroban                    | `0.3.1-32`                                                                                                                       |
-| Stellar Horizon                   | `stellar-horizon:2.22.0~soroban-318`                                                                                             |
-| Friendbot Stellar                 | `soroban-v0.0.2-alpha`                                                                                                           |
-| Stellar Quickstart                | `stellar/quickstart:soroban-dev@sha256:8046391718f8e58b2b88b9c379abda3587bb874689fa09b2ed4871a764ebda27`                         |
-| Stellar JS Stellar Base           | `8.0.1-soroban.5`                                                                                                                |
-| Cliente Stellar JS Soroban        | `v0.2.0`                                                                                                                         |
-| Frase de paso de la red Futurenet | `Test SDF Future Network ; October 2022`                                                                                         |
-
-### Registro de cambios
-
-#### XDR
-
-- Eliminar BigInt de ScVal
-- Agregar u128 e i128 a ScVal
-- Cambiar la estructura de eventos en meta
-- Cambiar la estructura de operación de transacción para implementaciones e invocaciones de contratos de Soroban
-
-Ver https://github.com/stellar/stellar-xdr/compare/48d5e17ae63bba0aa9725cd9d18d7438f44c07b1...026c9cd074bdb28ddde8ee52f2a4502d9e518a09 para más detalles.
-
-#### Entorno Soroban
-
-- Actualizar crate-git-revision a 0.0.4 (contribución de [@brson])
-- Agregar Host::with_artificial_test_contract_frame
-- Reestructurar el marco de referencia de rendimiento, agregar código de calibración para todos los CostTypes
-- Deshabilitar los costos de presupuesto para cmp de objeto
-- Cambios de Env para desacoplar la instancia del contrato de la fuente
-- Eliminar BigInt, cambiar todo a u128 e i128
-
-Ver https://github.com/stellar/rs-soroban-env/releases v0.0.10, v0.0.11 para más detalles.
-
-#### SDK de Rust para Soroban
-
-- Renombrar data a storage por @leighmcculloch en #786
-- Agregar posibilidad de obtener el Presupuesto actual desde env en pruebas por @leighmcculloch en #789
-- Agregar Env::as_contract para testutils por @leighmcculloch en #761
-- Actualizar la implementación del contrato para que coincida con los cambios de Env por @dmkozh en #766
-- Hacer contract_id público en los clientes de contratos. por @dmkozh en #768
-- Eliminar BigInt por @sisuresh en #770
-- Agregar soroban-ledger-snapshot
-- Cambiar la salida JSON de gen de flujo a matriz (contribución de [@vinamogit])
-- Contribuciones de [@vinamogit]
-
-Ver https://github.com/stellar/rs-soroban-sdk/releases v0.3.0, v0.3.1, v0.3.2 para más detalles.
-
-#### RPC de Soroban
-
-- Agregar el subcomando de versión de soroban-rpc
-- Agregar un nuevo método jsonrpc getLedgerEntry, desaprobando y reemplazando getContractData que permite a una aplicación obtener cualquier entrada del ledger
-- Se agregó un nuevo método getEvents actualmente respaldado por horizon
-
-Ver https://github.com/stellar/soroban-tools/releases v0.3.0, v0.3.1 para más detalles.
-
-#### CLI de Soroban
-
-- Corregir la instalación de apt-get en el flujo de trabajo de publicación
-- Descripción de tipo agregada a errores al usar --arg (contribución de [@waldmatias])
-- Soporte adicional de CLI para los cambios en la implementación del contrato
-- Agrega soporte para `soroban contract deploy --wasm-hash`, así como `soroban contract install --wasm`
-- Agregar xdr y versión de env a la salida del subcomando de versión
-- Corregir que el footpoint no se estableció correctamente al implementar el contrato de token envuelto (contribución de [@overcat])
-- Contribuciones de [@waldmatias], [@willemneal], [@overcat], [@brson]
-
-Ver https://github.com/stellar/soroban-tools/releases v0.3.0, v0.3.1, 0.3.3 para más detalles.
-
-## Vista previa 4 (15 de noviembre de 2022)
-
-### Software
-
-| Software                          | Versión                                                                                                  |
-| --------------------------------- | -------------------------------------------------------------------------------------------------------- |
-| XDR                               | https://github.com/stellar/stellar-xdr-next/tree/48d5e17ae63bba0aa9725cd9d18d7438f44c07b1                |
-| Entorno Soroban                   | `v0.0.9`                                                                                                 |
-| Versión de la Interfaz Soroban    | `23`                                                                                                     |
-| Stellar Core                      | `19.5.1-1111.4e813f20e.focal~soroban`                                                                    |
-| SDK de Rust para Soroban          | `v0.2.1`                                                                                                 |
-| CLI de Soroban                    | `v0.2.1`                                                                                                 |
-| RPC de Soroban                    | `0.3.1-32`                                                                                               |
-| Stellar Horizon                   | `2.22.0~soroban-304`                                                                                     |
-| Stellar Quickstart                | `stellar/quickstart:soroban-dev@sha256:0993d3350148af6ffeab5dc8f0b835236b28dade6dcae77ff8a09317162f768d` |
-| Frase de paso de la red Futurenet | `Test SDF Future Network ; October 2022`                                                                 |
-
-### Registro de cambios
-
-#### XDR
-
-- Cambios triviales en espacios en blanco
-
-#### Entorno Soroban
-
-- Ajuste de máquina virtual
-- Agregar eventos de token
-- Capturar pánicos de contratos nativos en try_call
-- Mejorar la información de errores de tokens integrados
-- Agregar conversión faltante de Status->ScStatus para la variante ContractError
-- Capturar cadenas de pánico del usuario en compilaciones nativas, evitar el error espurio NoContractRunning
-- Algunas pequeñas correcciones a eventos de depuración de errores
-
-Ver https://github.com/stellar/rs-soroban-env/releases v0.0.7, v0.0.8, v0.0.9 para más detalles.
-
-#### SDK de Rust para Soroban
-
-- Agregar Logger::print en testutils
-- Agregar conversión de Address a Identifier
-- Eliminar funciones obsoletas
-- Eliminar la captura de pánicos y corregir las pruebas que utilizan try_call nativo que ahora funciona
-- Reintroducir un unwrap optimizado que aborta
-- Agregar assert_with_error! macro
-- Renombrar panic_error! a panic_with_error!
-
-Ver https://github.com/stellar/rs-soroban-sdk/releases v0.2.0, v0.2.1 para más detalles.
-
-#### RPC de Soroban
-
-- Lanzamiento inicial
-
-#### CLI de Soroban
-
-- Las cadenas y símbolos se representan como texto en la salida JSON
-- Los bytes se representan como hexágonos en la salida JSON
-- Las cuentas en invocaciones se crean en sandbox
-- Agregar subcomando optimize que optimiza contratos
-- Corregir el nombre del bin en el comando de completado
-- Corregir el problema de cumplimiento con jsonrpc
-
-Ver https://github.com/stellar/soroban-cli/releases v0.2.0, v0.2.1 para más detalles.
-
-## Vista previa 3 (11 de octubre de 2022)
-
-### Software
-
-| Software                          | Versión                                                                                                  |
-| --------------------------------- | -------------------------------------------------------------------------------------------------------- |
-| XDR                               | https://github.com/stellar/stellar-xdr-next/tree/161e2e5b64425a49f9ccfef7f732ae742ed5eec4                |
-| Entorno Soroban                   | `v0.0.6`                                                                                                 |
-| Versión de la Interfaz Soroban    | `23`                                                                                                     |
-| Stellar Core                      | `19.4.1-1097.4e813f20e.focal~soroban`                                                                    |
-| SDK de Rust para Soroban          | `v0.1.1`                                                                                                 |
-| CLI de Soroban                    | `v0.1.2`                                                                                                 |
-| RPC de Soroban                    | ???                                                                                                      |
-| Stellar Horizon                   | `2.22.0~soroban-304`                                                                                     |
-| Stellar Quickstart                | `stellar/quickstart:soroban-dev@sha256:e58d83f92a61f43406087f488dd1cba110a92646dca85f14b3a416163609e853` |
-| Frase de paso de la red Futurenet | `Test SDF Future Network ; October 2022`                                                                 |
-
-### Registro de cambios
-
-Ver https://www.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.
-
-## Vista previa 1 (1 de agosto de 2022)
-
-Ver https://www.stellar.org/blog/project-jump-cannon-soroban-preview-release.
-
-[@waldmatias]: https://github.com/waldmatias
-[@willemneal]: https://github.com/willemneal
-[@overcat]: https://github.com/overcat
-[@brson]: https://github.com/brson
-[@vinamogit]: https://github.com/vinamogit
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/README.mdx
deleted file mode 100644
index 45ff198bd6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/README.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
-# Plataformas SDF
-
-SDF ha open-sourced algunas "plataformas" que facilitan realizar ciertas tareas en la red.
-
-## Plataforma Anchor
-
-La Plataforma Anchor es un conjunto de herramientas y APIs que permiten a desarrolladores y empresas desarrollar sus propios servicios de entrada y salida para la red Stellar. Proporciona una interfaz estandarizada, incluyendo la implementación de varias Propuestas del Ecosistema Stellar (SEPs), para facilitar la integración de empresas con monederos y exchanges basados en Stellar.
-
-[¡Aprende más sobre la API de la Plataforma Anchor aquí!](./anchor-platform/README.mdx)
-
-## Stellar Disbursement Platform
-
-La Stellar Disbursement Platform (SDP) permite a las organizaciones distribuir pagos masivos a destinatarios utilizando Stellar.
-
-[¡Aprende más sobre la API de la Stellar Disbursement Platform aquí!](./stellar-disbursement-platform/README.mdx)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/CONTRIBUTING.md b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/CONTRIBUTING.md
deleted file mode 100644
index ee79fc8646..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/CONTRIBUTING.md
+++ /dev/null
@@ -1,246 +0,0 @@
----
-draft: true
----
-
-# Bienvenido a Anchor Platform Madness <!-- omit in toc -->
-
-¡Hola, y bienvenido a la nueva versión de la documentación de Anchor Platform!
-
-Estamos muy contentos de tenerte aquí, y esperamos que este documento te ayude a comprender cómo (y más importante, _dónde_) hacer los cambios necesarios en nuestra documentación. Comencemos con un poco de vocabulario de Docusaurus, ¿de acuerdo?
-
-## ¡AVISO! AP HA SIDO DESVERSIONADO
-
-La documentación de Anchor Platform ha sido desversionada, y ahora sólo mantenemos una versión "actual" de los documentos. Así que, cualquier cosa en esta página que
-hable de crear una nueva versión, actualizar versiones antiguas, etc., puede ser ignorada.
-
-~~Sin embargo, la documentación de la Plataforma Anchor _todavía_ permanece en su propia instancia de docusaurus. Por lo tanto, la información aquí sobre enlazar dentro y entre instancias sigue siendo relevante. (Esto no será así para siempre, pero por ahora, sí lo es.)~~
-
-¡Ya no es una instancia separada del plugin! Actualizaré este documento pronto, pero por ahora los detalles del enlace se pueden resumir en:
-
-- casi siempre `[usa un](../../relative/link.mdx)` con la extensión del archivo,
-  a menos que estés enlazando desde/hacia un documento de notas de reunión.
-
-## Resumen Rápido (TL;DR)
-
-- Para las versiones _no lanzadas_ de Anchor Platform:
-  - Agrega y edita documentos en `/platforms/anchor-platform`
-  - Actualiza y regenera la documentación de la API en `/openapi/anchor-platform/main-*.yaml`
-- Para las versiones _lanzadas_ de Anchor Platform:
-  - Actualiza y cambia documentos en `/ap_versioned_docs`
-  - Actualiza y regenera la documentación de la API en `/openapi/anchor-platform/versions/*.yaml`
-
-Lanza una **nueva versión** usando el siguiente script de yarn:
-
-```bash
-# replace `3.0.0` with the needed version
-VERSION=3.0.0 yarn ap:versions:new
-```
-
-> _Nota:_ Creo que el comando de yarn anterior actualmente es incompatible con Windows, aunque podría estar equivocado.
-
-Regenera la documentación de la API para versiones **ya lanzadas** usando el siguiente script de yarn. Esto regenera la documentación de la API para **todas** las versiones lanzadas, así que deberías ser selectivo con los archivos que añades a tu commit.
-
-```bash
-yarn ap:versions:regen
-```
-
-## Tabla de Contenidos <!-- omit in toc -->
-
-- [¡AVISO! AP HA SIDO DESVERSIONADO](#notice-ap-has-been-de-versioned)
-- [Resumen Rápido (TL;DR)](#tldr)
-- [Más sobre Docusaurus de lo que nunca quisiste saber](#more-about-docusaurus-than-you-ever-wanted-to-know)
-  - [Nomenclatura de Versiones](#versions-nomenclature)
-  - [Plugins](#plugins)
-  - [Instancias](#instances)
-  - [Enlaces](#links)
-    - [Ejemplos](#examples)
-- [Directorios que Debes Conocer](#directories-to-know)
-  - [Directorios que Ya Conoces](#directories-you-already-know-about)
-  - [Directorios Nuevos y Geniales](#new-shiny-directories)
-- [Creación de Nuevas Versiones](#making-new-versions)
-  - [Usa Docusaurus para "Etiquetar" una Nueva Versión](#use-docusaurus-to-tag-a-new-release)
-  - [Configura el plugin OpenAPI](#configure-the-openapi-plugin)
-    - [Copia los archivos de especificación OpenAPI (empaquetados) al directorio versionado](#copy-the-bundled-openapi-specfiles-to-the-versioned-directory)
-    - [Añade configuración a la instancia del plugin OpenAPI](#add-configuration-to-the-openapi-plugin-instance)
-- [Actualizar versiones antiguas](#updating-old-versions)
-  - [Actualizar páginas de documentación](#update-documentation-pages)
-  - [Actualizar especificación de API](#update-api-specification)
-
-## Más sobre Docusaurus de lo que nunca quisiste saber
-
-Sé que puede parecer un poco misterioso, pero aquí tienes algo de conocimiento y contexto para ayudarte a entender lo que viene.
-
-### Nomenclatura de Versiones
-
-Así es como Docusaurus define estos términos, por lo que usaré esta nomenclatura en este documento también.
-
-- La **versión actual** se refiere a la versión de la documentación de AP contenida en el directorio `/platforms/anchor-platform`. Este conjunto de documentos está disponible en la URL `/platforms/anchor-platform/next`. Este es el conjunto de documentos "en construcción".
-
-- La **última versión** se refiere al conjunto de documentos de AP más recientemente "lanzado". Estos se encuentran en `/ap_versioned_docs` (más sobre esto más adelante), y están disponibles en la URL `/platforms/anchor-platform`. Este es el conjunto "estable" de documentos.
-
-### Plugins
-
-Aquí intervienen dos plugins de Docusaurus:
-
-1. `@docusaurus/plugin-content-docs` es la base de trabajo de Docusaurus. Se encarga del renderizado de markdown, enrutamiento, etc. Cuando piensas en actualizar `some-file.mdx`, este es el plugin que estás usando.
-2. `docusaurus-plugin-openapi-docs` es el plugin que se usa para generar páginas MDX a partir de archivos de especificación OpenAPI. Este plugin es capaz de versionar por sí mismo, por lo que se debe tener cuidado y consideración en cuanto a su configuración.
-
-Ambas configuraciones de plugins se han separado en un archivo `/config/anchorPlatform.config.ts`, para facilitar su gestión y reducir la complejidad del archivo principal `docusaurus.config.ts`.
-
-### Instancias
-
-Aquí las cosas se vuelven un poco más técnicas, pero te prometo que esta parte es útil de conocer. Ambos [plugins](#plugins) que mencioné antes son realmente sólo _instancias_ de esos dos plugins. De hecho, cada uno de esos plugins se usa en otras partes de nuestro sitio de documentación para Horizon, SDP, y la documentación "regular". _Generalmente_ no es importante tener en cuenta las diferentes instancias de plugins, pero sí es **muy relevante** cuando hablamos de enlaces. Así que...
-
-### Enlaces
-
-> [!ADVERTENCIA]
->
-> Esta sección está desactualizada. Por ahora, ignorala en su mayoría.
-
-La mayoría de las veces, **especialmente en documentos versionados**, es importante [enlazar a otros documentos usando rutas de archivo _relativas_](https://docusaurus.io/docs/versioning#link-docs-by-file-paths).
-Esto permite que Docusaurus reescriba URLs cuando es necesario en tiempo de compilación.
-
-¡Sin embargo, hay una **EXCEPCIÓN GRANDE**! Docusaurus sólo puede manejar estos enlaces cuando los archivos fuente y destino son procesados por la misma _instancia del plugin_.
-Entonces, en términos prácticos:
-
-- Si estás enlazando _desde_ y _hacia_ documentos MDX _dentro_ de la misma instancia del plugin de documentos, usa rutas de archivo _relativas_.
-- Si estás enlazando _entre_ instancias de plugins, **debes** usar rutas de _URL_. Por convención, usamos rutas _absolutas_ para esto también, para hacer un poco más obvio cuándo está sucediendo este comportamiento.
-
-#### Ejemplos
-
-Esto debería ayudar a aclararlo un poco.
-
-- Quiero enlazar _desde_ el documento MDX `/platforms/anchor-platform/sep-guide/sep6/configuration.mdx` _hacia_ el documento MDX `/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx`:
-  - Estamos en la misma instancia del plugin `/platforms/anchor-platform`.
-  - Usa una ruta de archivo **relativa**
-  - Enlázalo `[algo así](../../api-reference/platform/rpc/methods/notify_amounts_updated.mdx)`
-- Quiero enlazar _desde_ el documento MDX `/docs/learn/fundamentals/anchors.mdx` _hacia_ el documento MDX `/platforms/anchor-platform/admin-guide/getting-started.mdx`
-  - Estamos "cruzando" entre las instancias del plugin `/docs` y `/platforms/anchor-platform`.
-  - Usa una ruta de **URL absoluta**
-  - Enlázalo `[algo así](/platforms/anchor-platform/admin-guide/getting-started)` (nota que no hay extensión `.mdx`)
-- Quiero enlazar _desde_ el documento MDX `/platforms/anchor-platform/README.mdx` _hacia_ el documento MDX `/docs/tools/developer-tools/wallets.mdx`
-  - Estamos "cruzando" entre las instancias del plugin `/platforms/anchor-platform` y `/docs`.
-  - Usa una ruta de **URL absoluta**
-  - Enlázalo `[algo así](/docs/tools/developer-tools/wallets)` (nota que no hay extensión `.mdx`)
-- ¡Comodín! Quiero enlazar _desde_ el documento MDX `/platforms/anchor-platform/admin-guide/events/configuration.mdx` _hacia_ el documento MDX `/platforms/stellar-disbursement-platform/admin-guide/60-anchor-platform-integration-points.mdx`
-  - Estamos "cruzando" entre las instancias del plugin `/platforms/anchor-platform` y `/platforms/stellar-disbursement-platform`.
-  - Usa una ruta de **URL absoluta**
-  - Enlázalo `[algo así](/platforms/stellar-disbursement-platform/admin-guide/anchor-platform-integration-points)` (nota que no hay extensión `.mdx`)
-
-> _Nota:_ Reemplaza la instancia del plugin `/platforms/anchor-platform` con la instancia `/platforms/stellar-disbursement-platform` en los ejemplos anteriores, y todo funciona prácticamente igual.
-
-Lee más sobre enlaces [aquí](https://docusaurus.io/docs/markdown-features/links) (especialmente hacia el final de la página).
-
-## Directorios que Debes Conocer
-
-Hay varios directorios que _todos_ alimentan el producto final que es nuestra documentación versionada de AP.
-
-### Directorios que Ya Conoces
-
-- `/platforms/anchor-platform`: Aquí es donde estás ahora, y tradicionalmente ha sido el lugar para modificar cualquier contenido markdown que se convierta en nuestras páginas de documentación de AP. No ha cambiado mucho aquí, excepto que requiere un cambio de mentalidad.
-  **Toda la documentación y contenido ubicado aquí ahora debe considerarse la versión `actual` (en construcción) de los documentos de AP.** Así que, mientras construimos para `v3.x` (y más adelante), querrás actualizar _el contenido aquí_.
-  Los lectores aún podrán _ver_ este contenido antes de que se "lance", pero se les informará que es la versión no lanzada.
-
-  También hay un nuevo directorio aquí que debes conocer:
-
-  - `/platforms/anchor-platform/assets`: Como es probable que las diversas imágenes, diagramas, etc., necesiten actualizarse o cambiarse de una versión a otra, estamos ubicando los activos relevantes en este directorio. Esto
-    permite que también sean versionados. Si quieres actualizar un diagrama o imagen para un próximo lanzamiento, deberías hacerlo aquí.
-
-- `/openapi/anchor-platform`: Este es probablemente el lugar con el que ya estás familiarizado. Los archivos han sido renombrados recientemente, pero en su mayoría querrás modificar `main-{platform,callbacks,custody}.yaml`, que luego será "empaquetado" más adelante en un solo archivo que contiene todo.
-  **Los archivos en este directorio también deben considerarse la versión `actual` (en construcción) de los documentos de especificación de AP.** Así que, mientras construimos para `v3.x` (y más adelante), querrás actualizar _los archivos de especificación aquí_.
-
-  También hay un nuevo directorio aquí que debes conocer:
-
-  - `/openapi/anchor-platform/versions`: Este directorio almacena una copia de los archivos de especificación _empaquetados_ para cada versión que se lanza. El plugin que usamos para generar la documentación de la API a partir de estos archivos de especificación se configura para usar _estas_ especificaciones versionadas para toda la documentación que no sea la `actual`.
-
-- `/openrpc/src/anchor-platform`: Recientemente, movimos la especificación RPC a este directorio para que pueda beneficiarse de los mismos procesos de construcción y verificaciones de validación que la especificación `stellar-rpc`. Al igual que con los otros directorios cubiertos hasta ahora, cualquier cambio en estos archivos debe considerarse parte de la versión `actual` (en construcción) de la documentación. No hay (¿todavía?) muchas herramientas o ergonomía para actualizar las versiones "antiguas" de estas especificaciones. La versión `actual` de la especificación se genera en `/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json`.
-  Esto significa que _sí_ se incluye en el proceso de versionado, así que cualquier cambio en versiones "antiguas" probablemente sólo necesite hacerse en esos archivos de especificación versionados por ahora (más sobre eso en la siguiente sección).
-
-### Directorios Nuevos y Geniales
-
-- `/ap_versioned_sidebars`: Podemos pasar rápidamente por este. Cuando haces una nueva versión de la documentación, Docusaurus almacena una copia de la barra lateral en ese momento. Realmente no deberías molestarte con nada aquí.
-
-- `/ap_versioned_docs`: Aquí es donde viven los conjuntos "lanzados" de la documentación de AP.
-  Cada vez que se lanza una versión, _todo_ lo que está dentro del directorio `/platforms/anchor-platform` se copia en un subdirectorio aquí.
-  Notarás que ya tenemos una versión `v2.8.4` aquí. Cuando lancemos `v3.x`, se colocará una
-  _nueva_ copia de los archivos aquí. La copia `latest` (estable) de los documentos de AP se extrae desde este directorio. Si encuentras algo para corregir o actualizar en una versión lanzada de la documentación, tendrás que actualizarlo aquí.
-
-## Creación de Nuevas Versiones
-
-Como se señaló en el [Resumen Rápido (TL;DR)](#tldr), este proceso se automatiza con el script `VERSION=3.0.0 yarn ap:versions:new`. Sin embargo, esto es lo que sucede bajo el capó de ese script.
-
-### Usa Docusaurus para "etiquetar" un nuevo lanzamiento
-
-¡Es realmente bastante simple! Usa la CLI de Docusaurus para hacer un nuevo lanzamiento:
-
-```bash
-# `ap` is the ID of the AP `@docusaurus/plugin-content-docs` plugin instance
-yarn docusaurus docs:version:ap 3.0.0
-```
-
-Esto crea una nueva copia de los documentos en `/ap_versioned_docs`, y funcionará correctamente para mostrar la nueva versión en el sitio. Cualquier cambio futuro en la versión 3.0.0 de los documentos debe hacerse dentro del directorio `/ap_versioned_docs`.
-
-### Configura el plugin OpenAPI
-
-También necesitaremos poder modificar/actualizar/regenerar la documentación de la API si surge la necesidad. Así que necesitaremos configurar adecuadamente la instancia de plugin `docusaurus-plugin-openapi-docs`.
-
-#### Copia los archivos de especificación OpenAPI (empaquetados) al directorio versionado
-
-Por el momento, es tan simple como copiar los archivos:
-
-```bash
-cp openapi/anchor-platform/bundled-platform.yaml openapi/anchor-platform/versions/platform-3.0.0.yaml
-cp openapi/anchor-platform/bundled-callbacks.yaml openapi/anchor-platform/versions/callbacks-3.0.0.yaml
-cp openapi/anchor-platform/bundled-custody.yaml openapi/anchor-platform/versions/custody-3.0.0.yaml
-```
-
-> Observa que estamos copiando el archivo _empaquetado_, no el archivo _principal_. Esto asegura que el archivo versionado contiene todo lo que necesita.
-
-#### Añade configuración a la instancia del plugin OpenAPI
-
-> _Nota:_ Estas partes `versions` de la configuración ahora se generan dinámicamente, usando una función `makeVersions()`, así que estos pasos manuales de configuración no deberían ser necesarios. _Puede que_ quieras avanzar o ajustar la cadena `anchorPlatformNextVersion` en el archivo de configuración cuando lances una nueva versión de la documentación.
-
-Para poder usar el CLI del plugin para actualizar versiones ya lanzadas, tenemos que actualizar la configuración en `/config/anchorPlatform.config.ts`. Haz una nueva entrada en el objeto `versions` de cada archivo de especificación, y copia el formato de las entradas que ya existen. Para referencia, así es como se ve actualmente para el "servidor de la plataforma" en `v2.8.4`:
-
-```typescript
-ap_platform: {
-  specPath: "openapi/anchor-platform/bundled-platform.yaml",
-  outputDir: "platforms/anchor-platform/api-reference/platform/transactions",
-  hideSendButton: true,
-  template: "src/template.mustache",
-  version: "3.0.0",
-  label: "v3.0.0",
-  baseUrl: '/platforms/anchor-platform/next/api-reference/platform/transactions',
-  versions: {
-    "2.8.4": {
-      specPath: "openapi/anchor-platform/versions/platform-2.8.4.yaml",
-      outputDir: "ap_versioned_docs/version-2.8.4/api-reference/platform/transactions",
-      label: "v2.8.4",
-      baseUrl: "/platforms/anchor-platform/api-reference/platform/transactions"
-    }
-  }
-}
-```
-
-## Actualizar versiones antiguas
-
-### Actualizar páginas de documentación
-
-Supongamos que encuentro un error ortográfico en la documentación de la Guía del Administrador `v2.8.4`. Encuentra el archivo relevante en el directorio `/ap_versioned_docs/version-2.8.4`, corrígelo y haz commit. Las actualizaciones de contenido son bastante sencillas aquí.
-
-> _Nota_: Dado que la especificación RPC se trata de manera similar a los documentos MDX, usa el mismo proceso para hacer actualizaciones en el archivo de especificación RPC. Para `v2.8.4`, está ubicado aquí: `/ap_versioned_docs/version-2.8.4/api-reference/platform/rpc/anchor-platform.openrpc.json`.
-
-### Actualizar especificación de API
-
-Esto es un poco más complejo, pero no mucho. Encuentra y cambia la(s) parte(s) relevante(s) del archivo de especificación `/openapi/anchor-platform/versions/{platform, callbacks,custody}-2.8.4.yaml`.
-
-Luego, regenera las páginas MDX:
-
-```bash
-# `ap-apis` is the ID of the AP `docusaurus-plugin-openapi-docs` plugin instance
-yarn docusaurus gen-api-docs:version -p ap-apis:2.8.4
-```
-
-> _Nota:_ Puedes usar un script de yarn para regenerar automáticamente la documentación de API para **todas** las versiones lanzadas: `yarn ap:versions:regen`. Esto regenera todas las versiones, así que querrás ser selectivo con los archivos que añades al commit.
-
-Haz commit de los cambios y estarás listo para continuar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/README.mdx
deleted file mode 100644
index 0cc835215a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/README.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: "La Plataforma Anchor: Construir y Gestionar On/Off-Ramps en la Red Stellar"
-sidebar_position: 10
-sidebar_label: Resumen del Producto
-description: Aprende cómo la Plataforma Anchor (AP) simplifica el proceso de construir y gestionar un on y off-ramp en Stellar. Conoce cómo integrarte con la AP o obtener información sobre la API.
----
-
-# Plataforma Anchor
-
-La Plataforma Anchor proporciona un conjunto de herramientas y APIs para construir servicios de on y off-ramp en la red Stellar. Con interfaces estandarizadas y la implementación completa de propuestas clave del ecosistema Stellar (SEPs), simplifica la integración con billeteras y exchanges basados en Stellar, permitiéndote centrarte en la lógica principal de tu negocio en lugar de en los detalles de implementación del protocolo.
-
-## SEPs compatibles
-
-La Plataforma Anchor implementa las siguientes propuestas del ecosistema Stellar:
-
-- **[SEP-1](sep-guide/sep1/README.mdx)** — Archivo Stellar.toml para descubrimiento de servicios
-- **[SEP-6](sep-guide/sep6/README.mdx)** — Operaciones de depósito y retiro
-- **[SEP-10](sep-guide/sep10/README.mdx)** — Autenticación web usando transacciones de desafío/respuesta
-- **SEP-12** — Gestión de datos KYC/AML de clientes
-- **[SEP-24](sep-guide/sep24/README.mdx)** — Flujos interactivos de depósito y retiro
-- **[SEP-31](sep-guide/sep31/integration.mdx)** — Procesamiento de pagos transfronterizos (solo recepción)
-- **SEP-38** — Cotizaciones y servicios de tasa de cambio
-- **[SEP-45](sep-guide/sep45/README.mdx)** — Autenticación web usando desafíos/respuestas para cuentas de contrato
-
-## Características clave
-
-- **Implementaciones completas de SEP** — Soporte total para flujos de trabajo de depósito, retiro y procesamiento de pagos
-- **Autenticación y autorización** — Soporte para SEP-10 y SEP-45 tanto para cuentas tradicionales como de contrato inteligente
-- **Gestión de clientes** — Integración SEP-12 para cumplimiento KYC/AML y manejo de datos de clientes
-- **Procesamiento de transacciones** — Gestión completa del ciclo de vida de transacciones con seguimiento de estado y callbacks por webhook
-- **Servicios de cotización y exchange** — Integración SEP-38 para descubrimiento de precios y cálculos de tasas de cambio
-- **Soporte multiactivo** — Configuración flexible para múltiples activos con varios métodos de depósito y retiro
-- **Soporte para contratos inteligentes** — Soporte nativo para cuentas de contrato Stellar (cuentas C) mediante SEP-45
-
-## Enlaces de documentación
-
-- **[Arquitectura](./admin-guide/architecture.mdx)** — Arquitectura del sistema y descripción de componentes
-- **[Comenzar](./admin-guide/getting-started.mdx)** — Instrucciones para configuración inicial y despliegue
-- **[Manejo de Eventos](./admin-guide/events/README.mdx)** — Entrega de eventos, webhooks y patrones de integración
-- **[Guías SEP](./sep-guide/README.mdx)** — Guías de implementación para propuestas del ecosistema Stellar
-- **[Referencia de API](./api-reference/README.mdx)** — Documentación completa y referencia de la API
-
-## Recursos adicionales
-
-La documentación para la Plataforma Anchor está en desarrollo. Los desarrolladores pueden explorar el código y la documentación existente en el [repositorio de GitHub](https://github.com/stellar/java-stellar-anchor-sdk).
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
-[sep-12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
-[anchor-platform-github]: https://github.com/stellar/java-stellar-anchor-sdk
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/README.mdx
deleted file mode 100644
index e9a995c616..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Guía del Administrador
-sidebar_position: 10
----
-
-import DocCardList from "@theme/DocCardList";
-
-Todo lo que necesitas saber sobre cómo configurar, ejecutar y utilizar la Plataforma Anchor.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/_category_.json
deleted file mode 100644
index 1d4401ab2f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/_category_.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
-  "label": "Admin Guide",
-  "collapsed": false
-}
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/architecture.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/architecture.mdx
deleted file mode 100644
index 53fa520e6e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/architecture.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Arquitectura
-sidebar_position: 20
----
-
-## Arquitectura
-
-Antes de comenzar con la Anchor Platform, familiaricémonos con la arquitectura. Esta sección describirá los componentes involucrados y cómo interactúan.
-
-### Arquitectura Fundamental
-
-Los siguientes componentes arquitectónicos son necesarios para todas las implementaciones de la Anchor Platform.
-
-<div style={{width: '600px'}}>
-
-![arquitectura fundamental de Anchor Platform](/assets/ap/anchor-platform-architecture-1.png)
-
-</div>
-
-#### Cliente
-
-El cliente es una aplicación, como un monedero o remitente de transferencias, que actúa en nombre de un usuario y realiza solicitudes al sistema. Los clientes hacen solicitudes al componente servidor SEP de la Anchor Platform usando conjuntos de estándares llamados [SEPs][seps] (Stellar Ecosystem Proposals).
-
-#### Servidor SEP
-
-El servidor SEP es un servidor orientado al cliente y debe ser accesible desde una red externa. El servidor SEP procesa las solicitudes de los usuarios y gestiona el estado de las transacciones que inician. Cuando el servidor SEP necesita proporcionar información que no tiene al cliente, como la tasa de cambio para un par de activos o el estado KYC de un cliente, realiza solicitudes síncronas de [callback][callback-api] al servidor de negocio y devuelve la información en un formato compatible con SEP.
-
-:::note
-
-El servidor SEP nunca almacenará información sensible, como KYC (PII), en la base de datos.
-
-:::
-
-#### Servidor de Negocio
-
-El servidor de negocio es un servicio que tú (el negocio) debes implementar para conectar la Anchor Platform con tus sistemas internos. El servidor de negocio responde a solicitudes de callback enviadas por el servidor SEP, como solicitudes de cotización, recibe eventos enviados por el servicio de eventos, como notificaciones de pagos recibidos en tu cuenta Stellar, y proporciona actualizaciones al servidor de plataforma cuando ocurren eventos fuera de cadena, como la iniciación de una transferencia bancaria a un cliente.
-
-#### Servidor de Plataforma
-
-El servidor de plataforma es un componente interno. Debe estar alojado en una red privada y no debe ser accesible desde Internet. Este servidor permite al negocio obtener y actualizar el estado de las transacciones usando su [API][platform-api].
-
-#### Base de Datos
-
-La Anchor Platform utiliza una base de datos PostgreSQL para almacenar eventos y entidades Stellar. Se usa principalmente para almacenar transacciones.
-
-#### Kafka
-
-Kafka se utiliza como eje de mensajería para la Anchor Platform, facilitando la comunicación y las interacciones basadas en eventos entre diferentes componentes. Permite que componentes como el servidor SEP, el servidor de negocio y el servicio de eventos publiquen y se suscriban a eventos de transacciones y pagos de manera confiable y escalable.
-
-### Arquitectura Completa
-
-Además de los componentes descritos arriba, la Anchor Platform incluye varios otros componentes que ofrecen funcionalidad adicional. Tu negocio puede elegir cuáles de los componentes adicionales usar, pero el diagrama a continuación visualiza la arquitectura del sistema si se utilizan todos los componentes.
-
-<div style={{ width: "800px" }}>
-  [![arquitectura completa de Anchor Platform](/assets/ap/anchor-platform-architecture-2.png)](/assets/ap/anchor-platform-architecture-2.png)
-</div>
-#### Servicio de Eventos
-
-El servicio de eventos permite que la Anchor Platform envíe webhooks HTTP a clientes registrados y a tu servidor de negocio cuando cambia el estado de las transacciones, eliminando la necesidad de que los clientes y/o tu servidor de negocio consulten continuamente las APIs de Anchor Platform. Funciona leyendo eventos publicados en un tópico de Kafka por otros componentes de Anchor Platform. [Lee más][events] sobre el uso del servicio de eventos.
-
-#### Observador de Pagos
-
-El Observador de Pagos monitorea la cadena de bloques Stellar usando Stellar RPC o Horizon, detecta automáticamente pagos relacionados con el negocio y actualiza las transacciones correspondientes en la base de datos de Anchor Platform. Si también usas el servicio de [events], los pagos a tus cuentas activarán un callback HTTP hacia tu servidor de negocio.
-
-Si ya tienes una solución para monitorear pagos a tus cuentas Stellar, como una integración con tu exchange, Horizon o RPC, entonces este componente no es necesario, aunque tu servidor de negocio deberá notificar a Anchor Platform cuando se haya realizado un pago asociado a una transacción de Anchor Platform a una de tus cuentas Stellar vía la [Platform API][platform-api].
-
-[seps]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/README.md
-[platform-api]: ../api-reference/platform/transactions/README.mdx
-[callback-api]: ../api-reference/callbacks/README.mdx
-[events]: ./events/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx
deleted file mode 100644
index e530c7933b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/assets-and-client-wallets.mdx
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Activos y Clientes de Billeteras
-sidebar_position: 40
----
-
-# Activos y Clientes de Billeteras
-
-Esta guía explica cómo configurar activos y clientes de billeteras en la Anchor Platform.
-
-## Configuración de Activos
-
-Los activos definen los tokens y monedas que tu Anchor Platform admite para depósitos y retiradas de fondos. En la guía "Comenzar", los activos se configuran en el archivo `config/assets.yaml` mediante el `ap_start.sh`.
-
-Para la lista completa de campos y valores por defecto, consulta la [referencia de configuración de activos](https://github.com/stellar/anchor-platform/blob/develop/core/src/main/resources/config/anchor-asset-default-values.yaml).
-
-### Ejemplo de Configuración de Activos
-
-```yaml
-items:
-  - id: stellar:native
-    distribution_account: "G...DIST"
-    significant_decimals: 7
-    sep6:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - SEPA
-          - SWIFT
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - bank_account
-          - cash
-    sep24:
-      enabled: true
-    sep31:
-      enabled: true
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - iso4217:USD
-```
-
-### Explicación de Campos
-
-- **`id`** (Obligatorio) - El identificador del activo en el formato `SCHEMA:CODE:(ISSUER)` o `stellar:native` que representa XLM, el activo nativo de Stellar. Por ejemplo, `stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5` representa Circle USD. Para monedas fiat, usa `iso4217:CODE` (por ejemplo, `iso4217:USD`, `iso4217:CAD`).
-
-- **`distribution_account`** - La dirección de cuenta Stellar que posee el activo para distribución. No es necesario para activos fiat (`iso4217`).
-
-- **`significant_decimals`** - La cantidad de decimales que el activo admite.
-
-- **`sep6`** - Habilita SEP-6 y configura los límites y métodos de depósito/retirada por activo.
-
-- **`sep24`** - Habilita los flujos interactivos SEP-24 y sus configuraciones por activo.
-
-- **`sep31`** - Habilita el soporte para pagos transnacionales SEP-31 para el activo.
-
-- **`sep38`** - Habilita las cotizaciones SEP-38 y `exchangeable_assets` para pares de monedas admitidos.
-
-## Configuración de Clientes de Billeteras
-
-Los clientes de billeteras son las aplicaciones que se conectan a tu Anchor Platform para realizar transacciones en nombre de los usuarios.
-
-Para la lista completa de campos y valores por defecto de los clientes, consulta la [referencia de configuración de clientes](https://github.com/stellar/anchor-platform/blob/main/platform/src/main/resources/config/anchor-client-default-values.yaml).
-
-### Ejemplo de Configuración de Cliente
-
-```yaml
-items:
-  - name: "referenceCustodial"
-    type: custodial
-    signing_keys:
-      - GDJLB...KLTG
-    callback_urls:
-      sep6: https://client.example.com/callbacks/sep6
-      sep24: https://client.example.com/callbacks/sep24
-      sep31: https://client.example.com/callbacks/sep31
-      sep12: https://client.example.com/callbacks/sep12
-  - name: "reference"
-    type: noncustodial
-    domains:
-      - wallet-server:8092
-      - client.example.com
-    callback_urls:
-    ...
-```
-
-### Explicación de Campos
-
-**Configuración de Cliente Custodial:**
-
-- **`name`** (Obligatorio) - Un identificador único para el cliente.
-
-- **`type: custodial`** (Obligatorio) - El tipo de cliente. Debe establecerse en `custodial` para clientes custodiales.
-
-- **`signing_keys`** (Obligatorio) - Una lista de claves públicas Stellar usadas para la autenticación SEP-10 del cliente. El anchor usa estas claves para verificar que las solicitudes provienen del cliente autorizado.
-
-- **`callback_urls`** (Opcional) - URLs a las que el servicio puede enviar callbacks para diferentes tipos SEP.
-  - **`sep6`** - URL de callback para actualizaciones de estado de transacciones SEP-6 (depósito/retirada)
-  - **`sep24`** - URL de callback para actualizaciones de estado de transacciones SEP-24 (depósito/retirada interactivo)
-  - **`sep31`** - URL de callback para actualizaciones de estado de transacciones SEP-31 (pagos transnacionales)
-  - **`sep12`** - URL de callback para actualizaciones de información de clientes SEP-12 (KYC)
-
-**Configuración de Cliente No Custodial:**
-
-- **`name`** (Obligatorio) - Un identificador único para el cliente, similar al de clientes custodiales. Típicamente un nombre que representa claramente la entidad cliente.
-
-- **`type: noncustodial`** (Obligatorio) - El tipo de cliente. Debe establecerse en `noncustodial` para clientes no custodiales. Los clientes no custodiales permiten a los usuarios controlar sus propias claves privadas, y la billetera actúa como interfaz para cuentas controladas por el usuario.
-
-- **`domains`** (Obligatorio) - Una lista de dominios asociados con el cliente, usada para verificar su identidad.
-
-- **`callback_urls`** (Opcional) - URLs a las que el servicio puede enviar callbacks para diferentes tipos SEP. Funciona de la misma manera que para clientes custodiales (ver arriba).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/observer/observer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/observer/observer.mdx
deleted file mode 100644
index 58a8364998..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/observer/observer.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
-Usar el Payment Observer te permite delegar este paso a la Anchor Platform. Para habilitar el Payment Observer, usa el flag `--stellar-observer` en la sección de comandos del [archivo compose](../../getting-started.mdx#configuration).
-
-El Payment Observer rastreará todas las transacciones enviadas a la cuenta de distribución. Cuando se detecta la transacción con el memo esperado en la red, el estado cambiará automáticamente a `pending_anchor` y se emitirá un evento (si se usa Kafka).
-
-Para actualizar los estados de la transacción, el observer realiza las solicitudes JSON-RPC correspondientes a la plataforma. Debe usar la siguiente URL.
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_BASE_URL=http://platform-server:8085
-```
-
-</CodeExample>
-
-:::caution
-
-El Payment Observer no validará los montos. Es tu responsabilidad verificar que el monto enviado por el usuario sea correcto.
-
-:::
-
-:::info
-
-Si ya tienes un sistema que monitorea pagos, asegúrate de que la lógica del sistema coincida con la descripción a continuación:
-
-Primero, espera a que la transacción sea incluida en el libro mayor (usando un SDK). Esta transacción debe tener el memo esperado y la dirección de destino (cuenta de distribución). Una vez que esta transacción haya sido detectada y verificada, notifica al usuario que los fondos han sido recibidos usando la solicitud JSON-RPC [notify_onchain_funds_received](#funds-received-1).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/error.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/error.mdx
deleted file mode 100644
index 435038af4b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/error.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-<div>
-
-| Código de error | Significado                                           |
-| :-------------- | :---------------------------------------------------- |
-| \-32600         | El JSON enviado no es un objeto Request válido        |
-| \-32601         | El método no existe o no está disponible              |
-| \-32602         | Parámetro(s) del método no válido(s)                  |
-| \-32603         | Error interno JSON-RPC                                |
-
-</div>
-
-:::tip
-
-También haremos referencia a una variable `$transaction_id`. Esta es una identificación de la transacción que se devuelve desde la Plataforma Anchor en una solicitud de inicio de retiro o depósito. Puedes obtener el ID de la transacción conectando la cartera de prueba a tu instancia local de la Plataforma Anchor.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/request.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/request.mdx
deleted file mode 100644
index 7721a19ba7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/request.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
-El objeto Request debe contener los siguientes atributos:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- jsonrpc
-  - cadena
-  - Una cadena que especifica la versión del protocolo JSON-RPC. DEBE ser exactamente "2.0"
-- method
-  - cadena
-  - Una cadena que contiene el nombre del método a invocar. La lista de métodos disponibles puede verse en [Métodos JSON-RPC][json-rpc-methods]
-- params
-  - objeto
-  - Un valor estructurado que contiene los parámetros correspondientes a la llamada del método, que se usarán durante la invocación del método.
-- id
-  - cadena
-  - Un identificador establecido por el cliente. El Servidor responderá con el mismo valor en el objeto Response.
-
-</AttributeTable>
-
-:::tip
-
-Es posible proporcionar varias actualizaciones en una sola solicitud JSON-RPC (colocando varios objetos de solicitud JSON-RPC). Cuando una actualización se realiza de esta forma, todas las actualizaciones se harán secuencialmente.
-
-Lo más importante es que cada solicitud JSON-RPC no es atómica. Si una actualización falla, todas las actualizaciones anteriores se APLICARÁN y todas las actualizaciones posteriores también se procesarán y APLICARÁN.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/response.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/response.mdx
deleted file mode 100644
index 61ba90b81e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/response.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
-La respuesta se expresa como un solo objeto JSON, con los siguientes atributos:
-
-<AttributeTable>
-
-- ATRIBUTO
-  - TIPO DE DATO
-  - DESCRIPCIÓN
-- jsonrpc
-  - cadena
-  - Una cadena que especifica la versión del protocolo JSON-RPC. Está establecido en "2.0"
-- result
-  - objeto
-  - Un valor estructurado que contiene los detalles actualizados de la transacción
-- id
-  - cadena
-  - Un identificador enviado por el cliente
-- error
-  - objeto
-  - Un valor estructurado que contiene los detalles del error
-    - id
-      - cadena
-      - Id único de la transacción para la cual ocurrió un error
-    - code
-      - número
-      - Un número que indica el tipo de error que ocurrió. Por favor ve una lista de [códigos de error](#error-codes) abajo
-    - message
-      - cadena
-      - Una cadena que proporciona una breve descripción del error
-    - data
-      - cadena
-      - Un valor primitivo o estructurado que contiene información adicional sobre el error
-
-</AttributeTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/rpc.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/rpc.mdx
deleted file mode 100644
index bc2ecb5eb8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/rpc/rpc.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
-Antes de hacer solicitudes JSON-RPC, primero vamos a crear una plantilla para hacer una solicitud a la Plataforma Anchor.
-
-<CodeExample>
-
-```bash
-# call-json-rpc.sh
-#!/usr/bin/env bash
-
-curl localhost:8085 \
-    -X POST \
-    -H 'Content-Type: application/json' \
-    --data "@$1"
-```
-
-</CodeExample>
-
-Este pequeño script hará una solicitud JSON-RPC a la Plataforma Anchor alojada en el puerto predeterminado (8085). Los datos de la transacción JSON almacenados en el archivo proporcionado se usarán como cuerpo (las solicitudes deben ser un arreglo).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/api_key.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/api_key.mdx
deleted file mode 100644
index 7e1de23599..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/api_key.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-Para habilitar la autenticación mediante clave API, modifica tu archivo `dev.env`:
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_AUTH_TYPE=api_key
-# Will be used as API key
-SECRET_PLATFORM_API_AUTH_SECRET="your API key that business server will use"
-```
-
-</CodeExample>
-
-Una vez habilitado, todas las solicitudes deben incluir un encabezado `X-Api-Key` válido, configurado con la clave API correspondiente.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/jwt.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/jwt.mdx
deleted file mode 100644
index 8d5955831b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/jwt.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-Para habilitar la autenticación JWT, modifica tu archivo `dev.env`:
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_AUTH_TYPE=jwt
-# Will be used to sign the JWT token
-SECRET_PLATFORM_API_AUTH_SECRET="your secret that business server will use"
-```
-
-</CodeExample>
-
-Anchor Platform utiliza el algoritmo HMAC SHA-256 (HS256) para firmar los tokens JWT. Asegúrate de que `SECRET_PLATFORM_API_AUTH_SECRET` tenga al menos 32 caracteres para mayor seguridad.
-
-Una vez habilitado, todas las solicitudes deben incluir un encabezado `Authorization` válido con el formato `Bearer <token JWT>`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/security.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/security.mdx
deleted file mode 100644
index 624a9725b3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/component/security/security.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
-:::caution
-
-Por defecto, los endpoints de la API de la Plataforma como `GET /transactions` y `GET /transactions/:id` no están protegidos y son accesibles para cualquier persona que tenga acceso al servidor, incluidas las aplicaciones de wallet.
-
-:::
-
-:::info
-
-Se recomienda mantener el servidor de la Plataforma accesible solo desde la red privada. Sin embargo, es posible que quieras añadir una capa adicional de protección asegurando la API.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/README.mdx
deleted file mode 100644
index 1cdd8caa32..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Manejo de eventos
-sidebar_position: 120
----
-
-import DocCardList from "@theme/DocCardList";
-
-Recibe actualizaciones de transacciones mediante eventos webhook HTTP.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/delivery.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/delivery.mdx
deleted file mode 100644
index f9f45c69ef..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/delivery.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Garantías de entrega
-sidebar_position: 30
----
-
-## Garantías de entrega
-
-Dependiendo del sistema de mensajería que uses, habrá diferentes garantías de entrega. El servicio de eventos utiliza Kafka como sistema de mensajería, por lo que las garantías de entrega dependerán de la configuración del productor y del corredor que utilices. Dependiendo del número de particiones configuradas para el tema `TRANSACTION`, los eventos pueden entregarse fuera de orden.
-
-:::caution
-
-Cualquier lógica de transacción que dependa del orden debe usar el `status` de la transacción y los campos `updated_at` para determinar el orden de los eventos.
-
-:::
-
-Las siguientes subsecciones describirán las garantías de entrega desde la perspectiva del cliente y del servidor de negocios.
-
-### Garantías de entrega para el cliente
-
-Para cada cliente, el servicio de eventos intentará entregar cada evento hasta tres veces con un retroceso exponencial. Si el evento no se entrega después de tres intentos debido a errores HTTP 4xx o 5xx, el evento será omitido. Si el cliente no es accesible después de tres intentos, el servicio de eventos dejará de intentar entregar cualquier evento a ese cliente.
-
-### Garantías de entrega para el servidor de negocios
-
-El servicio de eventos intentará entregar cada evento al servidor de negocios hasta tres veces con un retroceso exponencial. Si el evento no se entrega después de tres intentos debido a errores HTTP 4xx o 5xx, el evento será omitido. Si el servidor de negocios no es accesible después de tres intentos, el servicio de eventos dejará de intentar entregar cualquier evento al servidor de negocios.
-
-:::note
-
-Las garantías de entrega para el servidor de negocios son las mismas que las garantías de entrega para el cliente. En el futuro, el servicio de eventos omitirá los eventos que no se entreguen a clientes que no estén accesibles.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/getting-started.mdx
deleted file mode 100644
index 90b7e66ff4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/getting-started.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Anchor Platform proporciona un servicio de eventos que envía notificaciones por webhook HTTP a:
-
-**Servidores empresariales**
-
-- Cambios en el estado de las transacciones
-- Actualizaciones de cotizaciones
-- Cambios en el estado de KYC del cliente
-
-Los esquemas de eventos para servidores empresariales están definidos en la [referencia de la API](../../api-reference/callbacks/post-event.api.mdx).
-
-**Aplicaciones cliente**
-
-- Cambios en el estado de las transacciones que afectan a sus usuarios
-- Cambios en el estado de KYC del cliente que afectan a sus usuarios
-
-_Los esquemas de eventos para aplicaciones cliente están definidos en sus respectivos SEPs:_
-
-- [Eventos de transacción SEP-6](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md#single-historical-transaction)
-- [Eventos de cliente SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#response)
-- [Eventos de transacción SEP-24](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#single-historical-transaction)
-- [Eventos de transacción SEP-31](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#get-transaction)
-
-Esto elimina la necesidad de que los servidores empresariales y las aplicaciones cliente realicen sondeos continuos a las APIs para obtener actualizaciones.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/integration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/integration.mdx
deleted file mode 100644
index 859637fa08..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/events/integration.mdx
+++ /dev/null
@@ -1,161 +0,0 @@
----
-title: Integración
-sidebar_position: 20
----
-
-Esta guía te mostrará cómo integrarte con el servicio de eventos para comenzar a recibir eventos. El servicio de eventos actualmente solo soporta Apache Kafka como el intermediario de mensajes backend.
-
-Se asume que estás familiarizado con Kafka y no se cubrirá cómo configurar un clúster de Kafka.
-
-## Requisitos
-
-Anchor Platform enviará eventos al tema de Kafka `TRANSACTION`. El servicio de eventos consumirá eventos de este tema y los enviará a los endpoints apropiados.
-
-## Configuración
-
-Primero, el productor Kafka del servicio de eventos debe configurarse usando la sección `event.queue` del archivo de configuración o estableciendo las variables de entorno. A continuación se muestra el conjunto de variables de entorno requeridas para configurar el productor Kafka del servicio de eventos:
-
-<CodeExample>
-
-```bash
-# dev.env
-EVENTS_ENABLED=true
-EVENTS_QUEUE_TYPE=kafka
-EVENTS_QUEUE_KAFKA_BOOTSTRAP_SERVER=localhost:9092
-```
-
-```yaml
-# dev.services.yaml
-events:
-  enabled: true
-  queue:
-    type: kafka
-    kafka:
-      bootstrap_server: localhost:9092
-```
-
-</CodeExample>
-
-Anchor Platform permite configurar un subconjunto de la configuración del cliente del productor Kafka. Consulta el [archivo de valores por defecto][default-values-file] para más información sobre lo que está disponible. Para más información sobre la configuración del cliente del productor Kafka, visita la [documentación de Kafka](https://kafka.apache.org/documentation/#producerconfigs).
-
-Luego, el procesador de eventos debe configurarse en la sección `event_processor` del archivo de configuración de Anchor Platform o estableciendo las variables de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-EVENT_PROCESSOR_CLIENT_STATUS_CALLBACK_ENABLED=true
-EVENT_PROCESSOR_CALLBACK_API_REQUEST_ENABLED=true
-```
-
-```yaml
-# dev.services.yaml
-event_processor:
-  client_status_callback:
-    enabled: true
-  callback_api_request:
-    enabled: true
-```
-
-</CodeExample>
-
-Esto habilitará que el procesador de eventos comience a procesar eventos del tema `TRANSACTION`. En este ejemplo, el procesador de eventos enviará eventos a endpoints de callback de cliente y servidor de negocios.
-
-## Recibir Eventos
-
-El servicio de eventos puede usarse para enviar eventos a endpoints de callback de cliente y servidor de negocios. El servicio de eventos enviará eventos a estos endpoints como solicitudes HTTP POST con los datos del evento en el cuerpo de la solicitud.
-
-### Como aplicación cliente
-
-Las aplicaciones cliente pueden recibir actualizaciones sobre las transacciones de sus usuarios e información del cliente. El esquema de los datos del evento dependerá del tipo de evento que se envíe.
-
-Para recibir eventos como aplicación cliente, necesitarás exponer URLs de callback a las que el servicio de eventos pueda enviar eventos. El servicio de eventos enviará una solicitud POST a este endpoint con los datos del evento en el cuerpo de la solicitud. El esquema de los datos del evento dependerá del tipo de evento que se envíe. Anchor Platform permite configurar endpoints únicos según el tipo de evento.
-
-Anchor Platform solo enviará eventos a clientes listados en la configuración de clientes. Consulta la [documentación de configuración de clientes][clients-config] para más información.
-
-#### Firma de Callback
-
-Anchor Platform firma las solicitudes de callback que envía a las aplicaciones cliente. La firma se incluye en la cabecera `Signature` de la solicitud. La especificación de la firma de la URL de callback se puede encontrar en las especificaciones del protocolo SEP correspondientes.
-
-- [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)
-
-### Como servidor de negocios
-
-Además de las actualizaciones de estado de transacciones SEP, los servidores de negocios pueden recibir eventos sobre la creación de cotizaciones SEP-31 o actualizaciones de información de clientes SEP-12. El esquema de los datos del evento dependerá del tipo de evento que se envíe. Visita la [documentación de la API de eventos](../../api-reference/callbacks/post-event.api.mdx) para más información sobre el esquema de los datos del evento.
-
-Para recibir eventos como servidor de negocios, necesitarás exponer una URL de callback a la que el servicio de eventos pueda enviar eventos. El servicio de eventos enviará una solicitud POST a este endpoint con los datos del evento en el cuerpo de la solicitud.
-
-#### Configuración
-
-La API de callback del servicio de eventos puede configurarse usando la sección `callback_api` del archivo de configuración de Anchor Platform o estableciendo las variables de entorno.
-
-El siguiente es un ejemplo de cómo configurar la API de callback del servicio de eventos con autenticación JWT:
-
-<CodeExample>
-
-```bash
-# dev.env
-
-# note `/callback` will not be used for event callbacks
-# instead events will be sent to `http://localhost:8081/event`
-# all other callbacks (rates, customer, etc.) will use the provided `/callback` root path
-CALLBACK_API_BASE_URL=http://localhost:8081/callback
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
-SECRET_CALLBACK_API_AUTH_SECRET="a secret for signing jwts"
-```
-
-```yaml
-# dev.services.yaml
-callback_api:
-  base_url: http://localhost:8081/callback
-  auth:
-    type: jwt
-    jwt:
-      expiration_milliseconds: 30000
-      http_header: Authorization
-```
-
-</CodeExample>
-
-El siguiente es un ejemplo de cómo configurar la API de callback del servicio de eventos con autenticación por clave API:
-
-<CodeExample>
-
-```bash
-# dev.env
-CALLBACK_API_BASE_URL=http://localhost:8081/callback
-CALLBACK_API_AUTH_TYPE=api_key
-CALLBACK_API_AUTH_API_KEY_HTTP_HEADER=X-Api-Key
-SECRET_CALLBACK_API_AUTH_SECRET="your API key"
-```
-
-```yaml
-# dev.services.yaml
-callback_api:
-  base_url: http://localhost:8081/callback
-  auth:
-    type: api_key
-    api_key:
-      http_header: X-Api-Key
-```
-
-</CodeExample>
-
-Esto configura la API de callback del servicio de eventos que se usará para enviar eventos a endpoints de callback de clientes y servidores de negocios. Las siguientes son las opciones de configuración soportadas:
-
-- `base_url`: La URL base del endpoint de callback del servidor de negocios.
-- `secret`: El secreto que se usará al enviar eventos al endpoint de callback del servidor de negocios. Se usa para firmar el cuerpo de la solicitud cuando la autenticación JWT está activada y es la clave API cuando la autenticación por clave API está habilitada.
-- `auth`: El método de autenticación que se usará al enviar eventos al endpoint de callback del servidor de negocios. Los siguientes métodos de autenticación son soportados:
-  - `JWT`: El servicio de eventos enviará un JSON Web Token (JWT) en la cabecera `Authorization` de la solicitud. Las siguientes son las opciones de configuración soportadas:
-    - `expiration_milliseconds`: El tiempo de expiración del JWT en milisegundos.
-    - `http_header`: La cabecera en la cual se enviará el JWT.
-  - `API_KEY`: El servicio de eventos enviará una clave API en la cabecera `Authorization` de la solicitud. Las siguientes son las opciones de configuración soportadas:
-    - `http_header`: La cabecera en la cual se enviará la clave API.
-
-[default-values-file]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[clients-config]: ../../sep-guide/sep10/README.mdx#config-with-client-attribution
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/getting-started.mdx
deleted file mode 100644
index 000a20bb05..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/admin-guide/getting-started.mdx
+++ /dev/null
@@ -1,139 +0,0 @@
----
-title: Comenzar
-sidebar_position: 30
----
-
-# Comenzar
-
-Esta guía te ayudará a poner en marcha rápidamente la Anchor Platform (solo TESTNET) con una referencia comercial funcionando localmente usando Docker Compose.
-
-Ten en cuenta que esto no está pensado para usarse en producción.
-
-## Requisitos previos
-
-- Tener instalado [Docker](https://www.docker.com/get-started) y Docker Compose
-- Tener instalado el [Stellar CLI](https://github.com/stellar/stellar-cli)
-
-## Inicio rápido
-
-### 1. Clonar el repositorio de Anchor Platform
-
-```bash
-git clone https://github.com/stellar/anchor-platform
-```
-
-### 2. Navegar al directorio quick-run
-
-```bash
-cd anchor-platform/quick-run
-```
-
-### 3. Iniciar todos los servicios
-
-```bash
-./ap_start.sh
-```
-
-### 4. Verificar que la plataforma esté funcionando
-
-Espera unos momentos para que los servicios se inicialicen y luego verifica que la plataforma responda:
-
-```bash
-curl http://localhost:8080/.well-known/stellar.toml
-```
-
-Deberías ver el archivo de configuración Stellar TOML retornado.
-
-### 5. Comprobar el estado del servicio
-
-```bash
-docker-compose ps
-```
-
-Todos los servicios deberían mostrarse como "Up" en la columna de estado.
-
-## Qué incluye
-
-La configuración `quick-run` incluye:
-
-- **docker-compose.yaml** - Definiciones completas de servicios con todas las dependencias
-- **dev.env** - Variables de entorno preconfiguradas
-- **config/** - Archivos de configuración requeridos:
-  - `assets.yaml` - Definiciones de activos
-  - `clients.yaml` - Configuraciones de clientes
-  - `reference-config.yaml` - Ajustes del servidor de referencia
-  - `stellar.localhost.toml` - Archivo TOML SEP-1
-
-:::tip
-
-Para más información sobre cómo configurar activos y carteras de clientes, consulta la guía [Assets and Client Wallets](./assets-and-client-wallets.mdx).
-
-:::
-
-## Pruebas con Stellar Demo Wallet
-
-Puedes probar la Anchor Platform usando el [Stellar Demo Wallet](https://demo-wallet.stellar.org):
-
-1. Abre el [Stellar Demo Wallet](https://demo-wallet.stellar.org) en tu navegador.
-2. Haz clic en el botón **"Generate keypair for new account (testnet only)"**.
-3. Haz clic en el botón **"Create Account"** junto a la clave PUBLIC.
-4. Ahora deberías ver `XLM` disponible en la sección **Balances**, indicando que tu cuenta está cargada.
-5. Haz clic en **"Add home domain"** e ingresa la siguiente URL:
-   ```
-   http://localhost:8080
-   ```
-   Esto conecta la demo wallet con tu instancia local de Anchor Platform corriendo en el puerto 8080.
-6. Ahora deberías poder realizar transacciones SEP (depósitos, retiros, etc.) con tu instancia local de Anchor Platform.
-
-## Personalizando la configuración
-
-Para modificar ajustes:
-
-1. Edita `dev.env` para variables de entorno
-2. Edita los archivos en `config/` para configuraciones específicas de servicios
-3. Reinicia los servicios: `docker-compose restart`
-
-## Detener servicios
-
-Para detener todos los servicios:
-
-```bash
-docker-compose down
-```
-
-## Cómo implementar tu servidor de callback empresarial
-
-Una vez que tengas la Anchor Platform en marcha, puedes reemplazar el servidor de referencia con tu propia implementación del servidor de callback empresarial. Esto te permite implementar tu propia lógica empresarial para manejar depósitos, retiros y otras operaciones del anchor.
-
-### 1. Apagar el servidor de negocio de referencia
-
-Después de que la Anchor Platform esté iniciada y funcionando, detén el servicio del servidor de referencia:
-
-```bash
-docker-compose stop reference-server
-```
-
-Esto detiene el servidor de referencia manteniendo la Anchor Platform y otros servicios en funcionamiento. La plataforma seguirá funcionando, pero ya no recibirá callbacks del servidor de referencia.
-
-### 2. Implementa y ejecuta tu propio servidor de referencia
-
-Implementa tu propio servidor de callback que cumpla con la API de callback de Anchor Platform.
-
-Puedes usar el [kotlin-reference-server](https://github.com/stellar/anchor-platform/tree/develop/kotlin-reference-server) como implementación de referencia para entender los endpoints y estructuras de datos requeridos.
-
-Asegúrate de que tu servidor de callback sea accesible en `http://localhost:8091` (o el endpoint configurado) y que la Anchor Platform pueda conectarse.
-
-Tu servidor debe:
-
-- Escuchar en el puerto **8091** (o configurar la plataforma para usar otro puerto)
-- Implementar los endpoints de callback requeridos según la documentación de la API de Anchor Platform
-- Manejar la lógica empresarial para:
-  - Cálculo de tarifas
-  - Determinación de tasa de cambio
-  - Actualizaciones de estado de transacciones
-  - Gestión de información del cliente (KYC)
-  - Procesamiento de depósitos y retiros
-
-### 3. Prueba tu integración usando la demo wallet
-
-Sigue los pasos descritos en la sección [Pruebas con Stellar Demo Wallet](#testing-with-stellar-demo-wallet) arriba y verifica que tu servidor maneje correctamente los depósitos, retiros y otras operaciones SEP iniciadas desde la wallet.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/README.mdx
deleted file mode 100644
index b8868bcf2a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Referencia de API
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Ver toda la información de la API de Anchor Platform.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/README.mdx
deleted file mode 100644
index 367a0818ca..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Servidor de callbacks
-sidebar_position: 20
----
-
-La plataforma Anchor proporciona varias funcionalidades de callback para el servidor de tu negocio.
-
-<EndpointsTable title="Callbacks">
-
-|        |                                         |
-| ------ | --------------------------------------- |
-| GET    | [/customer](./get-customer.api.mdx)     |
-| PUT    | [/customer](./put-customer.api.mdx)     |
-| DELETE | [/customer/:id](./del-customer.api.mdx) |
-| POST   | [/event](./post-event.api.mdx)          |
-| GET    | [/rate](./get-rates.api.mdx)            |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/del-customer.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/del-customer.api.mdx
deleted file mode 100644
index 4a24f0d8fb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/del-customer.api.mdx
+++ /dev/null
@@ -1,80 +0,0 @@
----
-id: del-customer
-title: "Delete Customer Data"
-description: "The request for this endpoint is identical to the"
-sidebar_label: "Delete Customer Data"
-hide_title: true
-hide_table_of_contents: true
-api: eJztVE1v2zAM/SsCd9gGOHaa7eRb0eZQYBiKpTslASZLTKxNllSRXhsY/u+DHLtptmy/YL7Ypvgh8j2+DljuCco13LTEvsFIsM3geUYYBvNqeT+7WkA2fHy4SocaSUUT2HgHJTzUKCI+tkgsdj4Krg0JdDp441gYEkajY6OkFewF17hx62+3y0/Lh6Uo1Fj02/ZdzRyoLIq94bqtcuWbghitlXF6z0L07JW3RWV9VTSSGGOBytOBGJuCMMzm86tF3ug3U+KZRouM7zduuqPGnXGohXHi2Fu+cRt3O7il64kp9C0JLVkKH8Vji+354XiWGh4qGO/yjYMMfMAo0++dhhI02mmukEGQUTbIacblugOTxhck15CBkw1CCUZDBqRqbCSUHfAhJCtxNG4PfQapCRNRQ8mxxX6bLBS8I6Tkv5h/TK9zgFatUkiUp/iPlxymGwrnE4St0zlkoLxjdJzcZQjWqKGr4julmO7PS/rqOypOXcY0AzbHK2GMPl7sxegL5rMe12P0NgM2bJPfcjD06ckAnxkdGe+O8/yBBygn6mbwU9oWL1I4za1Brv0IETIO6HANJbxwsuiM7hMcGH9OkLXRQgkTVZW0tpLqR161ZBwSzY6+OT7LJliUTtU+JipDKmnczqeWU7bj5D/k83wOlzZqdXCqjt75lsTNWIbE9f2doIDK7EY4xo1DsTquiLgeSop7K3nnYyNC9AmWgeP/znvcC5p2mUQjNYrqMKR/yfdUG4vCDIsdok/EMm4v5EkCom+EFMoadCxeMScXD2n3jzN5m+qMxB1lgfBUWu52qPi88u/+l0oMGzhR5dTeakAFMrBGoSNMIIwLdx2kqlEsBhhO6JZF8fT0lMvhNPdxX4yhVHy6u1l+Xi1ni3ye19zYgbPBEzfSvUo8CsrLbt1Klr8j3Z2W7L+MnsvoKAuMz1wEK41LijHg042LugZ1UtbS6KQStSdOJ11XScKv0fZ9Mj+2GA9QrrdJFKKRVeLHugNtKH1rKHfSEv4DnXdfRlF6L/52udEo3eGkPQDZqEpGQ7/tM6hRaoyv5OpaKQz8KuQPsT1TqyPi0Pe/AB/asHM=
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-12,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete Customer Data"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/customer/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The request for this endpoint is identical to the
-[`DELETE /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-delete)
-request defined in SEP-12.
-
-Delete the customer's data or queue the customers data for deletion.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"path","name":"id","schema":{"type":"string"},"required":true}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"204":{"description":"Success."},"404":{"description":"Customer not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/get-customer.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/get-customer.api.mdx
deleted file mode 100644
index ee11a1434b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/get-customer.api.mdx
+++ /dev/null
@@ -1,91 +0,0 @@
----
-id: get-customer
-title: "Retrieve Customer's Info"
-description: "The request and response for this endpoint is identical to the"
-sidebar_label: "Retrieve Customer's Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWG1z2zYS/is7uA9pZihKdtJco28eRcnp2jo+y+lNx/bYELES0YAAC4CWNR7995sFSImyGbu13ZvLTfzFFAksnt199gV7wwS6zMrSS6PZkJ3kCBZ/r9B54FqARVca7RDmxoLPpQPUojRSe5AOpEDtZcYVeAM+xzN9evlhfAL9rHLeFGgvz7/LvS/dsN9fSJ9XszQzRd95VIrb5n+vtMabzKj+TJlZv+DOo+1jZtzKeSz6DsveYLC3nxbib43g3gL9yzPdCVXgXGoUIDVMx0e9vf30TJ/pkx3wXCmzdJApido78GZIawD2UniPPstJG5hLVMKFR4f2Cm0wjbToSLaxAi0pbnEhCTJw0LiEBiJcSQ68hkCWOfr0X7FMWfmXjQ9Jqcm8rYEw6EAbDzm/QuBbtI0WKGpfI5Tc8gI9WgcOyeM6vK5lJyA9uNxUimzvK6sjBWqr1aYS213RPSkQxxwvtq8aKTOsBaGAZY4atGlj4BYDjjS6aj+FUY7Z56id575yYOZtlXzOPRR8BVxZ5GIVD2jU3JDiDhcgC3KXOfocoykameT5ubEFp3iBJXfAswxLjyIBi79hFp6MBeelUqARhYPCWAz70tve6FwV9rcWxc9VKbgP5tyc3+0BuOWA9EyzhHm+cGx4ykaNIuw8Ydc9h2V4TSx9wxIW2Vo/vNqjRaZEG46bCDZkC/SNCJawrXfY8PSGSUohv1doVyxhmhfIhkwKlnQkmck7clbbtMDd1v23SBMdW1q8kqZyQJFUszBlCXNZjgVnwxvmVyWd6byVesHW66QbE88yU2nfCWwaQ4988HN1jQIO4mLglc9juiM3LKWPSeJIcU8eCeEezDd4FKYCC9MJiD7AFVcV1vl2vpJ60eZ5wMLB5ZzirVYuIf5ajETa+UKZ+7J+vnw01ouwtgswfSCHBeCVQ0Eh1UB/EPd9gBKGuiqIr4FVOXc5URuvPTv/ItgHcfIsBPMOF6WDGZKZf/x1FBJiClPEusad0MZpiZmcExuk0c+dzAlaz7VPeHmmhcmqArW/Vdoe40BvuXZR74svBGhrCcia78tc1qWxMdSLmBDJXtw5k0kKjhT+Tdm7nSnn1hS7FhZYohYOTF022ud9h+kiTbYZsZEiW2WFipTidkGJoyDiuJePs4XigVm7FniHc16pWA0uUV+m8BPXi4ovEDIjEGrfoIDKEU0m04/w5tXb3l4K/6gKroEKDp8p6kY2cl0CWW5khi6hjuVMF+gcX6BrFcCQ+KQDVR/3kIPPE9YkSUff9wcD+rerzS9cSbHJmNAkcEAZClxTHvFaOu+a6rONhRi6pOxsdbsxkC40PdSAFRU1HKU1V1LgthLF3OVqQ8w6kvvMiFUKx62fEmO5v91gQjRE0+KdaanhNEbCX9ppRi9kRnvUnuzLy1LVkdn/zZGRb+46ycyoIWDkoUhaylyxU6HCWloqrV5Gx0nR4d6kWX5PKjwYjcZHJ+N3LGFHxx9H4+l0cviBJexwPH43vZgcvv/IEnY8/ud4RIvO1wmLDUIXUC6EJJ24OtoB11agI5/eUSbK/TLmzYuZ1DwGY1XMQktBXU5AuUPhDsvUodT6xq3lJEt6LDpMtl5TMxPVa32dGaOQa7Ze04KavuLim5E6jfQURm5ImLBfxseT95PRwcnk4+HF8fhfnybHNTnRWmO7cBGyOmF2w/bSK3r1YduiNjmFcOM1L0oVbTGtsgyd+/HXUQjcqijIwLHwZdxhvH60WpWcU0OAGlzcOa+UWlFz8EKE3MdLIg5SKQ3proloJvYy3J+//qH3aj7f671++73ovd1/Pej9nX8/ED8M3mTzsKkxatt2HVScS+v8RSxct5P8yW5ZDkshLE3ueOruceuEKf5HZdPKPyUaCy7VBRfConMPig+roVn9h46o/xL2uqv+jYlT6VMy+G7kfomjSXcWX+9WgLj7fEvYAI81+F/fxX9oPLw3lRZfgw4h1DxqRx1PuBZ+Roqt+rK5CZB7Lp3U1RToc1PfOMNN0+dsyDbzE6JBuB7HIyqr2JA1HUDGlZrx7HM6o+4MnevFtWmdA7jOcmOpQ2B0FLWYpDJJiwZ/lQ7SQff1cKWz3BpN19BRfYyDg6MJ7LTrmxlKc508CEdub4ulNeSWejR1n9zY67imfXNQcIFNJ7aRt8ylQpoHSEeyKUfFW2IzIgsdOK+nHNBiThjInOlokxdu05a5uudyuD2az+eY+d2Tb6/vOiKOIGqqbNWbBq+whCmZIaXp4U3TlR+UPMsR9oMbtt4d9vvL5TLl4Wtq7KJfb3X9nyaj8eF03NtPB2nuCxU4WxrnC65bgo/RW4lXuOmCXziYEAHuFNNNoH2bin6bin6biv5fTkVjkaMJUr9UXIYGN2Sbm7rinLJNxTlPWG6cp3c3NzPu8JNV6zW9jhMFqkNCOrr1Czacc+XwgZzynEPQTlVi5ZWttpQxmoP8OZjPNBK9B+F2IPsEmH/9oPQeDerx7RPgP31s+gC8ZmL7DBi//pHpPbZ6BjN9pbPT+4xye2L8SPP8jw1W79G4ngtv9TynH1bS4Wx4SrOKHLlA27rjHISy19p154a2c7X5MD5h6/V/AIMyEEU=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-12,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Customer's Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/customer"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The request and response for this endpoint is identical to the
-[`GET /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-get)
-request and response defined in SEP-12.
-
-This endpoint allows clients to:
-
-  1. Fetch the fields the server requires in order to register a new customer via a SEP-12
-[`PUT /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-put) request
-
-If the server does not have a customer registered for the parameters sent in the request, it should return the
-fields required in the response. The same response should be returned when no parameters are sent.
-
-  2. Check the status of a customer that may already be registered
-
-This allows clients to check whether the customers information was accepted, rejected, or still needs more info.
-If the server still needs more info, or the server needs updated information, it should return the fields required.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"query","name":"id","description":"The ID of the customer as returned in the response of a previous PUT request.","schema":{"type":"string"}},{"in":"query","name":"account","description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","schema":{"type":"string"}},{"in":"query","name":"memo","description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","schema":{"type":"string"}},{"in":"query","name":"memo_type","description":"The type of memo used to identify a customer with a shared account.","schema":{"type":"string","enum":["id","hash","text"]}},{"in":"query","name":"type","description":"The type of action the customer is being KYCd for. See the\n[Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification)\ndocumented in SEP-12.\n","schema":{"type":"string"}},{"in":"query","name":"transaction_id","description":"The transaction id with which the customer's info is associated. When information from the customer depends on the\ntransaction (e.g., more information is required for larger amounts)\n","schema":{"type":"string"}},{"in":"query","name":"lang","description":"Defaults to `en`. Language code specified using ISO 639-1. Human readable descriptions, choices, and\nmessages should be in this language.\n","schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Valid request. Customer either already exists or the customer identified by the parameters is new and must\nprovide the field values described in the response body. Response bodies are identical to the schema defined\nin [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-get).\n","content":{"application/json":{"schema":{"type":"object","required":["status"],"properties":{"id":{"type":"string"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","NEEDS_INFO","REJECTED"]},"fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"}}}},"provided_fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","REJECTED","VERIFICATION_REQUIRED"]},"error":{"type":"string"}}}},"message":{"type":"string"}},"title":"GetCustomerResponse"},"examples":{"SuccessKYC":{"summary":"The case when a customer has been successfully KYC'd and approved","value":{"id":"d1ce2f48-3ff1-495d-9240-7a50d806cfed","status":"ACCEPTED","provided_fields":{"first_name":{"description":"The customer's first name","type":"string","status":"ACCEPTED"},"last_name":{"description":"The customer's last name","type":"string","status":"ACCEPTED"},"email_address":{"description":"The customer's email address","type":"string","status":"ACCEPTED"}}}}}}}},"400":{"description":"Error.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Not Found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/get-rates.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/get-rates.api.mdx
deleted file mode 100644
index 2db4112e09..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/get-rates.api.mdx
+++ /dev/null
@@ -1,107 +0,0 @@
----
-id: get-rates
-title: "Retrieve Rates"
-description: "Transactions that involve two non-equivalent on & off-chain assets (such as USDC on Stellar and fiat EUR) must"
-sidebar_label: "Retrieve Rates"
-hide_title: true
-hide_table_of_contents: true
-api: eJztW+tv4zYS/1cGOuA2uZPtbLYtCgP7Id1N2wB37WKToB/iXExLo4iNRGpJyl5fkP7thxlSDz8Sp9m9uz7yyZFEcjjv3wyZ2yhFmxhZOalVNI7OjFBWJPRkweXCgVRzXcwR3EKD0mqAH2o5FwUqB1rBX0Fn2SDJhVQgrEVnYc/WSQ7Cwvnp2zc05tRhUQgDQqWQSeHg+Pz9PpS1dRNVWwT8mORCXSMY4TBQFQYh0WVZK5kIhyk4DS5HSApJlEVVFfRBagUGP9RonVTXPMJ1HAzhpxxVmGOhFDc4UWG4bVZ8VwiXaVNCpg292NhQvDrMokppk9I2lJuVhEpyWkNDhi7JQbrhRE3Ue+YqEQpmCBdSpbzxOV7u5c5VdjwaLRaLoVRztE5XmEoxTHQ5cmhKO5KjbsKHWjscClvtgzYTdZFJUz5qkWxEQ7vpQzjrtkt6gMrouUzpHZy8ZUXhx0oaL2CZEXsTFWTfClAALctCYkaPeEHParNgKm2ia0Ua9Nq1FSYyk8kWTVq/r1bSUiVFnbJFIEz9+CuZTqESRpTo0EyUVxrrQliteB/H0uVoYGqxKK5ESeSnoA1MZ/WyfV7IoiCFBCIpSNXjzHY0bAyz2oHCORqYaZcP4UTxlqwoERZiGU8U9kmmWMg5muVViS7X6ZTlycQ3vpRied8m1snGYKVKEDypiQrskc/1uPOPkpTTuh29Y8FM1HnFDpOgnDf+YtBWWln0Zu512OmAxTQXhUyFQ2/lLEDmqTIyQdDZyjpM6cS/CxPJiDIhi3VX4sX9vAcc/EXnaAvpchDw/dnZO7BOuNpOVKJT3sP0y4ND+Eak8J1wuBDLKW+EDGrFEOIVM4hhykxMY6+kDHHKsadhOSVbyHRR6IUd04IDcocp2zwPxo+SlDVRAIPu/TAogp0rF3MEAZW2ktyY1q79lq28VuQMQrmrFBNZisJOIcVMKm8MLHBaChKtMnlde5ccrpNz2okikMMPtSgacdq6ZErtyBQdaWIYBBBW8i6+vn94/dp7d8/U4hVxwi+vgxX8DTqxwt+BZeO510UKztT4OFKdFcdwL6m9dVr7W4itayrVaEFp51X2GD62LBos6pfX7GSNpoT1UpduyTZKbqxrlZKPoTHaMO/A4W31w9oq05cH/9obbDOL/elERXHkxLWNxhcRJ5XoMo4+DixW/Or0+N3g1cso9n98TR91hd5gTtJoHF2j89PiqItu0fjiNpKU+j/UaJZRHClRYjSO3LLCKF6HB5RglxVbL0m28UxMh3CSwZQSwjReiQdehiHCBX3IJijyE6catFfCTYdRHNkkx1JE41u/hXFknZHqOoojVHVJnHYpMYojIhld3sURbUUaTKMx6eou3s5Wm0Y2eDtSIFNUTmYSTYMGtgGOUtx0wZPZp8QlLaXOkOZr6yGLzjI0kEr6oWUyRAYe3ZsATti03nhaJ29tm56ISBPIq3pWyARucMmve48NOVG7nDggyARzKYBM4eXBEJrU7AOEsrXBiWKgtbZSSM9d9GlCbylckiPlld7oG6UXigjPsNAkkhB00Fu4RxjBa2Qvp3r2tCo4+/VoZn2ZUxbrMZRu5YgE7h0IFjlyFtaG3HyiepMZxvg8QibC2mWQRtvszMljlCF82+AaC6JYiGU7E1bXHLJP3mewd/fZYBdOtzqYD4j3GB9LjgS8hjql6mBrtg4H1ERdHPGqJ8HCw2rfalMK14HIa+nyesbQ0Xqra34HldFOJ7oYzQo9G5XCOjQjTLRdWoflyGI1ODh49fWwTP/CZAdyhdQgY1L7O0T2WDduudshwdbGg5g68W0IrI+n/oAS62W77TLziZBhSU8SO83wAcMbwk80jHJuExNJsIlWP9cqCeu4fAWRPdGluhV2Mdfzi19tF1sZgh4/E+UZ6iPOJ3LEZZNZXhG+3crTxcnpj/Dq5VdfDV6CKKpcDA47s0Q1XMgb6StBba5H9DQ6Of3xys+4CjP2ocHPJIzaonlhIakN5yaRpgYt5aYm2tpc1wUXh5g4X3h1QZ3zQFP5cTDXql06NAfC06xejkhGUAnJGIj7AgQJpJsoCvxzIQsxK5Dz0EJTUC81NwVILBLtE8XqwcaVyByarWL1xv6CYJnlXDHt4RPgMoj26WSJLUjg0trHmj4A4HQmrS/HuFb2NbhHC16WEzWj4uDi/OwNkEK//urg5VpRbzVrUFo9oK8D2sNAqHRAewhRYpi7stgHz32XHYO+DLraKJh+cXBAJdJEvfdZfUpbFKpf7DODWpG8WUZ9EEApmGuXRKjgA422PyUTrlXFW7XiP/WjkTZsrt5zqY1EsMqvtBbBdK+yDbL3bFD1LbLMmzJOVE8MXXnbcsjonSdar96299C5QA/NN9XbSiG7XsXtCCe98LjeOviEOPmJ8hbUS2sQp+8l4EpYzYwuf+8i39rI2SXzS8rFvuqx9P3w4IB+VqV7WicJBdUojhKtHCpHY3p7Hv1saeDtJiE9+xkTSnCVocrOSU+GgOruUTLdVlKt7u3kbROg+9Hqhx/P4Pz0+C0BbAVTWuJ1h5mnQ8IgXYzcRsXHqGgcceiisLVB+rgzhJWo+jjybDe7+eP4rtUcjSVCTf+KSrEUZss+IKBNUPqqldzADWRn1FhdB0sxG4+um3KXiguq+HzH0IhU0j5EAZlUQiUYr6y64FA9o2iboTGhovPdz5mwDarlurkf38IQ32Zt2n3sOST2uhCrnY4BbQke0+6AvQuD2eeGukx3ELZm9/dZf31w+igtPoBW+4jufmR6Qi21IPBefd6ErtXmcYdpVoriGFKsQq2rFeR64Qt8aiCyQ3dWFUIh8dqDqr+W1Qewa9Nw7+PPR7Lat4DPymmGW+PSRtvFfwH/ftb0VjyBlDajqclQtZ1mgijtRqkpwGz4Ri4I54yc1Q6HGyGQu6SPEzoPZU/xqDYwyWz5uvNxumsLUVqqaeokuTDXLOMh/JNcjp2+MmiRT0qkgt9M8UkMh55xj2VhjCBUIR2Wdnfu8eDjMQKjkW0OQozZcfGjKKsCYXr05nvuLMcw/caIf8tCCk7eCf3lc4f/eopmTuHNP6JLAh89crt2cwQOP24zSm8DT3LgEMGDLfmOadeT55ZyY9fUn67Lvc2W/f60QfUz9F1n61fxZwBDwn69lsCFF36748s4ctIVtGVqBn+L+JaXfx+AS3S3Pt97TWP2m/N7M1cn+qQcr3UeeuHvkmb0V+tv4i6Ovjg83MRP56oymhAUV4fHykm3bCoqPhLqicfXPZh66NALmbVK0VinA8Rtmpx04uZrGzon5ppJgPWArX/A5Q8ALRVCduOA+KmnWk11Bk1xNlFcEIfOOS3jjwxKYv66FwJXkUsbuUP/fabTpUeunwlv8i62dqK2Ycx1q/Cze2Z0zC+8xr/chph5wNrZ8OOE7EXbntW2IuGeBwmXZfM7kAwjbIeKYKs/srnBZTRuTn/iiIukradAVJWEQo+PgPj0x+XROBpx4UD+aebNSVBtimgcNfklEUUxE8nNcFZbqdDagR87DBE5NPgTXUZERqpME5sBX0fj6NXwYHiwNSieLlWSG610beFNIGPh6N1Je0NgtRhoDkHWD6gro0kV7dHc/ev6KtF2p/ylSLHxnc6wcklNJxdiMXk+H2W03sq4SWwxNrZQ8lna4IsuXjQ3TSz2Lhi0JXBHeX38NhL+DDCYR8feKWsliqNCJkjxs8250VElkhzhkNXQaTf0lgR/5fZSmGpH/zh5c/zD6fHgcHjAXSW200pbVwrVW/g9UhtujtCcKa5l19alnu8UPd8per5T9Hyn6PlO0fOdouc7Rb/FO0UelVK5O6oKIRUBVoYKtwEqXvge82Uc5do6er69pZbkuSnu7ui1P2UgAJlKLszSaJyJwuIDsGDvfcC++/C/uFa0lUuPosNVp4Cho4gOTx7Px/O9oed7Q0+6N/SARfZvqT3RLNfc609wqegBea7cuPrcAv3D3DF6QID9+1ZPlN9v7pLRTntpWpafh+H/08WjXUr9DEw+30TaEc1Xr3J9gqSfLyc9/XLSAwpauxT2CQp6vqe09c7MrlC7eSXpv6ODP/vdpR3J4CE1XNKDkaSHaHxB/3CRo0jR9E4jjpIEq34u2ThLWTmM+O74LLq7+w+n2PMK
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-31,SEP-38'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Rates"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/rate"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Transactions that involve two non-equivalent on & off-chain assets (such as USDC on Stellar and fiat EUR) must
-use exchange rates that are communicated to the client application requesting the transaction. When clients make
-requests to the Platform for these exchange rates, the Platform sends this request to the anchor to fetch it.
-
-Rates can be [indicative](https://www.investopedia.com/terms/i/indicativequote.asp) or
-[firm](https://www.investopedia.com/terms/f/firmquote.asp). The anchor must provide an ID and expiration if the
-client requests a firm rate.
-
-Anchors can provide discounted rates specific client applications. The Platform includes the `client_id` parameter
-for this reason.
-
-Either `sell_amount` or `buy_amount` will be included in requests as parameters, but never both. In the same way,
-either `sell_delivery_method` and `buy_delivery_method` may be included in requests, but never both, since either
-`sell_asset` or `buy_asset` is a Stellar asset.
-
-
-Upon receiving the response, the Anchor Platform will validate the amount and price of the response.
-
-If the validation fails, the Platform will respond to the client application's request with a HTTP status
-code of `502 Bad Gateway`.
-
-The `sell_amount`, `buy_amount`, `price`, and `fee` are validated as follows:
-
-- if `rate.fee` exists,
-  - `rate.fee.asset` must have a positive value of `significant_decimals` defined in the asset configuration.
-  - `rate.fee.total` must equal to the sum of `rate.fee.details.amount`.
-  - if the `rate.fee.asset == rate.sell_asset`, `sell_amount ~= price * buy_amount + fee` must hold true.
-  - if the `rate.fee.asset == rate.buy_asset`,  `sell_amount ~= price * (buy_amount + fee)` must hold true.
-- if `rate.fee` does not exist, `sell_amount ~= price * buy_amount` must hold true.
-
-The `~=` is defined as equality within rounding error.
-    The rounding error is defined as `10^(-significant_decimals)`
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"query","name":"type","description":"The type of rate requested. If `firm`, the response must include `rate.id` and `rate.expires_at`.","schema":{"type":"string","enum":["indicative","firm"]},"required":true},{"in":"query","name":"client_id","description":"An identifier for the client application making the request. This ID can be used to offer different fees to different clients.\n\nClient IDs will be the Stellar public key the public key used to authenticate via SEP-10. Anchors must ensure\nthat the public key specified in the request matches a public key known to belong to the sending anchor.\n\nThis parameter will only be specified if the client is authenticated via SEP-10. Anchors can define whether or not\nauthentication is required for fetching indicative rates. Firm rates always require authentication.\n","schema":{"type":"string"}},{"in":"query","name":"sell_asset","description":"The asset the client application will send to the anchor in exchange for `buy_asset` in\n[Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format).\n","schema":{"type":"string"},"required":true},{"in":"query","name":"buy_asset","description":"The asset the that the anchor will send in exchange for `sell_asset` in\n[Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format).\n","schema":{"type":"string"},"required":true},{"in":"query","name":"sell_amount","description":"The amount of `sell_asset` the client application will send in exchange for `buy_asset`. Will not be used in\nconjunction with `buy_amount`.\n","schema":{"type":"string"}},{"in":"query","name":"buy_amount","description":"The amount of `buy_asset` the anchor will send in exchange for `sell_asset`. Will not be used in conjunction\nwith `sell_amount`.\n","schema":{"type":"string"}},{"in":"query","name":"country_code","description":"The [ISO 3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) code of the user's current address.\nAnchors should expect this parameter to be provided if one of the assets of the buy/sell pair is fiat and it\nis available in two or more countries.\n","schema":{"type":"string"}},{"in":"query","name":"expire_after","description":"The client's desired `expires_at` date and time for the quote that can be used if this is a firm quote. This should\nbe a [UTC ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) string. Anchors should return `400 Bad\nRequest` if an expiration date on or after the requested value cannot be provided.\n","schema":{"type":"string"}},{"in":"query","name":"sell_delivery_method","description":"The method the client or user will use to deliver `sell_asset` to the Anchor. This value may affect the\nexpiration and price provided. The values used for this parameter is defined in the application's configuration.\nWill not be used in conjunction with `buy_delivery_method`.\n","schema":{"type":"string"}},{"in":"query","name":"buy_delivery_method","description":"The method the client or user wants used to receive `buy_asset` from the Anchor. This value may affect the\nexpiration and price provided. The values used for this parameter is defined in the application's configuration.\nWill not be used in conjunction with `sell_delivery_method`.\n","schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","properties":{"rate":{"type":"object","properties":{"id":{"type":"string","description":"ID of the firm quote. NOT USED when `type=indicative`."},"expires_at":{"type":"string","format":"date-time","description":"Expiration for the quote. NOT USED when `type=indicative`."},"price":{"type":"string","description":"The conversion price offered by the anchor for one unit of `buy_asset` in terms of `sell_asset`, without including fees. In traditional finance, `buy_asset` would be referred to as the base asset and `sell_asset` as the counter asset. The formula `sell_amount - fee = price * buy_amount` must hold true ([ref](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#price-formulas))."},"sell_amount":{"type":"string","description":"The amount of `sell_asset` the anchor will exchange for `buy_asset`. It could be different from the `sell_amount` provided in the request, depending on how fees are applied by the Anchor."},"buy_amount":{"type":"string","description":"The amount of `buy_asset` the anchor will provide with `sell_asset`. It could be different from the `buy_amount` provided in the request, depending on how fees are applied by the Anchor."},"fee":{"type":"object","description":"An object describing the fees added on top of the rate provided via the `price` attribute.","properties":{"total":{"type":"string","description":"The total fee to be applied."},"asset":{"type":"string","description":"The asset the fee will be charged in. Must be represented in [Asset Identification Format](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#asset-identification-format)."},"details":{"type":"array","items":{"type":"object","properties":{"name":{"type":"string","description":"The name of the fee, for example `ACH fee`, `Brazilian conciliation fee`, `Service fee`, etc."},"description":{"type":"string","description":"A text describing the fee."},"amount":{"type":"string","description":"The amount of asset applied. If `fee.details` is provided, `sum(fee.details.amount)` should be equals `fee.total`."}},"required":["name","amount"],"title":"RateFeeDetailResponse"}}},"required":["total","asset"],"title":"RateFeeResponse"}},"required":["price","sell_amount","buy_amount"]}},"title":"RateResponse"}}}},"422":{"description":"Unprocessable Entity. This status should be returned when the anchor understood the request but cannot\nreturn a success response.\nIn these cases, the Platform will respond to the client application's request with a `400 Bad Request`\nand include the error message provided by the anchor in the response body.\n","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"500":{"description":"Error. The Platform will respond to the client application with the same response code and body.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/post-event.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/post-event.api.mdx
deleted file mode 100644
index 81fc5d4b7c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/post-event.api.mdx
+++ /dev/null
@@ -1,76 +0,0 @@
----
-id: post-event
-title: "Receive an Event"
-description: "Receive a JSON object representing an event."
-sidebar_label: "Receive an Event"
-hide_title: true
-hide_table_of_contents: true
-api: eJztHF1v2zjyrxB86R1gO4nb/Ti/dbtZIIfbNlvnXi4JXFoaW2wkUiWpOEbg/34YkpIoWXZso0CzgPISmx8zw+HMcD5oPlPDlppObunlIwij6f2APg015LZtenk9/JkO7P/xO//h7QUOkjkoZrgUVzGd0FxqYwHQAY1BR4rn2Ecn9DNEwB+BMPLv6aePRM6/QmSIglyBBmG4WBImCODc0Z2gA6rgWwHa/CbjNZ0800gKg3Anz5Tlecoji/Tsq0boz1RHCWQMP5l1DnRCHQI6oLlCEg0Hjb08DsZoo7hY0s3AN7Q7BhREkSEDjGJCswhRziIFzEBMB41WbZgp9CxKmFjazm+FNBAMjgptZAZqVuSxbbpvs+gmARKAdMwgSNKIfGCCzIFIAUQuiEmALGSayhUXy8mdGJIvHRR+IUPCGhBXTBPfSUyiZLFMLKzp5TUBEeeSC6NHBAnJ2TqVLCZcEy7soBDFF7LgkMajLdRNNiAFONW1IuVNehKkxw09GmuDv26ptqmxyEfOygW+/ZW8v77aicbOrRFYoeAZaMOyvEsyFlJlzNAJxc0c4lCc4gG/LIfBqvCrFPBpQSe329NQDbiCGKWQoxxpyOmAPnBhv1jG0gFlmSyEmcFTDpGTtxi04cJqyYxFEXa7CcpAPGMG5e8g3UCEe1Rj/I7ebzxBe4bFkEvNkYQVN0ms2IqldqJfQsfUpnZcS635PK2E6ZGlBWqBIs4qhYKlA8RcRDLLUzCASug/xpazi0LE9iM85ZbHAwpKSYW7BSLmYjnTBtKUhS3wZEAJlgZNhQY1s+gXoGaWxTt7A2LKAUxESQOpUYVuQ6ADKuQsY+oBsMtIOdMZS1P/OWVqCbilhpsUuTi1XJpeXo/f7TNwbQvEtVMBVA2WrthaE8hys97F6BECbwtfh/SHYuyGo9BqDR1y6Pu7ZNHN2O7Z1At/72bXZHHxygiShXktFC0AZjEYxlP9EklGGiv0Oyhy3ccQhMLXxsyUYms6oNxA9iJFgmVQmb5timx3J0G7mddQh30s/APg92DsZqvPrWxT+gG7bGttjg8+Y7z/cNScyu4dNasyWso5b0fSiXbPuwXlts3m68MBZKA1W3bvoTPenSLSpSmzyti/EsXzZC0AXgtFOVtn1vM/QhsP8h94PHvJva5P2ep0ve9S1B9tK18LKT42OlIhSx04YtKmYdg+e6Wzhsvu2KzhdJ1ox61b6z12pA3l4hFSmVsnqRTLg9zVrpDq6vcyZApDD+/3T906iACzkuph5OxOJg8DjSNPAL5TH3ZgwGFHoCHTRBZpjPGij64JXzhIXBMhDRFFmo7C8BaekO0J0wluWmy1L9iRw6SlM57lGWzRjRGagiXXBhTE+7hVCcJBzGoEz37mgGDmgHFhMwxp2sFEtxQuxehUO7glzR6I2+gB1bJQEQRhWHdwtsuTOV7SPf42az8GrG2QeBh7vRi+BLyWKz/SMsQks/KrzXwsWJGi/JSNmy02HUSUH0zmgBscw5ybbZEK193F+hMwRQril1C9pvOrack9tTdBFmJzwAYcyr5NfZCHJ8QuL7jb4L5mY0l4TKy1DCLuPyGTN0hjddTOyoU1Sb1akFzJRx5DPCAGQ26LTleEFBpiG3A7MK2Ae7DNpwDd35JdUcrRFMUyY7wr8KpG7Izpyuxqp3neXjrGJsQkDI0YN9wnRFsc0GQujUuQahAxKMJETHwspFyWuqmqbtjLJHiuXsVvNGEKfDZce4pizIcv1piRHSKh2uJ1KXcydTkh8t4mjfSAzAtj+e77XZ49GDG6E3fiD6kIs0MuxqTk1cBlPnns056BBOpiseARt/lnSRZFmq5runBWCaOUk3mhuQCt35DfWPQAIm6h3aLcI/cm5Itd4heUI0+MbulDC97PpM5HnQzwoAimS3wsz7zSVJwIPJoyt+4Y7s6CQ4+aS24SK5y18pUnj1Tkz+IJ4qqBxbECrUtSpBhGCePo/Bhu1qc4sy6rWm619ZnqFWLmljCiE6ZqIgZklYByTl6zBzWo2o8R7Th/rmJnvZxG9XrT602vN4fqzaYM0WSvOL3i9IpzuOLUrUH8U1bKTq7Afv/KKl6wOKCy6o/P71hMfXvxA4up3oeuGyr3ICyQBjGlWEh/pyIYUd22CLu7yqNvL75rebTFur482pdH+/JoXx7ty6N9ebQvj/bl0b482pdH+/JoXx7ty6Ov7Pzqy6OvpjzK+/Lojy6PXrl0nP+RjT0DSiZon1StS6FW3Uv4I3Jlx63JCnN07R+b3LoE5f0/EmNyPTk7847SSKrlWa6kkZFMzzTkw4vxPwd3wm6//62QFwB/XpU/6wjzyzZNOiKfMJ+54hq2MrTN7GU5ra/k9on1PrHeV3J7ven1pq/k9orTK87fRXF2VXKxqHdfFhdOzsxqSNPZnvDS9e8s38yL9b7ZtnvnZFdE1UclMHPFo27331afZrv7e+vTW5/e+hzt7h6Quzk6Sxwi+8uaryB8P9GUBSA/lJBcwmsrM+szsuU7BuEjCEFywj3xUYLQuRTaoR+fn28ndHCP3FsWXBNdRBFo7TQzVxK/IOdtOoHFa1RbH0YQgbkR9ySIfbahREXmMl4jMHv3wkrLuxcRc/HIUh4Tmzf6am9idEH16QVtxcJeYCG+0OoEARN3Qrt6zu0zfYA1nZQvpQyolcK9L6Zs7lG0TSLL51J89pdO6Bn4l1M0qEebq7l9poVK6YSW6ZKIpemcRQ+j0mwN3dgRPDEsYbunBEaRzCgiwtdRPtfvqFy6QaWc1HLo5WXHKyf1Mxh0fD5+Nzz/ZTj+183FT5OfLibjX0fnv1z8jzafvmg+btHEZS89UcsTd7MpeBqivL7UvGfU1pqO+zTlORsMckfr1r0Gf9/liAn+PsohM9r3Rdylj50zgiset+WFjPYyd5u+Eu194xZFwOjg8sS+jQsvTOwb17wksW9k98WIvTTsugyxb1J1AaJec3DvoeNmwxGb7qvZh8yoK2K3bVmvavtBCb92CQ+UqEOHNqve+xjXqHTvHri531nJ3lqpO62b38u1+/JpeBTuo64uatbg9vC4WagLamrtak1Dj7aLNNuKdwjbN9agn4xqZxnocM5WxYNWWaWtFLM9E1sFhnpqo64QNIflhDpV3iS8Y7lNyloJw2NnN+OWE2ZX0WH7gArCvnZz24CHQV6rtT00DOn2HqQuTAtO5zB6Czbh9MVvu64tsC/bhqZTGoKwXiGWjLAD/Rh3XL0dnY/OO/336VpEiZJCFpp88A6Oxse6iM4hqstQWPILowsXPpHrlBl0pNGbRL/OBlz74cawQO+JeJOpScZiIHMXIVbwVglPgXDrPXpP1cUVfhpZKJlhmGGVhATP0lnH8k44b+yNrlxMjd6tSUBDjZotFljdamBuj+9CYaPAyq2vlje1/iAd0JRHIDTUVz3p+5xFCZCx3Ybar5ycna1WqxGzvbYQ56fqs/9cfbj8OL0cjkfno8RkqVUbdFozJgLA1dt+gnQ+/he83nf8O4CBxTrLU7RPG0/9s3ecb6lznO8HNEGHenJLn5/nTMN/VbrZYPO3AtSaTm7v0UNXnM2Rabd4vCXArPGqXPkPjtLhjQuEvEO//eZgw4+//jS9QbX3bxVmMsY5iq3Q+rIVnVCKLyVW18Bs2zNNmVgWzoNxMPHv/7YTTgw=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Receive an Event"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/event"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Receive a JSON object representing an event.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string"},"type":{"type":"string","enum":["transaction_created","transaction_status_changed","quote_created","customer_updated"],"description":"The transaction event type. Can be one of the following:\n- `transaction_created` - a transaction was created through the SEP endpoints. The payload is in the `transaction` field.\n- `transaction_status_changed` - the status of a transaction has changed. The payload is in the `transaction` field.\n- `quote_created` - a quote was created via the SEP38 API. The payload is in the `quote` field.\n"},"timestamp":{"type":"string","format":"date-time"},"payload":{"type":"object","properties":{"transaction":{"oneOf":[{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"},{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}]},"quote":{"type":"object","properties":{"id":{"type":"string"},"sell_amount":{"type":"string"},"sell_asset":{"type":"string"},"buy_amount":{"type":"string"},"buy_asset":{"type":"string"},"expires_at":{"type":"string","format":"date-time"},"price":{"type":"string"},"total_price":{"type":"string"},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"transaction_id":{"type":"string"},"created_at":{"type":"string","format":"date-time"}},"title":"Quote"},"customer":{"type":"object","properties":{"id":{"type":"string"}},"title":"Customer"}}}},"required":["id","type","payload","timestamp"],"title":"Event"}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"The event is successfully processed and ready to receive next event. The response body is empty."},"400":{"description":"The event is invalid or rejected. The response body contains the error message."}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/put-customer.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/put-customer.api.mdx
deleted file mode 100644
index e39841ff75..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/callbacks/put-customer.api.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
----
-id: put-customer
-title: "Create or Update Customer Info"
-description: "**The Anchor Platform does not persist any customer KYC data.**"
-sidebar_label: "Create or Update Customer Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJztGmtv47jxrxDsh7tdyHLWF7Sov6Ve78G9XjbNo8UhDmRKGkW8lUgdSSUxAv/3YkjJelhytr0W6AL+ksic4bw4M5wh+UoNe9R0fk8XpTYyB6Xpg0dfJhoKO3yzvJr8kXr2/4dZ9TE7rz5++IDYMehI8cJwKeicvn9/mwK5EFEqFbnKmEmkykksQRMhDSlAaa4NYWJLooon+emXBYmZYf7792uxFkhAwW8lWLyYKNCFFBpIIhUxKdcERFxILgxhCgiPQRgesYwYSUwKa3G/ubq7JdOa/ubh+9SYQs+n00du0jL0I5lPtYEsY6r+PymUNDKS2TTMZDjNmTagphBJvdUG8qmGYnJ29mHm5/EfasKTojTv1mJQ1hgSLiAmXBBnPB9VW2QcUOyiyHjE0GSa5OzLXl9NnrlJUQuSyCyTz1w87m0RynjrkeeURynhGq3xzFQMcaU3YdbofmV8vRZ5qQ15YhmPmQErXm1+REeLk4JpDbFXyW5KJSys1vA7TTY83vjkupYvksIwLlAuKbIt0Ubhd8Ihi1H6LFuLEMaEI6yl4aZlhumvWoqNpY4GMtsCBpmuRcgFU9s2Q/K1/PIyM7xgykzRKSdogB7LtaAelQUoK9QqpnNalKYODurRai3+IuMtnb/SajJ+9pXBMR2lkDP8Qup0TmX4K0SGerRQyMVw0AjlMf7tBhJGweojkUlnQVAht07Ot4yNlcrnZEIYKRQ8cVlqgjFQietTr5bArRfdeZRFkSyd7Iecb1xUEKnIz+ULxOTCYRNWmtTFm4G4se0+0p84cw5/Nsg0h1wOc0QIOmtZR3SyRcdijeqWGSM6ZQpiUomPAQEKrBBdCMbIpvrejAoTuNEhiRCCNrWSldr5Vi3bm4IdcvQoiDLHtMpj6tGU6RRx4MXQh12NfEwQFuFg1x+4JiGgoX76ZRFjGPhrcQPOHve3OPGmgIgnlWv+t1MhijbRbQ7vSCyjMgdh2tnP5u5cYroWifTX4pNUxO0hZCtLEjFRpUz8qYh8FlZtXTs55imXCRL+WLr4bJGZnaPjT+qs6/xoo6GYnU/2+wAaC9fRhfmBOxjFhHY2DsYisoVDeOX/LiP30iaqifyY1jLiGCw++WcKwgJUbuUniZJ5dzljKEDEmrhlXos2v+/Bf/S9xoo1Fa5tnHN0PjRzxtQjZooc3VC/G1Y24UqbQLAcWumpAWfsGJTFMUfWLDuKo0DrwAaD2gaRjIcRtWEGAqmCQsknLqJhrIib7SCgkNqwbJx8JccgLJchzyAQZR6CGsSAnPEsOEYj5MqkAe6wh2CPulWic2oR9uhFxkb0dPA3jRYy8WXc9hZa5aFj2nXw6vwzwusNKkUqxVFLWqxQ4b581OAvBhQ6lvX8BFRQbxmHLpGx8CjLKCwDlnF2dPFzKWB7jEoHz/poPMZPbQsjj3pLhTK8DX6EQkHkcsWdBrIZNsaGcKENsHhwUzPspcpeI6Bxt5FRVBbMCTMYC0Umt6DGCewxjpkgY+KxZI8w7tw8HndGHr8dHDwOuNYlfH1U8jiAl4K7beXfmnbEcXhx1A4aXgbHFSSgFMvGVrGTtIInUPut9+0M9hY6Ogk3GQ5dNXVvVYdb8EANfap0T5XuqdL9lirdU/F3Kv5Oxd+p+DsVf/+z4q9IpZFo8ERJV3qMEnQnmp1JIYu+fOUcIQ1T24AV6J0sC2QS1GS+ksIbdaqjVigpk0CBxrJgKH0Nkh6rcds0ZRJwEckhrxo2Uj0r408gBqUenPf/V1f/XNfSTYG9s4K6KtcqNjs7O8wVN2UUgdaYAv7jE+j6yAirNNyFS3v1M1StD27a5aDZ67LvYrFYXt0uP1KPXl1/XixvblaXP1KPXi6XH2+C1eWnz9Sj18u/LheI9GBLEjzPHxK0qTeuOsK1FbBzuldRB8oMZ5VG5v1A5TIercLbcyGPUnaWYSjDp5JHbXaUKcWQFjeQD8UXZt7CqdeChlJmwETlENW+EwcnIw0a6fd45N4JPfqP5fXq02pxcbv6fBlcL/9+t7qunBOUkkNp3q5ODlqzx6HNqBX1P0Krm3bhXU0/HwrwlbDXdu5W9PdEeXd1x/TwhiN9180SbvZDo9TSDtRqnB+qcSkN+SRLEX8LOlT1p9B4K0vn96/0C2zpvL4N96httb7uVnz3gH5hUlndIKIWzKR0Tve30hR3R/WEV+7Iq1QZndO6ZY1YlmEN4Iel5rjHTRyuDy8sL9Dr7VVvJHOKrNCG183N5NIh1Rm8CYb9QUgz5IrR7u+qAHPNez+g+rckrT231VU2o61msiVIv4fsgAZaxwY+0DE2QNcoNr87/eEBj47e3W6wlUC6TWA7Aza9H52dzc4nZ3+azP5Me21ef8KYXq2mrjfY7+VGwP2F6nRuveFuw9YD9vq0lilG2rOW/TtdWWu8acYOTN7twUbATevVItrruA4gfenq7qg/cmD2di/U9oROCzQAGBCl1/A0gH2f0xka845eV9P1t6EG5gDj0MDtur8VX1iyNz87VfNIuPSq35HYGcHCxC0S2xBjMnSwH/wz/4z23xbZ49qtiFIlBZ77LqosqcnF1Yp0zuaqt0LN8W7/RVKhJG4vfv3gaJyuO2nTzROdnMVAwm33NPg55RkQbs9iCyWxPHeHuvXrHXvXy0h08ALIJ7d40+tS+nd6f8itq6csuvU6iCUJRKbLuY8/xMIdA1ZbXqPejd1U0Et5BFiSzF9p5dwXBYtSIDO7DM3mNJ9On5+ffWahvlSP02qqnv5ttVhe3iwnM//MT02e2b0XE3DORIvwQgG+RpKK3BX2XVJdF5EVusFB+bgvG05Py05Py771p2VVxsebkGmRMW6bFxtdr1WBeE/3BeKDR1OpDY69voZMw53Kdjsc/q0EtaXz+wcsShVnIcb1PXYqKTC7S+6r14WTYXLrmr+qhh28xtt59aSLKILCtNAPCvZOgXt1d4u1Q/UmLndbF9K1ZL3mE2Xc7f4Fg5L/Sw==
-sidebar_class_name: "put api-method"
-info_path: docs/platforms/anchor-platform/api-reference/callbacks/callbacks-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-12,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create or Update Customer Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"put"}
-  path={"/customer"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-**The Anchor Platform does not persist any customer KYC data.**
-
-The request and response for this endpoint are identical to the
-[`PUT /customer`](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#customer-put)
-request and response defined in SEP-12.
-
-Client applications make requests with the following request body, which is forwarded to the anchor. Anchors
-must validate and persist the data passed, and return the customer's `id`. Requests containing only string fields will
-be forwarded to the anchor as with the `application/json` content type. Requests containing
-binary fields will be forwarded to the anchor as with the `multipart/form-data` content type.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","properties":{"id":{"description":"The ID of the customer as returned in the response of a previous PUT request.","type":"string"},"account":{"description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","type":"string"},"memo":{"description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","type":"string"},"memo_type":{"description":"The type of memo used to identify a customer with a shared account.","type":"string","enum":["id","hash","text"]},"type":{"description":"The type of action the customer is being KYCd for.\nSee the [Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification) documented in SEP-12 for more info.\nFor SEP-31 you can define your own types in the assets configuration.\nFor SEP-24 pre-defined value `sep24-customer` is used.\n","type":"string"},"transaction_id":{"description":"The transaction id with which the customer's info is associated. When information from the customer depends on the\ntransaction (e.g., more information is required for larger amounts)\n","type":"string"},"first_name":{"type":"string"},"last_name":{"type":"string"},"additional_name":{"type":"string"},"address_country_code":{"type":"string"},"state_or_province":{"type":"string"},"city":{"type":"string"},"postal_code":{"type":"string"},"address":{"type":"string"},"mobile_number":{"type":"string"},"email_address":{"type":"string"},"birth_date":{"type":"string","format":"date"},"birth_place":{"type":"string"},"birth_country_code":{"type":"string"},"bank_name":{"type":"string"},"bank_account_number":{"type":"string"},"bank_account_type":{"type":"string"},"bank_number":{"type":"string"},"bank_phone_number":{"type":"string"},"bank_branch_number":{"type":"string"},"external_transfer_memo":{"type":"string"},"clabe_number":{"type":"string"},"cbu_alias":{"type":"string"},"mobile_money_number":{"type":"string"},"mobile_money_provider":{"type":"string"},"crypto_address":{"type":"string"},"crypto_memo":{"description":"Deprecated. Use `external_transfer_memo` instead.","type":"string"},"tax_id":{"type":"string"},"tax_id_name":{"type":"string"},"occupation":{"type":"string"},"employer_name":{"type":"string"},"employer_address":{"type":"string"},"language_code":{"type":"string"},"id_type":{"type":"string"},"id_country_code":{"type":"string"},"id_issue_date":{"type":"string","format":"date"},"id_expiration_date":{"type":"string","format":"date"},"id_number":{"type":"string"},"ip_address":{"type":"string"},"sex":{"type":"string"},"referral_id":{"type":"string"},"mobile_number_verification":{"type":"string"},"email_address_verification":{"type":"string"}},"title":"PutCustomerRequest"}},"multipart/form-data":{"schema":{"type":"object","properties":{"id":{"description":"The ID of the customer as returned in the response of a previous PUT request.","type":"string"},"account":{"description":"The Stellar or Muxed Account authenticated with the Platform via SEP-10.","type":"string"},"memo":{"description":"The memo value identifying a customer with a shared account, where the shared account is `account`.","type":"string"},"memo_type":{"description":"The type of memo used to identify a customer with a shared account.","type":"string","enum":["id","hash","text"]},"type":{"description":"The type of action the customer is being KYCd for.\nSee the [Type Specification](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#type-specification) documented in SEP-12 for more info.\nFor SEP-31 you can define your own types in the assets configuration.\nFor SEP-24 pre-defined value `sep24-customer` is used.\n","type":"string"},"first_name":{"type":"string"},"last_name":{"type":"string"},"additional_name":{"type":"string"},"address_country_code":{"type":"string"},"state_or_province":{"type":"string"},"city":{"type":"string"},"postal_code":{"type":"string"},"address":{"type":"string"},"mobile_number":{"type":"string"},"email_address":{"type":"string"},"birth_date":{"type":"string","format":"date"},"birth_place":{"type":"string"},"birth_country_code":{"type":"string"},"bank_name":{"type":"string"},"bank_account_number":{"type":"string"},"bank_account_type":{"type":"string"},"bank_number":{"type":"string"},"bank_phone_number":{"type":"string"},"bank_branch_number":{"type":"string"},"external_transfer_memo":{"type":"string"},"clabe_number":{"type":"string"},"cbu_alias":{"type":"string"},"mobile_money_number":{"type":"string"},"mobile_money_provider":{"type":"string"},"crypto_address":{"type":"string"},"crypto_memo":{"description":"Deprecated. Use `external_transfer_memo` instead.","type":"string"},"tax_id":{"type":"string"},"tax_id_name":{"type":"string"},"occupation":{"type":"string"},"employer_name":{"type":"string"},"employer_address":{"type":"string"},"language_code":{"type":"string"},"id_type":{"type":"string"},"id_country_code":{"type":"string"},"id_issue_date":{"type":"string","format":"date"},"id_expiration_date":{"type":"string","format":"date"},"id_number":{"type":"string"},"photo_id_front":{"type":"string","format":"binary"},"photo_id_back":{"type":"string","format":"binary"},"notary_approval_of_photo_id":{"type":"string","format":"binary"},"ip_address":{"type":"string"},"photo_proof_residence":{"type":"string","format":"binary"},"sex":{"type":"string"},"photo_proof_of_income":{"type":"string","format":"binary"},"proof_of_liveness":{"type":"string","format":"binary"},"referral_id":{"type":"string"},"mobile_number_verification":{"type":"string"},"email_address_verification":{"type":"string"}},"title":"PutCustomerMultipartRequest"}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Success.","content":{"application/json":{"schema":{"type":"object","required":["status"],"properties":{"id":{"type":"string"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","NEEDS_INFO","REJECTED"]},"fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"}}}},"provided_fields":{"type":"object","additionalProperties":{"required":["type","description"],"properties":{"type":{"type":"string","enum":["string","binary","number","date"]},"description":{"type":"string"},"choices":{"type":"array","items":{"type":"string"}},"optional":{"type":"boolean"},"status":{"type":"string","enum":["ACCEPTED","PROCESSING","REJECTED","VERIFICATION_REQUIRED"]},"error":{"type":"string"}}}},"message":{"type":"string"}},"title":"GetCustomerResponse"}}}},"400":{"description":"Invalid data.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Not Found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/README.mdx
deleted file mode 100644
index a6aa25336e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/README.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Servidor de Platform Server
-sidebar_position: 10
----
-
-import { MethodTable } from "@site/src/components/MethodTable";
-
-Los datos en la Anchor Platform están disponibles a través de dos APIs diferentes: una API REST y una API JSON-RPC. Cada una de estas APIs tiene documentación asociada aquí.
-
-<MethodTable title="Tipos de API">
-
-|                                       |   |
-| ------------------------------------- | - |
-| [REST API](./transactions/README.mdx) |   |
-| [JSON-RPC API](./rpc/README.mdx)      |   |
-
-</MethodTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/README.mdx
deleted file mode 100644
index caecc23ae8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: API JSON-RPC
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Interactúa con tu instancia de Anchor Platform mediante solicitudes RPC ligeras y fáciles de usar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json
deleted file mode 100644
index 8fa9f9e324..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/anchor-platform.openrpc.json
+++ /dev/null
@@ -1,10163 +0,0 @@
-{
-  "openrpc": "1.2.6",
-  "info": {
-    "title": "Anchor Platform",
-    "description": "The Anchor Platform is a set of tools and APIs that enable developers and businesses to build their own on and off-ramp services for the Stellar network. It provides a standardized interface, including the implementation of several Stellar Ecosystem Proposals (SEPs), to make it easy for businesses to integrate with Stellar-based wallets and exchanges.",
-    "termsOfService": "https://stellar.org/terms-of-service",
-    "contact": {
-      "name": "Stellar Development Foundation",
-      "url": "https://stellar.org/connect",
-      "email": "hello@stellar.org"
-    },
-    "license": {
-      "name": "Apache 2.0",
-      "url": "https://www.apache.org/licenses/LICENSE-2.0.html"
-    },
-    "version": "2.8.4"
-  },
-  "servers": [
-    {
-      "name": "Platform API",
-      "url": "https://platform-server.exampleanchor.com",
-      "summary": "Example URL endpoint for the Platform Server.",
-      "description": "Example URL endpoint for the Platform Server. Note: This is an example URL only, you must configure your own Platform Server."
-    }
-  ],
-  "methods": [
-    {
-      "name": "do_stellar_payment",
-      "summary": "Submits a Stellar payment",
-      "description": "Submits a payment to a stellar network by a custody service.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "do_stellar_paymentResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "do_stellar_paymentExample",
-          "description": "Example request to the `do_stellar_payment` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Do Stellar payment"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "do_stellar_refund",
-      "summary": "Submits a Stellar refund",
-      "description": "Submits a refund payment to a stellar network by a custody service",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "refund",
-          "description": "An object describing refund associated with this transaction.",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "amount_fee"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "Amount to be refunded",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "Amount of assets to refund",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of refund",
-                    "type": "string"
-                  }
-                }
-              },
-              "amount_fee": {
-                "title": "amount_fee",
-                "description": "Amount of fee",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "The amount of fee",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of fee charged by anchor",
-                    "type": "string"
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "do_stellar_refundResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "do_stellar_refundExample",
-          "description": "Example request to the `do_stellar_refund` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Do Stellar refund"
-            },
-            {
-              "name": "refund",
-              "value": {
-                "amount": {
-                  "amount": 1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                },
-                "amount_fee": {
-                  "amount": 0.1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                }
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "get_transaction",
-      "summary": "Retrieve a transaction.",
-      "description": "Retrieve a transaction by its ID.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "get_transactionResponse",
-        "schema": {
-          "title": "Platform Transaction",
-          "description": "A platform transaction object",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "funding_method": {
-              "description": "Funding method used for transferring or settling assets.",
-              "type": "string"
-            },
-            "type": {
-              "description": "DEPRECATED in favor of funding_method. Type of deposit, withdrawal or receive.",
-              "type": "string"
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "user_action_required_by": {
-              "title": "user_action_required_by",
-              "description": "Time and date by which user action is required.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "stellar_transactions": {
-              "type": "array",
-              "items": {
-                "title": "stellar_transaction",
-                "type": "object",
-                "required": [
-                  "id",
-                  "created_at",
-                  "envelope",
-                  "payments"
-                ],
-                "properties": {
-                  "id": {
-                    "title": "hash",
-                    "description": "The Stellar transaction hash.",
-                    "type": "string"
-                  },
-                  "memo": {
-                    "title": "memo",
-                    "type": "string"
-                  },
-                  "memo_type": {
-                    "title": "memo_type",
-                    "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-                    "type": "string",
-                    "enum": [
-                      "id",
-                      "hash",
-                      "text"
-                    ]
-                  },
-                  "created_at": {
-                    "title": "created_at",
-                    "description": "The date and time when the transaction is created.",
-                    "type": "string"
-                  },
-                  "envelop": {
-                    "description": "The transaction envelope, containing all the transaction information.",
-                    "type": "string"
-                  },
-                  "payments": {
-                    "type": "array",
-                    "items": {
-                      "required": [
-                        "id",
-                        "payment_type",
-                        "source_account",
-                        "destination_account",
-                        "amount"
-                      ],
-                      "properties": {
-                        "id": {
-                          "description": " The ID of the payment in the Stellar Network.",
-                          "type": "string"
-                        },
-                        "payment_type": {
-                          "description": " The ID of the payment in the Stellar Network.",
-                          "type": "string",
-                          "enum": [
-                            "payment",
-                            "path_payment"
-                          ],
-                          "default": "payment"
-                        },
-                        "source_account": {
-                          "title": "source_account",
-                          "description": "The account being debited in the Stellar Network.",
-                          "type": "string"
-                        },
-                        "destination_account": {
-                          "title": "destination_account",
-                          "description": "The account being credited in the Stellar Network.",
-                          "type": "string"
-                        },
-                        "amount": {
-                          "type": "object",
-                          "properties": {
-                            "amount": {
-                              "title": "amount",
-                              "description": "A stringified amount of an asset.",
-                              "type": "string"
-                            },
-                            "asset": {
-                              "title": "asset",
-                              "description": "An asset.",
-                              "type": "string"
-                            }
-                          }
-                        }
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "source_account": {
-              "title": "source_account",
-              "description": "The account being debited in the Stellar Network.",
-              "type": "string"
-            },
-            "destination_account": {
-              "title": "destination_account",
-              "description": "The account being credited in the Stellar Network.",
-              "type": "string"
-            },
-            "external_transaction_id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "memo": {
-              "title": "memo",
-              "type": "string"
-            },
-            "memo_type": {
-              "title": "memo_type",
-              "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-              "type": "string",
-              "enum": [
-                "id",
-                "hash",
-                "text"
-              ]
-            },
-            "refund_memo": {
-              "title": "memo",
-              "type": "string"
-            },
-            "refund_memo_type": {
-              "title": "memo_type",
-              "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-              "type": "string",
-              "enum": [
-                "id",
-                "hash",
-                "text"
-              ]
-            },
-            "client_domain": {
-              "description": "The domain of the client.",
-              "type": "string"
-            },
-            "request_client_ip_address": {
-              "description": "The IP address of the client requesting the transaction.",
-              "type": "string"
-            },
-            "customers": {
-              "description": "The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\n            this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.",
-              "type": "object",
-              "properties": {
-                "sender": {
-                  "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                  "type": "object",
-                  "properties": {
-                    "id": {
-                      "type": "string",
-                      "description": "The `id` of the customer registered through SEP-12."
-                    },
-                    "account": {
-                      "type": "string",
-                      "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                    },
-                    "memo": {
-                      "type": "string",
-                      "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                    }
-                  }
-                },
-                "receiver": {
-                  "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                  "type": "object",
-                  "properties": {
-                    "id": {
-                      "type": "string",
-                      "description": "The `id` of the customer registered through SEP-12."
-                    },
-                    "account": {
-                      "type": "string",
-                      "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                    },
-                    "memo": {
-                      "type": "string",
-                      "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                    }
-                  }
-                }
-              }
-            },
-            "creator": {
-              "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-              "type": "object",
-              "properties": {
-                "id": {
-                  "type": "string",
-                  "description": "The `id` of the customer registered through SEP-12."
-                },
-                "account": {
-                  "type": "string",
-                  "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                },
-                "memo": {
-                  "type": "string",
-                  "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "get_transactionExample",
-          "description": "Example request to the `get_transaction` method.",
-          "params": [
-            {
-              "name": "id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            }
-          ],
-          "result": {
-            "name": "platformTransactionResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "31",
-              "kind": "receive",
-              "status": "completed",
-              "funding_method": "SWIFT",
-              "amount_expected": {
-                "amount": "100",
-                "asset": "iso4217:USD"
-              },
-              "amount_in": {
-                "amount": "100.0000",
-                "asset": "iso4217:USD"
-              },
-              "amount_out": {
-                "amount": "98.0000000",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "fee_details": {
-                "total": "2.0000",
-                "asset": "iso4217:USD"
-              },
-              "quote_id": "quote-id",
-              "message": "Please don't forget to foo bar",
-              "refunds": {
-                "amount_refunded": {
-                  "amount": "90.0000",
-                  "asset": "iso4217:USD"
-                },
-                "amount_fee": {
-                  "amount": "8.0000",
-                  "asset": "iso4217:USD"
-                },
-                "payments": [
-                  {
-                    "id": "1111",
-                    "id_type": "stellar",
-                    "amount": {
-                      "amount": "50.0000",
-                      "asset": "iso4217:USD"
-                    },
-                    "fee": {
-                      "amount": "4.0000",
-                      "asset": "iso4217:USD"
-                    }
-                  },
-                  {
-                    "id": "2222",
-                    "id_type": "stellar",
-                    "amount": {
-                      "amount": "40.0000",
-                      "asset": "iso4217:USD"
-                    },
-                    "fee": {
-                      "amount": "4.0000",
-                      "asset": "iso4217:USD"
-                    }
-                  }
-                ]
-              },
-              "stellar_transactions": [
-                {
-                  "id": "stellar-tx-id",
-                  "memo": "my-memo",
-                  "memo_type": "text",
-                  "envelope": "here_comes_the_envelope",
-                  "payments": [
-                    {
-                      "id": "payment-id",
-                      "amount": {
-                        "amount": "100.0000",
-                        "asset": "iso4217:USD"
-                      },
-                      "payment_type": "payment",
-                      "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-                      "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-                    }
-                  ]
-                }
-              ],
-              "external_transaction_id": "external-tx-id",
-              "customers": {
-                "sender": {
-                  "id": "sender-id"
-                },
-                "receiver": {
-                  "id": "receiver-id"
-                }
-              },
-              "creator": {
-                "id": "creator-id"
-              }
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "get_transactions",
-      "summary": "Retrieve a list of transactions.",
-      "description": "Query a list of transactions by SEP, transaction status or other criteria.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "sep",
-          "summary": "Sep of the transaction.",
-          "description": "Sep of the transaction belongs to",
-          "required": true,
-          "schema": {
-            "title": "sep",
-            "description": "Protocol of the transaction.",
-            "type": "integer",
-            "enum": [
-              6,
-              24,
-              31
-            ]
-          }
-        },
-        {
-          "name": "order_by",
-          "summary": "The field that transactions will be ordered by .",
-          "description": "Specifies field that transactions will be ordered by. Note, that secondary sort is transaction id in ascending value.",
-          "required": false,
-          "schema": {
-            "title": "order_by",
-            "description": "The order by string used to sort the results.",
-            "type": "string",
-            "enum": [
-              "created_at",
-              "transfer_received_at",
-              "user_action_required_by"
-            ],
-            "default": "created_at"
-          }
-        },
-        {
-          "name": "statuses",
-          "summary": "The statuses of transactions.",
-          "description": "The statuses of the transaction to filter by.",
-          "required": false,
-          "schema": {
-            "title": "status",
-            "description": "The statuses of the transaction to filter by.",
-            "type": "array",
-            "enum": [
-              "incomplete",
-              "completed",
-              "refunded",
-              "expired",
-              "error",
-              "pending_stellar",
-              "pending_external",
-              "pending_user_transfer_start",
-              "pending_user_transfer_complete",
-              "pending_anchor",
-              "pending_trust",
-              "pending_user",
-              "no_market",
-              "too_small",
-              "too_large",
-              "pending_sender",
-              "pending_receiver",
-              "pending_transaction_info_update",
-              "pending_customer_info_update"
-            ]
-          }
-        },
-        {
-          "name": "page_size",
-          "summary": "The number of transactions to return.",
-          "description": "The number of records to return in each page.",
-          "required": false,
-          "schema": {
-            "title": "page_size",
-            "description": "The number of records to return in each page.",
-            "type": "integer",
-            "default": 20
-          }
-        },
-        {
-          "name": "page_number",
-          "summary": "The page number of transactions to return.",
-          "description": "Page number to use for continuous search. Page count beings at 0.",
-          "required": false,
-          "schema": {
-            "title": "page_number",
-            "description": "Page number to use for continuous search. Page count beings at 0.",
-            "type": "integer",
-            "default": 0
-          }
-        }
-      ],
-      "result": {
-        "name": "get_transactionResponse",
-        "schema": {
-          "type": "object",
-          "properties": {
-            "records": {
-              "type": "array",
-              "items": {
-                "title": "Platform Transaction",
-                "description": "A platform transaction object",
-                "type": "object",
-                "properties": {
-                  "id": {
-                    "title": "transaction_id",
-                    "description": "A unique transaction identifier.",
-                    "type": "string"
-                  },
-                  "sep": {
-                    "title": "sep",
-                    "description": "Protocol of the transaction.",
-                    "type": "integer",
-                    "enum": [
-                      6,
-                      24,
-                      31
-                    ]
-                  },
-                  "kind": {
-                    "title": "kind",
-                    "description": "The kind of transaction that is desired.",
-                    "type": "string",
-                    "enum": [
-                      "undefined",
-                      "receive",
-                      "deposit",
-                      "deposit-exchange",
-                      "withdrawal",
-                      "withdrawal-exchange"
-                    ]
-                  },
-                  "status": {
-                    "title": "status",
-                    "description": "Processing status of the transaction.",
-                    "type": "string",
-                    "enum": [
-                      "pending_anchor",
-                      "pending_trust",
-                      "pending_user",
-                      "pending_user_transfer_start",
-                      "pending_user_transfer_complete",
-                      "incomplete",
-                      "no_market",
-                      "too_small",
-                      "too_large",
-                      "pending_sender",
-                      "pending_receiver",
-                      "pending_transaction_info_update",
-                      "pending_customer_info_update",
-                      "completed",
-                      "refunded",
-                      "expired",
-                      "error",
-                      "pending_external",
-                      "pending_stellar"
-                    ]
-                  },
-                  "funding_method": {
-                    "description": "Funding method used for transferring or settling assets.",
-                    "type": "string"
-                  },
-                  "type": {
-                    "description": "DEPRECATED in favor of funding_method. Type of deposit, withdrawal or receive.",
-                    "type": "string"
-                  },
-                  "amount_expected": {
-                    "type": "object",
-                    "title": "amount_expected",
-                    "description": "The amount expected in the payment.",
-                    "properties": {
-                      "amount": {
-                        "title": "amount",
-                        "description": "A stringified amount of an asset.",
-                        "type": "string"
-                      },
-                      "asset": {
-                        "title": "asset",
-                        "description": "An asset.",
-                        "type": "string"
-                      }
-                    }
-                  },
-                  "amount_in": {
-                    "type": "object",
-                    "title": "amount_in",
-                    "description": "Amount expected/received by anchor.",
-                    "properties": {
-                      "amount": {
-                        "title": "amount",
-                        "description": "A stringified amount of an asset.",
-                        "type": "string"
-                      },
-                      "asset": {
-                        "title": "asset",
-                        "description": "An asset.",
-                        "type": "string"
-                      }
-                    }
-                  },
-                  "amount_out": {
-                    "type": "object",
-                    "title": "amount_out",
-                    "description": "The amount expected to be sent by anchor to user at end of transaction.",
-                    "properties": {
-                      "amount": {
-                        "title": "amount",
-                        "description": "A stringified amount of an asset.",
-                        "type": "string"
-                      },
-                      "asset": {
-                        "title": "asset",
-                        "description": "An asset.",
-                        "type": "string"
-                      }
-                    }
-                  },
-                  "fee_details": {
-                    "title": "fee_details",
-                    "description": "Description of fee charged by the anchor.",
-                    "type": "object",
-                    "required": [
-                      "total",
-                      "asset"
-                    ],
-                    "properties": {
-                      "total": {
-                        "type": "number"
-                      },
-                      "asset": {
-                        "type": "string"
-                      },
-                      "details": {
-                        "type": "array",
-                        "description": "Details about fee charged.",
-                        "items": {
-                          "properties": {
-                            "name": {
-                              "type": "string"
-                            },
-                            "description": {
-                              "type": "string"
-                            },
-                            "amount": {
-                              "type": "number"
-                            }
-                          }
-                        }
-                      }
-                    }
-                  },
-                  "quote_id": {
-                    "title": "quote_id",
-                    "description": "The id returned from a SEP-38 POST /quote response",
-                    "type": "string"
-                  },
-                  "started_at": {
-                    "title": "started_at",
-                    "description": "Start date and time of transaction.",
-                    "type": "string"
-                  },
-                  "updated_at": {
-                    "title": "updated_at",
-                    "description": "The date and time of transaction reaching the current status.",
-                    "type": "string"
-                  },
-                  "completed_at": {
-                    "title": "completed_at",
-                    "description": "The date and time of transaction reaching completed or refunded status.",
-                    "type": "string"
-                  },
-                  "transfer_received_at": {
-                    "title": "transfer_received_at",
-                    "description": "The date and time of receiving transfer.",
-                    "type": "string"
-                  },
-                  "user_action_required_by": {
-                    "title": "user_action_required_by",
-                    "description": "Time and date by which user action is required.",
-                    "type": "string"
-                  },
-                  "message": {
-                    "title": "message",
-                    "description": "Human readable explanation of transaction status",
-                    "type": "string"
-                  },
-                  "refunds": {
-                    "title": "refunds",
-                    "description": "An object describing any on or offchain refund associated with this transaction.",
-                    "type": "object",
-                    "properties": {
-                      "amount_refunded": {
-                        "type": "object",
-                        "description": "The total amount refunded in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "amount_fee": {
-                        "type": "object",
-                        "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "payments": {
-                        "type": "array",
-                        "description": "A list of objects containing information on the individual payments made back as refunds.",
-                        "items": {
-                          "properties": {
-                            "id": {
-                              "title": "id",
-                              "description": "The Stellar transaction hash.",
-                              "type": "string"
-                            },
-                            "id_type": {
-                              "type": "string"
-                            },
-                            "amount": {
-                              "type": "object",
-                              "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                              "properties": {
-                                "amount": {
-                                  "title": "amount",
-                                  "description": "A numerical representation of an amount of some asset.",
-                                  "type": "string"
-                                },
-                                "asset": {
-                                  "title": "asset",
-                                  "description": "An asset.",
-                                  "type": "string"
-                                }
-                              }
-                            },
-                            "fee": {
-                              "type": "object",
-                              "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                              "properties": {
-                                "amount": {
-                                  "title": "amount",
-                                  "description": "A numerical representation of an amount of some asset.",
-                                  "type": "string"
-                                },
-                                "asset": {
-                                  "title": "asset",
-                                  "description": "An asset.",
-                                  "type": "string"
-                                }
-                              }
-                            },
-                            "requested_at": {
-                              "title": "datetime",
-                              "description": "The date and time of requesting refund.",
-                              "type": "string"
-                            },
-                            "refunded_at": {
-                              "title": "datetime",
-                              "description": "The date and time of making refund.",
-                              "type": "string"
-                            }
-                          }
-                        }
-                      }
-                    }
-                  },
-                  "stellar_transactions": {
-                    "type": "array",
-                    "items": {
-                      "title": "stellar_transaction",
-                      "type": "object",
-                      "required": [
-                        "id",
-                        "created_at",
-                        "envelope",
-                        "payments"
-                      ],
-                      "properties": {
-                        "id": {
-                          "title": "hash",
-                          "description": "The Stellar transaction hash.",
-                          "type": "string"
-                        },
-                        "memo": {
-                          "title": "memo",
-                          "type": "string"
-                        },
-                        "memo_type": {
-                          "title": "memo_type",
-                          "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-                          "type": "string",
-                          "enum": [
-                            "id",
-                            "hash",
-                            "text"
-                          ]
-                        },
-                        "created_at": {
-                          "title": "created_at",
-                          "description": "The date and time when the transaction is created.",
-                          "type": "string"
-                        },
-                        "envelop": {
-                          "description": "The transaction envelope, containing all the transaction information.",
-                          "type": "string"
-                        },
-                        "payments": {
-                          "type": "array",
-                          "items": {
-                            "required": [
-                              "id",
-                              "payment_type",
-                              "source_account",
-                              "destination_account",
-                              "amount"
-                            ],
-                            "properties": {
-                              "id": {
-                                "description": " The ID of the payment in the Stellar Network.",
-                                "type": "string"
-                              },
-                              "payment_type": {
-                                "description": " The ID of the payment in the Stellar Network.",
-                                "type": "string",
-                                "enum": [
-                                  "payment",
-                                  "path_payment"
-                                ],
-                                "default": "payment"
-                              },
-                              "source_account": {
-                                "title": "source_account",
-                                "description": "The account being debited in the Stellar Network.",
-                                "type": "string"
-                              },
-                              "destination_account": {
-                                "title": "destination_account",
-                                "description": "The account being credited in the Stellar Network.",
-                                "type": "string"
-                              },
-                              "amount": {
-                                "type": "object",
-                                "properties": {
-                                  "amount": {
-                                    "title": "amount",
-                                    "description": "A stringified amount of an asset.",
-                                    "type": "string"
-                                  },
-                                  "asset": {
-                                    "title": "asset",
-                                    "description": "An asset.",
-                                    "type": "string"
-                                  }
-                                }
-                              }
-                            }
-                          }
-                        }
-                      }
-                    }
-                  },
-                  "source_account": {
-                    "title": "source_account",
-                    "description": "The account being debited in the Stellar Network.",
-                    "type": "string"
-                  },
-                  "destination_account": {
-                    "title": "destination_account",
-                    "description": "The account being credited in the Stellar Network.",
-                    "type": "string"
-                  },
-                  "external_transaction_id": {
-                    "title": "transaction_id",
-                    "description": "A unique transaction identifier.",
-                    "type": "string"
-                  },
-                  "memo": {
-                    "title": "memo",
-                    "type": "string"
-                  },
-                  "memo_type": {
-                    "title": "memo_type",
-                    "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-                    "type": "string",
-                    "enum": [
-                      "id",
-                      "hash",
-                      "text"
-                    ]
-                  },
-                  "refund_memo": {
-                    "title": "memo",
-                    "type": "string"
-                  },
-                  "refund_memo_type": {
-                    "title": "memo_type",
-                    "description": "The memo type of the transaction in the Stellar network. Should be present if memo is not null.",
-                    "type": "string",
-                    "enum": [
-                      "id",
-                      "hash",
-                      "text"
-                    ]
-                  },
-                  "client_domain": {
-                    "description": "The domain of the client.",
-                    "type": "string"
-                  },
-                  "request_client_ip_address": {
-                    "description": "The IP address of the client requesting the transaction.",
-                    "type": "string"
-                  },
-                  "customers": {
-                    "description": "The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\n            this object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.",
-                    "type": "object",
-                    "properties": {
-                      "sender": {
-                        "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                        "type": "object",
-                        "properties": {
-                          "id": {
-                            "type": "string",
-                            "description": "The `id` of the customer registered through SEP-12."
-                          },
-                          "account": {
-                            "type": "string",
-                            "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                          },
-                          "memo": {
-                            "type": "string",
-                            "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                          }
-                        }
-                      },
-                      "receiver": {
-                        "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                        "type": "object",
-                        "properties": {
-                          "id": {
-                            "type": "string",
-                            "description": "The `id` of the customer registered through SEP-12."
-                          },
-                          "account": {
-                            "type": "string",
-                            "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                          },
-                          "memo": {
-                            "type": "string",
-                            "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                          }
-                        }
-                      }
-                    }
-                  },
-                  "creator": {
-                    "description": "A object that identify end-user. \nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend. \nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used. \nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.",
-                    "type": "object",
-                    "properties": {
-                      "id": {
-                        "type": "string",
-                        "description": "The `id` of the customer registered through SEP-12."
-                      },
-                      "account": {
-                        "type": "string",
-                        "description": "Either the Stellar account or Muxed account address of the on-chain entity."
-                      },
-                      "memo": {
-                        "type": "string",
-                        "description": "The memo value identifying a customer with a shared account, where the shared account is `account`."
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "get_transactionsExample",
-          "description": "Example request to the `get_transactions` method.",
-          "params": [
-            {
-              "name": "sep",
-              "value": "31"
-            },
-            {
-              "name": "order_by",
-              "value": "created_at"
-            },
-            {
-              "name": "statuses",
-              "value": [
-                "completed"
-              ]
-            }
-          ],
-          "result": {
-            "name": "platformTransactionResponses",
-            "value": {
-              "records": [
-                {
-                  "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-                  "sep": "31",
-                  "kind": "receive",
-                  "status": "completed",
-                  "funding_method": "SWIFT",
-                  "amount_expected": {
-                    "amount": "100",
-                    "asset": "iso4217:USD"
-                  },
-                  "amount_in": {
-                    "amount": "100.0000",
-                    "asset": "iso4217:USD"
-                  },
-                  "amount_out": {
-                    "amount": "98.0000000",
-                    "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                  },
-                  "fee_details": {
-                    "total": "2.0000",
-                    "asset": "iso4217:USD"
-                  },
-                  "quote_id": "quote-id",
-                  "message": "Please don't forget to foo bar",
-                  "refunds": {
-                    "amount_refunded": {
-                      "amount": "90.0000",
-                      "asset": "iso4217:USD"
-                    },
-                    "amount_fee": {
-                      "amount": "8.0000",
-                      "asset": "iso4217:USD"
-                    },
-                    "payments": [
-                      {
-                        "id": "1111",
-                        "id_type": "stellar",
-                        "amount": {
-                          "amount": "50.0000",
-                          "asset": "iso4217:USD"
-                        },
-                        "fee": {
-                          "amount": "4.0000",
-                          "asset": "iso4217:USD"
-                        }
-                      },
-                      {
-                        "id": "2222",
-                        "id_type": "stellar",
-                        "amount": {
-                          "amount": "40.0000",
-                          "asset": "iso4217:USD"
-                        },
-                        "fee": {
-                          "amount": "4.0000",
-                          "asset": "iso4217:USD"
-                        }
-                      }
-                    ]
-                  },
-                  "stellar_transactions": [
-                    {
-                      "id": "stellar-tx-id",
-                      "memo": "my-memo",
-                      "memo_type": "text",
-                      "envelope": "here_comes_the_envelope",
-                      "payments": [
-                        {
-                          "id": "payment-id",
-                          "amount": {
-                            "amount": "100.0000",
-                            "asset": "iso4217:USD"
-                          },
-                          "payment_type": "payment",
-                          "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-                          "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-                        }
-                      ]
-                    }
-                  ],
-                  "external_transaction_id": "external-tx-id",
-                  "customers": {
-                    "sender": {
-                      "id": "sender-id"
-                    },
-                    "receiver": {
-                      "id": "receiver-id"
-                    }
-                  },
-                  "creator": {
-                    "id": "creator-id"
-                  }
-                }
-              ]
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_amounts_updated",
-      "summary": "Update transaction amounts",
-      "description": "Update amount_out and fee_details values",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_amounts_updatedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_amounts_updatedExample",
-          "description": "Example request to the `notify_amounts_updated` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Amounts updated"
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 1
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_customer_info_updated",
-      "summary": "Customer info updated",
-      "description": "The customer's status for the transaction has been updated. Use this method to notify the wallet of the status change. If `customer_id` and `customer_type` are provided, the transaction status will reflect the customer's status. If not, the transaction status will default to the standard pending status for the SEP.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "customer_id",
-          "description": "The SEP-12 ID of the customer",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        },
-        {
-          "name": "customer_type",
-          "description": "The SEP-12 type of the customer",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_customer_info_updatedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_customer_info_updatedExample",
-          "description": "Example request to the `notify_customer_info_updated` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Customer info updated"
-            },
-            {
-              "name": "customer_id",
-              "value": "45f8884d-d6e1-477f-a680-503179263359"
-            },
-            {
-              "name": "customer_type",
-              "value": "sep31-receiver"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_interactive_flow_completed",
-      "summary": "Interactive flow completed",
-      "description": "Platform has collected the transaction amounts and fees from the business",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_expected",
-          "description": "The amount expected in the payment",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_interactive_flow_completedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_interactive_flow_completedExample",
-          "description": "Example request to the `notify_interactive_flow_completed` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Interactive flow completed successfully."
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 0.9,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "amount_expected",
-              "value": {
-                "amount": 1
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_offchain_funds_available",
-      "summary": "Offchain funds are available",
-      "description": "Funds are ready for the user / recipient to pick up.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "external_transaction_id",
-          "summary": "ID of the transaction on external network",
-          "description": "The unique identifier of this transaction on the external network.",
-          "required": false,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_offchain_funds_availableResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_offchain_funds_availableExample",
-          "description": "Example request to the `notify_offchain_funds_available` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Offchain funds available"
-            },
-            {
-              "name": "stellar_transaction_id",
-              "value": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_offchain_funds_pending",
-      "summary": "Offchain funds pending",
-      "description": "Payment has been submitted to external network, but is not yet confirmed",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "external_transaction_id",
-          "summary": "ID of the transaction on external network",
-          "description": "The unique identifier of this transaction on the external network.",
-          "required": false,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_offchain_funds_pendingResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_offchain_funds_pendingExample",
-          "description": "Example request to the `notify_offchain_funds_pending` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Offchain funds pending"
-            },
-            {
-              "name": "external_transaction_id",
-              "value": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_offchain_funds_received",
-      "summary": "Offchain funds received",
-      "description": "Payment is being processed internally by anchor",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "funds_received_at",
-          "description": "The date and time of receiving funds.",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "external_transaction_id",
-          "summary": "ID of the transaction on external network",
-          "description": "The unique identifier of this transaction on the external network.",
-          "required": false,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_offchain_funds_receivedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_offchain_funds_receivedExample",
-          "description": "Example request to the `notify_offchain_funds_received` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Funds received successfully"
-            },
-            {
-              "name": "funds_received_at",
-              "value": "2023-07-04T12:34:56Z"
-            },
-            {
-              "name": "external_transaction_id",
-              "value": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1
-              }
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 0.9
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "amount_expected",
-              "value": {
-                "amount": 1
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_offchain_funds_sent",
-      "summary": "Offchain funds sent",
-      "description": "Transaction flow is fully completed for the SEP-6 and SEP-24 withdrawal flow or SEP-31 receive flow. Payment has been submitted to external network, but is not yet confirmed for SEP-24 deposit flow",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "funds_sent_at",
-          "description": "The date and time of sending funds.",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "external_transaction_id",
-          "summary": "ID of the transaction on external network",
-          "description": "The unique identifier of this transaction on the external network.",
-          "required": false,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_offchain_funds_sentResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_offchain_funds_sentExample",
-          "description": "Example request to the `notify_offchain_funds_sent` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Offchain funds sent"
-            },
-            {
-              "name": "funds_sent_at",
-              "value": "2023-07-04T12:34:38Z"
-            },
-            {
-              "name": "external_transaction_id",
-              "value": "3320c6faad48c3cf39b6d4ac15ed50b6e5868b62551e69cde15df2d66c8ca360"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_onchain_funds_received",
-      "summary": "Onchain funds received",
-      "description": "Notify that the payment is being processed internally by anchor for SEP-6 or SEP-24. For SEP-31, notify that the payment is being processed by the Receiving Anchor. In the request, amount parameters are optional, but have a strict rule of how to set them. Either none, only `amount_in`, or all of fields (`amount_in`, `amount_out`, `fee_details`) must be specified. ",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "stellar_transaction_id",
-          "summary": "Transaction ID on Stellar",
-          "description": "The unique transaction identifier for this transfer on the Stellar network.",
-          "required": true,
-          "schema": {
-            "title": "hash",
-            "description": "The Stellar transaction hash.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_onchain_funds_receivedResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_onchain_funds_receivedExample",
-          "description": "Example request to the `notify_onchain_funds_received` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Onchain funds received"
-            },
-            {
-              "name": "stellar_transaction_id",
-              "value": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_onchain_funds_sent",
-      "summary": "Onchain funds sent",
-      "description": "Transaction flow is fully completed for SEP-6 or SEP-24 deposit",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "stellar_transaction_id",
-          "summary": "Transaction ID on Stellar",
-          "description": "The unique transaction identifier for this transfer on the Stellar network.",
-          "required": true,
-          "schema": {
-            "title": "hash",
-            "description": "The Stellar transaction hash.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_onchain_funds_sentResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_onchain_funds_sentExample",
-          "description": "Example request to the `notify_onchain_funds_sent` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Onchain funds sent"
-            },
-            {
-              "name": "stellar_transaction_id",
-              "value": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_refund_pending",
-      "summary": "Refund pending",
-      "description": "Refund has been submitted, but is not yet confirmed",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "refund",
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "amount_fee",
-              "id"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "Amount to be refunded",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "Amount of assets to refund",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of refund",
-                    "type": "string"
-                  }
-                }
-              },
-              "amount_fee": {
-                "title": "amount_fee",
-                "description": "Amount of fee",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "The amount of fee",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of fee charged by anchor",
-                    "type": "string"
-                  }
-                }
-              },
-              "id": {
-                "title": "id",
-                "description": "The Stellar transaction hash.",
-                "type": "string"
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_refund_pendingResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_refund_pendingExample",
-          "description": "Example request to the `notify_refund_pending` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Refund pending"
-            },
-            {
-              "name": "refund",
-              "value": {
-                "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
-                "amount": {
-                  "amount": 1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                },
-                "amount_fee": {
-                  "amount": 0.1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                }
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_refund_sent",
-      "summary": "Payment refunded",
-      "description": "Refund payment completed",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "refund",
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "amount_fee",
-              "id"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "Amount to be refunded",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "Amount of assets to refund",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of refund",
-                    "type": "string"
-                  }
-                }
-              },
-              "amount_fee": {
-                "title": "amount_fee",
-                "description": "Amount of fee",
-                "type": "object",
-                "required": [
-                  "amount",
-                  "asset"
-                ],
-                "properties": {
-                  "amount": {
-                    "title": "amount",
-                    "description": "The amount of fee",
-                    "type": "string"
-                  },
-                  "asset": {
-                    "title": "asset",
-                    "description": "The asset of fee charged by anchor",
-                    "type": "string"
-                  }
-                }
-              },
-              "id": {
-                "title": "id",
-                "description": "The Stellar transaction hash.",
-                "type": "string"
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_refund_sentResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_refund_sentExample",
-          "description": "Example request to the `notify_refund_sent` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Refund sent"
-            },
-            {
-              "name": "refund",
-              "value": {
-                "id": "ab295bf48920f2bab4aa7cfe31f488eed779d42e57a243aacdff2e6e96ec484e",
-                "amount": {
-                  "amount": 1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                },
-                "amount_fee": {
-                  "amount": 0.1,
-                  "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-                }
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_transaction_error",
-      "summary": "Transaction processing error",
-      "description": "There was an error processing transaction",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_transaction_errorResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_transaction_errorExample",
-          "description": "Example request to the `notify_transaction_error` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Transaction error"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_transaction_expired",
-      "summary": "Transaction has expired",
-      "description": "Funds were never received by the anchor and the transaction is considered abandoned by the user",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_transaction_expiredResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_transaction_expiredExample",
-          "description": "Example request to the `notify_transaction_expired` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Transaction expired"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_transaction_on_hold",
-      "summary": "Transaction transaction is on hold",
-      "description": "Notify transaction is currently on hold by the anchor (e.g. compliance hold). Anchor should update message to guide user through the steps.",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_transaction_on_holdResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_transaction_on_holdExample",
-          "description": "Example request to the `notify_transaction_on_hold` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Transaction on hold, please contact customer service to lift the hold."
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_transaction_recovery ",
-      "summary": "Transaction recovery",
-      "description": "Transaction status is changed from error / expired to pending_anchor(SEP-6 or SEP-24) or pending_receiver(SEP-31)",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_transaction_recoveryResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_transaction_recoveryExample",
-          "description": "Example request to the `notify_transaction_recovery` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Transaction recovered"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "notify_trust_set",
-      "summary": "Asset trustline set",
-      "description": "The user has added a trustline for the asset",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "success",
-          "description": "Flag which indicates if trustline was configured by user.",
-          "required": false,
-          "schema": {
-            "type": "boolean"
-          }
-        }
-      ],
-      "result": {
-        "name": "notify_trust_setResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "notify_trust_setExample",
-          "description": "Example request to the `notify_trust_set` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Trustline set"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "request_offchain_funds",
-      "summary": "Request offchain funds",
-      "description": "The user has to initiate transfer to the anchor",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "This is required if the transaction is associated with a firm quote and for transactions where `amount_in.asset` and `amount_out.asset` are the same.",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_expected",
-          "description": "The amount expected in the payment",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "instructions",
-          "description": "A set of SEP-9 fields that describe how the user can complete the offchain deposit",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "additionalProperties": {
-              "type": "object",
-              "properties": {
-                "name": {
-                  "type": "string",
-                  "description": "The SEP-9 field name"
-                },
-                "field": {
-                  "type": "object",
-                  "properties": {
-                    "value": {
-                      "type": "string",
-                      "description": "The value of the field"
-                    },
-                    "description": {
-                      "type": "string",
-                      "description": "A human readable description of the field"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      ],
-      "result": {
-        "name": "request_offchain_fundsResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "request_offchain_fundsExample",
-          "description": "Example request to the `request_offchain_funds` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Request offchain funds"
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 0.9,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "amount_expected",
-              "value": {
-                "amount": 1
-              }
-            },
-            {
-              "name": "instructions",
-              "value": {
-                "organization.bank_number": {
-                  "value": "123456789",
-                  "description": "US Bank routing number"
-                },
-                "organization.bank_account_number": {
-                  "value": "123456789",
-                  "description": "US Bank account number"
-                }
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "request_onchain_funds",
-      "summary": "Request onchain funds",
-      "description": "The user has to initiate transfer to the anchor",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        },
-        {
-          "name": "SEP-31"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "amount_in",
-          "description": "The amount expected in the payment",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be received by the Anchor",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "Amount sent by anchor to user",
-          "required": true,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_out",
-          "description": "This is required if the transaction is associated with a firm quote and for transactions where `amount_in.asset` and `amount_out.asset` are the same.",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount",
-              "asset"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              },
-              "asset": {
-                "title": "asset",
-                "description": "The asset to be sent by anchor to user at end of transaction",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "fee_details",
-          "description": "Description of fees charged by the anchor",
-          "required": true,
-          "schema": {
-            "title": "fee_details",
-            "description": "Description of fee charged by the anchor.",
-            "type": "object",
-            "required": [
-              "total",
-              "asset"
-            ],
-            "properties": {
-              "total": {
-                "type": "number"
-              },
-              "asset": {
-                "type": "string"
-              },
-              "details": {
-                "type": "array",
-                "description": "Details about fee charged.",
-                "items": {
-                  "properties": {
-                    "name": {
-                      "type": "string"
-                    },
-                    "description": {
-                      "type": "string"
-                    },
-                    "amount": {
-                      "type": "number"
-                    }
-                  }
-                }
-              }
-            }
-          }
-        },
-        {
-          "name": "amount_expected",
-          "description": "The amount expected in the payment",
-          "required": false,
-          "schema": {
-            "type": "object",
-            "required": [
-              "amount"
-            ],
-            "properties": {
-              "amount": {
-                "title": "amount",
-                "description": "A numerical representation of an amount of some asset.",
-                "type": "string"
-              }
-            }
-          }
-        },
-        {
-          "name": "destination_account",
-          "description": "Destination account",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        },
-        {
-          "name": "memo",
-          "description": "Value of memo to attach to transaction",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        },
-        {
-          "name": "memo_type",
-          "description": "Type of memo that anchor should attach to the transaction",
-          "required": false,
-          "schema": {
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "request_onchain_fundsResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "request_onchain_fundsExample",
-          "description": "Example request to the `request_onchain_funds` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Requesting onchain funds"
-            },
-            {
-              "name": "amount_in",
-              "value": {
-                "amount": 1,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "amount_out",
-              "value": {
-                "amount": 0.9,
-                "asset": "iso4217:USD"
-              }
-            },
-            {
-              "name": "fee_details",
-              "value": {
-                "total": 0.1,
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              }
-            },
-            {
-              "name": "amount_expected",
-              "value": {
-                "amount": 1
-              }
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    },
-    {
-      "name": "request_trust",
-      "summary": "A trustline to the asset isn't set",
-      "description": "The user must add a trustline for the asset to complete",
-      "paramStructure": "by-name",
-      "tags": [
-        {
-          "name": "SEP-6"
-        },
-        {
-          "name": "SEP-24"
-        }
-      ],
-      "params": [
-        {
-          "name": "transaction_id",
-          "summary": "ID of the transaction.",
-          "description": "The unique identifier of this transaction.",
-          "required": true,
-          "schema": {
-            "title": "transaction_id",
-            "description": "A unique transaction identifier.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "message",
-          "summary": "Human readable explanation.",
-          "description": "Human readable explanation of transaction status.",
-          "required": false,
-          "schema": {
-            "title": "message",
-            "description": "A human readable message.",
-            "type": "string"
-          }
-        },
-        {
-          "name": "user_action_required_by",
-          "description": "Time and date by which user action is required",
-          "required": false,
-          "schema": {
-            "title": "datetime",
-            "description": "A date and time.",
-            "type": "string"
-          }
-        }
-      ],
-      "result": {
-        "name": "request_trustResponse",
-        "schema": {
-          "name": "response",
-          "type": "object",
-          "properties": {
-            "id": {
-              "title": "transaction_id",
-              "description": "A unique transaction identifier.",
-              "type": "string"
-            },
-            "sep": {
-              "title": "sep",
-              "description": "Protocol of the transaction.",
-              "type": "integer",
-              "enum": [
-                6,
-                24,
-                31
-              ]
-            },
-            "kind": {
-              "title": "kind",
-              "description": "The kind of transaction that is desired.",
-              "type": "string",
-              "enum": [
-                "undefined",
-                "receive",
-                "deposit",
-                "deposit-exchange",
-                "withdrawal",
-                "withdrawal-exchange"
-              ]
-            },
-            "status": {
-              "title": "status",
-              "description": "Processing status of the transaction.",
-              "type": "string",
-              "enum": [
-                "pending_anchor",
-                "pending_trust",
-                "pending_user",
-                "pending_user_transfer_start",
-                "pending_user_transfer_complete",
-                "incomplete",
-                "no_market",
-                "too_small",
-                "too_large",
-                "pending_sender",
-                "pending_receiver",
-                "pending_transaction_info_update",
-                "pending_customer_info_update",
-                "completed",
-                "refunded",
-                "expired",
-                "error",
-                "pending_external",
-                "pending_stellar"
-              ]
-            },
-            "amount_expected": {
-              "type": "object",
-              "title": "amount_expected",
-              "description": "The amount expected in the payment.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_in": {
-              "type": "object",
-              "title": "amount_in",
-              "description": "Amount expected/received by anchor.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "amount_out": {
-              "type": "object",
-              "title": "amount_out",
-              "description": "The amount expected to be sent by anchor to user at end of transaction.",
-              "properties": {
-                "amount": {
-                  "title": "amount",
-                  "description": "A stringified amount of an asset.",
-                  "type": "string"
-                },
-                "asset": {
-                  "title": "asset",
-                  "description": "An asset.",
-                  "type": "string"
-                }
-              }
-            },
-            "fee_details": {
-              "title": "fee_details",
-              "description": "Description of fee charged by the anchor.",
-              "type": "object",
-              "required": [
-                "total",
-                "asset"
-              ],
-              "properties": {
-                "total": {
-                  "type": "number"
-                },
-                "asset": {
-                  "type": "string"
-                },
-                "details": {
-                  "type": "array",
-                  "description": "Details about fee charged.",
-                  "items": {
-                    "properties": {
-                      "name": {
-                        "type": "string"
-                      },
-                      "description": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "number"
-                      }
-                    }
-                  }
-                }
-              }
-            },
-            "quote_id": {
-              "title": "quote_id",
-              "description": "The id returned from a SEP-38 POST /quote response",
-              "type": "string"
-            },
-            "started_at": {
-              "title": "started_at",
-              "description": "Start date and time of transaction.",
-              "type": "string"
-            },
-            "updated_at": {
-              "title": "updated_at",
-              "description": "The date and time of transaction reaching the current status.",
-              "type": "string"
-            },
-            "completed_at": {
-              "title": "completed_at",
-              "description": "The date and time of transaction reaching completed or refunded status.",
-              "type": "string"
-            },
-            "transfer_received_at": {
-              "title": "transfer_received_at",
-              "description": "The date and time of receiving transfer.",
-              "type": "string"
-            },
-            "message": {
-              "title": "message",
-              "description": "Human readable explanation of transaction status",
-              "type": "string"
-            },
-            "refunds": {
-              "title": "refunds",
-              "description": "An object describing any on or offchain refund associated with this transaction.",
-              "type": "object",
-              "properties": {
-                "amount_refunded": {
-                  "type": "object",
-                  "description": "The total amount refunded in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "amount_fee": {
-                  "type": "object",
-                  "description": "The total amount charged in fees for processing all refund payments, in units of amount_in_asset.",
-                  "properties": {
-                    "amount": {
-                      "title": "amount",
-                      "description": "A numerical representation of an amount of some asset.",
-                      "type": "string"
-                    },
-                    "asset": {
-                      "title": "asset",
-                      "description": "An asset.",
-                      "type": "string"
-                    }
-                  }
-                },
-                "payments": {
-                  "type": "array",
-                  "description": "A list of objects containing information on the individual payments made back as refunds.",
-                  "items": {
-                    "properties": {
-                      "id": {
-                        "title": "id",
-                        "description": "The Stellar transaction hash.",
-                        "type": "string"
-                      },
-                      "id_type": {
-                        "type": "string"
-                      },
-                      "amount": {
-                        "type": "object",
-                        "description": "The amount sent back for the payment identified by id, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "fee": {
-                        "type": "object",
-                        "description": "The amount charged as a fee for processing the refund, in units of amount_in_asset.",
-                        "properties": {
-                          "amount": {
-                            "title": "amount",
-                            "description": "A numerical representation of an amount of some asset.",
-                            "type": "string"
-                          },
-                          "asset": {
-                            "title": "asset",
-                            "description": "An asset.",
-                            "type": "string"
-                          }
-                        }
-                      },
-                      "requested_at": {
-                        "title": "datetime",
-                        "description": "The date and time of requesting refund.",
-                        "type": "string"
-                      },
-                      "refunded_at": {
-                        "title": "datetime",
-                        "description": "The date and time of making refund.",
-                        "type": "string"
-                      }
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "examples": [
-        {
-          "name": "request_trustExample",
-          "description": "Example request to the `request_trust` method.",
-          "params": [
-            {
-              "name": "transaction_id",
-              "value": "1c186184-09ee-486c-82a7-aa7a0ab1119d"
-            },
-            {
-              "name": "message",
-              "value": "Request trust"
-            }
-          ],
-          "result": {
-            "name": "AnchorPlatformResponse",
-            "value": {
-              "id": "1c186184-09ee-486c-82a7-aa7a0ab1119d",
-              "sep": "24",
-              "kind": "deposit",
-              "status": "completed",
-              "amount_expected": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_in": {
-                "amount": "1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "amount_out": {
-                "amount": "0.9",
-                "asset": "iso4217:USD"
-              },
-              "fee_details": {
-                "total": "0.1",
-                "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-              },
-              "started_at": "2023-08-04T10:04:06.280923Z",
-              "updated_at": "2023-08-04T10:04:15.716233Z",
-              "message": "Transaction complete",
-              "source_account": "GB4GJAV4Q7DPGU7WI3H5TMVKEYZJ4JFLFEF3O3TRJKDPXK7NAMRBXWFL",
-              "destination_account": "GDIN5ZULIOT5YPBIXJXFGNH4TCNTDKIA4ZF6QQE3S2P5P44BHCQQJNDC"
-            }
-          }
-        }
-      ]
-    }
-  ],
-  "components": {}
-}
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/README.mdx
deleted file mode 100644
index f258e7c7dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/README.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Métodos JSON-RPC
-order: 20
-sidebar_label: Métodos
----
-
-Esta sección enumera los métodos de la API JSON-RPC de Anchor Platform que deben ser invocados por los clientes Stellar para actualizar el estado de la transacción.
-
-La especificación OpenRPC para la API JSON-RPC está disponible [aquí](https://playground.open-rpc.org/?schemaUrl=https://raw.githubusercontent.com/stellar/stellar-docs/main/static/assets/rpc-methods/open-rpc.json).
-
-La colección de Postman está disponible [aquí](https://documenter.getpostman.com/view/9257637/2s9Y5U1kra)
-
-<EndpointsTable title="Métodos JSON-RPC">
-
-|   |                                                                              |
-| - | ---------------------------------------------------------------------------- |
-|   | [do_stellar_payment](./do_stellar_payment.mdx)                               |
-|   | [do_stellar_refund](./do_stellar_refund.mdx)                                 |
-|   | [get_transaction](./get_transaction.mdx)                                     |
-|   | [get_transactions](./get_transactions.mdx)                                   |
-|   | [notify_amounts_updated](./notify_amounts_updated.mdx)                       |
-|   | [notify_customer_info_updated](./notify_customer_info_updated.mdx)           |
-|   | [notify_interactive_flow_completed](./notify_interactive_flow_completed.mdx) |
-|   | [notify_offchain_funds_available](./notify_offchain_funds_available.mdx)     |
-|   | [notify_offchain_funds_pending](./notify_offchain_funds_pending.mdx)         |
-|   | [notify_offchain_funds_received](./notify_offchain_funds_received.mdx)       |
-|   | [notify_offchain_funds_sent](./notify_offchain_funds_sent.mdx)               |
-|   | [notify_onchain_funds_received](./notify_onchain_funds_received.mdx)         |
-|   | [notify_onchain_funds_sent](./notify_onchain_funds_sent.mdx)                 |
-|   | [notify_refund_pending](./notify_refund_pending.mdx)                         |
-|   | [notify_refund_sent](./notify_refund_sent.mdx)                               |
-|   | [notify_transaction_error](./notify_transaction_error.mdx)                   |
-|   | [notify_transaction_expired](./notify_transaction_expired.mdx)               |
-|   | [notify_transaction_on_hold](./notify_transaction_on_hold.mdx)               |
-|   | [notify_transaction_recovery](./notify_transaction_recovery.mdx)             |
-|   | [notify_trust_set](./notify_trust_set.mdx)                                   |
-|   | [request_offchain_funds](./request_offchain_funds.mdx)                       |
-|   | [request_onchain_funds](./request_onchain_funds.mdx)                         |
-|   | [request_trust](./request_trust.mdx)                                         |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.mdx
deleted file mode 100644
index 8f21a26488..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_payment.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: hacer_pago_stellar
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "do_stellar_payment")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.mdx
deleted file mode 100644
index 26776c91ae..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/do_stellar_refund.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: realizar_reembolso_stellar
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "do_stellar_refund")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.mdx
deleted file mode 100644
index 0aec020e3a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transaction.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: obtener_transacción
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "get_transaction")[0]}
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.mdx
deleted file mode 100644
index 034885b06c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/get_transactions.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: obtener_transacciones
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "get_transactions")[0]}
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
deleted file mode 100644
index 2f27b337cb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_amounts_updated.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: notificar_cantidades_actualizadas
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notify_amounts_updated")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
deleted file mode 100644
index c40f4ab289..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_customer_info_updated.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_actualizacion_info_cliente
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_customer_info_updated",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
deleted file mode 100644
index dda1c16e16..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_interactive_flow_completed.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_flujo_interactivo_completado
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_interactive_flow_completed",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
deleted file mode 100644
index 8e5b7b6874..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_available.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_fuera_de_cadena_disponibles
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_offchain_funds_available",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
deleted file mode 100644
index 43d2d4ce16..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_pending.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_fuera_de_cadena_pendientes
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_offchain_funds_pending",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
deleted file mode 100644
index cc31c386d1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_received.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_fuera_de_cadena_recibidos
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_offchain_funds_received",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
deleted file mode 100644
index 9004d11ddd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_offchain_funds_sent.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_offchain_enviados
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_offchain_funds_sent",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
deleted file mode 100644
index 531631dedc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_received.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_recibo_de_fondos_onchain
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_onchain_funds_received",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
deleted file mode 100644
index 69e0519e77..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_onchain_funds_sent.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_fondos_onchain_enviados
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_onchain_funds_sent",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.mdx
deleted file mode 100644
index a69e5a372a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_pending.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: notificar_reembolso_pendiente
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notify_refund_pending")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.mdx
deleted file mode 100644
index 12f34da809..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_refund_sent.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: notificar_reembolso_enviado
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "notify_refund_sent")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.mdx
deleted file mode 100644
index 7986f4ec9a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_error.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_error_transacción
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_transaction_error",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
deleted file mode 100644
index 9935b83f63..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_expired.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_transacción_expirada
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_transaction_expired",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
deleted file mode 100644
index aac4eeda31..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_on_hold.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_transacción_en_espera
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_transaction_on_hold",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
deleted file mode 100644
index 12bbbf6cd6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_transaction_recovery.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: notificar_recuperación_de_transacción
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter(
-      (meth) => meth.name === "notify_transaction_recovery",
-    )[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.mdx
deleted file mode 100644
index 63b7b65613..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/notify_trust_set.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: notificar_establecimiento_de_confianza
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "notify_trust_set")[0]}
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.mdx
deleted file mode 100644
index db5fac4514..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_offchain_funds.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: solicitar_fondos_offchain
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "solicitar_fondos_offchain")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.mdx
deleted file mode 100644
index d395ed2a65..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_onchain_funds.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: solicitar_fondos_cadena
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={
-    rpcSpec.methods.filter((meth) => meth.name === "request_onchain_funds")[0]
-  }
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.mdx
deleted file mode 100644
index 62a368d0ae..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/methods/request_trust.mdx
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: request_trust
-hide_title: true
----
-
-import { RpcMethod } from "@site/src/components/RpcMethod";
-import rpcSpec from "../anchor-platform.openrpc.json";
-
-<RpcMethod
-  method={rpcSpec.methods.filter((meth) => meth.name === "request_trust")[0]}
-/>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
deleted file mode 100644
index 38cac14017..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/rpc/overview.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Resumen
-sidebar_position: 10
----
-
-JSON-RPC es un protocolo de llamada a procedimiento remoto (RPC) sin estado y liviano.
-
-Es simple y fácil de usar, ya que utiliza un único punto de conexión HTTP y un objeto JSON que contiene el nombre del método y los parámetros. Es independiente del transporte, dado que los conceptos pueden usarse dentro del mismo proceso, a través de sockets, por HTTP o en varios otros entornos de paso de mensajes. Usa [JSON](http://www.json.org/) ([RFC 4627](http://www.ietf.org/rfc/rfc4627.txt)) como formato de datos.
-
-:::note
-
-Todos los nombres de miembros intercambiados entre el Cliente y el Servidor que se consideren para cualquier tipo de coincidencia deben ser sensibles a mayúsculas y minúsculas.
-
-:::
-
-Puedes leer más sobre el protocolo JSON-RPC [aquí](https://www.jsonrpc.org/specification).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/README.mdx
deleted file mode 100644
index ecfba437f5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/README.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Transacciones
-sidebar_position: 10
----
-
-Las transacciones son representaciones de una transacción SEP. Contiene información sobre el protocolo que se está utilizando y toda la información necesaria que pasa una parte externa (como una billetera o un anchor).
-
-No debe confundirse con las [transacciones](../../../../../learn/glossary.mdx#transaction) de Stellar.
-
-<EndpointsTable title="Puntos finales">
-
-|     |                                              |
-| --- | -------------------------------------------- |
-| GET | [/transactions/:id](get-transaction.api.mdx) |
-| GET | [/transactions/](./get-transactions.api.mdx) |
-
-</EndpointsTable>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.api.mdx
deleted file mode 100644
index 6254bd3bff..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/get-transaction.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: get-transaction
-title: "Retrieve a Transaction"
-description: "Provides the information necessary for the business to determine the state of the transaction identified by `id`, decide if any action must be taken to continue processing the transaction, and act on the decision."
-sidebar_label: "Retrieve a Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXN1P67gS/1csv+yuFFLgoPPQN/Yuu6q0HwjOfeKgHjeeNF4SO8d2KBXq/341ttOmbQotQqLnyi+Qxh8zHs+HZ36tn6llU0OHd/SLZtKwzAolDb1P6NOJgdq13F5dn3ymift/fhEePp1hJ1WDZjhkxOmQTsF2ZqEJ5WAyLWr3aUivtXoUHAyxBRAhc6UrN5ZIyMAYpuckV9q1ThojJBhDrCIcLOhKSHAtxjILROXug11RI4KDtCIXwMlkTr4J/i0hHDLBgYicMDknoWPVGEsmQCx7AIkEMiWtkA2QWitkRMjp5uwJYZLjBERJ14YzG6FkShNaM80qZBKl9UwFrrVmtqAJlawCOqSC04Rq+N4IDZwOrW4goSYroGJ0+EztvMZexmohp3SxuMfOplbSgMH289NT/LcuzY6kSa4ayZEVXApIi71ZXZcicwIe/GtwyHOHpJLwT+7YDcTV5F/I7Bqbd55vAzVN6IOQ7oNltjH+QVvgY2ZRD2qNmmCF51fwnlX5ibbeJxRkUyGxz/R+Eei80ItDrYywTrnc0wk8ZQWTU6AJnQlbcM1mrFz7sOqCFMISemhsqKsyRkxKr3KNIY+sbMBpqDOIrnqYDoNCZqqqS7Dg9sM/+v3PG8ndIzzVTsQJBa2VRh0CyYWcjo2FsmTdN/BkQUu3ovZV1hirKtBjNKJxU3PmiLXNjQE9dtzloMduo3a2dnhtOzCZFWs8Wd2YzRlQt9W4YvoBsMkqNTYVK8vwXDKN0k6oFbZEGd86Gd5eXX9GTfCCf20DvhRAKrCF4s7kkCz+4d4puM0nSpN2n4nK86xgQhKUs0mREKtUI+0YnmrIcBeGL+u7704TyoyBHsUO7X3K7Uf0GPNKBpd+9IotIY+MIdXYY+EoBxhzsEyU5jWWrLLOPHZw5JsPYQgVcZMy05rNaUKFhepVjpzbb6W6zZGPCn0M7Rbemmm8JMLfAX7r9F1stfmVLRL6vVEWxruc9cq/9xiqj910SNH1nFhRAY7xnuiwMUsPedCopf/SkIF4PJRPdIHec4/bbRtP5vtPUOFxZdq/h97N96pIn6WMl2HhSAwvsJUDHAtHNZtXIO1B1rjXgUTw8a5I1EbzVTxexuH7PkP9aF95LKwgTTCHmnNrAwcMWqw5tptgdM5xuR0brx3P3ujH3fk309B6NdSLRyhV7c5LrVrudf7tO9yMfutNZHyGcevXQSTYmdIPqfc7ldr33FSpN0y+0x52UMBuB5Aht4VqSo7ZV63BgLSYm7mZhCFSWSKbskw79mfhCcVeMIPplODO+jo7sp+29PGPDVt8z5ghGqbCWNDAX5LWUhH2ElaXRjsycYknExLzTVaWPUJcpsjpW/3gljaHSfxGJ9SoRmcwZlkW/AMHY4V0RDtvd51kDtf0QH9TtH93RLvG4n7iDWr42uQrvQo9nUBsMW4/3uPsOWtK63J4/3KxJaa9mAqdyQRwgzlMhN1Wqe66+0T/BkqZBv4aqWOKX+uePHDbrSMt9tiAfcW3WAXyboTYdQrud7jH7CyJ4MR5y07y/RdU6gvyuAy14/0iySjHmhgW7XhCbCGMJ2+WjLl0HEsiftq1mki6Qe6HFFdWCnRFXFVM9CVeyx47c7q2WNPrnreX7qoctmDoxIQVGOe2JWDIRNnC10NBctCuPBlyIZ1+lVsnYN/tdRaCVEf8J0OYBuK7mcCRL7HOCUh+gowaR9eXg8mtLw+RS1c/MgmZNNbJPbTfOPY6PdKv8qv8XWnCXJezc9LKKnFLwxouyQWUvKNxpslzkaHIsQyUN2U5X/GFo9o5Wj1pS8k/kV9Z9gCSb5Dd4jwQDy7km1viN9SjwIzZ0P+N+T6TUCE8v3j7hHtlMH3q42QWjGYpic6JxhZaNdMiCNzHgn1DzZWwBeg142sjj9Lkr+YJ+PIF41xj/T6wouSJL83hRtn5Ww6zvvzabrU7M61WiDVAwogpmF4xkZBZATrABmstaEHL/UhpT/wZce+9vEVFu4l2E+1mX7tZtCmaioYTDScazv6Gs3rbyX8CaPZmpHYTA9uV478/ont+cSCk28Fv3w+pPb/4QKj2qLHY84tDwFhhgm8UhrByxuaGQFXb+S5BRwA2ArARgI0AbARgIwAbAdgIwEYANgKwEYCNAGwEYI8sfkUA9gMB2HcFXJNtOUUANgKwsR4e6+E/Yj08ArDRbqLdRAA2Gk40nI8FYB1S9mYE9v2RVfz19R7Iagif7wimfjr7QDA1nKFXL5bHgy5A2skpe38e2/vr2T549NPZu8KjG6KL8GiERyM8GuHRCI9GeDTCoxEejfBohEcjPBrh0QiPHln8ivDo0cCjIsKjHw2PjsI1e/5mORcDWiGYUFRdQaHO3Nv5UzJy/eZkhjW6ECSX9ck7X6C8/7mwtjbDwSAclFKlp4NaK6syVQ4M1Cdn578kX6Xbfs9oqwAhXnnxr9eXXZk0Jf9gPXMmDGxVaNerl+2wiOTGwnosrEckN9pNtJuI5EbDiYbzoxjOLiQXQb17n9Jd9F2r/Cvj5MYXCQ+5T/nl+q5HO/tLvP1JaDfN9aM7CcCVe9Eu4mJ7Ed27odGKD78f+oPWE9JfaXxV9O6ZPsCcDtvLyBPqNOnFS8nx9mx/a7C/kTyUUOiQDrrZ4OBZ8IVD7PVje3N3o0s6pG3+UZfMYoHrxHdJ4YkhFOR/kptmqqJIChMgXDJO4oX/KT1NT+lqdddhHnLr5um1kpYW8bQchozJla8EEAShlARpUzKyHY9TKBMKKYzUWjzi1egh33SeKvREFZi4MgwEbD/XqnK2NXIkwKbEIdiBPEg2KcNF7d2r2HOwWeFm9lCaN8/ljewd8ZLGXaMurCGX1yPvFUuRgTSwQhjpZc2yAsi5k9dK+sPBYDabpcy1uvwvDDWDP0f/ufr79urkPD1NC1uVTrlqZWzFZGfiG7BawCMQRl64kf55ZQ//t5fTB1PEWgJqtJAOYNQOcPZ2cUc3vtExxDJ2QlG5sPX5ecIM/FeXiwW+/t6AntPh3T0aoxaoKM54uDD4zOkwZ6WBF0T9801wBr+QXQy25WM5X9k8xW/WOG8gOPrwhBbAXCa+dBOXWQa17QzZcnJr3uGPqy90sfgfaB/iSg==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/anchor-platform/api-reference/platform/transactions/platform-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Provides the information necessary for the business to determine the state of the transaction identified by `id`, decide if any action must be taken to continue processing the transaction, and act on the decision.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"path","name":"id","required":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Transaction found.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["6"]},"kind":{"type":"string","enum":["deposit","deposit-exchange","withdrawal","withdrawal-exchange"]},"status":{"type":"string","description":"Possible status value for SEP-6 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_customer_info_update","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP6"},"type":{"type":"string","description":"The method the user used to deposit or withdraw offchain funds."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"type":"string","description":"If provided, this memo should be used for refund transactions."},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP6"},{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"},{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}]}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Transaction not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.api.mdx
deleted file mode 100644
index 105df4d8c2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/api-reference/platform/transactions/get-transactions.api.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-id: get-transactions
-title: "Retrieve a List of Transactions"
-description: "Allows to query list of transactions for desired SEP. This api supports pagination, and it's possible (and recommended) to make multiple requests to query transactions. The last page is reached when the number of elements returned by the endpoint is smaller than provided `page_size`."
-sidebar_label: "Retrieve a List of Transactions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztXVtv47YS/isEX7oLKEo2G/TBb+lpehAg3Qab7dNu4NDS2GIjkSpJ5dLA//1ghpQt2bJjp4smPeDLxqZIznCu5Hxe8Yk7MbN89JV/MUJZkTmpleXXCX84sFDTk6uzy4MfeUJ/j0/Ch48fsJOuwQgccp7zEZ+B682S8BxsZmSNX/mIn5alvrfMafZnA+aRldI6pqfMdQaxqTYsBysN5Ozq7DJlXwppmagls01da+Msq8VMKiKbMKFyJt0PltXaWjkpgb3DJgOZripQOeTvkWAlboFVTelkXQIz8GcD1nVY6bKAJIGVwjqkBExaZkBkBeTsvgDFXAFMNdUEDDIPJVSgHPZxjVGQs8kjdQGV11oqh+NtJcoSDHOFUKw2+k7mkLMbnH5s5V9wk/KE18KIChwYlPoTlygy4o4nXIkK+IhbqHnCkX2UDx8500DCbVZAJfjoibvHmro5I9WMJxxUU6EKUX2kOlTbfFUvF1rfNnVfDRMotZpJNUMZOVQBKoPPk2HGtMnBjCfY8jw3mQHhIB8LxxNOVKdgxgYykHdtc2PBjD0z43a9OP81Mj8VTen4qDvR2qKuasjkVIJlUwlljqJ3/SXey7JkE2DEO+ktZZ+0g8T3tZBplQvzyKw2pMXOaCZzJhUTNgOVo5TuRNlA+k2dp5AGM5EVWCeq2tv0MdOGVdpAnwlpmcxBOZmJEgnD44IvJOvNSebPSH4nsQubBZfsSxHbt4iPCPQks/ACL1lpmWrKMmGiLFcl7Ap65sWzWBn6VsIMzITJS7AW/chqZNdTY+8+/X5xccUuTq++vE+/qV+0YfAgqrpEFoLBkIBZJR6Z0o7kFVjOSd5WV31RI0GLEUDNmFROs5sh07thE8AeyHXKzpGvZGhRWh0sF2ZXdeZDUIgHU2lwuVON4c8rdIuklmazWefWCddYsENqF8YI7CodVHbIHPp6vmzDpp+zXQ9KcJXJjilJlWnUhgOe8PZjTqFp2mDQxb4PNQWphIMxGk209r4ytg7KUnRb4MGBUaLsNFEAWGjIOmHcxqcdZtoOQmVFj6gzjV2dASWqx5Uwt0ChSOsxRerwuRRm1p3TYj7pzhnspk9mIbCxVFM9bupc9DjLGut0Bab3+DrhTroSFXVFirg6uzwtSz5fc8xfZIkpYj1pLs2fTIB8KtgJGTJ6SZt6EjalacgXLMulFZMScvYuRAU2gULcSW3eb7TBRe4aMkKpHMxILoswc3y0HmPkX4BsCmalmqENgjBZQVk3Zb82lty61lY6eQeb3YFY8Rl5R2bWebnETB+yutOssUBCzbRyUjW6sYG5lFHPTDfK+VBhmXDsKOXzazR/W2uFnjl64sdHR/inT6ezQWJT3ag8JQ9SDpTD3qKuS5nR5ubwD4tDnjor0gp+m9LuIKxNT/6AjMza4F7MSU8atz8mtzuEhcUEy03FVy7Ra/1e41Yq+kKW5D+YkHKvV6nKfD3ezP1EW/cmuCMhOlt65UB2QEqkTwfwkBVCkYNi9MyNuKcAsvyy7IIUwhJeFhHJGGgj/IohcTByvMGIORTMfkRL8IJ/TgG4+67AFTqnTQaSxX9y9MugfNxLtXpmejrNCiEVQzlT1uSiQv8cw0MNGWrhGXv33XnChbUwYNjh+ZBx+xHrT+ZLGZz60Uu2pHpjDOnGvRWOpgDjHJyQ5bNRymlH7rGBI/94H4bQEFcp7xU3KR+1Ul3nyKerIYY2C6/nGttE+AvAz52+87VnfmXzhP/ZaAfjTcF6Gd8HHHWqTYVPOIaeA9yq4hgfifYbs4iQe40aPCzuzueGM+XOE1RgrZgN69CH+UETGfKU8SItvBHHC2xNAd4KR7V4pMrKPt6404ZE5uNNmajN5st8vMjD10OO+tqx8q2wEipqezpk6wN7DJr3Atvn4HQUuEhj49727O/sf3tVKlB3UOqa9kutWe60/x3a3Jz/TFXPAvoVJV9TufLrYArcvTa3qY87ld5131TpF0y+0R82UMBue5BhV4VuypxOcwYsYFF06mfC4pF2vtzS8T8HDyj2QtgClZaT93U0spu1DPFPVaNVvu8F1m9n0jqqBG6R1sIQdhJWl0Y7MqFDpZAKD99UY1kTol+K1Cp9aRxcs+YwiVd0wq1uTAZjkWUhPuRgXSiqd1o37WT2t/RAf1W0nzqi7bG4m3iDGT43+dKuQk8SiCvG7ddePbRtnK+JaSemQudQR8xhIt26SXXXPST6F1DKDOTPkXpL+asfyQO3nfIIDXpOAbuKb75M5P0S3fAOYTjgvuVgiYAERcvO4ftXqPQX5HGRase7ZZLzaadSSOAPkbcLxug4jiURP20fPlsh968UV1ZKDEW5roQcOngtemw807XFmsHwvL50qnIQuiKVdBLz3LoELJtoV1C7r0UHoMFXodNvam0HHErWz7IQpHqe/2CZMMB8Nxs4IoBq+oiQ5gEyaomuh4HZVUDATql+ZBM2aRzJPTz/TOx1eqTflId0BHX5cMxaWREAxm5kfhOgpaXF2WY6lRmKHMtA06YsH5d84ah2jtZOJo2VCqz9gf0ksltQ+QrZNc4D8RBCbmiJN2hHgRm7Yv8r8/3IQoXw+OTlE+50ghkyH5JZcJqFJDo7GlcY3cyKIHCfC3ZNNWfSFWScS+drM4827NfmASGH0CDy3ARAD/trdeBLc6go9/iSzawvv7aqpj3TcoUEmwlmC2GWTCQIUBq/yes/QQ9a6CPlA/nnPPfRK+A60W+i30S/2dFv5u0RTUfHiY4THWd3x1m2ds4/HjTb8PBCWhdQtdfDgldRtk1VhO+PGR+f7AkadxDi74cFH5/E38cMo73HJ/vAvdIuf0kmynvxaBlUtXvcJOgI8UaIN0K8EeKNEG+EeCPEGyHeCPFGiDdCvBHijRDvG8tfEeJ9RYj3u0K6ybqcIsQbId5YcY8V939jxT1CvNFvot9EiDc6TnSc14V4ESnbjvESlvZ6IO/3B2/DO0ieA29Dhv6OeO3HD6+I1/7DLw/4+OG7IrAroosIbERgIwIbEdiIwEYENiKwEYGNCGxEYCMCGxHYiMC+sfwVEdg3g8DKiMC+NgJ77it+4f16lANaIdhQt12ireTu7fz0BkX/dlYsA4YkuSiBfvU10Ot3hXO1HR0eho1Sqs3ssDba6UyXhxbqgw/H75NvitTvGW0NIOQrL/5+CZsqsSn7DUum99LCWhG4XyBth0WwONbuY+0+gsXRb6LfRLA4Ok50nH+L42wCixHU2w4WY49rf+g7GXr99E8iZ599GXGf905vrwB7PHS4CDx8TO0ehP3ozhHhjBraRZysL6L7Dm308/3fo/1K6wkHZGV93fTrE7+FRz5q71pJONna1jtX8C3j/uXI/sKVUGThI364gm1bMHftXSKNKfmIt4eTuhQOq18Hvksarlbw/yU4zXRF7zLH0xGuFifxcv+YHqVHfLmwyzAPu6J5Bl2opcU8LQKY8eTlywQMESqtQLmUnbtOOCq0DVUWwWoj74SD9jBKYSz0DDc/iCyDAPxPja7I8c6JBLhwgUwgDwpfdG97AZriObisoJk9zuZ91+Gn1QtqcNSMSWfZ6eW5D5mlzEBZWMKP/LTGC2PYMclrKf3R4eH9/X0q6CkdDsNQe3hx/p+zT1dnB8fpUVq4yr/6v9bWVUJ1Jv4Mzki4AybYRbg+Z9udO09Ln4jX72y/fid4NRYu0EOkIjTTELrtXewr77nYdcLRTLH96WkiLPxuyvkcm/39BOh47c0KfDQVpYUt2nn3OcSQ92yP+3g2sO3Div9BT4gpnH5FtDs//2/352yVVOf6or8trnhfzqvdl/O8jl+u4H/63pXtnr28AOil9rrn3Stb2eneBfNCfv7+/SvPc7i4ImbJ4zV+MRKZ5KOviH8WIKhCuticnWYZ1K4zam1r2duT/ffsC5/P/weQ8/fV
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/anchor-platform/api-reference/platform/transactions/platform-server
-custom_edit_url: null
-hide_send_button: true
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={'SEP-6,SEP-24,SEP-31'} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a List of Transactions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/transactions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows to query list of transactions for desired SEP. This api supports pagination, and it's possible (and recommended) to make multiple requests to query transactions. The last page is reached when the number of elements returned by the endpoint is smaller than provided `page_size`.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"in":"query","name":"sep","required":true,"schema":{"type":"string","enum":["6","24","31"]},"description":"Lookup transactions belonging to this SEP."},{"in":"query","name":"order_by","schema":{"type":"string","enum":["created_at","transfer_received_at","user_action_required_by"],"default":"created_at"},"description":"Specifies field that transactions will be ordered by. Note, that secondary sort is transaction id in ascending value.\nI.e. when timestamps for 2 or more transactions is identical, they will be sorted by id."},{"in":"query","name":"order","schema":{"type":"string","enum":["asc","desc"],"default":"asc"},"description":"Specifies order. Note, that when the field is null, all transactions with null value will be last, regardless of soring order (NULLS LAST).\nFor example, transfer time may not be specified for some transactions, resulting into `transfer_received_at` being null. If so, transactions with non-null values will be sorted and returned first, followed by all transactions with null timestamps."},{"in":"query","name":"statuses","schema":{"type":"array","items":{"type":"string","description":"Possible status values for all transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEPAll"}},"description":"Filters transactions for specified array of statuses. If not provided, filtering is disabled (default behavior)"},{"in":"query","name":"page_size","schema":{"type":"integer","default":20},"description":"Size of a single search page. Must be positive."},{"in":"query","name":"page_number","schema":{"type":"integer","default":0},"description":"Page number to use for continuous search. Page count beings at 0."}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Transaction found.","content":{"application/json":{"schema":{"oneOf":[{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["6"]},"kind":{"type":"string","enum":["deposit","deposit-exchange","withdrawal","withdrawal-exchange"]},"status":{"type":"string","description":"Possible status value for SEP-6 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_customer_info_update","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP6"},"type":{"type":"string","description":"The method the user used to deposit or withdraw offchain funds."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"type":"string","description":"If provided, this memo should be used for refund transactions."},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP6"}}},"title":"TransactionListSEP6"},{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","amount_expected","destination_account","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["24"]},"kind":{"type":"string","enum":["deposit","withdrawal"]},"status":{"type":"string","description":"Possible status value for SEP-24 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_user_transfer_start","pending_user_transfer_complete","pending_anchor","pending_trust","pending_user","no_market","too_small","too_large"],"title":"StatusSEP24"},"type":{"type":"string","description":"This field is always empty for SEP-24 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"If provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The user that initiated the transaction is both the sender and receiver.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP24"}}},"title":"TransactionListSEP24"},{"type":"object","properties":{"records":{"type":"array","items":{"type":"object","required":["id","sep","kind","status","started_at"],"properties":{"id":{"type":"string"},"sep":{"type":"string","enum":["31"]},"kind":{"type":"string","enum":["receive"]},"status":{"type":"string","description":"Possible status value for SEP-31 transactions","enum":["incomplete","completed","refunded","expired","error","pending_stellar","pending_external","pending_sender","pending_receiver","pending_transaction_info_update","pending_customer_info_update"],"title":"StatusSEP31"},"type":{"type":"string","description":"This field is always empty for SEP-31 transactions."},"amount_expected":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_in":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_out":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee_details":{"type":"object","required":["total","asset"],"properties":{"total":{"type":"string"},"asset":{"type":"string"},"details":{"type":"array","items":{"type":"object","required":["name","amount"],"properties":{"name":{"type":"string"},"amount":{"type":"string"},"description":{"type":"string"}},"title":"FeeDescription"}}},"title":"FeeDetails"},"quote_id":{"type":"string"},"started_at":{"type":"string","format":"date-time"},"updated_at":{"type":"string","format":"date-time"},"completed_at":{"type":"string","format":"date-time"},"transfer_received_at":{"type":"string","format":"date-time"},"user_action_required_by":{"type":"string","format":"date-time"},"message":{"type":"string"},"refunds":{"type":"object","properties":{"amount_refunded":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"amount_fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"payments":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string"},"id_type":{"type":"string","enum":["stellar","external"]},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"fee":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"},"requested_at":{"type":"string","format":"date-time"},"refunded_at":{"type":"string","format":"date-time"}}}}},"title":"Refunds"},"stellar_transactions":{"type":"array","items":{"type":"object","required":["id","created_at","envelope","payments"],"properties":{"id":{"type":"string","description":"The ID of the transaction in the Stellar network."},"memo":{"type":"string","description":"The memo of the transaction in the Stellar network."},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text","hash","id"]},"created_at":{"type":"string","format":"date-time","description":"The time the transaction was registered in the Stellar network."},"envelope":{"type":"string","description":"The transaction envelope, containing all the transaction information."},"payments":{"type":"array","items":{"type":"object","required":["id","payment_type","source_account","destination_account","amount"],"properties":{"id":{"type":"string","description":"The ID of the payment in the Stellar Network."},"payment_type":{"type":"string","description":"The type of payment in the Stellar Network.","enum":["payment","path_payment"],"default":"payment"},"source_account":{"type":"string","description":"The account being debited in the Stellar Network."},"destination_account":{"type":"string","description":"The account being credited in the Stellar Network."},"amount":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string"},"asset":{"type":"string"}},"title":"Amount"}}}}},"title":"StellarTransaction"}},"source_account":{"type":"string"},"destination_account":{"type":"string"},"external_transaction_id":{"type":"string"},"memo":{"type":"string"},"memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"refund_memo":{"description":"if provided, this memo should be used for refund transactions.","type":"string"},"refund_memo_type":{"type":"string","description":"The memo type of the transaction in the Stellar network. Should be present if memo is not null.","enum":["text id hash"],"title":"MemoType"},"client_domain":{"type":"string"},"client_name":{"type":"string"},"customers":{"type":"object","description":"The Identification info of the sending and receiving customers. If they were created through [SEP-12](https://stellar.org/protocol/sep-12),\nthis object should contain the SEP-12 customer `id`. Otherwise, the `account` address of the customer.\n","properties":{"sender":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"},"receiver":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}}},"creator":{"type":"object","description":"StellarId's are objects that identify end-users and SEP-31 Sending Anchors, but not SEP-31 Receiving Anchors.\n\nFor a SEP-12 customer, the `id` field should be sufficient to fully identify the customer in the business' Backend.\n\nFor a SEP-31 Sending Anchor, the `account` and `memo` fields should be used.\n\nFor a SEP-6 or SEP-24 Anchor, the `account` and `memo` fields should be used.\n","properties":{"id":{"type":"string","description":"The `id` of the customer registered through SEP-12."},"account":{"type":"string","description":"Either the Stellar account or Muxed account address of the on-chain entity."},"memo":{"type":"string","description":"The memo value identifying a customer with a shared account, where the shared account is `account`."}},"title":"StellarId"}},"title":"TransactionSEP31"}}},"title":"TransactionListSEP31"}]}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}},"404":{"description":"Transaction not found.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"id":{"type":"string"}},"required":["error"],"title":"Error"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/README.mdx
deleted file mode 100644
index ef7e1e7efd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Guías SEP
-sidebar_position: 30
----
-
-import DocCardList from "@theme/DocCardList";
-
-Guías para implementar Propuestas del Ecosistema Stellar (SEP) con Anchor Platform.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/_category_.json
deleted file mode 100644
index aa65b42d31..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/_category_.json
+++ /dev/null
@@ -1,5 +0,0 @@
-{
-  "label": "SEP Guides",
-  "collapsed": false
-}
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep1/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep1/README.mdx
deleted file mode 100644
index 82c6a6b371..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep1/README.mdx
+++ /dev/null
@@ -1,198 +0,0 @@
----
-title: Archivo de Información Stellar (SEP-1)
-sidebar_position: 50
----
-
-## Descripción general
-
-SEP-1 (Archivo de Información Stellar) permite que las wallets y otras aplicaciones Stellar descubran información sobre tu servicio de ancla. Al alojar un archivo `stellar.toml` en `/.well-known/stellar.toml`, permites que las aplicaciones encuentren automáticamente:
-
-- Información de tu organización
-- Activos y monedas que se soportan
-- Puntos finales de autenticación (SEP-10)
-- Puntos finales de SEP para SEP-6, SEP-24, SEP-31, SEP-38, SEP-45
-
-Para más detalles, por favor consulta la [especificación SEP-1][sep-1].
-
-## Crear tu archivo stellar.toml
-
-Crea un archivo `stellar.toml` con la información de tu servicio. Aquí tienes un ejemplo mínimo para comenzar:
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["GD...G"]  # Your distribution account public keys
-SIGNING_KEY = "GD...G"  # Your signing key (public key) for SEP-10 authentication
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"  # Use "Public Global Stellar Network ; September 2015" for mainnet
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "https://your-website.com"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-:::tip
-
-Para una lista completa de todos los atributos disponibles en `stellar.toml`, consulta la [especificación SEP-1][sep-1]. Necesitarás añadir secciones adicionales como `[[CURRENCIES]]`, `TRANSFER_SERVER`, `TRANSFER_SERVER_SEP0024`, `WEB_AUTH_ENDPOINT`, `WEB_AUTH_FOR_CONTRACTS_ENDPOINT`, `DIRECT_PAYMENT_SERVER`, etc., conforme configures los activos soportados y otros SEPs.
-
-:::
-
-:::important
-
-**Producción vs. Desarrollo**: Necesitarás archivos `stellar.toml` separados para testnet y mainnet:
-
-- **Testnet**: Usa `NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"`
-- **Mainnet**: Usa `NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"`
-
-Asegúrate de que tu archivo de producción incluya tus cuentas de distribución reales del Mainnet, claves de firma y las URLs del servicio de producción.
-
-:::
-
-## Configuración
-
-Para habilitar SEP-1, necesitas configurar cómo la Anchor Platform debe acceder a tu archivo `stellar.toml`. La plataforma soporta tres métodos:
-
-| Tipo     | Caso de Uso                                  | Descripción                                                            |
-| -------- | -------------------------------------------- | ---------------------------------------------------------------------- |
-| `file`   | **Recomendado para la mayoría de los casos** | Lee desde un archivo local en el servidor                              |
-| `string` | Pruebas rápidas o configuraciones simples    | Proporciona el contenido TOML directamente en la configuración         |
-| `url`    | Alojamiento externo                          | Obtiene el archivo desde una URL remota (útil para contenido dinámico) |
-
-### Variables de Entorno
-
-Configura SEP-1 usando las siguientes variables de entorno:
-
-- `SEP1_ENABLED`: Setea a `true` para habilitar SEP-1
-- `SEP1_TOML_TYPE`: Uno de `file`, `string`, o `url`
-- `SEP1_TOML_VALUE`: El valor depende del tipo (ver ejemplos abajo)
-
-### Método 1: Archivo (Recomendado)
-
-Ideal para: despliegues en producción donde manejas el archivo en disco.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/path/to/your/stellar.toml
-```
-
-</CodeExample>
-
-:::tip
-
-Al usar Docker, monta tu archivo `stellar.toml` como un volumen y referencia la ruta dentro del contenedor. Por ejemplo:
-
-```yaml
-# docker-compose.yaml
-volumes:
-  - ./config/stellar.toml:/config/stellar.toml:ro
-```
-
-Luego configura `SEP1_TOML_VALUE=/config/stellar.toml` en tu entorno.
-
-:::
-
-### Método 2: Cadena de texto
-
-Ideal para: pruebas rápidas, desarrollo, o cuando configures mediante variables de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=string
-SEP1_TOML_VALUE="ACCOUNTS = [\"GD...G\"]
-SIGNING_KEY = \"GD...G\"
-NETWORK_PASSPHRASE = \"Test SDF Network ; September 2015\"
-[DOCUMENTATION]
-ORG_NAME = \"Your organization\"
-ORG_URL = \"https://your-website.com\""
-```
-
-</CodeExample>
-
-:::caution
-
-Cuando uses el tipo `string`, asegúrate de que el contenido TOML esté correctamente escapado según el formato de tu archivo de entorno. Para configuraciones complejas, el tipo `file` es más fácil de manejar.
-
-:::
-
-### Método 3: URL
-
-Ideal para: contenido dinámico o cuando alojes el archivo externamente.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=url
-SEP1_TOML_VALUE=https://example.com/stellar.toml
-```
-
-</CodeExample>
-
-:::note
-
-Cuando uses el tipo `url`, la Anchor Platform obtendrá el archivo en cada solicitud. Asegúrate de que la URL sea accesible desde tu servidor de Anchor Platform y que devuelva contenido TOML válido.
-
-:::
-
-## Accediendo a tu archivo stellar.toml
-
-Una vez configurado y habilitado, la Anchor Platform sirve automáticamente tu archivo `stellar.toml` en el endpoint estándar SEP-1:
-
-- **`/.well-known/stellar.toml`** - El endpoint principal (servido con `Content-Type: text/plain`)
-- **`/`** - Redirige a `/.well-known/stellar.toml` cuando SEP-1 está habilitado
-
-### Probar tu configuración
-
-Después de iniciar la Anchor Platform, verifica tu configuración:
-
-```bash
-# Test the endpoint
-curl http://localhost:8080/.well-known/stellar.toml
-
-# Or test the redirect
-curl -L http://localhost:8080/
-```
-
-Deberías ver el contenido de tu `stellar.toml` devuelto como texto plano.
-
-### Alternativa: Alojamiento externo
-
-También puedes alojar tu archivo `stellar.toml` usando un servidor de archivos estático como [nginx] o una CDN. Si eliges este enfoque:
-
-1. Aloja el archivo en `https://your-domain.com/.well-known/stellar.toml`
-2. Asegúrate de que sea accesible públicamente
-3. Asegúrate de que tu archivo `stellar.toml` incluya las URLs correctas apuntando a tus endpoints de Anchor Platform
-
-El servicio SEP-1 de Anchor Platform es opcional si alojas el archivo externamente, pero ofrece una manera conveniente de gestionar todo en un solo lugar.
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep10/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep10/README.mdx
deleted file mode 100644
index 14d025d022..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep10/README.mdx
+++ /dev/null
@@ -1,291 +0,0 @@
----
-title: Autenticación Stellar (SEP-10)
-sidebar_position: 60
----
-
-## Resumen
-
-SEP-10 (Autenticación Web Stellar) permite a las aplicaciones de billetera crear sesiones autenticadas con anclas Stellar demostrando control sobre una cuenta Stellar. Una vez autenticadas, las billeteras reciben un Token Web JSON (JWT) que usan en solicitudes posteriores a los servicios estandarizados del ancla.
-
-Para la especificación completa, consulta [SEP-0010: Autenticación Web Stellar](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md).
-
-La Plataforma Anchor tiene implementado SEP-10 con soporte para:
-
-- **Flujo de Desafío/Respuesta**: GET `/auth` para solicitar un desafío, POST `/auth` para validar y recibir un JWT
-- **Atribución de Cliente**: Verificación opcional de identidad de la aplicación cliente para billeteras no custodiales
-- **Soporte para Billeteras Custodiales**: Soporte para billeteras custodiales que gestionan cuentas de usuario
-- **Múltiples Dominios de Origen**: Soporte para múltiples dominios y patrones comodín
-
-## Flujo Típico de Autenticación
-
-1. El **Cliente** solicita un desafío único del **Servidor**
-2. El **Cliente** verifica y firma el desafío
-3. El **Cliente** envía el desafío firmado al **Servidor**
-4. El **Servidor** verifica el desafío y responde con un token de sesión JWT
-
-## Habilitar SEP-10
-
-Para habilitar SEP-10, configura las siguientes variables de entorno en tu archivo `dev.env`.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP10_ENABLED=true
-SEP10_HOME_DOMAINS=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret encryption key"
-```
-
-</CodeExample>
-
-### Configuración Requerida (Si está habilitado)
-
-| Variable                    | Valor Predeterminado | Descripción                                                                                                                                                                                                 |
-| --------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SEP10_ENABLED`             | `false`              | Establece en `true` para habilitar la autenticación SEP-10                                                                                                                                                  |
-| `SEP10_HOME_DOMAINS`        | `localhost:8080`     | Lista de dominios de origen (separados por comas). Soporta patrones comodín como `*.stellar.org`. El `home_domain` debe coincidir con el host donde se sirve tu archivo `stellar.toml`.                     |
-| `SECRET_SEP10_SIGNING_SEED` | _Requerido_          | La clave privada correspondiente a `SIGNING_KEY` en tu archivo `stellar.toml`. Se usa para firmar los desafíos de autenticación. Las billeteras verifican esta firma antes de firmar y devolver el desafío. |
-| `SECRET_SEP10_JWT_SECRET`   | _Requerido_          | La clave de cifrado usada para firmar y verificar tokens JWT emitidos a billeteras autenticadas.                                                                                                            |
-
-:::important
-
-La `SIGNING_KEY` en tu archivo `stellar.toml` debe ser la clave pública derivada de `SECRET_SEP10_SIGNING_SEED`. Las billeteras verificarán que las transacciones de desafío estén firmadas por esta clave.
-
-:::
-
-### Configuración Opcional
-
-<CodeExample>
-
-```bash
-# dev.env
-# Optional: Specify web_auth_domain (default: first home_domain if only one is specified)
-SEP10_WEB_AUTH_DOMAIN=localhost:8080
-
-# Optional: Challenge transaction timeout in seconds (default: 900)
-SEP10_AUTH_TIMEOUT=900
-
-# Optional: JWT token timeout in seconds (default: 86400 = 24 hours)
-SEP10_JWT_TIMEOUT=86400
-
-# Optional: Require Authorization header in GET /auth requests (default: false)
-SEP10_REQUIRE_AUTH_HEADER=false
-
-# Optional: Client attribution requirement (default: false)
-SEP10_CLIENT_ATTRIBUTION_REQUIRED=false
-
-# Optional: Client allow list (default: empty, all configured clients allowed)
-# Comma-separated list of client names that are allowed to authenticate
-SEP10_CLIENT_ALLOW_LIST=client1,client2
-```
-
-</CodeExample>
-
-| Variable                            | Valor Predeterminado                                                  | Descripción                                                                                                                                                                                                                                                           |
-| ----------------------------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `SEP10_WEB_AUTH_DOMAIN`             | Primer `home_domain` si se especifica uno solo, de lo contrario vacío | La propiedad `web_auth_domain` usada en las respuestas SEP-10. Requerido si tienes múltiples `home_domains` o usas patrones comodín. Debe coincidir con el host del servidor SEP.                                                                                     |
-| `SEP10_AUTH_TIMEOUT`                | `900`                                                                 | Tiempo en segundos durante el cual una transacción de desafío permanece válida. Los clientes deben firmar y enviar el desafío dentro de esta ventana.                                                                                                                 |
-| `SEP10_JWT_TIMEOUT`                 | `86400`                                                               | Tiempo en segundos durante el cual un token JWT emitido permanece válido. Después de expirar, los clientes deben volver a autenticarse.                                                                                                                               |
-| `SEP10_REQUIRE_AUTH_HEADER`         | `false`                                                               | Si es `true`, requiere un encabezado Authorization válido (Bearer JWT) en las solicitudes GET `/auth` para desafíos. Esto previene accesos no autorizados al endpoint y es útil para flujos de reautenticación donde los clientes necesitan refrescar sus tokens JWT. |
-| `SEP10_CLIENT_ATTRIBUTION_REQUIRED` | `false`                                                               | Si es `true`, las billeteras no custodiales deben proporcionar un `client_domain` en las solicitudes de desafío. Requiere configuración en el cliente (ver más abajo).                                                                                                |
-| `SEP10_CLIENT_ALLOW_LIST`           | Vacío (se permiten todos los clientes configurados)                   | Lista separada por comas de nombres de cliente permitidos para autenticarse. Solo relevante cuando `SEP10_CLIENT_ATTRIBUTION_REQUIRED=true`. Si está vacío, todos los clientes configurados están permitidos.                                                         |
-
-:::tip
-
-**Múltiples Dominios de Origen**: Si especificas múltiples `home_domains` (por ejemplo, `ap.stellar.org,*.sdp.stellar.org`), también debes establecer `SEP10_WEB_AUTH_DOMAIN` para indicar qué dominio hospeda el endpoint de autenticación.
-
-:::
-
-## Atribución de Cliente
-
-La atribución de cliente te permite restringir la autenticación a aplicaciones específicas de billetera y verificar su identidad. Esta es una característica opcional que solo debería habilitarse si es un requisito de negocio.
-
-:::info
-
-Por defecto, la Plataforma Anchor permite que cualquier persona con una cuenta Stellar se autentique. La atribución de cliente solo es necesaria si quieres:
-
-- Restringir la autenticación a aplicaciones específicas de billetera
-- Verificar la identidad de aplicaciones de billetera no custodiales
-- Rastrear qué aplicaciones de billetera usan tus usuarios
-
-:::
-
-### Habilitar Atribución de Cliente
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP10_CLIENT_ATTRIBUTION_REQUIRED=true
-```
-
-</CodeExample>
-
-Cuando `SEP10_CLIENT_ATTRIBUTION_REQUIRED=true`, las billeteras no custodiales deben:
-
-1. Proporcionar un parámetro `client_domain` en la solicitud de desafío
-2. Firmar la transacción de desafío con `SIGNING_KEY` del archivo `stellar.toml` de ese dominio
-3. Tener su dominio listado en tu configuración de clientes
-
-### Configuración de Cliente
-
-Configura los clientes permitidos en tu archivo de configuración YAML:
-
-<CodeExample>
-
-```yaml
-clients:
-  # Each item in the list may contain the following fields:
-  #   - name: (required) the name of the client
-  #   - type: (required) `custodial` or `noncustodial`
-  #
-  #   If the type is `custodial`,
-  #   - signing_keys: (required) the custodial SEP-10 signing key(s) of the client.
-  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
-  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
-  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
-  #   - callback_urls.sep12: (optional) the URL of the client's SEP-12 callback API endpoint.
-  #   - allow_any_destination: (optional) default to false. If set to true, allows any destination for deposits.
-  #   - destination_accounts: (optional) list of accounts allowed to be used for the deposit.
-  #                           If allow_any_destination is set to true, this configuration option is ignored.
-  #
-  #   If the type is `noncustodial`,
-  #   - domains: (required) the domains of the client.
-  #   - callback_urls.sep6: (optional) the URL of the client's SEP-6 callback API endpoint.
-  #   - callback_urls.sep24: (optional) the URL of the client's SEP-24 callback API endpoint.
-  #   - callback_urls.sep31: (optional) the URL of the client's SEP-31 callback API endpoint.
-  #   - callback_urls.sep12: (optional) the URL of the client's SEP-12 callback API endpoint.
-
-  # custodial client
-  - name: bluecorp
-    type: custodial
-    signing_keys: "the signing key 1 of bluecorp","the signing key 2 of bluecorp"
-    callback_urls:
-      sep6: https://callback.bluecorp.com/api/v1/anchor/callback/sep6
-      sep12: https://callback.bluecorp.com/api/v1/anchor/callback/sep12
-    allow_any_destination: false
-    destination_accounts: GA...
-
-  # noncustodial client
-  - name: pinkcorp
-    type: noncustodial
-    domains: pinkcorp.com
-    callback_urls:
-      sep6: https://callback.pinkcorp.com/api/v2/anchor/callback/sep6
-      sep12: https://callback.pinkcorp.com/api/v2/anchor/callback/sep12
-
- - name: redcorp
-    type: custodial
-    signing_keys: "the signing key of redcorp",
-
-```
-
-</CodeExample>
-
-O configura mediante variables de entorno:
-
-<CodeExample>
-
-```bash
-# dev.env
-# custodial client
-CLIENTS[0]_NAME=bluecorp
-CLIENTS[0]_TYPE=custodial
-CLIENTS[0]_SIGNING_KEYS="the signing key 1 of bluecorp","the signing key 2 of bluecorp"
-CLIENTS[0]_ALLOW_ANY_DESTINATION=false
-CLIENTS[0]_DESTINATION_ACCOUNTS=GA...
-
-# noncustodial client
-CLIENTS[1]_NAME=pinkcorp
-CLIENTS[1]_TYPE=noncustodial
-CLIENTS[1]_DOMAINS=pinkcorp.com
-
-# custodial client
-CLIENTS[2]_NAME=redcorp
-CLIENTS[2]_TYPE=custodial
-CLIENTS[2]_SIGNING_KEYS="the signing key of redcorp"
-```
-
-</CodeExample>
-
-## Configurar stellar.toml
-
-Actualiza tu archivo `stellar.toml` para anunciar soporte SEP-10. Las billeteras descubren tu endpoint de autenticación a través de este archivo.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-SIGNING_KEY = "add your signing key here (public key from SECRET_SEP10_SIGNING_SEED)"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-```
-
-</CodeExample>
-
-Estos campos deben coincidir con las opciones de configuración establecidas en la sección [Habilitar SEP-10](#enable-sep-10) arriba.
-
-`WEB_AUTH_ENDPOINT` - La URL donde está corriendo el servicio de autenticación. Esta es la URL que los clientes usarán para autenticarse con el ancla. El endpoint debe soportar:
-
-- `GET <WEB_AUTH_ENDPOINT>` - Solicitar un desafío
-- `POST <WEB_AUTH_ENDPOINT>` - Intercambiar desafío firmado por token de sesión JWT
-
-`SIGNING_KEY` - La clave pública correspondiente a la clave privada especificada en `SECRET_SEP10_SIGNING_SEED`. Esta clave se usa para firmar los desafíos de autenticación presentados a las aplicaciones de billetera.
-
-:::important
-
-- **`SIGNING_KEY`**: Debe ser la clave pública derivada de `SECRET_SEP10_SIGNING_SEED`
-- **`WEB_AUTH_ENDPOINT`**: Usa `https://` en producción. La ruta `/auth` es el endpoint estándar SEP-10.
-- **Coincidencia de Host**: El host en `WEB_AUTH_ENDPOINT` debe coincidir con uno de tus `SEP10_HOME_DOMAINS` (o el `SEP10_WEB_AUTH_DOMAIN`, si está especificado).
-
-:::
-
-## Cómo Probar el Flujo de Autenticación
-
-El flujo de autenticación SEP-10 consta de dos pasos:
-
-1. **GET `/auth`** - Solicitar una transacción de desafío
-   - Parámetros: `account` (requerido), `memo` (opcional), `home_domain` (opcional), `client_domain` (opcional)
-   - Retorna: Una transacción de desafío en formato XDR
-
-2. **POST `/auth`** - Validar el desafío firmado y recibir un JWT
-   - Cuerpo: `{ "transaction": "<signed_challenge_xdr>" }`
-   - Retorna: `{ "token": "<jwt_token>" }`
-
-El token JWT debe incluirse en solicitudes API posteriores como token Bearer en el encabezado `Authorization`.
-
-:::tip
-
-**Probar Tu Configuración**: Puedes probar la autenticación SEP-10 usando curl y Stellar CLI. Para obtener más información sobre Stellar CLI, consulta la [documentación de Stellar CLI](../../../../tools/cli/README.mdx).
-
-```bash
-# Verify if `stellar` command line is installed
-stellar --version
-
-# List your Stellar keys/identities
-stellar keys ls
-
-# Get your account ID (public key) and secret seed
-# Replace 'alice' with your identity name from `stellar keys ls`
-IDENTITY_NAME="alice"
-ACCOUNT_ID=$(stellar keys public-key "$IDENTITY_NAME")
-SECRET_SEED=$(stellar keys secret "$IDENTITY_NAME")
-
-# Step 1: Request challenge and save the transaction XDR
-CHALLENGE_RESPONSE=$(curl -s "http://localhost:8080/auth?account=$ACCOUNT_ID")
-CHALLENGE_XDR=$(echo "$CHALLENGE_RESPONSE" | jq -r '.transaction')
-
-# Step 2: Sign the challenge transaction using Stellar CLI
-# Note: The output includes info messages; the signed XDR is on the last line
-SIGNED_CHALLENGE_XDR=$(echo "$CHALLENGE_XDR" | stellar tx sign --sign-with-key "$SECRET_SEED" 2>&1 | tail -1)
-
-# Step 3: Submit the signed challenge and receive JWT token
-curl -X POST "http://localhost:8080/auth" \
-  -H "Content-Type: application/json" \
-  -d "{\"transaction\": \"$SIGNED_CHALLENGE_XDR\"}"
-```
-
-:::
-
-[sep1-ap]: ../sep1/README.mdx
-[sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/README.mdx
deleted file mode 100644
index c7cbd53967..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Depósitos y Retiros Gestionados (SEP-24)
-sidebar_position: 90
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-24 permite que las carteras y/o exchanges ofrezcan al usuario un medio para interactuar directamente con una rampa de entrada y salida.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/configuration.mdx
deleted file mode 100644
index 2d2d63722f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/configuration.mdx
+++ /dev/null
@@ -1,211 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-## Modificar un archivo Stellar Info
-
-A continuación, modifiquemos el archivo `stellar.toml` creado [anteriormente][sep1-ap]. Las carteras deben saber que tu negocio admite la funcionalidad SEP-24 y también deben conocer todas las monedas que admites.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-TRANSFER_SERVER_SEP0024 = "http://localhost:8080/sep24"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
-WEB_AUTH_CONTRACT_ID = "Your web auth contract id"
-
-# Add support for USDC
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-# Optionally, add support for XLM
-[[CURRENCIES]]
-code = "native"
-status = "test"
-is_asset_anchored = false
-anchor_asset_type = "crypto"
-desc = "XLM, the native token of the Stellar network."
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que necesitarás crear otro archivo para tu despliegue en producción que utilice la frase de contraseña de la red pública, las URL de servicio de producción, tus cuentas de distribución y la clave de firma de Mainnet, así como las cuentas emisoras de Mainnet de los activos que utiliza tu servicio.
-
-## Habilitar depósitos y retiros alojados
-
-Ahora estás listo para habilitar depósitos y retiros alojados mediante la API SEP-24. Especifica lo siguiente en tu archivo `dev.assets.yaml` y cambia los valores según tus preferencias. Este archivo de ejemplo habilitará el soporte para USDC de Circle y un dólar fiat.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep24:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - SEPA
-          - SWIFT
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - bank_account
-          - cash
-  - id: iso4217:USD
-    significant_decimals: 2
-  # Optional support for XLM
-  - id: stellar:native
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 7
-    sep24:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - SEPA
-          - SWIFT
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - bank_account
-          - cash
-```
-
-</CodeExample>
-
-La información proporcionada para el valor `assets` coincide en gran medida con la información que se expondrá a la aplicación de cartera mediante el endpoint SEP-24 [`GET /info`][sep24-get-info]. La plataforma Anchor también utiliza esta información para validar las solicitudes realizadas a tu servicio.
-
-Agrega las siguientes variables a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-// Required
-SEP24_ENABLED=true
-SEP24_INTERACTIVE_URL_BASE_URL=http://example.com
-SEP24_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET="your encryption key shared with your business server"
-SECRET_SEP24_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-
-// Optional
-SEP24_INITIAL_USER_DEADLINE_SECONDS=1209600
-```
-
-</CodeExample>
-
-`SEP24_INTERACTIVE_URL_BASE_URL` es la URL que la plataforma Anchor proporcionará a las aplicaciones de cartera cuando inicien transacciones. Las aplicaciones de cartera abrirán esta URL en una vista web dentro de su aplicación, cediendo el control de la experiencia del usuario de la cartera a tu negocio. Esta URL apunta al widget web que implementa tu negocio. Contiene toda la lógica definida por el negocio. Examinaremos esta experiencia con más detalle en secciones posteriores.
-
-`SEP24_MORE_INFO_URL_BASE_URL` es la URL que la plataforma Anchor proporcionará a las aplicaciones de cartera cuando quieran mostrar información sobre una transacción iniciada previamente. Esta URL es utilizada mayormente por las carteras en sus vistas de historial de transacciones, y tu negocio puede definir qué información mostrar acerca de la transacción.
-
-`SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET` y `SECRET_SEP24_MORE_INFO_URL_JWT_SECRET` son claves de cifrado que la plataforma Anchor usará para generar tokens de corta duración que añadirá a las URLs proporcionadas a la cartera. Tu servidor de negocio también debe tener estas claves en su entorno para verificar la firma del token.
-
-`SEP24_INITIAL_USER_DEADLINE_SECONDS` es un parámetro opcional que define el tiempo en segundos que tiene el usuario para actuar antes de que la transacción pase al siguiente estado. Determina el campo `user_action_required_by`, que indica la fecha límite. Consulta [JSON-RPC Methods][json-rpc-methods] para ejemplos de uso.
-
-## Probar con la billetera de demostración
-
-¡Las carteras ahora deberían poder descubrir, autenticar e iniciar transacciones con tu servicio! Tu proyecto y archivos fuente ahora deberían verse algo así.
-
-<CodeExample>
-
-```
-├── dev.env
-├── docker-compose.yaml
-├── config
-│   ├── dev.assets.yaml
-│   ├── dev.stellar.toml
-```
-
-</CodeExample>
-
-Tu entorno ahora debería verse de la siguiente manera.
-
-<CodeExample>
-
-```bash
-# dev.env
-ASSETS_TYPE=file
-ASSETS_VALUE=/home/dev.assets.yaml
-
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/home/dev.stellar.toml
-
-SEP10_ENABLED=true
-SEP10_HOME_DOMAIN=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret encryption key"
-
-SEP24_ENABLED=true
-SEP24_INTERACTIVE_URL_BASE_URL=http://localhost:8081
-SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET="your encryption key shared with your business server"
-SECRET_SEP24_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-```
-
-</CodeExample>
-
-Para probar esto, ve a la [Cartera de Demostración Stellar][stellar-demo-wallet].
-
-[![cartera de demostración conectada a la plataforma anchor](/assets/ap/anchor-platform-sep24-demo-wallet.png)](/assets/ap/anchor-platform-sep24-demo-wallet.png)
-
-Inicia una transacción haciendo lo siguiente:
-
-- Crear un nuevo par de claves
-- Haz clic en el botón "Agregar activo" y escribe
-  - el código del activo Stellar en tu archivo `stellar.toml`
-  - tu dominio principal, `localhost:8080`
-- Selecciona el desplegable y haz clic en "Depósito SEP-24", luego haz clic en "Iniciar"
-
-La cartera de demostración debería poder encontrar tu archivo `stellar.toml`, autenticar usando el par de claves Stellar que acabas de crear e iniciar una transacción. Sin embargo, cuando la cartera de demostración intente abrir la URL proporcionada por la plataforma Anchor, obtendrás una página de no encontrado.
-
-[![cartera de demostración tras iniciar una transacción](/assets/ap/anchor-platform-sep24-demo-wallet-widget.png)](/assets/ap/anchor-platform-sep24-demo-wallet-widget.png)
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
-[sep1-ap]: ../sep1/README.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/example.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/example.mdx
deleted file mode 100644
index 2ecca21616..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/example.mdx
+++ /dev/null
@@ -1,438 +0,0 @@
----
-title: Ejemplo
-sidebar_position: 40
----
-
-Integrarse con Anchor Platform implica tres áreas clave:
-
-- Crear una experiencia de usuario basada en web que pueda abrirse en una vista web móvil
-- Proporcionar actualizaciones del estado de las transacciones a Anchor Platform
-- Obtener actualizaciones del estado de las transacciones desde Anchor Platform
-
-## Crear una experiencia de usuario basada en web
-
-Anchor Platform no ofrece una interfaz de usuario marca blanca que tu negocio pueda utilizar; en cambio, espera que el negocio construya su propia interfaz y sistema backend. No construiremos toda una experiencia de usuario de entrada y salida en esta guía, pero cubriremos las maneras en que tu producto existente debe actualizarse para ser compatible con Anchor Platform.
-
-### Autenticación
-
-Si tu negocio ya tiene un producto de entrada y salida, probablemente ya cuentes con un sistema para la autenticación de usuarios. Sin embargo, dado que Anchor Platform autentica al usuario antes de proporcionar la URL del negocio, requerir al usuario que pase por otra forma de autenticación resulta innecesario. De esta forma, se puede pensar que Anchor Platform proporciona una forma alternativa de autenticación.
-
-El negocio es libre de seguir exigiendo que los usuarios se autentiquen usando su sistema existente, pero la experiencia ideal sería saltar este paso y crear una sesión autenticada si ya se autenticaron usando su cuenta Stellar.
-
-Anchor Platform añade un parámetro de consulta JWT `token` a la URL del negocio que se proporciona a la aplicación wallet. Este token está firmado con el valor `SECRET_SEP24_INTERACTIVE_URL_JWT_SECRET` configurado previamente, e incluye la información necesaria para identificar al usuario. El proceso debería verse algo así:
-
-1. Pasa el `token` añadido a la URL de tu sistema backend
-2. Verifica la firma del `token` y revisa su caducidad
-3. Crea una sesión autenticada para el usuario identificado por `token.sub`
-
-El contenido decodificado del `token` se verá algo así:
-
-<CodeExample>
-
-```json
-{
-  "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
-  "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB:1234567",
-  "exp": 1516239022,
-  "data": {
-    "first_name": "John",
-    "last_name": "Doe",
-    "email": "johndoe@example.com"
-  }
-}
-```
-
-</CodeExample>
-
-Nota que el valor `sub` identifica al usuario usando una cuenta Stellar y un entero. Este será el valor cuando aplicaciones de custodia que usan una cuenta global se autentiquen con tu servicio. Cuando carteras no custodias se autentiquen, el token puede verse un poco diferente.
-
-<CodeExample>
-
-```json
-{
-  "jti": "e26cf292-814f-4918-9b40-b4f76a300f98",
-  "sub": "GB244654NC6YPEFU3AY7L25COGES445P3Q63W6Q76JHR3UBJMLT2XBOB",
-  "exp": 1516239022,
-  "data": {
-    "client_domain": "api.vibrantapp.com",
-    "first_name": "John",
-    "last_name": "Doe",
-    "email": "johndoe@example.com"
-  }
-}
-```
-
-</CodeExample>
-
-El valor `sub` aquí solo contiene una clave pública para identificar al usuario, y el campo `data.client_domain` identifica la aplicación wallet usada para autenticar.
-
-En ambos casos, toda la información dentro del objeto `data` es opcional y solo estará presente si la wallet la proporciona.
-
-Vamos a añadir un servidor backend a nuestro archivo compose que se usará para verificar el token y crear sesiones web autenticadas para usuarios que inicien transacciones.
-
-<CodeExample>
-
-```yaml
-# docker-compose.yaml
----
-business-server:
-  build: .
-  ports:
-    - "8081:8081"
-  env_file:
-    - ./dev.env
-  depends_on:
-    - platform-server
-```
-
-</CodeExample>
-
-Vamos a crear un contenedor Docker sencillo para nuestra aplicación.
-
-<CodeExample>
-
-```docker
-FROM node:19
-
-WORKDIR /home
-COPY . .
-RUN npm install
-
-CMD ["node", "server.js"]
-```
-
-</CodeExample>
-
-Ahora vamos a crear una aplicación NodeJS mínima.
-
-<CodeExample>
-
-```bash
-yarn init -y
-yarn add express jsonwebtoken
-touch server.js
-```
-
-</CodeExample>
-
-A continuación, un ejemplo de un servidor backend autenticando un usuario usando NodeJS.
-
-<CodeExample>
-
-```js
-# server.js
-const express = require("express");
-const jwt = require("jsonwebtoken");
-const app = express();
-const port = process.env.BUSINESS_SERVER_PORT;
-
-app.use(express.json());
-
-/*
- * We'll store user session data in memory, but production systems
- * should store this data somewhere more persistent.
- */
-const sessions = {};
-
-/*
- * Create an authenticated session for the user.
- *
- * Return a session token to be used in future requests as well as the
- * user data. Note that you may not have a user for the stellar account
- * provided, in which case the user should go through your onboarding
- * process.
- */
-app.post("/session", async (req, res) => {
-  let decodedPlatformToken;
-  try {
-    decodedPlatformToken = validatePlatformToken(req.body.platformToken);
-  } catch (err) {
-    res.status = 400;
-    res.send({ "error": err });
-    return;
-  }
-  let user = getUser(decodedPlatformToken.sub);
-  let sessionToken = jwt.sign(
-    { "jti": decodedPlatformToken.jti },
-    process.env.SESSION_JWT_SECRET
-  );
-  sessions[sessionToken] = user;
-  res.send({
-    "token": sessionToken,
-    "user": user
-  });
-});
-
-/*
- * Validate the signature and contents of the platform's token
- */
-function validatePlatformToken(token) {
-  if (!token) {
-    throw "missing 'platformToken'";
-  }
-  let decodedToken;
-  try {
-    decodedToken = jwt.verify(token, process.env.SECRET_SEP10_JWT_SECRET);
-  } catch {
-    throw "invalid 'platformToken'";
-  }
-  if (!decodedToken.jti) {
-    throw "invalid 'platformToken': missing 'jti'";
-  }
-  return decodedToken;
-}
-
-/*
- * Query your own database for the user based on account:memo string parameter
- */
-function getUser(sub) {
-  return null;
-}
-
-app.listen(port, () => {
-    console.log(`business server listening on port ${port}`);
-});
-```
-
-</CodeExample>
-
-Ejecuta esto junto con el servidor de la plataforma y la base de datos, e inicia una nueva transacción con la [demo wallet][stellar-demo-wallet]. Luego, enviaremos el token a nuestro servidor.
-
-<CodeExample>
-
-```bash
-curl \
-  -X POST \
-  -H 'Content-Type: application/json' \
-  -d '{"platformToken": "<paste the token from the URL here>"}' \
-  http://localhost:8081/session | jq
-```
-
-</CodeExample>
-
-## Proporcionar actualizaciones a la plataforma
-
-Vamos a crear un endpoint para nuestro servidor de negocio que acepte la información recogida en nuestra UI.
-
-<CodeExample>
-
-```js
-# server.js
-
-// Production systems should either let the Anchor Platform generate its own memos
-// or have your custodial service generate a memo for each transaction.
-const transactionMemos = {};
-
-app.post("/transaction", async (req, res) => {
-  let sessionToken;
-  try {
-    sessionToken = validateSessionToken(req.headers.get("authorization"));
-  } catch (err) {
-    res.status = 400;
-    res.send({ "error": err })
-    return;
-  }
-  // assuming this is a withdrawal transaction, we'll provide a memo, which is
-  // required by our third-party custodian to credit us the payment. When the
-  // payment is made with this memo, we can match the on-chain payment with the
-  // transaction in the Anchor Platform's database.
-  transactionMemos[req.body.transaction.id] = parseInt(Math.random() * 100000);
-  let rpcRequestBody = [
-    {
-      "id": 1,
-      "jsonrpc": "2.0",
-      "method": "request_onchain_funds",
-      "params": {
-        "transaction_id": req.body.transaction.id,,
-        "message": "waiting for the user to provide off-chain funds.",
-        "amount_in": {
-          "amount": req.body.amount_in.amount,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "amount_out": {
-          "amount": req.body.amount_out.amount,
-          "asset": "iso4217:USD"
-        },
-        "fee_details": {
-          "total": req.body.fee_details.total,
-          "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-        },
-        "destination_account": "GD...G",
-        "memo": transactionMemos[req.body.transaction.id],
-        "memo_type": "id"
-      }
-    }
-  ];
-  let platformResponse;
-  try {
-    platformResponse = await updatePlatformTransaction(rpcRequestBody);
-  } catch (err) {
-    res.status = 500;
-    res.send({ "error": err })
-    return;
-  }
-  res.send({
-    "transaction": platformResponse.records[0]
-  });
-});
-
-function validateSessionToken(authorizationHeader) {
-    let parts = authorizationHeader.split(" ");
-    if (parts.length != 2 || parts[0] != "Bearer") {
-        throw "invalid authorization header format";
-    }
-    let sessionToken = parts[1];
-    try {
-        jwt.verify(sessionToken, process.env.SESSION_JWT_SECRET);
-    } catch {
-        throw "invalid session token";
-    }
-    if (!sessions[sessionToken]) {
-        throw "expired session";
-    }
-    return sessionToken;
-}
-
-async function updatePlatformTransaction(requestBody) {
-  let response = await fetch(
-    `${process.env.PLATFORM_SERVER}`,
-    {
-      method: "POST",
-      headers: {
-        "Content-Type": "application/json"
-      },
-      body: JSON.stringify(requestBody)
-    }
-  );
-  if (response.status != 200) {
-    throw `unexpected status code: ${response.status}`;
-  }
-  return await response.json();
-}
-```
-
-</CodeExample>
-
-Esto actualizará la base de datos de Anchor Platform con la información proporcionada y permitirá que las aplicaciones wallet obtengan esta información actualizada para transmitírsela al usuario. Ya deberías haber informado al usuario sobre los montos de la transacción y que tu negocio está esperando que llegue el pago en cadena, pero proporcionando estas actualizaciones permites a los usuarios ver el estado de sus transacciones desde su aplicación móvil sin necesidad de abrir nuevamente la UI del negocio.
-
-:::note
-
-Actualmente, Anchor Platform no envía notificaciones a la aplicación wallet cuando cambian los estados de las transacciones; sin embargo, está en nuestra hoja de ruta agregar estas notificaciones o "callback requests" para que las wallets no tengan que hacer polling a Anchor Platform en busca de actualizaciones.
-
-:::
-
-## Obtener actualizaciones desde la plataforma
-
-Si solo usas Anchor Platform para exponer las APIs SEP a aplicaciones wallet, entonces no tendrás una razón fuerte para obtener actualizaciones del estado de las transacciones desde Anchor Platform, principalmente porque no actualizará el estado de la transacción hasta que hagas solicitudes `JSON-RPC API`.
-
-Sin embargo, si usas Anchor Platform para monitorear la red Stellar en busca de pagos entrantes (asociados con transacciones de retirada de fondos), Anchor Platform actualizará los estados de las transacciones cuando se reciban esos pagos.
-
-Hay dos formas de obtener actualizaciones desde Anchor Platform,
-
-- Haciendo polling al endpoint `GET /transactions/:id` del API de la plataforma para las transacciones por las que esperas un pago
-- Recibiendo eventos de cambio de estado de transacciones mediante streaming desde un clúster Kafka
-
-Aunque hacer streaming de cambios de estado de transacciones desde un clúster Kafka puede ser un enfoque más robusto y escalable, usaremos el método de polling en esta guía. Configurar y usar un clúster Kafka será tema de una sección distinta de la documentación.
-
-Primero, configuremos Anchor Platform para observar la red Stellar en busca de pagos entrantes.
-
-<CodeExample>
-
-```yaml
-# docker-compose.yml
----
-stellar-observer:
-  image: stellar/anchor-platform:latest
-  command: --stellar-observer
-  env_file:
-    - ./dev.env
-  volumes:
-    - ./config:/home
-  depends_on:
-    - db
-```
-
-</CodeExample>
-
-El comando `--stellar-observer` inicia un proceso que monitorea las cuentas de distribución configuradas en tu archivo `config.yaml` en busca de pagos de retirada de fondos.
-
-Si se envía un pago a una de estas cuentas y el memo adjunto a la transacción coincide con un valor `memo` proporcionado o generado por Anchor Platform, Anchor Platform considerará que la transacción con ese memo se ha recibido y actualizará el estado de la transacción a `pending_anchor`. Esto se hace realizando una solicitud `JSON-RPC API`, por lo que necesitamos configurar la URL que debe usar.
-
-<CodeExample>
-
-```bash
-# dev.env
-PLATFORM_API_BASE_URL=http://platform-server:8085
-```
-
-</CodeExample>
-
-Hagamos algunas adiciones al archivo `server.js` para poder hacer polling a Anchor Platform para los pagos que esperamos.
-
-<CodeExample>
-
-```js
-// server.js
-...
-/*
- * Fetch the transaction data from the Platform API
- *
- * Production systems should have proper retry mechanisms.
- */
-async function getPlatformTransaction(transactionId) {
-  let response = await fetch(`${process.env.PLATFORM_SERVER}/transactions/${transactionId}`)
-  if (response.status != 200) {
-    throw `unexpected status code: ${response.status}`;
-  }
-  return await response.json();
-}
-
-(async () => {
-  while (true) {
-    await new Promise(r => setTimeout(r, 2000));
-    let requestPromises;
-    for (const transactionId in transactionMemos) {
-      requestPromises.push(getPlatformTransaction(transactionId))
-    }
-    let transactions = await new Promise.all(requestPromises);
-    for (const transaction in transactions) {
-      // assuming all requests were successful
-      if (transaction.status == "pending_anchor") {
-        // initiate off-chain delivery of funds
-        console.log(`received payment for transaction ${transaction.id}`);
-      }
-    }
-  }
-})()
-```
-
-</CodeExample>
-
-## Implementación completa de ejemplo
-
-Stellar proporciona una implementación de servidor de negocio de ejemplo para SEP-24. Está dividida en dos partes: 1) una UI web, accesible para el usuario final; y 2) una implementación backend, usada para obtener y enviar actualizaciones desde/hacia Anchor Platform.
-
-El código para la UI web puede encontrarse [aquí][sep-24-ref-ui]
-
-El código para el backend forma parte de Anchor Platform, y está disponible como un [submódulo][sep-24-ref].
-
-[sep-1]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[sep-38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep24-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#info
-[anchor-platform-image]: https://hub.docker.com/r/stellar/anchor-platform
-[docker-compose]: https://docs.docker.com/compose/
-[minikube]: https://minikube.sigs.k8s.io/docs/
-[kubernetes]: https://kubernetes.io/
-[nginx]: https://www.nginx.com/
-[ap-default-values]: https://github.com/stellar/java-stellar-anchor-sdk/blob/develop/platform/src/main/resources/config/anchor-config-default-values.yaml
-[stellar-demo-wallet]: https://demo-wallet.stellar.org
-[stellar-lab]: https://lab.stellar.org/
-[postgresql]: https://www.postgresql.org/
-[aurora-postgresql]: https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraPostgreSQL.html
-[h2]: https://www.h2database.com/html/main.html
-[sqlite]: https://www.sqlite.org/index.html
-[flyway]: https://documentation.red-gate.com/fd/redgate-flyway-documentation-138346877.html
-[sep-24-ref-ui]: https://github.com/stellar/sep24-reference-ui
-[sep-24-ref]: https://github.com/stellar/java-stellar-anchor-sdk/tree/develop/kotlin-reference-server
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/faq.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/faq.mdx
deleted file mode 100644
index 25814b8d99..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/faq.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Preguntas frecuentes
-sidebar_position: 50
----
-
-### ¿Cómo usar los JWT?
-
-Como parte del flujo, una vez que un usuario realiza una solicitud, por ejemplo, una solicitud interactiva de retiro/deposito, será procesada por la Anchor Platform y enviada a tu servicio. La Anchor Platform realizará una llamada `GET` a `<configured url>?token=<jwt token>`.
-
-Este token JWT contendrá:
-
-1. `exp` es el tiempo de expiración del token. Debes verificar que el token proporcionado no haya expirado.
-2. `sub` es la cuenta asociada con esta transacción. Puede usarse para identificar la cuenta de usuario. Ten en cuenta que este valor puede ser diferente de la cuenta que se usará para recibir/enviar fondos.
-3. `jti` es el hash de la transacción.
-4. `data` es la carga extra establecida por el usuario. Siempre contendrá el `asset` Stellar que desea depositar o retirar. Si lo proporciona el cliente, también contendrá la `amount` que el usuario desea transaccionar, el `client_domain` de la billetera verificado durante la autenticación SEP-10, y el `client_name` (definido como 'name' en la configuración de [clients] si se proporciona), y la preferencia de idioma `lang` del usuario.
-
-### ¿Cómo proporcionar las tarifas?
-
-Actualmente, se recomienda proporcionar las tarifas/tasas de cambio en el iFrame/vista web de tu aplicación.
-
-El estándar [SEP-24] proporciona un endpoint `/fee` para que las empresas establezcan tarifas estáticas para sus transacciones. Sin embargo, la Anchor Platform actualmente no lo soporta.
-
-:::note
-
-El endpoint /fee será descontinuado en el futuro.
-
-:::
-
-### ¿Cómo identificar la cuenta de usuario?
-
-Debes usar el campo `sub` del token JWT. Para billeteras custodiales, este valor estará en el formato `account:memo`. Usa el memo para identificar al usuario. Para billeteras no custodiales, simplemente usa el valor `sub` en sí, que será igual a la cuenta del usuario.
-
-### ¿Cómo identificar la billetera?
-
-Utiliza el atributo `data.client_domain` dentro del token JWT. En presencia de la configuración de [clients], el token JWT incorporará adicionalmente el campo `data.client_name`, permitiendo identificar la billetera.
-
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[clients]: ../sep10/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx
deleted file mode 100644
index 1d49dc0607..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/getting-started.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía te llevará a través de la configuración e integración con la Plataforma Anchor para construir un servicio de acceso y salida compatible con [SEP-24][sep-24], el protocolo estandarizado del ecosistema para depósitos y retiradas alojados.
-
-Al aprovechar el soporte de SEP-24 de la Plataforma Anchor, las empresas hacen que su servicio de acceso y salida esté disponible como una experiencia dentro de la aplicación a través de aplicaciones basadas en Stellar, como wallets e intercambios, ampliando su alcance y conectándose con usuarios mediante las aplicaciones que ya utilizan.
-
-Antes de continuar con esta sección, asegúrate de haber [instalado][installation-ap] ya la Plataforma Anchor y de haber configurado las funciones necesarias requeridas por SEP-24: [SEP-1 (Archivo de Información Stellar)][sep1-ap], [SEP-10 (Autenticación Stellar)][sep10-ap] y [SEP-45 (Autenticación Web Stellar para cuenta de contrato)][sep45-ap].
-
-## La experiencia básica del usuario
-
-La experiencia completa del cliente para un depósito y un retiro es algo así:
-
-1. El cliente abre la aplicación wallet SEP-24 de su elección
-2. El cliente selecciona un activo para depositar y el wallet encuentra un anchor (los clientes también podrían elegir el anchor específico)
-3. Una vez que el wallet se autentica con el anchor, el cliente empieza a ingresar su información KYC y de la transacción que el anchor solicita
-4. El wallet proporciona instrucciones, y el cliente deposita moneda fiat real con el anchor (por ejemplo, realiza una transferencia bancaria)
-5. Una vez que el wallet recibe el depósito, el cliente recibe el activo tokenizado en la red Stellar desde la cuenta de distribución del anchor
-
-El cliente puede entonces usar el activo digital en la red Stellar para remesas, pagos, comercio, almacenamiento de valor u otro caso de uso no listado aquí. En una fecha posterior, el cliente podría decidir retirar sus activos de la red Stellar, lo cual sería algo así:
-
-1. El cliente abre su aplicación wallet
-2. El cliente selecciona el activo para retirar y el wallet encuentra el anchor
-3. Después de autenticarse con el anchor, el wallet abre la URL interactiva proporcionada y permite al cliente ingresar la información de la transacción (KYC ya ha sido recopilado)
-4. Después de pedir la aprobación del cliente, el wallet envía la cantidad especificada del balance del activo del cliente a la cuenta de distribución del anchor en Stellar
-5. Una vez que el anchor recibe el pago, el cliente recibe los fondos retirados mediante transferencia bancaria.
-
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/integration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/integration.mdx
deleted file mode 100644
index 5452b713ba..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/integration.mdx
+++ /dev/null
@@ -1,927 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-import Security from "../../admin-guide/component/security/security.mdx";
-import UsingApiKey from "../../admin-guide/component/security/api_key.mdx";
-import UsingJwt from "../../admin-guide/component/security/jwt.mdx";
-import Rpc from "../../admin-guide/component/rpc/rpc.mdx";
-import RpcRequest from "../../admin-guide/component/rpc/request.mdx";
-import RpcResponse from "../../admin-guide/component/rpc/response.mdx";
-import RpcError from "../../admin-guide/component/rpc/error.mdx";
-import Observer from "../../admin-guide/component/observer/observer.mdx";
-
-Uno de los principales puntos de interacción con la Anchor Platform es notificar a la Anchor Platform sobre eventos relacionados con la transacción.
-
-En general, querrás proporcionar actualizaciones para los siguientes eventos:
-
-- Tu negocio está procesando la información KYC proporcionada por el usuario
-- Tu negocio está listo para recibir fondos del usuario
-- Tu negocio ha recibido fondos del usuario
-- Tu negocio ha enviado fondos al usuario
-- Tu negocio ha procesado un reembolso para la transacción del usuario
-- Tu negocio experimentó un error inesperado
-
-Esto se hace haciendo solicitudes JSON-RPC al endpoint de la API de la Platform. Las solicitudes JSON-RPC te permiten actualizar el estado de la transacción. Para mover la transacción a un estado específico, es necesario hacer la solicitud JSON-RPC correspondiente y pasar los datos requeridos por este método RPC.
-
-La API JSON-RPC de la Anchor Platform está diseñada para notificar a la plataforma sobre cambios en el estado de la transacción. Por lo tanto, la API será llamada cada vez que un usuario o el anchor realice alguna acción que progrese el estado de la transacción en el flujo.
-
-La comunicación desde la Anchor Platform sobre actualizaciones de transacciones, actualizaciones de clientes y creación de cotizaciones se maneja a través del servicio de eventos. Esta es una característica opcional que debe configurarse por separado de la integración SEP-6. Para más información, consulta [Gestión de Eventos][event-handling].
-
-Puedes conocer más sobre el flujo y estados de la transacción en el [documento del protocolo SEP-24][sep-24]
-
-## Callbacks
-
-La Anchor Platform depende del servidor de negocio para proporcionar y almacenar información sobre cotizaciones.
-
-### Cotizaciones y Tarifas
-
-Para admitir el intercambio de activos no equivalentes, la Anchor Platform expone una API compatible con SEP-38 para proporcionar cotizaciones para el intercambio. La API de cotización se utiliza para proporcionar al usuario la cantidad esperada del activo que recibirá a cambio del activo que está enviando. La API de cotización también se usa para mostrar al usuario las tarifas esperadas para la transacción. Por lo tanto, tu servidor de negocio debe implementar la [API de tarifas][rate-callback] para proporcionar cotizaciones a la Anchor Platform.
-
-## Seguridad de la API de la Platform
-
-<Security />
-
-### Uso de API Key
-
-<UsingApiKey />
-
-### Uso de JWT
-
-<UsingJwt />
-
-## Realizando solicitudes JSON-RPC
-
-<Rpc />
-
-### Solicitud JSON-RPC
-
-<RpcRequest />
-
-### Respuesta JSON-RPC
-
-<RpcResponse />
-
-### Códigos de error
-
-<RpcError />
-
-## Actualizando la transacción de depósito vía JSON-RPC
-
-El diagrama del flujo de depósito SEP-24 define la secuencia/reglas de la transición del estado de la transacción y un conjunto de métodos JSON-RPC que deben ser llamados para cambiar ese estado. No puedes definir el estado que deseas establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene atributos requeridos, la Anchor Platform devolverá un error y no cambiará el estado de la transacción.
-
-[![flujo de depósito SEP24](/assets/ap/sep24-deposit-flow-diagram.png)](/assets/ap/sep24-deposit-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en un estado de error o ha expirado.
-
-:::
-
-### Listo para recibir fondos
-
-El primer paso del flujo de depósito después de iniciar el depósito es recopilar KYC. Generalmente se hace en la aplicación web, pero también puede ser proporcionado opcionalmente por la aplicación de billetera, usando [SEP-9]. Una vez que se recopila el KYC necesario, se debe hacer una solicitud JSON-RPC `request_offchain_funds`.
-
-<CodeExample>
-
-```json
-// request-offchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_offchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request offchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es la cantidad que el usuario debe enviar al negocio.
-- `amount_out` es la cantidad que el usuario recibirá.
-- `fee_details` es el monto total de las tarifas cobradas por el negocio.
-- `asset` es parte del campo `amount_x` y está en formato SEP-38. En este ejemplo, está establecido en USD, asumiendo que el usuario realizó una transferencia bancaria al sistema usando USD.
-
-La información sobre las cantidades (entrada/salida/fee) es necesaria si quieres mover la transacción desde el estado `incomplete` a `pending_user_transfer_start`. Si el estado de la transacción cambia de `pending_anchor` a `pending_user_transfer_start`, puedes omitir la definición de cantidades.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-offchain-funds.json
-```
-
-</CodeExample>
-
-:::tip
-
-Cuando el proceso de KYC es largo (por ejemplo, verificación de ID), se recomienda primero establecer el estado de la transacción a `pending_anchor` usando la solicitud JSON-RPC `notify_interactive_flow_completed`. Esto indicará al usuario que el KYC está siendo procesado.
-
-:::
-
-### Procesando información KYC
-
-:::tip
-
-Este paso es opcional. La mayoría de los negocios no lo utilizan. Puedes omitirlo e ir al [siguiente paso](#funds-received).
-
-Se recomienda usar este estado cuando la verificación KYC pueda necesitar realizarse de manera asíncrona.
-
-:::
-
-**Debes** especificar los campos `amount_x`.
-
-<CodeExample>
-
-```json
-// kyc-in-process.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_interactive_flow_completed",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Interactive flow completed.",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh kyc-in-process.json
-```
-
-</CodeExample>
-
-### Fondos recibidos
-
-Si se recibieron fondos offchain, querrás proporcionar información actualizada de la transacción.
-
-<CodeExample>
-
-```json
-// offchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds received",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `funds_received_at` es la fecha y hora de recepción de los fondos
-- `external_transaction_id` es el ID de la transacción en la red externa
-
-Los campos de monto son opcionales. Si se omiten, se tomarán los valores de las solicitudes JSON-RPC previas.
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-received.json
-```
-
-</CodeExample>
-
-### Esperando fondos del usuario
-
-En el mundo real, el proceso de confirmación de transferencia puede tomar tiempo. En tales casos, las transacciones deben establecerse a un nuevo estado que indique que se ha recibido la confirmación de la transferencia, pero los fondos aún no se han recibido.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Enviando fondos onchain
-
-Luego, envía una transacción en la red Stellar para cumplir con la solicitud del usuario. Después de completar la transacción, es necesario enviar la solicitud JSON-RPC `notify_onchain_funds_sent` para notificar al usuario que los fondos fueron enviados con éxito.
-
-<CodeExample>
-
-```json
-// onchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds sent",
-      "stellar_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `stellar_transaction_id` es el ID de la transacción en la red Stellar de la transferencia
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-sent.json
-```
-
-</CodeExample>
-
-Después de esta solicitud JSON-RPC, la transacción pasará al estado `completed`.
-
-### Pendiente de confianza
-
-Este estado debe establecerse si un pago requiere una trustline de activo que no fue configurada por el usuario. Hay dos maneras en que la transacción puede pasar al estado `pending_trust`. La primera es cuando el servidor de negocio detecta que la trustline no está configurada. La segunda es cuando el negocio mismo detecta que falta la trustline y quiere notificar al usuario que debe configurarla. Para mover la transacción al estado `pending_trust`, es necesario hacer la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// request-trust.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_trust",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine not configured"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-trust.json
-```
-
-</CodeExample>
-
-:::info
-
-El servidor de negocio verifica periódicamente si la trustline fue configurada. Si fue así, puede enviar un pago y cambiar el estado de la transacción a `pending_stellar`.
-
-:::
-
-### Trust Set
-
-Este estado debe establecerse si el negocio ha detectado si la trustline fue o no configurada por el usuario.
-
-<CodeExample>
-
-```json
-// trust-set.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_trust_set",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine set",
-      "success": "true"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- El flag `success` que define si la trustline fue o no configurada por el usuario
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh trust-set.json
-```
-
-</CodeExample>
-
-:::info
-
-Dependiendo del flag `success`, el estado de la transacción será cambiado a `pending_stellar` si la trustline fue configurada, o a `pending_anchor` si no fue así.
-
-:::
-
-### Enviando reembolso
-
-Existe la posibilidad de enviar fondos de regreso al usuario (reembolso). Puedes reembolsar la suma completa (reembolso total) o realizar varios reembolsos parciales. Además, si el usuario envió más dinero del esperado, puedes reembolsar una parte de la suma al usuario y enviar el resto como fondos onchain.
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::info
-
-Si la suma de los reembolsos es menor que `amount_in`, el estado de la transacción se establecerá en `pending_anchor`. Solo si la suma de los reembolsos es igual a `amount_in`, el estado de la transacción será `refunded`.
-
-:::
-
-### Reembolso pendiente
-
-Es similar a [Reembolso enviado](#refund-sent), pero maneja el caso cuando un reembolso ha sido enviado a la red externa pero aún no está confirmado. El estado de la transacción se establece en `pending_external`. Este es el estado que se establece al esperar que la red de Bitcoin u otra red de criptomonedas externa complete una transacción, o cuando se espera una transferencia bancaria.
-
-### Error en la transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, es necesario establecer el estado de la transacción a `error`. Puedes usar el campo mensaje para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario ha hecho una transferencia, debes hacer una recuperación de la transacción y luego puedes reintentar procesar la transacción o iniciar un reembolso.
-
-:::
-
-### Transacción expirada
-
-Tu negocio puede querer manejar transacciones abandonadas expirando aquellas que hayan permanecido inactivas por cierto período. Para lograr esto, verifica el estado de la transacción usando el endpoint `GET /transactions` y ordena los resultados por la marca de tiempo `user_action_required_by`. Si la marca de tiempo ha pasado, ejecuta manualmente la lógica apropiada, como expirar la transacción o iniciar un auto-reembolso, basado en el estado actual de la transacción. Por ejemplo, para expirar una transacción, el negocio debe cambiar el estado de la transacción a `expired`:
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no puede usarse después de que el usuario haya hecho una transferencia.
-
-:::
-
-### Transacción en espera
-
-En casos raros, puedes querer pausar la transacción actual y solicitar más información al usuario (después de que se haya recibido la transferencia). Esto podría usarse para casos de cumplimiento.
-
-<CodeExample>
-
-```json
-// transaction-hold.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_on_hold",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction is on hold. Please contact customer support to resolve the hold."
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-hold.json
-```
-
-</CodeExample>
-
-### Recuperación de transacción
-
-El estado de la transacción puede cambiarse de `error/expired` a `pending_anchor`. Después de la recuperación, puedes reembolsar los activos recibidos o continuar con el procesamiento de la transacción. Para recuperar una transacción, es necesario realizar la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-## Actualizando la transacción de retirada vía JSON-RPC
-
-Este diagrama define la secuencia/reglas de transición del estado de una transacción para el flujo de retirada SEP-24.
-
-[![flujo de retirada SEP24](/assets/ap/sep24-withdrawal-flow-diagram.png)](/assets/ap/sep24-withdrawal-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en un estado de error o ha expirado.
-
-:::
-
-Una vez que el flujo de depósito ha finalizado, implementar la retirada es sencillo. Algunas partes del flujo son similares y pueden reutilizarse.
-
-El punto de partida tanto para la retirada como para el depósito es el mismo.
-
-### Listo para recibir fondos
-
-Similar al depósito, el siguiente paso es notificar al usuario que el anchor está listo para recibir fondos. Sin embargo, dado que tu servicio recibirá transacciones a través de la red Stellar, la actualización se verá diferente.
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "iso4217:USD"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `memo` Valor del memo para adjuntar a la transacción
-- `memo_type` Tipo de memo que el anchor debería adjuntar a la transacción
-- `destination_account` Cuenta destino
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-:::tip
-
-Establecer `memo`, `memo_type` y `destination_account` es opcional.
-
-Si la integración con un custodio externo está habilitada, la Anchor Platform puede generar `memo`, `memo_type` y `destination_address` si se elige el tipo de generador de información de depósito correspondiente. También puedes proporcionar `memo` y `memo_type` en la solicitud como se muestra arriba. Ten en cuenta que el memo debe ser único, esto es lo que ayuda a asociar las transacciones Stellar con las transacciones SEP.
-
-Si tu negocio administra los activos, la Anchor Platform puede generar los memos por ti. Cuando el estado cambia a `pending_user_transfer_start`, la Anchor Platform establece automáticamente el `memo` y `memo_type` (solo si no están incluidos en la solicitud).
-
-:::
-
-:::note
-
-La cuenta Stellar que se usará para recibir fondos debe estar configurada.
-
-:::
-
-### Procesando información KYC
-
-Este paso es opcional y es similar a [Procesar información KYC](#processing-kyc-information) del flujo de depósito.
-
-### Fondos recibidos
-
-Si se recibieron fondos onchain, necesitas proporcionar los montos y cambiar el estado de la transacción a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método será llamado automáticamente por el observador de pagos Stellar cuando detecte que se han recibido fondos onchain.
-
-:::
-
-### Monto actualizado
-
-Si se recibieron fondos onchain, pero por alguna razón `amount_in` difiere del especificado en el flujo interactivo (`amount_expected`), puedes actualizar `amount_out` y `fee_details` para que correspondan al `amount_in` real. El estado de la transacción en este caso no cambiará y será igual a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// amounts-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_amounts_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Amounts updated",
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh amounts-updated.json
-```
-
-</CodeExample>
-
-:::note
-
-Solo `amount_out` y `fee_details` pueden actualizarse usando esta solicitud JSON-RPC, y no necesitas especificar los activos de las cantidades.
-
-:::
-
-### Fondos offchain enviados
-
-Para completar la transacción y cambiar su estado a `completed`, necesitas hacer la solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Fondos offchain disponibles
-
-Puedes mover el estado de la transacción a `pending_user_transfer_complete` si se enviaron fondos offchain y está listo para que el usuario/beneficiario los recoja.
-
-<CodeExample>
-
-```json
-// offchain-funds-available.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_available",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds available",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-available.json
-```
-
-</CodeExample>
-
-### Fondos offchain pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago ha sido enviado a una red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, necesitas correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Reembolso enviado
-
-La lógica de reembolso funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Reembolso enviado](#refund-sent) del flujo de depósito.
-
-### Error en la transacción
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Error en la transacción](#transaction-error) del flujo de depósito.
-
-### Transacción expirada
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Transacción expirada](#expired-transaction) del flujo de depósito.
-
-### Transacción en espera
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Transacción en espera](#on-hold-transaction) del flujo de depósito.
-
-### Recuperación de transacción
-
-Funciona de la misma manera que para el flujo de depósito. Para más detalles, consulta [Recuperación de transacción](#transaction-recovery) del flujo de depósito.
-
-## Rastreando transacciones Stellar
-
-<Observer />
-
-[sep-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md
-[sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
-[event-handling]: ../../admin-guide/events/README.mdx
-[rate-callback]: ../../api-reference/callbacks/README.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
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
deleted file mode 100644
index b088a875d5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx
+++ /dev/null
@@ -1,122 +0,0 @@
----
-title: Configurar un servidor de producción
-sidebar_position: 60
----
-
-Una vez que el servidor de prueba esté en vivo y hayas probado tanto los flujos de depósito como de retiro, es hora de comenzar con el despliegue real conectado a KYC real y proveedores reales de sistemas bancarios. Antes de utilizar cualquier API bancaria, es fundamental que realices una auditoría completa de seguridad en el sistema para asegurarte de que no existan vulnerabilidades.
-
-## Desplegar un entorno seguro
-
-Asegúrate de mantener el servidor de prueba activo y despliega el sistema de producción (mainnet) en un entorno separado. Tener dos despliegues te permite validar nuevas funciones en la testnet antes de moverlas al despliegue final de producción. También puedes tener un tercer entorno de preproducción si hay un equipo grande trabajando en esta base de código y/o habrá muchas incorporaciones que deban ser probadas internamente antes de compartirlas con otras instituciones.
-
-Para cambiar a la red pública (mainnet) de Stellar, solo tienes que cambiar la [frase de paso](../../../../networks/README.mdx#network-passphrases) de la red (para autenticar las solicitudes) y la [URL de Horizon](https://horizon.stellar.org/).
-
-Puedes copiar tus configuraciones de desarrollo existentes para crear una configuración de producción.
-
-Primero, necesitas cambiar tu archivo de información (`stellar.toml`):
-
-<CodeExample>
-
-```toml
-# stellar.toml
-NETWORK_PASSPHRASE = "Public Global Stellar Network ; September 2015"
-```
-
-</CodeExample>
-
-Luego, cambia tu configuración de la plataforma Anchor en el archivo `production.env`:
-
-### Para conexión al servidor Horizon:
-
-<CodeExample>
-
-```bash
-# production.env STELLAR_NETWORK_NETWORK="Public"
-STELLAR_NETWORK_HORIZON_URL="https://horizon.stellar.org"
-```
-
-</CodeExample>
-
-### Para conexión al servidor RPC de Stellar:
-
-<CodeExample>
-
-```bash
-# production.env STELLAR_NETWORK_NETWORK="Public"
-STELLAR_NETWORK_RPC_URL="https://mainnet.sorobanrpc.com"
-```
-
-</CodeExample>
-
-## Conectar con KYC real
-
-La mayoría de las anchors necesitan recopilar información de [Conoce a tu Cliente](https://es.wikipedia.org/wiki/Conoce_a_tu_cliente) para cumplir con las regulaciones locales antes de aceptar depósitos y retiros. El flujo de KYC usualmente consiste en un formulario simple que recopila información relevante sobre el usuario, como nombre, correo electrónico, dirección, edad y número de identificación emitido por el gobierno.
-
-Cómo manejes el KYC depende de ti: existen muchos servicios que ofrecen soluciones KYC mediante APIs y iframes, validan los datos ingresados y sincronizan con bases de datos gubernamentales para verificar requisitos. Cada jurisdicción tiene requisitos específicos de KYC, y varían de una a otra, por lo que es mejor encontrar un proveedor de KYC específico para el país que satisfaga tus necesidades.
-
-Algunos países requieren diferentes campos de KYC según la cantidad a depositar o retirar. Si ese es tu caso y necesitas adaptar tus formularios KYC en función del monto de depósito o retiro, simplemente añade un campo de cantidad antes del formulario KYC y asegúrate de que los campos KYC se actualicen según ese valor.
-
-La información KYC debe estar vinculada a la sesión creada mediante [Autenticación web de Stellar](../sep10/README.mdx) y, en consecuencia, al usuario, por lo que solo necesitas solicitarla una vez. Después de completar el primer flujo de KYC, un usuario no debería tener que ingresar la información nuevamente.
-
-Asegúrate de que los mensajes de error y validación sean claros e incluyan instrucciones sobre qué hacer después para garantizar una buena experiencia de usuario y aumentar la tasa de conversión de KYC. También debes localizar los mensajes según el idioma y la ubicación del usuario.
-
-## Autocompletar el formulario KYC
-
-Autocompletar el formulario KYC es una excelente forma de reducir la fricción para comenzar a usar una anchor, y las wallets suelen proporcionar un conjunto de campos comúnmente usados en el ecosistema. En resumen, la anchor puede mostrar el formulario KYC con los valores del usuario que fueron enviados previamente por la wallet en los endpoints `/transactions/deposit/interactive` y `/transactions/withdraw/interactive`.
-
-Todos los campos de [SEP-9](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md) pueden ser enviados por las wallets en los endpoints mencionados, pero los más comunes son: correo electrónico, nombre, apellido y número de teléfono. Además, deberías permitir que los campos autocompletados sean editables, ya que el usuario podría haber ingresado un nombre diferente durante el proceso de registro en la wallet y podría querer editarlo antes de finalizar el proceso KYC de la anchor.
-
-Todos los datos de SEP-9 enviados desde la wallet forman parte del [JWT interactivo](./faq.mdx#how-to-use-jwts) enviado por la plataforma Anchor.
-
-## Conectarse a sistemas bancarios reales
-
-Se espera que los emisores de tokens respaldados por fiat gestionen una reserva completa. Eso significa que existe una relación 1:1 entre los tokens en la red Stellar y el dinero en el banco. Dado que cada token fiat en Stellar está respaldado y puede canjearse por un activo real subyacente, los emisores de tokens respaldados por fiat necesitan conectarse a sistemas bancarios reales para validar depósitos de usuarios (a través de transferencias bancarias, pagos con tarjeta de crédito, etc.). y para completar los retiros de usuarios (generalmente mediante transferencias bancarias). Si eres una anchor que acepta depósitos y retiros de un token emitido por otra organización, seguirás un proceso similar.
-
-Para obtener (e identificar) una transferencia de usuario, los emisores suelen utilizar una de dos aproximaciones:
-
-- Sondeo de API: esta opción consiste en consultar la API bancaria mediante un trabajo cron para verificar el estado actualizado de la lista de transferencias recibidas y enviadas desde la cuenta bancaria del emisor. Una vez que el sistema confirma una nueva transacción e identifica que está relacionada con un depósito específico, puede enviar los fondos digitales a la cuenta de ese usuario.
-- Webhook: no todos los sistemas bancarios admiten esta opción, pero es la opción más ligera en términos de lógica de backend. En este enfoque, el banco envía proactivamente una notificación al endpoint del emisor una vez que recibe una nueva transferencia, actualizando esa información en la base de datos del emisor. El emisor puede entonces asociar esa transacción a un depósito en proceso existente y validar que el usuario pueda recibir sus fondos digitales.
-
-Hay muchas formas de identificar que una transferencia bancaria específica corresponde a un depósito concreto (y, en consecuencia, a un usuario). Algunos bancos (y países) tienen infraestructuras que permiten la creación de una cuenta bancaria única por transferencia; otros requieren que los usuarios añadan un parámetro de identificación a sus transferencias. Algunos bancos proporcionan el número de identificación del usuario en la información de la transacción para que los emisores puedan correlacionarlo con la información proporcionada en el formulario KYC.
-
-Asegúrate de realizar una auditoría de seguridad completa en tus sistemas cuando las conexiones a sistemas bancarios estén activas. Algunos bancos proporcionan una API de prueba que puede usarse para desarrollo y despliegue en entornos de testnet o preproducción, lo que te permite probar y auditar la base de código antes de pasar a una integración bancaria final lista para producción. Para mayor seguridad, algunas anchors prefieren añadir un paso manual final antes de aprobar transferencias de retiro. En términos de experiencia de usuario, esta aprobación manual es aceptable siempre que los tiempos de espera estén alineados con las expectativas del usuario, lo que generalmente significa que no sean mayores a un par de horas.
-
-## Probar casos límite
-
-Una vez que tu aplicación esté completamente funcional, es recomendable probar diferentes escenarios y casos extremos para asegurarte de que el sistema se comporta como se espera. Aquí tienes una lista de sugerencias de pruebas que deberían cubrir una gran cantidad de casos extremos de la aplicación:
-
-### Pruebas generales
-
-- Prueba la usabilidad del flujo interactivo
-- Prueba la interfaz usando información de distintas localidades y revisa el contenido traducido, incluyendo mensajes de error, respuestas, formatos de fecha y formatos de número.
-
-### Pruebas KYC
-
-- Verifica que KYC aparezca con una nueva SK de wallet
-- Verifica que KYC no acepte entradas con formato incorrecto y que los mensajes de error sean comprensibles
-- Verifica que puedas usar la misma información KYC (correo, teléfono, nombre de usuario, etc.) múltiples veces
-- Verifica que puedas realizar el proceso KYC varias veces con la misma SK Stellar.
-
-### Prueba interactiva
-
-- Verifica que el flujo de depósito funcione y que los sistemas bancarios estén operativos
-- Verifica que no puedas realizar un retiro con un valor mayor al saldo actual
-- Verifica que el flujo de retiro funcione y que los sistemas bancarios estén operativos
-
-### Pruebas de seguridad
-
-- Asegúrate de que los endpoints de la plataforma estén protegidos
-
-## Pulido e internacionalización
-
-Soportar dos idiomas (inglés y el idioma del país de la moneda fiat) permite a los usuarios tener una experiencia fluida al navegar por las pantallas, y apoya a instituciones internacionales (como wallets) que necesitan probar el producto antes de comenzar nuevas integraciones.
-
-Puedes soportar múltiples idiomas en tu aplicación web usando el parámetro `Accept-Language` de los encabezados http para localizar el contenido, y permitiendo que los usuarios cambien eso de forma sencilla (por ejemplo, un icono de bandera en la barra superior). Si una wallet específica no envía el parámetro del encabezado, recomendamos mostrar al usuario una pantalla de selección de idioma al inicio de los procesos de depósito y retiro. Una vez que un usuario elige un idioma, puedes almacenar su selección para que solo necesites preguntarles una vez. Además de localizar el texto, asegúrate de revisar el formato de números, fechas, etc.
-
-Tener un grupo de testers beta es una excelente forma de verificar si hay casos límite que necesiten ajuste, y para confirmar que el sistema funciona bien con una variedad de entradas de usuario. Puedes realizar pruebas beta usando una etapa de lanzamiento suave antes de comenzar a invertir esfuerzo en marketing y distribución. Documentar el proceso de pruebas con capturas de pantalla y videos es muy útil para auditorías de seguridad futuras, y da claridad y confianza a socios nuevos y usuarios potenciales sobre el producto.
-
-## Conectarse a wallets
-
-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.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/README.mdx
deleted file mode 100644
index 1182d8e05b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Pagos Transfronterizos (SEP-31)
-sidebar_position: 100
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-31 permite que las wallets y/o exchanges interactúen con el conjunto existente de servicios de envío de Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/configuration.mdx
deleted file mode 100644
index 44a12873c7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/configuration.mdx
+++ /dev/null
@@ -1,344 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-## Modificar un archivo Stellar Info
-
-Comencemos modificando nuestro archivo `stellar.toml` creado [anteriormente][sep1-ap]. Las billeteras deben saber que tu negocio soporta la funcionalidad SEP-31, y también necesitan conocer todas las monedas que admites.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-DIRECT_PAYMENT_SERVER = "http://localhost:8080/sep31"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que deberás crear otro archivo para el despliegue en producción que utilice la frase de paso de la red pública, las URLs de servicio de producción, tus cuentas de distribución mainnet y la clave de firma, así como las cuentas emisoras mainnet de los activos que utiliza tu servicio.
-
-## Habilitar Pagos Transfronterizos
-
-Ahora estás listo para habilitar los pagos transfronterizos en la API SEP-31. Especifica lo siguiente en tu archivo `dev.assets.yaml`.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep31:
-      enabled: true
-      quotes_supported: true
-      quotes_required: true
-      receive:
-        min_amount: 0
-        max_amount: 10000
-        methods:
-          - ACH
-```
-
-</CodeExample>
-
-La información proporcionada en los objetos `sep31` y `send` corresponde estrechamente a la información que se expondrá a la aplicación de billetera mediante el endpoint SEP-31 [`GET /info`][sep31-get-info]. La plataforma Anchor también usa esta información para validar las solicitudes hechas a tu servicio. `sep31.fields.transaction` debe dejarse vacío y será eliminado en una futura versión, pero puedes ajustar los valores `send.min_amount` y `send.max_amount` según los límites de tu servicio.
-
-Las propiedades `sep31.quotes_supported` y `sep31.quotes_required` determinan si las organizaciones que envían pueden y están obligadas a solicitar una tasa de cambio mediante el endpoint [SEP-38 `POST /quote`][sep38-post-quote]. Casi todos los remitentes prefieren este enfoque para poder comunicar la tasa a sus clientes antes de proceder.
-
-Agrega la siguiente variable a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP31_ENABLED=true
-```
-
-</CodeExample>
-
-¡Los remitentes ahora deberían poder descubrir, autenticarse e iniciar transacciones con tu servicio! Ejecuta el siguiente comando para iniciar la plataforma Anchor.
-
-<CodeExample>
-
-```bash
-docker compose up
-```
-
-</CodeExample>
-
-Verifica que tu API esté activa.
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep31/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente.
-
-<CodeExample>
-
-```json
-{
-  "receive": {
-    "USDC": {
-      "enabled": true,
-      "quotes_supported": true,
-      "quotes_required": true,
-      "min_amount": 0,
-      "max_amount": 10000,
-      "fields": {
-        "transaction": {}
-      }
-    }
-  }
-}
-```
-
-</CodeExample>
-
-## Habilitar la API KYC para Clientes
-
-Los negocios necesitan recopilar y validar información KYC de los clientes para quienes están facilitando transacciones. Los clientes determinan qué información KYC debe recopilarse y envían esa información a través de una API SEP-12 KYC alojada por la plataforma Anchor, pero la plataforma Anchor nunca almacena información personal identificable (PII). En cambio, la plataforma reenvía las solicitudes de los clientes al servidor del negocio y devuelve las respuestas del negocio al cliente, actuando como un servidor proxy.
-
-Consulta la [especificación de la API KYC de la plataforma Anchor][platform-api-kyc] para obtener detalles sobre los endpoints que deben implementarse en el servidor de tu negocio.
-
-Para poner esta API a disposición de los clientes, añadamos la URL del servicio a nuestro archivo Stellar Info.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-KYC_SERVER = "http://localhost:8080/sep12"
-```
-
-</CodeExample>
-
-Habilitémosla también en nuestro entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP12_ENABLED=true
-```
-
-</CodeExample>
-
-Finalmente, debemos definir los tipos de clientes de tu negocio. Cada tipo de cliente requiere un conjunto diferente de información KYC. Por ejemplo, puedes ofrecer tu servicio de pagos transfronterizos en dos jurisdicciones regulatorias distintas, por lo que los clientes en diferentes jurisdicciones tienen diferentes requisitos KYC y serían representados usando diferentes tipos.
-
-:::info
-
-Actualmente, los tipos de clientes deben ser mutuamente exclusivos, es decir, un cliente no puede ser más de un tipo.
-
-Esta limitación existe porque la plataforma Anchor no puede validar si un cliente está aprobado para un tipo específico de transacción, como enviar una cantidad grande. Solo puede validar que un cliente está aprobado para uno de los tipos de clientes definidos. Esta limitación será eliminada en una futura versión.
-
-:::
-
-En esta guía, solo tendremos dos tipos: un tipo de cliente remitente y un tipo de cliente receptor. Actualmente, nuestros tipos de clientes están definidos en nuestra configuración de activos, pero esto cambiará en una futura versión.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-sep31:
-  sep12:
-    sender:
-      types:
-        sep31-sender:
-          description: customers sending to recipients
-    receiver:
-      types:
-        sep31-receiver:
-          description: customers receiving from senders
-```
-
-</CodeExample>
-
-Volvamos a hacer ping al endpoint info para verificar. Después de `docker compose up`, ejecuta el siguiente comando:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep31/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente:
-
-<CodeExample>
-
-```json
-{
-  "receive": {
-    "USDC": {
-      "enabled": true,
-      "quotes_supported": true,
-      "quotes_required": true,
-      "min_amount": 0,
-      "max_amount": 10000,
-      "fields": {
-        "transaction": {}
-      }
-    }
-  }
-}
-```
-
-</CodeExample>
-
-## Habilitar la API RFQ
-
-Los negocios necesitan proporcionar a sus contrapartes del lado del envío una API [Rate][get-rates-api] para comprobar las tasas de cambio que están ofreciendo entre el activo on-chain utilizado para la liquidación y el activo fiat utilizado para pagar al destinatario. Si la tasa es competitiva, los remitentes también deben poder solicitar un compromiso con la tasa actualmente ofrecida por el negocio por un corto período de tiempo.
-
-La plataforma Anchor provee la [API SEP-38 RFQ][sep38] para los remitentes con este propósito.
-
-Para poner esta API a disposición de los clientes, añadamos la URL del servicio a nuestro archivo Stellar Info.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-DIRECT_PAYMENT_SERVER = "http://localhost:8080/sep31"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-KYC_SERVER = "http://localhost:8080/sep12"
-QUOTE_SERVER = "http://localhost:8080/sep38"
-```
-
-</CodeExample>
-
-Habilitémosla también en nuestro entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP38_ENABLED=true
-```
-
-</CodeExample>
-
-También necesitamos habilitar USDC para usarla en esta API, así como agregar un activo off-chain con el que pueda intercambiarse.
-
-<CodeExample>
-
-```yaml
-# dev.assets.yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep31:
-      enabled: true
-      quotes_supported: true
-      quotes_required: true
-      receive:
-        min_amount: 0
-        max_amount: 10000
-        methods:
-          - ACH
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - iso4217:BRL
-      country_codes:
-        - BR
-  - id: iso421:BRL
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-      country_codes:
-        - BR
-      significant_decimals: 2
-      buy_delivery_methods:
-        - name: PIX
-          description: Have BRL sent directly to your bank account.
-```
-
-</CodeExample>
-
-¡Probemos que tu API RFQ esté activa! Tras `docker compose up`:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/sep38/info | jq
-```
-
-</CodeExample>
-
-Deberías obtener lo siguiente:
-
-<CodeExample>
-
-```json
-{
-  "assets": [
-    {
-      "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-    },
-    {
-      "asset": "iso4217:BRL",
-      "country_codes": ["BR"],
-      "buy_delivery_methods": [
-        {
-          "name": "PIX",
-          "description": "Have BRL sent directly to your bank account."
-        }
-      ]
-    }
-  ]
-}
-```
-
-</CodeExample>
-
-## Configurar la Autenticación para la API de Callback
-
-Así como tu negocio necesitará hacer solicitudes a la plataforma Anchor, la plataforma Anchor necesitará hacer solicitudes a tu negocio. Agreguemos autenticación a estas solicitudes también.
-
-<CodeExample>
-
-```bash
-# dev.env
-CALLBACK_API_BASE_URL=http://server:8081
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-SECRET_CALLBACK_API_AUTH_SECRET=<your jwt encryption key>
-```
-
-</CodeExample>
-
-`CALLBACK_API_BASE_URL` utiliza `server` en lugar de `localhost` como host porque la plataforma Anchor realizará solicitudes a tu servidor de negocio desde dentro de la red local creada por docker compose. Al configurar tu servicio en un entorno de staging o producción, asegúrate de actualizar las URLs de tu servicio.
-
-Definiremos el servidor que implementa los endpoints definidos en la API de Callback en la sección siguiente.
-
-[sep31-get-info]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#get-info
-[sep1-ap]: ../sep1/README.mdx
-[get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
-[sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[sep38-post-quote]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md#post-quote
-[platform-api-kyc]: ../../api-reference/callbacks/get-customer.api.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx
deleted file mode 100644
index 5cc1bde41b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/getting-started.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía te llevará a través de la configuración e integración con la Anchor Platform con el propósito de desarrollar un servicio receptor de pagos transfronterizos compatible con [SEP-31][sep-31], el protocolo estandarizado del ecosistema para pagos transfronterizos.
-
-Aprovechando el soporte de la Anchor Platform para SEP-31, las empresas hacen que su servicio sea compatible con el conjunto existente de servicios emisores de Stellar.
-
-:::info
-
-A medida que mejoramos la documentación, partes de esta guía relevantes para otros casos de uso podrían ser trasladadas a sus propias secciones.
-
-:::
-
-Antes de continuar con esta sección, asegúrate de haber [instalado][installation-ap] la Anchor Platform y configurado las funciones necesarias requeridas por SEP-31: [SEP-1 (Archivo de Información de Stellar)][sep1-ap], [SEP-10 (Autenticación de Stellar)][sep10-ap] y [SEP-45 (Autenticación Web de Stellar para cuenta de contrato)][sep45-ap].
-
-[sep-31]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/integration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/integration.mdx
deleted file mode 100644
index b5923b9441..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep31/integration.mdx
+++ /dev/null
@@ -1,618 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-Integrarse con la Plataforma Anchor para facilitar pagos transfronterizos implica implementar, al menos, lo siguiente:
-
-- Los endpoints de la API KYC [`GET /customer`][get-customer] y [`PUT /customer`][put-customer] para solicitar y recopilar los datos KYC de los clientes
-- El endpoint RFQ de la API [`GET /rate`][get-rate] para proporcionar las tasas FX entre los activos on y off-chain soportados
-- Solicitudes `GET /transactions` para obtener actualizaciones sobre el estado de las transacciones en la Plataforma Anchor (documentación próximamente)
-- Solicitudes [`JSON-RPC`][json-rpc-methods] para actualizar los estados de las transacciones de la Plataforma Anchor
-
-También pueden requerirse los siguientes según tu caso de uso:
-
-- [`DELETE /customer`][delete-customer] si tu negocio desea o debe permitir que los remitentes soliciten la eliminación de datos de clientes
-
-## Crear un Servidor de Negocio
-
-Primero, vamos a crear un servidor de negocio y añadirlo al archivo docker compose.
-
-<CodeExample>
-
-```yaml
-version: "3.8"
-
-services:
-  sep-server:
-    image: stellar/anchor-platform:latest
-    command: --sep-server
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-    ports:
-      - "8080:8080"
-    depends_on:
-      - db
-  platform-server:
-    image: stellar/anchor-platform:latest
-    command: --platform-server
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-    ports:
-      - "8085:8085"
-    depends_on:
-      - db
-
-  server:
-    build: .
-    ports:
-      - "8081:8081"
-    env_file:
-      - ./dev.env
-  db:
-    image: postgres:14
-    ports:
-      - "5432:5432"
-    env_file:
-      - ./dev.env
-```
-
-</CodeExample>
-
-Luego, crea un servidor web sencillo usando tu lenguaje de programación preferido y un `Dockerfile` que inicie el servidor. `docker compose up` debería iniciar correctamente los tres servicios.
-
-Esta guía no ofrece una implementación ejemplo de los endpoints, pero puedes encontrar más información sobre los esquemas de solicitud y respuesta en la [Referencia API de la Plataforma Anchor][ap-api], y las secciones a continuación ampliarán conceptos importantes para comprender al implementar los endpoints.
-
-## Endpoints de Callback de Cliente
-
-La Plataforma Anchor nunca almacena la información personal identificable (PII) de tus clientes, sino que actúa como servidor proxy entre las aplicaciones cliente y tu negocio, reenviando solicitudes y respuestas a la otra parte. Actualmente, las solicitudes y respuestas son casi idénticas a las definidas en la [especificación API SEP-12 KYC][sep12].
-
-### Identificación de Clientes
-
-Los clientes pueden identificarse usando dos enfoques.
-
-El primer enfoque utiliza una cuenta Stellar y un memo. Al usar la Plataforma Anchor para facilitar pagos transfronterizos, la organización remitente utiliza su propia cuenta Stellar, la que se usa para autenticarse via [Autenticación Stellar SEP-10][ap-sep10], para registrar clientes con tu negocio. Los memos se utilizan para distinguir clientes únicos que provienen de la misma organización remitente.
-
-El segundo enfoque usa IDs de clientes generados por tu servicio. Por ejemplo, si una organización remitente está registrando un cliente, tu negocio recibirá una solicitud `PUT /customer` como la siguiente:
-
-<CodeExample>
-
-```json
-{
-  "account": "GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47",
-  "memo": "780284017",
-  "type": "sep31-sender",
-  "first_name": "John",
-  "last_name": "Doe",
-  "email": "johndoe@example.com"
-}
-```
-
-</CodeExample>
-
-En este ejemplo, la clave pública `GDJ...X47` identifica a la organización remitente, y el memo `780284017` identifica al cliente. Los memos suelen ser enteros de 64 bits, pero también pueden ser otros tipos de datos, así que deben guardarse como cadenas. Como respuesta, tu negocio debe devolver un ID de cliente.
-
-<CodeExample>
-
-```json
-{
-  "id": "fb5ddc93-1d5d-490d-ba5f-2c361cea41f7"
-}
-```
-
-</CodeExample>
-
-Tu servidor de negocio puede usar cualquier identificador para los clientes mientras sea una cadena.
-
-Tras registrar a un cliente, la organización remitente puede usar cualquier enfoque para verificar el estado del cliente. Por ejemplo, podrías recibir una solicitud `GET /customer` como la siguiente:
-
-<CodeExample>
-
-```
-/customer?account=GDJUOFZGW5WYBK4GIETCSSM6MTTIJ4SUMCQITPTLUWMQ6B4UIX2IEX47&memo=780284017&type=sep31-sender
-```
-
-</CodeExample>
-
-O la organización remitente podría usar el identificador que devolviste cuando registraron originalmente al cliente.
-
-<CodeExample>
-
-```
-/customer?id=fb5ddc93-1d5d-490d-ba5f-2c361cea41f7&type=sep31-sender
-```
-
-</CodeExample>
-
-Tu negocio debe mantener un mapeo entre la cuenta y memo usados para registrar al cliente originalmente, el ID que devuelves en la respuesta, y los datos KYC proporcionados. En futuras iteraciones de la Plataforma Anchor, podríamos mantener este mapeo por ti para que solo tengas que trabajar con los IDs que generes.
-
-### Tipos de Clientes
-
-Tu negocio probablemente requiere diferentes conjuntos de información KYC según el tipo de cliente. Puedes definir las etiquetas para cada tipo de cliente en tu archivo `dev.assets.yaml`, y tus organizaciones remitentes deberán usar la etiqueta correcta al registrar o consultar el estado de los clientes.
-
-En solicitudes `PUT /customer`, debes usar el tipo proporcionado para evaluar si el remitente ha entregado todos los campos requeridos. En solicitudes `GET /customer`, debes usar el tipo para determinar el estado del cliente.
-
-### Prueba con la Demo Wallet
-
-Puedes probar tu implementación con la [Demo Wallet Stellar][demo-wallet] siguiendo los pasos a continuación.
-
-1. Selecciona "Generar par de claves para nueva cuenta"
-2. Selecciona "Crear cuenta"
-3. Selecciona "Agregar activo" e ingresa el código del activo y el dominio principal de la Plataforma Anchor, `localhost:8080`
-4. Selecciona "Agregar línea de confianza"
-5. Fondea tu cuenta con un saldo del activo
-6. Selecciona "SEP-31 Enviar" en el menú desplegable
-
-Deberías ver que la demo wallet encuentra las URLs de tu servicio, se autentica y verifica qué campos KYC necesita recopilar. Luego debería mostrar un formulario para introducir los detalles KYC del remitente y receptor.
-
-[![demo wallet después de iniciar una transacción](/assets/ap/anchor-platform-sep31-demo-wallet-widget.png)](/assets/ap/anchor-platform-sep31-demo-wallet-widget.png)
-
-Una vez que hayas ingresado la información solicitada, la enviará a la Plataforma Anchor, que a su vez la enviará a tu servidor de negocio. Una vez que la demo wallet tiene los IDs de clientes que generaste, iniciará una transacción que debería fallar.
-
-## Endpoint de Callback de Tasas
-
-Una vez que la organización remitente haya registrado a los clientes involucrados en la transacción, necesitará solicitar una cotización, o tasa FX, a tu negocio. La Plataforma Anchor solicita esta información a tu servidor de negocio usando el endpoint [`GET /rate`][get-rate].
-
-### Cotizaciones Firmes vs Indicativas
-
-Las solicitudes de cotización tendrán un parámetro `type` que será [`indicative`][indicative] o [`firm`][firm]. Si `type=firm`, tu respuesta debe incluir el campo `id` y `expires_at` (fecha y hora) y reservar la liquidez necesaria para cumplir esta cotización hasta que expire. Si `type=indicative`, no debes devolver los campos `id` ni `expires_at` porque la tasa proporcionada no se usará en una transacción.
-
-Ten en cuenta que el cliente puede solicitar que la cotización expire después de una fecha y hora específica usando el parámetro `expires_after`. Tu negocio debe respetar esta solicitud devolviendo un valor `expires_at` igual o posterior a la fecha y hora solicitadas, o rechazar la solicitud con una respuesta 400 Bad Request, que se reenviará al cliente.
-
-### Uso del ID del Cliente
-
-Las solicitudes pueden incluir un parámetro `client_id` que identifica a la organización remitente que solicita la tasa. Puedes usar este parámetro para cumplir con los términos comerciales acordados con esa organización remitente, como ofrecer tarifas con descuento. El `client_id` puede no estar presente en solicitudes indicativas, en cuyo caso debe devolverse tu precio de mercado. Actualmente, el `client_id` siempre será la clave pública Stellar que la organización remitente usó para autenticarse con la Plataforma Anchor.
-
-### Métodos de Entrega
-
-Es común que las tarifas y comisiones del negocio difieran según las vías de pago usadas para enviar fondos al destinatario. Si tus métodos de entrega están configurados en tu archivo `asset.yaml`, los clientes siempre indicarán la vía de pago que desean que use tu negocio para solicitudes de cotizaciones firmes.
-
-Dado que este endpoint se utiliza actualmente solo para pagar remesas en activos off-chain, se usará el `buy_delivery_method`. Si este endpoint se usa en otros flujos de transacciones como depósitos SEP-24, podría pasarse también el `sell_delivery_method` para negocios que soporten esos tipos de transacciones.
-
-## Obteniendo actualizaciones del estado de las transacciones
-
-Para facilitar pagos transfronterizos, necesitarás detectar cuándo una organización remitente ha enviado a tu negocio un pago on-chain y determinar a qué transacción corresponde ese pago.
-
-La forma más sencilla es ejecutar el Stellar Observer, que detectará estos pagos y actualizará el registro de la transacción correspondiente con información sobre el pago. Tu negocio podrá luego detectar estas actualizaciones consultando periódicamente el endpoint `GET /transactions` de la API de la Plataforma.
-
-### Ejecutando el Stellar Observer
-
-El Stellar Observer monitorea el libro mayor de Stellar para detectar pagos hechos a tu(s) cuenta(s) y actualiza los registros de transacciones correspondientes con la información del pago on-chain. Para ejecutar el observer, añade lo siguiente a tu archivo docker compose.
-
-<CodeExample>
-
-```yaml
-services:
-  ...
-  observer:
-    image: stellar/anchor-platform:latest
-    command: --stellar-observer
-    env_file:
-      - ./dev.env
-    volumes:
-      - ./config:/home
-```
-
-</CodeExample>
-
-### Consultar pagos recibidos
-
-El Stellar Observer realiza solicitudes JSON-RPC a la API de Plataforma cuando detecta que se recibieron pagos para transacciones iniciadas por organizaciones remitentes, actualizando así la fecha y hora `transfer_received_at` de la transacción.
-
-Tu negocio debe consultar periódicamente la API de Plataforma en `GET /transactions` para detectar estas actualizaciones. Puedes consultar el siguiente ejemplo:
-
-<CodeExample>
-
-```bash
-curl http://localhost:8080/transactions?sep=31&order_by=transfer_received_at&order=desc
-```
-
-</CodeExample>
-
-La respuesta incluirá una lista de transacciones de pagos transfronterizos iniciadas por organizaciones remitentes. Esta lista estará ordenada según el momento en que se recibió el pago para esa transacción. Para cada transacción devuelta, tu negocio debe verificar si ya se detectó el pago para esa transacción. Si es así, has detectado todos los pagos realizados a tu(s) cuenta(s).
-
-## Actualizando Transacciones via JSON-RPC
-
-El diagrama del flujo SEP-31 define la secuencia/reglas para la transición de estado de la transacción y un conjunto de métodos JSON-RPC que deben llamarse para cambiar ese estado. No puedes definir el estado que deseas establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene los atributos requeridos, la Plataforma Anchor devolverá un error y no cambiará el estado de la transacción.
-
-[![flujo sep31](/assets/ap/sep31-transition-diagram.png)](/assets/ap/sep31-transition-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el flujo más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> significan que la transacción está en estado de error o ha expirado.
-
-:::
-
-Puedes crear una [plantilla][sep24-integration-make-json-rpc-request] para realizar solicitudes JSON-RPC a la Plataforma Anchor.
-
-Este capítulo también incluye información sobre el formato de la [solicitud][sep24-integration-rpc-request]/[respuesta][sep24-integration-rpc-response] y los [códigos de error][sep24-integration-error-codes] que puede devolver la Plataforma Anchor.
-
-### Listo para recibir fondos
-
-Las transacciones SEP-31 deberían comenzar con el estado `pending_receiver`. Para solicitar fondos del Anchor remitente, el Anchor receptor debe cambiar el estado de la transacción a `pending_sender` mediante la siguiente solicitud RPC:
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-El estado de la transacción cambiará a `pending_sender`.
-
-### Fondos recibidos
-
-Si el Anchor remitente ha enviado los fondos, el Anchor receptor debe cambiar el estado de la transacción a `pending_receiver` mediante la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-El estado de la transacción cambiará a `pending_receiver`.
-
-### Fondos offchain enviados
-
-Para completar la transacción y cambiar su estado a `completed`, debes hacer una solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Fondos offchain pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago ha sido enviado a una red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Verificación de información del cliente
-
-En algunos casos, el Anchor receptor podría necesitar solicitar información actualizada al Anchor remitente. Por ejemplo, el banco informa al Anchor receptor que el nombre del cliente receptor es incorrecto o le falta una inicial intermedia. Dado que esta información fue enviada mediante SEP-12, la transacción debe pasar al estado `pending_customer_info_update` hasta que el Anchor remitente haga otra solicitud SEP-12 `PUT /customer` para actualizarla. El Anchor remitente puede verificar qué campos se deben actualizar haciendo una solicitud SEP-12 `GET /customer` que incluya el id o los parámetros cuenta y memo. El Anchor receptor debe responder con un estado `NEEDS_INFO` e incluir `last_name` en los campos descritos.
-
-Después que el Anchor remitente haga una solicitud SEP-12 `PUT /customer`, llama al método JSON-RPC `notify_customer_info_updated` para actualizar el estado de la transacción. Además, llama a este método cada vez que el estado SEP-12 de un cliente cambie, por ejemplo al pasar de `NEEDS_INFO` a `PROCESSING` cuando la información del cliente está siendo validada. Esto asegura que cualquier cliente configurado con una URL de callback sea notificado del estado más reciente del cliente, permitiendo que el cliente solicite al usuario actualizar su información.
-
-<CodeExample>
-
-```json
-// notify-customer-info-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_customer_info_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Customer info updated",
-      "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
-      "customer_type": "sep31-receiver" // or sep31-sender
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh notify-customer-info-updated.json
-```
-
-</CodeExample>
-
-### Reembolso enviado
-
-Existe la posibilidad de reenviar todos los fondos al `Sending Anchor` (reembolso). Debes reembolsar la suma completa (reembolso total).
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "amount_fee": {
-          "amount": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::note
-
-No puedes realizar múltiples reembolsos en el flujo SEP-31. Por esta razón, el monto a reembolsar más la comisión deben sumar `amount_in`. De lo contrario, recibirás un error.
-
-:::
-
-### Error de transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, es obligatorio establecer el estado de la transacción a `error`. Puedes usar el campo mensaje para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario ha realizado una transferencia, deberías hacer una recuperación de la transacción para luego volver a intentar procesarla o iniciar un reembolso.
-
-:::
-
-### Transacción expirada
-
-Tu negocio puede querer expirar aquellas transacciones abandonadas por el usuario después de un tiempo. Es buena práctica limpiar las transacciones inactivas en estado `incomplete`. Para ello, simplemente cambia el estado de la transacción a `expired`.
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no puede usarse después que el usuario haya hecho una transferencia.
-
-:::
-
-### Recuperación de transacción
-
-El estado de la transacción puede cambiar de `error/expired` a `pending-anchor`. Después de la recuperación, puedes reembolsar los activos recibidos o continuar procesando la transacción. Para recuperar la transacción, es necesario hacer la siguiente solicitud JSON-RPC:
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para ejecutar esto, debes correr:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-### Configuración
-
-Puedes habilitar estos tipos de transacciones actualizando la configuración de tu archivo `assets.yaml`:
-
-<CodeExample>
-
-```yaml
-items:
-  - ...
-    sep31:
-      quotes_required: false
-```
-
-</CodeExample>
-
-[ap-api]: ../../README.mdx
-[ap-sep10]: ../sep10/README.mdx
-[sep12]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md
-[demo-wallet]: https://demo-wallet.stellar.org
-[indicative]: https://www.investopedia.com/terms/i/indicativequote.asp
-[firm]: https://www.investopedia.com/terms/f/firmquote.asp
-[get-customer]: ../../api-reference/callbacks/get-customer.api.mdx
-[put-customer]: ../../api-reference/callbacks/put-customer.api.mdx
-[get-rate]: ../../api-reference/callbacks/get-rates.api.mdx
-[put-customer-callback]: ../../api-reference/callbacks/put-customer.api.mdx
-[delete-customer]: ../../api-reference/callbacks/del-customer.api.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
-[sep24-integration-make-json-rpc-request]: ../sep24/integration.mdx#making-json-rpc-requests
-[sep24-integration-rpc-request]: ../sep24/integration.mdx#json-rpc-request
-[sep24-integration-rpc-response]: ../sep24/integration.mdx#json-rpc-response
-[sep24-integration-error-codes]: ../sep24/integration.mdx#error-codes
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep45/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep45/README.mdx
deleted file mode 100644
index b7519a5326..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep45/README.mdx
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: Autenticación Stellar para Cuentas de Contrato (SEP-45)
-sidebar_position: 70
----
-
-## Descripción general
-
-SEP-45 (Autenticación Web Stellar para Cuentas de Contrato) permite a las aplicaciones de billeteras inteligentes crear sesiones autenticadas con anclas Stellar demostrando control sobre una cuenta de contrato (`C...`). Una vez autenticadas, las billeteras reciben un Token Web JSON (JWT) que utilizan en solicitudes posteriores a los servicios estandarizados del ancla.
-
-Para la especificación completa, consulta [SEP-0045: Autenticación Web Stellar para Cuentas de Contrato][sep-45].
-
-La Plataforma Anchor implementa SEP-45 con soporte para:
-
-- **Flujo Desafío/Respuesta**: GET `/sep45/auth` para solicitar entradas de autorización, POST `/sep45/auth` para validar y recibir un JWT
-- **Autenticación de Cuenta de Contrato**: Soporte para cuentas de contrato (`C...`) usando entradas de autorización Soroban
-- **Simulación de Transacciones**: Simulación automática de transacciones para verificar entradas de autorización
-- **Múltiples Dominios Principales**: Soporte para múltiples dominios y patrones comodín
-
-:::info
-
-**SEP-45 vs SEP-10**: SEP-45 no reemplaza a SEP-10. SEP-45 soporta cuentas de contrato (`C...`), mientras que SEP-10 soporta cuentas clásicas (`G...`) y cuentas multiplexadas (`M...`). Los servicios que deseen soportar todos los tipos de cuentas deben implementar ambos SEPs.
-
-:::
-
-## Flujo Típico de Autenticación
-
-1. El **Cliente** solicita un desafío único al **Servidor**
-2. El **Cliente** verifica y firma el desafío
-3. El **Cliente** envía el desafío firmado al **Servidor**
-4. El **Servidor** verifica el desafío y responde con un token de sesión JWT
-
-Se proporciona una implementación del contrato SEP-45 en el [repositorio Platform Anchor][sep-45-contract]. Una instancia de este contrato está desplegada en `CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX` en testnet.
-
-## Activar SEP-45
-
-SEP-45 requiere integración con Stellar RPC para simular transacciones. La Plataforma Anchor puede conectarse al servidor Stellar RPC de tu elección. Puedes usar un proveedor público de Stellar RPC, o ejecutar el tuyo propio. Una lista de proveedores públicos se encuentra [aquí][rpc-providers].
-
-Para activar SEP-45, configura las siguientes variables de entorno en tu archivo `dev.env`.
-
-<CodeExample>
-
-```bash
-# dev.env
-STELLAR_NETWORK_TYPE=rpc
-STELLAR_NETWORK_RPC_URL=https://soroban-testnet.stellar.org
-SEP45_ENABLED=true
-SEP45_HOME_DOMAINS=localhost:8080
-SEP45_WEB_AUTH_CONTRACT_ID="CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP45_JWT_SECRET="a secret encryption key"
-```
-
-</CodeExample>
-
-### Configuración requerida (si está habilitado)
-
-| Variable                     | Por defecto | Descripción                                                                                                                                                                                             |
-| ---------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `STELLAR_NETWORK_TYPE`       | _Requerido_ | Debe establecerse en `rpc` para SEP-45. Esto habilita el modo RPC para la Plataforma Anchor.                                                                                                            |
-| `STELLAR_NETWORK_RPC_URL`    | _Requerido_ | La URL del servidor Stellar RPC utilizado para simular transacciones. Puedes usar un proveedor público o ejecutar el tuyo propio. Una lista de proveedores públicos se encuentra [aquí][rpc-providers]. |
-| `SEP45_ENABLED`              | `false`     | Establece en `true` para habilitar la autenticación SEP-45                                                                                                                                              |
-| `SEP45_HOME_DOMAINS`         | _Requerido_ | Lista de dominios principales (separados por comas). Soporta patrones comodín como `*.stellar.org`. El `home_domain` debe coincidir con el host donde se sirve tu archivo `stellar.toml`.               |
-| `SEP45_WEB_AUTH_CONTRACT_ID` | _Requerido_ | El ID del contrato del contrato SEP-45. Este contrato debe implementar la función `web_auth_verify` como se describe en la [especificación SEP-45][sep-45].                                             |
-| `SECRET_SEP10_SIGNING_SEED`  | _Requerido_ | La clave privada correspondiente a la `SIGNING_KEY` en tu archivo `stellar.toml`. SEP-45 usa la misma clave de firma que SEP-10. Usada para firmar desafíos de autenticación.                           |
-| `SECRET_SEP45_JWT_SECRET`    | _Requerido_ | La clave de cifrado usada para firmar y verificar los tokens JWT emitidos a las billeteras autenticadas.                                                                                                |
-
-:::important
-
-- **Requisito RPC**: SEP-45 requiere Stellar RPC para simular transacciones. Debes establecer `STELLAR_NETWORK_TYPE=rpc` y proporcionar una `STELLAR_NETWORK_RPC_URL` válida.
-- **ID del Contrato**: El `SEP45_WEB_AUTH_CONTRACT_ID` debe coincidir con el contrato desplegado en la dirección especificada en el campo `WEB_AUTH_CONTRACT_ID` de tu archivo `stellar.toml`.
-- **Clave de Firma**: La `SIGNING_KEY` en tu archivo `stellar.toml` debe ser la clave pública derivada de `SECRET_SEP10_SIGNING_SEED`.
-
-:::
-
-### Configuración Opcional
-
-<CodeExample>
-
-```bash
-# dev.env
-# Optional: Specify web_auth_domain (default: first home_domain if only one is specified)
-SEP45_WEB_AUTH_DOMAIN=localhost:8080
-
-# Optional: Challenge timeout in seconds (default: 900)
-SEP45_AUTH_TIMEOUT=900
-
-# Optional: JWT token timeout in seconds (default: 86400 = 24 hours)
-SEP45_JWT_TIMEOUT=86400
-```
-
-</CodeExample>
-
-| Variable                | Por defecto                                                           | Descripción                                                                                                                                                                          |
-| ----------------------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `SEP45_WEB_AUTH_DOMAIN` | Primer `home_domain` si solo se especifica uno, de lo contrario vacío | La propiedad `web_auth_domain` usada en las respuestas de SEP-45. Requerido si tienes múltiples `home_domains` o usas patrones comodín. Debe coincidir con el host del servidor SEP. |
-| `SEP45_AUTH_TIMEOUT`    | `900`                                                                 | Tiempo en segundos que un desafío permanece válido. Los clientes deben firmar y enviar las entradas de autorización dentro de esta ventana.                                          |
-| `SEP45_JWT_TIMEOUT`     | `86400`                                                               | Tiempo en segundos que un token JWT emitido permanece válido. Después de la expiración, los clientes deben reautenticarse.                                                           |
-
-:::tip
-
-**Múltiples Dominios Principales**: Si especificas múltiples `home_domains` (ej., `ap.stellar.org,*.sdp.stellar.org`), también debes establecer `SEP45_WEB_AUTH_DOMAIN` para especificar qué dominio aloja el endpoint de autenticación.
-
-:::
-
-## Configurar stellar.toml
-
-Actualiza tu archivo `stellar.toml` para publicitar soporte para SEP-45. Las billeteras descubren tu endpoint de autenticación a través de este archivo.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here (public key from SECRET_SEP10_SIGNING_SEED)"
-WEB_AUTH_FOR_CONTRACTS_ENDPOINT = "http://localhost:8080/sep45/auth"
-WEB_AUTH_CONTRACT_ID = "CD3LA6RKF5D2FN2R2L57MWXLBRSEWWENE74YBEFZSSGNJRJGICFGQXMX"
-```
-
-</CodeExample>
-
-Estos campos deben coincidir con las opciones de configuración establecidas en la sección [Activar SEP-45](#enable-sep-45) arriba.
-
-`WEB_AUTH_FOR_CONTRACTS_ENDPOINT` - La URL donde se ejecuta el servicio de autenticación. Esta es la URL que los clientes usarán para autenticarse con el ancla. El endpoint debe soportar:
-
-- `GET <WEB_AUTH_FOR_CONTRACTS_ENDPOINT>` - Solicitar entradas de autorización
-- `POST <WEB_AUTH_FOR_CONTRACTS_ENDPOINT>` - Intercambiar entradas de autorización firmadas por un JWT de sesión
-
-`WEB_AUTH_CONTRACT_ID` - El ID del contrato del contrato SEP-45. Este es el contrato que se usará para construir el desafío. El contrato debe implementar la función `web_auth_verify` como se describe en la [especificación SEP-45][sep-45]. Esto debe coincidir con `SEP45_WEB_AUTH_CONTRACT_ID`.
-
-:::important
-
-- **`SIGNING_KEY`**: Debe ser la clave pública derivada de `SECRET_SEP10_SIGNING_SEED`
-- **`WEB_AUTH_FOR_CONTRACTS_ENDPOINT`**: Usa `https://` en producción. El path `/sep45/auth` es el endpoint estándar SEP-45.
-- **Coincidencia de Host**: El host en `WEB_AUTH_FOR_CONTRACTS_ENDPOINT` debe coincidir con uno de tus `SEP45_HOME_DOMAINS` (o el `SEP45_WEB_AUTH_DOMAIN` si se especifica).
-
-:::
-
-[sep1-ap]: ../sep1/README.mdx
-[sep-45]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md
-[sep-45-contract]: https://github.com/stellar/anchor-platform/tree/main/soroban/contracts/web-auth
-[rpc-providers]: /docs/data/apis/rpc/providers
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/README.mdx
deleted file mode 100644
index 5be772ba82..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Depósitos y Retiros Programáticos (SEP-6)
-sidebar_position: 80
----
-
-import DocCardList from "@theme/DocCardList";
-
-SEP-6 permite una forma en la que las billeteras y/o exchanges interactúan con un anchor en nombre de los usuarios, sin que el usuario necesite interactuar directamente con la rampa de entrada y salida.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/configuration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/configuration.mdx
deleted file mode 100644
index 02cd493916..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/configuration.mdx
+++ /dev/null
@@ -1,254 +0,0 @@
----
-title: Configuración
-sidebar_position: 20
----
-
-# Configuración
-
-Para habilitar los depósitos y retiradas SEP-6, la Anchor Platform debe estar configurada para hacer lo siguiente:
-
-- Proporcionar las URLs de servicio necesarias para los endpoints SEP-6, 12 y 38 en el archivo `stellar.toml`
-- Proporcionar información sobre los activos on y off-chain, así como las vías de pago admitidas por tu negocio vía los endpoints `/info` de SEP-6 y SEP-38
-- Admitir los endpoints y callbacks necesarios para solicitar información KYC y proporcionar tasas de cambio
-
-## Habilitar Depósitos y Retiradas Programáticos
-
-Agrega las siguientes variables a tu archivo de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_ENABLED=true
-SEP12_ENABLED=true
-SEP38_ENABLED=true
-```
-
-</CodeExample>
-
-### Modificar un Archivo Stellar Info
-
-Vamos a modificar el archivo `stellar.toml` creado [antes][sep1-ap]. Las billeteras necesitan saber que tu negocio admite la funcionalidad SEP-6, y también necesitan conocer todos los activos Stellar que admites.
-
-<CodeExample>
-
-```toml
-# dev.stellar.toml
-ACCOUNTS = ["add your public keys for your distribution accounts here"]
-SIGNING_KEY = "add your signing key here"
-NETWORK_PASSPHRASE = "Test SDF Network ; September 2015"
-
-TRANSFER_SERVER = "http://localhost:8080/sep6"
-WEB_AUTH_ENDPOINT = "http://localhost:8080/auth"
-KYC_SERVER = "http://localhost:8080/sep12"
-ANCHOR_QUOTE_SERVER = "http://localhost:8080/sep38"
-
-# Add support for USDC
-[[CURRENCIES]]
-code = "USDC"
-issuer = "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-status = "test"
-is_asset_anchored = false
-desc = "USD Coin issued by Circle"
-
-[DOCUMENTATION]
-ORG_NAME = "Your organization"
-ORG_URL = "Your website"
-ORG_DESCRIPTION = "A description of your organization"
-```
-
-</CodeExample>
-
-Ten en cuenta que necesitarás crear otro archivo para tu despliegue en producción que use la clave de paso de la red pública, tus URLs de servicio de producción, tus cuentas de distribución y claves de firma de Mainnet, así como las cuentas emissoras de activos de Mainnet que utiliza tu servicio.
-
-### Modificar el Archivo de Configuración de Activos
-
-Ahora estás listo para especificar lo siguiente en tu archivo `dev.assets.yaml`, y cambiar los valores según tu caso de uso. Este archivo de activos de ejemplo habilita el soporte para USDC de Circle y un fiat USD para depositar y retirar.
-
-Los métodos especificados en las secciones `sep38` son métodos que el endpoint SEP-38 [`GET /info`][sep38] expondrá.
-
-Los métodos especificados en las secciones `deposit` y `withdraw` son los métodos que el endpoint SEP-6 [`GET /info`][sep-6] expondrá. Los métodos listados deben coincidir con los métodos definidos en la sección SEP-38 del archivo.
-
-También ten en cuenta que los activos fiat, aquellos con `schema: iso4217`, no necesitan especificar los objetos de configuración `sep6_enabled`, `deposit` o `withdraw`. De manera similar, los activos Stellar, aquellos con `schema: stellar`, no necesitan especificar los objetos de configuración `sep38.sell_delivery_methods` o `sep38.buy_delivery_methods`.
-
-<CodeExample>
-
-```yaml
-items:
-  - id: stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-    distribution_account: GBLSAHONJRODSFTLOV225NZR4LHICH63RIFQTQN37L5CRTR2IMQ5UEK7
-    significant_decimals: 2
-    sep6:
-      enabled: true
-      deposit:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - ACH
-      withdraw:
-        enabled: true
-        min_amount: 0
-        max_amount: 10
-        methods:
-          - ACH
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - iso4217:USD
-  - id: iso4217:USD
-    significant_decimals: 2
-    sep38:
-      enabled: true
-      exchangeable_assets:
-        - stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5
-      buy_delivery_methods:
-        - name: ACH
-          description: ACH debits for US bank accounts
-      sell_delivery_methods:
-        - name: ACH
-          description: ACH credit for US bank accounts
-```
-
-</CodeExample>
-
-### Administrar Cuentas de Distribución
-
-Ten en cuenta que el ejemplo anterior lista un atributo `distribution_account` para la entrada USDC. Si se especifica, esta cuenta será proporcionada junto con un memo único y generado aleatoriamente por transacción a los clientes como la dirección a la cual enviar fondos para transacciones de retirada. El memo de la transacción es cómo tú o la Anchor Platform harán coincidir los fondos recibidos con un registro de transacción en la base de datos de Anchor Platform.
-
-Si no dispones de tu propia cuenta Stellar y en su lugar usas un tercero que te proporciona una cuenta Stellar y memo para recibir fondos en tu nombre, como un exchange o custodio, debes omitir el campo `distribution_account` de tu archivo de configuración de activos. En su lugar, deberás proporcionar la cuenta Stellar y memo que desees usar para recibir fondos mediante una solicitud al Anchor Platform [`request_onchain_funds`][request-onchain-funds] para cada transacción.
-
-Para configurar la Anchor Platform para esperar que la cuenta Stellar y memo se proporcionen vía API en lugar de configurarse vía archivo de activos, especifica la siguiente variable de entorno.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=none
-```
-
-</CodeExample>
-
-### Habilitar Callbacks al Servidor del Negocio
-
-Los negocios necesitan recolectar y validar la información KYC de los clientes para quienes están facilitando transacciones. Los clientes preguntan a tu negocio qué información KYC debe recopilarse y envían esa información mediante la API KYC SEP-12 alojada por la Anchor Platform, pero la Anchor Platform nunca almacena información de identificación personal (PII). En su lugar, reenvía las solicitudes de los clientes al servidor del negocio, y devuelve las respuestas del negocio al cliente, actuando como un servidor proxy.
-
-Además, los negocios deben proporcionar a los clientes una API [Rates][get-rates-api] para consultar las tasas de cambio que están ofreciendo entre los activos onchain y offchain admitidos por el negocio. Si la tasa es competitiva, los clientes también deben poder solicitar un compromiso con la tasa actualmente ofrecida por el negocio por un corto período de tiempo. De manera similar a la API KYC, la Anchor Platform realiza solicitudes a tu servidor empresarial para obtener tasas de cambio y cotizaciones y las devuelve a los clientes.
-
-Para habilitar estas solicitudes a tu servidor empresarial, primero necesitarás agregar tu servidor al archivo docker compose. Luego, para admitir solicitudes a tu servidor empresarial desde la Anchor Platform, necesitas habilitar callbacks.
-
-<CodeExample>
-
-```bash
-# dev.env
-CALLBACK_API_BASE_URL=http://business-server:3000/callbacks
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
-SECRET_CALLBACK_API_AUTH_SECRET="a secret used to sign JWTs"
-```
-
-</CodeExample>
-
-Lo anterior indica a la Anchor Platform que incluya un [JWT][how-to-use-jwt], firmado con el secreto configurado, en el encabezado `Authorization` de las solicitudes realizadas a `/callbacks/<callback endpoint>` para que tu servidor pueda autenticar a la Anchor Platform antes de procesar las solicitudes.
-
-Consulta la [API KYC][platform-api-kyc] y la [API de Tasas][get-rates-api] para detalles sobre los endpoints que deben implementarse en tu servidor empresarial.
-
-### Configuración Opcional Adicional
-
-`more_info_url` es una URL opcional proporcionada por tu servidor empresarial para que las aplicaciones de billeteras muestren información sobre transacciones iniciadas previamente. Esta URL es usada típicamente por las billeteras en sus vistas de historial de transacciones, y tu negocio puede especificar la información que se mostrará sobre la transacción.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP6_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-```
-
-</CodeExample>
-
-Los negocios pueden establecer un plazo para las acciones del usuario en las transacciones usando el campo `user_action_required_by`. Para ejemplos, consulta los [Métodos JSON-RPC][json-rpc-methods]. Además, el parámetro `initial_user_deadline_seconds` establece un tiempo predeterminado (en segundos) que el usuario tiene para actuar antes de que la transacción pase al estado `EXPIRED`.
-
-<CodeExample>
-
-```bash
-# dev.env
-SEP6_INITIAL_USER_DEADLINE_SECONDS=1209600
-```
-
-</CodeExample>
-
-## Probar con la Demo Wallet
-
-Las billeteras ahora deberían poder descubrir, autenticarse e iniciar transacciones con tu servicio. Tu proyecto y archivos fuente deberían verse ahora algo así.
-
-<CodeExample>
-
-```
-├── dev.env
-├── docker-compose.yaml
-├── config
-│   ├── dev.assets.yaml
-│   ├── dev.stellar.toml
-```
-
-</CodeExample>
-
-Tu entorno ahora debería verse algo parecido a lo siguiente.
-
-<CodeExample>
-
-```bash
-# dev.env
-ASSETS_TYPE=file
-ASSETS_VALUE=/home/dev.assets.yaml
-
-SEP1_ENABLED=true
-SEP1_TOML_TYPE=file
-SEP1_TOML_VALUE=/home/dev.stellar.toml
-
-SEP6_ENABLED=true
-SEP6_DEPOSIT_INFO_GENERATOR_TYPE=none
-SEP6_MORE_INFO_URL_BASE_URL=http://example.com
-SECRET_SEP6_MORE_INFO_URL_JWT_SECRET="your encryption key shared with your business server"
-
-SEP10_ENABLED=true
-SEP10_HOME_DOMAIN=localhost:8080
-SECRET_SEP10_SIGNING_SEED="a Stellar private key"
-SECRET_SEP10_JWT_SECRET="a secret used to sign JWTs"
-
-SEP12_ENABLED=true
-
-SEP38_ENABLED=true
-
-CALLBACK_API_BASE_URL=http://business-server:3000/callbacks
-CALLBACK_API_AUTH_TYPE=jwt
-CALLBACK_API_AUTH_JWT_EXPIRATION_MILLISECONDS=30000
-CALLBACK_API_AUTH_JWT_HTTP_HEADER=Authorization
-SECRET_CALLBACK_API_AUTH_SECRET="a secret used to sign JWTs"
-```
-
-</CodeExample>
-
-Para probar esto, ve a la [Stellar Demo Wallet][stellar-demo-wallet].
-
-Inicia una transacción de depósito haciendo lo siguiente:
-
-- Crear un nuevo par de claves
-- Haz clic en el botón "Add Asset" e ingresa
-  - el código del activo Stellar en tu archivo `stellar.toml`
-  - tu dominio principal, `localhost:8080`
-- Selecciona el desplegable y haz clic en "SEP-6 Deposit", luego haz clic en "Start"
-
-La demo wallet debería poder encontrar tu archivo `stellar.toml`, autenticarse usando el par de claves Stellar que acabas de crear e iniciar una transacción.
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[sep1-ap]: ../sep1/README.mdx
-[stellar-demo-wallet]: https://demo-wallet.stellar.org/
-[get-rates-api]: ../../api-reference/callbacks/get-rates.api.mdx
-[sep38]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0038.md
-[platform-api-kyc]: ../../api-reference/callbacks/get-customer.api.mdx
-[request-onchain-funds]: ../../api-reference/platform/rpc/methods/request_onchain_funds.mdx
-[how-to-use-jwt]: ../sep24/faq.mdx
-[json-rpc-methods]: ../../api-reference/platform/rpc/methods/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx
deleted file mode 100644
index b330f7ff07..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/getting-started.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía te enseñará a configurar e integrar con la Anchor Platform con el propósito de desarrollar un servicio de entrada y salida compatible con [SEP-6][sep-6], el protocolo estandarizado del ecosistema para depósitos y retiros programáticos.
-
-Al aprovechar el soporte del Anchor Platform para SEP-6, las empresas hacen que su propio servicio de entrada y salida esté disponible como una experiencia integrada en aplicaciones basadas en Stellar, como wallets y exchanges, ampliando su alcance y conectándose con los usuarios a través de las aplicaciones que ya utilizan.
-
-Antes de continuar con esta sección, asegúrate de haber [instalado][installation-ap] la Anchor Platform y configurado las características necesarias requeridas por SEP-6: [SEP-1 (Stellar Info File)][sep1-ap], [SEP-10 (Stellar Authentication)][sep10-ap] y [SEP-45 (Stellar Web Authentication for contract account)][sep45-ap].
-
-## La experiencia básica del usuario
-
-La experiencia completa del cliente para un depósito o retiro usando SEP-6 es la siguiente:
-
-1. El cliente abre la aplicación de wallet SEP-6 de su preferencia
-2. El cliente selecciona un activo para depositar y la wallet encuentra un anchor (los clientes también pueden elegir el anchor específico)
-3. Una vez que la wallet se autentica con el anchor, el cliente comienza a ingresar su información KYC y la información de la transacción solicitada por el anchor
-4. La wallet proporciona instrucciones y el cliente deposita la moneda fiduciaria real con el anchor (como una transferencia bancaria)
-5. Cuando la wallet recibe el depósito, el cliente recibe el activo tokenizado en la red Stellar desde la cuenta de distribución del anchor
-
-El cliente puede entonces usar el activo digital en la red Stellar para remesas, pagos, comercio, reserva de valor u otro caso de uso no listado aquí. En una fecha posterior, el cliente podría decidir retirar sus activos de la red Stellar, lo cual se vería así:
-
-1. El cliente abre su aplicación wallet
-2. El cliente selecciona el activo para retirar y la wallet encuentra el anchor
-3. Después de autenticarse con el anchor, el cliente puede ingresar su información de la transacción y cualquier información adicional KYC que no haya sido recopilada aún
-4. Tras solicitar la aprobación del cliente, la wallet envía la cantidad especificada del saldo del activo del cliente a la cuenta de distribución del anchor en Stellar
-5. Una vez que el anchor recibe el pago, el cliente recibe los fondos retirados mediante cualquier método que soporte el anchor (como transferencia bancaria)
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[installation-ap]: ../../admin-guide/getting-started.mdx
-[sep1-ap]: ../sep1/README.mdx
-[sep10-ap]: ../sep10/README.mdx
-[sep45-ap]: ../sep45/README.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/integration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/integration.mdx
deleted file mode 100644
index e9595256b9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep6/integration.mdx
+++ /dev/null
@@ -1,897 +0,0 @@
----
-title: Integración
-sidebar_position: 30
----
-
-import Security from "../../admin-guide/component/security/security.mdx";
-import UsingApiKey from "../../admin-guide/component/security/api_key.mdx";
-import UsingJwt from "../../admin-guide/component/security/jwt.mdx";
-import Rpc from "../../admin-guide/component/rpc/rpc.mdx";
-import RpcRequest from "../../admin-guide/component/rpc/request.mdx";
-import RpcResponse from "../../admin-guide/component/rpc/response.mdx";
-import RpcError from "../../admin-guide/component/rpc/error.mdx";
-import Observer from "../../admin-guide/component/observer/observer.mdx";
-
-Uno de los puntos principales de interacción con Anchor Platform es notificar a la Plataforma sobre eventos relacionados con las transacciones.
-
-En general, querrás proporcionar actualizaciones para los siguientes eventos.
-
-- Tu negocio requiere que el usuario envíe información KYC para procesar una transacción
-- Tu negocio actualizó las cantidades de entrada/salida/comisión para una transacción
-- Tu negocio está listo para recibir fondos del usuario
-- Tu negocio ha recibido fondos del usuario
-- Tu negocio ha enviado fondos al usuario
-- Tu negocio ha procesado un reembolso para la transacción del usuario
-- Tu negocio experimentó un error inesperado
-
-Esto se realiza haciendo solicitudes JSON-RPC al punto final de la API de la Plataforma. Las solicitudes JSON-RPC te permiten actualizar el estado de la transacción. Para mover la transacción a un estado específico, es necesario hacer una solicitud JSON-RPC correspondiente y pasar los datos requeridos por el método RPC.
-
-La API JSON-RPC de Anchor Platform está diseñada para notificar a la plataforma sobre cambios en el estado de la transacción. Dado esto, la API será llamada cada vez que un usuario o el anchor tome alguna acción que progrese el estado de la transacción en el flujo.
-
-La comunicación desde Anchor Platform sobre actualizaciones de transacciones, actualizaciones de clientes y creación de cotizaciones se maneja a través del servicio de eventos. Esta es una función opcional que debe configurarse separadamente de la integración SEP-6. Para más información, consulta [Manejo de Eventos][event-handling].
-
-Puedes obtener más información sobre el flujo y los estados de la transacción en el [documento del protocolo SEP-6][sep-6].
-
-## Callbacks
-
-Anchor Platform depende del servidor del negocio para proporcionar y almacenar información sobre clientes y cotizaciones.
-
-### Información del Cliente
-
-Anchor Platform no almacena información del cliente. En cambio, reenvía todas las solicitudes SEP-12 de clientes al servidor del negocio. El servidor del negocio es responsable de almacenar y gestionar esta información. Por lo tanto, tu servidor del negocio debe implementar las [APIs de cliente][customer-callback] para manejar actualizaciones KYC.
-
-### Cotizaciones y Tarifas
-
-Para admitir el intercambio de activos no equivalentes, Anchor Platform expone una API compatible con SEP-38 para proporcionar cotizaciones del exchange. La API de cotizaciones se usa para proporcionar al usuario la cantidad esperada del activo que recibirá a cambio del activo que está enviando. La API de cotizaciones también se usa para proporcionar al usuario las tarifas esperadas para la transacción. Por lo tanto, tu servidor del negocio debe implementar la [API de tarifas][rate-callback] para proporcionar cotizaciones a Anchor Platform.
-
-## Asegurar la API de la Plataforma
-
-<Security />
-
-### Uso de Clave API
-
-<UsingApiKey />
-
-### Uso de JWT
-
-<UsingJwt />
-
-## Realizando solicitudes JSON-RPC
-
-<Rpc />
-
-### Solicitud JSON-RPC
-
-<RpcRequest />
-
-### Respuesta JSON-RPC
-
-<RpcResponse />
-
-### Códigos de error
-
-<RpcError />
-
-## Actualizando Transacción de Depósito (Exchange) vía JSON-RPC
-
-El diagrama del flujo de depósito SEP-6 define las secuencias/reglas de la transición de estados de la transacción y un conjunto de métodos JSON-RPC que deben llamarse para cambiar ese estado. No puedes definir el estado que quieres establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene atributos requeridos, Anchor Platform devolverá un error y no cambiará el estado de la transacción.
-
-El flujo de depósito exchange es igual que el flujo de depósito, excepto que no será necesario recalcular las cantidades al solicitar fondos fuera de cadena, si el usuario ha proporcionado una cotización firme del anchor.
-
-[![sep6 deposit flow](/assets/ap/sep6-deposit-flow-diagram.png)](/assets/ap/sep6-deposit-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> indican que la transacción está en un estado de error o ha caducado.
-
-:::
-
-### Verificación de Información KYC
-
-Aunque Anchor Platform no requiere que un cliente tenga su información KYC recopilada antes de iniciar un depósito, tu negocio puede querer recolectar esta información antes de que el cliente haga una transferencia. Escuchando eventos de creación de transacciones, o consultando el punto final [`GET /transactions`][get-transactions], puedes determinar si una transacción requiere que el cliente actualice su información. Los campos requeridos SEP-9 pueden comunicarse al usuario devolviendo un estado `NEEDS_INFO` con los campos requeridos en el atributo `fields`.
-
-Después de que el usuario haya enviado su información KYC, llama al método JSON-RPC `notify_customer_info_updated` para actualizar el estado de la transacción. Además, llama a este método siempre que el estado SEP-12 de un cliente cambie, por ejemplo, cuando la información del cliente está siendo validada y el estado cambia de `NEEDS_INFO` a `PROCESSING`. Esto asegura que cualquier cliente configurado con una URL de callback sea notificado del último estado del cliente, permitiendo que el cliente solicite al usuario actualizar su información.
-
-<CodeExample>
-
-```json
-// notify-customer-info-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_customer_info_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Customer info updated",
-      "customer_id": "45f8884d-d6e1-477f-a680-503179263359",
-      "customer_type": "sep6-deposit" // or sep6-withdrawal
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh notify-customer-info-updated.json
-```
-
-</CodeExample>
-
-### Listo para Recibir Fondos
-
-Después de que el usuario haya enviado su información KYC, el anchor puede notificar a la Plataforma que está listo para recibir fondos. El anchor debe usar el RPC `request_offchain_funds` para proporcionar las cantidades finales al usuario. Para ello, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-offchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_offchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request offchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "iso4217:USD"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "iso4217:USD"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "instructions": {
-        "organization.bank_number": {
-          "value": "123456789",
-          "description": "US Bank routing number"
-        },
-        "organization.bank_account_number": {
-          "value": "123456789",
-          "description": "US Bank account number"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es la cantidad que el usuario debe enviar al negocio.
-- `amount_out` es la cantidad que el usuario recibirá.
-- `fee_details` es la cantidad total de comisiones recogidas por el negocio.
-- `asset` es parte del campo `amount_x` y está en formato SEP-38. En este ejemplo, está configurado en USD, asumiendo que el usuario realizó una transferencia bancaria al sistema usando USD.
-- `instructions` es el conjunto de campos estándar SEP-9 que el usuario debe usar para enviar fondos al negocio. En este ejemplo, el usuario debe enviar fondos a la cuenta bancaria con el número de ruta `123456789` y número de cuenta `123456789`.
-
-La información sobre las cantidades (entrada/salida/comisión) es obligatoria si quieres mover la transacción al estado `pending_user_transfer_start`.
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-offchain-funds.json
-```
-
-</CodeExample>
-
-:::caution
-
-Para depósitos exchange con cotización firme (la solicitud está asociada con un `quote_id`), no deben proporcionarse cantidades.
-
-:::
-
-### Fondos Recibidos
-
-Si se recibieron fondos fuera de cadena, querrás proporcionar información actualizada de la transacción.
-
-<CodeExample>
-
-```json
-// offchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds received",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      },
-      "amount_expected": {
-        "amount": 10
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `funds_received_at` es la fecha y hora de recepción de los fondos.
-- `external_transaction_id` es el ID de la transacción en la red externa.
-
-Los campos de cantidad son opcionales. Si se omiten, se usarán los valores anteriores a esta solicitud.
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-received.json
-```
-
-</CodeExample>
-
-### Esperando Fondos del Usuario
-
-En el mundo real, el proceso de confirmación de transferencia puede llevar tiempo. En tales casos, las transacciones deben establecerse en un nuevo estado que indique que la confirmación de la transferencia ha sido recibida pero los fondos aún no han sido recibidos.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_received_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Enviando Fondos Onchain
-
-Luego, envía una transacción en la red Stellar para cumplir con el depósito del usuario. Después de que la transacción Stellar haya sido enviada, es necesario enviar la solicitud JSON-RPC `notify_onchain_funds_sent` para notificar al usuario que los fondos fueron enviados exitosamente.
-
-<CodeExample>
-
-```json
-// onchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds sent",
-      "stellar_transaction_id": "7...9"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `stellar_transaction_id` es el ID de la transacción en la red Stellar de la transferencia.
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-sent.json
-```
-
-</CodeExample>
-
-Después de esta solicitud JSON-RPC, la transacción cambiará al estado `completed`.
-
-### Confianza Pendiente
-
-Este estado debe establecerse si un pago requiere una trustline de activo que el usuario no ha configurado. Hay dos formas en que la transacción puede moverse al estado `pending_trust`. La primera es cuando el servidor del negocio detecta que la trustline no está configurada. La segunda es cuando el negocio mismo detecta que falta la trustline y quiere notificar al usuario que debe configurarla. Para mover la transacción al estado `pending_trust`, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-trust.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_trust",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine not configured"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-trust.json
-```
-
-</CodeExample>
-
-:::info
-
-El sistema de procesamiento de pagos verifica periódicamente si la trustline fue configurada. Si lo estuvo, enviará automáticamente un pago y cambiará el estado de la transacción a `pending_stellar`.
-
-:::
-
-### Trust Set
-
-Este estado debe establecerse si el negocio ha detectado que la trustline fue o no configurada por el usuario.
-
-<CodeExample>
-
-```json
-// trust-set.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_trust_set",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Asset trustine set",
-      "success": "true"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- Flag `success` que define si la trustline fue o no configurada por el usuario
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh trust-set.json
-```
-
-</CodeExample>
-
-:::info
-
-Dependiendo del flag `success`, el estado de la transacción cambiará a `pending_stellar` si la trustline fue configurada o a `pending_anchor` si no lo fue.
-
-:::
-
-### Reembolso Enviado
-
-A veces, es necesario devolver fondos al usuario (reembolso). Puedes reembolsar la suma total (reembolso completo) o hacer varios reembolsos parciales a la `source_account` usando el `refund_memo` y `refund_memo_type` asociados con la transacción, si están presentes. Además, si el usuario envió más dinero del esperado, puedes reembolsar una parte al usuario y enviar el resto como fondos onchain.
-
-<CodeExample>
-
-```json
-// refund-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_refund_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Refund sent",
-      "refund": {
-        "id": "1c186184-09ee-486c-82a6-aa7a0ab1119c",
-        "amount": {
-          "amount": 10,
-          "asset": "iso4217:USD"
-        },
-        "fee_details": {
-          "total": 1,
-          "asset": "iso4217:USD"
-        }
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh refund-sent.json
-```
-
-</CodeExample>
-
-:::info
-
-Si la suma de los reembolsos es menor que `amount_in`, el estado de la transacción será `pending_anchor`. Solo si la suma de los reembolsos es igual a `amount_in`, el estado de la transacción será `refunded`.
-
-:::
-
-### Reembolso Pendiente
-
-Este es similar a [Reembolso Enviado](#refund-sent), pero maneja el caso cuando un reembolso ha sido enviado a la red externa pero aún no confirmado. El estado de la transacción se establece en `pending_external`. Este es el estado que se configurará cuando se espere que Bitcoin u otra red externa de cripto complete una transacción, o cuando se espere una transferencia bancaria.
-
-### Error de Transacción
-
-Si encuentras un error irrecuperable al procesar la transacción, es necesario configurar el estado de la transacción a `error`. Puedes usar el campo mensaje para describir los detalles del error.
-
-<CodeExample>
-
-```json
-// transaction-error.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_error",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Error occurred"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-error.json
-```
-
-</CodeExample>
-
-:::tip
-
-Si un usuario hizo una transferencia, debes hacer una recuperación de la transacción, y luego puedes reintentar procesarla o iniciar un reembolso.
-
-:::
-
-### Transacción Caducada
-
-Tu negocio puede querer manejar transacciones abandonadas expirándolas después de que permanezcan inactivas por un periodo determinado. Para lograrlo, verifica el estado de la transacción usando el punto final `GET /transactions` y ordena los resultados por la marca temporal `user_action_required_by`. Si la marca temporal ha pasado, ejecuta manualmente la lógica correspondiente, como caducar la transacción o iniciar un reembolso automático, basado en el estado actual de la transacción.
-
-<CodeExample>
-
-```json
-// transaction-expired.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_expired",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction expired"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-expired.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método JSON-RPC no puede usarse después de que el usuario haya hecho una transferencia.
-
-:::
-
-### Recuperación de Transacción
-
-El estado de la transacción puede cambiarse de `error/expired` a `pending_anchor`. Después de la recuperación, puedes reembolsar los activos recibidos o continuar con el procesamiento de la transacción. Para recuperar una transacción, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// transaction-recovery.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_transaction_recovery",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Transaction recovered"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh transaction-recovery.json
-```
-
-</CodeExample>
-
-## Actualizando Transacción de Retirada (Exchange) vía JSON-RPC
-
-El diagrama del flujo de retirada SEP-6 define la secuencia/reglas de la transición de estados de la transacción. No puedes definir el estado que quieres establecer para una transacción específica en tus solicitudes. Cada método JSON-RPC define las estructuras de datos que espera en la solicitud. Si la solicitud no contiene atributos requeridos, Anchor Platform devolverá un error y no cambiará el estado de la transacción.
-
-El flujo de retirada exchange es igual que el flujo de retirada, excepto que no será necesario recalcular las cantidades al solicitar fondos onchain, si el usuario ha proporcionado una cotización firme del anchor.
-
-[![sep6 withdrawal flow](/assets/ap/sep6-withdrawal-flow-diagram.png)](/assets/ap/sep6-withdrawal-flow-diagram.png)
-
-:::tip
-
-Los estados en <span style={{color: "green"}}>verde</span> son obligatorios y definen el camino más corto.
-
-Los estados en <span style={{color: "#B0BF1A"}}>amarillo</span> son opcionales y pueden omitirse.
-
-Los estados en <span style={{color: "red"}}>rojo</span> indican que la transacción está en un estado de error o ha caducado.
-
-:::
-
-Una vez que el flujo de retirada ha terminado, implementar la retirada es sencillo. Algunas partes del flujo son similares y pueden reutilizarse.
-
-El punto de partida tanto para retirada como para depósito es el mismo.
-
-### Listo para Recibir Fondos
-
-De manera similar al depósito, el paso después de que se ha recopilado KYC es notificar al usuario que el anchor está listo para recibir fondos. Sin embargo, como tu servicio estará recibiendo transacciones sobre la red Stellar, la solicitud RPC será diferente. El anchor debe usar el RPC `request_onchain_funds` para proporcionar las cantidades finales al usuario. Para ello, realiza la siguiente solicitud JSON-RPC.
-
-<CodeExample>
-
-```json
-// request-onchain-funds.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "request_onchain_funds",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Request onchain funds",
-      "amount_in": {
-        "amount": 10,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_out": {
-        "amount": 9,
-        "asset": "iso4217:USD"
-      },
-      "fee_details": {
-        "total": 1,
-        "asset": "stellar:USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-      },
-      "amount_expected": {
-        "amount": 10
-      },
-      "destination_account": "GD...G",
-      "memo": "12345",
-      "memo_type": "id"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-- `amount_in` es la cantidad que el usuario debe enviar al negocio.
-- `amount_out` es la cantidad que el usuario recibirá.
-- `fee_details` es la cantidad total de comisiones recogidas por el negocio.
-- `asset` es parte del campo `amount_x` y está en formato SEP-38. En este ejemplo, está configurado en USD, asumiendo que el usuario realizó una transferencia bancaria al sistema usando USD.
-- `memo` es el memo que el usuario debe usar al enviar sus fondos onchain al anchor.
-- `memo_type` es el tipo de memo que el usuario debe usar al enviar sus fondos onchain al anchor.
-- `destination_account` es la cuenta a la que el usuario debe enviar los fondos.
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh request-onchain-funds.json
-```
-
-</CodeExample>
-
-:::caution
-
-Para retiradas exchange con cotización firme (la solicitud está asociada con un `quote_id`), no deben proporcionarse cantidades.
-
-:::
-
-:::tip
-
-Configurar `memo`, `memo_type` y `destination_account` es opcional.
-
-Si la integración con un custodio tercero está habilitada, Anchor Platform puede generar `memo`, `memo_type` y `destination_address` si se elige un `deposit_info_generator_type` correspondiente. También puedes proporcionar `memo` y `memo_type` a la solicitud como se muestra arriba. Nota que el memo debe ser único, esto ayuda a asociar transacciones Stellar con transacciones SEP.
-
-Si tu negocio administra los activos, Anchor Platform puede generar memos por ti. Cuando el estado cambia a `pending_user_transfer_start`, Anchor Platform asigna automáticamente `memo` y `memo_type` (solo si no están incluidos en la solicitud).
-
-:::
-
-:::note
-
-Debe configurarse la cuenta Stellar que se usará para recibir fondos.
-
-:::
-
-### Fondos Recibidos
-
-Si se recibieron fondos onchain, necesitas proporcionar las cantidades y cambiar el estado de la transacción a `pending_anchor`.
-
-<CodeExample>
-
-```json
-// onchain-funds-received.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_onchain_funds_received",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Onchain funds received",
-      "stellar_transaction_id": "7...9",
-      "amount_in": {
-        "amount": 10
-      },
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh onchain-funds-received.json
-```
-
-</CodeExample>
-
-:::tip
-
-Este método será llamado por el observador de pagos Stellar cuando detecte que se han recibido fondos onchain.
-
-:::
-
-### Cantidad Actualizada
-
-Si se recibieron fondos onchain, pero por alguna razón `amount_in` difiere de lo especificado en el flujo interactivo (`amount_expected`), puedes actualizar `amount_out` y `fee_details` para que correspondan al `amount_in` real. El estado de la transacción en este caso no cambiará y seguirá siendo `pending_anchor`.
-
-<CodeExample>
-
-```json
-// amounts-updated.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_amounts_updated",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Amounts updated",
-      "amount_out": {
-        "amount": 9
-      },
-      "fee_details": {
-        "total": 1
-      }
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh amounts-updated.json
-```
-
-</CodeExample>
-
-:::note
-
-Solo `amount_out` y `fee_details` pueden actualizarse usando esta solicitud JSON-RPC, y no necesitas especificar los activos de las cantidades.
-
-:::
-
-### Fondos Fuera de Cadena Disponibles
-
-Puedes mover el estado de la transacción a `pending_user_transfer_complete` si se enviaron fondos fuera de cadena y está listo para que el usuario/beneficiario los recoja.
-
-<CodeExample>
-
-```json
-// offchain-funds-available.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_available",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds available",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-available.json
-```
-
-</CodeExample>
-
-### Fondos Fuera de Cadena Pendientes
-
-Otra opción es mover el estado de la transacción a `pending_external`. Este estado significa que el pago se ha enviado a una red externa, pero aún no está confirmado.
-
-<CodeExample>
-
-```json
-// offchain-funds-pending.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_pending",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds pending",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-pending.json
-```
-
-</CodeExample>
-
-### Fondos Fuera de Cadena Enviados
-
-Para completar la transacción y cambiar su estado a `completed`, necesitas hacer la solicitud JSON-RPC `notify_offchain_funds_sent`.
-
-<CodeExample>
-
-```json
-// offchain-funds-sent.json
-[
-  {
-    "id": 1,
-    "jsonrpc": "2.0",
-    "method": "notify_offchain_funds_sent",
-    "params": {
-      "transaction_id": "<transaction_id>",
-      "message": "Offchain funds sent",
-      "funds_sent_at": "2023-07-04T12:34:56Z",
-      "external_transaction_id": "a...c"
-    }
-  }
-]
-```
-
-</CodeExample>
-
-Para procesar esto, necesitas ejecutar:
-
-<CodeExample>
-
-```bash
-./call-json-rpc.sh offchain-funds-sent.json
-```
-
-</CodeExample>
-
-### Reembolso Enviado
-
-La lógica de reembolso funciona de la misma manera que en el flujo de depósito. Para más detalles, consulta [Reembolso Enviado](#refund-sent) del flujo de depósito.
-
-### Error de Transacción
-
-Funciona de la misma manera que en el flujo de depósito. Para más detalles, consulta [Error de Transacción](#transaction-error) del flujo de depósito.
-
-### Transacción Caducada
-
-Funciona de la misma manera que en el flujo de depósito. Para más detalles, consulta [Transacción Caducada](#expired-transaction) del flujo de depósito.
-
-### Recuperación de Transacción
-
-Funciona de la misma manera que en el flujo de depósito. Para más detalles, consulta [Recuperación de Transacción](#transaction-recovery) del flujo de depósito.
-
-## Seguimiento de Transacciones Stellar
-
-<Observer />
-
-[sep-6]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md
-[manejo-de-eventos]: ../../admin-guide/events/README.mdx
-[callbacks-de-cliente]: ../../api-reference/callbacks/README.mdx
-[callbacks-de-tarifa]: ../../api-reference/callbacks/README.mdx
-[obtencion-de-transacciones]: ../../api-reference/platform/transactions/get-transactions.api.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/README.mdx
deleted file mode 100644
index 0058f56650..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/README.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Introducción a Stellar Disbursement Platform
-sidebar_label: Introducción
-pagination_label: Introducción a Stellar Disbursement Platform
-sidebar_position: 10
-pagination_next: platforms/stellar-disbursement-platform/admin-guide/overview
----
-
-# Stellar Disbursement Platform
-
-La Stellar Disbursement Platform (SDP) es una herramienta desarrollada para organizaciones que permite realizar pagos masivos a un grupo de destinatarios a través de la red Stellar.
-
-Este es un proyecto open-source desarrollado sobre la red Stellar, y el código puede encontrarse en los siguientes repositorios:
-
-- [stellar/stellar-disbursement-platform-backend](https://github.com/stellar/stellar-disbursement-platform-backend): Este repositorio contiene el código del backend e infraestructura para la Stellar Disbursement Platform.
-- [stellar/stellar-disbursement-platform-frontend](https://github.com/stellar/stellar-disbursement-platform-frontend): Este repositorio contiene el código del frontend web para la Stellar Disbursement Platform.
-- [stellar/helm-charts](https://github.com/stellar/helm-charts/tree/main/charts/stellar-disbursement-platform): Este repositorio contiene el Helm chart para desplegar la Stellar Disbursement Platform usando kubernetes.
-
-En esta sección, encontrarás una [Guía para Administradores](./stellar-disbursement-platform/admin-guide/) que te enseñará cómo ejecutar la Stellar Disbursement Platform, así como una [Referencia de API](./api-reference/admin.tag.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/advanced-configration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/advanced-configration.mdx
deleted file mode 100644
index 4170ea4847..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/advanced-configration.mdx
+++ /dev/null
@@ -1,236 +0,0 @@
----
-title: Configuración avanzada
-description: Entiende cómo configurar el Stellar Disbursement Platform para diversos escenarios. Esto incluye multi-arrendamiento, testnet versus mainnet, etc.
-keywords:
-  - SDP
-  - configuration
-sidebar_position: 45
----
-
-En esta guía, aprenderás sobre las opciones avanzadas de configuración para el Stellar Disbursement Platform (SDP). Estas configuraciones te permiten adaptar el SDP para cumplir con requisitos específicos, como multi-arrendamiento, selección de red y ajuste de rendimiento.
-
-## Configuración de Testnet a Mainnet
-
-Al aprovisionar una nueva instancia de SDP, esta se configura para operar en modo Mainnet o Testnet según las variables de entorno establecidas durante la configuración. La mayoría de los usuarios comenzarán con Testnet para desarrollo y pruebas antes de pasar a Mainnet para uso en producción.
-
-:::caution
-
-Una instancia de SDP está diseñada para operar en Testnet o Mainnet. No se admite cambiar entre estas redes en una instancia existente y podría causar comportamientos inesperados. Si necesitas cambiar la red, se recomienda crear una nueva instancia de SDP con la configuración deseada.
-
-:::
-
-Una vez valides tu configuración en Testnet, puedes desplegar una nueva instancia configurada para Mainnet estableciendo las variables de entorno apropiadas durante el proceso de aprovisionamiento.
-
-### Variables de entorno
-
-Al cambiar de Testnet a Mainnet, debes actualizar las siguientes variables de entorno para cada servicio para apuntar a los recursos de la red pública.
-
-#### Servicio principal de SDP
-
-| Variable             | Valor para Testnet                    | Valor para Mainnet                               | Descripción                                                                |
-| :------------------- | :------------------------------------ | :----------------------------------------------- | :------------------------------------------------------------------------- |
-| `NETWORK_PASSPHRASE` | `Test SDF Network ; September 2015`   | `Public Global Stellar Network ; September 2015` | La frase de contraseña para la red Stellar.                                |
-| `HORIZON_URL`        | `https://horizon-testnet.stellar.org` | `https://horizon.stellar.org`                    | La URL del servidor Horizon.                                               |
-| `DISABLE_MFA`        | x                                     | `false`                                          | Desactiva la autenticación multifactor. **Debe ser `false` para Mainnet.** |
-
-#### Servicio de envío de transacciones (TSS)
-
-| Variable             | Valor para Testnet                    | Valor para Mainnet                               | Descripción                                 |
-| :------------------- | :------------------------------------ | :----------------------------------------------- | :------------------------------------------ |
-| `NETWORK_PASSPHRASE` | `Test SDF Network ; September 2015`   | `Public Global Stellar Network ; September 2015` | La frase de contraseña para la red Stellar. |
-| `HORIZON_URL`        | `https://horizon-testnet.stellar.org` | `https://horizon.stellar.org`                    | La URL del servidor Horizon.                |
-
-#### Panel de control
-
-| Variable             | Valor para Testnet                        | Valor para Mainnet                       | Descripción                                        |
-| :------------------- | :---------------------------------------- | :--------------------------------------- | :------------------------------------------------- |
-| `HORIZON_URL`        | `https://horizon-testnet.stellar.org`     | `https://horizon.stellar.org`            | La URL del servidor Horizon usado por el frontend. |
-| `STELLAR_EXPERT_URL` | `https://stellar.expert/explorer/testnet` | `https://stellar.expert/explorer/public` | La URL para el explorador Stellar Expert.          |
-
-### Consideraciones críticas
-
-Antes de desplegar en Mainnet, debes atender los siguientes requisitos críticos para asegurar que tu instancia funcione correctamente.
-
-**Debes** generar un nuevo par de claves seguro para tu Cuenta de Distribución en Mainnet. No reutilices las claves de Testnet.
-
-- **Generar claves**: Crea un nuevo par de claves y configura `DISTRIBUTION_PUBLIC_KEY` y `DISTRIBUTION_SEED`.
-- **Generar frase de cifrado**: Debes generar nuevas frases de cifrado para las cuentas de distribución de arrendatarios y cuentas de canal configurando `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE` y `CHANNEL_ACCOUNTS_ENCRYPTION_PASSPHRASE`.
-- **Financiar la cuenta**: La Cuenta de Distribución requiere un saldo inicial de XLM para funcionar. Es responsable de:
-  1. **Crear cuentas de canal**: El sistema creará automáticamente `NUM_CHANNEL_ACCOUNTS` (por defecto: 2).
-  2. **Bootstrapear arrendatarios**: Cuando se aprovisiona un nuevo arrendatario, el sistema transfiere una cantidad de arranque de XLM desde la Cuenta de Distribución a la Cuenta de Distribución del arrendatario. Esto se controla mediante `TENANT_XLM_BOOTSTRAP_AMOUNT` (por defecto: 5 XLM).
-
-### Métodos de configuración
-
-Puedes configurar el SDP para Mainnet usando Helm Charts (para despliegues en Kubernetes) o Docker Compose (para despliegues locales o simples).
-
-#### Helm Charts
-
-Si despliegas con Helm, el chart proporciona un ajuste global que configura automáticamente los parámetros de red necesarios.
-
-En tu archivo `values.yaml`, configura `global.isPubnet` como `true`. Esto establecerá automáticamente el `NETWORK_PASSPHRASE`, `HORIZON_URL` y `STELLAR_EXPERT_URL` correctos para todos los servicios.
-
-```yaml
-global:
-  # Set to true for Mainnet
-  isPubnet: true
-```
-
-#### Docker Compose
-
-Actualiza tu archivo `.env` con los siguientes valores:
-
-```bash
-# Network Configuration
-NETWORK_TYPE="pubnet"
-NETWORK_PASSPHRASE="Public Global Stellar Network ; September 2015"
-HORIZON_URL="https://horizon.stellar.org"
-
-# Security
-DISABLE_MFA=false
-
-# Distribution Account (Mainnet Keys)
-DISTRIBUTION_PUBLIC_KEY="G..."
-DISTRIBUTION_SEED="S..."
-
-# Encryption Passphrases
-DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE="S..."
-CHANNEL_ACCOUNTS_ENCRYPTION_PASSPHRASE="S..."
-```
-
-## Configuración de un solo arrendatario a multi-arrendatarios
-
-El Stellar Disbursement Platform (SDP) soporta multi-arrendamiento, permitiendo que una sola instancia sirva a varias organizaciones (arrendatarios). Cada arrendatario tiene sus propios datos aislados, usuarios y cuenta de distribución (fuente de fondos).
-
-### Configuración
-
-Para habilitar multi-arrendamiento, debes actualizar tu configuración para desactivar el modo de arrendatario único y asegurar el acceso a la API de administración.
-
-1. **Desactivar modo de arrendatario único**: Establece la variable de entorno `SINGLE_TENANT_MODE` a `false`.
-2. **Exponer puerto de administración**: Asegura que el puerto de la API de administración (por defecto `8003`) esté expuesto en el servicio backend del SDP.
-
-### Enrutamiento e ingreso
-
-El SDP identifica al arrendatario para cada solicitud usando uno de los siguientes métodos, en orden de prioridad:
-
-1. **Encabezado HTTP**: El encabezado `SDP-Tenant-Name`.
-2. **Subdominio**: El prefijo del nombre de host (por ejemplo, `tenant1` en `tenant1.sdp.stellar.org`).
-
-#### Encabezado HTTP
-
-Puedes especificar explícitamente el arrendatario configurando el encabezado `SDP-Tenant-Name` en tus solicitudes HTTP.
-
-```bash
-curl -H "SDP-Tenant-Name: tenant1" https://sdp.stellar.org/ ...
-```
-
-#### Enrutamiento por subdominio
-
-En un entorno de producción, es común usar enrutamiento por subdominio. Por ejemplo, `tenant1.sdp.stellar.org` y `tenant2.sdp.stellar.org` apuntarán a la misma instancia de SDP.
-
-#### Helm Charts
-
-Al desplegar con Helm, configuras el dominio wildcard usando el valor `sdp.route.mtnDomain`. Esto crea una regla de Ingress que coincide con todos los subdominios.
-
-En tu archivo `values.yaml`:
-
-```yaml
-sdp:
-  route:
-    # The wildcard domain for multi-tenancy
-    mtnDomain: "*.sdp.stellar.org"
-```
-
-:::note
-
-Asegúrate de que tu proveedor DNS tenga un registro A wildcard (por ejemplo, `*.sdp.stellar.org`) apuntando a la IP del Load Balancer de tu Ingress Controller.
-
-:::
-
-#### Docker Compose (desarrollo local)
-
-Para desarrollo local con Docker Compose debes mapear subdominios específicos de arrendatarios a `127.0.0.1` en el archivo `/etc/hosts` de tu máquina (para usuarios de Windows, el archivo está en `C:\Windows\System32\drivers\etc\hosts`).
-
-**Ejemplo de `/etc/hosts`:**
-
-```text
-127.0.0.1   localhost
-127.0.0.1   sdp.local           # Default/Admin domain
-127.0.0.1   tenant1.sdp.local   # First tenant
-127.0.0.1   tenant2.sdp.local   # Second tenant
-```
-
-### Aprovisionamiento de arrendatarios
-
-En modo multi-arrendatario, aprovisionas nuevos arrendatarios usando la API de administración (puerto `8003` por defecto). Cada arrendatario tendrá sus propios datos aislados.
-
-**Endpoint**: [POST /tenants](../api-reference/create-tenant.api.mdx) **Ejemplo de solicitud:**
-
-```bash
-curl --location 'http://localhost:8003/tenants' \
---header 'Content-Type: application/json' \
---header 'Authorization: Basic <Base64 Admin Credentials>' \
---data '{
-    "name": "tenant1",
-    "organization_name": "Tenant One Organization",
-    "base_url": "https://tenant1.sdp-api.stellar.org",
-    "sdp_ui_base_url": "https://tenant1.sdp-dashboard.stellar.org",
-    "owner_email": "owner@tenant1.com",
-    "owner_first_name": "Jane",
-    "owner_last_name": "Doe",
-    "distribution_account_type": "DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT"
-}'
-```
-
-#### Cuentas de distribución multi-arrendatario
-
-Este es el campo más importante, ya que determina la fuente de fondos (cuenta de distribución) para el arrendatario, así como cómo se almacena el secreto de esta cuenta.
-
-Esto se determina por el campo `distribution_account_type` en la llamada API mencionada arriba. Los valores posibles se describen a continuación:
-
-- `DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT`
-
-- **Plataforma**: Stellar
-
-- **Ubicación de almacenamiento del secreto**: Base de datos, cifrada con `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`
-
-- **Activos soportados**: Cualquier activo Stellar
-
-- **Aislamiento de clave/secreto**: Segregado por arrendatario
-
-- **Adecuado para**: Multi-arrendatario y arrendatario único
-
-- **¿Cómo se configura?**: La cuenta de distribución se genera aleatoriamente y se financia durante el proceso de aprovisionamiento, y el secreto se cifra y almacena de forma segura en la base de datos. La cuenta se financia desde la cuenta HOST de distribución por una cantidad definida en `TENANT_XLM_BOOTSTRAP_AMOUNT`.
-
-- `DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT`
-
-- **Plataforma**: [Circle](https://www.circle.com)
-
-- **Ubicación de almacenamiento del secreto**: Base de datos, cifrada con `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE`
-
-- **Activos soportados**: [USDC](https://www.circle.com/en/usdc)/[EURC](https://www.circle.com/en/eurc)
-
-- **Aislamiento de clave/secreto**: Segregado por arrendatario
-
-- **Adecuado para**: Multi-arrendatario y arrendatario único
-
-- **¿Cómo se configura?**: La clave API de Circle la proporciona el propio arrendatario una vez que tiene acceso al panel de control. El secreto se cifra y almacena de forma segura en la base de datos.
-
-- 🔴 `DISTRIBUTION_ACCOUNT.STELLAR.ENV`
-
-- **Plataforma**: Stellar
-
-- **Ubicación de almacenamiento del secreto**: Variable de entorno `DISTRIBUTION_SEED`
-
-- **Activos soportados**: Cualquier activo Stellar
-
-- **Aislamiento de clave/secreto**: 🚨 Mismo cuenta de distribución que la HOST
-
-- **Adecuado para**: Solo arrendatario único
-
-- **¿Cómo se configura?**: El arrendatario usará la cuenta HOST **tal cual**. El host es responsable de crear la cuenta y configurarla con el secreto `DISTRIBUTION_SEED`.
-
-:::warning
-
-Una vez creado un arrendatario, no se puede cambiar el tipo de cuenta de distribución. Si deseas usar un tipo diferente de cuenta de distribución, tendrás que crear un nuevo arrendatario.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/cli-manual.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/cli-manual.mdx
deleted file mode 100644
index 1b5faf49a9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/cli-manual.mdx
+++ /dev/null
@@ -1,655 +0,0 @@
----
-title: Manual CLI
-description: Guía para usar el CLI de Stellar Disbursement Platform
-keywords:
-  - SDP
-  - CLI
-sidebar_position: 50
----
-
-## Comando raíz
-
-El comando `stellar-disbursement-platform` es el punto de entrada principal para la aplicación. Proporciona varios subcomandos para administrar el servicio, la base de datos y otras utilidades.
-
-### Uso
-
-```bash
-stellar-disbursement-platform [command] [flags]
-```
-
-:::tip
-
-Para todos los comandos siguientes, puedes usar la flag `--help` para obtener más información sobre el comando y sus opciones. Por ejemplo:
-
-```bash
-stellar-disbursement-platform serve --help
-```
-
-:::
-
-## Flags globales
-
-Las siguientes flags están disponibles para todos los comandos:
-
-| Flag                   | Descripción                                                                                                                              |
-| :--------------------- | :--------------------------------------------------------------------------------------------------------------------------------------- |
-| `--base-url`           | La URL base del servidor backend de SDP. Por defecto es `http://localhost:8000`.                                                         |
-| `--database-url`       | URL de la base de datos Postgres. Por defecto es `postgres://localhost:5432/sdp?sslmode=disable`.                                        |
-| `--environment`        | El entorno en el que se ejecuta la aplicación. Ejemplos: `development`, `staging`, `production`. Por defecto es `development`.           |
-| `--log-level`          | El nivel de logs usado en este proyecto. Opciones: `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `FATAL` o `PANIC`. Por defecto es `TRACE`. |
-| `--network-passphrase` | La passphrase de la red Stellar. Por defecto es `Test SDF Network ; September 2015`.                                                     |
-| `--sdp-ui-base-url`    | La URL base del servidor UI de SDP. Por defecto es `http://localhost:3000`.                                                              |
-| `--sentry-dsn`         | El DSN (clave cliente) del proyecto Sentry. Si no se proporciona, no se usará Sentry.                                                    |
-
-## Comando Serve
-
-El comando `serve` inicia el servidor backend de Stellar Disbursement Platform. Este servidor maneja las solicitudes API, procesa las distribuciones y administra las operaciones de los tenants.
-
-### Uso
-
-```bash
-stellar-disbursement-platform serve [flags]
-```
-
-### Flags
-
-| Flag                                                 | Descripción                                                                                                                                                                                                       |
-| :--------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--admin-account`                                    | ID de la cuenta administrador. Para usar, agrégalo al encabezado de la solicitud como 'Authorization', formateado como 'ADMIN_ACCOUNT:ADMIN_API_KEY' codificado en Base64.                                        |
-| `--admin-api-key`                                    | Clave API para la cuenta administrador. Para usar, agrégalo al encabezado de la solicitud como 'Authorization', formateado como 'ADMIN_ACCOUNT:ADMIN_API_KEY' codificado en Base64.                               |
-| `--admin-port`                                       | Puerto donde el servidor del tenant administrador estará escuchando. Por defecto es `8003`.                                                                                                                       |
-| `--aws-access-key-id`                                | El ID de la clave de acceso de AWS.                                                                                                                                                                               |
-| `--aws-region`                                       | La región de AWS.                                                                                                                                                                                                 |
-| `--aws-secret-access-key`                            | La clave secreta de acceso de AWS.                                                                                                                                                                                |
-| `--aws-ses-sender-id`                                | La dirección de email que AWS usará para enviar correos. Utiliza AWS SES.                                                                                                                                         |
-| `--aws-sns-sender-id`                                | El ID del remitente de la cuenta AWS que envía el mensaje SMS. Utiliza AWS SNS.                                                                                                                                   |
-| `--bridge-api-key`                                   | Clave API de Bridge. Esto solo se debe configurar si la integración con Bridge está habilitada.                                                                                                                   |
-| `--bridge-base-url`                                  | URL base de Bridge. Esto solo se debe configurar si la integración con Bridge está habilitada. Por defecto es `https://api.bridge.xyz`.                                                                           |
-| `--captcha-type`                                     | El tipo de CAPTCHA a utilizar. Opciones: `GOOGLE_RECAPTCHA_V2`, `GOOGLE_RECAPTCHA_V3`. Por defecto es `GOOGLE_RECAPTCHA_V2`.                                                                                      |
-| `--channel-account-encryption-passphrase`            | Clave privada ed25519 compatible con Stellar usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, tomará como valor el de la opción `distribution-seed`.                  |
-| `--circle-api-type`                                  | Tipo de API de Circle. Opciones: `TRANSFERS`, `PAYOUTS`. Por defecto es `TRANSFERS`.                                                                                                                              |
-| `--cors-allowed-origins`                             | URLs de Cors permitidas para acceder a los endpoints, separadas por ",".                                                                                                                                          |
-| `--crash-tracker-type`                               | Tipo de rastreador de fallos. Opciones: `SENTRY`, `DRY_RUN`. Por defecto es `DRY_RUN`.                                                                                                                            |
-| `--db-conn-max-idle-time-seconds`                    | Tiempo máximo en segundos que una conexión puede estar inactiva antes de cerrarse. Por defecto es `10`.                                                                                                           |
-| `--db-conn-max-lifetime-seconds`                     | Tiempo máximo en segundos de vida útil para una sola conexión. Por defecto es `300`.                                                                                                                              |
-| `--db-max-idle-conns`                                | Número máximo de conexiones inactivas de base de datos retenidas por pool. Por defecto es `2`.                                                                                                                    |
-| `--db-max-open-conns`                                | Número máximo de conexiones abiertas de base de datos por pool. Por defecto es `20`.                                                                                                                              |
-| `--disable-mfa`                                      | Desactiva la autenticación Multi-Factor (MFA) por email.                                                                                                                                                          |
-| `--disable-recaptcha`                                | Desactiva ReCAPTCHA para iniciar sesión y recuperar contraseña.                                                                                                                                                   |
-| `--distribution-account-encryption-passphrase`       | Clave privada ed25519 compatible con Stellar usada para cifrar y descifrar las claves privadas de las cuentas de distribución de los tenants.                                                                     |
-| `--distribution-public-key`                          | La clave pública de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                                                |
-| `--distribution-seed`                                | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                                                |
-| `--ec256-private-key`                                | La clave privada EC256 usada para firmar el token de autenticación. Esta clave EC debe ser al menos tan fuerte como prime256v1 (P-256).                                                                           |
-| `--email-sender-type`                                | Tipo de remitente de email. Opciones: `DRY_RUN`, `TWILIO_EMAIL`, `AWS_EMAIL`. Por defecto es `DRY_RUN`.                                                                                                           |
-| `--enable-bridge-integration`                        | Habilita la integración Bridge para Liquidity Sourcing.                                                                                                                                                           |
-| `--horizon-url`                                      | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                                              |
-| `--instance-name`                                    | Nombre de la instancia SDP. Ejemplo: `SDP Testnet`.                                                                                                                                                               |
-| `--max-base-fee`                                     | La tarifa base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                                                |
-| `--max-invitation-resend-attempts`                   | El número máximo de intentos para reenviar una invitación a las Carteras Receptoras. Por defecto es `3`.                                                                                                          |
-| `--metrics-port`                                     | Puerto donde el servidor de métricas estará escuchando. Por defecto es `8002`.                                                                                                                                    |
-| `--metrics-type`                                     | Tipo de monitor de métricas. Opciones: `PROMETHEUS`. Por defecto es `PROMETHEUS`.                                                                                                                                 |
-| `--port`                                             | Puerto donde el servidor estará escuchando. Por defecto es `8000`.                                                                                                                                                |
-| `--recaptcha-site-key`                               | La clave del sitio 'reCAPTCHA v2 - No soy un robot' de Google.                                                                                                                                                    |
-| `--recaptcha-site-secret-key`                        | La clave SECRETA del sitio 'reCAPTCHA v2 - No soy un robot' de Google.                                                                                                                                            |
-| `--recaptcha-v3-min-score`                           | El umbral mínimo de puntuación para reCAPTCHA v3 (de 0.0 a 1.0, donde 1.0 es probablemente una buena interacción). Solo se usa cuando captcha-type es GOOGLE_RECAPTCHA_V3. Por defecto es `0.5`.                  |
-| `--reset-token-expiration-hours`                     | El tiempo de expiración en horas del Token de Restablecimiento. Por defecto es `24`.                                                                                                                              |
-| `--scheduler-payment-job-seconds`                    | El intervalo en segundos para los trabajos de pago que sincronizan transacciones entre SDP y TSS. Debe ser mayor a 5 segundos. Por defecto es `30`.                                                               |
-| `--scheduler-receiver-invitation-job-seconds`        | El intervalo en segundos para el trabajo de invitación a receptores que envía invitaciones a nuevos receptores. Debe ser mayor a 5 segundos. Por defecto es `30`.                                                 |
-| `--sep10-client-attribution-required`                | Si es true, la autenticación SEP-10 requiere que se proporcione y valide client_domain. Si es false, client_domain es opcional. Por defecto es `true`.                                                            |
-| `--sep10-signing-private-key`                        | La clave privada de la cuenta Stellar que firma las transacciones SEP-10. También se usa para firmar URLs.                                                                                                        |
-| `--sep10-signing-public-key`                         | La clave pública de la cuenta Stellar que firma las transacciones SEP-10. También se usa para firmar URLs.                                                                                                        |
-| `--sep24-jwt-secret`                                 | El secreto JWT usado para firmar el token JWT SEP-24.                                                                                                                                                             |
-| `--single-tenant-mode`                               | Esta opción habilita la función Modo Tenant Único. Cuando la multi-tenencia no es necesaria, esta opción evita la resolución de tenant siempre resolviendo al tenant por defecto configurado en la base de datos. |
-| `--sms-sender-type`                                  | Tipo de remitente SMS. Opciones: `DRY_RUN`, `TWILIO_SMS`, `TWILIO_WHATSAPP`, `AWS_SMS`. Por defecto es `DRY_RUN`.                                                                                                 |
-| `--tenant-xlm-bootstrap-amount`                      | La cantidad del activo nativo que será enviada a la cuenta de distribución del tenant desde la cuenta de distribución del host cuando se cree, si aplica. Por defecto es `5`.                                     |
-| `--twilio-account-sid`                               | El SID de la cuenta Twilio.                                                                                                                                                                                       |
-| `--twilio-auth-token`                                | El token de autenticación de la cuenta Twilio.                                                                                                                                                                    |
-| `--twilio-sendgrid-api-key`                          | La clave API de la cuenta Twilio SendGrid.                                                                                                                                                                        |
-| `--twilio-sendgrid-sender-address`                   | La dirección de email que Twilio SendGrid usará para enviar correos.                                                                                                                                              |
-| `--twilio-service-sid`                               | El ID de servicio usado dentro de Twilio para enviar mensajes.                                                                                                                                                    |
-| `--twilio-whatsapp-from-number`                      | El número de WhatsApp Business usado para enviar mensajes (con prefijo whatsapp:).                                                                                                                                |
-| `--twilio-whatsapp-receiver-invitation-template-sid` | El SID de contenido de Twilio para la plantilla de invitación de receptor WhatsApp (comienza con HX).                                                                                                             |
-| `--twilio-whatsapp-receiver-otp-template-sid`        | El SID de contenido de Twilio para la plantilla OTP de receptor WhatsApp (comienza con HX).                                                                                                                       |
-
-## Comando TSS
-
-El comando `tss` ejecuta el Servicio de Envío de Transacciones, que es responsable de enviar transacciones a la red Stellar.
-
-### Uso
-
-```bash
-stellar-disbursement-platform tss [flags]
-```
-
-### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                      |
-| :--------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Clave privada ed25519 compatible con Stellar usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, tomará como valor el de la opción `distribution-seed`. |
-| `--crash-tracker-type`                         | Tipo de rastreador de fallos. Opciones: `SENTRY`, `DRY_RUN`. Por defecto es `DRY_RUN`.                                                                                                           |
-| `--db-conn-max-idle-time-seconds`              | Tiempo máximo en segundos que una conexión puede estar inactiva antes de cerrarse. Por defecto es `10`.                                                                                          |
-| `--db-conn-max-lifetime-seconds`               | Tiempo máximo en segundos de vida útil para una sola conexión. Por defecto es `300`.                                                                                                             |
-| `--db-max-idle-conns`                          | Número máximo de conexiones inactivas de base de datos retenidas por pool. Por defecto es `2`.                                                                                                   |
-| `--db-max-open-conns`                          | Número máximo de conexiones abiertas de base de datos por pool. Por defecto es `20`.                                                                                                             |
-| `--distribution-account-encryption-passphrase` | Clave privada ed25519 compatible con Stellar usada para cifrar y descifrar las claves privadas de las cuentas de distribución de los tenants.                                                    |
-| `--distribution-public-key`                    | La clave pública de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                               |
-| `--distribution-seed`                          | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                               |
-| `--horizon-url`                                | La URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                             |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                               |
-| `--num-channel-accounts`                       | Número de cuentas de canal a utilizar para enviar transacciones. Por defecto es `2`.                                                                                                             |
-| `--queue-polling-interval`                     | Intervalo de sondeo (en segundos) para consultar la base de datos en busca de transacciones pendientes por procesar. Por defecto es `6`.                                                         |
-| `--tss-metrics-port`                           | Puerto donde el servidor de métricas estará escuchando. Por defecto es `9002`.                                                                                                                   |
-| `--tss-metrics-type`                           | Tipo de monitor de métricas. Opciones: `TSS_PROMETHEUS`. Por defecto es `TSS_PROMETHEUS`.                                                                                                        |
-
-## Comando DB
-
-El comando `db` proporciona utilidades para la gestión y migración de bases de datos. Realiza dos funciones principales:
-
-1. Ejecutar migraciones de bases de datos para varios esquemas (admin, auth, sdp, tss).
-2. Configurar activos y carteras basadas en la passphrase de la red.
-
-### Uso
-
-```bash
-stellar-disbursement-platform db [command] [flags]
-```
-
-### Subcomandos
-
-| Comando             | Descripción                                                      |
-| :------------------ | :--------------------------------------------------------------- |
-| `admin`             | Migraciones de admin para el módulo multi-tenant.                |
-| `auth`              | Migraciones del esquema de autenticación.                        |
-| `sdp`               | Migraciones del esquema SDP.                                     |
-| `setup-for-network` | Configura activos y carteras basadas en la passphrase de la red. |
-| `tss`               | Migraciones del esquema TSS.                                     |
-
----
-
-### DB Admin
-
-El comando `db admin` gestiona las migraciones para el esquema admin, que maneja la configuración de multi-tenancy.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db admin [command] [flags]
-```
-
-#### Subcomandos
-
-| Comando   | Descripción                             |
-| :-------- | :-------------------------------------- |
-| `migrate` | Ayudantes para migraciones de esquemas. |
-
-#### DB Admin Migrate
-
-El comando `migrate` te permite ejecutar migraciones hacia arriba o hacia abajo.
-
-**Uso**
-
-```bash
-stellar-disbursement-platform db admin migrate [command] [flags]
-```
-
-**Subcomandos**
-
-| Comando | Descripción                                               |
-| :------ | :-------------------------------------------------------- |
-| `up`    | Migra la base de datos hacia arriba [count] migraciones   |
-| `down`  | Migra la base de datos hacia abajo [count] migraciones    |
-
-**Ejemplos**
-
-```bash
-# Apply all pending migrations
-stellar-disbursement-platform db admin migrate up
-
-# Apply the next 2 migrations
-stellar-disbursement-platform db admin migrate up 2
-
-# Revert the last migration
-stellar-disbursement-platform db admin migrate down 1
-```
-
----
-
-### DB Auth
-
-El comando `db auth` gestiona las migraciones para el esquema de autenticación.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db auth [command] [flags]
-```
-
-#### Flags
-
-| Flag          | Descripción                                                                                                                                             |
-| :------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `--all`       | Aplica el comando a todos los tenants. Debe establecerse `--tenant-id` o `--all`, pero la opción `--all` se ignorará si `--tenant-id` está configurado. |
-| `--tenant-id` | El ID del tenant donde se aplicará el comando.                                                                                                          |
-
-#### Subcomandos
-
-| Comando   | Descripción                             |
-| :-------- | :-------------------------------------- |
-| `migrate` | Ayudantes para migraciones de esquemas. |
-
-#### DB Auth Migrate
-
-Similar a `admin migrate`, este comando acepta subcomandos `up` y `down`.
-
-**Ejemplos**
-
-```bash
-# Apply migrations for a specific tenant
-stellar-disbursement-platform db auth migrate up --tenant-id <tenant-id>
-
-# Apply migrations for all tenants
-stellar-disbursement-platform db auth migrate up --all
-```
-
----
-
-### DB SDP
-
-El comando `db sdp` gestiona las migraciones para el esquema SDP (Stellar Disbursement Platform), que contiene las tablas de lógica de negocio principal.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db sdp [command] [flags]
-```
-
-#### Flags
-
-| Flag          | Descripción                                                                                                                                             |
-| :------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `--all`       | Aplica el comando a todos los tenants. Debe establecerse `--tenant-id` o `--all`, pero la opción `--all` se ignorará si `--tenant-id` está configurado. |
-| `--tenant-id` | El ID del tenant donde se aplicará el comando.                                                                                                          |
-
-#### Subcomandos
-
-| Comando   | Descripción                             |
-| :-------- | :-------------------------------------- |
-| `migrate` | Ayudantes para migraciones de esquemas. |
-
-#### DB SDP Migrate
-
-Similar a `admin migrate`, este comando acepta subcomandos `up` y `down`.
-
-**Ejemplos**
-
-```bash
-# Apply migrations for a specific tenant
-stellar-disbursement-platform db sdp migrate up --tenant-id <tenant-id>
-
-# Apply migrations for all tenants
-stellar-disbursement-platform db sdp migrate up --all
-```
-
----
-
-### DB TSS
-
-El comando `db tss` gestiona las migraciones para el esquema TSS (Transaction Submission Service).
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db tss [command] [flags]
-```
-
-#### Subcomandos
-
-| Comando   | Descripción                             |
-| :-------- | :-------------------------------------- |
-| `migrate` | Ayudantes para migraciones de esquemas. |
-
-#### DB TSS Migrate
-
-Similar a `admin migrate`, este comando acepta subcomandos `up` y `down`.
-
-**Ejemplos**
-
-```bash
-# Apply all pending migrations
-stellar-disbursement-platform db tss migrate up
-```
-
----
-
-### DB Setup For Network
-
-El comando `db setup-for-network` configura los activos y carteras registrados en la base de datos basándose en la passphrase de la red. Inserta o actualiza las entradas de estas tablas según la passphrase de red configurada.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform db setup-for-network [flags]
-```
-
-#### Flags
-
-| Flag          | Descripción                                                                                                                                             |
-| :------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `--all`       | Aplica el comando a todos los tenants. Debe establecerse `--tenant-id` o `--all`, pero la opción `--all` se ignorará si `--tenant-id` está configurado. |
-| `--tenant-id` | El ID del tenant donde se aplicará el comando.                                                                                                          |
-
-#### Ejemplo
-
-```bash
-# Setup for a specific tenant
-stellar-disbursement-platform db setup-for-network --tenant-id <tenant-id>
-
-# Setup for all tenants
-stellar-disbursement-platform db setup-for-network --all
-```
-
-## Comando Auth
-
-El comando `auth` proporciona ayudantes para la gestión de autenticación, específicamente para agregar usuarios al sistema.
-
-### Uso
-
-```bash
-stellar-disbursement-platform auth [command] [flags]
-```
-
-### Subcomandos
-
-| Comando    | Descripción                 |
-| :--------- | :-------------------------- |
-| `add-user` | Agregar usuario al sistema. |
-
----
-
-### Auth Add User
-
-El comando `auth add-user` añade un nuevo usuario al sistema. El email debe ser único y la contraseña debe tener al menos 12 caracteres.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform auth add-user <email> <first name> <last name> [flags]
-```
-
-#### Flags
-
-| Flag          | Descripción                                                                                                                                                                                      |
-| :------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--owner`     | Establecer al usuario como propietario (superusuario). Por defecto es "false".                                                                                                                   |
-| `--password`  | Establece la contraseña del usuario. Debe tener al menos 12 caracteres de longitud. Si se omite, el comando generará una contraseña aleatoria.                                                   |
-| `--roles`     | Establece los roles del usuario. Deben estar separados por comas. Ejemplo: `role1, role2`. Roles disponibles: `owner`, `financial_controller`, `developer`, `business`, `initiator`, `approver`. |
-| `--tenant-id` | El ID del tenant al que se agregará el usuario.                                                                                                                                                  |
-
-#### Ejemplo
-
-Para agregar un nuevo usuario con roles específicos y una contraseña:
-
-```bash
-stellar-disbursement-platform auth add-user mary.jane@stellar.org Mary Jane \
---roles approver,initiator --password \
---tenant-id 'f347e6b0-249c-4960-b0d2-aebcf4c6a60d'
-```
-
-## Comando Cuentas de Canal
-
-El comando `channel-accounts` gestiona las cuentas de canal utilizadas para la presentación de transacciones.
-
-### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts [command] [flags]
-```
-
-### Flags
-
-| Flag                        | Descripción                                                                                        |
-| :-------------------------- | :------------------------------------------------------------------------------------------------- |
-| `--crash-tracker-type`      | Tipo de rastreador de fallas. Opciones: `SENTRY`, `DRY_RUN`. Por defecto es `DRY_RUN`.             |
-| `--distribution-public-key` | La clave pública de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal. |
-| `--tss-metrics-port`        | Puerto donde el servidor de métricas estará escuchando. Por defecto es `9002`.                     |
-| `--tss-metrics-type`        | Tipo de monitor de métricas. Opciones: `TSS_PROMETHEUS`. Por defecto es `TSS_PROMETHEUS`.          |
-
-### Subcomandos
-
-| Comando  | Descripción                                                     |
-| :------- | :-------------------------------------------------------------- |
-| `create` | Crear cuentas de canal.                                         |
-| `delete` | Eliminar una cuenta de canal especificada.                      |
-| `ensure` | Garantizar que exista un número específico de cuentas de canal. |
-| `verify` | Verificar que las cuentas de canal existan en la red.           |
-| `view`   | Listar claves públicas de todas las cuentas de canal.           |
-
----
-
-### Crear Cuentas de Canal
-
-El comando `create` crea cuentas de canal.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts create [count] [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                           |
-| :--------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Clave privada ed25519 compatible con Stellar usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, por defecto será el valor de la opción `distribution-seed`. |
-| `--distribution-account-encryption-passphrase` | Clave privada ed25519 compatible con Stellar usada para cifrar y descifrar las claves privadas de las cuentas de distribución de los tenants.                                                         |
-| `--distribution-seed`                          | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                                    |
-| `--horizon-url`                                | URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                                     |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                                    |
-
----
-
-### Eliminar Cuentas de Canal
-
-El comando `delete` elimina una cuenta de canal específica del almacenamiento y de la red.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts delete [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                           |
-| :--------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Clave privada ed25519 compatible con Stellar usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, por defecto será el valor de la opción `distribution-seed`. |
-| `--channel-account-id`                         | ID de la cuenta de canal a eliminar.                                                                                                                                                                  |
-| `--delete-all-accounts`                        | Eliminar todas las cuentas de canal gestionadas en la base de datos y en la red.                                                                                                                      |
-| `--distribution-account-encryption-passphrase` | Clave privada ed25519 compatible con Stellar usada para cifrar y descifrar las claves privadas de las cuentas de distribución de los tenants.                                                         |
-| `--distribution-seed`                          | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                                    |
-| `--horizon-url`                                | URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                                     |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                                    |
-
----
-
-### Garantizar Cuentas de Canal
-
-El comando `ensure` garantiza que exista el número especificado de cuentas de canal. Si no existen, las creará. Si existen más cuentas de canal de las especificadas, eliminará las cuentas en exceso.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts ensure <count> [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                           |
-| :--------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Clave privada ed25519 compatible con Stellar usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, por defecto será el valor de la opción `distribution-seed`. |
-| `--distribution-account-encryption-passphrase` | Clave privada ed25519 compatible con Stellar usada para cifrar y descifrar las claves privadas de las cuentas de distribución de los tenants.                                                         |
-| `--distribution-seed`                          | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                                    |
-| `--horizon-url`                                | URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                                     |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                                    |
-
-#### Ejemplo
-
-```bash
-stellar-disbursement-platform channel-accounts ensure 5
-```
-
----
-
-### Verificar Cuentas de Canal
-
-El comando `verify` verifica que todas las cuentas de canal en la base de datos existan en la red Stellar.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts verify [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                           |
-| :--------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Clave privada ed25519 compatible con Stellar usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, por defecto será el valor de la opción `distribution-seed`. |
-| `--delete-invalid-accounts`                    | Eliminar de almacenamiento las cuentas de canal que se verifiquen como inválidas en la red.                                                                                                           |
-| `--distribution-account-encryption-passphrase` | Clave privada ed25519 compatible con Stellar usada para cifrar y descifrar las claves privadas de las cuentas de distribución de los tenants.                                                         |
-| `--distribution-seed`                          | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                                    |
-| `--horizon-url`                                | URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                                     |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                                    |
-
----
-
-### Ver Cuentas de Canal
-
-El comando `view` lista las claves públicas de todas las cuentas de canal almacenadas actualmente en la base de datos.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform channel-accounts view [flags]
-```
-
-## Comando Cuenta de Distribución
-
-El comando `distribution-account` gestiona la cuenta de distribución.
-
-### Uso
-
-```bash
-stellar-disbursement-platform distribution-account [command] [flags]
-```
-
-### Flags
-
-| Flag                        | Descripción                                                                                        |
-| :-------------------------- | :------------------------------------------------------------------------------------------------- |
-| `--crash-tracker-type`      | Tipo de rastreador de fallas. Opciones: `SENTRY`, `DRY_RUN`. Por defecto es `DRY_RUN`.             |
-| `--distribution-public-key` | La clave pública de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal. |
-
-### Subcomandos
-
-| Comando  | Descripción                                     |
-| :------- | :---------------------------------------------- |
-| `rotate` | Rotar la cuenta de distribución para un tenant. |
-
----
-
-### Rotar Cuenta de Distribución
-
-El comando `rotate` rota la cuenta de distribución para un tenant.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform distribution-account rotate [flags]
-```
-
-#### Flags
-
-| Flag                                           | Descripción                                                                                                                                                                                           |
-| :--------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--channel-account-encryption-passphrase`      | Clave privada ed25519 compatible con Stellar usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, por defecto será el valor de la opción `distribution-seed`. |
-| `--distribution-account-encryption-passphrase` | Clave privada ed25519 compatible con Stellar usada para cifrar y descifrar las claves privadas de las cuentas de distribución de los tenants.                                                         |
-| `--distribution-seed`                          | La clave privada de la cuenta de distribución Stellar del HOST, usada para crear cuentas de canal.                                                                                                    |
-| `--horizon-url`                                | URL del servidor Stellar Horizon con el que esta aplicación se comunicará. Por defecto es `https://horizon-testnet.stellar.org/`.                                                                     |
-| `--max-base-fee`                               | La tarifa base máxima para enviar una transacción Stellar. Por defecto es `10000`.                                                                                                                    |
-| `--tenant-id`                                  | El ID del tenant donde se aplicará el comando.                                                                                                                                                        |
-| `--tenant-xlm-bootstrap-amount`                | La cantidad del activo nativo que se enviará a la cuenta de distribución del tenant desde la cuenta de distribución del host cuando se cree, si es aplicable. Por defecto es `5`.                     |
-
-#### Ejemplo
-
-Para rotar la cuenta de distribución de un tenant específico:
-
-```bash
-stellar-disbursement-platform distribution-account rotate --tenant-id 'f347e6b0-249c-4960-b0d2-aebcf4c6a60d'
-```
-
-## Comando Mensaje
-
-El comando `message` proporciona comandos relacionados con mensajería.
-
-### Uso
-
-```bash
-stellar-disbursement-platform message [command] [flags]
-```
-
-### Flags
-
-| Flag                                                 | Descripción                                                                                                                  |
-| :--------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------- |
-| `--aws-access-key-id`                                | El ID de clave de acceso de AWS.                                                                                             |
-| `--aws-region`                                       | La región de AWS.                                                                                                            |
-| `--aws-secret-access-key`                            | La clave secreta de acceso de AWS.                                                                                           |
-| `--aws-ses-sender-id`                                | La dirección de correo electrónico que AWS usará para enviar correos. Usa AWS SES.                                           |
-| `--aws-sns-sender-id`                                | El ID del remitente de la cuenta AWS que envía el mensaje SMS. Usa AWS SNS.                                                  |
-| `--message-sender-type`                              | Tipo de remitente del mensaje. Opciones: `TWILIO_SMS`, `TWILIO_WHATSAPP`, `TWILIO_EMAIL`, `AWS_SMS`, `AWS_EMAIL`, `DRY_RUN`. |
-| `--twilio-account-sid`                               | El SID de la cuenta Twilio.                                                                                                  |
-| `--twilio-auth-token`                                | El token de autenticación de la cuenta Twilio.                                                                               |
-| `--twilio-sendgrid-api-key`                          | La clave API de la cuenta Twilio SendGrid.                                                                                   |
-| `--twilio-sendgrid-sender-address`                   | La dirección de correo electrónico que Twilio SendGrid usará para enviar correos.                                            |
-| `--twilio-service-sid`                               | El ID del servicio utilizado dentro de Twilio para enviar mensajes.                                                          |
-| `--twilio-whatsapp-from-number`                      | El número de WhatsApp Business usado para enviar mensajes (con prefijo `whatsapp:`).                                         |
-| `--twilio-whatsapp-receiver-invitation-template-sid` | El SID de contenido de Twilio para la plantilla de invitación de receptor de WhatsApp (comienza con HX).                     |
-| `--twilio-whatsapp-receiver-otp-template-sid`        | El SID de contenido de Twilio para la plantilla OTP de receptor de WhatsApp (comienza con HX).                               |
-
-### Subcomandos
-
-| Comando | Descripción        |
-| :------ | :----------------- |
-| `send`  | Enviar un mensaje. |
-
----
-
-### Enviar Mensajes
-
-El comando `send` envía un mensaje a un destinatario.
-
-#### Uso
-
-```bash
-stellar-disbursement-platform message send [flags]
-```
-
-#### Flags
-
-| Flag             | Descripción                                                                                           |
-| :--------------- | :---------------------------------------------------------------------------------------------------- |
-| `--email`        | El correo electrónico al que se enviará el mensaje. Obligatorio si se envía un correo electrónico.    |
-| `--message`      | El texto del mensaje a enviar.                                                                        |
-| `--phone-number` | El número de teléfono al que se enviará el mensaje, en formato E.164. Obligatorio si se envía un SMS. |
-| `--title`        | El título que se establecerá en el correo electrónico. Obligatorio si se envía un correo electrónico. |
-
-#### Ejemplo
-
-```bash
-# Send an SMS
-stellar-disbursement-platform message send --phone-number "+1234567890" --message "Hello World" --message-sender-type TWILIO_SMS
-
-# Send an Email
-stellar-disbursement-platform message send --email "user@example.com" --title "Hello" --message "Hello World" --message-sender-type AWS_EMAIL
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.mdx
deleted file mode 100644
index af0f65afc2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/configuring-sdp.mdx
+++ /dev/null
@@ -1,241 +0,0 @@
----
-title: Configuración
-description: Comprende las opciones de configuración disponibles para la Plataforma de Desembolso Stellar (SDP)
-keywords:
-  - SDP
-  - configuration
-sidebar_position: 40
----
-
-Los servicios de la Plataforma de Desembolso Stellar pueden configurarse mediante un conjunto de opciones que se pasan por la línea de comandos o se establecen como variables de entorno. Dependiendo de cómo estés usando y desplegando la SDP, estas configuraciones pueden establecerse en un ConfigMap en Kubernetes, como variables de entorno en un contenedor Docker, pasarse como argumentos de línea de comandos, etc.
-
-En esta sección discutiremos las diferentes opciones de configuración disponibles para la SDP.
-
-:::tip[Notes]
-
-- Las configuraciones marcadas con 🔑 son sensibles y deben almacenarse de forma segura.
-- Todas las configuraciones pueden pasarse como variables de entorno o flags de CLI. Por ejemplo, la variable de entorno `BASE_URL` podría pasarse mediante el flag `--base-url`. Los flags de CLI tienen prioridad sobre las variables de entorno, aunque estas últimas son más convenientes.
-
-:::
-
-## Servicio principal de SDP
-
-Para obtener la configuración más actualizada, puedes ejecutar el siguiente comando en el [repositorio git del backend de stellar-disbursement-platform](https://github.com/stellar/stellar-disbursement-platform-backend):
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform serve --help
-```
-
-</CodeExample>
-
-### Configuración operativa
-
-La configuración operativa permite controlar métricas, registro y otros aspectos operativos del Servicio principal de SDP.
-
-- `PORT` - El puerto en el que el Servicio principal de SDP escuchará las solicitudes HTTP entrantes. Por defecto: 8000.
-- `LOG_LEVEL` - Determina el nivel de verbosidad de los registros. Opciones: "TRACE", "DEBUG", "INFO", "WARN", "ERROR", "FATAL", o "PANIC". Por defecto: "TRACE".
-- `METRICS_PORT` - El puerto en el que el Servicio principal de SDP expondrá sus métricas. Por defecto: 8002.
-- `METRICS_TYPE` - El tipo de métricas a exponer. Opciones: "PROMETHEUS". Por defecto: "PROMETHEUS".
-- `CRASH_TRACKER_TYPE` - El tipo de rastreador de fallos a usar. Opciones: "SENTRY", "DRY_RUN". Por defecto: "DRY_RUN".
-- `SENTRY_DSN` - 🔑 El DSN (clave de cliente) del proyecto Sentry. Si no se proporciona, no se usará Sentry.
-- `ENVIRONMENT` - El entorno donde la aplicación está ejecutándose. Ejemplo: "development", "staging", "production". Por defecto: "development".
-- `BASE_URL` - La URL base del servidor backend de SDP. Por defecto: "http://localhost:8000". Las URLs específicas para cada tenant se configurarán durante el [proceso de provisión de tenants](./advanced-configration#provisioning-tenants).
-- `SDP_UI_BASE_URL` - La URL base de la interfaz de usuario/dashboard de SDP usada para enviar el enlace de invitación cuando se crea un usuario nuevo. Las URLs específicas para cada tenant se configurarán durante el [proceso de provisión de tenants](./advanced-configration#provisioning-tenants).
-
-### Configuración de base de datos
-
-Las siguientes configuraciones están relacionadas con la base de datos PostgreSQL usada por el Servicio principal de SDP.
-
-- `DATABASE_URL` - 🔑 La cadena de conexión para la base de datos PostgreSQL. El formato es `postgres://usuario:contraseña@host:puerto/base_de_datos?sslmode=disable`. Por defecto: "postgres://localhost:5432/sdp?sslmode=disable".
-- `DB_MAX_OPEN_CONNS` - Máximo número de conexiones abiertas por pool a la base de datos. Por defecto: 20.
-- `DB_MAX_IDLE_CONNS` - Máximo número de conexiones inactivas mantenidas en el pool. Por defecto: 2.
-- `DB_CONN_MAX_IDLE_TIME_SECONDS` - Cierra conexiones inactivas después de N segundos. Por defecto: 10.
-- `DB_CONN_MAX_LIFETIME_SECONDS` - Recicla conexiones después de N segundos. Por defecto: 300.
-
-### Configuración de mensajería
-
-La configuración de mensajería permite configurar el servicio de mensajería usado para enviar mensajes a los destinatarios y a los usuarios del dashboard de SDP. La configuración predeterminada está establecida en "DRY_RUN", lo que significa que no se enviarán mensajes y estos se registrarán en la consola. Esto se recomienda solamente para propósitos de prueba.
-
-- `EMAIL_SENDER_TYPE`: El tipo de mensajero usado para enviar invitaciones a nuevos usuarios del dashboard. Opciones: "DRY_RUN", "TWILIO_EMAIL", "AWS_EMAIL". Por defecto: "DRY_RUN".
-- `SMS_SENDER_TYPE`: El tipo de mensajero usado para enviar mensajes SMS a los destinatarios. Opciones: "DRY_RUN", "TWILIO_SMS", "TWILIO_WHATSAPP", "AWS_SMS". Por defecto: "DRY_RUN".
-
-#### Configuración AWS
-
-Las siguientes configuraciones son necesarias cuando se usa AWS SES o SNS para enviar emails o mensajes SMS.
-
-- `AWS_ACCESS_KEY_ID` - 🔑 La ID de la clave de acceso de AWS.
-- `AWS_REGION` - La región AWS donde el servicio SES está disponible.
-- `AWS_SECRET_ACCESS_KEY` - 🔑 La clave secreta de acceso de AWS.
-- `AWS_SES_SENDER_ID` - El email que AWS SES usará como remitente al enviar correos electrónicos. Requerido cuando `EMAIL_SENDER_TYPE` está configurado a "AWS_EMAIL".
-- `AWS_SNS_SENDER_ID` - El ID del remitente para usar al enviar SMS usando AWS SNS. Requerido cuando `SMS_SENDER_TYPE` está configurado a "AWS_SMS".
-
-#### Configuración Twilio
-
-Las siguientes configuraciones son necesarias cuando `SMS_SENDER_TYPE=TWILIO_SMS`.
-
-- `TWILIO_ACCOUNT_SID` - 🔑 El SID de la cuenta Twilio.
-- `TWILIO_AUTH_TOKEN` - 🔑 El token de autenticación Twilio.
-- `TWILIO_SERVICE_SID` - El SID del servicio Twilio.
-
-Las siguientes configuraciones son necesarias cuando `SMS_SENDER_TYPE=TWILIO_WHATSAPP`.
-
-- `TWILIO_ACCOUNT_SID` - 🔑 El SID de la cuenta Twilio.
-- `TWILIO_AUTH_TOKEN` - 🔑 El token de autenticación Twilio.
-- `TWILIO_SERVICE_SID` - El SID del servicio Twilio.
-- `TWILIO_WHATSAPP_FROM_NUMBER` - El número de empresa WhatsApp usado para enviar mensajes (con prefijo whatsapp:).
-- `TWILIO_WHATSAPP_RECEIVER_INVITATION_TEMPLATE_SID` - El SID de contenido Twilio para la plantilla de invitación WhatsApp del receptor (comienza con HX).
-- `TWILIO_WHATSAPP_RECEIVER_OTP_TEMPLATE_SID` - El SID de contenido Twilio para la plantilla OTP WhatsApp del receptor (comienza con HX).
-
-Las siguientes configuraciones son necesarias cuando `EMAIL_SENDER_TYPE=TWILIO_EMAIL`.
-
-- `TWILIO_SENDGRID_API_KEY` - 🔑 La clave API para el servicio Twilio SendGrid (correo electrónico).
-- `TWILIO_SENDGRID_SENDER_ADDRESS` - La dirección de correo electrónico usada para enviar emails vía Twilio SendGrid.
-
-#### Configuración general de mensajería
-
-- `MAX_INVITATION_RESEND_ATTEMPTS` - El número máximo de intentos para reenviar (automáticamente) la invitación a las Carteras Receptoras. Por defecto: 3.
-
-### Configuración Stellar
-
-La configuración Stellar permite configurar cuentas, transacciones y otros ajustes relacionados con Stellar.
-
-- `NETWORK_PASSPHRASE` - La frase contraseña de la red Stellar. Por defecto "Test SDF Network ; September 2015".
-- `HORIZON_URL` - La URL del servidor Horizon para usar al enviar transacciones. Por defecto "https://horizon-testnet.stellar.org/".
-- `SEP10_SIGNING_PUBLIC_KEY` - La clave pública de la cuenta Stellar que firma las transacciones SEP-10. También se usa para firmar URLs.
-- `SEP10_SIGNING_PRIVATE_KEY` - 🔑 La clave privada de la cuenta Stellar que firma las transacciones SEP-10. También se usa para firmar URLs.
-- `MAX_BASE_FEE` - La tarifa base máxima para enviar una transacción Stellar. Por defecto: 10000.
-- `SEP10_CLIENT_ATTRIBUTION_REQUIRED` - Determina si se requiere la atribución del cliente SEP-10. Por defecto: true.
-
-#### Configuración de cuentas de canal
-
-La siguiente configuración es necesaria para usar la [CLI de cuentas de canal](./cli-manual#channel-accounts-command) para gestionar cuentas de canal.
-
-- `CHANNEL_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 Una clave secreta Stellar ed25519 (que empieza con `S`) usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, tomará por defecto el valor de `DISTRIBUTION_SEED`.
-
-#### Configuración de cuentas de distribución
-
-Las siguientes configuraciones están relacionadas con las cuentas de distribución usadas para enviar fondos a destinatarios. Esta configuración debe coincidir con la configuración en el Servicio principal de SDP.
-
-- `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 Una clave secreta Stellar ed25519 (que comienza con `S`) usada para cifrar/descifrar las claves privadas en memoria de las cuentas de distribución.
-- `DISTRIBUTION_PUBLIC_KEY` - La clave pública de la cuenta anfitrión de distribución Stellar. Usada para distribuir fondos, crear cuentas de canal y cuentas de distribución de tenants.
-- `DISTRIBUTION_SEED` - 🔑 La clave privada de la cuenta anfitrión de distribución Stellar. Usada para distribuir fondos, crear cuentas de canal y cuentas de distribución de tenants.
-
-### Configuración de seguridad
-
-La configuración de seguridad permite configurar los aspectos de seguridad del Servicio principal de SDP.
-
-- `CORS_ALLOWED_ORIGINS` - Especifica los dominios permitidos para hacer solicitudes cross-origin. "_" significa que todos los dominios están permitidos. Los dominios pueden contener comodines, por ejemplo, "https://_.example.com".
-- `SEP24_JWT_SECRET` - 🔑 El secreto usado para firmar el token JWT para transacciones SEP-24. Este secreto se usa durante el flujo de registro de la cartera receptora.
-
-#### Configuración de autenticación del dashboard
-
-Las siguientes configuraciones están relacionadas con la autenticación y autorización de usuarios del dashboard.
-
-- `RESET_TOKEN_EXPIRATION_HOURS` - El tiempo de expiración en horas del token para restablecer la contraseña. Por defecto: 24 (horas).
-- `EC256_PUBLIC_KEY` - La clave pública EC256 usada para validar la firma del token. Esta clave EC debe ser al menos tan fuerte como prime256v1 (P-256).
-- `EC256_PRIVATE_KEY` - 🔑 La clave privada EC256 usada para firmar el token de autenticación. Esta clave EC debe ser al menos tan fuerte como prime256v1 (P-256).
-- `DISABLE_MFA` - Deshabilita la autenticación multifactor (MFA) para los usuarios del dashboard de SDP.
-- `DISABLE_RECAPTCHA` - Deshabilita Google reCAPTCHA v2 para los usuarios del dashboard de SDP. Este flag no afecta el reCAPTCHA usado en el flujo SEP-24.
-
-#### Configuración Recaptcha
-
-Las siguientes configuraciones son necesarias cuando se usa Google reCAPTCHA v2 para proteger el Servicio principal de SDP contra bots. ReCaptcha se usa tanto para los usuarios del dashboard como para los receptores de fondos durante el flujo SEP-24.
-
-- `RECAPTCHA_SITE_KEY` - La clave del sitio Google reCAPTCHA v2 - No soy un robot.
-- `RECAPTCHA_SITE_SECRET_KEY` - 🔑 La clave secreta del sitio reCAPTCHA usada para validar las respuestas del reCAPTCHA.
-
-### Configuración de trabajos en segundo plano
-
-- `SCHEDULER_PAYMENT_JOB_SECONDS`: Intervalo en segundos para el trabajo que sincroniza pagos entre SDP y TSS. El mínimo es 5 s.
-- `SCHEDULER_RECEIVER_INVITATION_JOB_SECONDS`: Intervalo en segundos para el trabajo que envía invitaciones a receptores. El mínimo es 5 s.
-
-### Configuración multi-inquilino
-
-- `ADMIN_ACCOUNT`: El nombre de usuario de la cuenta de administrador usada para autenticar las solicitudes HTTP al servidor Admin. Las solicitudes dirigidas a Admin deben añadir el encabezado "Authorization", formateado como Base64 codificado `"ADMIN_ACCOUNT:ADMIN_API_KEY"`.
-- `ADMIN_API_KEY`: La clave API de la cuenta de administrador usada para autenticar las solicitudes HTTP al servidor Admin. Las solicitudes dirigidas a Admin deben añadir el encabezado "Authorization", formateado como Base64 codificado `"ADMIN_ACCOUNT:ADMIN_API_KEY"`.
-- `ADMIN_PORT`: el puerto del servidor Admin usado para crear y gestionar tenants. Por defecto es 8003.
-- `INSTANCE_NAME`: el nombre de la instancia SDP que se mostrará en el archivo `stellar.toml`. Ejemplo: "SDP Testnet".
-- `SINGLE_TENANT_MODE`: Cuando se establece a `"true"`, activa el modo de un solo inquilino, útil para desarrollo local o configuraciones de inquilino único. Además de establecerlo en true, necesitarás configurar el tenant predeterminado llamando a la solicitud [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx).
-- `TENANT_XLM_BOOTSTRAP_AMOUNT`: La cantidad de XLM que la cuenta Stella anfitriona depositará a la cuenta de distribución del tenant para su inicialización.
-
-### Configuración de integración del bridge
-
-Las siguientes configuraciones son necesarias cuando se usa la integración del Bridge.
-
-- `ENABLE_BRIDGE_INTEGRATION` - Determina si la integración del bridge está habilitada.
-- `BRIDGE_BASE_URL` - La URL base de la API del bridge. Por defecto: `"https://api.bridge.xyz"`.
-- `BRIDGE_API_KEY` - 🔑 La clave API para la integración del bridge. Requerido si `ENABLE_BRIDGE_INTEGRATION` está establecido como true.
-
-## Servicio de envío de transacciones (TSS)
-
-Para obtener la configuración más actualizada, puedes ejecutar el siguiente comando en el [repositorio git del backend de stellar-disbursement-platform](https://github.com/stellar/stellar-disbursement-platform-backend):
-
-<CodeExample>
-
-```bash
-./stellar-disbursement-platform tss --help
-```
-
-</CodeExample>
-
-### Configuración general
-
-- `QUEUE_POLLING_INTERVAL` - Intervalo de sondeo (segundos) para consultar la base de datos sobre transacciones pendientes para procesar. Por defecto: 6.
-
-### Configuración operativa
-
-La configuración operativa permite controlar métricas, registro y otros aspectos operativos del Servicio de envío de transacciones (TSS).
-
-- `LOG_LEVEL` - Determina el nivel de verbosidad de los registros. Opciones: "TRACE", "DEBUG", "INFO", "WARN", "ERROR", "FATAL", o "PANIC". Por defecto: "TRACE".
-- `TSS_METRICS_PORT` - El puerto en el que el TSS expondrá sus métricas. Por defecto: 9002.
-- `TSS_METRICS_TYPE` - El tipo de métricas a exponer. Opciones: "PROMETHEUS". Por defecto: "PROMETHEUS".
-- `CRASH_TRACKER_TYPE` - El tipo de rastreador de fallos a usar. Opciones: "SENTRY", "DRY_RUN". Por defecto: "DRY_RUN".
-- `SENTRY_DSN` - 🔑 El DSN (clave de cliente) del proyecto Sentry. Si no se proporciona, no se usará Sentry.
-- `ENVIRONMENT` - El entorno donde la aplicación está ejecutándose. Ejemplo: "development", "staging", "production". Por defecto: "development".
-
-### Configuración de base de datos
-
-Las siguientes configuraciones están relacionadas con la base de datos PostgreSQL usada por el Servicio principal de SDP.
-
-- `DATABASE_URL` - 🔑 La cadena de conexión para la base de datos PostgreSQL. El formato es `postgres://usuario:contraseña@host:puerto/base_de_datos?sslmode=disable`. Por defecto: "postgres://localhost:5432/sdp?sslmode=disable".
-- `DB_MAX_OPEN_CONNS` - Máximo número de conexiones abiertas por pool a la base de datos. Por defecto: 20.
-- `DB_MAX_IDLE_CONNS` - Máximo número de conexiones inactivas mantenidas en el pool. Por defecto: 2.
-- `DB_CONN_MAX_IDLE_TIME_SECONDS` - Cierra conexiones inactivas después de N segundos. Por defecto: 10.
-- `DB_CONN_MAX_LIFETIME_SECONDS` - Recicla conexiones después de N segundos. Por defecto: 300.
-
-### Configuración Stellar
-
-La configuración Stellar permite configurar cuentas, transacciones y otros ajustes relacionados con Stellar.
-
-- `NETWORK_PASSPHRASE` - La frase contraseña de la red Stellar. Por defecto "Test SDF Network ; September 2015".
-- `HORIZON_URL` - La URL del servidor Horizon para usar al enviar transacciones. Por defecto "https://horizon-testnet.stellar.org/".
-- `MAX_BASE_FEE` - La tarifa base máxima para enviar una transacción Stellar. Por defecto: 10000.
-
-#### Configuración de cuentas de canal
-
-Las siguientes configuraciones son necesarias para usar cuentas de canal para enviar transacciones a la red Stellar.
-
-- `NUM_CHANNEL_ACCOUNTS` - Número de cuentas de canal a utilizar para el envío de transacciones. Por defecto: 2.
-- `CHANNEL_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 Una clave secreta Stellar ed25519 (que comienza con `S`) usada para cifrar/descifrar las claves privadas de las cuentas de canal. Si no se establece, tomará por defecto el valor de la opción 'DISTRIBUTION_SEED'.
-
-#### Configuración de cuentas de distribución
-
-Las siguientes configuraciones están relacionadas con las cuentas de distribución usadas para enviar fondos a destinatarios. Esta configuración debe coincidir con la configuración en el Servicio principal de SDP.
-
-- `DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE` - 🔑 Una clave secreta Stellar ed25519 (que comienza con `S`) usada para cifrar/descifrar las claves privadas en memoria de las cuentas de distribución.
-- `DISTRIBUTION_PUBLIC_KEY` - La clave pública de la cuenta anfitrión de distribución Stellar. Usada para distribuir fondos, crear cuentas de canal y cuentas de distribución de tenants.
-- `DISTRIBUTION_SEED` - 🔑 La clave privada de la cuenta anfitrión de distribución Stellar. Usada para distribuir fondos, crear cuentas de canal y cuentas de distribución de tenants.
-
-## Dashboard
-
-El dashboard SDP es una aplicación web que permite a los usuarios gestionar sus cuentas, ver el historial de transacciones y más. Las variables de entorno pueden establecerse en un objeto global `window._env_` o como variables `process.env`. Todas las variables de entorno usadas en este repositorio están en el archivo `src/constants/envVariables.ts`, incluyendo sus tipos. La ubicación predeterminada del objeto `window._env_` es `public/settings/env-config.js`.
-
-### Configuración general
-
-- `API_URL` - La URL base del Servicio principal de SDP. Por defecto: "http://localhost:8000".
-- `STELLAR_EXPERT_URL` - La URL base del explorador Stellar Expert. Por defecto: "https://stellar.expert/explorer/testnet".
-- `HORIZON_URL` - La URL base del servidor Horizon. Por defecto: "https://horizon-testnet.stellar.org".
-- `RECAPTCHA_SITE_KEY` - La clave del sitio Google reCAPTCHA v2 - No soy un robot. Esta clave debe coincidir con la utilizada en el Servicio principal de SDP.
-- `SINGLE_TENANT_MODE` - Cuando se establece a `"true"`, activa el modo de un solo inquilino, útil para desarrollo local o configuraciones de inquilino único. Además de establecerlo en true, necesitarás configurar el tenant predeterminado llamando a la solicitud [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx). Por defecto: "false".
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
deleted file mode 100644
index d445e1bbb5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/deploy-the-sdp.mdx
+++ /dev/null
@@ -1,112 +0,0 @@
----
-title: Despliegue
-sidebar_position: 30
----
-
-## Despliegue mediante Helm Charts
-
-### Requisitos mínimos del sistema
-
-- **Cuentas Stellar**: Necesitarás una **Cuenta de Distribución** (con fondos) y una **Cuenta de Firma SEP-10**.
-- **Certificados**: Al ejecutar el SDP en una configuración multiusuario, necesitarás adquirir certificados TLS comodín para facilitar la provisión de usuarios, ya que el SDP utiliza subdominios para diferenciar entre ellos. Esto te permitirá provisionar usuarios sin tener que configurar manualmente certificados TLS para cada uno. Puedes usar un servicio como [Let's Encrypt](https://letsencrypt.org/) o [Namecheap](https://www.namecheap.com/security/ssl-certificates/) para obtener estos certificados.
-
-| Componente     | Requisito | Notas                                                                          |
-| :------------- | :-------- | :----------------------------------------------------------------------------- |
-| **Kubernetes** | v1.19+    | Para despliegue con Helm                                                       |
-| **Helm**       | v3.14.0+  | Para despliegue con Helm                                                       |
-| **PostgreSQL** | v14.0+    | Requerido para ambos métodos de despliegue                                     |
-| **RAM**        | 4GB+      | Memoria mínima recomendada para ejecutar la pila completa en modo multiusuario |
-
-### Instalando el Chart
-
-#### 1. Agregar el Repositorio Helm de Stellar
-
-Agrega el repositorio oficial de charts Helm de Stellar a tu cliente Helm local:
-
-```shell
-helm repo add stellar https://helm.stellar.org/charts
-```
-
-#### 2. Preparar la Configuración
-
-Descarga el archivo de configuración mínima para usarlo como base:
-
-```shell
-curl -LJO https://raw.githubusercontent.com/stellar/stellar-disbursement-platform-backend/main/helmchart/sdp/minimal-values.yaml
-```
-
-Los siguientes parámetros pueden establecerse en el archivo `minimal-values.yaml` o sobrescribirse directamente mediante la CLI durante la instalación:
-
-- `global.distributionPublicKey`: Clave pública de la cuenta de distribución.
-- `global.distributionPrivateKey`: Clave privada de la cuenta de distribución.
-- `global.sep10PublicKey`: Clave pública para la autenticación SEP-10.
-- `global.sep10PrivateKey`: Clave privada para la autenticación SEP-10.
-- `global.isPubnet`: Establecer en `true` para Mainnet.
-
-Consulta el [README del Helm Chart](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/helmchart/sdp/README.md#parameters) para obtener una lista completa de parámetros.
-
-:::tip
-
-Hay una explicación más detallada de cómo configurar el SDP en la [Guía de Configuración](configuring-sdp).
-
-:::
-
-#### 3. Instalar el Chart
-
-Instala el chart usando tu archivo de valores personalizado. Puedes sobrescribir valores directamente mediante la CLI o modificar el archivo `minimal-values.yaml`.
-
-```shell
-helm install sdp -f minimal-values.yaml stellar/stellar-disbursement-platform \
-     --set "global.distributionPublicKey=<YOUR_KEY>" \
-     --set "global.distributionPrivateKey=<YOUR_SECRET>" \
-     --set "global.sep10PublicKey=<YOUR_KEY>" \
-     --set "global.sep10PrivateKey=<YOUR_SECRET>"
-```
-
-## Despliegue mediante Docker Compose
-
-Esta sección describe cómo desplegar el SDP usando Docker Compose para un entorno similar a producción. A diferencia de la configuración de desarrollo, esta configuración usa imágenes precompiladas para producción y requiere la configuración explícita de variables de entorno y secretos.
-
-### Requisitos mínimos del sistema
-
-- **Cuentas Stellar**: Necesitarás una **Cuenta de Distribución** (con fondos) y una **Cuenta de Firma SEP-10**.
-- **Acceso a la red**: Acceso de salida a la red Stellar (Horizon/Soroban) y a cualquier integración de terceros (Twilio, AWS SES, etc.).
-
-| Componente | Requisito | Notas                                                     |
-| :--------- | :-------- | :-------------------------------------------------------- |
-| **Docker** | v20.10+   | Requerido para la orquestación de contenedores            |
-| **RAM**    | 4GB+      | Memoria mínima recomendada para ejecutar la pila completa |
-
-### Pasos para el despliegue
-
-#### 1. Clona el Repositorio
-
-```shell
-git clone https://github.com/stellar/stellar-disbursement-platform-backend.git
-cd stellar-disbursement-platform-backend
-```
-
-#### 2. Crear archivo de entorno
-
-Copia el archivo de entorno de ejemplo.
-
-```shell
-cp dev/.env.example dev/.env
-```
-
-#### 3. Configura las variables de entorno
-
-Edita `dev/.env` y completa las siguientes variables con las claves de tus cuentas Stellar:
-
-- `DISTRIBUTION_PUBLIC_KEY`
-- `DISTRIBUTION_SEED`
-- `SEP10_SIGNING_PUBLIC_KEY`
-- `SEP10_SIGNING_PRIVATE_KEY`
-
-Para despliegue en mainnet, establece: _ `NETWORK_TYPE=pubnet` _ `NETWORK_PASSPHRASE=Public Global Stellar Network ; September 2015` _ `HORIZON_URL=https://horizon.stellar.org` _ `DISABLE_MFA=false` (Impuesto por seguridad)
-
-#### 4. Iniciar los Servicios
-
-```shell
-docker compose -f dev/docker-compose.yml up -d
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.mdx
deleted file mode 100644
index 81978f0456..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/design-and-architecture.mdx
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Arquitectura
-sidebar_position: 20
----
-
-La Plataforma de Desembolso Stellar consta de tres servicios desplegados juntos:
-
-- **Dashboard**: la interfaz de usuario que los administradores usan para iniciar y rastrear el progreso de los desembolsos
-- **Servicio Central SDP**: el servicio principal de backend que realiza varias funciones:
-  - **API del Dashboard**: la API que usa la interfaz frontal para todas las solicitudes de desembolso. La API está documentada [aquí](../api-reference)
-  - **API Admin**: la API que usa la organización anfitriona para administrar la provisión y configuración de inquilinos. La API está documentada [aquí](../api-reference/admin)
-  - **Servicio de Mensajería**: un proceso recurrente que envía mensajes de texto a los usuarios para invitarlos a descargar la wallet seleccionada para un desembolso en particular y verificar su teléfono con un OTP
-  - **Registro de Wallet**: una aplicación web que registra a un destinatario recogiendo y verificando su código OTP e información de verificación a través del protocolo [SEP-24: Depósito y Retiro Hospedado](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md) de Stellar
-- **Servicio de Envío de Transacciones**: el servicio que envía todas las transacciones de pago a la red Stellar. Este servicio está diseñado para maximizar el rendimiento de los pagos, manejar la cola y la reaplicación/control de errores de forma elegante
-
-## Dependencias {#dependencies}
-
-- **Orquestación de Contenedores**: el SDP se empaqueta como contenedores Docker y puede desplegarse en Kubernetes o AWS Fargate. SDF proporciona un Helm Chart para Kubernetes
-- **Postgres**: el SDP usa un servidor de base de datos Postgres para todos sus servicios
-- **Twilio o AWS SNS y SES**: el servicio de mensajería del SDP usa mensajes SMS/WhatsApp vía Twilio o AWS SNS y correos administrativos para configuración y recuperación de cuentas de organizaciones vía AWS SES o Twilio SendGrid
-- **Cuentas Stellar**:
-  - Cuenta de Distribución: el SDP requiere acceso a al menos una cuenta Stellar financiada para realizar pagos al destinatario
-  - Cuenta de Autenticación SEP-10: el SDP necesita una cuenta Stellar para el protocolo de autenticación mutua [SEP-10: Autenticación Web Stellar](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) usado para conectar aplicaciones wallet
-
-## Diagrama de Arquitectura
-
-![Architecture Diagram](/assets/SDP/SDP2-2.png)
-
-### Roles de Usuario {#user-roles}
-
-El SDP define los siguientes roles de usuario:
-
-- **Admin Anfitrión**: la organización que aloja la instancia SDP y administra la provisión y configuración de los inquilinos a través de la API `Tenant Admin`
-- **Usuario del Dashboard**: un usuario que pertenece a un inquilino y usa el Dashboard del SDP para crear y administrar desembolsos, destinatarios y otros datos específicos del inquilino.
-- **Usuario API**: un usuario que pertenece a un inquilino y utiliza la `Dashboard API` para crear y gestionar desembolsos, destinatarios y otros datos específicos del inquilino de forma programática
-- **Receptores**: los usuarios finales que reciben los fondos enviados a través del SDP. Los receptores pueden usar una aplicación wallet que soporte SEP-24 para registro automático, o recibir fondos directamente en su cuenta Stellar.
-
-### Flujo de Trabajo {#workflow}
-
-1. El admin anfitrión usa la API `Tenant Admin` para proveer y administrar inquilinos.
-2. `Usuario del Dashboard` y `Usuario API` usan el Servicio Central SDP para enviar desembolsos y administrar/invitar a otros usuarios. Esto puede hacerse vía la interfaz del Dashboard o directamente mediante la `Dashboard API`.
-3. Para pagos que requieren registro SEP-24, el `Servicio Central SDP` envía un mensaje para notificar a los receptores. El mensaje contiene un enlace profundo que abre la wallet destino, lo que a su vez inicia el **flujo de depósito SEP-24** y registra a los receptores.
-4. El Servicio de Envío de Transacciones saca los pagos listos para ser procesados y luego los envía a la red Stellar mediante Cuentas Canal.
-
-## Base de Datos y Esquemas {#database}
-
-El SDP usa una base de datos Postgres para todos sus servicios. El esquema de la base de datos es gestionado por el Servicio Central SDP y está versionado en el código. El esquema de la base de datos está diseñado para ser consciente de los inquilinos, lo que significa que cada inquilino tiene su propio conjunto de tablas y datos. Esto permite que el SDP sea multi-inquilino y soporte varias organizaciones usando la misma instancia.
-
-Hay 3 tipos de esquemas en la base de datos:
-
-- **Esquema Admin**: contiene tablas para administrar inquilinos. Este esquema es usado por la API Admin para gestionar la configuración y provisión de inquilinos.
-- **Esquema TSS**: contiene tablas para administrar transacciones. Este esquema es usado por el Servicio de Envío de Transacciones para manejar el estado de las transacciones de pago.
-- **Esquemas de Inquilinos**: cada inquilino tiene su propio esquema que contiene tablas para administrar desembolsos, destinatarios y otros datos específicos del inquilino. Estos esquemas están prefijados con `sdp_`.
-
-## Multi-inquilino {#multi-tenancy}
-
-El SDP puede desplegarse en configuración multi-inquilino, donde múltiples organizaciones comparten la misma instancia del SDP. Cada organización se denomina inquilino y tiene su propio conjunto de datos y configuración. Una organización anfitriona puede administrar múltiples inquilinos y su configuración mediante la API Admin.
-
-### Resolución de Inquilinos {#tenant-resolution}
-
-El SDP utiliza una estrategia de resolución de inquilinos para determinar a qué inquilino pertenece una solicitud. La resolución de inquilinos solo es necesaria para solicitudes no autenticadas, ya que las autenticadas incluyen la información del inquilino en el token JWT.
-
-- **Encabezado**: el encabezado `SDP-Tenant-Name` se usa para especificar el nombre del inquilino en la solicitud. Cuando está presente, este encabezado se usa para intentar resolver el inquilino.
-- **Subdominio**: el SDP puede usar el subdominio de la URL de la solicitud para resolver el inquilino. Por ejemplo, `tenant1.sdp.backend.test` resolvería al inquilino `tenant1`.
-
-La prioridad de resolución es la siguiente: token JWT (solicitudes autenticadas) > Encabezado > Subdominio.
-
-#### Modo de Inquilino Único {#single-tenant-mode}
-
-Cuando el modo inquilino único está habilitado usando la variable de entorno `SINGLE_TENANT_MODE`, todos los inquilinos se resolverán automáticamente al inquilino predeterminado. Un inquilino predeterminado se establece llamando a la API [`POST /tenants/default-tenant`](../api-reference/default-tenant.api.mdx).
-
-El inquilino predeterminado es útil para propósitos de desarrollo o cuando el SDP es usado por una sola organización. Esto permite a la organización omitir especificar el inquilino en cada solicitud y simplifica la configuración operativa del SDP, eliminando la necesidad de proveer certificados TLS comodín para configuraciones multi-inquilino.
-
-#### Resolución de Subdominios {#subdomain-resolution}
-
-Cuando se ejecuta el SDP en modo multi-inquilino, el SDP usa el subdominio de la URL de la solicitud para resolver el inquilino. Por ejemplo, `tenant1.sdp.backend.test` resolvería al inquilino `tenant1`. Esto permite que el SDP diferencie entre inquilinos sin requerir que el nombre del inquilino se especifique en la solicitud.
-
-La resolución de subdominios es especialmente importante para el proceso de Registro de Wallet, ya que el SDP depende de los subdominios para diferenciar entre inquilinos durante el flujo de depósito SEP-24. Los dominios principales, que contienen el nombre del inquilino como subdominio, se utilizan durante el proceso de registro por el SDP para identificar al inquilino y dirigir la solicitud de registro de wallet al contexto correcto del inquilino.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
deleted file mode 100644
index e58c4a6992..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/getting-started.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Comenzar
-sidebar_position: 10
----
-
-Esta guía cubre cómo ejecutar la Plataforma de Desembolso Stellar localmente, enviar un desembolso de muestra y reclamarlo mediante la cartera demo en Testnet. Considera este recorrido como un entorno de aprendizaje en lugar de la ruta para implementaciones en producción.
-
-### Requisitos previos
-
-- **Docker:** Asegúrate de tener Docker instalado en tu sistema. Si no, puedes descargarlo desde [aquí](https://www.docker.com/products/docker-desktop) y arrancarlo una vez instalado.
-- **Git:** Necesitarás Git para clonar el repositorio. Puedes descargarlo desde [aquí](https://git-scm.com/downloads).
-- **Go:** Requerido para generar tu archivo de entorno. Instálalo desde [aquí](https://golang.org/dl/).
-- **jq:** Útil para scripts opcionales y diagnóstico. Puedes descargarlo desde [aquí](https://jqlang.org/download/)
-
-Para macOS y Linux, puedes instalarlo con Homebrew:
-
-```bash
-brew install --cask docker
-brew install git go jq
-```
-
-### Clona el repositorio
-
-```bash
-git clone https://github.com/stellar/stellar-disbursement-platform-backend.git
-cd stellar-disbursement-platform-backend
-```
-
-### Ejecuta el asistente
-
-```bash
-make setup
-```
-
-En las indicaciones, elige según lo siguiente. El asistente genera y financia las cuentas firmantes SEP-10 y de distribución (testnet), inicia Docker y muestra las credenciales del tenant.
-
-```
-? Select an existing run configuration or create new:
-▸ Create new configuration
-✔ Setup name (optional): <sdp-setup-name>
-? Select network:
-▸ testnet
-? Select tenant mode:
-▸ single-tenant
-? Account setup:
-▸ Generate new accounts
-? Launch local environment now (project=sdp-sdp-test, setup=<sdp-setup-name>)? [Y/n] Y
-? Initialize tenants and users? [y/N] Y
-```
-
-Al finalizar deberías ver:
-
-```
-🎉🎉🎉🎉 SUCCESS! 🎉🎉🎉🎉
-Single tenant mode - Login URL:
-🔗Default tenant: http://localhost:3000
-  username: owner@default.local  password: Password123!
-```
-
-### Inicia sesión en el SDP
-
-Abre http://localhost:3000 e inicia sesión usando las credenciales de administrador generadas por el asistente de configuración (organización: default). ![Inicio de sesión](/assets/SDP/SDP32.png)
-
-### Envía un desembolso de prueba
-
-Haz clic en `New Disbursement +` en el panel; verás una cuenta de distribución financiada lista para usar:
-
-- Elige número de teléfono como Tipo de Contacto de Registro. Este es el canal que los destinatarios usarán para recibir mensajes.
-- Selecciona XLM como el activo a desembolsar.
-- Escoge Demo Wallet como la cartera receptora.
-- Elige Fecha de Nacimiento como el método de verificación; los destinatarios la ingresarán para confirmar su identidad.
-- Asigna un nombre al desembolso. ![Detalles del Desembolso](/assets/SDP/SDP33.png)
-
-Crea y carga un archivo de desembolso:
-
-- Descarga la plantilla a través de `Download CSV Template`; incluye todas las columnas requeridas.
-- Actualiza los números de teléfono de marcador de posición o inválidos antes de usarla.
-- La columna de verificación contiene los datos de identidad que deben coincidir los destinatarios. ![CSV de Desembolso](/assets/SDP/SDP34.png)
-
-Haz clic en el botón Revisar. Cuando estés listo para comenzar el desembolso, haz clic en el botón "Confirm disbursement". En Detalles del Desembolso verás el pago en estado `Ready`, lo que significa que el receptor aún no ha aceptado la invitación y el pago. ![Panel de Desembolso](/assets/SDP/SDP35.png)
-
-### Recibir pago
-
-:::note
-
-Esta sección muestra el flujo del Demo Wallet solo en Testnet para que puedas observar la experiencia del receptor mientras ejecutas SDP localmente. Para producción o integraciones con carteras reales, sigue la guía en [Making Your Wallet SDP-Ready](./making-your-wallet-sdp-ready.mdx).
-
-:::
-
-Reclama el pago en la cartera demo creando primero una cartera:
-
-- Abre la cartera demo: http://localhost:4000.
-- Haz clic en `Generate Keypair for new account` para crear un par de claves; guarda las claves pública y secreta si planeas reutilizar la cuenta.
-- Haz clic en `Create account` para crear la cuenta en la testnet de Stellar (la cuenta inicia con 10,000 XLM). ![Creación de Demo Wallet](/assets/SDP/SDP36.png)
-
-Para recibir tu pago, inicia un depósito SEP-24:
-
-- En Activo XLM, haz clic en `Add Home Domain`, ingresa `localhost:8000` y haz clic en `Override`.
-- En el menú desplegable `Select action`, elige `SEP-24 Deposit`, luego haz clic en `Start`. ![Depósito SEP-24](/assets/SDP/SDP37.png)
-
-Verifica tu identidad:
-
-- Cuando se solicite, ingresa el mismo número de teléfono usado en el CSV de desembolso.
-- Completa la verificación OTP y Fecha de Nacimiento. El OTP aparece en los registros del contenedor `sdp-api` (por ejemplo, “Aquí está el código de verificación de 6 dígitos que solicitaste ...”). ![Código OTP](/assets/SDP/SDP38.png) ![Verificación PII](/assets/SDP/SDP39.png)
-
-### Monitorización
-
-- En el panel SDP, el pago cambia de `Ready` a `PENDING` durante el flujo de la cartera, y luego a `Success` cuando los fondos se depositan. ![Panel SDP](/assets/SDP/SDP40.png)
-
-- En la cartera demo, el saldo se actualiza reflejando el nuevo monto. ![Saldo de Demo Wallet](/assets/SDP/SDP41.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.mdx
deleted file mode 100644
index 5b049490cf..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/making-your-wallet-sdp-ready.mdx
+++ /dev/null
@@ -1,176 +0,0 @@
----
-title: Preparar tu Wallet para SDP
-sidebar_position: 80
----
-
-Recuerda que cualquier instancia de SDP necesitará un acuerdo con un proveedor de wallet antes de enviar desembolsos a esa wallet. Esto asegura que las wallets estén cómodas recibiendo fondos de tu organización y regula cualquier arreglo comercial entre las organizaciones. La wallet necesitará incluir en su lista blanca el dominio del SDP antes de que el SDP pueda enviar desembolsos a esa wallet. Cuando se añade el dominio de la wallet a un SDP, se está incluyendo efectivamente en la lista blanca por parte del SDP. Ambas partes listando a la otra les permite recuperar el archivo stellar.toml y verificar la clave de firma necesaria para el handshake [SEP-10].
-
-En esta página, cubriremos los aspectos técnicos de la integración SDP-Wallet, incluyendo cómo añadir una Wallet en la base de datos del SDP, cómo validar y soportar los enlaces de registro usando [deep linking] de aplicaciones móviles, cómo iniciar el flujo de registro de usuario en la wallet usando [SEP-24], y un enfoque recomendado para manejar [deferred deep linking].
-
-## Agregar una Wallet a un SDP
-
-La lista predeterminada de wallets SDP depende de qué red se esté usando (testnet o pubnet). La red se pasa como variable de entorno y luego la lista de wallets se puede inicializar apropiadamente al iniciar el SDP mediante el comando CLI `./stellar-disbursement-platform db setup-for-network`, de acuerdo con una lista fija de wallets conocidas. Alternativamente, las wallets se pueden insertar directamente en la base de datos del SDP mediante un comando SQL. Ambos métodos requieren añadir el nombre de la wallet, página principal, dominio cliente SEP-10 y esquema de deep link.
-
-Para insertarlo directamente en la base de datos, actualiza tus valores y ejecuta la siguiente consulta en Postgres. Asegúrate de revisar primero tu base de datos y el espacio de nombres.
-
-<CodeExample>
-
-```sql
-INSERT INTO wallets (name, homepage, deep_link_schema, sep_10_client_domain)
-VALUES ('Vibrant Assist', 'https://vibrantapp.com', 'https://vibrantapp.com/sdp', 'api.vibrantapp.com');
-```
-
-</CodeExample>
-
-Para configurar una wallet mediante código, añádela a la sección de testnet o pubnet de `DefaultWalletsNetworkMap`. Esto se usará cuando ejecutes el comando CLI `./stellar-disbursement-platform db setup-for-network`, que actualiza la base de datos SDP y hace que la wallet esté disponible para nuevos desembolsos. Añade tu nueva wallet siguiendo el mismo formato ya presente en el código.
-
-<CodeExample>
-
-```go
-var DefaultWalletsNetworkMap = WalletsNetworkMapType{
-	utils.PubnetNetworkType: {
-		{
-			Name:              "Vibrant Assist",
-			Homepage:          "https://vibrantapp.com/assist",
-			DeepLinkSchema:    "https://vibrantapp.com/sdp",
-			SEP10ClientDomain: "api.vibrantapp.com",
-		},
-	},
-	utils.TestnetNetworkType: {
-		{
-			Name:              "Vibrant Assist",
-			Homepage:          "https://vibrantapp.com",
-			DeepLinkSchema:    "https://vibrantapp.com/sdp-dev",
-			SEP10ClientDomain: "api-dev.vibrantapp.com",
-		},
-		{
-			Name:              "Demo Wallet",
-			Homepage:          "https://demo-wallet.stellar.org",
-			DeepLinkSchema:    "https://demo-wallet.stellar.org",
-			SEP10ClientDomain: "demo-wallet-server.stellar.org",
-		},
-	},
-}
-```
-
-</CodeExample>
-
-## Experiencia de Registro del Receptor
-
-La experiencia de registro del receptor es fundamental para que esta aplicación sea fluida y fácil de usar. Esto requiere que la wallet soporte [deferred deep linking], que se discutirá en una sección posterior. Una buena descripción de la experiencia de registro es la siguiente:
-
-1. El receptor recibe un mensaje de invitación notificándole que tiene un pago pendiente de la organización y se le invita a hacer clic en un [deep link] para abrir o instalar y abrir una aplicación de wallet
-
-2. Cuando el receptor abre la aplicación de wallet, la wallet inmediatamente integra al receptor, crea una cuenta Stellar y trustline para el activo deseado, inicia una transacción de depósito [SEP-24] con el SDP, y abre la página web de registro del SDP como una pantalla superpuesta/iframe dentro de la app.
-
-3. El usuario confirma su número de teléfono y fecha de nacimiento directamente con el SDP, sin compartir datos con la wallet, y después de concluir el registro, se le redirige a la aplicación de wallet. Aquí están las pantallas que demuestran estos pasos:
-
-   ![Flujo de Registro](/assets/SDP/SDP25.png)
-
-4. El usuario recibe el pago en segundos
-
-## Enlace Profundo de Registro
-
-Una vez que el usuario ha instalado la aplicación de wallet, esta debe ser capaz de interpretar un [deep link] que siga el formato registrado en el SDP para iniciar el [Procedimiento de Registro de Wallet](#wallet-registration-procedure). El formato del deep link soportado por el SDP sigue este formato:
-
-```url
-https://<host-with-optional-path>?asset=<asset>&domain=<domain>&name=<name>&signature=<signature>
-```
-
-- `asset`: el activo Stellar.
-- `domain`: el dominio que aloja el archivo `stellar.toml` del SDP. La wallet necesitará usarlo tanto para obtener el archivo `stellar.toml`, como para rellenar el campo `home_domain` en la transacción GET challenge [SEP-10].
-- `name`: el nombre de la organización que envía los pagos.
-- `signature`: una firma de la clave de firma [SEP-10] del SDP.
-
-:::info
-
-Ten en cuenta que el deep link es específico para cada SDP, organización pagadora y activo. No es específico para cada receptor individual. No hay riesgo en compartir el enlace con receptores que forman parte del mismo desembolso. El enlace será el mismo para múltiples receptores, y estos probarán su identidad como parte del flujo de depósito [SEP-24].
-
-:::
-
-A continuación, un ejemplo de enlace de registro (firmado)
-
-```url
-https://vibrantapp.com/sdp-dev?asset=USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5&domain=ap-stellar-disbursement-platform-backend-dev.stellar.org&name=Stellar+Test&signature=fea6c5e805a29b903835bea2f6c60069113effdf1c5cb448d4948573c65557b1d667bcd176c24a94ed9d54a1829317c74f39319076511512a3e697b4b746ae0a
-```
-
-En este ejemplo, el host es `https://vibrantapp.com/sdp-dev` y la firma es el resultado de firmar la URL (sin firma) abajo usando la clave de firma [SEP-10] `SBUSPEKAZKLZSWHRSJ2HWDZUK6I3IVDUWA7JJZSGBLZ2WZIUJI7FPNB5`, con la clave pública siendo `GBFDUUZ5ZYC6RAPOQLM7IYXLFHYTMCYXBGM7NIC4EE2MWOSGIYCOSN5F`:
-
-```url
-https://vibrantapp.com/sdp-dev?asset=USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5&domain=ap-stellar-disbursement-platform-backend-dev.stellar.org&name=Stellar+Test
-```
-
-En este ejemplo, la firma es `fea6c5e805a29b903835bea2f6c60069113effdf1c5cb448d4948573c65557b1d667bcd176c24a94ed9d54a1829317c74f39319076511512a3e697b4b746ae0a`.
-
-A continuación, un fragmento JavaScript demostrando cómo verificar la firma:
-
-```js
-#!/usr/bin/env node
-
-const { Keypair } = require("stellar-sdk");
-
-// The SDP's stellar.toml SIGNING_KEY
-//
-// For security, this should ideally be fetched from
-// https://<domain>/.well-known/stellar.toml on demand
-const keypair = Keypair.fromPublicKey(
-  "GBFDUUZ5ZYC6RAPOQLM7IYXLFHYTMCYXBGM7NIC4EE2MWOSGIYCOSN5F",
-);
-console.log("public key:", keypair.publicKey());
-
-let url =
-  "https://vibrantapp.com/sdp-dev?asset=USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5&domain=ap-stellar-disbursement-platform-backend-dev.stellar.org&name=Stellar%20Test";
-let signature =
-  "fea6c5e805a29b903835bea2f6c60069113effdf1c5cb448d4948573c65557b1d667bcd176c24a94ed9d54a1829317c74f39319076511512a3e697b4b746ae0a";
-
-console.log(
-  "verified:",
-  keypair.verify(
-    Buffer.from(url.toString(), "utf8"),
-    Buffer.from(signature, "hex"),
-  ),
-);
-```
-
-### Procedimiento de Registro de Wallet
-
-Al abrir el [deep link] de registro, estos son los pasos que la wallet debe seguir para aplicar las medidas de seguridad y privacidad esperadas en este flujo, y para permitir que el usuario ingrese su información directamente con el SDP:
-
-1. 🚨 Confirma que el `domain` del deep link esté en la lista blanca (allowlist) de la wallet. Esto es crucial para autenticar desde una wallet confiable.🚨
-2. Obtén el archivo toml del SDP en `{domain}/.well-known/stellar.toml` y confirma que la variable `SIGNING_KEY` esté poblada.
-3. Verifica que la firma del enlace de registro haya sido realizada usando `SIGNING_KEY`, similar a la función `keypairPk.verify(...)` en el fragmento arriba, y que la firma sea válida con el contenido del enlace.
-4. Revisa el `asset` del enlace y confirma que el usuario receptor tenga una trustline para ese activo. Crea una si no existe.
-5. (Opcional) Usa el `name` del enlace para actualizar la interfaz de usuario de la wallet.
-6. Inicia el flujo de depósito [SEP-24] con ese activo usando el valor `TRANSFER_SERVER_SEP0024` del archivo toml del SDP.
-   - Esto incluye usar [SEP-10] para autenticar al usuario con el servidor SDP. Ten en cuenta que el SDP requiere que los campos `client_domain` y `home_domain` sean proporcionados en la solicitud `GET <WEB_AUTH_ENDPOINT>`, y deberían establecerse como sigue:
-     - `client_domain`: el dominio del servidor de wallet que expone el archivo `stellar.toml` del servidor de wallet.
-   - `home_domain`: el dominio del servidor SDP que estaba presente en el enlace de registro.
-   - `account`: la cuenta Stellar de la wallet del receptor.
-7. Lanza el flujo de depósito en un navegador _in-app_ dentro de tu aplicación móvil, siguiendo las instrucciones en la especificación [SEP-24].
-   - ATENCIÓN: la wallet no debe, bajo ninguna circunstancia, extraer o intentar extraer contenido del navegador _in-app_ para obtener información del receptor.
-   - NOTA: se recomienda altamente usar un navegador _in-app_ en lugar de un webview.
-8. 🎉 ¡Felicidades! El usuario receptor ahora puede completar los formularios en el navegador _in-app_ y registrarse para recibir su pago 🎉.
-
-Además, la wallet debería guardar el enlace y/o los atributos del enlace y asociarlos con el usuario receptor individual por estas razones:
-
-1. Así es como la wallet sabrá que el usuario está asociado con cierta organización o SDP.
-2. Guardar la información es útil para reportes y solución de problemas, especialmente si la wallet necesita justificar la fuente de fondos por regulaciones o propósitos fiscales.
-3. Si la organización pagadora quiere cubrir cualquier comisión de pago cobrada por la wallet o el offramp, la wallet necesitará saber qué usuarios y transacciones deben ser facturados upstream.
-
-### Enlaces diferidos (Deferred Deep Links)
-
-Es muy probable que el receptor no tenga la aplicación wallet necesaria instalada en su dispositivo. Por esta razón, las wallets deberían soportar el concepto de [deferred deep linking], que permite el siguiente flujo:
-
-1. La acción inicial del receptor al hacer clic en el deep link debería redirigirlo a la tienda de aplicaciones apropiada para descargar la aplicación wallet.
-2. Después de instalar y abrir la aplicación, el receptor debería ser redirigido al flujo típico de integración de wallet.
-3. Una vez que el usuario se haya integrado con éxito, la wallet debería usar la información incluida en el deep link para iniciar el [Procedimiento de Registro de Wallet](#wallet-registration-procedure).
-
-El deferred deep linking es una característica común soportada por numerosas soluciones móviles de deep linking; existen servicios de terceros que se pueden usar para implementar esta funcionalidad, como Singular, Branch, AppsFlyer, Adjust, entre otros. [Aquí](https://medium.com/bumble-tech/universal-links-for-android-and-ios-1ddb1e70cab0) hay una publicación de blog con más información sobre cómo implementar [deferred deep linking].
-
-El SDP soporta un formato básico de enlace, tal como `https://<host-con-ruta-opcional>`. Si el sistema de deep linking de tu wallet necesita una estructura más compleja, deberás gestionarlo con una aplicación web. Esta aplicación debería ser propiedad del proveedor de la wallet, y debería ser capaz de recibir el deep link, interpretarlo y dirigir al usuario a la ubicación correcta.
-
-[deferred deep linking]: https://en.wikipedia.org/wiki/Mobile_deep_linking#Deferred_deep_linking
-[deep link]: https://en.wikipedia.org/wiki/Mobile_deep_linking
-[deep linking]: https://en.wikipedia.org/wiki/Mobile_deep_linking
-[sep-10]: https://stellar.org/protocol/sep-10
-[sep-24]: https://stellar.org/protocol/sep-24
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
deleted file mode 100644
index 95a4de8e77..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/monitoring.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Monitorización
-description: Guía para usar la CLI de la Plataforma de Distribución Stellar
-keywords:
-  - SDP
-  - CLI
-sidebar_position: 70
----
-
-Esta guía explica cómo la Plataforma de Distribución Stellar (SDP) expone métricas en tiempo de ejecución y cómo conectar esas métricas con el conjunto Prometheus + Grafana.
-
-### Puntos finales de métricas
-
-Tanto el Dashboard API como el Servicio de Envío de Transacciones (TSS) exponen puntos finales `/metrics` compatibles con Prometheus. El servidor HTTP está definido en [serve_metrics.go](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/internal/serve/serve_metrics.go) y se controla a través de las siguientes variables de entorno:
-
-- `METRICS_PORT` – Puerto usado por el servidor de métricas del Dashboard API (por defecto [8002](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/docker-compose-sdp.yml)).
-- `METRICS_TYPE` – Backend de monitorización en uso (actualmente `PROMETHEUS`).
-- `TSS_METRICS_PORT` – Puerto usado por el servidor de métricas del TSS (por defecto [9002](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/docker-compose-tss.yml)).
-- `TSS_METRICS_TYPE` – Backend de monitorización para el TSS (por defecto `TSS_PROMETHEUS`).
-
-Cuando el servidor se inicia, monta la ruta `/metrics` y muestra contadores e histogramas específicos de solicitudes, base de datos y TSS que se alinean con los dashboards de Grafana provistos en [Grafana README](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/resources/grafana/README.md).
-
-### Conjunto local Prometheus y Grafana
-
-Proveemos un archivo Docker Compose que inicia Prometheus y Grafana preconfigurados para extraer las métricas de la SDP.
-
-1. Desde la [raíz del repositorio](https://github.com/stellar/stellar-disbursement-platform-backend/), ejecuta:
-
-```sh
-cd dev
-docker compose -p sdp-multi-tenant -f docker-compose-monitoring.yml up -d
-```
-
-Esto lanza Prometheus en el puerto `9090` y Grafana en el puerto `3002` por defecto según la [configuración de monitorización](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/docker-compose-monitoring.yml).
-
-2. El contenedor de Prometheus carga su configuración desde [config prometheus](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/prometheus/prometheus.yml), que apunta a `host.docker.internal:8002/metrics` por defecto. Ajusta la lista de `targets` si ejecutas la API en un host diferente o si quieres extraer las métricas del TSS (`host.docker.internal:9002`).
-3. Grafana usa la configuración de datasource en [datasource](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/grafana/datasource.yaml), que apunta a la instancia de Prometheus mencionada. Si tienes un despliegue de Prometheus existente, actualiza esta URL en consecuencia.
-
-Para desmontar el conjunto de monitorización, ejecuta:
-
-```sh
-cd dev
-docker compose -p sdp-multi-tenant -f docker-compose-monitoring.yml down
-```
-
-### Cargar el Dashboard de Grafana de SDP
-
-1. Navega a [http://localhost:3002](http://localhost:3002) e inicia sesión con las credenciales por defecto `admin` / `admin`. ![Inicio de sesión en Grafana](/assets/SDP/SDP42.png)
-
-2. Haz clic en el ícono `+` en la barra de navegación superior (junto al campo de búsqueda), elige `Importar dashboard` y pega el contenido de [Grafana Dashboard Json](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/resources/grafana/dashboard.json). ![Importar Dashboard](/assets/SDP/SDP43.png)
-
-3. Selecciona el datasource `prometheus` provisto por [datasource](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/grafana/datasource.yaml). ![Seleccionar datasource](/assets/SDP/SDP44.png)
-
-Este dashboard visualiza volumen/latencia de solicitudes HTTP, tiempos de consultas a base de datos y estadísticas de transacciones TSS, detalles descritos en [Grafana README.md](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/resources/grafana/README.md). Todos los paneles pueden filtrarse por método, ruta, tenant o instancia para distinguir tráfico entre múltiples despliegues.
-
-### Integración con instancias externas de Prometheus
-
-Si ya gestionas un clúster Prometheus, añade trabajos de scrap equivalentes a los que están en [config prometheus](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/dev/prometheus/prometheus.yml). Cada subsistema expone métricas en `http://<host>:<METRICS_PORT>/metrics` (Dashboard API) y `http://<host>:<TSS_METRICS_PORT>/metrics` (TSS). Los despliegues con [Helm](https://github.com/stellar/stellar-disbursement-platform-backend/blob/develop/helmchart/sdp/values.yaml) exponen las mismas configuraciones mediante `sdp.configMap.data.METRICS_*` y `tss.configMap.data.TSS_METRICS_*`. Una vez que los nuevos trabajos estén presentes, puedes importar el mismo JSON de dashboard en tu despliegue Grafana o adaptar las consultas PromQL a tu suite de observabilidad preferida.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/overview.mdx
deleted file mode 100644
index 82bb132b18..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/overview.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Descripción general
-sidebar_position: 5
-pagination_label: "Guía del administrador: descripción general"
----
-
-El proceso paso a paso completo del SDP generalmente se ve algo así después de que el SDP está implementado y los usuarios organizacionales han sido configurados:
-
-1. La organización financia la cuenta de distribución del SDP con un activo basado en Stellar (p. ej., USDC)
-2. Un administrador inicia sesión en el panel del SDP y carga un archivo CSV que contiene la información de pago para iniciar una nueva dispersión de fondos
-3. El SDP envía un mensaje de texto a cada beneficiario primerizo en el CSV invitándolos a descargar una aplicación de billetera compatible con Stellar
-4. Mientras tanto, el SDP comienza inmediatamente a realizar pagos a cada beneficiario que ya tiene una billetera registrada a su nombre
-5. Cada beneficiario primerizo hace clic en un enlace profundo para descargar la aplicación de billetera compatible con Stellar que la organización seleccionó para esta dispersión, descarga la aplicación y pasa por el proceso de registro en la billetera
-6. Una vez que el beneficiario se ha registrado y su cuenta Stellar ha sido creada, la billetera se autentica inmediatamente con el SDP usando los parámetros del enlace profundo y abre la vista web de registro del SDP para que el beneficiario complete la verificación
-7. El usuario confirma su identidad proporcionando un código OTP enviado a su número de teléfono y un dato adicional de verificación por razones de seguridad. El SDP admite tres tipos diferentes de información de verificación: fecha de nacimiento, PIN personal y DNI. Esta información es ingresada por el beneficiario en un flujo web y se envía directamente al SDP, lo que significa que la billetera no necesita procesar ni almacenar esta información.
-8. El SDP verifica la información del beneficiario. Si coincide con la información del CSV, el SDP realiza automáticamente el pago a la cuenta Stellar del beneficiario
-
-Representación gráfica del flujo de fondos:
-
-![Flow of Funds](/assets/SDP/SDP1.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/security.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/security.mdx
deleted file mode 100644
index b3eab8f91b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/security.mdx
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Seguridad
-sidebar_position: 60
----
-
-Este manual describe las medidas de seguridad implementadas en la Stellar Disbursement Platform (SDP) para proteger la integridad de la plataforma y sus usuarios. Al seguir estas directrices, puedes asegurarte de que tu uso de la SDP sea lo más seguro posible.
-
-La seguridad es un aspecto crítico de la SDP. Las medidas descritas en este documento están diseñadas para mitigar riesgos y mejorar la seguridad de la plataforma. Se recomienda encarecidamente a los usuarios seguir estas directrices para proteger sus cuentas y operaciones.
-
-### Implementación de reCAPTCHA
-
-Se ha integrado el reCAPTCHA de Google en la SDP para evitar ataques automatizados y asegurar que las interacciones sean realizadas por humanos y no por bots.
-
-El reCAPTCHA está habilitado por defecto y puede desactivarse configurando la variable de entorno `DISABLE_RECAPTCHA` a `true`.
-
-La configuración está disponible en dos niveles:
-
-1. **Predeterminado del entorno** – Configura `DISABLE_RECAPTCHA=true` para aplicar la configuración globalmente a todos los tenants.
-2. **Anulación por tenant** – Cada organización puede habilitar o deshabilitar reCAPTCHA a través de sus propias configuraciones (UI o API). Cuando existe, la elección a nivel de tenant anula el valor predeterminado del entorno.
-
-Usa las siguientes variables de entorno para controlar el comportamiento del reCAPTCHA:
-
-- `CAPTCHA_TYPE` – `GOOGLE_RECAPTCHA_V2` (predeterminado) o `GOOGLE_RECAPTCHA_V3`.
-- `RECAPTCHA_SITE_KEY` – Clave de sitio de Google emitida para el tipo de CAPTCHA elegido.
-- `RECAPTCHA_SITE_SECRET_KEY` – Clave secreta de Google asociada con la clave de sitio.
-- `RECAPTCHA_V3_MIN_SCORE` – Puntuación mínima permitida (0.0–1.0, por defecto 0.5) cuando `CAPTCHA_TYPE=GOOGLE_RECAPTCHA_V3`.
-
-**Nota:** Desactivar reCAPTCHA en los entornos de producción (pubnet) reduce sustancialmente la protección contra abusos automatizados. Esta configuración debe usarse solo cuando se aplican controles compensatorios equivalentes.
-
-### Aplicación de la Autenticación Multi-Factor
-
-La Autenticación Multi-Factor (MFA) proporciona una capa adicional de seguridad a las cuentas de usuario. Se aplica por defecto en la SDP y se basa en OTPs enviados al correo electrónico de la cuenta.
-
-La MFA está habilitada por defecto y puede desactivarse en el entorno de desarrollo configurando la variable de entorno `DISABLE_MFA` a `true`.
-
-**Nota:** La MFA no puede desactivarse en entornos de producción (pubnet) por riesgos de seguridad.
-
-### Limitación de Tasa de Solicitudes y Protecciones de Red
-
-La SDP aplica limitación de tasa en la capa HTTP para frenar abusos automatizados. Cada par único `<IP, endpoint>` está limitado a 40 solicitudes dentro de 20 segundos (ventana móvil). Las solicitudes que superen este umbral recibirán respuestas limitadas hasta que la ventana se reinicie.
-
-### Modelos de Autenticación y Autorización
-
-Todas las rutas API autenticadas requieren que los clientes presenten una clave API emitida por la SDP o un JWT derivado de los flujos SEP10/SEP24. Estos dos mecanismos funcionan en paralelo: los JWT son para usuarios interactivos, mientras que las claves API habilitan integraciones programáticas con su propio modelo de alcance.
-
-#### Roles JWT
-
-Los JWT representan usuarios humanos que inician sesión a través de la UI. Después de la autenticación, la plataforma los autoriza según los roles asignados a su cuenta de usuario. Los roles principales son:
-
-- **Owner** – Control total, incluyendo creación de usuarios, asignación de roles y edición de configuración de la organización. Owner es el único rol que puede otorgar o revocar acceso a otros.
-- **Financial Controller** – Puede realizar todas las tareas operativas (carteras, activos, desembolsos, estadísticas) excepto la gestión de usuarios. Este rol es ideal para el personal financiero que ejecuta pagos.
-- **Developer** – Administra configuración técnica como carteras, activos y claves API, y puede ver estadísticas; no puede modificar usuarios ni flujos financieros.
-- **Business** – Solo lectura sobre datos comerciales (desembolsos, receptores, estadísticas) pero no tiene acceso a detalles de gestión de usuarios.
-- **Initiator** – Crea y guarda desembolsos pero no puede enviarlos. Mutuamente exclusivo del rol Approver para garantizar la separación de funciones.
-- **Approver** – Revisa y envía desembolsos pero no puede crear nuevos; mutuamente exclusivo con Initiator.
-
-Cada endpoint API especifica qué roles JWT pueden acceder a él—por ejemplo, las rutas de gestión de claves API (`/api-keys`) requieren Owner o Developer, mientras que la creación de desembolsos requiere Initiator o Financial Controller y el envío requiere Approver o Financial Controller.
-
-#### Permisos de la clave API
-
-Las claves API omiten los roles JWT e incluyen sus propios ámbitos de permisos. Cuando una solicitud incluye una clave API, el middleware valida la clave, confirma que la dirección IP del llamante esté permitida (si está restringida), verifica la expiración y finalmente asegura que la clave contenga los ámbitos requeridos por el endpoint. Las claves API se usan típicamente para automatización e integraciones entre servicios donde se necesita acceso preciso de lectura/escritura; crearlas o rotarlas sigue requiriendo un usuario con el rol JWT apropiado (Owner o Developer) para acceder a los endpoints `/api-keys`.
-
-Los ámbitos disponibles mapean directamente a los principales recursos de la SDP:
-
-- `read:all`, `write:all`
-- `read:disbursements`, `write:disbursements`
-- `read:receivers`, `write:receivers`
-- `read:payments`, `write:payments`
-- `read:organization`, `write:organization`
-- `read:users`, `write:users`
-- `read:wallets`, `write:wallets`
-- `read:statistics`
-- `read:exports`
-
-#### Configuración recomendada
-
-Para mejorar la seguridad, las responsabilidades de desembolso deberían distribuirse entre varios usuarios con el rol Financial Controller.
-
-1. **Flujo de aprobación**: Activa el flujo de aprobación en la página de la organización para requerir dos usuarios en el proceso de desembolso. El propietario puede hacerlo en _Perfil > Organización > ... > Editar detalles > Flujo de aprobación > Confirmar_.
-2. **Rol Financial Controller**: Crea dos usuarios con el rol _Financial Controller_ en la página de la organización para aplicar la separación de funciones. El propietario puede hacerlo en _Configuración > Miembros del equipo_.
-3. **Gestión de la cuenta Owner**: Utiliza la cuenta Owner únicamente para la gestión de usuarios y la configuración de la organización. Evita usar la cuenta Owner para tareas de financial controller para minimizar la exposición de esa cuenta.
-
-### Buenas prácticas para la gestión de carteras
-
-La cartera de SDP debería usarse principalmente como una hot wallet con una cantidad limitada de fondos para minimizar posibles pérdidas.
-
-#### Hot y Cold Wallets
-
-- Una hot wallet está conectada a internet y permite transacciones rápidas.
-- Una cold wallet está desconectada y se usa para almacenar fondos de manera segura.
-- Aprende más sobre estos conceptos en [Investopedia](https://www.investopedia.com/hot-wallet-vs-cold-wallet-7098461).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/README.mdx
deleted file mode 100644
index d79d223827..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Interfaz de usuario
-sidebar_position: 100
----
-
-import DocCardList from "@theme/DocCardList";
-
-Una descripción y recorrido por las distintas partes de la interfaz de usuario de SDP.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.mdx
deleted file mode 100644
index 6a6579457f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/analytics.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Analítica
-sidebar_position: 60
----
-
-La página de Analítica proporciona información completa sobre varios aspectos de las transacciones financieras, permitiéndote rastrear y comprender métricas clave relacionadas con los pagos. A medida que estén disponibles más métricas y estadísticas, se añadirán fichas adicionales a esta pantalla. La página muestra información como la tasa de pagos exitosos, el número total de pagos exitosos, el número de pagos fallidos y el número de pagos pendientes. Además, muestra el monto total desembolsado, el monto promedio por transacción, el monto total en USDC y la cantidad de personas y billeteras involucradas en las transacciones.
-
-Con más detalle:
-
-- La "tasa de pagos exitosos" indica el porcentaje de pagos procesados exitosamente sobre el total de pagos intentados.
-- "Pagos exitosos" muestra la cantidad de todas las transacciones que se han completado con éxito.
-- "Pagos fallidos" revela el número de transacciones que no se realizaron correctamente, lo que ayuda a identificar problemas en el proceso de pago.
-- "Pagos pendientes" proporciona el número de transacciones que aún están por procesarse.
-- "Total desembolsado" ofrece información sobre el monto total de fondos que se han enviado.
-- El "monto promedio" ofrece un valor promedio de todas las transacciones que han ocurrido en USDC.
-- "USDC" revela el monto total de fondos en el sistema, denominado en USDC.
-- "Individuos" representa la cantidad de personas involucradas en estas transacciones.
-- "Billeteras" indica la cantidad de billeteras digitales únicas involucradas en las transacciones.
-
-![Analítica](/assets/SDP/SDP24.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.mdx
deleted file mode 100644
index cb85f2c3ea..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/circle-configuration.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Configuración de Circle
-sidebar_position: 70
----
-
-Si el tenant fue creado con una cuenta de distribución [Circle], entonces el propietario del tenant deberá configurar manualmente esa cuenta desde el panel de SDP.
-
-Una vez que un usuario con privilegios de propietario inicie sesión, verá un banner en la parte superior de la página indicando que la cuenta de Circle está pendiente de configuración:
-
-![Circle Configuration Banner](/assets/SDP/SDP30.png)
-
-Al hacer clic en el banner, el usuario será llevado a la sección Cuenta de Distribución, donde podrá ingresar la clave API de Circle y el ID de la billetera de Circle.
-
-![Circle Configuration](/assets/SDP/SDP31.png)
-
-:::info
-
-La clave API se almacenará en la base de datos cifrada mediante la clave «DISTRIBUTION_ACCOUNT_ENCRYPTION_PASSPHRASE», mientras que el ID de la billetera se almacena en texto plano.
-
-El ID de la billetera se usa para identificar la cuenta (interna) de Circle al realizar desembolsos. Es útil porque una cuenta de Circle puede tener varias billeteras, cada una con diferentes monedas y saldos.
-
-:::
-
-[Circle]: https://www.circle.com
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.mdx
deleted file mode 100644
index ba6c588ee0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/dashboard-home.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Inicio del Panel de Control
-sidebar_position: 10
----
-
-La página principal del panel de control contiene un resumen de la actividad reciente de desembolsos y métricas clave de rendimiento.
-
-Esto incluye:
-
-- Tasa de pagos exitosos: El porcentaje de pagos completados con éxito (los pagos pendientes no se cuentan como exitosos).
-- Pagos exitosos: El número total de pagos que se han realizado con éxito.
-- Pagos fallidos: El número total de pagos que no pudieron procesarse.
-- Pagos restantes: El número total de pagos programados que aún no se han procesado.
-- Total desembolsado: La cantidad total de fondos enviados con éxito a los beneficiarios por una organización a lo largo del tiempo.
-- Individuos: El número total de personas que están fijadas para recibir desembolsos.
-- Carteras: El número total de carteras utilizadas dentro del SDP. Esto usualmente equivale al número de individuos, pero es posible que cada persona tenga más de una cartera.
-
-![Dashboard Home](/assets/SDP/SDP19.png)
-
-En el lado izquierdo del panel de Stellar Disbursement Platform está el logo de la organización y pestañas que te ayudan a navegar por la plataforma.
-
-Incluyen:
-
-- Inicio: Este es el panel principal que ofrece una visión general de las actividades de tu organización.
-- Desembolsos: Esta sección muestra el historial y los detalles de todos los desembolsos.
-- Receptores: Listas de personas que están fijadas para recibir desembolsos.
-- Pagos: Aquí puedes encontrar el historial y detalles granulares de todos los pagos.
-- Carteras: Información relacionada con la cartera de tu organización, la fuente de fondos para tus desembolsos.
-- Analíticas: Herramientas de visualización de datos para ayudarte a analizar tus desembolsos y pagos.
-- Perfil: Gestiona tu información personal y de la organización.
-- Configuración: Ajusta las configuraciones del SDP según tu preferencia.
-
-El panel también muestra una lista de Desembolsos Recientes, proporcionando una vista rápida de tus desembolsos más recientes.
-
-Cada entrada muestra:
-
-- Nombre del Desembolso: El nombre único que tu organización asigna a la operación de desembolso.
-- Total de pagos: Número total de pagos dentro del desembolso específico.
-- Exitosos: Número de pagos que han sido enviados con éxito desde la cartera de distribución del SDP a las carteras de los receptores hasta ahora.
-- Fallidos: Número de pagos que fallaron durante el proceso.
-- Restantes: Número de pagos que están programados pero aún no se han procesado, usualmente porque el receptor no ha configurado una cartera.
-- Creado el: La fecha y hora en que se creó el desembolso, mostrada en tu zona horaria local.
-- Cantidad total: El valor total del desembolso en el activo correspondiente.
-- Cantidad desembolsada: La cantidad del desembolso que se ha pagado con éxito hasta ahora.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.mdx
deleted file mode 100644
index 2dbd7aad3a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/disbursements.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Desembolsos
-sidebar_position: 20
----
-
-La página de Desembolsos proporciona una lista paginada de todos los desembolsos, detallando el estado de cada uno y la información de pago relacionada.
-
-![Desembolsos](/assets/SDP/SDP20.png)
-
-La página contiene lo siguiente:
-
-- Borradores: Haz clic en el botón Borradores en la parte superior derecha para acceder a una lista de desembolsos que han sido creados pero aún no enviados.
-- Nuevo desembolso: Haz clic en el botón Nuevo Desembolso para iniciar el proceso de crear un nuevo desembolso.
-- Buscar por nombre del desembolso: Introduce el nombre de un desembolso para encontrar rápidamente detalles específicos.
-- Filtrar: Te permite reducir la lista de desembolsos basándote en criterios específicos como estado o fecha de creación.
-- Exportar: Usa esta opción para descargar los datos del desembolso en formato CSV.
-- Detalle del desembolso: Cada desembolso se muestra con los siguientes detalles:
-  - Nombre del desembolso: El nombre único asignado al desembolso por tu organización.
-  - Pagos totales: El número total de pagos dentro del desembolso.
-  - Exitosos: La cantidad de pagos dentro del desembolso que se han procesado exitosamente desde la cuenta de distribución hacia las carteras registradas.
-  - Fallidos: La cantidad de pagos que fallaron durante el procesamiento.
-  - Restantes: La cantidad de pagos que aún están por procesar.
-  - Creado el: La fecha y hora en la que se creó el desembolso.
-  - Monto total: El valor total del desembolso en el activo correspondiente.
-  - Monto desembolsado: La cantidad del desembolso que ya ha sido pagada.
-- Puedes hacer clic en un desembolso individual para ver sus detalles, incluyendo una lista completa de receptores y pagos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.mdx
deleted file mode 100644
index 22c783bbf6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/payments.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Pagos
-sidebar_position: 40
----
-
-La página de Pagos proporciona una lista de todos los pagos, detallando el estado de cada uno y la información relacionada.
-
-![Payments](/assets/SDP/SDP22.png)
-
-La página de Pagos incluye:
-
-- Buscar por ID de pago: Introduce un ID de pago para encontrar rápidamente detalles específicos del pago.
-- Filtro: Esta herramienta te permite reducir la lista de pagos según criterios específicos.
-- Exportar: Esta opción te permite descargar los datos de pagos en formato CSV.
-- Detalles del pago: Cada pago se lista con los siguientes detalles:
-  - ID de pago: Un identificador único asignado a cada pago.
-  - Dirección de la wallet: La dirección de la wallet digital a la que se envía el pago. Un guion ("-") indica que la dirección de la wallet aún no está configurada. El pago no puede realizarse hasta que la wallet del receptor sea creada y vinculada en el Stellar Disbursement Platform.
-  - Nombre de la distribución: El nombre de la distribución asociada con el pago.
-  - Completado en: La fecha y hora en que se completó el pago. Un guion ("-") indica que el pago aún no ha sido completado.
-  - Monto: El valor del pago en el activo correspondiente.
-  - Estado: El estado actual del pago. Las opciones son:
-    - `DRAFT`: Estado no terminal para pagos que fueron registrados en la base de datos pero cuya distribución aún no ha comenzado. Los pagos en este estado pueden ser eliminados o pasar a `READY`.
-    - `READY`: Estado no terminal para pagos que están esperando que el receptor se registre. Tan pronto como el receptor se registre, el estado cambia a `PENDING`.
-    - `PENDING`: Estado no terminal para pagos que fueron marcados por la plataforma correspondiente de la cuenta de distribución (actualmente TSS o Circle) para su envío a la red Stellar. Pueden o no haber sido enviados a la red aún.
-    - `PAUSED`: Estado no terminal para pagos que fueron pausados manualmente. Los pagos en este estado pueden reanudarse.
-    - `SUCCESS`: Estado terminal para pagos que fueron enviados exitosamente a la red Stellar.
-    - `FAILED`: Estado terminal para pagos que fallaron al enviarse a la red Stellar. Los pagos en este estado pueden intentarse nuevamente.
-    - `CANCELED`: Estado terminal para pagos que fueron cancelados manual o automáticamente.
-- Puedes hacer clic en un pago individual para ver sus detalles, incluyendo un historial detallado del estado y detalles del blockchain de Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.mdx
deleted file mode 100644
index 5881bd5209..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/receivers.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Receptores
-sidebar_position: 30
----
-
-La página de Receptores muestra una lista de personas configuradas para recibir pagos, con información sobre sus billeteras e historial de pagos. Esta información te permite rastrear y administrar los pagos realizados a cada receptor, y proporciona una visión rápida de la interacción de cada receptor con una distribución de fondos.
-
-![Receivers](/assets/SDP/SDP20x.png)
-
-La página de Receptores incluye lo siguiente:
-
-- Buscar y Filtrar: En la parte superior de la página de Receptores, hay varias herramientas disponibles para ayudarte a encontrar información específica:
-  - Buscar por número de teléfono: Ingresa el número de teléfono de un receptor para encontrar su información rápidamente.
-  - Filtrar: Usa esta herramienta para reducir la lista de receptores según criterios específicos.
-  - Exportar: Esto te permite descargar los datos de los receptores en formato CSV.
-- Detalles del receptor: Cada receptor está listado con los siguientes detalles:
-  - Número de teléfono: El número de teléfono del receptor, que sirve como identificador único dentro del SDP.
-  - Proveedor(es) de billetera: El proveedor de la billetera digital del receptor (normalmente una aplicación no custodial en el teléfono de la persona).
-  - Billeteras registradas: El número de billeteras registradas y vinculadas exitosamente al SDP por receptor. Un guion ("-") indica que no se ha registrado ninguna billetera.
-  - Pagos totales: El número total de pagos destinados al receptor.
-  - Exitosos: El número de pagos que se han enviado con éxito a la billetera del receptor.
-  - Creado en: La fecha y hora en que se creó el receptor en el sistema, mostrada en tu zona horaria local.
-  - Monto(s) recibido(s): El monto total que el receptor ha recibido con éxito en el/los activo(s) correspondiente(s).
-- Puedes hacer clic en un receptor individual para ver sus detalles, incluyendo sus billeteras vinculadas y el historial completo de pagos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/wallets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/wallets.mdx
deleted file mode 100644
index 1e2bd05b6a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/admin-guide/user-interface/wallets.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Carteras De Dinero Digital
-sidebar_position: 50
----
-
-La página de Carteras proporciona información detallada sobre tu cuenta de distribución, que es la cuenta principal de Stellar desde la que se realizan tus desembolsos.
-
-![Wallets](/assets/SDP/SDP23.png)
-
-La página de Carteras incluye lo siguiente:
-
-- Clave pública de la cuenta de distribución: Este es tu identificador único para tu cuenta de distribución en la red Stellar. Usas esta clave pública para recibir fondos en tu cuenta de distribución.
-- Saldo: Esta sección muestra el saldo actual de diferentes activos digitales en tu cuenta de distribución:
-  - USDC, EUROC, etc.: Este es el saldo actual disponible para realizar pagos dentro de un desembolso.
-  - XLM: Este es el saldo de Stellar Lumens. Esto se usa para financiar la cuenta de distribución (reserva base) y las tarifas de transacción asociadas con la realización de pagos. Esto es solo con fines informativos y no es la fuente de fondos para los desembolsos. En general, no necesitas preocuparte por mantener esto, ya que las tarifas de la red Stellar son muy bajas.
-
-### Agregar fondos
-
-Agrega fondos a tu cuenta de distribución: Puedes depositar activos digitales basados en Stellar en tu cuenta de distribución enviándolos a la clave pública proporcionada. Asegúrate de que tu cuenta tenga una trustline al activo antes de enviar fondos. Como principio general, no uses tu cuenta de distribución como un lugar de almacenamiento a largo plazo para dinero. Está destinada a ser una cartera de paso para financiar desembolsos.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/admin.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/admin.tag.mdx
deleted file mode 100644
index ac04e35d21..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/admin.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: admin
-title: "Admin (Tenant Management)"
-description: "Admin (Tenant Management)"
-custom_edit_url: null
----
-
-
-
-The Admin API oversees the management of tenants within the system, facilitating tasks such as provisioning new tenants, updating their information, and retrieving tenant data.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/api-keys.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/api-keys.tag.mdx
deleted file mode 100644
index 71bb54e4f4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/api-keys.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: api-keys
-title: "API Keys"
-description: "API Keys"
-custom_edit_url: null
----
-
-
-
-API Keys functionality allows to create access key with granular permissions and resource management.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.api.mdx
deleted file mode 100644
index 986110bbdd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/authenticate-mfa.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: authenticate-mfa
-title: "Provide Multi-Factor Authentication"
-description: "Governs the multi-factor authentication process for SDP user login, including the ability to remember the device so MFA is not always required."
-sidebar_label: "Provide Multi-Factor Authentication"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV01z2zYQ/SsYnJIMKTqetAfe5I80bpPUEznTg+NxluRSRAQCDLC0rHr03zsLkhZlJXLSNjPRRRKweHj7sNhd3EmCuZfppZy2VKEhlQMpa+RVJAv0uVNN+JvK3+wNOuMFVSjqVpOKS8jJOgFbC0XjbI7ei9I6MTs5F61HJ7SdKxMJZXLdFsrMAwpkSitaCbLCYY11hi6MF3ijchTeijcvp0J5YSwJ0EtYeeHwc6scFhMZSdugC3ueFTKVIxr45uVURrIBBzUSOvbvThqoUabyJKDHZycykoodqxAKdPKhv2cFo5UKnbDliJeM5EBCpiVoj5H0tNKM7VXdaLbA20bbAjcGeYU1yPRO0qoJluSUmcv1+qqDQ09HtlixxTYNlqA3EAUQyEjm1hAaYttnyTP+2sBvqF3KuoTrnFlcRcO2NvuEObE2jtUjhZ5X3VvuEHyoyps9Jx8Q1uxPd5jX9Rgws1YjmB3Eo25clBrmO6HAwdNB5tBQXsE12QWax3lesFmIQYfH0/OL41dTcQNaFYHqRLy7Hw2AHGWDdKI1mgOY9/94cjabHr0+vX532tt/FLk1pZq3XejxQo/ExMm1OJFr/oxDhIfDgG+s8Z3ehwcHuyc9a3O+OGWrHwi7feTQNLqfSD55a7bPf/85f6N426mgU6hzbB3JF1/ifgSFeNdF6f/HFp2z7nG2J0igtBeQ2ZbCqXUL13wNyYF/dKfgF95CuLybjeWZCSEjlGlakmO4UqEurktrZbr5PQ4iGfXjGbh7mwycMIiF53DJUIARyhDOOcbv1X2+q+57wwFhnfo7AP9Yeb9dNukJqB3bmZZvLkPU6D3Mv5BQ1l8T+y0n+bGbGxbDPi8Ono+QH674kcAB+zbmDDdHE/cJOc5ssYr7usK/O3A0XlnTFZ0FrmS6d2Ukb0C39whcEGqkynJNa2y4Tw1QJVOZ1CWnf4/uZqhprdMylWGRx7x1ilYzPv7ufI4QHDq+zaNzgEb9gaudW/T7XxecbYuQM7fzTyS8mhssxFJRxUF7Ojv85VfROHUDhGKBK67GvQzTXrchc41LLIuoTGkDG0WhZM4ItQYnTpTPWuexRkPiXAOV1tVien7GAqHzHcvDyfPJAWvQ1jU4lvaiQrEf48ns5Pwp300QZK0WWas0BTetm4PpqYY7WcMCRdbqhWhgxShhFMTc2bbhNsBhrhoVJrgdCtlm2N0gLa1bTHZr0U9H8YP5YC4q5cOWRtgGText63Lk9o3vuqAKiKc7KqEKNEMj9AAuEmCKMMFRLnIwnNxK25oiLKz4j9Z2yY2fw8Z6RdYp9CnziMWl7/CS/jsuRiLFTS9SnEG+QFNcPamIGp8myVxR1WaT3NbJdyE8TUVw/p7Kims6geq7294seKVM6cCTa3NqXe8gnws9dqaT7/CsdCGj/xfXBojHfFtiJgbbf+1NhbqO8woc+b2UR3YJOcSkBmWSfmCvP4+58Qp1LQJQ4F9go+1qeFfsv2utZ7tFm6EzSOgnHzhNEbra/1nO0IUeP5WDWz3NiXXzJBjFtox9bxZJrXI0PtSbIQE2kFcoDkOe6vIzY6VJslwuJxBmA1q/1Cevz45P385O48PJwaSiWoc8yam/BjMCPnf2RhUouhb8ZdeCTx92ilup527TK/yE77e+IBHeUtJoUIYbh6DYXV/ywhuGny8VF8L0Ut7dZeDxvdPrNQ9/bpGLwOUVF1GnIOOScnm1joaKwzWyUJ4nNq+1r0q058n3Ra5dcR8/KIdSLtfRUPuPO/j4ghE2Fvxy2xhN8xwbGk3vNHZbfcH5n7MLGXUNAz/fwtNNOljy4xSWgcB6/Q9FjJ0S
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Provide Multi-Factor Authentication"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/mfa"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Governs the multi-factor authentication process for SDP user login, including the ability to remember the device so MFA is not always required.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"Device-ID","in":"header","description":"Identifier of the device","required":false,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"MFA request data","content":{"*/*":{"schema":{"required":["mfa_code"],"type":"object","properties":{"mfa_code":{"type":"string","description":"Multi-factor authentication code"},"remember_me":{"type":"boolean","description":"Boolean flag to remember the user"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation. ReCAPTCHA token is required unless the `DISABLE_RECAPTCHA` configuration is set to true."}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Successful authentication","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string","description":"Authentication token"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/authentication.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/authentication.tag.mdx
deleted file mode 100644
index a7c1b1271d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/authentication.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: authentication
-title: "Authentication"
-description: "Authentication"
-custom_edit_url: null
----
-
-
-
-Authentication controls the log in/log out process for all SDP users, as well as the token refresh process. Authentication uses a JWT approach signed with an ES256 private key.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/balances.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/balances.tag.mdx
deleted file mode 100644
index 77993d11d2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/balances.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: balances
-title: "Balances"
-description: "Balances"
-custom_edit_url: null
----
-
-
-
-Endpoints related to balances. A balance is an amount of a particular asset held by an organization, tenant, or account.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/bridge-integration.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/bridge-integration.tag.mdx
deleted file mode 100644
index 458e0ab900..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/bridge-integration.tag.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-id: bridge-integration
-title: "Bridge Integration"
-description: "Bridge Integration"
-custom_edit_url: null
----
-
-
-
-Bridge integration endpoints for connecting organizations with Bridge services.
-
-**Integration Flow:**
-1. Organization opts into Bridge (OPTED_IN status)
-2. Complete KYC verification process via Bridge
-3. Create virtual account for USD deposits (READY_FOR_DEPOSIT status)
-4. Receive USD deposits that are automatically converted to USDC on Stellar
-
-**Status Description:**
-- NOT_ENABLED → Bridge service not configured
-- NOT_OPTED_IN → Organization hasn't opted in
-- OPTED_IN → Organization opted in, KYC link created
-- READY_FOR_DEPOSIT → Virtual account created, ready for deposits
-- ERROR → Integration error occurred
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-api-key.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-api-key.api.mdx
deleted file mode 100644
index 44dc4afd0e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-api-key.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-api-key
-title: "Create API Key"
-description: "Creates a new API Key to access SDP endpoints. API Key can be configured to have a granular read/write access, also API key can be restricted to the specific IP or range of the IPs."
-sidebar_label: "Create API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWG1v2zYQ/isEP7WD/BKv3Yu+pU2GeRtWo04xYGkQnKSTxYUiVb7E9Qz99+EoyZaVFzddC2yfLJPHh3fH43N33HIHK8vjS366mLNfcWP5VcQztKkRlRNa8Zi/NggOLQOmcM1aOeY0gzRFa9nybMFQZZUWytnxTiAFxRJkqVa5WHmDGS0p4BYZsJUB5SUYZhCyydoIhy1axEBaHUBu9iAGrTMidQ2IK5DZClORi5TNF0wbZkCtkOk8zM0Xdswjris0QDbMs50Vp4v5r7jhETf4waN1r3S24fGWp1o5VI4+oaqkSMPCyV+WPLDlNi2wBPpymwp5zHXyF6auxREGM3KhghJ5xCs0pbBWaBWcWRlSxAm0tD7I7HHILLXiQ5f/7EtQI3IOJBIZLWK5NsG61jW8PtxpjwnGwOYO5G/COnJQb004hp1Phd1BR1w4LO19eqLyJdlKusUgJY94OL72OwxnwibeWCxRObsTGI4GUYMpils0e7H+SBCpYHMI1BsIAtqsQIm/w4nthAaDQdDb/kbdvzC1Bimxt8f+f5i2DpywTqS7EfxYaeMsv6ojXgo1b/x1UkccP1bCbK4zcPcedK5NCY7HnARGToSQOTyqN+EDJAtQwQRG0sMQYM9Kbx3dD6HCeO6dN/icQgOk1GvMrkUVjlErfJPz+PJY4C2FWkm6QQyyzNDt1oa9np+9bW4Yr6M7YfZAqNRD6FOSpwjcg+MA3vL6DvvMF7vbH2J24IMxm+dMaccqo29FhlkUZnvc4S1mLDe6ZKA2bL7gdR1xJ5zEASu8bSiB1ySwv9fOeAwDttLKNrd4Nj2hn4GBHWcFzIxZHxgt91KSnz6bYg4JRGTH6eOdEh88MpGhciIXaO4jjy/KRPRzFOuiIJZ3HuQ+grWSG2bQeaMwY1qlyMA1LhRaPT/Ocp8afk/hv7v3519u2qI9HvpfgjrOB4zRZsSeYW10XoP7zC3+KFAdsNAabBfz/Q2ST4iIdxYNWxd6d2cGyvoq+wrKSrCOtdD9XZ6kcR9kqDbNXRPvfBXFLWn9IIc1LEUkVkf8xXR6l6deQcba8oeN2C1IkTURg8bokBJ7VPXN5JunsFOAOO7FM3QgpGWQaO+Cmc3CcAecAXt0p2AefoSyktjbmM9VMIgJVXlatIfLBcrsOteax/tvJizbUX3UjidgdjIJGKYQM0skkSADxYRyuEITXNw4+Z5k8E6Bd4U24u8A/MU9+ume4lS8+L6c8mWCwdklWgure8imfsi/v2vHDizba9Ht82J60kMermiQ78uAX2u3cETf3j2in7RJRJah+irnc7/79ns+xQ0Hq2idxdQb4TahonuFYNCcelfw+PKKKqgSXaGp6am0DRoDzfEJVGJ0Qz0eIZhQZBOAN5LHPNReHfCSrG8M7MPvE2Elmj7q0KW//HHR1lvahGOgAqSxL2JWrCjHr4Ur6BqdL2cvv2OVEbeUqKiU411Rwk/bE+zKd0HgBUIWrl3EyVdv9x3c+d5lLcCOdw6Kh17bcjXItnw2nb0YTb8fzX68OHkZvzyJZz+Mp9+f/MkHtUDvAgqV6+CTloiXDiU1tWe9ToctJDjieyJyHnFyeuOr2fhkPKWT8GUJZtPWR49jPFueLZ4TZwFzWkuWeCFdcHa/3wlcVcINssTLG9b1S6FlZyujfUV1gcFUVCJM6FtsKrpud4Vurc3N+N4S7r+l4nv1Xl1Q8UZbKqYrVCOrvUmRWgK6sswV4Gi6UUUr5nTVVUYDuIiBatJ5qjPsWohce5WFhdRkaQoHoVbMYKWtcNoItDHpMWKXtsGbtL+jftc7qlonjRJIb1BlV88K5yobTyYr4QqfjFNdTp6E8DxmwfidKht6cHEgyMMFslYsWCVUbsA641PqEhsDu1L+0TMdP8Gy3AQm/TemdRDHbFtjwjrZz7amQFmO0gKMs4+q3JObOIM4KUGoSTvwqD3HzPgZZckCUNA/w0rqDYXXUUuYtyR34xM0Ch3a8XsiS4emtG/yJZpbkRIvdWa1ao61WU2C0EjnI9uKRVyKFKl03LPoaQVpgWwWeKrJEoQVTybr9XoMYTagtUvt5Lf56/Pfl+ej2Xg6LlwpA1tTFipB9YCbkrV7KhyyTO857n/7+NjmSYcf3aSSIFRoNMiF2zYdX/JdOr6KeEGZOr7k220CFt8ZWdc0/MEjpYbLq4jfghHUg4ckH3XZkPJ3aL7568ZnowvamcSlbzL1oMSgJ5xmxWmaYuUele0XE4s3ywse8aR9Mi11RmsMrOlNDNZUQtCjq+sa9TC25RLUyjfFWYMZCp875UTz7th+9B6qQG16Gg4Lg8aQpu16YMl22xQrdb2Tb6YeXNG6tpOms7uq6/ofTv4Wzg==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/api-keys"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new API Key to access SDP endpoints. API Key can be configured to have a granular read/write access, also API key can be restricted to the specific IP or range of the IPs.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","required":["name","permissions"],"properties":{"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","description":"List of permissions granted to this API key","items":{"type":"string","enum":["read:all","write:all","read:disbursements","write:disbursements","read:receivers","write:receivers","read:payments","write:payments","read:organization","write:organization","read:users","write:users","read:wallets","write:wallets","read:statistics","read:exports"]},"minItems":1},"expiry_date":{"type":"string","format":"date-time","description":"Optional expiration date for the API key (must be in the future)"},"allowed_ips":{"oneOf":[{"type":"string","description":"Single IP address or CIDR range"},{"type":"array","items":{"type":"string"},"description":"Array of IP addresses or CIDR ranges"}],"description":"IP restrictions for the API key. If not provided, the key can be used from any IP"}},"title":"CreateAPIKeyRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"API key created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"key":{"type":"string","description":"The actual API key (only returned once at creation)"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"CreateAPIKeyResponse"}}}},"400":{"description":"Bad request - validation errors","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-asset.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-asset.api.mdx
deleted file mode 100644
index 26489ab0d0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-asset.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-asset
-title: "Create Asset"
-description: "This endpoint is used to create a new asset that can be used in a Disbursement. Note: the organization must hold a balance in a particular asset to use it in a disbursement."
-sidebar_label: "Create Asset"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVVk1T20gQ/Stdc0qqJIsQEqp0Mxg2bFggMQm1a3wYSW1rYmlGmQ8bRaX/vtUjCcxHyGZz2eVg7Jnu191vevpNwyxfGhbP2Llecim+cSuUZPOAZWhSLSr/M2aXuTCAMquUkBaEAWcwA6sg1cgtAgeJG+DGoAWbcwspl5BgZyYkcJgIkzhtsERpR3CmLMZgcwS1FRdKZyzkqsiAQ8ILLlPsvCuurUhdwfUQRBE2CNvtZ9voLGCqQu0hTzIWs0Of5JgcWcA0fnVo7IHKahY3DwodD+gJ9rVlLGCpkhalJXNeVYVIPXb0xZBPw0yaY8npG2ELjRkxmqoMWcCEMQ41UWrrClnMVPIFU0qk0pSmFWjI1ZvHzWBlrBZyyR4fBPYM9PB4w8uqII9P08kha28D/iOo3nYb5reDg8ne/snx29Or9/sX+39Mjj5PD68+7k8uPl19fn325+vJ5Yejz8ene2fjy73xh3ev/zo9PT4dv2Et/QVbFFjt0C+YSknTVbm78+p7pPd0g3FpisYsXFHU97gn9L2dncf+BzyD/lQDEHLNC3G7AInKalDaN1ul1VpkmHnyoq546ubeZ/QgXBswg6nTwtYsnjXsALlGPXY2Z/Fs3s4DdhMS0hJl2IcLKVwoeUlU0nfPrUVphJLGo6ywZvGzngFb88LdIlCgEm2uqJcrZXzvcEqCRb4XDKNE9Rp1F8HpgsXM+w35T6lFuyPYruK2R3gl3mP9qEd+v7rs7vBCaeDO5iht3/0BGLGUmMFG2By4hKPp7pu3UGmxpomwwpro7JmgaEoP4yVggsBz5BlqRjTTTfp4dy+Phm4crkXX3He9/QtdSsEXypcurO/4qcWCJsv2iIKLgtuF0iWML07oQFCbjpLd0avRDhHuypLrur9Iz2O8mE4uXlKjcbBKFZA4UVjP6fb4MzR3Sr5CSFyxgorXhOJXOSy1chWoBWhMRSX8hlpj19dDdIl2o/Rq9ORd/2+leC2vpVcVCilBVShDo5xO/S2lCdkJiTB9KkqCVR7+CbgAuMz8BvXLoD4L5WTmHXP6URRqI+QSNFbKCKu0QBNTHiHMTIcX9f/DbUEJq56kMOHpCmU2f5FbW5k4ipbC5i4ZpaqMfgrhZQy++NtUaqDBwwUxnCP0Zr4qIReaG6tdap3uC1yo+6w+eaajn6hsof3c+5XSBogf1bbBBAbbf11NjkUZpjnX1jyb8pZdZDViVHIho37h2Xp+VMY7LErwQD7/DKtC1dReP6wEnCG7lUtQS7RoRtc0Ey3q0pwvpqjXIqW5NJTVpzlSehl5o1AtQtObBawQKUrjh+UwbSue5gi7fk51YkBYcRRtNpsR97serXc10enJ4dHZ9CjcHe2MclsWfiiT1JRcbgF3DykYXlL3ZkxzJ53/u+diL4IWb2xUFVxIkglPXNMr7Yz1SjsPWE4SHM9Y0yTc4CddtC0tf3VIcjCbk3xrwRMSl9m8DQahuxP/w46p8JLi3qn9o7flPeW/OJ9esqB7EsQNKzth1HxDb1q+IcWnh6/tHhpNt9awgsul40uy7TDpaPkj9V959e+/UKbDlqy3Mnyo41059NkG33Fpmu5t0ba39t3Wdz16ugZrOo1527Z/AxqDc2E=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Asset"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/assets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to create a new asset that can be used in a Disbursement. Note: the organization must hold a balance in a particular asset to use it in a disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Asset to be created","content":{"application/json":{"schema":{"required":["code","issuer"],"type":"object","properties":{"code":{"type":"string","description":"The asset code","example":"USDC"},"issuer":{"type":"string","description":"The issuer","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Asset created successfully","content":{}},"400":{"description":"Bad request, invalid request body or the provided code/issuer is invalid.","content":{}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx
deleted file mode 100644
index 226a191ae9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-direct-payment.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-direct-payment
-title: "Create Direct Payment"
-description: "Creates a new direct payment that is immediately sent to the specified receiver if they have a valid registered wallet. Direct payments bypass the disbursement workflow and are processed instantly."
-sidebar_label: "Create Direct Payment"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWW1z4jgS/isqfZrZw2DAvAyfjglkN7e5TDYkk9rNpFKy3WBtbMkjyWG4FP/9qmUbm8DmbbJVN/clMVb306/ubkn31LCFpqMrespWCQij6XWDhqADxVPDpaAjeqCAGdCEEQFLEnIFgSFpTk5MxAzhmvAkgZAzA/GKaLsgiYmA6BQCPucQEgUB8DtQhM9xZUUidgeEkTsWc1xdcG1AQUiWLI7BNMlkS5Im/iplWlvUkGs/UxqsCkupbuexXBImQsIUkFTJALSGkHChDRMmXjVpg8oUFEObjsKNVbmMwnbaoAq+ZqDNRxmu6OieBlIYXBjdU5amMQ8sf+tPjY65pzqIIGH4ZFYp0BGV/p8QlDhcQYieZYnMLDjTGgz6N1Woi+GgLXK+XqFoo7hY0IdxOI9g4/aCZ12C7lFhWwgPnxYwRihyNCHvMg0EuIkwWiGRiiDjexSXI+wigcgSNFYww++ANmgQM615sJtOuRTkf0xOIMO9cvZhWdp1g3KtM1DP5cqpCQtDBVqTd2XIyFwqUmhPrHd1oZEwigXm5jmuPCiIydGErtf7FVAwBwUiAOIUn8lq1xlkyU1EKt04xKFGdcrP6W1Cf1Z+nKhvg0LCePwCLktfuhIB0kgKuBFZ4j8nIBscy0YKtnWD5qXgpgR+PlDOWGm0E4IN5d4ofGOBiVcEleEhCIMVrKbQ2/j8Mtcx9/izTbx8yrKC4MnsqkULvhlQgsU3RXl5Vop/sg8sJiX3pjjVXYYlg5sY9lfcs7zc0vV6Xa+ZRmVgX+hUCp17tOO28d+2DtstggRWQkh0FmADmGdxvKKN11fxl8cUa3Qm+NesnjhE2o5XqonV8htLUuuUfvtDyIa9gTMcdHqOF/SGzoduN3SCdsdlXm8I7rxn8+P1TaIuru26Tdf97r5RAc7nDALP7zpe33cdL/Q9h3mB5/SDbs8dur3BwO29qp7XhVzMJgffW+C3AH/++HHiDY4O+8eXvw5OB/+eTD/PDi7PBpPTi8vP3ZPfu5Pz36afD4+9k/G5N/7tl+4fx8eHx+PckjzJbtjeaMylSnCFhsyAY3iybUnH7XQdt+O43fO2O/J6o177DwTN0vDtQUOI4TtB+wVorwDdqTaYbzMDccxU3izJJpHK795G4y1aVqXcgHlBfxiGzrDfDhzP84bOcNjuOsC6834YsoHf6T3axyqoSKpM/7P43Qxk8pz2VbH/o93per3+YPjB/ZGSY28cNxN6EZXv7neVFj0Wsg8Q9hyv12OONxh2HOYCOO2+O+gPwA3Bb6M8wZL94+UG6TP3FROGjLXm2uoYyQRStniCLzIm1aNW6y7nZ2laBltDetN2b4KYY+sLZcK4eByLpdwJ4a65ixUCpDcxF7c3O13l2Tq1dJgi/Bvl08Dpts877qiH0W/2veFb5dQ+4Fq7z+cQ62DDTPaM0QZzMKfd0zGL/cXkbHx4Thv0bDqe/E4b9HR6Mjk6+Rmfxhez6YQ26Ozi4GA6m9EGPRwfHdtXB+OTgyk+Xlf6FSPILFfutVPQ9JHhp+6yYtlx3fYPVidKf21vldd2ZPNcd3co+8hCUg52W8PXT62fXjJvgVLyGc1+AobxWBPmy8zYrMkZ84gqpp+UZE3ZeGIjmB6J/GyCizTLx6gSzm7DbuZS4gRUPuMxyGaGbRTvfaY2ND5TRACEGg9HfCBMEC4MLOycXDp0z5R7IVhmIqn4fyzwm3v0+Z7a/ZSrvVoCWu+twuu/8u+JNGTLskqLUo7ntmvIDzly5H0z/d8lzYaouxuiQ6l8HoYg/pb47HdfJfMlbtjisuZ4u+ag5YcyEz9qur0wLeaFqfsywqtnxBlomakAiNhwleI0BJniZkVHV/f0IzAFapyZiI6urtfXiGEiieeOqbRlMWW4Rlvl6SZFBHUHSluATMV0RClylsAz9Hruljr8xnyW8l9htVMe/3V5TjJdHGthNmN7yt3SIJovBJ644hkTE2Q66/T6JFX8jhkgt2CPTfORjI6LD8Fy0gbFGYlGwMJil48uPqtOT6eVp8uta1XAN3tP7LDV6zLGmyNEu2es1svtX/Vm60yull/1nca2jGJHUL3YHvWr9w+Pnmro1VC8jb2Pdu9QUVvnYi5tEIsuW+6lJvUT7tOYGWzfZHx6RBsUsyQPbqfZbrqYOlmSMLV6sB/bj/FuNjl9j72KESNlTPyMx8Zmh1QLJooI2x6VsFsgfhbfVofwRhJGFkpmKc5oCgKecrsgceNgatIFGDyZb+4d8/63VPwivojzCG8xNH4GMgXhFB96qiRWps09R66KFMTItJxSH8A17EUELmACk4AJbPa2WljGCH/EsVxysSAKUqm5kYqDHqEeDrnSOV6r+O/UbzuctHCS47PgFkR4/a7cRSy4iTI/30G8BOH9iFjjN6qsCH5XjIv8sqUgs1ZxMVdMG5UFJlOFgRgX81RMmy+wbK5sy/ke00qIp2xbgk9K2ldbE0GcOEHElNGPqlyjaxkF0MKdZqt48ag9T5nxC8QJsUBW/xDSWK4wvZ60hGQa6W4zH5QAA7r5Bau7AZXoT/MZqDse1LeqhZpNqRYtS+TIuaMLsgaNeQBC27Jf9o2UBRGQjq1TeVtDrFGrtVwum8yuWrSCVbeOjw6mJ7Op02m6zcgksW0v2DYTJmrA+XFyeUtYXeFtFZvaFd7/zT1m0SYNfDOtNMbDinXh2ftirLiiae02N8KJY3RF7+99puFCxes1vv6aAXaMq+sGvWOKMx/7z9U1HqjkXR3nkFtYFbdZmI7nKBnJ4yyfOB5MWOtGyTEOAkjNo7T1oej00ww39X5x7ZrkjV+xJV6lsiWOQnh/a6s+Eth39zRmYpHlk1mOaee+nbHo1o5FxQNaVS6JVU3DhwNObgj+RbP2stzf50PXer2hz5f+kqNwbUmNsbter9f/BTAv1RU=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Direct Payment"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new direct payment that is immediately sent to the specified receiver if they have a valid registered wallet. Direct payments bypass the disbursement workflow and are processed instantly.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","required":["amount","asset"],"properties":{"amount":{"type":"string","description":"The payment amount"},"asset":{"type":"object","properties":{"id":{"type":"string","description":"Asset ID (use either id or type)"},"type":{"type":"string","enum":["native","classic"],"description":"Asset type (use either id or type)"},"code":{"type":"string","description":"Asset code"},"issuer":{"type":"string","description":"Asset issuer address (required for classic assets)"},"contract_id":{"type":"string","description":"Contract ID"}},"description":"Asset reference - specify either id or type with required fields"},"receiver":{"type":"object","properties":{"id":{"type":"string","description":"Receiver ID"},"email":{"type":"string","description":"Receiver email address"},"phone_number":{"type":"string","description":"Receiver phone number"},"wallet_address":{"type":"string","description":"Receiver wallet address"}},"description":"Receiver reference - specify exactly one identifier"},"wallet":{"type":"object","properties":{"id":{"type":"string","description":"Wallet ID"},"address":{"type":"string","description":"Wallet address"}},"description":"Wallet reference - specify either id or address"},"external_payment_id":{"type":"string","description":"Optional external payment identifier"}},"title":"CreateDirectPaymentRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Direct payment created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the payment","example":"619da857-8725-4c58-933d-c120a458e0f5"},"amount":{"type":"string","description":"The payment amount","example":"100.00"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"7a4c68dd-861c-4448-8813-ea3f6dda7b25"},"email":{"type":"string","example":"horus@example.com"},"phone_number":{"type":"string","example":"+1234567890"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"description":"The receiver object"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"external_payment_id":{"type":"string","description":"External payment identifier","example":"payment-001"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DirectPayment"}}}},"400":{"description":"Bad Request","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-disbursement.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-disbursement.api.mdx
deleted file mode 100644
index 31b6080bf7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-disbursement.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-disbursement
-title: "Create Disbursement"
-description: "Creates a new disbursement in  `draft ` state with basic details. Important: a disbursement is not triggered until the organization adds receivers through the Upload Disbursement Instructions endpoint and the status changes from  `draft ` to  `ready `."
-sidebar_label: "Create Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzlGWtz2rj2r2j0Zbc7GAyYkPKNBHKbuynJBtJOt81Q2ToGbWzJleSwbIb/fufIhphAk/S1s/feL4Gg8z5H56U7atnM0N57OhAmzLWBFKQ19LpGOZhIi8wKJWmPHmtgFgxhRMKC8AowEZKQj1yz2JKPxFhmgSyEnZOQGRERDpaJxNTJaZopbZm0PcIeEDBEKkusFrMZaOAkl1YkxM6BKD1jUvzFUArCODdEQwTiFrQhdq5VPps7uKssUYyTqhLkVBqr8whRDQHJMyWkJUxyh4GC5oZEcyZnYEisVVpRwypCPmpgfEk+1mmNqgy0E+KUb4xRZUZrVMOnHIw9UnxJe3c0UtLiQe+O/tL4BT9MNIeU4Te7zID2qAr/gAhRM430rQCDp5KlUIEyVgs5o6saXbAkATsVfO8pM+bzh7egRSwip8I0FpDsAatRkHnqYqE/GU7PT6ZHp5eTV7RG3w37l9PX5yP3z8XpiNboqD85PR/1z6ang+no6vXR8BJjxgqbIMU3FXYnjtsKDTQTxhZmnKJ5WGSnhQifF2X4un96hlxfnY+Ga0614udpfzSYvu2fnQ0n0/5gcDkcjx9A7oOoiHlZkei4EGiCcjhhizCbbkmdgjFsBlMLaZYwu89NqxqFP1maJXDvS/p6SUaw2A5Pd7TlVAotDoedIPDCLrS8wGcvPcYD3wuazbjr804UhDGtepryVqvLDg4jrxUHvtdsAnghdA48vxW0WNRs+b7fovvdv+PlR/zz0PzPtQ59p3IyZ7dAGMnY0um9YMIKOSOx0mSp8uLm3d3VzytXfcRSWK3q5DgR0Q0eVj11JuTNaoVXtOAOuk5Xq9WquIJCA6e9mCUG3C8mU9IUF6vlN/FjO7H1dxIarVUvL8uypLRc4w+DKM+/yfsu48PEOpkDyaX4lAMRHKQVsQBNVOyS1AOxNoFFD5ovOTvsdL3DbqvjBVHn0HvZbnMPXc6CziH4cQfDeH8u2ScDQj7JdiuA0UnfclX2SRHlxqqUrJFIboCjpw1IToS8FZYV+dx5v6wEdYKoHznELE/sR1KyJsLInyzRYHMtgdfJqXTalcc/GVK6mQj7kyGZMkaECSBpxosiEaskUQuM1o1Et0wLFiZgevuDlizmIppjTUMC1XNnMOQZi1mOZQ5L0f7Y3qKRCHlDZiCxAgEn4ZKMBxcbo1jlgNbGID8LSSJmgNi5MOvSmmkwZamuWKBWKM5yq1JmRcSSZElYloHkKJ11sCD5i/pWEPxtd/q/rGQUmfxrs8K9fTuMs5fAO17Q6TAv6B62POYDeM0Dv3vQBZ9D2Hzsbt9TeiNCzaQlfWOEsYgzVylkbPYE3tzazPQajdsCn2VZPVIp4hvIpk1/GiUCpJ1ylTIhH6fFMuFxuK3v0uIA2RSDe7qTT58tU8PwDMkjvch1ZXzK7D5KsdIpnlDOLHhWuOJ7T77lt9qe3/XazUnL73X8XtCpHwSHvyPhPOM/gvDqPqreFqGz7uK+PYbimEEUhG0vOAh9L+Bh4LEgCryDqN3xD/1Ot+u7+hAp/ozM3EehiIOtMrkaD46RiDAmB/1cMgU0plgNxmwR/NfR0SDonp4cnL39tXvRfT0Yvhkfv73sDi6u3r5pj961B5Pfhm9OzoJRfxL0f3vV/v3s7OSs3/lO3m95fnvSRA/1Os3v5fldohwS+EaiByXRTkl0ta+Wji0kCdPEhRTZBNI65pw33J12k9Cj88Bl/2RCa/Ry2B+8ozU6nvQvJ8MBZs7+1dh9OT5/fXE2xB8rybLaLowLLv+QWaTQeToXxiq9rPBnWrMlrVFhITVP38PcgN47c1V91o7bnWb4EjzgfuwFfsw81m4GXjPodrph0OKsSOh/tyMwuIxlafbdgnv1GMtXhbGH0uolfQ4kAsUigenTla7asXoxhJ7f9lDEemS+V234m7KDVZYl07KxqgaDkBZmoHfbZkQgMk/DYm7YoFa4Nf0dylNTDjhfSN7kUQTGxHmyl9PhLqOYiQT4V7AqEPcrtMtGAzYjaPsv57TB/SwzlqocO54yzp452DkRSYG7mao4MYrETG+Fw6Hv133/PgAKnK/gYhUJ7yc4vsWk6W+4sFvQOJ59CZ8SZ80pA70210Mujslnrng5qwe+vzuMHzFOLos92vebwkFrtac7cYsaq9kzsvxOYi4iB0mUo9S+RdCDVVAphtNRb3S8F2HNJPD9Cll6Km9ZIjgppguSaXUrOHD648kXXtqzMrmSLLdzpcVfLr7+N900UpZsqbnPlM2qKR9g/EjChWvau645UToUnIP88X7Zr929AM8AcHoYiHIt7JL23t/RI2AadD+3c9p7f726rtE/PZw7ZiC9Mqq9UPGlVy5W8XthQpAGF0OOyg0sae9RzBq9ZUm+oYCMUrBzhXvRTLmrkzEUgjb41sMIyqtx6eQY5TqhPerQ12qM0ayF5arK3DeYmfgVljv59d9vJ8WyC1co6GxcBRYeqxEjZhJ48arCJBmOW50DkmlxiwupG1jifqY0SL+ME4eJfSwSnwPjeA9wVpOxctKUmXk9JGxt9i4SZrF9If2L02J7bAopW/Vm3Ucb5GnKsG/eGjT20/h5PLh4gYsoRqxSCQlzkVinZvVxx230UnYDJMyTm00Zdss4MtMqz4o6HYlMuAOFyy5b4S7BLpS+qe8tXf8sET/ID3JSrueYJCoD6RmV6wgwAeMtJHbO3MNYIYqSxKpsvZ59QK62edPCeCcRk9gBxCqX3CFu7TE1ZMoIq7QA00M5PPLeFPQa5ae31UxnpZG8kEU3IPn1z+tNzEzYeR4WW5gvofCiR5zyG1GWbhHLhCz2nSWY00rIWLPiGS/XpYLoF/uUT+tfoFmsXab8FtXWJJ7SbQEhWcN+tTZzSFIvmjNtzaMiV+AaVgM0sMltlD88qs9TaryCJCWOkJOfQ5aopVuTP3nXcoNwN3kIWoIFU/+AacqCTs15PAZ9K6Lquq8Us670rOGAPBV7pgSr0UREIE31qa2fsWgOpOXyVJGfkVav0VgsFnXmTh21EtU0zk6Ph6Px0GvV/frcponLk1gEUiYrhItHX/Lg1Xcr1VReff/fH8zLamfhT9vIEtwSr0p33JWV9T3drqzXuJ02Fg/u7kJm4EonqxX+/CkHrDXvr7FqF68vrjuorQvbfc0/LuzvuZ38fZHHF/hVbQ3UjyLIbOV4pz3a6gcuzse4cwnLh/3UrUypZgt8CGUL1wDUKNsp8zeuzJdfUMT1kVxWeD8s2IWI+BcF3otyd1c0EavVBr44+ixGaac1NHrjerVa/QeRl67T
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new disbursement in  `draft ` state with basic details. Important: a disbursement is not triggered until the organization adds receivers through the Upload Disbursement Instructions endpoint and the status changes from  `draft ` to  `ready `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"name":{"type":"string"},"wallet_id":{"type":"string"},"asset_id":{"type":"string"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"receiver_registration_message_template":{"type":"string"}},"example":{"name":"My New Disbursement name","wallet_id":"e2de8544-b7e2-40a9-ad40-411f70d5c4bf","asset_id":"d227a68c-2f40-11ee-be56-0242ac120002","verification_field":"DATE_OF_BIRTH","registration_contact_type":"PHONE_NUMBER","receiver_registration_message_template":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"A new disbursement","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Invalid wallet provided"}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Invalid wallet provided"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-receiver.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-receiver.api.mdx
deleted file mode 100644
index db5b9c9ef5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-receiver.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-receiver
-title: "Create Receiver"
-description: "Creates a new Receiver. Allows clients to create a single receiver record, which can later be referenced in payments or disbursements."
-sidebar_label: "Create Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWd1X27gS/1d09NTujRPnO+RpQxNaWiiUUNgt5eTI9jhWsSWvJBNyOfnf75FkJ85HCWy79/RhX4ixZ36aL82MRo9YkanE/Rt8AT7QexAS31ZwANIXNFWUM9zHbwQQBRIRxGCGCsIqGsQxn0nkxxSYkkhx5BtKRJCkbBoDEjmtfuAiqKBZRP0I+YShmCgQyNM0IQhgPgSIMpSSeWLQuEABlV4mJJgXVVzBPAVBtFDHwVKsQhxcwQL+ykCqQx7Mcf8R+5wpYEo/kjSNqW9Ya9+kVuoRSz+ChOgnzuAsxP2bR6zmKeA+5t438FWOSAUE2kDwoEAwEk9ogCv4HgQNc0hjslRo6RQFqSEhITTWDzmiVIKyKd607EiTIRIEAqREPEQqWhkNV3DIRUIU7ud4iwpOI85gwrLEA7Ef/1xTI0u9Bb+orOm0X9icGNEAmKIhBYFCLrZA102zgiVCkPkW6lWJGuX2thGwhV3BVEFShlw6at369uu2PsCyRLsyIAomPJx4VKhIc1OGK5gZGQoHz4GIScKZirY3xOU8BW3O+x2yB8YEJM52SrBp0RR8BcE6kGVeLNbDzyAVyLeLxWJReUm8zkgcg/o3UtdAC6Psi9FrQ4cos1pqJ23CoVcJeUB1ZCFfPz9Wc5PuV2qsII6J2PSBXVBrk0DC98OcpTbKkSZfqmFRCuyt4Cve3+plyMOxVa2+WCxuK1hRFcNWPr6wyRgv1rGUyMC8kCln0pqg4db1z7qcBU5eUwIkM98HKcMsjrWHnp3dnzb/7nCCB5KkRqmw1/S8TrPnBAFpOa06dJye6x84gduEDoDfIBA+J9pXiP+pt9vtRrPTa3Xbz4jsFWMmRb3RbLYM0/d27Yr8W8Dhd01W5WKqeXJDToh6mrHhNpqO23Dc5mXd7bfa/Xa96rruF42huCLxpCjSe3A0w8prL+EKCY0heCaHi01AJYQyyqYvY5pSqUBAMNlOBTuY6pbJBGYwIQnP2M7s8dytLyWoic+D3cVquezn8fCNXtnSUymzfTH29vBw2OoeH3VOrj90z7unw9HV+M31RXd4/vn6qvnxz+bw8tPo6uik9XFw2Rp8etf8cnJydDJo79Bvj0Vct+q6Jl8UaWBg2RZP5tdnWmjflui5TbdZD1pOPXBbTqvXPXC8TnDgBH6706qHBwe9HpR0Ej++ots4gAYErhOC13Fafst1el6r67i9Zof02t1WnTTWzFHksROqYFVzflyQNgnIAQRtp9VuE6fV7TUc4gI49Y7b7XTBDcAz4cpIsie8rqgnCFNoICWVppJEPIGUTPfwRUqlsl+r3Vt+kqZVnydrytvCWagubQWbPFHySiH85o/B++Yf75tXH5rvj941P50Oj87GH04bH09PvxyOz5pXx5ed0efzT9fj4XXjfbd12mheXIxPygvtrogbBJPd3eJPSphZGvwwBmX39EUYB9sYMZFqkoCUZAoTCUx9B229CCuagFQkSdEsArbe8GjE4r8AEYaMmLY7Ih7PFFIRlUV/skvOuvsTCkxBOilE+ZXKy7+V4pmVQiqist02zc9sw4vB0SWu4IvRYPin+X17PL4cXYyGuIKPTgZv346G+HY770qbg8Z2geVSk4hKxcX87/vk/yjychvuWm158tKJxtGk+zbbl50Fam3Vd9Y6I6bE3Lbwm+TX+blj1zdsjqe45brbff0hCVBxNljr4n+r/faSxh2E4M84Vw5BERrLZUYCZBlt4y3IfkcbVZb2XC6Mj9k9iakeWqWZzW8FXEghDiYh5/r8UDwjKlcjgkr+3iNiSeMRgRhAYAZpHtiMqmCam9MadMdB6TMjmYq4oP81wD/dos+31PaWyM9D5nBqSs8O+O/Z9yNXaE2zlRTFOi23XkLe5LDIuw6H/9RqxkXNbRcdceHRIAD2j/hnt/lWa77EDGtcRp2DbXXecBbG1FfIWXUDJBZAgjmCByqV/Hnn85cH5aLYLRL8TFA1N5PdQyACxCBTEe7f3OqxRQIq4nqOnHKTilKiv+GaWA7CNYQwTxohEzHuY6xZC+SxVsLKWcZfVZSUfoDtcdL760uUSQjM9EWHkB5SWftUkKRTBgGaURXpFDAaN9odlAp6rwfrdzCv4qKnx4M8+gynLlwaPAISmJRRwdrWF6uZ+Kjkbjs+wJkE8XseBqZ53xxklCt5aUyxer0x7F3N0DdnrPlIdOnAW9PYhrY/z+tHMeIalgb/6DwmStc4NDg/tgtKa8ZGtV51tZOyJCG6kuPLCNDTGK/Gw/PXOhUTpDiPkZfRWBk/cDElLLelScEJuQPkZfHd6k5CcUTQVPAs1dM3AT5N7dUH11tAlVZnoGZc3FW3fP/rifiVfWWXulPXSzLEU2CO5JnwAaWC6y2FVESU/mxF4Qwpnhbzxw24CiIsMB90t2puejxAIc9YYBgj/Y++N6JsigSkXFLFBQXZ13I46CY/mtXyX6d8CeSkuZEcj/h3wILbV8UhdEpVlHk6hmsvQnjdR0b5pShzpDMXodrCEaCczGhFWSiIVCLzVSZyBYsB6pM+rb5As1CYxPkjqhUQ+3SbgYcK2r+tTQRx4vgREUo+KXKJrqYEQE0fqGr5iyf12afGO4gTZICM/AGkMZ/r8NqrCcr0PSW6yzwQDBTI6ledRxWIRJ6FYxD31C9POnIx9UC1ZogcHjoyJ6vgmPrApEmwRYZOiR8Bapg8ZQuIxurXarPZrErMV4OWs8rayfGb0cfxyGlU3Wqkktgkcl2hEsJKwHbWjkqXn2tppnT5+evc3uaFQcGDqqUxoczMR4QZY9vie4NXxfdWj6Gk0i8fHz0i4bOIFwv9+q8MdLa/udVFRVDi6dpxo+tJXvt0FbqDue1UtBWcy/LlWX+7IdF3aZZj4PuQqidpy73D+dlYn/C8/Mo5MSd0LMhMX8aRmW4Y9LX18irUvHvEMWHTzLaRFtO0aFvNw51pHvKHUm0lbF6ScLMNsIrov6UrwnWWx0fbmiwWS/r81vF7HLlpC2rtPH0J+T+9lhdZ
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new Receiver. Allows clients to create a single receiver record, which can later be referenced in payments or disbursements.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"oneOf":[{"type":"object","required":["external_id","verifications"],"properties":{"email":{"type":"string","description":"Email address of the receiver","format":"email"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External identifier for the receiver"},"verifications":{"type":"array","description":"Verification requirements for the receiver","items":{"type":"object","properties":{"type":{"type":"string","enum":["date_of_birth","pin","national_id","year_month"],"description":"Type of verification required"},"value":{"type":"string","description":"Expected verification value"}},"required":["type","value"]}}}},{"type":"object","required":["external_id","wallets"],"properties":{"email":{"type":"string","description":"Email address of the receiver","format":"email"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External identifier for the receiver"},"wallets":{"type":"array","description":"Wallet information for the receiver (max 1 wallet)","items":{"type":"object","properties":{"address":{"type":"string","description":"Stellar address of the wallet"},"memo":{"type":"string","description":"Optional memo for the wallet address"}},"required":["address"]},"maxItems":1}}}],"title":"CreateReceiverRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Receiver created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"400":{"description":"Bad Request","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"409":{"description":"Conflict - receiver already exists","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-tenant.api.mdx
deleted file mode 100644
index 19cb8124c5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-tenant.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-tenant
-title: "Create Tenant"
-description: "Create Tenant"
-sidebar_label: "Create Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWW132jgW/is6OnvOtrO2IUBCh09LgJmSEqC8tduUpbJ9jTWxJY8kh6Y5/Pc9km1eAiXJbHt2PwHy1XPvla6e+8g8YEWWEjducNOPKcNzC/MEBFGUs66PG7glgCiYACNMYQsL+DMFqS65f48bD9jjTAFT+usvpV/0h/RCiIn+pk2pAF+D+1QqQd1Uwy6I5/GUqYW6TwBbmJFYf3CxJIx+M54XxdiKgVhATGi0+RVQIdW+QUSKkbmFDWoDc/cP8HTEidAJKQpSB2WsGg+FlY6KLbGFfZCeoIl2jht4EgJSJmWkJzioq5AMeRr5KCbKC5EKASVEKRAMffn3DbG/2fN//O0LXlsnUn2W293pKJ+O9DTEA+M2i8vBFgaWxnpx293xZNS9nE66g/6i2WoNpv2JM550er3myOn0Z9g6bdK+XMya097ke3at7qjV62zN5uv9nXlWXmYCSiUIBLaehojvC5ASr4/s7EshzVSzV1u4bVW8FE3P3IId1OXz4HambbBcImGRimcu2bg9RC7xboH5SIK4A/F3iTQEmo56DurqeqASBRQiH1GJGFcoEfyO+uBbplY0wopGEVoC04caEGdgIHzEmTEJuVToy2Vz3FlMR70vyOMsoMs0YwALEebvVF12GnQm0k8WKV28PKFpt+QTGbqcCB9d/pRkxu3hYtpdvDCntYXhK4mTCLY8gQX4HhcJPnmsn3269g5N9uufuQeHi+UximvggR46QnUN3CNSHSXOBh6Bj1pZ4NstwqFSiWyUSrlPOy8uR/qF/4NtfTxnY7te6xXbcnxAIglmRCacyYxtK+Uz/bFfCUO9q9LQG2KwyrcBW7vNhCRJRD2TUukPqaftdpbTFE/9Y9W42Vt8Vq9euOBX7br7a8Wu1S/K9psgqNjnZ4FbfgNQrv8a6BL/ua3C2YvJjVIwhfaDSWLPSbGVhbOD/f/x5/qk/z2/iqhUHt24vMtNOv1mf7JojTrNSaeNrWJgOBrMuuPuoL872GxNurN9u3ZnOzj/Xp8uetLz0lYQRURsunQ+WfcQHwVc7PRytkRByny5vyC/tz42r6ofr6qzd9Wr395W31+3fxuM311X+tfXny7Hg+qsO7noTIfvP4zbHypX9dp1pToajXs/QGY8jt0ojKcC/x/qjaPpfr9oDhPObAsRdVRlPTN9U0YdbOFhp9/u9n9fTMedUVFx3UHfxEvlwoeApJHaCc/lPALCDuK7zMZREJElUiExDLKSaBWCCkHsNisqs/gzbMSFbpSOQcy9FUTsGeHuL4g6tkABF7F+gn2iwFbUqOltZVbKlZpdrtqV+uSs3qicNc7PPumqSxP/x4P6EMH3QY/QLY1BKhIneoHY7uqsiESvJA/Ua5SDOn81rL3mdrMl5b2FfYJFTpftqTNs6S62V0Wbe9Jjht5w597uzPfUjG6J+E2t7Hukdm77Z35g12qeb7+pemf2xblXrlWq517lPCjc7CqfnyQgtpx/nMmPLY7hzPez9vVw0OlX3769urqozWqVd9PJoD/42K+3LmaV4Xg2bPY6s6v6sPuvweXFdbV9Nav391ezoUQK+2fkWB045XL50/7CnrBbW1hRZWoqvy9nIql2TAVNGUlVyAX9Bv6P0z4gBBeHp8hoWyWIfBrhgFNZGrsgNEQMUpLlkQaTpblTb3kYuM8V2ktzG0Xhp1Y+20F+PONnAhtsCV4qqLrHjZsHfEkk9ZqpCnHjZr6eW/ir7XEflsDs/L2H7XL/3s6PiP5+QFDZ+xK0eWECXxUwrXalcXEL97hxEtfCdyRKN/g6jBhUyPURTrhR/AnRIeJSxnr65GfKL3ORHTszschurMsn299LIAJEluRmH0lC38FhLlcfJtumqBcPmMor00KSLhn4aEVViAhDnXHl/AIlgt7p9G/h3tlySTNfdzNTH0QNHgLxdV3pZskCbqLJT08hTtpUuqmQEANTaBgRpZkcNYddvUggZBZlxTlzynoN0jgm4v6RwDmO8WrcHr7WzZQgxXmE3JRGyqS5e5uSSHEUk1tAbhrdooTcaxQzStBS8DTRekKARxNqHvC7vFsX3hmoFRe3zkkN9v8R4mf2mU30FVy7ZIgnwGzJU+GBvodrrsikCZV5KPrOzZNCUT2C296ydaUjjzDkAgp4yjaX9YBHEV9piSUg4ZIqLijIho7DRjcywyvln7a/s0h2ki9S0YDmr4ous6QqTF3H43HpRQivG8gkvwnlXr81UISyTHAVVyydFWWBIFKJ1FOpyBPU+6Ke2lPnBZkFwnSE/ya1AuKp3FbgosL2L2cTQhTbXkiEkidD3rErKQFQigllpXzgZD5PpfEWohgZoEzEQxLxe11eT2aCUqntblMXBAMF0vmsaUqBiOUgGIO4o97uBTYPU8uYkjGyeWDL3MzCEfWAyd3XSM2EeCGgiuGprSxqlEqr1coh5qlBy6fKUq/b6vTHHbvilJ1QxZHhSU3/MWE7wI+7zR7JbOhdwVdVSiJCmdHw2bU+ayI3uGgicwvr12d66OFB67epiNZrPfxnCppWb+a6NQlKXE3SN/qWk3P4trG1MhljTzIRW3Qy/d/A2iqMmp4Hidp5fKB49precDDWV0U3/8sh5r7Rp2Sl/44gK9Pr1uv/ACMxhh4=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/tenants"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Create Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"required":["distribution_account_type","name","organization_name","owner_email","owner_first_name","owner_last_name"],"type":"object","properties":{"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`"},"distribution_account_type":{"type":"string","description":"The distribution account type of the tenant.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"owner_email":{"type":"string","description":"The owner user e-mail address"},"owner_first_name":{"type":"string","description":"The owner user first name"},"owner_last_name":{"type":"string","description":"The owner user last name"},"organization_name":{"type":"string","description":"The organization name"},"base_url":{"type":"string","description":"The SDP backend server's base URL. If this field is not provided, the SDP will generate one based on the host `BASE_URL` configuration, and the tenant name."},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL. If this field is not provided, the SDP will generate one based on the host `SDP_UI_BASE_URL` configuration, and the tenant name."}},"example":{"name":"redcorp","distribution_account_type":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","owner_email":"owner@redcorp.org","owner_first_name":"Owner","owner_last_name":"Last","organization_name":"Red Corp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Provision a new tenant","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-user.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-user.api.mdx
deleted file mode 100644
index 22aa14dcc0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-user.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-user
-title: "Create User"
-description: "This endpoint creates a new SDP user as the result of an SDP owner adding their information in the UI. It also handles sending the invite email."
-sidebar_label: "Create User"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1lv2zgQ/isEn9pCsmLHzuGnTY/FprtoAzjBPrhBMRJHFmuKVEnKjtfwf18MJcdykjrbLgr0xZI1B7+5h2vuYeb4eMpvHFrHbyMu0GVWVl4azcf8upCOoRaVkdqzzCJ4dAyYxiWbvL1itUPLwDFfILPoauWZyRnoQDRLTVQhpJ4Rh7RM6tzYEkg7kzqI3Vz22KVnoJxhBWih0DGHeivEpF5IjwxLkKrHI24qtEHBpeBj/iZAIvQ84ha/1uj8ayNWfLzmmdEetafXV8kreriswBLoza8q5GNu0i+YeR7xypJeL9ERNZfW+c8aSuzwOm+lnvFNxBUcolqjGi0tBayFFY+49Fi6JyQ2EQ/GfYN0B2Wl8CEq/t4Umu9B4W8N8vvjpzytndToQlTbA5rnb40vM1PyzYbOIL9Ji4KPc1AOwxdXGe0aOwZHfXrsZ0bjeMGjrpuhqpTMQnSSL474uj7fHTNtAUVdmyIuSZ10nyHzcoF71m3tuo2eCZ0Uj/3Y8SLvnx6fpCiO49P0fBAPT0+O4rM8H8Sjfp4enSEenZ7nFMVDKdDVF+JwOCe67BSjAwH/oezZeWxHTo1RCHo/haaNe/gpDLOT0WgU9/PT43h4nh7HMOj34/x8lIpBeobZ+dF+bA7k27dSq5OJAheoKEgUvg5ab2vcRC2oUT4UeV+IODsb5vHwbADx2RBEPBr281wMT/B0BI9AgcYfBZVLDTqToD5TAluj1CN8TTVQykkfohf6TFMzw6eK4kZD7Qtj5T/fVxmHUxqtNfbJZME7b8E9r8F58HWXT9dlSqZEvETnYPZUJ9s8aD8tDP7BeLZn5g7F9pzhUb+j+aHEz1TchOb4cWh+NzaVQqD++XF52rodgP/AEOxwmNVW+lUo3NcIFu1F7Qs+nt5SUt7FmRE4Qx23cy9OjVjFbR3Qe+NC1E4a7YKWOa74+KBkxBeg6nsNdFCJvjBUopVxwQtAIHhSh52BcNoFvdEBtaWyC2Jb+BNyZ+OxrhG7DlfJP5Gw7gfs/d/XtF4Ilhsbgozat5GKmJMzjYItpS9o23g3GYxOWGXlAjyyOa5oUWgdcdHmR5CkRkrKCwQRSpn+5yagaWt84lEpsOytdGltHZaoPbtS4GlzYRdXl+QitK5BOej1e9QrXV2WYFdhZUJ2WMeLydurl0zSHuWNUSytpfLBTGNnoFuojnnDSpgjS2s1ZxWsSEv4CmxmTV3RqmUxk5UMBLNAGzam7eka/dLYee+Ra389iJ/0Jx12TTpSM1Ohjp2pbYassoaqj/kCPJEbKEYzb4L6J9RFDLQIBMpzloFmKbLc1FoEwYL+KGWWtGNarIyT3liJbkw4YjZ1jb6kfcai46S4ap0Up5DNUYvbF4X3lRsnyUz6ok5p0CTfpeHlmAXj76GsGLUokLrZrFu2YJXUuQXnbZ352rYGUlz8czHtfYdluQ0d8v+YtlXxnG1LTNmW94etKVCVcVaA9e4g5A5f4i1iUoLUSfvhoD3PmfEHqpIFRQG/wEqZ1fYKc7jWaE2fsXmdotXo0fU+UZvyaEv3MZ+gXciM+tLWrBZmz9hZEphik8euZYu4khlqFwbLtgFWkBXIBqFPNf2ZdI2TZLlc9iBQg7ZW1CV/Xb5592HyLh70jnqFL1Xok9T8S9Adxc0VgLWXr70W07l8/Yp3yHbyeLzzSaVAhg0+uGbdTrcpr7c34oKm3njK1+sUHN5YtdnQ5681Ur+f3tLEtBLSsGHfbqLtcNnN2zeNL+JrOnY3YOlSSutvw3SRZVj5DvnRarI3i68+Tq551Azp8ZqXRpCMhSXtuLAMQzji8GjUzsOobV8I4pakV52zHw7NBiL9EuAnRdbrZpBvNvf8DembEq2fttwUhdvNZvMvTKbC3w==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create User"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/users"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint creates a new SDP user as the result of an SDP owner adding their information in the UI. It also handles sending the invite email.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"first_name":{"type":"string"},"last_name":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"email":{"type":"string"}},"example":{"first_name":"John","last_name":"Doe","roles":["business"],"email":"email@email.com"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Created","content":{"application/json":{"schema":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-wallet.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-wallet.api.mdx
deleted file mode 100644
index 966b61bc6c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/create-wallet.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: create-wallet
-title: "Create Wallet"
-description: "Creates a new wallet provider that can be used for disbursements. The wallet must be configured with supported assets and proper authentication domains."
-sidebar_label: "Create Wallet"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWFtz27YS/isYPCUdUpIVO2n55sQ+U7dp4omdpnMUjQckVyIqEmBwkaKj4X8/swAoUpJj2W0z0xeLJne/vWCx+wEbathc02RCP7GyBKPpNKI56Ezx2nApaELfKGAGNGFEwIqsnBiplVzyHBQxBTMkY4KkQKyGnMykIjnXqVUaKhBGD8htAa1eZbVB0UyKGZ9bBTlZcVMQbetaKgM5YVqD0YSJHI3UoAizpgBheMbQI5LLinGhBzSi+Nm9vMq3jvo4aEQVfLGgzWuZr2myoZkUBoTBR1bXZUAb/qkxyA3VWQEVwyezroEmVKZ/QtbicAU5JkmwCmhEC1lBzeb4mAPUdyUXi7uAEFEN9d3J6C4rOQhz593FtPpwDAeNZhxUZ04bxcWc7if/Z1sxEStgOUtLIKhE5IyYLqPtStCm59dx3CBJPn54+wDgQXRHgS8AaoIaxGu4euih93KPBu7N1VEjN5fX8cmIeK1QEM7QbqmgARCYuLyHmUpZAhMHoJ8KMAXsOMs1CfoO3Wq/4jNmS0MToyw0EfUF2zPAlGLrA/hzfIupdvJEwQwUiAx0r/bTNTEF18E8jSg3UDloKeD9jCaTw/Lcs7ILjohXF3S/9nh+PMce6eqCNs3uHuA5nTbRMUfelExrnu1He+CKRzl0BoSt0FrmcdAkzWT+iNL2jjvZJqJcawvqsVpemrA8V6D1QegOIvixhX5EMt4xw5dA/nj729/Oh3BQdHqva9PGvfcVecfz41X5FuYsWydkrzqvLjR5ljEhpNk2dtenQ3eecSjz559Fv0R3PW7QEcNNCXud+YNvy16giyBsJgW6lkL7XIxHJ/izt0391swcZE60zTLQembLcu2W5i92+cdsEPjKqtoFdMZy9hPkZ/Hp2RmLT1/9OI7ZCCA+eTl69fIVjHJIT7D6vtXkO6TfeaqYMORca45ZebiJd3qFMbVOhsOl12d1Pchk9ZSW2mGxmsc5LAeHWI/p/8d8Guq8RnjEC6t2x8x9SDOpKvxCc2YgNtzN2g5+PBq/iEev4hcnt+NRcjZKTs8GL09//C8C2zr/HsC9Gg68onF1ezoaHVbma5aTQDpITJas5LlnLKCUVHq3On8Y/vCUgnQQj5m+hvFSE5ZKa9wk84o4CL8axfRRSy68bWq2humVcAERLmpraB/O9YK7mZQ06Z5xdG43dxTep0xtZVKmiADINTESWwwThAsDc+QdTZvke7b/R4EzXir+Pwf8j2f08Zmi2jBj+3LCVqnnTRVofe8Wbr6V33fSkJ3IOi9aO6ejkx7yvoZHvq/pfS9rboleHC7Rf6RKeZ6D+C7rc3/6OptPScOOlgvnp8Nw3kgxK3mGezrQQuzqEWn7dETwxLNPe1mJpH1N4CvXRv9zk+npZdu0+0lDZhU3a0cjXwNToM6tKWgymTZTXGtTSDxH1VI7uwy/0eEqHAwRQC1BaadvVUkTSlGxxb3BELyXffSOgdT8VzikIL98uu1OjrsEPiKaz8WWewhyeTM+e0lqxZfMAFnAGk+BfsjS81CdnvpHFKceLYC5o0wTUcz0h+5MeNmVQwDY9tRuAvf77P4k7L7dP3H73C2cQZDkdAeGiecZ3RJuM9WS3pbydlAtnb1HKTBDXJE+AZy0osiguZhJtyJhqN0YKEumyEXvwE6uS2ZwYpLz6ysaUVxyv1LjwclghPHaqmJqTROKJ/uHMZ7dXFw/x2nAiJGyJKnlpXFLLdWcibBcbgpUbAEkteWC1Gztrg7wLSNzJW2N3FRBxmvuPshlOKm11gWYlVSLwUF5/ftc/Cw+i1s85qFJQWQNItbSqgzw7I171t+qcB1ckYIYWbfH9D24yF2V4AeslfYqZiatyJ1igf+UpVxxMScKaqm5kYqDTtCPmEy0xxuG37h/eRPXIUlxyrIFiHz6rCV5c24Km3qC9xSE5wlxwW9dWeNlkMErHedsEHNRcTFTTBtlM2NVCLC9T3hwTQdPiGymXGf+O6G1EMdiW0FKWtm/HE0BZRVnBVNGP+hyT25oFMAQ29IwvHgwnmNh/AxlRRyQv+2DupRrLK+jkRCrUW5hU1ACDOiBO0MaUJV+P7sBteRZ/yQR3BxINR86oVjOYh3EIlryDITu9/DzmmUFkLHrU35GIVYyHK5WqwFzXx1aUNXDt1dvLt/dXMbjwWhQmKp0swJHYMVED9gfYcn2dnGnyfRuF//N16VhUBj4aoZ1iUOqCUnahGk/oavuGrhAHpBM6GaTMg0fVdk0+PqLBez9k2lEl0xxHG2OQkTtsMXBtoC1p06YlfjW35ssWWk9EdjjPzjFvMZ5lkFtHpTtU5Xr9ze3NKJpuOOt/LRUbIX3tmyFDAVviV3/RgH3bkNLJubWD3iP6TjjAVtZOLYSHnp3b0ysex7u8w4fCP7tDeddlc3Gc6Gm2cr7T9/UCKltpXHppk3T/B9aG1Dk
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Create Wallet"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/wallets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Creates a new wallet provider that can be used for disbursements. The wallet must be configured with supported assets and proper authentication domains.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","required":["name","homepage","deep_link_schema","sep_10_client_domain"],"properties":{"name":{"type":"string","description":"Human-readable name of the wallet provider"},"homepage":{"type":"string","description":"Homepage URL of the wallet provider"},"deep_link_schema":{"type":"string","description":"Deep link schema for the wallet application"},"sep_10_client_domain":{"type":"string","description":"SEP-10 client domain for authentication"},"enabled":{"type":"boolean","description":"Whether the wallet is enabled for use","default":true},"assets":{"type":"array","description":"Array of asset references supported by this wallet","items":{"oneOf":[{"type":"object","description":"Asset reference by ID","properties":{"id":{"type":"string","description":"Asset ID"}},"required":["id"]},{"type":"object","description":"Classic asset reference","properties":{"type":{"type":"string","enum":["classic"]},"code":{"type":"string","description":"Asset code"},"issuer":{"type":"string","description":"Asset issuer address"}},"required":["type","code","issuer"]},{"type":"object","description":"Native XLM asset reference","properties":{"type":{"type":"string","enum":["native"]}},"required":["type"]}]}},"assets_ids":{"type":"array","description":"Legacy: Array of asset IDs (cannot be used with assets field)\n","items":{"type":"string"}}},"title":"CreateWalletRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Wallet created successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"}}}},"400":{"description":"Bad request - validation errors","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"409":{"description":"Conflict - wallet name, homepage, or deep link schema already exists","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/default-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/default-tenant.api.mdx
deleted file mode 100644
index 46017e9842..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/default-tenant.api.mdx
+++ /dev/null
@@ -1,77 +0,0 @@
----
-id: default-tenant
-title: "Default Tenant"
-description: "Sets the tenant specified in the request body as the default one, resolving all the incoming API request to that tenant when the env `SINGLE_TENANT_MODE` is set to true. Once set, the default tenant can be overwritten but never unset, although it is only effective when `SINGLE_TENANT_MODE` is set to true."
-sidebar_label: "Default Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWG1zGjkS/isq1VVdsssMGLCd5Rs2JMGxgRhMcnF8RDPqYbSekWYlDYS4+O9XPS+82MR2crtX92G/BEfT72p1P9131LKZoa1r2uaxkPSmQjkYX4vECiVpi47AGmJDIBYkk5aYBHwRCOBEyOxcwx8pGEs8xZeE5bQcApZGligJFaLBqGgu5IywKMo+C+mrGA/aw96a3ypiQ2ZLPYsQcvkg5+TLqNd/c96djrv9dn88vRh0ul+IMMRAzqdTcMlA+oAnlR0TCnE+k8QDouagF1pYC5J4qSUS5qBJKjM2FtlQpbOQCIvClYyWBIIAfCvmkBv0HEM+y8+ys6tdGJIaCNKIBEoTDnOIVBKDtCRJdaIMGKL0xuVRZ1iwcOItCSNGyFkEROkZk+Ibw6txyTgUBkOqFnnQt7+iMeZWJMV1LTHYW5coJEHHl+vgM8mJEXES4dWatREGbJoQlYDOpLIoWqJBGmI1L0VKAE5UQBKt5oLj6UJE3Geak/H5iPigrQiEzyyYzPs4jaxwymtRMhCzNBdv3M+SVuhaXY/TFi0iOc7oaYUWFp8ovqStO+oraUFa/POX6i/4Y/wQYoZ/IanQwDG7BcfUtssEaIsq73fwUViiUZkVYJBecPy3oDFWCzmj95/DeCuI3KWrVYXCVxYnEZQS6MFx48gD3nCOvd/qTvP4qOa8CoK6c3gQeLVXALXj3wK6WiHrxsKARQayE5MoaXKD6rUD/Nm14F5qcbBMRIZWtkPBkiTCkAslq78bZNuOy89EYe3kM92rUMli+KF4IoNLepaYUKURJzGzfpilWMKsBS3Jl39fM+ebc/PrP764OzZ5UQq+0gnq9ZiBaaqj5+nGLPeYfwv4AEDPQf/TEBRBri7Pd5WE1iamVa2WypyCzzU8cZWeoXLDk2kqpj9uw1WvypkJPYXv5uRZ+nf0WmZTs/fiZBrjAygq1ulltz3udmilPBheDia9UW/Q3z5sn457k126TndzeLOqUC5QhZeiH1Pm+yqVdso412D22rHHbQtRxDQpmEnBnJe9rE6uVcgZCVLJzW5A3px+bJ81Pp41Ju8aZ6/fNt5fdF4PRu8u6v2Li08no0Fj0hsfda+G7z+MOh/qZ8fNi3rj8nJ0Tr9nfm7zz9iOHE8aXtxEpzcaX/ZOrsa9QX/aPj0dXPXH7mjcPT9vX7rd/oRWHifpnEwn7avz8ffoTnuXp+fdDdl3b+v7SfPQ4ZwW63zWXLfErWPwTPezNOrSCh12+51e/830atS9LDOuN+hn9gozLRr4lnmeUhEw+cC+k/ycBBGb5RjChNgUFyHYEPRO47uHTzSRyrqZxEJbWYh9DcwCnzK7L0CB0jF+oZxZcKyIYScz67V606k1nPrx+OC4VT9oHR58wqxLE/7nC+UQwfeF7im3IgZjWZxsAEeJuZghL4wK7EtSCHV/1qyd5na9Kco7gX2iijyeto+94Qp2sZ0sKvrRwwq9rp07t3PzsK2/ata4z5qHDj/ggdNs+tx51fAPnKNDv9asNw79+mFQqmlRDTxrSNv9aF3Bi48PGsie/nGfZ5u2eL77K/m+4GQ18/2kczEcdPuNt2/Pzo6ak2b93dV40B987B+fHk3qw9Fk2D7vTs6Oh71/DU6OLhqds8lxfzeaLQS6u29kXx64tVrt025gH6FbVagVNsupAu3lIKm5DwVdSZbaUGnxDfifh31Aa6UfvqIM5FnNzNMSHtRUmcYeaBQRgzFstqfB5G5u5VthBu0rS3bc3FhR6mnWDrYk3+f4KwXnV9N4eDWvlfYE5yD/+nvZ793GgGcQZH4Y8FMt7JK2ru/oCTPCb6c2pK3rm9VNhX51fMVhBtIphg8HZ12neOn4dx5BkAanmEzILSxp61HOCp2zKF1LQEUx2FBhrUmUyYLA0AhazcuzqRbPrxiesARkiDXXmJeLTE7pzgjDm0fwBJgGnXu1DiNLxDtYPmgSZx/Gm2aOlw7SFjdXIUbMJHCyEDYkTJLuqH54RBIt5swCuYWlu6mB7SJfMk4sICg8BMbxPWCTl4HKrClefQmqOsJ4qTaQDcjDiFnsQLgrwJiBNrmVdffArWEM0jhmenkPmO2X8WLUGb5EEMCIVSoiXioim7m5PTwbnJ5jdgvES6NbkrAlSslOGZlphSNxQDT4IhHZB9wq5DNzoV2CXSh96z6KHf8/TMRtRbZJQJUSZ33pGJVqH3Cix9eYQyphClOy5UJSIsF74irZJgE/YOKXW5dApZJnjCH+B1cWCA01JMoIq7QA00I7HHJtcnnV4tfhW0FykiJIZeO8eVF2x5mwYeq5voqrPyThZStfo6xNWeJKwjIhc6BYjobolZCBZsbq1LepLhzEe7FP3an7A54FOquY/41rpYinfFuAR0ran/YmhCh2/JBpax41eYuuajVANWZCVouDR/15yo23EMUkE1Qs15JIrfddj7+1FPdq5Db1QEuwUOyfLOjYDIIR6LnwtwfvwkyEX9WMyFGBYwqyCo2ED9JkjaYsgAnzQyD1rE5t4FyrWl0sFi7LvmbSClZTPe+ddvujrlN3a25o4yirk9gNYia3BJc7oPVWbKfKbG3F/l7f/r2+/R+vbwtsYeGrrSYREzIbfPNdWA5ormkBaDZzdwlpbio0ROzTuqZ3dzgFXelotcLjP1LAJn99g7hJC+YhZLjGXUGBKDao6zTPfmecj4IlzML98KpSErV9HxK79fkBPt1BZMPBCBcuXrF2jhXPpjy2wJU0W2TIa7X6DxL6xLI=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Default Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/tenants/default-tenant"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Sets the tenant specified in the request body as the default one, resolving all the incoming API request to that tenant when the env `SINGLE_TENANT_MODE` is set to true. Once set, the default tenant can be overwritten but never unset, although it is only effective when `SINGLE_TENANT_MODE` is set to true.
-
-Default tenant is useful for development purposes or when the SDP is used by a single organization. This allows the organization to skip specifying the tenant in every request and simplifies the SDP setup operationally by removing the need of providing wildcard TLS certificates for multi-tenant configurations.
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"required":["id"],"type":"object","properties":{"id":{"type":"string","description":"The tenant id."}},"example":{"id":"1736bed3-7b92-4760-8ff2-51fb08ee079f"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Default tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.api.mdx
deleted file mode 100644
index c57a26092b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: delete-a-disbursement
-title: "Deletes a Draft Disbursement"
-description: "Deletes a Disbursement in Draft or Ready Status by `id`."
-sidebar_label: "Deletes a Draft Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWW132rgS/is6+tJ2jw0mQEj5RgO5zd00yQJtT7ebQ4U1Bm1syZVksizH/33PyIaYQN76sufeL4mxZp550WhGM15Ry2aGdj/TvjDTTBtIQFpDrzzKwYRapFYoSbu0DzFYMISRKiERkvQ1iyxRmgyB8SUZWWYzQ6ZL8kXwLzXqUZWCZghzyjdAvSoK9WjKNEvAgkZdVlSyBGiXCk49KlB8yuyc3tXptE9UROwcyJcqnBOq4WsmNHDatToDjxq7jBHSiCSNgXoU/kpjxYF2IxYbJAjnkDDaXVG7TB2l1ULOaJ5fIZpJlTRgcP0gCPDfPv/wbe9wsEzEhno0VNKipd0VZWkai9A5pP6nQebVrnA1/RNC5xiN7rOiEC34roJ3vTKeA8mk+JoBERykFZEAvXYU33Y7/MWcO7r0sPGas6N2xz/qHLT9Vtg+8l83m9wPGwcBa7WPIIjaNPfKnXmKDkj5qNgtd50jdo7eDkEsQE80zISxRfBMEjCGzWBiIUljZp+oRZgZqxKyZiKZAU6sIgYkJ0IuhHXoBt+t5ZoaQdYvHCKWxfYLKUUTYeQLSzTYTEvgNXIqnXXl8gtDym0mwr4wJFXGiGkMCM04d6SRimN1I+TsVqMF04JNYzBdslrVLvSMSfG3Uwr9kefkZi7CORHGAVTXncNQZiRmmQZOmOSIMay47UzI67sYsZDXZAYSjyVwPKqj/uXGKVY5orUzyEshScgMEDsXBiGksiTVYMrzX/GAVxjOMqsSZkXI4nhJWJqC5KiddbQg+avaVhB8UhmZswUQRlK2dKFww4RFL0VKk6XKSKRVst89NXIci/D6HrvdruJb0LUitCoRhbvFQjspomg3mkBmCabGwbve6Rn16OXbi/PB5Pz9uzeDIfWK15PeeX/ysXd2NhhPev3+cDAa3aHcR3HlUSusM76q9HGh0Bj1yD16w+IY7LdmhVv/thlnr4G3/Va7zfxW5+jAZwGA3zgMOocdCDhMGw+d7VukD2KqmbSkZ4wwFnnmKoGUzR7hm1ubmm69vij4WZrWQpUgv4F00ggmYSxA2glXCRPyYSyWCp/DoraLxQHSCQb35L5k/rhOdcNThEe8UAMekAmz+5AipRNcoZxZ8K1IYAv+IDho+kHHbzbGB0G3HXRb7dph6+h3BM5S/jOA89uo+liETu5RZsyPiKEoYhC2pk2/dTgN/BaftnzWClv+YdhsB0dBu9MJXH0IXU19LDP3UCniaKtC3o/6xwgijMlAPxWmoMYUq8GYLcD/vHnTb3VOTw7PPv7auey86w8+jI4/Djv9y/cfPzTPPzX7498GH07OWue9cav329vm72dnJ2e99g/a/QM/aI4buEPdduNH7fwuKC/uHt8DeliCtkvQfF8tHVmIY6aJCymyCaR1zLndcGfaXQEfyqj9Ye9kTD06HPT6n6hHR+PecDzoY+bsvR+5h+OLd5dnA3xZSZbV60Jx0UR5C9AiKq9Uk0hAvD+W17J748Hk4mTy5nQ4fks9+mnQG07eXZy7H5en59Sj573x6cV572xy2l+n+4oSHyriTpy0jc2TuTBW6WVFPtOaLfEaayExj5/DzICePHYYm1Gz3Zi+Bh94EPmtIGI+azZafqPVaXemrQPOioT+b28EBpexLEl/WHDnD4l8Wzh7IK1e0qdQIlEkYpg8XumqN1Y/gqkfNH1UsRaaH1Ub/qXsYJVl8aS8WFWDQUgLM9C712ZkIDJLpkXfsGGtSGsEO8gTUzY4z4Q3WRiCMVEW75V0tCsoYiIG/g2iCsb9Bu2K0YCXEfT98yVteO8VxhKV4Y2njLMnNnZORVLwbroqTowiEdNb4XAUBLUguA2AgucbpFhFprcdHN8S0gg2UtgCNLZnz5FT8qwlpaDX7rorxQm554jTPMel1r62/A3jZAhfMzDWI8dMYu9SlEvCtrpSYufMkjkzxFimrbOz0rT/Uv/lOX06aK2ecH/pF/MBwqYqK5sjx5ij9Vazx+uFs3zjqY1geioXLBbY4aZZ4cw1nKuPk0gpvNStn7Gt20xMvPL9lOkNzZRpIgG4KcOBSbI+Cnm+9n9j1//vJcvsXGnx98/x6NM9tVsMi9OKEGX7um/4c49/z5UlW5bdarGW0woaFeS7HAXyvlnQz5Lmtqi5u0UnSk8F5yB/yv7sd9+tzOe4YYvLmdPaNQctP1GZ/H8Nt2eGRVSaui8iWtWIGIJRmQ7BjW8KrrU4A2GmhV260esbYBp0L7Nz2v18hcPPBOxc4ei2SJxuWourtF5NoKa+EjyniKYX6zlupmPapRRR1kJGuAOFi6qibu/LqfgVljup8r8fx8XsDidCGNk42Sxc5BEjZhI4uRF2jplpMDpoH5JUiwXO165hieOmcqTcKw+F41xPl+fAuMtk+DtSTpuy0Kx7nq1B5WXMLN7GSO/ylLr+wxRaHtQatQB9kCUJwzZgq2/aj/Fy1L98hQmYEatUTKaZiK0zU1WGXS7xJuwayDSLrze3CjdbJDOtsrS4doQiFW5B4ezOVqRLsDdKX9f2VuL/LRX/kH/IcTltZJKoFKRfRm+qFR63olwLU6qiJLEqXU+b78B5bi6KCzhwICGTWMHcEXCMW2NZDakywiotwHRRD598NgVevfzvb/UGaekkf8rCa5D86uV6sDQTdp5Ni6HScxBedYkzfqPK0s2VmZDF+LYkc1YJGWlmrM5Cm+nSQNwX+9ie1p5hWaRdHv0e09YQj9l2A1Oypv1ma+YQJ344Z9qaB1Wu0NWtBqjjnb1evnjQnsfMeAtxQhyQ059DGqulm/o/etYyg3TX2RS0xC9utT8wTVnQibmIRqAXIqxOL0s1a0rP6o7IV5FvSjKPxiIEaVzVWCfAlIVzIAcuTxX5GbG69frNzU2NuVWHVrKa+tnp8eB8NPAPakFtbpPY5clUGZswWQGufCF0XwTvfOHbyjmr29L8PV8Wy5Jh4S9bT2OcHOelTauyRn3eauSxCesKjoOMuTIWl1erKTPwXsd5jq+/ZoBp+/OVR9ffZVwh48LgM998LrzXnJfD8h79ijz0fXKv6usSKLH+LVic4S/q0WtYFl9D8yscuRfVCtUqFnphCKmtsOzcH7bKeH+A4xzqUbZTea9d5S0fUMBeje7W0EIL/Jt797CsVkVdz/MNfbF0L0dp5cZ4NCLP838AieCGsQ==
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Deletes a Draft Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/disbursements/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Deletes a Disbursement in Draft or Ready Status by `id`.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Deleted Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"400":{"description":"Bad Request, Cannot delete a disbursement that has started","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-api-key.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-api-key.api.mdx
deleted file mode 100644
index 7b74f62ca1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-api-key.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: delete-api-key
-title: "Delete API Key"
-description: "Permanently deletes an API key. This action cannot be undone. Once deleted, the API key will no longer be able to authenticate API requests."
-sidebar_label: "Delete API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVV01v3DYQ/SsET0mglWzX7UE3t3ZRN0FixA56cHzgSrMrZimSHg69URf678VQkr22NzbcIkB6Wa3E+XpD6r3RRpJaBlleyqOzU/EWuiCvMllDqFB70s7KUp4BtsqCJdOJGgwQBKGsYIcVdLm4aHQQqmJrUSlrHYk5iGhrZyEXH2wFo1udCWpgchRrbYywThhnl4Dso+YGBDmhIjVgSVeKBnOE6wiBQi4z6Tyg4mSntSzlcYp8dHb6FjqZSa9QtUCAjGkjrWpBllLXMpOasXhFjXwI8KLhcvV1BKFrzrvQgMIt7lVLbkQhM8nlaIRaloQRMhmqBloly42kznPCQKjtUvb9FRsH72yAwOsHe4d8uZ9/SjF2SYRYVRDCIhrTyT6Th3v7j50+We6SQ/03MLrKWQJLbPemeMOXR0W5+ReoiJuE3EPSQ0mA6HBH7ZmEr4QqPB8hkKK4bWdjOwfkEC2EoJawqzV9yqBab2CrDPnekbiH7K6KKc/h3v5W5IceQ2TlveHzo50tvgTu2Oa7ZUtb9NPjLfrd4VzXNdjvsj+723eX8yVtuOeV4DxxTPkFX7ho/6/H7oXHY4K662Qcbp+MjxBcxAq2GjSlC1BF1NQlUvoVFAIeRWpkeXnFFNECNY7Z7JZhEk+VslBez1bQhWKj615yILyZyC2ikaWUHGCKf87NH7qzneW2C8rrgSfv7+yff12IGKAWC4fb5KudzUTQSwu1WGtqmPZPzg9+/kV41DdMziwAMpt49mh8L5LnRLkNqJp3pef7hUvVaOI+y3MCYxSKYx3mEQO0YEmcGUULhy0zr8wkwx2qPMj38z3uQWxbhd1I3E/HeHV+fPZasD4Jcs6IedSGEkyHS2XHUgOze6tWIObRrIRXHUdJT5VYooue1QCh0l6nBXcDmNRhym6B1g5X+U5t+bFK/Gw/2yTZOsm482Bn48H16PhNE9Qo4uWhFGcFOT/p4YNwmVC2TguVq4H1n4U8nf7k2PCNMW6t7VIgeBc0OdQQSq5jJi7DEK8Yr7N6q0kzPzZpNlfVCmx99aoh8qEsiqWmJs7zyrXFiyK8Lod55baUTjCHKc0dbkCMZgmVtgtUgTBWFHEEyPtCz+1p/gJkC0wU+l+gTSGew7aGuZhs/zWaBkw7qxqFFJ4secuuIAQoWqVtMT54Es9zMP4A04oUKNVfgzeu4+P1LBIRA9ut4hzQ8hybf2aaIsA2fFicA97oinlpgjWWmTtcFslo5hazMJpl0ugKbEiCMRGgV1UD4iDx1MDPHKssivV6nau0mqKNrqF4d/rbyfvzk9lBvpc31JrEk94FapXdCjyMuWIc0h+yzOZOh3+0aX0UHoKvVHijtGV5Tp3ZjCJ3KSeRk5ksdc0fII0LxCubzVwF+ISm7/nxdQTm/curTN4o1FxAUsJaB/5fy3KhTIAnuvPq4zi6vxYvnvp3QpmE1fKm3CgT+U5mcgXd8OHRX/XZpIFc67BwVFXgacuFp6d7o8DxybuTixOZSfVIwlfpBIx/OObOIh6K8ZCYf/vsGy6bzTAg9P2t/bD0TY8R2C1ey3j7/h9IugUA
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Permanently deletes an API key. This action cannot be undone. Once deleted, the API key will no longer be able to authenticate API requests.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"The unique identifier of the API key to delete","required":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"204":{"description":"API key deleted successfully"},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"API key not found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-asset.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-asset.api.mdx
deleted file mode 100644
index fa3636ede7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/delete-asset.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: delete-asset
-title: "Delete Asset"
-description: "This endpoint is used to soft delete an asset."
-sidebar_label: "Delete Asset"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVsFu4zYQ/RViTgkgW6mx7UG3dGOgaRfdoE7Rg+MDLY0s1hTJJUf2qoL+fTGU5HqTTYJsL71YljjzZt5wOI8dkNwFyNbw0e+kUf9IUtbAJoECQ+6Vi68Z3FcqCDSFs8qQUEE0AQtBVgRbkihQI6GQRsgQkOaQgHXoI9ZtARncRINrXoQEnPSyRkLPgTswskbIQBWQgOJgTlIFjzO4vRG2FFThEINjD2EhAY+fGuWxgIx8gwkEajVDBlU7zQb42WlbIGSl1IEN8gprCVkH1LpoSV6ZHfT9htGCsyZg4PXF1RU/vs4lEhnDFyI0eY4hlI3WLSSQW0NoCLKu7xNYXL17zl9qj7JoJ5wnru+edzWWRGkb89ipTyBg3nhFbSztzyg9+uuGKsjWGyZXI1WWt+RUvFjtDNJY1pB2quiBYfxh2qDGa8gA2H1CX3EBhwqdxzjVUzr1G7ZPNvHXv+6HzimtF7KhCg2pPPZJIoLaGSzEUVHFrbRcLX78STivDpJQ7LHlthp7haNZP3Xr2DYVygI9cBGUKW3MRlFshBWh1tKLGxW2jQ9YoyFxpyWV1tfi+u4WEmC6Q5aL+Q/zK65BU9fSt7H9UbyMcbG6ubvkgyEFWavFtlGaIk17drACt20t9yi2jd4LJ1tGiV+l2HnbOG5yj7lyKi7YA/rY9FN0g3S0fj9/Utr/X4oP5sHEucEhjbAOzSzYxuconLd/Y06CKhmnyZCKNYKsm475I7hESFPEhdwWKHJpxBaHQxAdK37R2h6V2QmPzgZF1isMGecxE+sw4KXjc1acFWnmxiLNtjLfoyk2FxWRC1ma7hRVzXae2zp9E8JlJiL5Uyqt4JMqFVe4QjGaRVbKlF4G8k1OjR8J8r7Qa3s6fwOz0sdB8V+oTRCvcTviVky2382mQl3P8kp6Ci+mfGaXkkdMa6lMOn54kc9rNH5BXYsIFPMv0Gnbcnu9ykQ0ge32zRa9QcIwf+AxRejr8LFcoT+onOfSRGtMc279Lo1GM1vOwmiWgFY5moA80aYB6GReoVjEOTXMZ8bK0vR4PM5lXI1oo2tIP9y+X/6+Ws4W86t5RbWOc9LZQLU0Z8CDUotJqr+aMd2/WvP2C8EoDISfKXVaKgP9mHk3StAaBgmCBDJV8B2ksoH4e9dtZcA/ve57/vypQZ7K600CB+mV3PKMX3dQqMD/i5PMP5v9xR/jjeFSvHSv+GbOk8IZlreD1A2/QQJ7bIdbTL/pz3T2Zvlheb+EBOQThdxHhRz/MIFvQj/WuiEO//bJMy5dN+hv35/sh6VnPUbtPLEwzKLvvwCSVJKU
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Delete Asset"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/assets/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to soft delete an asset.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the asset to delete","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Asset deleted successfully","content":{}},"204":{"description":"Asset already deleted","content":{}},"404":{"description":"Asset not found","content":{}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/disbursements.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/disbursements.tag.mdx
deleted file mode 100644
index badcdef409..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/disbursements.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: disbursements
-title: "Disbursements"
-description: "Disbursements"
-custom_edit_url: null
----
-
-
-
-Endpoints related to disbursements. A disbursement is a group of payments sent to multiple individuals at once. An SDP user with the appropriate role triggers a new disbursement through the SDP dashboard by uploading a list of receivers and amounts. When the receiver has linked their wallet to the SDP, the payment automatically begins. SDP users can track their disbursements in real-time through the SDP dashboard. Each disbursement must have a unique name defined by the organization.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.api.mdx
deleted file mode 100644
index 2cf119dab3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: download-disbursement-instructions
-title: "Download Disbursement Instructions"
-description: "Allows an SDP user to download the raw CSV file that was uploaded when creating the disbursement. This will only return results after instructions have been attached to a draft disbursement."
-sidebar_label: "Download Disbursement Instructions"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVV0tz2zYQ/isYnJIMJTqu2wNvTuy0bjupJ3Lag6PpLMmliAgEGGApRdXov3cWfJiSX3XTzDQXUUPu6/uw2MdWEiy8TK7lmfJp4zxWaMjLeSRz9JlTNSlrZCJPtbZrL8CI2dmlaDw6QVbkdm20hVxQicLBWrye/S4KpVFQCSTW4EVTswDmYl2iEZlDIGUWQSEfuZyKq1J5sVZaC2v0Rjikxhnh0DeavICC0AllPLkm45i8KGGFIkU0AoggKzHnkEDkDgraNy4jaWt0wIoXuUzkWRf4GPXFyLiMZA0OKiR0TM9WGqhQJlLlMpKKGamBSnlI08WZsEUAN7YsI+nwU6Mc5jIh12AkPW002/OqqjXKSOLnWtscZVKA9iyQlViBTLaSNnWQJKfMQu52c7bma2s8ev5+fHTEj/1Axu6HU5GRLBHyAGkrX1tDaGhypnxtvWoVD+1clRhUGX4PrT0azAe7zO8XAIqGUK7Cl8MYCD9TnPnVl3nZRTJr3YSvvc1kK/EzBGuJbMVO7iL0FeSCDxE9RUKZFWg1vBCjXNnz8iJ+wY9bQdn0I2acFrXjvCTVniQ6Z93t2A+T7AwJlPYCUttQOJFWccd0kAP/qKcAc4A9OJYXHS5l6obk2FyhUOd/FtbK5Oa/UF4MiR1171Nwg0wKThjE3PPNTJHLhzKEC3TMdEf2y9tkvzfQUGmd+isY/s8Z/edMSU9AzVjONFWKgewKvYcF3plsd/P71pLYQ3YTRe/n5OjlyPKhRmsZ6lqrLFSz+KNvr+3X8haO6LvbR/TGulTlOZqvcj5303fj8yk07GkFOCeP1Eum4Y1tzLeae0/MkaKDeld6nIzT4x1627gMhRm0ences8Yp2oRe+QrBoTttqJTJ9ZwbVoVUWm68CwwwuXcmMh43aR9vVb6L1X4X9uhWfQtunA41en7jbsZn0ZI1djqQArX6BTe3KujPf1zxDJOLwrqQ8GioIysSXi24ua0VlVywzmfH3/8gaqdWQCiWuOFu100Dp91dCZr9YNC22JDDyhQ2RKMo9JcZodbg9oYDcamBCusqcXp5ISPJcNsoj6cvp0fMQVNV4DZdN37YxrPZ2eVzrssgyFot0kZpCjCtW4DpQg31uIIlirTRS1HDJpxAOz8tnG1q7vUOM1Wr8MGueOAbeTdIa+uW01vU/v9C/GA+mDBcqjC/2hrNpMvj2lm+eO20qnwXijWCbN1POwfmIgGmnXczm6PIwHBjC5chKPK8ZHlY5inXYZisrFPoE45jIq59ay/unpPxHZjUHUmTFLIlmnz+rCSqfRLHC0Vlk04zW8VPsvA8aSfrIZSN4JIGihkuUXRiAZUyhYP2+jWuA8jnQo+d6fQJyAoXKuqXQOtNPIZtjanoZf81mhJ1NclKcOQfDHkkF5NDjCtQJu5ePIjnMRg/oa5EMBTiz7HWdtMvUQ/ftcaz3LJJ0Rkk9NMPXKYIXeV/K2boVirjutTD6sKcWreIg9DEFhPfiUVSqwyND/2jL4A1L17iONSptj6zrSSO1+v1FMLXYK1T9fGvF6/P387OJ8fTo2lJlQ51sraeKjAjw/2Cto/rYEXbqzzbm1b97W+rXfsKW0qtQRnu+YHfbdc8r+Ve85SRTLrddETRPJKl9cTS220KHt87vdvx608Ncke5nkdyBU5Byv3pestG+X8+LFT3cvzsXTf5Pxf3br13wuhbs+G+vALdhM0rkkvctAv2br7rF9UQU/vhNMuwppHKsMLtDRg/nl/JSMKtMWAZxoDuD1u9M4zDht665t9ddI/KdtsOGbvdIN9+ulejgzYgNox4t/sbFvwyRw==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Download Disbursement Instructions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}/instructions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows an SDP user to download the raw CSV file that was uploaded when creating the disbursement. This will only return results after instructions have been attached to a draft disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Disbursement CSV file","headers":{"Content-Disposition":{"description":"The filename of the returned CSV file.","style":"simple","explode":false,"schema":{"type":"string"}},"Content-Type":{"description":"text/csv","style":"simple","explode":false,"schema":{"type":"string"}}},"content":{"text/csv":{"example":""}}},"400":{"description":"Bad request, invalid request parameters","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Disbursement Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-disbursements.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-disbursements.api.mdx
deleted file mode 100644
index 7aa1fcfb9e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-disbursements.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: export-disbursements
-title: "Export Disbursements"
-description: "Exports a CSV file of disbursements."
-sidebar_label: "Export Disbursements"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWNty2zYQ/RUMnpIMJcpumge+qZHcpk0aT+S043E0GZBciohIgFks7aga/ntnQUqmfJEvcWbyYpHEYvecXWAvXktSCyejMzn9VlkkJ+eBTMElqCvS1shosyCUeD37R2S6AGEzkWoX1+igBENuKANpK0DFW96kMpLgN036QjKQlUJVAgGyxbU0qgQZya8ykJotfa0BV/Kq/bFwoDDJBQGWonaQCrLCywrK0daLXFAOO4gEq/awEL7WGiGVUaYKB4F0tCrYamaxlAEDLWwKMiKseTXJoVQyWktaVSzmCLVZyKYJtngdKardftDTbyohUSpKcmGNx9duY99dRfuEOAMJpi45npMP46MTGcgP0/HkVAZydjL+cDKdyEAejz/O/MPr9++O30754zyQpMnb68ds1jJt2Lwqq3bd6+25I0FQBOlnRZ9VRoD7HfPeFCuBQDWa3TMkKFckFILoFAqvTVCunUgVwVAcWSwVReL09PR08O7dYDJ5wgD3OR6ORq8Go4PB6PAWojFkFuHJmLbqfiKqziLtZ3ekoUi3t5Hld0k+5ZFOIVN1QTsh6J10jznor8371zXVCIlHvZfQZCMmMouekDaL62nuB5BSLumxad8YG9OYs0VXWePAsZbD0Yh/dqHfmpfZK9YQGPII4BuFiTvn59txZf7kyUjG2ihcyaZpmkC+HB1ct/vRqJpyi/o/SHdNvQhf3GjFxl8g4dhVyPWCdMsKEC3eclAJlbtbQ5eTL+VMXcaArKIE59QCbsrpTf8qbGHIvy2JHWaXKDZ2Xo4Oepqv7mg1q6oqdOJrYvjFscfWP8yaD9Ev10N0ZDHWaQrmh8TnZvdd2nyIG3Z28T4HSY2aVr5V+A0UAo5rymV0NudrUQLllluNBXjAipdk2DYeLrx6Dxzg+abvqLGQkZSsZWNkxp5oyfZNbRmrSv8F15PGn/+etDmQcwaHBAx1XAPh9MJAKi405UIZMZ0d/vpKVKjPFYFYworTSZejxl00VT9P5aBSPsINv2fWo+mK9IygKBSKfrEWx4Uivr1ifPxGBpLptigPhwfDEfugLku+0pE8yUHs1/FsNjl+LjS3fWRtIeJaF+RpWlwo00F1nPxLtQQR18VSVGrVVTgrlFigrSvOSQiJrrRfsOe+pF9aN0AXFpfDa679+SB+Mp/MCZdoNmmErcAMnK0xAVGh5YvTVnbtOijc+Nlq0/FdURcIZVK/kNgURKKMiEFktjbppmPMbFHYCy5DCJV1mixqcBHjGIgz1+oLu99B/8QPqs5Jg1glSzDp/FlOVLkoDBea8joeJrYMH6TheSQ8+S2UleCEojR7OAfRiXlW2mSoHGGdUI0dQY4L3RXT4QOYZejz2fdQ26i4i9sFxGIj+2g2ORTlIMkVktsLuScXEgKEpdIm7D7s5XMXjT+gKIVX5PGnUBV2xcfrTiaidiy3rGNAAwRu+InTFE9k7n02AzzXCeelDa0O5tDiIvRCA5sNXCcWyEInYJxP/5sEWKkkB3Ho81Sbn1lXFIYXFxdD5Ve9tm6rC9++eT39ezYdHA5Hw5zKwufJyjoqlekpbqdXcXUS3ck168vSeN9ptysLvqWqCqUNdxoe97orRWfdDOyt7VifBzK3jlhkvY6Vg49YNA1/bjtTLlGpdiouem3mrYC/bzy+kccSVt1Yfq6KGnytDB6C6cHT7x4Y22n7kViefODcg/WGUfjHo77n8Hg/2NvB9pG47zEW7ot1O3Y+0vY9J7g99vuj4iWIOb+gZhS++Qw2nRlf1HbjOEmg6kPfzlo7rervU/6PjLrWWi59a9k9sNbNkln1dF5tElvT/Jf9dOOW9bptXJtmK98u3bqjo7aRZu/Mm6b5H3hhCE8=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Disbursements"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of disbursements.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"q","in":"query","description":"A search term used to query through the disbursement names.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the disbursement.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return disbursements that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return disbursements that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort disbursements","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["name","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting disbursements.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"CSV file of disbursements","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.api.mdx
deleted file mode 100644
index c5e7012278..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-payments-csv.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: export-payments-csv
-title: "Export Payments"
-description: "Exports a CSV file of payments."
-sidebar_label: "Export Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWG1v2zYQ/isEP7WFZDle6m7+5sVOl61NgzrpEKRGQUkni7VEqkcqqWvovw9HyY7cOM7LEqBfYkl3vHueI3kvWXIrZoYPLvj4e6HRGj71eAwmQllYqRUfrARMsIPJJ5bIDJhOWCEWOShrOtzjugAUpH0U8wEHp3/SyA8mn7jHC4EiBwtIrpZciRz4gBsrbGm4xyX5+VYCLvhN7yKyLBc2SplWzKbA6mUEgt4aIIQD4VspEWI+SERmwOPGLjJylGjMuUfIMh0DH1gsSRqlkAs+WHK7KGo8KNXsBoTT23ySSVXmFL3Rx+HhKff4x/FwdM49fjI+Hh0dv6Wn4dlkPOIen5wdHIwnE+7xw+HRO/fpYHh8MKbHqcettA5rE7hJHZuKUIu8cKLaSeWtA4gQgbwE/CLj3VE8OzsaMZsKyxAKBEM7wwRbrWeyjmwsrAiFgaeL5Qb+sB/2+29E7PejqOfv96PE/yOEN/7r/l4sRARv4v3f2/QiBGEh/iLsF5FYwN0cP6hswRBsiWp9OmvOAoE1tpgzxGwqDbGFDjvUmAs7YOfn5+f++/f+aPRM7Hvdbt/v7vnd3i0cQ0g0wlOQrC39QiyNRrub2KGELGalgZhZzUh/I8U84dVORJnZjci37nHr47RqEYglQuSg7mQxWqmxRKNjIdXsuYkIE7UY1G8EixhMyaMptDJgyEqv26WfTdTb8jr3eKSVpSxHzuG7DSJzSc+3Q0rcIaOLLpXABa+qqvL4fnfvpsszJUqbapQ/IN509Sp4tdWLDr9CRFtVINUbK2tCgKjxljNpUZi7LTRV6FpPlXkISCZyMEbMYIt5x2x96tcw+LG2bIPZNYqVn/3uXsvyzytqy6IoMhm5mhp8NRSx5bN5c1v0280tOtQYyjgG9Sz7sz181z4fEoaNVbTOQFSitAvXbPwJAgGHpU354GJKNyIHm2pqVWbgAAsS8aBuXEzQugIG8HLVtJSY8QHnZGBlf0JBqHm2vazJikL+AzezxN//ntaZjpIE7QYo29D0mJEzBTG7kjZlQrHxpPe6zwqUl8ICm8OCkkiTlIbNRop2YkpBxHR6K3pPtEPTtBYTC1kmkI2kCUs0QCzZSSYsXVw2PDniHie6NcpeZ6/TpRiUeU63uW6Edtt4MRmdvGSSegurdcbCUmbW0dQ4E6qBaijF52IOLCyzeauOaSbYDHVZUCZCiGQhnUBfupp97V2BvdI472zt1X4tiJ/VZ3VKhZhcKqYLUL7RJUbACtR0Z+r6LU0DhbpcXaxazZ/MeUyo2AkiHQOLhGIhsESXKl61x4nOMn1FdQeh0EZajRLMgHD47MLU9oLm149bQfKLJkh+KKI5qHj6IrW2MIMgmEmblmEn0nnwIAsvB8yRX0NZMMolQlKEU2CNmmMlVYLCWCwjW2JDkPbF3rWnnQcwS9Clsv9DbWXiLm5XELKV7qPZpJDlfpQKtGYn5JZeYBEgyIVUQfNhJ5+7aPwFWc6cIYc/hiLTCzpedzJhpSG9eRkCKrBgOp8pTVnA3HxIJoCXMqK8tKLVwOxonAVOydeJbxo1j2cyAmVc5l8lwEJEKbCey1N1fiZbgyC4urrqCCd11pqlJnh3dDA+noz9XqfbSW2euTxZaGNzoVqG65mXnVxXgo00s7wuiPcYj5ti4HqoIhNSUWvh0C6b2nPRDM3GVaPG59TjqTaWpMslTWVnmFUVfa57T6pJsTQizFrd5A6Y95+jtwKew6I9sl+KrARXD72HwHj4ILoDzOb4+0hETzk27sC6ZZZ9VsD3HAHvh3g9mT4S8h3D3a7zVg+Oj/R79zi2w3V75Lv2P6UXlATAtZPequGi61gvHEYRFG3U6+lpo/l8O6Z/GIkbHePcdYzNA1ldidSiZfPn3q92TX8pRFuXLJd1P1pVa/1adOuKhtpKm6IzrarqPxK+AXI=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of payments.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"status","in":"query","description":"Exact match on the status of the payment.","required":false,"style":"form","explode":true,"schema":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"example":"DRAFT"},{"name":"receiver_id","in":"query","description":"UUID that represents a receiver in the database","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"b6b667ad-6cc2-46cf-9be7-561daace7d48"},{"name":"created_at_after","in":"query","description":"Only return payments that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return payments that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"CSV file of payments","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.api.mdx
deleted file mode 100644
index 1b4e75d75d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/export-receivers-csv.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: export-receivers-csv
-title: "Export Receivers"
-description: "Exports a CSV file of receivers."
-sidebar_label: "Export Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWNtu2zgQ/RWCT20hW0622we9eWsnm912W8RpiyA1CkoaWawlUiVHdr2G/n0xlGTLieNcNgH6ElnicOacGXIuWXMUM8uDKz7+WWiDlk89HoONjCxQasWDdoEJ9nbymSUyA6YTZiACuQBj+9zjugAjSPws5gEHt+G8FXg7+cw9XggjckAwZGzNlciBB/wH97gkIz9KMCt+3fSQWRAmShmCyVlpIWaomZNlmBpdzlKGKWzAsCLVCr6pMg/BeAxyITOPCRWzsxHhNPCjlAZiHiQis+Bxi6uMcCTa5Nwj5JmOgQdoSlqNUsgFD9YcVwWJWTRSzXhVeRsGFgWW9jCN8U8RIcsFRinTyiGut5Ejd/AvRZYBPiFUj4Mqc4rv6Hx4csE9fj4eji7d8/RscjE+H4+4x0/eDU9PxyMKPkp0djbx++IwTWqeFVkWeeFEapUdZ0QGBEL8TeA3kSCYw275oLIVM4ClUdvjxDAVyIQB1ihjThPDVFoWC4Q+O9EmFxiwy8vLy977973R6AlD2+V3PBi86Q2OeoPjW0iGkGgDT8KyVvUL0bTa4GFmJxKyeHMrSX5L8ClPcAyJKDPccX3nYHc+Trs3M5YGIgf1IItRK8YSbRwLqWa76e0ZmAgbdSjUb4SLKEzJoi20smBJy/FgQI9d2HtzMfd4pBWCQmcdfqIf2QX9vh1T4o4ZD3golTArXlVV5fHXg6ObNj8pUWKqjfwX4l1Tr/xXe63o8DtEFKzCUI1AWTMCY7S55VSiEfZuDU3a3crVOZ9U5GCtmMG+tF11z/0GBv9HI9thtkXR2nk9OOpovr6j1iyKIpORq4P+d0seWz+bNRei326G6ESbUMYxqGeJz373bW0+xA07u2ifhag0EleuP/gDhAEzLDHlwdWUrkQOmGpqL2bgAAta4n7dbFi/ewcsmEXbaJQm4wHnpKE1MCEv1ES7ZjZsRSH/hpuJ4q8vF3WyozxB4QCFDU+PWTlTELOlxJQJxcaT49/fsMLIhUBgc1hRGmny0rCJpOjmphRETMe3ovdEOzRNIZ4gZJkwbCRtWBoLOShkHzOBdHPZ8OMZ9zjRrVEe94/6A/JBmed0nQN+kQI7rOPFZPTxJZPU4qHWGQtLmaGjqc1MqAaqpSyfizmwsMzmrBAr0uK+CjYzuiyaXCQL6Rb0wtXtrXUFuNRm3r/h2l8P4lf1VV1QLSaTiukCVM/q0kTACqPp0tQlXNoGCvV1umgbumvq6h6UFiIdA4uEYiGwRJcqbhvCRGeZXtalp9BWojYSbEA4euzK1vr85tmLO07qFY2TeqGI5qDi6YsUsbCB788kpmXYj3TuP0jDy4A58hsoK0bJREjycAqsEXOspEqMsGjKCEvTEKS44F0x7T+AWWJcLvs/1FoVd3FbQsha2UezSSHLe1EqDNqDkDtyPhoAPxdS+c2Hg3zuovEnZDlzihz+GIpMr+h43cmElZbk5mUIRgGC7X+lNEUjmP2QTMAsZER5qaXVwOxrM/OdUE8nPduIeTyTESjrUn+bAAsRpcCOXZ6q8zPpCnx/uVz2hVt12pqt1n939nb8z2TcO+4P+inmmcuThbaYC9VRXE+q7LxTCnbyzHpbEu8z1TblwLVRRSakou7C4V035eeqmXXrdre1OvV4qi3S8nodCgufTFZV9LnuQKksxdKKMOu0lLcCfeoZeC+rOayaaXwhshJcxfQegvIxI+4BJJup+pFwnnS0PIBzz8D7vIjvOSbeD/JmfH0k5jsGwEPxrYfLR9q9x8h2wHZ3LtwCmNKLkYTAdZxe25LRba03DqMIii7szYC105+ejunfLOJGTzl3PWXzg7S2S2rV0Xm9O6xN01/y0d4t63XdsVbVRr5eunVHQ62VJu9Mq6r6D9uw+Rc=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Export Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/exports/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Exports a CSV file of receivers.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"q","in":"query","description":"A search term used to query through the receiver phone_number, email, and ID.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the receiver wallet.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return receivers that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return receivers that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort receivers","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting receivers.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"CSV file of receivers","content":{"text/csv":{"schema":{"type":"string","format":"binary"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/forgot-password.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/forgot-password.api.mdx
deleted file mode 100644
index 0b4045a635..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/forgot-password.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: forgot-password
-title: "Forgot Password"
-description: "Sends an email with a token to an SDP user who has gone through the Forgot Password process."
-sidebar_label: "Forgot Password"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVk1v4zYQ/SsET7sLyUqDtgfd8lVs+rXG2kUPTrAYSWOJtURyh6M4XsP/vRhKTlyniLEtClQXSeTwcd4M5w23mqEOOl/oi54btGxKYOOsvk90haEk4+Nvrmdoq6DAKuzAtGptuFGg2K3QKnYyMbueqj4gqXXjVANB1c6i4oZcXzeKG1Q/OKodqymEsHZUKU+uxBAmOtHOI8Wdbyud62U03NvpRBN+7jHwpas2Ot8euTbC+j3saKwqYNCJLp1ltCzr3mXv5BXKBjuQLzE1hJVEIBIT4rzxqHPtij+wZJ1oT+IdGwyyZDDLt3uzwGRsrY/jdRPD5JaRuIRFJ0KrA9b5iLETXiV4Lhv4FCN5GnYeA750pAivLqbzq/cX6gFaUw1p28mTHNBi6jEOBO9sGBicn52dDuKQ5oCWVehLSdOyb9vNV8SzwxCgxtMR3Ru+IC9U2HArQ78MRh9HInog+u3fUbmESn0czsAJd09kmsjR6ZRcI4Npg4LC9RzTPSzcJRofmSCc3ClSwUfofIsHG+tbG1OrjPW9LHqGWxpsq09L56RY9t/KBPWUgGQcL4CebAogZRGrIBVboBStsYw10nBwxI3HtHQV1mjTsYzSwlWb1EIn/sv34AjaYJwV6djqFW50/urKRD9A2z8h7O4T3SE3Tordu5gnD9zoXGdD7af+ufgD0gPSsFVPrc51BAhY9mR4M5N0Dhm7RCAkkbKDmIM3P+HmRdp+/H0udVnFYoK/qF+igqktVqPKWXUzO//ue+XJPACjWuFGJGsMiezmyHwZCjDRRsAbhCpGVf6XLnozHuQZY9sCqWsTip4CdlJi0xZY1EFdTG8lWEhh8PJ88s3kTGLQdx2QhHneoHod483sevpWDoPos2tV0ZuWI01HNdjR1XgIOlihKvp2pTxsBCWOgqrJ9V7Ui7A03sQJ94AUj/d+d4u8drSavBSp/52Ld/bOzhsT4pZWOY82Da6nEqUJSU0qboBlenDFSVfze/0+gksU2CpOyIlXJVippqXrbRUXNvLTtm5tbK0IvQuGHRkMufiRqkUY8LLxnVYHQUr9GKS0gHKFtrp/0zD7kGdZbbjpi0npuuyrEN7mKpJ/cmWjRBXBSIQbVKNZZGXskiAw9SX3NBKUvPCpnE6+gtmSoij/G2p7iFPc1liove0/ZtNg26VlA8ThVZcP7DImxKwDY7Nx4FU+p2i8x7ZTESj6X6Fv3UaO10kmqg9it+oLJIuMYXInMsVIXfiwnCE9mFJ0aU9rdHPiqM6iUeqWaRjNEt2aEqX/5tsnAfRQNqjOo04N+ixYeZat1+sJxNmINi4N2c+3Vze/zm7S88nZpOGujTopbaADewB8dF08lpntc2v/r2+nYydhfOTMt2CsNPdIdTv2rYU+7lv3iW6ks+ULvd0WEPA3anc7Gf7coyj54l66IhkopC8s7nfJvm0899SrgWE6Fweem6hcZHbJ3uiiLNHz8fRhi51+mM11MvReuXC5SswI1nK1hnXsqLvdnySKRJ4=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Forgot Password"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/forgot-password"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Sends an email with a token to an SDP user who has gone through the Forgot Password process.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Forgot password request data","content":{"*/*":{"schema":{"required":["email"],"type":"object","properties":{"email":{"type":"string","description":"Email of the user","format":"email"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Forgot password email sent successfully","content":{"*/*":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"}}}},"400":{"description":"Bad Request","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-assets.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-assets.api.mdx
deleted file mode 100644
index 665d6023af..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-assets.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-assets
-title: "Get All Assets"
-description: "Fetches the list of available assets to populate the dropdown box in the New Disbursement flow. Note: the organization must hold a balance in a particular asset to use it in a disbursement."
-sidebar_label: "Get All Assets"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVV11z2jgU/SsaPW1nbOzwkez4jZYkzTabpgtpZpsyO7J9wSqypJWuoZThv+9INgQS2vRjO7PLA9jS1dE5V9I9YkWRTS1N7uhrM2WSf2LIlaTjgOZgM8O1f03oGWBWgCVYABHcIlETwuaMC5YKIMxaQEtQEa10JRiCD8yN0rlaSJKqj4RL33YFCzLgNq2MhRIkkolQixa5UgiJD1A7PEhZWSSFEjlhJGWCyQwcECOaGeRZJZipJ3dzVxYIx7o/35miRQOqNBgPeZHThJ4D9oXoe9Y0oAasVtKCpcmKtuPY/ezL79+L3gzKlESQ6GKZ1oJnHj76YN2AFbVZASVzT7jUQBPKjGFLGlCOUNqddpV+gAxpQLVxJJHXNHi+E2PRcDmlAYWPrNTCNU0mDLJu2gm7x2kcdvO0G7Ju1g2Ps04v/jXunZzEPbp2NHM4hPRAn8+hj92d5GY4eOFAuLUVmK+FqaMJy3MD1u4Bnj9/PuieXJwdX96+Ork++X1w+nb44vaPk8H1ze3bztWfncHozenbs8vuVX/U7b952Xl3eXl22a+VGGAI+V8MDxGZKFO6HpozhBB5ua+kHbc7YdwO487oKE66vaR39M6BVjr/90FzEPCDoMcNaK8BXT9M9agAMkQQ9ydgu5GQo0fyq0HX7hPQbnz0eFvfSFZhoQz/BPl3bOnPbF0wRh3YLGunEg37is1vkWG1GyerMgXjIEqwlk0PbOla5jaPWxr0SiHZk3nPYjNPNz7aQX444mcC10vTebw0Z8qkPM9B/vx1OazunsBXBHgdFrLKcFzS5G5FnwMzYPoVFjS5G6/HLg1YKFd9p+C5MddFo21BtWDmYKwfXRlBE0rdsA3q0Kmshexi39dXzV/B8lFJ+u125IwhJxNlfO5BYpPAgFg+lZCTBceCMElOh+3eMdGGz52DzWDpnEOy0h+mZtlqfwwod+AFsNxtS1ci5UR5Ns3h25zNPa+7Fgzd8Sf96wsaUCe3ZtluHbVil4OqLJlZPjjfhzF+GQ6unxFuCSOolCBpxQV6mbsW6l25ZDMgaSVmRLOlQ/GtjEyNqrRzNQMZ19x3qDkYb8Sb2SXgQplZ61Fq/3sU38v3clRw66eURGmQoVWVyYBoo9yhIFgw51ANFSUJKg9/AC4gTOa+wxkjyZgkKZCJqmTuBxbuRQi14HJKDGhlOSrDwSaOR0jubI0XNb/h7qUk1E2SwpRlM5D5+JcCUdskiqYciyptZaqMvgnhWUK8+C2VJXGVg3FZ39uaMK+Ky4lhFk2VYWUagW5d8Kk1bX2DsonxhetHpG0gntK2gJRsYr9bTQGiDLOCGbRfpLwTF6EBiErGZdQ0fFHPUzJegiiJB/L8c9BCLd32elIJqayLm1UpGAkItvXelSkEU9rXkyGYOc9cXdrIami2lJlGPihUk9A2YQEVPANpfb3fFEDNsgJI29epuj47rCSKFotFi/lej9YMtdHlxYvTq+Fp2G7FrQJL4eukVhZLJneAzwFJXwiyvY7vVZnVvfv97/+ENE6F8BEjLRiX/gbqUrlq7PCONnY4DmihLLqW1SplFm6MWK9d898VOIO4Gwd0zgx30r3DBhs3cv45A+ch/SwD7bx2zkRVe+SD28OeL5+fjmhA2SNbnXlbbR4c+qZLLnewHxpkTcF9r4PPDFmtatNer7fxdddnRzQSN9Eug+P1ev0PXdMlYQ==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Assets"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/assets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the list of available assets to populate the dropdown box in the New Disbursement flow. Note: the organization must hold a balance in a particular asset to use it in a disbursement.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of assets","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-roles.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-roles.api.mdx
deleted file mode 100644
index a2e14c816f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-roles.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-roles
-title: "Get All Roles"
-description: "Fetches available SDP roles, such as owner, financial controller, business user, and developer."
-sidebar_label: "Get All Roles"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVsFy2zYQ/ZWdPSUzlOi4aQ+8uY2TpukknsieHhRNByRXIiIQYBdLKapG/95ZiLLl2ImbNun0IorYxcN7C2IftihmEbGY4lUkjjjLsKZYse3EBo8FPiepGopgVsY6UzqCybML4OAoZhD7qgETIaw9cQZz642vrHFQBS8cnNPRso/WU4zQR301voaaVuRCRzzGDPVpdLWXNRb4guTMubeKjxkyxS74SBGLLZ6enOjjNr83rzBDXY68aNR0nbNVwsvfR03ZYqwaao3+k01HWGAo31MlmGHHurrY/QJJ1VGaYTYbzNAKtcfjUdj6Be52uwzpg2k7R0fTp3gtDzO8rsnvNzXBDA9FUf1aPJx9ZTCFe3ry5G7BrrzppQls/6T665WOmAPfUyLVJGziwwhRjPTHeb5vS2KFaClGs6B7d+B21QYa+DoI3JJ5w+KwztOTJ0fIH8/4lsD7rfnu7tY8D1zauib/7fflfnU3BP5GQtIRqerZygaL6RZ/JMPEZ700WExnu5mWQZqgx3pBiZvREObaCWLOwyGPxCvtPQrRs8MCUeceoCcqda/meIGbU9rZV6TH9HYxf/ntUjtODfPAaQPIy1DFDKJdeKphbaUB4+F8cvr9D9CxXRkhWNJG+5I3rcKfDXuXZmozUPCGTK3f5k7f5yGxsaK1womQc4bhmY1lz5Fa8gIXzsg8cAtnFy8xQ5W7Z3k6fjI+0Rr0bWt4gwVeNgSfx3g0eXbxGGwEAxKCg7K3TpLMwAvjB6oRJEBrlgRl75bQmY2ipFEDCw59B2EOTJXtbAqEFTHI0eqeZB14Ob5T2v8fxXf+nb9sbExLeggd+VEMPVcEHQc9GSCNEQ3vqQQPEhL8PXB7k9JAFWqCyngoCeah93Wa2OiLc2Ft/QKYuhCtBLYUC+Uxgmnc4+XDc1QfFWnUDUUalaZakq9njxqRLhZ5vrDS9OW4Cm3+RQiPC0jir6lskgEbqxVuCIa0pMr6OZso3FfS8yBQ90Ue2tPxFyibc+pe/0baAeIhbWsq4ZD7j9U05NpR1RiW+FnKR3m5MFHeGuvzYeCzeh6S8TO5FhJQ4l9T58JGP68HlYCa/wKWfUnsSSiO32mbEuI2vplPiFe20r50kDXQHAde5ClpFOajOKRl6GxFPqamf2iAnakagtPUp/b9WbGKPF+v12OTogltmBrzX1/+dP56cj46HZ+MG2ld6pNdiNIafwT8ggTOnIPDZe9Wk9neOOB/cAcdrETog+SdM9brtSNp3Q6mNcVkWnonTXRnGTYhiga229JEumK32+nwHz1pI5/OMlwZtso32WF2cA31uSVprz+rKurUGFfG9Xsv+8jqb5noi/NLzNDcsb9lsr/hj6IfQn5zhP2xke0p6O8u+8SU7XZvrrvddf4+9MkZg8RDthZSL6N/AR1/ZDM=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Roles"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/users/roles"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches available SDP roles, such as owner, financial controller, business user, and developer.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"roles":{"type":"array","items":{"type":"string"}}},"example":{"roles":["developer","financial_controller","business","owner"]}},"example":{"roles":["developer","financial_controller","business","owner"]}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.api.mdx
deleted file mode 100644
index 14f3d5f511..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-tenants.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-tenants
-title: "Get All Tenants"
-description: "Get All Tenants"
-sidebar_label: "Get All Tenants"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV21z2rgW/isazZ257VzbvCZ0+UaATaEJUN7abZplZfsYa2NLXuk4LJvhv9+RbQIEkrTde2f2E4l89JwXHT3P0QNFttS0eUNbfswFvbWoTEAx5FL0fNqkl4CtKJqCYAI1tagCnUihQdPmA62Wy+bHB+0pnpg9tElbJOIaiQxIouQ911wK8AnmCGTFMSQYAlfEkyLgyzR3ZrA9KRAEGkiWJBH3si+l37XBfaDaCyFm5i9cJ0CblCnF1tSiHCHWe+vS/R08pBZNlEkGeR4t9/dsNCoultSi8CeLk8gsVRq1cxf8mt1wf6ra9cZ52X4XBFX7rBK45XcA5cZPAd1YVLAYTiEdlmEaQpE0MRsc0kOiQ5lGPokZelkRSMIQQQny2683zP7Lvv3Pv35zDmJyoxQ8qRLj12UaFqmKvs33pDMiLvPuQPhEg7oH9W9NDASZja8OnYSIiW6WSltndrHP0X7iSLU0zrWfLFK++P4YZr2Sz3ToSqZ8cvFN/g/8IsNUnzw4kcamcafdQWswXbTH3da026HWdmE0Hs57k95wsL/Yak9780O7Tne3eLuxqM+NCzc1eSyY58lU4IL5vgJ9Mo4TaSNEEVOk2EyKzSTV4JNAKrJzIZYkSIWvDwty2f7c6tc+92vzD7X+z+9rH687Pw8nH66rg+vrLxeTYW3em553Z6OPnyadT9V+o35drY3Hkyv6XPh5zD8Su9nxauDFSXR6k+m4dzGb9oaDRavdHs4GU2cy7V5dtcZOdzCn1ssmnYvFvDW7mj5n1+6N21fdndmzp/V80xwnnNsaujIXch/usQbfmH7WRl1q0VF30OkNLhezSXe87bjecJDFy/XCh4ClEe6F50oZARNH8V3k6ySI2JJgyDIGWWmyCgFDUFnEBcdwncefYxOpiJDoZIiFt4BFGjYW9RQwBH/B8FSBAqli84X6DMFGHsNBZ1bL1bpdrtnVxrTSaFYrzbPKF9N1aeL/70F9iOB50BN0y2PQyOLEFEjsV2fFNHmjZYBvSQHq/GhYG6OBf6RcgW8O/ZEQDwr7Cou83LYv3WHLqNhBFxV6dMzQj9x5cDq3exnmkkjf1cu+x+pntl/xA7te93z7Xc2r2OdnXrlerZ151bNg66ZJFfiZIO3r0SODFx+PBOSEfjzds29bXN/TTH6qOBlnfpx3rkfD7qD2/n2/f16f16sfZtPhYPh50Gifz6ujyXzUuurO+41R75fhxfl1rdOfNwaH1WyiSuHwjpzqA6dcLn85LOwLdhuLIsesp/JB6nhF083GtFa9XDmeqGaCpRhKxf8C/wfGpGfGIVBKquOLtTENgop9w0B1RLMijV1QBiIGrdnyhObkae61YBEGHUgkB2nuotj6qZcre8hPd/w/gTNsDV6qOK5p8+aBXjDNvVaKIW3e3G5un9LRJSBpRRHZDc4xYCjNdVtCVklmttISPhrkQ5rO0PMbQg3u1uvEHGte9wtgClTufDcMJ/wDrI94sf9putMvkxQILDrGIpovzWyezeRMkO6kenZOEsXvGQK5g7Wzu/atoh7ZTnNnDHgIzDfnbXRNBDKLpmjr7RzR4dpNlYYYBJJRxNCQLmmNetSiJt08yqpTccqmBmkcM7V+Moucxngz6YzeGt1jBKWMiJvyCLM0pVoyUYSqCUoSszsgbhrdkYStDUq2yshSyTQx0q/A4wnPPsj7Qli33gXgSqo758Vx6Z8R4lfxVUxDrjOXgsgEhK1lqjwwbzFzh/MpgusiFCkIymQ7/DyBswgTfvbBkz4QjwniAglkKvxsY2j+iSK5MtOQgkRqjlJx0E0Th01udI5XKn5tf69IdlIUaasVt2+2grDkGKau48m49F0Ib5skS/4xlLV5YiLjIp+Ntq8hkxUXgWIaVephqooEzbnga2fqfEdmgcqY+u+ktoV4LbcVuGRr+8PZhBDFthcyhfrFkPfsSqgASjHjolQsvJjPa2m8hygmGVA+b0MSybVpr1czIak2dnepC0oAgna+GppCULEeBhNQ99zbf2sWYZqJo5QZ2TKwdWFm0Yh7IHSmI1sCTJgXAqlmPLWbYJql0mq1clj2NUMrturSVa/dHUy6dtUpOyHGUcaTidQYM7EHfCwVBzTzSPAIf2IpiRgX2cCdv8FzGbmhWxm5tWgoNZqlhwczbM1UtNmY5T9SMMR6c2vRe6Y4cw1N35gnScHiRnfuwHBvy/MgMSJ1z6I015YnY4YRpkdBu+xO6WbzX3zwSBU=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Tenants"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/tenants"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Get All Tenants
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of provisioned tenants with their configurations","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"},"title":"Tenants"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-users.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-users.api.mdx
deleted file mode 100644
index 8a81b8775c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-users.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-users
-title: "Get All Users"
-description: "Fetches all SDP users within the organization, whether they are active yet or not."
-sidebar_label: "Get All Users"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV99v2zYQ/lcIPrWA5F+x48RPy5a06zZ0wZJiD2lQnKSTxZoiVfJk1zX0vw9HyY6dpMnaocBeJFs8fvy+O/I+aSMJ5l7ObuQ7j87L20hm6FOnKlLWyJl8hZQW6AVoLa7OL0XNYWKlqFBGUIHCujkY9QU4PhKrAqlAxyNrAQ4FpKSWKNZIwjphLPVkJG2FLkx4k8mZfI10pnW7fiQd+soaj17ONnI0GPDtkNJfSLUzXoCoYK4MEGZCK0/C5oJRxDkSKM1gqTWEhhgDqkqrNKza/+gZaCN9WmAJ/IvWFcqZBOdgLSOpCMtAwOGnWjnMOENYgtIykrlynj4YKJEjM774D61OGUkNd4POagw57eBt8hFTkpGsHKeAVKtSZXsUPDll5jKS+BnKSvOj4fToOMHsKJ4mp6N4PD0exCd5PoonwzwZnCAOpqe5bA6IPYn3my0Mx99RfTL83CJHt/IfRDZbmU9k8d6MZj9jd8OJtRrBhPHd6jdteuQUxunxZDKJh/n0KB6fJkcxjIbDOD+dJNkoOcH0dHBYm07ngcygZSelvf8Urr3UlruKzW5khkvUXCQu3x5bcjU2UUdqko+zfJhlcXoyzuPxyQjikzFk8WQ8zPNsfIzTCTwgBQa/l1SuDJhUgf7AG9tZrR/wy0F7bHjLKQrV4xPBRdr/72XTcJbHg+HD4/XOQE2FdeoLZt9xhL6yx9E56x7dPfiZHPjnETwB1ftxpi6TVluJ3sP8kW3cytxtph0N+daSOJB5x2K7zngw3EO+P+NHArelOXpYmlfWJSrL0Pz4ujyu7o7AvwgIOjymtVO0Dif5ZwSH7qymQs5ubnmXlkiF5aM0x8ANeEj2684MPLol/+LJtePTIXnWFvSKRbY69qHvGlGlfkfuRIdp/O3va/axTOTWhdSjoS5/kfBqbjALDifAiIur0eRYVE4tgVAscM3+1Z3bs65qYSb3OwYvEDLeldzkTG4Dm+7oXRFqDU6cK5/UzmOJhsSlBsqtK8XZ5RsZSZbbshz1hj1uab4uS3BrOZPXBYqnMV5cnV++FIq9kazVIqmVpiBz36a9ICtKWKBIar0QFawZJTwFMXe2rthKHaaqUmHALltL361ukFbWLXoPUvv/o/jevDfXhfJhSSNshSb2tnYpispZPhOCCiAebqlYI8gG+EfgIgEmCwOpzVCkYESCIre1ycLEgv9obVfKzIXDynpF1in0M+YRixvf4vW7e5ztJSmuuiTFCaQLNNnti4Ko8rN+f66oqBP2g/43IbyciSB+R2UtuHGA4gwXKLqwoEqZ3IEnV6dUu04g14Weq2nvG5TlLvSt/yJtC/GcthUmYhv73WoK1GWcFuDIP0l5L65PDrFfgjL97sGTep6T8SvqUgSgwD/DSts1b69nlYjac9yiTtAZJPS999ymCF3p/8yv0C1Vyn1pK6uj2bNu3g9Bsc1j34VFUqsUjQ/tftsAK0gLFKPQp9r+zFizfn+1WvUgjAa0bqrv//Hml4u3VxfxqDfoFVTq0Ccr66kEswf8GkmcaS22HwUHTWZz530/5vOkcw/Cz9SvNKjwshzkbTqHupH19nOpsJ74wWaTgMd3TjcNP/5UI/fsm9tILsEpSMLL7G0TbQ2CLW2B3NbP0hQrdr8l6Lq1rXt+fuCUry+uZSThgdMtgtN1Pxh9O2TWe9j3PaulwFd+q310ymbT+mjT7OLboa/O6CRuozmBt03T/AOX6wb/
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Users"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/users"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all SDP users within the organization, whether they are active yet or not.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns a paginated list of User Details","content":{"application/json":{"schema":{"type":"array","items":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"},"title":"Users"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.api.mdx
deleted file mode 100644
index a5fbf25f29..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-all-wallets.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-all-wallets
-title: "Get All Wallets"
-description: "Fetches the list of available wallet providers to populate the dropdown box in the New Disbursement flow. The organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement. The initial list reflects all SDP-compatible wallets."
-sidebar_label: "Get All Wallets"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV99v2zYQ/lcIPrWAZDtufnR689a06za0AZKuwNIgOElnizVFcuTJrmvofx+OkmMnTpO2Q4E9LA+xTd59/L4jdR+1lgSzILNL+R60RgryKpElhsIrR8oamcmXSEWFQVCFQqtAwk4FLEBpyDWKZUwTztuFKtEHQVY46xoNhDGl9NaVdmlEbj8JZeLYG1yKFyrkjQ9YoyEx1XY5EBcVCutnYNRn4MVFqGyjS1FY60tlGHGpqIoQd9YVOU6tRxFQY0HKzAQIB55U0Wjwe9FT6wWIcodCt7oyihToTqfHKYMFAVqL8xdnaWFrB6S2ssNAJtI69JHu61Jm8hXSROtNMRPpMThrAgaZreV4NOKP2/Wd3FR1eZNVWENoiIPBOa2KuMDwY+CMtQxFhTXwN1o5lJkE72ElE6kI67AzbvOPWJBMpPNMk1THQ5U7MYG8MjOZSPwEtdM8dAQl/ITlUXp4dATp4cnzcQojxPTgeHRyfIKjEvMD2SbSQI0PI/2pcg+GxCQEFYhzKlujg9kjeRWRC9lwuOjywblBYWvOD+iuD0bXhVZo6Lq0NSjzMBY4lZa4GOxjlYjuWiszv96r6FdzGobSMTzjFR6BsLwGug9pan3NM7IEwpRUjbfgx6Pxs3R0kj47uBiPsqNRdng0OD58/hcDN678EcBtIklRDOpOrGz5L5GHo4P9g/rOQEOV9eozlt9xRr9wFtF76/dVtayAPHzFaQ4E1OzGmabO0TNEjSHce9Y6mTc1uqEh31gSt2RuWWzWORwd7CDfzfiRwN3WPNvfmpfW56os0fz4fblf3ZbAVwREHQGLxitayexyLX9G8OgnDVUyu7xqr7gMVFluqDOM3ICn5HDbIgP6BfoQ0xuvZSYl521gz1lmp2QXfNsxnfoduWXeLuRv7y9EE7DsHKKhCg31FUxEUDODZedBYMTp+fjoWDivFuxMc1yxG3QtUU76fYuZ3JgZvEIo+Vy2/HtqI5v+8Tsn1GxUt1zxTAPxsy0mZ69lIllux3I8OBiMuAZNXYNfyUyyeT2M8eT8xdlToYIAQdZqkTdKU5S5a7nRv2uYo8gbPRcOVowSR0HMvG0cG5XHQjkVJ+wCfTTkzeoGaWn9fLBX2v8exQ/mg7moVIhLGmEdmjTYxhfINwV+KgRVQDzdUbFGkI3w98AlAkwZJwpboijAiBzF1DamjIkV/9DaLvl24tHZoMh6hSFjHqm4DB3esP9Md68nqeuLlOZQzNGUV082djRTVDV5Z0XfgvA0E1H8DZWV4NYBynR3vT4sqlJm6iGQbwpqfC+Q94Ue29PBNyib+ti5/o20DcRj2paYi03sd6upUNdpUYGn8CDlnbghecQhX1mG/cCDeh6T8SvqWkSgyL9Ep+2Kj9ejSkQTOG7e5OgNEobBB25ThL4Ob6fn6Beq2L3z9DQH1s+GMSi10zT0YYnUqkATYsPfNEAHRYViHPtU158ZKxsOl8vlAOJsROtTw/CP17+cvjk/TceD0aCiWsc+6WygGswO8CskMdFabK/Yt9rMeut//7+5PPLm0lsh4ScaOs336Lbfq3VvuJdyuX0trGwgHlqvcwj4zuu25eG/G2QLurxK5AK84tpGE082fscOPUd2qUlRoGM7X4BuOhe+c0G5Zf2vTi9kImHPuOfRuPsvjL6ZMqsd7LsW3FHg/23yhZT1ursWtO1NfDf1xYxe4iaaS3jVtu0/QGNoHg==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get All Wallets"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/wallets"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the list of available wallet providers to populate the dropdown box in the New Disbursement flow. The organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement. The initial list reflects all SDP-compatible wallets.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of wallets","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-api-key.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-api-key.api.mdx
deleted file mode 100644
index e57bc2e521..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-api-key.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: get-api-key
-title: "Get API Key Details"
-description: "Retrieves a specific API key by its ID. Returns the API key details including permissions and restrictions, but does not include the actual key value for security reasons."
-sidebar_label: "Get API Key Details"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWFFv2zYQ/isEn9pCttKs24PesiZrsxZdkKToQxoElHi22EikyjvG8Qz99+EoKVFsN2m6BVifbIu87+47nu8+aiVJzVFmZ3Lv6FC8gyXK80RqwMKbhoyzMpPHQN7AFaBQAhsozMwUgrdfwlLkS2EIxeH+VBwDBW9RUAk3yxpImQqFsUUVtLFz0YCvDaJxFoWyWnhA8qZgX5iIPJDQDlBYR70RREBVUFBVxLxSVQAxc14gFMEbWgoPCp3FqUyka8ArRjvUMpNvgPaODt/BUiayUV7VQOCZ70paVYPMpNEykYZ5NopKuU7+tAQRrPkaQBgNlszMgBduNmYpE+nhazAetMzIB0gkFiXUSmYrScuG3TBJO5dte86bsXEWAXl9d2eHP+56HdLn+9RrgaEoAHEWqor9Fc4SWGJL1TSVKSLl9Auy+WrTvcu/QEGcBM8JItM5N3ozxPUMfNxgz6kf02+TPpkPQb0NtbITD0qrvALBRtvARiUywlTeK6ZuCGrcktl1Z+8NEh/UuODmXlkCLcgJKg2OnaqqcgvQF6b5L5z2aOLwSCitPSACCufF68P9Y+GVnQOyMVw3xi8vtKKt2Zs5XyuSmeQNEzI1bKT0gBHi4QvetF6ZbSILD4pAXyj6QRefSrB3/tQLhaJHHTvIl99RTAheLEo32K8HGxr9BMFWCkn00GMvj4p4DLIeNq9dBHyiwJGjbhNJhirougN3tLblh692Xm72j49WBSqdN3+DvtstXqQvHtMgwHvnt9Y9XJNX+DACkqIw3mdDnYNniBoQ1XxL5XfM4FrVTQWjMOQHR+IOs9soBj+vdl6OkNctOuRtLfOpvMUj+mXziP5wPjdag32S89mevlufj0nDHatI59W3JxbP7ZkL9mctu0eWx0B1W2W8GlfGMaALvoBRggZ3g4qJquR3UB78XqBSZmfnrBZqoNKxlplDpMkqJZOpaszkEpaYroxuJaP4q0HaBF/JTEq2HsBPOPNdasYubgddYzqVdPdY//x0GvtPHNNc2SwCutQkAs3cghYLQ6VQVhyc7P76m2i8ueJBdAlLlmO9ytrr/xTRchBcJSjNR9Ly75mL0fQt7oSgqpQX+wbz4BFqsCSOKkXcSblFykQy3S7K3enL6Q7nINS18stett2P8exk/+i5MCxqyblK5MFUFGk6P1e2DxVZKtTqEkQeqkvRqCWjxKdKzL0LDU9cD4VpTFxwV9DpmcG7BVo4fzndqiz/XyF+tp/tKcsidmmFa8BO+qptvOO/maBSES93oTgryDWD5liDS6K854XCaRCFsiKHrvSjYck/WCbxrcBD49CQ8wYw4zgm4gw7vLT/nOhRkiZNn6RJropLsPr8WUnUYJamc0NlyKeFq9NHITzPRCR/E8pScANTpr/S9NsiK2NnXiH5UFDwPcFByN57ptNHMJv52D//DbUB4iFuC8jFsPeH2ZRQ1ZOiVJ7w3pBH+1LyAGmtjE37B/fyeYjGW6hqEYFi/Bqayi25vB5kIgLyvsuQg7dAgNPP3KYIfI1/zU7AX5mC+9JAqw9z6vw8jZsmbjbBflsiK1OAxTgthgbYqKIEsRv7VNefGStL08ViMVVxNaL1ppi+P3x98OHkYLI73ZmWVFexTzYOqVZ2BPwGSPR3d7Hf3bbXW83qdhL/ZJf5fjgRXFPaVMrYqN45e6t+EJ7JYRDKRGZG8+uL0iHxymqVK4SPvmpbfvw1AM+Gs/NEXilv+Aoap6U2yN+1zGaqQrgnec+O+2v+c/Gd7wW2EhhGruUdMQE8rRPJJvGFRHveJsN05Ai7hb2igIZGJhs65Y5ceHNwKhOpNsZ8F1j/hdG3hrM+sLsQuuvON0xWq05EtO3N/m7pmxY9xRvmzKBt238AeweBYw==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get API Key Details"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves a specific API key by its ID. Returns the API key details including permissions and restrictions, but does not include the actual key value for security reasons.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"The unique identifier of the API key","required":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"API key retrieved successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"API key not found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.api.mdx
deleted file mode 100644
index c909d70015..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-bridge-integration.api.mdx
+++ /dev/null
@@ -1,68 +0,0 @@
----
-id: get-bridge-integration
-title: "Get Bridge Integration Status"
-description: "Retrieves the current Bridge integration status and information for the organization."
-sidebar_label: "Get Bridge Integration Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWm1z2zYS/isYfGo7tCQrTpPq0zmWnThJLdeyL5dzPBqIXEmoSIAFQCmqR//9ZkGQBKk3u2lmrp1ME5HAvmP32SUeaQQ6VDw1XAraozdgFIcFaGJmQMJMKRCGvFE8mgLhwsBUMVxKtGEm04SJiHAxkSrJH0+ksjulmjLB/7QPW1/EDZhMCU1ivgASMcPIRMnErnS0T68vCRdhnEVcTMmHz2c+hwVXJmMxYWEoM2FIBIbxWLe+CBpQmUIu02VEe3QKJqd4WQlLA6ohzBQ3K9q7f6RvgClQp5mZ0d79w/ohoAp0KoUGTXuPtNvp4F91w+w2gXImi4jOwhC0nmRxvKIBDaUwIAzSYmka89Bua/+ukeAj1eEMEob/MqsUaI/K8e8QGho0OJ/JJI3BwDYv+KavrOdZTkHMDETW5jSgqUJrGZ4rmq/zJNBGcTHdlMCFgaMrJ77jeM3OILKE9u7p1eB2dH51+ubjeZ8G9tfg+va8P7q8ogH1/nlzftr/PLoY3Iz659eD4eUtDej5zc3ghj4EFL4yVJ32/B2GG/tow8vDXJt1QMNMG5mAGvHosHJOjWIPuUSBK874fHTcfcHGIZKer8LRhtl2OA6DeAGKT5znSczF3HfZhkOeIu+d4H9kQHgEwvAJB1WeOeSHLGryo8AnL3+OYILiY2iOBEvgMJ+LLI4JLi38nYLSUpBMRKCm0p3SGq/3ciZIXwJygoTxeBuXXHvacyuabM/xKWFRpEBrq1rTjDWWv8uZ+Jf72Qplgqxzjof0u12lVrVt5F0QcxHxBY8yhmKOM80FaF0PzPJpFZgfPp8h7SJarEf22SFTfNPJNx+t7mF+9ouUuNMMM2NS3Wu3xzaYW9pAHDPVkmranq/CdhUARupvk4iFIaRWIAMqsclAg1rwEJ4qkJHaE2jrgdrhso0DlW/sfRFHREiDdJSBqGdtlSqJyRhfkBXY5IUvcS0Xzq5QX+qWkHFm7LZiFe5hS8ZR7VE2lj1y6n6Ru9jwhGFyBgETHnIWk8FSgKoJigTsuRkpWHBY5mx1Nk641rw4VCR/abmlqZKLQpWazsUrXKYAE8/WZcUrXJayTDfNkj/Dt3IyGUumIlxxVmTB6uEX/0R4VqYBrexIA+obiAbUVxffOqkp1tpcMsx+Vgis4SW7+vFqUPGOWJXtMaSfGkG3RcwO85h14cxECH4wpSCwkPbIbSPGy2jK9+UGrJy1sbxa5hnRUfetUlPas1Wh8O1gWCmcG5BLMVLAtBS+3kwphtiDG0i22GPdNMhNTqFMtCVt8gOfEAdbxjH86J/ue3pZep5EMswSEKZISqcuddeiccJ4jGpicVaAiGTEzN4cFDEDR4YnsOHDTzMQtXpHlkwTR7aWhLqd7sujzvFR5/i20+nZP//9rvjAOuePjCuIbP1AcaqSG5Qlz3L0yoOXl2sZsRbcdbkfaqfhIxfzSzGRqJ0DyyMHlg/jlH830HUTz98N+ySCVGpu9N8MWRrAvmbZBRu9ev3L19WfqNRTD3hTF+9Qs9DwBbPZ8rTQVOdPwWFlFq2saIW2uC2C7Ru957XTXT61slW/6kfcW1S40YnuWFTHPYIFxGjy0QRglIIKQWw9O3VL9IttZAIWvOE2NgXCNGGk3FTJ1Gm9/M7gWctMhTBy1h1xoY3KbLZ5App+w8S8cAzxt1qP6Tyn2lg1ckds1SN3zMR8NC7Ktlo9ERdfeZAYSZSh5pGqGWGYYx/XL+Umxn4qXD218wrrUVmjnukISVplnq+AghD4Ag2HBGqEP0Eca3LB1FSWDBwsP8yjKAKH2Rx3X5BfGRdkaAIyZIJcKCZCrkMZkLPTinNu5JHIkjGoJwSm75l8024bHndfnLz8+dXrXzolPyUzC2aexc9tcvwaLI47nU735DVySNkKK+ZI4RDjG4r3MEtTaRGro0gsxZ2KYnKa0YAuuQL60KxW28+DF61+lDUCYruXttuyqf/DrhTYz1W49NNEbgPDRQ43DmaNfrWYhFJM+DRTVWULpViANeAkE9FmcfMFPRwD154TnA8qSf1gcN3Q81JBTZPKJbVMYLPskw9pkZj8Zrs6qXfDfr27f9v/7br74fq3tx8u331+//Y/V3eXnwe/vju9uTu9OTt91X9/+/Ji0L24GAw+fH7xpvtp+Nu7tyefXryyZyqW4TycMS5GCSTyCeep3EBwQwkYPJMSo5jQLNwwrz3OG2Cs5staVBcG2xOIlR+3YrwSoW2v1fWiur8O1uN7p0gF2JPYXYy4GI2fEEJ32pZospxJYjdujGpxmieLSlUPLlAIx2o8/zKEv+UJaMOSlCwRzNckyAXbJccuSN8AvaOiy3iuWdy+g+DUt8cu3n+XeZrT7+e1O414daH6sGeQWsSWo2wzCTb+ILATtKhQZ0mCOKdEgH5/XKwL6ILFGfiT5tpcGEVDukU81QkP/KBAskVg7KRbDonXXpDuIVoQDPLBSNmVb1L3xs81eFwDuM1Zll3gjV9r09dqVlqOSjdnmcUo058yViPFJw79/JnfE8dydU02hjDevMWfVfhhvz0W91mvmcuqE9ZIOPvCnEWr0USqIrPWfd9sDYujXrZ+W12/7QPFvhjY0n3bVVU3WzWzjV5xa5tn27L9LA+0VTv6nGZf4mMR21XUmopaO9DsBg6B+B0Y3sfdO2C3h5s3YHMDzW4Awzp4K0FXU8/QQwDfAHK2YBwPiOwrT36k7ysluwIf/wvoSed486PlnWCZmUnF/8xPaPVB8qf2T/u/QdaBMCglt3RBtkgYxba27we+NToXrwOagNZsuqVzzTUrC1wpBr2ShtQ0q6Qo+Jx0jj3KzR055W1fZb8XN+uiF5suupBqzKMIxHfxz3bzVTyfY4baLqvOyaY6qPmFzMQ/NdyeGRYTp+q2iDjxI+IG8ixtkUy+q2Bn2NRmM4ek/HsLD0jCzKS72GBzIF5aoK6AH/HGJQe1AKXtHYdMYdKjeLmhuPswROvn5vFvQFTjh5R/gNUGGn3/6ZbgZ5r8819mZjjFzc0TEM2nAiKy5GZGmCDnw+7Ln0mqbFUjc1i1aEBdBTl1B6KQFrEZnQGL0C1r/D3JG0OHS4v61Od6nCkNtre+jplBBI33RTBfgtK5lN3WcQvLSFXvb2dA9tP4Ydi//tEOgYmRMibjjMfGqul3JBoHigmbAxln8bwYtdinjEyVzFIccykIecrtC7mAvFktuAswS6nmrU2g/38n4hfxRdzOuLYsESKDOHKRmyqJR42YGbMD8FwU7MNlWgz6GuQCC67sTSIZAQmZIGPIw99unOGPOJZLHDioHL9IxQEH9jh7v3dFu+3+Poo8Ix2lzkhHYxbOQUQPPxTwdsrNLBsjhm4/i8KPPWKVL0VZ4YjIMC60m/faZcWtJ8VypJUpp2Axpdjr09YzNJsom0O/RbWCxCHdljAmxdq/rM0M4uQonDFl9F6RvXVtowDaCeOi7R7s1eeQGu8gToglVIxBY7my1xUOnjVssqZkno1BCTDgrpfZaw6Diftg7PVQteYJFx3JyVF1FyLmIQhtK0aRAFMWzoB0bZ7K8zPS6rXby+WyxexbS81t1e2Pl2fnV8Pzo26r05qZJLZ5MpXaJEx4hN9CeUXPqx5kWE2lvKTzWNXlf+JtP1erDHw17TRmXGBJt8Z8dMXxnm4pjg8BnUlt8O3j45hpuFPxeo2P/8gAy8X9A3Z/iuPowt4KDIrahNV0DlhRTu3X/KpN3EQKa79ivz3HZpFtFNm5LbLuH0i9eCW8FnSjXOYi4P/XwY4tj495CV+vy/X5q507nIrFarTmw3q9/h9++7Od
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Bridge Integration Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/bridge-integration"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves the current Bridge integration status and information for the organization.
-Returns live data from the Bridge API including KYC status and virtual account details.
-
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Bridge integration status retrieved successfully","content":{"application/json":{"schema":{"type":"object","description":"Complete Bridge integration information including status and related data","properties":{"status":{"type":"string","description":"Current status of the Bridge integration","enum":["NOT_ENABLED","NOT_OPTED_IN","OPTED_IN","READY_FOR_DEPOSIT","ERROR"],"example":"OPTED_IN","title":"BridgeIntegrationStatus"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"kyc_status":{"type":"object","description":"KYC verification link information","properties":{"id":{"type":"string","description":"Unique identifier for the KYC link","example":"kyc_456def"},"full_name":{"type":"string","description":"Full name of the person undergoing KYC","example":"John Doe"},"email":{"type":"string","format":"email","description":"Email address for KYC verification","example":"john@example.com"},"type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"},"kyc_link":{"type":"string","format":"uri","description":"URL for completing KYC verification","example":"https://bridge.stellar.org/kyc/456def"},"tos_link":{"type":"string","format":"uri","description":"URL for accepting terms of service","example":"https://bridge.stellar.org/tos/456def"},"kyc_status":{"type":"string","description":"KYC verification status:\n- not_started: KYC process not yet started\n- incomplete: KYC process started but not complete\n- awaiting_ubo: Awaiting Ultimate Beneficial Owner verification\n- under_review: KYC submission under review\n- approved: KYC verification approved\n- rejected: KYC verification rejected\n- paused: KYC process paused\n- offboarded: Customer offboarded\n","enum":["not_started","incomplete","awaiting_ubo","under_review","approved","rejected","paused","offboarded"],"example":"under_review","title":"KYCStatus"},"tos_status":{"type":"string","description":"Terms of Service acceptance status:\n- pending: Terms of service not yet accepted\n- approved: Terms of service accepted\n","enum":["pending","approved"],"example":"approved","title":"TOSStatus"},"rejection_reasons":{"type":"array","items":{"type":"string"},"description":"Reasons for KYC rejection (if applicable)","example":["Incomplete documentation","Address verification failed"]},"created_at":{"type":"string","format":"date-time","description":"When the KYC link was created","example":"2025-01-01T00:00:00Z"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"}},"required":["id","full_name","email","type","kyc_link","tos_link","kyc_status","tos_status","customer_id"],"title":"KYCLinkInfo"},"virtual_account":{"type":"object","description":"Virtual account information for USD deposits","properties":{"id":{"type":"string","description":"Unique identifier for the virtual account","example":"va_789xyz"},"status":{"type":"string","description":"Virtual account status:\n- activated: Account is active and ready for deposits\n- deactivated: Account is deactivated\n","enum":["activated","deactivated"],"example":"activated","title":"VirtualAccountStatus"},"developer_fee_percent":{"type":"string","description":"Developer fee percentage as a string","example":"0.5"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"source_deposit_instructions":{"type":"object","description":"Bank deposit instructions for sending USD to the virtual account","properties":{"bank_beneficiary_name":{"type":"string","description":"Name of the bank account beneficiary","example":"Stellar Bridge"},"currency":{"type":"string","description":"Currency for deposits","example":"usd"},"bank_name":{"type":"string","description":"Name of the receiving bank","example":"Wells Fargo"},"bank_address":{"type":"string","description":"Address of the receiving bank","example":"123 Main St, San Francisco, CA"},"bank_account_number":{"type":"string","description":"Bank account number for deposits","example":"1234567890"},"bank_routing_number":{"type":"string","description":"Bank routing number","example":"121000248"},"payment_rails":{"type":"array","items":{"type":"string"},"description":"Supported payment rails for deposits","example":["ach","wire"]}},"required":["bank_beneficiary_name","currency","bank_name","bank_address","bank_account_number","bank_routing_number","payment_rails"],"title":"VirtualAccountDepositInstructions"},"destination":{"type":"object","description":"Destination configuration for converted funds","properties":{"payment_rail":{"type":"string","description":"Payment rail for destination","example":"stellar"},"currency":{"type":"string","description":"Destination currency","example":"usdc"},"address":{"type":"string","description":"Stellar address for receiving USDC","example":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37"},"blockchain_memo":{"type":"string","description":"Blockchain memo for the destination transaction","example":"12345"}},"required":["payment_rail","currency","address"],"title":"VirtualAccountDestination"}},"required":["id","status","developer_fee_percent","customer_id","source_deposit_instructions","destination"],"title":"VirtualAccountInfo"},"opted_in_by":{"type":"string","description":"User ID who opted the organization into Bridge","example":"user_789"},"opted_in_at":{"type":"string","format":"date-time","description":"Timestamp when organization opted into Bridge","example":"2025-01-01T00:00:00Z"},"virtual_account_created_by":{"type":"string","description":"User ID who created the virtual account","example":"user_789"},"virtual_account_created_at":{"type":"string","format":"date-time","description":"Timestamp when virtual account was created","example":"2025-01-01T00:00:00Z"}},"required":["status"],"title":"BridgeIntegrationInfo"},"examples":{"not_enabled":{"summary":"Bridge service not enabled","value":{"status":"NOT_ENABLED"}},"not_opted_in":{"summary":"Organization not opted in","value":{"status":"NOT_OPTED_IN"}},"opted_in":{"summary":"Organization opted in, KYC pending","value":{"status":"OPTED_IN","customer_id":"cust_123abc","kyc_status":{"id":"kyc_456def","full_name":"John Doe","email":"john@example.com","type":"business","kyc_link":"https://bridge.stellar.org/kyc/456def","tos_link":"https://bridge.stellar.org/tos/456def","kyc_status":"under_review","tos_status":"approved","created_at":"2025-01-01T00:00:00Z","customer_id":"cust_123abc"},"opted_in_by":"user_789","opted_in_at":"2025-01-01T00:00:00Z"}},"ready_for_deposit":{"summary":"Virtual account created and ready","value":{"status":"READY_FOR_DEPOSIT","customer_id":"cust_123abc","virtual_account":{"id":"va_789xyz","status":"activated","developer_fee_percent":"0.5","customer_id":"cust_123abc","source_deposit_instructions":{"bank_beneficiary_name":"Stellar Bridge","currency":"usd","bank_name":"Wells Fargo","bank_address":"123 Main St, San Francisco, CA","bank_account_number":"1234567890","bank_routing_number":"121000248","payment_rails":["ach","wire"]},"destination":{"payment_rail":"stellar","currency":"usdc","address":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37","blockchain_memo":"12345"}},"virtual_account_created_by":"user_789","virtual_account_created_at":"2025-01-01T00:00:00Z"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.api.mdx
deleted file mode 100644
index e859650e6b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-organization-circle-balances
-title: "Get Organization (Circle) Balances"
-description: "ATTENTION, this endpoint is only enabled when the tenant distribution account type is `CIRCLE`."
-sidebar_label: "Get Organization (Circle) Balances"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWFtz2jgU/isavWzbMZdAmszwxi0pCSEXIOk2zaSyfcDa2JIryaGU4b/vHNkGk5CEdmd3Ng/ByOd8Ohed77NZUMOmmjZuaYuFTHig6Z1DfdCe4rHhUtAGbY5G3cGodz5wiAm4JiD8WHJhCNdEinBOQDA3BJ/MAhDEBEAMCCYM8bk2irsJ4hDmeTIRhph5DOj5rd27ave738rUoTIGxdCq59MGPQZzrqZM8J927V2bKy+E96sAHapAx1Jo0LSxoLVqFT82Y74CkyihbTSyAPaHJikccddwnhQGhEEUFsch96xp5S+NUAuqvQAihlcKvidcgY/1yvKhDnULlcPsaINK9y/w8F6sMDfD01BznydQ2jCTYCDW+20U31eg7WVmiGUWU/q0caMASGZM5MTWYltLHBIr0CDMuoHPmjUcdfv95pXtFvxgURzivsftz82T+ueT+vVp/eToU/3yrHN0Pjw9qw3Ozr60huf1697ooDu+uLwZdm5qJ4f7Z7X61dWwT5cO9Wwb7mcsDMHcc3+3dHqdPJOsjan/LikUzts6g71qtXqwf1A9rGFM6f67xGFRX6np5i6d3nB01WuNcYjum+32+XgwKmclLXda99fNcX+EHiKJ8EC8at8dXFNnZ8itdmkp1mZ3Syc/hFuyX+fRbI96191CoKuFi+6g0xsc34+H3at7u9rEHendEsvKTVqGQqGa2SgsC/Oz3pspxeZbC//mMHMDURHqpSHSGsy9J/0dG27tCdrnbc/2JDw9b0MDYcgUEWBmUj1sHoDxsNPGVNNdudYJqF/ZN/X4nZ2PW63O/mHv6KB/c3p4cXjW6V4P2zdXh52L8c11ffBnvTO67F4f9fcHzdF+8/JT/Uu/f9RvfrTRRjlb7RCntX0S4bNZK1erFE/Ec/+8gznCkz5vnTHSTpQCYcJ5pky5ICUafDKRqkgU2xA0Bpifzkxf6DL9c+j+NmFpMZ8gd4M2DhHSEJ3EsVSmKH9bdY9ra56zl51ASyPlTQX6UPmwKTqvn2NQSu5wlDpgGA81Ya5MjI0gdVxig4xib0+MLcmqmauNaU88spD7hIs4MbQIN+EQ+vcTKWljfY11WGmfk627TK1sXHuSwdfESOICYYJwYWAKiq4bs/e8MWPBEhNIxX9a4J01/bfKu3vZnvOqSCIXbOUj0JpNtxDQ8qViD6QhG2muo8j32a/uFZCfevybwBZbg5cobua0cbugLWAKVDMxAW3c3i3v0N8EEh/ypmBLxfAWrRT4W4N6BKWtf6JC2qAUHXPcITYurWwRfa0cMT+F59JxcjNaswKGDcJkZ8Ihmk8Fzi83AR637rD28YDEij8yA+QB5jihgkVWAbOMrSeqDYIHwHx7PPH7RNpoMlLJubnDtZsoDRE+o1yEzEykikjzokcdiummUdbKe+Uq1iCJIqbmGTW+jvFu2Ll4j1PFiJEyJG7CQ2PTLFKonaaIPQBxk/CBxGyOKHaVkamSSYzMpMDjMbc35COol9TlOXv/v0L8Kr6KUaYHTBAZgyhpmSgPSKwkTikxAbOUnIYiBTEyzrn5CZxDmPDtDav+HhNISxOZCN86BvglDOWMiylREEvNjVQcdAPjKJFbneJVss+SXyhSKc6KVHKZ9wDCv3sXGBPrRqUy5SZI3LIno8ovIbxvEJv8KpQ5QTJkPHsdysxsVlxMFNNGJZ5JVJZgrpuv9rT8C5lNlOXif5JaDvFWbjNwSW7729kEEEYlL2DK6FdDLthVjAKoRIyLSrbwaj5vpfEJwohYIBu/D3Eo53i83syEJBrtHhIXlAADuvwVacqAivT5ZAjqkXvIS3laWZhlqaYVa1SSk5LOzBwacg+EtkqRE2DMvABIzfJUys+I1ahUZrNZmdm7Fi1z1ZV+r90dDLulWrlaDkwUWp6MpTYREwXgYzCk+NpP8vd+Unjx32CexVrk/4PfKDJ9MfDDVOKQcYEKbguwyGTsduOXgEBqg2uLhcs0jFW4XOLy9wSQ2G/vHPrIFMegrDY6uYqg7j0Acn/T8yBGlXxkYZJq25MHmQ1FPe7i+x57JocPVg6zC0TPb4l5AfupsKUh4P+l84LLYpGK7XK5sk9vveiRpZhbYw3vlsvl3+fIblM=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Organization (Circle) Balances"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/balances"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-ATTENTION, this endpoint is only enabled when the tenant distribution account type is `CIRCLE`.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns the organization's Circle balances","content":{"application/json":{"schema":{"required":["account","balances"],"type":"object","properties":{"account":{"required":["status","type"],"type":"object","properties":{"address":{"type":"string","description":"The address of the distribution account, present when the account type is `STELLAR`.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"circle_wallet_id":{"type":"string","description":"The ID of the Circle wallet, present when the account type is `CIRCLE`.","example":"1000646072"},"type":{"type":"string","description":"The type of the distribution account.","example":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"status":{"type":"string","example":"ACTIVE","enum":["ACTIVE","PENDING_USER_ACTIVATION"]}},"title":"DistributionAccount"},"balances":{"type":"array","description":"The organization's Circle balances","items":{"type":"object","properties":{"asset_code":{"type":"string","description":"The asset code of the balance in the Stellar network.","example":"USDC"},"asset_issuer":{"type":"string","description":"The asset issuer of the balance in the Stellar network.","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"amount":{"type":"string","description":"The amount of the balance.","example":"100.00"}},"description":"The balances of the organization's distribution account. Currently, this is only used for the Circle distribution accounts.","title":"Balance"}}}}}}},"400":{"description":"Bad request, not supported when the distribution account is not of the CIRCLE type.","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-info.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-info.api.mdx
deleted file mode 100644
index c60bdbc909..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-info.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-organization-info
-title: "Get Organization Info"
-description: "This endpoint returns the organization's info. It is used in many places across the UI. It returns the name in the navbar and the public key of the organization’s distribution account."
-sidebar_label: "Get Organization Info"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWOty4jgWfhWt/nR3rTF00tNTxT8amAzduTCBpGc3nXKEfYw1yJJHkmFoiqp9jX29fZKtI9tgCCHpndmtnT+Jkc7107lJK2rZ1ND2Hb3SUyb5V2a5kvTeoxGYUPPM/WzTccINARlliktLNNhcS0NsAkTV+F4ZwmWsfDKwhBuSG4gIlyRlckkywUIwhIVamYLzZuAI68IkSwE5iu/5hGnCZOR+ZvlE8JDMYElU/Ejzv/7xT0MibqzmkxwXCAtDlUvrU4+qDLSjGkS0Tc/A1n0dyFhRj2owmZIGDG2v6Emrhf92Ibgu7ayrJRFYxoWhHg2VtCAt8rEsEzx0BM1fDDKvqAkTSBl+afg15xoiBL1ucVBaTD3KTcCyTKs5E8GG3KNCTVWQa0E9ikBRj2ZsmYK0QchkCEI4lUEGmqsoiNgS7co0n7NwGWRK8HAZCC5nzt0Q+Bx0wOWc24JPgwEZBVxa0Ki5FGB5Cl+VhCC3YaDi2IDF+LDLDGibqskvEFqnB2G2vEDQ2ddeVVTopZxSj8JvLM0ELo0sGqxJh0d0XfPtKFNibWbazaYpmBsRN5NcG0AQGplgNlY6bUxYOAMZNSKY+yWlr/S0WT+5JipExQePYO+YjGU2d1igZc86z6JIgzGHXNnPKiAlcRXUh2LYI5k7G0sWCRTJUe4QlI+p9jAa98/PO9cP/g5eZ92fOx9Pf/54evvp9OMPP57+dNH74Wr06eLk8uLi7x9GV6e3g/H7/s3wp8+j3ueTj9+/uzg5vb4enSMwIdehgGDBhAAb8Ohl7gx6lSddx08K/pe40B1cd8/7ex68bbVa79+9b31/gjYV+l9ih5N6BNNdLb3BaHw9+HAzHlxdBp1u9+rmcuyXkPq9D8Ft5+Z8jBwyTzEgjtL3L2+p92KRB+kKKLZk92uvCsKj+dHpjge3/Zqhm4Vh/7I3uDwLbkb968CtdlAjvV8jrNwWMNSA6pSp8ESKBEU9DmawfP5Aev3hdb/bGfd7fyFDAcwA0RCDJlaRQ8L9Kim4NBZY9McF9aFidhTRv7Za7VYLWQ8W5S3vRCkBTD7yvS/ZRIAhaS4sb+QGNKnEkIXSs1ioBYmVJvVaZuo2WJ3D+htK9tYmXJ+CPlx3Upd9KibIRGzCrEuWUW9IFlwIsmDc4gEVOtzeVjNu4EplVCkgYXMgUmFTn3JjQUPkk0FMHloPXkGRAit7fSGXy2ldbAzM5trVg4gbRG738L9bv6Dp/cEAFHoII6XigpQbR4D24+nVwShQKwB40v1KWN2Ll7l/oKG/qCQiZXVuO0NMKZEUEo81XNdGS/JGSV4PzcLrYtgKUjCGTSGwkGJrfmHhDnNjVUoqpmKItIq4INxGiilALqPPJ8j6EEHMcmEfSKmacCNfVROmC8Wi9ZTbrwwppzbC7StDMmUMnwhA0SwqQj5WQqgFnvLGojnT3OV0m6xWfn2WvGQprNdkkfAwwTNEAfV9ggSoM+bTXEPkhtvVyr+uwXbO5Wxfhju5KUgcYyEik6UL0gqUvVQkr7kkIdZYi0M7Ny4hq/bLdxDwCsdZblXKLA+ZEEssTyAjtK5ICJDRm90K/DeVF6m+zYl6LixVTmKt0sPw+KQreDh7wu966mBoKZv9vkC6Gg834bA5QgN2Ax8ShCqCRziGCt21UK5uTSVYs//kIXc1Hj5iqwFxMLCOA/I/iLuN3dxgkOknwMgSJYHMQfO4vIY5v3xan3V27rvrNW69a719fO27kSy3idL8q7uDvfiad/yKAFor/TiO1+it1cw8L+HROCjzdAIaRZQgHxDv3NzguTGDXipLdtzcWlHpedd6W5O8z/HfFOxkGwhzze2Stu9W9AMwDbqT24S27+7X98hvE4W3+yk4qBhu0Z0bH0UhGruFk+HumpQicyV7hIdXoFvXsEGRZfwTLB8Vm4+fx0WXwtqHpoO0ZVx4xPCphIgsuE0Ik6Q/OvnufdFwLeBjhl9d5tu0U3pdWctReAIswlPFARRfKtCaMoKrG3SvNjiSYXkJJp3hgHoU3S2sPPHf+i3EIE9TppdlkTwu4/WoN3yDycaIVUqQSc6FdW7WgXWtOGUzIJNczKqO4FYZmWqVZzhkaQh5xt2GcjNSTbsEi6Owf7CO/3+Z+EV+keOyvjFJVAayYVSuQyCZVpipm/GwMMXNyll1Fd0T522et1zhDZkkE2wAuYwc40430JApw63SHEwb7WiQu3Iue9mDyP3rapybcpvkEz9UafObJLxpE+f8xpSla2eMl0NtSea84jLWzFidh26kdQ5Wk/LRM/W/wbNYu3r8e1yrRDzn2wImpKL9j71JQKSNMGHamqMm1+iaVgM0U8Zls1w46s9zbvwIIiVOUHHrhEyopRs2ns213CDdLJ+AlmDB+F+wTFnQqbmKR6DnPHzqzuCIGipumJLMo4KHIA1sXwtpJ2NhAuTE1amiPqOsdrO5WCx85nadtJLVNM8H3f7lqN848Vt+YlPh6mSmjE2ZrAk+A7s7FJWPvjvFZrXt7X/u5+6yW1n4zTYzwbjEmaB8Wi0a4x1Ve6/9iTIW11erCTNwo8V6jcu/5oCt4u7eo9UI6jquV/Ul7KTuCYh2whAy7L1zJvKiW+6NRzt9+qyPj1/sUYOduQZbfqD0aksua7L3W2VhAv5de0+wrFZF+16vN/TF1pMcpYsVNeJ4v16v/w0sJvOd
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Organization Info"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/organization"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint returns the organization's info. It is used in many places across the UI. It returns the name in the navbar and the public key of the organization’s distribution account.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns organization details","content":{"application/json":{"schema":{"required":["distribution_account","is_approval_required","logo_url","name","payment_cancellation_period_days","privacy_policy_link","receiver_invitation_resend_interval_days","timezone_utc_offset"],"type":"object","properties":{"name":{"type":"string","example":"Stellar Aid"},"logo_url":{"type":"string","example":"https://stellar-disbursement-platform-backend-dev.stellar.org/organization/logo"},"distribution_account":{"required":["status","type"],"type":"object","properties":{"address":{"type":"string","description":"The address of the distribution account, present when the account type is `STELLAR`.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"circle_wallet_id":{"type":"string","description":"The ID of the Circle wallet, present when the account type is `CIRCLE`.","example":"1000646072"},"type":{"type":"string","description":"The type of the distribution account.","example":"DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"status":{"type":"string","example":"ACTIVE","enum":["ACTIVE","PENDING_USER_ACTIVATION"]}},"title":"DistributionAccount"},"distribution_account_public_key":{"type":"string","description":"DEPRECATED! Please refer to distribution_account.address instead.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"timezone_utc_offset":{"type":"string","example":"+00:00"},"is_approval_required":{"type":"boolean","description":"Enables multi-user approval workflow for disbursements","example":true},"receiver_invitation_resend_interval_days":{"type":"integer","description":"The amount of days that the SDP will wait to resend the invitation to the receivers that have not registered. If `0`, that means the resending invitation feature is disabled.","example":5},"payment_cancellation_period_days":{"type":"integer","description":"The amount of days that the SDP will wait to cancel a payment that is waiting for the receiver to register. If `0`, that means the payment cancellation feature is disabled.","example":5},"privacy_policy_link":{"type":"string","description":"The link to the organization privacy policy","example":"https://stellar.org/privacy-policy"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"otp_message_template":{"type":"string","description":"The custom OTP message template set to send OTP code to the receiver complete the registration flow. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.OTP}} which is the OTP code to send to the receiver complete the registration flow (in case this is not present in the message, it's automatically appended at the end).","example":"{{.OTP}} is your {{.OrganizationName}} phone verification code."}},"title":"Organization"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.api.mdx
deleted file mode 100644
index 0dfb46575b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-organization-logo.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-organization-logo
-title: "Retrieve Organization Logo"
-description: "Retrieves the logo of the organization for display in the UI navbar."
-sidebar_label: "Retrieve Organization Logo"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVcFu20YQ/ZXBnBKAEl0D7YE3tzFSN0FtVA56sHVYkiNyq+XudnYoVRX078WsKEdJUBtpeygvJHeGb98bku/tUUyXsHrAW+6Mt38ascHjssCWUsM25tsKfyFhSxtKID2BC12AsMrX4ew5WAWG1qbozA6sz/UPN+DNpjY8xwJDJM6dNy1W+JbkfNf3oQtYIFOKwSdKWO3x8uJCT5+SuX2HBTbBC3nRqonR2SZjlKERklkSJjNoLTU9DUavZBcJK0zC1ndY4CrwYAQrrK03vMODHgUOJH1Qdh0JFhiN9FhheS6zdEemiXhDrNPb48gOK8TDUpebka3sFrr1Ucb3ZJj4alSsJyYm2ne0w89H/dOv9zAmavMwzSg9eZnUFZBs56mFrZUejIfrxeW330FkuzFCsKadDtmbQeF1t8CnN1qgVfCeTEuMKtT6VchsrDjtXwg5Zxje2FSPnGggL3DnjOig4OruBgtUuUeWl/Nv5hc6g3EYdHoV3vcEz2O8Wry5ew02gQEJwUE9WidZ5vl0E0iAwawJ6tGtIZqdouRVAx2HMeqnx9TYaHMhbIjzp3ba3ZNsA6/nX4z2/0fx0T/6+96mvKWHEMnPUhi5IYgcfqNGQHojWj5SCR4kxNPP9xlcAca3udCElqAxHmqCVRh9mx/s9ca5sLW+A6YYkpXAllKlPGbwkI545XSetWdDmsVpSLPaNGvy7fJVLxJTVZadlX6s500Yyq9CeF1BFv9EZQf6Wxvrjz4ztWVV1q/YJOGxkZEngfpe5KV3Ov8KZSvOrvJvpJ0gXtK2pRpOvf9YTU9umDW9YUnPUj7rK4WJysFYX04Lz+p5ScaP5AbIQEfzp+jCTj+vF5XAmLRvPdbEnoTS/FFtSoiHdLtaEG9so750kjXRnAfuytw0C6tZmtoKdLYhn0gd7WSA0TQ9wWX2qaM/K1ZVltvtdm5yNaNNj6by/c0P1z8vrmeX84t5L4PLPhlDksH4M+BTGMJ5esEUX584zv5jTP1XETqFh9AfUkZnrMfDpG4/hdUDngPqaJTZssA+JNHyfl+bRB/YHQ66/PtIauAPywI3hq2pNQ4elofilBaab2tSj79qGooaixvjxmOG/U30ahA+Renb63s8HP4CJa4Ftw==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Organization Logo"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/organization/logo"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves the logo of the organization for display in the UI navbar.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/octet-stream":{"schema":{"type":"string","format":"binary"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-profile.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-profile.api.mdx
deleted file mode 100644
index 408d73998a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/get-profile.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: get-profile
-title: "Get Profile"
-description: "Fetches the individual information of the logged in user to populate the Profile page."
-sidebar_label: "Get Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVlFv4zYM/iuCnu4Ax+4KbA9+Wrd2XW/DViwd9pAGg2wzthpZ0ig6uVzg/z5QttOkXdvdhgHLQ+KIH6nvo2hSe0mqDjJfyFt0K21ALhNZQShRe9LOylx+B1Q2EAQ1ILSt9EZXnTJC25XDVjFIuFW0GlfXUAltRRcABTnhne+MIojmcQfhVQ2pTKTzgNH/ppK5vAaaKCQSIXhnAwSZ7+X52Rn/nLL6BahDG4ad/MGxdJbAEuOV90aXcYPsIbDTXoaygVbxE+08yFy64gFKkon0yHRID1uuNAb63aoWjrCBUNtaJhI+qtYbXvqgLMg+kUb9Lfili2holTavIx8qB18zLHVYsw86M1AbfRSi2slEaoI2PI/V94l0WCurP8UMvECOYYdNT2UP2k6kRf4H+k84HiguZAUbMJxOLqa/YCHnBMYoFBe6Ym2kKYqezr/nTyIDlB1q2sl8sZffgELAi44amS+W/TKRLVDjuHJqiAeo2CSzx1oIgBvAEN07ZMaS/aawc66FIafHwR8z7PUPwCk+LbwPv91x0VVi5VCojhqwNJZZIoKuLVRiq6kRyoqr+fmXXwmPesPvwBp2XPZjDng3h2Ni+CA5eAOqAozHwu9XZDMmZ8rZpQ5FhwFasCRujSJ+DcXF7Y1MJMsdWJ6nX6RnnIOubRXuZC7vGhCvx3g3v7x9L3QQSpBzRhSdNhRlHp9h4Pe6VWsQRWfWwqsdR4mrStToOs/tAKHUXkeD23AvONrdAm0drtNnqf3/Uby39/au0SFuaYXzYGfBdVgC9xxuHYIaRWweqDgryPmpIT4Jlwhlq2goXQWiVFYUIFaus1V0bPiPMW6rbS0QvAuaHGoIOfOYiUUY4mXj76w6StLMj0maFapcg62W7xoiH/IsqzU1XZGWrs0+K8L7XETxByo7wf1VaTtMgxEWVWm7QhUIu5I6HAXyudBbZ5p+hrIVxvb+b6RNId7StoVCTNh/rKYB087KRiGFVykf4TJCgKxV2mbjwqt63pLxPZhWxECRfwXeuB2X15tKRBcYt+4KQAsEIb3nNkWAbfh5NQfc6JL70iRrpMmzIIugmVvNwghLpNEl2BCnzNQAvSobEOexTw39mWPlWbbdblMVrTHa6BqyH2++vfppfjU7T8/ShloT+6R3gVpljwJfA4nHq8RJi9k/XhD+u3vNOD8IPlLmjdKWZ1wUuB+n1EL6x9tW4wLx0n5fqAC/oul7Xv6jA+7bi2UiNwq1KngKLJZ9Mg0JHmtr4NZ+UZbgeQZulOmG0fXk6nMyL6+v7mQi1bNpt47Tbnzg6JPJ7o5iP51bAwX+7pMXXPb7YZb2/QE/mF70GCVOaE7hsu/7PwGOS8iP
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Get Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/profile"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches the individual information of the logged in user to populate the Profile page.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns user profile","content":{"application/json":{"schema":{"type":"object","properties":{"first_name":{"type":"string","example":"Jane"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string","example":"jdoe@mail.org"},"roles":{"type":"array","items":{"type":"string"}},"organization_name":{"type":"string"}},"example":{"first_name":"Jane","last_name":"Doe","email":"jdoe@mail.org","roles":["developer"],"organization_name":"Stellar Aid"},"title":"Profile"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx
deleted file mode 100644
index 8a32c7c311..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-all-disbursement-receivers
-title: "List All Disbursement Receivers"
-description: "Fetches a list of receivers within a specific disbursement using the disbursement  `id `. This endpoint supports pagination."
-sidebar_label: "List All Disbursement Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWutz2zYS/1cw/HDT9ESJbz1mOneKJTtOZMex7LhN6lFBYimh5qsAaMf16H+/AUhKlEXJcZL22pl+iSNyH79dLBe7CzxoAs+5NviojSj3c8YhhkRw7bqlEeABo5mgaaINtEMQwQI4wiiiXKA0RAwCoLfAOLqjYkEThBHPIKAhDRCpCUM5p8kciQVsPka/UIJ+aaOLBeUIEpKlNBGI51mWMsFRhuc0wVJ7W2tpaQZM/Tgm2kCbUC6GUVSHfF6h0VpahhmOQcgfg48PWoJj0AYaJVpLo9KWDIuF9tjA45E0SqKsi9VaGoPfcsqAaAPBcmhpXNxHUh6ncRaB1tLgUxalBLRBiCMuCYIFxFgbPGjiPlOUgtFkri2XrRWYDM+hgvNbDux+C8/FAqQPACV57ANDIkWhXIP2BqRKZYkpTFlcR1QifgyoELkFaBbRmIqnYZWIihhIGeESHAORswRlwBTsbwrzWsriWZpw4PK9ZRjyzyay4Soy6wuI6oERpImQizp40HCWRTRQIdX5lUsBD9sAUv9XCKRDMiYDUNBC/To0n6ZN4JPYDgVpO1bhM9D+I931g/2v9Qr8YGlLKQduP4fT3ObE80J5yUoTAXNgdd7esqWJVOBoP5npLSUhFUrf2druZUsjWNR9hRnDMlyogJg/7RdK9tsGgY3dbmDorucZuuO7WMdh19NxgEnQ9Y2+37clCogxjfaLqhLVfyVpO2Vz5aNFmsCsjLC97P82Xde1bK/ndF2l8ZMAluBo9pQJOWem1TcMU3JVIGZ3OIpAfL2DeoZt2CZxdJMYju70un3d90hfJ4HrOWbY7/d6UFf89RoNqw8WEEMPwfd0J3AMvec7Xd3o2R7uuV3HxJZWj5fq05tQoaB8K9NdTHAfiKs7rot1p9uzdGwA6KZndL0uGAR85fMite2T9J76DCcCDTmnXEieRRqDSs57+RZCZHzQ6dwW/DjL2kEabxh/pYytTOcCogizGSaEAef7pR8d/Dh8bf/42n7/xn59+Mp+dzI6fDt9c2Kdnpx8eDl9a78/vvDGl2fvrqajK+t11zmx7PPz6aSuKIY4bdiCNglmxdsGqoABFkBm+InkZRmWrRuWbtgXpjFw3IFrtg3D+CBl5Bn5ahk0uaXPktHflhFhLmYxcC7TJIdE7JC2uZ0IGgMXOM7Q3QISVRhUnxKSEqtfBOEEKZgqMyLsp7lAQhY1Zbw34TSNbZwqH88yfF+UYPvtLfJ8QTqroHwGT4hpBOQztRhFAokxTWgyfx5TgWiG4zTfZHnmRoE5BzELVJ2wT+3ldHQgNRf0lPP8qcR+9PLlyOkeH3qTqzfds+7JaPx+enB13h2dXV69t09/skcX78bvDyfO6fDCGb57ZX+YTA4nQ7fBvv2KTMNoG8ZGdhgWbEv1QWKRN/s0yWNVmp8PDy+0lnY+Ho5+Un+PjqcX4/PxSGtph5Ph0dF4JCv2x3mXFzloWihYqZotKBcpu//yNfkTIa8+wyZtso6U37KsRUCXpE99bB8aN6gNra8K74wTwe61ZRN5QV37Ar9+SyMktKzQdXXbcvu607MsHTtg6QEYpm07/X43dFR07wy37TK9oK26mgpqU2CudwXBcMJxIKXsqG+29aw7pxo3okXOnBaCUQLiLmU3bXQsUIAT5APKORAkaCrZgps6yB3MZSf5sXo8wX7KsFys6++qHTlaPWuXNsmKr/OihVK24hx/kkuzZqooQT3vvGhvJjTftvvEDHp9YpuO2fP8nul0AwuHTtBXhYjvEz8gXUxwj5h2z7PtvtH1nL6vtlLKgggKz4bAZrIrAi4+270Hih9V/KjkR8cj5UzKUZpE9yhjIPe29W5V+fIOcxRjAqX3CnGbFnYd7PV8D+t26HV1x3J83e/5hg5u38Zmn3Qdz65HyaobbzRib07btq+gbQjTHankbHw6Oj49kv8bXk5VQpleHhyMp1OZWobHE/XoYHh6MJ5sJpmzQvYz8uGjDjNBeD5nMJdlzarbjEFg2Quh4tPnSHaZxY6pLCqUyNFJQoqvZFVZpOFqufjKEcECJ3PgKA2CnDEg7W+Rl/+Kbi9LssYA+hZpv1ZPbqb9DUCb6X4/kWp769OhL8z726uRJ/S3HBAlkAga0mK68nhkVjc9z9U8a2114Jo+Nomruxaxdce0Qh27/UD3ILQt4vax79j7mqKGMQ+OYQeM2sZVe6H/miegW/39GWBXgE0vhucXKohWAXbw9uRsMr7YDKf6dGcdU/sblm3jFL3cpza+xn0e3xdsnm4bF4Y5sKyB2233bLPfdT+jB9qGpTqLgunbI+u1bdNzzUdfQ92fVbuqiuivr2rCEEPg+LbueL6hO8R3dOwEju4Ftmv0DLfbNVQ1vau6f5R+JSikaJsK/90lf5OYghpV/fi36gv2h+EXJa6ngugLhRKI4CuFeqVQd51ityO6KtZUSKFVIK0aIRVp/wzI/hmQ/UkDsr/KZOtP66F3NrCV6/8uOWu7OPubom86t9ycNDRR1E9fFLFjmNunYJcJzsUiZfR3IJsnXt93vn/OIRcwljbspsUBCMNf0o1U53ktbXfpryxb+XIFQztNBdqwbI2i0uMYZk3yY45CctOx3x+lTS2Rvb1EhynzKSGQ/CHr0+y+tc7nuGGDS5njbJsjLT9M8+TvGm7PDIuwNLUpIpx6RJwDT3MWAEpWXJU6DkHOqLhX1xNeAmbAhrlYaIOP1/KsOwaxSOU9h7k6PVDXFQZap17+884DJcsOqx1uc2C31ZWHnEXaQNOksErXVC5E4am6xvXII6NvYHvm8frqohjUhSlTAS4b1MJTLcTpPAGi7n/IU5Dx1HI9lDF6K9uXG7iXo4vyfsGw/DaKBFZeMVgAJsU9BI0mYXFeVWbAqmzcOMs/i7CQyRcNz461libNLVBabbNtSB/kcYzlJGej9GyW8d10dPZCjs8wEmkaIT+nkVBmpmyOkxKqutsQ4xtAfh7dVHMS9RSjOUvzrLwHQTOqXqTygKhp8tnY7/21IP6c/Jyo6zhSZYLSDBK9DOKMpfKrQ2KB1cyxgCL753TVnz4S11pNvGTPVk191ZegGBfyRxSld3JSxiBLORUpo8AHEoeOPpY1YTWe1TdmDVnpJN3HwQ0kZD3NnVOxyH1Zb3aeJeHFoLiLtIJyX43yuAJbkimraBIyzAXLA5Gz0kC5LuKpNW0/w7KQqXT6NaZVIp6y7Q58VNF+sTULiGI9WGAm+F7INbqOYAAdecDYKR/stecpM15BFCMlSOEnkEXpfTWI3f+tFdPxm9wHloAA3v5ZpikBLOZvwymwWxrUG5v64YIi0tNQ5yVZS4toAAlXm0eVADMcLABZKk8V+VnKGnQ6d3d3bazeKmklK+9Mjg/Gp9OxbrWN9kLEkcqTWcpFjJOaYHkZDg2jaPe1p42087DepP/fl/rKnUfAJ9HJIkzVtSLlmody0/u4MV+UtgzU2HO9713LjpQLSfrw4GMOlyxaLuXj4v6a3A0J5diPavfQdjpk36W7RrQ3cL++zXeLoxzUvtt6rtLPvVL3BIjVDb41lGv5g1GJ5ZnO+O68vL/3Au28HNmIp6ookvs6kgonJdryWg4Sis1fYipeDIMAsjr4rapsozg6GsvmGG9VMTeqiin/I6U3wnlcjxQQ5L9y8RpZHh6KGmm5XNEXr3ZylCauLJcWLJfL/wF345aZ
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Disbursement Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches a list of receivers within a specific disbursement using the disbursement  `id `. This endpoint supports pagination.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}},{"name":"page","in":"query","description":"The page number to fetch.","required":false,"style":"form","explode":true,"schema":{"type":"number"}},{"name":"page_limit","in":"query","description":"The number of records to return per page.","required":false,"style":"form","explode":true,"schema":{"type":"number"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of Disbursement Receivers","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ec3a57c0-5660-4b5a-af76-acadc7b09b93"},"email":{"type":"string","example":"receiver@mail.org"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr129001"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"},"payment":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"}},"title":"ReceiverWalletLite"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementReceiver"}}},"title":"DisbursementReceiverPagination"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.api.mdx
deleted file mode 100644
index 731d3661ab..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-disbursements.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-all-disbursements
-title: "List All Disbursements"
-description: "Fetches all disbursements the organization has created. This endpoint supports pagination. The response includes basic aggregations on payments within the disbursement."
-sidebar_label: "List All Disbursements"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWm1z4jgS/isqfbjdrbLBvIUMVVtXzEB2ckteNjAzlZ1NscJuY11sySPJZNgU//2qZQMmEEgyma29LyGgfnm61Wq1Wrqnhk017XymPa4nmdKQgDCa3jg0AO0rnhouBe3QEzB+BJqwOCZBmZSYCIhUUyb4XwyJScQ08RUwA0GFjCKuCYgglVwYorM0lcpokrIpF5YcSYAo0KkUGggXfpwFoMmEae4TNp0qmFpCTaQgKZvnWu+4ibiwystwKtShMgVlOU4D2qEDrk03jjfNc2jKFEvAgELj76lgCdAOTdkUqEM5WvwlAzWnD/2AYJGKKPiSgUYbqUPxC1cQ0E7IYg0O1WYeo8BQqoQ6FL6msQyAdozKcNSPIGG0c0/NPEUykSUTUFZZyLLY0E5tsXA2YI1jnnCzH1wPQi6ARPKOJEzM0atZbJ0Vx2SCmE2mBASk8NzS69/HhLpXtuHLfuhdooEpPyIGVEIyDQExklhaYiIls2m0NdkERevXAK+N4mJKy3i1YSbT+0H3vzLfkIQZP8LgRHw5G5HhztB8JZwOBZEldtVedU9G1KFX/W7vmjp0OOpejfo96tDL7oeh/efdxdnloI8/3ixQA0tSqzJnLVlcrNkxM2MWGjuXe2y/EPG8CKithMAMYQqWSYBYacRgJgiYgQo5kSphpkOur6+v3bMzt9d7xTks21j3vCPXq7le/RFDJxBKdWDJP8PSXNw/yFQt1YGcccIhDlYLDuk3jXzNqF2lhtIUlILZYnbKYzflFRlwBb5FvT8JLslIKJU1iIvppk2vuhTXRjHtl6zJvyE2NOMGNebZVqOUuufhx8MkGHNtMHmUtysSgGE8xpnwpTAgDHKyNI25b/e56n81st9vg5ST/4KPLk4V7oqG58rXu+9hWgFfzc4MtIq8f+P29HPjX+td6meMQZoqmD2Fs7bNyaa58oKVCwNTm5BWvMcLhxppWLyfrHa0QEJurL7Ltd0LhwbMlH3FlGIYTdxAog/7hQe7g+FhsZAJ/iUDwgMQhocc1K69YcMrR7U3ATtutd3jdr3lNv3Wsfum0Qhcv1b3WLN1DF7YQvz5sngKBqQ8qHYj5M5R9gJj1gc+AzVWMOXa5HXVOAGtccoMJGnMzBNR+Jk2MiFLpnXOAYEVyYybos4zkiz16rw8/LNYZH+SQjXhWvxgVgVNhZzm228x/IMmxVIh3PygSSq15pMYUDQLAksayjiWd5gbVohmTHE2iUF3yP195aJU1KI/FgtyF3E/Ijwvesvj1mGoM+TTTOGeJwKUcVVy24CL24cyYi5uyRQEVqy4f8zJsHe5coqRRZmWO4P8yAXxmS42GK6JkIakCrQ1dMMDTm44y4xMmOE+i+M5YWkKIkB0xtKCCH6qbATBtcxIxGZA2LLUJneM2wyK2XQuMxIqmex2T4W8i7l/+4jddlbxV1CVPLRKEYWzxXwzzqPo8Xqnf9Y9HWB18/7ivD8+/3D2tn9Fnfzncfe8N/7UHQz6o3G317vqD4cPKHdR3KzTQxn0uxzQCHEsHHrH4hjMS7PC2r8tFrA3ELTcZqvF3Gb7uO4yD8CtHXntozZ4AUxq+9b2WtJHPlFMGNLVmmuDPJFMwB5g9vJFxqS6U63Ocn6WphVfJsivIR3XvLEfcxBmHMiEcbFfFku5G8Cssi0rAEjHGNzjPTXsAUxVHaQoHuWVaoIdkkJbZGGJwAy4htsyolwa1Ruu13YbtVHd67S8TrNVOWoe/46CszT4HoJLm86nPHQWDmVav0YMhSEDvzlpuM2jiec2g0nTZU2/6R75jZZ37LXabc/uD74tXw5l5i6CIpa2rOTDsPcOhXCtM1BPFZNTY4pVoPWGwF/evu0126cnR4NPv7Yv22e9/sfhu09X7d7lh08fG+fXjd7ot/7Hk0HzvDtqdn973/h9MDgZdFuvNPt112uMajhDnVbttWZ+W2gAMXyj0KNCaKsQuti1lw4NxDFTxIYUWQXSMubsbNg1nZ9iX+0EuVZRLheGuZaFQ2egeFiUpeMQjxZ7dXdH/fHFyfjt6dXoPXXodb97NT67OLdfLk/PqUPPu6PTi/PuYHzaW6b7EoiPJXX2ILO2eRxxbaSav7zCyzSo8aHF2AgbrdrkDbgQeKHb9ELmskat6daa7VZ70qwHLE/of/dEYHBpw5L01YJ7sU/l+9zZfWHUnD6FEolCHsP48E5XrljdECau13ARYsXXr7U3/E3ZwR5Yxsse5s6Ty4Oljgwkb61hAb9iLR9xvC3JY10cEp8pXme+D1qHWbxT0/G2opDxGIIXqMoZdxu0rUYBFiPo++drWvE+qowlMsOKp4izJx7sLESS865OVQHRkoRs4wxKjz2v4nnrAMh5XqDFSOzirnGWldS8lRY2A4XHs+foKXiWmlJQS3c91GKVPLLE6eKxkfLR2xI1vdp2A+SDYJmJpOJ/Weteqd0BSskdJYxtnxnFnrAVbGXvotu9cGhx3trVTF6UG3QrGPRcGrJh5hrFUk/Tq5UkP+T4noLzqWlsT82JVBMeBCC+/7zstm4N4AkE1g4Nfqa4mdsbnrfAFKhuZiLa+XyD/bgETCTximgKFhvDIVp92P3UoGbLa6JMxbRDKXIvhQ/R2Nyesop10ZHyX2G7S/mfT6O8AYLHapwCbA/lfnSI5lO8pcE7LsIE6Q/rrSOSKj7DJsUtzPHMXjRFu8XssXJjNAIWYHRi/S5CadEUa3JZOG50ey5jZnBLI93LU2qLOJ2jrFdqFQ99kCUJw1pqo/jcLePHYe/yJ2xOMGKkjMkk47GxZpZvCW2XJ2G3QCZZfLu+18MGDZkqmaV57vZ5yu2AnNk7hLV2AeZOqtvKznT2z4L4h/hDjIqWDRNEpiBcLTPlA0mVxLWRXyVwXUDByySZLlt2D8Q5trmEA3hqIz4TuCuEMhPB8hZq3dtSkErNjVQcdAdxuOSzzuVVi093o8BKCye5E+bfgghuflyezqfcRNkkP5k/R8JPnfwWeAVlbptzjIu8B1aQWau4CBXTRmW+yVRhIM6LOTSnlWdYFiqbv77FtKWIQ7bdwYQsaV9sTQRx4voRU0bvhVyiqxoFUMXCp1r8sNeeQ2a8hzghVpDFH0Aay7ltnR5ca5lGuttsAkqAAV35A9MU3vLqi3AIasb9cguogFmRalq1RK4MXV2QOTTmPght0/4yAabMj4DUbZ7K8zPK6lSrd3d3FWZHrbSCVVcHp+/658O+W694lcgksc2TqdQmYaIkGB8OkG4ck4dPBzayzf16M/x/eiNRbE4GvppqGmOjb1F4777YCD/TzY3wBhuM2uDA/f2Eafig4sUCf86v4XB7DLjG9vn6Tu1RV+1+RrET1S3M1y8zZizOwG7BznPUfcvDiAOgVu8yXgjt2x4+7AH35eWYnv2uYQ+M1TuKF2J59XcGe7DueAHx/VE/8c3A02Cv3jO8EPcTXgPsm+v8tcFLF+nTLu736C+/EFiDuMEv+cWeLf2dZX2MKStn7Po+pGXoW8eajQPDL31s1LGtQv/WFvrFPyh9OSTmJdkPS/YcAv5Ff+1kub/PjxGLxYo+H3qUozBxSY1eulksFv8DJt+7Aw==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Disbursements"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all disbursements the organization has created. This endpoint supports pagination. The response includes basic aggregations on payments within the disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"q","in":"query","description":"A search term used to query through the disbursement names.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the disbursement.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"]},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return disbursements that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return disbursements that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort disbursements","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["name","created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting disbursements.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A list of Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}},"title":"DisbursementPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx
deleted file mode 100644
index 76a7be61b9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-payments.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-all-payments
-title: "List All Payments"
-description: "Returns all individual payments matching the request criteria. This endpoint supports pagination and filtering on payment status, receiver ID, and timestamp. Each payment has details on the transaction itself, receiver, disbursement, asset, status history, and blockchain information."
-sidebar_label: "List All Payments"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWltv27gS/isEHw62gGXrZvkCLA7c2EnTJmkaJ8223SCgxJHNjW4lqaTewP/9gJRky7FjJ2kK7ALnpY2l4cw3w+HcxHssyUTg/jd8SmYxJFLgqwamIALOMsnSBPfxGcicJwKRKEIsoeyW0ZxEKCsXoJjIYMqSCZJTQBy+5yAkCjiTwBlpovMpEwgSmqUskUjkWZZyKVBGJiwhSgQiCUUhixR9MkFpUrFGQhKZiwbiEAC7BY4Ohw1NLVkMQpI4a6IRCaaLBVMiEAVJWCQUHwVIcpIIEmhBTAqIwiW/BqJM+DkXoFY3EBECZKMUi6ZMyJTPCol+lAY3wZSwBLEkTHmsoTdxA6cZcP3jkOI+PmJCDqJoYc0GzggnMUjgysz3OCEx4D7OyARwAzNl4O858Bl+aPbzKSgjLUwKVElTPxgHivshiQQ0sJCzSDFUmHADw48sSingvuS5ehtMISa4f4/lLFNkSR77wLWwkOSRxH1rPm8sYGmq7bBmGaA0XGz/K2ASUm28IkzyWPkiZRwCqUTXtgdf1YEqy1xHLGZyO9whhCwBNE3vUEySGeIg8kgKdMeiCPnKuMq5gSKWlP4rsjQR8GtsbZt1HQo/245/9IMEsjhilUeX7pmG+le5D6+Bd20fhmeD/XPcwGejwfALbuDT0cnw8ORA/TW4GI+GuIHHF3t7o/EYN/D+4PBoNMRXcyWIxJmWXHCo6VwdvWtGtyt+cXE4RHJKJOKQcRA61JBlKCj3ixJJfCLg9dRfwe97vud1CDW8ILAN1wtCo+dDx2h7FiUkgA51u3X1Ag5EAr0m8pqEUm/+Fh0/JtGs9MBlONU6Ew6o5IU0IyRVGKVEQhPt6/DTR1++fPliHB8bw+Ev0t42Tc8wLcO0H9HRhzDlOwLG05QsOP2DtBQp3xFa9hlEFOUCKJIpUvS/JCgugkfN8LUzWnu4EiCLGKqQbo+PFRkKU66VUDm40uNVo8pSESKCmgbFLwVLaXClJBYxWCgutmmq/1ZRD6ryASiKmJAPElKQJlJljP49JlkWsUDn59ZfQi2+X4eY+n8V+SbjKptLVohelii7aRP4ITeG0oWb/VelrN+d/ywz1+/K4XDG4fYpK631lWRSCC+XskTCRMecxdruvIFlKkm0nczy5oqQSS3vdKn3vIFVhK2tJpwT5UZMQix224XR7bpRGtp22G4bjt3uGW7Xtg3igm0EYFqO4/Z6ndBVKEic5slGC69XTQXtgwS5ItUyzaZpKr5CQhQRfl0rE683Y16XczisZKwUmUViGheMUQLyLuU3TXQoUUASVXMUIYOlallwUwf5yGKUC3Uqv1WPj4ifcqKK06vfplJmot9qRYtnzVKnZsonrTcNlPLFytEPtTXLRRUl6OetN80VK5m+4/SoFXR71LFcq+v5XcvtBDYJ3aBHekDbvk/9gHYIJV1qOV3PcXpmx3N7vjJtwHgQQWHZEPh1Wcc+2bx7ej2q1i9ai8OhNiZTJX40Q2VxgO6mkKzY8o6o3oRCab2C3aqGHZd4Xd8jhhN6HcO1Xd/wu75pQLvnEKtHO67n1L1kUetvVEIT6pLuSfptrON+svpq4L3Byd5IF2L1A615jwtwC5jXZYez4XQ/CLcJIpMJh8lKwI1BEhUcUHH0BVJhl7CkagULISCKjk2dkqprU6ur7RILQwRTkkxAoDQIcs6LdueJUebfZfYYhFDt3yYHWthokzJF36miJpFgKFK8WsjYjmHahumcW2bfbffb1le8GthrgN4Vmz9KJJ/hHUQ6D9R7sRfG/fXdyBP2PQfEKCSShQx4tTEr4mqq57nuHJZaB23LJxZtG22bOoZr2aFB2r3A8CB0bNruEd/VZ7ioi56CSVE+AqOWuGovjL/yBAy7tz0CPOZg4/PB2bl2ooWD7X08Pj0ana+607AmcelTtfrvScppepWnVk7jNotvczbPcMxz0+rbdr/daXYdq9dpf1Ww8ow+C1ZEhETFotdH1m06lte2HpyGuj2PmARdZqgJ0M9XNWFIIHB9x3A93zRc6rsGcQPX8AKnbXbNdqdjtvXm6cJ5l30GChTStHUhF+PhnmLChMiBP5VNQY0IpRyEWGF48Pbt0O0c7ntHlx86p53j4ejzeO/yrDM8vbj87Jx8cYbnn0af94/ck8G5O/j0zvl6dLR/NGjvdsMXBa5dTvRCphQi+EmmXsm0vQyx6x5dFWvapdDCkSrv07uh8CwmInckil7D+bqmYzoWdQ2Lmq7hdjs9w/doz6BB23OtsNfrdqEu+OclmnYPbKCmEYLvGW7gmkbXdzuG2XU80m13XIvYK0fvrBRdHbvXUr1NqK5LDbfdJobb6doGMQEMyzM7XgdMCr61LRcsOX1mPieJRAMhmND7NE1jyDam7fq6qrK+LdaTLGsGabyi/KVWtlK9Ki2rA7mV+8HeH4P3zh/vnc8fnPf775xPx8P9j+MPx/bJ8fHXt+OPzufDc290cfrpcjy8tN933GPbOTsbH+0+oVvPTdM0zSccyKfxeH6CPBsdHI7PR2c6Ne4fDQ4OVhNj5U2isGyVGzf426rp/y0xa704w/MND+ttu37vmtb66OQiIbmcppz9DfT1RiXAebohBek5m+TkJSV8OT2fN/Dj9bJWc2G+BQx8kkq0ouYSRSXHNa0a54crfiXjYmuc9a3ZT7nPKIXk1+/LZu2WAJ5AoPUQEOScyZn+tPUWCAc+yOUU979dqUleDHKaqs9iE9DYiHqFW7VRnQB+W30ay3mE+xirhRXfsdKzUKXOfdmvZuwDrDes7y/PiymLGmoq66vuojBhAwk2UR987picIpKg0dhueyjj7FbVnjcwU31nOUQdlBtH6oPUKRCqHFOVXkmYajTlSaxyfr20RKcRkerco8HpIW5gpW6B0m5aTVPZII9jotrwlbphM4/fxsPTN2r2QZBM0wj5OYukVjPlE5KUUIWaSMfkBpCfRze1sXuKCJrwNNelNYeAZUy/SG/1J4b1sdXGYv2fBfHP5M9Ef2RWIhOUZpAYIs15ACjjqToWxecGJkooqvlJF83FA3aNxbhCFdzVyC5M84RWH+DCNIrSOzXm4JClgsmUMxB9hcNA38qEXs3WjJVGMSuNZPgkuIGELkdxEyanua+KhdazOLzpF1/YF1Bm1RxGaLAlmdaKJSEnQvI8kDkvFVT7InftafMZmoVch66fUa1isUu3O/BRRftibaYQxUYwJVyKrZBrdC3JAVoxYUmrfLBVn11qvIMoRpqRxk8hi9JZNUXbftaK0eZN7gNPQIJo/qnClAQei4/hGPgtC+pVaX0yrImMNDRESdbAEQsgETriVwEwI8EUkK3jVBGfFa9+q3V3d9ck+q3mVi4VraPDvdHJeGTYTbM5lXGk42SWChmTpMZY3ZNAgyhCtZsSK4HmfpkC/38DZfsNlDIXSvghW1lEmP5sozfrvky533BWu94zTYVUz+7v1ZfzCx7N5+px8YFQJWLKBPGj2ie/R3dm8yWVjYBuYLa893JLohx0sm88S9z65ZMtssrLLC+U9TM3R3YYYHFx5YXQnnMpZAuUxf2TF8J4/hWNLWBWL4a8ENFrXqjYgnXDLY9fCviJlyOehnhxZ+OFkLdfe9jmbsWNipcex50XFbaIrl+GWMq/Uj84UwB0w9KoSnsVA4uFgyCArI56rRlbaXMORmpuQdZ6lBvdo5R/KO7Vq2RW4/2w2yggqH+VqTYuub8vOqD5fEFfvHp0RaliRa2sdDWfz/8Hje1HzQ==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Payments"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/payments"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns all individual payments matching the request criteria. This endpoint supports pagination and filtering on payment status, receiver ID, and timestamp. Each payment has details on the transaction itself, receiver, disbursement, asset, status history, and blockchain information.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"type","in":"query","description":"Type of payments","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["direct","disbursement"]}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"status","in":"query","description":"Exact match on the status of the payment.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED"]},"example":"DRAFT"},{"name":"receiver_id","in":"query","description":"UUID that represents a receiver in the database","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"b6b667ad-6cc2-46cf-9be7-561daace7d48"},{"name":"created_at_after","in":"query","description":"Only return payments that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return payments that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort payments","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting payments.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A paginated list of payments","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"}},"title":"ReceiverWalletLite"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}},"title":"PaymentPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.api.mdx
deleted file mode 100644
index fda4b0c078..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-all-receivers.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: list-all-receivers
-title: "List All Receivers"
-description: "Returns all receivers matching the request criteria. This endpoint supports pagination and filtering on receiver status, receiver attributes, and timestamp. Each payment has details on the receiver, high-level payments metrics, and wallets associated with the receiver."
-sidebar_label: "List All Receivers"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWW1v2zgS/isEPxx2cZYtvzsGFndu7aRpkzaN02TTNjBoaWSxoUiVpOJ6A//3AynJlhNXzlsP+2G/xJE0M3yeITlDztxiTWYK97/gU/CA3oBU+KqCfVCepLGmguM+PgWdSK4QYQzJXAxFRHsh5TOkQ0ASviegNPIk1SApqaKzkCoE3I8F5RqpJI6F1ArFZEY5MYYR4T4KKDPyfIYEX9lGShOdqMr6BdFa0mmiQVWsmqYRKE2iuIpGxAtRTBYRcI1CopAPmlCmjMEUWWqjgkI6Cx0GN8ByeYUi0JJ6mdU5YQy0QkQp4VGiwUdzqsMNM1VcwSIGaSkc+riPj6jSA8bW/qvgmEgSgTYP/S+3mJMIcB/HZAa4gqlx6fcE5ALfdfRZCMZBK3eCb4YzD1SCj/sBYQoqWOkFMwYDISNcwfAjZsIH3NcyMV+9ECKC+7dYL2IjxpNoCtIOFpCEadyvL5eVDVgTRiOqy8ENIaAcUCjmKCJ8gSSohGmF5pQxNDWYzSoBH9Hc8SoWXMGvodBwixy+l0MfIAVEeiHSICOUKPCRFsjKIh1Kkcw2JxnFoeAwSUetIIgIZekSORy+BB2lzZLHRQbpki+nMfpBPJ3uu3x1p2pIBJv405X8glArGHgSmTgxPB3sn+EKPh0Nhpf29+BwfDY6HQ1xBe8fDQ4ORkN8tTSWSRTboVKVAllPgtldE6InJNB2Yktof+Bska2uQvjRIdGISECZMWQtIW3Cjk80VNG+kBHRfXR5eXnpHB87w+ELTl2RX8N1O45bd9zGT0hOIRByx95/IMvU1N+IphJyR+DYp8D81a4z8muCL7lCV7Gh4PrCwi28vCruPJ9K8CzU8vCXi6FASMvCZK0VkRfda2smRHkFCumTwWUoXJkR0xirjJWG65qfu6Evy7jgI0aVNqEiT1V5qsQV7AmugWujT+KYUc/mt9o3ZYzc3ocqpt/AM96NpcmGmqYQ1tl9tyyHH3proFktuP+Y1PRH81/rDPWHWXo4lnDzEM36fU0ySwfPVCnXMLPxZ6XbW1awFpqwcrF6Z2kEqbbjnax5LyvYJ7roKyIlMeuJaojUbr9Qv5xb0GtOp51mz/F90nJadeg4Pdfbc3y3CR0Ar0EgsFwLOazc4r/r7Xa70ez0Wt12uuU1SE7YZBeURMl6o9lsWSWTJMvFv/kC/mvEqkLa2FLYkqWKDbfRdNyG4zbP6m6/1e6361XXdT/jfK4m+YFuhx2joBLPA6WC5FFaAaEM/AdquEZDGo9wymePU5pRpUGCP8lOo+VK9VTJ7md/QiKRbI7zyLVHlAI98WyQKhv203j42oycylOlkl1r7ODVq2Gre7jfObp41z3pHg9H5+PXF6fd4cmni/Pm+8vm8Ozj6Hz/qPV+cNYafHzT/Hx0tH80aG/ht8Mjrlt1XVzcnYNUzby679QX3p09t+k2637Lqftuy2n1unvOtOPvOb7X7rTqwd5erwcFTvL5I7qNPWiA7zoBTDtOy2u5Tm/a6jpur9khvXa3VSeNDXfk4f+Iagsl9cnzgbSJT/bAbzutdps4rW6v4RAXwKl33G6nC64PU7tc07xbZumcTiXhGg2UokobnVBEYO9PpXqh1rHq12o3qT6J46onog3yF5ZsTl1pYIzICfF9CWrHXjt4/efgbfPPt83zd823+2+aH4+H+x/G744b74+PP78af2ieH551Rp9OPl6MhxeNt93WcaN5ejo+Kg4UQSS2HrOKApP06xaplwiYSew/2wblN/RRNvbu22BE6UkESpkcrYDrn1jbPM+sbv5oHsLmDR8Zi/mTjwhHFmZWbJiKRKfH5my9b8NZd18gweSikxzK3ym9/JMpHpgpsgv5s2/C9+OuSmPQOB1gNdQkpEoLuXj6nPwfIa+24bbRAnsjNVcrosExors22+etCWpj1Depd0ZcywVebhNPpbd/2/62eGy3Ai23fv8K9YmTRIdC0r/Af7mrEkgptuyE9PgtyVOmOzvrLys4C6vbSk7L4p1+BQO/Fxpt0FyjyMdpufWC5bsav9JwOjXN+1OzL+SU+j7wXz8v29mtATxAwPJQ4CWS6oWtDL8CIkEOEh3i/pcrc6OPQIfClJVnNkXFxHzCtWLBRIG8yUvLiWS4j7HRzA2PDdGUS9H8OqjE9B3cr2+8vThLazSmvGHcD1xnPqwgRWc8r4YTjkbjRruDYklviAZ0DQtT/cjKKYNs5kixpBIC8e0mNM9BegLK9uI4PfigIVXTRCqwdfwTRrSJImhwcogr2NBNUTaq9aprfJBEETGx0tbMy238Nh6e/I6oQgRpIRiaJpRpS1PIGeEZVGWKUxG5BjRN2PW6Q6AFImgmRRKb0okEj8bUfhA3tty4Hp2Dngt5Xd1a1v97QfzKv3LboDFDciRi4I4SifQAxVKYfZFWHqnKoJhys4jzOvMdc1lPJgRkzgPII9z0AwKRcD+vUweCMTFPK2axUFQLSUH1DQ4HfckOv7Xs1/ELTnLizEnOlHjXwP2r3/Jj/ozqMJmaI37tURZ+76fdqRWUBTLBg1Dj4RBQJmZZUR5IorRMPJ3IjKCZF71rTquPYBZIG7ueQy03sYvbHKYol30ymxBY5HghkVqVQi7I1bQEqJkjay17UcpnF403wCJkDVn8PsRMLPJmZPleS5SRu06mIDloUNWvJkyZzpD6EIxB3lCveJfMYJqSVc0KOSJwVCZWwYx6wJUN+XkAjIkXAmrYOJXGZ2OrX6vN5/MqsV+ttUxV1Y4OX4/ej0dOo+pWQx0xGydjoXREeMGwaTSiAWOo2GrciDS36yT4T9P2TtM2y34afuhazAi1lVo7PbdZlv2C11n2ypQclDYvb2+nRMEnyZZL8zrtDpjc61NFpqxQ7v/pXGzv625FdA2Ldav4hrAEbH6vPGa453Rqd4BaNYqfCO2lO7ElcL8/HeVTGq0lSFa93SfCedEGaAnOLW3ZX4v4gc3Mh0FeNVmfiHlHm7JsftMW6FN36+7GYsnYxe7lGsCVeZDUILAXi0p+AjdxK1UceB7ERdj3Lk0b15GDkakbkHtXiWt7lcj+MdbzT3xRsH33UpBCMH+Nr7aq3N6mF5XlciWffvqpRkYxlzZeuloul/8D/JOeXw==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List All Receivers"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/receivers"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Returns all receivers matching the request criteria. This endpoint supports pagination and filtering on receiver status, receiver attributes, and timestamp. Each payment has details on the receiver, high-level payments metrics, and wallets associated with the receiver.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"page","in":"query","description":"The page requested.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":1}},{"name":"page_limit","in":"query","description":"Define how many results will be returned in the response.","required":false,"style":"form","explode":true,"schema":{"type":"number","default":20}},{"name":"q","in":"query","description":"A search term used to query through the receiver phone_number, email, and ID.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"status","in":"query","description":"Exact match on the status of the receiver wallet.","required":false,"style":"form","explode":true,"schema":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"]},"example":"DRAFT"},{"name":"created_at_after","in":"query","description":"Only return receivers that are created after this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"created_at_before","in":"query","description":"Only return receivers that are created before this date. Format: YYYY-MM-DD","required":false,"style":"form","explode":true,"schema":{"type":"string"},"example":"2006-01-02"},{"name":"sort","in":"query","description":"Field used to sort receivers","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"created_at","enum":["created_at"]}},{"name":"direction","in":"query","description":"Direction for sorting receivers.","required":false,"style":"form","explode":true,"schema":{"type":"string","default":"asc","enum":["asc","desc"]}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"A paginated list of Receiver details","content":{"application/json":{"schema":{"type":"object","properties":{"pagination":{"type":"object","properties":{"next":{"type":"string","example":"?page=3&page_limit=2"},"prev":{"type":"string","example":"?page=1&page_limit=2"},"pages":{"type":"integer","example":8},"total":{"type":"integer","example":16}},"title":"Pagination"},"data":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}},"title":"ReceiverPagination"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-api-keys.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-api-keys.api.mdx
deleted file mode 100644
index 028bca8c37..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/list-api-keys.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: list-api-keys
-title: "List API Keys"
-description: "Retrieves all API keys created by the current user. The results are ordered by creation date in descending order (most recent first). API key values are not included in the response for security reasons."
-sidebar_label: "List API Keys"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV1Fv20YM/ivEPbWFbKdZtwe9ZW22Zi26oEnQhzQIzhJtXS3dqSQVxzP83weepERx0qTpFmCYX2zryI8feUd+p7URO2eTnpq9wwN4hys2Z4nJkTNytbjgTWo+opDDC2SwZQlqt8AVQ0ZoBXOYrkAKhKwhQi/QMNIYjgsEQm5KYbCEEChHao2jnwsecisIzoNGQ587P2/N4FkVWIAwU7yZI5bn4z4uXNiywRbUBwHns7LJMVcgaYPWwTPCLBAwZg05WQGh5eB5bBITaqQY/yA3qXnvWPYOD2Liiemd2aRrs7uzo183a3GVPXVFyYGbLEPmWVOWK5OYLHhBL+pq67p0WQw2+cLqvzacFVhZ/SWrGk1qLJFVPydY8eB5mH7BTExialLK4lpWLh/YsJDzc7O9YSfefW0QXI5e3MwhxWJodTr6ZpMYbyt8GOptU1k/IrS5nZYI6nQXWI1UOWYXPH9Hal2szXYw3QwIMxigwZys11MmAaRwPAxqyzIsMT939b8RtEODg0OweU7IjAyB4PXBm49A1s+R1Rkva0ercz27d1VvFqiyYlKjBiNxFd4q6b4iDDogzLar2XXWuZUfDPGpQD8EhaW96tdhgOnqOw4TI8GyCFf9vkW2qfMnIFtaFuigh1EexXgIsk1b184bfiLirKw3iREnJbZj453G1U9iXu28vD1ZTrxtpAjk/sL85hh5MXlx5+T4xoRAokB3Hny8FLLfMWNYrDRDO99UUySFqJDZzu84+m1meGmrusQBDfMhCNzI7JpFH+fVzssB8rZHi3zXLH2qaHGLfrq9Rb8Fmro8R/8k+3N3+a5jPqYMN7zUr1dCk56uza9oCWmvkcKkp2ebMy2HFEH1cI6RsNUlM7G1Gy1aaWSkCySO/g2VJjVGHXvcI02+zW+Ifj2Va6cNsN1Cf3w6js0SNUV3QRWrTS8BdnOPOSydFGA97B/t/vwL1OQudGoucKVq3qqY2es2MHrq8FfwAm2up3aj/2chsun68UiwLC3BG8fThhgrvWkclla07bWfTWI03Zbl7vjleEdr0FSVpZVJjV5v7sd4dvTm8Dk4BgsSQgnTxpUS0ww0t76jyqprlV0gTJtyAbVdKUp8amFOoalVHggzV7u4EC6wFd8+ukdZBlqMb5X2v0fxs//sj1XDNaSHUKMfcWgoQ6gpaK+AFFZ0uaUSPEioe4HcgkvA+naqZyFHyKyHqd5NGp9Hx0L/qKbrvZKwDuwkkENOlccITrnFm3Tfo3xQpFHdFWk0tdkCfX72rBCpOZ1M5k6KZjrOQjV5FMLzFGLyV1RWoDPEOq1wgdCZxaycn5FloSaThroE+1vXvXs6fkRmM4oj7J+k1kM8lNsSp9Db/nA2BZbVKCssCd9LeWA3EUKcVNb5Sffg3nweSuMtlhVEoMg/x7oMKz1eD2YCDavdopkieRTk8WcdU4JU8Z+zI6QLl+lc6tPqaI4DzSfRaBRmI+7MElO6DD3Hid8PwNpmBcJunFPtfFasdDJZLpdjG1cjWufKk/cHr/c/HO2Pdsc740KqMs7JOrBU1g+A4/X46t1wa8isr2Xwf/aW2MmW4KVM6tI6Hy+hWtd1p46n5kodzxJTBBZ9tl5PLeMJlZuNPv7aoOrF6VliLiw5fYeKkpv04qRyqjfS1OxlGdYqvpF6lMwtqb8h1L/vH5vE2Fsqu4gq2/1Q9H7JrwbY23rZUmivxt9wWa9bDd9sruzbpW96dCn21lrDs81m8zdb8Mig
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"List API Keys"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/api-keys"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieves all API keys created by the current user. The results are ordered by creation date in descending order (most recent first). API key values are not included in the response for security reasons.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"API keys retrieved successfully","content":{"application/json":{"schema":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/log-in.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/log-in.api.mdx
deleted file mode 100644
index 849fb937fd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/log-in.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: log-in
-title: "Log In"
-description: "Allows credentialed SDP users to log in to the SDP dashboard with a password. Note: all passwords must be at least 8 characters long and a combination of uppercase letters, lowercase letters, numbers, and symbols."
-sidebar_label: "Log In"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV1tT2zgU/isaPbWdXAjby+KnDZS2pkAoSQsNZagsn9hKZEmVZIzL5L/vHNmhoWVhuruzs7OzT9bl6Ds3+XxH19SzzNHojA5Ln4PygjMvtKLnHZqC41aYMI3oUEpdOcItpCjGJKRk/PKIlA6sI14TqTMiFI58DmErZS5PNLMpqYTPCSOGOVdpm/bIofYQESblzZojRek8SYAwTyQw58mvhOfMMu5Rg9QqI0ylhBGui0SoYCfRM1IaA5YzB0SCR9kOkbr6fkmVRRIGiOHqItHS9WiHagM2QMUpjei+zmJFO9TClxKc39ZpTaNryrXyoDwOn/Sf4MfxHAqGIxQVFlIMIhRMSNqhK6cwjL42QCOqkzlwj3sWVXoBDk83J6LrlZjzVqiMLtcw7tq0wJnxPGcXXi9A/SjzffomKEZm2hILO8Ojyc6bIblkUqTB9x45vlkNgEQ4snKMlEqCcyGtn1/G4+H2/u7F8W4r/5lwrWYiK5so4kEHPlwDW0KPLpcdClesMBLW/KVznatUw2847XFdrActokXtgFvwdLlcLjtrIZ4x6SCsOKOVa2K4ubGBn9sOj97SznremDGyvdz9udPqdhLvT9IfxPg711opCvVenrzmYiT2Xr3/Gg8ORexidfyM78TP44U5/bCzt9WDem/ANz/U8dy8iAu5iOdapKeHkouBme7ELi4++I8n0uH69GSQs5OrYfOtyo+bWz4WleDFlpueHoiR9C/i4lmenLxHpZP0dFtyNTV8c6uO1SCdjSsxPc2reK6vDud8MJp8rEeTd7/M3vWeTudb9fYpz7uifPXxVXfBL3bzN0dXc1OZC8gORvvJ6PJpMn07Ghy8uuTFbjZ9diBP3wwuBrPpLHt/xQ63+cFOenzw/OD1+MtbzavXavh/ZO6JDMbm6V03dpul5LipO3/f1QVrtb2zhMCVt8w9jOA88+W6XFNJEaIA51gGd/0Z3//2jRk0VqHorNGIo+umrJQ93dhYg785hmSjWAFE2xvioP+wrqDuqst1ChmobssU3USndRflaURx3KgC5YRWSLDXdAE1je492aGXTJY3CMtztMvnGkui0eFaGOZzGtG+1JlAonJgL8E2CkqLlTUcc8BLK3w9xmvS5HEbmAWLNL+WL2bEW6h/YIu9kwn6nwbCYLc6gw5xIlOw4nRFdsebz54TY8Ul80AWUCOrtoFAbdqKr01P0aECwXNgKd6fJc5nOlgjPOaOjj1IySx5KVxSWgcFKE+OJPMzbQsyPIoxRGBdY+Vmb9DbwBiURcEsBneCnce9GI/GL48eI0kx4rWWJCmF9MFNbTOmWlNDQ1OwBZCklAtiWI0oYZWRzOrSYONhgQsjwoa+BNv0Pa12Bb7SdtH7kYj/dSZ+Up/UJBcuqFREG1Bdp0vLgRirsSYQnzOP240pGru8AH8HXNNg4Qbec8KZwp5upkuVhoM5TrCXFCojFox2wmsrwEVoR5ecuQav33676VqQuqYNUjdhfAEqPX+Ue29c1O9nwudlgq1E/6cQHkckOH9jSo0NjWdCNR1PKxa8EmpmmfO25L60rYOYF/9QTns/4dnMhsr/V1xbQTzkWwUJWcn+aW9ykEUXG3Xv7jV5Ta7vLUC/YEL124V7/XnIjTcgi/BUaP6SFIzUNV6vBz0hpUO5RZmAVeDB9T5hmfJgCzeajcFeCo51aeVWa2ZP26wfhLp61nWtWIdKwUG5QEKrAmgYz4FshjrV1GfEivr9qqp6LOwGtPao6+/HO7uH493uZm+jl/tChjqJxb9gag14X2ckvFRuVZe1l8p/9sHWMpeHK983kgmFnUgI7XXLjme0YcfzDs2RNaMzen2dMAfvrVwucflLCcgXZ+fIuFawBNnn7HzZWZHTN77eaQLanaDabwSNz8BlZyU05ByMX9v+oWW7xeVHo/GEdhqSj65poVM8Y1mFL09WBRJfLn8HWQuC8g==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Log In"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/login"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows credentialed SDP users to log in to the SDP dashboard with a password. Note: all passwords must be at least 8 characters long and a combination of uppercase letters, lowercase letters, numbers, and symbols.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"required":["email","password"],"type":"object","properties":{"email":{"type":"string"},"password":{"type":"string"},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation. ReCAPTCHA token is required unless the `DISABLE_RECAPTCHA` configuration is set to true."}},"example":{"email":"johndoe@mail.com","password":"mysecret"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Invalid credentials","extras":{"status":400,"message":"Invalid username or password"}}},"example":{"error":"Invalid credentials","extras":{"status":400,"message":"Invalid username or password"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/organization.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/organization.tag.mdx
deleted file mode 100644
index 9ce2148264..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/organization.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: organization
-title: "Organization"
-description: "Organization"
-custom_edit_url: null
----
-
-
-
-Organization endpoints manage the process of getting and updating organizational profile information. The organization's profile has basic information set at the time of SDP deployment. It can be modified by the Owner. Organizations can also manage their preferences, like which assets to use, through these endpoints.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.api.mdx
deleted file mode 100644
index 68f52bd365..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/patch-organization-circle.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: patch-organization-circle
-title: "Circle Account Setup"
-description: "Updates the Circle configuration for the organization. Only account owners have permission to do this. Note: in the first time configuration, all fields are mandatory, but after it is been configured at least once, you can replace a single field at a time."
-sidebar_label: "Circle Account Setup"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV1Fz2zYM/is4PuzaO9nOctse/JYmuTXbrs3V6e0h9fUgCbJYU6RKgnE1n//7DpRsa2mWtFsf9jA/2DIJgPgA8AO0VYyroOa36rVfodV/IGtn1TJTJYXC6zb9nau3bYlMAbgmONe+MASFs5VeRZ80oHI+bbqRmSm8tqYDLAoXLYPbWPIBarwjaMk3OgTRZAelA651mMIrxzQHbZOpSvvAwLq5d1YGaAxUmkwZAD1Bg7ZEdr7LII8MWDF50Aw6QE5kD9pUAjIYwsDgbEEZdC5CgRY8tQYLAoSg7cpQb12kMTkwVZlyLfXnX5Vqrq6Ri3ocsz4qKlOePkYK/MKVnZpv78Xxwdixg5wgphCXKlOFs0yWRRvb1ugiic0+BDGxVaGoqUF54q4lNVcu/0AFq0y1XpxkTaHX1e/X1I0EA3ttV+p+cm+OST27voI1dbDRXI+SFMTH69eLG/gOfr68AfZoQ0U+qF2mNmgM8XtdftlJVxfgqnEhbdAQQ+VdA5uaPPXJj7YMsNHGSGyChGMnnz6+2lOp5uwjpYXQOht60KcnJ18Y9SHeEGJRUAhVNKb7dsFvKARc0UMhoU/YtIae8KuHu8vUDw8heoElvOkL7dv5TN47/3QSL4hRmwCYu8gpWb3iTqCxx/DkSQnXIQyHg9WVvUOjS9C2jazG5tJ9fF85p+bHZ7ngh2rIhvUc/UEmRw+WqAzDFUML2jKtyA/R3WUqUBG95k7Nb7fqBaEnfxa5VvPb5W6ZqU+TwpW0IjsZ7vUkd2U3sdgIPHnu/SSb7kmyki7do5qZukMTDxbkoIa4dsIsrTCLRAzFCzUbM+qsSBUz6StGiff+Tq6hHBu9UXOVjO1BLSTzfXLH0A7pwVb/St1nGf7l9xuIgcrE6hi5JstDUWUQ9MpS2TMEWrhcnP74E7Re3yGTcIdw5RAeOc35fVPJlBbjNWGZEpApKdA3R7q8PFbEgbuORTiimf3iTkxWLgHSnK7UgskY9HChQx59oIYsw7VBrpxvhN4k9uRDD/R0+v30RMIYmwZ9NzDU4zaeLS6un0vpIbBzBvKoDadIjTOVSq7BNUEezRpa7MRKWkVYeRdbYUFPhW512nB31HfQ/emWeOP8evogif63XHxn39mbWod0pAXXkp0EF31B0HonDABcY9+Qkyup6bX7PnDPXAZoy7QhFyj155ygctGWSVG6gzPGbbRdSed2QbPzmsJc/JjAbejtzYbfSTkK0qQdgjTJsViTLZfPauY2zGezleY65tPCNbOvsvB8Dgn8wZVOGJ1R235eGsQSKm0rj4F9LDj6AeB+dHo0p9OvQFb51A/+DbS9iaewbSiHvew/RlOTaSZFjZ7Doy6P5GbsiWYNajsbFh7F8xSMl2QaSIaS/yW1xnVSXk8igSgTI6xjTt4SU5i+E6Zj8k14XS3I3+lCeGkPa3Bz6vxqloQmrpqEQSxTRhdkQ6LAPYe2WNQEp4mneooXW/PZbLPZTDHtJmuDapj9dnV++WpxOTmdnkxrbkyi2tYFbtCODO8nvmE6XxDH9j7XbI+jxf+vANm+azJ94llrUFvpQCkn26Fd36oxehnN/tKwl5mqXWCR225zDPTWm91Olj9Gkv5zu5TRwGvMpZvdLnfZvl8eB4vzPiWTG/HmOEl8Nvntsr3GWVFQy4/KjieQ67Ob85cq62cTmWVdKUoeN/J6gxuZMuR9iPuJZ9uvbZVBu4pp6FW9USk8/GziWKeJY3gQWPst241cvD879EjkW3A9qLLd9vPMbneQ77f+VmOI7V5aErrc7XZ/Ai5DXfM=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Circle Account Setup"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/organization/circle-config"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the Circle configuration for the organization. Only account owners have permission to do this. Note: in the first time configuration, all fields are mandatory, but after it is been configured at least once, you can replace a single field at a time.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Circle configuration to be updated","content":{"application/json":{"schema":{"type":"object","properties":{"api_key":{"type":"string","description":"The Circle API key with permissions to POST & GET transfers"},"wallet_id":{"type":"string","description":"The ID of the Circle walet from where the funds will be sent"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Circle configuration updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string","example":"Circle configuration updated"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/payments.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/payments.tag.mdx
deleted file mode 100644
index e89ad4323c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/payments.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: payments
-title: "Payments"
-description: "Payments"
-custom_edit_url: null
----
-
-
-
-Endpoints related to payments. An SDP payment is an individual payment from an organization to a receiver. Each payment is part of a disbursement and occurs on the Stellar network. Granular payment status is stored in the SDP database and can be viewed in real-time on the SDP dashboard.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/profile.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/profile.tag.mdx
deleted file mode 100644
index 7f8a1db9f8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/profile.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: profile
-title: "Profile"
-description: "Profile"
-custom_edit_url: null
----
-
-
-
-Profiles endpoints manage the process of getting and updating individual profile information. Profile information is set when the account is created and can be updated by the user on the SDP dashboard Profile page. Note: profiles never refer to receivers of funds.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.api.mdx
deleted file mode 100644
index 5f4b0c1c4a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: provide-signed-challenge-transaction
-title: "Provide Signed Challenge Transaction"
-description: "Allows the wallet to post the signed SEP-10 challenge transaction. More information     [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the toml file under the  `WEB_AUTH_ENDPOINT ` variable."
-sidebar_label: "Provide Signed Challenge Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFmTo7YW/isq7ksm8QJ0u6ftqjx4bzw23jBeeqYSAbKRAQlLwrTp8n+/JUxv6VvTk+Q+5CE8sEhHR2fTOd/hURFwx5XGvTJDO8wFgwJTonwrKR7iLsNx/tlQmmFIUw6Ej0AKwxAJICiIKRf5EMc7gjww707KmgpcX1KQHQKCQcKhK3lUwIgyBDDZUhblmwB53fuIoW8/+ULEvFGt7rDwE6fi0qjKBQpDyJ6e5ZhRQV0aVp2QOtUIcoFYFbmUn7hAUZWjuKyqmlqJvP88C/CpAiwfAUS8mGIiQMJC4EIiJZTiOYkAmIOY0SP2kAcwybURNArBFocIJMRDLB8Dvy+7rd+aC+vut67ZmYwN0wK/gyNkGDohqiglhcboYjzDUxrK5MJznhum/SSP9WIPpaQwdEgQFy3qnZTGo+JSIhAR8vXn6s/ywV0fRVC+iVOMlIZCnT1yhVJSYia3ExjxfPYV2xdiLhgmO+V8LinoAUZxiN7RKk157eStY+BZorfY4YDG7kS/nSzbQee6U5vt9/zgf9bu0uOht/qld22vJHl/2nx7dfP7KmMLN59qbcdiq/1hvnV57bZumX8w4Wd1tt5Dk/S05qyrt51hTcWz+t1kNbeqWyMamPn6tpSv01JhP8zgyvS9vp157Vq2XtaCdVS/Hka9ZK37RxfXfCcyqXM1CBxd8+HyOlnrdWH0e5rX3z3vP+17/XEvNKaRlsF+3F121+pQtQeL3iZx+3Y4Cx5sq7PWbVV8GdmtyXq1SRa23TL3LTpU6yvYrmsj3T56Qe162RuIudU8TvXFi6pHH/XsNN/OR1+62t2+TxZtM504q9so+9w+UDH3vzjNXx5G+p2zD29WqtWKuzGzxwt737wJD6OBtr/Rj+yBaFHvCg0yPoR1XvdndNu/anK8Dq4WOX9msOB4iJqqXQ+NjWuf2gtvD2/aOA0mKbdvW1vjur0Zn2ba+PD5xI/mYJmu1f617sUPZn080Q7ZtZdEtzDu6/7h+GAv90Fn+uuvyvks40ZGKGbIUxpbGHKUj/CYEn6JO11V5eNtpiiSgA+Jx30YyHzBAU9cF3G+TUJ5VF5FOozjELv5uanu+SV+fzjsaYB+IOAvVAo6DXyn7+IxHhiLzNBMbHCDzGpu27gxgnhltwf1CjoNMm9pSKK7qbWx57a/XnTt1XKxGVjdmj23vdY0G10trdls0bWhZfeWs25szLpiaasbON8PhlPNs6dBaJuLcL0Mat3p3OBGFKtwbtwY+65q9qeZuffwWjfSjeWe1noPb6IZ3vQX+qhv+xur5W86bjbSzb25t4NR1NVNa3c16uyyTb+HR/pUH1mbaNzZaSMrSEf7KR62B7F7NZJyU+9ulroZPQ71DV+vWimaaxiuBsFwOfPdu2ayicLTZjnwXd3Ov+UZGZ6kjKHvtY2bkbXIzI6hmVlQM9sp3qz81NjTB9MaqaNsqo6yQN1OK7fEad1ebW6O/daura3q7Mq8odN2z2plHWxYzW17APlsK9RM/dcl/0SXSKdcq9r7E7wgMBE+ZThD3v/vtCLGKPvwtBZUiizbz3X5Vc2S9ZpQAY4wxN7fXZyb4KHsUg/tECkX9bjsUO9UJjCSUsp3RW4iEOGYEgmVHpUAnZTGd1eWlCMMk2cO528lJULCpxIbSNgkzQOFrzSU6jtgoZQUjtgRsctmCQuVhpKz4MhNGBanubT5xawtBBlizUTyerYtjPEXJOV+69jB0gIJRx7YUgakjxERhTtLTxguxcIHkIDuXK/dgJjhIxQIBOgkE3dhlGYRHrAAMlgy9xH0EMtdIkFeLg0W0jHK/ALhQAdzJ2EcRYgIMAmhkFgQNCeGNBdi/CKlXtEqqrRBEkWQnQp/fp/HT/PO5JN0LwSC0hA4CQ5FriZlO0gKUbkErZGsSU4SBiCGJ8klH4Vgx2gSA7oFDLk4xvkEPRbw72l3gkRKWVB5Z9p/nohfyVdi+ZjnWxJAY0TKnCbMzc+GPKJA+DAHwBdRKAGC5uz/B7sSgMTLJ2TM5yDaQWBLE+LlC335IXsETHaAoZhyLCjDiDekHGVw/0c4770yUjkujFR2oBsg4v1QQ/BdDp8aIFf+WZQTkHkMYnJpYgqyXCtMtgxywRJXJKxQUPpFfOTTyp/QbMvyNPp3VHti8ZFuKXLAE+1f1sZHYVR2fcgE/67Ir+iqgiFUjSAm1WLgu/p8pMYdCiOQM8rl91Ac0pMMrw81AQmXdEHiIEaQQLzyVaYpgVjEx9s5Ykfsyrz0pFYhZoWyXTUnKtNtmRdkJSXELiI8rzBPCTCGro+AnuepS36WvBrVapqmFZjP5tyKpbw6NNpdc94t6xW14osozPOkLAQRJK8YF20juPSN4LlxBG87xze551Xn+G+b/mGbXlRIgR5ENQ4hJsq5cOFjUZHvlfcV+VtJ8WXVbtwrj48O5GjBwvNZDh8SJGvU/TdZ8S/byK9z6akgvuCF9sVNZUuK8AIQZLN/Lj0RNV0XxeLV9DvM9QZLTMZziRec4h9CRD25hsFU/l+AaQ4czuf/Aj5zNP4=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Provide Signed Challenge Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/WEB_AUTH_ENDPOINT"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to post the signed SEP-10 challenge transaction. More information     [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the toml file under the  `WEB_AUTH_ENDPOINT ` variable.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"transaction":{"type":"string"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAvheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3AsiYk3UAAABArIrkvqmA0V9lIZcVyCUdja6CiwkPwsV8BfI4CZOyR1Oq7ysvNJWwY0G42dpxN9OP1qz4dum8apG2hqvxVWjkDQ=="}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"SEP-10 handshake was successful.","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJHQTZVSVhYUEVXWUZJTE5VSVdBQzM3WTRRUEVaTVFWREpIREtWV0ZaSjJLQ1dVQklVNUlYWk5EQSIsImp0aSI6IjE0NGQzNjdiY2IwZTcyY2FiZmRiZGU2MGVhZTBhZDczM2NjNjVkMmE2NTg3MDgzZGFiM2Q2MTZmODg1MTkwMjQiLCJpc3MiOiJodHRwczovL2ZsYXBweS1iaXJkLWRhcHAuZmlyZWJhc2VhcHAuY29tLyIsImlhdCI6MTUzNDI1Nzk5NCwiZXhwIjoxNTM0MzQ0Mzk0fQ.8nbB83Z6vGBgC1X9r3N6oQCFTBzDiITAfCJasRft0z0"}},"example":{"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJHQTZVSVhYUEVXWUZJTE5VSVdBQzM3WTRRUEVaTVFWREpIREtWV0ZaSjJLQ1dVQklVNUlYWk5EQSIsImp0aSI6IjE0NGQzNjdiY2IwZTcyY2FiZmRiZGU2MGVhZTBhZDczM2NjNjVkMmE2NTg3MDgzZGFiM2Q2MTZmODg1MTkwMjQiLCJpc3MiOiJodHRwczovL2ZsYXBweS1iaXJkLWRhcHAuZmlyZWJhc2VhcHAuY29tLyIsImlhdCI6MTUzNDI1Nzk5NCwiZXhwIjoxNTM0MzQ0Mzk0fQ.8nbB83Z6vGBgC1X9r3N6oQCFTBzDiITAfCJasRft0z0"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"The provided transaction is not valid"}},"example":{"error":"The provided transaction is not valid"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/receivers.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/receivers.tag.mdx
deleted file mode 100644
index 64d048dffd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/receivers.tag.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-id: receivers
-title: "Receivers"
-description: "Receivers"
-custom_edit_url: null
----
-
-
-
-Endpoints related to receivers. A receiver is an individual receiving a payment in a disbursement. The receiver is tracked by phone number to reduce the need for personally identifiable information. Each receiver must be unique within the disbursement.
-
-Each receiver will have at least one wallet associated with them. The wallet public key will remain null until the receiver registers with a wallet provider and links the wallet to the SDP through SEP-24. Receivers must verify their identity through that process, which requires the SDP to store verification information on receivers like date of birth, national ID number, or personal PIN. This information can be updated by the organization through the receiver endpoints.
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/refresh-token.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/refresh-token.api.mdx
deleted file mode 100644
index 24512cebf9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/refresh-token.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: refresh-token
-title: "Refresh Token"
-description: "A user’s token expires after 15 minutes. This endpoint handles refreshing the user’s token without disrupting their experience. It is triggered within the 30-second window before the token expires."
-sidebar_label: "Refresh Token"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV+FS2zgQfhWNfrUzTkJSaAf/AwqtaSGUhAJJM4wsr20ltiQkOcbNZKavca93T3Ij2YEALVzvrjM3N/cnjqXdT7uftPvJC2xIorE/xjuFSYEbRolhguOJhyPQVDHpXn28gwoN6vdvv2lkxAw4ghvJFGhEYgMKdbdQznhhQLfRMGUaAY+kYNyglPAoA40UxAp0yniCTAoP0UpmUlEYFDGtCmkaK6bsMqAYcAptFBjENDKKJQkoiJwT4w7u1UZLAxXcDvJIlCiEWChwc/fibWMPCwnKpRlE2MendWBDa4U9rEBLwTVo7C9wb2PDPu5TcQqmUFwjgjiUiFAKukkDe5gKboAb60WkzBo+O1NtXRdY0xRyYv+ZSgL2sQinQA32sFQ2LMPqhWu4OzNtFOMJXi49DDcklxmsWWGoDtPwHWV9dnhw9jXoHrNAB/x0i+4Fr4OZvPi8d7jdhuqwS3ufq2Aq3wR5NgumgkUXxxllXTnaC3SQfzaX55m246PzbkrOb3bqZ1lc9rZNwEpG8209ujhi/cy8CfKtNDw/s4sOo4vdjPKRpL3tKuDdKB6UbHSRlsFU3BxPabc/vKz6w0+v4k/tzdF0u9q9oGmLFQeXB60ZvdpP35/cTGUpryA56n8M+/PNcPSh3z06mNN8PxltHWUX77tX3XgUJ2c35HiXHu1Fp0evj94Nrj8IWr7jO/8z8wQzlpvN753kXRKhU7guQJt/7uiCUkI9ProPG8pbMIRlGpHQ1r2t09rR7aNRRD+70vLBnjcL44DPScYixLgsrNMdXMwgi65iIbB/99/2FAXXBVMQYa8ZD4m6tQmJQhwgskWOQkCEI8YNJKActzW73cfsnnFSmFQo9tUB/1p6/zxtWBtiinU7XuQhOOZz0Jok8L3G8wOyj4VB99K8i2K1zuZGdw35ocevBHbYGmihmKmwP17gXSAKlBU77I8ny4n1N6mwOiCFqwJJ7BzuNHrVWjV2DWoOSjuUQmXYx9i6r9AHdvtqftfXuOWRSPYBqkdVcHg+tFIYoVgoF/ydBntIs4Q3MmcP3f6gt/UaScXmxACaQWW1jJPcwu80edfq7WFmwVMgkTuk9j0WLhpmLM14YCDLiEJvmQ4LpSEHbtBJRkwsVI52TgLsYZtuHWWv3W1vWA6KPCeqwj4epoCexngxeHvy0tYWQUaIDIUFy4xLU6iE8CZUV1M5mQEKi2yGJKksihslKFGikEjESAFlkrkJMQflusVqdQ6mFGrWfkTtvy/EL/wLd5cjuyRHQgJvaVEoCkgqYWsVmZS4S04diuDICAf/HTgPER65CSoiQJRw25xiUfDIOab2JctEaS9TCqTQzAjFQPs2jhYa6xqv0zxb0RpJLdmQ1AoJnQGPJi9SY6T2O52EmbQI21TknZ9CeOnXN8PbUCpkWyJhluEUUGPmsmI8VkQbVVBTqCZBuy/muT1t/0RmsXId+e+ktoJ4LrcSQrSy/cvZpJDlLZoSZfSTIa/ZdYwC6OSE8U4z8GQ+z6XxHrIcOSAXfwQyE9XqRv90rRXa2s2KEBQH+5nwxbYpAyrX/XgAas6o7UurtJow20IlHWfUEnFLN2YezhgFrp1erBqgJDQF1HN9qu7PFsvvdMqybBM369AaV935GOztHw/2W732Rjs1eeb6pBWBnPA14ObzAK2+D+41mcWdqv+nvpAa0TJwYzoyI4zby4FjddEI5BjfF8iJh1MroP4YLxYh0XCmsuXSDl8XYCVjPPHwnChGQitA48nSW+mTVdQZWFXZoRSkFeE5yYpaNR9clO4p9kl/MMQeJo+UduaUtvlj4VdTvFoDf6iZdQz2d+n9wGWxqHV8uby1r6d+6NHkuLK2TE6Wy+UfvFR/mQ==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Refresh Token"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/refresh-token"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-A user’s token expires after 15 minutes. This endpoint handles refreshing the user’s token without disrupting their experience. It is triggered within the 30-second window before the token expires.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns a new access token","content":{"application/json":{"schema":{"type":"object","properties":{"token":{"type":"string"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}},"example":{"token":"eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyIjp7ImlkIjoidXNlci1pZCIsImVtYWlsIjoiZW1haWxAZW1haWwuY29tIiwicm9sZXMiOlt7Im5hbWUiOiJTdXBlcnZpc29yIn1dfSwiZXhwIjoxNjc1OTYyOTQ3fQ.4Zj9yBXch-iuFYF-kc_EhHPxjpwp_egMOLbOv4bZKO1MFvcmEgZ5MlXH1_1fZfgUxaNBcMCdRM6MGSqKocwGnA"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/registration.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/registration.tag.mdx
deleted file mode 100644
index 65139164b3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/registration.tag.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-id: registration
-title: "Registration"
-description: "Registration"
-custom_edit_url: null
----
-
-
-
-The registration endpoints guide the process for a receiver to verify their identity and link their wallet address to an SDP. The registration process only needs to happen once per receiver to link their wallet. Only SDP-compatible wallet providers can facilitate the registration process. These endpoints must be supported and hit by the wallet providers after the receiver gets the initial invite. After the wallet address is successfully linked, the payment automatically begins.
-
-There are two parts to the registration flow. First, the wallet must authenticate and initiate a registration flow using the Anchor Platform Endpoints defined below. Note that these endpoints are hosted on a different host than the Stellar Disursement Platform.
-
-The second part of the registration flow is handled by the webview that is opened within the wallet application. This webview uses the endpoints defined in the Stellar Disbursement Platfrom Endpoints section to complete the registration process. The wallet application can chose not to use the webview and intstead integrate directly with the API.
-
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.api.mdx
deleted file mode 100644
index 2e74aaa6df..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: request-challenge-transaction
-title: "Request Challenge Transaction"
-description: "Allows the wallet to get the SEP-10 challenge transaction to be signed. More information [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the Get Stellar toml endpoint response under the `WEB_AUTH_ENDPOINT` variable."
-sidebar_label: "Request Challenge Transaction"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtzGrkS/isqnZekFmaA2EnM1j5w9xUTwNhex5XVzDSMQCMJSQPGLv/3LWkGfGPts9mcqj1V4YG5qKfv6v5ad9iQicbVK9yHCdVGEUMFx9cFHIEOFZXusYprjImlRiYGtCSMgUFGoIm9xIAGrV6xXEJhbFf4BJBRhGsS2m8tXQBI0wmHyEMnQgGifCxU4iShqxgUXL+LjZG66vsTauI08EKR+NoAY0Str0WphBGhYH7AROAnRBtQPoRCr7SBxNcgi6VSueQl0X82mrz30DAGBDySgnKDUsVQSLhV1eoZpAZRjaQSCxpBhCh39nTAoEEmFRmRsIfvFWgpuAaU8giUI/7jvFX/Vjsb7n9rdZu904Pu8A+0IIqSgIGHC1hIyJx6EOEq7sM8BW0aawWHD57CBSyJIgkYUDYid5iTBHAVkzAUKTe4gKkNxTwFtcLPA2TNbDAK3KBaRl9Ay5iGsbM3AERQ7kiU80PvOp7nvUdCoSS9gejh/Yl7b2KShTdnu6Q6Bm3jSVITAzc0JAbQkpo4ywJQC1CetVnBPKUKIlw1KoUC1mbFrCU27LiA4UYyEcFmNYwhIbh6h81KWjJtFOUTfH9f2PgggUS87QBL5RQ0hoSxvbOKbc1LD51ytkISVEKNsbEfI7KJ+jMXUY1SbdN3IyRJtbFeFWNklUY08tCpiUHlOqwkaEQUIC4M0qmUQhmInvpmTJj+Ic4JXYC+RSIhlL/uJbKOZtMRe6gLEK33aColoxChYIUIYzml9s/dhtc/MrDXllW2lbRdr5RK9vJU19MjXMCh4Aa4savEqhe6veRPtSW5eylCBFMI7V6Ryu48QzMBjyK/RZ8C5mCWQs2+SaK1jBXRsNXlGG5IIhm8YIlr9jexf80D2k8rdTWfw2nYq3zunTdmzZ3mbn861fP4U3l/uZi3L35p74wuLHnnS+3pr+X+L27VWeiW6uNTMy4/W69nt636ZxXPu+RTqX85JV3eLtf6rUojON4t0f7efu9iMPTHB8lh133fsPo16yXSYbfkohtHndFt1Ni9vTzfnV0mezvHSTu9rMSLkO7GQdIVwYfDWVApx+R8J72s7JmDTrscdSYb+V86Uee0zQ6+JOVb0pGt89Zl6bg0Ojxr/56GnRHrz25Gw+ZlZVQyRyejeu/y4vf0bDSqd6d1cVzauyCNvfJJZbSIZrs75+1DMxjWFl8qZw+mjmNoj5ZOXAxHrfL+tMPPGt1lL7j4nNx+asyFGcRHQe2Xm5PKfjBlHy9Kw7psSTU6PRtNax/Z/OSwPP1YWagbXk7aH+DwVh+TPb0X98W486E2+e03vD32eAjaoEGzjbrZKvoVDUAaSAJQqFIq7/5Mh5/p8DQdbELsbCtkB2OkRfIU9yyJRgnVmvKJ7cCULwijrkH8oIoHSgm1tdbBjVFEv81hjTu2FMJnuZ/LwnUSIZUhHA8/FrRhtb6zqMS2xgAQJNKs8P+GpeOagImFBV8TcEYSE+Mq9l/gNlzA2mGYDH2liuEqxrZXaQhTRc1qYH2fOacORIGqpZbXxj9E0iN42XQPz4cOP6CxUI/BExW8kCPjDEYRjlqDyu5HJBVdWHA1g5W1Ou/zVppQ9JbkcNH1+RhIBMpVI5tfThtqXFdeo5km1UGqNCS28fcYMTYNUa13gAvYmptpWfHKXsn6IE0SolY5pHqdx7tBs+fgEUFGCIaClDLjzBRqQniuqgONCZlZwM1mSJKV5ZJBSTRRIpUWRykIqXSIA4lFDq7X0vM96W1Fff8uFb/yr3wYU+1EciQk8KIWqQrBzhl2o2XImupcFTcjOfZb2BUQ4VGGYkUEayw/FimP3IexfbCzma0jCqTQ1AhFQVetHkV09XyKih45qShzJxUDEs6AR//VHPYqh/dV5IzfqLJCtp4RyrPhMSdzVlE+VkQblYYmVbmBNi7mrZh6f8OysXLl9J+Ytmbxlm1LCNCa9rutiYElxTAmyuhXVX5E5xsF4Fs47+cvXrXnLTP2gSXIMXL6RyCZWNn0etMSlLp2NksDUBwMaO+rLVMGVKJPx3Y+pKGtS2uzcjU9oSa+IyqKcVHnZAXMaAg8A+LrAihJGAOquDqV1WfLq+r7y+XSI27Vccs/1f7xQaPVHbSKFa/kxSZhrk5KoU1C+CPG+ViONnM5ejqYPyk6dw8t+ue5yHefi+Qt08CN8SWzg+t9HtO7vEVf4Zct+rqAY6GNXby7C4iGM8Xu7+3rbN61jTui2gp5mLD/Mnrv+vk8+x79q85PtvpmBqsnh0ELwlJwCKXwd2z+fzknecUH+WHQdzrgUdD/4WnIKyo+P5J50PXaPmTbAFevru8LawRnUzf7uBaGIB+H+MUcYLlsYG2nNcT3938CaiWJfQ==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Request Challenge Transaction"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/WEB_AUTH_ENDPOINT"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to get the SEP-10 challenge transaction to be signed. More information [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md#challenge). The endpoint url can change but is provided in the Get Stellar toml endpoint response under the `WEB_AUTH_ENDPOINT` variable.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"account","in":"query","description":"The Client Account, which can be a stellar account (G...) or muxed account (M...) that the Client wishes to authenticate with the Server..","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"memo","in":"query","description":"The memo to attach to the challenge transaction. Only permitted if a Stellar account (G...) is used. The memo must be of type id. Other memo types are not supported.","required":false,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"client_domain","in":"query","description":"a Client Domain. Need to be supplied by all Clients/Wallets.","required":true,"style":"form","explode":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"transaction":{"type":"string"},"network_passphrase":{"type":"string"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAfheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3Ag==","network_passphrase":"Test SDF Network ; September 2015"}},"example":{"transaction":"AAAAAgAAAADIiRu2BrqqeOcP28PWCkD4D5Rjjsqh71HwvqFX+F4VXAAAAGQAAAAAAAAAAAAAAAEAAAAAXzrUcQAAAABfOtf1AAAAAAAAAAEAAAABAAAAAEEB8rhqNa70RYjaNnF1ARE2CbL50iR9HPXST/fImJN1AAAACgAAADB0aGlzaXNhdGVzdC5zYW5kYm94LmFuY2hvci5hbmNob3Jkb21haW4uY29tIGF1dGgAAAABAAAAQGdGOFlIQm1zaGpEWEY0L0VJUFZucGVlRkxVTDY2V0tKMVBPYXZuUVVBNjBoL09XaC91M2Vvdk54WFJtSTAvQ2UAAAAAAAAAAfheFVwAAABAheKE1HjGnUCNwPbX8mz7CqotShKbA+xM2Hbjl6X0TBpEprVOUVjA6lqMJ1j62vrxn1mF3eJzsLa9s9hRofG3Ag==","network_passphrase":"Test SDF Network ; September 2015"}}}},"400":{"description":"If some information was missing or invalid.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"account":{"type":"string"}}}},"example":{"error":"Bad request.","extras":{"account":"account cannot be empty"}}},"example":{"error":"Bad request.","extras":{"account":"account cannot be empty"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/request-registration-url.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/request-registration-url.api.mdx
deleted file mode 100644
index d0f8b9136b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/request-registration-url.api.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-id: request-registration-url
-title: "Request Registration URL"
-description: "The deposit endpoint allows a wallet to get deposit information from an anchor,  so a user has all the information needed to initiate a deposit."
-sidebar_label: "Request Registration URL"
-hide_title: true
-hide_table_of_contents: true
-api: eJztV21v2zYQ/isH7sPaQbYyJ002A8Pg5WV12iVZnKRA06CgqLPFmSJV8mTVC/Lfh6PkxEm7ZC8YsAHzF1nS8eFzD+9N14LkLIjhpTjFmQ7kJWlnxVUicgzK6yreDsVZgZBj5YImQJtXTlsCaYxrAkhopDFIQA5mSLd22k6dLyMgTL0rQVqQVhXOJwDBgYQ6oIdCBkYCKvDeEouYY86g2mrSkhDkCrv/zr6zY2YQHBikEFe34BAqVHq6BJnnmpGkuYdLhaRoHncv60AQ6qyMhAm9VKQXaJaw0BIkVK6qK3AesMwwZ0KZdw2vbLTNXcP8MgSZGeS/K35wYlAGBFWgmsfdciSpDeaQO1WXaKllc1mgx6tnBVEVhmk601TUWV+5Mg2Exki/uvYq78gpZ9LMuCwtZSD0KSoXloGwTANWvY2NwVa/zL/oWPQGz/vvrEiEq7A92HEuhuIUP9QYaP3Az09fi0TgR0JvpdlzKojh9YMQONA2h9L59pSAeYtE1N6IofiH6IubRHgMlbMBI6PBxsanxEarsAKPH2rtMdwdLzmYamPA1ffj0VkOW8wqOUMoXCA+2OVaFPVFIpSzhJZ4x6/Sr/gSVIGl5H+0rFAMhct+QUUiEZVnkUm3PNu3t1aBvLYz8TCpRqaRywChTZ216Huv6kCuRP+eOb9vM6EfT0iWlWHIp6xZung2T5E4P339eQGAc77L7FC42uR8aYAKHYBXkbvTmXO4zZX7NFeBISvd757G6Jgv1dS45nuplKstfffjaPfNztHx0cXW5k9vxwcvd49f7f58OHo1OZyMJ5Px7sHF+eFgd3v/7fjNi52dzePzzZd721sXY3ZT5097eXbr15ehVZrLwngPps63Hq2qVgqNpiL3spEmBhQGuqdFw/FUB2yXjfdYhw81+la8lLy0gQ/G2btKSa6rBIEk1QHcNBqv4O9J9s1gWoSdwbfT7c282FhsiZv2l4gSqXCcwZULMeYkFWIo0rPT0dHkYP/0/WT/9CJeTjiV1qmEtPMvXQsckYiAfoGeG8B1l8ri5oofq9prWk443tuQ/gGlRz+qectbtWWlX+HyE7UP35yxQnlUV9ZUoCWtYuYlEPTMYh5V5o6wPxm82IbK6wVX+DkuWQ0rS4bn3ZzXv7ZNKRGawQuUOXrBgnC8RzaaonSTttbAng5Z7QNymYUTI4kTH0YnY5EIdrdlOeh/3d9gDeqylH7ZRcnjGM8meyfPQXO0k3MGslobim46P5O2oxr4wEs5R8hqM4dKLhklPpUw8447yhQ8Kl3p+MItuFat7W6RGufn/c8G8r+LIrfiM04F3tKCq9D2gqu9Qqi84/LYtlwdOircg121yoEHcAlIm8cXyuUISlpur1NX2zwuLPiG5w5tZ+DbmHZeYxgyjx5cPuw7+ZpIvaoTqZdJNUeb/6HG+yjC8yFE52+pLIHbhtS27UKdWfRK26mXgXytqPadg239eeJM+3/Cs6mPXevvuLaCeMq3BjNY2f5lbwo0ZU8V0lN4lPKaXUoeMS2ltmn34FF/nnLjJZoSIlDkn2Nl3JLD60lPoA5sN68z9BYJQztuEfoyHE8n6BdarXfBjmbf+VkajXpu2gudWSKMVmhDHBxWBbCSqkAYxDp1N2oN07Rpmr6MbyNatzSkr8e7+0eT/d6gv9EvqDSxTnK/KKVdA+5mQFgfAqGdAu/Vm+u7Iej/b4D/9DdA17EJP1JaGant2oTYDhKX4ncGCV69NkrEGIngsSXfjRNXieBJkpGurzMZ8Nybmxt+HOcjMby8SsRCes1K8d1NsurmPH/MkXvwSCmsGHkhTc2MefTmmeR2+jk5npyJm5vfAD7MREc=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Request Registration URL"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/TRANSFER_SERVER_SEP0024/transactions/deposit/interactive"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-The deposit endpoint allows a wallet to get deposit information from an anchor,  so a user has all the information needed to initiate a deposit.
-
-It also lets the anchor specify additional information that the user must submit interactively via a popup or embedded browser window to be able to deposit. Please check the detailed documentation [here](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#deposit-2).
-
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"An anchor requires the user to fill out information on a webpage hosted by the anchor.","content":{"*/*":{"schema":{"type":"object","properties":{"type":{"type":"string","description":"Always set to interactive_customer_info_needed.","example":"interactive_customer_info_needed"},"url":{"type":"string","description":"URL hosted by the anchor. The wallet should show this URL to the user as a popup.","example":"https://api.example.com/kycflow?account=GACW7NONV43MZIFHCOKCQJAKSJSISSICFVUJ2C6EZIW5773OU3HD64VI"},"id":{"type":"string","description":"The anchor's internal ID for this deposit / withdrawal request. The wallet will use this ID to query the /transaction endpoint to check status of the request.","example":"82fhs729f63dh0v4"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/reset-password.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/reset-password.api.mdx
deleted file mode 100644
index 52352d2902..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/reset-password.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: reset-password
-title: "Reset Rassword"
-description: "Allows an SDP user who has gone through the Forgot Password process to set their new password with a token sent via email."
-sidebar_label: "Reset Rassword"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVlFv2zYQ/isHPrWFZGXBtge9pU2HZRtao86whyQoTtJJYi2R7JGy4xr+78NRcmw3RYJuD5tfLInH7+6+493HrQrYeJXfqIshtGSCLjFoa9RdoiryJWsXX3N10XV27QENLC7nMHhiWLcWWvTQWEMQWrZD00JoCX6x3NgAc/R+bbkCx7Yk7yFY8BTERDMYWoPbW6x1aAEh2CUZ8GQCrDQC9ai7mUqUdcQxrqtK5YrJU9iDq0QxfR7Ih9e22qh8+1XcH8T44GiyhQoDqkSV1gQyQba9yl7Jny9b6lGexFQzVcKOO/bmKXyMkQpLYeNI5coWn6gMKlGOJdigyQvGw758u7f0gbVp1Nf8vjumo7YciRSa1e7U57NI15HEwVMlhOtKqlpvAGGFna6OqRBmJkLUTn7JUdKBBxpdO2v8mM752dljhuengH4opdj10HWbE4YF/sdvAbzGCj5MYZyUBJ3rpgOZffLWnNbnaeaJ2fLzZF1SQN15wMIO8WTCuHGXKLoPjP5ZT5E2usfedXTkWF2ZkW9t3CCbDnC1pq76WFur8sMzaA8P5CfT9wL5waZA6RmqYhsVJJ2oTaBGTshuqt59WtqKGjLpVNa0sNUmNdhL/PI8BkLGa2uk77dqSRuVP7kzUSvshgeE3V2iegqtlV50NhbNYWhVrrJ4BNKjbvHEK+LR08CdylXc76kcWIfNQqo5Fuw1IRPLGDqiHJ3+nTaPqvbbX9fjAZdGwZPJlYDXjaH9SDHwdnH+08/gWK8wECxpIwNlYkS8WdZfxpmXKC3gLWEVSZX32sZodJDiqkWgrkOGS+2LgT31MqnmHYbacg8X8yvhitiPUZ7PfpidCQdD3yMLy9ctwdMYLxaX85dyFmQY2g6KQXchpmm5QTOFGs9Aj0uCYuiW4HAjKPErQsN2cGBrYCq103HBrmicKHvvhsLa8nL2eHr870K8NbfmutU+ujRgHZnU24FLEmGRloTQYpDlMRRrINgI/w24BNBUcUEOPJRopJlqO5gqbmzlRbROmwaYnPU6WNbkc4kjhRs/4mXTf1odkZS6iaS0wHJJprp70YbgfJ5ljQ7tUMxK22ffhfAyh5j8QygbkAmJWhhuCSazmJU2NaMPPJRh4CnBvZQ8WdPZd2RWcxzQ/ya1PcRzua2pgL3tP86mpa5PyxY5+CdDPrLLAhNlPWqTTR+ezOe5NH6lrocIFOOvyHV2I8fr2Uxg8GK3HApiQ4H87FbGVCDu/ft6QbzSpcylfVpTmDPLTRaNUlunfjJLVKdLMj6q1H4AOixbgvM4p8b5LFh5lq3X6xnG1Yg2bfXZH1dv3r5bvE3PZ2ezNvRdnJOiAj2aI+Dx2vXhIAQnU2Z7UPn/9mI5yUyg+5C5DrUR4Y88bCdNu1FfadpdoloRvfxGbbcFevqTu91OPn8eSKb8zZ0IJmssRDNu7nbJXlIOcvtmTD+9Fv8HfZU76C7ZG12UJblwtPzoPnQixfP3i2uVjBqdb1VvK9nDuJZLK66j9O52fwOrz0ME
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Reset Rassword"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/reset-password"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows an SDP user who has gone through the Forgot Password process to set their new password with a token sent via email.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Reset password request data","content":{"*/*":{"schema":{"required":["password","reset_token"],"type":"object","properties":{"password":{"type":"string","description":"New password for the user"},"reset_token":{"type":"string","description":"Token used to identify a valid password reset request"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Password reset successfully","content":{}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.api.mdx
deleted file mode 100644
index 944b1bb6fb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-a-disbursement
-title: "Retrieve a Disbursement"
-description: "Fetches information on a specific disbursement by  `id `."
-sidebar_label: "Retrieve a Disbursement"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWVtz27gO/iscvmw7I9nyLU795sbONmfTJBu77XTbjEuLkM2NRKok5dTr0X8/A0p25Ni5tE13zpwXX0Tgw4UgAEIratnM0N4nOhBmmmkDCUhr6JVHOZhQi9QKJWmPHoMN52CIkJHSCcOnREnCiEkhFJEICa8AkOmSkC+Cky816lGVgnYcJ5z26CVYLWAB/apE6tGUaZaABY3qrKhkCdAeFZx6VKAGKbNzeletkwFREbFzIF+qcE6shq+Z0MBpz+oMPGrsMkZII5I0BupR+JbGigPtRSw2SBDOIWG0t6J2mTpKq4Wc0Ty/QjSTKmnA4HozCPBrW5eqAoSDZSI21KOhkhYt7K0oS9NYhM4V9b8NMq12harp3xA6h2h0nBWFSMF3FbvrjfEcSCbF1wyI4CCtiATotYP4trvhG3Nu6NGDxivODjtd/7Db7PjtsHPov2q1uB82mgFrdw4hiDo098odeYoOSPmo2C13nSF2jl4OQSxATzTMhLFF2EwSMIbNYGIhSWNmn6hFmBmrErJmIpkBTqwiBiQnQi6EdegGn63lmhpB1i8cIpbF9gspRRNh5G+WaLCZlsBr5EQ668rl3wwpt5kI+5shqTJGTGNAaMa5I41UHKsbIWe3Gi2YFmwag+mR1ap2rmdMin+cUuiPPCc3cxHOiTAOoLruHIYyIzHLNHDCJEeMy4rbToW8vosRC3lNZiDxQALHYzoaXGycYpUjWjuDvBCShMwAsXNhEEIqS1INxhm65QGvMJxlVmF2CFkcLwlLU5ActbOOFiR/WdsKgo8qI3O2AMJIypYuFG6YsOilSGmyVBmJtEr2u6dGjmIRXt9jt9tVfAq6VoRWJaJwt1hoJ0UU7UYTyCzBrDh82z85pR69eHN+NpycvXv7enhJveLxpH82mHzon54Ox5P+YHA5HI3uUO6juPKoFdYZX1X6qFBojHrkHr1hcQz2R7PCrX87jLNXwDt+u9Nhfrt72PRZAOA3DoLuQRcCDtPGQ2f7Fum9mGomLekbI4xFnrlKIGWzR/jm1qamV68vCn6WprVQJchvIJ00gkkYC5B2wlXChHwYi6XC57Co7WJxgHSCwT25L4k/rlPd8BThES/UgAdkwuw+pKIE0h7lzIJvRQJb8M2g2fKDrt9qjJtBrxP02p3aQfvwLwTOUv4rgPPbqPpQhE7uUWbMc8RQFDEI29OW3z6YBn6bT9s+a4dt/yBsdYLDoNPtBq4+hK6WPpaZ+6gUcbRVIe9GgyMEEcZkoJ8KU1BjitVgzBbg769fD9rdk+OD0w9/dC+6bwfD96OjD5fdwcW7D+9bZx9bg/Gfw/fHp+2z/rjd//NN66/T0+PTfueZdr/pB61xA3eo12k8187vgnKI4SdBD0rQTgma76ulIwtxzDRxIUU2gbSOObcb7kxbZjPzUEYdXPaPx9Sjl8P+4CP16GjcvxwPB5g5++9G7sfR+duL0yE+rCTLarswKqTkHl2AxuazSOqRgHh/LK9l98fDyfnx5PXJ5fgN9ejHYf9y8vb8zP25ODmjHj3rj0/Oz/qnk5PBOt1XlHhfEXfspG1snsyFsUovK/KZ1myJ7auFxDx+DjMDevLYYWxFrU5j+gp84EHkt4OI+azVaPuNdrfTnbabnBUJ/d/eCAwuY1mSPltw5w+JfFM4eyitXtKnUCJRJGKYPF7pqh2rH8HUD1o+qlgLzXPVhn8pO1hlWTwpG6tqMAhpYQZ6t21GBiKzZFrcGzasFWmNYAd5YsoLznfCmywMwZgoi/dKOtwVFDERA/8BUQXjfoN2xWjAZgR9//2SNrz3CmOJyrDjKePsiRc7pyIpeDe3Kk6MIhHTW+FwGAS1ILgNgILnB6RYRaa3Nzi+JaQRbKSwBWi8nn2PnJJnLSkFvXbXXSlOyD1HnOY5LrWDxu51/J1kmZ0rLf5xmj/TNRy0VnvakxyVtpo9Ic3vZOYidBCivEvtm0DkecUtGzXombJky8xbLdZy2kGjgnyX41cCF1vT2t2aY6WngnOQv35f9lt3q8ATCAoz2rtmoMXHKpP/3+EVlRbuC4B2NQC2Bjpyw/mLsR28gTDTwi7d5PA1MA26n9k57X26wtldAnaucPY4g2LSiEu0Xi30pr4SPKcIpRfrGWSmY9qjFCHWEka4kYWnq3Jue75U/AHLnZT3nw/jYv6EUw08JTidK2LEI0bMJHByI+ycMEmGo2bngKRaLHBGdA1LHJmU49B+ecAc53oyOgfGcYfx+iQj5bQpk+W6b9/y30XMLHYUpH9xQl0PbQotm7VGLUAfZEnCsJXd6v33Y7wYDS5e4myIEatUTKaZiK0zU1UGNm7IlrBrINMsvt5URjcfIzOtsrQonaFIhVtQOH+yFekS7I3S17W91eR/S8XP8rMclxMzJolKQfpGZToEkmqFp5bYOcPba6mKksSqdD0xvQPnudkeLuClmYRMYlF28e8Yt0aLGlJlhFVagOmhHj75ZAq8evntb/W3aekkf8rCa5D86sV6ODITdp5Ni8HI9yC87BFn/EaVpZuNMiGLEWRJ5qwSMtLMWJ2FNtOlgbgv9rE9rX2HZZF2uflnTFtDPGbbDUzJmvaHrZlDnPjhnGlrHlS5Qle3GqCOfWe9fPCgPY+Z8QbihDggpz+HNFZLN7l+9KxlBumusyloCRZM7TOmKQs6MefRCPRChNUJXKlmTelZ3RH5KvJNSebRWIQgjSsb6wSYsnAOpOnyVJGfEatXr9/c3NSYW3VoJaupn54cDc9GQ79ZC2pzm8QuT6bK2ITJCvD6tRRh5M6Lqa10s7qt9D/1TqwsFxa+2Xoa4+QzL+1ZlfXp09ZFFC8RPcHxIj5XxuLyajVlBt7pOM/x8dcMMGV/uvLo+r2CK2JcGPzNN6+57rXnxWX5xuwleei92l7V1+VPYu1bsDjDf9Sj17As3uLlVzgyLioVqlUs9MMQUlth2Wmetur370OcWLCdknvtSm75A9H3qnO3eBYq4Gfu3cOyWhUFPc839MXSvRyliRvL0YI8z/8L0ysX1w==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Disbursement"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/disbursements/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches information on a specific disbursement by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Disbursement details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","example":"619da857-8725-4c58-933d-c120a458e0f5"},"name":{"type":"string","description":"The name of the disbursement","example":"Disbursement Name"},"receiver_registration_message_template":{"type":"string","description":"The custom template used to send invitations to receivers. The `default` message isn't returned. In the message's content it's possible to add the following template variables: {{.OrganizationName}} which is the Organization Name configured and {{.RegistrationLink}} which is the link generated by SDP to send to the receiver (in case this is not present in the message, it's automatically appended at the end).","example":"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register."},"registration_contact_type":{"type":"string","enum":["EMAIL","PHONE_NUMBER","EMAIL_AND_WALLET_ADDRESS","PHONE_NUMBER_AND_WALLET_ADDRESS"],"title":"RegistrationContactType"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"},"sep_10_client_domain":{"type":"string","example":"api-dev.vibrantapp.com"},"deep_link_schema":{"type":"string","example":"https://vibrantapp.com/sdp-dev"},"created_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-07-31T20:50:45.648Z"}},"title":"Wallet"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"status_history":{"type":"array","items":{"type":"object","properties":{"user_id":{"type":"string","example":"3f351b9e-ed0f-40fa-a314-14757b42dab1"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"DisbursementStatusHistoryEntry"},"title":"DisbursementStatusHistory"},"file_name":{"type":"string","example":"disbursement-feb-03-2023.csv"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"total_payments":{"type":"integer","description":"Total number of payments","example":10},"total_payments_sent":{"type":"integer","description":"Total number of successful payments","example":8},"total_payments_failed":{"type":"integer","description":"Total number of failed payments","example":1},"total_payments_remaining":{"type":"integer","description":"Total number of remaining payments","example":1},"amount_disbursed":{"type":"string","description":"The total amount disbursed so far","example":"800.00"},"total_amount":{"type":"string","description":"The total amount to be disbursed","example":"1000.00"},"average_amount":{"type":"string","description":"The average amount per payment","example":"100.00"}},"title":"Disbursement"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx
deleted file mode 100644
index 550a16f2b8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-a-payment
-title: "Retrieve a Payment"
-description: "Fetches detailed information on a specific payment by  `id `."
-sidebar_label: "Retrieve a Payment"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWVlz27oO/iscPrUzlq3V25sbO2laJ01jJzmnaaalRMjiibaSVFJfj//7HVKSl9hZus3cc19ahwTA7wNBgIQWWJKZwP1rfEbmCaRS4JsGpiACznLJshT38SHIIAKBKEjCYqCIpWHGE6KmUZYigkQOAQtZgPLSCPLnCH1lFH1t4gbOcuBa+JjiPj4HyRncwaBaEDdwTjhJQAJXQBY4JQngPmYUNzBTAHIiI/wQ1fEQZSGSEaCvlSW9GIdvBeNAcV/yAhpYyHmsrAmW5DHgBobveZxRwP2QxEIJBBEkBPcXWM5zLSk5S2d4ubxR1kSepQKEmrdNU/23DaNau3KOwA0cZKlUvPoLTPI8ZoHm3vpHKPnF7nqZ/w8E2g1ceUqycjVGdzEp9ETz6GNKQ9sOPc9wbK9nuF3bNogLthGAaTmO2+t1QhcvG5gkWVGieWhrm8g0AlTK1n7NVxu0XtUyzaZpKrtCQhwT/kVykgoSKCtf9mPeXWe9dxvaiKV6aFIaRinI+4zfNtGxRAFJkQ+oEECRZJlSC243QT6ijArB0hm6rofHxM84kRmf37yKpMxFv9WKV2PNilMz47PW6wbK+Epz9F1tzVqplgQ93nrd3PKS6TtOj1pBt0cdy7W6bb9ruZ3AJqEb9EgPqOf71A9oh1DSpZbTbTtOz+y03Z6vXBswHsRQejYE/kXFNAj5YvceaH1U66NKHx0PtTOZQFkaz1HOQSjX3UeQbvnyngiUEAqV90pz2ww7Lml3/TYxnLDdMVzb9Q2/65sGeD2HWD3acdvOZpSscsBeElqQyEK8jF8puydM0yJRqWx4Pjic4gY+Hw2Gf+MGPhudDo9Pj9SvwcVkNMQNPLk4OBhNJriBDwfHYz10MDg9GKmfNw0smdQ0q9M9KcGtYH6JmFABswGXcE7mO2gHKSKzGYcZkUBRzIQ+XAlIQokkqDz6AqmUQViqnC1X/EAgktLylLAEhCRJrrTr7RIrRwQRSWcgUBYEBedA1VYxCYl4Psv8u9yegBBkBnsDaOWjfWTKeqWyJpFgKNGtaLZN2zFM2zCdqWX2Xa/vWZ/wcvkIoLfl5o9Syef4GSE1T5nwCy4gga08/EN5f3c3ipR9KwAxCqlkIQNeb8zWchvUi0JX1DXrwLN8YlHP8GzqGK5lhwbxeoHRhtCxqdcjvqvPcFmPX4JJST4CY6NwbUwY/xQpGHbv6QzwWIBNpoPzqQ6iVYAdfDg5G4+m2+E03FhxHVMBB3Uqv5AXFkctr+rU1ml8yuNPBVvbcMypafVtu+91ml3H6nW8TwpWkdMfghUTIVGp9PuRdZuO1fasB6dh059jJkFfM4SAn47uNYQwJBC4vmO4bd80XOq7BnED12gHjmd2Ta/TMT29efoK95x/BgoU0rKbi1xMhgfKCBOiAP5SM6U0IpRyEGLL4NGbN0O3c3zYHl+975x1Toajy8nB1XlneHZxdemc/u0Mpx9Hl4dj93QwdQcf3zqfxuPD8cB7Pgx/KnE9F0Q/aZRCDL9otF0Z9dYpdjei68uaDim0CqQ6+vRuKDwcAmB3wL/ckzj+HcHXNR3TsahrWNR0Dbfb6Rl+m/YMGnht1wp7vW4XNhf+9RVNuwc2UNMIwW8bbuCaRtd3O4bZddqk63Vci9hbR++8Wro+dr+LukeovpcarucRw+10bYOYAIbVNjvtDpgUfOupWrC2dMl8TlKJBkIwofcpyhLI95btTb36Zn1X6pM8bwZZskX+SpOtqddXy/pAPmn96OCvwTvnr3fO5Xvn3eFb5+PJ8PDD5P2JfXpy8unN5INzeTxtjy7OPl5Nhlf2u457Yjvn55Px8yf0yXPTNE3zBQfyZTZ+vECej46OJ9PRuS6Nh+PB0dF2YayjSZSerWvjnnjbdv2/JWftXs7wcqlGXdPafcpfpKSQUcbZf4D+vnc8cJ7tqTFLhV5y8jN39LRIfODKxOMXYk1z5Z8VDHyaSbRFc42iXsc1rQ3LDzX+pOFya5zdrTnMuM8ohfTP78t+dmsALxAoabi7NBTjw6xI/7/DK6wY7gsAdzMA6t5ZulL6c2a1ZQFBwZmc6zbjGyAc+KCQEe5f36huXwIyylSPcgZlW1JN4Vb10hWtBaNLrKzwu7pXWfAY9zFW2rXxidq50rWbS6w7BTl7D7utgndX07K/FWZcHwv1riuDooEEm6VA0T2TESIpGk1sr41yzu7Urf8W5urFX7VNB9WJ0pp1BzUCQtWWqktvGmYaTZUY69vW5qUencVEqoyLBmfHuIEV3RKl3bSapvJBkSRENUC2bmz7bbyaDM9eq64TQTLLYuQXLJaaZsZnJK2gCiQzlJBbQH4R39btBT1K0IxnhX7UcAhYzvREdgd8b8Nw7zPpfwvi5/RzOo2Y0EumKMshNURW8ABQzjN1TJGMiG7VlVDUszNbPesemGusGkXqqVM3S3Xoa8VI/RHH2b1qMHHIM8FkxhmIvsJhoOvqKlV3NY2tJ3peOcnwSXALKV03QWdMRoWvrmmtH7Lwuo80+RWUed0BExpsJaZZsTTkREheBLLgFUG1L/K5PW3+ALOQ62T8K9RqE89xuwcf1bI/zSaCODGCiHApnoS8IdeSHKCVEJa2qoEn+TxH4y3ECdKGNH4KeZzN6/7l02etbCrfFj7wFCSI5meVpiTwRHwIJ8DvWLD5HtjsyWshIwsNUYk1cMwCSIUuFnUCzEkQAbJ1nirzs7LVb7Xu7++bRM9qa5WqaI2PD0ank5FhN81mJJNY58k8EzIh6Ybh+ssVImj97Wor0yzWVf2Xv5pV1ULCd9nKY8JSfUdWdBZVZbrGdQbCDdxnVN3so0xINbNY+ETABY+XSzX8rQCVrK9vGviOcEZ8lfqvF6oXp37T1dewR+m8Oq8+rL1Gj3x52wu4rnmpKnh3JC7UX7iBb2FefuJb3qgXYlmeFKJyYhAEkMsNlZ0r0la9PhqpVw/ZqbO3us5WP5T1vXAeVswSgvp32XhEZbEoq/hyuZIvpx7VqCiumCsGy+Xyv38J9VY=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Payment"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/payments/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches detailed information on a specific payment by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Payment`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Payment details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"ddf22f55-3259-4822-a4e2-ce01334997f4"},"amount":{"type":"string","description":"The amount of the payment","example":"100.00"},"stellar_transaction_id":{"type":"string","description":"The ID of the transaction in the Stellar network. It can be used tio track the payment in the Stellar network using [Stellar Laboratory](https://laboratory.stellar.org/), or [StellarExpert](https://stellar.expert/).","example":"0b339d1c89d314186b8147c2af4c9a9ed5bbdbcd7ada8d138633907649b"},"circle_transfer_request_id":{"type":"string","description":"The Circle transfer request ID. It is only present when the payment was made using Circle.","example":"74a68b6a-3f67-424b-b8b0-e593a19d7463"},"stellar_operation_id":{"type":"string"},"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_history":{"type":"array","description":"An aggregated list of metadata objects containing the statuses and the timestamp of when these status changes occurred.","items":{"type":"object","properties":{"status":{"type":"string","description":"The status of the payment","enum":["DRAFT","READY","PENDING","PAUSED","SUCCESS","FAILED","CANCELED"],"title":"PaymentStatus"},"status_message":{"type":"string"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"PaymentStatusHistoryEntry"},"title":"PaymentStatusHistory"},"disbursement":{"type":"object","properties":{"id":{"type":"string","description":"The unique identifier of the disbursement","format":"uuid","example":"c51ba1d5-52d3-412f-a59c-6ef32d59ab43"},"name":{"type":"string","description":"The name of the disbursement","example":"disbursement-june-29"},"status":{"type":"string","enum":["DRAFT","READY","STARTED","PAUSED","COMPLETED"],"title":"DisbursementStatus"},"created_at":{"type":"string","description":"The creation timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:57.831975Z"},"updated_at":{"type":"string","description":"The last update timestamp of the disbursement","format":"date-time","example":"2023-06-30T01:22:58.316511Z"}},"title":"DisbursementLite"},"asset":{"type":"object","properties":{"id":{"type":"string","example":"ffaec4b3-46b0-4db4-a4c4-6c3508057705"},"code":{"type":"string","description":"Asset code","example":"USDC"},"issuer":{"type":"string","description":"Asset issuer address","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"deleted_at":{"type":"string","format":"date-time","example":"2023-06-03T10:55:51Z"}},"description":"The Stellar asset object","title":"Asset"},"receiver_wallet":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"}},"title":"ReceiverWalletLite"},"created_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2023-02-03T10:45:51Z"}},"title":"Payment"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Payment not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.api.mdx
deleted file mode 100644
index eba9efc42a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-a-receiver
-title: "Retrieve a Receiver"
-description: "Fetches detailed information on a specific receiver by  `id `, including all associated wallets."
-sidebar_label: "Retrieve a Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtz27gO/iscPrWzli1b8iV+Wrd20rRJmsa57DbNuJQIW2wkUktSSX08/u9noEvqxE7ctN2dnTPnxbJEXD6AIABiQS2bGdq/pCcQgrgBbehVjXIwoRapFUrSPt0FG0ZgCAfLRAycCDlVOmG4TJQkjJgUQjEVIdGlFBLMCfksOPlcI0KGccaFnBEWx4QZo0LBLHByy+IYrKnTGlUp6FzePqd9egJWC7iBQQWK1mjKNEvAIsD+5YJKlgDtU8FpjQoEmTIb0YfI94dETYmNgHyuRH1GdRr+yoQGTvtWZ1Cjxs5jFGdEksZAaxS+prHiQPtTFhskCCNIGO0vqJ2nOaXVQs7ocnmF0kyqpAGD6y3Xxcd9HJVyMsxdaGiNhkpakBZpWZrGIszNb3wxyLBYV6iCLxBadIRGZ1lRqBN8HRTCZ7khfTrteUHQ8XoO58x3/CZ0nJ4b7jjc9aADELYYTOmyRtNISZjILAlAPy3xt2a73W55nZ7fbSMnfLWgJYsn26BkRjdbnufnTAkT8dPkX7iC35GsrvQMeUINGDYTZp9mbLktz3FbjuudNt2+3+63m3XXdT+iDKssiycpmycgrdkiBxlMFoZgzDR7Ftc0PyffyeEih0aPSCFnz2OaCWNBA5+UZ+lppmbBlMcin7BEZff1MK3ZHA+UhcRsjz1mDNhJmJ+Tp9SejYevUXNBL4zJtsXY3qtXQ7+7v9s5uHjXPe4eDkfn49cXJ93h8dnFuXf0pzc8/TA63z3wjwan/uDDG+/jwcHuwaC9wb4tHnHduuvSJYaGsPmnQcGGn9ad+kwPbTsSPddzvSb3nSZ3fcfvdXecoMN3HB62O35zurPT68GKTfrnNbqtHWgBd50pBB3HD33X6QV+13F7Xof12l2/yVr33FGlrgNhcyiFT34eSJtxtgO87fjtNnP8bq/lMBfAaXbcbqcLLocgD9ci0T8l6VwEmklLBsYIY5EnUgmkbLaFL7I2Nf1G46bgZ2laD1Vyz/iL3NjKdGMhjpmeMM41mC1nbe/1H4O33h9vvfN33tvdN96Hw+Hu+/G7w9bR4eHHV+P33vn+aWd0dvzhYjy8aL3t+oct7+RkfLCqKIFEbag59wkmxeoGql+RMLOU/7QMIW/Es2TsrMuImbGTBIxhM5gYkPYRaffrrhUJGMuSlNxGIPNG4K5DQYnVGydMkhxm0dSwQGWW2EiYsknZiLPp/oICU5FOKij/pvLy/0rxnZXCWGazzT6VWYL99fBksHtKa/RkNBj+mT/39seno5PRkNbo7sFgb280xNb7Yd41RQ4aFwruVE0iYazS8x/fk38Q8t0x3KStuErQPsVE4yDptsP2cWOBuqf1TeGdkbR6TpebyAvqzWv4dVmjvttcb+XPJMtspLT4D/Bf18aD1mpDpBfttWY/sp1lL7+s0TJtbrq9LJcrvr6DQY+UJffM/Iai0uO7zRXJDzn+TsHF1njrW7OrdCA4B/n378tm674B+A6Cwgx/3Qy0eFdl8n8ivB4Pg2lp4qYI8Fcj4ASMynQIRN5xLUvRBsJMCzvPRwKvgGnQg8xGtH95hRfzBGykcKAwyyt4PiLo00bVApjGQvAlRTH6phosZDqmfUqRvZI+Ri8XbljV8S3xpuIdzNeaj7cXpyQzwMlU6TyEQdpyA2vEiJnEEYiwEfYeo3Gr3SGpFjfMArmGOU4pyhnHoIz+nLMad0TAeJ6o8H1adIllFhsXzSEZChNk2gCWe3IcM4uZlgyO92mNorkFyla9WXfRB1mSMKwn9DQC8rSMF+Ph8UsiDGHEKhWTIBOxzc1UesZkCdUQq0jCroEEWXxNqsYDvzIy0ypLcTijIRSpyBcUtmV2RbsEe6v0dX3Ntf8+iJ/kJ3mK/SKqlESlIJ0ybFOt8EgRGzGLywUUJYlVaTWeeiCuRpjk+QL2TCRkkgRQxH7OGOFLHKtbnKppSJURVmkBpo84HHJZXhAa5dPhK05y0tJJTsDCa5D86kV1FZoJG2UBXoMaz5Lwsk9y4++gzAlmLibQwxGQkiy3SsipZsbqLLSZLg3EfbHb9rT+DMumOk+cP2NaJWKbbbcQkIr2h62JIE6cMGLamichr9A1rAZoYFvfKD88ac82M95AnJBcUI6fQxqrOYbXVktIZpDuOgtAS7Bg6p8wTVnQiXk/HYO+EeHqfbuEiWO9Rk7kqKljSrIajUUI0uTlokqAKQsjIK08TxX5GWX1G43b29s6y1dzaSWraRzsvx4djUdOq+7WI5vEeZ5MlbEJkyuCqzkzYWRl0nwv1Sy+leB/Yg5eVhQLX20jjZmQ+R1c56PSonxd3g2DcIrcFxw78EgZi0uLRcAMnOl4ucTPf2WAGf3yqkZvmBYswPpwuaBcGPzP78bbj5r84qSclL8kj83SN0KuKqPEsnjD4gzfaI1ew7yY2i+vcE5TFDGEVCwMwhBSu8Ky1vTcK+t7I7yesLVqfJ1X4/IPSt8I52FdLSDg77L2CMtiUdT65fKOvlh6lKM08c5ytGC5XP4X9tWslA==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/receivers/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches detailed information on a specific receiver by  `id `, including all associated wallets.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Receiver`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Receiver Details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.api.mdx
deleted file mode 100644
index 2457762756..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-a-tenant
-title: "Retrieve a Tenant"
-description: "Retrieve a Tenant"
-sidebar_label: "Retrieve a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWGlz2zgS/Sso1FZtUktSp60Mv8mWkkixJUVXMnG8Ckg0RYxJgAOA1mhc+u9b4KHDku0kM1u1tZ9kA328bjReN/iANVkq7N7gNo0Zx7cWFglIopngPYpdPAYtGdxDewqccI0tnBBJYtAgjdoD5iQG7GJGsYUZxy5OiA6xhSkoX7LEGMIu7nWQkGhAYkAiQDoE9C03+M3BFpbwe8okUOxqmYKFlV5HxqhicRIBtjD8kUSCAnYDEikj4IcQE+w+YL1OMkktGV/izebWWFOJ4AqU2a9Xq+bnEE3uGlHQhEUKW9gXXAPXRpIkScT8LAGV35QRfzh2J7zfwM+SIU26NMudMXoMyYAnWRgurrUa5x7Qht3yfqnbzdZ51X4TBHX7rBZ41TcA1dYvAd5YRU6PLT2KIgSk80iMgoN6GqlQpBFFMdF+mKU5IVqD5Ojbv2+I/ad9+69/ZBnfYfKiFHwhE+PXIwoWqYy+z/ekM0Ie8e+AU6RA3oP8p0LGBJqNrw6dhFonyq1USmd2oecomjhCLo1zRZNFyhY/jmHWq1CiQk8QSdHFd/k/8KuJTtXJg+NpbK7GtDtoD6aLy3G3Pe12sFUujMbDeW/SGw72F9uX0978UK7T3S3ebixMmXHhpSaOBfF9kXK9IJRKUCdxnAhbQxQRiQplVCijVAFFgZBo54IvUZByqg4T8u7yc7vf+NxvzD80+m/fNz5ed94OJx+u64Pr6y8Xk2Fj3pued2ejj58mnU/1fqt5XW+Mx5Mr/BT8HPPPYDcaLwIvTqLTm0zHvYvZtDccLNqXl8PZYOpMpt2rq/bY6Q7m2HpepHOxmLdnV9On5C5748ur7k7sydN6umiOA85lS97bN7fNwXeGn5VRF1t41B10eoN3i9mkOy4rrjccZHiZWlAISBrpPXieEBEQfoTvIl9HQUSWSIckY5CVQqsQdAgyQ1xwDFM5/ty2oXMutJNZLLxl5LyxsC+BaKALok8lKBAyNjuYEg22ZjEcVGa9Wm/a1YZdb01rLbdec89qX0zVpQn9+41SiOBpoyfolsWgNIkTkyC+n50VUeiVEoF+jQqjzs/C2uw3xJsdKR8k9gUWeb5sn7vDVtHKd1VU9KNjht5y58Hp3O5FmLdE/KZZpT5pntm0RgO72fSp/abh1+zzM7/arDfO/PpZULpxsQSaNaT9frRl8GLzqIGc6B+PdfZli+t7mslPJSfjzI/zzvVo2B003r/v98+b82b9w2w6HAw/D1qX5/P6aDIfta+6835r1Pt1eHF+3ej0563BYTaLEWf/jpyqA6darX45TOwzchsLa6azmirmtM3G1FGzWjuefmacpDoUkv0J9O+bfUBKIU9MZKYatCTqZQtHnMrT2ANpTMSgFFmeaDB5mHv1VsDAA6HRQZg7FKWfZrW2Z/mxxn/TcH40zeOjMaJvRcr/L87l6fwFRYinUtfcT90YlEilD6bVFFqbwrQCP5VMr7NHyAVRzG+nOsTuza15AxymtXzEIIK2z5gYdCgMOS0hf9UYZVzJ6VxVHhjdGKLI5tr8pZOTCjbmS+cTcwh5li6ASJA5hm02SMI+wPqolfQ/TXct35QGcF2cr4UUW3KgaMV0iAhH3Un97Bwlkt0TDegO1s6OKdtFVWWa5fsrBELN6ZhRgAciQ1NwQzl6dZjyUqkgBq7RKCLa9CnUHvWwhU24Ocq6U3OqJgdpHBO5fjS+nbbxatIZvTajAkFaiAh5KYt0FqaQS8ILqAppgWJyB8hLozuUkLWxkq0StJQiTcy0JMFnCcs2xH0xi5TeOeiVkHfOsxPm/wbEr/wrn4ZMZS45Eglwu6jqRApz4/LBi6kCiuBIi6ScFx+ZsxDhNNvwBQXkE448yK9Gphiaf6JIrMwAKSERimkhGSjX4LDRjcrtVYpfm+4lyU6KJJXt9fZV2UOXTIep5/girvyQhdcuyoLfQlkjQ2yE8XycLB+QJirGA0mUlqmvU1kEaM5Fv3Smzg9EFsiMV/9KaKWJl2JbgYdK2Z+OJoQotv2QSK2ehbwnV9ESoBITxivFwrPxvBTGe4hilBnKnyiQRGJtyuvFSFCqjNxd6oHkoEE5Xw1NaZCxGgYTkPfM33+eFzDNkFbJhGwR2KoQs3DEfOAq6yYlASbEDwHVM57aDX1upbJarRyS7WbWClVVuepddgeTrl13qk6o4yjjyUQoHRO+Z/hUxzggmi3Fa/hDV5KIMJ69UvIPF3k3ucFFN8EWdhk1k3EolDYbDw9mTp3JaLMxy7+nYAj25tbC90Qy4hm6vnkwk6j5m24/fD3CsJ0R8Ktx8WR4jZ7/1nYSdtmuuOlV9yRKzX/Ywnewzr/tbczLsugsBli+0fZ9SPSeytGgYprlttO+607xZvMf2XEDIA==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Retrieve a Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID or Name of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.api.mdx
deleted file mode 100644
index c84636808d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: retrieve-all-statistics
-title: "Retrieve All Statistics"
-description: "Fetches all metrics on all disbursements the organization has created. The response includes basic aggregations on payments, receivers, receiver wallets, and assets."
-sidebar_label: "Retrieve All Statistics"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWNty2zYQ/RUMnpIZ6mLF6YPelMRN03ZST+RMHhSNZ0WuSEQgwAJLKYqG/95ZkJKoi+3YvUz6YovE7sHZC/ZA2kiC1MvhRI4JSHlSsZfTSCboY6cKUtbIofwZKc7QC9Ba5EhOxV5YEx4T5Wel85ijIS8oQ2FdCkZ9A/YVGXgROwTCpCtuMhQOfWGNR6FMrMsEvZiBV7GANHWYBqeAXcA6QEbCYYxqia71UaxAa+RFMIkA75F8V0bSFugCxLtEDuUHZopLHGndCi6SWwpeDjdy0O/zv8N436JBB1rs3Xa8ZSRjawgNsRsUhVZx2LL3xbPvRvo4wxz4E60LlENpZ18wJhnJwjFBUvXOZAn07UH+Wk7KEKbo5HEpbthLmDKfoRN2fph/Gcm5dTlQDfDTpYwkfoW80CiHg34VySatt7EtDaHzD9NMHMzpLLG7t7qoOMuQrB/pN2CGaBJl0kd6vgixlR6TJ1D1ZRyjP5/9uz1fVpGcg9JP2jIU/7F+lxV7KuIHeV1X8vW2kK3iQs4v/e1sfRvORmsfcA7WMpKKMP+O4gf329gm2LL15LhALWby4/jN6zMMHt9dZ7Av+v1uvy/PtNQZ48HO+LSPzpi/2JsfN8+9TE475oz5y535SZvcCw5LdJA+kPG9+XErnTO+bKxP+2fUVOrupVfrUWiiKlSgHsC3zQD+QedI7ZcqT+iedDznGtL0PzvYB+f6Q5PiT3WG2+e7VoydHj5BLfa+98bR7/fblBo5bIloVfH6Zf/iVDs/Gigps059w+SfE0t0zrrTJq+YNTn4jv7zBFS27eqsMESO3p89cHWYu7zsaMj3lsRBmHsW230u+xct5GOPfxM4YHuMS6doLYeTjXyF4NCNSsrkcDKtpuxPmeVLUoohVcBLsufb9ySPrm6zyUaWTsuhlOy6RR5z6erctvH3UlOo33B90pK/froRPGrF3LpAHA01XREJr1KDiVgpygQYcTUevPxJFE4tgVAscM2XPAM5w4+amIMnKxqDZwgJ17Ti57kNbJomHhNqDU68aV2YxLUG4nMgRtfvZCQ53JrloHvR7XMOyjwHt+ajlKG4H+PZ+M31c6G8AEHWajErlaYQZvtK7AVZkcMCxazUi909l9+CSJ0ti+agqkKFBcsXXmrtbpBW1i26p6f9h6P42Xw2N5nyYUsjbIGm423pYhSFs3xOBWVAvFxTsUaQDfBn4OrrPi/wjUTEYMQMxdyWJgmOGT9obVfKpMJhYb0i6xT6IfPoiImv8XrN/0778twpmiR1ZhAv0CTTZxlR4Ye9XqooK2fd2Oa9RyE8H4oQ/I7KWvA4BGXqb0qNWYhKmbkDT66MqXRNgFwXeqim3UdENndhGv+d0LYQD8W2wpnY2j45mgx13okzcOTvpdyy65FD7OWgTK95cW88D4XxC+pcBKDAP8FC2zW314ORiNKz3aKcoTNI6LufeUwRutz/MR+jW6qY59I2rIZm17q0F4w6dt7xjVkktYqRv34ON7sBWECcoRiEOVXPZ8Ya9nqr1aoLYTWgNa6+9/u711fvx1edQbffzSjXYU4W1lMOpgW8/d4sRrr9Ffh43Gz22v6/+YGgkSbCr9QrNCjD8h9yt2k0cCL9wQ8hmfXEbzebGXj86HRV8es/S2RVmEwjuQSnYMYaM5lW0VaCWDQXyMIximMsWGSXoMtaGI/uQQeC/PbqRkYSTrR0EbS0+cDo2yWzbmEfq2JNgf9W0R0um02t1FW1s6+X7vRoQtxacxanVVX9BYk1YOY=
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve All Statistics"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/statistics"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches all metrics on all disbursements the organization has created. The response includes basic aggregations on payments, receivers, receiver wallets, and assets.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"General Statistics response","content":{"application/json":{"schema":{"type":"object","properties":{"total_disbursements":{"type":"integer","description":"Total number of disbursements","format":"int64","example":20},"payment_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":2},"pending":{"type":"integer","format":"int64","example":3},"paused":{"type":"integer","format":"int64","example":1},"success":{"type":"integer","format":"int64","example":5},"failed":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":14}},"title":"PaymentCounters"},"payment_amounts_by_asset":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"payment_amounts":{"type":"object","properties":{"draft":{"type":"string","example":"100.00"},"ready":{"type":"string","example":"200.00"},"pending":{"type":"string","example":"300.00"},"paused":{"type":"string","example":"100.00"},"success":{"type":"string","example":"500.00"},"failed":{"type":"string","example":"100.00"},"average":{"type":"string","example":"100.00"},"total":{"type":"string","example":"1400.00"}},"title":"PaymentAmounts"}},"title":"PaymentAmountsByAsset"}},"receiver_wallets_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":1},"registered":{"type":"integer","format":"int64","example":1},"flagged":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":4}},"title":"ReceiverWalletsCounters"},"total_receivers":{"type":"integer","description":"Total number of receivers","format":"int64","example":1000}},"title":"GeneralStatistics"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.api.mdx
deleted file mode 100644
index c28c73adc3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: retrieve-disbursement-statistics
-title: "Retrieve Disbursement Statistics"
-description: "Fetches metrics on a specific disbursement by  `id `."
-sidebar_label: "Retrieve Disbursement Statistics"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNWFFz2zYM/is8PrV3suW46R70ljbplm3X5eL0+pDmUkqCLdYSyZKQXc2n/74DJdly7Dh1tu76YlsiAH4fAAIwVxzFzPHolk9QoHQoE8fvAp6CS6w0KLXiEX8HmGTgWAFoZeKYVkwwZyCRU5mwVLq4tA4KUMjiirHPMmWfhzzg2oAVZOMy5RG/Jm1YwHlPvrdrwI2wogAES4BWXIkCeMRlygMuCYYRmPGH2C7PmZ4yzIB97hv2+1v4WkoLKY/QlhBwh1VOJp0sTA484PDN5DoFHk1F7kggyaAQPFpxrIyXRCvVjNf1HVlzRisHjtbHoxF9bWO5BiytcsytWbGptlsO4gFPtEL6Fa24MCaXiXdR+MWRjdUuBh1/gYQUjSWHomwQGFGRwftEl6rx2VMaqRVT7IlJhTADywM+1bYQ2Lz65dQ7RngXRSc1ERdpdaTeuA64AZWS947TfEWaonQUtqOhujJJwLkjNV/XAZ8KmT9rS9Qo8mP1TmvSlOjT8aqJ5NsukN4BTXBFQS/dfVzdC+egHz1hrajoaCAU3xF8r36f+Gx/mN49ZPzD5PztHgTHZ9ce2yej0XA04ntSao/weC28m0d7xF9txB8mz0EkuxmzR/z1WnwnTQ4aFwuwYvaExzfiD1Npn/BpK72bP2dtpB5felOd+SSqfQQSkAuw90uR54DuJ60jjd5MOgT7rOM5zcVs9r8d7K1zfd26+GPj4f759rbvuxjsr1fbveWGNJgqixgsdbyN7kEeo1EfUb9Dul7vrWuSOh2d7Pa0D0qUmGkr/4b0v2teYK22e/osQUcrviMJqceWfbnGNWSiAOf2nrqG5to5axj8vUa2RXODotvndHTSs/xQ40cabkLzajc077SNZZqC+vFx2c9uA+A7BDwPB0lpJVZ+wHsDwoI9KzHj0e0djVgFYKZpVpyBx0YDX8TDzTwV9mcpF65kWnOyahfd1FjanEeck7VuswmRb/j1t9x0UiP/gGrnxP3+8YZRJ/EzHIUEFLZ+DZiTMwUpW0rMmFDsYjJ+/QszVi4EAptDReNnO8CetdH0mt0sm4FIKVtrep5qj6Y9pBOEPBeW9Q8ru8oF0jFnZ1eXPOBEt0E5Hp4MR+SDsiiErahSZMAO23gxOb96yaRjgqHWOYtLmaOnqe1MqBaqY6hZIebA4jKfs3Yg8G8Fm1ldmrYOSSP9gl6A9ZN4t7sCXGo7H+4Ws58O4if1Sd1k0vktFdMG1MDp0ibAjNV0VhhmAmm5gaIVQ226/x4PzAVMqNQv0MDFEqFYDGyqS5V6xYwe8lwvpZoxC0Y7idpKcBHhGLBb19gL2+9BP+0HpnXSIBbJHFR69yJDNC4Kw5nErIyHiS7Coyy8jJgnv4ZSMSooQpKHM2CtmGcl1dQKh7ZMsLQtQYoLPhXT4RHMptbXs39DrTPxFLclxKyTfTabDPJikGTCojsIuScXogUICyFV2L44yOcpGr9BXjBvqPnPCSbXFaXXk0xY6UhuXsZgFSC44ScqUwi2cH9NJ2AXMqG61NFqYQ61nYVeaKCnA9eKBTyXCSjn20BXAI1IMmBjX6ea+ky2ojBcLpdD4Ve9tVbVhX9evr14P7kYjIejYYZF7uuk0Q4LoXqGuxuFbV5bdwpbdWe1aZPPvtNoewbCNwxNLqSiicOTWrX96pa7LQT9jsUDHsmUblgy7ZBkV6tYOPhg87qm119LoCJ+exfwhbBSxNQSbldkhX6n66uKR4m9uG5vPV6yQ3cje3l0DVFRN1yIvKQnHvA5VM1NTH1XB13vIljNwlmSgMGeys4IstXcf7244QEXO0147ptw+4Os74XzsJ02EOizDh5RWa2aFl/Xa/lm6VGNluKaOTGo6/ofs/+oyA==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Disbursement Statistics"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/statistics/disbursements/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Fetches metrics on a specific disbursement by  `id `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Disbursement`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Returns statistics for disbursement","content":{"application/json":{"schema":{"type":"object","properties":{"payment_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":2},"pending":{"type":"integer","format":"int64","example":3},"paused":{"type":"integer","format":"int64","example":1},"success":{"type":"integer","format":"int64","example":5},"failed":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":14}},"title":"PaymentCounters"},"payment_amounts_by_asset":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"payment_amounts":{"type":"object","properties":{"draft":{"type":"string","example":"100.00"},"ready":{"type":"string","example":"200.00"},"pending":{"type":"string","example":"300.00"},"paused":{"type":"string","example":"100.00"},"success":{"type":"string","example":"500.00"},"failed":{"type":"string","example":"100.00"},"average":{"type":"string","example":"100.00"},"total":{"type":"string","example":"1400.00"}},"title":"PaymentAmounts"}},"title":"PaymentAmountsByAsset"}},"receiver_wallets_counters":{"type":"object","properties":{"draft":{"type":"integer","format":"int64","example":1},"ready":{"type":"integer","format":"int64","example":1},"registered":{"type":"integer","format":"int64","example":1},"flagged":{"type":"integer","format":"int64","example":1},"total":{"type":"integer","format":"int64","example":4}},"title":"ReceiverWalletsCounters"},"total_receivers":{"type":"integer","description":"Total number of receivers","format":"int64","example":100}},"title":"DisbursementsStatistics"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.api.mdx
deleted file mode 100644
index 0980031a5e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file.api.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-id: retrieve-stellar-info-file
-title: "Retrieve Stellar Info File"
-description: "Allows the wallet to fetch the SEP-10 server url, SEP-10 signing public key and SEP-24 server url."
-sidebar_label: "Retrieve Stellar Info File"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNVltvIjcY/Suf/NSVuGQJm0hUeSAwBBJ2YBnIjUHIzHwwLh57antgKeK/VzaQsu1m022ranlBY38+PseXc7wlhi40qY3JABdMG0UNk4JMCiRGHSmWuc8aqXMu1xpMgrCmnKMBI2GOJkpcW+D1i+/PQKNaoYJc8cJLE1sIJhaQ5TPOIljiBqiIXW+lejKgRApEZrifvxOTGhmgUQxXGBjknKqOmMsW40gKRKHOpNCoSW1LKmdn9u9LukO5RAFMw4pyFrsZHXWcZXSBsGacwwyBSxpjDEKqlHK+sRwiKQwKYyENfjZlI1NuP/AzTTOOdikajd7IHwZX45DcXDcq7fuHVqflXz7ctlu9wf11o3l32xs8vvILSQFCctOsn1dvnysXreeni+pjI3iqXjRGftDuPl5eVLrt28dPrwNMIOjc+B3/ZnrnPV19Hez10eB7w4fe4G7arwdBvz2oB95VSIaoDQTNFvho1lIt4WcIMDOYzlBB5ez9h5BAuzfoPPf86WjQvQpJYkyma+VyIhX7TYqiQW0EmpLeb1dJqkVI4MG7ntZHw/bU85v9XscfnoykWfFQXIyZnuVKY4rCFDNOzVyqtDij0RJFXIxxdQpbprlJQgLDQd0PWt5gGniDe/fXPzurVP+LGTRmlWpIQjEeN3uN0UfPH9aHnZ4/mUBvcDP16x/toh1OJtRZvK9tjAYDz290vGAygUjGCFcQEm806DVCAkzrHJVrurm+blYvO62L7sPdZf/yY9O7DxoPg8tmf/Rwf+4/nTeHn7z7Vrfq14fV+qf2+XO32+rWPziUKdUazZSKKJEKY7gCo3KE/feh02yy/eRzRk1IQBtqcu1aOFthSMBemFN6r/MfBc0fmP6eXSjIbrfbFUiKJpHWPhZoSIFk1CSkRsqlNXJeXAq5FuXjRrurXSB7D7IeuCW54qRGyG5im6NcMbMJogTTvdVcI1Wo6rmF3BLLkdQIzdgdbsifDfP2YQi5xhjmUoE9sCgMi5y7FZwpYgxrZhKgAryg8uECMsVW1KC1SGtEgqbObXLjbtjelwuEWfAEaYyKWL1MzKVjw4xzp+OZbJ6cd+gfzjvU+x1SIFbunmWl9L50ZtcgT1OqNtY5rZt/E+OnoNl/Z72VgpGSwyxn3DiZUi2oOFDVNiBSukSY5XwJGd1YFNdKYaFknoGcg8KIZcx1SBsE5mR2sXei0l+W9sejGIpQDBOm3ZQCZIaiqGWuIoRMyV8wMmASamz3nooUYKSD/wpc4SWv3BWMqLBZNZe5iN3AxH7YPLa5qjCTmhmpGOqa5VGE8eGAl/+W901+Orrlgpkkn5UimZa/C+FdDZz4FyobsClKmdg/GA5lThUTc0W1UXlkcnUQaPfFvLWnpe9QNlcuxP+NtCPEW9rWOINj7T9WkyBPi1FCldHfpHxSVzYKsZxSJsqHhm/qeUtGG3kKDsjxjzHjcmOP15tKINe2bpnPUAk0qEuhtSmDKtW9eYBqxSLrS0dZpynriopyXtSHsgLhLEKh0Tra0QAzGiUIFedTe3+2WLVyeb1el6jrdWiHobrc7TQ8P/CKldJZKTEpdz6ZSW1SKk6Aj+/LF332hQmHJ+YXjrP941X4/zyED9HiHqAZp0yQ3UH79pBoY3KSaNbATzNtUiCJ1MZWbbczqnGk+G5nm3/N0br8eFIgK6oYndnMGE92hWOk2BBcog2CehRhZiN0RXn+wsbh23h8ydkbb0h2u98BxMo+qQ==
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Retrieve Stellar Info File"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/.well-known/stellar.toml"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Allows the wallet to fetch the SEP-10 server url, SEP-10 signing public key and SEP-24 server url.
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Token is valid and the webpage will be loaded normally.","content":{"text/toml":{"example":"ACCOUNTS=[\"GBC2HVWFIFN7WJHFORVBCDKJORXXXXXXXXXXXXXXXXXXXXXXXX\", \"GDA34JZ26FZY64XCSY46CUNSHLX762LHJXQXXXXXXXXXXXXXXXXXXXXXXXX\"] SIGNING_KEY=\"GDA34JZ26FZY64XCSY46XXXXXXXXXXXXXXXXXXXXXXXX\" NETWORK_PASSPHRASE=\"Test SDF Network ; September 2015\" HORIZON_URL=\"https://horizon-testnet.stellar.org\" WEB_AUTH_ENDPOINT=\"https://ap-stellar-disbursement-platform-backend-dev.stellar.org/auth\" TRANSFER_SERVER_SEP0024=\"https://ap-stellar-disbursement-platform-backend-dev.stellar.org/sep24\"\n[[DOCUMENTATION]] ORG_NAME=\"Stellar Aid\"\n[[CURRENCIES]] code = \"EUROC\" issuer = \"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5\" is_asset_anchored = true anchor_asset_type = \"fiat\" status = \"live\" desc = \"EUROC\"\n[[CURRENCIES]] code = \"USDC\" issuer = \"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5\" is_asset_anchored = true anchor_asset_type = \"fiat\" status = \"live\" desc = \"USDC\"\n"}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.api.mdx
deleted file mode 100644
index 5aeec0d658..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: send-one-time-passcode
-title: "Send One-Time Passcode"
-description: "This endpoint generates a 6-digit OTP and sends it to the user contact (email or phone number SMS) provided in the request body, as long as it matches the receiver contact info stored in the SDP. A valid SEP-24 token should be included in this request's Authorization header."
-sidebar_label: "Send One-Time Passcode"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWEtv20YQ/iuDvSQBSMkx0gLlzUlcJH1ZiBT04BjJkByRWy932d2hZVXQfy9mSVmU7dpJH0AO1UXScnae3858y41irILKztU7qnRgj6ydVReJKikUXrfxb6YWtQ5AtmydtgwVWfLIFADh27TUlWY4W8wAbQmBbBlAM7ADrgm6QB4KZxkLhqfUoDbgPLS1swS2a3LyMP95/gxa7650SSVoGzd6+r2jwJC7cp0ABjDOVvKtGRrkoqYwyBWkr0ZGtF06COz8Xtf89WwCJ3CFRpcwP52lxy+A3SVZCLXrTAk5gbaF6W7s67Bz4EmAk45r5/UfMTlQE5bkJypRrqU+YW9Llak52fLM0kI3NMMQCleSSlSLHhti8pLljbLYkMrUgUaVKC1J7hWr27k/8HfpPOCBO0+/d75BzuDJS0JPHjZRcvvkmUqUxKA9lSpj31GiAq+N2A+6aY24R9etEUezJZogAkVNDapso3jdRkn22lZqu73otVHgl65ci8Shm2f5b1RwXwVtta0OaqwSJU/IsuzEtjW6iP5PfwuyfTOyvHf6XHkqsOWixo8xKkHm4JiL9iTDXurAmoJsjkY/DkbvhHE7t7MxDNnBqtZFHSEjeF5pYwQagSxP4FRzTR4+jS18Eix/iqj+BANmxPWJ2iYqLj/uw2k8E/+28duJe9SNxQ2+PL06mS1evRkOTI/RrXxuAyouhNbZ0Cf/+OjoHmAsZjEICF1RUAjLzpj138VDQyFgRY/jYCd4D5ITxZrjMfi5F3o3xKD6GF/cF8VLLOFdj/8v8f1hJ8l79xkofU2M2gTA3HUcAdJvFIxds8fwqKUYF11jPPV7w+qt7Xuitm3HaqxuqcmUH5fOqWz/e4wylQzrOfobmRw9WKIyCJ5zArSgLVNFvgdQzO7zu9l9b3dNLSr+b9P7+WlTgZG7sdzQWLbJQwD7i2T/4hgOwtx7sbPz4uj5SPPtHf+l4lia4+/ulubE9u0IQ3+Kh7le6Suy/XSXCWzZrOP8rzHYJwx03QpIYE08gTMrD5dM/mZd80GDO2ALWKG2k68JBnGW36eg7E/m/SAYsnqdyvaKbDrMz1QoTTowAfndV4xs0M72NOGS1ip7cGeirtB0NxpkPDfEtRMm0rrYpFrkWmVqukJjiFM/YnhTx61KVCB/tWMmnTcqU1FRoKLzmtdzSXCfgZ5bCG0ZxYqt/pHWd9rVD78upJDlDVkhy0PtEgi6slTCSnMt3eF0fvzNt9B6fYVMcElrqftnkCRJrODg3Z6SnO4PxiEJ2LfVYSLvF+5MyVFthUfGYIdhMWcyBj281iHvfKBGcDszyEvnGziZvZWakA99Eo4nzydHkuKuadCvI4cmeFjH0/nr2TPpsQjsnIG804ZjFp2v0A6ZiL21wUuCvDOX0OJatMRVhMq7rgW3lEOpWx0fOGHHPLJuiVfOX07ucoCvzsUP9oONlw8xacG1ZNPgOl+QXBgi4+QaWR73rjgL7KL6e9QlsUXJAzlYUKCVBrR0nS3jxlr+GONWQl89tS5odl5TyMSPFM5Dr286fKflKElpOyQpzbG4JFtePK2Z25BNp5XmussnhWumX6ThWQaL/ioyuLLe8ev+7jOIxai0XXoM7LuCOz8EKHXhx2o6+YLIlj625H8S2k7FY7GtKIed7N+OpibTpEWNnsODLo/kpuyJpg1qOx0WHoznsTDekGkgKor+l9QatxZ4PRoJdEHkLrucvCWmMPkgXZDJN+FsOSd/pQvpS7uwBjcnzlfTKJS6ZRoGsUQZXZBw3Gx/CW2xqAmOY5/q27/oyqbT1Wo1wfg0ahu2hulPb1+d/jI/TY8nR5OaGxPbsEybBu1IsdyE4cxSKndhGF2GD7rNZj/f/3+/cO/7hWHMMl3ztDWorYylWKjNMNzP1T3DXd5McCtXpFqIQHauNpscA733ZruV5d87kol0fiEkwmvMZb6dX2yT3XTdU5BXfYnShbiy5xx36Ng22e04KQpq+UHZMVeZnc0XKulJjFzbItNSHlcynXEllERetHBPjTb92kYZtFXXc9lep3z+BCT9qZM=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Send One-Time Passcode"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/wallet-registration/otp"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint generates a 6-digit OTP and sends it to the user contact (email or phone number SMS) provided in the request body, as long as it matches the receiver contact info stored in the SDP. A valid SEP-24 token should be included in this request's Authorization header.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"Authorization","in":"header","description":"SEP-24 token for authorization (Format: 'Bearer {token}')","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Object containing phone number","content":{"application/json":{"schema":{"required":["recaptcha_token"],"type":"object","properties":{"phone_number":{"type":"string","description":"Phone number to which the OTP will be sent. Either `phone_number` or `email` is required."},"email":{"type":"string","description":"Email to which the OTP will be sent. Either `phone_number` or `email` is required."},"recaptcha_token":{"type":"string","description":"Token for reCAPTCHA validation"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OTP sent successfully","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"429":{"description":"An OTP was sent to the given user recently and hasn't expired yet. Only after expired it will be sent to the user again.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"code":{"type":"string"},"details":{"type":"string"}}}}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/sidebar.ts b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/sidebar.ts
deleted file mode 100644
index 213799850a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/sidebar.ts
+++ /dev/null
@@ -1,435 +0,0 @@
-import type { SidebarsConfig } from "@docusaurus/plugin-content-docs";
-const sidebar: SidebarsConfig = {
-  apisidebar: [{
-    type: "doc",
-    id: "platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api"
-  }, {
-    type: "categoría",
-    label: "Administrador (Gestión del inquilino)",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/admin"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-all-tenants",
-      label: "Obtener todos los inquilinos",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/create-tenant",
-      label: "Crear inquilino",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/retrieve-a-tenant",
-      label: "Recuperar un inquilino",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant",
-      label: "Eliminar suavemente un inquilino",
-      className: "método-api delete"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-a-tenant",
-      label: "Actualizar un inquilino",
-      className: "método-api patch"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/default-tenant",
-      label: "Inquilino predeterminado",
-      className: "método-api post"
-    }]
-  }, {
-    type: "categoría",
-    label: "Autenticación",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/authentication"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/log-in",
-      label: "Iniciar sesión",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/refresh-token",
-      label: "Actualizar token",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/authenticate-mfa",
-      label: "Proporcionar Autenticación Multifactor",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/forgot-password",
-      label: "Olvidar contraseña",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/reset-password",
-      label: "Restablecer contraseña",
-      className: "método-api post"
-    }]
-  }, {
-    type: "categoría",
-    label: "Claves API",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/api-keys"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/list-api-keys",
-      label: "Listar Claves API",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/create-api-key",
-      label: "Crear Clave API",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-api-key",
-      label: "Obtener detalles de Clave API",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-api-key",
-      label: "Actualizar Clave API",
-      className: "método-api patch"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/delete-api-key",
-      label: "Eliminar Clave API",
-      className: "método-api delete"
-    }]
-  }, {
-    type: "categoría",
-    label: "Saldos",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/balances"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-organization-circle-balances",
-      label: "Obtener saldos de la organización (Circle)",
-      className: "método-api get"
-    }]
-  }, {
-    type: "categoría",
-    label: "Integración Bridge",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/bridge-integration"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-bridge-integration",
-      label: "Obtener estado de integración con Bridge",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-bridge-integration",
-      label: "Actualizar estado de integración con Bridge",
-      className: "método-api patch"
-    }]
-  }, {
-    type: "categoría",
-    label: "Desembolsos",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/disbursements"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/list-all-disbursements",
-      label: "Listar todos los desembolsos",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/create-disbursement",
-      label: "Crear desembolso",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/retrieve-a-disbursement",
-      label: "Recuperar un desembolso",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/delete-a-disbursement",
-      label: "Eliminar un desembolso en borrador",
-      className: "método-api delete"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/list-all-disbursement-receivers",
-      label: "Listar todos los receptores de desembolso",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/download-disbursement-instructions",
-      label: "Descargar instrucciones de desembolso",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions",
-      label: "Subir instrucciones de desembolso",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status",
-      label: "Actualizar estado de un desembolso",
-      className: "método-api patch"
-    }]
-  }, {
-    type: "categoría",
-    label: "Organización",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/organization"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-organization-info",
-      label: "Obtener información de la organización",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-organization-profile",
-      label: "Actualizar perfil de la organización",
-      className: "método-api patch"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-organization-logo",
-      label: "Recuperar logo de la organización",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/patch-organization-circle",
-      label: "Configuración de cuenta Circle",
-      className: "método-api patch"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-all-assets",
-      label: "Obtener todos los activos",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/create-asset",
-      label: "Crear activo",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/delete-asset",
-      label: "Eliminar activo",
-      className: "método-api delete"
-    }]
-  }, {
-    type: "categoría",
-    label: "Pagos",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/payments"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/list-all-payments",
-      label: "Listar todos los pagos",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/create-direct-payment",
-      label: "Crear pago directo",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/retrieve-a-payment",
-      label: "Recuperar un pago",
-      className: "método-api get"
-    }]
-  }, {
-    type: "categoría",
-    label: "Perfil",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/profile"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-profile",
-      label: "Obtener perfil",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-user-profile",
-      label: "Actualizar perfil de usuario",
-      className: "método-api patch"
-    }]
-  }, {
-    type: "categoría",
-    label: "Receptores",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/receivers"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/list-all-receivers",
-      label: "Listar todos los receptores",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/create-receiver",
-      label: "Crear receptor",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/retrieve-a-receiver",
-      label: "Recuperar un receptor",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-receiver",
-      label: "Actualizar un receptor",
-      className: "método-api patch"
-    }]
-  }, {
-    type: "categoría",
-    label: "Registro",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/registration"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/start-wallet-registration",
-      label: "Iniciar registro de cartera",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/send-one-time-passcode",
-      label: "Enviar código de acceso único",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration",
-      label: "Verificar registro del receptor",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/retrieve-stellar-info-file",
-      label: "Recuperar archivo de información Stellar",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/request-challenge-transaction",
-      label: "Solicitar transacción de desafío",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/provide-signed-challenge-transaction",
-      label: "Proporcionar transacción de desafío firmada",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/request-registration-url",
-      label: "Solicitar URL de registro",
-      className: "método-api post"
-    }]
-  }, {
-    type: "categoría",
-    label: "Estadísticas",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/statistics"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/retrieve-all-statistics",
-      label: "Recuperar todas las estadísticas",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/retrieve-disbursement-statistics",
-      label: "Recuperar estadísticas de desembolsos",
-      className: "método-api get"
-    }]
-  }, {
-    type: "categoría",
-    label: "Usuarios",
-    link: {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/users"
-    },
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-all-users",
-      label: "Obtener todos los usuarios",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/create-user",
-      label: "Crear usuario",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-user-activation-status",
-      label: "Actualizar estado de activación del usuario",
-      className: "método-api patch"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-all-roles",
-      label: "Obtener todos los roles",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-user-role",
-      label: "Actualizar rol de usuario",
-      className: "método-api patch"
-    }]
-  }, {
-    type: "categoría",
-    label: "Exportaciones",
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/export-disbursements",
-      label: "Exportar desembolsos",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/export-payments-csv",
-      label: "Exportar pagos",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/export-receivers-csv",
-      label: "Exportar receptores",
-      className: "método-api get"
-    }]
-  }, {
-    type: "categoría",
-    label: "Carteras",
-    items: [{
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/get-all-wallets",
-      label: "Obtener todas las carteras",
-      className: "método-api get"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/create-wallet",
-      label: "Crear cartera",
-      className: "método-api post"
-    }, {
-      type: "doc",
-      id: "platforms/stellar-disbursement-platform/api-reference/update-wallet",
-      label: "Actualizar cartera",
-      className: "método-api patch"
-    }]
-  }]
-};
-export default sidebar.apisidebar;
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.api.mdx
deleted file mode 100644
index 127902aae0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/soft-delete-a-tenant.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: soft-delete-a-tenant
-title: "Soft delete a Tenant"
-description: "Soft delete a Tenant"
-sidebar_label: "Soft delete a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWW1zGjkS/isq1VVdsjsDGLCd5Rs2ZINjAwFMsnF8RDPqYbSekWYljb2si/9+JY2Gl4Bfkt0PV1f+BEit7qdbre5H4h5rMle4dYXbNGUcX3tYZCCJZoL3KG7hsYh0BxLQ0J4AJ1xjD2dEkhQ0SLPwHnOSAm5hRrGHGcctnBEdYw9TUKFkmVGFW7jXQSJCOgb0tVD0tYI9LOGPnEmguKVlDh5WepEYZYqlWQLYw/BnlggKuBWRRBmBMIaU4NY91ovMSmrJ+Bwvl9dGm8oEV6DMfL1WMx/bKApXKCogIAqasER56I7pGBHEBfchzfQCfaWF5IzoryhikBjvQsE1cG3UkixLWGjjVP1dGd33u9hE8DuENmLSRFWzAhmju/iNp8T63MIHx42jAGjDPw5+qfvN46Oa/yaK6v7hQRTU3gDUjn+J8NJzgd/VtO3yJAakC3fNggrqaaRikScUpUSHsd2TjGgNkqOv/7ki/l/+9c//stuzxhQkOYRCZsZuQBTMcpk8z/a4M0QBCW+AU6RA3oL8t0JGBbocnW8bibXOVKtaLY35bl1F0awi5NwYVzSb5Wz2/Rgue1VKVBwIIik6eZb9Lbua6Fzt3Tiep+YETbr9dn8yOx1125NuB3vlwHA0mPbGvUF/c7B9OulNt+U63fXg9dLDlBkTQW78mJEwFDnXM0KpBLUXxx63NSQJkcgtRm4xyhVQFAmJ1ib4HEU5p2o7IL+efmqfNT6dNabvG2dv3zU+XHTeDsbvL+r9i4vPJ+NBY9qbHHUvhx8+jjsf62fHzYt6YzQan+OH4BeYfwS7WfEkcLcTnd54MuqdXE56g/6sfXo6uOxPKuNJ9/y8Pap0+1PsPS7SOZlN25fnk4fkTnuj0/PuWuzB3Xo4aXYdLmTLIrmpbhWDZ7pv06iLPTzs9ju9/q+zy3F3VGZcb9C3eJmaUYhInugNeIEQCRC+g++kGEdRQuZIx8RWkDuF7mLQMUiL2NUYpgr8hW4kJOJCV6xGZ81W8qWHQwmkqLD7AhQJmZoZTIkGX7MUtjKzXqs3/VrDrx9PDo5b9YPW4cFnk3V5Rv95pete8Mxyy1JQmqSZCRDfjM4dUeiVEpF+jZzSyo/CWm52z6t1Ud4K7BNV5PG0fewMe67fr7PI9aPdCr2qnVu7c73hYdES8ZtmjYakeejTAxr5zWZI/TeN8MA/OgxrzXrjMKwfRqWZFpZAbUPa7EerCu4mdxrInv7x7ZpNWXd891fyfcGxNfPDtHMxHHT7jXfvzs6OmtNm/f3lZNAffOofnx5N68PxdNg+707Pjoe93wYnRxeNztn0uL8dTceHNs/Ivjyo1Gq1z9uBfURu6WHNtM0pR+aWS5NHjVpzlypNtrOWJBIIXZRpiwKIhASkY6aQyUNQ9pS/UKQXivRCkV4o0gtFeqFILxTphSL9v1Ck5r7XpBNCS+7j7eQxU+ZYI0gSNmdBAkgLFMAqp9FbIZHb3r2LN0uEGxWyEGQaxaRQHwBwQ03CGGjxilWsI6Fmt8ZfVzS/4WY/VX/6HjoGUgr59MHuFM9piAQi1xZIsXBpEllLop60ZGO9kfTOMO7xW5IwihjPco031dm3uVkkBG6tvyNHSu3J99x4QORKJiAScQCq3K4QjhjXMAdp97vY8T2kuC80eity/g++Bj4Q2+fHbJd38TwNwIY9BaXIfA+fcE7uCbVxMXIurhGUNpq15oZWPAIlchmCzcViVRk/BWEumV7YN+IToljYznWMW1fX5ql2O6zmldmdDETQ6qE5BR0LU/aKKfv0bFTganEgVPWe0aWpQpY0F8/RRcXCxkgJYWy2oojVCRAJskCyignJ2HtY7KTz2cfJmk+QXMfAtdtlDyk25+WRIxx1x/XDI5RJe+jQDSwq6zJsrAnJ/rIry0fyGAi12WZ+R8KicYWn5HUdpoJcKkiBazRMiDZNELWHPexh426Bsl45qNRMDPI0JXLxDTfcr+PVuDN8bQ4JQVqIBAU5S7R1U8g54Q6qPRwpuQEU5MkNysjCaLGjBM2lyDNDxSSELGN2Qtw6olNa56DvhLypPEpf/zcgfuFf+MRcZo1JjkQG3He5nUlhzl3B6phyUARHWmQlGf1GnYcIp3YiFBRQSLipMvaA2IWx+ZEk4s6wUwmZUEwLyUC1DA4fXalCX9V9+nQjSH7mglT27utXZYOeMx3nQSUUafW7NLxuoUlxk3dQFsiUN8J40YjK26nxivFIEqVlHupcOgfNvuin9rTyHZ5F0lbXv+NaqeIp3+4gQKXsD3sTQ5L6YUykVo9C3pCraglQTQnjVTfwqD9PufEOkhRZRcX9B7JELEx6PekJypWRu8kDkBw0qMoXU6Y0yFQNojHIWxZu3v0dTMMAq1bIF5GvnJiHExYCV7anlAUwI2EMqG7r1JpRtqrVu7u7CrGzVptbqqrnvdNuf9z165VaJdZpYutkJpROCd9Q/EDf2Ko1qyqv4U9dzRLCuL0FFQ8jRUO5wq6hYA+3GDXMOxZKm4n7e8ODL2WyXJrhP3IwNfbq2sO3RDISmIp9dW+YrvlOV39UfoNhRRbwq5EjJq/R/v9E98ItOxU3beqWJLn5hT18A4viv9elubG6pmIAFRPtMIRMbyzZYSqmT676bKd73p108XL5XzPDNpQ=
-sidebar_class_name: "delete api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Soft delete a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"delete"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Soft delete a Tenant
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Deleted Tenant details, with a non-empty `deleted_at` field","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"304":{"description":"The tenant was already deleted before this request.","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"400":{"description":"Bad request, when the tenant is not elligible to be deleted. For example, when the tenant is the default tenant or when it has not been patched with the deactivated status.","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.api.mdx
deleted file mode 100644
index 890a65412b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/start-wallet-registration.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: start-wallet-registration
-title: "Start Wallet Registration"
-description: "This is the endpoint the browser reaches with the first token so that the receiver can confirm their verification information through a webflow. Requires a valid SEP-24 token in the request."
-sidebar_label: "Start Wallet Registration"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVV1Fv2zYQ/isEn1pAttKg24Pf0jVYs3VdMKfoQxoUJ+kksaZI9niK6xn+78NRsuOkabysK7A92RLJ4/d9R353WmuGJurZpf4DGxOZgI13+irTFcaSTEiPM33RmqhMVNyiQlcFbxynh4L8MiIpQihbjGppuE0DtaHIiv0CnYpecQvDAsISzTWSKsGp0rvaUCcDhtQ1kqlNmSAo42pP3fCfW/J90ypQSyxq65dT9Qd+6g1hVKCuwZpKzU/PJ8fPxw2NG/f61GPkqc60DzhwO6v0TM8ZiN+Btci3eGc6AEGHjCSirLWDDvVMp6g600a0+NQjrfSXCuFtDH3EStWeFPTcouORmM40DdgrPWPqMdORV1Z2EcI60/g5WF/hbrRssQM9W2teBZkWmYxr9GaT3eAjcBFKif/BVIeB7s1XplIQoy8NMFY3+dvn8i9ivpJQMXgXMcr48dGR/NyBOCQxjqkFVyVISywCNKiWxlpVoLIeKqyUk3Ni7UrSXHrH6DjtjJ85b7mz8vA1QHfFeXXx22uVNtlG2mw2m0w/vw/mC6jSOcTIj9naFx+xlBWB5FSyGZRAIk+HEb5EBmOjgsL3w40aFm4kCUwQD+6UCOFn6IJkcLexPnOD3MaFnvV+uNqgrT7U3kvCt/8lP7tTkY3vC6DdnAJIOcQqKvaSLpB7ydggJVEHWZ99KetbJzfGk/kzBf5Ouv59vXRk4H5/nuu7ApPkHcYIDd530r+i8hvP6ha/GxTbfZ4fPduLfHfFEBlCsKOj5B+j6Lb+brttElFuvVhng0kg4FbPdL5MHjqhPRPNo5irznREut76aE9Wz7SW6x+x7Mnwai75GwR+gUBIJ73E3AkJwfyKX9rXL+8uvmatmYqmcVsTA6dO58c//KgCmWtgVAtMFjFa5snIcWvKyTFbhCodT3mufUJjOBndnNFaIPXSxKKniB06VucWWBxQnZyf6UwL3QHl8fTZ9Eg06LsOaLWtDw/GeDJ/ef5UbhUo9t6qojeWE01PDbgRarpNHSxQFb1dqAAriZLegmrI90H5WqqsCSYNeCm2vLe7Q156WkzvL2H/KYjv3Xu3bT3AKR/QTaLvqUQVyMtlHRoLE0co0iz4FP6ecNmukpS+wtSAFKhq37sqLZSuxVvrl8Y1ijD4aNiTwTgTHBN1GYd4+fg7qfZEmoRRpEkB5QJddfWkZQ5xlueN4bYvpqXv8kdFeDpTifwOyipVJTBuaMTGaYmVcTVBZOpL7mkkKHnhQzmdPoJZTcmLv4XaNsQhbkss1HbuP2bTou0mZQvE8UHIe/NyJsS8A+Py8cWDfA7ReIW2UylQwl9hsH4lx+sgE9VHmbfoCySHjHH6XmyKkbr4ez1Hujal+NKW1ghz6qnJ06SJrydxnJZpa0p0MdWGrQEG6djVcfKpwZ8l1izPl8vlFNJoijYujfnrs59O38xPJ8fTo2mqwuKTwUfuwO0FTs21Grprdae9vmU465va/v//wBirVmpRggXjpD1Isq7Hanmp76mWUiNSvbzKdOsjy7T1uoCIb8luNvJ6aOOlilYmQmGlCa/BRnxAzicj/OqpesSHyb0cFrja+wK6BttjKuXZN+B5/PfHQ9DufvzcYLySBzICUs8urzbZtsKLmsPqk7LEwHurbppMWb7re34+vdCbzV+5a2QA
-sidebar_class_name: "get api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Start Wallet Registration"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"get"}
-  path={"/wallet-registration/start"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This is the endpoint the browser reaches with the first token so that the receiver can confirm their verification information through a webflow. Requires a valid SEP-24 token in the request.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"token","in":"query","description":"The SEP-24 token used for authentication","required":true,"style":"form","explode":true,"schema":{"type":"string"}},{"name":"transaction_id","in":"query","description":"The transaction id associated with the SEP-24 token","required":true,"style":"form","explode":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Token is valid and the webpage will be loaded normally.","content":{"text/html":{"schema":{"type":"string","description":"HTML page content"}}}},"400":{"description":"Bad Request","content":{"text/html":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"text/html":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/statistics.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/statistics.tag.mdx
deleted file mode 100644
index 3586c69ffc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/statistics.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: statistics
-title: "Statistics"
-description: "Statistics"
-custom_edit_url: null
----
-
-
-
-Statistics endpoints return general aggregated data per organization, as well as disbursement-specific metrics. SDP users can use this data to monitor their disbursements over time.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.api.mdx
deleted file mode 100644
index 05d922792b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-a-disbursement-status.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-a-disbursement-status
-title: "Update a Disbursement Status"
-description: "Updates the status of a disbursement according to the state machine. The disbursement must move from  `draft ` to  `ready ` in order to start the disbursement and trigger payments. Payments will start as soon as this endpoint is hit. A disbursement can also be moved into  `paused ` state by an SDP user to prevent further payments from going out and restarted when they are ready."
-sidebar_label: "Update a Disbursement Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWN9v2zYQ/lcOfGoB2Uqzbg96c5sWzX50QZ1iD2mAUNLZYi2R7PHk1DP0vw9HyY6dOMm6odtQ7CWyxLvj992RvI9ZK9bzoLILdWJC3lLABi0HdZmoEkNBxrNxVmXqvS81YwCuEAJrbgO4GWgod9xAF4Wj0tg5sNtaIjS6qIzFMZxXuO/QtIGhcUuEGbkG4KokPWO4En+4ItTlCq7AWHBUIsnXwJo4xt6f2ZbAZOZzJPB6FUmM4Wz4BdemrgdXHSA4Z+XJlQmAtvTOWAYToDI8hsl+5EJb0HVwkGNEWoKxEZ3XbcASrgaS+Qq0henJGbShh+oJlxJh1hJXO7h6rnMneXJtj50wosMSriu0wm8FmhBiCsYqUc4jaanFabmtxmS3ZtNYFJUor0k3yEhS1rWyukGVKVOqRBmppNdcqdvlPT2Rct5Oq0oU4afWEJYqY2oxUYFXtcQLpvE1qkThZ1+7ElU203UQg6LCRqtsrXjloyWTsXPVdZcSLXhnAwYZPz46ksc+kF8wBD1HeDdYqkQVzrKAydZKe1+bIuYh/RjEYb0z4Q3WC9X0cWQhDzhc/hELoeRJksmmR7ExPAA4UWw4sh1QbUF1wlvHDOyG2NtEMFRUdZ2Een6I7Qtdwjv81GLgLyH6MCMkcnSAj2Bm0uHxCP0G37GzbZMjSYgH0tXtZ2WAETnSluMNhM0kz4+OkvtSaAJYx/0ukC2V425W/+Hp+io+u1vF91a3XDkyv2P5zZbxrWPYo3kotc92U3vL42sG7kvz3d3SvHaUm7JE+/XrcpjdDYA/YdDTeH6XhjB+7Vr7bS+v2cDw0AJ4fu+mtVvPrxw7hg9YtGR4FXvrC9SENGm5UtnFpTS4BrlyZd9liyp2YxlU6W5bDenalF0aNh07IC037bqlWmVKSazNVFOpaJ/y3Qm3qdXe/ISrOy39x9/OISqUmaO4XdDysFgSCGZuRWwYrkS2vJoef/8DeDJLkTILjJJjUA6TYadFz42IqFCXUupO3mcuohl65ZSxrjXBXiLPas0zRw1Mzk5VooRuj/J4/Gx8JDlom0bTSmVKROLDMZ5MT86eymGtgZ2rIW9NzZGmo7m2A9QgJ3ijFwh5Wy9u1Bc70DAn13qRPISF8SYOuKXotp3ZLfK1o8X4Tmr/exA/2A/2XOSsTGnBebSj4FoqEDw52b7AlY4drofiLLDzG9F3K1zS6+kKoXAlRgmcY78RomMlL3XtrkXCEnoXDDsyGDLBMYKL0MdLh+dod/WP/JCkUa6LBdry8knF7EOWpnPDVZuPC9ekXxThaQaR/BbKCuSU1Mb2F5bBLLIydkY6MLUFtzQQlLrwYzUdfwGzGcVD+u9Q24R4jNs15rCx/ctsKqybUVFp4vAg5B27lAkxbbSx6fDhQT6P0XiDdQMxUMRfoq/dKt4kH91rbRC7RZsjWWQM4w9yTDFSE36dTZGWppBzaUNrgDl2NE+j0cjNRmEwS1RtChSJn22vThOviwrhOJ5T/fkssbI0vb6+Hus4GqMNriH9+fTlq7fTV6Pj8dG44qaO56R3gRttdwL3tzjQ+7y2F7m9M2d90/f/v4v/y3fxoe8yfubU19pYkTxxYayHfn+h9vq9SlQWL+BDy79MVOUCi916neuA76nuOvn8qUVpgheXiVpqMjqXlnqxlnDyu9xes+9dHE/eDbfgp3Dvpf4ggY2asCIllrpu5U0laoGr/v8H3WWXbBq/YOoHJkWBnndc7ojSPV10Njl/+UYlSt/RMIuoYYYfEv8goNtqpAchf7vkHpf1uldIXbe174fu9RhIbrkLh67r/gAA78jm
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Disbursement Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/disbursements/{id}/status"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the status of a disbursement according to the state machine. The disbursement must move from  `draft ` to  `ready ` in order to start the disbursement and trigger payments. Payments will start as soon as this endpoint is hit. A disbursement can also be moved into  `paused ` state by an SDP user to prevent further payments from going out and restarted when they are ready.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={undefined}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Message Response","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"Disbursement started"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Disbursement is not ready to be started"}}},"example":{"error":"Bad request","extras":{"status":400,"message":"Disbursement is not ready to be started"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.api.mdx
deleted file mode 100644
index 84784f0fd7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-a-tenant.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-a-tenant
-title: "Update a Tenant"
-description: "This endpoint updates the Tenant data."
-sidebar_label: "Update a Tenant"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1zGjkS/isq1VVdsjcDGLDJ8g0DWePYQACTbBwf0Yx6GK1npFlJY8K6+O9b0szwYvBLcsnV1fEFkPpdradbfY81mSvcvMYtGjOObxxMQfmSJZoJjpt4EjKFgNNEMK5RmlCiQSEdApoAJ1wjSjQpYQeLBCQxTD2Km/jKErYyGuzghEgSgwZpdN1jTmLATcwodjAzahKiQ/xQd6+DRGB1fckEfTGKJPyZMgkUN7VMwcFKLyMjTLE4iQA7GL4mkaCAmwGJlCHwQ4gJbt5jvUwspZaMz/FqdZNJA6VPBV0ail0DLpjSxoSAQUQV0iIPAAqEtHbpwj9fcA1cGxG/lH8xX3tahfcH+DYW0sRKM1Bm1yMKZqmM9u3bPwpA484QecS/BU6RAnkH8p8KGRHoanRRwisHK5rMUjb7drFXvTIlKvQEkRSd7ojURKfqkCTgaWySZ9Ltt/qTWXvUbU26HewUC8PRYNob9wb97cVWe9Kb7tJ1upvFm5X5PDxnu6ASwVUWtmqlsn9eWdbRdWqCJixSu8dDkiRivs3U8h/KsL38rBg9GISvxGZeEx81aice0Jrb8H6tuvXGScV9EwRV9/go8CpvACqNXwMT0Cz9X3IwWYIhw1BCPY1UKNKIophoP7QZmBCtQXL05d/XxP3LvfnXP+wl2djkRSn4QiZG7w/NtW0lodaJapbLhTI35yspmpSEnP+MxHxK/47e/3L2Opgyo8JLjR8z4vsi5XpGKJWgDtpxwG0NUUQkyplRzoxSBdSCz0YFn6Mg5VTtBuS39sfWee3jeW36rnb+9qz2/rLzdjB+d1ntX15+Oh0PatPe5KR7NXz/Ydz5UD1v1C+rtdFofIEfMz+z+XtsNxzPGp6fRKc3nox6p1eT3qA/a7Xbg6v+pDSedC8uWqNStz/FztMkndPZtHV1MXmMrt0btS+6G7JHT+vxpNl3OKMtStW2uHUMXui+TaMudvCw2+/0+r/NrsbdUZFxvUHf2svUjEJA0khvmecJEQHhe/adZusoiMgc6ZBYBFkotAhBh7BdxBDLynouGwmJuNAlKzHXZuvpysG+BAOzM6IPBSgQMjY72GCxq1kMO5lZrVTrbqXmVhuTo0azetQ8Pvpksi6rrD9YKIUIHhd6AG5ZDEqTODEB4tvRWRCFXikR6NcoF1r6XrN2atv1BpR3AvsMijydtk/dYSfvujZZlNejfYReY+fO6dxseZiVRPymXqE+qR+79IgGbr3uU/dNzT9yT479Sr1aO/arx0GhpoklUFuQtuvRGsHzzb0CcqB+POTZps2v72EkPxQci5nvp53L4aDbr52dnZ+f1Kf16ruryaA/+NhvtE+m1eF4OmxddKfnjWHv98HpyWWtcz5t9HejmXel23fkUB6UKpXKp93APkG3crBm2uZU3lJnPVL9UBd0SigaZW3tj2t9QEohn79EnazlQsQTqbb3J2NcmaTRkqhnNVm/thIsV4x7/I5EjCLGk1TjbXG2O58FQuDm5reBs/Utc/J1j8g1jUck4gBZW+8BIhwxrmEO0sY2i+7RgR6Tk1SHQrK/rOCfG96Xh22/zeFp7IGNfAxKkfmB8r16LNh9odGOmxsrCj31ytGW5IccP1NwdjT1/aMxpG9Fyv8vzuXx+AW5i4dCV98O3QiUSKUPppDnXEVqK/BTyfTSvsZPiWJ+K9Uhbl7fmEfxV9cXFObA3fx57HqCLt0cv83vTD1wxQTPnvS3sMTNJzkdfEeidC3BKIpBh4Jm738/tHMCYwUuZ1VXle8ZXRk8t8+PTFGG/Za98GJsTjML9ykQCTJzZh1WkrB3sNwDq/MPk01nZnIMuM4TxUGKzTlQtGA6NNjQHVePT1Ai2Z15/9/CsrQpaK08PS1nMdEIgVCLJeZ/IKw1OYQXHXKHKS+VCmLgGg0jok07gVrDngkVSJVZWS0dlSomBmkcE7l80GUflvFq3Bm+NhBIkBYiQl7KIm3dFHJOeG6qhb6Y3ALy0ugWJWRppNhVguZSpIlpaiX4LGF2Q9zlLWOhnYNeCHlbevIh8L9h4mf+mdthllHJkUiAu/n1SKQwVzfrj5nKTREcaZEUbf0DcQ4inNoNk+/IJ9zUEHvHLGNo/kSRWJg+X0IiFNNCMlBNY4eLrlUmr5x/u3QrSG6SB6nogm5eFa3OnOkw9Uq+iMvfJOF1E1nn16YskUFIwnjW9RfvfOMV44EkSsvU16nMHSwGXk+eaekbPAukBej/xLVCxHO+LcBDBe13exNCFLt+SKRWT5q8RVfWEqAcE8bL+cKT/jznxhlEMbKCspckJJFYmvR61hOUKkN3m3ogOWhQpc8GpjTIWA2CMcg75m9PUXIzTS9dtkSuCFyVkzk4Yj5wZctSAYAJ8UNAVYtTm968WS4vFosSsbtWWs6qyhe9drc/7rrVUqUU6jiyOJkIpWPCtwRnAz1E0HqQvAMz95sy//JBdV4TNHzV5SQijNvXZzaQysrPNc7LD3Zwk1Hz4gmF0mbj/t68P65ktFqZ5T9TMIh8fWNqm2TEM/h+fW9eGOY3Xc+gHzX71ShvUl+jw+Pug+YWdY0vt6oqdvIizChemUlBXoI21bmdqXUn2UOwYDQT65VTELV8HxK9tb3XP+1U7mFr0j4zb7l8gh7b0TuWZGFm9WRha/Vq9TcBCVu7
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Tenant"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/tenants/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint updates the Tenant data.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Tenant`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"List of fields to update for the tenant","content":{"*/*":{"schema":{"type":"object","properties":{"base_url":{"type":"string","description":"The SDP backend server's base URL."},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL."},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Updated Tenant details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"name":{"type":"string","description":"The tenant name. It should match the pattern `^[a-z-]+$`.","example":"bluecorp"},"base_url":{"type":"string","description":"The SDP backend server's base URL.","example":"https://bluecorp-backend.sdp.org"},"sdp_ui_base_url":{"type":"string","description":"The SDP UI/dashboard Base URL.","example":"https://bluecorp.sdp.org"},"status":{"type":"string","enum":["TENANT_CREATED","TENANT_PROVISIONED","TENANT_ACTIVATED","TENANT_DEACTIVATED"]},"distribution_account_address":{"type":"string","description":"The Stellar account address used for distributing funds.","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"distribution_account_type":{"type":"string","description":"The Stellar account type used for distributing funds.","enum":["DISTRIBUTION_ACCOUNT.STELLAR.ENV","DISTRIBUTION_ACCOUNT.STELLAR.DB_VAULT","DISTRIBUTION_ACCOUNT.CIRCLE.DB_VAULT"]},"distribution_account_status":{"type":"string","description":"The status of the distribution account used for distributing funds.","enum":["ACTIVE","PENDING_USER_ACTIVATION"]},"is_default":{"type":"boolean","description":"Boolean flag that shows whether the tenant is the default or not.","default":false},"created_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"updated_at":{"type":"string","format":"date-time","example":"2024-03-27T17:21:51Z"},"deleted_at":{"type":"string","description":"The timestamp when the tenant was (soft) deleted.","format":"date-time","example":"2024-03-27T17:21:51Z"}},"required":["base_url","created_at","distribution_account_address","distribution_account_status","distribution_account_type","id","is_default","name","sdp_ui_base_url","status","updated_at"],"example":{"id":"840dca45-d1df-44cd-83c1-65c04235c25f","name":"redcorp","base_url":"https://redcorp-backend.sdp.org","sdp_ui_base_url":"https://redcorp.sdp.org","status":"TENANT_PROVISIONED","distribution_account":"GCQVDMPOEN3HHJJ64V42KUTONOXN7C6V2PSVPALEVJ7PIYOB6M3DJV7N","is_default":true,"created_at":"2024-03-27T17:21:51.000Z","updated_at":"2024-03-27T17:21:51.000Z"},"title":"Tenant"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-api-key.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-api-key.api.mdx
deleted file mode 100644
index 0e82bef1ff..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-api-key.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-api-key
-title: "Update API Key"
-description: "Updates an existing API key's permissions and IP restrictions. The API key name and expiration date cannot be modified after creation."
-sidebar_label: "Update API Key"
-hide_title: true
-hide_table_of_contents: true
-api: eJzVWN1z2zYS/1cweLmkQ0mOL3cPenMSd6K203psZ/rgeDwgsRJRkwACLCSrGv7vNwuQEkXJdpw2M70nUcBiP37YT2w4ioXn0xt+djFjP8Pa89uMS/CFUxaV0XzKP1kpEDwTmsGD8qj0ghH1Paz/5ZkFVyvvldFEIdnsgjnw6FRBx/2YXZfQkTMtaohU8GCVE0TBiDkrhNYGWQ6sNlLNFUgm5giOFQ4i2Zhn3FhIZ2Zyq9bZxexnWPOMW+FEDQiOrNlwksSnXEmecUVWWIElH5pGugWtvgRgSoJGkuyYmTPsKY2GhSiLZ9zBl6AcSD5FFyDjviihFny64bi2JJAs1wveNLeJGDy+M3JNFIXRCBrpU1hbqSLaMvnDkyqbQ1Ym/wMK3BN6w3tw001ZR6CgAk8H+5s7PsI5sT4w/RflkSzt39/CCY0gyWIsle8QIAgRan9oZsZBh5r0ciDkVFQVz/jKKYT2Oy5L5fPgPNSg0W8JhquR1EEBakmX2JH1VyKJFet9Rr2FSGDcQmj1Z0R3SzRYjITB9wV1/+LWSlQV9GTs/sdtjwIpEortCjxY49Dz2ybjtdKzhNebJuOiqswK5J2yEUCj4bd5dNEhlPv3c6X0ogIKJyGlA++Zcez97MMlc0IvgDfZwQU/cknNkPUZ0dPd75jDgL3nzUEeGEQ2mxvXj5Mxm80ZBbF1ZqkkyGyXLvbOOaiF0izooiRRkjdNxlFhBYOovkzxwxsi2I+8uOCt0T55/unJCf0M7GwDOEWvZD4UBXg/D1VFcH1zPO4HnZLH4mKQQg9yzAA8uqSUsp5j9THUQo/I50ReQcqoR5g9nQq+1lNekiQOXf0vCm25Pe2lGY+lZH0XE/QR9ObG1QL5lBPBCFUNB5CeD4rRfv4nGbEKgbwT+I0ifi9B7xWVlfCs5doXkK+/wpk8OLYqTXd+qGzr7n+zspXw2EVSX8qLNO4zGapNe3fBfyfF/SDPtH1DE3PL22PZ452QrK3gbMSWolIy+Qg4Z2Kl6CWQHyY/vCRnRBbP4/YBUKjKM5GbgNGwdDB6PTrhn5UUzYMHUdsKeoL5TEeDmNI20KEdu7mCSt7NjeHT3TdTnm0TcNau58JtaXLhmAaQntJCTj0eUxphAS5CnEB+cwjyJy0ClsapPyPjvx3Rr0eKU00PfTod6hwi2DV4LxZH0kvzGL6/GmR7lu206OS8PXnT4zw8kTgfq0vfS1q8on8fXtGPxuVKStDf5X6Ow7eT+RIY9k5Fc94+3hRQpzI3Qf+/ut0L3aMz9ZhnvO17xiV4E1wBPYA6cR6K4BSuY/f6DoQDdxaw5NObW+oWa8DSyDRqFWUcyWiTT4RVo3tY+8lGyYYTH7fs5rTgKj7lsdvs2F8R9gmcvpBdP2FVGvn2L/an369jmo/dEPk29VoJnIx5tdAg2UphSbnp/Or0P/9l1qkl1XtqXnnXf/GzNiy6USFOjyUIGXNZxgnoy91kd77De6/n6o1Et4POqOclSs9NNK0tS1cIVSUc+9AbjthFJZCqH5U1nnHCLpl8On4zPiFAQ10Lt24H2qd5vLr6cPGa8rlgaEzF8qAqjJj1R6SYx2txDywP1T3rRixaFWzhTLDUJTkolFVxwywh9aCddA24Mu5+fHTm/mep+Fl/1tfUyqr4yGEs6FEbBNYZilqGpUDaTqoYzdDYrk8csMviAwdtFEbGlw0qiDGS4sGS/pA7pMHIGq/QOAV+SnqM2I1P/Cbt76g/KI9sC9IoF8U9aHn7qkS0fjqZLBSWIR8Xpp68iMPrKYvGb1VZM8qHQhHCJbCWLFql9NwJjy4UGFxrYDd8PHmn4xdYNncxHf8V0zoWz9m2gpx1tN9sTQlVPSpK4dA/qXKPboIOYEJj8KRdeNKe58z4CFXNIqOovwRbmTW517OWsOCJ7j7k4DQg+PFnynkIrva/za/ALVVBeakzq1VzbNxiEolGZj7yLVnGK1WA9jEZdtnUiqIEdhrzVEr2xGs6maxWq7GIu5Fbe9RPfpm9P//16nx0Oj4Zl1hXMela47EWusc4PRSw9tlymGV6r23/nPfLtn4hPODEVkLpOEcRJpu2Vt7wrlbyjE+VpNJRGo+0s9nkwsMnVzUNLX8JQBn/5jbjS+EUPQbEgiqVp2/Jp3NReXgCl1eXbUf/mr34HfSoKV191nQdS1EF+sczTgNefIpt6HWsLaWka9p4nzQaXdPx3cGD5oZevNKJs6IAi0/S9vuRi7Pr9x95xvP2IbY2kg45saLXO7FKWpoIUWw74tqGV0IvQuqKEtPYcx00I+mFtP3oPezt4zBsK5IlafZ95Mhmk1qdptnSp61HT7TYbiEnIJqm+R8ZyV6i
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update API Key"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/api-keys/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates an existing API key's permissions and IP restrictions. The API key name and expiration date cannot be modified after creation.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"The unique identifier of the API key to update","required":true,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"application/json":{"schema":{"type":"object","required":["permissions"],"properties":{"permissions":{"type":"array","description":"List of permissions granted to this API key","items":{"type":"string","enum":["read:all","write:all","read:disbursements","write:disbursements","read:receivers","write:receivers","read:payments","write:payments","read:organization","write:organization","read:users","write:users","read:wallets","write:wallets","read:statistics","read:exports"]},"minItems":1},"allowed_ips":{"oneOf":[{"type":"string","description":"Single IP address or CIDR range"},{"type":"array","items":{"type":"string"},"description":"Array of IP addresses or CIDR ranges"}],"description":"IP restrictions for the API key. If not provided, existing restrictions remain unchanged"}},"title":"UpdateAPIKeyRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"API key updated successfully","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","description":"Unique identifier for the API key"},"name":{"type":"string","description":"Human-readable name for the API key"},"permissions":{"type":"array","items":{"type":"string"},"description":"List of permissions granted to this API key"},"allowed_ips":{"type":"array","items":{"type":"string"},"description":"List of allowed IP addresses or CIDR ranges"},"expiry_date":{"type":"string","format":"date-time","description":"Expiration date of the API key"},"created_at":{"type":"string","format":"date-time","description":"When the API key was created"},"created_by":{"type":"string","description":"User who created the API key"},"updated_at":{"type":"string","format":"date-time","description":"When the API key was last updated"},"updated_by":{"type":"string","description":"User who last updated the API key"},"last_used_at":{"type":"string","format":"date-time","description":"When the API key was last used"}},"title":"APIKey"}}}},"400":{"description":"Bad request - validation errors","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"API key not found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.api.mdx
deleted file mode 100644
index e95e8ed912..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-bridge-integration.api.mdx
+++ /dev/null
@@ -1,77 +0,0 @@
----
-id: update-bridge-integration
-title: "Update Bridge Integration Status"
-description: "Updates the Bridge integration status. Supports two main operations:"
-sidebar_label: "Update Bridge Integration Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWutv27YW/1cIfmoH+RE3XTd/um6ctGm6JIud9eYmgUFLxzZnidRIyp4X+H+/OCRlSZadR7sCu8AdhraWyPN+/MijBxqBDhVPDZeCdul1GjEDmpgZkPeKR1MgXBiYKoYLiDbMZLpJBlmaSmU0MUtJEsYFkSm4Nbp7Jw6a5CI1DS6IkTmZV25vl9zRi8vhcX90en5HX5MGOVJgWZ7dHJGYizmZSEWkmjLB/3JcpRhLpiIupnei0/QbyG9cmYzFpBeGMhOmzODquNe/GZ1cXI36x5cXg9NhldPC72R+J5sYUJY/S1MlFyy+EzSgG5VOI9qlmbWMU+a0MAkNqIYwU9ysaPf2gb4HpkD1MjOj3dv79X1AFfyRgTbvZbSi3Qf7kyuIaNeoDAIaSmFAGHzF0jTmoSXb+l2jPx6oDmeQMPyXWaVAu1SOf4fQ0GDLcVeOCxrcSbrffTSgqULlDAdtebjHBQ9tFBfTGo8hU1Mwnop1E4YJrxgDRJbQ7u3GxzSoe4PeBxT+ZEkaI7PNynVAIWE83iXIRKqEGdr1K7YlO8anhEWRAu0kQ28uQPGJNyh5Je1iFgckggnLYoxeSTINiliir2lZqt/lTPzL/2yGMkHpJlkcjwRL4GlTnWRxTHDpy4XBXVVZPsmZIH0JKMN8FY4c6ye9tUqByEmNeclJXER8waOMoUXHmeYCtK56Z/M0oIYb++js5ghp0/U6KEXzbR5G98XKWrZcMhPOfKhafzs+NvZkakbcxXyWJEytMDZSg/EldwQzDeiCxRmUA7gcdT6U6o6s+LGwbdm0hdaoY2jLxshXjZGvGlVBfU3aqiw7Zaynw9r+h8bUqRTamaPTbuNfVZ/uyGmX7RHRWRiC1qjbiv5tZeVIot12VxMuXFa6f4dxhhU6rw5MRERBbEWLmGFfXXSOMqVAbKqOnOzpTaWwPr8Yjo7Pe+8/H/dpYH+V4uLRwhTQ46uri6s9BeqRwB44bTBaMm1kAmrEo6eV82rke8hpv5L4+Hx00HnDxmGe+zWz7XFcreTY1lpyWc0hz5H3WvA/MiA8AmH4hIPadIG8e1fkR4EP3/4YweSry6f3dwpKY7CLCNRUYpyd3RztLZLfr4082SP+KbXZRYv1yGN2yBSvO/nqs9U9dLnvjb3fDDNjUt1ttcY2mJvaQBwz1ZRq2pqvwlYRAEbqb5OIhSGkViADKrHFQINa8BCeK5CRuiTQzoTa47JaQnm4eScaREiDdJSBqGttlSqJxRhfkJWDTPgS13Lh7QrVpX4JGWfGbstX4R62ZBzVHmVj2SU9/4tcx4YnFuqBgAkPOYvJxVKAqgiKBGzejBQsOCwdW52NE641z5OKuJeWmwXBuSoVnfNXuEwBFp6dy/JXuCxlmd42i3uGb+VkYrE9rjjKq2Dx8K6cESUr04AWdqQBLRuIBrSsLr71UlNssU4yrH5WCMT5G3bV9NqiUkqxotpjSD8bPucxO3Ax68OZiRDKwZSCwEbaJcOtGN9Ek9vnDFg4q7a8WFYyoqdetkpF6ZKtcoWHF4NCYWdALsVIAdNSlPVmSjHEHtxAssMe6/qZxVLYFNoNbfKKT4iHLeO4ioZv6enG8ySSYZaAMHlR6vnSXYnGCeMxqrmBctGImUdrECKqhuEJ1Hz4ZQai0u/IkmniyVaKUKfdedtoHzTaB8N2u2v//893xQdbaJxHFaQbbFqe5VhqD6W6XKmIleCuyn1fyYbPXMxPxUSidjtA8uM45bets3gZVGJcXA/6JIJUam7qB9dvgyx1sF5YdsFG7376+c/VX6jUcxN8W5dSUrPQ8AWz1TK/r+DaPQWPlVm0sqLl2uK2CHZvLD2vZPfmqZWt+FVN8dKi3I1edM+iSPcIFhCjyUcTgFEKKgSxM3eqlujn28gELHjDbWwKhGnCyGZTIVO7+fY7g2ctMxXCyFt3xIU2KrPV5hlo+j0T89wxpLzVeky7mmpj1cg9sVWN3DET89E4b9tq9UxcfF6CxEhiE2olUhUjDBz28eclZ2I8T4Wr5568wmpUVqhnOkKSVpmXK6AgBL5AwyGBCuEvEMeanDA1lRsGHpY/zSNvAk+zOei8Ib/g7eXABGTABDlRTIRchzIgR72CszPySGTJGNQzArPsGbdpvw0POm8O3/747qef2xt+SmYWzLyIn9/k+W2xOGi3253Dn5BDylbYMUeK8fhbmre/AoaIeIrEUtyrKBanGQ3okiug99vdanc+lKK1HGVbAbHbS7ttua3//b4S2HcqnJbLhLOB4cLBjSerRr9YTEIpJnyaqaKzhVIswBpwkomo3tzKgj4dA5clJ3gfFJKWg8Gfhl5WCiqaFC6pVAJbZZ+dpHlhKh+2i0y9HvSrp/sP/V8vO2eXv344O/148+nDv8+vT28ufvnYu7ruXR313vU/Dd+eXHROTi4uzm7evO98Gfz68cPhlzfvbE7FMpyHM8bFKIFEPiOfNhsIbtgAhpJJiVFMaBbWzGvTuQbGKr6sRHVusEcCsfDjToy3QWi7e3W1qT7eB6vxvVekHOxJPF2MuBiNnxFC19q2aLKcSWI3WpNW5jylm96t4AKFcKzC86sh/JAnoA1LUrJEMF+dNFnB9smxD9Jvgd5Rfsp4qVn8vifBadke+3j/XebZnpW97Ljz8gmBiy17HX7YPqjfgF8LlpmZVPwvK0DpmvuH1g+P32xXyysoJXf0VjuUMIrtBIVP3GD7HrMOaAJas+kOPOQ025htIwY9l4ZUNCukyPkctg9KlLd3OMq77vq/Fzfrojd1F51INeZRBOK7+Ge3+QqeLzFDZZdV57CuDmp+IjPxvxpuLwyLiVd1V0QcliPiClwrsddSblfOzrCpxnz3J7TyuPweSZiZxJF6itNAC8lwWk79fW2Db03X1QKUtsP1TOFEj+JUPR+6D9D+zkDl0XsBa1N+Bqtalfv0ZYjT1shdK2dmhrcDzkAB0XwqICJLbmaECXI86Lz9kaTKHprJHFZNGlA/Puz5lMilxQEmnQGL0DHrgKKxr4oPAI4Lm3/HmSWKMXE4x5fZHG31uR5nSoOFipcxM9gQSO/yFCeVoLQzTqd50Gyj6TfjzeEMyOM0Xg36l6/tnQYxUsZknPHY1D7lsFPuhM2BjLN4np8c7FNGpkpmKZ7aFIQ85faFXIDDXjl3AWYp1bxZ71v/OBHvxJ0Yzri2LO0XMqLhUyZVEnOcmBmz9zlOFISVMs3PrVvkAntNhC9CGQEJmSBjcHlnN87wRxzLJeJn5dCdVBzw/gmvkm498G/5vxtRyUiN1BupMWbhHER0/yofoky5mWVjjMLWiyi87hKr/EaUFZ54DONC++sLu8xqxcVEMYdDM+UVzEH3oz5tvkCzibLF+1tUy0k8pdsSxiRf+9XazCBOGuGMKaMfFbm0rmUUQAu/x2r5B4/q85QaHyFOiCWUn+pjubLTtydzDWvRlMyzMSgBBnTTXlPaqd3FxM8/SpO6yogOFzXkpFGM9mIegtC2bOZ1N2XhDEjH1inXFpBWt9VaLpdNZt9aan6rbn0+PTo+Hxw3Os12c2aS2JbnVGqTMFEifF35eKrUucigOGeV6s5DgQn+//Fc6eM535QM/Glaacy4wLZkHfXg+/0t3dHv7wM6k9rg24eHMdNwreL1Gh//kQG2ott7/KZGcZwL2S/sgrzdIkCYg/0Yx3mkMXSTDv8JTh0ErYN8R8+Oyh5dWwYul73h0Ue8YfLf9CUywk2K4ZwQ/+xS+/3g5nbZPnugMRPTzKEnR9RisxpgmVvA4v+BauWvxKok4jb0cJrgn6jXzi0PDw4Ordeb9e7V3h3etvlqdOP9er3+LwM3yU0=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Bridge Integration Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/bridge-integration"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the Bridge integration status. Supports two main operations:
-1. Opt-in to Bridge (status: "OPTED_IN") - Creates KYC link for organization onboarding
-2. Create Virtual Account (status: "READY_FOR_DEPOSIT") - Creates virtual account after KYC approval
-
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"required":true,"content":{"application/json":{"schema":{"type":"object","description":"Request to update Bridge integration status","properties":{"status":{"type":"string","description":"Target status for the integration","enum":["OPTED_IN","READY_FOR_DEPOSIT"],"example":"OPTED_IN"},"email":{"type":"string","format":"email","description":"Email address for KYC verification (optional, defaults to user email)","example":"john@example.com"},"full_name":{"type":"string","description":"Full name for KYC verification (optional, defaults to user name)","example":"John Doe"},"kyc_type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"}},"required":["status"],"title":"BridgeIntegrationPatchRequest"},"examples":{"opt_in":{"summary":"Opt into Bridge integration","value":{"status":"OPTED_IN","email":"john@example.com","full_name":"John Doe","kyc_type":"business"}},"create_virtual_account":{"summary":"Create virtual account","value":{"status":"READY_FOR_DEPOSIT"}}}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Bridge integration updated successfully","content":{"application/json":{"schema":{"type":"object","description":"Complete Bridge integration information including status and related data","properties":{"status":{"type":"string","description":"Current status of the Bridge integration","enum":["NOT_ENABLED","NOT_OPTED_IN","OPTED_IN","READY_FOR_DEPOSIT","ERROR"],"example":"OPTED_IN","title":"BridgeIntegrationStatus"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"kyc_status":{"type":"object","description":"KYC verification link information","properties":{"id":{"type":"string","description":"Unique identifier for the KYC link","example":"kyc_456def"},"full_name":{"type":"string","description":"Full name of the person undergoing KYC","example":"John Doe"},"email":{"type":"string","format":"email","description":"Email address for KYC verification","example":"john@example.com"},"type":{"type":"string","description":"Type of KYC verification","enum":["individual","business"],"example":"business","title":"KYCType"},"kyc_link":{"type":"string","format":"uri","description":"URL for completing KYC verification","example":"https://bridge.stellar.org/kyc/456def"},"tos_link":{"type":"string","format":"uri","description":"URL for accepting terms of service","example":"https://bridge.stellar.org/tos/456def"},"kyc_status":{"type":"string","description":"KYC verification status:\n- not_started: KYC process not yet started\n- incomplete: KYC process started but not complete\n- awaiting_ubo: Awaiting Ultimate Beneficial Owner verification\n- under_review: KYC submission under review\n- approved: KYC verification approved\n- rejected: KYC verification rejected\n- paused: KYC process paused\n- offboarded: Customer offboarded\n","enum":["not_started","incomplete","awaiting_ubo","under_review","approved","rejected","paused","offboarded"],"example":"under_review","title":"KYCStatus"},"tos_status":{"type":"string","description":"Terms of Service acceptance status:\n- pending: Terms of service not yet accepted\n- approved: Terms of service accepted\n","enum":["pending","approved"],"example":"approved","title":"TOSStatus"},"rejection_reasons":{"type":"array","items":{"type":"string"},"description":"Reasons for KYC rejection (if applicable)","example":["Incomplete documentation","Address verification failed"]},"created_at":{"type":"string","format":"date-time","description":"When the KYC link was created","example":"2025-01-01T00:00:00Z"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"}},"required":["id","full_name","email","type","kyc_link","tos_link","kyc_status","tos_status","customer_id"],"title":"KYCLinkInfo"},"virtual_account":{"type":"object","description":"Virtual account information for USD deposits","properties":{"id":{"type":"string","description":"Unique identifier for the virtual account","example":"va_789xyz"},"status":{"type":"string","description":"Virtual account status:\n- activated: Account is active and ready for deposits\n- deactivated: Account is deactivated\n","enum":["activated","deactivated"],"example":"activated","title":"VirtualAccountStatus"},"developer_fee_percent":{"type":"string","description":"Developer fee percentage as a string","example":"0.5"},"customer_id":{"type":"string","description":"Bridge customer ID","example":"cust_123abc"},"source_deposit_instructions":{"type":"object","description":"Bank deposit instructions for sending USD to the virtual account","properties":{"bank_beneficiary_name":{"type":"string","description":"Name of the bank account beneficiary","example":"Stellar Bridge"},"currency":{"type":"string","description":"Currency for deposits","example":"usd"},"bank_name":{"type":"string","description":"Name of the receiving bank","example":"Wells Fargo"},"bank_address":{"type":"string","description":"Address of the receiving bank","example":"123 Main St, San Francisco, CA"},"bank_account_number":{"type":"string","description":"Bank account number for deposits","example":"1234567890"},"bank_routing_number":{"type":"string","description":"Bank routing number","example":"121000248"},"payment_rails":{"type":"array","items":{"type":"string"},"description":"Supported payment rails for deposits","example":["ach","wire"]}},"required":["bank_beneficiary_name","currency","bank_name","bank_address","bank_account_number","bank_routing_number","payment_rails"],"title":"VirtualAccountDepositInstructions"},"destination":{"type":"object","description":"Destination configuration for converted funds","properties":{"payment_rail":{"type":"string","description":"Payment rail for destination","example":"stellar"},"currency":{"type":"string","description":"Destination currency","example":"usdc"},"address":{"type":"string","description":"Stellar address for receiving USDC","example":"GDQP2KPQGKIHYJGXNUIYOMHARUARCA7DJT5FO2FFOOKY3B2WSQHG4W37"},"blockchain_memo":{"type":"string","description":"Blockchain memo for the destination transaction","example":"12345"}},"required":["payment_rail","currency","address"],"title":"VirtualAccountDestination"}},"required":["id","status","developer_fee_percent","customer_id","source_deposit_instructions","destination"],"title":"VirtualAccountInfo"},"opted_in_by":{"type":"string","description":"User ID who opted the organization into Bridge","example":"user_789"},"opted_in_at":{"type":"string","format":"date-time","description":"Timestamp when organization opted into Bridge","example":"2025-01-01T00:00:00Z"},"virtual_account_created_by":{"type":"string","description":"User ID who created the virtual account","example":"user_789"},"virtual_account_created_at":{"type":"string","format":"date-time","description":"Timestamp when virtual account was created","example":"2025-01-01T00:00:00Z"}},"required":["status"],"title":"BridgeIntegrationInfo"}}}},"401":{"description":"Unauthorized","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}},"application/json":{"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}}},"application/json":{"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.api.mdx
deleted file mode 100644
index ab9c4a9012..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-organization-profile.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-organization-profile
-title: "Update Organization Profile"
-description: "Updates the organization profile details. Only account owners have permission to do this. Note: both fields are optional but at least one should be sent in the request. It is not necessary to set the header Content-Type for this request. It is set automatically by the HTTP client."
-sidebar_label: "Update Organization Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWF1z27YS/Ss7eGkylSjH7b0PfHPTdJJ+2J5amTsd22ND5FJEBAIosJTKaPjf7yxA2rStOk17O3Mf6geLIhYHZ3eB3QPtBcl1EPmlOPNradRHScoacT0TJYbCKxe/5uK9KyVhAKoR7MQSnLeV0gglklQ6ZHBmdAeyKGxrCOzOoA9Qyy2CQ9+oEHgSWSgtUK1CBqeWMIeVpRoqhboMID2CjQtLDauWQBJolIHAGoRQ21aXsEIIaAiUiZw8/tpioAzeEagAxhIYLDAE6TteLiBFuxpliR5eW0NoaL7sHEJlfeTyGITnyJZsI0kVUusOVl0EebtcnkOhFRrKxExYhz4G4115F6lpNM9TiMRMDAt8Y8tO5HtRJBb82LSalJOeFpX1zbyUJPl1KGps4hN1DkUu7OoDFiRmwnlelhQGHtV2bSdWgbwya/E4icsagS3BVk8SOYOYRgaApg3EAXZmDdbDB4dr9pOZSRK5WCkjfSf6mRh5Pr/uCXx/cXYKaRSolgTsulQmbahh73Ce2hi9LCbobryyWtsdz91gF3KA2ynzGyMbvIUXCf5lHqcY3AG/P+zqLakGP1qDNy0VN7aqAtIhhNEMksnvgKlwI53zdiv1DWdYeSxv4cXKWo3SvMxhVyPV6OPc0RJ21m8qbXe809DIlcaSg20sZXDrsUC1RX/jca0Cpe110/B+XuMNYeO0pCdOD+MwjqcTQnY4IQkygDJbRSkT2PDwdJEMLtCUaVSFdCQBG0cdn4eUj9sSK9lquoWt1G06QIppW3L/K5LhjgXC2fKcDQrbOI2Eg+U9Z+A4/hXi31kP+Jtk+By+2F+JJ/vrSuRwJU5xd+bXp/H7DK7EgW2UDL88Os6PjpLRoe3BVuRb5PE/luuE+4ttUzGV4GTXcOR2MiWTfelsC5W3Dez32bQCMeO+z+C1VsWGB3+eLPWjMpu+v98H6LNE/FA2Ew2GX573Pe/dzrb+8Hrgaj47W/SqUkXKVGFLzK5E/8WVmVaUD8Ea0cc/rpLBWRNSZTs+OuKPhwXl7Acxm1ZP6ZweVlhEqAelcww6d7nBH25wz1fU0fBJcWOGpEjzq5+S0c8DYa6IwzZ6ACEOdsxU6koIbcGNqmq17kSKwNdHr546/d7Ilmrr1UcsP8f95/1E760/4CV7Ql6GTyMEktRO7UzbrNAzxDNB7B/GaqAhTm3sufdu3rMY1/n66NUE+fGMvxM4pearp6n5zvqVKks0f39eDnt3T+APGEQ/AhatV9SJ/HIvvkHp0Z+0VIv88rq/5jBQbVnOOElFzewkD4rFdCsLhvFcriNK67XIheDpI/oFe5scmq5x55V06gfsngiG7/+zhDZgGYsa5wANDYGcQVBrgyXsFNUgDby5OP7Xv8F5teVmssGOpQqXbBYeQ/pGtorBkwSMgVKmSrJpOM8XhFpLD9+qsGp9wFhgz7UkLlRwcv5OzAS7m1geZ6+yI45B2zSsh5LAeh7jxcW35y+5bEoga1neKk3RzWlgoxRq5AZh1erNWOrjWwlrb1vHUsRjoZyKA3Y7yItxdYPEAiM7qAH/vyhemSuz5JbNSxqwDs082NYXyKWSD0eSjCoMVOIFwo1i7BHcDKQp4wC3GiikYSVb2daUceIDOenR2aDIeoUhZx5zuAwJbzF8zstJkOZuCNJ8JYsNmvL6RU3kQr5YrBXV7SorbLP4LISXOSzT3WOg0j3UxoNZ9EqZystAvi2o9YOD6fLyiZxmn+FZ5WMB+yuujRCf8m2HKxht/7Q3NepmXtTSU3iW8sRuQR5x0UhlFsOLZ/35lBtvUTcQgSL/Ep223ahdnz9rbYi3mnaF3iBhyKIsIvRNOKsu0G9VwXVpdGugmVm/XkSjua3mYTCbCa0KZBmS7+8KoJNFjXAc61Sqz4yVLxa73S6TcTSiDVPD4sd3r9+cXryZH2dHWU2NjnXS2UCNNBPgdMuFqeiD+3vug5Izuef+8zPCMz8jDC2R8DdaOC2VYQUVc7Yfuu/lAyHJGra2gfj9fr+SAd973ff8+tcWuR9dXs/EVnrFl8vY2Gdj8+N2vUFuWVMXuLvxvUjkB3+P6GfjpJOiQEcT8ydK54GGOD9Zvn4rZmI1/O7R2JInMXIEnt0/JpbyiUrYRJUwPDD7cch0ExqP+31iy/+Z+8Ep+33SIH1/Z5+GfnfGEMLRmvN03ff9fwEWx+eE
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Organization Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/organization"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the organization profile details. Only account owners have permission to do this. Note: both fields are optional but at least one should be sent in the request. It is not necessary to set the header Content-Type for this request. It is set automatically by the HTTP client.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"multipart/form-data":{"schema":{"type":"object","properties":{"logo":{"type":"string","description":"The logo of the organization, file type must be png or jpeg.","format":"binary"},"data":{"type":"string","description":"A JSON string that contains the details to update. Contains the following keys:  `organization_name` (string): the new name of the organization, `timezone_utc_offset` (string): the new timezone offset of the organization, `is_approval_required` (boolean): whether the approval workflow is enabled or not. `receiver_registration_message_template` (string): the message template sent to the receivers inviting them to registration. Sending this field empty sets the `default` value for it. `otp_message_template` (string): the message template sent to the receivers sending the OTP to complete the registration flow. Sending this field empty sets the `default` value for it. For example: '{\"organization_name\": \"NewOrgName\", \"timezone_utc_offset\": \"+02:00\", \"is_approval_required\": true, \"receiver_registration_message_template\": \"You have a payment waiting for you from {{.OrganizationName}}. Click {{.RegistrationLink}} to register.\", \"otp_message_template\": \"{{.OTP}} is your {{.OrganizationName}} phone verification code.\"}'\n","format":"json"}}}}}}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"organization profile updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-receiver.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-receiver.api.mdx
deleted file mode 100644
index 2158cfee5f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-receiver.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-receiver
-title: "Update a Receiver"
-description: "This endpoint allows an organization to add and update information on the receiver, including email address, external ID, date of birth, personal PIN, and national ID number. The response includes all information on the receiver."
-sidebar_label: "Update a Receiver"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWVt32zYS/is4eEq7pETdZT1VseTEie06lhO3cXNUiByJiEmAAUA7qo/+e88ApCxZsmU3zW7P7r7ECjHXD4OZweCWGjbTtHdJzyAEfg1K008ejUCHimeGS0F79DzmmoCIMsmFISxJ5I0mTBCpZkzwPxiSESMJiyLCRETyLGIGCBdTqVK3igQxEFUo8QgXYZJHXMwIpIwnyKtAa4/AVwNKsIQcDjxi5cgpmXBlYo9koLTEtdPDE8+qEla8pSYiTyegKuTcKtKZFBoKPaDR7McsqlCPygyUXTyMaI++t16UsFCPZkyxFAxC1Lu8pYKlQHuUR9SjHGHKmInpfewOB2g/avq9FPU76lLwJecKItozKgePajNPUJzmaZYA9Sh8zRIZAe1NWaKRIIwhZbR3S808s5RGcTGji8UnJw20eSmjOVKsm3DEtUEjphySSONGZcyEMZlKtQYB9WgohQFhUMaP1R/xz4ZaOfkMoUE4FOJlOGirkhkYy+nY7tSmlfdhGaxubInQ0pCFRzOEdJeU0zIeeATC8CkP3d66SNgmtoyXMY92iz9ZCa4tsmzg7pYytPG9zcVYChg7W5/gK1I/4ll5bp7k2fDukG3KssKYDcPNjaW1vW7gBzU/qNFil2it3mjSe9jaj612p7tHl0jRzzIWPxWyK6FM6T2zl/+r1Rvok+HGHopTjNfy+Jy5WKcLNHT9GNkP7uDboKwHweZxcOc6IqU8MgDDeKLXw59lWVKEU/WzluI5Z2H7DiwxpdNuYzJpN7p+FLGm36xB2+8G4Z4fBQ1oA4R1BtOnBMidxH/VWq1WvdHuNjutJwTDHWOuVa3eaDQfjec78s+RhJ+QrCLVDHlCBQjmmJnHGetBveEHdT9onNeCXrPVa9UqQRB8tLssDUvGGZunIIzeIQcZdB6GoPU0fxbXlPEEoidyBNTGUsq44GL2PKYZ1wYUROMbliSwi6nmmGwsRmOWynxdD1OKzbHEGEj17thjWoMZh7ZyPKb2/Wiwj5odPdc63xVjr16+HDQ7hwfto4u3ndPO8WD4YbR/cdYZnL6/+NA4+bUxOH83/HBw1Dzpnzf77143Ph4dHRz1W1v824FIEFSCwOahMgH0HRt+2gT1mQjtOhLdoBE0alHTr0VB0292O3v+pB3t+VHYajdr0729bhdWfFLfrjGo70EdosCfwqTtN8Nm4HcnzY4fdBtt1m11mjVWX4OjTF1H3FhTHCbfbkiLRWwPopbfbLWY3+x06z4LAPxaO+i0OxBEMKm5KpruCK8PfKKYMKSvNcdc7dFYppCx2Q6+2JhM96rVa8fPsszWiVXnL6yzpevaQJIwNS76xx0hvP9L/03jlzeND28bbw5eN94dDw5+Hr09rp8cH398Ofq58eHwvD18f/ruYjS4qL/pNI/rjbOz0dGqohRSuaULWycYu9UtVH9HwnT99bfJ4OKaP0vG3qaMhGkzTkFrNoOxBmEekLZefw1PQRuWZuQmhvUmnKDE8n94lyDWTNfUsYnMDTF4FynifZudteBvKDAl6bg05Z9UXv5fKZ5YKbRhJt+OqchTvPMOzvoH59SjZ8P+4Ff799Xh6Hx4NhxQjx4c9V+9Gg7wOnw/72qXg0ZOwVLVOObaSDX/63vybzR5eQy3aXPXZNqz3b+PpLsO28etBWpN62uHzlAYNXfd+31yR719Db8uPNrc1tK/ZNjOu2vB39bFg1LyCfey4vawTE9AHKPrwhXbveuLezeuQjE9FNcs4RHhIstdsivF2Zv8eColXibK34RrsrwOecX3CVNLmglTRAC4EcAEXHo1MCuwdejWtlyYBMtNLBX/wwr+vvA+HbbNw1LclBYeLYrStmnJA2CfSEPW3LyzotTTDGorku9zfE/Bbmsam1tzINWERxGI778v2727M+AJBM6N5qYb6PGBzMV/RXg9HAbTwsVtEdBcjYAz0DJXIRCx5FpGwd4mfPtSTBMeGpymZmtjIuWmq/9JWB8CBKe0mZLXPIKomAFznNIqYNGcMK1lyO2c5oabmDAhTQyK5NqNau+0lbMlJyLNtcHclgv+JYdlXtMQ5oqbuR3cvgSmQPVzHGddfsLx6Vcf26AZCL8YpPoTGc39YsKLv4tJldBcCjf+vYI57T3K6dFrluRLCagoBRPLyM2Kw9jOlO1QrVp2wLp6y6MFRYvVdTlpzhU6aAWUjoxwv9yWrLpz13dk/C3MN4rVm4tzhDCys1/MMTg2daHgEc1n4g5vMhzVW22SKX6Ns9ormFdoefOj/SI9Wc5y/h0Di4r5IQ7arTVFER+5uxEZcD3JlQbsdslpwgw2GqR/eohggdLOynqlVgkQgzxNGbZTNlgel/FiNDj9wUYQMVImZJLzxFg3V18pbOlL2RWQSZ5ckbLvto8XZKZknuE4VEHIM24XJN5KzIp2AeZGqqvKBrT/PBN/E78J+3TD3WtNBsIv8kqmJB5OYmJmcNmZYl9xsnIgfE+ce2/BBYx4EjKB58wmp/ItZSrxaQizkIJMam6k4qB7aIdPLov7cbX460crIPlZAZI/YeEViOjTi3ISMOMmzic4Bag+S8IPPWKdX5oyJ5gDGUeEYyAFmfWKi6li2qg8NLkqHCxfRx7d08ozPJsqm4K/xbVSxC7fbmBCStq/7E0MSeqHMVNGP2ryCl3VKIAq3mqrxYdH/dnlxmtIUmIFWfsjyBI5x/Da6QnJNdJd5RNQAgzoym+YpgyoVP88HYG65uHquKkwE6faVUvky6mvCzKPJjwEoW35KhNgxsIYSN3mKZefUVavWr25uakwu2qlFay6enS4PzwZDf16JajEJk1snsykNikTK4Ld6wRhZOXhcS3R3N6V8v+Zh9miqBn4aqpZwriwUzBlHytcBb1cjmPxHafHI7wDx1IbXLq9nTAN71WyWODnLzlgUbn8hAVacTbBEnV5SyOu8Xe0fHJ9EPcXZ8U96wfy0PvuVpPL4izmK80B9Ypegkd08Qknpa6O3jUZ+06xf47sd4z4QrvwSqJ+GEJmVpY32ry1BuS0f77/mnquNend0tTOgahiN/g4zW5sw+FRttFWXNm2oviBNm516n6D4GzEf9HirSy3t65pWSyW9G7pQY4CqCV+6OJisfgTrog8jg==
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update a Receiver"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/receivers/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint allows an organization to add and update information on the receiver, including email address, external ID, date of birth, personal PIN, and national ID number. The response includes all information on the receiver.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the `Receiver`.","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"List of fields to patch for the receiver","content":{"*/*":{"schema":{"type":"object","properties":{"date_of_birth":{"type":"string","description":"Date of birth of the receiver"},"pin":{"type":"string","description":"Personal identification number of the receiver"},"national_id":{"type":"string","description":"National ID of the receiver"},"email":{"type":"string","description":"Email of the receiver"},"phone_number":{"type":"string","description":"Phone number of the receiver"},"external_id":{"type":"string","description":"External ID of the receiver"}},"example":{"date_of_birth":"1980-01-01","pin":"1234","national_id":"123456789","email":"john@example.com","external_id":"external123"},"title":"PatchReceiverRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Updated Receiver Details","content":{"application/json":{"schema":{"type":"object","properties":{"id":{"type":"string","example":"f83bb638-dda4-41e6-80c9-d03e6eec2aef"},"phone_number":{"type":"string","example":"+15552368475"},"external_id":{"type":"string","example":"usr12334"},"email":{"type":"string","example":"jdoe@mail.org"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"successful_payments":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"registered_wallets":{"type":"string","example":"1"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"wallets":{"type":"array","items":{"type":"object","properties":{"id":{"type":"string","example":"803031d4-1d04-4879-b6d9-dc5641f9988e"},"receiver":{"type":"object","properties":{"id":{"type":"string","example":"029e2ed0-feb6-4c40-8b47-0836a85741a2"}},"title":"ReceiverLite"},"wallet":{"type":"object","properties":{"id":{"type":"string","example":"5ada9ed5-455a-4782-a0ee-160767e0deb1"},"name":{"type":"string","example":"Vibrant Assist"},"homepage":{"type":"string","example":"https://vibrantapp.com"}},"title":"WalletLite"},"stellar_address":{"type":"string","example":"GCXAJ3XJ3VK3JFH3QMDFOSKM2NMMZBSO3VIT6EUPQWSDW2J74M23RRSL"},"stellar_memo":{"type":"string"},"stellar_memo_type":{"type":"string"},"created_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"updated_at":{"type":"string","example":"2023-02-03T10:45:51.000Z"},"invited_at":{"type":"string","example":"2023-02-09T10:45:51.000Z"},"last_message_sent_at":{"type":"string","description":"timestamp when the receiver last received an invitation about this wallet","example":"2023-02-10T10:45:51.000Z"},"total_payments":{"type":"string","example":"2"},"payments_received":{"type":"string","example":"2"},"failed_payments":{"type":"string","example":"0"},"remaining_payments":{"type":"string","example":"0"},"received_amounts":{"type":"array","items":{"type":"object","properties":{"asset_code":{"type":"string","example":"USDC"},"asset_issuer":{"type":"string","example":"GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"},"received_amount":{"type":"string","example":"100.00"}},"title":"Amount"}},"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"status_history":{"type":"array","items":{"type":"object","properties":{"status":{"type":"string","enum":["DRAFT","READY","REGISTERED","FLAGGED"],"title":"ReceiversWalletStatus"},"timestamp":{"type":"string","format":"date-time","example":"2023-02-10T10:45:51Z"}},"title":"ReceiversWalletStatusHistoryEntry"}}},"title":"ReceiverWallet"}}},"title":"Receiver"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}},"409":{"description":"Conflicting phone number or email","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object"}}},"example":{"error":"The provided email is already associated with another user.","extras":{"email":"email must be unique"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.api.mdx
deleted file mode 100644
index 99c986c543..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-activation-status.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-user-activation-status
-title: "Update User Activation Status"
-description: "Updates the SDP user’s activation status. This endpoint is primarily used to move a user into active status when they accept the invite to join an SDP organization account and create a password."
-sidebar_label: "Update User Activation Status"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV21v2zYQ/isEP62F5LfYefGnpWmHthu6AE6wD24QnMiTxUYiVZKy4wYG9jf29/ZLhqNkW64zZ+lQYNgXS9Ydj89zx3vhA/cwc3w85dcOreM3EZfohFWlV0bzMb8uJXh0zGfIJq8vWeXQ/vn7H46B8GoOpMWcB1+5DrvKlGOoZWmU9kw5VlpVgFX5kpZJ5g0rzBwZBCtMaW9qM9iYYIsMNW21ZCAElj5sq/RceaTVn4zSDHQAYuwMtPpSIwAhTKU9Ay2ZsAieNinBuYWxssMjbkq0QfWd3JAixucbFpOAgEfc4ucKnX9l5JKPH7gw2qP29Pqy+5IeTmRYAL35ZYl8zE3yCYXnES8t7eMVOpISyVslW4rOW6VnfBVx5W5r5i1pYkyOoPlqFXG8h6LMcccMHwkYHPXEWSzhbBQPE9mPkwEMYoCR7Mn0eISp5Du2U8gdrlZkkWgpi3L9kb640mhXgx30evTYDf5FcCXZbHkByjJXIvis+8mRXtsl222mHAtQOY94qqzztxoKJHS7ECOew1ZoTY7hEB727GNObfmM90+OjhOUR/FJcjaIhyfHvfg0TQfxqJ8mvVPE3slZSlFoATto773JNOlvoR5Uf22QtGv6j0W/prmVgLWwJLd4LNwjK55zYKa1e/gJDMXxaDSK++nJUTw8S45iGPT7cXo2SuQgOUVx1tuNTcNzh2bgsqFSP38Mvx1hik3ExlMucY45BYnC10LrbYWrqAE1Socy7UsZi9NhGg9PBxCfDkHGo2E/TeXwGE9GsAcKNH4rqFRp0EJBfksH2Jo838NXZwMdOeVD9Kgs8N0ULNA5mJEwFK5W6VuAY1WoJpK5Sgh0Lq3yfMnrpBv2+vtZda2h8pmx6svzUutwTqC1xj562vDeW3BPW6hrcEtPV0VS+2LjgP2j+VW1amDwD8azHZpbFOt9hr1+y/LXK76n4To0R/uh+cnYREmJ+vvH5XF2WwD/QCHwcCgqq/wyZP4rBIv2vPIZH09v6FTfx8JInKGOm74WJ0Yu4yaR6L12IWqnjHbByh0u+fjgyojPIa82FmijAn1mKMdL8CIjNwCh4F1KGdfd5gwnzHZO0wZtVlnK4WBiTWVCrq291ya0LZel+hkJ927w3v92Vc8ZqbEh4Kh9E7WIOTXTKNlC+YwmiDeTweiY5pM5zQp3uKQhoXHKeXNW1mgVGc8QJOUClWKdmoCmKRgTj3kOlr1WLqmswwK1Z5c5+NTYgp1fviN3oXU1ykGn36HC66qiAEuOvqLR6qCNHyavL1/QQAXMG5OzpFK5DzTbU5ALAxbcIUuq/I6VsCQr4SuwmTVVyUzKLApVqiAwc7T1YNfsrtEvjL3r7Ln2vwfxo/6ow7xJW2pmStSxM5UVyEprKBOZzyBMoTUUo5k3wfwj5qIwOZKAzjwToFmCLDWVlmFhRn/y3CyUnjGLpXHKG6vQjQlHzKauttdtnrFsOSkuGyfFCYg71PLmh8z70o273ZnyWZVQ1+o+y8KLcT1sb6AsGZUrULqe1Bu1wErp1ILzthK+sg1Biot/KqadZzBLbaiW/4ba2sRT3BaYsLXuN7PJMC9ikYH17iDkll7XW8RuAUp3mw8H+TxF4y3mBQuGAn6JZW6WdLyeZMIqR3p3VYJWo0fX+UhlyqMt3K/pBO1cCapLa1oNzI6xs25Qik0au0Yt4rkSqF1oMusCWILIkA1CnarrM9kad7uLxaIDQRqsNUtd95d3F28+TN7Eg06vk/kiD3WyNM4XoFuG63sXowmLbW9ebHP12ik6ravX/+UW2vQvj/e+W+agwqUiOPihaZfTMGGSL1oN8ybimXGepA8PCTi8tvlqRZ8/V0gtZHpDDdkqSMIN4GYVrfvVtp1f1M6MrwjDtn/TnZbG81rpPPBtifcmn51Wf3l+dfGWR/UQQHOykbTIwoKGcFiExh5x2Gvfd6F9Ny+EcS3Sy9bmXzfiGiP9EuJHlzw81MPBarXRr0V/u6Jx1FqbYnKzWq3+An7c+m0=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Activation Status"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/users/activation"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the SDP user’s activation status. This endpoint is primarily used to move a user into active status when they accept the invite to join an SDP organization account and create a password.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"user_id":{"type":"string"},"is_active":{"type":"boolean"}},"example":{"user_id":"5ca230c9-da95-4bd1-b2a2-aa5d0df65efd","is_active":false}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Created","content":{"application/json":{"schema":{"required":["email","first_name","id","is_active","last_name","roles"],"type":"object","properties":{"id":{"type":"string","example":"1736bed3-7b92-4760-8ff2-51fb08ee079f"},"first_name":{"type":"string","example":"John"},"last_name":{"type":"string","example":"Doe"},"email":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}},"is_active":{"type":"boolean"}},"example":[{"id":"7a4c6555-1f73-49b3-a211-f95bd2b8ec90","first_name":"John","last_name":"Doe","email":"email@email.com","roles":["developer"],"is_active":true},{"id":"5f4df1dd-c84f-482a-84ad-541ffd46e75a","first_name":"Jane","last_name":"Doe","email":"email@email.com","roles":["financial_controller"],"is_active":false}],"title":"User"},"example":{"message":"user activation was updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-profile.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-profile.api.mdx
deleted file mode 100644
index 830476516a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-profile.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-user-profile
-title: "Update User Profile"
-description: "Updates the profile details of the logged in user, including changing password for authenticated/logged in users. Note: all fields are optional but at least one should be sent in the request."
-sidebar_label: "Update User Profile"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdV91v2zYQ/1cIPq2FbKVZtwc9Lf1Cu3ZpsCTYg2sMlHSyWFMkyzvF8Qz978NRkj+SzFk3FBj2YtG8z9+P1N1pI0ktUGYzeRFcpQ3IeSJLwCJoT9pZmclrXyoCFFSD8L2SKIGUNihcFbeNWyygFNqKFiEkQtvCtKW2C1HUyi544RXiyoVSVC4I1VINlnShCMr00Bqn4twRZEIZIyoNpkShAggX81FG5C0JRcKAQhLOgsDataYUOQgES+yHcwrwpQWkqUyk8xAUW78rt3iuEcIIOZGD8gtXrmW2kYWzBJZ4+TR9yg8samgUr2jtQWbS5Z+hIJlIH9g9aUCWVjog/W5VA3u6SEHbhewSadQxKTRKmwclI3sPCNnuVjXewN348g3/Oef1QWT5QW23h5D986f4Oy1cI/dDymaNUAQg2XUcjsnSAUqZVcogxB30zmJPwenJCT8OL9HH9zLZp1V5b/j4tbPpZ2SVfY53EWayAUS1iPfyOPWj4oMUkSYmSP7SK/06JCwP2du6kHwTt7e9jTemFNgWBSBWrTHrgYvnJ8/ug722fMFd0H9A+TWwj+ODEFx4+N7cUlD4uAckRe2+nm2bHAK7OELenRs2pCHPHYkDmLssxjjPT57teb5r8S0d90fz/f2jeeNCrssS7Lc/l4fR7RL4GwoRB0LRBk1rmc028gWoAOGspVpms3k3T+TtpHAlLMBOhiI2yV25ngyvOq97CsGidhajlyWsZXbUMpE3yrRbDxyoAaodlwOvqKhjheAsZOq3ZRQh3EDoY7SB60q0HBFcMqM9afs4tswpr98Dp3t4Zj//dsWd4V7r0M4mAvXCQilWmmqhrHh9efrDj8IHfaMIxBLWXP8HLs6GKxItZSI1O69BlfwKdPy/cjGboVZcEhijgnilMW8DQsPd5cIoqlxoxNnFO2YJAvZZnk6fTU+Yg7ZpVGB+r2oQx318d/nq4onQKJQg57i1aUMRpgsLZYdUUZATjVqCyFuzFF6t2UvcVWIRXOu5DwcotNdR4G4gxB44RrdAKxeW03vU/vdS/GQ/2ataYwxphfNgJ+jaUMThg19AQbUiFvepOCvI+XESueMuEcqWUcBXXRTK8phQudaW0bDmP8a4FY8oAbxDTS5owIzzmIgZ9v7S4Tkp90ia+IGkSa6KJdhy/l1N5DFL04Wmus25k6Zf5eFJJiL4bSprwVVKadvPX4NaRKVtFRRSaAtqwwCQz4UeO9PpVyCrQiyS/wba6OIxbCvIxaj7j9HUYJpJUatAeDTlPb2UAkDaKG3TYeMonsdgvAXTiOgo5l+CN27N1+tRJKJF1lu2OQQLBDj9xGWKIDT4sbqEcKMLrksjrCHNqQuLNCpNXDXBQS2RRhfAI0622RZAr4oaxGmsU319Zl9Zmq5Wq6mK0uhtMMX0w7uXr88vX09OpyfTmhoT66R3SI2ye477kVrwTC12Q/VBqdkbqv8HXxRDwyK4pdQbpS3PUJHRzdAWZ9LvPqhqh8Rbm02uEK6D6Tre/tICN4rZnLtt0CrntjObd8nYlXa9+mVP3uSKA++aM3+ddMmodFYU4GlPfG+sOejjF2dXL9/KpO/wPP26ko2CWvEXkVrF9p1Ida9JL2OTHhac4yiy673gd9ttnyP/csYPmmw2/QjQdVv9XvSXFgNRozYfxLzruj8B2ak/fQ==
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Profile"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/profile"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates the profile details of the logged in user, including changing password for authenticated/logged in users. Note: all fields are optional but at least one should be sent in the request.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"first_name":{"type":"string"},"last_name":{"type":"string"},"email":{"type":"string"},"password":{"type":"string"}},"example":{"first_name":"FirstName","last_name":"LastName","email":"email@email.com","password":"mysecret"}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"},"example":{"message":"user profile updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-role.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-role.api.mdx
deleted file mode 100644
index d3a7d4a378..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-user-role.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-user-role
-title: "Update User Role"
-description: "Updates an SDP user’s role by  `user_ID `."
-sidebar_label: "Update User Role"
-hide_title: true
-hide_table_of_contents: true
-api: eJzNV1Fv20YM/iuHe1oLyXLcpkD1ljYdmnVogznBHlxjPeko62rpTiVPcTTDwP7G/t5+ycCT7NhNlrTrCuwlkkXyu+8jJZJZS68WJNOZvCRAkvNIaqAcTeONszKVl41WHkgoK6an56IlwL/++JMEugpE1gnxgR/9dnYqPoxkJF0DqDj0TO+CGfkXV4GMJMKnFsi/cLqT6Vrmznqwnm8fJ4/5QnkJteI73zUgU+myj5B7GckGGdsbILaGQ43ecySPxi7kJpJMjfYsClF1MpLGQ013RGw2kYRrVTcVHEDL41xNnozz57FWz4/jp5k+irOJmsRKHeuxLp4dQ6Hl7ryZ1HAFFbOU801AZbkGQcu0UBVBeEKNs9Tzm4zHfDlM+Ls3MtpPjGqayuQhp8lHYpcvz1INRGoBd2k+kLzzC+JDbUmsAEG0oYJaUJvnQFS0VdV9czTHPx0f3dZ+aVXrS4fmd9D/XRYA0eGdbwpce1T0MAJ55dt9P9vWGSBD3JPiz9I00JBvnRcHMm9YbM95Oj7aQ/484nsC96V5crs0PzrMjNZgv39d7lZ3Q+ALHIIOgrxF4zuZztbyBSgEPGl9KdPZfDOP5HWcOw0LsPHQleLM6S62qmYyfN+nECwZZymgLKGT6b2RkbxSVbtD4INq8KXjftIon5ecBsUsZMKfCyV9+2C6eMUtmM9psZKpDNFbFVPOap+4fS03Xa4xb4ApH9btp18vuGlrUTgMtQbrh4JFgszCghYr40tu8K+mk+NnokFzpTyIJXTc0Yd8nAyvSYjkZsrgJSjNn8GGfxcusDGeyyKnHqpKoTg1lLVIUIP14rxSvnBYi5PzM84UIPUsJ6Oj0Zhz0Na1Qs7xRQnifowfpqfnj4QhoYR3rhJZayofZDpcKDtQJeGdqNUSRNZWS9GojlHCUyUW6NpGuEIg5KYxweCuAIXfO92CXzlcjm6l9v9H8b19by9KQ+FIK1wDNibXYg6iQccfofCl8mzuqTgrvAvwd8BFQlkdDPy6i1xZkYEoXGt1CCz5R1W5lbELgdA4Mt6hAUqZRyxm1OMlwzXWe0mKmyFJcabyJVg9/6H0vqE0SRbGl202yl2dfBXCo1QE8TsqneBOpQxnuAQxuAVVxhaoyGOb+xYHgVwX/1BNR1+hrMDQKL9F2hbiIW0ryMTW91+rKaGq47xU6Oleynt+iUeApFbGJsODe/U8JOM1VLUIQIG/hqZyHb9eDyoRLbHfss0ALXig0XtuUx6wpnfFFPDK5NyXtrIGmiOHiyQ4xa6IaXCLZGVysBTmy7YBNiovQUxCn+r7M2OlSbJarUYqWAPaEErJz2cvX72dvoono/Go9HUV+mTjyNfK7gH3S7LgLVkMa/JBn9lbk792Gx9Gg4drnzSVMpY3lsB9PQyhWdjZaLfFziNZOvJsWK8zRXCJ1WbDjz+1wI15NucJh0Zl3OZn8020nQI38/Flzze+4ONvBiKv+Jto63SS59D4PfOtVeJgdp6fXLx8LaN+qvLS6TQHoVoxd7UK4zKS6tZQXIahONwwx63JdnuHfz7eeo78lxnfGbJe9yN3s9n596Z/jBgStfXmcvA/Cn8DgWvBcw==
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update User Role"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/users/roles"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Updates an SDP user’s role by  `user_ID `.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={undefined}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"*/*":{"schema":{"type":"object","properties":{"user_id":{"type":"string"},"roles":{"type":"array","items":{"type":"string"}}},"example":{"user_id":"5ca230c9-da95-4bd1-b2a2-aa5d0df65efd","roles":["developer"]}}}},"required":false}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"OK","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string"}},"example":{"message":"user roles were updated successfully"}},"example":{"message":"user roles were updated successfully"}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-wallet.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-wallet.api.mdx
deleted file mode 100644
index f2c03176e5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/update-wallet.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: update-wallet
-title: "Update Wallet"
-description: "This endpoint is used to enable or disable a wallet provider. Note: the organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement."
-sidebar_label: "Update Wallet"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWF1v27gS/SsDPrWFbKdB733wW9oEaHa73SBp0QukRpaSxhYbiuTyw67X0H+/GJKyFTuNs7tY4OLmJYk0c2bmiDNzpA3zfOHY9JZ94VKid2xWsBpdZYXxQis2ZZ8a4QBVbbRQHoSD4LAGrwEVLyWCtlALF//ksIooYKxeihrtGD5qj1PwDdktuBJ/cIIF1+gga6i0trVQ3COshG+i3R4ElDjXFsGhxMoLtQAOhlsvqiC5PbCeawucEiqDddii8mNWMG3QxsCXNZuyz6bmHlPBrGCGW96iR0s8bJjiLbIpEzUrmCACDPcN22fl8hz0fJiv1xAiLiuYxd+DsFizqbcBC+b8WhKmE62RZIDfjdQ1sumcS0cGVYMtZ9MN82sTLb0VasG6bpbQ0Pm3ul6TxcM8vmyjl5gToMQrrTwqT/bcGCmqWP3kmyOnzWE8XX7DKpJhiSsv0NHdxMV+VvtcvA8tVyOLvI6ngJz2yOkfD+sK1ugWDV88BzdbwufrD08A1ojmTgp1f/cjGveBzxENkAckj3hqBugDyiiAQ3P3+uSukgKVv6t1y4U6HuTm4mr0+gSSFySvdDyDb1D5QYDUSfUAs9RaIlcHoF8a9A0+SDZ2Z/SP6MEhQXLnqJt3iNxavj7AO6OrxG20B4tztKgqdOCCMdp6rKFcg6cZsOobRnhsI7RW+Os8Ns3+MdqL8hCcEC/PDw6bqI+TmpAuz1nXDdvslpxnXXEskXeSOyeq/WoPUkkoh8mgCi1FqxIOhWRVbOTnJR5tu4IJ5wLa53ola+B1bdG5g9IjRM5jC/0MMj5yL5YI//nwy9/mQ0UoNns0tVk36+hGK9TVAPV1wbzwcS4OB/J1mnase4hFgzRecEYrl7I6PTn54UDMoxBcqCp0bh6kXD+ci68mrx6OwmHiLTpHM2pWHJmQveEjo3tX3y/J6DonT7V1BXvzWPpveQ154BcQXOBSrqHicefGRkT4Lbf7bzAXKGtohXO0F+dWt9Eg+0Op6/X4SNFPV4fW6mcc03P0XEgHvNTBxxSSI422795ydzRSJAS/87gfd4HZpVpyKWoQygTPhnCx9ru51my6+5uG4fYxFvl6ye3WpuQWFGLt8sbkCoTyuKBN0vWP5c0PT5XSHuY6qPqfYPX5bDHnuQ9DOxXaMm3DJw5kqu8xPfAI8x8Hpe7S6gO/OXkzCMWu0elgKxwQ1Idr0Te6TjKqaqLc8g2bsklaJ26yEXXHaMnaZS/BgpVsyhiJH4dVsMKvb4jbVPxb5BbtWSCY3Xoz4mc83G8/ffmU9Orh4i3AiYXCOilPruDi5vRf/wZjxZL06D3G3slqkKJpm9VrLwwb5FGCdAUjIq93Ou1ix2cG2HbOTv4Mu2lfwezuPS4+hiM4a4ckNfu9f5v26e5sbZnqd1e/uXZQ/VZ6xCkP+I4WnlBzHZnP0+3GoyQpfj4Q3XAluZ9r28LZ1SUrGD3a9EROx6/HJ1RXaFtu1/EFA+FpjBc351cvqbc5eK0llEFIHx/p8KUi9nTL7xHKIO/B8DWhxKscFlYHQ0LHYiWMiDf0MiupPrpCv9L2fnxwjP73Uvyqvqr4ZkYhFWiDapR70FhNQwN8w6M6TKloBV6bXkbvwRXAVR1v0JmAiisajrGRo2ND/0ipV7RnLBrthNdWoJtSHiO4dQlvkn+Phi9gI5NJGpW8ukdVz1403hs3nUwWwjehHFe6nfwphJdTiMVvU1kDjWMuiOEGIZvFqoSaW+68DZUPNhfY6/0nn+n4T1Q2t3Eb/J3Seohjta2whN72L1fToGxHVcOtd0+mPLCbeIs4ofEzyReerOdYGe9RthCBYv41GqnXdLyOVgIhyp37UKJV6NGNv9JI9mhb9+v8Bu1SVDSX+rJymmNtF5NoNNLzkctmBZOiQhJlu1l9ZnjVIJzGOZV2EWFNJ5PVajXm8W5Ey65u8uHy3cXHm4vR6fhk3PhWxp1gtPMtVwPgpHNh++XhwZDZ7BTF/8U3l7w5PH73EyNpa3WZzU3WALcsawBWsCm9wNF2dJ5ubDYld/jZyq6jy78HpFVxOyvYkltBhccVl0motx9Sfsjoi+ssC1/Ck59uHs261xiKBMaSy0D/sYLd4zp9KYp7McsByivdeJeijz6lF7Te8UCA0Z5NHmdVhcYPbElZkgzaqqirs0/v3rOClflrUJt2uOUr+u7EVykxHRmIaile2zDJ1SIk2ZFi0s9/ASmTDgQ=
-sidebar_class_name: "patch api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Update Wallet"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"patch"}
-  path={"/wallets/{id}"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint is used to enable or disable a wallet provider. Note: the organization should coordinate with the wallet provider before selecting a particular wallet provider for a disbursement.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the wallet to update","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Wallet to be updated","content":{"application/json":{"schema":{"type":"object","properties":{"name":{"type":"string","description":"Human-readable name of the wallet provider"},"homepage":{"type":"string","description":"Homepage URL of the wallet provider"},"deep_link_schema":{"type":"string","description":"Deep link schema for the wallet application"},"sep_10_client_domain":{"type":"string","description":"SEP-10 client domain for authentication"},"enabled":{"type":"boolean","description":"Whether the wallet is enabled for use"},"assets":{"type":"array","description":"Array of asset references supported by this wallet","items":{"oneOf":[{"type":"object","description":"Asset reference by ID","properties":{"id":{"type":"string","description":"Asset ID"}},"required":["id"]},{"type":"object","description":"Classic asset reference","properties":{"type":{"type":"string","enum":["classic"]},"code":{"type":"string","description":"Asset code"},"issuer":{"type":"string","description":"Asset issuer address"}},"required":["type","code","issuer"]},{"type":"object","description":"Native XLM asset reference","properties":{"type":{"type":"string","enum":["native"]}},"required":["type"]}]}}},"minProperties":1,"title":"UpdateWalletRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Wallet updated successfully","content":{"*/*":{"schema":{"required":["message"],"type":"object","properties":{"message":{"type":"string"}},"title":"MessageResponse"}}}},"400":{"description":"Bad request, usually caused by the `enabled` field missing from the request body.","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"404":{"description":"Wallet not found","content":{"*/*":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}}}},"application/json":{"example":{"error":"Not found","extras":{"status":404,"message":"Resource not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.api.mdx
deleted file mode 100644
index eeaa4ef3de..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/upload-disbursement-instructions.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: upload-disbursement-instructions
-title: "Upload Disbursement Instructions"
-description: "Adds a file containing a list of receivers to a  `DRAFT` disbursement. This step is required before a disbursement can begin. The file must be a CSV and has a different possible formats according with the disbursement configuration, and they can be found at [public/resources/disbursementTemplates](https://github.com/stellar/stellar-disbursement-platform-frontend/tree/58873bbf36cff4614e603daf449079b1d9fad24a/public/resources/disbursementTemplates). The operation is idempotent, guaranteed by deleting and recreating the disbursement attributes when this endpoint is called."
-sidebar_label: "Upload Disbursement Instructions"
-hide_title: true
-hide_table_of_contents: true
-api: eJztWFtz2zYW/isYPCU7lGg7btrwzYmTWe/utJnY2X1QPGOQOBRRgwAKHEhRNfrvnQOSMnWJk03Tnc5O9SCR4rmfD+B3sOYo5oEXM36pQhl9gBYMBn6bcQmh8sqhsoYX/ELKwASrlQZWWYNCGWXmTDCtAjJbMw8VqAX4wNAywdjd5buLNzd3TI7sTtlNowILCI6pwDz8EpUHyUqorQcmdoRZJQwrYa4MqUHnuo0BWUmir67/zYSRrBEhKdY1eNJyNgRVamC19a3AwERVWS8p2KXChmEDe26sqdU8ekGZZskmNrDq3bPaRiOZQDZzsdSqyj0EG30FIR+buYHWaYEQbp80iC4UeT5X2MRyWtk2DwhaCz/8TsaaE9KjYCe1twbByBw9QP7dDz98/6ws62fPq7o+f356Ds9PnklRn5+/OPn+RXkqX9RCnp2L/MvietpV0TroMqUGKAmtswgGMzaPwguDQO1YMQkaMDXYSGqtB5FuD6onEL0qI0JgywYMQ2owGOmsMkg+KqE1yCnP+Nb1leQFf++0FXKMuisT0MeKJALPuBNetIDgCZ5rbkQLvOBK8owrQqQT2PB9mF5dEhYpyrFlnvEBa7xAHyHjAVea7AXVOg084/DRaSuBF7XQgQSqBlrBizXHlUuS6JWZ883mtrMGAV9auSKJKvUN6bKNGpUTHvPUUikw2Xiw9hDIjBOkaan1Hmz5M1QUrPNUK1QQSCNJHcSxn/k4X6ZGpewWDloWU8U7GNDq6deyjq0JCe0L4anzDkxaLrZNhVyK1WHblyJsFw7I7aphtQJNG0VazSGWAXBoSG21tktl5gWb3bnGGrjL2B20Qmm6UJK+RWujQbpagFe1qhJg6N6JVQLJJd0sCVR4IaWHEO5ueca71c4LXioj/Ipv6LPf9vRHcNaErrJnJ6f0s1vIV4R1IJiN2iqc030w+c+B5NaHCPlE/1oIQcyPtJAChI8iAXAsx99QZ7p2gWQhVhWEOmq9+joVUjo/OTlM9aWQ7F0H5W+XLnhv/ZFkKXD0InzeQm3tUf1HCrlXlz4GfmUWQivZQb2DCPvb9OPqVz6OJvnjpfB85IP/aJGJiI316leQ/H/jomvVEVS+NyPBP1GvAgqMYzkT2xL817Vrrx7jKAY/5yenX9Gkb2G4a82zw9a8sb5UUoL54/tyPLuHAL5AoEvj/DANyvgNkZ3/a3jVfYbHAHA+BsDO+9RsNf9g28l8gCp6havEe16C8OAvIja8mN0S+WgBG0sUytm0byciVPAd2hfytZKbXO1SqgB+MfCp6DUvOCeDg79ramtX97HXbX2FU/+E1QHz+Md/blgMIGn3S2sGDPaIyVhQcwOyo97CsNfXZ989Z86rhUBg97AiYthTu4t+uSXNgeU1ICT1e0P3dfdeUJio23VHpneYHnvbk2l28faKZ5zS7aI8m55OT6gGsW2JIBSceNDjNp5cX759SiRWMLRWszIqjSlN6+fC9KGmiacV98DKqO9ZT1T6OWjubXT9fKScSg/sAnyiRIN3A7i0/n56UNo/X4gfzAeThjhyaWicMJNu7mDOW1rDDBuRmH8XijUMrRtI4J65B+JYWQm7Ixcpjmkj8+BsUGi9glBQHBM2+7LBqhTVPRj5O0az3sLToptgt6GshmE4pGB7sZSVMrUX3fKLvk+Q+oKf6+n0v8hsGBm/wdT5udyWULJB9quzaUC3k6oRHh8flEdy3TTcCmXy/o9H8/lcGn8H3bJkKMUvwWm7Gkbbx9daDCR3H0vwBhDC9ANtUwi+DT/V1+AXqqJ9aUirD3Nq/TxPQhNbT0IvlnGtKjAhvUSGDdCJqgF2lvapbn8mW0WeL5fLqUhPk7VeNeT/unr1+sfr15Oz6cm0wVanfZJeC60wI8PdrL2b1d60vbPvjCbavw5+/jr4+b0HPz19QPiIudNCGaJvCd/rnrzM+A554Rkv+oOeEUhvM94Q4ylmfL0uRYD3Xm829PcvEeiNPrvN+EJ4JUriB7M1GaVruT3U+STKn7zrIfmUffII6WgaAzUyxIsWQke64xm/h1V3WrW53WQDi6GYugevOs+TG1J/UDx2erTJBqWLqgKHI/EDbr5DD9/+dH3DM172h1RtOt1KByXJbvZwScQy4+KA7d0nttdfUPBHs93nbV2w9E2hH1VZrzsuudls5btHn9ToK7gtLOW62Wx+Ay1wFCU=
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Upload Disbursement Instructions"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/disbursements/{id}/instructions"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-Adds a file containing a list of receivers to a  `DRAFT` disbursement. This step is required before a disbursement can begin. The file must be a CSV and has a different possible formats according with the disbursement configuration, and they can be found at [public/resources/disbursementTemplates](https://github.com/stellar/stellar-disbursement-platform-frontend/tree/58873bbf36cff4614e603daf449079b1d9fad24a/public/resources/disbursementTemplates). The operation is idempotent, guaranteed by deleting and recreating the disbursement attributes when this endpoint is called.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"id","in":"path","description":"ID of the Disbursement","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"content":{"multipart/form-data":{"schema":{"required":["file"],"type":"object","properties":{"file":{"type":"string","description":"Disbursement instructions file to upload. The CSV file columns can vary depending om the way the disbursement was configured, and the fields are a subset of the following: [`phone`, `email`, `id`, `amount`, `verification`, `paymentID`, `walletAddress`]","format":"binary"}}}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"201":{"description":"Created","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string"}},"example":{"message":"File uploaded succesfully"}},"example":{"message":"File uploaded succesfully"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"foo":{"type":"string"},"message":{"type":"string"}}}},"example":{"error":"Invalid file format *.xyz","extras":{"foo":"bar","message":"Not authorized"}}},"example":{"error":"Invalid file format *.xyz","extras":{"foo":"bar","message":"Not authorized"}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}},"403":{"description":"Forbidden","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"}},"example":{"error":"Forbidden"}},"example":{"error":"Forbidden"}}}},"404":{"description":"Not Found","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}},"example":{"error":"Not found","extras":{"status":404,"message":"Disbursement not found"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/users.tag.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/users.tag.mdx
deleted file mode 100644
index ca02e0b383..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/users.tag.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: users
-title: "Users"
-description: "Users"
-custom_edit_url: null
----
-
-
-
-The users endpoints facilitate the creation of new SDP users - including setting the appropriate role, sending an email invitation, and activating a user - and managing roles.
-
-
-
-```mdx-code-block
-import DocCardList from '@theme/DocCardList';
-import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
-
-<DocCardList items={useCurrentSidebarCategory().items}/>
-```
-      
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.api.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.api.mdx
deleted file mode 100644
index a80fe7ae08..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/stellar-disbursement-platform/api-reference/verify-receiver-registration.api.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-id: verify-receiver-registration
-title: "Verify Receiver Registration"
-description: "This endpoint verifies the receiver's registration by validating the OTP and other verification values provided in the request body. A valid SEP-24 token should be included in the Authorization header of the request."
-sidebar_label: "Verify Receiver Registration"
-hide_title: true
-hide_table_of_contents: true
-api: eJzdWG1v2zYQ/isEv7QFJDsNun3QN6dx1+wlMWK3w5AGLiWdLc4UqZGnuJ6h/z4cKcVynMXd1g7D8iUWdXzujXf3UFuOYul4csOvYSkdWoHSaH4b8RxcZmXlHxM+K6RjoPPKSI3sDqxcSHAMC2AWMpB3YJ85ZnsYLN2wO6FkLlDqpZe8mk2Y0DkzWIBtQbIgfCdUDY5V1tzJHHImdYv9Ww0OWWryzYCNAiCbjifx6SuGZgWaucLUKmcpMKkzVfc2j2osjJW/Bw0FiBwsM4s+8IBH3FQQLL7IecLfk1Wb69anvaBEvBJWlIBgKWJbrkUJPOF7enjEJQUsqOMP47hn+sJYJvaMfP7G2FJgwp6dgbBg2dZLNs9e8IiTzdJCzhO0NUTc4UaRfifLSgGPOHyqlMmBJwuhHAlkBZSCJ1uOm8pLopV6yZvmNqCBwzOTb0hi38z3/dzkAkUbXMpkVRgNc12XKdghlEKqiDIbPZLQyKfbwuvRZPb67Si4zSOeGY2gkfSKqlLtnuGvjpRvD+026a+QISXAUrZQgqO3Xvmhew9jPiYxJpwzmRQIOVtLLPaObndipucT720qHAzYWPpz+rHv8EdmLPvoFX9k0rEuJwPeRLwveNysCUmzIP1vWGewOm7UlYZ4JktgE+Hc2ti8syL3p7WfYsLcez4K/v7ggOwKPt14H2sH9iHwfCFB5Y/Bg65L6l3no9l4fvVmfnZxPXvLI/7LeHQ9/+nq0j9MLi55xC9Hs4ury9GP84vz+eW7n87G19TkUKIvob5lb7y2hiokExVmhZiHc3vUv5mv6l3ArCnZd8YsFexqgDfNTu1jbeY61CVvmuZhyfsFVxntwvk/PTk5UrquzjJwblGrL1d1JTgnlvBoPj4J34oSblbkgPfh1WNWnomcdZ5+uX5grfmMwjsHFFI5JlJToz91YWNDDqAV7qgm79e9s/eK+YUOA0rqqkbeh/NHeL4whie73/0S5VG7ngp7L5MKyzRA7hgamnBCM6kRllQj99F9eRjdd7obKx7464b388PGHQqs+3Jtr2yiPz9VzZ8F+9Ig23NzZ0Wn59XJyx7ywx1fE9hjf4ozk8MSdNwO25h4TNzSBvodwEE7aXTgFCvY8OTJnRH3rbNDoFleAhaG2EtlfD1VAgue8OFaKAUY92nZcK9lR9yBvev4TG0VT7hHdJDVVuJmSmcjJC8wEiI7vSSJSv4Am4MS+/7nGbXy/J7igMZWZ8ScXOpuzgnNxtPTb75llZV3AoGtYEOk7DOoFUWYjvD1jsiMe8kM3GDXA/aH827dj8Xd4/5Ee3y9G0gHc+dgYvRqROqF8YFre/8UQSlh2bl0aW0dlKCRTZTAhbElG00uglIX7DgdvBycULrqshR24xk5sKcxnk/PJy+oxwiGxiiW1lKhz4ixS6HbqPreUooVsLRWK1aJDaH4VcGW1tQVcWYLmaykf2GIkmBPuwZcG7saHM7D/5yJH/QH7a8ypFIzU4GOnalt5pkI9SyGhUB6HUwxmqGpulvDA7hAb+kFVSvLhKYmvTA13XECZ1sYpcyaaLOFyjiJxkpwCdkRsxsX8Ibt/zjvBSmu2iDFqchWoPPb5wVi5ZLhcCmxqNNBZsrhX0J4kTDv/L0pG0ajQUgdbnKtmPdK6oUVDm2dYW1bBykveCyng7/g2cL6yfRPXOsgjvm2hpR1sn/bmwJUGWeFsOieNLknN0QLMCyF1MN24Ul/jrnxFlTJPJC3P4dKmU13v3661mpHcqs6BasBwQ0+UEdFsKW7WkzB3smM+lLnVmvmwNjl0AvFZhG7ViziSmagnW+1Xa+uRFYAO/V9KowSwkqGw/V6PRD+rUdrt7rhjxevx5fTcXw6OBkUWCrf0mmElUL3gMOVnHVkmT24lO/1nO2O7Pyfv1m00xfhEw4rJaS/jPmYb9vhf8MfGf4P59ttxAtiDMkN327pWvnOqqah5d9qoClzc0tsw0qR0sy6uW2ibvruuMrrEPB4RjbtyMkB02yibscoy6DCJ2X7pGZyNZ3xKLAdun/4TxzcijVNXLEmykJfcTBwqG1Y23Il9LIO/Cxg0t8fkvC7BA==
-sidebar_class_name: "post api-method"
-info_path: docs/platforms/stellar-disbursement-platform/api-reference/stellar-disbursement-platform-api
-custom_edit_url: null
----
-
-import { SepBadge } from "@site/src/components/SepBadge";
-
-<SepBadge tags={''} />
-
-import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
-import ParamsDetails from "@theme/ParamsDetails";
-import RequestSchema from "@theme/RequestSchema";
-import StatusCodes from "@theme/StatusCodes";
-import OperationTabs from "@theme/OperationTabs";
-import TabItem from "@theme/TabItem";
-import Heading from "@theme/Heading";
-
-<Heading
-  as={"h1"}
-  className={"openapi__heading"}
-  children={"Verify Receiver Registration"}
->
-</Heading>
-
-<MethodEndpoint
-  method={"post"}
-  path={"/wallet-registration/verification"}
-  context={"endpoint"}
->
-  
-</MethodEndpoint>
-
-
-
-This endpoint verifies the receiver's registration by validating the OTP and other verification values provided in the request body. A valid SEP-24 token should be included in the Authorization header of the request.
-
-<Heading
-  id={"request"}
-  as={"h2"}
-  className={"openapi-tabs__heading"}
-  children={"Request"}
->
-</Heading>
-
-<ParamsDetails
-  parameters={[{"name":"Authorization","in":"header","description":"SEP-24 token for authorization (Format: 'Bearer {token}')","required":true,"style":"simple","explode":false,"schema":{"type":"string"}}]}
->
-  
-</ParamsDetails>
-
-<RequestSchema
-  title={"Body"}
-  body={{"description":"Verification data including phone_number/email, OTP, verification value, and reCAPTCHA token","content":{"application/json":{"schema":{"type":"object","properties":{"email":{"type":"string","description":"Email associated with the receiver in the SDP database. Either `phone_number` or `email` is required."},"phone_number":{"type":"string","description":"Phone number associated with the receiver in the SDP database. Either `phone_number` or `email` is required."},"otp":{"type":"string","description":"One-Time Password received for verification"},"verification":{"type":"string","description":"Verification value provided by the user"},"verification_field":{"type":"string","enum":["DATE_OF_BIRTH","YEAR_MONTH","PIN","NATIONAL_ID_NUMBER"],"title":"VerificationField"},"recaptcha_token":{"type":"string","description":"Token received from Google reCAPTCHA"}},"title":"ReceiverRegistrationRequest"}}},"required":true}}
->
-  
-</RequestSchema>
-
-<StatusCodes
-  id={undefined}
-  label={undefined}
-  responses={{"200":{"description":"Verification successful","content":{"application/json":{"schema":{"type":"object","properties":{"message":{"type":"string","example":"ok"}}}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string","description":"Details about the error"},"extras":{"type":"object","properties":{}}},"example":{"error":"Invalid input","extras":{"field_foo":"field_foo is required","field_bar":"field_bar needs to be an integer"}}}}}},"401":{"description":"Unauthorized","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"string"},"extras":{"type":"object","properties":{"status":{"type":"number"},"message":{"type":"string"}}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}},"example":{"error":"Not authorized","extras":{"status":401,"message":"Not authorized"}}}}}}}
->
-  
-</StatusCodes>
-
-
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tokens/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tokens/README.mdx
deleted file mode 100644
index 1ec9c8096b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tokens/README.mdx
+++ /dev/null
@@ -1,93 +0,0 @@
----
-sidebar_position: 10
-title: "Emisión de Activos vs. Creación de Tokens Personalizados: Diferencias Clave y Prácticas Recomendadas"
-sidebar_label: Activos Stellar y Tokens de Contrato
-description: Conoce las diferencias entre la emisión de activos en la red Stellar, la creación de tokens de contratos inteligentes, y la información y prácticas recomendadas para cada uno.
----
-
-:::info
-
-El término "custom token" ha quedado obsoleto en favor de "contract token". Ve la conversación en el [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
-
-:::
-
-# Activos Stellar y Tokens de Contrato
-
-Los tokens existen en dos formas en Stellar:
-
-1. Activos emitidos por cuentas de Stellar (`G...` direcciones) y su implementación del [Stellar Asset Contract (SAC)][sac] incorporado, y
-2. [Contract tokens][ti] issued by a deployed WASM contract (`C...` addresses).
-
-Several factors can help you determine whether to issue an asset on Stellar or create a contract token with a smart contract for your project.
-
-Sin embargo:
-
-### TL;DR
-
-Si es posible, recomendamos emitir un activo de Stellar y usar el SAC para interactuar con ese activo en contratos inteligentes o para enviarlo a direcciones de contratos. Más sobre por qué a continuación.
-
-## Emitiendo activos en Stellar
-
-Stellar tiene soporte de primera para la tokenización de activos — emitir un activo se puede hacer utilizando una [transacción incorporada](./quickstart.mdx) sin el desarrollo de un contrato inteligente.
-
-Las transacciones de Stellar son rápidas y rentables, lo que hace que la red sea excelente para remesas y micropagos. También tiene características integradas para cumplimiento, gestión de activos y auditoría. Si buscas realizar transferencias de valor, emitir activos en Stellar tiene todas las capacidades necesarias.
-
-Activos de Stellar:
-
-- Son compatibles con productos del ecosistema Stellar (como billeteras Stellar) y otros productos del ecosistema (como exchanges).
-- Se benefician de [anclajes](../learn/fundamentals/anchors.mdx), los puentes entre la red Stellar y los sistemas financieros tradicionales. Explora el [directorio de anclajes de Stellar](https://anchors.stellar.org/) global para más detalles.
-- Proporciona al emisor un control granular sobre la gestión de activos con características que permiten al emisor [nombrar el activo](./control-asset-access.mdx#naming-an-asset), [determinar el control de acceso](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags), [limitar el suministro del activo](./control-asset-access.mdx#limiting-the-supply-of-an-asset), [publicar información del activo](./publishing-asset-info.mdx) y [asegurar el cumplimiento](./anatomy-of-an-asset.mdx#compliance).
-
-:::note
-
-Note that while these items are also possible with smart contract tokens, it is more work to build the token contract rather than using the already-implemented features of Stellar asset tokens.
-
-:::
-
-Los activos emitidos en la red Stellar son accesibles para contratos inteligentes mediante el uso del Stellar Asset Contract (SAC) de ese activo.
-
-### Stellar Asset Contract
-
-El Stellar Asset Contract (SAC) está compilado en la capa del protocolo y permite que los contratos inteligentes interactúen con los activos emitidos en Stellar. Una instancia del SAC puede ser desplegada para cada activo de Stellar por cualquier persona que desee interactuar con el activo desde un contrato. El SAC tiene acceso a todos los saldos de cuenta (para XLM) y saldos de trustline (para todos los demás activos), así como los saldos de tokens de contratos inteligentes.
-
-Lee más sobre el SAC [aquí][sac].
-
-Aprende cómo desplegar un Stellar Asset Contract para un activo en [esta Guía Práctica](../tools/cli/cookbook/deploy-stellar-asset-contract.mdx).
-
-**Beneficios del SAC:**
-
-- Compatibilidad: el SAC se beneficia de la interoperabilidad existente de los activos de Stellar.
-- Eficiencia de costo y recursos: el SAC está integrado en el protocolo en lugar de ser un contrato que se ejecuta en una máquina virtual. Each function within the SAC will be more resource-efficient than its contract-coded counterpart.
-- Menos trabajo: no tienes que escribir un contrato completamente nuevo. El SAC de un activo Stellar ya existe en la red y solo necesita ser desplegado para ser utilizado.
-- Personalización: las direcciones de administrador pueden ser contratos. Los emisores de activos pueden establecer un contrato inteligente diferente como administrador para el SAC de su activo. Hacer del administrador otro contrato inteligente permite la adición de lógica personalizada y descentralizada para las capacidades administrativas de los activos, como autorizar saldos y líneas de confianza, acuñar tokens, etc.
-
-**Desventajas del SAC:**
-
-- Además de la personalización mencionada anteriormente, no es posible modificar el comportamiento de los activos de Stellar o su SAC. If you’re looking to use assets in a way not supported by Stellar assets, you can create your own smart contract token using the token interface and all applications that interact with tokens using the token interface will be able to interact with the contract token.
-
-## Contract tokens
-
-If you have a unique use case where the capabilities Stellar Assets are not sufficient, you can create a contract token that implements the [token interface][ti]. La interfaz de token especifica las funciones y eventos que un contrato debe implementar para ser compatible con aplicaciones que utilizan tokens.
-
-The SAC also implements the token interface and applications that interoperate with the token interface can seamlessly interact with Stellar assets and contract tokens.
-
-:::note
-
-Los contratos inteligentes no pueden utilizar activos de Stellar a menos que ese activo de Stellar tenga un SAC desplegado. Cualquiera puede desplegar el SAC para un activo de Stellar en su dirección reservada.
-
-:::
-
-**Estos escenarios de ejemplo no son posibles con el SAC y demuestran para qué podrías usar la interfaz de token:**
-
-- As the creator of a new token, you decide to implement a feature within your token smart contract that enables you to receive a 1% fee from every transaction involving your token. Cada vez que alguien transfiere tu token a otro usuario, se deduce automáticamente el 1% del monto transferido y se envía a una dirección de billetera designada que controlas.
-- Quieres desarrollar un contrato de fábrica que automatice la creación de instancias de un token específico. Este contrato sirve como una forma centralizada y estandarizada de desplegar nuevos contratos de token a pedido sin intervención manual cada vez que se necesita una nueva instancia.
-
-## Enlaces útiles
-
-- [Tutorial para emitir un activo][how-to-issue]
-- [Stellar Asset Contract][sac]
-- [Interfaz de token][ti]
-
-[how-to-issue]: ./how-to-issue-an-asset.mdx
-[sac]: ./stellar-asset-contract.mdx
-[ti]: ./token-interface.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tokens/anatomy-of-an-asset.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tokens/anatomy-of-an-asset.mdx
deleted file mode 100644
index 2abe4a90e9..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tokens/anatomy-of-an-asset.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Resumen de Activos
-sidebar_position: 20
----
-
-Emitir activos es una característica central de Stellar: cualquier activo puede ser tokenizado (o acuñado) en la red y luego rastreado, mantenido y negociado rápida y económicamente. Los activos pueden representar muchas cosas: criptomonedas (como bitcoin o ether), monedas fiduciarias (como dólares o pesos), otros tokens de valor (como NFTs), participaciones en fondos, o incluso bonos y acciones. Cualquier cuenta de Stellar puede emitir un activo, y dado que cualquiera puede crear una cuenta, cualquiera puede emitir activos: bancos, procesadores de pagos, negocios de servicios de dinero, empresas con fines de lucro, organizaciones sin fines de lucro, comunidades locales e individuos. Es un proceso autoservicio que no requiere permisos.
-
-Emitir un activo en Stellar es fácil y solo requiere varias operaciones. Sin embargo, hay consideraciones adicionales que podrías necesitar evaluar dependiendo de tu caso de uso, tales como la publicación de información sobre el activo, el cumplimiento y la oferta del activo, que cubriremos en esta documentación. Los activos en Stellar tienen dos características identificadoras: el código del activo y el emisor. Dado que más de una organización puede emitir un crédito que represente el mismo activo, los códigos de los activos a menudo se superponen (por ejemplo, varias empresas ofrecen un token USD en Stellar). Los activos se identifican de manera única por la combinación de su código de activo y emisor.
-
-Los activos emitidos en la red Stellar son accesibles a contratos inteligentes. Cada activo de Stellar tiene reservado un [Contrato de Activo Stellar](./stellar-asset-contract.mdx) que puede ser implementado por cualquier persona que quiera interactuar con el activo desde un contrato.
-
-## Stablecoins
-
-Una categoría importante de activos es la stablecoin. Una stablecoin es un token basado en blockchain cuyo valor está vinculado a otro activo, como el dólar de EE. UU., otras monedas fiduciarias, productos básicos como el oro, o incluso criptomonedas. Hay dos tipos de stablecoins: 1) stablecoins respaldadas por reservas que deben tener un mecanismo para canjear el activo que las respalda, y 2) stablecoins algorítmicas que no tienen activos que las respalden y en su lugar dependen de un algoritmo para controlar la oferta de la stablecoin. Al hablar de stablecoins, nuestra documentación se centrará en stablecoins respaldadas por reservas.
-
-Las stablecoins respaldadas por reservas están vinculadas a un activo del mundo real en una proporción de 1:1. Dado que el activo subyacente se mantiene como colateral, los usuarios deberían poder intercambiar su stablecoin por el activo en cualquier momento. Las reservas de activos pueden ser mantenidas por custodios independientes y deben ser auditadas regularmente.
-
-Actualmente, uno de los casos de uso más significativos de Stellar es la tokenización de la moneda fiduciaria para procesos como pagos transnacionales. Con los anchors, los usuarios pueden conectar tokens de Stellar a rieles existentes que permiten el depósito de activos del mundo real a cambio de moneda digital y viceversa. Aprende más sobre los anchors en nuestra [sección de Anchors](../learn/fundamentals/anchors.mdx).
-
-### Gestión de tesorería
-
-Al emitir una stablecoin respaldada por reservas, debes configurar su reserva fuera de la cadena, que almacena de forma segura el activo que respalda la stablecoin. Cuando los usuarios deseen canjear su stablecoin, pueden recibir una cantidad equivalente del activo de reserva subyacente del emisor.
-
-## Cumplimiento
-
-Como emisor de activos, es posible que debas cumplir con requisitos regulatorios que varían según la jurisdicción. Stellar tiene características integradas que pueden ayudar a cumplir con estos requisitos, tales como:
-
-- [Controlar el acceso a un activo con flags](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags)
-- [SEP-0008: Activos Regulados](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) - los activos regulados son activos que requieren la aprobación del emisor (o de un tercero delegado) por transacción. Consulta esta Propuesta del Ecosistema Stellar para aprender cómo implementar activos regulados en tu caso de uso.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tokens/control-asset-access.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tokens/control-asset-access.mdx
deleted file mode 100644
index e5c7bd4fd8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tokens/control-asset-access.mdx
+++ /dev/null
@@ -1,226 +0,0 @@
----
-title: Consideraciones sobre el diseño de activos
-sidebar_position: 40
----
-
-## Cuentas de emisión y distribución
-
-Es práctica recomendada en la red Stellar crear dos cuentas al emitir un activo: 1) la cuenta de emisión y 2) la cuenta de distribución.
-
-La **cuenta de emisión** crea (o emite) el activo en la red ejecutando una operación de pago. La cuenta de emisión siempre estará vinculada a la identidad del activo. Cualquier cuenta que quiera mantener el activo debe primero establecer una línea de confianza con la cuenta de emisión. Lee sobre las líneas de confianza en nuestra [sección de líneas de confianza](../learn/fundamentals/stellar-data-structures/accounts.mdx#trustlines).
-
-La **cuenta de distribución** es el primer destinatario del activo emitido y maneja todas las demás transacciones.
-
-Ten en cuenta que también puedes emitir un activo creando una oferta o un depósito de fondos de liquidez con la cuenta de emisión.
-
-Es práctica recomendada emitir un activo enviándolo desde la cuenta de emisión a una cuenta de distribución por dos razones principales: seguridad y auditoría.
-
-### Seguridad
-
-La cuenta de distribución será una cuenta activa, lo que significa que algún servicio web tiene acceso directo para firmar sus transacciones.
-
-Por ejemplo, si la cuenta desde la que distribuyes también es la cuenta de emisión y es comprometida por un actor malicioso, el actor puede ahora emitir tanto del activo como desee. Si el actor malicioso canjea los tokens recién emitidos con un servicio anchor, es posible que el anchor no tenga la liquidez para admitir las retiradas de fondos de los clientes. El riesgo es menor si usas una cuenta de distribución: si la cuenta de distribución se ve comprometida, puedes congelar el saldo de activos de la cuenta y comenzar con una nueva cuenta de distribución sin cambiar la cuenta de emisión.
-
-### Auditoría
-
-Usar una cuenta de distribución es mejor para la auditoría porque una cuenta de emisión no puede mantener un saldo de su propio activo. Enviar un activo de vuelta a su cuenta de emisión quema (elimina) el activo. Si tienes un inventario de los activos emitidos en una cuenta separada, es más fácil de rastrear y puede ayudar con la contabilidad.
-
-## Nombrar un activo
-
-Una de las cosas que debes decidir al emitir un activo es cómo llamarlo. Un código de activo es el código identificador del activo. Hay tres formatos posibles: Alfanumérico 4, Alfanumérico 12 y participaciones de fondos de liquidez.
-
-Aprende sobre las participaciones en fondos de liquidez en la [Entrada Enciclopédica de Fondos de Liquidez](../learn/fundamentals/liquidity-on-stellar-sdex-liquidity-pools.mdx).
-
-- Máximo de 4 caracteres alfanuméricos: Se permiten cualquier carácter del conjunto a-z, A-Z, 0-9. El código puede ser más corto que 4 caracteres, pero los caracteres finales deben estar vacíos.
-- Máximo de 12 caracteres alfanuméricos: Se permiten cualquier carácter del conjunto a-z, A-Z, 0-9. El código puede tener cualquier cantidad de caracteres de 5 a 12, pero los caracteres finales deben estar vacíos.
-- El activo de participación de fondo se define por el identificador del fondo de liquidez (PoolID), que a su vez se define por los dos activos de los que se componen sus reservas.
-
-Siempre que se encuentre en alguna de estas categorías, puedes elegir cualquier código de activo que desees. Dicho esto, si estás emitiendo una moneda, deberías usar el código ISO 4217 apropiado, y si estás emitiendo una acción o un bono, el número ISIN apropiado. Hacer esto facilita que las interfaces de Stellar muestren y ordenen correctamente tu token en sus listados y permite a los potenciales titulares del token entender qué representa tu token.
-
-## Controlar el acceso a un activo con flags
-
-Cuando emites un activo en Stellar, cualquiera puede mantenerlo por defecto. En general, eso es algo bueno: el acceso fácil significa mejor alcance y mejor liquidez. Sin embargo, si necesitas controlar el acceso a un activo para cumplir con regulaciones (o por cualquier otra razón), puedes hacerlo fácilmente habilitando flags en tu cuenta de emisión.
-
-Los flags se crean a nivel de cuenta utilizando una operación `set_options`. Se pueden establecer en cualquier momento del ciclo de vida de un activo, no solo cuando lo emites.
-
-### Tipos de flags
-
-El (0xn) junto a cada tipo de flag denota la configuración de bits para cada flag.
-
-#### Autorización Requerida (0x1)
-
-Cuando `AUTH_REQUIRED_FLAG` está habilitado, un emisor debe aprobar una cuenta antes de que esa cuenta pueda mantener su activo. Esta configuración permite a los emisores evaluar a los potenciales titulares de tokens y aprobar líneas de confianza.
-
-Para permitir el acceso, el usuario crea una línea de confianza, y el emisor la aprueba cambiando el flag `AUTHORIZE` con la operación `Set_Trust_Line_Flag`.
-
-Hay dos niveles de autorización que un emisor de activos puede otorgar utilizando la operación `Set_Trust_Line_Flag`:
-
-- `AUTHORIZED_FLAG`: significa autorización completa que permite a una cuenta transaccionar libremente con el activo para hacer y recibir pagos, realizar pedidos y depositar en un fondo de liquidez.
-- `AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG`: denota autorización limitada que permite a una cuenta mantener órdenes actuales, retirar de un fondo de liquidez o cancelar órdenes actuales - pero no transaccionar de otra manera con el activo.
-
-#### Autorización Revocable (0x2)
-
-Cuando `AUTH_REVOCABLE_FLAG` está habilitado, un emisor puede revocar la autorización de una línea de confianza existente, congelando así el activo mantenido por una cuenta. Hacer esto evita que esa cuenta transfiera o comercie el activo y cancela las órdenes abiertas de la cuenta para el activo.
-
-`AUTH_REVOCABLE_FLAG` también permite al emisor reducir la autorización de completa a limitada, lo que impide que la cuenta transfiera o comercie el activo, pero no cancela las órdenes abiertas de la cuenta para el activo. Esta configuración es útil para emisores de activos regulados que necesitan autorizar transacciones caso por caso para asegurar que cada una cumpla con ciertos requisitos.
-
-Todos los cambios en la autorización de activos se realizan con la operación Set Trustline Flags.
-
-Hay tres niveles de autorización que un emisor de activos puede eliminar utilizando la operación `Set_Trust_Line_Flag`:
-
-- `AUTHORIZED_FLAG`: significa autorización completa que permite a una cuenta transaccionar libremente con el activo para hacer y recibir pagos y realizar pedidos.
-- `AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG`: denota autorización limitada que permite a una cuenta mantener órdenes actuales, pero no transaccionar de otra manera con el activo.
-- `CLAWBACK_ENABLED`: habilita a la cuenta de emisión para recuperar (quemar) todos los activos. Consulta nuestra [sección sobre Clawbacks](../build/guides/transactions/clawbacks.mdx) para más información.
-
-#### Clawback Habilitado (0x8)
-
-Con la flag `AUTH_CLAWBACK_ENABLED_FLAG` establecida, cualquier línea de confianza _subsecuente_ establecida con esta cuenta tendrá habilitados los clawbacks. Puedes leer más sobre clawbacks (y cómo controlarlos selectivamente en una base por trustline) [aquí](../build/guides/transactions/clawbacks.mdx).
-
-Ten en cuenta que esta flag requiere que la revocación también esté establecida.
-
-#### Autorización Inmutable (0x4)
-
-Con esta configuración, ninguno de los otros flags de autorización (`AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`) puede ser establecido, y la cuenta de emisión no puede ser fusionada. Estableces esta flag para indicar a los potenciales titulares de tokens que tu cuenta de emisión y sus activos persistirán en el ledger en un estado abierto y accesible.
-
-### Operación Set Trustline Flag
-
-La cuenta de emisión puede configurar varios flags de autorización y líneas de confianza para las líneas de confianza individuales a un activo. El parámetro de activo es del tipo TrustLineAsset. Si estás modificando una línea de confianza a un activo regular (es decir, uno en formato Code:Issuer), esto es equivalente al tipo de activo. Si estás modificando una línea de confianza a una participación de fondo, esta es la identificación única del fondo de liquidez.
-
-### Flujo de ejemplo
-
-Veamos cómo un emisor de un activo regulado podría usar la flag `AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG`.
-
-Si el emisor desea aprobar transacciones caso por caso mientras permite que las cuentas mantengan ofertas, puede dejar una cuenta en el estado `AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG`. Esa cuenta puede tener ofertas pero no puede hacer nada más con el activo.
-
-Para iniciar una nueva operación, la cuenta mantenedora solicita que el emisor apruebe y firme una transacción. Una vez que el emisor inspecciona la operación y decide aprobarla, la coloca entre un conjunto de operaciones, primero otorgando autorización, luego reduciéndola.
-
-Aquí hay un pago de A a B colocado entre operaciones `set_trust_line_flags`:
-
-- Operación 1: El emisor utiliza `SetTrustLineFlags` para autorizar completamente la cuenta A, activo X
-- Operación 2: El emisor utiliza `SetTrustLineFlags` para autorizar completamente la cuenta B, activo X
-- Operación 3: Pago de A a B
-- Operación 4: El emisor utiliza `SetTrustLineFlags` para establecer la cuenta B, activo X en estado `AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG`
-- Operación 5: El emisor utiliza `SetTrustLineFlags` para establecer la cuenta A, activo X en estado `AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG`
-
-El sándwich de autorización permite al emisor inspeccionar el pago específico y otorgar autorización solo para ello. Dado que las operaciones agrupadas en una transacción son simultáneas, A y B solo están autorizados para la operación de pago específica y preaprobada. La autorización completa no se extiende más allá de la transacción específica.
-
-### Código de muestra
-
-En los siguientes ejemplos de código, se omite la verificación de errores adecuada. Sin embargo, siempre debes validar tus resultados, ya que hay muchas formas en que las solicitudes pueden fallar. Consulta la página de [Manejo de Errores](../data/apis/horizon/api-reference/errors/error-handling.mdx) para obtener consejos sobre estrategias de gestión de errores.
-
-El siguiente ejemplo establece que la autorización sea tanto requerida como revocable:
-
-<CodeExample>
-
-```js
-var StellarSdk = require("stellar-sdk");
-var server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-
-// Keys for issuing account
-var issuingKeys = StellarSdk.Keypair.fromSecret(
-  "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4",
-);
-
-server
-  .loadAccount(issuingKeys.publicKey())
-  .then(function (issuer) {
-    var transaction = new StellarSdk.TransactionBuilder(issuer, {
-      fee: 100,
-      networkPassphrase: StellarSdk.Networks.TESTNET,
-    })
-      .addOperation(
-        StellarSdk.Operation.setOptions({
-          setFlags: StellarSdk.AuthRevocableFlag | StellarSdk.AuthRequiredFlag,
-        }),
-      )
-      // setTimeout is required for a transaction
-      .setTimeout(100)
-      .build();
-    transaction.sign(issuingKeys);
-    return server.submitTransaction(transaction);
-  })
-  .then(console.log)
-  .catch(function (error) {
-    console.error("Error!", error);
-  });
-```
-
-```java
-import org.stellar.sdk.*;
-import org.stellar.sdk.Network;
-import org.stellar.sdk.responses.AccountResponse;
-
-Server server = new Server("https://horizon-testnet.stellar.org");
-
-// Keys for issuing account
-KeyPair issuingKeys = KeyPair
-  .fromSecretSeed("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4");
-AccountResponse sourceAccount = server.accounts().account(issuingKeys.getAccountId());
-
-Transaction setAuthorization = new Transaction.Builder(sourceAccount, Network.TESTNET)
-  .addOperation(new SetOptionsOperation.Builder()
-    .setSetFlags(
-      AccountFlag.AUTH_REQUIRED_FLAG.getValue() |
-      AccountFlag.AUTH_REVOCABLE_FLAG.getValue())
-    .build())
-  .build();
-setAuthorization.sign(issuingKeys);
-server.submitTransaction(setAuthorization);
-```
-
-```python
-from stellar_sdk import Keypair, Network, Server, TransactionBuilder, AuthorizationFlag
-from stellar_sdk.exceptions import BaseHorizonError
-
-# Configure Stellar SDK to talk to the horizon instance hosted by Stellar.org
-# To use the live network, set the hostname to horizon_url for mainnet
-server = Server(horizon_url="https://horizon-testnet.stellar.org")
-# Use the test network, if you want to use the live network, please set it to `Network.PUBLIC_NETWORK_PASSPHRASE`
-network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-
-# Keys for accounts to issue and receive the new asset
-issuing_keypair = Keypair.from_secret(
-    "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4"
-)
-issuing_public = issuing_keypair.public_key
-
-# Transactions require a valid sequence number that is specific to this account.
-# We can fetch the current sequence number for the source account from Horizon.
-issuing_account = server.load_account(issuing_public)
-
-transaction = (
-    TransactionBuilder(
-        source_account=issuing_account,
-        network_passphrase=network_passphrase,
-        base_fee=100,
-    )
-    .append_set_options_op(
-        set_flags=AuthorizationFlag.AUTH_REVOCABLE_FLAG | AuthorizationFlag.AUTHORIZATION_REQUIRED
-    )
-    .build()
-)
-transaction.sign(issuing_keypair)
-try:
-    transaction_resp = server.submit_transaction(transaction)
-    print(f"Transaction Resp:\n{transaction_resp}")
-except BaseHorizonError as e:
-    print(f"Error: {e}")
-```
-
-</CodeExample>
-
-## Limitar el suministro de un activo
-
-:::danger Advertencia
-
-Esta sección detalla cómo bloquear tu cuenta con el propósito de limitar el suministro de tu activo emitido. Sin embargo, bloquear tu cuenta significa que nunca podrás hacer nada con ella de nuevo: ya sea ajustar firmantes, cambiar el dominio principal, reclamar cualquier XLM mantenido, o cualquier otra operación. Tu cuenta estará completamente congelada.
-
-:::
-
-Teniendo en cuenta esa advertencia, es posible bloquear la cuenta de emisión de un activo para que el suministro del activo no pueda aumentar. Para hacer esto, primero establece el peso maestro de la cuenta de emisión a 0 utilizando la operación Set Options. Esto evita que la cuenta de emisión pueda firmar transacciones y, por lo tanto, incapacita al emisor para emitir más activos. Asegúrate de hacer esto solo después de haber emitido todos los activos deseados a la cuenta de distribución. Si el activo tiene un Contrato de Activos Stellar, también asegúrate de que el administrador del contrato no haya sido actualizado desde el valor predeterminado (que es el emisor) utilizando la llamada de contrato `set_admin`. Si el administrador no era el emisor, entonces el administrador podría emitir el activo incluso con la cuenta de emisión bloqueada.
-
-Obtén más información sobre los pesos de firma en la [Entrada de Enciclopedia sobre Firma y Multisig](../learn/fundamentals/transactions/signatures-multisig.mdx).
-
-Consulta cómo hacerlo en los pasos opcionales del [Tutorial sobre Emisión de un Activo](./how-to-issue-an-asset.mdx#configure-maximum-supply).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tokens/how-to-issue-an-asset.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tokens/how-to-issue-an-asset.mdx
deleted file mode 100644
index 38503661f5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tokens/how-to-issue-an-asset.mdx
+++ /dev/null
@@ -1,759 +0,0 @@
----
-title: "Emitir un activo en Stellar: Establecer líneas de confianza, gestionar suministro y distribución"
-sidebar_label: Emitir un activo Tutorial
-description: Aprende a emitir un activo Stellar, establecer líneas de confianza y gestionar el suministro. Sigue esta guía paso a paso para crear y distribuir activos en la red.
-sidebar_position: 70
----
-
-# Tutorial de emisión de activos
-
-En este tutorial, recorreremos los pasos para emitir un activo en la red de prueba Stellar.
-
-:::note
-
-Si deseas interactuar con un activo emitido en la red Stellar en contratos inteligentes, puedes crear o desplegar el [Contrato de Activo Stellar](./stellar-asset-contract.mdx) para ese activo.
-
-:::
-
-## Requisitos previos
-
-Debes asegurarte de tener la cantidad requerida de XLM para crear tus cuentas de emisión y distribución y cubrir el saldo mínimo y las tarifas de transacción. Si estás emitiendo un activo en la red de prueba, puedes financiar tu cuenta obteniendo XLM de prueba de friendbot. Si estás emitiendo un activo en producción, necesitarás adquirir XLM de otra billetera o exchange.
-
-Si deseas evitar que tus usuarios tengan que lidiar con tarifas de transacción, considera usar transacciones de incremento de tarifas. Lee más en nuestra [Guía de Transacciones Fee-Bump](../build/guides/transactions/fee-bump-transactions.mdx).
-
-Aprende sobre la testnet y la mainnet en nuestra [sección de redes](../networks/README.mdx).
-
-Aprende más sobre las tarifas en nuestra [sección de Tarifas, Límites de Recursos y Medición](../learn/fundamentals/fees-resource-limits-metering.mdx).
-
-## Herramientas fundamentales
-
-### Keypair de cuenta emisora
-
-Primero, debes generar un keypair único. La clave pública actuará como tu [identidad de emisión](../learn/fundamentals/stellar-data-structures/assets.mdx#issuer) en la red, mientras que utilizarás la clave secreta para firmar transacciones.
-
-<CodeExample>
-
-```js
-const issuerKeypair = StellarSdk.Keypair.random();
-
-console.log("Issuer Public Key:", issuerKeypair.publicKey());
-console.log("Issuer Secret Key:", issuerKeypair.secret());
-```
-
-```python
-from stellar_sdk import Keypair
-
-issuer_keypair = Keypair.random()
-
-print("Issuer Public Key:", issuer_keypair.public_key)
-print("Issuer Secret Key:", issuer_keypair.secret)
-```
-
-```java
-KeyPair issuerKeypair = KeyPair.random();
-
-System.out.println("Issuer Public Key: " + issuerKeypair.getAccountId());
-System.out.println("Issuer Secret Key: " + issuerKeypair.getSecretSeed());
-```
-
-```go
-import (
-  "github.com/stellar/go-stellar-sdk/keypair"
-  "fmt"
-)
-
-issuerKeypair := keypair.MustRandom()
-
-fmt.Println("Issuer Public Key:", issuerKeypair.Address())
-fmt.Println("Issuer Secret Key:", issuerKeypair.Seed())
-```
-
-</CodeExample>
-
-:::info
-
-La dirección de tu cuenta no cambiará una vez que emitas tu activo, incluso si modificas sus [firmantes](../learn/fundamentals/transactions/signatures-multisig.mdx). Muchos emisores emplean [claves públicas de vanity](https://github.com/JFWooten4/py-stellar-vanity-toolkit) relacionadas con su activo. Por ejemplo, podrías configurar un firmante personalizado en [base32](../learn/glossary.mdx#account-id) como `GASTRO...USD`.
-
-:::
-
-:::note
-
-Muchos usuarios aseguran su cuenta emisora con técnicas de almacenamiento en frío, como una billetera de hardware o una configuración de múltiples firmas. Esto añade una capa adicional de protección al mantener tu clave secreta fuera de línea o requerir múltiples aprobaciones para transacciones.
-
-:::
-
-### Keypair de cuenta de distribución
-
-Tu activo puede ser emitido y transferido entre cuentas a través de un pago, contrato, o saldo reclamable. Aunque no es necesario crear una cuenta de distribución, es una práctica recomendada, así que lo haremos en este ejemplo. Lee más en nuestra [sección de Cuentas de Emisión y Distribución](./control-asset-access.mdx#issuing-and-distribution-accounts).
-
-#### Tres Operaciones
-
-##### Generar un nuevo keypair
-
-<CodeExample>
-
-```js
-const distributorKeypair = StellarSdk.Keypair.random();
-```
-
-```python
-distributor_keypair = Keypair.random()
-```
-
-```java
-KeyPair distributorKeypair = KeyPair.random();
-```
-
-```go
-distributorKeypair := keypair.MustRandom()
-```
-
-</CodeExample>
-
-##### Importar un keypair existente
-
-<CodeExample>
-
-```js
-const distributorKeypair = StellarSdk.Keypair.fromSecret(‘SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4’)
-```
-
-```python
-distributor_keypair = Keypair.from_secret("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4")
-```
-
-```java
-KeyPair distributorKeypair = KeyPair.fromSecretSeed("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4");
-```
-
-```go
-distributorKeypair := keypair.MustParseFull("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4")
-```
-
-</CodeExample>
-
-##### Emplear [múltiples firmas](../learn/fundamentals/transactions/signatures-multisig.mdx)
-
-:::danger
-
-Ten cuidado al trabajar con claves secretas en bruto. Si no tienes habilitado el [clawback](../build/guides/transactions/clawbacks.mdx) de trustline del emisor, cualquier error aquí podría ocasionar la pérdida permanente de activos. Muchos usuarios colocan sus primeros proyectos en la [testnet](../networks/README.mdx#testnet) o prueban las [Misiones](../learn/interactive/quest.mdx) que ofrecen un entorno introductorio con bajo riesgo.
-
-:::
-
-### Objeto de activo local
-
-El objeto activo es una combinación de tu [código](./control-asset-access.mdx#naming-an-asset) y tu clave pública de emisión. Después de tu emisión, cualquiera puede buscar en la red tu activo único.
-
-<CodeExample>
-
-```js
-const astroDollar = new StellarSdk.Asset(
-  "AstroDollar",
-  issuerKeypair.publicKey(),
-);
-```
-
-```python
-from stellar_sdk import Keypair, Asset
-
-astro_dollar = Asset("AstroDollar", issuer_keypair.public_key)
-```
-
-```java
-Asset astroDollar = Asset.createNonNativeAsset("AstroDollar", issuerKeypair.getAccountId());
-```
-
-```go
-import (
-  "github.com/stellar/go-stellar-sdk/keypair"
-  "github.com/stellar/go-stellar-sdk/txnbuild"
-)
-
-astroDollar := txnbuild.CreditAsset{Code: "AstroDollar", Issuer: issuerKeypair.Address()}
-```
-
-</CodeExample>
-
-:::info
-
-Aunque cualquiera puede crear un activo, puede haber implicaciones de [cumplimiento](./anatomy-of-an-asset.mdx#compliance) del mundo real relevantes para tu caso de uso.
-
-:::
-
-:::note
-
-Querrás asegurarte de publicar información sobre tu activo para establecer confianza con tus usuarios y prevenir errores. Aprende cómo hacerlo en nuestra [sección de Publicar Información Sobre Tu Activo](./publishing-asset-info.mdx).
-
-:::
-
-## Transacciones de red
-
-### Desarrollar transacción para establecer la línea de confianza del distribuidor
-
-Las cuentas deben establecer una [línea de confianza](../learn/fundamentals/stellar-data-structures/accounts.mdx#trustlines) con la cuenta emisora para tener el activo de ese emisor. Esto es cierto para todos los activos excepto para el token nativo de la red, [Lumens](../learn/fundamentals/lumens.mdx).
-
-:::note
-
-Si deseas evitar que tus usuarios tengan que lidiar con líneas de confianza o XLM, considera usar reservas patrocinadas. Lee más en nuestra [Entrada Enciclopédica de Reservas Patrocinadas](../build/guides/transactions/sponsored-reserves.mdx).
-
-:::
-
-<CodeExample>
-
-```js
-const StellarSdk = require("stellar-sdk");
-const server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-const account = await server.loadAccount(distributorKeypair.publicKey());
-
-// This step only builds the transaction.  It still needs to be signed.
-const transaction = new StellarSdk.TransactionBuilder(account, {
-  fee: StellarSdk.BASE_FEE,
-  networkPassphrase: StellarSdk.Networks.TESTNET,
-})
-  // The `changeTrust` operation creates (or alters) a trustline
-  .addOperation(
-    StellarSdk.Operation.changeTrust({
-      asset: astroDollar,
-      limit: "1000", // optional
-      source: distributorKeypair.publicKey(),
-    }),
-  )
-  .setTimeout(100)
-  .build();
-```
-
-```python
-from stellar_sdk import Keypair, Asset, Network, Server, TransactionBuilder
-
-server = Server("https://horizon-testnet.stellar.org")
-distributor_account = server.load_account(distributor_keypair.public_key)
-
-transaction = (
-  TransactionBuilder(
-    source_account=distributor_account,
-    network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-    base_fee=100
-  )
-  .append_change_trust_op(asset=astro_dollar, limit="1000")
-  .set_timeout(100)
-  .build()
-)
-```
-
-```java
-Server server = new Server("https://horizon-testnet.stellar.org");
-AccountResponse distributorAccount = server.accounts().account(distributorKeypair.getAccountId());
-
-Transaction transaction = new Transaction.Builder(distributorAccount, Network.TESTNET)
-  .addOperation(
-    new ChangeTrustOperation.Builder(astroDollar, "1000")
-    .setSourceAccount(distributorKeypair.getAccountId())
-    .build()
-  )
-  .setTimeout(100)
-  .build();
-```
-
-```go
-import (
-  "github.com/stellar/go-stellar-sdk/clients/horizonclient"
-  "github.com/stellar/go-stellar-sdk/keypair"
-  "github.com/stellar/go-stellar-sdk/network"
-  "github.com/stellar/go-stellar-sdk/txnbuild"
-)
-
-client := horizonclient.DefaultTestNetClient
-distributorAccountRequest := horizonclient.AccountRequest{AccountID: distributorKeypair.Address()}
-distributorAccount, _ := client.AccountDetail(distributorAccountRequest)
-
-transaction, _ := txnbuild.NewTransaction(
-  txnbuild.TransactionParams{
-    SourceAccount:        &distributorAccount,
-    IncrementSequenceNum: true,
-    BaseFee:              txnbuild.MinBaseFee,
-    Operations: []txnbuild.Operation{
-      &txnbuild.ChangeTrust{
-        Line:  astroDollar,
-        Limit: "1000",
-      },
-    },
-    Timebounds: txnbuild.NewInfiniteTimeout(),
-  },
-)
-```
-
-</CodeExample>
-
-### Pago de emisor al distribuidor
-
-Los pagos son la operación más popular para realmente emitir (o acuñar) tu activo, en comparación con [otras emisiones](../learn/fundamentals/transactions/list-of-operations.mdx#path-payment-strict-send). Un pago crea la cantidad de un activo especificado, hasta [el máximo entero de 64 bits](../learn/fundamentals/stellar-data-structures/assets.mdx#amount-precision). Es relevante mencionar que no necesitas aumentar la cantidad de emisión de tu activo por el [incremento mínimo](../learn/fundamentals/stellar-data-structures/assets.mdx#amount-precision) de XDR.
-
-<CodeExample>
-
-```js
-// We're using TransactionBuilder(...) as a short-hand here
-// to show that these operations can be "chained" together.
-const transaction = new StellarSdk.TransactionBuilder(...)
-  // The `payment` operation sends the `amount` of the specified
-  // `asset` to our distributor account
-  .addOperation(StellarSdk.Operation.payment({
-    destination: distributorKeypair.publicKey(),
-    asset: astroDollar,
-    amount: '1000',
-    source: issuerKeypair.publicKey()
-  }))
-```
-
-```python
-# We're using TransactionBuilder(...) as a short-hand here
-# to show that these operations can be "chained" together.
-transaction = (
-  TransactionBuilder(...)
-  .append_payment_op(
-    destination=distributor_keypair.public_key,
-    asset=astro_dollar,
-    amount="1000"
-  )
-)
-```
-
-```java
-// We're using TransactionBuilder(...) as a short-hand here
-// to show that these operations can be "chained" together.
-Transaction transaction = new Transaction.Builder(...)
-  .addOperation(new PaymentOperation.Builder(
-    distributorKeypair.getAccountId(),
-    astroDollar,
-    "1000"
-  )
-  .setSourceAccount(
-    issuerKeypair.getAccountId()
-  )
-```
-
-```go
-// We're using TransactionBuilder(...) as a short-hand here
-// to show that these operations can be "chained" together.
-transaction, _ := txnbuild.NewTransaction(
-  txnbuild.TransactionParams{
-    SourceAccount:        &issuerAccount,
-    IncrementSequenceNum: true,
-    BaseFee:              txnbuild.MinBaseFee,
-    Operations: []txnbuild.Operation{
-      &txnbuild.Payment{
-        Destination: distributorKeypair.Address(),
-        Amount:      "1000",
-        Asset:       astroDollar,
-      },
-    },
-    Timebounds: txnbuild.NewInfiniteTimeout(),
-  },
-)
-```
-
-</CodeExample>
-
-:::note
-
-También puedes crear un mercado directamente desde la cuenta emisora y emitir tokens a través del comercio.
-
-:::
-
-### Transacciones opcionales
-
-#### Configurar suministro máximo
-
-:::danger
-
-Esta sección detalla cómo bloquear tu cuenta con el propósito de limitar el suministro de tu activo emitido. However, locking your account means you’ll never be able to do anything with it ever again&mdash;whether that’s adjusting signers, changing the home domain, claiming any held XLM, or any other operation. Tu cuenta estará completamente congelada.
-
-:::
-
-Puedes configurar permanentemente el número exacto de un activo que existirá alguna vez. Aprende más sobre el suministro de activos en nuestra sección sobre [Limitando el Suministro de un Activo](./control-asset-access.mdx#limiting-the-supply-of-an-asset)
-
-<CodeExample>
-
-```js
-const lockAccountTransaction = new StellarSdk.TransactionBuilder(...)
-  // This `setOptions` operation locks the issuer account
-  // so there can never be any more of the asset minted
-  .addOperation(StellarSdk.Operation.setOptions({
-    masterWeight: 0,
-    source: issuerKeypair.publicKey()
-  }))
-```
-
-```python
-lock_account_transaction = (
-  TransactionBuilder(...)
-  .append_set_options_op(master_weight=0)
-)
-```
-
-```java
-Transaction lockAccountTransaction = new Transaction.Builder(...)
-  .addOperation(new SetOptionsOperation.Builder()
-    .setMasterKeyWeight(0)
-    .setSourceAccount(issuerKeypair.getAccountId())
-  )
-```
-
-```go
-lockAccountTransaction, _ := txnbuild.NewTransaction(
-  txnbuild.TransactionParams{
-    SourceAccount:        &issuerAccount,
-    IncrementSequenceNum: true,
-    BaseFee:              txnbuild.MinBaseFee,
-    Operations: []txnbuild.Operation{
-      &txnbuild.SetOptions{
-        MasterWeight: txnbuild.NewThreshold(0),
-      },
-    },
-    Timebounds: txnbuild.NewInfiniteTimeout(),
-  },
-)
-```
-
-</CodeExample>
-
-#### Aprobar la línea de confianza del distribuidor
-
-Si habilitas la [bandera de autorización](./control-asset-access.mdx#authorization-required-0x1), la cuenta emisora también necesita aprobar la solicitud de línea de confianza de la cuenta distribuidora antes del pago de emisión. Necesitarás hacer esto para todas las nuevas cuentas cuando se configuró para tu activo.
-
-<CodeExample>
-
-```js
-const issuingAccount = await server.loadAccount(issuerKeypair.publicKey());
-const transaction = new StellarSdk.TransactionBuilder(...)
-  .addOperation(
-    StellarSdk.Operation.setTrustLineFlags({
-      trustor: distributorKeypair.publicKey(),
-      asset: astroDollar,
-      flags: {
-        authorized: true,
-      },
-    }),
-  )
-  .setTimeout(100)
-  .build();
-```
-
-```python
-from stellar_sdk import Server, Keypair, Network, TransactionBuilder, SetTrustLineFlags
-
-server = Server("https://horizon-testnet.stellar.org")
-issuer_account = server.load_account(issuer_keypair.public_key)
-
-transaction = (
-    TransactionBuilder(...)
-    .append_set_trust_line_flags_op(
-        trustor=distributor_keypair.public_key,
-        asset=astro_dollar,
-        flags=SetTrustLineFlags.AUTHORIZED_FLAG
-    )
-    .set_timeout(100)
-    .build()
-)
-```
-
-```java
-AccountResponse issuerAccount = server.accounts().account(issuerKeys.getAccountId());
-Transaction transaction = new Transaction.Builder(...)
-  .addOperation(new SetTrustLineFlagsOperation.Builder(
-    distributorKeys.getAccountId(),
-    astroDollar
-  ).setAuthorized(true).build())
-  .setTimeout(100)
-  .build();
-```
-
-```go
-issuerAccountRequest := horizonclient.AccountRequest{AccountID: issuerKeypair.Address()}
-issuerAccount, _ := client.AccountDetail(issuerAccountRequest)
-
-transaction, _ := txnbuild.NewTransaction(
-  txnbuild.TransactionParams{
-    SourceAccount:        &issuerAccount,
-    IncrementSequenceNum: true,
-    BaseFee:              txnbuild.MinBaseFee,
-    Operations: []txnbuild.Operation{
-      &txnbuild.SetTrustLineFlags{
-        Trustor:   distributorKeypair.Address(),
-        Asset:     astroDollar,
-        Authorized: txnbuild.AuthorizeFlag,
-      },
-    },
-    Timebounds: txnbuild.NewInfiniteTimeout(),
-  },
-)
-```
-
-</CodeExample>
-
-## Ejemplo de código completo
-
-<CodeExample title="Emitir un Activo">
-
-```js
-var StellarSdk = require("stellar-sdk");
-var server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-
-// Keys for accounts to issue and receive the new asset
-var issuerKeys = StellarSdk.Keypair.fromSecret(
-  "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4",
-);
-var receivingKeys = StellarSdk.Keypair.fromSecret(
-  "SDSAVCRE5JRAI7UFAVLE5IMIZRD6N6WOJUWKY4GFN34LOBEEUS4W2T2D",
-);
-
-// Create an object to represent the new asset
-var astroDollar = new StellarSdk.Asset("AstroDollar", issuerKeys.publicKey());
-
-// First, the receiving account must trust the asset
-server
-  .loadAccount(receivingKeys.publicKey())
-  .then(function (receiver) {
-    var transaction = new StellarSdk.TransactionBuilder(receiver, {
-      fee: 100,
-      networkPassphrase: StellarSdk.Networks.TESTNET,
-    })
-      // The `changeTrust` operation creates (or alters) a trustline
-      // The `limit` parameter below is optional
-      .addOperation(
-        StellarSdk.Operation.changeTrust({
-          asset: astroDollar,
-          limit: "1000",
-        }),
-      )
-      // setTimeout is required for a transaction
-      .setTimeout(100)
-      .build();
-    transaction.sign(receivingKeys);
-    return server.submitTransaction(transaction);
-  })
-  .then(console.log)
-
-  // Second, the issuing account actually sends a payment using the asset
-  .then(function () {
-    return server.loadAccount(issuerKeys.publicKey());
-  })
-  .then(function (issuer) {
-    var transaction = new StellarSdk.TransactionBuilder(issuer, {
-      fee: 100,
-      networkPassphrase: StellarSdk.Networks.TESTNET,
-    })
-      .addOperation(
-        StellarSdk.Operation.payment({
-          destination: receivingKeys.publicKey(),
-          asset: astroDollar,
-          amount: "10",
-        }),
-      )
-      // setTimeout is required for a transaction
-      .setTimeout(100)
-      .build();
-    transaction.sign(issuerKeys);
-    return server.submitTransaction(transaction);
-  })
-  .then(console.log)
-  .catch(function (error) {
-    console.error("Error!", error);
-  });
-```
-
-```python
-from stellar_sdk import Asset, Keypair, Network, Server, TransactionBuilder
-
-# Configure Stellar SDK to talk to the Horizon instance hosted by SDF
-# To use the live network, set the hostname to horizon_url for mainnet
-server = Server(horizon_url="https://horizon-testnet.stellar.org")
-# Use test network, if you need to use public network, please set it to `Network.PUBLIC_NETWORK_PASSPHRASE`
-network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-
-# Keys for accounts to issue and receive the new asset
-issuerKeypair = Keypair.from_secret(
-    "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4"
-)
-issuer_public = issuerKeypair.public_key
-
-distributor_keypair = Keypair.from_secret(
-    "SDSAVCRE5JRAI7UFAVLE5IMIZRD6N6WOJUWKY4GFN34LOBEEUS4W2T2D"
-)
-distributor_public = distributor_keypair.public_key
-
-# Transactions require a valid sequence number that is specific to this account.
-# We can fetch the current sequence number for the source account from Horizon.
-distributor_account = server.load_account(distributor_public)
-
-# Create an object to represent the new asset
-astro_dollar = Asset("AstroDollar", issuer_public)
-
-# First, the receiving account must trust the asset
-trust_transaction = (
-    TransactionBuilder(
-        source_account=distributor_account,
-        network_passphrase=network_passphrase,
-        base_fee=100,
-    )
-    #  The `changeTrust` operation creates (or alters) a trustline
-    #  The `limit` parameter below is optional
-    .append_change_trust_op(asset=astro_dollar, limit="1000")
-    .set_timeout(100)
-    .build()
-)
-
-trust_transaction.sign(distributor_keypair)
-trust_transaction_resp = server.submit_transaction(trust_transaction)
-print(f"Change Trust Transaction Resp:\n{trust_transaction_resp}")
-
-issuer_account = server.load_account(issuer_public)
-# Second, the issuing account actually sends a payment using the asset.
-payment_transaction = (
-    TransactionBuilder(
-        source_account=issuer_account,
-        network_passphrase=network_passphrase,
-        base_fee=100,
-    )
-    .append_payment_op(
-        destination=distributor_public,
-        asset=astro_dollar,
-        amount="10",
-    )
-    .build()
-)
-payment_transaction.sign(issuerKeypair)
-payment_transaction_resp = server.submit_transaction(payment_transaction)
-print(f"Payment Transaction Resp:\n{payment_transaction_resp}")
-```
-
-```java
-Server server = new Server("https://horizon-testnet.stellar.org");
-
-// Keys for accounts to issue and receive the new asset
-KeyPair issuerKeys = KeyPair
-  .fromSecretSeed("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4");
-KeyPair receivingKeys = KeyPair
-  .fromSecretSeed("SDSAVCRE5JRAI7UFAVLE5IMIZRD6N6WOJUWKY4GFN34LOBEEUS4W2T2D");
-
-// Create an object to represent the new asset
-Asset astroDollar = Asset.createNonNativeAsset("AstroDollar", issuerKeys.getAccountId());
-
-// First, the receiving account must trust the asset
-AccountResponse receiving = server.accounts().account(receivingKeys.getAccountId());
-Transaction allowAstroDollars = new Transaction.Builder(receiving, Network.TESTNET)
-  .addOperation(
-    // The `ChangeTrust` operation creates (or alters) a trustline
-    // The second parameter limits the amount the account can hold
-    new ChangeTrustOperation.Builder(astroDollar, "1000").build())
-  .build();
-allowAstroDollars.sign(receivingKeys);
-server.submitTransaction(allowAstroDollars);
-
-// Second, the issuing account actually sends a payment using the asset
-AccountResponse issuer = server.accounts().account(issuerKeys.getAccountId());
-Transaction sendAstroDollars = new Transaction.Builder(issuer, Network.TESTNET)
-  .addOperation(
-    new PaymentOperation.Builder(receivingKeys.getAccountId(), astroDollar, "10").build())
-  .build();
-sendAstroDollars.sign(issuerKeys);
-server.submitTransaction(sendAstroDollars);
-```
-
-```go
-package main
-
-import (
-  "github.com/stellar/go-stellar-sdk/clients/horizonclient"
-  "github.com/stellar/go-stellar-sdk/keypair"
-  "github.com/stellar/go-stellar-sdk/network"
-  "github.com/stellar/go-stellar-sdk/txnbuild"
-  "log"
-)
-
-func main() {
-  client := horizonclient.DefaultTestNetClient
-
-  // Remember, these are just examples, so replace them with your own seeds.
-  issuerSeed := "SDR4C2CKNCVK4DWMTNI2IXFJ6BE3A6J3WVNCGR6Q3SCMJDTSVHMJGC6U"
-  distributorSeed := "SBUW3DVYLKLY5ZUJD5PL2ZHOFWJSVWGJA47F6FLO66UUFZLUUA2JVU5U"
-
-  /*
-   * We omit error checks here for brevity, but you should always check your
-   * return values.
-   */
-
-  // Keys for accounts to issue and distribute the new asset.
-  issuer, err := keypair.ParseFull(issuerSeed)
-  distributor, err := keypair.ParseFull(distributorSeed)
-
-  request := horizonclient.AccountRequest{AccountID: issuer.Address()}
-  issuer_account, err := client.AccountDetail(request)
-
-  request = horizonclient.AccountRequest{AccountID: distributor.Address()}
-  distributorAccount, err := client.AccountDetail(request)
-
-  // Create an object to represent the new asset
-  astroDollar := txnbuild.CreditAsset{Code: "AstroDollar", Issuer: issuer.Address()}
-
-  // First, the receiving (distribution) account must trust the asset from the
-  // issuer.
-  tx, err := txnbuild.NewTransaction(
-    txnbuild.TransactionParams{
-      SourceAccount:        distributorAccount.AccountID,
-      IncrementSequenceNum: true,
-      BaseFee:              txnbuild.MinBaseFee,
-      Preconditions: txnbuild.Preconditions{
-				TimeBounds: txnbuild.NewInfiniteTimeout(),
-			},
-      Operations: []txnbuild.Operation{
-        &txnbuild.ChangeTrust{
-          Line:  astroDollar,
-          Limit: "5000",
-        },
-      },
-    },
-  )
-
-  signedTx, err := tx.Sign(network.TestNetworkPassphrase, distributor)
-  resp, err := client.SubmitTransaction(signedTx)
-  if err != nil {
-    log.Fatal(err)
-  } else {
-    log.Printf("Trust: %s\n", resp.Hash)
-  }
-
-  // Second, the issuing account actually sends a payment using the asset
-  tx, err = txnbuild.NewTransaction(
-    txnbuild.TransactionParams{
-      SourceAccount:        issuer_account.AccountID,
-      IncrementSequenceNum: true,
-      BaseFee:              txnbuild.MinBaseFee,
-      Preconditions: txnbuild.Preconditions{
-				TimeBounds: txnbuild.NewInfiniteTimeout(),
-			},
-      Operations: []txnbuild.Operation{
-        &txnbuild.Payment{
-          Destination: distributor.Address(),
-          Asset:       astroDollar,
-          Amount:      "10",
-        },
-      },
-    },
-  )
-
-  signedTx, err = tx.Sign(network.TestNetworkPassphrase, issuer)
-  resp, err = client.SubmitTransaction(signedTx)
-
-  if err != nil {
-    log.Fatal(err)
-  } else {
-    log.Printf("Pay: %s\n", resp.Hash)
-  }
-}
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tokens/publishing-asset-info.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tokens/publishing-asset-info.mdx
deleted file mode 100644
index 137ca527d2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tokens/publishing-asset-info.mdx
+++ /dev/null
@@ -1,369 +0,0 @@
----
-title: Publicar información sobre un activo
-sidebar_position: 80
----
-
-Los activos Stellar se definen por quién los emitió, qué representan y los términos y condiciones de su uso. Todos estos deben ser definidos y hechos públicos por el emisor en un [archivo de información Stellar](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md). Es crucial proporcionar información clara sobre lo que representa. En Stellar, haces eso vinculando tu cuenta emisora a un dominio principal, publicando un archivo de información Stellar en ese dominio y asegurándote de que ese archivo esté completo y sea preciso.
-
-Los emisores de activos más exitosos proporcionan a los exchanges, billeteras y posibles compradores mucha información sobre sí mismos para establecer confianza.
-
-Completar tu archivo de información Stellar no es un paso que puedas omitir.
-
-## ¿Qué es un archivo de información Stellar?
-
-Un archivo de información Stellar es un lugar común donde Internet puede encontrar información sobre la integración Stellar de tu organización. Lo escribes en TOML, un formato de archivo de configuración simple y ampliamente utilizado, diseñado para ser legible tanto por humanos como por máquinas, y lo publicas en `https://YOUR_DOMAIN/.well-known/stellar.toml`.
-
-De esta manera, todos saben dónde encontrarlo, cualquiera puede buscarlo y demuestra que el propietario del dominio HTTPS que aloja el `stellar.toml` asume la responsabilidad de las cuentas y activos listados en él.
-
-Usando una operación `set_options`, puedes vincular tu cuenta Stellar al dominio que aloja tu archivo de información Stellar, creando así una conexión definitiva on-chain entre esta información y esa cuenta.
-
-## Completar tu `stellar.toml`
-
-La primera Propuesta del Ecosistema Stellar (SEP) es [SEP-0001: Archivo de Información Stellar](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) y especifica todo lo que alguna vez necesitarías incluir en tu archivo de información Stellar. Esta sección recorrerá las secciones de SEP-0001 que se relacionan con los emisores de activos. Utiliza esta sección junto con el SEP para asegurarte de completar correctamente tu `stellar.toml`.
-
-Las cuatro secciones que cubriremos son:
-
-1. Información General
-2. Documentación de la Organización
-3. Documentación del Punto de Contacto
-4. Documentación de la Moneda
-
-Para cada una de esas secciones, te haremos saber qué campos son obligatorios, lo que significa que todos los emisores de activos deben incluirlos para ser listados por exchanges y billeteras, y cuáles campos son sugeridos. Completar los campos sugeridos es una buena manera de hacer que tu activo destaque.
-
-**Nota:** es una buena idea mantener las secciones en el orden presentado en SEP-0001: Archivo de Información Stellar, que también es el orden en que se presentan aquí. TOML requiere que las matrices estén al final, por lo que si revuelves el orden, puedes causar errores para los analizadores de TOML.
-
-### 1. Información General
-
-Campo obligatorio para todos los emisores de activos:
-
-- `ACCOUNTS`: Una lista de claves públicas para todas las cuentas Stellar asociadas con tu activo.
-
-Listar tus claves públicas permite a los usuarios confirmar que las posees. Por ejemplo, cuando [google.com](https://google.com/) aloja un archivo `stellar.toml`, los usuarios pueden estar seguros de que solo las cuentas que se enumeran pertenecen a Google. Si alguien dice: "Necesitas pagar tu factura de Google este mes, envía el pago a la dirección GIAMGOOGLEIPROMISE", pero esa clave no está listada en el `stellar.toml` de Google, entonces los usuarios saben que no deben confiar en ella.
-
-Hay varios campos donde enumeras información sobre tu integración Stellar para facilitar su descubrimiento. Si eres un servicio ancla, y has establecido infraestructura para interoperar con billeteras y permitir el depósito y la retirada de activos dentro de la aplicación, asegúrate de incluir las ubicaciones de tus servidores en tu archivo `stellar.toml` para que esas billeteras sepan dónde encontrar los endpoints relevantes a consultar. En particular, enumera estos:
-
-#### Campos sugeridos para emisores de activos:
-
-- `TRANSFER_SERVER` si admites [SEP-0006: API de Depósito y Retirada](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md)
-- `TRANSFER_SERVER_SEP0024` si admites [SEP-0024: Depósito y Retirada Interactiva](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md)
-- `KYC_SERVER` si admites [SEP-0012: API KYC](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)
-- `WEB_AUTH_ENDPOINT` si admites [SEP-0010: Autenticación Web Stellar](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md)
-- `DIRECT_PAYMENT_SERVER` si admites [SEP-0031: API de Pagos Transnacionales](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md)
-
-Si admites otras Propuestas del Ecosistema Stellar — como federación o firma delegada — o aloja una instancia pública de Horizon que otras personas puedan usar para consultar el ledger, también deberías agregar la ubicación de esos recursos a [Información General](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md#general-information) para que sean descubribles.
-
-### 2. Documentación de la Organización
-
-La información básica sobre tu organización se incluye en una tabla TOML llamada [`DOCUMENTATION`]. La documentación de la organización es tu oportunidad para informar a los exchanges y compradores sobre tu negocio y demostrar que tu negocio es legítimo y de confianza.
-
-#### Campo obligatorio para todos los emisores de activos:
-
-- `ORG_NAME` El nombre legal de tu organización, y si tu negocio tiene uno, su ORG_DBA oficial.
-- `ORG_URL` La URL HTTPS del sitio web oficial de tu organización. Para demostrar que el sitio web es tuyo, debes hospedarlo en el mismo dominio que enumeras aquí. De esta manera, los exchanges y compradores pueden ver el certificado SSL en tu sitio web y sentirse razonablemente seguros de que eres quien dices ser.
-- `ORG_LOGO` Una URL a un logotipo de la empresa, que aparecerá junto a tu organización en los exchanges. Esta imagen debe tener una relación de aspecto cuadrada como PNG transparente, preferiblemente de tamaño 128x128. Si no proporcionas un logotipo, el ícono junto a tu organización aparecerá en blanco en muchos exchanges.
-- `ORG_PHYSICAL_ADDRESS` La dirección física de tu organización. Entendemos que puedes querer mantener privada tu dirección laboral. Al menos, deberías poner la ciudad y el país en el que operas. Una dirección de calle es ideal y proporciona un mayor nivel de confianza y transparencia a tus posibles tenedores de activos.
-- `ORG_OFFICIAL_EMAIL` La mejor dirección de correo electrónico comercial para tu organización. Este debería estar hospedado en el mismo dominio que tu sitio web oficial.
-- `ORG_SUPPORT_EMAIL` El mejor correo para solicitudes de soporte.
-
-#### Campos sugeridos para emisores de activos:
-
-- `ORG_GITHUB` La cuenta oficial de Github de tu organización.
-- `ORG_KEYBASE` La cuenta oficial de Keybase de tu organización. Tu cuenta de Keybase debería contener prueba de propiedad de cualquier cuenta pública en línea que enumeres aquí, incluyendo el dominio de tu organización.
-- `ORG_TWITTER` El identificador oficial de Twitter de tu organización.
-- `ORG_DESCRIPTION` Una descripción de tu organización. Esto es bastante abierto, y puedes escribir tanto como desees. Es un lugar ideal para distinguirte describiendo lo que haces.
-
-Los emisores que enumeran información verificada, incluidos los documentos de verificación de teléfono/dirección y las verificaciones de Keybase, son priorizados por los clientes de Stellar.
-
-### 3. Documentación del Punto de Contacto
-
-La información sobre el/los principales punto(s) de contacto de tu organización va en un [array de tablas](https://github.com/toml-lang/toml#array-of-tables) TOML llamado `[[PRINCIPALS]]`. Necesitas proporcionar información de contacto para al menos una persona en tu organización. Si no lo haces, los exchanges no pueden verificar tu oferta, y es poco probable que los compradores estén interesados. Se pueden agregar múltiples principales con entradas adicionales de `[[PRINCIPALS]]`.
-
-#### Campo obligatorio para todos los emisores de activos:
-
-- `name` El nombre del contacto principal.
-- `email` La dirección de correo electrónico oficial del contacto principal. Este debería estar hospedado en el mismo dominio que el sitio web oficial de tu organización.
-
-#### Campos sugeridos para emisores de activos:
-
-- `github` La cuenta personal de Github del punto de contacto.
-- `twitter` El identificador personal de Twitter del punto de contacto.
-- `keybase` La cuenta personal de Keybase del punto de contacto. Esta cuenta debería contener prueba de propiedad de cualquier cuenta pública en línea listada aquí y puede contener prueba de propiedad del dominio de tu organización.
-
-### 4. Documentación de la Moneda
-
-La información sobre el/los activo(s) que emites va en un [array de tablas](https://github.com/toml-lang/toml#array-of-tables) TOML llamado `[[CURRENCIES]]`. Si emites múltiples activos, puedes incluirlos todos en un solo `stellar.toml`. Cada activo debe tener su propia entrada `[[CURRENCIES]]`.
-
-(Estas entradas también se utilizan para los activos que apoyas pero no emites, pero como esta sección se centra en la emisión de activos, el lenguaje reflejará eso.)
-
-#### Campo obligatorio para todos los emisores de activos:
-
-- `code` El código del activo. Esta es una de las dos piezas clave de información que identifican tu token. Sin ella, tu token no puede ser listado en ninguna parte.
-- `issuer` La clave pública Stellar de la cuenta emisora. Esta es la segunda pieza clave de información que identifica tu token. Sin ella, tu token no puede ser listado en ninguna parte.
-- `is_asset_anchored` Una indicación de si tu token está anclado o es nativo: verdadero si tu token puede ser redimido por un activo fuera de la red Stellar, falso si no puede. Los exchanges utilizan esta información para clasificar los tokens por tipo en las listas. Si no proporcionas esto, es poco probable que tu token aparezca en vistas de mercado filtradas.
-
-Si estás emitiendo tokens anclados (ligados, stablecoin, respaldados por activos), hay varios campos adicionales requeridos:
-
-- `anchor_asset_type` El tipo de activo que representa tu token. Las categorías posibles son fiat, cripto, acciones, bonos, productos básicos, bienes raíces y otros.
-- `anchor_asset` El nombre del activo que sirve de ancla para tu token.
-- `redemption_instructions` Instrucciones para redimir tu token por el activo subyacente.
-- `attestation_of_reserve` Una URL para la atestación u otra prueba, evidencia o verificación de reservas, como auditorías de terceros, que todos los emisores de stablecoins deberían ofrecer para cumplir con las prácticas recomendadas.
-
-#### Campos sugeridos para emisores de activos:
-
-- `desc` Una descripción de tu token y de lo que representa. Este es un buen lugar para aclarar qué hace tu token y por qué alguien podría querer poseerlo.
-- `conditions` Cualquier condición que impongas a la redención de tu token.
-- `image` Una URL a una imagen PNG o GIF con un fondo transparente que represente tu token. Sin ella, tu token aparecerá en blanco en muchos exchanges.
-
-## Cómo publicar tu archivo de información Stellar
-
-Después de seguir los pasos anteriores para completar tu archivo de información Stellar, publícalo en la siguiente ubicación: `https://YOUR_DOMAIN/.well-known/stellar.toml`
-
-Habilita CORS para que las personas puedan acceder a este archivo desde otros sitios, y establece el siguiente encabezado para una respuesta HTTP para una solicitud de archivo `/.well-known/stellar.toml`.
-
-`Access-Control-Allow-Origin:` \*
-
-Establece un tipo de contenido `text/plain` para que los navegadores rendericen el contenido en lugar de solicitar una descarga.
-
-`content-type: text/plain`
-
-También deberías usar la operación `set_options` para establecer el dominio principal en tu cuenta emisora.
-
-```nginx title="Configure stellar.toml for nginx"
-server {
-  server_name my.example.com;
-  root /var/www/my.example.com;
-
-  location = /.well-known/stellar.toml {
-    types { } default_type "text/plain; charset=utf-8";
-    allow all;
-    if ($request_method = 'OPTIONS') {
-      add_header 'Access-Control-Allow-Origin' '*';
-      add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS';
-      add_header 'Content-Length' 0;
-      return 204;
-    }
-    if ($request_method = 'GET') {
-      add_header 'Access-Control-Allow-Origin' '*';
-      add_header 'Access-Control-Allow-Methods' 'GET, OPTIONS';
-      add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range';
-    }
-  }
-
-  // CertBot SSL configuration
-  // ...
-}
-```
-
-## Código de ejemplo para establecer el dominio principal de tu cuenta emisora
-
-<CodeExample title="Establecer Dominio Principal">
-
-```js
-var StellarSdk = require("stellar-sdk");
-var server = new StellarSdk.Horizon.Server(
-  "https://horizon-testnet.stellar.org",
-);
-
-// Keys for issuing account
-var issuingKeys = StellarSdk.Keypair.fromSecret(
-  "SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4",
-);
-
-server
-  .loadAccount(issuingKeys.publicKey())
-  .then(function (issuer) {
-    var transaction = new StellarSdk.TransactionBuilder(issuer, {
-      fee: 100,
-      networkPassphrase: StellarSdk.Networks.TESTNET,
-    })
-      .addOperation(
-        StellarSdk.Operation.setOptions({
-          homeDomain: "yourdomain.com",
-        }),
-      )
-      // setTimeout is required for a transaction
-      .setTimeout(100)
-      .build();
-    transaction.sign(issuingKeys);
-    return server.submitTransaction(transaction);
-  })
-  .then(console.log)
-  .catch(function (error) {
-    console.error("Error!", error);
-  });
-```
-
-```python
-from stellar_sdk import Keypair, Network, Server, TransactionBuilder
-from stellar_sdk.exceptions import BaseHorizonError
-
-# Configure Stellar SDK to talk to the horizon instance hosted by Stellar.org
-# To use the live network, set the hostname to horizon_url for mainnet
-server = Server(horizon_url="https://horizon-testnet.stellar.org")
-# Use the test network, if you want to use the live network, please set it to `Network.PUBLIC_NETWORK_PASSPHRASE`
-network_passphrase = Network.TESTNET_NETWORK_PASSPHRASE
-
-# Keys for accounts to issue and receive the new asset
-issuing_keypair = Keypair.from_secret("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4")
-issuing_public = issuing_keypair.public_key
-
-# Transactions require a valid sequence number that is specific to this account.
-# We can fetch the current sequence number for the source account from Horizon.
-issuing_account = server.load_account(issuing_public)
-
-transaction = (
-  TransactionBuilder(
-    source_account = issuing_account,
-    network_passphrase = network_passphrase,
-    base_fee = 100,
-  )
-  .append_set_options_op(
-    home_domain = "yourdomain.com"
-  )
-  .build()
-)
-transaction.sign(issuing_keypair)
-
-try:
-  transaction_resp = server.submit_transaction(transaction)
-  print(f"Transaction Resp:\n{transaction_resp}")
-except BaseHorizonError as e:
-  print(f"Error: {e}")
-```
-
-```java
-Server server = new Server("https://horizon-testnet.stellar.org");
-
-// Keys for issuing account
-KeyPair issuingKeys = KeyPair
-  .fromSecretSeed("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4");
-AccountResponse sourceAccount = server.accounts().account(issuingKeys.getAccountId());
-
-Transaction setHomeDomain = new Transaction.Builder(sourceAccount, Network.TESTNET)
-  .addOperation(new SetOptionsOperation.Builder()
-    .setHomeDomain("yourdomain.com").build())
-  .build();
-setHomeDomain.sign(issuingKeys);
-server.submitTransaction(setHomeDomain);
-```
-
-```go
-func main() {
-	client := horizonclient.DefaultTestNetClient
-
-	// Keys for issuing account
-	issuingKeypair := keypair.MustParseFull("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U6MM63WBSBZATAQI3EBTQ4")
-	issuingAccount, err := client.AccountDetail(horizonclient.AccountRequest{AccountID: issuingKeypair.Address()})
-	if err != nil {
-		log.Fatal(err)
-	}
-
-	// Build the transaction
-  tx, err := txnbuild.NewTransaction(
-    txnbuild.TransactionParams{
-      SourceAccount:        &issuingAccount,
-      IncrementSequenceNum: true,
-      BaseFee:              txnbuild.MinBaseFee,
-      Preconditions:        txnbuild.Preconditions{TimeBounds: txnbuild.NewTimeout(100)},
-      Operations: []txnbuild.Operation{
-        &txnbuild.SetOptions{
-          HomeDomain: "yourdomain.com",
-        },
-      },
-    },
-  )
-	if err != nil {
-		log.Fatal(err)
-	}
-
-	tx, err = tx.Sign(network.TestNetworkPassphrase, issuingKeypair)
-	if err != nil {
-		log.Fatal(err)
-	}
-
-  resp, err := client.SubmitTransaction(tx)
-	if err != nil {
-		log.Fatal(err)
-	}
-
-	fmt.Println("Transaction response:", resp)
-}
-```
-
-</CodeExample>
-
-## Ejemplo de `stellar.toml`
-
-<CodeExample>
-
-```toml
-NETWORK_PASSPHRASE="Public Global Stellar Network ; September 2015"
-FEDERATION_SERVER="https://api.domain.com/federation"
-AUTH_SERVER="https://api.domain.com/auth"
-TRANSFER_SERVER="https://api.domain.com"
-SIGNING_KEY="GBBHQ7H4V6RRORKYLHTCAWP6MOHNORRFJSDPXDFYDGJB2LPZUFPXUEW3"
-HORIZON_URL="https://horizon.domain.com"
-ACCOUNTS=[
-"GD5DJQDDBKGAYNEAXU562HYGOOSYAEOO6AS53PZXBOZGCP5M2OPGMZV3",
-"GAENZLGHJGJRCMX5VCHOLHQXU3EMCU5XWDNU4BGGJFNLI2EL354IVBK7",
-"GAOO3LWBC4XF6VWRP5ESJ6IBHAISVJMSBTALHOQM2EZG7Q477UWA6L7U"
-]
-VERSION="2.0.0"
-
-[DOCUMENTATION]
-ORG_NAME="Organization Name"
-ORG_DBA="Organization DBA"
-ORG_URL="https://www.domain.com"
-ORG_LOGO="https://www.domain.com/awesomelogo.png"
-ORG_DESCRIPTION="Description of issuer"
-ORG_PHYSICAL_ADDRESS="123 Sesame Street, New York, NY 12345, United States"
-ORG_PHYSICAL_ADDRESS_ATTESTATION="https://www.domain.com/address_attestation.jpg"
-ORG_PHONE_NUMBER="1 (123)-456-7890"
-ORG_PHONE_NUMBER_ATTESTATION="https://www.domain.com/phone_attestation.jpg"
-ORG_KEYBASE="accountname"
-ORG_TWITTER="orgtweet"
-ORG_GITHUB="orgcode"
-ORG_OFFICIAL_EMAIL="support@domain.com"
-
-[[PRINCIPALS]]
-name="Jane Jedidiah Johnson"
-email="jane@domain.com"
-keybase="crypto_jane"
-twitter="crypto_jane"
-github="crypto_jane"
-id_photo_hash="be688838ca8686e5c90689bf2ab585cef1137c999b48c70b92f67a5c34dc15697b5d11c982ed6d71be1e1e7f7b4e0733884aa97c3f7a339a8ed03577cf74be09"
-verification_photo_hash="016ba8c4cfde65af99cb5fa8b8a37e2eb73f481b3ae34991666df2e04feb6c038666ebd1ec2b6f623967756033c702dde5f423f7d47ab6ed1827ff53783731f7"
-
-[[CURRENCIES]]
-code="USD"
-issuer="GCZJM35NKGVK47BB4SPBDV25477PZYIYPVVG453LPYFNXLS3FGHDXOCM"
-display_decimals=2
-
-[[CURRENCIES]]
-code="BTC"
-issuer="GAOO3LWBC4XF6VWRP5ESJ6IBHAISVJMSBTALHOQM2EZG7Q477UWA6L7U"
-display_decimals=7
-anchor_asset_type="crypto"
-anchor_asset="BTC"
-redemption_instructions="Use SEP6 with our federation server"
-collateral_addresses=["2C1mCx3ukix1KfegAY5zgQJV7sanAciZpv"]
-collateral_address_signatures=["304502206e21798a42fae0e854281abd38bacd1aeed3ee3738d9e1446618c4571d10"]
-
-# asset with meta info
-[[CURRENCIES]]
-code="GOAT"
-issuer="GD5T6IPRNCKFOHQWT264YPKOZAWUMMZOLZBJ6BNQMUGPWGRLBK3U7ZNP"
-display_decimals=2
-name="goat share"
-desc="1 GOAT token entitles you to a share of revenue from Elkins Goat Farm."
-conditions="There will only ever be 10,000 GOAT tokens in existence. We will distribute the revenue share annually on Jan. 15th"
-image="https://static.thenounproject.com/png/2292360-200.png"
-fixed_number=10000
-```
-
-</CodeExample>
-
-[sep-0001]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md
-[sep-0020]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md
-[seps]: https://github.com/stellar/stellar-protocol/tree/master/ecosystem
-[guía de twilio]: https://support.twilio.com/hc/en-us/articles/223183008-Formatting-International-Phone-Numbers
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tokens/quickstart.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tokens/quickstart.mdx
deleted file mode 100644
index 9e62ca21e1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tokens/quickstart.mdx
+++ /dev/null
@@ -1,112 +0,0 @@
----
-sidebar_position: 30
-title: Comenzar
----
-
-¡Emite tu primer activo en la red Stellar en **una sola transacción**!
-
-<CodeExample>
-
-```js
-import {
-  Keypair,
-  Horizon,
-  TransactionBuilder,
-  Networks,
-  Operation,
-  Asset,
-  BASE_FEE,
-} from "stellar-sdk";
-
-const horizonUrl = "https://horizon-testnet.stellar.org";
-const friendbotUrl = "https://friendbot.stellar.org";
-
-const issuerKeypair = Keypair.random();
-const destinationKeypair = Keypair.random();
-
-console.log(
-  `issuer keys:\n${issuerKeypair.publicKey()}\n${issuerKeypair.secret()}\n`,
-);
-console.log(
-  `destination account keys:\n${issuerKeypair.publicKey()}\n${issuerKeypair.secret()}\n`,
-);
-
-await fetch(friendbotUrl + `?addr=${issuerKeypair.publicKey()}`); // pre-fund the `issuer` account using friendbot
-await fetch(friendbotUrl + `?addr=${destinationKeypair.publicKey()}`); // pre-fund the `destination` account using friendbot
-
-const server = new Horizon.Server(horizonUrl);
-const account = await server.loadAccount(issuerKeypair.publicKey());
-const abcAsset = new Asset("ABC", issuerKeypair.publicKey());
-
-const transaction = new TransactionBuilder(account, {
-  fee: BASE_FEE,
-  networkPassphrase: Networks.TESTNET,
-})
-  .addOperation(
-    Operation.changeTrust({
-      asset: abcAsset,
-      source: destinationKeypair.publicKey(),
-    }),
-  )
-  .addOperation(
-    Operation.payment({
-      destination: destinationKeypair.publicKey(),
-      asset: abcAsset,
-      amount: "100",
-    }),
-  )
-  .setTimeout(30)
-  .build();
-
-transaction.sign(issuerKeypair, destinationKeypair);
-const res = await server.submitTransaction(transaction);
-console.log(`transaction hash:\n${res.hash}`);
-```
-
-```python
-import requests
-from stellar_sdk import Asset, Keypair, Network, Server, TransactionBuilder
-
-horion_url = "https://horizon-testnet.stellar.org"
-friendbot_url = "https://friendbot.stellar.org"
-
-issuer_keypair = Keypair.random()
-destination_keypair = Keypair.random()
-
-print(f"issuer keys:\n{issuer_keypair.public_key}\n{issuer_keypair.secret}\n")
-print(f"issuer keys:\n{destination_keypair.public_key}\n{destination_keypair.secret}\n")
-
-requests.get(f"{friendbot_url}?addr={issuer_keypair.public_key}")
-requests.get(f"{friendbot_url}?addr={destination_keypair.public_key}")
-
-server = Server('https://horizon-testnet.stellar.org')
-account = server.load_account(issuer_keypair.public_key)
-abc_asset = Asset('ABC', issuer_keypair.public_key)
-
-transaction = (
-    TransactionBuilder(
-        source_account=account,
-        network_passphrase=Network.TESTNET_NETWORK_PASSPHRASE,
-        base_fee=100,
-    )
-    .append_change_trust_op(
-        asset=abc_asset,
-        source=destination_keypair.public_key,
-    )
-    .append_payment_op(
-        destination=destination_keypair.public_key,
-        amount='100',
-        asset=abc_asset,
-    )
-    .set_timeout(30)
-    .build()
-)
-
-transaction.sign(issuer_keypair)
-transaction.sign(destination_keypair)
-
-res = server.submit_transaction(transaction)
-print(f"Transaction hash:\n{res['hash']}")
-```
-
-</CodeExample>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tokens/stellar-asset-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tokens/stellar-asset-contract.mdx
deleted file mode 100644
index 3581fbf628..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tokens/stellar-asset-contract.mdx
+++ /dev/null
@@ -1,256 +0,0 @@
----
-sidebar_position: 50
-title: Usar Activos Emitidos en Contratos Inteligentes con el Stellar Asset Contract (SAC)
-description: Aprende a realizar pagos e interactuar con activos emitidos en la red Stellar en contratos inteligentes usando el Stellar Asset Contract (SAC), un contrato incorporado.
-sidebar_label: Contrato de Activo Stellar
----
-
-:::info
-
-El término "custom token" ha sido desaprobado en favor de "contract token". Ve la conversación en el [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
-
-:::
-
-# Contrato de Activos Stellar (SAC)
-
-El Contrato de Activo Stellar (SAC) es una implementación de [CAP-46-6 Activo Estandarizado de Contrato Inteligente] y [SEP-41 Interfaz de Token] para los [activos] Stellar.
-
-Ve ejemplos de cómo usar el SAC en las [Guías de Cómo Hacer Tokens](../build/guides/tokens/README.mdx).
-
-## Descripción general
-
-:::note
-
-Los activos Stellar son emitidos por cuentas Stellar. Emite un activo en Stellar siguiendo el [Tutorial para Emitir un Activo](./how-to-issue-an-asset.mdx).
-
-:::
-
-El Contrato de Activo Stellar permite a usuarios y contratos realizar pagos con, e interactuar con, activos. El SAC puede interactuar con activos mantenidos por cuentas o contratos Stellar.
-
-El SAC es un contrato incorporado especial que tiene acceso a la funcionalidad de la red Stellar que le permite usar activos Stellar directamente.
-
-Cada activo Stellar tiene una instancia del SAC reservada en la red. Para usar el SAC reservado para un activo, solo necesita ser implementada la instancia.
-
-Cuando el SAC transfiere activos entre cuentas, ocurren los mismos débitos y créditos que cuando se utiliza una operación de pago Stellar, porque el SAC interactúa directamente con las líneas de confianza de la cuenta Stellar. Cuando el SAC transfiere activos entre contratos, utiliza entradas del libro mayor de Datos del Contrato para almacenar los saldos de los contratos.
-
-Los saldos de cuentas Stellar para el activo nativo siempre se almacenan en la cuenta, y los saldos de contratos Stellar para el activo nativo siempre se almacenan en una entrada de datos del contrato.
-
-Los saldos de cuentas Stellar para activos emitidos siempre se almacenan en líneas de confianza, y los saldos de contratos Stellar para activos emitidos siempre se almacenan en una entrada de datos del contrato.
-
-Por ejemplo, al transferir de una cuenta Stellar a un contrato Stellar, se debita la entrada de la línea de confianza de la cuenta Stellar y se acredita una entrada de datos del contrato.
-
-Y, por ejemplo, al transferir de un contrato Stellar a una cuenta Stellar, se debita una entrada de datos del contrato y se acredita la entrada de la línea de confianza de la cuenta.
-
-En ambos ejemplos, es un solo activo el que se transfiere de la cuenta al contrato y de regreso. No se requiere puente y no se necesitan tokens intermedios. Un activo en Stellar y su Stellar Asset Contract representan el mismo activo. El SAC de un activo es simplemente una API para interactuar con el activo.
-
-El SAC implementa la [Interfaz de Token SEP-41], que es similar al ampliamente utilizado estándar de token ERC-20. Contracts that depend on only the SEP-41 portion of the SAC's interface, are also compatible with any contract token that implements SEP-41.
-
-Algunas funcionalidades disponibles en la red Stellar en operaciones de transacción, como el libro de órdenes, no tienen funciones expuestas en el Contrato de Activo Stellar en el protocolo actual.
-
-## Implementación
-
-Cada activo Stellar en Stellar tiene una dirección de contrato reservada a la que se puede implementar el Contrato de Activo Stellar. Cualquiera puede iniciar la implementación y el emisor del activo Stellar no necesita estar involucrado.
-
-Se puede desplegar utilizando el [Stellar CLI] como se muestra [aquí](../tools/cli/cookbook/deploy-stellar-asset-contract.mdx).
-
-O el [Stellar SDK] puede usarse como se muestra [aquí](../learn/fundamentals/contract-development/contract-interactions/stellar-transaction.mdx#xdr-usage) llamando a `InvokeHostFunctionOp` con `HOST_FUNCTION_TYPE_CREATE_CONTRACT` y `CONTRACT_ID_FROM_ASSET`. El recurso token tendrá un identificador determinista, que será el hash sha256 de `HashIDPreimage::ENVELOPE_TYPE_CONTRACT_ID_FROM_ASSET` xdr especificado [aquí][contract_id].
-
-Cualquiera puede implementar las instancias del Contrato de Activo Stellar. Nota que la inicialización de los Contratos de Activo Stellar ocurre automáticamente durante la implementación. El emisor del activo tendrá los permisos administrativos después de que se haya implementado el contrato.
-
-[contract_id]: https://github.com/stellar/stellar-xdr/blob/dc23adf60e095a6ce626b2b09128e58a5eae0cd0/Stellar-transaction.x#L661
-[cli stellar]: ../tools/cli/stellar-cli.mdx
-[sdk stellar]: ../tools/sdks/README.mdx
-
-## Interacción con activos clásicos de Stellar
-
-El Contrato de Activo Stellar es la única manera para que los contratos interactúen con activos Stellar, ya sea el activo nativo XLM, o aquellos emitidos por cuentas Stellar.
-
-El emisor del activo será el administrador del contrato implementado. Debido a que el token nativo Stellar no tiene un emisor, tampoco tendrá un administrador. Tampoco puede ser quemado.
-
-Después de que se ha implementado el contrato, los usuarios pueden usar su saldo de cuenta clásica (para lúmenes) o línea de confianza (para otros activos). Hay algunas diferencias dependiendo de si estás usando una cuenta clásica `Address` vs un `Address` de contrato (correspondiente a un contrato regular o a un contrato de cuenta personalizado). La siguiente sección hace referencia a algunas banderas de emisor y línea de confianza de Stellar clásico, sobre las cuales puedes aprender más [aquí](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags).
-
-- Usando `Address::Account`
-  - El saldo debe existir en una línea de confianza (o en una cuenta para el saldo nativo). Esto significa que el contrato no almacenará el saldo en ContractData. Si falta la línea de confianza o la cuenta, cualquier función que intente interactuar con ese saldo fallará.
-  - Se seguirán las Semánticas de Línea de Confianza clásicas.
-    - Las transferencias solo tendrán éxito si las líneas de confianza correspondientes tienen el `AUTHORIZED_FLAG` configurado.
-    - Un saldo de línea de confianza solo puede recuperarse usando la función de contrato `clawback` si la línea de confianza tiene la bandera `TRUSTLINE_CLAWBACK_ENABLED_FLAG` configurada.
-    - Las transferencias a la cuenta del emisor quemarán el token, mientras que las transferencias desde la cuenta del emisor acuñarán.
-    - Los saldos de la línea de confianza se almacenan en un entero con signo de 64 bits, aunque la interfaz acepta enteros con signo de 128 bits. Cualquier operación que intente enviar o recibir un monto mayor que el monto máximo que puede ser representado por un entero con signo de 64 bits fallará.
-- Usando `Address::Contract`
-  - El saldo y el estado de autorización se almacenarán en el almacenamiento del contrato, en lugar de una línea de confianza.
-  - Los saldos se almacenan en un entero con signo de 128 bits.
-  - Un saldo solo puede recuperarse si la cuenta del emisor tenía la bandera `AUTH_CLAWBACK_ENABLED_FLAG` configurada cuando se creó el saldo. Un saldo se crea cuando un `Address::Contract` está en el extremo receptor de una transferencia exitosa, o si el administrador establece el estado de autorización. Lee más sobre `AUTH_CLAWBACK_ENABLED_FLAG` [aquí](./control-asset-access.mdx#clawback-enabled-0x8).
-
-### Autorización de Saldo Requerida
-
-En el caso de `Address::Contract`, si el emisor tiene la bandera `AUTH_REQUIRED_FLAG` configurada, entonces el `Address::Contract` especificado necesitará ser autorizado explícitamente con `set_auth` antes de poder recibir un saldo. Esta lógica se alinea con cómo interactúan las líneas de confianza con la bandera de emisor `AUTH_REQUIRED_FLAG`, permitiendo a los emisores de activos tener el mismo control en Soroban que tienen en Stellar clásico. Lee más sobre `AUTH_REQUIRED_FLAG` [aquí](./control-asset-access.mdx#authorization-required-0x1).
-
-### Revocación de Autorización
-
-El administrador solo puede revocar la autorización de un `Address`, si el emisor del activo tiene la bandera `AUTH_REVOCABLE_FLAG` configurada. La desautorización fallará si falta el emisor. Este requisito es verdadero tanto para los saldos de línea de confianza de `Address::Account` como para los saldos de contrato de `Address:Contract`. Nota que cuando una línea de confianza es desautorizada desde Soroban, la bandera `AUTHORIZED_FLAG` se borra y la bandera `AUTHORIZED_TO_MAINTAIN_LIABILITIES_FLAG` se establece para evitar tener que retirar ofertas y canjear participaciones en el fondo.
-
-## Semánticas de Autorización
-
-Consulta la [visión general de autorización](../learn/fundamentals/contract-development/authorization.mdx) y el [ejemplo de autorización](../build/smart-contracts/example-contracts/auth.mdx) para obtener información general sobre la autorización en Soroban.
-
-El contrato de token contiene tres tipos de operaciones que siguen la [interfaz](./token-interface.mdx#code):
-
-- obtenedores, como `balance`, que no cambian el estado del contrato
-- mutadores no privilegiados, como `incr_allow` y `xfer`, que cambian el estado del contrato pero no requieren privilegios especiales
-- mutadores privilegiados, como `clawback` y `set_admin`, que cambian el estado del contrato pero requieren privilegios especiales
-
-Los obtenedores no requieren autorización porque no cambian el estado del contrato y todos los datos del contrato son públicos. Por ejemplo, `balance` simplemente devuelve el saldo del `Address` especificado sin cambiarlo.
-
-Los mutadores no privilegiados requieren autorización del `Address` que gasta o permite gastar su saldo. Las excepciones son las operaciones `xfer_from` y `burn_from` donde el `Address` requiere autorización de la entidad 'gastos' que ha recibido una autorización de otro `Address` previamente.
-
-Los mutadores privilegiados requieren autorización de una identidad privilegiada específica, conocida como el "administrador". Por ejemplo, solo el administrador puede `mint` más del token. De manera similar, solo el administrador puede nombrar a un nuevo administrador.
-
-## Interfaz del Contrato
-
-El [módulo `token`] del SDK de Rust contiene dos traits, y estructuras cliente correspondientes, para interactuar con SACs.
-
-1. El [trait `TokenInterface`] y la [estructura `TokenClient`] pueden usarse para invocar el "subconjunto básico" de la funcionalidad SAC. Implementan la común [Interfaz Token SEP-41], e incluyen funciones como `transfer`, `burn`, `allowance`, etc.
-2. El [trait `StellarAssetInterface`] y la [estructura `StellarAssetClient`] pueden utilizarse para invocar el "subconjunto extendido" de la funcionalidad SAC. Ellos _extienden_ la común interfaz token SEP-41 con funcionalidad administrativa. Además de todas las funciones de `TokenInterface`, estos traits contienen funciones administrativas como `set_admin`, `clawback`, `set_authorized`, etc.
-
-```rust
-pub trait StellarAssetInterface {
-    // All this is available in any SEP-41-compliant contract
-    fn allowance(env: Env, from: Address, spender: Address) -> i128;
-    fn approve(env: Env, from: Address, spender: Address, amount: i128, expiration_ledger: u32);
-    fn balance(env: Env, id: Address) -> i128;
-    fn transfer(env: Env, from: Address, to: MuxedAddress, amount: i128);
-    fn transfer_from(env: Env, spender: Address, from: Address, to: Address, amount: i128);
-    fn burn(env: Env, from: Address, amount: i128);
-    fn burn_from(env: Env, spender: Address, from: Address, amount: i128);
-    fn decimals(env: Env) -> u32;
-    fn name(env: Env) -> String;
-    fn symbol(env: Env) -> String;
-
-    //! Everything below is specifically available to SAC instances
-
-    /// Sets the administrator to the specified address `new_admin`.
-    ///
-    /// # Arguments
-    ///
-    /// * `new_admin` - The address which will henceforth be the administrator
-    ///   of this token contract.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with topics `["set_admin", admin: Address], data =
-    /// [new_admin: Address]`
-    fn set_admin(env: Env, new_admin: Address);
-
-    /// Returns the admin of the contract.
-    ///
-    /// # Panics
-    ///
-    /// If the admin is not set.
-    fn admin(env: Env) -> Address;
-
-    /// Sets whether the account is authorized to use its balance. If
-    /// `authorized` is true, `id` should be able to use its balance.
-    ///
-    /// # Arguments
-    ///
-    /// * `id` - The address being (de-)authorized.
-    /// * `authorize` - Whether or not `id` can use its balance.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with topics `["set_authorized", id: Address], data =
-    /// [authorize: bool]`
-    fn set_authorized(env: Env, id: Address, authorize: bool);
-
-    /// Returns true if `id` is authorized to use its balance.
-    ///
-    /// # Arguments
-    ///
-    /// * `id` - The address for which token authorization is being checked.
-    fn authorized(env: Env, id: Address) -> bool;
-
-    /// Mints `amount` to `to`.
-    ///
-    /// # Arguments
-    ///
-    /// * `to` - The address which will receive the minted tokens.
-    /// * `amount` - The amount of tokens to be minted.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with topics `["mint", to: Address], data
-    /// = amount: i128`
-    fn mint(env: Env, to: Address, amount: i128);
-
-    /// Clawback `amount` from `from` account. `amount` is burned in the
-    /// clawback process.
-    ///
-    /// # Arguments
-    ///
-    /// * `from` - The address holding the balance from which the clawback will
-    ///   take tokens.
-    /// * `amount` - The amount of tokens to be clawed back.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with topics `["clawback", admin: Address, to: Address],
-    /// data = amount: i128`
-    fn clawback(env: Env, from: Address, amount: i128);
-}
-```
-
-## Errores de contrato
-
-Todos los contratos inteligentes integrados en la red Stellar comparten los mismos tipos de error, que se describen a continuación.
-
-```rust
-#[derive(Debug, FromPrimitive, PartialEq, Eq)]
-pub(crate) enum ContractError {
-    // Indicates an internal error in protocol implementation, such as invalid
-    // ledger state. This may not happen in the real networks, but might appear
-    // when using malformed test data (such as malformed ledger snapshots).
-    InternalError = 1,
-    // Indicates an impossible function has been invoked, such as clawback for
-    // an asset that does not have clawback enabled. Or, an operation has been
-    // called affecting the issuer's trustline.
-    OperationNotSupportedError = 2,
-    // Indicates the SAC has already been initialized. This error may only occur
-    // during initialization of an asset's SAC instance.
-    AlreadyInitializedError = 3,
-    // Unused = 4, - this error code is not used by SAC
-    // Unused = 5, - this error code is not used by SAC
-    // An account that would be modified by this transaction does not exist on
-    // the network.
-    AccountMissingError = 6,
-    // Unused = 7, - this error code is not used by SAC
-    // Indicates an amount less than zero was provided for a transfer amount.
-    NegativeAmountError = 8,
-    // Indicates an insufficient spender's available allowance amount. Also used
-    // to indicate a problem with expiration ledger when creating an allowance.
-    AllowanceError = 9,
-    // Indicates too low of a balance to spend the requested amount, or a
-    // balance as a result of this transaction would be too low or high, or a
-    // problem with attempting a clawback on a non-clawback-enabled trustline.
-    BalanceError = 10,
-    // Indicates an address has had its balance authorization revoked by the
-    // asset issuer.
-    BalanceDeauthorizedError = 11,
-    // Indicates this transaction would result in a spender's allowance
-    // overflowing.
-    OverflowError = 12,
-    // Indicates a trustline entry does not exist for this address to hold this
-    // asset.
-    TrustlineMissingError = 13,
-}
-```
-
-Fuente: https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-host/src/builtin_contracts/contract_error.rs
-
-[activos]: ../learn/fundamentals/stellar-data-structures/assets.mdx
-[módulo `token`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/index.html
-[trait `TokenInterface`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/trait.TokenInterface.html
-[estructura `TokenClient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.TokenClient.html
-[trait `StellarAssetInterface`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/trait.StellarAssetInterface.html
-[Estructura `StellarAssetClient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.StellarAssetClient.html
-[cap-46-6 activo estandarizado de contrato inteligente]: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-06.md
-[interfaz de token sep-41]: ./token-interface.mdx
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tokens/token-interface.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tokens/token-interface.mdx
deleted file mode 100644
index bd2ec24b42..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tokens/token-interface.mdx
+++ /dev/null
@@ -1,250 +0,0 @@
----
-sidebar_position: 60
-title: "Crear tokens de contrato en Stellar: estándares e integración"
-description: Aprende sobre y crea tokens de contrato en la red Stellar. Conoce los estándares, la funcionalidad y la integración de los tokens de contrato.
-sidebar_label: Interfaz de Token
----
-
-:::info
-
-El término "token personalizado" ha sido reemplazado por "token de contrato". Ver la conversación en el [Stellar Developer Discord](https://discord.com/channels/897514728459468821/966788672164855829/1359276952971640953).
-
-:::
-
-# Interfaz de Token
-
-Los contratos de token, incluyendo el Contrato de Activo Stellar y ejemplos de implementaciones de tokens, exponen la siguiente interfaz común.
-
-Los tokens desplegados en Soroban pueden implementar cualquier interfaz que elijan, sin embargo, deberían cumplir con la siguiente interfaz para ser interoperables con contratos construidos para admitir los tokens integrados de Soroban.
-
-Nota que, en casos específicos, la interfaz no tiene que ser implementada completamente. For example, the contract token may not implement the administrative interface compatible with the Stellar Asset Contract - it won't stop it from being usable in the contracts that only perform the regular user operations (transfers, allowances, balances etc.).
-
-### Requisitos de Compatibilidad
-
-For any given contract function, there are three requirements that should be consistent with the interface described here:
-
-- Interfaz de función (nombre y argumentos) - si no es consistente, entonces los usuarios simplemente no podrán usar la función en absoluto. Este es el requisito firme.
-- Autorización - los usuarios tienen que autorizar las llamadas a las funciones del token con todos los argumentos de la invocación (ver los comentarios de la interfaz). If this is inconsistent, then the contract token may have issues with getting the correct signatures from the users and may also confuse the wallet software.
-- Eventos - el token tiene que emitir los eventos en el formato especificado. Si es inconsistente, entonces el token puede no ser manejado correctamente por los sistemas posteriores, como los exploradores de bloques.
-
-### Código
-
-La interfaz a continuación utiliza el Rust [soroban-sdk](../tools/sdks/contract-sdks.mdx#soroban-rust-sdk) para declarar un rasgo que cumple con la interfaz de token [SEP-41](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md).
-
-```rust
-pub trait TokenInterface {
-    /// Returns the allowance for `spender` to transfer from `from`.
-    ///
-    /// The amount returned is the amount that spender is allowed to transfer
-    /// out of from's balance. When the spender transfers amounts, the allowance
-    /// will be reduced by the amount transferred.
-    ///
-    /// # Arguments
-    ///
-    /// * `from` - The address holding the balance of tokens to be drawn from.
-    /// * `spender` - The address spending the tokens held by `from`.
-    fn allowance(env: Env, from: Address, spender: Address) -> i128;
-
-    /// Set the allowance by `amount` for `spender` to transfer/burn from
-    /// `from`.
-    ///
-    /// The amount set is the amount that spender is approved to transfer out of
-    /// from's balance. The spender will be allowed to transfer amounts, and
-    /// when an amount is transferred the allowance will be reduced by the
-    /// amount transferred.
-    ///
-    /// # Arguments
-    ///
-    /// * `from` - The address holding the balance of tokens to be drawn from.
-    /// * `spender` - The address being authorized to spend the tokens held by
-    ///   `from`.
-    /// * `amount` - The tokens to be made available to `spender`.
-    /// * `expiration_ledger` - The ledger number where this allowance expires. Cannot
-    ///    be less than the current ledger number unless the amount is being set to 0.
-    ///    An expired entry (where expiration_ledger < the current ledger number)
-    ///    should be treated as a 0 amount allowance.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with topics `["approve", from: Address,
-    /// spender: Address], data = [amount: i128, expiration_ledger: u32]`
-    fn approve(env: Env, from: Address, spender: Address, amount: i128, expiration_ledger: u32);
-
-    /// Returns the balance of `id`.
-    ///
-    /// # Arguments
-    ///
-    /// * `id` - The address for which a balance is being queried. If the
-    ///   address has no existing balance, returns 0.
-    fn balance(env: Env, id: Address) -> i128;
-
-    /// Transfer `amount` from `from` to `to`.
-    ///
-    /// # Arguments
-    ///
-    /// * `from` - The address holding the balance of tokens which will be
-    ///   withdrawn from.
-    /// * `to` - The address which will receive the transferred tokens.
-    /// * `amount` - The amount of tokens to be transferred.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with:
-    /// * topics `["transfer", from: Address, to: Address]`
-    /// * data `{ to_muxed_id: Option<u64>, amount: i128 }: Map`
-    ///
-    /// Legacy implementations may emit an event with:
-    /// * topics `["transfer", from: Address, to: Address]`
-    /// * data `amount: i128`
-    fn transfer(env: Env, from: Address, to: MuxedAddress, amount: i128);
-
-    /// Transfer `amount` from `from` to `to`, consuming the allowance that
-    /// `spender` has on `from`'s balance. Authorized by spender
-    /// (`spender.require_auth()`).
-    ///
-    /// The spender will be allowed to transfer the amount from from's balance
-    /// if the amount is less than or equal to the allowance that the spender
-    /// has on the from's balance. The spender's allowance on from's balance
-    /// will be reduced by the amount.
-    ///
-    /// # Arguments
-    ///
-    /// * `spender` - The address authorizing the transfer, and having its
-    ///   allowance consumed during the transfer.
-    /// * `from` - The address holding the balance of tokens which will be
-    ///   withdrawn from.
-    /// * `to` - The address which will receive the transferred tokens.
-    /// * `amount` - The amount of tokens to be transferred.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with topics `["transfer", from: Address, to: Address],
-    /// data = amount: i128`
-    fn transfer_from(env: Env, spender: Address, from: Address, to: Address, amount: i128);
-
-    /// Burn `amount` from `from`.
-    ///
-    /// Reduces from's balance by the amount, without transferring the balance
-    /// to another holder's balance.
-    ///
-    /// # Arguments
-    ///
-    /// * `from` - The address holding the balance of tokens which will be
-    ///   burned from.
-    /// * `amount` - The amount of tokens to be burned.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with topics `["burn", from: Address], data = amount:
-    /// i128`
-    fn burn(env: Env, from: Address, amount: i128);
-
-    /// Burn `amount` from `from`, consuming the allowance of `spender`.
-    ///
-    /// Reduces from's balance by the amount, without transferring the balance
-    /// to another holder's balance.
-    ///
-    /// The spender will be allowed to burn the amount from from's balance, if
-    /// the amount is less than or equal to the allowance that the spender has
-    /// on the from's balance. The spender's allowance on from's balance will be
-    /// reduced by the amount.
-    ///
-    /// # Arguments
-    ///
-    /// * `spender` - The address authorizing the burn, and having its allowance
-    ///   consumed during the burn.
-    /// * `from` - The address holding the balance of tokens which will be
-    ///   burned from.
-    /// * `amount` - The amount of tokens to be burned.
-    ///
-    /// # Events
-    ///
-    /// Emits an event with topics `["burn", from: Address], data = amount:
-    /// i128`
-    fn burn_from(env: Env, spender: Address, from: Address, amount: i128);
-
-    /// Returns the number of decimals used to represent amounts of this token.
-    ///
-    /// # Panics
-    ///
-    /// If the contract has not yet been initialized.
-    fn decimals(env: Env) -> u32;
-
-    /// Returns the name for this token.
-    ///
-    /// # Panics
-    ///
-    /// If the contract has not yet been initialized.
-    fn name(env: Env) -> String;
-
-    /// Returns the symbol for this token.
-    ///
-    /// # Panics
-    ///
-    /// If the contract has not yet been initialized.
-    fn symbol(env: Env) -> String;
-}
-```
-
-:::caution[CAUTION CUANDO MODIFIQUES LOS ALLOWANCES]
-
-La función `approve` sobrescribe el valor anterior con `amount`, por lo que es posible que la asignación anterior sea gastada en una transacción anterior antes de que `amount` sea escrito en una transacción posterior. El resultado de esto es que `spender` puede gastar más de lo previsto. Este problema puede evitarse estableciendo primero la asignación a 0, verificando que el spender no haya gastado ninguna parte de la asignación anterior, y luego estableciendo la asignación al nuevo monto deseado. Puedes leer más sobre este problema aquí - https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729.
-
-:::
-
-### Metadatos
-
-Otro requisito para cumplir con la interfaz de token es escribir los metadatos estándar (`decimal`, `name`, y `symbol`) para el token en un formato específico. Este formato permite a los usuarios leer datos constantes directamente del ledger en lugar de invocar una función de Wasm. El [ejemplo de token](https://github.com/stellar/soroban-examples/blob/main/token/src/metadata.rs) demuestra cómo usar el Rust [soroban-token-sdk](https://github.com/stellar/rs-soroban-sdk/blob/main/soroban-token-sdk/src/lib.rs) para escribir los metadatos, y alentamos encarecidamente a las implementaciones de tokens a seguir este enfoque.
-
-### Manejo de Condiciones de Fallo
-
-En la interfaz de token, hay varias instancias donde las llamadas a funciones pueden fallar por varias razones, como la falta de autorización adecuada, asignación insuficiente o balance, etc. Para manejar estas condiciones de fallo, es importante especificar el comportamiento esperado cuando surgen tales situaciones.
-
-Es importante notar que la interfaz de token no solo incorpora el concepto de autorización para igualar la autorización de activos en Stellar Classic, sino que también utiliza el mecanismo de autorización de Soroban. Así que, si intentas hacer una llamada de token y falla, podría deberse a alguno de los procesos de autorización de token.
-
-Para proporcionar más contexto, cuando usas la interfaz de token, hay una función llamada `authorized` que devuelve "true" si una dirección tiene autorización de token.
-
-Se pueden encontrar más detalles sobre la Autorización [aquí](../learn/fundamentals/contract-development/authorization.mdx).
-
-Para las funciones en la interfaz de token, se debe utilizar [trapping](https://doc.rust-lang.org/book/ch09-00-error-handling.html) como la forma estándar de manejar condiciones de fallo, ya que la interfaz no está diseñada para devolver códigos de error. Esto significa que cuando una función encuentra un error, se detendrá la ejecución y se revertirán cualquier cambio de estado que ocurriera durante la llamada a la función.
-
-### Condiciones de Fallo
-
-Aquí hay una lista de condiciones de fallo básicas y su comportamiento esperado para funciones en la interfaz de token:
-
-#### Funciones de administrador:
-
-- Si el administrador no autorizó la llamada, la función debería interrumpirse.
-- Si el administrador intenta realizar una acción no válida (por ejemplo, acuñar una cantidad negativa), la función debería interrumpirse.
-
-#### Funciones de token:
-
-- Si el llamador no está autorizado para realizar la acción (por ejemplo, transferir tokens sin la autorización adecuada), la función debería interrumpirse.
-- Si la acción resultaría en un estado no válido (por ejemplo, transferir más tokens que los disponibles en el balance o asignación), la función debería interrumpirse.
-
-### Ejemplo: Manejo de Asignación Insuficiente en la función `burn_from`
-
-En la función `burn_from`, el contrato de token debería verificar si el spender tiene suficiente asignación para quemar la cantidad especificada de tokens de la dirección `from`. Si la asignación es insuficiente, la función debería interrumpirse, deteniendo la ejecución y revirtiendo cualquier cambio de estado.
-
-Aquí hay un ejemplo de cómo se puede modificar la función `burn_from` para manejar esta condición de fallo:
-
-```rust
-fn burn_from(
-    env: soroban_sdk::Env,
-    spender: Address,
-    from: Address,
-    amount: i128,
-) {
-    // Check if the spender has enough allowance
-    let current_allowance = allowance(env, from, spender);
-    if current_allowance < amount {
-        // Trap if the allowance is insufficient
-        panic!("Insufficient allowance");
-    }
-
-    // Proceed with burning tokens
-    // ...
-}
-```
-
-Al delinear claramente cómo manejar los fallos e incorporar las técnicas adecuadas de gestión de errores en la interfaz de token, podemos hacer que los contratos de token sean más robustos y seguros.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/README.mdx
deleted file mode 100644
index 6679ecbb65..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/README.mdx
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "Herramientas de Desarrollo de Blockchain: SDKs, APIs y Utilidades para Construir"
-sidebar_position: 0
-sidebar_label: Descripción general de herramientas
-description: Explora herramientas para construir, probar y desplegar aplicaciones de blockchain. Accede a SDKs, APIs y utilidades para optimizar el desarrollo en la red Stellar.
----
-
-# Resumen de Herramientas
-
-Esta sección de la documentación proporcionará enlaces a los SDK y herramientas para desarrolladores para su uso al desarrollar en Stellar, así como documentación para varias plataformas mantenidas por SDF, como la Anchor Platform y la Stellar Disbursement Platform (SDP).
-
-## Herramientas para Desarrolladores
-
-### [SDKs](./sdks/README.mdx)
-
-Los Kits de Desarrollo de Software (SDK) de Stellar proporcionan a los desarrolladores las herramientas, bibliotecas y documentación para interactuar y desarrollar en la blockchain. Simplifican tareas como crear y desplegar contratos inteligentes y enviar transacciones, además de ofrecer APIs para acceder a datos e integrar funcionalidades en aplicaciones.
-
-### [Stellar CLI](./cli/README.mdx)
-
-La interfaz de línea de comandos para contratos inteligentes de Soroban. Te permite crear, desplegar e interactuar con contratos inteligentes; configurar identidades; generar pares de claves; gestionar redes; y más.
-
-### [Laboratorio](./lab/README.mdx)
-
-Stellar Lab es nuestra nueva herramienta de referencia para el desarrollo, experimentación y pruebas, así como para explorar APIs que los desarrolladores utilizan para interactuar con la red Stellar.
-
-### [Inicio Rápido](./quickstart/README.mdx)
-
-Inicio rápido es un entorno de red Stellar local (nodo) que permite a los desarrolladores ejecutar una versión local de la red Stellar para el desarrollo y pruebas.
-
-### [Contratos OpenZeppelin](./openzeppelin-contracts.mdx)
-
-OpenZeppelin Stellar Contracts es una colección de contratos auditados y utilidades para Stellar. Los contratos son desarrollados por OpenZeppelin en colaboración con la comunidad Stellar y la Stellar Development Foundation (SDF), con el objetivo de ofrecer una biblioteca de contratos de alta calidad y auditados que puedan usarse para construir aplicaciones en la red Stellar.
-
-### [Scaffold Stellar](./scaffold-stellar.mdx)
-
-Scaffold Stellar es un kit de herramientas para desarrolladores para construir aplicaciones descentralizadas (dApps) y contratos inteligentes en Stellar. Proporciona herramientas CLI, plantillas de contratos reutilizables, un registro de contratos inteligentes y un frontend moderno.
-
-### [Más Herramientas para Desarrolladores](./developer-tools/README.mdx)
-
-Encuentra otras herramientas para desarrolladores mantenidas por SDF y el ecosistema que ayudan a agilizar el proceso de desarrollo para aplicaciones y contratos inteligentes en Stellar.
-
-## Plataformas de SDF
-
-### [Plataforma Anchor](../platforms/anchor-platform/README.mdx)
-
-La Anchor Platform es un conjunto de herramientas y APIs que permiten a los desarrolladores y empresas crear sus propios servicios de acceso y salida para la red Stellar. Proporciona una interfaz estandarizada, incluyendo la implementación de varias Propuestas del Ecosistema Stellar (SEPs), para facilitar a las empresas la integración con billeteras y exchanges basados en Stellar.
-
-### [Stellar Disbursement Platform (SDP)](../platforms/stellar-disbursement-platform/README.mdx)
-
-La Stellar Disbursement Platform (SDP) es una herramienta desarrollada para que las organizaciones realicen pagos masivos a un grupo de beneficiarios a través de la red Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/README.mdx
deleted file mode 100644
index 9ed18129a6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/README.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Stellar CLI
-description: La CLI para interactuar con la red Stellar
-sidebar_position: 20
----
-
-# Stellar CLI
-
-La interfaz de línea de comandos para contratos inteligentes Soroban. Te permite crear, implementar e interactuar con contratos inteligentes; configurar identidades; generar pares de claves; gestionar redes; y más.
-
-Instala Stellar CLI como se explica en [Configuración](../../build/smart-contracts/getting-started/setup.mdx#install-the-stellar-cli). Para ejemplos sobre cómo usar la Stellar CLI, por favor consulta [Guías de Stellar CLI](./cookbook/README.mdx).
-
-La documentación completa de referencia generada automáticamente está disponible [aquí](stellar-cli.mdx).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/README.mdx
deleted file mode 100644
index 19afbd03fd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Libro de recetas de cocina
-hide_table_of_contents: true
-sidebar_class_name: sidebar-category-items-hidden
-sidebar_position: 150
----
-
-import DocCardList from "@theme/DocCardList";
-
-Guías que te ayudarán a usar el CLI de Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/_category_.json
deleted file mode 100644
index d0ae8bacd4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsible": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/asset-management.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/asset-management.mdx
deleted file mode 100644
index b37f652284..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/asset-management.mdx
+++ /dev/null
@@ -1,291 +0,0 @@
----
-title: Gestión de activos
-hide_table_of_contents: false
-description: Emitir un activo Stellar, desplegar su contrato y acuñar, quemar, congelar y recuperar.
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/asset-management.mdx
----
-
-El [stellar-cli] se puede usar para emitir y administrar activos en la red Stellar.
-
-Esta guía asume que el [stellar-cli] ha sido configurado para usar testnet o una red local de prueba. Para usar testnet, ejecuta el siguiente comando.
-
-```bash
-stellar network use testnet
-```
-
-### Emisión de activos
-
-Para crear un activo Stellar usando el [stellar-cli], se realizan varios pasos:
-
-- Debe existir una cuenta emisora.
-- Se debe seleccionar un código de activo.
-- Opcionalmente, se configura un administrador.
-
-#### Creación del emisor
-
-Para crear un emisor, genera una clave y fóndala. El financiamiento usa friendbot, el grifo de testnet, y solo está disponible en testnet.
-
-```bash
-stellar keys generate issuer
-```
-
-```bash
-stellar keys fund issuer
-```
-
-Visualiza la clave pública con:
-
-```bash
-stellar keys public-key issuer
-```
-
-Configura la clave del emisor para firmar transacciones:
-
-```bash
-stellar keys use issuer
-```
-
-#### Configuración del emisor
-
-Las cuentas emisoras tienen varias flags de configuración que se pueden activar y afectan a todos los activos emitidos por el emisor.
-
-En esta guía, la cuenta emisora se configurará con las funciones revocables y de clawback habilitadas. Estas funciones permiten al administrador del activo revocar la autorización para usar un activo, lo que tiene el efecto de congelar el saldo, y realizar clawback, lo que equivale a quemar forzosamente el activo.
-
-```bash
-stellar tx new set-options \
-  --set-revocable \
-  --set-clawback-enabled
-```
-
-Para otras opciones, consulta el manual del comando [stellar tx new set-options].
-
-Para ver la transacción antes de enviarla, usa la opción `--build-only` y pasa la transacción por el comando tx edit:
-
-```bash cookbooktest.ignore="because piping isn't supported"
-stellar tx new set-options \
-  --set-revocable \
-  --set-clawback-enabled \
-  --build-only \
-  | stellar tx edit \
-  | stellar sign \
-  | stellar send
-```
-
-#### Elección del código de activo
-
-Elige un código de activo de entre 1 y 12 caracteres.
-
-El código del activo junto con la dirección de la cuenta emisora identificarán de forma única el activo. Un emisor puede emitir múltiples activos, cada uno distinguido por su código de activo.
-
-Para el resto de esta guía se usará el código de activo `ABC`.
-
-#### Configuración del contrato de activo
-
-En la red existe un contrato incorporado para cada activo. Su dirección está reservada y puede ser calculada usando el siguiente comando.
-
-```bash
-stellar contract asset id --asset ABC:issuer
-```
-
-El contrato no se despliega automáticamente. Cualquiera puede desplegar el contrato, no es una acción que requiera autorización.
-
-##### Despliegue del contrato
-
-Despliega el contrato de activo incorporado.
-
-La opción `--asset` especifica el nombre del activo, que tiene el formato `<asset-code>:<asset-issuer>`.
-
-La opción `--alias` almacena localmente un alias que se puede usar en comandos posteriores para referenciar la dirección del contrato.
-
-```bash
-stellar contract asset deploy --asset ABC:issuer --alias mycontract
-```
-
-Ejecuta el siguiente comando para obtener algunos datos de solo lectura del contrato y confirmar que está desplegado.
-
-```bash
-stellar contract invoke --id mycontract -- name
-```
-
-##### Configuración del administrador
-
-En este punto, el emisor es el administrador del contrato. Vamos a crear otra cuenta que será el administrador.
-
-```bash
-stellar keys generate admin
-```
-
-```bash
-stellar keys public-key admin
-```
-
-```bash
-stellar keys fund admin
-```
-
-Usando la cuenta emisora, invoca la función `set_admin` del contrato de activo.
-
-```bash
-stellar keys use issuer
-```
-
-```bash
-stellar contract invoke --source issuer --id mycontract -- set_admin --new_admin admin
-```
-
-### Acciones
-
-Una vez que el contrato de activo está desplegado y configurado, se pueden realizar las siguientes acciones.
-
-#### Acuñar (Solo administrador)
-
-Genera y fondea una cuenta de usuario a la que se transferirá el activo acuñado.
-
-```bash
-stellar keys generate user
-```
-
-```bash
-stellar keys fund user
-```
-
-```bash
-stellar keys public-key user
-```
-
-Usando la cuenta de usuario, confía en el activo para que la cuenta pueda mantenerlo.
-
-```bash
-stellar keys use user
-```
-
-```bash
-stellar tx new change-trust --line ABC:issuer
-```
-
-Para acuñar el activo al usuario, usa la cuenta de administrador, invocando la función `mint` del contrato de activo.
-
-```bash
-stellar keys use admin
-```
-
-```bash
-stellar contract invoke --id mycontract -- mint --to user --amount 25
-```
-
-Consulta el saldo después de acuñar.
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user
-```
-
-#### Transferir
-
-Genera y fondea una segunda cuenta de usuario a la que la cuenta de usuario del paso anterior pueda transferir el activo.
-
-```bash
-stellar keys generate user2
-```
-
-```bash
-stellar keys fund user2
-```
-
-```bash
-stellar keys public-key user2
-```
-
-Usando la cuenta user2, confía en el activo para que la nueva cuenta pueda mantenerlo.
-
-```bash
-stellar keys use user2
-```
-
-```bash
-stellar tx new change-trust --line ABC:issuer
-```
-
-Usando la cuenta de usuario, invoca la función `transfer` del contrato de activo.
-
-```bash
-stellar keys use user
-```
-
-```bash
-stellar contract invoke --id mycontract -- transfer --from user --to user2 --amount 3
-```
-
-Consulta los saldos después de la transferencia.
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user
-```
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user2
-```
-
-#### Quemar
-
-Usando la cuenta de usuario, invoca la función `burn` del contrato de activo.
-
-```bash
-stellar keys use user
-```
-
-```bash
-stellar contract invoke --id mycontract -- burn --from user --amount 5
-```
-
-Consulta el saldo después de quemar.
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user
-```
-
-#### Revocar autorización / Congelar (Solo administrador)
-
-Un administrador puede revocar la autorización de un usuario para usar el activo. El usuario seguirá manteniendo el saldo pero no podrá transferirlo ni crear nuevos pagos. Cualquier responsabilidad existente, como las creadas por ofertas en Stellar, seguirá existiendo y podría ejecutarse.
-
-Usando la cuenta de administrador, invoca la función `set_authorized` del contrato de activo.
-
-```bash
-stellar keys use admin
-```
-
-```bash
-stellar contract invoke --id mycontract -- set_authorized --id user --authorize false
-```
-
-Usando la cuenta de usuario, invoca la función `transfer` del contrato de activo. La invocación fallará porque ya no están autorizados para transferir.
-
-```bash
-stellar keys use user
-```
-
-```bash cookbooktest.fail cookbooktest.stderr="balance is deauthorized"
-stellar contract invoke --id mycontract -- transfer --from user --to user2 --amount 3
-```
-
-#### Clawback (Solo administrador)
-
-Un administrador puede recuperar el saldo de un usuario. La cantidad recuperada será quemada.
-
-Usando la cuenta de administrador, invoca la función `clawback` del contrato de activo.
-
-```bash
-stellar keys use admin
-```
-
-```bash
-stellar contract invoke --id mycontract -- clawback --from user --amount 1
-```
-
-Consulta el saldo después del clawback.
-
-```bash
-stellar contract invoke --id mycontract -- balance --id user
-```
-
-[stellar-cli]: ../stellar-cli.mdx
-[stellar tx new set-options]: ../stellar-cli.mdx#stellar-tx-new-set-options
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/contract-build-meta.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/contract-build-meta.mdx
deleted file mode 100644
index 44dee01c07..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/contract-build-meta.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Agregar metadatos al contrato WASM durante la compilación
-hide_table_of_contents: true
-description: Incluir metadatos en el código byte del contrato WASM durante la compilación
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/contract-build-meta.mdx
----
-
-Para construir un contrato inteligente, usa el comando `stellar contract build`. La opción `--meta` te permitirá agregar entradas de metadatos adicionales a la sección personalizada `contractmetav0` del archivo WASM resultante en el momento de la construcción.
-
-```bash cookbooktest.ignore
-export SHA=$(git rev-parse HEAD)
-```
-
-```bash
-stellar contract build \
-    --manifest-path ./cmd/crates/soroban-test/tests/fixtures/test-wasms/hello_world/Cargo.toml \
-    --meta source_repo=https://github.com/stellar/stellar-cli \
-    --meta commit_sha=$SHA
-```
-
-Luego puedes usar `stellar contract info meta` para ver los metadatos:
-
-```bash
-stellar contract info meta \
-  --wasm target/wasm32v1-none/release/test_hello_world.wasm
-```
-
-```bash cookbooktest.ignore
-Contract meta:
- • rsver: 1.91.0 (Rust version)
- • rssdkver: 23.0.1#510d3feb724c2b01d7e7ab7652f03b9f8efc3f35 (Soroban SDK version and its commit hash)
- • cliver: 23.1.4#v20.0.0-646-g70895dd66fb7dbf2f4c2a81cf38546512ba4198e-dirty
- • source_repo: https://github.com/stellar/stellar-cli
- • commit_sha: c6f881689d3f4936cb3262089eb70142e9ca9c91
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/contract-lifecycle.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/contract-lifecycle.mdx
deleted file mode 100644
index b57cb401ee..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/contract-lifecycle.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Ciclo de vida del contrato
-hide_table_of_contents: true
-description: Gestiona el ciclo de vida de un contrato inteligente Stellar usando la CLI
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/contract-lifecycle.mdx
----
-
-Para gestionar el ciclo de vida de un contrato inteligente Stellar usando la CLI, sigue estos pasos:
-
-1. Configura tu red preferida. Para esta guía, usaremos `testnet`. Una lista de redes disponibles se puede encontrar [aquí](../../../networks/README.mdx)
-
-```bash
-stellar network use testnet
-```
-
-2. Crea una identidad para Alice:
-
-```bash
-stellar keys generate alice -q
-```
-
-3. Fondea la identidad:
-
-```bash
-stellar keys fund alice
-```
-
-4. Despliega un contrato:
-
-```bash
-stellar keys use alice
-```
-
-```bash
-stellar contract deploy --wasm /path/to/contract.wasm --alias mycontract
-```
-
-Esto mostrará el ID del contrato resultante, por ejemplo:
-
-```
-CBB65ZLBQBZL5IYHDHEEPCVUUMFOQUZSQKAJFV36R7TZETCLWGFTRLOQ
-```
-
-Para aprender más sobre cómo desarrollar archivos de contrato `.wasm`, consulta nuestro [tutorial para comenzar](../../../build/smart-contracts/getting-started/setup.mdx).
-
-5. Invoca una función del contrato:
-
-```bash
-stellar contract invoke --id mycontract -- <FUNCTION>
-```
-
-6. Consulta el estado del contrato:
-
-```bash
-stellar contract read --id mycontract --durability <DURABILITY> --key <KEY>
-```
-
-Nota: `<DURABILITY>` es `persistent` o `temporary`. `KEY` proporciona la clave de la entrada de almacenamiento que se está leyendo.
-
-7. Gestiona los estados expirados:
-
-```bash
-stellar contract extend --id mycontract --ledgers-to-extend 1000 --durability <DURABILITY> --key <KEY>
-```
-
-Esto extiende el estado de la instancia provista por la clave dada al menos 1000 libros contables desde el libro contable actual.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/deploy-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/deploy-contract.mdx
deleted file mode 100644
index 7c5988c3d4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/deploy-contract.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Desplegar un contrato desde bytecode Wasm cargado
-hide_table_of_contents: true
-description: Desplegar una instancia de un contrato compilado que ya se ha cargado en la red
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/deploy-contract.mdx
----
-
-Para desplegar una instancia de un contrato inteligente compilado que ya ha sido cargado en la red Stellar, usa el comando `stellar contract deploy`:
-
-```bash
-stellar contract deploy \
-    --source S... \
-    --network testnet \
-    --wasm-hash <hex-encoded-wasm-hash> \
-    --alias <alias>
-```
-
-:::tip
-
-Opcionalmente, asigna un alias reemplazando `<alias>` con el nombre de alias que desees para el contrato. El alias es una asignación almacenada localmente a la dirección del contrato, y puede usarse en otros comandos de stellar-cli en lugar de la dirección.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/deploy-stellar-asset-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/deploy-stellar-asset-contract.mdx
deleted file mode 100644
index 5c7628f19b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/deploy-stellar-asset-contract.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Implementar el Contrato de Activos Stellar para un activo Stellar
-hide_table_of_contents: true
-description: Implementa un SAC para un activo Stellar para que pueda interactuar con contratos inteligentes
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/deploy-stellar-asset-contract.mdx
----
-
-El CLI de Stellar puede implementar un [Stellar Asset Contract] para un activo Stellar de modo que cualquier contrato inteligente de Stellar pueda interactuar con el activo.
-
-Cada activo Stellar tiene reservado un contrato que cualquiera puede implementar. Una vez implementado, cualquier contrato puede interactuar con ese activo manteniendo un saldo del activo, recibiendo el activo o enviando el activo.
-
-Implementar el Contrato de Activos Stellar para un activo Stellar habilita ese activo para su uso en contratos inteligentes.
-
-El Contrato de Activos Stellar puede implementarse para cualquier posible activo Stellar, ya sean activos que ya se usan en Stellar o activos que nunca han tenido actividad. Esto significa que no es necesario que el emisor haya sido creado, ni que nadie esté aún en posesión del activo en Stellar.
-
-Para realizar la implementación, usa el siguiente comando:
-
-```bash cookbooktest.ignore
-stellar contract asset deploy \
-    --source S... \
-    --network testnet \
-    --asset USDC:GCYEIQEWOCTTSA72VPZ6LYIZIK4W4KNGJR72UADIXUXG45VDFRVCQTYE
-```
-
-El argumento `asset` corresponde al símbolo y a la dirección del emisor, que es como se identifican los activos en Stellar.
-
-Lo mismo puede hacerse para el activo nativo [Lumens]:
-
-```bash cookbooktest.fail cookbooktest.stderr="contract already exists"
-stellar contract asset deploy \
-    --source S... \
-    --network testnet \
-    --asset native
-```
-
-:::note
-
-Implementar el activo nativo fallará en testnet o mainnet porque ya existe un Stellar Asset Contract.
-
-:::
-
-Para cualquier activo, la dirección del contrato se puede obtener con:
-
-```bash
-stellar contract id asset \
-    --network testnet \
-    --asset native
-```
-
-[stellar asset contract]: ../../../tokens/stellar-asset-contract.mdx
-[lumens]: ../../../learn/fundamentals/lumens.mdx
-[sep-41]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md
-[`soroban_sdk::token`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/
-[`token::tokenclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.TokenClient.html
-[`token::stellarassetclient`]: https://docs.rs/soroban-sdk/latest/soroban_sdk/token/struct.StellarAssetClient.html
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-instance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-instance.mdx
deleted file mode 100644
index ea33a0220c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-instance.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Extender el TTL de una instancia de contrato desplegada
-hide_table_of_contents: true
-description: Usa la CLI para extender el tiempo de vida (TTL) de una instancia de contrato
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-instance.mdx
----
-
-Puedes usar la CLI de Stellar para extender el TTL de una instancia de contrato como sigue:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-Este ejemplo usa 535,679 libros contables como el nuevo TTL para archivo. Este es el valor máximo permitido para este argumento en la CLI. Esto corresponde aproximadamente a 30 días (calculando un promedio de 5 segundos por cierre de libro contable).
-
-Cuando extiendes una instancia de contrato, esto incluye:
-
-- la propia instancia del contrato
-- cualquier entrada `env.storage().instance()` dentro del contrato
-- el código Wasm del contrato
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-storage.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-storage.mdx
deleted file mode 100644
index a53fd18e8e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-storage.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Extender el TTL de la entrada de almacenamiento de un contrato desplegado
-hide_table_of_contents: true
-description: Usa el CLI para extender el tiempo de vida (TTL) de la entrada de almacenamiento persistente de un contrato
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-storage.mdx
----
-
-Puedes usar el CLI de Stellar para extender el TTL de la entrada de almacenamiento persistente de un contrato. Para una entrada de almacenamiento que usa un `Symbol` simple como clave de almacenamiento, puedes ejecutar un comando así:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --key COUNTER \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-Este ejemplo usa 535,679 libros contables como el nuevo TTL de archivo. Este es el valor máximo permitido para este argumento en el CLI. Esto corresponde aproximadamente a 30 días (promediando tiempos de cierre de libro contable de 5 segundos).
-
-Si tu entrada de almacenamiento usa una clave más avanzada, como `Balance(Address)` en un contrato de token, necesitarás proporcionar la clave en forma XDR codificada en base64:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --key-xdr AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAA4AAAAHQmFsYW5jZQAAAAAB \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-:::info
-
-Asegúrate de consultar nuestra [guía sobre cómo crear claves XDR para el libro contable](../../../build/guides/rpc/generate-ledger-keys-python.mdx) para obtener ayuda generándolas.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-wasm.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-wasm.mdx
deleted file mode 100644
index 91ca09d8dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/extend-contract-wasm.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Extender el TTL del código Wasm de un contrato desplegado
-hide_table_of_contents: true
-description: Usar Stellar CLI para extender el TTL del bytecode Wasm de un contrato, con o sin el binario local
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-wasm.mdx
----
-
-Puedes usar Stellar CLI para extender el TTL del bytecode Wasm de un contrato. Esto se puede hacer de dos formas: si tienes o no el contrato compilado localmente. Si tienes el binario compilado en tu máquina local:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --wasm ../relative/path/to/soroban_contract.wasm \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-Este ejemplo usa 535,679 ledgers como el nuevo TTL de archivo. Este es el valor máximo permitido para este argumento en la CLI. Esto corresponde aproximadamente a 30 días (con un promedio de cierre de ledger de 5 segundos).
-
-Si no tienes el binario compilado en tu máquina local, aún puedes usar la CLI para extender el TTL del bytecode. Necesitarás conocer el hash Wasm del código de contrato instalado:
-
-```bash
-stellar contract extend \
-    --source S... \
-    --network testnet \
-    --wasm-hash <hex-encoded-wasm-hash> \
-    --ledgers-to-extend 535679 \
-    --durability persistent
-```
-
-:::info
-
-Puedes aprender más sobre cómo encontrar el hash Wasm correcto para una instancia de contrato [aquí (JavaScript)](../../../build/guides/rpc/retrieve-contract-code-js.mdx) y [aquí (Python)](../../../build/guides/rpc/retrieve-contract-code-python.mdx).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/install-deploy.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/install-deploy.mdx
deleted file mode 100644
index 6f68e34d7a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/install-deploy.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Instalar y desplegar un contrato inteligente
-hide_table_of_contents: true
-description: Combina los comandos instalar y desplegar en la CLI de Stellar para realizar ambas tareas
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/install-deploy.mdx
----
-
-Puedes combinar los comandos `install` y `deploy` de la CLI de Stellar para cumplir con ambas tareas:
-
-```bash
-stellar contract deploy \
-    --source S... \
-    --network testnet \
-    --wasm ../relative/path/to/soroban_contract.wasm
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/install-wasm.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/install-wasm.mdx
deleted file mode 100644
index 045658f5dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/install-wasm.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Subir bytecode Wasm
-hide_table_of_contents: true
-description: Usa el CLI de Stellar para subir un contrato inteligente compilado en el ledger
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/install-wasm.mdx
----
-
-Para usar el CLI de Stellar y subir un contrato inteligente compilado en el ledger, usa el comando `stellar contract upload`:
-
-```bash
-stellar contract upload \
-    --source S... \
-    --network testnet \
-    --wasm ../relative/path/to/soroban_contract.wasm
-```
-
-:::note
-
-Ten en cuenta que este comando devolverá el ID hash del bytecode Wasm, en lugar de una dirección para una instancia del contrato.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/payments-and-assets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/payments-and-assets.mdx
deleted file mode 100644
index 3e654414bb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/payments-and-assets.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Pagos y activos
-hide_table_of_contents: true
-description: Envía XLM, stellar classic o un activo soroban usando la CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/payments-and-assets.mdx
----
-
-Para enviar pagos y trabajar con activos usando la CLI de Stellar, sigue estos pasos:
-
-1. Configura tu red preferida. Para esta guía, usaremos `testnet`. Una lista de redes disponibles puede encontrarse [aquí](../../../networks/README.mdx)
-
-```bash
-stellar network use testnet
-```
-
-2. Financia las cuentas:
-
-```bash
-stellar keys generate alice
-```
-
-```bash
-stellar keys fund alice
-```
-
-```bash
-stellar keys generate bob
-```
-
-```bash
-stellar keys fund bob
-```
-
-3. Obtén el ID del contrato del activo stellar:
-
-```bash
-stellar contract id asset --asset native
-```
-
-4. Obtén la clave pública de Bob:
-
-```bash
-stellar keys address bob
-```
-
-5. Envía 100 XLM de Alice a Bob:
-
-```bash
-stellar keys use alice
-```
-
-```bash
-stellar contract invoke --id <ASSET_CONTRACT_ID> -- transfer --to bob --from alice --amount 100
-```
-
-6. Consulta el saldo de la cuenta:
-
-```bash
-stellar contract invoke --id <ASSET_CONTRACT_ID> -- balance --id bob
-```
-
-Para más información sobre las funciones disponibles para el contrato de activo Stellar, consulta el [código de la interfaz de token](../../../tokens/token-interface.mdx#code)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/restore-contract-instance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/restore-contract-instance.mdx
deleted file mode 100644
index 9cb74f1213..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/restore-contract-instance.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Restaurar un contrato archivado usando la CLI de Stellar
-hide_table_of_contents: true
-description: Restaurar una instancia de contrato archivada usando la CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/restore-contract-instance.mdx
----
-
-Si la instancia de tu contrato ha sido archivada, puedes restaurarla fácilmente usando la CLI de Stellar.
-
-```bash
-stellar contract restore \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --durability persistent
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/restore-contract-storage.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/restore-contract-storage.mdx
deleted file mode 100644
index a1198208fc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/restore-contract-storage.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Restaurar datos de contratos archivados usando la CLI de Stellar
-hide_table_of_contents: true
-description: Restaurar entradas de almacenamiento de contratos archivados usando la CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/restore-contract-storage.mdx
----
-
-Si la entrada de almacenamiento persistente de un contrato ha sido archivada, puedes restaurarla usando la CLI de Stellar. Para una entrada de almacenamiento que use un `Symbol` simple como clave de almacenamiento, puedes ejecutar un comando así:
-
-```bash
-stellar contract restore \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --key COUNTER \
-    --durability persistent
-```
-
-Si tu entrada de almacenamiento usa una clave de almacenamiento más avanzada, como `Balance(Address)` en un contrato de token, necesitarás proporcionar la clave en forma XDR codificada en base64:
-
-```bash
-stellar contract restore \
-    --source S... \
-    --network testnet \
-    --id C... \
-    --key-xdr AAAABgAAAAHXkotywnA8z+r365/0701QSlWouXn8m0UOoshCtNHOYQAAAA4AAAAHQmFsYW5jZQAAAAAB \
-    --durability persistent
-```
-
-:::info
-
-Asegúrate de revisar nuestra [guía para crear claves de libro mayor XDR](../../../build/guides/rpc/generate-ledger-keys-python.mdx) para obtener ayuda generando las claves.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/stellar-keys.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/stellar-keys.mdx
deleted file mode 100644
index 3535e765d5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/stellar-keys.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-title: Claves Stellar
-hide_table_of_contents: true
-description: Administrar claves Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/stellar-keys.mdx
----
-
-Esta guía te muestra cómo generar, inspeccionar y eliminar una identidad Stellar usando la CLI.
-
-### 1. Generar una Nueva Identidad
-
-Ejecuta el siguiente comando para crear un nuevo par de claves y guardarlo bajo el alias llamado `carol`:
-
-```bash
-stellar keys generate carol
-```
-
-Salida:
-
-```
-✅ Key saved with alias carol in ".config/soroban/identity/carol.toml"
-```
-
-La CLI guarda esta identidad en un archivo TOML.
-
-### 2. Verificar el Archivo de Identidad
-
-Navega al directorio de configuración y lista su contenido:
-
-```bash cookbooktest.ignore
-cd .config/soroban/identity && ls
-```
-
-Salida:
-
-```
-carol.toml
-```
-
-El archivo carol.toml contiene la frase Seed para tu identidad.
-
-### 3. Ver la Frase Seed
-
-```bash cookbooktest.ignore
-cat carol.toml
-```
-
-Salida:
-
-```
-seed_phrase = "patrol clean public grocery roof aim have valve cherry dismiss lunar tail duty license capable little version banana amount often cover dice couple party"
-```
-
-:::danger
-
-Nota: La frase Seed es información sensible. Trátala con cuidado y nunca la expongas públicamente.
-
-:::
-
-### 4. Derivar la Clave Secreta
-
-Para mostrar la clave secreta de la identidad carol:
-
-```bash
-stellar keys secret carol
-```
-
-Salida:
-
-```
-SCJP663VYFZPYN75H2DYJA3FYUBP5UR23HZ4ZDHDMDY6TXVYUYMWNKTI
-```
-
-:::danger
-
-Nota: La clave secreta es información sensible. Trátala con cuidado y nunca la expongas públicamente.
-
-:::
-
-### 5. Derivar la Clave Pública
-
-Para mostrar la clave pública correspondiente a la identidad carol:
-
-```bash
-stellar keys public-key carol
-```
-
-Salida:
-
-```
-GD3BFFX7DTNJAGDVVM5RYGGQQNURZTH4VSBLWF55YXY3L6T2WWZK57EI
-```
-
-Esta es la dirección pública de tu clave.
-
-### 6. Fondéa esta cuenta
-
-```bash
-stellar keys fund carol
-```
-
-Salida:
-
-```
-✅ Account carol funded on "Test SDF Network ; September 2015"
-```
-
-También puedes fondear la cuenta mientras creas la clave usando `stellar keys generate --fund`.
-
-### 7. Eliminar la Identidad
-
-Cuando ya no necesites esta identidad, elimínala usando:
-
-```bash
-stellar keys rm carol
-```
-
-Salida:
-
-```
-ℹ️  Removing the key's cli config file
-```
-
-En este punto, el archivo de identidad carol.toml se elimina y el alias ya no está disponible en la CLI.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-new-create-claimable-balance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-new-create-claimable-balance.mdx
deleted file mode 100644
index d7113ca6e3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-new-create-claimable-balance.mdx
+++ /dev/null
@@ -1,248 +0,0 @@
----
-title: Crear saldo reclamable
-hide_table_of_contents: true
-description: Crear saldos reclamables con varias condiciones de reclamación usando el CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-new-create-claimable-balance.mdx
----
-
-Los saldos reclamables te permiten enviar pagos que el destinatario puede reclamar según condiciones específicas. Esto es útil para funcionalidades tipo escrow, pagos condicionales o transferencias con bloqueo temporal.
-
-## Configuración
-
-Para los siguientes ejemplos usaremos estas cuentas:
-
-```bash
-stellar network use testnet
-```
-
-```bash
-stellar keys generate --fund alice
-```
-
-```bash
-stellar keys generate bob --fund
-```
-
-```bash
-stellar keys generate charlie --fund
-```
-
-## Ejemplos básicos
-
-### Saldo reclamable incondicional
-
-Crear un saldo reclamable que el destinatario pueda reclamar inmediatamente:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 50_000_000 \
-  --asset native \
-  --claimant bob
-```
-
-También puedes especificar explícitamente incondicional:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 50_000_000 \
-  --asset native \
-  --claimant 'bob:"unconditional"'
-```
-
-### Múltiples reclamantes
-
-Crear un saldo reclamable que pueda ser reclamado por cualquiera de varios destinatarios:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 75_000_000 \
-  --asset native \
-  --claimant bob \
-  --claimant charlie
-```
-
-## Predicados basados en tiempo
-
-### Antes de un tiempo absoluto
-
-Crear un saldo reclamable que debe reclamarse antes de una fecha específica:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 30_000_000 \
-  --asset native \
-  --claimant 'bob:{"before_absolute_time":"1735689599"}'
-```
-
-### Antes de un tiempo relativo
-
-Crear un saldo reclamable que debe reclamarse dentro de 1 hora (3600 segundos) desde la creación:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 25_000_000 \
-  --asset native \
-  --claimant 'bob:{"before_relative_time":"3600"}'
-```
-
-## Predicados lógicos
-
-### Predicado NOT
-
-Crear un saldo reclamable que pueda reclamarse después de cierto tiempo (NO antes del tiempo relativo):
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 40_000_000 \
-  --asset native \
-  --claimant 'bob:{"not":{"before_relative_time":"7200"}}'
-```
-
-Esto significa: "Puede reclamarse, PERO NO antes de que hayan pasado 2 horas" (efectivamente: puede reclamarse después de 2 horas).
-
-### Predicado AND
-
-Crear un saldo reclamable con múltiples condiciones que TODAS deben ser verdaderas:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 60_000_000 \
-  --asset native \
-  --claimant 'bob:{"and":[{"before_absolute_time":"1735689599"},{"not":{"before_relative_time":"86400"}}]}'
-```
-
-Esto significa: "Puede reclamarse antes del 31 de diciembre de 2024 Y después de que haya pasado 1 día".
-
-### Predicado OR
-
-Crear un saldo reclamable donde cualquiera de las condiciones pueda ser verdadera:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 35_000_000 \
-  --asset native \
-  --claimant 'bob:{"or":[{"before_relative_time":"3600"},{"not":{"before_absolute_time":"1717200000"}}]}'
-```
-
-Esto significa: "Puede reclamarse dentro de 1 hora O después del 1 de junio de 2024".
-
-## Ejemplos complejos
-
-### Reclamantes mixtos con diferentes predicados
-
-Crear un saldo reclamable con múltiples reclamantes que tienen distintas condiciones de reclamación:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 100_000_000 \
-  --asset native \
-  --claimant 'bob:{"before_relative_time":"3600"}' \
-  --claimant 'charlie:{"not":{"before_relative_time":"86400"}}'
-```
-
-Esto crea un saldo donde:
-
-- Bob puede reclamar dentro de 1 hora
-- Charlie puede reclamar después de que haya pasado 1 día
-
-### Pago tipo escrow
-
-Crear un escrow donde el destinatario tiene 30 días para reclamar, de lo contrario vuelve al remitente:
-
-```bash
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 200_000_000 \
-  --asset native \
-  --claimant 'bob:{"before_relative_time":"2592000"}' \
-  --claimant 'alice:{"not":{"before_relative_time":"2592000"}}'
-```
-
-Esto significa:
-
-- Bob puede reclamar dentro de 30 días
-- Alice puede reclamar de nuevo después de 30 días si Bob no ha reclamado
-
-### Saldo reclamable con activo personalizado
-
-Crear un saldo reclamable para un activo personalizado:
-
-```bash cookbooktest.ignore
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 1000_000_000 \
-  --asset USDC:GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
-  --claimant 'bob:{"before_absolute_time":"1735689599"}'
-```
-
-## Comprender los predicados
-
-**Nota**: Los predicados deben ser JSON válido, por lo que debes usar comillas y escape adecuados.
-
-### Tipos de predicados
-
-| Tipo                   | Descripción                                            | Ejemplo                                 |
-| ---------------------- | ------------------------------------------------------ | --------------------------------------- |
-| `unconditional`        | Puede reclamarse en cualquier momento                  | `"unconditional"`                       |
-| `before_absolute_time` | Debe reclamarse antes de un timestamp específico       | `{"before_absolute_time":"1735689599"}` |
-| `before_relative_time` | Debe reclamarse dentro de X segundos desde la creación | `{"before_relative_time":"3600"}`       |
-| `not`                  | Niega otro predicado                                   | `{"not":{...}}`                         |
-| `and`                  | Ambos predicados deben ser verdaderos                  | `{"and":[{...},{...}]}`                 |
-| `or`                   | Cualquiera de los predicados puede ser verdadero       | `{"or":[{...},{...}]}`                  |
-
-### Notas sobre el formato de tiempos
-
-- **Tiempos absolutos**: Usa timestamps Unix (segundos desde epoch)
-- **Tiempos relativos**: Segundos desde la creación del saldo reclamable
-- **Timestamps**: Deben estar en el futuro al crear el saldo
-
-## Casos de uso comunes
-
-### 1. Pago simple con fecha límite
-
-```bash
-# Bob has 7 days to claim
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 50_000_000 \
-  --claimant 'bob:{"before_relative_time":"604800"}'
-```
-
-### 2. Pago diferido
-
-```bash
-# Bob can only claim after 1 day
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 100_000_000 \
-  --claimant 'bob:{"not":{"before_relative_time":"86400"}}'
-```
-
-### 3. Fondo de emergencia
-
-```bash
-# Bob can claim immediately, but if he doesn't claim within 48 hours, Alice can reclaim
-stellar tx new create-claimable-balance \
-  --source alice \
-  --amount 500_000_000 \
-  --claimant 'bob:{"before_relative_time":"172800"}' \
-  --claimant 'alice:{"not":{"before_relative_time":"172800"}}'
-```
-
-## Notas
-
-- `--amount`: Cantidad en stroops (1 XLM = 10,000,000 stroops)
-- `--asset`: Usa "native" para XLM o formato "CODE:ISSUER" para otros activos
-- `--claimant`: Cuenta con predicado opcional (puede especificarse varias veces)
-- Los predicados se evalúan cuando se reclama el saldo, no cuando se crea
-- Los predicados `And` y `Or` deben tener exactamente 2 subpredicados
-- Los predicados complejos pueden anidarse para crear condiciones sofisticadas de reclamación
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-new.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-new.mdx
deleted file mode 100644
index da58a98c7d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-new.mdx
+++ /dev/null
@@ -1,189 +0,0 @@
----
-title: Comandos tx
-hide_table_of_contents: true
-description: Crear transacciones Stellar usando la CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-new.mdx
----
-
-Hasta ahora, los ejemplos de la CLI interactuando con la blockchain han sido mediante el comando `contract`. Subiendo contratos, desplegando contratos y ejecutándolos. Cada uno de estos son diferentes tipos de transacciones, que deben ser firmadas y enviadas a la red (y en el caso de transacciones relacionadas con contratos, simuladas primero).
-
-Técnicamente, estos tres son diferentes operaciones, de las cuales una transacción puede contener hasta 100 operaciones. Sin embargo, en el caso de operaciones relacionadas con contratos, una transacción está limitada a solo una.
-
-Entonces, para todas las demás transacciones, la CLI proporciona los subcomandos `tx`. Estos son:
-
-- `new`
-- `sign`
-- `send`
-- `simulate`
-
-## `tx new`
-
-Para los siguientes ejemplos usaremos las siguientes cuentas:
-
-```sh
-stellar keys generate --fund alice --network testnet
-stellar keys generate bob
-# You can add a public key to the keys
-stellar keys add --public-key GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI charlie
-## and use testnet
-stellar network use testnet
-```
-
-### Crear cuenta
-
-Crea y financia una nueva cuenta Stellar. Arriba, `alice` fue financiado por [friendbot](../../../networks/README.mdx#friendbot). Sin embargo, `bob` y `charlie` no fueron financiados. Por lo tanto, podemos usar el comando `create-account` para financiarlos.
-
-`bob` recibirá 10 XLM y `charlie` recibirá 1 XLM.
-
-```sh
-stellar tx new create-account \
-  --source alice \
-  --destination bob \
-  --starting-balance 100_000_000
-
-stellar tx new create-account \
-  --source alice \
-  --destination charlie \
-  --starting-balance 10_000_000
-```
-
-Notas:
-
-- `--starting-balance`: Saldo inicial en stroops para financiar la cuenta (1 XLM = 10,000,000 stroops)
-
-### Pago
-
-`bob` siente que `charlie` solo recibió 1 XLM, así que enviará 4 XLM más a `charlie`.
-
-```sh
-stellar tx new payment \
-  --source bob \
-  --destination charlie \
-  --asset native \
-  --amount 40_000_000
-```
-
-Notas:
-
-- `--asset`: El activo a enviar - "native" para XLM o en formato "CODE:ISSUER" para otros activos
-
-### Incrementar Secuencia
-
-Incrementa el número de secuencia de una cuenta:
-
-```sh
-stellar tx new bump-sequence \
-  --source alice \
-  --bump-to 123450
-```
-
-### Fusión de cuentas
-
-Fusiona una cuenta con otra, transfiriendo todos los XLM.
-
-`bob` decide seguir compartiendo su riqueza y fusiona su cuenta con la de `charlie`.
-
-```sh
-stellar tx new account-merge \
-  --source bob \
-  --account charlie
-```
-
-Notas:
-
-- `--source`: La cuenta a eliminar del libro mayor, por lo que esta es su transacción final
-
-### Configurar Flags de Trustline
-
-Modificar flags de autorización en una trustline:
-
-```sh
-stellar tx new set-trustline-flags \
-  --source alice \
-  --asset USDC:GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
-  --trustor charlie \
-  --set-authorize \
-  --set-authorize-to-maintain-liabilities \
-  --set-trustline-clawback-enabled
-```
-
-Argumentos:
-
-- `--source`: La cuenta emisora que establece los flags (debe ser el emisor del activo)
-- `--asset`: El activo en formato CODE:ISSUER
-- `--trustor`: La cuenta cuya trustline tendrá modificados los flags
-- `--set-authorize`: Activar autorización completa
-- `--set-authorize-to-maintain-liabilities`: Activar autorización limitada
-- `--set-trustline-clawback-enabled`: Activar clawback para esta trustline
-- `--clear-*`: Flags para eliminar cada configuración correspondiente
-
-### Configurar Opciones
-
-Configurar ajustes de cuenta:
-
-```sh
-stellar tx new set-options \
-  --source alice \
-  --inflation-dest GBUG7QTBTT47XVDVE6RZYWRUZBPLOIO57INE6LYZDMIXMMDCREQRUQKI \
-  --home-domain "example.com" \
-  --master-weight 100 \
-  --med-threshold 100 \
-  --low-threshold 100 \
-  --high-threshold 100 \
-  --signer GBXSGN5GX4PZOSBHB4JJF67CEGSGT7DGBGGUGWXI4WOQMQEA4SFV2HTJ \
-  --signer-weight 1 \
-  --set-required \
-  --set-revocable \
-  --set-clawback-enabled \
-  --set-immutable
-```
-
-Notas:
-
-- `--source`: Cuenta para modificar los ajustes
-- `--inflation-dest`: Establecer cuenta destino de inflación
-- `--home-domain`: Establecer dominio principal para federación/cumplimiento
-- `--master-weight`: Peso de la clave maestra de la cuenta (0-255)
-- `--low-threshold`: Umbral de peso para operaciones de baja seguridad
-- `--med-threshold`: Umbral de peso para operaciones de seguridad media
-- `--high-threshold`: Umbral de peso para operaciones de alta seguridad
-- `--signer`: Añadir una nueva clave pública firmante
-- `--signer-weight`: Peso para el nuevo firmante (0 elimina al firmante)
-- `--set-required`: Activar requisito de autorización para nuevas trustlines
-- `--set-revocable`: Activar revocación de trustlines
-- `--set-clawback-enabled`: Activar clawback para la cuenta emisora del activo
-- `--set-immutable`: Hacer ajustes de la cuenta inmutables
-- `--clear-*`: Flags para eliminar cada configuración correspondiente
-
-### Cambiar Trust
-
-Crear o modificar una trustline:
-
-```sh
-stellar tx new change-trust \
-  --source alice \
-  --line USDC:ISSUER \
-  --limit 100000000
-```
-
-Argumentos:
-
-- `--source`: Cuenta que crea/modifica la trustline
-- `--line`: Activo para crear trustline en formato CODE:ISSUER
-- `--limit`: Cantidad máxima que se puede poseer (0 elimina la trustline)
-
-### Administrar Datos
-
-Administrar las entradas de datos de la cuenta:
-
-```sh
-stellar tx new manage-data \
-  --source alice \
-  --data-name config \
-  --data-value 7465737476616c7565 # hex encoded
-```
-
-Notas:
-
-- `--data-name`: Nombre de la entrada de datos (hasta 64 bytes)
-- `--data-value`: Valor codificado en hexadecimal a almacenar (hasta 64 bytes, omitir para eliminar)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-op-add.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-op-add.mdx
deleted file mode 100644
index 58adf0c19f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-op-add.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: tx op add
-hide_table_of_contents: true
-description: Crear transacciones Stellar utilizando la CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-op-add.mdx
----
-
-Como se vio antes, puedes usar pipes para pasar un sobre de transacción entre comandos. Antes solo habíamos visto transacciones con una operación, sin embargo, como se mencionó, puede haber hasta 100 operaciones en una sola transacción.
-
-Para agregar una operación a una transacción puedes usar el comando `tx op add`. Este comando toma el sobre de transacción del comando anterior y le añade una operación.
-
-Consideremos un ejemplo más complicado. Considera emitir un activo, aquí `USDC`, con el requisito de que solo el emisor pueda transferir fondos al distribuidor.
-
-```sh
-
-stellar keys generate --fund issuer
-stellar keys generate --fund distributor
-
-ISSUER_PK=$(stellar keys address issuer)
-
-ASSET="USDC:$ISSUER_PK"
-
-# Issue the asset by setting its options, establishing a trustline, and
-# transferring the smallest amount possible to the distributor. Then
-# deauthorize the distributor so that people can only send Claimable Balances,
-# rather than transferring assets directly.
-
-# first the issuer sets the options for being able to clawback and revoke the asset
-stellar tx new set-options --fee 1000 --source issuer --set-clawback-enabled --set-revocable --build-only \
-# next the distributor establishes a trustline with the asset. Note that here the distributor the source account for the operation, not the issuer
-| stellar tx op add change-trust --op-source distributor --line $ASSET \
-# then the issuer sends the smallest amount possible to the distributor
-| stellar tx op add payment --destination distributor --asset $ASSET --amount 1 \
-# finally the issuer deauthorizes the distributor from being able to send the asset
-| stellar tx op add set-trustline-flags --asset $ASSET --trustor distributor --clear-authorize \
-# Then both accounts need to sign the transaction
-| stellar tx sign --sign-with-key issuer \
-| stellar tx sign --sign-with-key distributor \
-| stellar tx send
-
-# Next is an example of sandwiching an operation. That is giving permission in one operation, preforming the operation, and then removing the permission in a third operation.
-# Here is an example of minting new assets to the distributor with a sandwich transaction
-# First authorize the distributor to receive the asset
-stellar tx new set-trustline-flags --fee 1000 --build-only --source issuer --asset $ASSET --trustor $distributor_PK --set-authorize \
-# Then mint the asset to the distributor
-| stellar tx op add payment --destination distributor --asset $ASSET --amount 1_000_000_000_000 \
-# Finally remove the authorization
-| stellar tx op add set-trustline-flags --asset $ASSET --trustor distributor --clear-authorize \
-| stellar tx sign --sign-with-key issuer \
-| stellar tx send
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-sign.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-sign.mdx
deleted file mode 100644
index 3384879364..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/tx-sign.mdx
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: tx sign y tx send
-hide_table_of_contents: true
-description: Crear transacciones Stellar usando la CLI de Stellar
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-sign.mdx
----
-
-Los ejemplos anteriores de uso de `tx new` mostraron cómo crear transacciones. Sin embargo, estas transacciones estaban listas para ser firmadas y enviadas a la red inmediatamente.
-
-Para evitar esto, cada uno de los subcomandos tiene el argumento `--build-only`, que como su nombre indica solo construye la transacción y muestra el sobre de la transacción.
-
-## `tx sign`
-
-Volvamos al primer ejemplo de creación de la cuenta de `bob`:
-
-```sh
-stellar tx new create-account \
-  --source alice \
-  --destination bob \
-  --starting-balance 100_000_000 \
-  --build-only
-```
-
-saldría algo así:
-
-```sh
-AAAAAgAAAADwSUp9CwmVlPN40mKX1I1j39y6DmYc36QS1aK2x6eYVQAAAGQAEcMsAAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAACTMkzn1TwPo8SIhnKvnyuv9K2/aWjpX9NTYfyiA7vXaAAAAAAX14QAAAAAAAAAAAA==
-```
-
-Puedes inspeccionarlo con [stellar lab!](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&xdr$blob=AAAAAgAAAADwSUp9CwmVlPN40mKX1I1j39y6DmYc36QS1aK2x6eYVQAAAGQAEcMsAAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAACTMkzn1TwPo8SIhnKvnyuv9K2//aWjpX9NTYfyiA7vXaAAAAAAX14QAAAAAAAAAAAA==;;) Donde también puedes firmar y enviar la transacción.
-
-Sin embargo, también puedes firmar la transacción con el comando `tx sign`. Para hacer esto, puedes canalizar la salida del comando `tx new` hacia el comando `tx sign`:
-
-```sh
-stellar tx new create-account \
-    --source alice \
-    --destination bob \
-    --starting-balance 100_000_000 \
-    --build-only \
-  | stellar tx sign --sign-with-key alice
-```
-
-Esto debería mostrar algo así:
-
-```sh
-AAAAAgAAAAAebE8Ewg9uzvHRAl+UmvP0kixsyp238kkz0zOy+91FeQAAAGQAFJk4AAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAPpiy8qfSw4pLYG/Bav78FfrFWlte7YQfiHX41DQ+nGWAAAAAAX14QAAAAAAAAAAAfvdRXkAAABA4kjz9Yeub/IrzogjMr57U4nYwCmSJAXxIW+7Xyjan/UweIByF7uEhVS4gEl1N138uq07njVxZwRMtugWyMleCg==
-```
-
-Puedes nuevamente [verlo en lab y observar que ahora hay una firma adjunta al sobre de la transacción](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&xdr$blob=AAAAAgAAAAAebE8Ewg9uzvHRAl+UmvP0kixsyp238kkz0zOy+91FeQAAAGQAFJk4AAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAPpiy8qfSw4pLYG//Bav78FfrFWlte7YQfiHX41DQ+nGWAAAAAAX14QAAAAAAAAAAAfvdRXkAAABA4kjz9Yeub//IrzogjMr57U4nYwCmSJAXxIW+7Xyjan//UweIByF7uEhVS4gEl1N138uq07njVxZwRMtugWyMleCg==;;).
-
-:::tip
-
-¡O firma con lab! Aunque actualmente debes enviarlo desde lab y no puedes regresar al CLI (¡un trabajo en progreso!).
-
-```sh
-stellar tx new create-account \
-    --source alice \
-    --destination bob \
-    --starting-balance 100_000_000 \
-    --build-only \
-  | stellar tx sign --sign-with-lab
-```
-
-:::
-
-## `tx send`
-
-Finalmente, para enviar la transacción a la red, puedes usar el comando `tx send`. Este comando enviará la transacción a la red.
-
-```sh
-stellar tx new create-account \
-    --source alice \
-    --destination bob \
-    --starting-balance 100_000_000 \
-    --build-only \
-  | stellar tx sign --sign-with-key alice \
-  | stellar tx send
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/upload-deploy.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/upload-deploy.mdx
deleted file mode 100644
index 2efabaa34e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/upload-deploy.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Sube y despliega un contrato inteligente
-hide_table_of_contents: true
-description: Combina los comandos de subir y desplegar en la CLI de Stellar para realizar ambas tareas
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/upload-deploy.mdx
----
-
-Puedes combinar los comandos `upload` y `deploy` del Stellar CLI para realizar ambas tareas:
-
-```bash
-stellar contract deploy \
-    --source S... \
-    --network testnet \
-    --wasm ../relative/path/to/soroban_contract.wasm
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/upload-wasm.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/upload-wasm.mdx
deleted file mode 100644
index 93dd732a54..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/cookbook/upload-wasm.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Subir el bytecode Wasm
-hide_table_of_contents: true
-description: Usa la CLI de Stellar para subir un contrato inteligente compilado al ledger
-custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/upload-wasm.mdx
----
-
-Para usar el CLI de Stellar y subir un contrato inteligente compilado en el ledger, utiliza el comando `stellar contract upload`:
-
-```bash
-stellar contract upload \
-    --source S... \
-    --network testnet \
-    --wasm ../relative/path/to/soroban_contract.wasm
-```
-
-:::note
-
-Ten en cuenta que este comando devolverá el hash ID del bytecode Wasm, en vez de una dirección para una instancia de contrato.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/install-cli.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/install-cli.mdx
deleted file mode 100644
index 35be0a6612..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/install-cli.mdx
+++ /dev/null
@@ -1,94 +0,0 @@
----
-title: Instalar el CLI
-description: Cómo instalar el Stellar CLI.
-sidebar_position: 10
----
-
-import { StellarCliGitHubVersion } from "@site/src/components/StellarCliGitHubVersion";
-
-# Instalar el Stellar CLI
-
-### Stellar CLI
-
-Hay varias formas de instalar la versión más reciente del Stellar CLI.
-
-Instalar con script (macOS, Linux):
-
-```text
-curl -fsSL https://github.com/stellar/stellar-cli/raw/main/install.sh | sh
-```
-
-Instalar con Homebrew (macOS, Linux):
-
-```text
-brew install stellar-cli
-```
-
-Instalar con winget (Windows):
-
-```text
-winget install --id Stellar.StellarCLI
-```
-
-Instalar con cargo desde la fuente ([github.com/stellar/stellar-cli](https://github.com/stellar/stellar-cli)):
-
-```text
-cargo install --locked stellar-cli
-```
-
-:::note
-
-Instalar desde la fuente requiere Rust y sistemas de compilación C.
-
-Para instalar Rust, consulta:
-
-- https://www.rust-lang.org/tools/install
-
-Para instalar un sistema de compilación C en Debian/Ubuntu, utiliza:
-
-```
-sudo apt update && sudo apt install -y build-essential
-```
-
-:::
-
-Instalar en tu acción de GitHub (esta es una opción preferida para instalar el CLI en tus acciones de GitHub)
-
-<StellarCliGitHubVersion />
-
-:::note
-
-También puedes utilizar la herramienta de terceros [SVM (Stellar Version Manager)](https://www.npmjs.com/package/svm-cli), un administrador de versiones para Stellar CLI que te permite instalar y cambiar entre diferentes versiones de stellar-cli.
-
-:::
-
-## Configurar autocompletado
-
-El Stellar CLI admite autocompletado. Para configurar, ejecuta los siguientes comandos:
-
-```text
-stellar completion --shell <SHELL>
-```
-
-Los valores posibles de SHELL son `bash`, `elvish`, `fish`, `powershell`, `zsh`, etc.
-
-Para habilitar el autocompletado en la shell bash actual, ejecuta:
-
-```text
-source <(stellar completion --shell bash)
-```
-
-Para habilitar el autocompletado permanentemente, ejecuta:
-
-```text
-echo "source <(stellar completion --shell bash)" >> ~/.bashrc
-```
-
-## Recetario del Stellar CLI
-
-Para entender cómo aprovechar al máximo la CLI de Stellar, consulta el [Manual de Cocina de la CLI de Stellar](./cookbook/README.mdx) para recetas y una colección de recursos que te enseñarán a usar la CLI. Ejemplos de recetas incluidas en el recetario del CLI son: enviar pagos, gestionar el ciclo de vida del contrato, extender instancia/almacenamiento/wasm del contrato, y más.
-
-## Tutoriales en video
-
-- Video tutorial sobre `network container`, `keys` y `contract init` de la [reunión de desarrolladores del 2024-06-27](/meetings/2024/06/27)
-- Video tutorial sobre `alias` y `snapshot` de la [reunión de desarrolladores del 2024-09-12](/meetings/2024/09/12)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/plugins-list.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/plugins-list.mdx
deleted file mode 100644
index 6026ec381d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/plugins-list.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Lista de Plugins
-description: Consulta una lista de plugins publicados de Stellar CLI
-sidebar_position: 30
----
-
-Esta es una lista de todos los plugins disponibles ofrecidos por la comunidad, así que revísalos con cuidado antes de usarlos.
-
-### [theahaco/scaffold-stellar](https://github.com/theahaco/scaffold-stellar)
-
-El ciclo de vida de la aplicación Stellar simplificado. CLI `stellar scaffold`: inicia, aprende y desarrolla aplicaciones ambiciosas. CLI `stellar registry`: crea, publica, despliega y actualiza binarios Wasm + contratos inteligentes (o usa los de otros)
-
-[https://github.com/theahaco/scaffold-stellar](https://github.com/theahaco/scaffold-stellar)
-
-### [lightsail-network/stellar-contract-bindings](https://github.com/lightsail-network/stellar-contract-bindings)
-
-Herramienta CLI diseñada para generar enlaces de lenguaje para contratos inteligentes Stellar Soroban.
-
-[https://github.com/lightsail-network/stellar-contract-bindings](https://github.com/lightsail-network/stellar-contract-bindings)
-
-### [OpenZeppelin/stellar-upgrader-cli](https://github.com/OpenZeppelin/stellar-upgrader-cli)
-
-CLI que ayuda a los desarrolladores a actualizar contratos Stellar
-
-[https://github.com/OpenZeppelin/stellar-upgrader-cli](https://github.com/OpenZeppelin/stellar-upgrader-cli)
-
-### [brozorec/smart-account-sign](https://github.com/brozorec/smart-account-sign)
-
-Herramienta CLI para interactuar con Stellar Smart Accounts
-
-[https://github.com/brozorec/smart-account-sign](https://github.com/brozorec/smart-account-sign)
-
-### [fnando/stellar-hello-plugin](https://github.com/fnando/stellar-hello-plugin)
-
-Este es solo un plugin de ejemplo para Stellar CLI
-
-[https://github.com/fnando/stellar-hello-plugin](https://github.com/fnando/stellar-hello-plugin)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/plugins.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/plugins.mdx
deleted file mode 100644
index 784d16859d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/plugins.mdx
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: Plugins
-description: Cómo usar plugins con el Stellar CLI
-sidebar_position: 20
----
-
-# Plugins
-
-El Stellar CLI admite plugins de una manera muy simple. Todo lo que necesitas es un ejecutable (no tiene que ser un binario) en tu `PATH` que comience con `stellar-` y el CLI lo detectará y cargará automáticamente.
-
-También puedes instalar plugins que están disponibles públicamente. Un ejemplo es [rs-stellar-strkey](https://github.com/stellar/rs-stellar-strkey); puedes instalarlo usando cargo de Rust:
-
-```sh
-cargo install --locked stellar-strkey --features cli
-```
-
-Eso instalará el binario `stellar-strkey` en tu directorio `~/.cargo/bin`. Para el propósito de este ejemplo, asumiremos que ese directorio ya está en tu `$PATH`.
-
-:::danger Advertencia de seguridad
-
-¡Ten cuidado! Los plugins tienen el mismo acceso a tu sistema que el Stellar CLI en sí. Solo instala plugins de fuentes en las que confíes.
-
-:::
-
-## Listar plugins disponibles
-
-Para listar los plugins disponibles en tu sistema, usa el comando `stellar plugin ls`:
-
-```console
-$ stellar plugin ls
-Installed Plugins:
-    strkey
-```
-
-## Crear un nuevo plugin
-
-Como se mencionó anteriormente, los plugins solo necesitan ser un ejecutable disponible en tu `PATH` que comience con `stellar-`. Comienza creando un nuevo archivo llamado `stellar-hello`. Este ejemplo muestra cómo crear un plugin usando `bash`, así que necesitas un sistema que lo soporte (basado en Unix o WSL de Windows).
-
-```sh
-touch ~/.bin/stellar-hello
-```
-
-Agrega el siguiente contenido al archivo:
-
-```bash
-#!/usr/bin/env bash
-
-echo "hello from stellar plugin"
-```
-
-Ahora, haz el archivo ejecutable con `chmod`:
-
-```sh
-chmod +x ~/.bin/stellar-hello
-```
-
-Si todo está configurado correctamente (es decir, el `~/.bin` está en tu `PATH` y `~/.bin/stellar-hello` es ejecutable), deberías poder encontrarlo:
-
-```console
-$ stellar plugin ls
-Installed Plugins:
-    hello
-    strkey
-```
-
-Finalmente, puedes ejecutarlo llamando a `stellar hello`:
-
-```console
-$ stellar hello
-hello from stellar plugin
-```
-
-:::tip
-
-Si usas GitHub para alojar el repositorio de tu plugin, considera añadir un tema de repositorio `stellar-cli-plugin` [repository topic](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics). De este modo, tu plugin aparecerá listado con `stellar plugin search`.
-
-:::
-
-Cuando ejecutas un comando y no se encuentra un comando incorporado, el CLI de Stellar busca un plugin. Esto sucede incluso para subcomandos. Por ejemplo, supongamos que estás creando un nuevo plugin para generar enlaces Ruby para tu contrato; podrías tener algo como `stellar-contract-bindings-ruby`, y los usuarios podrían ejecutar `stellar contract bindings ruby` en lugar de la versión con guiones.
-
-### Resolución de problemas
-
-Si Stellar CLI no puede encontrar tu plugin, asegúrate de limpiar todos los elementos anteriores:
-
-- Asegúrate de que el archivo comience con `stellar-`
-- Verifica que sea ejecutable (`chmod +x`)
-- Verifica que su ubicación esté en tu `PATH`
-- Reinicia tu terminal o recarga tu configuración de shell
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/stellar-cli.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/stellar-cli.mdx
deleted file mode 100644
index a8bcada2e0..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/cli/stellar-cli.mdx
+++ /dev/null
@@ -1,5233 +0,0 @@
----
-sidebar_position: 10
-description: Este documento contiene el contenido de ayuda para el programa de línea de comandos Stellar.
----
-
-# Manual de Stellar CLI
-
-Este documento contiene el contenido de ayuda para el programa de línea de comandos `stellar`.
-
-## `stellar`
-
-Trabaja sin problemas con cuentas, contratos y activos de Stellar desde la línea de comandos.
-
-- Generar y gestionar claves y cuentas
-- Crear, desplegar e interactuar con contratos
-- Desplegar contratos de activos
-- Transmitir eventos
-- Iniciar testnets locales
-- Decodificar, codificar XDR
-- ¡Más!
-
-Para información adicional, ver:
-
-- Documentación de Stellar: https://developers.stellar.org
-- Documentación de Contratos Inteligentes: https://developers.stellar.org/docs/build/smart-contracts/overview
-- Documentación de CLI: https://developers.stellar.org/docs/tools/developer-tools/cli/stellar-cli
-
-Para empezar, genera una nueva identidad:
-
-```
-stellar keys generate alice
-```
-
-Usa claves con el flag `--source` en otros comandos.
-
-Los comandos que funcionan con contratos están organizados bajo el subcomando `contract`. Enuméralos:
-
-```
-stellar contract --help
-```
-
-Usa contratos como un CLI:
-
-```
-stellar contract invoke --id CCR6QKTWZQYW6YUJ7UP7XXZRLWQPFRV6SWBLQS4ZQOSAF4BOUD77OTE2 --source alice --network testnet -- --help
-```
-
-Todo después de los `--` dobles (el "slop") se analiza como argumentos para el CLI específico del contrato, generado sobre la marcha a partir del esquema del contrato. Para el ejemplo hello world, con una función llamada `hello` que toma un argumento de cadena `to`, así es como lo invocas:
-
-```
-stellar contract invoke --id CCR6QKTWZQYW6YUJ7UP7XXZRLWQPFRV6SWBLQS4ZQOSAF4BOUD77OTE2 --source alice --network testnet -- hello --to world
-```
-
-**Uso:** `stellar [OPTIONS] <COMMAND>`
-
-###### **Subcomandos:**
-
-- `contract` — Herramientas para desarrolladores de contratos inteligentes
-- `doctor` — Diagnosticar y solucionar incidencias de CLI y red
-- `events` — Observa la red en busca de eventos de contratos
-- `env` — Imprime las variables de entorno
-- `keys` — Crea y gestiona identidades, incluyendo claves y direcciones
-- `network` — Configura la conexión a redes
-- `container` — Inicia redes locales en contenedores
-- `config` — Gestionar la configuración del CLI
-- `snapshot` — Descarga una imagen de un ledger desde un archivo de respaldo
-- `tx` — Firmar, simular y enviar transacciones
-- `xdr` — Decodificar y codificar XDR
-- `strkey` — Decodificar y codificar strkey
-- `completion` — Imprimir código de autocompletado para el shell especificado
-- `cache` — Almacenar en caché transacciones y especificaciones de contratos
-- `version` — Imprimir información de versión
-- `plugin` — El subcomando para plugins de CLI
-- `ledger` — Obtener información del ledger
-- `fee-stats` — Obtener estadísticas de tarifa de la red
-
-###### **Opciones:**
-
-- `--list` — ⚠️ Obsoleto, usa `stellar plugin ls`. Listar los plugins instalados. Por ejemplo. `stellar-hello`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-- `-f`, `--filter-logs <FILTER_LOGS>` — Filtrar salida de logs. Para activar `stellar_cli::log::footprint=debug` o apagar `=off`. También se puede usar la variable de entorno `RUST_LOG`
-- `-q`, `--quiet` — No escribir logs en stderr incluyendo `INFO`
-- `-v`, `--verbose` — Registrar eventos DEBUG
-- `--very-verbose` [alias: `vv`] — Registrar eventos DEBUG y TRACE
-- `--no-cache` — No almacenar en caché tus simulaciones y transacciones
-
-## `stellar contract`
-
-Herramientas para desarrolladores de contratos inteligentes
-
-**Uso:** `stellar contract <COMMAND>`
-
-###### **Subcomandos:**
-
-- `asset` — Utilidades para desplegar un contrato de activo Stellar o obtener su id
-- `alias` — Utilidades para gestionar alias de contratos
-- `bindings` — Generar bindings de cliente de código para un contrato
-- `build` — Crear un contrato desde el código fuente
-- `extend` — Extender el tiempo de vida del ledger de una entrada de ledger de datos de contrato
-- `deploy` — Desplegar un contrato wasm
-- `fetch` — Obtener el binario Wasm de un contrato
-- `id` — Generar el id del contrato para un contrato o activo dado
-- `info` — Acceder a información sobre contratos
-- `init` — Inicializar un proyecto de contrato Soroban
-- `inspect` — ⚠️ Obsoleto, usa `contract info`. Inspeccionar un archivo WASM listando funciones del contrato, metadatos, etc.
-- `upload` — Instalar un archivo WASM en el ledger sin crear una instancia del contrato
-- `install` — ⚠️ Obsoleto, usa `contract upload`. Instala un archivo WASM en el ledger sin crear una instancia de contrato
-- `invoke` — Invocar una función de contrato
-- `optimize` — ⚠️ Obsoleto, usa `build --optimize`. Optimizar un archivo WASM
-- `read` — Imprimir el valor actual de una entrada del ledger de datos del contrato
-- `restore` — Restaurar un valor evicto para una entrada del ledger de datos del contrato
-
-## `stellar contract asset`
-
-Utilidades para desplegar un contrato de activo Stellar o obtener su id
-
-**Uso:** `stellar contract asset <COMMAND>`
-
-###### **Subcomandos:**
-
-- `id` — Obtener el Id del contrato de activo Soroban integrado. Obsoleto, usa `stellar contract id asset` en su lugar
-- `deploy` — Desplegar contrato de activo Soroban integrado
-
-## `stellar contract asset id`
-
-Obtener el Id del contrato de activo Soroban integrado. Obsoleto, usa `stellar contract id asset` en su lugar
-
-**Uso:** `stellar contract asset id [OPTIONS] --asset <ASSET>`
-
-###### **Opciones:**
-
-- `--asset <ASSET>` — ID del activo clásico Stellar a envolver, por ejemplo "native", "USDC:G...5", "USDC:alias"
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-- `-n`, `--network <NETWORK>` — Nombre de red a usar de la configuración
-
-## `stellar contract asset deploy`
-
-Desplegar contrato de activo Soroban integrado
-
-**Uso:** `stellar contract asset deploy [OPTIONS] --asset <ASSET> --source-account <SOURCE_ACCOUNT>`
-
-###### **Opciones:**
-
-- `--asset <ASSET>` — ID del activo clásico Stellar a envolver, por ejemplo "USDC:G...5"
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si se usa frase Seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase Seed para firmar, establece qué ruta jerárquica determinista usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--alias <ALIAS>` — El alias que se utilizará para guardar el id del activo. Siempre que se use, `--alias` siempre sobrescribirá la configuración existente del id del contrato sin pedir confirmación
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Endpoint del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de red a usar de la configuración
-
-- `--fee <FEE>` — Cantidad de tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Salida del costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el base64 xdr a stdout
-
-## `stellar contract alias`
-
-Utilidades para gestionar alias de contratos
-
-**Uso:** `stellar contract alias <COMMAND>`
-
-###### **Subcomandos:**
-
-- `remove` — Eliminar alias de contrato
-- `add` — Agregar alias de contrato
-- `show` — Mostrar el id del contrato asociado a un alias dado
-- `ls` — Listar todos los alias
-
-## `stellar contract alias remove`
-
-Eliminar alias de contrato
-
-**Uso:** `stellar contract alias remove [OPTIONS] <ALIAS>`
-
-###### **Argumentos:**
-
-- `<ALIAS>` — El alias de contrato que será eliminado
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor RPC
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar contract alias add`
-
-Agregar alias de contrato
-
-**Uso:** `stellar contract alias add [OPTIONS] --id <CONTRACT_ID> <ALIAS>`
-
-###### **Argumentos:**
-
-- `<ALIAS>` — El alias de contrato que se utilizará
-
-###### **Opciones:**
-
-- `--overwrite` — Sobrescribir el alias de contrato si ya existe
-- `--id <CONTRACT_ID>` — El id del contrato que se asociará con el alias
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-- `-n`, `--network <NETWORK>` — Nombre de red a usar de la configuración
-
-## `stellar contract alias show`
-
-Mostrar el id del contrato asociado a un alias dado
-
-**Uso:** `stellar contract alias show [OPTIONS] <ALIAS>`
-
-###### **Argumentos:**
-
-- `<ALIAS>` — El alias de contrato que será mostrado
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-- `-n`, `--network <NETWORK>` — Nombre de red a usar de la configuración
-
-## `stellar contract alias ls`
-
-Listar todos los alias
-
-**Uso:** `stellar contract alias ls [OPTIONS]`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-## `vínculos de contrato stellar`
-
-Generar enlaces de código del cliente para un contrato
-
-**Uso:** `stellar contract bindings <COMMAND>`
-
-###### **Subcomandos:**
-
-- `json` — Generar enlaces Json
-- `rust` — Generar enlaces de Rust
-- `typescript` — Generar un paquete de TypeScript / JavaScript
-- `python` — Generar enlaces de Python
-- `java` — Generar enlaces de Java
-- `flutter` — Generar enlaces para Flutter
-- `swift` — Generar enlaces para Swift
-- `php` — Generar enlaces para PHP
-
-## `vínculos de contrato stellar json`
-
-Generar enlaces Json
-
-**Uso:** `stellar contract bindings json --wasm <WASM>`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta al binario wasm
-
-## `vínculos de contrato stellar rust`
-
-Generar enlaces de Rust
-
-**Uso:** `stellar contract bindings rust --wasm <WASM>`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta al binario wasm
-
-## `vínculos de contrato stellar typescript`
-
-Generar un paquete de TypeScript / JavaScript
-
-**Uso:** `stellar contract bindings typescript [OPTIONS] --output-dir <OUTPUT_DIR> <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta del archivo wasm en el sistema de archivos local. Proporciona esto O `--wasm-hash` O `--contract-id`
-- `--wasm-hash <WASM_HASH>` — Hash del blob wasm en una red. Proporciona esto O `--wasm` O `--contract-id`
-- `--contract-id <CONTRACT_ID>` [alias: `id`] — ID/alias del contrato en una red. Proporciona esto O `--wasm-hash` O `--wasm`
-- `--output-dir <OUTPUT_DIR>` — Dónde colocar el proyecto generado
-- `--overwrite` — Si se debe sobrescribir el directorio de salida si ya existe
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de la red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar del config
-
-## `vínculos de contrato stellar python`
-
-Generar enlaces de Python
-
-**Uso:** `stellar contract bindings python`
-
-## `vínculos de contrato stellar java`
-
-Generar enlaces de Java
-
-**Uso:** `stellar contract bindings java`
-
-## `stellar contract bindings flutter`
-
-Generar enlaces para Flutter
-
-**Uso:** `stellar contract bindings flutter`
-
-## `stellar contract bindings swift`
-
-Generar enlaces para Swift
-
-**Uso:** `stellar contract bindings swift`
-
-## `stellar contract bindings php`
-
-Generar enlaces para PHP
-
-**Uso:** `stellar contract bindings php`
-
-## `contrato stellar construir`
-
-Crear un contrato desde el código fuente
-
-Se construyen todas las crates que están referenciadas por el manifiesto cargo (Cargo.toml) que tienen cdylib como su tipo de crate. Las crates se construyen para el objetivo wasm32. A menos que se configure de otra manera, las crates se construyen con sus características predeterminadas y con su perfil de lanzamiento.
-
-En los espacios de trabajo, se construyen todas las crates a menos que se especifique un nombre de paquete, o el comando se ejecute desde el subdirectorio de una crate de workspace.
-
-Para ver los comandos que se ejecutarán, sin ejecutarlos, usa la opción --print-commands-only.
-
-**Uso:** `stellar contract build [OPTIONS]`
-
-###### **Características:**
-
-- `--features <FEATURES>` — Construir con la lista de características activadas, separadas por espacio o coma
-- `--all-features` — Construir con todas las características activadas
-- `--no-default-features` — Construir sin activar la característica predeterminada
-
-###### **Metadatos:**
-
-- `--meta <META>` — Agregar clave-valor a los metadatos del contrato (agrega el meta a la sección personalizada `contractmetav0`)
-
-###### **Opciones:**
-
-- `--manifest-path <MANIFEST_PATH>` — Ruta al Cargo.toml
-
-- `--package <PACKAGE>` — Paquete para construir
-
-  Si se omite, se construyen todos los paquetes que construyen para el tipo de crate cdylib.
-
-- `--profile <PROFILE>` — Construir con el perfil especificado
-
-  Valor predeterminado: `release`
-
-- `--out-dir <OUT_DIR>` — Directorio para copiar archivos wasm
-
-  Si se proporciona, los archivos wasm pueden encontrarse en el directorio de destino de cargo, y en el directorio especificado.
-
-  Si se omite, los archivos wasm se escriben solo en el directorio de destino de cargo.
-
-- `--optimize` — Optimizar el wasm generado
-
-###### **Otros:**
-
-- `--print-commands-only` — Imprimir comandos para construir sin ejecutarlos
-
-## `contrato stellar extender`
-
-Extender el tiempo de vida del libro mayor de una entrada de libro mayor de datos del contrato.
-
-Si no se especifican claves, el contrato en sí se extiende.
-
-**Uso:** `stellar contract extend [OPTIONS] --ledgers-to-extend <LEDGERS_TO_EXTEND> --source-account <SOURCE_ACCOUNT>`
-
-###### **Opciones:**
-
-- `--ledgers-to-extend <LEDGERS_TO_EXTEND>` — Número de libros mayores a extender las entradas
-
-- `--ttl-ledger-only` — Solo imprime el nuevo libro mayor de tiempo de vida
-
-- `--id <CONTRACT_ID>` — ID del contrato que posee las entradas de datos. Si no se proporcionan claves, la instancia del contrato se extenderá
-
-- `--key <KEY>` — Clave de almacenamiento (símbolos solamente)
-
-- `--key-xdr <KEY_XDR>` — Clave de almacenamiento (XDR codificado en base64)
-
-- `--wasm <WASM>` — Ruta al archivo wasm del código del contrato a extender
-
-- `--wasm-hash <WASM_HASH>` — Ruta al archivo wasm del código del contrato a extender
-
-- `--durability <DURABILITY>` — Durabilidad de la entrada de almacenamiento
-
-  Valor predeterminado: `persistent`
-
-  Valores posibles:
-
-  - `persistent`: Persistente
-  - `temporary`: Temporal
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una wallet ledger
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar del config
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr en base64 en stdout
-
-## `contrato stellar desplegar`
-
-Desplegar un contrato wasm
-
-**Uso:** `stellar contract deploy [OPTIONS] --source-account <SOURCE_ACCOUNT> <--wasm <WASM>|--wasm-hash <WASM_HASH>> [-- <CONTRACT_CONSTRUCTOR_ARGS>...]`
-
-###### **Argumentos:**
-
-- `<CONTRACT_CONSTRUCTOR_ARGS>` — Si se proporciona, se pasarán a la función `__constructor` del contrato con los argumentos proporcionados para esa función como `--arg-name value`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Archivo WASM a desplegar
-
-- `--wasm-hash <WASM_HASH>` — Hash del archivo WASM ya instalado/desplegado
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una wallet ledger
-
-- `-i`, `--ignore-checks` — Si deseas ignorar las comprobaciones de seguridad al desplegar contratos
-
-  Valor predeterminado: `false`
-
-- `--alias <ALIAS>` — El alias que se utilizará para guardar el id del contrato. Siempre que se utilice, `--alias` siempre sobrescribirá la configuración del id del contrato existente sin pedir confirmación
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--salt <SALT>` — Sal personalizada de 32 bytes para el id del token
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar del config
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr en base64 en stdout
-
-## `contrato stellar obtener`
-
-Obtener el binario wasm de un contrato
-
-**Uso:** `stellar contract fetch [OPTIONS]`
-
-###### **Opciones:**
-
-- `--id <CONTRACT_ID>` — ID del contrato a obtener
-- `--wasm-hash <WASM_HASH>` — Wasm para obtener
-- `-o`, `--out-file <OUT_FILE>` — Dónde escribir la salida, de lo contrario se usa stdout
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de la red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar del config
-
-## `identificación del contrato stellar`
-
-Generar el id del contrato para un contrato o activo dado
-
-**Uso:** `stellar contract id <COMMAND>`
-
-###### **Subcomandos:**
-
-- `asset` — Desplegar el contrato de activo integrado de Soroban
-- `wasm` — Desplegar contrato Wasm normal
-
-## `activo de identificación del contrato stellar`
-
-Desplegar contrato de activo integrado de Soroban
-
-**Uso:** `stellar contract id asset [OPTIONS] --asset <ASSET>`
-
-###### **Opciones:**
-
-- `--asset <ASSET>` — ID del activo clásico Stellar a envolver, por ejemplo "native", "USDC:G...5", "USDC:alias"
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar contract id wasm`
-
-Desplegar contrato Wasm normal
-
-**Uso:** `stellar contract id wasm [OPCIONES] --salt <SALT> --source-account <SOURCE_ACCOUNT>`
-
-###### **Opciones:**
-
-- `--salt <SALT>` — ID del contrato Soroban
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar contract info`
-
-Accede a la información sobre contratos
-
-**Uso:** `stellar contract info <COMMAND>`
-
-###### **Subcomandos:**
-
-- `interface` — Muestra la interfaz de un contrato
-- `meta` — Muestra los metadatos almacenados en un contrato
-- `env-meta` — Muestra los metadatos necesarios del entorno almacenados en un contrato
-- `build` — Muestra la información de compilación del contrato, si está disponible
-
-## `stellar contract info interface`
-
-Muestra la interfaz de un contrato.
-
-La interfaz de un contrato describe las funciones, parámetros y tipos que el contrato pone a disposición para ser llamados.
-
-Los datos producidos por este comando son un flujo de valores `SCSpecEntry` XDR. Consulta las definiciones de tipo en [stellar-xdr](https://github.com/stellar/stellar-xdr). [Consulta también el formato de datos XDR](https://developers.stellar.org/docs/learn/encyclopedia/data-format/xdr).
-
-No produce datos cuando no hay datos presentes en el contrato.
-
-**Uso:** `stellar contract info interface [OPCIONES] <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta del archivo Wasm en el sistema de archivos local. Proporciona esto O `--wasm-hash` O `--contract-id`
-- `--wasm-hash <WASM_HASH>` — Hash del blob Wasm en una red. Proporciona esto O `--wasm` O `--contract-id`
-- `--contract-id <CONTRACT_ID>` [alias: `id`] — ID/alias del contrato en una red. Proporciona esto O `--wasm-hash` O `--wasm`
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `rust`
-
-  Valores posibles:
-
-  - `rust`: Salida de código Rust de la interfaz del contrato
-  - `xdr-base64`: Salida XDR de la entrada de información
-  - `json`: Salida JSON de la entrada de información (una línea, no formateada)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada de información
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar contract info meta`
-
-Muestra los metadatos almacenados en un contrato.
-
-Los metadatos de un contrato son una serie de pares clave-valor que el desarrollador del contrato puede establecer con cualquier valor para proporcionar metadatos sobre el contrato. Los metadatos también contienen información como la versión del SDK de Rust y la versión del compilador de Rust.
-
-Los datos producidos por este comando son un flujo de valores `SCMetaEntry` XDR. Consulta las definiciones de tipo en [stellar-xdr](https://github.com/stellar/stellar-xdr). [Ver también el formato de datos XDR](https://developers.stellar.org/docs/learn/encyclopedia/data-format/xdr).
-
-No devuelve datos cuando no hay datos presentes en el contrato.
-
-**Uso:** `stellar contract info meta [OPCIONES] <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta del archivo Wasm en el sistema local. Proporcionar esto O `--wasm-hash` O `--contract-id`
-- `--wasm-hash <WASM_HASH>` — Hash del blob Wasm en la red. Proporcionar esto O `--wasm` O `--contract-id`
-- `--contract-id <CONTRACT_ID>` [alias: `id`] — ID/alias del contrato en la red. Proporcionar esto O `--wasm-hash` O `--wasm`
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `text`
-
-  Valores posibles:
-
-  - `text`: Salida de texto de la entrada de información meta
-  - `xdr-base64`: Salida XDR de la entrada de información
-  - `json`: Salida JSON de la entrada de información (una línea, no formateada)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada de información
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red para usar desde la configuración
-
-## `stellar contract info env-meta`
-
-Muestra los metadatos necesarios del entorno almacenados en un contrato.
-
-Env-meta es información almacenada en todos los contratos, en la sección personalizada `contractenvmetav0` de WASM, sobre el entorno para el cual se construyó el contrato. Env-meta permite que el entorno Soroban sepa si el contrato es compatible con la red en su configuración actual.
-
-Los datos producidos por este comando son un flujo de valores `SCEnvMetaEntry` XDR. Consulta las definiciones de tipo en [stellar-xdr](https://github.com/stellar/stellar-xdr). [Consulta también el formato de datos XDR](https://developers.stellar.org/docs/learn/encyclopedia/data-format/xdr).
-
-No produce datos cuando no hay datos presentes en el contrato.
-
-**Uso:** `stellar contract info env-meta [OPCIONES] <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta del archivo Wasm en el sistema de archivos local. Proporciona esto O `--wasm-hash` O `--contract-id`
-- `--wasm-hash <WASM_HASH>` — Hash del blob Wasm en una red. Proporciona esto O `--wasm` O `--contract-id`
-- `--contract-id <CONTRACT_ID>` [alias: `id`] — ID/alias del contrato en una red. Proporciona esto O `--wasm-hash` O `--wasm`
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `text`
-
-  Valores posibles:
-
-  - `text`: Salida de texto de la entrada de información meta
-  - `xdr-base64`: Salida XDR de la entrada de información
-  - `json`: Salida JSON de la entrada de información (una línea, no formateada)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada de información
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está configurado, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `información de compilación del contrato stellar`
-
-Muestra la información de compilación del contrato, si está disponible.
-
-Si el contrato tiene una entrada meta como `source_repo=github:user/repo`, este comando intentará recuperar la información de atestiguamiento del archivo WASM.
-
-**Uso:** `stellar contract info build [OPTIONS] <--wasm <WASM>|--wasm-hash <WASM_HASH>|--contract-id <CONTRACT_ID>>`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta del archivo Wasm en el sistema de archivos local. Proporciona esto O `--wasm-hash` O `--contract-id`
-- `--wasm-hash <WASM_HASH>` — Hash del blob Wasm en una red. Proporciona esto O `--wasm` O `--contract-id`
-- `--contract-id <CONTRACT_ID>` [alias: `id`] — ID/alias del contrato en una red. Proporciona esto O `--wasm-hash` O `--wasm`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar contract init`
-
-Inicializa un proyecto de contrato Soroban.
-
-Este comando creará un proyecto de espacio de trabajo Cargo y añadirá un contrato Stellar de ejemplo. El nombre del contrato puede especificarse con `--name`. Puede ejecutarse varias veces con diferentes nombres para generar múltiples contratos, y los archivos no se sobrescribirán a menos que se pase `--overwrite`.
-
-**Uso:** `stellar contract init [OPCIONES] <PROJECT_PATH>`
-
-###### **Argumentos:**
-
-- `<PROJECT_PATH>`
-
-###### **Opciones:**
-
-- `--name <NAME>` — Un flag opcional para especificar el nombre de un nuevo contrato.
-
-  Valor predeterminado: `hello-world`
-
-- `--overwrite` — Sobrescribir todos los archivos existentes.
-
-## `stellar contract inspect`
-
-⚠️ Obsoleto, usa `contract info`. Inspeccionar un archivo WASM listando funciones del contrato, metadatos, etc.
-
-**Uso:** `stellar contract inspect [OPCIONES] --wasm <WASM>`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta al binario wasm
-- `--output <OUTPUT>` — Solo salida XDR en base64
-
-  Valor predeterminado: `docs`
-
-  Valores posibles:
-
-  - `xdr-base64`: XDR de la matriz de entradas de especificaciones del contrato
-  - `xdr-base64-array`: Matriz de xdr de entradas de especificaciones del contrato
-  - `docs`: Impresión bonita de entradas de especificaciones del contrato
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar contract upload`
-
-Instalar un archivo WASM en el ledger sin crear una instancia de contrato
-
-**Uso:** `stellar contract upload [OPCIONES] --source-account <SOURCE_ACCOUNT> --wasm <WASM>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Valor por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--wasm <WASM>` — Ruta al binario wasm
-- `-i`, `--ignore-checks` — Si ignorar las comprobaciones de seguridad al desplegar contratos
-
-  Valor por defecto: `false`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-- `--fee <FEE>` — cantidad de tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Salida del costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el base64 xdr a stdout
-
-## `instalar contrato stellar`
-
-⚠️ Obsoleto, usa `contract upload`. Instalar un archivo WASM en el ledger sin crear una instancia de contrato
-
-**Uso:** `stellar contract install [OPTIONS] --source-account <SOURCE_ACCOUNT> --wasm <WASM>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…) o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--wasm <WASM>` — Ruta al binario wasm
-- `-i`, `--ignore-checks` — Si ignorar las comprobaciones de seguridad al desplegar contratos
-
-  Valor por defecto: `false`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Imprimir el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr en base64 a stdout
-
-## `invocar contrato stellar`
-
-Invocar una función de contrato
-
-Genera un "CLI implícito" para el contrato especificado sobre la marcha utilizando el esquema del contrato, que se incrusta en cada contrato de Soroban. El "slop" en este comando, todo lo que viene después de `--`, se pasa a este CLI implícito. Obtén ayuda detallada para un contrato dado:
-
-invocar contrato stellar ... -- --help
-
-**Uso:** `stellar contract invoke [OPTIONS] --id <CONTRACT_ID> --source-account <SOURCE_ACCOUNT> [-- <CONTRACT_FN_AND_ARGS>...]`
-
-###### **Argumentos:**
-
-- `<CONTRACT_FN_AND_ARGS>` — Nombre de la función como subcomando, luego argumentos para esa función como `--arg-name value`
-
-###### **Opciones:**
-
-- `--id <CONTRACT_ID>` — ID del contrato a invocar
-- `--is-view` — ⚠️ Obsoleto, usa `--send=no`. Ver el resultado simulando y no firmar ni enviar la transacción
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…) o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--send <SEND>` — Si enviar o no una transacción
-
-  Valor por defecto: `default`
-
-  Valores posibles:
-
-  - `default`: Enviar transacción si la simulación indica que hay escrituras en el ledger, eventos publicados o se requiere autenticación, de lo contrario devolver el resultado de la simulación
-  - `no`: No enviar transacción, devolver resultado de la simulación
-  - `sí`: Siempre enviar transacción
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Imprimir el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr en base64 a stdout
-
-## `optimizar contrato stellar`
-
-⚠️ Obsoleto, usa `build --optimize`. Optimizar un archivo WASM
-
-**Uso:** `stellar contract optimize [OPTIONS] --wasm <WASM>...`
-
-###### **Opciones:**
-
-- `--wasm <WASM>` — Ruta a uno o más binarios wasm
-- `--wasm-out <WASM_OUT>` — Ruta para escribir el archivo WASM optimizado (por defecto a la misma ubicación que --wasm con sufijo .optimized.wasm)
-
-## `leer contrato stellar`
-
-Imprimir el valor actual de una entrada de ledger de datos de contrato
-
-**Uso:** `stellar contract read [OPTIONS]`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Tipo de salida a generar
-
-  Valor por defecto: `string`
-
-  Valores posibles:
-
-  - `string`: Cadena
-  - `json`: Json
-  - `xdr`: XDR
-
-- `--id <CONTRACT_ID>` — ID del contrato que posee las entradas de datos. Si no se proporcionan claves, la instancia del contrato se extenderá
-
-- `--key <KEY>` — Clave de almacenamiento (solo símbolos)
-
-- `--key-xdr <KEY_XDR>` — Clave de almacenamiento (XDR codificada en base64)
-
-- `--wasm <WASM>` — Ruta al archivo Wasm del código del contrato a extender
-
-- `--wasm-hash <WASM_HASH>` — Ruta al archivo Wasm del código del contrato a extender
-
-- `--durability <DURABILITY>` — Durabilidad de la entrada de almacenamiento
-
-  Valor por defecto: `persistent`
-
-  Valores posibles:
-
-  - `persistent`: Persistente
-  - `temporary`: Temporal
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `restaurar contrato stellar`
-
-Restaurar un valor desalojado de una entrada de ledger de datos de contrato.
-
-Si no se especifican claves, el contrato en sí se restaurará.
-
-**Uso:** `stellar contract restore [OPTIONS] --source-account <SOURCE_ACCOUNT>`
-
-###### **Opciones:**
-
-- `--id <CONTRACT_ID>` — ID del contrato que posee las entradas de datos. Si no se proporcionan claves, la instancia del contrato se extenderá
-
-- `--key <KEY>` — Clave de almacenamiento (solo símbolos)
-
-- `--key-xdr <KEY_XDR>` — Clave de almacenamiento (XDR codificada en base64)
-
-- `--wasm <WASM>` — Ruta al archivo Wasm del código del contrato a extender
-
-- `--wasm-hash <WASM_HASH>` — Ruta al archivo Wasm del código del contrato a extender
-
-- `--durability <DURABILITY>` — Durabilidad de la entrada de almacenamiento
-
-  Valor por defecto: `persistent`
-
-  Valores posibles:
-
-  - `persistent`: Persistente
-  - `temporary`: Temporal
-
-- `--ledgers-to-extend <LEDGERS_TO_EXTEND>` — Número de ledgers para extender la entrada
-
-- `--ttl-ledger-only` — Solo imprimir el nuevo ledger de Tiempo de Vida
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…) o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una wallet ledger
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar de la configuración
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Imprimir el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr en base64 a stdout
-
-## `stellar doctor`
-
-Diagnosticar y solucionar incidencias en CLI y red
-
-**Uso:** `stellar doctor [OPTIONS]`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `eventos stellar`
-
-Observa la red para eventos de contratos
-
-**Uso:** `stellar events [OPTIONS]`
-
-###### **FILTROS:**
-
-- `--id <CONTRACT_IDS>` — Un conjunto de (hasta 5) IDs de contratos para filtrar eventos. Este parámetro se puede pasar varias veces, por ejemplo, `--id C123.. --id C456..`, o pasado con múltiples parámetros, por ejemplo, `--id C123 C456`.
-
-  Aunque la especificación admite múltiples objetos de filtro (es decir, combinaciones de tipo, IDs y temas), solo se puede especificar un conjunto en la línea de comandos hoy, aunque ese conjunto puede tener múltiples IDs/temas.
-
-- `--topic <TOPIC_FILTERS>` — Un conjunto de filtros de tema (hasta 5) para filtrar temas de eventos. Un filtro de tema único puede contener de 1 a 4 segmentos diferentes, separados por comas. Un asterisco (`*` carácter) indica un segmento comodín.
-
-  Además de hasta 4 segmentos posibles de filtro de tema, también se puede añadir el comodín "**", que permitirá un número flexible de temas en los eventos devueltos. El comodín "**" debe ser el último segmento en una consulta.
-
-  Si no se incluye el comodín "\*\*", solo se devolverán eventos con el número exacto de temas que el filtro dado.
-
-  **Ejemplo:** filtro de tema con dos segmentos: `--topic "AAAABQAAAAdDT1VOVEURSAA==,*"`
-
-  **Ejemplo:** dos filtros de tema con uno y dos segmentos cada uno: `--topic "AAAABQAAAAdDT1VOTE...` --topic '_,_'\`
-
-  **Ejemplo:** filtro de tema con cuatro segmentos y el comodín "**": --topic "AAAABQAAAAdDT1VOTEVSAA==,_,_,\*,**"
-
-  Ten en cuenta que todos estos filtros de tema se combinan con los IDs de contrato en un solo filtro (es decir, combinación de tipo, IDs y temas).
-
-- `--type <EVENT_TYPE>` — Especifica qué tipo de eventos de contrato mostrar
-
-  Valor predeterminado: `all`
-
-  Valores posibles: `all`, `contract`, `system`
-
-###### **Opciones:**
-
-- `--start-ledger <START_LEDGER>` — El primer número de secuencia de ledger en el rango para obtener eventos https://developers.stellar.org/docs/learn/encyclopedia/network-configuration/ledger-headers#ledger-sequence
-
-- `--cursor <CURSOR>` — El cursor correspondiente al inicio del rango de eventos
-
-- `--output <OUTPUT>` — Opciones de formato de salida para el flujo de eventos
-
-  Valor por defecto: `pretty`
-
-  Valores posibles:
-
-  - `pretty`: Salida de consola colorida y orientada al ser humano
-  - `plain`: Salida de consola orientada al ser humano sin colores
-  - `json`: Salida de consola formateada en JSON
-
-- `-c`, `--count <COUNT>` — El número máximo de eventos a mostrar (deferirse al límite definido por el servidor)
-
-  Valor predeterminado: `10`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar env`
-
-Imprime las variables de entorno
-
-Imprime en stdout en un formato que se puede usar como archivo .env. Las variables de entorno tienen precedencia sobre los valores predeterminados.
-
-Pasa un nombre para obtener el valor de una sola variable de entorno.
-
-Si no hay variables de entorno en uso, imprime los valores predeterminados.
-
-**Uso:** `stellar env [OPCIONES] [NOMBRE]`
-
-###### **Argumentos:**
-
-- `<NOMBRE>` — Nombre de la variable de entorno para obtener el valor.
-
-  Ej.: $ stellar env STELLAR_ACCOUNT
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar keys`
-
-Crear y administrar identidades, incluidas claves y direcciones
-
-**Uso:** `stellar keys <COMMAND>`
-
-###### **Subcomandos:**
-
-- `add` — Agregar una nueva identidad (keypair, ledger, almacenamiento seguro específico del sistema operativo)
-- `public-key` — Dada una identidad, devuelve su dirección (clave pública)
-- `fund` — Financiar una identidad en una red de prueba
-- `generate` — Generar una nueva identidad utilizando una frase semilla de 24 palabras La frase semilla puede almacenarse en un archivo de configuración (predeterminado) o en un almacenamiento seguro específico del sistema operativo
-- `ls` — Listar identidades
-- `rm` — Eliminar una identidad
-- `secret` — Mostrar la clave secreta de una identidad
-- `use` — Establecer la identidad predeterminada que se utilizará en todos los comandos. Esto te permite omitir `--source-account` o establecer una variable de entorno, reutilizando este valor en todos los comandos que lo requieran
-- `unset` — Eliminar la identidad clave predeterminada definida previamente con `keys use <identity>`
-
-## `stellar keys add`
-
-Agregar una nueva identidad (keypair, ledger, almacenamiento seguro específico del sistema operativo)
-
-**Uso:** `stellar keys add [OPTIONS] <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Nombre de la identidad
-
-###### **Opciones:**
-
-- `--secret-key` — ⚠️ Obsoleto, usa `--secure-store`. Ingresa la clave secreta (S) cuando se solicite
-
-- `--seed-phrase` — ⚠️ Obsoleto, usa `--secure-store`. Ingresa la clave usando frase Seed de 12-24 palabras
-
-- `--secure-store` — Guarda la nueva clave en la tienda de credenciales segura de tu sistema operativo.
-
-  En Mac usa Keychain, en Windows es Secure Store Service, y en plataformas \*nix utiliza una combinación de keyutils del kernel y el servicio secreto basado en DBus.
-
-  Esto solo admite frases Seed por ahora.
-
-- `--public-key <PUBLIC_KEY>` — Agregar una clave pública, ed25519 o cuenta multiplexada, por ejemplo, G1.., M2..
-
-- `--overwrite` — Sobrescribir una identidad existente si ya existe
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global está siempre activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar keys public-key`
-
-Dada una identidad, devuelve su dirección (clave pública)
-
-**Uso:** `stellar keys public-key [OPTIONS] <NAME>`
-
-**Alias del comando:** `address`
-
-###### **Argumentos:**
-
-- `<NAME>` — Nombre de la identidad a buscar, se utiliza la identidad de prueba predeterminada si no se proporciona
-
-###### **Opciones:**
-
-- `--hd-path <HD_PATH>` — Si la identidad es una frase semilla, usa esta ruta hd, el valor predeterminado es 0
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar keys fund`
-
-Financiar una identidad en una red de prueba
-
-**Uso:** `stellar keys fund [OPTIONS] <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Nombre de la identidad a buscar, se utiliza la identidad de prueba predeterminada si no se proporciona
-
-###### **Opciones:**
-
-- `--hd-path <HD_PATH>` — Si la identidad es una frase semilla, usa esta ruta hd, el valor predeterminado es 0
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor RPC
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar de la configuración
-
-## `stellar keys generate`
-
-Generar una nueva identidad utilizando una frase semilla de 24 palabras La frase semilla puede almacenarse en un archivo de configuración (predeterminado) o en un almacenamiento seguro específico del sistema operativo
-
-**Uso:** `stellar keys generate [OPTIONS] <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Nombre de la identidad
-
-###### **Opciones:**
-
-- `--seed <SEED>` — Semilla opcional para usar al generar la frase semilla. De lo contrario, se generará aleatoriamente
-
-- `-s`, `--as-secret` — Mostrar la identidad generada como una clave secreta
-
-- `--secure-store` — Guarda la nueva clave en la tienda de credenciales segura de tu sistema operativo.
-
-  En Mac usa Keychain, en Windows es Secure Store Service, y en plataformas \*nix utiliza una combinación de keyutils del kernel y el servicio secreto basado en DBus.
-
-- `--hd-path <HD_PATH>` — Al generar una clave secreta, cuál `hd_path` debe usarse de la frase semilla original
-
-- `--fund` — Financiar el par de claves generado
-
-  Valor predeterminado: `false`
-
-- `--overwrite` — Sobrescribir identidad existente si ya existe
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor RPC
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar keys ls`
-
-Listar identidades
-
-**Uso:** `stellar keys ls [OPTIONS]`
-
-###### **Opciones:**
-
-- `-l`, `--long`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar keys rm`
-
-Eliminar una identidad
-
-**Uso:** `stellar keys rm [OPTIONS] <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Identidad a eliminar
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, volviendo a `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar keys secret`
-
-Mostrar la clave secreta de una identidad
-
-**Uso:** `stellar keys secret [OPTIONS] <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Nombre de la identidad a buscar, se utiliza la identidad de prueba predeterminada
-
-###### **Opciones:**
-
-- `--phrase` — Mostrar frase semilla en lugar de clave privada
-- `--hd-path <HD_PATH>` — Si la identidad es una frase semilla, usa esta ruta hd, el valor predeterminado es 0
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar keys use`
-
-Establecer la identidad predeterminada que se utilizará en todos los comandos. Esto te permite omitir `--source-account` o establecer una variable de entorno, reutilizando este valor en todos los comandos que lo requieran
-
-**Uso:** `stellar keys use [OPTIONS] <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Establecer el nombre de la red predeterminada
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar keys unset`
-
-Eliminar la identidad clave predeterminada definida previamente con `keys use <identity>`
-
-**Uso:** `stellar keys unset [OPTIONS]`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar network`
-
-Configurar la conexión a redes
-
-**Uso:** `stellar network <COMMAND>`
-
-###### **Subcomandos:**
-
-- `add` — Agregar una nueva red
-- `rm` — Eliminar una red
-- `ls` — Listar redes
-- `use` — Establecer la red predeterminada que se utilizará en todos los comandos. Esto te permite omitir `--network` o establecer una variable de entorno, reutilizando este valor en todos los comandos que lo requieran
-- `health` — Obtener el estado del RPC configurado
-- `info` — Comprueba la salud del RPC configurado
-- `settings` — Obtener los ajustes de configuración de la red
-- `unset` — Eliminar la red predeterminada definida previamente con `network use <network>`
-
-## `stellar network add`
-
-Agregar una nueva red
-
-**Uso:** `stellar network add [OPTIONS] --rpc-url <RPC_URL> --network-passphrase <NETWORK_PASSPHRASE> <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Nombre de la red
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) opcional para incluir en solicitudes al RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de la red para firmar la transacción enviada al servidor rpc
-
-## `stellar network rm`
-
-Eliminar una red
-
-**Uso:** `stellar network rm [OPTIONS] <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Red a eliminar
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar network ls`
-
-Listar redes
-
-**Uso:** `stellar network ls [OPTIONS]`
-
-###### **Opciones:**
-
-- `-l`, `--long` — Obtén más información sobre las redes
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, utiliza `$XDG_CONFIG_HOME/stellar` si está definido, y en caso contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `usar red stellar`
-
-Establece la red por defecto que se usará en todos los comandos. Esto te permite omitir `--network` o configurar una variable de entorno, reutilizando este valor en todos los comandos que lo requieran
-
-**Uso:** `stellar network use [OPTIONS] <NAME>`
-
-###### **Argumentos:**
-
-- `<NAME>` — Establece el nombre de la red por defecto
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está configurado, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar network health`
-
-Obtener el estado del RPC configurado
-
-**Uso:** `stellar network health [OPTIONS]`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `text`
-
-  Valores posibles:
-
-  - `text`: Salida de texto con el estado de salud de la red
-  - `json`: Resultado JSON de la solicitud RPC
-  - `json-formatted`: Salida JSON formateada (multilínea) de la solicitud RPC
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar network info`
-
-Comprueba la salud del RPC configurado
-
-**Uso:** `stellar network info [OPTIONS]`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `text`
-
-  Valores posibles:
-
-  - `text`: Salida en texto de la información de la red
-  - `json`: Resultado JSON de la solicitud RPC
-  - `json-formatted`: Salida JSON formateada (multilínea) de la solicitud RPC
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar network settings`
-
-Obtener los ajustes de configuración de la red
-
-**Uso:** `stellar network settings [OPTIONS]`
-
-###### **Opciones:**
-
-- `--internal` — Incluir ajustes de configuración internos que no se pueden actualizar y son mantenidos internamente por la red
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `json`
-
-  Posibles valores:
-
-  - `xdr`: XDR (tipo `ConfigUpgradeSet`)
-  - `json`: JSON, XDR-JSON del tipo XDR `ConfigUpgradeSet`
-  - `json-formatted`: Formato JSON, XDR-JSON del tipo XDR `ConfigUpgradeSet`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar network unset`
-
-Eliminar la red predeterminada definida previamente con `network use <network>`
-
-**Uso:** `stellar network unset [OPTIONS]`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `contenedor stellar`
-
-Iniciar redes locales en contenedores
-
-**Uso:** `stellar container <COMMAND>`
-
-###### **Subcomandos:**
-
-- `logs` — Obtener registros de un contenedor de red en ejecución
-- `start` — Iniciar un contenedor que ejecute un nodo Stellar, RPC, API y friendbot (grifo)
-- `stop` — Detener un contenedor de red iniciado con `stellar container start`
-
-## `registros de contenedor stellar`
-
-Obtener registros de un contenedor de red en ejecución
-
-**Uso:** `stellar container logs [OPTIONS] [NAME]`
-
-###### **Argumentos:**
-
-- `<NAME>` — Contenedor para obtener registros
-
-  Valor por defecto: `local`
-
-###### **Opciones:**
-
-- `-d`, `--docker-host <DOCKER_HOST>` — Argumento opcional para sobreescribir el host de Docker por defecto. Esto es útil cuando usas una ruta de host de Docker no estándar para tu runtime de contenedor compatible con Docker, por ejemplo, Docker Desktop por defecto está en $HOME/.docker/run/docker.sock en lugar de /var/run/docker.sock
-
-## `iniciar contenedor stellar`
-
-Iniciar un contenedor que ejecute un nodo Stellar, RPC, API y friendbot (grifo).
-
-`iniciar contenedor stellar NETWORK [OPCIONES]`
-
-Por defecto, al iniciar un contenedor de testnet, sin ningún argumento opcional, se ejecutará el equivalente al siguiente comando de Docker:
-
-`docker run --rm -p 8000:8000 --name stellar stellar/quickstart:testing --testnet --enable rpc,horizon`
-
-**Uso:** `stellar container start [OPTIONS] [NETWORK]`
-
-###### **Argumentos:**
-
-- `<NETWORK>` — Red a iniciar. El valor por defecto es `local`
-
-  Valores posibles: `local`, `testnet`, `futurenet`, `pubnet`
-
-###### **Opciones:**
-
-- `-d`, `--docker-host <DOCKER_HOST>` — Argumento opcional para sobreescribir el host de Docker por defecto. Esto es útil cuando usas una ruta de host de Docker no estándar para tu runtime de contenedor compatible con Docker, por ejemplo, Docker Desktop por defecto está en $HOME/.docker/run/docker.sock en lugar de /var/run/docker.sock
-
-- `--name <NAME>` — Argumento opcional para especificar el nombre del contenedor
-
-- `-l`, `--limits <LIMITS>` — Argumento opcional para especificar los límites solo para la red local
-
-- `-p`, `--ports-mapping <PORTS_MAPPING>` — Argumento para especificar el mapeo `HOST_PORT:CONTAINER_PORT`
-
-  Valor por defecto: `8000:8000`
-
-- `-t`, `--image-tag-override <IMAGE_TAG_OVERRIDE>` — Argumento opcional para sobreescribir la etiqueta de imagen de Docker por defecto para la red dada
-
-- `--protocol-version <PROTOCOL_VERSION>` — Argumento opcional para especificar la versión del protocolo solo para la red local
-
-## `detener contenedor stellar`
-
-Detener un contenedor de red iniciado con `stellar container start`
-
-**Uso:** `stellar container stop [OPTIONS] [NAME]`
-
-###### **Argumentos:**
-
-- `<NAME>` — Contenedor a detener
-
-  Valor por defecto: `local`
-
-###### **Opciones:**
-
-- `-d`, `--docker-host <DOCKER_HOST>` — Argumento opcional para sobreescribir el host de Docker por defecto. Esto es útil cuando usas una ruta de host de Docker no estándar para tu runtime de contenedor compatible con Docker, por ejemplo, Docker Desktop por defecto está en $HOME/.docker/run/docker.sock en lugar de /var/run/docker.sock
-
-## `stellar config`
-
-Administrar la configuración del CLI
-
-**Uso:** `stellar config <COMMAND>`
-
-###### **Subcomandos:**
-
-- `migrate` — Migrar la configuración local al directorio global
-- `dir` — Mostrar el directorio de configuración global
-
-## `stellar config migrate`
-
-Migrar la configuración local al directorio global
-
-**Uso:** `stellar config migrate [OPTIONS]`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está configurado, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `stellar config dir`
-
-Mostrar el directorio de configuración global.
-
-La ubicación dependerá de cómo esté configurado tu sistema.
-
-- Busca la variable de entorno `XDG_CONFIG_HOME`. Si está definida, se utilizará `$XDG_CONFIG_HOME/stellar`. - Si no está definida, se usa por defecto `$HOME/.config`. - Puede ser sobrescrita mediante la opción `--config-dir`.
-
-**Uso:** `stellar config dir [OPTIONS]`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-## `imagen stellar`
-
-Descargar una imagen de un ledger desde un archivo
-
-**Uso:** `stellar snapshot <COMMAND>`
-
-###### **Subcomandos:**
-
-- `create` — Crear una imagen de ledger utilizando un archivo de historial
-- `merge` — Combinar varias imágenes del ledger en un único archivo de imagen
-
-## `crear imagen stellar`
-
-Crear una imagen de ledger utilizando un archivo de historial.
-
-Los filtros (dirección, wasm-hash) especifican qué entradas de ledger incluir.
-
-Las direcciones de cuenta incluyen la cuenta y las líneas de confianza.
-
-Las direcciones de contrato incluyen el wasm relacionado y los datos del contrato.
-
-Si un contrato es un contrato de activo Stellar, incluye la cuenta del emisor del activo y las líneas de confianza, pero no incluye todas las líneas de confianza de otras cuentas que sostienen el activo. Para incluirlas, especifica las direcciones de las cuentas relevantes.
-
-Cualquier ID de contrato no válido pasado como `--address` será ignorado.
-
-**Uso:** `stellar snapshot create [OPTIONS]`
-
-###### **Opciones de filtro:**
-
-- `--address <ADDRESS>` — Dirección/alias de cuenta o contrato a incluir en la imagen
-- `--wasm-hash <WASM_HASHES>` — Hashes de WASM a incluir en la imagen
-
-###### **Opciones:**
-
-- `--ledger <LEDGER>` — El número de secuencia de ledger a tomar la imagen. Por defecto, es el ledger archivado más reciente
-
-- `--output <OUTPUT>` — Formato del archivo de salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles: `json`
-
-- `--out <OUT>` — Ruta de salida donde se escribirá la imagen
-
-  Valor por defecto: `snapshot.json`
-
-###### **Opciones (Archivo):**
-
-- `--archive-url <ARCHIVE_URL>` — URL de archivo
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar snapshot merge`
-
-Combinar múltiples imágenes del ledger en un solo archivo de imagen.
-
-Cuando la misma clave del ledger aparece en varias imágenes, la entrada de la última imagen en la lista de argumentos tiene prioridad. Metadatos (protocol_version, sequence_number, timestamp, etc.) se toman de la última imagen.
-
-Ejemplo: stellar snapshot merge A.json B.json --out merged.json
-
-Esto permite combinar imágenes de diferentes implementaciones de contratos o imágenes editadas manualmente sin regenerarlas desde cero.
-
-**Uso:** `stellar snapshot merge [OPTIONS] <SNAPSHOTS> <SNAPSHOTS>...`
-
-###### **Argumentos:**
-
-- `<SNAPSHOTS>` — Archivos de imagen para fusionar (se requieren al menos 2)
-
-###### **Opciones:**
-
-- `-o`, `--out <OUT>` — Ruta de salida para la imagen fusionada
-
-  Valor predeterminado: `snapshot.json`
-
-## `stellar tx`
-
-Firmar, simular y enviar transacciones
-
-**Uso:** `stellar tx <COMMAND>`
-
-###### **Subcomandos:**
-
-- `update` — Actualizar la transacción
-- `edit` — Edita un sobre de transacción desde stdin. Este comando respeta las variables de entorno `STELLAR_EDITOR`, `EDITOR` y `VISUAL`, en ese orden
-- `hash` — Calcular el hash de un sobre de transacción
-- `new` — Crear una nueva transacción
-- `operation` — Manipular las operaciones en una transacción, incluyendo agregar nuevas operaciones
-- `send` — Enviar un sobre de transacción a la red
-- `sign` — Firmar un sobre de transacción añadiendo la firma al sobre
-- `simulate` — Simular un sobre de transacción desde stdin
-- `fetch` — Obtener una transacción de la red por hash. Si no se pasa subcomando, se devolverá el sobre de la transacción.
-- `decode` — Decodifica un sobre de transacción de XDR a JSON
-- `encode` — Codifica un sobre de transacción de JSON a XDR
-
-## `stellar tx update`
-
-Actualizar la transacción
-
-**Uso:** `stellar tx update <COMMAND>`
-
-###### **Subcomandos:**
-
-- `sequence-number` — Editar el número de secuencia en una transacción
-
-## `stellar tx update sequence-number`
-
-Editar el número de secuencia en una transacción
-
-**Uso:** `stellar tx update sequence-number <COMMAND>`
-
-**Alias del comando:** `seq-num`
-
-###### **Subcomandos:**
-
-- `next` — Obtener el seq-num de la cuenta fuente y aumentarlo para la tx dada
-
-## `stellar tx update sequence-number next`
-
-Obtener el seq-num de la cuenta fuente y aumentarlo para la tx dada
-
-**Uso:** `stellar tx update sequence-number next [OPTIONS]`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx edit`
-
-Edita un sobre de transacción desde stdin. Este comando respeta las variables de entorno `STELLAR_EDITOR`, `EDITOR` y `VISUAL`, en ese orden.
-
-Ejemplo: Comenzar una nueva sesión de edición
-
-$ stellar tx edit
-
-Ejemplo: Canaliza un sobre de transacción XDR
-
-$ stellar tx new manage-data --data-name hola --build-only | stellar tx edit
-
-**Uso:** `stellar tx edit`
-
-## `hash de tx stellar`
-
-Calcula el hash de un sobre de transacción
-
-**Uso:** `stellar tx hash [OPCIONES] [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar tx new`
-
-Crea una nueva transacción
-
-**Uso:** `stellar tx new <COMANDO>`
-
-###### **Subcomandos:**
-
-- `account-merge` — Transferir saldo XLM a otra cuenta y eliminar la cuenta origen
-- `begin-sponsoring-future-reserves` — Comenzar a patrocinar reservas futuras para otra cuenta
-- `bump-sequence` — Incrementar número de secuencia para invalidar transacciones anteriores
-- `change-trust` — Crear, actualizar o eliminar una trustline
-- `claim-claimable-balance` — Reclamar un claimable balance mediante su balance ID
-- `clawback` — Recuperar un asset de una cuenta
-- `clawback-claimable-balance` — Recuperar un saldo reclamable por su ID de saldo
-- `create-account` — Crear y financiar una cuenta nueva
-- `create-claimable-balance` — Crear un claimable balance que puede ser reclamado por cuentas especificadas
-- `create-passive-sell-offer` — Crear una oferta pasiva de venta en el Stellar DEX
-- `end-sponsoring-future-reserves` — Terminar de patrocinar reservas futuras
-- `liquidity-pool-deposit` — Depositar activos en un Fondo de Liquidez
-- `liquidity-pool-withdraw` — Retirar activos de un Fondo de Liquidez
-- `manage-buy-offer` — Crear, actualizar o eliminar una oferta de compra
-- `manage-data` — Establecer, modificar o eliminar entradas de datos de la cuenta
-- `manage-sell-offer` — Crear, actualizar o eliminar una oferta de venta
-- `path-payment-strict-send` — Enviar un pago con un activo diferente usando búsqueda de rutas, especificando la cantidad a enviar
-- `path-payment-strict-receive` — Enviar un pago con un activo diferente usando búsqueda de rutas, especificando la cantidad a recibir
-- `payment` — Enviar activo a cuenta destino
-- `revoke-sponsorship` — Revocar el patrocinio de una entrada del ledger o firmante
-- `set-options` — Establecer opciones de cuenta como flags, firmantes y dominio principal
-- `set-trustline-flags` — Configurar flags de autorización y trustline para un activo
-
-## `stellar tx new account-merge`
-
-Transferir saldo XLM a otra cuenta y eliminar la cuenta origen
-
-**Uso:** `stellar tx new account-merge [OPCIONES] --source-account <SOURCE_ACCOUNT> --account <ACCOUNT>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionan las banderas `--build-only` o `--sim-only`, también se utilizará esta clave para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--account <ACCOUNT>` — Cuenta muxed con la cual fusionar, e.g. `GBX...`, 'MBX...'
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Salida el costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar tx new begin-sponsoring-future-reserves`
-
-Comenzar a patrocinar reservas futuras para otra cuenta
-
-**Uso:** `stellar tx new begin-sponsoring-future-reserves [OPTIONS] --source-account <SOURCE_ACCOUNT> --sponsored-id <SPONSORED_ID>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionan las banderas `--build-only` o `--sim-only`, también se utilizará esta clave para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--sponsored-id <SPONSORED_ID>` — Cuenta que será patrocinada
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Salida el costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar tx new bump-sequence`
-
-Incrementar número de secuencia para invalidar transacciones anteriores
-
-**Uso:** `stellar tx new bump-sequence [OPCIONES] --source-account <SOURCE_ACCOUNT> --bump-to <BUMP_TO>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionan las banderas `--build-only` o `--sim-only`, también se utilizará esta clave para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--bump-to <BUMP_TO>` — Número de secuencia al que aumentar
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, volviendo a `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Salida el costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar tx new change-trust`
-
-Crear, actualizar o eliminar una trustline
-
-**Uso:** `stellar tx new change-trust [OPCIONES] --source-account <SOURCE_ACCOUNT> --line <LINE>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionan las banderas `--build-only` o `--sim-only`, también se utilizará esta clave para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--line <LINE>`
-- `--limit <LIMIT>` — Límite para la línea de confianza, 0 para eliminar la línea de confianza
-
-  Valor por defecto: `9223372036854775807`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Salida el costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase clave de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new claim-claimable-balance`
-
-Reclamar un claimable balance mediante su balance ID
-
-**Uso:** `stellar tx new claim-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --balance-id <BALANCE_ID>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si NO se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es el camino `0`
-- `--hd-path <HD_PATH>` — Si usas frase Seed para firmar, define cuál camino jerárquico determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--balance-id <BALANCE_ID>` — ID del balance reclammable a reclamar (cadena hex de 64 caracteres)
-
-###### **Opciones (Global):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new clawback`
-
-Recuperar un asset de una cuenta
-
-**Uso:** `stellar tx new clawback [OPCIONES] --source-account <SOURCE_ACCOUNT> --from <FROM> --asset <ASSET> --amount <AMOUNT>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source` Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…) o una frase semilla (--source "kite urban…"). Si no se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--from <FROM>` — Cuenta de la cual recuperar los assets, por ejemplo `GBX...`
-- `--asset <ASSET>` — Asset a recuperar
-- `--amount <AMOUNT>` — Cantidad del asset a recuperar, en stroops. 1 stroop = 0.0000001 del activo
-
-###### **Opciones (Global):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Salida del costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad extra de instrucciones al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construye la transacción y solo escribe el xdr base64 a stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, por ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar de la configuración
-
-## `stellar tx new clawback-claimable-balance`
-
-Recuperar un saldo reclamable por su ID de saldo
-
-**Uso:** `stellar tx new clawback-claimable-balance [OPCIONES] --source-account <SOURCE_ACCOUNT> --balance-id <BALANCE_ID>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source` Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…) o una frase semilla (--source "kite urban…"). Si no se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--balance-id <BALANCE_ID>` — ID del saldo reclamable a recuperar. Acepta varios formatos: - Formato API con prefijo de tipo (72 caracteres): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato hash directo (64 caracteres): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato dirección (base32): BAAMLBZI42AD52HKGIZOU7WFVZM6BPEJCLPL44QU2AT6TY3P57I5QDNYIA
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Salida del costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones adicionales al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construye la transacción y solo escribe el xdr base64 a stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase clave de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new create-account`
-
-Crear y financiar una cuenta nueva
-
-**Uso:** `stellar tx new create-account [OPCIONES] --source-account <SOURCE_ACCOUNT> --destination <DESTINO>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source` Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…) o una frase semilla (--source "kite urban…"). Si no se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--destination <DESTINATION>` — ID de la cuenta a crear, e.g. `GBX...`
-- `--starting-balance <STARTING_BALANCE>` — Saldo inicial en stroops de la cuenta, por defecto 1 XLM
-
-  Valor por defecto: `10_000_000`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Salida del costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones adicionales al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construye la transacción y solo escribe el xdr base64 a stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar varios encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase clave de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new create-claimable-balance`
-
-Crear un claimable balance que pueda ser reclamado por cuentas especificadas
-
-**Uso:** `stellar tx new create-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --amount <AMOUNT>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxada (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron las opciones de `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una wallet ledger
-
-- `--asset <ASSET>` — Activo que se almacenará en el ClaimableBalanceEntry
-
-  Valor predeterminado: `native`
-
-- `--amount <AMOUNT>` — Cantidad de activo a almacenar en la entrada, en stroops. 1 stroop = 0.0000001 del activo
-
-- `--claimant <CLAIMANTS>` — Reclamantes del claimable balance. Formato: account_id o account_id:predicate_json Puede especificarse varias veces para múltiples reclamantes.
-
-  Ejemplos:
-
-  - `--claimant alice (incondicional)` - `--claimant 'bob:{"before_absolute_time":"1735689599"}'` - `--claimant 'charlie:{"and":[{"before_absolute_time":"1735689599"},{"before_relative_time":"3600"}]}'`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Salida del costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y escribir solo el xdr base64 a stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase clave de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar de la configuración
-
-## `stellar tx new create-passive-sell-offer`
-
-Crear una oferta pasiva de venta en el Stellar DEX
-
-**Uso:** `stellar tx new create-passive-sell-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxada (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con una clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--selling <SELLING>` — Activo a vender
-- `--buying <BUYING>` — Activo a comprar
-- `--amount <AMOUNT>` — Cantidad del activo a vender para ofrecer, en stroops. 1 stroop = 0.0000001 del activo (por ej. 1 XLM = `10_000_000` stroops)
-- `--price <PRICE>` — Precio de 1 unidad del activo a vender en términos del activo a comprar como "numerador:denominador" (ej., "1:2" significa 0.5)
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Salida del costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y escribir solo el xdr base64 a stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red para usar de la configuración
-
-## `stellar tx new end-sponsoring-future-reserves`
-
-Terminar de patrocinar reservas futuras
-
-**Uso:** `stellar tx new end-sponsoring-future-reserves [OPTIONS] --source-account <SOURCE_ACCOUNT>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si no se proporcionan las flags `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = <b>0,0000001</b> xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Salida del costo de la ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr base64 a stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red para usar de la configuración
-
-## `stellar tx new liquidity-pool-deposit`
-
-Depositar activos en un Fondo de Liquidez
-
-**Uso:** `stellar tx new liquidity-pool-deposit [OPTIONS] --source-account <SOURCE_ACCOUNT> --liquidity-pool-id <LIQUIDITY_POOL_ID> --max-amount-a <MAX_AMOUNT_A> --max-amount-b <MAX_AMOUNT_B>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…) o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una wallet ledger
-
-- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — ID del Fondo de Liquidez al que depositar
-
-- `--max-amount-a <MAX_AMOUNT_A>` — Cantidad máxima del primer activo a depositar, en stroops
-
-- `--max-amount-b <MAX_AMOUNT_B>` — Cantidad máxima del segundo activo a depositar, en stroops
-
-- `--min-price <MIN_PRICE>` — Precio mínimo para el primer activo en términos del segundo activo como "numerador:denominador" (p.ej., "1:2" significa 0.5)
-
-  Valor predeterminado: `1:1`
-
-- `--max-price <MAX_PRICE>` — Precio máximo para el primer activo en términos del segundo activo como "numerador:denominador" (p.ej., "1:2" significa 0.5)
-
-  Valor predeterminado: `1:1`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = <b>0,0000001</b> xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Salida del costo de la ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr base64 a stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar de la configuración
-
-## `stellar tx new liquidity-pool-withdraw`
-
-Retirar activos de un Fondo de Liquidez
-
-**Uso:** `stellar tx new liquidity-pool-withdraw [OPTIONS] --source-account <SOURCE_ACCOUNT> --liquidity-pool-id <LIQUIDITY_POOL_ID> --amount <AMOUNT> --min-amount-a <MIN_AMOUNT_A> --min-amount-b <MIN_AMOUNT_B>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si no se proporcionan las flags `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — ID del Fondo de Liquidez del que retirar
-- `--amount <AMOUNT>` — Cantidad de participaciones del fondo a retirar, en stroops
-- `--min-amount-a <MIN_AMOUNT_A>` — Cantidad mínima del primer activo a recibir, en stroops
-- `--min-amount-b <MIN_AMOUNT_B>` — Cantidad mínima del segundo activo a recibir, en stroops
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = <b>0,0000001</b> xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Salida del costo de la ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr base64 a stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red para usar de la configuración
-
-## `stellar tx new manage-buy-offer`
-
-Crear, actualizar o eliminar una oferta de compra
-
-**Uso:** `stellar tx new manage-buy-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…) o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--selling <SELLING>` — Activo a vender
-- `--buying <BUYING>` — Activo a comprar
-- `--amount <AMOUNT>` — Cantidad del activo a comprar para adquirir, en stroops. 1 stroop = 0.0000001 del activo (ej. 1 XLM = `10_000_000` stroops). Usa `0` para eliminar la oferta
-- `--price <PRICE>` — Precio de 1 unidad del activo a comprar en términos del activo a vender como "numerador:denominador" (ej., "1:2" significa 0.5)
-- `--offer-id <OFFER_ID>` — ID de la oferta. Si es 0, creará una nueva oferta. De lo contrario, actualizará la oferta existente
-
-  Valor por defecto: `0`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = <b>0,0000001</b> xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Imprime el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el xdr en base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Punto de conexión del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new manage-data`
-
-Establecer, modificar o eliminar entradas de datos de la cuenta
-
-**Uso:** `stellar tx new manage-data [OPCIONES] --source-account <SOURCE_ACCOUNT> --data-name <DATA_NAME>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es el camino `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase Seed para firmar, establece qué ruta determinista jerárquica usar, p.ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--data-name <DATA_NAME>` — Cadena de hasta 64 bytes de largo. Si este es un nuevo nombre, añadirá el par nombre/valor dado a la cuenta. Si este nombre ya está presente, entonces el valor asociado será modificado
-- `--data-value <DATA_VALUE>` — Cadena hex de hasta 64 bytes de largo. Si no está presente, entonces se eliminará el nombre existente. Si está presente, entonces este valor se establecerá en el `DataEntry`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Mostrar costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new manage-sell-offer`
-
-Crear, actualizar o eliminar una oferta de venta
-
-**Uso:** `stellar tx new manage-sell-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se utilizará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--selling <SELLING>` — Activo a vender
-- `--buying <BUYING>` — Activo a comprar
-- `--amount <AMOUNT>` — Cantidad del activo a vender para ofrecer, en stroops. 1 stroop = 0.0000001 del activo (ej. 1 XLM = `10_000_000` stroops). Usa `0` para eliminar la oferta
-- `--price <PRICE>` — Precio de 1 unidad del activo a vender en términos del activo a comprar como "numerador:denominador" (ej., "1:2" significa 0.5)
-- `--offer-id <OFFER_ID>` — ID de la oferta. Si es 0, creará una nueva oferta. De lo contrario, actualizará la oferta existente
-
-  Valor por defecto: `0`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0,0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Salida del costo de ejecución a stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simular
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrolla la transacción y solo escribe el xdr en base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar de la configuración
-
-## `stellar tx new path-payment-strict-send`
-
-Enviar un pago con un activo diferente usando búsqueda de rutas, especificando la cantidad a enviar
-
-**Uso:** `stellar tx new path-payment-strict-send [OPTIONS] --source-account <SOURCE_ACCOUNT> --send-asset <SEND_ASSET> --send-amount <SEND_AMOUNT> --destination <DESTINATION> --dest-asset <DEST_ASSET> --dest-min <DEST_MIN>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde donde se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase semilla (--source "kite urban…"). Si no se proporcionaron las flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--send-asset <SEND_ASSET>` — Activo a enviar (pagar con)
-- `--send-amount <SEND_AMOUNT>` — Cantidad del activo a enviar a deducir de la cuenta del emisor, en stroops. 1 stroop = 0.0000001 del activo (ej. 1 XLM = `10_000_000` stroops)
-- `--destination <DESTINATION>` — Cuenta que recibe el pago
-- `--dest-asset <DEST_ASSET>` — Activo que recibirá el destinatario
-- `--dest-min <DEST_MIN>` — Cantidad mínima del activo destino que la cuenta destinataria puede recibir. La operación fallará si esta cantidad no puede ser cumplida
-- `--path <PATH>` — Lista de activos intermedios para la ruta de pago, separados por comas (hasta 5 activos). Cada activo debe tener el formato 'code:issuer' o 'native' para XLM
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — cantidad de comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor por defecto: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción.
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar de la configuración
-
-## `stellar tx new path-payment-strict-receive`
-
-Enviar un pago con un activo diferente usando búsqueda de rutas, especificando la cantidad a recibir
-
-**Uso:** `stellar tx new path-payment-strict-receive [OPTIONS] --source-account <SOURCE_ACCOUNT> --send-asset <SEND_ASSET> --send-max <SEND_MAX> --destination <DESTINATION> --dest-asset <DEST_ASSET> --dest-amount <DEST_AMOUNT>`
-
-###### **Opciones:**
-
-- Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es el camino `0` `--hd-path <HD_PATH>` — Si usas frase Seed para firmar, define cuál camino jerárquico determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una wallet ledger
-- `--send-asset <SEND_ASSET>` — Activo a enviar (pagar con)
-- `--send-max <SEND_MAX>` — Cantidad máxima del activo a enviar a deducir de la cuenta del emisor, en stroops. 1 stroop = 0.0000001 del activo (ej. 1 XLM = `10_000_000` stroops)
-- `--destination <DESTINATION>` — Cuenta que recibe el pago
-- `--dest-asset <DEST_ASSET>` — Activo que recibirá el destinatario
-- `--dest-amount <DEST_AMOUNT>` — Cantidad exacta del activo destino que la cuenta destinataria recibirá, en stroops. 1 stroop = 0.0000001 del activo
-- `--path <PATH>` — Lista de activos intermedios para la ruta de pago, separados por comas (hasta 5 activos). Cada activo debe tener el formato 'code:issuer' o 'native' para XLM
-
-###### **Opciones (Globales):**
-
-- Si NO se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final.
-- En ese caso, intentar firmar con clave pública fallará `--global` — ⚠️ Obsoleto: la configuración global siempre está activa `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración.
-
-###### **Opciones (RPC):**
-
-- En ese caso, intentar firmar con clave pública fallará `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-
-  `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración.
-
-- Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, volviendo a `~/.config/stellar` en caso contrario.
-
-- Contiene archivos de configuración, alias y otros ajustes persistentes
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en almacenamiento seguro del SO.
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…").
-
-- Si NO se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final.
-
-## `stellar tx new payment`
-
-Enviar activo a cuenta destino
-
-**Uso:** `stellar tx new payment [OPTIONS] --source-account <SOURCE_ACCOUNT> --destination <DESTINATION> --amount <AMOUNT>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase semilla (--sign-with-key "kite urban…"). Si usas frase semilla, `--hd-path` por defecto es la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si usas una frase semilla para firmar, establece qué ruta jerárquica determinista usar, ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una wallet ledger
-
-- `--destination <DESTINATION>` — Cuenta a la que enviar, por ejemplo `GBX...`
-
-- `--asset <ASSET>` — Activo a enviar, predeterminado nativo, es decir. XLM
-
-  Valor por defecto: `native`
-
-- `--amount <AMOUNT>` — Cantidad del activo mencionado a enviar, en stroops. 1 stroop = 0.0000001 del activo (ej. 1 XLM = `10_000_000` stroops)
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new revoke-sponsorship`
-
-Revocar patrocinio de una entrada del ledger o firmante
-
-**Uso:** `stellar tx new revoke-sponsorship [OPTIONS] --source-account <SOURCE_ACCOUNT> --account-id <ACCOUNT_ID>`
-
-###### **Opciones:**
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…").
-- Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, volviendo a `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en almacenamiento seguro del SO.
-- Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es el camino `0` `--hd-path <HD_PATH>` — Si usas frase Seed para firmar, define cuál camino jerárquico determinista usar, p. ej. `m/44'/148'/{hd_path}`.
-- Ejemplo: `--hd-path 1`.
-- Por defecto: `0`
-- `--account-id <ACCOUNT_ID>` — ID de cuenta (requerido para todos los tipos de patrocinio)
-- `--asset <ASSET>` — Activo para patrocinio de trustline (formato: CODE:ISSUER)
-- `--data-name <DATA_NAME>` — Nombre de dato para patrocinio de entrada de datos
-- `--offer-id <OFFER_ID>` — ID de oferta para patrocinio de oferta
-- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — ID del pool para patrocinio de fondos de liquidez. Acepta múltiples formatos: - Formato API con prefijo de tipo (72 caracteres): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de hash directo (64 caracteres): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de dirección (base32): LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
-- `--claimable-balance-id <CLAIMABLE_BALANCE_ID>` — ID de balance reclamable para patrocinio de balance reclamable. Acepta múltiples formatos: - Formato API con prefijo de tipo (72 caracteres): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de hash directo (64 caracteres): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de dirección (base32): BAAMLBZI42AD52HKGIZOU7WFVZM6BPEJCLPL44QU2AT6TY3P57I5QDNYIA
-- `--signer-key <SIGNER_KEY>` — Clave del firmante para patrocinio de firmante
-
-###### **Opciones (Globales):**
-
-- Si NO se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final.
-- En ese caso, intentar firmar con clave pública fallará `--global` — ⚠️ Obsoleto: la configuración global siempre está activa `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración.
-
-###### **Opciones (RPC):**
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org `--sign-with-ledger` — Firmar con una ledger wallet
-
-  `--fee <FEE>` — cantidad de comisión para la transacción, en stroops.
-
-- 1 stroop = 0.0000001 xlm
-
-- Valor por defecto: `100`
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--rpc-url <RPC_URL>` — Punto de conexión del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new set-options`
-
-Establecer opciones de cuenta como flags, firmantes y dominio principal
-
-**Uso:** `stellar tx new set-options [OPTIONS] --source-account <SOURCE_ACCOUNT>`
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta de origen de la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si se usa Seed phrase, `--hd-path` predetermina a la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una Seed phrase para firmar, establece qué ruta jerárquica determinista usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--inflation-dest <INFLATION_DEST>` — Cuenta del destino de inflación
-- `--master-weight <MASTER_WEIGHT>` — Un número del 0-255 (inclusive) que representa el peso de la clave maestra. Si el peso de la clave maestra se actualiza a 0, se desactiva efectivamente
-- `--low-threshold <LOW_THRESHOLD>` — Un número del 0-255 (inclusive) que representa el umbral que esta cuenta establece en todas las operaciones que realiza que tienen un umbral bajo. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
-- `--med-threshold <MED_THRESHOLD>` — Un número del 0-255 (inclusive) que representa el umbral que esta cuenta establece en todas las operaciones que realiza que tienen un umbral medio. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
-- `--high-threshold <HIGH_THRESHOLD>` — Un número del 0-255 (inclusive) que representa el umbral que esta cuenta establece en todas las operaciones que realiza que tienen un umbral alto. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
-- `--home-domain <HOME_DOMAIN>` — Establece el dominio de origen de una cuenta. Ver https://developers.stellar.org/docs/learn/encyclopedia/network-configuration/federation
-- `--signer <SIGNER>` — Añadir, actualizar o eliminar un firmante de una cuenta
-- `--signer-weight <SIGNER_WEIGHT>` — El peso del firmante es un número del 0-255 (inclusive). El firmante se elimina si el peso es 0
-- `--set-required` — Cuando se habilita, un emisor debe aprobar una cuenta antes de que esta cuenta pueda poseer su activo. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-required-0x1
-- `--set-revocable` — Cuando se habilita, un emisor puede revocar la autorización de una línea de confianza existente, congelando así el activo que posee una cuenta. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-revocable-0x2
-- `--set-clawback-enabled` — Habilita a la cuenta emisora a recuperar (quemar) todo el activo. https://developers.stellar.org/docs/tokens/control-asset-access#clawback-enabled-0x8
-- `--set-immutable` — Con esta configuración, ninguno de los otros flags de autorización (`AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`) puede ser configurado, y la cuenta emisora no puede ser fusionada. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-immutable-0x4
-- `--clear-required`
-- `--clear-revocable`
-- `--clear-immutable`
-- `--clear-clawback-enabled`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, de lo contrario utiliza `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes.
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx new set-trustline-flags`
-
-Configurar flags de autorización y trustline para un activo
-
-**Uso:** `stellar tx new set-trustline-flags [OPTIONS] --source-account <SOURCE_ACCOUNT> --trustor <TRUSTOR> --asset <ASSET>`
-
-###### **Opciones:**
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…").
-- Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, volviendo a `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en almacenamiento seguro del SO.
-- Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es el camino `0` `--hd-path <HD_PATH>` — Si usas frase Seed para firmar, define cuál camino jerárquico determinista usar, p. ej. `m/44'/148'/{hd_path}`.
-- Ejemplo: `--hd-path 1`.
-- Por defecto: `0`
-- `--trustor <TRUSTOR>` — Cuenta a la que establecer flags de confianza, por ejemplo `GBX...`, o alias, o cuenta muxed, `M123...`
-- `--asset <ASSET>` — Activo para establecer flags de confianza
-- `--set-authorize` — Significa autorización completa permitiendo a una cuenta transaccionar libremente con el activo para realizar y recibir pagos y realizar pedidos
-- `--set-authorize-to-maintain-liabilities` — Denota una autorización limitada que permite a una cuenta mantener los pedidos actuales pero no transaccionar de otra manera con el activo
-- `--set-trustline-clawback-enabled` — Habilita a la cuenta emisora a recuperar (quemar) todo el activo. Consulta nuestra sección sobre Clawbacks: https://developers.stellar.org/docs/learn/encyclopedia/transactions-specialized/clawbacks
-- `--clear-authorize`
-- `--clear-authorize-to-maintain-liabilities`
-- `--clear-trustline-clawback-enabled`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, de lo contrario utiliza `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes.
-
-###### **Opciones (RPC):**
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org `--sign-with-ledger` — Firmar con una ledger wallet
-
-  `--fee <FEE>` — cantidad de comisión para la transacción, en stroops.
-
-- 1 stroop = 0.0000001 xlm
-
-- Valor por defecto: `100`
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de la red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation`
-
-Manipula las operaciones en una transacción, incluyendo la adición de nuevas operaciones
-
-**Uso:** `stellar tx operation <COMMAND>`
-
-**Alias del comando:** `op`
-
-###### **Subcomandos:**
-
-- `add` — Añadir operación a una transacción
-
-## `stellar tx operation add`
-
-Añadir operación a una transacción
-
-**Uso:** `stellar tx operation add <COMMAND>`
-
-###### **Subcomandos:**
-
-- `account-merge` — Transferir saldo XLM a otra cuenta y eliminar la cuenta origen
-- `begin-sponsoring-future-reserves` — Comenzar a patrocinar reservas futuras para otra cuenta
-- `bump-sequence` — Incrementar número de secuencia para invalidar transacciones anteriores
-- `change-trust` — Crear, actualizar o eliminar una trustline
-- `claim-claimable-balance` — Reclamar un saldo reclamable por su ID de saldo
-- `clawback` — Recuperar un activo de una cuenta
-- `clawback-claimable-balance` — Recuperar un balance reclamable por su ID de balance
-- `create-account` — Crear y financiar una cuenta nueva
-- `create-claimable-balance` — Crear un saldo reclamable que puede ser reclamado por cuentas específicas
-- `create-passive-sell-offer` — Crear una oferta pasiva de venta en el Stellar DEX
-- `end-sponsoring-future-reserves` — Finalizar patrocinio de reservas futuras
-- `liquidity-pool-deposit` — Depositar activos en un fondo de liquidez
-- `liquidity-pool-withdraw` — Retirar activos de un fondo de liquidez
-- `manage-buy-offer` — Crear, actualizar o eliminar una oferta de compra
-- `manage-data` — Establecer, modificar o eliminar entradas de datos de la cuenta
-- `manage-sell-offer` — Crear, actualizar o eliminar una oferta de venta
-- `path-payment-strict-receive` — Enviar un pago con un activo diferente usando búsqueda de rutas, especificando la cantidad a recibir
-- `path-payment-strict-send` — Enviar un pago con un activo diferente usando búsqueda de rutas, especificando la cantidad a enviar
-- `payment` — Enviar activo a cuenta destino
-- `revoke-sponsorship` — Revocar patrocinio de una entrada del ledger o firmante
-- `set-options` — Establecer opciones de cuenta como flags, firmantes y dominio principal
-- `set-trustline-flags` — Configurar flags de autorización y trustline para un activo
-
-## `stellar tx operación agregar fusionar cuenta`
-
-Transferir saldo XLM a otra cuenta y eliminar la cuenta origen
-
-**Uso:** `stellar tx operation add account-merge [OPTIONS] --source-account <SOURCE_ACCOUNT> --account <ACCOUNT> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta fuente utilizada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si NO se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará.
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si se usa una frase Seed, `--hd-path` por defecto es la ruta `0`.
-- `--hd-path <HD_PATH>` — Si usas una frase Seed para firmar, establece qué ruta jerárquica determinista usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--account <ACCOUNT>` — Cuenta muxed con la que fusionarse, p. ej. `GBX...`, 'MBX...'
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, de lo contrario utiliza `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes.
-
-###### **Opciones (RPC):**
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org `--sign-with-ledger` — Firmar con una ledger wallet
-
-  `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor rpc
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-- `--rpc-url <RPC_URL>` — Endpoint del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase contraseña de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar tx operation add begin-sponsoring-future-reserves`
-
-Comenzar a patrocinar reservas futuras para otra cuenta
-
-**Uso:** `stellar tx operation add begin-sponsoring-future-reserves [OPTIONS] --source-account <SOURCE_ACCOUNT> --sponsored-id <SPONSORED_ID> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta fuente utilizada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta multiplexada (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si NO se proporcionaron los flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará.
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si se usa una frase Seed, `--hd-path` por defecto es la ruta `0`.
-- `--hd-path <HD_PATH>` — Si usas una frase Seed para firmar, establece qué ruta jerárquica determinista usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--sponsored-id <SPONSORED_ID>` — Cuenta que será patrocinada
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, de lo contrario utiliza `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes.
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Endpoint del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase contraseña de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a utilizar desde la configuración
-
-## `stellar tx operación agregar aumentar-secuencia`
-
-Incrementar número de secuencia para invalidar transacciones anteriores
-
-**Uso:** `stellar tx operation add bump-sequence [OPTIONS] --source-account <SOURCE_ACCOUNT> --bump-to <BUMP_TO> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o entrada estándar si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen utilizada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase seed (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si se usa una frase Seed, `--hd-path` por defecto es la ruta `0`.
-- `--hd-path <HD_PATH>` — Si usas una frase Seed para firmar, establece qué ruta jerárquica determinista usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--bump-to <BUMP_TO>` — Número de secuencia al que aumentar
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operación agregar cambiar-confianza`
-
-Crear, actualizar o eliminar una trustline
-
-**Uso:** `stellar tx operation add change-trust [OPTIONS] --source-account <SOURCE_ACCOUNT> --line <LINE> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta fuente utilizada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase seed (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase seed (--sign-with-key "kite urban…"). Si se usa frase seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase seed para firmar, establece qué ruta determinista jerárquica se usará, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--line <LINE>`
-- `--limit <LIMIT>` — Límite para la línea de confianza, 0 para eliminar la línea de confianza
-
-  Valor predeterminado: `9223372036854775807`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está configurado, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add claim-claimable-balance`
-
-Reclamar un saldo reclamable por su ID de saldo
-
-**Uso:** `stellar tx operation add claim-claimable-balance [OPCIONES] --source-account <SOURCE_ACCOUNT> --balance-id <BALANCE_ID> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o entrada estándar si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen utilizada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase seed (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase seed (--sign-with-key "kite urban…"). Si se usa frase seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase seed para firmar, establece qué ruta determinista jerárquica se usará, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--balance-id <BALANCE_ID>` — ID del saldo reclamable a reclamar (cadena hexadecimal de 64 caracteres)
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add clawback`
-
-Recuperar un activo de una cuenta
-
-**Uso:** `stellar tx operation add clawback [OPCIONES] --source-account <SOURCE_ACCOUNT> --from <FROM> --asset <ASSET> --amount <AMOUNT> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta fuente utilizada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase seed (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase seed (--sign-with-key "kite urban…"). Si se usa frase seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase seed para firmar, establece qué ruta determinista jerárquica se usará, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--from <FROM>` — Cuenta desde la que se recuperarán activos, por ejemplo `GBX...`
-- `--asset <ASSET>` — Activo a recuperar
-- `--amount <AMOUNT>` — Cantidad del activo a recuperar, en stroops. 1 stroop = 0.0000001 del activo
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add clawback-claimable-balance`
-
-Recuperar un balance reclamable por su ID de balance
-
-**Uso:** `stellar tx operation add clawback-claimable-balance [OPCIONES] --source-account <SOURCE_ACCOUNT> --balance-id <BALANCE_ID> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción base64 o archivo con XDR a decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase seed (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase seed (--sign-with-key "kite urban…"). Si se usa frase seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase seed para firmar, establece qué ruta determinista jerárquica se usará, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--balance-id <BALANCE_ID>` — ID del balance reclamable a recuperar. Acepta múltiples formatos: - Formato API con prefijo de tipo (72 caracteres): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de hash directo (64 caracteres): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de dirección (base32): BAAMLBZI42AD52HKGIZOU7WFVZM6BPEJCLPL44QU2AT6TY3P57I5QDNYIA
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operación agregar crear-cuenta`
-
-Crear y financiar una cuenta nueva
-
-**Uso:** `stellar tx operation add create-account [OPTIONS] --source-account <SOURCE_ACCOUNT> --destination <DESTINATION> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta fuente usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase seed (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase seed (--sign-with-key "kite urban…"). Si se usa frase seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase seed para firmar, establece qué ruta determinista jerárquica se usará, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--destination <DESTINATION>` — ID de cuenta a crear, p. ej. `GBX...`
-- `--starting-balance <STARTING_BALANCE>` — Saldo inicial en stroops de la cuenta, predeterminado 1 XLM
-
-  Valor predeterminado: `10_000_000`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el coste de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones a simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir el xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add create-claimable-balance`
-
-Crear un saldo reclamable que puede ser reclamado por cuentas especificadas
-
-**Uso:** `stellar tx operation add create-claimable-balance [OPTIONS] --source-account <SOURCE_ACCOUNT> --amount <AMOUNT> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción en base-64 XDR o archivo que contiene XDR a decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta fuente utilizada para la operación
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase seed (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con la clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase seed (--sign-with-key "kite urban…"). Si se usa frase seed, `--hd-path` por defecto es la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si se usa una frase seed para firmar, establece qué ruta determinista jerárquica se usará, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una ledger wallet
-
-- `--asset <ASSET>` — Activo que se mantendrá en la ClaimableBalanceEntry
-
-  Ejemplo: `--hd-path 1`.
-
-- `--amount <AMOUNT>` — Cantidad de activo para almacenar en la entrada, en stroops. 1 stroop = 0.0000001 del activo
-
-- `--claimant <CLAIMANTS>` — Reclamantes del saldo reclamable. Formato: account_id o account_id:predicate_json Se puede especificar varias veces para múltiples reclamantes.
-
-  Ejemplos:
-
-  - `--claimant alice (incondicional)` - `--claimant 'bob:{"before_absolute_time":"1735689599"}'` - `--claimant 'charlie:{"and":[{"before_absolute_time":"1735689599"},{"before_relative_time":"3600"}]}'`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido; de lo contrario, usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir la xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add create-passive-sell-offer`
-
-Crear una oferta de venta pasiva en el Stellar DEX
-
-**Uso:** `stellar tx operation add create-passive-sell-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción en base-64 XDR o archivo que contiene XDR a decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si no se proporcionaron las flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con una clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase seed (--sign-with-key "kite urban…"). Si se usa frase seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase seed para firmar, establece qué ruta determinista jerárquica se usará, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--selling <SELLING>` — Activo a vender
-- `--buying <BUYING>` — Activo a comprar
-- `--amount <AMOUNT>` — Cantidad de activo a vender para ofrecer, en stroops. Por defecto: `0`
-- `--price <PRICE>` — Precio de 1 unidad del activo a vender en términos del activo a comprar como "numerador:denominador" (p. ej., "1:2" significa 0.5)
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir la xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add end-sponsoring-future-reserves`
-
-Finalizar patrocinio de reservas futuras
-
-**Uso:** `stellar tx operation add end-sponsoring-future-reserves [OPTIONS] --source-account <SOURCE_ACCOUNT> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción en base-64 XDR o archivo que contiene XDR a decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si no se proporcionaron las flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con una clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas frase Seed para firmar, establece la ruta determinista jerárquica a usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir la xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add liquidity-pool-deposit`
-
-Depositar activos en un fondo de liquidez
-
-**Uso:** `stellar tx operation add liquidity-pool-deposit [OPTIONS] --source-account <SOURCE_ACCOUNT> --liquidity-pool-id <LIQUIDITY_POOL_ID> --max-amount-a <MAX_AMOUNT_A> --max-amount-b <MAX_AMOUNT_B> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si no se proporcionaron las flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con una clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si usas frase Seed para firmar, establece la ruta determinista jerárquica a usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una ledger wallet
-
-- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — ID del fondo de liquidez para depositar
-
-- `--max-amount-a <MAX_AMOUNT_A>` — Cantidad máxima del primer activo a depositar, en stroops
-
-- `--max-amount-b <MAX_AMOUNT_B>` — Cantidad máxima del segundo activo a depositar, en stroops
-
-- `--min-price <MIN_PRICE>` — Precio mínimo para el primer activo en términos del segundo activo como "numerador:denominador" (por ejemplo, "1:2" significa 0.5)
-
-  Valor predeterminado: `1:1`
-
-- `--max-price <MAX_PRICE>` — Precio máximo para el primer activo en términos del segundo activo como "numerador:denominador" (por ejemplo, "1:2" significa 0.5)
-
-  Valor predeterminado: `1:1`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — monto de la comisión para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Desarrollar la transacción y solo escribir la xdr base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final RPC del servidor
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add liquidity-pool-withdraw`
-
-Retirar activos de un fondo de liquidez
-
-**Uso:** `stellar tx operation add liquidity-pool-withdraw [OPTIONS] --source-account <SOURCE_ACCOUNT> --liquidity-pool-id <LIQUIDITY_POOL_ID> --amount <AMOUNT> --min-amount-a <MIN_AMOUNT_A> --min-amount-b <MIN_AMOUNT_B> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta fuente usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si no se proporcionaron las flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con una clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas frase Seed para firmar, establece la ruta determinista jerárquica a usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — ID del fondo de liquidez para retirar
-- `--amount <AMOUNT>` — Cantidad de acciones del fondo para retirar, en stroops
-- `--min-amount-a <MIN_AMOUNT_A>` — Cantidad mínima del primer activo a recibir, en stroops
-- `--min-amount-b <MIN_AMOUNT_B>` — Cantidad mínima del segundo activo a recibir, en stroops
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final RPC del servidor
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add manage-buy-offer`
-
-Crear, actualizar o eliminar una oferta de compra
-
-**Uso:** `stellar tx operation add manage-buy-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si usas frase Seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas frase Seed para firmar, establece la ruta determinista jerárquica a usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Predeterminado: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--selling <SELLING>` — Activo a vender
-- `--buying <BUYING>` — Activo a comprar
-- `--amount <AMOUNT>` — Cantidad de activo a comprar para adquirir, en stroops. 1 stroop = 0.0000001 del activo (p. ej. 1 XLM = `10_000_000` stroops). Usa `0` para eliminar la oferta
-- `--price <PRICE>` — Precio de 1 unidad del activo a comprar en términos del activo a vender como "numerador:denominador" (p. ej., "1:2" significa 0.5)
-- `--offer-id <OFFER_ID>` — ID de la oferta. Si es 0, se creará una nueva oferta. De lo contrario, actualizará la oferta existente
-
-  Valor predeterminado: `0`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está establecido, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final RPC del servidor
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operación agregar gestionar-datos`
-
-Establecer, modificar o eliminar entradas de datos de la cuenta
-
-**Uso:** `stellar tx operation add manage-data [OPTIONS] --source-account <SOURCE_ACCOUNT> --data-name <DATA_NAME> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si usas Seed phrase, `--hd-path` usa por defecto la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas Seed phrase para firmar, establece qué ruta jerárquica determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--data-name <DATA_NAME>` — Cadena de hasta 64 bytes de longitud. Si es un nombre nuevo, se agregará el par nombre/valor dado a la cuenta. Si este Nombre ya está presente, entonces el valor asociado será modificado
-- `--data-value <DATA_VALUE>` — Cadena hexagonal de hasta 64 bytes. Si no está presente, entonces se eliminará el Nombre existente. Si está presente, este valor se establecerá en el `DataEntry`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está definido, en caso contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — Punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add manage-sell-offer`
-
-Crear, actualizar o eliminar una oferta de venta
-
-**Uso:** `stellar tx operation add manage-sell-offer [OPTIONS] --source-account <SOURCE_ACCOUNT> --selling <SELLING> --buying <BUYING> --amount <AMOUNT> --price <PRICE> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si usas Seed phrase, `--hd-path` usa por defecto la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas Seed phrase para firmar, establece qué ruta jerárquica determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--selling <SELLING>` — Activo a vender
-- `--buying <BUYING>` — Activo a comprar
-- `--amount <AMOUNT>` — Cantidad de activo a vender para ofrecer, en stroops. 1 stroop = 0.0000001 del activo (p. ej. 1 XLM = `10_000_000` stroops). Usa `0` para eliminar la oferta
-- `--price <PRICE>` — Precio de 1 unidad del activo a vender en términos del activo a comprar como "numerador:denominador" (p. ej., "1:2" significa 0.5)
-- `--offer-id <OFFER_ID>` — ID de la oferta. Si es 0, se creará una nueva oferta. De lo contrario, actualizará la oferta existente
-
-  Valor predeterminado: `0`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está definido, en caso contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final RPC del servidor
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add path-payment-strict-receive`
-
-Enviar un pago con un activo diferente usando la búsqueda de rutas, especificando la cantidad a recibir
-
-**Uso:** `stellar tx operation add path-payment-strict-receive [OPTIONS] --source-account <SOURCE_ACCOUNT> --send-asset <SEND_ASSET> --send-max <SEND_MAX> --destination <DESTINATION> --dest-asset <DEST_ASSET> --dest-amount <DEST_AMOUNT> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si usas Seed phrase, `--hd-path` usa por defecto la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas Seed phrase para firmar, establece qué ruta jerárquica determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--send-asset <SEND_ASSET>` — Activo a enviar (pagar con)
-- `--send-max <SEND_MAX>` — Cantidad máxima del activo a enviar para deducir de la cuenta del emisor, en stroops. 1 stroop = 0.0000001 del activo (p. ej. 1 XLM = `10_000_000` stroops)
-- `--destination <DESTINATION>` — Cuenta que recibe el pago
-- `--dest-asset <DEST_ASSET>` — Activo que la cuenta destino recibirá
-- `--dest-amount <DEST_AMOUNT>` — Cantidad exacta del activo destino que la cuenta destino recibirá, en stroops. 1 stroop = 0.0000001 del activo
-- `--path <PATH>` — Lista de activos intermedios para la ruta de pago, separados por comas (hasta 5 activos). Cada activo debe estar en el formato 'código:emisor' o 'native' para XLM
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está definido, en caso contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final RPC del servidor
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation add path-payment-strict-send`
-
-Enviar un pago con un activo diferente usando la búsqueda de rutas, especificando la cantidad a enviar
-
-**Uso:** `stellar tx operation add path-payment-strict-send [OPTIONS] --source-account <SOURCE_ACCOUNT> --send-asset <SEND_ASSET> --send-amount <SEND_AMOUNT> --destination <DESTINATION> --dest-asset <DEST_ASSET> --dest-min <DEST_MIN> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si usas Seed phrase, `--hd-path` usa por defecto la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas Seed phrase para firmar, establece qué ruta jerárquica determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--send-asset <SEND_ASSET>` — Activo a enviar (pagar con)
-- `--send-amount <SEND_AMOUNT>` — Cantidad de activo a enviar para deducir de la cuenta del emisor, en stroops. 1 stroop = 0.0000001 del activo (p. ej. 1 XLM = `10_000_000` stroops)
-- `--destination <DESTINATION>` — Cuenta que recibe el pago
-- `--dest-asset <DEST_ASSET>` — Activo que la cuenta destino recibirá
-- `--dest-min <DEST_MIN>` — Cantidad mínima del activo destino que la cuenta destino puede recibir. La operación fallará si no se puede cumplir esta cantidad
-- `--path <PATH>` — Lista de activos intermedios para la ruta del pago, separados por comas (hasta 5 activos). Cada activo debe estar en el formato 'código:emisor' o 'native' para XLM
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está definido, en caso contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final RPC del servidor
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor RPC
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx operation agregar pago`
-
-Enviar activo a cuenta destino
-
-**Uso:** `stellar tx operation add payment [OPTIONS] --source-account <SOURCE_ACCOUNT> --destination <DESTINATION> --amount <AMOUNT> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en base 64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si usas Seed phrase, `--hd-path` usa por defecto la ruta `0`
-
-- `--hd-path <HD_PATH>` — Si usas Seed phrase para firmar, establece qué ruta jerárquica determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-
-- `--sign-with-ledger` — Firmar con una ledger wallet
-
-- `--destination <DESTINATION>` — Cuenta a la que se envía, ej. `GBX...`
-
-- `--asset <ASSET>` — Activo a enviar, por defecto native, es decir, XLM
-
-  Valor predeterminado: `native`
-
-- `--amount <AMOUNT>` — Cantidad del activo mencionado a enviar, en stroops. 1 stroop = 0.0000001 del activo (p. ej. 1 XLM = `10_000_000` stroops)
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está definido, en caso contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase clave de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar de la configuración
-
-## `stellar tx operation add revoke-sponsorship`
-
-Revocar patrocinio de una entrada del ledger o firmante
-
-**Uso:** `stellar tx operation add revoke-sponsorship [OPTIONS] --source-account <SOURCE_ACCOUNT> --account-id <ACCOUNT_ID> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si usas Seed phrase, `--hd-path` usa por defecto la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas Seed phrase para firmar, establece qué ruta jerárquica determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--account-id <ACCOUNT_ID>` — ID de cuenta (requerido para todos los tipos de patrocinio)
-- `--asset <ASSET>` — Activo para patrocinio de trustline (formato: CODE:ISSUER)
-- `--data-name <DATA_NAME>` — Nombre de dato para patrocinio de entrada de datos
-- `--offer-id <OFFER_ID>` — ID de oferta para patrocinio de oferta
-- `--liquidity-pool-id <LIQUIDITY_POOL_ID>` — ID del pool para patrocinio de fondos de liquidez. Acepta múltiples formatos: - Formato API con prefijo de tipo (72 caracteres): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de hash directo (64 caracteres): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de dirección (base32): LAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
-- `--claimable-balance-id <CLAIMABLE_BALANCE_ID>` — ID de balance reclamable para patrocinio de balance reclamable. Acepta múltiples formatos: - Formato API con prefijo de tipo (72 caracteres): 000000006f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de hash directo (64 caracteres): 6f2179b31311fa8064760b48942c8e166702ba0b8fbe7358c4fd570421840461 - Formato de dirección (base32): BAAMLBZI42AD52HKGIZOU7WFVZM6BPEJCLPL44QU2AT6TY3P57I5QDNYIA
-- `--signer-key <SIGNER_KEY>` — Clave del firmante para patrocinio de firmante
-
-###### **Opciones (Globales):**
-
-- Ejemplo: `--hd-path 1`.
-- Por defecto: `0` Por defecto, utiliza `$XDG_CONFIG_HOME/stellar` si está definido, y en caso contrario recurre a `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase clave de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar de la configuración
-
-## `stellar tx operation add set-options`
-
-Establecer opciones de cuenta como flags, firmantes y dominio principal
-
-**Uso:** `stellar tx operation add set-options [OPTIONS] --source-account <SOURCE_ACCOUNT> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--operation-source-account <OPERATION_SOURCE_ACCOUNT>` [alias: `op-source`] — Cuenta origen usada para la operación
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la que se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una Seed phrase (--source "kite urban…"). Si no se proporcionaron las banderas `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si usas Seed phrase, `--hd-path` usa por defecto la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas Seed phrase para firmar, establece qué ruta jerárquica determinista usar, p. ej. `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--inflation-dest <INFLATION_DEST>` — Cuenta del destino de inflación
-- `--master-weight <MASTER_WEIGHT>` — Un número de 0-255 (inclusive) que representa el peso de la clave maestra. Si el peso de la clave maestra se actualiza a 0, efectivamente queda deshabilitado
-- `--low-threshold <LOW_THRESHOLD>` — Un número de 0-255 (inclusive) que representa el umbral que esta cuenta establece en todas las operaciones que realiza que tienen un bajo umbral. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
-- `--med-threshold <MED_THRESHOLD>` — Un número de 0-255 (inclusive) que representa el umbral que esta cuenta establece en todas las operaciones que realiza que tienen un umbral medio. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
-- `--high-threshold <HIGH_THRESHOLD>` — Un número de 0-255 (inclusive) que representa el umbral que esta cuenta establece en todas las operaciones que realiza que tienen un alto umbral. https://developers.stellar.org/docs/learn/encyclopedia/security/signatures-multisig#multisig
-- `--home-domain <HOME_DOMAIN>` — Establece el dominio de origen de una cuenta. Ver https://developers.stellar.org/docs/learn/encyclopedia/network-configuration/federation
-- `--signer <SIGNER>` — Agregar, actualizar o eliminar un firmante de una cuenta
-- `--signer-weight <SIGNER_WEIGHT>` — El peso del firmante es un número de 0-255 (inclusive). El firmante se elimina si el peso es 0
-- `--set-required` — Cuando se habilita, un emisor debe aprobar una cuenta antes de que esa cuenta pueda poseer su activo. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-required-0x1
-- `--set-revocable` — Cuando se habilita, un emisor puede revocar la autorización de una línea de confianza existente, congelando así el activo mantenido por una cuenta. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-revocable-0x2
-- `--set-clawback-enabled` — Habilita la cuenta emisora para recuperar (quemar) todo el activo. https://developers.stellar.org/docs/tokens/control-asset-access#clawback-enabled-0x8
-- `--set-immutable` — Con esta configuración, ninguna de las otras banderas de autorización (`AUTH_REQUIRED_FLAG`, `AUTH_REVOCABLE_FLAG`) puede ser establecida, y la cuenta emisora no puede fusionarse. https://developers.stellar.org/docs/tokens/control-asset-access#authorization-immutable-0x4
-- `--clear-required`
-- `--clear-revocable`
-- `--clear-immutable`
-- `--clear-clawback-enabled`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, utiliza `$XDG_CONFIG_HOME/stellar` si está definido, y de lo contrario recurre a `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--fee <FEE>` — Cantidad de la tarifa para la transacción, en stroops. 1 stroop = 0.0000001 xlm
-
-  Valor predeterminado: `100`
-
-- `--cost` — Mostrar el costo de ejecución en stderr
-
-- `--instructions <INSTRUCTIONS>` — Número de instrucciones para simulate
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- `--build-only` — Construir la transacción y solo escribir el XDR base64 en stdout
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase clave de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar de la configuración
-
-## `stellar tx operation add set-trustline-flags`
-
-Configurar flags de autorización y trustline para un activo
-
-**Uso:** `stellar tx operation add set-trustline-flags [OPTIONS] --source-account <SOURCE_ACCOUNT> --trustor <TRUSTOR> --asset <ASSET> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--rpc-url <RPC_URL>` — punto final RPC del servidor
-- Contiene archivos de configuración, alias y otras configuraciones persistentes `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una Seed phrase (--sign-with-key "kite urban…"). Si usas Seed phrase, `--hd-path` usa por defecto la ruta `0` `--hd-path <HD_PATH>` — Si usas Seed phrase para firmar, establece qué ruta jerárquica determinista usar, p. ej. `m/44'/148'/{hd_path}`.
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o con una clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si se usa frase Seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase Seed para firmar, establece qué ruta determinista jerárquica usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una billetera ledger
-- `--trustor <TRUSTOR>` — Cuenta para establecer banderas de línea de confianza, p.ej. `GBX...`, o alias, o cuenta multiplexada, \`M123...\`\`
-- `--asset <ASSET>` — Activo para establecer banderas de línea de confianza
-- `--set-authorize` — Significa autorización completa que permite a una cuenta transaccionar libremente con el activo para hacer y recibir pagos y realizar pedidos
-- `--set-authorize-to-maintain-liabilities` — Denota autorización limitada que permite a una cuenta mantener pedidos actuales pero no transaccionar con el activo de otra manera
-- `--set-trustline-clawback-enabled` — Habilita a la cuenta emisora para recuperar (quemar) todo el activo. Ve nuestra sección sobre Clawbacks: https://developers.stellar.org/docs/learn/encyclopedia/transactions-specialized/clawbacks
-- `--clear-authorize`
-- `--clear-authorize-to-maintain-liabilities`
-- `--clear-trustline-clawback-enabled`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, utiliza `$XDG_CONFIG_HOME/stellar` si está definido, y de lo contrario recurre a `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en peticiones al proveedor RPC `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de red para firmar la transacción enviada al servidor rpc
-
-  `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración.
-
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-- Por defecto usa `$XDG_CONFIG_HOME/stellar` si está definido, en caso contrario usa `~/.config/stellar`.
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase clave de red para firmar la transacción enviada al servidor rpc
-
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar de la configuración
-
-## `stellar tx send`
-
-Envía un sobre de transacción a la red
-
-**Uso:** `stellar tx send [OPTIONS] [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o entrada estándar si está vacío
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, o de lo contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx sign`
-
-Firma un sobre de transacción añadiendo la firma al sobre
-
-**Uso:** `stellar tx sign [OPTIONS] [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción en base-64 XDR, o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o con una clave guardada en el almacenamiento seguro del sistema operativo. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si se usa frase Seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si se usa una frase Seed para firmar, establece qué ruta determinista jerárquica usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una billetera ledger
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, o de lo contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de la red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar tx simulate`
-
-Simula un sobre de transacción desde stdin
-
-**Uso:** `stellar tx simulate [OPTIONS] --source-account <SOURCE_ACCOUNT> [TX_XDR]`
-
-###### **Argumentos:**
-
-- `<TX_XDR>` — Sobre de transacción XDR en Base-64 o archivo que contiene XDR para decodificar, o entrada estándar si está vacío
-
-###### **Opciones:**
-
-- `-s`, `--source-account <SOURCE_ACCOUNT>` [alias: `source`] — Cuenta desde la cual se origina la transacción. Alias `source`. Puede ser una identidad (--source alice), una clave pública (--source GDKW...), una cuenta muxed (--source MDA…), una clave secreta (--source SC36…), o una frase Seed (--source "kite urban…"). Si no se proporcionaron las flags `--build-only` o `--sim-only`, esta clave también se usará para firmar la transacción final. En ese caso, intentar firmar con una clave pública fallará
-- `--sign-with-key <SIGN_WITH_KEY>` — Firmar con una clave local o una clave guardada en el almacenamiento seguro del SO. Puede ser una identidad (--sign-with-key alice), una clave secreta (--sign-with-key SC36…), o una frase Seed (--sign-with-key "kite urban…"). Si se usa una frase Seed, `--hd-path` por defecto es la ruta `0`
-- `--hd-path <HD_PATH>` — Si usas una frase Seed para firmar, establece qué ruta jerárquicamente determinista usar, por ejemplo `m/44'/148'/{hd_path}`. Ejemplo: `--hd-path 1`. Por defecto: `0`
-- `--sign-with-lab` — Firmar con https://lab.stellar.org
-- `--sign-with-ledger` — Firmar con una ledger wallet
-- `--instruction-leeway <INSTRUCTION_LEEWAY>` — Permite esta cantidad de instrucciones extra al presupuestar recursos durante la simulación de la transacción
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está configurado, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red que se usará desde la configuración
-
-## `stellar tx fetch`
-
-Obtener una transacción de la red por hash. Si no se pasa subcomando, se devolverá el sobre de la transacción.
-
-**Uso:** `stellar tx fetch [OPTIONS]        fetch <COMMAND>`
-
-###### **Subcomandos:**
-
-- `result` — Obtener el resultado de la transacción
-- `meta` — Obtener los metadatos de la transacción
-- `fee` — Obtener la información de la comisión de la transacción
-- `events` — Obtener los eventos de la transacción
-
-###### **Opciones:**
-
-- `--hash <HASH>` — Hash de la transacción a obtener
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON con XDRs analizados (una línea, no formateado)
-  - `json-formatted`: Salida JSON formateada (multilínea) con XDRs analizados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red que se usará desde la configuración
-
-## `stellar tx fetch result`
-
-Obtener el resultado de la transacción
-
-**Uso:** `stellar tx fetch result [OPTIONS] --hash <HASH>`
-
-###### **Opciones:**
-
-- `--hash <HASH>` — Hash de la transacción a obtener
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor por defecto: `json`
-
-  Posibles valores:
-
-  - `json`: Salida JSON con XDRs analizados (una línea, no formateado)
-  - `json-formatted`: Salida JSON formateada (multilínea) con XDRs analizados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red que se usará desde la configuración
-
-## `stellar tx fetch meta`
-
-Obtener los metadatos de la transacción
-
-**Uso:** `stellar tx fetch meta [OPTIONS] --hash <HASH>`
-
-###### **Opciones:**
-
-- `--hash <HASH>` — Hash de la transacción a obtener
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `json`
-
-  Posibles valores:
-
-  - `json`: Salida JSON con XDRs analizados (una línea, no formateado)
-  - `json-formatted`: Salida JSON formateada (multilínea) con XDRs analizados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red que se usará desde la configuración
-
-## `stellar tx fetch fee`
-
-Obtener la información de la comisión de la transacción
-
-**Uso:** `stellar tx fetch fee [OPTIONS] --hash <HASH>`
-
-###### **Opciones:**
-
-- `--hash <HASH>` — Hash de la transacción a obtener
-- `--output <OUTPUT>` — Formato de salida para el comando fee
-
-  Valor por defecto: `table`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada del ledger con XDRs parseados (en una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada del ledger con XDRs parseados
-  - `table`: Formateado en una tabla comparando tipos de comisión
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red que se usará desde la configuración
-
-## `stellar tx fetch events`
-
-Obtener los eventos de la transacción
-
-**Uso:** `stellar tx fetch events [OPCIONES] --hash <HASH>`
-
-###### **Opciones:**
-
-- `--hash <HASH>` — Hash de la transacción para obtener
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de los eventos con XDRs analizados (una línea, no formateado)
-  - `json-formatted`: Salida JSON formateada (multilínea) de eventos con XDRs analizados
-  - `text`: Salida de eventos legible para humanos con XDRs analizados
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red que se usará desde la configuración
-
-## `stellar tx decode`
-
-Decodificar un sobre de transacción de XDR a JSON
-
-**Uso:** `stellar tx decode [OPCIONES] [ENTRADA]...`
-
-###### **Argumentos:**
-
-- `<INPUT>` — XDR o archivos que contienen XDR para decodificar, o entrada estándar si está vacío
-
-###### **Opciones:**
-
-- `--input <INPUT_FORMAT>`
-
-  Valor predeterminado: `single-base64`
-
-  Valores posibles: `single-base64`, `single`
-
-- `--output <OUTPUT_FORMAT>`
-
-  Valor por defecto: `json`
-
-  Valores posibles: `json`, `json-formatted`
-
-## `stellar tx encode`
-
-Codificar un sobre de transacción de JSON a XDR
-
-**Uso:** `stellar tx encode [OPCIONES] [ENTRADA]...`
-
-###### **Argumentos:**
-
-- `<INPUT>` — XDR o archivos que contienen XDR para codificar, o entrada estándar si está vacío
-
-###### **Opciones:**
-
-- `--input <INPUT_FORMAT>`
-
-  Valor predeterminado: `json`
-
-  Valores posibles: `json`
-
-- `--output <OUTPUT_FORMAT>`
-
-  Valor predeterminado: `single-base64`
-
-  Valores posibles: `single-base64`, `single`
-
-## `stellar xdr`
-
-Decodificar y codificar XDR
-
-**Uso:** `stellar xdr [CHANNEL] <COMMAND>`
-
-###### **Subcomandos:**
-
-- `types` — Ver información sobre tipos
-- `guess` — Adivina el tipo de XDR
-- `decode` — Decodificar XDR
-- `encode` — Codificar XDR
-- `compare` — Comparar dos valores XDR entre sí
-- `generate` — Generar valores XDR
-- `version` — Imprimir información de la versión
-
-###### **Argumentos:**
-
-- `<CHANNEL>` — Canal de XDR en el que operar
-
-  Valor predeterminado: `+curr`
-
-  Valores posibles: `+curr`, `+next`
-
-## `tipos xdr de stellar`
-
-Ver información sobre tipos
-
-**Uso:** `tipos xdr de stellar <COMMAND>`
-
-###### **Subcomandos:**
-
-- `listar` —
-- `esquema` —
-- `schema-files` — Generar archivos de esquema JSON para los tipos XDR, escribiendo un archivo por cada tipo en el directorio out
-
-## `tipos xdr de stellar listar`
-
-**Uso:** `tipos xdr de stellar listar [OPCIONES]`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>`
-
-  Valor predeterminado: `plain`
-
-  Valores posibles: `plain`, `json`, `json-formateado`
-
-## `tipos xdr de stellar esquema`
-
-**Uso:** `tipos xdr de stellar esquema [OPCIONES] --type <TYPE>`
-
-###### **Opciones:**
-
-- `--type <TYPE>` — Tipo de XDR a decodificar
-- `--output <OUTPUT>`
-
-  Valor predeterminado: `json-esquema-borrador201909`
-
-  Valores posibles: `json-schema-draft201909`
-
-## `stellar xdr types schema-files`
-
-Generar archivos de esquema JSON para los tipos XDR, escribiendo un archivo por cada tipo en el directorio out
-
-**Uso:** `stellar xdr types schema-files [OPTIONS] --out-dir <OUT_DIR>`
-
-###### **Opciones:**
-
-- `--out-dir <OUT_DIR>`
-- `--output <OUTPUT>`
-
-  Valor por defecto: `json-schema-draft201909`
-
-  Valores posibles: `json-schema-draft201909`
-
-## `tipos xdr de stellar adivinar`
-
-Adivinar el tipo XDR.
-
-Imprime una lista de tipos en los que los valores XDR pueden ser decodificados.
-
-**Uso:** `stellar xdr guess [OPTIONS] [INPUT]`
-
-###### **Argumentos:**
-
-- `<INPUT>` — XDR o archivo que contiene XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--input <INPUT_FORMAT>`
-
-  Valor predeterminado: `single-base64`
-
-  Valores posibles: `single`, `single-base64`, `stream`, `stream-base64`, `stream-framed`
-
-- `--output <OUTPUT_FORMAT>`
-
-  Valor predeterminado: `lista`
-
-  Valores posibles: `lista`
-
-- `--certainty <CERTAINTY>` — Certeza como un valor arbitrario
-
-  Valor predeterminado: `2`
-
-## `tipos xdr de stellar decodificar`
-
-Decodificar XDR
-
-**Uso:** `stellar xdr decode [OPTIONS] --type <TYPE> [INPUT]...`
-
-###### **Argumentos:**
-
-- `<ENTRADA>` — XDR o archivos que contienen XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--type <TYPE>` — Tipo de XDR a decodificar
-
-- `--input <INPUT_FORMAT>`
-
-  Valor predeterminado: `stream-base64`
-
-  Valores posibles: `single`, `single-base64`, `stream`, `stream-base64`, `stream-framed`
-
-- `--output <OUTPUT_FORMAT>`
-
-  Valor predeterminado: `json`
-
-  Valores posibles: `json`, `json-formatted`, `text`, `rust-debug`, `rust-debug-formatted`
-
-## `tipos xdr de stellar codificar`
-
-Codificar XDR
-
-**Uso:** `stellar xdr encode [OPTIONS] --type <TYPE> [INPUT]...`
-
-###### **Argumentos:**
-
-- `<ENTRADA>` — XDR o archivos que contienen XDR para decodificar, o stdin si está vacío
-
-###### **Opciones:**
-
-- `--type <TYPE>` — Tipo de XDR a codificar
-
-- `--input <INPUT_FORMAT>`
-
-  Valor predeterminado: `json`
-
-  Valores posibles: `json`
-
-- `--output <OUTPUT_FORMAT>`
-
-  Valor predeterminado: `single-base64`
-
-  Valores posibles: `single`, `single-base64`, `stream`
-
-## `tipos xdr de stellar comparar`
-
-Compara dos valores XDR entre sí
-
-Salidas: `-1` cuando el valor XDR izquierdo es menor que el derecho, `0` cuando el valor XDR izquierdo es igual al derecho, `1` cuando el valor XDR izquierdo es mayor que el derecho
-
-**Uso:** `tipos xdr de stellar comparar [OPCIONES] --type <TYPE> <LEFT> <RIGHT>`
-
-###### **Argumentos:**
-
-- `<LEFT>` — Archivo XDR a decodificar y comparar con el valor derecho
-- `<RIGHT>` — Archivo XDR a decodificar y comparar con el valor izquierdo
-
-###### **Opciones:**
-
-- `--type <TYPE>` — Tipo de XDR de ambas entradas
-- `--input <INPUT>`
-
-  Valor predeterminado: `single-base64`
-
-  Valores posibles: `single`, `single-base64`
-
-## `stellar xdr generate`
-
-Generar valores XDR
-
-**Uso:** `stellar xdr generate <COMMAND>`
-
-###### **Subcomandos:**
-
-- `default` — Generar valores XDR predeterminados
-- `arbitrary` — Generar valores XDR arbitrarios
-
-## `stellar xdr generate default`
-
-Generar valores XDR predeterminados
-
-**Uso:** `stellar xdr generate default [OPTIONS] --type <TYPE>`
-
-###### **Opciones:**
-
-- `--type <TYPE>` — Tipo de XDR a generar
-- `--output <OUTPUT_FORMAT>`
-
-  Valor predeterminado: `single-base64`
-
-  Valores posibles: `single`, `single-base64`, `json`, `json-formatted`, `text`
-
-## `stellar xdr generate arbitrary`
-
-Generar valores XDR arbitrarios
-
-**Uso:** `stellar xdr generate arbitrary [OPTIONS] --type <TYPE>`
-
-###### **Opciones:**
-
-- `--type <TYPE>` — Tipo de XDR a generar
-- `--output <OUTPUT_FORMAT>`
-
-  Valor predeterminado: `single-base64`
-
-  Valores posibles: `single`, `single-base64`, `json`, `json-formatted`, `text`
-
-## `tipos xdr de stellar versión`
-
-Imprimir información de versión
-
-**Uso:** `tipos xdr de stellar versión`
-
-## `stellar strkey`
-
-Decodifica y codifica strkey
-
-**Uso:** `stellar strkey <COMANDO>`
-
-###### **Subcomandos:**
-
-- `decode` — Decodificar strkey
-- `encode` — Codificar strkey
-- `zero` — Generar el strkey cero
-- `version` — Imprimir información de la versión
-
-## `stellar strkey decode`
-
-Decodificar strkey
-
-**Uso:** `stellar strkey decode <STRKEY>`
-
-###### **Argumentos:**
-
-- `<STRKEY>` — Strkey a decodificar
-
-## `stellar strkey encode`
-
-Codificar strkey
-
-**Uso:** `stellar strkey encode <JSON>`
-
-###### **Argumentos:**
-
-- `<JSON>` — JSON del Strkey a codificar
-
-## `stellar strkey zero`
-
-Generar el strkey cero
-
-**Uso:** `stellar strkey zero [OPCIONES] <STRKEY>`
-
-###### **Argumentos:**
-
-- `<STRKEY>` — Tipo de strkey para generar su valor cero
-
-  Valores posibles: `public_key_ed25519`, `pre_auth_tx`, `hash_x`, `muxed_account_ed25519`, `signed_payload_ed25519`, `contract`, `liquidity_pool`, `claimable_balance_v0`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Formato de salida
-
-  Valor por defecto: `strkey`
-
-  Valores posibles: `strkey`, `json`
-
-## `stellar strkey version`
-
-Imprimir información de la versión
-
-**Uso:** `stellar strkey version`
-
-## `stellar completación`
-
-Imprimir código de completado de shell para el shell especificado
-
-Asegúrate de que el paquete de completado para tu shell esté instalado, por ejemplo, bash-completion para bash.
-
-Para habilitar el autocompletado en el shell bash actual, ejecuta: `source <(stellar completación --shell bash)`
-
-Para habilitar el autocompletado permanentemente, ejecuta: `echo "source <(stellar completación --shell bash)" >> ~/.bashrc`
-
-**Uso:** `stellar completación --shell <SHELL>`
-
-###### **Opciones:**
-
-- `--shell <SHELL>` — El tipo de shell
-
-  Valores posibles: `bash`, `elvish`, `fish`, `powershell`, `zsh`
-
-## `stellar cache`
-
-Almacenar en caché las transacciones y las especificaciones de contratos
-
-**Uso:** `stellar cache <COMANDO>`
-
-###### **Subcomandos:**
-
-- `limpiar` — Eliminar la caché
-- `ruta` — Mostrar la ubicación de la caché
-- `registro de acciones` — Acceder a los detalles sobre acciones en caché como transacciones y simulaciones. (Experimental. Puede haber cambios significativos en cualquier momento.)
-
-## `stellar cache limpiar`
-
-Eliminar la caché
-
-**Uso:** `stellar cache limpiar`
-
-## `stellar cache ruta`
-
-Mostrar la ubicación de la caché
-
-**Uso:** `stellar cache ruta`
-
-## `stellar cache registro de acciones`
-
-Acceder a los detalles sobre acciones en caché como transacciones y simulaciones. (Experimental. Puede haber cambios significativos en cualquier momento.)
-
-**Uso:** `stellar cache registro de acciones <COMANDO>`
-
-###### **Subcomandos:**
-
-- `ls` — Listar acciones en caché (transacciones, simulaciones)
-- `leer` — Leer acción en caché
-
-## `stellar cache registro de acciones ls`
-
-Listar acciones en caché (transacciones, simulaciones)
-
-**Uso:** `stellar cache registro de acciones ls [OPCIONES]`
-
-###### **Opciones:**
-
-- `-l`, `--long`
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto usa `$XDG_CONFIG_HOME/stellar` si está configurado, o `~/.config/stellar` en caso contrario. Contiene archivos de configuración, alias y otras configuraciones persistentes
-
-## `stellar cache registro de acciones leer`
-
-Leer acción en caché
-
-**Uso:** `stellar cache registro de acciones leer --id <ID>`
-
-###### **Opciones:**
-
-- `--id <ID>` — ID de la entrada en la caché
-
-## `stellar versión`
-
-Imprimir información de la versión
-
-**Uso:** `stellar version [OPTIONS]`
-
-###### **Opciones:**
-
-- `--only-version` — Mostrar solo la versión
-- `--only-version-major` — Mostrar solo la versión mayor
-
-## `stellar plugin`
-
-El subcomando para plugins CLI
-
-**Uso:** `stellar plugin <COMMAND>`
-
-###### **Subcomandos:**
-
-- `search` — Buscar plugins CLI usando GitHub
-- `ls` — Listar plugins instalados
-
-## `stellar plugin search`
-
-Buscar plugins CLI usando GitHub
-
-**Uso:** `stellar plugin search`
-
-## `stellar plugin ls`
-
-Listar plugins instalados
-
-**Uso:** `stellar plugin ls`
-
-## `stellar ledger`
-
-Obtener información del ledger
-
-**Uso:** `stellar ledger <COMMAND>`
-
-###### **Subcomandos:**
-
-- `entry` — Trabajar con entradas de ledger
-- `latest` — Obtener la secuencia más reciente del ledger e información desde la red
-- `fetch` —
-
-## `stellar ledger entry`
-
-Trabajar con entradas de ledger
-
-**Uso:** `stellar ledger entry <COMANDO>`
-
-###### **Subcomandos:**
-
-- `fetch` — Obtener entradas de ledger. Este comando admite todos los tipos de entradas de ledger admitidas por el RPC. Lee más sobre el comando RPC aquí: [https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys](https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys)
-
-## `stellar ledger entry fetch`
-
-Obtener entradas de ledger. Este comando admite todos los tipos de entradas de ledger admitidas por el RPC. Lee más sobre el comando RPC aquí: [https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys](https://developers.stellar.org/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#types-of-ledgerkeys)
-
-**Uso:** `stellar ledger entry fetch <COMANDO>`
-
-###### **Subcomandos:**
-
-- `account` — Obtener entrada de cuenta por clave pública o alias
-- `contract-data` — Obtener entrada de ledger de contrato por dirección o alias y clave de almacenamiento
-- `claimable-balance` — Obtener una entrada de ledger de balance reclamable por id
-- `liquidity-pool` — Obtener una entrada de ledger de fondos de liquidez por id
-- `contract-code` — Obtener el bytecode WASM de un Contrato por hash WASM
-- `trustline` — Obtener un trustline por cuenta y activo
-- `data` — Obtener entradas de datos clave-valor adjuntas a una cuenta (ver manageDataOp)
-- `offer` — Obtener una oferta por cuenta e id de oferta
-
-## `stellar ledger entry fetch account`
-
-Obtener entrada de cuenta por clave pública o alias
-
-**Uso:** `stellar ledger entry fetch account [OPCIONES] --account <ACCOUNT>`
-
-###### **Opciones:**
-
-- `--account <ACCOUNT>` — Alias o dirección de la cuenta a consultar
-
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada del ledger con XDRs parseados (en una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada del ledger con XDRs parseados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-- `--hd-path <HD_PATH>` — Si la identidad es una frase Seed usa este camino hd, predeterminado es 0
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado, y en caso contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red que se usará desde la configuración
-
-## `stellar ledger entry fetch contract-data`
-
-Obtener entrada de ledger de contrato por dirección o alias y clave de almacenamiento
-
-**Uso:** `stellar ledger entry fetch contract-data [OPCIONES] --contract <CONTRACT>`
-
-###### **Opciones:**
-
-- `--contract <CONTRACT>` — Alias o dirección del contrato a obtener
-
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada del ledger con XDRs parseados (en una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada del ledger con XDRs parseados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-- `--durability <DURABILITY>` — Durabilidad de la entrada de almacenamiento
-
-  Valor predeterminado: `persistent`
-
-  Valores posibles:
-
-  - `persistent`: Persistente
-  - `temporary`: Temporal
-
-- `--key <KEY>` — Clave de almacenamiento (solo símbolos)
-
-- `--key-xdr <KEY_XDR>` — Clave de almacenamiento (XDR codificado en base64)
-
-- `--instance` — Si la entrada ledger de la instancia del contrato debe incluirse en la salida
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado, y en caso contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden agregar múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red que se usará desde la configuración
-
-## `stellar ledger entry fetch claimable-balance`
-
-Obtener una entrada de ledger de balance reclamable por id
-
-**Uso:** `stellar ledger entry fetch claimable-balance [OPCIONES]`
-
-###### **Opciones:**
-
-- `--id <ID>` — Ids de balance reclamable para obtener una entrada
-- `--output <OUTPUT>` — Formato de salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada del ledger con XDRs parseados (en una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada del ledger con XDRs parseados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado, y en caso contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir varios encabezados pasando la opción múltiples veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar ledger entry fetch liquidity-pool`
-
-Obtener una entrada de fondo de liquidez en el ledger por id
-
-**Uso:** `stellar ledger entry fetch liquidity-pool [OPTIONS]`
-
-###### **Opciones:**
-
-- `--id <ID>` — IDs de fondos de liquidez
-- `--output <OUTPUT>` — Formato de salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada del ledger con XDRs analizados (una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada del ledger con XDRs analizados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado, y en caso contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir varios encabezados pasando la opción múltiples veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar ledger entry fetch contract-code`
-
-Obtener el bytecode WASM de un contrato por el hash WASM
-
-**Uso:** `stellar ledger entry fetch contract-code [OPTIONS]`
-
-###### **Opciones:**
-
-- `--wasm-hash <WASM_HASH>` — Obtener bytecode WASM por hash
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada ledger con XDRs analizados (una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada ledger con XDRs analizados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado, y en caso contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir varios encabezados pasando la opción múltiples veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar ledger entry fetch trustline`
-
-Obtener una trustline por cuenta y activo
-
-**Uso:** `stellar ledger entry fetch trustline [OPTIONS] --account <ACCOUNT> --asset <ASSET>`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Formato de salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada del ledger con XDRs analizados (una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada del ledger con XDRs analizados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-- `--account <ACCOUNT>` — Alias o dirección de la cuenta a consultar
-
-- `--asset <ASSET>` — Activos para obtener información de trustline
-
-- `--hd-path <HD_PATH>` — Si la cuenta es una frase seed, usar esta ruta HD, el valor por defecto es 0
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activada
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está configurado, y en caso contrario `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir varios encabezados pasando la opción múltiples veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar ledger entry fetch data`
-
-Obtener entradas de datos clave-valor adjuntas a una cuenta (ver manageDataOp)
-
-**Uso:** `stellar ledger entry fetch data [OPTIONS] --account <ACCOUNT> --data-name <DATA_NAME>`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Formato de salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada del ledger con XDRs analizados (una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada del ledger con XDRs analizados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-- `--account <ACCOUNT>` — Alias o dirección de la cuenta a consultar
-
-- `--data-name <DATA_NAME>` — Obtener entradas de datos clave-valor adjuntas a una cuenta (ver manageDataOp)
-
-- `--hd-path <HD_PATH>` — Si la identidad es una frase seed, usar esta ruta HD, el valor por defecto es 0
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir varios encabezados pasando la opción múltiples veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar ledger entry fetch offer`
-
-Obtener una oferta por cuenta e id de oferta
-
-**Uso:** `stellar ledger entry fetch offer [OPTIONS] --account <ACCOUNT> --offer <OFFER>`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Formato de salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Salida JSON de la entrada del ledger con XDRs analizados (una línea, sin formato)
-  - `json-formatted`: Salida JSON formateada (multilínea) de la entrada del ledger con XDRs analizados
-  - `xdr`: Salida RPC original (contiene XDRs)
-
-- `--account <ACCOUNT>` — Alias o dirección de la cuenta a consultar
-
-- `--offer <OFFER>` — ID de una oferta realizada en el Stellar DEX
-
-- `--hd-path <HD_PATH>` — Si la identidad es una frase seed, usar esta ruta HD, el valor por defecto es 0
-
-###### **Opciones (Globales):**
-
-- `--global` — ⚠️ Obsoleto: la configuración global siempre está activa
-- `--config-dir <CONFIG_DIR>` — Ubicación del directorio de configuración. Por defecto, usa `$XDG_CONFIG_HOME/stellar` si está definido, de lo contrario usa `~/.config/stellar`. Contiene archivos de configuración, alias y otros ajustes persistentes
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir varios encabezados pasando la opción múltiples veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar ledger latest`
-
-Obtener la secuencia más reciente del ledger e información desde la red
-
-**Uso:** `stellar ledger latest [OPTIONS]`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Formato de salida
-
-  Valor por defecto: `text`
-
-  Valores posibles:
-
-  - `text`: Salida de texto de la información de la red
-  - `json`: Resultado JSON de la solicitud RPC
-  - `json-formatted`: Salida JSON formateada (multilínea) de la solicitud RPC
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir varios encabezados pasando la opción múltiples veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar ledger fetch`
-
-**Uso:** `stellar ledger fetch [OPTIONS] <SEQ>`
-
-###### **Argumentos:**
-
-- `<SEQ>` — Secuencia del ledger para comenzar a obtener (inclusive)
-
-###### **Opciones:**
-
-- `--limit <LIMIT>` — Número de ledgers a obtener
-
-  Valor predeterminado: `1`
-
-- `--output <OUTPUT>` — Formato de la salida
-
-  Valor predeterminado: `text`
-
-  Valores posibles:
-
-  - `text`: Salida de texto de la información de la red
-  - `json`: Resultado JSON de la solicitud RPC
-  - `json-formatted`: Salida JSON formateada (multilínea) de la solicitud RPC
-
-- `--xdr-format <XDR_FORMAT>` — Formato del XDR en la salida
-
-  Valor predeterminado: `json`
-
-  Valores posibles:
-
-  - `json`: Los campos XDR se obtendrán como JSON y serán accesibles vía los campos headerJson y metadataJson
-  - `xdr`: Los campos XDR se obtendrán como XDR y serán accesibles vía los campos headerXdr y metadataXdr
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — endpoint del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC a incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir varios encabezados pasando la opción múltiples veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de paso de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar desde la configuración
-
-## `stellar fee-stats`
-
-Obtener estadísticas de tarifas de red
-
-**Uso:** `stellar fee-stats [OPTIONS]`
-
-###### **Opciones:**
-
-- `--output <OUTPUT>` — Formato de salida
-
-  Valor predeterminado: `text`
-
-  Valores posibles:
-
-  - `text`: Salida de texto con la información de la red
-  - `json`: Resultado JSON de la solicitud RPC
-  - `json-formatted`: Salida JSON formateada (multilínea) de la solicitud RPC
-
-###### **Opciones (RPC):**
-
-- `--rpc-url <RPC_URL>` — punto final del servidor RPC
-- `--rpc-header <RPC_HEADERS>` — Encabezado(s) RPC para incluir en las solicitudes al proveedor RPC, ejemplo: "X-API-Key: abc123". Se pueden añadir múltiples encabezados pasando la opción varias veces
-- `--network-passphrase <NETWORK_PASSPHRASE>` — Frase de contraseña de red para firmar la transacción enviada al servidor rpc
-- `-n`, `--network <NETWORK>` — Nombre de la red a usar según la configuración
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/IDEs.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/IDEs.mdx
deleted file mode 100644
index 028d6cc2dc..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/IDEs.mdx
+++ /dev/null
@@ -1,7 +0,0 @@
----
-title: IDE
-description: Explorar IDEs para Stellar.
-sidebar_label: IDE
-sidebar_position: 70
-draft: true
----
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/README.mdx
deleted file mode 100644
index ad6b836123..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Herramientas para Desarrolladores; Crear, Probar, Desplegar Aplicaciones y Configurar Rampas con SDKs y APIs
-description: Descubre herramientas para desarrolladores para crear, probar, desplegar aplicaciones y configurar rampas. Explora SDKs, APIs y más para agilizar el desarrollo en la red Stellar.
-sidebar_label: Más herramientas de desarrollador
-sidebar_position: 50
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Más herramientas de desarrollador
-
-Consulta aún más herramientas útiles creadas por SDF y la comunidad en esta sección.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/_category_.json
deleted file mode 100644
index 9e3a55f459..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": true
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/ai-bot.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/ai-bot.mdx
deleted file mode 100644
index aab0133d72..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/ai-bot.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Bot de IA (Stella)
-description: Stella es un bot de IA que te ayudará con todas tus preguntas sobre Stellar
-sidebar_label: Bot de IA Stella
-sidebar_position: 117
----
-
-# Conoce a Stella
-
-Tu asistente de IA para el desarrollo en Stellar. Stella es una asistente de IA para ayudar a desarrolladores y usuarios con preguntas sobre la cadena de bloques Stellar y los contratos inteligentes.
-
-**¡Ahora en Beta!** Estamos pilotando Stella para facilitar el desarrollo en Stellar. Tus [comentarios](#help-us-improve) nos ayudan a mejorar esta experiencia para toda la comunidad.
-
-Puedes chatear con Stella aquí mismo haciendo clic en el ícono amarillo al final de esta página, o unirte al canal #stella-help en el [Discord de desarrolladores de Stellar](https://discord.gg/stellardev).
-
-## Fuentes de conocimiento
-
-Stella extrae información de una base de conocimientos extensa, que incluye:
-
-- Stack Overflow: Soluciones reales y respuestas validadas por la comunidad
-- Manual SCF: Ideas profundas sobre los procesos del Fondo Comunitario Stellar
-- Contenido de YouTube: Tutoriales, demostraciones y charlas de conferencias del ecosistema Stellar
-- Repositorios de GitHub: Ejemplos de código y patrones de implementación
-
-## Ayúdanos a mejorar
-
-¡Esperamos tus comentarios! Usa 👍/👎 para calificar las respuestas o haz clic en "Agregar comentario" para compartir sugerencias específicas. Cada aporte nos ayuda a mejorar a Stella para todos los desarrolladores.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/analytics-platforms.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/analytics-platforms.mdx
deleted file mode 100644
index 8bfee17d08..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/analytics-platforms.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Plataformas de Análisis
-description: Explora la historia completa de los datos de la red Stellar.
-sidebar_label: Plataformas de Análisis
-sidebar_position: 18
----
-
-# Plataformas de Análisis
-
-There's a wide range of analytics platforms that make exploring Stellar network data easy and fun! The following platforms allow you to easily create aggregates, visualizations, and dashboards to figure out exactly the story you want to tell, with Stellar data..
-
-### [Artemis](https://app.artemisanalytics.com/project/stellar?from=projects)
-
-Artemis te permite evaluar, comparar y analizar cadenas y dApps en tendencia a través de varias métricas en un solo terminal. Ofrecen paneles de control preconstruidos y la capacidad de crear los tuyos propios
-
-### [Dune](https://dune.com/)
-
-Dune es una plataforma basada en la web que te permite consultar datos de la red Stellar y agregarlos en bellos paneles de control.
-
-### [DappRadar](https://dappradar.com/chain/stellar)
-
-Descubre y sigue dapps en la red Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/anchor-tools.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/anchor-tools.mdx
deleted file mode 100644
index 5240fbdb6b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/anchor-tools.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Herramientas de Anchor
-description: Explora un conjunto de herramientas para desarrolladores para Stellar, incluyendo el directorio de anclajes, billetera de demostración y Polaris.
-sidebar_label: Herramientas de Anchor
-sidebar_position: 20
----
-
-# Herramientas de Anchor
-
-### [Directorio de Anclajes](https://anchors.stellar.org/?)
-
-Visualiza todos los anclajes en Stellar, sus monedas y dónde operan.
-
-### [Billetera de Demostración](https://demo-wallet.stellar.org/)
-
-Una aplicación para probar interactivamente los servicios de anclaje. Permite a los desarrolladores de aplicaciones financieras probar sus integraciones y aprender cómo funcionan los protocolos del ecosistema Stellar (SEPs); utiliza la billetera de demostración para probar Activos Regulados (SEP-8), Depósito y Retirada de Fondos (SEP-24), y Pagos Transnacionales (SEP-31) con cualquier dominio local que tenga un Archivo de Información de Stellar (también conocido como SEP-1, o un archivo stellar.toml).
-
-### [Suite de Pruebas de Anchor](https://anchor-tests.stellar.org/)
-
-Una suite de pruebas para validar los servidores de transferencia SEP6, SEP24, SEP31.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/asset-tools.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/asset-tools.mdx
deleted file mode 100644
index f81a203921..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/asset-tools.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Sandbox de Activos
-description: Explorar un conjunto de herramientas para desarrolladores de Stellar, incluido el sandbox de activos.
-sidebar_label: Sandbox de Activos
-sidebar_position: 30
----
-
-# Sandbox de Activos
-
-### [Sandbox de Activos](https://stellar.cheesecakelabs.com/?utm_source=stellar&utm_medium=landing-page&utm_campaign=stellar-asset-sandbox)
-
-Un sandbox admitido por SDF y Cheesecake Labs para que las empresas experimenten con la emisión de activos en la red de prueba de Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/block-explorers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/block-explorers.mdx
deleted file mode 100644
index 10d3160fb4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/block-explorers.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Exploradores de Bloques
-description: Explorar un conjunto de herramientas para desarrolladores de Stellar, incluyendo exploradores de bloques.
-sidebar_label: Exploradores de Bloques
-sidebar_position: 40
----
-
-# Exploradores de Bloques
-
-Los exploradores de bloques existen para mostrar públicamente los datos de la blockchain de una manera fácilmente digerible. Se pueden explorar con un navegador web ordinario y no requieren habilidades especiales de desarrollador para usarlos. Los exploradores de bloques disponibles para Soroban indexan datos relacionados con pagos, cuentas, contratos desplegados, historial de transacciones y más.
-
-### [StellarExpert](https://stellar.expert/explorer/public)
-
-Explora transacciones y actividad de la red con StellarExpert. Consulta las estadísticas específicas de un código de activo, hash de transacción, dirección de cuenta o número de secuencia de ledger. No disponible para Futurenet.
-
-### [StellarChain](https://stellarchain.io/)
-
-Explora transacciones y actividad de la red para las redes de Stellar, incluyendo Futurenet.
-
-### [Stellar Explorer](https://steexp.com/)
-
-Consulta datos relacionados con pagos, cuentas, contratos desplegados y más para el Futurenet, Testnet y Mainnet de Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/jupyter-notebooks.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/jupyter-notebooks.mdx
deleted file mode 100644
index 602ce59a1f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/jupyter-notebooks.mdx
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Cuadernos Jupyter
-description: Experimenta con contratos en Jupyter Notebooks
-sidebar_label: Cuadernos Jupyter
-sidebar_position: 71
----
-
-# Cuadernos Jupyter
-
-Los Jupyter Notebooks son un formato de documento que puede incluir código, texto y otros resultados enriquecidos. Y con la configuración adecuada admiten contratos Soroban Rust.
-
-Para utilizar contratos Soroban en un Jupyter Notebook, se requiere la siguiente configuración. La siguiente configuración utiliza Visual Studio Code, pero se puede usar cualquier cliente y servidor Jupyter.
-
-:::caution
-
-El soporte de Rust en Jupyter Notebooks es experimental. Puedes encontrar errores o comportamientos inesperados.
-
-:::
-
-## Comenzar
-
-1. Instala [Visual Studio Code] (VSCode)
-
-2. Instala la [extensión Jupyter Notebook] en VSCode
-
-3. Instala el núcleo Jupyter de Rust `evcxr` con:
-   ```
-   cargo install --locked evcxr_jupyter
-   evcxr_jupyter --install
-   ```
-
-4. Ejecuta el comando `Crear: Nuevo Jupyter Notebook` en VSCode
-
-5. Haz clic en el botón `Seleccionar kernel` en la parte superior derecha
-
-6. Selecciona `Jupyter Kernel...`
-
-7. Selecciona `Rust` buscando Rust
-
-8. Ingresa en la primera línea una importación de la dependencia `soroban-sdk` con la característica `testutils` habilitada.
-   ```rust
-   :dep soroban-sdk = { version = "22.0.7", features = ["testutils"] }
-   ```
-
-9. Ingresa un contrato. Por ejemplo:
-
-   ```rust
-   use soroban_sdk::{contract, contractimpl};
-
-   #[contract]
-   pub struct Contract;
-
-   #[contractimpl]
-   impl Contract {
-       pub fn add(x: u32, y: u32) -> u32 {
-           x+y
-       }
-   }
-   ```
-
-10. Ingresa algún código para crear un entorno Soroban, registrar el contrato y invocarlo.
-
-```rust
-use soroban_sdk::{Env};
-
-let env = Env::default();
-let id = env.register(Contract, ());
-let client: ContractClient = ContractClient::new(&env, &id);
-client.add(&1, &2)
-```
-
-11. Haz clic en el botón de reproducir para ejecutar el código.
-
-Felicidades, tienes un Jupyter Notebook con código de contrato que debería verse algo así como la captura de pantalla a continuación, listo para hackear y experimentar.
-
-## Captura de pantalla
-
-![Un cuaderno de Jupyter en ejecución](/assets/dev-tools/jupyter-notebooks.png)
-
-## Comunidad
-
-¿Tienes ideas sobre cómo mejorar los contratos Soroban en Jupyter Notebooks? Únete a la comunidad en [Discord].
-
-[Discord]: https://discord.com/channels/897514728459468821/1263811925813366794
-[Visual Studio Code]: https://code.visualstudio.com
-[Extensión Jupyter Notebook]: https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter
-[Jupyter Desktop]: https://github.com/jupyterlab/jupyterlab-desktop
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/network-insights.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/network-insights.mdx
deleted file mode 100644
index 2d6cab89fe..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/network-insights.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Información de la Red
-description: Herramientas para encontrar información única sobre la red Stellar
-sidebar_label: Información de la Red
-sidebar_position: 85
----
-
-# Información de la Red
-
-### [StellarFee](https://stellarfee.expert/)
-
-Una herramienta GUI que es un útil estimador de tarifas, simulador de transacciones para encontrar los recursos consumidos y las tarifas esperadas para una transacción.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/network-status.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/network-status.mdx
deleted file mode 100644
index 82b2949802..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/network-status.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Estado de la Red
-description: Explorar un conjunto de herramientas para desarrolladores para monitorear el estado de la red Stellar.
-sidebar_label: Estado de la Red
-sidebar_position: 90
----
-
-# Estado de la Red
-
-### [Tablero](https://dashboard.stellar.org/)
-
-Muestra el estado actual de Testnet y Mainnet. Monitorea estadísticas de tarifas, operaciones recientes, suministro de lumen y más.
-
-### [Stellarbeat](https://stellarbeat.io/)
-
-Visualiza los nodos de la red Stellar y el consenso.
-
-### [Página de Estado](https://status.stellar.org/)
-
-Rastrea incidentes de la red y mantenimiento programado para Testnet y Mainnet. Suscríbete a actualizaciones para ser notificado sobre eventos importantes, incluyendo mejoras de protocolo y reinicios de Testnet.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/node-operator-tools.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/node-operator-tools.mdx
deleted file mode 100644
index 40ecd7374f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/node-operator-tools.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Herramientas para Operadores de Nodo
-description: Explora un conjunto de herramientas para desarrolladores de Stellar, incluidas las herramientas para operadores de nodo.
-sidebar_label: Herramientas para Operadores de Nodo
-sidebar_position: 100
----
-
-# Herramientas para Operadores de Nodo
-
-### [Repositorio de GitHub](https://github.com/stellar/go-stellar-sdk/tree/master/tools)
-
-Un repositorio de GitHub con herramientas como Stellar Archivist (para el mantenimiento del archivo de Stellar Core) y Horizon cmp (compara las respuestas de dos servidores Horizon).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/openzeppelin-contracts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/openzeppelin-contracts.mdx
deleted file mode 100644
index fdca3bd16f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/openzeppelin-contracts.mdx
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: OpenZeppelin Stellar Contracts
-description: Biblioteca de contratos y asistente de contratos OpenZeppelin Stellar
-sidebar_label: OpenZeppelin Contracts
-sidebar_position: 105
----
-
-<script async src="https://wizard.openzeppelin.com/build/embed.js"></script>
-
-Para llevar contratos inteligentes probados a la comunidad de desarrolladores de Stellar, OpenZeppelin contribuye activamente a una biblioteca de contratos inteligentes y extensiones, así como a herramientas para desarrolladores.
-
-## Comenzar con Contract Wizard
-
-[El asistente de contratos de OpenZeppelin](https://wizard.openzeppelin.com/stellar) incluye soporte para contratos inteligentes basado en Rust de Stellar, facilitando a los desarrolladores la generación y despliegue de contratos seguros y auditados. Después de seleccionar la plantilla y opciones deseadas, puedes descargarla como un archivo único, un paquete de desarrollo Rust o un [Paquete Scaffold Stellar](./scaffold-stellar). Pruébalo a continuación o visita el asistente [aquí](https://wizard.openzeppelin.com/stellar).
-
-<oz-wizard data-lang="stellar"></oz-wizard>
-
-¡Para una guía sobre cómo usar estos contratos, mira el video vinculado abajo!
-
-<iframe
-  width="560"
-  height="315"
-  src="https://www.youtube.com/embed/iD7ZspsZLVo?si=TvAo70F1mA0pDWz6&amp;amp;controls=1"
-  title="YouTube video player"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
-  referrerpolicy="strict-origin-when-cross-origin"
-  allowfullscreen
-></iframe>
-
-## Contratos y utilidades OpenZeppelin Stellar
-
-OpenZeppelin Stellar Contracts es una colección de contratos y utilidades auditados para Stellar. Los contratos son desarrollados por OpenZeppelin en colaboración con la comunidad de Stellar y la Stellar Development Foundation (SDF), con el objetivo de ofrecer una biblioteca de contratos de alta calidad y auditados para construir aplicaciones en la red Stellar.
-
-### Módulos auditados disponibles
-
-**Token fungible**
-
-- Extensiones:
-  - **Burnable**: Permite a los tenedores de tokens destruir sus tokens
-  - **Capped**: Establece límites máximos de suministro
-  - **Allowlist**: Restringe transferencias a direcciones aprobadas
-  - **Blocklist**: Previene transferencias desde/hacia direcciones bloqueadas
-
-**Token no fungible**
-
-- Extensiones:
-  - **Burnable**: Permite a los tenedores destruir sus NFTs
-  - **Enumerable**: Habilita iteración sobre todos los tokens y tokens de un propietario
-  - **Consecutive**: Permite acuñar múltiples tokens en lotes de forma eficiente
-  - **Royalties**: Soporta regalías para creadores en ventas secundarias
-
-**Token Stablecoin**
-
-- Extensiones:
-  - **Burnable**: Permite a los tenedores destruir sus tokens
-  - **Capped**: Establece límites máximos de suministro
-  - **Allowlist**: Restringe transferencias a direcciones aprobadas
-  - **Blocklist**: Previene transferencias desde/hacia direcciones bloqueadas
-
-**Utilidades**
-
-- **Utilidades pausables y actualizables**
-- **Control de acceso basado en roles y propiedad**
-- **Distribuidor Merkle**
-
-**Próximamente**
-
-- Token de seguridad (ERC-3643)
-- Multisig
-- Firmante Passkey
-- Bóveda de tokens (ERC-4626)
-
-Estas implementaciones se irán lanzando con el tiempo, asegurando que los desarrolladores de Stellar tengan acceso a opciones extensibles de contratos. Todos los contratos y extensiones son auditados por el equipo de seguridad de OpenZeppelin, mejorando la seguridad y confiabilidad de los contratos y extensiones. Para usar la biblioteca, por favor visita: https://github.com/OpenZeppelin/stellar-contracts.
-
-```
-Repository Structure
-│── audits/                    # Audit reports
-│── docs/                      # Documentation
-│── examples/                  # Example contracts
-│── packages/
-│   ├── tokens/                # Various token types (fungible, non-fungible, etc.)
-│   ├── contract-utils/        # Utilities for token types (pausable, upgradable, etc.)
-│   ├── constants/             # Shared constants
-│   ├── test-utils/            # Utilities for tests
-
-```
-
-Para enviar comentarios, por favor abre issues aquí: [https://github.com/OpenZeppelin/stellar-contracts/issues](https://github.com/OpenZeppelin/stellar-contracts/issues)
-
-## Documentación de OpenZeppelin Stellar Contracts
-
-Para documentación adicional sobre contratos inteligentes Stellar de OpenZeppelin, por favor visita: [https://docs.openzeppelin.com/stellar-contracts](https://docs.openzeppelin.com/stellar-contracts/.).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/openzepplin-contracts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/openzepplin-contracts.mdx
deleted file mode 100644
index 024b6cbe83..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/openzepplin-contracts.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Contratos Stellar de OpenZeppelin
-description: Biblioteca de Contratos y Asistente de Contratos de OpenZeppelin Stellar
-sidebar_label: Contratos Stellar de OpenZeppelin
-sidebar_position: 105
----
-
-Para llevar contratos inteligentes probados en batalla a la comunidad de desarrolladores de Stellar, OpenZeppelin está contribuyendo activamente a una biblioteca de contratos inteligentes y extensiones, así como a herramientas de desarrollo.
-
-## Comenzar con Contract Wizard
-
-![Asistente de contratos](/assets/dev-tools/openzeppelin-contract-wizard.png)
-
-[Contract Wizard de OpenZeppelin](https://wizard.openzeppelin.com/stellar) incluye soporte para contratos inteligentes basados en Rust de Stellar, lo que facilita a los desarrolladores generar y desplegar contratos seguros y auditados. Los desarrolladores pueden aprovechar plantillas de contratos preconstruidas para:
-
-- Tokens Fungibles (FTs)
-- Macros Pausables
-
-Y pronto:
-
-- Tokens No Fungibles (NFTs)
-- Macros Actualizables
-- Estándar Multi-Token
-- Estándar de Token de Seguridad
-- Estándar de Token RWA
-- Estándar de Bóveda de Tokens
-- Y más por venir
-
-Estas implementaciones se lanzarán a lo largo del año, asegurando que los desarrolladores de Stellar tengan acceso a opciones de contratos extensibles. Todos los contratos y extensiones son auditados por el equipo de seguridad de OpenZeppelin, mejorando la seguridad y fiabilidad de los contratos y extensiones.
-
-Para comenzar, visita: https://wizard.openzeppelin.com/stellar.
-
-Para una guía sobre cómo usar estos contratos, consulta: https://www.youtube.com/watch?v=iD7ZspsZLVo.
-
-## Contratos y utilidades de OpenZeppelin Stellar
-
-OpenZeppelin Stellar Contracts es una colección de contratos y utilidades auditadas para Stellar. Los contratos son desarrollados por OpenZeppelin en colaboración con la comunidad de Stellar y la Stellar Development Foundation (SDF), en un esfuerzo por ofrecer una biblioteca de contratos de alta calidad y auditados que puedan ser usados para crear aplicaciones en la red Stellar.
-
-Para usar la biblioteca, por favor ve a: https://github.com/OpenZeppelin/stellar-contracts.
-
-```
-Repository Structure
-│── audits/                    # Audit reports
-│── docs/                      # Documentation
-│── examples/                  # Example contracts
-│── packages/
-│   ├── tokens/                # Various token types (fungible, non-fungible, etc.)
-│   ├── contract-utils/        # Utilities for token types (pausable, upgradable, etc.)
-│   ├── constants/             # Shared constants
-│   ├── test-utils/            # Utilities for tests
-
-```
-
-Para proporcionar comentarios, por favor abre incidencias aquí: https://github.com/OpenZeppelin/stellar-contracts/issues
-
-## Documentos para OpenZeppelin Stellar Contracts
-
-Para obtener documentación adicional sobre contratos inteligentes de Stellar por OpenZeppelin, visita: https://docs.openzeppelin.com/stellar-contracts/.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/scaffold-stellar.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/scaffold-stellar.mdx
deleted file mode 100644
index 7c6febf719..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/scaffold-stellar.mdx
+++ /dev/null
@@ -1,110 +0,0 @@
----
-title: Scaffold Stellar
-description: Kit de herramientas por convención para el desarrollo de contratos inteligentes Stellar
-sidebar_label: Scaffold Stellar
-sidebar_position: 110
----
-
-**Scaffold Stellar** es un kit de herramientas para desarrolladores para crear aplicaciones descentralizadas (dApps) y contratos inteligentes en la blockchain Stellar. Te ayuda a pasar de la idea a una dApp de pila completa funcionando más rápido — proporcionando herramientas CLI, plantillas de contratos reutilizables, un registro de contratos inteligentes y un frontend moderno.
-
-## Requisitos previos
-
-Antes de comenzar, asegúrate de tener instalado lo siguiente:
-
-| Herramienta                                             | Descripción                                                        | Enlace de instalación                                         |
-| ------------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------- |
-| [Rust & Cargo](https://www.rust-lang.org/tools/install) | Para escribir y compilar contratos inteligentes                    | `curl https://sh.rustup.rs -sSf \| sh`                        |
-| [Node.js & npm](https://nodejs.org/)                    | Para el desarrollo del frontend                                    | Descargar desde el sitio oficial                              |
-| [Stellar CLI](https://github.com/stellar/stellar-cli)   | Para construir, desplegar e interactuar con contratos inteligentes | [`Link for the repo`](https://github.com/stellar/stellar-cli) |
-| [Docker](https://www.docker.com/get-started/)           | Para ejecutar una red Stellar local mediante la imagen `stellar/quickstart` | [Descargar Docker Desktop](https://www.docker.com/products/docker-desktop/) |
-
-## Comenzar
-
-### Instalación
-
-Instala las herramientas CLI requeridas:
-
-```bash
-# Install stellar-scaffold CLI
-cargo install stellar-scaffold-cli
-
-# Install registry CLI (to easily deploy your contract to the registry)
-cargo install stellar-registry-cli
-```
-
-### Crear un nuevo proyecto
-
-1. Inicializa un proyecto nuevo:
-
-```bash
-stellar scaffold init my-project
-cd my-project
-```
-
-Ya tendrás varios contratos de ejemplo en el proyecto, o puedes comenzar desde el [Asistente OpenZeppelin](./openzeppelin-contracts) para personalizar tu contrato y crear un proyecto Scaffold Stellar desde allí.
-
-2. Configura tu entorno de desarrollo:
-
-```bash
-# Copy and configure environment variables
-cp .env.example .env
-
-# Install frontend dependencies
-npm install
-```
-
-3. Inicia el entorno de desarrollo:
-
-```bash
-npm run dev
-```
-
-¡Tendrás una dApp en funcionamiento, con un par de contratos para empezar, lista para que comiences a construir!
-
-Explora el archivo `environments.toml` para personalizar tu(s) entorno(s) de desarrollo.
-
-## Estructura del proyecto
-
-Cuando ejecutas `stellar scaffold init`, crea una estructura de proyecto full-stack con contratos de ejemplo y un frontend moderno:
-
-```
-my-project/
-├── contracts/            # Rust smart contracts (compiled to WASM)
-├── packages/            # Auto-generated TypeScript contract clients
-├── src/                # React frontend code
-│   ├── components/     # Reusable UI components
-│   ├── contracts/      # Contract interaction logic
-│   ├── App.tsx        # Main app component
-│   └── main.tsx       # Entry point
-├── environments.toml   # Configuration per environment (dev/test/prod)
-├── .env               # Local environment variables
-├── package.json       # Frontend packages
-└── target/           # Build outputs
-```
-
-Esta plantilla proporciona una aplicación frontend lista para usar con contratos inteligentes de ejemplo y sus clientes TypeScript. El frontend está configurado con `Vite`, `React` e incluye componentes básicos para interactuar con los contratos.
-
-## Características
-
-- **Plugins CLI para Stellar**
-  - `stellar scaffold init`: Inicializar nuevos proyectos de contratos inteligentes Stellar
-  - `stellar scaffold upgrade`: Transformar espacios de trabajo de contratos Stellar existentes en proyectos Scaffold
-  - `stellar scaffold build`: Desarrolla contratos y genera clientes TypeScript
-  - `stellar scaffold watch`: Modo de desarrollo con recarga en caliente
-  - `stellar registry`: Publicar, desplegar y administrar contratos inteligentes
-
-- **Gestión del entorno**
-  - Builds específicos para cada entorno (desarrollo, pruebas, staging, producción)
-  - Integración fluida con contratos locales y desplegados
-  - Configuración de red mediante `environments.toml`
-  - Admitir múltiples entornos de despliegue
-
-- **Registro de contratos inteligentes**
-  - Plataforma on-chain para publicación de binarios Wasm
-  - Gestión de versiones y denominación de contratos
-  - Verificación de contratos y gestión de dependencias
-  - Flujo seguro de despliegue para testnet y mainnet
-
-### Más recursos
-
-Para más información, consulta el [proyecto en GitHub](https://github.com/theahaco/scaffold-stellar)!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/security-tools.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/security-tools.mdx
deleted file mode 100644
index 4d0c79eea1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/security-tools.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Herramientas de Seguridad
-description: Explorar un conjunto de herramientas de seguridad para desarrolladores de Stellar.
-sidebar_label: Herramientas de Seguridad
-sidebar_position: 115
----
-
-# Herramientas de Seguridad
-
-### [Scout: Combatiente de Errores](https://www.coinfabrik.com/products/scout/)
-
-Una herramienta de análisis de código estático desarrollada para ayudar a los desarrolladores y auditores de Soroban a identificar posibles amenazas de seguridad y aplicar prácticas recomendadas.
-
-### [Almanax](https://www.almanax.ai/)
-
-Almanax es un ingeniero de seguridad con IA diseñado para ayudar a los equipos a prevenir ataques.
-
-Almanax utiliza LLMs para identificar vulnerabilidades complejas de seguridad tanto en contratos inteligentes como en código convencional. También se integra con pipelines de CI/CD para detectar automáticamente incidencias antes de que el código llegue a producción.
-
-### [Certora Sunbeam](https://docs.certora.com/en/latest/docs/sunbeam/index.html)
-
-Sunbeam es una herramienta de verificación formal desarrollada por Certora para contratos inteligentes Soroban en la blockchain Stellar. Diseñada específicamente para bytecode WebAssembly (Wasm), Sunbeam verifica el código del contrato desplegado, no solo el código fuente en Rust, eliminando la necesidad de confiar en el compilador Rust. Los desarrolladores escriben propiedades de corrección usando un lenguaje de especificación ligero integrado en Rust, y Sunbeam comprueba rigurosamente que el Wasm compilado cumple esas propiedades.
-
-### [El Portal de Seguridad Soroban](https://sorobansecurity.com)
-
-El Portal de Seguridad Soroban es una plataforma de seguridad desarrollada por Inferara. Es una solución impulsada por la comunidad, basada en una base de datos en constante mantenimiento de auditorías de seguridad e informes de vulnerabilidades relacionados con el desarrollo de contratos inteligentes Soroban. La experiencia del usuario se enriquece con búsqueda semántica y otras funciones, permitiendo una búsqueda fluida y el trabajo con datos relacionados con la seguridad. El Portal también abarca proyectos, auditores, herramientas y muchos más del ecosistema Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/wallets.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/wallets.mdx
deleted file mode 100644
index f4692433f3..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/developer-tools/wallets.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Integración de billeteras
-description: Explorar un conjunto de herramientas para desarrolladores para billeteras Stellar.
-sidebar_label: Integración de billeteras
-sidebar_position: 130
----
-
-# Integración de Billetera
-
-### [Stellar Wallet Kit](https://github.com/Creit-Tech/Stellar-Wallets-Kit/)
-
-Un kit de billetera fácil de usar para gestionar la integración a múltiples billeteras del ecosistema Stellar. Aprende más sobre cómo integrar esta biblioteca desde [la documentación del Kit de Billeteras Stellar](https://stellarwalletskit.dev/).
-
-![Kit de Billeteras Stellar](/assets/dev-tools/stellar-wallet-kit.gif)
-
-El Kit de Billeteras Stellar admite muchas billeteras, incluyendo:
-
-- Albedo
-- Freighter
-- Hana
-- Billetera Hardware Ledger
-- Billetera Hardware Trezor
-- Lobstr
-- Rabet
-- WalletConnect
-- xBull
-- Billetera caliente
-
-### [Account Viewer](https://accountviewer.stellar.org/)
-
-Una billetera simplificada donde puedes verificar el saldo de XLM de una cuenta y enviar pagos simples en Testnet y Mainnet. El [código fuente](https://github.com/stellar/account-viewer-v2) de Account Viewer también es útil e instructivo para los desarrolladores que están desarrollando funciones relacionadas con billeteras en sus aplicaciones.
-
-### [Billetera Freighter](https://www.freighter.app/)
-
-La extensión de billetera no custodial insignia de SDF que permite a los usuarios firmar transacciones Stellar a través de su navegador. El código de la billetera Freighter es de código abierto aquí: https://github.com/stellar/freighter.
-
-### [NEAR Intents](https://docs.near.org/chain-abstraction/intents/overview)
-
-NEAR Intents es un protocolo de transacciones multichain para billeteras que permite a los usuarios o agentes de IA simplemente expresar el resultado que desean (como intercambiar Token A por Token B), y luego permite que una red de formadores de mercado fuera de cadena (llamados solucionadores) compita para cumplir esa solicitud; una vez seleccionada la mejor solución, se envía al usuario para su aprobación, luego se verifica y ejecuta a través de un contrato inteligente Verifier en NEAR.
-
-Lee la [documentación](https://docs.near.org/chain-abstraction/intents/overview).
-
-### [Calculadora de Patrocinio de Billeteras Stellar](https://docs.google.com/spreadsheets/d/1LgVMFRggdjBAxSpI4nxucUmbZIsnUbMPT8RJQ_rJ5k4/edit?gid=1771515065#gid=1771515065)
-
-Estimaciones de los requisitos de XLM para billeteras que buscan usar reservas patrocinadas y transacciones con incremento de tarifa para cubrir la creación de cuentas, tarifas de transacción, trustlines y más.
-
-- [Hoja de cálculo simplificada](https://docs.google.com/spreadsheets/d/1Vhk__s-ZrJLEgEs3N2oGEsI35RKPixD5w-qQ6uGYnO0/edit?gid=270060868#gid=270060868)
-- [Artículo tutorial y video](https://cheesecakelabs.com/blog/stellar-lumens-xlm-cost-estimator/)
-
-### [Dfns](https://www.dfns.co/)
-
-Una plataforma de billetera como servicio que optimiza las operaciones de activos digitales, ofreciendo soporte completo para funciones de billetera, incluyendo la detección automática de saldos de activos y NFT (cuando corresponda), historial de transferencias on-chain, transferencias de activos, transmisión de transacciones y generación de firmas.
-
-Consulta la [documentación](https://docs.dfns.co/d/api-docs/wallets/broadcast-transaction/stellar).
-
-### [Privy](https://docs.privy.io/wallets/overview/chains)
-
-Infraestructura de billetera que permite a los usuarios crear programáticamente una nueva billetera dentro de sus aplicaciones.
-
-Sigue esta [guía](https://docs.privy.io/wallets/wallets/create/create-a-wallet) para crear una billetera Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/infra-tools/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/infra-tools/README.mdx
deleted file mode 100644
index ee45fea933..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/infra-tools/README.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Herramientas de infraestructura
-sidebar_position: 70
----
-
-import DocCardList from "@theme/DocCardList";
-
-Una lista de herramientas de red e infraestructura para Stellar.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/infra-tools/cross-chain.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/infra-tools/cross-chain.mdx
deleted file mode 100644
index 45e6900558..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/infra-tools/cross-chain.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Cross-Chain
-sidebar_label: Cross-Chain
-sidebar_position: 10
----
-
-Puentes y capas de mensajería que conectan distintas blockchains.
-
-## [Axelar](https://www.axelar.network/)
-
-Axelar Network es la red universal de interoperabilidad que conecta de forma segura todos los ecosistemas blockchain, aplicaciones, activos y usuarios.
-
-Configúrate para escribir contratos inteligentes cross-chain en Stellar usando Axelar en las siguientes guías.
-
-### Conoce los contratos Stellar GMP
-
-General Message Passing (GMP) es un protocolo de comunicación cross-chain que permite que contratos inteligentes en distintas blockchains se comuniquen entre sí. Con GMP, los contratos Stellar pueden:
-
-- Enviar mensajes a contratos en otras cadenas como Ethereum, Avalanche, Base, Polygon, etc.
-- Recibir y procesar mensajes de contratos en otras cadenas.
-- Ejecutar operaciones cross-chain de forma segura y eficiente.
-
-[Explorar la documentación de Stellar GMP →](https://docs.axelar.dev/dev/general-message-passing/stellar-gmp/intro/)
-
-### Conoce el Servicio de Token Intercadena (ITS) de Stellar
-
-El Servicio de Token Intercadena (ITS) permite que los tokens escalen a través de múltiples cadenas admitiendo tanto tokens existentes como recién acuñados, preservando la fungibilidad y funcionalidad nativa en cadenas EVM conectadas, y automatizando el despliegue y mantenimiento para ayudar a los equipos a manejar fácilmente el suministro en una red abierta, escalable y segura. Para el ecosistema Stellar, ITS ofrece:
-
-- Creación de nuevos tokens que pueden existir en múltiples blockchains.
-- Conexión de tokens Stellar existentes con otros ecosistemas blockchain.
-- Transferencias seguras de tokens entre Stellar y otras cadenas.
-
-[Aprende a usar ITS de Axelar con Stellar →](https://docs.axelar.dev/dev/send-tokens/stellar/intro/)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/README.mdx
deleted file mode 100644
index bf61fd504a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/README.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Laboratorio
-description: Explora Laboratorio, una herramienta de desarrollador para aprender sobre la red Stellar
-sidebar_label: Laboratorio
-sidebar_position: 30
----
-
-# Laboratorio
-
-### [Laboratorio Stellar](https://lab.stellar.org)
-
-Laboratorio Stellar es nuestra nueva herramienta para el desarrollo, la experimentación y las pruebas, así como para explorar las APIs que los desarrolladores utilizan para interactuar con la red Stellar. Ya seas un desarrollador que busca probar transacciones, explorar métodos RPC o puntos finales de Horizon, o profundizar en el ecosistema, Laboratorio Stellar proporciona una interfaz moderna y fácil de usar que hace que el proceso sea fluido e intuitivo.
-
-![Laboratorio: Página de inicio](/assets/lab/lab.png)
-
-### Características de Laboratorio Stellar
-
-- Crea Cuentas Fácilmente: Crea cuentas en Mainnet, Testnet y Futurenet utilizando una interfaz web. Puedes usar Friendbot para financiar esas cuentas directamente en Laboratorio para Testnet y Futurenet.
-- Accede a Métodos RPC y Puntos Finales de Horizon: Aprovecha potentes métodos RPC de Stellar y puntos finales de Stellar Horizon en una interfaz web para interactuar con la red Stellar y obtener datos cruciales. Prueba los métodos RPC para obtener estados del ledger como cuentas, trustlines, contrato wasm, y más.
-- Simular y Enviar: Laboratorio admite la capacidad de usar proveedores RPC personalizados para que puedas simular transacciones, guardar transacciones y enviar transacciones directamente usando Laboratorio. También puedes enviar transacciones usando Horizon.
-- Guarda y Comparte Solicitudes API: Guarda fácilmente tus solicitudes y transacciones para el futuro o compártelas con compañeros de equipo para crear más rápido juntos.
-- Soporte XDR ⇔ JSON: Hemos introducido un mapeo canónico [XDR a JSON](https://www.npmjs.com/package/@stellar/stellar-xdr-json-web) que se utiliza en Laboratorio Stellar (también utilizado en el [CLI de Stellar](https://github.com/stellar/stellar-cli)). Puedes verlo en acción en el Laboratorio donde [XDR se puede convertir a JSON](https://lab.stellar.org/xdr/view).
-- Compatible con Móviles: Escuchamos que usas Laboratorio en móviles, así que optimizamos Laboratorio para tener un diseño responsivo para móviles.
-
-![Laboratorio XDR a JSON](/assets/lab/xdr-json-lab.png)
-
-Estas son las características que están disponibles ahora. Habrá más características próximas para apoyar contratos inteligentes. Esperamos poder mostrarte el futuro de Laboratorio Stellar.
-
-### Tutorial en Video para Laboratorio Stellar
-
-- Video tutorial para el laboratorio de la [reunión de desarrolladores del 2024-11-14](/meetings/2024/11/14)
-
-### ¿Qué pasa con el Antiguo Laboratorio?
-
-En caso de que lo necesites, la versión anterior de Laboratorio Stellar aún es accesible [aquí](https://old-lab.stellar.org). Sin embargo, ya no se mantendrá activamente. Te animamos a explorar el nuevo Lab y, si crees que falta algo, por favor contáctanos en el [Stellar Github](https://github.com/stellar/laboratory/issues).
-
-### ¡Ayúdanos a Mejorar!
-
-Estamos comprometidos a hacer que Laboratorio Stellar sea aún mejor. Si tienes alguna solicitud de características, por favor envíalas en [Github](https://github.com/stellar/laboratory/issues). Tu opinión es importante para nosotros en las iteraciones del producto y en moldear el futuro de Laboratorio Stellar.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/account.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/account.mdx
deleted file mode 100644
index 45aa82b27f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/account.mdx
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Cuenta
-description: Explora la página de la cuenta de Stellar Lab creando y financiando una cuenta en Stellar
-sidebar_position: 10
----
-
-# Cuenta
-
-## [Crear llave de cuenta Keypair](https://lab.stellar.org/account/create)
-
-![Lab: Crear cuenta](/assets/lab/lab-account-create.png)
-
-Desde la navegación principal del Laboratorio, haz clic en el enlace "Cuenta" para expandir la subnavegación. Haz clic en la página "Crear Par de Claves de Cuenta". Aquí puedes generar un [par de claves](../../learn/glossary.mdx#keypair) siguiendo estos pasos:
-
-1. Asegúrate de que estás en la red Stellar para la que quieres generar la llave. Puedes ver la red actual en la esquina superior derecha de la página. Haz clic en el menú desplegable para cambiar la red (no olvides proporcionar la información necesaria). Usaremos la red Testnet para este ejemplo.
-2. Haz clic en el botón "Generar llaves" para crear las llaves públicas y secretas para una cuenta. Guárdalas en un lugar seguro, incluso si solo se utilizan para pruebas.
-
-:::warning
-
-Cualquiera con la llave secreta de la cuenta tiene acceso total y control sobre la cuenta. Mantén la llave secreta a salvo.
-
-:::
-
-3. Una cuenta está activa solo una vez que está financiada. Puedes usar Friendbot para financiarla solo en las redes Testnet y Futurenet. Haz clic en el botón "Financiar cuenta con Friendbot" para agregar 10.000 XLM a la cuenta. Cuando la operación finaliza, se mostrará un mensaje en la parte inferior.
-
-:::info
-
-El Friendbot se puede utilizar para una nueva cuenta o cuentas con saldo inferior a un saldo inicial de 10.000 XLM. Haz clic nuevamente en el botón "Financiar cuenta con Friendbot" para ver qué sucede. ¡Es el Lab, así que siéntete libre de experimentar (mientras estés en la red Testnet o Futurenet)!
-
-:::
-
-4. Opcionalmente, para guardar la llave Keypair generada, haz clic en el botón "Guardar llave". Ingresa el nombre en el pop-up y haz clic en el botón "Guardar" para almacenar la llave en el almacenamiento local del navegador. Haz clic en el enlace "Guardado" en el menú principal para expandir el submenú, luego haz clic en el enlace "[Keypairs](./saved/keypairs)" para ver los keypairs guardados. La función de guardar está disponible solo en las redes Testnet y Futurenet.
-
-## [Financiar cuenta](https://lab.stellar.org/account/fund)
-
-![Lab: Financiar cuenta](/assets/lab/lab-account-fund.png)
-
-Si ya tienes un par de claves que quieres financiar, ve a la página "Financiar Cuenta" (bajo el ítem "Cuenta" en el menú principal).
-
-1. Si has generado una llave keypair en la página "Crear llave de cuenta Keypair", puedes usar su llave pública haciendo clic en el botón "Rellenar la llave generada". El botón estará deshabilitado si no hay llave keypair.
-2. Siempre puedes ingresar manualmente una llave pública.
-3. Una vez que ingreses la llave pública, haz clic en el botón "Obtener lumens" para financiar la cuenta con 10.000 XLM en la red Testnet o Futurenet.
-4. Verás un mensaje de respuesta una vez que la operación se haya completado.
-
-:::info
-
-También puedes crear una cuenta usando un SDK de Stellar. Sigue una guía [aquí](../../build/guides/transactions/create-account.mdx).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/README.mdx
deleted file mode 100644
index 00c3ab56cd..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/README.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Explorador de API
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Herramientas para Desarrolladores
-
-Esta sección demuestra cómo utilizar los métodos RPC y los endpoints de Horizon en el Laboratorio Stellar a través de diferentes redes, incluyendo características como compartir URLs y guardar solicitudes para su uso futuro.
-
-Puedes explorar los diferentes endpoints del RPC y Horizon, hacer solicitudes a estos endpoints y guardarlas para su uso futuro.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/horizon-endpoint.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/horizon-endpoint.mdx
deleted file mode 100644
index 09c12d27c4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/horizon-endpoint.mdx
+++ /dev/null
@@ -1,356 +0,0 @@
-# Puntos finales de Horizon
-
-:::warning
-
-Horizon se considera obsoleto. Recibirá los cambios necesarios para admitir las actualizaciones del protocolo, pero no lanzará nuevas funciones. Considera cambiar a [Stellar RPC u otro producto de datos](../../../data/apis/README.mdx).
-
-:::
-
-Horizon proporciona una API HTTP para acceder a los datos almacenados en la red Stellar. Esta API actúa como un puente entre las aplicaciones y Stellar Core. El [Explorador de API](https://lab.stellar.org/endpoints) del Stellar Lab ofrece una interfaz de usuario para los puntos finales de Horizon, permitiendo a los desarrolladores interactuar con Horizon en Futurenet, Testnet, Mainnet y redes personalizadas. Los desarrolladores pueden usar Stellar Lab para crear y enviar transacciones, consultar saldos de cuentas y transmitir eventos como transacciones para una cuenta.
-
-Los datos en el ledger de Stellar están organizados en [recursos](../../../data/apis/horizon/api-reference/resources): **Cuentas, Activos, Saldos reclamables, Efectos, Ledgers, Fondos de Liquidez, Ofertas, Operaciones, Negociaciones** y **Transacciones**. Cada recurso tiene múltiples puntos finales. Los puntos finales que agregan datos de ledger (también conocidos como [agregaciones](../../../data/apis/horizon/api-reference/aggregations)) incluyen recursos como **Libros de órdenes, Rutas, Agregaciones de comercio** y **Estadísticas de tarifas**.
-
-Los puntos finales de Horizon de Stellar Lab listan cada tipo de recurso en el menú, lo que permite a los desarrolladores interactuar con sus respectivos endpoints.
-
-![Lab: Página de Horizon](/assets/lab/horizon-endpoints.png)
-
-:::info
-
-Para obtener información detallada sobre cada punto final en una página, haz clic en el enlace **Ver Docs** en el encabezado para acceder a su documentación de referencia de API.
-
-:::
-
-![Lab: Horizon - Ver Docs](/assets/lab/lab-horizon-view-docs.png)
-
-## Ejemplos de puntos finales de Horizon
-
-Exploraremos varias ejemplos de puntos finales de Horizon en Testnet y Mainnet. También tenemos [documentación sobre cómo configurar un entorno local de red Stellar](../quickstart-with-lab) si estás interesado en usar un entorno local. Esto demostrará cómo usar el Lab para acceder a estos puntos finales.
-
-- [Cuenta única](#single-account): `/accounts/:account-id`
-- [Pagos para Cuenta](#payments-for-account): `/accounts/:account-id/payments`
-- [Todos los activos](#all-assets): `/assets`
-
-### [Cuenta única](https://lab.stellar.org/endpoints/accounts/single)
-
-El punto final de cuenta única `/accounts/:account-id` proporciona información sobre una cuenta específica. Este ejemplo usa una cuenta `GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F` en Testnet.
-
-![Lab: Horizon - Cuenta única](/assets/lab/lab-single-account.png)
-
-Cuando hago clic en el botón **Enviar**, el punto final de cuenta devuelve los detalles de la cuenta en formato `JSON`. Los desarrolladores pueden usar la funcionalidad **Copiar JSON** para copiar y pegar la respuesta. Junto con los detalles de la cuenta, como `id`, `balances` de la cuenta, incluyendo los activos a los que la cuenta tiene establecida su trustline, `thresholds`, `flags` y `signers` (3 signers en la cuenta de ejemplo).
-
-El punto final también proporciona enlaces a páginas de recursos relacionados en el Stellar Lab para la cuenta consultada. Por ejemplo, la respuesta incluye `transactions`, `operations`, `payments` y más bajo `_links`. Al hacer clic en un `href` de transacción lleva a los desarrolladores a la [Página de Transacciones para Cuenta](https://lab.stellar.org/endpoints/transactions/account?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$account_id=GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F;;) en el Stellar Lab donde los desarrolladores pueden consultar transacciones para esa cuenta de inmediato.
-
-![Lab: Horizon - Respuesta de Cuenta Única](/assets/lab/lab-single-account-response.png)
-
-```{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F"
-    },
-    "transactions": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/transactions{?cursor,limit,order}",
-      "templated": true
-    },
-    "operations": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/operations{?cursor,limit,order}",
-      "templated": true
-    },
-    "payments": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/payments{?cursor,limit,order}",
-      "templated": true
-    },
-    "effects": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/effects{?cursor,limit,order}",
-      "templated": true
-    },
-    "offers": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/offers{?cursor,limit,order}",
-      "templated": true
-    },
-    "trades": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/trades{?cursor,limit,order}",
-      "templated": true
-    },
-    "data": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/data/{key}",
-      "templated": true
-    }
-  },
-  "id": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F",
-  "account_id": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F",
-  "sequence": "4113457683103748",
-  "sequence_ledger": 958608,
-  "sequence_time": "1731620848",
-  "subentry_count": 3,
-  "last_modified_ledger": 958608,
-  "last_modified_time": "2024-11-14T21:47:28Z",
-  "thresholds": {
-    "low_threshold": 5,
-    "med_threshold": 5,
-    "high_threshold": 5
-  },
-  "flags": {
-    "auth_required": false,
-    "auth_revocable": false,
-    "auth_immutable": false,
-    "auth_clawback_enabled": false
-  },
-  "balances": [
-    {
-      "balance": "0.0000000",
-      "limit": "922337203685.4775807",
-      "buying_liabilities": "0.0000000",
-      "selling_liabilities": "0.0000000",
-      "last_modified_ledger": 958608,
-      "is_authorized": true,
-      "is_authorized_to_maintain_liabilities": true,
-      "asset_type": "credit_alphanum4",
-      "asset_code": "USDC",
-      "asset_issuer": "GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5"
-    },
-    {
-      "balance": "9990.9999400",
-      "buying_liabilities": "0.0000000",
-      "selling_liabilities": "0.0000000",
-      "asset_type": "native"
-    }
-  ],
-  "signers": [
-    {
-      "weight": 2,
-      "key": "GAGOOY3NKKNEXDOVKTKIP2AUCT6ZOQD4SMWAB54TSHTAXATLJSVVDJCZ",
-      "type": "ed25519_public_key"
-    },
-    {
-      "weight": 1,
-      "key": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F",
-      "type": "ed25519_public_key"
-    },
-    {
-      "weight": 2,
-      "key": "GDFHN4ILDFEBM5YHW6MYOQIRNY3EQ7VV72IW3YIAZNXDW363SUAK7BBL",
-      "type": "ed25519_public_key"
-    }
-  ],
-  "data": {},
-  "num_sponsoring": 0,
-  "num_sponsored": 0,
-  "paging_token": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F"
-}
-```
-
-### [Pagos para Cuenta](https://lab.stellar.org/endpoints/payments/account)
-
-El punto final de pagos para cuenta `/accounts/:account-id/payments` proporciona pagos exitosos para una cuenta dada y puede ser usado en modo de transmisión. Vamos a usar la misma cuenta que usamos en el ejemplo anterior: `GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F`.
-
-![Lab: Horizon - Pagos](/assets/lab/horizon-payments.png)
-
-Cuando hago clic en el botón **Submit**, el endpoint devuelve los registros de pagos (consulta la [referencia de la API](../../../data/apis/horizon/api-reference/get-payments-by-account-id.api.mdx) para más información sobre el formato de la respuesta), incluyendo el [objeto payment](../../../data/apis/horizon/api-reference/resources/payments/object.mdx) que fueron enviados con éxito en la cuenta en formato `JSON`.
-
-![Lab: Horizon - Respuesta de Pagos](/assets/lab/horizon-payments-response.png)
-
-```
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/payments?cursor=&limit=10&order=asc"
-    },
-    "next": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/payments?cursor=4115390418391041&limit=10&order=asc"
-    },
-    "prev": {
-      "href": "https://horizon-testnet.stellar.org/accounts/GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F/payments?cursor=4113457683111937&limit=10&order=desc"
-    }
-  },
-  "_embedded": {
-    "records": [
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/4113457683111937"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/b86ad0433bd024d37739b803529e77601bceb83976d6ae328a61f8f0f8300cb6"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/4113457683111937/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc&cursor=4113457683111937"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc&cursor=4113457683111937"
-          }
-        },
-        "id": "4113457683111937",
-        "paging_token": "4113457683111937",
-        "transaction_successful": true,
-        "source_account": "GAIH3ULLFQ4DGSECF2AR555KZ4KNDGEKN4AFI4SU2M7B43MGK3QJZNSR",
-        "type": "create_account",
-        "type_i": 0,
-        "created_at": "2024-11-14T20:34:58Z",
-        "transaction_hash": "b86ad0433bd024d37739b803529e77601bceb83976d6ae328a61f8f0f8300cb6",
-        "starting_balance": "10000.0000000",
-        "funder": "GAIH3ULLFQ4DGSECF2AR555KZ4KNDGEKN4AFI4SU2M7B43MGK3QJZNSR",
-        "account": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F"
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/4113586532130817"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/bbc6b423efb9c5a8ebb1ac72437a326ffd4b8a202782157f9a9bca38f742f7d7"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/4113586532130817/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc&cursor=4113586532130817"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc&cursor=4113586532130817"
-          }
-        },
-        "id": "4113586532130817",
-        "paging_token": "4113586532130817",
-        "transaction_successful": true,
-        "source_account": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F",
-        "type": "payment",
-        "type_i": 1,
-        "created_at": "2024-11-14T20:37:28Z",
-        "transaction_hash": "bbc6b423efb9c5a8ebb1ac72437a326ffd4b8a202782157f9a9bca38f742f7d7",
-        "asset_type": "native",
-        "from": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F",
-        "to": "GDE25LQ34AFCSDMYTOI6AVVEHRXFRJI4MOAVIUGUDUQEC5ZWN5OZDLAZ",
-        "amount": "4.0000000"
-      },
-      {
-        "_links": {
-          "self": {
-            "href": "https://horizon-testnet.stellar.org/operations/4115390418391041"
-          },
-          "transaction": {
-            "href": "https://horizon-testnet.stellar.org/transactions/6de546bd7702f1590f21928e6aa1329582b436f11d9fc9bcce304ea51f1893b0"
-          },
-          "effects": {
-            "href": "https://horizon-testnet.stellar.org/operations/4115390418391041/effects"
-          },
-          "succeeds": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=desc&cursor=4115390418391041"
-          },
-          "precedes": {
-            "href": "https://horizon-testnet.stellar.org/effects?order=asc&cursor=4115390418391041"
-          }
-        },
-        "id": "4115390418391041",
-        "paging_token": "4115390418391041",
-        "transaction_successful": true,
-        "source_account": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F",
-        "type": "payment",
-        "type_i": 1,
-        "created_at": "2024-11-14T21:12:31Z",
-        "transaction_hash": "6de546bd7702f1590f21928e6aa1329582b436f11d9fc9bcce304ea51f1893b0",
-        "asset_type": "native",
-        "from": "GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F",
-        "to": "GCNJ2TA24PJNDPE2JF3BYVLUTJX2GLRDGGBG4SYMQHKHYDHSMAPRZXWC",
-        "amount": "5.0000000"
-      }
-    ]
-  }
-}
-```
-
-### [Todos los activos](https://lab.stellar.org/endpoints/assets)
-
-El punto final `/assets` de Horizon proporciona información sobre un activo. Dado que no estamos interesados en datos históricos, utilizaremos el Horizon de Mainnet de SDF para recuperar la información más reciente sobre el activo.
-
-![Lab: Horizon - Página de Activos](/assets/lab/horizon-assets.png)
-
-Inquiramos sobre uno de los activos más populares de la red Stellar: [USDC de Circle](https://www.circle.com/usdc). Para hacer esto, ingresa `USDC` como el Código del Activo y `GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN` como el Emisor del Activo.
-
-![Lab: Horizon - Página de Activos](/assets/lab/horizon-assets-usdc.png)
-
-Cuando hago clic en el botón **Enviar**, el punto final `/assets` devuelve los detalles del activo `USDC` en formato `JSON`.
-
-![Lab: Horizon - Página de Activos](/assets/lab/horizon-assets-usdc-response.png)
-
-La respuesta JSON para el activo `USDC` incluye [el objeto asset](../../../data/apis/horizon/api-reference/resources/assets/object.mdx), que contiene detalles sobre USDC, como el archivo TOML del activo (también conocido como [el archivo de información Stellar](../../../tokens/publishing-asset-info.mdx)), el número de saldos reclamables, pools de liquidez, contratos, cuentas, balances y flags.
-
-Muestra que `auth_revocable` está establecido en `true` bajo `flags`, indicando que esta cuenta (en este caso, el emisor de `USDC`) puede congelar el saldo de un titular de un activo que ha emitido.
-
-```
-{
-  "_links": {
-    "self": {
-      "href": "https://horizon.stellar.org/assets?asset_code=USDC&asset_issuer=GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN&cursor=&limit=10&order=asc"
-    },
-    "next": {
-      "href": "https://horizon.stellar.org/assets?asset_code=USDC&asset_issuer=GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN&cursor=USDC_GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN_credit_alphanum4&limit=10&order=asc"
-    },
-    "prev": {
-      "href": "https://horizon.stellar.org/assets?asset_code=USDC&asset_issuer=GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN&cursor=USDC_GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN_credit_alphanum4&limit=10&order=desc"
-    }
-  },
-  "_embedded": {
-    "records": [
-      {
-        "_links": {
-          "toml": {
-            "href": "https://centre.io/.well-known/stellar.toml"
-          }
-        },
-        "asset_type": "credit_alphanum4",
-        "asset_code": "USDC",
-        "asset_issuer": "GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN",
-        "paging_token": "USDC_GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN_credit_alphanum4",
-        "contract_id": "CCW67TSZV3SSS2HXMBQ5JFGCKJNXKZM7UQUWUZPUTHXSTZLEO7SJMI75",
-        "num_claimable_balances": 449,
-        "num_liquidity_pools": 645,
-        "num_contracts": 388,
-        "num_archived_contracts": 18,
-        "accounts": {
-          "authorized": 1058053,
-          "authorized_to_maintain_liabilities": 0,
-          "unauthorized": 0
-        },
-        "claimable_balances_amount": "8567.4304807",
-        "liquidity_pools_amount": "6154162.8631633",
-        "contracts_amount": "2734426.6007745",
-        "archived_contracts_amount": "26.3776599",
-        "balances": {
-          "authorized": "121258232.6884846",
-          "authorized_to_maintain_liabilities": "0.0000000",
-          "unauthorized": "0.0000000"
-        },
-        "flags": {
-          "auth_required": false,
-          "auth_revocable": true,
-          "auth_immutable": false,
-          "auth_clawback_enabled": false
-        }
-      }
-    ]
-  }
-}
-```
-
-## Función de compartir
-
-El Stellar Lab ofrece una función de compartir que te permite copiar una URL a su página, la cual redirige a los usuarios a un formulario con la URL del punto final y los valores de parámetro prellenados. Esta función facilita la colaboración con otros.
-
-Por ejemplo, al hacer clic en el ícono de compartir en la página de Pagos para Cuenta con el ID de cuenta `GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F`, copia una URL que incluye el parámetro de ID de cuenta y la configuración de red. Un ejemplo de una URL copiada es [este enlace](https://lab.stellar.org/endpoints/payments/account?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$account_id=GBPIMUEJFYS7RT23QO2ACH2JMKGXLXZI4E5ACBSQMF32RKZ5H3SVNL5F;;).
-
-![Lab: Horizon - Función Compartir](/assets/lab/horizon-share.png)
-
-## Solicitudes Guardadas
-
-El ícono junto al ícono de Función Compartir te permite guardar un punto final con sus parámetros en el almacenamiento local de tu navegador. Muestra el punto final para la red seleccionada, que puede ser cambiada usando el menú en la esquina superior derecha.
-
-![Lab: Horizon - Guardar](/assets/lab/horizon-save.png)
-
-Hacer clic en el ícono abre un modal. Recomendamos proporcionar un nombre identificable para facilitar la búsqueda posterior.
-
-![Lab: Horizon - Modal](/assets/lab/horizon-save-modal.png)
-
-Los endpoints guardados se encuentran en el menú principal bajo el menú "Guardados", en el submenú "[Solicitudes](../saved/requests.mdx)".
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/rpc-methods.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/rpc-methods.mdx
deleted file mode 100644
index d27ee63fba..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/api-explorer/rpc-methods.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
-# Métodos RPC
-
-Los métodos RPC son un conjunto de funciones que permiten a los desarrolladores interactuar directamente con la red Stellar. Puedes aprender más sobre todos los métodos RPC [aquí](../../../data/apis/rpc/api-reference/methods). El Laboratorio proporciona una manera fácil de utilizar estos métodos desde la interfaz de usuario. Para acceder a los elementos "RPC Methods", haz clic en el enlace "API Explorer" en la navegación principal, luego haz clic en el enlace del submenú "RPC Methods", que abrirá otro submenú que enumera todos los métodos RPC por nombre. Haz clic en el nombre del método para abrir esa página.
-
-:::warning
-
-Se requiere la URL de RPC para enviar estos métodos. Puedes actualizar o establecer la URL RPC en el selector de red en la esquina superior derecha.
-
-:::
-
-## Ejemplo
-
-Seleccionaremos el método `getLedgerEntries` como ejemplo. En la parte superior de la página hay un enlace "Ver Documentos" para aprender más sobre este método. El campo de entrada de solo lectura muestra la URL de RPC (verás una advertencia para proporcionar la URL de RPC si el campo de entrada está vacío). Junto al campo de entrada hay un botón de Enviar, que estará desactivado hasta que todos los datos requeridos estén llenos y sean válidos. Los botones Compartir y Guardar están junto al botón de Enviar. Más sobre ellos abajo.
-
-Hay dos maneras de ingresar la Clave del Ledger: cadena XDR Base64 o entradas manuales. Puedes cambiar el modo de entrada haciendo clic en el botón "Cambiar entrada". Aquí hay un ejemplo al ingresar la cadena XDR `AAAABgAAAAHMA/50/Q+w3Ni8UXWm/trxFBfAfl6De5kFttaMT0/ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=`. Las entradas manuales se generan como de solo lectura (la cadena XDR se generaría si se selecciona y completa correctamente el modo de entrada manual).
-
-![Laboratorio: ejemplo getLedgerEntries](/assets/lab/rpc-methods-item.png)
-
-Puedes agregar múltiples claves de ledger al hacer clic en el botón "Agregar otra clave de ledger".
-
-Puedes cambiar el formato de respuesta en el menú desplegable "Formato XDR": `base64` (XDR) o `json` (más legible para humanos).
-
-La sección "Cuerpo" genera una vista previa del cuerpo que se enviará.
-
-Para enviar la solicitud, haz clic en el botón Enviar en la parte superior (debería estar habilitado si todos los campos son correctos). Una vez que se procesa la solicitud, la respuesta se mostrará en la parte inferior de la página.
-
-## Función de compartir
-
-El laboratorio Stellar te permite compartir métodos RPC con datos rellenados. Simplemente haz clic en el botón Compartir (junto al botón Enviar) para copiar el enlace para compartir. [Aquí](https://lab.stellar.org/endpoints/rpc/get-ledger-entries?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&endpoints$params$xdrFormat=base64&ledgerKeyEntries=%5B%22AAAABgAAAAHMA//50//Q+w3Ni8UXWm//trxFBfAfl6De5kFttaMT0//ACwAAABAAAAABAAAAAgAAAA8AAAAHQ291bnRlcgAAAAASAAAAAAAAAAAg4dbAxsGAGICfBG3iT2cKGYQ6hK4sJWzZ6or1C5v6GAAAAAE=%22%5D;;) es un ejemplo del enlace que se puede compartir a partir de lo anterior.
-
-## Solicitudes guardadas
-
-Puedes guardar métodos en el almacenamiento local del navegador haciendo clic en el botón Guardar (junto al botón Compartir). Una vez que hagas clic en ese botón, aparecerá un modal donde necesitarás ingresar el nombre y hacer clic en guardar. Para ver tus métodos RPC guardados en el Lab, haz clic en el enlace "Guardados" en el menú principal y luego en el enlace del submenú "[Solicitudes](../saved/requests.mdx)". Luego haz clic en la pestaña "RPC Methods" en la esquina superior derecha.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/quickstart-with-lab.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/quickstart-with-lab.mdx
deleted file mode 100644
index b52fa376b7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/quickstart-with-lab.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
-# Usar Lab con Quickstart
-
-## Descripción general
-
-[Quickstart](https://github.com/stellar/quickstart) proporciona una manera fácil de configurar un entorno de red Stellar local. Específicamente, la imagen de docker de Quickstart agrupa Stellar Core con Horizon, RPC, Friendbot y las bases de datos PostgreSQL necesarias. Ahora es posible usar Stellar Lab como una interfaz en Quickstart.
-
-## Requisitos previos
-
-- [Stellar CLI](../cli/install-cli.mdx)
-- [Docker](https://www.docker.com/)
-
-## Iniciar Quickstart
-
-Quickstart se puede iniciar para diferentes redes. En este ejemplo, iniciaremos Quickstart para `testnet`. Inicia Quickstart con el Stellar CLI usando el siguiente comando:
-
-```sh
-stellar network container start testnet
-```
-
-Quickstart generalmente se iniciará en `http://localhost:8000`. Con esta información, ahora podemos configurar Stellar Lab para usar la red local.
-
-## Configurar Stellar Lab para usar Horizon Local y RPC Local
-
-![Lab: selector de red](/assets/lab/lab-custom-network.png)
-
-1. Abre el selector de red de Stellar Lab en la esquina superior derecha.
-2. Selecciona la red `Personalizada` en el menú desplegable.
-3. Para la URL de RPC, ingresa `http://localhost:8000/rpc`.
-4. Para la URL de Horizon, ingresa `http://localhost:8000.`.
-5. Para el [network passphrase](../../networks/README.mdx), ingresa `Test SDF Network ; September 2015`
-6. Haz clic en el botón `Cambiar a la red personalizada` y cambia a usar tu Quickstart.
-
-Ahora deberías poder usar los puntos finales de Horizon, los puntos finales de RPC y Friendbot en Lab, con solicitudes que se envían a tu entorno local (Quickstart). Lab te proporciona una interfaz amigable para interactuar con tu entorno local.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/README.mdx
deleted file mode 100644
index f728c096da..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Guardado
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Guardado
-
-Ver keypairs, solicitudes y transacciones guardadas en el almacenamiento local.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/keypairs.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/keypairs.mdx
deleted file mode 100644
index 135a808982..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/keypairs.mdx
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Keypairs
-sidebar_label: Keypairs
-description: Ver keypairs guardados (cuentas).
-sidebar_position: 0
----
-
-# [Keypairs](https://lab.stellar.org/account/saved)
-
-:::important
-
-Solo puedes guardar keypairs en redes de prueba—nunca en Mainnet—y jamás debes reutilizar keypairs de Mainnet en redes de prueba ni compartir tus claves secretas con nadie.
-
-:::
-
-## Resumen
-
-![Lab: Saved Keypairs](/assets/lab/lab-account-saved.png)
-
-Esta página muestra los keypairs guardados para la red seleccionada (solo Testnet y Futurenet) en el almacenamiento local del navegador. Cada keypair tiene lo siguiente:
-
-1. Nombre: facilita encontrar el keypair que buscas. Puedes actualizar el nombre en cualquier momento haciendo clic en el botón de editar y guardando el nuevo nombre.
-2. Clave pública: la dirección pública de la cuenta. Puedes copiarla rápidamente con un clic en el botón.
-3. Clave secreta: la clave secreta de la cuenta. Haz clic en el botón Ojo para alternar entre formato enmascarado y texto claro. Como la clave pública, puedes copiarla haciendo clic en el botón Copiar.
-4. Frase de recuperación: la frase de paso de 12 o 24 palabras. Haz clic en el botón Ojo para alternar entre formato enmascarado y texto claro. Como la clave pública, puedes copiarla haciendo clic en el botón Copiar.
-5. Botón de eliminar: haz clic en este botón para borrar el keypair.
-6. Elimina el keypair guardado si ya no es necesario.
-7. La fecha y hora de la última vez que se guardó.
-8. Saldo de XLM si la cuenta está financiada.
-9. Si la cuenta no está financiada, puedes obtener 10,000 XLM haciendo clic en el botón "Financiar con Friendbot". Esto puede ser útil tras el reinicio de Testnet o Futurenet, ya que todas tus cuentas guardadas también se restablecerán.
-
-## Guardar keypair manualmente
-
-Para añadir un keypair manualmente, haz clic en el botón "Añadir keypair manualmente" ubicado en la esquina superior derecha de la pantalla. Esto abrirá un modal donde puedes ingresar un nombre para tu keypair junto con la [clave secreta de Stellar](../../../learn/glossary.mdx#secret-private-key) (que comienza con la letra "S") o la frase de recuperación (una frase de 12 o 24 palabras).
-
-![Lab: Add keypair manually](/assets/lab/lab-account-saved-manual.png)
-
-## Uso de keypairs guardados
-
-Los keypairs guardados facilitan trabajar con cuentas Stellar y firmar transacciones. Al crear una transacción, haz clic en el botón "Obtener dirección" en el campo Cuenta de origen y elige la cuenta deseada del menú desplegable.
-
-![Lab: Use saved public key](/assets/lab/lab-account-saved-usage-public.png)
-
-Cuando sea momento de firmar, ve a la sección de Firmas en la página Firmar transacción. Si no la ves, primero importa tu transacción XDR. Luego haz clic en "Usar clave secreta" en la sección "Firmar con clave secreta" y selecciona la clave de la cuenta que deseas utilizar.
-
-![Lab: Use saved secret key](/assets/lab/lab-account-saved-usage-secret.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/requests.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/requests.mdx
deleted file mode 100644
index 0da0374a57..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/requests.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Solicitudes
-sidebar_label: Solicitudes
-description: Consulta los endpoints de Horizon guardados y los métodos RPC.
-sidebar_position: 1
----
-
-# [Solicitudes](https://lab.stellar.org/endpoints/saved)
-
-En esta página, puedes ver las solicitudes guardadas tanto para los **métodos RPC** como para los **endpoints de Horizon**. Selecciona la pestaña que quieres ver en la esquina superior derecha.
-
-:::info
-
-Solo se muestran los elementos de la red seleccionada. Si no ves el elemento que buscas, intenta cambiar de red.
-
-:::
-
-## Métodos RPC
-
-![Lab: Saved RPC Methods](/assets/lab/lab-rpc-methods-saved.png)
-
-Cada elemento de solicitud RPC guardada contiene lo siguiente:
-
-1. Nombre del método RPC: identifica rápidamente el método que necesitas.
-2. Nombre: facilita encontrar el método RPC que buscas. Puedes actualizar el nombre en cualquier momento haciendo clic en el botón de editar y guardando el nuevo nombre.
-3. URL RPC: lugar donde enviar la solicitud.
-4. Comparte la URL para ver el método con todos los datos en el Lab.
-5. Ver el elemento en el Explorador de API, donde puedes enviarlo.
-6. Ver carga útil.
-7. Fecha y hora de la última guardada.
-8. Eliminar el elemento si ya no es necesario.
-
-## Endpoints de Horizon
-
-![Lab: Horizon - Saved Requests Page](/assets/lab/lab-horizon-saved-requests.png)
-
-Los endpoints de Horizon guardados contienen lo siguiente:
-
-1. Nombre: puedes actualizarlo en cualquier momento haciendo clic en el botón de editar y guardando el nuevo nombre.
-2. URL de Horizon: endpoint para obtener los datos.
-3. Comparte la URL para ver el endpoint con todos los datos en el Lab.
-4. Ver el elemento en el Explorador de API, donde puedes enviarlo.
-5. Fecha y hora de la última guardada.
-6. Eliminar el elemento si ya no es necesario.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/transactions.mdx
deleted file mode 100644
index f090027428..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/saved/transactions.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Transacciones
-sidebar_label: Transacciones
-description: Ver transacciones guardadas.
-sidebar_position: 2
----
-
-# [Transacciones](https://lab.stellar.org/transaction/saved)
-
-![Lab: Transacciones Guardadas](/assets/lab/lab-transactions-saved.png)
-
-En esta página, verás las transacciones guardadas en el almacenamiento local de tu navegador. Solo muestra las transacciones en la red seleccionada, la cual puedes cambiar en la esquina superior derecha.
-
-Las transacciones guardadas tienen lo siguiente:
-
-1. Nombre: facilita encontrar la transacción que buscas. Puedes actualizar el nombre en cualquier momento haciendo clic en el botón de editar y guardando el nuevo nombre.
-2. Operaciones: lista de operaciones en esta transacción.
-3. Eliminar la transacción guardada.
-4. La fecha y hora del último guardado.
-5. El botón de compartir para obtener un enlace compartible de esta transacción.
-6. Las transacciones guardadas en la página "Transaction Builder" tienen el botón "Ver en el constructor" que te lleva a la página "Construir Transacción".
-7. Las transacciones guardadas en la página "Submit Transaction" tienen el botón "Ver en el que envía" que te lleva a esa página.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/README.mdx
deleted file mode 100644
index 084e35f2ba..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/README.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Contratos Inteligentes
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Stellar Lab proporciona un conjunto completo de herramientas para explorar, probar e interactuar con contratos inteligentes en la red Stellar. Estas herramientas están diseñadas para ayudar a los desarrolladores a comprender el comportamiento del contrato, depurar incidencias y probar las interacciones del contrato sin escribir código adicional.
-
-:::tip
-
-Si no conoces ningún ID de contrato inteligente de Stellar, consulta la [Lista de Contratos Inteligentes](https://lab.stellar.org/smart-contracts/contract-list) y haz clic en cualquiera de los elementos. Esto te llevará a la página "Explorador de Contratos", donde el ID seleccionado ya estará rellenado. ¡Carga el contrato y échale un vistazo!
-
-:::
-
-### Consejos para nuevos desarrolladores
-
-- **Comienza con Testnet**: Siempre empieza tu desarrollo y pruebas en Testnet, donde el XLM es gratuito y los errores no tienen consecuencias en el mundo real.
-- **Examina contratos de ejemplo**: Estudia contratos conocidos para entender patrones comunes y prácticas recomendadas.
-- **Guarda tus configuraciones**: Escribe el ID del contrato que quieres explorar en el [Explorador de Contratos](https://lab.stellar.org/smart-contracts/contract-explorer), te dará la opción de guardarlo para acceder rápidamente mediante 'Guardar ID de Contrato'.
-- **Verifica el estado de la red**: Asegúrate de estar conectado a la red correcta.
-
-## Recursos adicionales
-
-- [Documentación de Smart Contracts](../../../build/smart-contracts/README.mdx)
-- [Herramientas CLI de Soroban](../../cli/README.mdx)
-- [Contratos de ejemplo](../../../build/smart-contracts/example-contracts/README.mdx)
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/contract-explorer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/contract-explorer.mdx
deleted file mode 100644
index 72339a1bea..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/contract-explorer.mdx
+++ /dev/null
@@ -1,126 +0,0 @@
----
-title: Explorador de Contratos
-sidebar_label: Explorador de Contratos
-description: Explora e interactúa con contratos inteligentes desplegados en Stellar a través de una interfaz basada en navegador. Consulta especificaciones del contrato, código fuente, almacenamiento, información de desarrollo, historial de versiones e invoca métodos de contrato directamente.
-sidebar_position: 0
----
-
-# Explorador de Contratos
-
-El [Explorador de Contratos](https://lab.stellar.org/smart-contracts/contract-explorer) es tu interfaz principal para examinar contratos inteligentes desplegados en la red Stellar. Mediante una intuitiva interfaz basada en navegador, puedes acceder a información completa sobre [especificaciones del contrato](#contract-spec), [código fuente](#source-code), [estado del almacenamiento](#contract-storage), [información de desarrollo](#build-info), [historial de versiones](#version-history) y [enlaces de cliente](#bindings), además de [invocar métodos del contrato](#invoke-contract) directamente sin herramientas de línea de comandos.
-
-:::warning
-
-Se requiere la URL RPC para ver la información del contrato. Puedes actualizar o establecer la URL RPC en el selector de red en la esquina superior derecha. Consulta [Proveedores RPC](../../../data/apis/rpc/providers.mdx).
-
-:::
-
-![Lab: Contract Explorer](/assets/lab/lab-contract-explorer.png)
-
-## Comenzar
-
-Para explorar un contrato:
-
-1. Navega al [Explorador de Contratos](https://lab.stellar.org/smart-contracts/contract-explorer)
-2. Selecciona tu red `Testnet` o `Mainnet`
-3. Introduce un ID de contrato
-4. Explora las pestañas para familiarizarte con la estructura y capacidades del contrato
-
-Vamos a cargar el ID de contrato `CAJJZSGMMM3PD7N33TAPHGBUGTB43OC73HVIK2L2G6BNGGGYOSSYBXBD` en la red `Mainnet` y ver qué podemos aprender sobre él.
-
-## Información del contrato
-
-En la sección "Información del contrato", podemos ver la fecha en que se creó el contrato y la dirección Stellar del creador. También muestra el hash Wasm y el repositorio de GitHub, junto con un enlace al código fuente de este contrato. Además, puedes ver cuántas entradas de almacenamiento tiene este contrato.
-
-![Lab: Contract Explorer: Contract Info](/assets/lab/lab-contract-explorer-info.png)
-
-## Especificación del contrato
-
-En esta sección, puedes ver la [Meta de contrato](../../../learn/fundamentals/contract-development/overview#contract-meta), la [Meta del entorno de contrato](../../../learn/fundamentals/contract-development/overview#environment-meta), y la [Especificación del contrato](../../../learn/fundamentals/contract-development/overview#contract-spec) desde el archivo Wasm. Puedes ver cada sección en formatos `Interface`, `JSON` o `XDR`, seleccionando el tipo desde el menú desplegable en la esquina superior derecha de la vista del editor. También puedes descargar cada sección individualmente en el formato seleccionado (el botón de descarga está ubicado junto al menú desplegable de tipo), o descargar el archivo Wasm completo haciendo clic en el botón "Descargar Wasm" al final de la sección.
-
-![Lab: Contract Explorer: Contract Spec](/assets/lab/lab-contract-explorer-spec.png)
-
-## Código fuente
-
-En el editor de código, puedes ver el archivo `README.md` del repositorio del contrato inteligente. Puedes explorar más el código abriéndolo en un Dev Container, Codeanywhere, o usando el enlace de GitHub (consulta el menú desplegable en la esquina superior derecha de la vista del editor).
-
-![Lab: Contract Explorer: Source Code](/assets/lab/lab-contract-explorer-source.png)
-
-## Almacenamiento del contrato
-
-Esta sección muestra todas las entradas de datos almacenadas para el contrato inteligente en un formato legible para humanos. Los datos pueden filtrarse por `Key` y `Value`, ordenarse por las columnas `Durability`, `TTL` o `Updated`, y exportarse en formatos `XDR` o `JSON`.
-
-![Lab: Contract Explorer: Contract Storage](/assets/lab/lab-contract-explorer-storage.png)
-
-### Restaurar Footprint
-
-Las entradas de almacenamiento archivadas pueden restaurarse haciendo clic en el botón `Restore` junto a la entrada.
-
-![Lab: Contract Explorer: Contract Storage Restore](/assets/lab/stellar-lab-restore.png)
-
-Esta acción te redirige a la [página Construir Transacciones](https://lab.stellar.org/transaction/build) con una operación `RestoreFootprintOp` configurada automáticamente con los parámetros necesarios para restaurar el footprint archivado.
-
-![Lab: Contract Explorer: Contract Storage Restore in action](/assets/lab/restore-footprint.gif)
-
-:::tip
-
-Verifica que el XDR de la Transacción Soroban preparada incluya los datos del contrato que deseas restaurar en sus recursos `footprint.read_write`, y confirma que tanto los bytes de lectura como de escritura sean diferentes de cero.
-
-:::
-
-## Información de compilación
-
-Si el contrato inteligente tiene configurada la verificación de compilación (siguiendo el [SEP de validación de código fuente de contrato](https://github.com/orgs/stellar/discussions/1573)), esta sección muestra información de la attestación de GitHub.
-
-:::info
-
-"Compilación verificada" solo significa que la acción de GitHub ha certificado que se compiló el Wasm, pero no verifica el código fuente. Asegúrate siempre de comprender completamente qué hace el contrato inteligente antes de usarlo.
-
-:::
-
-![Lab: Contract Explorer: Build Info](/assets/lab/lab-contract-explorer-build.png)
-
-## Historial de versiones
-
-En esta sección, puedes encontrar el historial de cambios del Wasm.
-
-![Lab: Contract Explorer: Version History](/assets/lab/lab-contract-explorer-version.png)
-
-## Bindings
-
-Bindings son una función del [CLI de Stellar](../../cli) que generan bibliotecas cliente completamente tipadas para tus contratos inteligentes, adaptadas a tu lenguaje de programación elegido, incluyendo TypeScript, JSON, Rust, Python y Java. Esto facilita integrar los contratos Stellar en tu aplicación como si fueran módulos nativos. Cada binding proporciona funciones con seguridad de tipos que corresponden a los métodos de tu contrato. Para aprender más sobre generar bindings, consulta el [comando de bindings del CLI de Stellar](../../cli/stellar-cli#stellar-contract-bindings).
-
-## Invocar contrato
-
-La página Invocar Contrato te permite interactuar directamente con contratos inteligentes a través de la interfaz web, sin necesidad de herramientas de línea de comandos o scripts personalizados.
-
-:::warning
-
-Se requiere una wallet conectada para invocar el contrato.
-
-:::
-
-### Cómo usar
-
-1. **Conecta tu billetera**: Elige conectar una billetera del navegador haciendo clic en "Connect Wallet" en la esquina superior derecha.
-2. **Selecciona la red**: `Testnet` o `Mainnet` en la esquina superior derecha.
-3. **Introduce los detalles del contrato**: Proporciona el ID del contrato
-4. **Selecciona una Función**: Escoge qué función del contrato quieres invocar de las opciones disponibles.
-5. **Completa los parámetros**: Introduce los parámetros requeridos para la función seleccionada. Lab proporciona sugerencias de tipo basadas en la [Especificación del Contrato](#contract-spec).
-6. **Simulate**: Simula la transacción para obtener la cantidad correcta de la tarifa y ver el resultado antes de enviarla a la red. Por defecto, verás el resultado de la función invocada. Si quieres la respuesta completa de la invocación del contrato, simplemente activa "Show full response".
-7. **Enviar**: Usa esto solo cuando sea una operación de `Write` y desees cambiar los datos en la red.
-
-![Lab: Contract Explorer: Invoke Contract](/assets/lab/lab-contract-explorer-invoke.gif)
-
-:::info
-
-Una vez que simules la función, verás una herramienta emergente que indica `Read` o `Write` junto al título de la función invocada. Cuando una transacción no cambia el estado del contrato, se considera una operación de `Read`. En este caso, no es necesario enviar la transacción a la red, ya que no modifica ningún dato. Puedes simplemente simular la transacción para ver los resultados sin incurrir en costos.
-
-:::
-
-### Casos de Uso
-
-- **Pruebas**: Prueba rápidamente funciones del contrato durante el desarrollo sin desplegar scripts de prueba
-- **Depuración**: Investiga incidencias invocando funciones con diferentes parámetros y examinando las salidas
-- **Educación**: Aprende cómo funcionan los contratos explorando e invocando contratos públicos
-- **Prototipado**: Experimenta con interacciones de contratos antes de desarrollar aplicaciones completas
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/smart-contract-list.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/smart-contract-list.mdx
deleted file mode 100644
index 0014599a71..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/smart-contract-list.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Lista de contratos inteligentes
-sidebar_label: Lista de contratos inteligentes
-description: Una lista de contratos inteligentes Stellar en la red seleccionada
-sidebar_position: 1
----
-
-# Lista de contratos inteligentes
-
-Esta página muestra una lista de contratos inteligentes Stellar en la red seleccionada. La tabla muestra el ID o dirección del contrato inteligente, junto con su fecha y hora de creación. Al hacer clic en la dirección del contrato, se te dirigirá a la página "Contract Explorer", donde la dirección seleccionada ya estará rellenada.
-
-![Lab: Smart Contract List](/assets/lab/lab-smart-contract-list.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/upload-deploy-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/upload-deploy-contract.mdx
deleted file mode 100644
index 6fdda020e7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/smart-contracts/upload-deploy-contract.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Subir y desplegar contrato
-sidebar_label: Subir y desplegar contrato
-description: Sube el bytecode WASM de tu contrato y despliega el contrato en la red.
-sidebar_position: 2
----
-
-# Subir y desplegar contrato
-
-Hay varias formas de subir y desplegar contratos en la red Stellar. Si estás familiarizado con el flujo de trabajo de la CLI, puedes subir y desplegar contratos fácilmente usando dos comandos diferentes en la [Stellar CLI](../../cli/README.mdx). Si prefieres hacerlo todo en una interfaz web, la página ["Subir y desplegar contrato"](https://lab.stellar.org/smart-contracts/deploy-contract) en Stellar Lab ofrece una forma cómoda de subir y desplegar contratos en la red.
-
-![Lab: Explorador de contratos](/assets/lab/lab-upload-deploy-page.png)
-
-El proceso de despliegue consta de dos fases distintas:
-
-1. **Fase de subida**: subir el bytecode `WASM` a la red
-2. **Fase de despliegue**: desplegar una instancia de contrato a partir del bytecode subido con éxito
-
-:::tip
-
-Cada fase de subida y despliegue requiere crear una transacción y firmarla.
-
-:::
-
-## Fase de subida
-
-La "fase de subida" acepta archivos `.wasm` mediante arrastrar y soltar o selección en el explorador de archivos. Durante esta fase, Lab verifica si el archivo `.wasm` subido ya existe en la red. Si no está en la red, crea una transacción de subida que debes firmar usando alguno de estos métodos: clave secreta, hardware wallet, wallet de extensión o firma.
-
-![Lab: Subir y desplegar contrato - subiendo contrato](/assets/lab/lab-upload-contract.gif)
-
-Si el bytecode `WASM` solicitado ya está subido en la red, Lab omite la sección "Subir contrato" y abre por defecto la sección "Desplegar contrato". Verás un mensaje: "Este contrato `WASM` ya está subido. Hash Wasm: \*\*\*\*"
-
-![Lab: Subir y desplegar contrato - omitiendo subir contrato](/assets/lab/lab-already-uploaded.gif)
-
-## Fase de despliegue
-
-Durante la "fase de despliegue", Lab verifica si los metadatos del contrato `WASM` tienen un constructor y qué argumentos requiere. Una vez que todos los campos requeridos están completos, crea una transacción de despliegue. Después de que la transacción esté firmada y enviada con éxito, puedes verificar tu contrato inmediatamente en exploradores de blockchain como [Stellar.Expert](https://stellar.expert/explorer/) o [el explorador de contratos de Stellar Lab](https://lab.stellar.org/smart-contracts/contract-explorer).
-
-![Lab: Subir y desplegar contrato - desplegando contrato](/assets/lab/lab-deploy-contract.gif)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/transactions.mdx
deleted file mode 100644
index 05b723e4e2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/transactions.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
-# Transacciones
-
-## [Crear Transacción](https://lab.stellar.org/transaction/build)
-
-![Laboratorio: Crear Transacción](/assets/lab/lab-transactions-build.png)
-
-Puedes acceder a la página "Crear transacción" haciendo clic en el enlace "Transacciones" en la navegación principal del Laboratorio. La interfaz de usuario del constructor de transacciones tiene mensajes útiles, enlaces y validación de entradas para facilitar el aprendizaje sobre cómo crear transacciones en la red Stellar. Hay tres secciones principales: parámetros, operaciones y validación de transacciones (error o éxito).
-
-### Parámetros
-
-Una transacción en Stellar requiere una cuenta de origen, un número de secuencia de transacción y una tarifa base. El memo y los límites de tiempo son opcionales.
-
-Una vez que ingreses una dirección pública válida en el campo "Cuenta de Origen", puedes obtener automáticamente el número de secuencia haciendo clic en el botón "Obtener siguiente secuencia".
-
-La tarifa base es 100 por defecto, pero puede que necesites aumentar la tarifa si la red está congestiona.
-
-### Operaciones
-
-![Laboratorio: Operaciones de transacción](/assets/lab/lab-transactions-ops.png)
-
-Una transacción requiere al menos una operación, pero Stellar admite hasta 100 operaciones en una sola transacción.
-
-Selecciona el tipo de operación del menú desplegable para obtener los campos para ese tipo de operación y complétalos según sea necesario.
-
-Si deseas agregar más operaciones, haz clic en el botón "Agregar Operación" en la parte inferior de la sección de operaciones. También puedes duplicar, eliminar y mover la operación haciendo clic en el botón correspondiente en la parte superior derecha de la sección de cada operación.
-
-También puedes guardar una transacción válida haciendo clic en el botón de guardar en la parte inferior de la sección de operaciones. Necesitarás ingresar un nombre para esta transacción en un pop-up y hacer clic en el botón "Guardar". Las transacciones se guardan en el almacenamiento local del navegador y se pueden encontrar en la página "[Transacciones Guardadas](./saved/transactions)" (accesible haciendo clic en el enlace Guardadas en la navegación izquierda y luego en el subelemento de menú "Transacciones").
-
-Hacer clic en el botón de compartir (justo al lado del botón de guardar) te permite compartir un enlace con toda la información de la transacción proporcionada. Puedes compartir cualquier transacción, incluso si es inválida o incompleta.
-
-### Validación de Transacciones
-
-![Laboratorio: Validación de transacción exitosa](/assets/lab/lab-transactions-response-success.png)
-
-La sección de validación en la parte inferior de la página muestra la información de la transacción creada si todo es correcto. Hacer clic en el botón "Iniciar sesión en Firmante de Transacciones" te llevará a la página "Firmar Transacción", donde podrás firmar la transacción. También puedes hacer clic en el botón "Ver en visualizador XDR" para ver el JSON de la transacción construida.
-
-Si hay errores en esta transacción, los verás agrupados por sección (parámetros y cada operación) para facilitar identificar qué necesita corrección.
-
-![Laboratorio: Error de validación de transacción](/assets/lab/lab-transactions-response-error.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/README.mdx
deleted file mode 100644
index 50da169ebe..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Ver XDR
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Ver XDR
-
-Esta sección proporciona herramientas para trabajar con datos [XDR](../../../learn/fundamentals/data-format/xdr.mdx) (External Data Representation). Puedes decodificar XDR en un formato JSON fácil de leer, convertir JSON nuevamente en formato XDR o comparar dos conjuntos de datos XDR para ver sus diferencias lado a lado. Aprende más sobre la conversión de XDR a JSON [aquí](../../../learn/fundamentals/data-format/xdr-json.mdx).
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/diff-xdr.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/diff-xdr.mdx
deleted file mode 100644
index d1f6f1dda6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/diff-xdr.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Diferencias en XDRs
-sidebar_label: Diferencias en XDRs
-description: La herramienta Diferencias en XDRs compara dos XDRs codificados en base-64 y resalta las diferencias entre ellos en formato JSON.
-sidebar_position: 2
----
-
-# Diferencias en XDRs
-
-:::info
-
-Obtén más información sobre las herramientas de conversión de XDR a JSON [aquí](../../../learn/fundamentals/data-format/xdr-json.mdx).
-
-:::
-
-## Acceder a la herramienta Diferencias en XDRs
-
-Para acceder a la página de [Diferencias en XDRs](https://lab.stellar.org/xdr/diff), selecciona "Ver XDR" en el menú de navegación izquierdo y luego elige la opción "Diferencias en XDRs" en el submenú.
-
-![Lab: página de Diferencias en XDRs](/assets/lab/lab-xdr-diff.png)
-
-## Comparar datos XDR
-
-En esta página, puedes comparar dos [XDRs](../../../learn/fundamentals/data-format/xdr.mdx) codificados en base-64 viendo sus diferencias en JSON. Introduce el XDR Original en el primer campo de entrada y el XDR Modificado en el segundo campo. Ambos XDRs deben tener el mismo tipo de XDR, el cual se completa automáticamente al ingresar un valor Original válido. Si el tipo sugerido parece incorrecto, puedes seleccionar uno alternativo desde el menú desplegable. Hay una función de búsqueda disponible para ayudar a encontrar el tipo adecuado.
-
-![Lab: menú desplegable de tipo XDR](/assets/lab/lab-xdr-diff-dropdown.png)
-
-## Comprender la salida
-
-Una vez ingresados ambos valores XDR, se mostrará una vista comparativa abajo resaltando las diferencias entre los dos objetos. Debajo de cada diferencia, encontrarás un botón para copiar los datos JSON correspondientes.
-
-![Lab: salida de Diferencias en XDRs](/assets/lab/lab-xdr-diff-filled.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/json-to-xdr.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/json-to-xdr.mdx
deleted file mode 100644
index e4ad21ad57..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/json-to-xdr.mdx
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: JSON a XDR
-sidebar_label: JSON a XDR
-description: El convertidor de JSON a XDR transforma objetos JSON en formato XDR codificado en base 64.
-sidebar_position: 1
----
-
-# JSON a XDR
-
-:::info
-
-Aprende más sobre las herramientas de conversión de JSON a XDR [aquí](../../../learn/fundamentals/data-format/xdr-json.mdx).
-
-:::
-
-## Acceder al convertidor de JSON a XDR
-
-Para acceder a la página de [JSON a XDR](https://lab.stellar.org/xdr/to), selecciona "Ver XDR" en el menú de navegación izquierdo y luego escoge la opción "JSON a XDR" del submenú.
-
-![Lab: página JSON a XDR](/assets/lab/lab-xdr-from-json.png)
-
-## Ingresar datos JSON
-
-En esta página puedes introducir un objeto JSON válido de [XDR](../../../learn/fundamentals/data-format/xdr.mdx) en el campo de entrada. Para obtener datos de ejemplo, navega a la página "[XDR a JSON](./xdr-to-json.mdx)", y usa el botón "Copiar JSON" debajo de la salida JSON para copiar un objeto formateado para pruebas.
-
-## Comprender la salida
-
-Después de ingresar un objeto JSON válido, la interfaz muestra dos componentes clave:
-
-1. **Tipo XDR** – El tipo identificado de datos XDR, con un valor preseleccionado automáticamente. Si el tipo sugerido parece incorrecto, puedes seleccionar una alternativa del menú desplegable. Hay una función de búsqueda disponible para ayudarte a encontrar el tipo adecuado. ![Lab: menú desplegable de tipo XDR](/assets/lab/lab-xdr-from-json-dropdown.png)
-2. **Salida XDR** – Un XDR codificado en base 64 generado según el tipo XDR seleccionado. Puedes copiar esta salida haciendo clic en el botón de copiar debajo del campo.
-
-![Lab: salida JSON a XDR](/assets/lab/lab-xdr-from-json-filled.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/xdr-to-json.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/xdr-to-json.mdx
deleted file mode 100644
index 57088aa21a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/lab/view-xdr/xdr-to-json.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: XDR a JSON
-sidebar_label: XDR a JSON
-description: El convertidor de XDR a JSON transforma datos XDR codificados en base-64 en un formato JSON legible.
-sidebar_position: 0
----
-
-# XDR a JSON
-
-:::info
-
-Aprende más sobre herramientas de conversión de XDR a JSON [aquí](../../../learn/fundamentals/data-format/xdr-json.mdx).
-
-:::
-
-Para acceder a la página [XDR a JSON](https://lab.stellar.org/xdr/view), selecciona "Ver XDR" en el menú de navegación lateral izquierdo, luego elige la opción "XDR a JSON" en el submenú.
-
-![Lab: página de XDR a JSON](/assets/lab/lab-xdr-to-json.png)
-
-## Ingresar datos XDR
-
-En esta página, puedes introducir un [XDR](../../../learn/fundamentals/data-format/xdr.mdx) codificado en base-64 en el campo de entrada ubicado en la parte superior. Alternativamente, puedes obtener un XDR de ejemplo seleccionando el enlace "obtener la última transacción" que está debajo del campo de entrada.
-
-## Entendiendo la salida
-
-Después de cargar un XDR válido (por ejemplo, obteniendo la última transacción), la interfaz muestra tres componentes clave:
-
-1. **Hash de transacción** – Un campo de solo lectura que contiene el hash de la transacción, el cual puedes copiar para usar en otras herramientas, como obtener detalles de la transacción mediante [API Explorer > Métodos RPC > getTransaction](https://lab.stellar.org/endpoints/rpc/get-transaction).
-2. **Tipo de XDR** – El tipo identificado de datos XDR, con un valor preseleccionado automáticamente. Si el tipo sugerido parece incorrecto, puedes seleccionar otra opción desde el menú desplegable. Hay una función de búsqueda disponible para ayudarte a encontrar el tipo adecuado. ![Lab: menú desplegable del tipo de XDR](/assets/lab/lab-xdr-to-json-dropdown.png)
-3. **Salida JSON** – Un objeto JSON generado según el tipo de XDR seleccionado. Puedes copiar este objeto haciendo clic en el botón "Copiar JSON" que está debajo de la salida.
-
-![Lab: salida de XDR a JSON](/assets/lab/lab-xdr-to-json-filled.png)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/openzeppelin-contracts.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/openzeppelin-contracts.mdx
deleted file mode 100644
index 36d73ec2c1..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/openzeppelin-contracts.mdx
+++ /dev/null
@@ -1,119 +0,0 @@
----
-title: Contratos y herramientas de OpenZeppelin
-description: Biblioteca de contratos y herramientas de OpenZeppelin
-sidebar_label: Contratos y herramientas de OpenZeppelin
-sidebar_position: 44
----
-
-<script async src="https://wizard.openzeppelin.com/build/embed.js"></script>
-
-Para ofrecer contratos inteligentes comprobados a la comunidad de desarrolladores de Stellar, OpenZeppelin contribuye activamente a una biblioteca de contratos inteligentes y extensiones, así como a herramientas para desarrolladores (incluidos productos como [Contract Wizard](https://wizard.openzeppelin.com/stellar), [Relayer](https://github.com/OpenZeppelin/openzeppelin-relayer), [Monitor](https://github.com/OpenZeppelin/openzeppelin-monitor) y [UI Builder](https://builder.openzeppelin.com/)). Para la documentación más reciente sobre productos de OpenZeppelin, por favor visita: [https://docs.openzeppelin.com/stellar-contracts](https://docs.openzeppelin.com/stellar-contracts/.).
-
-## Comenzar con el Asistente de Contratos
-
-[El Asistente de Contratos de OpenZeppelin](https://wizard.openzeppelin.com/stellar) incluye admitir para contratos inteligentes basados en Rust de Stellar, facilitando a los desarrolladores generar y desplegar contratos seguros y auditados. Después de seleccionar tu plantilla y opciones deseadas puedes descargarlo como un solo archivo, un paquete de desarrollo Rust o un [Paquete Scaffold Stellar](./scaffold-stellar). Pruébalo a continuación o visita el asistente [aquí](https://wizard.openzeppelin.com/stellar).
-
-<oz-wizard data-lang="stellar"></oz-wizard>
-
-Para una guía sobre cómo usar estos contratos, ¡mira el video que aparece abajo!
-
-<iframe
-  width="560"
-  height="315"
-  src="https://www.youtube.com/embed/iD7ZspsZLVo?si=TvAo70F1mA0pDWz6&amp;amp;controls=1"
-  title="YouTube video player"
-  frameborder="0"
-  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
-  referrerpolicy="strict-origin-when-cross-origin"
-  allowfullscreen
-></iframe>
-
-## Contratos y Utilidades Stellar de OpenZeppelin
-
-OpenZeppelin Stellar Contracts es una colección de contratos auditados y utilidades para Stellar. Los contratos son desarrollados por OpenZeppelin en colaboración con la comunidad Stellar y la Stellar Development Foundation (SDF), en un esfuerzo por crear una biblioteca de contratos de alta calidad y auditados que pueden usarse para crear aplicaciones en la red Stellar.
-
-### Módulos Auditados Disponibles
-
-**Token Fungible**
-
-- Extensiones:
-  - **Quemable**: Permitir a los poseedores destruir sus tokens
-  - **Con límite**: Establecer límites máximos de suministro
-  - **Lista blanca**: Restringir transferencias a direcciones aprobadas
-  - **Lista negra**: Prevenir transferencias desde/hacia direcciones bloqueadas
-
-**Token No Fungible**
-
-- Extensiones:
-  - **Quemable**: Permitir a los poseedores destruir sus NFTs
-  - **Enumerables**: Habilitar iteración sobre todos los tokens y los tokens del propietario
-  - **Consecutivo**: Crear múltiples tokens en lotes de manera eficiente
-  - **Regalías**: Admitir regalías para creadores en ventas secundarias
-
-**Token Stablecoin**
-
-- Extensiones:
-  - **Quemable**: Permitir a los poseedores destruir sus tokens
-  - **Con límite**: Establecer límites máximos de suministro
-  - **Lista blanca**: Restringir transferencias a direcciones aprobadas
-  - **Lista negra**: Prevenir transferencias desde/hacia direcciones bloqueadas
-
-**Token RWA (ERC-3643)** El token RWA amplía la funcionalidad estándar de token fungible con características regulatorias necesarias para tokens de seguridad, incluyendo:
-
-- Características:
-  - **Gestión de identidad**: Integración con registros de identidad para cumplimiento de KYC/AML
-  - **Marco de cumplimiento**: Normas modulares de cumplimiento y validación para transferencias y creación
-  - **Controles de transferencia**: Restricciones y validaciones sofisticadas para transferencias
-  - **Mecanismos de congelamiento**: Capacidades de congelamiento a nivel de dirección y parcial de tokens
-  - **Sistema de recuperación**: Recuperación de cuentas perdidas/antiguas para inversionistas verificados
-  - **Operaciones pausables**: Funcionalidad de pausa de emergencia para todo el token
-  - **Control de acceso basado en roles (RBAC)**: Gestión flexible de privilegios para funciones administrativas
-
-**Bóveda de tokens** La Bóveda de tokens fungibles extiende el Token fungible y aplica [SEP-56 Tokenized Vault Standard](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0056.md), permitiendo que los tokens fungibles representen participaciones en un fondo de activos subyacentes. El estándar de bóveda tokenizada es la interfaz formalizada para bóvedas que generan rendimiento y contienen activos subyacentes. Las participaciones en la bóveda permiten colaterales hiperfungibles en DeFi y permanecen completamente compatibles con las operaciones estándar de tokens fungibles.
-
-**Cuentas inteligentes**
-
-Las Cuentas inteligentes son billeteras basadas en contratos diseñadas para una autorización flexible y programable. Este marco adopta un enfoque centrado en el contexto, separando tres aspectos distintos: quién puede firmar (firmantes), qué pueden hacer (reglas de contexto/alcance) y cómo se aplican esos permisos (políticas). La versión inicial incluye políticas para multisig y límites de gasto.
-
-- Componentes:
-  - **Reglas de contexto**: Tabla de enrutamiento para autorización
-  - **Firmantes**: Lista de firmantes autorizados (dirección delegada o firmantes externos)
-  - **Políticas**: Módulo de aplicación ligado a las reglas de contexto
-  - **Verificadores**: Contratos de confianza que validan firmas en nombre de cuentas inteligentes
-
-**Utilidades**
-
-- **Utilidades pausables y actualizables**
-- **Control de acceso basado en roles y poseedor**
-- **Distribuidor Merkle**
-
-**Próximamente**
-
-- Matemáticas de punto fijo
-- Gobernador
-
-Todos los contratos y extensiones son auditados por el equipo de seguridad de OpenZeppelin, mejorando la seguridad y fiabilidad de los contratos y extensiones. Se está completando una verificación formal adicional por Certora. Para usar la biblioteca, visita: https://github.com/OpenZeppelin/stellar-contracts.
-
-```
-Repository Structure
-│── audits/                    # Audit reports
-│── docs/                      # Documentation
-│── examples/                  # Example contracts
-│── packages/
-│   ├── access/                # Access control, ownable, and role transfer utilities
-│   ├── accounts/              # Smart account framework
-│   ├── tokens/                # Various token types (fungible, non-fungible, RWA, vault, etc.)
-│   ├── contract-utils/        # Utilities for token types (pausable, upgradable, etc.)
-│   ├── constants/             # Shared constants
-│   ├── test-utils/            # Utilities for tests
-
-```
-
-Para proporcionar comentarios sobre estos contratos y utilidades, abre incidencias en: [https://github.com/OpenZeppelin/stellar-contracts/issues](https://github.com/OpenZeppelin/stellar-contracts/issues)
-
-### Herramientas de OpenZeppelin
-
-- [Relayer](https://github.com/OpenZeppelin/openzeppelin-relayer): Infraestructura para retransmitir transacciones en Stellar.
-- [Monitor](https://github.com/OpenZeppelin/openzeppelin-monitor): Herramienta de infraestructura para monitorear eventos y transacciones en blockchain.
-- [Constructor de interfaz de usuario](https://builder.openzeppelin.com/): Herramienta de código abierto para crear formularios de interfaz de usuario para contratos.
-- [Servidor MCP](https://mcp.openzeppelin.com/): Genera contratos inteligentes de Stellar seguros basados en plantillas de OpenZeppelin.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/README.mdx
deleted file mode 100644
index ced7bed61f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/README.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: Introducción rápida
-description: Introducción rápida es un entorno de red local de Stellar (nodo) para desarrollo y pruebas.
-sidebar_label: Introducción rápida
-sidebar_position: 40
----
-
-# Introducción rápida
-
-Introducción rápida es un entorno de red local de Stellar (nodo) que permite a los desarrolladores ejecutar una versión local de la red Stellar para desarrollo y pruebas. La introducción rápida ejecuta una versión local de Stellar Core, Horizon, RPC y todo lo demás necesario para replicar la red pública.
-
-Para más información sobre cómo ejecutar los servicios de Stellar en producción, consulta la documentación de los servicios individuales aquí:
-
-- [Cómo ejecutar Stellar Core en producción](../../validators/README.mdx)
-- [Cómo ejecutar Horizon en producción](../../data/apis/horizon/admin-guide/overview.mdx)
-- [Cómo ejecutar RPC en producción](../../data/apis/rpc/admin-guide/README.mdx)
-
-La introducción rápida está destinada para uso en desarrollo, no en producción, aunque ejecutarla en modo público hará que se una a la red pública.
-
-**Ejecutar la introducción rápida**
-
-¿Listo para comenzar? La sección de Comenzar en la documentación de la introducción rápida mostrará cómo ejecutar la introducción rápida, pero hay algunas configuraciones que decidir primero. Lo más importante, el modo de red en el que se ejecutará la introducción rápida (pubnet, testnet, futurenet, local). Infórmate sobre los modos en la sección Modos de red.
-
-:::info
-
-La introducción rápida puede ser implementada usando la guía de Comenzar, pero las configuraciones utilizadas en la guía pueden no ser ideales para tu caso de uso, así que por favor familiarízate con las opciones para configurar la introducción rápida de acuerdo a tu caso de uso.
-
-:::
-
-:::caution
-
-Por favor nota: la imagen de la introducción rápida no está destinada para propósitos de producción. La información sobre cómo configurar un entorno de producción está disponible [aquí](../../validators/README.mdx).
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/README.mdx
deleted file mode 100644
index 1c867cdd11..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Uso Avanzado
-description: Quickstart se puede configurar según tus preferencias personales y casos de uso
-sidebar_label: Uso Avanzado
-sidebar_position: 50
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Uso Avanzado
-
-Quickstart funciona directamente, y cuando se lanza usando el CLI de Stellar, no se requiere configuración. Aunque la configuración estándar puede funcionar para muchos casos de uso, puede que no se ajuste a las necesidades de todos. Si se necesita una configuración personalizada, el contenedor de Quickstart se puede ejecutar usando el CLI de docker.
-
-Lee más sobre la configuración y el establecimiento de Quickstart:
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/_category_.json
deleted file mode 100644
index 4fb6019997..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-}
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/container.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/container.mdx
deleted file mode 100644
index c4a2562be8..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/container.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Contenedor
-description: Quickstart se empaqueta como un contenedor de Docker
-sidebar_label: Contenedor
-sidebar_position: 10
----
-
-# Contenedor
-
-Quickstart se empaqueta como una imagen de contenedor de Docker y proporciona una configuración efímera predeterminada y no validante que debería funcionar para la mayoría de los desarrolladores. Al configurar un contenedor con esta imagen usando un volumen basado en el host (descrito a continuación en la sección "Configuración"), un operador obtiene acceso a la personalización completa de la configuración y la persistencia de datos.
-
-La imagen de Quickstart [docker](https://hub.docker.com/r/stellar/quickstart) utiliza el siguiente software:
-
-- [PostgreSQL](https://www.postgresql.org)
-- [stellar-core](https://github.com/stellar/stellar-core)
-- [horizon](https://github.com/stellar/stellar-horizon)
-- [friendbot](https://github.com/stellar/friendbot)
-- [stellar-rpc](https://github.com/stellar/stellar-rpc/tree/main/cmd/stellar-rpc)
-- [supervisord](http://supervisord.org/)
-
-El CLI de Stellar tiene comandos para iniciar y detener un contenedor de Quickstart, y también un comando para obtener los registros de un contenedor en ejecución. Consulta la [documentación](../../cli/stellar-cli.mdx#stellar-container) del CLI de Stellar para más información.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/operation-modes.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/operation-modes.mdx
deleted file mode 100644
index 6b42be228c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/operation-modes.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Modos de Operación
-description: Quickstart puede operar en diferentes modos para diferentes casos de uso
-sidebar_label: Modos de Operación
-sidebar_position: 30
----
-
-# Modos de Operación
-
-## Contenedores en Segundo Plano vs. Interactivos
-
-Los contenedores de Docker pueden ejecutarse de manera interactiva (usando las banderas `-it`) o en un estado de fondo y separado (usando la bandera `-d`). Muchos de los comandos de ejemplo a continuación utilizan las banderas `-it` para ayudar en la depuración, pero en muchos casos, solo querrás ejecutar un nodo en segundo plano. Se recomienda que utilices las [guías](https://docs.docker.com/get-started) en docker para familiarizarte con su uso.
-
-## Modo efímero
-
-El modo efímero se proporciona para admitir entornos de desarrollo y pruebas. Cada vez que inicias un contenedor en modo efímero, la base de datos comienza vacía y se utilizará un archivo de configuración predeterminado para la red adecuada.
-
-Iniciar un nodo efímero es simple, solo elabora un comando `docker run` para lanzar la imagen adecuada, pero no montes un volumen. Para elaborar tu comando de docker, necesitas el nombre de la red que planeas usar y las banderas para exponer los puertos que deseas que estén disponibles (consulta la sección llamada "Puertos" a continuación para aprender sobre la exposición de puertos). Así, lanzar un nodo de testnet mientras expones Horizon sería:
-
-```sh
-docker run --rm -it -p "8000:8000" --name stellar stellar/quickstart --testnet
-```
-
-Como parte del lanzamiento, un contenedor en modo efímero generará una contraseña aleatoria para asegurar el servicio de postgresql y la mostrará en la salida estándar. Puedes usar esta contraseña (siempre que hayas expuesto el puerto de postgresql) para acceder a la base de datos de postgresql en ejecución.
-
-## Modo persistente
-
-En comparación con el modo efímero, el modo persistente es más complicado de operar, pero también más poderoso. El modo persistente utiliza un volumen de host montado, un directorio en la máquina host que se expone al contenedor de docker en ejecución, para almacenar todos los datos de la base de datos así como los archivos de configuración utilizados para ejecutar servicios. Esto te permite gestionar y modificar estos archivos desde el sistema host.
-
-Nota que no hay garantía de que la organización de los archivos del volumen permanezca consistente entre las versiones de la imagen que ocurren en cada commit al repositorio stellar/quickstart. En cualquier momento se pueden añadir nuevos archivos, eliminar archivos antiguos, o cambiar las dependencias y referencias entre ellos. Por esta razón, el modo persistente está destinado principalmente a ejecutar instancias de prueba de corta duración para desarrollo. Si se necesita consistencia durante un período de tiempo, utiliza referencias de digest de imagen para fijar a una compilación específica.
-
-Iniciar un contenedor en modo persistente es igual que en modo efímero con una excepción:
-
-```sh
-docker run --rm -it -p "8000:8000" -v "/home/scott/stellar:/opt/stellar" --name stellar stellar/quickstart --testnet
-```
-
-La opción `-v` en el ejemplo anterior le dice a docker que monte el directorio del host `/home/scott/stellar` en el contenedor en la ruta `/opt/stellar`. Puedes personalizar el directorio del host a cualquier ubicación que desees, simplemente asegúrate de usar el mismo valor cada vez que inicies el contenedor. También nota: se requiere una ruta de directorio absoluta. La segunda parte del montaje de volumen (`/opt/stellar`) nunca debe ser cambiada. Este directorio especial es verificado por el contenedor para ver si está montado desde el sistema host, lo cual se usa para determinar si debemos iniciar en modo efímero o persistente.
-
-Al lanzar un contenedor en modo persistente por primera vez, el script de lanzamiento notará que el volumen montado está vacío. Esto desencadenará un proceso de inicialización interactivo para completar la configuración inicial para el contenedor. Esta inicialización interactiva añade algunas complicaciones al proceso de configuración porque en la mayoría de los casos no querrás ejecutar el contenedor interactivamente durante la operación normal, sino más bien en segundo plano. Recomendamos los siguientes pasos para configurar un nodo en modo persistente:
-
-1. Ejecuta una sesión interactiva del contenedor al principio, asegurándote de que todos los servicios inicien y funcionen correctamente.
-2. Apaga el contenedor interactivo (usando Ctrl-C).
-3. Inicia un nuevo contenedor usando el mismo directorio del host en segundo plano.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/ports.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/ports.mdx
deleted file mode 100644
index 7cdd24bf0d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/ports.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Puertos
-description: Quickstart puede operar en diferentes modos para diferentes casos de uso
-sidebar_label: Puertos
-sidebar_position: 40
----
-
-# Puertos
-
-Quickstart expone un puerto principal a través del cual los servicios proporcionan sus APIs:
-
-| Puerto | Servicio                         | Descripción           |
-| ------ | -------------------------------- | --------------------- |
-| 8000   | horizon, stellar-rpc, friendbot  | puerto http principal |
-
-Quickstart también expone varios otros puertos que la mayoría de los desarrolladores no necesitan, pero están disponibles:
-
-| Puerto  | Servicio                    | Descripción                         |
-| ------- | --------------------------- | ----------------------------------- |
-| 5432    | postgresql                  | puerto de acceso a la base de datos |
-| 6060    | horizon                     | puerto de administración            |
-| 6061    | stellar-rpc                 | puerto de administración            |
-| 11625   | stellar-core                | puerto de nodo usuario              |
-| 11626   | stellar-core                | puerto http principal               |
-| 11725   | stellar-core (horizon)      | puerto de nodo usuario              |
-| 11726   | stellar-core (horizon)      | puerto http principal               |
-| 11825   | stellar-core (stellar-rpc)  | puerto de nodo usuario              |
-| 11826   | stellar-core (stellar-rpc)  | puerto http principal               |
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/run-command-examples.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/run-command-examples.mdx
deleted file mode 100644
index f0e44f5322..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/run-command-examples.mdx
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: Ejecutar comandos
-description: Ejemplos de comandos para iniciar Quickstart en los diferentes modos
-sidebar_label: Ejecutar comandos
-sidebar_position: 50
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-# Ejecutar comandos
-
-A continuación, se presenta una lista de varias maneras en que puedes ejecutar el contenedor Quickstart, anotadas para ilustrar qué opciones están habilitadas. También se recomienda que aprendas y te familiarices con el comando de docker. Iniciar una red dev/test local efímera solamente:
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-docker run -d \
-  -p "8000:8000" \
-  --name stellar \
-  stellar/quickstart \
-  --local
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-docker run -d `
-  -p "8000:8000" `
-  --name stellar `
-  stellar/quickstart `
-  --local
-```
-
-</TabItem>
-
-</Tabs>
-
-Iniciar un nodo testnet efímero en primer plano:
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-docker run --rm -it \
-  -p "8000:8000" \
-  --name stellar \
-  stellar/quickstart \
-  --testnet
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-docker run --rm -it `
-  -p "8000:8000" `
-  --name stellar `
-  stellar/quickstart `
-  --testnet
-```
-
-</TabItem>
-
-</Tabs>
-
-Iniciar un nuevo nodo persistente usando el directorio del host `/str`:
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-docker run -it --rm \
-  -p "8000:8000" \
-  -v "/str:/opt/stellar" \
-  --name stellar \
-  stellar/quickstart \
-  --testnet
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-docker run -it --rm `
-  -p "8000:8000" `
-  -v "/str:/opt/stellar" `
-  --name stellar `
-  stellar/quickstart `
-  --testnet
-```
-
-</TabItem>
-
-</Tabs>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/service-options.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/service-options.mdx
deleted file mode 100644
index b204af3ffb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/advanced-usage/service-options.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Opciones del Servicio
-description: El inicio rápido se puede comenzar con todos los servicios habilitados, o con servicios seleccionados habilitados
-sidebar_label: Opciones del Servicio
-sidebar_position: 20
----
-
-# Opciones del Servicio
-
-Todos los modos de red ejecutan todos los servicios (Core, Horizon y RPC) por defecto, pero la opción --enable se puede usar para habilitar solo algunos de los servicios. El comportamiento de la opción habilitar es ligeramente diferente en modo de red local.
-
-La opción toma una lista de nombres de servicio separados por comas para habilitar. Para habilitar todos los servicios, que es el comportamiento por defecto, usa:
-
-```sh
---enable core,horizon,rpc
-```
-
-Para ejecutar solo servicios seleccionados, simplemente especifica solo esos servicios. Por ejemplo, para habilitar el RPC, usa:
-
-```sh
- --enable rpc
-```
-
-:::info
-
-En modo de red local, el servicio principal siempre se ejecuta sin importar qué opciones se pasen, el servicio de grifo Friendbot se ejecuta siempre que Horizon está en funcionamiento, y Horizon se ejecuta cuando se solicita RPC para que Friendbot esté disponible.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/README.mdx
deleted file mode 100644
index 30eab5563f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/README.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Despliegue en la nube
-description: Quickstart se puede desplegar en cualquier nube para crear una red de prueba compartible
-sidebar_label: Despliegue en la nube
-sidebar_position: 45
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Despliegue en la nube
-
-Quickstart puede desplegarse en una plataforma en la nube para crear una red de pruebas compartible para pruebas coordinadas y multiusuario.
-
-Cualquier plataforma que admita un entorno de ejecución de contenedores puede desplegar la imagen de Quickstart:
-
-```
-docker.io/stellar/quickstart:latest
-```
-
-Utiliza las siguientes variables de entorno para configurar la imagen:
-
-- `NETWORK` - La red que el contenedor configurará o a la que se conectará. Uno de:
-  - `local` - Se creará una nueva red local para desarrollo/pruebas.
-  - `testnet` - El contenedor se conectará a la testnet pública.
-- `NETWORK_PASSPHRASE` - Para redes `local`, la frase de contraseña de red que se usará.
-- `RANDOMIZE_NETWORK_PASSPHRASE` - Para redes `local`, la frase de contraseña tendrá un sufijo aleatorio.
-- `LIMITS` - Los límites de red que se configurarán para los contratos inteligentes. Uno de:
-  - `testnet` - Límites que igualarán la testnet pública.
-  - `unlimited` - Límites máximos admitidos por la red bajo cualquier configuración. Útil para pruebas experimentales antes de la optimización.
-
-:::warning
-
-Quickstart está diseñado para desarrollo y pruebas, no para producción.
-
-:::
-
-Ejemplos de cómo desplegar en diferentes proveedores:
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/_category_.json
deleted file mode 100644
index 4fb6019997..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-}
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/digitalocean.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/digitalocean.mdx
deleted file mode 100644
index 31aefb605a..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/digitalocean.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: DigitalOcean
-description: Desplegar Quickstart en DigitalOcean
-sidebar_label: DigitalOcean
-sidebar_position: 10
----
-
-# DigitalOcean
-
-Despliega en DigitalOcean App Platform usando el siguiente enlace:
-
-[![Deploy to DigitalOcean](https://www.deploytodo.com/do-btn-blue.svg)](https://cloud.digitalocean.com/apps/new?repo=https://github.com/stellar/quickstart/tree/master)
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/fly.io.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/fly.io.mdx
deleted file mode 100644
index d91b94df83..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/cloud/fly.io.mdx
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Fly.io
-description: Desplegar introducción rápida en fly.io
-sidebar_label: Fly.io
-sidebar_position: 10
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-# Fly.io
-
-Desplegar en Fly.io siguiendo los pasos a continuación.
-
-Instala la CLI de Fly. Consulta [fly.io/docs/flyctl/install](https://fly.io/docs/flyctl/install) para las instrucciones.
-
-Inicia la imagen:
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-<TabItem value="unix" label="macOS/Linux">
-
-```shell
-fly launch \
-    --image docker.io/stellar/quickstart:latest \
-    --ha=false \
-    --env NETWORK=local \
-    --env LIMITS=testnet \
-    --env NETWORK_PASSPHRASE="My Network" \
-    --internal-port 8000
-```
-
-</TabItem>
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-fly launch `
-    --image docker.io/stellar/quickstart:latest `
-    --ha=false `
-    --env NETWORK=local `
-    --env LIMITS=testnet `
-    --env NETWORK_PASSPHRASE="My Network" `
-    --env RANDOMIZE_NETWORK_PASSPHRASE=false `
-    --internal-port 8000
-```
-
-</TabItem>
-</Tabs>
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/README.mdx
deleted file mode 100644
index 37250a7376..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Depuración
-description: Usa Quickstart para depuración
-sidebar_label: Depuración
-sidebar_position: 40
----
-
-import DocCardList from "@theme/DocCardList";
-
-# Depuración
-
-Llegará un momento en que querrás inspeccionar el contenedor en ejecución, ya sea para depurar uno de los servicios, revisar registros, o quizás realizar algunas otras tareas administrativas.
-
-Hay diferentes formas de depurar Quickstart:
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/_category_.json
deleted file mode 100644
index 4fb6019997..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-}
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/diagnostic-events.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/diagnostic-events.mdx
deleted file mode 100644
index 638e211420..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/diagnostic-events.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Eventos de diagnóstico
-description: Los eventos de diagnóstico de Soroban contienen registros sobre eventos internos
-sidebar_label: Eventos de diagnóstico
-sidebar_position: 10
----
-
-# Eventos de diagnóstico
-
-Los eventos de diagnóstico de Soroban contienen registros sobre eventos internos que han ocurrido mientras un contrato está ejecutándose. Son particularmente útiles para depurar por qué un contrato está atrapado (en pánico).
-
-Para habilitar los eventos de diagnóstico de Soroban, proporciona la siguiente opción de línea de comandos al iniciar el contenedor: `--enable-soroban-diagnostic-events`
-
-En modo de red local, los diagnósticos están habilitados por defecto y se pueden desactivar con: `--disable-soroban-diagnostic-events`
-
-:::info
-
-Los eventos de diagnóstico no están medidos y su ejecución no está medida ni restringida por límites de red o límites de recursos de transacciones. Esto significa que los recursos consumidos por una instancia con eventos de diagnóstico habilitados pueden exceder los recursos normalmente requeridos por un despliegue con eventos de diagnóstico deshabilitados.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/viewing-logs.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/viewing-logs.mdx
deleted file mode 100644
index 4f8ebbb21c..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/debugging/viewing-logs.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Ver registros
-description: Ver registros dentro del contenedor Quickstart
-sidebar_label: Ver registros
-sidebar_position: 20
----
-
-# Ver registros
-
-Puedes ver registros iniciando un nuevo shell interactivo dentro del contenedor en ejecución:
-
-```sh
-docker exec -it stellar /bin/bash
-```
-
-El comando anterior asume que iniciaste tu contenedor con el nombre `stellar`. Reemplaza ese nombre con el que elegiste, si es diferente. Cuando se ejecute, abrirá un shell interactivo que se ejecuta como root dentro del contenedor.
-
-Los registros se pueden encontrar dentro del contenedor en la ruta `/var/log/supervisor/`. Se mantiene un archivo tanto para el **_stdout_** como para el **_stderr_** de los procesos gestionados por [supervisord](https://supervisord.org/index.html). Además, puedes usar el comando `tail` proporcionado por supervisord.
-
-Alternativamente, para mostrar todos los registros en la salida del contenedor para todos los servicios, agrega la opción `--logs`.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/explorer.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/explorer.mdx
deleted file mode 100644
index 2e5d1b22f4..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/explorer.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Explorador
-description: Usar Explorador cuando Lab se ejecuta en Quickstart
-sidebar_label: Explorador
-sidebar_position: 15
----
-
-Cuando ejecutas **Stellar Lab** mediante **Quickstart**, un explorador ligero de bloques/transacciones está disponible automáticamente junto a Lab. Esto facilita inspeccionar la actividad de la red en tu red local de Quickstart mientras construyes y pruebas.
-
-### URLs
-
-**Lab (inicio):** `http://localhost:8000/lab`
-
-**Explorador:** `http://localhost:8000/lab/transactions-explorer`
-
-Si usas un host o puerto personalizados al iniciar Quickstart, reemplaza `localhost:8000` por tu dirección elegida.
-
-### Qué puedes hacer con el Explorador
-
-- Examinar las transacciones recientes en tu red Quickstart.
-- Explorar una transacción para ver sus detalles (hash, resultado, operaciones involucradas, etc.).
-- Usarlo junto con las herramientas de Lab (por ejemplo, construir/firma de transacciones) para verificar rápidamente los resultados de la red local.
-
-### Resumen
-
-1. Inicia Quickstart (según las instrucciones del repositorio).
-2. Abre Lab: `http://localhost:8000/lab`.
-3. Abre el Explorador: `http://localhost:8000/lab/transactions-explorer`.
-4. Construye y envía transacciones en Lab, luego cambia al Explorador para confirmar que se registraron.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/faucet.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/faucet.mdx
deleted file mode 100644
index e7b7356964..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/faucet.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Grifo
-description: Usa el grifo Friendbot para financiar cuentas en Quickstart
-sidebar_position: 30
----
-
-# Grifo
-
-Quickstart utiliza Friendbot como un grifo de activos nativos para testnet, futurenet y redes locales, igual que se usa Friendbot en el testnet público y futurenet.
-
-Friendbot está disponible en `:8000/friendbot` y puede usarse para financiar cuentas y contratos. Por ejemplo:
-
-```sh
-curl http://localhost:8000/friendbot?addr=G...
-```
-
-En modo de red local, se está ejecutando un Friendbot local. En modos de red testnet y futurenet, las solicitudes al `:8000/friendbot` endpoint se redirigirán a las implementaciones de Friendbot para la red respectiva.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/README.mdx
deleted file mode 100644
index 605a7c3547..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/README.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Comenzar
-description: Usa el Stellar CLI para instalar Quickstart
-sidebar_label: Comenzar
-sidebar_position: 10
----
-
-# Comenzar
-
-En esta guía, configurarás Quickstart usando el Stellar CLI. Quickstart usará la configuración estándar, que funcionará para muchos casos de uso. Para una configuración más personalizada de Quickstart, consulta la sección de Uso Avanzado.
-
-## Requisitos Previos
-
-Antes de seguir los pasos de esta guía, deben estar instalados y configurados los siguientes elementos en tu sistema local:
-
-- [Stellar CLI](../../../build/smart-contracts/getting-started/setup.mdx#install-the-stellar-cli)
-- [Docker](https://docs.docker.com/get-started/get-docker/)
-
-## Iniciar Quickstart
-
-Cuando uses el Stellar CLI para iniciar Quickstart, la imagen de docker se descargará automáticamente, y se aplicará la configuración estándar. Lo único que necesitas hacer para empezar es ejecutar este comando:
-
-```sh
-stellar container start local
-```
-
-En este ejemplo, se elige el modo de red local, consulta la sección de Modos de Red para más información sobre los modos de red disponibles. Después de ejecutar el comando, Quickstart estará funcionando en tu sistema local. En el siguiente paso, usarás Stellar Lab para verificar que Quickstart está funcionando correctamente.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/_category_.json
deleted file mode 100644
index 4fb6019997..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": true
-}
\ No newline at end of file
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/connect-stellar-lab.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/connect-stellar-lab.mdx
deleted file mode 100644
index 74f1fdb0c2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/connect-stellar-lab.mdx
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Conectar Stellar Lab
-description: Conectar Quickstart a Stellar Lab
-sidebar_label: Conectar Stellar Lab
-sidebar_position: 10
----
-
-# Conectar Stellar Lab
-
-Una forma de confirmar que Quickstart se inició correctamente y está disponible es conectar a Quickstart desde [Stellar Lab](https://lab.stellar.org).
-
-Navega a [Stellar Lab](https://lab.stellar.org) y en la esquina superior derecha, usa el menú desplegable para seleccionar la red personalizada. Esto te permitirá proporcionar los detalles de conexión — utiliza estos detalles de testnet:
-
-- URL RPC: `http://localhost:8000/rpc`
-- URL Horizon: `http://localhost:8000`
-- Frase de contraseña de red: `Standalone Network ; February 2017`
-
-![Stellar Lab](/assets/quickstart/stellar_lab_screenshot.png)
-
-Cambia a la red personalizada y puedes comenzar a interactuar con Quickstart. Una buena primera tarea podría ser navegar a la pestaña de Cuenta, crear una cuenta y financiarla con Friendbot (faucet).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/deploy-smart-contract.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/deploy-smart-contract.mdx
deleted file mode 100644
index 981f878c69..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/getting-started/deploy-smart-contract.mdx
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Desplegar Contrato Inteligente
-description: Desplegar un contrato inteligente en la red local de Quickstart.
-sidebar_label: Desplegar Contrato Inteligente
-sidebar_position: 20
----
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-import { getPlatform } from "@site/src/helpers/getPlatform";
-
-# Desplegar Contrato Inteligente
-
-Ahora puedes desplegar un contrato inteligente en la red local de Quickstart. Si ya tienes un contrato inteligente, puedes desplegar tu contrato inteligente existente, de lo contrario, puedes seguir esta guía para crear un contrato inteligente y desarrollarlo.
-
-## Crear Identidad
-
-Antes de que puedas desplegar y al invocar un contrato inteligente, necesitas crear una identidad en la red local. La identidad es un parámetro requerido, referido como `source-account` o `source`. Así es como puedes crear una identidad en la red local llamada `bob`:
-
-```sh
-stellar keys generate --global bob --network local --fund
-```
-
-La identidad tendrá una clave privada y una clave pública, y puede ser llamada por el nombre `bob` por conveniencia.
-
-## Desplegar contrato
-
-Desplegar un contrato inteligente en Quickstart testnet no es muy diferente de desplegar un contrato inteligente en el testnet público. Especifica la URL RPC para que sea la de Quickstart y puedes desplegarlo:
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract deploy \
-  --wasm target/wasm32v1-none/release/hello_world.wasm \
-  --source-account bob \
-  --network local \
-  --alias hello_world
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract deploy `
-  --wasm target/wasm32v1-none/release/hello_world.wasm `
-  --source-account bob `
-  --network local `
-  --alias hello_world
-```
-
-</TabItem>
-
-</Tabs>
-
-## Al invocar contrato
-
-Ahora que has desplegado el contrato inteligente en el Quickstart testnet, también puedes al invocarlo:
-
-<Tabs groupId="platform" defaultValue={getPlatform()}>
-
-<TabItem value="unix" label="macOS/Linux">
-
-```sh
-stellar contract invoke \
-  --id hello_world \
-  --source-account bob \
-  --network local \
-  -- \
-  hello \
-  --to RPC
-```
-
-</TabItem>
-
-<TabItem value="windows" label="Windows (PowerShell)">
-
-```powershell
-stellar contract invoke `
-  --id hello_world `
-  --source-account bob `
-  --network local `
-  -- `
-  hello `
-  --to RPC
-```
-
-</TabItem>
-
-</Tabs>
-
-¡Eso es todo!
-
-Ahora puedes sumergirte en algunos de los beneficios de ejecutar tu propio nodo local con Quickstart. Algunos beneficios son que es más rápido al invocar un contrato, tienes mejores opciones de depuración, etc.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/network-modes.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/network-modes.mdx
deleted file mode 100644
index 21325b64d7..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/quickstart/network-modes.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Modos de Red
-description: Quickstart admite los modos de red local, testnet, futurenet y pubnet
-sidebar_label: Modos de Red
-sidebar_position: 20
----
-
-# Modos de Red
-
-Quickstart puede operar en diferentes modos de red, y debes decidir qué modo es adecuado para tu propósito antes de iniciar el contenedor. Los cuatro modos de red disponibles son `local`, `testnet`, `futurenet` y `pubnet` (mainnet).
-
-El [Stellar Lab](https://lab.stellar.org) puede conectar con Quickstart, lo que facilita la creación y financiación de cuentas.
-
-## Local
-
-El modo de red local te permite personalizar Quickstart añadiendo parámetros al comando de inicio del contenedor. Los parámetros disponibles son:
-
-- `--protocol-version {version}` para ejecutar una versión específica del protocolo (por defecto es la última versión)
-- `--limits {limits}` para configurar límites de recursos específicos de Soroban a uno de:
-  - `default` deja los límites configurados extremadamente bajos, que es la configuración predeterminada de stellar-core
-  - `testnet` establece los límites para igualar los utilizados en testnet (la configuración predeterminada de Quickstart)
-  - `unlimited` establece los límites a los máximos recursos que se pueden configurar
-
-Algunas configuraciones y valores son específicos del modo de red local, de los cuales debes ser consciente al ejecutar Quickstart en el modo de red local.
-
-### Frase Secreta de la Red
-
-La frase secreta de la red predeterminada para la red local es:
-
-```sh
-Standalone Network ; February 2017
-```
-
-Establece la frase secreta de la red en el SDK o la herramienta que estás utilizando. Si los clientes utilizan una frase secreta de red incorrecta al firmar transacciones, las transacciones fallarán con un error de autenticación.
-
-### Cuenta Raíz
-
-La cuenta raíz de la red está fijada en:
-
-```sh
-Public Key: GBZXN7PIRZGNMHGA7MUUUF4GWPY5AYPV6LY4UV2GL6VJGIQRXFDNMADI
-Secret Key: S...
-```
-
-La cuenta raíz se deriva de la frase secreta de la red y si la frase secreta de la red se cambia, la cuenta raíz también cambiará. Para recuperar los detalles de la cuenta raíz al cambiar la frase secreta de la red, consulta los registros de stellar-core en su primer inicio. Consulta [Visualización](https://github.com/stellar/quickstart?tab=readme-ov-file#viewing-logs) de registros para más detalles.
-
-En modo de red local, un ledger ocurre cada segundo, por lo que las transacciones se finalizan más rápido que en redes desplegadas.
-
-## Testnet
-
-El modo de red testnet es recomendado para el desarrollo de software. Las cuentas creadas en testnet pueden ser financiadas con Friendbot (faucet) para que no tengas que preocuparte por perder tokens reales al probar tu software.
-
-## Futurenet
-
-El modo de red futurenet funciona como el testnet, y la mayor diferencia es que contiene las últimas características de vanguardia que aún no han llegado al testnet. Esto puede ser útil para desarrolladores que construyen contratos inteligentes que dependen de nuevas características que no están disponibles en testnet, o para probar contratos inteligentes existentes antes de los cambios en test- y mainnet.
-
-## Pubnet
-
-En modo de red pubnet, Quickstart será parte de la red pública de producción de Stellar, también conocida como mainnet. En modo pubnet, Quickstart consumirá más disco, memoria y recursos de CPU debido al tamaño del ledger y la frecuencia de transacciones. Si ocurren advertencias de espacio en disco y la imagen está siendo utilizada en un runtime de Docker que usa una VM, como la de macOS y Windows, puede que sea necesario aumentar la asignación de espacio en disco de la VM.
-
-:::caution
-
-Quickstart no es adecuado para ningún uso en producción ya que tiene una cuenta raíz fija. Cualquier red privada destinada a un uso en producción también requeriría una frase secreta de red única.
-
-:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/ramps/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/ramps/README.mdx
deleted file mode 100644
index 041352888b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/ramps/README.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Rampas
-sidebar_position: 60
----
-
-import DocCardList from "@theme/DocCardList";
-
-Rampas de entrada y salida (llamadas [anchors](../../learn/fundamentals/anchors.mdx) en el universo Stellar) que conectan la red Stellar con las vías de pago tradicionales.
-
-Stellar cuenta con servicios de anchor que operan a nivel mundial. Consulta el [Directorio de Anclajes](https://anchors.stellar.org/) para obtener información sobre los anchors de Stellar.
-
-Los anchors pueden emitir sus propios activos en la red Stellar o pueden respaldar activos que ya existen.
-
-Puedes configurar un anchor usando la [Anchor Platform](../../platforms/anchor-platform/README.mdx) mantenida por SDF, que es la forma más fácil de desplegar un servicio de anchor compatible con las Propuestas del Ecosistema Stellar (SEP).
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/ramps/moneygram.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/ramps/moneygram.mdx
deleted file mode 100644
index 44efde228b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/ramps/moneygram.mdx
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Rampas de MoneyGram
-sidebar_label: Rampas de MoneyGram
-sidebar_position: 10
----
-
-MoneyGram Ramps es un producto de MoneyGram que permite a los usuarios de aplicaciones de terceros, como billeteras criptográficas y exchanges, depositar (cash-in) y retirar (cash-out) USDC en Stellar.
-
-[Explora la documentación de MoneyGram Ramps](https://developer.moneygram.com/moneygram-developer/docs/integrate-moneygram-ramps) para conocer los requisitos técnicos para integrar MoneyGram Ramps en una billetera existente o para crear una nueva aplicación de billetera.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/scaffold-stellar.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/scaffold-stellar.mdx
deleted file mode 100644
index eb3f2fcc5b..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/scaffold-stellar.mdx
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: Scaffold Stellar
-description: Kit de herramientas por convención en lugar de configuración para el desarrollo de contratos inteligentes en Stellar
-sidebar_label: Scaffold Stellar
-sidebar_position: 45
----
-
-**Scaffold Stellar** es un kit de herramientas para desarrolladores para crear aplicaciones descentralizadas (dApps) y contratos inteligentes en la blockchain de Stellar. Te ayuda a pasar de la idea a una dApp full-stack funcional más rápido — proporcionando herramientas CLI, plantillas de contratos reutilizables, un registro de contratos inteligentes y un frontend moderno.
-
-Visita la página principal de [Scaffold Stellar](https://scaffoldstellar.org) para guías, documentación y más.
-
-## Prerequisitos
-
-Antes de comenzar, asegúrate de tener instalado lo siguiente:
-
-| Herramienta                                             | Descripción                                                        | Enlace de instalación                                         |
-| ------------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------- |
-| [Rust & Cargo](https://www.rust-lang.org/tools/install) | Para escribir y compilar contratos inteligentes                    | `curl https://sh.rustup.rs -sSf \| sh`                        |
-| [Node.js & npm](https://nodejs.org/)                    | Para el desarrollo frontend                                        | Descarga desde el sitio oficial                               |
-| [Stellar CLI](https://github.com/stellar/stellar-cli)   | Para construir, desplegar e interactuar con contratos inteligentes | [`Link for the repo`](https://github.com/stellar/stellar-cli) |
-| [Docker](https://www.docker.com/get-started/)           | Para ejecutar una red Stellar local mediante la imagen `stellar/quickstart` | [Descargar Docker Desktop](https://www.docker.com/products/docker-desktop/) |
-
-## Comenzar
-
-### Instalación
-
-Instala las herramientas CLI requeridas:
-
-```bash
-# Install stellar-scaffold CLI
-cargo install --locked stellar-scaffold-cli
-
-# Install registry CLI (to easily deploy your contract to the registry)
-cargo install --locked stellar-registry-cli
-```
-
-:::tip Para una instalación más rápida, usa cargo-binstall
-
-En lugar de compilar desde el código fuente, puedes acelerar la instalación obteniendo el binario directamente usando [cargo-binstall](https://github.com/cargo-bins/cargo-binstall). Esto es especialmente útil en entornos de CI.
-
-```bash
-# Install cargo-binstall (see other install methods in their README linked above)
-cargo install cargo-binstall
-
-# Install the binaries
-cargo binstall stellar-scaffold-cli stellar-registry-cli
-```
-
-:::
-
-### Crear un proyecto nuevo
-
-1. Inicializa un proyecto nuevo:
-
-```bash
-stellar scaffold init my-project
-cd my-project
-```
-
-Esto creará la estructura del proyecto en el directorio que especificaste con varios contratos de ejemplo. O puedes comenzar desde el [OpenZeppelin Wizard](./openzeppelin-contracts) para personalizar tu contrato y comenzar un proyecto Scaffold Stellar desde allí.
-
-2. Inicia la aplicación:
-
-```bash
-npm start
-```
-
-¡Tendrás una dApp en funcionamiento integrada con los contratos iniciales, lista para comenzar a desarrollar!
-
-Explora el archivo `environments.toml` para personalizar tu(s) entorno(s) de desarrollo que se configuran mediante tu archivo `.env`.
-
-## Estructura del proyecto
-
-Cuando ejecutas `stellar scaffold init`, crea una estructura de proyecto full-stack con contratos de ejemplo y un frontend moderno:
-
-```
-my-project/
-├── contracts/          # Rust smart contracts (compiled to WASM)
-├── packages/           # Auto-generated TypeScript contract clients
-├── src/                # React frontend code
-│   ├── components/     # Reusable UI components
-│   ├── contracts/      # Contract interaction logic
-│   ├── App.tsx         # Main app component
-│   └── main.tsx        # Entry point
-├── environments.toml   # Configuration per environment (dev/test/prod)
-├── .env                # Local environment variables
-├── package.json        # Frontend packages
-└── target/             # Build outputs
-```
-
-Esta plantilla proporciona una aplicación frontend lista para usar con contratos inteligentes de ejemplo y sus clientes TypeScript. El frontend está configurado con `Vite`, `React` e incluye componentes básicos para interactuar con los contratos.
-
-## Características
-
-- **Plugins CLI para Stellar**
-  - `stellar scaffold init`: Inicializar proyectos nuevos de contratos inteligentes Stellar
-  - `stellar scaffold upgrade`: Transformar espacios de trabajo de contratos Stellar existentes en proyectos Scaffold
-  - `stellar scaffold build`: Construir contratos y generar clientes TypeScript
-  - `stellar scaffold watch`: Modo desarrollo con recarga en caliente
-  - `stellar registry`: Publicar, desplegar y gestionar contratos inteligentes
-
-- **Gestión de entornos**
-  - Compilaciones específicas para cada entorno (desarrollo, pruebas, staging, producción)
-  - Integración fluida con contratos locales y desplegados
-  - Configuración de red mediante `environments.toml`
-  - Admite múltiples entornos de despliegue
-
-- **Registro de contratos inteligentes**
-  - Plataforma de publicación on-chain de binarios Wasm
-  - Gestión de versiones y nombrado de contratos
-  - Verificación de contratos y gestión de dependencias
-  - Flujo de despliegue seguro para testnet y mainnet
-
-### Más recursos
-
-Para obtener más información, consulta el [proyecto en GitHub](https://github.com/theahaco/scaffold-stellar).
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/README.mdx
deleted file mode 100644
index 3271aa4d59..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/README.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Explorar SDKs para el Desarrollo de Blockchain con JavaScript, Python y Más
-sidebar_label: SDKs
-description: Explorar SDKs para desarrollar aplicaciones de blockchain. Usar JavaScript, Python y más para interactuar con la red Stellar y agilizar el desarrollo.
-sidebar_position: 10
----
-
-# SDKs
-
-import DocCardList from "@theme/DocCardList";
-
-La sección del SDK se divide en tres categorías:
-
-- [SDKs de contrato](./contract-sdks.mdx) que se utilizan para crear contratos inteligentes que se desplegarán en la red Stellar;
-- [SDKs de cliente y XDR](./client-sdks.mdx) que son utilizados por aplicaciones para interactuar con la red;
-- [Crea tu propio SDK](./build-your-own.mdx) que detalla los requisitos mínimos para crear tu propio SDK.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/_category_.json
deleted file mode 100644
index 0d44758281..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-  "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/build-your-own.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/build-your-own.mdx
deleted file mode 100644
index 14986948b5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/build-your-own.mdx
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: Desarrollar tu propio SDK de contrato
-sidebar_position: 30
----
-
-:::note
-
-Esto es para crear un SDK para escribir contratos inteligentes.
-
-:::
-
-Soroban actualmente tiene un SDK mantenido por SDF para escribir contratos en Rust, que se puede encontrar [aquí][soroban-sdk]. Un SDK mantenido por la comunidad está disponible para escribir contratos en AssemblyScript, que se puede encontrar [aquí][as-soroban-sdk].
-
-Para crear SDKs para otros idiomas, se deben incluir varias cosas en el SDK para proporcionar a los contratos la base que necesitan para aceptar entradas, decodificarlas, almacenar datos, llamar a otros contratos, etc.
-
-A continuación se muestra una lista de funcionalidades que un SDK de Soroban necesita admitir para esas cosas, así como algunos detalles sobre lo que un SDK puede proporcionar en cuanto a capacidades de prueba.
-
-## Funcionalidad
-
-### Conversiones de Valor
-
-- [Val] codificar/decodificar
-- [Objeto] codificar/decodificar
-- [Símbolo] codificar/decodificar
-- [Opción] codificar/decodificar
-- [Error] codificar/decodificar
-
-### Funciones Host
-
-Las funciones host definidas en [env.json] son funciones que se pueden llamar desde el entorno Wasm Guest. Estas necesitan estar disponibles para que los contratos las llamen, de alguna forma, preferiblemente envueltas para que los contratos tengan una interfaz más amigable.
-
-Las funciones host tienen nombres amigables en el archivo anterior, como `get_ledger_version`, sin embargo, en el Wasm solo se pueden importar a través de nombres cortos, como `x.4`. La letra que precede al punto es el módulo, y el valor después del punto es el nombre de la función. Las asignaciones están disponibles en env.rs.
-
-### Tipos de SDK
-
-Todos los tipos en [soroban-sdk](https://docs.rs/soroban-sdk) deberían ser admitidos. Notablemente:
-
-- [Mapa]
-- [Vec]
-- [Bytes]
-
-### Tipos Definidos por el Usuario
-
-Los contratos deberían poder crear tipos definidos por el usuario, como estructuras, uniones o enumeraciones, y hacer que se transmitan al host para almacenamiento y se transmitan de vuelta para carga.
-
-Los SDK hacen esto al convertir objetos hacia y desde un `Val`. En el [soroban-sdk] esto se refiere a un [Val].
-
-#### Estructuras
-
-Las estructuras con campos nombrados deben ser traducidas a un `Mapa` con claves como `Símbolos` y los valores como el valor del campo, es decir, `Mapa<Symbol, V>`.
-
-Las estructuras con campos no nombrados deben ser traducidas a un `Vec` con los valores como los elementos. es decir, `Vec<V>`.
-
-#### Uniones
-
-Las uniones (o enumeraciones en algunos idiomas) con variantes nombradas y valores de unidad o tupla deben ser traducidas a un `Vec` con el primer elemento como un `Símbolo` del nombre de la variante, y cero o más elementos adicionales representando un valor almacenado con la variante.
-
-#### Enumeraciones
-
-Las enumeraciones con valores enteros deben ser traducidas a un `u32`.
-
-### Errores Definidos por el Usuario
-
-Los errores son valores `u32` que se traducen a un [Error].
-
-### Generación de Meta del Entorno
-
-Los contratos deben contener una sección personalizada de Wasm con el nombre `contractenvmetav0` y contener un [`SCEnvMetaEntry`] serializado. La versión de la interfaz almacenada dentro debe igualar la versión de las funciones host admitidas.
-
-Para ver el Meta del Entorno, considera usar el Explorador de Contratos de Stellar Lab, o el comando de Stellar CLI `stellar contract info env-meta --contract-id <contract-id>`.
-
-### Generación de Meta del Contrato
-
-Los contratos pueden incluir opcionalmente una sección Wasm personalizada llamada `contractmetav0`, que contiene un [`SCMetaEntry`] serializado. Esta sección no es utilizada por la red en sí, pero permite a los contratos incorporar metadatos arbitrarios, incluyendo el nombre del contrato, versión, autor, interfaces admitidas, repositorio de origen o dominio principal. Las aplicaciones y herramientas pueden leer estos metadatos para proporcionar experiencias de desarrollador más ricas, mejor indexación, o un descubrimiento de contratos mejorado.
-
-Para agregar metadatos al Meta del Contrato, utiliza el comando de Stellar CLI `stellar contract build --meta <meta>`.
-
-Para ver el Meta del Contrato, utiliza el Explorador de Contratos de Stellar Lab, o el comando de Stellar CLI `stellar contract info meta --contract-id <contract-id>`.
-
-### Generación de Especificaciones de Contrato
-
-Los contratos deben contener una sección personalizada de Wasm con el nombre `contractspecv0` y contener un flujo serializado de [`SCSpecEntry`]. Debería haber un `SCSpecEntry` para cada función, estructura y unión exportada por el contrato.
-
-Para ver el Meta del Contrato, utiliza el Explorador de Contratos de Stellar Lab, o el comando de Stellar CLI `stellar contract info interface --contract-id <contract-id>`.
-
-## Pruebas
-
-Cualquier SDK de Soroban preferiblemente proporciona un entorno de prueba para ejecutar funciones de contrato en el contexto de un entorno de ejecución de Soroban. El [soroban-sdk] hace esto al incrustar la biblioteca de Rust del entorno Soroban, [soroban-env-host].
-
-El entorno de prueba debería incluir:
-
-- Invocación de funciones de contrato.
-- Pruebas de integración entre múltiples contratos.
-
-[soroban-sdk]: https://docs.rs/soroban-sdk
-[as-soroban-sdk]: https://github.com/Soneso/as-soroban-sdk
-[soroban-env-host]: https://github.com/stellar/rs-soroban-env
-[val]: https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-common/src/val.rs
-[error]: https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-common/src/error.rs
-[object]: https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-common/src/object.rs
-[symbol]: https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-common/src/symbol.rs
-[opción]: https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-common/src/option.rs
-[env.json]: https://github.com/stellar/rs-soroban-env/blob/main/soroban-env-common/env.json
-[map]: https://github.com/stellar/rs-soroban-sdk/blob/main/soroban-sdk/src/map.rs
-[vec]: https://github.com/stellar/rs-soroban-sdk/blob/main/soroban-sdk/src/vec.rs
-[bytes]: https://github.com/stellar/rs-soroban-sdk/blob/main/soroban-sdk/src/bytes.rs
-[`scenvmetaentry`]: https://github.com/stellar/stellar-xdr/blob/next/Stellar-contract-env-meta.x
-[`scspecentry`]: https://github.com/stellar/stellar-xdr/blob/next/Stellar-contract-spec.x
-[`scmetaentry`]: https://github.com/stellar/stellar-xdr/blob/next/Stellar-contract-meta.x
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/client-sdks.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/client-sdks.mdx
deleted file mode 100644
index 5bd27c2226..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/client-sdks.mdx
+++ /dev/null
@@ -1,127 +0,0 @@
----
-title: Simplificar el Desarrollo en Blockchain con SDKs para Java, Python y Más
-sidebar_label: Cliente y SDK XDR
-sidebar_position: 20
-description: Explora la biblioteca SDK de Stellar para simplificar el desarrollo en blockchain. Aprovecha Rust, JavaScript, Python y más para crear en y integrar con la red.
----
-
-# SDKs de Cliente y XDR
-
-Los SDK de Cliente y XDR son utilizados por aplicaciones para interactuar con la red.
-
-:::note
-
-Para SDKs para crear contratos inteligentes, consulta [SDKs de Contrato](./contract-sdks.mdx).
-
-:::
-
-Todos los SDK son open-source; presenta una incidencia de GitHub o una pull request en el repositorio específico del SDK si tienes preguntas o sugerencias.
-
-Cada SDK tiene su propio código fuente y documentación. Aprende a usar un SDK específico consultando la documentación.
-
-## SDK de JavaScript
-
-[SDK de JavaScript](https://github.com/stellar/js-stellar-sdk) | [Docs](https://stellar.github.io/js-stellar-sdk/) | [NPM](https://www.npmjs.com/package/@stellar/stellar-sdk)
-
-**El SDK de JavaScript es mantenido por SDF.**
-
-`stellar-sdk` es la biblioteca de JavaScript para comunicarse con Stellar RPC y Horizon. Admite crear transacciones en la red Stellar. Se utiliza para crear aplicaciones Stellar tanto en el navegador como en un entorno de Node.js.
-
-Proporciona:
-
-- Una API de capa de red para métodos Stellar RPC y la API de Horizon.
-- Facilidades para crear y firmar transacciones, para comunicarse con una instancia de RPC, para comunicarse con una instancia de Horizon, y para enviar transacciones o consultar el estado de la red.
-
-## SDK de Python
-
-[SDK de Python](https://github.com/StellarCN/py-stellar-base) | [Docs](https://stellar-sdk.readthedocs.io/en/latest/) | [Ejemplos](https://github.com/StellarCN/py-stellar-base/tree/master/examples)
-
-**El SDK de Python es mantenido por desarrolladores dedicados de la comunidad.**
-
-`py-stellar-base` es una biblioteca de Python para comunicarse con un servidor Stellar Horizon. Se utiliza para desarrollar aplicaciones Stellar en Python. Admite Python 3.7+ así como PyPy 3.7+.
-
-Este SDK es mantenido por un desarrollador dedicado de la comunidad.
-
-Proporciona:
-
-- Una API de capa de red para puntos finales de Horizon.
-- Instalaciones para construir y firmar transacciones, para comunicarse con una instancia Stellar Horizon y para enviar transacciones o consultar el historial de la red.
-
-## Rust
-
-La funcionalidad para interactuar con datos Stellar se puede encontrar en las siguientes crates de Rust:
-
-- `stellar-xdr` – [Code](https://github.com/stellar/rs-stellar-xdr) | [Docs](https://docs.rs/stellar-xdr)
-
-  Proporciona codificación/decodificación [XDR] e implementación de referencia de [XDR-JSON]. **Mantenido por SDF.**
-
-- `stellar-strkey` – [Código](https://github.com/stellar/rs-stellar-strkey) | [Docs](https://docs.rs/stellar-strkey)
-
-  Proporciona codificación/decodificación de Stellar Strkey (Dirección) [SEP-23]. **Mantenido por SDF.**
-
-[XDR]: ../../learn/fundamentals/data-format/xdr
-[XDR-JSON]: ../../learn/fundamentals/data-format/xdr-json.mdx
-[SEP-23]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md
-
-- `soroban-client` - [Código](https://github.com/rahul-soshte/rs-soroban-client) | [Documentación](https://docs.rs/soroban-client/latest/soroban_client/)
-
-  Una biblioteca Rust para interactuar con el entorno de contratos inteligentes Soroban. Proporciona APIs para crear y enviar transacciones, comunicarse con servidores RPC de Stellar y admite todas las operaciones clásicas de Stellar. **Mantenido por un desarrollador dedicado de la comunidad.**
-
-- `rs-stellar-rpc-client` - [Code](https://github.com/stellar/rs-stellar-rpc-client)
-
-  Cliente RPC de Rust para Stellar. **Mantenido por SDF.**
-
-## SDK de iOS
-
-[SDK de iOS](https://github.com/Soneso/stellar-ios-mac-sdk) | [Docs](https://github.com/Soneso/stellar-ios-mac-sdk/tree/master/docs) | [Docs de Contrato Inteligente](https://github.com/Soneso/stellar-ios-mac-sdk/blob/master/soroban.md)
-
-**Mantenido por un desarrollador dedicado de la comunidad.**
-
-El `stellar-ios-mac-sdk` es un SDK open source de Stellar para iOS y Mac. Proporciona APIs para crear transacciones y conectarse a Horizon. También proporciona funcionalidad para desplegar e invocar contratos inteligentes de Soroban y se comunica con el servidor RPC de Stellar.
-
-El SDK de iOS es mantenido por un desarrollador comunitario dedicado, Soneso.
-
-## SDK de Flutter
-
-[SDK de Flutter](https://github.com/Soneso/stellar_flutter_sdk) | [Docs](https://github.com/Soneso/stellar_flutter_sdk/blob/master/soroban.md)
-
-**Mantenido por un desarrollador dedicado de la comunidad.**
-
-El `stellar-flutter-sdk` es un SDK open source de Stellar para desarrolladores de Flutter. Proporciona APIs para crear transacciones y conectarse a Horizon. También proporciona funcionalidad para desplegar e invocar contratos inteligentes de Soroban y se comunica con el servidor RPC de Stellar.
-
-El SDK de Flutter de Stellar es mantenido por un desarrollador comunitario dedicado, Soneso.
-
-## SDK de PHP
-
-[SDK de PHP](https://github.com/Soneso/stellar-php-sdk) | [Docs](https://github.com/Soneso/stellar-php-sdk/blob/main/soroban.md)
-
-**Mantenido por un desarrollador dedicado de la comunidad.**
-
-El `stellar-php-sdk` es un SDK open source de Stellar para desarrolladores de PHP. Proporciona APIs para crear transacciones y conectarse a Horizon. También proporciona funcionalidad para desplegar e invocar contratos inteligentes de Soroban y se comunica con el servidor RPC de Stellar.
-
-El SDK de PHP de Stellar es mantenido por un desarrollador comunitario dedicado, Soneso.
-
-## SDK de Java
-
-[SDK de Java](https://github.com/lightsail-network/java-stellar-sdk) | [Docs](https://lightsail-network.github.io/java-stellar-sdk/)
-
-**Mantenido por un desarrollador dedicado de la comunidad.**
-
-`java-stellar-sdk` proporciona APIs para crear transacciones y conectarse a Horizon y también proporciona funcionalidad para desplegar e invocar contratos inteligentes de Soroban y se comunica con el servidor RPC de Stellar.
-
-## Go
-
-**El SDK de Go es mantenido por SDF.**
-
-Este SDK está dividido en paquetes separados, todos los cuales puedes encontrar en el [Go SDK](https://github.com/stellar/go-stellar-sdk). Las bibliotecas clave son:
-
-- `txnbuild` [SDK](https://github.com/stellar/go-stellar-sdk/tree/main/txnbuild) | [Documentación](https://godoc.org/github.com/stellar/go-stellar-sdk/txnbuild): permite la construcción, firma y codificación de transacciones Stellar.
-- `Horizon Client` [SDK](https://github.com/stellar/go-stellar-sdk/tree/main/clients/horizonclient) | [Documentación](https://godoc.org/github.com/stellar/go-stellar-sdk/clients/horizonclient): proporciona un cliente web para interactuar con los puntos finales REST del servidor Horizon para recuperar información del ledger y enviar transacciones desarrolladas con `txnbuild`.
-- `RPC Client` [SDK](https://github.com/stellar/stellar-rpc/tree/main/client) | [Docs](https://pkg.go.dev/github.com/stellar/stellar-rpc/client): proporciona un envoltorio de sdk para invocar puntos finales RPC.
-- [Ingest SDK](../../data/indexers/build-your-own/ingest-sdk/README.mdx): adquirir y analizar datos de la red Stellar.
-
-## C# .NET
-
-[SDK de C# .NET](https://github.com/Beans-BV/dotnet-stellar-sdk) | [Docs](https://elucidsoft.github.io/dotnet-stellar-sdk/)
-
-**Este SDK es mantenido por desarrolladores dedicados de la comunidad.**
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/contract-sdks.mdx b/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/contract-sdks.mdx
deleted file mode 100644
index 1701a87a87..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/tools/sdks/contract-sdks.mdx
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Desarrollar contratos inteligentes que se desplegarán en la red Stellar
-sidebar_label: SDK de Contrato
-sidebar_position: 10
----
-
-# SDKs de Contrato
-
-Los SDK de Contrato se utilizan para crear contratos inteligentes que se despliegarán en la red Stellar.
-
-:::note
-
-Para los SDK de Cliente y XDR, visita esta [página](./client-sdks.mdx).
-
-:::
-
-Todos los SDK son open-source; presenta una incidencia o un pull request en el repositorio específico del SDK si tienes preguntas o sugerencias.
-
-Cada SDK tiene su propio código fuente y documentación. Aprende a utilizar un SDK específico consultando la documentación.
-
-## SDK de Soroban Rust
-
-[SDK de Rust](https://github.com/stellar/rs-soroban-sdk) | [Documentación](https://docs.rs/soroban-sdk)
-
-**El SDK de Rust es mantenido por SDF.**
-
-El crate `soroban-sdk` de Rust contiene el SDK de Soroban Rust para crear contratos inteligentes para Stellar.
-
-Reporta incidencias y comparte comentarios sobre el `soroban-sdk` [aquí](https://github.com/stellar/rs-soroban-sdk/issues/new/choose).
-
-**Agrega `soroban-sdk` como una dependencia** utilizando [crates.io](https://crates.io/crates/soroban-sdk) para encontrar la versión de la publicación más reciente del SDK.
-
-Agrega las siguientes secciones al `Cargo.toml` para importar el `soroban-sdk` y reemplaza `$VERSION` con la versión publicada.
-
-```toml
-[dependencies]
-soroban-sdk = $VERSION
-
-[dev_dependencies]
-soroban-sdk = { version = $VERSION, features = ["testutils"] }
-```
-
-## SDK de Solidity
-
-[Compilador Hyperledger Solang](https://github.com/hyperledger-solang/solang) | [Documentación](https://solang.readthedocs.io/en/v0.3.4/)
-
-**El compilador Solang es mantenido por la comunidad Hyperledger.**
-
-Solang es un compilador basado en llvm para Solidity que puede dirigirse a múltiples blockchains, incluyendo Stellar.
-
-Los ejemplos admitidos de Solidity se pueden encontrar dentro del [repositorio Solang](https://github.com/hyperledger-solang/solang/tree/main/examples/soroban).
-
-Puedes informar incidencias y añadir solicitudes de funciones al repositorio Solang [aquí](https://github.com/hyperledger-solang/solang/issues/new/choose).
-
-El compilador Solang también ofrece un IDE web que puedes usar para compilar, desplegar e interactuar con contratos Solidity en Soroban. Puedes acceder al IDE web [aquí](https://solang.io/).
-
-## SDK de AssemblyScript
-
-[SDK de AssemblyScript](https://github.com/Soneso/as-soroban-sdk)
-
-**El SDK de AssemblyScript es mantenido por desarrolladores dedicados de la comunidad.**
-
-El `as-soroban-sdk` es un SDK de código abierto que admite la escritura de programas para la plataforma de contratos inteligentes Soroban utilizando el lenguaje de programación AssemblyScript.
-
-El SDK AssemblyScript Soroban es mantenido por el desarrollador dedicado de la comunidad, Soneso. Informa incidencias y comparte tus comentarios [aquí](https://github.com/Soneso/as-soroban-sdk/issues/new).
-
-## Crates de contratos y extensiones de OpenZeppelin
-
-Los contratos de OpenZeppelin se publican en cuatro crates:
-
-- Stellar Macros: https://crates.io/crates/stellar-macros
-- Stellar Access Control: https://crates.io/crates/stellar-access
-- Stellar Contract Utilities: https://crates.io/crates/stellar-contract-utils
-- Stellar Tokens: https://crates.io/crates/stellar-tokens
-
-Consulta la página de [OpenZeppelin para Contratos Stellar](../openzeppelin-contracts.mdx#openzeppelin-stellar-contracts-and-utilities) para obtener información adicional.
-
-## Crate Rust Stellar Axelar Std Derive
-
-Axelar ha creado un crate Rust con macros útiles para el desarrollo de contratos inteligentes Stellar. Consulta el Crate Rust [`stellar_axelar_std_derive`](https://axelarnetwork.github.io/axelar-amplifier-stellar/stellar_axelar_std_derive/index.html) para macros de atributo y macros derive, y para información adicional.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/README.mdx
deleted file mode 100644
index 17afed97b2..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/README.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: "Validadores: Rol, Configuración e Importancia en la Seguridad de la Red y el Consenso"
-sidebar_label: Introducción a los validadores
-description: Aprende cómo los validadores admiten la seguridad de la red y el consenso. Comprende su rol, requisitos de configuración y cómo ayudan a mantener la integridad de la red Stellar.
-sidebar_position: 10
----
-
-# Introducción a los Validadores
-
-Stellar es una red de usuario a usuario compuesta por nodos, que son ordenadores que mantienen un [ledger](../learn/fundamentals/stellar-data-structures/ledgers.mdx) distribuido común, y que se comunican para validar y añadir [transacciones](../learn/fundamentals/transactions/operations-and-transactions.mdx) a él. Los nodos utilizan un programa llamado Stellar Core — una implementación del [Stellar Consensus Protocol](../learn/fundamentals/stellar-consensus-protocol.mdx) — para mantenerse sincronizados mientras trabajan para acordar la validez de los conjuntos de transacciones y aplicarlas al ledger. En general, los nodos alcanzan consenso, aplican un conjunto de transacciones y actualizan el ledger cada 3-5 segundos.
-
-Esta sección de la documentación explica cómo ejecutar un nodo validador, que participa en el consenso para validar transacciones y determinar la configuración de la red. Un nodo validador _no debe_ ser utilizado para el acceso a datos de la red y la presentación de transacciones. Hay dos variedades de nodos _no validadores_ que se pueden utilizar para esos propósitos, cada uno de los cuales tiene su propio proceso para la configuración, interacción, mantenimiento y monitoreo. Son:
-
-1. Los [**Nodos RPC de Stellar**](../data/apis/rpc/README.mdx) se pueden utilizar para simular y/o enviar transacciones, así como para exponer un servicio RPC para consultar y recuperar el estado actual de la red. Esta es la mejor opción para casos de uso en tiempo real.
-2. [**Galexie Nodes**](../data/indexers/build-your-own/galexie/README.mdx) se pueden usar para recuperar y almacenar datos de la red en masa para un procesamiento posterior. Notablemente, _no_ admite el envío de transacciones, por lo que es más adecuado para indexadores o casos de uso analíticos.
-
-Si estás interesado en ejecutar un nodo validador — porque emites un activo que te gustaría ayudar a asegurar mediante la validación de transacciones, porque quieres ayudar a aumentar la salud de la red y la descentralización, o porque deseas participar en la gobernanza de la red — entonces esta sección de la documentación es para ti. Explica los aspectos técnicos y operativos de instalar, configurar y mantener un nodo validador de Stellar Core, y debería ayudarte a averiguar la mejor manera de establecer tu integración con Stellar.
-
-## Proceso de configuración del nodo
-
-El flujo básico, el cual puedes navegar utilizando la "Guía del Administrador" a la izquierda, va (aproximadamente) así:
-
-### Configuración inicial
-
-1. Utiliza la información en esta página de _Introducción_ para determinar qué [tipo de nodo](#types-of-nodes) deseas ejecutar.
-2. El software [previo](./admin-guide/prerequisites.mdx) debe ser instalado (y configurado de acuerdo con tus necesidades).
-3. [Instalar](./admin-guide/installation.mdx) el software Stellar Core en tu instancia.
-4. [Configurar](./admin-guide/configuring.mdx) el software Stellar Core para satisfacer tus necesidades y entorno.
-5. [Preparar](./admin-guide/environment-preparation.mdx) tu instancia de nodo y entorno. Esto incluye el paso opcional de configurar tu nodo para [publicar archivos de historial](./admin-guide/publishing-history-archives.mdx) del ledger.
-6. [Iniciar tu nodo](./admin-guide/running-node.mdx) y unirte a la red.
-7. [Registro](./admin-guide/logging.mdx) y [monitoreo](./admin-guide/monitoring.mdx) deben ser configurados adecuadamente y utilizados para satisfacer tus necesidades.
-
-### Requerimientos continuos
-
-8. Es necesario realizar [mantenimiento](./admin-guide/maintenance.mdx) de vez en cuando para mantener tu nodo actualizado y participando en la red.
-9. Las [actualizaciones de la red](./admin-guide/network-upgrades.mdx) requieren consenso de los validadores, y necesitarás considerar emitir un voto en caso de una actualización de protocolo.
-10. Los [ajustes de Soroban](./admin-guide/soroban-settings.mdx) son a nivel de red, configurables, y cualquier persona puede proponer cambios. Al igual que las actualizaciones de protocolo, los cambios a estos ajustes requerirán consenso de los validadores, así que deberías estar preparado para participar.
-
-### Otra información
-
-- Stellar Core utiliza una robusta herramienta de [línea de comandos](./admin-guide/commands.mdx) para controlar y operar un nodo. Hemos recopilado información sobre algunos de los comandos más utilizados, y enlazado a documentación CLI más completa.
-- Hemos recogido información diversa y útil sobre [temas avanzados](./admin-guide/advanced.mdx) que podrían ser útiles mientras comprendes e implementas tu nodo central.
-
-## Tipos de nodos validadores {#types-of-nodes}
-
-Hay dos tipos de nodos validadores, y realizan las mismas funciones básicas: ejecutan Stellar Core, se conectan a usuarios, presentan transacciones y almacenan el estado del ledger. La diferencia es esta: un **Validador Básico** no publica un archivo de historial; un **Validador Completo** sí lo hace.
-
-:::info
-
-Los nodos no validadores, como Stellar RPC o Galexie, incluyen un "Captive" Core optimizado para atender sus necesidades operativas.
-
-:::
-
-### Validador básico
-
-#### Validador, sin archivo público
-
-Un validador básico realiza un seguimiento del ledger y envía transacciones para una posible inclusión, pero _no_ está configurado para publicar archivos de historial. Requiere una clave secreta y está [configurado para participar en el consenso](./admin-guide/configuring.mdx#validating-node) votando y firmando cambios en el ledger, lo que significa que admite la red y aumenta la descentralización.
-
-La ventaja: las firmas pueden servir como respaldos oficiales de ledgers específicos en tiempo real. Eso es importante si, por ejemplo, emites un activo en Stellar que representa un activo del mundo real: puedes informar a tus clientes que solo honrarás transacciones y redimirás activos de ledgers firmados por tu validador, y en el improbable caso de que algo le suceda a la red, puedes usar tu nodo como el árbitro final de la verdad. Configurar tu nodo como validador te permite resolver cualquier pregunta _por adelantado y por escrito_ sobre cómo planeas manejar desastres y disputas.
-
-### Validador completo
-
-#### Validador, ofrece archivo público
-
-Un validador completo es igual que un validador básico, pero además publica un [Archivo de Historial](./admin-guide/environment-preparation.mdx) que contiene imágenes del ledger, incluyendo todas las transacciones y sus resultados. Un validador completo escribe en un almacenamiento de objetos accesible por internet, como AWS o Azure, por lo que es un poco más costoso y complejo de ejecutar, pero también hace más para respaldar la resiliencia y descentralización de la red.
-
-Cuando otros nodos se unen a la red o experimentan dificultades y temporalmente se desincronizan, pueden consultar los archivos ofrecidos por validadores completos para ponerse al día con el historial de la red. Los archivos redundantes previenen un único punto de falla y permiten a los participantes de la red verificar la veracidad de un historial dado.
-
-Generalmente, las organizaciones que operan validadores completos también forman parte o están en camino de unirse a [Tier 1](./tier-1-orgs.mdx), que es un grupo central de participantes de la red que ejecutan tres validadores completos para aportar la máxima redundancia.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/README.mdx
deleted file mode 100644
index 6d999bedbb..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/README.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: Guía del Administrador
-sidebar_position: 20
----
-
-import DocCardList from "@theme/DocCardList";
-
-Stellar Core es el programa que los nodos usan para comunicarse con otros nodos para crear y mantener la red peer-to-peer Stellar. Es una implementación del Stellar Consensus Protocol configurada para construir una cadena de ledgers garantizada para estar en acuerdo entre todos los nodos participantes en todo momento.
-
-Estas páginas describen varios aspectos de la instalación, configuración y mantenimiento de un nodo `stellar-core`.
-
-<DocCardList />
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/_category_.json b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/_category_.json
deleted file mode 100644
index 3dcd42977f..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/_category_.json
+++ /dev/null
@@ -1,3 +0,0 @@
-{
-    "collapsed": false
-}
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/advanced.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/advanced.mdx
deleted file mode 100644
index a7a1478439..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/advanced.mdx
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Avanzado
-sidebar_position: 130
----
-
-Esta página contiene información que es útil saber pero que no debería detener a alguien de ejecutar un nodo.
-
-## Crear Tu Propia Red Privada
-
-El [repositorio de GitHub de stellar-core] contiene [un archivo `testnet.md`] que incluye un breve tutorial que demuestra cómo configurar y ejecutar una red de prueba aislada y de corta duración.
-
-## Información de Ejecución: Inicio y Parada
-
-Stellar-core se puede iniciar directamente desde la línea de comandos, o a través de un sistema de supervisión como `init`, `upstart` o `systemd`.
-
-Stellar-core se puede cerrar de manera limpia en cualquier momento entregando `SIGINT` o pulsando `CTRL-C`. Puede ser terminado de forma segura y forzada con `SIGTERM` o `SIGKILL`. Este último puede dejar un archivo de bloqueo obsoleto en el `BUCKET_DIR_PATH`, y puede que necesites eliminar este archivo antes de que stellar-core se reinicie. En términos generales, todos los componentes están diseñados para recuperarse de un cierre abrupto. En términos generales, todos los componentes están diseñados para recuperarse de una terminación abrupta.
-
-Stellar-core también puede ser empaquetado en un sistema de contenedores como Docker, siempre que el `BUCKET_DIR_PATH` y la base de datos se almacenen en volúmenes persistentes. Para un ejemplo, ver [`stellar/quickstart`]. Para un ejemplo, ver [`stellar/quickstart`].
-
-## Arquitectura Detallada
-
-El [repositorio de GitHub de stellar-core] también contiene [el archivo `architecture.md`], que describe cómo stellar-core está estructurado internamente, cómo se pretende que sea implementado y la colección de servidores y servicios necesarios para obtener la funcionalidad y rendimiento completo.
-
-## Pruebas de Rendimiento Reproducibles Con Stellar Supercluster
-
-[Stellar Supercluster] es una herramienta que permite ejecutar redes simuladas de nodos stellar-core en clústeres de Kubernetes. Un caso de uso para Supercluster es ejecutar pruebas de rendimiento reproducibles. El repositorio de GitHub de Supercluster contiene varias documentos para ayudar a los usuarios a ejecutar pruebas teóricas máximas de Transacciones Por Segundo (TPS):
-
-- [`doc/getting-started.md`] detalla las dependencias para crear y ejecutar Supercluster.
-- [`doc/eks.md`] detalla cómo construir un clúster de EKS compatible con Supercluster en AWS.
-- [`doc/theoretical-max-tps.md`] explica cómo ejecutar la prueba teórica de TPS máxima en un clúster de EKS. También contiene una tabla de resultados de las propias pruebas teóricas máximas de TPS de SDF, así como las configuraciones utilizadas para lograr esos resultados.
-
-### Otros Recursos de Supercluster
-
-Supercluster es útil más allá de las pruebas de rendimiento reproducibles. Algunos recursos útiles para aprender más sobre Supercluster incluyen:
-
-- [`doc/measuring-transaction-throughput.md`] detalla pruebas adicionales de TPS máximas más allá de la prueba teórica máxima de TPS.
-- [`doc/missions.md`] lista todas las pruebas (denominadas "misiones") que Supercluster admite.
-
-[repositorio de github de stellar-core]: https://github.com/stellar/stellar-core
-[un archivo `testnet.md`]: https://github.com/stellar/stellar-core/blob/master/docs/software/testnet.md
-[`stellar/quickstart`]: https://github.com/stellar/quickstart
-[el archivo `architecture.md`]: https://github.com/stellar/stellar-core/blob/master/docs/architecture.md
-[Stellar Supercluster]: https://github.com/stellar/supercluster/tree/main
-[`doc/getting-started.md`]: https://github.com/stellar/supercluster/blob/main/doc/getting-started.md
-[`doc/eks.md`]: https://github.com/stellar/supercluster/blob/main/doc/eks.md
-[`doc/theoretical-max-tps.md`]: https://github.com/stellar/supercluster/blob/main/doc/theoretical-max-tps.md
-[`doc/measuring-transaction-throughput.md`]: https://github.com/stellar/supercluster/blob/main/doc/measuring-transaction-throughput.md
-[`doc/missions.md`]: https://github.com/stellar/supercluster/blob/main/doc/missions.md
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/commands.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/commands.mdx
deleted file mode 100644
index a934fac377..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/commands.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Comandos
-sidebar_position: 120
----
-
-Stellar Core se puede controlar usando un CLI robusto.
-
-:::info
-
-Aquí cubriremos una selección de los comandos y la sintaxis _esenciales_, pero el **mejor recurso** para utilizar la línea de comandos `stellar-core` se encuentra en el [repositorio de GitHub de stellar-core].
-
-Adicionalmente, aunque los comandos en esta página son comandos _CLI_, hay un conjunto adicional de [_comandos de punto final _HTTP_] que proporcionan un mayor control administrativo sobre un nodo central en ejecución.
-
-:::
-
-## Obtener `--help` en Cualquier Lugar
-
-La opción `--help` (aliases: `-h` o `-?`) se puede especificar en _cualquier lugar_ de la línea de comandos. Te mostrará el mensaje de ayuda para el comando relevante. Algunos ejemplos de uso son los siguientes:
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg --help
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg run --help
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg --help new-db
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg catchup --help
-```
-
-## Comandos Esenciales
-
-Para todos los comandos de stellar-core, las opciones pueden _solo_ colocarse después del comando.
-
-### `new-db`
-
-El **comando `new-db`** crea o restaura la base de datos local al ledger génesis.
-
-#### `new-db` Opciones
-
-- `--minimal-for-in-memory-mode`: Restablece la base de datos especial utilizada solo para el modo en memoria. (ver el `--in-memory` flag en [`opciones de ejecución`](#run-options))
-
-### `run`
-
-El **comando `run`** ejecutará el nodo `stellar-core`.
-
-#### `run` Opciones
-
-- `--disable-bucket-gc`: Mantiene todos, incluso los viejos, buckets en disco.
-- `--metadata-output-stream <STREAM>`: Nombre de archivo o número de descriptor de archivo `fd:N` para transmitir metadatos.
-- `--wait-for-consensus`: Espera a escuchar de la red antes de votar, solo para nodos de validación.
-
-Ciertas características, como las opciones de modo `in-memory`, han sido desaprobadas, por lo que no se enumeran aquí.
-
-### `catchup`
-
-El **comando `catchup`** ejecutará un catchup desde archivos de historia sin conectarse a la red.
-
-#### `catchup` Opciones
-
-- `<DESTINATION_LEDGER/LEDGER_COUNT>`: (requerido) El ledger de destino es cualquier número válido o `current` y el conteo de ledger es cualquier número válido o `max`.
-- `--archive <ARCHIVE-NAME>`: Nombre del archivo a utilizar para catchup. Usa `any` para seleccionar aleatoriamente.
-- `--trusted-checkpoint-hashes <FILE-NAME>`: Obtener el hash del ledger de destino de la salida confiable de `verify-checkpoints`.
-- `--output-file <FILE-NAME>`: Archivo de salida.
-- `--disable-bucket-gc`: Mantiene todos, incluso los viejos, buckets en disco.
-- `--extra-verification`: Verifica todos los archivos del archivo para el rango de catchup.
-- `--trusted-hash <HASH>`: Hash del ledger al que hacer catchup.
-- `--force-untrusted-catchup`: Forzar catchup no verificado.
-- `--metadata-output-stream <STREAM>`: Nombre de archivo o número de descriptor de archivo `fd:N` para transmitir metadatos.
-- `--force-back`: Fuerza el estado del ledger a un estado anterior, preservando datos históricos más antiguos.
-
-:::info
-
-Para reiterar, esta página cubre una selección de los comandos _esenciales_, pero solo hemos rozado la superficie. El **mejor, más completo recurso** para utilizar la línea de comandos `stellar-core` se encuentra en el [repositorio de GitHub de stellar-core].
-
-:::
-
-[repositorio de GitHub de stellar-core]: https://github.com/stellar/stellar-core/blob/master/docs/software/commands.md
-[comandos de punto final _HTTP_]: https://github.com/stellar/stellar-core/blob/master/docs/software/commands.md#http-commands
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
deleted file mode 100644
index 254e273b4e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx
+++ /dev/null
@@ -1,295 +0,0 @@
----
-title: Configurando
-sidebar_position: 40
----
-
-:::info
-
-Antes de intentar configurar stellar-core, se recomienda encarecidamente intentar ejecutar primero una red privada o unirse a la red de prueba.
-
-:::
-
-## Conceptos Básicos de Configuración
-
-Después de que hayas [instalado](./installation.mdx) Stellar Core, tu próximo paso es completar un archivo de configuración que especifique cosas cruciales sobre tu nodo, como si se conecta a la red pública de Testnet o a la Mainnet, a qué base de datos escribe, y qué otros nodos están en su [conjunto de quórum](#choosing-your-quorum-set).
-
-Toda la configuración de stellar-core se realiza con un archivo [TOML](https://github.com/toml-lang/toml). Por defecto, Stellar Core carga ese archivo desde `./stellar-core.cfg` y los paquetes de Debian utilizarán el archivo `/etc/stellar/stellar-core.cfg`. Puedes especificar un archivo diferente para cargar en la línea de comandos:
-
-```bash
-stellar-core --conf betterfile.cfg <COMMAND>
-```
-
-Al instalar usando paquetes oficiales de Debian, el archivo de unidad systemd está configurado para usar el archivo `/etc/stellar/stellar-core.cfg`. Los ejemplos en esta documentación no especifican `--conf betterfile.cfg` por razones de brevedad.
-
-Esta página te guiará a través de los campos clave que necesitarás incluir en tu archivo de configuración para poner tu nodo en funcionamiento.
-
-:::info
-
-Esta página intenta (tan estrictamente como sea posible) enfocarse en los campos y valores específicos que puedes necesitar modificar en tu archivo de configuración de Stellar Core. Para mantener esta página concisa, intentamos evitar el contexto conceptual y la información de fondo. Probablemente encontrarás parte de esa información relacionada en las páginas de [prerrequisitos](./prerequisites.mdx) o [preparación del entorno](./environment-preparation.mdx), si quieres.
-
-:::
-
-### Ejemplos de Configuración
-
-Mientras revisamos algunos de los conceptos básicos de configuración en esta página, hemos escrito este contenido para que funcione mejor junto con ejemplos de configuración concretos, así que, mientras lo lees, es posible que quieras revisar lo siguiente:
-
-- El [ejemplo completo de configuración] no es una configuración real, sino que documenta a fondo todos los elementos de configuración posibles, así como sus valores predeterminados. Tiene todos los controles que puedes ajustar y todas las configuraciones que puedes modificar junto con explicaciones detalladas sobre cómo ajustarlos y configurarlos. No necesitas poner todo desde el ejemplo completo de configuración en tu archivo de configuración. Los campos que omitas asumirán la configuración predeterminada, y la configuración predeterminada generalmente te servirá bien. Sin embargo, hay algunos campos requeridos, y esta página explicará cuáles son.
-
-- Si quieres conectarte a la red de Testnet, consulta el [ejemplo de configuración de Testnet]. Como puedes ver, la mayoría de los campos del [ejemplo completo de configuración] se han omitido ya que la configuración predeterminada funciona bien. Puedes adaptar fácilmente esta configuración para satisfacer tus necesidades de Testnet.
-
-- Si deseas conectarte a la red de Mainnet, consulta este [ejemplo de configuración de Mainnet] para un validador completo. Incluye un conjunto de quórum adecuadamente configurado con todos los actuales [validador Tier 1](../tier-1-orgs.mdx), que es un buen lugar para comenzar para la mayoría de las configuraciones. Este nodo está configurado para [validar](#validating-node) y escribir el historial en un [archivo público](./environment-preparation.mdx#configuring-to-publish-data-to-an-archive), pero puedes deshabilitar cualquiera de estas características ajustando esta configuración para que sea un poco más ligera.
-
-La auditoría de la red P2P está habilitada por defecto, consulta la sección de [topología de superposición](./monitoring.mdx#overlay-topology-survey) para más detalles si deseas desactivarla.
-
-### Frase de Contraseña de Red
-
-Usa el campo `NETWORK_PASSPHRASE` para especificar si tu nodo se conecta a la [red](../../networks/README.mdx) Testnet o Mainnet.
-
-- `NETWORK_PASSPHRASE="Test SDF Network ; Septiembre 2015"`
-- `NETWORK_PASSPHRASE="Public Global Stellar Network ; Septiembre 2015"`
-
-Para más información sobre el Network Passphrase y cómo funciona, consulta la [sección de redes](../../networks/README.mdx#network-passphrases).
-
-### Base de Datos
-
-Especificas la base de datos de tu nodo utilizando el campo llamado adecuadamente `DATABASE` de tu archivo de configuración, sobre el cual puedes leer más en el [ejemplo completo de configuración][complete-example-database]. Por defecto, utiliza una base de datos en memoria, pero puedes especificar una ruta según el ejemplo.
-
-### Buckets
-
-Los archivos XDR planos de Stellar Core se colocan en un directorio especificado en el archivo de configuración como `BUCKET_DIR_PATH`, que por defecto es `buckets`.
-
-## Nodo Validador
-
-:::note
-
-:::noteSi no tienes la intención de que tu nodo participe en las votaciones de consenso, puedes avanzar directamente a la configuración de tu [conjunto de quórum](#choosing-your-quorum-set):::
-
-:::
-
-Si deseas validar, debes generar una clave pública/privada para tu nodo. Los nodos no deben compartir claves. Debes asegurarte de _asegurar tu clave privada_. Si se ve comprometida, alguien puede enviar mensajes falsos a la red y esos mensajes parecerán provenir de ti.
-
-Genera un par de claves para tu nodo validador así:
-
-```bash
-stellar-core gen-seed
-```
-
-Tu salida debería verse algo así:
-
-```text
-Secret seed: SBAAOHEU4WSWX6GBZ3VOXEGQGWRBJ72ZN3B3MFAJZWXRYGDIWHQO37SY
-Public: GDMTUTQRCP6L3JQKX3OOKYIGZC6LG2O6K2BSUCI6WNGLL4XXCIB3OK2P
-```
-
-Agrega esta semilla secreta a tu archivo de configuración y marca el nodo como "validador":
-
-```toml
-NODE_SEED="SBAAOHEU4WSWX6GBZ3VOXEGQGWRBJ72ZN3B3MFAJZWXRYGDIWHQO37SY mynode"
-NODE_IS_VALIDATOR=true
-
-NODE_HOME_DOMAIN=<your domain name here - i.e., stellar.org>
-
-[[HOME_DOMAINS]]
-HOME_DOMAIN=<your domain name here, same as NODE_HOME_DOMAIN>
-QUALITY="MEDIUM"
-```
-
-Si no incluyes un `NODE_SEED` o configuras `NODE_IS_VALIDATOR=true`, tu nodo seguirá observando SCP y viendo todos los datos en la red, pero no enviará mensajes de validación.
-
-Si ejecutas múltiples validadores, asegúrate de establecer un `HOME_DOMAIN` común para ellos configurando la propiedad `NODE_HOME_DOMAIN` al mismo valor. Esto asegurará que tus nodos se agrupan correctamente durante la [generación del conjunto de quórum](#home-domains-array). También necesitas incluir tus otros nodos en el [`ARRAY DE VALIDADORES`](#validators-array) de tu archivo de configuración.
-
-Si deseas que otros validadores agreguen tu nodo a sus conjuntos de quórum, también debes compartir tu clave pública (`GDMTUTQ...`) publicando un archivo `stellar.toml` en tu dominio de origen siguiendo las especificaciones establecidas por [SEP-20].
-
-## Elegir tu Conjunto de Quórum
-
-Para crear tu conjunto de quórum, Stellar Core se basa en dos matrices de tablas: `[[HOME_DOMAINS]]` y `[[VALIDATORS]]`. Consulta la [`MATRIZ HOME_DOMAINS`](https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L671) del ejemplo de configuración y la [`MATRIZ VALIDATORS`](https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L688) para verlas en acción.
-
-:::info
-
-Es beneficioso hacer una breve pausa aquí y explorar algo de información de fondo sobre los quórums de validadores y el consenso de la red. Si deseas, puedes avanzar y comenzar a crear tu [matriz de dominios de origen](#home-domains-array) ahora. ¡De lo contrario, sigue leyendo, amigo!
-
-:::
-
-No importa qué tipo de nodo ejecutes — Validador Básico o Completo — necesitas seleccionar un conjunto de quórum, que consiste en validadores (agrupados por organización) con los que tu nodo verifica si debe aplicar un conjunto de transacciones a un ledger. Si deseas saber más sobre cómo funcionan los conjuntos de quórum, consulta este artículo sobre [cómo Stellar aborda los quórums]. Si deseas ver cómo se ve un conjunto de quórum que consiste en todos los validados Tier 1 — una configuración probada y verdadera — consulta la [configuración de red pública para un Validador Completo].
-
-Un buen conjunto de quórum:
-
-- se alinea con las prioridades de tu organización,
-- tiene suficiente redundancia para manejar fallas arbitrarias de nodos y
-- mantiene una buena intersección de quórums.
-
-Dado que crear un buen conjunto de quórum es algo difícil de hacer, stellar core _genera automáticamente_ un conjunto de quórum para ti basado en la información estructurada que proporcionas en tu archivo de configuración. Tú eliges los validadores en los que quieres confiar; stellar core los configura en un conjunto de quórum óptimo.
-
-Para generar un conjunto de quórum, stellar core:
-
-- Agrupa validadores de la misma organización en un subquórum
-- Establece el umbral para cada uno de esos subquórums
-- Asigna pesos a esos subquórums según la calidad
-
-Si bien esto no te exonera de toda responsabilidad — aún necesitas elegir validadores de confianza y vigilar su funcionamiento para asegurarte de que son consistentes y confiables — facilita tu vida y reduce las posibilidades de error humano.
-
-### Descubrimiento de Validadores
-
-Cuando añades un nodo validador a tu conjunto de quórum, generalmente es porque confías en la _organización_ que ejecuta el nodo: confías en SDF, no en una clave pública de Stellar anónima.
-
-Para crear un enlace autovalidado entre un nodo y la organización que lo ejecuta, un validador declara un dominio de origen on-chain utilizando una operación [`set_options`](../../learn/fundamentals/transactions/list-of-operations.mdx#set-options) y publica información organizacional en un archivo `stellar.toml` alojado en ese dominio. Para descubrir cómo funciona eso, consulta [SEP-20].
-
-Como resultado de ese enlace, puedes buscar un nodo por su clave pública de Stellar y verificar el archivo `stellar.toml` para averiguar quién lo ejecuta. Es posible hacerlo manualmente, pero también puedes consultar la lista de nodos en [Stellarbeat.io](https://stellarbeat.io/nodes). Si decides confiar en una organización, puedes utilizar esa lista para recopilar la información necesaria para agregar sus nodos a tu configuración.
-
-Cuando miras esa lista, descubrirás que las organizaciones más confiables realmente ejecutan más de un validador, y agregar todos los nodos de una organización a tu conjunto de quórum crea la redundancia necesaria para mantener una falla arbitraria de nodos. Cuando una organización con un trío de nodos apaga uno para mantenimiento, por ejemplo, los dos nodos restantes votan en nombre de la organización, y la presencia en la red de la organización persiste.
-
-### Matriz de Dominios de Origen
-
-`[[HOME_DOMAINS]]` define un superconjunto de validadores: cuando agregas nodos alojados por la misma organización a tu configuración, comparten un dominio de origen, y la información en la tabla `[[HOME_DOMAINS]]`, específicamente la calificación de calidad, se aplicará automáticamente a cada uno de esos validadores.
-
-Para cada organización que desees agregar, crea una tabla separada `[[HOME_DOMAINS]]` y completa los siguientes campos requeridos:
-
-| Campo       | Requisitos | Descripción                                                                |
-| ----------- | ---------- | -------------------------------------------------------------------------- |
-| HOME_DOMAIN | cadena     | URL del dominio de origen vinculado a un grupo de validadores              |
-| CALIDAD     | cadena     | Calificación para los nodos de esta organización: `ALTA`, `MEDIA` o `BAJA` |
-
-Aquí hay un ejemplo de una matriz `[[HOME_DOMAINS]]`, que crea dos tablas `[[HOME_DOMAINS]]`:
-
-```toml
-[[HOME_DOMAINS]]
-HOME_DOMAIN="testnet.stellar.org"
-QUALITY="HIGH"
-
-[[HOME_DOMAINS]]
-HOME_DOMAIN="some-other-domain"
-QUALITY="LOW"
-```
-
-### Matriz de Validadores
-
-Para cada nodo que desees agregar a tu conjunto de quórum, completa una tabla `[[VALIDATORS]]` con los siguientes campos:
-
-| Campo         | Requisitos | Descripción                                                                                                       |
-| ------------- | ---------- | ----------------------------------------------------------------------------------------------------------------- |
-| NOMBRE        | cadena     | Un alias único para el nodo                                                                                       |
-| CALIDAD       | cadena     | Calificación para el nodo (requerida a menos que se especifique en `[[HOME_DOMAINS]]`): `ALTA`, `MEDIA` o `BAJA`. |
-| HOME_DOMAIN   | cadena     | URL del dominio de origen vinculado al validador                                                                  |
-| CLAVE_PÚBLICA | cadena     | Clave pública de Stellar asociada con el validador                                                                |
-| DIRECCIÓN     | cadena     | Peer:puerto asociado con el validador (opcional)                                                                  |
-| HISTORIA      | cadena     | comando GET del archivo asociado con el validador (opcional)                                                      |
-
-Si el `HOME_DOMAIN` del nodo se alinea con una organización definida en la matriz `[[HOME_DOMAINS]]`, la calificación de calidad especificada allí se aplicará al nodo. Si estás agregando un nodo individual que _no_ está cubierto en esa matriz, necesitarás especificar la `CALIDAD` aquí.
-
-Aquí hay un ejemplo, que crea tres tablas `[[VALIDATORS]]`:
-
-```toml
-[[VALIDATORS]]
-NAME="sdftest1"
-HOME_DOMAIN="testnet.stellar.org"
-PUBLIC_KEY="GDKXE2OZMJIPOSLNA6N6F2BVCI3O777I2OOC4BV7VOYUEHYX7RTRYA7Y"
-ADDRESS="core-testnet1.stellar.org"
-HISTORY="curl -sf http://history.stellar.org/prd/core-testnet/core_testnet_001/{0} -o {1}"
-
-[[VALIDATORS]]
-NAME="sdftest2"
-HOME_DOMAIN="testnet.stellar.org"
-PUBLIC_KEY="GCUCJTIYXSOXKBSNFGNFWW5MUQ54HKRPGJUTQFJ5RQXZXNOLNXYDHRAP"
-ADDRESS="core-testnet2.stellar.org"
-HISTORY="curl -sf http://history.stellar.org/prd/core-testnet/core_testnet_002/{0} -o {1}"
-
-[[VALIDATORS]]
-NAME="rando-node"
-QUALITY="LOW"
-HOME_DOMAIN="rando.com"
-PUBLIC_KEY="GC2V2EFSXN6SQTWVYA5EPJPBWWIMSD2XQNKUOHGEKB535AQE2I6IXV2Z"
-ADDRESS="core.rando.com"
-```
-
-:::info Nota Importante
-
-Tu conjunto de quórum se configura automáticamente basado en la información que proporcionas en las tablas `[[VALIDATORS]]` y/o `[[HOME_DOMAINS]]`. Eliminar un validador resultará en la generación de un nuevo conjunto de quórum y puede tener consecuencias inesperadas para ti y otros participantes de la red. Asegúrate de considerar cuidadosamente las implicaciones de eliminar un validador de tu configuración y sigue la guía para [coordinarte con otros validadores](../tier-1-orgs.mdx#coordinate-with-other-validators) antes de realizar cambios.
-
-:::
-
-### Calidad del Validador
-
-`CALIDAD` es un campo requerido para cada nodo que añadas a tu conjunto de quórum. Ya sea que la especifiques para un conjunto de nodos en una tabla `[[HOME_DOMAINS]]`, o para un solo nodo en una tabla `[[VALIDATORS]]`, significa lo mismo, y tienes las mismas tres opciones de calificación: `ALTA`, `MEDIA` o `BAJA`.
-
-#### Calidad ALTA
-
-Los validadores de calidad **ALTA** reciben el mayor peso en la configuración automática del conjunto de quórum. Antes de asignar una calificación de calidad alta a un nodo, asegúrate de que tenga baja latencia y buen tiempo de actividad, y que la organización que ejecuta el nodo sea confiable y de confianza.
-
-Un validador de alta calidad:
-
-- publica un archivo, y
-- pertenece a un conjunto de nodos que brinda redundancia.
-
-Elegir nodos redundantes es una buena práctica. El requisito de archivo se hace cumplir programáticamente.
-
-#### Calidad MEDIA
-
-Los validadores de calidad **MEDIA** están anidados por debajo de los validadores de calidad alta, y su peso combinado es equivalente a una _única entidad de alta calidad_. Si un nodo no publica un archivo, pero tú lo consideras confiable, o tienes un interés organizacional en incluirlo en tu conjunto de quórum, dale una calificación de calidad media.
-
-#### Calidad BAJA
-
-Los validadores de calidad **BAJA** están anidados por debajo de los validadores de calidad media, y su peso combinado es equivalente a una _única entidad de calidad media_. Si demuestran ser confiables a lo largo del tiempo, puedes actualizar su calificación a media para darles un papel más importante en la configuración de tu conjunto de quórum.
-
-### Generación Automática del Conjunto de Quórum
-
-:::info :::info Nota ImportanteEs ideal configurar al menos 4 entidades en tu quórum si vas a utilizar generación automática de conjuntos de quórum. La compensación aquí es sobre la tolerancia a fallos: un quórum con menos de 4 entidades tolerará **cero** fallas de nodos. Tómate este momento para asegurarte de que tu quórum configurado cumpla con la tolerancia a fallos requerida.:::
-
-Es ideal configurar al menos 4 entidades en tu quórum si vas a utilizar generación automática de conjuntos de quórum. El compromiso aquí es sobre la tolerancia a fallos: un quórum con menos de 4 entidades tolerará **cero** fallas de nodos. Tómate este momento para asegurarte de que tu quórum configurado cumpla con la tolerancia a fallos requerida.
-
-:::
-
-Una vez que agregues validadores a tu configuración, stellar core genera automáticamente un conjunto de quórum utilizando las siguientes reglas:
-
-- Los validadores con el mismo dominio de origen se agrupan automáticamente y se les da un umbral que requiere una simple mayoría (`2f+1`)
-- Los grupos heterogéneos de validadores tienen un umbral que asume fallo bizantino (`3f+1`)
-- El peso combinado de las entidades de calidad `BAJA` es equivalente a una sola entidad de calidad `MEDIA`
-- Las entidades se agrupan por `CALIDAD` y se anidan de `ALTA` a `BAJA`
-- _Diagrama: Representación de los niveles de calidad anidados y cómo interactúan._
-- Quórum y Red de Superposición
-
-![Diagrama de Generación Automática de Quorum Set](/assets/diagrams/validator_complete.png)
-
-_Diagrama: Representación de los niveles de calidad anidados y cómo interactúan._
-
-### Quorum y Red de Superposición
-
-Para sincronizarse y ejecutar el consenso, tu validador necesita poder conectarse a la Stellar Network. En la mayoría de los casos, es suficiente confiar en el descubrimiento de usuarios integrado en el nodo. Sin embargo, tu validador puede configurarse para conectarse a usuarios específicos a través de `KNOWN_PEERS` y `PREFERRED_PEERS` en el archivo de configuración. Estos pueden ser nombres de dominio o IPs. Esto puede ser útil para solucionar problemas.
-
-Además, configurar `PREFERRED_PEER_KEYS` con las claves de tu quorum set podría ser una buena idea para dar prioridad a los nodos que te permiten alcanzar consenso.
-
-Sin esa configuración, tu validador depende de otros nodos en la red para reenviar los mensajes correctos, lo cual se suele hacer como un esfuerzo adicional.
-
-### Impacto de la Calidad del Validador en la Nominación
-
-El Stellar Consensus Protocol utiliza niveles de calidad de validadores para determinar qué validador debe nominar el siguiente conjunto de transacciones para su inclusión en un ledger. Este proceso de elegir el validador que nominará el siguiente conjunto de transacciones se llama _elección de líder_. Para empezar, el algoritmo de elección de líder asigna a organizaciones y validadores pesos de la siguiente manera:
-
-- Sea $O_q$ el conjunto de todas las organizaciones con un nivel de calidad dado $q$. $O_q$ incluye todas las organizaciones explícitamente definidas en el archivo de configuración a nivel de calidad $q$, así como una sola organización virtual que contiene $O_r$ donde $r$ es el siguiente nivel de calidad por debajo de $q$.
-- Todas las organizaciones de algún nivel de calidad $q$ tienen peso $w_q$.
-- Si una organización de calidad $q$ tiene $n$ nodos, entonces el peso de cada nodo es $\frac{w_q}{n}$.
-- $w_\top$ es `1`, donde $\top$ es el valor de calidad más alto asignado a cualquier organización.
-- $w_\texttt{LOW} = 0$.
-  - Esto permite a un validador participar en algunas actividades SCP sin ser confiado para nominar conjuntos de transacciones.
-- Para todos los demás valores $q$, $w_q = \frac{w_p}{10 \times \left|\  O_p\ \right|}$ donde $p$ es el siguiente valor de calidad por encima de $q$.
-
-El algoritmo de elección de líder luego asigna a cada validador una probabilidad de ganar la elección de líder del peso del validador dividido por el peso total de todos los validadores. En conjunto, estas probabilidades de ganar aseguran que el algoritmo de elección de líder de Stellar Core tenga las siguientes propiedades:
-
-1. Las organizaciones de mayor calidad tienen una mayor oportunidad de ganar la elección de líder que las organizaciones de menor calidad.
-2. Las organizaciones de calidad igual tienen una igual posibilidad de ganar la elección de líder.
-
-#### Ejemplo de Peso de Nominación de Validador
-
-Supongamos que hay 3 organizaciones de calidad `HIGH`, 2 organizaciones de calidad `MEDIUM` y 1 organización de calidad `LOW`. El peso de cada organización es el siguiente:
-
-- Cada organización de calidad `HIGH` tiene un peso de `1`.
-- Cada organización de calidad `MEDIUM` tiene un peso de `1/(10 * 3)`, o `1/30`.
-- Cada organización de calidad `LOW` tiene un peso de `0`.
-
-[configuración de ejemplo completa]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg
-[configuración de ejemplo de testnet]: https://github.com/stellar/quickstart/blob/master/testnet/core/etc/stellar-core.cfg
-[configuración de ejemplo de mainnet]: https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg
-[base de datos de ejemplo completa]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L48
-[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
-[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-plugin-content-docs/current/validators/admin-guide/environment-preparation.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/environment-preparation.mdx
deleted file mode 100644
index 52be5c3478..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/environment-preparation.mdx
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: Preparación del Entorno
-sidebar_position: 50
----
-
-## Inicializar la Base de Datos y el Estado Local
-
-Después de configurar tu [base de datos](./configuring.mdx#database) y los ajustes de [cubos](./configuring.mdx#buckets), antes de ejecutar Stellar Core por primera vez, debes inicializar la base de datos:
-
-```bash
-stellar-core new-db
-```
-
-Este comando inicializará la base de datos, así como el directorio de cubos, y luego saldrá. También puedes usar este comando si tu base de datos se corrompe y deseas reiniciarla desde cero.
-
-### Mantenimiento Automático
-
-Algunas tablas en stellar-core se utilizan para publicar datos de ledger en archivos de historial.
-
-Si no se gestionan correctamente, esas tablas crecerán sin límites. Para evitar esto, un programador integrado eliminará datos de los ledgers antiguos que ya no son utilizados por otras partes del sistema.
-
-Por defecto, stellar-core realizará este mantenimiento automático. Los campos de configuración que controlan el comportamiento del mantenimiento automático son:
-
-- `AUTOMATIC_MAINTENANCE_PERIOD`,
-- `AUTOMATIC_MAINTENANCE_COUNT`
-
-Si necesitas regenerar los metadatos, la forma más sencilla es reproducir ledgers para el rango que te interese después de (opcionalmente) limpiar la base de datos con el comando `new-db` [referenciado anteriormente](#initialize-the-database-and-local-state).
-
-En algunos casos, el mantenimiento automático tiene demasiado trabajo que hacer para volver al estado nominal. Esto puede ocurrir tras grandes operaciones de actualización, como al realizar una actualización completa que puede crear un retraso de decenas de millones de ledgers.
-
-Si esto sucede, el rendimiento de la base de datos puede ser restaurado. El nodo requerirá un tiempo de inactividad mientras realizas los siguientes comandos de recuperación:
-
-1. ejecuta el comando http `maintenance` manualmente con un gran número de ledgers, y
-2. realiza una operación de mantenimiento de la base de datos como `VACUUM FULL` para recuperar/reconstruir la base de datos según sea necesario.
-
-### Instantáneas y Restauración de Metadatos
-
-Algunas implementaciones de Stellar Core querrán conservar los metadatos de _toda la historia_ de la red. Estos metadatos pueden ser bastante grandes y computacionalmente costosos de regenerar de nuevo al reproducir ledgers en stellar-core desde un estado inicial de base de datos vacío, como se describe en la sección anterior.
-
-Esto puede ser especialmente costoso si debe ejecutarse más de una vez. Por ejemplo, al poner en línea un nuevo nodo. O cuando se necesite reingestar datos históricos para incluir más metadatos en tus datos almacenados (como ocurrió en [Protocol 23](https://stellar.org/blog/developers/stellar-events-retroactive-events)).
-
-:::info
-
-Debido a los requisitos de tamaño muy grandes, **recomendamos no** conservar metadatos para toda la historia de la red a menos que sea absolutamente necesario para tu caso de uso.
-
-:::
-
-Por eso, algunos operadores prefieren cerrar sus procesos de stellar-core y _tomar imágenes a nivel de sistema de archivos_ o _volcados a nivel de base de datos_ del contenido de la base de datos y del directorio de buckets de Stellar Core, después de que se genere los metadatos por primera vez. Esas imágenes luego se pueden restaurar, poniendo a stellar-core en un estado que contiene metadatos sin realizar una reproducción completa.
-
-Cualquier estado razonablemente reciente servirá; si tal instantánea es un poco antigua, stellar-core reproducirá ledgers desde cuando se tomó la instantánea hasta el estado actual de la red de todos modos; pero este procedimiento puede acelerar enormemente la restauración de nodos validador, o clonarlos para crear nuevos.
-
-## Archivos de Historia
-
-Stellar Core normalmente interactúa con uno o más archivos de historia, que son instalaciones configurables donde los [Validadores Completos](../README.mdx#full-validator) almacenan archivos planos que contienen puntos de control de historia: archivos de cubo y registros de historia. Los archivos de historia suelen ser servicios de almacenamiento de mercancías fuera del sitio, como Amazon S3, Google Cloud Storage, Azure Blob Storage, o servidores SCP/SFTP/HTTP personalizados.
-
-Utiliza plantillas de comandos en el archivo de configuración para dar los detalles de qué servicios utilizarás y cómo acceder a ellos. El [ejemplo de configuración] demostrará cómo configurar un archivo de historia a través de plantillas de comandos.
-
-### Configurando para Obtener Datos de un Archivo
-
-No importa qué tipo de nodo estés ejecutando, deberías configurarlo para `get` historia de uno o más archivos públicos. Puedes configurar cualquier número de archivos para descargar: Stellar Core redirigirá automáticamente entre ellos.
-
-Cuando [elijas tu Quorum Set](./configuring.mdx#choosing-your-quorum-set), debes incluir nodos de alta calidad — que, por definición, publican archivos — y añadir la ubicación del archivo de cada nodo en el campo `HISTORY` dentro del [array de validadores](./configuring.mdx#validators-array).
-
-:::note
-
-Si notas muchos errores relacionados con la descarga de archivos, deberías asegurarte de que todos los archivos en tu configuración están actualizados. Puedes revisar la [configuración de ejemplo de Mainnet] para ver cómo podrías usar validadores de Tier 1 actualizados para sus archivos de historia.
-
-:::
-
-### Configurando para Publicar Datos en un Archivo
-
-Las secciones de archivos también pueden ser configuradas con comandos `put` y `mkdir` para hacer que la instancia publique en ese archivo (para nodos configurados como [validadores completos](../README.mdx#full-validator)).
-
-La primera vez que quieras usar tu archivo, _antes de arrancar tu nodo_, necesitas inicializarlo con:
-
-```bash
-stellar-core new-hist <historyarchive>
-```
-
-:::note
-
-En un entorno de producción seguro, Stellar Core debe ejecutarse como un usuario dedicado. Los paquetes de Debian garantizarán que el usuario `stellar` exista en el sistema. Por esta razón, puede que necesites ejecutar comandos como el usuario stellar, por ejemplo:
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg new-hist <historyarchive>
-```
-
-:::
-
-Una guía más detallada y estrategias para publicar archivos de historia se pueden encontrar en la página de [publicación de archivos de historia](./publishing-history-archives.mdx). Por favor, consulta allá para más información.
-
-:::info IMPORTANTE:
-
-- Asegúrate de configurar tanto `put` como `mkdir` si `put` no crea automáticamente subcarpetas.
-- Escribir en el mismo archivo desde diferentes nodos no está soportado y resultará en un comportamiento indefinido, _potencialmente pérdida de datos_.
-- No ejecutes `new-hist` en un archivo existente a menos que quieras borrarlo.
-
-:::
-
-## Otra Preparación
-
-Además, debes asegurarte de que tu entorno operativo también esté funcional. Esto significa que deberías haber considerado y preparado lo siguiente.
-
-- [Registro](./logging.mdx) y rotación de registros
-- [Monitoreo](./monitoring.mdx) e infraestructura de alertas
-
-[ejemplo de configuración]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg
-[ejemplo de configuración de Mainnet]: 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/validators/admin-guide/installation.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/installation.mdx
deleted file mode 100644
index e2451d882e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/installation.mdx
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: Instalando
-sidebar_position: 30
----
-
-Existen tres formas comunes de instalar y ejecutar Stellar Core:
-
-1. **Usando [paquetes](#package-based-installation) publicados.** Para uso en producción, recomendamos instalar Stellar Core usando paquetes publicados.
-
-2. **Creando desde [código fuente](#installing-from-source).** En algunas situaciones poco comunes, o si deseas sacrificar la conveniencia por el máximo control, puede ser necesario crear desde el código fuente.
-
-3. **Usa una [imagen de Docker](#docker-based-installation).** Usar una imagen de Docker es el método más rápido y fácil, así que es una buena opción para muchos desarrolladores.
-
-## Versión de Lanzamiento
-
-Cualquiera que sea el método que uses, debes asegurarte de instalar la última [versión](https://github.com/stellar/stellar-core/releases) ya que estas compilaciones son compatibles con versiones anteriores y son acumulativas.
-
-El esquema del número de versión que seguimos es `protocol_version.release_number.patch_number`, donde:
-
-- `protocol_version` es la versión máxima del protocolo admitida por ese lanzamiento (todas las versiones son 100% compatibles con versiones anteriores),
-- `release_number` se incrementa cuando se incluye un conjunto de nuevas características o correcciones de errores que no afectan al protocolo en el lanzamiento, y
-- `patch_number` se usa cuando se debe implementar una corrección crítica.
-
-## Instalación Basada en Paquetes
-
-Si estás usando una versión LTS reciente de Ubuntu, proporcionamos [`stellar-core`](https://github.com/stellar/stellar-core) y [`stellar-rpc`](https://github.com/stellar/stellar-rpc) en formato de paquete binario Debian. Los paquetes están firmados criptográficamente por la Stellar Development Foundation y los archivos se pueden validar en el sistema para confirmar que no han sido manipulados. Los paquetes de Debian utilizan la verificación criptográfica incorporada del sistema operativo durante las actualizaciones, lo que mitiga muchos ataques a la cadena de suministro.
-
-La huella digital de la clave de firma del paquete SDF es **AEAF 01EE A6CA FCEF DDAE 8AA7 0463 8272 A136 B5A6** (A136B5A6)
-
-Actualmente no publicamos paquetes para distribuciones de Linux basadas en RPM. Si utilizas dicha distribución, recomendamos usar [imágenes de docker](#docker-based-installation)
-
-### Configurar el repositorio Apt de SDF en el sistema
-
-```bash
-sudo install -d /etc/apt/keyrings
-sudo curl -fsSL https://apt.stellar.org/SDF.asc -o /etc/apt/keyrings/SDF.asc
-sudo chmod a+r /etc/apt/keyrings/SDF.asc
-echo "deb [signed-by=/etc/apt/keyrings/SDF.asc] https://apt.stellar.org $(lsb_release -cs) stable" | sudo tee -a /etc/apt/sources.list.d/SDF.list
-```
-
-Opcionalmente, puedes añadir un repositorio de pruebas. Esto no se recomienda para sistemas de producción, pero puede ser útil para sistemas no productivos que utilizan testnet:
-
-```bash
-echo "deb [signed-by=/etc/apt/keyrings/SDF.asc] https://apt.stellar.org $(lsb_release -cs) stable" | sudo tee -a /etc/apt/sources.list.d/SDF.list
-```
-
-### Instalar paquetes
-
-Publicamos varios paquetes por conveniencia.
-
-| Paquete                          | Dependencias             | Comentarios                                                                                                                                                                                            |
-| -------------------------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| stellar-core                     | ninguna                  | instala el binario stellar-core, servicio systemd, script logrotate, documentación                                                                                                                     |
-| stellar-core-utils               | ninguna                  | instala herramientas útiles de línea de comandos (stellar-core-cmd, stellar-core-gap-detect)                                                                                                           |
-| stellar-core-prometheus-exporter | ninguna                  | instala un exportador de Prometheus para facilitar la ingesta de métricas de stellar-core                                                                                                              |
-| stellar-core-postgres            | stellar-core, PostgreSQL | configura un servidor PostgreSQL, crea una base de datos stellar, un rol y un usuario del sistema, la configuración predeterminada de stellar-core contenida en este paquete se conectará a la Testnet |
-| stellar-archivist                | ninguna                  | instala la herramienta cli stellar-archivist para gestionar los archivos de historial de stellar-core                                                                                                  |
-
-Para instalar un paquete elegido, ejecuta:
-
-```bash
-# To install stellar-core
-sudo apt-get update && apt-get install <package_name>
-```
-
-## Instalando desde el Código Fuente
-
-El repositorio del código fuente de Stellar Core contiene instrucciones extensas y completas para crear el software desde el código fuente. Por favor, [consulta `INSTALL.md`](https://github.com/stellar/stellar-core/blob/master/INSTALL.md) para más información.
-
-## Instalación Basada en Docker
-
-### Entornos de Desarrollo
-
-SDF mantiene una [imagen de inicio rápido](https://github.com/stellar/quickstart) que ejecuta un validador de Stellar Core, un "Captive Core" incluido con Stellar RPC, y todos los demás componentes necesarios para admitir el desarrollo local. Es una forma rápida de configurar una configuración predeterminada, no validante, efímera que debería funcionar para la mayoría de los desarrolladores. Además, la imagen de inicio rápido puede ser iniciada preconfigurada para su uso como nodo de Mainnet, Testnet, Futurenet o red Local.
-
-:::info
-
-La imagen de inicio rápido no está destinada a servir como un nodo de instancia de nivel producción. Please plan your production instance(s) carefully.
-
-:::
-
-### Entornos de Producción
-
-SDF también mantiene una imagen independiente solo de Stellar-Core, [`stellar/stellar-core`](https://hub.docker.com/r/stellar/stellar-core).
-
-Uso de Ejemplo:
-
-```bash
-docker run stellar/stellar-core:latest help
-docker run stellar/stellar-core:latest gen-seed
-```
-
-Para ejecutar el demonio de Stellar Core, necesitas proporcionar un archivo de configuración:
-
-```bash
-# Initialize postgres DB (see DATABASE config option)
-docker run -v "/path/to/config/dir:/etc/stellar/" stellar/stellar-core:latest new-db
-# Run stellar-core daemon in the background
-docker run -d -v "/path/to/config/dir:/etc/stellar/" stellar/stellar-core:latest run
-```
-
-La imagen utiliza paquetes deb, por lo que es posible confirmar que el checksum del binario `stellar-core` en la imagen de docker coincide con lo que hay en el paquete deb firmado criptográficamente. Consulta la [sección de instalación basada en paquetes](#package-based-installation) para más información. Para calcular este checksum en la imagen de docker, puedes ejecutar:
-
-```bash
-docker run --entrypoint=/bin/sha256sum stellar/stellar-core:latest /usr/bin/stellar-core
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/logging.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/logging.mdx
deleted file mode 100644
index 1896354aaa..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/logging.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Registro
-sidebar_position: 70
----
-
-Stellar Core envía registros a error estándar y `stellar-core.log` por defecto, configurable con el campo `LOG_FILE_PATH`.
-
-Los mensajes de registro se clasifican por niveles de _prioridad_ progresivos: `TRACE`, `DEBUG`, `INFO`, `WARNING`, `ERROR` y `FATAL`. El sistema de registro solo emite esos mensajes en o por encima de su nivel de registro configurado. El sistema de registro solo emite aquellos mensajes en su nivel de registro configurado o superior.
-
-Los mensajes de registro en diferentes niveles de prioridad se pueden codificar por color en el error estándar configurando `LOG_COLOR=true` en el archivo de configuración. Por defecto, no están codificados por colores.
-
-El nivel de registro puede ser controlado por configuración, el flag de línea de comandos `--ll`, o ajustado dinámicamente mediante comandos administrativos (HTTP). Para hacerlo, ejecuta: Para hacerlo, ejecuta:
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command "ll?level=debug"
-```
-
-mientras tu nodo esté en ejecución.
-
-Los niveles de registro también se pueden ajustar en base a cada partición a través de la interfaz administrativa. Por ejemplo, el sistema de historial puede ser configurado para registro de nivel `DEBUG` ejecutando:
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command "ll?level=debug&partition=history"
-```
-
-Contra un sistema en funcionamiento.
-
-:::info
-
-Por favor, revisa el [referencia de Comandos HTTP] para más información sobre las particiones disponibles para usar en el comando `ll`.
-
-:::
-
-El nivel de registro por defecto es `INFO`, que es moderadamente detallado y debería emitir mensajes de progreso cada pocos segundos durante el funcionamiento normal.
-
-[Referencia de Comandos HTTP]: https://github.com/stellar/stellar-core/blob/master/docs/software/commands.md#http-commands
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/maintenance.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/maintenance.mdx
deleted file mode 100644
index 393f751ad5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/maintenance.mdx
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Mantenimiento
-sidebar_position: 90
----
-
-Mantenimiento aquí se refiere a cualquier cosa que implique sacar temporalmente tu validador de la red (para aplicar parches de seguridad, actualizar el sistema, etc.).
-
-Como administrador de un validador, debes asegurarte de que el mantenimiento que vas a aplicar al validador sea seguro para la red en general y para tu validador.
-
-Seguro significa que los otros validadores que dependen del tuyo no se verán demasiado afectados cuando apagues tu validador para mantenimiento y que tu validador seguirá operando como parte de la red cuando vuelva a estar en línea.
-
-Si estás cambiando algunas configuraciones que pueden impactar configuraciones a nivel de red como la versión del protocolo, revisa [la página de actualizaciones de la red](./network-upgrades.mdx).
-
-Si estás cambiando la configuración de tu conjunto de quorum, también lee [la sección sobre qué hacer](#special-considerations-during-quorum-set-updates).
-
-## Pasos recomendados para realizar como parte de un mantenimiento
-
-Recomendamos realizar los siguientes pasos en orden (repetir secuencialmente según sea necesario si ejecutas múltiples nodos).
-
-1. Anuncia tu intención a otros que puedan depender de ti. Se requiere algo de coordinación para evitar situaciones donde demasiados nodos se apaguen al mismo tiempo.
-2. Las dependencias deben evaluar la salud de su quorum
-3. Si no hay objeciones, apaga tu instancia
-4. Cuando termines, inicia tu instancia que debería reincorporarse a la red
-5. La instancia estará completamente sincronizada cuando esté tanto `Sincronizada` como _no haya retrasos en la subida de historial_.
-
-## Consideraciones especiales durante las actualizaciones de conjunto de quorum
-
-Cuando te unas a las filas de los operadores de nodos, también es importante unirse a la conversación. La mejor manera de hacerlo: sigue el canal `#validators` en el [Discord de Desarrolladores de Stellar](https://discord.gg/stellardev). Si no puedes hacer esto por alguna razón, inscríbete en el [Grupo de Google de Validadores de Stellar](https://groups.google.com/forum/#!forum/stellar-validators).
-
-A veces, una organización necesita hacer cambios que impactarán los conjuntos de quorum de otros:
-
-- sacar un validador por un largo período de tiempo
-- agregar nuevos validadores a su grupo
-
-En ambos casos, es crucial organizar los cambios para preservar la intersección de quorum y la buena salud general de la red:
-
-- Ten cuidado al eliminar demasiados nodos de tu conjunto de quorum _antes_ de que los nodos sean apagados. Si diferentes personas eliminan diferentes conjuntos, los conjuntos restantes pueden no superponerse entre nodos y pueden causar divisiones en la red.
-- Ten cuidado al agregar demasiados nodos a tu conjunto de quorum al mismo tiempo. Si no se hace con cuidado, esto puede hacer que esos nodos superen tu configuración.
-
-Los pasos recomendados son que la entidad que agrega/elimina nodos lo haga primero entre sus propios nodos, y luego haga que las personas reflejen esos cambios gradualmente (a lo largo de varias rondas) en sus respectivas configuraciones de quorum.
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/monitoring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/monitoring.mdx
deleted file mode 100644
index ee74aad1fe..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/monitoring.mdx
+++ /dev/null
@@ -1,669 +0,0 @@
----
-title: Monitoreo
-sidebar_position: 80
----
-
-Una vez que tu nodo esté en funcionamiento, es importante mantener un ojo en él para asegurarte de que se mantenga a flote y siga contribuyendo a la salud de la red en general. Para ayudar con eso, Stellar Core expone información vital que puedes usar para monitorear tu nodo y diagnosticar problemas potenciales.
-
-Puedes acceder a esta información utilizando comandos e inspeccionando la salida de Stellar Core. La primera mitad de esta página cubrirá este enfoque. También puedes conectar [Prometheus](#using-prometheus) para facilitar el monitoreo, combinarlo con [Alertmanager](#configure-notifications-using-alertmanager) para automatizar la notificación, y usar [tableros preconstruidos de Grafana](#visualize-metrics-using-grafana) para crear representaciones visuales del bienestar de tu nodo.
-
-:::info
-
-[**Stellarbeat**](https://www.stellarbeat.io), un panel de monitoreo administrado por la comunidad, también puede ser útil para ver la salud de la red en su conjunto. Debes mantener un ojo muy atento en tu(s) nodo(s) usando algunas de las herramientas sugeridas en esta página, pero monitorear el rendimiento de todos los nodos de la red también puede ser útil para entender cómo interactúan todos entre sí.
-
-:::
-
-Sin importar cómo decidas monitorear, lo más importante es que tengas un sistema en marcha para asegurarte de que tu integración siga funcionando.
-
-## Información General del Nodo
-
-Si ejecutas `sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'info'`, la salida se verá algo así:
-
-```json
-{
-  "info": {
-    "build": "v20.4.0",
-    "ledger": {
-      "age": 0,
-      "baseFee": 100,
-      "baseReserve": 100000000,
-      "closeTime": 0,
-      "hash": "39c2a3cd4141b2853e70d84601faa44744660334b48f3228e0309342e3f4eb48",
-      "maxTxSetSize": 100,
-      "num": 1,
-      "version": 20
-    },
-    "network": "Public Global Stellar Network ; September 2015",
-    "peers": {
-      "authenticated_count": 8,
-      "pending_count": 2
-    },
-    "protocol_version": 20,
-    "quorum": {
-      "node": "GCRQF",
-      "qset": {
-        "agree": 22,
-        "cost": 37256128,
-        "delayed": 0,
-        "disagree": 0,
-        "fail_at": 6,
-        "hash": "5c464e",
-        "lag_ms": 1942,
-        "ledger": 51251628,
-        "missing": 1,
-        "phase": "EXTERNALIZE"
-      },
-      "transitive": {
-        "critical": null,
-        "intersection": true,
-        "last_check_ledger": 51251539,
-        "node_count": 24
-      }
-    },
-    "startedOn": "2024-04-15T16:16:25Z",
-    "state": "Synced!"
-  }
-}
-```
-
-Algunos campos destacados de este punto final `info` son:
-
-- `build`: el número de versión para esta instancia de Stellar Core
-- `ledger`: una representación del estado local de tu nodo, que puede ser diferente del estado de la red si tu nodo estuvo desconectado de la red, por ejemplo. Algunos subcampos importantes:
-  - `age`: tiempo transcurrido desde que este ledger se cerró (durante la operación normal menos de 10 segundos)
-  - `num`: número del ledger
-  - `version`: versión del protocolo de este ledger
-- `network` la [frase de paso de la red]([Networks section](../../networks/README.mdx#network-passphrases)) para la red que esta instancia de core está usando
-- `peers`: información sobre la conectividad a la red
-  - `authenticated_count`: el número de conexiones en vivo
-  - `pending_count`: el número de conexiones que aún no están completamente establecidas
-- `protocol_version`: la versión máxima del protocolo que esta instancia reconoce
-- `state`: el estado de sincronización del nodo con respecto a la red
-- `quorum`: resumen del estado de los participantes del protocolo SCP, que es la misma información devuelta por el comando `quorum` ([ver abajo](#quorum-health)).
-
-## Información del Usuario
-
-El comando `peers` devuelve información sobre los usuarios a los que tu nodo está conectado.
-
-Esta lista es el resultado de conexiones entrantes de otros usuarios y conexiones salientes de este nodo a otros usuarios. Si se usa `compact=false` en el comando, también devuelve algunas métricas extras sobre cada usuario, como el número de mensajes descartados.
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'peers'
-```
-
-La salida se verá algo así:
-
-```json
-{
-  "authenticated_peers": {
-    "inbound": [
-      {
-        "address": "18.234.41.75",
-        "elapsed": 6,
-        "flow_control": {
-          "local_capacity": {
-            "flood": 200,
-            "reading": 200
-          },
-          "local_capacity_bytes": {
-            "flood": 300000
-          },
-          "peer_capacity": 175,
-          "peer_capacity_bytes": 291340
-        },
-        "id": "SDF 1",
-        "latency": 172,
-        "olver": 32,
-        "ver": "stellar-core 20.4.0 (7fc7671b8bc1ccc3b1f16a6ab83bc9f671db8b70)"
-      }
-    ],
-    "outbound": [
-      {
-        "address": "3.238.239.100:11625",
-        "elapsed": 105,
-        "flow_control": {
-          "local_capacity": {
-            "flood": 200,
-            "reading": 200
-          },
-          "local_capacity_bytes": {
-            "flood": 300000
-          },
-          "peer_capacity": 175,
-          "peer_capacity_bytes": 291340
-        },
-        "id": "SDF 3",
-        "latency": 172,
-        "olver": 32,
-        "ver": "stellar-core 20.4.0 (7fc7671b8bc1ccc3b1f16a6ab83bc9f671db8b70)"
-      },
-      {
-        "address": "85.190.254.217:11625",
-        "elapsed": 295,
-        "flow_control": {
-          "local_capacity": {
-            "flood": 200,
-            "reading": 200
-          },
-          "local_capacity_bytes": {
-            "flood": 300000
-          },
-          "peer_capacity": 169,
-          "peer_capacity_bytes": 288408
-        },
-        "id": "SatoshiPay Frankfurt",
-        "latency": 282,
-        "olver": 32,
-        "ver": "stellar-core 20.4.0 (7fc7671b8bc1ccc3b1f16a6ab83bc9f671db8b70)"
-      }
-    ]
-  },
-  "pending_peers": {
-    "inbound": ["211.249.63.74:11625", "45.77.5.118:11625"],
-    "outbound": ["178.21.47.226:11625", "178.131.109.241:11625"]
-  }
-}
-```
-
-## Encuesta de Topología de Overlay
-
-Hay un mecanismo de encuesta en el overlay que permite a un validador solicitar información de conexión de otros nodos en la red. La encuesta puede ser activada por un validador y se difundirá a través de la red como cualquier otro mensaje, pero solicitará información de otros nodos sobre a qué nodos está conectado y un breve resumen de sus volúmenes de tráfico por conexión.
-
-Por defecto, un nodo retransmitirá o responderá a un mensaje de encuesta si el mensaje se originó desde un nodo en el quórum transitorio del nodo receptor. Este comportamiento puede ser anulado configurando el campo `SURVEYOR_KEYS` en el archivo de configuración a un conjunto más restrictivo de nodos para retransmitir o responder. Establece `SURVIVOR_KEYS` a `["$self"]` para optar por no responder a las solicitudes de encuesta en su totalidad.
-
-La encuesta funciona en dos fases: la fase de recolección y la fase de reporte. Durante la fase de recolección, los nodos registran información sobre sí mismos y sus usuarios, como el número de mensajes enviados a un usuario dado. Durante la fase de reporte, el encuestador solicita los resultados de la fase de recolección a los nodos en la red.
-
-El encuestador comienza la fase de recolección transmitiendo un `TimeSlicedSurveyStartCollectingMessage`. El encuestador termina la fase de recolección e inicia la fase de reporte transmitiendo un `TimeSlicedSurveyStopCollectingMessage`. Estos mensajes de "inicio/parar recolección" aseguran que la fase de recolección sea aproximadamente igual en duración para todos los nodos presentes durante toda la fase de recolección. Recomendamos enviar el mensaje de "parar recolección" aproximadamente 20 minutos después del mensaje de "iniciar recolección". Si pasan 30 minutos sin recibir un mensaje de "parar recolección", la encuesta pasará automáticamente a la fase de reporte.
-
-Además, los mensajes de "parar/iniciar recolección" contienen un campo `nonce` que identifica la instancia de la encuesta. El nonce en el mensaje de "parar recolección" debe coincidir con el nonce del mensaje de "iniciar recolección". El encuestador debe elegir un entero sin signo aleatorio de 32 bits para el nonce.
-
-Durante la fase de reporte, el encuestador envía mensajes `TimeSlicedSurveyRequestMessage` a nodos individuales para reunir la información que el nodo registró durante la fase de recolección.
-
-### Script de Encuesta de Overlay
-
-Para simplificar la ejecución de una encuesta de overlay, stellar-core incluye un script [`OverlaySurvey.py`](https://github.com/stellar/stellar-core/blob/master/scripts/OverlaySurvey.py) en el [`directorio scripts`](https://github.com/stellar/stellar-core/tree/master/scripts). Este script recorre la red utilizando los puntos finales HTTP de la encuesta de overlay para construir un grafo que contiene la topología de la red de overlay. El script genera este grafo en formato JSON, así como en GraphML. Puedes analizar el archivo GraphML usando un visor de GraphML como [Gephi](https://gephi.org/).
-
-Un ejemplo de uso del script de encuesta para ejecutar una encuesta de overlay es el siguiente:
-
-```bash
-$ python3 OverlaySurvey.py survey -n http://127.0.0.1:11626 -c 20 -sr sr.json -gmlw gmlw.graphml
-```
-
-Los argumentos que usa este ejemplo son:
-
-- subcomando `survey` - ejecutar encuesta y analizar
-  - `-n NODE`, `--node NODE` - dirección del nodo de encuesta inicial
-  - `-c DURATION`, `--collectDuration DURATION` - duración de la fase de recolección de la encuesta en minutos
-  - `-gmlw GRAPHMLWRITE`, `--graphmlWrite GRAPHMLWRITE` - archivo de salida para el archivo graphml
-  - `-sr SURVEYRESULT`, `--surveyResult SURVEYRESULT` - archivo de salida para los resultados de la encuesta
-
-Por lo tanto, este ejemplo ejecutará una encuesta desde un nodo de stellar-core que se ejecuta en la máquina local con una duración de fase de recolección de 20 minutos y generará los resultados en `sr.json` y `gmlw.graphml`.
-
-#### Adjuntarse a una Encuesta en Ejecución
-
-Usa la opción `--startPhase` para adjuntar el script a una encuesta que ya está en ejecución. Esto puede ser necesario si algo sucedió durante la ejecución del script que provocó que el script terminara antes de tiempo (como perder la conexión con el nodo encuestador). `--startPhase` tiene tres valores posibles:
-
-- `startCollecting`: iniciar una encuesta desde el principio de la fase de recolección. Este es el valor predeterminado cuando `--startPhase` no está especificado. Indica que te gustaría iniciar una nueva encuesta desde el principio (es decir, no estás adjuntando el script a una encuesta existente).
-- `stopCollecting`: transmitir inmediatamente un `TimeSlicedSurveyStopCollectingMessage` para la encuesta actualmente en ejecución y comenzar a encuestar a nodos individuales por resultados. Usa esta opción si tu encuesta está actualmente en la fase de recolección y deseas moverla a la fase de reporte.
-- `surveyResults`: comenzar a encuestar a nodos individuales por resultados. Usa esta opción si tu encuesta está en la fase de reporte.
-
-#### Más Opciones del Script de Encuesta
-
-El script de encuesta contiene subcomandos y opciones adicionales para analizar aún más los resultados de la encuesta. Puedes encontrar una lista completa de subcomandos ejecutando:
-
-```bash
-$ python3 OverlaySurvey.py -h
-```
-
-A partir de ahí, puedes ejecutar:
-
-```bash
-$ python3 OverlaySurvey.py <subcommand> -h
-```
-
-para más información sobre cualquier subcomando dado.
-
-### Ejemplo de Comando de Encuesta Usando Puntos Finales HTTP
-
-Esta sección describe un ejemplo de ejecución de una encuesta de overlay llamando directamente a los puntos finales HTTP de la encuesta. Te recomendamos encarecidamente utilizar el script de encuesta de overlay en su lugar. Esta sección puede ser útil para cualquiera que quiera modificar el script de encuesta, o para cualquiera que tenga curiosidad sobre los detalles de bajo nivel de cómo funciona la encuesta y los datos que incluye.
-
-En este ejemplo, tenemos tres nodos `GBBN`, `GDEX` y `GBUI` (los mencionaremos por las primeras cuatro letras de sus claves públicas). Ejecutaremos los comandos a continuación desde `GBUI`, y ten en cuenta que `GBBN` tiene `SURVEYOR_KEYS=["$self"]` en su archivo de configuración, por lo que `GBBN` no retransmitirá ni responderá a ningún mensaje de encuesta.
-
-```bash
-# 1. Begin the surveyor collecting phase
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'startsurveycollecting?nonce=1234'
-# 2. Stop the surveyor collecting phase, and begin the reporting phase
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'stopsurveycollecting?nonce=1234'
-# 3. Request survey results from the `GBBN` node
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'surveytopologytimesliced?node=GBBNXPPGDFDUQYH6RT5VGPDSOWLZEXXFD3ACUPG5YXRHLTATTUKY42CL&inboundpeerindex=0&outboundpeerindex=0'
-# 4. Request survey results from the `GDEX` node
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'surveytopologytimesliced?node=GDEXJV6XKKLDUWKTSXOOYVOYWZGVNIKKQ7GVNR5FOV7VV5K4MGJT5US4&inboundpeerindex=0&outboundpeerindex=0'
-# 3. Retrieve and display the results of issued survey commands
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'getsurveyresult'
-```
-
-Una vez que se reciban las respuestas, el comando `getsurveyresult` devolverá un resultado como este:
-
-```json
-{
-  "backlog": [],
-  "badResponseNodes": null,
-  "surveyInProgress": true,
-  "topology": {
-    "GBBNXPPGDFDUQYH6RT5VGPDSOWLZEXXFD3ACUPG5YXRHLTATTUKY42CL": null,
-    "GDEXJV6XKKLDUWKTSXOOYVOYWZGVNIKKQ7GVNR5FOV7VV5K4MGJT5US4": {
-      "inboundPeers": [
-        {
-          "bytesRead": 26392,
-          "bytesWritten": 26960,
-          "duplicateFetchBytesRecv": 0,
-          "duplicateFetchMessageRecv": 0,
-          "duplicateFloodBytesRecv": 10424,
-          "duplicateFloodMessageRecv": 43,
-          "messagesRead": 93,
-          "messagesWritten": 96,
-          "nodeId": "GBBNXPPGDFDUQYH6RT5VGPDSOWLZEXXFD3ACUPG5YXRHLTATTUKY42CL",
-          "secondsConnected": 22,
-          "uniqueFetchBytesRecv": 0,
-          "uniqueFetchMessageRecv": 0,
-          "uniqueFloodBytesRecv": 11200,
-          "uniqueFloodMessageRecv": 46,
-          "version": "v12.2.0-46-g61aadd29"
-        },
-        {
-          "bytesRead": 32204,
-          "bytesWritten": 31212,
-          "duplicateFetchBytesRecv": 0,
-          "duplicateFetchMessageRecv": 0,
-          "duplicateFloodBytesRecv": 11200,
-          "duplicateFloodMessageRecv": 46,
-          "messagesRead": 115,
-          "messagesWritten": 112,
-          "nodeId": "GBUICIITZTGKL7PUBHUPWD67GDRAIYUA4KCOH2PUIMMZ6JQLNVA7C4JL",
-          "secondsConnected": 23,
-          "uniqueFetchBytesRecv": 176,
-          "uniqueFetchMessageRecv": 2,
-          "uniqueFloodBytesRecv": 14968,
-          "uniqueFloodMessageRecv": 62,
-          "version": "v12.2.0-46-g61aadd29"
-        }
-      ],
-      "numTotalInboundPeers": 2,
-      "numTotalOutboundPeers": 0,
-      "maxInboundPeerCount": 64,
-      "maxOutboundPeerCount": 8,
-      "addedAuthenticatedPeers": 0,
-      "droppedAuthenticatedPeers": 0,
-      "p75SCPFirstToSelfLatencyMs": 72,
-      "p75SCPSelfToOtherLatencyMs": 112,
-      "lostSyncCount": 0,
-      "isValidator": false,
-      "outboundPeers": null
-    }
-  }
-}
-```
-
-En este ejemplo, ten en cuenta que el nodo `GBBN` bajo el campo `topology` tiene un valor `null` porque está configurado para no responder al mensaje de encuesta.
-
-Algunos campos destacados de este punto final `getsurveyresult` son:
-
-- `backlog`: lista de nodos para los cuales aún no se han enviado las solicitudes de encuesta.
-- `badResponseNodes`: lista de nodos que enviaron una respuesta malformada.
-- `topology`: mapa de nodos a información de conexión.
-  - `inboundPeers`/`outboundPeers`: lista de información de conexión por nodos.
-    - `averageLatencyMs`: latencia promedio con este usuario en milisegundos.
-    - `bytesRead`: el número total de bytes leídos de este usuario.
-    - `bytesWritten`: el número total de bytes escritos a este usuario.
-    - `duplicateFetchBytesRecv`: el número de bytes recibidos que eran conjuntos de transacciones duplicados y conjuntos de quórum.
-    - `duplicateFetchMessageRecv`: el conteo de conjuntos de transacciones duplicados y conjuntos de quórum recibidos de este usuario.
-    - `duplicateFloodBytesRecv`: el número de bytes recibidos que eran duplicados de transacciones y votos del SCP.
-    - `duplicateFloodMessageRecv`: el conteo de transacciones duplicadas y votos SCP recibidos de este usuario.
-    - `messagesRead`: el número total de mensajes leídos de este usuario.
-    - `messagesWritten`: el número total de mensajes escritos a este usuario.
-    - `nodeId`: clave pública del nodo.
-    - `secondsConnected`: el número total de segundos que este usuario ha estado conectado al nodo encuestado.
-    - `uniqueFetchBytesRecv`: el número de bytes recibidos que eran conjuntos de transacciones y conjuntos de quórum únicos.
-    - `uniqueFetchMessageRecv`: el conteo de conjuntos de transacciones y conjuntos de quórum únicos recibidos de este usuario.
-    - `uniqueFloodBytesRecv`: el número de bytes recibidos que eran transacciones únicas y votos del SCP.
-    - `uniqueFloodMessageRecv`: el conteo de transacciones únicas y votos SCP recibidos de este usuario.
-    - `version`: versión de stellar-core.
-- `numTotalInboundPeers`/`numTotalOutboundPeers`: el número de usuarios entrantes y salientes a los que este nodo está conectado. La respuesta tendrá un subconjunto aleatorio de 25 usuarios conectados por dirección (entrante/saliente). Estos campos te indican si te faltan nodos para que puedas enviar otra solicitud para obtener otro subconjunto aleatorio de nodos.
-- `maxInboundPeerCount`/`maxOutboundPeerCount`: el número total de usuarios entrantes y salientes que este nodo puede aceptar. Estos campos corresponden a las configuraciones de stellar-core `MAX_ADDITIONAL_PEER_CONNECTIONS` y `TARGET_PEER_CONNECTIONS`, respectivamente.
-- `addedAuthenticatedPeers`: el número de usuarios autenticados añadidos.
-- `droppedAuthenticatedPeers`: el número de usuarios autenticados descartados.
-- `p75SCPFirstToSelfLatencyMs`: latencia del percentil 75 para escuchar sobre nuevos mensajes de SCP en milisegundos.
-- `p75SCPSelfToOtherLatencyMs`: latencia del percentil 75 para que otros nodos escuchen los mensajes SCP de este nodo en milisegundos.
-- `lostSyncCount`: el número de veces que este nodo perdió la sincronización.
-- `isValidator`: ¿Es este nodo un validador?
-
-## Salud del Quórum
-
-Para ayudar a los operadores de nodos a monitorear sus conjuntos de quórum y mantener la salud de la red en general, Stellar Core también proporciona métricas sobre otros nodos en tu conjunto de quórum. Debes monitorearlos para asegurarte de que estén funcionando y de que tu conjunto de quórum mantenga una buena superposición con el resto de la red.
-
-### Diagnósticos del Conjunto de Quórum
-
-El comando `quorum` te permite diagnosticar problemas con el conjunto de quórum del nodo local.
-
-Si ejecutas:
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'quorum'
-```
-
-La salida se verá algo así:
-
-```json
-{
-  "node": "GCTSF",
-  "qset": {
-    "agree": 6,
-    "cost": 20883268,
-    "delayed": null,
-    "disagree": null,
-    "fail_at": 2,
-    "fail_with": ["sdf_watcher1", "sdf_watcher2"],
-    "hash": "d5c247",
-    "lag_ms": {
-      "sdf_watcher1": 192,
-      "sdf_watcher2": 215,
-      "sdf_watcher3": 79,
-      "stronghold1": 321,
-      "eno": 266,
-      "tempo.eu.com": 225,
-      "satoshipay": 249
-    },
-    "ledger": 24311847,
-    "missing": ["stronghold1"],
-    "phase": "EXTERNALIZE",
-    "value": {
-      "t": 3,
-      "v": [
-        "sdf_watcher1",
-        "sdf_watcher2",
-        "sdf_watcher3",
-        {
-          "t": 3,
-          "v": ["stronghold1", "eno", "tempo.eu.com", "satoshipay"]
-        }
-      ]
-    }
-  },
-  "transitive": {
-    "critical": [["GDM7M"]],
-    "intersection": true,
-    "last_check_ledger": 24311536,
-    "node_count": 21
-  }
-}
-```
-
-Esta salida tiene dos secciones principales: `qset` y `transitive`. La primera describe el nodo y su conjunto de quórum. La última describe el cierre transitivo del conjunto de quórum del nodo.
-
-### Información por Nodo del Conjunto de Quórum
-
-Entradas a observar en la sección `qset`, que describen el nodo y su conjunto de quórum, son:
-
-- `agree`: el número de nodos en el conjunto de quórum que parecen estar funcionando como se espera. El nodo local no tiene razón para creer que este nodo esté `delayed`, `disagree` o `missing`. Ten en cuenta que `agree` no tiene nada que ver con términos de SCP como "accept" o "confirming".
-- `delayed`: los nodos que están participando en el consenso pero parecen estar atrasados.
-- `disagree`: los nodos que están participando pero no están de acuerdo con esta instancia.
-- `fail_at`: el número de nodos fallidos que _causarían_ que esta instancia se detenga.
-- `fail_with`: un ejemplo de tal fallo potencial.
-- `missing`: los nodos que parecen estar fuera durante esta ronda de consenso.
-- `value`: el conjunto de quórum utilizado por este nodo (`t` es el umbral expresado como un número de nodos).
-
-En el ejemplo anterior, 6 nodos están funcionando correctamente, uno está fuera (`stronghold1`), y la instancia fallará si fallan algún par de nodos que todavía están funcionando (o un nodo y un conjunto de quórum interno).
-
-Si un nodo está atascado en el estado `Joining SCP`, este comando permite encontrar rápidamente la razón:
-
-- demasiados validadores faltantes (fuera o sin buena conectividad), las soluciones son:
-  - [ajustar tu conjunto de quórum](./configuring.mdx#choosing-your-quorum-set) (umbrales, agrupamiento, etc.) basado en los nodos que no están faltando
-  - intentar obtener un [mejor camino de conectividad](./configuring.mdx#quorum-and-overlay-network) hacia los validadores que faltan
-- la división de la red causaría que el SCP se quedara atascado debido a nodos que no están de acuerdo. Esto ocurriría si hay un error en el SCP, la red no tiene intersección de quórum o los nodos en desacuerdo están comportándose mal (comprometidos, etc.).
-
-Ten en cuenta que el nodo que no puede alcanzar consenso no significa que la red en su conjunto no pueda alcanzar consenso (y lo opuesto es cierto, la red puede fallar debido a un conjunto diferente de validadores que fallan).
-
-Puedes obtener una idea de la salud del conjunto de quórum de un nodo diferente utilizando:
-
-```bash
-# the `NAME` of a validator
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'quorum?node=$sdf1'
-# OR the `PUBLIC_KEY` of a validator
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'quorum?node=@GABCDE'
-```
-
-La salud general de la red se puede evaluar recorriendo todos los nodos y observando su salud. Ten en cuenta que esto es solo una aproximación, ya que los nodos remotos pueden no haber recibido los mismos mensajes (en particular: `missing` para otros nodos no es fiable).
-
-### Información resumida de cierre transitivo
-
-Al mostrar información del conjunto de quórum sobre el nodo local en lugar de otro nodo, también se proporciona un resumen del cierre transitivo del conjunto de quórum en el campo `transitive`. Esto tiene varios subcampos importantes:
-
-- `last_check_ledger`: el último ledger en el que se verificó el cierre transitivo para la intersección de quórum. Esto se restablecerá cuando el nodo arranque y cada vez que un nodo en el quórum transitivo cambie su conjunto de quórum. Puede retrasarse respecto al último ledger cerrado por varias ledgers dependiendo del coste computacional de verificar la intersección de quórum.
-- `node_count`: el número de nodos en el cierre transitivo, que se consideran al calcular la intersección de quórum.
-- `intersection`: si el cierre transitivo disfrutó o no de la intersección de quórum en la última verificación. Esto es de **máxima importancia** para prevenir divisiones en la red. Siempre debería ser cierto. Si alguna vez es falso, uno o más nodos en el cierre transitivo del conjunto de quórum están _actualmente_ mal configurados, y la red está en riesgo de dividirse. Se deben tomar medidas correctivas de inmediato, para lo cual se presentarán dos subcampos adicionales para ayudar a sugerir remedios:
-  - `last_good_ledger`: esto anotará el último ledger para el cual el campo `intersection` se evaluó como verdadero; si algún nodo se reconfiguró en o alrededor de ese ledger, revertir ese cambio de configuración es la acción correctiva más fácil de tomar.
-  - `potential_split`: esto contendrá un par de listas de identificadores de validadores, que es un par potencial de quórums disjuntos permitidos por la configuración actual. En otras palabras, una posible división en el consenso permitida por la configuración actual. Esto puede ayudar a delimitar la causa de la mala configuración: probablemente involucra un umbral de consenso demasiado bajo en uno de los dos quórums potenciales, y/o la ausencia de una relación de confianza obligatoria que uniría a los dos.
-- `critical`: un campo de "advertencia anticipada" que lista los nodos que _podrían causar_ que la red no disfrute de la intersección de quórum, si estuvieran mal configurados suficientemente. En una configuración de red transitoria saludable, este campo será `null`. Si no es `null`, entonces la red está esencialmente "una mala configuración" (de los conjuntos de quórum de los nodos listados) lejos de no disfrutar más de la intersección de quórum, y de nuevo, se deben tomar medidas correctivas: ajuste cuidadoso de los conjuntos de quórum de _nodos que dependen de_ los nodos listados, típicamente para fortalecer quórums que dependen de ellos.
-
-### Análisis detallado del quórum transitorio
-
-El punto final de quórum también puede recuperar información detallada sobre el quórum transitorio. Este es un formato que es más fácil de procesar que lo que devuelve `scp`, ya que no contiene todos los mensajes de SCP.
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'quorum?transitive=true'
-```
-
-La salida se ve algo así como:
-
-```json
-{
-  "critical": null,
-  "intersection": true,
-  "last_check_ledger": 121235,
-  "node_count": 4,
-  "nodes": [
-    {
-      "distance": 0,
-      "heard": 121235,
-      "node": "GB7LI",
-      "qset": {
-        "t": 2,
-        "v": ["sdf1", "sdf2", "sdf3"]
-      },
-      "status": "tracking",
-      "value": "[ txH: d99591, ct: 1557426183, upgrades: [ ] ]",
-      "value_id": 1
-    },
-    {
-      "distance": 1,
-      "heard": 121235,
-      "node": "sdf2",
-      "qset": {
-        "t": 2,
-        "v": ["sdf1", "sdf2", "sdf3"]
-      },
-      "status": "tracking",
-      "value": "[ txH: d99591, ct: 1557426183, upgrades: [ ] ]",
-      "value_id": 1
-    },
-    {
-      "distance": 1,
-      "heard": 121235,
-      "node": "sdf3",
-      "qset": {
-        "t": 2,
-        "v": ["sdf1", "sdf2", "sdf3"]
-      },
-      "status": "tracking",
-      "value": "[ txH: d99591, ct: 1557426183, upgrades: [ ] ]",
-      "value_id": 1
-    },
-    {
-      "distance": 1,
-      "heard": 121235,
-      "node": "sdf1",
-      "qset": {
-        "t": 2,
-        "v": ["sdf1", "sdf2", "sdf3"]
-      },
-      "status": "tracking",
-      "value": "[ txH: d99591, ct: 1557426183, upgrades: [ ] ]",
-      "value_id": 1
-    }
-  ]
-}
-```
-
-La salida comienza con la misma información resumida que en el bloque `transitive` de la consulta no transitoria (si se consulta para el nodo local), pero también incluye un array `nodes` que representa un recorrido del quórum transitorio centrado en el nodo de consulta.
-
-Los campos notables contenidos en esta respuesta son:
-
-- `node`: la identidad del validador
-- `distance`: cuán lejos está ese nodo del nodo raíz (es decir, cuántas saltos del conjunto de quórum)
-- `heard`: el último número de secuencia de ledger en el que este nodo emitió un voto
-- `qset`: el conjunto de quórum del nodo
-- `status`: uno de `behind|tracking|ahead` (comparado con el nodo raíz) o `missing|unknown` (cuando no hay mensajes recientes de SCP para ese nodo)
-- `value_id`: un ID único para lo que el nodo está votando (te permite saber rápidamente si los nodos están votando por lo mismo)
-- `value`: por lo que el nodo está votando
-
-## Usando Prometheus
-
-Monitorear `stellar-core` usando Prometheus es, con mucho, la solución más simple, especialmente si ya tienes un servidor Prometheus dentro de tu infraestructura. Prometheus es una base de datos de series temporales de código abierto y gratuito con un lenguaje de consulta simple pero increíblemente poderoso `PromQL`. Prometheus también está estrechamente integrado con Grafana, por lo que puedes renderizar visualizaciones complejas con facilidad.
-
-Para que Prometheus capture métricas de la aplicación `stellar-core`, necesitarás instalar el stellar-core-prometheus-exporter (`apt-get install stellar-core-prometheus-exporter`) y configurar tu servidor Prometheus para capturar este exportador (puerto por defecto: `9473`). Además, Grafana se puede usar para visualizar métricas.
-
-### Instalar un servidor Prometheus dentro de tu infraestructura
-
-Instalar y configurar un servidor Prometheus está fuera del alcance de este documento, sin embargo es un proceso bastante simple: Prometheus es un único binario en Go que puedes descargar desde https://prometheus.io/docs/prometheus/latest/installation/.
-
-### Instalar el `stellar-core-prometheus-exporter`
-
-El stellar-core-prometheus-exporter es un exportador que captura el punto final de métricas `stellar-core` (`http://localhost:11626/metrics`) y presenta estas métricas en el formato basado en texto de Prometheus disponible para que Prometheus las capture y las almacene en su base de datos de series temporales.
-
-El exportador necesita ser instalado en cada nodo Stellar Core que desees monitorear.
-
-```bash
-apt-get install stellar-core-prometheus-exporter
-```
-
-Necesitarás abrir el puerto `9473` entre tu servidor Prometheus y todos tus nodos Stellar Core para que tu servidor Prometheus pueda capturar métricas.
-
-### Apunta Prometheus al stellar-core-prometheus-exporter
-
-Apuntar tu instancia de Prometheus al exportador se puede lograr configurando manualmente un trabajo de captura; sin embargo, dependiendo del número de hosts que necesites monitorear, esto puede volverse rápidamente complicado. Afortunadamente, el proceso también se puede automatizar utilizando varios complementos de "descubrimiento de servicios" de Prometheus. Por ejemplo, con una instancia alojada en AWS puedes usar el complemento `ec2_sd_config`.
-
-#### Manual
-
-```yaml
-- job_name: "stellar-core"
-  scrape_interval: 10s
-  scrape_timeout: 10s
-  static_configs:
-    - targets: [
-          "core-node-001.example.com:9473",
-          "core-node-002.example.com:9473",
-        ] # stellar-core-prometheus-exporter default port is 9473
-    - labels:
-      application: "stellar-core"
-```
-
-#### Usando descubrimiento de servicios (EC2)
-
-```yaml
-- job_name: stellar-core
-  scrape_interval: 10s
-  scrape_timeout: 10s
-  ec2_sd_configs:
-    - region: eu-west-1
-      port: 9473
-  relabel_configs:
-    # ignore stopped instances
-    - source_labels: [__meta_ec2_instance_state]
-      regex: stopped
-      action: drop
-    # only keep with `core` in the Name tag
-    - source_labels: [__meta_ec2_tag_Name]
-      regex: "(.*core.*)"
-      action: keep
-    # use Name tag as instance label
-    - source_labels: [__meta_ec2_tag_Name]
-      regex: "(.*)"
-      action: replace
-      replacement: "${1}"
-      target_label: instance
-    # set application label to stellar-core
-    - source_labels: [__meta_ec2_tag_Name]
-      regex: "(.*core.*)"
-      action: replace
-      replacement: stellar-core
-      target_label: application
-```
-
-### Crear reglas de alerta
-
-Una vez que Prometheus capture métricas, podemos agregar reglas de alerta. Las reglas recomendadas están [**aquí**](https://github.com/stellar/packages/blob/master/docs/stellar-core-alerting.rules) (requieren Prometheus 2.0 o posterior). Copia las reglas en _/etc/prometheus/stellar-core-alerting.rules_ en el servidor Prometheus y agrega lo siguiente al archivo de configuración de prometheus para incluir el archivo:
-
-```yaml
-rule_files:
-  - "/etc/prometheus/stellar-core-alerting.rules"
-```
-
-Las reglas están documentadas en línea, y recomendamos encarecidamente que revises y verifiques todas ellas, ya que cada entorno es diferente.
-
-### Configurar notificaciones usando Alertmanager
-
-Alertmanager es responsable de enviar notificaciones. Instalar y configurar un servidor Alertmanager está fuera del alcance de este documento, sin embargo, es un proceso bastante simple. La documentación oficial está [aquí](https://github.com/prometheus/alertmanager/).
-
-Todas las reglas de alerta recomendadas tienen la etiqueta de "severidad":
-
-- **critical** normalmente requiere atención inmediata. Indican una interrupción en curso o muy probable. Recomendamos que las alertas críticas notifiquen a los administradores 24x7
-- **warning** normalmente puede esperar hasta las horas laborables. Las advertencias indican problemas que probablemente no tengan impacto en producción, pero que pueden llevar a alertas críticas o interrupciones si se dejan sin manejar
-
-El siguiente ejemplo de configuración de Alertmanager demuestra cómo enviar notificaciones utilizando diferentes métodos basados en la etiqueta de severidad:
-
-```yaml
-global:
-  smtp_smarthost: localhost:25
-  smtp_from: alertmanager@example.com
-route:
-  receiver: default-receiver
-  group_by: [alertname]
-  group_wait: 30s
-  group_interval: 5m
-  repeat_interval: 1h
-  routes:
-    - receiver: critical-alerts
-      match:
-        severity: critical
-    - receiver: warning-alerts
-      match:
-        severity: warning
-receivers:
-  - name: critical-alerts
-    pagerduty_configs:
-      - routing_key: <PD routing key>
-  - name: warning-alerts
-    slack_configs:
-      - api_url: https://hooks.slack.com/services/slack/warning/channel/webhook
-  - name: default-receiver
-    email_configs:
-      - to: alerts-fallback@example.com
-```
-
-En los ejemplos anteriores, las alertas con severidad "critical" se envían a pagerduty y las advertencias se envían a slack.
-
-### Exportadores útiles
-
-Puedes encontrar útiles los siguientes exportadores para monitorear tu infraestructura, ya que proporcionan una increíble información sobre el sistema operativo y las métricas de la base de datos. Instalar y configurar estos exportadores está fuera del alcance de este documento, pero debería ser relativamente sencillo.
-
-- [node_exporter](https://prometheus.io/docs/guides/node-exporter/) se puede utilizar para rastrear todas las métricas del sistema operativo.
-- [postgresql_exporter](https://github.com/wrouesnel/postgres_exporter) se puede utilizar para monitorear la base de datos local de stellar-core.
-
-### Visualizar métricas usando Grafana
-
-Una vez que hayas configurado Prometheus para capturar y almacenar métricas de tu stellar-core, querrás una buena manera de representar estos datos para el consumo humano. Grafana ofrece la manera más sencilla y efectiva de lograr esto. Instalar Grafana está fuera del alcance de este documento, pero es un proceso muy simple, especialmente al usar los [paquetes apt preconstruidos](https://grafana.com/docs/installation/debian/#apt-repository)
-
-Recomendamos que los administradores importen los siguientes dos tableros en sus implementaciones de Grafana:
-
-- [**Stellar Core Monitoring**](https://grafana.com/grafana/dashboards/10603) - muestra las métricas más importantes, el estado del nodo y trata de resaltar problemas comunes. Es un buen punto de partida para solucionar problemas
-- [**Stellar Core Full**](https://grafana.com/grafana/dashboards/10334) - muestra un resumen simple de salud así como todas las métricas expuestas por el `stellar-core-prometheus-exporter`. Es mucho más detallado que el _Stellar Core Monitoring_ y puede ser útil durante la solución de problemas en profundidad
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/network-upgrades.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/network-upgrades.mdx
deleted file mode 100644
index 393434e6f6..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/network-upgrades.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Actualizar la red
-sidebar_position: 100
----
-
-La red misma tiene configuraciones a nivel de red que pueden ser actualizadas.
-
-Esto se realiza mediante validadores que votan y coinciden con nuevos valores de la misma manera en que se alcanza el consenso para los conjuntos de transacciones, etc.
-
-Un nodo puede ser configurado para votar por actualizaciones usando el endpoint `upgrades`. Consulta [Comandos](./commands.mdx) para más información.
-
-Las configuraciones de la red son:
-
-- la versión del protocolo utilizado para procesar transacciones;
-- el número máximo de transacciones que pueden ser incluidas en un cierre de ledger dado. Configuración separada para transacciones Soroban y clásicas;
-- el costo (tarifa) asociado con el procesamiento de operaciones;
-- la reserva base utilizada para calcular el saldo de lumen necesario para almacenar datos no Soroban en el ledger; y
-- configuraciones de red Soroban generalizadas almacenadas en `ConfigSettingsEntries`.
-
-Cuando el tiempo de la red es posterior al `upgradetime` especificado en el comando `upgrades`, el validador votará para actualizar la red al valor especificado en ese comando `upgrades`. Si el tiempo de la red ha pasado el `upgradetime` por más de 12 horas, la actualización será ignorada.
-
-Cuando un validador está listo para cambiar valores de la red, la salida de `info` contendrá información sobre la votación.
-
-Para que un nuevo valor sea adoptado, se necesita alcanzar el mismo nivel de consenso entre nodos que para los conjuntos de transacciones.
-
-## Notas importantes sobre las configuraciones a nivel de red
-
-Los cambios en las configuraciones a nivel de red deben ser orquestados adecuadamente entre validadores así como nodos no validadores. El proceso general que los validadores han utilizado para proponer y votar sobre las configuraciones de la red es el siguiente:
-
-1. Un cambio es revisado entre operadores (los cambios pueden ser agrupados).
-2. Se elige una fecha efectiva en el futuro para que el cambio surta efecto (controlada por el parámetro `upgradetime` del comando `upgrades`).
-3. Si es aplicable, se envía comunicación a todos los usuarios de la red.
-
-Esta cuidadosa orquestación juega un papel importante en el funcionamiento de la red Stellar. Este proceso de planificación se lleva a cabo para evitar comportamientos indebidos de nodos, dar a conocer nuevas características incluidas en una actualización del protocolo para que el ecosistema esté al tanto y pueda aprovecharlas, y también le da al ecosistema tiempo para prepararse para cambios disruptivos que pueden tener un efecto (ya sea directa o indirectamente) en sus integraciones con Stellar. Un plan inapropiado puede causar incidencias tales como:
-
-- nodos que no alcanzan consenso (también conocido como "quedarse atascados"), y teniendo que usar el historial para reintegrarse
-- la reconfiguración de la red que toma efecto en un tiempo no determinístico (causando que las tarifas cambien antes de lo programado, por ejemplo)
-
-Para más información, consulta cómo el versionado tiene en cuenta las actualizaciones de red en [el documento `versioning.md`](https://github.com/stellar/stellar-core/blob/master/docs/versioning.md) en el repositorio de GitHub de stellar-core.
-
-## Actualización de configuraciones Soroban
-
-El mecanismo para actualizar configuraciones Soroban es más complejo que actualizar algo como la `baseReserve`. El endpoint `upgrades` en stellar-core requerirá que los validadores voten sobre un `ConfigUpgradeSetKey` serializado, que contiene un contractID y el hash SHA-256 del `ConfigUpgradeSet` que se aplicará a las configuraciones existentes. El `ConfigUpgradeSet` serializado debe existir en el ledger como `Temporary` `ContractData` bajo el contractID especificado anteriormente y con la clave `SCVal` `Bytes` que contiene el hash SHA-256 del `ConfigUpgradeSet`.
-
-Esto significa que alguien que desee proponer una actualización de configuración necesitará crear un contrato inteligente que escriba los bytes del `ConfigUpgradeSet` en `ContractData` (recuerda, se requiere una entrada `Temporary`), invocarlo para escribir el xdr de actualización, y luego compartir el `ConfigUpgradeSetKey` serializado para votar.
-
-Tenemos mucho más detalle en la [siguiente página](./soroban-settings.mdx) sobre _cómo_ elaborar una propuesta de actualización para estas configuraciones. Asegúrate de leer y comprender eso.
-
-## Ejemplo de comando de actualización
-
-Como ejemplo, aquí está el comando `upgrades` utilizado para actualizar la versión del protocolo a la versión 9 en el 31 de enero de 2018.
-
-```bash
-# arm the node to vote for the upgrade
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command 'upgrades?mode=set&upgradetime=2018-01-31T20:00:00Z&protocolversion=9'
-# view the status of the node
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command info
-```
-
-En este punto, `info` te dirá que el nodo está configurado para votar por esta actualización:
-
-```json
-"status" : [
-  "Armed with network upgrades: upgradetime=2018-01-31T20:00:00Z, protocolversion=9"
-]
-```
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/prerequisites.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/prerequisites.mdx
deleted file mode 100644
index 29194af9f5..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/prerequisites.mdx
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: Requisitos previos
-sidebar_position: 20
----
-
-Puedes instalar Stellar Core de [varias maneras diferentes](./installation.mdx), y una vez lo hagas, puedes [configurarlo](./configuring.mdx) para participar en la red en varios [niveles diferentes](../README.mdx#types-of-nodes): puede ser un Validador Básico o un Validador Completo. No importa cómo instales Stellar Core o qué tipo de nodo ejecutes, sin embargo, necesitas configurar y conectarte a la red peer-to-peer y almacenar el estado del ledger en una [base de datos](./configuring.mdx#database) SQL.
-
-## Requisitos de Hardware
-
-:::info
-
-El CPU, RAM, Disco y red dependen de la actividad de la red. Si decides colocalizar ciertas cargas de trabajo, necesitarás tener esto en cuenta.
-
-:::
-
-En el momento de escribir esto (abril de 2024), Stellar Core con PostgreSQL funcionando en la misma máquina funcionó bien en una instancia de [c5d.2xlarge](https://aws.amazon.com/ec2/instance-types/c5/) en AWS (8x Intel Xeon vCPUs a 3,4 GHz; 16 GB RAM; 100 GB NVMe SSD (10.000 iops)).
-
-Stellar Core está diseñado para funcionar en hardware relativamente modesto para que una amplia gama de individuos y organizaciones puedan participar en la red, y los nodos básicos deberían poder funcionar bastante bien sin una gran sobrecarga. Dicho esto, cuanto más pidas a tu nodo, mayores serán los requisitos.
-
-| Tipo de Nodo             | CPU                     | RAM   | Disco           | SKU de AWS    | SKU de Google Cloud |
-| ------------------------ | ----------------------- | ----- | --------------- | ------------- | ------------------- |
-| Nodo Validador Principal | 8x Intel Xeon @ 3,4 GHz | 16 GB | 100 GB NVMe SSD | [c5d.2xlarge] | [n4-highcpu-8]      |
-
-_\* Suponiendo una ventana de retención de 30 días para el almacenamiento de datos._
-
-## Acceso a la Red Stellar
-
-Stellar Core interactúa con la red peer-to-peer para mantener un ledger distribuido sincronizado, lo que significa que tu nodo necesita hacer ciertos [puertos TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol#TCP_ports) disponibles para la comunicación entrante y saliente.
-
-### Entrante
-
-Un nodo Stellar Core necesita permitir que todas las IPs se conecten a su `PEER_PORT` a través de TCP. Puedes especificar un puerto cuando [configuras] Stellar Core, pero la mayoría de la gente usa el predeterminado, que es **11625**.
-
-### Saliente
-
-Un nodo Stellar Core necesita conectarse a otros nodos en internet a través de su `PEER_PORT` sobre TCP. Puedes encontrar información sobre los `PEER_PORT`s de otros nodos en un explorador de red como [Stellarbeat](https://stellarbeat.io/), pero la mayoría también usa el puerto predeterminado para esto, que es (nuevamente) **11625**.
-
-## Acceso al Sistema Interno
-
-Stellar Core también necesita conectarse a ciertos sistemas internos, aunque exactamente cómo se logra esto puede variar según tu configuración.
-
-### Entrante
-
-- Stellar Core expone un endpoint HTTP _sin autenticar_ en su `HTTP_PORT`. Puedes especificar un puerto cuando [configuras] Stellar Core, pero la mayoría de la gente usa el predeterminado, que es **11626**.
-- El `HTTP_PORT` es utilizado por otros sistemas (como Stellar RPC) para enviar transacciones, por lo que este puerto puede tener que estar expuesto al resto de tus direcciones IP internas.
-- También es utilizado para consultar la [info](./commands.mdx) de Stellar Core y proporcionar [métricas](./monitoring.mdx).
-- Y para realizar comandos administrativos como [programar actualizaciones](./network-upgrades.mdx) y cambiar niveles de registro
-- Para más sobre eso, consulta [comandos](./commands.mdx)
-
-:::note Nota sobre exponer el endpoint HTTP
-
-Si necesitas exponer este endpoint a otros hosts en tu red local, te recomendamos encarecidamente que uses un servidor proxy inverso intermedio para implementar la autenticación. No expongas el endpoint HTTP a la cruda e inhumana Internet abierta.
-
-:::
-
-### Saliente
-
-- Stellar Core requiere acceso a una base de datos (PostgreSQL, por ejemplo). Si esa base de datos reside en una máquina diferente en tu red, necesitarás permitir esa conexión. Especificarás la base de datos cuando [configures] Stellar Core.
-- Puedes bloquear de manera segura todas las demás conexiones.
-
-## Almacenamiento
-
-La mayoría de las necesidades de almacenamiento provienen de la base de datos backend de stellar-core, que necesita almacenar todo el estado del ledger. En su mayor parte, el contenido tanto de la base de datos como de los directorios relacionados (como `buckets`) pueden ser ignorados, ya que son completamente gestionados por Stellar Core. En términos de espacio de almacenamiento, 100 GB son suficientes (a partir de abril de 2024).
-
-### Base de datos
-
-La base de datos se consulta durante el consenso y se modifica atómicamente cuando se aplica un conjunto de transacciones al ledger. Es de acceso aleatorio, granular y rápido.
-
-A partir de agosto de 2024, Stellar Core cambió oficialmente a BucketListDB como su backend de base de datos principal. Ten en cuenta que BucketListDB aún requiere una base de datos SQL, ya sea SQLite o Postgres (recomendado).
-
-Si usas PostgreSQL, te recomendamos que configures tu base de datos local para que sea accesible a través de un socket de dominio Unix, así como actualizar los siguientes parámetros de configuración de PostgreSQL:
-
-```text
-# !!! DB connection should be over a Unix domain socket !!!
-# shared_buffers = 25% of available system ram
-# effective_cache_size = 50% of available system ram
-# max_wal_size = 5GB
-# max_connections = 150
-```
-
-### Bolsas
-
-Stellar-core almacena el estado del ledger en forma de archivos XDR planos llamados "buckets." Los archivos de buckets se utilizan para el hashing y la transmisión de diferencias del ledger a archivos de historia. Si se utiliza BucketListDB, el directorio `buckets` también se usa como un backend principal de base de datos. Si se utiliza SQL, el directorio `buckets` solo se utiliza para hashing y archivos de historia, y simplemente representa una copia del estado del ledger almacenado en SQL.
-
-Los buckets deben estar almacenados en un disco local rápido con suficiente espacio para almacenar varias veces el tamaño del ledger actual. El tamaño actual del ledger es aproximadamente 10 GB (a partir de abril de 2024), así que por favor planifica en consecuencia.
-
-## Consideraciones de Kubernetes
-
-Actualmente no recomendamos ejecutar nodos validador en Kubernetes. Si decides hacerlo, considera lo siguiente:
-
-- Datos sensibles como semillas de nodos se almacenarán en etcd de Kubernetes. Considera consumir credenciales utilizando herramientas como [vault agent](https://developer.hashicorp.com/vault/docs/platform/k8s/injector) o el [driver CSI de AWS Secrets Store](https://github.com/aws/secrets-store-csi-driver-provider-aws) para mejorar la seguridad
-- Considera cómo el tráfico externo llegará a los pods. Los nodos de Tier 1 necesitan nombres DNS públicos y los puertos necesarios deben ser accesibles desde internet
-- Los validadores tienen semillas únicas y configuraciones de archivo de historial, por lo que cada pod requerirá su propia configuración específica
-- Asegúrate de que siempre haya suficientes recursos disponibles para los pods
-- Dependiendo de cómo se publiquen los archivos de historial, puede que necesites bifurcar imágenes de docker para incluir herramientas adicionales
-
-[configurar]: ./configuring.mdx
-[c5d.2xlarge]: https://aws.amazon.com/ec2/instance-types/c5/
-[n4-highcpu-8]: https://cloud.google.com/compute/docs/general-purpose-machines#n4-highcpu
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/publishing-history-archives.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/publishing-history-archives.mdx
deleted file mode 100644
index 0b0a0b683e..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/publishing-history-archives.mdx
+++ /dev/null
@@ -1,291 +0,0 @@
----
-title: Publicar archivos de historia
-sidebar_position: 50
----
-
-Si deseas ejecutar un [validador completo](../README.mdx#full-validator), debes configurar tu nodo para publicar un archivo de historia. Puedes alojar un archivo utilizando un blob store como Amazon S3 o los espacios de Digital Ocean, o simplemente puedes servir un archivo local directamente a través de un servidor HTTP como Nginx o Apache. Si estás configurando un [validador básico](../README.mdx#basic-validator), puedes omitir esta sección. No importa qué tipo de nodo planeas ejecutar, asegúrate de configurarlo para `get` historia, lo cual se cubre en [Preparación del entorno](./environment-preparation.mdx).
-
-## Almacenamiento en caché y archivos de historia
-
-El costo _principal_ de ejecutar un validador muy probablemente será el ancho de banda de salida. Una parte crucial de tu estrategia para gestionar esos costos debería ser el almacenamiento en caché. Puedes reducir significativamente estos costos de transferencia de datos utilizando técnicas comunes de caché o una CDN. Se aplican tres reglas simples al almacenar en caché los archivos de historia:
-
-1. No almacenes en caché el archivo de estado del archivo `.well-known/stellar-history.json` (`Cache-Control: no-cache`)
-2. No almacenes en caché las respuestas HTTP 4xx (`Cache-Control: no-cache`)
-3. Almacena en caché todo lo demás durante el mayor tiempo posible (**> 1 día**)
-
-## Archivo de historia local usando nginx
-
-Aquí, demostramos cómo puedes configurar tu nodo para almacenar sus archivos de historia en el sistema de archivos local, y luego publicar esa historia utilizando nginx para nuestro software de servidor web.
-
-Primero, debes agregar una estrofa de configuración de historia a tu archivo de configuración `/etc/stellar/stellar-core.cfg`.
-
-```toml
-[HISTORY.local]
-get="cp /mnt/xvdf/stellar-core-archive/node_001/{0} {1}"
-put="cp {0} /mnt/xvdf/stellar-core-archive/node_001/{1}"
-mkdir="mkdir -p /mnt/xvdf/stellar-core-archive/node_001/{0}"
-```
-
-Luego, debes ejecutar el comando `new-hist` de Stellar Core para crear el archivo de historia local.
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg new-hist local
-```
-
-Este comando crea la estructura del archivo de historia:
-
-```bash
-$ tree -a /mnt/xvdf/stellar-core-archive/
-/mnt/xvdf/stellar-core-archive
-└── node_001
-    ├── history
-    │   └── 00
-    │       └── 00
-    │           └── 00
-    │               └── history-00000000.json
-    └── .well-known
-        └── stellar-history.json
-
-6 directories, 2 files
-```
-
-Ahora que la estructura de archivos del archivo de historia está lista, puedes configurar un host virtual en nginx para servir el archivo local.
-
-```nginx
-server {
-  listen 80;
-  root /mnt/xvdf/stellar-core-archive/node_001/;
-
-  server_name history.example.com;
-
-  # do not cache 404 errors
-  error_page 404 /404.html;
-  location = /404.html {
-    add_header Cache-Control "no-cache" always;
-  }
-
-  # do not cache history state file
-  location ~ ^/.well-known/stellar-history.json$ {
-    add_header Cache-Control "no-cache" always;
-    try_files $uri =404;
-  }
-
-  # cache entire history archive for 1 day
-  location / {
-    add_header Cache-Control "max-age=86400";
-    try_files $uri =404;
-  }
-}
-```
-
-## Archivo de historia de Amazon S3
-
-Ahora, demostremos una configuración donde tu nodo almacena sus archivos de historia utilizando el servicio S3 de Amazon. Luego puedes publicar esa historia utilizando un sitio estático de Amazon S3, o nuevamente usar nginx para tu software de servidor web. Esta vez, usando nginx, incluiremos también alguna configuración de proxy y CDN.
-
-Comienza agregando una estrofa de configuración de historia a tu archivo de configuración `/etc/stellar/stellar-core.cfg`.
-
-```toml
-[HISTORY.s3]
-get='curl -sf http://history.example.com/{0} -o {1}' # Cached HTTP endpoint
-put='aws s3 cp --region us-east-1 {0} s3://bucket.name/{1}' # Direct S3 access
-```
-
-Luego, debes ejecutar el comando `new-hist` de Stellar Core para crear e inicializar el archivo S3.
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg new-hist s3
-```
-
-Estos archivos de historia S3 pueden ser servidos con algo tan simple como un sitio estático de Amazon S3.
-
-Opcionalmente, puedes querer colocar un proxy inverso y CDN delante del sitio estático de S3 (usaremos nginx para este ejemplo).
-
-```nginx
-server {
-  listen 80;
-  root /srv/nginx/history.example.com;
-  index index.html index.htm;
-
-  server_name history.example.com;
-
-  # use google nameservers for lookups
-  resolver 8.8.8.8 8.8.4.4;
-
-  # bucket.name s3 static site endpoint
-  set $s3_bucket "bucket.name.s3-website-us-east-1.amazonaws.com";
-
-  # do not cache 404 errors
-  error_page 404 /404.html;
-  location = /404.html {
-    add_header Cache-Control "no-cache" always;
-  }
-
-  # do not cache history state file
-  location ~ ^/.well-known/stellar-history.json$ {
-    add_header Cache-Control "no-cache" always;
-    proxy_intercept_errors on;
-    proxy_pass  http://$s3_bucket;
-    proxy_read_timeout 120s;
-    proxy_redirect off;
-    proxy_buffering off;
-    proxy_set_header        Host            $s3_bucket;
-    proxy_set_header        X-Real-IP       $remote_addr;
-    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
-    proxy_set_header        X-Forwarded-Proto $scheme;
-  }
-
-  # cache history archive for 1 day
-  location / {
-    add_header Cache-Control "max-age=86400";
-    proxy_intercept_errors on;
-    proxy_pass  http://$s3_bucket;
-    proxy_read_timeout 120s;
-    proxy_redirect off;
-    proxy_buffering off;
-    proxy_set_header        Host            $s3_bucket;
-    proxy_set_header        X-Real-IP       $remote_addr;
-    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
-    proxy_set_header        X-Forwarded-Proto $scheme;
-  }
-}
-```
-
-## Rellenar un archivo de historia
-
-Dada la opción, lo mejor es configurar tu archivo de historia _antes de_ que tu nodo inicie la sincronización con una red existente. De esa manera, la historia de tu validador se publica a medida que te unes y luego sincronizas con la red.
-
-Sin embargo, si no has publicado un archivo durante la sincronización inicial del nodo, los pasos requeridos para crear un archivo de historia para un validador existente — en otras palabras, para actualizar un validador básico a un validador completo — son bastante sencillos. Primero, deberás detener tu instancia de `stellar-core`:
-
-```bash
-systemctl stop stellar-core # modify this if not using systemctl
-```
-
-Luego, agrega la configuración del archivo de historia al archivo de configuración de tu nodo `/etc/stellar/stellar-core.cfg`.
-
-```toml
-[HISTORY.local]
-get="cp /mnt/xvdf/stellar-core-archive/node_001/{0} {1}"
-put="cp {0} /mnt/xvdf/stellar-core-archive/node_001/{1}"
-mkdir="mkdir -p /mnt/xvdf/stellar-core-archive/node_001/{0}"
-```
-
-A continuación, debes ejecutar el comando `new-hist` de Stellar Core para crear e inicializar el archivo local. (Esto se realiza como usuario `stellar`.)
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg new-hist local
-```
-
-Ahora puedes reiniciar tu instancia de Stellar Core:
-
-```bash
-systemctl start stellar-core # modify this if not using systemctl
-```
-
-A medida que permites que tu nodo se una a la red nuevamente, puedes observar cómo comienza a publicar varias comprobaciones de punto en el archivo recién creado.
-
-```log
-2019-04-25T12:30:43.275 GDUQJ [History INFO] Publishing 1 queued checkpoints [16895-16895]: Awaiting 0/0 prerequisites of: publish-000041ff
-```
-
-En esta etapa, tu validador está publicando con éxito su historia, lo que permite a otros usuarios unirse a la red utilizando tu archivo.
-
-## Archivo de historia completo
-
-La herramienta de línea de comandos [stellar-archivist](https://github.com/stellar/go-stellar-sdk/tree/main/tools/stellar-archivist) puede usarse para reflejar, escanear y reparar archivos existentes. Usando los [repositorios de paquetes SDF](https://github.com/stellar/packages), puedes instalar `stellar-archivist` ejecutando:
-
-```bash
-apt-get install stellar-archivist
-```
-
-Si decides publicar un archivo completo — lo que permite a otros usuarios unirse a la red desde el libro mayor de génesis — puedes usar `stellar-archivist` para agregar todos los datos de historia faltantes a tu archivo parcial, y para verificar el estado y la integridad de tu archivo. Por ejemplo:
-
-```bash
-stellar-archivist scan file:///mnt/xvdf/stellar-core-archive/node_001
-```
-
-```log
-2019/04/25 11:42:51 Scanning checkpoint files in range: [0x0000003f, 0x0000417f]
-2019/04/25 11:42:51 Checkpoint files scanned with 324 errors
-2019/04/25 11:42:51 Archive: 3 history, 2 ledger, 2 transactions, 2 results, 2 scp
-2019/04/25 11:42:51 Scanning all buckets, and those referenced by range
-2019/04/25 11:42:51 Archive: 30 buckets total, 30 referenced
-2019/04/25 11:42:51 Examining checkpoint files for gaps
-2019/04/25 11:42:51 Examining buckets referenced by checkpoints
-2019/04/25 11:42:51 Missing history (260): [0x0000003f-0x000040ff]
-2019/04/25 11:42:51 Missing ledger (260): [0x0000003f-0x000040ff]
-2019/04/25 11:42:51 Missing transactions (260): [0x0000003f-0x000040ff]
-2019/04/25 11:42:51 Missing results (260): [0x0000003f-0x000040ff]
-2019/04/25 11:42:51 No missing buckets referenced in range [0x0000003f, 0x0000417f]
-2019/04/25 11:42:51 324 errors scanning checkpoints
-```
-
-Como puedes ver en la salida del comando `scan`, falta algo de historia, libro mayor, transacciones y resultados del archivo de historia local.
-
-Puedes reparar los datos faltantes usando el comando `repair` de stellar-archivist combinado con un archivo completo conocido — como el archivo público de historia SDF:
-
-```bash
-stellar-archivist repair http://history.stellar.org/prd/core-testnet/core_testnet_001/ file:///mnt/xvdf/stellar-core-archive/node_001/
-```
-
-```log
-2019/04/25 11:50:15 repairing http://history.stellar.org/prd/core-testnet/core_testnet_001/ -> file:///mnt/xvdf/stellar-core-archive/node_001/
-2019/04/25 11:50:15 Starting scan for repair
-2019/04/25 11:50:15 Scanning checkpoint files in range: [0x0000003f, 0x000041bf]
-2019/04/25 11:50:15 Checkpoint files scanned with 244 errors
-2019/04/25 11:50:15 Archive: 4 history, 3 ledger, 263 transactions, 61 results, 3 scp
-2019/04/25 11:50:15 Error: 244 errors scanning checkpoints
-2019/04/25 11:50:15 Examining checkpoint files for gaps
-2019/04/25 11:50:15 Repairing history/00/00/00/history-0000003f.json
-2019/04/25 11:50:15 Repairing history/00/00/00/history-0000007f.json
-2019/04/25 11:50:15 Repairing history/00/00/00/history-000000bf.json
-...
-2019/04/25 11:50:22 Repairing ledger/00/00/00/ledger-0000003f.xdr.gz
-2019/04/25 11:50:23 Repairing ledger/00/00/00/ledger-0000007f.xdr.gz
-2019/04/25 11:50:23 Repairing ledger/00/00/00/ledger-000000bf.xdr.gz
-...
-2019/04/25 11:51:18 Repairing results/00/00/0e/results-00000ebf.xdr.gz
-2019/04/25 11:51:18 Repairing results/00/00/0e/results-00000eff.xdr.gz
-2019/04/25 11:51:19 Repairing results/00/00/0f/results-00000f3f.xdr.gz
-...
-2019/04/25 11:51:39 Repairing scp/00/00/00/scp-0000003f.xdr.gz
-2019/04/25 11:51:39 Repairing scp/00/00/00/scp-0000007f.xdr.gz
-2019/04/25 11:51:39 Repairing scp/00/00/00/scp-000000bf.xdr.gz
-...
-2019/04/25 11:51:50 Re-running checkpoing-file scan, for bucket repair
-2019/04/25 11:51:50 Scanning checkpoint files in range: [0x0000003f, 0x000041bf]
-2019/04/25 11:51:50 Checkpoint files scanned with 5 errors
-2019/04/25 11:51:50 Archive: 264 history, 263 ledger, 263 transactions, 263 results, 241 scp
-2019/04/25 11:51:50 Error: 5 errors scanning checkpoints
-2019/04/25 11:51:50 Scanning all buckets, and those referenced by range
-2019/04/25 11:51:50 Archive: 40 buckets total, 2478 referenced
-2019/04/25 11:51:50 Examining buckets referenced by checkpoints
-2019/04/25 11:51:50 Repairing bucket/57/18/d4/bucket-5718d412bdc19084dafeb7e1852cf06f454392df627e1ec056c8b756263a47f1.xdr.gz
-2019/04/25 11:51:50 Repairing bucket/8a/a1/62/bucket-8aa1624cc44aa02609366fe6038ffc5309698d4ba8212ef9c0d89dc1f2c73033.xdr.gz
-2019/04/25 11:51:50 Repairing bucket/30/82/6a/bucket-30826a8569cb6b178526ddba71b995c612128439f090f371b6bf70fe8cf7ec24.xdr.gz
-...
-```
-
-Una exploración final del archivo local confirma que ha sido reparado con éxito
-
-```bash
-stellar-archivist scan file:///mnt/xvdf/stellar-core-archive/node_001
-```
-
-```log
-2019/04/25 12:15:41 Scanning checkpoint files in range: [0x0000003f, 0x000041bf]
-2019/04/25 12:15:41 Archive: 264 history, 263 ledger, 263 transactions, 263 results, 241 scp
-2019/04/25 12:15:41 Scanning all buckets, and those referenced by range
-2019/04/25 12:15:41 Archive: 2478 buckets total, 2478 referenced
-2019/04/25 12:15:41 Examining checkpoint files for gaps
-2019/04/25 12:15:41 Examining buckets referenced by checkpoints
-2019/04/25 12:15:41 No checkpoint files missing in range [0x0000003f, 0x000041bf]
-2019/04/25 12:15:41 No missing buckets referenced in range [0x0000003f, 0x000041bf]
-```
-
-Finalmente, puedes iniciar tu instancia de stellar Core una vez más.
-
-```bash
-systemctl start stellar-core
-```
-
-Ahora deberías tener un archivo de historia completo siendo escrito por tu validador completo. ¡Felicidades!
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/running-node.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/running-node.mdx
deleted file mode 100644
index 0a23b89a1d..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/running-node.mdx
+++ /dev/null
@@ -1,112 +0,0 @@
----
-title: Ejecutando
-sidebar_position: 60
----
-
-## Comenzar Tu Nodo
-
-Una vez que [hayas configurado tu entorno](./prerequisites.mdx), [configurado tu nodo](./configuring.mdx), configurado tu [quorum set](./configuring.mdx#choosing-your-quorum-set) y seleccionado archivos para `obtener` [historia de](./environment-preparation.mdx#history-archives), estás listo para comenzar Stellar Core.
-
-Utiliza un comando equivalente a:
-
-```bash
-sudo systemctl start stellar-core
-```
-
-En este punto, estás listo para observar la actividad de tu nodo principal a medida que se une a la red.
-
-Puede que quieras avanzar y revisar la página de [Registro](./logging.mdx) para familiarizarte con la salida de Stellar Core.
-
-## Interaccionar Con Tu Instancia
-
-Cuando tu nodo está ejecutándose, puedes interactuar con Stellar Core a través de un punto final HTTP administrativo. Los comandos pueden emitirse utilizando herramientas HTTP en línea de comandos como `curl`, o ejecutando un comando de CLI como
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg http-command <http-command>
-```
-
-El punto final HTTP [no está destinado a ser expuesto a internet público](./prerequisites.mdx#internal-system-access). Se accede típicamente por administradores, o por una aplicación de nivel medio para presentar transacciones a la red Stellar.
-
-Los detalles de los comandos del _HTTP_ endpoint disponibles se pueden encontrar en el [repositorio de stellar-core en GitHub](https://github.com/stellar/stellar-core/blob/master/docs/software/commands.md#http-commands). Además, [la página de comandos](./commands.mdx) contiene una visión general de algunos de los comandos _CLI_ más útiles (comandos no HTTP) para gestionar un nodo principal en ejecución.
-
-## Uniéndote a la Red
-
-Tu nodo pasará por las siguientes fases mientras se une a la red, y puedes consultar la salida a continuación utilizando el punto final de información mencionado [aquí](./monitoring.mdx#general-node-information) :
-
-### Establecer Conexión con Otros Nodos.
-
-Deberías ver `authenticated_count` aumentar.
-
-```json
-"peers" : {
-  "authenticated_count" : 3,
-  "pending_count" : 4
-},
-```
-
-### Observando Consenso
-
-Hasta que el nodo vea un quorum, dirá:
-
-```json
-"state" : "Joining SCP"
-```
-
-Después de observar consenso, un nuevo campo `quorum` mostrará información sobre las decisiones de la red. At this point the node will switch to a "_Catching up_" state:
-
-```json
-"quorum" : {
-  "qset" : {
-    "ledger" : 22267866,
-    "cost" : 20883268,
-    "agree" : 5,
-    "delayed" : 0,
-    "disagree" : 0,
-    "fail_at" : 3,
-    "hash" : "980a24",
-    "lag_ms" : 430,
-    "missing" : 0,
-    "phase" : "EXTERNALIZE"
-  },
-  "transitive" : {
-    "intersection" : true,
-    "last_check_ledger" : 22267866,
-    "node_count" : 21
-  }
-},
-"state" : "Catching up",
-```
-
-### Poniéndose al día
-
-Esta es una fase donde el nodo descarga datos de cualquier archivo configurado. Esta fase comienza con algo como:
-
-```json
-"state" : "Catching up",
-"status" : [ "Catching up: Awaiting checkpoint (ETA: 35 seconds)" ]
-```
-
-Y luego pasará por las varias fases de descarga y aplicación de estado, como:
-
-```json
-"state" : "Catching up",
-"status" : [ "Catching up: downloading ledger files 20094/119803 (16%)" ]
-```
-
-Puedes especificar cuán atrás en el tiempo va tu nodo para ponerse al día en tu archivo de configuración. Si estableces el campo `CATCHUP_COMPLETE` en `true`, tu nodo reproducirá la _historia completa_ de la red, lo que puede llevar mucho tiempo. Semanas. Puedes acelerar el proceso copiando archivos existentes de otro validador completo, usando la herramienta [`archivist`](./publishing-history-archives.mdx#complete-history-archive). Ten en cuenta que solo necesitas reproducir todo el historial de la red si estás configurando un Validador Completo. De lo contrario, puedes especificar un punto de partida para ponerte al día usando el campo `CATCHUP_RECENT`. Para sincronizarte tan rápido como sea posible, simplemente usa los valores predeterminados de configuración para `CATCHUP_RECENT` y `CATCHUP_COMPLETE`. Consulta el [ejemplo completo de configuración] para más detalles.
-
-:::info
-
-Los campos de configuración `CATCHUP_COMPLETE` y `CATCHUP_RECENT` son mutuamente excluyentes. Si el campo `CATCHUP_COMPLETE` está establecido en `true`, el campo `CATCHUP_RECENT` será ignorado.
-
-:::
-
-### Sincronizado
-
-Cuando el nodo haya terminado de ponerse al día, su estado cambiará a:
-
-```json
-"state" : "Synced!"
-```
-
-[ejemplo completo de configuración]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/soroban-settings.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/soroban-settings.mdx
deleted file mode 100644
index b4243f4f39..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/soroban-settings.mdx
+++ /dev/null
@@ -1,176 +0,0 @@
----
-title: Configuraciones de Soroban
-sidebar_position: 110
----
-
-Soroban tiene una gran colección de configuraciones almacenadas en el ledger que se pueden modificar a través de un voto de validator. Aquí puedes descubrir cómo proponer una nueva actualización de configuraciones así como cómo examinar una actualización propuesta. También puedes consultar la [página de Comandos](./commands.mdx) para más detalles sobre los comandos de stellar-core utilizados a continuación.
-
-## Proponer una Actualización de Configuraciones
-
-Esta sección describirá cómo proponer una actualización de configuraciones, pero echa un vistazo a la [página de Actualización de la Red](./network-upgrades.mdx#upgrading-soroban-settings) para más información sobre cómo funciona internamente el mecanismo de actualización de configuraciones.
-
-:::info
-
-Si se te pide que votes por una actualización, por favor pasa a la sección [Examinar una Actualización Propuesta](#examine-a-proposed-upgrade) para detalles sobre cómo lograr eso.
-
-:::
-
-## Script de Ayuda
-
-Un script para ayudarte a crear las transacciones a continuación está disponible [en el repositorio de GitHub de stellar-core](https://github.com/stellar/stellar-core/blob/master/scripts/settings-helper.sh), con detalles de uso [también disponibles](https://github.com/stellar/stellar-core/blob/master/scripts/README.md). Hemos guardado la información a continuación por ahora, porque es importante estar consciente de cómo funciona el proceso subyacente para generar las transacciones en caso de que el script tenga algunos problemas. Hemos guardado la información a continuación por ahora, porque es importante estar al tanto de cómo funciona el proceso subyacente para generar las transacciones en caso de que el script tenga algunas incidencias.
-
-### 1. Crear un Conjunto de Actualización
-
-La herramienta `stellar` CLI permite el uso de un archivo de entrada JSON para codificar una colección de configuraciones de Soroban en una cadena codificada en base64 que representa el tipo XDR `ConfigUpgradeSet`. Puedes usar los archivos [`pubnet_phase1.json`] y [`pubnet_phase2.json`] como punto de partida para formular tu propuesta de actualización. También puedes extraer directamente de un nodo core en ejecución usando `http-command 'sorobaninfo?format=upgrade_xdr' | stellar-xdr decode --type ConfigUpgradeSet --output json-formatted`. Esto te permitirá obtener las configuraciones exactas que se están ejecutando en ese nodo core en formato JSON, facilitando el cambio solo del valor que deseas. Una vez que tengas tu archivo JSON con valores actualizados, usa el siguiente comando para crear el conjunto de actualización XDR requerido:
-
-```bash
-stellar xdr encode --type ConfigUpgradeSet path/to/upgrade.json
-```
-
-La salida del archivo JSON de la fase 2, por ejemplo, se vería así:
-
-```text
-AAAAAgAAAAEAAAAAHc1lAAAAAAAF9eEAAAAAAAAAABkCgAAAAAAAAgAAAMgAB6EgAAAAfQABEXAAAAAoAAIIAAAAABkAAQQAAAAAAAAAGGoAAAAAAAAnEAAAAAAAAAb6AAAAAukO3QD///////0NfwAAAAAAAOFfAAAD6A==
-```
-
-:::info
-
-La `stellar` CLI se puede instalar usando brew o cargo:
-
-```bash
-brew install stellar-cli
-# OR
-cargo install --locked stellar-cli
-```
-
-También puedes descargar un [binario precompilado] de la última versión para tu sistema desde GitHub.
-
-:::
-
-### 2. Generar Transacciones de Actualización de Configuraciones
-
-Puedes usar el comando `get-settings-upgrade-txs` de stellar-core para crear una serie de transacciones que:
-
-1. Restore the Wasm entry from the next step (if it exists).
-2. Upload a simple smart contract's Wasm bytecode to the network that allows for `Temporary` ledger entries to be created, keyed using `Bytes` `SCVal`s.
-3. Create's a contract instance from the previously uploaded Wasm bytecode.
-4. Invoke the newly created contract instance's `write` function with your (validated) base64-encoded upgrade set.
-
-Se requieren cuatro argumentos para este comando:
-
-- `PUBLIC_KEY`: (posicional) la clave pública que será la fuente para estas transacciones. Ten en cuenta que estarás enviando transacciones, así que la cuenta para la clave pública especificada debe existir y tener fondos para pagar las tarifas de transacción.
-- `SEQUENCE_NUMBER`: (posicional) el número de secuencia _actual_ para la clave pública especificada.
-- `NETWORK_PASSPHRASE`: (posicional) la frase de contraseña de la red a la que se enviarán estas transacciones.
-- `--xdr AAAA...`: el conjunto de actualización codificado en base64 generado en [el paso 1](#1-create-an-upgrade-set).
-- `--signtxs`: (opcional) si se proporciona, este comando te pedirá una clave secreta y devolverá transacciones _firmadas_ que pueden ser enviadas a la red de inmediato.
-
-Por ejemplo, el comando para la actualización de la fase 2 podría haber sido así:
-
-```bash
-sudo -u stellar stellar-core --conf /etc/stellar/stellar-core.cfg get-settings-upgrade-txs \
-    GAUQW73V52I2WLIPKCKYXZBHIYFTECS7UPSG4OSVUHNDXEZJJWFXZG56 \
-    73014444032 \
-    "Public Global Stellar Network ; September 2015" \
-    --xdr AAAAAgAAAAE... \
-    --signtxs
-```
-
-La salida de este comando incluirá tres conjuntos de `TransactionEnvelope`s y sus correspondientes `Hash`es de transacción, seguidos de una cadena XDR base64 codificada `ConfigUpgradeSetKey`:
-
-```bash showLineNumbers
-# restore Wasm `TransactionEnvelope` (truncated here)
-AAAAAgAAAABSvbro8P/XAQP+eTvW1TnB4+r4vZx5fKj+DsWuWN3gjQX14QAAA...LgymJ36XIBrUVMU2wg=
-# restore Wasm transaction `Hash`
-3a2457d3fc081ab3a72dfe7ee2236f3a282c62f21d7e3dbdb5b13ac0d09c8647
-# upload Wasm `TransactionEnvelope` (truncated here)
-AAAAAgAAAABi/B0L0JGythwN1lY0aypo19NHxvLCyO5tBEc...wF9wL68IAAAAdkJxSgpyRStTvbSA9jgs=
-# upload Wasm transaction `Hash`
-19c49f18e5442db9d626f7485c34ecb0cd938034255515099b37acebdb6677a7
-# create contract instance `TransactionEnvelope` (truncated here)
-AAAAAgAAAABi/B0L0JGythwN1lY0aypo19NHxvLCyO5tBEc...AAd0OB3n3Yadews=
-# create contract instance transaction `hash`
-9e70cbff631247638fae96b9d996d8d22b6fa75208380d5f5d714a57c0a90947
-# invoke contract `TransactionEnvelope` (truncated here)
-AAAAAgAAAABi/B0L0JGythwN1lY0aypo19NHxvLCyO5tBEc...F9wX14QAAAAARAAAAAwAAAAAAAAAAAAAAAQAAAAAAAAAYAAAAAAAAAAGd/IhWQcE2UdzIof7ygqCuAmYD8ycsJbB
-# invoke contract transaction `Hash`
-4f6457d3fc081ab3a72dfe7ee2236f3a282c62f21d7e3dbdb5b13ac0d09c8647
-# base64-encoded `ConfigUpgradeSetKey`
-nfyIVkHBNlHcyKH+8oKgrgJmA/MnLCW3E4Fhg4XYTkqZa2MyqzRdB2+mN3DOKUFKtZIAXp6o3DHrkgR0mo7rUw==
-```
-
-### 3. Enviar Transacciones de Actualización de Configuraciones
-
-Estas cuatro transacciones pueden ser enviadas a la red a través de tu nodo. Reemplaza los marcadores de posición a continuación con los `TransactionEnvelope`s en las líneas 1, 3, 5 y 7.
-
-:::note
-
-Si no proporcionaste el parámetro `--signtxs` al comando `get-settings-upgrade-txs`, no olvides firmarlas antes de enviarlas a la red.
-
-:::
-
-```bash
-http-command 'tx?blob=<LINE_1_OUTPUT>'
-http-command 'tx?blob=<LINE_3_OUTPUT>'
-http-command 'tx?blob=<LINE_5_OUTPUT>'
-http-command 'tx?blob=<LINE_7_OUTPUT>'
-```
-
-### 4. Verificar Actualizaciones Propuestas
-
-Puedes verificar que las actualizaciones propuestas han sido configuradas usando el comando `dumpproposedsettings` de stellar-core, proporcionando la cadena XDR `ConfigUpgradeSetKey` de la línea 9 arriba:
-
-```bash
-http-command 'dumpproposedsettings?blob=<LINE_9_OUTPUT>'
-```
-
-### 5. Programar las Actualizaciones
-
-Ahora puedes programar la actualización en todos los validators requeridos usando el comando `upgrades` de stellar-core, proporcionando la salida `ConfigUpgradeSetKey` de la línea 9 arriba y un tiempo acordado en el futuro:
-
-```bash
-http-command 'upgrades?mode=set&upgradetime=YYYY-MM-DDTHH:MM:SSZ&configupgradesetkey=<LINE_9_OUTPUT>'
-```
-
-### 6. Actualizar Stellar Expert
-
-Uno de los métodos más utilizados para "seguir" una actualización de las configuraciones de Soroban de la red es la [página del Historial de Protocolo] en [stellar.expert].
-
-Para asegurarte de que esa página se actualice con las actualizaciones propuestas, por favor completa un PR contra [este repositorio].
-
-### Depuración
-
-Una vez que se ejecuten las cuatro transacciones, deberías ver la actualización propuesta al ejecutar el comando `dumpproposedsettings` ([ver paso 4 arriba](#4-verify-proposed-upgrades)). Si no lo haces, entonces uno o más de los transacciones anteriores fallaron durante la aplicación, o la actualización es inválida. Si alguna de las transacciones anteriores falla durante el envío, deberías recibir un `TransactionResult` como respuesta junto con el motivo de la falla.
-
-Si alguna de las transacciones anteriores falla durante la presentación, deberías recibir un `TransactionResult` como respuesta junto con el motivo de la falla. La falla será más probablemente debido a una de las siguientes razones:
-
-- Los recursos son demasiado bajos. Necesitarás aumentar los recursos codificados en [`SettingsUpgradeUtils.cpp`].
-- La tarifa o la tarifa reembolsable son demasiado bajas. Necesitarás aumentarlas en [`SettingsUpgradeUtils.cpp`].
-- Wasm ha caducado. Necesitarás restaurar el Wasm.
-
-Deberías confirmar qué causó la falla viendo el `TransactionResult` de la transacción fallida usando el [Stellar Lab](https://lab.stellar.org) o un explorador de bloques.
-
-Si las transacciones tuvieron éxito pero el comando `dumpproposedsettings` todavía devuelve un error, entonces la actualización es inválida. La reportación de errores aquí necesita ser mejorada, pero las comprobaciones de validez ocurren [aquí](https://github.com/stellar/stellar-core/blob/3007c595c2fe9b53502aa0daf8089d119a9c37cb/src/herder/Upgrades.cpp#L1451).
-
-## Examinar una Actualización Propuesta
-
-Puedes usar el comando `dumpproposedsettings` de stellar-core junto con una cadena XDR `ConfigUpgradeSetKey` codificada en base64 para consultar una actualización propuesta:
-
-```bash
-http-command 'dumpproposedsettings?blob=A6MvjFLujnqaZa5hacafWyYwhpk4cgRpyu0z6ilZ0pm1S7fmjSNnsyjGwGodLGiD8ss8S1AHiOBBb6GQbOeMbw=='
-```
-
-## Examinar Configuraciones Actuales
-
-También puedes obtener las configuraciones actuales de Soroban para comparar usando `sorobaninfo` de stellar-core.
-
-```bash
-http-command 'sorobaninfo?format=detailed'
-```
-
-[`pubnet_phase1.json`]: https://github.com/stellar/stellar-core/blob/master/soroban-settings/pubnet_phase1.json
-[`pubnet_phase2.json`]: https://github.com/stellar/stellar-core/blob/master/soroban-settings/pubnet_phase2.json
-[binario precompilado]: https://github.com/stellar/stellar-cli/releases/latest
-[página del historial de protocolo]: https://stellar.expert/explorer/pubnet/protocol-history
-[stellar.expert]: https://stellar.expert
-[este repositorio]: https://github.com/stellar-expert/staged-soroban-upgrades
-[`settingsupgradeutils.cpp`]: https://github.com/stellar/stellar-core/blob/master/src/main/SettingsUpgradeUtils.cpp
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/tier-1-orgs.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/tier-1-orgs.mdx
deleted file mode 100644
index 7dca813300..0000000000
--- a/i18n/es/docusaurus-plugin-content-docs/current/validators/tier-1-orgs.mdx
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Organizaciones de Nivel 1
-sidebar_position: 30
----
-
-Para ayudar con la descentralización de Stellar, los equipos más avanzados que desarrollan en Stellar ejecutan validadores y se esfuerzan por unirse a las filas de "organizaciones de Nivel 1"
-
-Recuerda que la red Stellar se compone de organizaciones que cada una ejecuta validadores, y cada organización decide por sí misma, configurando un conjunto de quorum, de qué organizaciones y cuántas requiere acuerdo para comprometerse a un nuevo ledger particular. Las organizaciones de Nivel 1 son un grupo de organizaciones que, debido a que la mayoría de las otras organizaciones requieren su acuerdo, llevan sobre sus hombros la seguridad y la disponibilidad de la red Stellar.[^1]
-
-Para convertirse en una organización de Nivel 1, un equipo que ejecute validadores debe convencer a suficientes otras organizaciones en la red Stellar para que confíen en ellos al incluirlos en sus conjuntos de quorum. Como parte de este proceso, deben cumplir con algunos requisitos que son aceptados por la comunidad de validadores de Stellar. Por ejemplo, las organizaciones de Nivel 1 generalmente ejecutan tres validadores, coordinan cualquier cambio a sus conjuntos de quorum entre ellas y se adhieren a un estándar más alto de tiempo de actividad y capacidad de respuesta.
-
-Como administradora de la red Stellar, la SDF trabaja en estrecha colaboración con las organizaciones de Nivel 1 para asegurar la salud de la red, mantener una robusta intersección de quorum y construir redundancia para minimizar las interrupciones de la red. Esta guía describe los requisitos mínimos recomendados por la SDF para ser una organización de Nivel 1. Sin embargo, al final, la SDF por sí sola no puede agregar o quitar una organización de Nivel 1; esto depende de los conjuntos de quorum de muchas otras organizaciones en la red.
-
-## Por qué tres validadores
-
-La recomendación más importante para una organización de Nivel 1 es establecer y mantener tres validadores completos. ¿Por qué tres?
-
-En Stellar, los validadores eligen confiar en organizaciones cuando configuran su conjunto de quorum. Si eres una organización de confianza, quieres que tu presencia en la red persista incluso si un nodo falla o lo apagas para mantenimiento. Un trío de nodos validadores permite que eso suceda: al configurar sus conjuntos de quorum, otros participantes pueden requerir que ⅔ de tus nodos validadores estén de acuerdo. Si 1 tiene incidencias, no hay problema: los otros dos aún votan en nombre de tu organización, así que el espectáculo continúa. Para asegurar redundancia, también es importante que esos tres validadores completos estén geográficamente distribuidos: si están en el mismo centro de datos, corren el riesgo de caer al mismo tiempo.
-
-Aquí hay lo que las organizaciones de Nivel 1 también deberían esperar unas de otras:
-
-## Publicar Archivos de Historia
-
-Además de participar en el Stellar Consensus Protocol, un validador completo publica un archivo de transacciones de la red. Para hacer eso, necesitas configurar Stellar Core para grabar la historia en un archivo accesible públicamente y agregar la ubicación de ese archivo a tu stellar.toml. Recomendamos que, como organización de Nivel 1, deberías configurar cada uno de tus nodos para grabar la historia en un archivo separado.
-
-Los archivos públicos hacen que la red sea más resistente: cuando nuevos nodos se conectan, o cuando nodos existentes pierden sincronización, necesitan consultar un archivo para averiguar qué se perdieron. Compartir imágenes del ledger, que detallan transacciones y sus resultados, permite que esos nodos se pongan al día, y más archivos significan más redundancia y mayor descentralización. Además, compartir la historia mantiene a todos honestos.
-
-## Configurar un Conjunto de Quorum Seguro
-
-Por simplicidad, recomendamos que cada nodo de Nivel 1 use la misma configuración de conjunto de quorum, que se compone de conjuntos de quorum internos que representan a cada organización de Nivel 1.
-
-Para configurar un conjunto de quorum para tu validador, recomendamos incluir varias organizaciones de Nivel 1 o copiar el conjunto de quorum existente de Nivel 1 y agregar opcionalmente organizaciones adicionales en las que confíes. Usando organizaciones de Nivel 1 existentes como una red de seguridad, podemos trabajar juntos para expandir el quorum de manera metódica y deliberada.
-
-Para ver cómo se ve el conjunto de quorum recomendado actualmente, consulta el [ejemplo de archivo de configuración de Validador Completo](https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg).
-
-:::note
-
-Asegúrate de agregar correctamente tus propios validadores a los quorum sets de tus validadores. Como una organización de Nivel 1 con tres validadores y archivos históricos, SDF recomienda declarar tu organización como [`CALIDAD` ALTA](./admin-guide/configuring.mdx#validator-quality) en la configuración de tu quorum set. Declarar tu organización en un nivel de calidad inferior [puede limitar su participación en el consenso](./admin-guide/configuring.mdx#impact-of-validator-quality-on-nomination).
-
-:::
-
-## Declarar tu Nodo
-
-[SEP-20](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) es una especificación abierta que explica cómo funciona la auto-verificación de los nodos validadores. Los campos que especifica son bastante simples: debes establecer el dominio principal de la cuenta Stellar de tu validador a tu sitio web, donde publicas información sobre tu nodo y tu organización en un archivo stellar.toml.
-
-Es una manera fácil de propagar información y aprovecha la red para permitir que otros participantes descubran tu nodo y lo agreguen a sus conjuntos de quorum sin necesidad de una base de datos centralizada.
-
-## Mantén tus Nodos Actualizados
-
-Ejecutar un validador requiere vigilancia. Debes estar atento a tus nodos, mantenerlos actualizados con la última versión de Stellar Core y revisar los canales públicos para obtener información sobre lo que está sucediendo actualmente con otros validadores. A medida que las organizaciones se unen o salen de la red, es posible que debas actualizar la configuración del conjunto de quorum de tus validadores para asegurarte de que tengan una robusta intersección de quorum con Nivel 1 y una robusta disponibilidad de quorum.
-
-Las mejores dos maneras de hacer eso:
-
-- Unirse a la lista de correo de validadores [email list](https://groups.google.com/forum/#!forum/stellar-validators)
-- descargar Keybase y unirse al [canal #validators](https://keybase.io/team/stellar.public) en el equipo stellar.public
-
-Siempre anunciamos nuevos lanzamientos de Stellar Core en esos canales. También puedes encontrar esos lanzamientos en nuestro github.
-
-También es crítico que prestes atención a la información sobre lo que significan esas actualizaciones: a menudo, necesitarás configurar tus validadores para votar sobre algo oportuno, como cuándo votar para actualizar a una nueva versión del protocolo, o cuán alto establecer el límite de operaciones por ledger.
-
-## Coordinar con Otros Validadores
-
-Ya sea que ejecutes un trío de validadores o un solo nodo, es importante que coordines con otros validadores cuando realices un cambio significativo o notes algo incorrecto. Debes informarles cuando planeas:
-
-- Apagar tu nodo para mantenimiento
-- Hacer cambios en tu conjunto de quorum
-
-Informar a otros validadores cuando planeas apagar tu nodo para mantenimiento o actualizar a la última versión de stellar-core previene que una masa crítica de nodos se desconecten al mismo tiempo.
-
-Informar a otros validadores cuando planeas cambiar tu conjunto de quorum les permite responder, ajustar y pensar en las implicaciones del cambio. Para que la red Stellar se expanda de manera segura, la SDF recomienda que los validadores coordinen fuera de la cadena para mantener una buena intersección de quorum.
-
-## Monitorea tu conjunto de quorum
-
-Recomendamos usar Prometheus para extraer y almacenar tus métricas de stellar-core, y Grafana para renderizar esos datos para consumo humano. Puedes encontrar instrucciones paso a paso para configurar el monitoreo y las alertas en [Monitoreo y Diagnósticos](./admin-guide/monitoring.mdx), junto con enlaces a los paneles de Grafana que hemos creado para facilitar las cosas.
-
-También puedes usar [Stellarbeat](https://stellarbeat.io) para ver las configuraciones de quorum de los validadores, obtener información sobre su disponibilidad y tiempo de actividad, y el comando de quorum para diagnosticar problemas con el conjunto de quorum del nodo local.
-
-Deberías hacer revisiones periódicas de tu conjunto de quorum. Si los nodos tienen mal tiempo de actividad o demuestran ser poco confiables, es posible que debas eliminarlos de tu conjunto de quorum para no quedarte atascado y para que la red no se detenga. También puedes querer agregar nuevas organizaciones que comienzan a funcionar y demuestran ser confiables. Si planeas hacer alguna de esas cosas, recuerda comunicarte y coordinarte con otros validadores.
-
-## Ponte en contacto
-
-Si crees que puedes ser una organización de Nivel 1, háznoslo saber en el canal `#validators` en el [Discord de Desarrolladores de Stellar](https://discord.gg/stellardev). Los miembros de la comunidad pueden ayudarte en el proceso, y una vez que estés en marcha, los miembros del equipo de la SDF te ayudarán a unirte a Nivel 1, para que puedas tomar tu lugar como pilar de la red. Una vez que hayas demostrado que eres receptivo, confiable y mantienes un buen tiempo de actividad,<!-- `href`s needed --> la SDF puede recomendar que otros validadores ajusten su conjunto de quorum para incluir tus validadores.
-
-A medida que Stellar crece, y cada vez más empresas desarrollan en la red, las organizaciones de Nivel 1 serán cruciales para una expansión saludable de la red.
-
-[^1]: La noción de organización de Nivel 1 puede definirse con precisión, pero eso no es el objetivo de esta página. <!-- `href` needed -->
diff --git a/i18n/es/docusaurus-plugin-content-pages/index.mdx b/i18n/es/docusaurus-plugin-content-pages/index.mdx
deleted file mode 100644
index 8e2e776bcd..0000000000
--- a/i18n/es/docusaurus-plugin-content-pages/index.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-hide_table_of_contents: true
-title: Herramientas de desarrollador, SDKs y recursos clave para Desarrollar
-description: Desarrollar aplicaciones descentralizadas, emitir activos y escribir contratos inteligentes en la blockchain de capa 1 de Stellar. Conectarse a vías de pago y crear proyectos interoperables en una red abierta
----
-
-import WayfindingBoxes from "@site/src/components/Homepage/WayfindingBoxes";
-import NavigatingTheDocs from "@site/src/components/Homepage/NavigatingTheDocs";
-import DeveloperResources from "@site/src/components/Homepage/DeveloperResources";
-import PathfindingTable from "@site/src/components/Homepage/PathfindingTable";
-
-# Bienvenido a la Documentación para Desarrolladores de Stellar
-
-Stellar es una red blockchain de código abierto, descentralizada, peer-to-peer y de capa 1 que proporciona un marco para que los desarrolladores creen aplicaciones, emitan activos, escriban contratos inteligentes y se conecten a vías de pago existentes. Stellar está diseñada para permitir a creadores, innovadores y desarrolladores crear proyectos en la red que puedan interoperar entre sí.
-
-La documentación para desarrolladores te enseñará cómo crear aplicaciones, emitir y usar tokens, escribir contratos inteligentes, configurar rampas de entrada y salida, configurar un nodo validador, y más.
-
-## **Stellar para...**
-
-<WayfindingBoxes />
-
-<hr />
-
-## **Navegar por la documentación**
-
-Lo que cada sección principal de la documentación para desarrolladores contiene.
-
-<NavigatingTheDocs />
-
-## **Recursos para desarrolladores**
-
-Interactúa con otros desarrolladores de Stellar, mantente al día con los estándares del ecosistema y las actualizaciones del protocolo, y aprende sobre eventos futuros.
-
-<DeveloperResources />
-
-<hr />
diff --git a/i18n/es/docusaurus-plugin-content-pages/platforms.mdx b/i18n/es/docusaurus-plugin-content-pages/platforms.mdx
deleted file mode 100644
index d03075fb9f..0000000000
--- a/i18n/es/docusaurus-plugin-content-pages/platforms.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
-# Plataformas SDF
-
-SDF ha liberado como open-source algunas "plataformas" que facilitan lograr ciertas cosas en la red.
-
-## Anchor Platform
-
-La Anchor Platform es un conjunto de herramientas y APIs que permiten a los desarrolladores y empresas crear sus propios servicios de entrada y salida para la red Stellar. Proporciona una interfaz estandarizada, incluyendo la implementación de varias Propuestas del Ecosistema Stellar (SEPs), para facilitar a las empresas la integración con billeteras y exchanges basados en Stellar.
-
-[¡Aprende más sobre la API de la Anchor Platform aquí!](/platforms/anchor-platform)
-
-## Plataforma de Desembolso Stellar
-
-La Plataforma de Desembolso Stellar (SDP) permite a las organizaciones realizar pagos masivos a los destinatarios utilizando Stellar.
-
-[¡Aprende más sobre la API de la Plataforma de Desembolso Stellar aquí!](/platforms/stellar-disbursement-platform)
diff --git a/i18n/es/docusaurus-theme-classic/footer.json b/i18n/es/docusaurus-theme-classic/footer.json
deleted file mode 100644
index f29920d203..0000000000
--- a/i18n/es/docusaurus-theme-classic/footer.json
+++ /dev/null
@@ -1,98 +0,0 @@
-{
-  "link.title.Resources": {
-    "message": "Recursos",
-    "description": "The title of the footer links column with title=Resources in the footer"
-  },
-  "link.title.Tools": {
-    "message": "Herramientas",
-    "description": "The title of the footer links column with title=Tools in the footer"
-  },
-  "link.title.Community": {
-    "message": "Comunidad",
-    "description": "The title of the footer links column with title=Community in the footer"
-  },
-  "link.title.About": {
-    "message": "Acerca de",
-    "description": "The title of the footer links column with title=About in the footer"
-  },
-  "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"
-  },
-  "link.item.label.Stellar Quest": {
-    "message": "Búsqueda Stellar",
-    "description": "The label of footer link with label=Stellar Quest linking to https://quest.stellar.org/"
-  },
-  "link.item.label.Soroban Quest": {
-    "message": "Búsqueda Soroban",
-    "description": "The label of footer link with label=Soroban Quest linking to https://fastcheapandoutofcontrol.com/tutorial"
-  },
-  "link.item.label.YouTube": {
-    "message": "YouTube",
-    "description": "The label of footer link with label=YouTube linking to https://www.youtube.com/@StellarDevelopmentFoundation"
-  },
-  "link.item.label.Twitch": {
-    "message": "Twitch",
-    "description": "The label of footer link with label=Twitch linking to https://m.twitch.tv/stellarorg/home"
-  },
-  "link.item.label.Explorer": {
-    "message": "Explorador",
-    "description": "The label of footer link with label=Explorer linking to https://stellar.expert"
-  },
-  "link.item.label.Lab": {
-    "message": "Laboratorio",
-    "description": "The label of footer link with label=Lab linking to https://lab.stellar.org"
-  },
-  "link.item.label.Status": {
-    "message": "Estado",
-    "description": "The label of footer link with label=Status linking to https://status.stellar.org/"
-  },
-  "link.item.label.Dashboard": {
-    "message": "Tablero",
-    "description": "The label of footer link with label=Dashboard linking to https://dashboard.stellar.org/"
-  },
-  "link.item.label.All Tools": {
-    "message": "Todas las Herramientas",
-    "description": "The label of footer link with label=All Tools linking to /docs/tools"
-  },
-  "link.item.label.Contribute to Docs": {
-    "message": "Contribuir a la Documentación",
-    "description": "The label of footer link with label=Contribute to Docs linking to https://github.com/stellar/stellar-docs?tab=readme-ov-file#contributing"
-  },
-  "link.item.label.Developer Discord": {
-    "message": "Discord de Desarrolladores",
-    "description": "The label of footer link with label=Developer Discord linking to https://discord.gg/stellardev"
-  },
-  "link.item.label.Developer Google Group": {
-    "message": "Grupo de Google de Desarrolladores",
-    "description": "The label of footer link with label=Developer Google Group linking to https://groups.google.com/g/stellar-dev"
-  },
-  "link.item.label.Stack Exchange": {
-    "message": "Stack Exchange",
-    "description": "The label of footer link with label=Stack Exchange linking to https://stellar.stackexchange.com/"
-  },
-  "link.item.label.Stellar Community Fund": {
-    "message": "Fondo Comunitario Stellar",
-    "description": "The label of footer link with label=Stellar Community Fund linking to https://communityfund.stellar.org/"
-  },
-  "link.item.label.About SDF": {
-    "message": "Acerca de SDF",
-    "description": "The label of footer link with label=About SDF linking to https://stellar.org/foundation"
-  },
-  "link.item.label.Careers": {
-    "message": "Carreras",
-    "description": "The label of footer link with label=Careers linking to https://stellar.org/foundation/careers"
-  },
-  "link.item.label.Events": {
-    "message": "Eventos",
-    "description": "The label of footer link with label=Events linking to https://stellar.org/events"
-  },
-  "link.item.label.Grants & Funding": {
-    "message": "Subvenciones y Financiamiento",
-    "description": "The label of footer link with label=Grants & Funding linking to https://stellar.org/foundation/grants-and-funding"
-  },
-  "link.item.label.Developer Meetings": {
-    "message": "Reuniones de desarrolladores",
-    "description": "The label of footer link with label=Developer Meetings linking to /meetings"
-  }
-}
diff --git a/i18n/es/docusaurus-theme-classic/navbar.json b/i18n/es/docusaurus-theme-classic/navbar.json
deleted file mode 100644
index 1a8886d64d..0000000000
--- a/i18n/es/docusaurus-theme-classic/navbar.json
+++ /dev/null
@@ -1,314 +0,0 @@
-{
-  "item.label.Build": {
-    "message": "Desarrollar",
-    "description": "Navbar item with label Build"
-  },
-  "item.label.Learn": {
-    "message": "Aprender",
-    "description": "Navbar item with label Learn"
-  },
-  "item.label.Tokens": {
-    "message": "Tokens",
-    "description": "Navbar item with label Tokens"
-  },
-  "item.label.Data": {
-    "message": "Datos",
-    "description": "Navbar item with label Data"
-  },
-  "item.label.Tools": {
-    "message": "Herramientas",
-    "description": "Navbar item with label Tools"
-  },
-  "item.label.Networks": {
-    "message": "Redes",
-    "description": "Navbar item with label Networks"
-  },
-  "item.label.Validators": {
-    "message": "Validadores",
-    "description": "Navbar item with label Validators"
-  },
-  "item.label.Overview": {
-    "message": "Resumen",
-    "description": "Navbar item with label Overview"
-  },
-  "item.label.Introduction": {
-    "message": "Introducción",
-    "description": "Navbar item with label Introduction"
-  },
-  "item.label.Getting Started": {
-    "message": "Comenzar",
-    "description": "Navbar item with label Getting Started"
-  },
-  "item.label.Example Contracts": {
-    "message": "Contratos de ejemplo",
-    "description": "Navbar item with label Example Contracts"
-  },
-  "item.label.Application Design Considerations": {
-    "message": "Consideraciones sobre el diseño de la aplicación",
-    "description": "Navbar item with label Application Design Considerations"
-  },
-  "item.label.Tutorial: Wallet SDK": {
-    "message": "Tutorial: SDK de billeteras",
-    "description": "Navbar item with label Tutorial: Wallet SDK"
-  },
-  "item.label.Tutorial: Payment Application, JavaScript": {
-    "message": "Tutorial: Aplicación de pagos, JavaScript",
-    "description": "Navbar item with label Tutorial: Payment Application, JavaScript"
-  },
-  "item.label.Tutorial: Network Ingestion Pipeline": {
-    "message": "Tutorial: Canal de ingestión de red",
-    "description": "Navbar item with label Tutorial: Network Ingestion Pipeline"
-  },
-  "item.label.Tutorial: Passkey Dapp": {
-    "message": "Tutorial: Dapp con passkey",
-    "description": "Navbar item with label Tutorial: Passkey Dapp"
-  },
-  "item.label.Tutorial: Dapp Frontend": {
-    "message": "Tutorial: Frontend de Dapp",
-    "description": "Navbar item with label Tutorial: Dapp Frontend"
-  },
-  "item.label.Smart Wallets": {
-    "message": "Billeteras inteligentes",
-    "description": "Navbar item with label Smart Wallets"
-  },
-  "item.label.Contract Conventions": {
-    "message": "Convenciones de contratos",
-    "description": "Navbar item with label Contract Conventions"
-  },
-  "item.label.Contract Events": {
-    "message": "Eventos del contrato",
-    "description": "Navbar item with label Contract Events"
-  },
-  "item.label.Contract Storage": {
-    "message": "Almacenamiento del contrato",
-    "description": "Navbar item with label Contract Storage"
-  },
-  "item.label.Contract Testing": {
-    "message": "Pruebas de contratos",
-    "description": "Navbar item with label Contract Testing"
-  },
-  "item.label.Dapp Development": {
-    "message": "Desarrollo de Dapps",
-    "description": "Navbar item with label Dapp Development"
-  },
-  "item.label.Fees & Metering": {
-    "message": "Tarifas y medición",
-    "description": "Navbar item with label Fees & Metering"
-  },
-  "item.label.Freighter Wallet": {
-    "message": "Billetera Freighter",
-    "description": "Navbar item with label Freighter Wallet"
-  },
-  "item.label.Stellar Basics": {
-    "message": "Conceptos básicos de Stellar",
-    "description": "Navbar item with label Stellar Basics"
-  },
-  "item.label.RPC": {
-    "message": "RPC",
-    "description": "Navbar item with label RPC"
-  },
-  "item.label.State Archival": {
-    "message": "Archivado de estado",
-    "description": "Navbar item with label State Archival"
-  },
-  "item.label.Stellar Asset Contract Tokens": {
-    "message": "Tokens de contrato de activos Stellar",
-    "description": "Navbar item with label Stellar Asset Contract Tokens"
-  },
-  "item.label.Transactions": {
-    "message": "Transacciones",
-    "description": "Navbar item with label Transactions"
-  },
-  "item.label.Type Conversions": {
-    "message": "Conversiones de tipo",
-    "description": "Navbar item with label Type Conversions"
-  },
-  "item.label.Stellar Stack": {
-    "message": "Stack de Stellar",
-    "description": "Navbar item with label Stellar Stack"
-  },
-  "item.label.Lumens (XLM)": {
-    "message": "Lumens (XLM)",
-    "description": "Navbar item with label Lumens (XLM)"
-  },
-  "item.label.Stellar Consensus Protocol (SCP)": {
-    "message": "Protocolo de Consenso Stellar (SCP)",
-    "description": "Navbar item with label Stellar Consensus Protocol (SCP)"
-  },
-  "item.label.Data Structures": {
-    "message": "Estructuras de datos",
-    "description": "Navbar item with label Data Structures"
-  },
-  "item.label.Operations & Transactions": {
-    "message": "Operaciones y transacciones",
-    "description": "Navbar item with label Operations & Transactions"
-  },
-  "item.label.Stellar Ecosystem Proposals (SEPs)": {
-    "message": "Propuestas del ecosistema Stellar (SEPs)",
-    "description": "Navbar item with label Stellar Ecosystem Proposals (SEPs)"
-  },
-  "item.label.Smart Contracts": {
-    "message": "Contratos inteligentes",
-    "description": "Navbar item with label Smart Contracts"
-  },
-  "item.label.Data Format": {
-    "message": "Formato de datos",
-    "description": "Navbar item with label Data Format"
-  },
-  "item.label.Ramps (anchors)": {
-    "message": "Rampas (anchors)",
-    "description": "Navbar item with label Ramps (anchors)"
-  },
-  "item.label.Migrate from Another Chain": {
-    "message": "Migrar de otra cadena",
-    "description": "Navbar item with label Migrate from Another Chain"
-  },
-  "item.label.Interactive Learning": {
-    "message": "Aprendizaje interactivo",
-    "description": "Navbar item with label Interactive Learning"
-  },
-  "item.label.Stellar Assets & Contract Tokens": {
-    "message": "Activos Stellar y tokens de contrato",
-    "description": "Navbar item with label Stellar Assets & Contract Tokens"
-  },
-  "item.label.Assets Overview": {
-    "message": "Resumen de activos",
-    "description": "Navbar item with label Assets Overview"
-  },
-  "item.label.Quickstart Guide": {
-    "message": "Guía de inicio rápido",
-    "description": "Navbar item with label Quickstart Guide"
-  },
-  "item.label.Asset Design Considerations": {
-    "message": "Consideraciones para el diseño de activos",
-    "description": "Navbar item with label Asset Design Considerations"
-  },
-  "item.label.Stellar Asset Contract": {
-    "message": "Contrato de activo Stellar",
-    "description": "Navbar item with label Stellar Asset Contract"
-  },
-  "item.label.Token Interface": {
-    "message": "Interfaz del token",
-    "description": "Navbar item with label Token Interface"
-  },
-  "item.label.Tutorial: Issue an Asset": {
-    "message": "Tutorial: Emitir un activo",
-    "description": "Navbar item with label Tutorial: Issue an Asset"
-  },
-  "item.label.Publish Asset Information": {
-    "message": "Publicar información del activo",
-    "description": "Navbar item with label Publish Asset Information"
-  },
-  "item.label.Hubble": {
-    "message": "Hubble",
-    "description": "Navbar item with label Hubble"
-  },
-  "item.label.Providers": {
-    "message": "Proveedores",
-    "description": "Navbar item with label Providers"
-  },
-  "item.label.Horizon": {
-    "message": "Horizon",
-    "description": "Navbar item with label Horizon"
-  },
-  "item.label.Migrate Horizon to RPC": {
-    "message": "Migrar Horizon a RPC",
-    "description": "Navbar item with label Migrate Horizon to RPC"
-  },
-  "item.label.Build Your Own": {
-    "message": "Construir el tuyo",
-    "description": "Navbar item with label Build Your Own"
-  },
-  "item.label.SDKs": {
-    "message": "SDKs",
-    "description": "Navbar item with label SDKs"
-  },
-  "item.label.Stellar CLI": {
-    "message": "Stellar CLI",
-    "description": "Navbar item with label Stellar CLI"
-  },
-  "item.label.Lab": {
-    "message": "Laboratorio",
-    "description": "Navbar item with label Lab"
-  },
-  "item.label.Quickstart": {
-    "message": "Guía rápida",
-    "description": "Navbar item with label Quickstart"
-  },
-  "item.label.More Developer Tools": {
-    "message": "Más herramientas para desarrolladores",
-    "description": "Navbar item with label More Developer Tools"
-  },
-  "item.label.MoneyGram Ramps": {
-    "message": "Rampas de MoneyGram",
-    "description": "Navbar item with label MoneyGram Ramps"
-  },
-  "item.label.Cross-Chain": {
-    "message": "Entre cadenas",
-    "description": "Navbar item with label Cross-Chain"
-  },
-  "item.label.Anchor Platform": {
-    "message": "Anchor Platform",
-    "description": "Navbar item with label Anchor Platform"
-  },
-  "item.label.Stellar Disbursement Platform": {
-    "message": "Stellar Disbursement Platform",
-    "description": "Navbar item with label Stellar Disbursement Platform"
-  },
-  "item.label.Software Versions": {
-    "message": "Versiones de software",
-    "description": "Navbar item with label Software Versions"
-  },
-  "item.label.Resource Limits & Fees": {
-    "message": "Límites de recursos y tarifas",
-    "description": "Navbar item with label Resource Limits & Fees"
-  },
-  "item.label.Validators Introduction": {
-    "message": "Introducción a validadores",
-    "description": "Navbar item with label Validators Introduction"
-  },
-  "item.label.Admin Guide": {
-    "message": "Guía del administrador",
-    "description": "Navbar item with label Admin Guide"
-  },
-  "item.label.Tier 1 Organizations": {
-    "message": "Organizaciones de nivel 1",
-    "description": "Navbar item with label Tier 1 Organizations"
-  },
-  "item.label.Contract Authorization": {
-    "message": "Autorización de contrato",
-    "description": "Navbar item with label Contract Authorization"
-  },
-  "item.label.OpenZeppelin Contracts": {
-    "message": "Contratos de OpenZeppelin",
-    "description": "Navbar item with label OpenZeppelin Contracts"
-  },
-  "item.label.Tutorial: Payment Application, Swift": {
-    "message": "Tutorial: Aplicación de Pago, Swift",
-    "description": "Navbar item with label Tutorial: Payment Application, Swift"
-  },
-  "item.label.SDEX": {
-    "message": "SDEX",
-    "description": "Navbar item with label SDEX"
-  },
-  "item.label.RPC Providers": {
-    "message": "Proveedores RPC",
-    "description": "Navbar item with label RPC Providers"
-  },
-  "item.label.Horizon Providers": {
-    "message": "Proveedores Horizon",
-    "description": "Navbar item with label Horizon Providers"
-  },
-  "item.label.Scaffold Stellar": {
-    "message": "Estructurar Stellar",
-    "description": "Navbar item with label Scaffold Stellar"
-  },
-  "item.label.Networks Overview": {
-    "message": "Resumen de Redes",
-    "description": "Navbar item with label Networks Overview"
-  },
-  "item.label.Contract Accounts": {
-    "message": "Cuentas de Contrato",
-    "description": "Navbar item with label Contract Accounts"
-  }
-}
diff --git a/package.json b/package.json
index b64226f603..046f95129e 100644
--- a/package.json
+++ b/package.json
@@ -17,7 +17,6 @@
     "bundle-stellar-disbursement-platform": "redocly bundle stellar-disbursement-platform --output openapi/stellar-disbursement-platform/bundled.yaml",
     "api:gen": "docusaurus gen-api-docs all && rm docs/data/apis/horizon/api-reference/*.info.mdx && rm docs/platforms/anchor-platform/api-reference/{callbacks,platform/transactions}/*.info.mdx && rm docs/platforms/stellar-disbursement-platform/api-reference/*.info.mdx",
     "api": "yarn api:clean && yarn api:bundle && yarn api:gen",
-    "write-translations": "docusaurus write-translations",
     "write-heading-ids": "docusaurus write-heading-ids",
     "format:mdx": "prettier --config .prettierrc.js --write \"{docs,src/pages,meeting-notes}/**/*.{md,mdx}\"",
     "ci-format:mdx": "prettier --config .prettierrc.js --write --log-level silent \"{docs,src/pages,meeting-notes}/**/*.{md,mdx}\"",
@@ -31,10 +30,7 @@
     "rpcspec:build": "node openrpc/scripts/build.mjs",
     "rpcspec:validate": "node openrpc/scripts/build.mjs && node openrpc/scripts/validate.mjs",
     "stellar-cli:build": "node scripts/stellar_cli_plugins.mjs && node scripts/stellar_cli.mjs",
-    "stellar-cli:fix-links": "./scripts/fix_cli_links.sh",
-    "crowdin": "crowdin",
-    "crowdin:fix": "node scripts/copyIgnoredFiles.mjs && ./scripts/fix_translations.sh",
-    "crowdin:sync": "docusaurus write-translations && crowdin upload --no-progress --delete-obsolete && crowdin download --no-progress"
+    "stellar-cli:fix-links": "./scripts/fix_cli_links.sh"
   },
   "dependencies": {
     "@docusaurus/core": "3.9.2",
@@ -74,7 +70,6 @@
     ]
   },
   "devDependencies": {
-    "@crowdin/cli": "^4.14.1",
     "@docusaurus/eslint-plugin": "3.9.2",
     "@docusaurus/module-type-aliases": "3.9.2",
     "@docusaurus/tsconfig": "3.9.2",
diff --git a/scripts/copyIgnoredFiles.mjs b/scripts/copyIgnoredFiles.mjs
deleted file mode 100644
index 11dd67a1ea..0000000000
--- a/scripts/copyIgnoredFiles.mjs
+++ /dev/null
@@ -1,126 +0,0 @@
-import fs from 'fs';
-import path from 'path';
-import { globSync } from 'glob';
-// import glob from 'glob';
-import yaml from 'js-yaml';
-
-// Define the list of language codes
-const languages = ['es'];
-
-/**
- * Reads and parses the crowdin.yaml file.
- * @param {string} filePath - The path to the crowdin.yaml file.
- * @returns {Object} - The parsed configuration object.
- */
-function readCrowdinConfig(filePath) {
-    try {
-        const fileContent = fs.readFileSync(filePath, 'utf8');
-        return yaml.load(fileContent);
-    } catch (err) {
-        logMessage(`Error reading or parsing the file ${filePath}: ${err.message}`);
-        process.exit(1);
-    }
-}
-
-/**
- * Extracts the sources array from the configuration object.
- * @param {Object} config - The parsed configuration object.
- * @returns {string[]} - The array of source paths.
- */
-function extractSources(config) {
-    return config.files.map(file => file.source.replace(/\/\*\*\/\*$/, '').replace(/^\//, ''));
-}
-
-/**
- * Logs a message to the console with a timestamp.
- * @param {string} message - The message to log.
- */
-function logMessage(message) {
-    console.log(`[${new Date().toISOString()}] ${message}`);
-}
-
-/**
- * Copies a file or directory from source to destination.
- * @param {string} src - The source path.
- * @param {string} dest - The destination path.
- */
-function copyFileOrDirectory(src, dest) {
-    const destDir = path.dirname(dest);
-    fs.mkdirSync(destDir, { recursive: true });
-
-    const stat = fs.statSync(src);
-    if (stat.isDirectory()) {
-        fs.cpSync(src, dest, { recursive: true });
-        logMessage(`Successfully copied directory ${src} to ${dest}`);
-    } else {
-        fs.copyFileSync(src, dest);
-        logMessage(`Successfully copied file ${src} to ${dest}`);
-    }
-}
-
-/**
- * Replaces placeholders in the translation path with actual values.
- * @param {string} translationPath - The translation path template.
- * @param {string} languageCode - The language code to replace placeholders.
- * @param {string} srcPath - The source file path.
- * @param {string[]} sources - The array of source paths.
- * @returns {string} - The translation path with placeholders replaced.
- */
-function getTranslationPath(translationPath, languageCode, srcPath, sources) {
-    let relativePath = srcPath;
-
-    for (const source of sources) {
-        if (srcPath.startsWith(source)) {
-            relativePath = srcPath.replace(`${source}/`, '');
-            break;
-        }
-    }
-
-    const destPath = translationPath
-        .replace('%two_letters_code%', languageCode)
-        .replace('%original_file_name%', path.basename(srcPath))
-        .replace('**', path.dirname(relativePath).replace(/\\/g, '/'));
-
-    return path.join(process.cwd(), destPath);
-}
-
-/**
- * Copies ignored files for each language based on the configuration.
- */
-function copyIgnoredFilesForLanguages(config) {
-    const sources = extractSources(config);
-
-    config.files.forEach(({ source, translation, ignore = [] }) => {
-        ignore.forEach(ignorePattern => {
-            let srcPattern = source
-                .replace(/^\//, '') // Strip the leading slash for the source path
-                .replace(/\*\*\/\*$/, ''); // strips the glob patter from the end
-            srcPattern += ignorePattern;
-
-            const files = globSync(srcPattern);
-            if (!files) {
-                logMessage(`Error processing pattern ${srcPattern}`);
-                return;
-            }
-
-            files.forEach(srcPath => {
-                languages.forEach(languageCode => {
-                    const destPath = getTranslationPath(translation, languageCode, srcPath, sources);
-                    copyFileOrDirectory(srcPath, destPath);
-                });
-            });
-        });
-    });
-}
-
-/**
- * Main function to execute the workflow.
- */
-function main() {
-    const config = readCrowdinConfig('crowdin.yaml');
-    copyIgnoredFilesForLanguages(config);
-    logMessage('Ignored files copied for all specified languages.');
-}
-
-// Execute the main function
-main();
diff --git a/scripts/fix_translations.sh b/scripts/fix_translations.sh
deleted file mode 100755
index ac605936d7..0000000000
--- a/scripts/fix_translations.sh
+++ /dev/null
@@ -1,6 +0,0 @@
-#!/usr/bin/env sh
-
-perl -i -pe's/\s\{/ \\{/g' i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/transactions/list-of-operations.mdx
-perl -i -pe's/<\s(.*\.mdx)>/\1/' i18n/es/docusaurus-plugin-content-docs-ap/**/admin-guide/component/observer/observer.mdx
-find i18n/es/docusaurus-plugin-content-docs/current -type f -print0 | xargs -0 perl -i -pe's/{\/_/{\/\*/'
-find i18n/es/docusaurus-plugin-content-docs/current -type f -print0 | xargs -0 perl -i -pe's/_\/}/\*\/}/'
diff --git a/yarn.lock b/yarn.lock
index d6989fc5c9..6d7f215b1d 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -1147,17 +1147,6 @@
   resolved "https://registry.npmjs.org/@colors/colors/-/colors-1.5.0.tgz"
   integrity sha512-ooWCrlZP11i8GImSjTHYHLkvFDP48nS4+204nGb1RiX/WXYHmJA2III9/e2DWVabCESdW7hBAEzHRqUn9OUVvQ==
 
-"@crowdin/cli@^4.14.1":
-  version "4.14.1"
-  resolved "https://registry.npmjs.org/@crowdin/cli/-/cli-4.14.1.tgz"
-  integrity sha512-kPhXW4Cw8feITgN1ymH9UPScKoFj5IwIL3PbKSeF/UhQW9jjVsjlGVO5WM0QYy5kZYJWQ+4e81ciXFr5vyflqQ==
-  dependencies:
-    command-exists-promise "^2.0.2"
-    node-fetch "2.7.0"
-    shelljs "^0.10.0"
-    tar "^7.5.2"
-    yauzl "^3.2.0"
-
 "@csstools/cascade-layer-name-parser@^2.0.5":
   version "2.0.5"
   resolved "https://registry.npmjs.org/@csstools/cascade-layer-name-parser/-/cascade-layer-name-parser-2.0.5.tgz"
@@ -2291,13 +2280,6 @@
   resolved "https://registry.npmjs.org/@isaacs/cliui/-/cliui-9.0.0.tgz"
   integrity sha512-AokJm4tuBHillT+FpMtxQ60n8ObyXBatq7jD2/JA9dxbDDokKQm8KMht5ibGzLVU9IJDIKK4TPKgMHEYMn3lMg==
 
-"@isaacs/fs-minipass@^4.0.0":
-  version "4.0.1"
-  resolved "https://registry.npmjs.org/@isaacs/fs-minipass/-/fs-minipass-4.0.1.tgz"
-  integrity sha512-wgm9Ehl2jpeqP3zw/7mo3kRHFp5MEDhqAdwy1fTGkHAwnkGOVsgpvQhL8B5n1qlb01jV3n/bI0ZfZp5lWA1k4w==
-  dependencies:
-    minipass "^7.0.4"
-
 "@jest/schemas@^29.6.3":
   version "29.6.3"
   resolved "https://registry.npmjs.org/@jest/schemas/-/schemas-29.6.3.tgz"
@@ -5143,11 +5125,6 @@ browserslist@^4.0.0, browserslist@^4.23.0, browserslist@^4.24.0, browserslist@^4
     node-releases "^2.0.27"
     update-browserslist-db "^1.2.0"
 
-buffer-crc32@~0.2.3:
-  version "0.2.13"
-  resolved "https://registry.npmjs.org/buffer-crc32/-/buffer-crc32-0.2.13.tgz"
-  integrity sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==
-
 buffer-from@^1.0.0:
   version "1.1.2"
   resolved "https://registry.npmjs.org/buffer-from/-/buffer-from-1.1.2.tgz"
@@ -5404,11 +5381,6 @@ chokidar@^4.0.0:
   dependencies:
     readdirp "^4.0.1"
 
-chownr@^3.0.0:
-  version "3.0.0"
-  resolved "https://registry.npmjs.org/chownr/-/chownr-3.0.0.tgz"
-  integrity sha512-+IxzY9BZOQd/XuYPRmrvEVjF/nqj5kgT4kEq7VofrDoM1MxoRjEWkrCC3EtLi59TVawxTAn+orJwFQcrqEN1+g==
-
 chrome-trace-event@^1.0.2:
   version "1.0.4"
   resolved "https://registry.npmjs.org/chrome-trace-event/-/chrome-trace-event-1.0.4.tgz"
@@ -5525,11 +5497,6 @@ comma-separated-tokens@^2.0.0:
   resolved "https://registry.npmjs.org/comma-separated-tokens/-/comma-separated-tokens-2.0.3.tgz"
   integrity sha512-Fu4hJdvzeylCfQPp9SGWidpzrMs7tTrlu6Vb8XGaRGck8QSNZJJp538Wrb60Lax4fPwR64ViY468OIUTbRlGZg==
 
-command-exists-promise@^2.0.2:
-  version "2.0.2"
-  resolved "https://registry.npmjs.org/command-exists-promise/-/command-exists-promise-2.0.2.tgz"
-  integrity sha512-T6PB6vdFrwnHXg/I0kivM3DqaCGZLjjYSOe0a5WgFKcz1sOnmOeIjnhQPXVXX3QjVbLyTJ85lJkX6lUpukTzaA==
-
 commander@2.20.3, commander@^2.20.0:
   version "2.20.3"
   resolved "https://registry.npmjs.org/commander/-/commander-2.20.3.tgz"
@@ -7093,7 +7060,7 @@ fast-deep-equal@^3.1.1, fast-deep-equal@^3.1.3:
   resolved "https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-3.1.3.tgz"
   integrity sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==
 
-fast-glob@^3.2.11, fast-glob@^3.2.9, fast-glob@^3.3.0, fast-glob@^3.3.2:
+fast-glob@^3.2.11, fast-glob@^3.2.9, fast-glob@^3.3.0:
   version "3.3.3"
   resolved "https://registry.npmjs.org/fast-glob/-/fast-glob-3.3.3.tgz"
   integrity sha512-7MptL8U0cqcFdzIzwOTHoilX9x5BrNqye7Z/LuC7kCMRio1EMSyqRK3BEAUD7sXRq4iT4AzTVuZdhgQ2TCvYLg==
@@ -10548,18 +10515,11 @@ minimist@^1.2.0, minimist@^1.2.5, minimist@^1.2.6:
   resolved "https://registry.npmjs.org/minimist/-/minimist-1.2.8.tgz"
   integrity sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==
 
-"minipass@^5.0.0 || ^6.0.2 || ^7.0.0", minipass@^7.0.4, minipass@^7.1.2, minipass@^7.1.3:
+"minipass@^5.0.0 || ^6.0.2 || ^7.0.0", minipass@^7.1.2, minipass@^7.1.3:
   version "7.1.3"
   resolved "https://registry.npmjs.org/minipass/-/minipass-7.1.3.tgz"
   integrity sha512-tEBHqDnIoM/1rXME1zgka9g6Q2lcoCkxHLuc7ODJ5BxbP5d4c2Z5cGgtXAku59200Cx7diuHTOYfSBD8n6mm8A==
 
-minizlib@^3.1.0:
-  version "3.1.0"
-  resolved "https://registry.npmjs.org/minizlib/-/minizlib-3.1.0.tgz"
-  integrity sha512-KZxYo1BUkWD2TVFLr0MQoM8vUUigWD3LlD83a/75BqC+4qE0Hb1Vo5v1FgcfaNXvfXzr+5EhQ6ing/CaBijTlw==
-  dependencies:
-    minipass "^7.1.2"
-
 mlly@^1.7.3, mlly@^1.7.4:
   version "1.7.4"
   resolved "https://registry.npmjs.org/mlly/-/mlly-1.7.4.tgz"
@@ -10710,7 +10670,7 @@ node-fetch-h2@^2.3.0:
   dependencies:
     http2-client "^1.2.5"
 
-node-fetch@2.7.0, node-fetch@^2.6.1:
+node-fetch@^2.6.1:
   version "2.7.0"
   resolved "https://registry.npmjs.org/node-fetch/-/node-fetch-2.7.0.tgz"
   integrity sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A==
@@ -11286,11 +11246,6 @@ pathe@^2.0.1:
   resolved "https://registry.npmjs.org/pathe/-/pathe-2.0.3.tgz"
   integrity sha512-WUjGcAqP1gQacoQe+OBJsFA7Ld4DyXuUIjZ5cc75cLHvJ7dtNsTugphxIADwspS+AraAUePCKrSVtPLFj/F88w==
 
-pend@~1.2.0:
-  version "1.2.0"
-  resolved "https://registry.npmjs.org/pend/-/pend-1.2.0.tgz"
-  integrity sha512-F3asv42UuXchdzt+xXqfW1OGlVBe+mxa2mqI0pg5yAHZPvFmY3Y6drSf/GQ1A86WgWEN9Kzh/WrgKa6iGcHXLg==
-
 perfect-scrollbar@^1.5.5:
   version "1.5.6"
   resolved "https://registry.npmjs.org/perfect-scrollbar/-/perfect-scrollbar-1.5.6.tgz"
@@ -13169,14 +13124,6 @@ shelljs@0.8.5:
     interpret "^1.0.0"
     rechoir "^0.6.2"
 
-shelljs@^0.10.0:
-  version "0.10.0"
-  resolved "https://registry.npmjs.org/shelljs/-/shelljs-0.10.0.tgz"
-  integrity sha512-Jex+xw5Mg2qMZL3qnzXIfaxEtBaC4n7xifqaqtrZDdlheR70OGkydrPJWT0V1cA1k3nanC86x9FwAmQl6w3Klw==
-  dependencies:
-    execa "^5.1.1"
-    fast-glob "^3.3.2"
-
 should-equal@^2.0.0:
   version "2.0.0"
   resolved "https://registry.npmjs.org/should-equal/-/should-equal-2.0.0.tgz"
@@ -13718,17 +13665,6 @@ tapable@^2.0.0, tapable@^2.2.1, tapable@^2.3.0:
   resolved "https://registry.npmjs.org/tapable/-/tapable-2.3.0.tgz"
   integrity sha512-g9ljZiwki/LfxmQADO3dEY1CbpmXT5Hm2fJ+QaGKwSXUylMybePR7/67YW7jOrrvjEgL1Fmz5kzyAjWVWLlucg==
 
-tar@^7.5.2:
-  version "7.5.11"
-  resolved "https://registry.npmjs.org/tar/-/tar-7.5.11.tgz"
-  integrity sha512-ChjMH33/KetonMTAtpYdgUFr0tbz69Fp2v7zWxQfYZX4g5ZN2nOBXm1R2xyA+lMIKrLKIoKAwFj93jE/avX9cQ==
-  dependencies:
-    "@isaacs/fs-minipass" "^4.0.0"
-    chownr "^3.0.0"
-    minipass "^7.1.2"
-    minizlib "^3.1.0"
-    yallist "^5.0.0"
-
 terser-webpack-plugin@^5.3.16, terser-webpack-plugin@^5.3.9:
   version "5.3.16"
   resolved "https://registry.npmjs.org/terser-webpack-plugin/-/terser-webpack-plugin-5.3.16.tgz"
@@ -14798,11 +14734,6 @@ yallist@^3.0.2:
   resolved "https://registry.npmjs.org/yallist/-/yallist-3.1.1.tgz"
   integrity sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==
 
-yallist@^5.0.0:
-  version "5.0.0"
-  resolved "https://registry.npmjs.org/yallist/-/yallist-5.0.0.tgz"
-  integrity sha512-YgvUTfwqyc7UXVMrB+SImsVYSmTS8X/tSrtdNZMImM+n7+QTriRXyXim0mBrTXNeqzVF0KWGgHPeiyViFFrNDw==
-
 yaml-ast-parser@0.0.43:
   version "0.0.43"
   resolved "https://registry.npmjs.org/yaml-ast-parser/-/yaml-ast-parser-0.0.43.tgz"
@@ -14836,14 +14767,6 @@ yargs@17.0.1, yargs@^17.0.1:
     y18n "^5.0.5"
     yargs-parser "^20.2.2"
 
-yauzl@^3.2.0:
-  version "3.2.1"
-  resolved "https://registry.yarnpkg.com/yauzl/-/yauzl-3.2.1.tgz#d35befb9a0fdd328da41926be895ade2de14dbe7"
-  integrity sha512-k1isifdbpNSFEHFJ1ZY4YDewv0IH9FR61lDetaRMD3j2ae3bIXGV+7c+LHCqtQGofSd8PIyV4X6+dHMAnSr60A==
-  dependencies:
-    buffer-crc32 "~0.2.3"
-    pend "~1.2.0"
-
 yocto-queue@^0.1.0:
   version "0.1.0"
   resolved "https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz"